H2FMS CFS Announcement-04SEP.pdf

Holistic Health and Fitness Management System (H2FMS)

Other Transaction (OT) Opportunity

Call for Solutions (CFS)

W91CRB-25-S-H2FMS

In Cooperation with Army Open Solicitation (W9128Z-25-S-A002)

SECTION 1 - Overview

1.1 Background and Introduction

The U.S. Army is advancing its Holistic Health and Fitness (H2F) initiative to strengthen Soldier readiness by addressing the H2F domains—physical, mental, spiritual, nutritional, and sleep. To support this effort, the Army seeks to acquire a unified, digital platform known as Holistic Health and Fitness Management System (H2FMS) utilizing a Modular System Architecture (MOSA) approach.

H2FMS will streamline data across fragmented sources, using new tools to deliver personalized wellness insights, track performance across the Army formations, and support leadership decisions with predictive analytics. This solution aligns with Army modernization goals and empowers soldiers to take proactive ownership of their wellness while enhancing overall unit effectiveness and Soldier lethality.

The Army Contracting Command – Aberdeen Proving Ground (ACC-APG), on behalf of Product Manger Holistic Health and Fitness (PdM H2F), intends to competitively award agreements for a H2FMS prototyping project as detailed below. PdM H2F seeks innovative software solutions, with a preference for commercial or commercially based modified software solutions, that can be rapidly prototyped and offer significant improvements over current capabilities.

The Government anticipates using Other Transaction (OT) Authority, leading to one (1) or more H2FMS Prototype OT Agreements (OTAs) under the authority of 10 U.S.C. § 4022, however, the Government reserves the right, at its sole discretion, to award solution(s) through one or more authorities specified in the Army Open Solicitation. The Government’s intent is to award agreement(s) to prime contractor(s) who provide full prototype solutions either individually or through creative teaming or subcontracting arrangements. The Government encourages competent providers (and any subcontractors) to be on multiple teams to achieve the vision and best solutions. Agreement awards will be dependent on available funding and criteria established in this CFS.

The Government’s expectation is that initial prototype software capabilities will be delivered rapidly after award of any resulting OT agreement(s) as identified in the draft SOO. The Government reserves the right to cancel this opportunity or make no awards in conjunction with this opportunity.

To be considered for an OTA award, interested vendors must comply with at least one of the following conditions of 10 US Code §4022(d):

(A) At least one (1) Non-Traditional Defense Contractor (NTDC), as defined in section 3014 of Title 10 US Code §3014, is participating to a significant extent in this prototype project.

(B) All significant participants in the transaction other than the Federal Government are small business or NTDCs.

(C) At least one third of the total cost of the prototype project is to be paid out of funds provided by parties to the transaction other than the Federal Government.

1.2 Prototype Project – Problem Statement

The anticipated scope of the H2FMS prototype project encompasses:

• Single Software Application: Utilizing established commercial agile development practices, develop a unified software platform to support Soldiers, Leaders, & H2F practitioners, ensuring functionality both with and without embedded Human Performance Technologies (HPTs) or Area Support Teams (ASTs).

• Access Across Devices: Ensure compatibility with personal and government-furnished equipment across major operating systems.

• Role-Based Configuration: Enable customizable permissions for roles such as Soldier, H2F Practitioner, leader, and administrator.

• Integration with Technology: Ensure secure Application Program Interfaces (APIs) are implemented to enable synchronization with human performance technologies, such as wearable devices, Army Systems of Record, and integration with a data Lakehouse. This will facilitate informed decision-making and advanced data analytics.

• User Experience: Deliver an intuitive interface requiring no more than 4 hours of training for administrators and no more than 1 hour of training for end users as well as quick start in-app tutorial to get started in the app under 1 minute. Include personalized content delivery and gamified features to encourage consistent usage and behavioral change.

• Data Management: Integrate with the cARMY environment, the Army Data Lakehouse, and the Enterprise Cloud Management Agency (ECMA) to ensure reliable data management, seamless data sharing, and compliance with Army cloud standards.

• Automation: Implement business rules to automate resource optimization and system functions based on events or alerts.

• Security: Comply with applicable Army cybersecurity and privacy standards, including continuous third-party monitoring and alignment with NIST and Department of the Army protocols.

• Analytics: Provide tools to track software usage and quantify human performance across all H2F domains.

• Comprehensive Coverage: Include management, analysis, and reporting capabilities for all five domains of the H2F program.

• Training and Education: Offer tools to create, manage, and assign training and educational plans, including multimedia content.

• Data Capture and Facilities Management: Enable survey creation, data import, and scheduling for facilities and resources.

• Personnel and Event Management: Include scheduling and notification systems for personnel and event coordination.

• Visualization: Provide customizable dashboards and reporting tools for performance tracking and decision support.

• Strategic Alignment: Support the Army People Strategy by integrating data across all H2F domains to inform decisions at every echelon.

1.3 Call for Solutions (CFS) Procedures

This CFS is a competitive procedure seeking innovative prototype solutions that can address the stated prototype requirements contained in the draft Statement of Objectives (SOO) and the associated supporting documents included within this opportunity. Subject to the availability of funds, this CFS will result in the award of OTs for prototype projects in accordance with 10 U.S.C. § 4022, however, the Government reserves the right, at its sole discretion, to award solution(s) through one or more authorities specified in the Army Open Solicitation. This CFS, and any OT awarded as a result of this CFS, is not subject to the FAR or its supplements.

This CFS is soliciting in accordance with the below instructions and the associated documents provided as attachments. All responses to this announcement will be governed by this CFS.

2-phase Competitive Process. The Government will employ a 2-phased competitive solicitation process to award the OTAs, as outlined below:

Phase 1

Step 1: Request for White Papers (RWP). The Government requests interested vendors to provide white papers on their proposed innovative H2FMS solution. White papers will present the vendor’s planned approach to design, develop, test, and deploy H2FMS software solution prototypes, with a primary focus on the vendor’s proposed technical solution and schedule compliance. White papers will be limited to ten (10) pages. NOTE: Vendor white papers are expected to propose a system level H2FMS solution. White papers addressing only subsets or portions of the H2FMS solution may not be considered for awards or invited to subsequent Steps under this CFS. Vendors that are interested in providing only portions of the solution should seek to privately team or perform as subcontractors with vendors planning to propose as prime offerors for the H2FMS solution.

Phase 2

Step 2: Solutions Demonstration (Government Option). Vendors whose white papers receive a favorable evaluation in accordance with CFS Section 4.1 may be invited to present their solutions demonstrations either virtually through Microsoft Teams or in person at Point of View Retreat Center, Lorton VA, with in-person being the preferred location. The Government reserves the right to limit the number of vendors invited to this step.

The solutions demonstration may not be required for all solutions to proceed to Step 3 and will be requested at the Government’s discretion based on the results of evaluations of the Step 1 White Paper submissions. If requested, the vendor’s solution demonstration will focus on software capabilities demonstrations, areas not able to be covered in the white paper submissions, and other details as provided below.

Step 3: Request for Prototype Proposals (RPP) and OTA Awards. Following Government evaluation of Phase 1 white papers and solution demonstrations (if requested), favorable vendors who are selected for potential award will be requested to submit formal technical and cost proposals and to enter alpha negotiations on OTA terms and conditions. The Government reserves the right to limit the number of vendors invited to submit a proposal.

SECTION 2 – DEFINITIONS

“Call for Solutions” is the terminology used for this action to competitively award prototyping agreements under the authority of 10 U.S.C. § 4022. Please note, any references to “Request for

Solutions” found elsewhere in the documentation associated with W91CRB-25-S-H2FMS shall be understood to mean “Call for Solutions.”

“Nontraditional Defense Contractor” is defined in 10 U.S.C. § 2302(9) as an entity that is not currently performing and has not performed, for at least the one-year period preceding the solicitation of sources by the DoD for the procurement or transaction, any contract or subcontract for the DoD that is subject to full coverage under the cost accounting standards prescribed pursuant to 41 U.S.C. § 1502 and the regulations implementing such section. This includes all small business concerns under the criteria and size standards in 13 C.F.R. § 121.

“Prototype Project” can generally be described as a proof of concept, model, reverse engineering to address obsolescence, pilot, novel application of commercial technologies for defense purposes, agile development activity, creation, design, development, demonstration of technical or operational utility, or combinations of the foregoing. A process, including a business process, may be the subject of a prototype project. Although assistance terms are generally not appropriate in OTA, ancillary work efforts that are necessary for completion of the prototype project, such as test site training or limited logistics support, may be included in prototype projects. A prototype may be physical, virtual, or conceptual in nature. The quantity should generally be limited to that needed to prove technical or manufacturing feasibility or evaluate military utility.

“Nonprofit Institution” means a nonprofit institution, as defined in 15 U.S.C. § 3703 as an organization owned and operated exclusively for scientific or educational purposes, no part of the net earnings of which inures to the benefit of any private shareholder or individual.

“Small Business” is defined under Section 3 of the Small Business Act (15 U.S.C. 632)

“Innovative” means any new technology, process, method, or business practice; or any new application of an existing technology, process, method, or business practice that contributes to enhancing the mission effectiveness of personnel of the Department of Defense or improving platforms, systems, components, or materials proposed to be acquired or developed by the Department of Defense, or to improvement of platforms, systems, components, or materials in use by the armed forces.

SECTION 3 – INSTRUCTIONS FOR WHITE PAPERS, SOLUTIONS DEMONSTRATIONS

AND REQUEST FOR PROTOTYPE PROPOSALS (RPP)

3.1 General Guidelines

a. Unnecessarily elaborate brochures or proposals are not desired.

b. Use of a diagram(s) or figure(s) to depict the essence of the proposed solution is strongly encouraged.

c. Technical data with military application may require appropriate approval, authorization, or license for lawful exportation.

d. All White Papers, Solutions Demonstrations and Prototype Proposals are strongly encouraged to be UNCLASSIFIED. White Papers, Solutions Demonstrations and Prototype Proposals containing data that is not to be disclosed to the public for any purpose or used by the Government except for evaluation purposes shall include the following on the cover page (or slide, handout, etc. for Solutions Demonstrations and Oral Presentations):

"This [select one: White Paper, Solutions Demonstration or Prototype Proposal] includes data that shall not be disclosed outside the Government, except to non-Government personnel for evaluation purposes, and shall not be duplicated, used, or disclosed -- in whole or in part -- for any purpose other than to evaluate this submission. If, however, an agreement is awarded to this Company as a result of --or in connection with - the submission of this data, the Government will attain certain data rights, subject to the negotiated terms contained in the resulting agreement. This restriction does not limit the Government's right to use the information contained in this data if it is obtained from another source without restriction. The data subject to this restriction are contained in sheets [insert numbers or other identification of sheets]"

Each restricted data sheet should be marked as follows:

"Use or disclosure of data contained on this sheet is subject to the restriction on the title page of this proposal. "

e. Submissions must be submitted electronically via the instructions included herein.

f. Submissions sent through other channels or after the CFS period has ended will not be reviewed nor evaluated.

3.2 STEP 1 - White Paper Instructions

The Government may be unable to evaluate the white paper if a vendor fails to provide the information requested below.

White Papers are limited to ten (10) pages, not including the Cover sheet, Executive Summary, and required Annexes. White paper submissions that exceed the page limits in the Request for White Papers (RWP) will not be evaluated beyond the stated limitations. Vendors shall organize their white papers as described in the attached RWP.

Vendors shall not include any other items (e.g., brochures, data sheets, etc.) with their white paper submission.

Vendors shall format their white papers in accordance with the following:

Item Format

Minimum Font Size (Narrative) 12pt

Minimum Font Size (Spreadsheet) 10pt

Minimum Font Size (Figures & Tables) no less than 8pt

Font Color Automatic (black) (Body Text & Headings)

Line Spacing (minimum) Single (1.0)

Page Size 8.5” x 11”

Page Margin 1” Left, right, top, bottom

Page Number Location Bottom Center

Page Background None - Backgrounds/Themes not allowed

Table Heading Shading None / No Fill

Table Cell/Row Shading None / No Fill

Table Line color Automatic

NOTE: White papers SHALL NOT CONTAIN CLASSIFIED INFORMATION and proprietary information shall be clearly marked as such.

3.2.1. White Paper Contents

Detailed instructions for white paper content requirements are available as a separate “Request for White Papers (RWP)” attachment to the SAM.Gov post.

3.2.2. White Paper Submission

White papers shall be submitted via e-mail to the following points of contact (POC):

• Mr. Dennis A. Beauclair Jr. dennis.a.beauclair3.civ@army.mil,

• Mr. Alexander S. Obriwin alexander.s.obriwin.civ@army.mil, and

• MAJ Michael A. Ashburn at michael.a.ashburn8.mil@army.mil.

White papers shall be submitted to the above stated points of contact no later than the due date and time posted on the SAM.gov combined synopsis/solicitation associated with this CFS. Responses received after the response time and date will not be considered. Requests for extension will not be considered.

Subject line for responses shall read: “H2FMS White Paper, (First word in Vendor’s Business Name).” Example: “H2FMS White Paper, ACME”

Questions regarding this opportunity may be submitted to the Government white paper submission POCs identified above no later than five (5) business days prior to the close of white paper submissions.

PHASE 2

3.3 STEP 2 - Solution Demonstrations

If invited, vendors will be provided with a time block of up to two (2) hours for their solution demonstration. For planning purposes 30-45 mins should be allocated to software demonstration and 75 to 90 minutes to presentation topics and discussion. Set-up time is not included in the time block. If presenting in person, vendors may arrive up to 30 minutes before their scheduled start time to set-up for their demonstration or they may show up for introductions and overviews from the PEO and Proponent leadership. In-person solution demonstrations will be held at Point of View Retreat Center, Lorton, VA.

Virtual demonstrations will be conducted via Microsoft Teams. The Government will make the final determination as to whether a demonstration is conducted in person or virtually. The Government will provide invited vendors with a scheduled date and time and other pertinent demonstration details as soon as reasonably available upon favorable white paper reviews. The schedule will be determined by the Contracting Office. The vendor shall be limited to no more than five (5) personnel. Personnel who attend demonstrations shall be employed by the prime vendor or a significant teaming vendor. The Government may request verification prior to or after solution demonstrations. Solution demonstrations are intended to be interactive, with the Government able to ask questions at any point. The vendor’s personnel must be able to demonstrate the vendor’s solution and answer technical and programmatic questions on the vendor’s solution. The vendor is responsible for bringing their sample hardware to the designated location. The demonstration may be video recorded by the United States Government (USG); the vendor is not authorized to record any part of the demonstration. After the vendor’s demonstration, the Government may request clarification of any points addressed which are still unclear.

Vendors shall provide an accompanying PowerPoint presentation not to exceed twenty-five (25) slides.

The due date and time for PowerPoint presentations will be provided as part of the Step 2 invitation, and a very short turnaround time may be required for submission of the demonstration presentations. Any slides or material not presented in the allotted demonstration time will be removed from the presentation and disregarded by the Government for evaluation. The Government reserves the right to remove any material that is illegible. Unsolicited changes to the presentation after submission will not be accepted.

3.3.1 Software Demonstrations. Solutions must demonstrate applicability to real-world Army use cases, including individual Soldier performance tracking, unit-level readiness assessments, and administrative/technical support for the H2F Front End Solution. Demonstrations should reflect how the system will support decision-making and health optimization across all five H2F domains.

Vendor should provide sample software capabilities as described below.

Dashboard Capability: User interfaces must present integrated views of performance across the five domains. Dashboards should highlight correlations (e.g., reduced sleep impacting physical output) and provide actionable insights. Vendors will demonstrate the ability to change and modify integrated views at the command level.

Role-Based Access: H2F team members (e.g., HRTs, strength coaches, and athletic trainers must be able to view and act on shared data to coordinate care and training strategies. Vendors may demonstrate how administrators will be able to view who has access to specific dashboard and demonstrate the ability to make changes to the unit/echelons/Army Commands.

Predictive Analytics: Vendors may demonstrate how their system uses historical and real-time data to forecast readiness risks and recommend interventions across all three domains

Cross-Domain Data Synchronization: Vendors may demonstrate how their solution/system allows the ability for real-time data exchange between physical activity metrics, nutritional intake, and sleep quality indicators. (For example, sleep duration and recovery scores could influence physical training recommendations, while caloric intake and hydration status could adjust recovery protocols and exertion thresholds).

Soldier Experience & Accessibility/Ease of Use: Solutions must feature intuitive, role-based interfaces tailored to Soldiers, leaders, and H2F practitioners. Vendors should be able to show how soldiers/leaders/HRTs will easily navigate the software. Vendors should also explain the process of submitting tickets for help using the software.

Supplemental capability videos are acceptable but should not be used as a substitute for live demonstrations of working software and live presentation of the demonstration topics.

Quick reference guides or other instructional handouts on the operation of sample software may be provided to the Government attendees.

3.3.2. Demonstration Topics. Vendors shall also address the topics listed below in their demonstrations.

3.3.2.1. Technical Solution Overview. At a minimum, the vendor shall address the following:

System Architecture: Describe the overall architecture, scalability and data flow

Customization and Configuration: Show how the solution can be tailored (UI configurations, workflows, business rules/logic)

Security and Compliance: Demonstrate data validation, sanitization and anonymization of data (if applicable). Show proof of compliance standards, data encryption at rest and in motion.

Identity, Access and Authentication Management: Show support for DoD approved identify federation (CAC/PIV, PKI, SAML 2.0, OIDC) if applicable

Support and Maintenance – vendor provided support (tiers, hours, escalation paths)

3.3.2.2. Schedule. Vendor will present their program schedule, with a focus on how the schedule supports achieving the prioritized prototype at full scale as described in the SOO.

3.3.2.3. Agile Development Capabilities. Vendor will describe their capabilities, experience and approach to agile development capabilities to successfully develop and deploy the H2F Front End solution in prototype, full-scale deployment, and follow-on production phases, and provide an estimate.

Vendors must demonstrate a mature CI/CD pipeline that supports automated testing, secure deployment, and rapid iteration across all core H2F modules, including sleep, nutrition, and physical readiness. The solution should enable infrastructure-as-code and continuous compliance to ensure scalability, resilience, and alignment with DoD DevSecOps standards.

3.3.2.4. Proposed Cost Share (Optional). Vendors shall discuss the costs of the prototype project to be paid out of funds provided by the vendor (to include team member contributions if applicable) and any relevant rationale for the cost share. Note: Cost share is generally considered to include forward-looking costs directly associated with the prototype project under consideration and does not include prior investments.

3.4 STEP 3 - Request for Prototype Proposals, Alpha Negotiations and OT Award(s)

Following Government evaluation of solution demonstrations, vendors selected for potential awards will be provided with a Request for Prototype Proposals (RPP) and invited to submit formal technical and cost proposals and to enter into alpha negotiations for OTA terms and conditions.

As part of the request for prototype proposals, vendors will be provided with the latest version of the H2FMS SOO as well as other Government-generated documents such as DD1423s (Deliverables Requirements List), Draft Agreement Language, Pricing Template (Excel file) and/or similar documents, and asked to provide detailed proposals in several volumes addressing the following general categories (subject to change):

1. Technical Volume

a. Detailed Technical Approach

b. Vendor-Generated Statement of Work to address all objectives in the Government-provided SOO

c. Technical Basis of Estimate

d. Integrated Master Schedule (IMS)

e. Detailed Data Rights Assertions Table (DRAT)

2. Past Performance Information (Government and/or Commercial Experience Examples)

3. Price Volume

a. Completed Excel Template

b. Completed Price Narrative Volume that includes any necessary supporting price data to assist the Government in establishing pricing to be fair and reasonable

The Government reserves the right to limit the number of vendors invited to submit a proposal. The RPP will provide further details regarding the proposal submission requirements.

The Government anticipates making multiple OT awards for the H2FMS prototype project. The number of awards will be dependent on available funding, to include proposed vendor cost share. The Government anticipates funding a base award for Phase 1 of the prototype project, with options for additional phases to be exercised at the Government’s sole discretion in the future. The Government’s intent is to carry multiple vendors across Phase 1 detailed in the SOO; however, the Government reserves the right to down select at any point and for any reason at the Government’s sole discretion.

SECTION 4 – EVALUATION APPROACH

4.1 Phase 1 White Papers – Basis of Evaluation

The Government will evaluate the white paper solutions against the below stated criteria:

• Relevance of the WP in addressing the USG’s needs.

• Technical merit and feasibility of the solution to address USG’s needs.

• Vendor’s approach is unique and/or innovative.

• Affordability of submitted ROM Cost/Price

Solutions submitted in response to this CFS will be evaluated based on merit of the solution against the prototype project requirements, not against other solutions submitted in response to this CFS.

When a vendor is not invited to demonstrations at the end of Step 1 or not invited to submit a prototype proposal after Step 2, the Government will notify the vendor with a non-selection letter. The non-selection letter will give a summary of why the Government did not choose the solution. The Government will provide general feedback summarizing the rationale that led to the non-selection decision, however, generally will not provide significant feedback beyond the non-selection letter.

If a vendor’s submitted white paper is of interest to the Government but a demonstration is not required and a Request for Prototype Proposals may still be requested from that vendor, the Government will notify the vendor of this possibility with a notification letter.

The Army expects that it may receive more solutions than has the resources to award. All submissions will be fairly considered; however, only a select few may be invited to provide a demonstration or submit a proposal. The Government reserves the right to limit the number of companies invited to provide a demonstration or submit a proposal. As such, a company’s solution may be evaluated to be of merit but not invited to provide a demonstration or submit a proposal. Solutions that are chosen for demonstrations or RPP will be notified in writing as soon as practicable.

Upon completion of Phase 1 White Paper evaluations, the Government will notify the Company that:

a. The proposed solution has been selected for possible agreement and is invited to present a solutions demonstration with potential to submit a full prototype proposal; or

b. The proposed solution has been selected for possible agreement, a demonstration is not required at present, and the Government may subsequently request the vendor to submit a full prototype proposal; or

c. The proposed solution is not of interest to the Government; or

d. The proposed solution is of interest, but not eligible for a request for prototype proposal due to the availability of Government resources.

If the proposed solution is of interest, but not eligible for a proposal due to availability of Government resources, the Company may be contacted with a request to respond to a Request for Prototype Proposal within 120 calendar days from the notification of non-selection. If the Government does not send an RPP to the Company within 120 calendar days, the Company will no longer be eligible for an award.

4.2 Phase 2 Solutions Demonstrations and Prototype Proposals – General Basis of Evaluation

The RPP will further refine the basis of evaluation, which will generally adhere to the below guidelines.

All Phase 2 vendor submissions, including all Demonstration content and Prototype Proposal Volumes will be evaluated by Government subject matter experts using, but not limited to, the following criteria:

a. Technical merit of the demonstrated solution and proposal with an emphasis on cybersecurity compliance, feasibility, achievability, and the extent to which the proposal represents an innovative technical solution that provides significant improvements over current capabilities will be considered.

b. Realism and/or adequacy of the proposal performance schedule.

Technical merit and schedule are anticipated to be the primary and most important factors and are equally important.

The final cost/price proposal must be determined to be fair and reasonable and affordable for a vendor’s proposal to be considered eligible for award.

SECTION 5 – AWARDS

5.1 General Guidelines

Upon favorable review and receipt of available funds, the Government may choose to make award(s), Awards made as a result of this CFS will be made using prototype project Other Transaction agreements.

The Agreements Officer will negotiate directly with the vendor on the terms and conditions of the OT agreement, including payments, and will execute the OT agreement on behalf of the Government. Only an Agreements Officer has the authority to enter into or modify a binding agreement on behalf of the Government.

Companies must register in the System for Award Management (SAM.gov) and have a Unique Entity Identification (UEI) to receive an award. Companies must commence SAM registration upon receipt of an RPP and must maintain registration in SAM throughout Phase 2 of the CFS process, throughout the period of performance of the prototype project and during any subsequent follow-on production transaction or contract.

Companies must also register in the prescribed Government invoicing system (e.g. Procurement Integrated Enterprise Environment (PIEE), Wide Area Work Flow (WAWF), etc.). The Agreements Officer can assist those Companies from whom a full proposal is requested.

The Company must be determined to be responsible by the Agreements Officer and must not be suspended or debarred from award by the Federal Government nor be prohibited by Presidential Executive Order and/or law from receiving an award.

Receipt of a RPP does not guarantee that a Company will receive an award. The Government reserves the right, at any point prior to award of an OT agreement, to cancel the RPP or to forgo award to any vendor at the Government’s sole discretion.

5.2 Comptroller General Access to Information

In projects that provide for payments in a total amount exceeding $5,000,000, the Agreement will include a mandatory clause that provides the Comptroller General with the ability to examine the records of any party to the agreement or any entity that participates in the performance of the agreement as required by 10 U.S.C. § 4022.

5.3 Procurement Integrity Act (PIA)

As required by 10 U.S.C. § 4022(h), all OT agreements awarded under this CFS shall be treated as Federal Agency procurements for purpose of 41 U.S.C. Chapter 21. Accordingly, the CFS competitive solicitation process and awards made thereof must adhere to the ethical standards required by the PIA.

SECTION 6 – ITERATIVE PROTOTYPING

6.1 Iterative Prototyping Process

Prototype OTs awarded against this CFS will allow for an iterative prototyping process.

An iterative prototyping process will allow the Government to modify, by mutual agreement, the work in a prototype project to allow the adaptation and modification of the technology being prototyped to meet additional unique and discrete purposes/mission sets or new technologies or processes discovered during the prototype process. These additional unique and discrete purposes/mission sets can be generated by the original Government customer or originate with other organizations within the Federal Government.

6.2 Future Requests for White Papers and Vendor On-ramps

In recognition of the rapid rate of technology innovation among Industry, the Government may periodically issue follow-on requests for white papers to assess the need for additional H2FMS OT awards at both the prime and component level to keep pace with industry’s advancements. The Government may update the procedures and evaluation criteria as required. New requests for white papers will be posted to SAM.gov. Vendors who may be able to provide future support for subtasks/subsystems/subcomponents or extensibility/integration with new modules or devices associated with H2FMS should continue to monitor SAM.gov for future opportunities to support the H2FMS solution.

SECTION 7 – FOLLOW-ON PRODUCTION

Upon successful completion of a prototype project under the OT, the Government and Company may negotiate follow-on production contract(s) or agreement(s) without further competition. Any concept, technology, or solution successfully proven through a Prototype OT can be transitioned to production.

Prototype OTs awarded as a result of this CFS will include language providing for the potential award of follow-on production contract(s) or agreement(s) as authorized under 10 U.S.C. § 4022(f).

Individual Prototype OTs will explicitly identify follow-on production contract(s) or agreement(s) as a potential outcome of a successful prototyping effort.

SECTION 8 - SUCCESSFUL COMPLETION

A transaction for a prototype project is deemed successfully completed upon the written determination of the appropriate approving official (program manager and Agreement Officer) for the matter in question that efforts conducted under a Prototype OT: (1) met the key technical goals of a project; (2) satisfied success metrics incorporated into the Prototype OT; or (3) accomplished a particularly favorable or unexpected result that justifies the transition to production. Furthermore, successful completion can occur prior to the conclusion of a prototype project to allow the Government to transition any aspect of the prototype project determined to provide utility into production while other aspects of the prototype project have yet to be completed. Any Prototype OT shall contain a provision that sets forth the conditions under which that prototype agreement must be successfully completed.

SECTION 9 – NON-GOVERNMENT ADVISORS

Non-Government advisors are anticipated to be used in Phase 1 and 2 evaluations and during proposal development and alpha negotiations. Non-Government advisors will have signed non-disclosure agreements (NDAs) with the Government. Submission of an offer under this CFS will constitute a grant of authority by the submitting Company to the Government to allow the use of non-Government advisors to participate in evaluations of all phases of the CFS process. Non-Government advisors from the following companies are anticipated to be utilized:

DCS Corporation LMI Consulting, Inc.

If additional non-Governmental advisors are used during evaluations, advance notice will be provided by the Government as applicable.

The Government understands that information provided in response to this CFS is presented in confidence and may contain trade secret or commercial or financial information, and it agrees to protect such information from unauthorized disclosure to the maximum extent permitted or required by Law, to include:

a. 18 U.S.C. 1905 (Trade Secrets Act);

b. 18 U.S.C. 1831 et seq. (Economic Espionage Act);

c. 5 U.S.C. 552(b)(4) (Freedom of Information Act);

d. Executive Order 12600 (Pre-disclosure Notification Procedures for Confidential Commercial Information); and,

e. Any other statute, regulation, or requirement applicable to Government employees.

ACC/Army policy is to treat all submissions as confidential information, and to disclose their contents only for the purpose of evaluation. Restrictive notices notwithstanding, during the evaluation process, submissions may be handled by support contractors for administrative purposes and/or to assist with technical evaluation.

Submissions will not be returned. The original copy of each submission received will be retained by ACC with all other non-required copies destroyed.

SECTION 10 - ADDITIONAL INFORMATION

10.1 Security Clearances

If awarded an OT under the procedures of this CFS, the vendor will be responsible for providing personnel with appropriate security clearances to ensure compliance with Government security regulations. The vendor shall fully cooperate on all security checks and investigations by furnishing requested information to verify the vendor employee's eligibility for any required clearance.

The vendor's proposed solution (e.g., data, integration with supporting DoD Infrastructure, architecture) will determine the personnel security clearance and/or facility clearance requirements for the prototype effort. The Government will provide additional details regarding the personnel security clearance and/or facility clearance requirements in the provided requirements documents and/or RPP.

10.2 Data Storage

To protect against seizure and improper use by non-United States (U.S.) persons and government entities, all data stored and processed by/for the DoD must reside in a facility under the exclusive legal jurisdiction of the U.S. If awarded an OT under the procedures of this CFS, the vendor will be required to maintain all government data that is not physically located on DoD premises within the 50 States, the District of Columbia, and outlying areas of the U.S., unless otherwise authorized by the responsible Government, as described in DoD Instruction (DoDI) 8510.01, Risk Management Framework for DoD Systems, and the DoD Cloud Computing Security Requirements Guide.

During the performance of an OT, if Government data is co-located with the non-Government data, the vendor will be required to isolate the Government data into an environment where it may be reviewed, scanned, or forensically evaluated in a secure space with access limited to authorized Government personnel identified by the Agreements Officer, and without the Company's involvement. The vendor will be required to record all physical access to the cloud storage facilities and all logical access to the Government data. This may include the entrant's name, role, purpose, account identification, entry and exit time. The vendor will be required to provide such records to the Agreements Officer or designee in accordance with the agreement or upon request to comply with federal authorities.

10.3. Company Incurred Evaluation Costs

The Government will not reimburse interested vendors for any costs incurred while participating in Phases 1 and 2 of the CFS process. Additionally, the Government will not consider the costs associated with participating in Phases 1 and 2 of this CFS as allowable charges and such costs should not be included within the ROM or any pricing information.

10.4. Export Controls

Research findings and technology developments arising from a resulting prototype OT may constitute a significant enhancement to the national defense and to the economic vitality of the United States. As such, in the conduct of all work related to this effort, the recipient will be required to comply strictly with the Arms Export Control Act, 22 U.S.C. § 2751-2794, including the International Traffic in Arms Regulation (ITAR), 22 C.F.R. § 120 et seq.; the Export Administration Act, 50 U.S.C. app. § 2401-2420; the

National Industrial Security Program Operating Manual, 32 CFR § 117; and the Department of Commerce Export Regulation, 15 CFR § 730-774.

10.5 Associate Agreements

Associate Contractor Agreements (ACA) or other similar agreements may be a necessary augmentation to individual agreements to accomplish joint participation in the success of the Government’s requirements.

The intent of the ACAs should be to share information between contractors, data and/or technical expertise to ensure cooperation and success to the greatest degree to meet the terms of an agreement.

Contractors will not be relieved of any agreement terms and conditions as a result of a disagreement under an ACA, nor is the Government liable for improper disclosure of any proprietary data as a result of an ACA or similar agreements. The Government reserves the right to specify subcontracts, service providers and/or license agreements in requirements.

10.6 Organizational Conflicts of Interest (OCI)

An organizational conflict of interest means that because of other activities or relationships with other persons, a person/company/vendor is unable or potentially unable to render impartial assistance or advice to the Government, or the person's/company’s/vendor’s objectivity in performing the contract work is or might be otherwise impaired or has an unfair competitive advantage. The Government seeks to acquire unbiased advice and/or goods and services from offerors/contractors/vendors that are free from, or have mitigated, Organizational Conflicts of Interest, relating to Agreements under this CFS.

To prevent an OCI issue relating to mission requirements, contractor’s performing on this prototype project agree that the Contractor’s future procurement with the Government may be restricted if the Offeror/contractor/vendor and the Government are unable to avoid, neutralize, or mitigate actual or potential OCI before an OT agreement award.

The Government will not automatically exclude an offeror due to an actual or potential OCI. Agreements Officers are committed to working with potential contractors to eliminate or mitigate actual and potential OCI situations, without detriment to the integrity of the competitive process, mission, or the legitimate business interests of the community.

If the Offeror or contractor is aware, or should have been aware, of an OCI before award of an agreement and does not fully disclose that conflict to the Agreements Officer, the Government may terminate the Contractor for default.

The Offeror or contractor, by submitting an offer and/or signing the agreement, warrants that it is not now aware of any actual or potential OCI relating to any agreement awarded under this prototype project.

The Contractor shall have an ongoing obligation to make “a prompt and full disclosure” to the cognizant Agreements Officer any OCI that arises during the performance of the Agreement. OCIs that arise before award shall be disclosed to the Army Contracting Command (ACC) POCs listed in Section 12 below.

SECTION 11 – H2FMS DOCUMENT PACKAGE.

The H2FMS Statement of Objectives (SOO) contains Controlled Unclassified Information (CUI) technical information and will be sent to vendors upon request via DoD SAFE.

Vendors shall send an email request with the subject line “Request for H2FMS CUI Documents” to the administrative points of contacts listed below:

• MAJ Michael A. Ashburn at michael.a.ashburn8.mil@army.mil, and

• Ms. Diamond J. Bush at diamond.j.bush.ctr@army.mil.

The email must include a completed H2FMS CUI Document Request Form and the vendor’s CAGE code.

The H2FMS SOO will not be made available after the Request for White Papers deadline has passed. See the CFS announcement on SAM.gov for the latest white paper due date and time.

PART 12 – GOVERNMENT POINTS OF CONTACT

Questions regarding this opportunity should be sent via email to the following POCs by the dates specified in the SAM.gov announcement associated with this CFS:

• Mr. Dennis A. Beauclair Jr. dennis.a.beauclair3.civ@army.mil,

• Mr. Alexander S. Obriwin alexander.s.obriwin.civ@army.mil, and