EN 62264-5:2012

SLOVENSKI STANDARD
01-maj-2012
Integracija sistemov za upravljanje podjetij - 5. del: Prenosi posla v proizvodnjo
(IEC 62264-5:2011)
Enterprise system integration - Part 5: Business to manufacturing transactions (IEC
62264-5:2011)
Integration von Unternehmensführungs- und Leitsystemen - Teil 5: Transaktionen
zwischen Geschäftsabläufen und Produktionssteuerung (IEC 62264-5:2011)
Intégration du système de commande d'entreprise - Partie 5: Transactions entre
systèmes de gestion de commande d'entreprise et systèmes de fabrication (CEI 62264-
5:2011)
Ta slovenski standard je istoveten z: EN 62264-5:2012
ICS:
25.040.01 Sistemi za avtomatizacijo v Industrial automation
industriji na splošno systems in general
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.

EUROPEAN STANDARD
EN 62264-5
NORME EUROPÉENNE
March 2012
EUROPÄISCHE NORM
ICS 25.040.99; 35.100; 35.200
English version
Enterprise system integration -
Part 5: Business to manufacturing transactions
(IEC 62264-5:2011)
Intégration du système de commande Integration von Unternehmensführungs-
d'entreprise - und Leitsystemen -
Partie 5: Transactions entre systèmes de Teil 5: Transaktionen zwischen
gestion de commande d'entreprise et Geschäftsabläufen und
systèmes de fabrication Produktionssteuerung
(CEI 62264-5:2011) (IEC 62264-5:2011)

This European Standard was approved by CENELEC on 2012-02-03. CENELEC members are bound to comply
with the CEN/CENELEC Internal Regulations which stipulate the conditions for giving this European Standard
the status of a national standard without any alteration.

Up-to-date lists and bibliographical references concerning such national standards may be obtained on
application to the CEN-CENELEC Management Centre or to any CENELEC member.

This European Standard exists in three official versions (English, French, German). A version in any other
language made by translation under the responsibility of a CENELEC member into its own language and notified
to the CEN-CENELEC Management Centre has the same status as the official versions.

CENELEC members are the national electrotechnical committees of Austria, Belgium, Bulgaria, Croatia, Cyprus,
the Czech Republic, Denmark, Estonia, Finland, France, Germany, Greece, Hungary, Iceland, Ireland, Italy,
Latvia, Lithuania, Luxembourg, Malta, the Netherlands, Norway, Poland, Portugal, Romania, Slovakia, Slovenia,
Spain, Sweden, Switzerland, Turkey and the United Kingdom.

CENELEC
European Committee for Electrotechnical Standardization
Comité Européen de Normalisation Electrotechnique
Europäisches Komitee für Elektrotechnische Normung

Management Centre: Avenue Marnix 17, B - 1000 Brussels

© 2012 CENELEC - All rights of exploitation in any form and by any means reserved worldwide for CENELEC members.
Ref. No. EN 62264-5:2012 E
The text of document 65E/100/CDV, future edition 1 of IEC 62264-5, prepared by SC 65E, "Devices and
integration in enterprise systems", of IEC TC 65, "Industrial-process measurement, control and
automation" was submitted to the IEC-CENELEC parallel vote and approved by CENELEC as
The following dates are fixed:
(dop) 2012-11-03
• latest date by which the document has
to be implemented at national level by
publication of an identical national
standard or by endorsement
(dow) 2015-02-03
• latest date by which the national

standards conflicting with the
document have to be withdrawn
Attention is drawn to the possibility that some of the elements of this document may be the subject of
patent rights. CENELEC [and/or CEN] shall not be held responsible for identifying any or all such patent
rights.
Endorsement notice
The text of the International Standard IEC 62264-5:2011 was approved by CENELEC as a European
Standard without any modification.

- 3 - EN 62264-5:2012
Annex ZA
(normative)
Normative references to international publications
with their corresponding European publications

The following documents, in whole or in part, are normatively referenced in this document and are
indispensable for its application. For dated references, only the edition cited applies. For undated
references, the latest edition of the referenced document (including any amendments) applies

NOTE  When an international publication has been modified by common modifications, indicated by (mod), the relevant EN/HD
applies.
Publication Year Title EN/HD Year

IEC 62264-1 - Enterprise-control system integration - EN 62264-1 -
Part 1: Models and terminology

IEC 62264-2 - Enterprise-control system integration - EN 62264-2 -
Part 2: Object model attributes

IEC 62264-3 - Enterprise-control system integration - EN 62264-3 -
Part 3 Activity models of manufacturing
operations management
IEC 62264-5 ®
Edition 1.0 2011-02
INTERNATIONAL
STANDARD
NORME
INTERNATIONALE
Enterprise-control system integration –
Part 5: Business to manufacturing transactions

Intégration du système de commande d’entreprise –
Partie 5: Transactions entre systèmes de gestion de commande d’entreprise et
systèmes de fabrication
INTERNATIONAL
ELECTROTECHNICAL
COMMISSION
COMMISSION
ELECTROTECHNIQUE
PRICE CODE
INTERNATIONALE
CODE PRIX XE
ICS 25.040.99; 35.100; 35.200 ISBN 978-2-88912-378-0

– 2 – 62264-5  IEC:2011
CONTENTS
FOREWORD . 7
INTRODUCTION . 9
1 Scope . 10
2 Normative references . 10
3 Terms, definitions and abbreviations . 10
3.1 Terms and definitions . 10
3.2 Abbreviations . 11
4 Transaction messages and verbs . 11
4.1 General . 11
4.2 Transaction models . 12
4.3 Message structure . 13
4.3.1 General structure . 13
4.3.2 Application identification area . 14
4.3.3 Data area . 14
4.3.4 Message nouns . 14
4.3.5 Wildcard . 15
5 Message verbs . 16
5.1 Verbs and transaction models . 16
5.2 GET verb . 18
5.3 SHOW verb . 19
5.4 PROCESS verb . 20
5.5 ACKNOWLEDGE verb . 20
5.6 CHANGE verb . 22
5.7 CANCEL verb . 22
5.8 CONFIRM verb . 23
5.9 RESPOND verb . 24
5.10 SYNC verb . 24
5.11 SYNC ADD verb . 25
5.12 SYNC CHANGE verb . 25
5.13 SYNC DELETE verb . 25
6 Message nouns . 26
6.1 General . 26
6.2 Defined message contents . 26
6.2.1 Transaction service profile . 26
6.2.2 Personnel class . 26
6.2.3 Person . 26
6.2.4 Qualification test specification . 26
6.2.5 Equipment class . 27
6.2.6 Equipment . 27
6.2.7 Equipment capability test specification . 27
6.2.8 Maintenance request . 27
6.2.9 Maintenance work order . 27
6.2.10 Maintenance response. 27
6.2.11 Material class . 27
6.2.12 Material definition . 27
6.2.13 Material lot . 27

62264-5  IEC:2011 – 3 –
6.2.14 Material sublot . 28
6.2.15 QA test Specification . 28
6.2.16 Process segment . 28
6.2.17 Production capability . 28
6.2.18 Product definition . 28
6.2.19 Production schedule . 29
6.2.20 Production performance . 29
6.3 Personnel model . 30
6.3.1 Personnel model elements . 30
6.3.2 Personnel class verbs . 30
6.3.3 Personnel class verb actions . 30
6.3.4 Person verbs . 33
6.3.5 Person verb actions . 33
6.3.6 Qualification test specification verbs . 36
6.3.7 Qualification test specification verb actions . 36
6.4 Equipment model . 38
6.4.1 Equipment model elements . 38
6.4.2 Equipment class verbs . 38
6.4.3 Equipment class verb actions . 38
6.4.4 Equipment verbs . 41
6.4.5 Equipment verb actions . 41
6.4.6 Equipment capability test specification verbs . 44
6.4.7 Equipment capability test specification test verb actions . 44
6.5 Maintenance model . 46
6.5.1 Maintenance model elements . 46
6.5.2 Maintenance request verbs . 46
6.5.3 Maintenance request verb actions . 46
6.5.4 Maintenance response verbs . 47
6.5.5 Maintenance response verb actions . 48
6.5.6 Maintenance work order verbs . 48
6.5.7 Maintenance work order verb actions . 49
6.6 Material model. 50
6.6.1 Material model elements . 50
6.6.2 Material class verbs . 50
6.6.3 Material class verb actions . 50
6.6.4 Material definition verbs . 53
6.6.5 Material definition verb actions . 53
6.6.6 Material lot verbs . 56
6.6.7 Material lot verb actions . 56
6.6.8 Material sublot verbs . 59
6.6.9 Material sublot verb actions . 59
6.6.10 QA test specification verbs . 62
6.6.11 QA test specification verb actions . 62
6.7 Process segment model . 64
6.7.1 Process segment model elements . 64
6.7.2 Process segment verbs . 64
6.7.3 Process segment verb actions . 64
6.8 Production capability model . 66
6.8.1 Production capability model elements . 66

– 4 – 62264-5  IEC:2011
6.8.2 Production capability verbs . 66
6.8.3 Production capability verb actions . 66
6.9 Product definition model . 70
6.9.1 Production definition model elements . 70
6.9.2 Product definition verbs . 70
6.9.3 Product definition verb actions . 70
6.10 Production schedule model . 71
6.10.1 Production schedule model element . 71
6.10.2 Production schedule verbs . 72
6.10.3 Production schedule verb actions . 72
6.11 Production performance model . 75
6.11.1 Production performance model elements . 75
6.11.2 Production performance verbs . 76
6.11.3 Production performance verb actions . 76
6.12 Transaction Profile . 78
7 Completeness, compliance and conformance . 80
7.1 Completeness . 80
7.2 Compliance . 80
7.3 Conformance . 80
Annex A (informative) Transaction models and business scenario examples . 83
Annex B (informative) Questions on the use of transactions . 94
Annex C (informative) Patterns for Verbs . 97
Annex D (informative) General rules for identifying nouns from object models . 102
Bibliography . 105

Figure 1 – Typical exchanged messages in a transaction . 13
Figure 2 – Typical exchanged data set . 13
Figure 3 – Typical layout of an application identification area. 14
Figure 4 – GET with wildcard and SHOW response . 15
Figure 5 – GET and SHOW transaction . 19
Figure 6 – GET and SHOW transaction with a CONFIRM always . 20
Figure 7 – PROCESS/ACKNOWLEDGE transaction . 21
Figure 8 – Example of ACKNOWLEDGE to a process message . 21
Figure 9 – CHANGE/RESPOND transaction . 22
Figure 10 – CANCEL message . 22
Figure 11 – Example of a GET message with Confirm OnError . 23
Figure 12 – Confirm Message . 24
Figure 13 – SYNC ADD transaction with confirmation . 25
Figure 14 – SYNC DELETE transaction with no confirmation . 26
Figure 15 – Object grouping for the personnel model . 30
Figure 16 – Object grouping for the equipment model . 38
Figure 17 – Object grouping for the maintenance model . 46
Figure 18 – Object grouping for the material model . 50
Figure 19 – Object grouping for the process segment model . 64
Figure 20 – Object grouping for the production capability model . 66

62264-5  IEC:2011 – 5 –
Figure 21 – Object grouping for the product defintion model . 70
Figure 22 – Object grouping for the production schedule model . 72
Figure 23 – Object grouping for the production performance model. 75
Figure 24 – Transaction profile model . 78
Figure A.1 – Coordination of planning and operations processes . 83
Figure A.2 – Push model – Production schedule and production performance . 84
Figure A.3 – Pull model – Production schedule and production performance . 85
Figure A.4 – Publish model – Production schedule and production performance . 85
Figure A.5 – Push model – Production schedule changes . 86
Figure A.6 – Publish model – Production schedule changes. 86
Figure A.7 – Push model – Production schedule cancelled . 87
Figure A.8 – Push and pull model – Schedule cancelled . 87
Figure A.9 – Push model – Daily production performance . 88
Figure A.10 – Pull model – Daily production performance . 88
Figure A.11 – Publish model – Daily production schedule . 89
Figure A.12 – Pull and push model – Production capability and production schedule . 89
Figure A.13 – Publish and push model – Production capability and production schedule . 90
Figure A.14 – Push and pull model – Schedule changes . 91
Figure A.15 – Publish model – Schedule changes after capability changes . 91
Figure A.16 – Push model – Material lot added, material lot quantity changed . 92
Figure A.17 – Publish and push model – Material quantity changes . 92
Figure A.18 – Push and pull model – Material quantity changes . 93
Figure D.1 – Object model with composite relationships . 103
Figure D.2 – Object model with non composite relationships . 104
Figure D.3 – Example of multiple composite objects . 104

Table 1 – Defined verbs . 17
Table 2 – Acknowledge request options . 20
Table 3 – Acknowledge element . 21
Table 4 – Respond options . 22
Table 5 – Confirmation request options . 23
Table 6 – Respond element . 24
Table 7 – Personnel class verb actions . 31
Table 8 – Person verb actions . 34
Table 9 – Qualification test specification verb actions . 37
Table 10 – Equipment class verb actions . 39
Table 11 – Equipment verb actions . 42
Table 12 – Equipment capability test specification verb actions . 45
Table 13 – Maintenance request verb actions . 47
Table 14 – Maintenance response verb actions. 48
Table 15 – Maintenance work order verb actions . 49
Table 16 – Material Class verb actions . 51
Table 17 – Material definition verb actions . 54

– 6 – 62264-5  IEC:2011
Table 18 – Material lot verb actions . 57
Table 19 – Material sublot verb actions . 60
Table 20 – QA test verb actions . 63
Table 21 – Process segment verb actions . 65
Table 22 – Production Capability verb actions. 67
Table 23 – Production capability element definitions for GET and no ID messages . 69
Table 24 – Product definition verb actions . 71
Table 25 – Production schedule verb actions . 73
Table 26 – Production Schedule element definitions for GET and no ID messages . 75
Table 27 – Production Performance verb actions . 76
Table 28 – Production Performance definitions for GET and no ID messages . 78
Table 29 – Supported action attributes . 79
Table 30 – Transaction Profile verb actions . 80
Table 31 – Supported verb-noun actions . 81
Table 32 – Vendor conformance example . 82
Table C.1 – GET message with object ID is specified . 97
Table C.2 – GET message with wildcard in object ID . 98
Table C.3 – GET message with no object ID specified . 98
Table C.4 – PROCESS message with Object ID specified . 98
Table C.5 – PROCESS message with no object ID . 99
Table C.6 – CHANGE message with object ID . 99
Table C.7 – CHANGE message with wildcard object ID . 99
Table C.8 – CANCEL message with object ID . 100
Table C.9 – CANCEL message with wildcard in object ID . 100
Table C.10 – SYNC message with object ID. 100
Table C.11 – SYNC message with wildcard in object ID . 101

62264-5  IEC:2011 – 7 –
INTERNATIONAL ELECTROTECHNICAL COMMISSION
____________
ENTERPRISE-CONTROL SYSTEM INTEGRATION –

Part 5: Business to manufacturing transactions

FOREWORD
1) The International Electrotechnical Commission (IEC) is a worldwide organization for standardization comprising
all national electrotechnical committees (IEC National Committees). The object of IEC is to promote
international co-operation on all questions concerning standardization in the electrical and electronic fields. To
this end and in addition to other activities, IEC publishes International Standards, Technical Specifications,
Technical Reports, Publicly Available Specifications (PAS) and Guides (hereafter referred to as “IEC
Publication(s)”). Their preparation is entrusted to technical committees; any IEC National Committee interested
in the subject dealt with may participate in this preparatory work. International, governmental and non-
governmental organizations liaising with the IEC also participate in this preparation. IEC collaborates closely
with the International Organization for Standardization (ISO) in accordance with conditions determined by
agreement between the two organizations.
2) The formal decisions or agreements of IEC on technical matters express, as nearly as possible, an international
consensus of opinion on the relevant subjects since each technical committee has representation from all
interested IEC National Committees.
3) IEC Publications have the form of recommendations for international use and are accepted by IEC National
Committees in that sense. While all reasonable efforts are made to ensure that the technical content of IEC
Publications is accurate, IEC cannot be held responsible for the way in which they are used or for any
misinterpretation by any end user.
4) In order to promote international uniformity, IEC National Committees undertake to apply IEC Publications
transparently to the maximum extent possible in their national and regional publications. Any divergence
between any IEC Publication and the corresponding national or regional publication shall be clearly indicated in
the latter.
5) IEC itself does not provide any attestation of conformity. Independent certification bodies provide conformity
assessment services and, in some areas, access to IEC marks of conformity. IEC is not responsible for any
services carried out by independent certification bodies.
6) All users should ensure that they have the latest edition of this publication.
7) No liability shall attach to IEC or its directors, employees, servants or agents including individual experts and
members of its technical committees and IEC National Committees for any personal injury, property damage or
other damage of any nature whatsoever, whether direct or indirect, or for costs (including legal fees) and
expenses arising out of the publication, use of, or reliance upon, this IEC Publication or any other IEC
Publications.
8) Attention is drawn to the Normative references cited in this publication. Use of the referenced publications is
indispensable for the correct application of this publication.
9) Attention is drawn to the possibility that some of the elements of this IEC Publication may be the subject of
patent rights. IEC shall not be held responsible for identifying any or all such patent rights.
International Standard IEC 62264-5 has been prepared by subcommittee 65E: Devices and
integration in enterprise systems, of IEC technical committee 65: Industrial-process
measurement, control and automation.
The text of this standard is based on the following documents:
CDV Report on voting
65E/100/CDV 65E/156/RVC
Full information on the voting for the approval of this standard can be found in the report on
voting indicated in the above table.
This publication has been drafted in accordance with the ISO/IEC Directives, Part 2.

– 8 – 62264-5  IEC:2011
The list of all the parts of the IEC 62264 series, under the general title Enterprise-Control
system integration, can be found on the IEC website.
The committee has decided that the contents of this publication will remain unchanged until
the stability date indicated on the IEC web site under "http://webstore.iec.ch" in the data
related to the specific publication. At this date, the publication will be
• reconfirmed,
• withdrawn,
• replaced by a revised edition, or
• amended.
62264-5  IEC:2011 – 9 –
INTRODUCTION
This part of IEC 62264 is based on the use of IEC 62264 abstract models previously defined
in IEC 62264-1 and IEC 62264-2 combined with verbs to define a transaction model for
information exchange. It is recognized that other non-IEC 62264-5 transaction protocols are
possible and are not deemed invalid as a result of this standard. Transactions occur at all
levels within the enterprise and between enterprise partners, and are related to both required
and actual activities, but the focus of this part of IEC 62264 is the interface between
enterprise/business systems and manufacturing systems.
This standard defines business-to-manufacturing transactions and manufacturing-to-business
transactions that may be used in relation to the objects that are exchanged between Level 4
and Level 3, as defined in the object models of IEC 62264-1 and IEC 62264-2. Models are
introduced which provide descriptions of the transactions and explanations of the required
transaction processing behaviour.
Technology specific implementations to provide this behaviour are not defined in this
standard. This part of IEC 62264 has the intent of providing insight into the level of work
required to construct transactional exchanges.

– 10 – 62264-5  IEC:2011
ENTERPRISE-CONTROL SYSTEM INTEGRATION –

Part 5: Business to manufacturing transactions

1 Scope
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.
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.
IEC 62264-1, Enterprise-control system integration – Part 1: Models and terminology
IEC 62264-2, Enterprise-control system integration – Part 2: Object model attributes
IEC 62264-3, Enterprise-control system integration – Part 3: Activity models of
manufacturing operations management
3 Terms, definitions and abbreviations
3.1 Terms and definitions
For the purposes of this document, the following terms and definitions apply. Terms,
definitions and concepts expressed in IEC 62264-1, IEC 62264-2 and IEC 62264-3 apply,
except where differences are explicitly stated in this document.
3.1.1
application
ordered set of physical and virtual processes, performed by a set of resources that conduct a
set of transactions intended to accomplish a definite objective; information provider or
information user performing the activity that is involved in a transaction
3.1.2
identifier
ID
information to identify an object or a property of an object

62264-5  IEC:2011 – 11 –
3.1.3
message
structured information unit conveyed in a one-way transfer of data between one sending
application to one or more receiving applications
3.1.4
noun
one of two parts in the content of a message, the one that represents one or more objects, as
defined in IEC 62264-1 and IEC 62264-2 object models
3.1.5
transaction
sequence of related messages that are exchanged among applications performing Level 3 or
Level 4 activities
3.1.6
verb
one of two parts in the content of a message, the one that defines the action to be performed,
or the response to a request
3.1.7
wildcard
information to identify a collection of objects or properties of objects
3.2 Abbreviations
OAGIS – Open Applications Group Interface Standard
SYNC – Synchronized data
4 Transaction messages and verbs
4.1 General
This clause defines a common set of transactions, messages and verbs that shall be used
between Level 4 and Level 3 applications to exchange the data defined in the object models
of IEC 62264-1, Clause 7 and IEC 62264-2.
A transaction shall consist of a sequence of messages, where each message shall have a
structure as defined in 4.2.
Messages shall contain both a verb area and a noun area. Information conveyed in a
message shall be contained in the noun area of a message while the actions associated with
information shall be contained in the verb area.
The role of an application initiating a transaction shall determine the set of verbs to be used in
conducting the transaction. These transaction models are described in 4.2.
Three different transaction models are defined.
a) A PULL transaction model where a user of data requests the data from a provider of the
data.
b) A PUSH model where a provider of data requests an action (processing, changing or
cancelling) on the data by another user.
c) A PUBLISH transaction model where the owner of data publishes it to users (subscribers)
of the data.
– 12 – 62264-5  IEC:2011
NOTE 1 The phrase “owner of data” is used to identify the application that has responsibility for enforcing the
consistency of data.
NOTE 2 This standard does not address the case where there may be multiple systems that can act as the owner
of data. In these situations, configurations should be set up so that one master owner of the data should be
designated, with other systems performing the role of data users.
4.2 Transaction models
There are three classes of actions provided by the verb set: query/reporting, transaction
processing, and data synchronization. These are defined by three different transaction
models.
a) A PULL model where a user of data requests information from an information provider.
This model is used for query/reporting.
Information provider applications listen for GET messages and respond with SHOW
messages to complete the transaction.
Information user applications send GET messages.
1) Requests for information are sent through GET messages.
2) A GET message describes the scope of the requested information.
3) A SHOW message returns the information.
b) A PUSH model where a sender of information sends new or changed information to the
receiver to process requests. This model is used for transaction processing.
Receiver applications listen for PROCESS, CHANGE or CANCEL messages.
Sender applications send PROCESS, CHANGE and CANCEL messages.
1) New information is pushed to the receiver through a PROCESS message. Responses
may be returned to the sender through an ACKNOWLEDGE message.
2) Changes to information are pushed to the receiver through a CHANGE message.
Responses may be returned to the sender through a RESPOND message.
3) Information to be removed is pushed to the receiver through a CANCEL message.
c) A PUBLISH model where the provider of data publishes it to users (subscribers) of the
data. This model is used for data synchronization.
Subscriber applications receive SYNC messages.
Publisher applications send SYNC messages.
1) The publisher sends SYNC messages containing new, changed or deleted information
to subscribers.
2) A subscriber receives SYNC messages containing new, changed or deleted
information.
The timing of the publication and scope of the published information is not defined in a
message. It is determined by an out-of-band agreement between the publisher and
subscriber, therefore there is no SUBSCRIBE message defined in this standard.
Example: An out-of-band agreement means that the agreement is not defined in the transaction protocol.
For example: an agreement between a publisher and subscriber may be set up through configuration
parameters in the applications, or an agreement may be set up dynamically through a web service agreement,
or an agreement may be set up through a third party application.
A single application may support one or more transaction models and the application may
take on multiple roles (sender, receiver, provider and user).
NOTE 1 The transactions are based on the assumption that the exchanged information (noun) is contained in a
message of some form. The exact form of the messages is not defined in this standard; for example, the messages
could be tab delimited files, XML files, electronic mail messages, or data in a named pipe. The exact form of the
transport mechanism for the sending, receiving, listening and publishing of messages is not defined in this
standard.
NOTE 2 The transaction message models do not imply any specific architecture or mechanism for transporting
the messages.
62264-5  IEC:2011 – 13 –
The transactions assume the ability to send an empty or nearly empty message that identifie
...