<![CDATA[The OT Crowd]]>Break room talk, not a briefing.

Proprietary automation economics are hitting a wall. Closed control systems lock plants into one vendor's roadmap, pricing, and upgrade cycle, and every modernization turns into a rip-and-replace bet. Open Process Automation (OPA) changes the math. It decouples hardware, software, and lifecycles so plants can upgrade piece by piece, mix vendors, and own their architecture. The OT Crowd digs into what that means for the plant floor, the budget, and everyone who builds, sells, and runs these systems.

Jarie asks the questions you're thinking. David and Andrew tell you what's really going on. David is the OT veteran who has seen the field cycles, the vendor lock-in, and the migration that almost went sideways. Andrew co-chaired the Open Process Automation Forum's Technical Working Group and came up on the I/O vendor side, so he knows how O-PAS gets written (and argued over) and what it takes to ship into an open stack.

Each episode brings in operators, integrators, and standards people to dig into open control, O-PAS, plant-floor problems, and how the industry markets and sells it all.

No hype. No brochure. Just honest conversation worth your commute.

New here? Start with our five-part series, What Is OPA?, which covers why OPA matters, what it is (and isn't), and how the architecture works.

Think you can stump us? Send your question at theotcrowd.com/stump-the-hosts

A CPLANE production.

]]>https://theotcrowd.com/Riverside.fm (https://riverside.com)Mon, 05 Oct 2026 18:52:26 GMTSun, 27 Sep 2026 15:26:44 GMT60Jarie Bolander, David DeBari, & Andrew Vanderpool<p>Break room talk, not a briefing.</p><p>Proprietary automation economics are hitting a wall. Closed control systems lock plants into one vendor's roadmap, pricing, and upgrade cycle, and every modernization turns into a rip-and-replace bet. Open Process Automation (OPA) changes the math. It decouples hardware, software, and lifecycles so plants can upgrade piece by piece, mix vendors, and own their architecture. The OT Crowd digs into what that means for the plant floor, the budget, and everyone who builds, sells, and runs these systems.</p><p>Jarie asks the questions you're thinking. David and Andrew tell you what's really going on. David is the OT veteran who has seen the field cycles, the vendor lock-in, and the migration that almost went sideways. Andrew co-chaired the Open Process Automation Forum's Technical Working Group and came up on the I/O vendor side, so he knows how O-PAS gets written (and argued over) and what it takes to ship into an open stack.</p><p>Each episode brings in operators, integrators, and standards people to dig into open control, O-PAS, plant-floor problems, and how the industry markets and sells it all.</p><p>No hype. No brochure. Just honest conversation worth your commute.</p><p>New here? Start with our five-part series, What Is OPA?, which covers why OPA matters, what it is (and isn't), and how the architecture works.</p><p>Think you can stump us? Send your question at theotcrowd.com/stump-the-hosts</p><p>A CPLANE production.</p>episodicJarie Bolander, David DeBari, & Andrew Vanderpooljarie.bolander@cplaneai.comno<![CDATA[E01: Introducing The OT Crowd]]>Meet the crowd. Jarie asks the questions you're thinking (and learns out loud). David is the OT veteran who has seen the alarm floods, the vendor lock-in, and the migration that almost went sideways (and knows a thing or two about O-PAS). Andrew co-chaired OPAF's Technical Working Group and came up on the I/O vendor side, so he knows how O-PAS gets written (and argued over).

In this first episode, they explain why the show exists: break-room talk about industrial automation, not another vendor keynote. They walk through the format, starting with the five-part What Is OPA? series, followed by guest episodes with operators, integrators, and standards people. They also cover what the show will (and won't) cover.

]]>3a5fa13e-1fc7-447c-9ff3-dc33f5f16ed0Mon, 28 Sep 2026 19:32:29 GMT<p>Meet the crowd. Jarie asks the questions you're thinking (and learns out loud). David is the OT veteran who has seen the alarm floods, the vendor lock-in, and the migration that almost went sideways (and knows a thing or two about O-PAS). Andrew co-chaired OPAF's Technical Working Group and came up on the I/O vendor side, so he knows how O-PAS gets written (and argued over).</p><p>In this first episode, they explain why the show exists: break-room talk about industrial automation, not another vendor keynote. They walk through the format, starting with the five-part <i><em>What Is OPA?</em></i> series, followed by guest episodes with operators, integrators, and standards people. They also cover what the show will (and won't) cover.</p>no00:21:251E01: Introducing The OT Crowdfull