Performance Work Statement - WIFI Patients_V7.pdf

PERFORMANCE WORK STATEMENT (PWS)

DEPARTMENT OF VETERANS AFFAIRS

Office of Information & Technology VIS 17, Doris Miller VA, Waco

Patient WIFI Maintenance and Support – Base Plus 3-year extension.

Date: 8/4/2025

VA-25-00042596

PWS Version Number: 7.0

Contents

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 TECHNICAL KICKOFF MEETING

5.1.3 REPORTING REQUIREMENTS

5.1.4 AS-BUILT DRAWINGS

5.2 HARDWARE AND SOFTWARE REFRESH - CAMPUS

5.3 NEW SERVICES AT Waco BLDG. 202 Canteen

5.3.1 INSTALLATION AND SERVICE

5.4 Hardware replacement

5.5 WIFI SYSTEM SERVICE REQUIREMENTS (BASE/FOLLOW ON

CONTRACT )

5.5.1 SOFTWARE AND LICENSING REQUIREMENTS (BASE/FOLLOW ON

CONTRACT)

5.5.2 WEB CONTENT FILTERING (BASE/FOLLOW ON CONTRACT)

5.5.3 GUEST WIFI LANDING PAGE

5.6 VGIA OPERATION

5.7 TECHNICAL SUPPORT

5.8 MAINTENANCE

5.9 OPTION Periods one through four

5.10 OPTIONAL TASK ONE

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) 21

6.1.3 INTERNET PROTOCOL VERSION 6 (IPV6)

6.1.4 TRUSTED INTERNET CONNECTION (TIC)

6.1.5 STANDARD COMPUTER CONFIGURATION

6.1.6 VETERAN FOCUSED INTEGRATION PROCESS (VIP) AND PRODUCT

LINE MANAGEMENT (PLM)

6.1.7 PROCESS ASSET LIBRARY (PAL)

6.1.8 AUTHORITATIVE DATA SOURCES

6.1.9 SOCIAL SECURITY NUMBER (SSN) REDUCTION

6.1.10 SOFTWARE AND LICENSING REQUIREMENTS

6.2 SECURITY AND PRIVACY REQUIREMENTS

6.2.1 POSITION/TASK RISK DESIGNATION LEVEL(S)

6.2.2 CONTRACTOR PERSONNEL SECURITY REQUIREMENTS

6.3 METHOD AND DISTRIBUTION OF DELIVERABLES

6.4 PERFORMANCE METRICS

6.5 FACILITY/RESOURCE PROVISIONS

6.6 SHIPMENT OF HARDWARE OR EQUIPMENT

ADDENDUM A – ADDITIONAL VA REQUIREMENTS, CONSOLIDATED

ADDENDUM B – VA INFORMATION AND INFORMATION SYSTEM

SECURITY/PRIVACY LANGUAGE................................. Error! Bookmark not defined.

1.0 BACKGROUND

The Department of Veterans Affairs (VA), Office of Information & Technology (OIT), VIS17, Doris Miller, VA Waco and Olin E. Teague, VA Temple 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.

Waco VA,Temple VA and Cedar Park OPC campuses are in need of a contractor that can provide materials, installation and long-term maintenance service to the existing patient WIFI system at each campus.

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,

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 https://www.va.gov/vapubs/index.cfm https://www.va.gov/vapubs/index.cfm http://www.va.gov/vapubs http://www.va.gov/vapubs

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,

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,

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

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

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 https://www.va.gov/process/ https://www.va.gov/process/maps.asp https://www.va.gov/process/artifacts.asp https://www.va.gov/trm/TRMHomePage.aspx

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 https://arch.idmanagement.gov/#what-is-the-ficam-architecture https://arch.idmanagement.gov/#what-is-the-ficam-architecture https://www.voa.va.gov/documentlistpublic.aspx?NodeID=514 https://www.voa.va.gov/documentlistpublic.aspx?NodeID=514 https://www.voa.va.gov/DocumentView.aspx?DocumentID=4896 https://www.cisa.gov/publication/tic-30-core-guidance-documents

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, https://www.voa.va.gov/DocumentListPublic.aspx?NodeId=28 https://www.voa.va.gov/DocumentView.aspx?DocumentID=4371 https://www.voa.va.gov/DocumentListPublic.aspx?NodeId=28 https://www.voa.va.gov/DocumentView.aspx?DocumentID=4946

3.0 SCOPE OF WORK

The Contractor shall maintain and sustain the existing WIFI service network and infrastructure (hardware and components) in accordance with the site specifications for Waco, Temple, and Cedar Park OPC. This includes product licensing, maintenance, support, programming, testing, and installation of new and existing patient WIFI to include Building 202 Canteen in Waco, Temple VAMC and Cedar Park OPC.

The contractor shall provide both on site and remote support and repair to current existing hardware, software, and firewalls throughout the entire contract period for Waco, Temple, and Cedar Park VA facilities. The Contractor shall monitor and maintain the guest WIFI network and tune network performance to meet the requirements of this PWS. The contractor shall respond to On-Site and remote to repairs/work (Critical and/or Normal) in accordance with established service level standards noted in subsequent sections.

The Contractor shall complete a hardware and software refresh of the aged guest WIFI components at all the currently serviced areas Waco, Temple, Cedar Park.

The contractor shall provide 20 additional licenses via an Optional Task, if exercised.

4.0 PERFORMANCE DETAILS

4.1 PERFORMANCE PERIOD

The PoP shall be 1 year from Notice to Proceed (NTP). After successful completion of the base year contract the contractor may be engaged for additional years of service maintenance not to exceed three additional years.

The installation work required during the base year shall occur at the Waco VA canteen facility and shall not take place on Federal holidays or weekends unless directed by the Contracting Officer (CO). As this contract requires on call and emergency service related to WIFI outages this work restriction may be waved as required to maintain integrity of service.

There are eleven (11) 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 Juneteenth June 19 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 primarily performed at the Contractors facility/remote locations based upon concurrence and approval from the VA Contracting Officer's Representative. All on-site work shall be performed at the following locations:

Name Address City State Zip

Doris Miller VA Campus 4800 Memorial Drive Waco Tx 76711

Olin E. Teague Campus 1901 Veterans Memorial Drive Temple Tx 76504

Cedar Park Outpatient Clinic 1401 Medical Parkway Building C Suites 200/400 Cedar Park Tx 78613

Offsite Tasks such as network monitoring, trouble shooting, and software upgrades under this PWS shall be performed at Contractor facilities. The Contractor shall identify the Contractor’s place of performance in their proposal submission.

4.3 TRAVEL

Travel shall be in accordance with the Federal Travel Regulations (FTR) and requires advanced concurrence by the COR. Contractor travel within the local commuting area will not be reimbursed.

Travel requires advanced concurrence by the COR. Contractor travel will not be reimbursed.

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 detailing each site for the lifecycle of the project. 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 or price schedule 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 TECHNICAL KICKOFF MEETING

A technical kickoff meeting shall be held within 10 days after TO award. The Contractor shall coordinate the date, time, and location (can be virtual) with the Contracting Officer (CO), as the Post-Award Conference Chairperson, the VA PM, as the Co-Chairperson, the Contract Specialist (CS), and the COR. The Contractor shall provide a draft agenda to the CO and VA PM at least five (5) calendar days prior to the meeting. Upon Government approval of the final agenda, the Contractor shall distribute to all meeting attendees. During the kickoff-meeting, the Contractor shall present, for review and approval by the Government, 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 and the following statement “As the Post-Award Conference Chairperson, I have reviewed the entirety of this presentation and assert that it is an accurate representation and summary of the discussions held during the Technical Kickoff Meeting for the Guest WIFI Services – Waco/Temple/Cedar Park VAMC.” The Contractor shall submit the final updated presentation to the CO for review and signature within three (3) calendar days after the meeting. The Contractor shall also work with the CS, the Government’s designated note taker, to prepare and distribute the meeting minutes of the kickoff meeting to the CO, COR and all attendees within three (3) 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.

5.1.3 REPORTING REQUIREMENTS

The Contractor shall provide the COR with 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.

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 weekly progress report also contains a weekly incident section to detail the WIFI network, and any issues (to include oversight and monitoring of the installed wireless network(s) and trouble tickets received and resolution) encountered during the reporting period or adverse events, including unauthorized access attempts, security vulnerabilities, and performance problems.

Deliverables:

A. Weekly Progress Reports

5.1.4 AS-BUILT DRAWINGS

The Contractor shall provide detailed network architectural drawings for the current state of the Waco, Temple and Cedar Park locations after hardware/software refresh. At a minimum, the drawings shall include:

• Manufacturer model identifiers

• Serial numbers

• MAC addresses

• VA-assigned Equipment Inventory List (EE) numbers

• Location of device including building and room number

• Drawings are to be provided in a concise digital package:

• Digital drawings shall be provided in the latest version of CAD & PDF.

• At minimum drawing shall be 24x36 in size and drawn to architectural scale.

• Reporting documents shall be delivered in both Microsoft Word and PDF format.

In the event of any hardware or software refresh, as a result of natural attrition and/or refresh, the Contractor shall update these drawings/documents on an ad-hoc basis.

A. Waco/Temple/Cedar Park as built drawing B. Refreshed Drawings/documents

5.2 HARDWARE AND SOFTWARE REFRESH - CAMPUS

Refresh efforts shall be the second priority of the Base Year Contractor. Upon completion of the tasks noted Performance Work Statement 5.2, the Contractor shall provide a “Hardware Evaluation Report” with recommendations for VA Consideration.

Upon approval of the VA Contracting Officers Representative, the Contractor shall secure, deliver, install, and configure all infrastructure recommended for replacement. A detailed transition strategy and implementation plan shall be thoroughly discussed in detail at the Kickoff Meeting, and the finalized plan provided to the COR within 14 days after Kickoff.

All hardware shall be new and not used or refurbished in any way.

All infrastructure requirements per Section 5.0 “Specific Tasks and Deliverables” shall have a transition plan to seamlessly switch over to new ISP services within 30 days of award.

A. Hardware Evaluation Report

5.3 NEW SERVICES AT WACO BLDG. 202 CANTEEN

The Contractor shall stand up under the Base year contract a new VGIA services at the Waco Bldg. 202 Canteen locations outlined in Section 4.1, Place of Performance, within the first quarter of the base period. Security and logging requirements shall mirror the capabilities of the main campus. It is preferred that all logging activities to be routed through the main campus logging server.

The Contractor shall first gain the COR’s approval for either of two hardware mounting options per CBOC:

• Leverage existing rack space

• Utilize a contractor-provided 4 rack mount unit (RMU) 19” wall mounted rack box approximately 8”H x 20”W x 22”D

The Contractor shall use pink CAT6 cabling to distinguish the VGIA network from the VA OI&T network. Clearly label all hardware components as “VGIA”.

The Contractor shall provide the COR with an Excel spreadsheet of all hardware components listing the following details prior to installation:

• Manufacturer

• Nomenclature (example: Web Filter)

• Model Number

• Serial Number

• Date of Installation

• Location (example: Gladstone CBOC)

• Room Number

• Cost

All Contractor provided hardware shall be new and not used or refurbished in any way.

A. Excel spreadsheet of all hardware components: CBOC

5.3.1 INSTALLATION AND SERVICE

The contractor will be responsible for the following:

1. Install new WIFI service to Waco building 202 Canteen area. The Contractor will provide the necessary AP with licenses:

• Mount AP on ceiling of Bldg. 202 Canteen.

• Install cabling to local IT closet.

• Run fiber back to head end in building 4.

5.4 HARDWARE REPLACEMENT

The Contractor shall provide and replace failed hardware components to restore WIFI services and meet uptime requirements

5.5 WIFI SYSTEM SERVICE REQUIREMENTS (BASE/FOLLOW ON CONTRACT)

The contractor shall furnish all personnel, equipment, tools, materials, transportation, management supervision, and other items and services necessary to perform all WIFI installation tasks and functions. The contractor must perform to the standards identified in the performance work statement.

The contractor shall provide ongoing support to the existing solution which includes, but is not limited to:

1. Purchase/renewal of annual software licenses for (3) firewall appliances/hardware.

2. Provide annual licensing and support renewal for FortiGate 60E for (3) locations.

3. Provide annual support and licensing for Ruckus equipment for 167 access points, 40ISX switches, SCI, and SmartZones 100 at Waco/Temple. This number may increase based on exercise of any optional task during the life of this effort.

The contractor shall be responsible for connecting existing and new WIFI components to the existing 1G internet service provided by others. The Contractor shall not be responsible for providing the underlying internet connectivity from the source. In the event of an outage, the Contractor shall notify the site Point of Contact.

The Contractor shall also perform the following services as part of this effort:

1. The Cable Distribution System will be maintained to satisfy the digital data and voice requirements of the Department of Veterans Affairs, Veteran Integrated Service Network (VISN) 10.

2. AP (Wireless Access Point) and Cable Installation: Install at minimum Cat 6A cabling and APs in accordance with work orders, location drawings, and specifications.

3. Horizontal cabling shall be at minimum Category 6A (Cat6A) American National Standards Institute (ANSI) Telecommunications Industry Association (TIA) - 1179 Healthcare Facility Telecommunications Infrastructure.

4. Installation shall be compliant with the Building Industry Consulting Service International (BICSI) standards ANSI/NECA(National Educational Consultancy Association)/BICSI 568, Standard for Installing Commercial Building Telecommunications Cabling and ANSI/TIA -1179-A Healthcare Facility Telecommunications Infrastructure for new installations.

5. New cable installations additionally shall be compliant with TIA 568.2-D, TIA Technical Service Bulletin (TSB)-184-A, and National Fire Protection Association (NFPA) -70 Section 725.144 to prevent Power over Ethernet (PoE) heat accumulation. Provide certification reports to the COR.

6. Alternatively, new Unshielded Twisted Pair (UTP) cabling shall carry a UL listed Limited Power (LP) rating.

7. Cat6A cable shall be terminated to identified RJ-45 patch panel in IT closet and CAT6A RJ-45 jack at wall plate and labeled at both ends.

8. Use a cable analyzer to determine cable length (max cable length 90M/295 linear feet) and certify that cable meets or exceeds TIA-EIA-568-C.2.

9. Cables shall be installed in continuous lengths from origin to destination, no splices with a one-foot service loop.

10. Use existing raceways as much as possible. Cable shall be installed in accordance with manufacturer’s recommendations and best industry practices.

Existing raceways shall not be filled greater than the National Electric Code (NEC) maximum fill for the raceway type. Cables shall be supported with J hooks or cable bags every four (4) to five (5) feet whenever there is an absence of a cable tray. Any areas requiring the use of fire sealing material will conform to the ANSI/NFPA-70 FIRE SEALING / SAFETY standard. The VA, upon written request, will authorize the contractor to provide a quote to increase number or size of pathways only in the event the total pathways provided to any given area are inadequate.

11. Label patch panels in accordance with specifications and VAMC standard. Patch panel labels shall include outlet number, jack number. All label printing shall be machine generated

12. Confirm locations, including installation height, with COR.

13. Patch and finish disturbed surfaces to match existing.

14. All material, installed by the contractor, shall be new, tested, and certified.

15. Attach all AP units to ceiling grid or other prior approved location using manufacturer recommended hardware.

16. Contractor shall be proficient of the following:

• Ruckus Brand Server or compatible licenses or components, switches, and

AP’s.

• Forti Gate or compatible Firewall.

• Contractor shall notify COR and IT subject matter expert of any periodic manufacture updates prior to installation throughout the life of the contract.

5.5.1 SOFTWARE AND LICENSING REQUIREMENTS

The Contractor shall be responsible for the provision of all software licenses and any associated licensing maintenance required for any development, delivery, integration, operation, and/or maintenance associated with its proposed application(s), software products, software solution, and/or system including, but not limited to, any and all application(s), software and/or software products that comprise, are a part of, or integrate with the Contractor’s proposed application(s), software products, software solution, and/or system for the life of any resulting contract.

WIFI

5.5.2 WEB CONTENT FILTERING

The Contractor shall implement and maintain Web content filtering so that VA can deny guest WIFI to unacceptable and inappropriate Internet content, and to best maintain performance of the network. Web content filtering shall include VA administrator-configurable options and a capability to review and modify filtering. The Contractor shall update the web content filter at the request of patient and guest users and/or VA personnel, only after approval by the VA COR. These web content filtering database updates shall be based on industry standards. The Contractor shall vet any website access requests to determine the level of risk to allow users access to the site and advise the COR accordingly.

VA is responsible for providing a filter list to the Contractor that defines websites to be blocked. The Contractor shall update the filtering service upon receipt of the new filter list. In the event a web page is blocked, the Web Content Filtering will allow notification to the user that the web page was blocked due to VA customer web policy. This service also provides mitigation for common internet malware. The Contractor shall provide a Web Content Filtering Report detailing the findings and any service performed. All efforts associated with this activity shall be reported to the COR in the Quarterly Utilization Report.

5.5.3 GUEST WIFI LANDING PAGE

The Contractor shall provide an introduction page with usage agreements for acknowledgement at the time of login with information on the program, rules and restrictions and usage agreements. If no agreement acknowledgement is received from the user, access shall be denied. [Users of guest WIFI must acknowledge that they are aware of the risk of using a public network]. The Contractor shall provide a homepage at login displaying information security warning, public access information, VA non-liability disclaimer. VA will provide, to the Contractor, the information for the homepage that will be displayed upon login.

The Contractor shall design and implement a landing page for guest login (also known as a welcome, home, introduction page) that includes usage agreements and terms and conditions for acknowledgement at the time of login:

1. Rules and restrictions

2. Information security warning

3. Public network access risk information

4. VA non-liability disclaimer

The landing page operation shall require guest acceptance of guest WIFI terms and conditions before allowing guest internet access. VA will provide the Contractor all content and information to be displayed, including legal language, when a guest accesses the landing page. The Contractor shall provide other recommendations for landing page content. Final landing page content shall be determined by VA consideration of recommendations provided by the Contractor.

The Contractor shall update the guest WIFI Landing Page Software Code to keep the code current with VA security standards, which are outlined in “Attachment D Security Information for guest WIFI Access”. The Contractor shall update the guest WIFI Landing Page to reflect any VA-approved or VA-authorized changes to it.

The following is an example of a landing page for the Doris Miller VA Campus VAMC. A similar page will be required for the Olin E. Teague facility:

“Welcome to the Doris Miller VA Campus VAMC Guest Wireless Network A Service VENDORCo”

To use this service, you agree to the following:

1 VENDORCo monitors the use of this system for purposes related to security management, system maintenance and system troubleshooting.

2 During monitoring, information may be examined, recorded, copied, and used for authorized purposes. If the monitoring reveals possible evidence of criminal activity, VENDORCo can provide records to law enforcement.

3 There is NO EXPECTATION OF PRIVACY in the use of the VA Guest Network as all information, including personal information, placed or sent over this network may be monitored.

4 You agree to abide by the VA Guest Network Acceptable Use Policy (Listed below).

5 Violation of the VA Guest Network Acceptable Use Policy may result in revocation of access, civil or criminal proceedings.

6 Access to this network may be disabled at any time. Your bandwidth may be limited by based on your usage and the usage of others.

The VA is not responsible for issues regarding access. Technical issues should be directed to VENDER Co help desk at 1-800-999-0000.

VA Guest Network Acceptable Use Policy

1. Attempting to access or accessing another's account, private files, or e-mail without the owner's permission; or misrepresenting oneself as another individual in electronic communication is prohibited.

2. Using the VA Guest Network to engage in conduct that interferes with others' use of guest network and/or the activities of other users is prohibited.

3. Using the VA Guest Network for commercial or profit-making purposes is prohibited.

Prohibited activity includes soliciting alms or contributions, vending, or debt collecting.

4. Using the VA Guest Network for illegal activities is prohibited. Criminal and illegal use includes but is not limited to obscenity, child pornography, threats, harassment, copyright infringement, defamation, theft, and unauthorized access.

5. Peer-to-Peer software such as KaZaa, Bearshare, or Gnutella that can be used to share files such as music, movies, or software in violation of copyright laws is prohibited on all computers connected to the VA network (including the Guest Network). The Medical Center does not support the download or distribution of these copyrighted files and any violation of this policy will result in revocation of guest network access.

6. Use of the VA Guest Network to access gambling sites is prohibited.

7. Use of the VA Guest Network which results in a disturbance to the VA facility or impedes or disrupts the performance of official duties by government employees is prohibited.

To agree to the above and gain access to the Internet please click the ACCEPT button below.”

5.6 VGIA OPERATION

The Contractor shall provide service availability with an expected 99.8% of VGIA uptime for the areas listed in PWS Scope 3.0.

The Contractor shall be responsible for the operation of the solution ensuring that the VGIA always meets all requirements of Section 5.6.

The Contractor shall monitor the network to verify the wireless physical requirements such as spectrum support and user density (bandwidth), antenna diversity (signal quality), and availability requirements within coverage areas are within limits specified in the solution requirements of 5.6.

The Contractor shall perform ongoing monitoring of the Radio Frequency (RF) environment, not only for potential IEEE 802.11 wireless interference, but also for all interference sources in the Industrial, Scientific, and Medical (ISM bands). Monitoring shall include Bluetooth, Zig Bee 802.15,4 and other device radio frequencies.

The Contractor shall provide and operate VGIA with no interference with other VA wireless networks. If there is conflict for wireless spectrum or physical space, the needs of VA official-use networks shall take precedence over VGIA access.

The Contractor shall monitor the typical usage of Wireless Application Protocol (WAPs).

Where high usage areas are noted, the Contractor shall re-evaluate and upgrade the bandwidth. If the link/usage averages in excess of 85% of current throughput capacity per month, the Contractor shall re-evaluate and provide additional bandwidth. The Contractor shall report these evaluations in the Quarterly Utilization Report.

The Contractor shall provide VA a VGIA Quarterly Utilization Report that summarizes for each building network traffic levels, security issues, and peak simultaneous devices connections for the previous month. The Contractor shall report in the Quarterly Utilization Report access point utilization evaluations, along with incidences of interference resulting in degraded performance, and recommendations for any areas that require adjusted bandwidth. The Contractor shall include any observed security Issues in the Quarterly Utilization Report. Any actions performed on this subtask shall be reported in the Weekly Progress Report as noted in Section 5.1.3.

Consecutive months of uptime that does not meet these metrics shall require written notification to the VA Contracting Officer, which may result in further penalties and action as appropriate.

A. VGIA Quarterly Utilization Report

5.7 TECHNICAL SUPPORT

The Contractor shall provide technical support for the guest WIFI system on topics related to its operation and configuration. The Contractor shall provide a 24x7x365 technical support through a toll-free contact number for technical support of all VAMC.

The Contractor shall provide a 3-hour response time for trouble tickets entered through the technical support call center.

The Contractor shall recommend to the COR all firmware/software upgrades developed and offered by guest WIFI device manufacturers within 60 days of manufacturer release and perform installation of upgrades upon COR approval.

The Contractor shall provide technical support for all guest WIFI software including any manufacturer-sponsored modification or revisions. The support provided shall consist of correction of errors, provision of manufacturer-sponsored modifications, improvements, and revisions. The Contractor shall furnish full documentation of all manufacture sponsored changes and/or modifications to the software. The Contractor shall furnish the most current version of manufacturer-supplied user manuals, when applicable. All efforts associated with this activity shall be reported to the COR in the Weekly/Semi- Weekly/Quarterly Progress Report.

Deliverables:

A. Manufacturer documentations – sponsored software changes/modification

5.8 MAINTENANCE

The Contractor shall identify issues, troubleshoot anomalies, and provide maintenance for the guest WIFI system and all operational infrastructure. The Contractor shall replace any failed Wireless application protocols (WAP’s) with new WIFI – 5 WAPs that at a minimum exceed the following:

1. Multiple input Multiple output (MIMO) technology with a minimum of 3 spatial streams

2. Data rates up to 3.46 Gbps operating in the 5GHz range.

The Contractor shall identify issues, troubleshoot anomalies, and provide maintenance for the GUEST WIFI. The Contractor shall provide a 24x7x365 toll-free contact number for maintenance.

After receipt of a maintenance call/trouble ticket, the Contractor shall respond within three (3) hours. If issue resolution requires onsite support, the Contractor shall immediately collaborate with the COR for onsite actions within 24 hours. Next business day response and corrective action applies if maintenance call/trouble ticket occurs over the weekend. Once repairs are initiated, work shall continue until completed. The Contractor shall troubleshoot the guest WIFI hardware and software to determine the best method of repair. The Contractor shall notify the COR of identified defect/failure and continue corrective measures until the problem is resolved.

The Contractor shall provide, configure, install, and test replacement equipment when either failed or scheduled refresh hardware needs to be replaced. Functionality shall be verified by the COR prior to Contractor departure.

Routine scheduled maintenance shall be scheduled during off peak hours after 9:00pm Central in patient care areas unless otherwise approved by the COR.

Maintenance can be scheduled anytime in non-patient areas. Holidays and weekends work must be scheduled with COR. The Contractor shall notify VA of routine maintenance seven (7) days prior to the event and shall indicate whether a scheduled event poses a risk of the service to be offline, or which may degrade system performance. The Contractor shall provide and install manufacturer software/firmware upgrades within 60 days of manufacturer release. The Contractor shall notify the COR of all upgrades and receive approval prior to installation.

The Contractor shall update the guest WIFI Devices Inventory Document annually with any changes to the following information for all equipment, devices, and software for the guest WIFI Solution in a guest WIFI Device Inventory Document and update the Device Inventory Document:

1. Manufacturer model identifiers

2. Serial numbers

3. MAC addresses

4. VA-assigned Equipment Inventory List (EIL) numbers

5. Location of device including building and room number

Any actions performed on this subtask shall be reported in the Weekly Progress Report, including any identified security issues, the number of service calls and the resolution of the calls, the amount of time taken to resolve the calls, user complaints and the Contractor action taken on those user complaints. Any actions performed on this task shall be reported to the COR.

The Contractor shall adhere to the standards outlined by the National Fire Protection Association (NFPA-101 Life Safety Code).

5.9 OPTION PERIODS ONE THROUGH FOUR

The Contractor shall maintain the system as described in PWS Sections 5.1.4, 5.5 and its underlying subsections, 5.6-5.8.

5.10 OPTIONAL TASK ONE

The Contractor shall furnish an additional quantity of up to 20 licenses. This Optional Task may be exercised multiple times up to the Not to Exceed quantity for the life of the contract.

A. Licenses

6.0 GENERAL REQUIREMENTS

6.1 ENTERPRISE AND IT FRAMEWORK

6.1.1 VA TECHNICAL REFERENCE MODEL

The Contractor shall support the VA enterprise management framework. In association with the framework, the Contractor shall comply with OIT Technical Reference Model (VA TRM). The VA TRM is one component within the overall Enterprise Architecture (EA) that establishes a common vocabulary and structure for describing the information technology used to develop, operate, and maintain enterprise applications. Moreover, the VA TRM, which includes the Standards Profile and Product List, serves as a technology roadmap and tool for supporting OIT. Architecture & Engineering Services (AES) has overall responsibility for the VA TRM.

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

The Contractor shall ensure Commercial Off-The-Shelf (COTS) product(s), software configuration and customization, and/or new software are Personal Identity Verification (PIV) card-enabled by accepting HSPD-12 PIV credentials using VA Enterprise Technical Architecture (ETA), https://www.ea.oit.va.gov/EAOIT/VA_EA/Enterprise_Technical_Architecture.asp, and VA Identity and Access Management (IAM) approved enterprise design and integration patterns, https://www.oit.va.gov/library/recurring/edp/index.cfm. The Contractor shall ensure all Contractor delivered applications and systems comply with the VA Identity, Credential, and Access Management policies and guidelines set forth in VA Handbook 6510 VA Identity and Access Management, VA Handbook 0735 Homeland Security Presidential Directive 12 (HSPD-12) Program, and align with the Federal Identity, Credential, and Access Management Roadmap and Implementation Guidance v2.0.

The Contractor shall ensure all Contractor delivered applications and systems provide user authentication services compliant with the National Institute of Standards and https://www.ea.oit.va.gov/EAOIT/VA_EA/Enterprise_Technical_Architecture.asp https://www.oit.va.gov/library/recurring/edp/index.cfm

Technology (NIST) Special Publication (SP) 800-63-3, VA Handbook 6500 Appendix F, “VA System Security Controls”, and VA IAM enterprise requirements for direct, assertion based authentication, and/or trust based authentication, as determined by the design and integration patterns. Direct authentication at a minimum must include Public Key Infrastructure (PKI) based authentication supportive of PIV card and/or Common Access Card (CAC), as determined by the business need.

The Contractor shall ensure all Contractor delivered applications and systems conform to the specific Identity and Access Management PIV requirements set forth in the Office of Management and Budget (OMB) Memoranda M-05-24, M-19-17, and NIST Federal Information Processing Standard (FIPS) 201-2. OMB Memoranda M-05-24 and M-19- 17 can be found at:

https://www.whitehouse.gov/sites/whitehouse.gov/files/omb/memoranda/2005/m05- 24.pdf, and https://www.whitehouse.gov/wp-content/uploads/2019/05/M-19-17.pdf respectively. Contractor delivered applications and systems shall be on the FIPS 201-2 Approved Product List (APL). If the Contractor delivered application and system is not on the APL, the Contractor shall be responsible for taking the application and system through the FIPS 201 Evaluation Program.

The Contractor shall ensure all Contractor delivered applications and systems support:

1. Automated provisioning and are able to use enterprise provisioning service.

2. Interfacing with VA’s Master Person Index (MPI) to provision identity attributes, if the solution relies on VA user identities. MPI is the authoritative source for VA user identity data.

3. The VA defined unique identity (Secure Identifier [SEC ID] / Integrated Control Number [ICN]).

4. Multiple authenticators for a given identity and authenticators at every Authenticator Assurance Level (AAL) appropriate for the solution.

5. Identity proofing for each Identity Assurance Level (IAL) appropriate for the solution.

6. Federation for each Federation Assurance Level (FAL) appropriate for the solution, if applicable.

7. Two-factor authentication (2FA) through an applicable design pattern as outlined in VA Enterprise Design Patterns.

8. A Security Assertion Markup Language (SAML) implementation if the solution relies on assertion-based authentication. Additional assertion implementations, besides the required SAML assertion, may be provided as long as they are compliant with NIST SP 800-63-3 guidelines.

9. Authentication/account binding based on trusted Hypertext Transfer Protocol (HTTP) headers if the solution relies on Trust based authentication.

10. Role Based Access Control.

11. Auditing and reporting capabilities.

12. Compliance with VIEWS 00155984, PIV Logical Access Policy Clarification https://www.voa.va.gov/DocumentView.aspx?DocumentID=4896.

https://www.whitehouse.gov/sites/whitehouse.gov/files/omb/memoranda/2005/m05-24.pdf https://www.whitehouse.gov/sites/whitehouse.gov/files/omb/memoranda/2005/m05-24.pdf https://www.whitehouse.gov/wp-content/uploads/2019/05/M-19-17.pdf https://www.voa.va.gov/DocumentView.aspx?DocumentID=4896

The required Assurance Levels for this specific effort are Identity Assurance Level 3, Authenticator Assurance Level 3, and Federation Assurance Level 3.

6.1.3 INTERNET PROTOCOL VERSION 6 (IPV6)

The Contractor solution shall support Internet Protocol Version 6 (IPv6) based upon the memo issued by the Office of Management and Budget (OMB) on November 19, 2020 (https://www.whitehouse.gov/wp-content/uploads/2020/11/M-21-07.pdf). IPv6 technology, in accordance with the USGv6 Program (https://www.nist.gov/programs-projects/usgv6-program/usgv6-revision-1), NIST Special Publication (SP) 500-267B Revision 1 “USGv6 Profile” (https://doi.org/10.6028/NIST.SP.500-267Br1), and NIST SP 800-119 “Guidelines for the Secure Deployment of IPv6” (https://doi.org/10.6028/NIST.SP.800-119), compliance shall be included in all IT infrastructures, application designs, application development, operational systems and sub-systems, and their integration. In addition to the above requirements, all devices shall support native IPv6 and dual stack (IPv6 / IPv4) connectivity without additional memory or other resources being provided by the Government, so that they can function in a mixed environment. All public/external facing servers and services (e.g.

web, email, DNS, ISP services, etc.) shall support native IPv6 and dual stack (IPv6 / IPv4) users and all internal infrastructure and applications shall communicate using native IPv6 and dual stack (IPv6 / IPv4) operations.

6.1.4 TRUSTED INTERNET CONNECTION (TIC)

The Contractor solution shall meet the requirements outlined in Office of Management and Budget Memorandum M-19-26, “Update to the Trusted Internet Connections (TIC) Initiative“ (https://www.whitehouse.gov/wp-content/uploads/2019/09/M-19-26.pdf), VA Directive 6513 “Secure External Connections”, and shall comply with the TIC 3.0 Core Guidance Documents, including all Volumes and TIC Use Cases, found at the Cybersecurity & Infrastructure Security Agency (CISA) (https://www.cisa.gov/publication/tic-30-core-guidance-documents). Any deviations must be approved by the VA TIC 3.0 Working Group at vaoisesatic30team@va.gov.

6.1.5 STANDARD COMPUTER CONFIGURATION

The Contractor IT end user solution that is developed for use on standard VA computers shall be compatible with and be supported on the standard VA operating system, currently Windows 10 (64bit), Edge (Chromium based), and 365 Apps for enterprise. Applications delivered to VA and intended to be deployed to Windows 10 workstations shall be delivered as a signed .msi package with switches for silent and unattended installation and updates shall be delivered in signed .msp file formats for easy deployment using Microsoft Endpoint Configuration Manager (CM) VA’s current desktop application deployment tool. Signing of the software code shall be through a vendor provided certificate that is trusted by VA using a code signing authority such as https://www.whitehouse.gov/wp-content/uploads/2020/11/M-21-07.pdf file://///R04.med.va.gov/V03/EAS/Users/vhaeasWymbsk/TEMPLATES--NEW%20TAC%20PROCESS/PWS%20TEMPLATE%20(DO%20NOT%20TOUCH)%20-%20In%20Process%20Revisions/DO%20NOT%20TOUCH%20(next%20version/IPv6/(https:/www.nist.gov/programs-projects/usgv6-program/usgv6-revision-1 file://///R04.med.va.gov/V03/EAS/Users/vhaeasWymbsk/TEMPLATES--NEW%20TAC%20PROCESS/PWS%20TEMPLATE%20(DO%20NOT%20TOUCH)%20-%20In%20Process%20Revisions/DO%20NOT%20TOUCH%20(next%20version/IPv6/(https:/www.nist.gov/programs-projects/usgv6-program/usgv6-revision-1 https://doi.org/10.6028/NIST.SP.500-267Br1 https://doi.org/10.6028/NIST.SP.800-119…