TC 65 - Industrial-process measurement, control and automation

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-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-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-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-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-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-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 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 61326-2-7:2025 specifies the EMC test requirements for process automation equipment using at least one Ethernet APL (Ethernet ADVANCED PHYSICAL LAYER) compliant port according IEC TS 63444. The type of equipment covered by this document includes INFRASTRUCTURE DEVICES such as switches as well as measurement and control devices. This document provides requirements for the EMC test setups of the APL interface for devices intended for use in process control and process measurement.
The other functions of the equipment remain covered by other parts of the IEC 61326 series.
NOTE Ethernet-APL uses IEEE Std. 802.3 2022 Ethernet Physical Layer 10BASE-T1L, suitable to be used for full-duplex communication over a single balanced pair of conductors.
The test levels are based on the intended environment as stated in the product’s specification or user documentation and selected appropriately from IEC 61326-1.

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 PAS 63595:2025 defines wireless communication systems based on 5G and beyond technologies applicable for industrial process measurement and control applications. Based on common terminology, generic descriptions, and use cases, this document provides requirements for related users, designers, and device manufacturers.
This document considers cellular wireless communication systems according to the specifications of the terrestrial radio interfaces of International Mobile Telecommunications-2020 (IMT-2020) developed by 3GPP as 5G Release 15 and beyond (see ITU-R M.2150-1:02/2022).
NOTE 1 Non-cellular professional stand-alone wireless communication systems, also called NR+, are not considered.
NOTE 2 The PAS is a pre-standard and can be converted into a series of documents for users, designers, and device manufacturers.
NOTE In accordance with ISO/IEC Directives, Part 1, IEC PASs are automatically withdrawn after 4 years.

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 TR 61508-3-3:2025 makes a proposal as to which topics to consider and which methods and techniques to use when designing object-oriented software to ensure suitable quality for use in functional safety applications.
Object-oriented languages are perceived as "state-of-the-art" nowadays. Such languages seem to be excluded from use by several statements in IEC 61508-3. However there are additions in some tables such as in IEC 61508-3:2010, Table B.1, where notes are added under which their use might be justified. Such exceptions that would allow, for example, dynamic objects, name the main concerns such as memory allocation and predictable timing issues and guide the user to safe use of object-oriented languages. These considerations are taken up in this document to specify methods and techniques that allow the reduction of systematic faults to the levels required by the respective systematic capabilities.
This document is not intended to replace any part of IEC 61508-3. Rules that exist in IEC 61508‑3 are valid here as well and are not repeated, including rules that concern:
• the software life cycle,
• involvement of the assessor,
• modularization,
• principle of information hiding,
• proving and conventional testing,
• basic aspects of documentation,
• low coupling and high cohesion,
• responsibilities and training of people,
• operational experience as described in IEC 61508-4 and IEC 61508-7
This TR is a supplement to the IEC 61508 standard series. It has to be read in conjunction with IEC 61508-3 and proposes a way how the use of object-oriented software in safety relevant applications can be justified.

IEC 61326-2-6:2025 applies to the BASIC SAFETY and ESSENTIAL PERFORMANCE of IN VITRO DIAGNOSTIC MEDICAL ELECTRICAL EQUIPMENT (IVD MEE). This part of IEC 61326 applies to the BASIC SAFETY and ESSENTIAL PERFORMANCE of IVD MEE in the presence of electromagnetic disturbances and to electromagnetic disturbances emitted by IVD MEE.
BASIC SAFETY with regard to electromagnetic disturbances is applicable to all IVD MEE.
NOTE 1 Performance with respect to electromagnetic disturbances other than ESSENTIAL PERFORMANCE is the subject of IEC 61326-1:2020
NOTE 2 IT equipment can be a part of an IVD MEE, if it is required to maintain BASIC SAFETY or ESSENTIAL PERFORMANCE.
This edition includes the following significant technical changes with respect to the previous edition:
- Update of the document with respect to test levels and documentation.

IEC TR 63319:2025 uses a meta-modelling approach to identify commonalities among ten smart manufacturing reference models. Each reference model is placed into the context of the meta-model to facilitate analysis of both common and distinct features. Major smart manufacturing reference model topics are identified, and the reference models compared within each topic.
As part of the meta-modelling approach development, a collection of models differing in extent of abstraction characterizes the evolution of a particular smart manufacturing system from the meta-model through a unifying smart manufacturing reference model and successively less abstract domain models to a model for system implementation.
This document presents a range of issues and challenges for further work to specify a high-level smart manufacturing reference model that unifies the concepts and practices identified using the meta-model approach analysis of the smart manufacturing reference models.
It is published as a dual logo standard.

IEC 61131-3:2025 specifies the syntax and semantics of programming languages for programmable controllers as defined in IEC 61131-1.
This document specifies the syntax and semantics of a unified suite of programming languages for programmable controllers (PCs). This suite consists of the textual language structured text (ST), and the graphical languages, ladder diagram (LD) and function block diagram (FBD).
An additional set of graphical and equivalent textual elements named sequential function chart (SFC) is defined for structuring the internal organization of programs and function blocks. Also, configuration elements are defined which support the installation of programmable controller programs into programmable controller systems.
In addition, features are defined which facilitate communication among programmable controllers and other components of automated systems.
This edition includes the following significant technical changes with respect to the previous edition:
a) inclusion of UTF-8 strings and their associated functions;
b) Annex B contains a comprehensive list of features that have been added, removed or deprecated in comparison to IEC 61131-3:2013.

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 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 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 PAS 62443-2-2: 2025 provides guidance on the development, validation, operation, and maintenance of a set of technical, physical, and process security measures called Security Protection Scheme (SPS). The document’s goal is to provide the asset owner implementing an IACS Security Program (SP) with mechanisms and procedures to ensure that the design, implementation and operation of an SPS manage the risks resulting from cyberthreats to each of the IACS included in its operating facility.
The document is based on contents specified in other documents of the IEC 62443 series and explains how these contents can be used to support the development of technical, physical, and process security measures addressing the risks to the IACS during the operation phase.

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 62541-15:2025 describes a safety communication layer (services and a protocol) for the exchange of SafetyData using IEC 62541 mechanisms. It identifies the principles for functional safety communications defined in IEC 61784‑3 that are relevant for this safety communication layer. This safety communication layer is intended for implementation in safety devices only.
NOTE 1 This document targets controller-to-controller communication. However, easy expandability to other use-cases (e.g. OPC UA field level communication) has already been considered in the design of this document.
NOTE 2 This document does not cover electrical safety and intrinsic safety aspects. Electrical safety relates to hazards such as electrical shock. Intrinsic safety relates to hazards associated with potentially explosive atmospheres.
This document defines mechanisms for the transmission of safety-relevant messages among participants within a network using OPC UA technology in accordance with the requirements of the IEC 61508 series and IEC 61784-3 for functional safety. These mechanisms can be used in various industrial applications such as process control, manufacturing, automation, and machinery.
This document provides guidelines for both developers and assessors of compliant devices and systems.
NOTE 3 The resulting SIL claim of a system depends on the implementation of this document within the system – implementation of this document in a standard device is not sufficient to qualify it as a safety device.

IEC 62657-4:2025 specifies a concept and methods for central coordination (CC) of automation applications using wireless communications to extend the coexistence management according to IEC 62657-2. It establishes system elements, interfaces and relationships for a central coordination. Functions, data, and data exchange for assessing and maintaining the coexistence state are specified.
This document specifies the central coordination point (CCP) approach as one example of the usage of the formal description given in IEC 62657-3. This document is applicable to develop, implement, or modify procedures or solutions.
This document provides requirements for automated coexistence management systems.
This document provides requirements for:
– determination of the coexistence state,
– automated coexistence management procedures,
– CC amendments for existing wireless communication solutions,
– CC functions that coordinate legacy and new wireless communication systems,
– CC sequences and message formats for data exchange.
This document is not restricted to a specific radio frequency range nor is it restricted to a specific wireless communication technology.
This edition includes the following significant technical changes with respect to the previous edition:
a) The data item (parameter) to be exchanged between CCP and CMWCA and CMWD to ensure interoperability between CCP providers and device providers.
b) The sequence of services conducted between CCP and CMWCA and CMWD are now defined. When the CCP providers and the device providers implement similar process, clearly defined sequence and unified execution specifications ensure interoperability as expected.
c) The message formats of sequence diagram to be exchanged between CCP and CMWCA and CMWD are defined. By defining the message formats, the hierarchical structure of each data (parameter), and implementing the same message format by the CCP provider and the device provider, enables to exchange data correctly and ensure interoperability.

IEC 62657-2:2025 specifies:
– the fundamental assumptions, concepts, parameters, and procedures for wireless communication coexistence;
– specifies coexistence parameters and how they are used in an application requiring wireless coexistence;
– provides guidelines, requirements, and best practices for wireless communication's availability and performance in an industrial automation plant; it covers the life‑cycle of wireless communication coexistence;
– helps the work of all persons involved with the relevant responsibilities to cope with the critical aspects at each phase of life-cycle of the wireless communication coexistence management in an industrial automation plant. Life-cycle aspects include: planning, design, installation, implementation, operation, maintenance, administration and training;
– provides a common point of reference for wireless communication coexistence for industrial automation sites as a homogeneous guideline to help the users assess and gauge their plant efforts;
– deals with the operational aspects of wireless communication coexistence regarding both the static human/tool-organization and the dynamic network self-organization.
This document provides a major contribution to national and regional regulations by supporting to fulfil the requirements using coexistence management.
This edition includes the following significant technical changes with respect to the previous edition:
a) alignment of some definitions and specifications of coexistence parameters in order to facilitate their future inclusion in the IEC Common Data Dictionary (IEC CDD) maintained by the IEC;
b) alignment of some definitions and specifications to be consistent with the new IEC 62657-3 and IEC 62657-4;
c) edition 3 of this document was published in June 2022. Some comments were made in the last development stages of this document asking for explanations on how the parts of the IEC 62657 series were structured and how they were related to each other. Resolution of these comments was deferred until a next edition, which means this edition.

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 63165:2024 applies to the industrial water quality analyzer system that uses a photometric method to determine the concentration of one or more chemical components in industrial water (water used in manufacturing, processing, cooling, washing, boiler, etc).
The objective of this document is to:
- specify the terminology and definitions related to the performance characteristics of a photometric industrial water quality analyzer system;
- unify the performance expression and verifying methods of such an analyzer system;
- specify the test procedures to be used in making statements on the performance characteristics of a photometric industrial water quality analyzer system.

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 TR 63283-5:2024 describes the market and innovation trend analysis affecting smart manufacturing (SM). The market and innovation trends will influence the evolution of smart manufacturing and it will be important to have good insights on these trends. Specific aspects of the market trends are the evolution of the business cases that is assumed to highlight new supplier chain models, new revenue streams, new customer services, and/or new customer segments.
The document will address the following topics:
• Market watch: Identify the important, likely, and/or disruptive market trends (e.g. mass customization) from an end-to-end perspective, which impact smart manufacturing topics/aspects. This includes the end-user, producers, supply chain, regulators, etc.
• Business model watch: Identify the new business model trends from an end-to-end perspective, which impact smart manufacturing.
• Technological watch: Identify the important, likely, and/or disruptive innovations (AI chipsets, 6G, quantum computing, etc.) describing the impacted smart manufacturing topics/aspects; this topic will focus on those technologies that are still under development but is assumed to influence (or is assumed to be influenced by) smart manufacturing.
There are many more new trends which are used in SM. In this document, only some frequently discussed trends are presented. Some technologies are considered to have priority according to their maturity.
This work will focus on how they can be used in SM.

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 61010-2-201:2024 supplements or modifies the corresponding clauses in IEC 61010-1 so as to convert that publication into the IEC standard: Particular requirements for control equipment. This document is to be used in conjunction with IEC 61010-1:2010, and IEC 61010 1:2010/AMD1:2016. Where a particular subclause of IEC 61010-1 is not mentioned in this document, that subclause applies as far as is reasonable. Where this document states "addition", "modification", "replacement", or "deletion", the relevant requirement, test specification or note in IEC 61010 1 should be adapted accordingly.
This edition includes the following significant technical changes with respect to the previous edition:
a) 1.1.1: the related equipment included in the Scope has been clarified;
b) 4.3.2.101: the optical fibre module has been deleted;
c) 5.4.3: equipment installation has been clarified;
d) 6.7.1.1: revision of the figure representing insulation between separate circuits has been included;
e) 6.7.101: the subclause relating to insulation for FIELD WIRING TERMINALS of OVERVOLTAGE CATEGORY ll with a nominal voltage up to 1 000 V has been deleted;
f) 6.7.1.101: a new subclause relating to insulation for SELV/PELV CIRCUITS has been included;
g) 6.8.3: specification of voltage tester has been added;
h) 6.9.3: an additional exception relating to colour coding has been included;
i) 6.9.101: a new subclause relating to wiring for secondary circuits e.g. SELV/PELV has been included;
j) 8.2.2.101: additional requirements for glass displays have been included;
k) 8.3: the subclause relating to the drop test has been removed;
l) 9.3.2: additional requirements for material of connectors and insulating material have been included;
m) The particular requirements for non-metallic material have been clarified;
n) Clause 11: the particular requirements for protection against HAZARDS from fluid and solid foreign objects have been removed;
o) 12.4: an additional subclause relating to microwave radiation has been included;
p) 14.102: the description of switching devices has been clarified;

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 61784-3-19:2024 specifies a safety communication layer (services and protocol) based on IEC 61784‑1-19, IEC 61784-2-19 and the IEC 61158 series (Type 24 and Type 27). It identifies the principles for functional safety communications defined in IEC 61784‑3 that are relevant for this safety communication layer. This safety communication layer is intended for implementation in safety devices only.
NOTE 1 It does not cover electrical safety and intrinsic safety aspects. Electrical safety relates to hazards such as electrical shock. Intrinsic safety relates to hazards associated with potentially explosive atmospheres.
This document defines mechanisms for the transmission of safety-relevant messages among participants within a distributed network using fieldbus technology in accordance with the requirements of the IEC 61508 series for functional safety. These mechanisms can be used in various industrial applications such as process control, manufacturing automation and machinery.
This document provides guidelines for both developers and assessors of compliant devices and systems.
NOTE 2 The resulting SIL claim of a system depends on the implementation of the selected functional safety communication profile within this system – implementation of a functional safety communication profile according to this document in a standard device is not sufficient to qualify it as a safety device.

IEC 63339:2024 specifies the unified reference model for smart manufacturing (URMSM) using a terminology and structure, and establishes criteria for creating reference models, as specializations, that support smart manufacturing. The terminology and structure comprise a set of common modelling elements, their associations, and conformance criteria. These common modelling elements address aspects and perspectives of products and production and their lifecycle considerations.
The URMSM enables an approach for creating multiple models based upon a reference model that is sufficient for understanding significant relationships among entities involved in smart manufacturing (SM) and for the development of standards and other specifications.
The URMSM specifications in this document accommodate consistent, coherent, compatible specializations for relevant aspects of manufacturing systems consisting of equipment, products, and services within the domain of manufacturing. Provisions of this document are applicable for a new smart manufacturing reference model (SMRM) or elaboration of existing SMRM capabilities, for example, improving capabilities for analysis of opportunities and synthesis of technological advances, and improving interoperability of new and existing systems.
This document is not intended to prescribe interoperability considerations or data schemas of models. Standardization of content relative to models will be the subject of other standards and texts specific to those model domains.

This document defines a set of environmental performance evaluation (EPE) data classes, including their properties.
It is applicable to entire manufacturing facilities or to parts of a manufacturing facility.
This document applies to manufacturing systems including discrete, batch and continuous control, which are defined in IEC 62264-1.
The following are outside the scope of this document:
- syntax of EPE data and data models;
- protocols to exchange EPE data;
- functions that can be enabled by the use of EPE data;
- product life cycle assessment;
- EPE data that are specific to a particular industry sector, manufacturer or machinery;
- acquisition of EPE data.

IEC TS 61508-3-2:2024 covers the general assurance of dependable software used in critical operational-technology (OT) which is running on hardware devices which are specified as part of the OT application. It is particularly aimed at safety-related software which is being developed according to the E/E/PE software functional safety standard IEC 61508-3; in particular, the development of the software follows a Formal Safety Requirements Specification. Successful use of some or all of the assurance points specified in this document enhances the confidence that a particular piece of safety-related software meets the requirements of the SIL of the safety function which it (partially or fully) implements, and thereby increases the systematic capability of the software.

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 62443-2-1:2024 specifies asset owner security program (SP) policy and procedure requirements for an industrial automation and control system (IACS) in operation. This document uses the broad definition and scope of what constitutes an IACS as described in IEC TS 62443‑1‑1. In the context of this document, asset owner also includes the operator of the IACS.
This document recognizes that the lifespan of an IACS can exceed twenty years, and that many legacy systems contain hardware and software that are no longer supported. Therefore, the SP for most legacy systems addresses only a subset of the requirements defined in this document. For example, if IACS or component software is no longer supported, security patching requirements cannot be met. Similarly, backup software for many older systems is not available for all components of the IACS. This document does not specify that an IACS has these technical requirements. This document states that the asset owner needs to have policies and procedures around these types of requirements. In the case where an asset owner has legacy systems that do not have the native technical capabilities, compensating security measures can be part of the policies and procedures specified in this document.
This edition includes the following significant technical changes with respect to the previous edition:
a) revised requirement structure into SP elements (SPEs),
b) revised requirements to eliminate duplication of an information security management system (ISMS), and
c) defined a maturity model for evaluating requirements.

IEC 63303:2024 defines general structures and functions of HMI systems.
An HMI life cycle example for HMI systems is included.
This document specifies requirements and recommendations for activities in each stage of the life cycle including designing, using, and maintaining the HMI system.
It also provides requirements and recommendations for functions and performance of HMI systems.
The requirements and recommendations in this document are applicable to any controlled process using an HMI to interface to a control system. There can be differences in implementation to meet the specific needs based on the application and controlled process type.

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 61784-3:2021 explains some common principles that can be used in the transmission of safety-relevant messages among participants within a distributed network which use fieldbus technology in accordance with the requirements of IEC 61508 (all parts) for functional safety. These principles are based on the black channel approach. They can be used in various industrial applications such as process control, manufacturing automation and machinery.

IEC 61784-5-19:2024 specifies the installation profile for CPF 19 (MECHATROLINKTM[1]). The installation profiles are specified in the annexes. These annexes are read in conjunction with IEC 61918:2018, IEC 61918:2018/AMD1:2022 and IEC 61918:2018/AMD2:2024.
[1] MECHATROLINKTM and Σ-LINKTM II are trade names of YASKAWA ELECTRIC CORPORATION. This information is given for the convenience of users of this document and does not constitute an endorsement by IEC of the trade names holder or any of its products. Compliance to this profile does not require use of the trade names. Use of the trade name requires permission of the trade name holder.

IEC 61784-5-8:2024 specifies the installation profiles for CPF 8 (CC-LinkTM[1]). The installation profiles are specified in the annexes. These annexes are read in conjunction with IEC 61918:2018, IEC 61918:2018/AMD1:2022 and IEC 61918:2018/AMD2:2024.
[1] CC-Link™, CC-Link/LT™ and CC‑Link IE™ are trade names of Mitsubishi Electric Co., control of trade name use is given to CCLink Partner Association. 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. Use of the trade name requires permission of the trade name holder.

IEC 61784-5-6:2024 specifies the installation profiles for CPF 6 (INTERBUSTM)[1]. The installation profiles are specified in the annexes. These annexes are read in conjunction with IEC 61918:2018, IEC 61918:2018/AMD1:2022 and IEC 61918:2018/AMD2:2024.
[1] INTERBUSTM is a trade name of INTERBUS Club, an independent organisation of users and vendors of INTERBUS products. 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 INTERBUS. Use of the trade name INTERBUS requires permission of the trade name holder.