SC 65E - Devices and integration in enterprise systems

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-13:2025 is available as IEC 62541-13:2025 RLV which contains the International Standard and its Redline version, showing all changes of the technical content compared to the previous edition.IEC 62541-13:2025 defines the information model associated with Aggregates. Programmatically produced aggregate examples are listed in Annex A. This third edition cancels and replaces the second edition published in 2020. This edition constitutes a technical revision.
This edition includes the following technical changes with respect to the previous edition:
a) Multiple fixes for the computation of aggregates
• The Raw status bit is always set for non-bad StatusCodes for the Start and End aggregates.
• Entries in the Interpolative examples Tables A2.2 Historian1, Historian2, and Historian3 have been changed from Good to Good, Raw status codes when the timestamp matches with the timestamp of the data source.
• Missing tables have been added for DurationInStateZero and DurationInStateNonZero.
• The value of zero has been removed for results with a StatusCode of bad.
• Data Type was listed as "Status Code" when it is "Double" for both Standard Deviation and both Variance Aggregates.
• Rounding Error in TimeAverage and TimeAverage2 have been corrected.
• The status codes have been corrected for the last two intervals and the value has been corrected in the last interval.
• The wording has been changed to be more consistent with the certification testing tool.
• UsedSlopedExtrapolation set to true for Historian2 and all examples locations needed new values or status' are modified.
• Values affected by percent good and percent bad have been updated.
• PercentGood/PercentBad are now accounted for in the calculation.
• TimeAverage uses SlopedInterpolation but the Time aggregate is incorrectly allowed to used Stepped Interpolation.
• Partial bit is now correctly calculated.
• Unclear sentence was removed.
• Examples have been moved to a CSV.
• The value and status code for Historian 3 have been updated.
• TimeAverage2 Historian1 now takes uncertain regions into account when calculating StatusCodes.
• TimeAverage2 Historian2 now takes uncertain regions into account when calculating StatusCodes.
• Total2 Historian1 now takes uncertain regions into account when calculating StatusCodes
• Total2 Historian2 now takes uncertain regions into account when calculating StatusCodes
• Maximum2 Historian1 now takes uncertain regions into account when calculating StatusCodes
• MaximumActualTime2 Historian1 now takes uncertain regions into account when calculating StatusCodes
• Minimum2 Historian1 now takes uncertain regions into account when calculating StatusCodes
• MinimumActualTime2 Historian1 now has the StatusCodes calculated while using the TreatUncertainAsBad flag.
• Range2 Historian1 now looks at TreatUncertainAsBad in the calculation of the StatusCodes.
• Clarifications have been made to the text defining how PercentGood/PercentBad are used. The table values and StatusCodes of the TimeAverage2 and Total2 aggregates have been corrected.

IEC 62541-7: 2025 specifies value and structure of Profiles in the OPC Unified Architecture.
OPC UA Profiles are used to segregate features with regard to testing of OPC UA products and the nature of the testing. The scope of this document includes defining functionality that can only be tested. The definition of actual TestCases is not within the scope of this document, but the general categories of TestCases are covered by this document.
Most OPC UA applications will conform to several, but not all of the Profiles.
This fourth edition cancels and replaces the third edition published in 2020. This edition constitutes a technical revision.
This edition includes the following significant technical changes with respect to the previous edition:
a) Profiles and ConformanceUnits are not part of this document, but are solely managed in a public database as described in Clause 1.

IEC 62541-4:2025 is available as IEC 62541-4:2025 RLV which contains the International Standard and its Redline version, showing all changes of the technical content compared to the previous edition.IEC 62541-4:2025 defines the OPC Unified Architecture (OPC UA) Services. The Services defined are the collection of abstract Remote Procedure Calls (RPC) that are implemented by OPC UA Servers and called by OPC UA Clients. All interactions between OPC UA Clients and Servers occur via these Services. The defined Services are considered abstract because no particular RPC mechanism for implementation is defined in this document. IEC 62541‑6 specifies one or more concrete mappings supported for implementation. For example, one mapping in IEC 62541‑6 is to UA-TCP UA-SC UA-Binary. In that case the Services described in this document appear as OPC UA Binary encoded payload, secured with OPC UA Secure Conversation and transported via OPC UA TCP. Not all OPC UA Servers implement all of the defined Services. IEC 62541‑7 defines the Profiles that dictate which Services must be implemented in order to be compliant with a particular Profile. A BNF (Backus-Naur form) for browse path names is described in Annex A. This fourth edition cancels and replaces the third edition published in 2020. This edition constitutes a technical revision.
This edition includes the following significant technical changes with respect to the previous edition:
a) addition of new definitions to Method Call Service to allow optional Method arguments;
b)addition of reference to SystemStatusChangeEventType for event monitored item error scenarios;
c) enhancement of the general description of how determining if a Certificate is trusted;
d) addition of support for ECC;
e) addition of revisedAggregateConfiguration to AggregateFilterResult structure;
f) addition of INVALID to the BrowseDirection enumeration data type;
g) addition of INVALID to the TimestampsToReturn enumeration data type;
h) addition of definitions that make sure the subscription functionality works if retransmission queues are optional;
i) addition of client checks has been added to be symmetric to the Server Certificate check has been added;
j) clarification that ‘local’ top level domain is not appended by server into certificate and not checked by client when returned from LDS-ME;
k) addition of a definition for expiration behaviour of IssuedIdentityTokens;
l) addition of status code Good_PasswordChangeRequired to ActivateSession;
m) restriction of AdditionalInfo to servers in debug mode;
n) addition of new status code Bad_ServerTooBusy;
o) addition of definition for cases where server certificate must be contained in GetEndpoints response.

IEC 62541-10:2025 is available as IEC 62541-10:2025 RLV which contains the International Standard and its Redline version, showing all changes of the technical content compared to the previous edition.IEC 62541-10:2025 defines the Information Model associated with Programs in OPC Unified Architecture (OPC UA). This includes the description of the NodeClasses, standard Properties, Methods and Events and associated behaviour and information for Programs. The complete AddressSpace model including all NodeClasses and Attributes is specified in IEC 62541-3. The Services such as those used to invoke the Methods used to manage Programs are specified in IEC 62541-4. An example for a DomainDownload Program is defined in Annex A. This fourth edition cancels and replaces the third edition published in 2020. This edition constitutes a technical revision.
This edition includes the following significant technical changes with respect to the previous edition:
- StateMachine table format has been aligned.

IEC 62541-17:2025 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.

IEC 62541-19: 2025 defines an Information Model of the OPC Unified Architecture. The Information Model describes the basic infrastructure to reference from an OPC UA Information Model to external dictionaries like IEC Common Data Dictionary or ECLASS.

IEC 62541-16:2025 defines an Information Model. The Information Model describes the basic infrastructure to model state machines.
NOTE State Machines were dealt with in IEC 62541‑5:2020, Annex B. In newer versions of IEC 62541‑5 this Annex B was removed and replaced by this document

IEC 63082-1:2025 defines the concepts and terminology necessary to understand and communicate effectively about intelligent device management (IDM). This document explains the relationship between IDM and other existing asset management standards.
Additionally, this document describes principles and defines organizational and functional structures associated with IDM. This document also introduces the concept of IDM program for coordination of multiple stakeholders.
This first edition cancels and replaces the first edition of IEC TR 63082-1 published in 2020. This edition constitutes a technical revision.
This edition includes the following significant technical changes with respect to IEC TR 63082‑1:2020:
a) alignment with clause structure of IEC 63082-2.

IEC 62541-18: 2025 defines an Information Model. The Information Model describes the basic infrastructure to model role-based security.
NOTE In the previous version, Role-Based Security was in IEC 62541-5:2020, Annex F.

IEC 62453-1:2025 is available as IEC 62453-1:2025 RLV which contains the International Standard and its Redline version, showing all changes of the technical content compared to the previous edition.IEC 62453-1:2025 presents an overview and guidance for the IEC 62453 series. It
• explains the structure and content of the IEC 62453 series (see Clause 5);
• provides explanations of some aspects of the IEC 62453 series that are common to many of the parts of the series;
• describes the relationship to some other standards;
• provides definitions of terms used in other parts of the IEC 62453 series.
This third edition cancels and replaces the first edition published in 2016. This edition constitutes a technical revision.
This edition includes the following significant technical changes with respect to the previous edition:
a) introduction of a new implementation technology (defined in IEC TS 62453-43);
b) introduction of an OPC UA information model for FDT (defined in IEC 62453-71).

IEC 63489:2025 specifies the definition of cross-domain product data concepts (classes and properties) in the context of smart manufacturing.
This document will be published as a set of concepts within cross-domain data dictionary "General Items (IEC 61360-7)” in the IEC CDD.

IEC 63270-1:2025 provides guidance on the functional structure model, procedure, method, interface of function blocks. It also offers guidance on data requirements for predictive maintenance of equipment, devices and systems for industrial automation applications.
Condition monitoring is not only within the scope of this document but can also be an important input for predictive maintenance.

IEC 61987-41: 2025 provides:
• a characterization for the integration of process analysers in the Common Data Dictionary (CDD),
• generic structures for operating lists of properties (OLOP) and device lists of properties (DLOP) of measuring equipment in conformance with IEC 61987-10,
• generic structures for Dynamic Data, e.g. for condition monitoring of process analysers.
The generic structures for the OLOP and DLOP contain the most important blocks for process analysers. Blocks pertaining to a specific equipment type will be described in the corresponding part of the IEC 61987 standard series. Similarly, equipment properties are not part of this document. Thus, OLOP, DLOPs and LOPDs for selected process analysers families will be found in the IEC CDD.

IEC TS 62453-53-90:2025 provides information for integrating the HART®[1] technology into the CLI-based implementation of FDT interface specification (IEC TS 62453-43).
This document specifies implementation of communication and other services based on IEC 62453‑309.
This document neither contains the FDT specification nor modifies it.
[1] HART® and WirelessHART® are trade names of products supplied by FieldComm Group. This information is given for convenience of users of this document and does not constitute an endorsement by IEC of the product named. Equivalent products may be used if they can be shown to lead to the same results.

IEC TS 62453-53-31:2025 provides information for integrating the PROFIBUS[1] technology into the CLI-based implementation of FDT interface specification (IEC TS 62453-43).
This document specifies implementation of communication and other services based on IEC 62453‑303-1.
This document neither contains the FDT specification nor modifies it.
[1] PROFIBUS™ is a trade name of the non-profit organization PROFIBUS Nutzerorganisation e.V. (PNO). This information is given for the convenience of users of this document and does not constitute an endorsement by IEC of the trade name holder or any of its products. Compliance to this document does not require use of the registered logos for PROFIBUS™. Use of the registered logos for PROFIBUS™ requires permission of PNO.

IEC 61987-100:2025 provides the semantics of the data needed for the area of process automation, the Industrial Internet of Things (IIoT), and smart manufacturing. Classification and description of products with classes and properties for future objects within the scope of TC 65 (Industrial-process measurement, control and automation) will be developed as IEC 61987 DB standard and published via IEC CDD data dictionary IEC 61987.

IEC TS 62453-43:2024 specifies how the common FDT principles are implemented based on the CLI technology and web technologies for graphical user interfaces. The specification includes the object behaviour and object interaction via. NET Standard interfaces and JavaScript APIs. Emphasis has been placed on support of distributed Frame Application architectures.
This document specifies FDT version 3.0.

IEC 63261:2024 provides requirements for the E&I objects of a digital 3D plant model, used in the engineering phase to design and construct a process plant and its instrumentation. It provides guidance how to model plants and their electrical and instrumentation equipment.
This document also specifies the content and the possible output of the 3D plant model at project milestones.
This document can be used by the contractual partners to agree upon the content of the 3D plant model to be delivered at specified milestones.
This document does not specify the transfer and format of digital 3D plant models.
This document does not specify definitions or instructions to equipment representations and details of elements in the 3D plant model not belonging to electrical and instrumentation domains.
The content of the corrigendum 1 (2025-09) has been included in this copy.

IEC 61987-1:2024 defines a generic structure in which product features of industrial process measurement devices shall be arranged, in order to facilitate the understanding of product descriptions when they are transferred from one party to another. It applies to the production of catalogues supplied by the manufacturer of such devices and helps the user to formulate their requirements. This document will also serve as a reference document for all future standards which are concerned with process measuring equipment.
In addition, this document also provides a basic structure for the production of further standards listing the properties of process control equipment, for example, for actuators and infrastructure devices.
This edition includes the following significant technical changes with respect to the previous edition:
a) Addition of a subclause “Digital communication” in Clause 5, in order to allow a more comprehensive description of the properties of such an interface;
b) Alignment of clause headings, as described in the introduction, to correspond with those of the IEC CDD.

IEC 62382:2024 defines procedures and specifications for loop check, which comprises the activities between the completion of the loop construction (including installation and point-to-point checks) and the beginning of cold commissioning. This document is applicable for the construction of new plants and for expansion or retrofits (i.e. revamping) of electrical and instrument (E&I) installations in existing plants (including PLC, DCS, panel-mounted and field instrumentation). It does not include a detailed checkout of power distribution systems, except as they relate to the loops being checked (i.e. a motor starter or a power supply to a four-wire transmitter). Loop checks can be performed throughout the lifecycle of the plant. This document is also applicable when loop checks are performed after commissioning. This document describes what is intended to be tested but not how the test is performed, due to the wide range of technologies and equipment available.
The intent of this document is to provide a means for all parties, including the owner, the installer and the vendor, to clearly establish and agree on the scope of activities and responsibilities involved in performing these tests in order to achieve a timely delivery and acceptance of the automation system. The activities described in this document can be taken as a guideline and adapted to the specific requirements of the process, plant or equipment.
This edition includes the following significant technical changes with respect to the previous edition:
a) general re-organization of the content of the previous edition, moving informative content to the annexes;
b) replacing the forms based on I/O type in IEC 62382:2012, Annex A to Annex E with an example of a generic loop check form;
c) providing additional references to other applicable standards.

IEC 63082-2:2024 specifies requirements and recommendations for establishing and maintaining intelligent device management (IDM) as outlined in IEC TR 63082-1 in an enterprise having one or more facilities.
The following topics are included in the scope of this document:
- optimizing functionality and performance of intelligent devices for their use;
- managing information related to IDM;
- integrating intelligent devices into industrial automation and control systems (IACS) in facilities;
- exchanging information between stakeholders that achieve and sustain IDM;
- coordinating multiple asynchronous IDM life cycles.
The following topics are outside the scope of this document:
- defining and determining the function and performance of intelligent devices;
- defining and specifying technologies and tools that provide, preserve and manage information related to IDM such as FDT, FDI, portable on-line and off-line tools, configuration tools, historians, and maintenance planning tools;
- defining and specifying technologies and tools that are used to design intelligent devices;
- defining and specifying communication network architecture, communication technologies, cybersecurity requirements, and network management requirements.

IEC 62381:2024 defines requirements and checklists for the factory acceptance test (FAT), the factory integration test (FIT), the site acceptance test (SAT), and the site integration test (SIT). These tests are carried out to demonstrate that the automation system meets the requirements of the applicable specification. This document provides a means for all parties, including the owner, the buyer, and the vendor, to clearly establish and agree on the scope of activities and responsibilities involved in performing these tests in order to achieve a timely delivery and acceptance of the automation system. The activities specified in this document can be used to develop test plans adapted to the specific requirements of the process/plant/equipment. The annexes of this document contain checklists which are available for consideration when preparing specific test procedures and documentation for a specific automation system.
This edition includes the following significant technical changes with respect to the previous edition:
a) General re-organization of the standard;
b) Current technology incorporated;
c) Optional factory integration test (FIT) added;
d) Replaced the forms in the annexes with detailed checklists of activities which can be used to develop project-specific test plans; and
e) Provided additional references to other applicable standards.

IEC 61987-32:2024 This part of IEC 61987 provides an operating list of properties (OLOP) for the description of the operating parameters and the collection of requirements for I/O modules and a device list of properties (DLOP) for the description of a range of I/O module types.
The structures of the OLOP and the DLOPs correspond to the general structures defined in IEC 61987-11 and agree with the fundamentals for the construction of LOPs defined in IEC 61987-10.
Aspects other than the OLOP, needed in different electronic data exchange processes and described in IEC 61987-10 and IEC 61987-11, are published in IEC 61987-92.
The locations of the libraries of properties and of blocks used in the LOPs concerned are listed in Annex C and Annex D.

IEC 61406-2:2024 complements IEC 61406-1 by providing additional requirements for those cases where data elements are encoded within the Structured Identification Link string with standardized syntax and semantics.
In addition, this document covers cases where the uniqueness relates to product types/models or lots/batches. The default assumption is that the Identification Link identifies unique objects such as unique serialized products, assets, persons or packages, unless otherwise identified.

IEC 62453-302:2023 provides information for integrating the CIP™ technology into the FDT interface specification (IEC 62453‑2). Communication Profile Family 2 (commonly known as CIP™[1]) defines communication profiles based on IEC 61158-2 Type 2, IEC 61158-3-2, IEC 61158-4-2, IEC 61158-5-2, IEC 61158-6-2, and IEC 62026-3. The basic profiles CP 2/1 (ControlNet™[2]), CP 2/2 (EtherNet/IP™[3]), and CP 2/3 (DeviceNet™1) are defined in IEC 61784‑1 and IEC 61784‑2. An additional communication profile (CompoNet™1), also based on CIP™, is defined in IEC 62026-7. This part of IEC 62453 specifies communication and other services. This specification neither contains the FDT specification nor modifies it.
[1] CIP™ (Common Industrial Protocol), DeviceNet™ and CompoNet™ are trade names of Open DeviceNet Vendor Association, Inc (ODVA). This information is given for the convenience of users of this document and does not constitute an endorsement by IEC of the trade name holder or any of its products. Compliance to this standard does not require use of the trade names CIP™, DeviceNet™ or CompoNet™. Use of the trade names CIP™, DeviceNet™ or CompoNet™ requires permission of Open DeviceNet Vendor Association, Inc.
[2] ControlNet™ is a trade name of ControlNet International, Ltd. This information is given for the convenience of users of this document and does not constitute an endorsement by IEC of the trademark holder or any of its products. Compliance to this profile does not require use of the trade name ControlNet™. Use of the trade name ControlNet™ requires permission of ControlNet International, Ltd.
[3] EtherNet/IP™ is a trade name of ControlNet International, Ltd. and Open DeviceNet Vendor Association, Inc. This information is given for the convenience of users of this document and does not constitute an endorsement by IEC of the trademark holder or any of its products. Compliance to this profile does not require use of the trade name EtherNet/IP™. Use of the trade name EtherNet/IP™ requires permission of either ControlNet International, Ltd. or Open DeviceNet Vendor Association, Inc.

IEC 62453-71:2023 specifies an OPC UA Information Model to represent the device information based on FDT-defined device integration.

IEC 62769-150-1:2023 specifies an FDI profile of IEC 62769 for IEC 62734 (ISA100.11a)[1].
[1] ISA100 WIRELESSTM is a trade name of the non-profit consortium Wireless Compliance Institute. This information is given for the convenience of users of this standard and does not constitute an endorsement by IEC of the trademark holder or any of its products. Compliance does not require use of the trade name. Use of the trade name requires permission of the trade name holder.

IEC 62769-103-4:2023 specifies an FDI®[1] profile of IEC 62769 for IEC 61784-2_CP 3/4, IEC 61784-2_CP3/5 and IEC 61784-2_CP3/6 (PROFINET[2]).
[1] FDI is a registered trademark of the non-profit organization Fieldbus Foundation, Inc. This information is given for the convenience of users of this document and does not constitute an endorsement by IEC of the trademark holder or any of its products. Compliance does not require use of the trade name. Use of the trade name requires permission of the trade name holder.
[2] PROFINET is the trade name of the non-profit consortium PROFIBUS & PROFINET International. This information is given for the convenience of users of this technical report and does not constitute an endorsement by IEC of the trademark holder or any of its products. Compliance does not require use of the trade name. Use of the trade name requires permission of the trade name holder.

IEC 62769-109-1:2023 specifies an FDI®[1] profile of IEC 62769 for IEC 61784‑1_CP 9/1 (HART®)[2] and IEC 61784‑1_CP 9/2 (WirelessHART®)[3].
[1] FDI is a registered trademark of the non-profit organization Fieldbus Foundation, Inc. This information is given for the convenience of users of this document and does not constitute an endorsement by IEC of the trademark holder or any of its products. Compliance does not require use of the trade name. Use of the trade name requires permission of the trade name holder.
[2] HART is the trade name of the non-profit consortium FieldComm Group. This information is given for the convenience of users of this technical report and does not constitute an endorsement by IEC of the trademark holder or any of its products. Compliance does not require use of the trade name. Use of the trade name requires permission of the trade name holder.
[3] WirelessHART is the trade name of the non-profit consortium FieldComm Group. This information is given for the convenience of users of this technical report and does not constitute an endorsement by IEC of the trademark holder or any of its products. Compliance does not require use of the trade name. Use of the trade name requires permission of the trade name holder.

IEC 62769-103-1:2023 specifies an FDI®[1] profile of IEC 62769 for IEC 61784-1_CP 3/1 (PROFIBUS DP)[2] and IEC 61784-1_CP3/2 (PROFIBUS PA).
[1] FDI is a registered trademark of the non-profit organization Fieldbus Foundation, Inc. This information is given for the convenience of users of this document and does not constitute an endorsement by IEC of the trademark holder or any of its products. Compliance does not require use of the trade name. Use of the trade name requires permission of the trade name holder.
[2] PROFIBUS is the trade name of the non-profit consortium PROFIBUS & PROFINET International. This information is given for the convenience of users of this technical report and does not constitute an endorsement by IEC of the trademark holder or any of its products. Compliance does not require use of the trade name. Use of the trade name requires permission of the trade name holder.

IEC 62769-102-2:2023 defines the protocol-specific definitions (PSDs) as defined in IEC 62769‑100 (annex on generic protocol extensions) for the Ethernet/IP protocol.

IEC 62769-101-2:2023 specifies the IEC 62769 profile for IEC 61784‑1, CP 1/2 (Foundation™ Fieldbus HSE)[1].
[1] Foundation™ Fieldbus is the trade name of the non-profit consortium Fieldbus Foundation. This information is given for the convenience of users of this technical report and does not constitute an endorsement by IEC of the trademark holder or any of its products. Compliance does not require use of the trade name. Use of the trade name requires permission of the trade name holder.

IEC 62769-6-200:2023 specifies the technology mapping for the concepts described in the Field Device Integration (FDI®[1]) standard. The technology mapping focuses on implementation regarding the components FDI® Client and User Interface Plug-in (UIP) for the Runtime HTML5.
[1] FDI is a registered trademark of the non-profit organization Fieldbus Foundation, Inc. This information is given for the convenience of users of this document and does not constitute an endorsement by IEC of the trademark holder or any of its products. Compliance does not require use of the trade name. Use of the trade name requires permission of the trade name holder.

IEC 62769-151-1:2023 defines the protocol-specific definitions (PSDs) as defined in IEC 62769‑7 for the OPC UA protocol.

IEC 62769-6-100:2023 specifies the technology mapping for the concepts described in the Field Device Integration (FDI®[1]) standard. The technology mapping focuses on implementation regarding the components FDI® Client and User Interface Plug-in (UIP) using the Runtime .NET. This runtime is specific only to the WORKSTATION platform as defined in IEC 62769‑4.
[1] FDI is a registered trademark of the non-profit organization Fieldbus Foundation, Inc. This information is given for the convenience of users of this document and does not constitute an endorsement by IEC of the trademark holder or any of its products. Compliance does not require use of the trade name. Use of the trade name requires permission of the trade name holder.

IEC 62769-101-1:2023 specifies an FDI®[1] profile of IEC 62769 for IEC 61784‑1_CP 1/1 (Foundation™ Fieldbus H1)[2].
[1] FDI is a registered trademark of the non-profit organization Fieldbus Foundation, Inc. This information is given for the convenience of users of this document and does not constitute an endorsement by IEC of the trademark holder or any of its products. Compliance does not require use of the trade name. Use of the trade name requires permission of the trade name holder.
[2] Foundation™ Fieldbus is the trade name of the non-profit consortium Fieldbus Foundation. This information is given for the convenience of users of this standard and does not constitute an endorsement by IEC of the trademark holder or any of its products. Compliance does not require use of the trade name. Use of the trade name requires permission of the trade name holder.

IEC 62769-100:2023 specifies an FDI®[1] profile of IEC 62769 for Generic Protocols. That means that all interfaces are defined and a host can add support for more protocols without changing its implementation. Nevertheless, there are some protocol specific definitions (PSD) that need to be specified per protocol using this profile. Annex C specifies what PSD need to be defined per protocol so that FDI® Device Packages, FDI® Communication Packages for Gateways and FDI® Communication Servers, FDI® Communication Server, Gateways and Devices supporting such a protocol can work together in a host not aware about this specific protocol.

IEC 62769-6:2023 specifies the technology mapping for the concepts described in the Field Device Integration (FDI®[1]) standard. The technology mapping focuses on implementation of the components FDI® Client and User Interface Plug-in (UIP) in the specified technologies for the WORKSTATION platform and the MOBILE platform as defined in IEC 62769-4. There are individual subparts for the currently supported technologies .NET and HTML5.

IEC 62769-7:2023 specifies the elements implementing communication capabilities called Communication Devices. The overall FDI®[1] architecture is illustrated in Figure 1. The architectural components that are within the scope of this document have been highlighted in this illustration. The document scope with respect to FDI® Packages is limited to Communication Devices. The Communication Server shown in Figure 1 is an example of a specific Communication Device.
[1] FDI® is a registered trademark of the non-profit organization Fieldbus Foundation, Inc. This information is given for the convenience of users of this document and does not constitute an endorsement by IEC of the trademark holder or any of its products. Compliance does not require use of the trade name. Use of the trade name requires permission of the trade name holder.

IEC 62769-4:2023 specifies the FDI®[1] Packages. The overall FDI® architecture is illustrated in Figure 1. The architectural components that are within the scope of this document have been highlighted in Architecture diagram figure.
[1] FDI® is a registered trademark of the non-profit organization Fieldbus Foundation, Inc. This information is given for the convenience of users of this document and does not constitute an endorsement by IEC of the trademark holder or any of its products. Compliance does not require use of the trade name. Use of the trade name requires permission of the trade name holder.

IEC 62769-5:2023 defines the FDI®[1] Information Model. One of the main tasks of the Information Model is to reflect the topology of the automation system. Therefore, it represents the devices of the automation system as well as the connecting communication networks including their properties, relationships, and the operations that can be performed on them. The types in the AddressSpace of the FDI® Server constitute some kind of catalogue, which is built from FDI® Packages. The fundamental types for the FDI® Information Model are well defined in OPC UA for Devices (IEC 62541‑100). The FDI® Information Model specifies extensions for a few special cases and otherwise explains how these types are used and how the contents are built from elements of DevicePackages.
[1] FDI® is a registered trademark of the non-profit organization Fieldbus Foundation, Inc. This information is given for the convenience of users of this document and does not constitute an endorsement by IEC of the trademark holder or any of its products. Compliance does not require use of the trade name. Use of the trade name requires permission of the trade name holder.

IEC 62769-8:2023 specifies how the internal view of a device model represented by the EDD can be transferred into an external view as an OPC-UA information model by mapping EDD constructs to OPC-UA objects.

IEC 62769-1:2023 describes the concepts and overview of the Field Device Integration (FDI®[1]) specifications. The detailed motivation for the creation of this technology is also described . Reading this document is helpful to understand the other parts of this multi-part standard.
[1] FDI® is a registered trademark of the non-profit organization Fieldbus Foundation, Inc. This information is given for the convenience of users of this document and does not constitute an endorsement by IEC of the trademark holder or any of its products. Compliance does not require use of the trade name. Use of the trade name requires permission of the trade name holder.

IEC 62769-2:2023 specifies the FDI®[1] Client. See Annex C for some typical FDI® Client use cases. The overall FDI® architecture is illustrated in Figure 1. The architectural components that are within the scope of this document have been highlighted in Figure 1.
[1] FDI® is a registered trademark of the non-profit organization Fieldbus Foundation, Inc. This information is given for the convenience of users of this document and does not constitute an endorsement by IEC of the trademark holder or any of its products. Compliance does not require use of the trade name. Use of the trade name requires permission of the trade name holder.

IEC 62769-3:2023 specifies the FDI®[1] Server. The overall FDI® architecture is illustrated in Figure 1. The architectural components that are within the scope of this document have been highlighted in this figure. Annex A provides a functional description of the FDI® Server.
[1] FDI® is a registered trademark of the non-profit organization Fieldbus Foundation, Inc. This information is given for the convenience of users of this document and does not constitute an endorsement by IEC of the trademark holder or any of its products. Compliance does not require use of the trade name. Use of the trade name requires permission of the trade name holder.

IEC 61987-31:2022 provides
a characterization for the integration of infrastructure devices in the Common Data Dictionary (CDD);
generic structures in conformance with IEC 61987-10 for Operating Lists of Properties (OLOPs) and Device Lists of Properties (DLOPs) of infrastructure devices.
The generic structures for the OLOP and DLOP contain the most important blocks for infrastructure devices. Blocks pertaining to a specific equipment type will be described in the corresponding part of the IEC 61987 series. Similarly, equipment properties are not part of this part of IEC 61987. For instance, the OLOP and DLOP for I/O-modules are to be found in IEC 61987-32.

IEC 62714-2:2022 specifies normative as well as informative AML libraries for the modelling of engineering information for the exchange between engineering tools in the plant automation area by means of AML. Moreover, it presents additional user-defined libraries as an example. Its provisions apply to the export;import applications of related tools. This part of IEC 62714 specifies AML role class libraries and the usage of AML attributes to represent semantic information. Role classes provide semantics to AML objects, attribute types provide semantics to AML attributes. The association of role classes to AML objects or attribute types to AML attributes represent the possibility to add (also external) semantic information to it. By associating a role class to an AML object or an attribute type to an AML attribute, it gets semantic information. This part of IEC 62714 does not define details of the data exchange procedure or implementation requirements for the import;export tools.

IEC 63365:2022 applies to products used in the process measurement, control and automation industry. It establishes a concept and requirements for the digital nameplate and provides alternative electronically readable solutions (e.g. 2D codes, RFID or firmware) to current conventional plain text marking on the nameplate or packaging of products.
The digital nameplate information is contained in the electronically readable medium affixed to the product, the packaging or accompanying documents. The digital nameplate information is available offline without Internet connection. After electronic reading, all digital nameplate information is displayed in a human readable text format. The digital nameplate also includes the Identification Link String according to IEC 61406-1 which provides additional online information for the product.
This document does not specify the contents of the conventional nameplate, which are subject to regional or national regulations and standards.