BS EN 62264-5:2012
$215.11
Enterprise system integration – Business to manufacturing transactions
Published By | Publication Date | Number of Pages |
BSI | 2012 | 110 |
This part of IEC 62264 defines transactions in terms of information exchanges between applications performing business and manufacturing activities associated with Levels 3 and 4. The exchanges are intended to enable information collection, retrieval, transfer and storage in support of Enterprise-Control system integration. This part of IEC 62264 is consistent with the IEC 62264-1 models and terminology and IEC 62264-2 object model attributes. This standard also defines transactions that specify how to exchange the objects defined in IEC 62264-1, Clause 7, IEC 62264-2 and this standard. Other uses of the transaction model are not defined in this part.
The models covered in this standard are: Personnel Model, Equipment Model, Maintenance Model, Material Model, Process Segment Model, Production Capability Model, Product Definition Model, Production Schedule Model, and Production Performance Model.
PDF Catalog
PDF Pages | PDF Title |
---|---|
6 | English CONTENTS |
11 | INTRODUCTION |
12 | 1 Scope 2 Normative references 3 Terms, definitions and abbreviations 3.1 Terms and definitions |
13 | 3.2 Abbreviations 4 Transaction messages and verbs 4.1 General |
14 | 4.2 Transaction models |
15 | 4.3 Message structure Figures Figure 1 – Typical exchanged messages in a transaction Figure 2 – Typical exchanged data set |
16 | Figure 3 – Typical layout of an application identification area |
17 | Figure 4 – GET with wildcard and SHOW response |
18 | 5 Message verbs 5.1 Verbs and transaction models |
19 | Tables Table 1 – Defined verbs |
20 | 5.2 GET verb |
21 | 5.3 SHOW verb Figure 5 – GET and SHOW transaction |
22 | 5.4 PROCESS verb 5.5 ACKNOWLEDGE verb Figure 6 – GET and SHOW transaction with a CONFIRM always Table 2 – Acknowledge request options |
23 | Figure 7 – PROCESS/ACKNOWLEDGE transaction Figure 8 – Example of ACKNOWLEDGE to a process message Table 3 – Acknowledge element |
24 | 5.6 CHANGE verb 5.7 CANCEL verb Figure 9 – CHANGE/RESPOND transaction Figure 10 – CANCEL message Table 4 – Respond options |
25 | 5.8 CONFIRM verb Figure 11 – Example of a GET message with Confirm OnError Table 5 – Confirmation request options |
27 | 5.11 SYNC ADD verb 5.12 SYNC CHANGE verb 5.13 SYNC DELETE verb Figure 13 – SYNC ADD transaction with confirmation |
28 | 6 Message nouns 6.1 General 6.2 Defined message contents Figure 14 – SYNC DELETE transaction with no confirmation |
32 | 6.3 Personnel model Figure 15 – Object grouping for the personnel model |
33 | Table 7 – Personnel class verb actions |
36 | Table 8 – Person verb actions |
39 | Table 9 – Qualification test specification verb actions |
40 | 6.4 Equipment model Figure 16 – Object grouping for the equipment model |
41 | Table 10 – Equipment class verb actions |
44 | Table 11 – Equipment verb actions |
47 | Table 12 – Equipment capability test specification verb actions |
48 | 6.5 Maintenance model Figure 17 – Object grouping for the maintenance model |
49 | Table 13 – Maintenance request verb actions |
50 | Table 14 – Maintenance response verb actions |
51 | Table 15 – Maintenance work order verb actions |
52 | 6.6 Material model Figure 18 – Object grouping for the material model |
53 | Table 16 – Material Class verb actions |
56 | Table 17 – Material definition verb actions |
59 | Table 18 – Material lot verb actions |
62 | Table 19 – Material sublot verb actions |
65 | Table 20 – QA test verb actions |
66 | 6.7 Process segment model Figure 19 – Object grouping for the process segment model |
67 | Table 21 – Process segment verb actions |
68 | 6.8 Production capability model Figure 20 – Object grouping for the production capability model |
69 | Table 22 – Production Capability verb actions |
71 | Table 23 – Production capability element definitions for GET and no ID messages |
72 | 6.9 Product definition model Figure 21 – Object grouping for the product defintion model |
73 | 6.10 Production schedule model Table 24 – Product definition verb actions |
74 | Figure 22 – Object grouping for the production schedule model |
75 | Table 25 – Production schedule verb actions |
77 | 6.11 Production performance model Figure 23 – Object grouping for the production performance model Table 26 – Production Schedule element definitions for GET and no ID messages |
78 | Table 27 – Production Performance verb actions |
80 | 6.12 Transaction Profile Figure 24 – Transaction profile model Table 28 – Production Performance definitions for GET and no ID messages |
81 | Table 29 – Supported action attributes |
82 | 7 Completeness, compliance and conformance 7.1 Completeness 7.2 Compliance 7.3 Conformance Table 30 – Transaction Profile verb actions |
83 | Table 31 – Supported verb-noun actions |
84 | Table 32 – Vendor conformance example |
85 | Annex A (informative) Transaction models and business scenario examples Figure A.1 – Coordination of planning and operations processes |
86 | Figure A.2 – Push model – Production schedule and production performance |
87 | Figure A.3 – Pull model – Production schedule and production performance Figure A.4 – Publish model – Production schedule and production performance |
88 | Figure A.5 – Push model – Production schedule changes Figure A.6 – Publish model – Production schedule changes |
89 | Figure A.7 – Push model – Production schedule cancelled Figure A.8 – Push and pull model – Schedule cancelled |
90 | Figure A.9 – Push model – Daily production performance Figure A.10 – Pull model – Daily production performance |
91 | Figure A.11 – Publish model – Daily production schedule Figure A.12 – Pull and push model – Production capability and production schedule |
92 | Figure A.13 – Publish and push model – Production capability and production schedule |
93 | Figure A.14 – Push and pull model – Schedule changes Figure A.15 – Publish model – Schedule changes after capability changes |
94 | Figure A.16 – Push model – Material lot added, material lot quantity changed Figure A.17 – Publish and push model – Material quantity changes |
95 | Figure A.18 – Push and pull model – Material quantity changes |
96 | Annex B (informative) Questions on the use of transactions |
99 | Annex C (informative) Patterns for Verbs Table C.1 – GET message with object ID is specified |
100 | Table C.2 – GET message with wildcard in object ID Table C.3 – GET message with no object ID specified Table C.4 – PROCESS message with Object ID specified |
101 | Table C.5 – PROCESS message with no object ID Table C.6 – CHANGE message with object ID Table C.7 – CHANGE message with wildcard object ID |
102 | Table C.8 – CANCEL message with object ID Table C.9 – CANCEL message with wildcard in object ID Table C.10 – SYNC message with object ID |
103 | Table C.11 – SYNC message with wildcard in object ID |
104 | Annex D (informative) General rules for identifying nouns from object models |
105 | Figure D.1 – Object model with composite relationships |
106 | Figure D.2 – Object model with non composite relationships Figure D.3 – Example of multiple composite objects |
107 | Bibliography |