Production planning · Apparel manufacturing
Factory OS takes the production line off the spreadsheet. A dual-track milestone engine schedules every order, nine SOP gates hold the line before cutting, and a capacity engine tells you what the floor can actually take.
295 live production orders across nine departments — Adidas, Nike and Reebok programmes.
Dual-track milestone engine
Real production doesn't run on a single deadline. Factory OS schedules each order on two tracks at once, so a slipped delivery date and a late goods receipt are handled by different logic instead of the same overworked spreadsheet.
Milestones are calculated as offsets from the customer request date. Change the CRD once and every downstream step — fabric, cut, sew, finish — recalculates against it. No more re-keying a column of dates by hand.
Some steps can't start until material physically lands. Track B milestones fire on the goods receipt (GRN) event — inspection, kitting and everything gated behind them start their clock the moment stock is received, not a day the planner guessed.
SOP quality gates
Cutting is the point of no return. Factory OS makes the nine standard-operating-procedure checks mandatory: the order cannot advance until each gate is signed off, with evidence attached and every override logged against a name.
An order is blocked from progressing until all nine gates pass. The workflow enforces the sequence — no skipping ahead to keep a ship date.
Each gate carries its proof — attach the photo, spec or lab result at the point of sign-off so the record travels with the order, not a separate folder.
When production has to move under exception, the override is captured — who authorised it and why — so nothing bypasses the gate silently.
GATE 01 → GATE 09 · each step is auditable, each override is named.
Capacity engine
Every commitment eventually meets the same question — can the floor actually make it in time? Factory OS answers with real production-day maths and lets planners test the answer before they promise it.
Load is worked out in real production days, so a plan reflects the working calendar of the line rather than raw days on a Gantt.
Throughput is measured as LPCD across the floor, giving a consistent unit to plan and compare orders against.
Simulate an overtime scenario and see how the schedule flexes before committing — pressure-test a date instead of finding out on the floor.
Product tour
Role-adaptive dashboards, a custom Gantt, FullCalendar and Kanban plus table views — the same order, seen the way each team needs to see it.
Under the hood
Fourteen routes, thirty-one-plus API endpoints, Excel import so no one loses their existing data, and analytics that read straight off the live order book.
See Factory OS run a real order end to end — dual-track milestones, nine SOP gates and a what-if capacity plan. We'll walk your team through it.