Predictive maintenance pilot checklist & success criteria

{"Title":"Predictive maintenance pilot checklist & success criteria","IntroductionHtml":"

This interactive checklist helps teams scope a focused, low-risk predictive maintenance (PdM) pilot that proves value. Fill the fields with cross-functional input from reliability, maintenance, controls/automation, IT, and safety before buying sensors or building models. Save the form to record commitments, owners, and acceptance criteria that will determine whether you scale the pilot.

","SubmitLabel":"Save pilot details","SuccessMessage":"Pilot checklist saved.","DataType":"PredictiveMaintenancePilotChecklist","SchemaVersion":"1.0","Fields":[{"Key":"business_goal","Type":"textarea","Label":"Business goal (what outcome will this pilot prove?)","HelpText":"Describe the measurable business outcome this pilot must demonstrate (for example: reduce unplanned downtime for Asset X by N hours per month, or reduce emergency repairs by Y%). Link to cost, safety, quality, or throughput impact.","Required":true},{"Key":"baseline_period_days","Type":"number","Label":"Baseline measurement period (days)","HelpText":"Number of days of historical data used to calculate baseline metrics.","Required":true},{"Key":"baseline_unplanned_downtime_hours","Type":"number","Label":"Baseline unplanned downtime (hours) for target assets","HelpText":"Total unplanned downtime for the baseline period for the selected assets.","Required":true},{"Key":"baseline_mttr_hours","Type":"number","Label":"Baseline MTTR (hours)","HelpText":"Mean time to repair for the target asset(s) during the baseline period.","Required":false},{"Key":"baseline_mtbf_hours","Type":"number","Label":"Baseline MTBF (hours)","HelpText":"Mean time between failures for the target assets during the baseline period.","Required":false},{"Key":"candidate_assets","Type":"textarea","Label":"Candidate assets and brief failure modes","HelpText":"List assets included in the pilot and the top failure modes you expect to detect (e.g., Motor A — bearing wear; Pump 3 — seal leak). Separate items with semicolons.","Required":true},{"Key":"asset_criticality","Type":"select","Label":"Why these assets? (select primary reason)","Options":[{"Value":"high_downtime_cost","Label":"High downtime cost"},{"Value":"frequent_failures","Label":"Frequent failures"},{"Value":"safety_impact","Label":"Safety or compliance risk"},{"Value":"repair_lead_time","Label":"Long repair lead time or spare constraints"},{"Value":"other","Label":"Other"}],"Required":true},{"Key":"sensors_required","Type":"textarea","Label":"Required sensors, placements, and sample rates","HelpText":"Specify sensor types (vibration, temperature, current, pressure, acoustic, etc.), approximate placement, and target sample rates (e.g., 5 kHz for vibration envelope). Note any constraints (explosive atmosphere, mounting access).","Required":true},{"Key":"data_collection_owner","Type":"text","Label":"Data collection & storage owner (team/person)","HelpText":"Who will be responsible for collecting, storing, and granting access to raw signals during the pilot? Include system (e.g., historian, cloud bucket) and retention policy.","Required":true},{"Key":"data_quality_checks","Type":"textarea","Label":"Data quality checks & acceptance criteria","HelpText":"Define the minimum data quality checks (signal continuity, missing samples, timestamp alignment, SNR thresholds) and who will own verification.","Required":true},{"Key":"controls_and_it_involved","Type":"yesno","Label":"Controls/IT involvement confirmed?","HelpText":"Has controls/automation and IT signed off on connectivity, network security, and data pathways?","Required":true},{"Key":"pilot_duration_weeks","Type":"number","Label":"Planned pilot duration (weeks)","HelpText":"How many weeks will you run the pilot to collect required signal diversity and failure events (or to validate predictions)?","Required":true},{"Key":"minimum_failure_events_expected","Type":"number","Label":"Minimum number of failure events expected during pilot","HelpText":"Estimate how many true failure or degraded events you need to validate models. If none expected, state how you will simulate or use historical replay.","Required":false},{"Key":"acceptance_reduction_unplanned_downtime_pct","Type":"number","Label":"Acceptance: target reduction in unplanned downtime (%)","HelpText":"The percent reduction in unplanned downtime you must achieve to consider the pilot successful.","Required":true},{"Key":"acceptance_false_positive_rate_pct","Type":"number","Label":"Acceptance: maximum acceptable false-positive rate (%)","HelpText":"Maximum acceptable percent of alerts that are false positives, or operationally tolerable alarm load.","Required":true},{"Key":"acceptance_precision_pct","Type":"number","Label":"Optional: target precision (%)","HelpText":"If you use precision/recall metrics, specify target precision to ensure alerts are actionable.","Required":false},{"Key":"acceptance_recall_pct","Type":"number","Label":"Optional: target recall (%)","HelpText":"If capturing most failures is important, specify a minimum recall target.","Required":false},{"Key":"safety_and_governance_signoff","Type":"checkbox","Label":"Safety & governance sign-offs obtained","Options":[{"Value":"safety","Label":"Safety officer"},{"Value":"environmental","Label":"Environmental/compliance"},{"Value":"security","Label":"Cybersecurity/IT"},{"Value":"operations_manager","Label":"Operations/plant manager"}],"HelpText":"Select the groups that have provided sign-off for the pilot.","Required":true},{"Key":"operator_training_plan","Type":"textarea","Label":"Operator/maintenance training & change management","HelpText":"Describe how operators and maintenance will receive alerts, what actions they will take, and any training or documentation needed.","Required":true},{"Key":"integration_with_work_orders","Type":"yesno","Label":"Will alerts integrate with CMMS/work order system?","HelpText":"If yes, specify CMMS and how alerts map to work order priorities.","Required":true},{"Key":"metrics_and_reporting","Type":"textarea","Label":"Weekly metrics & dashboard items to track","HelpText":"List the specific metrics to report during pilot (e.g., alerts per week, true positives, false positives, downtime hours avoided, MTTR change, cost avoided).","Required":true},{"Key":"rollout_plan_if_success","Type":"textarea","Label":"Rollout plan if pilot succeeds","HelpText":"High-level steps, estimated timeline, required budgets, and responsibilities to scale from pilot to production.","Required":true},{"Key":"pilot_risks_and_mitigation","Type":"textarea","Label":"Known risks and mitigation actions","HelpText":"Call out risks such as sensor failure, data leakage, regulatory constraints, or operator overload and how you will mitigate them.","Required":true},{"Key":"final_decision_owner","Type":"text","Label":"Who will sign the final go/no-go decision?","HelpText":"Name and role of the person or governance body that will approve scaling.","Required":true},{"Key":"notes_and_actions","Type":"textarea","Label":"Immediate next actions (assign owners & due dates)","HelpText":"List the next practical steps (e.g., purchase sensor X by date, configure historian ingestion, run signal validation script) and owner names.","Required":false}]}