How to gather WiFi requirements

If we prepare well, an excellent WiFi service and a happy customer should follow.

So what is involved in preparation to deliver an enterprise-grade Wireless service?

  1. Information and Requirements gathering (this blogpost)
  2. Wireless Design
  3. Wireless Deployment & Testing

The below is a list of things I consider are absolutely key to understand before being able to move to the next step: designing the customer’s WiFi service.

The first engagement is usually a sit-down with the customer to understand what they want to achieve by installing an (enterprise-grade) WiFi service; understand their outcome expectations and to flesh out business and technical requirements. A heads up, the ‘outcome expectations’ can be a long conversation, as it should be.

Site Environment. We will discuss the site environments in the first meeting but we still need to get on-premise at some stage. Wall materials, ceiling heights, external and internal interference, numbers and density of users and more. It will entail at least one site inspection followed by one or more site surveys. The outcomes from these site surveys provide detailed information in order that we can plan the design.

Numbers of users accessing the service. How many users? Are the users clumped together in one main area or spread evenly across an area?

Types of applications used over the service. Find out the critical business applications to be prioritised and the resource requirements of these apps.  We will need to estimate numbers of simultaneous users.

Types of technology accessing the service.  Each device has different behaviour and different capability sets when using wireless.  It’s not just about which 802.11 standard it supports.

Existing wireless – some or all of it may need to be removed. If some of the current Access Point placement is going to be maintained, we can re-use the existing infrastructure cabling = cost + time savings. Ta Dah!

PoE switch port availability. Enough PoE (Power over Ethernet) ports to supply power to all Access Points. Some vendors’ Access Points require extra grunt. PoE+ power rather than PoE. Check the customer’s switch fleet to see what is supported.

10GbE port availability. Some wireless vendors use wireless controllers that, in a chosen architecture, will require 10GbE interfaces to be utilised.

Preferred vendor. If customer has one. Some customers or their service providers will only work with a particular manufacturer. Vendor selection impacts the design phase as WiFi vendors diverge in their approach to deliver an enterprise-grade WiFi service.

Backhaul bandwidth. Calculations must consider bandwidth both per individual site and the aggregate to data centres/Internet. If creating an extra 300Mbps of sustained traffic for an event, then perhaps the existing 20 Megabit pipes to the site will not cut it.

Guest service. This sets off its own subset of requirements:

Presentation of the Guest service: some organisations require some legal Ts & Cs to be accepted by a Guest before allowing public access. Some will want to present logos or advertise something in a captive web portal. Some will wish to charge for access.

Where is Guest WiFi to be available in the organisation? Only at head office meeting rooms, only in cafe areas?

Guest on-boarding, security and network access. How do Guests receive their access credentials, how long are they allowed on the network, any bandwidth restrictions? In addition, there maybe separate levels of Guest use depending on the type of guest. Trusted contractor versus general public for example.

BYOD. If using BYOD, hopefully there’s already a framework in place to determine who is allowed to access what, from which device. If the BYOD device type isn’t standardised  then we will make general assumptions about capability and tackle individual issues as they come up.

Security Requirements. This conversation is more about how to authenticate authorised users than type of encryption.

Application Visibility and Control (AVC) and Reporting. If the customer hasn’t had insight into what applications are going over their network before now, then they are in for a treat. AVC also provides the network with the ability to prioritise critical business apps over non-critical traffic, e.g. social media.

Support. Who will support the user community? Are they experienced at troubleshooting WiFi? Is training required?

Management. How the wireless infrastructure will be integrated into the organisation’s existing ICT management toolsets: alerting, reporting, maintenance, asset and lifecycle management.

At the end of this, Network Architects are armed with much of the information we need to begin design. For larger organisations, with multiple locations, it is just the beginning of perhaps months of work of site surveys and site analysis.

Site surveys will always uncover challenges, which is why we do them. At the end of a recent site survey, I found the office tenants below and above my customer were using 80MHz wide channels. Thank you. Thank you for messing up the spectrum for everyone. But also, sorry for what I’m going to do to your 80MHz channels when I turn my 27 APs on.

 

 

A simple BYOD definition

We all know what it stands for but what is it really?

BYOD is a company defined set of policies, applied to the network infrastructure.

Together these policies or framework, control access to different areas of your company network depending on the who/what/where scenario: who’s asking, what device they’re using and the location they’re using the device at.

For example, a corporate-issued laptop accessing the network from within the office.  Usually, full access to company resources.  Personal smartphone over a public Wi-Fi hotspot?  This may have some restrictions.

For organisations, their decision to introduce a BYOD framework comes down to a balance of improved productivity vs cost of implementation/integration and the higher risk of loss of sensitive data.

 

Business Agility and Wi-Fi

Often in business, time = money.

In a competitive market, a business must stay agile; whether it is rapid development of new ideas to open new markets, reaction to competitive threats, or using new intelligence gained from data mining (Big Data) to improve their market share.

For a business to be agile in supporting the primary business objectives, technology is considered more and more of a competitive advantage but only if it can enable the toolsets (applications and infrastructure for example) needed by staff.

The computer network is enablement.  This is not to say it is more important than any other business asset;  just that we all know what happens when the network goes down.  Productivity stops. People complain.  Customer Service is impacted.

Wi-Fi has shown that it can improve productivity in the workplace.  Staff have the flexibility to move around the office or campus environments.  By not being tied to their desks they are able to participate and work where and when required; improving not only productivity but often staff satisfaction/morale and staff retention.  It takes less time to install a wireless network than to run wired infrastructure cabling throughout a building – it is certainly cheaper – hence the office is available earlier and the business of doing business is accelerated.

BYOD devices such as tablets and Smartphones drive Wi-Fi adoption in business even further.

The ‘consumerisation’ revolution has been elevated largely through maturing Wi-Fi technology.  iPads in hotel rooms for guests to order services, restaurant waiters with Wi-Fi connected devices to order reliably,  immediately and error-free, self-registration through your smartphone at events…Companies or organisations are constantly innovating using technology over the Wi-Fi network to showcase new services and/or new products.

I see Wi-Fi as a true enabler of improved agility in today’s business environment.

When Wi-Fi is professionally designed and implemented, it will always be there. Invisible, reliable and immediate, like turning on a light switch.