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

Other files attached to RFP - Space Test Experiments Platform (STEP) 2. 0, newest first.
File Type Posted
Questions_Answers_Step2.0_28June24v2.pdf PDF
ATTACHMENT 9 - IDIQ SECTION L INSTRUCTIONS FOR PROPOSAL_v2.pdf PDF
Questions_Answers_Step2_28June24v2.pdf PDF
STEP 2.0_IDIQ_Section Jv2.pdf PDF
Questions_Answers_13Jun24.pdf PDF
Attachment 17 SF328-18b.pdf PDF
Solicitation FA880924RB0010001.pdf PDF
ATTACHMENT 12 Gateway Questionnaire_Response Form v2.pdf PDF
Attachment 13 Prior Customer Questionnaire v2.pdf PDF
Vendor_Registration.pdf PDF
ATTACHMENT 10 IDIQ SECTION M EVALUATION FACTORS.pdf PDF
Attachment 19 Acronym List.pdf PDF
FA880924RB001 RFP STEP 2.pdf PDF
Attachment 2 Systems Requirement Document (SRD) (3).pdf PDF
ATTACHMENT 5 Ordering Guide.pdf PDF
Attachment 15 IDIQ_CDRL Table.pdf PDF
Solicitation - FA880924RB001Final.pdf PDF
Attachment 4 DD254 FA880924RB001.pdf PDF
ATTACHMENT 9 - IDIQ SECTION L INSTRUCTIONS FOR PROPOSAL.pdf PDF
Attachment 12 Gateway Questionnaire_Response Form.pdf PDF
Attachment 13 Prior Customer Questionnaire.pdf PDF
Attachment 17 SF328-18b.pdf PDF
Attachment 20 Compliance-Reference Table.pdf PDF
Attachment 7 IDIQ_OCI Checklist.pdf PDF
Attachment 1 Statement of Work (SOW).pdf PDF
Attachment 3 Spacecraft and Ground Technical Specification Sheet (SGTSS).pdf PDF
Attachment 6 ON OFF RAMPING PROC.pdf PDF
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 PLANOMB 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
XB
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
XOther
2. COMMODITY TYPE
Space System
3. PLAN ITERATION TYPE
XINITIAL
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
XCONTRACT (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)
XRDT&E
XPROCUREMENT
O&M
FMS
WCF
OTHER
10a. APPROVED PLAN NUMBER
AF-22-G1
10b. APPROVED PLAN REVISION NUMBER
10c. APPROVED PLAN REQUIREMENTS
XAT COMPLETION COSTS FOR STANDARD FUNCTIONAL CATEGORIES (FlexFile or Legacy)
XAT COMPLETION COSTS FOR RECURRING/NONRECURRING (FlexFile only)
XTECHNICAL DATA REQUIRED
10d. COST REPORT TYPE
XFLEXFILE
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 PLANCOST, SOFTWARE, & TECHNICAL DATA REPORTING/EARNED VALUE MANAGEMENT CO-PLAN
11. WORK BREAKDOWN STRUCTURE (WBS)12. COST13. TECHNICAL DATA
a. WBS
CODEb. WBS
LEVELc. WBS ELEMENT NAMEa. ACTUALS TO
DATE (ATD)b. LEGACY
1921-1c. LEGACY
1921-2d. LEGACY
1921-5e. EAC/FAC
(See item 10d)a. QUANTITYb. SRDR
FORMATSc.

MAINT. &

REPAIR

PARTS

i. QUANTITY
DATAii. GFE

QUANTITY

1.01STEP 2.0
1.12SEIT/PM and Support Equipment
1.1.13Systems EngineeringXX
1.1.23System Test and Evaluation
1.1.2.14Developmental Test and EvaluationXX
1.1.2.24Operational Test and EvaluationXX
1.1.2.34Mockups/System Integration Labs (SILs)XX
1.1.2.44Test and Evaluation SupportXX
1.1.2.54Test FacilitiesXX
1.1.33Assembly, Integration and TestXX
1.1.43Program ManagementXX
1.1.53Support EquipmentXX
1.22Space Vehicle
1.2.13SEIT/PM and Support Equipment
1.2.1.14Systems EngineeringXX
1.2.1.24Assembly, Integration and TestXX
1.2.1.34Program ManagementXX
1.2.1.44Support EquipmentXX
1.2.23Bus
1.2.2.14SEIT/PM and Support Equipment
1.2.2.1.15Systems EngineeringXX
1.2.2.1.25Assembly, Integration and TestXX
1.2.2.1.35Program ManagementXX
1.2.2.1.45Support EquipmentXX
1.2.2.24Structures and Mechanisms (SMS)XX
1.2.2.34Thermal Control (TCS)XX
1.2.2.44Electrical Power (EPS)XX
1.2.2.54Attitude Control Subsystem (ACS)XX
1.2.2.64Propulsion SubsystemXX
1.2.2.74Telemetry, Tracking, and Command Subsystem (TT&C)XX
1.2.2.84Bus Flight SoftwareXX
1.2.33Payload Suite Integration & Test
1.2.3.14SEIT/PM and Support Equipment
1.2.3.1.15Systems EngineeringXX
1.2.3.1.25Assembly, Integration and TestXX
1.2.3.1.35Program ManagementXX
1.2.3.1.45Support EquipmentXX
1.2.3.24Payloads Integration & Test
1.2.3.2.15Inter-Port AI&T
1.2.3.2.1.16Inter-Port AI&T #1XX
1.2.3.2.1.26Inter-Port AI&T #nXX
1.2.3.2.1.36Inter-Port AI&T #3XX
1.2.3.2.1.46Inter-Port AI&T #4XX
1.2.3.2.1.56Inter-Port AI&T #5XX
1.2.3.2.1.66Inter-Port AI&T #6XX
1.2.3.2.25Multi-Payload Intra-Port AI&T
1.2.3.2.2.16Multi-Payload Intra-Port AI&T #1XX
1.2.3.2.2.26Multi-Payload Intra-Port AI&T #nXX
1.2.3.2.2.36Multi-Payload Intra-Port AI&T #3XX
1.2.3.2.2.46Multi-Payload Intra-Port AI&T #4XX
1.2.3.2.2.56Multi-Payload Intra-Port AI&T #5XX
1.2.3.2.2.66Multi-Payload Intra-Port AI&T #6XX
1.2.3.2.35Payload I&T
1.2.3.2.3.16Payload #1 I&TXX
1.2.3.2.3.26Payload #n I&TXX
1.2.3.2.3.36Payload #3 I&TXX
1.2.3.2.3.46Payload #4 I&TXX
1.2.3.2.3.56Payload #5 I&TXX
1.2.3.2.3.66Payload #6 I&TXX
1.2.3.2.3.76Payload #7 I&TXX
1.2.3.2.3.86Payload #8 I&TXX
1.2.3.2.3.96Payload #9 I&TXX
1.2.3.2.3.106Payload #10 I&TXX
1.2.3.2.3.116Payload #11 I&TXX
1.2.3.2.3.126Payload #12 I&TXX
1.2.3.2.3.136Payload #13 I&TXX
1.2.3.2.3.146Payload #14 I&TXX
1.2.3.2.3.156Payload #15 I&TXX
1.2.3.2.3.166Payload #16 I&TXX
1.2.3.2.3.176Payload #17 I&TXX
1.2.3.2.3.186Payload #18 I&TXX
1.2.3.2.3.196Payload #19 I&TXX
1.2.3.2.3.206Payload #20 I&TXX
1.2.43Payload (N/A to program)XX
1.2.53Booster AdapterXX
1.2.63Space Vehicle StorageXX
1.2.73Launch Systems Integration (LSI)XX
1.2.83Launch OperationsXX
1.2.93Mission Operations SupportXX
1.2.103Space Vehicle OtherXX
1.32Ground Segment
1.3.13SEIT/PM and Support Equipment
1.3.1.14Systems EngineeringXX
1.3.1.24Assembly, Integration and TestXX
1.3.1.34Program ManagementXX
1.3.1.44Support EquipmentXX
1.3.23Ground Functions
1.3.2.14SEIT/PM and Support EquipmentXX
1.3.2.24COTS HardwareXX
1.3.2.34Custom HardwareXX
1.3.2.44Ground Function SoftwareXX
1.3.2.54Pre-Operations Mission SupportXX
1.3.33Ground Terminal/Gateway (GT) (N/A to program)XX
1.3.43External Network (T-COMM) (N/A to program)XX
1.3.53User Equipment (N/A to program)XX
1.3.63Facilities (N/A to program)XX
1.3.73Vehicles and Shelters (N/A to program)XX
1.42Orbital Transfer Vehicle (OTV) (N/A to program)XX
1.52Launch Vehicle (N/A to program)XX
1.62Insurance (N/A to program)XX
1.72Task Order (N/A to program)XX

Subtotal Cost X X

Reporting Contractor G&AXX
Reporting Contractor Undistributed BudgetXX
Reporting Contractor Management ReserveXX
Reporting Contractor FCCMXX
Total CostXX

Reporting Contractor Profit/Loss or Fee X X

Total PriceXX
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 IDb.
DATA REPORT(S)c.
SUBMISSION EVENT NAMEd.
REPORT CYCLEe. AS OF DATEf. DUE DATE
(YYYYMMDD)(YYYYMMDD)
1Cost and Hour Report (FlexFile)Contract AwardInitialTBDTBD
2Technical Data ReportContract AwardInitialTBDTBD
3Technical Data ReportAnnual Report 1InterimTBDTBD
4Cost and Hour Report (FlexFile)Annual Report 2InterimTBDTBD
5Cost and Hour Report (FlexFile)SV LaunchInterimTBDTBD
6Technical Data ReportSV LaunchFinalTBDTBD
7Cost and Hour Report (FlexFile)End of Ops SupportFinalTBDTBD

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. IDb. NAMEc. DATE

a. ID b. NAME

21. PRODUCT SIZE REPORTING ELEMENTS
a. CODEb. NAMEc. RELEASE IDd. CSCI ID
22. PRODUCT SIZE SUBMISSIONSc. RELEASE ID:1234
a. NUMBERb. NAMEIncluded?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. IDb. NAMEc. PHASE/MILESTONE
1Task Order 1…nB
17. END ITEMS
a. IDb. NAME
1STPSat-8 ...STPSat-n
18. OPTIONAL REQUIREMENTS
a. ORDER/LOT IDb. END ITEM IDc. 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 CODE27. WBS ELEMENT NAME28. ITEM TYPE29. TECHNICAL PARAMETER
a. PARAMETER NAMEb. UNIT OF MEASUREc. UNIT OF MEASURE QUALIFIERd. REPEATABLEe. REMARKS
1.0Space SystemProgramDatesContract Award DateDate
1.0Space SystemProgramDatesAuthority to Proceed (ATP) DateDate
1.0Space SystemProgramDatesPreliminary Design Review (PDR) DateDate
1.0Space SystemProgramDatesCritical Design Review (CDR) DateDate
1.0Space SystemProgramDatesBus Complete DateDate
1.0Space SystemProgramDatesAvailable for Launch (AFL) DateDate
1.0Space SystemProgramDatesTransfer to Launch Processing Facility DateDate
1.0Space SystemProgramDatesLaunch DateDate
1.0Space SystemSpaceSysDesign LifeMonths
1.0Space SystemSpaceSysMean Mission Duration (MMD)Years
1.0Space SystemSpaceSysOrbit RegimeList
1.0Space SystemSpaceSysOrbit AltitudeKilometers
1.0Space SystemSpaceSysOrbit InclinationDegrees Angular
1.0Space SystemSpaceSysContract TypeList
1.2Space VehicleSpaceVehiclePower - Beginning of Life (BOL)Watts
1.2Space VehicleSpaceVehicleAverage Day Power (EOL)Watts
1.2Space VehicleSpaceVehicleDelta-VMeters per Second
1.2Space VehiclePhysicalStrucDryDry Weight - BasicPounds
1.2Space VehiclePhysicalStrucDryDry Weight - Growth AllowancePounds
1.2Space VehiclePhysicalStrucDryDry Weight - Including Growth AllowancePounds
1.2Space VehiclePhysicalStrucWetWet Weight - BasicPounds
1.2Space VehiclePhysicalStrucWetWet Weight - Growth AllowancePounds
1.2Space VehiclePhysicalStrucWetWet Weight - Including Growth AllowancePounds
1.2.2BusBusBus ModelDescriptor
1.2.2BusBusFlight HeritageDescriptor
1.2.2BusBusVoltage - BusVoltsBus Level
1.2.2BusPhysicalStrucDryDry Weight - BasicPounds
1.2.2BusPhysicalStrucDryDry Weight - Growth AllowancePounds
1.2.2BusPhysicalStrucDryDry Weight - Including Growth AllowancePounds
1.2.2BusPhysicalStrucWetWet Weight - BasicPounds
1.2.2BusPhysicalStrucWetWet Weight - Growth AllowancePounds
1.2.2BusPhysicalStrucWetWet Weight - Including Growth AllowancePounds
1.2.2.2Structures and Mechanisms (SMS)PhysicalOtherMaterial Mix 1…nPercent of Total WeightMaterial NameY
1.2.2.2Structures and Mechanisms (SMS)PhysicalStrucDryDry Weight - BasicPounds
1.2.2.2Structures and Mechanisms (SMS)PhysicalStrucDryDry Weight - Growth AllowancePounds
1.2.2.2Structures and Mechanisms (SMS)PhysicalStrucDryDry Weight - Including Growth AllowancePounds
1.2.2.2Structures and Mechanisms (SMS)HeritageNew DesignPercent
1.2.2.3Thermal Control (TCS)PhysicalStrucDryDry Weight - BasicPounds
1.2.2.3Thermal Control (TCS)PhysicalStrucDryDry Weight - Growth AllowancePounds
1.2.2.3Thermal Control (TCS)PhysicalStrucDryDry Weight - Including Growth AllowancePounds
1.2.2.3Thermal Control (TCS)HeritageNew DesignPercent
1.2.2.4Electrical Power (EPS)EPSSpacePower - Beginning of Life (BOL)Watts
1.2.2.4Electrical Power (EPS)EPSSpacePower - End of Life (EOL)Watts
1.2.2.4Electrical Power (EPS)EPSSpaceNumber of Solar Array PanelsQuantityPanels
1.2.2.4Electrical Power (EPS)EPSSpaceSolar Array ConfigList
1.2.2.4Electrical Power (EPS)EPSSpaceSolar Array Incidence AngleDegrees
1.2.2.4Electrical Power (EPS)EPSSpaceSolar Array AreaSquare Meters
1.2.2.4Electrical Power (EPS)EPSSpaceArticulated Solar ArraysList
1.2.2.4Electrical Power (EPS)EPSSpacePower ConsumptionWatts
1.2.2.4Electrical Power (EPS)EPSSpaceSolar Cell AreaSquare Meters
1.2.2.4Electrical Power (EPS)EPSSpaceSolar Cell TypeList
1.2.2.4Electrical Power (EPS)BatteryBattery CapacityAmpere Hours
1.2.2.4Electrical Power (EPS)BatteryOutput VoltageVolts
1.2.2.4Electrical Power (EPS)BatteryType of BatteryList
1.2.2.4Electrical Power (EPS)BatteryNumber of Battery CellsQuantityCells
1.2.2.4Electrical Power (EPS)PhysicalStrucDryDry Weight - BasicPounds
1.2.2.4Electrical Power (EPS)PhysicalStrucDryDry Weight - Growth AllowancePounds
1.2.2.4Electrical Power (EPS)PhysicalStrucDryDry Weight - Including Growth AllowancePounds
1.2.2.4Electrical Power (EPS)HeritageNew DesignPercent
1.2.2.5Attitude Control Subsystem (ACS)ACSPointing AccuracyDegrees AngularBus Level
1.2.2.5Attitude Control Subsystem (ACS)ACSNumber of ADCS SensorsQuantitySensors
1.2.2.5Attitude Control Subsystem (ACS)PhysicalStrucDryDry Weight - BasicPounds
1.2.2.5Attitude Control Subsystem (ACS)PhysicalStrucDryDry Weight - Growth AllowancePounds
1.2.2.5Attitude Control Subsystem (ACS)PhysicalStrucDryDry Weight - Including Growth AllowancePounds
1.2.2.5Attitude Control Subsystem (ACS)HeritageNew DesignPercent
1.2.2.6Propulsion SubsystemTanksPropellant TypeDescriptorYG
1.2.2.6Propulsion SubsystemPhysicalStrucDryDry Weight - BasicPounds
1.2.2.6Propulsion SubsystemPhysicalStrucDryDry Weight - Growth AllowancePounds
1.2.2.6Propulsion SubsystemPhysicalStrucDryDry Weight - Including Growth AllowancePounds
1.2.2.6Propulsion SubsystemHeritageNew DesignPercent
1.2.2.7Telemetry, Tracking, and Command Subsystem (TT&C)TTandCBandList
1.2.2.7Telemetry, Tracking, and Command Subsystem (TT&C)TTandCBandwidth CrosslinkMegahertz
1.2.2.7Telemetry, Tracking, and Command Subsystem (TT&C)TTandCBandwidth DownlinkMegahertz
1.2.2.7Telemetry, Tracking, and Command Subsystem (TT&C)TTandCBandwidth UplinkMegahertz
1.2.2.7Telemetry, Tracking, and Command Subsystem (TT&C)TTandCCommunication Band TypeList
1.2.2.7Telemetry, Tracking, and Command Subsystem (TT&C)TTandCData Rate Average CrosslinkKilobits per Second
1.2.2.7Telemetry, Tracking, and Command Subsystem (TT&C)TTandCData Rate Average DownlinkKilobits per Second
1.2.2.7Telemetry, Tracking, and Command Subsystem (TT&C)TTandCData Rate Average UplinkKilobits per Second
1.2.2.7Telemetry, Tracking, and Command Subsystem (TT&C)TTandCData Rate Maximum CrosslinkKilobits per Second
1.2.2.7Telemetry, Tracking, and Command Subsystem (TT&C)TTandCData Rate Maximum DownlinkKilobits per Second
1.2.2.7Telemetry, Tracking, and Command Subsystem (TT&C)TTandCData Rate Maximum UplinkKilobits per Second
1.2.2.7Telemetry, Tracking, and Command Subsystem (TT&C)TTandCTT&C StandardDescriptor
1.2.2.7Telemetry, Tracking, and Command Subsystem (TT&C)PhysicalStrucDryDry Weight - BasicPounds
1.2.2.7Telemetry, Tracking, and Command Subsystem (TT&C)PhysicalStrucDryDry Weight - Growth AllowancePounds
1.2.2.7Telemetry, Tracking, and Command Subsystem (TT&C)PhysicalStrucDryDry Weight - Including Growth AllowancePounds
1.2.2.7Telemetry, Tracking, and Command Subsystem (TT&C)HeritageNew DesignPercent
1.2.2.8Bus Flight SoftwareSoftwareNonSRDRProduct Size - DeliveredSLOC
1.2.2.8Bus Flight SoftwareSoftwareNonSRDRProduct Size - EffectiveSLOC
1.2.2.8Bus Flight SoftwareSoftwareNonSRDRESLOC EquationDescriptor
1.2.2.8Bus Flight SoftwareSoftwareNonSRDRNew CodeSLOC
1.2.2.8Bus Flight SoftwareSoftwareNonSRDRModified CodeSLOC
1.2.2.8Bus Flight SoftwareSoftwareNonSRDRReused CodeSLOC
1.2.2.8Bus Flight SoftwareSoftwareNonSRDRCarryover CodeSLOC
1.2.2.8Bus Flight SoftwareSoftwareNonSRDRAuto-generated codeSLOC
1.2.2.8Bus Flight SoftwareSoftwareNonSRDRDevelopment ProcessDescriptor
1.2.2.8Bus Flight SoftwareSoftwareNonSRDRLanguageDescriptor
1.2.3Payload Suite Integration & TestPhysicalStrucDryDry Weight - BasicPounds
1.2.3Payload Suite Integration & TestPhysicalStrucDryDry Weight - Growth AllowancePounds
1.2.3Payload Suite Integration & TestPhysicalStrucDryDry Weight - Including Growth AllowancePounds
1.2.3Payload Suite Integration & TestPhysicalStrucWetWet Weight - BasicPounds
1.2.3Payload Suite Integration & TestPhysicalStrucWetWet Weight - Growth AllowancePounds
1.2.3Payload Suite Integration & TestPhysicalStrucWetWet Weight - Including Growth AllowancePounds
1.2.3.2.1.1Inter-Port AI&T #1PayloadInterPortNumber of Inter-Port Connected PayloadsCount
1.2.3.2.1.1Inter-Port AI&T #1PayloadInterPortConnected Port IDsDescriptor
1.2.3.2.1.1Inter-Port AI&T #1PayloadInterPortConnected Payloads NamesDescriptor
1.2.3.2.1.1Inter-Port AI&T #1PayloadInterPortInter-Port Unique WeightPounds
1.2.3.2.1.2Inter-Port AI&T #nPayloadInterPortNumber of Inter-Port Connected PayloadsCount
1.2.3.2.1.2Inter-Port AI&T #nPayloadInterPortConnected Port IDsDescriptor
1.2.3.2.1.2Inter-Port AI&T #nPayloadInterPortConnected Payloads NamesDescriptor
1.2.3.2.1.2Inter-Port AI&T #nPayloadInterPortInter-Port Unique WeightPounds
1.2.3.2.1.3Inter-Port AI&T #3PayloadInterPortNumber of Inter-Port Connected PayloadsCount
1.2.3.2.1.3Inter-Port AI&T #3PayloadInterPortConnected Port IDsDescriptor
1.2.3.2.1.3Inter-Port AI&T #3PayloadInterPortConnected Payloads NamesDescriptor
1.2.3.2.1.3Inter-Port AI&T #3PayloadInterPortInter-Port Unique WeightPounds
1.2.3.2.1.4Inter-Port AI&T #4PayloadInterPortNumber of Inter-Port Connected PayloadsCount
1.2.3.2.1.4Inter-Port AI&T #4PayloadInterPortConnected Port IDsDescriptor
1.2.3.2.1.4Inter-Port AI&T #4PayloadInterPortConnected Payloads NamesDescriptor
1.2.3.2.1.4Inter-Port AI&T #4PayloadInterPortInter-Port Unique WeightPounds
1.2.3.2.1.5Inter-Port AI&T #5PayloadInterPortNumber of Inter-Port Connected PayloadsCount
1.2.3.2.1.5Inter-Port AI&T #5PayloadInterPortConnected Port IDsDescriptor
1.2.3.2.1.5Inter-Port AI&T #5PayloadInterPortConnected Payloads NamesDescriptor
1.2.3.2.1.5Inter-Port AI&T #5PayloadInterPortInter-Port Unique WeightPounds
1.2.3.2.1.6Inter-Port AI&T #6PayloadInterPortNumber of Inter-Port Connected PayloadsCount
1.2.3.2.1.6Inter-Port AI&T #6PayloadInterPortConnected Port IDsDescriptor
1.2.3.2.1.6Inter-Port AI&T #6PayloadInterPortConnected Payloads NamesDescriptor
1.2.3.2.1.6Inter-Port AI&T #6PayloadInterPortInter-Port Unique WeightPounds
1.2.3.2.2.1Multi-Payload Intra-Port AI&T #1PayloadIntraPortPort IDList
1.2.3.2.2.1Multi-Payload Intra-Port AI&T #1PayloadIntraPortNumber of Payloads on PortCount
1.2.3.2.2.1Multi-Payload Intra-Port AI&T #1PayloadIntraPortPayload NamesDescriptor
1.2.3.2.2.1Multi-Payload Intra-Port AI&T #1PayloadIntraPortIntra-Port Unique WeightPounds
1.2.3.2.2.2Multi-Payload Intra-Port AI&T #nPayloadIntraPortPort IDList
1.2.3.2.2.2Multi-Payload Intra-Port AI&T #nPayloadIntraPortNumber of Payloads on PortCount
1.2.3.2.2.2Multi-Payload Intra-Port AI&T #nPayloadIntraPortPayload NamesDescriptor
1.2.3.2.2.2Multi-Payload Intra-Port AI&T #nPayloadIntraPortIntra-Port Unique WeightPounds
1.2.3.2.2.3Multi-Payload Intra-Port AI&T #3PayloadIntraPortPort IDList
1.2.3.2.2.3Multi-Payload Intra-Port AI&T #3PayloadIntraPortNumber of Payloads on PortCount
1.2.3.2.2.3Multi-Payload Intra-Port AI&T #3PayloadIntraPortPayload NamesDescriptor
1.2.3.2.2.3Multi-Payload Intra-Port AI&T #3PayloadIntraPortIntra-Port Unique WeightPounds
1.2.3.2.2.4Multi-Payload Intra-Port AI&T #4PayloadIntraPortPort IDList
1.2.3.2.2.4Multi-Payload Intra-Port AI&T #4PayloadIntraPortNumber of Payloads on PortCount
1.2.3.2.2.4Multi-Payload Intra-Port AI&T #4PayloadIntraPortPayload NamesDescriptor
1.2.3.2.2.4Multi-Payload Intra-Port AI&T #4PayloadIntraPortIntra-Port Unique WeightPounds
1.2.3.2.2.5Multi-Payload Intra-Port AI&T #5PayloadIntraPortPort IDList
1.2.3.2.2.5Multi-Payload Intra-Port AI&T #5PayloadIntraPortNumber of Payloads on PortCount
1.2.3.2.2.5Multi-Payload Intra-Port AI&T #5PayloadIntraPortPayload NamesDescriptor
1.2.3.2.2.5Multi-Payload Intra-Port AI&T #5PayloadIntraPortIntra-Port Unique WeightPounds
1.2.3.2.2.6Multi-Payload Intra-Port AI&T #6PayloadIntraPortPort IDList
1.2.3.2.2.6Multi-Payload Intra-Port AI&T #6PayloadIntraPortNumber of Payloads on PortCount
1.2.3.2.2.6Multi-Payload Intra-Port AI&T #6PayloadIntraPortPayload NamesDescriptor
1.2.3.2.2.6Multi-Payload Intra-Port AI&T #6PayloadIntraPortIntra-Port Unique WeightPounds
1.2.3.2.3.1Payload #1 I&TPayloadUniquePayload NameDescriptor
1.2.3.2.3.1Payload #1 I&TPayloadUniqueHosted or Separable PayloadList
1.2.3.2.3.1Payload #1 I&TPayloadUniquePort IDList
1.2.3.2.3.1Payload #1 I&TPayloadUniqueManifest DateDate
1.2.3.2.3.1Payload #1 I&TPayloadUniqueDe-Manifest DateDate
1.2.3.2.3.1Payload #1 I&TPayloadUniqueRe-Manifest DateDate
1.2.3.2.3.1Payload #1 I&TPayloadUniqueLaunch with Mass ModelList
1.2.3.2.3.1Payload #1 I&TPayloadUniquePayload VolumeCubic Inches
1.2.3.2.3.1Payload #1 I&TPayloadUniquePayload Total WeightPounds
1.2.3.2.3.1Payload #1 I&TPayloadUniquePayload Weight - WetPounds
1.2.3.2.3.1Payload #1 I&TPayloadUniquePayload Weight - DryPounds
1.2.3.2.3.1Payload #1 I&TPayloadUniquePower - Maximum Consumption RateWatts
1.2.3.2.3.1Payload #1 I&TPayloadUniquePower - Average UsageWatts
1.2.3.2.3.1Payload #1 I&TPayloadUniquePower - InputWatts
1.2.3.2.3.1Payload #1 I&TPayloadUniqueProvided ItemsDescriptor
1.2.3.2.3.1Payload #1 I&TPayloadUniqueUnique Payload ItemsDescriptor
1.2.3.2.3.1Payload #1 I&TPayloadUniquePayload Clarification DetailsDescriptor
1.2.3.2.3.2Payload #n I&TPayloadUniquePayload NameDescriptor
1.2.3.2.3.2Payload #n I&TPayloadUniqueHosted or Separable PayloadList
1.2.3.2.3.2Payload #n I&TPayloadUniquePort IDList
1.2.3.2.3.2Payload #n I&TPayloadUniqueManifest DateDate
1.2.3.2.3.2Payload #n I&TPayloadUniqueDe-Manifest DateDate
1.2.3.2.3.2Payload #n I&TPayloadUniqueRe-Manifest DateDate
1.2.3.2.3.2Payload #n I&TPayloadUniqueLaunch with Mass ModelList
1.2.3.2.3.2Payload #n I&TPayloadUniquePayload VolumeCubic Inches
1.2.3.2.3.2Payload #n I&TPayloadUniquePayload Total WeightPounds
1.2.3.2.3.2Payload #n I&TPayloadUniquePayload Weight - WetPounds
1.2.3.2.3.2Payload #n I&TPayloadUniquePayload Weight - DryPounds
1.2.3.2.3.2Payload #n I&TPayloadUniquePower - Maximum Consumption RateWatts
1.2.3.2.3.2Payload #n I&TPayloadUniquePower - Average UsageWatts
1.2.3.2.3.2Payload #n I&TPayloadUniquePower - InputWatts
1.2.3.2.3.2Payload #n I&TPayloadUniqueProvided ItemsDescriptor
1.2.3.2.3.2Payload #n I&TPayloadUniqueUnique Payload ItemsDescriptor
1.2.3.2.3.2Payload #n I&TPayloadUniquePayload Clarification DetailsDescriptor
1.2.3.2.3.3Payload #3 I&TPayloadUniquePayload NameDescriptor
1.2.3.2.3.3Payload #3 I&TPayloadUniqueHosted or Separable PayloadList
1.2.3.2.3.3Payload #3 I&TPayloadUniquePort IDList
1.2.3.2.3.3Payload #3 I&TPayloadUniqueManifest DateDate
1.2.3.2.3.3Payload #3 I&TPayloadUniqueDe-Manifest DateDate
1.2.3.2.3.3Payload #3 I&TPayloadUniqueRe-Manifest DateDate
1.2.3.2.3.3Payload #3 I&TPayloadUniqueLaunch with Mass ModelList
1.2.3.2.3.3Payload #3 I&TPayloadUniquePayload VolumeCubic Inches
1.2.3.2.3.3Payload #3 I&TPayloadUniquePayload Total WeightPounds
1.2.3.2.3.3Payload #3 I&TPayloadUniquePayload Weight - WetPounds
1.2.3.2.3.3Payload #3 I&TPayloadUniquePayload Weight - DryPounds
1.2.3.2.3.3Payload #3 I&TPayloadUniquePower - Maximum Consumption RateWatts
1.2.3.2.3.3Payload #3 I&TPayloadUniquePower - Average UsageWatts
1.2.3.2.3.3Payload #3 I&TPayloadUniquePower - InputWatts
1.2.3.2.3.3Payload #3 I&TPayloadUniqueProvided ItemsDescriptor
1.2.3.2.3.3Payload #3 I&TPayloadUniqueUnique Payload ItemsDescriptor
1.2.3.2.3.3Payload #3 I&TPayloadUniquePayload Clarification DetailsDescriptor
1.2.3.2.3.4Payload #4 I&TPayloadUniquePayload NameDescriptor
1.2.3.2.3.4Payload #4 I&TPayloadUniqueHosted or Separable PayloadList
1.2.3.2.3.4Payload #4 I&TPayloadUniquePort IDList
1.2.3.2.3.4Payload #4 I&TPayloadUniqueManifest DateDate
1.2.3.2.3.4Payload #4 I&TPayloadUniqueDe-Manifest DateDate
1.2.3.2.3.4Payload #4 I&TPayloadUniqueRe-Manifest DateDate
1.2.3.2.3.4Payload #4 I&TPayloadUniqueLaunch with Mass ModelList
1.2.3.2.3.4Payload #4 I&TPayloadUniquePayload VolumeCubic Inches
1.2.3.2.3.4Payload #4 I&TPayloadUniquePayload Total WeightPounds
1.2.3.2.3.4Payload #4 I&TPayloadUniquePayload Weight - WetPounds
1.2.3.2.3.4Payload #4 I&TPayloadUniquePayload Weight - DryPounds
1.2.3.2.3.4Payload #4 I&TPayloadUniquePower - Maximum Consumption RateWatts
1.2.3.2.3.4Payload #4 I&TPayloadUniquePower - Average UsageWatts
1.2.3.2.3.4Payload #4 I&TPayloadUniquePower - InputWatts
1.2.3.2.3.4Payload #4 I&TPayloadUniqueProvided ItemsDescriptor
1.2.3.2.3.4Payload #4 I&TPayloadUniqueUnique Payload ItemsDescriptor
1.2.3.2.3.4Payload #4 I&TPayloadUniquePayload Clarification DetailsDescriptor
1.2.3.2.3.5Payload #5 I&TPayloadUniquePayload NameDescriptor
1.2.3.2.3.5Payload #5 I&TPayloadUniqueHosted or Separable PayloadList
1.2.3.2.3.5Payload #5 I&TPayloadUniquePort IDList
1.2.3.2.3.5Payload #5 I&TPayloadUniqueManifest DateDate
1.2.3.2.3.5Payload #5 I&TPayloadUniqueDe-Manifest DateDate
1.2.3.2.3.5Payload #5 I&TPayloadUniqueRe-Manifest DateDate
1.2.3.2.3.5Payload #5 I&TPayloadUniqueLaunch with Mass ModelList
1.2.3.2.3.5Payload #5 I&TPayloadUniquePayload VolumeCubic Inches
1.2.3.2.3.5Payload #5 I&TPayloadUniquePayload Total WeightPounds
1.2.3.2.3.5Payload #5 I&TPayloadUniquePayload Weight - WetPounds
1.2.3.2.3.5Payload #5 I&TPayloadUniquePayload Weight - DryPounds
1.2.3.2.3.5Payload #5 I&TPayloadUniquePower - Maximum Consumption RateWatts
1.2.3.2.3.5Payload #5 I&TPayloadUniquePower - Average UsageWatts
1.2.3.2.3.5Payload #5 I&TPayloadUniquePower - InputWatts

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 .