36C10B19R0010_Final.docx

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.

DUNS:

DUNS+4:

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. 2/2012)

PREVIOUS EDITION IS NOT USABLE

Prescribed by GSA - FAR (48 CFR) 53.212

7. FOR SOLICITATION

INFORMATION CALL:

STANDARD FORM 1449

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

SOLICITATION/CONTRACT/ORDER FOR COMMERCIAL ITEMS

36C10B19R0010 12-18-2018 Eleanor Slocum 732-440-9677 12-20-2018 noon

Department of Veterans Affairs Technology Acquisition Center

23 Christopher Way Eatontown NJ 07724

X

Y 541513 $27.5 Million

N/A

See Section B.

Department of Veterans Affairs Technology Acquisition Center 23 Christopher Way

Eatontown NJ 07724

See Section B.2 Contract Administration Data

Labroratory System Reengineering Project (LSRP) Remote Hosting for Alpha Site.

Period of Performance: 1/1/2019 - 12/31/2019 with three 12-month option periods.

See Section B for a list of required deliverables.

Points of Contact:

Eleanor Slocum, Contract Specialist Eleanor.Slocum@va.gov 732-440-9677

Sharon Fernandes, Contracting Officer Sharon.Fernandes@va.gov 732-440-9670

Sharon L. Fernandes Contracting Officer

Table of Contents

SECTION B - CONTINUATION OF SF 1449 BLOCKS

B.1 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. 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. 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 effected 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:

(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 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) The contractor shall deliver to VA a perpetual, nonexclusive license to use the software described in the Product Description.

(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 Product Description.

(3) Software Maintenance and Technical Support

(a) If the Government desires to continue software maintenance and support beyond the period of performance identified in this 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 so as 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 Product Description. However, prolonged delay (exceeding 2 business days) in resolving software problems will be noted in the Government’s various past performance records on the Contractor (e.g., www.ppirs.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. The Contractor shall furnish VA the most current version of the user manual and publications for all products/services provided under this order.

B.3 CONTRACT ADMINISTRATION DATA

(continuation from Standard Form 1449, block 18A.)

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

a. CONTRACTOR:

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

BASE PERIOD – (12 Months)

QTY

UNIT

UNIT PRICE

TOTAL

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

The Period of Performance (PoP) is 12 months from date of award

Due Thirty (30) days after contract (DAC) and updated by the 15th of each month thereafter.

Electronic submission to: COR

Inspection: destination Acceptance: destination

LO

NSP

Due 5th day of each month throughout the PoP.

Electronic submission to: COR

Inspection: destination Acceptance: destination

Due the 15th day of each month throughout the PoP.

Electronic submission to: COR

Due thirty 30 days after contract (DAC) and updated as new certificates are issued

Electronic submission to: COR

Inspection: destination Acceptance: destination

Due thirty 30 days after contract (DAC) and updated as new certificates are issued

Electronic submission to: COR

Inspection: destination Acceptance: destination

Update annually or as required.

Electronic submission to: COR

Inspection: destination Acceptance: destination

The PoP is 12 months from date of award.

The PoP is 12 months from date of award.

The PoP is 12 months from date of award.

MO

· System Security Plan

· Residual Risk Assessment

· Signatory Authority

· Self-Assessment

· Program Objective and Milestones (POAM)

· Privacy Impact Assessment (PIA)

· Contingency Plan

· Incident Response Plan

· Configuration Management Plan

· Security Configuration Checklist

- System Interconnection Agreements Update annually or as required.

Electronic submission to: COR

Inspection: destination

The price of this SLIN shall be included in CLIN 0004.

Due thirty (30) days after contract award and updated annually as required.

Electronic submission to COR

Inspection: destination Acceptance: destination

The price of this SLIN shall be included in CLIN 0004.

The PoP is 12 months from date of award.

Electronic submission to: COR

Inspection: destination

The price of this SLIN shall be included in CLIN 0005.

Due three (3) days after option award and updated throughout the PoP.

Electronic submission to: COR

Inspection: destination

Due thirty (30) days after option award and updated throughout the PoP.

Electronic submission to: COR

Inspection: destination

Total of the Base Period

OPTION PERIOD ONE (1) – (12 Months). This option may be exercise in accordance with FAR 52.217-9 Option to Extend the Term of the Contract.

QTY

UNIT

UNIT PRICE

TOTAL

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

The Period of Performance (PoP) is 12 months from exercise of option.

Due Thirty (30) days after exercise of option and updated by the 15th of each month thereafter.

Electronic submission to: COR

Due 5th day of each month throughout the PoP.

Electronic submission to: COR

Inspection: destination Acceptance: destination

Due the 15th day of each month throughout the PoP.

Electronic submission to: COR

Due thirty 30 days after exercise of option and updated as new certificates are issued

Electronic submission to: COR

Inspection: destination Acceptance: destination

Due thirty 30 days after exercise of option and updated as new certificates are issued

Electronic submission to: COR

Inspection: destination Acceptance: destination

Update annually or as required.

Electronic submission to: COR

Inspection: destination Acceptance: destination

The PoP is 12 months from exercise of option.

The PoP is 12 months from exercise of option.

The PoP is 12 months from exercise of option.

· System Security Plan

· Residual Risk Assessment

· Signatory Authority

· Self-Assessment

· Program Objective and Milestones (POAM)

· Privacy Impact Assessment (PIA)

· Contingency Plan

· Incident Response Plan

· Configuration Management Plan

· Security Configuration Checklist

- System Interconnection Agreements Update annually or as required.

Electronic submission to: COR

Inspection: destination

The price of this SLIN shall be included in CLIN 1004.

Due thirty (30) days after option award and updated annually as required.

Electronic submission to COR

Inspection: destination Acceptance: destination

The price of this SLIN shall be included in CLIN 1004.

Electronic submission to: COR

Inspection: destination

The price of this SLIN shall be included in CLIN 1005.

Due three (3) days after exercise of option and updated throughout the PoP.

Electronic submission to: COR

Inspection: destination

Due thirty (30) days after exercise of option and updated throughout the PoP.

Electronic submission to: COR

Inspection: destination

Total of the Option Period 1

OPTION PERIOD TWO (2) – (12 Months). This option may be exercised in accordance with FAR 52.217-9 Option to Extend the Term of the Contract

QTY

UNIT

UNIT PRICE

TOTAL

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

The Period of Performance (PoP) is 12 months from exercise of option.

Due Thirty (30) days after exercise of option and updated by the 15th of each month thereafter.

Electronic submission to: COR

Due 5th day of each month throughout the PoP.

Electronic submission to: COR

Inspection: destination Acceptance: destination

Due the 15th day of each month throughout the PoP.

Electronic submission to: COR

Due thirty 30 days after exercise of option and updated as new certificates are issued

Electronic submission to: COR

Inspection: destination Acceptance: destination

Due thirty 30 days after exercise of option and updated as new certificates are issued

Electronic submission to: COR

Inspection: destination Acceptance: destination

Update annually or as required.

Electronic submission to: COR

Inspection: destination Acceptance: destination

The PoP is 12 months from exercise of option.

The PoP is 12 months from exercise of option.

· System Security Plan

· Residual Risk Assessment

· Signatory Authority

· Self-Assessment

· Program Objective and Milestones (POAM)

· Privacy Impact Assessment (PIA)

· Contingency Plan

· Incident Response Plan

· Configuration Management Plan

· Security Configuration Checklist

- System Interconnection Agreements Update annually or as required.

Electronic submission to: COR

Inspection: destination

The price of this SLIN shall be included in CLIN 2004.

Due thirty (30) days after exercise of option and updated annually as required.

Electronic submission to COR

Inspection: destination Acceptance: destination

The price of this SLIN shall be included in CLIN 2004.

Electronic submission to: COR

Inspection: destination

The price of this SLIN shall be included in CLIN 2005.

Due three (3) days after exercise of option and updated throughout the PoP.

Electronic submission to: COR

Inspection: destination

Due thirty (30) days after exercise of option and updated throughout the PoP.

Electronic submission to: COR

Inspection: destination

Total of Option Period 2

OPTION PERIOD THREE (3) – (12 Months). This option may be exercised in accordance with FAR 52.217-9 Option to Extend the Term of the Contract

QTY

UNIT

UNIT PRICE

TOTAL

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

The Period of Performance (PoP) is 12 months from exercise of option.

Due Thirty (30) days after exercise of option and updated by the 15th of each month thereafter.

Electronic submission to: COR

Due 5th day of each month throughout the PoP.

Electronic submission to: COR

Inspection: destination Acceptance: destination

Due the 15th day of each month throughout the PoP.

Electronic submission to: COR

Due thirty 30 days after exercise of option and updated as new certificates are issued

Electronic submission to: COR

Inspection: destination Acceptance: destination

Due thirty 30 days after exercise of option and updated as new certificates are issued

Electronic submission to: COR

Inspection: destination Acceptance: destination

Update annually or as required.

Electronic submission to: COR

Inspection: destination Acceptance: destination

The PoP is 12 months from exercise of option.

The PoP is 12 months from exercise of option.

· System Security Plan

· Residual Risk Assessment

· Signatory Authority

· Self-Assessment

· Program Objective and Milestones (POAM)

· Privacy Impact Assessment (PIA)

· Contingency Plan

· Incident Response Plan

· Configuration Management Plan

· Security Configuration Checklist

- System Interconnection Agreements Update annually or as required.

Electronic submission to: COR

Inspection: destination

The price of this SLIN shall be included in CLIN 3004.

Due thirty (30) days after exercise of option and updated annually as required.

Electronic submission to COR

Inspection: destination Acceptance: destination

The price of this SLIN shall be included in CLIN 3004.

Electronic submission to: COR

Inspection: destination

The price of this SLIN shall be included in CLIN 3005.

Due three (3) days after exercise of option and updated throughout the PoP.

Electronic submission to: COR

Inspection: destination

Due thirty (30) days after exercise of option and updated throughout the PoP.

Electronic submission to: COR

Inspection: destination

Total of Option Period 3

OPTIONAL TASK – This optional task may be exercised in accordance with FAR 52.217-7 – Option for Increased Quantity – Separately Priced Line Item.

QTY

UNIT

UNIT PRICE

TOTAL

This Option may be exercised IAW FAR 52.217-7 – Option for Increased Quantity – Separately Priced Line Item in the base period or any of the option periods.

CLIN 4001 may be exercised up to two (2) times over the PoP of the contract. The PoP of the optional task shall not exceed 190 days from date of exercise of the optional task.

Total of Optional Task

Total Price (Base Period Plus Option Periods 1, 2, 3, and Optional Task)

36C10B19R0010

B.5 PERFORMANCE WORK STATEMENT

PERFORMANCE WORK STATEMENT (PWS)

DEPARTMENT OF VETERANS AFFAIRS

Office of Information & Technology

Laboratory System Reengineering Project (LSRP) Remote Hosting for Alpha Site

Date: 11/29/2018

TAC-19-50781

PWS Version Number: 3.0

1.0 BACKGROUND

The mission of the Department of Veterans Affairs (VA), Office of Information and Technology (OI&T), is to provide benefits and services to Veterans of the United States. In meeting these goals, OI&T 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 Cerner’s Millennium PathNet solution LIMS, heretofore known as Millennium solution, as the Veterans Health Administration (VHA) Laboratory Information Management System (LIMS) for the VA Medical Center (VAMC) in Huntington, West Virginia, referred to as the Alpha site. The LIMS supports the Veterans Health Administration (VHA) Pathology and Laboratory Medicine Services (PLMS). The PLMS provides the principal medical diagnostic laboratory testing functionality in all VA Medical Centers. Laboratory results are significant drivers in clinical decision making. The LIMS includes a Commercial Off-The-Shelf (COTS) application, Cerner Millennium PathNet, interfaced with Veterans Health Information Systems and Technology Architecture (VistA). The LIMS modernizes the legacy VistA laboratory application created over 30 years ago. It provides improved turnaround time and overall improvement in lab productivity for effective and efficient medical care of Veterans. The LIMS also addresses patient safety concerns, meets regulatory and accreditation standards, and supports enhanced business processes and emerging technologies. VA requires continued Remote Hosting (RH), System Management Services (SMS), Application Management Services (AMS), Disaster Recovery (DR) services, management and technical support for the Cerner Millennium PathNet LIMS inclusive of remote hosting of the data from the Genomic Laboratory and software maintenance of the Cerner Millennium software.

VA’s Cerner Millennium PathNet LIMS is currently running on the Cerner Millennium 2015 software version which can become obsolete and no longer be supported by Cerner. As a result, software maintenance may be required during performance. Degradation of the system would cause operational and performance issues affecting system interfaces, Section 508 and security functionality which puts patient safety at risk and negatively impacts VA’s ability to maintain an Authority to Operate (ATO). System maintenance is critical to patient safety and for the continued use of the Cerner Millennium PathNet LIMS until the scheduled replacement in 2023 by the Cerner health care system.

In Fiscal Year (FY) 2018, the Genomic Laboratory Information Management System (LIMS) Phase II was awarded. Phase II involves the implementation of the full Millennium Helix configuration developed in the Phase I non-production environment into the current Huntington VAMC non- production and production environments. All the genomic labs will be configured to operate in the non-production environment then, following successful testing and validation, will be implemented into the production environment. Phase II implementation is to configure and integrate the Reference Lab Network (RLN) connection and instrument interfaces to all genomic labs into the non-production and production domains. As a result, the Contractor shall remote host the Genomic Laboratory data for the Alpha sites.

2.0 APPLICABLE DOCUMENTS

In the performance of the tasks associated with this Performance Work Statement (PWS), 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 2016

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. Carnegie Mellon Software Engineering Institute, Capability Maturity Model® Integration for Development (CMMI-DEV), Version 1.3 November 2010; and Carnegie Mellon Software Engineering Institute, Capability Maturity Model® Integration for Acquisition (CMMI-ACQ), Version 1.3 November 2010

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

10. Public Law 109-461, Veterans Benefits, Health Care, and Information Technology Act of 2006, Title IX, Information Security Matters

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

12. VA Directive 0710, “Personnel Security and Suitability Program,” June 4, 2010, http://www.va.gov/vapubs/

13. VA Handbook 0710, Personnel Security and Suitability Security Program, May 2, 2016, http://www.va.gov/vapubs

14. VA Directive and Handbook 6102, “Internet/Intranet Services,” July 15, 2008

15. 36 C.F.R. Part 1194 “Electronic and Information Technology Accessibility Standards,” July 1, 2003

16. Office of Management and Budget (OMB) Circular A-130, “Managing Federal Information as a Strategic Resource,” July 28, 2016

17. 32 C.F.R. Part 199, “Civilian Health and Medical Program of the Uniformed Services (CHAMPUS)”

18. An Introductory Resource Guide for Implementing the Health Insurance Portability and Accountability Act (HIPAA) Security Rule, October 2008

19. Sections 504 and 508 of the Rehabilitation Act (29 U.S.C. § 794d), as amended by the Workforce Investment Act of 1998 (P.L. 105-220), August 7, 1998

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

21. VA Directive 6500, “Managing Information Security Risk: VA Information Security Program,” September 20, 2012

22. VA Handbook 6500, “Risk Management Framework for VA Information Systems – Tier 3: VA Information Security Program,” March 10, 2015

23. VA Handbook 6500.1, “Electronic Media Sanitization,” November 03, 2008

24. VA Handbook 6500.2, “Management of Breaches Involving Sensitive Personal Information (SPI)”, July 28, 2016

25. VA Handbook 6500.3, “Assessment, Authorization, And Continuous Monitoring Of VA Information Systems,” February 3, 2014

26. VA Handbook 6500.5, “Incorporating Security and Privacy in System Development Lifecycle”, March 22, 2010

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

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

29. OI&T 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

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

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

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

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

34. VA Directive 6300, Records and Information Management, February 26, 2009

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

36. NIST SP 800-37, Guide for Applying the Risk Management Framework to Federal Information Systems: a Security Life Cycle Approach, June 10, 2014

37. NIST SP 800-53 Rev. 4, Security and Privacy Controls for Federal Information Systems and Organizations, January 22, 2015

38. OMB Memorandum, “Transition to IPv6”, September 28, 2010

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

40. VA Handbook 0735, Homeland Security Presidential Directive 12 (HSPD-12) Program, March 24, 2014

41. OMB Memorandum M-06-18, Acquisition of Products and Services for Implementation of HSPD-12, June 30, 2006

42. OMB Memorandum 04-04, E-Authentication Guidance for Federal Agencies, December 16, 2003

43. 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

44. OMB memorandum M-11-11, “Continued Implementation of Homeland Security Presidential Directive (HSPD) 12 – Policy for a Common Identification Standard for Federal Employees and Contractors, February 3, 2011

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

46. Federal Identity, Credential, and Access Management (FICAM) Roadmap and Implementation Guidance, December 2, 2011

47. NIST SP 800-116, A Recommendation for the Use of Personal Identity Verification (PIV) Credentials in Physical Access Control Systems, November 20, 2008

48. OMB Memorandum M-07-16, Safeguarding Against and Responding to the Breach of Personally Identifiable Information, May 22, 2007

49. NIST SP 800-63-3, 800-63A, 800-63B, 800-63C, Digital Identity Guidelines, June 2017

50. NIST SP 800-157, Guidelines for Derived PIV Credentials, December 2014

51. NIST SP 800-164, Guidelines on Hardware-Rooted Security in Mobile Devices (Draft), October 2012

52. NIST SP 800-88, Guidelines for Media Sanitization, December 2014

53. NIST SP 800-70, National Checklist program for IT, February 2018

54. NIST SP 800-61, Computer Security Incident Handling Guide, August 2012

55. NIST SP 800-63-3, Digital Identity Guidelines, December 2017

56. NIST SP 800-47, Security Guide for Interconnecting Information Technology Systems, September 2002

57. NIST SP 800-34, Contingency Planning Guide for Federal Information Systems, November 2010

58. NIST SP 800-30, Guide for Conducting Risk Assessment, September 2012

59. NIST SP 800-18Guide for Developing Security Plans for Federal Information Systems, February 2006

60. NIST SP 800-16, A role-Based Model for Federal Information Technology/Cybersecurity Training, March 2014

61. Draft National Institute of Standards and Technology Interagency Report (NISTIR) 7981 Mobile, PIV, and Authentication, March 2014

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

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

64. VA Memorandum “Mandate to meet PIV Requirements for New and Existing Systems” (VAIQ# 7712300), June 30, 2015, https://www.voa.va.gov/DocumentView.aspx?DocumentID=4846

65. Trusted Internet Connections (TIC) Reference Architecture Document, Version 2.0, Federal Interagency Technical Reference Architectures, Department of Homeland Security, October 1, 2013, https://s3.amazonaws.com/sitesusa/wp-content/uploads/sites/482/2015/04/TIC_Ref_Arch_v2-0_2013.pdf

66. OMB Memorandum M-08-05, “Implementation of Trusted Internet Connections (TIC), November 20, 2007

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

68. VA Memorandum, VAIQ #7497987, Compliance – Electronic Product Environmental Assessment Tool (EPEAT) – IT Electronic Equipment, August 11, 2014 (reference Document Libraries, EPEAT/Green Purchasing Section, https://www.voa.va.gov/documentlistpublic.aspx?NodeID=552)

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

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

71. Executive Order 13693, “Planning for Federal Sustainability in the Next Decade”, dated March 19, 2015

72. Executive Order 13221, “Energy-Efficient Standby Power Devices,” August 2, 2001

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

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

75. Office of Information Security (OIS) VAIQ #7424808 Memorandum, “Remote Access”, January 15, 2014, https://www.voa.va.gov/DocumentListPublic.aspx?NodeId=28

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

77. VA Memorandum, “Implementation of Federal Personal Identity Verification (PIV) Credentials for Federal and Contractor Access to VA IT Systems”, (VAIQ# 7614373) July 9, 2015, https://www.voa.va.gov/DocumentListPublic.aspx?NodeId=28

78. VA Memorandum “Mandatory Use of PIV Multifactor Authentication to VA Information System” (VAIQ# 7613595), June 30, 2015, https://www.voa.va.gov/DocumentListPublic.aspx?NodeId=28

79. VA Memorandum “Mandatory Use of PIV Multifactor Authentication for Users with Elevated Privileges” (VAIQ# 7613597), June 30, 2015; https://www.voa.va.gov/DocumentListPublic.aspx?NodeId=28

80. “Veteran Focused Integration Process (VIP) Guide 2.0”, May 2017, https://www.voa.va.gov/DocumentView.aspx?DocumentID=4371

81. “VIP Release Process Guide”, Version 1.4, May 2016, https://www.voa.va.gov/DocumentView.aspx?DocumentID=4411

82. “POLARIS User Guide”, Version 1.2, February 2016, https://www.voa.va.gov/DocumentView.aspx?DocumentID=4412

83. VA Memorandum “Use of Personal Email (VAIQ #7581492)”, April 24, 2015, https://www.voa.va.gov/DocumentListPublic.aspx?NodeId=28

84. VA Memorandum “Updated VA Information Security Rules of Behavior (VAIQ #7823189)”, September, 15, 2017, https://www.voa.va.gov/DocumentListPublic.aspx?NodeId=28

85. Federal Continuity Directive 1 (FCD-1), (National Security Presidential Directive-51) NSPD-51/HSPD-20 National Continuity Policy.

86. Authorization Requirements SOP September 4, 2018

3.0 SCOPE OF WORK

The Contractor shall maintain the Cerner Millennium PathNet LIMS, heretofore known as Millennium, for the LSRP Alpha site and provide the following capabilities and services: monthly progress and on-boarding requirement reports, remote hosting, disaster recovery support, technical support, system security, network connectivity, application support requirements, testing, capacity planning, and operations & maintenance.

The Contractor shall also only remote host the data for Helix (Genomic Laboratories) for the Alpha site. Since the Helix (Genomic Laboratories) data is within the same data storage structure as Millennium PathNet LIMS, all disaster recovery, and system security support shall apply.

The Contractor shall provide software maintenance on the Cerner Millennium PathNet application as required under Optional Task 1, PWS, Paragraph 5.11 and all sub-paragraphs.

4.0 PERFORMANCE DETAILS

4.1 PERFORMANCE PERIOD

The Period of Performance (PoP) shall be a 12-month base period commencing on or about 1/1/2019 with three (3), 12-month option periods, if exercised. Tasks 5.1 through 5.10 shall be performed within the base period, and each option period, if exercised. Optional Task 1 may be exercised two (2) times any time throughout the period of performance in accordance with Section B, Price Schedule. The period of performance of the optional task shall not exceed 190 days from date of exercise of the optional task.

4.2 PLACE OF PERFORMANCE

Tasks under this PWS shall be performed at Contractor facilities.

4.3 TRAVEL

The Government does not anticipate travel under this effort.

5.0 SPECIFIC TASKS AND DELIVERABLES

The Contractor shall perform the following:

5.1 PROJECT MANAGEMENT

In performance of this effort, the Contractor shall identify its place of performance.

5.1.1 MONTHLY PROGRESS REPORT

The Contractor shall provide the COR/VA Program Manager (PM) with Monthly Progress Reports in electronic form in Microsoft Word and Project 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 CPMP and report any deviations. The Monthly Progress Report shall also include updates for Application Support Requirements (PWS paragraph 5.7. 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 at least weekly via a conference call to review project team information requests and shall track this activity in the Monthly Progress Report required under 5.1.1 including summary notes of Subject Matter Expert (SME) expertise Review, Inputs, Updates and Feedback information requests that were addressed and the Contractor project status.

Deliverable:

A. Monthly Progress Report

5.1.2 ONBOARDING

The Contractor shall manage the onboarding of its staff. Onboarding includes steps to obtain a VA network and email account, complete training as defined in section 5.1.4 for initiating background investigations, and gaining physical and logical access, which may include elevated privileges to the…