lexington center corporation high density wi-fi … · high density wi-fi infrastructure &...

High Density Wi-Fi Infrastructure – RFP Requirements_______________________ RFP Process Overview

LEXINGTON CENTER CORPORATION

HIGH DENSITY WI-FI INFRASTRUCTURE

& UNIFIED COMMUNICATIONS RFP

REQUIREMENTS

LEXINGTON CONVENTION CENTER RUPP ARENA

LEXINGTON OPERA HOUSE

High Density Wi-Fi Infrastructure – RFP Requirements________________________________Introduction

1 | P a g e

1 Introduction

This Request for Proposal (RFP) contains a list of requirements for products and services

associated with Wi-Fi deployment for the Lexington Center Corporation (Customer) and its

facilities. This includes The Lexington Convention Center consisting of exhibit halls, ballrooms,

meeting rooms, prefunction areas, loading docks and common areas. Rupp Arena consisting of

the lower and upper arena seating bowl, 3rd and 4th level concourses, concession stands, dressing

rooms, media/press interview, work and overflow areas, support spaces and the Lexington

Center administrative offices. The Lexington Opera House, located two blocks from Lexington

Center consisting of a 900 seat multi-balcony performing arts theater, back stage areas, dressing

rooms, rehearsal rooms, lobbies, game and pub areas. Triangle Park, an outdoor park adjacent to

the Lexington Center providing a café area, fountains and an area for small performances. Two

parking lots with various entry points and attendant stands. The Shops at Lexington Center, a

multilevel indoor mall area with shopping and a food court. In addition to the Wi-Fi products

and services, the customer is also seeking to replace the current traditional phone system with a

new IP based Unified Communication system. To support the high-density Wi-Fi deployment,

new IP phone system, all current administrative computer systems and peripherals, points-of-

sale, HVAC systems, IP video and any future IP delivery and network systems, a refresh of the

network core and edge switches, firewalls and supporting hardware and software is necessary.

1.1 Purpose This document enumerates the following:

a) Product features, functionalities, and capabilities required in Wi-Fi solutions to enhance

venue’s guest experience, enhance sponsor value and provide high performance wireless

connectivity for corporate and guest use.

b) Service requirements for design & dimensioning, installation & commissioning, optimization

& integration, maintenance & event support, and provisions for future system upgrades.

The purpose of this document is to list the requirements for Wi-Fi, network and IP Unified

Communications equipment providers, distributors, wireless service providers, consultants, and

other applicable third parties, in order to solicit responses and evaluate compliance against each

requirement.

1.2 Scope The scope of this document is limited to the requirements of Wi-Fi products and services,

Unified Communication System and supporting network hardware and software for deployment

at the location.


2 | P a g e

1.3 Background & General Information

The Customer is seeking to deploy a new Wi-Fi network to service high and low-density

capacity requirements at the locations listed above in the introduction. In addition, replacement

of existing phone system with a UCS solution within listed locations.

In view of the above, this RFP is being released to seek a response from interested bidders. The

RFP response should be created specifically to the demands and requirements of the arena,

convention center, theater and support areas.

1.4 Document Organization

This RFP document contains the following sections:

a) Section 1 : Introduction

b) Section 2 : RFP Process Overview

c) Section 3 : Business Terms

d) Section 4 : Statement of Qualifications

e) Section 5 : Product and Services Portfolio

f) Section 6 : Technical Requirements

g) Section 7 : Design Requirements

h) Section 8 : Unified Communication Requirements

i) Section 9 : Optimization and Acceptance Requirements

j) Section 10 : Cost and Pricing

k) Section 11 : RFP Response

1.5 Definitions and Acronyms

1.5.1 Definitions

1. From this point onwards, the authority in charge of this RFP distribution and/or review for

the location will be referred to as the “Customer”.

2. The authority in charge to which the RFP is to be released will be referred to as the “RFP

recipient”. The RFP recipient could be a wireless service provider, Wi-Fi equipment

provider, distributor, or any other third party to whom this RFP shall be released.

3. The word “Venue” used anywhere in this document refers to the locations as listed in section

1 Introduction unless otherwise referred to by its specific location name (e.g. Arena).

4. “Busy Hours of a Game/Event” shall be one and one-half hour before a game/event starts

until one hour after a game/event ends.


3 | P a g e

1.5.2 Acronyms

AP Access Point

BFO Best Final Offer

BOM Bill Of Materials

BW Bandwidth

DL Downlink

EIRP Equivalent Isotropic Radiated Power

FCC Federal Communications Commission

HA High Availability

IDF Intermediate Distribution Frame

KPI Key Performance Indicator

LAN Local Area Network

LPV Large Public Venue

MCS Modulation and Coding Scheme

MDF Main Distribution Frame

MU-MIMO Multi-User Multiple Input Multiple Output

MSLR Minimum Service Level Requirement

MTBF Mean Time Between Failures

Third Party Third Party

Opex Operational Expenditure

POS Point of Sale

QAM Quadrature Amplitude Modulation

RF Radio Frequency

RFP Request for Proposal

RSSI Received Signal Strength Indicator

SINR Signal to Interference and Noise Ratio

SLA Service Level Agreement

SSID Service Set Identification

UCS Unified Communications System

UE User Equipment

UL Uplink

Wi-Fi Wireless Fidelity

WLAN/WWAN Wireless Local Area Network / Wireless Wide Area Network

WPA Wi-Fi Protected Access

WEP Wired Equivalent Privacy


4 | P a g e

2 RFP Process Overview

This section describes the RFP response evaluation and final decision making process.

2.1 RFP Process

The RFP process is envisioned to be completed in four steps shown below.

Figure 2-1: RFP Process

a) Step 1: RFP is released by the Customer to the RFP recipients (8/19/16)

b) Step 2 Walk-Through for all venues between (8/22/16 – 8/31/16)

c) Step 3: RFP responses are submitted by the RFP recipients (9/19/16)

d) Step 4: RFP response evaluation by the Customer (9/19/16 – 10/7/16)

e) Step 5: Interviews may be conducted at Customer’s discretion and BFO opportunity

presented during Step 4 period.

Step 1: RFP Release

Step 2: Walk-Through of Facilities

Step 3: RFP Response Submitted By RFP

Recipients

Step 4 RFP Response Evaluation

Step 5 Interviews/Best & Final Offer

(BFO) Discretionary

Step 6: Final Stage/ Decision


5 | P a g e

f) Step 6: Final stage / decision by the Customer (10/10/16)

This RFP is specific to the location. The design, dimensioning, optimization, and other system

operations requirements will be specific to this location. The minimum requirements for

coverage and capacity as specified in the RFP will be specific to this location.

2.2 Requirements for RFP Recipient’s Response

The merits and qualifications of RFP recipient’s response will be evaluated based upon a number

of factors including the technical and business requirements stipulated in this RFP.

RFP recipient should therefore review each requirement associated with the products and

services solution captured in this RFP and respond to each one explicitly in the compliance

statement highlighting their full compliance, partial compliance, or non-compliance along with

supporting information and documentation, as applicable.

RFP recipients are given 30 days to prepare and submit their responses along with supporting

credentials, after which the Customer and its associates will initiate the evaluation process.

2.3 RFP Evaluation Process

The RFP evaluation process will commence immediately after completion of the RFP recipients’

response period and evaluation will last for a period of 18 days.

The response evaluation will be based upon a number of factors including, without limitation, the

technical and commercial requirements stipulated in this RFP document. It is acknowledged and

agreed that customer may share the results of and consult others in connection with this RFP

evaluation process

The evaluation process may also include multiple meetings with the RFP recipients to clarify

their responses and to seek more information on their product and service offerings, as needed.

Prior to awarding any portion of the RFP to any RFP recipient, the customer reserves the right to

request additional information regarding the RFP recipient (e.g., prior history with the customer).

The customer reserves the right to decide the winner(s) and shall not be required to disclose any

details of the evaluation outcomes.

RFP recipient shall assign a contact for customer in connection with the RFP. The customer

reserves the right to negotiate a change in the individual assigned to represent the company

awarded any rights if the assigned individual, in the opinion of the customer, is not meeting the

needs of the customer appropriately. This right shall carry forward through the response period

and during the term of any contract.

2.4 Final Decision

Based on the evaluation of RFP responses, the customer may choose a winner but is under no

obligation to inform other RFP recipients following a selection. For the avoidance of doubt,

customer is also under no obligation to select any winner in connection with this RFP.


6 | P a g e

The customer may choose to award a particular portion of the RFP to a specific vendor if the

customer decides that vendor presents the best solution.

The customer reserves the complete right to the RFP recipient selection process and no further

questions or query seeking any clarification about the decision-making process or reasoning

behind choosing one RFP recipient instead of another will be entertained.

PLEASE BE ADVISED THAT, BY VIRTUE OF RESPONDING TO THIS REQUEST AND

PARTICIPATING IN THIS PROCESS, IT IS EXPRESSLY UNDERSTOOD AND AGREED

BY YOU THAT THE CUSTOMER RESERVES THE RIGHT TO ACCEPT OR REJECT ANY

OR ALL SUBMISSIONS, EVEN IF ALL STATED REQUIREMENTS ARE OR ARE NOT

MET. YOU FURTHER ACKNOWLEDGE AND AGREE THAT THE CUSTOMER IS

UNDER NO OBLIGATION TO GRANT YOU, NOR ANY OTHER COMPANY, A LICENSE

OR ANY OTHER GRANT OF RIGHTS. YOU ACKNOWLEDGE AND AGREE THAT THE

CUSTOMER’S DECISION NOT TO AWARD A CONTRACT TO THE RFP RECIPIENT

SHALL NOT GIVE RISE TO ANY RIGHTS IN FAVOR OF THE RFP RECIPIENT. YOU

FURTHER ACKNOWLEDGE AND AGREE THAT THE CUSTOMER SHALL HAVE THE

RIGHT, IN ITS SOLE DISCRETION, WITHOUT GIVING REASONS THEREFORE, AT

ANY TIME AND IN ANY RESPECT, TO TERMINATE DISCUSSION WITH ANY OR ALL

PROSPECTIVE COMPANIES. RFP RECIPIENT SHALL SOLELY BE RESPONSIBLE FOR

ALL OF ITS COSTS DIRECTLY OR INDIRECTLY RELATED TO PREPARATION OF A

RESPONSE TO THE RFP AND SHALL NOT BE ENTITLED TO RECOVER ANY SUCH

COSTS FROM CUSTOMER (OR Third Party) UNDER ANY CIRCUMSTANCES.

AS A CONDITION OF PARTICIPATING IN THE RFP AND HAVING THE CUSTOMER

CONSIDER THE RFP RECIPIENT’S SUBMISSION, RFP RECIPIENT, ON BEHALF OF

ITSELF, ITS AFFILIATES, OFFICERS, DIRECTORS, EMPLOYEES, REPRESENTATIVES,

AGENTS, INSURERS, PRINCIPALS, PARTNERS, SUCCESSORS, AND ASSIGNS

(HEREIN THE " RFP RECIPIENT RELEASORS"), DOES HEREBY AGREE, FOR GOOD

AND VALUABLE CONSIDERATION, THE RECEIPT AND SUFFICIENCY OF WHICH IS

HEREBY ACKNOWLEDGED, TO UNCONDITIONALLY RELEASE, HOLD HARMLESS,

FOREVER DISCHARGE, AND COVENANT NOT TO SUE THE CUSTOMER, THIRD

PARTY AND ITS AFFILIATED OR RELATED ENTITIES, OFFICERS, DIRECTORS,

EMPLOYEES, REPRESENTATIVES, AGENTS, INSURERS, PRINCIPALS, PARTNERS,

SUCCESSORS, AND ASSIGNS (THE "CUSTOMER RELEASEES"), FOR ANY AND ALL

CLAIMS, LIABILITIES, OBLIGATIONS, DEMANDS, DAMAGES, COSTS, EXPENSES,

ATTORNEYS' FEES, OF ANY KIND WHETHER KNOWN OR UNKNOWN, THAT THE

RFP RECIPIENT RELEASORS HAVE EVER HAD, NOW HAVE, OR HEREAFTER MAY

HAVE AGAINST THE CUSTOMER RELEASEES ARISING OUT OF, IN CONNECTION

WITH, OR RELATING TO THIS RFP AND/OR SUBMISSION, INCLUDING, WITHOUT

LIMITATION, THE PROCESS, EVALUATION, OR DECISION THEREOF.

High Density Wi-Fi Infrastructure – RFP Requirements_______________________ Business Terms

7 | P a g e

3 Business Terms

3.1 Standalone Terms

The customer anticipates that it may execute an agreement with an RFP recipient

substantially in the form of an agreement which will obligate the applicable RFP

recipient to all requirements stipulated in the RFP as well as the commitments contained

in the RFP recipient’s response.

Some RFP recipients may have existing agreements with the customer. The agreement to

be set with respect to this RFP shall be independent of the pre-existing agreements.

In case of third-party contractors for hardware / software equipment purchase or design,

installation, configuration, optimization, and post-optimization, the RFP recipient, in

conjunction with the customer, shall be responsible for identifying, soliciting, and

qualifying the subcontractors.

All third-party contractors selected by the RFP recipient shall have to be approved by the

customer before commencement of work.

Falsification or misrepresentation of any information about the RFP recipient or any

third-party subcontractor will constitute grounds for cancellation of any contract resulting

from this RFP.

3.2 Sponsorship Interests

In this section, the RFP recipient shall indicate any interest, amount, and term for

sponsorship linkage agreement with Customer’s marketing partner, which will be given

consideration in our overall review of responses. Assets and sponsorship items will be

negotiated separately from this RFP proposal. To discuss sponsorship interest please

contact Keith Burdette, Rupp Arena Sports and Entertainment Properties, 859-233-4567

x3290. This negotiation must be conducted prior to submittal of RFP to customer (on or

before 9/19/16).

3.2.1 Other Considerations

Apart from the scenarios and model mentioned earlier in this section, the RFP recipient

may wish to offer other innovative and mutually beneficial business models and

financing that are not explicitly captured in this RFP.

Any financial credit towards trade-in of existing Wi-Fi, core/switches, firewalls will be

considered. Existing equipment is as follows:

1. Qty 2 – Cisco Nexus 5548UP Core Switches

2. Qty 4 – Cisco Nexus 5548UP N55-M16P= 16 port 1/10GE Ethernet/FCoE

modules

3. Qty 2 – Cisco ASA-5520 Firewall

High Density Wi-Fi Infrastructure – RFP Requirements______ _________________ Business Terms

8 | P a g e

4. Qty 2 – Cisco WLC-4400 WLAN Controller

5. Qty 13 – Cisco AIR-LAP1252AG-A-K9 Access Point

6. Qty 44 – Cisco AIR-CAP3502I-A-K9 Access Point

7. Qty 7 – Cisco AIR-CAP3502E-A-K9 Access Point

8. Qty 1 – Cisco Catalyst WS-C2960-24PC-L Switch

9. Qty 1 – Cisco Catalyst WS-C2960-G-48TC-L Switch

10. Qty 5 – Cisco Catalyst WS-C2960S-24PD-L Switch

11. Qty 2 – Cisco Catalyst WS-C2960S-24PS-L Switch

Please describe any other business consideration that you would like to submit as a part

of this business proposal.

3.3 Ownership of Consumer Data

Any data in the form of reports, logs, consumer behavior analysis, etc. collected from the

Wi-Fi system installed in the venue shall be owned by the Customer (or as otherwise

mutually agreed).

Customer shall not be required to pay any price to procure the data collected from the

Wi-Fi system installed in customer’s venues (or as otherwise mutually agreed).

List of such metrics shall be mutually agreed upon award of contract to the successful

RFP recipient.

3.3.1 Sharing of Event Performance Results

Data collected for all major events (e.g., games) at the venue shall be shared with the

customer and any consultant recruited by the customer.

Network shall be capable of tracking usage patterns and gathering analytics related to

consumer behavior and application usage to aid the marketing team of the customer.

Any external use of such data by the RFP recipient shall require explicit approval from

the customer.

3.4 Software Flexibility

Wi-Fi network installed at the venue must be compatible with a variety of popular user-

oriented platforms (e.g., iOS, Android, Windows, Blackberry).

Wi-Fi network must also be compatible with the private use application at all Point of

Sale, ticketing and scanning (Ticketmaster) and any other identified applications.

High Density Wi-Fi Infrastructure – RFP Requirements__________________ Statement of Qualifications

9 | P a g e

4 Statement of Qualifications

The purpose of this section is to evaluate the RFP recipient’s credentials, capabilities, and

relevant experience against the requirements stipulated in this document.

4.1 Company Background

This section shall include background information about the RFP recipient, overview of its

organization structure and shareholding status, description of its financial performance for the

past 2-3 years, and other relevant information, as applicable.

4.2 Experience in Large Sports Arenas and Convention Center Venues

This section shall include details for experience at any large sports arenas and convention venues

in the U.S. and other countries.

Companies wishing to be considered for this project shall have a minimum of 5 years’

experience on projects of similar size and requirements.

Provide contact name, phone number and email address for each project referenced.

Include information on each venue such as capacity, size, location, project value and

scope in terms of type of service installed.

Cisco providers must be Authorized Technology Provider (ATP) certified.

4.3 Company Financial Statements

In order to facilitate the evaluation and develop confidence about the company’s financial health,

the RFP recipient is required to disclose relevant financial statements to the customer.

While healthy financial performance may be treated as a necessary qualification, superior

financial performance alone may not be sufficient to win the contract.

4.4 Other

Any other relevant information about the company and/or its capabilities and qualifications may

also be provided.

High Density Wi-Fi Infrastructure – RFP Requirements_______________ Product and Services Portfolio

10 | P a g e

5 Product and Services Portfolio

The purpose of this section is to obtain information about Wi-Fi product and service offerings

relevant to high-density venue deployment.

The superiority of product and service offerings will be a critical consideration during the RFP

process.

5.1 Product Description

This section shall include the entire suite of Wi-Fi products that are currently offered and

supported by the RFP recipient along with features and capabilities.

5.1.1 Product Portfolio

The product portfolio shall be presented clearly highlighting their features and capabilities as

well as use cases (i.e., suitable deployment scenarios).

5.1.2 Description of Individual Network Elements

This section shall include details and provide necessary technical information regarding each

network element as well as ancillary products necessary for end-to-end Wi-Fi network

deployment for an arena/convention center venue.

RFP recipient must highlight whether these products have been deployed in any similar or

different commercial venues, and provide additional relevant details about the nature of

deployment.

In case any network element or product offering that has been recently developed and is not

commercially deployed in any network, RFP recipient must highlight the product’s features and

capabilities, use cases, benefits over existing product family, comparison with other similar

solutions present in the market, and any other relevant technical details.

5.2 Professional Services Description

This section shall include details regarding the RFP recipient’s professional service offerings for

Wi-Fi design, deployment, optimization, network design and management, and future upgrade

capabilities. This offering shall be treated as critical in facilitating the RFP response evaluation

and final decision-making process.

5.2.1 Design & Dimensioning

This section shall include details regarding RFP recipient’s credentials and past experience

performing design & dimensioning exercise to facilitate high-density Wi-Fi deployment in sports

and entertainment venues and convention centers along with any suitable examples.

High Density Wi-Fi Infrastructure – RFP Requirements__ Product and Services Portfolio

11 | P a g e

5.2.2 Installation & Commissioning

RFP recipient shall describe its capabilities and past experience for deployment and end-to-end

commissioning of commercial-grade Wi-Fi networks for high-capacity venues.

5.2.3 Optimization & Commercial Integration

RFP recipient shall describe its capabilities and past experience for system optimization and

performance acceptance to facilitate seamless integration to the commercial network. Thorough

experience from large-scale Wi-Fi deployments in sports venues shall be considered a critical

capability of the RFP recipient.

5.2.4 Maintenance Service & Event Support

RFP recipient shall highlight their credentials and capabilities for ensuring fault-free, smooth

maintenance of the deployed Wi-Fi network along with relevant examples. RFP recipient must

also provide examples of where it is responsible for Wi-Fi network performance in an arena

during special events. RFP recipient must highlight its capabilities of performance monitoring

and optimization on a real-time basis during the event.

5.2.5 Network Upgrades

RFP recipient shall outline how it plans to upgrade or install the Wi-Fi network to either manage

higher-capacity demand or deploy additional features and capabilities to leverage their

technological benefits. Examples of such experience shall be treated as useful inputs during the

evaluation process.

5.2.6 Maintenance / Monitoring / Repair Agreement

RFP recipient shall highlight its willingness and ability to enter into ongoing network

maintenance, monitoring, and repair service agreement against a specific set of service level

agreements that will include, but is not limited to, MTBF of individual network elements and

network up-time during special events. RFP recipient should share examples of current ongoing

support to any similar venue.

5.2.7 Commitment to Service Level Requirement

RFP recipient shall agree to the set of minimum service level requirements associated with its

products and services that are outlined in the subsequent technical requirement sections of this

document.

High Density Wi-Fi Infrastructure – RFP Requirements Technical Requirements

12 | P a g e

6 Technical Requirements

6.1 High-Density Wi-Fi Solution

1. RFP recipient shall provide complete Wi-Fi coverage and capacity to all users in all zones

with the installation of private and public SSIDs.

2. RFP recipient shall submit a report detailing the following items:

a. Overview of Wi-Fi solution architecture

b. High-level approach to facilitate high-density Wi-Fi solution

c. Key features and uniqueness of the solution along with competitive advantages over

solutions from other companies

6.2 Deployment Solution

RFP recipient shall provide a solution catering specifically to the requirements and needs

of the arena, convention center and theater.

RFP recipient shall prepare the solution to accommodate capacity demand of the venue,

in terms of estimated number of clients during events, estimated number of clients within

each public zone (bowl, concourse, concessions, exhibit halls, meeting rooms and other

public zones and estimated number of clients in private network (sidelines, ticketing,

press box, administrative offices and other private zones.

The LPV Wi-Fi will provide services to and including all administrative office and

personnel devices, Ticketmaster mobile ticket scanning, wireless point-of-sale (POS)

devices, guests including those purchasing Wi-Fi access, free access to fans/patrons,

high-performance WLAN access for press and media.

RFP recipient shall provide an LPV solution to include the following:

Wi-Fi onboarding fully customizable by the customer and able to collect a variety of

information such as email address, cell number and other demographic information as

desired as well as capturing device information such as device type and MAC

address.

Ability to connect to information, services and Internet using the onboarding

application as well as push notifications to users.

Location services utilizing both AP and BLE devices. Used to understand patron’s

traffic patterns and provide service notifications based on location.

Ability to locate, track and map WLAN devices and asset tags.

Provide real-time network and usage statistics and analytics.

Ability for full HD video surveillance over wireless network.


13 | P a g e

Ability to provide credit card payment gateway and portal for automated sale of Internet

service to clients and/or exhibitors in specific areas such as meeting rooms and exhibit

halls if customer decides to implement a payment gateway.

6.2.1 Baseline WLAN Coverage and Capacity

WLAN Device Support: The WLAN must support a variety of WLAN-enabled devices;

including but not limited to tablets, smartphones, laptops, ticket and PoS scanners, IP

video surveillance devices, IP phones, digital signage players.

High-density coverage and capacity: The WLAN must provide sufficient bandwidth to

support the variety of applications used by the thousands of WLAN devices throughout

the venues.

Higher-capacity areas (press and media area): The press and media areas typically

require higher-bandwidth Internet connections resulting from a higher number of devices

in a small area. These areas must be accommodated for special events.

Scalability: The network must be scalable to provide high quality Wi-Fi service in a

highly dense environment supporting up to 30,000 users simultaneously.

3G/4G offload: The venue WLAN must be designed to maximize the offload of data

traffic from the in-venue cellular network. The goal is to provide the users good service

for voice, texting, Internet applications and possibly video streaming.

High Availability: The WLAN must be designed to support automatic network recovery

from the loss of an Internet link or network equipment or link failure with minimal

downtime. Redundant controllers are required.

Enhanced security services: The WLAN should have in-depth security capabilities that

help ensure the integrity of the network, identify threats and devices that cause RF

interference that degrade Wi-Fi performance with the ability to contain such devices if

necessary.

Access point mounting restrictions: Because general seating areas have limited

overhead structure, access point and antenna placement is limited and aesthetic and sight-

line restrictions must be adhered to.

6.2.2 End User or WLAN Device Access Requirements

Comprehensive WLAN Coverage and seamless roaming: Users should experience a

consistently high level of WLAN performance anywhere within their designated area

within the venue and to be able to move about without losing WLAN connection. Note:

Seamless roaming does not require active hand-off between APs, unless for VoIP.

Simple Fan Internet access: The fan should only have to choose the venue network in

their device and have immediate access to an onboarding portal as designed for/by the


14 | P a g e

venue IT staff. The fan experience should be simple, fast, reliable and independent of

cellular carrier or device manufacturer.

Secure network access for internal IT personnel: This includes privileged-level access

to internal server resources with more stringent authentication using WPA2 pre-shared

keys or 802.1X with possible Microsoft Active Directory or other IT directory

integration.

Simple, secure network access for business visitors: This includes the implementation

of an authentication mechanism for allowing visitors limited access to internal resources

and the Internet.

WLAN for point-of-sale (PoS) devices and ticketing: The WLAN must support PoS

and ticketing WLAN devices with network segmentation for separating this traffic from

general property operations traffic. PoS and Ticketing scanners should use the 5 GHz

band.

6.2.3 Management and Control Requirements

Centralized WLAN management: The WLAN management system must support the

deployment, operation, and management of hundreds of access points and thousands of

users. In addition, the management system should provide the ability to turn off PoE to

certain APs during the off-season.

Tracking user, device, and network statistics: The WLAN management system must

include capabilities to track statistics for trend analysis, troubleshooting and WLAN

health monitoring.

Location services: The wireless network should be “location aware” and be able to track

hundreds to thousands of WLAN and active RFID devices from directly within the

WLAN infrastructure using AP or BLE devices.

Unified Wireless and Wired Network Management: The Network Management

System should provide a unified management platform for both the wireless and wired

network.

Measurement and reporting: Objective measurement and reporting of the fan Wi-Fi

experience.

6.2.4 Service and Support

Hardware and software support: The proposed hardware should include as a minimum

24x7 phone and email technical support with next-business-day advanced hardware

replacement. Software support should include access to the latest maintenance updates.

Support should also provide access to installation, configuration, maintenance and other

relevant technical documentation.

Game/Event Day Support: Recipient is required to provide on-site support consisting

of a minimum of two WLAN engineers to perform configuration, tuning, troubleshooting


15 | P a g e

and analysis of the entire end-to-end WLAN solution during Busy Hours of Game/Event

period. A minimum of ten (10) games/events of support is required with selection of the

games/events at customer’s discretion.

Turnkey WLAN solution: The WLAN Solution provider should provide a set of end-to-

end services for planning, designing, implementing, operating, and optimizing the

proposed Wireless LAN solution

Public Zone (Open Access)

Wi-Fi network shall be provided free of charge to all fans inside the arena bowl, concourses and in arena

lobby holding area, Triangle Park and outdoor arena plaza area.

Private Zone (Restricted Access)

Wi-Fi network shall be restricted requiring credentials for user login inside all facilities. Purpose for this

is to regulate access to networks for media and certain guests/users.

6.3 Equipment

This section will focus on hardware and software equipment, including ancillary products offered by the

RFP recipient or its third-party associates / contractors / suppliers.

6.3.1 Features, Requirements and Minimum Capabilities

6.3.1.1 Hardware

Access Points:

It is the customer’s desire to install the latest access point technology for LPVs in order to “future

proof” the venue install for the coming years.

APs shall be a minimum 4X4 with three spatial streams MU-MIMO capable using 802.11ac Wave

2 technology. Recipient may suggest different AP technology based on LPV experience.

APs shall be equipped with dual radios 2.4GHz and 5GHz mode. If desired, second radio should

have capability of performing wireless security monitoring.

Support channels up to 160MHz wide with ability to dynamically switch between 20-, 40-, 80- and

160-MHz channels depending on RF channel conditions.

Ability to detect and contain rogue devices utilizing one or both AP radios.

Each AP radio should have independent antennas for 2.4GHz and 5GHz operation.

Access Layer Network Controllers:

Network controllers should be configured as an HA pair with active/passive failover. It is

mandatory to configure network controllers individually for all APs within a zone. These network


16 | P a g e

controller pair shall be capable of monitoring and identifying issues with the network, providing

smooth troubleshooting, and generating periodic reports.

Controllers shall also provide:

Remote control, network monitoring, and configuration to dynamically re-assign channels and

manage RF parameter settings

Tracking and calculation performance during peak operation

Efficient troubleshooting in case of failures or breakdown

Real-time Wi-Fi maintenance reports, status, and alarms

Usage and performance reports.

Alarming or alerting of failures, breakdowns or other configurable threats or alerts via email.

Modules in Distribution and Core Layer:

Customer currently employs Cisco switching, routing and firewall equipment in MDF and all IDF

locations. It is the customer’s desire to continue use of Cisco equipment for LAN purposes

replacing the current equipment with new, HA hardware

Switches must be UPoE capable to provide sufficient power for access points, IP telephone,

security cameras, etc. Current network LAN supports 10Mbps backbone over multimode and

singlemode fiber optic cable, switches must be capable of uplink at 10Mbps or higher.

Network shall be equipped with suitable Cisco branded IDF switches, MDF LAN switches,

firewalls and core layer WLAN controllers. Two core switches installed in an aggregated

architecture are required to support all IDF and MDF switches.

Two redundant HA (active/passive) firewalls capable of high volume of connections.

All Cisco equipment should have SmartNET services included and listed independently from

hardware.

Wi-Fi Antennas:

Internal vs. External Antennas: Internal antennas shall be deployed in most standard scenarios.

External antennas shall be used for aesthetic reasons (e.g., to hide the AP) or when a directional

antenna is a necessity from a coverage / capacity perspective. Choice of antenna shall also

consider deployment constraints. Placement is limited in arena and additional mounting

hardware such as down pipes and beam rigging will be needed. Customer will work with

contractor to designate approved hanging locations. Unless otherwise negotiated, RFP recipient

and contractor will be responsible for acquisition and installation of all mounting hardware.

Omnidirectional and Directional Antennas: Omnidirectional antennas shall be used when the

AP is located on the ceiling (located 15-20 feet or lower) and there is no frequency reuse planned

in the vicinity. Directional antennas shall be used to provide coverage and higher capacity.

Please describe all antenna options.

Antenna Gain: The gain of the antenna shall be 0-14dBi. For different gain values, proper

technical justification shall be provided by the RFP recipient.


17 | P a g e

Horizontal and Vertical Beamwidth: The horizontal and vertical beamwidth shall be decided

based on the target coverage area and the size of the deployable antenna.

Access point/Antenna mounting restrictions: Customer preference is to have most access

points and antennas installed overhead with details to aesthetics. However, it is understood that

the design may include mounting of APs and antennas in the seating area. Painting of antennas

may be required for aesthetic reasons. Sight lines must remain clear inside arena, patron’s views

to all video screens including corner video and center hung cluster must not be impeded.

MDF & IDF Hardware:

Customer will identify new IDF closets acceptable for use. Electrical utilities for IDF closets will

be the responsibility of the customer.

MDF hardware to support entire venue network shall consist of the following minimum model

configurations:

(2) Cisco Catalyst C6880-X-LE Chassis

(4) Cisco Catalyst C6880-X-LE-16P10G Multi Rate Port Card

(4) Cisco Catalyst C6880-X-3KW-AC 3KW AC Power Supply

(2) Cisco Catalyst C6880-X-FAN Fan Tray

(2) Cisco SFP-10G-LR SFP Module

Number of singlemode or multimode SFP modules for field switches UL dependent on

IDF configuration and determined by AP design.

(3) Cisco Catalyst WS-C3850-48U-L 48 port UPOE LAN Base

(3) Cisco Catalyst PWR-C1_1100WAC/2 Secondary Power Supply

(3) Cisco Catalyst C3850-NM-2-10G 2X10GE Network Module

(3) Cisco Catalyst STACK-T1-50CM Type 1 50CM Stacking Cable

(2) Cisco ASA 5585-X Firewall Chassis with SSP10,8GE,2SFP+,2GE Mgt, 2AC,

3DES/AES configured as HA pair

IDF hardware to support venue network shall consist of the following minimum configuration,

quantity of switches based on high density wireless design:

Cisco Catalyst WS-C3850-48U-L 48 port UPOE LAN Base or WS-C3850-24U-L 24 port

UPOE LAN Base depending on density needed.

Cisco Catalyst PWR-C1_1100WAC/2 Secondary Power Supply

Cisco Catalyst C3850-NM-2-10G 2X10GE Network Module

All access points and WLAN controllers shall be compatible with above hardware configuration.

Respondent must document any exceptions to the use of the above Cisco hardware configuration

listing any incompatibilities.


18 | P a g e

Optical Fiber Cables:

Currently installed Multi-mode fiber cables can be used for short-distance connections within the

venue to decrease cost without the loss of quality.

It is recommended that single-mode fiber cables be used for long-distance backhaul connections

and any new IDF installations.

Customer has existing multi-mode and single-mode fiber infrastructure that can be utilized for

edge switch connections. Customer will coordinate with installer on existing fiber installation.

Copper Cables:

RFP recipient is responsible for acquiring a certified cable installer for this project. Customer

will work with installer to define cable routes available for all cable runs. Any installer’s license

required by local, state or federal code to be provided by request.

The installer is to terminate the cabling in the designated IDF closets or other agreed upon

location in approved design via a patch panel.

All copper cabling from MDF/IDF to all access points in the arena shall be Category 6 UTP, non-

shielded cable. All cabling at Opera House shall be Category 6 UTP, non-shielded cable. All

exhibit hall locations shall be Category 5e UTP, non-shielded cable as a temporary install.

Use of plenum rated or riser cable is dependent on the location of the cable runs. All systems

should follow the EIA/TIA-568B requirements for pin-out configurations and testing/certification

conformance standards.

All locations with exception of exhibit halls, will terminate at IDF using patch panels. Due to

temporary nature of exhibit hall install terminations can be direct Cat5 plugs.

Recipient will supply all Panduit patch panels utilizing Mini-Com patch panel jacks as well as

mounting racks for all panels and switch gear. All Mini-Com jacks terminated for access points

shall be yellow in color. Customer will coordinate rack and patch panel installation locations this

with cable installer.

Customer will install all necessary electrical outlets for racked switchgear.

R

Customer must approve all conduit runs prior to installation. Surface mounted cabling shall be

installed in conduit/cable tray and secured with approved fasteners along its length and only in

locations approved prior to installation.

Vendor shall take full responsibility for any damages caused by the Vendor during installation of

cabling. Full repair of any damage will be the sole responsibility of the Vendor, including

patching and painting of affected areas.

6.3.1.2 Software

IEEE Standard:

All APs shall be at least 802.11ac compliant with a provision to upgrade to newer standards in the

future.


19 | P a g e

APs shall also be backward-compatible to provide service to legacy devices (supporting standards

before 802.11n such as 802.11a and 802.11g).

802.11b traffic shall be blocked as transmissions over 802.11b decrease the overall efficiency and

throughput significantly. 802.11b shall be enabled only if the Third Party’s or Customer or venue

owner’s services mandatorily require it to be enabled. In such a case, 802.11b must be enabled only

in zones where the service will be required.

Security:

Security shall be provided for the private SSIDs in the venue.

Current required security standard shall be WPA2-Enterprise.

WEP standard shall not be used for any private SSIDs.

Loading Balancing or Band Steering:

Wi-Fi network shall be capable of loading balancing / band steering.

Channel aggregation or channel bonding:

Wi-Fi equipment shall be capable of supporting channel bonding of at least 40MHz.

Actual implementation will be a function of the design and dimensioning results.

Frame aggregation:

Frame aggregation shall be a required feature of the Wi-Fi network.

Maximum limit on aggregation level shall be controlled depending on the peak number of users

and type of traffic experienced.

Authentication:

Network shall be capable of implementing authentication features which could be optionally

turned on to admit only specific user groups in the arena (e.g., fans, ticket scanners, media).

Carrier Mobile Data Offload:

Network shall be capable of implementing mobile carrier data offload.

Tracking User Usage Patterns:

Network shall be capable of tracking the usage patterns and gathering analytics related to consumer

behavior and application usage to aid the marketing team of the customer.

Wi-Fi Multicast:

The Wi-Fi and network systems shall have full capability to perform multicasting.

Hotspot 2.0:

The infrastructure shall be capable of Hotspot 2.0 features.

Location-Based Services:

Network shall be capable of location-based services to estimate the location of a client in the

venue as well as provide statistics indicating number of devices and time spent in a particular

area. Ability to map a device’s path and view in real-time or past history.


20 | P a g e

Fan/Guest Onboarding Services:

A captive portal for onboarding of fans and guests which will capture desired information such as

email address, phone number or other customized demographics.

Portal should be easily customizable and mobile ready, independent of mobile device type with

ability to display banner advertising.

Graphical buttons or links should be easily added to direct fans/guests to Internet, social media or

other designated websites or informational displays.

It is desirable to collect information on fans/guests so portal can be personalized for when a

patron returns and logs back into the portal.

6.3.2 Reliability

RFP recipient shall establish their product superiority in terms of reliability levels that shall include, at the

minimum, the following:

Mean Time between Failures (MTBF) for individual network elements.

Maximum percentage of time with end-to-end fault-free operations during special events.

Maximum percentage of time with end-to-end fault-free operations throughout the year.

Network shall never be brought down for maintenance or repair work within 48 hours of any special

event.

Maintenance and repair associated with any service interruption shall always be performed during

the maintenance window, as mutually agreed between the customer and the RFP recipient (along

with prior approval from the customer).

6.3.3 Warranty and Maintenance

RFP recipient shall explain, in detail, its warranty for its products and services.

Provide a detailed schedule outlining manufacturer warranties, support, terms and conditions for

all equipment and software. Include length of coverage and repair or replacement options.

Provide a detailed schedule outlining subsequent annual maintenance for each piece of

equipment, software and licenses which begins immediately at the expiration of manufacturer’s

warranty. Include length of coverage and repair or replacement options.

6.3.4 Provision for Upgrades

RFP response shall also include provisions for future upgrades.

System upgrades may be needed for various reasons, including but not limited to, technology

upgrade, system coverage and capacity enhancement, software upgrade, and network

architectural change.

RFP recipient shall be responsible for suggesting such upgrade requirements and also performing

the upgrade in an elegant manner with minimum interruption to the commercial network.


21 | P a g e

RFP recipient shall obtain approval of activities as well as its bill of materials from the customer

prior to commencement of such activity.

6.3.5 Training

RFP recipient shall be responsible for offering training services to the customer and its personnel

to educate about the product solution and arena deployment.

6.3.6 Documentation

RFP recipient shall submit to customer Information Technology Department the following

documents within thirty (30) days of installation. These documents need to be in electronic

format as well as bounded/binder paper copy:

o End User guides

o System documentation

o Detailed inventory list of all equipment installed

o Full technical specification and as-built documentation including network diagrams.

o Other related documentation to the project.

High Density Wi-Fi Infrastructure – RFP Requirements Low-Level Wireless LAN Requirements

22 | P a g e

7 Low-Level Wireless LAN Requirements

Listed below are the detailed requirements for the wireless system. If RFP recipient does not fully

comply with any of the items below, please give an explanation.

7.1 Baseline WLAN Coverage/Capacity

Ref. # Description

Importance M – Mandatory HD – Highly Desirable

Comply F – Fully P – Partial N – Does Not

W1

WLAN RF coverage and AP capacity shall be designed to support both internal private applications (e.g., PoS, Ticketing) and public applications (e.g., guest access to Facebook, etc.)

M

W2

Support 802.11a/b/g/n/ac devices with a broad range of authentication options (Wireless Protected Access- Pre-Shared Key [WPA PSK], WPA2-PSK, WPA2-Enterprise, captive portal requiring credential entry).

M

W3 Support 2.4 and 5 GHz bands throughout the entire property. M

W4

Provide 2.4 and 5GHz coverage with support for a minimum number of concurrent active connections of 15,000 inside arena and the arena’s seating capacity and 10,000 for convention center, meeting rooms, pre-function areas and hallways.

M

W5 Provide minimum upload and download bandwidth of 2Mbps per device on 2.4GHz band and 5Mbps per device on 5GHz band.

M

W6 Be adaptable and dynamically change to accommodate the changing RF environment within the property. These changes should not require operator intervention.

M

W7 Be capable of dynamically filling coverage holes in case of AP failure.

M

W8 Support a centralized WLAN Deployment Model with redundant Wireless LAN Controllers and lightweight APs.

M

W9 Support unicast and multicast WLAN traffic M

W10 Provide standard QoS mechanisms for prioritizing unicast and multicast traffic.

M

W11 Support spectrum monitoring and analysis. M

W12 Designed to survive a WLAN controller failure where service is restored automatically without manual intervention.

M


23 | P a g e

Ref. # Description



W13 Provide multiple 1-Gbps links and support standards based link aggregation protocol.

M

W14 Provide logical separation of user groups associated with an SSID.

M

W15 Provide the ability to disable client-to-client communications on a per-SSID basis.

M

W16 Support standards based management protocols (i.e. SNMP v2c, SNMP v3, Syslog, etc.).

M

W17

Support integrated wireless intrusion prevention system (IPS) capabilities. That is, rogue AP detection can be performed without requiring dedicated APs or controllers for this purpose.

M

W18

Provide the ability to detect and contain rogue AP devices on either the same or separate channel as data traffic while simultaneously providing client services with no performance impact.

M

W19 AP network design should limit number of connections per AP in high-density areas to 100 or less.

HD

W20 Wireless design should provide an average RSSI in all areas at -65dBm or higher.

M

7.2 Wireless Access Point Requirements

Ref. # Description



WAP1 Simultaneous operation of 802.11a/g/n/ac standards. M


24 | P a g e

Ref. # Description



WAP2

802.11ac Wave 2 capabilities

4x4 MU-MIMO with four spatial streams

Maximal ratio combining (MRC)

802.11n and 802.11ac beamforming

20-, 40-, 80- and 160-MHz channels

PHY data rates up to 450 Mbps (40 MHz with 5 GHz)

Packet aggregation: A-MPDU (Tx/Rx), A-MSDU (Tx/Rx)

802.11 dynamic frequency selection (DFS)

Cyclic shift diversity (CSD) support

M

WAP3

Features to detect

Presence within 30 feet

Proximity to within 15 feet M

WAP4 256 QAM modulation M

WAP5

Integrated frequency spectrum analyzer (for 2.4GHz and 5GHz bands)

Granular spectral resolution of 78 kHz or better across 20-, 40-, 80- and 160-MHz-wide channels

RF interference detection & mitigation

Automatic detection and classification of interference sources (bluetooth, DECT, Microwave devices, audio-video transmission device, the device interfering etc.)

Ability to view the results of the analysis (FFT spectral density, spectrogram , the occupancy of the channel , the power level of signals) on a PC in real time

M

WAP6 Mechanisms for minimizing RF noise in a high-density environment M

WAP7

Configurable transmitter power

Range of 2.4 GHz to 200 mW

Range of 5 GHz to 200 mW M

WAP8

Power options:

AC power

802.3af, PoE + (802.3at), Cisco UPOE M

WAP9

Rugged metal housing and extended operating environments:

Operating temperature: -4° to 122°F (-20° to 50°C)

Operating humidity: 10% to 90% (noncondensing)

Must be able to withstand environmental temperatures up to 100°F without failure

M

WAP10 Gigabit Ethernet (10/100/1000) M

WAP11 Wi-Fi Certification M

WAP12 Compliance with Directive 1999/5/EC and 93/42/ECC M


25 | P a g e

Ref. # Description



WAP13

For APs with External Antennas, the antennas MUST support:

Gains up to 13 dBi for coverage of bowl areas; 6dBi for other areas

Narrow beamwidth (<30 degrees) for coverage of bowl areas

Articulating mount (for flexibility in mounting)

Paintable (for aesthetic purposes)

Operating temperature: -22° to 158°F (-30° to 70°C)

Must not present any sight line issues with patron seating

M

WAP14 Support zero-touch deployment. That is, APs shall be capable of being brought into service without the need for pre-staging or local direct-connect AP configuration.

M

WAP15 Comply with government communications regulations. M

WAP16 Support a 1-Gbps LAN connection. M

7.3 Wireless LAN Controller Requirements

Ref. # Description



WLC1

Wireless LAN controller MUST provide:

Support for up to 6000 access points and 64,000 clients

Minimum of 2 10-GE interfaces

Support for up to 4096 VLANs

M

WLC2

Provide wired speed, non-blocking performance for 802.11ac networks RF Management M

WLC3

Provide real-time and historical information about RF interference impacting network performance across controllers

M

WLC4

Enable control and provisioning of wireless access points (CAPWLC)-compliant DTLS encryption to help ensure full-line-rate encryption between access points and controllers across remote WAN/LAN links

M

WLC5 Proactive blocking of known threats M

WLC6 Use Link Aggregation with a minimum of two 1-Gbps load-balancing links when connecting to the wired network

M


26 | P a g e

Ref. # Description



WLC7 Be capable of maintaining service to their registered APs in case of a link failure to their connected switch.

M

WLC8

Be capable of maintaining service to their registered APs in case of a switch failure. That is, the WLAN controller is connected to two switches and therefore, a single switch failure would route all traffic to the remaining operational switch.

M

WLC9

Centralized management and control of:

Security policies with intrusion detection

Radio spectrum

Transmission quality according to the protocol CAPWLC (RFC 5415) or equivalent

M

WLC10

Bandwidth management:

Automatic adaptation to changes in real time

Optimization of access points (detection and elimination of areas without coverage)

Dynamic allocation of radio channels

Detection, elimination and avoidance of interference

AP load balancing

RF profiling (configuration parameters) for groups of access points

Automatic distribution of clients between access points

Support mechanisms for prioritization range 5GHz dual band clients

M

WLC11

Support for the mapping of SSIDs to VLANs segment on a wired network

1:1 and 1:n (where the SSID can be mapped to multiple segments of the VLAN user traffic fold between segments)

Ability to tunnel traffic to the controller and to a wired network at the level of the AP (configured per SSID)

M

WLC12 Support for unicast traffic (IPv4 and IPv6) M

WLC13

Support for multicast (IPv4 and IPv6)

Support for IGMP / MLD snooping

Ability to optimize the distribution of multicast traffic on a wired network (between the controller and the access point)

Support the conversion of multicast traffic to unicast

M

WLC14 Support for mobility (roaming - in ) users (L2 and L3 - IPv4 and IPv6, within and between controllers) M


27 | P a g e

Ref. # Description



WLC15

Support for QoS

802.1p

WMM, TSPEC

By limiting the upload/download bandwidth per user

Call Admission Control of - the static and dynamic band defined based on the analysis of traffic profiles

U- APSD

Support for a deep-packet inspection mechanism, such as NBAR2 with the ability to download future protocol updates without the need to install core controller software

M

WLC16

Support for security mechanisms :

802.11i, WPA2, WPA, WEP

802.1x EAP by (PEAP, EAP -TLS, EAP -FAST, EAP -TTLS )

Access control lists ( ACLs), including support for DNS-based (fully qualified domain name) access control lists (ACLs) for clients during registration. With DNS-based ACLs, clients that are in the registration phase are allowed to connect to the configured URLs phase of onboarding

Authorization server - RADIUS, TACACS +, LDAP, built-in local user database (min. 2,000 entries)

Ability to create different security policies within a single SSID

Ability to profile wireless devices and enforcement of policies such as VLAN assignment, QoS, ACL and time-of-day-based access VLAN assignment

Authentication (digital signature) 802.11 management frames (detection spoofing access points users to the addresses of infrastructure) - 802.11w or similar

Authentication of the access points based on X.509 certificates

Detection and deactivation of the foreign access points with built-in IDS to detect typical attacks on wireless networks (fake AP, NetStumbler, deathentication flood, etc.)

Ability to integrate with an IDS / IPS system

Cryptographic protection (DTLS) or equivalent control traffic and user traffic CAPWLC

Support for a DHCP proxy

M


28 | P a g e

Ref. # Description



WLC17

Support for guest access (IPv4 and IPv6)

To redirect users of a specific SSID to the login page (ability to personalize login page per SSID)

Ability to create users via a dedicated web portal (acting on the controller) with a time validity of the account

Ability to configure as a dedicated controller to handle guest traffic - all traffic from the guest SSID access harvested on other controllers must be sent to the controller (located in the public area of the network) in a way that ensures a logical separation of internal traffic

M

WLC18

Support for Apple iOS7 Captive Portal with the ability to detect and respond to pre-iOS7 Captive and iOS7-based changes to CNA M

WLC19 Support for location-based services, handling telemetry tags

M

WLC20 Support for redundancy (N +1 and 1:1)

M

WLC21 Sub-second stateful failover for Service Set Identifier (SSID) high availability M

WLC22 Support for redundant power supplies

M

WLC23

Ability to configure AP to automatically shut down its radio when the Ethernet link is not operational, and then to turn the radio back on when the Ethernet link comes back

M

WLC24

Ability to analyze traffic through a controller that allows for the identification and classification at the application level, the possibility of marking or reject traffic

M

WLC25 Ability to collect and export statistics using Netflow protocol / JFlow or equivalent M

WLC26

Mechanisms for deactivation of the radio modules at certain times in order to reduce the energy consumption of the system

M

WLC27 Support for management by HTTPS, SNMPv3, SSH, serial console port M

WLC28 Ability to terminate SSID broadcast and shutdown SSID based on a time interval or date and time range HD

WLC29

Clients connecting to a 2.4GHz radio are automatically steered to faster 5GHz connection and disconnected from 2.4GHz

M


29 | P a g e

7.4 WLAN Mobility Services Requirements

Ref. # Description



MS1

Scale:

Track up to 50,000 devices

Provide intrusion prevention services for up to 10,000 APs

Provide location services for up to 5000 APs

M

MS2 Track and locate interferers, rogues, Wi-Fi clients, and RF tags M

MS3 Detect fan presence and receive geo-fenced or zone-based alerts M

MS4 Provide system-wide interferer and event correlation

M

MS5 Perform zone-of-impact analysis

M

MS6 Provide a visual representation of the location of interferers, such as on a map M

MS7

Provide an XML-based API that allows the venue to integrate location information into applications, such as location-aware fan access, device-based services, browser-based services, mobile apps, online and onsite analytics, social analytics, and ads and offers

M

MS8 Provide a location-enabled captive portal supporting a custom onboarding/landing fan experience M

MS9

Provide on-site analytics show how, where, and when fans move throughout the venue in real-time and historically M

MS10 Provide tools that enable the organization to build and measure context-aware, targeted marketing campaigns M

MS11 Provide a seamless Wi-Fi sign-on experience for fans though use of captive portal/onboarding M

MS12 Provide a published location accuracy of +/-5M

M

MS13 Provide analytics that can run on-site

M

MS14 Provide analytics for device counts with on-site storage for 5 years M

MS15 Provide ability to compare clients in real-time vs previous 24-hour period M

MS16 Provide the ability to create zones of “interest”

M

MS17 Provide the ability to view client devices by Zones of “interest” M

MS18 Provide dwell times per Zones of “interest”

M

MS19 Provide daily and hourly visitor counts

M

MS20 Provide the ability to view client foot traffic pattern

M


30 | P a g e

Ref. # Description



MS21

Provide the ability to view client device information, at minimum device type, MAC address, Status (associated/unassociated), IP Address, SSID

M

MS22 Provide the ability to track BLE beacons without an overlay network M

MS23 Provide the ability to send PDF versions of reports via email

M

MS24 Provide role-based access (i.e. full administrative access vs read-only) M

MS25

Provide the ability to create a custom portals per SSID for wireless client on-boarding, including ability to use social media (e.g. Facebook)

M

MS26

Include intrusion prevention services that provide:

Rogue access point and ad-hoc rogue detection, classification, location tracking, and containment

Switch port tracing and disabling

M

MS27 Provide DoS attack identification and classification

HD

MS28 Provide wireless intrusion attack identification and classification HD

MS29 Provide active attack mitigation

HD

7.5 End User or WLAN Device Access Requirements

Ref. # Description



E1 The WLAN shall support all types of client devices, including but not limited to Laptops, iPads, tablets, POS scanners, Ticketing scanners, Smartphones and Wireless IP Handsets.

M

E2

The WLAN shall support a web-authentication capability for WLAN authentication for contractors, vendors, and other authorized visitors to the property that require access to internal server resources.

M

E3 The WLAN shall support 802.1X authentication for arena personnel and be capable of integrating with an existing Microsoft Active Directory or other LDAP user database.

M

E4 The WLAN shall support consistent performance and seamless roaming as clients move around the property. That is, the clients shall not have to re-authenticate when roaming.

M


31 | P a g e

Ref. # Description



E5

The WLAN shall provide open and equal fan access regardless of device and independent of cellular carrier. The fan should associate to the WLAN, navigate through a captive portal then have direct access to the Internet or other apps. Ability to create customized captive portals per WLAN.

M

E7

The WLAN shall provide features to encourage devices when associating to the WLAN to use the less crowded 5 GHz band. This is especially important for power users such as the Press or mission-critical applications like PoS or Ticketing.

M

E8 Since smartphones are the predominant device on the WLAN, the WLAN should provide features for optimizing the uplink and downlink performance of these devices.

M

E9 The WLAN shall support role based access which would allow specific users better performance or bandwidth allowance (i.e. media or internal staff)

E10 Upon authentication of user, WLAN shall place user on VLAN as determined by role.

M

7.6 Application Support

Ref. # Description



A1 The WLAN shall securely support internal private applications (e.g., PoS, Ticketing, Video Surveillance, Building Management Systems, Control Systems).

M

A2 The WLAN shall support a number of public applications including Internet Video, Email, Web Browsing, Social Networking, VPN, and Content uploads/downloads, specifically for media/press.

M

A3 The WLAN shall support Voice over WLAN with seamless roaming in designated areas within the property.

M

A4 The WLAN shall detect specific applications and accept or block access according to predetermined rules or ACLs. (i.e. block streaming by Periscope and Meerkat)

M

A5 The WLAN shall detect applications such as YouTube and automatically adjust bandwidth allowance based on predetermined values.

M


32 | P a g e

7.7 Management and Control

Ref. # Description



WNM1 Manage all APs and WLAN Controllers as a single system. M

WNM2

Provide the ability to import real floor plans, use integrated RF prediction tools to create a detailed WLAN design, including access point placement, configuration, and performance/coverage estimates.

M

WNM3 Provide the operator with the detected 802.11 and non-802.11 sources of interference and their general location.

M

WNM4 Provide the integration of wired network, WLAN and policy management into a unified system.

HD

WNM5

Provide roll-based access to specific levels of control of the network elements. For example, super user access with full WLAN configuration control verses Tier-1 personnel with read-only access for WLAN monitoring.

M

WNM6 Track the number of successful & failed connection attempts shown over time.

M

WNM7 Track user bandwidth & session duration statistics M

WNM8 Track the types of applications used HD

WNM9 Track the number of users per SSID M

WNM10 Track the number and type of user devices M

WNM11 Track the protocols used to connect (e.g., 802.11g, 802.11n) M

WNM12 Track the RF band usage (2.4 GHz, 5 GHz) M

WNM13 Track the devices causing radio interference and their location M

WNM14 Track the Internet uplink and downlink bandwidth utilization over time

M

WNM15 Track the network equipment state (up, down, errors) M

WNM16 Track AP Utilization (Channel Utilizations, uplink/downlink BW, peak device associations)

M

WNM17 Provide that ability to generate reports consisting the statistics mentioned above

M

WNM18

Provide wireless IPS network management and reporting as well as security event management and reporting with physical location tracking of where the security event took place on the network.

M

WNM19 Provide historical tracking of attacks and mitigation processes. HD


33 | P a g e

Ref. # Description



WNM20 Run on either an appliance or virtual infrastructure for scalability

M

WNM21 Support a variety of browsers, including Internet Explorer, Chrome, and Firefox

M

WNM22

Be compatible with all equipment in the Wi-Fi network including the access points, the WLAN controllers, the LAN infrastructure (to include both access and core devices) and any related appliances, such as a mobility service appliance.

M

WNM23

Support a variety of discovery protocols including ping, Cisco Discovery Protocol, Link Layer Discovery Protocol (LLDP), Address Resolution Protocol (ARP), Border Gateway Protocol (BGP), Open Shortest Path First (OSPF), and route table lookups

M

WNM24 Support flexible grouping of network elements into user definable groups

M

WNM25 Support flexible plug and play functionality to simplify the addition of new devices

M

WNM26 Provide tools and features that allow administrators to quickly assess service disruptions, receive notices about performance degradation, research resolutions, and take remedial action

M

WNM27

Provide tools for the configuration of

Access control lists (ACLs)

Routing protocols, including Enhanced Interior Gateway Protocol (EIGRP), Routing Information Protocol (RIP), OSPF, and static routes

Network Address Translation (NAT)

M

WNM28

Provide tools for monitoring

Network availability

Device performance and alerting

Application performance on the network leveraging the latest technologies, such as with NetFlow9 and NBAR2

Video and voice applications on the network

QoS with data regarding QoS policies applied to interfaces and class-based traffic patterns

M

WNM29 Provide switch-port tracing to locate a switch port to which a rogue access point on the wired network is connected and upon identification, disables that port.

HD

WNM30 Provide PCI Assistance Compliance Reporting HD


34 | P a g e

7.8 Wired Network Foundation

Ref. # Description



N1

The wired network shall be designed in a hierarchical topology with full redundancy such that single points of failure are pushed to the very edge of the network. This includes, redundant Core/Distribution switches, power supplies, firewalls, DHCP/DNS appliances, main processors, and links to access layer switches.

M

N2

The wired network shall use a modular design approach such that services delivered to the network like WLAN aggregation & authentication, video, or voice use dedicated network switches that connect to the Core/Distribution with dual load-balancing uplinks. Each uplink bandwidth shall be a minimum of 10Gbps.

M

N3 The wired network shall support fully redundant unicast and multicast routing that can survive a switch or link failure.

M

N4 The wired network shall support Quality of Service (QoS). That is, the marking of traffic on the ingress to the Access Layer and Queuing throughout the network.

M

N5 Access Layer switches shall connect to Core/Distribution switches with dual load-balancing uplinks. Each uplink bandwidth shall be a minimum of 10Gbps.

M

N6 All uplinks should be upgradeable from 1-Gbps to 10-Gbps without a whole Core/Distribution or Access Layer switch replacement.

HD

N7 Access Layer switches shall connect to the APs at a minimum of 1-Gigabits per second (Gbps).

M

N8 Access switches shall support at a minimum 802.1at Power over Ethernet.

M

N9 Access switches should support UPOE Power over Ethernet for future higher power devices.

HD

N10 Access Layer switches shall use Spanning Tree Protocol for loop protection, BPDU guard to prevent disruptions to the network from another switch and broadcast storm protection.

M

N11 Access Layer switches shall provide DHCP IP Helper services for forwarding DHCP requests to the centralized DHCP server.

M

N12

Access Layer switches shall limit the AP-assigned switch port to only allow network access to the assigned AP. An alert shall be sent to a Network Management console when an unauthorized device connects to the AP-assigned port.

M

N13 Firewalls shall be used for protecting network assets. M

N14 The wired network shall have fully redundant Internet connections that can survive an Internet connection or connected router failure.

HD


35 | P a g e

Ref. # Description



N15

The wired network shall be designed using proven best practices to insure network stability and robustness. These include but not limited to using routing protocols, IP address summarization, using Layer 3 for limiting fault-domains to the Access Layer, and VLANs for segregating services.

M

7.9 Service & Support

Ref. # Description



S1

The proposed hardware shall include as a minimum 24x7 phone and email technical support with next-business-day advanced hardware replacement. Software support should include access to the latest maintenance updates

M

S2

Respondent shall provide a set of end-to-end services for planning, designing, implementing, operating, and optimizing the Wireless LAN and wired network solution. This will include configuration of all switches, firewalls, controllers and access points.

M

S3

In a bid to ensure smooth performance and successful operations of the network, the RFP recipient shall be agreeable to providing ongoing system support. The support shall be for end-to-end Wi-Fi network including all network elements and ancillaries.

M

High Density Wi-Fi Infrastructure – RFP Requirements Unified Communications Requirements

36 | P a g e

8 Unified Communications Requirements

8.1 Overview

The Lexington Center Corporation is looking to replace its current telephone and voicemail system with a

complete Unified Communication system. The new Voice Over Internet Protocol (VoIP) solution will

replace existing T1 B1 digital and analog lines, local telecommunications services, long distance services,

voicemail and PBX equipment and telephone handset equipment throughout all venues. The system

should be managed as a single phone system with four-digit dialing extension numbers and capable of

future growth and expansion up to 300 users. The equipment shall be new models in current production.

No remanufactured, reconditioned or demo models will be accepted.

LCC’s Information Technology department will be providing support for UCS. The IT staff is

responsible for internal support of phone system and all its components. Ease of installation, operation,

management and support of new system will be key in the decision making process.

8.2 Scope and Specifications

Respondent must respond to each and every feature and identify whether they comply or do not comply

and identify any and all exceptions. Incomplete submissions may be subject to disqualification.

8.3 Services and System Requirements

8.3.1 Basic Features

Ref. # Description



UA1 Proposed solution must be compatible with Cisco branded switches and infrastructure.

M

UA2 Four digit dialing to all sites on network. M

UA3 Ability to utilize all voicemail features among all users independent of user’s location.

M

UA4 Capable of handling a minimum of thirty-two (32) incoming lines and must be expandable to handle more lines as needed without ‘fork-lift upgrades’.

M

UA5 Ability to function as part of a network with a centralized voicemail system, including the ability to light message waiting indicator lights at each device.

M


37 | P a g e

Ref. # Description



UA6 System must support Direct Inward Dialing as well as Caller-ID for all incoming calls.

M

UA7 All staff phones must have color displays and speakerphone capabilities

M

UA8 System must provide the ability to provide on-hold music or pre-recorded messages at each site.

M

UA9 System must support email integration with Microsoft Outlook 2016 and provide a ‘unified messaging’ solution. Ability to dial directly from Outlook Contacts.

M

UA10 System must be able to provide ability for collaboration and communication services such as instant messaging (IM), voice, video messaging, desktop sharing and conferencing.

M

UA11 System is required to handle forced account code collection (and associated reporting capabilities) for long distance calls.

M

UA12 Integration with Microcall call accounting software. M

UA13 System must provide ability for end user to ‘log in’ at any phone. M

UA14 In the event of outside loss of primary connectivity or power, system must be able to provide fail over dial tone and connectivity internally and externally for designated users.

M

UA15 System must have a method of attaching existing analog phones with minimal cost and effort. Describe method.

M

UA16 System must handle extension forwarding and call transfers to internal phones as well as to user’s cell phone or home phone.

M

UA17 System should allow end users to record calls to their extensions.

HD

UA18 The proposed solution should incorporate an integrated faxing service as a component of its telephony solution. Allows incoming faxes to multiple numbers.

M

UA19 Ability to allow the phone number to be blocked from Caller-ID when placing external calls.

M

UA20 Allow various levels of calling privileges such as long distance and international calls to be programmable by extension.

M


38 | P a g e

Ref. # Description



UA21 Ability to allow a call to be placed by entering an authorization code on an extension that would otherwise be blocked.

M

UA22 The system should be compatible with headsets both wired and Bluetooth for hands free operation.

M

UA23 The system should have Soft Phone technology. M

UA24 The system must provide the ability to include a minimum of three (3) inside or outside callers in a conference call.

M

UA25 System must support definable hunt groups. M

UA26

System must be able to support Automated Call Distributiion (ACD) for phone sales operation. ACD provides queue recording, on-hold music and, if configured, option to leave voicemail instead of remaining on hold.

M

UA27 System should support up to 300 users/phones with ability to expand.

M

UA28 System should support outbound faxing from end user PCs with Outlook integration.

8.3.2 Voicemail Details Required Features

Ref. # Description



UB1 System must be able to request a password or PIN to access user’s voicemail box.

M

UB2 Ability to access voicemail remotely. M

UB3 Must integrate with Microsoft Outlook 2016, voicemails appear as an email with audio attachment.

M

UB4 System must support “zero out” to the system attendant. M


39 | P a g e

Ref. # Description



UB5 System must provide warning notifications when limits are reached in regards to maximum number of minutes or disk space allotted to a single voicemail box..

M

UB6 System must time stamp each call with time and date. M

UB7 System must assign a default password for users and provide method to reset password for users that have been locked out of their mailboxes.

M

UB8 System must be capable of adding or modifying a class of service.

M

UB9 System must allow user to transfer calls to their own or another user’s voicemail box.

M

UB10 System should provide ability for users to change greeting message or password remotely.

M

UB11 System must provide users ability to obtain instructions through system prompts.

M

UB12 System must provide ability to transfer messages to other (multiple) users and append them with their own comments.

M

UB13 System must allow users to modify their own passwords, ability to record multiple greetings for internal and external callers and out-of-office messages.

M

UB14 Ability to perform a backup and restore on voicemail message system.

M

UB15 Ability to support multiple system prompts to greet callers with a ring, no answer message, off hook or a do not disturb message.

M

UB16 Ability to run detailed reports on system utilization by dates, times, extensions, etc.

M

UB17 Ability to record messages, send and mark messages as “urgent”, “private”, etc.

M


40 | P a g e

8.3.3 911 Calling

Ref. # Description



UC1 Allow all devices on network to call 911 to reach emergency services and send the correct address of the site and the handset location.

M

UC2 Ability to notify other extensions of 911 calls and origin of call. M

UC3 System must be able to alert LCC administration of 911 call placed, see their location via email, text and/or display on computer and/or mobile device.

M

8.3.4 Phones and Attendant Console Details Required Features

Ref. # Description



UD1

The proposed solution shall provide an attendant console for servicing incoming calls to the network. The console should feature a simple, uncluttered layout of call appearance keys, attendant function keys and a large, easy to read display.

M

UD2

The proposed solution shall preferable provide SIP compliant phones with flexible support for inline power, local power or closet power. User phones must feature a message waiting indicator light, bridges (multi) line appearance, intercom calling and multiple line appearances.

M

UD3

System must offer paging through the phone system, specifically through the phone speakers. System must offer the ability to mute the speaker so pages do not come through. Paging ability to be limited to certain users.

M

UD4 The proposed phones must provide a built-in switch for PC connectivity.

M

UD5

Attendant console and/or GUI version must display call presence and extension status for all location extensions. Operator/attendant console must provide drag and drop call handling functionality.

M

UD6 System shall display limited call presence information at a minimum for all GUI based user phone consoles.

M


41 | P a g e

Ref. # Description



UD7 If the proposed phones offer programmable buttons, they must be customizable on a per extension basis and not require a global ‘map’ across the enterprise.

M

UD8 Phones should have the option to turn volume on handset up or down.

M

UD9 Ability to access directory of phone number/extensions via the phone instrument display.

M

UD10 Phones should have Bluetooth and headset option for hands free operation.

M

UD11 System should support use of IP Soft Phones. M

UD12 System should include at least three conference style phones with remote microphones.

M

UD13 For bid purposes, include 60 color desk instruments similar to Cisco 8841 and 30 color desk instruments with Bluetooth capability similar to Cisco 8851.

8.3.5 Automated Attendant Required Features

Ref. # Description



UE1 The proposed solution shall provide an automated attendant with a minimum of a three (3) deep tree.

M

UE2 Customer requires a minimum of two separate automated attendants, one for ticketing operation and one for corporate.

M

UE2 The proposed solution shall be able to handle a minimum of thirty-five (35) automated attendant menus with customized recorded announcements.

M


42 | P a g e

8.3.6 System Monitoring and Diagnostics

Ref. # Description



UF1 Describe the remote diagnostics available to administrators. M

UF2

Respondent shall provide a set of end-to-end services for planning, designing, implementing, operating, and optimizing the Wireless LAN and wired network solution. This will include configuration of all switches, firewalls, controllers and access points.

M

UF3 Describe administrator console monitoring capabilities and alarm or alert notifications.

M

8.3.7 System Reporting and Call Detail Reporting and Accounting

Ref. # Description



UG1

Customer currently uses Microcall for call accounting. SMDR

records are transmitted to Microcall call accounting software to

generate billing for long distance charges for clients and guests.

System should either integrate with Microcall accounting

software or have its own capability of billing. Please describe

system call accounting capabilities, if any.

M

UG2 System must be capable of Call Detail Reporting (CDR) in the

form of detailed reports and ability to export call data to

Microsoft Excel. M

High Density Wi-Fi Infrastructure – RFP Requirements Cost and Pricing

43 | P a g e

9 Cost and Pricing

9.1 Bill of Materials (BOM)

At the conclusion of design phase and as part of the complete report, the RFP recipient shall create the

detailed bill of materials for review by the customer and its subsequent approval. Sample templates for

the bill of materials are provided below:

BOM for WiFi Elements

Venue/ Area

Item Name / Part Number

Item Description

Number of Units Unit Cost

Extended

BOM for Network Elements

Venue/ Area


Item Description


Extended

BOM for Ancillary Items

Venue/Area


Item Description


Extended

High Density Wi-Fi Infrastructure – RFP Requirements Cost and Pricing

44 | P a g e

BOM for Optical Fiber and Copper Backhaul

Venue/Area


Item Description


Extended

BOM for Unified Communications

Venue/Area


Item Description


Extended

BOM for Equipment Maintenance Schedule for years 1, 2 and 3.

Venue/Area


Item Description


Extended

9.2 Design Approval

Upon successful completion of the design and dimensioning exercise, the report shall be submitted to the

customer for approval.

The customer will review the report and communicate explicit approval, upon receipt of which

subsequent steps of installation and other activities will commence.

High Density Wi-Fi Infrastructure – RFP Requirements RFP Response Submission

45 | P a g e

10 RFP Response Submission

10.1 Response Due Date

The RFP response is due 9/19/16. Submissions must be received in paper copy and electronic

PDF format (CD or flash drive acceptable). Any submissions received after this date will be

disqualified.

The RFP response shall be address to the following person in a sealed envelope and sent to the

following address:

Lexington Center Corporation

Michael Fox – Wi-Fi/UCS RFP Response

430 West Vine Street

Lexington, Kentucky 40507

10.2 Notification of Award

Following the RFP response submission date, the customer shall evaluate RFP responses and quantify their

qualifications and shortcomings in an objective manner.

RFP recipient may be asked to participate in multiple rounds of discussions to clarify the customer’s

questions and queries and such support shall be extended by the RFP recipient.

Upon completion of evaluation, one or multiple recipients may be chosen by customer. However, customer

reserves the right not to select a winner as a result of this RFP.

lexington center corporation high density wi-fi … · high density wi-fi infrastructure &...

Documents