Draft OT Attachment 5 - CSDR Plan.xls
XLS spreadsheet 77 KB Posted
- Attached to
- SDA Tranche 1 Tracking Layer DRAFT Solicitation Federal contract opportunity
- Solicitation number
- SDA-SN-22-0006
- Issued by
- Space Development Agency
View the file
Other files for this federal contract opportunity
| File | Type | Posted |
|---|---|---|
| Draft OT T1 Tracking Layer Program Solicitation.pdf | ||
| Draft OT T1 Tracking Solicitation Post Notification 20220218.pdf | ||
| Draft T1 Tracking Layer Solicitation (Amendment 001).pdf | ||
| Draft OT Attachment 7 - Data Rights Table.pdf | ||
| Draft OT Attachment 3 - GFE_GFI List.pdf | ||
| Draft OT Attachment 6 - DD 254 .pdf | ||
| Draft T1 Tracking Layer Solicitation.pdf | ||
| Draft OT Attachment 4 - Agreement Officers Representative.pdf | ||
| Volume VI - Draft Other Transaction (OT) Agreement.pdf |
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 | |
| Tranche 1 Transport Layer (T1TL) | |
| 1b. PHASE/MILESTONE (check all that apply) | |
| Pre-A | |
| A | |
| X | B |
| C-LRIP | |
| C-FRP | |
| O&S | |
| 1c. PRIME MISSION PRODUCT | |
| Space System | |
| 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) | |
| 20210818 | |
| 5. LAST APPROVED PLAN DATE (YYYYMMDD) | |
| 6a. GOVERNMENT PLAN POINT OF CONTACT (POC) NAME (Last, First, M.) | |
| Palermo, Billy | |
| 6b. ADDRESS (Include ZIP Code) | |
| Office of the Under Secretary of Defense, Research and Engineering (USD(R&E)) |
3030 Defense Pentagon Washington, DC 20301
| 6c. TELEPHONE NUMBER (Include Area Code) | ||
| 571-372-4265 | ||
| 6d. E-MAIL ADDRESS | ||
| william.j.palermo2.civ@mail.mil | ||
| 7. PLAN TYPE | ||
| GOVERNMENT | ||
| X | CONTRACT (PRIME) | |
| CONTRACT (SUB) | ||
| 8. PLAN GOVERNMENT PREPARING ORGANIZATION | ||
| Space Development Agency | ||
| 9a. CONTRACTOR NAME/ADDRESS | ||
| i. REPORTING ORGANIZATION NAME | ||
| TBD | ||
| ii. DIVISION NAME | ||
| 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) | ||
| SDA-PS-22-01 | ||
| 9c. APPROPRIATION (check all that apply) | ||
| X | RDT&E | |
| PROCUREMENT | ||
| O&M | ||
| FMS | ||
| WCF | ||
| OTHER | ||
| 10a. APPROVED PLAN NUMBER | ||
| AF-21-H-C1 | ||
| 10b. APPROVED PLAN REVISION NUMBER | ||
| 0 | ||
| 10c. APPROVED PLAN REQUIREMENTS | ||
| AT COMPLETION COSTS FOR STANDARD FUNCTIONAL CATEGORIES (FlexFile or Legacy) | ||
| AT COMPLETION COSTS FOR RECURRING/NONRECURRING (FlexFile only) | ||
| X | TECHNICAL DATA REQUIRED | |
| 10d. COST REPORT TYPE | ||
| FLEXFILE | ||
| X | LEGACY DD 1921 SERIES | |
| DRAFT DD FORM 2794 (PAGE 1), METADATA, JANUARY 2019 | PREVIOUS EDITION IS OBSOLETE |
DD Form 2794, Pg 2 (REPORTING)
| COST AND SOFTWARE DATA REPORTING PLAN | COST, SOFTWARE, & TECHNICAL DATA REPORTING/EARNED VALUE MANAGEMENT CO-PLAN | |||||
| 11. WORK BREAKDOWN STRUCTURE (WBS) | 12. COST | 13. TECHNICAL DATA | ||||
| a. WBS | ||||||
| CODE | b. WBS | |||||
| LEVEL | c. WBS ELEMENT NAME | a. ACTUALS TO | ||||
| DATE (ATD) | b. LEGACY | |||||
| 1921-1 | c. LEGACY | |||||
| 1921-2 | d. LEGACY | |||||
| 1921-5 | e. EAC/FAC | |||||
| (See item 10d) | a. QUANTITY | b. SRDR | ||||
| FORMATS | c. |
MAINT. &
REPAIR
PARTS
| i. QUANTITY | ||
| DATA | ii. GFE |
QUANTITY
| 1.0 | 1 | Tranche 1 Tracking Layer | ||
| 1.1 | 2 | System Level SEIT/PM and Support Equipment | X | X |
| 1.2 | 2 | Baseline Space Vehicle | ||
| 1.2.1 | 3 | SEIT/PM and Support Equipment | X | X |
| 1.2.2 | 3 | Bus | X | X |
| 1.2.3 | 3 | Infrared Sensor Payload | X | X |
| 1.2.4 | 3 | Optical Communications Terminals | X | X |
| 1.2.5 | 3 | Ka Band Communications Payload | X | X |
| 1.2.6 | 3 | Networking and Encryption | X | X |
| 1.2.7 | 3 | Payload Other | X | X |
| 1.4 | 2 | Ground Element (NOVA) | ||
| 1.4.1 | 3 | Ground Element SEIT/PM, Other | X | X |
| 1.4.2 | 3 | Hardware | X | X |
| 1.4.3 | 3 | Software | X | X |
| 1.5 | 2 | Launch | ||
| 1.5.1 | 3 | Launch SEIT/PM and Support Equipment | X | X |
| 1.5.2 | 3 | Launch Vehicle adapter/dispenser | X | X |
| 1.5.3 | 3 | Launch Systems Integration (LSI) | X | X |
| 1.5.4 | 3 | Launch Operations | X | X |
| 1.6 | 2 | Operations | ||
| 1.6.1 | 3 | Launch and Early Operations (LEOps) | X | X |
| 1.6.2 | 3 | Operations and Sustainment (O&S) | X | X |
| Subtotal Cost | X | X | ||
| Reporting Contractor G&A | X | X | ||
| Reporting Contractor Undistributed Budget | ||||
| Reporting Contractor Management Reserve | ||||
| 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 |
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 | 1921, CWBS Dictionary | T1TRK- Contract Award | Initial | 20220121 | 20220321 | ||
| 2 | Technical Data Report | T1TRK- Contract Award | Initial | 20220121 | 20220321 | ||
| 3 | 1921, CWBS Dictionary | T1TRK- Critical Design Review | Interim | 20230401 | 20230601 | ||
| 4 | Technical Data Report | T1TRK- Critical Design Review | Interim | 20230401 | 20230601 | ||
| 5 | 1921, CWBS Dictionary | T1TRK- Second Launch | Final | 20250330 | 20250530 | ||
| 6 | Technical Data Report | T1TRK- Second Launch | Final | 20250330 | 20250530 | ||
| DRAFT DD FORM 2794 (PAGE 3), SUBMISSION EVENTS, JANUARY 2019 | PREVIOUS EDITION IS OBSOLETE |
DD Form 2794, Pg 4 (REMARKS)
| COST AND SOFTWARE DATA REPORTING PLAN |
| 15. REMARKS |
| a. CSDR Planning Approach & Preparation Instructions |
| THE GOVERNMENT AND CONTRACTOR SHALL REVIEW AND TAILOR CSDR REPORTING REQUIREMENTS TO THE CONTRACTOR’S ACCOUNTING SYSTEM AND TECHNICAL APPROACH TO CONTRACT EXECUTION. THE INTENT IS TO MAXIMIZE THE USE OF DATA, SYSTEMS, AND PROCESSES THE CONTRACTOR ALREADY UTILIZES IN ITS NORMAL COURSE OF BUSINESS (E.G., PURCHASE ORDERS RECEIPTS, PAYROLL INFORMATION, TAX RECORDS). CSDR IS DESIGNED NOT TO REQUIRE SIGNIFICATE REVISIONS IN EITHER ACCOUNTING SYSTEMS OR TECHNICAL APPROACHES IN ORDER FOR A CONTRACTOR TO BE COMPLIANT TO ITS REQUIREMENTS. |
| 1. 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 scope 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). |
| 2. Costs reported against this CSDR plan shall be cumulative in nature (i.e., each submission shall report any and all costs incurred on and prior to the submission’s “AS OF DATE” (block 14.e)). |
| 3. Regarding the WBS Structure (block 11): This CSDR plan utilizes MIL-STD-881E as the baseline for its WBS which has been extended to provide additional insight into system(s) or subsystem(s) which the Government believes to be high-risk or high-technical-interest in accordance with DoD Manual 5000.04. |
THE GOVERNMENT AND CONTRACTOR SHALL REVIEW THE WBS WHICH MAY BE REVISED AT THE CSDR READINESS REVIEW IF REQUIRED TO BETTER ALIGN THE WBS WITH THE CONTRACTOR’S ACCOUNTING SYSTEM AND/OR TECHNICAL APPROACH TO CONTRACT EXECUTION.
| __i. The contractor may extend any WBS element to allow the contractor to provide additional insight into its technical solution. Any and all extensions or tailoring of the WBS shall be in accordance with guidelines included in MIL-STD-881E and DoD Manual 5000.04. |
| __ii. WBS elements 1.2.8 (Payload Other) and 1.3.7 (Hosted Payload AI&T) shall be inclusive of Prime Contractor Payload SEIT PM and Support Equipment, Payload Structures and Mechanisms, Payload software development, and any other applicable costs. |
| 4. Direct Reporting Subcontractors: Application of CSDR subcontract flow down is not required by this CSDR Plan. |
| b. Submission Events and Dates |
| 1. Deliverable Perpetration Instructions by Event Type: 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). 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)). No "Actual to Date" costs are anticipated to reported on an "Initial" submission. |
The "Initial" submission shall have an "AS OF DATE" equal to the date of contract award and a "DUE DATE" 90 calendar days after the CSDR Readiness Review.
The contractor shall not prepare its initial submission until it has reviewed the CSDR plan with the CWIPT at the CSDR Readiness Review.
| __ii. Interim Submission(s): Submission events marked as an "Interim" submission in block 14.d shall have an "AS OF DATE" equal to date of the Critical Design Review and a "DUE DATE" 60 calendar days later. |
| __iii. Final Submission(s): Submission events marked as "Final" in block 14.d shall meet conditions listed in within DI-FNCL-81565C. |
| c. WBS Index and Dictionary |
| 1. The WBS Dictionary is a living document and must be maintain and update throughout the life of the contract, in accordance with DI-FNCL-82162, if changes to the WBS occur, the reporting entity shall submit an updated WBS Dictionary with its DD Form 1921 submissions. |
| d. Technical Data Report |
| 1. Include only UNCLASSIFIED information in Technical Data Report deliverables. Notify the Government Point of Contact (see block 6a) if any values associated with the Technical Parameter Requirements (block 29) would be considered classified CONFIDENTIAL, SECRET, or TOP SECRET, if reported. |
| e. CSDR Readiness Review |
| 1. The contractor shall host a CSDR Readiness Review (CSDR-RR) electronically or at the contractor’s facility where CSDRs are prepared with the Government’s Cost Working Group Integrated Product Team (CWIPT) IAW DFARS 242.503-2(b) and DoD Manual 5000.04 (CSDR Manual). The purpose of the CSDR-RR is to review the contract’s CSDR requirements and assess how the Contractor’s accounting system can be used to satisfy the CSDR requirements found in DoD 5000.04 (CSDR Manual) and this CSDR Plan. In a briefing presented by the Contractor in its own format, the Contractor shall: |
- Explain their proposed concept for addressing the CSDR requirements.
- Propose any changes to this CSDR Plan in order to tailor the plan to the contractor's accounting system to include any contractor recommended changes or additions to the WBS elements. These changes may include adjustments to the submission events and/or submission timelines, particularly in the case of a direct-reporting subcontractor performing against a different delivery schedule than the associated prime contractor.
The CSDR-RR shall be held within 60 days of contract award or the start of work meeting on a date mutually agreed to by the CWIPT and the contractor. This meeting has an anticipated duration of one business day.
DRAFT DD FORM 2794 (PAGE 4), REMARKS, JANUARY 2019 PREVIOUS EDITION IS OBSOLETE
DD Form 2794, Pg 8 (TECH RQTS)
| COST AND SOFTWARE DATA REPORTING PLAN - 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 | Tranche 1 Tracking Layer | Milestone Date | Contract Award | Date | |||
| 1.0 | Tranche 1 Tracking Layer | Milestone Date | System PDR | Date | |||
| 1.0 | Tranche 1 Tracking Layer | Milestone Date | System CDR | Date | |||
| 1.0 | Tranche 1 Tracking Layer | Milestone Date | System PRR | Date | |||
| 1.0 | Tranche 1 Tracking Layer | Milestone Date | Launch | Date | |||
| 1.0 | Tranche 1 Tracking Layer | Sys Quantities | No. of Production Units | Quantity | |||
| 1.0 | Tranche 1 Tracking Layer | Space System | Mission Type | Type | |||
| 1.0 | Tranche 1 Tracking Layer | Space System | Design Life (months) | Months | |||
| 1.0 | Tranche 1 Tracking Layer | Space System | Orbit Altitude (km) | Kilometers | |||
| 1.0 | Tranche 1 Tracking Layer | Space System | Orbit Inclination (deg) | Degrees | |||
| 1.0 | Tranche 1 Tracking Layer | Space System | Mission Assurance Class | List | Class A - D, Commercial | ||
| 1.2.2 | Bus | Spacecraft Bus | Bus Model | Name/Number | |||
| 1.2.2 | Bus | Spacecraft Bus | Flight Heritage | Name/Number | |||
| 1.2.3 | Bus | Spacecraft Bus | Current TRL | List | TRL 1 - TRL 9; bus level assessment | ||
| 1.2.2 | Bus | Spacecraft Bus | Mass - Basic | Kilograms (kg) | sum of all subsystems | ||
| 1.2.2 | Bus | Spacecraft Bus | Mass - Growth Allowance (kg) | Kilograms (kg) | |||
| 1.2.2 | Bus | Spacecraft Bus | No. of Production Units | Quantity | |||
| 1.2.2 | Bus | Spacecraft Bus | Power (Avg) | Watts (W) | |||
| 1.2.2 | Bus | Spacecraft Bus | Power (BOL/EOL) (W) | Watts (W) | |||
| 1.2.2 | Bus | Spacecraft Bus | Total Impulse (Delta-V) | Meter Seconds | meters per second | ||
| 1.2.3 | Infrared Sensor | Payload | Mass - Basic | Kilograms (kg) | |||
| 1.2.3 | Infrared Sensor | Payload | Mass - Growth Allowance (kg) | Kilograms (kg) | |||
| 1.2.3 | Infrared Sensor | Payload | No. of Production Units per SV | Quantity | |||
| 1.2.3 | Infrared Sensor | Payload | Aperture size | Millimeters | |||
| 1.2.3 | Infrared Sensor | Payload | Transmit Power | Watts (W) | |||
| 1.2.3 | Infrared Sensor | Payload | Data Rate | Mbps | |||
| 1.2.3 | Infrared Sensor | Payload | Current TRL | List | |||
| 1.2.3 | Infrared Sensor | Payload | |||||
| 1.2.4 | Optical Communications Terminals | Payload | Mass - Basic | Kilograms (kg) | By terminal; sum of all subsystems | ||
| 1.2.4 | Optical Communications Terminals | Payload | Mass - Growth Allowance (kg) | Kilograms (kg) | |||
| 1.2.4 | Optical Communications Terminals | Payload | No. of Production Units per SV | Quantity | |||
| 1.2.4 | Optical Communications Terminals | Payload | Aperture size | Millimeters | |||
| 1.2.4 | Optical Communications Terminals | Payload | Transmit Power | Watts (W) | |||
| 1.2.4 | Optical Communications Terminals | Payload | Data Rate | Mbps | |||
| 1.2.4 | Optical Communications Terminals | Payload | Current TRL | List | TRL 1 - TRL 9; PL Level assessment | ||
| 1.2.5 | Ka Band Communications Payload | Payload | Mass - Basic | Kilograms (kg) | |||
| 1.2.5 | Ka Band Communications Payload | Payload | Mass - Growth Allowance (kg) | Kilograms (kg) | |||
| 1.2.5 | Ka Band Communications Payload | Payload | No. of Production Units per SV | Quantity | |||
| 1.2.5 | Ka Band Communications Payload | Payload | Current TRL | List | TRL 1 - TRL 9; PL Level assessment | ||
| 1.2.5 | Ka Band Communications Payload | Payload | Frequency (Downlink/Uplink/Crosslink) | Megahertz | By Type of Antenna | ||
| 1.2.5 | Ka Band Communications Payload | Payload | Data Rate | Mbps | |||
| 1.2.5 | Ka Band Communications Payload | Payload | Transmit Power | Watts (W) | |||
| 1.2.5 | Ka Band Communications Payload | Payload | Diameter | Centimeters (cm) | By Type of Antenna | ||
| 1.2.5 | Ka Band Communications Payload | Payload | Antenna Type | List | ESA or Parabolic | ||
| 1.2.6 | Networking and Encryption | Payload | Mass - Basic | Kilograms (kg) | |||
| 1.2.6 | Networking and Encryption | Payload | Mass - Growth Allowance (kg) | Kilograms (kg) | |||
| 1.2.6 | Networking and Encryption | Payload | No. of Production Units per SV | Quantity | |||
| 1.2.6 | Networking and Encryption | Payload | Current TRL | List | TRL 1 - TRL 9; PL Level assessment | ||
| 1.2.6 | Networking and Encryption | Payload | Data Rate | Mbps | |||
| 1.2.7 | Payload Other | Payload | Mass - Basic | Kilograms (kg) | |||
| 1.2.7 | Payload Other | Payload | Mass - Growth Allowance (kg) | Kilograms (kg) | |||
| 1.2.7 | Payload Other | Payload | No. of Production Units per SV | Quantity | |||
| 1.2.7 | Payload Other | Payload | Current TRL | List | TRL 1 - TRL 9; PL Level assessment | ||
| 1.2.7 | Payload Other | Payload | Data Rate | Mbps | |||
| 1.4.2 | Hardware | Ground Element | No. of Locations where HW is deployed | List | Specify location | ||
| 1.5.2 | LV Adapter/Dispenser | Launch | Mass | Kilograms (kg) | |||
| DRAFT DD FORM 2794 (PAGE 8), TECHNICAL PARAMETER REQUIREMENTS, JANUARY 2021 |
File details come from the government source that posted it. Updated .