{"id":244234,"date":"2024-10-19T16:02:31","date_gmt":"2024-10-19T16:02:31","guid":{"rendered":"https:\/\/pdfstandards.shop\/product\/uncategorized\/bs-en-62264-52012\/"},"modified":"2024-10-25T11:01:26","modified_gmt":"2024-10-25T11:01:26","slug":"bs-en-62264-52012","status":"publish","type":"product","link":"https:\/\/pdfstandards.shop\/product\/publishers\/bsi\/bs-en-62264-52012\/","title":{"rendered":"BS EN 62264-5:2012"},"content":{"rendered":"
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.<\/p>\n
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.<\/p>\n
PDF Pages<\/th>\n | PDF Title<\/th>\n<\/tr>\n | ||||||
---|---|---|---|---|---|---|---|
6<\/td>\n | English \n CONTENTS <\/td>\n<\/tr>\n | ||||||
11<\/td>\n | INTRODUCTION <\/td>\n<\/tr>\n | ||||||
12<\/td>\n | 1 Scope 2 Normative references 3 Terms, definitions and abbreviations 3.1 Terms and definitions <\/td>\n<\/tr>\n | ||||||
13<\/td>\n | 3.2 Abbreviations 4 Transaction messages and verbs 4.1 General <\/td>\n<\/tr>\n | ||||||
14<\/td>\n | 4.2 Transaction models <\/td>\n<\/tr>\n | ||||||
15<\/td>\n | 4.3 Message structure Figures \n Figure 1 \u2013 Typical exchanged messages in a transaction Figure 2 \u2013 Typical exchanged data set <\/td>\n<\/tr>\n | ||||||
16<\/td>\n | Figure\u00a03 \u2013 Typical layout of an application identification area <\/td>\n<\/tr>\n | ||||||
17<\/td>\n | Figure 4 \u2013 GET with wildcard and SHOW response <\/td>\n<\/tr>\n | ||||||
18<\/td>\n | 5 Message verbs 5.1 Verbs and transaction models <\/td>\n<\/tr>\n | ||||||
19<\/td>\n | Tables \n Table 1 \u2013 Defined verbs <\/td>\n<\/tr>\n | ||||||
20<\/td>\n | 5.2 GET verb <\/td>\n<\/tr>\n | ||||||
21<\/td>\n | 5.3 SHOW verb Figure 5 \u2013 GET and SHOW transaction <\/td>\n<\/tr>\n | ||||||
22<\/td>\n | 5.4 PROCESS verb 5.5 ACKNOWLEDGE verb Figure 6 \u2013 GET and SHOW transaction with a CONFIRM always Table 2 \u2013 Acknowledge request options <\/td>\n<\/tr>\n | ||||||
23<\/td>\n | Figure 7 \u2013 PROCESS\/ACKNOWLEDGE transaction Figure 8 \u2013 Example of ACKNOWLEDGE to a process message Table 3 \u2013 Acknowledge element <\/td>\n<\/tr>\n | ||||||
24<\/td>\n | 5.6 CHANGE verb 5.7 CANCEL verb Figure\u00a09 \u2013 CHANGE\/RESPOND transaction Figure 10 \u2013 CANCEL message Table 4 \u2013 Respond options <\/td>\n<\/tr>\n | ||||||
25<\/td>\n | 5.8 CONFIRM verb Figure 11 \u2013 Example of a GET message with Confirm OnError Table 5 \u2013 Confirmation request options <\/td>\n<\/tr>\n | ||||||
27<\/td>\n | 5.11 SYNC ADD verb 5.12 SYNC CHANGE verb 5.13 SYNC DELETE verb Figure 13 \u2013 SYNC ADD transaction with confirmation <\/td>\n<\/tr>\n | ||||||
28<\/td>\n | 6 Message nouns 6.1 General 6.2 Defined message contents Figure 14 \u2013 SYNC DELETE transaction with no confirmation <\/td>\n<\/tr>\n | ||||||
32<\/td>\n | 6.3 Personnel model Figure 15 \u2013 Object grouping for the personnel model <\/td>\n<\/tr>\n | ||||||
33<\/td>\n | Table 7 \u2013 Personnel class verb actions <\/td>\n<\/tr>\n | ||||||
36<\/td>\n | Table 8 \u2013 Person verb actions <\/td>\n<\/tr>\n | ||||||
39<\/td>\n | Table 9 \u2013 Qualification test specification verb actions <\/td>\n<\/tr>\n | ||||||
40<\/td>\n | 6.4 Equipment model Figure 16 \u2013 Object grouping for the equipment model <\/td>\n<\/tr>\n | ||||||
41<\/td>\n | Table 10 \u2013 Equipment class verb actions <\/td>\n<\/tr>\n | ||||||
44<\/td>\n | Table 11 \u2013 Equipment verb actions <\/td>\n<\/tr>\n | ||||||
47<\/td>\n | Table 12 \u2013 Equipment capability test specification verb actions <\/td>\n<\/tr>\n | ||||||
48<\/td>\n | 6.5 Maintenance model Figure 17 \u2013 Object grouping for the maintenance model <\/td>\n<\/tr>\n | ||||||
49<\/td>\n | Table 13 \u2013 Maintenance request verb actions <\/td>\n<\/tr>\n | ||||||
50<\/td>\n | Table 14 \u2013 Maintenance response verb actions <\/td>\n<\/tr>\n | ||||||
51<\/td>\n | Table 15 \u2013 Maintenance work order verb actions <\/td>\n<\/tr>\n | ||||||
52<\/td>\n | 6.6 Material model Figure 18 \u2013 Object grouping for the material model <\/td>\n<\/tr>\n | ||||||
53<\/td>\n | Table 16 \u2013 Material Class verb actions <\/td>\n<\/tr>\n | ||||||
56<\/td>\n | Table 17 \u2013 Material definition verb actions <\/td>\n<\/tr>\n | ||||||
59<\/td>\n | Table 18 \u2013 Material lot verb actions <\/td>\n<\/tr>\n | ||||||
62<\/td>\n | Table 19 \u2013 Material sublot verb actions <\/td>\n<\/tr>\n | ||||||
65<\/td>\n | Table 20 \u2013 QA test verb actions <\/td>\n<\/tr>\n | ||||||
66<\/td>\n | 6.7 Process segment model Figure 19 \u2013 Object grouping for the process segment model <\/td>\n<\/tr>\n | ||||||
67<\/td>\n | Table 21 \u2013 Process segment verb actions <\/td>\n<\/tr>\n | ||||||
68<\/td>\n | 6.8 Production capability model Figure 20 \u2013 Object grouping for the production capability model <\/td>\n<\/tr>\n | ||||||
69<\/td>\n | Table 22 \u2013 Production Capability verb actions <\/td>\n<\/tr>\n | ||||||
71<\/td>\n | Table 23 \u2013 Production capability element definitions for GET and no ID messages <\/td>\n<\/tr>\n | ||||||
72<\/td>\n | 6.9 Product definition model Figure 21 \u2013 Object grouping for the product defintion model <\/td>\n<\/tr>\n | ||||||
73<\/td>\n | 6.10 Production schedule model Table 24 \u2013 Product definition verb actions <\/td>\n<\/tr>\n | ||||||
74<\/td>\n | Figure 22 \u2013 Object grouping for the production schedule model <\/td>\n<\/tr>\n | ||||||
75<\/td>\n | Table 25 \u2013 Production schedule verb actions <\/td>\n<\/tr>\n | ||||||
77<\/td>\n | 6.11 Production performance model Figure 23 \u2013 Object grouping for the production performance model Table 26 \u2013 Production Schedule element definitions for GET and no ID messages <\/td>\n<\/tr>\n | ||||||
78<\/td>\n | Table 27 \u2013 Production Performance verb actions <\/td>\n<\/tr>\n | ||||||
80<\/td>\n | 6.12 Transaction Profile Figure 24 \u2013 Transaction profile model Table 28 \u2013 Production Performance definitions for GET and no ID messages <\/td>\n<\/tr>\n | ||||||
81<\/td>\n | Table 29 \u2013 Supported action attributes <\/td>\n<\/tr>\n | ||||||
82<\/td>\n | 7 Completeness, compliance and conformance 7.1 Completeness 7.2 Compliance 7.3 Conformance Table 30 \u2013 Transaction Profile verb actions <\/td>\n<\/tr>\n | ||||||
83<\/td>\n | Table 31 \u2013 Supported verb-noun actions <\/td>\n<\/tr>\n | ||||||
84<\/td>\n | Table 32 \u2013 Vendor conformance example <\/td>\n<\/tr>\n | ||||||
85<\/td>\n | Annex A (informative) \nTransaction models and business scenario examples Figure A.1 \u2013 Coordination of planning and operations processes <\/td>\n<\/tr>\n | ||||||
86<\/td>\n | Figure A.2 \u2013 Push model\u00a0\u2013\u00a0Production schedule and production performance <\/td>\n<\/tr>\n | ||||||
87<\/td>\n | Figure A.3 \u2013 Pull model\u00a0\u2013 Production schedule and production performance Figure A.4 \u2013 Publish model\u00a0\u2013\u00a0Production schedule and production performance <\/td>\n<\/tr>\n | ||||||
88<\/td>\n | Figure A.5 \u2013 Push model\u00a0\u2013\u00a0Production schedule changes Figure A.6 \u2013 Publish model\u00a0\u2013\u00a0Production schedule changes <\/td>\n<\/tr>\n | ||||||
89<\/td>\n | Figure A.7 \u2013 Push model\u00a0\u2013\u00a0Production schedule cancelled Figure A.8 \u2013 Push and pull model\u00a0\u2013\u00a0Schedule cancelled <\/td>\n<\/tr>\n | ||||||
90<\/td>\n | Figure A.9 \u2013 Push model\u00a0\u2013\u00a0Daily production performance Figure A.10 \u2013 Pull model\u00a0\u2013\u00a0Daily production performance <\/td>\n<\/tr>\n | ||||||
91<\/td>\n | Figure A.11 \u2013 Publish model\u00a0\u2013\u00a0Daily production schedule Figure A.12 \u2013 Pull and push model\u00a0\u2013\u00a0Production capability and production schedule <\/td>\n<\/tr>\n | ||||||
92<\/td>\n | Figure A.13 \u2013 Publish and push model\u00a0\u2013\u00a0Production capability and production schedule <\/td>\n<\/tr>\n | ||||||
93<\/td>\n | Figure A.14 \u2013 Push and pull model\u00a0\u2013\u00a0Schedule changes Figure A.15 \u2013 Publish model\u00a0\u2013\u00a0Schedule changes after capability changes <\/td>\n<\/tr>\n | ||||||
94<\/td>\n | Figure A.16 \u2013 Push model\u00a0\u2013\u00a0Material lot added, material lot quantity changed Figure A.17 \u2013 Publish and push model\u00a0\u2013\u00a0Material quantity changes <\/td>\n<\/tr>\n | ||||||
95<\/td>\n | Figure A.18 \u2013 Push and pull model\u00a0\u2013\u00a0Material quantity changes <\/td>\n<\/tr>\n | ||||||
96<\/td>\n | Annex B (informative) \nQuestions on the use of transactions <\/td>\n<\/tr>\n | ||||||
99<\/td>\n | Annex C (informative) \nPatterns for Verbs Table C.1 \u2013 GET message with object ID is specified <\/td>\n<\/tr>\n | ||||||
100<\/td>\n | Table C.2 \u2013 GET message with wildcard in object ID Table C.3 \u2013 GET message with no object ID specified Table C.4 \u2013 PROCESS message with Object ID specified <\/td>\n<\/tr>\n | ||||||
101<\/td>\n | Table C.5 \u2013 PROCESS message with no object ID Table C.6 \u2013 CHANGE message with object ID Table C.7 \u2013 CHANGE message with wildcard object ID <\/td>\n<\/tr>\n | ||||||
102<\/td>\n | Table C.8 \u2013 CANCEL message with object ID Table C.9 \u2013 CANCEL message with wildcard in object ID Table C.10 \u2013 SYNC message with object ID <\/td>\n<\/tr>\n | ||||||
103<\/td>\n | Table C.11 \u2013 SYNC message with wildcard in object ID <\/td>\n<\/tr>\n | ||||||
104<\/td>\n | Annex D (informative) \nGeneral rules for identifying nouns from object models <\/td>\n<\/tr>\n | ||||||
105<\/td>\n | Figure D.1 \u2013 Object model with composite relationships <\/td>\n<\/tr>\n | ||||||
106<\/td>\n | Figure D.2 \u2013 Object model with non composite relationships Figure D.3 \u2013 Example of multiple composite objects <\/td>\n<\/tr>\n | ||||||
107<\/td>\n | Bibliography <\/td>\n<\/tr>\n<\/table>\n","protected":false},"excerpt":{"rendered":" Enterprise system integration – Business to manufacturing transactions<\/b><\/p>\n |