Capability blueprint — Manufacturing (MES)
Shop-Floor Execution System
CAPABILITY BLUEPRINTA reference architecture for this sector: how TEKTON would engineer the system, drawn from what our survey engine measures in estates like it. It is not a client engagement, no client is named or implied, and the interface above shows illustrative data.
THE CHALLENGE
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
01
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
02
Scheduling
- One relational schedule across sites and cells
- Drag-to-reschedule with capacity and tooling checks
- Works orders kept in step with the ERP
03
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
| 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 IT STARTS
A reference architecture, not a client engagement. Every engagement starts with a survey of the existing estate.