OPC Unified Architecture (OPC UA). There is an ongoing working group in place focused on improvements based on feedback from end users. • Part 5: System management : Since a process automa - tion system must control multiple management functions (such as hardware, operating systems, platform software, applications, and networks) using a common interface, the scope of this section is extensive. Initially, it concentrated on hardware but has since grown to cover other system management functions. Work has continued on refining and expanding the stand - ard, with Version 2.0 released in 2020 and Version 2.1 in 2021. Two additional more sections cover extensive areas: • Part 6.1: Information and exchange models : Overview and interfaces using OPC UA. • Part 6.2: Information and exchange models : Basic con - figuration using OPC UA’s information model. • Part 6.3: Information and exchange models : Alarm and events configuration using IEC 62682 (ISA-18.2). • Part 6.4: Information and exchange models : Function blocks. • Part 6.5: Information and exchange models : IEC 61499 event-based programming. • Part 6.6: Information and exchange models : IEC 61131-3 on how to open function blocks. • Part 7: Physical platforms . Two more sections are under development and will be released with future versions: • Part 8: Portability : This provides mechanisms for software
applications to be moved from one application or platform to another without the need to perform extensive rewrites. The Margo initiative will likely be part of this to support interoper - ability of edge applications, workloads, and devices. • Part 9: Orchestration : This concept ties many elements together, allowing the system to model internal tasks, so automated functions can be improved. Third-party plat - forms, such as Red Hat and Tricentis Tosca, may be incor - porated to meet the requirements. Adding these capabilities to O-PAS is a major undertaking. Certification of hardware and software under the standard follows the Open Process Automation (OPA) Certification Policy (see Figure 3 ) performed by multiple O-PAS Verification Labs, applying profiles under the standard: • Security: Part 2, SEC-F-001. • Connectivity: Part 4, OCF-001/002, NET-001/002. • System management: Part 5, OSM-001/002/003. • Physical platform: Part 7, DCP-001. Operational architecture A common information model at each device/workload is fundamental for O-PAS. In an OPA system (see Figure 4 ), applications can run natively or containerised on distrib - uted control nodes (DCNs), and they communicate over the O-PAS OCF. This provides a secure, standardised intercon - nection among software functions. Based on OPC UA, OCF provides protected, standards-based, reliable data transport. The basic O-PAS building block is the DCN. It is a scalable controller, I/O or gateway device that can execute I/O and
WASH MORE. ENTRAIN LESS. Take your VDU to the next level.
The next generation of wash nozzle is here.
Introducing the SMDmax ™.
42% larger maximum free passage ††
30-60% larger droplet size † ††
300% less entrainment † ††
† when tested with water †† when compared to traditional maximum free passage style nozzles
Don’t wait for your next turnaround: www.lechlerusa.com/SMDmax
15
PTQ Q2 2026
www.digitalrefining.com
Powered by FlippingBook