Ariox

05/29/2026

Rodney Fullmer published Part 2 of the OT/IT Integration Series this week.

The article covers the business model reason the major iPaaS platforms — Boomi, MuleSoft, Workato, Informatica — consistently decline to solve OT device connectivity.

The short version: their economics require building once and selling to thousands of customers. OT device integration can't be built once. Every deployment is different. The model breaks.

So they call it "out of scope." Rationally.

The article explains the full picture — including what the right category of solution looks like.

Part 2 of 3. Link in the first comment.

05/25/2026

Manufacturers have spent the last decade modernizing.

ERP systems upgraded, WMS platforms implemented, analytics tools deployed, cloud migrations completed. Seventy percent of them still enter operational data manually.

That's a symptom, not a contradiction.

The modernization wave addressed the enterprise systems layer. The factory floor device layer — the origin point of the actual operational data — was treated as someone else's problem. Device vendors owned a piece. Middleware tools owned a piece. IT contractors owned a piece. Nobody owned the whole connection.

So the rest of the stack modernized around the gap. The ERP got better. The analytics got smarter. The data feeding both stayed manual.

The integration layer survived modernization intact. The question is why.

Link to our breakdown in the comments.

05/18/2026

Siemens publishes an annual report on the cost of unplanned downtime.
The 2024 number: $1.4 trillion. Annually. Across the world's 500 largest manufacturers. Equivalent to 11% of their revenues.
That's unfortunately a structural condition that the industry has adapted to.
The average large plant now loses $129 million annually to downtime, up 65% since 2019. The per-incident cost has risen because labor costs more, materials cost more, and supply chains operating at higher capacity have less slack to absorb a stoppage.
The technology to reduce this significantly has existed for years. Real-time device data, fed into predictive maintenance systems, consistently reduces unplanned downtime by 35–50%.
The integration layer is what turns potential into practice. Device data that doesn't flow into analytics systems can't trigger predictive interventions.
Here's the link to our OT/IT Integration Cost Calculator:

05/04/2026

McKinsey studied why Industry 4.0 initiatives stall.
70% of pilots demonstrate value at small scale. 70% of those same pilots fail to reach full deployment.
The failure point is almost never the technology at the top or the bottom of the stack. ERP systems work. Advanced analytics platforms work. The devices on the floor generate data reliably.
The failure is in the middle. The integration layer that should connect shop floor devices to enterprise systems — the layer every vendor treats as someone else's problem.
McKinsey called it "the last-mile IT/OT problem."
The manufacturer who ran a successful pilot on one line can't replicate it across five lines because the integration work multiplies — different device generations, different protocols, different ERP configurations per site. The connection that worked at small scale breaks at real scale.
This is the problem nobody owns. It's also the only one worth solving.
Link to our breakdown of why it persists in the comments.

04/27/2026

Your ERP knows everything about your business.
Except what's actually happening on your factory floor right now.
The average manufacturer loses $129 million annually to unplanned downtime. Not because the equipment fails without warning. Because the warning signals — vibration anomalies, temperature drift, cycle time deviations — live in devices that have no path to the systems that could act on them.
The ERP shows what was planned. The floor shows what's happening.
Every shift that gap widens, it compounds.
Comment "Calculator" and we'll send you a tool that puts your specific numbers to this. Takes 90 seconds.

04/22/2026

Big update for integration builders!

and OpenAI are now available as connectors inside Lumino.

That means you can bring leading directly into your integration workflows, without duct-taping APIs together or over-engineering logic outside the platform. Use them to enrich data in-flight, interpret logs, automate decisioning, or add intelligence exactly where your integrations need it.

Lumino isn’t just moving data anymore, it’s allowing your integrations to function more intelligently.

Powered by and Anthropic, embedded directly into the integration layer—where this stuff actually belongs.

04/13/2026

Maybe YOU want to turn your data security liability to a strategic advantage. Visit us at the GTS Security Summit or schedule a discovery call here: https://hubs.li/Q04bqXgQ0

Automate workflows, eliminate data silos, and scale operations with Lumino, our user-friendly platform tailored for enterprises of all sizes!

04/10/2026

04/03/2026

We built an integration cost calculator specifically for Epicor environments.

10 integration areas.
Separated labor and friction costs.
FTE-equivalent estimates.
Adjusted for your team's IT maturity.

Takes about 2 minutes.
No email required to see your results.
No sales call to get the full picture.

The only thing it asks for is honest answers about how your systems are connected today.

Link in comments.

04/02/2026

There are four stages of ERP integration maturity.
Most mid-market manufacturers are stuck at stage two.

Stage 1: Manual. Export, transform, import. Every week.
Stage 2: Point-to-point. Custom scripts connecting two systems. Works until the third system arrives.
Stage 3: Platform. A dedicated integration layer that handles routing, transformation, and monitoring.
Stage 4: Automated. Self-healing connections with real-time sync and exception handling.

The jump from 2 to 3 is where most teams get stuck.
Not because they lack budget. Because the default approach (build another custom connection) keeps them at stage 2 no matter how many integrations they add.

We wrote a playbook about this exact problem.

Link in comments.