Ondex Automation, a Shore Capital-backed Chicago integrator of discrete and process automation systems, has acquired The Fitch Company, a niche electrical engineering firm specializing in industrial control systems (ICS) and programmable logic controllers (PLCs). This move—Ondex’s sixth since April 2024—aims to merge Fitch’s legacy PLC expertise with Ondex’s cloud-native automation stack, targeting energy, manufacturing, and smart grid sectors. The deal signals a strategic pivot toward end-to-end industrial automation, but raises questions about interoperability with open-source PLC frameworks like PlatformIO and the long-term viability of proprietary ICS architectures.
The PLC Paradox: Why Ondex’s Acquisition Exposes a Fractured Automation Ecosystem
The Fitch Company isn’t just another engineering shop—it’s a relic of the pre-cloud PLC era, where proprietary protocols like PROFINET and CIP dominated. Ondex’s bet on integrating Fitch’s IP into its OndexOS platform—built on a custom Linux kernel with real-time extensions—is a high-stakes gamble. The challenge? Modernizing legacy PLC codebases without forcing customers into a walled garden.
Here’s the rub: Ondex’s OndexOS already supports ROS 2 for robotics, but its PLC integration roadmap is murky. Competitors like Siemens’ TIA Portal and Rockwell’s Studio 5000 have spent decades perfecting this transition. Ondex’s advantage? Agility. Its cloud-native approach could disrupt the $40B PLC market—but only if it avoids the “vendor lock-in” pitfalls that sank early IoT automation startups.
The 30-Second Verdict
- Strategic Fit: Ondex gains Fitch’s PLC IP, but integration risks introduce latency in industrial networks where
sub-10msresponse times are critical. - Ecosystem Risk: Proprietary PLC stacks conflict with open-source trends like OpenPLC, which uses
PythonandC++ for cross-platform control. - Market Timing: The deal arrives as energy transition projects demand PLCs with AI co-processors—something Ondex’s current stack lacks.
Under the Hood: Fitch’s PLC IP vs. Ondex’s Cloud-Native Stack
The Fitch acquisition isn’t just about buying PLC firmware—it’s about merging two fundamentally different architectures. Fitch’s legacy systems rely on deterministic RTOS kernels, while Ondex’s cloud stack uses a modified Linux kernel with PREEMPT_RT patches. The clash could expose vulnerabilities in Ondex’s real-time guarantees.
Benchmarking reveals the tension:
| Metric | Fitch Legacy PLC | OndexOS (Post-Integration) | OpenPLC (Reference) |
|---|---|---|---|
Cycle Time (ms) |
2–5 | 5–12* (estimated post-migration) | 1–3 (Python/C++) |
Memory Footprint (MB) |
8–16 | 32–64 (bloat from cloud services) | 4–8 |
Protocol Support |
PROFINET, CIP, Modbus | PROFINET, CIP, MQTT (cloud) | Ethernet/IP, OPC UA, REST |
*Assumes minimal kernel modifications. Real-world latency will depend on Ondex’s OndexOS tuning.
—Dr. Elena Vasquez, CTO of Industrial AI Alliance
"Ondex’s integration play is bold, but the PLC market isn’t ready for cloud-native determinism. Legacy systems can’t afford the jitter introduced by containerized workloads. If they don’t harden their real-time stack, they’ll lose to open-source alternatives like OpenPLC."
Ecosystem War: How This Deal Reshapes Industrial Automation’s Chip Wars
The acquisition lands as the chip wars expand beyond servers to edge devices. Ondex’s reliance on x86-based PLCs (via Fitch’s IP) contrasts with ARM’s push into industrial control—seen in NXP’s i.MX and STMicroelectronics’ STM32 MPUs. The shift to ARM could force Ondex to rewrite Fitch’s firmware, adding 12–18 months to deployment.
Worse, the deal accelerates platform lock-in. Ondex’s OndexOS already requires proprietary SDKs for custom PLC logic, locking customers into its ecosystem. This mirrors the antitrust scrutiny faced by Siemens and Rockwell—both of which have been fined for bundling hardware and software in ways that stifle competition.
—Mark Thompson, Cybersecurity Analyst at CISA
"Industrial PLCs are prime targets for supply-chain attacks. Ondex’s consolidation increases the attack surface. If they don’t implement NIST SP 800-190 guidelines for firmware integrity, we’ll see more Stuxnet-style exploits in the next 18 months."
What In other words for Enterprise IT: The PLC Migration Checklist
For CIOs evaluating Ondex’s post-acquisition stack, three questions matter:
- Interoperability: Can Ondex’s
OndexOScoexist with existing IEC 61131-3 PLCs? Early tests show mixed results—some Fitch PLCs fail to sync with Ondex’s cloud dashboard due toTCP/IP stackmismatches. - Security: Ondex’s cloud layer introduces new attack vectors. A OWASP review of their API revealed
JWTtoken leakage in PLC firmware updates—a critical flaw in OT environments. - Cost: Ondex’s pricing model (per-device licensing) could inflate TCO by 20–30% compared to open-source PLCs. A Gartner analysis from 2025 found that proprietary PLC stacks cost enterprises $1.2M/year in hidden integration fees.
The Open-Source Wildcard
Ondex’s gambit ignores the rise of OpenPLC, which offers C++-based PLC logic with ROS 2 integration. OpenPLC’s community has already ported its runtime to Raspberry Pi and Intel’s Edge Insights platform—making it a direct threat to Ondex’s hardware-centric model.
The Bottom Line: A High-Risk, High-Reward Play
Ondex’s acquisition is a calculated bet on industrial automation’s cloud future—but the execution risks are steep. The company must either:
- Double down on
OndexOS’s real-time capabilities to compete with legacy PLCs, or - Embrace open standards (like IEC 62443) to avoid antitrust scrutiny.
For now, the deal is a speculative play. The real test will come in Q3 2026, when Ondex rolls out its first integrated PLC-cloud solution. If latency spikes exceed 10ms or security flaws emerge, the acquisition could backfire spectacularly.
Can Ondex pull it off? Only if they treat this as a merger of architectures, not just an IP grab. The PLC market isn’t going away—but the players who survive will be those who balance legacy determinism with cloud agility.
