EN IEC 62769-5:2021
(Main)Field Device Integration (FDI) - Part 5: Information Model
Field Device Integration (FDI) - Part 5: Information Model
This part of IEC 62769 defines the FDI Information Model. One of the main tasks of the Information Model is to reflect the topology of the automation system. Therefore, it represents the devices of the automation system as well as the connecting communication networks including their properties, relationships, and the operations that can be performed on them. The types in the AddressSpace of the FDI Server constitute a catalogue, which is built from FDI Packages. The fundamental types for the FDI Information Model are well defined in OPC UA for Devices (IEC 62541-100). The FDI Information Model specifies extensions for a few special cases and otherwise explains how these types are used and how the contents are built from elements of DevicePackages. The overall FDI architecture is illustrated in Figure 1. The architectural components that are within the scope of this document have been highlighted in this illustration. [Figure 1 - FDI architecture diagram]
Feldgeräteintegration (FDI) - Teil 5: FDI-Informationsmodell
Intégration des appareils de terrain (FDI) - Partie 5: Modèle d'Information
IEC 62769-5:2021 est disponible sous forme de IEC 62769-5:2021 RLV qui contient la Norme internationale et sa version Redline, illustrant les modifications du contenu technique depuis l'édition précédente . L’IEC 62769-5:2021 définit le Modèle d'Information FDI. L'un des principaux objectifs du Modèle d'Information est de refléter la topologie du système d'automatisation. Par conséquent, il représente les appareils du système d'automatisation ainsi que les réseaux de communication connectés, y compris leurs propriétés, leurs relations et les opérations dont ils peuvent faire l'objet. Les types présents dans l'AddressSpace (Espace d'adressage) du Serveur FDI constituent un catalogue, construit à partir des FDI Packages (Paquetages FDI). Les types fondamentaux pour le Modèle d'Information FDI sont définis dans l'OPC UA pour les Appareils (IEC 62541-100). Le Modèle d'Information FDI spécifie des extensions pour quelques cas spéciaux et explique la façon dont ces types sont utilisés et dont les contenus sont construits à partir des éléments de DevicePackages. L'architecture FDI complète est représentée à la Figure 1. Les composants architecturaux qui relèvent du domaine d'application du présent document ont été mis en évidence dans cette représentation.
Integracija procesne naprave (FDI) - 5. del: Informacijski model (IEC 62769-5:2021)
General Information
Relations
Standards Content (Sample)
SLOVENSKI STANDARD
01-julij-2021
Nadomešča:
SIST EN 62769-5:2015
Integracija procesne naprave (FDI) - 5. del: Informacijski model (IEC 62769-5:2021)
Field Device Integration (FDI) - Part 5: Information Model (IEC 62769-5:2021)
Feldgeräteintegration (FDI) - Teil 5: FDI-Informationsmodell (IEC 62769-5:2021)
Intégration des appareils de terrain (FDI) - Partie 5: Modèle d'Information (IEC 62769-
5:2021)
Ta slovenski standard je istoveten z: EN IEC 62769-5:2021
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
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.
EUROPEAN STANDARD EN IEC 62769-5
NORME EUROPÉENNE
EUROPÄISCHE NORM
March 2021
ICS 25.040.40; 35.100.05 Supersedes EN 62769-5:2015 and all of its amendments
and corrigenda (if any)
English Version
Field Device Integration (FDI) - Part 5: Information Model
(IEC 62769-5:2021)
Intégration des appareils de terrain (FDI) - Partie 5: Modèle Feldgeräteintegration (FDI) - Teil 5: FDI-Informationsmodell
d'Information (IEC 62769-5:2021)
(IEC 62769-5:2021)
This European Standard was approved by CENELEC on 2021-03-12. 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 obtained 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 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, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, the
Netherlands, Norway, Poland, Portugal, Republic of North Macedonia, Romania, Serbia, Slovakia, Slovenia, Spain, Sweden, Switzerland,
Turkey and the United Kingdom.
European Committee for Electrotechnical Standardization
Comité Européen de Normalisation Electrotechnique
Europäisches Komitee für Elektrotechnische Normung
CEN-CENELEC Management Centre: Rue de la Science 23, B-1040 Brussels
© 2021 CENELEC All rights of exploitation in any form and by any means reserved worldwide for CENELEC Members.
Ref. No. EN IEC 62769-5:2021 E
European foreword
The text of document 65E/762(F)/FDIS, future edition 2 of IEC 62769-5, 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
The following dates are fixed:
• latest date by which the document has to be implemented at national (dop) 2021-12-12
level by publication of an identical national standard or by endorsement
• latest date by which the national standards conflicting with the (dow) 2024-03-12
document have to be withdrawn
This document supersedes EN 62769-5:2015 and all of its amendments and corrigenda (if any).
Attention is drawn to the possibility that some of the elements of this document may be the subject of
patent rights. CENELEC shall not be held responsible for identifying any or all such patent rights.
Endorsement notice
The text of the International Standard IEC 62769-5:2021 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 62541-7 NOTE Harmonized as EN IEC 62541-7
IEC 62769-1 NOTE Harmonized as EN 62769-1
Annex ZA
(normative)
Normative references to international publications
with their corresponding European publications
The following documents are referred to in the text in such a way that some or all of their content
constitutes requirements of this document. For dated references, only the edition cited applies. For
undated references, the latest edition of the referenced document (including any amendments)
applies.
NOTE 1 Where 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.
Publication Year Title EN/HD Year
IEC 61784-1 - Industrial communication networks - EN IEC 61784-1 -
Profiles Part 1: Fieldbus profiles
IEC 61804-3 - Devices and integration in enterprise EN IEC 61804-3 -
systems - Function blocks (FB) for
process control and electronic device
description language (EDDL) - Part 3:
EDDL syntax and semantics
IEC 61804-4 - Devices and integration in enterprise EN IEC 61804-4 -
systems - Function blocks (FB) for
process control and electronic device
description language (EDDL) - Part 4:
EDD interpretation
IEC 62541-3 - OPC Unified Architecture - Part 3: EN IEC 62541-3 -
Address Space Model
IEC 62541-4 - OPC Unified Architecture - Part 4: EN IEC 62541-4 -
Services
IEC 62541-5 - OPC Unified Architecture - Part 5: EN IEC 62541-5 -
Information Model
IEC 62541-6 - OPC Unified Architecture - Part 6: EN IEC 62541-6 -
Mappings
IEC 62541-8 - OPC Unified Architecture - Part 8: Data EN IEC 62541-8 -
Access
IEC 62541-100 - OPC Unified Architecture - Part 100: EN 62541-100 -
Device Interface
IEC 62769-1 - Field Device Integration (FDI) - Part 1: EN IEC 62769-1 -
Overview
IEC 62769-2 - Field Device Integration (FDI) - Part 2: EN IEC 62769-2 -
FDI Client
IEC 62769-4 - Field Device Integration (FDI) - Part 4: EN IEC 62769-4 -
FDI Packages
IEC 62769-7 - Field Device Integration (FDI) - Part 7: EN IEC 62769-7 -
Communication Devices
IEC 62769-5 ®
Edition 2.0 2021-02
INTERNATIONAL
STANDARD
NORME
INTERNATIONALE
colour
inside
Field device integration (FDI) –
Part 5: Information Model
Intégration des appareils de terrain (FDI) –
Partie 5: Modèle d'Information
INTERNATIONAL
ELECTROTECHNICAL
COMMISSION
COMMISSION
ELECTROTECHNIQUE
INTERNATIONALE
ICS 25.040.40; 35.100.05 ISBN 978-2-8322-9313-3
– 2 – IEC 62769-5:2021 © IEC 2021
CONTENTS
FOREWORD . 7
INTRODUCTION . 9
1 Scope . 10
2 Normative references . 11
3 Terms, definitions, abbreviated terms and conventions . 11
3.1 Terms and definitions . 11
3.2 Abbreviated terms . 11
3.3 Conventions . 12
3.4 Conventions for graphical notation . 12
4 Overview of OPC Unified Architecture . 14
4.1 General . 14
4.2 Overview of OPC UA Devices . 14
5 Concepts . 16
5.1 General . 16
5.2 Device topology . 16
5.3 Online/offline . 18
5.4 Catalogue (Type Definitions) . 19
5.5 Communication . 19
6 AddressSpace organization . 19
7 Device Model for FDI . 20
7.1 General . 20
7.2 Online/offline . 20
7.3 Device health . 21
7.3.1 DeviceHealth Mapping . 21
7.3.2 DeviceHealth Diagnostics . 22
7.4 User interface elements . 23
7.4.1 General . 23
7.4.2 UI Description Type . 24
7.4.3 UI Plug-in Type . 24
7.5 Type-specific support information . 26
7.6 Actions . 27
7.6.1 Overview . 27
7.6.2 Action Type . 27
7.6.3 ActionService Type . 28
7.6.4 ActionService Object . 28
7.6.5 InvokeAction Method . 29
7.6.6 RespondAction Method . 30
7.6.7 AbortAction Method . 31
8 Network and connectivity . 32
9 Utility functions . 32
9.1 Overview. 32
9.2 Locking . 32
9.3 EditContext . 33
9.3.1 Overview . 33
9.3.2 EditContext Type . 33
IEC 62769-5:2021 © IEC 2021 – 3 –
9.3.3 EditContext Object . 33
9.3.4 GetEditContext Method . 34
9.3.5 RegisterNodes Method . 35
9.3.6 Apply Method . 36
9.3.7 Reset Method . 37
9.3.8 Discard Method . 38
9.4 Direct Device Access . 39
9.4.1 General . 39
9.4.2 DirectDeviceAccess Type . 39
9.4.3 DirectDeviceAccess Object . 40
9.4.4 InitDirectAccess Method . 41
9.4.5 EndDirectAccess Method . 41
9.4.6 Transfer Method . 42
10 Parameter Types . 43
10.1 General . 43
10.2 ScalingFactor Property . 44
10.3 Min_Max_Values Property . 44
11 FDI StatusCodes . 45
12 Specialized topology elements. 46
13 Auditing . 47
13.1 General . 47
13.2 FDI Client-provided context information . 47
13.3 LogAuditTrailMessage Method . 47
14 FDI Server Version . 48
15 Mapping FDI Package information to the FDI Information Model . 48
15.1 General . 48
15.2 Localization . 49
15.2.1 Localized text . 49
15.2.2 Engineering units . 49
15.3 Device . 49
15.3.1 General . 49
15.3.2 Mapping to Attributes to a specific DeviceType Node . 49
15.3.3 Mapping to Properties . 49
15.3.4 Mapping to ParameterSet . 50
15.3.5 Mapping to Functional Groups . 50
15.3.6 Mapping to DeviceTypeImage . 50
15.3.7 Mapping to Documentation . 50
15.3.8 Mapping to ProtocolSupport . 50
15.3.9 Mapping to ImageSet . 51
15.3.10 Mapping to ActionSet . 51
15.3.11 Mapping to MethodSet . 51
15.4 Modular Device . 51
15.5 Block . 51
15.5.1 General . 51
15.5.2 Mapping to Attributes . 51
15.5.3 Mapping to ParameterSet . 52
15.5.4 Mapping to Functional Groups . 52
15.5.5 Mapping to ActionSet . 52
– 4 – IEC 62769-5:2021 © IEC 2021
15.5.6 Mapping to MethodSet . 52
15.5.7 Instantiation rules . 52
15.6 Parameter . 52
15.6.1 General . 52
15.6.2 Private Parameters . 56
15.6.3 MIN_Value and MAX_Value . 57
15.6.4 Engineering units . 57
15.6.5 Enumerated Parameters . 57
15.6.6 Bit-enumerated Parameters . 57
15.6.7 Representation of records . 57
15.6.8 Representation of arrays, and lists of Parameters with simple data types . 58
15.6.9 Representation of values arrays, and lists of RECORD Parameters . 59
15.6.10 Representation of COLLECTION and REFERENCE ARRAY . 59
15.6.11 SCALING_FACTOR . 60
15.7 Functional Groups. 60
15.8 AXIS elements in UIDs . 61
15.9 Actions . 61
15.10 UIPs . 61
15.11 Protocols, Networks and Connection Points . 61
16 Profiles . 62
Annex A (normative) Namespace and Mappings . 63
Bibliography . 64
Figure 1 – FDI architecture diagram . 10
Figure 2 – OPC UA Graphical Notation for NodeClasses. 12
Figure 3 – OPC UA Graphical Notation for References . 12
Figure 4 – OPC UA Graphical Notation Example . 13
Figure 5 – Optimized Type Reference . 13
Figure 6 – OPC UA Devices Example: Functional Groups . 15
Figure 7 – OPC UA Devices example: Configurable components . 16
Figure 8 – Example of an automation system . 17
Figure 9 – Example of a Device topology . 18
Figure 10 – Example Device Types representing a catalogue . 19
Figure 11 – Online component for access to device data . 21
Figure 12 – Hierarchy of user interface Types . 24
Figure 13 – Integration of Actions within a TopologyElement . 27
Figure 14 – Action Service . 29
Figure 15 – EditContext type and instance . 34
Figure 16 – DirectDeviceAccessType . 39
Figure 17 – DirectDeviceAccess instance . 40
Figure 18 – OPC UA VariableTypes including OPC UA DataAccess . 44
Figure 19 – Example: Complex variable representing a RECORD . 58
Figure 20 – Complex variable representing a VALUE_ARRAY of RECORDs . 59
Table 1 – DeviceHealth Mapping . 22
IEC 62769-5:2021 © IEC 2021 – 5 –
Table 2 – DeviceType definition (excerpt applicable to this clause) . 22
Table 3 – DeviceType definition with DeviceHealth and DeviceHealthDiagnostics . 23
Table 4 – UIDescriptionType Definition . 24
Table 5 – UIPlugInType Definition . 25
Table 6 – ActionType Definition . 28
Table 7 – ActionServiceType Definition . 28
Table 8 – InvokeAction Method Arguments . 30
Table 9 – InvokeAction Method AddressSpace Definition . 30
Table 10 – RespondAction Method Arguments . 31
Table 11 – RespondAction Method AddressSpace Definition . 31
Table 12 – AbortAction Method Arguments . 31
Table 13 – AbortAction Method AddressSpace Definition . 32
Table 14 – EditContextType Definition . 33
Table 15 – GetEditContext Method Arguments . 34
Table 16 – GetEditContext Method AddressSpace Definition . 35
Table 17 – RegisterNodes Method Arguments . 35
Table 18 – RegisterNodes Method AddressSpace Definition . 35
Table 19 – RegistrationParameters DataType Structure . 36
Table 20 – RegisterNodesResult DataType Structure . 36
Table 21 – Apply Method Arguments . 37
Table 22 – Apply Method AddressSpace Definition . 37
Table 23 – ApplyResult DataType Structure . 37
Table 24 – Reset Method Arguments . 38
Table 25 – Reset Method AddressSpace Definition . 38
Table 26 – Discard Method Arguments . 38
Table 27 – Discard Method AddressSpace Definition . 39
Table 28 – DirectDeviceAccessType Definition . 40
Table 29 – DirectDeviceAccess Instance Definition . 41
Table 30 – InitDirectAccess Method Arguments . 41
Table 31 – InitDirectAccess Method AddressSpace Definition . 41
Table 32 – EndDirectAccess Method Arguments . 42
Table 33 – EndDirectAccess Method AddressSpace Definition. 42
Table 34 – Transfer Method Arguments . 42
Table 35 – Transfer Method AddressSpace Definition . 43
Table 36 – ScalingFactor Property Definition . 44
Table 37 – Min_Max_Values Property Definition . 45
Table 38 – Variant_Range DataType Structure . 45
Table 39 – Variant_Range Definition . 45
Table 40 – Good operation level result codes . 46
Table 41 – Uncertain operation level result codes . 46
Table 42 – Bad operation level result codes . 46
Table 43 – LogAuditTrailMessage Method Arguments . 48
Table 44 – LogAuditTrailMessage Method AddressSpace Definition . 48
– 6 – IEC 62769-5:2021 © IEC 2021
Table 45 – FDIServerVersion Property Definition . 48
Table 46 – DeviceType Property Mapping . 50
Table 47 – Setting OPC UA Variable Attributes from EDDL variable attributes . 53
Table 48 – Correspondence between EDDL and OPC UA standard data types . 54
Table 49 – FDI Server Facet Definition . 62
Table 50 – FDI Client Facet Definition. 62
IEC 62769-5:2021 © IEC 2021 – 7 –
INTERNATIONAL ELECTROTECHNICAL COMMISSION
____________
FIELD DEVICE INTEGRATION (FDI) –
Part 5: Information Model
FOREWORD
1) The International Electrotechnical Commission (IEC) is a worldwide organization for standardization comprising
all national electrotechnical committees (IEC National Committees). The object of IEC is to promote
international co-operation on all questions concerning standardization in the electrical and electronic fields. To
this end and in addition to other activities, IEC publishes International Standards, Technical Specifications,
Technical Reports, Publicly Available Specifications (PAS) and Guides (hereafter referred to as "IEC
Publication(s)"). Their preparation is entrusted to technical committees; any IEC National Committee interested
in the subject dealt with may participate in this preparatory work. International, governmental and non-
governmental organizations liaising with the IEC also participate in this preparation. IEC collaborates closely
with the International Organization for Standardization (ISO) in accordance with conditions determined by
agreement between the two organizations.
2) The formal decisions or agreements of IEC on technical matters express, as nearly as possible, an international
consensus of opinion on the relevant subjects since each technical committee has representation from all
interested IEC National Committees.
3) IEC Publications have the form of recommendations for international use and are accepted by IEC National
Committees in that sense. While all reasonable efforts are made to ensure that the technical content of IEC
Publications is accurate, IEC cannot be held responsible for the way in which they are used or for any
misinterpretation by any end user.
4) In order to promote international uniformity, IEC National Committees undertake to apply IEC Publications
transparently to the maximum extent possible in their national and regional publications. Any divergence
between any IEC Publication and the corresponding national or regional publication shall be clearly indicated in
the latter.
5) IEC itself does not provide any attestation of conformity. Independent certification bodies provide conformity
assessment services and, in some areas, access to IEC marks of conformity. IEC is not responsible for any
services carried out by independent certification bodies.
6) All users should ensure that they have the latest edition of this publication.
7) No liability shall attach to IEC or its directors, employees, servants or agents including individual experts and
members of its technical committees and IEC National Committees for any personal injury, property damage or
other damage of any nature whatsoever, whether direct or indirect, or for costs (including legal fees) and
expenses arising out of the publication, use of, or reliance upon, this IEC Publication or any other IEC
Publications.
8) Attention is drawn to the Normative references cited in this publication. Use of the referenced publications is
indispensable for the correct application of this publication.
9) Attention is drawn to the possibility that some of the elements of this IEC Publication may be the subject of
patent rights. IEC shall not be held responsible for identifying any or all such patent rights.
International Standard IEC 62769-5 has been prepared by subcommittee 65E: Devices and
integration in enterprise systems, of IEC technical committee 65: Industrial-process
measurement, control and automation.
This second edition cancels and replaces the first edition published in 2015. This edition
constitutes a technical revision.
This edition includes the following significant technical changes with respect to the previous
edition:
a) support for generic protocol extension for faster adoption of other technologies;
b) support of new protocols;
c) generic protocol extension to allow adoption of other communication protocols;
d) based on generic protocol extension: Modbus RTU.
– 8 – IEC 62769-5:2021 © IEC 2021
The text of this International Standard is based on the following documents:
FDIS Report on voting
65E/762/FDIS 65E/772/RVD
Full information on the voting for the approval of this International Standard can be found in
the report on voting indicated in the above table.
This document has been drafted in accordance with the ISO/IEC Directives, Part 2.
A list of all parts in the IEC 62769 series, published under the general title Field Device
Integration (FDI), can be found on the IEC website.
This standard contains attached files in the form of XML schema. These files are intended to
be used as a complement and do not form an integral part of the standard.
The committee has decided that the contents of this document will remain unchanged until the
stability date indicated on the IEC website under "http://webstore.iec.ch" in the data related to
the specific document. At this date, the document will be
• reconfirmed,
• withdrawn,
• replaced by a revised edition, or
• amended.
IMPORTANT – The 'colour inside' logo on the cover page of this publication indicates
that it contains colours which are considered to be useful for the correct
understanding of its contents. Users should therefore print this document using a
colour printer.
IEC 62769-5:2021 © IEC 2021 – 9 –
INTRODUCTION
The IEC 62769 series has the general title Field Device Integration (FDI) and the following
parts:
– Part 1: Overview
– Part 2: FDI Client
– Part 3: FDI Server
– Part 4: FDI Packages
– Part 5: FDI Information Model
– Part 6: FDI Technology Mapping
– Part 7: FDI Communication Devices
– Part 100: Profiles – Generic Protocol Extensions
– Part 101-1: Profiles – Foundation Fieldbus H1
– Part 101-2: Profiles – Foundation Fieldbus HSE
– Part 103-1: Profiles – PROFIBUS
– Part 103-4: Profiles – PROFINET
– Part 109-1: Profiles – HART and WirelessHART
– Part 115-2: Profiles – Protocol-specific Definitions for Modbus RTU
– Part 150-1: Profiles – ISA 100.11a
– 10 – IEC 62769-5:2021 © IEC 2021
FIELD DEVICE INTEGRATION (FDI) –
Part 5: Information Model
1 Scope
This part of IEC 62769 defines the FDI Information Model. One of the main tasks of the
Information Model is to reflect the topology of the automation system. Therefore, it represents
the devices of the automation system as well as the connecting communication networks
including their properties, relationships, and the operations that can be performed on them.
The types in the AddressSpace of the FDI Server constitute a catalogue, which is built from
FDI Packages.
The fundamental types for the FDI Information Model are well defined in OPC UA for Devices
(IEC 62541-100). The FDI Information Model specifies extensions for a few special cases and
otherwise explains how these types are used and how the contents are built from elements of
DevicePackages.
The overall FDI architecture is illustrated in Figure 1. The architectural components that are
within the scope of this document have been highlighted in this illustration.
IEC
Figure 1 – FDI architecture diagram
IEC 62769-5:2021 © IEC 2021 – 11 –
2 Normative references
The following documents are referred to in the text in such a way that some or all of their
content constitutes requirements of this document. For dated references, only the edition
cited applies. For undated references, the latest edition of the referenced document (including
any amendments) applies.
IEC 61784-1, Industrial communication networks – Profiles – Part 1: Fieldbus profiles
IEC 61804-3, Function blocks (FB) for process control and Electronic Device Description
Language (EDDL) – Part 3: EDDL syntax and semantics
IEC 61804-4, Function blocks (FB) for process control and electronic device description
language (EDDL) – Part 4: EDD interpretation
IEC 62541-3, OPC unified architecture – Part 3: Address Space Model
IEC 62541-4, OPC unified architecture – Part 4: Services
IEC 62541-5, OPC unified architecture – Part 5: Information Model
IEC 62541-6, OPC unified architecture – Part 6: Mappings
IEC 62541-8, OPC unified architecture – Part 8: Data Access
IEC 62541-100, OPC unified architecture – Part 100: OPC UA for Devices
IEC 62769-1, Field Device Integration (FDI) – Part 1: Overview
IEC 62769-2, Field Device Integration (FDI) – Part 2: FDI Client
IEC 62769-4, Field Device Integration (FDI) – Part 4: FDI Packages
IEC 62769-7, Field Device Integration (FDI) – Part 7: FDI Communication Devices
3 Terms, definitions, abbreviated terms and conventions
3.1 Terms and definitions
For the purposes of this document, the terms and definitions given in IEC 62769-1 apply.
ISO and IEC maintain terminological databases for use in standardization at the following
addresses:
• IEC Electropedia: available at http://www.electropedia.org/
• ISO Online browsing platform: available at http://www.iso.org/obp
3.2 Abbreviated terms
For the purposes of this document, the abbreviated terms given in IEC 62769-1 as well as the
following apply.
– 12 – IEC 62769-5:2021 © IEC 2021
HMI Human Machine Interface
SCADA Supervisory Control and Data Acquisition
TCP Transmission Control Protocol
3.3 Conventions
For the purposes of this document, the conventions given in IEC 62769-1 apply.
3.4 Conventions for graphical notation
OPC UA defines a graphical notation for an OPC UA AddressSpace. It defines graphical
symbols for all NodeClasses and how different types of References between Nodes can be
visualized. Figure 2 shows the symbols for the NodeClasses used in this document.
NodeClasses representing types always have a shadow.
IEC
Figure 2 – OPC UA Graphical Notation for NodeClasses
Figure 3 shows the symbols for the ReferenceTypes used in this document. The Reference
symbol is normally pointing from the source Node to the target Node. The only exception is
the HasSubType Reference. The most important References such as HasComponent,
HasProperty, HasTypeDefinition and HasSubType have special symbols avoiding the name of
the Reference. For other ReferenceTypes or derived ReferenceTypes, the name of the
ReferenceType is used together with the symbol.
IEC
Figure 3 – OPC UA Graphical Notation for References
IEC 62769-5:2021 © IEC 2021 – 13 –
Figure 4 shows a typical example for the use of the graphical notation. Object_A and
Object_B are instances of the ObjectType_Y indicated by the HasTypeDefinition References.
The ObjectType_Y is derived from ObjectType_X indicated by the HasSubType Reference.
The Object_A has the components Variable_1, Variable_2 and Method_1.
To describe the components of an Object on the ObjectType the same NodeClasses and
References are used on the Object and on the ObjectType such as for ObjectType_Y in the
example. The Nodes used to describe an ObjectType are instance declaration Nodes.
To provide more detailed information for a Node, a subset or all Attributes and their values
can be added to a graphical symbol (see for example Variable_1, the component of Object_A
in Figure 4).
IEC
Figure 4 – OPC UA Graphical Notation Example
To improve readability, this document frequently includes the type name inside the instance
box rather than displaying both boxes and a reference between them. This optimization is
shown in Figure 5.
IEC
Figure 5 – Optimized Type Reference
– 14 – IEC 62769-5:2021 © IEC 2021
4 Overview of OPC Unified Architecture
4.1 General
The main use case for OPC standards is the online data exchange between devices and HMI
or SCADA systems. In this use case, the device data is provided by an OPC server and is
consumed by an OPC client integrated in the HMI or SCADA system. OPC provides
functionality to browse through a hierarchical namespace containing data items and to read,
write and monitor these items for data changes. Numeric identifiers for NodeIds are defined in
Annex A.
OPC UA incorporates features like Data Access, Alarms and Historical Data via platform
independent communication mechanisms and generic, extensible and object-oriented
modelling capabilities for the information a system wants to expose.
The current version of OPC UA defines an optimized binary TCP protocol for high-
performance intranet communication as well as a mapping to Web Services. The abstract
service model does not depend on a specific protocol mapping and allows adding new
protocols in the future. Features like security, access control and reliability are directly built
into the transport mechanisms. Based on the platform independence of the protocols, OPC
UA servers and clients can be directly integrated into devices and controllers.
The OPC UA information model provides a standard way for Servers to expose Objects to
Clients. Objects in OPC UA terms are composed of other Objects, Variables and Methods.
OPC UA also allows relationships to other Objects to be expressed.
The set of Objects and related information that an OPC UA Server makes available to Clients
is referred to as its AddressSpace. The elements of the OPC UA Object Model are
represented in the AddressSpace as a set of Nodes described by Attributes and
interconnected by References. OPC UA defines various classes of Nodes to represent
AddressSpace components, most importantly Objects, Variables, Methods, ObjectTypes,
DataTypes and ReferenceTypes. Each NodeClass has a defined set of Attributes.
Objects are used to represent components like folders, Devices or Networks. An Object is
associated to a corresponding ObjectType that provides definitions for that Object.
Variables are used to represent values. Two categories of Variables are defined: Properties
and DataVariables.
Properties are Server-defined characteristics of Objects, DataVariables and other Nodes.
Properties are not allowed to have Prope
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.
Loading comments...