California cold feet on E911 Legislation?

This Avaya CONNECTED Blog
is also available as an MP3 Audio File


CPUC-MLTS Logo.pngIt’s no great secret that for several years now California has been touted as being very progressive with its E911 legislation. After initial Public Utilities Commission hearings in 2010, Bill A.B. 911 has recently been moving forward at lightning speed as it navigates its way through the legislative process.

A few weeks back, the bill was put into “SUSPENSE,” and today a Senate Appropriations Committee Fiscal Summary Bill Analysis was published on the California PUC website explaining the reasoning for this change.

Cue the suspenseful music!

The analysis reports a change to the Fiscal Impact (as proposed to be amended):
“Unknown one time costs, possibly in the hundreds of thousands to millions of dollars, from General Fund and various special funds to replace and update any ML TS system owned and operated by the state to be able to transmit the required information with 911 calls.”

As proposed, the bill would go into effect on January 1, 2016, and would require that the MLTS be operated and maintained so that dialing 911, or 911 and any additional digit for access codes (9 for example), route the caller to the PSAP with the “automatic display of the callers number address and location of the phone.”

161-5Percent-iStock_000014802700XSmall.jpgAs stated earlier in the PUC report, only a small fraction of companies would be affected by this new legislation, however that would account for a large majority of constituents that are serviced by these systems. The report documents that 95% of the 1.3 million businesses and government agencies within California would actually be exempt from this legislation, and the remaining 65,000 businesses “employ 9,521,366 Californians or 60.5% of the California workforce and serve countless visitors, customers, clients and tourists, are the business MLTS customers and end-users that require this critical E9-1-1 emergency services protection and would benefit from Enhanced 9-1-1 legislative mandate.”

Part of the issue here is that, despite the data presented during the PUC workshop in 2010, there is still a perception that 911 remediation is a costly undertaking for an MLTS environment. It is also clear that some of the base guidelines that are stated in the NENA MLTS Model Legislation document have not been taken into consideration. For example, requiring station level reporting to the PSAP becomes the burden for enterprises when implementing an E911 solution. Many stations within the enterprise do not have their own individual direct inward dial telephone number, and an organization with several thousand telephone instruments could be challenged with the operational costs managing locations at the individual device level.

As the NENA model legislation states, zone level reporting with the appropriate on-site notification mechanisms is adequate when establishing emergency response plans for a particular address. This reduces the complexity of the solution, as well as eliminates the ongoing and costly maintenance of the carrier PS-ALI database, which can now become static. Based on Avaya’s experience, eliminating this complexity not only reduces cost, but improves the chances of systems actually being implemented to where they will do some good. Let’s face it, you can have the best solution possible but if no one uses it, it’s worthless.

While I’m a proponent for legislation around E911 services in the enterprise, I do not believe in legislation that doesn’t actually solve the problem. California has an excellent opportunity to follow in the footsteps of states like Michigan, Massachusetts, Virginia, and the 15 other states that have implemented legislation and guidance around emergency services and multiline telephone systems.

Adopting this legislation, without clarification on zone level reporting requirements would be a huge mistake, now or in the future, and delaying the implementation of this bill until 2017 serves no purpose whatsoever. If there was a level of concern over requiring existing implementations enough time to evaluate and become compliant, there is always the proverbial “grandfather clause” that would allow existing systems to operate for an extended period of time past the implementation of the bill. New systems purchased on or after that date would require compliance, with of course a six month window at the beginning of the bill effective date to allow those businesses with construction plans already in place a short grace period.

martha.pngAPN Legal Correspondent Martha Buyer says, “There’s an old adage about never wanting to watch either legislation or sausage being made. My suspicion is that lobbyists got in the middle of this draft legislation and convinced the bill’s author and those supporting it, that the requested change was paramount to its adoption. Unfortunately, in the course of modifying the legislation to appease someone, the teeth–and effectiveness–may have been removed. At the end of the day, E911 legislation is all about safety and protecting people. Employers, who may have lobbied against an additional regulatory burden, may be unaware that they continue to have exposure, with or without legislation, for creating and maintaining a safe workplace, both for employees and guests.”

Again, most systems today will provide some level of 911 location granularity and reporting. This is not new to the industry, and we’ve worked closely with our DevConnect community to make it available several different solutions, at several different levels of functionality, and several price points which are nowhere near the costs indicated in the recent Bill Analysis.


Want more Technology, News and Information from Avaya? Be sure to check out the Avaya Podcast Network landing page at http://avaya.com/APN . There you will find additional Podcasts from Industry Events such as Avaya Evolutions and INTEROP, as well as other informative series by the APN Staff.

APN Blog Banner

Thanks for stopping by and reading the Avaya CONNECTED Blog on E9-1-1, I value your opinions, so please feel free to comment below or if you prefer, you can email me privately.

Public comments, suggestions, corrections and loose change is all graciously accepted 😉
Until next week. . . dial carefully.

Be sure to follow me on Twitter @Fletch911

Fletch_Sig.png 


CacheFly LogoAPN is Powered by Cachefly
CacheFly is the world’s fastest CDN, delivering rich-media content up to 10x faster than traditional delivery methods. With a proven track record and over a decade’s worth of CDN experience, companies around the world choose the CacheFly CDN for reliable and unbeatable performance. For more information, visit www.cachefly.com

Related Articles:

Check out the Cool Avaya Omnichannel Contact Center Demos at ICMI

Sometimes you travel to Orlando to really fun destinations. But this May 22-25, when you arrive in Orlando for the 2017 ICMI Contact Center Expo and Conference, we think you’ll be heading for what we like to call the second happiest place on earth. Visit Avaya’s Booth 623 for a fun omnichannel contact center experience that shows you how to create satisfaction—happiness—for customers throughout their interactions with your company.

Each year, contact center executives gather for a few days of education on the latest innovations designed to ensure customers have a great experience. I might not meet up with Mickey from Disney, but I may get together with Alex from Norwegian Cruise Lines, an Avaya customer, and many others who are going to have a wild ride at our cool contact center demos. We’ll show customer-focused companies our latest innovations. This includes the Avaya Oceana™ Solution for contact centers, which enables you to provide a greater customer experience over every communications channel—phone, email, web, SMS, chat, and more. And Avaya Aura® Workforce Optimization, which helps you drive a better customer experience by generating relevant and timely insights from each interaction.

At our demos, we believe customer service professionals will be as excited as kids visiting Goofy. Why? With just five minutes of prep, we can put your corporate website into our Avaya Oceana contact center transformation demo. We’ll set up a live, fully functional omnichannel contact center for taking calls and chat sessions from your website. It’s like magic to see a retail website suddenly support chat and WebRTC-based voice. We show you the exact experience your customers would have. Want to add voice? Will do. How about co-browsing and secured form fill? Done. How about a custom application for the iPhone? Done and fun!

Then we’ll add in our workforce optimization tools, giving you a 360-degree view of how to move from the old world of 800 numbers to the new world of a multi-touch omnichannel contact center. It all works with all of our Avaya solutions (which are used by 90% of the Fortune 100). It’s a great ride—with no height restrictions and guaranteed to be eye opening.

Visiting an Avaya booth at any tradeshow is a unique experience for many reasons:

  • Each demonstration we do is customized. The best way to show you the power of Avaya is to give you a glimpse into what your actual solution could be. If a vendor shows a canned demo, it might be an indication that the technology is not flexible or easy to customize.
  • Each demo shows multi-touch channels in action. Click on a live representation of your company’s mobile application and it connects to an agent. Follow the experience like your customers would.
  • We show the entire customer experience. A customer journey map shows the entire customer experience so that agents can add value to previous transactions and steps. By knowing what a customer has done in the past, or what a customer tried to do, an agent can be one step ahead with a relevant response.
    If a customer chatted with an agent yesterday and places a phone call today, it’s likely that both contacts are about the same transaction. An agent can see what information was exchanged with another agent, so the current agent can continue the customer journey fluidly. It’s a great way to reduce agent time requirements, while making the customer experience more personalized.
  • We are passionate about making a difference for your business. Meet an Avaya team with years of contact center experience and dedicated to helping your company create a competitive differentiation by transforming your customer experience.

We hope to see you at the ICMI Contact Center and Exhibition in Booth 623. We’ll have you saying “supercalifragilisticexpialidocious!” (Did you know Microsoft Word has supercalifragilisticexpialidocious in the dictionary?)

If you can’t make it to a show, an Avaya associate or partner can demo our solutions in person or online. To schedule a demonstration at the ICMI event or at another time, please email me at blgutnick@avaya.com.

Secure IoT Deployments with Avaya SDN Fx™ Architecture Solutions

Let’s look at how to deploy the IoT in a safe and sane manner—a top-of-mind business challenge. Before diving into the technology, let’s remember why secure IoT deployments are so important. The Yahoo breach is a lesson learned: Yahoo CEO Marissa Mayer lost $12M in bonuses over the Yahoo data breach and Yahoo paid $16M to investigate the breach and cover legal expenses as of March 2, 1017. It’s clear that the cost of not building a safe infrastructure is much more than the cost to build one.

Software Defined Networking (SDN) is sometimes over-hyped. At a base level, separating the control plane from the data plane makes sense (if one understands the definitions of a data plane and control plane). In a practical sense, it means the network infrastructure doesn’t need to be managed on a node-by-node basis (i.e., logging into network devices on each end of the cable to make complementary changes to configure a network link). This is where SDN can be over-hyped. The SDN solution automates the process of making the changes to each end of the cable, making the network easier to manage. But, it doesn’t reduce the complexity, increase the resiliency (other than reduce outages due to typing errors), or make it easier to troubleshoot or expand.

Avaya SDN FxTM Architecture is based on fabric, not network technology. The architecture was designed to be managed as an entity of subcomponents and not a bunch of nodes that are interconnected to create a larger entity. In other words, it’s like designing something to manage a forest, as opposed to managing the trees. Would you really want to manage a forest one tree at a time?

How SDN Fx Architecture Benefits the IoT

Although the SDN Fx network architecture wasn’t specifically designed for the IoT, it works well for providing a solid foundation to deploy IoT solutions. These are the key components of the SDN Fx Architecture that benefit the IoT:

Avaya Fabric Connect is Avaya’s implementation of Shortest Path Bridging (SPB/IEEE 802.1aq). SPB replaces the traditional network stack, greatly simplifying network configuration, management and security. Three key benefits of Fabric Connect apply directly to IoT deployment use case:

  • Hyper-Segmentation: SPB supports 16 million+ network segments. In theory, every IoT device on a network could have its own segment. More realistically, every device type can have its own segment. For instance, HVAC could be one network, security cameras could be on another, employees on a third, guests on a fourth, etc. It’s worth noting that the NSA sees segmenting IoT networks as a key to limiting exposure of IoT deployments. (In my next blog, I’ll examine how Avaya solutions provide security between devices on the same segment.)
  • Automatic Elasticity: Services in SPB are provisioned at the edge without touching the core of the network. This makes it very straightforward to provision network services for the hundreds or thousands of IoT devices that the business wants up and running yesterday. Plus, edge provisioning makes moving devices simple. When a device is disconnected from the network, the network service to that port is disabled and eliminates open holes in the network security. When the device is connected to the same or different port, the device is authenticated and services are automatically configured for the port.
  • Native Stealth: SPB operates at the Ethernet, not the IP layer. For example, if a would-be hacker gains access to one segment of a traditional network, they can go IP-snooping to discover the network architecture. A traditional network is only as secure as the least secure segment/component. With Fabric Connect, if a security loophole is overlooked in a less important network project, there isn’t a back door to access the rest of the network and the corporate data.

Avaya Fabric Extend provides the ability to extend an SPB fabric across a non-fabric network, such as IP core, between campuses over Multiprotocol Label Switching (MPLS), or out to the cloud over WAN. IoT deployments enable the phased adoption of SDN Fx so that IoT projects can gain the values above, without ripping and replacing significant network infrastructure or affecting non-IoT workloads.

Avaya Fabric Attach automates the elasticity of the SPB fabric for IoT devices and other devices supporting Automatic Attachment (IEEE 802.1Qcj). Fabric Attach allows the device to signal the network that it needs in order to connect to a service. If the device is authorized, the service is automatically provisioned. When the device is disconnected, the service is terminated. If the device is moved to a different network port, the service will be provisioned automatically to the new port. This makes deploying and moving Fabric Attach-enabled devices very simple. For a real-world example, see how Axis Communications is starting to deploy Fabric Attach in their IoT devices.

Avaya Open Networking Adapters—an Open Network Adapter is a small device that sits in-line with an IoT device to provide programmable security for IoT devices that lack adequate network security. One component of the solution is Fabric Attach, which provides automated service provisioning and mobility to devices that don’t have the auto-attach capability. (I’ll explore more about the power of Open Networking Adapters in an upcoming blog.)

The Avaya Identity Engines Portfolio provides powerful tools for managing user and device access to a network, commonly referred to as Authentication, Authorization, and Accounting. In the IoT use case, Identity Engines authenticate a device by MAC address or MAC address group and use predefined policies for the device type to dynamically configure services. For instance, a camera could be assigned to Video VLAN 30 and provisioned for multicast, while a phone would be authenticated, assigned to VLAN 20, and configured for SIP communications. This provides security for unauthorized devices joining the network and provides automatic segmentation based on device type and service requirements.

I’m not sure if there ever was a time when network design and implementation was static, but there was a time when the devices connected to the network could be predicted: servers, printers, storage, PCs, etc. With IoT, IT is being asked to design networks for devices that haven’t been thought of yet. The old network technologies were designed for mobility by work order, and IT was able to list the number of device types that wouldn’t work on the network. SDN Fx provides a true software-defined network and not software-defined automation on old network constructs. A fabric network has the intrinsic flexibility and security required for tomorrow’s IoT projects, today.

In my recent blogs about the IoT, I’ve looked at how the IoT enables Digital Transformation and examined a business-first approach to IoT technology adoption. Next in this blog series, I’ll explore the newest component of the SDN Fx solution for the IoT, the Avaya Surge™ Solution.

Customer Journey Analytics vs. Traditional Analytics—Know the Difference

It’s expected that 60% of all large organizations will develop customer journey mapping capabilities by 2018. Why? Because the average consumer isn’t so average anymore. Consider that a typical customer now owns three personal mobile devices, each with anywhere from 10 to 20 downloaded apps. This individual owns an average of five social media accounts, nearly three of which are actively used. Additionally, the average office worker receives up to 121 personal emails per day. Just imagine what these figures look like for consumers on the high end of this engagement spectrum.

To get a snapshot of my own activity, I followed these simple instructions to figure out how many emails I receive. It’s 10 a.m. and I show 59 emails received (up from 47 just two minutes ago). And tweets average around 6,000 per second—I have 1,175 in my queue based on who I am currently following. The question is: How do you bring your email, tweet, post, or blog to my attention amid all the clutter?

When we look at what this means to customer experience it is worth noting that we’ve reached a point where over 40% of customers now use up to seven different channels to interact with brands, from live chat to email to social media to SMS. Businesses increasingly understand this fact, and they’re taking the necessary steps to ensure they can deliver consistent, contextualized experiences across various channels and devices.

Each of the devices and channels offers its own set of diverse scenarios for linking to other devices and channels, making no two customer experiences the same. The not-so-good news is that businesses are still grappling to understand customers’ actions across these various touchpoints. They need to leverage data but, in fact, 43% of companies currently obtain little tangible benefit from their data, while 23% admit they derive no benefit whatsoever. Organizations are struggling to create a data strategy that delivers the insights needed to drive anticipatory engagement and repeat spending.

The bottom line is that a business can support virtually every interaction channel. However, without a comprehensive view of the data generated and shared across those channels organization-wide, it will fail. Supporting an array of channels is simply not enough. Businesses must gain an inherent understanding of how customers are using these channels so that they can adapt, evolve and change as needed. This is where the ability to understand your data—specifically, customer journey analytics—becomes vital.

The solution here may be simple to describe, but implementing it isn’t. Adopting customer journey analytics means businesses must now support a powerful, real-time visualization of the customer journey across all lines of business, not just the contact center. They need a roadmap to continually reinvent key processes and fine-tune organizational behavior. They must harness real-time and historical data across all channels and devices to intuitively understand customer needs and optimize business outcomes. Most challenging of all, they must do this in a way that shows tangible ROI and improves TCO.

To make customer journey analytics work, businesses must take a critical step from ideology to implementation—a move that can often feel like a leap of faith.

But there’s good news: technology has evolved to a point where companies can now easily, effectively and cost-efficiently achieve these core data objectives. The key is investing in an extensible, omnichannel customer engagement solution.

Your customer engagement solution should boast simple capabilities. It should be pretty easy to create and manage dynamic, multi-touch customer journeys. And you need a built-in, flexible analytics and reporting platform to deliver a single, comprehensive view of customer data across all sources, both internal and external. This lets you compete using customer journey analytics, and also easily add third-party data sources to amplify their strategy.

A customer engagement platform redefines the way businesses engage with digital consumers. Here’s how customer journey analytics stand apart from traditional reporting and analytics:

  • Obliterates Siloes: A siloed environment is the greatest barrier to data success, and it’s affecting more businesses than we realize. According to Deloitte’s 2017 “Contact Center Benchmarking Report,” nearly 60% of customer channels are currently being managed in silos. Analytics integration is vital for competing on customer experience (CX), an initiative that traditional analytics tools simply can’t support.
     

    Built on open, extensible architecture, a customer engagement platform has unparalleled flexibility for gathering transactional information from numerous different channels (IM, co-browsing, SMS, phone, email, IoT) and devices (phone, mobile/tablets, branch, desktop, kiosks). This enables companies to flexibly collect, process and analyze all real-time and historical data. They gain a rich visualization of their customer journey enterprise-wide. This means consistent, contextualized experiences no matter where and when interactions begin, end, continue—and no matter how many company agents are communicating with the customer.

  • Seamlessly combines internal and external data sources: The open nature of a customer engagement platform enables companies to combine internal data with that of virtually any other business intelligence (BI) tool. For example, insights collected internally can be combined with data from visualization tools from leading providers like MicroStrategy, Oracle, SAP and Tableau. This lets managers maximize the return on their existing investments, while driving their potential beyond what was initially imagined.
     

    Furthermore, this unique ability lets managers generate cradle-to-grave customer interaction reports, enabling them to identify innovative new ways to meet consumers’ evolving needs. Chances are you’re not going to get this with traditional reporting and analytics platforms.

  • Transforms the agent experience: A holistic customer engagement platform redefines agent and supervisor experiences by allowing companies to easily create, customize and integrate key applications for specific work groups. Supported by an advanced software development kit, companies can build their own contact center apps, or embed specific functions into their existing apps, to customize desktops for any unique customer/agent configuration. The solution represents a revolutionary way to serve digital consumers. And, it offers managers a new avenue for analyzing performance metrics for all ways customers are served.

With customers using more digital channels than ever, it’s clear that now is the time to adopt customer journey analytics via a customer engagement platform.

Interested in learning more or chatting about transforming your analytics environment? Contact us. We’re here to help and would love to hear from you.