36C26118Q0222-001.pdf

PDF 288 KB Posted

Attached to
Robot-RX & PACMED Move VA Palo Alto Health Care System
Solicitation number
36C26118Q0222
Issued by

About this file

36C26118Q0222 36C26118Q0222.pdf

View the file

Other files

File Type Posted
36C26118Q0222-000.docx DOCX document

On GovTribe

Work with this file

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file

Text version

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 50

640-18-1-092-0007

36C26118Q0222 01-04-2018

Felicia A. DeMita 925-372-2038 01-12-2018

10:00 AM PST

612MCP

Department of Veterans Affairs Network Contracting Office (NCO 21) VA Martinez Outpatient Clinic 150 Muir Road

CA 94553

811219

$20.5 Million

X

N/A

X

See block 9.

Department of Veterans Affairs FMS VA-9(101) Financial Services Center

PO Box 149971 Austin TX 78714-9971

See CONTINUATION Page

This is a request for quote for a PACMED and Robot-Rx move for VA Palo Alto Health Care System.

See Scope of Work for requirements in Section B.

Please direct questions to felicia.demita@va.gov

See CONTINUATION Page

X X

Felicia A. DeMita Contracting Officer

VA261-17-Q-1197

Table of Contents

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

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

Bookmark not defined.

SECTION B - CONTINUATION OF SF 1449 BLOCKS

B.1 CONTRACT ADMINISTRATION DATA

B.2 PRICE/COST SCHEDULE

ITEM INFORMATION

B.3 DELIVERY SCHEDULE

SECTION C - CONTRACT CLAUSES

C.1 VAAR 852.203-70 COMMERCIAL ADVERTISING (JAN 2008)

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

2012)

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

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

STATUTES OR EXECUTIVE ORDERS—COMMERCIAL ITEMS (NOV 2017)

SECTION D - CONTRACT DOCUMENTS, EXHIBITS, OR ATTACHMENTS

SECTION E - SOLICITATION PROVISIONS

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

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

ITEMS (NOV 2017)

36C26118Q0222

SECTION B - CONTINUATION OF SF 1449 BLOCKS

B.1 CONTRACT ADMINISTRATION DATA

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

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

a. CONTRACTOR:

b. GOVERNMENT: Contracting Officer 36C261 Felicia A. DeMita, felicia.demita@va.gov

Network Contracting Office (NCO 21)

VA Martinez Outpatient Clinic

150 Muir Road

CA 94553

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

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

B.2 PRICE/COST SCHEDULE

ITEM INFORMATION

ITEM

NUMBE

R

DESCRIPTION OF

SUPPLIES/SERVIC

ES

QUANTIT

Y

UNI

T UNIT PRICE AMOUNT

0001 PACMED move in accordance with the Statement of Work

1.00 JB ________________

0002 Robot-Rx move in accordance with the

1.00 JB ________________

GRAND TOTAL ________________

B.3 DELIVERY SCHEDULE

ITEM NUMBER QUANTITY

DELIVERY

DATE

0001 1.00 March 30, 2018

0002 1.00 March 30, 2018

ROBOT RX and PACMED Move and Re-installation Service

December 1, 2017

1. Background:

The VA Menlo Park Pharmacy project is a 3,000 SF new addition to existing Building 360 at VA Palo Alto Healthcare System Menlo Park Division. The construction is scheduled to be completed in February 2018. The existing pharmacy will relocate from Building 334 to this new space in Building 360, and the installation of medical equipment is scheduled to start on March 2018. The Department of Veterans Affairs Palo Alto Health Care System (VAPAHCS) is seeking the Omnicell (formerly Aesynt) or Omnicell certified contractor to de-install, move, re-install and calibrate the existing ROBOT-RX and PACMED from VA Menlo Park Building 334 to the new pharmacy in the new space in Building 360.

2. Scope of Work:

A. The Contractor will de-install, move, re-install, seismically anchors the units (to floor) and recalibrate existing Aesynt ROBOT-RX, PACMED and peripheral devices back to its original functional state in the new space at Building 360.

B. ROBOT-RX and PACMED will directly interface with Connect-RX Automation Software Platform.

C. The Contractor will fully test the ROBOT-RX, PACMED and all support equipment to insure compatibility and full integration with Connect-RX at time of install.

D. The Contractor shall comply with the current Internal Security Act and Memorandum of Understanding (ISA/MOU), and all VA information security requirements during de-install, move, re-installation, training and subsequent warranty period.

E. The Contractor will ensure the work performed is done in a way to protect the VA’s property to the maximum extent practicable. Contractor will ensure that any damage to the facility incurred through the de-install, move and re-installation of the ROBOT-RX and PACMED units will be repaired to bring the facility back to the conditions prior to the work performed.

F. The Contractor shall provide the following services for PACMED de-install, move and re-install including, but not limited to:

• Provide Project Planning and Management support

• Provide CAD file layout identifying final location.

• Provide project schedule outlining implementation service tasks, activities and timeframes.

• Tailor project schedule to fit customer and site conditions.

• Coordinate de-installation, move and re-installation date and time with customer prior to arriving on site.

• Identify and secure contractor’s resource commitments.

• Mobilize a team and conduct on-site kickoff meeting and attend follow up coordination meetings.

• Validate site, organizational and technical readiness for de-installation, move and re-installation of the equipment.

• Ensure timely reporting and communication of project activities, issues, risks, milestones and customer’s request for information.

• Provide installation assistance.

• Perform onsite inspection to validate site readiness.

• Perform disassembly of existing PACMED after customer removes all medication canisters.

• Move the equipment to the new location.

• Reassemble PACDMED back to the original functional state in the new location and connect it to building utility points of connection and any peripheral devices.

• After installation, Contractor shall fully test the PACMED to validate product functionality and to ensure compatibility and full integration with Connect-RX.

• The Contractor shall provide 1 day onsite support in the use and maintenance of the product.

G. The Contractor shall provide the following services for ROBOT-RX de-install, move and re-install including, but not limited to:

• Provide CAD file layout identifying final location.

• Provide schedule outlining implementation service tasks, activities and timeframes.

• Tailor move/installation schedule to fit customer and site conditions.

• Coordinate de-installation, move and installation date and time with customer prior arriving to the site.

• Identify and secure contractor’s resource commitments.

• Mobilize a team and conduct on-site kickoff meeting and attend follow up coordination meetings.

• Validate site, organizational and technical readiness for de-installation, move and re-installation of the equipment.

• Ensure timely reporting and communication of project activities, issues, risks, milestones and customer’s request for information.

• Provide installation assistance.

• Perform site inspection onsite to validate site readiness.

• Provide recommendations for all peripheral materials (PCs, Air compressor, UPS, Power and Furniture).

• Perform disassembly of existing ROBOT-Rx after VA Pharmacy team removes all medication from ROBOT-Rx cells.

• Move the equipment to the new location.

• Reassemble ROBOT-Rx in new location, including calibration, seismic anchoring, connecting to building utility point of connection and peripheral devices.

• Provide technical assistance such as reviewing engineering drawings to ensure the utility and structural design meets the equipment utility and structural support requirement.

• Support customer onsite for 2 days in the use and maintenance of the product.

• After the installation is complete, Contractor shall fully test the ROBOT RX to validate product functionality and to ensure compatibility and full integration with Connect-RX Automation Software platform.

The Government and the Contractor understand and agree that the services to be delivered under this contract by the Contractor to the Government are non-personal services and the parties recognize and agree that no employer-employee or master-servant relationships exist or will exist under the contract between the Government and the Contractor’s employees.

NOTES:

• The Contractor shall provide seismic restrain to maintain the integrity of Robot RX, and Pacmed equipment so that they remain safe and functional in case of seismic event.

• The Contractor shall provide structural seismic restrain design to resist seismic load based on the seismic design categories per section 4.0 of the lasted Seismic Design requirements (H-18-8) which can be found on https://www.cfm.va.gov/til//seismic.asp

• The Contractor shall submit a coordinated set of equipment anchorage drawings prior to installation including:

(i) Description, layout, and location of items to be anchored or braced with anchorage or brace points noted and dimensioned.

(ii) Details of anchorage or bracing at large scale with all members, parts brackets shown together with all connections, bolts, welds, etc., clearly identified and specified.

(iii) Numerical value of design seismic brace loads.

(iv) For expansion bolts, include design load and capacity if different from those specified.

• The Contractor shall submit design calculations prepared and sealed by a registered structural engineer.

• The Contractor is responsible for all costs of their travel and living expenses for this scope of work.

• The Contractor shall provide and use their own tools, equipment, fork lifts, delivery truck with lift gate and any other devices to perform their services.

https://www.cfm.va.gov/til/seismic.asp

• The Contractor shall coordinate with VA representative on the delivery path from the existing location to the new install location.

• The Contractor is responsible to check and designate the delivery path of equipment prior to move.

3. Location of equipment de-install and re-install:

VA Menlo Park

795 Willow Road

Bldg. 334 move to Bldg. 360 J-Wing

Menlo Park, CA 94025

4. Contracting Officer’s Representative (COR):

a. Technical representative POC: Baubak Bagherpour (650) 493-5000 x. 68745 or Douglas Klahold (650) 849-0119.

b. No Government personnel, other than the Contracting Officer (CO), have the authority to change or alter these requirements. The COR shall clarify technical points or supply relevant technical information, but no requirements in this scope of work may be altered as a sole result of such verbal clarification.

5. Reports/Deliverables:

After installations and testing, the ROBOT-RX and PACMED must function properly and integrate with Connect-RX Automation Software Platform.

6. Contractor Qualifications:

a. The Contractor needs to be the authorized or certified vendor by the manufacturer (Omnicell Inc.) to de-install, move and install ROBOT-RX and PACMED.

b. The Contractor who will be working in the project site needs to have valid OSHA 10 certification.

7. Period of Service:

All work under the order to be performed and completed in 12 months from the date of award.

8. Facility Hours:

The Pharmacy hours are 8:00 am to 4:30 pm. Work may be done during business or non-business hours. If weekend work is desired, the Contractor must request approval with the COR prior to doing so.

9. Electricity:

The VA does not anticipate that electricity shut-down would be required for this project.

However, it is ultimately up to the Contractor to determine if shutting off the electricity is required to safely de-install the units and re-install in the new building. If shut-off is required, the Contractor shall notify the COR at least three (3) weeks prior to the date for shut-off and shall coordinate with the COR to facilitate the shut-off.

10. Requirements While Working at VISN 21 Facilities:

The Contractor employees and/or Subcontractors approved by the COR shall wear visible identification at all times while on the premises of the facilities within the NCO. Identification shall include but not limited to a company identification card, which shall include the company name, employee name, title, and a photograph of the employee. Contractor Employees shall maintain a professional appearance commensurate to their industry.

It is the responsibility of the Contractor to park in the appropriate designated parking areas.

Information on parking is available from the VA Police Section. This will not invalidate or make reimbursement for parking violations of the Contractor under any conditions.

Any interior or exterior doors that shall be unlocked to gain access shall be kept locked during the performance of work unless it results in the creation of a safety hazard. In those instances, the Contractor is responsible to take necessary actions to maintain the same level of security prior to gaining access/performing work. Should any other devices need to be unlocked like an entry gate, those devices shall be locked immediately upon entry or exit. At no time, shall the Contractor allow any person into a locked area or loan keys/access cards to another person.

Contractor may be held in default for failure to comply with this requirement and subject the Contractor and its employees to contractual and other legal remedies.

Contractor personnel are required to check into the facility Police & Security Office at each visit to pick up a “Contractor” badge prior to contacting the COR. The Contractor’s staff shall also be required to sign in and out each day at a designated location determined by the COR.

Smoking is prohibited inside any buildings at the facilities within VISN 21.

Possession of weapons are prohibited. Enclosed containers, including tool kits, shall be subject to search. Violations of VA regulations may result in citation answerable in the United States (Federal) District Court, not a local district, state, or municipal court.

The Contractor shall not allow his/her employees, including Subcontractors’ employees, to open desk drawers, cabinets, or to use office equipment, including the use of non-pay telephones for any purpose other than a local emergency call. The Contractor shall be responsible to provide all necessary equipment, tools, parts, and materials to perform the work. The Government shall not be obligated to provide any equipment, tools, parts, and materials to assist the Contractor in performing the work.

11. Training:

The Contractor will provide on-site training to the VA staff after the installation of the ROBOT- RX and PACMED units. If additional training is required through the performance of the contract, the COR will request a contract modification through VA’s Contracting Officer. Any such additional training will be based on the Federal Supply Schedule rates with any applicable discounts.

12. Authority to Bind the Government:

The only person authorized to bind the Government is the Contracting Officer. Any changes to the contract must be made in writing and signed by the Contracting Officer. The Contracting Officer Representative (COR) is not authorized to make changes to anything outlined in the contract. If the Contractor takes direction from unauthorized Government representatives, it does so at its own risk. Any requests for adjustments from the Contractor after taking directions from unauthorized representatives will be disapproved.

13. Security:

Below are the security requirements for the contract.

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 SECURITY

a. The 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 extend necessary to perform the services specified in the contract, agreement or task order.

b. All contractors, subcontractors, and third-party services and associated 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 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 extend 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 accepted by VA, specifically to address mitigation of the resulting problems of communications, 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’ 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 purposed 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 contractor/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 onsite 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, backup, maintain, use, disclose and depose 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 becomes applicable to the VA information or information systems after execution of the contract, or if NIST issues or updated 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 disclosure 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 yearly basis and provide it to the COTR.

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, HIPPA, 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 designation 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 COTR, and approved by the VA Privacy Service in accordance with Directive 6507, VA Privacy Impact Assessment.

b. The contractor/subcontractor shall certify to the COTR 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 guideline provided by NIST or the VA. This includes Internet Explorer 7 configured to operate on Window 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 for installation to the default “program files” directly 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 03-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;

(2) Include the Privacy Act notification contained in this contract in every solicitation and resulting subcontract and in every subcontract 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

(3) 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 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 the 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) “Records” means any item, collection, or grouping of information about and 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 insure 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 included, 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 __7__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 no affecting the Systems within 10 working days. When the vendor is responsible for operations of maintenance of the Systems, they shall apply the Security Fixes within __10__ 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 and non- VA facilities, contractor/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 vulnerability scanning, system patching and change management procedure, 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 system. A Privacy Impact Assessment (PIA) must also be provided to the COTR 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 Actions 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 copies and electronic copies of the assessment must be provided to the COTR. The government reserves the right to conduct such an assessment using government personnel of another contractor/subcontractor. The contractor/subcontractor must take appropriate and timely action (this can be specified in the contract) to correct or mitigate any weakness 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 contractor/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 return to the vendor at the end of lease, for trade-in, or other purposed. The options are:

(1) Vendor must accept the system within 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 extend possible without negatively impacting system operation. Selective clearing down to patient data folder level is recommended using VA approve and validated overwriting technologies/methods/tools. Applicable media sanitization specifications need to be pre-approved and described in the purchase order of 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 COTR and simultaneously, the designated ISO and Privacy Officer for the contact of any known or suspended security/privacy incidents, or any unauthorized disclosure of sensitive information, including that contained in system(s) to which the contractor/subcontractor has access.

b. To the extend known by the contractor/subcontractor, the contractor/subcontractor’s notice to VA shall identify the information involved, the circumstances surrounding the incident (including to whom, how, when, and where the VA information or assets were placed at risk or compromised), and any other information that the contractor/subcontractor considers relevant.

c. With respect to unsecured protected health information, the business associate is deemed to have discovered a data breach when the business associate knew or should have known of a breach of such information. Upon discovery, the business associate must notify the covered entity of the breach. Notifications need to be made in accordance with the executed business associate agreement.

d. In instances of theft or break-in or other criminal activity, the contractor/subcontractor must concurrently report the incident to the appropriate law enforcement entity (or entities) of jurisdiction, including the VA OIG and Security and Law Enforcement. The contractor, its employees, and its subcontractors and their employees shall cooperate with VA and any law enforcement authority responsible for the investigation and prosecution of any possible criminal law violation(s) associated with any incident. The contractor/subcontractor shall cooperate with VA in any civil litigation to recover VA information, obtain monetary or other compensation from a third party for damages arising from any incident, or obtain relief against any third party arising from, or related to, the incident.

7. LIQUIDATED DAMAGES FOR DATA BREACH

a. Consistent with the requirements of 38 U.S.C. §5725, a contract may require access to sensitive personal information. If so, the contractor is liable to VA for liquidated damages in the event of a data breach or privacy incident involving any SPI the contractor/subcontractor processes or maintains under this contract.

b. The contractor/subcontractor shall provide notice to VA of a “security incident” as set forth in the Security Incident Investigation section above. Upon such notification, VA must secure from non- Department entity or the VA Office of Inspector General an independent risk analysis of the data breach to determine the level of risk associated with the data breach for the potential misuse of any sensitive personal information involved in the data breach. The term ‘data breach’ means the loss, theft, or other unauthorized access, or any access other than that incidental to the scope of employment, to data containing sensitive personal information, in electronic or printed form, that results in the potential compromise of the confidentiality of integrity of the data. Contractor shall fully cooperate with the entity performing the risk analysis. Failure to cooperate may be deemed a material breach and grounds for contract termination.

c. Each risk analysis shall address all relevant information concerning the data breach, including the following:

(1) Nature of the event (loss, theft, unauthorized access);

(2) Description of the event, including:

(a) Date of occurrence;

(b) Data elements involved, including any PII, such as full name, social security number, date of birth, home address, account number, disability code;

(3) Number of individuals affected or potentially affected;

(4) Names of individuals or groups affected or potentially affected;

(5) Ease of logical data access to the host, stolen or improperly accessed data in light of the degree of protection for the data, e.g., unencrypted, plain text;

(6) Amount of time the data has been out of VA control;

(7) The likelihood that the sensitive personal information will or has been compromised (made accessible to and usable by unauthorized persons);

(8) Known misuses of data containing sensitive personal information, if any;

(9) Assessment of the potential harm to the affected individuals;

(10) Data breach analysis as outlined in 6500.2 Handbook, Management of Security and Privacy Incidents, as appropriate; and

(11) Whether credit protection services may assist record subjects in avoiding or mitigating the results of identity theft based on the sensitive personal information that may have been compromised.

d. Based on the determinations of the independent risk analysis, the contractor shall be responsible for paying to the VA liquidated damages in the amount of $__37.50____ per affected individual to cover the cost of providing credit protection services to affected individuals consisting of the following:

(1) Notification;

(2) One year of credit monitoring services consisting of automatic daily monitoring of at least 3 relevant credit bureau reports;

(3) Data breach analysis;

(4) Fraud resolution services, including writing dispute letters, initiating fraud alerts and credit freezes, to assist affected individuals to bring matters to resolution;

(5) One year of identity theft insurance with $20,000.00 coverage at $0 deductible, and

(6) Necessary legal expenses the subjects may incur to repair falsified or damaged credit records, histories, or financial affairs.

8. SECURITY CONTROLS COMPLIANCE TESTING

On a periodic basis, VA including the Office of Inspector General, reserves the right to evaluate any or all the security controls and privacy practices implemented by the contractor under the clauses contained within the contract. With 10 working-days’ notice, at the request of the government, the contractor must fully cooperate and assist in a government-sponsored security controls assessment at each location wherein VA information is processed or stored, or information systems are developed, operated, maintained, or used on behalf of VA, including those initiated by the Office of Inspector General. The government may conduct a security control assessment on shorter notice (to include unannounced assessments) as determined by VA in the event of a security incident or at any other time.

9. TRAINING

a. All contractor employees and subcontractor employees requiring access to VA information and VA information systems shall complete the following before being granted access to VA information and its systems:

(1) Sign and acknowledge (either manually or electronically) understanding of and responsibilities for compliance with the Contractor Rules of Behavior, Appendix E relating to access to VA information and information systems;

(2) Successfully complete the VA Cyber Security Awareness and Rules of Behavior training and annually complete required security training;

(3) Successfully complete the appropriate VA privacy training and annually complete required privacy training; and

(4) Successfully complete and additional cyber security or privacy training, as required for VA personnel with equivalent information system access [to be defined by the VA program official and provided to the contracting officer for inclusion in the solicitation document – e.g., any role-based information security training required in accordance with NIST Special Publication 800- 16, Information Technology Security Training requirements.]

b. The Contractor shall provide to the contracting officer and/or COTR a copy of the training certificates and certification of signing the Contractor Rules of Behavior for each applicable employee within 1 week of the initiation of the contract and annually thereafter, as required.

c. Failure to complete the mandatory annual training and sign the Rules of Behavior annually, within the timeframe required, is ground for suspension or termination of all physical or electronic access privileges and removal from work on the contract until such time as the training and documents are complete.

SECTION C - CONTRACT CLAUSES

ADDENDUM to FAR 52.212-4 CONTRACT TERMS AND CONDITIONS—COMMERCIAL ITEMS

Clauses that are incorporated by reference (by Citation Number, Title, and Date), have the same force and effect as if they were given in full text. Upon request, the Contracting Officer will make their full text available.

The following clauses are incorporated into 52.212-4 as an addendum to this contract:

C.1 VAAR 852.203-70 COMMERCIAL ADVERTISING (JAN 2008)

The bidder or offeror agrees that if a contract is awarded to him/her, as a result of this solicitation, he/she will not advertise the award of the contract in his/her commercial advertising in such a manner as to state or imply that the Department of Veterans Affairs endorses a product, project or commercial line of…

This is the start of the file's text. The full file is on GovTribe.

File details come from the government source that posted it.