Defense Sustainment's Persistent Data Reconciliation Problem

Under 48 CFR § 46.407, contracting officers in federal acquisition should generally reject supplies that do not conform in all respects to contract requirements. In defense sustainment, evaluations of simple substitutes commonly consider form, fit, and function attributes.

That substitution determination depends on reconciling a part's identifier against its specification data, two categories of information that frequently reside in separate systems of record.

A 2025 report from the Defense Business Board, an internal advisory body to the Secretary of Defense, described the shape of the resulting problem in direct terms. Fragmented governance and inconsistent data-sharing policies have created disjointed data environments that limit interoperability and delay actionable insights, according to the Defense Business Board Supply Chain Illumination study.

The study identified integrated bill-of-materials, product lifecycle management, and enterprise resource planning visibility as a private-sector practice the department has not achieved at scale.

The gap is neither new nor recently discovered. The Government Accountability Office has been describing versions of it across multiple administrations. What persists is the reconciliation labor required whenever identifier data and specification data must be brought together to complete a sustainment action.

Identity, Specification, and the Reconciliation Framework

A part in a defense supply chain is typically resolved through an identifier such as a National Stock Number, a manufacturer part number, or a CAGE-code-plus-part-number pairing. That identifier lookup can return metadata about the part's assignment, source, and administrative status.

Dimensional information, performance characteristics, tolerances, and qualification attributes may live in separate systems, often maintained by different organizations on different update cadences.

When a part identifier is retired, superseded, or discontinued by its manufacturer, the sustainment workflow requires an equivalence determination. Form, fit, and function analysis, referred to as FFF or F3, is the standard framework for evaluating a simple substitute. Its criteria are specification-level rather than identifier-level, requiring the person performing the determination to reach across the systems where each attribute is stored.

Form refers to a component's physical geometry, including shape, size, dimensions, and mass. Fit describes the component's ability to interface or connect with adjacent components without modification. Function refers to the component's operational performance in the intended application.

For a simple substitute, all three must be reconciled before acceptance, and the underlying data for each attribute may reside in a system separate from the one holding the original part's identifier.

This pattern is well documented in defense sustainment under the heading of Diminishing Manufacturing Sources and Material Shortages, referred to as DMSMS. The Defense Logistics Agency's Defense Standardization Program Journal describes obsolescence management as a lifecycle-spanning discipline that requires tracking part status against sourcing options and continuously updating a program's authoritative parts list.

The Government-Industry Data Exchange Program, or GIDEP, has served as the Department of Defense's designated centralized database for sharing DMSMS information for decades. Most of its obsolescence data is obtained from manufacturers and their authorized distributors, supplemented by internal data mining and voluntary submissions from participants.

GIDEP addresses the shared notification and information layer of the problem; the specification reconciliation required to evaluate a specific substitute occurs downstream, in the systems where each program manages its own parts and specification data.

A Wider Class of Structurally Fragmented Data

The identity and specification pairing is one instance of a broader class. Configuration data, meaning what a system was designed to be, diverges over the operational life of a platform from as-built maintenance records, meaning what is actually installed on a given aircraft or ship after years of field modifications and repairs.

Certification and qualification data, which typically apply to a part class, must be reconciled against genealogy data to confirm that a specific unit in inventory carries the required certification through its supply chain history.

Technical data packages exist alongside contract metadata governing their use, including data rights, export-control flags under the International Traffic in Arms Regulations, and proprietary markings. Those data types are frequently maintained by different functional organizations, engineering on one side and contracts administration on the other.

Obsolescence status and active sourcing information, tracked through programs such as GIDEP, are often disconnected from the qualification and test history that describes whether a given lot is suitable for the intended application.

Each of these pairings shares a common structural feature. The two data types in each pair are functionally coupled, meaning a downstream sustainment action requires both to be resolved together. They are institutionally decoupled, meaning they are maintained separately by different organizations, systems, or functional lines with no persistent cross-reference layer stitching them together.

Fragmentation in defense supply chain systems is frequently described using the vocabulary of compartmentalization or strategic siloing. Classification boundaries and Controlled Unclassified Information handling constraints are real design choices with defensible rationales, particularly where genuine national security interests are at stake.

A portion of the fragmentation observed in sustainment workflows tracks those boundaries; a portion of it does not.

Where the underlying data is reachable through manual cross-reference by an appropriately credentialed worker, the immediate constraint is organizational rather than classificatory. In those cases, the language of compartmentalization can obscure a more ordinary problem rooted in legacy architecture and organizational structure.

The 2025 Government Accountability Office report on the defense industrial base observed that Department of Defense officials disagreed on whether relevant supplier information is readily available or too costly to obtain. That disagreement suggests that the fragmentation cannot be reduced to classification posture or adversary-facing security considerations alone.

Remediation Layers and Their Persistent Cost

The remediation landscape is neither empty nor recent. Individual services have built layers on top of GIDEP to address reconciliation within their scope. The Navy's Obsolescence Management Information System, developed at Naval Undersea Warfare Center Keyport, pulls DMSMS data from multiple sources and links it to stored part data, with a dedicated research team that contacts manufacturers and suppliers of commercial items not otherwise tracked in the databases.

NAVSEA's shipboard DMSMS tracking programs consolidate information from Fleet reporting, GIDEP, the Defense Logistics Agency, the Naval Supply Systems Command Weapon Systems Support office, and OEM correspondence to produce ship-level obsolescence visibility.

The Air Force Materiel Command has issued its own DMSMS instruction requiring information exchange among Air Force, Department of Defense, other government organizations, and industry, with GIDEP designated as the minimum baseline for information sharing.

At the policy level, Department of Defense Instruction 5000.97 on Digital Engineering directs program managers to implement digital engineering procedures to the maximum extent possible. The instruction requires programs to generate knowledge through digital threads and to develop authoritative data sources that integrate technical data and associated digital artifacts across the system lifecycle.

The gap between mandate and execution is documented across a series of GAO reports going back at least fifteen years. GAO-18-435, issued in 2018, found that the Manufacturing and Industrial Base Policy office's data systems do not fully leverage existing data from program offices on the companies providing parts at the lower tiers of the supply chain, and that such data is not currently collected in a standardized format.

The July 2025 report recommended that the department identify resources, priorities, and time frames to implement efforts to integrate and share supply chain data, a recommendation the department concurred with.

Industry descriptions of sustainment data remediation convey what compliance with such recommendations involves in practice. An illustrative shipbuilding project published by defense-industry consultancy Umbrex described harvesting multi-level bills of materials from product lifecycle management systems and reconciling them against enterprise resource planning item masters and integrated logistics support baselines to establish an authoritative parts list per ship class.

The example also describes cleansing part master records for identifiers, export-control flags, form-fit-function attributes, lifecycle status, and alternate sources, then configuring cross-system integration by defining authoritative field owners, synchronization cadence, and change triggers.

Standards including IEC 62402 for obsolescence management, MIL-STD-3018 for parts management, and EIA-649 for configuration management provide guidance that professionalizes the reconciliation discipline. Those standards describe how organizations should manage the work internally. They do not eliminate the underlying condition of institutionally decoupled data that makes the reconciliation necessary in the first place.

The Department of Defense's own logistics organization is actively working to make supply chain data available across the department through a single platform. The 2025 GAO report noted that the Office of the Deputy Assistant Secretary for Logistics is identifying the various systems and tools that store supply chain data, with a goal of consolidating visibility through the Advana platform.

That effort presupposes the current condition: the data exists, it is distributed across many systems, and consolidating it requires deliberate identification and integration work.

The persistence of manual reconciliation across decades of policy attention, standards development, and platform-specific tooling indicates that the shape of the problem is durable. The reconciliation labor is real, ongoing, and largely invisible in the higher-level abstractions used to describe defense acquisition.

Its fixes are well understood at the level of any given program, and its underlying pattern remains only partially addressed at the level of the acquisition system as a whole.

Sources

• Office of the Federal Register. "48 CFR § 46.407 Nonconforming supplies or services." Electronic Code of Federal Regulations, 2024.
• Under Secretary of Defense for Research and Engineering. "DoD Instruction 5000.97: Digital Engineering." U.S. Department of Defense, 2023.
• Defense Business Board. "Supply Chain Illumination in the Department of Defense." U.S. Department of Defense, 2025.
• U.S. Government Accountability Office. "GAO-25-107283: Defense Industrial Base: Actions Needed to Address Risks Posed by Dependence on Foreign Suppliers." U.S. Government Accountability Office, 2025.
• U.S. Government Accountability Office. "GAO-18-435: Defense Industrial Base: Integrating Existing Supplier Data and Addressing Workforce Challenges Could Improve Risk Analysis." U.S. Government Accountability Office, 2018.
• Defense Logistics Agency. "DMSMS Management: The Key to Higher Availability and Lower Costs." Defense Standardization Program Journal, 2014.
• Air Force Materiel Command. "AFMCI 20-105: Diminishing Manufacturing Sources and Materiel Shortages Program." U.S. Department of the Air Force, 2022.
• Government-Industry Data Exchange Program. "DMSMS Information Resource." GIDEP, 2024.
• Umbrex. "Shipbuilding and Marine Systems: Obsolescence and DMSMS Program Management." Umbrex, 2025.