Industrial automation systems and integration — Integration of life-cycle data for process plants including oil and gas production facilities — Part 13: Integrated asset planning life-cycle

ISO 15926-13:2018 specifies an ontology for asset planning for process plants, including oil and gas production facilities. In addition, it specifies an XML schema, derived from the ontology, for exchange of data used for asset planning. The following are within the scope of ISO 15926-13:2018: · portfolio, programme and project plans and schedules; · operational modification and ongoing maintenance plans and schedules; · calendars for plan execution; · constraints on the temporal relationships between items within plans and schedules, including succession link, lag, free and total float; · activity breakdown structures; · locations of activities; · resources required, including material, equipment and human resources, and their costs; · interfaces to systems that process work orders and purchase orders; · responsible organizations and people; · progress tracking and resource usage; · reference to standard classes of facility, activity and resource. The following are outside the scope of ISO 15926-13:2018: · standard classes of facility, activity and resource; · production planning; · plan simulation and optimization; · hazard identification and risk analysis; · manning and training of personnel; · budgeting and cost allocation.

Systèmes d'automatisation industrielle et intégration — Intégration de données de cycle de vie pour les industries de "process", y compris les usines de production de pétrole et de gaz — Partie 13: Titre manque

General Information

Status
Published
Publication Date
01-Aug-2018
Current Stage
9020 - International Standard under periodical review
Start Date
15-Jul-2023
Completion Date
15-Jul-2023
Ref Project

Buy Standard

Standard
ISO 15926-13:2018 - Industrial automation systems and integration -- Integration of life-cycle data for process plants including oil and gas production facilities
English language
96 pages
sale 15% off
Preview
sale 15% off
Preview

Standards Content (Sample)

INTERNATIONAL ISO
STANDARD 15926-13
First edition
2018-08
Industrial automation systems and
integration — Integration of life-cycle
data for process plants including oil
and gas production facilities —
Part 13:
Integrated asset planning life-cycle
Systèmes d'automatisation industrielle et intégration — Intégration
de données de cycle de vie pour les industries de "process", y compris
les usines de production de pétrole et de gaz —
Reference number
ISO 15926-13:2018(E)
©
ISO 2018

---------------------- Page: 1 ----------------------
ISO 15926-13:2018(E)

COPYRIGHT PROTECTED DOCUMENT
© ISO 2018
All rights reserved. Unless otherwise specified, or required in the context of its implementation, no part of this publication may
be reproduced or utilized otherwise in any form or by any means, electronic or mechanical, including photocopying, or posting
on the internet or an intranet, without prior written permission. Permission can be requested from either ISO at the address
below or ISO’s member body in the country of the requester.
ISO copyright office
CP 401 • Ch. de Blandonnet 8
CH-1214 Vernier, Geneva
Phone: +41 22 749 01 11
Fax: +41 22 749 09 47
Email: copyright@iso.org
Website: www.iso.org
Published in Switzerland
ii © ISO 2018 – All rights reserved

---------------------- Page: 2 ----------------------
ISO 15926-13:2018(E)

Contents Page
Foreword .v
Introduction .vi
1 Scope . 1
2 Normative references . 2
3 Terms, definitions, symbols and abbreviated terms . 2
3.1 Terms and definitions . 2
3.2 Abbreviated terms . 6
3.3 Symbols . 7
4 Layers and extension of integrated asset planning life-cycle data .8
4.1 Layers for integrated asset planning life-cycle data . 8
4.2 The documentation of the layers . 9
4.3 Use of the layers .10
4.4 Extensions for particular engineering applications .10
4.5 Simplification for a scheduling application view .10
5 Representation of planning data .12
5.1 Basis of the approach .12
5.2 Fundamental planning objects .14
5.2.1 Objective of planning . . .14
5.2.2 Required or proposed activity and specification .15
5.2.3 Alternative specifications .17
5.3 Schedule .18
5.3.1 Definition of a schedule .18
5.3.2 Level of a schedule .19
5.3.3 Role of a schedule . .20
5.4 Planning activity .21
5.5 Actual activity that fulfils a requirement .22
5.6 Decomposition of an activity .23
5.6.1 Parts of activities and their level .23
5.6.2 Decomposition of a specification .24
5.7 Classifications of an activity .25
5.7.1 Activity purpose and activity breakdown .25
5.7.2 Activity management objective .25
5.7.3 Asset life-cycle phase .26
5.7.4 Activity risk.27
5.7.5 Activity criticality .27
5.7.6 Activity priority .28
5.7.7 Activity completion status .28
5.7.8 Activity planning status .30
5.8 Resource for an activity .31
5.8.1 Specification of a resource.31
5.8.2 Resource breakdown . .34
5.8.3 Available physical object for a resource . .34
5.8.4 Quantity-based and time-based resources.34
5.8.5 Consumable material and equipment .35
5.8.6 Quantity base resource usage .35
5.8.7 Work centre and organizational level .37
5.8.8 Staff time and discipline .38
5.8.9 Consumption profile .39
5.8.10 Material resource availability checking and ordering .40
5.8.11 Material resource delivery .41
5.9 Participants in an activity .42
5.9.1 Subject of work .42
© ISO 2018 – All rights reserved iii

---------------------- Page: 3 ----------------------
ISO 15926-13:2018(E)

5.9.2 Subject of work and physical breakdown.44
5.9.3 Role of a person or organization .45
5.9.4 Planning software .46
5.10 Shutdown .46
5.10.1 Shutdown phase .46
5.10.2 Necessary shutdown for an activity .46
5.10.3 Shutdown scope .47
5.10.4 Shutdown reason .47
5.11 Dates and times for an activity .48
5.11.1 Beginning and end events for an activity .48
5.11.2 Required beginnings and ends .49
5.11.3 Required as early or as late as possible .50
5.11.4 Proposed beginnings and ends.51
5.11.5 Actual beginnings and ends .52
5.12 Duration of an activity .52
5.13 Measure of progress .54
5.13.1 Frontline date .54
5.13.2 Performance measurement .55
5.14 Event and milestone .56
5.15 Temporal relationships between activities and events .58
5.15.1 Succession relationship .58
5.15.2 Specified lag for a succession relationship .59
5.15.3 Specified lag with calendar for a succession relationship .61
5.15.4 Free float and total float for an activity in plan .62
5.15.5 Dependency relationship.63
5.16 Calendar .63
5.16.1 Working days .63
5.16.2 A repeating period in time.64
5.16.3 A repeating point in time .66
5.17 Identification of objects .66
5.18 Work order .67
5.19 Area of facility and site .67
6 Scheduling application view .67
6.1 Use of the scheduling application view model .67
6.2 Simplification of the ISO 15926 ontology .68
6.3 An actual activity in the scheduling application view model .69
6.4 Data planning for the scheduling application view .71
6.5 User defined properties in the scheduling application view .79
Annex A (normative) Ontology for integrated asset planning life-cycle .81
Annex B (normative) XML schema for exchange between scheduling applications .85
Annex C (informative) Relationship between the planning ontology and the scheduling
application interface .86
Annex D (informative) Schedule and activity level .88
Annex E (informative) Interface to reference data libraries .90
Annex F (informative) Usage scenarios .93
Annex G (informative) Relationship with UN/CEFACT XML schema for reporting project
schedule and cost performance .95
Bibliography .96
iv © ISO 2018 – All rights reserved

---------------------- Page: 4 ----------------------
ISO 15926-13:2018(E)

Foreword
ISO (the International Organization for Standardization) is a worldwide federation of national standards
bodies (ISO member bodies). The work of preparing International Standards is normally carried out
through ISO technical committees. Each member body interested in a subject for which a technical
committee has been established has the right to be represented on that committee. International
organizations, governmental and non-governmental, in liaison with ISO, also take part in the work.
ISO collaborates closely with the International Electrotechnical Commission (IEC) on all matters of
electrotechnical standardization.
The procedures used to develop this document and those intended for its further maintenance are
described in the ISO/IEC Directives, Part 1. In particular, the different approval criteria needed for the
different types of ISO documents should be noted. This document was drafted in accordance with the
editorial rules of the ISO/IEC Directives, Part 2 (see www .iso .org/directives).
Attention is drawn to the possibility that some of the elements of this document may be the subject of
patent rights. ISO shall not be held responsible for identifying any or all such patent rights. Details of
any patent rights identified during the development of the document will be in the Introduction and/or
on the ISO list of patent declarations received (see www .iso .org/patents).
Any trade name used in this document is information given for the convenience of users and does not
constitute an endorsement.
For an explanation of the voluntary nature of standards, the meaning of ISO specific terms and
expressions related to conformity assessment, as well as information about ISO's adherence to the
World Trade Organization (WTO) principles in the Technical Barriers to Trade (TBT) see www .iso
.org/iso/foreword .html.
This document was prepared by Technical Committee ISO/TC 184, Automation systems and integration,
Subcommittee SC 4, Industrial data.
A list of all parts in the ISO 15926 series can be found on the ISO website.
Any feedback or questions on this document should be directed to the user’s national standards body. A
complete listing of these bodies can be found at www .iso .org/members .html.
© ISO 2018 – All rights reserved v

---------------------- Page: 5 ----------------------
ISO 15926-13:2018(E)

Introduction
ISO 15926 is an International Standard for the representation of process industries facility life-
cycle information. This representation is specified by a generic, conceptual ontology that is suitable
as the basis for implementation in a shared database or data warehouse. This ontology is defined in
ISO 15926-2, and has an OWL (Web Ontology Language) representation defined in ISO/TS 15926-
12. ISO 15926-2 and ISO/TS 15926-12 are intended to be used as a foundation for domain specific
extensions defined in other parts of ISO 15926.
The ontology is designed to be used in conjunction with reference data, i.e. standard instances that
represent information common to a number of users, production facilities, or both. The support for a
specific life-cycle activity depends on the use of appropriate reference data in conjunction with the
ontology.
This document specifies an extension to the generic, conceptual ontology to support integrated
planning for assets throughout their life-cycle. The ontology enables the integration of planning data
from different sources within a company database.
The ontology is represented in OWL. This document also specifies an XML schema definition (XSD) for a
machine-readable exchange of data used for asset planning.
vi © ISO 2018 – All rights reserved

---------------------- Page: 6 ----------------------
INTERNATIONAL STANDARD ISO 15926-13:2018(E)
Industrial automation systems and integration —
Integration of life-cycle data for process plants including
oil and gas production facilities —
Part 13:
Integrated asset planning life-cycle
1 Scope
This document specifies an ontology for asset planning for process plants, including oil and gas
production facilities. In addition, it specifies an XML schema, derived from the ontology, for exchange of
data used for asset planning.
The following are within the scope of this document:
— portfolio, programme and project plans and schedules;
— operational modification and ongoing maintenance plans and schedules;
— calendars for plan execution;
— constraints on the temporal relationships between items within plans and schedules, including
succession link, lag, free and total float;
— activity breakdown structures;
— locations of activities;
— resources required, including material, equipment and human resources, and their costs;
— interfaces to systems that process work orders and purchase orders;
— responsible organizations and people;
— progress tracking and resource usage;
— reference to standard classes of facility, activity and resource.
EXAMPLE Standard classes are defined in ISO 19008.
The following are outside the scope of this document:
— standard classes of facility, activity and resource;
NOTE ISO 19008 contains such standard classes.
— production planning;
— plan simulation and optimization;
— hazard identification and risk analysis;
— manning and training of personnel;
— budgeting and cost allocation.
© ISO 2018 – All rights reserved 1

---------------------- Page: 7 ----------------------
ISO 15926-13:2018(E)

2 Normative references
The following documents are referred to in the text in such a way that some or all of their content
constitutes requirements of this document. For dated references, only the edition cited applies. For
undated references, the latest edition of the referenced document (including any amendments) applies.
ISO/TS 15926-12:2018, Industrial automation systems and integration — Integration of life-cycle data for
process plants including oil and gas production facilities — Part 12: Life-cycle integration ontology
3 Terms, definitions, symbols and abbreviated terms
3.1 Terms and definitions
For the purposes of this document, the terms and definitions given in ISO/TS 15926-12 and the
following apply.
ISO and IEC maintain terminological databases for use in standardization at the following addresses:
— ISO Online browsing platform: available at https: //www .iso .org/obp
— IEC Electropedia: available at http: //www .electropedia .org/
3.1.1
activity
individual that is something happening or changing
Note 1 to entry: The ISO/IEC/IEEE 15288:2015 definition of “activity” as “set of cohesive tasks of a process”
implies a hierarchy in which processes contain activities, and activities contain tasks. Within this document, all
are activities.
Note 2 to entry: The definition in the PMI Lexicon of Project Management Terms states that “activity” is an
element of work performed during the course of a project. An activity normally has an expected duration, an
expected cost, and expected resource requirements. Activities can be subdivided in tasks.
[SOURCE: ISO/TS 15926-12:2018, 3.1.1, modified — Notes to entry have been added.]
3.1.2
asset planning
planning that is for the construction, commissioning, refurbishment, maintenance, decommissioning,
and disposal of assets, including the running down and starting up of production by assets
3.1.3
baseline schedule
schedule that is used by a planning activity as a reference basis for comparison to monitor and control
progress on the planned activity
Note 1 to entry: The PMI Lexicon of Project Management Terms defines baseline schedule as “the approved
version of a schedule model that can be changed using formal change control procedures and is used as the basis
for comparison to actual results”.
Note 2 to entry: A baseline schedule is a specialization of the ISO/IEC/IEEE 15288:2015 definition of “baseline”
as “formally approved version of a configuration item, regardless of media, formally designated and fixed at a
specific time during the configuration item's life-cycle”.
[SOURCE: ISO 21500:2012, 2.3, modified]
3.1.4
calendar
pattern of working days and shifts that are available for scheduled activities
2 © ISO 2018 – All rights reserved

---------------------- Page: 8 ----------------------
ISO 15926-13:2018(E)

3.1.5
current schedule
schedule of the planned activity that is currently specified as the agreed working schedule by a planning
activity to the performer of the planned activity
Note 1 to entry: ISO 21500:2012 specifies that the role of a current schedule is to avoid adverse schedule impact.
3.1.6
decision gate
activity that approves continuation
Note 1 to entry: Continuation of work beyond a decision gate is contingent on the agreement of the decision-makers.
Note 2 to entry: Criteria for continuation of abandonment are established for each decision gate.
3.1.7
early finish
earliest possible point in time when the uncompleted portions of the activity can finish based on the
schedule
[SOURCE: PMI Lexicon of Project Management Terms]
3.1.8
early start
earliest possible point in time when the uncompleted portions of the activity can start based on the
schedule
[SOURCE: PMI Lexicon of Project Management Terms]
3.1.9
finish to finish
successor relationship in a plan that is from the finish of one activity to the finish of the next
3.1.10
finish to start
successor relationship in a plan that is from the finish of one activity to the start of the next
3.1.11
free float
period of time into which an activity in a plan can overrun without causing a delay to subsequent
activities in the plan
3.1.12
frontline date
date on which the achieved progress on an activity was scheduled
3.1.13
lag
period in time that is specified for a plan succession link
Note 1 to entry: This corresponds to the attributes “lead” and “lag” which are defined in ISO 21500:2012.
3.1.14
late finish
latest point in time that an activity can finish based on the schedule
3.1.15
late start
latest point in time that an activity can start based on the schedule
© ISO 2018 – All rights reserved 3

---------------------- Page: 9 ----------------------
ISO 15926-13:2018(E)

3.1.16
live schedule
schedule that has been revised from the current schedule to mitigate any delays
3.1.17
managed programme of work
activity that contains management and planning for the whole
3.1.18
milestone
event that is significant in a project, programme of work, or portfolio
[SOURCE: PMI Lexicon of Project Management Terms]
3.1.19
ontology
formal statement of an understanding of the world
Note 1 to entry: An ontology can be represented in any language. It need not be represented in a language
specifically designed for ontologies, such as OWL. An ontology can have different representations.
Note 2 to entry: An ontology does not specify what data need to be recorded about the world.
Note 3 to entry: The ontology defined by this document is principally concerned with the world outside a
computer system.
[SOURCE: ISO/TS 15926-12:2018, 3.1.3]
3.1.20
plan
specification of how an activity will be done
Note 1 to
...

Questions, Comments and Discussion

Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.