Integrated OEE+CMMS RFP Template: 60 Requirements for Both Functions

An integrated OEE+CMMS RFP must evaluate not just the depth of each function but the quality of the integration between them. A platform that provides excellent OEE analytics but weak CMMS work order management fails differently than a platform with strong CMMS but shallow OEE — and both fail differently than a platform that claims integration but delivers API connectivity between loosely coupled modules. The integrated RFP must include: OEE-specific requirements covering machine connectivity, loss categorization methodology, real-time monitoring capability, and multi-line reporting. CMMS-specific requirements covering work order management, PM automation, inventory management, procurement workflow, and calibration management. Integration-specific requirements covering the mechanism connecting OEE events to CMMS work orders, the shared asset data model, the unified reporting capability, and the vendor accountability for both functions. System requirements covering API access, SSO support, data export, uptime SLA, and security certifications. These four requirement categories together create the integrated platform evaluation framework that a standard OEE or CMMS RFP misses entirely.

OEE monitoring requirements (15): native PLC connectivity without additional hardware for your primary PLC brands, offline edge capability for connectivity interruption periods, real-time OEE display at line and plant level, historical OEE trend analysis with configurable periods, OEE loss categorization meeting ISO 22400 or Nakajima standard, automatic downtime detection without operator input, operator-facing downtime reason coding interface, multi-line OEE comparison dashboard, OEE target setting and variance alerting, shift-level and crew-level OEE reporting, quality rejection rate tracking with production count, changeover time tracking separately from unplanned downtime, planned maintenance downtime exclusion from OEE availability, customer-specific OEE reporting format capability, and API access to raw OEE data for external analytics. CMMS requirements (20): mobile work order creation and completion with offline sync, automated PM schedule generation with multiple trigger types, asset hierarchy with unlimited depth, spare parts inventory with reorder point automation, purchase order creation and three-way match, calibration management with NIST traceability, safety permit workflow for hazardous maintenance, contractor work order management, role-based access control, bulk PM template import, work order completion form configurability, OEE-triggered automatic work order creation, PM compliance dashboard, reactive vs planned ratio reporting, MTBF and MTTR by asset, maintenance cost per asset, ERP integration connector for your ERP, SSO support, data export in CSV and JSON, and SOC 2 Type II certification. Integration requirements (15): shared asset data model between OEE and CMMS, OEE event creates CMMS work order within 60 seconds automatically, asset attributes consistent across OEE and CMMS views, unified management dashboard combining OEE and maintenance KPIs, one vendor accountable for both OEE and CMMS support, joint OEE-maintenance root cause analysis reports, API provides both OEE and maintenance data in single connection, historical combined OEE-maintenance trend analysis, OEE improvement correlated to maintenance actions in reporting, and single login for both OEE and CMMS functions. Implementation requirements (10): reference customers in your industry deployed in last 18 months, deployment timeline for your site count and asset volume, data migration scope and timeline, training program for maintenance and operations teams, implementation project manager assignment, go-live support coverage, 30-day post-go-live hypercare period, uptime SLA above 99.5%, support response time SLA, and annual roadmap review meeting.

Weight the four requirement categories based on your primary pain point. If OEE data quality is the primary requirement (you have no OEE monitoring currently), weight OEE requirements at 35%, CMMS at 25%, integration at 25%, implementation at 15%. If maintenance cost reduction is the primary requirement (you have OEE but no CMMS), weight CMMS at 35%, integration at 30%, OEE at 20%, implementation at 15%. If data integration quality is the primary requirement (you have both OEE and CMMS but they are disconnected), weight integration requirements at 40%, CMMS at 25%, OEE at 20%, implementation at 15%. Create a weighted scoring matrix with each requirement scored 0 (not available), 1 (available with customization), or 2 (available natively). Multiply each score by the requirement weight and sum for a total vendor score. Shortlist the top three vendors for demo evaluation. The RFP score should be used to narrow the field, not make the final decision — the demo evaluation, reference checks, and total cost comparison should drive the final selection. Integrated platforms with strong scores on integration requirements but weaker scores on OEE or CMMS depth should be evaluated carefully — integration architecture quality matters most when both functions are genuinely capable.