After glass or body work, vehicles can leave the shop with a green ADAS dashboard and still be misaligned. NADIR closes the gap with shadow detection — telematics you already export, no ECU writes.
Hours from RO close to first flag — illustrative cohort.
Illustrative seed-data visualization. Validate on your representative fleet sample before operational decisions.
Plain language for fleet and investor conversations. Technical detail for engineering diligence.
NADIR helps fleets detect likely ADAS miscalibration after repair using data you already export.
Shadow mode means advisory tiers and signed records — not automatic vehicle changes.
Batch ingest with schema validation, Pulse residual scoring, repair-event join, EVB export.
All outputs are versioned: model_id, policy_id, confidence, reason_codes.
The most common post-repair ADAS gap in commercial fleets.
Windshield replacement disturbs forward camera bracket alignment more often than operators expect.
Static OEM scans at the shop may pass while dynamic lane keeping drift appears days later on highway routes.
NADIR watches dynamic residuals after RO close — not the scan receipt alone.
Lane offset estimates, steering corrections at highway speed, radar lead consistency.
Sparse camera features still useful when radar and yaw disagree persistently.
Pull forward camera calibration verification before next long haul assignment.
Attach NADIR EVB to internal QA ticket — advisory, not automatic vendor blame.
Prefer earliest accurate RO close from shop that performed glass work.
Document whether OEM static calibration was billed vs dynamic drive calibration.
EVB shows tier timeline relative to RO — pairs with shop invoice and scan report.
Every public NADIR deployment starts advisory. These boundaries protect fleet legal teams and set honest expectations for insurers.
Shadow mode means NADIR scores telematics, assigns NOMINAL / CAUTION / CRITICAL tiers, and exports signed evidence — without writing calibration parameters to the vehicle.
Your maintenance team decides whether to pull a unit, schedule a bay recalibration, or return it to route. NADIR does not override OEM safety controllers.
This is intentional: post-repair detection pilots should prove alert quality before anyone discusses automation or correction paths.
NADIR is not ASIL-certified software and does not replace OEM calibration procedures or static target rigs.
A valid evidence bundle signature proves integrity of the JSON record — not that the windshield camera is physically aligned.
Controlled benchmark figures on this site illustrate detector behavior on seed data; field accuracy requires your own MTTFF-RE readout.
If a vendor implies OEM sign-off from a dashboard alone, ask for the underlying evidence schema and pilot KPI.
After MTTFF-RE meets your SOW threshold, fleets may renew Shadow Ops ($750/mo) or open a regional evaluation ($15k+).
Correction, HORIZON forecasting, and tier upgrades remain internal or design-partner only until three paid shadow pilots complete.
Each expansion adds explicit contract language for data retention, rate limits, and excluded actuation paths.
NADIR provides advisory analytics on exported telematics correlated to repair order close timestamps.
Outputs include tier assignments, reason codes, and optional signed JSON evidence bundles.
Customer retains operational authority over vehicle dispatch and calibration vendor selection.
# SOW boundary snippet (illustrative)
scope:
mode: shadow_advisory
ecu_writes: false
kpi: MTTFF-RE
actuation: none
deliverables:
- weekly_digest_csv
- console_critical_queue
- sample_evidence_bundles
- week_4_exhibit_a_chartThe commercial motion is a bounded $750 proof on 50–150 VINs with one KPI — easy for fleet CFOs to approve.
Shadow detection de-risks integration: no ECU access, no bay hardware, no ASIL claims.
Expansion revenue attaches to proven alert quality, not tier shopping in week one.
Mean Time To First Flag after Repair Event. One number for pass, fail, or stop.
When a vehicle leaves a glass or body shop, start a clock at repair order close.
MTTFF-RE measures hours until NADIR assigns CAUTION or CRITICAL in the post-repair observation window.
If most events flag within seven days, your maintenance team gets actionable lead time before silent misalignment becomes a safety conversation.
Join repair_events.ro_closed_at to health_transitions where tier ∈ {CAUTION, CRITICAL}.
Delta = first_flag_at − ro_closed_at in UTC hours.
Appendix lists excluded VINs with reason: no_telemetry, invalid_vin, pre_existing_critical.
SELECT
re.vin,
re.ro_closed_at,
MIN(ht.scored_at) AS first_flag_at,
EXTRACT(EPOCH FROM (MIN(ht.scored_at) - re.ro_closed_at))/3600 AS mttff_hours
FROM repair_events re
JOIN health_transitions ht ON ht.vin = re.vin
AND ht.scored_at >= re.ro_closed_at
AND ht.tier IN ('CAUTION','CRITICAL')
GROUP BY 1,2Each dot or bar is one repair event in the pilot cohort.
Color encodes pass (≤168h) vs fail. Gray marks excluded rows.
Median line is the primary SLA statistic; mean is shown but not contractual.
Cherry-picked VINs with perfect telematics while hard cases were dropped from cohort.
RO timestamps backfilled days after close — inflates MTTFF-RE artificially.
Treating missing data as NOMINAL instead of excluded.
NADIR readouts include an exclusion appendix specifically to prevent silent passes.
Define cohort size, date range, procedure types (glass, front-end, mirror), and telemetry coverage minimum.
State median and pass-rate thresholds explicitly. Define stop conditions if CAUTION noise exceeds agreed bounds.
Clarify that shadow mode continues regardless of pass — expansion is a commercial decision, not automatic actuation.
How Pulse turns telematics into tiers after repair.
A green ADAS dashboard means self-check passed — not that alignment matches factory spec.
When camera lane proxy and radar range-rate disagree for days after glass work, that pattern elevates tier.
Single spikes from weather or harsh braking decay; persistence drives CAUTION and CRITICAL.
Pulse compares observed trajectories to a baseline envelope tuned for post-repair windows.
Outputs: tier, confidence, reason_codes[], model_id, policy_id.
Policies version independently from models — replay uses both IDs.
Sample CAUTION events with maintenance leads — label true vs nuisance.
Adjust observation window or procedure filters before week four readout.
Goal is actionable CRITICAL rate, not zero CAUTION.
Scoring window opens at RO close — pre-repair baseline excluded from post-RO residual.
Changepoint detectors flag abrupt shifts; sustained elevation drives tier transitions.
Cannot distinguish all root causes (wrong part vs skipped scan vs partial cal).
CRITICAL means inspect — not auto-assign blame to shop or OEM.
How to consume Console queue and weekly digest without alert fatigue.
Prioritize CRITICAL VINs with recent glass or ADAS module R&R.
Acknowledge rows in Console when bay inspection scheduled — feeds evidence workflow metadata.
Digest summarizes rising residuals without waking on-call at night.
Use digest in Monday maintenance standups alongside DVIR outcomes.
Verify camera bracket torque, windshield spec, radar bracket after bumper work.
Re-run OEM calibration if physical misalignment confirmed — NADIR does not replace bay tools.
Label sampled CAUTION events with maint team — tune policy filters if agreed.
Export MTTFF-RE trend + sample EVBs — shows detection program maturity.
How to interpret NADIR outputs without over-weighting signatures.
Signed JSON shows model version, tier transition, and repair join integrity.
Does not replace OEM scan, static target result, or expert witness on alignment.
Treat as supplemental telematics analytics alongside dashcam and shop docs.
Customer retains dispatch authority; NADIR provides tiers and optional signed records.
Pilot tier retention documented in SOW — bulk export via API for e-discovery.
NADIR does not certify AEB performance or replace OEM safety homologation.
Dense field reference for engineering diligence on this topic.
| Category | Field / control | Value | Notes |
|---|---|---|---|
| Pilot | mode | shadow_advisory | No ECU writes |
| Pilot | kpi | MTTFF-RE | Median ≤168h target |
| Pilot | cohort | 50–150 VINs | Shadow Proof SKU |
| Ingest | telemetry | POST /v1/telemetry/batch | CSV/JSONL |
| Ingest | repair | POST /v1/repair-events | RO anchor |
| Score | tier | NOMINAL|CAUTION|CRITICAL | Policy-bound |
| Score | model | pulse_residual_* | Versioned |
| Product | queue | Console CRITICAL rows | Operator-facing |
| Product | digest | Weekly CSV/email | CAUTION summary |
| Evidence | signature | HMAC-SHA256 | Integrity only |
| Evidence | verify | POST /v1/evidence/verify | Recompute digest |
| Security | transit | TLS 1.2+ | API only |
| Security | auth | Bearer + API key | Tenant scoped |
| Boundary | asil | Not claimed | Advisory analytics |
| Boundary | actuation | None | Shadow default |
| Commercial | proof | $750 flat | 4 weeks |
| Commercial | ops | $750/mo | After pass |
| Commercial | regional | $15k+ | 150–500 VINs |
Straight answers for buyers and reviewers.
Straight answers for buyers and reviewers.
Regional fleets and repair networks proving post-repair ADAS detection first.
VIN, timestamps, telematics signals, and repair close times.
No. Shadow advisory only — detection, queue, and evidence export.
No. NADIR is advisory analytics, not safety-certified software.
Static scans and dashboard greens do not prove dynamic alignment on route.
Detection-first — not correction sales in week one.
Anchor post-repair observation window
Cross-modal residuals → tier
Maintenance inspects before heavy routes
One KPI in week four readout
4-week paid shadow pilot on 50–150 ADAS vehicles.