SIST EN IEC 62541-17:2026

SLOVENSKI STANDARD
01-maj-2026
Enotna arhitektura OPC - 17. del: Nadomestna imena (IEC 62541-17:2025)
OPC unified architecture - Part 17: Alias names (IEC 62541-17:2025)
OPC Unified Architecture – Teil 17: Alias Namen (IEC 62541-17:2025)
Architecture unifiée OPC - Partie 17: Alias (IEC 62541-17:2025)
Ta slovenski standard je istoveten z: EN IEC 62541-17: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-17

NORME EUROPÉENNE
EUROPÄISCHE NORM February 2026
ICS 25.040
English Version
OPC unified architecture - Part 17: Alias Names
(IEC 62541-17:2025)
Architecture unifiée OPC - Partie 17: Alias OPC Unified Architecture - Teil 17: Alias Namen
(IEC 62541-17:2025) (IEC 62541-17:2025)
This European Standard was approved by CENELEC on 2026-01-16. 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-17:2026 E

European foreword
The text of document 65E/1042/CDV, future edition 1 of IEC 62541-17, 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
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
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.
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-17:2025 was approved by CENELEC as a European
Standard without any modification.
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-12 - OPC unified architecture - Part 12: EN IEC 62541-12 -
Discovery and global services
IEC 62541-14 - OPC unified architecture - Part 14: Pubsub EN IEC 62541-14 -

Under preparation. Stage at the time of publication: prEN IEC 62541-14:2024.
IEC 62541-17 ®
Edition 1.0 2025-12
INTERNATIONAL
STANDARD
OPC unified architecture -
Part 17: Alias Names
ICS 25.040  ISBN 978-2-8327-0857-6

IEC 62541-17:2025-12(en)
IEC 62541-17:2025 © IEC 2025
CONTENTS
FOREWORD . 3
1 Scope . 5
2 Normative references . 5
3 Terms, definitions and abbreviated terms . 5
3.1 Terms and definitions . 5
3.2 Abbreviated terms. 5
4 Use cases . 6
4.1 Complex configuration . 6
4.2 Automatic reconfiguration . 6
4.3 Cloud based system . 6
4.4 Aggregated systems . 6
5 AliasNames Information Model overview . 6
6 OPC UA ObjectTypes . 8
6.1 Overview . 8
6.2 AliasNameType ObjectType Definition . 8
6.3 AliasNameCategoryType ObjectType Definition . 8
6.3.1 Definition . 8
6.3.2 FindAlias Method . 9
7 OPC UA DataTypes . 11
7.1 Overview . 11
7.2 AliasNameDataType . 11
8 Reference Types . 11
8.1 Overview . 11
8.2 AliasFor ReferenceType . 11
9 Instances . 12
9.1 Overview . 12
9.2 Aliases . 12
9.3 TagVariables . 12
9.4 Topics . 13
Annex A (informative) Examples . 14
A.1 Overview . 14
A.2 AliasNames used within a single Server . 14
A.3 AliasNames in an aggregating Server . 15
A.4 Standalone AliasNames Server . 16
A.5 Aggregating Server with a collection of Aggregates . 17
A.6 GDS . 18
A.7 Client use of an AliasName Server . 18
Annex B (normative) GDS functionality . 20
B.1 Overview . 20
B.2 Register a Server. 21
B.3 Unregister a Server . 21
B.4 Disconnect between a Client and an AliasName Server . 22
Bibliography . 24

Figure 1 – AliasNames Overview. 7
IEC 62541-17:2025 © IEC 2025
Figure 2 – AliasNames Example. 7
Figure A.1 – AliasNames in a Server example . 14
Figure A.2 – Aggregating AliasNames Server example . 15
Figure A.3 – AliasNames Server example . 16
Figure A.4 – Aggregating Server example 2 . 17
Figure A.5 – GDS with merged AliasNames example. 18
Figure B.1 – Example GDS aggregating AliasNames . 20
Figure B.2 – Server Registration Process . 21
Figure B.3 – Unregister Server Process . 22
Figure B.4 – Example Client Process for Server subscription with errors . 23

Table 1 – AliasNameType Definition . 8
Table 2 – AliasNameCategoryType Definition . 9
Table 3 – FindAlias Method Arguments . 10
Table 4 – FindAlias Method Error Codes . 10
Table 5 – FindAlias Method AddressSpace definition . 10
Table 6 – AliasNameDataType DataType structure . 11
Table 7 – AliasNameDataType Definition . 11
Table 8 – AliasFor Definition . 12
Table 9 – Aliases definition. 12
Table 10 – TagVariables definition . 13
Table 11 – Topics definition . 13

IEC 62541-17:2025 © IEC 2025
INTERNATIONAL ELECTROTECHNICAL COMMISSION
____________
OPC unified architecture -
Part 17: Alias Names
FOREWORD
1) The International Electrotechnical Commission (IEC) is a worldwide organization for standardization comprising
all national electrotechnical committees (IEC National Committees). The object of IEC is to promote international
co-operation on all questions concerning standardization in the electrical and electronic fields. To this end and
in addition to other activities, IEC publishes International Standards, Technical Specifications, Technical Reports,
Publicly Available Specifications (PAS) and Guides (hereafter referred to as “IEC Publication(s)”). Their
preparation is entrusted to technical committees; any IEC National Committee interested in the subject dealt with
may participate in this preparatory work. International, governmental and non-governmental organizations liaising
with the IEC also participate in this preparation. IEC collaborates closely with the International Organization for
Standardization (ISO) in accordance with conditions determined by agreement between the two organizations.
2) The formal decisions or agreements of IEC on technical matters express, as nearly as possible, an international
consensus of opinion on the relevant subjects since each technical committee has representation from all
interested IEC National Committees.
3) IEC Publications have the form of recommendations for international use and are accepted by IEC National
Committees in that sense. While all reasonable efforts are made to ensure that the technical content of IEC
Publications is accurate, IEC cannot be held responsible for the way in which they are used or for any
misinterpretation by any end user.
4) In order to promote international uniformity, IEC National Committees undertake to apply IEC Publications
transparently to the maximum extent possible in their national and regional publications. Any divergence between
any IEC Publication and the corresponding national or regional publication shall be clearly indicated in the latter.
5) IEC itself does not provide any attestation of conformity. Independent certification bodies provide conformity
assessment services and, in some areas, access to IEC marks of conformity. IEC is not responsible for any
services carried out by independent certification bodies.
6) All users should ensure that they have the latest edition of this publication.
7) No liability shall attach to IEC or its directors, employees, servants or agents including individual experts and
members of its technical committees and IEC National Committees for any personal injury, property damage or
other damage of any nature whatsoever, whether direct or indirect, or for costs (including legal fees) and
expenses arising out of the publication, use of, or reliance upon, this IEC Publication or any other IEC
Publications.
8) Attention is drawn to the Normative references cited in this publication. Use of the referenced publications is
indispensable for the correct application of this publication.
9) IEC draws attention to the possibility that the implementation of this document may involve the use of (a)
patent(s). IEC takes no position concerning the evidence, validity or applicability of any claimed patent rights in
respect thereof. As of the date of publication of this document, IEC had not received notice of (a) patent(s), which
may be required to implement this document. However, implementers are cautioned that this may not represent
the latest information, which may be obtained from the patent database available at https://patents.iec.ch. IEC
shall not be held responsible for identifying any or all such patent rights.
IEC 62541-17 has been prepared by subcommittee 65E: Devices and integration in enterprise
systems, of IEC technical committee 65: Industrial-process measurement, control and
automation. It is an International Standard.
The text of this International Standard is based on the following documents:
Draft Report on voting
65E/1042/CDV 65E/1100/RVC
Full information on the voting for its approval can be found in the report on voting indicated in
the above table.
The language used for the development of this International Standard is English.
IEC 62541-17:2025 © IEC 2025
This document was drafted in accordance with ISO/IEC Directives, Part 2, and developed in
accordance with ISO/IEC Directives, Part 1 and ISO/IEC Directives, IEC Supplement, available
at www.iec.ch/members_experts/refdocs. The main document types developed by IEC are
described in greater detail at www.iec.ch/publications.
Throughout this document and the other Parts of the series, certain document conventions are
used:
Italics are used to denote a defined term or definition that appears in the “Terms and definitions”
clause in one of the parts of the series.
Italics are also used to denote the name of a service input or output parameter or the name of
a structure or element of a structure that are usually defined in tables.
The italicized terms and names are also often written in camel-case (the practice of writing
compound words or phrases in which the elements are joined without spaces, with each
element's initial letter capitalized within the compound). For example, the defined term is
AddressSpace instead of Address Space. This makes it easier to understand that there is a
single definition for AddressSpace, not separate definitions for Address and Space.
A list of all parts in the IEC 62541 series, published under the general title OPC Unified
Architecture, can be found on the IEC website.
The committee has decided that the contents of this document will remain unchanged until the
stability date indicated on the IEC website under webstore.iec.ch in the data related to the
specific document. At this date, the document will be
– reconfirmed,
– withdrawn, or
– revised.
IEC 62541-17:2025 © IEC 2025
1 Scope
This part of IEC 62541 provides a definition of AliasNames functionality. AliasNames provide a
manner of configuring and exposing an alternate well-defined name for any Node in the system.
This is analogous to the way domain names are used as an alias to IP addresses in IP networks.
Like a DNS Server, an OPC UA Server that supports AliasNames provides a lookup Method
that will translate an AliasName to a NodeId of the related Node on a Server. An aggregating
Server can collect these AliasNames from multiple Servers and provide a lookup Method to
allow Client applications to discover NodeIds on a system wide basis. An aggregating Server
could also define AliasNames for Nodes in other Servers that do not support AliasNames. A
GDS can be constructed that would automatically aggregate all AliasNames that are defined on
any Server that has registered with the GDS. In this case, the GDS also provides the lookup
mechanism for Clients at a well-known endpoint and address.
2 Normative references
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.
IEC 62541-1, OPC Unified Architecture - Part 1: Overview and Concepts
IEC 62541-3, OPC Unified Architecture - Part 3: Address Space Model
IEC 62541-4, OPC Unified Architecture - Part 4: Services
IEC 62541-5, OPC Unified Architecture - Part 5: Information Model
IEC 62541-12, OPC Unified Architecture - Part 12: Discovery and Global Services
IEC 62541-14, OPC Unified Architecture - Part 14: PubSub
3 Terms, definitions and abbreviated terms
3.1 Terms and definitions
For the purposes of this document, the terms and definitions given in IEC 62541-1,
IEC 62541-3, IEC 62541-4, IEC 62541-5, IEC 62541-12, and IEC 62541-14 and the following
apply.
ISO and IEC maintain terminology databases for use in standardization at the following
addresses:
– IEC Electropedia: available at https://www.electropedia.org/
– ISO Online browsing platform: available at https://www.iso.org/obp
3.1.1
AliasName
alternate well-defined name for any Node in the system
3.2 Abbreviated terms
GDS Global Discovery Server
IEC 62541-17:2025 © IEC 2025
4 Use cases
4.1 Complex configuration
For systems that are large and complex, engineering is often done in multiple tools and by
multiple individuals. The separate configurations are required to work together, but resolving
the references between these different configurations can be a significant task. A common
solution to simplify this task is a naming convention for the items that are being referenced.
Providing an automatic lookup capability for these names would greatly simplify configuration.
Each system can specify its own names and configurations can be built to just use the names,
without having to know the exact address of the items. The exact address would include the
address of the Server, the address of the tag in the Server, the required protocol for connecting
to the Server, security settings etc. OPC UA defines a GDS that can provide information about
what Servers are available in a system and how to connect to them, but it does not currently
provide information about the tags that are available in a given Server.
4.2 Automatic reconfiguration
In a system where many smaller Servers exist and these Servers could be dynamic, in that new
Servers can appear and disappear. Configuration could move between Servers. The automatic
resolution of where a specific piece of information is located would greatly simplify these
systems.
4.3 Cloud based system
Much like the previous use case, a cloud-based system, where Servers can be spun up in a
new cloud system or adjusted and split based on loading to multiple Servers. The automatic
resolution of where a specific piece of information is located would greatly simplify these
systems.
4.4 Aggregated systems
In systems where many simple devices exist, any given simple device could not have the ability
to provide name resolution, yet these systems can be much like systems in one of the previous
use cases. In a system such as this an aggregating Server could exist, where the aggregating
Server would provide the names as well as the lookup for the underlying Server. This
aggregating Server could also provide other functionality such as aggregation of values, but it
can also only provide the name def
...