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