Attachment 18 - CSDR Plan_MIDS JTRS Lots 9-13_12 July 2019.pdf
PDF 203 KB Posted
- Solicitation number
- N00039-19-R-1000
About this file
This document is a Cost and Software Data Reporting (CSDR) Plan for the MIDS-JTRS Production Terminals Lots 9-13 contract. The plan outlines CSDR reporting requirements for the production of various MIDS JTRS terminal configurations including CMN-4, TTNT, and F-22 terminals from 2019 through 2027. Key reporting events include an initial report due by November 2029 with annual interim reports due through May 2030 and a final report due by May 2027. Reporting will utilize the FlexFile format and include costs, hours, quantities, and software data for the terminal configurations and associated shop replaceable units at the work breakdown structure levels identified in the plan.
View the file
Other files
Show all 26
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
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.
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
DRAFT DD FORM 2794, JANUARY 2019 PREVIOUS EDITION IS OBSOLETE Page 1 of 6
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
MIDS - Multi-Functional Information Distribution System (Includes Low Volume Terminal and JTRS)
1b. PHASE/MILESTONE (check all that apply) Pre-A A B
C-LRIP
X C-FRP
O&S
1c. PRIME MISSION PRODUCT
MIDS JTRS Production Terminals
1d. ACQUISITION CATEGORY (ACAT) Pre-ACAT
X ACAT I (MDAP)
ACAT IA (MAIS)
ACAT II
ACAT III
Other
2. COMMODITY TYPE
Electronic System
3. PLAN ITERATION TYPE
X INITIAL
REVISION
4. CURRENT SUBMISSION DATE (YYYYMMDD)
20190712
5. LAST APPROVED PLAN DATE (YYYYMMDD)
6a. GOVERNMENT PLAN POINT OF CONTACT (POC) NAME (Last, First, M.)
Adam Landrey
6b. ADDRESS (Include ZIP Code) 33050 Nixie Way Building 17ARoom 401F San Diego, CA 92147 6c. TELEPHONE NUMBER (Include Area Code)
619-524-5763
6d. E-MAIL ADDRESS adam.landrey@navy.mil
7. PLAN TYPE
GOVERNMENT
X CONTRACT (PRIME)
CONTRACT (SUB)
8. PLAN GOVERNMENT PREPARING ORGANIZATION
NAVAIR 4.2
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
N-12-M-C23
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 6
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 Multi-functional Information Distribution System (MIDS) Joint Tactical Radio System (JTRS) X X
1.1 2 MIDS JTRS Production Terminals Prime Mission Product (PMP) X X
1.1.1 3 Concurrent Multi-Netting-4 (CMN-4) Production Terminals X X
1.1.1.1 4 CMN-4 Receiver/Transmitter Line Replaceable Unit (LRU) X X
1.1.1.1.1 5 Red Input/Output Shop Replaceable Unit (SRU) X X X
1.1.1.1.2 5 Cryptographic Subsystem/Protected Core Processor SRU X X X
1.1.1.1.3 5 Internal Power Supply SRU X X X
1.1.1.1.4 5 2-2000 MHz Transceiver Blank-Off Plate SRU X X X
1.1.1.1.5 5 Link 16 Transceiver SRU X X X
1.1.1.1.6 5 Radio Frequency Amplifier SRU X X X
1.1.1.1.7 5 Chassis SRU X X X
1.1.1.1.8 5 TACAN/Black Core Processor SRU X X X
1.1.1.1.9 5 CMN-4 Warranty X X
1.1.1.1.10 5 Receiver/Transmitter LRU Software X
1.1.1.1.11 5 Receiver/Transmitter LRU Integration, Assembly, Test and Checkout X X
1.1.1.2 4 CMN-4 Power Supply LRU X X X
1.1.1.3 4 CMN-4 Production Terminals Software X
1.1.1.4 4 CMN-4 Production Terminals Integration, Assembly, Test and Checkout X X
1.1.2 3 Tactical Targeting Network Technology (TTNT) Production Terminals X X
1.1.2.1 4 TTNT Receiver/Transmitter LRU X X
1.1.2.1.1 5 Red Input/Output SRU X X X
1.1.2.1.2 5 Cryptographic Subsystem/Protected Core Processor SRU X X X
1.1.2.1.3 5 Internal Power Supply SRU X X X
1.1.2.1.4 5 2-2000 MHz Transceiver Blank-Off Plate SRU X X X
1.1.2.1.5 5 Link 16 Transceiver SRU X X X
1.1.2.1.6 5 TTNT Transceiver SRU X X X
1.1.2.1.7 5 Radio Frequency Amplifier SRU X X X
1.1.2.1.8 5 Chassis SRU X X X
1.1.2.1.9 5 TACAN/Black Core Processor SRU X X X
1.1.2.1.10 5 TTNT Warranty X X
1.1.2.1.11 5 TTNT Receiver/Transmitter LRU Software X
1.1.2.1.12 5 TTNT Receiver/Transmitter LRU Integration, Assembly, Test and Checkout X X
1.1.2.2 4 TTNT Power Supply LRU X X X
1.1.2.3 4 TTNT External Power Amplifier LRU X X X
1.1.2.4 4 TTNT High Power Amplifier LRU X X X
1.1.2.5 4 TTNT Production Terminals Software X
1.1.2.6 4 TTNT Production Terminals Integration, Assembly, Test and Checkout X X
1.1.3 3 F-22 CMN-4 Production Terminals X X
1.1.3.1 4 F-22 CMN-4 Receiver/Transmitter LRU X X
1.1.3.1.1 5 Red Input/Output SRU X X X
1.1.3.1.2 5 Cryptographic Subsystem/Protected Core Processor SRU X X X
1.1.3.1.3 5 Internal Power Supply SRU X X X
1.1.3.1.4 5 Link 16 Transceiver SRU X X X
1.1.3.1.5 5 F-22 IFF-T Transceiver SRU X X X
1.1.3.1.6 5 F-22 Back Panel SRU X X X
1.1.3.1.7 5 F-22 Chassis SRU X X X
1.1.3.1.8 5 TACAN/Black Core Processor SRU X X X
1.1.3.1.9 5 F-22 CMN-4 Warranty X X
1.1.3.1.10 5 F-22 Receiver/Transmitter LRU Software X
1.1.3.1.11 5 F-22 Receiver/Transmitter LRU Integration, Assembly, Test and Checkout X X
1.1.3.2 4 F-22 RRFU LRU X X X
1.1.3.3 4 F-22 CMN-4 Production Terminals Software X
1.1.3.4 4 F-22 CMN-4 Production Terminals Integration, Assembly, Test and Checkout X X
1.2 2 Platform Integration, Assembly, Test and Checkout X
DRAFT DD FORM 2794, JANUARY 2019 PREVIOUS EDITION IS OBSOLETE Page 3 of 6
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.3 2 System Engineering X
1.3.1 3 Software Systems Engineering 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.4 2 Program Management X
1.4.1 3 Software Program Management X
1.4.2 3 Integrated Logistics Support (ILS) Program Management X X
1.4.3 3 Cybersecurity Program Management X X
1.4.4 3 Core Program Management X X
1.5 2 System Test and Evaluation X X
1.6 2 Training X
1.7 2 Data X
1.7.1 3 Data Deliverables X X
1.7.2 3 Data Repository X X
1.7.3 3 Data Rights X X
1.8 2 Peculiar Support Equipment X
1.9 2 Common Support Equipment X
1.10 2 Operational/Site Activation X
1.11 2 Industrial Facilities X
1.12 2 Initial Spares and Repair Parts X X
1.12.1 3 Red Input/Output SRU X X X
1.12.2 3 Cryptographic Subsystem/Protected Core Processor SRU X X X
1.12.3 3 Internal Power Supply SRU X X X
1.12.4 3 2-2000 MHz Transceiver Blank-Off Plate SRU X X X
1.12.5 3 Link 16 Transceiver SRU X X X
1.12.6 3 Radio Frequency Amplifier SRU X X X
1.12.7 3 Chassis SRU X X X
1.12.8 3 TACAN/Black Core Processor SRU X X X
1.12.9 3 TTNT Transceiver SRU X X X
1.12.10 3 F-22 IFF-T Transceiver SRU X X X
1.12.11 3 F-22 Back Panel SRU X X X
1.12.12 3 F-22 Chassis SRU X X X
1.12.13 3 Power Supply LRU X X X
1.12.14 3 TTNT External Power Amplifier LRU X X X
1.12.15 3 TTNT High Power Amplifier LRU X X X
1.12.16 3 F-22 Remote Radio Frequency Unit LRU X X X
1.12.17 3 Warranty 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 6
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 MIDS JTRS Lots 9-13 - Initial Report Initial 20200930 20201129
2 Cost and Hour Report (FlexFile), Quantity Data Report MIDS JTRS Lots 9-13 - Annual Report #1 Interim 20210331 20210530
3 Cost and Hour Report (FlexFile), Quantity Data Report MIDS JTRS Lots 9-13 - Annual Report #2 Interim 20220331 20220530
4 Cost and Hour Report (FlexFile), Quantity Data Report MIDS JTRS Lots 9-13 - Annual Report #3 Interim 20230331 20230530
5 Cost and Hour Report (FlexFile), Quantity Data Report MIDS JTRS Lots 9-13 - Annual Report #4 Interim 20240331 20240530
6 Cost and Hour Report (FlexFile), Quantity Data Report MIDS JTRS Lots 9-13 - Annual Report #5 Interim 20250331 20250530
7 Cost and Hour Report (FlexFile), Quantity Data Report MIDS JTRS Lots 9-13 - Annual Report #6 Interim 20260331 20260530
8 Cost and Hour Report (FlexFile), Quantity Data Report MIDS JTRS Lots 9-13 - Final Report Final 20270331 20270530
DRAFT DD FORM 2794, JANUARY 2019 PREVIOUS EDITION IS OBSOLETE Page 5 of 6
15. REMARKS
The contractor must report costs on all CLINs associated with the MIDS JTRS Production Terminals Lots 9-13 contract including Over and Above, Advance Procurement, Long Lead Materials, Multiyear Procurement, Inter-Division or Inter-Company Work Orders (IWOs), Foreign Military Sales (FMS), Warranty, etc. Costs should not be omitted based on contract CLIN structure or definition.
1. Describe significant accounting changes from previous accounting period, if applicable.
2. DD Form 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.
3. 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.
4. NON-RECURRING/RECURRING DEFINITIONS: The contractor will utilize the specific definitions and requirements in the CSDR Manual (DoD 5000.04-M-1), the latest FlexFile Implementation Guide and the definitions in the DIDs for the FlexFile to segregate Recurring and Nonrecurring costs discretely and not as an aggregate.
5. QUANTITY: 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.
6. 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.
7. 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.
DRAFT DD FORM 2794, JANUARY 2019 PREVIOUS EDITION IS OBSOLETE Page 6 of 6
INTRA-CONTRACT SCOPE REPORTING DEFINITION
16. ORDERS/LOTS
a. ID b. NAME c. PHASE/MILESTONE L9 Production Lot 9 C-FRP
L9A Production Lot 9 A C-FRP
L10 Production Lot 10 C-FRP
L10A Production Lot 10 A C-FRP
L11 Production Lot 11 C-FRP
L11A Production Lot 11 A C-FRP
L12 Production Lot 12 C-FRP
L12A Production Lot 12 A C-FRP
L13 Production Lot 13 C-FRP
L13A ProductionLot 13 A C-FRP
17. END ITEMS
a. ID b. NAME CMN4 Concurrent Multi-Netting-4 (CMN-4) Production Terminals
TTNT Tactical Targeting Network Technology (TTNT) Production Terminals
F22CMN4 F-22 CMN-4 Production Terminals
18. OPTIONAL REQUIREMENTS
a. ORDER/LOT ID b. END ITEM ID c. UNIT REPORTING (X if applicable)
d. SEQUENCING (X if applicable)
Name Role Decision Date Signature
Rick Burke CA Deputy Director Approved 8/2/2019 8:40:06 AM
Kelly Hazel DCARC Director Approved 8/1/2019 12:55:37 PM
File details come from the government source that posted it. Updated .