Tech Data

Tech Data

The CAPE & Service Cost Agencies have developed a standardized data template format that specifies the universe of technical parameters that can be collected for each weapon system commodity type (e.g., aircraft, ships, missiles) and defines each parameter consistent with systems engineering practices, MIL-STDs, and Industry guidelines. This revolutionary improvement to the DoD data repository lays the foundation for system architecture trades, affordability analysis, root cause analyses, and life cycle cost estimating activities. The resulting data templates serve as the basis of a new report titled the Technical Data Report (TDR), or 1921-T, that will be a key component of CSDR on future contracts. The Technical Data Working Group includes representatives from the Offices of the Deputy Assistant Secretary of Defense for Systems Engineering (DASD(SE)) and Assistant Secretary of Defense for Logistics and Materiel Readiness (ASD(L&MR)). This cooperation ensures that the parameters, units, and collection methodologies proposed are consistent with DoD data taxonomy and Industry processes.

DRAFT Technical Data DID – June 2017

Draft Technical Data Reporting Presentation.pptx (9/3/2016) - July Release

DRAFT FlexFile CSDR/EVM Co-Plan – June 2017 Release

Draft Technical Data Commodity Specific Standard Plans Tables.zip


Plan Standards By Commodity


Quantity Data Report

Format 1, DD Form 1921-Q, “Quantity Data Report,” is used by contractors to submit: (1) units completed to date, and (2) units delivered at completion, by variant and subsystem, if applicable.

DRAFT Quantity (-Q) Data Item Description - June 2017 Release

DRAFT Quantity Data DID – April 2017 Release

DRAFT Quantity (-Q) Data Exchange Item - July 2017 Release

DRAFT Quantity (-Q) File Format Specification – July 2017 Release

Maintenance and Repair Data

The Maintenance and Repair part DID and form is used by contractors to submit: (1) maintenance event data related to each maintenance event such as the specific system being repaired, location where the repair activity occurred, reason for failure, day failure was identified and day repair activity was completed, and (2) identify the repair parts associated with each maintenance event.

DRAFT Maintenance & Repair Data – June 2017 Release