CLC/TR IEC 62453-42:2019

SLOVENSKI STANDARD
01-julij-2019
Specifikacija vmesnika orodja procesne naprave - 42. del: Integracija profila
modela objekta - Skupna jezikovna infrastruktura (IEC TR 62453-42:2016)
Field device tool (FDT) interface specification - Part 42: Object model integration profile -
Common Language Infrastructure (IEC TR 62453-42:2016)
Field Device Tool (FDT)-Schnittstellenspezifikation - Teil 42: Profil zur Integration des
Objektmodells - Common Language Infrastructure (CLI) (IEC TR 62453-42:2016)
Spécification des interfaces des outils des dispositifs de terrain (FDT) - Partie 42: Profil
d'intégration des modèles d'objets - Infrastructure commune de langage (IEC TR 62453-
42:2016)
Ta slovenski standard je istoveten z: CLC/TR IEC 62453-42:2019
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.

TECHNICAL REPORT CLC/TR IEC 62453-42

RAPPORT TECHNIQUE
TECHNISCHER BERICHT
April 2019
ICS 35.100.05; 25.040.40; 35.110

English Version
Field device tool (FDT) interface specification - Part 42: Object
model integration profile - Common Language Infrastructure
(IEC TR 62453-42:2016)
Spécification des interfaces des outils des dispositifs de Field Device Tool (FDT)-Schnittstellenspezifikation - Teil 42:
terrain (FDT) - Partie 42: Profil d'intégration des modèles Profil zur Integration des Objektmodells - Common
d'objets - Infrastructure commune de langage Language Infrastructure (CLI)
(IEC TR 62453-42:2016) (IEC TR 62453-42:2016)

This Technical Report was approved by CENELEC on 2019-03-18.

CENELEC members are the national electrotechnical committees of Austria, Belgium, Bulgaria, Croatia, Cyprus, the Czech Republic,
Denmark, Estonia, Finland, Former Yugoslav Republic of Macedonia, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia,
Lithuania, Luxembourg, Malta, the Netherlands, Norway, Poland, Portugal, Romania, 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
© 2019 CENELEC All rights of exploitation in any form and by any means reserved worldwide for CENELEC Members.
Ref. No. CLC/TR IEC 62453-42:2019 E

European foreword
This document (CLC/TR IEC 62453-42:2019) consists of the text of the
IEC TR 62453-42:2016 prepared by 65E: "Devices and integration in enterprise systems", of
IEC technical committee 65: "Industrial process measurement, control and automation".

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.
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 When an International Publication has been modified by common modifications, indicated by (mod), the relevant

EN/HD applies.
NOTE 2 Up-to-date information on the latest versions of the European Standards listed in this annex is available here:
www.cenelec.eu.
Publication Year Title EN/HD Year
IEC 62453-1 2016 Field device tool (FDT) interface EN 62453-1 2017
specification - Part 1: Overview and
guidance
IEC 62453-2 2016 Field device tool (FDT) interface EN 62453-2 2017
specification - Part 2: Concepts and
detailed description
IEC TR 62453-42 ®
Edition 1.0 2016-04
TECHNICAL
REPORT
colour
inside
Field device tool (FDT) interface specification –

Part 42: Object model integration profile – Common Language Infrastructure

INTERNATIONAL
ELECTROTECHNICAL
COMMISSION
ICS 25.040.40; 35.100.05; 35.110 ISBN 978-2-8322-3226-2

– 2 – IEC TR 62453-42:2016  IEC 2016
CONTENTS
FOREWORD . 19
INTRODUCTION . 21
1 Scope . 23
2 Normative references. 23
3 Terms, definitions, abbreviations and conventions . 23
3.1 Terms and definitions . 23
3.2 Abbreviations . 30
3.3 Conventions . 30
4 Implementation concept . 31
4.1 Technological orientation . 31
4.2 Implementation of abstract FDT object model . 31
4.3 FDT Frame Application (FA) . 32
4.4 DTM Business Logic. 33
4.4.1 General . 33
4.4.2 Implementation of DTM, DTM Device Type, and Device Ident Info . 34
4.4.3 Implementation of DTM device parameter access . 35
4.4.4 Process Data Info . 35
4.4.5 Diagnostic Data Info . 36
4.4.6 Network Management Info . 36
4.4.7 Function Info . 37
4.4.8 Report Info . 37
4.4.9 Document Reference Info . 37
4.5 Implementation of DTM Functions . 37
4.5.1 DTM User Interface . 37
4.5.2 Function access control . 38
4.5.3 Handling of standard UI elements in modeless DTM UI interfaces . 38
4.5.4 Command functions . 39
4.6 User management . 39
4.6.1 General . 39
4.6.2 Multi-user access . 39
4.6.3 User levels . 39
4.7 Implementation of FDT and system topology . 42
4.7.1 General . 42
4.7.2 Topology management . 43
4.7.3 Data exchange between Frame Applications . 45
4.8 Implementation of Modularity . 45
4.9 Implementation of FDT communication . 45
4.9.1 Handling of communication requests . 45
4.9.2 Handling of communication errors . 46
4.9.3 Handling of loss of connection . 46
4.9.4 Point–to-point communication . 46
4.9.5 Nested communication . 47
4.9.6 Dynamic changes in network . 47
4.10 Identification . 48
4.10.1 DTM instance identification . 48
4.10.2 Hardware identification . 48
4.11 Implementation of DTM data persistence and synchronization . 49

IEC TR 62453-42:2016  IEC 2016 – 3 –
4.11.1 Persistence overview . 49
4.11.2 Relations of DTMDataSet . 50
4.11.3 DTMDataSet structure . 51
4.11.4 Types of persistent DTM data . 52
4.11.5 Data synchronization . 52
4.12 Implementation of access to device data and IO information . 53
4.12.1 Exposing device data and IO information . 53
4.12.2 Data access control . 54
4.12.3 Routed IO information . 56
4.12.4 Comparison of DTM and device data . 56
4.12.5 Support for multirole devices . 57
4.13 Clone of DTM instances . 58
4.13.1 General . 58
4.13.2 Replicating a part of topology with Parent DTM and a subset of its Child
DTMs . 58
4.13.3 Cloning of a DTM without its children . 58
4.13.4 Delayed cloning . 58
4.14 Lifecycle concepts . 59
4.15 Audit trail . 59
4.15.1 General . 59
4.15.2 Audit trail events . 59
5 Technical concepts . 60
5.1 General . 60
5.2 Support of .NET Common Language Runtime versions . 62
5.2.1 General . 62
5.2.2 Rules for FDT .NET assemblies . 62
5.2.3 DTM rules . 62
5.2.4 Frame Application rules . 62
5.2.5 FDT CLR extension concept . 63
5.3 Support for 32-bit and 64-bit target platforms . 63
5.4 Object activation and deactivation . 64
5.4.1 General . 64
5.4.2 Assembly loading and object creation . 64
5.4.3 Assembly dependencies . 65
5.4.4 Shared assemblies . 65
5.4.5 Object deactivation and unloading . 66
5.5 Datatypes . 67
5.5.1 General . 67
5.5.2 Serialization / deserialization . 67
5.5.3 Support of XML . 68
5.5.4 Optional elements . 68
5.5.5 Verify . 68
5.5.6 Clone . 68
5.5.7 Equals . 69
5.5.8 Lists . 69
5.5.9 Nullable . 70
5.5.10 Enumeration . 70
5.5.11 Protocol-specific datatypes. 70
5.5.12 Custom datatypes . 72

– 4 – IEC TR 62453-42:2016  IEC 2016
5.6 General object interaction. 73
5.6.1 General . 73
5.6.2 Decoupling of FDT Objects . 73
5.6.3 Parameter interchange with .NET datatypes . 74
5.6.4 Interaction patterns . 74
5.6.5 Properties . 74
5.6.6 Synchronous methods . 74
5.6.7 Asynchronous methods . 75
5.6.8 Events pattern . 81
5.6.9 Exception handling . 82
5.7 Threading . 86
5.7.1 Introduction . 86
5.7.2 Threading rules . 87
5.8 Localization support . 88
5.8.1 General . 88
5.8.2 Access to localized resources and culture-dependent functions . 89
5.8.3 Handling of cultures . 89
5.8.4 Switching the User Interface language . 90
5.9 DTM User Interface implementation . 90
5.9.1 General . 90
5.9.2 Resizing . 90
5.9.3 Private dialogs . 92
5.10 DTM User Interface hosting . 92
5.10.1 General . 92
5.10.2 Hosting DTM WPF controls . 92
5.10.3 Hosting DTM WinForms controls . 93
5.11 Static Function implementation . 94
5.12 Persistence . 96
5.12.1 Overview . 96
5.12.2 Data format . 97
5.12.3 Adding / reading / writing / deleting of data . 97
5.12.4 Searching for data . 99
5.13 Comparison of DTM and device data . 100
5.13.1 Comparison of datasets using IDeviceData / IInstanceData . 100
5.13.2 Comparison of datasets using IComparison . 101
5.14 Tracing . 101
5.15 Report generation . 101
5.15.1 General . 101
5.15.2 Report types . 102
5.15.3 DTM report data format . 102
5.15.4 Report data exchange . 103
5.16 Security . 103
5.16.1 General . 103
5.16.2 Strong naming of assemblies . 103
5.16.3 Identification of origin . 104
5.16.4 Code access security . 104
5.16.5 Validation of FDT compliance certification . 104
6 FDT Objects and interfaces . 106
6.1 General . 106

IEC TR 62453-42:2016  IEC 2016 – 5 –
6.2 Frame Application . 107
6.3 DTM Business Logic. 109
6.3.1 DTM BL interfaces . 109
6.3.2 State machines related to DTM BL . 114
6.3.3 State machine of instance data . 120
6.4 DTM User Interface . 123
6.5 Communication Channel . 124
6.6 Availability of interface methods . 125
7 FDT datatypes . 126
7.1 General . 126
7.2 Datatypes – Base . 127
7.3 General datatypes . 127
7.4 Datatypes – DtmInfo / TypeInfo . 128
7.5 Datatypes – DeviceIdentInfo . 130
7.6 Datatypes for installation and deployment . 135
7.6.1 Datatypes – SetupManifest . 135
7.6.2 Datatypes – DtmManifest . 136
7.6.3 Datatypes – DtmUiManifest . 137
7.7 Datatypes – Communication . 137
7.8 Datatypes – BusCategory . 143
7.9 Datatypes – Device / Instance Data . 143
7.9.1 General . 143
7.9.2 Datatypes used in reading and writing DeviceData . 150
7.10 Datatypes for export and import . 152
7.10.1 Datatypes – TopologyImportExport . 152
7.10.2 Datatypes – ImportExportDataset . 153
7.11 Datatypes for process data description . 154
7.11.1 Datatypes – ProcessDataInfo . 154
7.11.2 Datatypes – Process Image . 159
7.12 Datatypes – Address information . 160
7.13 Datatypes – NetworkDataInfo . 164
7.14 Datatypes – DTM functions . 166
7.15 Datatypes – DTM messages . 168
7.16 Datatypes for delegation of DTM UI dialog actions . 170
7.17 Datatypes – CommunicationChannelInfo . 170
7.18 Datatypes – HardwareIdentification and scanning . 172
7.18.1 General . 172
7.18.2 Datatypes – DeviceScanInfo . 172
7.18.3 Example – HardwareIdentification and scanning for HART . 173
7.19 Datatypes – DTM report types . 174
7.20 Information related to device modules in a monolithic DTM . 174
8 Workflows . 176
8.1 General . 176
8.2 Instantiation, loading and release . 176
8.2.1 Finding a DTM BL object . 176
8.2.2 Instantiation of a new DTM BL . 178
8.2.3 Configuring access rights . 180
8.2.4 Loading a DTM BL . 181
8.2.5 Loading a DTM with Expert user level . 182

– 6 – IEC TR 62453-42:2016  IEC 2016
8.2.6 Release of a DTM BL . 183
8.3 Persistent storage of a DTM . 184
8.3.1 Saving instance data of a DTM . 184
8.3.2 Copy and versioning of a DTM instance . 185
8.3.3 Dataset commit failed . 186
8.3.4 Export a DTM dataset to file . 186
8.4 Locking and DataTransactions in multi-user environments . 187
8.4.1 General . 187
8.4.2 Propagation of changes. 188
8.4.3 Synchronizing DTMs in multi-user environments . 190
8.5 Execution of DTM Functions . 191
8.5.1 General . 191
8.5.2 Finding a DTM User Interface object . 191
8.5.3 Instantiation of an integrated DTM graphical user interface . 192
8.5.4 Instantiation of a DTM UI triggered by the DTM BL . 193
8.5.5 Instantiation of a modal DTM UI triggered by DTM BL . 194
8.5.6 Release of a DTM User Interface . 195
8.5.7 Release of a DTM UI triggered by the DTM BL . 196
8.5.8 Release of a DTM User Interface triggered by itself . 197
8.5.9 Release of a non-modal DTM User Interface triggered by a standard
action . 198
8.5.10 Progress indication for prolonged DTM actions . 199
8.5.11 Starting an application . 200
8.5.12 Terminating applications . 201
8.5.13 Execution of command functions . 201
8.5.14 Execution of a command function with user interface . 201
8.5.15 Opening of documents . 202
8.5.16 Interaction between DTM User Interface and DTM Business Logic . 203
8.5.17 Interaction between DTM Business Logic and DTM User Interface . 205
8.5.18 Interaction between DTM User Interface and DTM Business Logic with
Cancel . 206
8.5.19 Retrieving information about available Static Functions . 207
8.5.20 Executing a Static Function . 208
8.5.21 Executing a Static Function with multiple arguments . 209
8.6 DTM communication . 210
8.6.1 General . 210
8.6.2 Establishing a communication connection . 211
8.6.3 Cancel establishment of communication connection . 212
8.6.4 Communicating with the device . 212
8.6.5 Frame Application or Child DTM disconnect a device . 213
8.6.6 Terminating a communication connection . 214
8.6.7 DTM aborts communication connection . 215
8.6.8 Communication Channel aborts communication connection . 216
8.7 Nested communication . 216
8.7.1 General . 216
8.7.2 Communication request for a nested connection . 217
8.7.3 Propagation of errors for a nested connection . 218
8.8 Topology planning . 219
8.8.1 General . 219

IEC TR 62453-42:2016  IEC 2016 – 7 –
8.8.2 Adding a DTM to the topology . 219
8.8.3 Removing a DTM from topology . 220
8.8.4 Frame Application creates topology . 221
8.8.5 DTM generates sub-topology . 222
8.8.6 Physical Layer and DataLinkLayer . 224
8.9 Instantiation, configuration, move and release of Child DTMs . 224
8.9.1 General . 224
8.9.2 Instantiation and configuration of Child DTM BL . 224
8.9.3 Interaction between Parent DTM and Child DTM . 225
8.9.4 Interaction between Parent DTM and Child DTM using IDtmMessaging . 227
8.9.5 Parent DTM moves a Child DTM . 227
8.9.6 Parent DTM removes Child DTM . 228
8.10 Topology scan . 229
8.10.1 General . 229
8.10.2 Scan of network topology . 229
8.10.3 Cancel topology scan . 230
8.10.4 Scan based DTM assignment . 231
8.10.5 Manufacturer-specific device identification . 232
8.11 Configuration of communication networks . 234
8.11.1 Configuration of a fieldbus master . 234
8.11.2 Integration of a passive device . 235
8.12 Using IO information . 235
8.12.1 Assignment of symbolic name to process data . 235
8.12.2 Creation of Process Image . 237
8.12.3 Validation of changes in process image while PLC is running . 238
8.12.4 Changing of variable names using process image interface . 239
8.13 Managing addresses . 240
8.13.1 Set DTM address with user interface . 240
8.13.2 Set DTM addresses without user interface . 241
8.13.3 Display or modify addresses of all Child DTMs with user interface . 242
8.14 Device-initiated data transfer . 243
8.15 Reading and writing data . 244
8.15.1 Read/write instance data . 244
8.15.2 Read/write device data . 246
8.16 Comparing data . 248
8.16.1 Comparing device dataset and instance dataset . 248
8.16.2 Comparing different instance datasets . 248
8.17 Reassigning a different DtmDeviceType at a device node . 249
8.17.1 General . 249
8.17.2 DTM detects a change in connected device type . 250
8.17.3 Search matching DtmDeviceTypes after incompatible device exchange . 252
8.17.4 Reassign DtmDeviceType after incompatible device exchange . 253
8.18 Copying part of FDT Topology . 255
8.18.1 Cloning of a single DTM without Children. 255
8.18.2 Cloning of a DTM with all its Children . 256
8.19 Sequences for audit trail . 256
8.19.1 General . 256
8.19.2 Audit trail of parameter modifications in instance dataset . 256
8.19.3 Audit trail of parameter modifications in device dataset . 257

– 8 – IEC TR 62453-42:2016  IEC 2016
8.19.4 Audit trail of function calls . 258
8.19.5 Audit trail of general notification . 259
9 Installation . 259
9.1 General . 259
9.2 Common rules . 259
9.2.1 Predefined installation paths . 259
9.2.2 Manifest files . 262
9.2.3 Paths in manifest files . 263
9.2.4 Common command line arguments . 263
9.2.5 Digital signatures of setup components . 264
9.3 Installation of FDT core assemblies . 264
9.4 Installation of communication protocols . 264
9.4.1 General . 264
9.4.2 Registration . 264
9.4.3 Protocol manifest . 264
9.5 Installation of DTMs . 265
9.5.1 General . 265
9.5.2 Registration . 266
9.5.3 DTM manifest . 267
9.5.4 DTM User Interface manifest . 268
9.6 DTM setup . 269
9.6.1 Structure . 269
9.6.2 DTM setup manifest . 270
9.6.3 DTM device identification manifest . 271
9.6.4 Setup creation rules . 273
9.7 DTM deployment . 274
9.8 Paths and file information . 276
9.8.1 Path information provided by a DTM . 276
9.8.2 Paths and persistence . 276
9.8.3 Multi-user systems . 276
10 Life cycle concept . 276
10.1 General . 276
10.2 Technical concept . 277
10.2.1 General . 277
10.2.2 DtmManifest / DtmInfo . 278
10.2.3 TypeInfo . 278
10.2.4 Supported DataSet formats . 279
10.2.5 DeviceIdentInfo . 279
10.2.6 Dataset . 280
10.2.7 DeviceScanInfo . 280
10.3 DTM setup . 280
10.4 Life Cycle Scenarios . 281
10.4.1 Overview . 281
10.4.2 Search for device type in DTM setups . 282
10.4.3 Search for installed DTMs . 283
10.4.4 Dataset migration for reassigned DTM . 285
11 Frame Application architectures . 286
11.1 General . 286
11.2 Standalone application . 286

-----------------
...