SHEET 05OPERATIONS · UN R155 POST-PRODUCTION

Two rooms.
One incident.

The OEM's Incident Command sees the fleet. Each affected project runs its own Incident Management. Both work the same trace on the same graph — nothing lost in handover, and the R155 report is written by what actually happened.

See incident response live Fleet Map · security events · R155 authority reporting
Incident Command — live● CRITICAL
INC-2031 telematics exploitation attempts
scope  : 1,204 vehicles · 2 programs · 3 projects
status : containment · opened 06:41 UTC
R155   : pre-notification drafted
STATION 1 · DETECT

Fleet events,
clustered and typed.

Vehicle SOC events land on the fleet map with geography and pattern clustering. A CVE match from Sheet 03 can raise the same alarm — one detection surface, two inputs.

INPUT ← vehicle SOC events
INPUT ← CVE watch · sheet 03
EMITS → anomaly clusters
scope: programs · projects · suppliers ← ONE ACTION
command timeline · decisions ← RECORDED
supplier evidence pulled in ← SHARES
STATION 2 · COMMAND

The program room.
Fleet-wide picture.

Promote a cluster to an incident and scope it across programs, projects and suppliers in one action. Every decision lands on the command timeline.

INCIDENT COMMAND → PROJECT INCIDENT MANAGEMENT · INC-2031 ONE INCIDENT · 3 PROJECTS
PROGRAM · INCIDENT COMMAND
CRITICAL INC-2031 · Telematics exploitation attempts
1,204 VEHICLES · EV GEN-4 + CITY VAN · OPENED 06:41 UTC
Scope: 2 programs · 3 projects · 1 supplier Status: Containment
Fleet anomaly cluster promoted to incident — 17 vehicles, UDS probe pattern 06:41 · FLEET MAP
Impact trace: TCU Connectivity Stack v3.2 across 3 projects 06:52 · KNOWLEDGE GRAPH
Work delegated to owning projects; supplier share requested from Tier-1 A 07:10 · INCIDENT COMMAND
Authority pre-notification drafted from incident record (R155) 08:30 · COMPLIANCE
DELEGATED · PROJECT INCIDENT MANAGEMENT
IM-114 · TCU IN PROGRESS
Patch wpa_supplicant, re-run claim CLM-07 verification
IM-115 · Central Gateway ANALYSIS
Confirm SecOC filtering blocks lateral movement
IM-116 · IVI NOT AFFECTED
VEX statement issued — component not present in image
RESULTS ROLL UP TO INC-2031 — CLAIMS, PATCHES, VEX ATTACHED.
STATION 3 · DELEGATE

The engineering room.
Project-level fix.

Each affected project works its slice: incidents attach to model nodes, impact analysis reuses the TARA, treatment tracks to verification. Findings convert to risks or vulnerabilities without duplication.

ATTACHES → component · interface · unit
RE-OPENS → TARA scenarios · risks
ROLLS UP → to INC-2031 automatically
R155 sections from the record ← GENERATED
threat scenarios updated ← LEARNED
feasibility re-rated on paths ← CLOSED LOOP
STATION 4 · REPORT & LEARN

The report writes itself.
The TARA gets smarter.

Authority reporting is generated from the incident record, not reconstructed. Closed incidents feed back: affected threat scenarios and feasibility ratings update on the paths that were actually attacked.

TITLEOPERATIONS — INCIDENT COMMAND & MANAGEMENT
STANDARDUN R155 · GB 44495-2024†
SURFACEFLEET MAP · SOC
DEPLOYON-PREM · AIR-GAP