MES implementation: what real manufacturing rollouts look like

This guide draws only on the published records in our evidence library. Most sources are vendor case studies or announcements. Read them as documented examples, not as industry benchmarks or verified results.

What MES implementation can include

The records describe much more than installing software. Before choosing solutions, BIC observed actual shop-floor work, documented processes, and examined existing systems to decide what to replace or improve. In the biologicals CDMO selection, workshops documented current business, IT, and manufacturing processes, user requirements, and pain points. Other records add data flows to ERP, quality workflows, traceability, training, and the scope of each go-live.

Pilot, phased rollout, or broader deployment?

The documented approaches differ:

• BIC began with its Bizerte, Tunisia facility as an initial pilot under a multi-site agreement. The pilot covered 90 machines at varying levels of automation and approximately 400 employees.
• Terumo Americas used a phased approach by value stream at its large Elkton, Maryland site.
• HT Micron phased its greenfield plant: the first deployment focused on core MES needs, with later phases intended to add capabilities such as automation and maintenance.
• Koller Enterprises implemented at five plants concurrently, with staggered go-lives so teams could learn from one another.
• Carolina Nonwovens went live without running parallel systems.

The biologicals CDMO identified possible pilot processes during selection. The source does not say whether a pilot was carried out. None of these records shows that one approach is better in general.

How long does MES implementation take?

• Carolina Nonwovens: implementation began in late April 2024, and the company went live just over five months later.
• Koller Enterprises: the full implementation across five plants spanned approximately one year. Individual divisions transitioned in approximately five to six months.
• HT Micron: software implementation took place in October and November 2014, test lots and employee training followed in December, and production was tracked in MES from January 1, 2015. The vendor announcement is titled "in record time", so this should not be read as a normal speed.

Comparing these dates directly can mislead. Carolina Nonwovens replaced fragmented systems, Excel tracking, and paper quality sheets at two facilities. Koller moved five plants. HT Micron was ramping up a new plant with a core first phase. Scope, starting point, manufacturing environment, and integrations all differ.

Who needs to be involved internally?

Carolina Nonwovens assigned dedicated internal resources exclusively to the project. Koller Enterprises appointed internal champions within its divisions. Terumo emphasized building knowledge internally rather than depending entirely on external partners. Carolina Nonwovens and Koller both worked with an implementation partner, Cumulus Consulting.

Where ERP and shop-floor integration enter the project

Integration shows up as part of the implementation itself. At Scanfil's Suzhou factory, the first Scanfil factory to use Siemens Opcenter, the MES returns production-report information to the ERP in a closed-loop data flow for routing control, traceability, and data collection. Terumo intended SAP S/4HANA, its ERP standard, and Siemens Opcenter Execution for Medical Device and Diagnostics to connect business logistics with manufacturing operations. Milwaukee Electronics later documented integration with Epicor ERP and with production systems including SMT and X-ray systems.

What the records show happening before go-live

The examples do not add up to one method, but several recurring steps appear: mapping current processes (BIC, the biologicals CDMO), turning requirements into vendor requirements (HT Micron sent its requirements to finalists), identifying pilot candidates, running test lots and training (HT Micron), and deciding the first scope of a phased rollout. For how these steps connect to vendor selection, see how to choose MES software.

Questions to settle before signing

• What exactly are we replacing?
• Which ERP, machines, and shop-floor systems must connect?
• What manufacturing processes must the MES support?
• Should we begin with a pilot, a value stream, one plant, or a broader rollout?
• Who on our team will own the implementation?
• What work belongs to us, the MES vendor, and an implementation partner?
• What must be tested before go-live?
• How will training and internal knowledge be handled?