36C10B24Q0225 Final.docx

36C10B24Q0225

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.

UEI:

EFT:

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. NOV 2021)

PREVIOUS EDITION IS NOT USABLE

Prescribed by GSA - FAR (48 CFR) 53.212

7. FOR SOLICITATION

INFORMATION CALL:

STANDARD FORM 1449

SOLICITATION/CONTRACT/ORDER FOR COMMERCIAL PRODUCTS AND COMMERCIAL SERVICES

OFFEROR TO COMPLETE BLOCKS 12, 17, 23, 24, & 30

Joseph Jeranek, Contract Specialist 848-377-5247 06-12-2024 15:00

EDT

36C10B Department of Veterans Affairs Technology Acquisition Center

23 Christopher Way Eatontown NJ 07724

X

541519 $34 Million

N/A

XX

See Delivery Schedule

36C10B Department of Veterans Affairs Technology Acquisition Center

23 Christopher Way Eatontown NJ 07724

TBD

36C10A

Technology Acquisition Center Financial Services Center PO Box 149971 Austin TX 78714-8971

Building Management Computer Control Systems Charles George VAMC, Asheville, North Carolina

POC:

Joseph Jeranek; Joseph.Jeranek@va.gov

Alternate POC:

Kendra Casebolt; Kendra.Casebolt@va.gov

Period of Performance:

12-month base with four 12-month option periods

Kendra M. Casebolt Contracting Officer

Table of Contents

SECTION B - CONTINUATION OF SF 1449 BLOCKS

B.1 CONTRACT ADMINISTRATION DATA

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

a. CONTRACTOR: TBD

b. GOVERNMENT: Contracting Officer 36C10B Department of Veterans Affairs Technology Acquisition Center 23 Christopher Way Eatontown NJ 07724

2. CONTRACTOR REMITTANCE ADDRESS: All payments by the Government to the contractor will be made in accordance with:

3. INVOICES: Invoices shall be submitted in arrears:

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.

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

B.2 GOVERNING LAW CLAUSE

Federal law and regulations, including the Federal Acquisition Regulations (FAR), shall govern this Contract/Order. Commercial license agreements may be made a part of this Contract/Order but only if both parties expressly make them an addendum hereto, as permitted by FAR 12.212. If the commercial license agreement is not made an addendum, it shall not apply, govern, be a part of or have any effect whatsoever on the Contract/Order; this includes, but is not limited to, any agreement embedded in the computer software (clickwrap), any agreement that is otherwise delivered with or provided to the Government with the commercial computer software or documentation (shrinkwrap), or any other license agreement otherwise referred to in any document. If a commercial license agreement is made an addendum, only those provisions addressing data rights regarding the Government’s use, duplication and disclosure of data (e.g., restricted computer software) are included and made a part of this Contract/Order, and only to the extent that those provisions are not duplicative or inconsistent with Federal law, Federal regulation, the incorporated FAR clauses and the provisions of this Contract/Order; those provisions in the commercial license agreement that do not address data rights regarding the Government’s use, duplication and disclosure of data shall not be included or made a part of the Contract/Order. Federal law and regulation including, without limitation, the Contract Disputes Act (41 U.S.C. § 7101 et seq.), the Anti-Deficiency Act (31 U.S.C. § 1341 et seq.), the Competition in Contracting Act (41 U.S.C. § 3301 et seq.), the Prompt Payment Act (31 U.S.C. § 3901 et seq.), Contracts for Data Processing or Maintenance (38 USC § 5725), and FAR clauses 52.212-4, 52.227-14, 52.227-19 shall supersede, control, and render ineffective any inconsistent, conflicting, or duplicative provision in any commercial license agreement. In the event of conflict between this clause and any provision in the Contract/Order or the commercial license agreement or elsewhere, the terms of this clause shall prevail. The Contractor shall deliver to the Government all data first produced under this Contract/Order with unlimited rights as defined by FAR 52.227-14. Claims of patent or copyright infringement brought against the Government as a party shall be defended by the U.S. Department of Justice (DOJ) in accordance with 28 U.S.C. § 516; at the discretion of DOJ, the Contractor may be allowed reasonable participation in the defense of the litigation. Any additional changes to the Contract/Order must be made by modification (Standard Form 30) and shall only be made by a warranted Contracting Officer. Nothing in this Contract/Order or any commercial license agreement shall be construed as a waiver of sovereign immunity.

B.3 SOFTWARE LICENSE, SOFTWARE MAINTENANCE AND SOFTWARE TECHNICAL SUPPORT

(1). Definitions.

a) Licensee. The term “licensee” shall mean the U.S. Department of Veterans Affairs (“VA”) and is synonymous with “Government.”

b) Licensor. The term “licensor” shall mean the Contractor having the necessary license or ownership rights to deliver license, software maintenance and support of the computer software being acquired. The term “Contractor” is the party identified in Block 17a on the SF1449. If the Contractor is a reseller and not the Licensor, the Contractor remains responsible for performance under this Contract/Order.

c) Software. The term “software” shall mean the licensed computer software product(s) cited in the Schedule of Supplies/Services.

d) Maintenance. The term “maintenance” is the process of enhancing and optimizing software, as well as remedying defects. It shall include all new fixes, patches, releases, updates, versions and upgrades, as further defined below.

e) Technical Support. The term “technical support” refers to the range of services providing assistance for the software via the telephone, email, a website or otherwise.

f) Release or Update. The term “release” or “update” are terms that refer to a revision of software that contains defect corrections, minor enhancements, or improvements of the software’s functionality. This is usually designated by a change in the number to the right of the decimal point (e.g., from Version 5.3 to 5.4). An example of an update is the addition of new hardware.

g) Version or Upgrade. The term “version” or “upgrade” are terms that refer to a revision of software that contains new or improved functionality. This is usually designated by a change in the number to the left of the decimal point (e.g., from Version 5.4 to 6).

(2). Software License.

a) Unless otherwise stated in the Schedule of Supplies/Services, the Performance Work Statement or Product Description, the software license provided to the Government is a perpetual, nonexclusive license to use the software.

b) The Government may use the software in a networked environment.

c) Any dispute regarding the license grant or usage limitations shall be resolved in accordance with the Disputes Clause incorporated in FAR 52.212-4(d).

d) All limitations of software usage are expressly stated in the Schedule of Supplies/Services and the Performance Work Statement/Product Description.

(3). Software Maintenance and/or Technical Support.

a) If the Government desires to continue software maintenance and support beyond the period of performance identified in this Contract/Order, the Government will issue a separate contract or order for maintenance and support. Conversely, if a contract or order for continuing software maintenance and technical support is not received, the Contractor is neither authorized nor permitted to renew any of the previously furnished services.

b) The Contractor shall provide software support services, which includes periodic updates, enhancements and corrections to the software, and reasonable technical support, all of which are customarily provided by the Contractor to its commercial customers to cause the software to perform according to its specifications, documentation or demonstrated claims.

c) Any telephone support provided by Contractor shall be at no additional cost.

d) The Contractor shall provide all maintenance services in a timely manner in accordance with the Contractor’s customary practice or as defined in the Performance Work Statement or Product Description. However, prolonged delay (exceeding two business days) in resolving software problems will be noted in the Government’s various past performance records on the Contractor (e.g., www.cpars.gov).

e) If the Government allows the maintenance and support to lapse and subsequently wishes to reinstate it, any reinstatement fee charged shall not exceed the amounts that would have been charged if the Government had not allowed the subscription to lapse.

(4). Disabling Software Code.

The Government requires delivery of computer software that does not contain any code that will, upon the occurrence or the nonoccurrence of any event, disable the software. Such code includes but is not limited to a computer virus, restrictive key, node lock, time-out, or other function, whether implemented by electronic, mechanical, or other means, which limits or hinders the use or access to any computer software based on residency on a specific hardware configuration, frequency of duration of use, or other limiting criteria. If any such disabling code is present, the Contractor agrees to indemnify the Government for all damages suffered as a result of a disabling caused by such code, and the contractor agrees to remove such code upon the Government’s request at no extra cost to the Government. Inability of the Contractor to remove the disabling software code will be considered an inexcusable delay and a material breach of contract, and the Government may exercise its right to terminate for cause. In addition, the Government is permitted to remove the code as it deems appropriate and charge the Contractor for consideration for the time and effort expended in removing the code.

(5). Manuals and Publications.

Upon Government request, the Contractor shall furnish the most current version of the user manual and publications for all products/services provided under this Contract/Order at no cost.

B.4 SCHEDULE OF SUPPLIES/SERVICES

NOTE: Offerors are required to complete Section B.4, in its entirety and submit with their respective quote. Offerors are cautioned that alterations to, or failure to propose pricing for any of, the line items specified below may render quotes unacceptable and therefore, ineligible for award. Please be advised that any successful Offeror’s Section B.4 submitted in response to this Request for Quotation will be incorporated into any resulting award and thereby serve as the Offeror’s Pricing for the life of the contract. All questions shall be directed to the Contract Specialist, Joseph Jeranek, Joseph.Jeranek@va.gov, 848-377-5101 prior to the closing date and time specified in Block 8 on page 1 of the SF 1449.

BASE PERIOD

Period of Performance (PoP): 12 months from Date of Award

This FFP Contract Line-Item Number (CLIN) shall include labor, materials, and other direct costs required for the successful completion of the services and deliverables detailed in PWS paragraph 4.0 and all associated subparagraphs.

Due 30 days after receipt of order (ARO) and updated every 30 days after.

Due within three (3) working days following last day of each month.

Due 30 days ARO.

IAW PWS 4.4

Due 15 days ARO

Work shall be executed in accordance with funding provided at time of award or under formal modification. Work shall not commence unless and until funding is provided by the Contracting Officer.

This Time and Material (T&M) CLIN includes work required for the performance of PWS paragraph 4.8.

$15,000.00

NTE

$15,000.00

Due 30 days ARO and every 30 days after.

This FFP CLIN shall include labor, materials, and other direct costs required for the successful completion of the services and deliverables detailed in PWS paragraph 5.0.

The cost of CLIN 0003 shall be included and allocated to CLIN 0001.

Due within 3 business days ARO.

OPTION PERIOD ONE

This 12-month option period may be exercised at the Government’s discretion In Accordance With (IAW) Federal Acquisition Regulation (FAR) 52.217-9, Option to Extend the Term of the Contract. Work shall not commence until, and unless, a formal modification is issued by the contracting officer. If exercised, the 12-month Option Period is to commence immediately upon expiration of the Base Period.

If exercised, the PoP shall be: 12 months from end of the Base Period

This FFP CLIN shall include labor, materials, and other direct costs required for the successful completion of the services and deliverables detailed in PWS paragraph 4.0 and all associated subparagraphs.

Due every 30 days.

Due within three (3) working days following last day of each month

Due 30 days ARO

IAW PWS 4.4

Due 15 days ARO

Work shall be executed in accordance with funding provided at time of award or under formal modification. Work shall not commence unless and until funding is provided by the Contracting Officer.

This T&M CLIN included work required for the performance of PWS paragraph 4.8.

$15,000.00

NTE

$15,000.00

Due 30 days ARO and every 30 days after.

This FFP CLIN shall include labor, materials, and other direct costs required for the successful completion of the services and deliverables detailed in PWS paragraph 5.0.

The cost of CLIN 1003 shall be included and allocated to CLIN 1001.

Due within 3 business days ARO.

OPTION PERIOD TWO

This 12-month option period may be exercised at the Government’s discretion In Accordance With (IAW) Federal Acquisition Regulation (FAR) 52.217-9, Option to Extend the Term of the Contract. Work shall not commence until, and unless, a formal modification is issued by the contracting officer. If exercised, the 12-month Option Period is to commence immediately upon expiration of Option Period One.

If exercised, the PoP shall be: 12 months from end of the Option Period One

This FFP CLIN shall include labor, materials, and other direct costs required for the successful completion of the services and deliverables detailed in PWS paragraph 4.0 and all associated subparagraphs.

Due every 30 days.

Due within three (3) working days following last day of each month.

Due 30 days ARO.

IAW PWS 4.4

Due 15 days ARO

Work shall be executed in accordance with funding provided at time of award or under formal modification. Work shall not commence unless and until funding is provided by the Contracting Officer.

This T&M CLIN included work required for the performance of PWS paragraph 4.8.

$15,000.00

NTE

$15,000.00

Due 30 days ARO and every 30 days after.

This FFP CLIN shall include labor, materials, and other direct costs required for the successful completion of the services and deliverables detailed in PWS paragraph 5.0.

The cost of CLIN 2003 shall be included and allocated to CLIN 2001.

Due within 3 business days ARO.

OPTION PERIOD THREE

This 12-month option period may be exercised at the Government’s discretion In Accordance With (IAW) Federal Acquisition Regulation (FAR) 52.217-9, Option to Extend the Term of the Contract. Work shall not commence until, and unless, a formal modification is issued by the contracting officer. If exercised, the 12-month Option Period is to commence immediately upon expiration of Option Period Two.

If exercised, the PoP shall be: 12 months from end of Option Period Two

This FFP CLIN shall include labor, materials, and other direct costs required for the successful completion of the services and deliverables detailed in PWS paragraph 4.0 and all associated subparagraphs.

Due every 30 days.

Due within three (3) working days following last day of each month.

Due 30 days ARO.

IAW PWS 4.4

Due 15 days ARO

Work shall be executed in accordance with funding provided at time of award or under formal modification. Work shall not commence unless and until funding is provided by the Contracting Officer.

This T&M CLIN included work required for the performance of PWS paragraph 4.8.

$15,000.00

NTE

$15,000.00

Due 30 days ARO and every 30 days after.

This FFP CLIN shall include labor, materials, and other direct costs required for the successful completion of the services and deliverables detailed in PWS paragraph 5.0.

The cost of CLIN 3003 shall be included and allocated to CLIN 3001.

Due within 3 business days ARO.

OPTION PERIOD FOUR

This 12-month option period may be exercised at the Government’s discretion In Accordance With (IAW) Federal Acquisition Regulation (FAR) 52.217-9, Option to Extend the Term of the Contract. Work shall not commence until, and unless, a formal modification is issued by the contracting officer. If exercised, the 12-month Option Period is to commence immediately upon expiration of Option Period Three.

If exercised, the PoP shall be: 12 months from end of Option Period Three

This FFP CLIN shall include labor, materials, and other direct costs required for the successful completion of the services and deliverables detailed in PWS paragraph 4.0 and all associated subparagraphs.

Due every 30 days.

Due within three (3) working days following last day of each month.

Due 30 days ARO.

IAW PWS 4.4

Due 15 days ARO

Work shall be executed in accordance with funding provided at time of award or under formal modification. Work shall not commence unless and until funding is provided by the Contracting Officer.

This T&M CLIN included work required for the performance of PWS paragraph 4.8.

$15,000.00

NTE

$15,000.00

Due 30 days ARO and every 30 days after.

This FFP CLIN shall include labor, materials, and other direct costs required for the successful completion of the services and deliverables detailed in PWS paragraph 5.0.

The cost of CLIN 4003 shall be included and allocated to CLIN 4001.

Due within 3 business days ARO.

Page 1 of Summary

Base Period Total

B.5 PERFORMANCE WORK STATEMENT

Performance Work Statement (PWS)

Charles George VAMC Asheville, North Carolina Building Management Computer Control Systems

Date: March 14, 2024

VA-24-00014005

PWS Version Number: 4.0

1.0 BACKGROUND

The Department of Veterans Affairs (VA) strives to provide high quality, effective, and efficient Information Technology (IT) services to those responsible for providing care to the Veterans at the point-of-care as well as throughout all the points of the Veterans’ health care in an effective, timely and compassionate manner.

The Charles George VA Medical Center (VAMC) requires maintenance on its Building Management Computer System (BMCS).

VA is seeking a contractor to furnish all labor and equipment necessary to maintain the BMCS at Charles George VAMC in accordance with system manufacturer and VA. The current main front end for this system is a custom multiple server arrangement that was designed by Automation Systems (ASI) with a hardware platform consisting of four (4) servers and software applications supporting but not limited to the ABB, American Automatrix, Computrols, Cisco, interconnected via multimode fiber network, and SonicWall appliances.

There are also third party and integrated systems interconnected to the campus system including but not limited to the following: Johnson Controls Legacy system (N2 protocol, American Automatrix (Legacy System), Eaton, and a Linux based Web Server array Appliance. The network is comprised of a Cisco Business class 350 network which utilizes multimode network for the main tier infrastructure within the hospital operating at 2GB. The second-tier network which provides connections to all of the main controllers is accomplished through 1GB ethernet connections utilizing CAT 6E cabling. These systems monitor, control, and provide alarms for critical HVAC and related systems that provide the proper engineering environment for hospital operations.

2.0 APPLICABLE DOCUMENTS

In the performance of the tasks associated with this Performance Work Statement, the Contractor shall comply with the following:

1. 44 U.S.C. § 3541-3549, “Federal Information Security Management Act (FISMA) of 2002”

2. “Federal Information Security Modernization Act of 2014”

3. Federal Information Processing Standards (FIPS) Publication 140-2, “Security Requirements for Cryptographic Modules”

4. FIPS Pub 199. “Standards for Security Categorization of Federal Information and Information Systems,” February 2004

5. FIPS Pub 200, “Minimum Security Requirements for Federal Information and Information Systems,” March 2006

6. FIPS Pub 201-2, “Personal Identity Verification of Federal Employees and Contractors,” August 2013

7. 10 U.S.C. § 2224, "Defense Information Assurance Program"

8. 5 U.S.C. § 552a, as amended, “The Privacy Act of 1974.”

9. Public Law 109-461, Veterans Benefits, Health Care, and Information Technology Act of 2006, Title IX, Information Security Matters

10. 42 U.S.C. § 2000d “Title VI of the Civil Rights Act of 1964”

11. VA Directive 0710, “Personnel Security and Suitability Program,” June 4, 2010, https://www.va.gov/vapubs/index.cfm

12. VA Handbook 0710, “Personnel Security and Suitability Program,” May 2, 2016, https://www.va.gov/vapubs/index.cfm

13. VA Directive and Handbook 6102, “Internet/Intranet Services,” August 5, 2019

14. 36 C.F.R. Part 1194 “Information and Communication Technology Standards and Guidelines,” January 18, 2017

15. Office of Management and Budget (OMB) Circular A-130, “Managing Federal Information as a Strategic Resource,” July 28, 2016

16. 32 C.F.R. Part 199, “Civilian Health and Medical Program of the Uniformed Services (CHAMPUS)”

17. NIST SP 800-66 Rev. 1, “An Introductory Resource Guide for Implementing the Health Insurance Portability and Accountability Act (HIPAA) Security Rule,” October 2008

18. Sections 504 and 508 of the Rehabilitation Act (29 U.S.C. § 794d), as amended, January 18, 2017

19. Homeland Security Presidential Directive (12) (HSPD-12), August 27, 2004

20. VA Directive 6500, “VA Cybersecurity Program,” February 24, 2021

21. VA Handbook 6500, “Risk Management Framework for VA Information Systems VA Information Security Program,” February 24, 2021

22. VA Handbook 6500.2, “Management of Breaches Involving Sensitive Personal Information (SPI),” March 12, 2019

23. VA Handbook 6500.5, “Incorporating Security and Privacy into the System Development Lifecycle,” March 22, 2010

24. VA Handbook 6500.6, “Contract Security,” March 12, 2010

25. VA Handbook 6500.8, “Information System Contingency Planning,” April 6, 2011

26. VA Handbook 6500.10, “Mobile Device Security Policy,” February 15, 2018

27. VA Handbook 6500.11, “VA Firewall Configuration,” August 22, 2017

28. OIT Process Asset Library (PAL), https://www.va.gov/process/ . Reference Process Maps at https://www.va.gov/process/maps.asp and Artifact templates at https://www.va.gov/process/artifacts.asp

29. One-VA Technical Reference Model (TRM) (reference at https://www.va.gov/trm/TRMHomePage.aspx)

30. VA Directive 6508, “Implementation of Privacy Threshold Analysis and Privacy Impact Assessment,” October 15, 2014

31. VA Handbook 6508.1, “Procedures for Privacy Threshold Analysis and Privacy Impact Assessment,” July 30, 2015

32. VA Handbook 6510, “VA Identity and Access Management,” January 15, 2016

33. VA Directive and Handbook 6513, “Secure External Connections,” October 12, 2017

34. VA Directive 6300, “Records and Information Management,” September 21, 2018

35. VA Handbook, 6300.1, “Records Management Procedures,“ March 24, 2010

36. NIST SP 800-37 Rev 2, “Risk Management Framework for Information Systems and Organizations: A System Life Cycle Approach for Security and Privacy,” December 2018

37. NIST SP 800-53 Rev. 5, “Security and Privacy Controls for Federal Information Systems and Organizations,” September 23, 2020 (includes updates as of 12/10/2020)

38. VA Directive 0735, “Homeland Security Presidential Directive 12 (HSPD-12) Program,” October 26, 2015

39. VA Handbook 0735, “Homeland Security Presidential Directive 12 (HSPD-12) Program,” March 24, 2014

40. OMB Memorandum 05-24, “Implementation of Homeland Security Presidential Directive (HSPD) 12 – Policy for a Common Identification Standard for Federal Employees and Contractors,” August 5, 2005

41. OMB Memorandum M-19-17, “Enabling Mission Delivery Through Improved Identity, Credential, and Access Management,” May 21, 2019

42. OMB Memorandum, “Guidance for Homeland Security Presidential Directive (HSPD) 12 Implementation,” May 23, 2008

43. Federal Identity, Credential, and Access Management (FICAM) Roadmap and Implementation Guidance, December 2, 2011, (NOTE: Part A of the FICAM Roadmap and Implementation Guidance, v2.0, was replaced in 2015 with an updated Architecture (https://arch.idmanagement.gov/#what-is-the-ficam-architecture)

44. NIST SP 800-116 Rev 1, “Guidelines for the Use of Personal Identity Verification (PIV) Credentials in Facility Access,“ June 2018

45. NIST SP 800-63-3, 800-63A, 800-63B, 800-63C, “Digital Identity Guidelines,” updated March 02, 2020

46. NIST SP 800-157, “Guidelines for Derived PIV Credentials,” December 2014

47. NIST SP 800-164, “Guidelines on Hardware-Rooted Security in Mobile Devices (Draft),” October 2012

48. Draft National Institute of Standards and Technology Interagency Report (NISTIR) 7981, “Mobile, PIV, and Authentication,” March 2014

49. VA Memorandum, VAIQ #7100147, “Continued Implementation of Homeland Security Presidential Directive 12 (HSPD-12),” April 29, 2011 (reference https://www.voa.va.gov/documentlistpublic.aspx?NodeID=514)

50. IAM Identity Management Business Requirements Guidance document, May 2013, (reference Enterprise Architecture Section, PIV/IAM (reference https://www.voa.va.gov/documentlistpublic.aspx?NodeID=514)

51. VA Memorandum “Personal Identity Verification (PIV) Logical Access Policy Clarification,” July 17, 2019, https://www.voa.va.gov/DocumentView.aspx?DocumentID=4896

52. Trusted Internet Connections (TIC) 3.0 Core Guidance Documents, https://www.cisa.gov/publication/tic-30-core-guidance-documents

53. OMB Memorandum M-19-26, “Update to the Trusted Internet Connections (TIC) Initiative,” September 12, 2019

54. OMB Memorandum M-08-23, “Securing the Federal Government’s Domain Name System Infrastructure,” August 22, 2008

55. Sections 524 and 525 of the Energy Independence and Security Act of 2007, (Public Law 110–140), December 19, 2007

56. Section 104 of the Energy Policy Act of 2005, (Public Law 109–58), August 8, 2005

57. Executive Order 13834, “Efficient Federal Operations,” dated May 17, 2018

58. Executive Order 13221, “Energy-Efficient Standby Power Devices,” August 2, 2001

59. VA Directive 0058, “VA Green Purchasing Program,” July 19, 2013

60. VA Handbook 0058, “VA Green Purchasing Program,” July 19, 2013

61. Office of Information Security (OIS) VAIQ #7424808 Memorandum, “Remote Access,” January 15, 2014, https://www.voa.va.gov/DocumentListPublic.aspx?NodeId=28

62. Clinger-Cohen Act of 1996, 40 U.S.C. §11101 and §11103

63. “Veteran Focused Integration Process (VIP) Guide 4.0,” January 2021, https://www.voa.va.gov/DocumentView.aspx?DocumentID=4371

64. VA Memorandum “Proper Use of Email and Other Messaging Services,” January 2, 2018, https://www.voa.va.gov/DocumentListPublic.aspx?NodeId=28

65. “DevSecOps Product Line Management Playbook” version 2.0, May 2021, https://www.voa.va.gov/DocumentView.aspx?DocumentID=4946

66. NIST SP 500-267B Revision 1, “USGv6 Profile,” November 2020

67. OMB Memorandum M-21-07, “Completing the Transition to Internet Protocol Version 6 (IPv6),” November 19, 2020

68. Social Security Number (SSN) Fraud Prevention Act of 2017

69. Section 240 of the Consolidated Appropriations Act (CAA) 2018, March 23, 2018

3.0 SCOPE OF WORK

The Contractor shall provide maintenance of VAMC BMCS at Charles George VAMC in accordance with system manufacturer specifications and VA policies. This task shall include hardware maintenance, software maintenance, training, software development, software customization, software repair, and hardware repair.

PERFORMANCE DETAILS

3.1 PERFORMANCE PERIOD

The Period of Performance (PoP) shall be 12 months from date of award, with four (4) 12-month option periods. The overall Period of Performance shall not exceed 60 months.

Any work at the Government site shall not take place on Federal holidays or weekends unless directed by the Contracting Officer (CO). If required, the CO may designate the Contractor to work during holidays and weekends.

There are eleven (11) Federal holidays set by law (USC Title 5 Section 6103) that VA follows:

Under current definitions, five are set by date:

If any of the above falls on a Saturday, then Friday shall be observed as a holiday. Similarly, if one falls on a Sunday, then Monday shall be observed as a holiday.

The other six are set by a day of the week and month:

3.2 PLACE OF PERFORMANCE

Tasks under this PWS shall be performed in VA facility, Charles George, located in Asheville, NC VAMC. Work may be performed at remote locations with prior concurrence from the Contracting Officer’s Representative (COR).

The Contractor shall be on site during regular business hours unless permission granted by the Utility Systems Supervisor between regular working hours of 7:30am to 4pm (eight-hour work per day). The Contractor will have a technician on site 40 hours a week not counting federal holidays. There will be work time needed outside regular business hours due to the needs of particular services or for emergency work. These conditions shall be coordinated with prior approval from the COR and will count towards 40 hours a week of service. The Contractor shall be no more than 125 miles away from the Charles George VA Facility.

3.3 TRAVEL

The Government does not anticipate travel under this effort to perform the tasks associated with the effort.

4.0 SPECIFIC TASKS AND DELIVERABLES

The Contractor shall perform maintenance on the Charles George VAMC BMCS.

Historically, this task has taken one staff year, with one on-site person, performing all duties list in section 5. The BMCS for purposes of this agreement, shall include all control(s) systems connected to the BMCS that are used to monitor and control critical systems throughout the hospital via independent network. This includes the PC's, servers, software, programming, graphics, data, and communication network of the BMCS. Instances of this equipment are air handlers, exhaust fans, refrigeration systems, chillers, cooling towers, isolation room controls, potable water controls, domestic heating systems, etc. Also included are the components in the field used to monitor, enable, and control the systems such as positioners, actuators, communication panels (to include all their panel contents, sensors, relays, inputs and outputs, controllers, software, power supplies, Uninterruptable Power Supplies (UPS), panel parts) to the final components that display data and/or are controllable. This includes any equipment installed after its warranty phase.

4.1 PROJECT MANAGEMENT

4.1.1 CONTRACTOR PROJECT MANAGEMENT PLAN

The Contractor shall deliver a Contractor Project Management Plan (CPMP) that lays out the Contractor’s approach, timeline, and tools to be used in execution of the contract. The CPMP should take the form of both a narrative and graphic format that displays the schedule, milestones, risks, and resource support. The CPMP shall also include how the Contractor shall coordinate and execute planned, routine, and ad hoc data collection reporting requests as identified within the PWS. The initial baseline CPMP shall be concurred upon and updated in accordance with Section B of the contract. The Contractor shall update and maintain the VA PM approved CPMP throughout the PoP.

Deliverable:

A. Contractor Project Management Plan

4.1.2 REPORTING REQUIREMENTS

The Contractor shall provide the COR a Monthly Report in Microsoft Word, either hand delivered or emailed (segregated by each system, and its associated devices and sensors) for all equipment in the system. The report shall clearly and concisely describe the data of services rendered, parts replaced, and repairs performed, the report will be in the form agreed with and approved by the COR and structured according to system. The report shall prescribe current problems anticipated future needs of the equipment and systems for preventive and predictive maintenance. The report shall be submitted to the COR within three working days following the last day of each month.

Deliverable:

A. Monthly Report

4.2 MONITORING AND TROUBLE SHOOTING

The entire network shall be monitored and alerted 24 hours a day, 7 days a week. Services for the network and servers shall include the following; Network hardware troubleshooting and repair, System patches and updates which are to be managed automatically, Root cause identification and proactive/automated repairs, 3rd party vendor engagement - for specialized software/application support, both on-site and on-site managed backups (daily), Basic DNS based Web content/virus filtering license, Enterprise-grade centralized Anti-Virus protection license, Enterprise-grade centralized Anti-Malware protection license, Patch management and system updates to address critical security issues, Firewall protection and monitoring. Licenses for the software are purchased by VA and are not part of this TO.

Knowledge and certifications in the following are expected in order to properly fulfill the task:

Computrols Engineering, Johnson Controls Engineering, American Automatrix Certification, ABB Certification, Microsoft Solutions Partner Modern Work Certification, On Staff Azure Administrators, Web Root Antivirus Platform Certification, Dell Partner Direct, VMWare Principal Partner and Cloud Provider, Cisco Certification, and SOC 2 Compliant.

The Contractor shall be able to program and shall program (when necessary) the front end and entire database used in the system, using the design tools that come with any front end that is used at the hospital as well as any programming tools developed by the manufacturers and environments described in this section. The current main system is Computrols CBAS20 and the programming tool is called CBAS Professional. During regular business hours there is a not to exceed four-hour response to equipment problems if a technician is not on site. The technician will check in with the COR when arriving and leaving the job site.

The Contractor should keep an adequate supply of critical parts on hand so to minimize equipment down time. A list of critical parts must be given to the Utility Systems Supervisor within 30 days that will be kept on site. Any parts that are on site at the start of the contract do not count against the parts cost for the year. Critical parts that are not on site must be supplied within 24 hours of the problem being noted. The Contractor must inform the COR before expending any costs beyond what is included in this contract (see optional task in section 4.8).

The Contractor shall maintain, secure and monitor 24/7, the remote access to the BMCS for technical assistance. Various portals shall be maintained to allow various additional departments within the facility and remotely to monitor and control the BMCS as well as providing for Systems Supervisors to monitor and control the system remotely in case of problems after hours and to monitor system performance. This includes the internet access and the software needed to access the system. Information needed for the sign in will be given to the Systems Supervisor within five working days of the contract being awarded. Security of the system is the responsibility of the Contractor and a security plan must be presented to the COR within 30 days of award of the contract. There should be a system in place to monitor and detect attempted unauthorized access of the system.

The Contractor will provide a monthly report for the PM, repairs, and parts cost for the month. Each month's report should also include the total cost of parts for the year up to that point. Technicians should communicate the need to replace a part prior to doing the repair with the Systems Supervisor and communicate the cost of the part. Anything beyond the expected costs in this contract, the Contractor will provide a quote to the Systems Supervisor for the cost of any part that needs to be replaced, the quote should be at the Contractors cost and no more than a 10% markup on the part. The VA can request to see the invoice to show the Contractors cost on any part. The COR and CO will decide whether to exercise the task in section 5.8 to cover this additional expense.

The Contractor shall provide an online portal for the COR to place work orders and to document the status of repairs and work.

Below is the itemized equipment covered under this effort: