How to choose MES software

This guide uses the decisions in our evidence library. Many of those sources come from MES vendors, so they show what manufacturers reportedly did and why. They do not show that one MES is better than another.

1. Start with the way the plant actually manufactures

The same MES question looks different in different plants. Scanfil documented high-mix, low-volume electronics at Suzhou, with orders of about 150 to 200 pieces and frequent line changeovers. Greenheck Group needed support for configure-to-order production. Terumo Americas makes regulated medical devices under FDA requirements. Write down your production type, order patterns, and regulatory needs before you look at products.

2. Define what you are replacing

Starting points in the records vary widely:

• Fragmented systems: Carolina Nonwovens ran a 1999 ERP, a separate MRP system, Excel tracking, and paper quality sheets.
• Homegrown software: SMART Modular Technologies used an internally developed WIP tracking system plus Excel.
• An existing MES: Terumo had Camstar in place, and Milwaukee Electronics had used earlier Aegis software since 2011.
• A greenfield plant: HT Micron needed MES quickly to support customer qualification at a new facility.

Each starting point changes what the project must replace, migrate, or build from nothing.

3. Understand ERP and shop-floor integration early

MES rarely stands alone. Scanfil sends production reports back to its ERP for routing control and traceability. Milwaukee Electronics later documented integration with Epicor ERP and with SMT and X-ray systems. Terumo paired its MES with SAP S/4HANA, and Greenheck named SAP integration, including variant handling, as a selection factor. Ask which systems and equipment must connect, and who builds each connection.

4. Turn manufacturing requirements into vendor requirements

HT Micron started with more than 500 customer requirements, identified which ones the MES had to meet, and sent them to finalists. Greenheck defined detailed requirements, issued RFIs, and ran technical assessments. Traceability, routing control, SPC, and quality workflows appear as explicit requirements across several records.

5. Evaluate vendors against your own processes

BIC began by observing real shop-floor work and documenting processes before choosing solutions. In the biologicals CDMO selection, workshops documented current processes and user requirements, and vendor demonstrations, proposals, and total cost of ownership were scored against them. A generic feature checklist does not test how a system handles your workflows.

6. Treat implementation as part of the purchase

Several records describe how the work was staffed and phased. Carolina Nonwovens assigned dedicated internal resources and went live just over five months after starting. Koller Enterprises implemented at five plants with internal champions and staggered go-lives. BIC started with a pilot plant. Terumo phased its large Elkton site by value stream and chose to build knowledge internally. Implementation partners are named in some records. Ask who does what: the vendor, a partner, or your team. Our MES implementation guide covers these examples in more detail.

7. Check the evidence behind vendor claims

Most sources here are vendor case studies or announcements. They are useful for learning what a manufacturer did, but reported results are not independently verified. Look for manufacturer publications, like Scanfil's own announcement, and for corroborating sources. Our evidence quality ratings explain how we weigh this.