25 Things to Test in an OEE Software Demo That Vendors Never Show You Voluntarily

OEE vendor demos follow a script: the sales engineer shows live dashboards, a polished mobile app, and the features most likely to impress. What they don't show is how the system behaves under real conditions, when connectivity drops, when a new machine type is encountered, when you need to run a report across 12 sites.

The goal of your demo is to stress-test the system in conditions that reflect your actual operating environment. The 25 tests below are organized into four categories: connectivity and edge, data and reporting, OEE-CMMS integration, and implementation realism. Always run tests yourself, every system looks smooth when operated by someone who built it.

• Disable WiFi, does the OEE display continue updating?
• Reconnect WiFi, does it sync automatically?
• Show live OEE updating in real time, what is the refresh latency?
• Show how a speed loss (reduced cycle time) registers in OEE performance rate
• Enter a downtime reason code as an operator would, how long does it take?
• Demonstrate connectivity for your specific PLC brand
• Show sensor-based connectivity for a machine without a digital output

Data and Reporting (8 tests)

• Generate OEE for 6 machines side by side for the last 30 days
• Show MTBF trend for a specific asset over 12 months
• Build a custom report without vendor assistance in under 10 minutes
• Schedule an automated report delivery to an email address
• Show shift-level OEE comparison across last 4 weeks
• Export 12 months of OEE data in CSV format
• Show how planned maintenance downtime is excluded from OEE calculation
• Demonstrate the audit trail for a modified downtime event

OEE-CMMS Integration (6 tests)

• Create a CMMS work order from a current OEE downtime event, how many steps?
• Show the asset record in both OEE and CMMS, is it the same record?
• Show a report combining OEE availability trend with PM compliance rate
• Show what happens to OEE data if the CMMS server has downtime
• Demonstrate automatic work order creation from an OEE threshold breach
• Show the API response for an OEE event, what CMMS data is included?

Implementation and Support (4 tests)

• Call the support line during the demo, actual hold time?
• Request a reference from a manufacturer in your industry who went live in last 18 months
• Show the onboarding timeline for a company of your size, specific or generic?
• Request the contract for review, specifically the termination clause and price escalation section

Score each test 0-2:

• 2 = Demonstrated natively, worked exactly as needed, no qualifications
• 1 = Demonstrated with limitations, worked but with caveats (custom configuration needed, certain scenarios not supported)
• 0 = Could not demonstrate, feature absent, promised for roadmap, or requires separate product

Decision Thresholds

• 45+ points: Shortlist for full RFP evaluation
• 35-44 points: Shortlist if no vendor scores higher in your priority areas
• Under 35 points: Eliminate regardless of price or brand recognition

Vendors that fail three or more tests in any single category are disqualified regardless of total score, fundamental category weaknesses reveal platform design philosophy that won't be fixed in your implementation timeline.