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

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

File Type Posted
Solicitation Amendment - HT003826RE0010003.pdf PDF
Solicitation Amendment HT003826RE0010003 SF 30.pdf PDF
RFP DeploymentSolutions Amendments QA 20260416.pdf PDF
Solicitation Amendment - HT003826RE0010002.pdf PDF
Exhibit A005 Transition-Out Plan CDRL_2026.04.13.pdf PDF
Performance Work Statement (PWS) Deployment Solutions_2026.04.13.pdf PDF
Solicitation Amendment HT003826RE0010002 SF 30.pdf PDF
RFP_DeploymentSolutions_QA_2026.04.13.pdf PDF
RFP_DeploymentSolutions_QA_2024.04.10.pdf PDF
RFP_DeploymentSolutions_QA_2024.04.08.pdf PDF
Solicitation Amendment HT003826RE0010001 SF 30.pdf PDF
Solicitation Amendment - HT003826RE0010001.pdf PDF
PEO DHMS Deployment Ordering Guide.pdf PDF
RFP_DeploymentSolutions_QA_2026.04.06.pdf PDF
Exhibit A001 Quality Control Plan CDRL.pdf PDF
Exhibit A002 Training Curriculum CDRL .pdf PDF
Exhibit A003 Deployment Approach CDRL.pdf PDF
Exhibit A004 Transition-In Plan CDRL.pdf PDF
Exhibit A007 CWBS CDRL.pdf PDF
Exhibit A010 Implementation Plan CDRL.pdf PDF
Organizational Conflict of Interest (OCI) Declaration and Disclosure.docx DOCX document
Solicitation - HT003826RE001.pdf PDF
Quality Assurance Surveillance Plan (QASP).docx DOCX document
Exhibit A005 Transition-Out Plan CDRL.pdf PDF
PWS - Deployment Solutions.docx DOCX document
Exhibit A008 Cost and Hour Report (FlexFile) CDRL.pdf PDF
NDA DHA Form 49.pdf PDF
Exhibit A006 CSP CDRL.pdf PDF
Exhibit A009 Technical Data Report CDRL.pdf PDF
Exhibit A011 Integrated Master Schedule CDRL.pdf PDF
PEO DHMS Operational View.pdf PDF
DHA Common Federal Training List.pdf PDF
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 PLANOMB 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
XC-LRIP
XC-FRP
XO&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
XOther
2. COMMODITY TYPE
Information System/Defense Business System
3. PLAN ITERATION TYPE
XINITIAL
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
XCONTRACT (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)
XRDT&E
XPROCUREMENT
XO&M
FMS
WCF
OTHER
10a. APPROVED PLAN NUMBER

10b. APPROVED PLAN REVISION NUMBER

10c. APPROVED PLAN REQUIREMENTS
XAT COMPLETION COSTS FOR STANDARD FUNCTIONAL CATEGORIES (FlexFile or Legacy)
XAT COMPLETION COSTS FOR RECURRING/NONRECURRING (FlexFile only)
XTECHNICAL DATA REQUIRED
10d. COST REPORT TYPE
XFLEXFILE
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 PLANCOST, SOFTWARE, & TECHNICAL DATA REPORTING/EARNED VALUE MANAGEMENT CO-PLAN
11. WORK BREAKDOWN STRUCTURE (WBS)12. COST13. TECHNICAL DATA
a. WBS
CODEb. WBS
LEVELc. WBS ELEMENT NAMEa. ACTUALS TO
DATE (ATD)b. LEGACY
1921-1c. LEGACY
1921-2d. LEGACY
1921-5e. EAC/FAC
(See item 10d)a. QUANTITYb. SRDR
FORMATSc.

MAINT. &

REPAIR

PARTS

i. QUANTITY
DATAii. GFE

QUANTITY

1.02Information Systems (IS)/Defense Business Systems (DBS) (Investment)X
1.12IS/DBS Development/Customization/ConfigurationX
1.1.13Custom Application 1....n (Specify)X
1.1.1.14Subsystem Hardware (Specifiy)XX
1.1.1.24Subsystem Software CSCI 1...n (Specify)XX
1.1.1.34Subsystem Software Level Integration, Assembly, Test, and CheckoutXX
1.1.23Enterprise Service Element 1...n (Specify)X
1.1.2.14Enterprise Service Element Hardware (Specify)XX
1.1.2.24Enterprise Service Element Software CSCI 1...n (Specify)XX
1.1.2.34Enterprise Service Element Integration, Assembly, Test, and CheckoutXX
1.1.33Enterprise/Management Information System 1...n (Specify)X
1.1.3.14Business Area Hardware (Specify)XX
1.1.3.24Business Area Software CSCI 1...n (Specify)XX
1.1.3.34Business Area Integration, Assembly, Test, and CheckoutXX
1.1.43External System Interface Development 1...n (Specify)X
1.1.4.14External System Interface Hardware (Specify)XX
1.1.4.24External System Interface Software CSCI 1...n (Specify)XX
1.1.4.34External System Interface Integration, Assembly, Test, and CheckoutXX
1.1.53System Level Infrastructure (Specify)X
1.1.5.14System Level Hardware (Specify)XX
1.1.5.24Service Infrastructure 1...n (Specify)XX
1.22System Level IntegrationXX
1.32Systems EngineeringX
1.3.13Software Systems EngineeringXX
1.3.23Integrated Logistics Support (ILS) Systems EngineeringXX
1.3.33Cybersecurity Systems EngineeringXX
1.3.43Core Systems EngineeringXX
1.3.53Other Systems Engineering 1...n (Specify)XX
1.42Program ManagementX
1.4.13Software Program ManagementXX
1.4.23Integrated Logistics Support (ILS) Program ManagementXX
1.4.33Cybersecurity Program ManagementXX
1.4.43Core Program ManagementXX
1.4.53Other Program Management 1...n (Specify)XX
1.52Change ManagementXX
1.62Data ManagementXX
1.72System Test and EvaluationX
1.7.13Developmental Test and EvaluationX
1.7.1.14Cybersecurity Test and EvaluationXX
1.7.1.24Other DT&E Tests 1…n (Specify)XX
1.7.23Operational Test and EvaluationX
1.7.2.14Cybersecurity Test and EvaluationXX
1.7.2.24Other OT&E Tests 1…n (Specify)XX
1.7.33Mock-ups/System Integration Labs (SILs)XX
1.7.43Test and Evaluation Management/SupportXX
1.7.53Test FacilitiesXX
1.82TrainingX
1.8.13EquipmentXX
1.8.23ServicesXX
1.8.33FacilitiesXX
1.8.43Training Software 1...n (Specify)XX
1.92DataX
1.9.13Data Deliverables 1...n (Specify)XX
1.9.23Data RepositoryXX
1.9.33Data Rights 1...n (Specify)XX
1.102Peculiar Support EquipmentX
1.10.13Test and Measurement EquipmentXX
1.10.23Support and Handling EquipmentXX
1.112Common Support EquipmentX
1.11.13Test and Measurement EquipmentXX
1.11.23Support and Handling EquipmentXX
1.122Operational Infrastructure/Site Activation by Site 1...n (Specify)X
1.12.13Initial Hardware ProcurementX
1.12.1.14End User EquipmentXX
1.12.1.24Cybersecurity EquipmentXX
1.12.1.34IT Infrastructure and Enterprise Software EquipmentXX
1.12.1.44Other 1...n (Specify)XX
1.12.23Initial Software License ProcurementX
1.12.2.14End User Software LicenseXX
1.12.2.24Cybersecurity Software Licenses/ServicesXX
1.12.2.34IT Infrastructure and EquipmentXX
1.12.2.44Other 1...n (Specify)XX
1.12.33Initial Software Release (Pre-IOC) Modification/EnhancementX
1.12.3.14Routine Fixes/Deficiency CorrectionXX
1.12.3.24Deployment Independent Verification and ValidationXX
1.12.3.34Installation/TestXX
1.12.43Site ActivationX
1.12.4.14Data MigrationXX
1.12.4.24User TrainingXX
1.12.4.34User DocumentationXX
1.12.4.44Management/Engineering SupportXX
1.12.4.54Site Installation, Test, and CheckoutXX
1.12.53Interim Operations and Support (Pre-IOC)X
1.12.5.14Help DeskXX
1.12.5.24System Database AdministratorXX
1.12.5.34Installation, Test, and CheckoutXX
1.12.5.44IT Equipment MaintenanceXX
1.132Industrial FacilitiesX
1.13.13Construction/Conversion/ExpansionXX
1.13.23Equipment Acquisition or ModernizationXX
1.13.33Maintenance (Industrial Facilities)XX
1.142Initial Spares and Repair PartsXX
2.01Information Systems (IS)/Defense Business Systems (DBS) (Sustainment)X
2.12Program ManagementXX
2.22Systems/Sustainment EngineeringXX
2.32Change ManagementXX
2.42Help DeskXX
2.52Data Cleansing/Data MaintenanceXX
2.62System/Database AdministrationXX
2.72IT Infrastructure/Network Maintenance SupportX
2.7.13IT Infrastructure Hardware/Equipment MaintenanceXX
2.7.23IT Infrastructure Software License Support ServicesXX
2.7.33IT Infrastructure ManagementXX
2.7.43Other IT Infrastructure Support 1...n (Specify)XX
2.82Operational Hardware Refresh/UpgradeX
2.8.13End-User EquipmentX
2.8.23Cybersecurity EquipmentXX
2.8.33IT Infrastructure and Enterprise Services EquipmentXX
2.8.43Other (Specify)XX
2.92Operational Software License Refresh/UpdateX
2.9.13End-User Software LicenseXX
2.9.23Cybersecurity Software Licenses/ServicesXX
2.9.33IT Infrastructure and Enterprise Software Licenses/ServicesXX
2.9.43Other (Specify)XX
2.102Cybersecurity Maintenance ManagementX
2.10.13Cybersecurity Compliance Operations and TrackingXX
2.10.23Follow-on Cybersecurity Test and EvaluationXX
2.10.33Cybersecurity and IT Certification and AccreditationXX
2.112Follow-on User TrainingXX
2.122System Independent Verification and ValidationXX
2.132Continuing System ImprovementsX
2.13.13Operational Hardware ModificationX
2.13.1.14Mod Kit Hardware DevelopmentXX
2.13.1.24Mod Kit Hardware ProcurementXX
2.13.1.34Mod Kit Hardware InstallationXX
2.13.23Software Release Modification/Enhancement 1...n (Specify)X
2.13.2.14Modifications/EnhancementsXX
2.13.2.24Routine Fixes and Deficiency CorrectionXX
2.13.2.34Installation/TestXX
2.13.2.44IAVAsXX
2.142AW/Safety/Networthiness CertificationXX
2.152FacilitiesXX

Subtotal Cost X X

Reporting Contractor G&AXX
Reporting Contractor Undistributed BudgetXX
Reporting Contractor Management ReserveXX
Reporting Contractor FCCMXX
Total CostXX

Reporting Contractor Profit/Loss or Fee X X

Total PriceXX
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 IDb.
DATA REPORT(S)c.
SUBMISSION EVENT NAMEd.
REPORT CYCLEe. AS OF DATEf. DUE DATE
(YYYYMMDD)(YYYYMMDD)
1Cost and Hour Report (FlexFile)Contract Award (plus 60 days)InitialTBDTBD
2Technical Data ReportContract Award (plus 60 days)InitialTBDTBD
3Cost and Hour Report (FlexFile)Annual Report - Year 1 (contract award +12 months)InterimTBD+1yrTBD+1yr
4Technical Data ReportAnnual Report - Year 1 (contract award +12 months)InterimTBD+1yrTBD+1yr
5Cost and Hour Report (FlexFile)Annual Report - Year 2 (contract award +24 months)InterimTBD+2yrTBD+2yr
6Technical Data ReportAnnual Report - Year 2 (contract award +24 months)InterimTBD+2yrTBD+2yr
7Cost and Hour Report (FlexFile)Annual Report - Year 3 (contract award +36 months)InterimTBD+3yrTBD+3yr
8Technical Data ReportAnnual Report - Year 3 (contract award +36 months)InterimTBD+3yrTBD+3yr
9Cost and Hour Report (FlexFile)Annual Report - Year 4 (contract award +48 months)InterimTBD+4yrTBD+4yr
10Technical Data ReportAnnual Report - Year 4 (contract award +48 months)InterimTBD+4yrTBD+4yr
11Cost and Hour Report (FlexFile)Annual Report - Year 5 (contract award +60 months) / Contract CompletionFinalTBD+5yrTBD+5yr
12Technical Data ReportAnnual Report - Year 5 (contract award +60 months) / Contract CompletionFinalTBD+5yrTBD+5yr
DD FORM 2794 (PAGE 3), SUBMISSION EVENTS, MAY 2024PREVIOUS 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. IDb. NAMEc. PHASE/MILESTONE
1Order TBDTBD
2Order TBDTBD
3Order TBDTBD
4Order TBDTBD
5Order TBDTBD
17. END ITEMS
a. IDb. NAME
MHS GENESISMHS GENESIS
MHSG-TMHS GENESIS Theater
OpMed CDPOpMed CDP
TBDTBD
18. UNIT/SUBLOT REPORTING AND UNIT SEQUENCING REQUIREMENTS
a. ORDER/LOT IDb. END ITEM IDc. UNIT/SUBLOT REPORTING
(X if applicable)d. UNIT SEQUENCING

(X if applicable)

1MHS GENESIS
1MHSG-T
1OpMed CDP
1TBD
2MHS GENESIS
2MHSG-T
2OpMed CDP
2TBD
3MHS GENESIS
3MHSG-T
3OpMed CDP
3TBD
4MHS GENESIS
4MHSG-T
4OpMed CDP
4TBD
5MHS GENESIS
5MHSG-T
5OpMed CDP
5TBD
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 CODE30. WBS ELEMENT NAME31. ITEM TYPE32. TECHNICAL PARAMETER
a. PARAMETER NAMEb. UNIT OF MEASUREc. UNIT OF MEASURE QUALIFIERd. REPEATABLEe. DEFINITIONf. REMARKS
2.7IT Infrastructure/Network Maintenance SupportProduction Downtime During DeploymentHoursThe total duration of production environment unavailability due to deployment activities
2.7IT Infrastructure/Network Maintenance SupportMean Time to Restore (MTTR)HoursThe average time taken to fully restore system functionality after a service-disrupting incident
2.13.2Software Release Modification/Enhancement 1...n (Specify)Deployments and Release Frequency (MVPs, MVCRs)IntegerThe number of software deployments and the frequency of releases, including minimum viable products and minimum viable change requests
2.13.2.3Installation/TestEnvironment MTTRHours(Time) Mean time to recover for Test Environments
2.13.2.3Installation/TestCapacityPercentage(Percentage) The amount of tester time planned, as a percentage of planned to maximum.
2.13.2.3Installation/TestDefect Rate Over TimePercentage(Percentage) The rate of defects discovered per test case executions.
2.13.2.3Installation/TestTest Case Library AutomationPercentage(Percentage) Percent of all unarchived test cases that are automated.
2.13.2.3Installation/TestInstall TimeHours(Time) Time to install code devlieries.
2.13.2.3Installation/TestTraceabilityPercentage(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.3Installation/TestPayback PeriodYears(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.3Installation/TestData Operational EfficiencyPercentage(Percentage) The amount of data used in PEO reports, divided by the total data in the Data Warehouse
2.13.2.3Installation/TestData SizeInteger(Integer) The total data points stored in the Data Warehouse
2.1Program ManagementDevelopment MethodologyDescribe your development methodology (waterfall, agile, etc.)
2.1Program ManagementDevSecOps (Y/N)Y/NYes (Y) if the system meets the definition of DevSecOps. No (N) if the system does not. (see Appendix X for definitions)
2.7.3IT Infrastructure ManagementCloud-Ready (Y/N)Y/NYes (Y) if the system meets the definition of Cloud-Ready. No (N) if the system does not. (see Appendix X for definitions)
2.7.3IT Infrastructure ManagementCloud-Hosted (Y/N)Y/NYes (Y) if the system meets the definition of Cloud-Hosted. No (N) if the system does not. (see Appendix X for definitions)
2.10.1Cybersecurity Compliance Operations and TrackingZero-Trust (ZT) Implementation (Y/N)Y/NYes (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.1Cybersecurity Compliance Operations and TrackingICAM Implementation (Y/N)Y/NYes (Y) if an ICAM architecture is being implemented. No (N) if it is not. (see Appendix X for definitions)
2.7.3IT Infrastructure ManagementLeveraging DECE (Y/N)Y/NYes (Y) if the system is leveraging DECE. No (N) if the system does not. (see Appendix X for definitions)
2.13.2.3Installation/TestNumber of New Test CasesIntegerThe total number of newly created test cases for accessing software functionality and performance
2.13.2.3Installation/TestNumber of New Test Cases AutomatedIntegerThe total count of new test cases converted to use automated testing tools
2.13.2.3Installation/TestTotal TestsIntegerThe combined number of manual and automated tests executed during the software testing process
2.13.2.3Installation/TestTotal percentage of Tests AutomatedIntegerThe ratio of automated tests out of the total number of tests expressed as a percentage
2.13.2Software Release Modification/Enhancement 1...n (Specify)Product Delivery Lead Time to ProductionDaysThe total time taken to deliver a new feature or product update, from development initiation to production deployment
2.13.2Software Release Modification/Enhancement 1...n (Specify)Number of User Stories Completed (formally # of User Stories Accepted)IntegerThe total count of user stories successfully completed and accepted by stakeholders
2.13.2Software Release Modification/Enhancement 1...n (Specify)Velocity (does not include predictability at this time)IntegerThe average number of user stories completed within a specific development timeframe, such as a sprint
2.13.2Software Release Modification/Enhancement 1...n (Specify)Story Completion RatePercentageThe percentage of user stories successfully completed within a timeframe compared to the total planned stories
2.13.2Software Release Modification/Enhancement 1...n (Specify)Cycle Time / ThroughputDaysThe average time taken to complete a user story, from development start to deployment
2.13.2.3Installation/TestAutomated Test CoveragePercentage(Percentage) Percent of Stories covered by Automated Test Cases.
2.13.2.3Installation/TestDefects Found By AutomationInteger(Integer) Defects found by Automated Test Cases
2.13.2.3Installation/TestDefect Rate Comparison Between Test Case TypePercentage(Decimal) For similar test cycles (i.e. regression testing), the difference in defect rate for Manual and Automated Testing
2.13.2.3Installation/TestAverage Time to CloseDays(Integer, Days) Number of days to close a defect. Does not include withdrawn defects.
2.13.2Software Release Modification/Enhancement 1...n (Specify)BurndownInteger(Integer) Amount of work (Stories, Story Points, Test Cases, Test Steps, Estimated Test Time) remaining in a release, version, or sprint.
2.13.2.3Installation/TestDefect Aging by SeverityDays(Integer, Days) The number of days a defect is in an open state.
2.13.2.3Installation/TestTest Cycle Lead TimeDays(Integer, Days) Time between delivery of requirement code and a Test Case Execution.
2.13.2.3Installation/TestVelocityInteger(Integer) Number of stories successfully tested per sprint or test plan.
2.13.2.3Installation/TestAutomated Test Case Time to RepairHours(Time) Average time to complete test script maintenance on an automated test case.
2.13.2.3Installation/TestConversion TimeHours(Time) Time invested in converting a manual Test Case into an Automation Test Case
2.13.2.3Installation/TestNumber of Defects/BugsIntegerThe total count of identified software flaws detected during deployment and testing
2.13.2.3Installation/TestDefect Resolution TimeHoursThe average time taken to fix and verify a reported software defect
2.13.2Software Release Modification/Enhancement 1...n (Specify)Number of RefactorsIntegerThe total count of code modifications made solely to improve maintainability, readability, and efficiency
2.13.2Software Release Modification/Enhancement 1...n (Specify)Change / Fail Percentage RatePercentageThe percentage of code changes resulting in production failures or requiring rollbacks
2.13.2.3Installation/TestTest CoveragePercentage(Percentage) Percent of Stories/Requirements covered by Test Cases.
2.13.2.3Installation/TestFailure RatePercentage(Percentage) What percentage of Test Case Executions result in a verdict of failure?
2.13.2.3Installation/TestNew DefectsInteger(Integer) The number of defects reported from testing today.
2.13.2.3Installation/TestTest Plan StatusPass/Fail/BlockedFinal verdict (Pass, Fail, Blocked) by test case, for a test plan.
2.13.2Software Release Modification/Enhancement 1...n (Specify)Recycle Rate (Delivery)Percentage(Percentage) What percent of delivered requirements are delivered more than once?
2.13.2.3Installation/TestRecycle Rate (Testing)Percentage(Percentage) What percent of delivered and installed requirements are tested more than once?
2.13.2.3Installation/TestRecidivismInteger(Integer) Number of times that a specific Defect has happened.
2.13.2Software Release Modification/Enhancement 1...n (Specify)Cyclomatic ComplexityInteger(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.1Program ManagementNumber of Total UsersIntegerThe total count of unique users who access and utilize the software
2.11Follow-on User TrainingNumber of Users TrainedIntegerNumber of end users trained by role/function
2.11Follow-on User TrainingNumber of Trainers TrainedIntegerNumber of trainers trained (train-the-trainers program)
2.11Follow-on User TrainingNumber of Sites Training CompletedIntegerNumber of sites that training has been completed with
2.13.2.3Installation/TestNumber of Platforms Product InstalledIntegerNumber of platforms product has been installed on
2.13.2.3Installation/TestNumber of Sites Deployment CompletedIntegerNumber of sites that deployment has been completed by role type, site/facility type, product deployed
2.1Program ManagementNumber of FISC (Federal Information System Controls) Audit NFRs (Notification of Finding and Recommendation)IntegerMetric should track NFRs recorded in DITPR. Answer N/A if not selected for FISC Audit; Metric required if selected for audit.
2.1Program ManagementPercent of Business/System Control Risk & Issue Reduction (NIST 800-53)PercentageThe 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 TYPEb. PARAMETER NAMEc. LIST ITEMS
Software LicensesActive UsersYes
Deployment HardwareBill of MaterialsYes

DD FORM 2794 (PAGE 9b), TECHNICAL PARAMETER REQUIREMENTS, MAY 2024

File details come from the government source that posted it. Updated .