[et_pb_section fb_built=”1″ _builder_version=”4.27″][et_pb_row][et_pb_column type=”4_4″][et_pb_text]<\/p>\n
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.<\/p>\n
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 \u2014 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.<\/p>\n
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.<\/strong> The 24-month filter is critical \u2014 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?<\/strong> The answer is frequently “2 of the 5 modules” \u2014 which tells you what actually works versus what is in marketing materials.<\/p>\n Question 3: How does your platform handle my specific product genealogy complexity?<\/strong> 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?<\/strong> Answers above 30% are yellow flags; above 50% are red. Question 5: Show me the data model for [specific workflow you care most about].<\/strong> 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?<\/strong> Forced annual upgrades often cost as much as a new implementation \u2014 know what you’re committing to.<\/p>\n 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?<\/strong> “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.<\/strong> Live demos beat marketing claims. Question 9: Who is responsible for PLC-level data mapping \u2014 you, your integrator, or our internal automation team?<\/strong> Answers that distribute responsibility unclearly mean the cost will fall on you.<\/p>\n Question 10: What is the typical duration and cost of SAP integration for a plant of our size?<\/strong> 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)?<\/strong> Historian integration is often forgotten in scoping but essential for OEE. Question 12: What happens to integration when either system is upgraded?<\/strong> Weak integration architectures break on every SAP patch. Ask for examples of customers managing through major version upgrades.<\/p>\n 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?<\/strong> 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?<\/strong> 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?<\/strong> Many MES platforms systematically miss micro-stops, producing OEE numbers 10-18 points higher than reality.<\/p>\n Question 16: Show me the Pareto analysis interface that operators actually use.<\/strong> Distinct from the executive dashboard, this is where the value lands. Question 17: What is the latency from event occurrence to dashboard update?<\/strong> 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?<\/strong> Reason code workflows are where operator buy-in is won or lost.<\/p>\n Instant download. No email confirmation needed.<\/p>\n \n Category 2: Integration Reality (Questions 7-12)<\/h2>\n
Category 3: OEE and Production Performance (Questions 13-18)<\/h2>\n
Download the free Excel checklist<\/h3>\n