Government furnished equipment management in defense contracts

When a defense contractor receives government property — test equipment, specialized tooling, raw material, or a vehicle fleet — it enters a legal accountability relationship that persists until the property is returned, transferred, or disposed of through authorized channels. That accountability is not informal. It is governed by FAR Part 45 and DFARS Part 245, enforced through DCMA property control system reviews, and backed by financial liability provisions that can make individual items the source of significant contract disputes. Getting government furnished equipment management right is not a back-office administrative concern; it is a contractual obligation with direct operational and financial consequences.

For defense contractors managing dozens or hundreds of contracts simultaneously, the administrative burden of GFE compliance compounds quickly. Each contract may furnish different categories of property under different CLINs. Equipment moves between locations. Subcontractors take possession of items that never leave the prime contractor's accountability books. Condition codes change. Items go missing. Without a purpose-built GFE management system, these obligations are managed through spreadsheets that cannot be audited on demand, produce no automatic alerts when condition changes occur, and provide no audit trail for DCMA surveyors who arrive unannounced for property control system reviews.

This article covers the complete technical and procedural landscape of GFE management: the regulatory framework, database architecture, condition tracking, CAO surveillance requirements, UID marking compliance, disposition workflows, and ERP integration patterns.

What GFE is and why it matters in defense contracts

Government furnished equipment is a subset of the broader category of government-furnished property (GFP) defined under FAR Part 45. The regulation distinguishes four main categories of government-furnished property, each with distinct accountability requirements.

Equipment refers to capital assets — machinery, vehicles, test sets, sensors, computing systems — that retain their identity throughout contract performance and must be returned at contract completion. Equipment items typically have a unit acquisition cost above the contractor's capitalization threshold and are tracked individually by serial number.

Material covers raw stock, components, assemblies, and consumable items furnished for incorporation into deliverable end items. Unlike equipment, material is consumed during performance and relief from accountability is documented through incorporation into deliverables rather than physical return.

Special tooling encompasses jigs, dies, fixtures, molds, patterns, and other items designed and built specifically for production of a particular end item. Special tooling is often co-located at contractor facilities for extended periods and presents the highest risk of co-mingling with contractor-owned tooling.

Government-furnished information (GFI) includes technical data packages, specifications, drawings, and software delivered to the contractor for performance reference. GFI accountability is handled separately from physical property — it flows through controlled document management systems and export control frameworks rather than physical inventory procedures.

The regulatory backbone for GFE management is FAR 52.245-1 (the standard clause incorporated into most contracts that include GFP) and DFARS 252.245-7003, which establishes the 11 property system criteria against which DCMA measures contractor property control systems. A contractor whose property control system is found inadequate under DFARS 252.245-7003 faces enhanced surveillance, potential withholding of contract payments, and in cases of systemic failure, disallowance of property-related costs.

For contractors navigating the broader competitive landscape, understanding GFE obligations is part of a larger set of contractual requirements covered in our complete guide to defense procurement.

GFE accountability database architecture

A GFE management system's data model must support four distinct record types that together constitute the complete accountability picture: the property master record, the possession record, the location record, and the transaction log. These are not independent tables — they form a linked structure where every transaction updates multiple records atomically.

Property master record

The property master record is the authoritative identity document for each GFE item. It must capture:

• National Stock Number (NSN) — the 13-digit NATO stock number identifying the item class
• Part number — manufacturer's part identifier
• Serial number — item-level identifier assigned by the manufacturer or government
• Unique Item Identifier (UII) — the globally unique IUID-system identifier
• Item description — plain-language and technical nomenclature
• Unit acquisition cost — the government's recorded cost for financial reporting
• Acquisition date — date the government acquired the item (not the date furnished to the contractor)
• Furnishing contract and CLIN — the authority under which the item is in contractor possession

The property master record also maintains a status field — active possession, returned, transferred, disposed, or pending disposition — that drives workflow routing and reporting.

Possession and location records

The possession record captures the contractual custody chain: when the contractor received the item, from whom (government shipping depot, predecessor contractor, or issuing activity), under which contract modification, and who at the contractor's organization accepted accountability. The location record captures the physical location at any point in time — down to building, room, and storage position for high-density environments.

-- Core GFE schema (simplified)
CREATE TABLE gfe_items (
    item_id         UUID PRIMARY KEY,
    nsn             CHAR(13),
    part_number     VARCHAR(50),
    serial_number   VARCHAR(100),
    uii             VARCHAR(50) UNIQUE,
    description     TEXT,
    unit_cost_usd   NUMERIC(12,2),
    acq_date        DATE,
    status          VARCHAR(30),  -- ACTIVE | RETURNED | TRANSFERRED | DISPOSED
    contract_id     UUID REFERENCES contracts(contract_id),
    clin            VARCHAR(20)
);

CREATE TABLE gfe_location (
    location_id     UUID PRIMARY KEY,
    item_id         UUID REFERENCES gfe_items(item_id),
    location_code   VARCHAR(50),
    custodian       VARCHAR(100),
    effective_from  TIMESTAMPTZ,
    effective_to    TIMESTAMPTZ
);

CREATE TABLE gfe_transactions (
    txn_id          UUID PRIMARY KEY,
    item_id         UUID REFERENCES gfe_items(item_id),
    txn_type        VARCHAR(30),  -- RECEIPT | MOVE | CONDITION_CHANGE | TRANSFER | RETURN
    txn_date        TIMESTAMPTZ,
    from_location   VARCHAR(50),
    to_location     VARCHAR(50),
    performed_by    VARCHAR(100),
    notes           TEXT,
    document_ref    VARCHAR(50)   -- DD Form number or system document ID
);

This schema supports on-demand audit queries: given an item's serial number or UII, the system can reconstruct the complete possession, location, and condition history from receipt through disposition — exactly what DCMA auditors require during a property control system review.

Condition code tracking and reporting

The DoD condition code system assigns a standardized serviceability rating to each item of government property. Condition codes are recorded at receipt, updated whenever a physical inspection or maintenance event changes the item's serviceability, and reported to the government through the annual physical inventory and through specific event-triggered reports.

The condition code scale

The standard DoD condition codes applicable to GFE are:

• Code A — Serviceable (Issuable without qualification): New or like-new; fully operational with all components and documentation.
• Code B — Serviceable (Issuable with qualification): Functional but with cosmetic damage, missing non-critical accessories, or minor wear that does not affect operational performance.
• Code C — Serviceable (Priority repair): Currently capable of limited use but requires repair; may be issued for immediate operational need.
• Code D — Unserviceable (Repairable): Requires repair before use; the cost of repair is economically justified relative to replacement value.
• Code E — Unserviceable (Incomplete): Missing assemblies or components to an extent that renders the item non-functional; requires additional parts before repair can begin.
• Code F — Unserviceable (Scrap): Beyond economical repair; suitable only for parts recovery or disposal as scrap.

Receiving inspection workflow

The receiving inspection is the critical first condition assignment event. When GFE arrives at the contractor's facility, the receiving inspector must: verify the quantity against the shipping document (DD Form 1149 or equivalent); check for physical damage, corrosion, missing accessories, or signs of improper storage; scan or manually record the IUID mark; and assign the appropriate condition code based on the inspection findings.

The receiving inspection record must be created before the item enters storage. A common failure in property control system audits is the discovery of items that have been in use for months with no receiving inspection record — the item simply moved from the dock to the shop floor without entering the property system. This constitutes a receipt procedure inadequacy under DCMA's PCSR criteria.

Condition change reporting

When a GFE item's condition changes — whether through use, maintenance, damage, or discovery during inventory — the contractor must update the condition record in the property system and report significant condition changes to the Contracting Officer. Items that degrade from code A to code D or below typically require written notification. Items that degrade to code F (scrap) trigger the loss-damage-destroyed reporting obligation under FAR 52.245-1(f)(1)(vii) if the degradation resulted from anything other than normal contract performance.

CAO surveillance and property control system audits

The Contract Administration Office (CAO) — typically DCMA for major defense contractors — is responsible for surveillance of the contractor's property control system (PCS). Surveillance is conducted through property control system reviews (PCSRs), which can be announced or unannounced. The frequency and depth of review is risk-based: contractors with large GFP portfolios, prior audit findings, or complex subcontractor arrangements receive more frequent surveillance.

The 11 PCSR criteria

DFARS 252.245-7003 defines 11 system adequacy criteria against which the DCMA auditor evaluates the contractor's property control system:

1. Acquisition — the system accurately records how each item was acquired and from what source.
2. Receiving — all property is processed through a formal receiving inspection before entering storage or use.
3. Records — property records are accurate, complete, and current for all GFP in contractor possession.
4. Physical inventory — annual physical inventory is conducted and reconciled to book records.
5. Subcontractor control — GFP flowed to subcontractors is tracked, and subcontractor property systems are assessed.
6. Reports — required reports (annual inventory, LDD notifications, excess property reports) are submitted timely and accurately.
7. Relief from responsibility — the contractor has a documented process for seeking relief from financial liability for lost or damaged GFP.
8. Utilization — GFP is being used for authorized contract purposes and is not idle or mis-applied.
9. Maintenance — required maintenance of GFP is performed and documented.
10. Property disposal — GFP disposition follows authorized channels and is properly documented.
11. Contract closeout — all GFP is accounted for and disposition completed before contract closes.

Corrective action tracking

When an audit finding identifies an inadequacy in one or more PCSR criteria, the CAO issues a Corrective Action Request (CAR). The contractor must respond within the timeframe specified in the CAR — typically 30 days for the initial corrective action plan, with implementation milestones for complex system changes. The GFE management system should include a CAR tracking module that records the finding, the root cause analysis, the corrective action plan, implementation milestones, and closure evidence. This module supports both internal management of audit responses and the evidence package required by DCMA when the CAR is formally closed.

Understanding CAO surveillance is part of the broader defense software maintenance contract compliance picture — property management systems are themselves subject to software maintenance obligations that must be negotiated at contract award.

IUID/UID marking requirements

Item Unique Identification (IUID) is DoD's property serialization and tracking system. Every covered item of government property must carry a UID mark — a 2D Data Matrix barcode — that encodes a globally unique identifier enabling the item to be tracked across its full lifecycle: production, government receipt, issue to a contractor, return, transfer, and final disposition.

MIL-STD-130N compliance

MIL-STD-130N is the marking specification that defines the physical requirements for UID marks on government property. The standard specifies mark size, data matrix symbol quality grades (minimum ISO/IEC 15415 grade 1.5), substrate and etch method requirements for different material types, and placement rules. For embedded marks (direct part marking on metal or composite surfaces), the acceptable methods include laser engraving, electro-chemical etching, and dot peening — each with specific depth and contrast requirements. For applied marks (labels and nameplates), the standard specifies label material grades, adhesive requirements, and durability requirements for the operating environment.

The UII structure

The Unique Item Identifier (UII) encoded in the Data Matrix has two acceptable constructs under MIL-STD-130N:

• Construct 1 (Manufacturer-assigned): Enterprise Identifier (CAGE code) + Original Part Number + Serial Number. Used when the manufacturer assigns the UID at production.
• Construct 2 (Government-assigned): Enterprise Identifier (CAGE code) + Enterprise-Assigned Sequential Number. Used when the government assigns the UID, typically for items that were not marked at production.

-- Example UII parse from 2D Data Matrix scan
-- Raw scan output (GS1 Application Identifiers):
-- (17D)5J0001234A(1P)12-34567-1(S)ABC123456

-- Parsed fields:
enterprise_id  = "5J"          -- CAGE code
part_number    = "12-34567-1"  -- Original Part Number (AI 1P)
serial_number  = "ABC123456"   -- Serial Number (AI S)

-- Constructed UII:
uii = "5J" || "12-34567-1" || "ABC123456"
    = "5J12-34567-1ABC123456"

-- Registered in IUIDR as:
{
  "uii": "5J12-34567-1ABC123456",
  "enterpriseId": "5J",
  "partNumber": "12-34567-1",
  "serialNumber": "ABC123456",
  "registrationDate": "2026-06-25",
  "contractNumber": "W52H09-26-C-0041",
  "clin": "0001"
}

Software integration for UID data capture

GFE management software must integrate with barcode scanning hardware to capture UII data at every transaction point: receiving, inventory, condition change, location move, and disposition. The scan input must be parsed to extract all encoded data elements — enterprise identifier, part number, serial number, and any supplemental data elements present — and validated against the property master record. A mismatch between the scanned UII and the recorded UII for the item triggers an exception workflow that holds the transaction and notifies a supervisor. Items with unreadable or damaged marks require a mark assessment: if the underlying data elements can still be retrieved from the property record, replacement marking may be required before further transactions.

GFE return, transfer, and disposition workflows

Every GFE item must reach an authorized end-state before the contract can close. The four authorized end-states — return to government, transfer to another contractor, excess/scrap disposition through DRMO, and relief from responsibility for LDD items — each require distinct documentation workflows and generate specific transaction records in the property system.

Return to government

Return is the most common end-state for equipment-category GFE at contract completion. The contractor initiates return by generating a property list identifying all items to be returned, with current condition codes, quantities, and the CLIN under which each item was furnished. The Contracting Officer must approve the return before physical shipment begins. Shipping is arranged through the Defense Transportation System (DTS) using the appropriate Transportation Control Number (TCN). At the receiving depot, government personnel conduct a receipt inspection and compare the accepted condition against the contractor's reported condition. Any condition downgrade discovered at government receipt creates a potential financial liability determination — the contractor may be charged for the difference in value between the reported condition and the accepted condition.

Contractor-to-contractor transfer

When GFE must move from one contractor to another — during a recompete transition, when a follow-on contract awards to a different contractor, or when a subcontractor's scope moves to a different subcontractor — the transfer requires a Contracting Officer authorization. The transferring contractor prepares a DD Form 1149 (Requisition and Invoice/Shipping Document) listing each item with its UII, condition code, and contract CLIN. The receiving contractor performs a receiving inspection on transfer, assigns new possession and location records, and reports any discrepancy from the transferred condition. The property master record transfers from the outgoing contractor's system to the incoming contractor's system; the transactional history must follow the item.

Excess and scrap disposition through DRMO

GFE that is no longer needed for contract performance before contract completion must be reported as excess to the Contracting Officer promptly. The Contracting Officer determines whether to redirect the excess to another contract, return it to a government depot, or authorize its turn-in to the Defense Reutilization and Marketing Organization (DRMO). Items in code F (scrap) condition that resulted from authorized use may be turned in to DRMO for parts recovery or metals recycling. The DRMO turn-in requires a DD Form 1348-1A (Issue Release/Receipt Document) and generates a demilitarization code review for items with controlled technology content.

Relief from responsibility

When GFE is lost, damaged, or destroyed during contract performance, the contractor's financial liability depends on whether the loss resulted from negligence, willful misconduct, or authorized use under contract. The contractor must investigate and submit a relief-from-responsibility report documenting the circumstances, estimated replacement or repair cost, and the contractor's position on liability. Items consumed during authorized contract performance (material incorporated into deliverables, for example) are relieved through a simpler process tied to delivery documentation.

Integration with contract management and ERP

GFE management does not operate in isolation. Property records must connect to contract records to support closeout, to financial systems to support government property reporting, and to maintenance management systems to track repair actions on GFE items. The integration architecture directly affects audit compliance: disconnected systems produce the reconciliation gaps that generate PCSR findings.

Linking GFE records to contract CLINs

Every GFE item must be linked to the CLIN under which it was furnished. This linkage enables contract closeout reconciliation — the process of confirming that all items on a CLIN have been returned, transferred, or properly disposed of before the CLIN is administratively closed. If the property system does not maintain CLIN-level linkage, closeout requires manual reconciliation between the property system and the contract, which is error-prone and slow. The CLIN link also drives the government property financial reporting — DD Form 1662 (DoD Property in the Custody of Contractors) is reported at the CLIN level.

Government-furnished data (GFD) handling

Government-furnished information presents a different integration challenge. GFD — technical data packages, specifications, drawings, classified material — flows through document management systems rather than property management systems, but it is still government property subject to accountability. The property system should maintain a GFD register that tracks controlled documents received, their security classification, the individuals who have accessed them, and their disposition at contract completion. For classified GFD, destruction certificates are required in lieu of physical return.

System interface design patterns

The recommended integration architecture uses an event-driven pattern: the GFE management system publishes property events (receipt, condition change, disposition) to a message queue, and downstream systems (contract management, ERP, financial reporting) subscribe to the events relevant to them. This decoupling prevents the tight coupling failures that occur when a single-point interface between the property system and ERP breaks and both systems fall out of sync.

-- GFE event schema (message queue payload)
{
  "event_type": "CONDITION_CHANGE",
  "event_id": "evt_9f2a1c3b",
  "timestamp": "2026-06-25T09:14:33Z",
  "item": {
    "uii": "5J12-34567-1ABC123456",
    "nsn": "5820-01-603-5291",
    "contract_id": "W52H09-26-C-0041",
    "clin": "0001"
  },
  "change": {
    "previous_condition": "A",
    "new_condition": "D",
    "reason": "Impact damage discovered during cycle count",
    "inspector": "J. Martinez",
    "inspection_date": "2026-06-25"
  },
  "requires_co_notification": true,
  "notification_deadline": "2026-06-26T09:14:33Z"
}

Subscribing systems consume this event and take appropriate action: the contract management system logs the condition change against the CLIN; the financial reporting system updates the book value of the item; the maintenance system creates a work order if the item is repairable; and the notifications module triggers a Contracting Officer notification if the event requires one.

ERP integration for government property accounting

Contractors subject to Cost Accounting Standards (CAS) must account for government property separately from contractor-owned assets on their financial statements. The ERP integration must maintain government property at its recorded government cost (not depreciated, unlike contractor-owned assets) and report it on the appropriate balance sheet line. When GFE is returned or transferred out, the ERP record must be updated simultaneously with the property system record to prevent reporting discrepancies. The integration should be validated through periodic reconciliation — the total government property balance in the ERP should match the total in the property management system to the cent. Discrepancies require investigation and resolution before the annual DD Form 1662 submission.

For context on how GFE obligations fit within the broader financial management of defense programs, our analysis of total cost of ownership defense software covers the full lifecycle cost picture, including property accountability system costs.