NADIR field guide

MTTFF-RE: The One Metric for ADAS Post-Repair Pilots

Mean time to first flag on repair events (MTTFF-RE) is the single KPI NADIR proves in 4-week shadow pilots. Definition, target, and sample readout.

01 / INTERACTIVE DIAGRAM

Post-repair detection path

Repair import → ingest → score → queue → evidence — illustrative seed data.

NADIR VISUAL · SEED DATAILLUSTRATIVE · NOT FIELD PERFORMANCE
Nominal Caution Critical

Article companion visual · not field performance.

02 / DETAILS

Read this article two ways

Plain language for fleet and investor conversations. Technical detail for engineering diligence.

Plain-language takeaway

This guide supports NADIR's detection-first motion: find likely post-repair miscalibration using telematics you already export.

Shadow mode means tiers and signed evidence — not automatic vehicle changes or ECU writes.

  • Pair reading with a 4-week $750 shadow proof if you're evaluating vendors.
  • Close pilots on MTTFF-RE — median flag within seven days on ≥70% of repair events.
03 / DETAILS

Article FAQ

Quick answers for fleet and engineering readers.

Article FAQ

Quick answers for fleet and engineering readers.

Fleet pilots drown in dashboards. NADIR shadow pilots commit to one measurable outcome: MTTFF-RE — mean time to first flag on repair events. If you cannot detect elevated residuals within seven days of glass or body work on at least seventy percent of eligible ROs, the pilot failed — regardless of how polished the UI looked in week one.

Definition

For each repair event with a known RO close timestamp and sufficient telematics coverage, MTTFF-RE is the elapsed time until the first CRITICAL (or agreed CAUTION+) tier transition attributable to post-repair scoring. Events with no flag within the observation window count against the SLA. Events without telemetry coverage are excluded explicitly in the readout appendix — not silently dropped.

Why fleets care

Maintenance leaders do not need another health score. They need to know which vehicles returned from shop with latent miscalibration before those vehicles accumulate miles, near-misses, or insurer questions. MTTFF-RE ties detection latency directly to repair-network accountability and internal QA — in days, not quarters.

Risk and legal teams get a single Exhibit A chart for pilot closeout instead of a binder of anecdotal screenshots.

Target for a 4-week shadow pilot

  • Population: 50–150 ADAS-equipped VINs with mixed repair types (glass, front-end, mirror)
  • Mode: Shadow only — queue and evidence exports, no ECU writes
  • SLA: MTTFF-RE ≤ 7 days on ≥ 70% of covered repair events
  • Deliverable: Signed evidence samples + weekly digest + week-4 MTTFF-RE chart

How it appears in Console

Operators see CRITICAL rows keyed to VIN and repair context. Executives see cohort curves: time-from-RO to first flag, stratified by shop and procedure type. Developers pull the same cohort via API for internal QA systems. The product walkthrough episode on analytics shows the fixture data end-to-end.

What MTTFF-RE is not

It is not a replacement for OEM calibration procedures, ASIL validation, or physical bay work. It is not a correction guarantee. NADIR advisory analytics surface candidates for human review; they do not command brakes, steering, or ECU parameter writes.

Next steps

Read the full KPI page at /pilots/kpi, review pilot pricing, and email founders from Start a shadow pilot with your RO feed format and telematics export sample.

Close the loop with MTTFF-RE.

Run a 4-week shadow pilot on 50–150 ADAS vehicles and export signed evidence.