What to prepare before an MES goes live
Most MES problems are not missing features. They come from routings, data and responsibilities that were never aligned before go-live. These seven checks can be done during selection.
1. One definition of operations and work orders
If the shop floor calls an operation one thing, the routing document another and the ERP a third code, reporting and traceability will drift. Agree the operation list, coding rules and work order splitting rules, and name an owner.
2. Master data you can actually import
Materials, BOMs, routings, equipment, teams and defect codes need an importable version. Without master data the system can record what happened, but not what should have happened.
3. Where the data comes from
- Manual reporting: simplest, accept the delay while the flow is proven.
- Barcode or station terminals: for many operations and precise batch traceability.
- Machine data: depends on protocols, gateways and shop-floor networks; assess retrofit scope and downtime.
All three can coexist, but every station needs a defined method and sync interval.
4. Boundaries with ERP and PLM
ERP for orders, purchasing, inventory and finance; MES for execution, reporting, quality and traceability. Decide who releases work orders, which fields return, and which system owns material codes. Unclear boundaries produce two sets of numbers that never reconcile.
5. Roles and permissions
Can a team leader resequence work orders? Can quality lock a batch? Who confirms returned quantities from subcontractors? Permissions decide whether the process can actually be followed. Walk through exception scenarios with real roles before go-live.
6. Acceptance metrics
Write targets as measurable numbers: reporting timeliness, on-time work order completion, traceability query time, monthly inventory variance. Without metrics, acceptance becomes a matter of opinion.
7. Rollout pace and training
Pilot on one line or workshop for two to four weeks across a full production cycle, then expand. Train by role and keep a paper or spreadsheet fallback so the first day does not stop production.
Questions we often hear
Does MES always require machine data collection?＋
No. Start with manual reporting and work order flow so operations, quantities, defects and owners are recorded, then add machine data for critical stations in stages. Whether machines expose an interface and can be modified must be confirmed on site.
Is MES suitable for high-mix, low-volume production?＋
Yes, but the design focus differs. High-mix production depends on flexible work order splitting, fast changeovers and routing changes, and reporting must follow batches and orders rather than a fixed line takt.
Where is the boundary between ERP and MES?＋
A common split is ERP for orders, purchasing, inventory and finance; MES for work order execution, operation reporting, quality and traceability. Both sides need shared material, work order and operation codes, with one agreed master source.
Assessing MES?
Start with operations, work orders and data sources, then decide between product configuration, custom development and interface integration.
Discuss your project ↗