DRAFT_52.212-1&2_DeploymentSolutions_2026.03.03.pdf

Draft HT003826RE001

CUI//PROCURE

52.212-1 INSTRUCTIONS TO OFFERORS--COMMERCIAL ITEMS (FEB 2026) (TAILORED) 1

1.0 Solicitation Information 3

This solicitation seeks full and open competitive offers. The North American Industry Classification System 4 (NAICS) code is delineated on the SF-1449 cover sheet (including NAICS and size standards). 5 The Government intends to award multiple award contracts to each and all qualifying offerors in response to the 7 Program Executive Office – Defense Healthcare Management System (PEO DHMS) Deployment Solutions 8 solicitation in accordance with 10 U.S.C. 3206(c) implemented by RFO 15.104(b)(1)(ii). Therefore, Price will not be 9 an evaluation factor for this solicitation. 10

2.0 General Instructions 12

Points of Contact (POC): Below are the only points of contact for this solicitation. All questions or concerns 14 shall be submitted to the Contracting Officer and Contract Specialist, using the submission instructions below. All 15 proposal submissions shall be submitted using the instructions in Section 2.2 below. Service of protest to the 16 Agency shall be submitted to the e-mail addresses below. 17

Table 1: Points of Contact 19 Name Title Email Ms. Joyce Elaine Pace-Reed Procuring Contracting Officer joyce.e.pace-reed.civ@health.mil Ms. Samantha Deluca Contract Specialist hailey.s.deluca.civ@health.mil

2.1. Instructions to Offerors 21

2.1.1 General Instructions 23

a. This section provides general guidance for preparing proposals as well as specific instructions on the 25 format and content of the proposal. The offeror’s proposal must include all data and information 26 requested and must be submitted in accordance with these instructions. Non-conformance with these 27 instructions and/or submittal of an incomplete package may result in an offer being considered 28 unacceptable and the proposal may not be evaluated. 29

b. Alternate proposals will not be accepted. If an Offeror (1) fails or refuses to assent to any of the terms and 30 conditions of this request for proposal (RFP), (2) proposes additional terms or conditions, (3) conditions its 31 proposal with assumptions or (4) fails to submit any of the information required by this solicitation, then 32 the Government may consider the offer to be unacceptable and therefore ineligible for contract award. 33

c. The proposal shall be clear, concise, and shall include sufficient detail for effective evaluation and for 34 substantiating the validity of stated claims. Offerors shall assume the Government has no prior knowledge 35 of its facilities and experience and will base its evaluation on the information presented in the offeror’s 36 proposal. 37

d. Elaborate brochures or documentation, binding, detailed artwork, or other embellishments are unnecessary 38 and are not desired. Do not include resumes. 39

e. Proposals must not include classified information. 40

f. All the requirements in the RFP are mandatory. Offerors’ proposal submission represents that the firm will 41 perform all the requirements specified in the solicitation. 42

g. The Government may consider any failure to comply with these instructions to be indicative of what could 43 be expected from an offeror during contract performance and may consider it a weakness of the proposal in 44 the appropriate factors. Statements such as “will comply,” “noted and understood,” “in accordance with 45 best/industry practices/standards,” etc., without supporting narrative are not acceptable. Cursory responses 46 or responses that merely reiterate or paraphrase the solicitation language, or other information 47 provided by the Government, will not be considered to satisfy the requirements of the solicitation. 48

Note: Throughout the RFP documents, unless otherwise specified, reference to days will mean calendar days, not 50 business days. In accordance with RFO 4.309(a)(1) the Government will retain its copy of all unsuccessful 51 proposals. 52

2.1.2 System for Award Management (SAM). 54

Offerors will not be eligible to receive a contract award unless they are registered in SAM at the time of proposal 55 submission and maintain an active record in SAM. 56

2.1.2.1 Contractor Teaming Arrangements & Joint Ventures 58

If an offeror is proposing under RFO Companion (FC) 9.000, where there is a joint venture or partnership, the 59 combined entity shall be registered in SAM, and the SF-1449 must reflect the combined entity as the Prime. 60 Offerors shall provide Teaming Agreements in accordance with Volume IV, Section 5. 62

2.2 Proposal Submission Instructions for Bidscale 64

Proposals must be submitted electronically via a secure online submission portal by [insert due date and time]. 65 Bidscale aids the Government in evaluating acquisitions and reduces submission rounds through a structured 66 submission process for proposal materials. The submission portal is a tool used solely to receive and evaluate 67 proposals for this solicitation. Only Government signed documents, including evaluation reports and contracts are 68 considered as the official record for contractual purposes. 69

1. Digital Submission Portal Access: 70 Offerors wishing to submit a proposal must first request a user account to access the digital submission portal. To 71 request an account, please send an email to customersuccess@bidscale.com. The email must include the 72 following information: 73

a. Subject Line: Submission Portal Account Creation 74

b. First Name 75

c. Last Name 76

d. Email Address 77

e. Company Name 78

f. Solicitation Name: PEO DHMS Deployment Solutions 79

Please allow at least 72 hours for account creation before the submission deadline. Once the account is created, 80 offerors will receive a confirmation email with login instructions. Only one account will be created for each offeror. 81

2. Upon successful account creation, proposals can be submitted through the link sent to the requesting 82 user: 83

a. Supported web browsers include Chrome, Edge, and Firefox. 84

b. The proposals must follow the format and guidelines outlined in 52.212-1 of the solicitation 85 document. 86

c. All required documents and attachments must be included. Submissions not fully uploaded or 87 submitted will not be considered. 88

d. You are able to resubmit your proposal documents up until the above deadline. 89

3. Confirm receipt of a confirmation email for your submission 90 Upon submission, you will receive a confirmation email from Bidscale acknowledging receipt of your proposal. 91 Bidscale is only authorized in a limited capacity to issue access to the submission portal and provide basic technical 92 support with its utilization. If a confirmation email was not received or technical issues occur with the submission 93 portal, contact Bidscale for assistance at customersuccess@bidscale.com and copy the Contracting Officer 94 and Contract Specialist at dha.ncr.co.mbx.cd-dhms-contracting@health.mil. 95

4. Evaluation: 96 The Government reserves the right to utilize artificial intelligence (AI) tools to collect, summarize, and compile 97 proposal and/or evaluation information during the evaluation process. AI tools will be used solely as an 98 administrative aid. All evaluation judgments and source selection decisions will be made by Government personnel. 99

5. Disclaimer: 100 Proprietary information submitted in response to this solicitation will be protected from unauthorized disclosure as 101 required by Subsection 27 of the Office of Procurement Policy Act as amended (41 U.S.C.423) (hereinafter referred 102 to as “the Act”) as implemented in the FAR. These companies are bound contractually by Organizational Conflict of 103 mailto:customersuccess@bidscale.com mailto:customersuccess@bidscale.com mailto:dha.ncr.co.mbx.cd-dhms-contracting@health.mil

Interest and disclosure clauses with respect to proprietary information. Contractor personnel will take all necessary 104 action to preclude unauthorized use or disclosure of an offeror's proprietary data. 105 The exclusive responsibility for source selection will reside with the Government. 107 The procuring Contracting Officer is the sole POC to offerors any proposal related questions. Bidscale is not 109 authorized to address any issues/questions related to contractor proposal submissions. Offerors are encouraged to 110 review all instructions carefully and ensure full compliance with all requests for proposal requirements to avoid any 111 disqualification. 112

2.3 Communications and Solicitation Question Instructions 114 Communications between the Government and offerors will be controlled by the Contracting Officer and 115 Contract Specialist. Offerors must submit all written proposal information via Bidscale Portal. 116 Solicitation questions must be submitted to the Contract Specialist attention via email dha.ncr.co.mbx.cd-118 dhms-contracting@health.mil. Solicitation questions must be submitted no later than [insert date and time]. 119 Questions provided using different means will not be considered. The Government will provide a response to the 120 questions via SAM.gov. Responses may or may not require an amendment. Offerors are responsible to monitor 121 SAM.gov for the most recent information for this solicitation. 122

2.3.1 Discussions 124

The Government will provide awards to all technically acceptable proposals. The Government intends to award 125 without discussions or establishment of a competitive range; however, the Government reserves the right to hold 126 discussions. If, during the evaluation period, it is determined to be in the best interest of the Government to hold 127 discussions, offeror responses to Evaluation Notices (ENs) and the Final Proposal Revision (FPR) will be 128 considered in making the source selection decision. 129 As the Government does not intend to hold discussions, offerors are advised to submit initial proposals that are 131 well defined and clearly acceptable without additional information or substitute pages. Further, initial proposals 132 should contain the offeror’s best terms rather than relying on the potential for future negotiations. 133

2.3.2 Clarifications 135

Offerors may be given the opportunity to clarify certain aspects of the proposal or resolve minor or clerical errors. 136 Such clarifications shall not be considered discussions. Offerors will not be given an opportunity to respond to 137 any identified weaknesses or deficiencies or revise their proposals. 138

2.4 Amendments to Solicitation 140

If this RFP is amended, all terms and conditions that are not amended remain unchanged. Offerors shall 141 acknowledge receipt of any amendment to this request by the day and time specified in the amendment(s). 142

2.5 Period of Acceptance of Offers 144

The offeror agrees to hold its proposal firm for 180 calendar days from the date specified for receipt of offers. 145

2.6 Discrepancies 147

If an offeror believes that the requirements in these instructions contain an error, omission, or are otherwise 148 unsound, the offeror shall immediately notify the Contracting Officer in writing via e-mail with supporting rationale 149 as well as the remedies the offeror is asking the Contracting Officer to consider as related to the omission or error. 150

3.0 Proposal Content 152

The purpose of these instructions is to prescribe the format of proposals and describe the approach for the 153 development and presentation of proposal information. Proposals shall be submitted in accordance with these 154 instructions or will be considered non-compliant. 155

3.1 Page Limitations 157

All proposals must comply with the page limitations identified in the applicable tables below. Page limitations shall 158 be treated as maximums. If exceeded, the excess pages will not be read or considered in the evaluation of the 159 proposal. Title pages, cover pages, tables of contents, tab indexing, glossaries, and lists of tables and figures are not 160 included in page limitations. Legible tables, charts, graphs and figures may be used to depict organizations, systems 161 and layout, implementation schedules, plans, etc., when described under specific factors below. 162

3.2 Page Size and Format for Written Proposal Submission 164

A page is defined as one 8.5” x 11” electronic page with 1” margins and no smaller than a 10-point font size. The 165 font shall be Times New Roman. NOTE: The font size limitation applies to all narrative elements, graphics, art, 166 figures, imported charts, charts, and any other graphical representation that includes text (font type can be varied 167 depending on the medium). Pages shall be numbered sequentially by volume. Pages shall include line numbering to 168 support review. 169

3.3 Title Page (not included in the page count) 171

Each volume must include a title page. The title pages must show: 172

• Solicitation Number, and 173

• Name, address, telephone numbers and e-mail address of the offeror 174

3.4 Cross-Referencing 176

The proposal volumes shall be written on a stand-alone basis so that its contents may be evaluated without cross-177 referencing to another volume. Information required for proposal evaluation which is not found in its designated 178 volume will be assumed to have been omitted from the proposal. 179

3.5 Indexing 181

Each volume shall contain a detailed Table of Contents to delineate the subparagraphs within that volume. Tab 182 indexing shall be used to identify sections and will not count against page limitations IAW paragraph 3.1. 183

3.6 Glossary of Abbreviations and Acronyms 185

Each volume shall contain a glossary of all abbreviations and acronyms used, with an explanation for each. As 186 stated above in paragraph 3.1, glossaries do not count against the page limitations for their respective volumes. 187

3.7 Compliant 189

Documents submitted in response to this solicitation must be fully compliant to and consistent with the terms and 190 conditions of the solicitation or may result in being rejected as noncompliant and not being evaluated. 191

4.0 Proposal Instructions 193

Table 2 provides a list of each volume, documents, file type, maximum page limits, and file formats. 194

Table 2: Proposal Volumes 196

ITEM ELECTRONIC FILE NAME FILE

TYPE

PAGE

LIMITS

Volume I: Factor 1 - Challenge Scenario 1a OfferorName_Factor1_ChallengeScenario1a .pdf 8 Volume I: Factor 1 - Challenge Scenario 1b OfferorName_Factor1_ChallengeScenario1b .pdf 8

Volume II: Factor 2 – Small Business Participation Small Business Participation Narrative OfferorName_Factor2_SmBusNar .pdf 2 Small Business Participation Attachment OfferorName_Factor2_SmBusNarAttachment .xls(x) 1

Volume III: Factor 3 – Supply Chain Risk Supply Chain Risk Management Plan OfferorName_Factor3_SupplyChain .pdf 3

Volume IV: Contract Documents

Section 1: Cover Letter OfferorName_CoverLetter .pdf 1 Section 2: Organizational Conflict of Interest (OCI) Declaration and Disclosure OfferorName_OCI .pdf UNL

Section 3: Support Contractor Proposal Access Consent Form OfferorName_AccessConsentForm .pdf UNL

Section 4: Small Business Subcontracting Plan OfferorName_SmallBusSubPlan .pdf UNL Section 5: Teaming Agreements OfferorName_TeamingAgreements .pdf UNL

NOTE: Volumes shall consist of the information specified for each evaluation factor listed below. All documents 198 shall be searchable and capable of using highlights and comment boxes. No pricing information shall be included 199 in Volumes I, II, III, and IV. 200

FACTOR 1: CHALLENGE SCENARIO 202

Offerors shall provide a (1) proposed Deployment Approach (A003) (Volume 1: Factor 1 – Challenge Scenario 1a) 203 as well as a (2) proposed Deployment Approach (A003) (Volume 1: Factor 1 – Challenge Scenario 1b) based on 204 both of the following scenarios. 205 The Program Executive Office Defense Healthcare Management Systems (PEO DHMS) is modernizing its global 207 healthcare capabilities, which includes the multi-faceted deployment of DHMS products (Federal Electronic Health 208 Record (EHR) and Operational Medicine (OpMed)). The objective is to create a secure, seamless, and interoperable 209 health information ecosystem that supports warfighters from the point of injury in austere, forward-deployed 210 locations to definitive care. 211 Offerors shall propose an innovative and scalable deployment plan addressing two interconnected lines of effort as 213 outlined below. The proposed approach shall address hardware and/or component installation and configuration 214 across various networks, continuous patient data access, and comprehensive user training tailored to the operational 215 environment and a diverse user audience. Additionally, the plan shall incorporate proactive risk mitigation strategies 216 to address deployment complexities and ensure mission success. 217 1a) Federal EHR product modernization and deployment: This effort focuses on the full implementation of the 219 Federal EHR at established, high-capacity treatment facilities. 220

Scope: 222

• One large accredited Outside Continental U.S. (OCONUS) medical center (250 beds), including two 223 community hospitals (125 beds) and five associated out-patient clinics spread across multiple time zones 224 with approximately 5,000 total users that includes foreign national employees and 50,000 beneficiaries. 225

• Services: Full-spectrum healthcare services are in scope, including inpatient, outpatient, acute, ambulatory, 226 specialty, and dental care. This also includes all associated Revenue Cycle services such as billing, patient 227 accounting, and referral management. 228

• Technical Environment: The solution must be integrated with a complex array of hardware, including 229 medical devices and IT systems that require real-time, secure data exchange. 230

1b) OpMed products’ modernization and deployment: This effort delivers mobile and interoperable OpMed 232 solutions to medical forces in deployed and tactical environments in both the Continental U.S. (CONUS) and 233 OCONUS. This includes theater hospitals, hospital ships, forward resuscitative sites, and submarines. These scalable 234 deployments can occur concurrently across multiple sites, countries, or theaters, in remote or austere environments 235 with each location receiving one or more products tailored to mission requirements. The deployment includes the 236 OpMed product suite: Battlefield Assisted Trauma Distributed Observation Kit-Joint (BATDOK-J), Operational 237 Medicine Care Delivery Platform (OpMed CDP), Theater Blood-Mobile (TBLD-M), and Medical Hub (MedHub). 238

Scope: 239

• Deploy globally to over five sites/units simultaneously across forward-deployed locations managed by 240 multiple Services in EUCOM and INDOPACOM (Role 1-3) with uncertain schedule and complex 241 infrastructure. This includes deployments from Naval vessels and field hospitals to forward resuscitative 242 and enroute care teams 243

• Services & Interoperability: Full-spectrum healthcare services are in scope, including ambulatory 244 care, emergency trauma, surgical stabilization, enroute care, behavioral health, forward resuscitative, 245 ancillary services (pharmacy, lab, imaging), and blood inventory and management. A critical requirement is 246 ensuring seamless data transmission through all roles of care and aggregating medical data for Command 247 and Control Situational Awareness (C2SA) reporting. 248

• Technical Environment: The plan will address integration with complex Service-specific hardware and 249 diverse Service networks, ensuring system security even in disconnected, intermittent, and low-bandwidth 250 (DIL) environments. The plan should address options for low-to-no touch deployments, where the products 251 will be remotely deployed and/or trained to the field. 252

FACTOR 2: SMALL BUSINESS PARTICIPATION 254

Offerors shall submit an approach (Volume II) that the Government will evaluate for compliance with the small 255 business utilization goals provided below. Offerors may claim small business credit for subcontractors to the third 256 tier. 257

(1) The following reflects minimum Subcontracting Goals for this procurement and shall be used in the 259 development of the Offeror’s submission for Factor 2: 260

i. Total Small Business - 30% 261

ii. Small Business – 12% 262

iii. HUBZone Small Business - 3% 263

iv. Service-Disabled Veteran-Owned Small Business - 5% 264

v. Small Disadvantaged Business - 5% 265

vi. Women-Owned Small Business - 5% 266

The above minimum goals are provided as a baseline for small business participation. The Offeror, 267 regardless of business size, shall propose small business participation for this specific requirement. 268

(2) Offerors shall provide a table identifying all proposed subcontractors, up to the third tier, individually by 269 name with addresses, business type (Other Than Small Business, Small Business, Small Disadvantaged 270 Business, Women-Owned Small Business, Veteran-Owned Small Business, Service-Disabled Veteran-271 Owned Small Business, and HUBZone Small Business) as determined by the SBA size standard for the 272 specific work being subcontracted; the principal service/supply being provided by the subcontractor; 273 NAICS Code; and the complexity of the service/product provided (defined as the depth of capabilities and 274 essential, non-commoditized services provided). The table shall describe the extent of small business 275 participation for this procurement with percentage and dollar amounts for specific small business 276 categories. 277

(3) Offerors shall include evidence, such as binding letters of commitment subject only to contract award, of 278 the Offeror’s ability to meet the small business participation goals. 279

(4) Offerors shall include an approach to achieve these participation goals throughout the life of the contract. 280

(5) Offerors shall provide evidence of meeting small business goals on prior contracts. If, historically, the 281

Offeror has not met/exceeded small business goals, an explanation shall be provided on what actions were 282 taken or will be taken to meet the goals on Deployment Solutions. 283

FACTOR 3: SUPPLY CHAIN RISK 285

In accordance with DFARS RFO Class Deviation 212.203, offerors shall submit a Supply Chain Risk Management 286 Plan (Volume III). The plan must describe processes for identifying, assessing, and mitigating supply chain risks 287 associated with hardware, software, and firmware, and confirm compliance with applicable DFARS 252.204-7017 288 and 252.204-7018 and FAR 52.204-8 Deviation, 52.204-26 52.240-90, and 52.240-91 requirements. 289

VOLUME IV: CONTRACT DOCUMENTS 291

(1) Cover Letter 292

The Offeror’s proposal shall include a cover letter on the Offeror’s letterhead stationery and signed by an executive 293 of the company who possesses authority to bind the Offeror contractually. The cover letter shall acknowledge 294 receipt of all amendments (if any are issued) to the RFP. The submittal letter shall identify all enclosures being 295 transmitted as part of the response to the RFP. The letter shall reference the RFP number and acknowledge that the 296 Offeror is submitting an offer in response to the RFP. It shall state: (1) Commercial and Government Entity (CAGE) 297 number, (2) Unique Entity Identifier (UEI), (3) Taxpayer Identification Number (TIN), and (4) a statement that the 298 proposal is valid 180 days past the estimated award date. 299

(2) Organizational Conflict of Interest (OCI) Declaration and Disclosure 301 Offerors shall complete and submit Attachment 16, OCI Declaration and Disclosure, Notice of Organizational 302 Conflict of Interest. In addition, the Offeror shall provide a complete list of all team members (including all 303 subcontractors at all tiers) so the Government may perform an independent OCI assessment. In accordance with 304 RFO 9.504, the Contracting Officer may withhold award from any Offeror when a conflict of interest is determined 305 to exist that cannot be avoided or mitigated. 306

(3) Support Contractor Proposal Access Consent 308 Contractor support personnel from the below listed companies under existing PEO DHMS contracts will be used for 309 administrative purposes only. This assistance will not include analyzing or evaluating proposals. 310

Table 3: Contractor Support Personnel - Administrative 312

Company POC Contact Information Unison Global (aka Bidscale)

Ben Ro Ben.Ro@unisonglobal.com

Unison Global (aka Bidscale)

Kelsey Fryling Kelsey.Fryling@unisonglobal.com

Proprietary information submitted in response to this solicitation will be protected from unauthorized disclosure as 314 required by Subsection 27 of the Office of Procurement Policy Act as amended (41 U.S.C. 423) (hereinafter referred 315 to as "the Act") as implemented in the FAR. Contractor Support Personnel are bound contractually by 316 Organizational Conflict of Interest and disclosure clauses with respect to proprietary information. Contractor 317 personnel will take all necessary action to preclude unauthorized use or disclosure of an Offeror's proprietary data. 318 Responses to this solicitation MUST clearly state permission is granted allowing the contractor support identified 320 above access to the contractor’s proposal. Subcontractors that provide proposal information separate from the Prime 321 contractor’s proposal submittal shall clearly state permission is granted allowing the contractor support identified 322 above access to the subcontractor’s proposal. The Offeror and its subcontractors may choose to execute a proposal 323 access agreement with these support contractors. Failure to clearly state permission is granted for access to the 324 contractor’s proposal may result in the offer being deemed unacceptable and therefore ineligible for contract award. 325 The exclusive responsibility for source selection will reside with the Government. 327

(4) Small Business Subcontracting Plan 329 Offerors (unless otherwise exempt due to being a small business concern or a company performing outside of any 330 State, territory, or possession of the United States, the District of Columbia, and the Commonwealth of Puerto Rico) 331 shall, in accordance with RFO 19.109 and FAR 52.219-9, submit a Small Business Subcontracting Plan, as part of 332 Volume III. The Small Business Subcontracting Plan will be approved and incorporated into any resultant contract 333 in accordance with RFO 19.109 and FAR 52.219-9. 334 If the Offeror is a participant in the Department of Defense/War (DoD/W) Comprehensive Subcontracting Test 336 Program specified in DFARS RFO Class Deviation 219.206-70, then the Offeror shall provide a copy of the 337 approved comprehensive plan and describe how small business participation on this contract will contribute to its 338 overall comprehensive subcontract goals. 339 Failure to deliver the documents specified above that allow for determination under RFO 9.104 will result in 341 rejection of the proposal. 342 Offerors shall submit a copy of any DCMA Subcontracting Compliance Rating letters, if applicable. 344 mailto:Ben.Ro@unisonglobal.com mailto:Kelsey.Fryling@unisonglobal.com

(5) Teaming Agreements 346 Offerors shall include all executed Deployment Solutions teaming agreements. If an Offeror is proposing under RFO 347 9.104-3(c)(2), where there is a joint venture or partnership, the Government would expect that the combined entity 348 be registered in SAM, and the contract document would reflect the combined entity as the Prime. 349 (End of Provision) 351

52.212-2 EVALUATION--COMMERCIAL ITEMS (FEB 2026) (TAILORED) 353

1.0 Basis for Contract Award 355

The Government intends to make an Indefinite Delivery, Indefinite Quantity (IDIQ) multiple award contract to each 356 and all qualifying offerors as defined in RFO 2.201 whose offer conforms to the solicitation requirements and is 357 determined to be a responsible offeror in accordance with RFO Part 9 – Contractor Qualifications. The Government 358 will evaluate each proposal in accordance with the evaluation criteria. A proposal will be considered “Technically 359 Acceptable” if it receives a rating of “Acceptable” in all evaluation factors below. A proposal that receives a rating 360 of “Unacceptable” in any factor will be deemed technically unacceptable and ineligible for award, except as 361 provided under Factor 1 (Challenge Scenario) with respect to the Challenge Scenarios 1a and 1b. For purposes of 362 Factor 1 (Challenge Scenario), an offeror will be rated Acceptable if it receives an Acceptable rating in either 363 Challenge Scenario 1a, Challenge Scenario 1b or both. Offerors that receive an Unacceptable rating in either 1a or 364 1b, yet receive an Acceptable rating in either 1a or 1b will remain eligible for award. 365 All awardees under this solicitation will be eligible to compete for any task order issued within the scope of this 367 resulting IDIQ contract. The Government does not intend to establish pools, channels, or scope-based limitations on 368 task order competition based on the Challenge Scenario evaluation results. 369 This source selection will be conducted in accordance with RFO Part 12, Acquisition of Commercial Items and RFO 371 Part 15, Contracting by Negotiation, as supplemented by the Defense Federal Acquisition Regulation Supplement 372 (DFARS). These regulations are available electronically at https://www.acquisition.gov/far-overhaul/far-part-373 deviation-guide. 374 Note that the Government will not award a contract to an offeror whose team has an unmitigated organizational 376 conflict of interest. Evaluation of an offeror’s proposal will be based on the information presented in the proposal. 377 Proposals which are unsubstantiated in terms of technical or schedule commitments, may be deemed to be reflective 378 of an inherent lack of technical competence, or indicative of a failure to comprehend the complexity and risks of the 379 proposed work and may be grounds for rejection of the proposal or may be considered a performance risk, impacting 380 the rating under the applicable Factor. 381 The Government will not award contract(s) to offerors that do not provide acceptable documents as required in 383 Volume III. Issues involving compliance or standards of responsibility may be resolved in clarifications with the 384 process outlined at 52.212-1 paragraph 2.3.2 and will not trigger the requirement for discussions with all offerors. If 385 the Government is unable to determine the offeror compliant in accordance with the solicitation, and responsible in 386 accordance with RFO Part 9 – Contractor Qualifications, as applicable, the offer will be rejected. 387

2.0 Evaluation Factors 389

The following evaluation factors will be used to evaluate each proposal. Award will be made to each and all 390 qualifying offerors whose proposals are determined to be Technically Acceptable and whose firms are determined to 391 be responsible. 392 Factor 1: Challenge Scenario 394 Factor 2: Small Business Participation 395 Factor 3: Supply Chain Risk 396 Offerors rated with Unacceptable in any Factor will not be eligible for award. For clarity, if an offeror 398 addresses Challenge Scenario 1a and 1b and receives an Acceptable in one scenario, however, receives an 399

Unacceptable in the second scenario, the offeror is still technically acceptable in Factor 1 and will remain eligible 400 for award. 401

FACTOR 1: CHALLENGE SCENARIO 404

Table 4: Factor 1 Challenge Scenario Acceptable/Unacceptable Ratings 406 Rating Definition Acceptable The proposal addresses all required minimum elements of the challenge scenario and presents a feasible and coherent approach. The Government has a reasonable expectation of successful performance. Any identified risks are manageable and do not indicate unsuccessful performance is likely. Offerors must receive at least an Acceptable rating in either 1a or 1b to be considered Acceptable for this factor.

Unacceptable The proposal fails to address one or more of the required minimum elements of the challenge scenario, contains material deficiencies, or presents performance risks that indicate unsuccessful performance is likely. Offerors who receive an Unacceptable rating in both 1a and 1b are considered Unacceptable for this factor.

The Government will conduct two separate evaluations of the offeror's proposed Deployment Approach (A003): one 408 for Volume 1: Factor 1 – Challenge Scenario 1a and one for Volume 1: Factor 1 – Challenge Scenario 1b. To be 409 rated Acceptable, the offeror’s proposal must meet the following minimum requirements for each applicable sub-410 factor: 411 Sub-Factor 1: Program Management and Governance 413 The proposal must describe a program management and governance approach that: 414

1. Includes a framework for managing, monitoring, and controlling all activities described in the challenge 415 scenario. 416

2. Addresses procedures for governance, risk management (identification, analysis, and mitigation), integrated 417 scheduling, quality control, and stakeholder communication. 418

3. Addresses the unique management challenges of supporting concurrent deployments in fixed-facility 419 (OCONUS medical center) (1a) or operational/expeditionary environments (1b). 420

Sub-Factor 2: Deployment and Integration 422 The proposal must describe a deployment and integration approach that: 423

1. Includes a methodology for site preparation and configuration (including data collection, migration, and 424 integration). 425

2. Includes a methodology for ensuring ongoing compliance with accrediting agencies (as it applies to 1a). 426

3. Addresses integration with hardware, medical devices, and networks (as it applies to 1a). 427

4. Addresses integration with hardware, medical devices, and diverse Service-specific networks (as it applies 428

1b). 429

5. Addresses how system security and data exchange will be maintained in disconnected, intermittent, and 430 low-bandwidth (DIL) environments (as it applies to 1b). 431

6. Presents at least one option for a low-to-no touch remote deployment for OpMed products (as it applies to 432

1b). 433 Sub-Factor 3: Continuity and Logistics 435 The proposal must demonstrate a continuity and logistics approach that: 436

1. Addresses how the continuity of healthcare delivery documentation will be maintained during deployment 437 to minimize disruption to patient care. 438

2. Addresses personnel travel requirements, including adherence to Status of Forces Agreements (SOFA) 439 where applicable. 440

3. Includes a methodology for network integration of all required hardware (as it applies to 1a). 441

4. Includes a methodology for supply chain management (as it applies to 1a). Includes a methodology for 442 managing the procurement, delivery, and tracking of hardware (as it applies to 1a). 443

Sub-Factor 4: Training 445 The proposal must demonstrate a training approach that: 446

1. Is scalable for a diverse user base across multiple time zones and locations. 447

2. Leverages existing curriculum. 448

3. Provides role-based training. 449

4. Includes methods for assessing user training performance and overall training effectiveness. 450

5. Protects Personally Identifiable Information (PII) and Protected Health Information (PHI). 451

6. Presents at least one option for 1a and three options for 1b for low-to-no touch remote training delivery. 452

Sub-Factor 5: User Adoption and Change Management 454 The proposal must demonstrate a user adoption and change management approach that: 455

1. Fosters and measures successful user adoption of the new product(s). 456

2. Details a methodology for proactive stakeholder engagement, strategic communications to drive user buy-457 in, and manage resistance to change. 458 The evaluation of Challenge Scenarios 1a and 1b is conducted solely to determine Factor 1 Acceptability at the 460 IDIQ level and does not restrict task order competition eligibility. 461

FACTOR 2: SMALL BUSINESS PARTICIPATION 463

Table 7: Factor 2 Acceptable/Unacceptable Ratings 465 Rating Definition Acceptable Proposal meets the minimum requirements of the solicitation.

Unacceptable Proposal does not meet the minimum requirements of the solicitation.

The Government will evaluate the offeror’s small business participation goals provided in the Addendum to 467 52.212-1. 468 The Government will evaluate the offeror’s proposed small business participation approach to ensure that it meets 470 the goals identified in FAR 52.212-1 Addendum. 471 The Government will evaluate whether the offeror’s approach thoroughly explains how it will meet all small 473 business goals throughout the life of the contract. 474 The Government will evaluate whether the proposed approach clearly evidences the offeror’s ability to meet the 476 offeror’s proposed goals. The Government will evaluate the offeror's explanation of historical achievements of 477 meeting proposed small business goals. If, historically, the offeror has not met small business goals, the Government 478 will assess the Offeror’s explanation of what actions it took to rectify the situation and what actions it will take to 479 meet its proposed goals on DHMS Deployment Solutions MAC. If the above criteria are not met, the Government 480 will consider the offer to be unacceptable and therefore ineligible for contract award. 481

FACTOR 3: SUPPLY CHAIN RISK 483

Table 8: Factor 3 Acceptable/Unacceptable Ratings 485 Rating Definition Acceptable Proposal meets the minimum requirements of the solicitation.

Unacceptable Proposal does not meet the minimum requirements of the solicitation.

The Government will evaluate the offeror’s approach to mitigating supply chain risk for information technology 487 supporting a covered system. To be rated Acceptable the offeror’s proposal must meet the following minimum 488 requirements provide a feasible and coherent approach to identify, assess, and mitigate supply chain risks associated 489 with hardware, software, and firmware, and confirm compliance with DFARS 252.204-7017 and 252.204-7018 and 490 FAR 52.204-8 Deviation, 52.204-26 52.240-90, and 52.240-91 requirements. 491 (End of Provision) 493