# Pilot Structure and KPIs The pilot is engineered to de-risk the buyer and prove value fast on a narrow footprint. ## Shape - **1–3 critical assets**, **90–120 day** duration. - **Read-only** integration, **On-Prem / VPC** deployment. - **Weekly technical reviews** with the operator's team. ## Success criteria - **<30-day** integration with **zero operational disruption**. - **>80%** operations-team validation of alerts. - **<1 non-actionable alert / asset / month** (signal, not noise). - **>30 days** lead-time improvement on detected failures. - **>85%** detection rate. ## Why these KPIs They map one-to-one to the buyer's fears: *Will it break my plant?* (zero disruption), *Will it drown my team?* (<1 false alert), *Will it actually warn me in time?* (>30 days lead time, >85% detection). Hitting them is what converts a paid pilot into expansion. See [[Renacore/Business Model and Go-To-Market]] and [[Deployment Velocity]]. ## Status The pilot KPIs are the *target* spec — **no pilot has yet been executed**. See [[Renacore/Traction and Pipeline]]. ## Related - [[Renacore MOC]] - [[Renacore/Architecture and Infrastructure]] - [[Renacore/Traction and Pipeline]] - [[Predictive Maintenance in O&G]]