Nineteen systems: what it takes to answer one question about readiness

Ask a naval aviation program how many aircraft are mission capable this morning and you have asked a question that crosses roughly nineteen systems, depending on how you count. None of them is wrong. Each was built for a real purpose by people solving a real problem.

Maintenance actions live in one place, flight hours in another, supply status in a third, personnel qualification in a fourth. Readiness is a derived figure that depends on all of them, which means it inherits every latency, definition and outage in the chain.

The failure mode is not that the number is unavailable. It is that several numbers are available, all defensible, and the one that reaches a decision maker depends on who assembled the brief. That is a governance gap, not a technology gap.

We map the chain first: which system is authoritative for which field, on what refresh cadence, with what known gaps. It is a document, not a dashboard, and it is usually the single most valuable artifact we produce in the first period of performance.

Only after that does instrumentation make sense. Build the pipeline first and you have automated the disagreement at higher speed and greater confidence, which is worse than the manual process it replaced.