Field Device Integration (FDI) - Part 103-1: Profiles - PROFIBUS

IEC 62769-103-1:2023 is available as IEC 62769-103-1: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-103-1:2023 specifies an FDI®[1] profile of IEC 62769 for IEC 61784-1_CP 3/1 (PROFIBUS DP)[2] and IEC 61784-1_CP3/2 (PROFIBUS PA).
[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.
[2] PROFIBUS is the trade name of the non-profit consortium PROFIBUS & PROFINET International. This information is given for the convenience of users of this technical report 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.

Feldgeräteintegration (FDI) - Teil 103-1: Profile - PROFIBUS

Intégration des appareils de terrain (FDI) - Partie 103-1: Profils - PROFIBUS

IEC 62769-103-1:2023 est disponible sous forme de IEC 62769-103-1: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-103-1:2023 spécifie un profil FDI®[1] de l'IEC 62769 pour le profil de communication CP 3/1 défini dans l'IEC 61784-1 (PROFIBUS DP)[2] et pour le profil de communication CP 3/2 (PROFIBUS PA) défini dans l'IEC 61784-1.
[1] FDI est une marque déposée de l’organisation à but non lucratif Fieldbus Foundation, Inc. Cette information est donnée à l'intention des utilisateurs du présent document et ne signifie nullement que l'IEC approuve le détenteur de la marque ou l'emploi de ses produits. La conformité n'exige pas l'utilisation de la marque. L'utilisation de la marque exige l'autorisation du détenteur de la marque.
[2] PROFIBUS est l'appellation commerciale du consortium PROFIBUS & PROFINET International, une organisation à but non lucratif. Cette information est donnée à l'intention des utilisateurs du présent rapport technique et ne signifie nullement que l'IEC approuve le détenteur des appellations commerciales ou l'emploi de ses produits. La conformité n'exige pas l'utilisation de l'appellation commerciale. L'utilisation de l'appellation commerciale exige l'autorisation du détenteur de l'appellation commerciale.

Integracija procesne naprave (FDI) - 103-1. del: Profili - PROFIBUS

General Information

Status
Not Published
Public Enquiry End Date
22-May-2022
Current Stage
6060 - National Implementation/Publication (Adopted Project)
Start Date
04-Jul-2023
Due Date
08-Sep-2023

Relations

Buy Standard

Draft
prEN IEC 62769-103-1:2022
English language
35 pages
sale 10% off
Preview
sale 10% off
Preview
e-Library read for
1 day

Standards Content (Sample)

SLOVENSKI STANDARD
oSIST prEN IEC 62769-103-1:2022
01-maj-2022
Integracija procesne naprave (FDI) - 103-1. del: Profili - PROFIBUS
Field Device Integration (FDI) - Part 103-1: Profiles - PROFIBUS
Intégration des appareils de terrain (FDI) - Partie 103-1: Profils - PROFIBUS
Ta slovenski standard je istoveten z: prEN IEC 62769-103-1: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-103-1: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-103-1:2022
---------------------- Page: 2 ----------------------
oSIST prEN IEC 62769-103-1:2022
65E/862/CDV
COMMITTEE DRAFT FOR VOTE (CDV)
PROJECT NUMBER:
IEC 62769-103-1 ED3
DATE OF CIRCULATION: CLOSING DATE FOR VOTING:
2022-03-04 2022-05-27
SUPERSEDES DOCUMENTS:
65E/829/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:
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 103-1: Profiles - PROFIBUS
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-103-1:2022
65E/862/CDV – 2 – IEC CDV 62769-103-1 © IEC:2022
NOTE FROM TC/SC OFFICERS:
---------------------- Page: 4 ----------------------
oSIST prEN IEC 62769-103-1:2022
65E/862/CDV – 3 – IEC CDV 62769-103-1 © IEC:2022
1 CONTENTS

3 FOREWORD .......................................................................................................................... 5

4 1 Scope ............................................................................................................................. 7

5 2 Normative references ...................................................................................................... 7

6 3 Terms, definitions, abbreviated terms and acronyms ....................................................... 7

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

8 3.2 Abbreviated terms and acronyms ........................................................................... 7

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

10 4.1 EDDL syntax .......................................................................................................... 8

11 4.2 XML syntax ............................................................................................................ 8

12 4.3 Capitalizations........................................................................................................ 8

13 5 Profile for PROFIBUS ..................................................................................................... 8

14 5.1 General .................................................................................................................. 8

15 5.2 Catalog profile ........................................................................................................ 9

16 5.2.1 Protocol support file ........................................................................................ 9

17 5.2.2 CommunicationProfile definition ...................................................................... 9

18 5.2.3 Profile device .................................................................................................. 9

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

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

21 5.3.1 Device type identification mapping ................................................................ 10

22 5.3.2 Device type revision mapping ........................................................................ 12

23 5.4 Information Model mapping .................................................................................. 13

24 5.4.1 ProtocolType definition ................................................................................. 13

25 5.4.2 DeviceType mapping ..................................................................................... 13

26 5.4.3 FunctionalGroup identification definition ........................................................ 14

27 5.4.4 ConnectionPoint definition ............................................................................ 14

28 5.4.5 Communication Device definition .................................................................. 17

29 5.4.6 Communication service provider definition .................................................... 18

30 5.4.7 Network definition ......................................................................................... 18

31 5.5 Methods ............................................................................................................... 19

32 5.5.1 Methods for FDI Communication Servers ...................................................... 19

33 5.5.2 Methods for Gateways .................................................................................. 22

34 Annex A (normative) Topology Scan result schema ............................................................. 29

35 A.1 General ................................................................................................................ 29

36 A.2 Target Namespace ............................................................................................... 29

37 A.3 Network ................................................................................................................ 29

38 A.4 ProfibusNetworkT ................................................................................................. 29

39 A.5 ProfibusConnectionPointT .................................................................................... 30

40 A.6 ProfibusIdentificationT .......................................................................................... 30

41 A.7 ProfibusAddressT ................................................................................................. 31

42 Annex B (normative) Transfer service parameters ............................................................... 32

---------------------- Page: 5 ----------------------
oSIST prEN IEC 62769-103-1:2022
65E/862/CDV – 4 – IEC CDV 62769-103-1 © IEC:2022

43 B.1 General ................................................................................................................ 32

44 B.2 Target Namespace ............................................................................................... 32

45 B.3 sendData .............................................................................................................. 32

46 B.4 receiveData .......................................................................................................... 32

47 B.5 TransferSendDataT .............................................................................................. 32

48 B.6 TransferResultDataT ............................................................................................ 33

49 B.7 OperationT ........................................................................................................... 33

50 Annex C (informativ) Mapping to PA DIM ............................................................................ 34

51 C.1 General ................................................................................................................ 34

52 C.2 Mapping table ...................................................................................................... 34

53 Bibliography ......................................................................................................................... 35

55 No table of figures entries found.

56 Table 1 – Capability File part .................................................... Error! Bookmark not defined.

57 Table 2 – CommunicationProfile definition ................................ Error! Bookmark not defined.

58 Table 3 – Device type catalog mapping .................................... Error! Bookmark not defined.

59 Table 4 – ProtocolType Foundation_H1 definition..................... Error! Bookmark not defined.

60 Table 5 – Inherited DeviceType Property mapping ................... Error! Bookmark not defined.

61 Table 6 – Identification Parameters .......................................... Error! Bookmark not defined.

62 Table 7 – Inherited BlockType property mapping ...................... Error! Bookmark not defined.

63 Table 8 – ConnectionPointType ConnectionPoint_Foundation_H1 definitionError! Bookmark not

64 defined.

65 Table 9 – Communication device ParameterSet definition ........ Error! Bookmark not defined.

66 Table 10 – Method Connect arguments .................................... Error! Bookmark not defined.

67 Table 11 – Method Disconnect arguments ................................ Error! Bookmark not defined.

68 Table 12 – Method Transfer arguments .................................... Error! Bookmark not defined.

69 Table 13 – Method GetPublishedData arguments ..................... Error! Bookmark not defined.

70 Table 14 – Method SetAddress arguments ............................... Error! Bookmark not defined.

71 Table A.1 – Attributes of FoundationH1ConnectionPointT ........ Error! Bookmark not defined.

72 Table A.2 – Elements of FoundationH1ConnectionPointT ......... Error! Bookmark not defined.

73 Table A.3 – Elements of FoundationH1NetworkT ...................... Error! Bookmark not defined.

74 Table A.4 – Attributes of FoundationBlockIdentificationT .......... Error! Bookmark not defined.

75 Table A.5 – Attributes of FoundationIdentificationT .................. Error! Bookmark not defined.

76 Table B1 – Elements of receiveData ......................................... Error! Bookmark not defined.

77 Table B2 – Enumerations of OperationT ................................... Error! Bookmark not defined.

78 Table B3 – Attributes of ResponseCodeT ................................. Error! Bookmark not defined.

79 Table B4 – Attributes of TransferResultDataT .......................... Error! Bookmark not defined.

80 Table B5 – Attributes of TransferSendDataT ............................ Error! Bookmark not defined.

---------------------- Page: 6 ----------------------
oSIST prEN IEC 62769-103-1:2022
IEC CDV 62769-103-1 © IEC:2022 – 5 – 65E/862/CDV
83 INTERNATIONAL ELECTROTECHNICAL COMMISSION
84 ____________
86 FIELD DEVICE INTEGRATION (FDI) –
88 Part 103-1: Profiles – PROFIBUS
90 FOREWORD

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

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

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

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

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

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

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

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

99 organizations.

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

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

102 Committees.

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

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

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

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

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

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

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

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

111 independent certification bodies.

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

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

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

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

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

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

118 for the correct application of this publication.

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

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

121 IEC 62769-103-1 has been prepared by subcommittee 65E: Devices and integration in enterprise systems,

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

123 International Standard.

124 This third edition cancels and replaces the second edition published in 2021. This edition constitutes a

125 technical revision.

126 This edition includes the following significant technical changes with respect to the previ ous edition:

127 a) added DEVICE_ID to the ProfibusIdentificationType and namespace to Annex A and Annex B;

128 b) added mapping from PB standard parameters to PA DIM.
---------------------- Page: 7 ----------------------
oSIST prEN IEC 62769-103-1:2022
65E/862/CDV – 6 – IEC CDV 62769-103-1 © IEC:2022
129 The text of this International Standard is based on the following documents:
Draft Report on voting
XX/XX/FDIS XX/XX/RVD
130

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

132 table.

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

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

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

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

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

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

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

140 document. At this date, the document will be
141 • reconfirmed,
142 • withdrawn,
143 • replaced by a revised edition, or
144 • amended.
145
---------------------- Page: 8 ----------------------
oSIST prEN IEC 62769-103-1:2022
IEC CDV 62769-103-1 © IEC:2022 – 7 – 65E/862/CDV
146 FIELD DEVICE INTEGRATION (FDI) –
147
148 Part 103-1: Profiles – PROFIBUS
149
150
151
152 1 Scope

153 This part of IEC 62769specifies an FDI profile of IEC 62769 for IEC 61784-1_CP 3/1 (PROFIBUS DP)

154 and IEC 61784-1_CP3/2 (PROFIBUS PA).
155 2 Normative references

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

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

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

159 IEC 61784-1, Industrial communication networks – Profiles – Part 1: Fieldbus profiles

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

161 Language (EDDL)
162 IEC 62541-100:2015, OPC Unified Architecture – Part 100: OPC UA for Devices
163 IEC 62769-2, Field Device Integration (FDI) – Part 2: FDI Client
164 IEC 62769-4, Field Device Integration (FDI) – Part 4: FDI Packages
165 IEC 62769-5, Field Device Integration (FDI) – Part 5: FDI Information Model

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

167 PI Order No.: 2.122:2008, Specification for PROFIBUS – Device Description and Device Integration –

168 Volume 1: GSD, V5.1, July 2008: GSD; available at
169 3 Terms, definitions, abbreviated terms and acronyms
170 3.1 Terms and definitions

171 For the purposes of this document, the terms and definitions given in IEC 61784 -1, IEC 61804 (all parts),

172 IEC 62541-100, IEC 62769-4, IEC 62769-5, IEC 62769-7 and PI Order No.: 2.122:2008 apply.

173 3.2 Abbreviated terms and acronyms
174 For the purposes of this document, the following abbreviations apply:
EDD Electronic Device Description
EDDL Electronic Device Description Language (see IEC 61804 (all parts))

PROFIBUS is the trade name of the non-profit consortium PROFIBUS & PROFINET International. This information is given for the

convenience of users of this technical report 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.

---------------------- Page: 9 ----------------------
oSIST prEN IEC 62769-103-1:2022
65E/862/CDV – 8 – IEC CDV 62769-103-1 © IEC:2022
GSD General station description (see PI Order No.: 2.122:2008)
I&M Identification and maintenance function
UUID Universally unique identifier (see ISO/IEC 11578)
XML Extensible markup language (see REC-xml-20081126)
175 4 Conventions
176 4.1 EDDL syntax

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

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

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

180 4.2 XML syntax

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

182 schema.
183 Example:
184 4.3 Capitalizations

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

186 Some of these terms using an acronym as a prefix for example
187 • FDI Client, or
188 • FDI Server.
189 Some of these terms are compound terms such as:
190 • Communication Servers, or
191 • Profile Package.

192 Parameter names or attributes are concatenated to a single term, where the original terms start in this

193 term with a capital letter such as:
194 • ProtocolSupportFile or
195 • ProtocolType.

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

197 two or more terms such as:
198 • PROFILE_ID or
199 • Profibus_PA_Network
200 5 Profile for PROFIBUS
201 5.1 General

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

203 Packages describing Communication Servers, Gateways and Devices.

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

205 in the Communication Servers hosted Information Model.
---------------------- Page: 10 ----------------------
oSIST prEN IEC 62769-103-1:2022
IEC CDV 62769-103-1 © IEC:2022 – 9 – 65E/862/CDV
206 5.2 Catalog profile
207 5.2.1 Protocol support file
208 5.2.1.1 FDI Device Package

209 Protocol specific attachments are mentioned in the Package Catalog as defined in

210 Error! Reference source not found.. A communication feature list (GSD) file according to PI Order No.:

211 2.122:2008 is a mandatory attachment for FDI Device Packages representing PROFIBUS DP and

212 PROFIBUS PA devices. Table 1 specifies the parameters of the ProtocolSupportFile in the FDI Device

213 Package.
214 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 According to PI Order No.: 2.122:2008
215
216 5.2.1.2 FDI Communication Packages

217 A GSD file as specified in PI Order No.: 2.122:2008 is an optional attachment for FDI Communication

218 Packages representing PROFIBUS DP and PROFIBUS PA devices. Table 2 specifies the parameters of

219 ProtocolSupportFile for FDI Communication Packages.
220 Table 2 – ProtocolSupportFile for FDI Communication Packages
Parameter Description
Content Type: text/plain
Root Namespace: empty

Source Relationship: http://fdi-cooperation.com/2010/relationship/attachment-protocol

Filename: According to PI Order No.: 2.122:2008
221
222 5.2.2 CommunicationProfile definition

223 Error! Reference source not found. defines a CommunicationProfileT string for the Catalog XML

224 schema. Table 3 defines the PROFIBUS specific values for this string.
225 Table 3 – PROFIBUS CommunicationProfile definition schema
Profile Identifier Protocol
"profibus_dp" PROFIBUS DP/V0; PROFIBUS DP/V1; PROFIBUS DP/V2
“profibus_pa” PROFIBUS PA
226
227 5.2.3 Profile device

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

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

230 content that is vendor independent.
---------------------- Page: 11 ----------------------
oSIST prEN IEC 62769-103-1:2022
65E/862/CDV – 10 – IEC CDV 62769-103-1 © IEC:2022
231 Table 4 – Catalog values for profile devices
Element Attribute Content
PackageType — Profile
Manufacturer — Empty
DeviceModel — The allowed profile identifier values (PROFILE_ID) are provided by
PROFIBUS & PROFINET International (PI). PI provides and maintains an
XML file (Profile_ID_Table) containing the assignment of PROFILE_ID to
profiles.
It is available at
The file can be downloaded by any engineering or service tool whenever it
is connected to the Internet.
NOTE More information is provided in PI Order No.: 3.502 (I&M Profile)
and related profile definitions are referred therein.
The string format shall be hexadecimal starting with 0x, e.g. ‘0x3D00’.
232 5.2.4 Protocol version information

233 Error! Reference source not found. defines an element type named InterfaceT for the Catalog XML

234 schema. The element type InterfaceT contains an element named Version which is supposed to provide

235 version information about the applied communication protocol profile. The value has to follow the Error!

236 Reference source not found. defined version information schema defined in the element type VersionT.

237 Table 5 describes how to apply the currently known protocol versions defined by the non-profit consortium

238 PROFIBUS & PROFINET International. The general rule is to apply the value “0” for parts of the version

239 information according to Error! Reference source not found. that are not used in currently known

240 protocol versions.
241 Table 5 – Version mapping examples
Protocol / Version InterfaceT Version value
PROFIBUS DP/V0
0.0.0
PROFIBUS DP/V1
1.0.0
PROFIBUS DP/V2
2.0.0
PROFIBUS PA 3.02
3.2.0 ,
PROFIBUS PA 4.0
4.0.0 ,

The protocols PROFIBUS DP/V0, PROFIBUS DP/V1 and PROFIBUS DP/V2 contain a single

number. This number is considered to be the major version. The minor and built numbers are

set to “0”.

The currently known PROFIBUS PA profile numbers are considered to provide major and minor

version information. Leading zeros are not considered in version value evaluation since only

the actual decimal values are relevant.
242
243 5.3 Associating a Package with a device
244 5.3.1 Device type identification mapping

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

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

The given table can be considered to be an example only since this document cannot foresee how future protocol versions

will be defined.
---------------------- Page: 12 ----------------------
oSIST prEN IEC 62769-103-1:2022
IEC CDV 62769-103-1 © IEC:2022 – 11 – 65E/862/CDV

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

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

249 The Communication Server implemented scan service (defined in 5.5.1.7) provides the scan result through

250 an XML document (the schema is defined in Clause A.6).

251 The Gateway implemented scan service (defined in 5.5.2.7) provides the scan result by means of the

252 Information Model that contains data structures created from EDD content as specified in 5.5.2.7.

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

254 and device instance identification.

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

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

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

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

259 package according to the device catalog information.

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

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

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

263 Instance present in the Information Model.

264 The FDI Device package contains device type identification information that can be compared to scan

265 result based on the Catalog Schema in Error! Reference source not found. defining the XML (simple)

266 element types “DeviceModel” and “Manufacturer”. Both types are used in the (complex) element types

267 “Protocol” and “RegDeviceType”.

268 As a result of the FDI Package deployment the FDI Package information is then present in the Information

269 Model as the specified FunctionalGroup Identification containing Ident_Number and Manufacturer_ID (see

270 5.4.3). The Ident_Number matches with the GSD specified Ident_Number. Manufacturer_ID is specified

271 through the I&M profile defined VendorID and DeviceID (see 5.4.3).

272 If a device is used as a profile device, the Ident_Number returned in the scan result does not fit to the

273 Ident_Number within the GSD. In this case, DEVICE_ID can be used to identify the FDI Package.

274 The mapping between different device identification data sources is described in Table 6. Since scan

275 results provided by the Communication Server or Gateway can convey data that is produced by the device

276 (firmware) the device type identification mapping shall be supported by providing corresponding data in

277 the FDI Device Package contained Catalog and Information Model.
278 Table 6 – Device identification information mapping
FDI Device Package Information Model Communication Server Gateway provid
...

Questions, Comments and Discussion

Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.