The ADKAR Model for Change Management: A Complete Guide
The ADKAR model is Prosci's five-stage framework for individual change management. Learn what each stage means and how to apply it step by step.
Learn the key steps to implement MES software in your factory: from needs assessment and system selection to staff training, configuration, and deployment.
A Manufacturing Execution System (MES) is software designed to manage, monitor, and control production processes on the factory floor in real time. Implementing one successfully requires a structured sequence of steps: needs assessment, system selection, configuration, staff training, pilot testing, and phased rollout. A typical MES implementation takes 8 to 12 months from requirements gathering to full deployment.
This guide covers each stage of the process in detail, with practical guidance on what a manufacturing execution system does and how to roll one out without disrupting live production. Whether you are starting your first MES project or replacing a legacy system, the framework below applies to discrete, process, and hybrid manufacturing environments.
MES software monitors, tracks, documents, and controls the process of manufacturing goods from raw materials to finished products. It sits between the plant floor and enterprise-level systems such as an ERP (Enterprise Resource Planning), bridging operational data with business planning. Key functions typically include production order management, real-time traceability, quality control, resource scheduling, and basic data management.
Implementation matters because MES software only delivers value when it is correctly configured to your processes, integrated with your existing systems, and actually used by operators on the floor. A poorly planned rollout leads to low adoption, data gaps, and a return on investment that never materializes. The steps below are designed to prevent exactly that.
Start by defining the scope and objectives of your project before evaluating any software. A clear needs assessment prevents scope creep and ensures the chosen system actually solves your operational problems.
Take inventory of existing infrastructure: machines, controllers, SCADA (Supervisory Control and Data Acquisition) systems, ERP connections, and manual paper-based steps. Document where data is lost, delayed, or inaccurate. Identify the production lines, shifts, and facilities the MES will cover from day one.
Establish the minimum set of functions the system must deliver. Common baseline requirements include:
Attach measurable targets to each requirement. For example, instead of "improve traceability," specify "reduce the time to trace a batch recall from 4 hours to 30 minutes." These targets become the validation criteria in step 6.
MES implementation is as much a people project as a technology project. Assess how operators, supervisors, and quality teams currently interact with production data, and identify the roles most affected by the change. Resistance from experienced floor workers is common, and early stakeholder involvement reduces it significantly.
"At first there was distrust. They were veterans, 57-58, afraid of losing their jobs: once our knowledge is in a new tool, anyone can do our job."
System selection should follow directly from your documented requirements. Evaluate vendors against the functional checklist you built in step 1, and verify integration capabilities before signing any contract.
The MES must exchange data with your ERP, SCADA, laboratory information systems, and any warehouse management tools in use. Confirm that the vendor supports the communication protocols your plant uses (OPC-UA, REST API, SQL connectors, or others). Integration failures are among the most common causes of MES project delays.
Ask each vendor how process owners can adapt workflows, forms, and reports after go-live. Platforms that support no-code or low-code configuration reduce dependency on the vendor for routine changes. This is especially relevant for manufacturers who need to respond quickly to new product introductions or regulatory changes.
Review the vendor's implementation methodology, reference customers in your industry, and the availability of certified integrators. A structured implementation methodology from the vendor reduces project risk. For a detailed breakdown of evaluation factors, see the guide on criteria for choosing MES software.
A detailed project plan is the foundation of a successful MES rollout. Treat it as a living document that is updated as the project progresses.
A realistic MES implementation timeline looks like this:
| Phase | Typical Duration | Key Activities |
|---|---|---|
| Requirements and selection | Months 1-2 | Needs assessment, vendor evaluation, contract |
| Design and configuration | Months 3-4 | System design, data mapping, integrations |
| Testing and training | Months 5-7 | UAT, staff training, pilot environment |
| Pilot deployment | Months 8-9 | Single line or cell go-live, issue resolution |
| Full rollout and optimization | Months 10-12 | Remaining lines/facilities, KPI review |
Effective MES projects include representatives from operations, IT, quality, and maintenance. Assign a project owner with authority to make decisions and resolve cross-departmental conflicts. Define RACI (Responsible, Accountable, Consulted, Informed) roles before the design phase begins so that accountability is clear at every stage.
MES systems depend on accurate master data: work centers, bill-of-materials structures, routing steps, and shift definitions. Audit your master data before configuration begins. Corrupted or incomplete master data is one of the most common causes of go-live delays.
Configuration translates your process requirements into working system behavior. It is typically led by a certified integrator working with your internal team.
The MES process flow mirrors the physical sequence of operations on your floor. Map each routing step, define the data to be collected at each operation (quantities, machine parameters, operator ID, quality checks), and configure the work instructions or electronic job cards operators will use.
Connect the MES to your ERP to receive production orders and return actuals. Connect to SCADA or PLC (Programmable Logic Controller) layers to collect machine data automatically. Test each integration in a sandbox environment before moving to production data.
Define inspection plans, control charts, and non-conformance workflows. Set up lot or serial number assignment rules so that traceability is enforced from the first production step. These configurations directly determine the value the system delivers for regulatory compliance and product recalls.
Staff training is one of the highest-risk steps in any MES project. Operators who do not understand the system will work around it, producing the data gaps that make the MES unreliable for planners and quality managers.
Operators need task-level training on the specific transactions they perform: clocking onto a work order, recording scrap, completing a quality check. Supervisors need training on monitoring dashboards and exception management. IT and maintenance staff need system administration and troubleshooting skills.
Classroom training alone is rarely sufficient for shop-floor staff who do not use a computer in their normal day. In-application guidance, delivered as step-by-step walkthroughs directly inside the MES interface, helps operators complete transactions correctly without needing to remember everything from a classroom session. Lemon Learning's digital adoption platform for manufacturing overlays contextual guidance on top of MES software, so operators get the right instruction at the right moment on the shop floor.
New hires, process changes, and software updates all create new training needs after go-live. Build a sustainable MES training program that includes refresher content and onboarding paths for new operators, not just a one-time launch event. For a broader look at how to structure this, the learning and development solutions page covers approaches that work across enterprise software deployments.
Testing confirms that the configured system behaves as designed and that it meets the success criteria defined in step 1. It also gives operators safe exposure to the system before production pressure is added.
UAT (User Acceptance Testing) should involve actual operators and supervisors, not just the IT team. Test every transaction type against real production scenarios: standard completions, scrap recording, material splits, quality holds, and shift handovers. Log defects and track resolution before setting a go-live date.
Validate the configured software in a pilot environment, either in a test cell or on a low-complexity production line. A pilot exposes integration issues, master data gaps, and usability problems before they affect the full facility. Use pilot results to refine training materials and adjust configurations.
A phased deployment approach reduces risk and allows the team to learn from each rollout wave before expanding further.
Begin MES deployment on one machine, line, or cell. Choose a production area that is representative of your operations but not your most critical or complex line. Resolve issues at this scale before expanding. This approach also creates internal champions who can support peers during broader rollout.
Once the first deployment is stable, replicate the configuration to other lines with similar process structures. Adjust for any differences in routing, machine types, or quality requirements. For facilities with significantly different processes, treat each as a separate deployment wave with its own testing cycle.
Understanding the advantages and limitations of MES software at this stage helps operations leaders set realistic expectations with plant managers during rollout.
Go-live is not the end of the project. Sustained value from an MES depends on consistent use, accurate data, and continuous improvement of both the system and the processes it supports.
Measure the success criteria defined in step 1. Common MES performance indicators include OEE (Overall Equipment Effectiveness), first-pass yield, on-time-in-full delivery, and mean time to trace a batch. Compare post-implementation figures to your documented baseline to demonstrate return on investment.
Assign ownership for master data maintenance: work center definitions, routing changes, and shift calendars. Establish a process for updating the MES when production processes change, so the system reflects reality at all times.
Operators who use the system daily will identify inefficiencies and gaps that were not visible during design. Create a lightweight feedback channel so these observations are captured, prioritized, and acted on. Continuous improvement of the MES configuration is what separates high-performing deployments from those that stagnate after go-live.
A successful MES implementation delivers real-time visibility into production, reliable traceability from raw material to finished product, and a measurable improvement in the efficiency and quality metrics that matter to the business. It also results in a workforce that is confident using the system and a technical team capable of maintaining and evolving it over time.
The steps covered in this guide, from needs assessment through monitoring and optimization, follow the implementation methodology used by leading MES vendors and integrators. The most consistent differentiator between projects that succeed and those that stall is investment in people: stakeholder involvement during design, role-specific training before go-live, and ongoing support after deployment. Technology alone does not transform a factory floor.
A typical MES (Manufacturing Execution System) implementation spans 8 to 12 months. The first two months usually cover requirements gathering and system selection, months three and four focus on system design and configuration, and the remaining time covers testing, staff training, pilot deployment, and full rollout.
The core steps are: (1) needs assessment and goal setting, (2) MES software selection, (3) implementation planning and team formation, (4) system configuration, (5) staff training, (6) testing and validation, (7) gradual deployment, and (8) ongoing monitoring and optimization.
Operators need hands-on training on the specific workflows the MES will manage on their line, including production order management, quality checks, and traceability functions. Training is typically delivered by the system integrator or software supplier and should include in-application guidance so staff can get answers in context without leaving the shop floor.
Many modern MES platforms offer no-code or low-code configuration tools that allow process owners to adapt workflows, forms, and dashboards without writing custom code. The level of customization available without programming varies by vendor, so this should be a specific evaluation criterion during system selection.
The ADKAR model is Prosci's five-stage framework for individual change management. Learn what each stage means and how to apply it step by step.
Preparing for the ITIL certification exam? Get study tips, exam format details, cost info, and a proven preparation strategy to pass on your first...
Learn what legacy application migration is, why it matters, which strategy fits your needs, and how to migrate legacy apps to the cloud step by step.