RFI Atch 3 - ESS Next Use Cases.pptx

January 2025 ESS Next Use Case Collection

Containers as a Service (CaaS)

Notes view: 1

Use Case| CaaS Capabilities in Scope: Provide Containers as a Service (CaaS) support to all DHMS programs as well as other military health organizations Personas in Scope: Enterprise Intelligence Data Solutions (EIDS), Joint Operational Medicine Information Systems (JOMIS) Use case: Development of Containers as a Service (CaaS) is an identified need for programs. Today, current capabilities do not maintain a standardized approach for development and management of containers by leveraging standardized container orchestration (e.g., EKS). The current capability does not enable standardized, scalable containers. Current offerings for users provide partial containers for various vendor software (COTS products) releases.

Outcome: Develop, manage and support “serverless computing” by finalizing and enforcing the standards (considering the design and usage patterns from PMOs) and provide scalable containers to allow developers/testers across programs to rapidly deploy and test applications. The vendor should enable and manage standardized container orchestration solution to automate container deployment, load balancing, scaling, and lifecycle management.

Copyright © 2024 by Boston Consulting Group. All rights reserved.

Notes view: 2

Use Case| CaaS Capabilities in Scope: Provide Containers as a Service (CaaS) support to all DHMS programs as well as other military health organizations Personas in Scope: EIDS, JOMIS Use case: ESS currently does not have a standardized approach to develop and manage containers. ESS either provides partial containers for vendor releases or has to rebuild containers without any standardization. As such, we are unable to perform containerized-based testing.

Outcome: Support and manage requirement analysis for pre-production environments to host Kubernetes Platform for container services. Additionally, provide capability to deploy standardized containers (applications) consistently anywhere – on-premise (VMs), and in cloud environments. Build and manage muti-tenancy and portable containers and enable the ability to rapidly move them from one cloud environment to another on-premise or vice versa. The standardized, scalable containers should allow for faster (and consistent) deployments, increased scalability, and an enhanced user experience.

Notes view: 3

Cybersecurity

Notes view: 4

Use Case| Cybersecurity Capabilities in Scope: Provide Cybersecurity support services to all DHMS programs as well as other military health organizations as required Personas in Scope: All programs Use case: The security policies/procedures in place today stem from DoD, DHA, and PEO DHMS

Currently, ESS maintains two distinct enclaves: TI.COM, and TI.MIL. TI.COM is connected to the commercial Internet, has no accreditation, and is not rated to hold CUI, although it is held to the similar security standards as TI.MIL. TI.MIL is a fully-accredited pre-production enclave directly connected to the Med-COI and access to the NIPRNET. This enclave is accredited to hold CUI data and categorized as Moderate.

Outcome: Provide seamless cyber security services that include STIG automation, security assessments, IAVA maintenance, manage security scanning tools, report security incidents, and provide support for system accreditation and ATO tracking in both TI.COM and TI.MIL enclaves.

Notes view: 5

Use Case| Cybersecurity Capabilities in Scope: Provide Cybersecurity support services to all DHMS programs as well as other military health organizations as required Personas in Scope: Cyber Use case: ESS performs NIST RMF-based Cybersecurity activities in the TI environment. However, ESS does not provide centralized cyber compliance reports. Zone structure and current utilization makes it difficult to see and report as required in some instances. In essence, depending on what Zone they are in, there is not a central place where Cyber can view metrics.

Outcome: Perform NIST RMF-based Cybersecurity activities on the TI and provide centralized cyber compliance reports at certain frequency, in compliance with SOC 2 Type 1 and Type 2 requirements. Provide consolidated reports across all zones.

Notes view: 6

Desktop as a Service (DaaS)

Notes view: 7

Use Case| DaaS Capabilities in Scope: Provide Desktop as a Service (DaaS) support to all DHMS programs as well as other military health organizations as required Personas in Scope: DoD Healthcare Management System Modernization (DHMSM), EIDS, JOMIS, Development, Test, & Evaluation (DT&E) Use case: Currently, ESS users are forced to make 'multiple hops' between interfaces to connect their Virtual Desktop Infrastructure (VDI) to DHA network within the Lab. Multiple PMO users use VDI/VPN to access the TI environment for DT&E activities for testing JLV/LNLP and DES/CHDR. For JOMIS PMO, VDIs are in use now for various needs related to testing, configuration, and connecting to various test environments (access workstreams in multiple sites); accessing Jira and Confluence tools. Programs have expressed a need for a consistent and scalable VDI platform that can keep up with latest OS baselines and patching. Need something to unify all services as opposed to piecemeal method today.

Outcome: Provide capability to remotely connect VDI to DHA network within the Lab to remove the need for AVHE and reduce latency. Provide remote VDI for PMOs to test applications within the METIC (including FFGAL), connected to DoD network enclaves (e.g., MED-COI, NIPRNET, SIPRNET)

Notes view: 8

Capabilities in Scope: Provide Desktop as a Service (DaaS) support to all DHMS programs as well as other military health organizations as required Personas in Scope: DHMSM, EIDS, JOMIS, DT&E Use case: ESS currently supports DHA imaging, security updates, and patching on the infrastructure (VDIs) and laptops in METIC, DDC, and cloud environments. Programs have shared that in the current process, there is no visibility into patching, versions, imaging, application virtualization or other technologies.

Outcome: The vendor should support standardization and maintenance of various DHA standardized desktop applications for VDI needs. Develop and publish standardized schedule for patching, maintenance, and version control process. Provide support for standard and customized desktops with a comprehensive set of tools for developers, testers, and integrators. The vendor should also maintain and track desktop licensing for VDIs.

Additionally, the vendor should also perform Analysis of Alternatives (AoA) and make recommendation for transition to a cloud-based DaaS solution (i.e., Workspaces) that meets Cyber Security compliance requirements (i.e. FedRAMP) and provides cost & performance efficiencies

Notes view: 9

Capabilities in Scope: Provide Desktop as a Service (DaaS) support to all DHMS programs as well as other military health organizations as required Personas in Scope: All programs Use case: ESS currently provides network access to enable B2B partner testing. However, teams must go through multiple 'network hops' to obtain connectivity for B2B testing. PMOs have a constant need to collaborate with external partners as well as a need for B2B partner test environments. With programs today, VDIs are in use for various needs related to testing and configuration of test environments (access workstreams in multiple sites); Jira and Confluence.

Outcome: Provide and maintain network access to VDI, AVHE, NIPRNET, MedCOI, SIPRNET (once approved by DHA/DHMS), and external partner connections as PMOs would need B2B for partner test environments

Notes view: 10

Data Center as a Service (DCaaS)

Notes view: 11

Use case: ESS currently does not configure WAN. The current configuration is a point-to-point network setup.

ESS currently provides support for the DDC (Equinix data center facility). This includes management and maintenance of network cabling and rack services, as required and approved. ESS currently manages the physical

Outcome: Work in close collaboration with the Equinix Data Center team to support the DDC environment to include installation and maintenance of network cable management, personnel access, and rack services, as required and approved. Provide effective management of DHMS IT systems and facility infrastructure at DDC. The vendor should ensure reliable functioning of servers and storage devices. Design, Develop and configure WAN network (and extend connectivity to cloud data center). Enable and manage access to multiple, redundant internet service providers for seamless connectivity.

Use Case| DCaaS (DHMS Data Center – DDC) Capabilities in Scope: Provide Data Center as a Service (DCaaS) support to all DHMS programs as well as other military health organizations as required Personas in Scope: DHMSM, JOMIS, DT&E, Cyber

Notes view: 12

Medical Enterprise Test Innovation Center (METIC)

Notes view: 13

Use case: ESS currently manages the inventory of the medical devices and other hardware assets. However, they do not manage a hardware product catalog and make it available to the PMOs to request products required for their testing, ensure there are periodic diagnostic tests performed on these devices, and are serviceable when a request is made by the PMO.

Outcome: The vendor should manage a hardware product catalog (incl. chip/devices catalog) through a store front solution and make it available to the PMOs to request for products required for their testing needs. Additionally, the vendor should provide physical storage space (cages) for assets that are not in static configuration in the Lab, including spares or equipment as it waits for DRMO. Provide locker for storage of securable supplies (iPhones, CACs, iPads, etc.) in METIC.

Use Case| METIC Capabilities in Scope: Provide METIC resources support to all DHMS programs as well as other military health organizations as required Personas in Scope: DHMSM, JOMIS, DT&E, Cyber

Notes view: 14

Capabilities in Scope: Provide METIC resources support to all DHMS programs as well as other military health organizations as required Personas in Scope: DHMSM, JOMIS, DT&E Use case: ESS currently provides conference rooms, audio-visual support, and office space for usage by PEO and PMO staff for engineering, test, and demonstration activities. Programs need audio and visual capability, plenty of square footage, and network connectivity to DoD network during demo days

Outcome: Provide conference rooms, audio-visual support, and office space for usage by PEO & PMO staff for engineering, test, and demonstration activities. Enable self-service capability (via store front) for the PEO & PMO resources to reserve the conference rooms and office space based on their needs. Identify and implement areas of improvement to streamline the process and enhance user experience.

Notes view: 15

Use case: ESS currently provides furniture, and equipment to accommodate PMO & PEO equipment and staff usage to accomplish work in the METIC. ESS facilities management currently provides asset management. However, they do not thoroughly track all assets, as they have been unable to provide a comprehensive list of all assets upon request.

Outcome: Provide sufficient office space, furniture, photo copier services, and ancillary equipment to accommodate PMO & PEO equipment and staff usage to accomplish work in the METIC. Develop and maintain the property book, integrate with the SDLCNext ITSM tool to track and receive all hardware and software assets in the METIC and the DDC. Additionally, enable capability to generate ad hoc and scheduled reports for appropriate tracking/monitoring of assets.

Capabilities in Scope: Provide METIC resources support to all DHMS programs as well as other military health organizations as required Personas in Scope: DHMSM, JOMIS, DT&E

Notes view: 16

Use case: ESS currently provides Data Center capabilities. However, support is provided only on weekdays for specific times. Programs have occasional need to perform test events during off-hours and on weekends. Programs have specifically requested support during off-hours on an as needed basis.

Outcome: Provide METIC availability, including testing infrastructure facility space, equipment floor space, and office floor space, from 0700 - 1900 M-F EST with options to schedule overtime and for weekend and surge support as required. This includes what is currently hosted as well as the capability to be expanded for additional requirements. This includes infrastructure, physical medical devices, peripherals (printers, laptops, storage areas), and facilities provisioned for consumption as well as METIC.

This is under the assumption that the DDC will operate 24x7x365 with remote capability to METIC

Capabilities in Scope: Provide METIC resources support to all DHMS programs as well as other military health organizations as required Personas in Scope: DHMSM, JOMIS, DT&E

Notes view: 17

Infrastructure as a Service (IaaS)

Notes view: 18

Use Case| IaaS Capabilities in Scope: Provide Infrastructure as a Service (IaaS) support to all DHMS programs as well as other military health organizations as required Personas in Scope: DHMSM, EIDS, JOMIS, Cyber, DT&E Use case: ESS currently provides network access and connectivity to .com, .mil network enclaves, and MedCOI (NPS). ESS also provides support to provision servers (and resource pools) and manages the virtualized environments for product deployments and testing needs. ESS also provides support for the network (.com and .mil) connections to use the physical devices on the METIC floor connected to DDC infrastructure, and other locations (e.g. additional test sites such as in Cloud One). The PMO users typically place service requests (via JIRA) and follow-up communication occurs via manual emails with the ESS team to provision the required infrastructure for the various PMO testing needs.

Outcome: Provide .mil, .com, and Med-COI network access and connectivity to test enclaves and external connections. Design solutions to streamline the network performance. Design and implement end-to-end automation (via IaC) to enable self-service standardized infrastructure service catalog (store front) offerings for the PMOs to self-deploy their infrastructure components . Integrate the service catalog with the SDLCNext ITSM tool to track/monitor/approve the automated infrastructure provisioning by the end-users.

Notes view: 19

Use Case| IaaS Capabilities in Scope: Provide Infrastructure as a Service (IaaS) support to all DHMS programs as well as other military health organizations as required Personas in Scope: All programs Use case: ESS currently provides IaaS capabilities through a private cloud in DDC. However, ESS does not leverage public cloud or utilize IaC. The current servers are hosted and configured in DDC (racking/networking support). Dedicated compute, memory, and storage is allocated for PMO, project, and a group based on the needs. ESS provides shared services for Authentication, Name services, and Mail services. ESS also manages pre-established internal and external network connections (VA, DMDC, AHLTA, and others).

Outcome: Provide a hybrid cloud operating model for IaaS services by leveraging on-prem “private cloud” and “public cloud” services (i.e. AWS) and enable end-to-end automation (IaC) for self-provisioning of infrastructure services to realize cost savings (via pay as you use cost model). The provisioning and de-provisioning of infrastructure components should be enabled via self-service (store front) for the PMOs. Develop appropriate migration plans to allow for transition to a hybrid cloud model operational model. Enable IaC (incl. version control, standard OS imaging, etc.) and provide standardization of managed services in both private and public cloud environments (considering the usage patterns of the end-users). Enable the extension of the DHA/DHMS security controls to the hybrid cloud operating model.

Notes view: 20

Platform as a Service (PaaS)

Notes view: 21

Use Case| PaaS Capabilities in Scope: Provide Platform as a Service (PaaS) support to all DHMS programs as well as other military health organizations as required Personas in Scope: EIDS, Cyber, JOMIS, DT&E Use case: "ESS currently provides a PaaS solution (Enterprise Service Platform, ESP) that enables a DevSecOps framework. Through this framework, ESS provides some tools (duplication of tools in some cases (i.e., GitHub and GitLab), and templated CI/CD pipelines). The users can build and test their applications using a set of tools (incl. GitHub, Jira, Sonatype (Nexus repository), and Fortify. The PMO users can use the templated pipelines and customize to perform their work.

Outcome: Develop and provide a centralized PaaS platform to enable standardized DevSecOps framework, standardized end-to-end processes to build and deploy CI/CD pipelines, standardized tools, and automated templated CI/CD pipelines to simplify the development and testing of applications in a hybrid cloud operating model. The enhanced PaaS solution should integrate security into all phases of the software development lifecycle. The vendor should implement an industry standard set of tools and support the management suite at the core of the PaaS offering. The PaaS solution should be suitable for both containerized and non-containerized applications.

Notes view: 22

Use Case| PaaS Capabilities in Scope: Provide Platform as a Service (PaaS) support to all DHMS programs as well as other military health organizations as required Personas in Scope: DHMSM, EIDS, JOMIS, Cyber, DT&E Use case: ESS currently provides a PaaS with a suite of tools that provide an avenue to leverage managed services. However, there is no centralized governance process to allow for enablement of standard set of tools/technologies. The current PaaS offering is using the free version of Sonatype Nexus Repository. It does not allow for tagging or custom metadata to be added. If we had a better solution for this, it would help us further utilize the Nexus API to enhance our pipeline and automation.

Outcome: Develop a centralized “platform management suite” which includes the industry standard set of tools/technologies at the core of PaaS offering for capabilities like code version control (incl. IaC), build (i.e., Maven), issue tracking, dynamic and static code scanning, container scanning, interactive application security testing, and centralized log analysis (i.e., Splunk). Establish a centralized governance process to enable standardized customizable pipeline templates (considering the usage patterns of the PMOs), de-duplication of tools (i.e., GitHub and GitLab), integration of tools, and seamless automation for optimization.

Notes view: 23

Software as a Service (SaaS)

Notes view: 24

Use Case| SaaS Capabilities in Scope: Provide Software as a Service (SaaS) support to all DHMS programs as well as other military health organizations as required Personas in Scope: JOMIS Use case: ESS currently provisions SaaS solutions after they are procured by PEO DHMS. However, ESS does not conduct preliminary research (like integration compatibility with the current toolset) to vet the tools prior to being procured by PEO DHMS. No governance process exists to identify potential duplication of tools for a given capability as well. The PMOs don't have access to specific tool(s) for temporary use/discrete time frame (e.g., for a set time to support a specific part of the project).

Outcome: The vendor should support PEO DHMS (and PMOs) with research, identification, and procurement of SaaS candidates/tools. The tools will be procured by PEO DHMS. The vendor should work with the software vendors to enable access to software tools on a monthly subscription basis and allow PMOs to get what they need for just the time limit they need it for and without the overhead procurement, seat license increases, or other acquisition overhead processes.

Notes view: 25

Use Case| SaaS Capabilities in Scope: Provide Software as a Service (SaaS) support to all DHMS programs as well as other military health organizations as required Personas in Scope: All Use case: ESS currently provides SaaS with fully-managed tools to enable development, integration, and testing. However, there is currently no automated service catalog to allow the users to provision via self-service. The end users must request for software tools via a service ticket (JIRA) and communicate manually (emails) with ESS to deploy a software product for their needs. The current process doesn't have a well-defined end-to-end process to manage the software packaging via a SaaS model delivery to the end users.

Outcome: The vendor should develop a scalable, reliable, accessible, and secure SaaS delivery model for the end users. The vendor should collaborate with the PMOs to understand the target users. The delivery of the SaaS products should be via a self-service portal (i.e., store front) for end users to access and utilize SaaS offerings via automated standardized service catalog products (incl. plug-ins). The vendor should provide fully-managed tools by packaging the software (host/install/configure in DHMS network boundary), tracking/monitoring licensing, coordinating PEO DHMS security approvals, periodic maintenance, and managing the cost model for end user consumption. The SaaS offerings should be deployable in a hybrid cloud operating model.

Notes view: 26

Program Management

Notes view: 27

Use Case| Program Management Capabilities in Scope: Provide Program Management support services to all DHMS programs as well as other military health organizations as required Personas in Scope: All Use case: ESS currently provides the first 7 metrics listed below. Additional metrics 8 - 11 have been added to better allow understanding of our utilization of various 'managed services' usage and our effective software license position.

Outcome: Develop and manage “utilization reports” for the below metrics:

1) % of available Compute utilized; 2) % of available Memory utilized; 3) % of available Storage utilized; 4) % of available Network utilized; 5) # of active user accounts; 6) # of METIC visit requests;

7) METIC space utilization; 8) # of licenses utilized for all software tools/technologies (capacity management); 9) # of software and hardware assets procured/provisioned; 10) Cost usage reports in hybrid cloud operating model; 11) # of containers (and standard templates) provisioned and consumed by the PMOs

Notes view: 28

Capabilities in Scope: Provide Program Management support services to all DHMS programs as well as other military health organizations as required Personas in Scope: All Use case: ESS currently provides 'customer advocates' to assist PMOs and customers to ensure their needs are met in a timely manner. The customer advocates also assist with onboarding and navigating ESS managed services. They also coordinate the non-standard requests with the PEO DHMS engineering team for final review/approval of such requests.

Outcome: The vendor should streamline the overall program management function and extend the current 'customer advocacy' responsibilities to include: centralizing and managing the governance process, central coordination of activities across multiple PMOs (provide single pane of glass view), develop, update, store, and maintain architecture documentation (that describes the various "as a service" topology) in a shared repository, perform demand analysis from each PMO, generate monthly and quarterly performance reports (via on-demand dashboard and/or reporting capability). The monthly reports should also include the cost consumption and usage metrics for various "services" leveraged by each PMO and ensure the overall operational environment is seamlessly managed in a hybrid cloud operating model.

Notes view: 29

Capabilities in Scope: Provide Program Management support services to all DHMS programs as well as other military health organizations as required Personas in Scope: All Use case: ESS currently provides Tier 1–4 Service Desk support for PEO DHMS customers. ESS also currently provides partnership with the PEO DHMS Change Management CM team to review and manage Change Requests (CR) submitted to the PEO Change Control Board (CCB). Additionally, ESS currently provides support for specialized projects, including facilitating POCs for new tools/technologies.

Outcome: The vendor should continue providing the Tier 1–4 Service Desk support for PEO DHMS customers along with the support for specialized projects. The service desk tickets should be routed from the enterprise ITSM system (SDLCNext). A new workflow process should be developed and implemented in the enterprise ITSM tool to manage all service tickets, CRs, and non-standard requests. The new enhanced ITSM workflow should be automated (via integration with the standardized service catalog (store front) to allow for the PMO users to self-provision services (where possible) and generate alerts/notifications to appropriate stakeholders for approval/tracking/reporting purposes.

Notes view: 30

All Categories

Notes view: 31

Use case: Provide network capability to allow users to connect to .com and .mil in the METIC and DDC and connect to Wi-Fi in METIC. The purpose of Wi-Fi capability in the METIC is for testers and users to connect remotely for various services.

Outcome: Provide secure network capability to allow users to connect to .com and .mil in the METIC and DDC and connect to Wi-Fi in METIC

Use Case| All Categories Capabilities in Scope: Provide integrated support across all as a service offerings to support all DHMS programs as well as other military health organizations as required Personas in Scope: DHMSM, JOMIS, Cyber, DT&E

Notes view: 32

Use case: ESS currently procures, installs, and configures software tools for programs. However, ESS does not manage the tools - programs are responsible for managing their own tools. These tools are currently provisioned in the 'Test Tools' enclave.

Outcome: Host, support, and provide ease of use automated managed software for any/all tools/technologies through standardized service catalog via automated self-service portal (store front). The vendor should track/monitor/report the tool(s) license usage and manage/report capacity planning of all the deployed tools usage patterns.

Capabilities in Scope: Provide integrated support across all as a service offerings to support all DHMS programs as well as other military health organizations as required Personas in Scope: DHMSM, EIDS, JOMIS, Cyber, DT&E

Notes view: 33

Use case: ESS currently performs ongoing optimization and improvement/upgrades, administration, and operation of networks and systems for DCaaS, DaaS, IaaS, PaaS, CaaS, and SaaS. The desired outcome captures optimization, improvement, and should streamline operations.

Outcome: Perform ongoing optimization, improvement, upgrades, administration, and operation of networks and systems to support DCaaS, DaaS, CaaS, and IaaS (e.g., VMWare resource pools, storage), PaaS, and SaaS capabilities. Appropriate metrics should be developed and reported on operational efficiency at govt approved pre-defined intervals.

Capabilities in Scope: Provide integrated support across all as a service offerings to support all DHMS programs as well as other military health organizations as required Personas in Scope: All programs

Notes view: 34

Use case: ESS currently provides network connectivity to the METIC for medical device and application testing. However, they do not currently provide access to SIPRNET as well as network connection for Garrision and .mil for DHMS program capabilities such as OpMed. The desired outcome will enable network connectivity to appropriate end points for better user experience and reduction of latency. Once development and test activities are fully achieved in .COM (configured to meet minimal DISA STIG standards), applications may migrate to .MIL for Government independent test and integration on the DoD Non-Secure Internet Protocol Router Network (NIPRNET).

Outcome: Provide operational support and optimize DoD Network enclaves' (e.g., Med-COI, NIPRNET and SIPRNET) network connection for Garrison and .mil for DHMS program capabilities such as OpMed. Provide access to secret network/vault for DHMS and DoD health programs conducting high side testing using SIPRNET in secure facilities.

Capabilities in Scope: Provide integrated support across all as a service offerings to support all DHMS programs as well as other military health organizations as required Personas in Scope: DT&E

Notes view: 35

Thank you oleObject2.bin image2.emf image3.png image4.png image5.png oleObject77.bin oleObject44.bin oleObject78.bin image12.emf oleObject12.bin oleObject79.bin oleObject80.bin oleObject81.bin oleObject82.bin oleObject83.bin oleObject84.bin oleObject85.bin oleObject86.bin oleObject87.bin oleObject88.bin oleObject89.bin oleObject90.bin oleObject91.bin oleObject92.bin oleObject93.bin oleObject94.bin oleObject95.bin oleObject96.bin oleObject97.bin oleObject98.bin oleObject99.bin oleObject100.bin oleObject101.bin oleObject102.bin oleObject103.bin oleObject104.bin oleObject105.bin oleObject106.bin oleObject107.bin oleObject108.bin oleObject109.bin oleObject110.bin oleObject111.bin oleObject112.bin oleObject38.bin oleObject113.bin oleObject1.bin image1.emf