🔥🔥 Don’t Miss Out on Our End of Autumn Sale. If you have any questions, feel free to click the bottom right corner to contact our customer service..

Concat us[email protected]
Shopping Cart

No products in the cart.

🔍
BS EN IEC 62714-5:2022

BS EN IEC 62714-5:2022

$198.66

Engineering data exchange format for use in industrial automation systems engineering. Automation markup language – Communication

Published By Publication Date Number of Pages
BSI 2022 68
PDF Format Searchable Printable Preview Now
Guaranteed Safe Checkout
Category:

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]

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.

PDF Catalog

PDF Pages PDF Title
2 undefined
7 Annex ZA (normative)Normative references to international publicationswith their corresponding European publications
12 English
CONTENTS
16 FOREWORD
18 1 Scope
2 Normative references
19 3 Terms, definitions, abbreviated terms and acronyms
3.1 Terms and definitions
3.2 Abbreviated terms and acronyms
20 4 Use cases and network structures
4.1 General
4.2 Use cases
4.2.1 Engineering activities
Figures
Figure 1 – General engineering activities communicationsystem engineering is embedded within
21 4.2.2 Lossless transfer of communication device instance information
22 Figure 2 – Information flow of the use case
23 Figure 3 – Alternative information flow of the use case
24 4.2.3 Lossless transfer of communication system information
25 Figure 4 – Information flow of the use case
26 4.3 Delimitation of modelling range
4.3.1 Scope of the modelling range
4.3.2 Interaction structures and life cycles
27 4.3.3 Network objects
Figure 5 – Example of a logical level view on communication systems
28 4.3.4 Network topologies
Figure 6 – Example of a physical level view on communication systems
Figure 7 – Combined views on communication systems
29 Figure 8 – Star topology example
Figure 9 – Ring topology example
30 Figure 10 – Line topology example
Figure 11 – Simple network with direct wiring
31 Figure 12 – Network with active infrastructure
Figure 13 – Networks connected by gateways
32 Figure 14 – Hierarchical structured networks
Figure 15 – Network covering multiple applications
33 4.3.5 Communication content
4.4 Derived modelling requirements
Figure 16 – General modelling strategy for PDUs
34 5 UML model
5.1 Overview
5.2 Logical topology
5.2.1 Aim of logical topology
Figure 17 – Structure of communication network
35 5.2.2 Item logicalTopology
5.2.3 Item logicalConnection
5.2.4 Item logicalEndPoint
Figure 18 – View on logical topology
36 5.3 Physical topology
5.3.1 Aim of physical topology
5.3.2 Item physicalTopology
5.3.3 Item physicalConnection
Figure 19 – View on physical topology
37 5.3.4 Item physicalEndPoint
5.4 Device
5.4.1 General
5.4.2 Item physicalDevice
38 5.4.3 Item Information
Figure 20 – Part 1 of the device model
39 5.4.4 Item physicalDeviceInformation
5.4.5 Item logicalDeviceInformation
5.4.6 Item logicalDevice
5.4.7 Item networkDataList
5.4.8 Item networkDataItem
5.4.9 Item logicalEndPointList
5.4.10 Item physicalEndPointList
5.4.11 Item physicalChannelList
40 5.4.12 Item physicalChannel
5.4.13 Item deviceResource
5.4.14 Item variableList
5.4.15 Item variable
41 5.4.16 Item pduList
5.4.17 Item pdu
Figure 21 – Part 2 of the device model
42 5.4.18 Item protocolData
5.4.19 Item payload
5.4.20 Item processDataItemList
5.4.21 Item parameterItemList
5.4.22 Item dataItem
5.4.23 Item processDataItem
43 5.4.24 Item processDataInput
5.4.25 Item processDataOutput
5.4.26 Item parameterItem
6 Representation within AutomationML
6.1 Overview of mapping
6.1.1 Introduction of mapping
6.1.2 General mapping rules
44 6.1.3 Basics
Tables
Table 1 – Mapping rules
45 6.1.4 Modelling of relations
Figure 22 – Communication role class library and communication interface class library
Figure 23 – Derived role class libraries and interface class libraries for a special example
46 6.1.5 Application process
Table 2 – Modelling of relations in AutomationML
47 Figure 24 – SystemUnitClassLib examples for communication system modelling
48 6.2 Basic communication role class library
6.2.1 General
Figure 25 – Final network model example
49 6.2.2 RoleClass PhysicalDevice
Figure 26 – Basic communication role class library
Figure 27 – CommunicationRoleClassLib
Figure 28 – XML text of the communication role class library
50 6.2.3 RoleClass PhysicalEndpointlist
6.2.4 RoleClass PhysicalConnection
6.2.5 RoleClass PhysicalNetwork
Table 3 – RoleClass PhysicalDevice
Table 4 – RoleClass PhysicalEndpointlist
Table 5 – RoleClass PhysicalConnection
Table 6 – RoleClass PhysicalNetwork
51 6.2.6 RoleClass LogicalDevice
6.2.7 RoleClass LogicalEndpointlist
6.2.8 RoleClass LogicalConnection
6.2.9 RoleClass LogicalNetwork
Table 7 – RoleClass LogicalDevice
Table 8 – RoleClass LogicalEndpointlist
Table 9 – RoleClass LogicalConnection
Table 10 – RoleClass LogicalNetwork
52 6.3 Basic communication interface class library
6.3.1 General
6.3.2 InterfaceClass PhysicalEndPoint
6.3.3 InterfaceClass LogicalEndPoint
Figure 29 – Basic communication interface class library
Figure 30 – CommunicationInterfaceClassLib
Figure 31 – XML text of the communication interface class library
Table 11 – InterfaceClass PhysicalEndPoint
53 6.4 Steps to model technology specific libraries
6.4.1 General
6.4.2 Step 1: Development of technology specific role classes
Figure 32 – Derivation of a technology specific role class libraryout of the base role class library
Table 12 – InterfaceClass LogicalEndPoint
54 6.4.3 Step 2: Development of technology specific interface classes
6.4.4 Step 3: Development of system unit class libraries
Figure 33 – Derivation of a technology specific role class library out of the base role class library
55 6.4.5 Step 4: Modelling the network
Figure 34 – Technology specific s
56 6.4.6 Step 5: Modelling the connections
6.5 PDU modelling
6.5.1 General
Figure 35 – Technology specific communication network
57 6.5.2 RoleClass CommunicationPackage
Figure 36 – Extended communication role class library
Figure 37 – Extended CommunicationRoleClassLib
Figure 38 – XML text of the extended communication role class library
58 6.5.3 InterfaceClass DatagrammObject
Figure 39 – Extended communication interface class library
Figure 40 – Extended CommunicationInterfaceClassLib
Figure 41 – XML text of the extended communication role class library
Table 13 – RoleClass CommunicationPackage
59 6.5.4 Steps to model technology specific libraries
Figure 42 – Derivation of a technology specific roleclass library out of the extended role class library
Table 14 – InterfaceClass DatagrammObject
60 Figure 43 – Derivation of a technology specific interface class library out of the extended interface class library
Figure 44 – Technology specific extended s
61 6.6 References to attributes
Figure 45 – Technology specific communication network with communication package models
62 Table 15 – Communication related attributes
63 6.7 Usage of metadata
64 Figure 46 − Field SourceDocumentInformation accordingto communication related libraries
65 Bibliography

Related products

BS EN IEC 62714-5:2022
$198.66