Name: BSI PD IEC/TR 62453-42:2016 PDF - PDF Standards Store
Price: 256.21 USD
Availability: InStock

IEC TR 62453-42:2016(E), which is a technical report, defines how the common FDT principles are implemented based on the .NET technology, including the object behaviour and object interaction via .NET interfaces. This document specifies FDT version 2.0.

PDF Catalog

PDF Pages	PDF Title
4	CONTENTS
21	FOREWORD
23	INTRODUCTION Figures Figure 1 – Relation of IEC 62453-42 to the IEC 62453 series
25	1 Scope 2 Normative references 3 Terms, definitions, abbreviations and conventions 3.1 Terms and definitions
32	3.2 Abbreviations 3.3 Conventions
33	4 Implementation concept 4.1 Technological orientation 4.2 Implementation of abstract FDT object model
34	4.3 FDT Frame Application (FA) Figure 2 – IEC 62453-42 Object Model Figure 3 – Frame Application
35	4.4 DTM Business Logic 4.4.1 General
36	4.4.2 Implementation of DTM, DTM Device Type, and Device Ident Info Figure 4 – DTM Business Logic
39	4.4.7 Function Info 4.4.8 Report Info 4.4.9 Document Reference Info 4.5 Implementation of DTM Functions 4.5.1 DTM User Interface
40	4.5.2 Function access control 4.5.3 Handling of standard UI elements in modeless DTM UI interfaces
41	4.5.4 Command functions 4.6 User management 4.6.1 General 4.6.2 Multi-user access 4.6.3 User levels
42	Table 1 – FDT User levels
43	Table 2 – Role dependent Access Rights and User Interfaces for DTMs
44	4.7 Implementation of FDT and system topology 4.7.1 General
45	4.7.2 Topology management Figure 7 – Logical topology and physical topology Figure 8 – FDT and logical topology
46	Figure 9 – DTMs and physical topology
47	4.7.3 Data exchange between Frame Applications 4.8 Implementation of Modularity 4.9 Implementation of FDT communication 4.9.1 Handling of communication requests
48	4.9.2 Handling of communication errors 4.9.3 Handling of loss of connection 4.9.4 Point–to-point communication Figure 10 – Point–to-point communication
49	4.9.5 Nested communication 4.9.6 Dynamic changes in network Figure 11 – Nested communication
50	4.10 Identification 4.10.1 DTM instance identification 4.10.2 Hardware identification
51	4.11 Implementation of DTM data persistence and synchronization 4.11.1 Persistence overview Figure 12 – Identification of connected devices
52	4.11.2 Relations of DTMDataSet Figure 13 – FDT storage and synchronization mechanism Figure 14 – Relation between DTMDataSet, DTM instance, and device
53	4.11.3 DTMDataSet structure Figure 15 – DTMDataSet structure
54	4.11.4 Types of persistent DTM data 4.11.5 Data synchronization
55	4.12 Implementation of access to device data and IO information 4.12.1 Exposing device data and IO information Figure 16 – Data Synchronization
56	4.12.2 Data access control
57	Table 3 – Description of properties related to data access control
58	4.12.3 Routed IO information 4.12.4 Comparison of DTM and device data Figure 17 – Routed IO information
59	4.12.5 Support for multirole devices Figure 18 – Multirole Device
60	4.13 Clone of DTM instances 4.13.1 General 4.13.2 Replicating a part of topology with Parent DTM and a subset of its Child DTMs 4.13.3 Cloning of a DTM without its children 4.13.4 Delayed cloning
61	4.14 Lifecycle concepts 4.15 Audit trail 4.15.1 General 4.15.2 Audit trail events
62	5 Technical concepts 5.1 General Figure 19 – FDT .NET Assemblies
63	Figure 20 – FDT Object implementation
64	5.2 Support of .NET Common Language Runtime versions 5.2.1 General 5.2.2 Rules for FDT .NET assemblies 5.2.3 DTM rules 5.2.4 Frame Application rules Table 4 – Supported CLR versions
65	5.2.5 FDT CLR extension concept 5.3 Support for 32-bit and 64-bit target platforms Figure 21 – FDT CLR extension concept
66	5.4 Object activation and deactivation 5.4.1 General 5.4.2 Assembly loading and object creation Figure 22 – Example: Assembly.LoadFrom()
67	5.4.3 Assembly dependencies 5.4.4 Shared assemblies Figure 23 – Example: Assembly dependencies
68	5.4.5 Object deactivation and unloading
69	5.5 Datatypes 5.5.1 General 5.5.2 Serialization / deserialization Figure 24 – Example: Datatype definition
70	5.5.3 Support of XML 5.5.4 Optional elements 5.5.5 Verify 5.5.6 Clone
71	5.5.7 Equals 5.5.8 Lists Figure 25 – Example: Data cloning Figure 26 – Example: Methods without data cloning
72	5.5.9 Nullable 5.5.10 Enumeration 5.5.11 Protocol-specific datatypes Figure 27 – Protocol-specific datatypes
73	Figure 28 – Protocol manifest and type info attributes
74	5.5.12 Custom datatypes Figure 29 – Example: Protocol assembly attributes Figure 30 – Example: Handling of protocol-specific assemblies in Frame Application
75	5.6 General object interaction 5.6.1 General 5.6.2 Decoupling of FDT Objects Figure 31 – Decoupled FDT Objects in IEC 62453-42
76	5.6.3 Parameter interchange with .NET datatypes 5.6.4 Interaction patterns 5.6.5 Properties 5.6.6 Synchronous methods
77	5.6.7 Asynchronous methods
78	Figure 32 – IAsyncResult pattern: blocking call Figure 33 – Example: Blocking use of asynchronous interface
79	Figure 34 – IAsyncResult pattern (simplified): blocking call Figure 35 – IAsyncResult pattern: non-blocking call
80	Figure 36 – Example: Non-blocking use of asynchronous interface Figure 37 – IAsyncResult pattern (simplified depiction): non-blocking call
82	Figure 38 – IAsyncResult pattern: canceling an operation
83	5.6.8 Events pattern Figure 39 – IAsyncResult pattern: providing progress events
84	5.6.9 Exception handling
88	5.7 Threading 5.7.1 Introduction
89	5.7.2 Threading rules
90	5.8 Localization support 5.8.1 General
91	5.8.2 Access to localized resources and culture-dependent functions 5.8.3 Handling of cultures
92	5.8.4 Switching the User Interface language 5.9 DTM User Interface implementation 5.9.1 General 5.9.2 Resizing
93	Figure 40 – Frame Application’s host window providing scroll bars Figure 41 – Control using internal scrollbars
94	5.9.3 Private dialogs 5.10 DTM User Interface hosting 5.10.1 General 5.10.2 Hosting DTM WPF controls
95	5.10.3 Hosting DTM WinForms controls Figure 42 – Example: Hosting a DTM WPF control in a WPF Frame Application Figure 43 – Example: Hosting a DTM WPF control in a WinForms Frame Application
96	5.11 Static Function implementation Figure 44 – Example: Hosting DTM WinForms controls in a WinForms Frame Application Figure 45 – Example: Hosting a DTM WinForms control in a WPF Frame Application
97	Figure 46 – Relation of StaticFunctionDescription to Static Function
98	5.12 Persistence 5.12.1 Overview Figure 47 – DTMDataset structure
99	5.12.2 Data format 5.12.3 Adding / reading / writing / deleting of data
100	Figure 48 – Example: Initialization of DTMDataSubset with DTM data Figure 49 – Example: Writing of DTM data in DTMDataSubset
101	5.12.4 Searching for data Figure 50 – Example: Reading of DTM data from a DTMDataSubset
102	5.13 Comparison of DTM and device data 5.13.1 Comparison of datasets using IDeviceData / IInstanceData Figure 51 – Example: Creation of a BulkData.DTMDataSubset with descriptor Figure 52 – Example: Searching for DTMDataSubsets with specific descriptor
103	5.13.2 Comparison of datasets using IComparison 5.14 Tracing 5.15 Report generation 5.15.1 General
104	5.15.2 Report types 5.15.3 DTM report data format
105	5.15.4 Report data exchange 5.16 Security 5.16.1 General 5.16.2 Strong naming of assemblies Figure 53 – Skeleton of a DTM-specific report fragment
106	5.16.3 Identification of origin 5.16.4 Code access security 5.16.5 Validation of FDT compliance certification Figure 54 – Example: Authenticode check
107	Figure 55 – Example: Conformity record file
108	6 FDT Objects and interfaces 6.1 General Figure 56 – Example: checking conformity record file
109	6.2 Frame Application Figure 57 – Frame Application interfaces
110	Table 5 – Frame Application interfaces
111	6.3 DTM Business Logic 6.3.1 DTM BL interfaces
112	Figure 58 – DTM Business Logic interfaces (Part 1)
113	Figure 59 – DTM Business Logic interfaces (Part 2)
114	Table 6 – DTM Business Logic interfaces
115	Table 7 – Availability of interfaces depending of type of DTM
116	6.3.2 State machines related to DTM BL
117	Figure 60 – State machine of DTM BL
118	Table 8 – Definition of DTM BL state machine
119	Figure 61 – Online state machine of DTM
120	Table 9 – Definition of online state machine
122	6.3.3 State machine of instance data Figure 62 – Modifications of data through a DTM
123	Figure 63 – ModifiedInDtm: State machine of instance data Table 10 – Description of instance dataset states
124	Figure 64 – ModifiedInDevice: State machine related to device data Table 11 – Description of dataset states regarding online modifications
125	6.4 DTM User Interface Figure 65 – DTM UI interfaces Tables
126	6.5 Communication Channel Figure 66 – Communication Channel interfaces Table 12 – DTM UI interfaces
127	6.6 Availability of interface methods Table 13 – Communication Channel interfaces Table 14 – Availability of DTM BL methods in different states
128	7 FDT datatypes 7.1 General
129	7.2 Datatypes – Base 7.3 General datatypes Figure 67 – FdtDatatype and FdtList Table 15 – FDT base datatypes
130	7.4 Datatypes – DtmInfo / TypeInfo Table 16 – FDT General datatypes
131	Figure 68 – DtmInfo / TypeInfo – datatypes Table 17 – DtmInfo datatype description
132	7.5 Datatypes – DeviceIdentInfo
133	Figure 69 – DeviceIdentInfo – datatypes Table 18 – DeviceIdentInfo datatype description
134	Figure 70 – DeviceIdentInfo – Example for HART
135	Table 19 – DeviceIdentInfo – Example for HART
136	Figure 71 – Example: DeviceIdentInfo creation
137	7.6 Datatypes for installation and deployment 7.6.1 Datatypes – SetupManifest Figure 72 – Example: Using DeviceIdentInfo Figure 73 – Example: DeviceIdentInfoTypeAttribute Figure 74 – SetupManifest – datatypes
138	7.6.2 Datatypes – DtmManifest Figure 75 – DtmManifest – datatypes Table 20 – SetupManifest datatype description Table 21 – DtmManifest datatype description
139	7.6.3 Datatypes – DtmUiManifest 7.7 Datatypes – Communication Figure 76 – DtmUiManifest – datatypes Table 22 – DtmUiManifest datatype description
140	Figure 77 – Communication datatypes – Connect Figure 78 – Communication datatypes – Transaction
141	Figure 79 – Communication datatypes – Disconnect Figure 80 – Communication datatypes – Subscribe
142	Figure 81 – Communication datatypes – Scanning Figure 82 – Communication datatypes – Address setting
143	Table 23 – Communication datatype description
144	Figure 83 – Example: Communication – Connect for HART
145	7.8 Datatypes – BusCategory 7.9 Datatypes – Device / Instance Data 7.9.1 General Figure 84 – Example: Communication – CommunicationType for HART Figure 85 – BusCategory – datatypes Table 24 – BusCategory datatype description
146	Figure 86 – Device / Instance data – datatypes
147	Table 25 – DeviceData datatype description
148	Figure 87 – Example: Providing information on data of a HART device
149	Figure 88 – Example: Providing information on module data of a PROFIBUS device
150	Figure 89 – Example: Providing information on data
151	Figure 90 – Example: Providing information on structured data
152	7.9.2 Datatypes used in reading and writing DeviceData Figure 91 – EnumInfo – datatype Figure 92 – Read and Write Request – datatypes Table 26 – Reading and Writing datatype description
153	Figure 93 – ResponseInfo – datatype Table 27 – Reading and Writing datatype description
154	7.10 Datatypes for export and import 7.10.1 Datatypes – TopologyImportExport Figure 94 – TopologyImportExport – datatypes
155	7.10.2 Datatypes – ImportExportDataset Figure 95 – ImportExportDataset – datatypes Table 28 – TopologyImportExport datatype description Table 29 – ImportExportDataset datatype description
156	7.11 Datatypes for process data description 7.11.1 Datatypes – ProcessDataInfo Figure 96 – ProcessDataInfo – datatypes
157	Figure 97 – IOSignalInfo – datatypes Table 30 – ProcessDataInfo datatype description
158	Table 31 – IOSignalInfo datatype description
159	Figure 98 – Example: ProcessDataInfo for HART (UML)
160	Figure 99 – Example: ProcessDataInfo creation for HART
161	7.11.2 Datatypes – Process Image Figure 100 – Example: Using ProcessData for HART Figure 101 – Example: IOSignalInfoType attribute
162	7.12 Datatypes – Address information Figure 102 – ProcessImage – datatypes Table 32 – ProcessImage datatype description
163	Figure 103 – AddressInfo – datatypes Table 33 – AddressInfo datatype description
164	Figure 104 – Example: AddressInfo creation
165	Figure 105 – Example: Using AddressInfo Figure 106 – Example: DeviceAddressTypeAttribute
166	7.13 Datatypes – NetworkDataInfo Figure 107 – NetworkDataInfo – datatypes
167	Figure 108 – Example: NetworkDataInfo creation example Table 34 – NetworkDataInfo datatype description
168	7.14 Datatypes – DTM functions Figure 109 – Example: NetworkDataInfo using example Figure 110 – Example: NetworkDataTypeAttribute example
169	Figure 111 – DTM Function – datatypes
170	7.15 Datatypes – DTM messages Table 35 – DTM Function datatype description
171	Figure 112 – DTM Messages – datatypes Table 36 – DTM Messages datatype description
172	7.16 Datatypes for delegation of DTM UI dialog actions 7.17 Datatypes – CommunicationChannelInfo Figure 113 – ActionItem – datatypes Figure 114 – CommunicationChannelInfo – datatypes Table 37 – ActionItem datatype description
173	Figure 115 – Example: Channel information Table 38 – CommunicationChannelInfo datatype description
174	7.18 Datatypes – HardwareIdentification and scanning 7.18.1 General 7.18.2 Datatypes – DeviceScanInfo Figure 116 – DeviceScanInfo – datatypes Table 39 – DeviceScanInfo datatype description
175	7.18.3 Example – HardwareIdentification and scanning for HART Figure 117 – Example: HARTDeviceScanInfo – datatype Table 40 – Example: HARTDeviceScanInfo datatype description
176	7.19 Datatypes – DTM report types 7.20 Information related to device modules in a monolithic DTM Figure 118 – DTM Report – datatypes Table 41 – Reporting datatype description
177	Figure 119 – Information related to device modules
178	8 Workflows 8.1 General 8.2 Instantiation, loading and release 8.2.1 Finding a DTM BL object
179	Figure 120 – Finding a DTM BL object
180	8.2.2 Instantiation of a new DTM BL
181	Figure 121 – Instantiation of a new DTM BL
182	8.2.3 Configuring access rights
183	8.2.4 Loading a DTM BL Figure 122 – Configuration of user permissions
184	8.2.5 Loading a DTM with Expert user level Figure 123 – Loading a DTM BL
185	8.2.6 Release of a DTM BL Figure 124 – Loading a DTM with Expert user level
186	8.3 Persistent storage of a DTM 8.3.1 Saving instance data of a DTM Figure 125 – Release of a DTM BL
187	8.3.2 Copy and versioning of a DTM instance Figure 126 – Saving data of a DTM
188	8.3.3 Dataset commit failed 8.3.4 Export a DTM dataset to file Figure 127 – Dataset commit failed
189	8.4 Locking and DataTransactions in multi-user environments 8.4.1 General Figure 128 – Export a DTM dataset to file
190	8.4.2 Propagation of changes
191	Figure 129 – Propagation of changes
192	8.4.3 Synchronizing DTMs in multi-user environments Figure 130 – Synchronizing DTMs in multi-user environments
193	8.5 Execution of DTM Functions 8.5.1 General 8.5.2 Finding a DTM User Interface object
194	8.5.3 Instantiation of an integrated DTM graphical user interface Figure 131 – Finding a DTM User Interface
195	8.5.4 Instantiation of a DTM UI triggered by the DTM BL Figure 132 – Instantiation of a DTM User Interface
196	8.5.5 Instantiation of a modal DTM UI triggered by DTM BL Figure 133 – Instantiation of a DTM UI triggered by DTM BL
197	8.5.6 Release of a DTM User Interface Figure 134 – Instantiation of a modal DTM UI triggered by DTM BL
198	8.5.7 Release of a DTM UI triggered by the DTM BL Figure 135 – Release of a DTM User Interface
199	8.5.8 Release of a DTM User Interface triggered by itself Figure 136 – Release of a DTM UI triggered by the DTM BL
200	8.5.9 Release of a non-modal DTM User Interface triggered by a standard action Figure 137 – Release of a DTM User Interface triggered by itself Figure 138 – Release of a non-modal DTM UI triggered by a standard action
201	8.5.10 Progress indication for prolonged DTM actions Figure 139 – Progress indication for prolonged DTM actions
202	8.5.11 Starting an application Figure 140 – Starting an application
203	8.5.12 Terminating applications 8.5.13 Execution of command functions 8.5.14 Execution of a command function with user interface Figure 141 – Execute a command function
204	8.5.15 Opening of documents Figure 142 – Execute a command function with user interface
205	8.5.16 Interaction between DTM User Interface and DTM Business Logic Figure 143 – Opening a document
206	Figure 144 – Interaction triggered by the DTM User Interface
207	8.5.17 Interaction between DTM Business Logic and DTM User Interface Figure 145 – Interaction triggered by the DTM Business Logic
208	8.5.18 Interaction between DTM User Interface and DTM Business Logic with Cancel Figure 146 – Interaction triggered and canceled by the DTM User Interface
209	8.5.19 Retrieving information about available Static Functions Figure 147 – Retrieving information about available Static Functions
210	8.5.20 Executing a Static Function Figure 148 – Example: Information about available Static Functions
211	8.5.21 Executing a Static Function with multiple arguments Figure 149 – Executing a Static Function
212	8.6 DTM communication 8.6.1 General Figure 150 – Executing a Static Function with multiple Arguments
213	8.6.2 Establishing a communication connection Figure 151 – Establishing a communication connection
214	8.6.3 Cancel establishment of communication connection 8.6.4 Communicating with the device Figure 152 – DTM cancels ongoing Connect operation
215	8.6.5 Frame Application or Child DTM disconnect a device Figure 153 – Communicating with the device
216	8.6.6 Terminating a communication connection Figure 154 – Child DTM disconnects
217	8.6.7 DTM aborts communication connection Figure 155 – Child DTM terminates a connection Figure 156 – Child DTM aborts a connection
218	8.6.8 Communication Channel aborts communication connection 8.7 Nested communication 8.7.1 General Figure 157 – Communication Channel aborts a connection
219	8.7.2 Communication request for a nested connection Figure 158 – Example: Nested communication behavior
220	8.7.3 Propagation of errors for a nested connection Figure 159 – Example: Nested communication data exchange
221	8.8 Topology planning 8.8.1 General 8.8.2 Adding a DTM to the topology
222	8.8.3 Removing a DTM from topology Figure 160 – Add DTM to topology
223	8.8.4 Frame Application creates topology Figure 161 – Removing a DTM from topology
224	8.8.5 DTM generates sub-topology Figure 162 – Frame Application creates topology
225	Figure 163 – DTM generates sub-topology
226	8.8.6 Physical Layer and DataLinkLayer 8.9 Instantiation, configuration, move and release of Child DTMs 8.9.1 General 8.9.2 Instantiation and configuration of Child DTM BL
227	8.9.3 Interaction between Parent DTM and Child DTM Figure 164 – Instantiation and configuration of Child DTM BL
228	Figure 165 – Interaction between Parent DTM and Child DTM
229	8.9.4 Interaction between Parent DTM and Child DTM using IDtmMessaging 8.9.5 Parent DTM moves a Child DTM Figure 166 – Interaction using IDtmMessaging
230	8.9.6 Parent DTM removes Child DTM Figure 167 – Parent DTM moves a Child DTM
231	8.10 Topology scan 8.10.1 General 8.10.2 Scan of network topology Figure 168 – Parent DTM removes Child DTM
232	8.10.3 Cancel topology scan Figure 169 – Scan of network topology
233	8.10.4 Scan based DTM assignment Figure 170 – Cancel topology scan
234	8.10.5 Manufacturer-specific device identification Figure 171 – Scan based DTM assignment
235	Figure 172 – Manufacturer-specific device identification
236	8.11 Configuration of communication networks 8.11.1 Configuration of a fieldbus master Figure 173 – Configuration of a fieldbus master
237	8.11.2 Integration of a passive device 8.12 Using IO information 8.12.1 Assignment of symbolic name to process data Figure 174 – Integration of a passive device
238	Figure 175 – Assignment of process data
239	8.12.2 Creation of Process Image
240	8.12.3 Validation of changes in process image while PLC is running Figure 176 – Creation of process image
241	8.12.4 Changing of variable names using process image interface Figure 177 – Validation of changes while PLC is running
242	8.13 Managing addresses 8.13.1 Set DTM address with user interface Figure 178 – Changing of variable names using process image interface
243	8.13.2 Set DTM addresses without user interface Figure 179 – Set DTM address with UI
244	8.13.3 Display or modify addresses of all Child DTMs with user interface Figure 180 – Set DTM addresses without UI
245	8.14 Device-initiated data transfer Figure 181 – Display or modify child addresses with UI
246	8.15 Reading and writing data 8.15.1 Read/write instance data Figure 182 – Device-initiated data transfer
247	Figure 183 – Read/write instance data
248	8.15.2 Read/write device data
249	Figure 184 – Read/write device data
250	8.16 Comparing data 8.16.1 Comparing device dataset and instance dataset 8.16.2 Comparing different instance datasets Figure 185 – Comparing device dataset and instance dataset
251	8.17 Reassigning a different DtmDeviceType at a device node 8.17.1 General Figure 186 – Compare instance data with persisted dataset
252	8.17.2 DTM detects a change in connected device type
253	Figure 187 – DTM triggers ActiveTypeChanged event
254	8.17.3 Search matching DtmDeviceTypes after incompatible device exchange
255	8.17.4 Reassign DtmDeviceType after incompatible device exchange Figure 188 – Find matching DtmDeviceTypes after incompatible device exchange
256	Figure 189 – Reassign a DtmDeviceType after incompatible device exchange
257	8.18 Copying part of FDT Topology 8.18.1 Cloning of a single DTM without Children Figure 190 – Clone DTM without children
258	8.18.2 Cloning of a DTM with all its Children 8.19 Sequences for audit trail 8.19.1 General 8.19.2 Audit trail of parameter modifications in instance dataset Figure 191 – Clone DTM with all children
259	8.19.3 Audit trail of parameter modifications in device dataset Figure 192 – Audit trail of parameter modifications in instance dataset
260	8.19.4 Audit trail of function calls Figure 193 – Audit trail of parameter modifications in device Figure 194 – Audit trail of function calls
261	8.19.5 Audit trail of general notification 9 Installation 9.1 General 9.2 Common rules 9.2.1 Predefined installation paths Table 42 – Predefined FDT installation paths
263	Figure 195 – GAC and FDT_Registry
264	9.2.2 Manifest files Figure 196 – Installation paths (with example DTM)
265	9.2.3 Paths in manifest files 9.2.4 Common command line arguments Table 43 – Predefined setup properties Table 44 – Setup command line parameters
266	9.2.5 Digital signatures of setup components 9.3 Installation of FDT core assemblies 9.4 Installation of communication protocols 9.4.1 General 9.4.2 Registration 9.4.3 Protocol manifest
267	9.5 Installation of DTMs 9.5.1 General Figure 197 – Example: Protocol manifest
268	9.5.2 Registration Figure 198 – Search for installed DTMs
269	9.5.3 DTM manifest
270	9.5.4 DTM User Interface manifest Figure 199 – Example: DtmManifest
271	9.6 DTM setup 9.6.1 Structure Figure 200 – Example: DtmUiManifest
272	9.6.2 DTM setup manifest Figure 201 – DTM setup structure
273	9.6.3 DTM device identification manifest Figure 202 – Example: DtmSetupManifest
275	9.6.4 Setup creation rules Figure 203 – Example: DeviceIdentManifest
276	9.7 DTM deployment
277	Figure 204 – DTM deployment
278	9.8 Paths and file information 9.8.1 Path information provided by a DTM 9.8.2 Paths and persistence 9.8.3 Multi-user systems 10 Life cycle concept 10.1 General
279	10.2 Technical concept 10.2.1 General Figure 205 – Overview DTM identification
280	10.2.2 DtmManifest / DtmInfo 10.2.3 TypeInfo Table 45 – DTM identification Table 46 – DtmType – user readable description of supported types
281	10.2.4 Supported DataSet formats 10.2.5 DeviceIdentInfo Table 47 – TypeInfo identification Table 48 – DtmType – Dataset support identification
282	10.2.6 Dataset 10.2.7 DeviceScanInfo 10.3 DTM setup Table 49 – Dataset identification Table 50 – DeviceScanInfo – scanned device identification
283	10.4 Life Cycle Scenarios 10.4.1 Overview Figure 206 – Identification attributes in DTM setup Table 51 – Setup information
284	10.4.2 Search for device type in DTM setups Table 52 – Changing DTM–- overview
285	10.4.3 Search for installed DTMs Figure 207 – Check DTM Setup for list of supported types
286	Figure 208 – Scan installed DTMs
287	10.4.4 Dataset migration for reassigned DTM Figure 209 – Dataset migration to a reassigned DtmDeviceType
288	11 Frame Application architectures 11.1 General 11.2 Standalone application 11.3 Remoted user Interface Figure 210 – Client / Server Application
289	11.4 Distributed multi-user application 11.5 OPC UA Figure 211 – Example for distributed multi-user application
290	Figure 212 – OPC UA server based on IEC TR 62453-42
291	Annex A (normative)FDT2 Use case model A.1 Use case model overview A.2 Actors Figure A.1 – Main use case diagram
292	A.3 Use cases A.3.1 Use case overview Table A.1 – Actors
293	A.3.2 Observation use cases Figure A.2 – Observation use cases Table A.2 – Observation use cases
294	A.3.3 Operation use cases
295	Figure A.3 – Operation use cases Table A.3 – Operation use cases
296	A.3.4 Maintenance use cases
297	Figure A.4 – Maintenance use cases
298	Table A.4 – Maintenance use cases
301	A.3.5 Planning use cases Figure A.5 – Planning use cases Table A.5 – Planning use cases
303	A.3.6 Main Operation
304	A.3.7 OEM Service A.3.8 Administration
305	Annex B (normative)FDT interface definition and datatypes
306	Annex C (normative)Mapping of services to interface methods C.1 General C.2 DTM services Table C.1 – General services Table C.2 – DTM services related to installation Table C.3 – DTM service related to DTM Information
307	Table C.4 – DTM services related to DTM state machine Table C.5 – DTM services related to function
308	Table C.6 – DTM services related to documentation Table C.7 – DTM services to access the instance data Table C.8 – DTM services to access diagnosis Table C.9 – DTM services to access to device data
309	Table C.10 – DTM services related to network management information Table C.11 – DTM services related to online operation Table C.12 – DTM services related to FDT-Channel objects
310	C.3 Presentation object services C.4 General channel services C.5 Process channel services Table C.13 – DTM services related to import and export Table C.14 – DTM services related to data synchronization Table C.15 – DTM UI state control Table C.16 – General channel service
311	C.6 Communication Channel Services Table C.17 – Channel services for IO related information Table C.18 – Channel services related to communication Table C.19 – Channel services related sub-topology management
312	C.7 Frame Application Services Table C.20 – Channel services related to functions Table C.21 – Channel services related to scan Table C.22 – FA services related to general events
313	Table C.23 – FA services related to topology management Table C.24 – FA services related to redundancy Table C.25 – FA services related to storage of DTM data Table C.26 – FA services related to DTM data synchronization
314	Table C.27 – FA related to presentation Table C.28 – FA services related to audit trail
315	Annex D (normative)FDT version interoperability guide D.1 Overview D.2 General
316	D.3 Component interoperability Table D.1 – Interoperability between components of different versions
317	Annex E (normative)FDT1.2.x / IEC 62453-42 Backward-Compatibility E.1 Overview E.2 Parallel FDT topologies Figure E.1 – Example: IEC TR 62453-42 Frame Applicationwith FDT1.2.x backward-compatibility support
318	E.3 Mixed FDT topologies Figure E.2 – IEC TR 62453-42 Frame Application with FDT1.2.x Device DTM
319	Figure E.3 – IEC TR 62453-42 Frame Application with FDT1.2.x Comm. and Gateway DTM Figure E.4 – IEC TR 62453-42 Frame Application with FDT1.2.x Gateway DTM
320	E.4 FDT1.2.x / IEC 62453-42 Adapters
321	E.5 FDT1.2.x XML / IEC TR 62453-42 Datatype Transformers E.5.1 General Table E.1 – Adapter interface mappings
322	E.5.2 Installation and Registration of Protocol-specific Transformers
323	E.5.3 Interaction between FDT2 and FDT1.2 components using Transformers
324	E.6 Sequences related to backward compatibility E.6.1 General E.6.2 Dataset migration from FDT1.x DTM to FDT2.x DTM Figure E.5 – IEC TR 62453-42 – FDT1.2 interaction using transformer
325	Figure E.6 – Dataset migration from FDT1.x DTM to FDT2.x DTM
326	Annex F (informative)Implementation Hints F.1 IAsyncResult pattern
327	F.2 Threading Best Practices
328	Annex G (informative)Trade names
329	Annex H (informative)UML Notation H.1 General H.2 Class diagram Figure H.1 – Note Figure H.2 – Class Figure H.3 – Association
330	Figure H.4 – Navigable Association Figure H.5 – Composition Figure H.6 – Aggregation Figure H.7 – Dependency
331	Figure H.9 – Abstract class, Generalization and Interface Figure H.10 – Interface related notations
332	H.3 Statechart diagram Figure H.11 – Multiplicity Figure H.12 – Enumeration datatype Figure H.13 – Elements of UML statechart diagrams
333	H.4 Use case diagram Figure H.14 – Example of UML state chart diagram Figure H.15 – UML use case syntax
334	H.5 Sequence diagram Figure H.16 – UML sequence diagram Figure H.17 – Empty UML sequence diagram frame
335	Figure H.18 – Object with life line and activation Figure H.19 – Method calls Figure H.20 – Modeling guarded call and multiple calls
336	Figure H.21 – Call to itself Figure H.22 – Continuation / StateInvariant
337	Figure H.23 – Alternative fragment Figure H.24 – Option fragment Figure H.25 – Loop combination fragment Figure H.26 – Break notation
338	H.6 Object diagram Figure H.27 – Sequence reference Figure H.28 – Objects Figure H.29 – Object association
339	Annex I (informative)Physical Layer Examples I.1 General I.2 Interbus S I.3 PROFIBUS I.4 PROFINET
341	Annex J (informative)Predefined SemanticIds J.1 General J.2 Data J.3 Images J.4 Documents
343	Bibliography

Published By	Publication Date	Number of Pages
BSI	2016	346


PDF Format	Searchable	Printable	Preview Now

Status	Withdrawn
Pages	346
Publication Date	2016-04-26
Withdrawn Date	2019-05-03
ISBN	978 0 580 82514 9
Standard Number	PD IEC/TR 62453-42:2016
Title	Field device tool (FDT) interface specification – Object model integration profile. Common Language Infrastructure
Identical National Standard Of	IEC TR 62453-42:2016
Descriptors	Automatic control systems, Open systems interconnection, Industrial, Fieldbus, Communication procedures, Data transmission, Interfaces (data processing), Bus networks, Computer networks, Communication networks, Control equipment, Process control, Application layer (OSI)
Publisher	BSI
Committee	GEL/65/3
ICS Codes	35.110 - Networking