580-22-201 Statement of Work.pdf

1 Foreword

Replace and Upgrade Building Automation System

Project No: 580-22-201 Scope of Work

1.1 Contractor shall provide all labor, materials, tools, equipment, expertise, administration, supervision, and transportation as necessary to perform all work in accordance with provided construction specifications, drawings, all documents attached to this contract, all terms and conditions of this contract, and this statement of work.

1.2 This document does not relieve the contractor of their professional responsibility to comply with all local and federal construction and environmental codes and to perform and complete a fully coordinated job.

2 General Project Description

2.1 Contractor shall replace the existing outdated, campus-wide Building Automation System (BAS) with a new modern system with upgraded capabilities. The new BAS shall promote an energy-efficient operation, improve patient and employee safety and health, promote resource conservation, and help monitor and/or control a wide variety of existing systems along with having sufficient capacity for future expansion. The additional capacity shall include initial spare control points and controllers, as well as the expandability of the new control panels. The new equipment shall be Direct Digital Control (DDC) based and BACnet compatible.

2.2 The new system will monitor and/or control various campus systems and functions, including a central chilled water plant, a central steam plant, HVAC systems, water quality monitoring points, lighting controls, some fire alarm system data points, and energy monitoring points. These new monitoring/control points and capabilities shall include temperature, humidity, energy, flows, lighting, status, and fuel tank data.

2.3 Everything that is currently connected to the existing BAS will be on the new system and the new items anything on pneumatics will now be converted, monitoring humidity, along with water and steam flow for energy monitoring.

2.4 There are approximately 57 existing system level controllers that shall be replaced which serve approximately 2,800 field controls and 103,000 individual points. There are approximately 100 pneumatic devices to integrate, around 400 new humidity monitors to add, about 100 flow meters between steam, water, and air, along with 100 energy meters for natural gas and electricity for monitoring.

Solar panel monitoring is to be included for data logging along with lighting controls. There will be additional capacity included for known future expansion of the campus in the next five (5) to ten years.

2.5 The current MEDVAMC Building Automation System will not be on or connected to the VA Network. Therefore, no Enterprise Risk Analysis is not required as of March 10, 2025.

2.6 Work includes specialized construction labor and supervision for architectural, mechanical, electrical, and demolition work as required by provided construction documents. This Scope of Work is not considered to be a comprehensive description of work details for this project. All work shall be completed per the plans/drawings, specifications, and VA 6500.6 directives.

2.7 The construction period shall be identified and scheduled for approximately seven hundred and thirty (730) calendar days after NTP.

3 General Construction Requirements

3.1 Prior to any mobilization and construction, the contractor shall request and have an approved Infection Control Construction Permit, Construction Safety Plan, and an Interim Life Safety Measures Certification from the VAMC. Project construction schedule, schedule of values and construction phases shall be provided and approved by VA’s COR/Project Engineer and/or Contracting Officer.

3.2 Contractor shall completely prepare site, prior to the installation of the equipment, and furnish labor, equipment, and materials to perform work for this specific project as required by construction documents.

3.3 The entire project’s associated construction and temporary works shall conform to the latest VA specifications, VA Standards, energy conservation methods, EPA, OSHA, NFPA, NEC, ASHRAE, LIFE SAFETY CODE, UBC, local, Federal and industry requirements and regulations.

3.4 Project Record Drawings: The Contractor shall maintain a set of Record

Drawings. The Contractor shall maintain a set of construction documents (field as-built drawings) to record actual construction changes during the construction process. The project record drawings will be always available for review by the VA Project Manager.

3.5 The following milestone dates shall be incorporated into the contractor’s schedule.

3.5.1 Submittal Schedule and log shall be provided within ten (10) calendar days after Notice to Proceed. The contractor shall provide it to the Contracting Officer’s Representative (COR) for approval and shall include the dates for submission of Shop Drawings, Product Data, and Samples.

3.5.2 All Shop Drawings, Product Data and Samples shall be submitted and approved by the VA within sixty (60) calendar days after Notice to Proceed. The VA will provide the Contractor with written comments within 15 business days after receiving each submittal.

3.5.3 The Contractor shall submit a construction schedule within ten (10) calendar days after Notice to Proceed. The construction schedule shall be prepared in terms of calendar days (not working days). Once the construction schedule is submitted by the Contractor and approved by the CO, no lateness in the schedule shall be tolerated without the CO’s approval.

3.5.4 A pre-construction meeting shall be held within ten (10) calendar days after award of Contract. During the construction, the Contractor shall attend all weekly construction progress meetings. The meeting schedule and place will be discussed in the pre-construction meeting.

4 General Contract Requirement

4.1 VA’s Normal Working Hours are 7:00 am to 4:30 p.m., Monday through Friday.

Contractor shall coordinate work with the COR in order to not disrupt the end user’s operations which may include work earlier or later in the day and on weekends or federal holidays with at no additional cost to the VA. Noise disturbances and utility shutdowns/tie-ins shall be coordinated with the COR and not interfere with VA daily operations.

4.2 Pursuant to clause 52.236-8 Other Contracts incorporated by reference under section

4.33 52.252-2 Clauses Incorporated by Reference, Contractor shall fully cooperate with the other contractors and with Government employees and shall carefully adapt scheduling and performing the work under this contract to accommodate the additional work, heeding any direction that may be provided by the Contracting Officer. If required by the Contracting Officer, Contractor shall, at no additional cost to the VA, coordinate with other VA’s activities including but not limited to construction activities near the job site to ensure the construction work under this project will be in harmony with those activities. This coordination shall include but not limited to the careful scheduling of work commencement, equipment mobilization etc.

4.3 The following legal holidays are observed by this Government

Agency: New Year's Day January 1st Martin Luther King's Birthday Third Monday in January Presidents Day Third Monday in February Memorial Day Last Monday in May Juneteenth Independence Day June 19th Independence Day July 4th Labor Day First Monday in September Columbus Day Second Monday in October Veterans Day November 11th Thanksgiving Day 4th Thursday in November Christmas Day December 25th and any day declared by the federal government as holiday.

5 Project Meetings

5.1 Each week the contractor shall hold a progress meeting to review progress to date and to resolve all questions for the upcoming week. The progress meeting shall include at a minimum, the Project Manager and the Superintendent representing the Contractor, the COR and the CO representing the Government. Technical supervisor (foreman), sub-contractors, suppliers, etc. shall attend when requested by the Contracting Officer. The meeting shall be same day, time, and place each week.

5.2 Meeting Minutes - The contractor shall take minutes of all meetings held relative to this project. The format must be acceptable to the Contracting Officer (CO).

Minutes must include the meeting date and time; agenda; meeting location; list of participants with their affiliations, and telephone numbers; be fully descriptive of issues, problems and decisions made; and action items with names of responsible parties and deadlines. In addition, the minutes must include, as attachments, all exhibits and references distributed as handout materials, unless the materials are part of a formal submission. The contractor shall provide, via e-mail, complete copies of all minutes to all attendees within 72 hours of the meeting. All challenges to the minutes will be reflected in a revised version prepared by the contractor and CO along with the contractor and COR shall sign/initial the minutes. In the event of any disputes or challenges that can’t be resolved, the Contracting Officer shall render a final decision. Copies of updated minutes shall be distributed to all attendees within 48 hours after change notice.

6 Safety and Security

6.1 Contract workers under this project may require a VA issued identification card before the start of construction work at the Houston VAMC. There is no charge for the badges; however, multiple trips to MEDVAMC facility maybe required.

6.2 Contract employees, including all subcontractor employees, must be TB tested and receive a flu shot (each year under the contract performance) if they will work within the VA Hospital Building 100. A letter from the prime contractor shall be submitted to the CO prior to work commencing that all staff members are TB negative, and the flu shot was received.

6.3 All contract personnel are subject to inspection of personal effects when entering or leaving the project site.

6.4 Parking is rigidly controlled throughout the Medical Center. Contractor parking is only allowed in authorized areas. Contractor shall abide by all police requirements. Parking in designated patient parking areas is strictly prohibited.

Parking for unloading equipment necessary to perform the work will be authorized in advance by the COR prior to starting the project.

7. 6500.6 APPENDIX C — VA INFORMATION AND INFORMATION SYSTEM

SECURITY AND PRIVACY LANGUAGE FOR INCLUSION IN

CONTRACTS, AS APPROPRIATE

7.1. GENERAL. This entire section applies to all acquisitions requiring any Information Security and Privacy language. Contractors, contractor personnel, subcontractors and subcontractor personnel will be subject to the same federal laws, regulations, standards, VA directives and handbooks, as VA personnel regarding information and information system security and privacy.

7.2. VA INFORMATION CUSTODIAL LANGUAGE. This entire section

applies to all acquisitions requiring any Information Security and Privacy language. a.

The Government shall receive unlimited rights to data/intellectual property first produced and delivered in the performance of this contract or order (hereinafter “contract”) unless expressly stated otherwise in this contract. This includes all rights to source code and all documentation created in support thereof. The primary clause used to define Government and Contractor data rights is FAR 52.227-14 Rights in Data – General. The primary clause used to define computer software license (not data/intellectual property first produced under this contractor or order) is FAR 52.227-19, Commercial Computer Software License.

b. Information made available to the contractor by VA for the performance or administration of this contract will be used only for the purposes specified in the service agreement, SOW, PWS, PD, and/ or contract. The contractor shall not use VA information in any other manner without prior written approval from a VA Contracting Officer (CO). The primary clause used to define Government and Contractor data rights is FAR 52.22714 Rights in Data – General.

c. VA information will not be co-mingled with any other data on the contractor’s information systems or media storage systems. The contractor shall ensure compliance with Federal and VA requirements related to data protection, data encryption, physical data segregation, logical data segregation, classification requirements and media sanitization.

d. VA reserves the right to conduct scheduled or unscheduled audits, assessments, or investigations of contractor Information Technology (IT) resources to ensure information security is compliant with Federal and VA requirements. The contractor shall provide all necessary access to records (including electronic and documentary materials related to the contracts and subcontracts) and support (including access to contractor and subcontractor staff associated with the contract) to VA, VA's Office Inspector General (OIG), and/or Government Accountability Office (GAO) staff during periodic control assessments, audits, or investigations.

e. The contractor may only use VA information within the terms of the contract and applicable Federal law, regulations, and VA policies. If become applicable after execution of the contract, the parties agree to negotiate contract modification and adjustment necessary to implement the new laws, regulations, and/or policies.

f. The contractor shall not make copies of VA information except as specifically authorized and necessary to perform the terms of the contract. If copies are made for restoration purposes, after the restoration is complete, the copies shall be destroyed in accordance with VA Directive 6500, VA Cybersecurity Program and VA Information Security Knowledge Service.

g. If a Veterans Health Administration (VHA) contract is terminated for default or cause with a business associate, the related local Business Associate Agreement (BAA) shall also be terminated and actions taken in accordance with VHA Directive 1605.05, Business Associate Agreements. If there is an executed national BAA associated with the contract, VA will determine what actions are appropriate and notify the contactor.

h. The contractor shall store and transmit VA sensitive information in an encrypted form, using VA-approved encryption tools which are, at a minimum, Federal Information Processing Standards (FIPS) 140-2, Security Requirements for Cryptographic Modules (or its successor) validated and in conformance with VA Information Security Knowledge Service requirements. The contractor shall transmit VA sensitive information using VA approved Transport Layer Security (TLS) configured with FIPS based cipher suites in conformance with National Institute of Standards and Technology (NIST) 800-52, Guidelines for the Selection, Configuration and Use of Transport Layer Security (TLS) Implementations.

i. The contractor’s firewall and web services security controls, as applicable, shall meet or exceed VA’s minimum requirements.

j. Except for uses and disclosures of VA information authorized by this contract for performance of the contract, the contractor may use and disclose VA information only in two situations: (i) in response to a qualifying order of a court of competent jurisdiction after notification to VA CO (ii) with written approval from the VA CO. The contractor shall refer all requests for, demands for production of or inquiries about, VA information and information systems to the VA CO for response.

k. Notwithstanding the provision above, the contractor 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 medical records pertaining to drug addiction, sickle cell anemia, alcoholism or alcohol abuse or infection with Human Immunodeficiency Virus (HIV). If the contractor is in receipt of a court order or other requests for the above-mentioned information, the contractor shall immediately refer such court order or other requests to the VA CO for response.

l. Information made available to the contractor by VA for the performance or administration of this contract or information developed by the contractor in performance or administration of the contract will be protected and secured in accordance with VA Directive 6500 and Identity and Access Management (IAM) Security processes specified in the VA Information Security Knowledge Service.

m. Any data destruction done on behalf of VA by a contractor shall be done in accordance with National Archives and Records Administration (NARA) requirements as outlined in VA Directive 6300, Records and Information Management, VA Handbook 6300.1, Records Management Procedures, and applicable VA Records Control Schedules.

n. The contractor shall provide its plan for destruction of all VA data in its possession according to VA Directive 6500 and NIST 800-88, Guidelines for Media Sanitization prior to termination or completion of this contract. If directed by the COR/CO, the contractor shall return all Federal Records to VA for disposition.

o. Any media, such as paper, magnetic tape, magnetic disks, solid state devices or optical discs that is used to store, process, or access VA information that cannot be destroyed shall be returned to VA. The contractor shall hold the appropriate material until otherwise directed by the Contracting Officer’s Representative (COR) or CO. Items shall be returned securely via VA-approved methods. VA sensitive information must be transmitted utilizing VA-approved encryption tools which are validated under FIPS 140-2 (or its successor) and NIST 800-52. If mailed, the contractor shall send via a trackable method (USPS, UPS, FedEx, etc.) and immediately provide the COR/CO with the tracking information. Self-certification by the contractor that the data destruction requirements above have been met shall be sent to the COR/CO within 30 business days of termination of the contract.

p. All electronic storage media (hard drives, optical disks, CDs, back-up tapes, etc.) used to store, process or access VA information will not be returned to the contractor at the end of lease, loan, or trade-in.

Exceptions to this paragraph will only be granted with the written approval of the VA CO.

--- End---

7.12 PATCHING GOVERNANCE. This entire section applies whenever the acquisition includes section 7.7 is included.

a. The contractor shall provide documentation detailing the patch management, vulnerability management, mitigation and update processes (to include third-party) prior to the connection of electronic devices, assets or equipment to VA’s assets. This documentation will include information regarding the follow:

(1) The resources and technical capabilities to sustain the program or process (e.g., how the integrity of a patch is validated by VA); and

(2) The approach and capability to remediate newly reported zero-day vulnerabilities for contractor products.

b. The contractor shall verify and provide documentation all procured products (including third-party applications, hardware, software, operating systems, and firmware) have appropriate updates and patches installed prior to delivery to VA.

c. The contractor shall provide or arrange the provision of appropriate software and firmware updates to remediate newly discovered vulnerabilities or weaknesses for their products and services within 30 days of discovery. Updates to remediate critical or emergent vulnerabilities will be provided within seven business days of discovery. If updates cannot be made available by contractor within these time periods, the contractor shall submit mitigations, methods of exploit detection and/or workarounds to the COR/CO prior to the above deadlines.

d. The contractor shall provide or arrange for the provision of appropriate hardware, software and/or firmware updates, when those products, including open-source software, are provided to the VA, to remediate newly discovered vulnerabilities or weaknesses.

Remediations of products or services provided to the VA’s system environment must be provided within 30 business days of availability from the original supplier and/or patching source. Updates to remediate critical vulnerabilities applicable to the Contractor’s use of the third-party product in its system environment will be provided within seven business days of availability from the original supplier and/or patching source. If applicable third-party updates cannot be integrated, tested and made available by Contractor within these time periods, mitigations and/or workarounds will be provided to the COR/CO before the above deadlines.

8. VA DIRECTIVE 6500.6 APPENDIX C

ISSO has assessed the following language from VA Directive 6500.6 Appendix C must be included in the contract and when applicable, the corresponding Appendix B security clause.

This contract will involve VA sensitive information which consist of proprietary VA Research Data. Please include the following7 sections from Appendix C:

a. Section 1: General (Required)

b. Section 2: VA Information Custodial Language (Required) Section 12

c. Patching Governance (Required)

Note: Any media which contains VA data cannot leave the VA. Per the COR, the contracted employee will be replacing/upgrading the physical components of the system and not have access to any VA data. The contracted employee will only have physical access to the system components for replacement and not any VA data. They system does not contain PHI or PII. Per the COR, the system will not be connected to the VA network at any time.

Project No: 580-22-201