Industry
Manufacturing software.
Manufacturing software has to talk to machines bought in 1998 and machines bought last month, and it cannot stop the line to do it. The constraint that shapes everything is that the physical process keeps running whether your service is up or not.
What shapes the architecture
Constraints that are specific to this sector.
These are the things that would be wrong or meaningless if written about a different industry. They are design inputs, not compliance paperwork added at the end.
- 01
The line does not wait for your uptime
Production continues during an outage, so events must be buffered at the edge and replayed. A system that loses an hour of production data during a deploy has lost the traceability that hour was for.
- 02
Protocols are industrial, not web
OPC-UA and Modbus, often over networks deliberately air-gapped from the internet. An on-premise gateway is not optional, and it has to degrade to local operation.
- 03
OEE is only useful if downtime is classified
Availability, performance and quality are easy to compute and useless without categorised stoppage reasons. Capturing why a machine stopped is an operator-interface problem more than a data problem.
- 04
Traceability must survive a recall
Genealogy from finished lot back to raw material batch has to be reconstructible years later, which means immutable records and retention that outlasts the current schema.
Typical work in manufacturing.
- Production monitoring and OEE dashboards
- Manufacturing execution (MES) layers
- Quality inspection and non-conformance
- Maintenance scheduling
- Inventory and material traceability
- ERP integration layers
What it has to talk to.
- OPC-UA
- Modbus TCP
- MQTT / Sparkplug B
- SAP / ERP connectors
- Barcode / RFID
Integration surfaces are where most sector projects actually fail. We treat each one as a boundary with its own translation layer, rather than letting an external format leak into the domain model.
Other sectors
Explore the rest.
Start here
Tell us the problem.
We'll be honest about the fit.
A first conversation costs nothing and is useful even if you go elsewhere — you'll leave with an architecture opinion and a realistic sense of scope.
- Reply within 24 hours
- No sales sequence