36C26118B0376-001.docx

36C26118B0376 Section L

1. SOLICITATION NUMBER

2. TYPE OF SOLICITATION

3. DATE ISSUED

PAGE OF PAGES

4. CONTRACT NUMBER

5. REQUISITION/PURCHASE REQUEST NUMBER

6. PROJECT NUMBER

7. ISSUED BY

CODE

8. ADDRESS OFFER TO

a. NAME

b. TELEPHONE NUMBER (Include area code) (NO COLLECT CALLS)

10. THE GOVERNMENT REQUIRES PERFORMANCE OF THE WORK DESCRIBED IN THESE DOCUMENTS (Title, identifying number, date) 12a. THE CONTRACTOR MUST FURNISH ANY REQUIRED PERFORMANCE AND PAYMENT BONDS?

(If "YES," indicate within how many calendar days after award in Item 12B.)

12b. CALENDAR DAYS

13. ADDITIONAL SOLICITATION REQUIREMENTS:

STANDARD FORM 1442 (REV. 8/2014)

STANDARD FORM 1442

Prescribed by GSA-FAR (48 CFR) 52.236-1(d)

SOLICITATION, OFFER,

AND AWARD

(Construction, Alteration, or Repair)

SOLICITATION

SOLICITATION

IMPORTANT - The "offer" section on the reverse must be fully completed by offeror.

9. FOR INFORMATION

CALL:

NOTE: In sealed bid solicitations "offer" and "offeror" mean "bid" and "bidder".

SEALED BID (IFB)

NEGOTIATED (RFP)

11. The Contractor shall begin performance within ____________ calendar days and complete it within calendar days after receiving award, notice to proceed. This performance period is mandatory negotiable. (See _____________________________).

YES

NO

a.

Sealed offers in original and ___________________copies to perform the work required are due at the place specified in Item 8 by _____________ (hour) local time _____________________ (date). If this is a sealed bid solicitation, offers must be publicly opened at that time. Sealed envelopes containing offers shall be marked to show the offeror's name and address, the solicitation number, the date and time offers are due.

b.

An offer guarantee is, is not required.

c.

All offers are subject to the (1) work requirements, and (2) other provisions and clauses incorporated in the solicitation in full text or by reference.

d.

Offers providing less than _______________________ calendar days for Government acceptance after the date offers are due will not be considered and will be rejected.

36C26118B0376 X 04-23-2018 612-18-2-6054-0013 612-18-429 Department of Veterans Affairs VA Sierra Pacific Network (VISN 21) VA Northern California HealthCare System 150 Muir Road Martinez

CA

94553-4668 Pastaveia St. John 10535 Hospital Way Bldg 650, Rm 3D-112 Mather

CA

95655 Pastaveia St. John 916.843.2822 Project 612-18-429, Install Replacement Voice and Data in Building 722

NAICS CODE: 238210 --Electrical Contractors and Other Wiring Installation Contractors Small Business Size Standard: $15M IAW VAAR 836.204, magnitude of construction is between $25,000 and $100,000.

Project description: Contractor shall provide all tools, labor, materials, equipment, project management, supervision, and transportation to complete the contract both within schedule and within budget as awarded. This project calls for installation of replacement voice and data in Building 722.

Place of Performance is 10535 Hospital Way Bldg 722 Mather, CA 95655 (Sacramento County)

The single organized site visit for this IFB has been scheduled as follows:

Date: 9 May 2018 Time: 10:00 AM Location: 10535 Hospital Way Bldg 722 Mather, CA 95655

In accordance with established public law, all bidders are required to be registered and current in System for Award Management (SAM), the official website of the U.S. Government at www.sam.gov.

This is a total Service-Disabled-Veteran-Owned-Small-Business (SDVOSB) set-aside under public law 109-461.

This contract will be awarded in accordance with FAR Part 14 -- Sealed Bidding.

x 52.211-10 X

09:00 AM PST

05-23-2018 x

14. NAME AND ADDRESS OF OFFEROR

15. TELEPHONE NUMBER

16. REMITTANCE ADDRESS

CODE

FACILITY CODE

17. The offeror agrees to perform the work required at the prices specified below in strict accordance with the terms of the solicitation, if this offer is accepted by the Government in writing within __________ calendar days after the date offers are due.

AMOUNTS

18. The offeror agrees to furnish any required performance and payment bonds.

19. ACKNOWLEDGMENT OF AMENDMENTS

AMENDMENT

NUMBER

DATE.

20a. NAME AND TITLE OF PERSON AUTHORIZED TO SIGN OFFER 20b. SIGNATURE 20c. OFFER DATE

21. ITEMS ACCEPTED:

22. AMOUNT

23. ACCOUNTING AND APPROPRIATION DATA

24. SUBMIT INVOICES TO ADDRESS SHOWN IN

ITEM

25. OTHER THAN FULL AND OPEN COMPETITION PURSUANT TO

10 U.S.C. 2304(c)( 41 U.S.C. 3304(a) (

26. ADMINISTERED BY

27. PAYMENT WILL BE MADE BY

PHONE:

FAX:

28. NEGOTIATED AGREEMENT

29. AWARD

Your Contractor agrees offer on this solicitation is hereby accepted as to the items listed. This to furnish and deliver all items or perform all work requirements identified award consummates the contract, which consists of (a) the Government on this form and any continuation sheets for the consideration stated in solicitation and your offer, and (b) this contract award. No further cont-this contract. The rights and obligations of the parties to this contract ractual document is necessary.

shall be governed by (a) this contract award, (b) the solicitation, and (c) the clauses, representations, certifications, and specifications incorporated by reference in or attached to this contract.

30a. NAME AND TITLE OF CONTRACTOR OR PERSON AUTHORIZED 31a. NAME OF CONTRACTING OFFICER

TO SIGN

30b. SIGNATURE 30c. DATE 31b. UNITED STATES OF AMERICA 31c. AWARD DATE

BY

OFFER

AWARD

STANDARD FORM 1442 (REV. 8/2014) BACK

(Include ZIP Code) (Include area code) (Include only if different than Item 14.)

(Insert any number equal to or greater than the minimum requirement stated in Item 13d. Failure to insert any number means the offeror accepts the minimum in Item 13d.)

(The offeror acknowledges receipt of amendments to the solicitation -- give number and date of each) (Type or print) (4 copies unless otherwise specified) (Type or print) (Type or print) (Contractor is required to sign this document and return _______ copies to issuing office.)

(Contractor is not required to sign this document.)

(Must be fully completed by offeror) (To be completed by Government)

CONTRACTING OFFICER WILL COMPLETE ITEM 28 OR 29 AS APPLICABLE

612-3680162-6054-854200-3220-23NRNR001

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

CA

94553-4668 Department of Veterans Affairs FMS-VA-2(101) Financial Services Center PO Box 149971 Austin

TX

78714-9971

Table of Contents

SECTION C - DESCRIPTION/SPECIFICATIONS/STATEMENT OF WORK

Install Replacement Voice and Data for B. 722 Project # 612-18-429 General Intention:

1. All work associated with this scope of work shall occur at the Bldg. 722 at the Mather VA Medical Center.

2. The contractor shall complete all work with 30 calendar days of notice to proceed.

3. A pre-bid walk is encouraged to ensure site conditions are represented correctly in the contractor’s proposal.

Scope of Work:

The purpose of this Scope of Work is to have a vendor Outfit TR (telecom Room) closet and pull Data Cat 6 cable in Building 722, Mather. The job will provide Voice/Data connectivity from the station location indicated to the local TR closet.

1. The vendor will install Berk-Tek Cat 6 LanMARK 1000 plenum rated cable (or equivalent) to 56 locations in Building 722, Mather. Cable to be installed tested and terminated on both ends.

1. The locations will be pulled 3 cables (unless stated otherwise). (3 Data).

1. The cables will be installed from the location to the TR closet located in the building.

1. The cables will be identified by using blue colored cable for Data.

1. The vendor will re-use rack currently in TR (Telecom Room) and provide horizontal wire-minder. Horizontal will be 2U around the switches minimum, 1U between patch panels.

1. The Data will be terminated in the IDF on Cat 6 rated Ortronics (or equivalent) patch panels. Labeling on patch panel will begin with 1A, 1B, 1C, 2A, 2B, 2C…etc.

1. The Copper cable pairs (24 of 25) are to be terminated on Cat 6 rated Ortronics (or equivalent) patch panel and labeled accordingly

1. The Data terminations at the station area will be terminated T568A configuration using Avaya / Systimax Cat 6 (or equivalent) connectors: Tan in color.

1. The locations will have tan Avaya / Systimax (or equivalent) faceplates and be labeled accordingly. Labels to match current hospital standards. (See IT for all labeling)

1. Vendor to supply Cat 6 patch cords for 50% (or 100 count; whichever is less) of available connections. Patch cords to be Yellow in color, 25% 3 ft., 25% 5 ft., 25% 7ft and 25% 10ft.

1. All Data cable should be laid in already installed cable tray. Any place where there is no cable tray; hangers will need to be installed by vendor.

1. All cable to be neatly ran and bundled together per hospital standards. *Station Locations subject to change*

1. All existing cable that has been cut out of use will be removed and disposed of by vendor.

Summary of Work to Be Completed:

1. Punch down T568A configuration on all cabling. Test all cable to hospital standards.

1. All wire to be neat and orderly matching, or, better than hospital standards.

1. If removal of ceiling tile will be required to install cabling, vendor will be responsible for replacement of all ceiling tiles removed by the Vendor, in the same condition as before tile was removed. Vendor will be responsible, replacing any broken or damaged ceiling tiles and ceiling grid.

1. Various locations of cabling may require the vendor to cut holes in walls. Vendor will supply all B-line faceplate adapters required to fulfill the job requirements. Locations that will require cut-in will be shown to vendor prior to installation of cabling.

Milestones:

1. Install Berk-Tek Cat 6 LanMARK 1000 plenum cable (or equivalent) for Data to the station location in Building 722.

1. Vendor will install 3 cables for Data to each location. Use blue Berk-Tek(or equivalent) plenum cable for Data.

1. In the IDF, Data and Copper Pairs will be terminated on the Cat 6 Patch panel including standoffs, wire minders.

1. At the station end, each cable will be terminated on Cat 6 Avaya/Systimax (or equivalent) RJ45 jacks; T568A configuration. The Data jacks will be tan.

1. The station location will have tan Avaya/Systimax (or equivalent) face plates.

1. All locations and patch panels are to be labeled accordingly.

1. All cables will be laid on cable tray where available.

1. When a cable run cannot be placed on a cable tray, the vendor will need to install a hanger and place the cable in the hanger. Cables are not to be resting on lights or equipment in the ceiling.

1. All cable installation will need to be installed neatly and orderly to meet VA hospital standards.

1. All cable fiber/copper will be installed, terminated and tested to current standards. Vendor must provide all material to install, terminate and test all cable.

Delivery.

1. The vendor must supply all hardware/personnel needed to complete the Job.

1. The job must be completed NLT 30 days after contract award.

1. All cable test results will be submitted to VA POC (Stanley Schrock/Johnny Neely)

1. IT requires a complete walk through of the job before contractor begins work due to the complexity of the work to be completed

1. Contractor to verify all cable counts are correct before beginning any work.

Records Management Language for Contracts Required The following standard items relate to records generated in executing the contract and should be included in a typical Electronic Information Systems (EIS) procurement contract:

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.

End of SOW 36C26118B0376 Section C

Page 1 of Page 1 of

SECTION E - INSPECTION AND ACCEPTANCE

36C26118B0376 Section E

Page 1 of Page 1 of

SECTION F - DELIVERIES OR PERFORMANCE

F.1 52.211-10 COMMENCEMENT, PROSECUTION, AND COMPLETION OF WORK (APR 1984)

The Contractor shall be required to (a) commence work under this contract within 10 calendar days after the date the Contractor receives the notice to proceed, (b) prosecute the work diligently, and (c) complete the entire work ready for use not later than 30 days after receipt of award. The time stated for completion shall include final cleanup of the premises.

(End of Clause)

F.2 52.236-13 ACCIDENT PREVENTION (NOV 1991)

(a) The Contractor shall provide and maintain work environments and procedures which will—

(1) Safeguard the public and Government personnel, property, materials, supplies, and equipment exposed to Contractor operations and activities;

(2) Avoid interruptions of Government operations and delays in project completion dates; and

(3) Control costs in the performance of this contract.

(b) For these purposes on contracts for construction or dismantling, demolition, or removal of improvements, the Contractor shall—

(1) Provide appropriate safety barricades, signs, and signal lights;

(2) Comply with the standards issued by the Secretary of Labor at 29 CFR Part 1926 and 29 CFR Part 1910; and

(3) Ensure that any additional measures the Contracting Officer determines to be reasonably necessary for the purposes are taken.

(c) If this contract is for construction or dismantling, demolition or removal of improvements with any Department of Defense agency or component, the Contractor shall comply with all pertinent provisions of the latest version of U.S. Army Corps of Engineers Safety and Health Requirements Manual, EM 385-1-1, in effect on the date of the solicitation.

(d) Whenever the Contracting Officer becomes aware of any noncompliance with these requirements or any condition which poses a serious or imminent danger to the health or safety of the public or Government personnel, the Contracting Officer shall notify the Contractor orally, with written confirmation, and request immediate initiation of corrective action. This notice, when delivered to the Contractor or the Contractor's representative at the work site, shall be deemed sufficient notice of the noncompliance and that corrective action is required. After receiving the notice, the Contractor shall immediately take corrective action. If the Contractor fails or refuses to promptly take corrective action, the Contracting Officer may issue an order stopping all or part of the work until satisfactory corrective action has been taken. The Contractor shall not be entitled to any equitable adjustment of the contract price or extension of the performance schedule on any stop work order issued under this clause.

(e) The Contractor shall insert this clause, including this paragraph (e), with appropriate changes in the designation of the parties, in subcontracts.

(End of Clause)

F.3 VAAR 852.236-87 ACCIDENT PREVENTION (SEP 1993)

The Resident Engineer on all assigned construction projects, or other Department of Veterans Affairs employee if designated in writing by the Contracting Officer, shall serve as Safety Officer and as such has authority, on behalf of the Contracting Officer, to monitor and enforce Contractor compliance with FAR 52.236-13, Accident Prevention. However, only the Contracting Officer may issue an order to stop all or part of the work while requiring satisfactory or corrective action to be taken by the Contractor.

(End of Clause) F.4 52.225-10 NOTICE OF BUY AMERICAN REQUIREMENT—CONSTRUCTION MATERIALS (MAY 2014)

(a) Definitions. "Commercially available off-the-shelf (COTS) item," "construction material," "domestic construction material," and "foreign construction material," as used in this provision, are defined in the clause of this solicitation entitled "Buy American—Construction Materials" (Federal Acquisition Regulation (FAR) clause 52.225-9).

(b) Requests for determinations of inapplicability. An offeror requesting a determination regarding the inapplicability of the Buy American statute should submit the request to the Contracting Officer in time to allow a determination before submission of offers. The offeror shall include the information and applicable supporting data required by paragraphs (c) and (d) of the clause at FAR 52.225-9 in the request. If an offeror has not requested a determination regarding the inapplicability of the Buy American statute before submitting its offer, or has not received a response to a previous request, the offeror shall include the information and supporting data in the offer.

(c) Evaluation of offers.

(1) The Government will evaluate an offer requesting exception to the requirements of the Buy American statute, based on claimed unreasonable cost of domestic construction material, by adding to the offered price the appropriate percentage of the cost of such foreign construction material, as specified in paragraph (b)(3)(i) of the clause at FAR 52.225-9.

(2) If evaluation results in a tie between an offeror that requested the substitution of foreign construction material based on unreasonable cost and an offeror that did not request an exception, the Contracting Officer will award to the offeror that did not request an exception based on unreasonable cost.

(d) Alternate offers.

(1) When an offer includes foreign solicitation in paragraph (b)(2) of the clause at FAR 52.225-9, the offeror also may submit an alternate offer based on use of equivalent domestic construction material.

(2) If an alternate offer is submitted, the offeror shall submit a separate Standard Form 1442 for the alternate offer, and a separate price comparison table prepared in accordance with paragraphs (c) and (d) of the clause at FAR 52.225-9 for the offer that is based on the use of any foreign construction material for which the Government has not yet determined an exception applies.

(3) If the Government determines that a particular exception requested in accordance with paragraph (c) of the clause at FAR 52.225-9 does not apply, the Government will evaluate only those offers based on use of the equivalent domestic construction material, and the offeror shall be required to furnish such domestic construction material. An offer based on use of the foreign construction material for which an exception was requested—

(i) Will be rejected as nonresponsive if this acquisition is conducted by sealed bidding; or

(ii) May be accepted if revised during negotiations.

36C26118B0376 Section F (End of Provision) Page 1 of Page 1 of

SECTION H - SPECIAL CONTRACT REQUIREMENTS

H.1 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 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 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 the contractor/ subcontractor has access.

b. To the extent 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 injunctive 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 a 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.