Detail of GB/T 18975.13-2023

Introduction of GB/T 18975.13-2023

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; - modification and maintenance of 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. 2 Normative references The following referenced documents are indispensable for the application 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 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 represented in Web Ontology Language (OWL) Note: GB / Z18975.12-2023 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 represented in Web Ontology Language(OWL) (ISO / TS15926-12 : 2018, IDT) 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. 3.1.1 activity individual that is something happening or changing Note 1 : The GB/T 22032-2021 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 : 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: GB/Z 18975.12-2023, 3.1.1, modified - Notes have been added] 3.1.2 asset planning planning that is for the construction, commissioning, refurbishment, maintenance, decommissioning, and disposal of assets, including running down and starting up 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 : 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 : A baseline schedule is a specialization of the GB/T 22032-2021 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: GB/T 37507-2019, 2.3, modified] 3.1.4 calendar pattern of working days and shifts that are available for scheduled activities 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: GB/T 37507-2019 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: Continuation of work beyond a decision gate is contingent on the agreement of the decision-makers. Note 2 : 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: This corresponds to the attributes "lead"and"lag"which are defined in GB/T 37507 -2019. 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 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 : 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 : An ontology does not specify what data need to be recorded about the world. Note 3 : The ontology defined by this document is principally concerned with the world outside a computer system. [Source: GB/Z 18975.12-2023, 3.1.3]

Contents of GB/T 18975.13-2023