Attachment 0015 - Cost and Software Data Reporting (CSDR) Plan - 20 July 2021.xlsx
XLSX spreadsheet 50 KB Posted
- Attached to
- Combat Net Radio (CNR) Solicitation
- Solicitation number
- W15P7T-21-R-0009
About this file
This document package includes a Cost and Software Data Reporting (CSDR) Plan and details for a federal contract opportunity to procure a modernized Combat Net Radio (CNR) system.
The CSDR Plan outlines reporting requirements for cost, software, and technical data for the CNR program. It specifies Work Breakdown Structure (WBS) elements and functional categories for reporting actual costs and hours. It also defines recurring and non-recurring cost reporting and establishes submission events over the life of the contract, with the final report due at contract completion. The plan identifies the Army Program Manager Tactical Radios as the government point of contact.
The related federal contract opportunity is a solicitation issued by the Army Contracting Command to procure a modernized CNR Receiver Transmitter to replace existing radios. It provides an overview of the requirement and refers to various attachments not publicly posted, related to the statement of work, life cycle sustainment plan, and program schedule. The solicitation identifies submission dates and evaluation criteria. Interested vendors must verify eligibility to access controlled documents before the Army will release full solicitation details. The Department of the Army Materiel Command is the contracting agency.
View the file
Other files
Show all 47
On GovTribe
Work with this file
- 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 | |
| Combat Net Radio (CNR) | |
| 1b. PHASE/MILESTONE (check all that apply) | |
| Pre-A | |
| A | |
| B | |
| C-LRIP | |
| C-FRP | |
| X | O&S |
| 1c. PRIME MISSION PRODUCT | |
| Combat Net Radio (CNR) | |
| 1d. ACQUISITION CATEGORY (ACAT) | |
| Pre-ACAT | |
| X | ACAT I (MDAP) |
| ACAT IA (MAIS) | |
| ACAT II | |
| ACAT III | |
| Other | |
| 2. COMMODITY TYPE | |
| Electronic System | |
| 3. PLAN ITERATION TYPE | |
| X | INITIAL |
| REVISION | |
| 4. CURRENT SUBMISSION DATE (YYYYMMDD) |
| 5. LAST APPROVED PLAN DATE (YYYYMMDD) |
| NA |
| 6a. GOVERNMENT PLAN POINT OF CONTACT (POC) NAME (Last, First, M.) |
| Ailes, Kevin C |
| 6b. ADDRESS (Include ZIP Code) |
| 6560 Surveillance Loop |
APG, MD 21005
| 6c. TELEPHONE NUMBER (Include Area Code) | |
| 443-395-2956 | |
| 6d. E-MAIL ADDRESS | |
| kevin.c.ailes.civ@mail.mil | |
| 7. PLAN TYPE | |
| GOVERNMENT | |
| X | CONTRACT (PRIME) |
| CONTRACT (SUB) | |
| 8. PLAN GOVERNMENT PREPARING ORGANIZATION | |
| Program Manager Tactical Radios |
Product Manager Waveforms
| 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: | |
| X | CBDR REQUIRED FOR THIS ORGANIZATION |
| 9b. CONTRACT NUMBER (List all that apply, separated by commas) | |
| TBD | |
| 9c. APPROPRIATION (check all that apply) | |
| RDT&E | |
| X | PROCUREMENT |
| O&M | |
| FMS | |
| WCF | |
| OTHER | |
| 10a. APPROVED PLAN NUMBER | |
| TBD | |
| 10b. APPROVED PLAN REVISION NUMBER | |
| TBD | |
| 10c. APPROVED PLAN REQUIREMENTS | |
| X | AT COMPLETION COSTS FOR STANDARD FUNCTIONAL CATEGORIES (FlexFile) |
| X | AT COMPLETION COSTS FOR RECURRING/NONRECURRING (FlexFile only) |
| X | TECHNICAL DATA REQUIRED |
| 10d. COST REPORT TYPE | |
| X | FLEXFILE |
| LEGACY DD 1921 SERIES |
DRAFT DD FORM 2794 (PAGE 1), METADATA, JANUARY 2019 PREVIOUS EDITION IS OBSOLETE
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 | CNR - Combat Net Radio | X | X | |
| 1.1 | 2 | Prime Mission Product (PMP) | X | X | X |
| 1.1.1 | 3 | Receiver/Transmitter | X | X | X |
| 1.1.2 | 3 | Vehicle Mount Adapter | X | X | X |
| 1.1.3 | 3 | Battery Box | X | X | X |
| 1.1.4 | 3 | Omni-Directional Antenna | X | X | X |
| 1.1.5 | 3 | External Speaker/Microphone | X | X | X |
| 1.1.6 | 3 | R/T Unit Warranty | X | X | X |
| 1.1.7 | 3 | PMP Radio Integration, Assembly, Test and Checkout | X | X | |
| 1.2 | 2 | Platform Integration, Assembly, Test and Checkout | X | X | |
| 1.3 | 2 | System Engineering | X | X | |
| 1.4 | 2 | Program Management | X | X | |
| 1.5 | 2 | System Test and Evaluation | X | X | |
| 1.6 | 2 | Training | X | X | |
| 1.6.1 | 3 | Equipment | X | X | |
| 1.6.2 | 3 | Services | X | X | |
| 1.6.3 | 3 | Facilities | X | X | |
| 1.7 | 2 | Data | X | X | |
| 1.7.1 | 3 | Technical Publications | X | X | |
| 1.7.2 | 3 | Engineering Data | X | X | |
| 1.7.3 | 3 | Management Data | X | X | |
| 1.7.4 | 3 | Support Data | X | X | |
| 1.7.5 | 3 | Data Depository | X | X | |
| 1.8 | 2 | Peculiar Support Equipment | X | X | |
| 1.9 | 2 | Common Support Equipment | X | X | |
| 1.10 | 2 | Operational/Site Activation | X | X | |
| 1.10.1 | 3 | System Assembly, Installation and Checkout on Site | X | X | |
| 1.10.2 | 3 | Contractor Technical Support | X | X | |
| 1.10.3 | 3 | Sustainment/Interim Contractor Support | X | X | |
| 1.11 | 2 | Industrial Facilities | X | X | |
| 1.12 | 2 | Initial Spares and Repair Parts | X | X | X |
| 1.12.1 | 3 | Receiver/Transmitter | X | X | X |
| 1.12.2 | 3 | Other Components (Batteries, Antennas, Handset, etc.) | X | 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 | CWBS Dictionary | Production CWBS Dictionary | Initial | 20220630 | 20220831 | ||
| 2 | Cost and Hour Report (FlexFile), Quantity Data Report | Production Initial Report | Initial | 20220930 | 20221130 | ||
| 3 | 3 | Cost and Hour Report (FlexFile), Quantity Data Report | Operational Test Units | Interim | 20221130 | 20230228 | |
| 4 | Cost and Hour Report (FlexFile), Quantity Data Report | Annual Report 1 | Interim | 20230630 | 20230831 | ||
| 5 | Cost and Hour Report (FlexFile), Quantity Data Report | Annual Report 2 | Interim | 20240630 | 20240831 | ||
| 6 | Cost and Hour Report (FlexFile), Quantity Data Report | Annual Report 3 | Interim | 20250630 | 20250831 | ||
| 7 | Cost and Hour Report (FlexFile), Quantity Data Report | Annual Report 4 | Interim | 20260630 | 20260831 | ||
| 8 | Cost and Hour Report (FlexFile), Quantity Data Report | Annual Report 5 | Interim | 20270630 | 20270831 | ||
| 9 | Cost and Hour Report (FlexFile), Quantity Data Report | Annual Report 6 | Interim | 20280630 | 20280831 | ||
| 10 | Cost and Hour Report (FlexFile), Quantity Data Report | Annual Report 7 | Interim | 20290630 | 20290831 | ||
| 11 | Cost and Hour Report (FlexFile), Quantity Data Report | Annual Report 8 | Interim | 20300630 | 20300831 | ||
| 12 | Cost and Hour Report (FlexFile), Quantity Data Report | Annual Report 9 | Interim | 20310630 | 20310831 | ||
| 13 | Cost and Hour Report (FlexFile), Quantity Data Report | Annual Report 10 | Interim | 20320630 | 20320831 | ||
| 14 | Cost and Hour Report (FlexFile), Quantity Data Report | Contract Completion (Total Contract Actuals) | Final | 20320630 | 20320831 |
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 |
| 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. |
| NON-RECURRING/RECURRING DEFINITIONS |
| Recurring and Non-Recurring Costs required for all levels: |
| Recurring costs. Repetitive elements of development, investment or sustainment costs that may vary with the quantity being produced or maintained, irrespective of system life cycle phase and appropriation. Recurring cost categories include procurement, and production and maintenance activities; acceptance testing; maintenance and support equipment, training, and data; test articles built to an operational configuration; and certain elements of systems engineering and program management. |
| Examples of Prime Mission Product activities include repetitive costs incurred when building prototype, test systems, or production units to an operational configuration. Examples of Prime Mission Product Hardware activities include Fabrication and assembly of partial/full prototype, test, or production units whether for customer or contractor use; Raw material, purchased parts, equipment associated with the fabrication and assembly of partial/full prototype or test units whether for customer or contractor use; Touch labor, integration and assembly, installation and check out; Engineering support for production unit fabrication, assembly and check out. |
| Examples of Prime Mission Product Software activities include Procurement of stand-alone or bundled COTS software licenses used in an operational system and installation and checkout of developed software into production units. Examples of Systems Engineering activities include Sustaining engineering, logistics support, planning, organizing, monitoring and reporting activities, document maintenance. Examples of Program Management activities include programmatic, financial, contractual, schedule, planning, organizing, and monitoring (quality information assurance, configuration management) activities in support of production unit fabrication, assembly and check out; meetings & efforts in support of supplier, manufacturing & production activities. |
| Nonrecurring costs. Non-repetitive elements of development, investment or sustainment costs that generally do not vary with the quantity being produced or maintained, irrespective of system life cycle phase and the appropriation. Nonrecurring cost categories include product design and development (PD&D) activities, including those for modifications; system test and evaluation (ST&E) including ST&E for modifications; tooling; pre-production or pre-maintenance activities; design and development of support equipment, training, and data; and certain elements of systems engineering and program management. |
| Examples of Prime Mission Product PD&D activities are: Requirements definition, engineering design, analysis & development; Redesign, rework & retest due to design flaws & first time corrective actions; test articles built for testing purposes only (i.e., units that are not production-representative) such as wind tunnel models, and bench and coupon test articles; structural development, static, fatigue, software, and ballistics testing; stress analysis; flight, ground, or sea testing of system properties; redesign as a result of testing; and retesting efforts; All configuration, quality, and data management efforts supporting release activity for first article configuration, delivery & certification; System safety plan, manuals, tech services, & maintenance manual development in support of first article delivery. |
| Examples of hardware design and development activities include material, purchased parts and labor associated with engineering models, operational models, bench, lab articles or partially built units (i.e. units that are not production representative), tooling, and ground support equipment for qualification, structural, static, fatigue or stress testing, and refurbishment of test units; and engineering support including manufacturing engineering, quality engineering, and tool engineering for development unit fabrication, assembly & tests. |
| Examples of software design and development activities include design and development of all software; delivered operational software and software developed to correct deficiencies and add capabilities; Initial integration of COTS and GOTS products into operational configuration; Support for HW-SW integration and test, system level testing; initial integration of COTS and GOTS products into operational configuration; and commercial software licenses for development facilities. System Engineering, Program Management, and Data activities occur throughout the system life cycle and are supportive in nature; as such, these costs take on the characteristics of the underlying activities being performed. |
| Examples of Systems Engineering activities include installation plans or quality inspection plans; requirements definition, allocation and flow-down; creation of specification and Interface Control Documents (ICDs); design and implementation of system security; top level design trade-offs; analyses, studies, and simulations for system performance and effectiveness, reliability, availability, maintainability or survivability; internal & external design review, IPT coordination & integration meetings; Certification & Control documentation; and supplier selection & coordination. Examples of Program Management activities include programmatic, financial, contractual, schedule, planning, organizing, and monitoring (quality information assurance, configuration management) activities in support of development, design & testing efforts. |
| Examples of System Test and Evaluation activities include development of test plans/procedures; subsystem and system level test and integration for developmental articles; test equipment in support of development including for static & fatigue testing, test stands, wind tunnel models, stress analysis, ballistics testing, flight, ground or sea testing of system, redesign from testing, retesting; System/Software Integration Laboratory (SIL) development; and analysis to support verification, validation & certification. Examples of Training activity include initial courseware development and simulator development. Examples of Initial Spares and Repair Parts activity include spare parts and material in support of the nonrecurring subsystem/system level articles. |
| Examples of Support Equipment activity include initial equipment design and test efforts, and test program sets development. Examples of Tooling activity include special test equipment, special tooling, procurement of initial & rate tooling, tool replacement (with the exact same tool) & tool modification (to accommodate product configuration changes). Examples of Operational/Site Activation activity include site planning efforts. |
| 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. | |
| 1921-3 CONTRACTOR BUSINESS DATA REPORT | |
| a. The Contractor Business Data Report is prepared by and for the business entity (e.g., business unit, segment, or site) responsible for submitting the Forward Pricing Rate | Proposal (FPRP) representing the basis for Forward Pricing Rate Agreement (FPRA) negotiations with the government. |
b. Reports are submitted annually at the end of the contractor's fiscal year.
c. Data for Future Years should be reflective of the number of years contained in the most current document, i.e., the FPRP or the FPRA.If the document applies to more than three future years, attach additional future year sheets as required. In the absence of these documents, estimates should be provided for three future years.
d. The existing 1921-3 requires strictly formatted data and necessitates mappings to a government standard, the new DRAFT 1921-3 may be submitted in the contractor’s own format and according to the contractor’s own rate structure, so long as it meets the data requirements in the DRAFT 1921-3 Data Item Description DI-FNCL-81765.
| 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.
| SRDR MAINTENANCE |
| Software Releases are meant to capture the technical information and effort associated with each software release. If a release is identified/definted on the contract and the CSDR plan has not been updated, it is the Reporting Entity's responsibility to submit the technical data, the dollars, and the hours in the SRDR by the appropriate Release(s). The CSDR plan will be revised accordingly to include any identified Releases. |
| CSCIs |
| For Software Release and CSCI WBS Element Names identified in Item 11d. as Subcomponent Release 1..n or Subcomponent Release 1..n CSCI 1..n, the Reporting Entity must specify the specific releases and associated CSCIs at the post award meeting in order to revise the CSDR Plan to reflect the Reporting Entity’s actual releases and associated CSCIs. |
| 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. |
| POST AWARD CONFERENCE (PAC) |
| 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-M-1 (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-M-1, 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.02 and DoDM 5000.04-M-1. |
| 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. |
| SUSTAINMENT |
| a. Reporting Entity shall provide the following Quantity information in the Remarks section of the Cost and Hour Report: number of systems supported by this contract, and number of repairs performed. The Reporting Entity must state the nominal capacity planned for each Delivery Order (e.g., the # of repairs, # of overhauls, # of flight hours, etc.) identified in the plan. This requirement is intended to capture what services are being bought with each effort. |
b. For Element 1.6 Installation and Personnel Support, the quantity listed should reflect the number of sites/bases/installations.
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 |
| QT | Quanlification Testing Units | O&S |
| Annual1 | Annual Report 1 | O&S |
| Annual2 | Annual Report 2 | O&S |
| Annual3 | Annual Report 3 | O&S |
| Annual4 | Annual Report 4 | O&S |
| Annual5 | Annual Report 5 | O&S |
| Annual6 | Annual Report 6 | O&S |
| Annual7 | Annual Report 7 | O&S |
| Annual8 | Annual Report 8 | O&S |
| Annual9 | Annual Report 9 | O&S |
| Annual10 | Annual Report 10 | O&S |
| 17. END ITEMS | ||
| a. ID | b. NAME | |
| CNR | Combat Net Radio |
| 18. OPTIONAL REQUIREMENTS | ||||
| a. ORDER/LOT ID | b. END ITEM ID | c. UNIT REPORTING | ||
| (X if applicable) | d. SEQUENCING |
(X if applicable)
DRAFT DD FORM 2794 (PAGE 5), INTRA-CONTRACT SCOPE, JANUARY 2019
DD Form 2794, Pg 6 (SRDR DEV)
| COST AND SOFTWARE DATA REPORTING PLAN - SRDR DEVELOPMENT | ||
| 19. RELEASES | ||
| a. ID | b. NAME | c. DATE |
| 20. CSCI'S | |
| a. ID | b. NAME |
| 21. PRODUCT SIZE REPORTING ELEMENTS | |||
| a. CODE | b. NAME | c. RELEASE ID | d. CSCI ID |
| 22. PRODUCT SIZE SUBMISSIONS | c. RELEASE ID: | ||||
| a. NUMBER | b. NAME | Included? | Included? | Included? |
DRAFT DD FORM 2794 (PAGE 6), SRDR DEVELOPMENT, JANUARY 2019
DD Form 2794, Pg 7 (SRDR MX)
| COST AND SOFTWARE DATA REPORTING PLAN - SRDR MAINTENANCE | ||
| 23. RELEASES | ||
| a. ID | b. NAME | c. DATE |
| 24. PRODUCT SIZE REPORTING ELEMENTS | ||
| a. CODE | b. NAME | c. RELEASE ID |
| 25. PRODUCT SIZE SUBMISSIONS | c. RELEASE ID: | ||||
| a. NUMBER | b. NAME | Included? | Included? | Included? |
DRAFT DD FORM 2794 (PAGE 7), SRDR MAINTENANCE, JANUARY 2019
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 |
DRAFT DD FORM 2794 (PAGE 8), TECHNICAL PARAMETER REQUIREMENTS, JANUARY 2019
File details come from the government source that posted it. Updated .