36C10B19Q0716-001.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. 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 87

36C10B19Q0716 09-06-2019

Tinamarie Giraud, Contract Specialist 732-440-9641 09-11-2019

12 PM EST

Department of Veterans Affairs

Technology Acquisition Center

23 Christopher Way

Eatontown NJ 07724

X

N/A

X

See Delivery Schedule

TBD

To Be Determined (TBD)

Financial Services Center

PO Box 149971

Austin TX 78714-8971

See CONTINUATION Page

Title: Software-as-a-Service (SaaS) Environmental Health &

Safety Auditing System

Points of Contact:

Contract Specialist: Tinamarie Giraud, 732-440-9641, Tinamarie.Giraud@va.gov.

Contracting Officer: Carol Newcomb, 732-795-1018, Carol.Newcomb@va.gov.

See CONTINUATION Page

Carol G. Newcomb

Contracting Officer

36C10B19Q0716

Table of Contents

SECTION A

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

SECTION B - CONTINUATION OF SF 1449 BLOCKS

B.1 CONTRACT ADMINISTRATION DATA

B.2 GOVERNING LAW

B.3 SOFTWARE LICENSE, MAINTENANCE AND TECHNICAL SUPPORT:

B.4 SCHEDULE OF DELIVERABLES

B.5 PERFORMANCE WORK STATEMENT (PWS)

1.0 BACKGROUND

2.0 APPLICABLE DOCUMENTS

3.0 SCOPE OF WORK

4.0 PERFORMANCE DETAILS

4.1 PERFORMANCE PERIOD

4.2 PLACE OF PERFORMANCE

4.3 TRAVEL

5.0 SPECIFIC TASKS AND DELIVERABLES

5.1 PROJECT MANAGEMENT

5.1.1 REPORTING REQUIREMENTS

5.1.2 TECHNICAL KICKOFF MEETING

5.2 EH&S AUDITING SAAS SYSTEM SOLUTION

5.2.1 FUNCTIONAL REQUIREMENTS

5.2.2 TECHNOLOGY REQUIREMENTS

5.2.3 UPGRADES AND ENHANCEMENTS TO SOFTWARE

5.2.4 ACCEPTANCE TESTING

5.2.5 EMERGENCY OPERATIONS

5.2.6 HELP DESK SUPPORT

5.2.7 SYSTEM ADMINISTRATION

5.2.8 INITIAL USER TRAINING

5.3 TRAINING

5.4 OPTION YEAR 1-4

5.5 OPTIONAL TASK - VARIABLE QUANTITIES OPTION

6.0 GENERAL REQUIREMENTS

6.1 ENTERPRISE AND IT FRAMEWORK

6.1.1 FEDERAL IDENTITY, CREDENTIAL, AND ACCESS MANAGEMENT

(FICAM)

6.1.2 INTERNET PROTOCOL VERSION 6 (IPV6)

6.1.3 TRUSTED INTERNET CONNECTION (TIC)

6.1.4 STANDARD COMPUTER CONFIGURATION

6.1.5 VETERAN FOCUSED INTEGRATION PROCESS (VIP)

6.2 SECURITY AND PRIVACY REQUIREMENTS

6.2.1 POSITION/TASK RISK DESIGNATION LEVEL(S)

6.3 METHOD AND DISTRIBUTION OF DELIVERABLES

6.4 FACILITY/RESOURCE PROVISIONS

6.5 GOVERNMENT FURNISHED PROPERTY

ADDENDUM A – ADDITIONAL VA REQUIREMENTS, CONSOLIDATED

ADDENDUM B – VA INFORMATION AND INFORMATION SYSTEM SECURITY/PRIVACY

LANGUAGE

7.0 POINTS OF CONTACT

SECTION C - CONTRACT CLAUSES

C.1 52.212-4 CONTRACT TERMS AND CONDITIONS—COMMERCIAL ITEMS (OCT

2018)

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

C.3 52.217-7 OPTION FOR INCREASED QUANTITY - SEPARATELY PRICED LINE ITEM

(MAR 1989)

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

C.5 VAAR 852.215-71 EVALUATION FACTOR COMMITMENTS (DEC 2009)

C.6 VAAR 852.219-75 SUBCONTRACTING COMMITMENTS MONITORING AND

COMPLIANCE (JUL 2018) (DEVIATION)

C.7 VAAR 852.232-72 ELECTRONIC SUBMISSION OF PAYMENT REQUESTS (NOV

2018)

C.8 VAAR 852.237-70 CONTRACTOR RESPONSIBILITIES (APR 1984)

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

STATUTES OR EXECUTIVE ORDERS-COMMERCIAL ITEMS (AUG 2019)

SECTION D - CONTRACT DOCUMENTS, EXHIBITS, OR ATTACHMENTS

SECTION E - SOLICITATION PROVISIONS

E.1 52.212-1 INSTRUCTIONS TO OFFERORS-COMMERCIAL ITEMS (OCT 2018)

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

1998)

E.3 52.204-24 REPRESENTATION REGARDING CERTAIN TELECOMMUNICATIONS

AND VIDEO SURVEILLANCE SERVICES OR EQUIPMENT (AUG 2019)

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

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

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

E.7 52.212-3 OFFEROR REPRESENTATIONS AND CERTIFICATIONS—COMMERCIAL

ITEMS (OCT 2018)

E.8 VAAR 852.270-1 REPRESENTATIVES OF CONTRACTING OFFICERS (JAN 2008) ..80

E.9 VAAR 852.215-70 SERVICE-DISABLED VETERAN-OWNED AND VETERAN-

OWNED SMALL BUSINESS EVALUATION FACTORS (JUL 2016)(DEVIATION)

E.10 VAAR 852.233-70 PROTEST CONTENT/ALTERNATIVE DISPUTE RESOLUTION

(OCT 2018)

E.11 VAAR 852.233-71 ALTERNATE PROTEST PROCEDURE (OCT 2018)

E.12 BASIS FOR AWARD

E.13 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

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 []

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.

Financial Services Center

PO Box 149971

Austin TX 78714-8971

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

AMENDMENT NO DATE

B.2 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.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 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 Technical Support

(a) If the Government desires to continue software maintenance and support beyond the period of performance identified in this contract or 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 Performance Work Statement/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. 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.4 SCHEDULE OF DELIVERABLES

NOTE: Non-TAA compliant items may be quoted for this procurement as Federal Acquisition

Regulation 25.401 (applicable exceptions) applies.

Vendors are instructed to complete Section B.4 and submit with their quote.

Vendors are cautioned that alterations to the line items as specified below may render quotes unacceptable. All questions shall be directed to the Contract Specialist, Tinamarie Giraud, and

Contracting Officer, Carol Newcomb, prior to the closing date and time specified in the Request for Quote (RFQ).

http://www.ppirs.gov/

BASE PERIOD (12 Months)

CONTRACT

LINE ITEM

NUMBER

(CLIN)

DESCRIPTION QTY UNIT

UNIT

PRICE

TOTAL

PRICE

Description: Single comprehensive, enterprise-wide Environmental Health and Safety (EH&S) auditing Software-as-a-Service (SaaS) system including helpdesk and maintenance support services In accordance With (IAW) Performance

Work Statement (PWS) Section 5.2 and associated subparagraphs.

Delivery/Due Dates: All SaaS components shall be delivered at contract Award in accordance with

Performance Details outlined in Section 4.0 of the

Performance Work Statement (PWS).

Contractor shall deliver 200 initial licenses. Upon

Authority To Operate (ATO) approval Contractor shall deliver 1,000 additional licenses for a total of

1,200 during the base period.

12 MO $ $

0001AA

Monthly Progress Report

Delivery/Due Dates: due the fifth day of each month throughout the Period of Performance

(PoP).

Electronic submission to: VA PM, COR, CO/CS.

12 EA

Not

Separately

Priced

(NSP)

Not

Separately

Priced

(NSP)

0001AB

User Documentation IAW 5.2.2

Delivery/Due: due within 5 days after the installation is complete.

1 LO NSP NSP

0001AC Facility User Abatement Process Report 1 LO NSP NSP

0001AD

System Testing and Acceptance Plan

Due:15 days after award.

1 LO NSP NSP

Training

1 LO $ $

0002AA

Training Schedule

Delivery/Due: Due within 10 days of award.

1 LO NSP NSP

0002AB Initial User Training IAW 5.2.8 1 LO $ $

0002AC Training IAW 5.3 1 LO $ $

OPTIONAL TASK - VARIABLE QUANTITIES

OPTION -Additional User License

This Optional Task may be exercised IAW FAR

52.217-7, Option for Increased Quantity –

Separately Priced Line Item. This optional task can be exercised up to 12 times throughout the life of this contract for up to 1,200 total licenses.

1 Lot-100 Additional User Licenses

Total Base Period: $

Total Optional Task: $

OPTION PERIOD ONE

(12 months)

This 12-month option period may be exercised IAW FAR 52.217-9, Option to Extend the Term of the

Contract (MAR 2000). Work shall not commence until, and unless, a formal modification is issued by the

Contracting Officer. If exercised, this option shall commence immediately after expiration of the Base Period.

CONTRACT

LINE ITEM

NUMBER

(CLIN)

DESCRIPTION QTY UNIT

UNIT

PRICE

TOTAL

PRICE

Description: Single comprehensive, enterprise-wide Environmental Health and Safety (EH&S) auditing Software-as-a-Service (SaaS) system including helpdesk and maintenance support services In accordance With (IAW) Performance

Work Statement (PWS) Section 5.1 through 5.3 and associated subparagraphs, with the exception of

5.2.8 “Initial User Training.

Delivery/Due Dates: All system components shall be delivered No Later Than (NLT) 5 days after contract Award in accordance with Section 4.0 of the Performance Work Statement (PWS).

1 LO $ $

Separately Priced Line Item. This optional task can

1 Lot=100 Additional User Licenses

Total Option Period One:

OPTION PERIOD TWO

(12 months)

This 12-month option period may be exercised IAW FAR 52.217-9, Option to Extend the Term of the

Contract (MAR 2000). Work shall not commence until, and unless, a formal modification is issued by the

Contracting Officer. If exercised, this option shall commence immediately after expiration of the Option

Period One.

CONTRACT

LINE ITEM

NUMBER

(CLIN)

DESCRIPTION QTY UNIT

UNIT

PRICE

TOTAL

PRICE

Description: Single comprehensive, enterprise-wide Environmental Health and Safety (EH&S) auditing Software-as-a-Service (SaaS) system including helpdesk and maintenance support services In accordance With (IAW) Performance

Work Statement (PWS) Section 5.1 through 5.3 and associated subparagraphs with the exception of 5.2.8

“Initial User Training..

contract Award in accordance with Section 4.0 of the Performance Work Statement (PWS).

1 LO $ $

Separately Priced Line Item. This optional task can

Total Option Period Two: $

OPTION PERIOD THREE

(12 months)

This 12-month option period may be exercised IAW FAR 52.217-9, Option to Extend the Term of the

Contract (MAR 2000). Work shall not commence until, and unless, a formal modification is issued by the

Contracting Officer. If exercised, this option shall commence immediately after expiration of the Option

Period Two.

CONTRACT

LINE ITEM

NUMBER

(CLIN)

DESCRIPTION QTY UNIT

UNIT

PRICE

TOTAL

PRICE

Description: Single comprehensive, enterprise-wide Environmental Health and Safety (EH&S) auditing Software-as-a-Service (SaaS) system including helpdesk and maintenance support services In accordance With (IAW) Performance

Work Statement (PWS) Section 5.1 through 5.3 and associated subparagraphs with the exception of 5.2.8

“Initial User Training.

contract Award in accordance with Section 4.0 of the Performance Work Statement (PWS).

Separately Priced Line Item. This optional task can

Total Option Period Three: $

OPTION PERIOD FOUR

(12 months)

This 12-month option period may be exercised IAW FAR 52.217-9, Option to Extend the Term of the

Contract (MAR 2000). Work shall not commence until, and unless, a formal modification is issued by the

Contracting Officer. If exercised, this option shall commence immediately after expiration of the Option

Period Three.

CONTRACT

LINE ITEM

NUMBER

(CLIN)

DESCRIPTION QTY UNIT

UNIT

PRICE

TOTAL

PRICE

Description: Single comprehensive, enterprise-wide Environmental Health and Safety (EH&S) auditing Software-as-a-Service (SaaS) system including helpdesk and maintenance support services In accordance With (IAW) Performance

Work Statement (PWS) Section 5.1 through 5.3 and associated subparagraphs, with the exception of

5.2.8 “Initial User Training.

contract Award in accordance with Section 4.0 of the Performance Work Statement (PWS).

1 LO $ $

This Optional Task may be exercised IAW FAR

52.217-7, Option for Increased Quantity –

Separately Priced Line Item. This optional task can

Total Option Period Four: $

Total Value: $

B.5 PERFORMANCE WORK STATEMENT (PWS)

DEPARTMENT OF VETERANS AFFAIRS

Veterans Health Administration (VHA)

VHA Center for Engineering & Occupational

Safety and Health (CEOSH)

Software-as-a-Service (SaaS) System

Services Environmental Health Safety Auditing

Date: July 18, 2019

TAC-19-51612

PWS Version Number: 1.8

TAC Number: TAC-19-51612

1.0 BACKGROUND

The Department of Veteran’s Affairs (VA), Veterans Health Administration (VHA), manages the largest medical system in the United States, providing care to over 8.9 million Veterans, employing 180,000 medical personnel and operating 171 hospitals in 18 regions throughout the continental United States., Alaska, Caribbean and Hawaii. The VHA Center for Engineering &

Occupational Safety and Health (CEOSH) is responsible for providing Environmental

Engineering Services for the VHA and as such CEOSH is the agency responsible for acquiring the services described in this PWS. It is projected that there will be approximately 1,100 users of the service in some form of administrative capacity at the national, regional, or local level.

The VHA requires a single comprehensive, enterprise-wide Environmental Health and Safety

(EH&S) auditing Software-as-a-Service (SaaS) system that meets the compliance auditing program and management systems requirements detailed in the following industry consensus documents: ISO 14001:2015, Environmental Management Systems; ISO 45001:2018, Occupational Health and Safety Management Systems; and ANSI/ASSE Z10-2012 (R2017), Occupational Health and Safety Management Systems Standard (OHSMS).

It is estimated that approximately 90 surveyors (5/region) and 1,026 VHA personnel (6/facility) will require system access and will utilize the EH&S system.

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. *-, Health Care, and Information Technology Act of 2006, Title IX, Information

Security Matters

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

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

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

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

8. 36 C.F.R. Part 1194 “Electronic and Information Technology Accessibility

Standards,” July 1, 2003

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

Information as a Strategic Resource,” July 28, 2016

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

Services (CHAMPUS)”

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

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

13. Homeland Security Presidential Directive (12) (HSPD-12), August 27, 2004 http://www.va.gov/vapubs/ http://www.va.gov/vapubs http://www.va.gov/vapubs

14. VA Directive 6500, “Managing Information Security Risk: VA Information Security

Program,” September 20, 2012

15. VA Handbook 6500, “Risk Management Framework for VA Information Systems –

Tier 3: VA Information Security Program,” March 10, 2015

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

17. VA Handbook 6500.2, “Management of Breaches Involving Sensitive Personal

Information (SPI)”, July 28, 2016

18. VA Handbook 6500.3, “Assessment, Authorization, And Continuous Monitoring Of

VA Information Systems,” February 3, 2014

19. VA Handbook 6500.5, “Incorporating Security and Privacy in System Development

Lifecycle”, March 22, 2010

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

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

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

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

24. VA Directive 6508, “Implementation of Privacy Threshold Analysis and Privacy

Impact Assessment,” October 15, 2014

25. VA Handbook 6508.1, “Procedures for Privacy Threshold Analysis and Privacy

Impact Assessment,” July 30, 2015

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

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

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

29. NIST SP 800-37, Guide for Applying the Risk Management Framework to Federal

Information Systems: a Security Life Cycle Approach, June 10, 2014

30. NIST SP 800-53 Rev. 4, Security and Privacy Controls for Federal Information

Systems and Organizations, January 22, 2015

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

32. VA Directive 0735, Homeland Security Presidential Directive 12 (HSPD-12)

Program, October 26, 2015

33. VA Handbook 0735, Homeland Security Presidential Directive 12 (HSPD-12)

Program, March 24, 2014

34. OMB Memorandum M-06-18, Acquisition of Products and Services for

Implementation of HSPD-12, June 30, 2006

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

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

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

38. OMB Memorandum, Guidance for Homeland Security Presidential Directive

(HSPD) 12 Implementation, May 23, 2008 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

39. Federal Identity, Credential, and Access Management (FICAM) Roadmap and

Implementation Guidance, December 2, 2011

40. NIST SP 800-116, A Recommendation for the Use of Personal Identity Verification

(PIV) Credentials in Physical Access Control Systems, November 20, 2008

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

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

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

44. NIST SP 800-164, Guidelines on Hardware-Rooted Security in Mobile Devices

(Draft), October 2012

45. Draft National Institute of Standards and Technology Interagency Report (NISTIR)

7981 Mobile, PIV, and Authentication, March 2014

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

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

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

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

50. OMB Memorandum M-08-05, “Implementation of Trusted Internet Connections

(TIC), November 20, 2007

51. OMB Memorandum M-08-23, Securing the Federal Government’s Domain Name

System Infrastructure, August 22, 2008

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

53. Sections 524 and 525 of the Energy Independence and Security Act of 2007, (Public

Law 110–140), December 19, 2007

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

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

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

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

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

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

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

60. Clinger-Cohen Act of 1996, 40 U.S.C. §11101 and §11103 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=4846 https://s3.amazonaws.com/sitesusa/wp-content/uploads/sites/482/2015/04/TIC_Ref_Arch_v2-0_2013.pdf https://s3.amazonaws.com/sitesusa/wp-content/uploads/sites/482/2015/04/TIC_Ref_Arch_v2-0_2013.pdf https://www.voa.va.gov/documentlistpublic.aspx?NodeID=552 https://www.voa.va.gov/DocumentListPublic.aspx?NodeId=28

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

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

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

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

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

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

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

68. VA Memorandum “Updated VA Information Security Rules of Behavior (VAIQ

#7823189)”, September, 15, 2017, https://www.voa.va.gov/DocumentListPublic.aspx?NodeId=28

69. Department of Veterans Affairs (VA) Directive 0710, “Personnel Suitability and

Security Program,” June 4, 2010

70. ANSI/ASSE Z10-2012 (R2017), Occupational Health and Safety Management

Systems Standard (OHSMS)

3.0 SCOPE OF WORK

The Contractor shall provide all labor, materials, tools and equipment, training, maintenance, technical support, travel, project management and supervision required to provide access and support to an EH&S auditing software-as-a-service system.

4.0 PERFORMANCE DETAILS

4.1 PERFORMANCE PERIOD

The Period of Performance (PoP) shall be 12-months with four (4) 12-month option periods for continued access to the SaaS. Contractor shall deliver 200 initial licenses. Upon Authority To

Operate (ATO) approval Contractor shall deliver 1,000 additional licenses. One (1) optional task is included for the purchase of additional user licenses.

Any work at the Government site shall not take place on Federal holidays or weekends unless directed by the Contracting Officer (CO).

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

Under current definitions, four are set by date:

https://www.voa.va.gov/DocumentListPublic.aspx?NodeId=28 https://www.voa.va.gov/DocumentView.aspx?DocumentID=4371 https://www.voa.va.gov/DocumentView.aspx?DocumentID=4411 https://www.voa.va.gov/DocumentView.aspx?DocumentID=4412

New Year's Day January 1

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 while training shall be conducted at Government facilities as reflected in section 4.3.

4.3 TRAVEL

The Government anticipates travel under this effort to perform the tasks associated with the effort, as well as to attend program-related meetings or conferences throughout the PoP. Include all estimated travel costs in your firm-fixed price line items. These costs will not be directly reimbursed by the Government.

The total estimated number of trips in support of the program related meetings for this effort is 9.

Anticipated locations include the following, estimated at 2 days in duration:

Location Period of Trip Number of Trips

1 St. Louis, MO ~1 per year of PoP up to 5

Eastern United States (US) Veterans

Integrated Service Network (VISN) 1 in base period

3 Western US VISN 1 in base period 1

4 Northern US VISN 1 in base period 1

5 Southern US VISN 1 in base period 1

5.0 SPECIFIC TASKS AND DELIVERABLES

The Contractor shall perform the following:

5.1 PROJECT MANAGEMENT

5.1.1 REPORTING REQUIREMENTS

The Contractor shall provide the COR 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. 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 and contractors remediation plans. The Contractor shall monitor performance against the CPMP and report any deviations. 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.

Deliverable:

A. Monthly Progress Report

5.1.2 TECHNICAL KICKOFF MEETING

The Contractor shall hold a technical kickoff meeting within 10 days after TO award. The

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

(3) calendar days after the meeting). The Contractor shall invite the Contracting Officer (CO), Contract Specialist (CS), COR, and the VA PM.

5.2 EH&S AUDITING SAAS SYSTEM SOLUTION

The Contractor shall provide access and EH&S Auditing SAAS System Solution Licenses to an

EH&S auditing system for approximately 1,200 initial users. This solution shall offer a broad

EH&S suite and management functionality to institute and manage the entire EH&S compliance assessment process and management system conformance assessment process; from field audits, workplace evaluations, and automated audit/findings report writing, through corrective action and management plans. The EH&S auditing system shall be configurable (modular) for tailoring solutions for specific VHA business processes and organizational work flows. The EH&S auditing system must allow access to the application for VHA personnel to provide role-based presentation: from simplest read-only access, to sophisticated configurations for administration and data/information entry. The SaaS EH&S auditing system must offer the following functional and technology requirements detailed in sections 5.2.1 and 5.2.2.

VHA will accept only a Commercial Off-The-Shelf (COTS) SaaS EH&S auditing system as defined in Federal Acquisition Regulations (FAR) Part 2.101. The system can be configurable to make it fully operational. Systems requiring development, customization or modifications to make the software operational is not desired and will not be accepted. The Contractor’s system must support mapping of the software to a VHA provided, complex organizational structure that includes varying user access and permissions.

The Contractor shall include unlimited, perpetual, non-exclusive software and interface site licenses for all products/services, further defined in the tasks included in this PWS. This shall include license and training for individual facilities defined by VHA.

The Contractor shall support the Government in becoming FedRamp compliant certification as well as obtaining and maintaining an Authority to Operate (ATO) in accordance with the Federal

Information Security Management Act, VA Directive and Handbook 6500, “Information

Security Program”, and VA Handbook 6500.3, “Assessment, Authorization, and

Continuous Monitoring of VA Information Systems,”.

A. EH&S Auditing SAAS System Solution Licenses

5.2.1 FUNCTIONAL REQUIREMENTS

EH&S auditing system shall:

a. Maintain EH&S audit source OSHA/EPA regulations/guidelines.

i. Be directly tied to regulatory citations.

ii. Update and validate regulatory citations and the associated EH&S audit criteria at a minimum semi-annually.

iii. Incorporate VHA defined/provided EH&S regulatory citations and focus areas.

b. Provide configurability

i. VHA defined focus areas auditing criteria statements.

ii. Create auditing checklists or guides

iii. Track multiple types of inspections/audits simultaneously (e.g. Internal, Environmental Protection Agency (EPA), Occupational Safety & Health

Administration (US), or other 3rd party outside agency inspections).

c. Access EH&S auditing data

i. Local (VA Medical Center or equivalent)

ii. Notify appropriate users via email when action needed and establish audit finding workflow and track abatement to completion.

iii. Allow facility level (local) to use for internal auditing without higher level

(regional or national) oversight.

iv. Regional (Veterans Integrated Service Network (VISN) or equivalent)

1. Notify appropriate users via email when action needed and establish audit finding workflow and track abatement to completion.

2. Allow for documenting Quality Assurance (QA) of audit findings

(local) prior to finalizing.

3. Allow for higher level approval of abatement plans (only for VHA

(national) mandated audits).

v. National

1. Ability to provide oversight and allow for documenting QA of audit findings prior to finalizing.

2. Ability to review and approve of abatement plans (only for VHA

(national) mandated audits).

d. Control EH&S auditing data.

i. Allow for documenting QA of audit findings prior to finalizing.

ii. Track open findings and abatement action progress in one plan.

iii. Have the ability to include photos and attachments in audits.

iv. Export to Microsoft Excel and Word.

v. Reports (Local, Regional, National)

1. Capability to configure standard audit reports generated from audit data.

2. Generate user defined ad hoc reports from audit data.

3. Capability to configure standard audit

Dashboard/Scorecard/Performance Measure.

e. Provide EH&S Auditing Administration Functions.

i. Provide 5 levels (minimum) of administrator access to support all organizational levels (program administrator, national, regional, local, audit finding manager, etc.)

ii. Maintain discontinued and archived audits.

iii. Auto-generate audit memos/letters (pre-audit, audit announcement, executive summary, final report).

iv. Store auditor’s electronic signatures for memo application.

v. Maintain a list of audit documents made available and reviewed prior to or during audits.

vi. Maintain a list of local Point-of-Contact (POCs) participating in audit.

vii. Allow for audit team selection from list of surveyors and facility staff.

5.2.2 TECHNOLOGY REQUIREMENTS

The EH&S Auditing System shall:

a. Include all User Documentation which shall include online help menus, user manuals, standard operating procedures, installation instructions, and data recovery procedures.

b. Meet NIST 800-53 Rev.3 requirements for Certification and Accreditation.

c. Meet moderate level Federal Risk and Authorization Management Program, or

FedRAMP, requirements. FedRAMP link: http://cloud.cio.gov/fedramp.

d. Utilize an internet application that shall remain fully accessible via standard web browsers with no plug-in requirements except Adobe Acrobat Reader thus maintaining no administrative client setup.

e. Utilize a data security interconnection infrastructure that shall address storage, generating, transmitting, and exchanging data.

f. Interfacing with common leading software platforms and operating systems.

A. User Documentation

5.2.3 UPGRADES AND ENHANCEMENTS TO SOFTWARE

Within 30 days after release the Contractor shall provide the latest upgrades/version changes/updates, enhancements and corrections to the SaaS EH&S auditing system that are customarily provided by the software publisher to its commercial customers so as to cause the system to perform according to its specifications, documentation or demonstrated claims.

Upgrades/version changes are defined as software improvements to the already existing software. Enhancements are defined as changes to improve efficiency of total system operation and not just software upgrades/version changes. The Contractor shall provide updates that are:

a. Initiated by the software publisher to improve functionality of the SaaS EH&S auditing system.

b. To maintain the SaaS EH&S auditing system compliant with new regulatory requirements.

The Contractor shall update all software and supporting electronic literature specified in section

5.2.2, as software updates are implemented. The Contractor shall limit the days and times the system is not available for use by scheduling updates during non-working days and hours as much as possible.

5.2.4 ACCEPTANCE TESTING

A minimum of 10 days prior to system “go-live” in a real-world environment, the Contractor shall submit a System Testing and Acceptance Plan to the COR for review and approval. The plan should test the functionality of the software, connectivity and operational readiness of users.

The VHA will provide test cases designed to stress the system capabilities. Any problems must be identified and be corrected by Contractor before the system can be re-tested. The system must pass the testing and be accepted prior to commencement of services and invoicing. As a minimum, the Contractor shall include and execute the following in the acceptance test plan:

a. Phase One testing shall demonstrate each facility’s interface/access and verify conductivity and that there is no degradation to the system response.

b. Phase Two testing shall demonstrate the analytical data input, extraction and reporting capability of the SaaS EH&S auditing system.

c. Phase Three testing shall demonstrate end-to-end functionality of SaaS EH&S auditing system.

A. System Testing and Acceptance Plan

5.2.5 EMERGENCY OPERATIONS

The Contractor shall possess and keep current and test disaster recovery and failover capabilities to mitigate the occurrence of hardware and software failure, power outages, and disruptions that may be caused by natural occurrence (such as hurricanes, tornadoes, earthquakes, etc.). The

Contractor shall provide remote location system roll over function of the system and backup of all software and data.

5.2.6 HELP DESK SUPPORT

a. The VHA will provide Tier I (Basic) user support affiliated with basic system functions (administrator assignments/accounts, system/site/location hierarchy maintenance, etc.). The Contractor shall provide Tier II (Advanced) Help Desk support to VHA users, of all aspects of the service purchased under this contract.

b. The Contractor shall provide Tier 2 Help Desk support via phone, email and/or chat accessible for VHA users from Monday through Friday between the hours of

8:00 AM Eastern Time and 5:00 PM Pacific Time, excluding federal holidays.

Help Desk support shall be available 24/7 during times of National Crisis either man-made or natural to support the Nation Response Framework Plan.

5.2.7 SYSTEM ADMINISTRATION

a. The Contractor shall provide maintenance and support services as further defined herein.

b. Upon completion of the installation, training, final acceptance testing the

Contractor shall provide all maintenance and support services to ensure that the

SaaS EH&S auditing system continues to function 99.0% of the time 24 hours per day 365 days per year. "System Availability" shall not include any minutes of downtime resulting from:

i. Scheduled maintenance pre-approved by the VA,

ii. Events of force majeure,

iii. Malicious attacks on the system,

iv. Issues associated with VA’s computing devices, local area networks or internet service provider connections, or

v. Contractor’s inability to deliver services because of VA’s acts or omissions.

c. All new software versions shall be covered in the maintenance services, including all subsequent versions designed to replace the version installed under this contract.

d. Maintenance and systems support (Tier II Help Desk) shall be provided during the entire contract period as well as during any contract authorized option extension periods, further defined in para. (s).

e. The Contractor shall distribute maintenance notification updates or releases by using an appropriate electronic or printed media to the COR.

f. Sixty (60) day prior to the expiration of each contract period the Contractor shall validate that the system’s user information for surveyors and users is accurate as of that date. The Contractor shall:

i. Compile a list of valid users and delete users that no longer have a valid email addresses;

ii. Coordinate the list with the COR;

iii. Update the coordinated list and that number is used to true-up the number of users utilized for computation of any license for the upcoming option year of the contract.

g. Forty-five (45) day prior to the expiration of each contract period the Contractor shall work with the COR to ensure the Government has access to all data generated under this contract, and the data shall be made available for export to an existing VHA database/server or the Contractor shall deliver to VHA a source dataset on the electronic media of their choice. The Government data and source dataset shall not be in a proprietary format.

5.2.8 INITIAL USER TRAINING

Prior to the “go-live” date, the Contractor shall provide on-site and web-based technical, end-user training on the use and operations of the software IAW the Contractor’s Integrated

Master Schedule. Final dates and times for all training at each location shall be agreed upon between the Contractor and the COR. The Contractor shall provide the COR an electronic list of persons who attended each training event.

a. Initial Surveyor/Administrator training.

i. Classroom based training. The Contractor shall provide a minimum of one (1) instructor to provide training to approximately 18 students per class (minimum of 10, maximum of 25), on-site at four (4) separate regional locations identified below. Classes shall each be approximately two (2) days in length. Breaks shall be scheduled every two (2) hours and a lunch break must be incorporated into the schedule. Total number of

Surveyors to be trained is estimated to be 90. VHA will provide the final number of personnel to be trained to the Contractor at time of kick of meeting .

ii. Objectives for Surveyor/Administrator (VISN IH, Safety, Green

Environmental Management System [GEMS], etc.) training. The following are minimum topics to be covered during training. The

Contractor shall provide training sufficient for…