Selecting a manufacturing analytics platform in 2026 is a more consequential decision than it was three years ago. The market now includes purpose-built manufacturing intelligence platforms, general-purpose BI tools configured for factory use, and AI-native platforms that promise predictive capabilities before they have delivered on descriptive ones. Getting the selection wrong means two to three years of a platform that does not connect to your equipment, produces OEE numbers nobody trusts, and generates more work for the IT team than value for the production floor. This vendor selection checklist gives manufacturing operations, IT, and procurement teams a structured 30-point evaluation framework covering the six dimensions that determine whether a manufacturing analytics platform delivers ROI: connectivity, core analytics, AI capabilities, deployment and support, pricing and contract terms, and vendor qualification.
iFactory Passes Every Criterion on This Checklist — See It Live on Your Use Cases
Before completing this vendor selection checklist against any platform, see iFactory demonstrated on your specific use cases — OEE on your machine types, downtime Pareto with your reason code structure, and quality analytics linked to your inspection data. We welcome evaluation against this checklist.
Connectivity — The Criterion That Determines Everything Else
The most important question in any manufacturing analytics platform evaluation is not "how good are the dashboards?" — it is "how does your data get in?" A platform with beautiful OEE dashboards that cannot connect to your Siemens PLCs, your SAP production orders, or your QMS inspection results is a display of fictional data. Connectivity failures are cited in over 60% of manufacturing analytics disappointments post-purchase — and they are almost always visible during the evaluation if the buyer tests connectivity on their specific systems rather than accepting a demo on vendor-managed data.
Demand Live Connector Demos
Do not accept a demo on vendor-managed sample data for connectivity evaluation. Bring your actual data source list — ERP version, PLC types, MES platform name — and ask the vendor to demonstrate data flowing from your system type into their platform during the evaluation.
Native vs. Middleware
A native connector built and maintained by the analytics vendor is materially different from a connector that relies on a third-party middleware layer. Native connectors have faster data throughput, fewer failure points, and vendor accountability when they break. Middleware-dependent connectors introduce a second vendor into every support escalation.
Connector Maintenance SLA
When your ERP vendor releases a new API version, or when your PLC firmware updates, will your analytics connector break? Ask every vendor: how are connectors maintained when source systems update? What is the SLA for restoring a broken connector? Who is responsible?
Legacy Equipment Strategy
A meaningful proportion of production equipment in most manufacturing plants does not have PLC connectivity. Ask each vendor how their platform handles legacy equipment: edge device options, manual operator entry with data quality controls, or hybrid capture. Vendors who say "we only connect to modern PLCs" cannot serve a real factory floor.
Integration Complexity and Timeline
Ask each vendor for the implementation timeline for your specific integration list — not a generic estimate. A vendor who says "two weeks" for any integration without reviewing your systems is not giving you a real answer. Get a written scope and timeline before contract.
Connector Documentation
Request the technical integration documentation for your top three connectors before signing. A vendor who cannot provide integration documentation pre-sale does not have mature connectors — they have demos.
Core Analytics — OEE, Downtime, Quality, and Maintenance
The core analytics capability of a manufacturing platform is its ability to calculate OEE correctly, capture and categorise downtime, track quality metrics including first-pass yield and defect Pareto, and surface maintenance KPIs including MTBF, MTTR, and PM compliance. These four use cases cover 80% of the ROI available from manufacturing analytics in most plants. Evaluate them in depth before spending evaluation time on AI features that require 12 months of data to deliver any value.
Every plant defines planned production time, ideal cycle time, and good count slightly differently. A platform with a hardcoded OEE formula will produce OEE numbers that do not match your operational definitions — and your team will reject the data. During evaluation, configure the OEE calculation with your specific definitions and verify the output against a manually calculated shift.
Platforms that provide a fixed reason code list you cannot modify are not suitable for production use. Your downtime reason codes must reflect your actual equipment failure modes, your terminology, and your maintenance team's language. Evaluate whether the reason code hierarchy is fully configurable and whether it can be maintained by operations staff without vendor involvement.
Basic quality dashboards show defect count and yield. Mature quality analytics show SPC charts with control limits, defect Pareto by cause with trend, First-Pass Yield at the operation level, and the ability to correlate quality trends with process parameters and downtime events. Evaluate the analytics depth, not the visual polish of the dashboard.
Multi-plant OEE benchmarking is only meaningful if every plant is using the same definition of planned production time, ideal cycle time, and good count. Ask each vendor how they enforce definition consistency across sites. A platform that allows each site to configure independently will produce incomparable OEE scores — which is worse than no benchmarking at all.
AI and Advanced Analytics — What to Evaluate in 2026
AI capabilities in manufacturing analytics platforms range from genuinely value-creating (anomaly detection that identifies process deviations before they cause defects, predictive maintenance models that produce equipment-specific failure predictions with measurable lead times) to marketing-grade (a chatbot interface over standard dashboards, a "smart alert" that fires on the same threshold-crossing logic any rule engine has done for 20 years). The evaluation framework for AI features must focus on demonstrated outcomes, not feature descriptions.
Evaluate on Your Data, Not Demo Data
Ask every vendor to run their anomaly detection on a sample of your historical production data during the evaluation. A genuine AI capability will surface anomalies in your data. A demo-only AI will only work on the carefully prepared dataset the vendor controls.
Predictive Maintenance Specificity
A predictive maintenance model that says "this machine may fail soon" is not predictive maintenance — it is a conditional alert. A genuine predictive model specifies the failure mode, the expected time to failure with a confidence interval, and the recommended action. Evaluate the specificity of the prediction, not the existence of the feature.
Training Data Requirements
Most AI models require 6–18 months of labelled historical data to produce reliable predictions. Ask every vendor: how much history is needed, who labels the data (your team or theirs), how frequently is the model retrained, and what happens to model accuracy when the process changes. Vendors who cannot answer these questions do not have production-grade AI.
False Positive Rate Disclosure
An anomaly detection system that fires 40 alerts per shift produces alert fatigue that is more damaging than no alerts. Ask every vendor for the measured false positive rate for anomaly detection in a production environment. Require a reference customer who can confirm the alert quality in practice — not a vendor-stated specification.
AI Roadmap in Writing
AI feature roadmaps change frequently. If a vendor's AI capabilities are a significant factor in your selection decision, require a written roadmap with delivery dates for Phase 2 features — not a verbal commitment from the sales team. Include roadmap milestones as a performance clause in the contract.
Phase Your AI Investment
Do not select a platform primarily on AI features that you will not use for 12–18 months. Select on the quality of core analytics (OEE, downtime, quality) and the AI capability available today. Platforms that deliver excellent descriptive and diagnostic analytics are the ones that will have the production data quality needed to make AI features valuable when you are ready for them.
Deployment — From Contract to Production Value
The deployment experience is where the gap between vendor sales claims and operational reality becomes visible. A platform that takes eight months to deploy when the vendor promised eight weeks has not delivered value; it has consumed eight months of internal implementation resource and delayed the operational improvement that justified the investment. The deployment criteria in this checklist focus on the contractual commitments, the implementation methodology, and the support structure that determine whether go-live happens on schedule.
The go-live timeline must be in the contract — not in the SOW as a "target." A vendor who will not contractually commit to a go-live date for the pilot line within a defined period does not believe the estimate they gave you in sales.
The implementation manager assigned to your project must be named before contract signing. The quality of the implementation manager is more important than the quality of the platform for a successful go-live. Ask to speak with the assigned implementation manager before you sign.
The pilot line implementation — data connections, dashboard configuration, user training — must be in scope in the base contract, not an additional professional services charge. Vendors who quote professional services separately for a standard pilot implementation are pricing the implementation cost out of the headline licence fee.
The support SLA during implementation is different from the support SLA in production. Confirm the SLA that applies after go-live: response time for P1 (production down) issues, escalation path, and named support contact versus generic ticket queue.
The implementation plan must include a parallel running period — two to four weeks where the analytics platform runs alongside the existing reporting method before the old method is decommissioned. A vendor who does not include parallel running in the implementation plan has not delivered enough production go-lives to know why it matters.
Pricing, Contract Terms, and Exit Rights
Manufacturing analytics platform contracts have become significantly more complex in 2026, with pricing models that combine per-site licences, per-connector fees, professional services charges, AI feature tiers, and annual escalation clauses that are not visible in the headline price. The pricing evaluation criteria below focus on total cost of ownership over three years — the relevant horizon for any platform investment — and the contract terms that protect your organisation when the relationship does not perform as expected.
All-In Pricing Request
Request a three-year total cost of ownership model from every vendor: year 1 (platform + implementation + training), year 2 (platform + support + any connector fees), year 3 (platform + support + estimated new connector or feature fees). Compare TCO, not headline annual licence.
Connector Fees
Some platforms include connectors in the platform licence. Others charge per connector, per connection, or per data volume. A platform with a low headline price and per-connector fees can cost significantly more at full deployment than a higher-priced platform with connectors included. Model your full connector list before comparing prices.
Scaling Economics
Model the cost of adding a second and third plant after the pilot. Some platforms price by site (flat fee per plant), others by user count, others by data volume. The pricing model that is competitive for a single plant may be prohibitive for a five-plant rollout. Evaluate scaling economics before signing.
Data Portability Rights
Your operational data — production records, downtime events, OEE history — must be exportable in a standard format on exit. If a vendor's contract does not explicitly grant data portability rights, the data is effectively hostage to the platform. This is a must-have contract term.
Exit Clause
A contract without an exit clause for non-performance is a five-year commitment regardless of whether the platform delivers value. Require a performance-based exit clause: if defined KPIs (uptime, go-live milestones, support response SLAs) are not met, you have the right to exit without penalty.
Price Escalation Cap
Annual renewal price escalation at vendor discretion is standard in many SaaS contracts and is a significant long-term cost risk. Require a cap — CPI plus a defined maximum percentage — written into the contract. Vendors who refuse a price cap on a multi-year deal should be scored accordingly.
See iFactory Scored Against Every Criterion on This Checklist
iFactory is built for manufacturing operations teams who need analytics running in production — not proof-of-concept dashboards. We provide written RFP responses, live connector demonstrations on your equipment types, reference customers in your industry, and contractual go-live commitments.
Manufacturing Analytics Vendor Selection Checklist — 30 Items
Use this checklist to score each vendor in your evaluation. The Demo column indicates criteria that should be verified in a live vendor demonstration. The Must-Have column marks criteria where a "no" answer is a disqualifying finding.
| # | Evaluation Criterion | Type | Priority | Demo | Required | Must-Have |
|---|---|---|---|---|---|---|
| 1 | Native connectors to your ERP (SAP, Oracle, Dynamics) demonstrated live — not via middleware only | Verify Live | High | ✓ | ✓ | ✓ |
| 2 | PLC/SCADA connectivity shown for your machine types (Siemens, Fanuc, Mitsubishi, Allen-Bradley) | Verify Live | High | ✓ | ✓ | ✓ |
| 3 | MES integration path documented — direct API or certified connector, not custom script | Evaluate | High | ✓ | ✓ | ✓ |
| 4 | Connector library breadth confirmed — number of certified connectors, update cadence, support SLA per connector | Evaluate | High | ✓ | ✓ | — |
| 5 | Legacy equipment without PLC connectivity handled — manual entry fallback or edge device option | Evaluate | Med | ✓ | ✓ | — |
| # | Evaluation Criterion | Type | Priority | Demo | Required | Must-Have |
|---|---|---|---|---|---|---|
| 6 | OEE calculation shown live on demo environment — Availability, Performance, Quality, Six Big Losses ranked | Verify Live | High | ✓ | ✓ | ✓ |
| 7 | Downtime Pareto with reason codes demonstrated — drill-down from plant to line to event | Verify Live | High | ✓ | ✓ | ✓ |
| 8 | Quality analytics covers first-pass yield, defect Pareto, and SPC charts — not dashboard only | Verify Live | High | ✓ | ✓ | ✓ |
| 9 | Maintenance analytics: MTBF, MTTR, PM compliance, and work order tracking in scope | Evaluate | High | ✓ | ✓ | — |
| 10 | Multi-line, multi-shift, multi-plant OEE benchmarking demonstrated | Verify Live | High | ✓ | ✓ | ✓ |
| # | Evaluation Criterion | Type | Priority | Demo | Required | Must-Have |
|---|---|---|---|---|---|---|
| 11 | AI anomaly detection demonstrated on real production data — not only on curated demo dataset | Verify Live | High | ✓ | ✓ | — |
| 12 | Predictive maintenance model shown — specific failure prediction with lead time, not generic alert | Evaluate | High | ✓ | ✓ | — |
| 13 | AI model training data requirements clarified — how much history needed, who trains, how often retrained | Evaluate | High | ✓ | ✓ | — |
| 14 | AI feature roadmap for 2026 provided in writing — not only verbal commitments | Reference | Med | — | ✓ | — |
| 15 | False positive rate for anomaly alerts measured and disclosed — not only stated as "low" | Evaluate | High | ✓ | ✓ | — |
| # | Evaluation Criterion | Type | Priority | Demo | Required | Must-Have |
|---|---|---|---|---|---|---|
| 16 | Go-live timeline contractually committed — not estimated during sales process only | Contractual | High | — | ✓ | ✓ |
| 17 | Implementation methodology documented: phases, milestones, and client responsibilities | Evaluate | High | ✓ | ✓ | ✓ |
| 18 | Named implementation manager assigned — not handed to a generic support queue after contract | Evaluate | High | ✓ | ✓ | ✓ |
| 19 | Pilot line go-live included in scope — not an additional professional services charge | Contractual | High | — | ✓ | ✓ |
| 20 | Training materials and change management support included — operator and supervisor level | Evaluate | Med | ✓ | ✓ | — |
| # | Evaluation Criterion | Type | Priority | Demo | Required | Must-Have |
|---|---|---|---|---|---|---|
| 21 | All-in pricing provided: platform licence, connectors, implementation, training, and support — no hidden line items | Contractual | High | — | ✓ | ✓ |
| 22 | Per-site vs. per-user pricing model clarified — scaling cost modelled for full plant rollout | Contractual | High | — | ✓ | ✓ |
| 23 | Contract term minimum and auto-renewal clauses reviewed — no 5-year lock-in without break clause | Contractual | High | — | ✓ | ✓ |
| 24 | Data export and portability rights in contract — your data is exportable in standard format on exit | Contractual | High | — | ✓ | ✓ |
| 25 | Annual price escalation cap specified in contract — not at vendor discretion on renewal | Contractual | Med | — | ✓ | — |
| # | Evaluation Criterion | Type | Priority | Demo | Required | Must-Have |
|---|---|---|---|---|---|---|
| 26 | Reference customers in your industry and plant size provided — not only enterprise references for an SME buyer | Reference | High | — | ✓ | ✓ |
| 27 | Reference call completed with a customer using the platform for 12+ months in production — not pre-sales reference | Reference | High | — | ✓ | ✓ |
| 28 | Vendor financial stability confirmed — funding status, customer count, and year founded reviewed | Evaluate | High | — | ✓ | — |
| 29 | Security certifications confirmed: SOC 2 Type II, ISO 27001, or equivalent — certificates in date | Evaluate | High | — | ✓ | ✓ |
| 30 | SLA for uptime (minimum 99.5%), support response (P1 < 1 hour), and data breach notification reviewed | Contractual | High | — | ✓ | ✓ |
Vendor Evaluation Scoring — How to Use This Checklist
Score each vendor on a 1–3 scale per criterion (1 = does not meet, 2 = partially meets, 3 = fully meets). Weight Must-Have criteria at 3×. Calculate a weighted total per vendor and compare. Any vendor scoring "1" on a Must-Have criterion should be flagged for clarification before advancing to contract negotiation — a Must-Have gap identified after signing is a deployment risk, not a negotiation point.
| Evaluation Dimension | What to Verify in Demo | Contract Requirement | Disqualifier if Missing |
|---|---|---|---|
| Connectivity | Live connection to your ERP and PLC type during demo — not vendor-managed data | Named connectors and SLAs in scope of work | ✓ |
| OEE Analytics | OEE configured with your definitions — Availability, Performance, Quality, Six Big Losses | OEE methodology documented in contract | ✓ |
| Downtime Tracking | Configurable reason code hierarchy, Pareto, drill-down to event level | Reason code configuration in onboarding scope | ✓ |
| Quality Analytics | FPY, defect Pareto, SPC charts — not just defect count dashboard | Quality analytics scope defined in contract | ~ |
| AI / Predictive | Anomaly detection on your historical data — false positive rate disclosed | AI roadmap milestones as contract clauses if material to selection | ✗ |
| Go-Live Timeline | Implementation plan reviewed with named implementation manager pre-sale | Contractual go-live date for pilot line — not target estimate | ✓ |
| Pricing / TCO | 3-year TCO model including connectors, implementation, and escalation | Price escalation cap, data portability, and exit clause | ✓ |
| Vendor Stability | Reference call with 12-month production customer in your industry | Uptime SLA (99.5%+), support SLA, breach notification in contract | ~ |
Frequently Asked Questions
What are the most important criteria when selecting a manufacturing analytics platform?
The three most important criteria are connectivity, OEE calculation correctness, and deployment track record. Connectivity — the ability to reliably pull data from your specific ERP, PLCs, and MES — determines whether the platform produces real data or demo data. OEE calculation correctness — whether the formula is configurable to your definitions of planned production time, ideal cycle time, and good count — determines whether the OEE number produced is meaningful. Deployment track record — how many plants of your size and type are live in production — determines whether the go-live timeline the vendor promises is achievable. AI features, UI design, and reporting flexibility matter less if these three fundamentals are not met.
What is a manufacturing analytics RFP and what should it include?
A manufacturing analytics RFP (Request for Proposal) is a structured document sent to vendor shortlists that requests written responses to specific evaluation criteria. A manufacturing analytics RFP should include: company and plant overview, current data sources and systems (ERP, MES, PLC types), Phase 1 analytics use cases and KPIs required, integration requirements and data volume estimates, deployment timeline requirements, contract term and commercial constraints, and evaluation scoring methodology. Vendors who cannot provide written RFP responses within two weeks of receipt typically cannot support a structured implementation process either. Book a Demo — iFactory provides written RFP responses on request.
How do you evaluate AI features in a manufacturing analytics platform?
Evaluate AI features in manufacturing analytics on three dimensions: demonstrated outcome on real data (not demo data), specificity of predictions (failure mode and time horizon, not just "anomaly detected"), and false positive rate in production use. Request a reference customer who has been using the AI feature in production for more than six months and ask them: how many alerts fire per shift, what percentage are actionable, and has the AI prediction led to a measurable reduction in unplanned downtime? Vendor marketing for AI features in manufacturing is substantially ahead of the delivered capability in most platforms in 2026. Evaluate outcomes, not feature names.
What contract terms are essential in a manufacturing analytics platform agreement?
The essential contract terms for a manufacturing analytics platform are: contractual go-live date for the pilot line (not a target estimate), data portability rights (your data exportable in standard format on exit), exit clause for non-performance tied to defined SLA metrics, price escalation cap on annual renewal, named connectors and integration scope in the statement of work, support SLA for P1 production issues (response within one hour), and uptime SLA of at least 99.5%. Contracts that do not include these terms shift all performance risk to the buyer.
How is iFactory different from general-purpose BI tools configured for manufacturing?
iFactory is purpose-built for manufacturing operations — not a general-purpose BI tool configured with manufacturing templates. The difference is visible in three areas: connectivity (iFactory has certified connectors for manufacturing-specific systems — PLCs, MES platforms, QMS — that general BI tools handle via generic data connectors or manual export), analytics depth (iFactory's OEE, Six Big Losses, MTBF, and quality analytics are pre-built with manufacturing-specific logic, not recreated from scratch in a BI configuration layer), and deployment speed (iFactory goes live in two weeks because the manufacturing use cases are pre-configured — not two to six months of BI configuration by a systems integrator). Book a Demo to compare directly against any platform you are evaluating.
iFactory Welcomes Structured Evaluation Against Every Criterion
Request a live demo structured around this vendor selection checklist — we demonstrate OEE on your machine types, show live connector documentation for your ERP and PLC, provide written RFP responses, and arrange reference customer calls within five working days.