Attachment 1 H2FMS RFI Admin Instruc Final 4AUG2025.pdf

Attachment #1 RFI with Admin Instructions

RFI_W91CRB_H2FMS

Request for Information (RFI) 2 for 3 Holistic Health and Fitness Management System (H2FMS) 4

Issued By 5 Product Manager Holistic Health and Fitness 6

(PdM H2F) 7

RFI_W91CRB_H2FMS 9

The U.S. Army Contracting Command-Aberdeen Proving Ground (ACC-APG), on behalf 11 of Product Manager Holistic Health and Fitness (PdM H2F), is seeking information from 12 Industry regarding capabilities to develop, integrate, deploy, and sustain the Holistic 13 Health and Fitness Management System (H2FMS). 14

1.0 Program Background 16

PdM Holistic Health and Fitness provides the Army with scientifically supported training, 18 education, tools, and strategies to enhance individual and unit readiness across H2F’s 19 five domains (physical, mental, spiritual, nutritional, and sleep). 20 PdM H2F has a current need for a human performance data management system in the 22 field to record and collect data from all five domains, prioritizing the physical, nutritional, 23 and sleep domains. The contemplated system, referred to as the H2F Management 24 System (H2FMS), will provide a comprehensive and integrated approach to managing 25 Soldier performance and well-being, leveraging data and analytics to inform decision-26 making and drive performance optimization. The H2FMS will provide an intuitive 27 interface tool for measuring, assessing and monitoring Soldier readiness. 28 The Department of Defense (DoD) currently has several personnel systems that track 30 various data points about Soldier training, assessments, injury, and demographics. 31 Many assessments are administered manually with paper/pen or across various DoD 32 websites. Traditional performance optimization methods have relied on local protocols 33 and manual tracking, which are limited in their scalability and effectiveness. Moreover, 34 these systems are limited in their ability to monitor physical, mental, sleep, nutritional, 35 and spiritual performance at the frequency and detail required to support H2F. There is 36 currently no system to enable H2F to facilitate data-informed actions, leveraging 37 domain-specific information to improve performance daily and over longer timeframes. 38 To meet H2F strategic objectives, the Army requires a software tool capability (H2FMS) 40 that can economically scale human performance teams (HPTs) and Area Support 41 Teams (ASTs) across the force and manage the application of those experts. H2FMS 42 will ingest Soldier fitness and performance data entered by users, analyze the data, and 43 enable leaders and HPTs to intervene with optimal training, education, and access to 44 care protocols. Role-based configurations will enable specific access to data, features, 1 and functions in the software and Amazon Web Services (AWS) cloud environment, 2 ensuring that users have the information and tools they need to perform their duties 3 effectively. 4 The H2FMS will provide intuitive user experiences with personalized individual Soldier 6 feedback and access to H2F resources and will enable leaders to make data-informed 7 decisions. A software capability is sought to simplify design, reduce costs, ensure 8 consistency, and facilitate scalability for the Army's H2F system. 9 The H2FMS will also enable enterprise-level trend analysis, tying directly to strategic 11 metrics for measuring return on investment for H2F and the H2FMS capability. This will 12 enable doctrine refinement and implementation of H2F best practices across the force. 13 As an enterprise-level system, H2FMS will allow Soldiers to maintain access to their 14 performance data throughout multiple duty stations, coaches, and leaders. By scaling 15 the H2FMS capability and providing it to every Soldier in a cost-efficient and feature-16 native platform, the Army will be able to efficiently collect and disseminate H2F doctrine 17 and techniques, enabling brigade unit readiness to fight and win as a premier land force 18 in multi-domain operations. 19 Every Soldier will have access to the H2FMS so that the individual can complete 21 assessments, log and track habits and scores for assessments performed outside of the 22 software, see trends from Bring-Your-Own-Device (BYOD) or government procured 23 wearable monitors, see their own performance historically and in near real-time, and 24 interact with H2F staff in one place. H2F staff will use the software to interact with 25 Soldiers, create and send Soldiers activity plans and educational material, create, 26 assign and receive Soldier assessments, schedule appointments, and schedule room 27 use. H2FMS will enhance Soldier lethality by providing a comprehensive assessment of 28 key performance indicators while supporting the Army’s culture of health, wellness, and 29 fitness. 30 See “Attachment 2 H2FMS Concept Exhibit Slides.pdf” included as an attachment to 32 the SAM.gov announcement for this RFI, which provides a draft visual system concept 33 overview (OV1) as well as a draft high-level system concept diagram (AV1) provided for 34 illustration purposes only. 35

2.0 Program Objectives 1

2.1 Software Must Haves: 3

The target timeframe for software application delivery is early 2QFY26. The Army 5 considers the following criteria and components to be essential to satisfy the overall 6 vision of the H2FMS requirement. *Note - The Army must have exclusive rights to all 7 data collected. Data collected cannot be distributed without the explicit consent of the 8 Army. 9

2.2 Core Application Features: 11

o Meets Department of Defense (DoD) Cybersecurity Requirements 13 o API Integration and Scalability with AWS GovCloud 14 o In-app Tutorials/Self Start Learning 15 o Role-Based User Interface with Role Toggle (Functionality tailored to roles—16

Soldier, H2F Performance Team, Leader, Administrator) 17 o Data Sanitization and Validation 18 o Basic Analytical Toolkit (Trend Identification & Reporting) 19 o Software Utilization Tracking 20

2.3 Mission Software Features—Physical, Nutrition and Sleep (Rolling Release): 22

2.3.1 H2F Readiness Dashboard 24

Empowers Soldiers and provides Leaders with a comprehensive, at-a-glance view of 26 individual and collective readiness. This dashboard brings together information providing 27 personalized insights and actionable recommendations. 28 o Readiness Summary (Tracked data from the H2F Domains) 30 o Comparative Data (Unit, MOS, Army Averages) 31 o Progress Tracking and Goal Setting 32 o Customizable User Interface 33

2.3.2 Physical Training (PT) Program Module: 35

Enables H2F Performance Teams, Leaders, and Soldiers to build, assign, monitor, and 37 adapt individualized and unit-level training programs aligned to readiness goals, MOS 38 demands, injury history, and wearable feedback. Facilitates data-driven PT 39 programming with interoperability to Army readiness systems and longitudinal analytics 40 fostering Soldier motivation, competition, and community. Some key sub-features are: 41 o PT Plan Builder (Import and Drag-and-Drop) 43 o Event-Aware Scheduling (Individual, Team, and UIC) 44 o Exercise Library/Instructional videos with user upload 45 o Army Fitness Test Scoring, Reporting, and Tracking 46 o Daily, Weekly, and Cumulative Load Dashboard 1 o Fitness Leaderboard 2

2.3.3 Nutrition Manager Module: 4

Empowers Soldiers to optimize performance through personalized nutrition guidance, 6 tracking, and education and provides a critical capability for Leaders and H2F 7 Performance Teams to monitor and improve Soldier readiness. This module integrates 8 wearable data to provide tailored recommendations based on individual needs, activity 9 levels, and dietary restrictions. Key sub-features are: 10 o Personalized Meal Planning (Calorie/Macro Targets, Dietary Preferences, 12 DFAC Meal Options) 13 o Food Logging (Manual Entry & Image/Barcode Scanning) 14 o Nutrient Tracking (Macro/Micronutrient Analysis) 15 o Recipe Library (with User Upload) 16 o Hydration Tracking 17 o Nutrition Education Resources 18

2.3.4 Sleep Management Module: 20

Enables Soldiers to monitor recovery and optimize sleep habits as well as provide 22 Leaders and H2F Performance Teams an opportunity to proactively address fatigue and 23 maintain peak performance. This module tracks sleep patterns, identifies deficiencies, 24 and recommends strategies for improved sleep quality. Key sub-features are: 25 o Sleep Tracking (Automatic & Manual Entry) 27 o Sleep Stage Analysis (Light, Deep, REM) 28 o Sleep Hygiene Education 29 o Personalized Sleep Recommendations 30

2.3.5 Decision Support Module: 32

Provides Leaders and H2F Performance Teams with actionable insights to optimize 34 program effectiveness and Soldier readiness. This module centralizes data collection, 35 analysis, and reporting, enabling identification of trends and decision opportunities. Key 36 sub-features are: 37 o Questionnaire Management Toolkit 39 o Data Alert Management Toolkit and Push Notification 40 o Leader Dashboards and Exportable Reports 41

2.3.6 Additional Capabilities to be Released: 44

o Dashboard Management Toolkit 46 o Education Library Management Toolkit 1 o Business Rule Automation Toolkit 2 o Schedule Management Toolkit 3 o Advanced Analytical & Reporting Toolkits 4 o Commercial API Integration 5 o Mental Fitness & Mindfulness Toolkits 6 o Offline Capability 7 o Communication System Manager 8

2.4 Software Development (SWD) Overarching Objectives: 10

o Consolidate disparate resources into a single platform 12 o Enable role-based permissions for access to data and features 13 o Give Soldiers digital/virtual access to communicate with the H2F Performance 14

Team 15 o Manage and track personnel and facility use 16 o Create, manage and assign customized training for each domain to include 17 reading, video, and audio, exercise and nutrition plans 18 o Allow information previously written by hand to be digitally recorded and 19 analyzed (e.g. AFT, pass/fall classes, completion of assignments, exercise and 20 food tracking, etc.) 21 o Software Use & Performance Tracking: end user tracking of H2FMS utilization, 22 system performance, and data synchronization with external sources 23 o Ingest data from wearable physiological monitors and connect with other Army 24 systems of record via secured Application Programming Interface (API) that allow 25 scalability 26 o Produce alerts when individuals or groups fall outside set parameters 27 o Automate operations and software functions triggered by events or alerts 28 o Integrate with the Army data lakehouse - Impact Level (IL) 5 29 o Provide software training and support 30 o Manage the software using DEVSECOPS platform 31 o Analyze and present data at each echelon up to brigade level commanders 32 o Must provide a vendor agnostic solution 33

2.4.1 SWD Technical Objectives: 35

o Must be Impact Level 4 with a privacy overlay and FedRAMP Moderate compliant 37

Must be able to implement a standardized scalable methodology for anonymizing 38 data 39 o Create unique identifiers to air gap/containerize data from general users 40 o Must be able to sanitize and validate air gapped/containerized data 41 o Must be able to create user visualization dashboards 42 o Must be able to support one-way data transfer via secured API pull from an IL5 43 data lakehouse environment at set recurring and ad hoc intervals. 44 o May be required to obtain an IL4/ FedRAMP Moderate compliant environment with 45 additional privacy controls 46 o May be required to obtain Defense Information System Agency (DISA) Provisional 1 Authorization (PA) 2 o May be required to obtain Authority to Operate (ATO) 3 o Role-Based User Interface with Role Toggle (Functionality tailored to roles—4

Soldier, H2F Performance Team, Leader, Administrator) 5

3.0 General Request for Information Requirements 7

This Request for Information (RFI) is seeking information from Industry to determine 9 their capabilities to act as a Prime contractor in the development, integration, 10 deployment, and sustainment of the H2FMS and is being issued solely for information 11 and planning purposes and shall not create any obligation on behalf of the Government. 12 Respondents who wish to contribute to any potential future contracts as a subcontractor, 14 rather than as a Prime, should clearly state this. 15

This RFI does not constitute a Request for Proposal (RFP) or a promise to issue an RFP 17 in the future. A solicitation for the H2FMS is not available currently. Requests for 18 solicitation will not receive a response; unsolicited proposal responses to this request will 19 not be considered as offers. Submissions will not be considered offers or proposal 20 responses, competitive evaluation of narrative and sample submissions (if applicable) will 21 not occur, nor will any binding contract award be made because of this request. All 22 information contained in this RFI notice is preliminary, subject to modification, and is in no 23 way binding on the Government. Telephone requests for additional information will not be 24 honored. This notice does not constitute a commitment by the United States Government 25 to contract for any supply or service whatsoever. All submissions in response to this 26 announcement are voluntary; therefore, the United States Government will not 27 compensate any vendor for information and/or samples submitted or any expenses 28 incurred with preparing a submission. 29

The Government intends to review all responses received, but based on the number of 31 responses received, may perform prioritized reviews at the Government’s discretion at 32 varying levels of detail as needed due to Government resource constraints. 33 The Government may not provide feedback to any/all vendors providing questions or 35 submissions to this RFI. 36 RFI participation is voluntary and does not preclude any vendor from participating in any 38 future RFP, if any is issued. It is the responsibility of vendors to monitor this website for 39 additional information pertaining to this requirement. 40 This RFI seeks to determine the availability and maturity of commercially available/non-41 developmental solutions, including modular solutions that could be used and/or modified 42 to fulfill the overall objectives of the H2FMS program. Modular solutions would need to 43 be capable of being combined/integrated with other solutions to create a single, unified 44 software solution for H2FMS. 45

4.0 RFI Responses 1

4.1 General 3

Potential sources who believe they possess the qualifications, expertise and 5 experience to provide an H2FMS solution are requested to provide voluntary 6 responses to this RFI by submitting narrative responses and samples (optional) to the 7 points of contact listed below. 8

Responses SHALL NOT CONTAIN CLASSIFIED INFORMATION and proprietary 10 information shall be clearly marked as such. 11

Responses will include a cover page, a one-page executive summary, and shall not 13 exceed (10) pages. Ensure the response is typed in 12-point font, single spaced, 14 with one (1) inch margins. Page count includes any appendices or attachments 15 (other than the industry recommendations and technical questions requested below). 16 Page count does not include a cover page or one-page executive summary. 17

RFI responses shall not include cost/price information outside of a rough order of 19 magnitude (ROM). Detailed cost and pricing information will be requested as part of a 20 potential future RFI if necessary, or through a future RFP. 21

RFI responses are encouraged to include industry recommendations and/or any 23 technical questions about the stated program objectives that may be helpful to the 24 Government in planning the acquisition strategy and developing the details of the 25 requirement. These responses should be submitted as an Appendix, which will not be 26 counted against the 10-page limitation. 27

4.2 Key Technical Questions: 29

Industry is requested to address the following questions to assist the Government in 31 understanding the current market conditions and technologies relevant to this 32 requirement. 33

4.2.1 Which Software Development approach would you recommend considering the 35 accelerated schedule, self-guided onboarding, and scale to 111 Active Component 36 Brigades in January FY26 in addition to the SWD objectives for both overarching and 37 technical? 38

4.2.2 What features does your platform software currently possess that have been 40 outlined in the SWD objectives, Software Releases (SR), and technical SWD objectives? 41 o How would you approach developing features not currently available in your 43 software? 44 o Does the timeline allow for feature development not currently available in your 45 software? 46

4.2.3 What features would you add to your software to achieve SWD objectives? How 2 would you phase your solution to meet SWD objectives? 3

4.2.4 If a teaming solution and/or subcontracting is suggested, please identify 5 key/anticipated teaming partners and/or subcontractors if known. Explain how the division 6 of work would be allocated and how features would be integrated into a single platform. 7

4.2.5 What contract/pricing structure/strategy (enterprise, consumption, incentive, etc.) 9 would you recommend for licenses for the following users based on this schedule: 10 o The application will be available in January FY26 for 111 Active Component 12 Brigades 13 o Onboard the Area Support Teams who will support dispersed teams and the HPTs 14 throughout FY26-28 to encompass the entire Army within two years 15

4.2.6 What vendor support strategy would you recommend for addressing technical 17 problems encountered by users of the software? 18

4.2.7 Given the program objectives, please identify risk or software development 20 concerns based on the software release priority for features that could be implemented 21 and deployed, within the first 4 months after award of any contemplated future contract. 22 Please include a brief rationale for your assessment. 23 o Core Application Features 25 o H2F Readiness Dashboard 26 o Physical Training Program Module 27 o Nutrition Manager Module 28 o Sleep Management Module 29 o Decision Support Module 30 o Dashboard Management Toolkit 31 o Education Library Management Toolkit 32 o Business Rule Automation Toolkit 33 o Schedule Management Toolkit 34 o Advanced Analytical & Reporting Toolkits 35 o Commercial API Integration 36 o Mental Fitness & Mindfulness Toolkits 37 o Offline Capability 38 o Communication System Manager 39

4.2.8 What is your estimated rough order of magnitude (ROM) price for the solution you 41 have discussed in your response? Please provide ROM pricing for full solutions only if 42 responding as Prime. ROM should be broken down by each major component of pricing 43 and should reflect pricing for each major project phase (such as Development, 44 Deployment, Sustainment/Maintenance or similar) over the first five (5) years. If you 45 respond as a potential subcontractor, please provide clear ROM pricing for the potential 1 partial solution being discussed. 2

4.2.9 Describe your approach to providing the Government with the necessary rights and 4 capabilities to competitively reprocure, further develop, maintain, and/or sustain the 5 presented solution over its lifecycle. Please address the following: 6 o To what extent can the Government obtain rights to the solution’s architecture 8 (e.g., unlimited rights, government purpose rights, etc.)? 9 o If providing unlimited rights to the architecture is not feasible, please detail an 10 alternative approach that would enable the Government to achieve continuous 11 competitive procurement, further development, maintenance, and sustainment. 12 o Clearly articulate any concerns you have regarding providing broader rights to 13 architecture and explain how the Government could reasonably execute your 14 presented alternative approach. 15

4.2.10 Cybersecurity: 17

Respondents should identify their approach to cybersecurity and ability to meet 19 DoD/Army requirements for the overarching objectives and the specific software 20 development option(s) they are responding to. 21

Cybersecurity Requirements: 23

Ability to obtain an ATO to include desktop and mobile applications in an IL2 and IL4 25 environment. Minimum FEDRAMP Moderate certified and the ability to obtain a 26 Defense Information System Agency (DISA) Provisional Authorization (PA). The system 27 must comply with all relevant federal and military regulations, including those related to 28 healthcare data, cybersecurity, data protection, and contractor compliance. This 29 includes adherence to any federal regulations such as Health Insurance Portability and 30 Accountability Act (HIPAA), NIST, DFARS, FISMA, and DoD Instructions, as well as 31 compliance with Army regulations related to medical records, personnel data, and 32 cybersecurity. Additionally, the system must operate in a cloud computing environment 33 in accordance with DoD, NIST RMF, and federal cloud computing regulations and 34 standards and comply with NIST SP 800-53 v4/5. The H2FMS must also ensure the 35 confidentiality, integrity, and availability of sensitive health and fitness information, 36 including personally identifiable information (PII) and protected health information (PHI), 37 and mark data/documents to protect sensitive information. 38

4.2.11 Software Development Capability: 40

Respondents are requested to detail their approach to 1) rapid prototyping and 42 development; 2) establishing and maintaining segregated DEVSECOPS and production 43 environments utilizing cloud/virtualization technologies; 3) continuous monitoring and 44 improvement of the live production environment; 4) use of baseline source code from 45 previous H2FMS solution. Suggest a recommended impact level based on industry’s 46 best practice. Describe your software delivery using a Continuous 1 Integrations/Continuous Delivery (CI/CD) automated pipeline. 2

4.2.12 Software Training Plan: 4

Respondents should outline their comprehensive approach to designing and delivering 6 a phased training program that empowers all user groups – practitioners, managers, 7 leaders, and general users – to successfully access and utilize the new software 8 application. This should include a description of how the training will be structured 9 across phases, the methods used to assess user understanding, and how feedback will 10 be incorporated for continuous improvement. Please also detail the initial 'get-started' 11 resources provided to leaders, practitioners, and managers upon application release. 12 These resources should clearly highlight key features and functionality and explain how 13 they support the users’ specific roles and responsibilities. Specifically, describe the 14 format of these resources (e.g., quick start guides, videos, webinars) and how their 15 effectiveness will be measured. 16

4.2.13 Data Rights: 18

The Government is seeking unlimited rights to the architecture associated with any 20 contemplated H2FMS solutions to competitively reprocure, maintain, and/or sustain the 21 solution in the future. Interested parties who do not want to provide unlimited rights to 22 the emergent reference architecture are requested to provide an alternative approach 23 the Government can use to competitively reprocure, further develop, maintain, and/or 24 sustain the contemplated deliverables. Responses should clearly articulate the basis for 25 concerns and how the Government could reasonably execute the approach in any 26 future acquisition efforts. 27

4.2.14 Potential Delivery Timelines: 29

Responses should specifically address their ability to deliver the outlined H2FMS 31 solution(s) by early 2QFY26. However, if the respondent believes that this timeline is 32 not feasible or unrealistic, an alternative timeline for software deployment is requested 33 with adequate supporting rationale. 34

5.0 Administrative: 36

Responses shall include the following information on the cover page: 38 o Vendor's name, address, point of contact, phone number, and e-mail address. 40 o Commercial and Government Entity (CAGE) Code. 41 o Unique Entity ID (created in SAM.gov). 42 o Business size/type (large business, small business, small-disadvantaged 43 business, 8(a) certified small-disadvantaged business, HUBZone small 44 business, woman-owned small business, very small business, veteran-owned 45 small business, service-disabled veteran-owned small business). 46 o Primary NAICS code. 1 o Does your entity qualify for the Non-Traditional Defense Contractor (NTDC) 2 designation, as defined in Title 10 US Code §3014? (Yes or No) 3 o Does your entity intend to propose as a prime? (Yes or No) 4 o Sample software demonstration video submitted (Yes or No) 5

Responses to this RFI shall be submitted via e-mail as follows: 7

Points of Contact (Narrative): Mr. Eric J. Roberts at eric.j.roberts48.civ@army.mil and 9 Mr. Alexander S. Obriwin at alexander.s.obriwin.civ@army.mil. 10

Response Time and Date: Responses or questions shall ONLY be submitted to the 12 above-mentioned Points of Contact no later than the SAM.GOV response date. 13 Requests for extension will not be considered. Subject line for responses shall read: 14

RFI [Question(s) -or- Response] RFI_W91CRB_H2FMS, [First word in Vendor’s 16 Business Name]. 17

Example: “RFI Response RFI_W91CRB_H2FMS, ACME”. 19

6. Optional Submission: 21 Submission of Sample Software Demonstration (Optional): Vendor may provide videos 23 of sample software no longer than 30 min in total duration. File names must include 24 vendor names. 25

Sample Software Demonstration videos, or website links to them, shall be emailed to 27 the above points of contact in section 5 as well as to the below submission point of 28 contact no later than the “Date Offers Due” response submission deadline posted to 29 the SAM.gov announcement for this RFI: 30

ATTN: MAJ Michael Ashburn 32 Email: michael.a.ashburn8.mil@army.mil 33

ATTN: Daniel Chang 35 Email: daniel.s.chang7.ctr@army.mil 36