Wireless Location Based Services (WLBS) are usually discussed in the areas of customer or guest engagement. However, there are also valuable use cases in the areas of employee engagement and facility safety. The WLBS demo at #AvayaENGAGE in Dubai highlights the employee engagement use case. Further, it demonstrates the power of the Avaya Breeze™ Platform and Unified Communications.
As a real world example … think about a public area, a store, a hotel, school, etc. A window is broken. A call reporting the incident comes to the control center. The controller needs to identify which resources are closest to the event. The closest member of the security team needs to respond to cordon off the area and determine if anyone was injured. A member of the janitorial team needs to be dispatched to clean up the glass and a member of the engineering team needs to respond to temporarily cover the opening and have the glass company implement a replacement.
The WLBS display shows the location of all devices probing the WLAN. The user interface allows the controller to sort displayed devices by role, for instance, eliminating all guest devices from the display or simply displaying the security team members. Further, the device indicators can be color coded based on the role to simplify identification. Once the correct person is identified, they can be selected on the screen, and either sent an SMS or called on their mobile device. This allows the controller to quickly identify the appropriate resource based on their location and contact them to respond to the situation.
For the #AvayaENGAGE Dubai demonstration, Avaya employees are being tracked in the common areas of the pavilion. Information about each employee has been captured in a database, including MAC address, device phone number, name and skill or role at the event. For instance, subject matter experts (SMEs) in Networking, Contact Center, and Unified Communications have been identified. If a guest has a question requiring an SME, the closest SME can be identified and contacted to see if they’re available to answer questions.
The following diagram shows all devices being tracked by the 23 WAPs participating in the WLBS demo. There were 352 guests at the time the screenshot was taken, so most of the circles are light blue. However, if you look closely, you can see a few other colors, such as the dark blue Executive and the tan Network SME. Solid dots indicate the devices are connected to the Avaya WLAN. Hollow dots indicated that the device is probing the network, but not connected to the WLAN.
As you can see, an unfiltered display, while providing crowd level information, isn’t very helpful in finding specific people or skills. The filter selections on the right of the screen provide filtering functions. Displayed devices can be limited to one or more skills or by name.
The next screenshot shows filtering enabled for executives. The dot for Jean Turgeon (JT) was selected. At this point, the operator could select to send an SMS message to JT or call his mobile device.
The WLBS solution consists of three Avaya components:
The WLAN at #AvayaENGAGE Dubai is implemented with Avaya 9144 WAPs. Each 802.1 wireless network client device probes the network every few seconds to determine which WAPs are available to provide service. Every WAP within the broadcast range of the network device will detect and respond to the probe message. The probe and response messages enable better network service, particularly when the device is moving and needs to change WAPs to get better service. The probe messages are done at the MAC level, therefore, each WAP in the broadcast area receives a message from every MAC address in range every few seconds.
When location services are enabled in the 9100 WAP (simple non-disruptive change via web interface or profile update in Avaya WLAN Orchestration System), each WAP sends the MAC address and distance information to a network address. In this demo, the information is sent to a Avaya Snap-in that collects the data from all of the WAPs, sorts the data based on MAC address and runs the data through a triangulation algorithm to calculate the location of the client device based on the known locations of the WAPs.
A second Avaya Snap-in manages device identity management. This Snap-in could work with something like Avaya Identity Engines to provide user information for the MAC addresses detected by the WAPs. Since the #AvayaENGAGE Dubai demo is a temporary environment, the Snap-in simply provides the ability to load a CSV (comma-separated value) file with the Avaya employee information. This provides the ability to map Avaya employee identities to the MAC addresses of their mobile devices.
The user interface Snap-in provides the display shown above. It takes the output from the triangulation Snap-in and displays it on a map in a Web browser window. It also uses information in the identity Snap-in to sort devices owned by Avaya employees vs. Engage guests, hotel employees and other hotel guests. The skill classification captured in the CSV file enables finer level filtering and skill based color indication on the screen.
When the icon for an employee on the map is selected, the pop-up frame shown above appears. Communication to the Avaya employees is performed via the Zang cloud-based communication platform. When the user selects the SMS button shown above, a screen appears to enter the message, which is sent to the Zang service which then sends to the employee’s device. If the Call button is selected, the Zang service initiates a phone call between the number shown in the Call-me-at field above and the Avaya employee’s phone number listed in the CSV import.
I’d like to say this is rocket science, but the Avaya infrastructure components and Avaya Breeze make it straight-forward architecture. Avaya believes a key to scalability is putting power in the edge devices to minimize back haul data, but also to simplify management. The intelligence of the AOS software running in the 9100s makes it simple to collect device location information. The Breeze Platform provides a full JAVA-based programing environment with object classes for Avaya communication product functionality. Finally, Zang was designed for business people to be able to programmatically integrate communication functionality into business processes without a major investment in infrastructure or expertise.
Keep watching this space. We’re already planning for the WLBS Demo at Avaya Engage 2017, in Las Vegas, February 12-15.