February 2026: Key Manufacturing Engineering Standards for OPC UA Interoperability

The February 2026 publication cycle delivers pivotal advancements in manufacturing engineering standards, with five new releases focused on the OPC Unified Architecture (OPC UA) suite. These standards reshape the landscape for industrial automation, interoperability, and secure information exchange — covering file transfer, device onboarding, network modeling, reference types, and scheduling. For manufacturing professionals, quality managers, and automation engineers, understanding these updates is critical for driving digital transformation, maintaining compliance, and ensuring efficient integration of complex systems.

Overview / Introduction

Manufacturing engineering is in the midst of a digital revolution, where seamless interoperability, robust cybersecurity, and standardized data models are indispensable. International standards are the backbone of this evolution, providing the requirements, specifications, and guidelines needed to reliably integrate equipment, streamline processes, and adapt to dynamic market needs.

This article examines five newly published standards within the OPC UA series:

• File Transfer
• Device Onboarding
• Base Network Modeling
• Common ReferenceTypes
• Scheduler Information Models

Professionals will gain a working knowledge of each standard’s scope, implementation best practices, compliance obligations, and projected impacts on manufacturing operations.

Detailed Standards Coverage

EN IEC 62541-20:2026 - OPC Unified Architecture – Part 20: File Transfer

OPC Unified Architecture – Part 20: File Transfer

This standard defines a robust information model for modeling file transfers within OPC UA-based systems. It introduces the FileType object, enabling the controlled transfer of files such as configuration data, firmware updates, and logs, between OPC UA clients and servers.

Key Requirements and Scope

• Defines the FileType and associated methods (Open, Close, Read, Write, GetPosition, SetPosition) to safely access file data.
• Incorporates file system management through the FileDirectoryType (supporting operations like Create, Delete, Move, Copy, and Directory navigation).
• Adds the TemporaryFileTransferType, optimizing transient use cases such as firmware upgrades, where handshake mechanisms and commit/rollback functionalities are required.
• Separates logical files and their physical storage, ensuring efficient file handling in highly available and distributed production environments.

Who Should Comply

• Industrial device manufacturers
• Software vendors developing OPC UA connectors or servers
• System integrators responsible for OT/IT convergence

Practical Implications

Adopting this standard enhances security by avoiding resource-heavy byte array transfers, supports robust multi-client operations, and streamlines traceable file interactions.

Notable Changes

• Moves file transfer mechanisms from Annex C (IEC 62541-5:2020) to a full standalone part, expanding model flexibility and implementation options.

Key highlights:

• Standardized file operations with advanced access control
• File directory and temporary file transfer support
• Improved concurrency and auditability in file exchanges

Access the full standard:View EN IEC 62541-20:2026 on iTeh Standards

EN IEC 62541-21:2026 - OPC Unified Architecture – Part 21: Device Onboarding

OPC Unified Architecture – Part 21: Device Onboarding

This standard addresses the entire lifecycle of industrial devices and composite systems, from initial authentication to configuration, operation, and decommissioning. It standardizes mechanisms to verify device authenticity, manage identities, and automate secure onboarding.

Scope and Requirements

• Models device life cycle processes: distribution, onboarding (including Trust On First Use), configuration, operation, and secure decommissioning.
• Describes workflows for physical control transfer, role/privilege assignment, software, and firmware updates via controlled ticketing mechanisms.
• Defines Registrar entities for device registration and management, enabling audit trail automation and compliance with zero-trust industrial environments.
• Specifies identity management using symbolic NodeIds and namespace URI mapping.

Applicability

• Device OEMs, integrators, and smart factory operators
• IT/OT security architects
• Certification bodies conducting device acceptance and onboarding audits

Implementation Impact

Organizations implementing this standard benefit from streamlined device commissioning, identity assurance, and reduced risk of unauthorized network access or configuration drift.

Notable Updates

• First OPC UA standard to create structured, auditable onboarding workflows and device registrar constructs.

Key highlights:

• End-to-end, role-based onboarding workflows
• Secure element support and device identity ticketing
• Automated audit event tracking across device life cycle

Access the full standard:View EN IEC 62541-21:2026 on iTeh Standards

EN IEC 62541-22:2026 - OPC Unified Architecture – Part 22: Base Network Model

OPC Unified Architecture – Part 22: Base Network Model

The Base Network Model provides a canonical OPC UA information model for describing network components and their configuration, laying the groundwork for consistent handling of industrial Ethernet, Time-Sensitive Networking (TSN), and, in the future, other network technologies.

Scope and Specifications

• Defines parameter sets for network talkers/listeners (particularly relevant for TSN applications), interfaces, ports, and priority mappings.
• Models networking resources with object type hierarchies for interfaces (IIetfBaseNetworkInterfaceType, IIeeeBaseEthernetPortType), VLAN tags, and stream communications.
• Mapping tables support virtual interfaces and link aggregation, with examples for advanced topologies.
• Future extensibility for non-Ethernet technologies is anticipated.

Target Audience

• Control system engineers
• Network architects in smart manufacturing settings
• Vendors of industrial network equipment (e.g., TSN switches, gateways)

Practical Implications

By adhering to this standard, enterprises can achieve greater plug-and-play compatibility for networked devices, automate mapping, and better support converged OT/IT architectures in the era of Industrial IoT.

Notable Advancements

• Introduces object models for dynamic, automated network configuration and diagnostics
• Enables network topology visualization in OPC UA address spaces

Key highlights:

• TSN-ready base model for networked components
• Object hierarchy for interfaces, VLANs, and streams
• Conformance for growing IIoT and Industry 4.0 applications

Access the full standard:View EN IEC 62541-22:2026 on iTeh Standards

EN IEC 62541-23:2026 - OPC Unified Architecture – Part 23: Common ReferenceTypes

OPC Unified Architecture – Part 23: Common ReferenceTypes

This document standardizes a suite of ReferenceTypes used broadly across OPC UA industrial information models, providing semantic consistency and richer context when connecting nodes in an OPC UA address space.

Major Specifications

• Defines granular relationship types such as IsExecutableOn, IsExecutingOn, Controls, Utilizes, Requires, IsPhysicallyConnectedTo, RepresentsSameEntityAs, and their associated modeling rules.
• Ensures that different vendors’ systems connect contextually comparable data in automation projects.
• Establishes best practices and definitions for extending and refining References for new application domains.

Intended Implementers

• OPC UA companion specification authors
• System architects creating large, complex digital twins
• MES and SCADA integration specialists

Business & Operational Benefits

Consistent use of these ReferenceTypes makes information models interoperable, discoverable, and easier to maintain — critical for safety, audit support, and knowledge transfer.

Distinguishing Features

• Standardizes what constitutes ‘real-world’ interconnections between devices, processes, and applications
• Facilitates model-based system engineering and automated reasoning

Key highlights:

• Comprehensive set of domain-specific relationship semantics
• Enables advanced navigation and automation in address spaces
• Simplifies compliance and validation in system integration

Access the full standard:View EN IEC 62541-23:2026 on iTeh Standards

EN IEC 62541-24:2026 - OPC Unified Architecture – Part 24: Scheduler

OPC Unified Architecture – Part 24: Scheduler

This standard introduces a detailed information model for time-based scheduling of server actions, such as variable writes and method invocations, supporting daily, weekly, and exception-based event planning.

Core Features and Specifications

• Allows definition and management of schedules that dictate when actions are executed by an OPC UA server, incorporating public holiday calendars and special event periods.
• Supports manipulation of schedules by clients (e.g., adding/removing dates, setting recurring events, adjusting priorities).
• Provides granular context for schedule-driven automation (for instance, batch processing, maintenance alerts, or access control changes).
• ObjectTypes like CalendarType and ScheduleType outline the data structure for reliable operation.

Applicability

• Industrial automation suppliers
• Process engineers implementing shift/release changes
• System operators looking for digital scheduling solutions inside OPC UA frameworks

Strategic Advantages

By integrating scheduling into the information model, manufacturers achieve more reliable, auditable, and adaptable automation scenarios, significantly improving process reliability and workforce management.

Notable Functions

• Accurate modeling of holidays and customized event lists for global operations
• Standard APIs enable client-side schedule management and dynamic adaptation

Key highlights:

• Schedules map to actions for highly flexible automation
• Calendar support for local and public holiday adaptation
• Write and method-call action support within information model

Access the full standard:View EN IEC 62541-24:2026 on iTeh Standards

Industry Impact & Compliance

The implementation of these new standards marks a decisive leap in secure, interoperable, and flexible manufacturing engineering solutions. Their adoption:

• Ensures vendor-neutral integration across digital factories
• Provides clear life cycle management and traceability for both devices and data
• Offers robust compliance paths for cybersecurity, privacy, and traceability requirements
• Sets a foundation for advanced analytics and machine learning by enabling high-quality, well-structured data flows

Compliance Considerations

• Manufacturers and integrators should review the effective dates and plan for migration or onboarding according to the outlined requirements.
• Certification processes may be adjusted to account for new models of device onboarding and data-handling policies.
• Non-compliance could expose organizations to operational inefficiencies, security incidents, and vendor lock-in risks.

Technical Insights

The five standards share several technical hallmarks and best practices relevant for modern manufacturing environments:

• Model-based configuration and automation: Each standard leverages structured OPC UA object and reference modeling to provide contextual metadata and interaction logic.
• Emphasis on security: Device onboarding, file transfer, and scheduling all incorporate security by design (authentication, audit, least privilege).
• Interoperability first: ReferenceTypes and network models reduce ambiguity between heterogeneous systems.
• Extensibility and future readiness: All models are prepared for the integration of next-generation technologies, like TSN or companion specs.
• Testability and certification: Standardized method signatures and data types facilitate automated conformance testing and third-party certification.

Implementation Best Practices

1. Assess legacy system compatibility and plan phased rollouts to mitigate downtime.
2. Leverage supplier support for integration packs and certified reference implementations.
3. Maintain comprehensive documentation for traceability and compliance audits.
4. Monitor standard updates via platforms like iTeh Standards for timely adoption.

Conclusion / Next Steps

The February 2026 standards updates for manufacturing engineering—especially around OPC UA—usher in new levels of integration, security, and operational efficiency for industrial environments. Ensuring compliance not only fulfills emerging requirements but delivers strategic business benefits, from cybersecurity resiliency to enhanced automation and data-driven decision making.

Recommendations:

• Download and review the full text of relevant standards
• Audit your internal workflows for compliance gaps
• Train engineering and IT staff on updated OPC UA models
• Engage with your technology providers on timelines for supporting these new standards

Explore all new manufacturing engineering standards or set up alerts for future updates at iTeh Standards. Stay current, stay compliant, and unlock your factory’s digital potential.