The Materialization of Emerging Technologies In the Structural Disruption of Process Automation

The global industrial sector is currently undergoing a series of transformations, marked by the transition from proprietary and monolithic control architectures to open, interoperable, and software-defined systems. At the heart of this metamorphosis is the Open Process Automation Standard (O-PAS), an initiative that not only challenges standards established more than five decades ago but also proposes a redefinition of the operational infrastructure of process industries. This report analyzes the strategic framework of O-PAS, its practical implementation in the field, the dynamism of the supplier ecosystem, the governance mechanisms, and, fundamentally, provides a critical assessment of the nature of this evolution.

Strategic Framework: Overcoming the Purdue Model and Ending Lock-in

Since the 1970s, industrial automation has been governed by the Purdue Model, a rigid hierarchy that isolates control functions into layers, often proprietary, resulting in the phenomenon known as " vendor lock-in ." In this scenario, the asset owner becomes dependent on a single supplier for hardware, software, and maintenance services, which limits innovation and increases lifecycle costs. O-PAS emerges as a strategic response to these inefficiencies, spearheaded by the Open Process Automation Forum (OPAF), a division of The Open Group that today has more than 100 member companies, including giants such as ExxonMobil, Saudi Aramco, Shell, and Petrobras, among others.

The O-PAS strategic vision is based on creating a "standard of standards," leveraging existing technologies such as OPC UA for connectivity, IEC 61131-3 and IEC 61499 for control logic, and ISA/IEC 62443 for cybersecurity. The central objective is to enable the development of "purpose-fitted" systems, composed of cohesive functional elements acquired from independent vendors and integrated in a modular way. This approach breaks down the barrier that prevented the reuse of control applications across different systems, reducing the complexity of upgrades and allowing for the agile infusion of new technologies, such as artificial intelligence and edge computing.

Evolution and Development Timeline of the Standard

The development of the O-PAS standard has been an iterative process, focused on progressive layers of functionality. Currently, the standard has reached a level of maturity that allows for the certification of real products and the execution of large-scale interoperability tests. The work of OPAF, subdivided into its working groups, has been developing the O-PAS standard based on versions, each addressing a series of requirements, in order to reach a level of maturity sufficient for use in real plants. The versions of the standard already released or about to be released, along with their scopes, can be seen in the table below.

The transition to Version 3.0 is particularly significant because it introduces the ability to move entire applications between different systems, based on system orchestration or management, regardless of the hardware vendor, ensuring that the control software has a lifespan that can exceed 30 years, even if the underlying hardware is periodically replaced.

Reference Architecture and the Distributed Control Node (DCN) Concept

The most profound structural innovation of O-PAS is the flattening of the traditional automation pyramid. By eliminating Purdue's rigid hierarchy, O-PAS ensures that data is available to any user or application with minimal overhead. The central component of this new architecture is the Distributed Control Node (DCN), which acts as the edge device, performing the control functions.

A DCN can be a physical or virtual device, varying in size and computational capacity. What differentiates it from a traditional PLC or DCS controller is the decoupling between the control software and the hardware platform. This separation allows for interchangeability: if a DCN fails, it can be replaced with another certified component from a different vendor, and the same control application can be downloaded and put into operation immediately.

Multi-vendor and multi-DCNs O-PAS architecture

Comparison of Density and Redundancy in DCN Architecture

Unlike traditional controllers that often manage hundreds or thousands of I/O points, O-PAS offers flexibility in point density per node, which directly impacts system availability. This means that the same component (DCN) can be used for anything from a few simple controls to large numbers of complex controls, limited only by the computational capacity of that DCN.

Support for 1:N redundancy is a transformative feature of O-PAS. Instead of requiring identical standby hardware for each active controller, a single high-availability computing platform can serve as backup for multiple computes or I/O nodes, optimizing hardware costs and physical cabinet space. Furthermore, the use of Linux-based operating systems and orchestration technologies allows for updates and security patches without requiring reboots or interrupting the process, a critical advancement for operational continuity.

Field Reality: Pilots, Testbeds , and Total Cost of Ownership (TCO) Results

The migration of O-PAS from a technical specification to an industrial reality is evidenced by field projects and testbeds operated by the largest companies in the sector. ExxonMobil has been one of the most advanced end-users in the process, progressing from an initial testbed to field testing in real plant processes. These results have spurred the community, with other large participating companies planning to expand their systems (such as Reliance in India and Petronas in Malaysia), in addition to Petrobras itself initiating a project for real-world application and validation of the technology. These pilots aim not only to test functionality but also to validate the economic viability of the open model.

Cost Results and Operational Efficiency

A study conducted by the integrator Wood PLC (USA) – available in the “ Common Questions ” section at https://www.woodplc.com/solutions/expertise/open-process-automation – demonstrated that the implementation of OPA ( Open Process Automation ) based architectures can reduce TCO by up to 53%, a reduction driven by several factors that go beyond the initial cost of hardware acquisition:

• Reduced CAPEX: The ability to use COTS (Commercial Off-the-Shelf) components and competition among hardware vendors reduces the prices paid for proprietary devices;
• OPEX Optimization: Hardware/software decoupling allows for computing technology upgrades in 5-7 year cycles without the need for expensive and risky software migrations, which traditionally occur every 20 years;
• Maintenance and Obsolescence: The ease of replacing individual components and granular obsolescence management prevent the catastrophic disruptions associated with the end of support for entire legacy systems;
• Seamless updates: the portable and modular nature of O-PAS applications allows component updates to be made to plant infrastructure without downtime, as the system can remain operational simply by changing the DCN responsible for the application.

Migration Strategies and Gradual Learning

Field experience shows that O-PAS does not require an "all or nothing" approach. On the contrary, the recommendation for end users has been to migrate small units or isolated PLCs to gain operational experience. This modular approach allows automation teams to retrain and adjust their support processes without the risks of an immediate large-scale migration. Initial projects have focused on scales of 100 to 10,000 I/O points to prove system stability before application in plants with 100,000 points or more.

Supplier Ecosystem: The Dance Between Giants and Newcomers

The O-PAS supplier ecosystem comprises a dynamic mix of traditional DCS manufacturers, information technology (IT) companies, industrial communications specialists, and systems integrators. This diversity is essential to the standard's success, but it also creates significant competitive tensions.

The heterogeneity of roles within the O-PAS architecture demonstrates that market openness is not just a trend, but a necessity for innovation. The standard reduces barriers to entry, allowing hardware, software, or service providers to contribute independently. In this scenario, the Systems Integrator assumes a central role, acting as the orchestrator capable of unifying components from multiple vendors through the interfaces standardized by the norm.

Governance and the Certification Program

The governance of O-PAS is exercised by The Open Group, ensuring that the standard remains neutral and independent of any specific vendor. The certification program is one of the pillars that sustains end-user confidence, ensuring that products truly deliver the promised interoperability. Another essential pillar, and even more important than certification at first, is constituted by interoperability tests (or IOPs). These tests take place semi-annually and aim to bring O-PAS solution developers face-to-face, with the objective of testing the real interoperability of their applications, which contributes to increasing the range of systems tested and the detection of improvements to be made.

Compliance Framework and Certification Profiles

Certification is based on "Profiles," which are logical sets of compliance requirements for specific system functions. Each product must undergo verification in recognized independent laboratories (Recognized Verification Labs) before receiving the O-PAS seal. Some of the profiles present in the standard are:

In August 2024, the ISASecure program was selected as the exclusive provider for verifying cybersecurity requirements in the O-PAS, integrating ISA/IEC 62443 certification directly into the standard's compliance workflow. This strategic decision simplifies the process for vendors and increases assurance for end users that multi-vendor systems are free of critical security vulnerabilities.

O-PAS in Synergy with MTP and NOA: The Trinity of Industry 4.0

One of the biggest strategic points of uncertainty for automation managers is how O-PAS relates to Module Type Package (MTP) and NAMUR Open Architecture (NOA). Although often seen as competitors, they actually form a complementary ecosystem for the future viability of the process industry.

• Module Type Package (MTP): Focuses on the modularization of process units (Package Units). It provides a functional and hardware-agnostic description so that a module (e.g., a centrifuge) can be quickly integrated into a higher-level orchestration system (POL - Process Orchestration Layer). MTP reduces engineering effort by up to 70% and time to market by 50%. O-PAS can serve as the control infrastructure where these MTP modules are connected and orchestrated.
• NAMUR Open Architecture (NOA): Solves the problem of "stranded data" in legacy systems. NOA creates a secure second data channel for monitoring and optimization (M+O) without interfering with central process control. O-PAS, being inherently open, facilitates NOA implementation by providing an infrastructure that already natively supports access to large-scale diagnostic and maintenance data.

While MTP focuses on " Plug & Produce " for physical modularity and NOA focuses on data extraction for advanced analytics, O-PAS focuses on opening up the central control architecture itself, replacing the proprietary DCS.

Structural Leap in Automation Architectures: The Democratization of Innovation

The central objective of O-PAS is to be the necessary catalyst for the process industry to take advantage of modern digital technologies. The structural leap manifests itself in:

1. Independent Innovation Cycles: Allows software innovation (e.g., new AI algorithms for predictive control) to not be limited by the 20-year hardware cycles of DCS vendors;
2. Capital Efficiency: Reduces TCO by allowing capital budgets to be focused on process improvements instead of simply replacing obsolete hardware "with new hardware of the same type";
3. Intrinsic Safety: By adopting the " secure by design " model and the ISA/IEC 62443 standard from the outset, O-PAS offers a much more robust security posture than legacy systems that relied solely on physical " air gaps ";
4. Superior Diagnostics (Redfish): Unlike legacy systems, where each vendor has proprietary logs, O-PAS uses the Redfish DMTF standard for hardware management. This means that diagnostics are unified: the orchestrator receives the same type of DCN alerts from any manufacturer, allowing for systemic visibility that closed systems never had.
5. Anti-Lock-in: By relying on global standards widely adopted by the IT and Automation industry, O-PAS eliminates the risk of creating a " lock-in " of complexity. Implementation requires no "magic," only adherence to standards that... Automation engineers or systems administrators should be familiar with this;
6. Orchestration as a Cost Reducer: The complexity of manual integration is mitigated by orchestration. O-PAS allows for automated software deployment and hardware configuration (similar to Kubernetes in IT). What previously required "huge teams" is now managed by software, allowing the engineering team to focus on process optimization, not on "running cables" or manually configuring IP addresses.

Financial Justification for the CFO: Beyond Bits and Bytes

For O-PAS to move from engineering testbeds to corporate budgets, automation leaders must translate the technical benefits into financial language that the CFO (Chief Financial Officer) understands, as the pressure for ROI (Return on Investment) in compliance and resilience has never been higher.

"Forecast Accuracy " is also improved, as the modularity of O-PAS allows for more linear scalability than traditional systems, where adding new control points often required purchasing entire underutilized controllers or expensive rack expansions.

Looking to the Future: The Challenges of O-PAS as the Ultimate Technology

Industrial automation systems have existed for about five decades, with continuous and increasingly accelerated technological evolution. However, the industrial market is conservative, which has led to the current characterization of systems: robustness and operational continuity are sought, even at the expense of adopting more complete, optimized, and modern technologies.

The pursuit of standardization is a constant requirement for end users, in order to gain control of their industrial plant, something that has already been achieved to some extent with the development of fieldbus communication protocols and systems integration (OPC). However, this standardization is lost when the information flow is blocked at the control layer, protected by proprietary hardware and software, where only a small standardized integration layer is available. One of the mottos of O-PAS technology is precisely to provide an open, secure, and interoperable process automation architecture.

However, like other automation technologies that emerged bringing numerous benefits to users but nevertheless lost momentum in adoption, O-PAS faces challenges in establishing itself as a definitive technology to be found in industrial plants worldwide:

1. Standard Consolidation: O-PAS is based on so-called quality attributes, a series of "desires" that a user of a process automation system would like to have available in their system, such as: security, modularity, portability, interchangeability, etc. The O-PAS standard brings together the most consolidated standards on the market for each of these attributes, in order to be "the standard of standards," but it is still under development for some of them. The release of version 3.0 of the standard should close some of these missing requirements, consolidating aspects not yet visible to the community;
2. Market participation: the forum responsible for discussions about the standard still has few solution developers, regardless of the solution type (hardware, software, service). Greater participation from large automation companies, software development centers, and academia could accelerate the completion of the standard and the development of more solutions. Similarly, a greater presence of end users should act as an incentive for developers to invest in the technology, making it mandatory in their projects.
3. Awareness and technical training of teams: with the theme of IT/OT convergence, Industry 4.0 and digitalization, engineering teams have been visualizing their systems "outside the PLC/DCS box," and gaining more knowledge of these emerging technologies, but in an isolated way. The continuity of this training, with awareness of the combined strength of these technologies, will increase the interest of end users in adopting the standard;
4. Dissemination: Even with the amount of news and research on the subject being published (and at the speed that it is published), there is still a lack of knowledge among end users about O-PAS, not only regarding the more intrinsic aspects, but also the basic capabilities that the technology can enable. Therefore, OPAF participants (manufacturers and end users) have been working to disseminate the concepts and expected (and perhaps not yet achieved) results of adopting O-PAS.

Conclusions and Strategic Recommendations

O-PAS is not just a new technical standard; it's a new business model for industrial automation. By 2026, it positions itself as a robust response to the technological stagnation caused by decades of proprietary hegemony. However, its implementation requires a profound cultural and organizational shift.

The conclusion of this report is that O-PAS represents an indispensable structural leap, but one that brings with it some challenges already faced by any disruptive technology introduced into the industrial automation environment. The benefit of interoperability and reduced TCO is real and measurable, but it requires the end user to assume a more active role in the technical governance of their systems. The risk of complexity only becomes a trap if the company tries to treat O-PAS with the same "buy and forget" mentality applied to traditional DCSs.

Ultimately, the success of O-PAS in the near future will depend on the ability of the supplier ecosystem to simplify the end-user experience by providing orchestration and diagnostic tools that manage the inherent complexity of an open system. For industries seeking leadership in the age of Artificial Intelligence and operational sustainability, the risk of controlled complexity in O-PAS is significantly lower than the risk of guaranteed stagnation in closed systems.

Adriano Marcelo Corteze – Marketing  
Octávio Paschoal – R&D 
Victor Teixeira C. Halfeld – R&D  
Nova Smar S/A  
06/FEB/2026