Planning across disconnected systems
Textile manufacturing is deceptively complex. A single style order triggers a cascade: yarn procurement, dyeing batch scheduling, warping, sizing, weaving, finishing, and packing — each stage with its own lead time, machine constraint, and labour requirement. This manufacturer ran six separate spreadsheets to coordinate these stages, with a planning team of eight spending most of Monday through Friday just keeping the sheets in sync.
When a buyer changed a delivery date or a dyeing batch was delayed, the ripple effect took two to three days to propagate through all the planning sheets. By the time the loom floor got updated schedules, some machines had already been set up for the wrong order.
One database for the whole factory
The migration connected yarn inventory, production orders, machine calendars, and despatch schedules into a single platform. A sales order now drives a multi-level production plan automatically — from finished goods requirement back through dyeing lots to yarn purchase requisitions.
- Constraint-aware scheduling — loom allocation respects machine downtime and maintenance windows
- Real-time yarn availability — production orders can only be confirmed if yarn stock or PO covers the requirement
- Dyeing batch consolidation — similar shades auto-grouped to maximise dye lot efficiency
- Delivery date simulation — sales team can check feasible delivery dates before confirming to buyer
- Delay cascade alerts — any upstream slip automatically flags downstream orders at risk
Results and team impact
The weekly planning cycle dropped from five days to two. The planning team — still the same eight people — now spends the freed time on what-if scenario analysis and buyer communication rather than spreadsheet reconciliation. On-time delivery improved from 74% to 91% in the first six months.
We used to plan for the factory. Now the system plans and we supervise exceptions. That is a fundamentally different job.
Go-live in days, not months
The manufacturer went live with the production planning module in eight days. The existing item master, BOM structure, and supplier data were migrated on day one. Machine calendars were configured on days two and three. The planning team ran parallel cycles for one week before cutting over. No big-bang cutover, no factory shutdown.