OPC unified architecture - Part 100: Devices

IEC 62541-100:2025 defines the information model associated with Devices. This document describes three models which build upon each other as follows: • The (base) Device Model is intended to provide a unified view of devices and their hardware and software parts irrespective of the underlying device protocols. • The Device Communication Model adds Network and Connection information elements so that communication topologies can be created. • The Device Integration Host Model finally adds additional elements and rules required for host systems to manage integration for a complete system. It enables reflecting the topology of the automation system with the devices as well as the connecting communication networks. This document also defines AddIns that can be used for the models in this document but also for models in other information models. They are: • Locking model – a generic AddIn to control concurrent access, • Software update model – an AddIn to manage software in a Device. This second edition cancels and replaces the first edition published in 2015. This edition constitutes a technical revision. This edition includes the following significant technical changes with respect to the previous edition: a a ComponentType that can be used to model any HW or SW element of a device has been defined and a SoftwareType has been added as subtype of ComponentType; b the new OPC UA interface concept and defined interfaces for Nameplate, DeviceHealth, and SupportInfo has been added. c) a new model for Software Update (Firmware Update) has been added; d) a new entry point for documents where each document is represented by a FileType instance has been specified; e) a model that provides information about the lifetime, related limits and semantic of the lifetime of things like tools, material or machines has been added.

OPC Unified Architecture - Teil 100: Geräteschnittstelle

Architecture unifiée OPC - Partie 100: Appareils

IEC 62541-100:2025 définit le modèle d'information associé aux Appareils. Le présent document décrit trois modèles qui s'appuient les uns sur les autres, comme suit: • le Modèle d'appareil (de base) vise à fournir une vue unifiée des appareils et de leurs parties matérielles et logicielles, et ce, indépendamment des protocoles d'appareils sous-jacents; • le Modèle de communication d'appareil ajoute des éléments d'information de Réseau et de Connexion afin de pouvoir créer les topologies de communication; • enfin, le Modèle d'hôte d'intégration d'appareil ajoute des éléments et des règles supplémentaires exigés pour que les systèmes hôtes gèrent l'intégration pour un système complet. Il permet également de refléter la topologie du système d'automatisation avec les appareils ainsi qu'avec les réseaux de communication connectés. Le présent document définit également les AddIns qui peuvent être utilisés pour les modèles de ce document, mais également pour ceux d'autres modèles d'information. À savoir: • Modèle de verrouillage – AddIn générique pour contrôler l'accès simultané; • Modèle de mise à jour logicielle – AddIn pour gérer le logiciel dans un Appareil. Cette deuxième édition annule et remplace la première édition parue en 2015. Cette édition constitue une révision technique. Cette édition inclut les modifications techniques majeures suivantes par rapport à l'édition précédente: a) un ComponentType qui peut être utilisé pour modéliser tout élément matériel ou logiciel d'un appareil a été ajouté, ainsi qu'un SoftwareType en tant que sous-type de ComponentType; b) le nouveau concept d'interface OPC UA et des interfaces définies pour Nameplate, DeviceHealth et SupportInfo ont été ajoutés; c) un nouveau modèle pour la mise à jour logicielle (mise à jour du micrologiciel) a été ajouté; d) un nouveau point d'entrée pour les documents où chacun d'entre eux est représenté par une instance de FileType a été spécifié; e) un modèle qui fournit des informations relatives à la durée de vie, aux limites associées et à la sémantique de la durée de vie d'éléments tels que des outils, du matériel ou des machines a été ajouté.

Enotna arhitektura OPC - 100. del: Vmesnik naprave

General Information

Status
Not Published
Publication Date
05-Feb-2026
Current Stage
6055 - Ratification Completed (DOR) - Publishing
Start Date
21-Jan-2026
Completion Date
21-Jan-2026

Relations

Effective Date
03-Feb-2026
Effective Date
03-Feb-2026
Effective Date
03-Feb-2026
Effective Date
03-Feb-2026
Effective Date
03-Feb-2026
Effective Date
03-Feb-2026
Effective Date
03-Feb-2026
Effective Date
03-Feb-2026
Effective Date
03-Feb-2026
Effective Date
03-Feb-2026
Effective Date
03-Feb-2026
Effective Date
03-Feb-2026
Effective Date
31-Jan-2023

Overview

prEN IEC 62541-100:2024 - OPC unified architecture - Part 100: Devices (CLC / IEC 62541-100:2025) defines the OPC UA information model for representing industrial devices, their hardware/software components, communications and host integration. The document specifies three layered models - the Device Model, Device Communication Model, and Device Integration Host Model - plus reusable AddIns (Locking, Software Update). This second edition is a technical revision that replaces the 2015 edition.

Key topics and technical requirements

  • Device Model

    • Provides a unified, protocol-agnostic representation of devices and their HW/SW elements.
    • Introduces a generic ComponentType and a SoftwareType (subtype) to model components consistently.
  • Device Communication Model

    • Adds Network and Connection elements so communication topologies and network relationships can be represented.
    • Defines ConnectionPoint, NetworkSet and reference types (e.g., ConnectsTo).
  • Device Integration Host Model

    • Adds elements and rules for host systems to manage device integration and to reflect automation-system topology (DeviceTopology, Online/Offline semantics, data transfer methods).
  • Interfaces and AddIns

    • New OPC UA interface concept with defined interfaces for Nameplate, DeviceHealth, and SupportInfo.
    • Locking model AddIn to control concurrent access to device resources.
    • Software update (Firmware Update) model AddIn covering update behaviors, state machines, update packages and safety/security considerations.
  • Other notable features

    • New entry point for documents where each document is represented by a FileType instance.
    • Lifetime model to represent lifetime, limits and semantic indicators (e.g., tools, consumables, machines).
    • Profiles and conformance units to support phased implementation.

Practical applications

  • Enables consistent device representation across OT/IT systems for:
    • Device manufacturers exposing device metadata and firmware/update capabilities via OPC UA.
    • System integrators and automation engineers mapping device topologies and networks.
    • Software vendors building Asset Management, Maintenance, and Device Management tools that consume standardized device information.
    • Operational teams implementing safe, auditable firmware update workflows and concurrent-access control.

Who should use this standard

  • Device vendors, automation OEMs, systems integrators, industrial software developers, asset/maintenance managers, and OT/IT architects implementing OPC UA-based device models, software update mechanisms and topology-aware integration.

Related standards

  • Part of the IEC/IEC 62541 (OPC UA) series; consult base OPC UA specifications and other 62541 parts for communication stacks, security and data modeling guidance.
Draft

prEN IEC 62541-100:2024 - BARVE

English language
143 pages
Preview
Preview
e-Library read for
1 day

Get Certified

Connect with accredited certification bodies for this standard

BSI Group

BSI (British Standards Institution) is the business standards company that helps organizations make excellence a habit.

UKAS United Kingdom Verified

National Aerospace and Defense Contractors Accreditation Program (NADCAP)

Global cooperative program for special process quality in aerospace.

ANAB United States Verified

CARES (UK Certification Authority for Reinforcing Steels)

UK certification for reinforcing steels and construction.

UKAS United Kingdom Verified

Sponsored listings

Frequently Asked Questions

EN IEC 62541-100:2026 is a draft published by CLC. Its full title is "OPC unified architecture - Part 100: Devices". This standard covers: IEC 62541-100:2025 defines the information model associated with Devices. This document describes three models which build upon each other as follows: • The (base) Device Model is intended to provide a unified view of devices and their hardware and software parts irrespective of the underlying device protocols. • The Device Communication Model adds Network and Connection information elements so that communication topologies can be created. • The Device Integration Host Model finally adds additional elements and rules required for host systems to manage integration for a complete system. It enables reflecting the topology of the automation system with the devices as well as the connecting communication networks. This document also defines AddIns that can be used for the models in this document but also for models in other information models. They are: • Locking model – a generic AddIn to control concurrent access, • Software update model – an AddIn to manage software in a Device. This second edition cancels and replaces the first edition published in 2015. This edition constitutes a technical revision. This edition includes the following significant technical changes with respect to the previous edition: a a ComponentType that can be used to model any HW or SW element of a device has been defined and a SoftwareType has been added as subtype of ComponentType; b the new OPC UA interface concept and defined interfaces for Nameplate, DeviceHealth, and SupportInfo has been added. c) a new model for Software Update (Firmware Update) has been added; d) a new entry point for documents where each document is represented by a FileType instance has been specified; e) a model that provides information about the lifetime, related limits and semantic of the lifetime of things like tools, material or machines has been added.

IEC 62541-100:2025 defines the information model associated with Devices. This document describes three models which build upon each other as follows: • The (base) Device Model is intended to provide a unified view of devices and their hardware and software parts irrespective of the underlying device protocols. • The Device Communication Model adds Network and Connection information elements so that communication topologies can be created. • The Device Integration Host Model finally adds additional elements and rules required for host systems to manage integration for a complete system. It enables reflecting the topology of the automation system with the devices as well as the connecting communication networks. This document also defines AddIns that can be used for the models in this document but also for models in other information models. They are: • Locking model – a generic AddIn to control concurrent access, • Software update model – an AddIn to manage software in a Device. This second edition cancels and replaces the first edition published in 2015. This edition constitutes a technical revision. This edition includes the following significant technical changes with respect to the previous edition: a a ComponentType that can be used to model any HW or SW element of a device has been defined and a SoftwareType has been added as subtype of ComponentType; b the new OPC UA interface concept and defined interfaces for Nameplate, DeviceHealth, and SupportInfo has been added. c) a new model for Software Update (Firmware Update) has been added; d) a new entry point for documents where each document is represented by a FileType instance has been specified; e) a model that provides information about the lifetime, related limits and semantic of the lifetime of things like tools, material or machines has been added.

EN IEC 62541-100:2026 is classified under the following ICS (International Classification for Standards) categories: 25.040.40 - Industrial process measurement and control; 35.100.05 - Multilayer applications. The ICS classification helps identify the subject area and facilitates finding related standards.

EN IEC 62541-100:2026 has the following relationships with other standards: It is inter standard links to EN IEC 62541-4:2020, EN IEC 62541-6:2026, EN IEC 62541-9:2020, EN IEC 62541-1:2026, EN IEC 62541-8:2026, EN IEC 62541-7:2020, EN IEC 62541-7:2026, EN IEC 62541-4:2026, EN IEC 62541-3:2026, EN IEC 62541-5:2026, EN IEC 62769-8:2023, EN IEC 62541-21:2026, EN 62541-100:2015. Understanding these relationships helps ensure you are using the most current and applicable version of the standard.

EN IEC 62541-100:2026 is associated with the following European legislation: Standardization Mandates: M/490. When a standard is cited in the Official Journal of the European Union, products manufactured in conformity with it benefit from a presumption of conformity with the essential requirements of the corresponding EU directive or regulation.

EN IEC 62541-100:2026 is available in PDF format for immediate download after purchase. The document can be added to your cart and obtained through the secure checkout process. Digital delivery ensures instant access to the complete standard document.

Standards Content (Sample)


SLOVENSKI STANDARD
01-marec-2024
Enotna arhitektura OPC - 100. del: Vmesnik naprave
OPC unified architecture - Part 100: Device interface
Architecture unifiée OPC - Partie 100: Interface d'appareils
Ta slovenski standard je istoveten z: prEN IEC 62541-100:2024
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.

65E/1050/CDV
COMMITTEE DRAFT FOR VOTE (CDV)
PROJECT NUMBER:
IEC 62541-100 ED2
DATE OF CIRCULATION: CLOSING DATE FOR VOTING:
2024-01-26 2024-04-19
SUPERSEDES DOCUMENTS:
65E/972/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.
Recipients of this document are invited to submit, with their comments, notification of any relevant “In Some Countries” clauses
to be included should this proposal proceed. Recipients are reminded that the CDV stage is the final stage for submitting ISC
clauses. (SEE AC/22/2007 OR NEW GUIDANCE DOC).

TITLE:
OPC Unified Architecture - Part 100: Device Interface

PROPOSED STABILITY DATE: 2026
NOTE FROM TC/SC OFFICERS:
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.

IEC CDV 62541-100 © IEC 2023 i

1 CONTENTS
3 FOREWORD . xi
4 1 Scope . 1
5 2 Reference documents . 1
6 3 Terms, definitions, abbreviated terms, and conventions . 2
7 3.1 Terms and definitions . 2
8 3.2 Abbreviated terms . 3
9 3.3 Conventions used in this document . 4
10 3.3.1 Conventions for Node descriptions . 4
11 3.3.2 NodeIds and BrowseNames . 6
12 3.3.3 Common Attributes . 7
13 4 Device model . 9
14 4.1 General . 9
15 4.2 Usage guidelines . 10
16 4.3 TopologyElementType . 10
17 4.4 FunctionalGroupType . 11
18 4.4.1 Model . 11
19 4.4.2 Recommended FunctionalGroup BrowseNames . 12
20 4.4.3 UIElement Type . 13
21 4.5 Interfaces . 14
22 4.5.1 Overview . 14
23 4.5.2 VendorNameplate Interface . 14
24 4.5.3 TagNameplate Interface . 16
25 4.5.4 DeviceHealth Interface . 17
26 4.5.5 OperationCounter Interface . 18
27 4.5.6 SupportInfo Interface . 20
28 4.6 ComponentType . 22
29 4.7 DeviceType . 23
30 4.8 SoftwareType . 26
31 4.9 DeviceSet entry point . 26
32 4.10 DeviceFeatures entry point . 27
33 4.11 BlockType . 28
34 4.12 DeviceHealth Alarm Types . 29
35 4.12.1 General . 29
36 4.12.2 DeviceHealthDiagnosticAlarmType . 30
37 4.12.3 FailureAlarmType . 30
38 4.12.4 CheckFunctionAlarmType . 31
39 4.12.5 OffSpecAlarmType . 31
40 4.12.6 MaintenanceRequiredAlarmType . 31
41 5 Device communication model . 32
42 5.1 General . 32
43 5.2 ProtocolType . 33
44 5.3 Network . 35
45 5.4 ConnectionPoint . 36
46 5.5 ConnectsTo and ConnectsToParent ReferenceTypes . 37
47 5.6 NetworkSet Object . 39
48 6 Device integration host model . 40

ii IEC CDV 62541-100 © IEC 2023

49 6.1 General . 40
50 6.2 DeviceTopology Object . 41
51 6.3 Online/Offline . 42
52 6.3.1 General . 42
53 6.3.2 IsOnline ReferenceType . 43
54 6.4 Offline-Online data transfer . 44
55 6.4.1 Definition . 44
56 6.4.2 TransferServices Type . 44
57 6.4.3 TransferServices Object . 45
58 6.4.4 TransferToDevice Method . 45
59 6.4.5 TransferFromDevice Method . 46
60 6.4.6 FetchTransferResultData Method . 47
61 7 Locking model . 51
62 7.1 Overview . 51
63 7.2 LockingServices Type . 51
64 7.3 LockingServices Object . 53
65 7.4 MaxInactiveLockTime Property . 53
66 7.5 InitLock Method . 53
67 7.6 ExitLock Method . 54
68 7.7 RenewLock Method . 55
69 7.8 BreakLock Method . 55
70 8 Software update model . 57
71 8.1 Overview . 57
72 8.2 Use Cases . 57
73 8.2.1 Supported Use Cases . 57
74 8.2.2 Unsupported Use Cases . 59
75 8.3 General . 59
76 8.3.1 System perspective . 59
77 8.3.2 Types of software . 60
78 8.3.3 Types of Devices . 60
79 8.3.4 Options for the Server . 60
80 8.3.5 Software Update Client . 63
81 8.3.6 Safety considerations . 67
82 8.3.7 Security considerations . 67
83 8.3.8 Update Behavior . 68
84 8.3.9 Installation of patches . 68
85 8.3.10 Incompatible parameters / settings . 68
86 8.3.11 AddIn model . 68
87 8.4 ObjectTypes . 69
88 8.4.1 SoftwareUpdateType . 69
89 8.4.2 SoftwareLoadingType . 72
90 8.4.3 PackageLoadingType . 72
91 8.4.4 DirectLoadingType . 74
92 8.4.5 CachedLoadingType . 75
93 8.4.6 FileSystemLoadingType . 77
94 8.4.7 SoftwareVersionType . 79
95 8.4.8 PrepareForUpdateStateMachineType . 81
96 8.4.9 InstallationStateMachineType . 84
97 8.4.10 PowerCycleStateMachineType . 89

IEC CDV 62541-100 © IEC 2023 iii

98 8.4.11 ConfirmationStateMachineType . 90
99 8.5 DataTypes . 92
100 8.5.1 SoftwareVersionFileType . 92
101 8.5.2 UpdateBehavior OptionSet . 93
102 9 Specialized topology elements . 94
103 9.1 General . 94
104 9.2 Configurable components . 94
105 9.2.1 General pattern . 94
106 9.2.2 ConfigurableObjectType . 94
107 9.3 Block Devices. 95
108 9.4 Modular Devices. 96
109 10 Lifetime model . 98
110 10.1 General . 98
111 10.2 LifetimeVariableType definition. 98
112 10.2.1 Overview . 98
113 10.2.2 VariableType definition. 98
114 10.3 BaseLifetimeIndicationType definition . 100
115 10.3.1 Overview . 100
116 10.3.2 ObjectType definition . 100
117 10.4 TimeIndicationType definition . 100
118 10.4.1 Overview . 100
119 10.4.2 ObjectType definition . 100
120 10.5 NumberOfPartsIndicationType definition . 100
121 10.5.1 Overview . 100
122 10.5.2 ObjectType definition . 101
123 10.6 NumberOfUsagesIndicationType definition . 101
124 10.6.1 Overview . 101
125 10.6.2 ObjectType definition . 101
126 10.7 LengthIndicationType definition . 101
127 10.7.1 Overview . 101
128 10.7.2 ObjectType definition . 101
129 10.8 DiameterIndicationType definition. 101
130 10.8.1 Overview . 101
131 10.8.2 ObjectType definition . 102
132 10.9 SubstanceVolumeIndicationType definition . 102
133 10.9.1 Overview . 102
134 10.9.2 ObjectType definition . 102
135 11 Profiles and ConformanceUnits . 103
136 11.1 Conformance Units . 103
137 11.2 Profiles . 105
138 11.2.1 General . 105
139 11.2.2 Profile list . 105
140 11.2.3 Device Server Facets . 106
141 11.2.4 Device Client Facets . 108
142 12 Namespaces . 111
143 12.1 Namespace Metadata . 111
144 12.2 Handling of OPC UA namespaces . 111
145 Annex A (normative) Namespace and mappings . 113

iv IEC CDV 62541-100 © IEC 2023

146 Annex B (informative) Examples . 114
147 B.1 Functional Group Usages . 114
148 B.2 Identification Functional Group . 115
149 B.3 Software Update examples . 115
150 B.3.1 Factory Automation Example . 115
151 B.3.2 Update sequence using Direct-Loading . 118
152 B.3.3 Update sequence using Cached-Loading . 119
153 B.3.4 Update sequence using File System based Loading . 120
154 Annex C (informative) Guidelines for the usage of OPC UA for Devices as base for
155 Companion Specifications . 122
156 C.1 Overview . 122
157 C.2 Guidelines to define Companion Specifications based on OPC UA for Devices . 124
158 C.3 Guidelines on how to combine different companion specifications based on OPC
159 UA for Devices in one OPC UA application . 125
160 C.4 Guidelines to manage the same Variables defined in different places . 127
161 C.5 Guidelines on how to use functionality in companion specifications . 128
162 Bibliography . 130
IEC CDV 62541-100 © IEC 2023 v

164 FIGURES
165 Figure 1 – Device model overview . 9
166 Figure 2 – Components of the TopologyElementType . 10
167 Figure 3 – FunctionalGroupType . 12
168 Figure 4 – Overview of Interfaces for Devices and Device components . 14
169 Figure 5 – VendorNameplate Interface . 14
170 Figure 6 – TagNameplate Interface . 17
171 Figure 7 – DeviceHealth Interface . 17
172 Figure 8 – Support information Interface . 20
173 Figure 9 – ComponentType . 22
174 Figure 10 – DeviceType . 24
175 Figure 11 – SoftwareType . 26
176 Figure 12 – Standard entry point for Devices . 27
177 Figure 13 – Standard entry point for DeviceFeatures . 28
178 Figure 14 – BlockType hierarchy . 28
179 Figure 15 – Device Health Alarm type hierarchy . 30
180 Figure 16 – Device communication model overview . 32
181 Figure 17 – Example of a communication topology . 33
182 Figure 18 – Example of a ProtocolType hierarchy with instances that represent specific
183 communication profiles . 34
184 Figure 19 – NetworkType . 35
185 Figure 20 – Example of ConnectionPointType hierarchy . 36
186 Figure 21 – ConnectionPointType. 36
187 Figure 22 – ConnectionPoint usage . 37
188 Figure 23 – Type Hierarchy for ConnectsTo and ConnectsToParent References . 38
189 Figure 24 – Example with ConnectsTo and ConnectsToParent References . 39
190 Figure 25 – Example of an automation system . 40
191 Figure 26 – Example of a Device topology . 41
192 Figure 27 – Online component for access to Device data . 42
193 Figure 28 – Type hierarchy for IsOnline Reference . 43
194 Figure 29 – TransferServicesType . 44
195 Figure 30 – TransferServices . 45
196 Figure 31 – LockingServicesType . 51
197 Figure 32 – LockingServices . 53
198 Figure 33 – Example with a device and several software components . 60
199 Figure 34 – Determine the type of update that the Server implements. . 63
200 Figure 35 – Different flows of Direct-Loading, Cached-Loading and FileSystem based
201 Loading . 64
202 Figure 36 – Prepare and Resume activities . 65
203 Figure 37 – Installation activity for Direct-Loading . 66
204 Figure 38 – Installation activity for Cached-Loading and File System based Loading . 66
205 Figure 39 – Resume activity . 67
206 Figure 40 – Example how to add the SoftwareUpdate AddIn to a component . 69
207 Figure 41 – SoftwareUpdateType . 70

vi IEC CDV 62541-100 © IEC 2023

208 Figure 42 – PackageLoadingType . 73
209 Figure 43 – DirectLoadingType. 74
210 Figure 44 – CachedLoadingType . 75
211 Figure 45 – FileSystemLoadingType. 77
212 Figure 46 – SoftwareVersionType. 79
213 Figure 47 – PrepareForUpdate state machine . 81
214 Figure 48 – PrepareForUpdateStateMachineType . 82
215 Figure 49 – Installation state machine . 85
216 Figure 50 – InstallationStateMachine . 85
217 Figure 51 – PowerCycle state machine . 89
218 Figure 52 – Confirmation state machine . 91
219 Figure 53 – ConfirmationStateMachineType . 91
220 Figure 54 – Configurable component pattern . 94
221 Figure 55 – ConfigurableObjectType . 95
222 Figure 56 – Block-oriented Device structure example . 96
223 Figure 57 – Modular Device structure example . 97
224 Figure B.1 – Analyser Device use for FunctionalGroups . 114
225 Figure B.2 – PLCopen use for FunctionalGroups . 114
226 Figure B.3 – Example of an Identification FunctionalGroup . 115
227 Figure B.4 – Example . 116
228 Figure B.5 – Example sequence of Direct-Loading . 118
229 Figure B.6 – Example sequence of Cached-Loading . 119
230 Figure B.7 – Example sequence of File System based Loading . 121
231 Figure C.1 – Example of applying two companion specifications based on OPC UA for
232 Devices . 123
233 Figure C.2 – Using composition to compose one device representation defined by two
234 companion specifications . 124
235 Figure C.3 – Example of applying several companion specifications (I) . 126
236 Figure C.4 – Example of applying several companion specifications (II) . 127
237 Figure C.5 – Options how to manage the same Variable . 128
238 Figure C.6 – Example on how to use AddIns and Interface . 128
239 Figure C.7 – Example on how to use Interface with additional Object . 129
IEC CDV 62541-100 © IEC 2023 vii

241 TABLES
242 Table 1 – Examples of DataTypes . 4
243 Table 2 – Type Definition Table . 5
244 Table 3 – Examples of Other Characteristics . 5
245 Table 4 – Type Additional References . 6
246 Table 5 – Type Additional Subcomponents . 6
247 Table 6 – Type Attribute values for child Nodes . 6
248 Table 7 – Common Node Attributes . 7
249 Table 8 – Common Object Attributes . 8
250 Table 9 – Common Variable Attributes . 8
251 Table 10 – Common VariableType Attributes . 8
252 Table 11 – Common Method Attributes . 8
253 Table 12 – TopologyElementType definition . 10
254 Table 14 – FunctionalGroupType definition . 12
255 Table 15 – Recommended FunctionalGroup BrowseNames . 13
256 Table 16 – UIElementType definition . 13
257 Table 17 – IVendorNameplateType definition . 15
258 Table 18 – VendorNameplate Mapping to IRDIs . 16
259 Table 19 – ITagNameplateType definition . 17
260 Table 20 – TagNameplate Mapping to IRDIs . 17
261 Table 21 – IDeviceHealthType definition . 18
262 Table 22 – DeviceHealthEnumeration values . 18
263 Table 23 – DeviceHealthEnumeration definition . 18
264 Table 24 – IOperationCounterType definition . 19
265 Table 25 – IOperationCounterType Attribute values for child Nodes . 19
266 Table 26 – ISupportInfoType definition . 21
267 Table 28 – ComponentType definition . 23
268 Table 29 – DeviceType definition . 24
269 Table 30 – SoftwareType definition . 26
270 Table 31 – DeviceSet definition . 27
271 Table 32 – DeviceFeatures definition . 28
272 Table 33 – BlockType definition. 29
273 Table 34 – DeviceHealthDiagnosticAlarmType definition . 30
274 Table 35 – FailureAlarmType definition . 31
275 Table 36 – CheckFunctionAlarmType definition . 31
276 Table 37 – OffSpecAlarmType definition . 31
277 Table 38 – MaintenanceRequiredAlarmType definition . 31
278 Table 39 – ProtocolType definition . 34
279 Table 40 – NetworkType definition . 35
280 Table 41 – ConnectionPointType definition . 37
281 Table 42 – ConnectsTo ReferenceType . 38
282 Table 43 – ConnectsToParent ReferenceType . 38
283 Table 44 – NetworkSet definition . 39

viii IEC CDV 62541-100 © IEC 2023

284 Table 45 – DeviceTopology definition . 42
285 Table 46 – IsOnline ReferenceType . 44
286 Table 47 – TransferServicesType definition . 45
287 Table 48 – TransferToDevice Method arguments . 46
288 Table 49 – TransferToDevice Method AddressSpace definition . 46
289 Table 50 – TransferFromDevice Method arguments. 47
290 Table 51 – TransferFromDevice Method AddressSpace definition . 47
291 Table 52 – FetchTransferResultData Method arguments . 48
292 Table 53 – FetchTransferResultData Method AddressSpace definition . 48
293 Table 54 – FetchResultDataType structure . 48
294 Table 55 – TransferResultErrorDataType structure . 49
295 Table 56 – TransferResultErrorDataType Definition . 49
296 Table 57 – TransferResultDataDataType structure . 49
297 Table 58 – TransferResultDataDataType definition . 50
298 Table 59 – LockingServicesType definition . 52
299 Table 60 – LockingServicesType Additional Variable Attributes . 52
300 Table 61 – MaxInactiveLockTime Property definition . 53
301 Table 62 – InitLock Method Arguments . 54
302 Table 63 – InitLock Method AddressSpace definition . 54
303 Table 64 – ExitLock Method Arguments. 54
304 Table 65 – ExitLock Method AddressSpace definition . 55
305 Table 66 – RenewLock Method Arguments . 55
306 Table 67 – RenewLock Method AddressSpace definition . 55
307 Table 68 – BreakLock Method Arguments . 55
308 Table 69 – BreakLock Method AddressSpace definition . 56
309 Table 70 – SoftwareUpdateType definition . 70
310 Table 71 – SoftwareUpdateType Attribute values for child Nodes . 72
311 Table 72 – SoftwareLoadingType definition . 72
312 Table 73 – PackageLoadingType definition . 73
313 Table 74 – TemporaryFileTransferType Result Codes . 73
314 Table 75 – DirectLoadingType definition . 75
315 Table 76 – CachedLoadingType definition . 76
316 Table 77 – GetUpdateBehavior Method Arguments . 77
317 Table 78 – GetUpdateBehavior Method AddressSpace definition . 77
318 Table 79 – FileSystemLoadingType definition . 78
319 Table 80 – GetUpdateBehavior Method Arguments . 78
320 Table 81 – GetUpdateBehavior Method AddressSpace definition . 78
321 Table 82 – ValidateFiles Method Arguments . 79
322 Table 83 – ValidateFiles Method AddressSpace definition . 79
323 Table 84 – SoftwareVersionType definition . 80
324 Table 85 – PrepareForUpdateStateMachineType definition . 82
325 Table 86 – PrepareForUpdateStateMachineType Attribute values for child Nodes . 83
326 Table 87 – PrepareForUpdateStateMachineType Additional References . 83

IEC CDV 62541-100 © IEC 2023 ix

327 Table 88 – InstallationStateMachineType definition . 86
328 Table 89 – InstallationStateMachineType Attribute values for child Nodes . 86
329 Table 90 – InstallationStateMachineType Additional References . 86
330 Table 91 – InstallSoftwarePackage Method Arguments . 88
331 Table 92 – InstallSoftwarePackage Method AddressSpace definition . 88
332 Table 93 – InstallFiles Method Arguments . 88
333 Table 94 – InstallFiles Method AddressSpace definition . 89
334 Table 95 – PowerCycleStateMachineType definition . 90
335 Table 96 – PowerCycleStateMachineType Attribute values for child Nodes . 90
336 Table 97 – PowerCycleStateMachineType Additional References . 90
337 Table 98 – ConfirmationStateMachineType . 91
338 Table 99 – ConfirmationStateMachineType Attribute values for child Nodes . 92
339 Table 100 – ConfirmationStateMachineType TargetBrowsePath . 92
340 Table 101 – SoftwareVersionFileType Items . 92
341 Table 102 – SoftwareVersionFileType definition . 93
342 Table 103 – UpdateBehavior OptionSet . 93
343 Table 104 – UpdateBehavior OptionSet Definition . 93
344 Table 105 – ConfigurableObjectType definition .
...

Questions, Comments and Discussion

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

Loading comments...