Shopping Cart

No products in the cart.

BS EN 62714-1:2014

$215.11

Engineering data exchange format for use in industrial automation systems engineering – Architecture and General Requirements

Published By Publication Date Number of Pages
BSI 2014 86
Guaranteed Safe Checkout
Categories: ,

If you have any questions, feel free to reach out to our online customer service team by clicking on the bottom right corner. We’re here to assist you 24/7.
Email:[email protected]

This part of IEC 62714 specifies general requirements and the architecture of 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.

PDF Catalog

PDF Pages PDF Title
6 English
CONTENTS
11 INTRODUCTION
Figures
Figure 1 – Overview of the engineering data exchange format AML
13 1 Scope
2 Normative references
3 Terms, definitions and abbreviations
3.1 Terms and definitions
16 3.2 Abbreviations
4 Conformity
Tables
Table 1 – Abbreviations
17 5 AML architecture specification
5.1 General
5.2 General AML architecture
18 5.3 AML document versions
Figure 2 – AML document version information
19 5.4 Meta information about the AML source tool
Table 2 – Meta information about the AML source tool
20 5.5 Object identification
Figure 3 – XML text of the AML source tool information
21 5.6 AML relations specification
5.6.1 General
5.6.2 Parent-child-relations between AML objects
Figure 4 – Object identification example of an AML class
Figure 5 – Object identification example of an AML object instance
22 5.6.3 Parent-child-relations between AML classes
Figure 6 – Example of a parent-child-relation between AML objects
Figure 7 – Example of a parent-child-relation between classes
23 5.6.4 Inheritance relations
5.6.5 Class-instance-relations
Figure 8 – Example of an inheritance relation between two classes
24 Figure 9 – Example of a class-instance-relation
25 5.6.6 Instance-instance-relations
Figure 10 – Example of a relation as block diagram and as object tree
26 Figure 11 – Example relation between the objects “PLC1” and “Rob1”
27 5.7 AML document reference specification
5.7.1 General
5.7.2 Referencing COLLADA documents
5.7.3 Referencing PLCopen XML documents
5.7.4 Referencing additional documents
6 AML base libraries
6.1 General
6.2 General provisions
28 6.3 AML interface class library – AutomationMLInterfaceClassLib
6.3.1 General
Table 3 – Interface classes of the AutomationMLInterfaceClassLib
29 Figure 12 – AML basic interface class library
30 6.3.2 InterfaceClass AutomationMLBaseInterface
6.3.3 InterfaceClass Order
Figure 13 – XML description of the AML basic interface class library
Table 4 – InterfaceClass AutomationMLBaseInterface
Table 5 – InterfaceClass Order
31 6.3.4 InterfaceClass PortConnector
6.3.5 InterfaceClass PPRConnector
6.3.6 InterfaceClass ExternalDataConnector
Table 6 – InterfaceClass PortConnector
Table 7 – InterfaceClass PPRConnector
Table 8 – InterfaceClass ExternalDataConnector
32 6.3.7 InterfaceClass COLLADAInterface
6.3.8 InterfaceClass PLCopenXMLInterface
6.3.9 InterfaceClass Communication
Table 9 – InterfaceClass COLLADAInterface
Table 10 – InterfaceClass PLCopenXMLInterface
33 6.3.10 InterfaceClass SignalInterface
6.4 AML basic role class library – AutomationMLBaseRoleClassLib
6.4.1 General
Table 11 – InterfaceClass Communication
Table 12 – InterfaceClass SignalInterface
34 Figure 14 – AML basic role class library
Figure 15 – AutomationMLBaseRoleClassLib
35 6.4.2 RoleClass AutomationMLBaseRole
6.4.3 RoleClass Group
Figure 16 – XML text of the AutomationMLBaseRoleClassLib
Table 13 – RoleClass AutomationMLBaseRole
36 6.4.4 RoleClass Facet
6.4.5 RoleClass Port
Table 14 – RoleClass Group
Table 15 – RoleClass Facet
37 Table 16 – Optional attributes for AML Port objects
Table 17 – Sub-attributes of the attribute “Cardinality”
38 6.4.6 RoleClass Resource
6.4.7 RoleClass Product
Table 18 – Interface of the AML Port class
Table 19 – RoleClass Resource
Table 20 – RoleClass Product
39 6.4.8 RoleClass Process
6.4.9 RoleClass Structure
6.4.10 RoleClass ProductStructure
Table 21 – RoleClass Process
Table 22 – RoleClass Structure
Table 23 – RoleClass ProductStructure
40 6.4.11 RoleClass ProcessStructure
6.4.12 RoleClass ResourceStructure
6.4.13 RoleClass PropertySet
Table 24 – RoleClass ProcessStructure
Table 25 – RoleClass ResourceStructure
Table 26 – RoleClass PropertySet
41 7 Modelling of user-defined data
7.1 General
7.2 User-defined attributes
7.3 User-defined InterfaceClasses
Figure 17 – Example of a user-defined attribute
42 7.4 User-defined RoleClasses
Figure 18 – Example of a user-defined InterfaceClass in a user-defined InterfaceClassLib
43 7.5 User-defined SystemUnitClasses
7.6 User-defined InstanceHierarchies
Figure 19 – Example of a user-defined RoleClass in a user-defined RoleClassLib
Figure 20 – Examples for different user-defined SystemUnitClasses
44 8 Extended AML concepts
8.1 General overview
8.2 AML Port object
Figure 21 – Example of a user-defined InstanceHierarchy
Figure 22 – AML representation of a user-defined InstanceHierarchy
45 8.3 AML Facet object
8.4 AML Group object
46 8.5 AML PropertySet
47 Figure 23 – Example illustrating the PropertySet concept
48 8.6 Support of multiple roles
Figure 24 – XML text of the PropertySet example
49 8.7 Splitting of AML top-level data into different documents
8.8 Internationalization
8.9 Version information of AML objects
50 Annex A (informative) General introduction into the Automation Markup Language
A.1 General Automation Markup Language concepts
A.1.1 The Automation Markup Language architecture
Figure A.1 – AML general architecture
52 A.1.2 Modelling of plant topology information
Figure A.2 – Plant topology with AML
53 A.1.3 Referencing geometry and kinematics information
A.1.4 Referencing logic information
Figure A.3 – Reference from CAEX to a COLLADA document
54 A.1.5 Modelling of relations
Figure A.4 – Reference from a CAEX to a PLCopen XML document
55 Figure A.5 – Relations in AML
56 Figure A.6 – XML description of the relations example
Figure A.7 – XML text of the SystemUnitClassLib of the relations example
Figure A.8 – XML text of the InstanceHierarchy of the relations example
57 A.2 Extended AML concepts and examples
A.2.1 General overview
A.2.2 AML Port concept
Figure A.9 – Port concept
Table A.1 – Overview of major extended AML concepts
58 Figure A.10 – Example describing the AML Port concept
59 Figure A.11 – XML description of the AML Port concept
60 Figure A.12 – XML text describing the AML Port concept
Figure A.13 – Definition of a user-defined AML Port class “myPortClass”
61 A.2.3 AML Facet concept
62 Figure A.14 – AML Facet example
Figure A.15 – XML text of the AML Facet example
63 A.2.4 AML Group concept
Figure A.16 – AML Group example
64 Figure A.17 – XML text for the AML Group example
65 Figure A.18 – Combination of the Facet and Group concept
66 Figure A.19 – XML text view for the combined Facet-Group example
67 A.2.5 PropertySet concept
Figure A.20 – Generic HMI template “B” visualizing a process variable “Y” of a conveyor
Figure A.21 – Generated HMI result “B” visualizing both conveyors with individual process variables
68 Figure A.22 – PropertySet example
Figure A.23 – PropertySet example
69 Figure A.24 – XML text for the instance hierarchy
70 A.2.6 Process-Product-Resource concept
Figure A.25 – PropertySet example AML library as XML code
71 Figure A.26 – Base elements of the Product-Process-Resource concept
72 Figure A.27 – PPRConnector interface
Figure A.28 – Example for the Product-Process-Resource concept
73 Figure A.29 – AML roles required for the Process-Product-Resource concept
Figure A.30 – Elements of the example
74 Figure A.31 – Links within the example
75 Figure A.32 – Links of the resource centric view on the example
76 Figure A.33 – InstanceHierarchy of the example in AML
77 Figure A.34 – InternalElements of the example
Figure A.35 – InternalLinks of the example
78 A.2.7 Support of multiple roles
Figure A.36 – InstanceHierarchy of the example in XML
79 Figure A.37 – Example of a user-defined instance supporting multiple roles
80 Figure A.38 – XML text of the AML representation of multiple role support
Figure A.39 – AML Role class library correspondingto the multiple role definition example
81 Figure A.40 – XML text of the AML role class library
82 Annex B (informative) XML Representation of AML Libraries
B.1 AutomationMLBaseRoleClassLib
83 B.2 AutomationMLInterfaceClassLib
84 Bibliography
BS EN 62714-1:2014
$215.11