Attachment 11 - CTSO INC 1 CDSR Memo.pdf

DEPARTMENT OF THE ARMY

OFFICE OF THE ASSISTANT SECRETARY OF THE ARMY

FINANCIAL MANAGEMENT AND COMPTROLLER

109 ARMY PENTAGON

WASHINGTON DC 20310-0109

09/23/2021

SAFM-CE

MEMORANDUM FOR JOINT PROGRAM EXECUTIVE OFFICE ARMAMENTS &

AMMUNITION (JPEO A&A)

SUBJECT: Close Terrain Shaping Obstacle (CTSO) CAVM Based Top Attack (TA) System Cost and Software Data Report (CSDR) (DD Form 2794)

1. Please note the following instructions are for the subject program referenced above:

a. The CSDR Manual, DoDM 5000.04-M-1, governs the application of CSDR requirements.

The most recently approved Data Item Descriptions (DIDs) for CCDRs, CWBS Dictionaries, SRDRs, FlexFiles, Technical Data Reports and Maintenance and Repair Reports must be used for this contract. The dollar thresholds governing the application of CSDRs at the program level is provided for in Title 10 Section 2334(g), as updated by the National Defense Authorization Act (NDAA) Fiscal Year (FY) 2017. CSDR Reporting must be consistent with the requirements in the DoDI 5000.73, Cost Analysis Guidance and Procedures. The most recently approved versions of these documents must be used for this contract.

b. The attached Deputy Assistant Secretary of the Army (Cost and Economics)-approved Contract CSDR Plan documents the WBS reporting elements, submission events, report types and any other additional tags required. The Deputy Assistant Secretary of the Army (Cost and Economics)-approved Contract CSDR Plan must be included in the Request For Proposal (RFP) due to the CSDR reporting requirements. Any proposed changes to the attached approved Contract CSDR Plan must be submitted to Deputy Assistant Secretary of the Army (Cost and Economics) for approval. Changes to the Contract CSDR Plan must be approved by Deputy Assistant Secretary of the Army (Cost and Economics) prior to the finalization of all contract actions associated with this CSDR requirement. A post-award conference must be held with the contractor to ensure an understanding of the requirements, discuss the contractor’s plan for providing the data including any mapping or allocation methods expected to be used, and to form agreement to any minor updates and adjustments based on conclusions drawn from discussions.

c. The Contract CSDR process uses the event field as the driver for each submission, not the "as of date.” The "as of date" is based on current knowledge and is used for tracking purposes. If the event slips, it is the responsibility of the Program Office /Lead Service Analyst (PO/LSA) to update the tracking system with the new event date via the CSDR Submit-Review. The PO/LSA will determine if a revised Contract CSDR Plan is required. If the Contractor does not inform the PO, the submission will be treated as being late.

SAFM-CE

SUBJECT: Close Terrain Shaping Obstacle (CTSO) CAVM Based Top Attack (TA) System Cost and Software Data Report (CSDR) (DD Form 2794)

2. Any questions relating to the subject CSDR Plan should be directed to Jenna Meyers (jenna.e.meyers.civ@mail.mil).

Jenna Meyers Technical Advisor

Deputy Assistant Secretary of the Army (Cost and Economics)

Attachments:

CSDR Plan: A-21-N-C1

OMB No. 0704-0188

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

X B

C-LRIP

C-FRP

O&S

1d. ACQUISITION CATEGORY (ACAT) Pre-ACAT

ACAT I (MDAP)

ACAT IA (MAIS)

ACAT II

ACAT III

X Other

3. PLAN ITERATION TYPE

X INITIAL

REVISION

7. PLAN TYPE

GOVERNMENT

X CONTRACT (PRIME)

CONTRACT (SUB)

X CBDR REQUIRED FOR THIS ORGANIZATION

9c. APPROPRIATION (check all that apply)

X RDT&E

PROCUREMENT

O&M

FMS

WCF

OTHER

X AT COMPLETION COSTS FOR STANDARD FUNCTIONAL CATEGORIES (FlexFile or Legacy) X AT COMPLETION COSTS FOR RECURRING/NONRECURRING (FlexFile only)

X TECHNICAL DATA REQUIRED

X FLEXFILE

LEGACY DD 1921 SERIES

DRAFT DD FORM 2794 (PAGE 1), METADATA, JANUARY 2019 PREVIOUS EDITION IS OBSOLETE

5. LAST APPROVED PLAN DATE (YYYYMMDD)

4. CURRENT SUBMISSION DATE (YYYYMMDD)

COST AND SOFTWARE DATA REPORTING PLAN

CAVM Based Top Attack (TA) System

2. COMMODITY TYPE

1c. PRIME MISSION PRODUCT

Close Terrain Shaping Obstacle (CTSO) Increment 1 CAVM Based Top Attack (TA) System

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

Missile System

20210804

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

i. REPORTING ORGANIZATION NAME

ii. DIVISION NAME

iii. LOCATION

9a. CONTRACTOR NAME/ADDRESS

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

Gulla, Nicole, E

6c. TELEPHONE NUMBER (Include Area Code)

6b. ADDRESS (Include ZIP Code)

10d. COST REPORT TYPE

183 Buffington Road Picatinny Arsenal, NJ 07806

10c. APPROVED PLAN REQUIREMENTS

10b. APPROVED PLAN REVISION NUMBER

TBD

6d. E-MAIL ADDRESS nicole.e.gulla.civ@mail.mil

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

TBD

A-21-N-C1

10a. APPROVED PLAN NUMBER

973-724-4194

8. PLAN GOVERNMENT PREPARING ORGANIZATION

OFFICE OF THE PROJECT MANAGER, CLOSE COMBAT SYSTEMS

mailto:nicole.e.gulla.civ@mail.mil#

i. QUANTITY

DATA

ii. GFE

QUANTITY

1.0 1 CAVM Based Top Attack (TA) System / Area Denial Capability Development X

1.1 2 Missile/Ordnance System Integration, Assembly, Test, and Checkout X X

1.2 2 Air Vehicle/Munition

1.2.1 3 Air Vehicle/Munition Integration, Assembly, Test, and Checkout X X

1.2.2 3 Airframe X X

1.2.3 3 Propulsion Subsystem 1...n (Specify) X X

1.2.4 3 Power and Distribution X X

1.2.5 3 Guidance X X

1.2.6 3 Navigation X X

1.2.7 3 Controls X X

1.2.8 3 Communications X X

1.2.9 3 Payload

1.2.9.1 4 Payload Common to All Variants (Munition)

1.2.9.1.1 5 Top Attack Munition X

1.2.9.1.1.1 6 Top Attack Munition IATC X X

1.2.9.1.1.2 6 Top Attack Munition Hardware X

1.2.9.1.1.2.1 7 Top Attack Munition Structure X X X

1.2.9.1.1.2.2 7 Top Attack Munition Power X X X

1.2.9.1.1.2.3 7 Top Attack Munition Sensor X

1.2.9.1.1.2.3.1 8 Targeting X X X

1.2.9.1.1.2.3.2 8 Orientation/Positioning X X X

1.2.9.1.1.2.4 7 Top Attack Munition External Interface X X X

1.2.9.1.1.2.5 7 Top Attack Munition Internal Interface X X X

1.2.9.1.1.3 6 Top Attack Munition Software

1.2.9.1.1.3.1 7 Top Attack Munition Software Release 1…n (Contractor Specfiy) X

1.2.9.1.1.3.1.1 8 Top Attack Munition Software CSCI 1…n (Contractor Specify) X X X

1.2.9.2 4 DPICM Payload Unique X X

1.2.9.3 4 Unitary Payload Unique X X

1.2.9.4 4 AT Payload Unique X X

1.2.9.5 4 Payload Software X X

1.2.10 3 On Board Test Equipment X X

1.2.11 3 On Board Training Equipment X X

1.2.12 3 Auxiliary Equipment X X

1.2.13 3 Air Vehicle Software X X

1.3 2 Encasement Device (Dispenser Launcher Munition (DLM))

1.3.1 3 Top Attack DLM X

1.3.1.1 4 Top Attack DLM IATC X X

1.3.1.2 4 Top Attack DLM Hardware X

1.3.1.2.1 5 Top Attack DLM Structure X X X

1.3.1.2.2 5 Top Attack DLM Power X X X

1.3.1.2.3 5 Top Attack DLM Sensor X

1.3.1.2.3.1 6 Top Attack DLM Tracking/Detecting X X X

1.3.1.2.3.2 6 Top Attack DLM Engagement X X X

1.3.1.2.3.3 6 Top Attack DLM Anti-Handling X X X

1.3.1.2.3.4 6 Top Attack DLM Geo-Location X X X

1.3.1.2.4 5 Top Attack DLM External Interface X

1.3.1.2.4.1 6 Top Attack DLM SAVO Output X X X

1.3.1.2.4.2 6 Top Attack DLM Manual Arming X X X

1.3.1.2.4.3 6 Top Attack DLM Blasting Initiation X X X

1.3.1.2.4.4 6 Top Attack DLM RCS Initiation X X X

1.3.1.2.4.5 6 Top Attack DLM Other X X X

1.3.1.2.5 5 Top Attack DLM Internal Interface X X X

1.3.1.3 4 Top Attack DLM Software

1.3.1.3.1 5 Top Attack DLM Software Release 1…n (Contractor Specify) X

1.3.1.3.1.1 6 Top Attack DLM Software CSCI 1…n (Contractor Specify) X X X

1.3.3 3 Encasement Device Software X X

1.3.4 3 Other Encasement Device Subsystems 1...n (Specify) X X

1.4 2 Command and/or Launch

1.4.1 3 Command and/or Launch Integration, Assembly, Test, and Checkout X X

1.4.2 3 Surveillance, Identification and Tracking Sensors X X

1.4.3 3 Communications X X

1.4.4 3 Launcher X X

1.4.5 3 Adapter Kits X X

1.4.6 3 Launch and Guidance Control X X

1.4.7 3 Ready Magazine X X

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

COST AND SOFTWARE DATA REPORTING PLAN

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

a. WBS

CODE

1.4.8 3 Auxiliary Equipment X X

1.4.1 3 Remote Control Station (RCS) X X

1.4.1.1 4 RCS IATC X X

1.4.1.2 4 RCS Hardware X X X

1.4.1.3 4 RCS Software

1.4.1.3.1 5 RCS Software Release 1…n (Contractor Specify) X

1.4.1.3.1.1 6 RCS Software CSCI 1…n (Contractor Specify) X X X

1.4.2 3 Planning Tool (Laptop) X X

1.4.2.1 4 Planning Tool IATC X X

1.4.2.2 4 Planning Tool Hardware X X X

1.4.2.3 4 Planning Software

1.4.2.3.1 5 Planning Tool Software Release 1…n (Contractor Specify) X

1.4.2.3.1.1 6 Planning Tool Software CSCI 1…n (Contractor Specify) X X X

1.4.3 3 Authoritative Safety Device (ASD) X

1.4.3.1 4 ASD IATC X X

1.4.3.2 4 ASD Hardware X X X

1.4.3.3 4 ASD Software

1.4.3.3.1 5 ASD Software Release 1…n (Contractor Specify) X

1.4.3.3.1.1 6 ASD Software CSCI 1…n (Contractor Specify) X X X

1.4.4 3 RCS Full Network Capability (INC 3) Software

1.4.4.1 4 RCS Full Network Capability Software Release 1…n (Contractor Specify) X

1.4.4.1.1 5 RCS Full Network Capability Software CSCI 1 …n (Contractor Specify) X X X

1.4.5 3 Planning Tool Full Network Capability (INC 3) Software

1.4.5.1 4 Planning Tool Full Network Capability Software Release 1…n (Contractor Specify X

1.4.5.1.1 5 Planning Tool Full Network Capability Software CSCI 1 …n (Contractor Spec X X X

1.4.6 3 ASD Full Network Capability (INC 3) Software

1.4.6.1 4 ASD Full Network Capability Software Release 1…n (Contractor Specify) X

1.4.6.1.1 5 ASD Full Network Capability Software CSCI 1 …n (Contractor Specify) X X X

1.5 2 Missile/Ordnance System Software Release X X

1.6 2 Platform Integration, Assembly, Test, and Checkout 1...n (Specify) X X

1.7 2 Systems Engineering

1.7.1 3 Software Systems Engineering X X X

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

1.7.3 3 Cybersecurity Systems Engineering X X

1.7.4 3 Core Systems Engineering X X

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

1.8 2 Program Management

1.8.1 3 Software Program Management X X X

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

1.8.3 3 Cybersecurity Management X X

1.8.4 3 Core Program Management X X

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

1.9 2 System Test and Evaluation

1.9.1 3 Development Test and Evaluation X X

1.9.2 3 Operational Test and Evaluation X X

1.9.3 3 Live Fire Test and Evaluation X X

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

1.9.5 3 Test and Evaluation Support X X

1.9.6 3 Test Facilities X X

1.10 2 Training

1.10.1 3 Equipment X X X

1.10.2 3 Services

1.10.2.1 4 Operator Instructional Services X X

1.10.2.2 4 Maintainer Instructional Services X X

1.10.3 3 Facilities X X

1.10.4 3 Training Software Release 1...n (Specify) X

1.10.4.1 4 Training Software CSCI 1...n (Contractor Specify) X X X

1.11 2 Data

1.11.1 3 Data Deliverables 1...n (Specify) X X

1.11.2 3 Data Repository X X

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

1.12 2 Peculiar Support Equipment

1.12.1 3 Test and Measurement Equipment X X X

1.12.2 3 Support and Handling Equipment X X X

1.13 2 Common Support Equipment

1.13.1 3 Test and Measurement Equipment X X X

1.13.2 3 Support and Handling Equipment X X X

1.14 2 Operational/Site Activation by Site 1...n (Specify) X X

1.15 2 Contractor Logistics Support (CLS) X X

1.16 2 Industrial Facilities X X

1.17 2 Initial Spares and Repair Parts X 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 (PAGE 2), REPORTING, JANUARY 2019

e. AS OF DATE f. DUE DATE

(YYYYMMDD) (YYYYMMDD)

1 Cost and Hour Report (FlexFile), Quantity Data Report Contract Award Initial 20220125 20220326 2 Technical Data Report Contract Award Initial 20220125 20220326 3 SRDR Development Contract Award Initial 20220125 20220326 4 Cost and Hour Report (FlexFile), Quantity Data Report Annual Report 1 Interim 20230125 20230326 5 Technical Data Report Annual Report 1 Interim 20230125 20230326 6 SRDR Development Annual Report 1 Interim 20230125 20230326 7 Cost and Hour Report (FlexFile), Quantity Data Report Annual Report 2 Interim 20240125 20240325 8 Technical Data Report Annual Report 2 Interim 20240125 20240325 9 SRDR Development Annual Report 2 Interim 20240125 20240325 10 Cost and Hour Report (FlexFile), Quantity Data Report Annual Report 3 Interim 20250125 20250326 11 Technical Data Report Annual Report 3 Interim 20250125 20250326 12 SRDR Development Annual Report 3 Interim 20250125 20250326 13 Cost and Hour Report (FlexFile), Quantity Data Report Annual Report 4 Interim 20260125 20260326 14 Technical Data Report Annual Report 4 Interim 20260125 20260326 15 SRDR Development Annual Report 4 Interim 20260125 20260326 16 Cost and Hour Report (FlexFile), Quantity Data Report Contract Completion Final 20270125 20270326 17 Technical Data Report Contract Completion Final 20270125 20270326 18 SRDR Development Contract Completion Final 20270125 20270326

DRAFT DD FORM 2794 (PAGE 3), SUBMISSION EVENTS, JANUARY 2019 PREVIOUS EDITION IS OBSOLETE

COST AND SOFTWARE DATA REPORTING PLAN

14. CSDR SUBMISSION EVENTS

a.

EVENT ID

b.

DATA REPORT(S)

c.

SUBMISSION EVENT NAME

d.

REPORT CYCLE

COST AND SOFTWARE DATA REPORTING PLAN

15. REMARKS

The contractor must report costs on all CLINs associated with the (Insert contract name) 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.

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.

i. Submission events marked "Initial" shall report the Contractor'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 Contractor'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 Contractor'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 Contractor'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.

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:

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.

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.

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 shall be reported against WBS with associated costs and hours attributed to the lowest level children WBS elements found beneath it.

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.

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 (PAGE 4), REMARKS, JANUARY 2019 PREVIOUS EDITION IS OBSOLETE

a. ID c. PHASE/MILESTONE 1 B 2 B 3 B

a. ID A B C D

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

d. SEQUENCING (X if applicable)

DRAFT DD FORM 2794 (PAGE 5), INTRA-CONTRACT SCOPE, JANUARY 2019

COST AND SOFTWARE DATA REPORTING PLAN

INTRA-CONTRACT SCOPE REPORTING DEFINITION

16. ORDERS/LOTS

b. NAME Base Year Option Year 1

18. OPTIONAL REQUIREMENTS

Option Year 2…n

17. END ITEMS

b. NAME CAVM Based Top Attack (TA) System Full Task Trainer Exportable TA Common

a. ID b. NAME c. DATE 1 Top Attack Munition Software Release 1…n (Contractor Specfiy) TBD 2 Top Attack DLM Software Release 1…n (Contractor Specify) TBD 3 RCS Software Release 1…n (Contractor Specify) TBD 4 Planning Tool Software Release 1…n (Contractor Specify) TBD 5 ASD Software Release 1…n (Contractor Specify) TBD 6 RCS Full Network Capability Software Release 1…n (Contractor Specify) TBD 7 Planning Tool Full Network Capability Software Release 1…n (Contractor Specify) TBD 8 ASD Full Network Capability Software Release 1…n (Contractor Specify) TBD 9 Training Software Release 1...n (Specify) TBD

a. ID b. NAME C1 Top Attack Munition Software CSCI 1…n (Contractor Specify) C2 Top Attack DLM Software CSCI 1…n (Contractor Specify) C3 RCS Software CSCI 1…n (Contractor Specify) C4 Planning Tool Software CSCI 1…n (Contractor Specify) C5 ASD Software CSCI 1…n (Contractor Specify) C6 RCS Full Network Capability Software CSCI 1 …n (Contractor Specify) C7 Planning Tool Full Network Capability Software CSCI 1 …n (Contractor Specify) C8 ASD Full Network Capability Software CSCI 1 …n (Contractor Specify) C9 Training Software CSCI 1...n (Contractor Specify)

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

1.2.9.1.1.3.1.1 Top Attack Munition Software CSCI 1…n (Contractor Specify) 1 C1

1.3.1.3.1.1 Top Attack DLM Software CSCI 1…n (Contractor Specify) 2 C2

1.4.1.3.1.1 RCS Software CSCI 1…n (Contractor Specify) 3 C3

1.4.2.3.1.1 Planning Tool Software CSCI 1…n (Contractor Specify) 4 C4

1.4.3.3.1.1 ASD Software CSCI 1…n (Contractor Specify) 5 C5

1.4.4.1.1 RCS Full Network Capability Software CSCI 1 …n (Contractor Specify) 6 C6

1.4.5.1.1 Planning Tool Full Network Capability Software CSCI 1 …n (Contractor Specify) 7 C7

1.4.6.1.1 ASD Full Network Capability Software CSCI 1 …n (Contractor Specify) 8 C8

1.10.4.1 Training Software CSCI 1...n (Contractor Specify) 9 C9

1 2 3 4 5 6 7 8 9

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

3 Contract Award X X X X X X X X X 6 Annual Report 1 X X X X X X X X X 9 Annual Report 2 X X X X X X X X X

12 Annual Report 3 X X X X X X X X X 15 Annual Report 4 X X X X X X X X X 18 Contract Completion X X X X X X X X X

DRAFT DD FORM 2794 (PAGE 6), SRDR DEVELOPMENT, JANUARY 2019

COST AND SOFTWARE DATA REPORTING PLAN - SRDR DEVELOPMENT

19. RELEASES

20. CSCI'S

21. PRODUCT SIZE REPORTING ELEMENTS

22. PRODUCT SIZE SUBMISSIONS c. RELEASE ID:

26. WBS ELEMENT

1.2.9 Payload

1.2.9 Payload

1.2.9 Payload

1.2.9 Payload

1.2.9 Payload

1.2.9.1 Payload Common to All Variants

1.2.9.1 Payload Common to All Variants

1.2.9.1 Payload Common to All Variants

1.2.9.1 Payload Common to All Variants

1.2.9.1 Payload Common to All Variants

1.2.9.1 Payload Common to All Variants

1.3 Encasement Device

1.3 Encasement Device

1.3 Encasement Device

1.3 Encasement Device

1.3 Encasement Device

1.3 Encasement Device

1.3.1 Top Attack DLM

1.3.1 Top Attack DLM

1.3.1 Top Attack DLM

1.4 Command and/or Launch

1.4 Command and/or Launch

1.4.1 Command and/or Launch Integration, Assembly, Test, and Checkout

1.4.1 Command and/or Launch Integration, Assembly, Test, and Checkout

1.4.1 Command and/or Launch Integration, Assembly, Test, and Checkout

1.4.11 Authoritative Safety Device (ASD)

1.4.11 Authoritative Safety Device (ASD)

1.4.11 Authoritative Safety Device (ASD)

1.4.11 Authoritative Safety Device (ASD)

1.4.11 Authoritative Safety Device (ASD)

1.4.11 Authoritative Safety Device (ASD)

1.4.11 Authoritative Safety Device (ASD)

1.4.11 Authoritative Safety Device (ASD)

1.6 Platform Integration, Assembly, Test, and Checkout 1...n (Specify)

1.6 Platform Integration, Assembly, Test, and Checkout 1...n (Specify)

1.6 Platform Integration, Assembly, Test, and Checkout 1...n (Specify)

1.7 Systems Engineering

1.7 Systems Engineering

1.8 Program Management

1.8 Program Management

1.8 Program Management

27. WBS ELEMENT NAME

1.9.4 Mock-ups/System Integration Labs (SILs)

1.9.4 Mock-ups/System Integration Labs (SILs)

1.9.4 Mock-ups/System Integration Labs (SILs)

1.9.5 Test and Evaluation Support

1.9.6 Test Facilities

1.9.6 Test Facilities

1.9.6 Test Facilities

1.10.1 Equipment

1.10.1 Equipment

1.10.1 Equipment

1.10.3 Facilities

1.10.3 Facilities

1.10.3 Facilities

1.11.1 Data Deliverables 1...n (Specify)

1.11.2 Data Repository

1.11.3 Data Rights 1...n (Specify)

1.12.1 Test and Measurement Equipment

1.12.1 Test and Measurement Equipment

1.12.1 Test and Measurement Equipment

1.12.1 Test and Measurement Equipment

1.12.1 Test and Measurement Equipment

1.12.2 Support and Handling Equipment

1.12.2 Support and Handling Equipment

1.12.2 Support and Handling Equipment

1.12.2 Support and Handling Equipment

1.12.2 Support and Handling Equipment

1.13.1 Test and Measurement Equipment

1.13.1 Test and Measurement Equipment

1.13.1 Test and Measurement Equipment

1.13.1 Test and Measurement Equipment

1.13.1 Test and Measurement Equipment

1.13.2 Support and Handling Equipment

1.13.2 Support and Handling Equipment

1.13.2 Support and Handling Equipment

1.13.2 Support and Handling Equipment

1.13.2 Support and Handling Equipment

1.14 Operational/Site Activation by Site 1...n (Specify)

1.14 Operational/Site Activation by Site 1...n (Specify)

1.14 Operational/Site Activation by Site 1...n (Specify)

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

a. PARAMETER NAME Heritage New Design Heritage Predecessor System Warhead Insensitive Munitions Requirements Warhead Weight - Explosive Warhead Warhead Penetration PhysicalOther Material Mix 1…n PhysicalStruc Volume PhysicalStruc Weight Warhead Insensitive Munitions Requirements Warhead Weight - Explosive Warhead Warhead Penetration Heritage New Design Heritage Predecessor System PhysicalOther Material Mix 1…n PhysicalStruc Volume PhysicalStruc Weight Cannister Thickness - Canister PhysicalOther Material Mix 1…n PhysicalStruc Volume PhysicalStruc Weight Heritage New Design Heritage Predecessor System IAT&CO Number of Electrical Connections IAT&CO Number of Mechanical Connections IAT&CO Number of Interface Control Drawings (ICD) Heritage New Design Heritage Predecessor System PhysicalOther Material Mix 1…n PhysicalElec Volume PhysicalElec Weight PhysicalElec Weight - Structural PhysicalElec Weight - Electronics PhysicalElec Power - Maximum Consumption Rate IAT&CO Number of Electrical Connections IAT&CO Number of Mechanical Connections IAT&CO Number of Interface Control Drawings (ICD) SysEng Number of Requirement Document - "Shalls" SysEng Number of Platforms - Integrated ProgMgmt Frequency of Government Program Reviews ProgMgmt Number of Contract Line Item Number (CLIN)s ProgMgmt Number of Subcontractors ProgMgmt Number of Customer Stakeholders

COST AND SOFTWARE DATA REPORTING PLAN - TECHNICAL PARAMETER REQ

TECHNICAL PARAMETER REQUIREMENTS

28. ITEM TYPE

ProgMgmt Number of CDRLs SIL Modeling Type SIL Mock-up / SIL - Size SIL Mock-up / SIL - Primary Purpose T&ESupport System Supply Packages ConstrConv Facility Name ConstrConv Facility Description ConstrConv New product alteration square footage TrainDevice Training Device Name TrainDevice Training Device Quantity TrainDevice Training Device Description ConstrConv Facility Name ConstrConv Facility Description ConstrConv New product alteration square footage Data Data Rights Category DataDepository Storage Footprint Data Data Rights Category SupportEquipment Quantity of Support Equipment SupportEquipment Number of Locations SupportEquipment Support Equipment Locations SupportEquipment Support and Handling Device Name SupportEquipment Support and Handling Device Description SupportEquipment Quantity of Support Equipment SupportEquipment Number of Locations SupportEquipment Support Equipment Locations SupportEquipment Support and Handling Device Name SupportEquipment Support and Handling Device Description SupportEquipment Quantity of Support Equipment SupportEquipment Number of Locations SupportEquipment Support Equipment Locations SupportEquipment Support and Handling Device Name SupportEquipment Support and Handling Device Description SupportEquipment Quantity of Support Equipment SupportEquipment Number of Locations SupportEquipment Support Equipment Locations SupportEquipment Support and Handling Device Name SupportEquipment Support and Handling Device Description OpSiteActivation Facility Description OpSiteActivation Organic Site Activation OpSiteActivation Amplifying Descriptive Text

b. UNIT OF MEASURE c. UNIT OF MEASURE QUALIFIER d.

REPEATABLE

Percent Descriptor List Pounds Inches Percent of Total Weight Material Name Y Cubic Inches Pounds List Pounds Inches Percent Descriptor Percent of Total Weight Material Name Y Cubic Inches Pounds Inches Percent of Total Weight Material Name Y Cubic Inches Pounds Percent Descriptor Quantity Electrical Connections Quantity Mechanical Connections Quantity Drawings Percent Descriptor Percent of Total Weight Material Name Y Cubic Inches Pounds Pounds Pounds Kilowatts Quantity Electrical Connections Quantity Mechanical Connections Quantity Drawings Quantity Shalls YG Quantity Platforms Quantity Reviews per Year Quantity CLINs Quantity Subcontractors Quantity Stakeholders

QUIREMENTS

29. TECHNICAL PARAMETER

Quantity CDRLs List YG Square Feet by Facility / Suite YG List YG Quantity Initial - Parts List and Count Descriptor Descriptor Feet Descriptor Training Device Name YG Quantity Devices YG Descriptor YG Descriptor Descriptor Feet List Square Feet Data storage size List Quantity Support Equipment Quantity Locations Descriptor Descriptor Support and Handling Device Name YG Descriptor Devices YG Quantity Support Equipment Quantity Locations Descriptor Descriptor Support and Handling Device Name YG Descriptor Devices YG Quantity Support Equipment Quantity Locations Descriptor Descriptor Support and Handling Device Name YG Descriptor Devices YG Quantity Support Equipment Quantity Locations Descriptor Descriptor Support and Handling Device Name YG Descriptor Devices YG Descriptor List Descriptor e.

REMARKS

COST AND SOFTWARE DATA REPORTING PL

TECHNICAL PARAMETER

26. WBS ELEMENT C 27. WBS ELEMENT NAME

1.2.9 Payload

1.2.9 Payload

1.2.9 Payload

1.2.9 Payload

1.2.9 Payload

1.2.9.1 Payload Common to All Variants

1.2.9.1 Payload Common to All Variants

1.2.9.1 Payload Common to All Variants

1.3 Encasement Device

1.3 Encasement Device

1.3 Encasement Device

1.3 Encasement Device

1.3 Encasement Device

1.3 Encasement Device

1.3.1 Top Attack DLM

1.3.1 Top Attack DLM

1.3.1 Top Attack DLM

1.4 Command and/or Launch

1.4 Command and/or Launch

1.4.1 Command and/or Launch Integration, Assembly, Test, and Checkout

1.4.1 Command and/or Launch Integration, Assembly, Test, and Checkout

1.4.1 Command and/or Launch Integration, Assembly, Test, and Checkout

1.4.11 Authoritative Safety Device (ASD)

1.4.11 Authoritative Safety Device (ASD)

1.4.11 Authoritative Safety Device (ASD)

1.4.11 Authoritative Safety Device (ASD)

1.4.11 Authoritative Safety Device (ASD)

1.4.11 Authoritative Safety Device (ASD)

1.4.11 Authoritative Safety Device (ASD)

1.4.11 Authoritative Safety Device (ASD)

1.6 Platform Integration, Assembly, Test, and Checkout 1...n (Specify)

1.6 Platform Integration, Assembly, Test, and Checkout 1...n (Specify)

1.6 Platform Integration, Assembly, Test, and Checkout 1...n (Specify)

1.7 Systems Engineering

1.7 Systems Engineering

1.8 Program Management

1.9.4 Mock-ups/System Integration Labs (SILs)

1.9.4 Mock-ups/System Integration Labs (SILs)

1.9.4 Mock-ups/System Integration Labs (SILs)

1.9.5 Test and Evaluation Support

1.9.6 Test Facilities

1.9.6 Test Facilities

1.9.6 Test Facilities

1.10.1 Equipment

1.10.1 Equipment

1.10.1 Equipment

1.10.3 Facilities

1.10.3 Facilities

1.10.3 Facilities

1.11.1 Data Deliverables 1...n (Specify)

1.11.2 Data Repository

1.11.3 Data Rights 1...n (Specify)

1.12.1 Test and Measurement Equipment

1.12.1 Test and Measurement Equipment

1.12.1 Test and Measurement Equipment

1.12.1 Test and Measurement Equipment

1.12.1 Test and Measurement Equipment

1.12.2 Support and Handling Equipment

1.12.2 Support and Handling Equipment

1.12.2 Support and Handling Equipment

1.12.2 Support and Handling Equipment

1.12.2 Support and Handling Equipment

1.13.1 Test and Measurement Equipment

1.13.1 Test and Measurement Equipment

1.13.1 Test and Measurement Equipment

1.13.1 Test and Measurement Equipment

1.13.1 Test and Measurement Equipment

1.13.2 Support and Handling Equipment

1.13.2 Support and Handling Equipment

1.13.2 Support and Handling Equipment

1.13.2 Support and Handling Equipment

1.13.2 Support and Handling Equipment

1.14 Operational/Site Activation by Site 1...n (Specify)

1.14 Operational/Site Activation by Site 1...n (Specify)

1.14 Operational/Site Activation by Site 1...n (Specify)

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

LAN - TECHNICAL PARAMETER REQUIREMENTS

REQUIREMENTS (Definitions)

29. TECHNICAL PARAMETER

a. PARAMETER NAME b. UNIT OF MEASURE

New Design Percent

Predecessor System Descriptor

Insensitive Munitions Requirements List

Weight - Explosive Pounds

Warhead Penetration Inches

Material Mix 1…n Percent of Total Weight

Volume Cubic Inches Weight Pounds

Insensitive Munitions Requirements List

Weight - Explosive Pounds

Warhead Penetration Inches

New Design Percent

Predecessor System Descriptor

Material Mix 1…n Percent of Total Weight

Volume Cubic Inches Weight Pounds Thickness - Canister Inches

Material Mix 1…n Percent of Total Weight

Volume Cubic Inches Weight Pounds

New Design Percent

Predecessor System Descriptor

Number of Electrical Connections Quantity

Number of Mechanical Connections Quantity

Number of Interface Control Drawings (ICD) Quantity

New Design Percent

Predecessor System Descriptor

Material Mix 1…n Percent of Total Weight

Volume Cubic Inches Weight Pounds Weight - Structural Pounds Weight - Electronics Pounds Power - Maximum Consumption Rate Kilowatts

Number of Electrical Connections Quantity

Number of Mechanical Connections Quantity

Number of Interface Control Drawings (ICD) Quantity

Number of Requirement Document - "Shalls" Quantity

Number of Platforms - Integrated Quantity

Frequency of Government Program Reviews Quantity

Number of Contract Line Item Number (CLIN)s Quantity

Number of Subcontractors Quantity

Number of Customer Stakeholders Quantity

Number of CDRLs Quantity

Modeling Type List Mock-up / SIL - Size Square Feet Mock-up / SIL - Primary Purpose List

System Supply Packages Quantity

Facility Name Descriptor

Facility Description Descriptor

New product alteration square footage Feet Training Device Name Descriptor

Training Device Quantity Quantity

Training Device Description Descriptor Facility Name Descriptor

Facility Description Descriptor

New product alteration square footage Feet Data Rights Category List Storage Footprint Square Feet Data Rights Category List Quantity of Support Equipment Quantity Number of Locations Quantity Support Equipment Locations Descriptor Support and Handling Device Name Descriptor Support and Handling Device Description Descriptor Quantity of Support Equipment Quantity Number of Locations Quantity Support Equipment Locations Descriptor Support and Handling Device Name Descriptor Support and Handling Device Description Descriptor

Quantity of Support Equipment Quantity Number of Locations Quantity Support Equipment Locations Descriptor Support and Handling Device Name Descriptor Support and Handling Device Description Descriptor Quantity of Support Equipment Quantity Number of Locations Quantity Support Equipment Locations Descriptor Support and Handling Device Name Descriptor Support and Handling Device Description Descriptor

Facility Description Descriptor

Organic Site Activation List

Amplifying Descriptive Text Descriptor

TECHNICAL PARAMETER (Definintions and Choice List)

DEFINITION List Item #1

List Item #2

List Item #3

Heritage: The extent of the item's design that is new using a 0- 100% scale with the following guidelines:

- 0%-10% Existing design. Build-to-print or previously qualified design solution, TRL is expected to be high (e.g.

TRL 9).

- 10%-40% Minor design change. No change to form, fit, function of the solution. May result from parts obsolescence and/or producibility enhancements. Considers updates to configuration drawings and test procedures as necessary.

Includes any design reviews and changes to engineering/prototype/qualification models as needed.

Anticipate the design will be qualified by similarity or analysis.

TRL is expected to be high (e.g. TRL 8-9.)

- 40%-70% Moderate design changes. Solution derived from previously qualified design. Includes updates to configuration drawings and test procedures. Includes design reviews, modified tooling & test equipment, and engineering/prototype/qualification models needed to qualify the modified design.