EN IEC 62769-3:2023

SLOVENSKI STANDARD
01-november-2023
Integracija procesne naprave (FDI®) - 3. del: Strežnik (IEC 62769-3:2023)
Field Device Integration (FDI®) - Part 3: Server (IEC 62769-3:2023)
Feldgeräteintegration (FDI®) - Teil 3: FDI-Server (IEC 62769-3:2023)
Intégration des appareils de terrain (FDI®) - Partie 3: Serveur (IEC 62769-3:2023)
Ta slovenski standard je istoveten z: EN IEC 62769-3:2023
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-3

NORME EUROPÉENNE
EUROPÄISCHE NORM May 2023
ICS 25.040.40; 35.100.05 Supersedes EN IEC 62769-3:2021
English Version
Field Device Integration (FDI®) - Part 3: Server
(IEC 62769-3:2023)
Intégration des appareils de terrain (FDI®) - Partie 3: Feldgeräteintegration (FDI®) - Teil 3: FDI-Server
Serveur (IEC 62769-3:2023)
(IEC 62769-3:2023)
This European Standard was approved by CENELEC on 2023-05-09. 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,
Türkiye 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
© 2023 CENELEC All rights of exploitation in any form and by any means reserved worldwide for CENELEC Members.
Ref. No. EN IEC 62769-3:2023 E

European foreword
The text of document 65E/856/CDV, future edition 3 of IEC 62769-3, 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) 2024-02-09
level by publication of an identical national standard or by endorsement
• latest date by which the national standards conflicting with the (dow) 2026-05-09
document have to be withdrawn
This document supersedes EN IEC 62769-3:2021 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.
Any feedback and questions on this document should be directed to the users’ national committee. A
complete listing of these bodies can be found on the CENELEC website.
Endorsement notice
The text of the International Standard IEC 62769-3:2023 was approved by CENELEC as a European
Standard without any modification.
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.cencenelec.eu.
Publication Year Title EN/HD Year
IEC 61804-3 - Devices and integration in enterprise systems - EN IEC 61804-3 -
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 systems - EN IEC 61804-4 -
Function blocks (FB) for process control and
electronic device description language (EDDL)
- Part 4: EDD interpretation
IEC 61804-5 - Devices and intergration in enterprise systems EN IEC 61804-5 -
- Function blocks (FB) for process control and
electronic device description language (EDDL)
- Part 5: EDDL Builtin library
IEC 62541-4 - OPC Unified Architecture - Part 4: Services EN IEC 62541-4 -
IEC 62541-7 - OPC unified architecture - Part 7: Profiles EN IEC 62541-7 -
IEC 62769-1 - Field Device Integration (FDI®) - Part 1: - -
Overview
IEC 62769-2 - Field Device Integration (FDI®) - Part 2: Client - -
IEC 62769-4 - Field Device Integration (FDI®) - Part 4: FDI - -
Packages
IEC 62769-5 - Field Device Integration (FDI®) - Part 5: FDI - -
Information Model
IEC 62769-7 - Field Device Integration (FDI®) - Part 7: - -
Communication Devices
IEC 62769-3 ®
Edition 3.0 2023-04
INTERNATIONAL
STANDARD
NORME
INTERNATIONALE
colour
inside
Field device integration (FDI®) –

Part 3: Server
Intégration des appareils de terrain (FDI®) –

Partie 3: Serveur
INTERNATIONAL
ELECTROTECHNICAL
COMMISSION
COMMISSION
ELECTROTECHNIQUE
INTERNATIONALE
ICS 25.040.40; 35.100.05 ISBN 978-2-8322-6446-1

– 2 – IEC 62769-3:2023 © IEC 2023
CONTENTS
FOREWORD . 5
1 Scope . 7
2 Normative references . 7
3 Terms, definitions, abbreviated terms and acronyms . 8
3.1 Terms and definitions . 8
3.2 Abbreviated terms and acronyms . 8
3.3 Conventions . 9
4 Overview . 9
5 Information Model . 9
5.1 General . 9
5.2 Online/Offline . 10
5.2.1 Overview . 10
5.2.2 Transfer to device . 10
5.2.3 Transfer from device . 11
5.2.4 Interactive Transfer to device . 11
5.3 Access privileges . 11
5.4 Private Parameters . 11
5.5 Locking . 12
5.6 EditContext . 13
5.6.1 Concept and usage model . 13
5.6.2 Services . 14
5.6.3 NodeIds . 14
5.6.4 Reading . 14
5.6.5 Writing . 15
5.6.6 Writing dominant and dependent Variables . 15
5.6.7 Actions (EDD METHODS) . 16
5.6.8 UIDs . 16
5.6.9 Synchronization . 17
5.7 Reading . 17
5.7.1 General . 17
5.7.2 Reading offline variables . 18
5.7.3 Reading online variables . 18
5.8 Writing . 19
5.8.1 General . 19
5.8.2 Write offline variables . 20
5.8.3 Writing online variables . 21
5.8.4 Writing to an EditContext . 22
5.9 Subscription . 23
5.9.1 General . 23
5.9.2 Subscription of offline variables . 24
5.9.3 Subscription of online variables . 25
5.10 Device topology . 26
5.10.1 General . 26
5.10.2 Connection Points . 26
5.10.3 Topology management . 27
5.10.4 Topology scanning . 30
5.10.5 Use of SCAN function . 31

IEC 62769-3:2023 © IEC 2023 – 3 –
5.10.6 Validation of defined topology . 31
5.11 User Interface Elements . 32
5.11.1 User Interface Descriptions. 32
5.11.2 User Interface Plug-ins . 33
5.12 Actions . 33
® ®
5.12.1 FDI Server – FDI Client interaction . 33
5.12.2 Action state machine . 36
5.12.3 Actions Proxies . 37
5.12.4 INTERACTIVE_TRANSFER_TO_DEVICE Action . 38
5.12.5 Actions, EDD Actions and Actions Proxies . 39
6 OPC UA services . 40
6.1 OPC UA profiles . 40
6.2 Service error information . 40
6.2.1 Overview . 40
6.2.2 OPC UA services and their response . 40
6.2.3 Mappings of EDDL response codes to OPC UA service response . 41
6.3 Parameter value update during write service request . 42
6.4 Localization . 42
6.5 Audit events . 42
7 Communication . 42
7.1 Notation . 42
7.2 General . 43
7.2.1 Concepts . 43
7.2.2 Terms . 45
7.3 Communication Service processing . 46
7.3.1 Communication Service invocation . 46
7.3.2 Analyze communication path . 46
7.3.3 Manage communication relations . 47
7.3.4 Communication service request mapping . 47
7.3.5 Communication service request propagation . 48
7.3.6 Communication error handling . 49 ®
7.4 FDI Communication Server specific handling . 49
7.4.1 Discovery . 49
7.4.2 Information Model synchronization . 50 ®
8 Parallel Execution within the FDI Server . 50
8.1 Motivation . 50
8.2 Internal structure of the EDD interpreter. 51
8.3 Rules for running an EDD entity . 51 ®
Annex A (informative) FDI Server functional structure . 53 ®
A.1 FDI functional elements . 53 ®
A.2 FDI Server extension . 54
Annex B (informative) Access privileges and user roles . 56
B.1 User roles and usage case . 56
B.2 Private data usage . 57 ®
Annex C (informative) Parallel execution within the FDI Server – Examples . 58
C.1 Simple example for a synchronous execution . 58
C.2 Example for a concurrent execution . 58
C.3 Deadlock detection in concurrent execution . 60

– 4 – IEC 62769-3:2023 © IEC 2023
Annex D (informative) Read-Only mode for UID Views . 61
D.1 Definition . 61
®
Figure 1 – FDI architecture diagram . 7
Figure 2 – Locking services . 12
Figure 3 – EditContext models . 13
Figure 4 – Online EditContext state diagram for dominant and dependent Variables . 15
Figure 5 – Offline EditContext state diagram for dominant and dependent Variables . 16
Figure 6 – EditContext for EDD Methods . 16
Figure 7 – Offline variable read . 18
Figure 8 – Online variable read . 19
Figure 9 – Offline variable write immediate . 20
Figure 10 – Online variable write immediate . 21
Figure 11 – Write with EditContext . 23
Figure 12 – Offline variable subscription . 24
Figure 13 – Online variable subscription . 25
Figure 14 – Topology with Network objects (non-normative) . 26
Figure 15 – Add Device to topology . 28
Figure 16 – Remove Device from topology . 29
Figure 17 – Scan topology . 30
Figure 18 – Action execution . 35
Figure 19 – Action state machine . 36
Figure 20 – System communication integration example . 43 ®
Figure 21 – FDI Communication Server integration example . 44
Figure 22 – Gateway integration example . 45
Figure 23 – Message propagation example scenario . 48 ®
Figure A.1 – Functional components of an FDI Server . 53 ®
Figure A.2 – FDI Server extensions . 55
Figure B.1 – User roles and access privileges . 56
Figure C.1 – Synchronous execution of two triggers . 58
Figure C.2 – Concurrent execution of two triggers (step1) . 58
Figure C.3 – Concurrent execution of two triggers (step 2) . 59
Figure C.4 – Concurrent execution of two triggers (step 3) . 59
Figure C.5 – Concurrent execution of two triggers (step 4) . 59
Figure C.6 – Concurrent execution of two triggers. 60

Table 1 – Action states . 36
Table 2 – Action state transitions . 37
Table 3 – EDD Action types and the EDD constructs that use them . 39
Table 4 – OPC UA severity bits and EDDL response codes TYPE . 41

IEC 62769-3:2023 © IEC 2023 – 5 –
INTERNATIONAL ELECTROTECHNICAL COMMISSION
____________ ®
FIELD DEVICE INTEGRATION (FDI ) –

Part 3: Server
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.
IEC 62769-3 has been prepared by subcommittee 65E: Devices and integration in enterprise
systems, of IEC technical committee 65: Industrial-process measurement, control and
automation. It is an International Standard.
This third edition cancels and replaces the second edition published in 2021. This edition
constitutes a technical revision.
This edition includes the following significant technical changes with respect to the previous
edition:
a) added interactive transfer to device.

– 6 – IEC 62769-3:2023 © IEC 2023
The text of this International Standard is based on the following documents:
Draft Report on voting
65E/856/CDV 65E/913/RVC
Full information on the voting for its approval can be found in the report on voting indicated in
the above table.
The language used for the development of this International Standard is English.
This document was drafted in accordance with ISO/IEC Directives, Part 2, and developed in
accordance with ISO/IEC Directives, Part 1 and ISO/IEC Directives, IEC Supplement, available
at www.iec.ch/members_experts/refdocs. The main document types developed by IEC are
described in greater detail at www.iec.ch/standardsdev/publications.
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.
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 document 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-3:2023 © IEC 2023 – 7 – ®
FIELD DEVICE INTEGRATION (FDI ) –

Part 3: Server
1 Scope
®1 ®
This part of IEC 62769 specifies the FDI Server. 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 figure. Annex A provides a functional description of the FDI Server.
®
Figure 1 – FDI architecture diagram
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.
___________
1 ®
FDI is a registered trademark of the non-profit organization Fieldbus Foundation, Inc. This information is given
for the convenience of users of this document and does not constitute an endorsement by IEC of the trademark
holder or any of its products. Compliance does not require use of the trade name. Use of the trade name requires
permission of the trade name holder.

– 8 – IEC 62769-3:2023 © IEC 2023
For undated references, the latest edition of the referenced document (including any
amendments) applies.
IEC 61804-3, Devices and integration in enterprise 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 systems − Function blocks (FB) for process
control and electronic device description language (EDDL) − Part 4: EDD interpretation
IEC 61804-5, Devices and integration in enterprise systems − Function blocks (FB) for process
control and electronic device description language (EDDL) − Part 5: EDDL Builtin library
IEC 62541-4, OPC unified architecture – Part 4: Services
IEC 62541-7, OPC unified architecture – Part 7: Profiles ®
) – Part 1: Overview
IEC 62769-1, Field Device Integration (FDI ®
IEC 62769-2, Field Device Integration (FDI ) – Part 2: Client
® ®
IEC 62769-4, Field Device Integration (FDI ) – Part 4: FDI Packages
® ®
IEC 62769-5, Field Device Integration (FDI ) – Part 5: FDI Information Model ®
IEC 62769-7, Field Device Integration (FDI ) – Part 7: Communication Devices
3 Terms, definitions, abbreviated terms and acronyms
3.1 Terms and definitions
For the purposes of this document, the terms and definitions given in IEC 62769-1 as well as
the following apply.
ISO and IEC maintain terminology databases for use in standardization at the following
addresses:
• IEC Electropedia: available at https://www.electropedia.org/
• ISO Online browsing platform: available at https://www.iso.org/obp
3.1.1
Actions Proxy ®
internal FDI Server entity that encapsulates all the EDD Methods specified in an EDD Action
definition
3.1.2
Connection Point
logical representation of a connection of a communication end point to a communication
network
3.2 Abbreviated terms and acronyms
For the purposes of this document, the abbreviated terms and acronyms given in IEC 62769-1
apply.
IEC 62769-3:2023 © IEC 2023 – 9 –
3.3 Conventions ®
Capitalization of the first letter of words is used in the IEC 62769 series to emphasize an FDI
defined term.
4 Overview ®
The structure for an FDI Server is shown in Figure 1.
® ®
FDI Servers that support connectivity with third-party FDI Clients shall support OPC UA. A
® ® ®
vendor can provide both an FDI Server and one or more FDI Clients. In this case, the FDI ®
Clients can communicate with the FDI Server through proprietary protocols. ®
An FDI Server communicates with devices via Native Communication (see 7.2.1) and/or
Communication Devices (see IEC 62769-7).
® ®
An FDI Server provides information to FDI Clients through an Information Model
(see IEC 62769-5) as follows.
• The Information Model includes information about Device Types and Device Instances. The
information for a Device Instance includes offline data (engineering data), as well as online
data (values from the physical device). ®
• The Information Model is created using information from FDI Packages. However, not all ®
Package is reflected in the Information Model.
of the information in an FDI ®
• Referential integrity of the Information Model is maintained using information from FDI
Packages. ®
• FDI Packages can contain Attachments that contain device manuals and protocol specific
information (see IEC 62769-4). Those Attachments, including device manuals and protocol
specific support files, are exposed via the Information Model. ®
• FDI Device Packages contain information about device types (see IEC 62769-4). Each
device type defined in a package is mapped to a distinct DeviceType node in the Information
Model.
® ®
• FDI Profile Packages are used to provide interaction with devices for which an FDI Device
Package does not exist (see IEC 62769-4). ®
• Multiple revisions of an FDI Package generate distinct DeviceType nodes in the Information
Model (see IEC 62769-4).
® ®
FDI Packages contain digital signatures that allow an FDI Server to authenticate their
contents (see IEC 62769-4).
® ® ®
An FDI Server shall verify the FDI Technology Version (see IEC 62769-1) of any FDI
® ®
Package it uses to ensure the FDI Package is compatible with the FDI Server.
5 Information Model
5.1 General
® ®
The FDI Server shall use the Device Definition of an FDI Package to maintain the Information
Model.
The Device Definition can contain conditional expressions. Conditional expressions are used
when a certain aspect of the Device Definition is not static but rather is dependent on the state ®
of the device. Whenever the online or offline values of a Device Instance are modified, the FDI
Server shall re-evaluate the relevant conditional expressions and modify the Information Model
accordingly.
– 10 – IEC 62769-3:2023 © IEC 2023
The evaluation of conditional expressions can invalidate variables in the Information Model. ®
The FDI Server shall change the AccessLevel attribute of invalidated variables such that they
are neither readable nor writable and the status of these variables shall be set to bad. Read
and write service requests for invalidated variables shall return a failure.
The Device Definition can specify relationships between variables in a device. These
relationships can impact the value of variables in the Information Model.
® ®
The FDI Server shall generate DataChange Notifications to any FDI Clients that are
subscribing to Information Model elements that have changed.
® ®
FDI Packages provide Business Logic that is used by the FDI Server to maintain the integrity ®
of the Information Model. The Business Logic specified in an FDI Package can invoke built-in ®
functions that shall be implemented by the FDI Server. The built-in functions that shall be ®
Server are specified in IEC 61804-5.
implemented by the FDI
5.2 Online/Offline
5.2.1 Overview ®
The Information Model maintained by the FDI Server contains online and offline values. The
online values reflect values in a physical component/device. The offline values reflect values
stored in a configuration database. ®
The offline values are updated through write service requests from an FDI Client or Business
® ®
Logic executed by the FDI Server. The offline values are not updated when the FDI Server
reads data from the device or writes data to the device.
The online values in the Information Model are not updated through write service requests.
Successful write service requests through the Information Model result in value changes in the
physical devices. The online values in the Information Model will then be updated as a result of
read service requests or subscriptions. ®
FDI Servers can provide a server-specific mechanism for creating Device Instances without ®
the presence of physical hardware. The FDI Server creates these instances using information ®
in FDI Packages. All read/write requests for online values for Device Instances with no physical
device shall return an error.
The transfer of information between the offline values and the physical device is supported
through the TransferToDevice, TransferFromDevice in the Information Model, and the
INTERACTIVE_TRANSFER_TO_DEVICE_ACTION implementing the transfer including user
interaction. These Methods shall implement the download and upload procedures, respectively,
as specified in IEC 61804-4. When no implementation is provided based on IEC 61804-4, then
these Methods shall return Bad_NotSupported, as per IEC 62541-4.
The Device shall have been locked prior to invoking these methods, as specified in
IEC 62769-5.
5.2.2 Transfer to device
The TransferToDevice method shall implement the download procedure as specified in
IEC 61804-4. This transfers the offline values to the physical device. ®
As a general rule, the FDI Server should not change the Online variable node when writing a
value to the device. The Online variable node should be updated only in the process of read ®
operations or subscriptions. Notwithstanding, as specified in IEC 62769-5, the FDI Server will
reset any cached Value for the target Nodes in the Information Model so that they will be re-
read next time they are requested.

IEC 62769-3:2023 © IEC 2023 – 11 –
The status information returned for each variable included in the write service request is used
to compose the TransferResult, as specified in IEC 62769-5.
5.2.3 Transfer from device
The TransferFromDevice method shall implement the upload procedure as specified in
IEC 61804-4. This transfers the values from the physical device to the offline values.
If any read operations from the device fail during upload, the corresponding offline value shall
not be modified.
The status information returned for each variable included in the read service request is used
to compose the TransferResult, as specified in IEC 62769-5.
5.2.4 Interactive Transfer to device ®
The FDI Server implements the Interactive Transfer to Device as specified in IEC 61804-4.
This transfers the offline values to the physical device. In contrast to the non-interactive
download performed with the TransferToDevice method, the interactive download may invoke
user interaction just before the download starts and after the download has been performed.
The Interactive Transfer to device is started by an invocation of the ®
Client using the InvokeAction
INTERACTIVE_TRANSFER_TO_DEVICE_ACTION by the FDI
service. ®
As a general rule, the FDI Server should not change the Online variable node when writing a
value to the device. The Online variable node should be updated only in the process of read ®
operations or subscriptions. Notwithstanding, as specified in IEC 62769-5, the FDI Server will
reset any cached Value for the target Nodes in the Information Model so that they will be re-
read next time they are requested.
5.3 Access privileges
Systems implement security and access policies based on a number of characteristics such as
® ®
user role and plant area. FDI Servers use these policies, along with information in FDI
Packages, to determine the access privileges granted to the user. ®
The elements of an FDI Package can be associated with one or more usage attributes. The ®
FDI Server uses these attributes to set the UserAccessLevel attribute of Variables and the ®
UserExecutable attribute of Methods. The usage attributes in an FDI Package are simply hints
® ®
Server, i.e., they may be disregarded or overridden by the FDI Server.
to be used by the FDI
See also Annex B.
5.4 Private Parameters ®
The Parameters and Actions specified in an FDI Package can be declared private. Private
Parameters and Actions shall not be browsable; they shall only be accessible through ®
references from other elements of an FDI Package. ®
More specifically, the FDI Server shall support private Parameters and Actions as follows. ®
• The FDI Server shall create nodes in the Information Model for the private Parameters and
Actions. ®
• The FDI Server shall not include information about private Parameters and Actions in a
response to a Browse, BrowseNext, QueryFirst, or QueryNext service request. ®
• The FDI Server shall return the NodeIds of private Parameters and Actions when the name
of a private Parameter or Action is passed to TranslateBrowsePathsToNodeIds. ®
• The FDI Server shall process a read/write service request for a private Parameter in the
same way as it does for public (browsable) Parameters (see 5.7 and 5.8).

– 12 – IEC 62769-3:2023 © IEC 2023 ®
• The FDI Server shall execute private Actions in the same way as it does public (browsable)
Actions (see 5.12).
An example of private parameters is parameters that should only be modified through an Action.
® ®
These parameters should not be visible to FDI Clients to prevent direct access. FDI Clients
invoke Actions to access these private parameters.
5.5 Locking
® ®
The FDI Server provides locking services to grant FDI Clients exclusive access to Device and
Network elements in the Information Model. The locking services consist of a set of Methods
and status information. The methods, and their behaviour, are specified in IEC 62769-5. ®
The following behaviour shall be implemented by the FDI Server to support locks.
• Locking applies to both online and offline nodes. ®
• Once locked by one FDI Client, any attempt to write to a Parameter or to execute an Action ®
by another FDI Client shall be rejected.
• Locking is not required for read services.
® ®
• Parameters that are locked by one FDI Client can still be read by other FDI Clients, i.e.,
read requests on a Parameter that is locked are not rejected. ®
Internal use of the locking mechanism for maintaining the Information Model integrity is FDI
Server vendor specific.
Figure 2 illustrates a locking sequence with multiple service invocations during the locked state.

Figure 2 – Locking services
A service request that requires locking shall fail either partially or completely if no lock has been
® ®
acquired by the FDI Client via InitLock prior to requesting the service. The FDI Client has to
release the lock via ExitLock after all service requests have been completed.
NOTE A write operation will partially fail, i.e., it will return a status code for each variable in the set of variables to
be written since some can belong to devices that are locked and some to devices that are not locked. ®
FDI Servers may queue InitLock requests until a service for which a lock has been created
completes and the lock has been released. However, such an optimization is not part of the ®
standard behaviour required of an FDI Server.

IEC 62769-3:2023 © IEC 2023 – 13 –
5.6 EditContext
5.6.1 Concept and usage model ®
The FDI Server provides the EditContext model to interact with Clients during their editing
task. The concept is closely related to UIDs and fulfills the needs for Server-driven UI dialogs
based on EDDL rules.
An EditContext can be used to make changes to Variable Values visible to the Server without
applying them to the online or offline representation of a Device. The Server will apply business
logic associated to the edited Variable which – in some cases – causes changes to other
Variable Values (e.g. if an engineering unit is changed) or the UID (e.g. a Variable becomes
invisibl
...