Rules enforced at decision points inside this engine. Run logs, memos, and review rationales cite these IDs.
Autonomy
- Fleet surveillance
R-FL01A unit flags only when residuals exceed its digital-twin tolerance with a matched failure signature; everything else stays in continuous surveillance.
M. Okada, Fleet Reliability Lead, RMC Lake Mary · 24-month replay
- Intervention simulation
R-FL04Intervention is proposed only where planned expected value beats run-to-failure; otherwise the unit is monitored with stepped alarms.
M. Okada, Fleet Reliability Lead, RMC Lake Mary · simulation policy
Routing
- Flag triage
R-FL03Every flag maps to its LTSA obligations, parts position, and crew requirement before any simulation is shown.
M. Okada, Fleet Reliability Lead, RMC Lake Mary · triage standard
Guardrail
- Fleet surveillance
R-FL02Instrument-fault candidates route to I&C work orders and are never counted as reliability flags or as saves.
S. Whitfield, I&C Lead · replay discipline
- Crew assignment
R-FL06Crew assignments require certifications current through the full outage window; an expiry inside the window blocks the assignment.
T. Yamazaki, Outage Director · policy standard
Escalation
- Outage bundling
R-FL05A P90 failure window inside 30 days forces the earliest safe outage window and overrides bundling latitude.
M. Okada, Fleet Reliability Lead, RMC Lake Mary · escalation standard
Governance
- Action-pack review
R-FL07Customer-facing scheduling releases only on dual approval: the responsible service manager and the account director.
M. Okada, Fleet Reliability Lead, RMC Lake Mary · review standard
- Action-pack review
R-FL08A sample of swept-clear units enters each action-pack review as an audit item.
M. Okada, Fleet Reliability Lead, RMC Lake Mary · added this cycle