36C10B25Q0431.docx

36C10B25Q0431

PAGE 1 OF

1. REQUISITION NO.

2. CONTRACT NO.

3. AWARD/EFFECTIVE DATE

4. ORDER NO.

5. SOLICITATION NUMBER

6. SOLICITATION ISSUE DATE

a. NAME

b. TELEPHONE NO. (No Collect Calls)

8. OFFER DUE DATE/LOCAL

TIME

9. ISSUED BY

CODE

10. THIS ACQUISITION IS

UNRESTRICTED OR

SET ASIDE:

% FOR:

SMALL BUSINESS

HUBZONE SMALL

BUSINESS

SERVICE-DISABLED

VETERAN-OWNED

SMALL BUSINESS

WOMEN-OWNED SMALL BUSINESS

(WOSB) ELIGIBLE UNDER THE WOMEN-OWNED

SMALL BUSINESS PROGRAM

EDWOSB

8(A)

NAICS:

SIZE STANDARD:

11. DELIVERY FOR FOB DESTINA-

TION UNLESS BLOCK IS

MARKED

SEE SCHEDULE

12. DISCOUNT TERMS

13a. THIS CONTRACT IS A

RATED ORDER UNDER

DPAS (15 CFR 700)

13b. RATING

14. METHOD OF SOLICITATION

RFQ

IFB

RFP

15. DELIVER TO

CODE

16. ADMINISTERED BY

CODE

17a. CONTRACTOR/OFFEROR

CODE

FACILITY CODE

18a. PAYMENT WILL BE MADE BY

CODE

TELEPHONE NO.

UEI:

EFT:

PHONE:

FAX:

17b. CHECK IF REMITTANCE IS DIFFERENT AND PUT SUCH ADDRESS IN OFFER 18b. SUBMIT INVOICES TO ADDRESS SHOWN IN BLOCK 18a UNLESS BLOCK BELOW IS CHECKED

SEE ADDENDUM

19.

20.

21.

22.

23.

24.

ITEM NO.

SCHEDULE OF SUPPLIES/SERVICES

QUANTITY

UNIT

UNIT PRICE

AMOUNT

(Use Reverse and/or Attach Additional Sheets as Necessary)

25. ACCOUNTING AND APPROPRIATION DATA

26. TOTAL AWARD AMOUNT (For Govt. Use Only) 27a. SOLICITATION INCORPORATES BY REFERENCE FAR 52.212-1, 52.212-4. FAR 52.212-3 AND 52.212-5 ARE ATTACHED. ADDENDA

ARE

ARE NOT ATTACHED.

27b. CONTRACT/PURCHASE ORDER INCORPORATES BY REFERENCE FAR 52.212-4. FAR 52.212-5 IS ATTACHED. ADDENDA

ARE

ARE NOT ATTACHED

28. CONTRACTOR IS REQUIRED TO SIGN THIS DOCUMENT AND RETURN _______________

29. AWARD OF CONTRACT: REF. ___________________________________ OFFER

COPIES TO ISSUING OFFICE. CONTRACTOR AGREES TO FURNISH AND

DATED ________________________________. YOUR OFFER ON SOLICITATION

DELIVER ALL ITEMS SET FORTH OR OTHERWISE IDENTIFIED ABOVE AND ON ANY

(BLOCK 5), INCLUDING ANY ADDITIONS OR CHANGES WHICH ARE

ADDITIONAL SHEETS SUBJECT TO THE TERMS AND CONDITIONS SPECIFIED

SET FORTH HEREIN IS ACCEPTED AS TO ITEMS:

30a. SIGNATURE OF OFFEROR/CONTRACTOR 31a. UNITED STATES OF AMERICA (SIGNATURE OF CONTRACTING OFFICER) 30b. NAME AND TITLE OF SIGNER (TYPE OR PRINT) 30c. DATE SIGNED 31b. NAME OF CONTRACTING OFFICER (TYPE OR PRINT) 31c. DATE SIGNED

AUTHORIZED FOR LOCAL REPRODUCTION

(REV. NOV 2021)

PREVIOUS EDITION IS NOT USABLE

Prescribed by GSA - FAR (48 CFR) 53.212

7. FOR SOLICITATION

INFORMATION CALL:

STANDARD FORM 1449

SOLICITATION/CONTRACT/ORDER FOR COMMERCIAL PRODUCTS AND COMMERCIAL SERVICES

OFFEROR TO COMPLETE BLOCKS 12, 17, 23, 24, & 30

36C10B25Q0431

XXX

Sarah MacArthur 848-377-5179

10:00 AM

EDT

Department of Veterans Affairs Technology Acquisition Center

23 Christopher Way Eatontown NJ 07724

X

N/A

See Delivery Schedule

Department of Veterans Affairs Technology Acquisition Center

23 Christopher Way

Department of Veterans Affairs Technology Acquisition Center Financial Services Center PO Box 149971 Austin TX 78714-8971

See CONTINUATION Page Project Title: InterSystems Software Updates and Technical

Type of Contract: Firm Fixed Price (FFP)

See Section B

See CONTINUATION Page

Matthew Newell

Table of Contents

SECTION B - CONTINUATION OF SF 1449 BLOCKS

B.1 GOVERNING LAW

Federal law and regulations, including the Federal Acquisition Regulations (FAR), shall govern this Contract/Order. Commercial license agreements may be made a part of this Contract/Order but only if both parties expressly make them an addendum hereto. If the commercial license agreement is not made an addendum, it shall not apply, govern, be a part of or have any effect whatsoever on the Contract/Order; this includes, but is not limited to, any agreement embedded in the computer software (clickwrap), any agreement that is otherwise delivered with or provided to the Government with the commercial computer software or documentation (shrinkwrap), or any other license agreement otherwise referred to in any document. If a commercial license agreement is made an addendum, only those provisions addressing data rights regarding the Government’s use, duplication and disclosure of data (e.g., restricted computer software) are included and made a part of this Contract/Order, and only to the extent that those provisions are not duplicative or inconsistent with Federal law, Federal regulation, the incorporated FAR clauses and the provisions of this Contract/Order; those provisions in the commercial license agreement that do not address data rights regarding the Government’s use, duplication and disclosure of data shall not be included or made a part of the Contract/Order. Federal law and regulation including, without limitation, the Contract Disputes Act (41 U.S.C. § 7101 et seq.), the Anti-Deficiency Act (31 U.S.C. § 1341 et seq.), the Competition in Contracting Act (41 U.S.C. § 3301 et seq.), the Prompt Payment Act (31 U.S.C. §3901 et seq.), Contracts for Data Processing or Maintenance (38 USC § 5725), and FAR clauses 52.212-4, 52.227-14, 52.227-19 shall supersede, control, and render ineffective any inconsistent, conflicting, or duplicative provision in any commercial license agreement. In the event of conflict between this Clause and any provision in the Contract/Order or the commercial license agreement or elsewhere, the terms of this Clause shall prevail. Claims of patent or copyright infringement brought against the Government as a party shall be defended by the U.S. Department of Justice (DOJ). 28 U.S.C. § 516. At the discretion of DOJ, the Contractor may be allowed reasonable participation in the defense of the litigation. Any additional changes to the Contract/Order must be made by contract/order modification (Standard Form 30) and shall only be affected by a warranted Contracting Officer. Nothing in this Contract/Order or any commercial license agreement shall be construed as a waiver of sovereign immunity.

B.2 SOFTWARE LICENSE, MAINTENANCE AND TECHNICAL SUPPORT SOFTWARE LICENSE, MAINTENANCE AND TECHNICAL SUPPORT:

1. Definitions.

Licensee. The term “licensee” shall mean the U.S. Department of Veterans Affairs (“VA”) and is synonymous with “Government.”

Licensor. The term “licensor” shall mean the contractor having the necessary license or ownership rights to deliver license, software maintenance and support of the computer software being acquired. The term “contractor” is the party identified in Block 17a on the SF1449. If the contractor is a reseller and not the Licensor, the contractor remains responsible for performance under this order.

Software. The term “software” shall mean the licensed computer software product(s) cited in the Schedule of Supplies/Services.

Maintenance. The term “maintenance” is the process of enhancing and optimizing software, as well as remedying defects. It shall include all new fixes, patches, releases, updates, versions and upgrades, as further defined below.

Technical Support. The term “technical support” refers to the range of services providing assistance for the software via the telephone, email, a website or otherwise.

Release or Update. The term “release” or “update” are terms that refer to a revision of software that contains defect corrections, minor enhancements or improvements of the software’s functionality. This is usually designated by a change in the number to the right of the decimal point (e.g., from Version 5.3 to 5.4). An example of an update is the addition of new hardware.

Version or Upgrade. The term “version” or “upgrade” are terms that refer to a revision of software that contains new or improved functionality. This is usually designated by a change in the number to the left of the decimal point (e.g., from Version 5.4 to 6).

1. Software License Unless otherwise stated in the Schedule of Supplies/Services, the Performance Work Statement or Product Description, the software license provided to the Government is a perpetual, nonexclusive license to use the software The Government may use the software in a networked environment.

Any dispute regarding the license grant or usage limitations shall be resolved in accordance with the Disputes Clause incorporated in FAR 52.212-4(d).

All limitations of software usage are expressly stated in the Schedule of Supplies/Services and the Performance Work Statement/Product Description.

1. Software Maintenance and Technical Support

1. Disabling Software Code. The Government requires delivery of computer software that does not contain any code that will, upon the occurrence or the nonoccurrence of any event, disable the software. Such code includes but is not limited to a computer virus, restrictive key, node lock, time-out or other function, whether implemented by electronic, mechanical, or other means, which limits or hinders the use or access to any computer software based on residency on a specific hardware configuration, frequency of duration of use, or other limiting criteria. If any such disabling code is present, the contractor agrees to indemnify the Government for all damages suffered as a result of a disabling caused by such code, and the contractor agrees to remove such code upon the Government’s request at no extra cost to the Government. Inability of the contractor to remove the disabling software code will be considered an inexcusable delay and a material breach of contract, and the Government may exercise its right to terminate for cause. In addition, the Government is permitted to remove the code as it deems appropriate and charge the Contractor for consideration for the time and effort expended in removing the code.

1. Manuals and Publications. Upon Government request, the contractor shall furnish the most current version of the user manual and publications for all products/services provided under this contract or order at no cost.

B.3 CONTRACT ADMINISTRATION DATA

1. Contract Administration: All contract administration matters will be handled by the following individuals:

a. CONTRACTOR: TBD

b. GOVERNMENT: Contracting Officer

2. CONTRACTOR REMITTANCE ADDRESS: All payments by the Government to the contractor will be made in accordance with:

3. INVOICES: Invoices shall be submitted in arrears:

4. GOVERNMENT INVOICE ADDRESS: All Invoices from the contractor shall be submitted electronically in accordance with VAAR Clause 852.232-72 Electronic Submission of Payment Requests.

5. ACKNOWLEDGMENT OF AMENDMENTS: The offeror acknowledges receipt of amendments to the Solicitation numbered and dated as follows:

B.4 PRICE SCHEDULE

Any resulting contract will be awarded on a firm-fixed-price basis as defined by Federal Acquisition Regulation Subpart 16.202. Accordingly, the Contractor shall ensure that any and all costs associated with the Contractor’s proposed application(s), software products, software solution, and/or system, shall be included in the Contractor’s proposed firm-fixed price, and shall serve as the Contractor’s firm-fixed price for the life of any resulting contract. No additional costs or fees relative to the Contractor’s proposed application(s), software products, software solution, and/or system including, but not limited to, licensing costs and any associated licensing maintenance required for the development, delivery, integration, operation, and/or maintenance of the Contractor’s proposed solution will be allowed, accepted, and/or paid by the Government.

Inspection: Destination Acceptance: Destination Free on Board (FOB): Destination

BASE PERIOD

The period of performance is six months commencing October 1, 2025 through March 31, 2026.

Contract Line Item Number

(CLIN)

Description

Quantity

Unit

Unit Price

Total Price

The SUTA Bundle shall also include dedicated 24 hours per day, 7 days per week support. Reporting of support tickets shall also be provided. The report shall detail the number of support tickets created and resolved for the period of performance.

SUTA Ticket Summary Report is due monthly in accordance with PD Section 1.2.

OPTION PERIOD 1 (6 Months) Option Period may be exercised in accordance with FAR 52.217-9, “Option to Extend the Term of the Contract.” Work shall not commence until, and unless, a formal modification is issued by the Contracting Officer. The period of performance is six months commencing April 1, 2026 through September 30, 2026.

The SUTA Bundle shall also include dedicated 24 hours per day, 7 days per week support. Reporting of support tickets shall also be provided. The report shall detail the number of support tickets created and resolved for the period of performance.

The Period of Performance for maintenance and support is April 1, 2026 through September 30, 2026.

SUTA Ticket Summary Report is due monthly in accordance with PD Section 1.2.

OPTION PERIOD 2 (6 Months) Option Period may be exercised in accordance with FAR 52.217-9, “Option to Extend the Term of the Contract.” Work shall not commence until, and unless, a formal modification is issued by the Contracting Officer. The period of performance is six months commencing October 1, 2026 through March 31, 2027.

The SUTA Bundle shall also include dedicated 24 hours per day, 7 days per week support. Reporting of support tickets shall also be provided. The report shall detail the number of support tickets created and resolved for the period of performance.

The Period of Performance for maintenance and support is October 1, 2026 through March 31, 2027.

SUTA Ticket Summary Report is due monthly in accordance with PD Section 1.2.

OPTION PERIOD 3 (6 Months) Option Period may be exercised in accordance with FAR 52.217-9, “Option to Extend the Term of the Contract.” Work shall not commence until, and unless, a formal modification is issued by the Contracting Officer. The period of performance is six months commencing April 1, 2027 through September 30, 2027.

The SUTA Bundle shall also include dedicated 24 hours per day, 7 days per week support. Reporting of support tickets shall also be provided. The report shall detail the number of support tickets created and resolved for the period of performance.

The Period of Performance for maintenance and support is April 1, 2027 through September 30, 2027.

SUTA Ticket Summary Report is due monthly in accordance with PD Section 1.2.

OPTION PERIOD 4 (6 Months) Option Period may be exercised in accordance with FAR 52.217-9, “Option to Extend the Term of the Contract.” Work shall not commence until, and unless, a formal modification is issued by the Contracting Officer. The period of performance is six months commencing October 1, 2027 through March 31, 2028.

The SUTA Bundle shall also include dedicated 24 hours per day, 7 days per week support. Reporting of support tickets shall also be provided. The report shall detail the number of support tickets created and resolved for the period of performance.

The Period of Performance for maintenance and support is October 1, 2027 through March 31, 2028.

SUTA Ticket Summary Report is due monthly in accordance with PD Section 1.2.

OPTION PERIOD 5 (6 Months) Option Period may be exercised in accordance with FAR 52.217-9, “Option to Extend the Term of the Contract.” Work shall not commence until, and unless, a formal modification is issued by the Contracting Officer. The period of performance is six months commencing April 1, 2028 through September 30, 2028.

The SUTA Bundle shall also include dedicated 24 hours per day, 7 days per week support. Reporting of support tickets shall also be provided. The report shall detail the number of support tickets created and resolved for the period of performance.

The Period of Performance for maintenance and support is April 1, 2028 through September 30, 2028.

SUTA Ticket Summary Report is due monthly in accordance with PD Section 1.2.

OPTION PERIOD 6 (6 Months) Option Period may be exercised in accordance with FAR 52.217-9, “Option to Extend the Term of the Contract.” Work shall not commence until, and unless, a formal modification is issued by the Contracting Officer. The period of performance is six months commencing October 1, 2028 through March 31, 2029.

The SUTA Bundle shall also include dedicated 24 hours per day, 7 days per week support. Reporting of support tickets shall also be provided. The report shall detail the number of support tickets created and resolved for the period of performance.

The Period of Performance for maintenance and support is October 1, 2028 through March 31, 2029.

SUTA Ticket Summary Report is due monthly in accordance with PD Section 1.2.

OPTION PERIOD 7 (6 Months) Option Period may be exercised in accordance with FAR 52.217-9, “Option to Extend the Term of the Contract.” Work shall not commence until, and unless, a formal modification is issued by the Contracting Officer. The period of performance is six months commencing April 1, 2029 through September 30, 2029.

The SUTA Bundle shall also include dedicated 24 hours per day, 7 days per week support. Reporting of support tickets shall also be provided. The report shall detail the number of support tickets created and resolved for the period of performance.

The Period of Performance for maintenance and support is April 1, 2029 through September 30, 2029.

SUTA Ticket Summary Report is due monthly in accordance with PD Section 1.2.

OPTION PERIOD 8 (6 Months) Option Period may be exercised in accordance with FAR 52.217-9, “Option to Extend the Term of the Contract.” Work shall not commence until, and unless, a formal modification is issued by the Contracting Officer. The period of performance is six months commencing October 1, 2029 through March 31, 2030.

The SUTA Bundle shall also include dedicated 24 hours per day, 7 days per week support. Reporting of support tickets shall also be provided. The report shall detail the number of support tickets created and resolved for the period of performance.

The Period of Performance for maintenance and support is October 1, 2029 through March 31, 2030.

SUTA Ticket Summary Report is due monthly in accordance with PD Section 1.2.

OPTION PERIOD 9 (6 Months) Option Period may be exercised in accordance with FAR 52.217-9, “Option to Extend the Term of the Contract.” Work shall not commence until, and unless, a formal modification is issued by the Contracting Officer. The period of performance is six months commencing April 1, 2030 through September 30, 2030.

The SUTA Bundle shall also include dedicated 24 hours per day, 7 days per week support. Reporting of support tickets shall also be provided. The report shall detail the number of support tickets created and resolved for the period of performance.

The Period of Performance for maintenance and support is April 1, 2029 through September 30, 2029.

SUTA Ticket Summary Report is due monthly in accordance with PD Section 1.2.

OPTIONAL TASK 1 (6 Months) Optional Task 1 - IAW FAR 52.217-7 Option for Increased Quantity Separately Priced Line Item (MAR 1989). This optional task may be exercised one time, two weeks prior to the end of the performance period. Work shall not commence until, and unless, a formal modification is issued by the Contracting Officer.

Each quantity of 1 = 1 Optional Task Team Size: FTEs = 5

· 2 System Administrator – Senior

· 2 Developer – Expert

· .5 Functional Analyst – Senior

· .25 Technical Writer/Editor – Senior

· .25 PM

OPTIONAL TASK 2 (6 Months) Optional Task 2 - IAW FAR 52.217-7 Option for Increased Quantity Separately Priced Line Item (MAR 1989). This optional task may be exercised one time, two weeks prior to the end of the performance period. Work shall not commence until, and unless, a formal modification is issued by the Contracting Officer.

Each quantity of 1 = 1 Optional Task

Team Size: FTEs = 4.5

· 2 Integration Engineer – Expert

· 1 Functional Analyst – Senior

· 1 Cyber Security Specialist – Senior

· .5 Technical Writer/Editor – Senior

OPTIONAL TASK 3 (6 Months) Optional Task 3 - IAW FAR 52.217-7 Option for Increased Quantity Separately Priced Line Item (MAR 1989). This optional task may be exercised one time, two weeks prior to the end of the performance period. Work shall not commence until, and unless, a formal modification is issued by the Contracting Officer.

Each quantity of 1 = 1 Optional Task

Team Size: FTEs = 4

· 2 Developer – Expert

· 1 Functional Analyst

· .5 Technical Writer/Editor – Senior

· .5 System Architect – Senior

OPTIONAL TASK 4 (6 Months) Optional Task 4 - IAW FAR 52.217-7 Option for Increased Quantity Separately Priced Line Item (MAR 1989). This optional task may be exercised one time, two weeks prior to the end of the performance period. Work shall not commence until, and unless, a formal modification is issued by the Contracting Officer.

Each quantity of 1 = 1 Optional Task

Team Size: FTEs = 7

· 3 Developer – Expert

· .5 Database Architect – Senior

· 1 Software/System Architect – Senior

· 1 Data Scientist

· .5 Test Engineer – Senior

· 1 Data Analyst

OPTIONAL TASK 5 (6 Months) Optional Task 5 - IAW FAR 52.217-7 Option for Increased Quantity Separately Priced Line Item (MAR 1989). This optional task may be exercised one time, two weeks prior to the end of the performance period. Work shall not commence until, and unless, a formal modification is issued by the Contracting Officer.

Each quantity of 1 = 1 Optional Task

Team Size: FTEs = 5

· 2 Cyber Security Specialist – Senior

· 1 Functional Analyst – Senior

· 1 Senior Software Engineer

SUMMARY:

TOTAL BASE PERIOD:

TOTAL OPTION PERIOD ONE:

TOTAL OPTION PERIOD TWO:

TOTAL OPTION PERIOD THREE:

TOTAL OPTION PERIOD FOUR:

TOTAL OPTION PERIOD FIVE:

TOTAL OPTION PERIOD SIX:

TOTAL OPTION PERIOD SEVEN:

TOTAL OPTION PERIOD EIGHT:

TOTAL OPTION PERIOD NINE:

TOTAL OPTIONAL TASK ONE:

TOTAL OPTIONAL TASK TWO:

TOTAL OPTIONAL TASK THREE:

TOTAL OPTIONAL TASK FOUR:

TOTAL OPTIONAL TASK FIVE:

TOTAL CONTRACT PRICE:

PRODUCT DESCRIPTION (PD)

DEPARTMENT OF VETERANS AFFAIRS

Office of Information & Technology Product Delivery Service (PDS) Health Platform Services

INTERSYSTEMS SOFTWARE UPDATES AND TECHNICAL ASSISTANCE

Date: 07/30/2025

VA-26-00003659

PD Version Number: 3.0

1.0 PRODUCT REQUIREMENTS

The Department of Veterans Affairs, Office of Information and Technology (OIT), Product Delivery Service (PDS) Health Platform Services has a requirement for Software Updates and Technical Assistance (SUTA) for brand name unlimited use, perpetual enterprise license products in the VA, which are InterSystems Interoperable, Reliable, Intuitive, Scalable (IRIS) Software, InterSystems HealthShare Health Connect Software, InterSystems HealthShare Heath Information Exchange Software, HealthShare Health Insight, InterSystems Action Engine. In addition, VA requires brand name IRIS - Advanced Server. All software shall be delivered via a VA-dedicated, contractor-provided, file transfer protocol (FTP) site. The current approved process to obtain new versions of the software is that the vendor (InterSystems) provides a secure email to VA staff with instructions on how and where to download the software from the vendor’s secure portal which requires log in credentials. VA staff perform md5sum checksum verifications to ensure that the software is the correct version and is authentic.

Please be advised that the Government hereby specifically reserves the right to determine, at any time during the designated option period, whether additional quantities of IT professional services, which include Advisory Packages identified in Section 1.3, are required. As such, the Government expressly provides herein that, if it so determines, it may procure optional quantities of up to 10 for each Advisory Package.

These optional quantities may be exercised multiple times during the designated option period, but in no instance shall the cumulative value of the options exercised exceed the aforementioned quantities, in accordance with Section B. Options may be exercised at any time and from time to time between the date of award of any resulting Delivery Order.

These requirements maintain the current infrastructure supporting VA’s current Electronic Health Record (EHR) database as the VA transitions to a new EHR. The Contractor shall also grant VA personnel access to its annual conference.

The period of performance shall be a base period of six (6) months followed by nine (9) six-month option periods and optional tasks.

Base Period – Period of performance 6 months

SUTA Bundle

Option Period 1 – Period of performance 6 months

SUTA Bundle

Option Period 2 – Period of performance 6months

SUTA Bundle

Option Period 3 – Period of performance 6 months

SUTA Bundle

Option Period 4 – Period of performance 6 months

SUTA Bundle

Option Period 5 – Period of performance 6 months

SUTA Bundle

Option Period 6 – Period of performance 6 months

SUTA Bundle

Option Period 7 – Period of performance 6 months

SUTA Bundle

Option Period 8 – Period of performance 6 months

SUTA Bundle

Option Period 9 – Period of performance 6 months

SUTA Bundle

1.1 SOFTWARE UPDATES AND TECHNICAL ASSISTANCE (SUTA)

SUTA Bundle shall include all upgrades and updates to the following InterSystems products:

· IRIS for Health

· HealthShare Health Connect

· HealthShare Unified Care Record (with Healthcare Action Engine)

· HealthShare Health Insight

· IRIS - Advanced Server

The SUTA Bundle shall also include dedicated 24 hours per day, 7 days per week support. Reporting of support tickets shall also be provided. The report shall detail the number of support tickets created and resolved for the period of performance (PoP). The vendor (InterSystems) shall have the ability to join Teams calls in order to provide support. Any logs that the vendor may need are uploaded via a secure server similar to the one where the software is downloaded from.

In addition, the Contractor shall provide Registration for training at InterSystems Global Summit.

1.2 DELIVERABLES

1.3 Advisory Packages (Optional tasks – 6-Month PoP):

Package A (VistA Operations Team) NTE 10 Quantities Team Size: FTEs = 5

· 2 System Administrator – Senior

· 2 Developer – Expert

· .5 Functional Analyst – Senior

· .25 Technical Writer/Editor – Senior

· .25 PM

Package B (Interfaces and Interoperability Team) NTE 10 Quantities Team Size: FTEs = 4.5

· 2 Integration Engineer – Expert

· 1 Functional Analyst – Senior

· 1 Cyber Security Specialist – Senior

· .5 Technical Writer/Editor – Senior

Package C (VDIF Support Team) NTE 10 Quantities Team Size: FTEs = 4

· 2 Developer – Expert

· 1 Functional Analyst

· .5 Technical Writer/Editor – Senior

· .5 System Architect – Senior

Package D (VistA Modernization Team) NTE 10 Quantities Team Size: FTEs = 7

· 3 Developer – Expert

· .5 Database Architect – Senior

· 1 Software/System Architect – Senior

· 1 Data Scientist

· .5 Test Engineer – Senior

· 1 Data Analyst

Package E (Security, Governance, and Reporting Team) NTE 10 Quantities Team Size: FTEs = 5

· 2 Cyber Security Specialist – Senior

· 1 Functional Analyst – Senior

· 1 Senior Software Engineer

Please be advised that the Government hereby specifically reserves the right to determine, at any time during the designated option period, whether additional quantities of IT professional services are required. As such, the Government expressly provides herein that, if it so determines, it may procure optional quantities of up to 10 quantities for each Advisory Package exercised in accordance with Section 1.3.1 Engineering Sustainment: Health, Performance, and Resilience and Section 1.3.2 Traditional Operational Support.

1.3.1 Engineering Sustainment: Health, Performance and Resilience

This component ensures IRIS and HealthShare environments are proactively managed to support system health, resiliency, and continuous performance:

1. System Monitoring

· Real-time Key Performance Indicator (KPIs): Central Processing Unit (CPU), memory, disk Input/Output (I/O), journaling integrity, Enterprise Cache Protocol (ECP) cache behavior

· Health Level Seven (HL7)/Fast Health Interoperability Resources (FHIR) message throughput analysis

· License Unit Health License Unit (HLU) utilization and capacity forecasting

1. Performance Management

· Cache optimization: global/routine cache configuration

· Indexing and query optimization strategies

· Connection and workload concurrency tuning

1. Health Automation (HA)

· Automated alerts for performance anomalies (e.g., cache miss, queue buildup) Smart routing load balancing (ECP) & message queue tuning)

1. Resilience Engineering

· Mirroring for HA/failover

· Tiered backup architecture (hot/warm/cold)

· Message replay & transaction recovery

· Journal and data integrity checks (checksums, crash validation)

1. Security

· Federal Information Processing Standard (FIPS) 140-2 encryption compliance (data at rest/in transit)

· Role-Based Access Control (RBAC) enforcement and auditing

· Consent-aware data masking and access enforcement

1.3.2 Traditional Operational Support

These elements sustain daily operations, secure configurations, and ensure compliant system usage:

1. System Administration

· User management, patching, and IRIS/HealthShare configuration maintenance Instance-level security review and control

1. Interface Management

· HL7/FHIR/X12 onboarding, validation, and endpoint testing

· Message queue visibility and remediation tooling API monitoring and throughput validation

1. Change Management

· Version control and rollback processes for IRIS and HealthShare modules Controlled release cycles with full impact assessments

1. Capacity and Resource Planning

· Forecasting HLU growth

· IRIS core and memory utilization modeling

1. Scaling strategies for interface count and data traffic

· Incident Response and Escalation

· 24/7 Tier-1 through Tier-3 support

· Service Level Agreement (SLA) based resolution timelines

· Vendor escalation protocols with InterSystems Engineering

1. Compliance Readiness

· Support for Health Insurance Portability and Accountability Act (HIPAA), Office of the National Coordinator for Health Information Technology (ONC) mandates, etc.

· Consent logic enforcement and logging

· Certified terminology integration (Systemized Nomenclature of Medicine – Clinical Terms (SNOMED CT), Logical Observation Identifiers, Names, and Codes (LOINC), International Classification of Diseases (ICD) -10)

1. Version Alignment

· Platform release compatibility tracking (IRIS ↔ HealthShare) Maintenance in Release/Long-Term Support (MIR/LTS) cycle compliance

1. Reporting & Governance

· Oversight & Strategic Planning

· Monthly reviews: Health dashboards, incident summaries, SLA reports

· Quarterly strategy updates: HLU trends, licensing requirements, scaling plans

· Audit readiness: Access log export, change reporting, interface-level activity tracking

2.0 NOTICE OF THE FEDERAL ACCESSIBILITY LAW AFFECTING ALL INFORMATION AND COMMUNICATION TECHNOLOGY (ICT) PROCUREMENTS (SECTION 508)

On January 18, 2017, the Architectural and Transportation Barriers Compliance Board (Access Board) revised and updated, in a single rulemaking, standards for electronic and information technology developed, procured, maintained, or used by Federal agencies covered by Section 508 of the Rehabilitation Act of 1973, as well as our guidelines for telecommunications equipment and customer premises equipment covered by Section 255 of the Communications Act of 1934. The revisions and updates to the Section 508-based standards and Section 255-based guidelines are intended to ensure that information and communication technology (ICT) covered by the respective statutes is accessible to and usable by individuals with disabilities.

2.1 SECTION 508 – INFORMATION AND COMMUNICATION TECHNOLOGY (ICT) STANDARDS

The Section 508 standards established by the Access Board are incorporated into, and made part of all VA orders, solicitations and purchase orders developed to procure ICT. These standards are found in their entirety at: https://www.access-board.gov/guidelines-and-standards/communications-and-it/about-the-ict-refresh/final-rule/text-of-the-standards-and-guidelines. A printed copy of the standards will be supplied upon request.

Federal agencies must comply with the updated Section 508 Standards beginning on January 18, 2018. The Final Rule as published in the Federal Register is available from the Access Board: https://www.access-board.gov/guidelines-and-standards/communications-and-it/about-the-ict-refresh/final-rule.

The Contractor shall comply with “508 Chapter 2: Scoping Requirements” for all electronic ICT and content delivered under this contract. Specifically, as appropriate for the technology and its functionality, the Contractor shall comply with the technical standards marked here:

2.2 COMPATABILITY WITH ASSISTIVE TECHNOLOGY

The standards do not require installation of specific accessibility-related software or attachment of an assistive technology device. Section 508 requires that ICT be compatible with such software and devices so that ICT can be accessible to and usable by individuals using assistive technology, including but not limited to screen readers, screen magnifiers, and speech recognition software.

2.3 ACCEPTANCE AND ACCEPTANCE TESTING

Deliverables resulting from this solicitation will be accepted based in part on satisfaction of the Section 508 Chapter 2: Scoping Requirements standards identified above.

The Government reserves the right to test for Section 508 Compliance before delivery. The Contractor shall be able to demonstrate Section 508 Compliance upon delivery.

3.0 INFORMATION TECHNOLOGY USING ENERGY-EFFICIENT PRODUCTS

3.1 EPEAT

EPEAT product compliance is not required in this acquisition.

3.2 ENERGY STAR

Energy Star compliance is not required in this acquisition.

3.3 FEMP

FEMP or FEMP low standby power product compliance is not required in this acquisition.

4.0 SHIPMENT OF HARDWARE OR EQUIPMENT

Electronic delivery to:

Primary

Alternate

5.0 GENERAL REQUIREMENTS

5.1 VA TECHNICAL REFERENCE MODEL

The Contractor shall support the VA enterprise management framework. In association with the framework, the Contractor shall comply with OIT Technical Reference Model (VA TRM). The VA TRM is one component within the overall Enterprise Architecture (EA) that establishes a common vocabulary and structure for describing the information technology used to develop, operate, and maintain enterprise applications. Moreover, the VA TRM, which includes the Standards Profile and Product List, serves as a technology roadmap and tool for supporting OIT. Architecture & Engineering Services (AES) has overall responsibility for the VA TRM.

5.2 ZERO TRUST – VA CRITICAL SECURITY CONTROLS

VA has established minimum mandatory security requirements and requires that any network connected software system or service must meet the VA Critical Security Controls as outlined in the VA Memorandum, “VA Security Controls”, https://www.voa.va.gov/DocumentView.aspx?DocumentID=5010. VA Critical Security Controls identify the minimum mandatory requirements that must be implemented across all VA enterprise infrastructure, cloud computing environments, information systems, networks, and specialized devices (medical devices/systems, special-purpose systems, and research scientific computing devices) that process, store, and/or transmit VA data. Effective July 1, 2025, the Contractor shall implement these VA Critical Security Controls, within any network connected software system or service prior to being authorized for use in the VA. This functional requirement is not negotiable, and Plan of Action & Milestones (POAM) will not be accepted in the event these controls cannot be implemented for new systems. Critical Security Controls are intended to increase VA’s security posture and provide security and privacy risk visibility into the VA network and is not a new requirement. The Contractor’s failure to maintain these VA Critical Controls after implementation will result in VA discontinuing the use of the system.

5.3 SOCIAL SECURITY NUMBER (SSN) REDUCTION

The Contractor solution shall support the Social Security Number (SSN) Fraud Prevention Act (FPA) of 2017 which prohibits the inclusion of SSNs on any document sent by mail. The Contractor support shall also be performed in accordance with Section 240 of the Consolidated Appropriations Act (CAA) 2018, enacted March 23, 2018, which mandates VA to discontinue using SSNs to identify individuals in all VA information systems as the Primary Identifier. The Contractor shall ensure that any new IT solution discontinues the use of SSN as the Primary Identifier to replace the SSN with the Integrated Control Number (ICN) in all VA information systems for all individuals. The Contractor shall ensure that all Contractor delivered applications and systems integrate with the VA Master Person Index (MPI) for identity traits to include the use of the ICN as the Primary Identifier. The Contractor solution may only use a Social Security Number to identify an individual in an information system if and only if the use of such number is required to obtain information VA requires from an information system that is not under the jurisdiction of VA.

5.4 INTERNET PROTOCOL VERSION 6 (IPV6)

The Contractor solution shall support Internet Protocol Version 6 (IPv6) based upon the memo issued by the Office of Management and Budget (OMB) on November 19, 2020 (https://www.whitehouse.gov/wp-content/uploads/2020/11/M-21-07.pdf). IPv6 technology, in accordance with the USGv6 Program (https://www.nist.gov/programs-projects/usgv6-program/usgv6-revision-1), NIST Special Publication (SP) 500-267B Revision 1 “USGv6 Profile” (https://doi.org/10.6028/NIST.SP.500-267Br1), and NIST SP 800-119 “Guidelines for the Secure Deployment of IPv6” (https://doi.org/10.6028/NIST.SP.800-119), compliance shall be included in all IT infrastructures, application designs, application development, operational systems and sub-systems, and their integration. In addition to the above requirements, all devices shall support native IPv6 and dual stack (IPv6 / IPv4) connectivity without additional memory or other resources being provided by the Government, so that they can function in a mixed environment. All public/external facing servers and services (e.g. web, email, DNS, ISP services, etc.) shall support native IPv6 and dual stack (IPv6 / IPv4) users and all internal infrastructure and applications shall communicate using native IPv6 and dual stack (IPv6 / IPv4) operations.

5.5 SOFTWARE AND LICENSING REQUIREMENTS

The Contractor shall be responsible for the provision of all software licenses and any associated licensing maintenance required for any development, delivery, integration, operation, and/or maintenance associated with its proposed application(s), software products, software solution, and/or system including, but not limited to, any and all application(s), software and/or software products that comprise, are a part of, or integrate with the Contractor’s proposed application(s), software products, software solution, and/or system for the life of any resulting contract.

5.6 TRUSTED INTERNET CONNECTION (TIC)

The Contractor solution shall meet the requirements outlined in Office of Management and Budget Memorandum M-19-26, “Update to the Trusted Internet Connections (TIC) Initiative“ (https://www.whitehouse.gov/wp-content/uploads/2019/09/M-19-26.pdf), VA Directive 6513 “Secure External Connections”, and shall comply with the TIC 3.0 Core Guidance Documents, including all Volumes and TIC Use Cases, found at the Cybersecurity & Infrastructure Security Agency (CISA) (https://www.cisa.gov/publication/tic-30-core-guidance-documents.)

6.0 POINTS OF CONTACT

VA Program Manager:

Contracting Officer’s Representative:

7.0 ADDITIONAL ITEMS

7.1 INFORMATION SECURITY CONSIDERATIONS

The assessment and authorization (A&A) requirements do not apply, and a Security Accreditation Package is not required.

All VA sensitive information shall be protected at all times in accordance with local security field office System Security Plans (SSP’s) and Authority to Operate (ATO)’s for all systems/LAN’s accessed while performing the tasks detailed in this Product Description.

a. A prohibition on unauthorized disclosure: “Information made available to the Contractor or Subcontractor by VA for the performance or administration of this contract or information developed by the Contractor/Subcontractor in performance or administration of the contract shall be used only for those purposes and shall not be used in any other way without the prior written agreement of the VA.” This clause expressly limits the Contractor/Subcontractor’s rights to use data as described in Rights in Data – General, FAR 52.227-14(d).(1).

b. A requirement for data breach notification: Upon discovery of any known or suspected security/privacy incidents, or any unauthorized disclosure of sensitive information, including that contained in system(s) to which the Contractor/Subcontractor has access, the Contractor/Subcontractor shall immediately notify the COR and simultaneously, the designated ISO, and Privacy Officer for the contract. The term “security incident” means an event that has, or could have, resulted in unauthorized access to, loss or damage to VA assets, or sensitive information, or an action that breaches VA security procedures. See VA Handbook 6500.6, Appendix C, paragraph 6.a.

c. A requirement to pay liquidated damages in the event of a data breach: “In the event of a data breach or privacy incident involving SPI the contractor processes or maintains under this contract, the contractor shall be liable to VA for liquidated…