RFP - 36C10B21R0006 - Final 22 DEC.pdf

PAGE 1 OF 1. REQUISITION NO.

2. CONTRACT NO. 3. AWARD/EFFECTIVE DATE 4. ORDER NO. 5. SOLICITATION NUMBER 6. SOLICITATION ISSUE DATE

a. NAME b. TELEPHONE NO. (No Collect Calls) 8. OFFER DUE DATE/LOCAL

TIME

9. ISSUED BY CODE 10. THIS ACQUISITION IS UNRESTRICTED OR SET ASIDE: % FOR:

SMALL BUSINESS

HUBZONE SMALL

BUSINESS

SERVICE-DISABLED

VETERAN-OWNED

SMALL BUSINESS

WOMEN-OWNED SMALL BUSINESS

(WOSB) ELIGIBLE UNDER THE WOMEN-OWNED

SMALL BUSINESS PROGRAM

EDWOSB

8(A)

NAICS:

SIZE STANDARD:

11. DELIVERY FOR FOB DESTINA-

TION UNLESS BLOCK IS

MARKED

SEE SCHEDULE

12. DISCOUNT TERMS

13a. THIS CONTRACT IS A

RATED ORDER UNDER

DPAS (15 CFR 700)

13b. RATING

14. METHOD OF SOLICITATION

RFQ IFB RFP

15. DELIVER TO CODE 16. ADMINISTERED BY CODE

17a. CONTRACTOR/OFFEROR CODE FACILITY CODE 18a. PAYMENT WILL BE MADE BY CODE

TELEPHONE NO. DUNS: DUNS+4:

PHONE: FAX:

17b. CHECK IF REMITTANCE IS DIFFERENT AND PUT SUCH ADDRESS IN OFFER

18b. SUBMIT INVOICES TO ADDRESS SHOWN IN BLOCK 18a UNLESS BLOCK BELOW IS CHECKED

SEE ADDENDUM

19. 20. 21. 22. 23. 24.

ITEM NO. SCHEDULE OF SUPPLIES/SERVICES QUANTITY UNIT UNIT PRICE AMOUNT

(Use Reverse and/or Attach Additional Sheets as Necessary)

25. ACCOUNTING AND APPROPRIATION DATA 26. TOTAL AWARD AMOUNT (For Govt. Use Only)

27a. SOLICITATION INCORPORATES BY REFERENCE FAR 52.212-1, 52.212-4. FAR 52.212-3 AND 52.212-5 ARE ATTACHED. ADDENDA ARE ARE NOT ATTACHED.

27b. CONTRACT/PURCHASE ORDER INCORPORATES BY REFERENCE FAR 52.212-4. FAR 52.212-5 IS ATTACHED. ADDENDA ARE ARE NOT ATTACHED

28. CONTRACTOR IS REQUIRED TO SIGN THIS DOCUMENT AND RETURN _______________ 29. AWARD OF CONTRACT: REF. ___________________________________ OFFER COPIES TO ISSUING OFFICE. CONTRACTOR AGREES TO FURNISH AND DATED ________________________________. YOUR OFFER ON SOLICITATION DELIVER ALL ITEMS SET FORTH OR OTHERWISE IDENTIFIED ABOVE AND ON ANY (BLOCK 5), INCLUDING ANY ADDITIONS OR CHANGES WHICH ARE ADDITIONAL SHEETS SUBJECT TO THE TERMS AND CONDITIONS SPECIFIED SET FORTH HEREIN IS ACCEPTED AS TO ITEMS:

30a. SIGNATURE OF OFFEROR/CONTRACTOR 31a. UNITED STATES OF AMERICA (SIGNATURE OF CONTRACTING OFFICER)

30b. NAME AND TITLE OF SIGNER (TYPE OR PRINT) 30c. DATE SIGNED 31b. NAME OF CONTRACTING OFFICER (TYPE OR PRINT) 31c. DATE SIGNED

AUTHORIZED FOR LOCAL REPRODUCTION (REV. 2/2012)

PREVIOUS EDITION IS NOT USABLE Prescribed by GSA - FAR (48 CFR) 53.212

7. FOR SOLICITATION

INFORMATION CALL:

STANDARD FORM 1449

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

SOLICITATION/CONTRACT/ORDER FOR COMMERCIAL ITEMS 79

36C10B21R0006 12-07-2020

Susan Meng 732-440-9676 12-30-2020 11:00 a

Department of Veterans Affairs Technology Acquisition Center

23 Christopher Way Eatontown NJ 07724 x

541519

$30 Million

N/A

X

See Delivery Schedule

23 Christopher Way Eatontown NJ 07724

Financial Services Center PO Box 149971 Austin TX 78714-8971

See CONTINUATION Page

Site Survey to Implement a Data Center Facilities Monitoring Tool

This Request for Proposal (RFP) will result in a Firm-Fixed- Price Price (FFP) contract.

Period of Performance (PoP): 60 month PoP with Optional Tasks Offerors will be evaluated in accordance with Section E.

Contacts:

Susan Meng, susan.meng@va.gov Contracting Specialist

Heather Paragano, heather.paragano@va.gov Contracting Officer

This is a small business set-aside in accordance with FAR 52.219-6 Notice of Total Small Business Set-Aside Small Business Set-Aside

See CONTINUATION Page

X X

36C10B21R0006

Table of Contents

SECTION A

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

SECTION B - CONTINUATION OF SF 1449 BLOCKS

B.1 CONTRACT ADMINISTRATION DATA

B.2 GOVERNING LAW CLAUSE

B.3 PRICE SCHEDULE

B.5 PERFORMANCE WORK STATEMENT

1.0 BACKGROUND

2.0 APPLICABLE DOCUMENTS

3.0 SCOPE OF WORK

4.0 PERFORMANCE DETAILS

4.1 PERFORMANCE PERIOD

4.2 PLACE OF PERFORMANCE

4.3 TRAVEL

5.0 SPECIFIC TASKS AND DELIVERABLES

5.1 PROJECT MANAGEMENT

5.1.1 CONTRACTOR PROJECT MANAGEMENT PLAN

5.1.2 REPORTING REQUIREMENTS

5.1.3 KICK OFF MEETING

5.2 SITE SURVEY

5.2.1 SITE READINESS

5.2.1.1 SITE SURVEY REPORT

5.2.1.2 SITE DRAWINGS

5.2.1.3 SITE FLOOR PLANS

5.2.1.4 SUPPORTING DOCUMENTATION

5.3 OEM AND/OR SERVICE PROVIDER ENGAGEMENT

5.4 OPTIONAL TASKS –SITE SURVEYS (FULL)

5.4.1 Cleveland Regional Data Center, 1620 E 105th Street, Building Data Center North, Room BM-660, Cleveland, Ohio, 44106

5.4.2 Brooklyn Regional Data Center, 800 Poly Place, Building 14, Brooklyn, New York, 11209 25

5.4.3 Temple Regional Data Center, 1901 Veterans Memorial Drive, Building 222, Room 106, Temple, Texas, 76504

5.4.4 Little Rock Regional Data Center, 2200 Fort Roots Drive, Building 102, Room 104, North Little Rock, Arkansas, 721146

5.5 OPTIONAL TASKS –SITE SURVEYS (PARTIAL)

5.5.1 AITC, 1615 Woodward Street, Austin, TX 78772

5.5.2 HITC, 5000 South 5th Avenue, Building 215, Hines, IL 60141

5.5.3 PITC, 5000 Wissahickon Avenue, Philadelphia, PA 19144

5.5.4 CRRC, 221 Butler Ave, Building 511, Martinsburg, WV 25405

5.5.5 Orlando Regional Data Center, 2500 S Lakemont Avenue, Room 134 A/B, Orlando, Florida, 32814

5.5.6 Cleveland Regional Data Center, 1620 E 105th Street, Building Data Center North, Room BM-660, Cleveland, Ohio, 44106

5.5.7 Brooklyn Regional Data Center, 800 Poly Place, Building 14, Brooklyn, New York, 11209 25

5.5.8 Temple Regional Data Center, 1901 Veterans Memorial Drive, Building 222, Room 106, Temple, Texas, 76504

5.5.9 Little Rock Regional Data Center, 2200 Fort Roots Drive, Building 102, Room 104, North Little Rock, Arkansas, 721146

6.0 GENERAL REQUIREMENTS

6.1 ENTERPRISE AND IT FRAMEWORK

6.1.1 VA TECHNICAL REFERENCE MODEL

6.1.2 FEDERAL IDENTITY, CREDENTIAL, AND ACCESS MANAGEMENT (FICAM)

6.1.3 INTERNET PROTOCOL VERSION 6 (IPV6)

6.1.4 STANDARD COMPUTER CONFIGURATION

6.1.5 VETERAN FOCUSED INTEGRATION PROCESS (VIP)

6.1.6 PROCESS ASSET LIBRARY (PAL)

6.1.7 AUTHORITATIVE DATA SOURCES

6.2 POSITION/TASK RISK DESIGNATION LEVEL(S)

6.2.1 CONTRACTOR PERSONNEL SECURITY REQUIREMENTS

6.3 METHOD AND DISTRIBUTION OF DELIVERABLES

6.4 PERFORMANCE METRICS

6.5 FACILITY/RESOURCE PROVISIONS

ADDENDUM A – ADDITIONAL VA REQUIREMENTS, CONSOLIDATED

ADDENDUM B – VA INFORMATION AND INFORMATION SYSTEM SECURITY/PRIVACY

LANGUAGE

SECTION C - CONTRACT CLAUSES

C.1 52.252-2 CLAUSES INCORPORATED BY REFERENCE (FEB 1998)

C.2 52.204-21 BASIC SAFEGUARDING OF COVERED CONTRACTOR INFORMATION

SYSTEMS (JUN 2016)

C.3 52.204-25 PROHIBITION ON CONTRACTING FOR CERTAIN

TELECOMMUNICATIONS AND VIDEO SURVEILLANCE SERVICES OR EQUIPMENT

(AUG 2020)

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

STATUTES OR EXECUTIVE ORDERS—COMMERCIAL ITEMS (OCT 2020)

C.5 52.217-7 OPTION FOR INCREASED QUANTITY-SEPERATELY PRICED LINE ITEM.

(MAR 1989)

C.6 VAAR 852.212-70 PROVISIONS AND CLAUSES APPLICABLE TO VA ACQUISITION

OF COMMERCIAL ITEMS. (APR 2020)

SECTION D - CONTRACT DOCUMENTS, EXHIBITS, OR ATTACHMENTS

SECTION E - SOLICITATION PROVISIONS

E.1 52.252-1 SOLICITATION PROVISIONS INCORPORATED BY REFERENCE (FEB 1998)

E.2 52.204-26 COVERED TELECOMMUNICATION EQUIPMENT OR SERVICES-

REPRESENTATION (OCT 2020)

E.3 52.209-7 INFORMATION REGARDING RESPONSIBILITY MATTERS (OCT 2018)

E.4 52.212-3 OFFEROR REPRESENTATIONS AND CERTIFICATIONS – COMMERCIAL

ITEMS (OCT 2020)

E.5 52.216-1 TYPE OF CONTRACT (APR 1984)

E.6 52.233-2 SERVICE OF PROTEST (SEP 2006)

E.7 52.212-2 EVALUATION – COMMERCIAL ITEMS (OCT 2014)

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

Attn: Heather Paragano heather.paragano@va.gov

Department of Veterans Affairs Office of Procurement, Acquisition and Logistics 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:

[X] 52.232-33, Payment by Electronic Funds Transfer—System For Award

Management

3. INVOICES: Invoices shall be submitted in arrears:

a. Quarterly []

b. Semi-Annually []

c. Other [X – Upon acceptance of deliverables/services in Section B]

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.

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

AMENDMENT NO DATE

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 U.S.C. § 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 PRICE SCHEDULE

All deliverables must be submitted to the VA Program Manager (PM), Contracting Officer’s Representative (COR), and Contracting Officer unless otherwise specified in the line item.

Please be advised that in accordance with Federal Acquisition Regulation (FAR) Part 2.101, a “day” means, unless otherwise specified, a CALENDAR day. Additionally, deliverables with due dates falling on a weekend or holiday shall be submitted the following Government workday after the weekend or holiday

Deliverables shall be provided via electronic submission to: VA Program Manager (PM), Contracting Officer’s Representative (COR) and Contracting Officer (CO).

Inspection: Destination Acceptance: Destination

BASE PERIOD

Period of Performance (PoP) shall be 60 months

Contract Line Item Number

(CLIN)

Description Qty Unit Unit Price Extended Price

0001 Project Management in accordance with (IAW) Performance Work Statement (PWS) Section 5.1 and its subtasks.

This CLIN includes all tasks, labor, and travel required for the successful completion of the services details in PWS Section 5.1 and its subtasks.

60 Month (Mo)

0001AA Contractor Project Management Plan

IAW PWS 5.1.1.

Due Thirty (30) days after contract award and updated monthly thereafter.

1 LO NSP NSP

0001AB Weekly Progress Report IAW PWS 5.1.2.

Due weekly throughout the PoP.

0001AC Draft Agenda IAW PWS 5.1.3.

Due three (3) days prior to the Contract kick off meeting.

0001AD Post Award Kickoff Meeting Minutes

IAW PWS 5.1.3.

Due the third calendar day after the kick-off meeting.

0002 Site Survey IAW PWS 5.2.

This CLIN includes all tasks, labor, and travel required for the successful completion of the services details in PWS Section 5.2 and its subtasks.

1 LO $ $

0002AA Draft Agenda (Survey Kick Off Meeting) IAW PWS 5.2.1

Due three (3) days prior to the Survey kick-off meeting

1 LO NSP NSP

0002AB Survey Kickoff Meeting Minutes IAW

PWS 5.2.1

Due by the third calendar day after the pre-survey kick-off meeting

1 LO NSP NSP

0002AC Site Survey Report IAW PWS 5.2.1.1

Due forty-five (45) days after the completion of the site survey and no later than sixty (60) days after Award

1 LO NSP NSP

0002AD Network Architecture Diagram

IAW PWS 5.2.1.2

Due forty-five (45) days after the completion of the site survey and no later than sixty (60) days after Contract Award

1 LO NSP NSP

0002AE Device Connection Diagrams IAW PWS 5.2.1.2

Due forty-five (45) days after the completion of the site survey and no later than sixty (60) days after Contract Award

1 LO NSP NSP

0002AF Device Network Interface Diagrams

IAW PWS 5.2.1.2

Due forty-five (45) days after the completion of the site survey and no later than sixty (60) days after Contract Award

1 LO NSP NSP

0002AG Site Floor Plans IAW PWS 5.2.1.3

Due forty-five days (45) after the completion of the site survey and no later than sixty (60) days after Contract Award

0002AH OEM/ASP Documentation/manual IAW

PWS 5.2.1.4

Due forty-five days (45) after the completion of the site survey and no later than sixty (60) days after Contract Award

1 LO NSP NSP

0003 OEM and/or Service Provider Engagement IAW PWS 5.3.

This CLIN includes all tasks, labor, and travel required for the successful completion of the services details in PWS Section 5.3

1 LO $ $

0003AA Device Monitoring Feasibility and Assessment Report IAW PWS 5.3

Due forty-five (45) days after the completion of the site survey and no later than sixty (60) days after Award.

1 LO NSP NSP

0004 Contractor Staff Roster IAW PWS 6.2.1 Due three (3) days after contract award and updated throughout the PoP.

1 LO $ $

TOTAL BASE PERIOD $

OPTIONAL TASKS

These optional tasks may be exercised IAW FAR 52.217-7 Option for Increased Quantity- Separately Price Line Item. Work shall not commence until, and unless, a formal modification is issued by the Contracting Officer. These optional tasks may be exercised at any time during the PoP.

Contract Line Item Number

(CLIN)

Description Qty Unit Unit Price Extended Price

0005 Full Site Survey - Cleveland Regional Data Center IAW PWS 5.4.1

If exercised, the Contractor is responsible for deliverables under SLINs 0001AA, 0001AB, 0002AA through 0002AH and 0003AA.

This CLIN includes all tasks, labor, and travel required for the successful completion of the services details in PWS Section 5.1 through 5.3 and its subtasks.

1 LO $ $

May be exercised one-time throughout the entire period of performance.

0006 Full Site Survey - Brooklyn Regional Data Center IAW PWS 5.4.2

If exercised, the Contractor is responsible for deliverables under SLINs 0001AA, 0001AB, 0002AA through 0002AH and 0003AA.

This CLIN includes all tasks, labor, and travel required for the successful completion of the services details in PWS Section 5.1 through 5.3 and its subtasks.

May be exercised one-time throughout the entire period of performance.

0007 Full Site Survey - Temple Regional Data Center IAW PWS 5.4.3

If exercised, the Contractor is responsible for deliverables under SLINs 0001AA, 0001AB, 0002AA through 0002AH and 0003AA.

This CLIN includes all tasks, labor, and travel required for the successful completion of the services details in PWS Section 5.1 through 5.3 and its subtasks.

May be exercised one-time throughout

0008 Full Site Survey - Little Rock Regional Data Center IAW PWS 5.4.4

If exercised, the Contractor is responsible for deliverables under SLINs 0001AA, 0001AB, 0002AA through 0002AH and 0003AA.

This CLIN includes all tasks, labor, and travel required for the successful completion of the services details in PWS Section 5.1 through 5.3 and its subtasks.

May be exercised one-time, throughout the entire period of performance.

0009 Partial Site Survey-AITC IAW PWS 5.5.1

If exercised, the Contractor is responsible for deliverables under SLINs 0001AA, 0001AB, 0002AA through 0002AH and 0003AA.

This CLIN includes all tasks, labor, and travel required for the successful completion of the services details in PWS Section 5.1 through 5.3 (with the exception of 5.1.3) and its subtasks.

May be exercised up to two times throughout the entire period of performance

NTE

LO $ $

0010 Partial Site Survey -HITC IAW PWS 5.5.2

If exercised, the Contractor is responsible for deliverables under SLINs 0001AA, 0001AB, 0002AA through 0002AH and 0003AA.

This CLIN includes all tasks, labor, and travel required for the successful completion of the services details in PWS Section 5.1 through 5.3 (with the exception of 5.1.3) and its subtasks.

May be exercised up to two times throughout the entire period of performance

NTE

LO $ $

0011 Partial Site Survey -PITC IAW PWS 5.5.3 If exercised, the Contractor is responsible for deliverables under SLINs 0001AA, 0001AB, 0002AA through 0002AH and 0003AA.

This CLIN includes all tasks, labor, and travel required for the successful completion of the services details in PWS Section 5.1 through 5.3 (with the exception of 5.1.3) and its subtasks.

NTE

LO $ $

May be exercised up to two times throughout the entire period of performance

0012 Partial Site Survey - CRRC IAW PWS 5.5.4

If exercised, the Contractor is responsible for deliverables under SLINs 0001AA, 0001AB, 0002AA through 0002AH and 0003AA.

This CLIN includes all tasks, labor, and travel required for the successful completion of the services details in PWS Section 5.1 through 5.3 (with the exception of 5.1.3) and its subtasks.

May be exercised up to two times throughout the entire period of performance

NTE

LO $ $

0013 Partial Site Survey - Orlando Regional Data Center IAW PWS 5.5.5

If exercised, the Contractor is responsible for deliverables under SLINs 0001AA, 0001AB, 0002AA through 0002AH and 0003AA.

This CLIN includes all tasks, labor, and travel required for the successful completion of the services details in PWS Section 5.1 through 5.3 (with the exception of 5.1.3) and its subtasks.

May be exercised up to two times throughout the entire period of performance

NTE

LO $ $

0014 Partial Site Survey - Cleveland Regional Data Center IAW PWS 5.5.6

If exercised, the Contractor is responsible for deliverables under SLINs 0001AA, 0001AB, 0002AA through 0002AH and 0003AA.

This CLIN includes all tasks, labor, and travel required for the successful completion of the services details in

NTE

PWS Section 5.1 through 5.3 (with the exception of 5.1.3) and its subtasks.

May be exercised up to two times throughout the entire period of performance

0015 Partial Site Survey - Brooklyn Regional Data Center IAW PWS 5.5.7

If exercised, the Contractor is responsible for deliverables under SLINs 0001AA, 0001AB, 0002AA through 0002AH and 0003AA.

This CLIN includes all tasks, labor, and travel required for the successful completion of the services details in PWS Section 5.1 through 5.3 (with the exception of 5.1.3) and its subtasks.

May be exercised up to two times throughout the entire period of performance

NTE

LO $ $

0016 Partial Site Survey - Temple Regional Data Center IAW PWS 5.5.8

If exercised, the Contractor is responsible for deliverables under SLINs 0001AA, 0001AB, 0002AA through 0002AH and 0003AA.

This CLIN includes all tasks, labor, and travel required for the successful completion of the services details in PWS Section 5.1 through 5.3 (with the exception of 5.1.3) and its subtasks.

May be exercised up to two times throughout the entire period of performance

NTE

LO $ $

0017 Partial Site Survey - Little Rock Regional Data Center IAW PWS 5.5.9

If exercised, the Contractor is responsible for deliverables under SLINs 0001AA, 0001AB, 0002AA through 0002AH and 0003AA.

NTE

This CLIN includes all tasks, labor, and travel required for the successful completion of the services details in PWS Section 5.1 through 5.3 (with the exception of 5.1.3) and its subtasks.

May be exercised up to two times throughout the entire period of performance

OPTIONAL TASKS TOTAL $

BASE + OPTIONS TOTAL $

B.5 PERFORMANCE WORK STATEMENT

1.0 BACKGROUND

The Department of Veterans Affairs (VA), Office of Information & Technology, Infrastructure Operations (IO), National Data Center Operations & Logistics, Data Center Operations (DCO), Connectivity 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. VA depends on Information Management/Information Technology (IM/IT) systems to meet mission goals.

DCO is one of four pillars of IO with responsibility for business operations, facilities management, telecommunications, and physical security. DCO provides 24x7 facilities cooling and power monitoring to its customers.

DCO has a requirement for a Site Survey to be conducted to obtain facility device information in order to implement a Data Center Facilities Systems Monitoring Tool. The Data Center Facilities Monitoring Tool provides a single pane view across all sites to monitor the operational health status of facilities equipment and provides real-time monitoring and alert capability for electrical, heating, ventilation, air conditioning and environmental conditions in and around data center computer room operations. The Site Survey shall be conducted at the Regional Data Center (RDC) located at the VA Medical Center (VAMC) in Orlando, FL.

The goal of the Site Survey is to gather accurate site-specific data for the Data Center Facilities Systems Monitoring Tool to be seamlessly implemented in Orlando RDC. The existing Nlyte Energy Monitoring Optimizer (NEO) monitoring tool has been implemented to date in the Austin Information Technology Center (AITC), Philadelphia Information Technology Center (PITC) and Hines Information Technology Center (HITC) and will be implemented in the Regional Data Centers as part of the planned expansion.

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 2016

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. Carnegie Mellon Software Engineering Institute, Capability Maturity Model®

Integration for Development (CMMI-DEV), Version 1.3 November 2010; and Carnegie Mellon Software Engineering Institute, Capability Maturity Model® Integration for Acquisition (CMMI-ACQ), Version 1.3 November 2010

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

10. Public Law 109-461, Veterans Benefits, Health Care, and Information Technology

Act of 2006, Title IX, Information Security Matters

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

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

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

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

15. 36 C.F.R. Part 1194 “Information and Communication Technology Standards and

Guidelines,” January 18, 2017

16. Office of Management and Budget (OMB) Circular A-130, “Managing Federal

Information as a Strategic Resource,” July 28, 2016

17. 32 C.F.R. Part 199, “Civilian Health and Medical Program of the Uniformed

Services (CHAMPUS)”

18. NIST SP 800-66 Rev. 1, An Introductory Resource Guide for Implementing the

Health Insurance Portability and Accountability Act (HIPAA) Security Rule, October 2008

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

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

21. VA Directive 6500, “VA Cybersecurity Program,” January 24, 2019

22. VA Handbook 6500, “Risk Management Framework for VA Information Systems –

Tier 3: VA Information Security Program,” March 10, 2015

23. VA Handbook 6500.2, “Management of Breaches Involving Sensitive Personal

Information (SPI)”, July 28, 2016

24. VA Handbook 6500.3, “Assessment, Authorization, And Continuous Monitoring Of

VA Information Systems,” February 3, 2014

25. VA Handbook 6500.5, “Incorporating Security and Privacy into the System

Development Lifecycle”, March 22, 2010

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

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

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

29. OI&T 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

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

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

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

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

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

35. VA Directive 6300, Records and Information Management, September 21, 2018

36. VA Handbook, 6300.1, Records Management Procedures, March 24, 2010

37. NIST SP 800-37 Rev 1, Risk Management Framework for Information Systems and

Organizations: A System Life Cycle Approach for Security and Privacy, December

38. NIST SP 800-53 Rev. 4, Security and Privacy Controls for Federal Information Systems and Organizations, January 22, 2015

39. OMB Memorandum, “Transition to IPv6”, September 28, 2010

40. VA Directive 0735, Homeland Security Presidential Directive 12 (HSPD-12)

Program, October 26, 2015

41. VA Handbook 0735, Homeland Security Presidential Directive 12 (HSPD-12)

Program, March 24, 2014

42. OMB Memorandum M-06-18, Acquisition of Products and Services for

Implementation of HSPD-12, June 30, 2006

43. OMB Memorandum 04-04, E-Authentication Guidance for Federal Agencies, December 16, 2003

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

45. OMB memorandum M-11-11, “Continued Implementation of Homeland Security Presidential Directive (HSPD) 12 – Policy for a Common Identification Standard for Federal Employees and Contractors, February 3, 2011

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

47. Federal Identity, Credential, and Access Management (FICAM) Roadmap and Implementation Guidance, December 2, 2011

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

49. OMB Memorandum M-07-16, Safeguarding Against and Responding to the Breach of Personally Identifiable Information, May 22, 2007

50. NIST SP 800-63-3, 800-63A, 800-63B, 800-63C, Digital Identity Guidelines, December 2017

51. NIST SP 800-157, Guidelines for Derived PIV Credentials, December 2014

52. NIST SP 800-164, Guidelines on Hardware-Rooted Security in Mobile Devices

(Draft), October 2012

53. Draft National Institute of Standards and Technology Interagency Report (NISTIR)

7981 Mobile, PIV, and Authentication, March 2014

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

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

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

57. Trusted Internet Connections (TIC) Reference Architecture Document, Version 2.2, Federal Interagency Technical Reference Architectures, Department of Homeland Security, June 19, 2017, https://www.dhs.gov/sites/default/files/publications/TIC_Ref_Arch_v2.2_2017.pdf

58. OMB Memorandum M-08-05, “Implementation of Trusted Internet Connections (TIC), November 20, 2007

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

60. VA Memorandum, VAIQ #7497987, Compliance – Electronic Product Environmental Assessment Tool (EPEAT) – IT Electronic Equipment, August 11, 2014 (reference Document Libraries, EPEAT/Green Purchasing Section, https://www.voa.va.gov/documentlistpublic.aspx?NodeID=552)

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

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

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

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

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

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

67. Office of Information Security (OIS) VAIQ #7424808 Memorandum, “Remote

Access”, January 15, 2014, https://www.voa.va.gov/DocumentListPublic.aspx?NodeId=28

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

69. “Veteran Focused Integration Process (VIP) Guide 3.2”, December 2018, https://www.voa.va.gov/DocumentView.aspx?DocumentID=4371

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

3.0 SCOPE OF WORK

The Contractor shall perform a detailed site survey capturing all mechanical, electrical, cooling and life safety devices to produce a report that includes all information required to install the NEO data center facilities monitoring tool. The VA estimates the Orlando RDC device count range is between 90 and 110 with a total required monitoring point count between 1,100 and 1,300. The scope also includes optional tasks for additional site surveys at locations listed in PWS 5.4 and 5.5. The Contractor shall verify all devices capable of being monitored and shall identify the recommended monitoring points per device.

4.0 PERFORMANCE DETAILS

4.1 PERFORMANCE PERIOD

The Period of Performance (PoP) shall be 60 months with four (4) optional tasks for full site surveys at additional sites and nine (9) optional tasks for follow on partial surveys at all sites listed in 4.2 for additional devices. These optional tasks may be exercised at the government’s discretion at any time during the period of performance.

Any work at the Government site shall not take place on Federal holidays or weekends unless directed by the Contracting Officer (CO).

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

Under current definitions, four are set by date:

New Year's Day January 1 Independence Day July 4 Veterans Day November 11 Christmas Day December 25

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:

Martin Luther King's Birthday Third Monday in January Washington's Birthday Third Monday in February Memorial Day Last Monday in May Labor Day First Monday in September Columbus Day Second Monday in October Thanksgiving Fourth Thursday in November

4.2 PLACE OF PERFORMANCE

Tasks under this PWS shall be performed in VA facilities located at the Orlando VAMC Lakemont Campus, 2500 S Lakemont Avenue, Orlando, FL 32814.

If the optional tasks are exercised (in accordance with 5.4 and 5.5), these tasks will be performed at the following sites:

1. Cleveland Regional Data Center, 1620 E 105th Street, Building Data Center North, Room BM-660, Cleveland, Ohio, 44106

2. Brooklyn Regional Data Center, 800 Poly Place, Building 14, Brooklyn, New York, 11209

3. Temple Regional Data Center, 1901 Veterans Memorial Drive, Building 222, Room 106, Temple, Texas, 76504

4. Little Rock Regional Data Center, 2200 Fort Roots Drive, Building 102, Room 104, North Little Rock, Arkansas, 721146

5. AITC, 1615 Woodward Street, Austin, TX 78772

6. HITC, 5000 South 5th Avenue, Building 215, Hines, IL 60141

7. PITC, 5000 Wissahickon Avenue, Philadelphia, PA 19144

8. Capital Regional Readiness Center (CRRC), 221 Butler Ave, Building 511, Martinsburg, WV 25405

4.3 TRAVEL

The Government anticipates travel under this effort to perform the tasks associated with the effort, as well as to attend program-related meetings throughout the PoP. All estimated travel costs shall be included in the firm-fixed price line items. These costs will not be directly reimbursed by the Government.

The total estimated number of trips in support of the program related meetings for this effort is two (2) trips for the initial site survey at RDC VAMC Orlando, FL, estimated at (ten) 10 days total duration and three (3) persons per trip:

If the optional tasks under 5.4 are exercised, travel will be required to:

1. Cleveland Regional Data Center, 1620 E 105th Street, Building Data Center North, Room BM-660, Cleveland, Ohio, 44106 estimated at two (2) trips, fifteen (15) days total duration and three (3) persons per trip.

2. Brooklyn Regional Data Center, 800 Poly Place, Building 14, Brooklyn, New York, 11209 estimated at one (1) trip, three (3) days total duration and three (3) persons per trip.

3. Temple Regional Data Center, 1901 Veterans Memorial Drive, Building 222, Room 106, Temple, Texas, 76504 estimated at two (2) trips, ten (10) days total duration and three (3) persons per trip.

4. Little Rock Regional Data Center, 2200 Fort Roots Drive, Building 102, Room 104, North Little Rock, Arkansas, 721146 estimated at one (1) trip, three (3) days total duration and three (3) persons per trip.

If the optional tasks under 5.5 are exercised, travel will be required to:

1. AITC), 1615 Woodward Street, Austin, TX 78772 estimated at one (1) trip, five (5) days total duration and two (2) persons per trip.

2. HITC, 5000 South 5th Avenue, Building 215, Hines, IL 60141 estimated at one (1) trip, five (5) days total duration and two (2) persons per trip.

3. PITC, 5000 Wissahickon Avenue, Philadelphia, PA 19144 estimated at one (1) trip, five

(5) days total duration and two (2) persons per trip.

4. CRRC, 221 Butler Ave, Building 511, Martinsburg, WV 25405 estimated at one (1) trip, five (5) days total duration and two (2) persons per trip.

5. Orlando Regional Data Center, 2500 S Lakemont Avenue, Room 134 A/B, Orlando, Florida, 32814 estimated at one (1) trip, five (5) days total duration and two (2) persons per trip.

6. Cleveland Regional Data Center, 1620 E 105th Street, Building Data Center North, Room BM-660, Cleveland, Ohio, 44106 estimated at one (1) trip, five (5) days total duration and two (2) persons per trip.

7. Brooklyn Regional Data Center, 800 Poly Place, Building 14, Brooklyn, New York, 11209 estimated at one (1) trip, three (3) days total duration and two (2) persons per trip.

8. Temple Regional Data Center, 1901 Veterans Memorial Drive, Building 222, Room 106, Temple, Texas, 76504 estimated at one (1) trip, five (5) days total duration and two (2) persons per trip.

9. Little Rock Regional Data Center, 2200 Fort Roots Drive, Building 102, Room 104, North Little Rock, Arkansas, 721146 estimated at one (1) trip, three (3) days total duration and two (2) persons per trip.

5.0 SPECIFIC TASKS AND DELIVERABLES

5.1 PROJECT MANAGEMENT

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

5.1.2 REPORTING REQUIREMENTS

The Contractor shall provide the COR with Weekly Progress Reports in electronic form in Microsoft Word and Project formats. The report shall include detailed instructions/explanations for each required data element, to ensure that data is accurate and consistent. These reports shall reflect data as of the last day of the preceding week.

The Weekly Progress Reports shall cover all work completed during the reporting period and work planned for the subsequent reporting period. The report shall also identify any problems that arose and a description of how the problems were resolved. If problems have not been completely resolved, the Contractor shall provide an explanation including their plan and timeframe for resolving the issue. The report shall also include an itemized list of all Information and Communication Technology (ICT) deliverables and their current Section 508 conformance status. The Contractor shall monitor performance against the CPMP and report any deviations. It is expected that the Contractor will keep in communication with VA accordingly so that issues that arise are transparent to both parties to prevent escalation of outstanding issues.

The Contractor shall attend weekly teleconference meetings with the COR and VA Project Team to discuss the status of the tasks.

Deliverable:

A. Weekly Progress Report

5.1.3 KICK OFF MEETING

A technical kickoff meeting shall be held within 10 days after award. The Contractor shall coordinate the date, time, and location (can be virtual) with the Contracting Officer (CO), the VA PM, the Contract Specialist (CS), and the Contracting Officer Representative (COR). The Contractor shall provide a draft agenda to the CO and VA PM at least five calendar days prior to the meeting. Upon Government approval of a final agenda, the Contractor shall distribute to all meeting attendees. During the kickoff-meeting, the Contractor shall present the details of the intended approach, work plan, and project schedule for each effort via a Microsoft Office PowerPoint presentation.

At the conclusion of the meeting, the Contractor shall update the presentation with a final slide entitled “Summary Report” which shall include notes on any major issues, agreements, or disagreements discussed during the kickoff meeting. The Contractor shall a prepare and distribute the meeting minutes of the kickoff meeting to the CO, COR and all attendees within three calendar days after the meeting. The Contractor shall obtain concurrence from the CS on the content of the meeting minutes prior to distribution of the document.

Deliverable:

A. Draft Agenda B. Post Award Kickoff Meeting Minutes

5.2 SITE SURVEY

5.2.1 SITE READINESS

The Contractor shall conduct a site survey at the location indicated in section 4.2 of this PWS.

Upon Award, VA will provide an initial list of devices obtained during initial discovery and a copy of site floor plans, if available, to form the basis of the survey. The device list and floor plan information is preliminary and by no means exhaustive, conclusive or vetted. It shall be the Contractor’s responsibility to verify and add to the device list and update the floor plans to provide a complete picture of facility devices including physical location supporting mechanical, electrical, cooling and life safety devices.

A site survey kick-off meeting shall be conducted prior to the start of the survey with facilities and engineering stakeholders who will provide insight into the facilities operations with specific focus on devices supporting mechanical, electrical, cooling and life safety for the purposes of monitoring and reporting. The Contractor shall provide a draft agenda to the COR and VA PM at least five calendar days prior to the meeting. Upon Government approval of a final agenda, the Contractor shall distribute to all meeting attendees. The Contractor shall prepare and distribute the meeting minutes to the COR and all attendees within three calendar days after the meeting. The Contractor shall obtain concurrence from the COR on the content of the meeting minutes prior to distribution of the document.

Deliverable:

A. Draft Agenda B. Pre-Survey Kickoff Meeting Minutes

5.2.1.1 SITE SURVEY REPORT

The Contractor’s report shall include platform requirements, site specific requirements, floor, cabinet (rack) and device specific information in a tabulated excel format to allow for easy manipulation of the data. In some cases, the information is not readily available through visual device inspection alone and the Contractor shall access the device communication interface, with prior VA approval, to verify specific device details (make, model, serial number, communications protocol, etc) required in order to monitor the device. The Contractor shall structure the report to include the following tabs:

1. Virtual Machine (VM) requirements

a. Processor – Virtual Core Processing Units (vCPUs)

b. Virtual host bus adapter (vHBA)

c. Storage - Disk space

d. Virtual Memory (vMemory)

e. Networking equipment

f. Network bandwidth

g. Operating System (OS)

2. Site Specific Report identifying unique site considerations and potential installation issues with a risk assessment of each

3. Floor Level Report:

a. Design Watts/Square Footage

b. Total Watt Capacity

c. Temperature Low Set Point

d. Temperature Overflow Size

e. Room Height

f. Room Depth

g. Total Square Footage

h. Usable Square Feet

i. Temperature High Set Point

j. Raised Floor Height

k. Room Width

4. Cabinet Level Report (Data Center):

a. Grid Location

b. Manufacturer

c. Height (in Rack Units)

d. Rating (Watts)

Circuit information – Power Distribution Unit (PDU)/Remote Panel Power (RPP) and panel associated with each circuit

5. Device Detail Report:

a. Device Type

b. Location

c. Room and floor/grid location

d. Unique device labeling

e. Quantity

f. Make and model

g. Serial Number

h. Communications protocol (TCP, Modbus, BACnet, dry contacts, etc)

i. Is the device interface web based?

j. Is the device currently monitored? If yes, how?

k. Was the device monitored in the past? If yes, how?

l. Does the device network interface require hardware, firmware or software upgrades to enable monitoring?

m. Does the current communication protocol, if applicable, support Simple Network

Management Protocol (SNMP) version 3?

n. If yes, provide detailed description of hardware (make, model), firmware or software upgrades and cost to enable monitoring.

o. Detailed description of how the hardware, firmware or software upgrades would be performed, the potential impact (risk assessment), time required to perform, resources required and backout plan.

p. Is the device cabled to the network? If yes, is the existing cabling sufficient for monitoring?

q. Existing IP address (if available from device interface)

r. Network switch location, model, unique identifier

s. Visual inspection of available network ports

t. Network patch panel (if equipped)

u. Recommended monitoring points per device

v. Recommendations on how to monitor device if not direct connect (for example, via existing Building Management System (BMS) or other existing monitoring solution.

6. Device Summary (Roll-up) High Level Report:

a. Device type

b. Total quantity

c. Manufacturer

d. Make/Model

e. Current monitoring status

f. Recommended number of monitoring points per device

g. Summary of monitoring points per device type

h. Total cables required (layout, type and quantity)

i. IP addressing (Total quantity of Private Addresses and Subnet)

7. Device Monitoring Point Report:

a. Device Type

b. Total devices with locations (buildings/floor/room numbers)

c. Recommended monitoring points

Deliverable:

A. Site Survey Report

5.2.1.2 SITE DRAWINGS

The Contractor shall provide detailed network architecture diagrams of the planned solution to and how it will seamlessly interface with the existing NEO monitoring systems located at AITC, PITC and HITC. The Contractor shall provide connection diagrams from the device level showing the physical cable connection points from a floor level to VA network or gateways. The Contractor shall provide detailed diagrams for each device showing the device network interface and how the network connection is made to each.

Deliverables:

A. Network Architecture Diagram B. Device Connection Diagrams C. Device Network Interface Diagrams

5.2.1.3 SITE FLOOR PLANS

The Contractor shall create a visual representation of all devices by developing floor plans in Microsoft Visio by room for all devices to be monitored as gathered in the Site Survey Report.

The floor plans shall include room orientation (North, South, East, West), doorways and any other recognizable markings to assist with device placement in each room. For Data Center floorplans, the Contractor shall display the z-grid tile location (border) around the perimeter of the room. Devices shall be represented by simple objects. PDU/RPP objects shall be color-coded beige (tan), Uninterruptible Power Supply (UPS) servicing data center shall be color-coded gold, cooling related objects shall be color-coded blue.

A. Floor Plans

5.2.1.4 SUPPORTING DOCUMENTATION

The Contractor shall provide copies of all Original Equipment Manufacturer (OEM) and/or Authorized Service Provider (ASP) documentation for devices detailing planned methods of procedure (mop) for connecting devices to external monitoring system. This information shall include Object Identification (OID), BACnet mapping and registers and Management Information Database (MIB) table entries to be used for each monitored point during configuration of the NEO system.

A. OEM/ASP documentation/manual

5.3 OEM AND/OR SERVICE PROVIDER ENGAGEMENT

Upon request by the COR, the Contractor shall act as a consultant for VA by engaging with OEMs and/or ASPs to determine the feasibility of monitoring a VA facility device, if further analysis on how to connect to the NEO system is required. In some cases, the best way to access the device’s monitored points may be via an existing Building Management System (BMS), Supervisory Control and Data Acquisition System (SCADA) or other existing control/monitoring system versus direct connect to the device itself. The Contractor shall perform a feasibility study and produce a report with viable options. It is anticipated that the Contractor shall perform online searches, conduct phone discussions or meetings with vendors and request/receive technical information from vendors in order to produce the report. The report shall include a detailed risk assessment, resource matrix, responsibility matrix, level of effort, expected timeline to implement, connection diagram and pros and cons for the proposed solution and a back out plan.

The report shall include a detailed assessment of the data type and number of points that will be ascertained from the proposed method. The Contractor shall present the final plan to VA COR for review.

A. Device Monitoring Feasibility and Assessment Report

5.4 OPTIONAL TASKS –SITE SURVEYS (FULL)

The Contractor shall provide additional full site surveys at RDCs listed below. The Contractor shall perform all PWS requirements and deliverables in sections 5.1, 5.2 and 5.3 with the exception of 5.1.3. Optional tasks under 5.4 may be exercised individually, one-time, throughout

5.4.1 Cleveland Regional Data Center, 1620 E 105th Street, Building Data Center North, Room BM-660, Cleveland, Ohio, 44106

5.4.2 Brooklyn Regional Data Center, 800 Poly Place, Building 14, Brooklyn, New York, 11209

5.4.3 Temple Regional Data Center, 1901 Veterans Memorial Drive, Building 222, Room 106, Temple, Texas, 76504

5.4.4 Little Rock Regional Data Center, 2200 Fort Roots Drive, Building 102, Room 104, North Little Rock, Arkansas, 721146

5.5 OPTIONAL TASKS –SITE SURVEYS (PARTIAL)

The Contractor shall provide additional partial site surveys at existing Information Technology Centers (ITCs) and RDCs) to capture newly added or replaced devices not identified or available on the initial survey. The Contractor shall perform all PWS requirements and deliverables in sections 5.1, 5.2 and 5.3 with the exception of 5.1.3. Optional tasks under 5.5 may be exercised individually, up to two times, throughout the entire period of performance.

5.5.1 AITC, 1615 Woodward Street, Austin, TX 78772

5.5.2 HITC, 5000 South 5th Avenue, Building 215, Hines, IL 60141

5.5.3 PITC, 5000 Wissahickon Avenue, Philadelphia, PA 19144

5.5…