Learn how to connect production orders, machine data and quality records, and how to decide whether to configure, integrate or build an MES.
A production order can look on schedule in the planning system while the line is waiting for a first-off inspection, using a different material lot or recording rejects on paper. A manufacturing execution system (MES) connects these events to the order so supervisors can see what is running, what is holding it up and what can be released.
This guide explains how UK factories can plan an MES that gives operators clear work instructions, helps supervisors track downtime and keeps quality checks and traceability records tied to each production order. It also covers which planning and machine systems to connect, when to build a custom workflow and what to prove on one line before rolling it out to others.
What Should a Manufacturing Execution System Do on the Shop Floor?
Start with the decisions operators, supervisors and quality teams make during a shift. The table maps common production events to the information each team needs and the action it can take.
| Shop-floor event | What the system should record | Decision it supports |
|---|---|---|
| Job release | Order, product, quantity, routing and approved instruction revision | Can the operator start the right job on this line? |
| Material consumption | Component or ingredient lot, quantity and order or batch reference | Which materials went into this run? |
| Downtime | Line, start and finish times, and a confirmed reason | Which stops need maintenance or a process change? |
| In-process inspection | Result, tolerance, operator and decision on affected stock | Can the job continue, or should affected units be held? |
| Rework and scrap | Affected units, reason and approved follow-up | Which units can return to production, and what should be written off? |
| Job completion | Good quantity, rejects, open holds and completion time | What can be booked into stock or passed to the next operation? |
Ask a vendor or development team to run a job through the proposed workflow with a material substitution or a failed check. Watch whether the operator sees what to do next and whether the supervisor can reconstruct the decision at handover. Use the same example across proposals and ask for the resulting order record so you can compare how each handles the interruption and what evidence remains.
How Should Operators Receive Jobs and Work Instructions?
A manufacturing execution system should show the current job, operation and approved instructions at the point of work. Before a changeover, an operator might need to confirm the tooling, scan the input material and complete a first-off inspection. Require confirmations that inform a decision or create a record someone will need later, so routine work stays manageable.
Decide how to handle a revision issued after work has started. On a Midlands machining line, a drawing might change after the first pieces have been made, so the supervisor needs to know which units used the earlier version and where to apply the new one. Preserve the revision used for each run and show who approved any deviation, especially when another shift takes over before the order is complete.
How Can Machine Data Help Explain Lost Production Time?
A manufacturing execution system can associate machine counts and stop signals with the active order and line. A stop signal can establish when equipment stopped, while an operator can record whether the cause was a material shortage, a quality check or a fault. If several machines stop together, agree which event represents the line stoppage so the same lost time is counted once.
Start with a few signals that can change a decision at the shift review. Use industrial IoT integration where compatible equipment can share counts or operating status, and give operators a quick way to capture information from older machines. Show when data was last received so supervisors can recognise a lost connection before they interpret a quiet dashboard as a stopped line.
How Should Quality Holds and Traceability Work?
A failed check should identify the affected material or units and trigger the agreed response. A manufacturing execution system can record where a hold began, which quantities it covers and who can release, rework or scrap the affected stock. If some of the order remains eligible to move, make the boundary clear to the next operator and to anyone booking output into stock.
Use software testing and QA to check that the system blocks held units from moving to the next operation and allows only authorised staff to release them. Include split lots, approved substitutions and rework so you can verify that staff can trace a suspect lot forward to every affected unit and work backwards from a finished unit to its inputs.
What Should Connect to ERP and Machine Control?
An enterprise resource planning (ERP) system typically supplies production orders and item data, while the manufacturing execution system records the work performed and returns confirmed quantities and material consumption. Machine controls continue to run the equipment. The ISA-95 framework gives teams a common reference for discussing how production and enterprise systems exchange information.
Agree which application owns each record, which identifiers the systems share and how staff will handle failed transfers. For example, an order-completion message retried after a network interruption should create only one stock receipt, and a rejected message should show who needs to review it. Data engineering can help align order, material and line identifiers before those records feed stock reporting or production analysis.
How Should Supervisors Compare Performance Across Shifts?
Agree what counts as good output, scrap, rework and planned downtime before comparing shifts. A short run with two changeovers can produce fewer units per hour than a longer run of the same product and still meet its production plan. Use data visualisation to show the product, planned run time and changeovers alongside output figures so supervisors can see which differences need investigating.
Give the incoming supervisor a view of unresolved issues at handover, including stoppages with no confirmed cause, incomplete orders and material awaiting a quality decision. If a stoppage recurred on the night shift, show which orders were affected and who will follow up so maintenance can investigate it. Assign an owner and a deadline to each item.
When Is a Custom MES Worth Building?
Compare configuration, integration and a custom build using the same production order and a real exception. Ask each team to demonstrate how its proposed manufacturing execution system handles the job during a shift and what staff would need to do outside the system.
- Configure an existing product when it supports the routing, instructions and quality steps your operators need, and supervisors can maintain the settings.
- Connect existing tools when planning, line control and quality applications work well individually but staff re-enter job details, consumption or inspection results between them.
- Build a targeted workflow when a recurring task needs custom manufacturing execution software, such as managing mixed-product rework with different approval rules on shared equipment.
- Compare the ongoing costs of each approach, including out-of-hours support, changes to routings, training for new operators and maintenance of machine and ERP connections.
The value of manufacturing operations software depends on where the proposed change removes work or improves decisions. If supervisors already have reliable machine data but spend hours reconciling orders and material use, first address how those records reach the stock and costing systems. Before committing, check how you would export order history, quality records and approved instructions if you moved to a different platform later.
How Can UK Factories Prove the Change on One Line?
Choose one line, cell or product family where you can observe a normal run, a changeover and an exception. Record a baseline for the problem you want to fix, such as time to reconcile output at the end of a shift, the share of stops with a confirmed reason or the time needed to trace a suspect lot. In North West England, the Made Smarter programme offers manufacturing businesses digital advice and support with planning technology adoption.
Before the pilot starts, agree what improvement would justify rolling out the system to another line. For example, if supervisors spend 30 minutes reconciling production figures at the end of a shift, set a target of 15 minutes and confirm that the figures still match the stock records. Compare the results with the baseline across routine runs, changeovers and disrupted shifts before deciding whether to expand the rollout.
How Can Dev Centre House Support Manufacturing Execution System Development?
Dev Centre House helps factory teams spend less time chasing production updates, reconciling shift figures and tracing batches across separate records. Through custom software development, we can connect the planning and shop-floor tools you already use or build a focused application that gives operators clearer instructions and helps supervisors resolve production issues sooner.
Book a consultation to discuss a recent run that needed extra work to close, whether the problem was an inspection hold, an unexplained stop or a mismatch in reported quantities. We’ll walk through how your team handled it and identify what a first release should do to make the next run easier to manage.
Conclusion
A manufacturing execution system should help your team explain what was made, why work stopped and which output can move to the next operation. Choose the controls that matter most to your plant and use a representative run to see how well they work across production, quality and planning.
Use the pilot results to compare each option against the time spent correcting records, investigating stops or locating affected stock today. IT consultancy and advisory can help you weigh the cost of the change against the improvements your team needs. Speak with Dev Centre House to review your findings and decide which shop-floor process to improve first.
FAQs
1. What does a manufacturing execution system do?
It guides and records shop-floor work by linking production orders to instructions, material use, output and quality decisions.
2. How does a manufacturing execution system work with ERP?
ERP typically provides production orders and item data, while the MES returns confirmed output, material consumption and completion status.
3. Can a manufacturing execution system work with older machinery?
Yes, teams can use compatible interfaces where available or have operators record the production events they need to track.
4. When is a custom MES worth considering?
Consider a custom build when a recurring shop-floor requirement cannot be handled effectively through existing product settings or integrations.
5. What should an MES pilot measure?
Measure the issue the pilot is meant to improve, such as shift reconciliation time, the share of stops with a confirmed reason or the time needed to trace a material lot.


