SIST EN 62769-5:2015

SLOVENSKI STANDARD
01-november-2015
Naprave in integracija v proizvodnih sistemih; Integracija procesne naprave - 5.
del: FDI informacijski model (IEC 62769-5:2015)
Devices and integration in enterprise systems; Field Device Integration - Part 5: FDI
Information Model (IEC 62769-5:2015)
Feldgeräteintegration (FDI) - Teil 5: FDI-Informationsmodell (IEC 62769-5:2015)
Intégration des appareils de terrain (FDI) - Partie 5: Modèle d'Information FDI (IEC
62769-5:2015)
Ta slovenski standard je istoveten z: EN 62769-5:2015
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 62769-5
NORME EUROPÉENNE
EUROPÄISCHE NORM
July 2015
ICS 25.040.40; 35.100
English Version
Field Device Integration (FDI) - Part 5: FDI Information Model
(IEC 62769-5:2015)
Intégration des appareils de terrain (FDI) - Partie 5: Modèle Feldgeräteintegration (FDI) - Teil 5: FDI-Informationsmodell
d'Information FDI (IEC 62769-5:2015)
(IEC 62769-5:2015)
This European Standard was approved by CENELEC on 2015-06-24. 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, Former Yugoslav Republic of Macedonia, France, Germany, Greece, Hungary, 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é Européen de Normalisation Electrotechnique
Europäisches Komitee für Elektrotechnische Normung
CEN-CENELEC Management Centre: Avenue Marnix 17, B-1000 Brussels
© 2015 CENELEC All rights of exploitation in any form and by any means reserved worldwide for CENELEC Members.
Ref. No. EN 62769-5:2015 E
European foreword
The text of document 65E/348/CDV, future edition 1 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 EN
62769-5:2015.
The following dates are fixed:
• latest date by which the document has to be (dop) 2016-03-24
implemented at national level by
publication of an identical national
standard or by endorsement
(dow) 2018-06-24
• latest date by which the national
standards conflicting with the
document have to be withdrawn
Attention is drawn 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.
Endorsement notice
The text of the International Standard IEC 62769-5:2015 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/TR 62541-1 NOTE Harmonized as CLC/TR 62541-1.
IEC 62541-7 NOTE Harmonized as EN 62541-7

Annex ZA
(normative)
Normative references to international publications
with their corresponding 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 (including 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.
Publication Year Title EN/HD Year

IEC 61784-1 -  Industrial communication networks - EN 61784-1 -
Profiles -- Part 1: Fieldbus profiles
IEC 61804-3 -  Function blocks (FB) for process control - -
and EDDL - Part 3: EDDL specification and
communication profiles
IEC 62541-3 -  OPC unified architecture - Part 3: Address EN 62541-3 -
Space Model
IEC 62541-4 -  OPC Unified Architecture - Part 4: Services EN 62541-4 -
IEC 62541-5 -  OPC unified architecture - Part 5: EN 62541-5 -
Information Model
IEC 62541-6 -  OPC unified architecture - Part 6: EN 62541-6 -
Mappings
IEC 62541-8 -  OPC Unified Architecture - Part 8: Data EN 62541-8 -
Access
IEC 62541-100 -  OPC unified architecture - Part 100: Device EN 62541-100 -
Interface
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
IEC 62769-5 ®
Edition 1.0 2015-05
INTERNATIONAL
STANDARD
NORME
INTERNATIONALE
colour
inside
Field Device Integration (FDI) –

Part 5: FDI Information Model
Intégration des appareils de terrain (FDI) –

Partie 5: Modèle d'Information FDI

INTERNATIONAL
ELECTROTECHNICAL
COMMISSION
COMMISSION
ELECTROTECHNIQUE
INTERNATIONALE
ICS 25.040.40; 35.100 ISBN 978-2-8322-2636-0

– 2 – IEC 62769-5:2015  IEC 2015
CONTENTS
FOREWORD . 6
INTRODUCTION . 8
1 Scope . 9
2 Normative references . 10
3 Terms, definitions, abbreviated terms, acronyms and conventions . 10
3.1 Terms and definitions . 10
3.2 Abbreviated terms and acronyms . 11
3.3 Conventions for graphical notation . 11
4 Overview of OPC Unified Architecture . 13
4.1 General . 13
4.2 Overview of OPC UA Devices . 13
5 Concepts . 15
5.1 General . 15
5.2 Device topology . 15
5.3 Online/offline . 17
5.4 Catalogue (Type Definitions) . 18
5.5 Communication . 18
6 AddressSpace organization . 18
7 Device Model for FDI . 19
7.1 General . 19
7.2 Online/offline . 19
7.3 Device health . 20
7.4 User interface elements . 20
7.4.1 General . 20
7.4.2 UI Description Type . 21
7.4.3 UI Plug-in Type . 21
7.5 Type-specific support information . 23
7.6 Actions . 23
7.6.1 Overview . 23
7.6.2 Action Type . 25
7.6.3 ActionService Type . 25
7.6.4 ActionService Object . 26
7.6.5 InvokeAction Method . 26
7.6.6 RespondAction Method . 27
7.6.7 AbortAction Method . 28
8 Network and connectivity . 28
9 Utility functions . 29
9.1 Overview. 29
9.2 Locking . 29
9.3 EditContext . 29
9.3.1 Overview . 29
9.3.2 EditContext Type . 30
9.3.3 EditContext Object . 30
9.3.4 GetEditContext Method . 30
9.3.5 RegisterNodes Method . 31

IEC 62769-5:2015  IEC 2015 – 3 –
9.3.6 Apply Method . 32
9.3.7 Reset Method . 33
9.3.8 Discard Method . 34
9.4 Direct Device Access . 34
9.4.1 General . 34
9.4.2 DirectDeviceAccess Type . 35
9.4.3 DirectDeviceAccess Object . 36
9.4.4 InitDirectAccess Method . 36
9.4.5 EndDirectAccess Method . 37
9.4.6 Transfer Method . 37
10 Parameter Types . 38
10.1 General . 38
10.2 ScalingFactor Property . 39
10.3 Min_Max_Values Property . 39
11 FDI StatusCodes . 40
12 Specialized topology elements. 40
13 Auditing . 41
13.1 General . 41
13.2 FDI Client-provided context information . 41
13.3 LogAuditTrailMessage Method . 41
14 FDI Server Version . 42
15 Mapping FDI Package information to the FDI Information Model . 42
15.1 General . 42
15.2 Localization . 43
15.2.1 Localized text . 43
15.2.2 Engineering units . 43
15.3 Device . 43
15.3.1 General . 43
15.3.2 Mapping to Attributes to a specific DeviceType Node . 43
15.3.3 Mapping to Properties . 43
15.3.4 Mapping to ParameterSet . 44
15.3.5 Mapping to Functional Groups . 44
15.3.6 Mapping to DeviceTypeImage . 44
15.3.7 Mapping to Documentation . 44
15.3.8 Mapping to ProtocolSupport . 44
15.3.9 Mapping to ImageSet . 44
15.3.10 Mapping to ActionSet . 45
15.3.11 Mapping to MethodSet . 45
15.4 Block . 45
15.4.1 General . 45
15.4.2 Mapping to Attributes . 45
15.4.3 Mapping to ParameterSet . 45
15.4.4 Mapping to Functional Groups . 45
15.4.5 Mapping to ActionSet . 46
15.4.6 Mapping to MethodSet . 46
15.4.7 Instantiation rules . 46
15.5 Parameter . 46
15.5.1 General . 46

– 4 – IEC 62769-5:2015  IEC 2015
15.5.2 Private Parameters . 49
15.5.3 MIN_Value and MAX_Value . 49
15.5.4 Engineering units . 49
15.5.5 Enumerated Parameters . 50
15.5.6 Bit-enumerated Parameters . 50
15.5.7 Representation of records . 50
15.5.8 Representation of arrays, and lists of Parameters with simple data types . 51
15.5.9 Representation of values arrays, and lists of RECORD Parameters . 52
15.5.10 Representation of COLLECTION and REFERENCE ARRAY . 52
15.5.11 SCALING_FACTOR . 52
15.6 Functional Groups. 53
15.7 AXIS elements in UIDs . 53
15.8 Actions . 54
15.9 UIPs . 54
15.10 Protocols, Networks and Connection Points . 54
Annex A (normative) Namespace and Mappings . 55
Bibliography . 56

Figure 1 – FDI architecture diagram . 9
Figure 2 – OPC UA Graphical Notation for NodeClasses. 11
Figure 3 – OPC UA Graphical Notation for References . 11
Figure 4 – OPC UA Graphical Notation Example . 12
Figure 5 – Optimized Type Reference . 12
Figure 6 – OPC UA Devices Example: Functional Groups . 14
Figure 7 – OPC UA Devices example: Configurable components . 15
Figure 8 – Example of an automation system . 16
Figure 9 – Example of a Device topology . 17
Figure 10 – Example Device Types representing a catalogue . 18
Figure 11 – Online component for access to device data . 20
Figure 12 – Hierarchy of user interface Types . 21
Figure 13 – Integration of Actions within a TopologyElement . 24
Figure 14 – Action Service . 26
Figure 15 – EditContext type and instance . 30
Figure 16 – DirectDeviceAccessType . 35
Figure 17 – DirectDeviceAccess instance . 36
Figure 18 – OPC UA VariableTypes including OPC UA DataAccess . 39
Figure 19 – Example: Complex variable representing a RECORD . 51
Figure 20 – Complex variable representing a VALUE_ARRAY of RECORDs . 52

Table 1 – UIDescriptionType Definition . 21
Table 2 – UIPlugInType Definition . 22
Table 3 – TopologyElementType with additions for Actions . 24
Table 4 – FunctionalGroupType with additions for Actions . 25
Table 5 – ActionType Definition . 25
Table 6 – ActionServiceType Definition . 25

IEC 62769-5:2015  IEC 2015 – 5 –
Table 7 – InvokeAction Method Arguments . 27
Table 8 – InvokeAction Method AddressSpace Definition . 27
Table 9 – RespondAction Method Arguments . 27
Table 10 – RespondAction Method AddressSpace Definition . 28
Table 11 – AbortAction Method Arguments . 28
Table 12 – AbortAction Method AddressSpace Definition . 28
Table 13 – EditContextType Definition . 30
Table 14 – GetEditContext Method Arguments . 31
Table 15 – GetEditContext Method AddressSpace Definition . 31
Table 16 – RegisterNodes Method Arguments . 31
Table 17 – RegisterNodes Method AddressSpace Definition . 32
Table 18 – RegistrationParameters DataType Structure . 32
Table 19 – RegisterNodesResult DataType Structure . 32
Table 20 – Apply Method Arguments . 33
Table 21 – Apply Method AddressSpace Definition . 33
Table 22 – ApplyResult DataType Structure . 33
Table 23 – Reset Method Arguments . 34
Table 24 – Reset Method AddressSpace Definition . 34
Table 25 – Discard Method Arguments . 34
Table 26 – Discard Method AddressSpace Definition . 34
Table 27 – DirectDeviceAccessType Definition . 35
Table 28 – DirectDeviceAccess Instance Definition . 36
Table 29 – InitDirectAccess Method Arguments . 37
Table 30 – InitDirectAccess Method AddressSpace Definition . 37
Table 31 – EndDirectAccess Method Arguments . 37
Table 32 – EndDirectAccess Method AddressSpace Definition. 37
Table 33 – Transfer Method Arguments . 38
Table 34 – Transfer Method AddressSpace Definition . 38
Table 35 – ScalingFactor Property Definition . 39
Table 36 – Min_Max_Values Property Definition . 40
Table 37 – Variant_Range DataType Structure . 40
Table 38 – Variant_Range Definition . 40
Table 39 – Good operation level result codes . 40
Table 40 – LogAuditTrailMessage Method Arguments . 42
Table 41 – LogAuditTrailMessage Method AddressSpace Definition . 42
Table 42 – FDIServerVersion Property Definition . 42
Table 43 – DeviceType Property Mapping . 44
Table 44 – Setting OPC UA Variable Attributes from EDDL variable attributes . 47
Table 45 – Correspondence between EDDL and OPC UA standard data types . 47

– 6 – IEC 62769-5:2015  IEC 2015
INTERNATIONAL ELECTROTECHNICAL COMMISSION
____________
FIELD DEVICE INTEGRATION (FDI) –

Part 5: FDI 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.
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.
The text of this standard is based on the following documents:
CDV Report on voting
65E/348/CDV 65E/425/RVD
Full information on the voting for the approval of this standard can be found in the report on
voting indicated in the above table.
This publication 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.

IEC 62769-5:2015  IEC 2015 – 7 –
The committee has decided that the contents of this publication will remain unchanged until
the stability date indicated on the IEC web site under "http://webstore.iec.ch" in the data
related to the specific publication. At this date, the publication 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.
– 8 – IEC 62769-5:2015  IEC 2015
INTRODUCTION
The International Electrotechnical Commission (IEC) draws attention to the fact that it is
claimed that compliance with this document may involve the use of patents concerning
a) Method for the Supplying and Installation of Device-Specific Functionalities, see Patent
Family DE10357276;
b) Method and device for accessing a functional module of automation system, see Patent
Family EP2182418;
c) Methods and apparatus to reduce memory requirements for process control system
US2013232186;
software applications, see Patent Family
d) Extensible Device Object Model, see Patent Family US12/893,680.
IEC takes no position concerning the evidence, validity and scope of this patent right.
The holders of these patent rights have assured the IEC that he/she is willing to negotiate
licences either free of charge or under reasonable and non-discriminatory terms and
conditions with applicants throughout the world. In this respect, the statement of the holder of
this patent right is registered with IEC. Information may be obtained from:
a) ABB Research Ltd
Claes Rytoft
Affolterstrasse 4
Zurich, 8050
Switzerland
b) Phoenix Contact GmbH & Co KG
Intellectual Property, Licenses & Standards
Flachsmarktstrasse 8, 32825 Blomberg
Germany
c) Fisher Controls International LLC
John Dilger, Emerson Process Management LLLP
st
301 S. 1 Avenue, Marshaltown, Iowa 50158
USA
d) Rockwell Automation Technologies, Inc.
1 Allen-Bradley Drive
Mayfield Heights, Ohio 44124
USA
Attention is drawn to the possibility that some of the elements of this document may be the
subject of patent rights other than those identified above. IEC shall not be held responsible for
identifying any or all such patent rights.
ISO (www.iso.org/patents) and IEC (http://patents.iec.ch) maintain on-line data bases of
patents relevant to their standards. Users are encouraged to consult the data bases for the
most up to date information concerning patents.

IEC 62769-5:2015  IEC 2015 – 9 –
FIELD DEVICE INTEGRATION (FDI) –

Part 5: FDI 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 some kind of 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.
User Interface
FDI Package
Description
FDI Package
User
Device Business User
Interface
Definition Interface
User Logic User
Plug-in
FDI Client Device Business
Interface Interface
Definition Logic
Description Plug-in
UID
Interpreter
UID
FDI Server
UIP
Information Model Management
Services
Information Model Business Logic
User Interface Processor
OPC UA
Plug-in
Device Object
Business
Device Object
Logic
Device Object
User Interface Services
Platform UI Services
(Drawing, Input Devices)
System Services
OPC UA
Services
OPC UA Client OPC UA
Services
System
Communication
Communication
Hardware
Server
Specified by this part of this International Standard Data
Store
Specified by other parts of this International Standard
Not specified by this International Standard
IEC
Figure 1 – FDI architecture diagram
OPC UA
Hosting Services
Device Access
Services
OPC UA Services
Business Logic
Interface
– 10 – IEC 62769-5:2015  IEC 2015
2 Normative references
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 (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 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
NOTE IEC 62769-1 is technically identical to FDI-2021
IEC 62769-2, Field Device Integration (FDI) – Part 2: FDI Client
NOTE IEC 62769-2 is technically identical to FDI-2022
IEC 62769-4, Field Device Integration (FDI) – Part 4: FDI Packages
NOTE IEC 62769-4 is technically identical to FDI-2024
IEC 62769-7, Field Device Integration (FDI) – Part 7: FDI Communication Devices
NOTE IEC 62769-7 is technically identical to FDI-2027
3 Terms, definitions, abbreviated terms, acronyms and conventions
3.1 Terms and definitions
For the purposes of this document, the terms and definitions given in IEC 62769-1 apply.
—————————
To be published.
Under consideration.
IEC 62769-5:2015  IEC 2015 – 11 –
3.2 Abbreviated terms and acronyms
For the purposes of this document, the abbreviated terms and acronyms given in IEC 62769-1
as well as the following apply.
HMI Human Machine Interface
SCADA Supervisory Control and Data Acquisition
TCP Transmission Control Protocol
3.3 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 standard.
NodeClasses representing types always have a shadow.
Object ObjectType
Variable VariableType
Method DataType
ReferenceType
IEC
Figure 2 – OPC UA Graphical Notation for NodeClasses
Figure 3 shows the symbols for the ReferenceTypes used in this standard. 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.
HasInputVars
HasComponent
HasProperty
HasTypeDefinition
HasSubType
Hierarchical
Reference
NonHierarchical
Reference
IEC
Figure 3 – OPC UA Graphical Notation for References

– 12 – IEC 62769-5:2015  IEC 2015
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).
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
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.
ObjectType_Y:
Object_B
BaseVariableType:
Variable_1
AnalogItemType:
Variable_2
Method_1
IEC
Figure 5 – Optimized Type Reference

IEC 62769-5:2015  IEC 2015 – 13 –
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 into 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.
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 Properties defined for them. An example for Properties of
Objects is the Manufacturer Property of a Device.
DataVariables represent the contents of an Object. DataVariables may have component
DataVariables. This is typically used by Servers to expose individual elements of arrays and
structures. This standard uses
...