RFI Atch 6 - Industry Day Deck.pptx
PPTX presentation 10 MB Posted
- Attached to
- ESS Next – Industry Day Announcement and RFI
- Solicitation number
- DHA_01152025
- Issued by
-
Defense Health Agency
About this file
This file is an Industry Day presentation deck attachment related to the Defense Health Agency's Enterprise Software Solutions (ESS) Next initiative. The presentation shares information about DHA's vision to transition existing services to a hybrid "everything as a service" model that will provide users with digital and physical capabilities to support development, testing, and delivery of applications for the Military Health System Enterprise.
The ESS Next program will offer self-provisioning of standardized services including software services (managed development and testing tools), infrastructure services (compute, network, storage), physical space and support services at the Medical Enterprise Test Innovation Center (METIC), virtual desktop services, and containerization services. The initiative aims to enable users to quickly access required tools for mission-critical product development while allowing organizational flexibility for scaling, innovation, and cost optimization. The Industry Day event is designed to facilitate collaboration between industry partners and government stakeholders, allowing companies to learn about requirements, engage in discussions, and explore capability alignment.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| ESS Next RFI_02.pdf | ||
| RFI Atch 7- ESS Next Industry Day and RFI QA.xlsx | XLSX spreadsheet | |
| ESS Next RFI_01.pdf | ||
| RFI Atch 5 - PRS Table_DRAFT.pdf | ||
| RFI Atch 4 - QASP_DRAFT.pdf | ||
| RFI Atch 3 - ESS Next Use Cases.pptx | PPTX presentation | |
| ESS Next RFI.pdf | ||
| RFI Atch 1 - ESS Next PWS_DRAFT.pdf | ||
| RFI Atch 2 - Capabilities Table.xlsx | XLSX spreadsheet | |
| Industry Day Invitation.pdf | ||
| Industry Day Invitation.pdf |
Show all 11
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
29 January 2025 ESS Next Industry Day Session 1
Objectives for today Welcome, Agenda, and Objectives DHMS Overview and Government’s Vision for ESS Next Timeline Overview Key Questions
Copyright © 2025 by Boston Consulting Group. All rights reserved.
Notes view: 1
Presenters Today Ground Rules Mr. Matt A. Gargett Chief Technology Officer (CTO) Program Executive Office, Defense Health Management Systems (PEO DHMS) Ms. Rachael Bealer Contract Specialist Defense Healthcare Management Systems Contracting Division (DHMS-CD) Defense Health Agency Vendors may ask clarifying questions based on the materials shown in today’s presentation
Maintain professional decorum throughout the presentation and engage in constructive dialogue
Attendee lists will be provided at the conclusion of industry day
Presentation Agenda
| Presenter | Topic |
| Ms. Rachael Bealer | Welcome and Ground Rules |
| Ms. Rachael Bealer | PEO DHMS Mission and Overview |
| Mr. Matthew Gargett | ESS Next Overview and Core Offerings |
| N/A | BREAK |
| Mr. Matthew Gargett | Enhancing Current ESS Capabilities |
| Mr. Matthew Gargett | ESS Next Future Offerings |
| Ms. Rachael Bealer | ESS Next Contract Timeline Overview |
| Ms. Rachael Bealer | Takeaways, Key Questions |
| USG Team | Concluding Remarks/Questions |
| BREAK | Lunch |
| USG Team/Vendors | 1-1 Sessions |
Notes view: 3
DHMS Overview and Government’s Vision for ESS Next
Become a world-class technology organization Continuously deliver capability Accelerate Healthcare IT improvements Enhance patient experience through seamless transition of care Program Executive Office (PEO) Defense Health Management Systems (DHMS) Mission (I/II) Mission statement:
The mission of PEO Defense Healthcare Management System is to transform the delivery of health care and advance data sharing through a modernized electronic health record for service members, veterans and their families
PEO DHMS aims to "drive patient-centered healthcare” through modern solutions" through four ambitious goals:
Copyright © 2022 by Boston Consulting Group. All rights reserved.
Notes view: 5
Program Executive Office (PEO) Defense Health Management Systems (DHMS) Mission (II/II) To enable software testing… The current Enterprise Shared Services (ESS) contract provides for many necessary functions, including physical space, environment assets, and supporting software
PEO DHMS is seeking to conduct a competitive follow-on contract to current ESS services, with a new contract award expected for October 2025.
This software needs to undergo rigorous Developmental Testing & Evaluation (DT&E) and well as Operational Testing (OT) as mandated by Federal Acquisition Regulation (FAR)/Defense Federal Acquisition Regulation (DFAR)/Adaptive Acquisition Framework (AAF) (esp. DODI 5000.89 and corresponding documents for each of the pathways) The Program Executive Office, Defense Healthcare Management Systems is an acquisition organization that oversees three program management offices (PMOs):
DOD Healthcare Management System Modernization (DHMSM) Joint Operational Medicine Information Systems (JOMIS) Enterprise Intelligence and Data Solutions (EIDS) Through the acquisition process, PEO DHMS also manages the configuration, customization, and development of software that's deployed around the world to support our service personnel and their families through these PMOs
Current ESS1 contract provides managed service support across six key areas:
Services are provided through an on-prem private cloud (i.e., information stored in a DHMS physical data center) Current ESS Contract 1Enterprise Software Services | 2as a service | 3Currently provided through IaaS | 4Everything as a service ESS Next provides all current ESS capabilities, plus additional enhanced/net-new capabilities, such as:
Future state intends to migrate select services to the cloud and enable hybrid cloud model (i.e., both on-prem and GovCloud) and build standard services offerings. These service offerings will be consumed by DHMS PMOs and other stakeholders via XaaS4 Future State Vision for ESS Next ESS Next plans to enhance current ESS capabilities Data Center aaS (METIC and DDC) Infrastructure aaS (Resource Pools, VMs) Platform aaS (DevSecOps platform with CI/CD Pipelines) Software aaS (Tools, such as JIRA, AHLTA) Desktop aaS3 (Virtual Desktops) Containers aaS (CI/CD release mgmt.)
PEO managed governance to standardize services across PMOs* Automated self-provisioning of services Enhanced Desktop aaS capability Provisioning of Standardized Containers aaS Streamlined (standard) ecosystem of tools/processes
Current ESS contract, awarded in 2023, provides managed service support for the development, testing, and deployment of PEO software applications through an on-prem private cloud (i.e., information is stored in a DHMS physical data center)
In the following slides I will cover, the examples provided are meant to be illustrative of capabilities that we believe would be beneficial to the PEO. We are eager to hear from industry what innovative approaches or inputs you may have to achieve these objectives
The Future state (ESS Next) intends to migrate select services to the cloud, utilizing hybrid cloud (i.e., both on-prem and GovCloud) ESS Next plans to employ an “as-a-service” model via centralized managed governance to standardize services, wherein products, tools, and services are provisioned on-demand to users This approach will drive value across 5 key areas:
Optimizing costs Increase Scalability Increase Productivity and Process Optimization (via automation) Enhance Cybersecurity Improve Speed of Service Delivery
Notes view: 7
ESS Next Core Offerings | Summary (I/III)
CUI
CUI
Distribution Statement D: Distribution authorized to the Department of Defense and U.S. DoD contractors only. Other requests for this document must be referred to PEO DHMS
| Requirement Offering | Description | Associated Products | Service Provider |
| Infrastructure as a Service (IaaS) | On-demand cloud infrastructure service that allows DHMS PMOs to access cloud-hosted virtual servers, networking, and storage resources to run applications and workloads | Compute, network, storage, memory, Infrastructure as a Code | GovCloud |
| Software as a Service (SaaS) | Managed software delivery that enables DHMS PMOs to access ready-to-use Approved tools/technologies hosted on cloud infrastructure | Tools that can be standardized (ATL/APL) and provided as a managed service for on-demand consumption | GovCloud and vendor provided Cloud SaaS products |
| Desktop as a Service (DaaS) | Fully-managed desktop service to allow users to access virtual desktops over the network | Virtual Desktop Infrastructure | On-prem Data Center (eventually cloud based desktops) |
At a high level, the ESS Next core offerings we are looking to enable include:
Infrastructure as a Service (IaaS) Developers & testers in PMOs can leverage IaaS to set up virtual hosts for sandbox, testing, and development environments much more quickly via self-service standardized service catalog product offerings through automation This should also include storage and networking capabilities
Software as a Service (SaaS) Develop and deliver managed software products via PEO enabled governance process for on-demand consumption by the PMOs (including license management as well)
Desktop as a service (DaaS) Provision fully managed virtual desktops to cater to various PMOs needs related to testing and configuration of test environments (access workstreams in multiple sites); Jira and Confluence Manage standardized virtual desktop images to meet DoD/DHA security compliance requirements
Notes view: 8
ESS Next Core Offerings | Summary (II/III)
CUI
CUI
Distribution Statement D: Distribution authorized to the Department of Defense and U.S. DoD contractors only. Other requests for this document must be referred to PEO DHMS
| Requirement Offering | Description | Associated Products | Service Provider | |
| Platform as a Service (PaaS) | On-demand service that allows DHMS PMOs and other stakeholders to access complete and ready-to-use platforms for developing, deploying, and managing applications | Databases, standardized templated pipelines, standardized suite of tools to manage DevSecOps processes (Version Control, Issue Tracking, etc.) | GovCloud | |
| Containers as a Service (CaaS) | Package of software that includes all dependencies: code, runtime, configuration, and system libraries so that it can run on any host system | Container orchestration system, serverless compute engine (Kubernetes/Fargate) | GovCloud | |
| Data Center as Service (DCaaS) | Hosts the DHMS Data Center (DDC) in Ashburn, VA. Includes testing Infrastructure (TI) and various | |||
| network connections. | Access to multiple, redundant internet service | |||
| Providers. Power Redundancy N+1; Cooling Redundancy N+2 | On-Prem Data Center |
Platform as a Service (PaaS) Develop and manage centralized DevSecOps platform with standardized tools and technologies PMOs need standardized pipeline automation for receipt acceptance of dev vendor delivery For example, JOMIS can leverage integration of product needs so that defined configurations are understood, consistent, and stable
Containers as a service (CaaS) Provision a standardized container orchestration system to allow users across PMOs to manage and deploy containerized applications For example, JOMIS currently uses OpenShift as needed to deploy Kubernetes clusters for container services
Data Center as a service (DCaaS) DHMS currently leases secure private cage at the Equinix Data Center in Ashburn, Virginia The data center space is used to host physical assets, hosts the Testing Infrastructure (TI) and various network connections (including racks)
Notes view: 9
Fully managed and secured facility to accommodate development, test, and integration activities that require physical equipment Hosts evaluations, product demonstrations, operational assessments, and other activities Over 16,000 sq feet of space with modern office accommodations, conference rooms, collaboration spaces, and secure storage Over 7,000 square feet of open, re-configurable lab space The METIC at a glance… ESS Next Core Offerings | Summary (III/III)
| Requirement Offering | Description | Associated Products | Service Provider |
| Medical Enterprise Test Innovation Center (METIC) | Shared testing facility located in Chantilly, Virginia. Physical extension of the Test Infrastructure, share common backbone and resources | Fixed Facility (FF) – Hospitals, Operational Medicine (OM) – theater, Physical medical devices, laptops, printers, conference rooms, meeting facilities, network peripherals | Government Approved Lab (GAL) |
The METIC is equipped to support test events involving medical devices for fixed facilities (e.g., hospitals) and operational medicine software for theater operations.
It offers a reconfigurable test area, conference rooms, and collaboration spaces, with connectivity to external data sources hosted by the DoD, VA, and commercial entities.
Located in Chantilly, VA (operates from 0700 - 1900 M-F ET Monday through Friday except Federal holidays) For example, at the METIC:
DT&E needs hosting services in a physical data center to include various assets currently hosted in the METIC and DDC with the flexibility to expand to support additional needs. This includes infrastructure, medical devices, and facilities provisioned for consumption Notes view: 10
// BREAK //
Why are we enhancing current ESS capabilities? (I/II) Feedback received on current ESS highlights a need for ESS Next enhancements
| Enhanced Requirements | Rationale | Capability Addressed |
| Provide a centralized platform to enable standardized DevSecOps framework, standardized processes, associated standardized tooling in both .com and .mil environments | Integrated products will provide controls so that defined configurations are understood, consistent, and stable | |
| PaaS | ||
| Enable end-to-end automation to drive faster provisioning, deployments, and reduced manual processes for requesting services | Achieve higher levels of automation for Infrastructure as Code (IaC), development of standard CI/CD templates, and containers to improve response times for TI requests and enable self-provisioning model for consumers | IaaS, Paas, CaaS |
| Allow users to remotely connect VDI to DHA network within the Lab via Desktop as a Service and potentially migrate DaaS to cloud for dynamic, flexible, and scalable desktop offerings | Streamline the ability for users to transition between interfaces to connect their VDI to DHA network within the Lab with no (low) network latency issues | DaaS |
We have conducted in-depth requirements gathering from existing ESS users across programs to develop a more robust ESS Next platform (and capabilities) to address identified gaps and enhance current offerings and align with the PEO 3.0 vision This effort, conducted throughout 2024, including careful mapping of current requirements and capabilities with existing programs while incorporating detailed feedback from various stakeholders to inform the future state of ESS Next
PEO DHMS wants to modernize and progressively transform the environments (starting with non-prod environments), workloads and infrastructure capabilities and extend the services into higher-value cloud native services and be able to implement additional operational models more efficiently (via automated and standardized services). This allows PEO DHMS to free up valuable resources, unlock new capabilities, accelerate innovation, and reduce technical debt The enhanced requirements reflected on this slide (and the following slide) represent qualitative rationale supporting the enhancement of current ESS services to meet PMO needs and align with PEO DHMS 3.0 vision
Why are we enhancing current ESS capabilities? (II/II) Feedback received on current ESS highlights a need for ESS Next enhancements
| Enhanced Requirements | Rationale | Capability Addressed |
| Provision containers as a service to allow users to manage and deploy standardized containerized application deployments. We currently don't have standard tools/processes for container orchestration in the .mil environment. The deployment of containers is yet to be defined | Container engines and orchestration frameworks such as Kubernetes, provide a standardized way to package applications — including the code, runtime and libraries — and to run them in a consistent manner across the entire software development life cycle and in multiple environments to allow for seamless integration of cross-PMO systems for deployment cycles | CaaS |
| Develop and standardize streamlined ecosystem of tools/processes to enable seamless cross-PMO system integration testing | Currently, each PMO uses different tools, making it difficult to perform system integration testing | SaaS |
Throughout the process of gathering feedback from programs, we've baselined current capabilities, map to where gaps exist, and have developed enhancements to be deployed in ESS Next aimed at addressing multiple program needs and concerns and align with PEO DHMS 3.0 vision These excerpts are a small subset of enhancements we've identified as critical to supporting ESS Next
Further, ESS Next will create a future-proof architecture In the short-term1, ESS Next will support pre-production environments only; this creates lower risk by creating ESS Next architecture in pre-production environments first, without encroaching on live applications
However, the architecture being developed will be scalable and flexible. This will allow for the addition of new enclaves for each DHMS PMO to potentially consume production workloads in the future if needed by the organization
In the meantime, we plan to capture metrics, maturing processes (service delivery), and standardizing services to ensure expansion to prod. is ready
1Timelines still being determined; current prime contracts support production environments today
The focus of ESS Next is to enable a hybrid cloud operating model to support pre-production workloads first via centralized governance and enable standardized service offerings In the future, this operating model could potentially consume production workloads
Notes view: 14
Ultimately, what will ESS Next provide?
ESS Next will provide managed service support key areas Infrastructure as a Service (Servers, Storage, Network) Platform as a Service (DevSecOps, CI/CD Pipelines) Data Center as a Service
(DDC)
Containers as a Service (Serverless Computing, Kubernetes Platform) Desktop as a Service (Virtual Desktops1, License Tracking) Software as a Service (Fully Managed Software Tools) 1Potentially in cloud in future state for scalable, flexible, and cost-effective desktop services | 2Enabling Requirements Program Management2 (Utilization reports, # of METIC visit requests) General Services2 (Incident tracking service requisitioning) Cyber Security and Policy Adherence2 (Apply to all other Services) The METIC (Secure, shared, Government Approved Lab (GAL) )
Available via Self-provisioning Catalog
Indicates core offering
ESS Next should provide standardized managed services to support the key areas identified on this slide As I mentioned earlier, these are examples meant to encourage you (as industry experts) to share your expertise, perspectives and make appropriate recommendations to the government
Notes view: 15
DHMS Overview and Government’s Vision for ESS Next
ESS Next Contract Timeline: Estimated Milestones Timeline subject to change. Any changes to this timeline will be posted to SAM.gov
ESS Next Timeline
RFI published (Jan 2025)
Industry Day (Jan 2025)
Acquisition Strategy (Mar 2025)
RFI Responses Due (Feb 2025)
Contract Award for ESS Next (Oct 2025)
Solicitation Release (May 2025)
Proposals Due (Jun 2025)
Notes view: 17
DHMS Overview and Government’s Vision for ESS Next
Takeaways: Key Questions for Industry & Day 2 Agenda With the information provided in today’s presentation, there are important questions the government is seeking industry’s perspective on as this process moves ahead:
Based on the requirement so far – what are we missing? What information would you need in order to place a bid?
In your opinion, are there any roadblocks that could be lifted that would encourage a more robust competition for this contract?
Where do you see the greatest risk to the government?
The following questions are intended to encourage industry to think critically about how they propose to compete for this work based on the governments objectives Industry Day 2
Tomorrow’s Industry Day activities will consist of 1-on-1 sessions with individual vendors. These sessions will start at 0930.
Tomorrow’s meetings will be 15-20 minutes in length and will be conducted confidentially with the USG team and Vendor attendees who have participated in today’s session.
During this time, Vendors may ask the USG questions related to ESS Next
These sessions will be conducted both in person and virtually. Your scheduled time slot is based on the order in which RSVPs were received
Notes view: 19
Thank you
Notes view: 20 oleObject2.bin image2.emf image3.png image4.png image5.png oleObject213.bin oleObject20.bin oleObject214.bin image22.emf oleObject215.bin oleObject216.bin oleObject217.bin oleObject218.bin oleObject144.bin image14.emf image15.png oleObject219.bin image13.emf image23.png oleObject12.bin oleObject220.bin oleObject56.bin oleObject221.bin oleObject222.bin oleObject223.bin oleObject224.bin image24.emf image25.png oleObject17.bin oleObject225.bin oleObject40.bin oleObject226.bin oleObject227.bin oleObject18.bin oleObject228.bin oleObject229.bin image26.emf oleObject230.bin oleObject231.bin image27.emf oleObject232.bin oleObject41.bin oleObject233.bin oleObject38.bin oleObject234.bin image28.emf oleObject1.bin image1.emf oleObject77.bin image12.png
File details come from the government source that posted it. Updated .