What Is OPA? Part 2

Show notes

This episode continues the OT Crowd mini-series on Open Process Automation, with Jarie and David digging into what OPA is meant to solve and why the standards-based approach matters. David explains the “standard of standards” idea, how OPA prioritizes interoperability, interchangeability, adequacy, portability, security, manageability, and reliability, and why those attributes matter for both plant teams and business leaders.

In this episode, Jarie and David connect the technical vision to real-world operational pain points like vendor lock-in, cybersecurity, and the constant struggle to get systems to work together. The conversation ends by framing OPA as a way to give operators, engineers, and managers more choice, more capability, and fewer reasons to say no.

Watch on YouTube. Listen on Spotify or Apple Podcasts.

Key topics

• OPA is described as a standards-based, open, secure, and interoperable architecture designed to lower lifecycle cost and improve business value.
• David explains the “standard of standards” model behind OPA, where the forum reuses proven standards instead of inventing new ones.
• Examples discussed include OPC UA for networking and interoperability, IEC 62443 for cybersecurity, IEC 61131 for control logic, IEC 61499 as a function block standard, and PA-DIM as the basis for the OPC UA data model.
• Interoperability is framed as a major automation challenge, especially when vendors struggle to get A to talk to B.
• Interchangeability is compared to everyday standardized parts like fuses and bolts, highlighting the value of being able to replace components without redesigning the system.
• Adequacy is defined as equal or better replacement capability, especially when the exact make and model is unavailable.
• Portability is presented as a major end-user benefit, reducing the need to rewrite or recreate code when moving between systems.
• Security, manageability, and reliability are described as nonnegotiable foundational attributes for any automation system.
• Jarie and David emphasize the growing urgency of cybersecurity, especially with increasing breaches and the accelerating threat landscape.
• David summarizes OPA as a way to give practitioners better tools, plant managers more flexibility, and operators a safer, less stressful way to get work done.

Timestamps

• 00:00 — Welcome to part two of the OPA mini-series
• 00:58 — The business purpose behind Open Process Automation
• 02:24 — Using existing standards instead of inventing new ones
• 03:18 — Control logic standards and the role of IEC 61131 and IEC 61499
• 04:17 — Why OPA is called a standard of standards
• 05:13 — Interoperability as one of the biggest automation challenges
• 05:42 — Interchangeability, adequacy, and why replacement parts should just work
• 06:40 — Why portability matters to end users and engineers
• 08:09 — Security, manageability, and reliability are not negotiable
• 09:02 — Why connected systems need real cybersecurity protections
• 09:26 — AI, faster vulnerability discovery, and the need for better defenses
• 10:14 — Open automation as freedom to choose and grow over time
• 11:50 — What OPA means for practitioners and plant managers
• 13:18 — No more proprietary lock-in or “you can’t put that here”
• 14:16 — Bringing advanced capabilities into the system instead of keeping them outside
• 15:14 — Helping operators succeed safely and with less hassle
• 16:18 — What’s coming next in part three

Notable quotes

“A standards based, open, secure, and interoperable architecture will allow for bringing business value and technology insertion.”

“Open process automation brings all the tools and capabilities that you’ve been asked to implement, that you’ve wanted to implement.”

“For the plant manager, the answer never has to be no anymore.”

Next: What Is OPA? Part 3.