IEC 62714-1:2018
(Main)Engineering data exchange format for use in industrial automation systems engineering - Automation Markup Language - Part 1: Architecture and general requirements
Engineering data exchange format for use in industrial automation systems engineering - Automation Markup Language - Part 1: Architecture and general requirements
IEC 62714-1:2018 is a solution for data exchange focusing on the domain of automation engineering. The data exchange format defined in the IEC 62714 series (Automation Markup Language, AML) is an XML schema based data format and has been developed in order to support the data exchange in a heterogeneous engineering tools landscape. The goal of AML is to interconnect engineering tools in their different disciplines, e.g. mechanical plant engineering, electrical design, process engineering, process control engineering, HMI development, PLC programming, robot programming, etc. This second edition cancels and replaces the first edition published in 2014. This edition constitutes a technical revision. This edition includes the following significant technical changes with respect to the previous edition:
a) use of CAEX 3.0 according to IEC 62424:2016
b) improved modelling of references to documents outside of the scope of the present standard,
c) modelling of references between CAEX attributes and items in external documents,
d) revised role libraries,
e) modified Port concept,
f) modelling of multilingual expressions,
g) modelling of structured attribute lists or array,
h) a new AML container format,
i) a new standard AML attribute library
Format d'échange de données techniques pour une utilisation dans l'ingéniérie des systèmes d'automatisation industrielle - Automation Markup Language - Partie 1: Architecture et exigences générales
L'IEC 62714-1:2018 constitue une approche de l'échange de données qui cible le domaine de l'ingénierie de l'automatisation. Le format d'échange de données défini dans la série IEC 62714 (Automation Markup Language, AML) est un format de données de type schéma XML pour les données d'ingénierie d'usine. L’AML a été mis au point afin de venir à l'appui de l'échange de données dans un environnement d'outils techniques hétérogène. L'objectif de l’AML est l'interconnexion des outils techniques dans leurs différentes disciplines, par exemple, ingénierie des installations mécaniques, études d'électricité, ingénierie de procédés, ingénierie de commande de processus, développement des IHM, programmation PLC, programmation de robots, etc. Cette deuxième édition annule et remplace la première édition parue en 2014. Cette édition constitue une révision technique. Cette édition inclut les modifications techniques majeures suivantes par rapport à l'édition précédente:
a) utilisation de CAEX 3.0 conformément à l'IEC 62424:2016
b) modélisation améliorée des références aux documents ne relevant pas du domaine d'application de la présente norme,
c) modélisation des références entre les attributs CAEX et les éléments dans des documents externes (dans une feuille Excel, par exemple),
d) bibliothèques de rôles révisées,
e) concept d'accès modifié,
f) modélisation des expressions multilingues,
g) modélisation de listes ou de tableaux d'attributs structuré(e)s,
h) nouveau format de conteneur AML,
i) nouvelle bibliothèque d'attributs AML normalisée.
General Information
Relations
Standards Content (Sample)
IEC 62714-1 ®
Edition 2.0 2018-04
REDLINE VERSION
INTERNATIONAL
STANDARD
colour
inside
Engineering data exchange format for use in industrial automation systems
engineering – Automation markup language –
Part 1: Architecture and general requirements
IEC 62714-2018-04 RLV(en)
All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized in any form
or by any means, electronic or mechanical, including photocopying and microfilm, without permission in writing from
either IEC or IEC's member National Committee in the country of the requester. If you have any questions about IEC
copyright or have an enquiry about obtaining additional rights to this publication, please contact the address below or
your local IEC member National Committee for further information.
IEC Central Office Tel.: +41 22 919 02 11
3, rue de Varembé info@iec.ch
CH-1211 Geneva 20 www.iec.ch
Switzerland
About the IEC
The International Electrotechnical Commission (IEC) is the leading global organization that prepares and publishes
International Standards for all electrical, electronic and related technologies.
About IEC publications
The technical content of IEC publications is kept under constant review by the IEC. Please make sure that you have the
latest edition, a corrigenda or an amendment might have been published.
IEC Catalogue - webstore.iec.ch/catalogue Electropedia - www.electropedia.org
The stand-alone application for consulting the entire The world's leading online dictionary of electronic and
bibliographical information on IEC International Standards, electrical terms containing 21 000 terms and definitions in
Technical Specifications, Technical Reports and other English and French, with equivalent terms in 16 additional
documents. Available for PC, Mac OS, Android Tablets and languages. Also known as the International Electrotechnical
iPad. Vocabulary (IEV) online.
IEC publications search - webstore.iec.ch/advsearchform IEC Glossary - std.iec.ch/glossary
The advanced search enables to find IEC publications by a 67 000 electrotechnical terminology entries in English and
variety of criteria (reference number, text, technical French extracted from the Terms and Definitions clause of
committee,…). It also gives information on projects, replaced IEC publications issued since 2002. Some entries have been
and withdrawn publications. collected from earlier publications of IEC TC 37, 77, 86 and
CISPR.
IEC Just Published - webstore.iec.ch/justpublished
Stay up to date on all new IEC publications. Just Published IEC Customer Service Centre - webstore.iec.ch/csc
details all new publications released. Available online and If you wish to give us your feedback on this publication or
also once a month by email. need further assistance, please contact the Customer Service
Centre: sales@iec.ch.
IEC 62714-1 ®
Edition 2.0 2018-04
REDLINE VERSION
INTERNATIONAL
STANDARD
colour
inside
Engineering data exchange format for use in industrial automation systems
engineering – Automation markup language –
Part 1: Architecture and general requirements
INTERNATIONAL
ELECTROTECHNICAL
COMMISSION
ICS 25.040.40; 35.060; 35.240.50 ISBN 978-2-8322-5662-6
– 2 – IEC 62714-1:2018 RLV © IEC 2018
CONTENTS
FOREWORD . 8
INTRODUCTION . 11
1 Scope . 13
2 Normative references . 13
3 Terms, definitions and abbreviations . 14
3.1 Terms and definitions . 14
3.2 Abbreviations . 17
4 Conformity . 17
5 AML architecture specification . 17
5.1 General . 17
5.2 General AML architecture . 17
5.3 AM Sub document versions and AML superior document information . 18
5.4 Meta information about the AML source tool . 19
Object identification .
5.5 AML relations specification . 22
5.5.1 General . 22
Parent-child-relations between AML objects .
Parent-child-relations between AML classes .
Inheritance relations .
5.5.2 Class-instance-relations . 24
5.5.3 Instance-instance-relations . 25
5.5.4 Identification of objects . 27
5.6 AML document reference specification . 27
5.6.1 General . 27
5.6.2 Referencing COLLADA documents . 27
5.6.3 Referencing PLCopen XML documents . 27
5.6.4 Referencing additional documents in the scope of IEC 62714 (all parts) . 27
5.6.5 Referencing documents outside of the scope of IEC 62714 (all parts) . 28
5.6.6 Referencing CAEX attributes to items in external documents . 28
6 AML base libraries . 29
6.1 General . 29
6.2 General provisions . 29
6.3 AML interface class library – AutomationMLInterfaceClassLib . 29
6.3.1 General . 29
6.3.2 InterfaceClass AutomationMLBaseInterface . 32
6.3.3 InterfaceClass Order . 33
InterfaceClass PortConnector .
6.3.4 InterfaceClass Port . 34
6.3.5 InterfaceClass PPRConnector . 34
6.3.6 InterfaceClass ExternalDataConnector . 35
6.3.7 InterfaceClass COLLADAInterface . 35
6.3.8 InterfaceClass PLCopenXMLInterface . 36
6.3.9 InterfaceClass ExternalDataReference . 36
6.3.10 InterfaceClass Communication . 37
6.3.11 InterfaceClass SignalInterface . 37
6.4 AML basic role class library – AutomationMLBaseRoleClassLib . 37
6.4.1 General . 37
6.4.2 RoleClass AutomationMLBaseRole . 40
6.4.3 RoleClass Group . 40
6.4.4 RoleClass Facet . 41
RoleClass Port .
6.4.5 RoleClass Resource . 42
6.4.6 RoleClass Product . 43
6.4.7 RoleClass Process . 43
6.4.8 RoleClass Structure . 43
6.4.9 RoleClass ProductStructure . 44
6.4.10 RoleClass ProcessStructure . 44
6.4.11 RoleClass ResourceStructure . 44
RoleClass PropertySet.
6.4.12 RoleClass ExternalData . 45
6.5 AML basic attribute type library . 46
6.5.1 General . 46
6.5.2 Attributes of the AutomationMLBaseAttributeTypeLib . 47
7 Modelling of user-defined data . 50
7.1 General . 50
7.2 User-defined attributes. 50
7.3 User-defined AttributeTypes . 50
7.4 User-defined InterfaceClasses . 51
7.5 User-defined RoleClasses . 52
7.6 User-defined SystemUnitClasses . 53
7.7 User-defined InstanceHierarchies . 54
8 Extended AML concepts . 55
8.1 General overview . 55
8.2 AML Port object interface . 55
8.3 AML Facet object . 56
8.4 AML Group object . 56
AML PropertySet .
Support of multiple roles .
8.5 Splitting of AML top-level data into different documents . 60
8.6 Internationalization, AML multilingual expression . 60
8.7 Version information of AML objects . 61
8.8 Modelling of structured attribute lists or arrays . 61
8.9 AML Container . 61
Annex A (informative) General introduction into the Automation Markup Language . 63
A.1 General Automation Markup Language concepts . 63
A.1.1 The Automation Markup Language architecture . 63
A.1.2 Modelling of plant topology information . 64
A.1.3 Referencing geometry and kinematics information . 66
A.1.4 Referencing logic information . 66
A.1.5 Referencing documents outside of the scope of IEC 62714 . 67
A.1.6 Interlinking CAEX attributes and attributes in external documents . 68
A.1.7 Modelling of relations. 69
A.2 Extended AML concepts and examples . 72
A.2.1 General overview . 72
A.2.2 AML Port concept . 72
– 4 – IEC 62714-1:2018 RLV © IEC 2018
A.2.3 AML Facet concept . 76
A.2.4 AML Group concept . 77
PropertySet concept .
A.2.5 Process-Product-Resource concept . 85
Support of multiple roles . 76
A.2.6 AML multilingual expression concept . 96
A.2.7 Attribute lists and arrays . 97
Annex B (informative) XML representation of standard AML base libraries . 101
AutomationMLBaseRoleClassLib .
AutomationMLInterfaceClassLib .
Bibliography . 105
Figure – Object identification example of an AML class .
Figure – Object identification example of an AML object instance .
Figure – Example of a parent-child-relation between AML objects .
Figure – Example of a parent-child-relation between classes .
Figure – Example of an inheritance relation between two classes .
Figure – Example of a class-instance-relation .
Figure – Example illustrating the PropertySet concept .
Figure – XML text of the PropertySet example .
Figure – PropertySet example .
Figure – PropertySet example .
Figure – XML text for the instance hierarchy .
Figure – PropertySet example AML library as XML code .
Figure – Example of a user-defined instance supporting multiple roles .
Figure – XML text of the AML representation of multiple role support .
Figure – AML Role class library corresponding to the multiple role definition example .
Figure – XML text of the AML role class library .
Figure 1 – Overview of the engineering data exchange format AML . 11
Figure 2 – AML document version information . 19
Figure 3 – XML text of the AML source tool information . 21
Figure 4 – Example of a relation as block diagram and as object tree . 26
Figure 5 – Example relation between the objects “PLC1” and “Rob1” . 26
Figure 6 – XML text of the example relation between the objects “PLC1” and “Rob1” . 27
Figure 7 – AML basic interface class library . 31
Figure 8 – XML description of the AML basic interface class library . 32
Figure 9 – AML basic role class library. 38
Figure 10 – AutomationMLBaseRoleClassLib . 39
Figure 11 – XML text of the AutomationMLBaseRoleClassLib . 39
Figure 12 – AML basic attribute type library . 46
Figure 13 – XML text of the AutomationMLBaseAttributeTypeLib . 47
Figure 14 – Example of a user-defined attribute . 50
Figure 15 – Examples for user-defined AttributeTypes . 51
Figure 16 – XML code of the examples for user-defined AttributeTypes . 51
Figure 17 – Example of a user-defined InterfaceClass in a user-defined
InterfaceClassLib . 52
Figure 18 – XML code of the example of a user-defined InterfaceClass in a user-
defined InterfaceClassLib . 52
Figure 19 – Example of a user-defined RoleClass in a user-defined RoleClassLib . 53
Figure 20 – XML code of the example of a user-defined RoleClass in a user-defined
RoleClassLib . 53
Figure 21 – Examples for different user-defined SystemUnitClasses . 53
Figure 22 – XML code of the examples for different user-defined SystemUnitClasses . 54
Figure 23 – Example of a user-defined InstanceHierarchy . 54
Figure 24 – AML representation of a user-defined InstanceHierarchy . 55
Figure A.1 – AML general architecture . 63
Figure A.2 – Plant topology with AML . 65
Figure A.3 – Reference from CAEX to a COLLADA document . 66
Figure A.4 – Reference from a CAEX to a PLCopen XML document . 67
Figure A.5 – Example of referencing an external document . 67
Figure A.6 – XML text of the example for referencing an external document . 68
Figure A.7 – Example of referencing a CAEX attribute to an item in an external
document . 69
Figure A.8 – XML text of the example for referencing a CAEX attribute to an item in an
external document . 69
Figure A.9 – Relations in AML . 70
Figure A.10 – XML description of the relations example . 71
Figure A.11 – XML text of the SystemUnitClassLib of the relations example . 71
Figure A.12 – XML text of the InstanceHierarchy of the relations example . 72
Figure A.13 – Port concept . 73
Figure A.14 – Example describing the AML Port concept . 73
Figure A.15 – XML description of the AML Port concept . 74
Figure A.16 – XML text describing the AML Port concept . 75
Figure A.17 – Definition of a user-defined AML Port class “UserDefinedPort” . 76
Figure A.18 – AML Facet example . 77
Figure A.19 – XML text of the AML Facet example . 77
Figure A.20 – AML Group example . 78
Figure A.21 – XML text for the AML Group example . 79
Figure A.22 – Combination of the Facet and Group concept . 80
Figure A.23 – XML text view for the combined Facet-Group example . 81
Figure A.24 – Generic HMI template “B” visualizing a process variable “Y” of a
conveyor . 82
Figure A.25 – Generated HMI result “B” visualizing both conveyors with individual
process variables . 82
Figure A.26 – Base elements of the Product-Process-Resource concept . 86
Figure A.27 – PPRConnector interface. 87
Figure A.28 – Example for the Product-Process-Resource concept . 87
Figure A.29 – AML roles required for the Process-Product-Resource concept . 88
Figure A.30 – Elements of the example . 88
– 6 – IEC 62714-1:2018 RLV © IEC 2018
Figure A.31 – Links within the example . 89
Figure A.32 – Links of the resource centric view on the example . 90
Figure A.33 – InstanceHierarchy of the example in AML . 91
Figure A.34 – InternalElements of the example . 92
Figure A.35 – InternalLinks of the example . 92
Figure A.36 – InstanceHierarchy of the example in XML . 93
Figure A.37 – Example describing the AML multilingual expression concept . 96
Figure A.38 – XML description of the AML multilingual expression concept . 96
Figure A.39 – XML text describing the AML multilingual expression concept . 97
Figure A.40 – AML model of a multilingual AttributeType . 97
Figure A.41 – XML code of the a multilingual AttributeType . 97
Figure A.42 – Attribute list “SupportedFrequencies” . 98
Figure A.43 – XML code for the attribute list “SupportedFrequencies” . 98
Figure A.44 – Example CAEX model of the array “Edges” . 99
Figure A.45 – XML code for the attribute array “Edges” . 100
Figure B.1 – XML text of the standard AML interface class library, role class library and
attribute type library . 104
Table – Meta information about the AML source tool .
Table – InterfaceClass PortConnector .
Table – Interface of the AML Port class .
Table – RoleClass PropertySet .
Table 1 – Abbreviations . 17
Table 2 – Interface classes of the AutomationMLInterfaceClassLib . 30
Table 3 – InterfaceClass AutomationMLBaseInterface . 32
Table 4 – InterfaceClass Order . 33
Table 5 – Optional attributes for AML Port interfaces . 34
Table 6 – InterfaceClass PPRConnector . 34
Table 7 – InterfaceClass ExternalDataConnector . 35
Table 8 – InterfaceClass COLLADAInterface . 35
Table 9 – InterfaceClass PLCopenXMLInterface . 36
Table 10 – InterfaceClass ExternalDataReference . 36
Table 11 – InterfaceClass Communication . 37
Table 12 – InterfaceClass SignalInterface . 37
Table 13 – RoleClass AutomationMLBaseRole . 40
Table 14 – RoleClass Group . 40
Table 15 – RoleClass Facet . 41
Table 16 – RoleClass Resource . 42
Table 17 – RoleClass Product . 43
Table 18 – RoleClass Process . 43
Table 19 – RoleClass Structure . 44
Table 20 – RoleClass ProductStructure . 44
Table 21 – RoleClass ProcessStructure . 44
Table 22 – RoleClass ResourceStructure . 45
Table 23 – RoleClass ExternalData . 45
Table 24 – Attribute Types of the AutomationMLBaseAttributeTypeLib . 47
Table 25 – Sub-attributes of the attribute “Cardinality” . 49
Table 26 – Sub-attributes of the attribute “AssociatedValue” . 49
Table A.1 – Overview of major extended AML concepts . 72
– 8 – IEC 62714-1:2018 RLV © IEC 2018
INTERNATIONAL ELECTROTECHNICAL COMMISSION
____________
ENGINEERING DATA EXCHANGE FORMAT FOR USE IN
INDUSTRIAL AUTOMATION SYSTEMS ENGINEERING –
AUTOMATION MARKUP LANGUAGE –
Part 1: Architecture and general requirements
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.
This redline version of the official IEC Standard allows the user to identify the changes
made to the previous edition. A vertical bar appears in the margin wherever a change
has been made. Additions are in green text, deletions are in strikethrough red text.
International Standard IEC 62714-1 has been prepared by subcommittee 65E: Devices and
integration in enterprise systems, of IEC technical committee 65: Industrial-process meas-
urement, control and automation.
This second edition cancels and replaces the first edition published in 2014. This edition
constitutes a technical revision.
This edition includes the following significant technical changes with respect to the previous
edition:
a) use of CAEX 3.0 according to IEC 62424:2016 which provides technical improvements as
attribute libraries, nested interfaces, new fields for indicating the source of an object, a
refinement of the mirror concept and native support of multiple roles, native meta
information about the CAEX file source tool, identification of instances via unique IDs
instead of pathes, etc.,
b) improved modelling of references to documents outside of the scope of the present
standard,
c) modelling of references between CAEX attributes and items in external documents,
e.g. within an Excel sheet,
d) revised role libraries,
e) modified Port concept,
f) modelling of multilingual expressions,
g) modelling of structured attribute lists or array,
h) a new AML container format,
i) a new standard AML attribute library.
The text of this International Standard is based on the following documents:
FDIS Report on voting
65E/582/FDIS 65E/586/RVD
Full information on the voting for the approval of this International Standard can be found in
the report on voting indicated in the above table.
This document has been drafted in accordance with the ISO/IEC Directives, Part 2.
A list of all parts in the IEC 62714 series, published 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.
– 10 – IEC 62714-1:2018 RLV © IEC 2018
The committee has decided that the contents of this document will remain unchanged until the
stability date indicated on the IEC website under "http://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 publication 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.
INTRODUCTION
IEC 62714 is a solution for data exchange focusing on the domain of automation engineering.
The data exchange format defined in the IEC 62714 series (Automation Markup Language,
AML) is an XML schema based data format for plant engineering data. AML and has been
developed in order to support the data exchange in a heterogeneous engineering tools
landscape. The goal of AML is to interconnect engineering tools in their different disciplines,
e.g. mechanical plant engineering, electrical design, process engineering, process control
engineering, HMI development, PLC programming, robot programming, etc. The application of
IEC 62714 is industry independent. It is applicable in all industries that require data exchange
in their engineering tool chain, e.g. in discrete industry or process industry.
AML stores engineering information following the object-oriented paradigm and allows
modelling of physical and logical plant components as data objects encapsulating different
aspects. An object may consist of other sub-objects, and may can itself be part of a larger
composition or aggregation. Typical objects in plant automation comprise information on
topology, geometry, kinematics and logic, whereas logic comprises sequencing, behaviour
and control. Therefore, an important focus in the data exchange in engineering is the
exchange of object oriented data structures, geometry, kinematics and logic.
AML combines existing industry data formats that are designed for the storage and exchange
of different aspects of engineering information. These data formats are used on an “as-is”
basis within their own specifications and are not branched for AML needs.
The core of AML is the top-level data format CAEX that connects. CAEX is utilized to
interconnect the different data formats. Therefore, AML has an inherent distributed document
architecture.
Figure 1 illustrates the basic AML architecture and the distribution of topology, geometry,
kinematics and logic information.
IEC
Figure 1 – Overview of the engineering data exchange format AML
Due to the different aspects of AML, the IEC 62714 series consists of different parts focusing
on different aspects:
• IEC 62714-1: Architecture and general requirements
This part specifies the general AML architecture, the modelling of engineering data,
classes, instances, relations, references, hierarchies, basic AML libraries and extended
AML concepts. It is the basis of all future parts, and it provides mechanisms to reference
other subformats.
– 12 – IEC 62714-1:2018 RLV © IEC 2018
• IEC 62714-2: Role class libraries
This part is intended to specify specifies additional AML libraries.
• IEC 62714-3: Geometry and kinematics
This part is intended to specify specifies the modelling of geometry and kinematics
information.
• IEC 62714-4 : Logic
This part is intended to specify specifies the modelling of logics, sequencing, behaviour
and control related information.
Further parts may will be added in the future in order to interconnect further data standards to
AML.
As long as no further parts describe the integration of further standards, it is important to
focus on a limited set of sub data formats. Otherwise, it would open up the usage of any data
format and data exchange would not work.
Clause 1 defines the scope for IEC 62714.
Clause 2 provides normative references.
Clause 3 provides terms, definitions and abbreviations.
Clause 4 defines the conformity to IEC 62714.
Clause 5 describes general architecture specifications for IEC 62714.
Clause 6 defines the basic AML libraries.
Clause 7 describes how to model user-defined data.
Clause 8 describes extended AML concepts.
Annex A gives an informative introduction, use cases and examples regarding AML.
Annex B gives an informative XML representation of the libraries defined in this part of
IEC 62714.
____________
Under consideration.
ENGINEERING DATA EXCHANGE FORMAT FOR USE IN
INDUSTRIAL AUTOMATION SYSTEMS ENGINEERING –
AUTOMATION MARKUP LANGUAGE –
Part 1: Architecture and general requirements
1 Scope
This part of IEC 62714 specifies general requirements and the architecture of automation
markup language (AML) for the modelling of engineering information, which is exchanged
between engineering tools for industrial automation and control systems. Its provisions apply
to the export/import applications of related tools.
This part of IEC 62714 does not define details of the data exchange procedure or
implementation requirements for the import/export tools.
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 62424:2008 2016, Representation of process control engineering – Requests in P&I
diagrams and data exchange between P&ID tools and PCE-CAE tools
IEC 62714 (all parts), Engineering data exchange format for use in industrial automation
systems engineering – Automation markup language
ISO/IEC 9834-8, Information technology – Open Systems Interconnection – Procedures for
the operation of OSI Registration Authorities: Generation and registration of Universally
Unique Identifiers (UUIDs) and their use as ASN.1 Object Identifier components
ISO/PAS 17506, Industrial automation systems and integration – COLLADA digital asset
schema specification for 3D visualization of industrial data
ISO/IEC 29500-2, Information technology – Document description and processing languages
– Office Open XML File Formats – Part 2: Open Packaging Conventions
IETF RFC 2046, Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types
[viewed 2017-11-13]. Available at
IETF RFC 4122, A Universally Unique Identifier (UUID) URN Namespace
[viewed 2017-11-13]. Available at
IETF RFC 5646, Tags for Identifying Languages
[viewed 2017-11-13]. Available at
COLLADA 1.4.1:March 2008, COLLADA – Digital Asset Schema Release 1.4.1
[viewed 2017-11-13]. Available at
– 14 – IEC 62714-1:2018 RLV © IEC 2018
Extensible Markup Language (XML) 1.0 1.0:2004, W3C Recommendation
(available at )
PLCopen XML 2.0:December 3rd 2008 and PLCopen XML 2.0.1:May 8th 2009, XML formats
for IEC 61131-3 [viewed 2017-11-13]. Available at
3 Terms, definitions and abbreviations
3.1 Terms and definitions
For the purposes of this document, the following terms and definitions 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
AML
XML based data exchange format for plant engineering data following IEC 62714
3.1.2
automation object
physical or logical entity in the automated system
Note 1 to entry
...
IEC 62714-1 ®
Edition 2.0 2018-04
INTERNATIONAL
STANDARD
NORME
INTERNATIONALE
colour
inside
Engineering data exchange format for use in industrial automation systems
engineering – Automation markup language –
Part 1: Architecture and general requirements
Format d’échange de données techniques pour une utilisation dans l’ingénierie
des systèmes d'automatisation industrielle – Automation markup language –
Partie 1: Architecture et exigences générales
All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized in any form
or by any means, electronic or mechanical, including photocopying and microfilm, without permission in writing from
either IEC or IEC's member National Committee in the country of the requester. If you have any questions about IEC
copyright or have an enquiry about obtaining additional rights to this publication, please contact the address below or
your local IEC member National Committee for further information.
Droits de reproduction réservés. Sauf indication contraire, aucune partie de cette publication ne peut être reproduite
ni utilisée sous quelque forme que ce soit et par aucun procédé, électronique ou mécanique, y compris la photocopie
et les microfilms, sans l'accord écrit de l'IEC ou du Comité national de l'IEC du pays du demandeur. Si vous avez des
questions sur le copyright de l'IEC ou si vous désirez obtenir des droits supplémentaires sur cette publication, utilisez
les coordonnées ci-après ou contactez le Comité national de l'IEC de votre pays de résidence.
IEC Central Office Tel.: +41 22 919 02 11
3, rue de Varembé info@iec.ch
CH-1211 Geneva 20 www.iec.ch
Switzerland
About the IEC
The International Electrotechnical Commission (IEC) is the leading global organization that prepares and publishes
International Standards for all electrical, electronic and related technologies.
About IEC publications
The technical content of IEC publications is kept under constant review by the IEC. Please make sure that you have the
latest edition, a corrigenda or an amendment might have been published.
IEC Catalogue - webstore.iec.ch/catalogue Electropedia - www.electropedia.org
The stand-alone application for consulting the entire The world's leading online dictionary of electronic and
bibliographical information on IEC International Standards, electrical terms containing 21 000 terms and definitions in
Technical Specifications, Technical Reports and other English and French, with equivalent terms in 16 additional
documents. Available for PC, Mac OS, Android Tablets and languages. Also known as the International Electrotechnical
iPad. Vocabulary (IEV) online.
IEC publications search - webstore.iec.ch/advsearchform IEC Glossary - std.iec.ch/glossary
The advanced search enables to find IEC publications by a 67 000 electrotechnical terminology entries in English and
variety of criteria (reference number, text, technical French extracted from the Terms and Definitions clause of
committee,…). It also gives information on projects, replaced IEC publications issued since 2002. Some entries have been
and withdrawn publications. collected from earlier publications of IEC TC 37, 77, 86 and
CISPR.
IEC Just Published - webstore.iec.ch/justpublished
Stay up to date on all new IEC publications. Just Published IEC Customer Service Centre - webstore.iec.ch/csc
details all new publications released. Available online and If you wish to give us your feedback on this publication or
also once a month by email. need further assistance, please contact the Customer Service
Centre: sales@iec.ch.
A propos de l'IEC
La Commission Electrotechnique Internationale (IEC) est la première organisation mondiale qui élabore et publie des
Normes internationales pour tout ce qui a trait à l'électricité, à l'électronique et aux technologies apparentées.
A propos des publications IEC
Le contenu technique des publications IEC est constamment revu. Veuillez vous assurer que vous possédez l’édition la
plus récente, un corrigendum ou amendement peut avoir été publié.
Catalogue IEC - webstore.iec.ch/catalogue Electropedia - www.electropedia.org
Application autonome pour consulter tous les renseignements
Le premier dictionnaire en ligne de termes électroniques et
bibliographiques sur les Normes internationales,
électriques. Il contient 21 000 termes et définitions en anglais
Spécifications techniques, Rapports techniques et autres
et en français, ainsi que les termes équivalents dans 16
documents de l'IEC. Disponible pour PC, Mac OS, tablettes
langues additionnelles. Egalement appelé Vocabulaire
Android et iPad.
Electrotechnique International (IEV) en ligne.
Recherche de publications IEC -
Glossaire IEC - std.iec.ch/glossary
webstore.iec.ch/advsearchform
67 000 entrées terminologiques électrotechniques, en anglais
La recherche avancée permet de trouver des publications IEC et en français, extraites des articles Termes et Définitions des
en utilisant différents critères (numéro de référence, texte, publications IEC parues depuis 2002. Plus certaines entrées
comité d’études,…). Elle donne aussi des informations sur les antérieures extraites des publications des CE 37, 77, 86 et
projets et les publications remplacées ou retirées. CISPR de l'IEC.
IEC Just Published - webstore.iec.ch/justpublished Service Clients - webstore.iec.ch/csc
Restez informé sur les nouvelles publications IEC. Just Si vous désirez nous donner des commentaires sur cette
Published détaille les nouvelles publications parues. publication ou si vous avez des questions contactez-nous:
Disponible en ligne et aussi une fois par mois par email. sales@iec.ch.
IEC 62714-1 ®
Edition 2.0 2018-04
INTERNATIONAL
STANDARD
NORME
INTERNATIONALE
colour
inside
Engineering data exchange format for use in industrial automation systems
engineering – Automation markup language –
Part 1: Architecture and general requirements
Format d’échange de données techniques pour une utilisation dans l’ingénierie
des systèmes d'automatisation industrielle – Automation markup language –
Partie 1: Architecture et exigences générales
INTERNATIONAL
ELECTROTECHNICAL
COMMISSION
COMMISSION
ELECTROTECHNIQUE
INTERNATIONALE
ICS 25.040.40; 35.060; 35.240.50 ISBN 978-2-8322-5521-6
– 2 – IEC 62714-1:2018 © IEC 2018
CONTENTS
FOREWORD . 7
INTRODUCTION . 9
1 Scope . 11
2 Normative references . 11
3 Terms, definitions and abbreviations . 12
3.1 Terms and definitions . 12
3.2 Abbreviations . 14
4 Conformity . 15
5 AML architecture specification . 15
5.1 General . 15
5.2 General AML architecture . 15
5.3 Sub document versions and AML superior document information . 16
5.4 Meta information about the AML source tool . 17
5.5 AML relations specification . 18
5.5.1 General . 18
5.5.2 Class-instance-relations . 18
5.5.3 Instance-instance-relations . 18
5.5.4 Identification of objects . 20
5.6 AML document reference specification . 20
5.6.1 General . 20
5.6.2 Referencing COLLADA documents . 20
5.6.3 Referencing PLCopen XML documents . 20
5.6.4 Referencing additional documents in the scope of IEC 62714 (all parts) . 20
5.6.5 Referencing documents outside of the scope of IEC 62714 (all parts) . 20
5.6.6 Referencing CAEX attributes to items in external documents . 21
6 AML base libraries . 21
6.1 General . 21
6.2 General provisions . 21
6.3 AML interface class library – AutomationMLInterfaceClassLib . 22
6.3.1 General . 22
6.3.2 InterfaceClass AutomationMLBaseInterface . 24
6.3.3 InterfaceClass Order . 24
6.3.4 InterfaceClass Port . 25
6.3.5 InterfaceClass PPRConnector . 25
6.3.6 InterfaceClass ExternalDataConnector . 26
6.3.7 InterfaceClass COLLADAInterface . 26
6.3.8 InterfaceClass PLCopenXMLInterface . 27
6.3.9 InterfaceClass ExternalDataReference . 27
6.3.10 InterfaceClass Communication . 27
6.3.11 InterfaceClass SignalInterface . 28
6.4 AML basic role class library – AutomationMLBaseRoleClassLib . 28
6.4.1 General . 28
6.4.2 RoleClass AutomationMLBaseRole . 30
6.4.3 RoleClass Group . 31
6.4.4 RoleClass Facet . 31
6.4.5 RoleClass Resource . 31
6.4.6 RoleClass Product . 32
6.4.7 RoleClass Process . 32
6.4.8 RoleClass Structure . 33
6.4.9 RoleClass ProductStructure . 33
6.4.10 RoleClass ProcessStructure . 34
6.4.11 RoleClass ResourceStructure . 34
6.4.12 RoleClass ExternalData . 34
6.5 AML basic attribute type library . 35
6.5.1 General . 35
6.5.2 Attributes of the AutomationMLBaseAttributeTypeLib . 36
7 Modelling of user-defined data . 39
7.1 General . 39
7.2 User-defined attributes. 39
7.3 User-defined AttributeTypes . 39
7.4 User-defined InterfaceClasses . 40
7.5 User-defined RoleClasses . 41
7.6 User-defined SystemUnitClasses . 42
7.7 User-defined InstanceHierarchies . 43
8 Extended AML concepts . 44
8.1 General overview . 44
8.2 AML Port interface . 44
8.3 AML Facet object . 44
8.4 AML Group object . 45
8.5 Splitting of AML top-level data into different documents . 45
8.6 Internationalization, AML multilingual expression . 45
8.7 Version information of AML objects . 46
8.8 Modelling of structured attribute lists or arrays . 46
8.9 AML Container . 46
Annex A (informative) General introduction into the Automation Markup Language . 48
A.1 General Automation Markup Language concepts . 48
A.1.1 The Automation Markup Language architecture . 48
A.1.2 Modelling of plant topology information . 49
A.1.3 Referencing geometry and kinematics information . 51
A.1.4 Referencing logic information . 51
A.1.5 Referencing documents outside of the scope of IEC 62714 . 52
A.1.6 Interlinking CAEX attributes and attributes in external documents . 53
A.1.7 Modelling of relations. 54
A.2 Extended AML concepts and examples . 57
A.2.1 General overview . 57
A.2.2 AML Port concept . 57
A.2.3 AML Facet concept . 60
A.2.4 AML Group concept . 62
A.2.5 Process-Product-Resource concept . 66
A.2.6 AML multilingual expression concept . 74
A.2.7 Attribute lists and arrays . 75
Annex B (informative) XML representation of standard AML base libraries . 79
Bibliography . 81
– 4 – IEC 62714-1:2018 © IEC 2018
Figure 1 – Overview of the engineering data exchange format AML . 9
Figure 2 – AML document version information . 17
Figure 3 – XML text of the AML source tool information . 17
Figure 4 – Example of a relation as block diagram and as object tree . 19
Figure 5 – Example relation between the objects “PLC1” and “Rob1” . 19
Figure 6 – XML text of the example relation between the objects “PLC1” and “Rob1” . 19
Figure 7 – AML basic interface class library . 23
Figure 8 – XML description of the AML basic interface class library . 24
Figure 9 – AML basic role class library. 29
Figure 10 – AutomationMLBaseRoleClassLib . 30
Figure 11 – XML text of the AutomationMLBaseRoleClassLib . 30
Figure 12 – AML basic attribute type library . 35
Figure 13 – XML text of the AutomationMLBaseAttributeTypeLib . 36
Figure 14 – Example of a user-defined attribute . 39
Figure 15 – Examples for user-defined AttributeTypes . 40
Figure 16 – XML code of the examples for user-defined AttributeTypes . 40
Figure 17 – Example of a user-defined InterfaceClass in a user-defined
InterfaceClassLib . 41
Figure 18 – XML code of the example of a user-defined InterfaceClass in a user-
defined InterfaceClassLib . 41
Figure 19 – Example of a user-defined RoleClass in a user-defined RoleClassLib . 42
Figure 20 – XML code of the example of a user-defined RoleClass in a user-defined
RoleClassLib . 42
Figure 21 – Examples for different user-defined SystemUnitClasses . 42
Figure 22 – XML code of the examples for different user-defined SystemUnitClasses . 43
Figure 23 – Example of a user-defined InstanceHierarchy . 43
Figure 24 – AML representation of a user-defined InstanceHierarchy . 44
Figure A.1 – AML general architecture . 48
Figure A.2 – Plant topology with AML . 50
Figure A.3 – Reference from CAEX to a COLLADA document . 51
Figure A.4 – Reference from a CAEX to a PLCopen XML document . 51
Figure A.5 – Example of referencing an external document . 52
Figure A.6 – XML text of the example for referencing an external document . 52
Figure A.7 – Example of referencing a CAEX attribute to an item in an external
document . 53
Figure A.8 – XML text of the example for referencing a CAEX attribute to an item in an
external document . 54
Figure A.9 – Relations in AML . 55
Figure A.10 – XML description of the relations example . 56
Figure A.11 – XML text of the SystemUnitClassLib of the relations example . 56
Figure A.12 – XML text of the InstanceHierarchy of the relations example . 57
Figure A.13 – Port concept . 58
Figure A.14 – Example describing the AML Port concept . 58
Figure A.15 – XML description of the AML Port concept . 59
Figure A.16 – XML text describing the AML Port concept . 60
Figure A.17 – Definition of a user-defined AML Port class “UserDefinedPort” . 60
Figure A.18 – AML Facet example . 61
Figure A.19 – XML text of the AML Facet example . 62
Figure A.20 – AML Group example . 63
Figure A.21 – XML text for the AML Group example . 63
Figure A.22 – Combination of the Facet and Group concept . 64
Figure A.23 – XML text view for the combined Facet-Group example . 65
Figure A.24 – Generic HMI template “B” visualizing a process variable “Y” of a
conveyor . 66
Figure A.25 – Generated HMI result “B” visualizing both conveyors with individual
process variables . 66
Figure A.26 – Base elements of the Product-Process-Resource concept . 67
Figure A.27 – PPRConnector interface. 67
Figure A.28 – Example for the Product-Process-Resource concept . 68
Figure A.29 – AML roles required for the Process-Product-Resource concept . 68
Figure A.30 – Elements of the example . 69
Figure A.31 – Links within the example . 69
Figure A.32 – Links of the resource centric view on the example . 70
Figure A.33 – InstanceHierarchy of the example in AML . 71
Figure A.34 – InternalElements of the example . 72
Figure A.35 – InternalLinks of the example . 72
Figure A.36 – InstanceHierarchy of the example in XML . 73
Figure A.37 – Example describing the AML multilingual expression concept . 74
Figure A.38 – XML description of the AML multilingual expression concept . 74
Figure A.39 – XML text describing the AML multilingual expression concept . 74
Figure A.40 – AML model of a multilingual AttributeType . 75
Figure A.41 – XML code of the a multilingual AttributeType . 75
Figure A.42 – Attribute list “SupportedFrequencies” . 76
Figure A.43 – XML code for the attribute list “SupportedFrequencies” . 76
Figure A.44 – Example CAEX model of the array “Edges” . 77
Figure A.45 – XML code for the attribute array “Edges” . 78
Figure B.1 – XML text of the standard AML interface class library, role class library and
attribute type library . 80
Table 1 – Abbreviations . 15
Table 2 – Interface classes of the AutomationMLInterfaceClassLib . 22
Table 3 – InterfaceClass AutomationMLBaseInterface . 24
Table 4 – InterfaceClass Order . 25
Table 5 – Optional attributes for AML Port interfaces . 25
Table 6 – InterfaceClass PPRConnector . 26
Table 7 – InterfaceClass ExternalDataConnector . 26
Table 8 – InterfaceClass COLLADAInterface . 26
Table 9 – InterfaceClass PLCopenXMLInterface . 27
Table 10 – InterfaceClass ExternalDataReference . 27
– 6 – IEC 62714-1:2018 © IEC 2018
Table 11 – InterfaceClass Communication . 28
Table 12 – InterfaceClass SignalInterface . 28
Table 13 – RoleClass AutomationMLBaseRole . 31
Table 14 – RoleClass Group . 31
Table 15 – RoleClass Facet . 31
Table 16 – RoleClass Resource . 32
Table 17 – RoleClass Product . 32
Table 18 – RoleClass Process . 33
Table 19 – RoleClass Structure . 33
Table 20 – RoleClass ProductStructure . 33
Table 21 – RoleClass ProcessStructure . 34
Table 22 – RoleClass ResourceStructure . 34
Table 23 – RoleClass ExternalData . 34
Table 24 – Attribute Types of the AutomationMLBaseAttributeTypeLib . 36
Table 25 – Sub-attributes of the attribute “Cardinality” . 38
Table 26 – Sub-attributes of the attribute “AssociatedValue” . 38
Table A.1 – Overview of major extended AML concepts . 57
INTERNATIONAL ELECTROTECHNICAL COMMISSION
____________
ENGINEERING DATA EXCHANGE FORMAT FOR USE IN
INDUSTRIAL AUTOMATION SYSTEMS ENGINEERING –
AUTOMATION MARKUP LANGUAGE –
Part 1: Architecture and general requirements
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 62714-1 has been prepared by subcommittee 65E: Devices and
integration in enterprise systems, of IEC technical committee 65: Industrial-process meas-
urement, control and automation.
This second edition cancels and replaces the first edition published in 2014. This edition
constitutes a technical revision.
This edition includes the following significant technical changes with respect to the previous
edition:
a) use of CAEX 3.0 according to IEC 62424:2016 which provides technical improvements as
attribute libraries, nested interfaces, new fields for indicating the source of an object, a
refinement of the mirror concept and native support of multiple roles, native meta
information about the CAEX file source tool, identification of instances via unique IDs
instead of pathes, etc.,
– 8 – IEC 62714-1:2018 © IEC 2018
b) improved modelling of references to documents outside of the scope of the present
standard,
c) modelling of references between CAEX attributes and items in external documents,
e.g. within an Excel sheet,
d) revised role libraries,
e) modified Port concept,
f) modelling of multilingual expressions,
g) modelling of structured attribute lists or array,
h) a new AML container format,
i) a new standard AML attribute library.
The text of this International Standard is based on the following documents:
FDIS Report on voting
65E/582/FDIS 65E/586/RVD
Full information on the voting for the approval of this International Standard can be found in
the report on voting indicated in the above table.
This document has been drafted in accordance with the ISO/IEC Directives, Part 2.
A list of all parts in the IEC 62714 series, published 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 "http://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 publication 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.
INTRODUCTION
IEC 62714 is a solution for data exchange focusing on the domain of automation engineering.
The data exchange format defined in the IEC 62714 series (Automation Markup Language,
AML) is an XML schema based data format for plant engineering data. AML and has been
developed in order to support the data exchange in a heterogeneous engineering tools
landscape. The goal of AML is to interconnect engineering tools in their different disciplines,
e.g. mechanical plant engineering, electrical design, process engineering, process control
engineering, HMI development, PLC programming, robot programming, etc. The application of
IEC 62714 is industry independent. It is applicable in all industries that require data exchange
in their engineering tool chain, e.g. in discrete industry or process industry.
AML stores engineering information following the object-oriented paradigm and allows
modelling of physical and logical plant components as data objects encapsulating different
aspects. An object may consist of other sub-objects, and can itself be part of a larger
composition or aggregation. Typical objects in plant automation comprise information on
topology, geometry, kinematics and logic, whereas logic comprises sequencing, behaviour
and control. Therefore, an important focus in the data exchange in engineering is the
exchange of object oriented data structures, geometry, kinematics and logic.
AML combines existing industry data formats that are designed for the storage and exchange
of different aspects of engineering information. These data formats are used on an “as-is”
basis within their own specifications and are not branched for AML needs.
The core of AML is the top-level data format CAEX. CAEX is utilized to interconnect the
different data formats. Therefore, AML has an inherent distributed document architecture.
Figure 1 illustrates the basic AML architecture and the distribution of topology, geometry,
kinematics and logic information.
IEC
Figure 1 – Overview of the engineering data exchange format AML
Due to the different aspects of AML, the IEC 62714 series consists of different parts focusing
on different aspects:
• IEC 62714-1: Architecture and general requirements
This part specifies the general AML architecture, the modelling of engineering data,
classes, instances, relations, references, hierarchies, basic AML libraries and extended
AML concepts. It is the basis of all future parts, and it provides mechanisms to reference
other subformats.
– 10 – IEC 62714-1:2018 © IEC 2018
• IEC 62714-2: Role class libraries
This part specifies additional AML libraries.
• IEC 62714-3: Geometry and kinematics
This part specifies the modelling of geometry and kinematics information.
• IEC 62714-4 : Logic
This part specifies the modelling of logics, sequencing, behaviour and control related
information.
Further parts will be added in the future in order to interconnect further data standards to
AML.
As long as no further parts describe the integration of further standards, it is important to
focus on a limited set of sub data formats. Otherwise, it would open up the usage of any data
format and data exchange would not work.
Clause 1 defines the scope for IEC 62714.
Clause 2 provides normative references.
Clause 3 provides terms, definitions and abbreviations.
Clause 4 defines the conformity to IEC 62714.
Clause 5 describes general architecture specifications for IEC 62714.
Clause 6 defines the basic AML libraries.
Clause 7 describes how to model user-defined data.
Clause 8 describes extended AML concepts.
Annex A gives an informative introduction, use cases and examples regarding AML.
Annex B gives an informative XML representation of the libraries defined in this part of
IEC 62714.
____________
Under consideration.
ENGINEERING DATA EXCHANGE FORMAT FOR USE IN
INDUSTRIAL AUTOMATION SYSTEMS ENGINEERING –
AUTOMATION MARKUP LANGUAGE –
Part 1: Architecture and general requirements
1 Scope
This part of IEC 62714 specifies general requirements and the architecture of automation
markup language (AML) for the modelling of engineering information, which is exchanged
between engineering tools for industrial automation and control systems. Its provisions apply
to the export/import applications of related tools.
This part of IEC 62714 does not define details of the data exchange procedure or
implementation requirements for the import/export tools.
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 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 (all parts), Engineering data exchange format for use in industrial automation
systems engineering – Automation markup language
ISO/PAS 17506, Industrial automation systems and integration – COLLADA digital asset
schema specification for 3D visualization of industrial data
ISO/IEC 29500-2, Information technology – Document description and processing languages
– Office Open XML File Formats – Part 2: Open Packaging Conventions
IETF RFC 2046, Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types
[viewed 2017-11-13]. Available at
IETF RFC 4122, A Universally Unique Identifier (UUID) URN Namespace
[viewed 2017-11-13]. Available at
IETF RFC 5646, Tags for Identifying Languages
[viewed 2017-11-13]. Available at
COLLADA 1.4.1:March 2008, COLLADA – Digital Asset Schema Release 1.4.1
[viewed 2017-11-13]. Available at
PLCopen XML 2.0:December 3rd 2008 and PLCopen XML 2.0.1:May 8th 2009, XML formats
for IEC 61131-3 [viewed 2017-11-13]. Available at
– 12 – IEC 62714-1:2018 © IEC 2018
3 Terms, definitions and abbreviations
3.1 Terms and definitions
For the purposes of this document, the following terms and definitions 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
AML
XML based data exchange format for plant engineering data following IEC 62714
3.1.2
automation object
physical or logical entity in the automated system
Note 1 to entry: An example of an automation object is an automation component, a valve or a signal.
3.1.3
AML object
data representation of an automation object with one or more CAEX RoleRequirements that
relate to an AML role class
Note 1 to entry: The AML objects are the core elements of AML. They represent instances and may contain
administration items, attributes, interfaces, relations and references.
3.1.4
AML class
predefined AML object type, either an AML system unit class, AML interface class, AML role
class or AML attribute type
Note 1 to entry: AML classes are stored within AML libraries, AML classes are of type SystemUnitClass,
InterfaceClass, RoleClass or AttributeType.
Note 2 to entry: AML classes define reusable sample solutions, characterized by attributes, interfaces and
aggregated objects.
Note 3 to entry: AML classes can be used for multiple instantiations.
Note 4 to entry: AML classes can be user-defined or standard AML classes.
3.1.5
AML attribute
CAEX attribute which belongs to an AML object and is related to an attribute defined in an
AML class or AML AttributeType
Note 1 to entry: AML attributes are described as an XML element corresponding to IEC 62424:2016, A.2.4.
3.1.6
AML document
certain AML CAEX document following IEC 62714 (all parts) including all referenced sub
documents
Note 1 to entry: AML documents may be stored as files, but also e.g. as string or data streams.
Note 2 to entry: AML documents contain AML objects and/or user-defined objects.
Note 3 to entry: An AML document may consist
...
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...