The MES Buyer’s Checklist: 42 Questions to Ask Before Signing the Contract in 2026

An MES selection is one of the higher-stakes decisions a manufacturing operation makes in any given five-year window. The software touches production scheduling, quality records, genealogy, labor tracking, OEE reporting, and often integrates with SAP, PLCs, quality labs, and maintenance systems. The deployment typically runs 6 to 18 months with fully-loaded costs between $400K and $4M for mid-market plants, and longer and more expensive for enterprise deployments. The platform chosen in 2026 will likely be running the plant in 2032. The consequences of a bad pick are proportionally large.

Most MES buyers go into the selection process with a narrow view of the questions that matter. They focus on feature-list comparisons, vendor references, and pricing — and discover in month 9 of implementation that the platform does not actually support their real production workflow, or that the reference customer they talked to uses only 30% of the modules, or that the pricing doubles when mandatory integration modules come online. This checklist is built from the specific failure patterns we have observed across 450+ factory deployments over the past decade. The 42 questions below are organized into seven categories and reflect what actually matters for delivery, not what sounds good in a demo.

Category 1: Scope Fit (Questions 1-6)

The first category separates MES vendors who can deliver your specific scope from those who will try to fit your scope into their default framework. Question 1: Show me three customers in my industry with similar scope to mine, running the platform in production for at least 24 months. The 24-month filter is critical — plenty of vendors have 6-month-old deployments that look great but have not yet hit the real operational stress. Question 2: Of the modules quoted in my package, which are you actually deploying in production at those three references? The answer is frequently “2 of the 5 modules” — which tells you what actually works versus what is in marketing materials.

Question 3: How does your platform handle my specific product genealogy complexity? Bring a real BOM from a real product and have them walk through the data model. Vendors who cannot do this concretely in a 45-minute meeting cannot do it during a 9-month implementation either. Question 4: What percentage of your reference implementations required custom development beyond the base product? Answers above 30% are yellow flags; above 50% are red. Question 5: Show me the data model for [specific workflow you care most about]. Concrete data model walk-through reveals whether the fit is structural or cosmetic. Question 6: What is your release cadence for the platform, and what is the customer’s upgrade obligation? Forced annual upgrades often cost as much as a new implementation — know what you’re committing to.

Category 2: Integration Reality (Questions 7-12)

MES integration is where 60% of cost overruns happen. The questions here surface whether integration is real or aspirational. Question 7: What are your out-of-the-box integrations for SAP/Oracle/Microsoft ERP, and which versions? “Supports SAP” is not an answer; specific SAP versions and connector types are. Question 8: Show me a working PLC integration for my specific PLC brand and model (Siemens S7-1500, Rockwell CompactLogix, etc.) at an existing customer. Live demos beat marketing claims. Question 9: Who is responsible for PLC-level data mapping — you, your integrator, or our internal automation team? Answers that distribute responsibility unclearly mean the cost will fall on you.

Question 10: What is the typical duration and cost of SAP integration for a plant of our size? Get specific numbers; hedges like “depends on your environment” suggest they do not know or do not want to say. Question 11: How does your platform handle historian data (OSIsoft PI, Aveva, Canary)? Historian integration is often forgotten in scoping but essential for OEE. Question 12: What happens to integration when either system is upgraded? Weak integration architectures break on every SAP patch. Ask for examples of customers managing through major version upgrades.

Category 3: OEE and Production Performance (Questions 13-18)

Most MES vendors claim OEE capabilities. Fewer deliver accurate OEE measurement. Question 13: At your 24-month reference customer, what is the measured accuracy of OEE numbers in your platform versus their actual production? If the answer is “we don’t measure accuracy,” that itself is the answer. Question 14: Does your OEE measurement come from PLC events, operator entry, or direct sensors? Different architectures have different accuracy profiles; you need to know which you are buying. Question 15: How are micro-stops (under 5 minutes) captured in your OEE calculation? Many MES platforms systematically miss micro-stops, producing OEE numbers 10-18 points higher than reality.

Question 16: Show me the Pareto analysis interface that operators actually use. Distinct from the executive dashboard, this is where the value lands. Question 17: What is the latency from event occurrence to dashboard update? Acceptable is under 60 seconds; some legacy MES platforms have 5-15 minute latencies that make real-time management impossible. Question 18: Can operators enter reason codes during the stop via tablet or HMI, and how are those codes categorized? Reason code workflows are where operator buy-in is won or lost.

Category 4: Total Cost of Ownership (Questions 19-24)

Initial license is typically 20-40% of TCO. The rest is implementation, integration, training, support, and upgrades. Question 19: Break down the first three-year TCO: license, professional services, training, support, infrastructure, upgrades. Vendors who resist breakdown are typically hiding implementation or integration costs. Question 20: What is the cost structure when I add a second plant? Third plant? Platform pricing models vary wildly; some become prohibitive at scale. Question 21: What are the mandatory annual costs to remain current and supported? This is the number that matters in year 4, not the license number in year 1.

Question 22: What happens to my costs if my production volume grows 30% in year 2? Some MES pricing is consumption-based and scales with volume; others are not. Know which you are buying. Question 23: What is the realistic total implementation cost from contract signing to go-live? Include vendor services, system integrator services, internal labor, training. Question 24: What are the cancellation terms if the implementation stalls? Real answer matters when things go wrong.

Category 5: Implementation Partner (Questions 25-30)

The system integrator often matters more than the software. Question 25: Will the vendor implement directly, or through a partner network? Partner implementations have wider quality variance. Question 26: Can I see the CVs of the specific implementation team that will work on my project? Senior talent rotates out of projects; make sure you get who you were shown. Question 27: What is the typical size of the implementation team on a project of our scope? Thin teams mean longer timelines.

Question 28: What is the governance structure during implementation, and how are change requests handled? Change requests are where scope creep happens; governance matters. Question 29: At your three reference customers, how did the implementation compare to the original plan in timeline and budget? Overruns over 20% are typical red flags. Question 30: What happens to my project if my primary integrator leaves or the partner company is acquired? Contingency planning matters more than nobody admits.

Category 6: Data Ownership and Exit (Questions 31-36)

This category is often skipped during the honeymoon of contract negotiation. It becomes critical in year 5-7. Question 31: Do I own my production data, or does your platform? Answers vary; never assume. Question 32: What is your policy on data export in standard formats? Proprietary-only exports are lock-in traps. Question 33: If I decide to migrate off your platform, what is the realistic cost and duration? Lock-in pricing manifests here.

Question 34: How long do you retain my historical data after contract termination? 30-day windows are common and often insufficient. Question 35: What are your cybersecurity certifications (SOC 2, ISO 27001)? For regulated industries, these are not optional. Question 36: What is your incident response SLA for security breaches affecting my data? Know the answer before you need it.

Category 7: Future-Proofing (Questions 37-42)

The platform you choose will still be running in 2032. Question 37: What is your product roadmap for the next 24 months, and what have you delivered from the previous 24-month roadmap? Delivery track record predicts future delivery. Question 38: How does your platform handle AI/ML integration — is this built-in, partner-dependent, or DIY? This capability gap will grow over the next 3 years. Question 39: Is your platform cloud-native, on-premise, or hybrid, and what is your long-term direction? Misalignment here creates migration costs in year 4-5.

Question 40: What is your financial stability? Revenue, profitability, growth rate? The platform outliving your vendor is a real risk. Question 41: Who are your three largest competitors, and what is your specific differentiation versus each? Vendors who cannot answer clearly do not understand their own position. Question 42: If I come back in 18 months and say the platform is not working, what is your remediation process? The answer tells you how seriously they take long-term customer success.

How to use this checklist — scoring methodology

The checklist works best with a structured scoring approach. For each question, score the answer 1-5 where 1 = evasive or concerning, 3 = acceptable, 5 = concrete and strong. Weight categories by your plant’s priorities — for example, heavily regulated industries weight Category 6 (Data Ownership) higher, plants with complex SAP environments weight Category 2 (Integration) higher. Calculate weighted scores per vendor and compare.

Plants using this methodology typically find that vendor rankings based on the full checklist differ significantly from rankings based on demos alone — often by 30-50% in final score. The difference is the value of structured due diligence versus marketing-driven evaluation.

When MES is not the right answer

Approximately 40% of plants that begin MES selection processes should actually not buy MES. Their primary needs — OEE measurement, downtime analysis, operator productivity visibility — are solvable with direct-sensor IoT platforms at 10-20% of MES cost and 2-6 weeks deployment versus 6-18 months. Full MES is the right answer when regulated batch records, complex scheduling, genealogy, or enterprise-scale integration are primary drivers. Otherwise, lighter alternatives deliver 80% of the value at dramatically lower total cost.

The 42-question checklist itself surfaces this clarification: if Categories 1-2 show weak vendor fit for your specific scope, and Categories 3-4 show OEE and TCO that could be met by simpler platforms, the checklist output is pointing you away from MES, not toward a specific MES vendor. That is a legitimate and valuable outcome.

Test a direct-sensor OEE alternative to MES — Free 48-hour POC
Measure your OEE, identify top Pareto causes, estimate MES-alternative TCO — all in 48 hours
Request a free TeepTrak POC

External references: Wikipedia: Manufacturing Execution System · MESA International · ISA-95 Standard

See also: MES RFP Template — How to Structure Vendor Proposals · MES Alternatives: When a Lightweight OEE Platform Beats Full MES · OEE Software Overview