EN IEC 62769-100:2020

SLOVENSKI STANDARD
01-februar-2021
Vključitev procesne terenske naprave (FDI) - 100. del: Profili - Splošni protokoli
(IEC 62769-100:2020)
Field device integration (FDI) - Part 100: Profiles - Generic protocolsi (IEC 62769-
100:2020)
Feldgeräteintegration (FDI) - Teil 100: Profile - Allgemeine Protokolle (IEC 62769-
100:2020)
Intégration des appareils de terrain (FDI) - Partie 100: Profils - Protocoles génériques
(IEC 62769-100:2020)
Ta slovenski standard je istoveten z: EN IEC 62769-100:2020
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-100

NORME EUROPÉENNE
EUROPÄISCHE NORM
November 2020
ICS 25.040.40; 35.100.05
English Version
Field device integration (FDI) - Part 100: Profiles - Generic
protocols
(IEC 62769-100:2020)
Intégration des appareils de terrain (FDI) - Partie 100: Feldgeräteintegration (FDI) - Teil 100: Profile - Allgemeine
Profils - Protocoles génériques Protokolle
(IEC 62769-100:2020) (IEC 62769-100:2020)
This European Standard was approved by CENELEC on 2020-10-29. 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
© 2020 CENELEC All rights of exploitation in any form and by any means reserved worldwide for CENELEC Members.
Ref. No. EN IEC 62769-100:2020 E

European foreword
The text of document 65E/739/FDIS, future edition 1 of IEC 62769-100, 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-07-29
level by publication of an identical national standard or by endorsement
• latest date by which the national standards conflicting with the (dow) 2023-10-29
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 shall not be held responsible for identifying any or all such patent rights.
Endorsement notice
The text of the International Standard IEC 62769-100:2020 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.cenelec.eu.
Publication Year Title EN/HD Year
IEC 61804 series Function blocks (FB) for process control and EN IEC 61804 series
electronic device description language
(EDDL)
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 62541-100 2015 OPC Unified Architecture - Part 100: Device EN 62541-100 2015
Interface
IEC 62769-2 - Field Device Integration (FDI) - Part 2: FDI - -
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: FDI - -
Communication Devices
IEC 62769-100 ®
Edition 1.0 2020-09
INTERNATIONAL
STANDARD
NORME
INTERNATIONALE
Field device integration (FDI) –

Part 100: Profiles – Generic protocols

Intégration des appareils de terrain (FDI) –

Partie 100: Profils – Protocoles génériques

INTERNATIONAL
ELECTROTECHNICAL
COMMISSION
COMMISSION
ELECTROTECHNIQUE
INTERNATIONALE
ICS 25.040.40; 35.100.05 ISBN 978-2-8322-8858-0

– 2 – IEC 62769-100:2020 © IEC 2020
CONTENTS
FOREWORD . 4
1 Scope . 6
2 Normative references . 6
3 Terms, definitions, abbreviated terms and conventions . 6
3.1 Abbreviated terms . 7
3.2 Conventions . 7
3.2.1 EDDL syntax. 7
3.2.2 XML syntax . 7
3.2.3 Capitalizations . 7
4 Profile for Generic Protocols . 8
4.1 General . 8
4.2 Catalog profile . 8
4.2.1 Protocol support file . 8
4.2.2 CommunicationProfile definition . 8
4.2.3 Profile device . 8
4.2.4 Protocol version information . 9
4.3 Associating a Package with a device . 9
4.3.1 Device type identification mapping . 9
4.3.2 Device type revision mapping . 10
4.4 Information Model mapping . 10
4.4.1 ProtocolType definition . 10
4.4.2 DeviceType mapping . 11
4.4.3 FunctionalGroup identification definition . 11
4.5 Topology elements . 12
4.5.1 ConnectionPoint definition . 12
4.5.2 Communication Device definition . 13
4.5.3 Communication service provider definition . 14
4.5.4 Network definition . 14
4.6 Methods . 15
4.6.1 Methods for FDI Communication Servers . 15
4.6.2 Methods for Gateways . 19
4.6.3 Transfer service parameters . 26
Annex A (normative) Topology Scan result schema . 27
A.1 General . 27
A.2 Network . 27
A.3 GenericNetworkT . 27
A.4 GenericConnectionPointT . 27
A.5 GenericIdentificationT . 28
A.6 GenericAddressT . 29
Annex B (normative) Transfer service parameters . 30
B.1 General . 30
B.2 sendData . 30
B.3 receiveData . 30
B.4 TransferSendDataT . 30
B.5 EddDataTypeInfoListT . 31

IEC 62769-100:2020 © IEC 2020 – 3 –
B.6 EddDataTypeInfoT . 31
B.7 EddDataTypeT . 32
B.8 TransferResultDataT . 33
Annex C (normative) Protocol-specific definitions . 34
C.1 General . 34
C.2 Header . 34
C.3 ProtocolIdentifier . 34
C.4 Address . 34
C.5 Manufacturer . 34
C.6 DeviceModel . 35
C.7 DeviceRevision . 35
C.8 SerialNumber . 35
C.9 Tag . 35
C.10 ProfileId . 35
C.11 Version . 36
C.12 ProtocolSupportFile . 36
Bibliography . 37

Table 1 – ProtocolSupportFile for FDI Device Packages . 8
Table 2 – Catalog values for profile devices . 9
Table 3 – Device identification information mapping . 10
Table 4 – Device revision information mapping . 10
Table 5 – Protocol type GenericProtocol . 11
Table 6 – Inherited DeviceType property mapping . 11
Table 7 – Generic Protocol Device Types identification attributes . 12
Table 8 – ConnectionPoint type for Generic Protocols . 12
Table 9 – Method Connect arguments . 15
Table 10 – Method Disconnect arguments . 16
Table 11 – Method Transfer arguments . 17
Table 12 – EddDataTypeInfo DataType Structure . 17
Table 13 – EddDataTypeEnum Values . 18
Table 14 – Method SetAddress arguments . 19
Table 15 – Connect service arguments . 20
Table 16 – Method Transfer arguments . 22
Table 17 – Method SetAddress arguments . 25
Table A.1 – Elements of GenericNetworkT . 27
Table A.2 – Attributes of GenericConnectionPointT . 28
Table A.3 – Elements of GenericConnectionPointT . 28
Table A.4 – Attributes of GenericIdentificationT . 29
Table B.1 – Attributes of TransferSendDataT . 31
Table B.2 – Elements of TransferSendDataT . 31
Table B.3 – Elements of EddDataTypeInfoListT . 31
Table B.4 – Attributes of EddDataTypeInfoT . 32
Table B.5 – Enumerations of EddDataTypeT . 33
Table B.6 – Attributes of TransferResultDataT . 33

– 4 – IEC 62769-100:2020 © IEC 2020
INTERNATIONAL ELECTROTECHNICAL COMMISSION
____________
FIELD DEVICE INTEGRATION (FDI) –

Part 100: Profiles – Generic protocols

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-100 has been prepared by subcommittee 65E: Devices and
integration in enterprise systems, of IEC technical committee 65: Industrial-process
measurement, control and automation.
FCG TS62769-100 Edition 1.1, Field Device Integration Part 100: Profiles – Generic
Protocols, a specification of the FieldComm Group, PROFIBUS Nutzerorganisation e. V., OPC
Foundation and FDT Group, serves as a basis for the elaboration of this standard.
The text of this International Standard is based on the following documents:
FDIS Report on voting
65E/739/FDIS 65E/743/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.

IEC 62769-100:2020 © IEC 2020 – 5 –
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.
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.
– 6 – IEC 62769-100:2020 © IEC 2020
FIELD DEVICE INTEGRATION (FDI) –

Part 100: Profiles – Generic protocols

1 Scope
This part of IEC 62769 specifies an FDI profile of IEC 62769 for generic protocols. That
means that all interfaces are defined, and a host can add support for more protocols without
changing its implementation. Nevertheless, there are some protocol-specific definitions (PSD)
that need to be specified per protocol using this profile. Annex C specifies what PSDs need to
be defined per protocol so that FDI Device Packages, FDI Communication Packages for
Gateways and FDI Communication Servers, FDI Communication Servers, Gateways and
Devices supporting such a protocol can work together in a host not aware about this specific
protocol.
NOTE A host not using an FDI Communication Server but a proprietary mechanism for communication defines its
own means to deal with this profile to support several protocols without changing its implementation. This is
specific to the proprietary way how the communication driver is bound to the host.
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 61804 (all parts), Function blocks (FB) for process control and Electronic Device
Description Language (EDDL)
IEC 61804-3, Function blocks (FB) for process control and Electronic Device Description
Language (EDDL) – Part 3: EDDL syntax and semantics
IEC 62541-100:2015, OPC Unified Architecture – Part 100: OPC UA for Devices
IEC 62769-2, Field Device Integration (FDI) – Part 2: FDI 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: FDI Communication Devices
3 Terms, definitions, abbreviated terms and conventions
For the purposes of this document, the terms and definitions given in IEC 61804 series,
IEC 62541-100, IEC 62769-2, IEC 62769-4, IEC 62769-5 and IEC 62769-7 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

IEC 62769-100:2020 © IEC 2020 – 7 –
3.1 Abbreviated terms
EDD electronic device description
EDDL Electronic Device Description Language (see IEC 61804)
FDI™ Field Device Integration™
FCG FieldComm Group
XML Extensible Markup Language (see FCG TS62769-100, Edition 1.1, Field Device
Integration Part 100: Profiles – Generic Protocols, available at
https://fieldcommgroup.org)
3.2 Conventions
3.2.1 EDDL syntax
This document specifies content for the EDD component that is part of FDI Communication
Packages. The specification content using EDDL syntax uses the font Courier New. The
EDDL syntax is used for method signature, variable, data structure and component
declarations.
3.2.2 XML syntax
XML syntax examples use the font Courier New. The XML syntax is used to describe XML
document schema.
Example:
3.2.3 Capitalizations
The IEC 62769 series uses capitalized terms to emphasize that these terms have an FDI-
specific meaning.
Some of these terms use an initialism as a prefix, for example:
• FDI Client, or
• FDI Server.
Some of these terms are compound terms, such as:
• Communication Servers, or
• Profile Package.
Parameter names or attributes are concatenated into a single term, where the original terms
start in this term with a capital letter, such as:
• ProtocolSupportFile or
• ProtocolType.
Parameter names or attributes can also be constructed by using an underscore character to
concatenate two or more terms, such as:
• DEVICE_REV or
• DEVICE_MODEL
___________
Field Device Integration (FDI) is the trademark of a product supplied by FieldComm Group. This information is
given for the convenience of users of this document and does not constitute an endorsement by IEC of the
product named. Equivalent products may be used if they can be shown to lead to the same results.

– 8 – IEC 62769-100:2020 © IEC 2020
4 Profile for Generic Protocols
4.1 General
This profile document to the FDI specification in IEC 62769 specifies the protocol specifics
needed for FDI Packages describing Communication Servers, Gateways and Devices.
For Communication Servers, this document defines protocol specifics as these need to be
considered in the Information Model hosted by the Communication Servers.
4.2 Catalog profile
4.2.1 Protocol support file
4.2.1.1 FDI Device Package
Protocol-specific attachments are mentioned in the Package Catalog as defined in
IEC 62769-5. As this document defines a profile generically suitable for many protocols, it
does not define requirements for any protocol-specific attachments. However, it does also not
prevent the usage of protocol-specific attachments. The PSDs (see Annex C) define the
requirements on the need of ProtocolSupportFiles for a specific protocol. However, the
configuration of a device using an FDI Device Package shall not require the usage of a
protocol-specific attachment. Table 1 specifies the parameters of the ProtocolSupportFile in
the FDI Device Package in case one or many are provided.
Table 1 – ProtocolSupportFile for FDI Device Packages
Parameter Description
Content Type text/plain
Root Namespace empty
Source Relationship http://fdi-cooperation.com/2010/relationship/attachment-protocol
Filename Not defined
4.2.1.2 FDI Communication Packages
The same rules as for FDI Device Packages apply.
4.2.2 CommunicationProfile definition
IEC 62769-4 defines a CommunicationProfileT string for the Catalog XML schema. The string
is protocol-specific and defined as ProfileIdentifier in the PSD (see Annex C).
4.2.3 Profile device
A Profile Package shall provide the catalog values for profile devices, enabling the FDI Server
to leverage a generic device description, if a specific one is not available. The definitions in
Table 2 focus on catalog content that is vendor-independent.

IEC 62769-100:2020 © IEC 2020 – 9 –
Table 2 – Catalog values for profile devices
Element Attribute Content
PackageType — Profile
Manufacturer — Empty
DeviceModel — The format of the DeviceModel is protocol specific and details on the
format are defined in the PSD (see Annex C).
In order to assign a scan result with a profile package the ProfileId of the
scan result shall be mapped to the DeviceModel of the profile package.

4.2.4 Protocol version information
IEC 62769-4 defines an element type named InterfaceT for the Catalog XML schema. The
element type InterfaceT contains an element named Version, which is supposed to provide
version information about the applied communication protocol profile. The value shall follow
the IEC 62769-4 defined version information schema defined in the element type VersionT.
The PSDs (see Annex C) define the mapping of versions of a specific protocol to this field.
4.3 Associating a Package with a device
4.3.1 Device type identification mapping
The purpose of device-type identification mapping is to enable FDI host systems to compare
the scan result against the topology representation in the Information Model. FDI host
systems shall also be enabled to determine the FDI Device Package that fits for a device
entry contained in the scan result. This will enable the user of an FDI host system to
synchronize the Information Model with the actual installation.
The Communication Server implemented scan service (defined in 4.6.1.7) provides the scan
result through an XML document (the schema is defined in Clause A.5).
The Gateway implemented scan service (defined in 4.6.2.7) provides the scan result by
means of the Information Model that contains data structures created from EDD content as
specified in 4.6.2.7.
For both ways of presenting the scan result, it is common that scan results contain device
type identification and device instance identification.
FDI host systems comparing the actual network topology configuration against the topology
representation in the Information Model shall be enabled to handle the following situations:
a) The physical Device instance identified at a specific device address is not logically present
in the Information Model (as Instance): enable the FDI Host system to find the appropriate
FDI Device Package according to the device catalog information.
b) The physical Device instance identified by the device address is logically present in the
Information Model (as Instance): enable the FDI Host system to compare device type
information presented in scan result (see the identification in Clause A.5) and the device
type specific information of the Instance present in the Information Model.
The FDI Device Package contains device type identification information that can be compared
to the scan results based on the Catalog Schema in IEC 62769-4 defining the XML (simple)
element types “DeviceModel” and “Manufacturer”. Both types are used in the (complex)
element types “Protocol” and “RegDeviceType”.
As a result of the FDI Package deployment, the FDI Package information is then present in
the Information Model as the specified FunctionalGroup Identification containing
SerialNumber and Tag (see 4.4.3).

– 10 – IEC 62769-100:2020 © IEC 2020
The mapping between different device identification data sources is described in Table 3.
Since scan results provided by the Communication Server or Gateway can convey data that is
produced by the device (firmware), the device type identification mapping shall be supported
by providing corresponding data in the Catalog and Information Model contained in the FDI
Device Package.
Table 3 – Device identification information mapping
FDI Device Package Information Model Communication Server Gateway provided
provided scan result scan result
FunctionalGroup: Element (path): COLLECTION
Catalog specified type
Identification ConnectionPoint/Identification ConnectionPoint.
Manufacturer
Browse Name: Attribute: Manufacturer Identification:
Manufacturer Manufacturer
Catalog specified type FunctionalGroup: Element (path): COLLECTION
Identification ConnectionPoint/Identification ConnectionPoint.
DeviceModel
Browse Name: Attribute: DeviceModel Identification.
DeviceModel DeviceModel
Since not all protocols that are intended to be used with this profile for generic protocols
might support a mandatory discovery mechanism allowing to identify the type of device
(Manufacturer and DeviceModel), the scan results provide the capability to exclude the
identification of the device and only provide the address. In that case, some host-specific
mechanisms can be used to assign the desired FDI package to the device, for example by
user interaction.
Since some protocols do not even have the mandatory capabilities to identify if there is a
device at all for a specific protocol, address hosts should provide the capability for some
users to add devices by manually specifying address information.
4.3.2 Device type revision mapping
IEC 62769-4 envisions a concept that allows to determine the compatibility between an FDI
Device Package and a Device. IEC 62769-4 specifies a lifecycle management process
bearing on a single version information provided for the entire device. This is captured in the
DeviceRevision (see Table 4). Mapping of version information is protocol-specific and needs
to be defined in the PSDs (see Annex C).
Table 4 – Device revision information mapping
FDI Device Package Information Model Communication Server Gateway provided
provided scan result scan result
Catalog specified type FunctionalGroup: Element (path): COLLECTION
ListOfSupportedDeviceRevisions Identification ConnectionPoint/Identification ConnectionPoint.
Browse Name: Attribute: DeviceRevision Identification.
DeviceRevision DeviceRevision
4.4 Information Model mapping
4.4.1 ProtocolType definition
In Table 5, a subtype of ProtocolType is defined to identify network communication using this
profile.
IEC 62769-100:2020 © IEC 2020 – 11 –
Table 5 – Protocol type GenericProtocol
Attribute Value
BrowseName GenericProtocol
IsAbstract False
References NodeClass BrowseName DataType TypeDefinition ModellingRule
Subtype of the ProtocolType defined in IEC 62541-100.
HasProperty Variable ProtocolIdentifier String PropertyType Mandatory

The mandatory Variable ProtocolIdentifier defines which concrete protocol is represented
using the GenericProtocol type. It shall match the ProtocolIdentifier defined for the
CommunicationProfile in 4.2.2. The string is protocol-specific and defined as ProfileIdentifier
in the PSDs (see Annex C).
4.4.2 DeviceType mapping
Each device type inherits the properties of DeviceType. The mapping of the inherited
properties from DeviceType is defined in Table 6. Note that only the attributes defined in
Annex C, and therefore expected by each generic protocol, are used. Specific protocols can
provide, for example, a SoftwareRevsion, but since this is not accessible for the host, this
profile does not make use of it.
Table 6 – Inherited DeviceType property mapping
Property Generic Protocol Mapping
SerialNumber SerialNumber (see Annex C)
RevisionCounter -1 (not defined)
Manufacturer String taken from FDI package catalog
(ManufacturerName from PackageT)
String taken from FDI package catalog (Name of
Model
DeviceTypeT, which is a localized name)
a
DeviceManual empty text string (not supported)
DeviceRevision DeviceRevision (see Annex C)
SoftwareRevision empty string (not defined)
HardwareRevision empty string (not defined)
a
Device manuals are exposed as attachments of the FDI Device Package.

4.4.3 FunctionalGroup identification definition
As defined in IEC 62541-100:2015, 5.3, each device representation in the FDI Server hosted
Information Model shall contain a protocol-specific FunctionalGroup named Identification. The
Parameters of this FunctionalGroup are defined for generic protocol device types as follows:

– 12 – IEC 62769-100:2020 © IEC 2020
Table 7 – Generic Protocol Device Types identification attributes
BrowseName DataType Mandatory/Optional
Manufacturer String Mandatory
DeviceModel String Mandatory
SerialNumber String Optional
Tag String Optional
DeviceRevision UInt16 Optional
ProfileId String Optional
The BaseDataVariable instances shall be created from VARIABLE declarations with identifiers
that correspond to the browse names listed in Table 7.
4.5 Topology elements
4.5.1 ConnectionPoint definition
The ConnectionPoint type GenericConnectionPoint shall be used to parameterize network
access points using the generic protocols. The ConnectionPoint type GenericConnectionPoint
is a sub type of the abstract type ConnectionPointType defined in IEC 62541-100. Table 8
specifies the representation of the GenericConnectionPoint in the AddressSpace.
Table 8 – ConnectionPoint type for Generic Protocols
Attribute Value
BrowseName GenericConnectionPoint
IsAbstract False
References NodeClass BrowseName DataType TypeDefinition ModellingRule
Sub type of the ConnectionPointType defined in IEC 62541-100.
HasProperty Variable Address String PropertyType Mandatory
HasProperty Variable ProtocolIdentifier String PropertyType Mandatory

The ConnectionPoint type GenericConnectionPoint shall be described by an EDD element
contained in a Communication Device related FDI Package that can drive a generic protocol
network. Actual ConnectionPoint properties are declared by VARIABLE constructs grouped
together in a COLLECTION named ConnectionPoint. For this profile, it shall only contain the
CONNECTION_POINT_ADDRESS, mapped to the OPC UA Property Address. In addition, the
PROTOCOL specified by the COMPONENT shall be mapped to the ProtocolIdentifier
Property. The following EDDL source code is an example describing a Connection Point for
an ExampleProtocol. The ProtocolIdentifier defined by the PSDs (see Annex C) shall be used
as the PROTOCOL name in the EDD.

COMPONENT ConnectionPoint_Generic
{
LABEL "Generic Connection Point";
CLASSIFICATION NETWORK_CONNECTION_POINT;
CAN_DELETE FALSE;
PROTOCOL ExampleProtocol;
CONNECTION_POINT ConnectionPoint;
}
VARIABLE Address
{
IEC 62769-100:2020 © IEC 2020 – 13 –
LABEL "Address";
HELP "Address of the device";
TYPE EUC();
CLASS LOCAL;
}
COLLECTION ConnectionPoint
{
LABEL "Connection Point";
MEMBERS
{
CONNECTION_POINT_ADDRESS, Address;
}
}
4.5.2 Communication Device definition
In accordance with IEC 62769-7, each FDI Communication Package shall contain an EDD
element describing the communication device. The following EDDL source code in is an
example describing a Communication Server.
COMPONENT Generic_Communication_Server
{
LABEL "Generic communication server";
PRODUCT_URI "urn:Company Name:Product Name";
CAN_DELETE TRUE;
CLASSIFICATION NETWORK_COMPONENT;
COMPONENT_RELATIONS
{
Generic_Communication_Device_Setup
}
}
COMPONENT_RELATION Generic_Communication_Device_Setup
{
LABEL "Relation between Device and communication device";
RELATION_TYPE CHILD_COMPONENT;
COMPONENTS
{
Generic_Communication_Device{AUTO_CREATE 1;}
}
MINIMUM_NUMBER 1;
MAXIMUM_NUMBER 4;
}
In accordance with IEC 62769-7, each FDI Communication Package shall contain at least one
EDD element describing at least one communication device component. The following EDDL
source code in is an example for a generic protocol communication device:
COMPONENT Generic_Communication_Device
{
LABEL "Generic communication device";
CAN_DELETE TRUE;
CLASSIFICATION NETWORK_COMPONENT;
COMPONENT_RELATIONS { Generic_Service_Provider_Relation }
}
COMPONENT_RELATION Generic_Service_Provider_Relation
{
LABEL "Relation to communication service provider";
RELATION_TYPE CHILD_COMPONENT;
COMPONENTS
{
Generic_Service_Provider{AUTO_CREATE 1;}
}
– 14 – IEC 62769-100:2020 © IEC 2020
MINIMUM_NUMBER 1;
MAXIMUM_NUMBER 1;
}
In an actual communication device the ConnectionPoint_Generic needs to be adapted
according to the supported protocol and the related connection point definitions given in 4.5.
The attribute BYTE_ORDER shall not be used for this profile as the byte order handling shall
be done in the gateway business logic.
4.5.3 Communication service provider definition
In accordance with IEC 62769-7, each FDI Communication Package shall contain at least one
EDD element describing at least one communication service provider component. The
following EDDL source code below is an example for a generic protocol communication
service provider component.
The component reference (ConnectionPoint_Generic) corresponds to the related connection
point definition in 4.5. The attribute BYTE_ORDER shall not be used for this profile as the
byte order handling shall be done in the gateway business logic.
COMPONENT Generic_Service_Provider
{
LABEL "Generic Protocol communication service provider";
CAN_DELETE TRUE;
CLASSIFICATION NETWORK_COMMUNICATION_SERVICE_PROVIDER;
COMPONENT_RELATIONS
{
Generic_Service_Provider_Connection_Point_Relation
}
}
COMPONENT_RELATION Generic_Service_Provider_Connection_Point_Relation
{
LABEL "Relation between communication service provider and Connection Point";
RELATION_TYPE CHILD_COMPONENT;
ADDRESSING {Address}
COMPONENTS
{
ConnectionPoint_Generic{ AUTO_CREATE 1;}
}
MINIMUM_NUMBER 1;
MAXIMUM_NUMBER 1;
}
4.5.4 Network definition
In accordance with to IEC 62769-7, each FDI Communication Package shall contain at least
one EDD element describing network configuration constraints using the component
construct.
COMPONENT Network_Generic
{
LABEL "Generic Network";
CAN_DELETE TRUE;
CLASSIFICATION NETWORK;
COMPONENT_RELATIONS
{
Generic_Network_Connection_Point_Relation
}
}
COMPONENT_RELATION Generic_Network_Connection_Point_Relation
{
LABEL "Relation between network and Connection Point";
RELATION_TYPE CHILD_COMPONENT;

IEC 62769-100:2020 © IEC 2020 – 15 –
ADDRESSING {Address}
COMPONENTS
{
ConnectionPoint_Generic
}
MINIMUM_NUMBER 1;
MAXIMUM_NUMBER 32;
}
4.6 Methods
4.6.1 Methods for FDI Communication Servers
4.6.1.1 General
The Communication Server contained Information Model shall implement services according
to method signatures described in 4.6.1.
4.6.1.2 Connect
Signature:
Connect(
[in] ByteString CommunicationRelationId,
[in] String Address,
[out] Int32 ServiceError);
Table 9 provides the description of the arguments.
Table 9 – Method Connect arguments
Argument Description
CommunicationRelationId The argument value contains the nodeId of the ConnectionPoint representing
the connection between a device and a physical network that is directly
connected to the Communication Server
...