SIST EN IEC 62541-100:2026

OPC unified architecture - Part 100: Devices (IEC 62541-100:2025)

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 (IEC 62541-100:2025)

Architecture unifiée OPC - Partie 100: Appareils (IEC 62541-100:2025)

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: Naprave (IEC 62541-100:2025)

IEC 62541-100:2025 določa informacijski model, povezan z napravami. Ta dokument opisuje tri modele, ki temeljijo drug na drugem, kot sledi:
- (Osnovni) model naprave je namenjen zagotavljanju enotnega pogleda na naprave ter njihove strojne in programske dele ne glede na osnovne protokole naprav.
- Model komunikacije naprave dodaja elemente informacij o omrežju in povezavah, da je mogoče ustvariti komunikacijske topologije.
- Model gostitelja za integracijo naprav končno dodaja dodatne elemente in pravila, potrebna za gostiteljske sisteme za upravljanje integracije celotnega sistema. Omogoča odsev topologije avtomatizacijskega sistema z napravami ter povezanimi komunikacijskimi omrežji.
Ta dokument prav tako določa AddIn-e (dodatke), ki se lahko uporabljajo za modele v tem dokumentu, pa tudi za modele v drugih informacijskih modelih. Ti so:
- Model zaklepanja – generični AddIn za nadzor sočasnega dostopa,
- Model posodobitve programske opreme – AddIn za upravljanje programske opreme v napravi.
To drugo izdajo preklicuje in nadomešča prva izdaja, objavljena leta 2015. Ta izdaja predstavlja tehnično revizijo.
Ta izdaja vključuje naslednje pomembne tehnične spremembe glede na prejšnjo izdajo:
a) Določen je bil ComponentType (tip komponente), ki ga je mogoče uporabiti za modeliranje katerega koli HW (strojne opreme) ali SW (programske opreme) elementa naprave, in dodan je bil SoftwareType (tip programske opreme) kot podtip ComponentType;
b) Dodan je bil nov koncept vmesnika OPC UA in definirani vmesniki za Nameplate (tablica z imenom), DeviceHealth (zdravje naprave) in SupportInfo (informacije o podpori);
c) Dodan je bil nov model za posodobitev programske opreme (posodobitev vdelane programske opreme);
d) Določena je bila nova vstopna točka za dokumente, kjer je vsak dokument predstavljen z instanco FileType (tip datoteke);
e) Dodan je bil model, ki zagotavlja informacije o življenjski dobi, povezanih omejitvah in semantiki življenjske dobe stvari, kot so orodja, materiali ali stroji.

General Information

• Status: Published
• Public Enquiry End Date: 30-Mar-2024
• Publication Date: 12-Apr-2026
• ICS: 25.040.40 - Industrial process measurement and control
• ICS: 35.100.05 - Multilayer applications
• ICS: 35.240.50 - IT applications in industry
• Technical Committee: MOV - Measuring equipment for electromagnetic quantities
• Current Stage: 6060 - National Implementation/Publication (Adopted Project)
• Start Date: 24-Feb-2026
• Due Date: 01-May-2026
• Completion Date: 13-Apr-2026
• Mandate: M/490 - Standardisation mandate to the European Standardisation Organisations (ESOs) to support European Smart Grid deployment
• Ref Project: EN IEC 62541-100:2026 - OPC unified architecture - Part 100: Devices

Relations

• Refers: SIST EN IEC 62541-8:2020 - OPC Unified Architecture - Part 8: Data Access (IEC 62541-8:2020)
• Effective Date: 10-Feb-2026
• Refers: SIST EN IEC 62541-3:2020 - OPC unified architecture - Part 3: Address Space Model (IEC 62541-3:2020)
• Effective Date: 10-Feb-2026
• Refers: SIST EN IEC 62541-6:2020 - OPC Unified Architecture - Part 6: Mappings (IEC 62541-6:2020)
• Effective Date: 10-Feb-2026
• Refers: SIST EN IEC 62541-5:2020 - OPC Unified Architecture - Part 5: Information Model
• Effective Date: 10-Feb-2026
• Refers: SIST EN IEC 62541-9:2020 - OPC Unified Architecture - Part 9: Alarms and conditions (IEC 62541-9:2020)
• Effective Date: 03-Feb-2026
• Refers: SIST EN IEC 62541-7:2026 - OPC Unified Architecture - Part 7: Profiles (IEC 62541-7:2025)
• Effective Date: 03-Feb-2026
• Refers: SIST EN IEC 62541-6:2026 - OPC unified architecture - Part 6: Mappings (IEC 62541-6:2025)
• Effective Date: 03-Feb-2026
• Refers: SIST EN IEC 62541-4:2020 - OPC Unified Architecture - Part 4: Services (IEC 62541-4:2020)
• Effective Date: 03-Feb-2026
• Refers: SIST EN IEC 62541-7:2020 - OPC unified architecture - Part 7: Profiles (IEC 62541-7:2020)
• Effective Date: 03-Feb-2026
• Refers: SIST EN IEC 62541-1:2026 - OPC unified architecture - Part 1: Overview and concepts (IEC 62541-1:2025)
• Effective Date: 03-Feb-2026
• Refers: SIST EN IEC 62541-8:2026 - OPC unified architecture - Part 8: Data access (IEC 62541-8:2025)
• Effective Date: 03-Feb-2026
• Refers: SIST EN IEC 62541-3:2026 - OPC unified architecture - Part 3: Address space model (IEC 62541-3:2025)
• Effective Date: 03-Feb-2026
• Refers: SIST EN IEC 62541-4:2026 - OPC unified architecture - Part 4: Services (IEC 62541-4:2025)
• Effective Date: 03-Feb-2026
• Refers: SIST EN IEC 62541-5:2026 - OPC unified architecture - Part 5: Information model (IEC 62541-5:2026)
• Effective Date: 03-Feb-2026
• Referred By: SIST EN IEC 62769-101-2:2023 - Field Device Integration (FDI)® - Part 101-2: Profiles - Foundation Fieldbus HSE (IEC 62769-101-2:2023)
• Effective Date: 10-Feb-2026

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.

Standards Content (Sample)

SLOVENSKI STANDARD
01-maj-2026
Enotna arhitektura OPC - 100. del: Naprave (IEC 62541-100:2025)
OPC unified architecture - Part 100: Devices (IEC 62541-100:2025)
OPC Unified Architecture - Teil 100: Geräteschnittstelle (IEC 62541-100:2025)
Architecture unifiée OPC - Partie 100: Appareils (IEC 62541-100:2025)
Ta slovenski standard je istoveten z: EN IEC 62541-100:2026
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.

EUROPEAN STANDARD EN IEC 62541-100

NORME EUROPÉENNE
EUROPÄISCHE NORM February 2026
ICS 25.040.40; 35.100.05 Supersedes EN 62541-100:2015
English Version
OPC unified architecture - Part 100: Devices
(IEC 62541-100:2025)
Architecture unifiée OPC - Partie 100: Appareils OPC Unified Architecture - Teil 100: Geräteschnittstelle
(IEC 62541-100:2025) (IEC 62541-100:2025)
This European Standard was approved by CENELEC on 2026-01-21. CENELEC members are bound to comply with the CEN/CENELEC
Internal Regulations which stipulate the conditions for giving this European Standard the status of a national standard without any alteration.
Up-to-date lists and bibliographical references concerning such national standards may be obtained on application to the CEN-CENELEC
Management Centre or to any CENELEC member.
This European Standard exists in three official versions (English, French, German). A version in any other language made by translation
under the responsibility of a CENELEC member into its own language and notified to the CEN-CENELEC Management Centre has the
same status as the official versions.
CENELEC members are the national electrotechnical committees of Austria, Belgium, Bulgaria, Croatia, Cyprus, the Czech Republic,
Denmark, Estonia, Finland, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, the
Netherlands, Norway, Poland, Portugal, Republic of North Macedonia, Romania, Serbia, Slovakia, Slovenia, Spain, Sweden, Switzerland,
Türkiye 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
© 2026 CENELEC All rights of exploitation in any form and by any means reserved worldwide for CENELEC Members.
Ref. No. EN IEC 62541-100:2026 E

European foreword
The text of document 65E/1050/CDV, future edition 2 of IEC 62541-100, prepared by SC 65E
"Devices and integration in enterprise systems" of IEC/TC 65 "Industrial-process measurement,
control and automation" was submitted to the IEC-CENELEC parallel vote and approved by
CENELEC as EN IEC 62541-100:2026.
The following dates are fixed:
• latest date by which the document has to be implemented at national (dop) 2027-02-28
level by publication of an identical national standard or by endorsement
• latest date by which the national standards conflicting with the (dow) 2029-02-28
document have to be withdrawn
This document supersedes EN 62541-100:2015 and all of its amendments and corrigenda (if any).
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.
This document has been prepared under a standardization request addressed to CENELEC by the
European Commission. The Standing Committee of the EFTA States subsequently approves these
requests for its Member States.
Any feedback and questions on this document should be directed to the users’ national committee. A
complete listing of these bodies can be found on the CENELEC website.
Endorsement notice
The text of the International Standard IEC 62541-100:2025 was approved by CENELEC as a
European Standard without any modification.
In the official version, for Bibliography, the following notes have to be added for the standard indicated:
IEC 61131-3 NOTE Approved as EN IEC 61131-3
IEC 61499-1:2012 NOTE Approved as EN 61499-1:2013 (not modified)
IEC 62541-19 NOTE Approved as EN IEC 62541-19 to be published
IEC 62591 NOTE Approved as EN 62591
IEC 62769 (series) NOTE Approved as EN IEC 62769 (series)
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  Where 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.cencenelec.eu.
Publication Year Title EN/HD Year
IEC 62541-1 - OPC Unified Architecture - Part 1: EN IEC 62541-1 -
Overview and concepts
IEC 62541-3 - OPC Unified Architecture - Part 3: Address EN IEC 62541-3 -
Space Model
IEC 62541-4 - OPC unified architecture - Part 4: Services EN IEC 62541-4 -
IEC 62541-5 - OPC Unified architecture - Part 5: EN IEC 62541-5 -
Information Model
IEC 62541-6 - OPC unified architecture - Part 6: EN IEC 62541-6 -
Mappings
IEC 62541-7 - OPC Unified Architecture - Part 7: Profiles EN IEC 62541-7 -
IEC 62541-8 - OPC unified architecture - Part 8: Data EN IEC 62541-8 -
access
IEC 62541-9 - OPC Unified Architecture - Part 9: Alarms EN IEC 62541-9 -
and Conditions
NAMUR - Self-monitoring and diagnosis of field - -
Recommendation devices
NE107
Under preparation. Stage at the time of publication: prEN IEC 62541-9:2024.
IEC 62541-100 ®
Edition 2.0 2025-12
INTERNATIONAL
STANDARD
OPC unified architecture -
Part 100: Devices
ICS 25.040.40; 35.100.05 ISBN 978-2-8327-0850-7

IEC 62541-100:2025-12(en)
IEC 62541-100:2025 © IEC 2025
CONTENTS
FOREWORD. 10
1 Scope . 12
2 Normative references . 12
3 Terms, definitions, abbreviated terms and conventions . 13
3.1 Terms and definitions . 13
3.2 Abbreviated terms . 15
3.3 Conventions used in this document. 15
3.3.1 Conventions for Node descriptions . 15
3.3.2 NodeIds and BrowseNames . 19
3.3.3 Common Attributes . 20
4 Device model. 22
4.1 General . 22
4.2 Usage guidelines . 23
4.3 TopologyElementType . 23
4.4 FunctionalGroupType . 25
4.4.1 Model . 25
4.4.2 Recommended FunctionalGroup BrowseNames . 27
4.4.3 UIElement Type . 27
4.5 Interfaces . 28
4.5.1 Overview . 28
4.5.2 VendorNameplate Interface . 28
4.5.3 TagNameplate Interface . 31
4.5.4 DeviceHealth Interface . 32
4.5.5 OperationCounter Interface . 33
4.5.6 SupportInfo Interface . 35
4.6 ComponentType . 37
4.7 DeviceType . 38
4.8 SoftwareType . 41
4.9 DeviceSet entry point . 42
4.10 DeviceFeatures entry point . 43
4.11 BlockType . 43
4.12 DeviceHealth Alarm Types . 45
4.12.1 General . 45
4.12.2 DeviceHealthDiagnosticAlarmType . 45
4.12.3 FailureAlarmType . 46
4.12.4 CheckFunctionAlarmType . 46
4.12.5 OffSpecAlarmType . 46
4.12.6 MaintenanceRequiredAlarmType . 47
5 Device communication model . 47
5.1 General . 47
5.2 ProtocolType . 49
5.3 Network . 49
5.4 ConnectionPoint . 51
5.5 ConnectsTo and ConnectsToParent ReferenceTypes . 53
5.6 NetworkSet Object . 54
6 Device integration host model . 55
IEC 62541-100:2025 © IEC 2025
6.1 General . 55
6.2 DeviceTopology Object . 56
6.3 Online/Offline . 57
6.3.1 General . 57
6.3.2 IsOnline ReferenceType . 58
6.4 Offline-Online data transfer . 59
6.4.1 Definition . 59
6.4.2 TransferServices Type . 60
6.4.3 TransferServices Object . 60
6.4.4 TransferToDevice Method . 61
6.4.5 TransferFromDevice Method . 62
6.4.6 FetchTransferResultData Method . 63
7 Locking model . 66
7.1 Overview . 66
7.2 LockingServices Type . 66
7.3 LockingServices Object . 68
7.4 MaxInactiveLockTime Property . 69
7.5 InitLock Method . 69
7.6 ExitLock Method . 70
7.7 RenewLock Method . 70
7.8 BreakLock Method . 71
8 Software update model . 72
8.1 Overview . 72
8.2 Use Cases . 72
8.2.1 General . 72
8.2.2 Supported Use Cases . 72
8.2.3 Unsupported Use Cases . 74
8.3 General . 75
8.3.1 System perspective . 75
8.3.2 Types of software. 75
8.3.3 Types of Devices . 75
8.3.4 Options for the Server . 76
8.3.5 Software Update Client . 78
8.3.6 Safety considerations . 84
8.3.7 Security considerations . 84
8.3.8 Update Behavior . 85
8.3.9 Installation of patches . 85
8.3.10 Incompatible parameters / settings . 85
8.3.11 AddIn model . 85
8.4 ObjectTypes . 86
8.4.1 SoftwareUpdateType . 86
8.4.2 SoftwareLoadingType . 89
8.4.3 PackageLoadingType . 90
8.4.4 DirectLoadingType . 92
8.4.5 CachedLoadingType . 93
8.4.6 FileSystemLoadingType . 95
8.4.7 SoftwareVersionType . 97
8.4.8 PrepareForUpdateStateMachineType . 99
8.4.9 InstallationStateMachineType . 103
IEC 62541-100:2025 © IEC 2025
8.4.10 PowerCycleStateMachineType . 107
8.4.11 ConfirmationStateMachineType . 109
8.5 DataTypes . 111
8.5.1 SoftwareVersionFileType . 111
8.5.2 UpdateBehavior OptionSet . 112
9 Specialized topology elements . 113
9.1 General . 113
9.2 Configurable components . 113
9.2.1 General pattern . 113
9.2.2 ConfigurableObjectType . 114
9.3 Block Devices . 115
9.4 Modular Devices . 116
10 Lifetime model . 117
10.1 General . 117
10.2 LifetimeVariableType definition . 117
10.2.1 Overview . 117
10.2.2 VariableType definition . 118
10.3 BaseLifetimeIndicationType definition . 119
10.3.1 Overview . 119
10.3.2 ObjectType definition . 119
10.4 TimeIndicationType definition . 119
10.4.1 Overview . 119
10.4.2 ObjectType definition . 120
10.5 NumberOfPartsIndicationType definition . 120
10.5.1 Overview . 120
10.5.2 ObjectType definition . 120
10.6 NumberOfUsagesIndicationType definition . 120
10.6.1 Overview . 120
10.6.2 ObjectType definition . 121
10.7 LengthIndicationType definition . 121
10.7.1 Overview . 121
10.7.2 ObjectType definition . 121
10.8 DiameterIndicationType definition . 121
10.8.1 Overview . 121
10.8.2 ObjectType definition . 122
10.9 SubstanceVolumeIndicationType definition . 122
10.9.1 Overview . 122
10.9.2 ObjectType definition . 122
11 Profiles and ConformanceUnits . 122
11.1 Conformance Units . 122
11.2 Profiles . 126
11.2.1 General . 126
11.2.2 Profile list . 127
11.2.3 Device Server Facets . 127
11.2.4 Device Client Facets . 131
12 Namespaces . 133
12.1 Namespace Metadata . 133
12.2 Handling of OPC UA namespaces . 134
IEC 62541-100:2025 © IEC 2025
Annex A (normative) Namespace and mappings . 136
Annex B (informative) Examples . 137
B.1 General . 137
B.2 Functional Group usages . 137
B.3 Identification Functional Group . 138
B.4 Software Update examples . 139
B.4.1 Factory Automation example . 139
B.4.2 Update sequence using Direct-Loading . 140
B.4.3 Update sequence using Cached-Loading . 141
B.4.4 Update sequence using File System based Loading . 142
Annex C (informative) Guidelines for the usage of OPC UA for Devices as base for
companion specifications . 144
C.1 Overview . 144
C.2 Guidelines to define companion specifications based on OPC UA for
Devices . 146
C.3 Guidelines on how to combine different companion specifications based on
OPC UA for Devices in one OPC UA application . 147
C.4 Guidelines to manage the same Variables defined in different places . 149
C.5 Guidelines on how to use functionality in companion specifications . 150
Bibliography . 152

Figure 1 – Device model overview . 22
Figure 2 – Components of the TopologyElementType . 23
Figure 3 – FunctionalGroupType . 26
Figure 4 – Overview of Interfaces for Devices and Device components . 28
Figure 5 – VendorNameplate Interface . 29
Figure 6 – TagNameplate Interface . 31
Figure 7 – DeviceHealth Interface . 32
Figure 8 – Support information Interface . 35
Figure 9 – ComponentType . 37
Figure 10 – DeviceType . 39
Figure 11 – SoftwareType . 41
Figure 12 – Standard entry point for Devices . 42
Figure 13 – Standard entry point for DeviceFeatures . 43
Figure 14 – BlockType hierarchy . 44
Figure 15 – Device Health Alarm type hierarchy . 45
Figure 16 – Device communication model overview . 48
Figure 17 – Example of a communication topology . 48
Figure 18 – Example of a ProtocolType hierarchy with instances that represent specific
communication profiles . 49
Figure 19 – NetworkType . 50
Figure 20 – Example of ConnectionPointType hierarchy . 51
Figure 21 – ConnectionPointType . 51
Figure 22 – ConnectionPoint usage . 52
Figure 23 – Type Hierarchy for ConnectsTo and ConnectsToParent References . 53
Figure 24 – Example with ConnectsTo and ConnectsToParent References . 54
IEC 62541-100:2025 © IEC 2025
Figure 25 – Example of an automation system . 55
Figure 26 – Example of a Device topology . 56
Figure 27 – Online component for access to Device data . 57
Figure 28 – Type hierarchy for IsOnline Reference . 59
Figure 29 – TransferServicesType . 60
Figure 30 – TransferServices . 61
Figure 31 – LockingServicesType . 67
Figure 32 – LockingServices . 68
Figure 33 – Example with a device and several software components . 75
Figure 34 – Determine the type of update that the Server implements . 79
Figure 35 – Different flows of Direct-Loading, Cached-Loading and FileSystem based
Loading . 80
Figure 36 – Prepare and Resume activities . 81
Figure 37 – Installation activity for Direct-Loading. 82
Figure 38 – Installation activity for Cached-Loading and File System based Loading . 83
Figure 39 – Resume activity . 84
Figure 40 – Example how to add the SoftwareUpdate AddIn to a component . 86
Figure 41 – SoftwareUpdateType . 87
Figure 42 – PackageLoadingType . 90
Figure 43 – DirectLoadingType . 92
Figure 44 – CachedLoadingType . 93
Figure 45 – FileSystemLoadingType . 95
Figure 46 – SoftwareVersionType . 97
Figure 47 – PrepareForUpdate state machine . 99
Figure 48 – PrepareForUpdateStateMachineType . 100
Figure 49 – Installation state machine . 103
Figure 50 – InstallationStateMachine . 103
Figure 51 – PowerCycle state machine . 108
Figure 52 – Confirmation state machine . 109
Figure 53 – ConfirmationStateMachineType . 110
Figure 54 – Configurable component pattern . 114
Figure 55 – ConfigurableObjectType . 114
Figure 56 – Block-oriented Device structure example . 115
Figure 57 – Modular Device structure example . 116
Figure B.1 – Analyser Device use for FunctionalGroups . 137
Figure B.2 – PLCopen use for FunctionalGroups . 138
Figure B.3 – Example of an Identification FunctionalGroup . 139
Figure B.4 – Example . 139
Figure B.5 – Example sequence of Direct-Loading . 141
Figure B.6 – Example sequence of Cached-Loading . 142
Figure B.7 – Example sequence of File System based Loading . 143
Figure C.1 – Example of applying two companion specifications based on OPC UA for
Devices . 145
IEC 62541-100:2025 © IEC 2025
Figure C.2 – Using composition to compose one device representation defined by two
companion specifications . 146
Figure C.3 – Example of applying several companion specifications (I) . 148
Figure C.4 – Example of applying several companion specifications (II) . 149
Figure C.5 – Options how to manage the same Variable . 150
Figure C.6 – Example on how to use AddIns and Interface. 151
Figure C.7 – Example on how to use Interface with additional Object . 151

Table 1 – Examples of DataTypes . 16
Table 2 – Type Definition table . 17
Table 3 – Examples of other characteristics. 17
Table 4 – Type Additional References . 18
Table 5 – Type Additional Subcomponents . 18
Table 6 – Type Attribute values for child Nodes . 19
Table 7 – Common Node Attributes . 20
Table 8 – Common Object Attributes . 20
Table 9 – Common Variable Attributes . 21
Table 10 – Common VariableType Attributes . 21
Table 11 – Common Method Attributes . 21
Table 12 – TopologyElementType definition . 24
Table 13 – TopologyElementType Additional Subcomponents . 25
Table 14 – FunctionalGroupType definition . 26
Table 15 – Recommended FunctionalGroup BrowseNames . 27
Table 16 – UIElementType definition . 28
Table 17 – IVendorNameplateType definition . 29
Table 18 – VendorNameplate Mapping to IRDIs . 31
Table 19 – ITagNameplateType definition . 31
Table 20 – TagNameplate Mapping to IRDIs . 32
Table 21 – IDeviceHealthType definition . 32
Table 22 – DeviceHealthEnumeration values . 33
Table 23 – DeviceHealthEnumeration definition . 33
Table 24 – IOperationCounterType definition . 34
Table 25 – IOperationCounterType Attribute values for child Nodes . 35
Table 26 – ISupportInfoType definition . 36
Table 27 – ISupportInfoType Additional Subcomponents . 36
Table 28 – ComponentType definition . 38
Table 29 – DeviceType definition . 40
Table 30 – SoftwareType definition . 41
Table 31 – DeviceSet definition . 43
Table 32 – DeviceFeatures definition . 43
Table 33 – BlockType definition . 44
Table 34 – DeviceHealthDiagnosticAlarmType definition . 45
Table 35 – FailureAlarmType definition . 46
IEC 62541-100:2025 © IEC 2025
Table 36 – CheckFunctionAlarmType definition . 46
Table 37 – OffSpecAlarmType definition . 47
Table 38 – MaintenanceRequiredAlarmType definition . 47
Table 39 – ProtocolType definition . 49
Table 40 – NetworkType definition . 50
Table 41 – ConnectionPointType definition . 52
Table 42 – ConnectsTo ReferenceType . 53
Table 43 – ConnectsToParent ReferenceType . 54
Table 44 – NetworkSet definition . 54
Table 45 – DeviceTopology definition . 57
Table 46 – IsOnline ReferenceType . 59
Table 47 – TransferServicesType definition . 60
Table 48 – TransferToDevice Method arguments . 62
Table 49 – TransferToDevice Method AddressSpace definition . 62
Table 50 – TransferFromDevice Method arguments . 62
Table 51 – TransferFromDevice Method AddressSpace definition . 63
Table 52 – FetchTransferResultData Method arguments . 64
Table 53 – FetchTransferResultData Method AddressSpace definition . 64
Table 54 – FetchResultDataType structure . 64
Table 55 – TransferResultErrorDataType structure . 65
Table 56 – TransferResultErrorDataType Definition . 65
Table 57 – TransferResultDataDataType structure . 65
Table 58 – TransferResultDataDataType definition . 66
Table 59 – LockingServicesType definition . 67
Table 60 – LockingServicesType Attribute Values for child Nodes . 67
Table 61 – MaxInactiveLockTime Property definition . 69
Table 62 – InitLock Method Arguments . 69
Table 63 – InitLock Method AddressSpace definition . 70
Table 64 – ExitLock Method Arguments . 70
Table 65 – ExitLock Method AddressSpace definition . 70
Table 66 – RenewLock Method Arguments . 71
Table 67 – RenewLock Method AddressSpace definition . 71
Table 68 – BreakLock Method Arguments . 71
Table 69 – BreakLock Method AddressSpace definition . 71
Table 70 – SoftwareUpdateType definition . 87
Table 71 – SoftwareUpdateType Attribute values for child Nodes . 89
Table 72 – SoftwareLoadingType definition . 89
Table 73 – PackageLoadingType definition . 90
Table 74 – TemporaryFileTransferType Result Codes . 91
Table 75 – DirectLoadingType definition . 92
Table 76 – CachedLoadingType definition . 93
Table 77 – GetUpdateBehavior Method Arguments . 94
Table 78 – GetUpdateBehavior Method AddressSpace definition . 95
IEC 62541-100:2025 © IEC 2025
Table 79 – FileSystemLoadingType definition .
...