Attachment 1 Construction SOW Rev5.docx

STATEMENT OF WORK

Project number: 663-20-102 Project Title: Renovate and Modernize Seattle Sterile Processing Service in B100 Basement – “Upgrade SPS” Seattle VA Project Location: VA Puget Sound Healthcare System, Seattle Division

1. GENERAL:

The Department of Veterans Affairs, VA Puget Sound Healthcare System (VAPSHCS) requires the services of a contractor to provide all necessary supervision, services, tools, labor, materials and equipment to completely prepare project areas for construction operations, including selective demolition and removal of existing materials, and furnishing all necessary tools, equipment, labor, materials, temporary equipment and items, specialty services, supervision, and performing all work to renovate the existing Sterile Processing Service (SPS) and ancillary spaces in the basement of Building 100, in addition to providing SPS temporary trailers and supporting sitework at the VAPSHCS Seattle Campus. The Notice to Proceed will not be issued until after receipt of bonds. All work shall be performed per contract drawings and specifications.

2. TASK:

All work indicated on the drawings and specifications. All submissions will take into consideration the existing site conditions; it is the responsibility of the Contractor to review the entire job area and existing site conditions prior to submission to properly be able to price the work. It includes the following:

a. Renovate the existing Sterile Processing Service to increase functionality and provide a modernized SPS. The project will correct noted facility deficiencies as well as improve efficiency for the SPS service line and associated ancillary spaces in the basement of Building 100, in addition the contractors will be providing the SPS team a temporary Sterilization Processing Service trailer for the duration site work at the VAPSHCS Seattle Campus at all construction phases.

3. WORK HOURS:

All renovation activities will take place at a busy Medical Center. The Contractor shall not interfere with existing, on-going functions, or normal activity of the hospital. Comment by Rhodes, Karen R. (NCO20) (she/her/hers): Verify this font is the same size as the rest of the document, it looks odd.

a. Unless instructed by the Contracting Officer Representative(COR), drawings, or specifications, construction work may occur during normal functioning business hours, 7:000 AM to 4:304:30 PM. Comment by Rhodes, Karen R. (NCO20) (she/her/hers): Spell out first time used—ensure these hours don’t conflict in any of the specifications.

b. National Holidays: The eleventen holidays observed by the Federal Government are: New Year’s Day, Martin Luther King’s Birthday, President’s Day, Juneteenth, Memorial Day, Independence Day, Labor Day, Columbus Day, Veteran’s Day, Thanksgiving Day and Christmas Day and any other day specifically declared by the President of the United States to be a national holiday. Comment by Rhodes, Karen R. (NCO20) (she/her/hers): There’s 11 in this list.

4. SCHEDULING:

The total period of performance is 410 calendar days. A written work schedule identifying the work schedule shall be submitted to the project COR for review and approval. All work must be scheduled through individuals as identified by the COR. VA reserves right to establish order and priority of work.

Calendar Days Total Period of Performance (Calendar Days)

Phase I Comment by Rhodes, Karen R. (NCO20) (she/her/hers): Are we going to have multiple NTPs? Comment by Berlemann Jr, Charles H.: No there will not be multiple NTPs. It is just how Seattle VAMC is trying to stage the construction project. We have to do the external work and

Phase II, Phase IIA, IIB, and III

Phase I – is all primarily external demolition and construction work that will support the installation of a sterilization processing service trailer. This will include but not excludeThe associated any civil engineering work required to provide mechanical hook ups to a sterilization trailer and an access decking for where the trailer will be installed per the supplied drawings and construction specifications. Comment by Rhodes, Karen R. (NCO20) (she/her/hers): This is ambiguous.

Phase II through Phase III shall be the related work to renovate the Sterilization Processing Services and associated spaces that are in Building 100 at VAPSHCS per the supplied drawings and construction specifications. Comment by Rhodes, Karen R. (NCO20) (she/her/hers): This font looks odd

5. CONTRACTOR PERSONNEL BADGES AND PARKING:

a. The contractor shall provide the COR with a list of contractor employees expected to enter the buildings to pick up confidential documents. While on VA premises, all contractor personnel shall comply with the rules, regulations, and procedures governing the conduct of personnel and the operation of the facility.

b. An access badge will be given to the contractor’s employee upon entrance into VA buildings. The contractor employee must safeguard the access badge and immediately report any lost, stolen, or destroyed badges to the COR. All contract personnel must properly display their access badges. Access badges must be worn at or above the waist and facing forward. The contractor’s employees must return the access badge(s) to the COR or designee at the end of each pick-up processthe day. Comment by Rhodes, Karen R. (NCO20) (she/her/hers): If they’re over 180 days, don’t they need a PIV? Comment by Berlemann Jr, Charles H.: Yes. However, the Seattle badging process seems to take forever to get folks on PIV badging. So we are using paper access badges until PIV is completed. Comment by Rhodes, Karen R. (NCO20) (she/her/hers): Wouldn’t this be at end of day?

c. The contractor shall be required to comply with all security policies/requirements of the VA Puget Sound Healthcare System. All security policies/requirements must be met, and employees cleared prior to the contractor performing work under this contract. Contractors that cannot meet the security and clearance requirements shall not be allowed to perform work under this contract. Comment by Rhodes, Karen R. (NCO20) (she/her/hers): Where can these be found? Comment by Berlemann Jr, Charles H.: They have been added as references to this SOW. Comment by Rhodes, Karen R. (NCO20) (she/her/hers): How is this accomplished? Comment by Berlemann Jr, Charles H.: This will be completed when the contractors submit their employees for the badging process. Comment by Berlemann Jr, Charles H.:

d. It is the responsibility of the contractor’s personnel to park in the appropriate designated parking areas. Parking information shall be coordinated with the facility COR.

6. INTERFERENCE TO NORMAL FUNCTION:

Contractor may be required to interrupt their work at any time so as not to interfere with the normal functioning of the facility, including utility services, fire protection systems, and passage of facility patients, personnel, equipment, and carts.

a. In the event of an emergency, contractor services may be stopped and rescheduled at no additional cost to the government.

b. Contractor personnel shall inform the COR or the designee of the need to gain access to secured areas. If access is required to secure areas, prearranged scheduling will be made with COR or designee.

7. PRIVACY OFFICER LANGUAGE FOR STATEMENT OF WORK (SOW): Comment by Rhodes, Karen R. (NCO20) (she/her/hers): Is this in here because of the way they filled out their 6500? Comment by Berlemann Jr, Charles H.: No this is boiler plate that is included because the local privacy office wants it included in all SOWs.

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

9.

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

11.

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

13.

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

15.

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

17.

18. PRIVACY OFFICER LANGUAGE FOR STATEMENT OF WORK (SOW): Comment by Rhodes, Karen R. (NCO20) (she/her/hers): Is this in here because of the way they filled out the 6500? Comment by Berlemann Jr, Charles H.: No this is boiler plate that is included because the local privacy office wants it included in all SOWs.

19. 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:

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

21.

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

23.

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

25.

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

27.

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

29.

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

31.

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

33.

34. 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.].

35.

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

37.

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

39.