Open-source manufacturing ERP, MES and QMS. Quoting, MRP, inventory, shop floor, quality and lot/serial traceability on one Postgres schema, with a REST API and MCP server. Self-host or use Carbon Cloud.
TypeScript ai-agentsbill-of-materialserpinventory-managementleanmanufacturingmanufacturing-execution-systemmcp-servermesmrpopen-source-erppostgresqlproduction-planningqmsquality-management-systemreact-routerself-hostedsupabasetraceabilitytypescript
---
title: Run the floor
description: Work hits the floor; the floor reports back.
label: "(IV)"
index: 3
---
Release the <Term id="job">production job</Term> and its supporting <Term>subassembly</Term> jobs to make them available on the shop floor.
<Figure illustration="shopfloor-loop" caption="On the floor, every operation reports back: material consumed, labor logged, parts scanned." />
## The schedule
Released work appears on the MES **Schedule** board, with one Kanban column per <Term>work center</Term>. Each column lists its queued <Term id="operation">operations</Term> by dispatch priority. The Display popover controls whether empty work centers and card fields—customer, description, due date, duration, progress, status, sales order, and thumbnail—are visible. Filters limit the board by work center, process, tag, or assignee.
<Figure illustration="schedule-board" caption="The MES schedule: operations grouped into work-center columns, ordered by dispatch priority." />
<Callout tone="amber" badge="DISPLAY, NOT DISPATCH" title="On the floor the board shows the plan; it doesn't reshuffle it.">
The MES board is read-only scheduling output. Operators can filter it but cannot drag work to reschedule it. Planners change work centers, dates, and sequence on the [ERP scheduling boards](/docs/reference/scheduling).
</Callout>
<Screenshot src="/screens/floor-mes-schedule.png" label="MES schedule board" caption="Released operations queued across the work-center columns: Clean Room Bay A, CNC Mill, PCB Lab, Potting Station, and QC Bench." ratio="wide" />
## Operations & work centers
A job's <Term>routing</Term> is an ordered list of operations. Each operation specifies a process, such as Mill, Weld, Anodize, or Assemble; its work center; and separate setup, labor, and machine times for scheduling and costing.
Carbon supports two operation types:
- Inside operation: runs at one of the company's work centers.
- <Term>Outside operation</Term>: runs at a supplier and returns to continue the routing.
<Figure illustration="outside-processing" caption="An outside step leaves the floor for a supplier and raises its own PO — then rejoins the routing." />
<Callout tone="blue" badge="OUTSIDE PROCESSING" title="A supplier-run step raises its own purchase order.">
Associate the process with a supplier and mark the operation Outside. Releasing the job creates an Outside Processing PO at the supplier's rate. The operation's lead time is included in the routing schedule.
</Callout>
<Screenshot src="/screens/floor-outside-operation.png" label="Job routing with an outside operation" caption="The structural frame's routing on J000001: machining and welding in-house, then a hard-anodize step outside at AstroMill Machining." ratio="wide" />
## Work instructions
The shop-floor view presents the current revision of the operation's work instructions. Each ordered step can include a description and measurement tolerance.
<Screenshot src="/screens/floor-work-instructions.png" label="Shop-floor work instructions" caption="The step checklist for J000001's final assembly and torque operation, with the torque and squareness tolerances each step must hit." ratio="wide" />
## At the station
The MES operation screen provides **Start** and **Pause** controls and records each action against the job:
- Select a work type and use **Start** or **Pause** to open or close a <Term id="production-event">production event</Term>. **Labor** is available by default; operations with setup or machine time expose those work types in the same control.
- Select **Issue Material** to <Term id="material-issue">issue</Term> components as they are consumed.
- Use **Log Completed** for good units, **Log Scrap** with a <Term>scrap</Term> reason, or **Log <Term>Rework</Term>** for reworked units. **Complete All** reports the entire remaining quantity.
- Select **Finish** to end all active production events and set the operation to **"Done"**.
<Figure illustration="mes-station" caption="The operator's panel: Setup, Labor, and Machine time toggles, quantity logging, and Finish." />
<Callout tone="green" badge="HOURS BECOME COST" title="Every toggle and every issue lands on the job's real cost.">
Carbon prices logged hours at the work center's labor and machine rates and posts issued material at cost. These amounts contribute to the job's [actual cost](/guides/job-costing).
</Callout>
<Callout tone="neutral" badge="FINISH vs END OPERATIONS" title="Ending your shift is not the same as finishing the work.">
**Finish** closes one operation. **End Operations** in the sidebar stops all of the operator's active production events without completing their operations. When time cards are enabled, clocking out also stops the operator's labor event.
</Callout>
<Screenshot src="/screens/floor-mes-operation.png" label="MES operation screen" caption="An operator on J000001's 'Machine structural panels' operation at the CNC Mill: the Labor work type, quantities, and the material list." ratio="wide" />
## Backflush & issue
Carbon consumes tracked and non-tracked bill-of-material components differently:
- Issued: operators explicitly issue tracked material when it is consumed, recording its serial or batch identity against the operation. Picking is separate: it transfers material from a warehouse shelf to the lineside shelf without consuming it.
- <Term id="backflush">Backflushed</Term>: Carbon automatically consumes non-tracked material when the operation or job reports completion.
Picked material that remains unconsumed returns to its warehouse source when the operation or job completes, according to the company's inventory setting.
<Callout tone="green" badge="BACKFLUSH" title="The everyday consumables update themselves as the floor builds.">
When an operation reports completion, Carbon removes backflushed material from stock and posts [its cost to the job](/guides/job-costing). Tracked parts remain explicitly issued.
</Callout>
## Scan & trace
Operators scan tracked parts during production. Carbon represents each serial, batch, or lot as a <Term>tracked entity</Term>. Scanning a component into a parent unit records a [tracked activity](/docs/reference/traceability), marks the component consumed, marks the parent produced, and permanently links them.
<Callout tone="blue" badge="SERIAL vs BATCH" title="Two tracking modes, one genealogy.">
Use <Term id="serial">serial tracking</Term> for individual units and <Term id="batch">batch tracking</Term> for lots. Scanning either tracking type into a parent records the genealogy, including links between serials and batches.
</Callout>
<Screenshot src="/screens/floor-shopfloor-scan.png" label="Shop-floor material issue" caption="An operator issuing one tracked Structural Frame Assembly into the job at the station." ratio="wide" />