EP05: What is OPA? Part 4

Most people think standards slow innovation down. Open Process Automation proves the opposite - if you get the architecture, cybersecurity, manageability, and conformance model right, interoperability gets easier and proprietary lock-in starts to disappear. Jarie Bolander and David DeBari break down part four of their five-part OPA series, unpacking how the Open Process Automation Forum defines the OPAS specification and why it’s built as a “standard of standards.” They explain the minimum requirements that make a modern automation system actually work across vendors, from IEC 62443 cybersecurity and SL2 protection to Redfish diagnostics, OPC UA communications, and the move toward application portability and orchestration. You'll discover: Why OPA deliberately adopts existing standards instead of inventing new ones How IEC 62443, Redfish, OPC UA, IEC 61131-3, and IEC 61499 fit into the architecture Why value, timestamp, quality, engineering range, and engineering units matter for real-world troubleshooting How conformance testing prevents “open” systems from being open in name only Why third-party certification is essential for true interoperability and vendor trust David also explains the practical pain points that OPA is trying to solve, from scaling errors and unit mismatches to proprietary connectors and one-port hardware that makes redundancy impossible. The result is a clearer picture of how the forum balances innovation with just enough structure to make systems portable, diagnosable, and secure. If you work in automation, industrial control, OT, or industrial software, this episode gives you the framework behind the standard and the reason compliance is the foundation for everything that comes next. Essential listening if you want to understand where OPA is headed and why part five matters.