Attach. B.6 SOW Secure Wireless.pdf

B.6 STATEMENT OF WORK (RFQ)

Scope of Work Secure Wireless for Red Lake Service Unit

1. STATEMENT OF WORK

The contractor will provide all of the labor for the installation of the Secure Wireless equipment that we have on site Install pair of 9800-L-F wireless controllers � Configure wireless controllers (green field) and existing LAN switches as needed � Install (4) 9130AXI-B wireless Access Points (APs) − IT Area − Inpatient Library − Admin Conf Rm − Lower Conf Rm Deliverables Activities related to scheduled tasks will support Deliverables necessary for a successful project.

� External Kickoff Deck � High-Level Design (HLD) � As-Built Documentation � Acceptance Testing Procedures (ATP) � Low-Level Design (LLD) � Post-install pictures of installed equipment On-site work will be accompanied by IT personal

2. Technical requirements

Engage Phase Project kickoff meeting to collect business requirements, solution expectations, and key success criteria − Review and discuss the BOM to validate all necessary components are available − Review and discuss the wireless survey report to validate RF configuration settings − Review and discuss the customer LAN infrastructure and network services − Review and discuss the traffic flows required to support the wireless network with the customer

Status meetings during the project

1.6.2 Plan Phase

Perform technical requirements gathering with the customer to document the solution − Discuss any potential risks with integrating the new wireless network

Develop a high‐level design (HLD) based on the outcome of the kickoff and requirements gathering meetings

1.6.3 Design Phase

Develop the low‐level design (LLD) based on the information collected from the customer during requirements gathering − IHS Design will consist of 2 x 9800‐L IOS‐XE WLC's to be installed HA‐SSO − Design WLAN for Single SSID for Internal Employees

Integration with Microsoft AD for authentication

− General configuration settings including hostname, SNMP, and best practice configuration − WLC L2/L3 information including VLAN and SVI − Interface connectivity and configuration including link aggregation settings − Wireless management interface and trustpoint settings − Mobility group member information − Multicast and mDNS settings − Stateful switchover (SSO) for high availability − AAA information including RADIUS and/or TACACS − ACL information AAA information including RADIUS and/or TACACS − Profile and tag information

Develop the acceptance test plan (ATP) document based on information collected from the customer during requirements gathering

Implement Phase Physical Installation of 2 x 9800‐L IOS XE WLCs and 4 x 9130AXI‐B access points − Rack, power, and cable each WLC to the network as documented in the LLD − Verify the configuration of each switch port designated for WLC connectivity − Verify the connectivity status of each interface after the WLC has completed the boot process − Install Access Point in locations consistent with Wireless Design Field technician will document the following prior to mounting − Serial Numbers − MAC Addresses − Data Cable ID − Location Description − Switch Port Field technician will mount AP in customer designated location Field technician will verify connectivity via activity light on AP Field technician will work with remote Engineer to ensure AP is being managed by WLC and performing as it should Field technician remove all scrap and trash material left in area and discard per Customer direction Field technician will take post‐installation photo of installed hardware as part of required deliverable from site WLC Global Configuration − Upgrade the code on each controller to the image documented in the

LLD

− Perform the initial setup configuration of each WLC − Configure stateful switchover for high availability − Configure mobility groups − Configure AAA services Define each RADIUS or TACACS+ server as documented in the LLD Define a server group for each protocol as documented in the LLD Configure a method list for each AAA service as documented in the LLD

− Configure Multicast and mDNS on the WLC Configure profiles and tags − Configure WLAN and policy profiles as documented in the LLD − Configure policy tags as documented in the LLD − Configure AP join and flex profiles as documented in the LLD − Configure site tags as documented in the LLD

− Configure 2.4 and 5 GHz RF profiles as documented in the LLD − Configure RF tags as documented in the LLD

Provision 4 APs (4) 9130AXI‐B for Internal Employee SSID − Configure the appropriate name for each

AP

− Apply tags to all APs based on the LLD − Import floor plans and place APs based on their installed location

Execute the Acceptance Test Plan (ATP) − Document the results of each test

Operate Phase Perform day‐one support and knowledge transfer with the customer Develop As‐Built Document

1.6.6 Testing

Utilizing the data obtained in the project initiation meeting, contractor will develop an ATP documentation package. The ATP package will include a document detailing test resource requirements, procedures, and expected results. The test plan document package will be reviewed by Indian Health Service to confirm both parties agree to the test plan criteria and methodologies. After reaching agreement, major changes to the ATP package as a result of a feature, application, or design change will go through a change control process to ensure no changes are implemented without having an agreed upon ATP.

1.6.7 Cutover Procedures

Contractor will formally turn the site over to Indian Health Service for daily operational support after the successful testing of the solution. As‐Built documentation will be provided for each installation as it is turned over, including e.g., design documents, configuration files, and diagrams. The actual As‐Built deliverables and format will be determined during the planning phase.

1.6.8 Documentation

Contractor employs a formal documentation development process, which utilizes a document change management tool to protect and control content production and editing. All documentation will be considered confidential and available for official use only, and with contributing staff unable to share data outside the project’s Information Technology (IT) domain.