MESkit public website
Create production orders, generate serialized units, move them through manufacturing routes, and log quality events — all in real time.
Last updated: March 7, 2026
What Run Mode does.
Run Mode is where manufacturing happens. You create production orders that specify what to build and how many. You generate units with auto-assigned serial numbers, advance them through route steps, log quality events at inspection gates, and scrap defective units. The WIP tracker shows real-time unit distribution across workstations. Every action is recorded in unit history for full traceability.
Plan what to build.
A production order specifies a part number, a route, and a quantity to produce. Orders appear in the left panel of Run Mode with status badges.
| Status | Meaning | Transitions to |
|---|---|---|
| new | Order created, not started | scheduled, running, closed |
| scheduled | Planned for production | running, closed |
| running | Units being produced | complete, closed |
| complete | All units produced | closed |
| closed | Finalized | (none) |
Order numbers are auto-assigned as PO-0001, PO-0002, etc. When all units complete their route, the order automatically transitions to complete.
Create serialized units for production.
Click Generate Units on a production order to create a batch of units. Each unit receives an auto-assigned serial number from the part number's serial algorithm (configured in Configure Mode).
Units start at step 0 (not yet entered the route). Their status is in_progress until they either complete the route or are scrapped.
Via chat: "Generate 10 units for PO-0001".
Advance WIP through the route.
Each unit follows the route steps defined in Configure Mode. Move advances a unit to its next step, records the completed step in unit history, and updates the unit's current position.
When a unit completes the last route step, it is automatically marked as completed and the production order's completion count increments.
Via chat: "Move SMX-00042 to the next step".
Inspect units at checkpoints.
Route steps marked as pass/fail gates in Configure Mode require explicit quality decisions. At a gate, the unit cannot advance until an operator passes or fails it.
Quality events are logged with type (inspection, rework, scrap), result (pass/fail), and optional defect code and notes. These events feed the Quality Monitor and yield analytics.
Test definitions allow measurable inspections — e.g., "Torque: 45–55 Nm". Recording a measured value auto-evaluates pass/fail against the limits and creates a quality event.
Via chat: "Record torque reading 52 Nm for SMX-00038".
Remove defective units from production.
Scrapping a unit marks it as scrapped, records a fail in unit history, and creates a scrap quality event. The unit stops moving through the route.
The Operator Assistant asks for confirmation before scrapping.
Via chat: "Scrap SMX-00015 — failed solder inspection".
Real-time unit distribution.
The right panel of Run Mode shows WIP (Work In Progress) — how many units are at each workstation right now. This view updates in real time via Supabase Realtime as units move, complete, or get scrapped.
Via chat: "How many units are at Station 2?" or "What is the current WIP status?".
Quick reference.
A production order specifies how many units of a part number to produce using a specific route. Orders follow a lifecycle: new → scheduled → running → complete → closed. Order numbers are auto-assigned as PO-0001, PO-0002, etc.
When you generate units, MESkit reads the serial algorithm configured for the part number in Configure Mode. It atomically increments the counter and generates serials like SMX-00001, SMX-00002 using the configured prefix and digit count.
When a unit reaches a route step marked as a pass/fail gate, it cannot advance automatically. An operator (or the Simulator) must explicitly pass or fail the unit. Failing a unit at a gate allows scrapping or rework.
Yes. The Simulator runs in the background via the top bar controls. You can manually create orders and move units while the simulation is active — both use the same tool layer.
WIP (Work In Progress) refers to units currently on the shop floor that have started but not yet completed their route. The WIP tracker shows how many units are at each workstation in real time.