01
OT and IT do not agree
The floor is deterministic and often isolated by policy; the cloud is neither. Most of the risk lives at that boundary.
ThinkDebug
Practical deep dives on software architecture, AI systems, and scaling digital products - drawn from the work we ship.
ERP, MES and shop-floor telemetry connected to the systems that already run the plant.
We build the software layer above the shop floor: MES and production tracking, machine telemetry and OEE, quality and traceability, and the integrations that connect all of it to the ERP the business actually plans with.
Manufacturing software sits between two worlds that do not agree. Operational technology on the floor is deterministic, long-lived and often air-gapped by policy. IT above it wants cloud, continuous delivery and open APIs. Most projects fail at that boundary rather than in either domain.
The other reality is that a line does not stop for a deployment. Uptime expectations on the floor are measured against production schedules, so releases, migrations and failure modes all have to be designed around a factory that is running.
The constraints that shape every build in this sector, and the ones teams usually meet too late.
The floor is deterministic and often isolated by policy; the cloud is neither. Most of the risk lives at that boundary.
Deployments, migrations and failures all have to be designed around production that is already running.
OPC UA, Modbus and vendor-specific formats, often from equipment older than the network it is now attached to.
Continuous sensor data becomes the largest storage cost quickly, and most of it is only interesting in aggregate.
For regulated goods you must show which batch, which machine, which operator - years after the fact.
Gloves, glare, noise and a shift pattern. An interface designed at a desk fails on the floor.
Swipe to read all 6
Each one is a system we have built before, not a capability we are willing to try.
Work orders, routing and shop-floor execution connected to what the ERP planned.
Ingestion from equipment with availability, performance and quality derived consistently.
Batch and genealogy records that answer a recall question years later.
Interfaces built for gloves, glare and a shift, not for a desk.
The layer between the floor and the systems that plan, cost and design.
Planned and unplanned downtime tracked well enough to act on rather than just report.
Engagements across sectors - the same team, the same standards.
Partnering with Thinkdebug to develop the Forever 52 mobile app has been a game-changer for us. They were always open to feedback, and it was clear they were as invested in our success as we were. What really sets them apart, though, is the amazing support we've received since the app launched. They’ve made sure the app continues to run smoothly and are always ready to fix any issues that come up.DMDhruv MehtaBusiness Head, Forever 52
Chosen for fit and long-term maintainability, never for novelty.
Send us the scope and we come back with an itemised estimate - no discovery fee, no obligation.
What we design and document against, from the first commit rather than the week before an audit.
Certification itself belongs to your entity and its assessor. What we provide is software built and documented so the assessment is about evidence rather than remediation.
Most of our work comes from clients we already shipped for. These are the reasons they give.
Segmentation, one-way flows and edge buffering are designed in, rather than treating the floor as though it were another cloud subnet.
Rolling deployment, backwards-compatible schemas and offline-tolerant edge software, because production does not pause for us.
Sampling, aggregation and retention are decided up front, since raw sensor data becomes the largest bill faster than anyone expects.
Batch genealogy is modelled so the question you get years later has an answer, not a reconstruction.
Large targets, high contrast, glove-friendly and readable under work lighting, tested where they will be used.
Floor and ERP reconcile against a defined source, so planning and reality stop quietly diverging.
Let's start with you.
Your information stays private. We reply within 24 hours.
Still have a question we have not answered?
Ask an engineerWhat we build for manufacturing, the work we have shipped, and what we have written about it.
