1、BSI Standards PublicationEngineering data exchange format for use in industrialautomation systems engineeringPart 1: Architecture and General RequirementsBS EN 62714-1:2014National forewordThis British Standard is the UK implementation of EN 62714-1:2014. It isidentical to IEC 62714-1:2014.The UK pa
2、rticipation in its preparation was entrusted to TechnicalCommittee AMT/7, Industrial communications: process measurement and control, including fieldbus.A list of organizations represented on this committee can be obtained onrequest to its secretary.This publication does not purport to include all t
3、he necessary provisions ofa contract. Users are responsible for its correct application. The British Standards Institution 2014.Published by BSI Standards Limited 2014ISBN 978 0 580 73983 5ICS 25.040.40; 35.060; 35.240.50Compliance with a British Standard cannot confer immunity fromlegal obligations
4、.This British Standard was published under the authority of theStandards Policy and Strategy Committee on 31 October 2014.Amendments/corrigenda issued since publicationDate Text affectedBRITISH STANDARDBS EN 62714-1:2014EUROPEAN STANDARDNORME EUROPENNEEUROPISCHE NORMEN 62714-1 October 2014 ICS 25.04
5、0.40; 35.060; 35.240.50 English Version Engineering data exchange format for use in industrial automation systems engineering - Part 1: Architecture andGeneral Requirements (IEC 62714-1:2014) Format dchange de donnes techniques pour uneutilisation dans lingnierie des systmes dautomatisationindustrie
6、lle - AutomationML - Partie 1: Architecture etexigences gnrales (CEI 62714-1:2014) Datenaustauschformat fr Planungsdaten industriellerAutomatisierungssysteme (AutomationML) - Teil 1: Architektur und allgemeine Festlegungen(IEC 62714-1:2014) This European Standard was approved by CENELEC on 2014-07-3
7、1. 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 obtain
8、ed 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
9、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, Former Yugoslav Republic of Macedonia, France, Germany, Greece, H
10、ungary, Iceland, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, the Netherlands, Norway, Poland, Portugal, Romania, Slovakia, Slovenia, Spain, Sweden, Switzerland, Turkey and the United Kingdom. European Committee for Electrotechnical Standardization Comit Europen de Normalisation Electrotech
11、niqueEuropisches Komitee fr Elektrotechnische Normung CEN-CENELEC Management Centre: Avenue Marnix 17, B-1000 Brussels 2014 CENELEC All rights of exploitation in any form and by any means reserved worldwide for CENELEC Members. Ref. No. EN 62714-1:2014 E EN 62714-1:2014 - 2 - Foreword The text of do
12、cument 65E/385/FDIS, future edition 1 of IEC 62714-1, 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 EN 62714-1:2014. The following date
13、s are fixed: latest date by which the document has to be implemented at national level by publication of an identical national standard or by endorsement (dop) 2015-05-01 latest date by which the national standards conflicting with the document have to be withdrawn (dow) 2017-07-31 Attention is draw
14、n to the possibility that some of the elements of this document may be the subject of patent rights. CENELEC and/or CEN shall not be held responsible for identifying any or all such patent rights. This document has been prepared under a mandate given to CENELEC by the European Commission and the Eur
15、opean Free Trade Association. Endorsement notice The text of the International Standard IEC 62714-1:2014 was approved by CENELEC as a European Standard without any modification. In the official version, for Bibliography, the following notes have to be added for the standards indicated: IEC 60027 (Se
16、ries) NOTE Harmonized as EN 60027 (Series). IEC 62264-1 NOTE Harmonized as EN 62264-1. IEC 62714-2 NOTE Harmonized as EN 62714-2 ISO 80000-1 NOTE Harmonized as EN ISO 80000-1. BS EN 62714-1:2014- 3 - EN 62714-1:2014 Annex ZA (normative) Normative references to international publications with their c
17、orresponding European publications The following documents, in whole or in part, are normatively referenced in this document and are indispensable for its application. For dated references, only the edition cited applies. For undated references, the latest edition of the referenced document (includi
18、ng any amendments) applies. NOTE 1 When 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. Publi
19、cation Year Title EN/HD Year IEC 62424 2008 Representation of process control engineering - Requests in P all changes shall be done at the master object. NOTE 1 According to IEC 62424:2008, A.2.14, an AML object with a relation to another AML object is called “mirror object” whereas the related AML
20、object is called “master object”. The mirror object is considered to be identical to the master object. This enables placing one object instance into different plant hierarchies and thus allows modelling of complex object networks with crossed structures. NOTE 2 IEC 62714 does not syntactically modi
21、fy the CAEX data format. An informative overview and additional examples regarding the plant topology are provided in A.1.2 and in IEC 62424:2008, Annex D. Reference and relation information: References and relations shall be stored according to 5.6 and 5.7. Relations between externally stored infor
22、mation shall be stored with CAEX mechanisms. If required, the related link partners shall be published in the CAEX plant topo-logy description by means of CAEX ExternalInterfaces. They shall be derived from AML standard interface classes specified in 6.3. NOTE 3 References depict links from CAEX obj
23、ects to externally stored information. An informative overview about relations is provided in A.1.5. References and publishing of interfaces are described in additional parts of IEC 62714. NOTE 4 Relations depict associations between CAEX objects. Geometry and kinematics information: Geometry and ki
24、nematics relevant information shall be stored using the data format COLLADA1. COLLADA interfaces that need to be intercon-nected within the top level format shall be published as CAEX ExternalInterfaces. NOTE 5 IEC 62714 does not syntactically modify the COLLADA data format. An overview example of h
25、ow to reference COLLADA is provided in A.1.3. Details are intended to be specified in IEC 62714-3. NOTE 6 By means of the COLLADA geometry information of different objects, a complete scene can be derived automatically. These files can be referenced from CAEX and can be interlinked using CAEX linkin
26、g mechanisms. Logic information: Logic information shall be stored using the data format PLCopen XML. If logic items, e.g. variables or signals, need to be interconnected within the top level format, they shall be published as CAEX ExternalInterfaces. All items of PLCopen XML that are pub-lished wit
27、hin the top level format shall have a unique ID within PLCopen XML. 1COLLADA is the trademark of a product supplied by the Khronos Group. This information is given for the convenience of users of this standard and does not constitute an endorsement by IEC of the product named. Equivalent products ma
28、y be used if they can be shown to lead to the same results. BS EN 62714-1:2014 16 IEC 62714-1:2014 IEC 2014 NOTE 7 Logic information describes sequences of actions and the internal behaviour of objects including I/O con-nections and logical variables. IEC 62714 does not modify the PLCopen XML format
29、. An informative overview of how to reference logic information is provided in A.1.4. Details are intended to be specified in IEC 62714-4. Referencing other data formats: IEC 62714 may be extended in the future by additional parts specifying the integration of further XML data formats utilizing the
30、AML reference mechanisms. Details may be defined in additional parts of IEC 62714. The data format AML does not provide consistency checks of constraints, attribute values, relations, references or the semantic correctness of the contained data: this is the respon-sibility of the source or target to
31、ol or the corresponding import/export application. AML only allows a syntactical proof of the document against the corresponding schemas. 5.3 AML document versions Each AML XML document shall store the underlying AML version which this standard follows. NOTE 1 Normative provisions regarding the vers
32、ion information related to AML object instances are defined in 8.9. The storage of tool specific meta information is defined in 5.4. Hence, the following provisions apply: The CAEX root element “CAEXFile” of each AML top level document shall have the CAEX child element “AdditionalInformation”. The e
33、lement “AdditionalInformation” shall have an attribute “AutomationMLVersion”. The value of this attribute “AutomationMLVersion” shall be stored in the XML document. It shall be “2.0” to correspond to this standard. Every referenced CAEX document shall follow the same AML version of the root docu-men
34、t. Mixing of documents with different AML versions is explicitly forbidden. Every referenced external document shall also follow the named schema versions speci-fied in the above AML version specification. Mixing of external document versions outside of one AML version specification is explicitly fo
35、rbidden. Figure 2 illustrates the XML text for a CAEX document following the AML version 2.0. Figure 2 AML document version information Every AML standard library and every user defined AML library shall define its version number utilizing the CAEX element “Version”. The syntax of the value of the v
36、ersion num-ber is not defined in this part of IEC 62714. If required, CAEX classes shall define their version number utilizing the CAEX element “Version”. The syntax and semantic of the version number of classes within an AML library is not defined in this part of IEC 62714. Same libraries of differ
37、ent versions are forbidden to be stored in the same AML file. NOTE 2 This ensures the uniqueness of AML library names within an AML file. The creator of an AML document shall ensure that only version compatible classes and external documents are referenced. IEC 62714 is based on the following docume
38、nt formats: CAEX version 2.15; PLCopenXML 2.0 and 2.0.1; COLLADA 1.5.0 as specified in ISO/PAS 17506 and COLLADA 1.4.1; BS EN 62714-1:2014IEC 62714-1:2014 IEC 2014 17 AML standard libraries as specified in this part of IEC 62714 and further parts of IEC 62714. 5.4 Meta information about the AML sour
39、ce tool In case of the need of a transfer of user defined data from a source tool to a destination tool, it is necessary to store information about the source tool directly into the AML document. Hence, the following provisions apply: Each AML document shall provide information about the tool which
40、has written the AML document. In a data exchange tool chain, all participating tools shall store this information in the CAEX document in the same way. Hence, the document may contain information about multiple tools of a data exchange tool chain. A tool may remove the writer information of other to
41、ols. This may hinder the iterative data exchange with the other tools: hence the removal of writer information of other tools is not recommended. This information shall be stored as part of the CAEX AdditionalInformation of the root object of the CAEX document. The AdditionalInfomation block shall b
42、e named “WriterHeader”. The meta information shall provide information about: the name of the exporting software, the writer tool; the ID of the writer tool (it shall remain unchanged); the vendor of the writer tool; the URL of the writer tool; the product version of the writer tool; the product rel
43、ease number of the writer tool; the last writing time of the writer; the project title of the source project; the project ID of the source project. The content of the meta information shall be defined by the writer tool and shall be of type xs:string. The required information shall be stored by mean
44、s of the attributes shown in Table 2. Table 2 Meta information about the AML source tool XML tag name Type Level Example WriterName xs:string Mandatory “ToolX AML Exporter” WriterID xs:string Mandatory “ToolXToAML123” WriterVendor xs:string Mandatory “ToolX Vendor” WriterVendorURL xs:string Mandator
45、y “http:/www.ToolX-Vendor.org” WriterVersion xs:string Mandatory “0.2” WriterRelease xs:string Mandatory “123 prealpha” LastWritingDateTime xs:DateTime Mandatory “2011-05-25T09:30:47” WriterProjectTitle xs:string Optional “eCarproduction” WriterProjectID xs:string Optional “eCarproduction_LinePLC.pr
46、j” For the XML representation of the meta information, the following provisions apply: The element “WriterHeader” shall be a child XML element of the CAEX element Addition-alInformation of the CAEX root element. BS EN 62714-1:2014 18 IEC 62714-1:2014 IEC 2014 Each meta information named in Table 2 s
47、hall be described as a child XML element of the “WriterHeader”. Multiple meta information of the same name are forbidden in the same “WriterHeader” element. The order of the meta information shall be equivalent to Table 2. Figure 3 illustrates the required XML text by means of an example. Figure 3 X
48、ML text of the AML source tool information 5.5 Object identification AML follows the object oriented paradigm. All engineering information is modelled as object or belongs to an object. But, in a heterogeneous tool landscape, different engineering tools use different concepts for the identification
49、of objects, e.g. a unique name, a unique identifier or a unique path. Some tools allow changes of the identifiers over the life time, others do not. IEC 62714 enables the data exchange between different engineering tools with such individual object identification concepts. Owing to the described characteristics, this part of IEC 62714 neutralizes this variety and defines one mandatory object identification concept. Regarding the object identification, the fol
