Attachment 0001 - CONTRACT COST AND DATA REPORTING (CSDR) PLAN.pdf

PDF 915 KB Posted

Attached to
M109A7 Self-Propelled Howitzer (SPH) and M992A3 Carrier, Ammunition, Tracked (CAT) Threshold 2 Armor Kits
Solicitation number
W56HZV-20-R-0164
Issued by

View the file

Other files

Show all 16

On GovTribe

Work with this file

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file

Text version

DRAFT DD FORM 2794, JANUARY 2019 PREVIOUS EDITION IS OBSOLETE Page 1 of 8

COST AND SOFTWARE DATA REPORTING PLAN OMB No. 0704-0188

The public reporting burden for this collection of information is estimated to average 8 hours per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection of information. Send comments regarding this burden estimate or any other aspect of this collection of information, including suggestions for reducing the burden, to Department of Defense, Executive Services Directorate (0704-0188). Respondents should be aware that notwithstanding any other provision of law, no person shall be subject to any penalty for failing to comply with a collection of information if it does not display a currently valid OMB control number.

PLEASE DO NOT RETURN YOUR COMPLETED FORM TO THE ABOVE ORGANIZATION.

1a. PROGRAM NAME

M109 Family of Vehicles (FoV)

1b. PHASE/MILESTONE (check all that apply) Pre-A A B

C-LRIP

C-FRP

X O&S

1c. PRIME MISSION PRODUCT

T2 Armor Kits and Components

1d. ACQUISITION CATEGORY (ACAT) Pre-ACAT

X ACAT I (MDAP)

ACAT IA (MAIS)

ACAT II

ACAT III

Other

2. COMMODITY TYPE

Electronic or Generic System

3. PLAN ITERATION TYPE

X INITIAL

REVISION

4. CURRENT SUBMISSION DATE (YYYYMMDD)

20230201

5. LAST APPROVED PLAN DATE (YYYYMMDD)

6a. GOVERNMENT PLAN POINT OF CONTACT (POC) NAME (Last, First, M.)

Schneider, Randy J

6b. ADDRESS (Include ZIP Code) 6501 E 11 Mile Road

SFAE-GCS-HB

Detroit Arsenal, MI 48397-5000 6c. TELEPHONE NUMBER (Include Area Code)

(586) 239-8039

6d. E-MAIL ADDRESS randy.j.schneider2.civ@mail.mil

7. PLAN TYPE

GOVERNMENT

X CONTRACT (PRIME)

CONTRACT (SUB)

8. PLAN GOVERNMENT PREPARING ORGANIZATION

PM Self Propelled Howitzer Systems

9a. CONTRACTOR NAME/ADDRESS

i. REPORTING ORGANIZATION NAME

TBD

ii. DIVISION NAME

iii. LOCATION

iv. CONTRACTOR BUSINESS DATA REPORT (CBDR 1921-3) REQUIREMENT:

CBDR REQUIRED FOR THIS ORGANIZATION

9b. CONTRACT NUMBER (List all that apply, separated by commas)

TBD - (A-13-C-C6)

9c. APPROPRIATION (check all that apply)

RDT&E

X PROCUREMENT

O&M

FMS

WCF

OTHER

10a. APPROVED PLAN NUMBER

A-13-C-C6

10b. APPROVED PLAN REVISION NUMBER

10c. APPROVED PLAN REQUIREMENTS X AT COMPLETION COSTS FOR STANDARD FUNCTIONAL CATEGORIES (FlexFile or Legacy) X AT COMPLETION COSTS FOR RECURRING/NONRECURRING (FlexFile only)

TECHNICAL DATA REQUIRED

10d. COST REPORT TYPE

X FLEXFILE

LEGACY DD 1921 SERIES

DRAFT DD FORM 2794, JANUARY 2019 PREVIOUS EDITION IS OBSOLETE Page 2 of 8

COST AND SOFTWARE DATA REPORTING PLAN

11. WORK BREAKDOWN STRUCTURE (WBS) 12. COST 13. TECHNICAL DATA

a. WBS

CODE

b. WBS LEVEL c. WBS ELEMENT NAME a. ACTUALS TO

DATE (ATD)

b. LEGACY

1921-1

c. LEGACY

1921-2

d. LEGACY

1921-5

e. EAC/FAC

(See item 10d)

a. QUANTITY

b. SRDR

FORMATS

c.

MAINT. &

REPAIR

PARTS

i. QUANTITY

DATA

ii. GFE

QUANTITY

1.0 1 M109 Family of Vehicles (FoV) T2/Armor Kits

1.1 2 M109 FoV T2/Armor Kits X

1.1.1 3 T2/Armor Kit Integration, Assembly, Test, and Checkout X X X

1.1.2 3 T2/Armor Kit Hardware X

1.1.2.1 4 T2/Armor Kit Non-Packaging Hardware X X X

1.1.2.2 4 T2/Armor Kit Packaging Hardware X X X

1.1.3 3 T2/Armor Kit Subsystem Software Release X X

1.1.4 3 T2/Armor Kit Transportation X X X

1.2 2 M109 FoV Integration, Assembly, Test, and Checkout X X

1.3 2 Systems Engineering

1.3.1 3 Software Systems Engineering X X

1.3.2 3 Integrated Logistics Support (ILS) Systems Engineering X X

1.3.3 3 Cybersecurity Systems Engineering X X

1.3.4 3 Core Systems Engineering X X

1.3.5 3 Other Systems Engineering 1...n (Specify) X X

1.4 2 Program Management

1.4.1 3 Software Program Management X X

1.4.2 3 Integrated Logistics Support (ILS) Program Management X X

1.4.3 3 Cybersecurity Management X X

1.4.4 3 Core Program Management X X

1.4.5 3 Other Program Management 1...n (Specify) X X

1.5 2 System Test and Evaluation

1.5.1 3 Development Test and Evaluation X X

1.5.2 3 Operational Test and Evaluation X X

1.5.3 3 Live Fire Test and Evaluation X X

1.5.4 3 Mock-ups/System Integration Labs (SILs) X X

1.5.5 3 Test and Evaluation Support X X

1.5.6 3 Test Facilities X X

1.6 2 Training

1.6.1 3 Equipment X X

1.6.2 3 Services X X

1.6.3 3 Facilities X X

1.6.4 3 Training Software 1...n (Specify) X X

1.7 2 Data

1.7.1 3 Data Deliverables X X

1.7.2 3 Data Repository X X

1.7.3 3 Data Rights 1...n (Specify) X X

1.8 2 Peculiar Support Equipment

1.8.1 3 Test and Measurement Equipment X X

1.8.2 3 Support and Handling Equipment X X

1.9 2 Common Support Equipment

1.9.1 3 Test and Measurement Equipment X X

1.9.2 3 Support and Handling Equipment X X

1.10 2 Operational/Site Activation by Site

1.10.1 3 System Assembly, Installation, and Checkout on Site X X

1.10.2 3 Contractor Technical Support X X

1.10.3 3 Site Construction X X

1.10.4 3 Site/Ship/Vehicle Conversion X X

1.10.5 3 Interim Contractor Support (ICS) X X

1.11 2 Contractor Logistics Support (CLS) X X

1.12 2 Industrial Facilities

1.12.1 3 Construction/Conversion/Expansion X X

1.12.2 3 Equipment Acquisition or Modernization X X

1.12.3 3 Maintenance (Industrial Facilities) X X

DRAFT DD FORM 2794, JANUARY 2019 PREVIOUS EDITION IS OBSOLETE Page 3 of 8

11. WORK BREAKDOWN STRUCTURE (WBS) 12. COST 13. TECHNICAL DATA

a. WBS

CODE

b. WBS LEVEL c. WBS ELEMENT NAME a. ACTUALS TO

DATE (ATD)

b. LEGACY

1921-1

c. LEGACY

1921-2

d. LEGACY

1921-5

e. EAC/FAC

(See item 10d)

a. QUANTITY

b. SRDR

FORMATS

c.

MAINT. &

REPAIR

PARTS

i. QUANTITY

DATA

ii. GFE

QUANTITY

1.13 2 Initial Spares and Repair Parts X X

Subtotal Cost X X

Reporting Contractor G&A X X Reporting Contractor Undistributed Budget X X Reporting Contractor Management Reserve X X Reporting Contractor FCCM X X Total Cost X X

Reporting Contractor Profit/Loss or Fee X X

Total Price X X

DRAFT DD FORM 2794, JANUARY 2019 PREVIOUS EDITION IS OBSOLETE Page 4 of 8

14. CSDR SUBMISSION EVENTS

a.

EVENT ID

b.

DATA REPORT(S)

c.

SUBMISSION EVENT NAME

d.

REPORT CYCLE

e. AS OF DATE f. DUE DATE

(YYYYMMDD) (YYYYMMDD)

1 Cost and Hour Report (FlexFile), Quantity Data Report Contract Award Initial 20231215 20240214

2 Cost and Hour Report (FlexFile), Quantity Data Report Annual Report 1 Interim 20241215 20250214

3 Cost and Hour Report (FlexFile), Quantity Data Report Annual Report 2 Interim 20251215 20260214

4 Cost and Hour Report (FlexFile), Quantity Data Report Annual Report 3 Interim 20261215 20270214

5 Cost and Hour Report (FlexFile), Quantity Data Report Annual Report 4 Interim 20271215 20280214

6 Cost and Hour Report (FlexFile), Quantity Data Report Annual Report 5 Interim 20281215 20290214

7 Cost and Hour Report (FlexFile), Quantity Data Report Contract Complete Final 20290622 20290822

DRAFT DD FORM 2794, JANUARY 2019 PREVIOUS EDITION IS OBSOLETE Page 5 of 8

15. REMARKS

a. CSDR Planning Approach & Preparation Instructions

1. In addition to the direction provided in the associated CSDR Data Item Descriptions (DIDs) and the CSDR Manual (DoDM 5000.04), all following instructions, requirements, and considerations found on this page/worksheet shall be utilized when collecting data and preparing CSDR submissions.

- The term "reporting entity" as used in this CSDR Plan refers to the organization preparing and submitting the CSDR data deliverables which could be a contractor, subcontractor, or Government depot/lab, etcetera.

- The term "contract" refers to any agreement between the Government and the reporting entity which includes actual contracts, any “agreements” (in the case of a contract executed under 10 U.S.C. 2371b (Other Transaction Authority (OTA)), a Military Interdepartmental Purchase Request (MIPR), or Memorandum of Agreement (MOA) between Government organizations (e.g., a Program Management Office and a depot/lab).

- The term "subcontract" refers to any agreement, purchase order, or instrument other than a prime contract calling for work or for the material required for the performance of one or more prime contracts. It usually covers procurement of major components or subsystems that require the subcontractor to do extensive design, development, engineering, and testing to meet a prime contractor’s procurement specifications.

2. This CSDR Contract plan is intended to capture costs associated with the contract number(s) listed in block 9.b. The contractor shall capture and report any and all costs incurred in order to perform the scopes of work on the Contract irrespective of contract type (e.g., firm-fixed price, cost-plus fixed fee) or funding source (i.e., via contract, via contractor internal research & development funds).

3. Costs reported against this CSDR Plan shall be cumulative in nature (i.e., each submission shall report any and all costs incurred on and prior to the submission’s “AS OF DATE” (block 14.e)).

4. Other than the Resource Distribution Table, submission events associated with this CSDR Plan are classified as either "Initial", "Interim", or "Final" submissions as identified in block 14.d of this CSDR Plan.

i. Submission events marked "Initial" shall report the reporting entity's total anticipated contract cost and resulting price using the maximum allowable contractor quantities, hours, or options (as applicable). For sealed bid contracts (i.e., contracts awarded under FAR Part 14) the reported FAC/EAC shall equal the value of the reporting entity's sealed bid (using the maximum allowable contractor quantities, hours, or options (as applicable)). For negotiated contracts (i.e., contracts award under FAR Part 15) the reported FAC/EAC shall be equal in overall value to the reporting entity's best and final offer (and consistent in distribution with any supporting cost and pricing data (e.g., basis of estimates, engineering build-ups) (using the maximum allowable contractor quantities, hours, or options (as applicable)). For all other contracts, the reported FAC/EAC shall be equal in overall value to the reporting entity's final proposal and consistent in distribution with any supporting data provided to substantiate the contract's value, reasonableness, and/or realism (e.g., basis of estimates, engineering build-ups) (using the maximum allowable contractor quantities, hours, or options (as applicable)). No ATD costs are anticipated to reported on an "Initial" submission except for any certified precontract costs incurred prior to or on the date of contract award.

ii. "Interim" report submissions are any report that is not either an "Initial" or "Final" report. Reported ATD, EAC/FAC, and quantities on "Interim" submissions shall be prepared reflecting only the value of work, quantities, hours, or options (as applicable) awarded on the report's "As Of Date" (do not include costs for anticipated but not awarded scopes of work, quantities, hours, or options).

iii. Reported ATD, EAC/FAC, and quantities on "Final" submissions shall be prepared reflecting the value of work, quantities, hours, and options (as applicable) anticipated to be awarded on a contract and meet the conditions listed in block 15.c.i.4 below.

5. Regarding the WBS Structure (block 11): This CSDR Plan utilizes MIL-STD-881D as the baseline for its WBS which has been extended to provide additional insight into system(s) or subsystem(s) which the Government believes to be high-risk or high-technical-interest in accordance with DoD Manual 5000.04.

i. WBS Element Names (block 11.c) Ending with "1...n (Contractor Shall Specify)": The contractor shall extend and specify (i.e., include additional WBS elements determined by the contractor) in order to provide additional insight into the contractor's technical approach or design. The additional WBS elements shall be developed in accordance with the WBS guidelines included in MIL-STD-881D and DoD Manual 5000.04.

ii. The contractor may extend any WBS element to allow the contractor to provide additional insight into its technical solution. Any and all extensions or tailoring of the WBS shall be in accordance with guidelines included in MIL-STD-881D and DoD Manual 5000.04.

iii. If changes to the contract scope, hours, or options (as applicable) necessitate the need to revise or add additional WBS elements to remain in compliance with MIL-STD-881D and DoD Manual 5000.04, any associated contract cost/price changes related to the updated CSDR Plan or submission of revised CSDR deliverables, shall be included within the contract modification that awards the changed scope of work, hours, or options (as applicable).

6. For effort reported under WBS Element 1.1.4, the reporting entity is requested to provide the quantity and effort of the item transported within the "Summary Remarks" section.

b. Resource Distribution Table

1. Submissions of the Resource Distriubtion Table (RDT) are required under the following conditions:

i. An RDT shall be delivered seven calendar days before the “Post-Award Cost and Software Data Reporting Conference”. Prepare this submission of the RDT at FAC/EAC value and utilizing the instructions at Block15.a.4.i.This copy of the RDT will be used during the “Post-Award Cost and Software Data Reporting Conference” in order to finalize which subcontractors will be required to provide CSDR reporting via electronic submission of deliverables directly to the Defense Cost and Resource Center (DCARC) and which subcontractors may qualify for a CSDR direct reporting subcontractor waiver.

ii. An RDT shall be delivered within thirty calendar days of the contractor identifying that a subcontractor who, at the time of initial subcontractor award, was not anticipated to qualify for direct subcontractor CSDR reporting via electronic submission of deliverables directly to the DCARC but is subsequently anticipated to meet the CSDR direct reporting subcontractor threshold value due to changes to scopes of work, end-item design, subcontractor/supplier, or subcontract price changes since initial contract award (unless the newly identified subcontractor has already been issued a subcontractor reporting waiver associated with this contract).

DRAFT DD FORM 2794, JANUARY 2019 PREVIOUS EDITION IS OBSOLETE Page 6 of 8

c. Submission Dates

i. All CSDR deliverable “AS OF DATE[S]” and “DUE DATE[S]” listed in blocks 14.e and 14.f are identified for planning purposes only. Submission dates are subject to change and are determined in accordance with the event drivers as identified below:

i. All “DUE DATE” requirements are equal to the “AS OF DATE” plus 60 calendar days. If the calculated “Due Date” does not fall on a regular business day, the “Due Date” will be the next regular business day on the contractor’s accounting calendar.

ii. Initial Submission: Submission events marked as an "Initial" submission in block 14.d. shall have an “AS OF DATE” as of the date of contract award.

iii. Interim Submission(s): Submission events marked as an "Interim" submission in block 14.d shall have an "AS OF DATE" based on the submission event name in block 14.c. For example, if the submission event name was "Contract Award Plus 24 Months" then the submission's "AS OF DATE" is the contract award date plus 24 calendar months. If the submission event name was "Complete Delivery of First Article Test Assets" then the submission's "AS OF DATE" would be the date the final First Artical Test Asset was delivered.

iv. Final Submission(s): Submission events marked as "Final" submission in block 14.d shall have an "AS OF DATE" when the following conditions have been met:

1. Condition 1: All end items anticipated to be procured on the contract have been delivered and accepted by the government (e.g., as evidenced by a completed DD Form 250) or higher tier contractor in the case of a subcontractor.

2. Condition 2: 95% or more of all ATD total costs have been incurred relative to all costs the reporting entity expects to incur for each and every Order/Lot (defined in Data Group B, Item 4 of the approved FlexFile DID).

d. Cost and Hour Report (FlexFile)

1. The contractor shall utilize the following mappings from its accounting system when preparing and submitting FlexFile Actual Cost-Hour Data:

i. {To be determined during the Post-Award CSDR Conference based on contractor's accounting system}

ii. {To be determined during the Post-Award CSDR Conference based on contractor's accounting system}

iii. {To be determined during the Post-Award CSDR Conference based on contractor's accounting system}

n. {To be determined during the Post-Award CSDR Conference based on contractor's accounting system}

2. The contractor shall utilize and include the following mappings from its accounting system to the Actual Cost-Hour Data tags:

i. WBS Element 1.1.4, T2/Armor Kit Transportation. The reporting entity is requested to utilize OCONUS/CONUS determination for item shipping destination = Tag1

ii. {To be determined during the Post-Award CSDR Conference based on contractor's accounting system} = Tag2

iii. {To be determined during the Post-Award CSDR Conference based on contractor's accounting system} = Tag3

xxv. {To be determined during the Post-Award CSDR Conference based on contractor's accounting system} = Tag25

3. The contractor shall provide the following files in order to meet the FlexFile DID's allowed, contractor provided format submisison option:

i. {To be determined during the Post-Award CSDR Conference}

4. End Item Scope: Block 17 of this CSDR Plan is meant to capture the discrete hardware end items that are DD-250'ed, ordered, procured, or exercised (as applicable) on the contract. If an End Item is DD-250'ed, ordered, procured, or exercised (as applicable) on the contract but is not listed in block 17, the contractor shall submit the dollars and hours in the Cost and Hour Report (FlexFile) and the quantity information in the Quantity Report tagged using the name of the End Item utilized on the contract. The CSDR Plan will be updated to include the appropriate End Item name in block 17, after reprot submission, if required.

i. End Item ID 1: The "Common" end item tag shall be used to report costs and hours which are not incurred or directly attributable to an individual end item. For example, overarching program management costs and hours that are required, independent of the type or quantity of end items on contract would be tagged against the “Common” end item. Common hardware (i.e., identical/homogeneous part numbers) procured and integrated into multiple end items shall utilize the end item tag for the prime product they were integrated onto and shall not be tagged with the “Common” end item.

ii. End Item ID 2: "T2 SPH Kit" shall be reported against WBS 1.1 (M109 FoV T2/Armor Kits) with associated costs and hours attributed to the lowest level children WBS elements found beneath it.

iii. End Item ID 3: "T2 CAT Kit" shall be reported against WBS 1.1 (M109 FoV T2/Armor Kits) with associated costs and hours attributed to the lowest level children WBS elements found beneath it.

iv. End Item ID 4: "Underbelly Kit" shall be reported against WBS 1.1 (M109 FoV T2/Armor Kits) with associated costs and hours attributed to the lowest level children WBS elements found beneath it.

DRAFT DD FORM 2794, JANUARY 2019 PREVIOUS EDITION IS OBSOLETE Page 7 of 8

v. End Item ID 5: "Undersponson SPH Kit" shall be reported against WBS 1.1 (M109 FoV T2/Armor Kits) with associated costs and hours attributed to the lowest level children WBS elements found beneath it.

vi. End Item ID 6: "Undersponson CAT Kit" shall be reported against WBS 1.1 (M109 FoV T2/Armor Kits) with associated costs and hours attributed to the lowest level children WBS elements found beneath it.

5. The contractor shall provide unit reporting for any given Order/Lot and End Item name as outlined in block 18 of this CSDR Plan. If Unit Reporting is selected in block18.c (Unit Reporting), it is expected that all touch labor costs and hours that are associated with the discrete units or sublots be tagged as Touch Manufacturing or Touch Maintenance as defined in DI-FNCL-82162, Data Group E, Item 7.

e. Period Of Performance & Additional Scope Of Work

1. If the Contract period of performance is extended by more than six months, or if the scope of work is modified to include work not otherwise covered by the CSDR Plan, the government may modify the CSDR Plan to require additional submission events and add additional WBS elements in order to ensure the accurate and complete collection of cost data associated with the modified contract. Depending on the scope and complexity of the contract modification, the contractor may be required to host or attend an additional Post-Award Cost and Software Data Reporting Conference to review the CSDR Plan changes and the contractor’s plan to collect and report costs associated with the additional scope of work.

f. Cost Accounting Standards (CAS) Disclosure Statement Differences

1. The contractor shall follow the accounting procedures specified in its latest approved CAS Disclosure Statement and with any clauses or requirements included in the contract. As part of the Post-Award Cost and Software Data Reporting Conference, the contractor shall identify any aspect(s) of its latest approved CAS Disclosure Statement which preclude or inhibit compliance with this CSDR Plan and DoD 5000.04 (CSDR Manual). The contractor shall identify any deviations from its CAS disclosure statement it intends to utilize to prepare CSDR submissions.

g. Nonrecurring/Recurring Segregation

1. The contractor shall utilize the specific definitions and requirements in the CSDR Manual (DoDM 5000.04) and the definitions in the DID for the Cost and Hour Report (FlexFile) report (DI-FNCL-82162) to segregate Recurring and Nonrecurring costs discretely and not as an aggregate.

h. COVID-19 Reporting

1. The contractor shall provide a description of the type and timing of all impacts to program schedule, incurred actual costs, forecasted at complete costs, in process quantities, and delivered quantities, which are directly attributable to the COVID-19 pandemic.

Per the DIDs, note any relevant information that could be used in the interpretation of the data. Provide general or, if available, quantifiable contract impacts within the Summary Remarks. Provide impacts to specific WBS Elements or Functional Elements within the Remarks by DD FORM 2794 WBS Element. Provide impacts to the business unit within the Remarks of each 1921-3 submission. Organize impacts under a heading in the remarks that refers to “COVID-19 impacts”, or similar language, that segments this information from the rest of the remarks.

If applicable, the contractor shall provide an explanation of any new charge codes, work packages, control accounts, pricing categories, or other methods explicitly utilized to capture impacts of COVID-19.

If there are no impacts to report, then report there are no impacts in the Summary Remarks of each FlexFile and the Remarks of each 1921-3 submission.

2. Additional Data Fields #1-#12 (FlexFile)

i. If applicable, the contractor shall utilize a “Tag” or the “Additional Data Field” referenced in Section B of the FlexFile DID (DI-FNCL-82162) to identify COVID-19 related data

i. CSDR Readiness Review Conference

1. The contractor shall host a CSDR Readiness Review Conference at the contractor’s facility where CSDRs are prepared with the Government’s Cost Working Group Integrated Product Team (CWIPT) IAW DFARS 242.503-2(b) and DoD Manual 5000.04 (CSDR Manual). The purpose of the Readiness Review Conference is to review the contract’s CSDR requirements and assess how the Contractor’s accounting system satisfies the CSDR requirements found in DoD 5000.04 (CSDR Manual) and this CSDR Plan. In a briefing presented by the Contractor in its own format, the Contractor shall:

- Demonstrate how it collects cost data in its accounting system and how that data will be utilized to provide actual cost transactions and minimize cost allocations when preparing CSDR data deliverables.

- Describe how recurring vs. nonrecurring costs are segregated in its accounting system and for the purpose of CSDR reporting.

- Demonstrate how the data from its accounting system will be mapped into the CSDR reports required by this CSDR Plan and associated CDRLs.

- Present the methodologies used for mapping internal cost accounts to the WBS, specifically showing how individual WBS elements and functional element codes will be populated.

- Propose any changes to this CSDR Plan in order to tailor the plan to the contractor's accounting system to include any contractor recommended changes or additions to the WBS elements. These changes may include adjustments to the submission events and/or submission timelines, particularly in the case of a direct-reporting subcontractor performing against a different delivery schedule than the associated prime contractor.

The contractor and CWIPT will also review the initial submission of the "Resource Distribution Table (RDT)", in order to finalize which subcontractors will be required to provide CSDR reporting and electronic submission of deliverables directly to the Defense Cost and Resource Center (DCARC) and which subcontractors may qualify for a CSDR direct reporting subcontractor waiver.

The Readiness Review shall be held within 90 days of contract award or the start of work meeting on a date mutually agreed to by the CWIPT and the contractor. This meeting has an anticipated duration of one business day.

DRAFT DD FORM 2794, JANUARY 2019 PREVIOUS EDITION IS OBSOLETE Page 8 of 8

INTRA-CONTRACT SCOPE REPORTING DEFINITION

16. ORDERS/LOTS

a. ID b. NAME c. PHASE/MILESTONE 1 Delivery Order 1 O&S

2 Deliver Order 2 O&S

3 Delivery Order 3 O&S

4 Delivery Order 4 O&S

5 Delivery Order 5 O&S

...n Delivery Order ...n O&S

17. END ITEMS

a. ID b. NAME 1 Common

2 T2 SPH Kit

3 T2 CAT Kit

4 Undersponson SPH Kit

5 Undersponson CAT Kit

18. UNIT/SUBLOT REPORTING AND UNIT SEQUENCING REQUIREMENTS

a. ORDER/LOT ID b. END ITEM ID c. UNIT/SUBLOT REPORTING (X if applicable)

d. UNIT SEQUENCING (X if applicable)

1 2 X X

1 3 X X

1 4 X X

1 5 X X

2 2 X X

2 3 X X

2 4 X X

2 5 X X

3 2 X X

3 3 X X

3 4 X X

3 5 X X

4 2 X X

4 3 X X

4 4 X X

4 5 X X

5 2 X X

5 3 X X

5 4 X X

5 5 X X

Name Role Decision Date Signature

Rick Burke CA Deputy Director Approved 2/24/2023 12:13:46 PM

Kelly Hazel DCARC Director Approved 2/17/2023 11:35:16 AM

Daniel Germony CAPE Analyst Approved 2/2/2023 12:04:40 PM

File details come from the government source that posted it. Updated .