MES (manufacturing execution system) implementation is configuring the system around how your plant really runs, connecting it to machines, operators and ERP (enterprise resource planning), and putting it into daily use. A sound rollout has seven phases: goals and team, current-state mapping, master data, infrastructure, integration, a pilot line and controlled rollout, each closed by a readiness test.
Key takeaways
- MES implementation runs in seven phases: goals and team, current-state map, master data, infrastructure, integration, pilot line and rollout.
- Each phase closes with evidence-based readiness, such as a signed list of targets or an end-to-end work order in a test environment.
- Most of an MES implementation is plant preparation, not software: clean master data, reliable network, machine signals and a firm ERP boundary.
- The pilot runs on one line in parallel with paper; other lines follow only once paper and system figures agree.
- Siemens' 2024 report found plants average 25 downtime incidents a month; without clean reason codes, an MES cannot explain that loss.
Why do MES projects struggle during implementation?
The first week after an MES decision is usually full of optimism. The software has been chosen, the screens look good and a go-live date is on the wall. The trouble tends to surface a few days before go-live: product codes in ERP do not match the labels on the floor, the downtime reason list has grown past thirty lines, and the wireless network drops out behind the presses.
This article is not about what an MES is or how it differs from ERP; we covered that in MES vs ERP explained. It is a checklist for what comes after the decision, written for the project lead and the production manager who need something they can tick off phase by phase.
The software itself is rarely the hardest part of an MES project. The real effort goes into clean data, machines that can report, operators who change their habits, and a firm line between what MES owns and what ERP owns.
What does a poorly planned MES rollout cost?
Rushing an MES implementation costs more than a late timeline. A half-finished MES leaves operators filling in both the paper form and the new screen, and trust in the numbers drains away. The wider picture also argues for caution: BCG's research "Flipping the Odds of Digital Transformation Success" (2020) found that 70% of digital transformations fall short of their objectives.
According to Siemens' True Cost of Downtime 2024 report, plants average 25 downtime incidents a month, and an average large plant loses 27 hours a month to unplanned downtime.
An MES can only make downtime losses visible if downtime reasons are coded properly. A system where most stops end up under "other" produces reports, but not decisions.
In-house capacity is usually thin as well. The TurkStat ICT Usage Survey on Enterprises 2026 shows that only 15.2% of Turkish enterprises employ ICT specialists, falling to 10.8% among firms with 10 to 49 staff. Your MES implementation plan has to assume that this small IT team will still be running day-to-day IT while the project is live. The line items that drive the budget are covered separately in our guide to MES software cost.
The MES implementation checklist in seven phases
In an MES implementation, the sequence below is designed so that each phase hands clean, tested inputs to the next:
- Goals, sponsor and team. Make a decision-maker from production the project owner and name one representative each from production, planning, maintenance, quality and IT. Write measurable goals, such as "shift reports without paper", "every stop has a recorded reason" and "no manual production entries in ERP".
- Current-state map. Draw how a work order is created, how it reaches the floor, and where production data returns to and how late. Mark every paper and spreadsheet step; our software requirements analysis guide describes the method.
- Master data clean-up. Gather product codes, bills of materials, routings, cycle times, the machine list, shift calendars and downtime and scrap reason codes in one trusted source. The approach to removing duplicates and stale records is covered in our master data management guide.
- Shop-floor infrastructure. Survey network coverage across the production area and fix the positions of operator terminals, barcode scanners and label printers. Decide machine by machine whether data will come straight from a PLC (programmable logic controller), counter or sensor, or whether operator input is enough.
- Integration design. Agree a written field-mapping table: which fields travel from ERP to MES (work order, recipe, product code), which come back (actual quantities, scrap, consumption) and how often. Define who is alerted, and how, when a transfer fails.
- Pilot line. Start with a bottleneck line or a handful of critical machines. Fix the success criteria and duration up front, and run paper and system in parallel for a while so you can compare the numbers.
- Training, go-live and rollout. Train operators at the terminal using real work orders. Write down the go-live day, the fallback plan and the support arrangements for the first week, then extend to other lines using what the pilot taught you.
Because the most visible function on the floor will be tracking each work order operation by operation, settle your work order tracking logic before anyone designs a screen.
When is an MES implementation phase "ready"?
Use this phase-by-phase readiness table in MES steering meetings to decide whether a phase is genuinely closed. The last column is the evidence you should see before signing a phase off.
| Phase | Key checkpoint | Owner | Ready when |
|---|---|---|---|
| Goals and team | Project owner and measurable targets | Production manager | Signed list of targets |
| Current-state map | Path of work orders and production data | Planning and production | Approved process map |
| Master data | Codes, routings, cycle times, reason codes | Planning and quality | Pilot line data complete |
| Infrastructure | Network, terminals, barcode, machine signals | IT and maintenance | Test reads succeed on the pilot line |
| Integration | Field mapping and failure alerts | IT and software team | End-to-end work order in a test environment |
| Pilot | Parallel run and criteria check | Project owner | Paper and system figures agree |
| Go-live | Training, support, fallback plan | Whole team | Operators close jobs unaided |
The readiness table deliberately has no "software" row. Most of the MES implementation effort is the plant's own preparation, and no supplier, however capable, can fix missing master data or a dead network zone on your behalf.
To track the phases, owners and sign-off dates in one plan, SmartPM project management software from the Smart family can be used. Phases are laid out on a Gantt chart with their dependencies; when a predecessor such as master data runs late, the dependent steps shift forward automatically and the critical path stays visible.
Five MES implementation items that are often overlooked
A downtime reason dictionary. Start with a short list that maintenance, production and quality all accept, simple enough for an operator to pick in a few seconds. Downtime codes decide how far you can trust your OEE (overall equipment effectiveness) figures; see our guide to OEE calculation.
Older machines. Not every machine has a ready data output. We explain the options in retrofitting legacy machines; deciding machine by machine before installation avoids surprises on the floor.
Traceability scope. If you need lot or serial records, design where each label is scanned before go-live, not after. The end-to-end design is in our production traceability guide, and the scanning infrastructure is part of our production traceability and barcode service.
Audit trails and permissions. In regulated sectors such as pharmaceuticals and food, and in automotive supply chains with demanding customer audits, you need to be able to show who changed a record and when. For drug manufacturing, the FDA guidance "Data Integrity and Compliance With Drug CGMP" (2018) expects audit trails to be reviewed as often as the underlying data, for example after each significant manufacturing step and before batch release. Confirm with your quality and regulatory leads which rules apply to your site; we unpack these requirements in GMP data integrity and ALCOA.
Plant network security. An MES bridges the office network and the machine network. How to segment that bridge is covered in our article on OT security for SCADA; network segmentation deserves its own line in the plan.
How Digital Bridge runs an MES implementation
At Digital Bridge we do not try to bend a packaged product to fit your plant. We run the MES implementation with you along the seven phases of this checklist:
- We start with a site assessment. For Industry 4.0 projects we offer a free on-site assessment, looking at how work orders reach the floor, how downtime and scrap are recorded today and which signals your machines can provide.
- We fix the scope in a written proposal. The requirements analysis ends in a written proposal covering scope, phases and price, and we agree the pilot line and its success criteria at that stage.
- We build the MES around your line's rules. Our MES production management service covers work orders, downtime and scrap, OEE, batch tracking and shift reports, configured for your plant; quality checks can be linked to a quality management system where needed.
- We connect it to your ERP. Our MES integrates with Logo, SAP, Mikro and custom ERP systems (Logo and Mikro are widely used Turkish ERP packages). We build the field-mapping table with you and draw the boundary on the ERP side from the start; the technical transfer options are summarised in our API integration guide.
- Hardware comes from the same team. Operator terminals, barcode equipment and machine signal collection are installed by one team; see our industrial data terminals page for the shop-floor side.
Technical support continues 24/7 after go-live. To see where MES sits in a broader plan, read our Industry 4.0 roadmap for SMEs or browse all our Industry 4.0 articles.
How to start your MES implementation this week
This week, pull together the master data for the line you would pilot: product codes, routings, cycle times and the downtime reasons you use today. Compare it with the phase-by-phase readiness table; every gap is a risk to your timeline. If you would like to fill in that table together and plan a site assessment, get in touch through our contact page.