OEE Software RFP Template: 47 Requirements and a Weighted Scoring Matrix

OEE software RFPs fail when they copy generic software procurement templates rather than specifying manufacturing requirements. A checklist asking whether the vendor has mobile access and reporting will return five vendors that all check every box, and give you no basis for differentiation.

See the OEE calculation this RFP is built around.

The RFP That Actually Works

Effective OEE RFPs ask how features work, not if they exist:

• Not "does the mobile app work offline?" but "show us data capture behavior during a 30-minute WiFi outage"
• Not "does it integrate with SAP?" but "show us a SAP PM work order created from an OEE downtime event in a live demo"
• Not "does it support multi-site?" but "show us the cross-site OEE comparison view for 6 sites simultaneously"

RFP development should start with your top 5 pain points in the current maintenance and production operation, weight requirements to your actual priorities to surface the right vendors.

Structure your OEE RFP across five requirement categories:

Machine Connectivity (10 requirements)

• Native PLC connectivity for your specific brands (Siemens, Allen-Bradley, Fanuc, Mitsubishi, etc.)
• Offline edge capability with local data buffering and auto-sync
• Retrofit sensor support for legacy machines without digital outputs
• OPC-UA and Modbus TCP support
• Connectivity to historian systems (OSIsoft PI, AVEVA PI)

OEE Analytics (12 requirements)

• Real-time OEE display with <60 second refresh latency
• Automatic downtime detection without operator input
• Operator downtime reason coding interface
• Six Big Losses categorization
• MTBF and MTTR tracking per asset
• Shift, crew, and line-level OEE comparison

CMMS Integration (10 requirements)

• Automatic work order creation from OEE downtime events
• Shared asset data model between OEE and CMMS
• PM compliance tracking connected to OEE performance trends

Reporting and Access (8 requirements)

• Custom dashboard builder without coding
• Scheduled report delivery via email
• API access for BI integration
• Role-based access control

Security and Compliance (7 requirements)

• SOC 2 Type II certification
• GDPR/data residency compliance for EU operations
• SSO support
• Data portability guarantee in contract

Weight RFP requirements in three tiers based on your operational priorities:

• Must-have (pass/fail): Offline capability, your specific PLC connectivity, PM compliance tracking, data export, any vendor that cannot meet these is eliminated regardless of price
• High-priority (weighted 3x): The specific capabilities addressing your top operational pain points, weight these triple if they're critical differentiators for your environment
• Standard (weighted 1x): All other features that add value but are not differentiating

After Scoring

Calculate total weighted scores and build a shortlist of three vendors for demo evaluation. The RFP score should inform but not determine final selection, implementation quality, vendor responsiveness, and product roadmap alignment often matter more than feature score differences at the margin.

Always include total first-year cost (licensing + implementation) as a separately scored dimension alongside functional requirements.