1g - T3TRK Cost and Software Data Reporting (CSDR) Plan.xls
XLS spreadsheet 195 KB Posted
- Attached to
- Proliferated Warfighter Space Architecture Tranche 3 Tracking Layer (T3TRK) Federal contract opportunity
- Solicitation number
- SDA-PS-25-02
- Issued by
- Department of the Air Force
About this file
This document is a Cost and Software Data Reporting (CSDR) Plan for the Space Development Agency's Tranche 3 Tracking Layer (T3TRK) contract, detailing comprehensive technical and cost reporting requirements for a space-based missile tracking and defense system. The plan covers the development of a constellation of space vehicles, including a minimum of 54 satellites across six orbital planes, with payloads including infrared sensors, Global Navigation Satellite Systems (GNSS), directed energy sensors, and various communication and tracking technologies.
The reporting plan outlines detailed technical parameters for each system component, including mass, power requirements, data rates, and technology readiness levels. Reporting will occur through multiple submission events from 2025 to 2030, with initial and annual cost and technical reports. The space vehicles will include multiple variants such as Missile Warning/Missile Tracking (MW/MT) and Missile Warning, Tracking and Defense (MWTD), with sophisticated payload capabilities across Ka-band, networking, navigation, and optical communication subsystems. The fully deployed constellation is estimated to eventually include more than 100 satellites in Low Earth Orbit (LEO), supporting global missile threat detection and tracking capabilities.
View the file
Other files for this federal contract opportunity
| File | Type | Posted |
|---|---|---|
| 0 T3TRK - Program Solicitation - Amendment 2 (4-29-25).pdf | ||
| 5 - T3TRK Past Performance Questionnaire (Rev1 - 4-29-25).pdf | ||
| 3 - T3TRK Resume Template Rev 1 (4-28-25).pdf | ||
| 0 T3TRK - Program Solicitation - Amendment 1 (4-28-25).pdf | ||
| 0 T3TRK - Program Solicitation.pdf | ||
| 1 - T3TRK Other Transaction Agreement (OTA).pdf | ||
| 2 - T3TRK Personnel and Facilities Template.pdf | ||
| 4 - T3TRK Personnel Matrix.xlsx | XLSX spreadsheet | |
| 1e - T3TRK Government Furnished Items (GFX).pdf | ||
| 1f - T3TRK DD Form 254 TEMPLATE.pdf | ||
| 3 - T3TRK Resume Template.pdf | ||
| 5 - T3TRK Past Performance Questionnaire.pdf | ||
| T3TRK - Solicitation CoverLtr.pdf | ||
| 1b - T3TRK Schedule of Milestones Payments.pdf | ||
| 1d - T3TRK Data Rights Assertion Table.pdf |
Show all 15
On GovTribe
Work with this file on GovTribe
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
DD Form 2794, Pg 1 (METADATA)
| COST AND SOFTWARE DATA REPORTING PLAN | OMB No. 0704-0671 |
| The public reporting burden for this collection of information is estimated to average 57 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-0671). 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 | ||
| T3TRK - SDA Tranche 3 Tracking Layer | ||
| 1b. PHASE/MILESTONE (check all that apply) | ||
| Pre-A | ||
| A | ||
| X | B | |
| C-LRIP | ||
| C-FRP | ||
| O&S | ||
| 1c. PRIME MISSION PRODUCT | ||
| T3 Tracking Layer | ||
| 1d. ACQUISITION CATEGORY (ACAT) | ||
| Pre-ACAT | ||
| ACAT I (MDAP) | ||
| ACAT IA (MAIS) | ||
| ACAT II | ||
| ACAT III | ||
| X | Other | |
| 2. COMMODITY TYPE | ||
| Space System | ||
| 3. PLAN ITERATION TYPE | ||
| X | INITIAL | |
| REVISION | ||
| 4. CURRENT SUBMISSION DATE (YYYYMMDD) | ||
| 20250310 | ||
| 5. LAST APPROVED PLAN DATE (YYYYMMDD) | ||
| 6a. GOVERNMENT PLAN POINT OF CONTACT (POC) NAME (Last, First, M.) | ||
| TBD | ||
| 6b. ADDRESS (Include ZIP Code) | ||
| 6c. TELEPHONE NUMBER (Include Area Code) | ||
| 6d. E-MAIL ADDRESS | ||
| 7. PLAN TYPE | ||
| GOVERNMENT | ||
| X | CONTRACT (PRIME) | |
| CONTRACT (SUB) | ||
| 8. PLAN GOVERNMENT PREPARING ORGANIZATION | ||
| Space Development Agency | ||
| 9a. CONTRACTOR NAME/ADDRESS | ||
| i. REPORTING ORGANIZATION NAME | ||
| TBD | ||
| ii. DIVISION NAME | ||
| iii. LOCATION | ||
| iv. CONTRACTOR BUSINESS DATA REPORT (CBDR 1921-3) REQUIREMENT: | ||
| CBDR REQUIRED FOR THIS ORGANIZATION | ||
| 9b. CONTRACT NUMBER (List all that apply, separated by commas) | ||
| TBD - (AF-25-D-C3) | ||
| 9c. APPROPRIATION (check all that apply) | ||
| X | RDT&E | |
| PROCUREMENT | ||
| O&M | ||
| FMS | ||
| WCF | ||
| OTHER | ||
| 10a. APPROVED PLAN NUMBER | ||
| AF-25-D-C3 | ||
| 10b. APPROVED PLAN REVISION NUMBER | ||
| 0 | ||
| 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 | ||
| DD FORM 2794 (PAGE 1), METADATA, MAY 2024 | PREVIOUS EDITION IS OBSOLETE |
DD Form 2794, Pg 2 (REPORTING)
| COST AND SOFTWARE DATA REPORTING PLAN | COST, SOFTWARE, & TECHNICAL DATA REPORTING/EARNED VALUE MANAGEMENT CO-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 | Tranche 3 Tracking Layer | X | X | |
| 1.1 | 2 | SEIT/PM and Support Equipment | X | ||
| 1.1.1 | 3 | Systems Engineering | X | X | |
| 1.1.2 | 3 | System Test and Evaluation | X | ||
| 1.1.2.1 | 4 | Developmental Test and Evaluation | X | X | |
| 1.1.2.2 | 4 | Operational Test and Evaluation | X | X | |
| 1.1.2.3 | 4 | Mockups/System Integration Labs (SILs) | X | X | |
| 1.1.2.4 | 4 | Test and Evaluation Support | X | X | |
| 1.1.2.5 | 4 | Test Facilities | X | X | |
| 1.1.3 | 3 | Assembly, Integration and Test | X | X | |
| 1.1.4 | 3 | Program Management | X | X | |
| 1.1.5 | 3 | Support Equipment | X | X | X |
| 1.2 | 2 | Space Vehicle | X | X | |
| 1.2.1 | 3 | SEIT/PM and Support Equipment | X | X | |
| 1.2.2 | 3 | Bus | X | X | |
| 1.2.2.1 | 4 | SEIT/PM and Support Equipment | X | X | |
| 1.2.2.2 | 4 | Bus Hardware | X | X | X |
| 1.2.2.3 | 4 | Bus Flight Software | X | X | |
| 1.2.3 | 3 | Baseline Payloads | X | ||
| 1.2.3.1 | 4 | Ka-band Mission Payload | X | X | |
| 1.2.3.1.1 | 5 | SEIT/PM and Support Equipment | X | X | |
| 1.2.3.1.2 | 5 | Hardware Subsystem 1...n (Specify) | X | X | X |
| 1.2.3.1.3 | 5 | Ka-band Software | X | X | |
| 1.2.3.2 | 4 | Networking and Data Routing Payload | X | X | |
| 1.2.3.2.1 | 5 | SEIT/PM and Support Equipment | X | X | |
| 1.2.3.2.2 | 5 | Hardware Subsystem 1...n (Specify) | X | X | X |
| 1.2.3.2.3 | 5 | Networking and Data Routing Software | X | X | |
| 1.2.3.3 | 4 | Navigation Subsystem | X | X | |
| 1.2.3.3.1 | 5 | SEIT/PM and Support Equipment | X | X | |
| 1.2.3.3.2 | 5 | Hardware Subsystem 1...n (Specify) | X | X | X |
| 1.2.3.3.3 | 5 | Navigation Software | X | X | |
| 1.2.3.4 | 4 | S-band Backup TT&C Subsystem | X | X | |
| 1.2.3.4.1 | 5 | SEIT/PM and Support Equipment | X | X | |
| 1.2.3.4.2 | 5 | Hardware Subsystem 1...n (Specify) | X | X | X |
| 1.2.3.4.3 | 5 | S-band TT&C Software | X | X | |
| 1.2.3.5 | 4 | Optical Communication Terminals (OCTs) | X | X | |
| 1.2.3.5.1 | 5 | SEIT/PM and Support Equipment | X | X | |
| 1.2.3.5.2 | 5 | Hardware Subsystem 1...n (Specify) | X | X | X |
| 1.2.3.5.3 | 5 | OCT Software | X | X | |
| 1.2.4 | 3 | Upsilon Transport Variant | X | X | |
| 1.2.5 | 3 | Lambda Transport Variant | X | X | |
| 1.2.6 | 3 | Sigma Transport Variant | X | X | |
| 1.2.7 | 3 | Tracking Variant | X | ||
| 1.2.7.1 | 4 | Infrared Mission Payload | X | X | |
| 1.2.7.1.1 | 5 | SEIT/PM and Support Equipment | X | X | |
| 1.2.7.1.2 | 5 | Hardware Subsystem 1...n (Specify) | X | X | X |
| 1.2.7.1.3 | 5 | Infrared Payload Flight Software | X | X | |
| 1.2.7.2 | 4 | Global Navigation Satellite Systems (GNSS) Payload | X | X | |
| 1.2.7.2.1 | 5 | SEIT/PM and Support Equipment | X | X | |
| 1.2.7.2.2 | 5 | Hardware Subsystem 1...n (Specify) | X | X | X |
| 1.2.7.2.3 | 5 | GNSS Flight Software | X | X | |
| 1.2.7.3 | 4 | Directed Energy (DE) Sensor Payload | X | X | |
| 1.2.7.3.1 | 5 | SEIT/PM and Support Equipment | X | X | |
| 1.2.7.3.2 | 5 | Hardware Subsystem 1...n (Specify) | X | X | X |
| 1.2.7.3.3 | 5 | DE Sensor Flight Software | X | X | |
| 1.2.8 | 3 | Custody Layer | X | X | |
| 1.2.9 | 3 | Space Vehicle Storage | X | X | X |
| 1.2.10 | 3 | Space Vehicle Other | X | X | |
| 1.3 | 2 | Ground Segment | X | ||
| 1.3.1 | 3 | SEIT/PM and Support Equipment | X | X | |
| 1.3.2 | 3 | Hardware (FlatSat) | X | X | X |
| 1.3.3 | 3 | Software (NOVA) | X | X | |
| 1.4 | 2 | Launch | X | ||
| 1.4.1 | 3 | Launch SEIT/PM and Support Equipment | X | X | |
| 1.4.2 | 3 | Launch Vehicle Adapter/Dispenser | X | X | X |
| 1.4.3 | 3 | Launch Systems Integration (LSI) | X | X | |
| 1.4.4 | 3 | Launch Operations | X | X | |
| 1.5 | 2 | Operations | X | ||
| 1.5.1 | 3 | Launch and Early Operations (LEOPs) | X | X | |
| 1.5.2 | 3 | Operations and Sustainment (O&S) | X | X | |
| 1.6 | 2 | Insurance | X | ||
| 1.6.1 | 3 | SEPM | X | X | |
| 1.6.2 | 3 | Insurance Policy | X | X | |
| 1.6.3 | 3 | Insurance Settlements | 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 | |||
| DD FORM 2794 (PAGE 2), REPORTING, MAY 2024 |
DD Form 2794, Pg 3 (EVENTS)
| COST AND SOFTWARE DATA REPORTING PLAN | |||||||
| 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 | T3TRK - Initial Cost Report | Initial | 20251231 | 20260302 | ||
| 2 | Technical Data Report | T3TRK - Initial Technical Report | Initial | 20251231 | 20260302 | ||
| 3 | Cost and Hour Report (FlexFile), Quantity Data Report | T3TRK - Annual Cost Report #1 | Interim | 20261231 | 20270302 | ||
| 4 | Technical Data Report | T3TRK - Annual Technical Report #1 | Interim | 20261231 | 20270302 | ||
| 5 | Cost and Hour Report (FlexFile), Quantity Data Report | T3TRK - Annual Cost Report #2 | Interim | 20271231 | 20280301 | ||
| 6 | Technical Data Report | T3TRK - Annual Technical Report #2 | Interim | 20271231 | 20280301 | ||
| 7 | Cost and Hour Report (FlexFile), Quantity Data Report | T3TRK - Annual Cost Report #3 | Interim | 20281231 | 20290302 | ||
| 8 | Technical Data Report | T3TRK - Annual Technical Report #3 | Interim | 20281231 | 20290302 | ||
| 9 | Cost and Hour Report (FlexFile), Quantity Data Report | T3TRK - Annual Cost Report #4 | Interim | 20291231 | 20300302 | ||
| 10 | Technical Data Report | T3TRK - Annual Technical Report #4 | Interim | 20291231 | 20300302 | ||
| 11 | Cost and Hour Report (FlexFile), Quantity Data Report | T3TRK - Final Cost Report | Final | 20301031 | 20301231 | ||
| 12 | Technical Data Report | T3TRK - Final Technical Report | Final | 20301031 | 20301231 | ||
| DD FORM 2794 (PAGE 3), SUBMISSION EVENTS, MAY 2024 | PREVIOUS EDITION IS OBSOLETE |
DD Form 2794, Pg 4 (REMARKS)
| COST AND SOFTWARE DATA REPORTING PLAN |
| 15. REMARKS |
| A. In addition to the direction provided in the associated CSDR Data Item Descriptions (DIDs) and the CSDR Manual (DoDM 5000.04), the following instructions, requirements, and considerations found on this page/worksheet shall be utilized when collecting data and preparing CSDR submissions. This CSDR Contract plan is intended to capture costs associated with the contract number(s) listed in block 9.b, irrespective of contract type (e.g., firm-fixed price, cost-plus fixed fee) or CLIN structure, 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. |
| B. CSDR PLAN REMARKS & PREPARATION INSTRUCTIONS |
| 1. Costs reported against this CSDR plan shall be cumulative in nature (i.e., each submission shall report any and all costs incurred on and prior to the submission's "AS OF DATE" (block 14.e)). |
| i. WBS Element Names (block 11.c) Ending with "1...n (Contractor Shall Specify)": The contractor shall extend and specify (i.e., include additional WBS elements determined by the contractor) in order to provide additional insight into the contractor's technical approach or design. The additional WBS elements shall be developed in accordance with the WBS guidelines included in MIL-STD-881F (or latest version). |
| ii. The contractor may extend any WBS element in accordance with guidelines included in MIL-STD-881F (or latest version). Any changes to WBS, Order/Lot, End Item, and/or Period of Performance must be reported to the government prior to submission or immediately, with revised CSDR Plan, must be approved by the CSDR Plan approval authority. |
| C. SUBMISSION EVENTS & DATES |
| 1. Deliverable Preparation Instructions by AS OF and DUE Dates: All CSDR deliverable "AS OF DATE[S]" and "DUE DATE[S]" listed in blocks 14.e and 14.f are identified for planning purposes only. Submission dates are subject to change and are determined in accordance with the event drivers as identified below: |
| i. All "DUE DATE" requirements are equal to the "AS OF DATE" plus 60 calendar days. If the calculated "DUE DATE" does not fall on a regular business day, the "DUE DATE" will be the next regular business day on the contractor's accounting calendar. |
| ii. "Final" Submission Events must meet both of the following two conditions: Condition 1: The final end item(s) has been delivered and accepted by the government (e.g., as evidenced by a completed DD-250) or higher tier contractor in the case of a subcontractor, and Condition 2: 95% or more of all ATD costs associated with the Subtotal, G&A and FCCOM have been incurred relative to all costs the reporting entity expects to incur for each and every Order/Lot (defined in Item 4 of Data Group B) associated with the contract Subtotal, G&A, FCCOM and UB. |
| iii. If the Contract period of performance is extended by more than six months, or if the scope of work is modified to include work not otherwise covered by the CSDR Plan, the government may modify the CSDR Plan to require additional submission events and add additional WBS elements in order to ensure the accurate and complete collection of cost data associated with the modified contract. |
| D. COST & HOUR REPORT (FLEXFILE) |
| 1. The Reporting Entity is required to provide unit or sublot (specify) reporting for any given Order/Lot and End Item as outlined in block 18 of the DD Form 2794. |
| 2. 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. |
| 3. WBS Definitions & Remarks (Data Group C) 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 WBS Definitions & Remarks shall contain a disclosure statement detailing any differences between the CSDR reporting methodology and the reporting entity's Cost Accounting Standards. WBS Definitions & Remarks 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. |
| 4. The reporting entity must maintain and update WBS Definitions & Remarks 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 Definitions. |
| 5. Order/Lot: 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. |
| 6. End Items: 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 report submission, if required. |
| 7. The contractor shall utilize and include the following mappings from its accounting system to the Actual Cost-Hour Data tags: |
| i. {To be determined during the CSDR Readiness Review based on contractor's accounting system} = Tag1 |
| ii. {To be determined during the CSDR Readiness Review based on contractor's accounting system} = Tag2 |
| iii. {To be determined during the CSDR Readiness Review based on contractor's accounting system} = Tag3 |
| E. QUANTITY DATA REPORT |
| 1. 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. |
| 2. The Reporting Entity shall provide meaningful quantity information lower than the summary level in the remarks for hardware-related content across the following WBS elements: Peculiar Support Equipment, Common Support Equipment, and Initial Spares and Repair Parts, if applicable. |
| F. TECHNICAL DATA REPORT |
| 1. Include only UNCLASSIFIED/CUI information in Technical Data Report deliverables submitted to CADE. Notify the Government if any values associated with the Technical Parameter Requirements are classified. |
| G. RESOURCE DISTRIBUTION TABLE (RDT) |
| 1. Submissions of the Resource Distribution Table (RDT) are required under the following conditions: |
| i. An RDT shall be delivered no later than seven calendar days before the "CSDR Readiness Review". Prepare this submission of the RDT in accordance with the RDT Instructions on the CADE website at FAC/EAC value.This copy of the RDT will be used during the "CSDR Readiness Review" in order to identify which subcontractors will be required to provide CSDR reporting via electronic submission of deliverables directly to CADE and which subcontractors may qualify for a CSDR direct reporting subcontractor waiver. |
| ii. The contractor must notify the government program office immediately of the contractor identifying that a subcontractor who, at the time of initial subcontractor award, was not anticipated to qualify for direct subcontractor CSDR reporting via electronic submission of deliverables directly to CADE but is subsequently anticipated to meet the CSDR direct reporting subcontractor threshold value due to changes to scopes of work, end-item design, subcontractor/supplier, or subcontract price changes since initial contract award (unless the newly identified subcontractor has already been issued a subcontractor reporting waiver associated with this contract). |
| H. RELATIONSHIP/USE OF COST ACCOUNTING STANDARDS (CAS) |
| 1. The contractor shall follow the accounting procedures specified in its latest approved CAS Disclosure Statement and with any clauses or requirements included in the contract. As part of the CSDR Readiness Review, the contractor shall identify any aspect(s) of its latest approved CAS Disclosure Statement which preclude or inhibit compliance with this CSDR Plan. The contractor shall identify any deviations from its CAS disclosure statement it intends to utilize to prepare CSDR submissions. |
| 2. The contractor shall provide a description of significant accounting systems or CAS changes and how those changes effect the latest CSDR deliverable or the ability to compare CSDR deliverables provided before/after the accounting system/CAS revision. The contractor shall provide the description within the submission remarks of the FlexFile deliverable. |
| I. CSDR READINESS REVIEW |
| 1. The contractor shall host a CSDR-RR with the Government's Cost Working Group Integrated Product Team (CWIPT) IAW DFARS 242.503-2(b) and DoD Manual 5000.04 (CSDR Manual). The purpose of the CSDR-RR is to review the contract's CSDR requirements and assess how the Contractor's accounting system satisfies the CSDR requirements found in DODM 5000.04 and this CSDR Plan. Reference the CADE website for instructions and additional information: https://cade.osd.mil/csdrreportingguidance/dd2794.html |
| 2. The contractor and CWIPT will also review the initial submission of the "Resource Distribution Table (RDT)", in order to finalize which subcontractors will be required to provide CSDR reporting and electronic submission of deliverables directly to Cost Assessment Data Enterprise (CADE), and which subcontractors may qualify for a CSDR direct reporting subcontractor waiver. |
| 3. The CSDR-RR shall be held within 60 days of contract award or the start of work meeting on a date mutually agreed to by the CWIPT and the contractor. |
| J. SPACE-SPECIFIC DEFINITIONS |
| 1. The definitions are intended for application to all levels of integration, or WBS indenture, within the ground system: parts, materials and labor; hardware components, subassemblies, major assemblies and end items ("boxes"); computer software configuration items (CSCIs) and components (CSCs); and subsystems, system segments, and the system as a whole. |
| 2. General Definitions |
| i. Acquisition costs for development of the ground system are classified as nonrecurring irrespective of the milestone, phase or gate of the overall program or the WBS element in question. So NRE costs include initial development, upgrades, and improvements to hardware, software and facilities that make up the system. Thus, requirements definition, design, engineering analyses, development hardware and software, development testing, and development support hardware and software are nonrecurring efforts. |
| ii. Acquisition costs for production of ground operations and processing centers (GOPCs), Ground Entry Points (GEPs), along with associated facilities, and components thereof; for spares; and for replicated spacecraft components used in ground testing and simulators are classified as recurring. Costs for installation of previously developed software in ground stations are recurring. Similarly, costs for acquisition and installation of commercial off-the-shelf software (COTS) for operational use in ground stations are recurring. |
| iii. Operations and Support (O&S) costs for development of concepts, procedures, training materials and simulators are classified as nonrecurring. Costs for system operation and maintenance, including training, are recurring. |
| iv. Nonrecurring (NRE) general examples which apply to hardware, software, facilities and O&S include: initial development of spacecraft, GOPCs, GEPs and other system segments, elements, interfaces; support equipment used for development; software development; development of upgrades and improvements (despite magnitude) |
| v. Recurring (REC) general examples: Ground hardware production and installation; Construction of operational ground facilities; installation of developed and COTS software in GOPCs and GEPs; replicated space hardware in GOPCs and GEPs; spares for spacecraft, GOPCs and GEPs; test equipment, software and procedure maintenance; and system operation and maintenance |
| vi. The software definitions apply to ground station operational software, development software, and ground test software for development and production. Ground support equipment (GSE) is addressed below. It is usually treated separately from assembly, integration and test for cost collection and estimating purposes. |
| 3. Space Hardware Related Definitions |
| i. Nonrecurring Cost: |
Requirements definition, engineering design & analysis;
Manufacturing tooling, fixtures and procedures;
Development units (breadboard, engineering, qual), including parts and materials;
Handling and test support equipment, simulators;
Development, qualification and life testing;
Development and production test procedures;
Engineering support for development unit fabrication, assembly & tests;
Redesign, rework and retest to correct design flaws;
Maintenance of tooling and unit test equipment until first launch
ii. Recurring Cost:
Hardware production units (proto-flight, flight, spare);
Production unit parts & materials, assembly and testing;
Setup for fabrication, assembly and test;
Engineering support for production unit fabrication, assembly & tests;
Spare parts, materials and subassemblies for production units;
Rework and retest due to workmanship problems;
Maintenance of designs and production procedures;
Maintenance of tooling and unit test equipment after first launch;
Refurbishment (of both qual and proto-flight units)
| 4. Software Related Definitions |
| i. Nonrecurring Cost: |
Development of delivered operational S/W;
Software test procedures;
Software configuration management, quality assurance & documentation;
Support for/conduct of first-time software I&T with hardware and subsequent higher level I&T;
Test, development support and space vehicle production support S/W: develop. and maint. up to 1st launch;
Commercial S/W licenses for development facilities and ground station development support;
Fixing deficiencies and developing enhancements in Ground and flight software from installation up to IOC
ii. Recurring Cost:
Installation and check-out of developed S/W in ground stations;
If first-time S/W I&T is performed at ground station, then it is NRE;
Maintenance of S/C production & test support S/W after first launch;
Acquisition of stand-alone and bundled COTS S/W in operational system;
Maintenance of flight S/W (usually embedded in acquisition contracts)
| 5. Systems Engineering Related Definitions |
| i. Nonrecurring Cost: |
Requirements definition, allocation and flow-down;
Specifications and ICDs - initial development & maintenance until all TBDs and TBRs are removed;
Top level design trade-offs and system definition;
Analyses and simulations of system performance and effectiveness, mission assurance, reliability,availability, maintainability, survivability, security, safety, EMI/EMC, radiation, survivability, contamination control, human engineering, autonomy and fault management;
Operations concept development;
Technical direction and configuration control during development;
Risk management though CDR;
Mass, power, link margin & reliability budgets -- initial development & maintenance until design complete;
Processing time & memory budgets;
Development, production, verification, risk management, training and security plans;
Parts, materials and processes - establishing procedures, etc.;
Product assurance development tasks;
Requirements verification through design completion, including demonstrations and IV&V;
Technical change management (RFIs, ECPs, etc.) -- NR tasks supporting changes, handling nonrecurring-only changes;
Design Integration -- mechanical, electrical, thermal, facilities;
Functional and physical configuration audit (FCA/PCA) support;
System documentation
ii. Recurring Cost:
Maintenance of specs, ICDs, plans & budgets -- after all TBDs and TBRs are removed;
Performance, S/W maintenance productivity metrics;
Analysis updates;
System configuration control after design completion;
Mass, power, link margin & reliability budgets - supporting production;
Support for production testing, rehearsals and operational test and evaluation;
Product assurance;
Requirements verification after design completion;
Launch readiness reviews, support for product acceptance;
Technical change management (RFIs, ECPs, etc.) -- supporting recurring portions of changes and recurring- only changes
| 6. Assembly Integration & Test (AI&T) Related Definitions |
| i. Nonrecurring Cost: |
Development, qualification and life testing - all levels and system segments;
Development and acceptance test plans and procedures;
Development, qualification and life test analysis and reports;
I&T for correcting software problems prior to IOC
ii. Recurring Cost:
Space vehicle assembly, integration and acceptance testing;
Acceptance test analysis and reports;
Integration and test of previously-developed software -in GOPCs, GEPs
| 7. Program Management Related Definitions |
| i. Nonrecurring Cost: |
Management activities applied to/associated with NRE efforts - top level program management, project control and planning, business/financial mgmt, subcontract mgmt, product effectiveness, computer support;
Procedures and infrastructure establishment - Cost accounting, configuration & data management, parts & material acquisition, security, facilities
ii. Recurring Cost:
Management activities applied to/associated with REC efforts
| 8. Expanded Ground Support Equipment Definitions |
| i. Nonrecurring Cost: |
Concept of operations and maintenance development;
Operations & maintenance procedure development;
Development of training materials, simulators and aids;
Initial ILS analysis and data;
Upgrades/changes to above associated with: Major redesigns, capability increments Recapitalization, operating system changes
ii. Recurring Cost:
System operation costs - operations, training, systems engineering & management staff;
Hardware maintenance & recapitalization;
Software maintenance - including COTS license costs;
Software modifications/fixes after IOC;
Reproduction and updating of technical data and manuals;
Procurement/production of hardware spares;
Rehearsals and initialization of space vehicles
| 9. Pre-Operations Support Definitions |
| i. Pre-Operations Maintenance 1..n (Specify): |
These elements contain all the resources related to the pre-operations (Pre-Ops) maintenance (software updates) of Software. This function begins with the acceptance of the Software elements and ends with the start of Operations.
ii. Pre-Operations Mission Support:
These elements include all the resources required for the operation of the Space or Ground system prior to turn-over. Includes, for example:
a. On-orbit testing; routine monitoring of Space or Ground system equipment health and status
b. Fault detection
c. Anomaly investigation and resolution. (The Mission Support period typically begins after installation and a specified time prior to launch and ends when the Space Vehicle achieves initial operational capability.)
DD FORM 2794 (PAGE 4), REMARKS, MAY 2024 PREVIOUS EDITION IS OBSOLETE
DD Form 2794, Pg 5 (SCOPE DEF)
| COST AND SOFTWARE DATA REPORTING PLAN | |||||
| INTRA-CONTRACT SCOPE REPORTING DEFINITION | |||||
| 16. ORDERS/LOTS | |||||
| a. ID | b. NAME | c. PHASE/MILESTONE | |||
| 1 | Baseline Development | B | |||
| 17. END ITEMS | |||||
| a. ID | b. NAME | ||||
| MW/MT | Missile Warning/Missile Tracking (MW/MT) Variant | ||||
| MWTD | Missile Warning, Tracking and Defense (MWTD) Variant | ||||
| 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)
DD FORM 2794 (PAGE 5), INTRA-CONTRACT SCOPE, MAY 2024
DD Form 2794, Pg 9a (TECH RQTS)
| COST AND SOFTWARE DATA REPORTING PLAN - TECHNICAL PARAMETER REQUIREMENTS | ||||||||||
| TECHNICAL PARAMETER REQUIREMENTS | ||||||||||
| 29. WBS | ||||||||||
| ELEMENT CODE | 30. WBS ELEMENT NAME | 31. ITEM TYPE | 32. TECHNICAL PARAMETER | |||||||
| a. PARAMETER NAME | b. UNIT OF MEASURE | c. UNIT OF MEASURE QUALIFIER | d. REPEATABLE | e. DEFINITION | f. REMARKS | |||||
| 1.0 | Tranche 3 Tracking Layer | Milestone Date | Contract Award | Date | Contract Award date | |||||
| 1.0 | Tranche 3 Tracking Layer | Milestone Date | System PDR | Date | PDR date | |||||
| 1.0 | Tranche 3 Tracking Layer | Milestone Date | System CDR | Date | CDR date | |||||
| 1.0 | Tranche 3 Tracking Layer | Milestone Date | System PRR | Date | PRR date | |||||
| 1.0 | Tranche 3 Tracking Layer | Milestone Date | Launch | Date | By Launch | Y | Date of each launch | |||
| 1.0 | Tranche 3 Tracking Layer | Space System | Orbit Altitude (km) | Kilometers (km) | For planet orbiting vehicles (satellites) the average orbital altitude of the vehicle from planet surface (Avg). For earth orbiting satellites, the average height above sea level. | |||||
| 1.0 | Tranche 3 Tracking Layer | Space System | Orbit Inclination (deg) | Degrees | The angular distance (in degrees) of the Space Vehicle (SV) orbital plane from the equator or the ecliptic from the orbited object. | |||||
| 1.0 | Tranche 3 Tracking Layer | Space System | Mission Assurance Class | List | The Mission Class (A through D) from the Technical Parameter Requirement list | Class A - D, Commercial | ||||
| 1.0 | Tranche 3 Tracking Layer | Space System | Mission Type | List | Defines the primary mission being executed (e.g. Communication, surveillance, scientific, navigation, experimental, environmental) | |||||
| 1.2 | Space Vehicle | SpaceVehicle | Learning Curve | Percent (%) | DELETE | |||||
| 1.2 | Space Vehicle | SpaceVehicle | Total Payload Mass | Kilograms (kg) | Combined mass of all payloads on a space vehicle. | |||||
| 1.2 | Space Vehicle | SpaceVehicle | Mass - Dry | Kilograms (kg) | Mass of space vehicle excluding fuel/propellant. | |||||
| 1.2 | Space Vehicle | SpaceVehicle | Mass - Wet | Kilograms (kg) | Total fueled mass of the space vehicle upon delivery to orbit. | |||||
| 1.2 | Space Vehicle | SpaceVehicle | Power - Beginning of Life (BOL) | Watts (W) | Beginning of Life (BOL) power | |||||
| 1.2 | Space Vehicle | SpaceVehicle | Power - End of Life (EOL) | Watts (W) | End of Life (EOL) power | |||||
| 1.2 | Space Vehicle | SpaceVehicle | Average Day Power (EOL) | Watts (W) | The average power output from the solar arrays when fully exposed to the sun at the end of spacecraft design life. | |||||
| 1.2 | Space Vehicle | SpaceVehicle | Average Eclipse Power (EOL) | Watts (W) | The average power output from the solar arrays when the sun is partially blocked by the earth (or other body) at the end of spacecraft design life. | |||||
| 1.2.2 | Bus | Spacecraft Bus | Vendor | Descriptor | Subcontractor producing the item (if applicable). | |||||
| 1.2.2 | Bus | Heritage | New Design | Percent (%) | 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. TRL is expected to be moderately high (e.g. TRL 7-8). - 70%-100% Major redesign or new design to meet derived requirements. New form, fit, and function solution. Includes design reviews, tooling & test equipment, and engineering/prototype/qualification models needed to qualify the design. This range suggests a significant design effort - TRL may be in the 5-7 range. Note for all designs lower than TRL-6, significant technology maturation may be required over and above the effort outlined above. | |||||
| 1.2.2 | Bus | Heritage | Flight Heritage | Name/Number | The heritage or most similar previous product from which the subject product was derived. | |||||
| 1.2.2 | Bus | Spacecraft Bus | Current TRL | List | Technology Readiness Levels (TRL) are a set of nine graded definitions/descriptions of stages of technology maturity. They were originated by the National Aeronautics and Space Administration and adapted by the DOD for use in its acquisition system. | |||||
| 1.2.2 | Bus | Spacecraft Bus | Learning Curve | Percent (%) | Estimated Unit Theory learning curve percentage where each time the cumulative production quantity doubles, the cost (or time) to produce one additional unit decreases by this constant percentage. | |||||
| 1.2.2 | Bus | Spacecraft Bus | Mass - Basic | Kilograms (kg) | The basic mass in kilograms (kg). This value is based on an assessment of the most recent baseline design, excluding mass growth allowance. Total dry weight of the product or box in kilograms (exclude propellants, pressurants, refrigerants, etc.). The weight excludes weight growth (contingency). Where the line-item described by the weight is being used to represent N identical items (assemblies or boxes), the weight is the weight of one assembly or box. Where the line-item represents a collection of different items, such as a collection of propulsion subsystem valves, filters and sensors, the unit weight is the sum of the weights of all of the items represented. | |||||
| 1.2.2 | Bus | Spacecraft Bus | Mass - Growth Allowance | Kilograms (kg) | The mass growth allowance in kilograms (kg). This value is the likely change to the basic mass, based on an assessment of the design maturity, allowing for design changes that may occur, excluding changes due to contract/requirements changes. Note that this value represents the summation of mass growth for a total quantity per space vehicle within the next higher unit/subsystem; i.e. it is not the mass growth for a single unit unless there is only one of these products within the next higher level product element. | |||||
| 1.2.2 | Bus | Spacecraft Bus | Total Required Power - Nominal | Watts (W) | Power required by all bus subsystems for nominal operations | |||||
| 1.2.2 | Bus | Spacecraft Bus | Total Required Power - Peak | Watts (W) | Peak Power required by all bus subsystems for operations | |||||
| 1.2.2 | Bus | Spacecraft Bus | Data Rate | Mbps | The speed at which information is transferred through a communications or computing medium; measured in megabits per second. | |||||
| 1.2.2 | Bus | Spacecraft Bus | Total Impulse (Delta-V) | Meters/Second | Total impulse is the product of thrust times duration over the motor burn time. This measures the total amount of momentum imparted to the rocket by the motor. | |||||
| 1.2.2.3 | Blus Flight Software | SoftwareNonSRDR | Equivalent Source Lines of Code Generated | Equivalent Source Lines of Code (ESLOC) | Actual to Date | Equivalent Source Lines of Code calculated as the sum of: Total New Lines of Code x 100% Total Modified Lines of Code x Adaptive Factor (typically varies between 15-50% depending on language and complexity) Total Reuse Lines of Code x Adaptive Factor (typically 5-7%) Auto-Generated Lines of Code x 32% | ||||
| 1.2.2.3 | Blus Flight Software | SoftwareNonSRDR | Equivalent Source Lines of Code Generated | Equivalent Source Lines of Code (ESLOC) | Estimate at Complete | Equivalent Source Lines of Code calculated as the sum of: Total New Lines of Code x 100% Total Modified Lines of Code x Adaptive Factor (typically varies between 15-50% depending on language and complexity) Total Reuse Lines of Code x Adaptive Factor (typically 5-7%) Auto-Generated Lines of Code x 32% | ||||
| 1.2.3.1 | Ka-band Mission Payload | Payload | Vendor | Descriptor | Subcontractor producing the item (if applicable). | |||||
| 1.2.3.1 | Ka-band Mission Payload | Heritage | New Design | Percent (%) | 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. TRL is expected to be moderately high (e.g. TRL 7-8). - 70%-100% Major redesign or new design to meet derived requirements. New form, fit, and function solution. Includes design reviews, tooling & test equipment, and engineering/prototype/qualification models needed to qualify the design. This range suggests a significant design effort - TRL may be in the 5-7 range. Note for all designs lower than TRL-6, significant technology maturation may be required over and above the effort outlined above. | |||||
| 1.2.3.1 | Ka-band Mission Payload | Heritage | Flight Heritage | Name/Number | The heritage or most similar previous product from which the subject product was derived. | |||||
| 1.2.3.1 | Ka-band Mission Payload | Payload | Current TRL | List | Technology Readiness Levels (TRL) are a set of nine graded definitions/descriptions of stages of technology maturity. They were originated by the National Aeronautics and Space Administration and adapted by the DOD for use in its acquisition system. | |||||
| 1.2.3.1 | Ka-band Mission Payload | Payload | Learning Curve | Percent (%) | Estimated Unit Theory learning curve percentage where each time the cumulative production quantity doubles, the cost (or time) to produce one additional unit decreases by this constant percentage. | |||||
| 1.2.3.1 | Ka-band Mission Payload | Payload | Mass - Basic | Kilograms (kg) | The basic mass in kilograms (kg). This value is based on an assessment of the most recent baseline design, excluding mass growth allowance. Total dry weight of the product or box in kilograms (exclude propellants, pressurants, refrigerants, etc.). The weight excludes weight growth (contingency). Where the line-item described by the weight is being used to represent N identical items (assemblies or boxes), the weight is the weight of one assembly or box. Where the line-item represents a collection of different items, such as a collection of propulsion subsystem valves, filters and sensors, the unit weight is the sum of the weights of all of the items represented. | |||||
| 1.2.3.1 | Ka-band Mission Payload | Payload | Mass - Growth Allowance | Kilograms (kg) | The mass growth allowance in kilograms (kg). This value is the likely change to the basic mass, based on an assessment of the design maturity, allowing for design changes that may occur, excluding changes due to contract/requirements changes. Note that this value represents the summation of mass growth for a total quantity per space vehicle within the next higher unit/subsystem; i.e. it is not the mass growth for a single unit unless there is only one of these products within the next higher level product element. | |||||
| 1.2.3.1 | Ka-band Mission Payload | Payload | Total Required Power - Nominal | Watts (W) | Power required by all payload subsystems for nominal operations | |||||
| 1.2.3.1 | Ka-band Mission Payload | Payload | Total Required Power - Peak | Watts (W) | Peak Power required by all payload subsystems for operations | |||||
| 1.2.3.1 | Ka-band Mission Payload | Payload | Data Rate | Mbps | The speed at which information is transferred through a communications or computing medium; measured in megabits per second. | |||||
| 1.2.3.1.2 | Hardware Subsystem 1...n (Specify) | PhysicalElec | Mass - Basic | Kilograms (kg) | The basic mass in kilograms (kg). This value is based on an assessment of the most recent baseline design, excluding mass growth allowance. Total dry weight of the product or box in kilograms (exclude propellants, pressurants, refrigerants, etc.). The weight excludes weight growth (contingency). Where the line-item described by the weight is being used to represent N identical items (assemblies or boxes), the weight is the weight of one assembly or box. Where the line-item represents a collection of different items, such as a collection of propulsion subsystem valves, filters and sensors, the unit weight is the sum of the weights of all of the items represented. | |||||
| 1.2.3.1.2 | Hardware Subsystem 1...n (Specify) | PhysicalElec | Mass - Growth Allowance | Kilograms (kg) | The mass growth allowance in kilograms (kg). This value is the likely change to the basic mass, based on an assessment of the design maturity, allowing for design changes that may occur, excluding changes due to contract/requirements changes. Note that this value represents the summation of mass growth for a total quantity per space vehicle within the next higher unit/subsystem; i.e. it is not the mass growth for a single unit unless there is only one of these products within the next higher level product element. | |||||
| 1.2.3.1.3 | Ka-band Flight Software | SoftwareNonSRDR | Equivalent Source Lines of Code Generated | Equivalent Source Lines of Code (ESLOC) | Actual to Date | Equivalent Source Lines of Code calculated as the sum of: Total New Lines of Code x 100% Total Modified Lines of Code x Adaptive Factor (typically varies between 15-50% depending on language and complexity) Total Reuse Lines of Code x Adaptive Factor (typically 5-7%) Auto-Generated Lines of Code x 32% | ||||
| 1.2.3.1.3 | Ka-band Flight Software | SoftwareNonSRDR | Equivalent Source Lines of Code Generated | Equivalent Source Lines of Code (ESLOC) | Estimate at Complete | Equivalent Source Lines of Code calculated as the sum of: Total New Lines of Code x 100% Total Modified Lines of Code x Adaptive Factor (typically varies between 15-50% depending on language and complexity) Total Reuse Lines of Code x Adaptive Factor (typically 5-7%) Auto-Generated Lines of Code x 32% | ||||
| 1.2.3.2 | Networking and Data Routing Payload | Payload | Vendor | Descriptor | Subcontractor producing the item (if applicable). | |||||
| 1.2.3.2 | Networking and Data Routing Payload | Heritage | New Design | Percent (%) | 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. TRL is expected to be moderately high (e.g. TRL 7-8). - 70%-100% Major redesign or new design to meet derived requirements. New form, fit, and function solution. Includes design reviews, tooling & test equipment, and engineering/prototype/qualification models needed to qualify the design. This range suggests a significant design effort - TRL may be in the 5-7 range. Note for all designs lower than TRL-6, significant technology maturation may be required over and above the effort outlined above. | |||||
| 1.2.3.2 | Networking and Data Routing Payload | Heritage | Flight Heritage | Name/Number | The heritage or most similar previous product from which the subject product was derived. | |||||
| 1.2.3.2 | Networking and Data Routing Payload | Payload | Current TRL | List | Technology Readiness Levels (TRL) are a set of nine graded definitions/descriptions of stages of technology maturity. They were originated by the National Aeronautics and Space Administration and adapted by the DOD for use in its acquisition system. | |||||
| 1.2.3.2 | Networking and Data Routing Payload | Payload | Learning Curve | Percent (%) | Estimated Unit Theory learning curve percentage where each time the cumulative production quantity doubles, the cost (or time) to produce one additional unit decreases by this constant percentage. | |||||
| 1.2.3.2 | Networking and Data Routing Payload | Payload | Mass - Basic | Kilograms (kg) | The basic mass in kilograms (kg). This value is based on an assessment of the most recent baseline design, excluding mass growth allowance. Total dry weight of the product or box in kilograms (exclude propellants, pressurants, refrigerants, etc.). The weight excludes weight growth (contingency). Where the line-item described by the weight is being used to represent N identical items (assemblies or boxes), the weight is the weight of one assembly or box. Where the line-item represents a collection of different items, such as a collection of propulsion subsystem valves, filters and sensors, the unit weight is the sum of the weights of all of the items represented. | |||||
| 1.2.3.2 | Networking and Data Routing Payload | Payload | Mass - Growth Allowance | Kilograms (kg) | The mass growth allowance in kilograms (kg). This value is the likely change to the basic mass, based on an assessment of the design maturity, allowing for design changes that may occur, excluding changes due to contract/requirements changes. Note that this value represents the summation of mass growth for a total quantity per space vehicle within the next higher unit/subsystem; i.e. it is not the mass growth for a single unit unless there is only one of these products within the next higher level product element. | |||||
| 1.2.3.2 | Networking and Data Routing Payload | Payload | Total Required Power - Nominal | Watts (W) | Power required by all payload subsystems for nominal operations | |||||
| 1.2.3.2 | Networking and Data Routing Payload | Payload | Total Required Power - Peak | Watts (W) | Peak Power required by all payload subsystems for operations | |||||
| 1.2.3.2 | Networking and Data Routing Payload | Payload | Data Rate | Mbps | The speed at which information is transferred through a communications or computing medium; measured in megabits per second. | |||||
| 1.2.3.2.2 | Hardware Subsystem 1...n (Specify) | PhysicalElec | Mass - Basic | Kilograms (kg) | The basic mass in kilograms (kg). This value is based on an assessment of the most recent baseline design, excluding mass growth allowance. Total dry weight of the product or box in kilograms (exclude propellants, pressurants, refrigerants, etc.). The weight excludes weight growth (contingency). Where the line-item described by the weight is being used to represent N identical items (assemblies or boxes), the weight is the weight of one assembly or box. Where the line-item represents a collection of different items, such as a collection of propulsion subsystem valves, filters and sensors, the unit weight is the sum of the weights of all of the items represented. | |||||
| 1.2.3.2.2 | Hardware Subsystem 1...n (Specify) | PhysicalElec | Mass - Growth Allowance | Kilograms (kg) | The mass growth allowance in kilograms (kg). This value is the likely change to the basic mass, based on an assessment of the design maturity, allowing for design changes that may occur, excluding changes due to contract/requirements changes. Note that this value represents the summation of mass growth for a total quantity per space vehicle within the next higher unit/subsystem; i.e. it is not the mass growth for a single unit unless there is only one of these products within the next higher level product element. | |||||
| 1.2.3.2.3 | Networking and Data Routing Software | SoftwareNonSRDR | Equivalent Source Lines of Code Generated | Equivalent Source Lines of Code (ESLOC) | Actual to Date | Equivalent Source Lines of Code calculated as the sum of: Total New Lines of Code x 100% Total Modified Lines of Code x Adaptive Factor (typically varies between 15-50% depending on language and complexity) Total Reuse Lines of Code x Adaptive Factor (typically 5-7%) Auto-Generated Lines of Code x 32% | ||||
| 1.2.3.2.3 | Networking and Data Routing Software | SoftwareNonSRDR | Equivalent Source Lines of Code Generated | Equivalent Source Lines of Code (ESLOC) | Estimate at Complete | Equivalent Source Lines of Code calculated as the sum of: Total New Lines of Code x 100% Total Modified Lines of Code x Adaptive Factor (typically varies between 15-50% depending on language and complexity) Total Reuse Lines of Code x Adaptive Factor (typically 5-7%) Auto-Generated Lines of Code x 32% | ||||
| 1.2.3.3 | Navigation Subsystem | Payload | Vendor | Descriptor | Subcontractor producing the item (if applicable). |
This is the start of the file's text. The full file is on GovTribe.
File details come from the government source that posted it. Updated .