Capability blueprint. Manufacturing (MES)
Shop-Floor Execution System
Reference architecture: one offline-first scheduling and CNC-uptime dashboard in place of a regional patchwork of spreadsheets and legacy screens.
Reference architecture. It shows how TEKWROUGHT would engineer a system in this sector. It is not a client engagement, and the interface shows illustrative data.
The problem
Regional plants often schedule from spreadsheets and ageing on-premises screens that disagree with each other and stop when the network does. The floor needs one schedule, live machine states and a system that keeps working offline and syncs when the line comes back.
The architecture
Machine data
- Spindle state and cycle counts from CNC controllers (MTConnect or OPC UA)
- Uptime, availability and downtime reasons per machine and shift
- Operator downtime codes captured at the machine
Scheduling
- One relational schedule across sites and cells
- Drag-to-reschedule with capacity and tooling checks
- Works orders kept in step with the ERP
On the floor
- Offline-first tablet app that queues changes and syncs
- Role-based access for planners, setters and supervisors
- Shift handover and OEE reports
Technology
| Layer | Components |
|---|---|
| Machines | MTConnect / OPC UA adapters |
| Sync | Offline-first client store with conflict-safe sync |
| Data | PostgreSQL, row-level security per site |
| Integration | ERP connectors (e.g. Epicor Kinetic REST) |
| Front end | Next.js dashboard and installable tablet app |
Where an engagement starts
A reference architecture, not a client engagement. Every engagement starts with a survey of the existing estate.
Have a system like this to modernise?
Every engagement starts with a measured survey of what you run today and a fixed fee for the work.