Production Management System: Right-Sized and Owned, Not a Bloated Suite
Most guides push a production management system as a giant MRP or ERP suite you rent forever. This is the honest version: what a production management system actually needs to do for a growing UK product business, where the generic platforms overshoot, and why a right-sized owned system usually wins on cost, control and adoption.
A production management system connects the records a manufacturer uses to turn a customer order into finished, checked goods: the works order, the plan, the materials, the shop floor activity, the quality checks and the completion back into stock. It gives sales, planning, purchasing, the floor and finance one traceable chain for each job instead of separate lists that disagree.
The practical problem is rarely a missing feature. It is the handoffs. Sales promises a date without seeing the load, materials are found short at the machine, nobody records the rework, and the job cost is reconstructed weeks later. This guide follows one order end to end and shows what each stage of the system has to hold, how the approaches compare and how to test one before committing.

A production management system should connect floor activity to the order, materials and cost behind it. Illustrative photograph, not an OpsMavix project.
Image credit: Sam Moghadam, Unsplash License. No edits.
Key Takeaways
- A production management system links order, works order, plan, materials, floor, quality and completion.
- The works order is the spine: every issue, booking, check and cost should reference it.
- Capacity and material checks belong before release, not after the job stalls.
- Quality results, scrap and rework need to be recorded against the job as they happen.
- Completion should update stock, close WIP and compare actual cost with the estimate.
- Choose configuration, integration, packaged software, a focused application or full ERP against demonstrated gaps.
In this guide:
- 1. Define What a Production Management System Covers
- 2. Follow One Order From Sales to Works Order
- 3. Plan Capacity and Sequence the Work
- 4. Control Materials and Work in Progress
- 5. Run the Shop Floor and Build Quality In
- 6. Complete Cost and Close Each Works Order
- 7. Compare the Available System Approaches
- 8. Pilot One Product Family Before Rollout
- Frequently Asked Questions
- How OpsMavix Can Help
1. Define What a Production Management System Covers
Think in stages, not modules
Vendors package production capabilities in different ways, so module names are a poor basis for comparison. Start with the stages a job passes through and the record each stage must create.
| Stage | Key record | Question it answers |
|---|---|---|
| Order intake | Sales order line with product, quantity and requested date | What has the customer asked for and by when? |
| Works order | Instruction to make a quantity of one item to a revision | What exactly are we making and from what? |
| Planning | Scheduled operations against work centres | When will each operation run and on which resource? |
| Materials | Allocations, issues and shortages | Can the job start, and what has it consumed? |
| Shop floor | Operation start, finish, quantities and time | Where is the job now and what actually happened? |
| Quality | Inspection results, non-conformances, rework | Did it pass, and what went wrong if not? |
| Completion | Finished goods receipt and job cost | What did we make, what did it cost and where is it? |
A system can cover all of these in one application or spread them across connected tools. What matters is that the chain stays traceable from the order line to the finished goods receipt.
Separate the business layer from the operations layer
The ISA-95 standard describes business systems such as ERP at level 4 and manufacturing operations systems such as MES at level 3, and focuses on the interface between them. That is a useful lens for any size of business. Orders, purchasing and accounts sit in the business layer; dispatching, recording and checking work sit in the operations layer. A production management system either spans both or owns the operations layer and exchanges data with the business layer.
Know what this guide is not
This guide covers the whole chain. Narrower angles have their own guides: live floor visibility in production monitoring systems, planning and scheduling engines in production planning software, and the toolset for planned versus actual control in production planning and control tools.
2. Follow One Order From Sales to Works Order
Turn demand into an instruction
A sales order says what the customer wants. A works order says what the factory will make. They are not the same record. One order line may create one works order, several works orders for sub-assemblies, or none if the item is already in stock. Make-to-stock products may get works orders from a replenishment plan rather than a customer order.
A useful works order carries the item, quantity, bill of materials revision, routing, due date and a link back to the demand it serves. If the bill of materials or routing changes after release, the works order should keep the version it was released with, so the floor builds what was planned and costs remain comparable.
Keep the states honest
| Works order state | What it means | Common mistake |
|---|---|---|
| Draft | Created but not checked for materials or capacity | Treating it as committed work |
| Released | Approved for the floor, materials allocated | Releasing before materials are confirmed |
| In progress | At least one operation started | No record of which operation |
| On hold | Stopped for a stated reason | Holding without a reason or owner |
| Completed | Finished quantity received into stock | Closing before scrap and rework are recorded |
| Closed | Costs finalised and variances reviewed | Leaving completed orders open indefinitely |
For more on what processing a works order involves day to day, see works order processing software.
3. Plan Capacity and Sequence the Work
Check the load before promising
Planning asks whether the work fits the resources. It needs the routing (which operations, on which work centre, with setup and run times) and the realistic capacity of each work centre after breaks, maintenance and expected losses.
Hypothetical worked example: one weld cell
The figures below are hypothetical. A weld cell has two welders working 37.5 hours a week each. The business plans at 85% of attended time to allow for interruptions.
- Planned capacity: 2 × 37.5 × 0.85 = 63.75 hours
- Already committed load next week: 52 hours
- New order: 150 units × 0.1 hours run time = 15 hours, plus 2 hours setup = 17 hours
- Total load: 52 + 17 = 69 hours
- Overload: 69 - 63.75 = 5.25 hours
The system should show that overload before the date is confirmed. The planner can then add 6 hours of overtime (capacity becomes 69.75 hours), move a lower-priority job, split the order across two weeks, or quote a later date. Each option has a cost; the point is to choose one deliberately rather than discover the problem on Thursday.
Decide how much scheduling you need
| Need | Typical tool | Watch for |
|---|---|---|
| Rough weekly load by work centre | Capacity view or spreadsheet with routing times | Times that are never updated from actuals |
| Sequenced jobs per work centre | Scheduling board | Plans that ignore material availability |
| Finite scheduling across many constraints | Advanced planning and scheduling | Set-up effort and data quality demands |
Many smaller shops only need the first two. A deeper treatment is in manufacturing scheduling software, and the question of whether you need full material requirements planning is covered in do you need an MRP system.
4. Control Materials and Work in Progress
Net requirements before release
Material control starts with the bill of materials. Explode the quantity required, allow for expected scrap, then net against free stock and confirmed incoming supply.
Hypothetical worked example: bracket requirement
Continuing the same hypothetical order of 150 units, each needing 2 brackets, with a 3% scrap allowance:
- Gross requirement: 150 × 2 = 300 brackets
- With scrap allowance: 300 × 1.03 = 309 brackets
- On hand: 180, of which 60 are allocated to other works orders, so free stock = 180 - 60 = 120
- Confirmed purchase order arriving before the job starts: 100
- Net shortfall: 309 - 120 - 100 = 89 brackets
The works order should not be released until those 89 are ordered with a delivery date that supports the schedule, or the plan is changed. Discovering the shortfall at the machine wastes setup time and disrupts the next job.
Treat WIP as a record, not a guess
Work in progress is material and labour that has left raw stock but not yet become finished goods. The system should know which materials were issued to which works order, which operations are complete and what quantity sits between operations. Decide early whether materials are issued at release, at each operation, or backflushed at completion; each method changes when stock and WIP move, and finance needs to agree how the WIP value is used for reporting.
| Issue method | When stock moves | Suits | Risk |
|---|---|---|---|
| Issue at release | Before work starts | Kitted jobs, high-value parts | Stock looks consumed if the job is delayed |
| Issue per operation | As each step begins | Long routings, staged materials | More transactions to record |
| Backflush at completion | When finished goods are booked | Simple, repetitive, low-value items | Scrap and substitutions hidden until counts |
5. Run the Shop Floor and Build Quality In

Inspection results are most useful when they are recorded against the works order and operation. Illustrative photograph, not an OpsMavix project.
Image credit: Spencer Davis, Unsplash License. No edits.
Capture what happened, where it happened
Floor recording should be quick enough to keep up during a busy week. A scan or tap to start and finish an operation, the quantity good and rejected, and a reason code when work stops is usually enough to drive status, actual times and WIP. Packaged products often offer this through a tablet or barcode app; Katana, for example, lists a “Shop floor app” and “Barcode scanning” among its manufacturing features. Test any such app with the devices, gloves and connectivity your floor actually has.
For live visibility of running, idle and stopped work centres, see production monitoring systems. For a job status view built on the same records, see building a production tracker.
Put checks inside the routing
Quality works best as part of the job, not a separate file. Define inspection points as operations or steps on the routing, with the characteristics to check and the acceptance limits. Then the system can stop a job moving on until the check is recorded.
| Quality record | Linked to | Why it matters |
|---|---|---|
| First-off inspection | Works order and first operation | Catches setup errors before a batch is made |
| In-process check | Operation and quantity | Shows where defects start |
| Non-conformance | Works order, operation, reason, quantity | Drives rework, scrap or concession decisions |
| Rework booking | Original works order | Keeps rework cost on the job that caused it |
| Final inspection | Completed quantity | Supports release into stock |
| Batch or serial record | Materials issued and finished goods | Allows tracing back to supplier lots |
Hypothetical first pass yield
In the same hypothetical order, 150 units are started and 147 pass inspection first time; 3 are reworked and then pass. First pass yield is 147 ÷ 150 = 98%, while final yield is 150 ÷ 150 = 100%. Reporting only final yield hides the rework cost. Scrap and rework tracking explains how to turn those reason codes into root-cause fixes.
6. Complete Cost and Close Each Works Order
Book completion carefully
Completion receives the finished quantity into stock at a location, records any final scrap, and releases the goods for dispatch or the next level of assembly. If lot or serial numbers apply, they are assigned here and linked to the materials issued.
Hypothetical worked example: actual job cost
All figures are hypothetical and exclude VAT and overhead absorption.
| Cost element | Calculation | Amount |
|---|---|---|
| Materials issued | From issue records | £2,460 |
| Welding labour | 17 hours × £38 | £646 |
| Assembly labour | 22 hours × £34 | £748 |
| Rework labour | 1.5 hours × £34 | £51 |
| Subcontract coating | Supplier invoice | £420 |
| Actual job cost | Sum of the above | £4,325 |
- Estimated cost at quote: £4,100, so the variance is 4,325 - 4,100 = £225 adverse
- Cost per unit: 4,325 ÷ 150 = £28.83
- Hypothetical selling price: 150 × £36 = £5,400
- Contribution: 5,400 - 4,325 = £1,075, or 1,075 ÷ 5,400 = 19.9%
The useful question is not only “did it make money?” but “which element moved?”. Here, the system can show whether the welding hours, the rework or the material issue explains the gap. That answer feeds back into routings and quotes. For the costing side in depth, see job costing software for manufacturing.
Close the loop
A works order should not close until scrap, rework and all issues are posted and the variance is reviewed by someone who can act on it. Agree with finance how labour rates, overhead and WIP valuation are applied, since the operational system and the accounts need the same definitions.
7. Compare the Available System Approaches
Match the approach to the gap
| Approach | Where it fits | What to check |
|---|---|---|
| Configure current tools | Accounting or stock software already has basic assembly or works orders | Edition limits, routing support, floor usability |
| Connect existing systems | Tools work individually but handoffs fail | Shared item and order references, failed transfer handling |
| Packaged production or MRP software | Standard make-to-order or make-to-stock flows | Routing depth, quality steps, costing method, integrations |
| Focused custom application | One valuable gap with clear boundaries, such as floor capture or quality | Data ownership, support, maintenance, integration scope |
| Full ERP, packaged or custom | Wider coordination across finance, sales, purchasing and production | Fit, migration, implementation capacity, ongoing change |
Packaged products have real strengths: established workflows, documentation and frequent updates. A broader ERP brings finance and production onto one database, which ERP in manufacturing discusses. Custom work brings exact fit but needs a maintenance and support arrangement. None is always cheaper or better.
Compare on one shared scenario
Ask each option to run the same scenario: the order in this guide, including the capacity overload, the bracket shortfall, three reworked units and the final cost variance. Mark each step as demonstrated, configurable, requiring development or unsupported. Include licences or hosting, implementation, data migration, training and support over several years. Manufacturing operations management software compares several packaged options on floor criteria.
8. Pilot One Product Family Before Rollout
Choose a representative slice
Pick a product family that touches every stage: a real customer order, at least two work centres, purchased materials, an inspection point and a subcontract operation if you use them. Load real opening stock and open orders; an empty test database cannot prove reconciliation.
Practical acceptance checklist
- Order lines create works orders with the correct BOM and routing revision.
- Capacity load per work centre matches a manual check.
- Material netting matches the worked calculation, including allocations and incoming supply.
- Release is blocked or warned when materials or capacity are short.
- Operators can record start, finish, quantities and stop reasons in under a minute.
- Inspection steps stop the job moving on until results are recorded.
- Rework and scrap stay on the originating works order.
- Completion updates stock, closes WIP and links lot or serial numbers where needed.
- Actual cost reconciles to issue, labour and supplier records.
- Data exchange with accounts and purchasing shows failures and can be corrected.
Run the pilot for several weeks, compare planned against actual each week and fix definitions before adding more product families.
Frequently Asked Questions
What is a production management system?
It is the set of connected records and workflows that take a manufacturing order from demand to finished goods: works orders, planning, materials, shop floor recording, quality and completion. It may be one application or several connected tools.
How is it different from ERP?
ERP usually covers the wider business, including finance, sales and purchasing. A production management system focuses on how goods are made. Some ERP products include it; some businesses run a production system alongside separate accounts and sales tools.
Is a production management system the same as MES?
They overlap. In ISA-95 terms, MES sits in the manufacturing operations layer, focused on dispatching and recording work. A production management system as described here also includes order-to-works-order conversion, planning and costing, which can sit in either layer.
Do I need MRP?
Only if the material netting is complex enough to need automation across many components and levels. Smaller shops often manage with BOM explosion and netting per works order, as in the bracket example above.
What data do I need before starting?
Clean item codes, current bills of materials, routings with realistic times, work centre capacities, opening stock and open orders. Gaps here cause more trouble than any software choice.
How should quality fit in?
As steps on the routing, with results recorded against the works order and operation. Non-conformances, rework and scrap should stay linked to the job that caused them.
Can it connect to my accounting software?
Usually, yes. Many packaged products list integrations with common accounting tools, and custom systems can be built to exchange data. Agree which system owns each record and how failed transfers are handled.
Can OpsMavix build a production management system?
Yes. OpsMavix can build focused applications or a full custom ERP, and can configure or integrate suitable existing tools where those approaches fit the requirements.
How OpsMavix Can Help
OpsMavix can map how an order becomes a works order, how it is planned and supplied, what the floor records, where quality checks sit and how completion and cost close the loop. From that map we define the smallest system change that makes the chain traceable.
That may mean configuring tools you already have, connecting them, building manufacturing production tracking for the floor, adding an inventory automation system for material control, giving managers a project operations dashboard, or developing a full custom ERP.
Contact OpsMavix with one recent late or over-cost works order, the records behind it and the handoff that creates the most rework. We can use that evidence to define requirements and a practical pilot.
Getting value from OpsMavix? Add us as a preferred source on Google — you'll see more of our operations content in your AI Overviews, AI Mode and Search.