EN IEC 62769-8:2023
(Main)Field device integration (FDI®) - Part 8: EDD to OPC-UA Mapping
Field device integration (FDI®) - Part 8: EDD to OPC-UA Mapping
IEC 62769-8:2023 specifies how the internal view of a device model represented by the EDD can be transferred into an external view as an OPC-UA information model by mapping EDD constructs to OPC-UA objects.
Feldgeräteintegration (FDI®) - Teil 8: EDD zu OPC-UA Mapping
Intégration des appareils de terrain (FDI®) - Partie 8: Mapping de l'EDD avec l'OPC-UA
L'IEC 62769-8:2023 spécifie comment la vue interne d'un modèle d'appareil représentée par l'EDD peut être transférée dans une vue externe sous forme de modèle d'information OPC-UA en mappant les constructions EDD avec des objets OPC-UA.
Integracija procesne naprave (FDI®) - 8. del: Preslikava EDD v OPC-UA (IEC 62769-8:2023)
General Information
Standards Content (Sample)
SLOVENSKI STANDARD
oSIST prEN IEC 62769-8:2022
01-maj-2022
Integracija procesne naprave (FDI) - 8. del: Preslikava EDD v OPC-UA
Field device integration (FDI) - Part 8: EDD to OPC-UA Mapping
Ta slovenski standard je istoveten z: prEN IEC 62769-8:2022
ICS:
25.040.40 Merjenje in krmiljenje Industrial process
industrijskih postopkov measurement and control
35.240.50 Uporabniške rešitve IT v IT applications in industry
industriji
oSIST prEN IEC 62769-8:2022 en,fr,de
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.
---------------------- Page: 1 ----------------------
oSIST prEN IEC 62769-8:2022
---------------------- Page: 2 ----------------------
oSIST prEN IEC 62769-8:2022
65E/851/CDV
COMMITTEE DRAFT FOR VOTE (CDV)
PROJECT NUMBER:
IEC 62769-8 ED1
DATE OF CIRCULATION: CLOSING DATE FOR VOTING:
2022-03-04 2022-05-27
SUPERSEDES DOCUMENTS:
65E/790/NP, 65E/836A/RVN
IEC SC 65E : DEVICES AND INTEGRATION IN ENTERPRISE SYSTEMS
SECRETARIAT: SECRETARY:
United States of America Mr Donald (Bob) Lattimer
OF INTEREST TO THE FOLLOWING COMMITTEES: PROPOSED HORIZONTAL STANDARD:
Other TC/SCs are requested to indicate their interest, if any, in
this CDV to the secretary.
FUNCTIONS CONCERNED:
EMC ENVIRONMENT QUALITY ASSURANCE SAFETY
SUBMITTED FOR CENELEC PARALLEL VOTING NOT SUBMITTED FOR CENELEC PARALLEL VOTING
Attention IEC-CENELEC parallel voting
The attention of IEC National Committees, members of
CENELEC, is drawn to the fact that this Committee Draft for Vote
(CDV) is submitted for parallel voting.
The CENELEC members are invited to vote through the
CENELEC online voting system.
This document is still under study and subject to change. It should not be used for reference purposes.
Recipients of this document are invited to submit, with their comments, notification of any relevant patent rights of which they are
aware and to provide supporting documentation.
TITLE:
Field device integration (FDI) - Part 8:EDD to OPC-UA Mapping
PROPOSED STABILITY DATE: 2025
Copyright © 2022 International Electrotechnical Commission, IEC. All rights reserved. It is permitted to download this
electronic file, to make a copy and to print out the content for the sole purpose of preparing National Committee positions. You
may not copy or "mirror" the file or printed version of the document, or any part of it, for any other purpose without permis sion
in writing from IEC.
---------------------- Page: 3 ----------------------
oSIST prEN IEC 62769-8:2022
65E/851/CDV – 2 – IEC CDV 62769-8 © IEC:2022
NOTE FROM TC/SC OFFICERS:
---------------------- Page: 4 ----------------------
oSIST prEN IEC 62769-8:2022
65E/851/CDV – 3 – IEC CDV 62769-8 © IEC:2022
1 CONTENTS
2
3 FOREWORD . 6
4 1 Scope . 8
5 2 Normative references . 8
6 3 Terms, definitions, abbreviated terms, acronyms and conventions . 8
7 3.1 Terms and definitions . 8
8 3.2 Abbreviated terms and acronyms . 9
9 3.3 Conventions for graphical notation . 9
10 4 Introduction . 10
11 5 Basic principles of explicit mapping . 11
12 5.1 Semantic maps to tag EDD constructs . 11
13 5.2 Alias collections . 12
14 5.2.1 Syntax of semantic id for alias mappings. 12
15 5.3 Namespace Alias Collection . 12
16 5.4 Reference Type Alias Collection . 14
17 5.5 Semantic maps for OPC-UA type mapping . 15
18 5.5.1 Syntax of Semantic Id for OPC-UA . 15
19 5.6 Semantic maps for unit mapping . 16
20 5.6.1 Syntax of Semantic Id for Units . 16
21 5.7 Explicit mapping of OPC-UA variable types . 16
22 5.8 Explicit mapping of complex OPC-UA types . 18
23 5.9 Explicit mapping of nested object and variable types . 20
24 5.9.1 When to use collections . 20
25 5.9.2 When to use menus . 20
26 5.9.3 OPC-UA diagram of nested mapping example . 20
27 5.9.4 EDD snippet of nested mapping example . 22
28 5.10 Explicit mapping of methods . 25
29 5.10.1 Mapping EDD methods to OPC-UA objects, variables or properties . 25
30 5.10.2 Mapping EDD methods to OPC-UA methods . 25
31 5.11 Explicit mapping of alarms . 27
32 5.12 Explicit mapping of units. 35
33 5.13 Explicit mapping of aggregated data by methods . 36
34 5.14 Explicit mapping with reference types . 38
35 5.14.1 Example: Adding an additional property to an instance of variable . 38
36 5.14.2 Example: Adding an additional variable to an instance of a variable or an object
37 40
38 5.14.3 Example: Adding an OPC-UA alias to a variable . 41
39 6 Implicit rules . 43
40 6.1 BrowseName of OPC-UA object . 43
41 6.1.1 General . 43
42 6.1.2 Overruling of BrowseName implicit rule . 43
43 6.2 DisplayName of OPC-UA object . 43
---------------------- Page: 5 ----------------------
oSIST prEN IEC 62769-8:2022
65E/851/CDV – 4 – IEC CDV 62769-8 © IEC:2022
44 6.2.1 General . 43
45 6.2.2 Overruling of DisplayName implicit rule . 43
46 6.3 HANDLING and AccessLevel. 43
47 6.4 VALIDITY and Availability . 43
48 6.5 Return values of EDD methods . 44
49 6.5.1 EDD methods mapped to OPC-UA objects, variables, properties or attributes 44
50 6.5.2 EDD methods mapped to OPC-UA methods . 44
51 6.6 Units . 44
52 6.7 Range . 44
53 6.8 Forward cast . 44
54 6.9 Backward cast . 44
55 6.10 Abstract OPC-UA types . 44
56 6.11 Unmapped mandatory OPC-UA properties, components and folders . 45
57 6.12 Semantic Identifiers and Dictionary References . 45
58 6.13 Implicit Type Casts for OPC-UA DataTypes . 46
59 7 Mapping the EDD device model into PA-DIM (OPC 30081) . 48
60 7.1 Explicit mapping of sub-devices . 48
61 7.2 Adding sub-devices . 48
62
63 Figure 1 - OPC UA Graphical Notation for NodeClasses . 9
64 Figure 2 -OPC UA Graphical Notation for References . 9
65 Figure 3 - OPC UA Graphical Notation Example . 10
66 Figure 4 - Optimized Type Reference . 10
67 Figure 5 - Similarity of OPC-UA objects and EDD collections . 11
68 Figure 6 - Syntax of sematic ids for EDD entry points . 12
69 Figure 7 - Syntax of sematic id for alias mapping . 12
70 Figure 8 - Namespace Collection . 14
71 Figure 9 - Reference Type Collection . 15
72 Figure 10 - Use of SEMANTIC_MAP for OPC-UA types . 15
73 Figure 11 - Syntax of OPC-UA type identifier. 15
74 Figure 13 - Syntax of Unit Identifier . 16
75 Figure 14 - Most simple mapping example. 17
76 Figure 15 - EDD variable mapped to an OPC-UA BaseDataVariableType . 18
77 Figure 16 - Simple mapping example with range and unit . 18
78 Figure 17 - Mapping of a collection to an OPC-UA variable . 19
79 Figure 18 - Nested objects and variables. 21
80 Figure 19 - Example of nested objects and variables . 25
81 Figure 20 - Simple method . 26
82 Figure 21 - Example of simple method mapping . 27
83 Figure 22 - Supported Alarms . 32
84 Figure 23 - Example of alarm mapping . 35
---------------------- Page: 6 ----------------------
oSIST prEN IEC 62769-8:2022
IEC CDV 62769-8 © IEC:2022 – 5 –
85 Figure 24 - EDD example of . 36
86 Figure 25 - Instance of PADIMType . 37
87 Figure 26 - Method of type DD_STRING mapped to a string variable . 38
88 Figure 27 - Adding a property which is not defined in mapped type . 39
89 Figure 28 - EDD example of adding a property . 39
90 Figure 29 - Adding a component . 40
91 Figure 30 - EDD example adding a component . 41
92 Figure 31 - Adding an alias . 42
93 Figure 32 - EDD example adding an alias . 43
94 Figure 33 - Explicit mapping of dictionary entries . 45
95 Figure 34 - Combination with an implicitly mapped dictionary entry . 46
96 Figure 35 - Sub Devices . 49
97 Figure 36 - Sub devices example . 50
98
99 Table 1 - Alarm properties mapping . 28
100 Table 2 - Implicit Type Casts . 46
101
102
---------------------- Page: 7 ----------------------
oSIST prEN IEC 62769-8:2022
65E/851/CDV – 6 – IEC CDV 62769-8 © IEC:2022
103 INTERNATIONAL ELECTROTECHNICAL COMMISSION
104 ____________
105
106 FIELD DEVICE INTEGRATION (FDI) –
107
108 Part 8: EDD to OPC-UA Mapping
109
110 FOREWORD
111 1) The International Electrotechnical Commission (IEC) is a worldwide organization for standardization comprising all national
112 electrotechnical committees (IEC National Committees). The object of IEC is to promote international co -operation on all
113 questions concerning standardization in the electrical and electronic fields. To this end and in addition to other activities , IEC
114 publishes International Standards, Technical Specifications, Technical Reports, Publicly Available Specifications (PAS) and
115 Guides (hereafter referred to as “IEC Publication(s)”). Their preparation is entrusted to technical committees; any IEC Natio nal
116 Committee interested in the subject dealt with may participate in this preparatory work. International, governmental and non -
117 governmental organizations liaising with the IEC also participate in this preparation. IEC collaborates closely with the
118 International Organization for Standardization (ISO) in accordance with conditions determined by agreement between the two
119 organizations.
120 2) The formal decisions or agreements of IEC on technical matters express, as nearly as possible, an international consensus of
121 opinion on the relevant subjects since each technical committee has representation from all interested IEC National Committees.
122 3) IEC Publications have the form of recommendations for international use and are accepted by IEC National Committees in that
123 sense. While all reasonable efforts are made to ensure that the technical content of IEC Publications is accurate, IEC cannot be
124 held responsible for the way in which they are used or for any misinterpretation by any end user.
125 4) In order to promote international uniformity, IEC National Committees undertake to apply IEC Publications transparently to the
126 maximum extent possible in their national and regional publications. Any divergence between any IEC Publication and the
127 corresponding national or regional publication shall be clearly indicated in the latter.
128 5) IEC itself does not provide any attestation of conformity. Independent certification bodies provide conformity assessment
129 services and, in some areas, access to IEC marks of conformity. IEC is not responsib le for any services carried out by
130 independent certification bodies.
131 6) All users should ensure that they have the latest edition of this publication.
132 7) No liability shall attach to IEC or its directors, employees, servants or agents including individual experts and members of its
133 technical committees and IEC National Committees for any personal injury, property damage or other damage of any nature
134 whatsoever, whether direct or indirect, or for costs (including legal fees) and expenses arising out of the p ublication, use of, or
135 reliance upon, this IEC Publication or any other IEC Publications.
136 8) Attention is drawn to the Normative references cited in this publication. Use of the referenced publications is indispensable for
137 the correct application of this publication.
138 9) Attention is drawn to the possibility that some of the elements of this IEC Publication may be the subject of patent rights. IEC
139 shall not be held responsible for identifying any or all such patent rights.
140 IEC 62769-8 has been prepared by subcommittee 65E: Devices and integration in enterprise systems, of
141 IEC technical committee 65: Industrial-process measurement, control and automation. It is an International
142 Standard.
143 The text of this International Standard is based on the following documents:
Draft Report on voting
XX/XX/FDIS XX/XX/RVD
144
145 Full information on the voting for its approval can be found in the report on voting indicated in the above
146 table.
147 The language used for the development of this International Standard is English.
---------------------- Page: 8 ----------------------
oSIST prEN IEC 62769-8:2022
IEC CDV 62769-8 © IEC:2022 – 7 –
148 This document was drafted in accordance with ISO/IEC Directives, Part 2, and developed in accordance
149 with ISO/IEC Directives, Part 1 and ISO/IEC Directives, IEC Supplement, available at
150 www.iec.ch/members_experts/refdocs. The main document types developed by IEC are described in greater
151 detail at www.iec.ch/standardsdev/publications.
152 The committee has decided that the contents of this document will remain unchanged until the stability date
153 indicated on the IEC website under "http://webstore.iec.ch" in the data related to the specific document. At
154 this date, the document will be
155 • reconfirmed,
156 • withdrawn,
157 • replaced by a revised edition, or
158 • amended.
159
---------------------- Page: 9 ----------------------
oSIST prEN IEC 62769-8:2022
65E/851/CDV – 8 – IEC CDV 62769-8 © IEC:2022
160 FIELD DEVICE INTEGRATION (FDI) –
161
162 Part 8: EDD to OPC-UA Mapping
163
164
165
166 1 Scope
167 This part of IEC 62769 specifies how the internal view of a device model represented by the EDD can be
168 transferred into an external view as an OPC-UA information model by mapping EDD constructs to OPC-UA
169 objects.
170 2 Normative references
171 The following documents, in whole or in part, are normatively referenced in this document and are
172 indispensable for its application. For dated references, only the edition cited applies. For undated
173 references, the edition of the referenced document (including any amendments), which applies for a specific
174 FDI Technology Version is defined within the FDI Technology Management Document and on the support
175 portals of FieldComm Group and PI International.
176 IEC 62769-1, Field Device Integration (FDI) – Part 1: Overview
177 IEC 62769-5, Field Device Integration (FDI) – Part 5: FDI Information Model
178 IEC 62769-6, Field Device Integration (FDI) – Part 6: FDI Technology Mapping
179 IEC 62541-3, OPC unified architecture – Part 3: Address Space Model
180 IEC 62541-4, OPC unified architecture – Part 4: Services
181 IEC 62541-5, OPC unified architecture – Part 5: Information Model
182 IEC 62541-8, OPC unified architecture – Part 8: Data Access
183 IEC 62541-9, OPC unified architecture – Part 9: Alarms and Conditions
184 IEC 62541-17, OPC unified architecture – Part 17: Alias Names
185 IEC 62541-19, OPC unified architecture – Part 19: Dictionary Reference
186 IEC 62541-100, OPC unified architecture – Part 100: Devices
187 OPC 30081, UA CS for Process Automation Devices - PA-DIM 1.00
188 UN/CEFACT, UNECE Recommendation N 20, Codes for Units of Measure Used in International Trade
189 https://www.unece.org/cefact/codesfortrade/codes_index.html
190 3 Terms, definitions, abbreviated terms, acronyms and conventions
191 3.1 Terms and definitions
192 For the purposes of this document, the terms and definitions given in IEC 62769-1, IEC 62769-5,
193 IEC 62769-6, IEC 62541-3, IEC 62541-3, IEC 62541-5, IEC 62541-8, IEC 62541-9, IEC 62541-17,
194 IEC 62541-19, IEC 62541-100, and OPC 30081 apply.
---------------------- Page: 10 ----------------------
oSIST prEN IEC 62769-8:2022
IEC CDV 62769-8 © IEC:2022 – 9 –
195 3.2 Abbreviated terms and acronyms
196 For the purposes of this document, the abbreviated terms and acronyms given in FCG TS62769 -1 as well
197 as the following apply.
PA-DIM Process Automation Device Information Model
198 3.3 Conventions for graphical notation
199 OPC UA defines a graphical notation for an OPC UA AddressSpace. It defines graphical symbols for all
200 NodeClasses and how different types of References between Nodes can be visualized. Figure 1 shows the
201 symbols for the NodeClasses used in this standard. NodeClasses representing types always have a shadow.
Object ObjectType
Variable VariableType
Method DataType
ReferenceType
202
203 Figure 1 - OPC UA Graphical Notation for NodeClasses
204 Figure 2 shows the symbols for the ReferenceTypes used in this standard. The Reference s ymbol is
205 normally pointing from the source Node to the target Node. The only exception is the HasSubType
206 Reference. The most important References such as HasComponent, HasProperty, HasTypeDefinition and
207 HasSubType have special symbols avoiding the name of the Reference. For other ReferenceTypes or
208 derived ReferenceTypes the name of the ReferenceType is used together with the symbol.
HasInputVars
HasComponent
HasProperty
HasTypeDefinition
HasSubType
Hierarchical
Reference
NonHierarchical
Reference
209
210 Figure 2 -OPC UA Graphical Notation for References
211 Figure 3 shows a typical example for the use of the graphical notation. Object_A and Object_B are instances
212 of the ObjectType_Y indicated by the HasTypeDefinition References. The ObjectType_Y is derived from
213 ObjectType_X indicated by the HasSubType Reference. The Object_A has the components Variable_1,
214 Variable_2 and Method_1.
---------------------- Page: 11 ----------------------
oSIST prEN IEC 62769-8:2022
65E/851/CDV – 10 – IEC CDV 62769-8 © IEC:2022
215 To describe the components of an Object on the ObjectType the same NodeClasses and References are
216 used on the Object and on the ObjectType such as for ObjectType_Y in the example. The Nodes used to
217 describe an ObjectType are instance declaration Nodes.
218 To provide more detailed information for a Node, a subset or all Attributes and their values can be added to
219 a graphical symbol (see for example Variable_1, the component of Object_A in Figure 3).
Types
ObjectType_X
Object_A
Object_B ObjectType_Y
Variable_1
DataType = Int32
Value = -22
AccessLevel = Read Variable_1 Variable_1
Variable_2 Variable_2
Variable_2
Method_1 Method_1
Method_1
220
221 Figure 3 - OPC UA Graphical Notation Example
222 To improve readability, this document frequently includes the type name inside the instance box rather than
223 displaying both boxes and a reference between them. This optimization is shown in Figure 4.
ObjectType_Y:
Object_B
BaseVariableType:
Variable_1
AnalogItemType:
Variable_2
Method_1
224
225 Figure 4 - Optimized Type Reference
226
227 4 Introduction
228 There are two types of mapping mechanisms – explicit and implicit mapping. Explicit mapping is provided
229 by the EDD constructs SEMANTIC_MAP in combination with COLLECTIONS, METHODS and VARIABLES
230 including the mapping of enumerations and is done by the EDD-developer. Implicit mapping is provided by
231 the implementation of the OPC-UA server in conjunction with a FDI server and covers definitions like default
232 casts (e.g. any number value to float64) or even the mapping of complete lists of unit codes from a fieldbus
233 domain (HART, Profibus, …) into an OPC-UA domain (e.g. UNECE, CDD, …).
---------------------- Page: 12 ----------------------
oSIST prEN IEC 62769-8:2022
IEC CDV 62769-8 © IEC:2022 – 11 –
234 Looking at OPC-UA objects containing named data items like attributes, properties, variables and other
235 objects, the most similar EDD objects are collections containing named data items like variables, menus
236 and other collections (see Figure 5).
COLLECTION SomeCollectionName
SomeObjectName
{
LABEL "Some Label";
HELP [blank];
Value1
MEMBERS
{
Value1, VAR_Value_1;
Value2
Value2, VAR_Value_1;
Property, VAR_Property_1;
}
Property
}
237
238 Figure 5 - Similarity of OPC-UA objects and EDD collections
239 In fact, the EDD construct collection is the key element for the basic principle of how EDD device model
240 data shall be mapped into an OPC-UA information model. The following clauses describe and define how
241 this must be done. Therefor this document has normative character for EDD developers and developers of
242 OPC-servers accessing an FDI server to publish an OPC-UA information model according to a specific OPC-
243 UA namespace and the mapping information provided by the EDD.
244 Clause 5 covers in detail how the mapping works in principle and for any OPC-UA information model based
245 on any namespace.
246 Based on Clause 5, Clause 7 describes some details how to map the EDD into PA-DIM. Additional normative
247 definitions how to map fieldbus specific data (e.g. identification) into PA-DIM is provided by the FDI-Profile
248 specifications for HART, FF, PROFINET, Profibus, Modbus and ISA100.
249 Before starting with doing some EDD mapping, it is strongly recommended to get a basic understanding of
250 OPC-UA concerning how object types, variable types and reference types are defined.
251 5 Basic principles of explicit mapping
252 5.1 Semantic maps to tag EDD constructs
253 For not having to use naming conventions for EDD constructs to link a specific purpose to an EDD construct,
254 semantic maps shall be used to kind of tag an EDD construct by a specifically defined semantic id. For the
255 time being three syntax definitions exist for three specific purposes. The details of how to use them will be
256 explained in the corresponding context.
257 The syntax of semantic ids for EDD entry pointes is illustrated in Figure 6.
---------------------- Page: 13 ----------------------
oSIST prEN IEC 62769-8:2022
65E/851/CDV – 12 – IEC CDV 62769-8 © IEC:2022
EDD // Type of Entry Point / Subtype of Entry Point
String literal defining the
subtype of the EDD entry point
Separator
String literal defining type of EDD entry point
Scope separator
String literal defining EDD scope
258
259 Figure 6 - Syntax of sematic ids for EDD entry points
260 5.2 Alias collections
261 Alias collections are used to define aliases for lengthy strings having a specific meaning. The alias should
262 be short and shall be unique across the complete EDD. Aliases will be used as member identifiers or as a
263 part of member identifiers or in SEMANTIC_MAPs for OPC-UA type mapping. Alias collections are the main
264 entry points to resolve EDD to OPC-UA mapping and shall not depend on each other (see 5.3 and 5.4).
265 5.2.1 Syntax of semantic id for alias mappings
266 The syntax of semantic id for alias mapping is illustrated in Figure 7.
EDD // AliasCollection / AliasType
String literal defining the type
of aliases of the alias collection
Separator
String literal defining entry point for alias collections
Scope separator
String literal defining EDD scope
267
268 Figure 7 - Syntax of sematic id for alias mapping
269
270 5.3 Namespace Alias Collection
271 To prevent name conflicts, any OPC-UA type is defined in scope of a specific namespace. A namespace
272 collection and appropriate variables shall be defined to provide suitable names for the namespace URIs.
273 The member identifier of the collection item shall be used as an alias wherever a namespace identifier is
274 needed. In the following example “__UA_” represents the namespace http://opcfoundation.org/UA/ which
275 is defined by the default value of the referenced variable “UA_Namespace”.
276 It is mandatory to define at least one namespace collection for an EDD defining EDD to OPC-UA mapping.
---------------------- Page: 14 ----------------------
oSIST prEN IEC 62769-8:2022
IEC CDV 62769-8 © IEC:2022 – 13 –
277 Definition:
278 The name of the namespace collectio
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.