FOR DEFENSE PROGRAM OFFICES + OEMS
A digital twin of every fielded unit: hardware, software, and every replacement.
Fielded configurations drift from as-built the moment a part is swapped or firmware is patched. 'Which fielded units carry X?' is unanswerable from build records alone.
HOW TEAMS USE REARM FOR THIS
01
HBOM + SBOM per unit
Hardware and software bill of materials per unit and per configuration, kept together.
↳ SBOM/xBOM Management02
Per-deployment composition
Each fielded deployment's exact composition tracked via the distribution model.
↳ Distribution03
Replacements tracking
Part and component swaps recorded against the twin. As-maintained, not just as-built.
↳ Distribution04
Fleet-wide exposure queries
By vulnerability or by part number: which fielded units carry X, answered in seconds.
↳ Dependency Search05
Evidence trail for sustainment audits
The same immutable history, extended to every fielded unit's service life.
↳ Audit EvidenceNOTE: copy pending verification against actual distribution page
PLACEHOLDER — SCREENSHOT 9: distribution page, HBOM + replacements
EVIDENCE
HBOM + SBOMReplacements
PER-UNIT CONFIGURATION · DISTRIBUTION MODEL · SUSTAINMENT AUDITS