Attachment 0011- Cost Report and Plan.pdf

SUBJECT: Cost and Software Data Reporting (CSDR) Plan Standard Policy

Please note the following instructions for all CSDR Plans:

The CSDR Manual, DoDM 5000.04-M-1, governs the application of CSDR requirements on all ACAT I Programs. The most recently approved Data Item

Descriptions (DIDs) for CCDRs, CWBS Dictionaries, and SRDRs must be used on all new contracts. The dollar thresholds governing the application of CSDRs to individual contracts and subcontracts are established in DoDI 5000.02, Operation of the Defense Acquisition System. The most recently approved versions of these documents must be used and applied on all new contracts.

Submit a copy of the pertinent Contract Data Requirement Lists (CDRLs) to the

Defense Cost and Resource Center (DCARC) within 30 days after the contract modification containing such requirements is awarded. This document must provide evidence that the CSDR requirements, as specified in the attached Contract CSDR

Plan, were placed on contract.

Contractors and subcontractors are required to submit the contract WBS (CWBS)

Index and Dictionary to the DCARC when the first report is due, or as specified in the

CSDR plan. The CWBS Dictionary must be maintained and updated throughout the life of the contract and resubmitted to the DCARC with CSDR submissions as changes occur.

A CA-approved Contract CSDR Plan must be included in all RFPs for contracts subject to CSDR reporting requirements per DFARS Section 234.7101. All contractors’ and subcontractors’ Contract CSDR Plans are to be submitted to DCARC for approval at least 60 days before issuing the solicitation to industry. Any changes to Contract CSDR Plans must be submitted to the DCARC for CA approval as individual contracts change. Contract CSDR Plans and subsequent changes must be approved prior to contract award, modification, or exercise of a contract option.

Contract CSDR Plans will also be updated to reflect current policies regarding CSDR requirements before a new contract or major modification is made.

Any RFP and ensuing contract for CSDRs must include the following requirement:

CSDRs must be submitted electronically to DCARC as DCARC approved Extensible

Markup Language (XML) files by report upload to the DCARC’s CSDR Submit-

Review system. The DCARC web site (http://cade.osd.mil/csdr) contains information about delivery methods and submission instructions.

W31P4Q-20-R-0015

ATTACHMENT 0011

The Contract CSDR Plan uses the event field as the driver for the submission of reports, not the "as of date." The "as of date" is based on current knowledge (when the CSDR Plan is developed) and is used for tracking purposes. If the event slips, it is the responsibility of the program office (PO) and/or Contractor to inform the

DCARC via the CSDR Submit-Review of the event slippage and allow DCARC to update the tracking system with the new event date. The DCARC will determine if a revised Contract CSDR Plan is required. If the PO and/or Contractor do not inform

DCARC, the submission will be treated as being late. Event slippages generally do not require that a revised Contract CSDR Plan be submitted. However, a Contract

CSDR Plan revision is required to add new events.

As referenced in CSDR Manual DoDM 5000.04-M-1, DD Form 1921-3, “Contract

Business Data Report” is required on all contracts issued after April 2, 2009 that contain CCDR requirements. This form must be submitted to DCARC in accordance with DI-FNCL-81765B.

Any questions relating to the subject Cost and Software Data Reporting Plan Standard

Policy may be directed to Mr. Kelly Hazel, (703) 614-5397.

Richard P. Burke

Deputy Director

Cost Assessment

W31P4Q-20-R-0015

ATTACHMENT 11

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

Army Integrated Air and Missile Defense (AIAMD)

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

X C-LRIP

X C-FRP

O&S

1c. PRIME MISSION PRODUCT

Army Integrated Air and Missile Defense (AIAMD)

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)

20191010

5. LAST APPROVED PLAN DATE (YYYYMMDD)

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

Perry, Alan

6b. ADDRESS (Include ZIP Code)

Bldg 5250 Martin Rd. Redstone Arsenal, AL

6c. TELEPHONE NUMBER (Include Area Code)

(256) 842-0493

6d. E-MAIL ADDRESS alan.w.perry.ctr@mail.mil

7. PLAN TYPE

GOVERNMENT

X CONTRACT (PRIME)

CONTRACT (SUB)

8. PLAN GOVERNMENT PREPARING ORGANIZATION

IAMD Project Office

9a. CONTRACTOR NAME/ADDRESS

i. REPORTING ORGANIZATION NAME

TBD

ii. DIVISION NAME

TBD

iii. LOCATION

TBD

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

X CBDR REQUIRED FOR THIS ORGANIZATION

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

TBD

9c. APPROPRIATION (check all that apply)

RDT&E

X PROCUREMENT

O&M

FMS

WCF

OTHER

10a. APPROVED PLAN NUMBER

A-19-D-C1

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)

X TECHNICAL DATA REQUIRED

10d. COST REPORT TYPE

X FLEXFILE

LEGACY DD 1921 SERIES

W31P4Q-20-R-0015

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 Integrated Air and Missile Defense (IAMD) Integrated Battle Command System (IBCS)

1.1 2 Integrated Battle Command System (IBCS)

1.1.1 3 Hardware

1.1.1.1 4 Engagement Operation Center (EOC) - S280 X

1.1.1.1.1 5 Hardware X X

1.1.1.1.2 5 Integration X X

1.1.1.2 4 EOC - Air Defense and Airspace Management (ADAM) X

1.1.1.2.1 5 Hardware X X

1.1.1.2.2 5 Integration X X

1.1.1.3 4 EOC -Air and Missile Defense Planning and Control System (AMDPCS) A X

1.1.1.3.1 5 Hardware X X

1.1.1.3.2 5 Integration X X

1.1.1.4 4 EOC - AMDPCS B X

1.1.1.4.1 5 Hardware X X

1.1.1.4.2 5 Integration X X

1.1.1.5 4 Integrated Collaborative Envronment (ICE) X

1.1.1.5.1 5 Hardware X X

1.1.1.5.2 5 Integration X X

1.1.1.6 4 Engagement Control Trailer (ECT) X

1.1.1.6.1 5 Hardware X X

1.1.1.6.2 5 Integration X X

1.1.1.7 4 Integrated Fire Control Network (IFCN) Relay X

1.1.1.7.1 5 Hardware X X

1.1.1.7.2 5 Integration X X

1.1.1.8 4 Plug and Fight Processing Unit (PFPU) X

1.1.1.8.1 5 Hardware X X

1.1.1.8.2 5 Integration X X

1.1.1.9 4 Sentinel B Kit X

1.1.1.9.1 5 Hardware X X

1.1.1.9.2 5 Integration X X

1.2 2 Platform Integration, Assembly, Test and Checkout X X X

1.3 2 System Engineering X X

1.4 2 Program Management 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 Mock-ups / System Integration Labs (SILs) X X

1.5.4 3 Test and Evaluation Support X X

1.5.5 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.7 2 Data

1.7.1 3 Technical Publications X X

1.7.2 3 Engineering Data X X

1.7.3 3 Management Data

1.7.3.1 4 CSDR Reporting X X

1.7.3.2 4 Other Reporting X X

1.7.4 3 Support Data X X

1.7.5 3 Data Depository 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

W31P4Q-20-R-0015

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.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.1 2 Operational/Site Activation

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 Sustainment/Interim Contractor Support X X

1.11 2 Industrial Facilities

1.11.1 3 Construction/Conversion/Expansion X X

1.11.2 3 Equipment Acquisition or Modernization X X

1.11.3 3 Maintenance (Industrial Facilities) X X

1.12 2 Initial Spares and Repair Parts

1.12.1 3 Initial Spares X X

1.12.2 3 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

W31P4Q-20-R-0015

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 AIAMD LRIP (FY21) Initial Cost and Hour Report (FlexFile), Quantity Data ReportInitial 20210630 20210831

2 Technical Data Report AIAMD Tech Data Initial Report Initial 20210831 20211031

3 Cost and Hour Report (FlexFile), Quantity Data Report AIAMD FRP 1 (FY22) Initial Cost and Hour Report (FlexFile), Quantity Data ReportInitial 20220630 20220831

4 Cost and Hour Report (FlexFile), Quantity Data Report AIAMD LRIP (FY21) Interim Cost and Hour Report (FlexFile), Quantity Data ReportInterim 20220630 20220831

5 Cost and Hour Report (FlexFile), Quantity Data Report AIAMD FRP 2 (FY23) Initial Cost and Hour Report (FlexFile), Quantity Data ReportInitial 20230630 20230831

6 Cost and Hour Report (FlexFile), Quantity Data Report AIAMD FRP 1 (FY22) Interim Cost and Hour Report (FlexFile), Quantity Data ReportInterim 20230630 20230831

7 Cost and Hour Report (FlexFile), Quantity Data Report AIAMD LRIP (FY21) Final Cost and Hour Report (FlexFile), Quantity Data ReportFinal 20230630 20230831

8 Technical Data Report AIAMD Tech Data Interim Report Interim 20231231 20240228

9 Cost and Hour Report (FlexFile), Quantity Data Report AIAMD FRP 3 (FY24) Initial Cost and Hour Report (FlexFile), Quantity Data ReportInitial 20240630 20240831

10 Cost and Hour Report (FlexFile), Quantity Data Report AIAMD FRP 2 (FY23) Interim Cost and Hour Report (FlexFile), Quantity Data ReportInterim 20240630 20240831

11 Cost and Hour Report (FlexFile), Quantity Data Report AIAMD FRP 1 (FY22) Final Cost and Hour Report (FlexFile), Quantity Data ReportFinal 20240630 20240831

12 Cost and Hour Report (FlexFile), Quantity Data Report AIAMD FRP 3 (FY24) Interim Cost and Hour Report (FlexFile), Quantity Data ReportInterim 20250630 20250831

13 Cost and Hour Report (FlexFile), Quantity Data Report AIAMD FRP 2 (FY23) Final Cost and Hour Report (FlexFile), Quantity Data ReportFinal 20250630 20250831

14 Technical Data Report AIAMD Tech Data Final Report Final 20251231 20260228

15 Cost and Hour Report (FlexFile), Quantity Data Report AIAMD FRP 3 (FY24) Final Cost and Hour Report (FlexFile), Quantity Data ReportFinal 20260630 20260831

W31P4Q-20-R-0015

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

15. REMARKS

NON-RECURRING/RECURRING DEFINITIONS

Recurring and Non-Recurring Costs required for all levels:

Recurring costs. Repetitive elements of development, investment or sustainment costs that may vary with the quantity being produced or maintained, irrespective of system life cycle phase and appropriation. Recurring cost categories include procurement, and production and maintenance activities; acceptance testing; maintenance and support equipment, training, and data; test articles built to an operational configuration; and certain elements of systems engineering and program management.

Examples of Prime Mission Product activities include repetitive costs incurred when building prototype, test systems, or production units to an operational configuration. Examples of Prime Mission Product Hardware activities include Fabrication and assembly of partial/full prototype, test, or production units whether for customer or contractor use; Raw material, purchased parts, equipment associated with the fabrication and assembly of partial/full prototype or test units whether for customer or contractor use; Touch labor, integration and assembly, installation and check out; Engineering support for production unit fabrication, assembly and check out.

Examples of Prime Mission Product Software activities include Procurement of stand-alone or bundled COTS software licenses used in an operational system and installation and checkout of developed software into production units. Examples of Systems Engineering activities include Sustaining engineering, logistics support, planning, organizing, monitoring and reporting activities, document maintenance. Examples of Program Management activities include programmatic, financial, contractual, schedule, planning, organizing, and monitoring (quality information assurance, configuration management) activities in support of production unit fabrication, assembly and check out; meetings & efforts in support of supplier, manufacturing & production activities.

Nonrecurring costs. Non-repetitive elements of development, investment or sustainment costs that generally do not vary with the quantity being produced or maintained, irrespective of system life cycle phase and the appropriation. Nonrecurring cost categories include product design and development (PD&D) activities, including those for modifications; system test and evaluation (ST&E) including ST&E for modifications; tooling; pre-production or pre-maintenance activities; design and development of support equipment, training, and data; and certain elements of systems engineering and program management.

Examples of Prime Mission Product PD&D activities are: Requirements definition, engineering design, analysis & development; Redesign, rework & retest due to design flaws & first time corrective actions; test articles built for testing purposes only (i.e., units that are not production-representative) such as wind tunnel models, and bench and coupon test articles;

structural development, static, fatigue, software, and ballistics testing; stress analysis; flight, ground, or sea testing of system properties; redesign as a result of testing; and retesting efforts; All configuration, quality, and data management efforts supporting release activity for first article configuration, delivery & certification; System safety plan, manuals, tech services, & maintenance manual development in support of first article delivery.

Examples of hardware design and development activities include material, purchased parts and labor associated with engineering models, operational models, bench, lab articles or partially built units (i.e. units that are not production representative), tooling, and ground support equipment for qualification, structural, static, fatigue or stress testing, and refurbishment of test units; and engineering support including manufacturing engineering, quality engineering, and tool engineering for development unit fabrication, assembly & tests.

Examples of software design and development activities include design and development of all software; delivered operational software and software developed to correct deficiencies and add capabilities; Initial integration of COTS and GOTS products into operational configuration; Support for HW-SW integration and test, system level testing; initial integration of COTS and GOTS products into operational configuration; and commercial software licenses for development facilities. System Engineering, Program Management, and Data activities occur throughout the system life cycle and are supportive in nature; as such, these costs take on the characteristics of the underlying activities being performed.

Examples of Systems Engineering activities include installation plans or quality inspection plans; requirements definition, allocation and flow-down; creation of specification and Interface Control Documents (ICDs); design and implementation of system security; top level design trade-offs; analyses, studies, and simulations for system performance and effectiveness, reliability, availability, maintainability or survivability; internal & external design review, IPT coordination & integration meetings; Certification & Control documentation; and supplier selection & coordination. Examples of Program Management activities include programmatic, financial, contractual, schedule, planning, organizing, and monitoring (quality information assurance, configuration management) activities in support of development, design & testing efforts.

Examples of System Test and Evaluation activities include development of test plans/procedures; subsystem and system level test and integration for developmental articles; test equipment in support of development including for static & fatigue testing, test stands, wind tunnel models, stress analysis, ballistics testing, flight, ground or sea testing of system, redesign from testing, retesting; System/Software Integration Laboratory (SIL) development; and analysis to support verification, validation & certification. Examples of Training activity include initial courseware development and simulator development. Examples of Initial Spares and Repair Parts activity include spare parts and material in support of the nonrecurring subsystem/system level articles.

Examples of Support Equipment activity include initial equipment design and test efforts, and test program sets development. Examples of Tooling activity include special test equipment, special tooling, procurement of initial & rate tooling, tool replacement (with the exact same tool) & tool modification (to accommodate product configuration changes).

Examples of Operational/Site Activation activity include site planning efforts.

FAC vs EAC

The checkmarks for EAC/FAC in column 12e at the WBS level shall be reported as "Forecast at Completion" (FAC). The Forecast At Completion (FAC) required here is not subject to the standards established in ANSI/EIA-748 guideline #27 (Estimate at Complete); therefore, the FAC does not need to be, but may be, derived from Industry Earned Value Management (EVM) processes.

IRAD EFFORT

The contractor should list the major relevant IRAD projects leveraged for this development effort, provide a brief description of the cost of the projects, and provide/attach any more detailed actual cost information at the level available.

WBS INDEX AND DICTIONARY

"The WBS Dictionary is a living document and must match the technical content, cost content, and work content of each end item (see Block 17) for all WBS elements for each Cost and Hour (FlexFile) submission. The dictionary shall contain a disclosure statement detailing any differences between the CSDR reporting methodology and the reporting entity's Cost Accounting Standards. The dictionary shall include a section detailing how parts are procured under this contract and any limitations of the parts procurement cost data or allocation of cost data for the WBS element.

The reporting entity must maintain and update the WBS Dictionary throughout the life of the contract, IAW DI-FNCL-82162, if changes to the WBS occur, the reporting entity shall annotate and track changes by adding the “As of Date” of the submitted FlexFile report and indicate the changes to the WBS Index and Dictionary Definitions.

For WBS elements identified in block 11 of the CSDR plan that is not within the contract's scope of work, the reporting entity shall report in the dictionary that “This CSDR WBS element is not associated with this contract’s scope of work”, and zero costs will be associated for ATD and FAC for these WBS elements."

COST ACCOUNTING STANDARDS (CAS) DISCLOSURE STATEMENT DIFFERENCES

Describe significant accounting changes from previous accounting period in the Remarks section of the reports, if applicable.

W31P4Q-20-R-0015

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

1921-3 CONTRACTOR BUSINESS DATA REPORT

a. The Contractor Business Data Report is prepared by and for the business entity (e.g., business unit, segment, or site) responsible for submitting the Forward Pricing Rate Proposal (FPRP) representing the basis for Forward Pricing Rate Agreement (FPRA) negotiations with the government.

b. Reports are submitted annually at the end of the contractor's fiscal year.

c. Data for Future Years should be reflective of the number of years contained in the most current document, i.e., the FPRP or the FPRA. If the document applies to more than three future years, attach additional future year sheets as required. In the absence of these documents, estimates should be provided for three future years.

d. The existing 1921-3 requires strictly formatted data and necessitates mappings to a government standard, the new DRAFT 1921-3 may be submitted in the contractor’s own format and according to the contractor’s own rate structure, so long as it meets the data requirements in the DRAFT 1921-3 Data Item Description DI-FNCL-81765.

END ITEMS/ORDER LOTS SCOPE IDIQ

Block 16 Orders/Lots is meant to capture the discrete Delivery Orders/Task Orders exercised on the contract. If a Delivery Order/Task Order is exercised on the contract and the CSDR plan has not been updated, it is the Reporting Entity's responsibility to still submit the dollars and hours in the FlexFile tagged to the appropriate Delivery Orders/Task Orders.

The CSDR plan will be revised accordingly to include all exercised Delivery Orders/Task Orders.

COST AND HOUR REPORT UNIT/SUBLOT REPORTING

The Reporting Entity is required to provide unit or sublot (specify) reporting for any given Order/Lot and End Item as outlined in block 18 of the DD Form 2794. If Unit Reporting is selected in item 18c (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 Data Group E, Item 7.

QUANTITY REPORTING

a. If the quantity for a given element differs from the quantity reported for the full system, provide a comment in the WBS Element Remarks section.

b. The Reporting Entity shall provide meaningful quantity information lower than the summary level in the remarks for WBS elements Peculiar Support Equipment, Common Support Equipment, and Initial Spares and Repair Parts, if applicable.

CSCIs

For Software Release and CSCI WBS Element Names identified in Item 11d. as Subcomponent Release 1..n or Subcomponent Release 1..n CSCI 1..n, the Reporting Entity must specify the specific releases and associated CSCIs at the post award meeting in order to revise the CSDR Plan to reflect the Reporting Entity’s actual releases and associated CSCIs.

FINAL COST REPORT

Final Cost Report to be submitted when final end item has been delivered and accepted by the government (e.g., as evidenced by a completed DD 250) and 95% or more of total costs for each Order/Lot (see Block 16) and each End Item (see Block 17) has been incurred.

POST AWARD CONFERENCE (PAC)

The Reporting Entity shall attend and participate in a post award CSDR conference which will be held with the Cost Working Group Integrated Product Team (CWIPT) IAW DFARS 242.503-2(b) and DoDM 5000.04-M-1 (CSDR Manual). During this meeting, the CWIPT and contractor will review the Reporting Entity's process for data collection and reporting to ensure it satisfies the guidelines outlined in the DoDM 5000.04-M-1, CSDR Manual, the approved CSDR plan reporting requirement, and the Resource Distribution Table. The Reporting Entity shall demonstrate how costs will be based, to the maximum extent possible, upon actual cost transactions and not cost allocations; describe how recurring

vs. nonrecurring costs will be segregated; demonstrate how the data from its accounting system will be mapped into the reporting categories in the approved CSDR plan. The Reporting Entity shall present the methodologies used for mapping internal cost accounts to the agreed upon WBS, specifically illustrating how individual WBS elements and functional element codes will be populated. The review shall include any reporting issue corrections and identify proposed changes to the approved CSDR Plan as necessary.

W31P4Q-20-R-0015

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

RESOURCE DISTRIBUTION TABLE (RDT)

The Reporting Entity is instructed to provide a Resource Distribution Table upon contract award, which identifies the value and work assigned to the Reporting Entity and its subcontractors. The Reporting Entity shall provide an updated RDT when additional quantities/scope are added to the contract to ensure that no major sub-contract(s) breach the direct CSDR reporting threshold specified in DoDI 5000.02 and DoDM 5000.04-M-1.

PERIOD OF PERFORMANCE (POP)

If contract Period of Performance is extended, the contractor shall submit an additional cost report for each additional year of extension. The final report will be moved to the revised end of the Period of Performance.

W31P4Q-20-R-0015

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 LRIP Low Rate Initila Production (LRIP)

17. END ITEMS

a. ID b. NAME EOC Engagement Operation Center

ADAM Air Defense and Airspace Management (ADAM)

AMDPCS A Air and Missile Defense Planning and Control System (AMDPCS) A

AMDPCS B Air and Missile Defense Planning and Control System (AMDPCS) B

ICE Integrated Collaborative Envronment (ICE)

ECT Engagement Control Trailer (ECT)

IFCN Integrated Fire Control Network (IFCN) Relay

B Kit Sentinel B-Side Kit

18. OPTIONAL REQUIREMENTS

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

d. SEQUENCING (X if applicable)

LRIP EOC X X

LRIP ADAM X X

LRIP AMDPCS A X X

LRIP AMDPCS B X X

LRIP ICE X X

LRIP ECT X X

LRIP IFCN X X

LRIP B Kit X X

W31P4Q-20-R-0015

Name Role Decision Date Signature

Burke, Rick CA Deputy Director Approved 12/18/2019 4:17:12 PM

Hazel, Kelly DCARC Director Approved 12/4/2019 4:56:30 PM

Tomick, John CAPE Analyst Approved 12/2/2019 3:34:13 PM

W31P4Q-20-R-0015