DHMS Deployment DD2794 CSDR Plan.xlsx
XLSX spreadsheet 76 KB Posted
- Attached to
- Program Executive Office (PEO) Defense Healthcare Management Systems (DHMS) Deployment Solutions
- Solicitation number
- HT003826RE001
- Issued by
-
Defense Health Agency
About this file
This is a Cost and Software Data Reporting (CSDR) Plan submitted on DD Form 2794 for the Defense Health Management System (DHMS) program under the Program Executive Office (PEO) DHMS. The plan establishes data reporting requirements for a multiple award Indefinite Delivery Indefinite Quantity (IDIQ) contract for Deployment Solutions, with initial submission due 60 days after contract award. The government point of contact is Christopher R. Metz at the Defense Health Agency (christopher.r.metz2.civ@health.mil, 571-225-4266). The plan covers three prime mission products: MHS GENESIS, MHS GENESIS Theater (MHSG-T), and Operational Medicine (OpMed) Care Delivery Platform (CDP), classified as an Information System/Defense Business System. Reporting requirements span five years with initial and annual cost and hour reports due at contract award plus 60 days, then annually through year five, along with corresponding technical data reports. The plan requires FlexFile cost reporting at completion, covering standard functional categories and recurring/nonrecurring costs, with a Forecast at Completion (FAC) requirement at the Work Breakdown Structure (WBS) level.
The technical parameter requirements are comprehensive and focus on deployment, testing, and operational metrics including production downtime during deployment, Mean Time to Restore (MTTR), software deployment frequency, test environment recovery time, test automation rates, defect tracking, installation time, and user training metrics. Additional metrics cover development methodology, DevSecOps implementation, cloud readiness and hosting status, Zero-Trust and ICAM cybersecurity implementations, and user story completion rates. The reporting entity must conduct a CSDR Readiness Review with the government's Cost Working Group Integrated Product Team (CWIPT) within 60 days of contract award, submit a Resource Distribution Table identifying subcontractors requiring direct CSDR reporting to the Cost Assessment Data Enterprise (CADE), and maintain cumulative cost data throughout contract performance. WBS elements not within contract scope must be marked as zero cost with explanatory remarks, and all technical data submitted to CADE must be unclassified or Controlled Unclassified Information (CUI).
View the file
Other files
Show all 32
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-0671 |
| The public reporting burden for this collection of information is estimated to average 57 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 | |
| PEO DHMS - PEO Defense Health Management System (DHMS) | |
| 1b. PHASE/MILESTONE (check all that apply) | |
| Pre-A | |
| A | |
| B | |
| X | C-LRIP |
| X | C-FRP |
| X | O&S |
| 1c. PRIME MISSION PRODUCT | |
| Various: 1. MHS GENESIS; 2. MHS GENESIS Theater; 3. Operational Medicine (OpMed) Care Delivery Platform (CDP) | |
| 1d. ACQUISITION CATEGORY (ACAT) | |
| Pre-ACAT | |
| ACAT I (MDAP) | |
| ACAT IA (MAIS) | |
| ACAT II | |
| ACAT III | |
| X | Other |
| 2. COMMODITY TYPE | |
| Information System/Defense Business System | |
| 3. PLAN ITERATION TYPE | |
| X | INITIAL |
| REVISION | |
| 4. CURRENT SUBMISSION DATE (YYYYMMDD) | |
| 20260128 | |
| 5. LAST APPROVED PLAN DATE (YYYYMMDD) | |
| N/A | |
| 6a. GOVERNMENT PLAN POINT OF CONTACT (POC) NAME (Last, First, M.) | |
| Metz, Christopher, R. | |
| 6b. ADDRESS (Include ZIP Code) | |
| 1700 North Moore Street Suite 2300 Arlington, VA 22209 | |
| 6c. TELEPHONE NUMBER (Include Area Code) | |
| (571) 225-4266 | |
| 6d. E-MAIL ADDRESS | |
| Christopher.R.Metz2.civ@health.mil | |
| 7. PLAN TYPE | |
| GOVERNMENT | |
| X | CONTRACT (PRIME) |
| CONTRACT (SUB) | |
| 8. PLAN GOVERNMENT PREPARING ORGANIZATION | |
| PEO DHMS - PEO Defense Healthcare Management Systems (DHMS) | |
| 9a. CONTRACTOR NAME/ADDRESS | |
| i. REPORTING ORGANIZATION NAME | |
| TBD | |
| ii. DIVISION NAME | |
| TBD | |
| iii. LOCATION | |
| TBD | |
| iv. CONTRACTOR BUSINESS DATA REPORT (CBDR 1921-3) REQUIREMENT: | |
| CBDR REQUIRED FOR THIS ORGANIZATION | |
| 9b. CONTRACT NUMBER (List all that apply, separated by commas) | |
| TBD | |
| 9c. APPROPRIATION (check all that apply) | |
| X | RDT&E |
| X | PROCUREMENT |
| X | O&M |
| FMS | |
| WCF | |
| OTHER | |
| 10a. APPROVED PLAN NUMBER |
10b. APPROVED PLAN REVISION NUMBER
| 10c. APPROVED PLAN REQUIREMENTS | |
| X | AT COMPLETION COSTS FOR STANDARD FUNCTIONAL CATEGORIES (FlexFile or Legacy) |
| X | AT COMPLETION COSTS FOR RECURRING/NONRECURRING (FlexFile only) |
| X | TECHNICAL DATA REQUIRED |
| 10d. COST REPORT TYPE | |
| X | FLEXFILE |
| LEGACY DD 1921 SERIES |
DD FORM 2794 (PAGE 1), METADATA, MAY 2024 PREVIOUS EDITION IS OBSOLETE
mailto:Christopher.R.Metz2.civ@health.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 | 2 | Information Systems (IS)/Defense Business Systems (DBS) (Investment) | X | |
| 1.1 | 2 | IS/DBS Development/Customization/Configuration | X | |
| 1.1.1 | 3 | Custom Application 1....n (Specify) | X | |
| 1.1.1.1 | 4 | Subsystem Hardware (Specifiy) | X | X |
| 1.1.1.2 | 4 | Subsystem Software CSCI 1...n (Specify) | X | X |
| 1.1.1.3 | 4 | Subsystem Software Level Integration, Assembly, Test, and Checkout | X | X |
| 1.1.2 | 3 | Enterprise Service Element 1...n (Specify) | X | |
| 1.1.2.1 | 4 | Enterprise Service Element Hardware (Specify) | X | X |
| 1.1.2.2 | 4 | Enterprise Service Element Software CSCI 1...n (Specify) | X | X |
| 1.1.2.3 | 4 | Enterprise Service Element Integration, Assembly, Test, and Checkout | X | X |
| 1.1.3 | 3 | Enterprise/Management Information System 1...n (Specify) | X | |
| 1.1.3.1 | 4 | Business Area Hardware (Specify) | X | X |
| 1.1.3.2 | 4 | Business Area Software CSCI 1...n (Specify) | X | X |
| 1.1.3.3 | 4 | Business Area Integration, Assembly, Test, and Checkout | X | X |
| 1.1.4 | 3 | External System Interface Development 1...n (Specify) | X | |
| 1.1.4.1 | 4 | External System Interface Hardware (Specify) | X | X |
| 1.1.4.2 | 4 | External System Interface Software CSCI 1...n (Specify) | X | X |
| 1.1.4.3 | 4 | External System Interface Integration, Assembly, Test, and Checkout | X | X |
| 1.1.5 | 3 | System Level Infrastructure (Specify) | X | |
| 1.1.5.1 | 4 | System Level Hardware (Specify) | X | X |
| 1.1.5.2 | 4 | Service Infrastructure 1...n (Specify) | X | X |
| 1.2 | 2 | System Level Integration | X | X |
| 1.3 | 2 | Systems Engineering | X | |
| 1.3.1 | 3 | Software Systems Engineering | X | X |
| 1.3.2 | 3 | Integrated Logistics Support (ILS) Systems Engineering | X | X |
| 1.3.3 | 3 | Cybersecurity Systems Engineering | X | X |
| 1.3.4 | 3 | Core Systems Engineering | X | X |
| 1.3.5 | 3 | Other Systems Engineering 1...n (Specify) | X | X |
| 1.4 | 2 | Program Management | X | |
| 1.4.1 | 3 | Software Program Management | X | X |
| 1.4.2 | 3 | Integrated Logistics Support (ILS) Program Management | X | X |
| 1.4.3 | 3 | Cybersecurity Program Management | X | X |
| 1.4.4 | 3 | Core Program Management | X | X |
| 1.4.5 | 3 | Other Program Management 1...n (Specify) | X | X |
| 1.5 | 2 | Change Management | X | X |
| 1.6 | 2 | Data Management | X | X |
| 1.7 | 2 | System Test and Evaluation | X | |
| 1.7.1 | 3 | Developmental Test and Evaluation | X | |
| 1.7.1.1 | 4 | Cybersecurity Test and Evaluation | X | X |
| 1.7.1.2 | 4 | Other DT&E Tests 1…n (Specify) | X | X |
| 1.7.2 | 3 | Operational Test and Evaluation | X | |
| 1.7.2.1 | 4 | Cybersecurity Test and Evaluation | X | X |
| 1.7.2.2 | 4 | Other OT&E Tests 1…n (Specify) | X | X |
| 1.7.3 | 3 | Mock-ups/System Integration Labs (SILs) | X | X |
| 1.7.4 | 3 | Test and Evaluation Management/Support | X | X |
| 1.7.5 | 3 | Test Facilities | X | X |
| 1.8 | 2 | Training | X | |
| 1.8.1 | 3 | Equipment | X | X |
| 1.8.2 | 3 | Services | X | X |
| 1.8.3 | 3 | Facilities | X | X |
| 1.8.4 | 3 | Training Software 1...n (Specify) | X | X |
| 1.9 | 2 | Data | X | |
| 1.9.1 | 3 | Data Deliverables 1...n (Specify) | X | X |
| 1.9.2 | 3 | Data Repository | X | X |
| 1.9.3 | 3 | Data Rights 1...n (Specify) | X | X |
| 1.10 | 2 | Peculiar Support Equipment | X | |
| 1.10.1 | 3 | Test and Measurement Equipment | X | X |
| 1.10.2 | 3 | Support and Handling Equipment | X | X |
| 1.11 | 2 | Common Support Equipment | X | |
| 1.11.1 | 3 | Test and Measurement Equipment | X | X |
| 1.11.2 | 3 | Support and Handling Equipment | X | X |
| 1.12 | 2 | Operational Infrastructure/Site Activation by Site 1...n (Specify) | X | |
| 1.12.1 | 3 | Initial Hardware Procurement | X | |
| 1.12.1.1 | 4 | End User Equipment | X | X |
| 1.12.1.2 | 4 | Cybersecurity Equipment | X | X |
| 1.12.1.3 | 4 | IT Infrastructure and Enterprise Software Equipment | X | X |
| 1.12.1.4 | 4 | Other 1...n (Specify) | X | X |
| 1.12.2 | 3 | Initial Software License Procurement | X | |
| 1.12.2.1 | 4 | End User Software License | X | X |
| 1.12.2.2 | 4 | Cybersecurity Software Licenses/Services | X | X |
| 1.12.2.3 | 4 | IT Infrastructure and Equipment | X | X |
| 1.12.2.4 | 4 | Other 1...n (Specify) | X | X |
| 1.12.3 | 3 | Initial Software Release (Pre-IOC) Modification/Enhancement | X | |
| 1.12.3.1 | 4 | Routine Fixes/Deficiency Correction | X | X |
| 1.12.3.2 | 4 | Deployment Independent Verification and Validation | X | X |
| 1.12.3.3 | 4 | Installation/Test | X | X |
| 1.12.4 | 3 | Site Activation | X | |
| 1.12.4.1 | 4 | Data Migration | X | X |
| 1.12.4.2 | 4 | User Training | X | X |
| 1.12.4.3 | 4 | User Documentation | X | X |
| 1.12.4.4 | 4 | Management/Engineering Support | X | X |
| 1.12.4.5 | 4 | Site Installation, Test, and Checkout | X | X |
| 1.12.5 | 3 | Interim Operations and Support (Pre-IOC) | X | |
| 1.12.5.1 | 4 | Help Desk | X | X |
| 1.12.5.2 | 4 | System Database Administrator | X | X |
| 1.12.5.3 | 4 | Installation, Test, and Checkout | X | X |
| 1.12.5.4 | 4 | IT Equipment Maintenance | X | X |
| 1.13 | 2 | Industrial Facilities | X | |
| 1.13.1 | 3 | Construction/Conversion/Expansion | X | X |
| 1.13.2 | 3 | Equipment Acquisition or Modernization | X | X |
| 1.13.3 | 3 | Maintenance (Industrial Facilities) | X | X |
| 1.14 | 2 | Initial Spares and Repair Parts | X | X |
| 2.0 | 1 | Information Systems (IS)/Defense Business Systems (DBS) (Sustainment) | X | |
| 2.1 | 2 | Program Management | X | X |
| 2.2 | 2 | Systems/Sustainment Engineering | X | X |
| 2.3 | 2 | Change Management | X | X |
| 2.4 | 2 | Help Desk | X | X |
| 2.5 | 2 | Data Cleansing/Data Maintenance | X | X |
| 2.6 | 2 | System/Database Administration | X | X |
| 2.7 | 2 | IT Infrastructure/Network Maintenance Support | X | |
| 2.7.1 | 3 | IT Infrastructure Hardware/Equipment Maintenance | X | X |
| 2.7.2 | 3 | IT Infrastructure Software License Support Services | X | X |
| 2.7.3 | 3 | IT Infrastructure Management | X | X |
| 2.7.4 | 3 | Other IT Infrastructure Support 1...n (Specify) | X | X |
| 2.8 | 2 | Operational Hardware Refresh/Upgrade | X | |
| 2.8.1 | 3 | End-User Equipment | X | |
| 2.8.2 | 3 | Cybersecurity Equipment | X | X |
| 2.8.3 | 3 | IT Infrastructure and Enterprise Services Equipment | X | X |
| 2.8.4 | 3 | Other (Specify) | X | X |
| 2.9 | 2 | Operational Software License Refresh/Update | X | |
| 2.9.1 | 3 | End-User Software License | X | X |
| 2.9.2 | 3 | Cybersecurity Software Licenses/Services | X | X |
| 2.9.3 | 3 | IT Infrastructure and Enterprise Software Licenses/Services | X | X |
| 2.9.4 | 3 | Other (Specify) | X | X |
| 2.10 | 2 | Cybersecurity Maintenance Management | X | |
| 2.10.1 | 3 | Cybersecurity Compliance Operations and Tracking | X | X |
| 2.10.2 | 3 | Follow-on Cybersecurity Test and Evaluation | X | X |
| 2.10.3 | 3 | Cybersecurity and IT Certification and Accreditation | X | X |
| 2.11 | 2 | Follow-on User Training | X | X |
| 2.12 | 2 | System Independent Verification and Validation | X | X |
| 2.13 | 2 | Continuing System Improvements | X | |
| 2.13.1 | 3 | Operational Hardware Modification | X | |
| 2.13.1.1 | 4 | Mod Kit Hardware Development | X | X |
| 2.13.1.2 | 4 | Mod Kit Hardware Procurement | X | X |
| 2.13.1.3 | 4 | Mod Kit Hardware Installation | X | X |
| 2.13.2 | 3 | Software Release Modification/Enhancement 1...n (Specify) | X | |
| 2.13.2.1 | 4 | Modifications/Enhancements | X | X |
| 2.13.2.2 | 4 | Routine Fixes and Deficiency Correction | X | X |
| 2.13.2.3 | 4 | Installation/Test | X | X |
| 2.13.2.4 | 4 | IAVAs | X | X |
| 2.14 | 2 | AW/Safety/Networthiness Certification | X | X |
| 2.15 | 2 | Facilities | 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 | |
| DD FORM 2794 (PAGE 2), REPORTING, MAY 2024 |
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) | Contract Award (plus 60 days) | Initial | TBD | TBD | ||
| 2 | Technical Data Report | Contract Award (plus 60 days) | Initial | TBD | TBD | ||
| 3 | Cost and Hour Report (FlexFile) | Annual Report - Year 1 (contract award +12 months) | Interim | TBD+1yr | TBD+1yr | ||
| 4 | Technical Data Report | Annual Report - Year 1 (contract award +12 months) | Interim | TBD+1yr | TBD+1yr | ||
| 5 | Cost and Hour Report (FlexFile) | Annual Report - Year 2 (contract award +24 months) | Interim | TBD+2yr | TBD+2yr | ||
| 6 | Technical Data Report | Annual Report - Year 2 (contract award +24 months) | Interim | TBD+2yr | TBD+2yr | ||
| 7 | Cost and Hour Report (FlexFile) | Annual Report - Year 3 (contract award +36 months) | Interim | TBD+3yr | TBD+3yr | ||
| 8 | Technical Data Report | Annual Report - Year 3 (contract award +36 months) | Interim | TBD+3yr | TBD+3yr | ||
| 9 | Cost and Hour Report (FlexFile) | Annual Report - Year 4 (contract award +48 months) | Interim | TBD+4yr | TBD+4yr | ||
| 10 | Technical Data Report | Annual Report - Year 4 (contract award +48 months) | Interim | TBD+4yr | TBD+4yr | ||
| 11 | Cost and Hour Report (FlexFile) | Annual Report - Year 5 (contract award +60 months) / Contract Completion | Final | TBD+5yr | TBD+5yr | ||
| 12 | Technical Data Report | Annual Report - Year 5 (contract award +60 months) / Contract Completion | Final | TBD+5yr | TBD+5yr | ||
| DD FORM 2794 (PAGE 3), SUBMISSION EVENTS, MAY 2024 | PREVIOUS EDITION IS OBSOLETE |
DD Form 2794, Pg 4 (REMARKS)
| COST AND SOFTWARE DATA REPORTING PLAN |
| 15. REMARKS |
In addition to the direction provided in the associated CSDR Data Item Descriptions (DIDs) and the CSDR Manual (DoDM 5000.04), the following instructions, requirements, and considerations found on this page/worksheet shall be utilized when collecting data and preparing CSDR submissions. This CSDR Contract plan is intended to capture costs associated with the contract number(s) listed in block 9.b, irrespective of contract type (e.g., firm-fixed price, cost-plus fixed fee) or CLIN structure, 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.
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. COST & HOUR REPORT (FLEXFILE)
1. 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.
2. 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.
3. WBS Definitions & Remarks (Data Group C) 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 WBS Definitions & Remarks shall contain a disclosure statement detailing any differences between the CSDR reporting methodology and the reporting entity's Cost Accounting Standards. WBS Definitions & Remarks 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.
4. The reporting entity must maintain and update WBS Definitions & Remarks 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 Definitions.
5. 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 WBS Definitions & Remarks 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.
6. Order/Lot: 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.
7. End Items: Block 17 of this CSDR Plan is meant to capture the discrete hardware end items that are DD-250'ed, ordered, procured, or exercised (as applicable) on the contract. If an End Item is DD-250'ed, ordered, procured, or exercised (as applicable) on the contract but is not listed in block 17, the contractor shall submit the dollars and hours in the Cost and Hour Report (FlexFile) and the quantity information in the Quantity Report tagged using the name of the End Item utilized on the contract. The CSDR Plan will be updated to include the appropriate End Item name in block 17, after report submission, if required.
i. End Item ID 1: The "Common" end item tag shall be used to report costs and hours which are not incurred or directly attributable to an individual end item. For example, overarching program management costs and hours that are required, independent of the type or quantity of end items on contract would be tagged against the “Common” end item. Common hardware (i.e., identical/homogeneous part numbers) procured and integrated into multiple end items shall utilize the end item tag for the prime product they were integrated onto and shall not be tagged with the “Common” end item.
8. The contractor shall utilize and include the following mappings from its accounting system to the Actual Cost-Hour Data tags:
i. {To be determined during the CSDR Readiness Review based on contractor's accounting system} = Tag1
ii. {To be determined during the CSDR Readiness Review based on contractor's accounting system} = Tag2
iii. {To be determined during the CSDR Readiness Review based on contractor's accounting system} = Tag3
d. SOFTWARE RESOURCE DATA REPORTING (SRDR) FORMATS
1. Software Resource Data Reporting is not required under this plan, as the contract is for software training and deployment services, NOT software development or maintenance.
e. 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.
2. Required technical data for the TDR will be a required outcome of the individual task order kick-off, and must be agreed to by the PEO DHMS CWIPT
f. 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).
g. 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.
l. CONTRACT-SPECIFIC REMARKS
1. Report Not Applicable Items as 0
2. TDR should reflect same metrics as reported in the PEO DHMS Cost Schedule Performance (CSP) Report
DD FORM 2794 (PAGE 4), REMARKS, MAY 2024 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 | Order TBD | TBD | |||
| 2 | Order TBD | TBD | |||
| 3 | Order TBD | TBD | |||
| 4 | Order TBD | TBD | |||
| 5 | Order TBD | TBD | |||
| 17. END ITEMS | |||||
| a. ID | b. NAME | ||||
| MHS GENESIS | MHS GENESIS | ||||
| MHSG-T | MHS GENESIS Theater | ||||
| OpMed CDP | OpMed CDP | ||||
| TBD | TBD | ||||
| 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)
| 1 | MHS GENESIS |
| 1 | MHSG-T |
| 1 | OpMed CDP |
| 1 | TBD |
| 2 | MHS GENESIS |
| 2 | MHSG-T |
| 2 | OpMed CDP |
| 2 | TBD |
| 3 | MHS GENESIS |
| 3 | MHSG-T |
| 3 | OpMed CDP |
| 3 | TBD |
| 4 | MHS GENESIS |
| 4 | MHSG-T |
| 4 | OpMed CDP |
| 4 | TBD |
| 5 | MHS GENESIS |
| 5 | MHSG-T |
| 5 | OpMed CDP |
| 5 | TBD |
| DD FORM 2794 (PAGE 5), INTRA-CONTRACT SCOPE, MAY 2024 |
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 | ||||
| 2.7 | IT Infrastructure/Network Maintenance Support | Production Downtime During Deployment | Hours | The total duration of production environment unavailability due to deployment activities | |||||
| 2.7 | IT Infrastructure/Network Maintenance Support | Mean Time to Restore (MTTR) | Hours | The average time taken to fully restore system functionality after a service-disrupting incident | |||||
| 2.13.2 | Software Release Modification/Enhancement 1...n (Specify) | Deployments and Release Frequency (MVPs, MVCRs) | Integer | The number of software deployments and the frequency of releases, including minimum viable products and minimum viable change requests | |||||
| 2.13.2.3 | Installation/Test | Environment MTTR | Hours | (Time) Mean time to recover for Test Environments | |||||
| 2.13.2.3 | Installation/Test | Capacity | Percentage | (Percentage) The amount of tester time planned, as a percentage of planned to maximum. | |||||
| 2.13.2.3 | Installation/Test | Defect Rate Over Time | Percentage | (Percentage) The rate of defects discovered per test case executions. | |||||
| 2.13.2.3 | Installation/Test | Test Case Library Automation | Percentage | (Percentage) Percent of all unarchived test cases that are automated. | |||||
| 2.13.2.3 | Installation/Test | Install Time | Hours | (Time) Time to install code devlieries. | |||||
| 2.13.2.3 | Installation/Test | Traceability | Percentage | (Percentage) The percentage of issues properly linked. Requirements must be linked to Test Cases. Failed Test Case Executions must be linked to a Defect. | |||||
| 2.13.2.3 | Installation/Test | Payback Period | Years | (Time, years) Test Case conversion time divided by time saved by the conversion to automation (time saved defined as average historical execution time, minus intervention time after automation); the amount of time that will pass before an automated test cases "repays" the investment in automation. | |||||
| 2.13.2.3 | Installation/Test | Data Operational Efficiency | Percentage | (Percentage) The amount of data used in PEO reports, divided by the total data in the Data Warehouse | |||||
| 2.13.2.3 | Installation/Test | Data Size | Integer | (Integer) The total data points stored in the Data Warehouse | |||||
| 2.1 | Program Management | Development Methodology | Describe your development methodology (waterfall, agile, etc.) | ||||||
| 2.1 | Program Management | DevSecOps (Y/N) | Y/N | Yes (Y) if the system meets the definition of DevSecOps. No (N) if the system does not. (see Appendix X for definitions) | |||||
| 2.7.3 | IT Infrastructure Management | Cloud-Ready (Y/N) | Y/N | Yes (Y) if the system meets the definition of Cloud-Ready. No (N) if the system does not. (see Appendix X for definitions) | |||||
| 2.7.3 | IT Infrastructure Management | Cloud-Hosted (Y/N) | Y/N | Yes (Y) if the system meets the definition of Cloud-Hosted. No (N) if the system does not. (see Appendix X for definitions) | |||||
| 2.10.1 | Cybersecurity Compliance Operations and Tracking | Zero-Trust (ZT) Implementation (Y/N) | Y/N | Yes (Y) if ZT is ready to be implemented and enforced within the environment. No (N) if it is not. (see Appendix X for definitions) | |||||
| 2.10.1 | Cybersecurity Compliance Operations and Tracking | ICAM Implementation (Y/N) | Y/N | Yes (Y) if an ICAM architecture is being implemented. No (N) if it is not. (see Appendix X for definitions) | |||||
| 2.7.3 | IT Infrastructure Management | Leveraging DECE (Y/N) | Y/N | Yes (Y) if the system is leveraging DECE. No (N) if the system does not. (see Appendix X for definitions) | |||||
| 2.13.2.3 | Installation/Test | Number of New Test Cases | Integer | The total number of newly created test cases for accessing software functionality and performance | |||||
| 2.13.2.3 | Installation/Test | Number of New Test Cases Automated | Integer | The total count of new test cases converted to use automated testing tools | |||||
| 2.13.2.3 | Installation/Test | Total Tests | Integer | The combined number of manual and automated tests executed during the software testing process | |||||
| 2.13.2.3 | Installation/Test | Total percentage of Tests Automated | Integer | The ratio of automated tests out of the total number of tests expressed as a percentage | |||||
| 2.13.2 | Software Release Modification/Enhancement 1...n (Specify) | Product Delivery Lead Time to Production | Days | The total time taken to deliver a new feature or product update, from development initiation to production deployment | |||||
| 2.13.2 | Software Release Modification/Enhancement 1...n (Specify) | Number of User Stories Completed (formally # of User Stories Accepted) | Integer | The total count of user stories successfully completed and accepted by stakeholders | |||||
| 2.13.2 | Software Release Modification/Enhancement 1...n (Specify) | Velocity (does not include predictability at this time) | Integer | The average number of user stories completed within a specific development timeframe, such as a sprint | |||||
| 2.13.2 | Software Release Modification/Enhancement 1...n (Specify) | Story Completion Rate | Percentage | The percentage of user stories successfully completed within a timeframe compared to the total planned stories | |||||
| 2.13.2 | Software Release Modification/Enhancement 1...n (Specify) | Cycle Time / Throughput | Days | The average time taken to complete a user story, from development start to deployment | |||||
| 2.13.2.3 | Installation/Test | Automated Test Coverage | Percentage | (Percentage) Percent of Stories covered by Automated Test Cases. | |||||
| 2.13.2.3 | Installation/Test | Defects Found By Automation | Integer | (Integer) Defects found by Automated Test Cases | |||||
| 2.13.2.3 | Installation/Test | Defect Rate Comparison Between Test Case Type | Percentage | (Decimal) For similar test cycles (i.e. regression testing), the difference in defect rate for Manual and Automated Testing | |||||
| 2.13.2.3 | Installation/Test | Average Time to Close | Days | (Integer, Days) Number of days to close a defect. Does not include withdrawn defects. | |||||
| 2.13.2 | Software Release Modification/Enhancement 1...n (Specify) | Burndown | Integer | (Integer) Amount of work (Stories, Story Points, Test Cases, Test Steps, Estimated Test Time) remaining in a release, version, or sprint. | |||||
| 2.13.2.3 | Installation/Test | Defect Aging by Severity | Days | (Integer, Days) The number of days a defect is in an open state. | |||||
| 2.13.2.3 | Installation/Test | Test Cycle Lead Time | Days | (Integer, Days) Time between delivery of requirement code and a Test Case Execution. | |||||
| 2.13.2.3 | Installation/Test | Velocity | Integer | (Integer) Number of stories successfully tested per sprint or test plan. | |||||
| 2.13.2.3 | Installation/Test | Automated Test Case Time to Repair | Hours | (Time) Average time to complete test script maintenance on an automated test case. | |||||
| 2.13.2.3 | Installation/Test | Conversion Time | Hours | (Time) Time invested in converting a manual Test Case into an Automation Test Case | |||||
| 2.13.2.3 | Installation/Test | Number of Defects/Bugs | Integer | The total count of identified software flaws detected during deployment and testing | |||||
| 2.13.2.3 | Installation/Test | Defect Resolution Time | Hours | The average time taken to fix and verify a reported software defect | |||||
| 2.13.2 | Software Release Modification/Enhancement 1...n (Specify) | Number of Refactors | Integer | The total count of code modifications made solely to improve maintainability, readability, and efficiency | |||||
| 2.13.2 | Software Release Modification/Enhancement 1...n (Specify) | Change / Fail Percentage Rate | Percentage | The percentage of code changes resulting in production failures or requiring rollbacks | |||||
| 2.13.2.3 | Installation/Test | Test Coverage | Percentage | (Percentage) Percent of Stories/Requirements covered by Test Cases. | |||||
| 2.13.2.3 | Installation/Test | Failure Rate | Percentage | (Percentage) What percentage of Test Case Executions result in a verdict of failure? | |||||
| 2.13.2.3 | Installation/Test | New Defects | Integer | (Integer) The number of defects reported from testing today. | |||||
| 2.13.2.3 | Installation/Test | Test Plan Status | Pass/Fail/Blocked | Final verdict (Pass, Fail, Blocked) by test case, for a test plan. | |||||
| 2.13.2 | Software Release Modification/Enhancement 1...n (Specify) | Recycle Rate (Delivery) | Percentage | (Percentage) What percent of delivered requirements are delivered more than once? | |||||
| 2.13.2.3 | Installation/Test | Recycle Rate (Testing) | Percentage | (Percentage) What percent of delivered and installed requirements are tested more than once? | |||||
| 2.13.2.3 | Installation/Test | Recidivism | Integer | (Integer) Number of times that a specific Defect has happened. | |||||
| 2.13.2 | Software Release Modification/Enhancement 1...n (Specify) | Cyclomatic Complexity | Integer | (Integer) Relative measure determining the stability and level of confidence in a Solution based on the count of nodes in the control-flow diagram. (Related to requirements/stories, informs the complexity of required test cases) | |||||
| 2.1 | Program Management | Number of Total Users | Integer | The total count of unique users who access and utilize the software | |||||
| 2.11 | Follow-on User Training | Number of Users Trained | Integer | Number of end users trained by role/function | |||||
| 2.11 | Follow-on User Training | Number of Trainers Trained | Integer | Number of trainers trained (train-the-trainers program) | |||||
| 2.11 | Follow-on User Training | Number of Sites Training Completed | Integer | Number of sites that training has been completed with | |||||
| 2.13.2.3 | Installation/Test | Number of Platforms Product Installed | Integer | Number of platforms product has been installed on | |||||
| 2.13.2.3 | Installation/Test | Number of Sites Deployment Completed | Integer | Number of sites that deployment has been completed by role type, site/facility type, product deployed | |||||
| 2.1 | Program Management | Number of FISC (Federal Information System Controls) Audit NFRs (Notification of Finding and Recommendation) | Integer | Metric should track NFRs recorded in DITPR. Answer N/A if not selected for FISC Audit; Metric required if selected for audit. | |||||
| 2.1 | Program Management | Percent of Business/System Control Risk & Issue Reduction (NIST 800-53) | Percentage | The percentage of NIST 800-53 security controls implemented and demonstrably compliant in eMass represents the proportion of controls actively used and proven to meet the required security standards | |||||
| DD FORM 2794 (PAGE 9a), TECHNICAL PARAMETER REQUIREMENTS, MAY 2024 |
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 |
| Software Licenses | Active Users | Yes |
| Deployment Hardware | Bill of Materials | Yes |
DD FORM 2794 (PAGE 9b), TECHNICAL PARAMETER REQUIREMENTS, MAY 2024
File details come from the government source that posted it. Updated .