Diagnostic stream
Paste CSV or a JSON array. Required columns: vehicle_id, timestamp (ISO 8601), dtc. Optional: status (pending | confirmed | permanent), odometer_km, battery_v, coolant_c, oil_pressure_kpa, def_level_pct. One row per code occurrence.
How the risk score is built
Rules (v0.1, deterministic, no trained model)
| Signal | Points | Basis |
|---|
- Each DTC occurrence is mapped to a component group. Points from all signals for a component are summed and capped at 100. The highest-scoring component per vehicle is reported as the predicted failure.
- The 48-hour horizon is the scoring window design target. It has not been validated against failure outcomes. Treat the score as a prioritization heuristic, not a probability.
- Code definitions, affected components and common causes come from the OBDex open database (CC0), fetched at runtime. Codes absent from that database fall back to SAE J2012 range-based classification only.
- Cost and labor fields shown are OBDex estimates in EUR as published there; they are not quotes.