Attachment J-12 BLQ-10 EW TI-26 TI-28 TI-30_CSDR Plan.pdf

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

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

AN/BLQ-10 Electronic Warfare System

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

C-LRIP

X C-FRP

O&S

1c. PRIME MISSION PRODUCT

AN/BLQ-10 Electronic Warfare System

1d. ACQUISITION CATEGORY (ACAT) Pre-ACAT

ACAT I (MDAP)

ACAT IA (MAIS)

ACAT II

X ACAT III

Other

2. COMMODITY TYPE

Electronic System

3. PLAN ITERATION TYPE

X INITIAL

REVISION

4. CURRENT SUBMISSION DATE (YYYYMMDD)

20230517

5. LAST APPROVED PLAN DATE (YYYYMMDD)

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

Nguyen, Timothy H

6b. ADDRESS (Include ZIP Code)

6c. TELEPHONE NUMBER (Include Area Code)

401-832-9165

6d. E-MAIL ADDRESS timothy.h.nguyen.civ@us.navy.mil

7. PLAN TYPE

GOVERNMENT

X CONTRACT (PRIME)

CONTRACT (SUB)

8. PLAN GOVERNMENT PREPARING ORGANIZATION

PEO UWS PMS435

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 - (NSEA-23-G-C1)

9c. APPROPRIATION (check all that apply)

X RDT&E

X PROCUREMENT

O&M

FMS

WCF

OTHER

10a. APPROVED PLAN NUMBER

NSEA-23-G-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

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

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 AN/BLQ-10A TI-26, TI-28, and TI-30 X X

1.1 2 AN/BLQ-10A Prime Mission Product (PMP) X X

1.1.1 3 Hardware X X

1.1.1.1 4 Technology Insertion (TI) X X

1.1.1.1.1 5 TI-26 X X X

1.1.1.1.2 5 TI-28 X X X

1.1.1.1.3 5 TI-30 X X X

1.1.1.2 4 Virginia Class New Construction X X X

1.1.1.3. 4 Virginia Class Modernization X X X

1.1.1.4. 4 Los Angeles Class Modernization X X X

1.1.1.5. 4 Seawolf Class Modernization X X X

1.1.1.6 4 Columbia Class New Construction X X X

1.1.1.7 4 Columbia Class Modernation X X X

1.1.2. 3 Software X

1.1.2.1 4 Advanced Processing Build (APB) X

1.1.2.1.1 5 TI-26/APB-25 Production System X X X

1.1.2.1.2 5 TI-26/APB-27 Production System X X X

1.1.2.1.3 5 TI-28/APB-27 Production System X X X

1.1.2.1.4 5 TI-28/APB-29 Production System X X X

1.1.2.1.5 5 TI-30/APB-29 Production System X X X

1.1.2.1.6 5 TI-30/APB-31 Production System X X X

1.2. 2 Integration, Assembly, and Checkout X X

1.3. 2 Systems Engineering X X

1.4 2 Program Management X X

1.5 2 Systems Test & Evaluation X

1.5.1 3 Development Test & Evaluation X X

1.5.2 3 Operational Test & Evaluation X X

1.5.3 3 Test & Evaluation Support X X

1.5.4 3 Test Facilities X X

1.6 2 Training X

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 X

1.7.1 3 Technical Publications X X

1.7.2 3 Engineering Data X X

1.7.3 3 Management Data X X

1.7.4 3 Support Data X X

1.7.5 3 Data Depository X X

1.7.6 3 Data Rights X X

1.8 2 Peculiar Support Equipment (PSE) X

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 (CSE) X

1.9.1 3 Test and Measurement Equipment X X

1.9.2 3 Support and Handling Equipment X X

1.10. 2 Fleet Supports X X

1.11 2 Initial Spares & Repair Parts X

1.11.1 3 INCO X X

1.11.2 3 OBRPs X X

Subtotal Cost X X

Reporting Contractor G&A X X

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

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

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 10

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 (plus 12 months) Initial 20250630 20250830

2 Technical Data Report Contract Award (plus 12 months) Initial 20250630 20250830

3 SRDR Development Contract Award (plus 12 months) Initial 20250630 20250830

4 Cost and Hour Report (FlexFile), Quantity Data Report Annual Report 1 Interim 20260630 20260830

5 Technical Data Report Annual Report 1 Interim 20260630 20260830

6 SRDR Development Annual Report 1 Interim 20260630 20260830

7 Cost and Hour Report (FlexFile), Quantity Data Report Annual Report 2 Interim 20270630 20270830

8 Technical Data Report Annual Report 2 Interim 20270630 20270830

9 SRDR Development Annual Report 2 Interim 20270630 20270830

10 Cost and Hour Report (FlexFile), Quantity Data Report Annual Report 3 Interim 20280630 20280830

11 Technical Data Report Annual Report 3 Interim 20280630 20280830

12 SRDR Development Annual Report 3 Interim 20280630 20280830

13 Cost and Hour Report (FlexFile), Quantity Data Report Annual Report 4 Interim 20290630 20290830

14 Technical Data Report Annual Report 4 Interim 20290630 20290830

15 SRDR Development Annual Report 4 Interim 20290630 20290830

16 Cost and Hour Report (FlexFile), Quantity Data Report Annual Report 5 Interim 20300630 20300830

17 Technical Data Report Annual Report 5 Interim 20300630 20300830

18 SRDR Development Annual Report 5 Interim 20300630 20300830

19 Cost and Hour Report (FlexFile), Quantity Data Report Annual Report 6 Interim 20310630 20310830

20 Technical Data Report Annual Report 6 Interim 20310630 20310830

21 SRDR Development Annual Report 6 Interim 20310630 20310830

22 Cost and Hour Report (FlexFile), Quantity Data Report Annual Report 7 Interim 20320630 20320830

23 Technical Data Report Annual Report 7 Interim 20320630 20320830

24 SRDR Development Annual Report 7 Interim 20320630 20320830

25 Cost and Hour Report (FlexFile), Quantity Data Report Annual Report 8 Interim 20330630 20330830

26 Technical Data Report Annual Report 8 Interim 20330630 20330830

27 SRDR Development Annual Report 8 Interim 20330630 20330830

28 Cost and Hour Report (FlexFile), Quantity Data Report Contract Completion (60 days from completion) Final 20340630 20340830

29 Technical Data Report Contract Completion (60 days from completion) Final 20340630 20340830

30 SRDR Development Contract Completion (60 days from completion) Final 20340630 20340830

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

15. REMARKS

Periodically, Orders may be placed and therefore Delivery Order # will be known at that time. The contractor must report costs on all CLINs associated with the AN/BLQ-10 TI26, TI28, and TI-30 contract including Over and Above, Long Lead Materials, Inter-Division or Inter-Company Work Orders (IWOs), Warranty, etc. Costs should not be omitted based on contract CLIN structure or definition.

INITIAL REPORT

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.

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.

COVID-19 Remarks:

"The Reporting Entity 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 Reporting Entity 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.

Additional Data Fields #1-#12 (FlexFile): If applicable, the Reporting Entity 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."

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.

NON-RECURRING/RECURRING DEFINITIONS

Recurring and Non-Recurring Costs required for all levels:

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

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.

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.

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

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.

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.

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.

SRDR DEVELOPMENT- RELEASES AND COMPUTER SOFTWARE CONFIGURATION ITEMS (CSCIs)

For Software Release and CSCI WBS Element Names identified in Item 11c. as Subcomponent Release 1..n or Subcomponent 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. See the SRDR Implementation Guide for more detail https://cade.osd.mil/policy/srdr

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.

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

CSDR READINESS REVIEW (CSDR-RR) also known as Post Award Conference (PAC)

The Reporting Entity shall attend and participate in a CSDR Readiness Review meeting (also known as the 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 (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, 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 standard functional categories in the FlexFile (functional data elements in the 1921 series) codes will be populated. The review shall include any reporting issue corrections and identify proposed changes to the approved CSDR Plan as necessary.

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.73 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.

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

INTRA-CONTRACT SCOPE REPORTING DEFINITION

16. ORDERS/LOTS

a. ID b. NAME c. PHASE/MILESTONE 1...n Delivery Order # (specifiy) C-FRP

17. END ITEMS

a. ID b. NAME TI26APB25 TI-26/APB-25 Production System

TI26APB27 TI-26/APB-27 Production System

TI28APB27 TI-28/APB-27 Production System

TI28APB29 TI-28/APB-29 Production System

TI30APB29 TI-30/APB-29 Production System

TI30APB31 TI-30/APB-31 Production System

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)

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

COST AND SOFTWARE DATA REPORTING PLAN - SRDR DEVELOPMENT

19. RELEASES

a. ID b. NAME c. DATE

1 APB-25 Release 20260930

2 APB-27 Release 20280930

3 APB-29 Release 20300930

4 APB-31 Release 20320930

20. CSCI'S

a. ID b. NAME

C1 TI-26/APB-25 Production System

C2 TI-26/APB-27 Production System

C3 TI-28/APB-27 Production System

C4 TI-28/APB-29 Production System

C5 TI-30/APB-29 Production System

C6 TI-30/APB-31 Production System

21. PRODUCT SIZE REPORTING ELEMENTS

a. CODE b. NAME c. RELEASE ID d. CSCI ID

1.1.2.1.1 TI-26/APB-25 Production System 1 C1

1.1.2.1.2 TI-26/APB-27 Production System 2 C2

1.1.2.1.3 TI-28/APB-27 Production System 2 C3

1.1.2.1.4 TI-28/APB-29 Production System 3 C4

1.1.2.1.5 TI-30/APB-29 Production System 3 C5

1.1.2.1.6 TI-30/APB-31 Production System 4 C6

22. PRODUCT SIZE SUBMISSIONS c. RELEASE ID: 1 2 3 4

a. NUMBER b. NAME Included? Included? Included? Included?

3 Contract Award (plus 12 months) X

6 Annual Report 1 X

9 Annual Report 2 X X

12 Annual Report 3 X X

15 Annual Report 4 X X

18 Annual Report 5 X X

21 Annual Report 6 X X

24 Annual Report 7 X X

27 Annual Report 8 X

30 Contract Completion (60 days from completion) X

26. WBS ELEMEN

a. PARAMETER NAME b. UNIT OF

MEASURE

c. UNIT OF MEASURE QUALIFIER d. REPEATABLE e. REMARKS

1.1.1.2 Virginia Class New Construction PhysicalElec Power - Maximum Consumption Rate Kilowatts

1.1.1.3. Virginia Class Modernization PhysicalElec Power - Maximum Consumption Rate Kilowatts

1.1.1.4. Los Angeles Class Modernization PhysicalElec Power - Maximum Consumption Rate Kilowatts

1.1.1.5. Seawolf Class Modernization PhysicalElec Power - Maximum Consumption Rate Kilowatts

1.1.1.6 Columbia Class New Construction PhysicalElec Power - Maximum Consumption Rate Kilowatts

1.1.1.7 Columbia Class Modernation PhysicalElec Power - Maximum Consumption Rate Kilowatts

1.2 Integration, Assembly, and Checkout IAT&CO Number of Interface Control Drawings (ICD) Quantity Drawings

1.3 Systems Engineering SysEng Number of Requirement Document - "Shalls" Quantity Shalls

1.3 Systems Engineering SysEng Number of Platforms - Integrated Quantity Platforms

1.4 Program Management ProgMgmt Frequency of Government Program Reviews Quantity Reviews per Year

1.4 Program Management ProgMgmt Number of Contract Line Item Number (CLIN Quantity CLINs

1.4 Program Management ProgMgmt Number of Subcontractors Quantity Subcontractors

1.4 Program Management ProgMgmt Number of CDRLs Quantity CDRLs

1.7 Data Data Data Rights Category List

1.8.1 Test and Measurement Equipment SupportEquipment Quantity of Support Equipment Quantity Support Equipment

1.8.2 Support and Handling Equipment SupportEquipment Quantity of Support Equipment Quantity Support Equipment

1.9.1 Test and Measurement Equipment SupportEquipment Quantity of Support Equipment Quantity Support Equipment

1.9.2 Support and Handling Equipment SupportEquipment Quantity of Support Equipment Quantity Support Equipment

DD FORM 2794 (PAGE 8), TECHNICAL PARAMETER REQUIREMENTS, JANUARY 2019

COST AND SOFTWARE DATA REPORTING PLAN - TECHNICAL PARAMETER REQUIREMENTS

TECHNICAL PARAMETER REQUIREMENTS

27. WBS ELEMENT NAME 28. ITEM TYPE

29. TECHNICAL PARAMETER

Name Role Decision Date Signature

Carlton Lavinder SCC Director Approved 6/16/2023 10:40:10 AM

DD Form 2794, Pg 8 (TECH RQ (2