RFP 36C10B23R0007.pdf

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

36C10B23R0007 12-08-2022

James Cummiskey – Contract Specialist 848-377-5117 12-15-2022

1:00 PM EST

Department of Veterans Affairs

Technology Acquisition Center

23 Christopher Way

Eatontown NJ 07724

X

541513

$32.5 Million

N/A

X

See Section B.

Department of Veterans Affairs

Technology Acquisition Center

23 Christopher Way

Eatontown NJ 07724

See Section B.1 Contract Administration

Data

Laboratory System Reengineering Project (LSRP) Remote

Hosting, Maintenance, and Sustainment.

Period of Performance: 1/1/2023 - 12/31/2023 with two (2)

12-month option periods.

Points of Contact:

James Cummiskey, Contract Specialist

James.Cummiskey@va.gov 848-377-5117

Heather Utt, Contracting Officer

Heather.Utt@va.gov 848-377-5047

X X

Heather Utt

Contracting Officer

36C10B23R0007

Table of Contents

SECTION A .................................................................................... Error! Bookmark not defined.

A.1 SF 1449 SOLICITATION/CONTRACT/ORDER FOR COMMERCIAL PRODUCTS

AND COMMERCIAL SERVICES ..................................... Error! Bookmark not defined.

SECTION B - CONTINUATION OF SF 1449 BLOCKS

B.1 CONTRACT ADMINISTRATION DATA

B.2 GOVERNING LAW CLAUSE

B.3 SOFTWARE LICENSE, MAINTENANCE, AND TECHNICAL SUPPORT

B.4 PRICE SCHEDULE

B.5 PERFORMANCE WORK STATEMENT

SECTION C - CONTRACT CLAUSES

C.1 52.252-2 CLAUSES INCORPORATED BY REFERENCE (FEB 1998)

C.2 52.204-21 BASIC SAFEGUARDING OF COVERED CONTRACTOR

INFORMATION SYSTEMS (NOV 2021)

C.3 52.212-5 CONTRACT TERMS AND CONDITIONS REQUIRED TO IMPLEMENT

STATUTES OR EXECUTIVE ORDERS—COMMERCIAL PRODUCTS AND

COMMERCIAL SERVICES (OCT 2022)

C.5 52.217-8 OPTION TO EXTEND SERVICES (NOV 1999)

C.6 52.217-9 OPTION TO EXTEND THE TERM OF THE CONTRACT (MAR 2000)

C.7 VAAR 852.212-70 PROVISIONS AND CLAUSES APPLICABLE TO VA

ACQUISITION OF COMMERCIAL ITEMS (APR 2020)

SECTION D - CONTRACT DOCUMENTS, EXHIBITS, OR ATTACHMENTS

SECTION E - SOLICITATION PROVISIONS

E.1 52.252-1 SOLICITATION PROVISIONS INCORPORATED BY REFERENCE (FEB

1998)

E.2 52.204-24 REPRESENTATION REGARDING CERTAIN TELECOMMUNICATIONS

AND VIDEO SURVEILLANCE SERVICES OR EQUIPMENT (NOV 2021)

E.3 52.204-26 COVERED TELECOMMUNICATIONS EQUIPMENT OR SERVICES—

REPRESENTATION (OCT 2020)

E.4 52.209-7 INFORMATION REGARDING RESPONSIBILITY MATTERS (OCT 2018)

E.5 52.212-3 OFFEROR REPRESENTATIONS AND CERTIFICATIONS—

COMMERCIAL PRODUCTS AND COMMERCIAL SERVICES (OCT 2022)

E.6 52.216-1 TYPE OF CONTRACT (APR 1984)

E.7 52.233-2 SERVICE OF PROTEST (SEP 2006)

E.8 BASIS FOR AWARD AND PROPOSAL SUBMISSION INSTRUCTIONS

SECTION B - CONTINUATION OF SF 1449 BLOCKS

B.1 CONTRACT ADMINISTRATION DATA

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

a. CONTRACTOR: TBD

b. GOVERNMENT: Contracting Officer 36C10B, Heather Utt/heather.utt@va.gov

Department of Veterans Affairs Technology Acquisition Center 23 Christopher Way Eatontown NJ 07724

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

[X] 52.232-33, Payment by Electronic Funds Transfer—System For Award Management, or

[] 52.232-36, Payment by Third Party

3. INVOICES: Invoices shall be submitted in arrears:

a. Quarterly []

b. Semi-Annually []

c. Other [X] Upon receipt and acceptance of deliverables IAW Section B Price Schedule.

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.

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

AMENDMENT NO DATE

B.2 GOVERNING LAW CLAUSE

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, as permitted by FAR 12.212. 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 U.S.C. § 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. The Contractor shall deliver to the Government all data first produced under this Contract/Order with unlimited rights as defined by FAR 52.227-14. Claims of patent or copyright infringement brought against the Government as a party shall be defended by the U.S.

Department of Justice (DOJ) in accordance with 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 modification

(Standard Form 30) and shall only be made 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.3 SOFTWARE LICENSE, MAINTENANCE, AND TECHNICAL SUPPORT

(1). Definitions.

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

b) 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 Contract/Order.

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

d) 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.

e) 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.

f) 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.

g) 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).

(2). Software License.

a) 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.

b) The Government may use the software in a networked environment.

c) 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).

d) All limitations of software usage are expressly stated in the Schedule of

Supplies/Services and the Performance Work Statement/Product Description.

(3). Software Maintenance and/or Technical Support.

a) If the Government desires to continue software maintenance and support beyond the period of performance identified in this Contract/Order, the Government will issue a separate contract or order for maintenance and support. Conversely, if a contract or order for continuing software maintenance and technical support is not received, the Contractor is neither authorized nor permitted to renew any of the previously furnished services.

b) The Contractor shall provide software support services, which includes periodic updates, enhancements and corrections to the software, and reasonable technical support, all of which are customarily provided by the Contractor to its commercial customers to cause the software to perform according to its specifications, documentation or demonstrated claims.

c) Any telephone support provided by Contractor shall be at no additional cost.

d) The Contractor shall provide all maintenance services in a timely manner in accordance with the Contractor’s customary practice or as defined in the Performance Work Statement or Product Description. However, prolonged delay (exceeding two business days) in resolving software problems will be noted in the Government’s various past performance records on the Contractor (e.g., www.cpars.gov).

e) If the Government allows the maintenance and support to lapse and subsequently wishes to reinstate it, any reinstatement fee charged shall not exceed the amounts that would have been charged if the Government had not allowed the subscription to lapse.

(4). 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.

(5). 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/Order at no cost.

B.4 PRICE SCHEDULE

BASE PERIOD

Period of Performance: January 1, 2023-December 31, 2023

LINE

ITEM

DESCRIPTION

QTY

UNIT

PRICE

TOTAL

0001 Project Management in accordance with (IAW) Performance Work Statement (PWS) paragraphs 5.1 and all sub-paragraphs.

This CLIN includes all labor, supplies, and reports required for the successful completion of the services.

The price of this CLIN shall be amortized throughout the priced line items.

12 MO NSP NSP

0001AA Monthly Progress and 508 Compliance

Report IAW PWS paragraph 5.1.1

Due 30 days after award and updated by the 15th of each month thereafter.

Electronic submission to: COR

EA

NSP

0001AB Meeting Agenda IAW PWS paragraph 5.1.2.

Due 5th day of each month throughout the

PoP.

Electronic submission to: COR

12 EA NSP NSP

0002 Site Maintenance and Software Support IAW PWS paragraph 5.2.

This CLIN includes all labor, supplies, and reports required for the successful completion of the services. 12 MO $ $

0002AA Quarterly LSRP software review and updates report IAW PWS paragraph 5.2

No longer than every 90 days

Evidence of: Software Support for Cerner PathNet LSRP implementation

Evidence of: Software Maintenance Support for Cerner PathNet LSRP implementation

Electronic submission to: COR 4 EA NSP NSP

0003 Remote Hosting of the LSRP Product IAW PWS paragraph 5.3 and all sub-paragraphs.

This CLIN includes all labor, supplies, and reports required for the successful completion of the services. 12 MO $ $

0004 Full Hardware and Software Disaster Recovery (DR) Support IAW PWS paragraph 5.4.

This CLIN includes all labor, supplies, and completion of the services.

MO

0005 System Security IAW PWS paragraph 5.5 and all sub-paragraphs.

This CLIN includes all labor, supplies, and

0005AA A&A Artifact Package IAW PWS paragraph 5.5

Due 30 days after award

No longer than every 90 days

Electronic submission to: COR 4 EA NSP NSP

0005AB FIPS Security Certificates IAW PWS paragraph 5.5.1

Due 30 days after award

Electronic submission to: COR 1 EA NSP NSP

0006 Application Support Requirements IAW PWS paragraph 5.6 and all sub-paragraphs

This CLIN includes all labor, supplies, and reports required for the successful completion of the services. 12 MO $ $

0006AA Quarterly test plan IAW PWS paragraph 5.6.1

Due 30 days after award, updates no longer than every 90 days

Electronic submission to: COR 4 EA NSP NSP

0006AB Weekly maintenance report IAW PWS paragraph 5.6.3

Due 5th day of each week throughout the PoP.

Electronic submission to: COR 52 EA NSP NSP

0007 Software Maintenance Upgrades Continuous Integration and Continuous Delivery (CICD) IAW PWS paragraph 5.7 and all sub-paragraphs.

This CLIN includes all labor, supplies, and reports required for the successful completion of the services. 12 MO $ $

0007AA Test Plans IAW PWS paragraph 5.7.2.2

Due 30 days after award, updates no longer than every 90 days

Electronic submission to: COR 4 EA NSP NSP

0007AB Testing Execution Summary and Test Results IAW PWS paragraph 5.7.2.2

Due 30 days after award, updates no longer than every 90 days

Electronic submission to: COR 4 EA NSP NSP

0007AC Testing Finding/Results (Contractor Format) IAW PWS paragraph 5.7.2.2

Due 30 days after award, updates no longer than every 90 days

0007AD Quarterly Updated Training Documents and Materials IAW PWS paragraph 5.7.4

Due 30 days after award, updates no longer than every 90 days

Electronic submission to: COR 4 EA NSP NSP

Total Base Period

OPTION PERIOD ONE (1) This option may be exercise in accordance with FAR 52.217-9

Option to Extend the Term of the Contract.

POP: January 1, 2024-December 31, 2024

LINE

1001 Project Management in accordance with (IAW) Performance Work Statement (PWS) paragraphs 5.1 and all sub-paragraphs.

This CLIN includes all labor, supplies, and reports required for the successful completion of the services.

The price of this CLIN shall be amortized throughout the priced line items.

12 MO NSP NSP

1001AA Monthly Progress and 508 Compliance

Report IAW PWS paragraph 5.1.1

Due 30 days after award and updated by

1001AB Meeting Agenda IAW PWS paragraph 5.1.2.

Due 5th day of each month throughout the

PoP.

12 EA NSP NSP

1002 Site Maintenance and Software Support IAW PWS paragraph 5.2.

This CLIN includes all labor, supplies, and reports required for the successful completion of the services. 12 MO $ $

1002AA Quarterly LSRP software review and updates report IAW PWS paragraph 5.2

No longer than every 90 days.

Evidence of: Software Support for Cerner PathNet LSRP implementation

Cerner PathNet LSRP implementation

1003 Remote Hosting of the LSRP Product IAW PWS paragraph 5.3 and all sub-paragraphs.

This CLIN includes all labor, supplies, and reports required for the successful completion of the services. 12 MO $ $

1004 Full Hardware and Software Disaster Recovery (DR) Support IAW PWS paragraph 5.4.

This CLIN includes all labor, supplies, and

1005 System Security IAW PWS paragraph 5.5 and all sub-paragraphs.

This CLIN includes all labor, supplies, and

1005AA A&A Artifact Package IAW PWS paragraph 5.5

Due 30 days after award, updates no longer than every 90 days.

1005AB FIPS Security Certificates IAW PWS paragraph 5.5.1

Due 30 days after award.

Electronic submission to: COR 1 EA NSP NSP

1006 Application Support Requirements IAW PWS paragraph 5.6 and all sub-paragraphs.

This CLIN includes all labor, supplies, and reports required for the successful completion of the services. 12 MO $ $

1006AA Quarterly test plan IAW PWS paragraph 5.6.1

Due 30 days after award, updates no longer than every 90 days.

Electronic submission to: COR 4 EA NSP NSP

1006AB Weekly maintenance report IAW PWS paragraph 5.6.3

Due 5th day of each week throughout the PoP.

Electronic submission to: COR 52 EA NSP NSP

1007 Software Maintenance Upgrades Continuous Integration and Continuous Delivery (CICD) IAW PWS paragraph 5.7 and all sub-paragraphs.

This CLIN includes all labor, supplies, and reports required for the successful completion of the services. 12 MO $ $

1007AA Test Plans IAW PWS paragraph 5.7.2.2

Due 30 days after award, updates no longer than every 90 days.

Electronic submission to: COR 4 EA NSP NSP

1007AB Testing Execution Summary and Test Results IAW PWS paragraph 5.7.2.2

Due 30 days after award, updates no longer

1007AC Testing Finding/Results (Contractor Format) IAW PWS paragraph 5.7.2.2

Due 30 days after award, updates no longer than every 90 days.

Electronic submission to: COR 4 EA NSP NSP

1007AD Quarterly Updated Training Documents and Materials IAW PWS paragraph 5.7.4

Due 30 days after award, updates no longer than every 90 days.

Electronic submission to: COR 4 EA NSP NSP

Total Option Period One

OPTION PERIOD TWO (2)

This option may be exercise in accordance with FAR 52.217-9 Option to Extend the Term of the Contract.

POP: January 1, 2025-December 31, 2025

LINE

2001 Project Management in accordance with (IAW) Performance Work Statement (PWS) paragraphs 5.1 and all sub-paragraphs.

This CLIN includes all labor, supplies, and reports required for the successful completion of the services.

The price of this CLIN shall be amortized throughout the priced line items.

12 MO NSP NSP

2001AA Monthly Progress and 508 Compliance

Report IAW PWS paragraph 5.1.1

Due 30 days after award and updated by

2001AB Meeting Agenda IAW PWS paragraph 5.1.2.

Due 5th day of each month throughout the

PoP.

Electronic submission to: COR

12 EA NSP NSP

2002 Site Maintenance and Software Support IAW PWS paragraph 5.2.

This CLIN includes all labor, supplies, and reports required for the successful completion of the services. 12 MO $ $

2002AA Quarterly LSRP software review and updates report IAW PWS paragraph 5.2

No longer than every 90 days.

Evidence of: Software Support for Cerner PathNet LSRP implementation.

Cerner PathNet LSRP implementation.

2003 Remote Hosting of the LSRP Product IAW PWS paragraph 5.3 and all sub-paragraphs.

This CLIN includes all labor, supplies, and reports required for the successful completion of the services. 12 MO $ $

2004 Full Hardware and Software Disaster Recovery (DR) Support IAW PWS paragraph 5.4.

This CLIN includes all labor, supplies, and

2005 System Security IAW PWS paragraph 5.5 and all sub-paragraphs.

This CLIN includes all labor, supplies, and

2005AA A&A Artifact Package IAW PWS paragraph 5.5

Due 30 days after award, updates no longer than every 90 days.

Electronic submission to: COR 4 EA NSP NSP

2005AB FIPS Security Certificates IAW PWS paragraph 5.5.1

Due 30 days after award

Electronic submission to: COR 1 EA NSP NSP

2006 Application Support Requirements IAW PWS paragraph 5.6 and all sub-paragraphs.

This CLIN includes all labor, supplies, and reports required for the successful completion of the services. 12 MO $ $

2006AA Quarterly test plan IAW PWS paragraph 5.6.1

Due 30 days after award, updates no longer than every 90 days.

Electronic submission to: COR 4 EA NSP NSP

2006AB Weekly maintenance report IAW PWS paragraph 5.6.3

Due 5th day of each week throughout the PoP.

Electronic submission to: COR 52 EA NSP NSP

2007 Software Maintenance Upgrades Continuous Integration and Continuous Delivery (CICD) IAW PWS paragraph 5.7 and all sub-paragraphs.

This CLIN includes all labor, supplies, and reports required for the successful completion of the services. 12 MO $ $

2007AA Test Plans IAW PWS paragraph 5.7.2.2

Due 30 days after award, updates no longer

B.5 PERFORMANCE WORK STATEMENT

1.0 BACKGROUND

The Department of Veterans Affairs (VA), Office of Information & Technology (OIT), Software Product Management (SPM), Health Services Portfolio, Clinical Services strives to provide high quality, effective, and efficient Information Technology (IT) services to those responsible for providing care to the Veterans at the point-of-care as well as throughout all the points of the Veterans’ health care in an effective, timely and compassionate manner. VA depends on Information Management/Information Technology (IM/IT) systems to meet mission goals.

In Fiscal Year (FY) 2008, The Department of Veterans Affairs (VA) Office of Information and Technology (OI&T) Laboratory System Re-engineering Project (LSRP) selected the Cerner PathNet solution for the Huntington, West Virginia Medical Center (referred to as the Alpha site). The Cerner PathNet Commercial Off-The-Shelf (COTS) application is interfaced with VistA and other VA systems. The LSRP Product provides the principal medical diagnostic laboratory testing functionality for the VA; the results of which are significant drivers in clinical decision making.

2007AB Testing Execution Summary and Test Results IAW PWS paragraph 5.7.2.2

Due 30 days after award, updates no longer than every 90 days.

Electronic submission to: COR 4 EA NSP NSP

2007AC Testing Finding/Results (Contractor Format) IAW PWS paragraph 5.7.2.2

Due 30 days after award, updates no longer than every 90 days.

Electronic submission to: COR 4 EA NSP NSP

2007AD Quarterly Updated Training Documents and Materials IAW PWS paragraph 5.7.4

Due 30 days after award, updates no longer than every 90 days.

Electronic submission to: COR 4 EA NSP NSP

Total Option Period Two

Total Base Period plus Options

2.0 APPLICABLE DOCUMENTS

In the performance of the tasks associated with this Performance Work Statement, the Contractor shall comply with the following:

1. 44 U.S.C. § 3541-3549, “Federal Information Security Management Act (FISMA) of 2002”

2. “Federal Information Security Modernization Act of 2014”

3. Federal Information Processing Standards (FIPS) Publication 140-2, “Security Requirements for Cryptographic Modules”

4. FIPS Pub 199. “Standards for Security Categorization of Federal Information and Information Systems,” February 2004

5. FIPS Pub 200, “Minimum Security Requirements for Federal Information and

Information Systems,” March 2006

6. FIPS Pub 201-2, “Personal Identity Verification of Federal Employees and

Contractors,” August 2013

7. 10 U.S.C. § 2224, "Defense Information Assurance Program"

8. 5 U.S.C. § 552a, as amended, “The Privacy Act of 1974”

9. Public Law 109-461, Veterans Benefits, Health Care, and Information

Technology Act of 2006, Title IX, Information Security Matters

10. 42 U.S.C. § 2000d “Title VI of the Civil Rights Act of 1964”

11. VA Directive 0710, “Personnel Security and Suitability Program,” June 4, 2010, https://www.va.gov/vapubs/index.cfm

12. VA Handbook 0710, “Personnel Security and Suitability Program,” May 2, 2016, https://www.va.gov/vapubs/index.cfm

13. VA Directive and Handbook 6102, “Internet/Intranet Services,” August 5,

14. 36 C.F.R. Part 1194 “Information and Communication Technology Standards and Guidelines,” January 18, 2017

15. Office of Management and Budget (OMB) Circular A-130, “Managing Federal

Information as a Strategic Resource,” July 28, 2016

16. 32 C.F.R. Part 199, “Civilian Health and Medical Program of the Uniformed

Services (CHAMPUS)”

17. NIST SP 800-66 Rev. 1, “An Introductory Resource Guide for Implementing the Health Insurance Portability and Accountability Act (HIPAA) Security Rule,” October 2008

18. Sections 504 and 508 of the Rehabilitation Act (29 U.S.C. § 794d), as amended, January 18, 2017

19. Homeland Security Presidential Directive (12) (HSPD-12), August 27, 2004

20. VA Directive 6500, “VA Cybersecurity Program,” February 24, 2021

21. VA Handbook 6500, “Risk Management Framework for VA Information

Systems VA Information Security Program,” February 24, 2021

22. VA Handbook 6500.2, “Management of Breaches Involving Sensitive

Personal Information (SPI),” March 12, 2019

23. VA Handbook 6500.5, “Incorporating Security and Privacy into the System

Development Lifecycle,” March 22, 2010

24. VA Handbook 6500.6, “Contract Security,” March 12, 2010

25. VA Handbook 6500.8, “Information System Contingency Planning,” April 6,

26. VA Handbook 6500.10, “Mobile Device Security Policy,” February 15, 2018 https://www.va.gov/vapubs/index.cfm https://www.va.gov/vapubs/index.cfm http://www.va.gov/vapubs http://www.va.gov/vapubs

27. VA Handbook 6500.11, “VA Firewall Configuration,” August 22, 2017

28. OIT Process Asset Library (PAL), https://www.va.gov/process/ . Reference

Process Maps at https://www.va.gov/process/maps.asp and Artifact templates at https://www.va.gov/process/artifacts.asp

29. One-VA Technical Reference Model (TRM) (reference at https://www.va.gov/trm/TRMHomePage.aspx)

30. VA Directive 6508, “Implementation of Privacy Threshold Analysis and Privacy Impact Assessment,” October 15, 2014

31. VA Handbook 6508.1, “Procedures for Privacy Threshold Analysis and Privacy Impact Assessment,” July 30, 2015

32. VA Handbook 6510, “VA Identity and Access Management,” January 15,

33. VA Directive and Handbook 6513, “Secure External Connections,” October 12, 2017

34. VA Directive 6300, “Records and Information Management,” September 21,

35. VA Handbook, 6300.1, “Records Management Procedures,“ March 24, 2010

36. NIST SP 800-37 Rev 2, “Risk Management Framework for Information

Systems and Organizations: A System Life Cycle Approach for Security and Privacy,” December 2018

37. NIST SP 800-53 Rev. 5, “Security and Privacy Controls for Federal Information Systems and Organizations,” September 23, 2020 (includes updates as of 12/10/2020)

38. VA Directive 0735, “Homeland Security Presidential Directive 12 (HSPD-12) Program,” October 26, 2015

39. VA Handbook 0735, “Homeland Security Presidential Directive 12 (HSPD-

12) Program,” March 24, 2014

40. OMB Memorandum 05-24, “Implementation of Homeland Security Presidential Directive (HSPD) 12 – Policy for a Common Identification Standard for Federal Employees and Contractors,” August 5, 2005

41. OMB Memorandum M-19-17, “Enabling Mission Delivery Through Improved Identity, Credential, and Access Management,” May 21, 2019

42. OMB Memorandum, “Guidance for Homeland Security Presidential Directive (HSPD) 12 Implementation,” May 23, 2008

43. Federal Identity, Credential, and Access Management (FICAM) Roadmap and Implementation Guidance, December 2, 2011, (NOTE: Part A of the FICAM Roadmap and Implementation Guidance, v2.0, was replaced in 2015 with an updated Architecture (https://arch.idmanagement.gov/#what-is-the-ficam-architecture)

44. NIST SP 800-116 Rev 1, “Guidelines for the Use of Personal Identity Verification (PIV) Credentials in Facility Access,“ June 2018

45. NIST SP 800-63-3, 800-63A, 800-63B, 800-63C, “Digital Identity Guidelines,” updated March 02, 2020

46. NIST SP 800-157, “Guidelines for Derived PIV Credentials,” December 2014

47. NIST SP 800-164, “Guidelines on Hardware-Rooted Security in Mobile

Devices (Draft),” October 2012

48. Draft National Institute of Standards and Technology Interagency Report

(NISTIR) 7981, “Mobile, PIV, and Authentication,” March 2014 https://www.va.gov/process/ https://www.va.gov/process/maps.asp https://www.va.gov/process/artifacts.asp https://www.va.gov/trm/TRMHomePage.aspx https://arch.idmanagement.gov/#what-is-the-ficam-architecture https://arch.idmanagement.gov/#what-is-the-ficam-architecture

49. VA Memorandum, VAIQ #7100147, “Continued Implementation of Homeland Security Presidential Directive 12 (HSPD-12),” April 29, 2011 (reference https://www.voa.va.gov/documentlistpublic.aspx?NodeID=514)

50. IAM Identity Management Business Requirements Guidance document, May 2013, (reference Enterprise Architecture Section, PIV/IAM (reference https://www.voa.va.gov/documentlistpublic.aspx?NodeID=514)

51. VA Memorandum “Personal Identity Verification (PIV) Logical Access Policy Clarification,” July 17, 2019, https://www.voa.va.gov/DocumentView.aspx?DocumentID=4896

52. Trusted Internet Connections (TIC) 3.0 Core Guidance Documents, https://www.cisa.gov/publication/tic-30-core-guidance-documents

53. OMB Memorandum M-19-26, “Update to the Trusted Internet Connections (TIC) Initiative,” September 12, 2019

54. OMB Memorandum M-08-23, “Securing the Federal Government’s Domain Name System Infrastructure,” August 22, 2008

55. Sections 524 and 525 of the Energy Independence and Security Act of 2007, (Public Law 110–140), December 19, 2007

56. Section 104 of the Energy Policy Act of 2005, (Public Law 109–58), August 8, 2005

57. Executive Order 13834, “Efficient Federal Operations,” dated May 17, 2018

58. Executive Order 13221, “Energy-Efficient Standby Power Devices,” August

2, 2001

59. VA Directive 0058, “VA Green Purchasing Program,” July 19, 2013

60. VA Handbook 0058, “VA Green Purchasing Program,” July 19, 2013

61. Office of Information Security (OIS) VAIQ #7424808 Memorandum, “Remote

Access,” January 15, 2014, https://www.voa.va.gov/DocumentListPublic.aspx?NodeId=28

62. Clinger-Cohen Act of 1996, 40 U.S.C. §11101 and §11103

63. “Veteran Focused Integration Process (VIP) Guide 4.0,” January 2021, https://www.voa.va.gov/DocumentView.aspx?DocumentID=4371

64. VA Memorandum “Proper Use of Email and Other Messaging Services,”

January 2, 2018, https://www.voa.va.gov/DocumentListPublic.aspx?NodeId=28

65. “DevSecOps Product Line Management Playbook” version 2.0, May 2021, https://www.voa.va.gov/DocumentView.aspx?DocumentID=4946

66. NIST SP 500-267B Revision 1, “USGv6 Profile,” November 2020

67. OMB Memorandum M-21-07, “Completing the Transition to Internet Protocol

Version 6 (IPv6),” November 19, 2020

68. Social Security Number (SSN) Fraud Prevention Act of 2017

69. Section 240 of the Consolidated Appropriations Act (CAA) 2018, March 23,

3.0 SCOPE OF WORK

The Contractor shall maintain the Cerner PathNet LSRP implementation, heretofore known as LSRP, for the Huntington LSRP Alpha site. This task shall provide the following capabilities and services:

1. LSRP monthly status and on-boarding reports, and

2. LSRP remote hosting and maintenance, and https://www.voa.va.gov/documentlistpublic.aspx?NodeID=514 https://www.voa.va.gov/documentlistpublic.aspx?NodeID=514 https://www.voa.va.gov/DocumentView.aspx?DocumentID=4896 https://www.cisa.gov/publication/tic-30-core-guidance-documents https://www.voa.va.gov/DocumentListPublic.aspx?NodeId=28 https://www.voa.va.gov/DocumentView.aspx?DocumentID=4371 https://www.voa.va.gov/DocumentListPublic.aspx?NodeId=28 https://www.voa.va.gov/DocumentView.aspx?DocumentID=4946

3. LSRP disaster recovery implementation and support, and

4. LSRP technical support (24/7/365), and

5. LSRP cyber security implementation and maintenance per VA Authority to

Operate requirements, and

6. LSRP network and application support, and

7. LSRP testing, capacity planning, and operations & maintenance support.

4.0 PERFORMANCE DETAILS

4.1 PERFORMANCE PERIOD

The Period of Performance (PoP) shall be a 12-month base period commencing on 1/1/2023 with two (2) 12-month option periods.

There are eleven (11) Federal holidays set by law (USC Title 5 Section 6103) that VA follows:

Under current definitions, five are set by date:

New Year's Day January 1 Juneteenth June 19 Independence Day July 4 Veterans Day November 11 Christmas Day December 25

If any of the above falls on a Saturday, then Friday shall be observed as a holiday.

Similarly, if one falls on a Sunday, then Monday shall be observed as a holiday.

The other six are set by a day of the week and month:

Martin Luther King's Birthday Third Monday in January Washington's Birthday Third Monday in February Memorial Day Last Monday in May Labor Day First Monday in September Columbus Day Second Monday in October Thanksgiving Fourth Thursday in November

4.2 PLACE OF PERFORMANCE

Tasks under this PWS shall be performed at Contractor facilities. The Contractor shall identify the Contractor’s place of performance in their proposal submission.

4.3 TRAVEL

Travel is not anticipated for this contractual agreement. If the government determines travel is necessary, a modification will be issued by the Contracting Officer. If added via modification, travel shall be in accordance with the Federal Travel Regulations (FTR) and requires advanced concurrence by the COR. Contractor travel within the local commuting area will not be reimbursed.

5.0 SPECIFIC TASKS AND DELIVERABLES

The Contractor shall perform the following:

5.1 PROJECT MANAGEMENT

5.1.1 MONTHLY PROGRESS REPORT

The Contractor shall provide the Contracting Officer Representative (COR)/VA Program

Manager (PM) with Monthly Progress Reports in electronic form in Microsoft Word and/or PostScript Document Format (PDF) formats. The report shall include detailed instructions/explanations for each required data element, to ensure that data is accurate and consistent. These reports shall reflect data as of the last day of the preceding month.

The Monthly Progress Reports shall cover all work completed during the reporting period and work planned for the subsequent reporting period. The report shall also identify any problems that arose and a description of how the problems were resolved.

This includes any disaster recovery efforts detailing what happened, how it was fixed and the remaining issues. If problems have not been completely resolved, the

Contractor shall provide an explanation including their plan and timeframe for resolving the issue. The report shall also include an itemized list of all Electronic and Information

Technology (EIT) deliverables and their current Section 508 conformance status. The

Contractor shall monitor performance against the Contractor Performance and

Management Plan (CPMP) and report any deviations. The Monthly Progress Report shall also include updates for Application Support Requirements (PWS paragraph 5.6).

The Contractor shall keep in communication with VA accordingly so that issues that arise are transparent to both parties to prevent escalation of outstanding issues.

The Contractor shall meet with the COR/VA PM weekly (via a conference call) to review project team information requests and shall track this activity in the Monthly Progress

Report.

Deliverable:

A. Monthly Progress and 508 compliance Report.

5.1.2 TECHNICAL KICKOFF MEETING

The Contractor shall hold a technical meeting within 10-days of contract award. The

Contractor shall present, for review and approval by the Government, the details of the intended approach, work plan, and project schedule. The Contractor shall specify dates, locations (can be virtual), agenda (shall be provided to all attendees at least five calendar days prior to the meeting), and meeting minutes (shall be provided to all attendees within three calendar days after the meeting). The Contractor shall invite the

Contracting Officer (CO), Contract Specialist, COR, and the VA PM.

A. Meeting Agenda.

5.1.3 COMPLIANCE REVIEWS AND AUDITS

The Contractor shall provide the required services outlined in the tasks below based on applicable federal and VA regulations. However, new federal laws as well as VA regulations, including, but not limited to, U.S. Food and Drug Administration regulations and U.S. Centers for Medicare & Medicaid Services regulations may arise during the performance of this effort that may require compliance by the Contractor in order to keep VA in compliance. To maintain such compliance, the Contractor and/or VA may require changes to existing technology or the implementation of new technology (e.g., hardware, storage, network, database, tools, etc.). As a result, the Contractor and VA agree to periodic reviews in order to evaluate any new federal laws and VA regulations that could impact providing and meeting the required services in the Performance Work

Statement (PWS).

If audits are required, VA shall provide written notice to the Contractor as required.

Upon notification, the Contractor shall permit access to the Contractor Technology

Center (CTC) and processing environment for VA’s auditors and/or an independent auditor retained by VA. Within a reasonable timeframe, VA will provide the Contractor an audit agenda prior to any audit date. Any such audit conducted by VA auditors and/or an independent auditor retained by VA shall be limited to one (1) audit per calendar year. The Contractor shall be required to provide reasonable support and assistance during any such audit(s) to include preparation, pre-audit events and one (1) business day of escorted physical CTC access. The Contractor shall conduct a periodic independent audit (internal or external agent) of the CTC operating environment in accordance with applicable standards. Any questions regarding CTC audits should be directed to its Executive for Regulatory Affairs.

Additionally, the Contractor shall cooperate with the VA Office of the Inspector General

(OIG) in the areas of facilities access, audits, security incident notification, and hosting location. Specifically, the Contractor (and any Subcontractors) shall:

A. Provide the Contracting Officer, COR, VA Project Manager, and representatives of the agency's Office of Inspector General, supervised access to the Contractor's facilities, installations, operations, documentation, databases, and personnel used for contract hosting services; provided the VA provides no less than 10 business days prior notice to Contractor of its requested access unless at directed request from OIG. This access shall be provided to the extent required to carry out audits, inspections, investigations, or other reviews to ensure compliance with contractual requirements for IT and information security, and to safeguard against threats and hazards to the integrity, availability, and confidentiality of agency information in the possession or under the control of the Contractor (or Subcontractor).

B. Fully cooperate with all audits, inspections, investigations, or other reviews conducted by or on behalf of the Contracting Officer or the agency Office of Inspector General as described in subparagraph (a). Full cooperation includes, but is not limited to, prompt disclosure (per agency policy) to authorized requests of data, information, and records requested in connection with any audit, inspection, investigation, or review, making employees of the Contractor available for interview by auditors, inspectors, and investigators within ten (10) business days from such request unless at the direct request of OIG. The Contractor shall provide access (per agency policy) to Contractor facilities, systems, data and personnel to the extent the auditors, inspectors, and investigators reasonably believe necessary to complete the audit, inspection, investigation, or other review. The Contractor's (and any Subcontractors') cooperation with audits, inspections, investigations, and reviews conducted under this clause will be provided at no additional cost to the Government.

5.2 SITE MAINTENANCE AND SOFTWARE SUPPORT

The contractor shall ensure that the necessary software support and maintenance of the

LSRP Product is maintained until such time as the new Electronic Health Record

Management (EHRM) system is implemented. This includes quarterly (e.g., every 90 days) software upgrades and patches that are necessary for the LSRP product to remain current. Support shall be available on a 24X7X365 basis including both scheduled maintenance and emergency support. Maintenance support for emergency support and scheduled maintenance shall be made available via the Cerner service desk.

The Contractor shall provide a quarterly Software Support Report to the VA COR. In this report the Contractor shall document the work performed during the reporting period as defined in this task.

Description Quantity

Software Support for Cerner PathNet LSRP implementation

Software Maintenance Support for Cerner PathNet LSRP implementation

A. Quarterly (no longer than every 90 days) LSRP software review and updates report.

• Evidence of: Software Support for Cerner PathNet LSRP implementation

• Evidence of: Software Maintenance Support for Cerner PathNet LSRP implementation

5.3 REMOTE HOSTING OF THE LSRP PRODUCT

The Contractor shall provide a high availability remote hosting environment for the

LSRP Product and associated data.

Metric Limit

Peak Concurrent Logons

(PCL)

Forty (40) Peak Concurrent Logons

Number of Sites One (1) located in Huntington, WV

Total Lab Procedures

(per Year)

(Total Lab Procedures as defined in the

Licensed Software

Scope of Use Limits)

Two Million (2,000,000) Lab Tests per Year

Note – It is assumed that no major volume fluctuations occur from month to month and that monthly order volume is approximately equal to 1/12 of the annual scope limit.

Note – It is assumed there are no more than twenty-one million (21,000,000) interface transactions per year associated with this Lab Order volume. (combined inbound and outbound interface volumes including application acknowledgement functionality)

Solutions to be Remote

Hosted

Cerner PathNet LSRP Implementation

(Gen Lab, Micro, AP, Synoptic Reporting, Open Engine, P2

Sentinel, CareAware iBus (historically referred to as MDBus))

Mock Upgrades Up to two (2) during the life of the contract inclusive of optional periods, with no more than one (1) during any contiguous 12 months.

Mock Upgrades require written notice from VA, no less than

90 days prior to project kickoff not inclusive of option execution and notice required to the Upgrade Center for upgrade services.

P2 Sentinel • One (1) Production instance configured in N+1.

• One (1) Non-Production instance configured in N only.

• Up to one (1.0) terabyte of disk storage total.

• P2 Sentinel is not included in the DR Scope of Service.

CareAware iBus • One (1) Production CareAware iBus cluster configured in N+1 to support up to 1,000 Device Connections;

excludes fetal monitor or other wave form devices.

• One (1) Non-Production CareAware iBus instance configured in N only.

• Location:

o Servers owned and remotely managed by the

Contractor at the CTC.

o CareAware iBus is not included in the DR scope of service until after migrated to CTC

The Contractor shall provide the following LSRP domains for VA use during each period of performance:

• One (1) Production Domain, and

• One (1) Pre-Production Domain, and

• One (1) Test Domain.

NOTE: Live data will not be used in the pre-production or testing environments.

The Contractor shall provide remote hosting services to include servers, software, monitoring and management, hardware infrastructure, testing automation, network infrastructure, and storage and backups solutions.

The Contractor shall meet or exceed the guidance provided in the following high availability and redundancy requirements for the Primary production data center.

A. Minimum n+1 facility design.

B. Federal Emergency Management Agency (FEMA) 361 standard for Enhanced

Fujita (EF) scale EF-5 tornado survivability.

C. Fire protection systems with multiple command and control rooms.

D. n+2 chiller plants and n+1 cooling loops.

E. Dual stack redundant “fail on” control architecture to support mechanical operations.

F. Multiple power feeds including commercial power, Uninterruptible Power Supply

(UPS), and n+2 emergency generators.

G. Water intrusion alarms.

H. Network diversity to include Internet connections, direct client connection circuits, communications suppliers, and n+1 systems supporting client application needs.

I. Redundant Storage Area Networks (SAN).

J. Physical security including facility, grounds, data center floor space manned by armed guards and using biometric readers in high-security areas.

K. VA security controls including antivirus software, stateful-inspection firewalls, intrusion prevention systems, virtual private networks with FIPS 140-2 certified in transit data encryption, system hardening, enterprise logging and proxy servers.

L. HIPAA Security Compliance in accordance with (IAW) Paragraph 2.0, Applicable Documents.

M. Update existing Disaster Recovery Plan. Guidance is found in VA Handbook 6500, 6500.8 IAW Paragraph 2.0, Applicable Documents.

N. The Contractor shall provide services 24 hours a day, seven (7) days a week, and 365 days a year with a 99.9 percent uptime for the production PathNet system (excluding planned maintenance - See Appendix C for further details).

O. The Contractor shall implement data backup procedures to ensure no loss of data. At a minimum, incremental data and system back-ups shall be performed once daily and a full data and system back-up shall be performed once weekly.

5.3.1 TECHNICAL SUPPORT

The Contractor shall provide the following technical support for production systems according to the Contractor’s best commercial practices:

A. Provide LSRP application and technical support twenty-four (24) hours per day, seven (7) days per week, and three hundred and sixty-five (365) days per year including Federal Holiday, utilizing both telephone and internet services.

B. Manage and support the entire LSRP solution including: all server operating systems as well as Millennium, Oracle, Citrix, and MQSeries (WebSphere MQ) software.

C. Maintain support for existing security, network, system, database, application, and bi-directional interfaces to the LSRP product.

D. Install and provide support on contractor hosted front end services such as Windows Operating System (OS), Active Directory, Web Interface Services, and Antivirus monitoring.

E. Provide server services (back end) required to support the LSRP product, including installing and monitoring back-end systems and providing database support.

F. Provide and support network connectivity and data center operations.

G. Provide and support telecommunications between the remote hosted application and Alpha site to which Millennium solution is delivered.

H. Handle storage requests and maintenance/issues within the Storage Area

Network (SAN).

I. Provide remote support for installation of identical replacement new lab instruments.

J. Provide remote support for installation of printers. This does not include the physical installation and connectivity of the lab instruments or printers to the network or terminal servers.

K. Provide support for the selection, procurement and deployment of peripheral technologies certified by Cerner (e.g. PCs, thin VA devices, hand-held devices, printers, document scanners, and barcode scanners, etc.). Contractor will publish a list of certified devices for VA use.

L. Provide system monitoring, optimization, performance, and availability services.

M. Provide training on the…