DevMAC Reboot_Final_v2_1.pdf

Development Multiple Award Contract (DevMAC) Reboot Request for Information

November 2023

BLUF

PEO DHMS must maximize value in a rapidly evolving Healthcare Industry.

DevMAC will provide an ecosystem of “builders” with expanding capabilities to leverage the Federal Single-Record Ecosystem and drive innovation across the Health IT sector.

2CUI//SP-PROCURE//DL ONLY

List: DoD Civilian and Military Personnel, WF3.0 Support Contractor, CFO Support Contractor

The “Product Line”

At its worst, in Model 1, most of the Software Development Life-Cycle (SDLC) is indirectly procured and managed.

Development talent is “sourced” by others with little input and/or visibility. Talent is sporadic, siloed, and/or transient and the products produced look and behave very “DoD”.

Legacy support contracts from Models 1 and 2 are usually very Government work focused and level of effort was applied to Government specified activities with little alignment to value for PEO customers.

These findings are not specific to PEO DHMS, but are common throughout DoD, resulting in updated software strategies at the DoD level.

PEO 3.0 is how we’ve begun to accelerate toward the more modern models that build on our successes with MHS

GENESIS.

Market Engagement leading up to PEO 3.0 launch clearly showed depending on developers to have DoD experience severely erodes available talent, and because of this, creativity was minimal and Government civilians were overwhelmed with “how”.

Operating Model 1 Multiple Developers – Single

Integrator

Operating Model 2 Multiple Developers – Multiple

Integrators

Operating Model 3 Fully Managed Solution

Single provider to configure, develop, integrate and manage licenses to provide a fully managed solution

Each development contractor provides different levels of management of the fully managed cloud stack.

Support levels are one of the following:

• Fully managed cloud stack is maintained by developer

• Fully managed cloud stack is a maintained in part by developer and the Government

• Fully managed cloud stack is maintained by a third party

PEO 2.0 Current State

JLV

DES

TMIP-J

Integrator

Application #1

Application #2…n

End User View

Integrator

Application #1

Application #2…n

End User View

Integrator for each Branch of Service

4CUI//SP-PROCURE//DL ONLY

The Burning Platform

PEO DHMS portfolio is a blend of buying and building capabilities

Various barriers baked into legacy approaches significantly reduce our ability to focus on: 1) user-centricity, 2) design thinking, 3) product thinking, and 4) value alignment/financial responsibility.

Capabilities

Mature (mostly) process to “buy” capabilities

Focus on maturing ability and throughput to “build” capabilities Buy Build

5CUI//SP-PROCURE//DL ONLY

Workforce 3.0

DevMAC

Workplace 3.x

CustomerX

Enablers “Products”

Every other Part of PEO 3.0 is about DevMAC

Illustrative for conceptual discussion, not exhaustive or decisional!

Question: How does the Government make it easier for developers, integrators, and all other prime contractors?

Question: What “enablers” should remain with the developer?

The “enabler” for DevMAC

DevX (nee: FXaaS)

• Simplify access to critical data connections

• SDK Libraries

• API/ICD Portfolio Library

• Tons and tons of guides

• Standard language/UI elements/cookbooks

• Pipeline Templates

• Concierge Security/Accred. support

• Concierge CAC support

• Cloud environment/account management

• On-prem environments/labs

• License concierge

• Onboarding Devs

6CUI//SP-PROCURE//DL ONLY

DevMAC

There’s no single or “right” answer

Illustrative for conceptual discussion, not exhaustive or decisional!

We just want to maximize talent and ideas across the continuum!

There are many different development/design/data paradigms that require different solutions! We don’t want DevX to limit possibilities; the point is to make stuff easier (and it’s possible standardization could do that, but maybe not!).

DevX (nee: FXaaS)

• Simplify access to critical data connections (managed solution)

• SDK Libraries (maybe curate SDKs created by others, maybe create them as a service)

• API/ICD Portfolio Library (maybe curate, maybe create, maybe maintain)

• Tons and tons of guides (maybe curate, maybe create, maybe maintain)

• Standard language/UI elements/cookbooks (manage and provide orientation)

• Pipeline Templates (manage and provide orientation)

• Concierge Security/Accred. Support (managed service)

• Concierge CAC support (managed service)

• Cloud environment/account management (procure capacity, provide as a service,

• On-prem environments/labs (managed solution)

• License concierge (managed solution)

• Onboarding Devs (managed solution)

7CUI//SP-PROCURE//DL ONLY

DevMAC Product Line

The Development Multiple Award Contract (DevMAC) will provide and ecosystem of builders with expanding capabilities to leverage the Federal Single-Record Ecosystem and drive innovation across the Health IT sector. But how?

1. Design and deliver a flexible talent pool that can evolve the traditional paradigm of long-term, methodical implementation of large and unwieldy software development projects.

2. Expand the funnel to attract modular teams with varied capabilities and skillsets in crowdsourcing idea generation and execution.

3. Improve the health of the Military Health System (MHS) developer industrial base by reducing barriers to new entrants.

Product Line

GOALS

8CUI//SP-PROCURE//DL ONLY

Agile Development

Includes SCRUM and Extreme Programming

DevSecOps/ DevOps

Development

Waterfall Development

Lean Development

Feature Driven

Development

Rapid Application

Development

Question: How should the different types of development methodologies be grouped into MAC Products?

Example: Alignment by Development Methodologies Each will be its solicitation and result in separate groups of IDIQS

Market engagement leading up to PEO 3.0 launch clearly showed depending on developers that have DoD experience severely erodes available talent;

because of this, creativity was minimal and Government civilians where overwhelmed with “how”

As design thinking and product thinking matured and gained traction, PEO DHMS began to quickly fall behind. This created the perfect opportunity!

The Government envisions to have multiple multiple award contracts based on an alignment methodology that makes the most sense and finds the right balance between integration risk and cost/speed/quality.

The first DevMAC IDIQ “Product” – we think this is our burning platform

Illustrative for conceptual discussion, not exhaustive or decisional!

DevMAC “Products”

9CUI//SP-PROCURE//DL ONLY

The “DevSecOps Lite” Product

Nov 9, 2023

Focus of first MAC Product

Workforce 3.0

• Radically increase Mid- Back-Office Talent and “agency”

• Processes that are efficient and easy (what do we do at a

“corporate” level that drives Devs insane)

• Celebrate wins

• Help measure and make decisions

Workplace 3.x

• Great Mid- Back-Office Tools

• Physical space improvements

• Easy to use/get Flex Space

• Collaboration enablers

DevX (nee: FXaaS)

• Simplify access to critical data connections

• SDK Libraries

• API/ICD Portfolio Library

• Tons and tons of guides

• Standard language/UI elements/cookbooks

• Pipeline Templates

• Concierge Security/Accred. support

• Concierge CAC support

• Cloud environment/account management

• On-prem environments/labs

• License concierge

• Onboarding Devs

CustomerX

• Onboard end-users

• “Aha” Moments

• Front-end of the feedback loop

• In-Field support (including technical)

• Drive adoption/retention

NEW!

Enablers “Products”

PEO 3.0 Update Illustrative for conceptual discussion, not exhaustive or decisional!

DevMAC

• Product Team as-a-Service

• DevSecOps Joint Teams (Gov/Ind)

• DevSecOps Industry Only

• Students/Geeks/Hobbyists

• SBIRS

• Accelerators/Incubators

• Challenges

11CUI//SP-PROCURE//DL ONLY

DevMAC DevSecOps “Lite” Product

Our Definition: This initial effort is not a full Government/ Industry partnership with unified Dev and Ops teams. We don’t currently possess enough Government talent to fill those rolls.

As the Government evolves and matures the Government/ Industry partnership may change, perhaps resulting in additional DevSecOps solicitations.

12CUI//SP-PROCURE//DL ONLY

This probably isn’t the BEST name, please make other suggestions if you have some.

Building the first DevMAC RFP Together

Industry Feedback

Iterative Update

Nov

RFI

Release

Industry Day

TBD

Nov – Dec Weekly release of documents for review and feedback

Dec 2023 RFP Finalized

RFP documentation updates published on SAM.gov

All content regarding DevMAC Reboot will be posted on SAM.gov with conversations on the Hive Hub (https://connect.bidscale.com/hive-hub)

Ad Hoc Hive Hub conversations (https://connect.bidscale.com/hive-hub)

1. This post starts with addressing our foundational unknowns and provides context about our aspirations

2. Feedback will be analyzed to develop further questions and draft RFP artifacts

3. Further engagements will be defined iteratively depending upon the outputs of the analyses

4. Potential final walk-thru industry day prior to release

13CUI//SP-PROCURE//DL ONLY

List: DoD Civilian and Military Personnel, WF3.0 Support Contractor, CFO Support Contractor https://connect.bidscale.com/hive-hub https://connect.bidscale.com/hive-hub

Question: How should talent within a single MAC be grouped into task orders to support DevSecOps/DevOps Development?

By “STACK”

Back End Stack UI/UX Developer

Front End Stack By “SPECIALTY”

Full Stack

Software Developer

Security Software Developer

DevOps Developer

Mobile Developer

Web Developer

By “PRODUCT”

Other?

Product 2

Product 4

Product…n

Talent Alignment

“Product” is up for interpretation. If this is the recommended approach, please provide details

Maximize talent and minimize the risk of integration efforts

Strike the right balance

14CUI//SP-PROCURE//DL ONLY

Potential Roads to the Finish Line

Task Order RFP Release

~120-150 days 90 days

Task Order RFP Release

~90 days

Source Selection Process

Source Selection Process

~30-60 days

Source Selection Process

Task Order RFP Release

The task order road to the finish line depends on how complex the order structure is, which is why we’re starting with this post.

15CUI//SP-PROCURE//DL ONLY

Question: Provide a recommended talent pricing strategy at the order level for your suggested ordering approach.

FAR/DFAR

S Clauses

Data Rights

Licenses

Scope and Ordering Guide

Establish Scope, Task Order Rules of

Engagement, and IDIQ Wide Requirements

Pricing set at the IDIQ level Organize with the Talent Alignment

T-Shirt Sizing Profit/Incentive Structure

DevMAC DevSecOps Lite Product IDIQ

• Next Focus

• Scope and Ordering Guide

• Talent Pricing Strategy

• Eval Criteria

16CUI//SP-PROCURE//DL ONLY

List: DoD Civilian and Military Personnel, WF3.0 Support Contractor, CFO Support Contractor

We will use your responses to create a notional task order strategy (see Attachment 1), and then we’ll work with you on:

Enterprise Intelligence and Data Solutions (EIDS) Program Management Office (PMO)

18CUI//SP-PROCURE//DL ONLY

List: DoD Civilian and Military Personnel, WF3.0 Support Contractor, CFO Support Contractor

Must avoid a gap in coverage with lapsing contract support.

While DevMAC will be a Federal Health Enterprise Contract under PEO 3.0, our initial burning platform deals with immediate EIDS requirements.

CarePoint

Biobank

Agile Core Services Data Access Layer (ACS DAL)

System Access Authorization

Request (SAAR)/ ESAAR Sustainment

Data Management Restructure

Data Governance

(TDS)

Role Based Access Control (RBAC)

Sustainment Only

MHS Population Health Portal (MHSPHP)

CAMP (TBI, PROCR)

BI Tools: SAS, Tableau, Qlik

Managed system/SW Lifecycle

Processes

DEVSECOPS

(Software Factory, Metronome)

M2/MDR

eDQ

DSS

DAVINCI

DMSS (SR,

PROMIS, DMED)

MIP Data Catalog

JHASIR

DVEIVR

DoDTR

SDK

Migrate ISSO and SysAdmin from JTS

Managed Enterprise Requirements and Architecture/Docs

FY23 FY24 FY25

OCT JAN APR JUL OCT

Overview

Mission

Deliver, connect, integrate, and curate health data at the right time, right place, and right format to enable informed decisions, research and innovation across the Military Health System (MHS), services and federal space.

Objectives

• Deliver first-class data platforms for advanced analytics, business intelligence, registries and data discovery capabilities

• Promote interoperability between legacy systems and the DoD’s electronic health record, MHS GENESIS

• Centralize, standardize and analyze data to support data-driven decisions and promote better patient/population health outcomes

• Manage enterprise data and architecture

EIDS PMO is the first customer of the DevMAC DevSecOps “Product”

19CUI//SP-PROCURE//DL ONLY

Data Science & Innovation Presentation Data Exchange Data

Management

CarePointAnalytic Workbench / SSBI / Data Science

Laboratory

ML/AI Workbench

Biobank

Data Lake (S3, Glacier, Amazon

EMR, ODS)

Data Warehouse (RedShift, Data

Virtualization Tools, SQL Studio, DAVINCI, Data Arc SQL, CarePoint – SQL Farm

Patient Lookup Tool

Data Services (per Service Catalog, MHS requests)

DAVINCI

Agile Core Services Data Access Layer (ACS DAL)

Data Exchange Service (DES)

Clinical Health Data Repository (CHDR)

MHS Population Health Portal

(MHSPHP)

System Access Authorization Request (SAAR)

Data Architecture

Data Lifecycle, Mapping, Metadata Mgmt

Data Model

(OMOP)

Data Governance

(TDS)

SLA/OLA Oversight

Role Based Access Control (RBAC)

Applications

RMPMT

Tri-Service Apps (PRT, DPT, DCAT, LM, COHORT

RMS)

CAMP (TBI, PROCR,

WorkWell, Contact

Tracing) eDQ

DSS

BEDSTAT

JHASIR

DVEIVR

ORION

DoDTR

DoDVA

Health Information Archive

SAS

Tableau

Qlikview

Data Solutions

M2/MDR

Current Alignment

Targeted to eventually leverage DevMAC

Question: Is the Government’s assumptions correct? Are there capabilities that should be grouped together?

Does this recommendation contradict or compliment the recommendation for slide #15?

Maximize talent and minimize the risk of integration efforts

Strike the right balance

Government’s assumption is each of the identified “set” should not be split out.

20CUI//SP-PROCURE//DL ONLY

The Data and Logic layers within the MIP enables the platform to operate as the central integrated data broker and service provider for the DHA.

MIP Behind the Scenes

RedS hift

S3

HL7JSON

MOV

Eit

FHIR

SQL

API Gateway Data

Exchange File Transfer

Enterprise Data Warehouse

Structured Data Storage Enterprise Data Lake

21CUI//SP-PROCURE//DL ONLY

Military Health Systems Population Health Portal

Clinical Assessment Management Portal

See Attachment 2 for further detail

The Military Health System Population Health Portal (MHSPHP) is a centralized, secure, web-based population health management system used by Army, Navy, and Air Force (AF) health care teams, as well as Managed Care Support Contractors (MCSC).

Clinical Assessment Management Portal (CAMP) provides an enterprise solution to improve point-of-care decision making and enhance patient-centered care through the collection and management of clinical assessments and patient questionnaires.

Initial Opportunity(ies)

22CUI//SP-PROCURE//DL ONLY

List: DoD Civilian and Military Personnel, WF3.0 Support Contractor, CFO Support Contractor

Traumatic Brain Injury (TBI) Portal and Patient Reported Outcomes Clinical Record (PROCR) are part of CAMP

TBI Portal is to serve as the automated support for the cutting-edge objectives of The National Intrepid Center of Excellence (NICoE) in the areas of Patient Referral Processing and the scheduling of providers, patients, and resources in support of the NICoE project and efforts. The TBI Portal is used to load patient referrals received from various referring providers from MTFs and military medical institutions across the country.

PROCR is a CDS utility for clinical care that focuses on returning military service members to duty and all patients to an active, productive life.

PROCR uses a holistic approach to patient reported outcomes and screening that includes collection of pain-related psychosocial factors, treatment history and MSK health.

Industry Feedback

Industry Feedback Requested

24CUI//SP-PROCURE//DL ONLY

List: DoD Civilian and Military Personnel, WF3.0 Support Contractor, CFO Support Contractor

Attachment 1 has a list of questions and requests associated the information presented. These questions are to inform the MAC IDIQ.

Attachment 2 provides additional information on the initial “task order” opportunity(ies) as well as a list of questions to inform the Government on required information to help support task order competitions.

The information provided will assist in finishing the schedule, developing compensation plans and evaluation criteria.

• Starting Dec 2023, information or requests will be provided an iterative basis.

The Government is investigating an opportunity for office calls or an industry day in December.

• Let us know your preference as part of the response

25CUI//SP-PROCURE//DL ONLY

List: DoD Civilian and Military Personnel, WF3.0 Support Contractor, CFO Support Contractor

The information provided will assist us in finishing the schedule, develop compensation plans and evaluation criteria.

• The Government will be sharing this information on an iterative basis after responses are received.

Thanks for reviewing the DevMAC Reboot

For informal discussions regarding DevMAC Reboot and other opportunities, please visit our HIVE Hub: https://connect.bidscale.com/hive-hub

Official draft and RFP documents available on SAM.gov!

https://connect.bidscale.com/hive-hub