Turn a sales or production plan into live work orders — an internal WO to replenish stock, a Sales Work Order tied to a customer OA for made-to-order jobs. Reserve and issue material, book good and reject WIP, transfer finished goods to stock, and read it all back as production MIS.
Customer jobs live in one spreadsheet, stock replenishment in another. Planners can't see the whole load on a work center, and a rush OA silently starves a stock job of material.
No reserve step, no BOM explosion — stores hand out material on trust. By month end, consumption doesn't reconcile to BOM and nobody can say which work order ate the excess.
Good and reject quantities aren't booked at each operation, so managers learn about a rejection spike only when finished goods fall short — and the reject is already scrap.
Production says it made 200; stores can't find them; dispatch double-counts. Without a controlled FG transfer, made and on-hand are two different numbers that never agree.
Every work order follows the same controlled path, whether it is a make-to-stock top-up or a make-to-order job against a customer OA — so the floor runs on process, not on memory.
Fast Production Software gives production and stores managers the shop floor they keep trying to build with slips and spreadsheets — with the measurement built in, for make-to-order and make-to-stock alike.
Raise a work order by hand or auto-generate it from the sales/production plan through Fast Planning / MRP. A make-to-stock top-up runs on an internal Work Order (WO); a make-to-order job runs on a Sales Work Order (SWO) tied to a customer OA, carrying its own order-specific BOM. Both move through 01 Draft → 4 Released → 10 Completed → 11 Closed, and job cards print for the floor.
A production requisition (PRMR) explodes the BOM against the work order. Material moves in two controlled steps: RES/WO reserves — earmarks stock so it can't be double-committed — then ISS/IWO issues it to the line, the real stock deduction charged to the order. Wrong issue? Reverse it. Unused? Return it. Cancel and it posts CRES / CISS. Read more on material issue & WIP.
Each work order runs a route of operations, one work center at a time, off a master or order-specific process sheet. Operators book WIP/OKPLUS good and WIP/OKNOTOKMINUS reject at each step, with process scrap (PSCR) removed from the route. Production slips move WIP operation to operation, and an in-process inspection branch pulls quality in where it belongs — so nothing is measured only at the end.
When the route is complete, output transfers to finished-goods stock as an FGM/FGM manufacture event plus an FGP/FG transfer, posting onto the same ledger Fast Inventory uses. FG can be lot-tracked, over-production is handled with an excess FG transfer, and semi-finished goods transfer the same way to feed the next assembly level — then it's on-hand for dispatch. Details on FG, rejection & rework.
Dhruv AI is the Fast Suite's AI analytics module. It gives production managers a role dashboard over live shop-floor data, a natural-language chat that turns a plain-English question into a query — validated through a read-only security sandbox — and clustering that groups reject remarks into labelled themes by work center and item, so a recurring defect surfaces without anyone hunting for it.
Master, multi-level and order-specific BOM with a Bill of Resources for machines, labour and operations — released for production, rolled up into BOM costing.
Internal WO for stock and Sales Work Order against a customer OA, generated from the sales plan, with WO specifications, job cards and live job-card status.
PRMR BOM explosion, RES/WO reserve then ISS/IWO issue, issue reversal and return, and good/reject WIP booked at each operation with process scrap.
Master and order process sheets, work centers, operation standard times, process specifications and an in-process inspection branch into quality.
Lot-tracked FG transfer to stock, excess FG for over-production, line rejection against the WO, and a full rework loop back to FG or the main flow.
WO follow-up and ageing, consumption vs BOM, process cost and rejection MIS — plus a Dhruv AI production dashboard, reject clustering and plain-English queries.
Yes. Make-to-stock runs on an internal Work Order; make-to-order runs on a Sales Work Order tied to a customer OA — both through the same reserve, issue, WIP and FG-transfer flow.
Yes — raise them by hand or auto-generate a WO/SWO from the sales/production plan, so what Fast Planning/MRP says to make becomes an actual order without re-keying.
A PRMR explodes the BOM; RES/WO reserves (earmarks) stock; ISS/IWO issues it — the real deduction. Stock commits only at issue, and consumption is measured against BOM.
Route complete → FGM/FGM manufacture plus FGP/FG transfer onto the shared ledger. FG is lot-tracked, excess FG is handled, and it's on-hand for dispatch immediately.
A WO replenishes stock; a SWO is tied to a specific customer OA and can carry an order-specific BOM and process sheet for that variant. Execution is identical.
WO follow-up/ageing, live job-card status, consumption vs BOM, process cost and rejection MIS, and BOM costing — with a Dhruv AI production dashboard on top.
Sheet-metal, machining and welded assemblies — make-to-order against a customer OA, with per-order BOM and process sheets.
Learn moreAPQP/PPAP-governed parts with work-center routing, in-process inspection, and line rejection and rework tracked per work order.
Learn moreMulti-level structural BOMs, sub-assembly manufacture, SFG to FG, and kit/component issue to the line.
Learn moreThe upstream behind this page — the sales/production plan that generates work orders and reserves the stock production issues against.
See the integrationA 30-minute demo — your BOM, your work orders, your route on screen. See WO/SWO, reserve and issue, WIP capture and FG transfer work as one shop floor.
