Statistics
AuraScore 83/100

Fleet Component Time-to-Failure Survival Analysis Report

Produce a parametric survival analysis report evaluating component wear, hazard rates, and replacement schedules across commercial transport fleets.

Use this template when evaluating censored telematics data to model critical vehicle component failure risks and optimize preventative maintenance thresholds. It guides the statistician through Kaplan-Meier estimation, parametric survival fitting, and covariate hazard evaluation.

Template

Role: Principal Reliability Statistician and Fleet Telematics Lead with 15+ years of experience in time-to-event parametric modeling for transport assets.

Context

  • Fleet operator profile: {{fleet_operator}}
  • Telematics telemetry scope: {{telematics_dataset_scope}}
  • Target component failure mode: {{failure_mode_target}}
  • Right-censoring observational window: {{censoring_threshold_days}}
  • Operating condition covariates: {{covariate_list}}
  • Target reliability benchmark: {{target_reliability_sla}}

Task

Generate an advanced parametric survival analysis and reliability engineering report for {{fleet_operator}} that rigorously quantifies the time-to-failure distribution of {{failure_mode_target}} under varied operating covariates, providing mathematically backed maintenance trigger thresholds to satisfy {{target_reliability_sla}}.

Method

  1. Formulate the right-censoring framework for the observational window defined by {{censoring_threshold_days}} across {{telematics_dataset_scope}}, categorizing suspensions versus unassisted mechanical failures.
  2. Construct non-parametric Kaplan-Meier survival curves and calculate Greenwood standard error intervals across baseline operating cohorts.
  3. Fit and compare parametric survival distributions (Weibull, Log-Normal, and Gamma) using log-likelihood, AIC, and BIC criteria to identify best-fit hazard behavior.
  4. Execute a Cox Proportional Hazards regression incorporating {{covariate_list}} to calculate hazard ratios (HR) and assess proportional hazards assumptions via Schoenfeld residuals.
  5. Compute the mean residual life (MRL) and B10/B5 life percentiles under median and stress-case covariate operational profiles.
  6. Formulate precise dynamic inspection and preventative replacement intervals that uphold {{target_reliability_sla}} while minimizing premature component disposal.
  7. Detail sensitivity diagnostics and residual survival probabilities at key odometer and operating-hour milestones.

Constraints

  • MUST evaluate both parametric and semi-parametric model goodness-of-fit metrics side by side.
  • MUST explicitly define right-censoring assumptions and handling of scheduled preventive component removals.
  • MUST NOT treat operating conditions as time-invariant if longitudinal telematics telemetry indicates significant covariate drift.
  • All statistical estimates must include 95% confidence intervals and standard errors.

Output format

Generate a structured statistical report with the following mandatory sections:

  1. Executive Summary & Reliability Scorecard (max 250 words)
  2. Censoring Architecture and Non-Parametric Survival Baseline
  3. Parametric Model Selection & Goodness-of-Fit Comparison Table
  4. Cox Proportional Hazards and Covariate Impact Analysis
  5. Predictive Reliability Milestones (B5, B10, MRL) Table
  6. Operational Maintenance Threshold Recommendations

Self-review

  • Confirm that all variables ({{fleet_operator}}, {{telematics_dataset_scope}}, {{failure_mode_target}}, {{censoring_threshold_days}}, {{covariate_list}}, and {{target_reliability_sla}}) are thoroughly integrated.
  • Verify that goodness-of-fit statistics (AIC/BIC, Log-Likelihood) are explicitly defined for each tested distribution.
  • Ensure calculated hazard ratios and confidence intervals align mathematically with stated maintenance cutoff recommendations.
AuraScore breakdown
83/100Provisional
Instruction clarity15/15 · Strong

Explicit role, a named task, and discrete steps the model can follow.

Context architecture12/12 · Strong

Background, inputs and variables the model needs before it starts.

Constraint engineering12/12 · Strong

Hard boundaries — what the model must and must not do.

Output specification6/14 · Thin

A named, field-level shape for the response.

Reasoning structure10/10 · Strong

Ordered work items that force analysis before an answer.

Model compatibility10/10 · Strong

Length and structure that travel across frontier models.

Token efficiency5/10 · Thin

Signal density — instruction weight without padding.

Reusability7/7 · Strong

Documented variables so the scaffold adapts to new inputs.

Robustness5/5 · Strong

Quality bar, assumptions and behaviour when inputs are thin.

Observed performance1/5 · Thin

How much real usage the template has behind it.

data-analytics
data-statistics
transport-logistics
statistics
survival-analysis
reliability-engineering