6_DID-A001_CSDR_Res-Distro-Table-Instructions.pdf

Addenda for CSDR Plans.

Provide the following additional information on a separate page(s) attached to the program or contract plan.

a. Resource Distribution Table (RDT) (formerly referred to as the Resource Assignment Matrix (RAM)).

The RDT is designed to provide an overview of the program’s total or contract acquisition funding and to help ensure that all contracts meeting the reporting thresholds contain CSDR requirements. Provide the name and address of any prime contractors, subcontractors, lower-tier subcontractors, and government-furnished equipment (GFE) providers that may meet the CSDR thresholds along with the specific WBS elements for which they are responsible. Include support contracts, government testing facilities, training facilities, and all other acquisition costs.

1. Program Plan RDT.

Contract/subcontract information provided in the RDT section must be consistent with the current contract and cost information provided in other official program acquisition documents such as the Selected Acquisition Report (SAR) and the Acquisition Plan (required by the Federal Acquisition Regulation (FAR)) and is required to be updated every year. Note that including a particular contract or subcontract in the RDT does not automatically result in CSDR being required. This decision is made by the CWIPT in coordination with the DoD PM. An example of a properly completed RDT can be found at the DCARC Web site. The information supplied is not intended in any way to preempt the prime contractor’s selection process for subcontractors. Instead, its purpose is to establish an early tracking mechanism to ensure all appropriate reporting requirements are implemented. The information contained in the RDT is required to be updated as RFPs are issued and contracts are awarded.

i. Enter the total program cost for the milestone/phase identified in Item 1c.

ii. The following information is mandatory for each prime contract:

a) Identify the contractor if known; otherwise enter ”TBD” (for “to be determined”) and include the estimated total contract value and the estimated total software development effort which, for CSDR purposes, represents the expected price at contract completion (i.e., initial contract award plus all expected contract changes). This value must also be based upon the assumption that all contract options will be exercised.

b) Identify each subcontractor if known; otherwise enter “TBD” (for “to be determined”) and its expected value and software development effort which, for CSDR purposes, represents the expected price at contract completion (i.e., initial contract award plus all expected contract changes). This value must also be based upon the assumption that all contract options will be exercised.

c) Using the WBS contained in Item 11 of the CSDR Plan, annotate with “X” the WBS elements for which the Prime contractor and each subcontractor have or will have effort.

iii. For government-furnished equipment (GFE):

a) Identify each source of GFE and its estimated total value and estimated total software development effort which, for CSDR purposes, represents the expected price at completion (i.e., initial funding plus all expected changes). This value must also be based upon the assumption that all funding options will be exercised. If the GFE is already on contract, provide the assigned prime contract number the Government has with the prime contractor along with the contractor name.

b) Using the WBS contained in Item 11 of the CSDR Plan, annotate with “X” the WBS elements for which the source of GFE has or will have effort.

2. Contract/Subcontract Plan RDT. Subcontract information provided in the RDT section must be consistent with current contract/subcontract information provided in the program plan RDT, that is, it must reflect the most current contract or subcontract value (including all mods and CLINs), and must conform to the applicable rules established above for the program plan RDT. In addition, include the assigned subcontract number for each subcontract between the prime and the subcontractor.

DD 2794 Form Instructions Revisions History

Rev Date Changes

0 4/26/2007 N/A

1 10/5/2007 • Item 1a: Changed example MDAP from AESA to UH-60M. •

Item 2: Removed ―Appendix A‖ from example entry. • Item 5:

Changed direction for initial plan submissions from entering

―initial‖ to leaving item blank. • Item 10b: Reiterated preference for numeric decimal WBS codes. • Item 13a: Changed direction from providing ―N/A‖ for non-applicable elements, to providing

―X‖ for every non-summary element. Removed direction for

CWBS column to match DD 1921 column. • Item 13b: Changed direction from providing ―N/A‖ for all non-applicable elements, to providing ―X‖ for all MIL-HDBK881A common elements.

Removed direction for DD 1921 column to match CWBS column.

• RDT Description: Provided additional language on purpose of

RDT, costs which must be included, and requirement for a total funding line for all providers not meeting thresholds. •

Contract/Subcontract Plan RDT: Clarified contract/subcontract values are required according to same definition provided in

Program RDT section.

2 3/7/2008 • Item 2 & 9: Edited item names for consistency with DD 2794 field names. • Item 11: Added instructions for usage of

―Non-MIL-HDBK 881 Attributable Costs‖ WBS element. • Item

15b: Revised language from ―these entries are mandatory‖ to

―these topics are mandatory‖.

3 6/2/2008 • Added revisions history table.

4 8/6/2008 • Item 15b: Added additional standard language for recurring/nonrecurring definitions.

5 6/3/2009 • Item 15b: Added mandatory language describing the requirement for the DD Form 1921-3.

6 5/18/2011 • Item 1a renamed Major Program / Name. • Item 1b

Phase/Milestone and Item 1c Prime Mission Product renumbered. •

Item 2 renamed WBS System Type. • Items 9a Contractor Name, 9b Contract Number moved (were 12a/b); Item 9c Appropriation added. • Items 11a Program/Contract/Subcontract and 11b

Contract/Subcontract modified. • Item 13 Reports Required:

expanded for clarification and to fit current uses. • Item 14 CSDR

Submission Dates: modified for Final Reports. • Item 15 Remarks:

added section about technical metrics. • Updated references to match current DoD organizational structure and documents.