Supply-chain visibility is usually strongest where it matters least. A prime contractor knows its first-tier suppliers well, knows many second-tier suppliers reasonably well, and beyond that relies on declarations, certifications and assumptions. The dependencies that cause the worst surprises — a single refinery, a single casting house, a single port — tend to sit in the tiers where records are thinnest.
Conventional monitoring is designed to react to what appears in the data: a late shipment, a price spike, a sanctions hit. It is not designed to notice what should appear and doesn't. That is the problem negative-space analysis addresses.
Start with what must be true
Every assembly implies an upstream structure. A part that contains a rare-earth permanent magnet implies a magnet maker, an alloy producer, a separation facility and, ultimately, a mineral source. A machined titanium fitting implies a forging or bar-stock supplier and a sponge producer. These implications come from the bill of materials, the material content and ordinary manufacturing knowledge — not from supplier reporting.
Writing those implications down creates a baseline: an explicit statement of the relationships that must exist for the system to have been built. The baseline is a model, and it can be wrong, which is exactly why it has to be explicit. An unstated assumption cannot be tested.
Compare the baseline with the evidence
The evidence side is whatever is actually available: supplier declarations, certificates of conformance, procurement records, trade and shipping data. Comparing the two produces several distinct kinds of gap.
- Missing tiers — a relationship the baseline requires but no record declares, such as a component with no recorded material source.
- Concentration — many independent-looking paths that converge on one upstream node.
- Inconsistency — a declared origin that is incompatible with the part's material, process or the supplier's known capacity.
- Staleness — declarations that predate a design revision, substitution or change of supplier.
Rank by consequence and confidence
A large program will produce many gaps, and most will be benign. Ranking matters more than detection. Two questions do most of the work: how consequential would this gap be if it reflected a real dependency — considering the part's criticality and how hard it is to substitute — and how confident are we that the gap is real rather than an artifact of missing records?
What a first evaluation needs
- A bounded scope — one system, subsystem or assembly family.
- Indentured bill-of-materials data and whatever supplier declarations exist for it.
- Dependencies or issues the sponsor has already identified, so results can be scored retrospectively.
- An agreement covering data handling, access and success criteria before any analysis begins.
Scored against known answers, a retrospective evaluation shows two things that matter to a program office: how many real issues the method would have surfaced earlier, and how many false leads it produced along the way. Both numbers should decide what happens next.
Federal policy is moving in the same direction. Recent executive action directs development of guidance for mapping critical defense supply chains from raw materials to end products; the FAIR DEFENSE page summarizes that context and links to the official text.