The engineers and mission management disagree
Debris assessment engineersEngineer entry
0.82
Anomaly score on the foam strike. Logged on day 2 at 10:00, before management review.
Mission managementManager entry
0.69
Classified in family on day 3 at 14:00. Imagery request not pursued. Simulated override.
The red tick marks the 0.7 threshold. The agency model independently scores the strike at 0.82.
Chosen:
Added to the audit log as entry #6, along with which evidence panels were open. The escalation status and divergence flag stay as logged.
Options are illustrative and need checking against the CAIB record before use.
Supporting evidence
Everything behind the decision is one click away. The log records which panels were open when a choice is made.
Debris assessment engineersEngineer entry
0.82
Day 2, 10:00. Before management review.
Mission managementManager entry
0.69
Day 3, 14:00. Classified in family.
Agency telemetryRisk Monitor Agent
0.82
Day 2, 10:02. Telemanom score, computed independently.
- Engineer signal above thresholdYes
- Management classification at or below thresholdYes
In this case the filtering ran from the agency toward the engineers. The same test catches it: when both are true, escalation is triggered regardless of what management decided.
Trend detection
Looks for a rising signal across flight history, including strikes that stayed below threshold.
Slope [x], p [x], last [N] flights
Resolution audit
Foam loss occurred on more than 80% of the 79 missions with imagery, and those strikes were treated as in family (CAIB, 2003).
Proceed [n] of [N], binomial p [x]
Bracketed values are placeholders for flight-history results.