ATTACHMENT 8 DD 2794 IDIQ CSDR Plan v2.xlsx
XLSX spreadsheet 96 KB Posted
- Attached to
- RFP - Space Test Experiments Platform (STEP) 2. 0 Federal contract opportunity
- Solicitation number
- FA880924RB001
- Issued by
- Department of the Air Force
About this file
This document is a DD Form 2794, which is a Cost and Software Data Reporting (CSDR) Plan for the Space Test Experiment Platform (STEP) 2.0 program. The STEP 2.0 program is an Indefinite Delivery/Indefinite Quantity (IDIQ) contract vehicle that will procure spacecraft and space access for science and technology experiments.
The CSDR Plan provides details on the technical, cost, and software data that the contractor must report for this contract. Key details include the contract phases, work breakdown structure, cost reporting requirements (actuals, forecast, and technical data), as well as the specific submission events and dates. The contract allows for Firm-Fixed Price (FFP) or Cost-Plus-Fixed-Fee (CPFF) contract types, and requires reporting of COVID-19 impacts. The CSDR Plan also defines the treatment of recurring and nonrecurring costs for various space system elements.
View the file
Other files for this federal contract opportunity
Show all 27
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-0188 |
| The public reporting burden for this collection of information is estimated to average 8 hours per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection of information. Send comments regarding this burden estimate or any other aspect of this collection of information, including suggestions for reducing the burden, to Department of Defense, Executive Services Directorate (0704-0188). Respondents should be aware that notwithstanding any other provision of law, no person shall be subject to any penalty for failing to comply with a collection of information if it does not display a currently valid OMB control number. |
PLEASE DO NOT RETURN YOUR COMPLETED FORM TO THE ABOVE ORGANIZATION.
| 1a. PROGRAM NAME | |
| Space Test Experiment Platform 2.0 (STEP 2.0) | |
| 1b. PHASE/MILESTONE (check all that apply) | |
| Pre-A | |
| A | |
| X | B |
| C-LRIP | |
| C-FRP | |
| O&S | |
| 1c. PRIME MISSION PRODUCT | |
| STPSat-8 through STPSat-n Space Systems | |
| 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) | |
| TBD | |
| 5. LAST APPROVED PLAN DATE (YYYYMMDD) |
| 6a. GOVERNMENT PLAN POINT OF CONTACT (POC) NAME (Last, First, M.) | |
| Adair, Carrie, L. | |
| 6b. ADDRESS (Include ZIP Code) | |
| 3548 Aberdeen Ave SE, Kirtland AFB, NM 87117 | |
| 6c. TELEPHONE NUMBER (Include Area Code) | |
| 505-846-3422 | |
| 6d. E-MAIL ADDRESS | |
| carrie.adair@spaceforce.mil | |
| 7. PLAN TYPE | |
| GOVERNMENT | |
| X | CONTRACT (PRIME) |
| CONTRACT (SUB) | |
| 8. PLAN GOVERNMENT PREPARING ORGANIZATION | |
| SSC/DCIS | |
| 9a. CONTRACTOR NAME/ADDRESS | |
| i. REPORTING ORGANIZATION NAME | |
| TBD | |
| ii. DIVISION NAME | |
| TBD | |
| iii. LOCATION | |
| TBD | |
| iv. CONTRACTOR BUSINESS DATA REPORT (CBDR 1921-3) REQUIREMENT: | |
| CBDR REQUIRED FOR THIS ORGANIZATION | |
| 9b. CONTRACT NUMBER (List all that apply, separated by commas) | |
| TBD | |
| 9c. APPROPRIATION (check all that apply) | |
| X | RDT&E |
| X | PROCUREMENT |
| O&M | |
| FMS | |
| WCF | |
| OTHER | |
| 10a. APPROVED PLAN NUMBER | |
| AF-22-G1 | |
| 10b. APPROVED PLAN REVISION NUMBER |
| 10c. APPROVED PLAN REQUIREMENTS | |
| X | AT COMPLETION COSTS FOR STANDARD FUNCTIONAL CATEGORIES (FlexFile or Legacy) |
| X | AT COMPLETION COSTS FOR RECURRING/NONRECURRING (FlexFile only) |
| X | TECHNICAL DATA REQUIRED |
| 10d. COST REPORT TYPE | |
| X | FLEXFILE |
| LEGACY DD 1921 SERIES |
DRAFT DD FORM 2794 (PAGE 1), METADATA, JANUARY 2019 PREVIOUS EDITION IS OBSOLETE
&F &A FA8809-24-R-B001
mailto:carrie.adair@spaceforce.mil 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 | STEP 2.0 | ||
| 1.1 | 2 | SEIT/PM and Support Equipment | ||
| 1.1.1 | 3 | Systems Engineering | X | X |
| 1.1.2 | 3 | System Test and Evaluation | ||
| 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 |
| 1.2 | 2 | Space Vehicle | ||
| 1.2.1 | 3 | SEIT/PM and Support Equipment | ||
| 1.2.1.1 | 4 | Systems Engineering | X | X |
| 1.2.1.2 | 4 | Assembly, Integration and Test | X | X |
| 1.2.1.3 | 4 | Program Management | X | X |
| 1.2.1.4 | 4 | Support Equipment | X | X |
| 1.2.2 | 3 | Bus | ||
| 1.2.2.1 | 4 | SEIT/PM and Support Equipment | ||
| 1.2.2.1.1 | 5 | Systems Engineering | X | X |
| 1.2.2.1.2 | 5 | Assembly, Integration and Test | X | X |
| 1.2.2.1.3 | 5 | Program Management | X | X |
| 1.2.2.1.4 | 5 | Support Equipment | X | X |
| 1.2.2.2 | 4 | Structures and Mechanisms (SMS) | X | X |
| 1.2.2.3 | 4 | Thermal Control (TCS) | X | X |
| 1.2.2.4 | 4 | Electrical Power (EPS) | X | X |
| 1.2.2.5 | 4 | Attitude Control Subsystem (ACS) | X | X |
| 1.2.2.6 | 4 | Propulsion Subsystem | X | X |
| 1.2.2.7 | 4 | Telemetry, Tracking, and Command Subsystem (TT&C) | X | X |
| 1.2.2.8 | 4 | Bus Flight Software | X | X |
| 1.2.3 | 3 | Payload Suite Integration & Test | ||
| 1.2.3.1 | 4 | SEIT/PM and Support Equipment | ||
| 1.2.3.1.1 | 5 | Systems Engineering | X | X |
| 1.2.3.1.2 | 5 | Assembly, Integration and Test | X | X |
| 1.2.3.1.3 | 5 | Program Management | X | X |
| 1.2.3.1.4 | 5 | Support Equipment | X | X |
| 1.2.3.2 | 4 | Payloads Integration & Test | ||
| 1.2.3.2.1 | 5 | Inter-Port AI&T | ||
| 1.2.3.2.1.1 | 6 | Inter-Port AI&T #1 | X | X |
| 1.2.3.2.1.2 | 6 | Inter-Port AI&T #n | X | X |
| 1.2.3.2.1.3 | 6 | Inter-Port AI&T #3 | X | X |
| 1.2.3.2.1.4 | 6 | Inter-Port AI&T #4 | X | X |
| 1.2.3.2.1.5 | 6 | Inter-Port AI&T #5 | X | X |
| 1.2.3.2.1.6 | 6 | Inter-Port AI&T #6 | X | X |
| 1.2.3.2.2 | 5 | Multi-Payload Intra-Port AI&T | ||
| 1.2.3.2.2.1 | 6 | Multi-Payload Intra-Port AI&T #1 | X | X |
| 1.2.3.2.2.2 | 6 | Multi-Payload Intra-Port AI&T #n | X | X |
| 1.2.3.2.2.3 | 6 | Multi-Payload Intra-Port AI&T #3 | X | X |
| 1.2.3.2.2.4 | 6 | Multi-Payload Intra-Port AI&T #4 | X | X |
| 1.2.3.2.2.5 | 6 | Multi-Payload Intra-Port AI&T #5 | X | X |
| 1.2.3.2.2.6 | 6 | Multi-Payload Intra-Port AI&T #6 | X | X |
| 1.2.3.2.3 | 5 | Payload I&T | ||
| 1.2.3.2.3.1 | 6 | Payload #1 I&T | X | X |
| 1.2.3.2.3.2 | 6 | Payload #n I&T | X | X |
| 1.2.3.2.3.3 | 6 | Payload #3 I&T | X | X |
| 1.2.3.2.3.4 | 6 | Payload #4 I&T | X | X |
| 1.2.3.2.3.5 | 6 | Payload #5 I&T | X | X |
| 1.2.3.2.3.6 | 6 | Payload #6 I&T | X | X |
| 1.2.3.2.3.7 | 6 | Payload #7 I&T | X | X |
| 1.2.3.2.3.8 | 6 | Payload #8 I&T | X | X |
| 1.2.3.2.3.9 | 6 | Payload #9 I&T | X | X |
| 1.2.3.2.3.10 | 6 | Payload #10 I&T | X | X |
| 1.2.3.2.3.11 | 6 | Payload #11 I&T | X | X |
| 1.2.3.2.3.12 | 6 | Payload #12 I&T | X | X |
| 1.2.3.2.3.13 | 6 | Payload #13 I&T | X | X |
| 1.2.3.2.3.14 | 6 | Payload #14 I&T | X | X |
| 1.2.3.2.3.15 | 6 | Payload #15 I&T | X | X |
| 1.2.3.2.3.16 | 6 | Payload #16 I&T | X | X |
| 1.2.3.2.3.17 | 6 | Payload #17 I&T | X | X |
| 1.2.3.2.3.18 | 6 | Payload #18 I&T | X | X |
| 1.2.3.2.3.19 | 6 | Payload #19 I&T | X | X |
| 1.2.3.2.3.20 | 6 | Payload #20 I&T | X | X |
| 1.2.4 | 3 | Payload (N/A to program) | X | X |
| 1.2.5 | 3 | Booster Adapter | X | X |
| 1.2.6 | 3 | Space Vehicle Storage | X | X |
| 1.2.7 | 3 | Launch Systems Integration (LSI) | X | X |
| 1.2.8 | 3 | Launch Operations | X | X |
| 1.2.9 | 3 | Mission Operations Support | X | X |
| 1.2.10 | 3 | Space Vehicle Other | X | X |
| 1.3 | 2 | Ground Segment | ||
| 1.3.1 | 3 | SEIT/PM and Support Equipment | ||
| 1.3.1.1 | 4 | Systems Engineering | X | X |
| 1.3.1.2 | 4 | Assembly, Integration and Test | X | X |
| 1.3.1.3 | 4 | Program Management | X | X |
| 1.3.1.4 | 4 | Support Equipment | X | X |
| 1.3.2 | 3 | Ground Functions | ||
| 1.3.2.1 | 4 | SEIT/PM and Support Equipment | X | X |
| 1.3.2.2 | 4 | COTS Hardware | X | X |
| 1.3.2.3 | 4 | Custom Hardware | X | X |
| 1.3.2.4 | 4 | Ground Function Software | X | X |
| 1.3.2.5 | 4 | Pre-Operations Mission Support | X | X |
| 1.3.3 | 3 | Ground Terminal/Gateway (GT) (N/A to program) | X | X |
| 1.3.4 | 3 | External Network (T-COMM) (N/A to program) | X | X |
| 1.3.5 | 3 | User Equipment (N/A to program) | X | X |
| 1.3.6 | 3 | Facilities (N/A to program) | X | X |
| 1.3.7 | 3 | Vehicles and Shelters (N/A to program) | X | X |
| 1.4 | 2 | Orbital Transfer Vehicle (OTV) (N/A to program) | X | X |
| 1.5 | 2 | Launch Vehicle (N/A to program) | X | X |
| 1.6 | 2 | Insurance (N/A to program) | X | X |
| 1.7 | 2 | Task Order (N/A to program) | 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 |
&F &A FA8809-24-R-B001
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) | Contract Award | Initial | TBD | TBD | ||
| 2 | Technical Data Report | Contract Award | Initial | TBD | TBD | ||
| 3 | Technical Data Report | Annual Report 1 | Interim | TBD | TBD | ||
| 4 | Cost and Hour Report (FlexFile) | Annual Report 2 | Interim | TBD | TBD | ||
| 5 | Cost and Hour Report (FlexFile) | SV Launch | Interim | TBD | TBD | ||
| 6 | Technical Data Report | SV Launch | Final | TBD | TBD | ||
| 7 | Cost and Hour Report (FlexFile) | End of Ops Support | Final | TBD | TBD |
DRAFT DD FORM 2794 (PAGE 3), SUBMISSION EVENTS, JANUARY 2019 PREVIOUS EDITION IS OBSOLETE
&F &A FA8809-24-R-B001
DD Form 2794, Pg 4 (REMARKS)
| COST AND SOFTWARE DATA REPORTING PLAN |
| 15. REMARKS |
The contractor must report costs on all CLINs associated with the STEP 2.0 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.
SUBMISSIONS
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.
| Summary |
| Space System development (design-related) costs are generally nonrecurring in nature. When system components (e.g. space vehicles and ground stations) are produced, their costs are recurring. The purpose of this approach is to yield cost segregation that can be used as the basis for estimating the costs of replicating satellites and the ground stations (e.g. backups or redundancies) or portions thereof. |
This CSDR Contract plan is intended to capture costs associated with the contract number(s) listed in block 9.b. The contractor shall capture and report any and all costs incurred in order to perform the scopes of work on the Contract irrespective of contract type (e.g., firm-fixed price, cost-plus fixed fee) or funding source (i.e., via contract, via contractor internal research & development funds).
The definitions are intended for application to all levels of integration, or WBS indenture, within a space system: parts, materials and labor; hardware components, subassemblies, major assemblies and end items (“boxes”); and subsystems, system segments, and the system as a whole.
| General Definitions |
| Acquisition costs for development of the space 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. |
Acquisition costs for production of operational spacecraft, ground operations and processing centers (GOPCs), Ground Terminals (G/Ts), along with associated facilities and vehicles/shelters, 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.
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.
Nonrecurring (NRE) general examples which apply to hardware, software, facilities and O&S include: initial development of spacecraft, GOPCs, G/Ts and other system segments, elements, interfaces; support equipment used for development; software development; development of upgrades and improvements (despite magnitude);
Recurring (REC) general examples: Spacecraft production, assembly, integration and test; Ground hardware production and installation; Construction of operational ground facilities; installation of developed and COTS software in GOPCs and G/Ts; replicated space hardware in GOPCs and G/Ts; spares for spacecraft, GOPCs and G/Ts; test equipment, software and procedure maintenance; and system operation and maintenance
Note that: Launch Vehicle, Launch Support, External Network (T-COMM) costs are not specifically detailed here, although the definitions for space hardware, software and SEIT/PM (Systems Engineering, Assembly Integration and Test, and Program Management) should be applied to launch vehicles. Alternatively, the ground hardware definitions should be applied to launch bases, launch-related O&S, and for T-COMM. Dissemination of system products and data is only addressed to the extent that the required resources are defined to be included within the system boundaries (i.e., ground stations, system O&S). Costs for system concept development and technology development prior to full-scale development (i.e., prior to acquisition contract Authority to Proceed, or ATP) are usually considered to be nonrecurring. They are not addressed further in the definitions.
The software definitions apply to flight software, ground station operational software, development software, and ground test software for space vehicle development and production. Ground support equipment (GSE) is addressed within the space and ground station hardware sections below. It is usually treated separately from assembly, integration and test for cost collection and estimating purposes."
| Space Hardware Related Definitions |
| 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
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)"
| Ground Hardware Related Definitions |
| Nonrecurring Cost |
Requirements definition, engineering design & analysis
Development unit parts, materials, fabrication, assembly and tests
Engineering support for development unit fabrication, assembly & test
Redesign, rework & retest of development hardware due to design flaws Simulators and test equipment specifically for supporting development
Parts, materials, fabrication, assembly, installation and tests of all installed operational hardware
| Engineering support for fabrication, assembly, installation & test of operational hardware |
| Spare parts, materials and subassemblies and assemblies |
Rework, reinstallation and retest of operational hardware due to workmanship problems
| Simulators and test equipment for supporting system operation, or for both development and operation | |
| Software Related Definitions | |
| 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
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)"
| Systems Engineering Related Definitions |
| 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
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
| Assembly Integration & Test (AI&T) Related Definitions |
| 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
Space vehicle assembly, integration and acceptance testing
Acceptance test analysis and reports
Integration and test of previously-developed software –in GOPCs, G/Ts and follow-on Space
| Program Management Related Definitions |
| 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
Management activities applied to/associated with REC efforts"
| Expanded Ground Support Equipment Definitions |
| 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
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"
| FAC vs EAC |
| The checkmarks for EAC/FAC in column 12e at the WBS level shall be reported as "Forecast at Completion" (FAC). The Forecast At Completion (FAC) required here is not subject to the standards established in ANSI/EIA-748 guideline #27 (Estimate at Complete); therefore, the FAC does not need to be, but may be, derived from Industry Earned Value Management (EVM) processes. |
| IRAD EFFORT |
| The contractor should list the major relevant IRAD projects leveraged for this development effort, provide a brief description of the cost of the projects, and provide/attach any more detailed actual cost information at the level available. |
| WBS INDEX AND DICTIONARY |
| The WBS Dictionary is a living document and must match the technical content, cost content, and work content of each end item (see Block 17) for all WBS elements for each Cost and Hour (FlexFile) submission. The dictionary shall contain a disclosure statement detailing any differences between the CSDR reporting methodology and the reporting entity's Cost Accounting Standards. The dictionary shall include a section detailing how parts are procured under this contract and any limitations of the parts procurement cost data or allocation of cost data for the WBS element. |
The reporting entity must maintain and update the WBS Dictionary throughout the life of the contract, IAW DI-FNCL-82162, if changes to the WBS occur, the reporting entity shall annotate and track changes by adding the “As of Date” of the submitted FlexFile report and indicate the changes to the WBS Index and Dictionary Definitions.
For WBS elements identified in block 11 of the CSDR plan that is not within the contract's scope of work, the reporting entity shall report in the dictionary that “This CSDR WBS element is not associated with this contract’s scope of work”, and zero costs will be associated for ATD and FAC for these WBS elements.
| COST ACCOUNTING STANDARDS (CAS) DISCLOSURE STATEMENT DIFFERENCES |
| Describe significant accounting changes from previous accounting period in the Remarks section of the reports, if applicable. |
| END ITEMS/ORDER LOTS SCOPE IDIQ |
| Block 16 Orders/Lots is meant to capture the discrete Delivery Orders/Task Orders exercised on the contract. If a Delivery Order/Task Order is exercised on the contract and the CSDR plan has not been updated, it is the Reporting Entity's responsibility to still submit the dollars and hours in the FlexFile tagged to the appropriate Delivery Orders/Task Orders. The CSDR plan will be revised accordingly to include all exercised Delivery Orders/Task Orders. |
| COST AND HOUR REPORT UNIT/SUBLOT REPORTING |
| The Reporting Entity is required to provide unit or sublot (specify) reporting for any given Order/Lot and End Item as outlined in block 18 of the DD Form 2794. If Unit Reporting is selected in item 18c (Unit Reporting), it is expected that all touch labor costs and hours that are associated with the discrete units or sublots be tagged as Touch Manufacturing or Touch Maintenance as defined in Data Group E, Item 7. |
| QUANTITY REPORTING |
| a. If the quantity for a given element differs from the quantity reported for the full system, provide a comment in the WBS Element Remarks section. |
b. The Reporting Entity shall provide meaningful quantity information lower than the summary level in the remarks for WBS elements Peculiar Support Equipment, Common Support Equipment, and Initial Spares and Repair Parts, if applicable.
| 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. The intent of the FlexFile is to collect data through program FOC. If there are changes to the program schedule, the CSDR plan and deliverables will be revisited. |
| CSDR Readiness Review |
| The Reporting Entity shall attend and participate in a post award CSDR conference which will be held with the Cost Working Group Integrated Product Team (CWIPT) IAW DFARS 242.503-2(b) and DoDM 5000.04 (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 functional element codes will be populated. The review shall include any reporting issue corrections and identify proposed changes to the approved CSDR Plan as necessary. |
| 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. |
| 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. |
| TECHNICAL DATA REPORTING |
| Unique contractor format is acceptable as long as the attached technical data requirements are provided (see DD Form 2794; page 8 TECH RQTS) |
| Payload Suite Integration & Test |
| WBS is built out to accommodate more than what is likely to be the final number of payloads and integration activities. For WBS elements that are not applicable a response of N/A is acceptable. |
HERITAGE DEFINITIONS
When preparing the “Percent (%) New” parameters within the Technical Data Report deliverable, the contractor shall utilize the “Heritage New Design Calculator” available at the following URL:
https://cade.osd.mil/policy/techdata
The Heritage New Design Calculator is a Government developed calculator, which facilitates a concise method to approximate the percent of new design for a payload and spacecraft bus. The contractor must review the questions within column F and mark column E either “y” for “Yes” or “n” for “No” within the associated column E of the Excel worksheet. After entering “y” or “n” between rows 4 and 16 of the calculator, cell E18 will report the “Percent (%) New” parameter, which shall be used to populate the Technical Data Report deliverable. If the prime contractor is unable to answer the questions since it is procuring the payload or spacecraft bus, the subcontractor shall be required to provide the “Percent (%) New” data directly to the Government (contact the Procuring Contracting Officer for additional directions if a subcontractor is reporting the required “Percent (%) New” value).
| MINIMUM TASK ORDER AWARD |
| In the event that a the reporting entity has been awarded a minimum Task Order, the CSDR requirements will not be required. |
DRAFT DD FORM 2794 (PAGE 4), REMARKS, JANUARY 2019 PREVIOUS EDITION IS OBSOLETE
&F &A FA8809-24-R-B001
DD Form 2794, Pg 6 (SRDR DEV)
| COST AND SOFTWARE DATA REPORTING PLAN - SRDR DEVELOPMENT | ||
| 19. RELEASES | ||
| a. ID | b. NAME | c. DATE |
a. ID b. NAME
| 21. PRODUCT SIZE REPORTING ELEMENTS | |||
| a. CODE | b. NAME | c. RELEASE ID | d. CSCI ID |
| 22. PRODUCT SIZE SUBMISSIONS | c. RELEASE ID: | 1 | 2 | 3 | 4 | |
| a. NUMBER | b. NAME | Included? | Included? | Included? | Included? |
DRAFT DD FORM 2794 (PAGE 6), SRDR DEVELOPMENT, JANUARY 2019
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 | Task Order 1…n | B |
| 17. END ITEMS | |
| a. ID | b. NAME |
| 1 | STPSat-8 ...STPSat-n |
| 18. OPTIONAL REQUIREMENTS | ||||
| 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
&F &A FA8809-24-R-B001
DD Form 2794, Pg 8 (TECH RQTS)
| COST AND SOFTWARE DATA REPORTING PLAN - TECHNICAL PARAMETER REQUIREMENTS | ||||||||||
| TECHNICAL PARAMETER REQUIREMENTS | ||||||||||
| 26. WBS | ||||||||||
| ELEMENT CODE | 27. WBS ELEMENT NAME | 28. ITEM TYPE | 29. TECHNICAL PARAMETER | |||||||
| a. PARAMETER NAME | b. UNIT OF MEASURE | c. UNIT OF MEASURE QUALIFIER | d. REPEATABLE | e. REMARKS | ||||||
| 1.0 | Space System | ProgramDates | Contract Award Date | Date | ||||||
| 1.0 | Space System | ProgramDates | Authority to Proceed (ATP) Date | Date | ||||||
| 1.0 | Space System | ProgramDates | Preliminary Design Review (PDR) Date | Date | ||||||
| 1.0 | Space System | ProgramDates | Critical Design Review (CDR) Date | Date | ||||||
| 1.0 | Space System | ProgramDates | Bus Complete Date | Date | ||||||
| 1.0 | Space System | ProgramDates | Available for Launch (AFL) Date | Date | ||||||
| 1.0 | Space System | ProgramDates | Transfer to Launch Processing Facility Date | Date | ||||||
| 1.0 | Space System | ProgramDates | Launch Date | Date | ||||||
| 1.0 | Space System | SpaceSys | Design Life | Months | ||||||
| 1.0 | Space System | SpaceSys | Mean Mission Duration (MMD) | Years | ||||||
| 1.0 | Space System | SpaceSys | Orbit Regime | List | ||||||
| 1.0 | Space System | SpaceSys | Orbit Altitude | Kilometers | ||||||
| 1.0 | Space System | SpaceSys | Orbit Inclination | Degrees Angular | ||||||
| 1.0 | Space System | SpaceSys | Contract Type | List | ||||||
| 1.2 | Space Vehicle | SpaceVehicle | Power - Beginning of Life (BOL) | Watts | ||||||
| 1.2 | Space Vehicle | SpaceVehicle | Average Day Power (EOL) | Watts | ||||||
| 1.2 | Space Vehicle | SpaceVehicle | Delta-V | Meters per Second | ||||||
| 1.2 | Space Vehicle | PhysicalStrucDry | Dry Weight - Basic | Pounds | ||||||
| 1.2 | Space Vehicle | PhysicalStrucDry | Dry Weight - Growth Allowance | Pounds | ||||||
| 1.2 | Space Vehicle | PhysicalStrucDry | Dry Weight - Including Growth Allowance | Pounds | ||||||
| 1.2 | Space Vehicle | PhysicalStrucWet | Wet Weight - Basic | Pounds | ||||||
| 1.2 | Space Vehicle | PhysicalStrucWet | Wet Weight - Growth Allowance | Pounds | ||||||
| 1.2 | Space Vehicle | PhysicalStrucWet | Wet Weight - Including Growth Allowance | Pounds | ||||||
| 1.2.2 | Bus | Bus | Bus Model | Descriptor | ||||||
| 1.2.2 | Bus | Bus | Flight Heritage | Descriptor | ||||||
| 1.2.2 | Bus | Bus | Voltage - Bus | Volts | Bus Level | |||||
| 1.2.2 | Bus | PhysicalStrucDry | Dry Weight - Basic | Pounds | ||||||
| 1.2.2 | Bus | PhysicalStrucDry | Dry Weight - Growth Allowance | Pounds | ||||||
| 1.2.2 | Bus | PhysicalStrucDry | Dry Weight - Including Growth Allowance | Pounds | ||||||
| 1.2.2 | Bus | PhysicalStrucWet | Wet Weight - Basic | Pounds | ||||||
| 1.2.2 | Bus | PhysicalStrucWet | Wet Weight - Growth Allowance | Pounds | ||||||
| 1.2.2 | Bus | PhysicalStrucWet | Wet Weight - Including Growth Allowance | Pounds | ||||||
| 1.2.2.2 | Structures and Mechanisms (SMS) | PhysicalOther | Material Mix 1…n | Percent of Total Weight | Material Name | Y | ||||
| 1.2.2.2 | Structures and Mechanisms (SMS) | PhysicalStrucDry | Dry Weight - Basic | Pounds | ||||||
| 1.2.2.2 | Structures and Mechanisms (SMS) | PhysicalStrucDry | Dry Weight - Growth Allowance | Pounds | ||||||
| 1.2.2.2 | Structures and Mechanisms (SMS) | PhysicalStrucDry | Dry Weight - Including Growth Allowance | Pounds | ||||||
| 1.2.2.2 | Structures and Mechanisms (SMS) | Heritage | New Design | Percent | ||||||
| 1.2.2.3 | Thermal Control (TCS) | PhysicalStrucDry | Dry Weight - Basic | Pounds | ||||||
| 1.2.2.3 | Thermal Control (TCS) | PhysicalStrucDry | Dry Weight - Growth Allowance | Pounds | ||||||
| 1.2.2.3 | Thermal Control (TCS) | PhysicalStrucDry | Dry Weight - Including Growth Allowance | Pounds | ||||||
| 1.2.2.3 | Thermal Control (TCS) | Heritage | New Design | Percent | ||||||
| 1.2.2.4 | Electrical Power (EPS) | EPSSpace | Power - Beginning of Life (BOL) | Watts | ||||||
| 1.2.2.4 | Electrical Power (EPS) | EPSSpace | Power - End of Life (EOL) | Watts | ||||||
| 1.2.2.4 | Electrical Power (EPS) | EPSSpace | Number of Solar Array Panels | Quantity | Panels | |||||
| 1.2.2.4 | Electrical Power (EPS) | EPSSpace | Solar Array Config | List | ||||||
| 1.2.2.4 | Electrical Power (EPS) | EPSSpace | Solar Array Incidence Angle | Degrees | ||||||
| 1.2.2.4 | Electrical Power (EPS) | EPSSpace | Solar Array Area | Square Meters | ||||||
| 1.2.2.4 | Electrical Power (EPS) | EPSSpace | Articulated Solar Arrays | List | ||||||
| 1.2.2.4 | Electrical Power (EPS) | EPSSpace | Power Consumption | Watts | ||||||
| 1.2.2.4 | Electrical Power (EPS) | EPSSpace | Solar Cell Area | Square Meters | ||||||
| 1.2.2.4 | Electrical Power (EPS) | EPSSpace | Solar Cell Type | List | ||||||
| 1.2.2.4 | Electrical Power (EPS) | Battery | Battery Capacity | Ampere Hours | ||||||
| 1.2.2.4 | Electrical Power (EPS) | Battery | Output Voltage | Volts | ||||||
| 1.2.2.4 | Electrical Power (EPS) | Battery | Type of Battery | List | ||||||
| 1.2.2.4 | Electrical Power (EPS) | Battery | Number of Battery Cells | Quantity | Cells | |||||
| 1.2.2.4 | Electrical Power (EPS) | PhysicalStrucDry | Dry Weight - Basic | Pounds | ||||||
| 1.2.2.4 | Electrical Power (EPS) | PhysicalStrucDry | Dry Weight - Growth Allowance | Pounds | ||||||
| 1.2.2.4 | Electrical Power (EPS) | PhysicalStrucDry | Dry Weight - Including Growth Allowance | Pounds | ||||||
| 1.2.2.4 | Electrical Power (EPS) | Heritage | New Design | Percent | ||||||
| 1.2.2.5 | Attitude Control Subsystem (ACS) | ACS | Pointing Accuracy | Degrees Angular | Bus Level | |||||
| 1.2.2.5 | Attitude Control Subsystem (ACS) | ACS | Number of ADCS Sensors | Quantity | Sensors | |||||
| 1.2.2.5 | Attitude Control Subsystem (ACS) | PhysicalStrucDry | Dry Weight - Basic | Pounds | ||||||
| 1.2.2.5 | Attitude Control Subsystem (ACS) | PhysicalStrucDry | Dry Weight - Growth Allowance | Pounds | ||||||
| 1.2.2.5 | Attitude Control Subsystem (ACS) | PhysicalStrucDry | Dry Weight - Including Growth Allowance | Pounds | ||||||
| 1.2.2.5 | Attitude Control Subsystem (ACS) | Heritage | New Design | Percent | ||||||
| 1.2.2.6 | Propulsion Subsystem | Tanks | Propellant Type | Descriptor | YG | |||||
| 1.2.2.6 | Propulsion Subsystem | PhysicalStrucDry | Dry Weight - Basic | Pounds | ||||||
| 1.2.2.6 | Propulsion Subsystem | PhysicalStrucDry | Dry Weight - Growth Allowance | Pounds | ||||||
| 1.2.2.6 | Propulsion Subsystem | PhysicalStrucDry | Dry Weight - Including Growth Allowance | Pounds | ||||||
| 1.2.2.6 | Propulsion Subsystem | Heritage | New Design | Percent | ||||||
| 1.2.2.7 | Telemetry, Tracking, and Command Subsystem (TT&C) | TTandC | Band | List | ||||||
| 1.2.2.7 | Telemetry, Tracking, and Command Subsystem (TT&C) | TTandC | Bandwidth Crosslink | Megahertz | ||||||
| 1.2.2.7 | Telemetry, Tracking, and Command Subsystem (TT&C) | TTandC | Bandwidth Downlink | Megahertz | ||||||
| 1.2.2.7 | Telemetry, Tracking, and Command Subsystem (TT&C) | TTandC | Bandwidth Uplink | Megahertz | ||||||
| 1.2.2.7 | Telemetry, Tracking, and Command Subsystem (TT&C) | TTandC | Communication Band Type | List | ||||||
| 1.2.2.7 | Telemetry, Tracking, and Command Subsystem (TT&C) | TTandC | Data Rate Average Crosslink | Kilobits per Second | ||||||
| 1.2.2.7 | Telemetry, Tracking, and Command Subsystem (TT&C) | TTandC | Data Rate Average Downlink | Kilobits per Second | ||||||
| 1.2.2.7 | Telemetry, Tracking, and Command Subsystem (TT&C) | TTandC | Data Rate Average Uplink | Kilobits per Second | ||||||
| 1.2.2.7 | Telemetry, Tracking, and Command Subsystem (TT&C) | TTandC | Data Rate Maximum Crosslink | Kilobits per Second | ||||||
| 1.2.2.7 | Telemetry, Tracking, and Command Subsystem (TT&C) | TTandC | Data Rate Maximum Downlink | Kilobits per Second | ||||||
| 1.2.2.7 | Telemetry, Tracking, and Command Subsystem (TT&C) | TTandC | Data Rate Maximum Uplink | Kilobits per Second | ||||||
| 1.2.2.7 | Telemetry, Tracking, and Command Subsystem (TT&C) | TTandC | TT&C Standard | Descriptor | ||||||
| 1.2.2.7 | Telemetry, Tracking, and Command Subsystem (TT&C) | PhysicalStrucDry | Dry Weight - Basic | Pounds | ||||||
| 1.2.2.7 | Telemetry, Tracking, and Command Subsystem (TT&C) | PhysicalStrucDry | Dry Weight - Growth Allowance | Pounds | ||||||
| 1.2.2.7 | Telemetry, Tracking, and Command Subsystem (TT&C) | PhysicalStrucDry | Dry Weight - Including Growth Allowance | Pounds | ||||||
| 1.2.2.7 | Telemetry, Tracking, and Command Subsystem (TT&C) | Heritage | New Design | Percent | ||||||
| 1.2.2.8 | Bus Flight Software | SoftwareNonSRDR | Product Size - Delivered | SLOC | ||||||
| 1.2.2.8 | Bus Flight Software | SoftwareNonSRDR | Product Size - Effective | SLOC | ||||||
| 1.2.2.8 | Bus Flight Software | SoftwareNonSRDR | ESLOC Equation | Descriptor | ||||||
| 1.2.2.8 | Bus Flight Software | SoftwareNonSRDR | New Code | SLOC | ||||||
| 1.2.2.8 | Bus Flight Software | SoftwareNonSRDR | Modified Code | SLOC | ||||||
| 1.2.2.8 | Bus Flight Software | SoftwareNonSRDR | Reused Code | SLOC | ||||||
| 1.2.2.8 | Bus Flight Software | SoftwareNonSRDR | Carryover Code | SLOC | ||||||
| 1.2.2.8 | Bus Flight Software | SoftwareNonSRDR | Auto-generated code | SLOC | ||||||
| 1.2.2.8 | Bus Flight Software | SoftwareNonSRDR | Development Process | Descriptor | ||||||
| 1.2.2.8 | Bus Flight Software | SoftwareNonSRDR | Language | Descriptor | ||||||
| 1.2.3 | Payload Suite Integration & Test | PhysicalStrucDry | Dry Weight - Basic | Pounds | ||||||
| 1.2.3 | Payload Suite Integration & Test | PhysicalStrucDry | Dry Weight - Growth Allowance | Pounds | ||||||
| 1.2.3 | Payload Suite Integration & Test | PhysicalStrucDry | Dry Weight - Including Growth Allowance | Pounds | ||||||
| 1.2.3 | Payload Suite Integration & Test | PhysicalStrucWet | Wet Weight - Basic | Pounds | ||||||
| 1.2.3 | Payload Suite Integration & Test | PhysicalStrucWet | Wet Weight - Growth Allowance | Pounds | ||||||
| 1.2.3 | Payload Suite Integration & Test | PhysicalStrucWet | Wet Weight - Including Growth Allowance | Pounds | ||||||
| 1.2.3.2.1.1 | Inter-Port AI&T #1 | PayloadInterPort | Number of Inter-Port Connected Payloads | Count | ||||||
| 1.2.3.2.1.1 | Inter-Port AI&T #1 | PayloadInterPort | Connected Port IDs | Descriptor | ||||||
| 1.2.3.2.1.1 | Inter-Port AI&T #1 | PayloadInterPort | Connected Payloads Names | Descriptor | ||||||
| 1.2.3.2.1.1 | Inter-Port AI&T #1 | PayloadInterPort | Inter-Port Unique Weight | Pounds | ||||||
| 1.2.3.2.1.2 | Inter-Port AI&T #n | PayloadInterPort | Number of Inter-Port Connected Payloads | Count | ||||||
| 1.2.3.2.1.2 | Inter-Port AI&T #n | PayloadInterPort | Connected Port IDs | Descriptor | ||||||
| 1.2.3.2.1.2 | Inter-Port AI&T #n | PayloadInterPort | Connected Payloads Names | Descriptor | ||||||
| 1.2.3.2.1.2 | Inter-Port AI&T #n | PayloadInterPort | Inter-Port Unique Weight | Pounds | ||||||
| 1.2.3.2.1.3 | Inter-Port AI&T #3 | PayloadInterPort | Number of Inter-Port Connected Payloads | Count | ||||||
| 1.2.3.2.1.3 | Inter-Port AI&T #3 | PayloadInterPort | Connected Port IDs | Descriptor | ||||||
| 1.2.3.2.1.3 | Inter-Port AI&T #3 | PayloadInterPort | Connected Payloads Names | Descriptor | ||||||
| 1.2.3.2.1.3 | Inter-Port AI&T #3 | PayloadInterPort | Inter-Port Unique Weight | Pounds | ||||||
| 1.2.3.2.1.4 | Inter-Port AI&T #4 | PayloadInterPort | Number of Inter-Port Connected Payloads | Count | ||||||
| 1.2.3.2.1.4 | Inter-Port AI&T #4 | PayloadInterPort | Connected Port IDs | Descriptor | ||||||
| 1.2.3.2.1.4 | Inter-Port AI&T #4 | PayloadInterPort | Connected Payloads Names | Descriptor | ||||||
| 1.2.3.2.1.4 | Inter-Port AI&T #4 | PayloadInterPort | Inter-Port Unique Weight | Pounds | ||||||
| 1.2.3.2.1.5 | Inter-Port AI&T #5 | PayloadInterPort | Number of Inter-Port Connected Payloads | Count | ||||||
| 1.2.3.2.1.5 | Inter-Port AI&T #5 | PayloadInterPort | Connected Port IDs | Descriptor | ||||||
| 1.2.3.2.1.5 | Inter-Port AI&T #5 | PayloadInterPort | Connected Payloads Names | Descriptor | ||||||
| 1.2.3.2.1.5 | Inter-Port AI&T #5 | PayloadInterPort | Inter-Port Unique Weight | Pounds | ||||||
| 1.2.3.2.1.6 | Inter-Port AI&T #6 | PayloadInterPort | Number of Inter-Port Connected Payloads | Count | ||||||
| 1.2.3.2.1.6 | Inter-Port AI&T #6 | PayloadInterPort | Connected Port IDs | Descriptor | ||||||
| 1.2.3.2.1.6 | Inter-Port AI&T #6 | PayloadInterPort | Connected Payloads Names | Descriptor | ||||||
| 1.2.3.2.1.6 | Inter-Port AI&T #6 | PayloadInterPort | Inter-Port Unique Weight | Pounds | ||||||
| 1.2.3.2.2.1 | Multi-Payload Intra-Port AI&T #1 | PayloadIntraPort | Port ID | List | ||||||
| 1.2.3.2.2.1 | Multi-Payload Intra-Port AI&T #1 | PayloadIntraPort | Number of Payloads on Port | Count | ||||||
| 1.2.3.2.2.1 | Multi-Payload Intra-Port AI&T #1 | PayloadIntraPort | Payload Names | Descriptor | ||||||
| 1.2.3.2.2.1 | Multi-Payload Intra-Port AI&T #1 | PayloadIntraPort | Intra-Port Unique Weight | Pounds | ||||||
| 1.2.3.2.2.2 | Multi-Payload Intra-Port AI&T #n | PayloadIntraPort | Port ID | List | ||||||
| 1.2.3.2.2.2 | Multi-Payload Intra-Port AI&T #n | PayloadIntraPort | Number of Payloads on Port | Count | ||||||
| 1.2.3.2.2.2 | Multi-Payload Intra-Port AI&T #n | PayloadIntraPort | Payload Names | Descriptor | ||||||
| 1.2.3.2.2.2 | Multi-Payload Intra-Port AI&T #n | PayloadIntraPort | Intra-Port Unique Weight | Pounds | ||||||
| 1.2.3.2.2.3 | Multi-Payload Intra-Port AI&T #3 | PayloadIntraPort | Port ID | List | ||||||
| 1.2.3.2.2.3 | Multi-Payload Intra-Port AI&T #3 | PayloadIntraPort | Number of Payloads on Port | Count | ||||||
| 1.2.3.2.2.3 | Multi-Payload Intra-Port AI&T #3 | PayloadIntraPort | Payload Names | Descriptor | ||||||
| 1.2.3.2.2.3 | Multi-Payload Intra-Port AI&T #3 | PayloadIntraPort | Intra-Port Unique Weight | Pounds | ||||||
| 1.2.3.2.2.4 | Multi-Payload Intra-Port AI&T #4 | PayloadIntraPort | Port ID | List | ||||||
| 1.2.3.2.2.4 | Multi-Payload Intra-Port AI&T #4 | PayloadIntraPort | Number of Payloads on Port | Count | ||||||
| 1.2.3.2.2.4 | Multi-Payload Intra-Port AI&T #4 | PayloadIntraPort | Payload Names | Descriptor | ||||||
| 1.2.3.2.2.4 | Multi-Payload Intra-Port AI&T #4 | PayloadIntraPort | Intra-Port Unique Weight | Pounds | ||||||
| 1.2.3.2.2.5 | Multi-Payload Intra-Port AI&T #5 | PayloadIntraPort | Port ID | List | ||||||
| 1.2.3.2.2.5 | Multi-Payload Intra-Port AI&T #5 | PayloadIntraPort | Number of Payloads on Port | Count | ||||||
| 1.2.3.2.2.5 | Multi-Payload Intra-Port AI&T #5 | PayloadIntraPort | Payload Names | Descriptor | ||||||
| 1.2.3.2.2.5 | Multi-Payload Intra-Port AI&T #5 | PayloadIntraPort | Intra-Port Unique Weight | Pounds | ||||||
| 1.2.3.2.2.6 | Multi-Payload Intra-Port AI&T #6 | PayloadIntraPort | Port ID | List | ||||||
| 1.2.3.2.2.6 | Multi-Payload Intra-Port AI&T #6 | PayloadIntraPort | Number of Payloads on Port | Count | ||||||
| 1.2.3.2.2.6 | Multi-Payload Intra-Port AI&T #6 | PayloadIntraPort | Payload Names | Descriptor | ||||||
| 1.2.3.2.2.6 | Multi-Payload Intra-Port AI&T #6 | PayloadIntraPort | Intra-Port Unique Weight | Pounds | ||||||
| 1.2.3.2.3.1 | Payload #1 I&T | PayloadUnique | Payload Name | Descriptor | ||||||
| 1.2.3.2.3.1 | Payload #1 I&T | PayloadUnique | Hosted or Separable Payload | List | ||||||
| 1.2.3.2.3.1 | Payload #1 I&T | PayloadUnique | Port ID | List | ||||||
| 1.2.3.2.3.1 | Payload #1 I&T | PayloadUnique | Manifest Date | Date | ||||||
| 1.2.3.2.3.1 | Payload #1 I&T | PayloadUnique | De-Manifest Date | Date | ||||||
| 1.2.3.2.3.1 | Payload #1 I&T | PayloadUnique | Re-Manifest Date | Date | ||||||
| 1.2.3.2.3.1 | Payload #1 I&T | PayloadUnique | Launch with Mass Model | List | ||||||
| 1.2.3.2.3.1 | Payload #1 I&T | PayloadUnique | Payload Volume | Cubic Inches | ||||||
| 1.2.3.2.3.1 | Payload #1 I&T | PayloadUnique | Payload Total Weight | Pounds | ||||||
| 1.2.3.2.3.1 | Payload #1 I&T | PayloadUnique | Payload Weight - Wet | Pounds | ||||||
| 1.2.3.2.3.1 | Payload #1 I&T | PayloadUnique | Payload Weight - Dry | Pounds | ||||||
| 1.2.3.2.3.1 | Payload #1 I&T | PayloadUnique | Power - Maximum Consumption Rate | Watts | ||||||
| 1.2.3.2.3.1 | Payload #1 I&T | PayloadUnique | Power - Average Usage | Watts | ||||||
| 1.2.3.2.3.1 | Payload #1 I&T | PayloadUnique | Power - Input | Watts | ||||||
| 1.2.3.2.3.1 | Payload #1 I&T | PayloadUnique | Provided Items | Descriptor | ||||||
| 1.2.3.2.3.1 | Payload #1 I&T | PayloadUnique | Unique Payload Items | Descriptor | ||||||
| 1.2.3.2.3.1 | Payload #1 I&T | PayloadUnique | Payload Clarification Details | Descriptor | ||||||
| 1.2.3.2.3.2 | Payload #n I&T | PayloadUnique | Payload Name | Descriptor | ||||||
| 1.2.3.2.3.2 | Payload #n I&T | PayloadUnique | Hosted or Separable Payload | List | ||||||
| 1.2.3.2.3.2 | Payload #n I&T | PayloadUnique | Port ID | List | ||||||
| 1.2.3.2.3.2 | Payload #n I&T | PayloadUnique | Manifest Date | Date | ||||||
| 1.2.3.2.3.2 | Payload #n I&T | PayloadUnique | De-Manifest Date | Date | ||||||
| 1.2.3.2.3.2 | Payload #n I&T | PayloadUnique | Re-Manifest Date | Date | ||||||
| 1.2.3.2.3.2 | Payload #n I&T | PayloadUnique | Launch with Mass Model | List | ||||||
| 1.2.3.2.3.2 | Payload #n I&T | PayloadUnique | Payload Volume | Cubic Inches | ||||||
| 1.2.3.2.3.2 | Payload #n I&T | PayloadUnique | Payload Total Weight | Pounds | ||||||
| 1.2.3.2.3.2 | Payload #n I&T | PayloadUnique | Payload Weight - Wet | Pounds | ||||||
| 1.2.3.2.3.2 | Payload #n I&T | PayloadUnique | Payload Weight - Dry | Pounds | ||||||
| 1.2.3.2.3.2 | Payload #n I&T | PayloadUnique | Power - Maximum Consumption Rate | Watts | ||||||
| 1.2.3.2.3.2 | Payload #n I&T | PayloadUnique | Power - Average Usage | Watts | ||||||
| 1.2.3.2.3.2 | Payload #n I&T | PayloadUnique | Power - Input | Watts | ||||||
| 1.2.3.2.3.2 | Payload #n I&T | PayloadUnique | Provided Items | Descriptor | ||||||
| 1.2.3.2.3.2 | Payload #n I&T | PayloadUnique | Unique Payload Items | Descriptor | ||||||
| 1.2.3.2.3.2 | Payload #n I&T | PayloadUnique | Payload Clarification Details | Descriptor | ||||||
| 1.2.3.2.3.3 | Payload #3 I&T | PayloadUnique | Payload Name | Descriptor | ||||||
| 1.2.3.2.3.3 | Payload #3 I&T | PayloadUnique | Hosted or Separable Payload | List | ||||||
| 1.2.3.2.3.3 | Payload #3 I&T | PayloadUnique | Port ID | List | ||||||
| 1.2.3.2.3.3 | Payload #3 I&T | PayloadUnique | Manifest Date | Date | ||||||
| 1.2.3.2.3.3 | Payload #3 I&T | PayloadUnique | De-Manifest Date | Date | ||||||
| 1.2.3.2.3.3 | Payload #3 I&T | PayloadUnique | Re-Manifest Date | Date | ||||||
| 1.2.3.2.3.3 | Payload #3 I&T | PayloadUnique | Launch with Mass Model | List | ||||||
| 1.2.3.2.3.3 | Payload #3 I&T | PayloadUnique | Payload Volume | Cubic Inches | ||||||
| 1.2.3.2.3.3 | Payload #3 I&T | PayloadUnique | Payload Total Weight | Pounds | ||||||
| 1.2.3.2.3.3 | Payload #3 I&T | PayloadUnique | Payload Weight - Wet | Pounds | ||||||
| 1.2.3.2.3.3 | Payload #3 I&T | PayloadUnique | Payload Weight - Dry | Pounds | ||||||
| 1.2.3.2.3.3 | Payload #3 I&T | PayloadUnique | Power - Maximum Consumption Rate | Watts | ||||||
| 1.2.3.2.3.3 | Payload #3 I&T | PayloadUnique | Power - Average Usage | Watts | ||||||
| 1.2.3.2.3.3 | Payload #3 I&T | PayloadUnique | Power - Input | Watts | ||||||
| 1.2.3.2.3.3 | Payload #3 I&T | PayloadUnique | Provided Items | Descriptor | ||||||
| 1.2.3.2.3.3 | Payload #3 I&T | PayloadUnique | Unique Payload Items | Descriptor | ||||||
| 1.2.3.2.3.3 | Payload #3 I&T | PayloadUnique | Payload Clarification Details | Descriptor | ||||||
| 1.2.3.2.3.4 | Payload #4 I&T | PayloadUnique | Payload Name | Descriptor | ||||||
| 1.2.3.2.3.4 | Payload #4 I&T | PayloadUnique | Hosted or Separable Payload | List | ||||||
| 1.2.3.2.3.4 | Payload #4 I&T | PayloadUnique | Port ID | List | ||||||
| 1.2.3.2.3.4 | Payload #4 I&T | PayloadUnique | Manifest Date | Date | ||||||
| 1.2.3.2.3.4 | Payload #4 I&T | PayloadUnique | De-Manifest Date | Date | ||||||
| 1.2.3.2.3.4 | Payload #4 I&T | PayloadUnique | Re-Manifest Date | Date | ||||||
| 1.2.3.2.3.4 | Payload #4 I&T | PayloadUnique | Launch with Mass Model | List | ||||||
| 1.2.3.2.3.4 | Payload #4 I&T | PayloadUnique | Payload Volume | Cubic Inches | ||||||
| 1.2.3.2.3.4 | Payload #4 I&T | PayloadUnique | Payload Total Weight | Pounds | ||||||
| 1.2.3.2.3.4 | Payload #4 I&T | PayloadUnique | Payload Weight - Wet | Pounds | ||||||
| 1.2.3.2.3.4 | Payload #4 I&T | PayloadUnique | Payload Weight - Dry | Pounds | ||||||
| 1.2.3.2.3.4 | Payload #4 I&T | PayloadUnique | Power - Maximum Consumption Rate | Watts | ||||||
| 1.2.3.2.3.4 | Payload #4 I&T | PayloadUnique | Power - Average Usage | Watts | ||||||
| 1.2.3.2.3.4 | Payload #4 I&T | PayloadUnique | Power - Input | Watts | ||||||
| 1.2.3.2.3.4 | Payload #4 I&T | PayloadUnique | Provided Items | Descriptor | ||||||
| 1.2.3.2.3.4 | Payload #4 I&T | PayloadUnique | Unique Payload Items | Descriptor | ||||||
| 1.2.3.2.3.4 | Payload #4 I&T | PayloadUnique | Payload Clarification Details | Descriptor | ||||||
| 1.2.3.2.3.5 | Payload #5 I&T | PayloadUnique | Payload Name | Descriptor | ||||||
| 1.2.3.2.3.5 | Payload #5 I&T | PayloadUnique | Hosted or Separable Payload | List | ||||||
| 1.2.3.2.3.5 | Payload #5 I&T | PayloadUnique | Port ID | List | ||||||
| 1.2.3.2.3.5 | Payload #5 I&T | PayloadUnique | Manifest Date | Date | ||||||
| 1.2.3.2.3.5 | Payload #5 I&T | PayloadUnique | De-Manifest Date | Date | ||||||
| 1.2.3.2.3.5 | Payload #5 I&T | PayloadUnique | Re-Manifest Date | Date | ||||||
| 1.2.3.2.3.5 | Payload #5 I&T | PayloadUnique | Launch with Mass Model | List | ||||||
| 1.2.3.2.3.5 | Payload #5 I&T | PayloadUnique | Payload Volume | Cubic Inches | ||||||
| 1.2.3.2.3.5 | Payload #5 I&T | PayloadUnique | Payload Total Weight | Pounds | ||||||
| 1.2.3.2.3.5 | Payload #5 I&T | PayloadUnique | Payload Weight - Wet | Pounds | ||||||
| 1.2.3.2.3.5 | Payload #5 I&T | PayloadUnique | Payload Weight - Dry | Pounds | ||||||
| 1.2.3.2.3.5 | Payload #5 I&T | PayloadUnique | Power - Maximum Consumption Rate | Watts | ||||||
| 1.2.3.2.3.5 | Payload #5 I&T | PayloadUnique | Power - Average Usage | Watts | ||||||
| 1.2.3.2.3.5 | Payload #5 I&T | PayloadUnique | Power - Input | Watts |
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 .