prEN IEC 62264-2:2024
(Main)Enterprise-control system integration - Part 2: Object and attributes for enterprise-control system integration
Enterprise-control system integration - Part 2: Object and attributes for enterprise-control system integration
Intégration des systèmes entreprise-contrôle - Partie 2: Objets et attributs pour l'intégration des systèmes de commande d'entreprise
Integracija sistemov za upravljanje podjetij - 2. del: Objektni modeli in lastnosti za integracijo sistemov za upravljanje podjeti
General Information
Relations
Standards Content (Sample)
SLOVENSKI STANDARD
01-marec-2025
Integracija sistemov za upravljanje podjetij - 2. del: Objektni modeli in lastnosti za
integracijo sistemov za upravljanje podjeti
Enterprise-control system integration - Part 2: Object and attributes for enterprise-control
system integration
Intégration des systèmes entreprise-contrôle - Partie 2: Objets et attributs pour
l'intégration des systèmes de commande d'entreprise
Ta slovenski standard je istoveten z: prEN IEC 62264-2:2024
ICS:
25.040.40 Merjenje in krmiljenje Industrial process
industrijskih postopkov measurement and control
35.240.50 Uporabniške rešitve IT v IT applications in industry
industriji
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.
65E/1147/CDV
COMMITTEE DRAFT FOR VOTE (CDV)
PROJECT NUMBER:
IEC 62264-2 ED3
DATE OF CIRCULATION: CLOSING DATE FOR VOTING:
2024-12-27 2025-03-21
SUPERSEDES DOCUMENTS:
65E/960/CD, 65E/1068/CC
IEC SC 65E : DEVICES AND INTEGRATION IN ENTERPRISE SYSTEMS
SECRETARIAT: SECRETARY:
United States of America Mr David Richmond
OF INTEREST TO THE FOLLOWING COMMITTEES: HORIZONTAL FUNCTION(S):
ASPECTS CONCERNED:
SUBMITTED FOR CENELEC PARALLEL VOTING NOT SUBMITTED FOR CENELEC PARALLEL VOTING
Attention IEC-CENELEC parallel voting
The attention of IEC National Committees, members of CENELEC,
is drawn to the fact that this Committee Draft for Vote (CDV) is
submitted for parallel voting.
The CENELEC members are invited to vote through the CENELEC
online voting system.
This document is still under study and subject to change. It should not be used for reference purposes.
Recipients of this document are invited to submit, with their comments, notification of any relevant patent rights of which they are aware
and to provide supporting documentation.
Recipients of this document are invited to submit, with their comments, notification of any relevant “In Some Countries” clau ses to be
included should this proposal proceed. Recipients are reminded that the CDV stage is the final stage for submitting ISC c lauses. (SEE
AC/22/2007 OR NEW GUIDANCE DOC).
TITLE:
Enterprise-control system integration - Part 2: Object and attributes for enterprise-control system integration
PROPOSED STABILITY DATE: 2029
NOTE FROM TC/SC OFFICERS:
file, to make a copy and to print out the content for the sole purpose of preparing National Committee positions. You may not copy or
"mirror" the file or printed version of the document, or any part of it, for any other purpose without permission in writing from IEC.
65E/1147/CDV – 2 – IEC CDV 62264-2 © IEC 2024
1 Contents
3 1 Scope . 18
4 2 Normative references . 18
5 3 Terms, definitions, abbreviations, and conventions . 20
6 3.1 Terms and definitions . 20
7 3.2 Abbreviations . 20
8 3.3 Conventions . 21
9 4 Manufacturing operations management information models . 52
10 4.1 Scope of information models . 52
11 4.2 Relationships of common information models to operations management
12 information models . 53
13 4.3 Cross-model relationships between conceptual operations management
14 information models and their objects . 53
15 4.4 Cross-model relationships for MOM activity context in information exchanges . 59
16 4.5 Attributes of an object in an information model . 61
17 5 Common object models . 76
18 5.1 Hierarchy scope information . 76
19 5.2 Spatial definition information . 78
20 5.3 Operational location information . 81
21 5.4 Personnel information . 88
22 5.5 Role-based equipment information . 96
23 5.6 Physical asset information . 105
24 5.7 Material information . 116
25 5.8 Process segment information . 141
26 5.9 Operations test information . 175
27 5.10 Operations record information . 191
28 5.11 Operations event information . 202
29 5.12 Containers, tools, and software . 229
30 6 Operations management information . 230
31 6.1 Operations definition information . 230
32 6.2 Operations schedule information . 271
33 6.3 Operations performance information . 311
34 6.4 Operations capability information . 345
35 6.5 Process segment capability information . 376
36 6.6 Operations segment capability information . 382
37 7 Cross-reference between IEC 62264-1 data flow models and the corresponding IEC
38 62264-2 object model . 388
39 8 List of objects . 390
40 9 Compliance . 393
41 Annex A (Informative) Value syntax in the value attribute . 395
42 Annex B (Informative) Implementation options for specifying values in unit of
43 measurement attribute . 396
IEC CDV 62264-2 © IEC 2024 – 3 – 65E/1147/CDV
44 B.1 Specifying value(s) for the “value unit of measurement” attribute in operations -
45 related class and definition property objects (IEC 62264-2) and work-related
46 definition and type property objects (IEC 62264-4) . 396
47 B.2 Specifying value(s) for the “unit of measurement” attribute where no object
48 specifies permissible values. . 397
49 Annex C (Informative) Use cases and examples . 401
50 C.1 Use case and examples . 401
51 C.2 Application of the standard . 407
52 C.3 Database mapping of the models . 407
53 C.4 XML usage . 408
54 Annex D (Informative) Example data sets . 412
55 D.1 General . 412
56 D.2 Material model example . 412
57 D.3 Equipment model and hierarchy scope examples . 414
58 D.4 Personnel model example . 418
59 D.5 Operations capability example . 419
60 D.6 Operations performance example . 420
61 D.7 Operations test model use case examples . 420
62 D.8 Example of planning and response state attributes and defined values . 427
63 D.9 Operations event definition record specification example . 430
64 D.10 Resource acquired example . 430
65 D.11 Work commenced/redirected/completed/aborted example . 433
66 Annex E (Informative) Questions and answers about object use . 436
67 E.1 General . 436
68 E.2 Inflow materials . 436
69 E.3 Multiple products per process segment . 436
70 E.4 Process segments vs. operations segments . 437
71 E.5 Segment parameter references . 438
72 E.6 Use of hierarchy scope in parameter objects . 439
73 E.7 Use of spatial definition in personnel objects . 439
74 E.8 How class name and property IDs are used to identify elements . 440
75 E.9 Possible capability overcounts . 441
76 E.10 Routing and process capability . 443
77 E.11 Product and process capability dependencies . 444
78 E.12 Representation of dependencies . 445
79 E.13 How a material transfer is handled . 446
80 E.14 How to extend the standard when properties cannot be used . 447
81 E.15 Modeling of tools . 447
82 E.16 What is equipment and what is a physical asset? . 447
83 E.17 How should dependencies in the operations schedule and operations response
84 be handled? . 448
85 E.18 How are “mixed” operations types used? . 448
86 E.19 What is the relationship between this standard and MESA International’s
87 B2MML? . 449
65E/1147/CDV – 4 – IEC CDV 62264-2 © IEC 2024
88 Annex F (informative) Implementation considerations for inheritance and persistence of
89 data exchange object models. . 452
90 F.1 Object inheritance considerations . 452
91 F.2 Record inheritance . 454
92 F.3 Object persistence considerations . 455
93 Annex G (informative) Logical information flows . 458
94 Annex H (Informative) Conceptual model to implementation model transformations . 460
95 Annex I (informative) Conceptual model to implementation data model examples . 465
96 I.1 Conceptual object model example: personnel model . 465
97 I.2 MESA – B2MML 7.0 (XSD) implementation model . 467
98 I.3 Simplified XSD implementation model . 468
99 I.4 Object Management Group (OMG) – Interface Definition Language (IDL) –
100 Common Data Representation (CDR) implementation model . 468
101 I.5 OPC Unified Architecture (UA) implementation model . 469
102 I.6 Flat buffers – Interactive Data Language (IDL) implementation model . 471
103 I.7 Internet Engineering Task Force (IETF) – JavaScript Object Notation (JSON) –
104 Schema implementation model . 471
105 I.8 Open Source Robo
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.