EN IEC 62714-5:2022
(Main)Engineering data exchange format for use in industrial automation systems engineering - Automation markup language - Part 5: Communication
Engineering data exchange format for use in industrial automation systems engineering - Automation markup language - Part 5: Communication
Engineering processes of technical systems and their embedded automation systems have to be executed with increasing efficiency and quality. Especially since the project duration tends to increase as the complexity of the engineered system increases. To solve this problem, the engineering process is more often being executed by exploiting software based engineering tools exchanging engineering information and artefacts along the engineering process related tool chain. Communication systems establish an important part of modern technical systems and, especially, of automation systems embedded within them. Following the increasing decentralisation of automation systems and the application of fieldbus and Ethernet technology connecting automation devices and further interacting entities have to fulfil special requirements on communication quality, safety and security. Thus, within the engineering process of modern technical systems, engineering information and artefacts relating to communication systems also have to be exchanged along the engineering process tool chain. In each phase of the engineering process of technical systems, communication system related information can be created which can be consumed in later engineering phases. A typical application case is the creation of configuration information for communication components of automation devices including communication addresses and communication package structuring within controller programming devices during the control programming phase and its use in a device configuration tool. Another typical application case is the transmission of communication device configurations to virtual commissioning tools, to documentation tools, or to diagnosis tools. At present, the consistent and lossless transfer of communication system engineering information along the complete engineering chain of technical systems is unsolved. While user organisations and companies have provided data exchange formats for parts of the relevant information like FDCML, EDDL, and GSD the above named application cases cannot be covered by a data exchange format. Notably the networking related information describing communication relations and their properties and qualities cannot be modelled by a data exchange format.
Datenaustauschformat für Planungsdaten industrieller Automatisierungssysteme - Automation markup language - Teil 5: Kommunikation
Format d’échange de données techniques pour une utilisation dans l’ingénierie des systèmes d'automatisation industrielle - Automation markup language - Partie 5: Communication
IEC 62714-5:2022 Les processus d'ingénierie des systèmes techniques et de leurs systèmes d'automatisation intégrés sont exécutés avec une efficacité et une qualité croissantes, d'autant plus que la durée du projet a tendance à augmenter avec la complexité du système d'ingénierie. Pour résoudre ce problème, le processus d'ingénierie est plus souvent exécuté en exploitant des outils d'ingénierie fondés sur des logiciels échangeant des informations et des artefacts d'ingénierie le long de la chaîne d'outils liée au processus d'ingénierie.
Oblika izmenjave tehničnih podatkov za uporabo v industrijskem inženiringu avtomatizacije sistemov - Označevalni jezik za avtomatizacijo - 5. del: Komunikacija (IEC 62714-5:2022)
Ta del standarda IEC 61010 določa varnostne zahteve za električno opremo in njene dodatke v kategorijah od a) do c), kjer koli je namenjena za uporabo in ima eno ali več spodaj navedenih lastnosti:
– HLADILNI SISTEM, ki ga upravlja ali nanj vpliva vgrajena grelna funkcija tako, da skupni grelni in HLADILNI SISTEM ustvarjata dodatne in/ali večje NEVARNOSTI, kot če bi bila sistema neodvisna;
– materiale, ki se obdelujejo pri namenski uporabi, vpeljejo znatno količino toplote v HLADILNI SISTEM, tako da HLADILNI SISTEM pri taki uporabi ustvarja dodatne in/ali večje NEVARNOSTI, kot če bi deloval zgolj pri največji NAZIVNI temperaturi okolja;
– funkcijo obsevanja obdelovanih materialov, ki predstavlja dodatne NEVARNOSTI;
– funkcijo za izpostavljanje materialov, ki se obdelujejo, prekomerni vlagi, ogljikovemu dioksidu, solni megli ali drugim snovem, ki lahko povzročijo dodatne NEVARNOSTI;
– funkcijo MEHANSKEGA GIBANJA, ki predstavlja dodatne NEVARNOSTI;
– določbo, ki UPRAVLJAVCU dovoljuje, da vstopi na območje delovanja, da naloži ali razloži obdelovane materiale.
General Information
Standards Content (Sample)
SLOVENSKI STANDARD
01-julij-2022
Oblika izmenjave tehničnih podatkov za uporabo v industrijskem inženiringu
avtomatizacije sistemov - Označevalni jezik za avtomatizacijo - 5. del:
Komunikacija (IEC 62714-5:2022)
Engineering data exchange format for use in industrial automation systems engineering -
Automation markup language - Part 5: Communication (IEC 62714-5:2022)
Datenaustauschformat für Planungsdaten industrieller Automatisierungssysteme -
Automation markup language - Teil 5: Kommunikation (IEC 62714-5:2022)
Format d'échange de données techniques pour une utilisation dans l'ingénierie des
systèmes d'automatisation industrielle - Automation markup language - Partie 5:
Communication (IEC 62714-5:2022)
Ta slovenski standard je istoveten z: EN IEC 62714-5:2022
ICS:
25.040.40 Merjenje in krmiljenje Industrial process
industrijskih postopkov measurement and control
35.060 Jeziki, ki se uporabljajo v Languages used in
informacijski tehniki in information technology
tehnologiji
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 IEC 62714-5
NORME EUROPÉENNE
EUROPÄISCHE NORM April 2022
ICS 25.040; 25.040.01
English Version
Engineering data exchange format for use in industrial
automation systems engineering - Automation markup language
- Part 5: Communication
(IEC 62714-5:2022)
Format d'échange de données techniques pour une Datenaustauschformat für Planungsdaten industrieller
utilisation dans l'ingénierie des systèmes d'automatisation Automatisierungssysteme - Automation markup language -
industrielle - Automation markup language - Partie 5: Teil 5: Kommunikation
Communication (IEC 62714-5:2022)
(IEC 62714-5:2022)
This European Standard was approved by CENELEC on 2022-04-15. 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, Republic of North Macedonia, Romania, Serbia, Slovakia, Slovenia, Spain, Sweden, Switzerland,
Turkey and the United Kingdom.
European Committee for Electrotechnical Standardization
Comité Européen de Normalisation Electrotechnique
Europäisches Komitee für Elektrotechnische Normung
CEN-CENELEC Management Centre: Rue de la Science 23, B-1040 Brussels
© 2022 CENELEC All rights of exploitation in any form and by any means reserved worldwide for CENELEC Members.
Ref. No. EN IEC 62714-5:2022 E
European foreword
The text of document 65E/844/FDIS, future edition 1 of IEC 62714-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:
• latest date by which the document has to be implemented at national (dop) 2023-01-15
level by publication of an identical national standard or by endorsement
• latest date by which the national standards conflicting with the (dow) 2025-04-15
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 shall not be held responsible for identifying any or all such patent rights.
Any feedback and questions on this document should be directed to the users’ national committee. A
complete listing of these bodies can be found on the CENELEC website.
Endorsement notice
The text of the International Standard IEC 62714-5:2022 was approved by CENELEC as a European
Standard without any modification.
Annex ZA
(normative)
Normative references to international publications
with their corresponding European publications
The following documents are referred to in the text in such a way that some or all of their content
constitutes requirements 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.
NOTE 1 Where an International Publication has been modified by common modifications, indicated by (mod),
the relevant EN/HD applies.
NOTE 2 Up-to-date information on the latest versions of the European Standards listed in this annex is available
here: www.cenelec.eu.
Publication Year Title EN/HD Year
IEC 61131-3 - Programmable controllers - Part 3: EN 61131-3 -
Programming languages
IEC 61131-10 2019 Programmable controllers - Part 10: PLC EN IEC 61131-10 2019
open XML exchange format
IEC 62424 2016 Representation of process control EN 62424 2016
engineering - Requests in P&I diagrams
and data exchange between P&ID tools
and PCE-CAE tools
IEC 62714-1 - Engineering data exchange format for use EN IEC 62714-1 -
in industrial automation systems
engineering - Automation Markup
Language - Part 1: Architecture and
general requirements
Engineering data exchange format for use
IEC 62714-4 - EN IEC 62714-4 -
in industrial automation systems
engineering - Automation markup
language - Part 4: Logic
IEC 81346 series Industrial systems, installations and - series
equipment and industrial products -
Structuring principles and reference
designations
IEC 62714-5 ®
Edition 1.0 2022-03
INTERNATIONAL
STANDARD
NORME
INTERNATIONALE
colour
inside
Engineering data exchange format for use in industrial automation systems
engineering – Automation markup language –
Part 5: Communication
Format d’échange de données techniques pour une utilisation dans l’ingénierie
des systèmes d'automatisation industrielle – Automation markup language –
Partie 5: Communication
INTERNATIONAL
ELECTROTECHNICAL
COMMISSION
COMMISSION
ELECTROTECHNIQUE
INTERNATIONALE
ICS 25.040; 25.040.01 ISBN 978-2-8322-1085-7
– 2 – IEC 62714-5:2022 © IEC 2022
CONTENTS
FOREWORD . 6
1 Scope . 8
2 Normative references . 8
3 Terms, definitions, abbreviated terms and acronyms . 9
3.1 Terms and definitions . 9
3.2 Abbreviated terms and acronyms . 9
4 Use cases and network structures . 10
4.1 General . 10
4.2 Use cases . 10
4.2.1 Engineering activities. 10
4.2.2 Lossless transfer of communication device instance information . 11
4.2.3 Lossless transfer of communication system information . 14
4.3 Delimitation of modelling range . 16
4.3.1 Scope of the modelling range . 16
4.3.2 Interaction structures and life cycles . 16
4.3.3 Network objects . 17
4.3.4 Network topologies . 18
4.3.5 Communication content . 23
4.4 Derived modelling requirements . 23
5 UML model . 24
5.1 Overview. 24
5.2 Logical topology . 24
5.2.1 Aim of logical topology . 24
5.2.2 Item logicalTopology . 25
5.2.3 Item logicalConnection . 25
5.2.4 Item logicalEndPoint . 25
5.3 Physical topology . 26
5.3.1 Aim of physical topology . 26
5.3.2 Item physicalTopology . 26
5.3.3 Item physicalConnection . 26
5.3.4 Item physicalEndPoint . 27
5.4 Device . 27
5.4.1 General . 27
5.4.2 Item physicalDevice . 27
5.4.3 Item Information . 28
5.4.4 Item physicalDeviceInformation . 29
5.4.5 Item logicalDeviceInformation . 29
5.4.6 Item logicalDevice . 29
5.4.7 Item networkDataList . 29
5.4.8 Item networkDataItem . 29
5.4.9 Item logicalEndPointList . 29
5.4.10 Item physicalEndPointList . 29
5.4.11 Item physicalChannelList . 29
5.4.12 Item physicalChannel . 30
5.4.13 Item deviceResource . 30
5.4.14 Item variableList . 30
5.4.15 Item variable . 30
IEC 62714-5:2022 © IEC 2022 – 3 –
5.4.16 Item pduList . 31
5.4.17 Item pdu . 31
5.4.18 Item protocolData . 32
5.4.19 Item payload . 32
5.4.20 Item processDataItemList . 32
5.4.21 Item parameterItemList . 32
5.4.22 Item dataItem . 32
5.4.23 Item processDataItem . 32
5.4.24 Item processDataInput . 33
5.4.25 Item processDataOutput . 33
5.4.26 Item parameterItem . 33
6 Representation within AutomationML . 33
6.1 Overview of mapping . 33
6.1.1 Introduction of mapping . 33
6.1.2 General mapping rules. 33
6.1.3 Basics . 34
6.1.4 Modelling of relations. 35
6.1.5 Application process . 36
6.2 Basic communication role class library . 38
6.2.1 General . 38
6.2.2 RoleClass PhysicalDevice . 39
6.2.3 RoleClass PhysicalEndpointlist . 40
6.2.4 RoleClass PhysicalConnection . 40
6.2.5 RoleClass PhysicalNetwork . 40
6.2.6 RoleClass LogicalDevice . 41
6.2.7 RoleClass LogicalEndpointlist . 41
6.2.8 RoleClass LogicalConnection . 41
6.2.9 RoleClass LogicalNetwork . 41
6.3 Basic communication interface class library . 42
6.3.1 General . 42
6.3.2 InterfaceClass PhysicalEndPoint . 42
6.3.3 InterfaceClass LogicalEndPoint . 42
6.4 Steps to model technology specific libraries . 43
6.4.1 General . 43
6.4.2 Step 1: Development of technology specific role classes . 43
6.4.3 Step 2: Development of technology specific interface classes . 44
6.4.4 Step 3: Development of system unit class libraries . 44
6.4.5 Step 4: Modelling the network . 45
6.4.6 Step 5: Modelling the connections . 46
6.5 PDU modelling . 46
6.5.1 General . 46
6.5.2 RoleClass CommunicationPackage . 47
6.5.3 InterfaceClass DatagrammObject . 48
6.5.4 Steps to model technology specific libraries . 49
6.6 References to attributes . 51
6.7 Usage of metadata . 53
Bibliography . 55
– 4 – IEC 62714-5:2022 © IEC 2022
Figure 1 – General engineering activities communication system engineering is
embedded within . 10
Figure 2 – Information flow of the use case . 12
Figure 3 – Alternative information flow of the use case . 13
Figure 4 – Information flow of the use case . 15
Figure 5 – Example of a logical level view on communication systems . 17
Figure 6 – Example of a physical level view on communication systems . 18
Figure 7 – Combined views on communication systems . 18
Figure 8 – Star topology example. 19
Figure 9 – Ring topology example . 19
Figure 10 – Line topology example . 20
Figure 11 – Simple network with direct wiring . 20
Figure 12 – Network with active infrastructure . 21
Figure 13 – Networks connected by gateways . 21
Figure 14 – Hierarchical structured networks . 22
Figure 15 – Network covering multiple applications . 22
Figure 16 – General modelling strategy for PDUs. 23
Figure 17 – Structure of communication network . 24
Figure 18 – View on logical topology . 25
Figure 19 – View on physical topology . 26
Figure 20 – Part 1 of the device model . 28
Figure 21 – Part 2 of the device model . 31
Figure 22 – Communication role class library and communication interface class
library . 35
Figure 23 – Derived role class libraries and interface class libraries for a special
example . 35
Figure 24 – SystemUnitClassLib examples for communication system modelling . 37
Figure 25 – Final network model example . 38
Figure 26 – Basic communication role class library . 39
Figure 27 – CommunicationRoleClassLib . 39
Figure 28 – XML text of the communication role class library . 39
Figure 29 – Basic communication interface class library . 42
Figure 30 – CommunicationInterfaceClassLib . 42
Figure 31 – XML text of the communication interface class library . 42
Figure 32 – Derivation of a technology specific role class library out of the base role
class library . 43
Figure 33 – Derivation of a technology specific role class library out of the base role
class library . 44
Figure 34 – Technology specific s . 45
Figure 35 – Technology specific communication network . 46
Figure 36 – Extended communication role class library . 47
Figure 37 – Extended CommunicationRoleClassLib . 47
Figure 38 – XML text of the extended communication role class library . 47
Figure 39 – Extended communication interface class library . 48
Figure 40 – Extended CommunicationInterfaceClassLib . 48
IEC 62714-5:2022 © IEC 2022 – 5 –
Figure 41 – XML text of the extended communication role class library . 48
Figure 42 – Derivation of a technology specific role class library out of the extended
role class library . 49
Figure 43 – Derivation of a technology specific interface class library out of the
extended interface class library . 50
Figure 44 – Technology specific extended s . 50
Figure 45 – Technology specific communication network with communication package
models . 51
Figure 46 − Field SourceDocumentInformation according to communication related
libraries . 54
Table 1 – Mapping rules . 34
Table 2 – Modelling of relations in AutomationML . 36
Table 3 – RoleClass PhysicalDevice . 40
Table 4 – RoleClass PhysicalEndpointlist . 40
Table 5 – RoleClass PhysicalConnection . 40
Table 6 – RoleClass PhysicalNetwork . 40
Table 7 – RoleClass LogicalDevice . 41
Table 8 – RoleClass LogicalEndpointlist . 41
Table 9 – RoleClass LogicalConnection . 41
Table 10 – RoleClass LogicalNetwork . 41
Table 11 – InterfaceClass PhysicalEndPoint . 42
Table 12 – InterfaceClass LogicalEndPoint . 43
Table 13 – RoleClass CommunicationPackage . 48
Table 14 – InterfaceClass DatagrammObject . 49
Table 15 – Communication related attributes . 52
– 6 – IEC 62714-5:2022 © IEC 2022
INTERNATIONAL ELECTROTECHNICAL COMMISSION
____________
ENGINEERING DATA EXCHANGE FORMAT FOR USE
IN INDUSTRIAL AUTOMATION SYSTEMS ENGINEERING –
AUTOMATION MARKUP LANGUAGE –
Part 5: Communication
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.
IEC 62714-5 has been prepared by subcommittee 65E: Devices and integration in enterprise
systems, of IEC technical committee 65: Industrial-process measurement, control and
automation. It is an International Standard.
The text of this International Standard is based on the following documents:
Draft Report on voting
65E/844/FDIS 65E/886/RVD
Full information on the voting for its approval can be found in the report on voting indicated in
the above table.
The language used for the development of this International Standard is English.
IEC 62714-5:2022 © IEC 2022 – 7 –
This document was drafted in accordance with ISO/IEC Directives, Part 2, and developed in
accordance with ISO/IEC Directives, Part 1 and ISO/IEC Directives, IEC Supplement, available
at www.iec.ch/members_experts/refdocs. The main document types developed by IEC are
described in greater detail at www.iec.ch/standardsdev/publications.
A list of all parts of the IEC 62714 series, under the general title Engineering data exchange
format for use in industrial automation systems engineering – Automation markup language,
can be found on the IEC website.
The committee has decided that the contents of this document will remain unchanged until the
stability date indicated on the IEC website under webstore.iec.ch in the data related to the
specific document. At this date, the document will be
• reconfirmed,
• withdrawn,
• replaced by a revised edition, or
• amended.
IMPORTANT – The "colour inside" logo on the cover page of this document indicates
that it contains colours which are considered to be useful for the correct understanding
of its contents. Users should therefore print this document using a colour printer.
– 8 – IEC 62714-5:2022 © IEC 2022
ENGINEERING DATA EXCHANGE FORMAT FOR USE
IN INDUSTRIAL AUTOMATION SYSTEMS ENGINEERING –
AUTOMATION MARKUP LANGUAGE –
Part 5: Communication
1 Scope
Engineering processes of technical systems and their embedded automation systems are
executed with increasing efficiency and quality. Especially since the project duration tends to
increase as the complexity of the engineered system increases. To solve this problem, the
engineering process is more often being executed by exploiting software based engineering
tools exchanging engineering information and artefacts along the engineering process related
tool chain.
Communication systems establish an important part of modern technical systems and,
especially, of automation systems embedded within them. Following the increasing
decentralisation of automation systems and the application of fieldbus and Ethernet technology
connecting automation devices and further interacting entities need to fulfil special
requirements on communication quality, safety and security. Thus, within the engineering
process of modern technical systems, engineering information and artefacts relating to
communication systems also need to be exchanged along the engineering process tool chain.
In each phase of the engineering process of technical systems, communication system related
information can be created which can be consumed in later engineering phases. A typical
application case is the creation of configuration information for communication components of
automation devices including communication addresses and communication package
structuring within controller programming devices during the control programming phase and
its use in a device configuration tool. Another typical application case is the transmission of
communication device configurations to virtual commissioning tools, to documentation tools, or
to diagnosis tools.
At present, the consistent and lossless transfer of communication system engineering
information along the complete engineering chain of technical systems is unsolved. While user
organisations and companies have provided data exchange formats for parts of the relevant
information like FDCML, EDDL, and GSD, the above named application cases cannot be
covered by a data exchange format. Notably the networking related information describing
communication relations and their properties and qualities cannot be modelled by a data
exchange format.
2 Normative references
The following documents are referred to in the text in such a way that some or all of their content
constitutes requirements 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 61131-3, Programmable controllers − Part 3: Programming languages
IEC 61131-10:2019, Programmable controllers – Part 10: PLC open XML exchange format
IEC 62424:2016, Representation of process control engineering − Requests in P&I diagrams
and data exchange between P&ID tools and PCE-CAE tools
IEC 62714-5:2022 © IEC 2022 – 9 –
IEC 62714-1, Engineering data exchange format for use in industrial systems engineering –
Automation Markup Language – Part 1: Architecture and general requirements
IEC 62714-4, Engineering data exchange format for use in industrial systems engineering –
Automation markup language − Part 4: Logic
IEC 81346 (all parts), Industrial systems, installations and equipment and industrial products –
Structuring principles and reference designations
3 Terms, definitions, abbreviated terms and acronyms
3.1 Terms and definitions
For the purposes of this document, the terms and definitions given in IEC 62714-1 and the
following apply.
ISO and IEC maintain terminological databases for use in standardization at the following
addresses:
• IEC Electropedia: available at http://www.electropedia.org/
• ISO Online browsing platform: available at http://www.iso.org/obp
3.1.1
AutomationML/AML
XML based data exchange format for plant engineering data
3.1.2
Automation object
entity in an automated system
Note 1 to entry: An example of an automation object is an automation component, a valve, or a signal.
3.2 Abbreviated terms and acronyms
For the purposes of this document, the following abbreviations apply.
AML Automation Markup Language
CAEX Computer Aided Engineering Exchange as defined in IEC 62424:2016
ECAD Computer aided engineering for electrical engineering
EDDL Electronic Device Description Language
FDCML Field Device Configuration Markup Language
GUID Global Unique Identifier
GSD General Station Description
HMI Human Machine Interface
ID Identifier
MCAD Computer aided engineering for mechanical engineering
OPC Open Platform Communications
PDU Protocol Data Unit
SCADA Supervisory Control And Data Acquisition
UML Unified Modelling Language
UUID Universal Unique Identifier
XML Extensible Markup Language
– 10 – IEC 62714-5:2022 © IEC 2022
4 Use cases and network structures
4.1 General
The modelling of communication systems based on AutomationML targets the modelling of a
large amount of information created, exchanged, and applied within the engineering process of
manufacturing systems. Nevertheless, not all possible communication system related
information will be modelled. Within the following subclause, the use cases for the application
of the communication system modelling as well as the relevant information sets within them are
named.
4.2 Use cases
4.2.1 Engineering activities
Network topology and communication system related information is relevant to various
engineering activities along the engineering chain of production systems. Within the
engineering process of production systems, the communication system can be designed in the
detailed engineering phase exploiting various tools. Thereby, communication system related
information is created which subsequently can be applied within the detailed design of devices
and the device commissioning. Figure 1 represents an example set of engineering activities
relevant within the general engineering process of production systems and the communication
system engineering embedded within.
Figure 1 – General engineering activities communication
system engineering is embedded within
Within the named engineering activities, engineering tools like (but not limited to) the following
will have a relevant impact:
• plant planning tools,
• mechanical engineering tools (MCAD),
• electrical engineering tools (ECAD),
• controller programming tools,
• robot programming tools,
• HMI programming tools,
• OPC system configuration tools,
IEC 62714-5:2022 © IEC 2022 – 11 –
• device configuration tools,
• bus configuration tools,
• simulation tools,
• SCADA systems,
• virtual commissioning tools,
• documentation tools,
• communication system security tools,
• communication system management tools,
• communication system diagnosis tools.
These tools will create and/or consume communication system related engineering information
depending on the use case of the engineering chain.
Nevertheless, (among others) there are two main application cases within this engineering
chain, where communication system related information can be exchanged between
engineering tools. These two use cases are the main target of the modelling of communication
systems based on AutomationML.
4.2.2 Lossless transfer of communication device instance information
Within the general engineering process, this use case covers the transition of communication
relevant information for configuration of communication components of sensors and actuators
from controller programming tool and similar tools to sensor and actuator
configuration/programming tools. It contains the transition of information relevant for correct
communication (like addresses and channels) as well as for correct structuring of
communication data packages transmitted within communication (like transmitted data points
of sensors). An overview is shown in Figure 2.
Within the related engineering activities, engineers with the engineering roles of controller
programmer, HMI programmer, electrical design engineer, commissioner communication,
commissioner controller, and robot programmer can be involved. They will execute the following
sequence of engineering and data exchange activities which should be seen as an example
sequence.
Step 1. Design of system instrumentation, definition of used/interconnected devices
Step 2. Export of device information from system instrumentation tool
Step 3. Import of device information to controller programming and device configuration tools
Step 4. Integration of device descriptions (like GSD) in controller programming tool
Step 5. Design of controller programs and configurations within controller programming tool
Step 6. Export of communication device relevant information from controller programming tool
Step 7. Import of communication device relevant information to device configuration tool
Step 8. Use of information for parameterisation of communication component of device
(addresses, etc.) and for structuring of communication packages (send data points)
– 12 – IEC 62714-5:2022 © IEC 2022
Figure 2 – Information flow of the use case
There are different alternatives possible but not usually applied. The following two sequences
are imaginable which will be in the focus of the use case.
Sequence 1:
Step 1. Design of communication system configurations within third party tool
Step 2. Integration of device descriptions
Step 3. Export of communication device relevant information
Step 4. Import of communication device relevant information to device
configuration/programming tool
Step 5. Use of information for parameterization of communication component of device
(addresses, etc.) and for structuring of communication packages (send data points)
Sequence 2:
Step 1. Third party tool, e.g. the device configuration tool provides information like signals,
data volume, describing the instance information
Step 2. Device vendor provides device descriptions, describing the type information
Step 3. Bus configuration tool consumes these snippets and device descriptions
Step 4. Bus configurator generates bus configuration
IEC 62714-5:2022 © IEC 2022 – 13 –
Step 5. Import of the bus configuration into the controller programming tool
Step 6. Use of information from peripheral devices inside the controller program
Both sequences are commonly depicted in Figure 3.
Figure 3 – Alternative information flow of the use case
Possible tools exporting communication system information can be e.g. controller programming
tools. They cover controller programming projects with data points (variables), device
configurations, and indirect communication network descriptions. In addition, communication
system engineering tools can be data sources as well as instrumentation tools like ECAD tools.
Data sinks of the data exchange can be tools for sensor communication configuration, HMI
programming, robot programming, OPC system configuration, or actor communication
configuration. They mostly cover programming projects with data points (variables), device
configurations, and indirect communication network descriptions. Relevant tools can be FDT
tools, HMI programming tools, and robot programming tools.
Based on this use case, the modelling of communication systems based on AutomationML
shou
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.
Loading comments...