EP02: What is OPA? Part 1

EPISODE DESCRIPTION - Ready to publish USB-C changed the consumer world by making one standard actually work. What if OT could do the same? In this kickoff to a multi-part OPA series, Jarie, Andrew, and David break down why open process automation could be the long-overdue “USB for OT” - and why that matters for every plant still trapped in proprietary lock-in.Jarie sets the stage for the series, Andrew explains what OPA really is, and David brings the hard-won historical perspective, showing how automation got here and why the old model is no longer enough. Together they make the case for a standards-based, interoperable, secure automation architecture that lets you upgrade and integrate systems without tearing everything apart.You’ll discover: Why OPA is best understood as a “standard of standards” How OPAST, OPAF, and the Open Group fit together Why certification and compliance are becoming non-negotiable in OT What USB-C, TCP/IP, fire hydrants, and safety systems have in common with industrial automation How interoperability and interchangeability reduce costly engineering workarounds David shares what it was like when vendors couldn’t even agree on basic protocols, and how the industry’s “bag of adapters” mentality has kept plants dependent on patching, mapping, and proprietary fixes for decades. Andrew and Jarie keep bringing it back to the real-world payoff: easier upgrades, better choices in hardware and software, and systems that can evolve without ripping and replacing everything when one component disappears.If you work in automation, controls, operations, or industrial cybersecurity, this episode makes the case for why standards are no longer a nice-to-have - they’re the foundation for safer, more flexible, more future-proof systems. It’s a sharp, practical, and surprisingly relatable conversation about why OT needs the same level of plug-and-play sanity the rest of technology already enjoys.Perfect listening if you’ve ever had to make incompatible systems talk, fight through vendor lock-in, or justify why “that’s just how we’ve always done it” is no longer a valid answer.