Most factories that fail with MES don't fail because of the software. They fail because of the rollout: too much scope, screens operators won't use, missing data, and no one on the floor who owns the result. This roadmap is built from what works for small and mid-sized plants — a phased plan where every phase delivers something useful.
Step 0: Decide what problem you are solving
"We want Industry 4.0" is not a goal. Before scoping any software, write down the two or three business problems MES must solve. Good examples:
- "We don't know where orders are until someone walks the floor — on-time delivery is 70%."
- "Our biggest customer wants lot traceability within one hour."
- "We think OEE on the CNC cell is low but have no reliable data."
- "Rejections are high and we don't know the top causes."
Each problem points to specific MES functions. Delivery visibility points to job booking and WIP. Traceability points to material scanning and genealogy. OEE points to downtime capture. This keeps scope honest.
Step 1: Map the current process on the floor
Spend a day on the shop floor with the people who do the work. Follow two or three orders from release to dispatch and record:
- What documents travel with the job (route card, drawing, inspection sheet).
- Every point where someone writes something down — and what happens to that paper.
- Where jobs wait, and why.
- How downtime and rejects are recorded, if at all.
- Which questions supervisors and planners answer by phone or by walking.
This map becomes the blueprint for MES screens. Software designed from the office almost always misses the reality of the floor.
Step 2: Define the minimum useful scope
For a first phase, choose the smallest set of functions that solves your top problem. For most plants that is:
- Barcoded job cards printed from the production order.
- Operation start / pause / complete with good and rejected quantity.
- Downtime with a short list of reasons.
- A live WIP and order status dashboard.
Everything else — inspections, material genealogy, machine signals, scheduling, costing — goes on the roadmap for later phases.
Step 3: Choose the pilot line
Pick one line or cell. The ideal pilot is important enough that results matter (a bottleneck, or a key customer's product), stable enough that the pilot isn't drowned in daily firefighting, and run by a supervisor who is open to change. Avoid piloting on your most chaotic area — you want a visible win within weeks.
Step 4: Prepare the master data
MES runs on master data. Before go-live you need:
- Items and routings — products with their sequence of operations and work centres.
- Machines and work centres — with IDs that match labels on the floor.
- Operators — names, IDs and, ideally, skills.
- Reason codes — 10–15 downtime reasons and 10–20 defect codes, agreed with supervisors.
- Standard times — ideal cycle times, if you want performance and OEE.
Data preparation is usually the longest task on the client side. Start it in parallel with software development.
Step 5: Design shop-floor screens with operators
This step makes or breaks adoption. Sit with two or three operators and test paper or clickable prototypes. Rules that work:
- Booking an operation should take two or three taps, or one scan.
- Use scanning rather than typing wherever possible.
- Big buttons, high contrast, readable from a metre away.
- Labels in the language operators actually use.
- No mandatory fields that operators can't know.
- Show the operator something useful back — their target, the drawing, the next job.
Step 6: Hardware and network
Keep hardware simple. Most first phases need only:
- Android tablets or rugged phones at workstations (one per cell is often enough).
- A label printer for job card and material barcodes.
- Reliable Wi-Fi on the floor — check coverage before go-live; dead zones kill adoption.
- A TV for the WIP dashboard.
Machine connectivity — PLC signals, sensors, counters — can come in a later phase. It's valuable, but it should not delay the first phase. Hardware and any third-party licences are the client's purchase.
Step 7: Build in short iterations
Develop in two-week cycles and demo working software to the pilot supervisor each time. Early feedback catches the details that make or break floor adoption — the extra field nobody can fill, the button in the wrong place, the report that shows the wrong shift boundary.
Step 8: Train on the floor, not in a meeting room
Train operators at their workstations, during their shift, in short sessions. Make one operator per shift a "champion" who helps others. Print a one-page picture guide and stick it beside the tablet.
Step 9: Parallel run, then cut over
Run paper and MES together for one to two weeks. Compare totals daily. Fix gaps. Then remove the paper — if paper stays, people will keep using it.
Step 10: Make supervisors use the data daily
The fastest way to kill an MES is to collect data nobody looks at. Put the WIP board and yesterday's downtime Pareto at the centre of the daily production meeting. When operators see that the reasons they enter lead to action — a recurring tool problem fixed, a material delay escalated — booking compliance rises.
Step 11: Measure against the baseline
Before go-live, record the baseline: on-time delivery, lead time, rejection rate, and (if possible) estimated utilisation. After eight to twelve weeks, compare. Track booking compliance too — the percentage of operations booked on time. If it's low, fix usability before adding scope.
Step 12: Roll out and extend
Once the pilot is stable, roll out line by line, reusing the same screens and training. Then add phases from the roadmap:
- Quality: in-process inspections, NCR and CAPA.
- Traceability: material lot scanning and genealogy.
- Machine data: automatic run/stop and counts for OEE.
- Planning: production scheduling fed by live MES status.
- Integration: completed quantities and consumption to ERP or accounting, where it offers an interface.
Common pitfalls checklist
- Scope creep in phase 1 — park ideas on the roadmap.
- Master data not ready — start early, assign an owner.
- Weak Wi-Fi — survey before go-live.
- No floor owner — the production head must sponsor it.
- Reports nobody reads — design reports for the daily meeting.
- Waiting for perfect machine integration — don't.
Where to start
If you'd like a second opinion on your MES plan — or want us to build it — we're happy to walk your pilot line with you (on site or by video) and propose a phase-one scope. See our MES software page or contact us.
Frequently asked questions
Which line should we pilot MES on?
Choose a line that matters (a bottleneck or a key customer's product) but isn't your most chaotic. You want a visible win within weeks.
Do we need new hardware?
Usually only rugged tablets or Android devices, barcode labels and possibly label printers. Machine connectivity hardware is optional and can come later. Hardware is purchased by the client.
How do we get operators to actually use it?
Design screens with them, keep booking to two or three taps, use scanning instead of typing, train on the floor, and make sure supervisors use the data in daily meetings.
What should we measure to know MES is working?
Booking compliance first, then WIP accuracy, on-time delivery, downtime minutes by reason, OEE and rejection rate compared with the pre-MES baseline.
