R

11. THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS

The above numbered solicitation is amended as set forth in Item 14. The hour and date specified for receipt of Offers is extended. is not extended.

Offers must acknowledge receipt of this amendment prior to the hour and date specified in the solicitation or as amended, by one of the following methods:

(a) By completing items 8 and 15, and returning copies of the amendment; (b) By acknowledging receipt of this amendment on each copy of the offer submitted;

or (c) By separate letter or electronic communication which includes a reference to the solicitation and amendment numbers. FAILURE OF YOUR ACKNOWLEDGMENT TO BE RECEIVED AT THE PLACE DESIGNATED FOR THE RECEIPT OF OFFERS PRIOR TO THE HOUR AND DATE SPECIFIED MAY RESULT IN REJECTION OF YOUR OFFER. If by virtue of this amendment you desire to change an offer already submitted, such change may be made by letter or electronic communication, provided each letter or electronic communication makes reference to the solicitation and this amendment, and is received prior to the opening hour and date specified.

12. ACCOUNTING AND APPROPRIATION DATA (If required)

13. THIS ITEM APPLIES ONLY TO MODIFICATIONS OF CONTRACTS/ORDERS.

IT MODIFIES THE CONTRACT/ORDER NUMBER AS DESCRIBED IN ITEM 14.

CHECK ONE A. THIS CHANGE ORDER IS ISSUED PURSUANT TO: (Specify authority) THE CHANGES SET FORTH IN ITEM 14 ARE MADE IN THE CONTRACT ORDER

NUMBER IN ITEM 10A.

B. THE ABOVE NUMBERED CONTRACT/ORDER IS MODIFIED TO REFLECT THE ADMINISTRATIVE CHANGES (such as changes in paying office, appropriation data, etc.) SET FORTH IN ITEM 14, PURSUANT TO THE AUTHORITY OF FAR 43.103(b).

C. THIS SUPPLEMENTAL AGREEMENT IS ENTERED INTO PURSUANT TO AUTHORITY OF:

D. OTHER (Specify type of modification and authority)

E. IMPORTANT: Contractor is not is required to sign this document and return copies to the issuing office.

14. DESCRIPTION OF AMENDMENT/MODIFICATION (Organized by UCF section headings, including solicitation/contract subject matter where feasible.)

Except as provided herein, all terms and conditions of the document referenced in Item 9A or 10A, as heretofore changed, remains unchanged and in full force and effect.

15A. NAME AND TITLE OF SIGNER (Type or print) 16A. NAME AND TITLE OF CONTRACTING OFFICER (Type or print)

15B. CONTRACTOR/OFFEROR

(Signature of person authorized to sign)

15C. DATE SIGNED 16B. UNITED STATES OF AMERICA

(Signature of Contracting Officer)

16C. DATE SIGNED

Previous edition unusable STANDARD FORM 30 (REV. 11/2016) Prescribed by GSA FAR (48 CFR) 53.243

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT 1. CONTRACT ID CODE PAGE OF PAGES

2. AMENDMENT/MODIFICATION NUMBER 3. EFFECTIVE DATE 4. REQUISITION/PURCHASE REQUISITION NUMBER 5. PROJECT NUMBER (If applicable)

6. ISSUED BY CODE 7. ADMINISTERED BY (If other than Item 6) CODE

8. NAME AND ADDRESS OF CONTRACTOR (Number, street, county, State and ZIP Code) (X) 9A. AMENDMENT OF SOLICITATION NUMBER

9B. DATED (SEE ITEM 11)

10A. MODIFICATION OF CONTRACT/ORDER NUMBE

10B. DATED (SEE ITEM 13)

CODE FACILITY CODE

SF 30 BLOCK 14 CONTINUATION PAGE

SUMMARY OF CHANGES

The following revisions have been made in response to industry questions. Block 14 (Description of Amendment/Modification):

1. Box 8 and 52.212-1, Section 2.2 has been revised to extend the closing date and time to 21 Apr 2026, 04:00 PM.

2. 52.212-1, Table 2: Proposal Volumes Section 3 has been revised to clarify the Support Contractor Proposal Consent is a statement to include in the Cover Letter.

3. 52.212-1, Table 2: Proposal Volumes Section 6 has been added to provide Item/Electronic File Name/File Type/Page Limits.

4. 52.212-1 VOLUME III; CONTRACT DOCUMENTS has been revised to provide offeror instructions at Section (6).

5. To Add Attachment 19: PEO DHMS Deployment Ordering Guide.

All other terms and conditions remain unchanged.

Solicitation/Contract Form

The following modifications were made:

Information From To Size Standard - Dollars $34,000,000.00 Reference Description North American Industry Classification System (NAICS) North American Industry Classification System

(NAICS)

541512

Response Due Time 12:00 PM 04:00 PM Response Due Date 27 Feb 2026 21 Apr 2026

List of Attachments

The following Attachment(s) were added:

PEO DHMS Deployment Ordering Guide

Instructions, Conditions, & Notices to Offerors or Quoters

Additional Regulation or Supplemental Clauses Incorporated by Full Text

The following Clauses modifications were made:

52.212-1 Instructions to Offerors-Commercial Products and Commercial Services. (Deviation) (Tailored) Feb 2026 hereby reads as follows:

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

1.0 Solicitation Information

This solicitation seeks full and open competitive offers. The North American Industry Classification System (NAICS) code is delineated on the SF-1449 cover sheet (including NAICS and size standards).

The Government intends to award multiple award contracts to each and all qualifying offerors in response to the Program Executive Office - Defense Healthcare Management System (PEO DHMS) Deployment Solutions solicitation in accordance with 10 U.S.C. 3206(c) implemented by RFO 15.104(b)(1)(ii). Therefore, Price will not be an evaluation factor for this solicitation.

2.0 General Instructions

All questions or concerns shall be submitted to the Contracting Officer and Points of Contact (POC): Below are the only points of contact for this solicitation.

Contract Specialist, using the submission instructions below. All proposal submissions shall be submitted using the instructions in Section 2.2 below. Service of protest to the Agency shall be submitted to the e-mail addresses below.

Table 1: Points of Contact

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

HT003826RE0010001

2.1.1 General Instructions

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

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

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

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

e. Proposals must not include classified information.

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

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

Note: Throughout the RFP documents, unless otherwise specified, reference to days will mean calendar days, not business days. In accordance with RFO 4.309(a)

(1) the Government will retain its copy of all unsuccessful proposals.

2.1.2 System for Award Management (SAM).

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

2.1.2.1 Contractor Teaming Arrangements & Joint Ventures

If an offeror is proposing under RFO Companion (FC) 9.000, where there is a joint venture or partnership, the combined entity shall be registered in SAM, and the SF-1449 must reflect the combined entity as the Prime.

Offerors shall provide Teaming Agreements in accordance with Volume III, Section 4.

2.2 Proposal Submission Instructions for Bidscale

Proposals must be submitted electronically via a secure online submission portal by . Bidscale aids the Government in April 21, 2026 at 4:00 PM Eastern Time evaluating acquisitions and reduces submission rounds through a structured submission process for proposal materials. The submission portal is a tool used solely to receive and evaluate proposals for this solicitation. Only Government signed documents, including evaluation reports and contracts are considered as the official record for contractual purposes.

1. Digital Submission Portal Access:

Offerors wishing to submit a proposal must first request a user account to access the digital submission portal. To request an account, please send an email to customersuccess@bidscale.com. The email must include the following information:

a. Subject Line: Submission Portal Account Creation

b. First Name

c. Last Name

d. Email Address

e. Company Name

f. Solicitation Name: PEO DHMS Deployment Solutions

Please allow at least 72 hours for account creation before the submission deadline. Once the account is created, offerors will receive a confirmation email with login instructions. Offerors may designate both a primary and backup user account. As a best practice, offerors are encouraged to use one user to complete the final submission to avoid partial uploads..

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

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

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

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

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

3. Confirm receipt of a confirmation email for your submission

Upon submission, you will receive a confirmation email from Bidscale acknowledging receipt of your proposal. Bidscale is only authorized in a limited capacity to issue access to the submission portal and provide basic technical support with its utilization. If a confirmation email was not received or technical issues occur with the submission portal, contact Bidscale for assistance prior to the closing date and time at customersuccess@bidscale.com and copy the Contracting Officer and Contract Specialist at dha.ncr.co.mbx.cd-dhms-contracting@health.mil. Offerors are responsible for completing proposal submissions before the closing date and time; therefore, early submissions are encouraged.

4. Evaluation:

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

5. Disclaimer:

Proprietary information submitted in response to this solicitation will be protected from unauthorized disclosure as required by Subsection 27 of the Office of Procurement Policy Act as amended (41 U.S.C.423) (hereinafter referred to as "the Act") as implemented in the FAR. These companies are bound contractually by Organizational Conflict of Interest and disclosure clauses with respect to proprietary information. Contractor personnel will take all necessary action to preclude unauthorized use or disclosure of an offeror's proprietary data.

The exclusive responsibility for source selection will reside with the Government.

The procuring Contracting Officer is the sole POC to offerors any proposal related questions. Bidscale is not authorized to address any issues/questions related to contractor proposal submissions. Offerors are encouraged to review all instructions carefully and ensure full compliance with all requests for proposal requirements to avoid any disqualification.

2.3 Communications and Solicitation Question Instructions

Communications between the Government and offerors will be controlled by the Contracting Officer and Contract Specialist. Offerors must submit all written proposal information via Bidscale Portal.

Solicitation questions must be submitted to the Contract Specialist attention via email dha.ncr.co.mbx.cd-dhms-contracting@health.mil. Solicitation questions must be submitted no later than . Questions provided using different means will not be considered. The Government will provide April 9, 2026 at 12:00 PM Eastern Time a response to the questions via SAM.gov. Responses may or may not require an amendment. Offerors are responsible to monitor SAM.gov for the most recent information for this solicitation.

2.3.1 Discussions

The Government will provide awards to all technically acceptable proposals. The Government intends to award without discussions or establishment of a competitive range; however, the Government reserves the right to hold discussions. If, during the evaluation period, it is determined to be in the best interest of the Government to hold discussions, offeror responses to Evaluation Notices (ENs) and the Final Proposal Revision (FPR) will be considered in making the source selection decision.

As the Government does not intend to hold discussions, offerors are advised to submit initial proposals that are well defined and clearly acceptable without additional information or substitute pages. Further, initial proposals should contain the offeror's best terms rather than relying on the potential for future negotiations.

2.3.2 Clarifications

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

2.4 Amendments to Solicitation

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

2.5 Period of Acceptance of Offers

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

2.6 Discrepancies

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

3.0 Proposal Content

The purpose of these instructions is to prescribe the format of proposals and describe the approach for the development and presentation of proposal information.

Proposals shall be submitted in accordance with these instructions or will be considered non-compliant.

3.1 Page Limitations

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

3.2 Page Size and Format for Written Proposal Submission

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

3.3 Title Page (not included in the page count)

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

Solicitation Number, and Name, address, telephone numbers and e-mail address of the offeror

3.4 Cross-Referencing

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

3.5 Indexing

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

3.6 Glossary of Abbreviations and Acronyms

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

3.7 Compliant

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

4.0 Proposal Instructions

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

Table 2: Proposal Volumes

ITEM

ELECTRONIC FILE

NAME

FILE

TYP

E

PAGE

LIMIT

S

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 - Supply Chain Risk Management Plan OfferorName_Factor3_ SupplyChain

.pdf 3

Volume III: Contract Documents

Section 1: Cover Letter OfferorName_CoverLet ter

.pdf 1

Section 2: Organizational Conflict of Interest (OCI) Declaration and Disclosure

OfferorName_OCI .pdf UNL

Section 3: Support Contractor Proposal Access Consent Statement Included in Cover Letter

N/A N/A

Section 4: Teaming Agreements OfferorName_Teaming Agreements

.pdf UNL

Section 5: Pre-Award Identification and Assertion of Restrictions on Commercial Technical Data and Commercial Computer Software

OfferorName_Pre- AwardAssertions

.pdf UNL

Section 6: Representation, Certification, & Other Statements OfferorName_RepsAndCerts .pdf UNL

NOTE: Volumes shall consist of the information specified for each evaluation factor listed below. All documents shall be searchable and capable of using highlights and comment boxes. File size shall not exceed 1.5 GB per file. No pricing information shall be included in Volumes I, II, and III.

FACTOR 1: CHALLENGE SCENARIO

Offerors shall provide a (1) proposed Deployment Approach (A003) (Volume 1: Factor 1 - Challenge Scenario 1a) as well as a (2) proposed Deployment Approach (A003) (Volume 1: Factor 1 - Challenge Scenario 1b) based on both of the following scenarios.

The Program Executive Office Defense Healthcare Management Systems (PEO DHMS) is modernizing its global healthcare capabilities, which includes the multi-faceted deployment of DHMS products (Federal Electronic Health Record (EHR) and Operational Medicine (OpMed)). The objective is to create a secure, seamless, and interoperable health information ecosystem that supports warfighters from the point of injury in austere, forward-deployed locations to definitive care.

Offerors shall propose an innovative and scalable deployment plan addressing two interconnected lines of effort as outlined below. The proposed approach shall address hardware and/or component installation and configuration across various networks, continuous patient data access, and comprehensive user training tailored to the operational environment and a diverse user audience. Additionally, the plan shall incorporate proactive risk mitigation strategies to address deployment complexities and ensure mission success. Offerors shall document any assumptions made within their proposed approach.

1a) Federal EHR product modernization and deployment: This effort focuses on the full implementation of the Federal EHR at established, high-capacity treatment facilities.

Scope:

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

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

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

1b) OpMed products' modernization and deployment: This effort delivers mobile and interoperable OpMed solutions to medical forces in deployed and tactical environments in both the Continental U.S. (CONUS) and OCONUS. This includes theater hospitals, hospital ships, forward resuscitative sites, and submarines.

These scalable deployments can occur concurrently across multiple sites, countries, or theaters, in remote or austere environments with each location receiving one or more products tailored to mission requirements. The deployment includes the OpMed product suite: Battlefield Assisted Trauma Distributed Observation Kit- Joint (BATDOK-J), Operational Medicine Care Delivery Platform (OpMed CDP), Theater Blood-Mobile (TBLD-M), and Medical Hub (MedHub).

Scope:

Rapidly deploy globally to no less than five sites/units simultaneously across forward-deployed locations managed by multiple Services in EUCOM and INDOPACOM (Role 1-3) with uncertain schedule and complex infrastructure. This includes deployments from Naval vessels and field hospitals to forward resuscitative and enroute care teams Services & Interoperability: Full-spectrum healthcare services are in scope, including ambulatory care, emergency trauma, surgical stabilization, enroute care, behavioral health, forward resuscitative, ancillary services (pharmacy, lab, imaging), and blood inventory and management. A critical requirement is ensuring seamless data transmission through all roles of care and aggregating medical data for Command and Control Situational Awareness (C2SA) reporting.

Technical Environment: The plan will address integration with complex Service-specific hardware and diverse Service networks for low-to-no-touch deployments, where the products may be remotely deployed and/or trained to the field in a disconnected, intermittent, and low-bandwidth (DIL) environment.

Note: For the purposes of the Challenge Scenario, the following terms are defined.

Innovative: A new or significantly improved technology, process, or method as of the date of the submission of the proposal.

Scalable: Resources can be quickly scaled up or down to match demand.

Feasible: The ability to achieve deployment with the available resources, technology, time, and schedule. It is a pragmatic assessment of whether an idea can be successfully executed in the real world, while actively minimizing risk.

Coherent: The approach is logical and understandable.

FACTOR 2: SUPPLY CHAIN RISK MANAGEMENT PLAN

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

VOLUME III: CONTRACT DOCUMENTS

(1) Cover Letter

The Offeror's proposal shall include a cover letter on the Offeror's letterhead stationery and signed by an executive of the company who possesses authority to bind the Offeror contractually. The cover letter shall acknowledge receipt of all amendments (if any are issued) to the RFP and include signed copies of the SF 30. The submittal letter shall identify all enclosures being transmitted as part of the response to the RFP. The letter shall reference the RFP number and acknowledge that the Offeror is submitting an offer in response to the RFP. It shall state: (1) Commercial and Government Entity (CAGE) number, (2) Unique Entity Identifier (UEI),

(3) Taxpayer Identification Number (TIN), (4) a statement that the proposal is valid 180 days past the estimated award date, (5) provide support contractor proposal access content (see 3) Support Contractor Proposal Access Consent below), and (6) include a statement clarifying the extent to which AI was or was not used in preparation of the proposal.

(2) Organizational Conflict of Interest (OCI) Declaration and Disclosure

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

(3) Support Contractor Proposal Access Consent

Contractor support personnel from the below listed companies under existing PEO DHMS contracts will be used for administrative purposes only. This assistance will not include analyzing or evaluating proposals.

Table 3: Contractor Support Personnel - Administrative

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 required by Subsection 27 of the Office of Procurement Policy Act as amended (41 U.S.C. 423) (hereinafter referred to as "the Act") as implemented in the FAR. Contractor Support Personnel are bound contractually by Organizational Conflict of Interest and disclosure clauses with respect to proprietary information. Contractor personnel will take all necessary action to preclude unauthorized use or disclosure of an Offeror's proprietary data.

The offeror's Cover Letter (Volume III Section 1) to this solicitation MUST clearly state permission is granted allowing the contractor support identified above access to the contractor's proposal. Subcontractors that provide proposal information separate from the Prime contractor's proposal submittal shall clearly state permission is granted allowing the contractor support identified above access to the subcontractor's proposal in a cover letter or similar notification. The Offeror and its subcontractors may choose to execute a proposal access agreement with these support contractors. Failure to clearly state permission is granted for access to the contractor's proposal may result in the offer being deemed unacceptable and therefore ineligible for contract award.

The exclusive responsibility for source selection will reside with the Government.

(4) Teaming Agreements

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

(5) Pre-Award Identification and Assertion of Restrictions on Commercial Technical Data and Commercial Computer Software

Offerors shall identify all commercial technical data, commercial computer software, and commercial computer software documentation in accordance with Addendum 3 - Pre-Award Identification and Assertion of Restrictions on Commercial Technical Data and Commercial Computer Software. The Government will consider this assertion as part of the offeror's responsibility.

(6) Representation, Certification, & Other Statements

The solicitation provides offerors Representation, Certification, & Other Statements. An offeror's current SAM record is preferred, and a submission is not required when the SAM record is current. Offeror shall submit requested representations and certifications only when missing from the SAM record.

(End of Provision)

DEF HC MGT SYS CONTRACT DIV DHMS-CD, 1700 NORTH MOORE STREET, SUITE 2300

ROSSLYN, VA 22209

UNITED STATES

Hailey Deluca, Email: hailey.s.deluca.civ@health.mil Telephone: 7039693223 AdminBy:

SCD: PAS: