CSDR Reporting Policies

CSDR Reporting Policies

1

DODI 5000.02
CSDR Requirements

Operation of the Defense Acquisition System

Department of Defense Instruction (DoDI) 5000.02, “Operation of the Defense Acquisition System,” dated January 7, 2015, summarizes CSDR requirements and reporting thresholds in Enclosure 1, Table 7, and describes Acquisition Category (ACAT) designations and descriptions in Enclosure 1, Table 1.

2

DODI 5000.73
Cost Analysis Guide

Cost Analysis Guidance and Procedures

The DoDI 5000.73, “Cost Analysis Guidance and Procedures,” dated June 9, 2015, incorporates and cancels DoD 5000.4-M, “Cost Analysis Guidance and Procedures.” It addresses CSDRs in Section 4.c.(1) and cites the still-active DoD 5000.04-M-1, “Cost and Software Data Reporting (CSDR) Manual.” It also establishes policy, assigns responsibilities, and provides procedures for the conduct of cost estimation and analysis in the DoD.

3

DODM 5000.04-M-1
CSDR Manual

Cost and Software Data Reporting Manual

The DoDM 5000.04-M-1, Cost and Software Data Reporting (CSDR) Manual, serves as the primary requirements document for the development, implementation, and operation of the CSDR system to ensure data reported is accurate and consistent. Please see the Supporting Docs Needed for "New" and "Revised" CSDR Plans.

4

DFARS
CSDR Mandate

Defense Federal Acquisition Regulations

234.7101 COST AND SOFTWARE DATA REPORTING, revised November 5, 2014, mandates the CSDR requirement for MDAPs and MAIS programs meeting conditions outlined in the DoDI 5000.02 and DoD 5000.04-M-1. 252.234–7003 and 252.234–7004: Cost and Software Data Reporting System, revised June 26, 2015, establish content requirements and mandate the CSDR Manual, DoDM 5000.04-M-1 and CSDR DIDs. 242.503-2 Post Award conference procedure, revised November 24, 2010, requires CSDRs be discussed during postaward conferences.

5

MIL-STD-881C
Work Breakdown Structures

The MIL-STD-881C, effective October 3, 2011 for all MDAP and MAIS programs that meet the requirements for CSDR reporting, MIL-STD-881C shall be implemented as a contract reporting requirement. The MIL-STD-881C contains 11 different WBS appendices, addressing Aircraft, Ships, Vehicles, Space, UAV, etc. The WBS is a product-oriented family tree composed of hardware, software, services, data, and facilities.

6

Standard Co-Planning
Defense Federal Acquisition Regulations

The CSDR/EVM Co-Plan (DD 2794) Instructions outline the joint effort between the Cost Assessment and Program Evaluation (CAPE) and the Performance Assessments and Root Cause Analyses (PARCA). The CSDR/EVM Co-Plan will help ensure the reporting requirements and structures are properly defined respectively for both cost reporting and program execution. The CSDR/EVM Plan Standards serve as a common starting point for CSDR/EVM Co-Plan development. Based on MIL-STD-881C, the plans provide standardized product extensions that are meant to be tailored to the specific program or contract. The RDT Instructions (PDF) should be use to complete and submit the Resource Distribution Table (RDT) 60 days prior to RFP release. Derived from MIL-STD-881C, plans are created at the Program, Prime Contract, and Subcontract levels across all lifecycle phases. An RDT maps government organizations, prime contracts, subcontracts, and Government Furnished Equipment (GFE) contracts and associated dollar values on a specific program. This is the primary mechanism for determining which contracts meet the requirements for CSDR reporting.

7

RFP & CDRL Standard Language
Request for Proposal (RFP) & Cost Data Requirements List (CDRL) CSDR Standard Language

To accomplish the requirements outlined in the DFARS clause, an approved CSDR Plan should be included in an RFP Statement of Work (SOW) in the case of competitive awards and on the CDRLs of all contracts that require reporting, as outlined in Section C3.4.2.4 of the CSDR Manual. Contractors are required to respond to RFPs using the WBS on the approved CSDR Plan, or they may propose changes to the WBS that pertain to their specific solution. The DCARC requires that draft RFP language and draft CDRLs must be included along with the proposed approved CSDR Plan, 60 days prior to RFP release. Draft CSDR CDRLs (DD Form 1423-1) must be submitted to the DCARC 60 days prior to RFP Release. The documents below are example CDRLs for properly placing Cost and Software Data Reporting on contract:

CDRL TABLE

8

Post Contract Award Meeting
Procedures and Documentation

The Post Contract Award Meeting Procedures should be used as guidelines for The Cost and Software Data Reporting (CSDR) Post Award Meeting, which is a collaborative discussion between industry and the government with respect to industry's approach to fulfilling their contractual obligations with the CSDR Contract Plan and CSDR policy as well as the government's expectations for each CSDR submission.

9

Data Item Descriptions (DIDs) & Reporting Forms
DIDs & Cost and Software Data Reporting Forms

The DID and corresponding report form will be specified in Block 14, Submission Events, of the approved contract or subcontract CSDR/EVM Co-Plan. All applicable DIDs and reporting forms are available here:

DATA ITEM DESCRIPTIONS & FORM TABLE