Predictive Maintenance Pilot — Success Criteria & Acceptance (Interactive Template)
An interactive, fillable template that helps teams define measurable pilot goals, data quality rules, timelines, operational acceptance thresholds, governance, rollback rules, and a scale-decision checklist for sensor-driven predictive maintenance pilots.
{
"Title": "Predictive Maintenance Pilot — Success Criteria & Acceptance",
"IntroductionHtml": "
Use this template to define clear, measurable success criteria, data requirements, timelines, governance, and scale decision rules for a sensor-driven predictive maintenance pilot. Fill required fields and use the scale decision checklist to make a fair, evidence-based scale-up decision.
", "SubmitLabel": "Save Pilot Criteria", "SuccessMessage": "Pilot criteria saved. You can update these fields and later submit pilot results against the acceptance criteria.", "DataType": "predictive_maintenance_pilot_criteria", "SchemaVersion": "1.0", "Fields": [ { "Key": "problem_statement", "Label": "Problem statement (concise)", "FieldType": "textarea", "Required": true, "HelpText": "Describe the reliability problem you want to solve and who is impacted (customers, line, shift, cost centers)." }, { "Key": "target_metric_description", "Label": "Target metric (description)", "FieldType": "text", "Required": true, "HelpText": "E.g., percent equipment downtime, mean time between failures (MTBF), number of unplanned stops per week." }, { "Key": "target_metric_value", "Label": "Target metric value (numeric)", "FieldType": "number", "Required": true, "HelpText": "Numeric target to judge success (for example: reduce downtime by 15)." }, { "Key": "target_metric_unit", "Label": "Target metric unit", "FieldType": "text", "Required": true, "HelpText": "Units (%, hours, stops per week)." }, { "Key": "baseline_value", "Label": "Baseline value (numeric)", "FieldType": "number", "Required": true, "HelpText": "Current measured value for the metric using the baseline period/method below." }, { "Key": "baseline_period", "Label": "Baseline measurement period", "FieldType": "text", "Required": true, "HelpText": "Date range and sampling frequency used to compute baseline (e.g., last 6 months, hourly readings)." }, { "Key": "baseline_method", "Label": "Baseline measurement method", "FieldType": "textarea", "HelpText": "How the baseline was measured, filters/exclusions, and responsible owner for baseline data." }, { "Key": "min_data_quality_sample_rate", "Label": "Minimum acceptable sample rate (Hz)", "FieldType": "number", "HelpText": "Minimum sensor sampling frequency required for reliable detection (enter N/A if not applicable)." }, { "Key": "min_data_quality_missing_pct", "Label": "Maximum acceptable missing data (%)", "FieldType": "number", "HelpText": "Percent of expected samples that may be missing before the data is considered unusable." }, { "Key": "min_data_quality_snr", "Label": "Minimum acceptable signal-to-noise ratio", "FieldType": "number", "HelpText": "If applicable, specify minimum SNR; otherwise enter N/A." }, { "Key": "pilot_start_date", "Label": "Pilot start date", "FieldType": "text", "HelpText": "Planned start date (YYYY-MM-DD)." }, { "Key": "pilot_duration_days", "Label": "Pilot duration (days)", "FieldType": "number", "Required": true, "HelpText": "Total timebox for the pilot to collect sufficient examples and evaluate outcomes." }, { "Key": "sample_size_required", "Label": "Required sample size (events / hours / units)", "FieldType": "number", "HelpText": "Minimum number of failure and non-failure examples or operational hours needed for validation." }, { "Key": "operational_false_positive_pct", "Label": "Maximum acceptable false positive rate (%)", "FieldType": "number", "HelpText": "Threshold beyond which alerts would create unacceptable reactive work or distraction." }, { "Key": "operational_false_negative_pct", "Label": "Maximum acceptable false negative rate (%)", "FieldType": "number", "HelpText": "Tolerance for missed failures; specify if detection must be near-perfect for safety-critical assets." }, { "Key": "actionable_lead_time_hours", "Label": "Minimum actionable lead time (hours)", "FieldType": "number", "HelpText": "Minimum advance notice required for maintenance to plan and act (e.g., 24 hours)." }, { "Key": "governance_owner_name", "Label": "Pilot owner (name)", "FieldType": "text", "Required": true }, { "Key": "governance_owner_role", "Label": "Pilot owner (role)", "FieldType": "text", "Required": true }, { "Key": "escalation_contact", "Label": "Escalation contact and path", "FieldType": "textarea", "HelpText": "Who to contact and the escalation path for operational or safety issues during the pilot." }, { "Key": "rollback_conditions", "Label": "Rollback conditions (clear triggers)", "FieldType": "textarea", "HelpText": "Define clear, measurable triggers that require pausing or rolling back the pilot (e.g., sustained false positive rate > X%, data loss > Y%)." }, { "Key": "scale_decision_checks", "Label": "Scale decision checklist", "FieldType": "checkbox", "Options": [ { "Value": "signal_validated", "Label": "Signal validated against known failures" }, { "Value": "model_performance", "Label": "Model meets performance thresholds" }, { "Value": "ops_integration", "Label": "Maintenance workflows integrated and actionable" }, { "Value": "safety_compliance", "Label": "Safety/regulatory review complete" }, { "Value": "cost_benefit_positive", "Label": "Preliminary cost/benefit positive or acceptable" }, { "Value": "training_complete", "Label": "Operators and maintainers trained" }, { "Value": "data_pipeline_ready", "Label": "Data ingestion/storage automated and reliable" }, { "Value": "support_commitment", "Label": "Support and budget committed for scale-up" } ], "HelpText": "Select all checks that must be true to move from pilot to scale. Consider weighting or mandatory checks in governance." }, { "Key": "evaluation_method", "Label": "Evaluation method", "FieldType": "select", "Options": [ { "Value": "before_after", "Label": "Before / After comparison" }, { "Value": "controlled_rollout", "Label": "Controlled rollout / A/B" }, { "Value": "statistical_test", "Label": "Statistical hypothesis test" }, { "Value": "other", "Label": "Other" } ], "HelpText": "How outcomes will be evaluated and which statistical or operational checks will be used." }, { "Key": "success_metrics", "Label": "Success metrics and how they'll be measured", "FieldType": "textarea", "HelpText": "List the metrics, calculation methods, measurement frequency, reporting cadence, and responsible owners." }, { "Key": "data_storage_retention", "Label": "Data storage and retention requirements", "FieldType": "textarea", "HelpText": "Where sensor and model data will be stored, retention period, backup and access controls." }, { "Key": "training_and_change_management", "Label": "Training and change management plan", "FieldType": "textarea", "HelpText": "How operators, maintenance technicians, and supervisors will be trained and how changes will be communicated across shifts." }, { "Key": "estimated_pilot_costs", "Label": "Estimated pilot costs (USD)", "FieldType": "number", "HelpText": "Include sensors, connectivity, storage, engineering hours, and maintenance labor estimates." }, { "Key": "notes_and_risks", "Label": "Key risks, mitigations, and open questions", "FieldType": "textarea", "HelpText": "Document primary risks (safety, data, operational) and proposed mitigations or outstanding questions to resolve." } ] }Discussion
Comments and conversation will live here.