How Is an MES Project Implemented? Steps and Timeline

How Is an MES Project Implemented? Steps and Timeline

An MES project is the phased implementation process from defining the scope of a manufacturing execution system to it being used on the shop floor. It typically consists of needs analysis, master data preparation, setting up the data collection infrastructure, configuration, validation on a pilot line, training, roll-out and post-go-live improvement.

In brief

  • The project is not a software installation but a change in the way people work; shop-floor teams must be involved from the start.
  • Critical prerequisite: master data (products, routings, machines, downtime codes, operators) must be clean and unique.
  • Typical path: pilot line → validation → roll-out; a measurable acceptance criterion is written for each phase.
  • Duration: a pilot scope takes a few months; a plant-wide, multi-module implementation is usually on the order of a year, split into phases.
  • The measure of success is not installation but use: what share of records are entered on the shop floor, on time and correctly?

The Project Flow Step by Step

  1. Setting goals and scope. Which problem will be solved? Write concrete goals, not “seeing OEE”, but things like “measuring and reducing setup losses” or “presenting lot history within minutes in a customer audit”.
  2. Current state analysis. Shop-floor forms, the machine park, existing automation, the data structure in the ERP and existing reports are examined.
  3. Master data preparation. Product codes, BOMs, routings, the machine list, shift calendar, and downtime and scrap reason codes are defined. This step is the most underestimated part of projects and the one that causes the most delays.
  4. Data collection infrastructure. Which signal will be read from which machine and with which protocol is determined; retrofit solutions are planned for old machines, and network and terminal locations are finalised.
  5. Configuration and integration. Screens, permissions, reports and KPI definitions are set up; the exchange of work orders, products and production confirmations with the ERP is defined.
  6. Pilot. A single line or department runs with real production for 4-8 weeks. Data accuracy, the difference between counters and the system, and operator usage time are measured.
  7. Training. Role-based training is given to operators, supervisors, quality, maintenance and planning; screen guides are posted on the shop floor.
  8. Roll-out. The set-up corrected in the pilot is moved to the other lines; a go-live checklist is used for each line.
  9. Post-go-live improvement. In the first months, downtime codes are simplified, reports are revised and alert thresholds are tuned.

Expected Timeline

PhaseContentTypical weight
Analysis and master dataScope, code structures, routings and BOMsThe longest preparation item in the project
InfrastructureConnectivity, terminals, network, serversProportional to machine variety
Configuration and integrationScreens, reports, ERP exchangeDepends on the number of modules
PilotValidation in real production4-8 weeks
Roll-outLine-by-line go-liveShort and repetitive per line

The biggest variable determining duration is not the software but the state of the master data and the variety of the machine park. In a plant with a messy code structure, preparation can take longer than configuration.

Who Takes Part?

  • Project owner (sponsor): The manager responsible for production; resolves priority conflicts.
  • Key users: One person each from production, quality, maintenance and planning; approve scope and tests.
  • IT: Servers, network, backup, authentication and the ERP connection.
  • Automation/maintenance: Machine signals, PLC access, retrofit work.
  • Shift supervisors: Responsible for changing operator habits; build daily usage discipline.

Common Mistakes

  • Rolling out everything at once: Opening all modules in one go makes troubleshooting impossible.
  • Collecting master data in parallel with the project: Starting a pilot while routings and downtime codes are not ready turns the pilot into data cleansing.
  • Running paper in parallel: A long parallel period leaves both records incomplete.
  • Rolling out without designing the operator screen: Screens that take long to use are abandoned on the shop floor.
  • Not writing acceptance criteria: If “it went live” is not measurable, the project never ends.

Frequently Asked Questions

How long does an MES project take?
It depends on scope and plant size. A pilot focused on production monitoring on a single line can go live within a few months, while a plant-wide implementation covering quality, traceability, maintenance and ERP integration is usually spread over a year, split into phases.
Which module should you start with?
In most plants, production monitoring and downtime recording are the first step, because they build the data infrastructure and deliver visible gains quickly. But if there is pressure from customer audits, traceability can be brought forward; if quality costs are high, the quality module.
What is the most common mistake in an MES project?
Treating the project as purely an IT job. An MES changes the way work is done on the shop floor; if production, quality and maintenance teams do not take part in scoping and testing, the system is not used or produces wrong data.

Project Implementation in EFFIX MES

EFFIX MES has a modular structure; production monitoring, quality, maintenance, traceability, planning and energy modules can go live in separate phases. On the master data side, products, routings (BOP), BOMs, machines and downtime codes are configured with dynamic definition screens; multi-site support makes the roll-out phase easier. Because the Inolink wireless IoT network and protocols such as OPC UA, MQTT, Modbus, MTConnect and Euromap are used for data collection, a machine park of different ages can be brought into a single set-up. On the ERP side, receiving work orders and sending production/scrap confirmations are defined with SAP, IFS, Netsis and generic adapter options; user permissions are managed with LDAP/Active Directory. Backup, version management and security gates are ready for post-go-live operation. For details, see the EFFIX MES page or request a demo.