DID FinderBack
Source
DI-MGMT-81898A

Space Systems Technical Data Report (SSTDR)

The Space Systems Technical Data Report (SSTDR) collects contractors' unit-level technical data and cost information across five formats to support DoD space acquisition program cost estimates and budgeting.

Approval DateJune 28, 2013
AMSC NumberF9413
Preparing Activity—
Project Number—
OPR19 (SMC/FMC)
DTIC Applicable—
GIDEP Applicable—
Limitation—
Applicable FormsDD Forms are not yet available. The following forms may be used to submit required information as follows: SSTDR Format: Space Hardware Data Summary | Form Number: 1 | Sample Format No.: 1 SSTDR Format: Space Hardware Detail Report | Form Number: 2 | Sample Format No.: None SSTDR Format: Space Unit Cost Report | Form Number: 3 | Sample Format No.: 3 SSTDR Format: Space Tech Baseline Report | Form Number: 4 | Sample Format No.: 4 SSTDR Format: GOPC/GT Hardware Detail Report | Form Number: 5 | Sample Format No.: None
Approval Limitation—
Form Version—
DID Formatdd_form_1664
963C CompliantNo
DISTRIBUTION STATEMENT A: Approved for public release; distribution is unlimited.
Supersedes
—
Related
DI-MGMT-81334ADI-MGMT-81466ADI-FNCL-81565ADI-FNCL-81DI-GDRQ-81231

Description & Purpose

—

Application & Interrelationship

—

Use & Relationship

This report consists of five formats for collecting contractors' technical data and unit cost on Department of Defense (DoD) space acquisition contracts.

Format 1 provides unit-level space hardware technical data on product-oriented Work Breakdown Structure (WBS) elements; these WBS data are used for cost model inputs. See Sample Format 1.

Format 2 provides the detailed space hardware technical data associated with the appropriate level of indenture. There is no sample for this format.

Format 3 provides estimate at complete (actuals and estimate to complete) cost information for the units, boxes, assemblies, SEIT/PM, Support Equipment and/or software CSCIs. See Sample Format 3.

Format 4 provides specific technical data to establish the technical baseline of the proposed/contracted system. See Sample Format 4.

Format 5 provides the detailed ground hardware technical data associated with the appropriate level of indenture. There is no sample for this format.

SSTDR data shall be used by DoD component staff, including program managers, engineers, cost estimators, and financial management personnel to: (1) Review and evaluate the baseline reasonableness; (2) Provide technical inputs required to develop a program cost estimate; and (3) Collect technical and cost information to develop estimating relationships (CERs).

SSTDR primary value to the Government is its ability to support the development of program cost estimates. It is important that the data be as accurate as possible so that they may be used for their intended purpose, which is to facilitate improved budgeting.

a. This Data Item Description (DID) contains the format and content preparation instructions for the data product generated by the specific and discrete task requirements as delineated in the contract.

b. This DID shall be used in conjunction with the Contract Work Breakdown Structure (CWBS) DID, DI-MGMT-81334A, CONTRACT PERFORMANCE REPORT (CPR) DID, DI-MGMT-81466A, Cost Data Summary Report DID, DI-FNCL-81565A, Cost & Software Data report DID, DI-FNCL-81, Detailed Mass props Status report DID, DI-GDRQ-81231

The same WBS shall be utilized for the Integrated Master Plan (IMP), Integrated Master Schedule (IMS), CPR, and Contractor Cost Data Report (CCDR) as applicable.

c. The SSTDR shall be used to obtain cost and technical information on contracts for programs that are ACAT 1 or 2 and any other program as designated by the PEO or Comptroller.

d. The SSTDR shall be required no more frequently than yearly. Data contained in the formats shall be as of the accounting month end of the milestones specified, with delivery no more than 90 days after milestone completion. This requirement may be tailored through contract negotiations. All formats are not required (or even normally provided) at the same time. Each format contains unique data that apply mainly to specific program phases and maturity. Format 2 and 5 are recommended at CDR and IOC milestones only and should always be accompanied by Format 1. Format 4 is usually provided only in phase A (to PDR) of the program.

e. Unless otherwise provided in the contract, data reported in the SSTDR shall pertain to all authorized contract work, including both priced and unpriced effort.

f. Submission of Formats 1 & 3 using a product-oriented WBS in accordance with the WBS Handbook, MIL-STD-881, and the CWBS DID, DI-MGMT-81334A, is mandatory. (Note: For contracts that require CCDRs, the CWBS shall be developed, approved, and maintained in accordance with DoD 5000.4-M-1, Cost and Software Data Reporting Manual, and the CWBS DID.)

Certain aspects of the report are subject to negotiation between the Government and the contractor, such as the level of detail to be reported in Format 1 (normally this will be at unit, assembly, or CSCI as defined in MIL-STD-881 for space systems). Although the SSTDR Contract Data Requirements List (CDRL) is subject to tailoring, requiring more information (e.g., additional technical parameters) in the SSTDR CDRL than specified in this DID is contrary to DoD policy. All negotiated reporting provisions shall be specified in the contract.

Preparation Instructions

1Referenced documents.The applicable issue of the documents cited herein, including their approval dates and dates of any applicable amendments, notices, and revisions, shall be as cited in the current issue of the DODISS at the time of the solicitation.
2Format.Use the relevant formats as listed above. All formats shall be submitted electronically in accordance with the following requirements. All formats shall be in a readable digital format: The American National Standards Institute (ANSI) X12 standard (839 transaction set), the United Nations Electronic Data Interchange for Administration, Commerce and Transport (UN/EDIFACT) standard (PROCST message), XML, or Microsoft Office compatible data formats. Contractor formats may be substituted whenever they contain all of the required data elements at the specified reporting levels and are compliant with the above electronic formats and approved by contracting officer. On-line access to the data may be provided to augment formal SSTDR submission. There shall be no hardcopies required, except as identified on the CDRL.
3Content.The SSTDR shall contain the following: Reference Appendix A of this DID for all field/data definitions, measurement units, and relevance. Reference Appendix B for sample Formats 1, 3, and 4. Corresponding MS Excel files are available at the following DAU Space Acquisition website: https://acc.dau.mil/CommunityBrowser.aspx?id=652968&lang=en-US
3.1Heading Information - Applies to all Formats.Preparation instructions for Heading Information apply to Formats 1 through 5.
3.1.1Format_Title
3.1.2Contractor_Name
3.1.3Contract_Number
3.1.4Program_Name
3.1.5Program_Phase
3.1.6Report_Date
3.1.7As_of_Date
3.1.8Security_Class
3.1.9POC_Tech
3.1.10POC_Phone
3.1.11Version
3.2Format 1 - Space Hardware Data Summary.Electronic submittal shall be machine readable in a table type format. Use sample format unless otherwise approved.
3.2.0Sub header information
3.2.0.1SV_Quantity
3.2.1Element identification
3.2.1.1WBS_Code
3.2.1.2Unit_ID_Code
3.2.1.3881_ID
3.2.1.4Subsystem
3.2.1.5WBS_Name
3.2.2Mass information
3.2.2.1Weight_Basic
3.2.2.2Qty_Per_SV
3.2.2.3Weight_Growth
3.2.2.4Predicted_Mass
3.2.3Number of units produced
3.2.3.1Units_Engr_Models
3.2.3.2Units_TQ
3.2.3.3Units_Engr_GFE
3.2.3.4Units_Flight_GFE
3.2.3.5Units_PQ
3.2.3.6Units_Flight
3.2.3.7Units_Spare
3.2.3.8Units_Refurb
3.2.4Non-recurring design parameters
3.2.4.1Unique_Comp
3.2.4.2New_Design
3.2.5Additional information
3.2.5.1Hdwr_Manufacturer
3.2.5.2TDS_Comments
3.3Format 2 - Space Hardware Detail Report.Electronic submittal shall be machine readable in contractor format.
3.3.1Element identification
3.3.1.1Antenna related elements
3.3.1.1.1Ant_Efficiency
3.3.1.1.2Antenna_Type
3.3.1.1.3Amp_Efficiency
3.3.1.1.4Array_Act_Elements
3.3.1.1.5Array_Area
3.3.1.1.6Array_Beamforming
3.3.1.1.7Array_Beams
3.3.1.1.8Array_Pwr_Per_Elemt
3.3.1.1.9Reflector_Size
3.3.1.2Communications related elements
3.3.1.2.1Band
3.3.1.2.2Channels_Qty
3.3.1.2.3Data_Rate_Avg_Dlink
3.3.1.2.4Data_Rate_Avg_Ulink
3.3.1.2.5Data_Rate_Avg_Xlink
3.3.1.2.6Data_Rate_Max_Dlink
3.3.1.2.7Data_Rate_Max_Ulink
3.3.1.2.8Data_Rate_Max_Xlink
3.3.1.2.9Downlink_Modes
3.3.1.2.10EIRP
3.3.1.2.11Frequency
3.3.1.2.12Gain
3.3.1.2.13Max_Frequency
3.3.1.2.14Min_Frequency
3.3.1.2.15SNR_Ratio
3.3.1.2.16Uplink_Modes
3.3.1.3Electrical Power related elements
3.3.1.3.1Battery_Capacity
3.3.1.3.2Battery_Type
3.3.1.3.3Bus_Voltage
3.3.1.3.4Solar_Array_Area
3.3.1.3.5Solar_Array_Config
3.3.1.3.6Solar_Cell_Area
3.3.1.3.7Solar_Cell_Type
3.3.1.4Focal Plane Array related elements
3.3.1.4.1Chip_Redesign
3.3.1.4.2FPA_Array_Size
3.3.1.4.3FPA_Operating_Band
3.3.1.4.4FPA_Temp
3.3.1.4.5FPA_Thermal_Type
3.3.1.4.6Pixel_Qty
3.3.1.4.7Pixel_Size
3.3.1.4.8ROIC_Redesign
3.3.1.5Optical Subsystem related elements
3.3.1.5.1Aperture_Qty
3.3.1.5.2Aperture_Size
3.3.1.5.3Curved_Elements
3.3.1.5.4F_Number
3.3.1.5.5Mirror_Qty
3.3.1.5.6Optical_Axis
3.3.1.5.7Scan_Mirror
3.3.1.6Payload related elements
3.3.1.6.1Field_of_View
3.3.1.6.2Payload_Gimbaled
3.3.1.6.3Payload_Type
3.3.1.7Pointing, Command & Control or Digital related elements
3.3.1.7.1ADCS_Type
3.3.1.7.2ASIC_ClockSpeed
3.3.1.7.3ASIC_Designs
3.3.1.7.4Data_Storage_Cap
3.3.1.7.5Gimbal_Type
3.3.1.7.6GN&C_Method
3.3.1.7.7OnBoard_Storage_Cap
3.3.1.7.8Pointing_Accuracy
3.3.1.7.9Pointing_Knowledge
3.3.1.8Power related elements
3.3.1.8.1Power_Avg
3.3.1.8.2Power_BOL
3.3.1.8.3Power_EOL
3.3.1.8.4Peak_Output_Power
3.3.1.9Program level related elements
3.3.1.9.1Bus_Model
3.3.1.9.2Flight_Heritage
3.3.1.9.3Launch_Availability
3.3.1.9.4Launch_Vehicle
3.3.1.9.5Mission_Class
3.3.1.9.6New_1st_Time_Integ
3.3.1.9.7Orbit_Inclination
3.3.1.9.8Sat_in_Constel_No
3.3.1.9.9Sponsoring_Agncy_No
3.3.1.9.10System_Name
3.3.1.9.11Time_Development
3.3.1.10Structure & Mechanisms related elements
3.3.1.10.1Articulated_Str_No
3.3.1.10.2Deployables
3.3.1.10.3Structures_Material
3.3.1.11Space Vehicle related elements
3.3.1.11.1Design_Life
3.3.1.11.2Impulse_Total
3.3.1.11.3MLE
3.3.1.11.4MMD
3.3.1.11.5Orbit_Altitude
3.3.1.11.6Orbit_Regime
3.3.1.11.7Orbital_Apoapsis
3.3.1.11.8Orbital_Periapsis
3.3.1.11.9Propulsion_Type
3.3.1.11.10Rad_Hardened
3.3.1.11.11Reliability
3.3.1.11.12Threat_Hardening
3.3.1.11.13Weight_Ctr_Limit
3.3.1.12WBS_Level
3.3.1.13Name
3.3.1.13.1881_ID
3.3.1.13.2Subsystem
3.3.1.13.3Unit_ID_Code
3.3.1.13.4WBS_Code
3.3.1.13.5WBS_Name
3.3.2Technical information
3.3.2.1Tech_Unit_of_Measure
3.3.2.2Tech_Value
3.3.3Optional Items:These items are not to be included within the report unless specifically requested within the CDRL referencing this DID format.
3.3.3.1ADCS_Box_Type
3.3.3.2ADCS_Pwr_Dissip
3.3.3.3ADCS_Sensor_No
3.3.3.4Comm_Freq_Range
3.3.3.5Flt_Comp_Act_No
3.3.3.6Flt_Comp_IRU_No
3.3.3.7Flt_Comp_Per_Uni_No
3.3.3.8Flt_Comp_Sensor_No
3.3.3.9IRU_Gyro_Drift
3.3.3.10IRU_Stability
3.3.3.11RF_Freq_Range
3.3.3.12TWTA_Dyn_Linear_Rang
3.3.3.13Wheel_Stability
3.3.3.14Wheel_Max_Moment
3.3.3.15Wheel_Torque
3.4Format 3 - Space Unit Cost Report.
3.4.1Summary Information Area
3.4.1.1COM_Included
3.4.1.2G&A_Included
3.4.1.3Actual Cost of Work Performed Cumulative To Date Area.The values entered within this block shall be the cumulative to-date Actual Cost of Work Performed (ACWP), without regard to ceiling, ending at the time period indicated by Report Date (Item 1). For each entry for which no costs have been incurred, enter a zero or leave blank.
3.4.1.3.1ACWP_COM
3.4.1.3.2ACWP_G&A
3.4.1.3.3ACWP_Total
3.4.1.4Estimated At Completion Area.These blocks shall present the contractor's estimated costs at completion. These estimates are intended to allow contractor management flexibility to express the most likely possible cost outcomes. Contractors shall provide the most accurate Estimates at Completion (EACs) possible through program-level assessments of factors that may affect the cost, schedule, or technical outcome of the contract. Such program-level assessments shall include consideration of known or anticipated risk areas, and planned risk reductions or cost containment measures. EACs shall be reported without regard to contract ceiling. For each entry for which no costs have been estimated, enter a zero or leave blank.
3.4.1.4.1EAC_COM
3.4.1.4.2EAC_G&A
3.4.1.4.3EAC_Total
3.4.2Detailed Area
3.4.2.1WBS_Code
3.4.2.2Unit_CSCI
3.4.2.3Subsystem
3.4.2.4ACWP_NRE
3.4.2.5ACWP_REC
3.4.2.6ACWP_Total
3.4.2.7EAC_NRE
3.4.2.8EAC_REC
3.4.2.9EAC_Total
3.4.2.10Unit_Cost_Comment
3.4.3Footer Area.
3.4.3.1Unit_Cost_Remarks
3.5Format 4 - Technical Baseline Data Report.The data elements below will be submitted in two reports by the contractor(s) chosen for the system technical maturation phase after Government Milestone A (KDP A) Acquisition Strategy deliberations. The initial report will be delivered at the System Requirements Review (SRR). The final report in this Format will be delivered by the contractor(s) chosen for system maturation prior to the System Functional Review (SFR) in sufficient time to support the development of a government Cost Analysis Requirements Document (CARD-Section 1.2.1 Technical/Physical Description). The CARD will be used for subsequent Milestone B (KDP B) Acquisition Decision Memorandum (ADM) deliberations. Subsequent to Milestone B, Format 2 Reports (see above) will be generated at the appropriate WBS levels and at times specified above. All reports will be consistent with electronic submittal and shall be machine readable in contractor format.
3.5.1Element identification
3.5.1.1Data Type ID.The following data type IDs apply to this format:
3.5.2Detailed Area
3.5.2.1SYSTEM (Spacecraft) LEVEL & GENERIC DATA ELEMENTS
3.5.2.1.1Design_Life
3.5.2.1.2Flight_Heritage
3.5.2.1.3Launch_Availability
3.5.2.1.4Mission_Class
3.5.2.1.5Orbit_Altitude
3.5.2.1.6Orbit_Inclination
3.5.2.1.7Orbit_Regime
3.5.2.1.8Sat_in_Constel_No
3.5.2.1.9Threat_Hardening
3.5.2.1.10Time_Development
3.5.2.1.11Weight_Basic
3.5.2.1.12Weight_Growth
3.5.2.2BUS LEVEL DATA ELEMENTS
3.5.2.2.1ADCS_Type
3.5.2.2.2Articulated_Str_No
3.5.2.2.3Battery_Capacity
3.5.2.2.4Battery_Type
3.5.2.2.5Bus_Model
3.5.2.2.6Bus_Voltage
3.5.2.2.7Deployables
3.5.2.2.8Frequency
3.5.2.2.9Impulse_Total
3.5.2.2.10Peak_Output_Power
3.5.2.2.11Pointing_Accuracy
3.5.2.2.12Pointing_Knowledge
3.5.2.2.13Power_BOL
3.5.2.2.14Power_EOL
3.5.2.2.15Processing_Rate
3.5.2.2.16Propulsion_Type
3.5.2.2.17Solar_Array_Area
3.5.2.2.18Solar_Array_Config
3.5.2.2.19Solar_Cell_Type
3.5.2.2.20Structures_Material
3.5.2.2.21Thermal_Type
3.5.2.2.22Thruster_Tank_No
3.5.2.2.23TT&C_Standard
3.5.2.3PAYLOAD PHYSICAL DATA ELEMENTS
3.5.2.3.1Field_of_View
3.5.2.3.2Gimbal_Type
3.5.2.3.3Instruments_No
3.5.2.3.4OnBoard_Storage_Cap
3.5.2.3.5Payload_Gimbaled
3.5.2.3.6Payload_Type
3.5.2.3.7Power_Avg
3.5.2.3.8Power_Peak
3.5.2.3.9SNR_Ratio
3.5.2.4PAYLOAD ELECTRONICS DATA ELEMENTS
3.5.2.4.1Antenna_Qty
3.5.2.4.2ASIC_Designs
3.5.2.4.3ASIC_GateCount
3.5.2.4.4Band_Amp_Qty
3.5.2.4.5Bandwidth_Dlink
3.5.2.4.6Bandwidth_Ulink
3.5.2.4.7Bandwidth_Xlink
3.5.2.4.8Channels_Qty
3.5.2.4.9Data_Process_Level
3.5.2.4.10Data_Rate_Avg_Dlink
3.5.2.4.11Data_Rate_Avg_Ulink
3.5.2.4.12Data_Rate_Avg_Xlink
3.5.2.4.13Data_Rate_Max_Dlink
3.5.2.4.14Data_Rate_Max_Ulink
3.5.2.4.15Data_Rate_Max_Xlink
3.5.2.4.16Data_Storage_Cap
3.5.2.4.17FPGA_Designs
3.5.2.4.18FPGA_GateCount
3.5.2.5OPTICAL PAYLOAD DATA ELEMENTS
3.5.2.5.1Aperture_Size
3.5.2.5.2Curved_Elements
3.5.2.5.3F_Number
3.5.2.5.4Mirror_Qty
3.5.2.5.5Optical_Axis
3.5.2.5.6Scan_Mirror
3.5.2.6IR PAYLOAD DATA ELEMENTS
3.5.2.6.1Chip_Redesign
3.5.2.6.2FPA_Array_Size
3.5.2.6.3FPA_Operating_Band
3.5.2.6.4FPA_Temp
3.5.2.6.5FPA_Thermal_Type
3.5.2.6.6Pixel_Qty
3.5.2.6.7Pixel_Size
3.5.2.6.8ROIC_Redesign
3.5.2.7ANTENNAS AND AMPLIFIERS PAYLOAD
3.5.2.7.1Amp_Efficiency
3.5.2.7.2Amp_Type
3.5.2.7.3Antenna_Type
3.5.2.7.4Band
3.5.2.7.5EIRP
3.5.2.7.6Gain
3.5.2.7.7Max_Frequency
3.5.2.7.8Power_Output
3.5.2.7.9Reflector_Size
3.5.2.8GROUND DATA ELEMENTS (PHYSICAL)
3.5.2.8.1GOPC_Qty
3.5.2.8.2GOPC_Reloc
3.5.2.8.3Ground_Sites_No
3.5.2.8.4Ground_Sites_Reloc
3.5.2.8.5Ground_Storage_Cap
3.5.2.9FLIGHT & GROUND SOFTWARE DATA ELEMENTS
3.5.2.9.1Effective_LOC

References

Corresponding MS Excel files are available at the following DAU Space Acquisition website https://acc.dau.mil/CommunityBrowser.aspx?id=652968&lang=en-US

Figures

Figure Sample Format 1: Appendix B - Sample Format 1, Space Hardware Data Summary (notional data example)

Figure Sample Format 1. Appendix B - Sample Format 1, Space Hardware Data Summary (notional data example)

Figure Sample Format 3: Appendix B - Sample Format 3, Space Unit Cost Report (notional data example)

Figure Sample Format 3. Appendix B - Sample Format 3, Space Unit Cost Report (notional data example)

Figure Sample Format 4 Part 1: Appendix B - Sample Format 4, Space Tech Baseline Report, Part 1 (notional data example)

Figure Sample Format 4 Part 1. Appendix B - Sample Format 4, Space Tech Baseline Report, Part 1 (notional data example)

Figure Sample Format 4 Part 2: Appendix B - Sample Format 4, Space Tech Baseline Report, Part 2 (notional data example)

Figure Sample Format 4 Part 2. Appendix B - Sample Format 4, Space Tech Baseline Report, Part 2 (notional data example)

Figure Sample Format 4 Tables: Appendix B - Sample Format 4, Amplifier/Antenna/Band Tables (notional data example)

Figure Sample Format 4 Tables. Appendix B - Sample Format 4, Amplifier/Antenna/Band Tables (notional data example)

Schema v3.0Community-maintained · Verify against ASSIST
Community-maintained — not an official government database.
Verify against ASSIST·GitHub·About·Disclaimer