Fast Planning/MRP is the upstream half of the shop floor. It suggests quantities and generates work orders from the sales, component and RM plan, and its reservation earmarks stock against each work order. Fast Production then issues material against those earmarks. Plan to work order to issue is one continuous chain on the same tables — no export file, no interface to babysit.
The handoff from planning to production is where re-keying and stock errors usually creep in. On the shared platform there is nothing to re-key: the plan generates the work order, and MRP reservation earmarks the stock the work order will draw against.
Because Fast Planning and Fast Production share the document engine, each step writes to the same tables the next step reads. There is no import, no reconciliation and no drift between what was planned and what gets made.
Every link below is a native table-level connection on the shared document engine — planning demand, work orders, reservations and issue are the same records read from both ends, not files passed between two systems.
Planning nets demand against stock and suggests what to make. From there, a work order is generated straight from the plan line, so the quantity, item and due date the planner set carry through to the floor without anyone typing them again. It becomes a live work order, born at Draft and released when it's ready to run. Explore the upstream side at fastplanningsoftware.com.
Reservation is the discipline that stops two jobs fighting over the same material. MRP earmarks stock against the work order; Production then issues against that earmark when the job runs. The reserve is a claim, not a movement — stock only truly leaves store stock at issue, which keeps on-hand honest between planning and the floor.
When planning and production are two systems, the gap between them is where errors live — a plan exported, a work order re-typed, a stock figure that no longer matches. On the shared document engine there is no gap: the plan, the work order, the reservation and the issue are the same records. What the planner committed is exactly what the floor issues against, and what the floor completes is exactly what planning sees next.
Planning/MRP generates work orders from the sales, component and RM plan — the suggested quantity becomes a WO or SWO without re-keying.
Stock is earmarked against the work order so it can't be double-committed — reserve first, issue when the job runs.
Production issues against the earmark the plan created — the real stock deduction happens at issue, keeping on-hand honest.
A customer order acceptance becomes an SWO with its own order-specific BOM, so each job is planned to the exact order.
A shortfall against the BOM raises a purchase requisition, tying production demand from the plan straight into procurement.
Production writes back to the same records, so planning sees actual WO status, consumption and completion against the plan with no reconciliation cycle.
In a 30-minute demo we'll take a plan through to generated work orders, reserved material and the first issue — one continuous chain, no re-keying.
