oSIST prEN IEC 62769-100:2022

Field device integration (FDI) - Part 100: Profiles - Generic protocols

IEC 62769-100:2023 is available as IEC 62769-100:2023 RLV which contains the International Standard and its Redline version, showing all changes of the technical content compared to the previous edition.

IEC 62769-100:2023 specifies an FDI®[1] 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 PSD need to be defined per protocol so that FDI® Device Packages, FDI® Communication Packages for Gateways and FDI® Communication Servers, FDI® Communication Server, Gateways and Devices supporting such a protocol can work together in a host not aware about this specific protocol.

Feldgeräteintegration (FDI) - Teil 100: Profile - Allgemeine Protokolle

Intégration des appareils de terrain (FDI) - Partie 100: Profils - Protocoles génériques

IEC 62769-100:2023 est disponible sous forme de IEC 62769-100:2023 RLV qui contient la Norme internationale et sa version Redline, illustrant les modifications du contenu technique depuis l'édition précédente.

L'IEC 62769-100:2023 spécifie un profil FDI®[1] de l'IEC 62769 pour les Protocoles Génériques. Cela signifie que toutes les interfaces sont définies, et qu'un hôte peut ajouter une prise en charge pour davantage de protocoles sans modifier la mise en œuvre. Néanmoins, certaines définitions spécifiques au protocole (PSD) nécessitent d'être spécifiées à l'aide de ce profil. L'Annexe C spécifie les PSD qu'il est nécessaire de définir par protocole, de sorte que les Paquetages d'Appareils FDI®, les Paquetages de Communication FDI® pour les Passerelles et les Serveurs de Communication FDI®, le Serveur de Communication FDI®, les Passerelles et les Appareils qui prennent en charge ce type de protocole puissent fonctionner ensemble dans un hôte, quel que soit ce protocole spécifique.

Integracija procesne naprave (FDI) - 100. del: Profili - Splošni protokoli

General Information

• Status: Not Published
• Public Enquiry End Date: 22-May-2022
• ICS: 25.040.40 - Industrial process measurement and control
• ICS: 35.100.05 - Multilayer applications
• ICS: 35.240.50 - IT applications in industry
• Technical Committee: MOV - Measuring equipment for electromagnetic quantities
• Current Stage: 6060 - National Implementation/Publication (Adopted Project)
• Start Date: 04-Jul-2023
• Due Date: 08-Sep-2023
• Ref Project: EN IEC 62769-100:2023 - Field device integration (FDI®) - Part 100: Profiles - Generic protocols

Relations

• Revised: SIST EN IEC 62769-100:2021 - Field device integration (FDI) - Part 100: Profiles - Generic protocolsi (IEC 62769-100:2020)
• Effective Date: 09-Nov-2021

Standards Content (Sample)

SLOVENSKI STANDARD
oSIST prEN IEC 62769-100:2022
01-maj-2022
Integracija procesne naprave (FDI) - 100. del: Profili - Splošni protokoli
Field device integration (FDI) - Part 100: Profiles - Generic protocols
Feldgeräteintegration (FDI) - Teil 100: Profile - Allgemeine Protokolle

Intégration des appareils de terrain (FDI) - Partie 100: Profils - Protocoles génériques

Ta slovenski standard je istoveten z: prEN IEC 62769-100:2022
ICS:
25.040.40 Merjenje in krmiljenje Industrial process
industrijskih postopkov measurement and control
35.240.50 Uporabniške rešitve IT v IT applications in industry
industriji
oSIST prEN IEC 62769-100:2022 en,fr,de

2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

---------------------- Page: 1 ----------------------
oSIST prEN IEC 62769-100:2022
---------------------- Page: 2 ----------------------
oSIST prEN IEC 62769-100:2022
65E/865/CDV
COMMITTEE DRAFT FOR VOTE (CDV)
PROJECT NUMBER:
IEC 62769-100 ED2
DATE OF CIRCULATION: CLOSING DATE FOR VOTING:
2022-03-04 2022-05-27
SUPERSEDES DOCUMENTS:
65E/832/RR
IEC SC 65E : DEVICES AND INTEGRATION IN ENTERPRISE SYSTEMS
SECRETARIAT: SECRETARY:
United States of America Mr Donald (Bob) Lattimer
OF INTEREST TO THE FOLLOWING COMMITTEES: PROPOSED HORIZONTAL STANDARD:
SC 65C
Other TC/SCs are requested to indicate their interest, if any,
in this CDV to the secretary.
FUNCTIONS CONCERNED:
EMC ENVIRONMENT QUALITY ASSURANCE SAFETY

SUBMITTED FOR CENELEC PARALLEL VOTING NOT SUBMITTED FOR CENELEC PARALLEL VOTING

Attention IEC-CENELEC parallel voting
The attention of IEC National Committees, members of
CENELEC, is drawn to the fact that this Committee Draft for
Vote (CDV) is submitted for parallel voting.
The CENELEC members are invited to vote through the
CENELEC online voting system.

This document is still under study and subject to change. It should not be used for reference purposes.

Recipients of this document are invited to submit, with their comments, notification of any relevant patent rights of which they

are aware and to provide supporting documentation.
TITLE:
Field device integration (FDI) - Part 100: Profiles - Generic protocols
PROPOSED STABILITY DATE: 2025

Copyright © 2022 International Electrotechnical Commission, IEC. All rights reserved. It is permitted to download this

electronic file, to make a copy and to print out the content for the sole purpose of preparing National Committee positions.

You may not copy or "mirror" the file or printed version of the document, or any part of it, for any other purpose without

permission in writing from IEC.
---------------------- Page: 3 ----------------------
oSIST prEN IEC 62769-100:2022
65E/865/CDV – 2 – IEC CDV 62769-100 © IEC:2022
NOTE FROM TC/SC OFFICERS:
---------------------- Page: 4 ----------------------
oSIST prEN IEC 62769-100:2022
65E/865/CDV – 3 – IEC CDV 62769-100 © IEC:2022
1 CONTENTS

3 FOREWORD .......................................................................................................................... 6

4 1 Scope ............................................................................................................................. 8

5 2 Normative References .................................................................................................... 8

6 3 Terms, definitions, abbreviated terms and Acronyms ...................................................... 8

7 3.1 Terms and definitions ............................................................................................. 8

8 3.2 Abbreviations ......................................................................................................... 8

9 4 Conventions .................................................................................................................... 9

10 4.1 EDDL syntax .......................................................................................................... 9

11 4.2 XML syntax ............................................................................................................ 9

12 4.3 Capitalizations........................................................................................................ 9

13 5 Profile for Generic Protocols ........................................................................................... 9

14 5.1 General .................................................................................................................. 9

15 5.2 Catalog profile ...................................................................................................... 10

16 5.2.1 Protocol support file ...................................................................................... 10

17 5.2.2 CommunicationProfile definition .................................................................... 10

18 5.2.3 Profile device ................................................................................................ 10

19 5.2.4 Protocol version information .......................................................................... 10

20 5.3 Associating a Package with a device .................................................................... 11

21 1.1.1 Device type identification mapping ................................................................ 11

22 5.3.1 Device type revision mapping ........................................................................ 12

23 5.4 Information Model mapping .................................................................................. 12

24 1.1.1 ProtocolType definition ................................................................................. 12

25 5.4.1 DeviceType mapping ..................................................................................... 13

26 5.4.2 FunctionalGroup identification definition ........................................................ 13

27 5.5 Topology elements ............................................................................................... 14

28 1.1.1 ConnectionPoint definition ............................................................................ 14

29 5.5.1 Communication Device definition .................................................................. 15

30 5.5.2 Communication service provider definition .................................................... 16

31 5.5.3 Network definition ......................................................................................... 16

32 5.6 Methods ............................................................................................................... 17

33 1.1.1 Methods for FDI Communication Servers ...................................................... 17

34 5.6.2 Methods for Gateways .................................................................................. 21

35 Annex A (normative) Topology Scan result schema ............................................................. 30

36 A.1 General ................................................................................................................ 30

37 A.2 Network ................................................................................................................ 30

38 A.3 GenericNetworkT ................................................................................................. 30

39 A.4 GenericConnectionPointT ..................................................................................... 30

40 A.5 GenericIdentificationT .......................................................................................... 31

41 A.6 GenericAddressT ................................................................................................. 32

42 A.7 GenericIdentificationExtendedT ............................................................................ 32

---------------------- Page: 5 ----------------------
oSIST prEN IEC 62769-100:2022
65E/865/CDV – 4 – IEC CDV 62769-100 © IEC:2022

43 Annex B (normative) Transfer service parameters ............................................................... 34

44 B.1 General ................................................................................................................ 34

45 B.2 sendData .............................................................................................................. 34

46 B.3 receiveData .......................................................................................................... 34

47 B.4 TransferSendDataT .............................................................................................. 34

48 B.5 EddDataTypeInfoListT .......................................................................................... 35

49 B.6 EddDataTypeInfoT ............................................................................................... 35

50 B.7 EddDataTypeT ..................................................................................................... 36

51 B.8 TransferResultDataT ............................................................................................ 37

52 Annex C (normative) Protocol Specific Definitions ............................................................... 38

53 C.1 General ................................................................................................................ 38

54 C.2 Header ................................................................................................................. 38

55 C.3 ProtocolIdentifier .................................................................................................. 38

56 C.4 Address ................................................................................................................ 38

57 C.5 Manufacturer ........................................................................................................ 38

58 C.6 DeviceModel ........................................................................................................ 39

59 C.7 DeviceRevision .................................................................................................... 39

60 C.8 SerialNumber ....................................................................................................... 39

61 C.9 Tag ...................................................................................................................... 39

62 C.10 ProfileId ............................................................................................................... 39

63 C.11 Version................................................................................................................. 39

64 C.12 ProtocolSupportFile .............................................................................................. 40

65 C.13 ExtendedDeviceRevision ...................................................................................... 40

66 Bibliography ......................................................................................................................... 41

68 No table of figures entries found.

69 Table 1 – ProtocolSupportFile for FDI Device Packages ....................................................... 10

70 Table 2 – Catalog values for profile devices ......................................................................... 10

71 Table 3 – Device identification information mapping ............................................................. 12

72 Table 4 – Device revision information mapping..................................................................... 12

73 Table 5 – Protocol type GenericProtocol .............................................................................. 13

74 Table 6 – Inherited DeviceType property mapping ................................................................ 13

75 Table 7 – Generic Protocol Device Types identification attributes ......................................... 13

76 Table 8 – ConnectionPoint type for Generic Protocols .......................................................... 14

77 Table 9 – Method Connect arguments .................................................................................. 17

78 Table 10 – Method Disconnect arguments ............................................................................ 18

79 Table 11 – Method Transfer arguments ................................................................................ 18

80 Table 12 – EddDataTypeInfo DataType Structure ................................................................. 19

81 Table 13 – EddDataTypeEnum Values ................................................................................. 20

82 Table 14 – Method SetAddress arguments ........................................................................... 21

83 Table 15 – Connect service arguments ................................................................................. 23

84 Table 16 – Method Transfer arguments ................................................................................ 24

---------------------- Page: 6 ----------------------
oSIST prEN IEC 62769-100:2022
IEC CDV 62769-100 © IEC:2022 – 5 – 65E/865/CDV

85 Table 17 – Method SetAddress arguments ........................................................................... 27

86 Table A.1 – Elements of GenericNetworkT ........................................................................... 30

87 Table A.2 – Attributes of GenericConnectionPointT .............................................................. 31

88 Table A.3 – Elements of GenericConnectionPointT .............................................................. 31

89 Table A.4 – Attributes of GenericIdentificationT .................................................................... 32

90 Table A.5 – Attributes of GenericIdentificationExtendedT ..................................................... 32

91 Table B.1 – Attributes of TransferSendDataT ....................................................................... 34

92 Table B.2 – Elements of TransferSendDataT ........................................................................ 35

93 Table B.3 – Elements of EddDataTypeInfoListT .................................................................... 35

94 Table B.4 – Attributes of EddDataTypeInfoT ......................................................................... 35

95 Table B.5 – Enumerations of EddDataTypeT ........................................................................ 36

96 Table B.6– Attributes of TransferResultDataT ...................................................................... 37

---------------------- Page: 7 ----------------------
oSIST prEN IEC 62769-100:2022
65E/865/CDV – 6 – IEC CDV 62769-100 © IEC:2022
99 INTERNATIONAL ELECTROTECHNICAL COMMISSION
100 ____________
101
102 FIELD DEVICE INTEGRATION (FDI) –
103
104 Part 100: Profiles – Generic Protocols
105
106 FOREWORD

107 1) The International Electrotechnical Commission (IEC) is a worldwide organization for standardization comprising all national

108 electrotechnical committees (IEC National Committees). The object of IEC is to promote international co-operation on all

109 questions concerning standardization in the electrical and electronic fields. To this end and in addition to other activities , IEC

110 publishes International Standards, Technical Specifications, Technical Reports, Publicly Available Specifications (PAS) and

111 Guides (hereafter referred to as “IEC Publication(s)”). Their preparation is entrusted to technical committees; any IEC Natio nal

112 Committee interested in the subject dealt with may participate in this preparatory work. International, governmental and non-

113 governmental organizations liaising with the IEC also participate in this preparation. IEC collaborates closely with the

114 International Organization for Standardization (ISO) in accordance with conditions determined by agreement between the two

115 organizations.

116 2) The formal decisions or agreements of IEC on technical matters express, as nearly as possible, an international consensus

117 of opinion on the relevant subjects since each technical committee has representation from all interested IEC National

118 Committees.

119 3) IEC Publications have the form of recommendations for international use and are accepted by IEC National Committees in

120 that sense. While all reasonable efforts are made to ensure that the technical content of IEC Publications is accurate, IEC

121 cannot be held responsible for the way in which they are used or for any misinterpretation by any end user.

122 4) In order to promote international uniformity, IEC National Committees undertake to apply IEC Publications transparently to

123 the maximum extent possible in their national and regional publications. Any divergence between any IEC Publication and the

124 corresponding national or regional publication shall be clearly indicated in the latter.

125 5) IEC itself does not provide any attestation of conformity. Independent certification bodies provide conformity assessment

126 services and, in some areas, access to IEC marks of conformity. IEC is not responsible for any services carried out by

127 independent certification bodies.

128 6) All users should ensure that they have the latest edition of this publication.

129 7) No liability shall attach to IEC or its directors, employees, servants or agents including individual experts and members of its

130 technical committees and IEC National Committees for any personal injury, property damage or other damage of any nature

131 whatsoever, whether direct or indirect, or for costs (including legal fees) and expenses arising out of the publication, use of,

132 or reliance upon, this IEC Publication or any other IEC Publications.

133 8) Attention is drawn to the Normative references cited in this publication. Use of the referenced publications is indispensable

134 for the correct application of this publication.

135 9) Attention is drawn to the possibility that some of the elements of this IEC Publication may be the subject of patent rights. IEC

136 shall not be held responsible for identifying any or all such patent rights.

137 IEC 62769-100 has been prepared by subcommittee 65E: Devices and integration in enterprise systems,

138 of IEC technical committee 65: Industrial-process measurement, control and automation. It is an

139 International Standard.

140 This second edition cancels and replaces the first edition published in 2020. This edition constitutes a

141 technical revision.

142 This edition includes the following significant technical changes with respect to the previous edition:

143 a) added ExtendedDeviceRevision implementing the FDI Version scheme and the method

144 ScanExtended.
---------------------- Page: 8 ----------------------
oSIST prEN IEC 62769-100:2022
IEC CDV 62769-100 © IEC:2022 – 7 – 65E/865/CDV
145 The text of this International Standard is based on the following documents:
Draft Report on voting
XX/XX/FDIS XX/XX/RVD
146

147 Full information on the voting for its approval can be found in the report on voting indicated in the above

148 table.

149 The language used for the development of this International Standard is English.

150 This document was drafted in accordance with ISO/IEC Directives, Part 2, and developed in accordance

151 with ISO/IEC Directives, Part 1 and ISO/IEC Directives, IEC Supplement, available at

152 www.iec.ch/members_experts/refdocs. The main document types developed by IEC are described in

153 greater detail at www.iec.ch/standardsdev/publications.

154 The committee has decided that the contents of this document will remain unchanged until the stability

155 date indicated on the IEC website under "http://webstore.iec.ch" in the data related to the specific

156 document. At this date, the document will be
157 • reconfirmed,
158 • withdrawn,
159 • replaced by a revised edition, or
160 • amended.
161
---------------------- Page: 9 ----------------------
oSIST prEN IEC 62769-100:2022
65E/865/CDV – 8 – IEC CDV 62769-100 © IEC:2022
162
163 FIELD DEVICE INTEGRATION (FDI) –
164
165 Part 100: Profiles – Generic Protocols
166
167
168
169 1 Scope

170 This part of IEC 62769 specifies an FDI profile of IEC 62769 for Generic Protocols. That means that all

171 interfaces are defined and a host can add support for more protocols without changing its implementation.

172 Nevertheless, there are some protocol-specific definitions (PSD) that need to be specified per protocol

173 using this profile. Annex C specifies what PSD need to be defined per protocol so that FDI Device

174 Packages, FDI Communication Packages for Gateways and FDI Communication Servers, FDI

175 Communication Server, Gateways and Devices supporting such a protocol can work together in a host not

176 aware about this specific protocol.

177 NOTE: A host not using FDI communication server but a proprietary mechanism for communication needs to define its own means

178 to deal with this profile to support several protocols without changing its implementation. This is specific to the proprietary way

179 how the communication driver is bound to the host.
180 2 Normative References

181 The following documents, in whole or in part, are normatively referenced in this document and are

182 indispensable for its application. For dated references, only the edition cited applies. For undated

183 references, the latest edition of the referenced document (including any amendments) applies.

184 IEC 61804 (all parts), Function blocks (FB) for process control and Electronic Device Description

185 Language (EDDL)

186 IEC 61804-3, Function blocks (FB) for process control and Electronic Device Description Language

187 (EDDL) – Part 3: EDDL syntax and semantics
188 IEC 62541-100: OPC Unified Architecture – Part 100: OPC UA for Devices
189 IEC 62769-1, Field Device Integration (FDI) – Part 1: Overview
190 IEC 62769-2, Field Device Integration (FDI) – Part 2: FDI Client
191 IEC 62769-4, Field Device Integration (FDI) – Part 4: FDI Packages
192 IEC 62769-5, Field Device Integration (FDI) – Part 5: FDI Information Model

193 IEC 62769-7, Field Device Integration (FDI) – Part 7: FDI Communication Devices

194 3 Terms, definitions, abbreviated terms and Acronyms
195 3.1 Terms and definitions

196 For the purposes of this document, the terms and definitions given in IEC 61804 series, IEC 62541-100,

197 IEC 62769-2, IEC 62769-4, IEC 62769-5, and IEC 62769-7 apply.
198 3.2 Abbreviations
199 For the purposes of this specification, the following abbreviations apply.
---------------------- Page: 10 ----------------------
oSIST prEN IEC 62769-100:2022
IEC CDV 62769-100 © IEC:2022 – 9 – 65E/865/CDV
200 EDD Electronic Device Description
201 EDDL Electronic Device Description Language (see IEC 61804)
202 FDI Field Device Integration
203 FCG FieldComm Group
204 XML Extensible markup language (see REC-xml-20081126)
205 4 Conventions
206 4.1 EDDL syntax

207 This part of IEC 62769 specifies content for the EDD component that is part of FDI Communication

208 Packages. The specification content using EDDL syntax uses the font Courier New. The EDDL syntax

209 is used for method signature, variable, data structure and component declarations.

210 4.2 XML syntax

211 XML syntax examples use font Courier New. The XML syntax is used to describe XML document

212 schema.
213 Example:
214 4.3 Capitalizations

215 The IEC 62769 series use capitalized terms to emphasize that these terms have a FDI specific meaning.

216 Some of these terms using an acronym as a prefix for example
217 • FDI Client, or
218 • FDI Server.
219 Some of these terms are compound terms such as:
220 • Communication Servers, or
221 • Profile Package.

222 Parameter names or attributes are concatenated to a single term, where the original terms start i n this

223 term with a capital letter such as:
224 • ProtocolSupportFile or
225 • ProtocolType.

226 Parameter names or attributes can also be constructed by using an underscore character to concatenate

227 two or more terms such as:
228 • DEVICE_REV or
229 • DEVICE_MODEL
230 5 Profile for Generic Protocols
231 5.1 General

232 This profile document to the FDI specification in IEC 62769 specifies the protocol specifics needed for FDI

233 Packages describing Communication Servers, Gateways and Devices.
---------------------- Page: 11 ----------------------
oSIST prEN IEC 62769-100:2022
65E/865/CDV – 10 – IEC CDV 62769-100 © IEC:2022

234 For Communication Servers this document defines also protocol specifics as these need to be considered

235 in the Communication Servers hosted Information Model.
236 5.2 Catalog profile
237 5.2.1 Protocol support file
238 5.2.1.1 FDI Device Package

239 Protocol specific attachments are mentioned in the Package Catalog as de fined in

240 IEC 62769-5. As this annex defines a profile generically suitable for many protocols it does not define

241 requirements for any protocol specific attachments. However, it does also not prevent the usage of

242 protocol specific attachments. The PSD define the requirements on the need of ProtocolSupportFiles for

243 a specific protocol. However, the configuration of a device using an FDI Device Package shall not require

244 the usage of a protocol specific attachment. Table 1 specifies the parameters of the ProtocolSupportFile

245 in the FDI Device Package in case one or many are provided.
246 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
247
248 5.2.1.2 FDI Communication Packages
249 The same rules as for FDI Device Packages applies.
250 5.2.2 CommunicationProfile definition

251 IEC 62769-4 defines a CommunicationProfileT string for the Catalog XML schema. The string is protocol specific

252 and defined as ProfileIdentifier in the PSD (see Annex C).
253 5.2.3 Profile device

254 A Profile Package shall provide the catalog values for profile devices, enabling the FDI Server to leverage

255 a generic device description, if a specific one is not available. The definitions in Table 2 focus on catalog

256 content that is vendor independent.
257 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.
258 5.2.4 Protocol version information

259 IEC 62769-4 defines an element type named InterfaceT for the Catalog XML schema. The element type

260 InterfaceT contains an element named Version which is supposed to provide version information about

261 the applied communication protocol profile. The value has to follow the IEC 62769-4 defined version

---------------------- Page: 12 ----------------------
oSIST prEN IEC 62769-100:2022
IEC CDV 62769-100 © IEC:2022 – 11 – 65E/865/CDV

262 information schema defined in the element type VersionT. The PSD (see Annex C) define the mapping of

263 versions of a specific protocol to this field.
264 5.3 Associating a Package with a device
265 1.1.1 Device type identification mapping

266 The purpose of device type identification mapping is to enable FDI host systems to compare the scan

267 result against the topology representation in the Information Model. FDI host systems shall also be enabled

268 to determine the FDI Device Package that fits for a device entry contained in the scan result. This will

269 enable the user of an FDI host system to synchronize the Information Model with the actual installation.

270 The Communication Server implemented scan service (defined in 5.6.1.7) provides the scan result through

271 an XML document (the schema is defined in Clause A.5).

272 The Gateway implemented scan service (defined in 5.6.2.7) provides the scan result by means of the

273 Information Model that contains data structures created from EDD content as specified in 5.6.2.7.

274 Common for both ways of presenting the scan result is that scan results contain device type identification

275 and device instance identification.

276 FDI host systems comparing the actual network topology configuration against the topology representation

277 in the Information Model shall be enabled to handle the following situations:

278 a) The physical Device instance identified at a specific device address is not logically present in the

279 Information Model (as Instance): Enable the FDI Host system to find the appropriate FDI Device

280 Package according to the device catalog information.

281 b) The physical Device instance identified by the device address is logically present in the Information

282 Model (as Instance): Enable the FDI Host system to compare device type information presented in

283 scan result (see the identification in Clause A.5) and the device type specific information of the

284 Instance present in the Information Model.

285 The FDI Device Package contains device type identification information that can be comp ared to scan

286 result based on the Catalog Schema in IEC 62769-4 defining the XML (simple) element types

287 “DeviceModel” and “Manufacturer”. Both types are used in the (complex) elem ent types “Protocol” and

288 “RegDeviceType”.

289 As a result of the FDI Package deployment the FDI Package information is then present in the Inform

...