36C26120Q0190-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 79

612-20-1-193-0004

36C26120Q0190 01-29-2020

Moneque Rodriguez 808-539-1304 02-12-2020

11:59PM

Department of Veterans Affairs VA Sierra Pacific Network (VISN 21) VA Pacific Islands Health Care System 459 Patterson Rd Honolulu HI 96819-1522

X 100

X

Y

541519

$30 Million

N/A

X

Department of Veterans Affairs VA Sierra Pacific Network (VISN 21) VA Northern California HealthCare System

VA Sierra Pacific Network (VISN 21) VA Pacific Islands Health Care System 459 Patterson Rd Honolulu HI 96819-1522

FMS VA-9(101) Financial Services Center

PO Box 149971 Austin TX 78714-9971

See CONTINUATION Page

Labor Management Staffing Software with training and install

Base: The base year is for a period of 12 months from date of delivery and acceptance.

Option Year I: Option Year I is for a period of 12 months from the end of the Base Year.

Option Year II: Option Year II is for a period of 12 months from the end of Option Year I.

Option Year III: Option Year III is for a period of 12 month from the end of the Option Year II.

Option Year IV: Option Year IV is for a period of 12 months from the end of the Option Year III.

***Please bring attention to Addendum to FAR 52.212-1 Instructions to Offerors***

See CONTINUATION Page

X X

X one

Mandy Thompson

36C26120Q0190

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

STATEMENT OF WORK

B.2 PRICE/COST SCHEDULE

ITEM INFORMATION

B.3 DELIVERY SCHEDULE

SECTION C - CONTRACT CLAUSES

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

2018) FAR 52.204-26 Covered Telecommunications Equipment or Services-Representation. 34

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

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

C.4 52.219-6 NOTICE OF TOTAL SMALL BUSINESS SET-ASIDE (DEVIATION 2019-

01)

C.5 52.219-14 LIMITATIONS ON SUBCONTRACTING (DEVIATION 2019-01)

C.6 VAAR 852.203-70 COMMERCIAL ADVERTISING (MAY 2018)

C.7 VAAR 852.215-71 EVALUATION FACTOR COMMITMENTS (OCT 2019)

C.8 VAAR 852.219-74 LIMITATIONS ON SUBCONTRACTING—MONITORING AND

COMPLIANCE (JUL 2018)

C.9 VAAR 852.219-75 SUBCONTRACTING COMMITMENTS MONITORING AND

COMPLIANCE (JUL 2018)

C.10 VAAR 852.232-72 ELECTRONIC SUBMISSION OF PAYMENT REQUESTS

(NOV 2018)

C.11 VAAR 852.246-71 REJECTED GOODS (OCT 2018)

C.12 VAAR 852.247-71 DELIVERY LOCATION (OCT 2018)

C.13 VAAR 852.247-73 PACKING FOR DOMESTIC SHIPMENT (OCT 2018)

C.14 VAAR 852.270-1 REPRESENTATIVES OF CONTRACTING OFFICERS (JAN

2008)

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

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

STATUTES OR EXECUTIVE ORDERS—COMMERCIAL ITEMS (OCT 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.204-24 REPRESENTATION REGARDING CERTAIN TELECOMMUNICATIONS

AND VIDEO SURVEILLANCE SERVICES OR EQUIPMENT (AUG 2019)

E.3 52.204-25 PROHIBITION ON CONTRACTING FOR CERTAIN

TELECOMMUNICATIONS AND VIDEO SURVEILLANCE SERVICES OR EQUIPMENT

(AUG 2019)

E.4 52.214-21 DESCRIPTIVE LITERATURE (APR 2002)

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

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

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

OWNED SMALL BUSINESS EVALUATION FACTORS (OCT 2019)

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

(OCT 2018)

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

E.10 52.252-1 SOLICITATION PROVISIONS INCORPORATED BY REFERENCE

(FEB 1998)

E.11 52.212-2 EVALUATION—COMMERCIAL ITEMS (OCT 2014)

E.12 52.212-3 OFFEROR REPRESENTATIONS AND CERTIFICATIONS—

COMMERCIAL ITEMS (OCT 2018)

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:

b. GOVERNMENT: Contracting Officer 36C261 Mandy Thompson

Department of Veterans Affairs

VA Sierra Pacific Network (VISN 21)

VA Pacific Islands Health Care System

459 Patterson Rd

Honolulu HI 96819-1522

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 Delivery and Acceptance

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.

Department of Veterans Affairs

FMS VA-9(101) Financial Services Center

PO Box 149971

Austin TX 78714-9971

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

AMENDMENT NO DATE

STATEMENT OF WORK

Northern California Healthcare System (NCHCS)

Labor Management Software and Implementation

Introduction:

This request seeks a solution to automate scheduling and staffing processes; provide decision support for staff assignments based on the objective and variable data;

improve patient care by matching nursing competency to required needs. Contractor software shall provide self-scheduling options to nursing providers and data for outcome measurements. Pull data from Veterans Health Information Systems and Technology Architecture (VistA); Decision Support System (DSS); VA Nursing Outcomes Database (VANOD) and Paid Enhancement for VANOD (PEV); Office of Nursing Service (ONS) to create strategic plans based on retrievable and accurate data. The system shall accommodate today’s increasing staffing challenges by using 21st century technology.

This system will accommodate all NCHCS facilities and VA staffed Community Based Out Patient Clinic (CBOC)/Out Patient Clinic (OPC) (Auburn, Chico, David Grant Medical Center, Fairfield, Martinez, McClellan, Mare Island, Oakland, Redding, Sacramento, Yreka, and Yuba City).

The system shall automate labor intensive time consuming processes that are now manually interfaced with multiple applications that increase efficiencies, data quality, and to support decision making. Staffing schedules are currently created several weeks in advance; however, as a patient population and available resources can change in a matter of hours, it is critical to have access to employee information to be able adjust staffing arrangements to manage the clinical nursing needs of Veterans and to facilitate communication in changing needs within the facility and with the employees. Because nursing care is delivered 24 hours/7 days a week, ability to access and modify scheduling by managers, supervisors and chiefs are needed.

Resource management not only involves staff planning, but also scores of managerial tasks including adherence to directives limiting hours of work in each period, regulatory dictates, and special pay and time accounting accordance to defined payment schedules. Nurses functioning as managers must have the flexibility to determine the appropriate level of nurses/nursing staff for patient care needs while considering a constellation of important variables, including the various education scope of practice and experience levels of staff. The number of staffing orientation, the number of temporary staff on the unit, the acuity of patients, anticipated acuity on a shift, the physical layout of the unit, the availability of hospital resources, the technology on the unit, and the unit turbulence (such as the number of admissions, discharges and transfers.) Potential use in other Services is under consideration.

Objectives:

There is a need for an acuity/patient classification system to match the changing care needs of the patients to the appropriate staffing level based on the patient condition and the amount of nursing required to manage the care of each patient.

Hospital based staffing requires a 24-hour coverage a day, 7 days a week. Nursing staff work a variety of shifts that require an hourly rate increase, and contract/agency and travel nurses all have different compensation requirements. Therefore, a Staff Scheduling system needs to accurately correlate and calculate time and cost by work unit, nurse's type and pay variables.

Nurse executives need data to plan for current and future staff needs and costs; this system gives them the tools to help manage their workforce. Multiple standardized reports are needed as well as the ability to create ad hoc reports.

Scope of Work

An integrated system and automated data extraction tools are necessary to effectively assign staffing resources and monitor standards of care. This system will pull from systems that have data stored to avoid duplicate effort and to feed the other downstream data systems.

The primary use of the system will be staffing scheduling, so managers can coordinate schedules, capture data, produce reports, and coordinate work assignments to meet patient care needs. The primary users of the system are nurse managers, supervisors, service chief and secretaries, who will coordinate schedules, capture data, produce reports, and coordinate work assignments.

Tasks or Requirements

Appropriate response to the fluctuations in patient census and acuities by using embedded decision support tools.

Adequate staffing levels based on patient acuity and other care related variables.

Collection of nationally comparable hours per patient day (HPPD) data.

Collection of data to prepare staffing reports, develop strategic plans and improve hiring practices.

Compliance with public law and other regulatory mandates for staffing regulations and monitors.

Ability to consolidate multiple administrative needs in one package (licensure, certifications, emergency notifications, etc.) Generation of predefined and adhoc reports.

Self-scheduling ability (major nursing satisfier).

Accurate accounting of contract/agency nursing utilization. Success factors:

production of accurate HPPD data, increase in efficiencies in managing staffing scheduling issues by 50%.

Selection Criteria

Vendor must meet or exceed all requirements as specified below.

Deliverables or Deliver Schedule

Specifications:

1. Utilizes an HL7 interface with Vista/Windows 10 that brings in real-time Admit, Discharge, and Transfer information. Utilizes an HR interface that brings in several points of data validation for VANOD including series, position, grade, step, licensure information, EOD, degrees, other schooling, BOC, ALBCC, Occupation Series Code and more. Utilizes the census interface to correlate with budgeting and reporting to databases like VANOD, DSS, NDNQI and more.

2. Ensure accurate NHPPD Calculation to Ensure Compliance with the Veterans Health Administration published Directive 2010-034 to provide a national standard for the staffing of patient care units.

Required Functional capabilities:

1. An automated staffing package is required to provide:

Demographic Tracking tools: maintains employee contact/ emergency contact information.

Maintains employee-preferred method of communication.

Vendor shall provide any software updates and installation as they become available.

Accurate calculation of Nursing Hours Per Patient Day (NHPPD) requires determining the actual hours of Direct care on each unit.

2. Staffing Scheduling Tools Maintain prospective schedules.

Audit trails for changes to the system Schedules can be created prospective across 12-month period.

Allow staff to switch shifts amongst peers Allow staff to make themselves available for overtime and advise of current

OT use in comparison to regular clients Manage Position Control

3. Proficiency System:

Ability to staff and maintain repositories of anecdotal notes for proficiency input, specialty certification tracking, licensure tracking, education (all degrees earned) tracking, skill based competencies tracking, ACLS/BLS/131.5 tracking, and continuing education tracking. Mandatory tracking, mandatory health information. Tools for staff to self- report professional portfolio.

4. Rule engines to facilitate scheduling:

Apply regulations (hour limits, time off requirements, staffing ratios, etc.) as they apply to individuals being scheduled to work.

Apply union requirements stored in the system to create staffing schedules Use staff preferences to create staffing schedules.

Match competencies to staffing needs. Match nursing staff with patient needs across the system while maintaining balanced patient workloads.

Apply unit preference to competencies, e.g. ICU nurses are ACLS certified.

Apply permanent schedules requests to when generating schedules.

Apply rotating shifts rules when generating schedules.

Capabilities to accommodate scheduling changes based on patient census scheduling.

Apply patient acuities to staffing needs.

Track hours per patient day.

Generate alternate work schedules.

Capability to allow or restrict swapping unit assignments based on competencies.

Capabilities to restrict overtime assignment based on regulations I. Predict staffing needs based on previous trends (i.e. high surgery days) Provide functionality to maintain disaster preparedness (notifications and call-backs).

5. Communication Tools:

Creates a personalized web-based dashboard for all stakeholders.

Web-based for employee access.

Web-based for managers access for staff bidding.

Staff bidding on open positions (Staff to staff communication, e.g. to swap shifts).

Exchange shifts between co-workers.

Alert applicants for checking status.

Produce real time reports for long-term strategy for hiring staff.

6. Training/Implementation

Vendor to provide on-site training at each facility to super users on general functionality, staff scheduling for end-users, and management reports for resource analysis.

On-site implementation of the system is required as follows:

Project Definition

Establishing Project Goals Assigning Project Roles & Workgroups Define Interfaces Workload Define and Document Existing Workflow Processes Label configuration of job codes and units and leave schedules Present Projections for Workflow Process

System Configuration System Administrator Training Security Configuration Workload and Unit Budget Validate Interface Data

User Training Pilot Unit Training User Training System-Wide Project Role Out Employee Access Position Tracking

Courses and Consultation Staffing Methodology Class Executive Analytics Class Reports Workshop Data Mining & Scorecards Set Up Alerts

7. Interoperability with CERNER

Government-Furnished Equipment and Government-Furnished Information

Utilizes VA computer workstations, laptops, monitors Due to PII, employee data will be stored on VA servers, behind the VA firewall which can be accessed through a VPN tunnel.

Security

VISTA Interface, access to employee and patient information General Information Security Requirements:

o Contractors, contractor personnel, subcontractors, and subcontractor personnel shall be subject to the same Federal laws, regulations, standards, and VA Directives and Handbooks as VA and VA personnel regarding information and information system security.

o Access to VA Information and VA Information Systems o A contractor/sub-contractor shall request logical (technical) or physical access to

VA information and VA information systems for their employees, subcontractors, and affiliates only to the extent necessary to perform the services specified in the contract, agreement, or task order.

o All contractors, subcontractors, and third-party servicers and associates working with VA information are subject to the same investigative requirements as those of VA appointees or employees who have access to the same types of information. The level and process of background security investigations for contractors must be in accordance with VA Directive and Handbook 0710, Personnel Suitability and Security Program. The Office for Operations, Security, and Preparedness is responsible for these policies and procedures.

o Contract personnel who require access to national security programs must have a valid security clearance. National Industrial Security Program (NISP) was established by Executive Order 12829 to ensure that cleared U.S. defense industry contract personnel safeguard the classified information in their possession while performing work on contracts, programs, bids, or research and development efforts. The Department of Veterans Affairs does not have a Memorandum of Agreement with Defense Security Service (DSS). Verification of a Security Clearance must be processed through the Special Security Officer located in the Planning and National Security Service within the Office of Operations, Security, and Preparedness.

o Custom software development and outsourced operations must be in the U.S. to the maximum extent practical. If such services are proposed to be performed abroad and are not disallowed by other VA policy or mandates, the contractor/subcontractor must state where all non-U.S. services are provided and detail a security plan, deemed to be acceptable by VA, specifically to address mitigation of the resulting problems of communication, control, data protection, and so forth. Location within the U.S. may be an evaluation factor.

o The contractor or subcontractor must notify the Contracting Officer immediately when an employee working on a VA system or with access to VA information is reassigned or leaves the contractor or subcontractor’s employ. The Contracting Officer must also be notified immediately by the contractor or subcontractor prior to an unfriendly termination.

Place of Performance

Northern California Healthcare System

Auburn

11985 Heritage Oaks Place

Suite 100

Auburn, CA 95603-2413

Chico VA Clinic

1601 Concord Avenue

Chico, CA 95928-9486

David Grant Medical Center –

103 Bodin Circle

Building 778

Travis AFB, CA 94535-1801

Fairfield VA Clinic

103 Bodin Circle

Building 778

Travis AFB, CA 94535-1801

Martinez VA Medical Center

150 Muir Road

Martinez, CA 94553-4668

McClellan VA Clinic

5342 Dudley Boulevard

Building 88

McClellan Park, CA 95652-1012

Mare Island VA Clinic

201 Walnut Avenue

Building 201

Mare Island, CA 94592-1107

Oakland VA Clinic

2221 Martin Luther King Jr. Way

Oakland, CA 94612-1318

Redding VA Clinic

351 Hartnell Avenue

Redding, CA 96002-1845

Sacramento

10535 Hospital Way

Mather, CA 95655-4200

Yreka VA Clinic

101 East Oberlin Road

Yreka, CA 96097-9645

Yuba City VA Clinic

425 Plumas Boulevard

Yuba City, CA 95991-5074

Hours of Operation

Normal hours of operation are Monday through Friday from 8:00 am to 4:30 pm, excluding holidays

All work must be scheduled in advance with the COR on a mutually agreed upon date and time.

Emergency services required shall be coordinated through the COR. Contractor must be available to perform emergency services within 3 hours of notification.

Federal Holidays observed by the VAMC are:

New Years’ Day Labor Day

Martin Luther King Day Columbus Day

Presidents’ Day Veterans’ Day

Memorial Day Thanksgiving Day

Independence Day Christmas Day

Records Management Requirements

1. Citations to pertinent laws, codes and regulations such as 44 U.S.C chapters 21, 29, 31 and 33; Freedom of Information Act (5 U.S.C. 552); Privacy Act (5 U.S.C. 552a); 36 CFR Part 1222 and Part 1228.

2. Contractor shall treat all deliverables under the contract as the property of the U.S.

Government for which the Government Agency shall have unlimited rights to use, dispose of, or disclose such data contained therein as it determines to be in the public interest.

3. Contractor shall not create or maintain any records that are not specifically tied to or authorized by the contract using Government IT equipment and/or Government records.

4. Contractor shall not retain, use, sell, or disseminate copies of any deliverable that contains information covered by the Privacy Act of 1974 or that which is generally protected by the Freedom of Information Act.

5. Contractor shall not create or maintain any records containing any Government Agency records that are not specifically tied to or authorized by the contract.

6. The Government Agency owns the rights to all data/records produced as part of this contract.

7. The Government Agency owns the rights to all electronic information (electronic data, electronic information systems, electronic databases, etc.) and all supporting documentation created as part of this contract. Contractor must deliver sufficient technical documentation with all data deliverables to permit the agency to use the data.

8. Contractor agrees to comply with Federal and Agency records management policies, including those policies associated with the safeguarding of records covered by the Privacy Act of 1974. These policies include the preservation of all records created or received regardless of format [paper, electronic, etc.] or mode of transmission [e-mail, fax, etc.] or state of completion [draft, final, etc.].

9. No disposition of documents will be allowed without the prior written consent of the Contracting Officer. The Agency and its contractors are responsible for preventing the alienation or unauthorized destruction of records, including all forms of mutilation. Willful and unlawful destruction, damage or alienation of Federal records is subject to the fines and penalties imposed by 18 U.S.C. 2701. Records may not be removed from the legal custody of the Agency or destroyed without regard to the provisions of the agency records schedules.

10. Contractor is required to obtain the Contracting Officer's approval prior to engaging in any contractual relationship (sub-contractor) in support of this contract requiring the disclosure of information, documentary material and/or records generated under, or relating to, this contract. The Contractor (and any sub-contractor) is required to abide by Government and Agency guidance for protecting sensitive and proprietary information.

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 Order but only if both parties expressly make them an addendum. 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 Order; this includes, but is not limited to, any agreement embedded in the computer software (clickwrap) or 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 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 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 Order. Federal law and regulation, including without limitation, the Contract Disputes Act (41 U.S.C. §601- 613), the Anti-Deficiency Act (31 U.S.C. §1341 et seq.), the Competition in Contracting Act (41 U.S.C. §253), the Prompt Payment Act (31 U.S.C. §3901, et seq.) 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 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 Order must be made by order modification (Standard Form 30). Nothing in this Order or any commercial license agreement shall be construed as a waiver of sovereign immunity.

IT CONTRACT SECURITY

VA INFORMATION AND INFORMATION SYSTEM SECURITY/PRIVACY

1. GENERAL

Contractors, contractor personnel, subcontractors, and subcontractor personnel shall be subject to the same Federal laws, regulations, standards, and VA Directives and Handbooks as VA and VA personnel regarding information and information system security.

2. ACCESS TO VA INFORMATION AND VA INFORMATION SYSTEMS

a. A contractor/subcontractor shall request logical (technical) or physical access to VA information and VA information systems for their employees, subcontractors, and affiliates only to the extent necessary to perform the services specified in the contract, agreement, or task order.

b. All contractors, subcontractors, and third-party servicers and associates working with VA information are subject to the same investigative requirements as those of VA appointees or employees who have access to the same types of information. The level and process of background security investigations for contractors must be in accordance with VA Directive and Handbook 0710, Personnel Suitability and Security Program. The Office for Operations, Security, and Preparedness is responsible for these policies and procedures.

c. Contract personnel who require access to national security programs must have a valid security clearance. National Industrial Security Program (NISP) was established by Executive Order 12829 to ensure that cleared U.S. defense industry contract personnel safeguard the classified information in their possession while performing work on contracts, programs, bids, or research and development efforts. The Department of Veterans Affairs does not have a Memorandum of Agreement with Defense Security Service (DSS). Verification of a Security Clearance must be processed through the Special Security Officer located in the Planning and National Security Service within the Office of Operations, Security, and Preparedness.

d. Custom software development and outsourced operations must be located in the U.S. to the maximum extent practical. If such services are proposed to be performed abroad and are not disallowed by other VA policy or mandates, the contractor/subcontractor must state where all non-U.S. services are provided and detail a security plan, deemed to be acceptable by VA, specifically to address mitigation of the resulting problems of communication, control, data protection, and so forth. Location within the U.S. may be an evaluation factor.

e. The contractor or subcontractor must notify the Contracting Officer immediately when an employee working on a VA system or with access to VA information is reassigned or leaves the contractor or subcontractor's employ. The Contracting Officer must also be notified immediately by the contractor or subcontractor prior to an unfriendly termination.

3. VA INFORMATION CUSTODIAL LANGUAGE

a. Information made available to the contractor or subcontractor by VA for the performance or administration of this contract or information developed by the contractor/subcontractor in performance or administration of the contract shall be used only for those purposes and shall not be used in any other way without the prior written agreement of the VA. This clause expressly limits the contractor/subcontractor's rights to use data as described in Rights in Data - General, FAR 52.227-14(d) (1).

b. VA information should not be co-mingled, if possible, with any other data on the contractors/subcontractor's information systems or media storage systems in order to ensure VA requirements related to data protection and media sanitization can be met. If co-mingling must be allowed to meet the requirements of the business need, the contractor must ensure that VA's information is returned to the VA or destroyed in accordance with VA's sanitization requirements. VA reserves the right to conduct on site inspections of contractor and subcontractor IT resources to ensure data security controls, separation of data and job duties, and destruction/media sanitization procedures are in compliance with VA directive requirements.

c. Prior to termination or completion of this contract, contractor/ subcontractor must not destroy information received from VA, or gathered/ created by the contractor in the course of performing this contract without prior written approval by the VA. Any data destruction done on behalf of VA by a contractor/subcontractor must be done in accordance with National Archives and Records Administration (NARA) requirements as outlined in VA Directive 6300, Records and Information Management and its Handbook 6300.1 Records Management Procedures, applicable VA Records Control Schedules, and VA Handbook 6500.1, Electronic Media Sanitization. Self-certification by the contractor that the data destruction requirements above have been met must be sent to the VA Contracting Officer within 30 days of termination of the contract.

d. The contractor/subcontractor must receive, gather, store, back up, maintain, use, disclose and dispose of VA information only in compliance with the terms of the contract and applicable Federal and VA information confidentiality and security laws, regulations and policies. If Federal or VA information confidentiality and security laws, regulations and policies become applicable to the VA information or information systems after execution of the contract, or if NIST issues or updates applicable FIPS or Special Publications (SP) after execution of this contract, the parties agree to negotiate in good faith to implement the information confidentiality and security laws, regulations and policies in this contract.

e. The contractor/subcontractor shall not make copies of VA information except as authorized and necessary to perform the terms of the agreement or to preserve electronic information stored on contractor/subcontractor electronic storage media for restoration in case any electronic equipment or data used by the contractor/subcontractor needs to be restored to an operating state. If copies are made for restoration purposes, after the restoration is complete, the copies must be appropriately destroyed.

f. If VA determines that the contractor has violated any of the information confidentiality, privacy, and security provisions of the contract, it shall be sufficient grounds for VA to withhold payment to the contractor or third party or terminate the contract for default or terminate for cause under Federal Acquisition Regulation (FAR) part 12.

g. If a VHA contract is terminated for cause, the associated BAA must also be terminated and appropriate actions taken in accordance with VHA Handbook 1600.01, Business Associate Agreements. Absent an agreement to use or disclose protected health information, there is no business associate relationship.

h. The contractor/subcontractor must store, transport, or transmit VA sensitive information in an encrypted form, using VA-approved encryption tools that are, at a minimum, FIPS 140-2 validated.

i. The contractor/subcontractor's firewall and Web services security controls, if applicable, shall meet or exceed VA's minimum requirements. VA Configuration Guidelines are available upon request.

j. Except for uses and disclosures of VA information authorized by this contract for performance of the contract, the contractor/subcontractor may use and disclose VA information only in two other situations: (i) in response to a qualifying order of a court of competent jurisdiction, or (ii) with VA's prior written approval. The contractor/subcontractor must refer all requests for, demands for production of, or inquiries about, VA information and information systems to the VA contracting officer for response.

k. Notwithstanding the provision above, the contractor/subcontractor shall not release VA records protected by Title 38 U.S.C. 5705, confidentiality of medical quality assurance records and/or Title 38 U.S.C. 7332, confidentiality of certain health records pertaining to drug addiction, sickle cell anemia, alcoholism or alcohol abuse, or infection with human immunodeficiency virus.

If the contractor/subcontractor is in receipt of a court order or other requests for the above mentioned information, that contractor/subcontractor shall immediately refer such court orders or other requests to the VA contracting officer for response.

l. For service that involves the storage, generating, transmitting, or exchanging of VA sensitive information but does not require C&A or an MOU-ISA for system interconnection, the contractor/subcontractor must complete a Contractor Security Control Assessment (CSCA) on a yearly basis and provide it to the COR.

4. INFORMATION SYSTEM DESIGN AND DEVELOPMENT

a. Information systems that are designed or developed for or on behalf of VA at non-VA facilities shall comply with all VA directives developed in accordance with FISMA, HIPAA, NIST, and related VA security and privacy control requirements for Federal information systems. This includes standards for the protection of electronic PHI, outlined in 45 C.F.R. Part 164, Subpart C, information and system security categorization level designations in accordance with FIPS 199 and FIPS 200 with implementation of all baseline security controls commensurate with the FIPS 199 system security categorization (reference Appendix D of VA Handbook 6500, VA Information Security Program). During the development cycle a Privacy Impact Assessment (PIA) must be completed, provided to the COR, and approved by the VA Privacy Service in accordance with Directive 6507, VA Privacy Impact Assessment.

b. The contractor/subcontractor shall certify to the COR that applications are fully functional and operate correctly as intended on systems using the VA Federal Desktop Core Configuration (FDCC), and the common security configuration guidelines provided by NIST or the VA. This includes Internet Explorer 7 configured to operate on Windows XP and Vista (in Protected Mode on Vista) and future versions, as required.

c. The standard installation, operation, maintenance, updating, and patching of software shall not alter the configuration settings from the VA approved and FDCC configuration. Information technology staff must also use the Windows Installer Service for installation to the default "program files" directory and silently install and uninstall.

d. Applications designed for normal end users shall run in the standard user context without elevated system administration privileges.

e. The security controls must be designed, developed, approved by VA, and implemented in accordance with the provisions of VA security system development life cycle as outlined in NIST Special Publication 800-37, Guide for Applying the Risk Management Framework to Federal Information Systems, VA Handbook 6500, Information Security Program and VA Handbook 6500.5, Incorporating Security and Privacy in System Development Lifecycle.

f. The contractor/subcontractor is required to design, develop, or operate a System of Records Notice (SOR) on individuals to accomplish an agency function subject to the Privacy Act of 1974, (as amended), Public Law 93-579, December 31, 1974 (5 U.S.C. 552a) and applicable agency regulations. Violation of the Privacy Act may involve the imposition of criminal and civil penalties.

g. The contractor/subcontractor agrees to:

(1) Comply with the Privacy Act of 1974 (the Act) and the agency rules and regulations issued under the Act in the design, development, or operation of any system of records on individuals to accomplish an agency function when the contract specifically identifies:

(a) The Systems of Records (SOR); and

(b) The design, development, or operation work that the contractor/ subcontractor is to perform;

(1) Include the Privacy Act notification contained in this contract in every solicitation and resulting subcontract and in every subcontract awarded without a solicitation, when the work statement in the proposed subcontract requires the redesign, development, or operation of a SOR on individuals that is subject to the Privacy Act; and

(2) Include this Privacy Act clause, including this subparagraph (3), in all subcontracts awarded under this contract which requires the design, development, or operation of such a

SOR.

h. In the event of violations of the Act, a civil action may be brought against the agency involved when the violation concerns the design, development, or operation of a SOR on individuals to accomplish an agency function, and criminal penalties may be imposed upon the officers or employees of the agency when the violation concerns the operation of a SOR on individuals to accomplish an agency function. For purposes of the Act, when the contract is for the operation of a SOR on individuals to accomplish an agency function, the contractor/subcontractor is considered to be an employee of the agency.

(1) "Operation of a System of Records" means performance of any of the activities associated with maintaining the SOR, including the collection, use, maintenance, and dissemination of records.

(2) "Record" means any item, collection, or grouping of information about an individual that is maintained by an agency, including, but not limited to, education, financial transactions, medical history, and criminal or employment history and contains the person's name, or identifying number, symbol, or any other identifying particular assigned to the individual, such as a fingerprint or voiceprint, or a photograph.

(3) "System of Records" means a group of any records under the control of any agency from which information is retrieved by the name of the individual or by some identifying number, symbol, or other identifying particular assigned to the individual.

i. The vendor shall ensure the security of all procured or developed systems and technologies, including their subcomponents (hereinafter referred to as "Systems"), throughout the life of this contract and any extension, warranty, or maintenance periods. This includes, but is not limited to workarounds, patches, hotfixes, upgrades, and any physical components (hereafter referred to as Security Fixes) which may be necessary to fix all security vulnerabilities published or known to the vendor anywhere in the Systems, including Operating Systems and firmware. The vendor shall ensure that Security Fixes shall not negatively impact the Systems.

j. The vendor shall notify VA within 24 hours of the discovery or disclosure of successful exploits of the vulnerability which can compromise the security of the Systems (including the confidentiality or integrity of its data and operations, or the availability of the system). Such issues shall be remediated as quickly as is practical, but in no event longer than 10 days.

k. When the Security Fixes involve installing third party patches (such as Microsoft OS patches or Adobe Acrobat), the vendor will provide written notice to the VA that the patch has been validated as not affecting the Systems within 10 working days. When the vendor is responsible for operations or maintenance of the Systems, they shall apply the Security Fixes within 5 days.

l. All other vulnerabilities shall be remediated as specified in this paragraph in a timely manner based on risk, but within 60 days of discovery or disclosure. Exceptions to this paragraph (e.g.

for the convenience of VA) shall only be granted with approval of the contracting officer and the VA Assistant Secretary for Office of Information and Technology.

5. INFORMATION SYSTEM HOSTING, OPERATION, MAINTENANCE, OR USE

a. For information systems that are hosted, operated, maintained, or used on behalf of VA at non-VA facilities, contractors/subcontractors are fully responsible and accountable for ensuring compliance with all HIPAA, Privacy Act, FISMA, NIST, FIPS, and VA security and privacy directives and handbooks. This includes conducting compliant risk assessments, routine vulnerablity scanning, system patching and change management procedures, and the completion of an acceptable contingency plan for each system. The contractor's security control procedures must be equivalent, to those procedures used to secure VA systems. A Privacy Impact Assessment (PIA) must also be provided to the COR and approved by VA Privacy Service prior to operational approval. All external Internet connections to VA's network involving VA information must be reviewed and approved by VA prior to implementation.

b. Adequate security controls for collecting, processing, transmitting, and storing of Personally Identifiable Information (PII), as determined by the VA Privacy Service, must be in place, tested, and approved by VA prior to hosting, operation, maintenance, or use of the information system, or systems by or on behalf of VA. These security controls are to be assessed and stated within the PIA and if these controls are determined not to be in place, or inadequate, a Plan of Action and Milestones (POA&M) must be submitted and approved prior to the collection of PII.

c. Outsourcing (contractor facility, contractor equipment or contractor staff) of systems or network operations, telecommunications services, or other managed services requires certification and accreditation (authorization) (C&A) of the contractor's systems in accordance with VA Handbook 6500.3, Certification and Accreditation and/or the VA OCS Certification Program Office. Government- owned (government facility or government equipment) contractor-operated systems, third party or business partner networks require memorandums of understanding and interconnection agreements (MOU-ISA) which detail what data types are shared, who has access, and the appropriate level of security controls for all systems connected to VA networks.

d. The contractor/subcontractor's system must adhere to all FISMA, FIPS, and NIST standards related to the annual FISMA security controls assessment and review and update the PIA. Any deficiencies noted during this assessment must be provided to the VA contracting officer and the ISO for entry into VA's POA&M management process. The contractor/subcontractor must use VA's POA&M process to document planned remedial actions to address any deficiencies in information security policies, procedures, and practices, and the completion of those activities. Security deficiencies must be corrected within the timeframes approved by the government. Contractor/subcontractor procedures are subject to periodic, unannounced assessments by VA officials, including the VA Office of Inspector General. The physical security aspects associated with contractor/ subcontractor activities must also be subject to such assessments. If major changes to the system occur that may affect the privacy or security of the data or the system, the C&A of the system may need to be reviewed, retested and re- authorized per VA Handbook 6500.3. This may require reviewing and updating all of the documentation (PIA, System Security Plan, Contingency Plan). The Certification Program Office can provide guidance on whether a new C&A would be necessary.

e. The contractor/subcontractor must conduct an annual self assessment on all systems and outsourced services as required. Both hard copy and electronic copies of the assessment must be provided to the COR. The government reserves the right to conduct such an assessment using government personnel or another contractor/subcontractor. The contractor/subcontractor must take appropriate and timely action (this can be specified in the contract) to correct or mitigate any weaknesses discovered during such testing, generally at no additional cost.

f. VA prohibits the installation and use of personally-owned or contractor/ subcontractor-owned equipment or software on VA's network. If non-VA owned equipment must be used to fulfill the requirements of a contract, it must be stated in the service agreement, SOW or contract. All of the security controls required for government furnished equipment (GFE) must be utilized in approved other equipment (OE) and must be funded by the owner of the equipment. All remote systems must be equipped with, and use, a VA-approved antivirus (AV) software and a personal (host-based or enclave based) firewall that is configured with a VA-approved configuration. Software must be kept current, including all critical updates and patches. Owners of approved OE are responsible for providing and maintaining the anti-viral software and the firewall on the non-VA owned OE.

g. All electronic storage media used on non-VA leased or non-VA owned IT equipment that is used to store, process, or access VA information must be handled in adherence with VA Handbook 6500.1, Electronic Media Sanitization upon: (i) completion or termination of the contract or (ii) disposal or return of the IT equipment by the contractor/subcontractor or any person acting on behalf of the contractor/subcontractor, whichever is earlier. Media (hard drives, optical disks, CDs, back-up tapes, etc.) used by the contractors/ subcontractors that contain VA information must be returned to the VA for sanitization or destruction or the contractor/subcontractor must self-certify that the media has been disposed of per 6500.1 requirements. This must be completed within 30 days of termination of the contract.

h. Bio-Medical devices and other equipment or systems containing media (hard drives, optical disks, etc.) with VA sensitive information must not be returned to the vendor at the end of lease, for trade-in, or other purposes. The options are:

(1) Vendor must accept the system without the drive;

(2) VA's initial medical device purchase includes a spare drive which must be installed in place of the original drive at time of turn-in; or

(3) VA must reimburse the company for media at a reasonable open market replacement cost at time of purchase.

(4) Due to the highly specialized and sometimes proprietary hardware and software associated with medical equipment/systems, if it is not possible for the VA to retain the hard drive, then;

(a) The equipment vendor must have an existing BAA if the device being traded in has sensitive information stored on it and hard drive(s) from the system are being returned physically intact; and

(b) Any fixed hard drive on the device must be non-destructively sanitized to the greatest extent possible without negatively impacting system operation. Selective clearing down to patient data folder level is recommended using VA approved and validated overwriting technologies/methods/tools. Applicable media sanitization specifications need to be pre-approved and described in the purchase order or contract.

(c) A statement needs to be signed by the Director (System Owner) that states that the drive could not be removed and that (a) and (b) controls above are in place and completed. The ISO needs to maintain the documentation.

6. SECURITY INCIDENT INVESTIGATION

a. The term "security incident" means an event that has, or could have, resulted in unauthorized access to, loss or damage to VA assets, or sensitive information, or an action that breaches VA security procedures. The contractor/ subcontractor shall immediately notify the COR and simultaneously, the designated ISO and Privacy Officer for the contract of any known or suspected security/privacy incidents, or any unauthorized disclosure of sensitive information, including that contained in system(s) to which…