How can we help?

Open the sales plan entry screen, choose the planning horizon, and enter gross demand for each finished good — typed against a forecast for make-to-stock, or pulled from confirmed orders for make-to-order. The plan seeds MRP; the same screen builds a production plan view you can review before you run the explosion. See Sales & Production Plan.

For each item, MRP subtracts what you already have and expect from what you need: Net Requirement = Gross Demand − Stock on Hand − Open Supply (open POs + open work orders + reserved stock). Gross demand is exploded through the BOM to every sub-assembly, component and raw material, and each level is netted, so only the true shortfall becomes a suggestion. See MRP — BOM Explosion & Netting.

After netting, raw-material and bought-out shortfalls go to the raw-material or bought-out plan and become purchase requisitions for the purchase team; in-house semi-finished and outsourced component shortfalls go to the component plan and become work orders with a specification and routing. One netted result splits cleanly into a buy list and a make list. See MRP — BOM Explosion & Netting.

A master process sheet holds, per item, the standard list of operations or activities, the machine each runs on, the standard cost, and the standard cycle and setting time, in the sequence they are performed. It exists for both job and batch production, and it is the template every order-specific process sheet is copied from. See Process Sheets & Routing.

An order process sheet is the routing for a specific order. You copy it from the master or a previous order, then modify cycle and setting times, capture order-wise cost per operation, re-sequence operations and reassign machines for that order. It becomes the manufacturing sheet and job card the floor works to. See Process Sheets & Routing.

A job card is the printable shop-floor document for a work order — carrying the process sheet, operations, machines and standard times, so the operator knows what to run and in what order. Job cards can be printed for a single work order or in batch for many at once, and they are the paper or barcode-backed instruction the floor books progress against. See Process Sheets & Routing.

Machine loading calculates how much work is assigned to each machine or resource against the time it has available. The machine loading report shows the daily load, loading as a percentage of capacity, the pending load from released work, and projected availability — so planners can level the load, spot overloads early and plan realistic dates. See Machine Loading & Capacity.

Priority management sets the sequence work runs in. Order or project priority decides which orders take precedence; resource priority decides which order a shared machine serves first. You can set priority and re-sequence it as things change, and the schedule respects that order when it lays work onto capacity. See Scheduling & Priority (Gantt).

Once work orders exist, they are laid out on a DayPilot Gantt board — a drag-oriented visual scheduler that shows work orders by priority and timeline across machines. Together with the order-wise planned schedule, it turns a netted, prioritised plan into a dated sequence the floor can follow. See Scheduling & Priority (Gantt).

Process status is updated shift, machine and operator-wise — often by scanning shift, machine and operator barcodes — recording OK and not-OK production, actual start and end times, actual cycle and setting times, and any machine stoppage or breakdown. That is the raw actual data every efficiency and OEE view is built from. See Plan vs Actual & OEE.

The plan-vs-actual report compares what the plan said would happen against what the floor actually booked — planned versus actual quantity and time, order by order and work centre by work centre. Alongside order-wise, work-centre, machine, shift and operator completed reports, it shows where the plan held and where it slipped. See Plan vs Actual & OEE.

Booked actuals roll up into work-centre, machine and operator utilization, daily and monthly operator efficiency, machine efficiency, and idle-time and additional-time summaries — with graphical dashboards for operator efficiency, machine efficiency and idle time. Together they give the OEE picture, so the biggest recurring loss names itself. See Plan vs Actual & OEE.

Natively, on one platform. Work orders the plan raises flow into Fast Production, which reports completion and consumption back; MRP nets against live Fast Inventory stock and can reserve it against a plan; and buy-side shortfalls become purchase requisitions for Fast Purchase. There is no interface and no data copy — the plan reads the same records execution uses. See Production, Inventory & Purchase.

Yes. Beyond barcode process-status booking, Fast Planning can capture machine data through IoT devices — machine start and end times of operations, and parameters like temperature and pressure — plus Pick-to-Light for inventory visibility. That Industry 4.0 capture feeds live machine status and the efficiency and OEE dashboards. See IoT / Industry 4.0 Machine Data.

Dhruv AI is our AI analytics layer. It adds a planning role dashboard with AI insight summaries on machine load, plan-vs-actual and OEE, answers plain-English questions through a safe read-only query sandbox, and clusters delay and breakdown-cause remarks into named recurring themes — so the biggest planning problems name themselves. See Dhruv AI Planning Analytics.

The admin module handles user entry and role configuration, with role-wise and user-wise access rights, so each user sees only the menus their role allows — planners run MRP and release work orders, purchase handle requisitions, supervisors book process status, managers see the dashboards. Users can be deactivated, passwords managed, and login history reviewed.

Yes. Every plan, work order, purchase requisition and stock reservation is a document with a status history, and every write is logged with the user who made it. Because the plan, the work order and the stock netting ride one shared item, BOM and stock ledger, you can trace a requirement from the sales plan through to the work order and purchase requisition it produced.

Fast Planning can run standalone for the sales plan, BOM explosion and netting, work-order and purchase-requisition suggestions and scheduling. It is normally licensed with Fast Production, Fast Inventory and Fast Purchase so the plan, the work order and the stock netting share one platform — with no duplicate data entry and no integration project. See integrations.