9. DD2794_Cost and Software Reporting Plan_AF-24-M-C1_20240510.xls
XLS spreadsheet 110 KB Posted
- Attached to
- Space Development Agency (SDA) Advanced Fire Control Ground Infrastructure (AFCGI) Federal contract opportunity
- Solicitation number
- FA240124R0001
- Issued by
- Department of the Air Force
About this file
This document is a Cost and Software Data Reporting (CSDR) Plan for the Advanced Fire Control Ground Infrastructure (AFCGI) contract. The CSDR plan provides detailed requirements for the contractor to report cost, software, and technical data to the government throughout the contract performance.
Key details include:
- The AFCGI contract is for the Space Development Agency's Advanced Fire Control (AFC) program, which will deliver integrated space and ground elements to demonstrate advanced fire control missions.
- The CSDR plan requires the contractor to report both initial and annual cost, software, and technical data reports at various milestones and events from contract award through final delivery.
- Specific reporting requirements are defined, including work breakdown structure elements, cost categories, software sizing metrics, and technical parameters.
- The plan provides instructions on CSDR plan preparation, submission events and dates, cost accounting requirements, and CSDR readiness review procedures.
View the file
Other files for this federal contract opportunity
| File | Type | Posted |
|---|---|---|
| 10. AFCGI Questions and Answers 10 July 2024.pdf | ||
| 10. AFCGI Questions and Answers.pdf | ||
| 0. AFCGI Cover Letter FA240124R0001.docx | DOCX document | |
| 00. SF33 FA240124R0001_Solicitation (Model Contract).docx | DOCX document | |
| 4b. AFCGI Small Business Participation.docx | DOCX document | |
| 7. AFCGI DD Form 1423 Contract Data Requirements List (CDRLs).docx | DOCX document | |
| 4. AFCGI Section L-Proposal Instructions.docx | DOCX document | |
| 4a. AFCGI Past Performance Questionnaire (PPQ).docx | DOCX document | |
| 4d. Cost-Price Template (Priced).xlsx | XLSX spreadsheet | |
| 5. AFCGI Section M Evaluation Factors.docx | DOCX document | |
| 6. AFCGI GFX_GFI List.docx | DOCX document | |
| 4c. AFCGI Resume Template.docx | DOCX document | |
| 4f. Personnel & Facilities Template.docx | DOCX document |
Show all 13
On GovTribe
Work with this file on GovTribe
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
DD Form 2794, Pg 1 (METADATA)
| COST AND SOFTWARE DATA REPORTING PLAN | OMB No. 0704-0671 |
| The public reporting burden for this collection of information is estimated to average 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-0671). Respondents should be aware that notwithstanding any other provision of law, no person shall be subject to any penalty for failing to comply with a collection of information if it does not display a currently valid OMB control number. |
PLEASE DO NOT RETURN YOUR COMPLETED FORM TO THE ABOVE ORGANIZATION.
| 1a. PROGRAM NAME | ||
| SDA Advanced Fire Control (AFC) Ground Segment | ||
| 1b. PHASE/MILESTONE (check all that apply) | ||
| Pre-A | ||
| A | ||
| X | B | |
| C-LRIP | ||
| C-FRP | ||
| O&S | ||
| 1c. PRIME MISSION PRODUCT | ||
| Advanced Fire Control Ground Infrastructure (AFCGI) | ||
| 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) | ||
| 20240510 | ||
| 5. LAST APPROVED PLAN DATE (YYYYMMDD) | ||
| 6a. GOVERNMENT PLAN POINT OF CONTACT (POC) NAME (Last, First, M.) | ||
| Otteson, Heather | ||
| 6b. ADDRESS (Include ZIP Code) | ||
| Pentagon | ||
| 6c. TELEPHONE NUMBER (Include Area Code) | ||
| (771) 221-0299 | ||
| 6d. E-MAIL ADDRESS | ||
| heather.f.otteson.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) | ||
| TBD - (AF-24-M-C1) | ||
| 9c. APPROPRIATION (check all that apply) | ||
| X | RDT&E | |
| X | PROCUREMENT | |
| X | O&M | |
| FMS | ||
| WCF | ||
| OTHER | ||
| 10a. APPROVED PLAN NUMBER | ||
| AF-24-M-C1 | ||
| 10b. APPROVED PLAN REVISION NUMBER | ||
| 10c. APPROVED PLAN REQUIREMENTS | ||
| X | 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 | ||
| X | FLEXFILE | |
| LEGACY DD 1921 SERIES | ||
| DRAFT DD FORM 2794 (PAGE 1), METADATA, JANUARY 2019 | PREVIOUS EDITION IS OBSOLETE |
heather.f.otteson.civ@mail.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 | Advanced Fire Control Ground Infrastructure (AFCGI) | X | |
| 1.1 | 2 | SEIT/PM and Support Equipment | X | |
| 1.1.1 | 3 | Systems Engineering | X | X |
| 1.1.2 | 3 | Assembly, Integration and Test | X | X |
| 1.1.3 | 3 | Program Management | X | X |
| 1.2 | 2 | Space Vehicle (N/A) | X | X |
| 1.3 | 2 | Ground Operations and Processing | X | |
| 1.3.1 | 3 | SEIT/PM and Support Equipment | X | X |
| 1.3.2 | 3 | COTS Hardware | X | X |
| 1.3.3 | 3 | Custom Hardware 1...n (Specify) | X | X |
| 1.3.4 | 3 | Ground Function Software | X | |
| 1.3.4.1 | 4 | SEPM | X | X |
| 1.3.4.2 | 4 | Assembly, Integration and Test | X | X |
| 1.3.4.3 | 4 | Support Equipment | X | X |
| 1.3.4.4 | 4 | Ground Function SW Release 1..n (Specify) | X | |
| 1.3.4.4.1 | 5 | Ground Segment Network Communications, Infrastructure, And Connectivity | X | |
| 1.3.4.4.1.1 | 6 | Enterprise Devsecops And Integration Support Services | X | X |
| 1.3.4.4.2 | 5 | Enterprise Services And Capabilities Development | X | |
| 1.3.4.4.2.1 | 6 | Data Management | X | X |
| 1.3.4.4.2.2 | 6 | Time Referencing | X | X |
| 1.3.4.4.2.3 | 6 | Health And Status Monitoring | X | X |
| 1.3.4.4.3 | 5 | Mission Services And Capabilities Development | X | |
| 1.3.4.4.3.1 | 6 | Network Management Services And Capabilities | X | X |
| 1.3.4.4.3.2 | 6 | Ground Resources Management (GRM) | X | X |
| 1.3.4.4.3.3 | 6 | Mission Management | X | X |
| 1.3.4.4.3.4 | 6 | Mission Data Processing | X | X |
| 1.3.4.4.3.5 | 6 | Mission Flight Dynamics | X | X |
| 1.3.4.4.3.6 | 6 | Common Operational Picture | X | X |
| 1.3.4.5 | 4 | Pre-Operations Maintenance 1..n (Specify) | X | X |
| 1.3.5 | 3 | Pre-Operations Mission Support | X | X |
| 1.4 | 2 | Ground Entry Point (GEP) 1...n (Specify) | X | |
| 1.4.1 | 3 | SEIT/PM and Support Equipment | X | X |
| 1.4.2 | 3 | Antenna 1...n (Specify) | X | X |
| 1.4.3 | 3 | Optical Communication Assembly 1...n (Specify) | X | X |
| 1.4.4 | 3 | RF Electronics Band 1...n (Specify) | X | X |
| 1.4.5 | 3 | Timing 1...n (Specify) | X | X |
| 1.4.6 | 3 | Baseband-Network 1...n (Specify) | X | X |
| 1.4.7 | 3 | Monitor and Control Hardware 1...n (Specify) | X | X |
| 1.4.8 | 3 | GEP Software | X | X |
| 1.4.9 | 3 | Pre-Operations Mission Support | X | X |
| 1.5 | 2 | Facilities 1...n (Specify) | X | |
| 1.5.1 | 3 | SEIT/PM and Support Equipment | X | X |
| 1.5.2 | 3 | Site Preparation | X | X |
| 1.5.3 | 3 | Landscape | X | X |
| 1.5.4 | 3 | Buildings 1...n (Specify) | X | X |
| 1.5.5 | 3 | Equipment and Building Fit Out 1...n (Specify) | X | X |
| 1.5.6 | 3 | Pre-Operations Maintenance 1...n (Specify) | X | X |
| 1.6 | 2 | System Test and Evaluation | X | |
| 1.6.1 | 3 | Developmental Test and Evaluation | X | X |
| 1.6.2 | 3 | Operational Test and Evaluation | X | X |
| 1.6.3 | 3 | Other Test and Evaluation | X | X |
| 1.7 | 2 | Training | X | X |
| 1.8 | 2 | Data | X | X |
| 1.9 | 2 | Peculiar Support Equipment | X | X |
| 1.10 | 2 | Common Support Equipment | X | X |
| 1.11 | 2 | Operational/Site Activation | X | |
| 1.11.1 | 3 | System Assembly, Installation, and Checkout | X | X |
| 1.11.2 | 3 | Contractor Technical Support | X | X |
| 1.11.3 | 3 | Site Construction | X | X |
| 1.11.4 | 3 | Site Conversion | X | X |
| 1.11.5 | 3 | Interim Contractor Support (ICS) | X | X |
| 1.12 | 2 | Contractor Logistics Support (CLS) | X | X |
| 1.13 | 2 | Industrial Facilities | X | X |
| 1.14 | 2 | Initial Spares and Repair Parts | X | X |
| 1.15 | 2 | Packaging, Handling, Storage, and Transportation (PHS&T) | 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 |
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) | AFCGI Initial Cost Report | Initial | 20250131 | 20250402 | ||
| 2 | Technical Data Report | AFCGI Initial Technical Report | Initial | 20250131 | 20250402 | ||
| 3 | Cost and Hour Report (FlexFile) | AFCGI Annual Cost Report #1 | Interim | 20260131 | 20260402 | ||
| 4 | Technical Data Report | AFCGI Annual Technical Report #1 | Interim | 20260131 | 20260402 | ||
| 5 | Cost and Hour Report (FlexFile) | AFCGI Annual Cost Report #2 | Interim | 20270131 | 20270402 | ||
| 6 | Technical Data Report | AFCGI Annual Technical Report #2 | Interim | 20270131 | 20270402 | ||
| 7 | Cost and Hour Report (FlexFile) | AFCGI Annual Cost Report #3 | Interim | 20280131 | 20280401 | ||
| 8 | Technical Data Report | AFCGI Annual Technical Report #3 | Interim | 20280131 | 20280401 | ||
| 9 | Cost and Hour Report (FlexFile) | AFCGI Annual Cost Report #4 | Interim | 20290131 | 20290402 | ||
| 10 | Technical Data Report | AFCGI Annual Technical Report #4 | Interim | 20290131 | 20290402 | ||
| 11 | Cost and Hour Report (FlexFile) | AFCGI Final Cost Report | Final | 20291231 | 20300302 | ||
| 12 | Technical Data Report | AFCGI Final Technical Report | Final | 20291231 | 20300302 | ||
| 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 |
| The contractor must report costs on all CLINs associated with the AFCGI 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. |
| a. CSDR PLAN REMARKS & PREPARATION INSTRUCTIONS |
| 1. Costs reported against this CSDR plan shall be cumulative in nature (i.e., each submission shall report any and all costs incurred on and prior to the submission’s “AS OF DATE” (block 14.e)). |
| i. WBS Element Names (block 11.c) Ending with "1...n (Contractor Shall Specify)": The contractor shall extend and specify (i.e., include additional WBS elements determined by the contractor) in order to provide additional insight into the contractor's technical approach or design. The additional WBS elements shall be developed in accordance with the WBS guidelines included in MIL-STD-881F (or latest version). |
| ii. The contractor may extend any WBS element in accordance with guidelines included in MIL-STD-881F (or latest version). Any changes to WBS, Order/Lot, End Item, and/or Period of Performance must be reported to the government prior to submission or immediately, with revised CSDR Plan, must be approved by the CSDR Plan approval authority. |
| b. SUBMISSION EVENTS & DATES |
| 1. Deliverable Preparation Instructions by AS OF and DUE Dates: All CSDR deliverable “AS OF DATE[S]” and “DUE DATE[S]” listed in blocks 14.e and 14.f are identified for planning purposes only. Submission dates are subject to change and are determined in accordance with the event drivers as identified below: |
| i. All “DUE DATE” requirements are equal to the “AS OF DATE” plus 60 calendar days. If the calculated “DUE DATE” does not fall on a regular business day, the “DUE DATE” will be the next regular business day on the contractor’s accounting calendar. |
| ii. “Final” Submission Events must meet both of the following two conditions: |
Condition 1: The final end item(s) has been delivered and accepted by the government (e.g., as evidenced by a completed DD-250) or higher tier contractor in the case of a subcontractor, and
Condition 2: 95% or more of all ATD costs associated with the Subtotal, G&A and FCCOM have been incurred relative to all costs the reporting entity expects to incur for each and every Order/Lot (defined in Item 4 of Data Group B) associated with the contract Subtotal, G&A, FCCOM and UB.
| iii. If the Contract period of performance is extended by more than six months, or if the scope of work is modified to include work not otherwise covered by the CSDR Plan, the government may modify the CSDR Plan to require additional submission events and add additional WBS elements in order to ensure the accurate and complete collection of cost data associated with the modified contract. |
| c. TECHNICAL DATA REPORT |
| 1. Include only UNCLASSIFIED/CUI information in Technical Data Report deliverables submitted to CADE. Notify the Government if any values associated with the Technical Parameter Requirements are classified. |
| d. RESOURCE DISTRIBUTION TABLE (RDT) |
| 1. Submissions of the Resource Distribution Table (RDT) are required under the following conditions: |
| i. An RDT shall be delivered no later than seven calendar days before the “CSDR Readiness Review”. Prepare this submission of the RDT, in accordance with the RDT Instructions on the CADE website, at FAC/EAC value and utilizing the instructions at Block15.a.4.i.This copy of the RDT will be used during the “CSDR Readiness Review” in order to identify which subcontractors will be required to provide CSDR reporting via electronic submission of deliverables directly to CADE and which subcontractors may qualify for a CSDR direct reporting subcontractor waiver. |
| ii. The contractor must notify the government program office immediately of the contractor identifying that a subcontractor who, at the time of initial subcontractor award, was not anticipated to qualify for direct subcontractor CSDR reporting via electronic submission of deliverables directly to CADE but is subsequently anticipated to meet the CSDR direct reporting subcontractor threshold value due to changes to scopes of work, end-item design, subcontractor/supplier, or subcontract price changes since initial contract award (unless the newly identified subcontractor has already been issued a subcontractor reporting waiver associated with this contract). |
| e. RELATIONSHIP/USE OF COST ACCOUNTING STANDARDS (CAS) |
| 1. The contractor shall provide a description of significant accounting systems or CAS changes and how those changes effect the latest CSDR deliverable or the ability to compare CSDR deliverables provided before/after the accounting system/CAS revision. The contractor shall provide the description within the submission remarks of the FlexFile deliverable. |
| f. CSDR READINESS REVIEW |
| 1. The contractor shall host a CSDR-RR 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 satisfies the CSDR requirements found in DODM 5000.04 and this CSDR Plan. Reference the CADE website for instructions and additional information: https://cade.osd.mil/policy/csdr-timeline |
| 2. The contractor and CWIPT will also review the initial submission of the "Resource Distribution Table (RDT)", in order to finalize which subcontractors will be required to provide CSDR reporting and electronic submission of deliverables directly to Cost Assessment Data Enterprise (CADE), and which subcontractors may qualify for a CSDR direct reporting subcontractor waiver. |
| 3. The CSDR-RR shall be held within 60 days of contract award or the start of work meeting on a date mutually agreed to by the CWIPT and the contractor. This meeting has an anticipated duration of one business day. |
| g. IRAD EFFORT |
| 1. 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. |
| h. SPECIAL INSTRUCTIONS |
| 1. The reporting entity 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).” |
| 2. The reporting entity is instructed to report costs for all prior and future contract years, per Page 3 of the DD 2794, in order to capture the entire contract cost. Data submitted in each CSDR deliverable shall reflect cumulative data from the contract Period of Performance Start Date through the As Of Date indicated on Page 3 of the DD 2794. Please note that the reporting entity may use their accounting month end date closest to the As Of Date listed on Page 3. |
| 3. Prime contractors are responsible for flowing down CSDR requirements to all subcontractors who meet the reporting thresholds specified in the DoDI 5000.73, or as required by the CWIPT. This includes requiring subcontractors to electronically report directly to the CADE Portal using the CSDR Submit-Review System. The prime contractor shall be required to work with the CWIPT and all appropriate subcontractors to prepare separate subcontract CSDR plans for submission to CAPE for approval. |
| Summary |
| The definitions are intended for application to all levels of integration, or WBS indenture, within the ground system: parts, materials and labor; hardware components, subassemblies, major assemblies and end items (“boxes”); computer software configuration items (CSCIs) and components (CSCs); and subsystems, system segments, and the system as a whole. |
| General Definitions |
| Acquisition costs for development of the ground system are classified as nonrecurring irrespective of the milestone, phase or gate of the overall program or the WBS element in question. So NRE costs include initial development, upgrades, and improvements to hardware, software and facilities that make up the system. Thus, requirements definition, design, engineering analyses, development hardware and software, development testing, and development support hardware and software are nonrecurring efforts. |
| Acquisition costs for production of ground operations and processing centers (GOPCs), Ground Entry Points (GEPs), along with associated facilities, and components thereof; for spares; and for replicated spacecraft components used in ground testing and simulators are classified as recurring. Costs for installation of previously developed software in ground stations are recurring. Similarly, costs for acquisition and installation of commercial off-the-shelf software (COTS) for operational use in ground stations are recurring. |
| 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, GEPs and other system segments, elements, interfaces; support equipment used for development; software development; development of upgrades and improvements (despite magnitude) |
| Recurring (REC) general examples: Ground hardware production and installation; Construction of operational ground facilities; installation of developed and COTS software in GOPCs and GEPs; replicated space hardware in GOPCs and GEPs; spares for spacecraft, GOPCs and GEPs; test equipment, software and procedure maintenance; and system operation and maintenance |
| The software definitions apply to ground station operational software, development software, and ground test software for development and production. Ground support equipment (GSE) is addressed below. It is usually treated separately from assembly, integration and test for cost collection and estimating purposes. |
| 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
| Recurring Cost: |
| Installation and check-out of developed S/W in ground stations |
If first-time S/W I&T is performed at ground station, then it is NRE Maintenance of S/C production & test support S/W after first launch Acquisition of stand-alone and bundled COTS S/W in operational system Maintenance of flight S/W (usually embedded in acquisition contracts)"
| 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
| Recurring Cost: |
| Maintenance of specs, ICDs, plans & budgets -- after all TBDs and TBRs are removed |
Performance, S/W maintenance productivity metrics Analysis updates System configuration control after design completion Mass, power, link margin & reliability budgets – supporting production Support for production testing, rehearsals and operational test and evaluation Product assurance Requirements verification after design completion Launch readiness reviews, support for product acceptance Technical change management (RFIs, ECPs, etc.) -- supporting recurring portions of changes and recurring- only changes
| 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
| Recurring Cost: |
| Space vehicle assembly, integration and acceptance testing |
Acceptance test analysis and reports Integration and test of previously-developed software –in GOPCs, GEPs
| 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
| Recurring Cost: |
| 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
| Recurring Cost: | |
| System operation costs – operations, training, systems engineering & management staff | |
| Hardware maintenance & recapitalization |
Software maintenance – including COTS license costs Software modifications/fixes after IOC Reproduction and updating of technical data and manuals Procurement/production of hardware spares Rehearsals and initialization of space vehicles
| Pre-Operations Support Definitions |
| Pre-Operations Maintenance 1..n (Specify): |
| These elements contain all the resources related to the pre-operations (Pre-Ops) maintenance (software updates) of Bus Flight Software. This function begins with the acceptance of the Bus Software elements and ends with the start of Operations. |
| Pre-Operations Mission Support: |
| This element includes all the resources required for the operation of the Ground system prior to turn-over. |
Includes, for example:
a. On-orbit testing; routine monitoring of Ground system equipment health and status
b. Fault detection
c. Anomaly investigation and resolution. (The Mission Support period typically begins after installation and a specified time prior to launch and ends when the Space Vehicle achieves initial operational capability.)
DRAFT DD FORM 2794 (PAGE 4), REMARKS, JANUARY 2019 PREVIOUS EDITION IS OBSOLETE
DD Form 2794, Pg 5 (SCOPE DEF)
| COST AND SOFTWARE DATA REPORTING PLAN | |||||
| INTRA-CONTRACT SCOPE REPORTING DEFINITION | |||||
| 16. ORDERS/LOTS | |||||
| a. ID | b. NAME | c. PHASE/MILESTONE | |||
| 1 | AFCGI | B | |||
| 17. END ITEMS | |||||
| a. ID | b. NAME | ||||
| 1...n | AFCGI End Items (1...n) | ||||
| 18. UNIT/SUBLOT REPORTING AND UNIT SEQUENCING REQUIREMENTS | |||||
| a. ORDER/LOT ID | b. END ITEM ID | c. UNIT/SUBLOT REPORTING | |||
| (X if applicable) | d. UNIT SEQUENCING |
(X if applicable)
DRAFT DD FORM 2794 (PAGE 5), INTRA-CONTRACT SCOPE, JANUARY 2019
DD Form 2794, Pg 9a (TECH RQTS)
| COST AND SOFTWARE DATA REPORTING PLAN - TECHNICAL PARAMETER REQUIREMENTS | ||||||||||
| TECHNICAL PARAMETER REQUIREMENTS | ||||||||||
| 29. WBS | ||||||||||
| ELEMENT CODE | 30. WBS ELEMENT NAME | 31. ITEM TYPE | 32. TECHNICAL PARAMETER | |||||||
| a. PARAMETER NAME | b. UNIT OF MEASURE | c. UNIT OF MEASURE QUALIFIER | d. REPEATABLE | e. DEFINITION | f. REMARKS | |||||
| 1.0 | Advanced Fire Control Ground Infrastructure (AFCGI) | Milestone Date | Contract Award | Date | ||||||
| 1.0 | Advanced Fire Control Ground Infrastructure (AFCGI) | Milestone Date | System PDR | Date | ||||||
| 1.0 | Advanced Fire Control Ground Infrastructure (AFCGI) | Milestone Date | System CDR | Date | ||||||
| 1.0 | Advanced Fire Control Ground Infrastructure (AFCGI) | Ground | Factory Locations | List | ||||||
| 1.0 | Advanced Fire Control Ground Infrastructure (AFCGI) | Ground | Testbed Locations | List | ||||||
| 1.3 | Ground Operations and Processing | Milestone Date | Authority to Proceed (ATP) Date | |||||||
| 1.3 | Ground Operations and Processing | Milestone Date | Physical Configuration Audit / Functional Configuration Audit (per site) | |||||||
| 1.3 | Ground Operations and Processing | GroundProcess | Number of GOPC Sites | Quantity | ||||||
| 1.3 | Ground Operations and Processing | GroundProcess | Installation Locations | Quantity | ||||||
| 1.3 | Ground Operations and Processing | SysEng | Number of Requirement Document - "Shalls" | Quantity | Shalls | |||||
| 1.3 | Ground Operations and Processing | Heritage | Predecessor System | Descriptor | ||||||
| 1.3 | Ground Operations and Processing | Heritage | New Design | Percent | ||||||
| 1.3.2 | COTS Hardware | GroundProcess | Number of Workstations | Quantity | Workstations | |||||
| 1.3.2 | COTS Hardware | GroundProcess | Number of Enclosures | Quantity | Enclosures | |||||
| 1.3.2 | COTS Hardware | GroundProcess | Number of Electronic Racks | Quantity | Racks | |||||
| 1.3.2 | COTS Hardware | GroundProcess | Number of Wide Area Networks | Quantity | Networks | |||||
| 1.3.2 | COTS Hardware | GroundProcess | Data Storage | Terabytes | ||||||
| 1.3.2 | COTS Hardware | GroundProcess | Number of Servers | Quantity | Servers | |||||
| 1.3.4.4 | Ground Function SW Release | SoftwareNonSRDR | New Code - Human Generated | SLOC | Actual to Date | The delivered size of the product developed that is human generated. | ||||
| 1.3.4.4 | Ground Function SW Release | SoftwareNonSRDR | New Code - Auto-Generated | SLOC | Actual to Date | The delivered size of the product developed that is auto-generated. | ||||
| 1.3.4.4 | Ground Function SW Release | SoftwareNonSRDR | New Code - Human Generated | SLOC | Estimate at Complete | The delivered size of the product developed that is human generated. | ||||
| 1.3.4.4 | Ground Function SW Release | SoftwareNonSRDR | New Code - Auto-Generated | SLOC | Estimate at Complete | The delivered size of the product developed that is auto-generated. | ||||
| 1.3.4.4 | Ground Function SW Release | SoftwareNonSRDR | Reused Code - Actual to Date | SLOC | Actual to Date | Code from external sources (government-furnished or otherwise) that is included and reused without modification. | ||||
| 1.3.4.4 | Ground Function SW Release | SoftwareNonSRDR | Reused Code - Estimate at Complete | SLOC | Estimate at Complete | Code from external sources (government-furnished or otherwise) that is included and reused without modification. | ||||
| 1.3.4.4 | Ground Function SW Release | SoftwareNonSRDR | Reused Code - AAF% | SLOC | Adaptation Adjustment Factor (AAF) - top-level percentage of effort of adapting the reused code to the new system relative to a line of new code. | |||||
| 1.3.4.4 | Ground Function SW Release | SoftwareNonSRDR | Modified Code - Actual to Date | SLOC | Actual to Date | Modified code is defined as pre-developed code that can be incorporated in the software component with a significant amount of effort, but less effort than required for a newly developed code. | ||||
| 1.3.4.4 | Ground Function SW Release | SoftwareNonSRDR | Modified Code - Estimate at Complete | SLOC | Estimate at Complete | Modified code is defined as pre-developed code that can be incorporated in the software component with a significant amount of effort, but less effort than required for a newly developed code. | ||||
| 1.3.4.4 | Ground Function SW Release | SoftwareNonSRDR | Modified Code - AAF% | SLOC | Adaptation Adjustment Factor (AAF) - top-level percentage of effort of adapting the modified code to the new system relative to a line of new code. | |||||
| 1.3.4.4 | Ground Function SW Release | SoftwareNonSRDR | Software Requirements Count - New | SRS | Shalls | The estimated or actual number of added or new requirements satisfied by the developed software product at the completion of the release | Specify estimate or actual | |||
| 1.3.4.4 | Ground Function SW Release | SoftwareNonSRDR | Software Requirements Count - Modified | SRS | Shalls | The estimated or actual number of modified requirements satisfied by the developed software product at the completion of the release | Specify estimate or actual | |||
| 1.3.4.4 | Ground Function SW Release | SoftwareNonSRDR | Software Requirements Count - Deleted | SRS | Shalls | The estimated or actual number of requirements deleted, and thus not included in the release | Specify estimate or actual | |||
| 1.4 | Ground Entry Point (GEP) 1..n | SysEng | Number of Requirement Document - "Shalls" | Quantity | Shalls | |||||
| 1.4 | Ground Entry Point (GEP) 1..n | Milestone Date | Authority to Proceed (ATP) Date | Descriptor | ||||||
| 1.4 | Ground Entry Point (GEP) 1..n | Milestone Date | Physical Configuration Audit / Functional Configuration Audit (per site) | Descriptor | ||||||
| 1.4 | Ground Entry Point (GEP) 1..n | GEP | Number of GEP Sites | Quantity | ||||||
| 1.4 | Ground Entry Point (GEP) 1..n | GEP | Installation Locations | Descriptor | ||||||
| 1.4 | Ground Entry Point (GEP) 1..n | Heritage | New Design | Percent | ||||||
| 1.4 | Ground Entry Point (GEP) 1..n | Heritage | Predecessor System | Descriptor | ||||||
| 1.4.2 | Antenna 1...n | Antenna | Number of Antennas per Site | Quantity | ||||||
| 1.4.2 | Antenna 1...n | PhysicalElec | Power - Maximum Consumption Rate | Kilowatts | Per Antenna Face | |||||
| 1.4.2 | Antenna 1...n | Antenna | Frequency Range | Megahertz | Instantaneous | |||||
| 1.4.2 | Antenna 1...n | Antenna | Aperture - Antenna (m) | Meters | ||||||
| 1.4.2 | Antenna 1...n | Antenna | Number of Sub Arrays | Quantity | ||||||
| 1.4.2 | Antenna 1...n | Antenna | Bandwidth | Gigahertz | ||||||
| 1.4.2 | Antenna 1...n | Antenna | Type of Steering | List | Beams | |||||
| 1.4.2 | Antenna 1...n | Antenna | Technology Type | Descriptor | ||||||
| 1.4.2 | Antenna 1...n | Antenna | Operational Mode | List | ||||||
| 1.4.2 | Antenna 1...n | Antenna | Array Beams | Quantity | ||||||
| 1.4.2 | Antenna 1...n | Antenna | Number of Array Active Elements | Quantity | ||||||
| DRAFT DD FORM 2794 (PAGE 9a), TECHNICAL PARAMETER REQUIREMENTS, JANUARY 2019 |
DD Form 2794, Pg 9b (TECH RQTS)
| COST AND SOFTWARE DATA REPORTING PLAN - TECHNICAL PARAMETER REQUIREMENTS | ||
| 33. TECHNICAL PARAMETER REQUIREMENTS (LIST ITEMS) | ||
| a. ITEM TYPE | b. PARAMETER NAME | c. LIST ITEMS |
| Antenna | Type of Steering | Electronically Scanned |
| Antenna | Type of Steering | Mechanically Scanned |
| Antenna | Type of Steering | Other |
| Antenna | Operational Mode | Active |
| Antenna | Operational Mode | Passive |
| DRAFT DD FORM 2794 (PAGE 9b), TECHNICAL PARAMETER REQUIREMENTS, JANUARY 2019 |
File details come from the government source that posted it. Updated .