Lehigh Carbon NG911 / E911 Review

Enterprise 9-1-1: Roadmap to campus safety

Mark J. Fletcher, ENPChief Architect Worldwide Public Safety Solutions

© 2013 Avaya Inc. All rights reserved. 22

Current Legislative Driver - MLTS Late Breaking News!


Avaya’s Message to Customers

Next Generation Emergency Services have been clearly defined in both the US (NENA 08-003) and Europe (NG112-LTD)

Enterprise administrators must look to the future when designing emergency services for users in their networks

Building a NENA i3 compliant architecture is the recommended decision from a technology and investment perspective

Avaya DevConnect Partners that have followed best practices and guidance set forth by Avaya’s strategy and thought leadership in the industry, are are able to provide resilient, life safety solutions that are fully compliant, and in lockstep, with the Next

Generation Emergency Service standards of tomorrow, effectively future proofing the customer’s emergency communications infrastructure investments today.

Mark J. Fletcher, ENPChief Architect

Avaya Worldwide Public Safety Solutions


THE PROBLEM TODAY:

LEGACY ANALOG BASED E9-1-1ANI/ALI DATABASES ARE IRRELEVANT


908-848-1000

AVAYA211 Mt AiryBasking Ridge, NJ

E911Selective Router

PSAP

MSAG

PS-ALI

ALI

PSTN

THE PROBLEM – 911 is Routed Based on Caller ID (ANI)

Call Server / PBX

908-848-2604

908-848-2601

908-848-2602

908-848-2603

908-848-2605

908-848-2606

908-848-2607

908-848-2602Good CLID

908-848-1000Screened CLID

Often the Carrier will MODIFY THIS before it is sent to Public Safety

PSAP

Solutions that manage the PS-ALI database can’t fix this.


Location Discovery

Understanding where the emergency is occurring is the key piece of information required to provide assistance.

BUT, where do I get that data?

What E9-1-1 Functionality is required today?


Some will say “Get it from the PBX . . . .“

TDM Not Discoverable on Network

MAC Work Needs Change Management

Proprietary IP User Moveable

May be located off network (VPN)

SIP Often behind SBC for security

May not report MAC Address

May be a BYOD device with several instances

IN AN EMERGENCY, THE PHONE NUMBER OF THE DEVICE IS NOT APPLICABLE IN TODAY’S NOMADIC ENVIRONMENTTHE DEVICE ID (MAC) AND THE LOCATION OF THE DEVICE IS THE KEY PIECE OF INFORMTION


Others will say “Get it from the NETWORK . . . .“

WHILE DURING THE PLANNING PHASE, THIS IS PROBABLY WHAT YOU THOUGHT YOU BOUGHT


Others will say “Get it from the NETWORK . . . .“

IN REALITY . . . THIS IS WHAT YOU PROBABLY HAVE NOW


Data Correlation

Fletch just made a 9-1-1 call

Someone needs to see if Fletch is alright.

Fletch just made a 9-1-1 call AND

The ambient temperature near Fletch is 227 degrees!

Someone needs to see if Sean is ON FIRE.



Proper Routing

Fletch just made a 9-1-1 call from his VPN phone

Fletch is 3 States away, we have no trunks there.

Fletch just called 9-1-1 from his VPN phone

Fletch is NOT on the corporate LAN and needs to be routed to a VPC.

Someone needs to see if Fletch is ON FIRE, again.



In addition to the PBX having data, what about:– LDAP

– HR Databases

– Directories

– Maps

– Cable Plant

Does mail get delivered to your cubicle?

Chances are you already have the information you need to locate someone in the building

Identify the problem . . . Then fix it

Graphic © Copyright and courtesy Scott Brinker @chiefmartec http://www/chiefmartec.com


The REAL problem is “How do I send additional data to the PSAP?”

SIMPLE – YOU CAN’T

Instead of worrying about a problem you can not solve, concentrate on eliminating the problems you CAN solve.

Remember the 3 main problems:

1.) Location – Someone has to be able to find you

2.) Routing – You need to get to the right agency

3.) ON SITE NOTIFICATION – Help is on the way, and you are ready to help


Location granularity INTERNALLY

Affordable technology exists that provides information to designated personnel on site:– Emergency Response Teams

– Designated Safety Officers

– Building Security

Data that can be provided includes– Floor Plans

– HazMat information

– Proxy to IP Video Feeds

What about After Hours?Many new applications will provide an output to a wall display

that can be located in a building lobby providing direction to first responders.


Clouds provide routing – Not On Site Notification

Enterprises could become isolated from services 100% in the cloud

100% Cloud based solutions may be isolated from the Enterprise


NG911 Data to the PSAP TODAY Over The Top of the Legacy 911 Network

• NENA 08-003 V2 ALDR / ACDR Functional Elements

• Preparing to switch to NG911 (there is no transition)


•Enterprise customers have advanced networks

•Enterprise Location Management (ELM) servers in the DMZ provide information about:

• Users• Devices• Location• Environmental Data• Event Correlation

•Emergency Call to PSAP•PIDF Location Object as DATA in SIP header•Retrieval of Call Specific Information via URL

NG9-1-1 BEYOND TOMORROW:Location URI/URL conveyed in the SIP header

Delivering Advanced Information to NG9-1-1


Because we are delivering detailed location information via SIP with the call . . . .

ANI and ALI databases are NO LONGER REQUIRED Nor is their management and monthly fees. The data PSAPs want is:

•Floorplans•Environmental Data•Video Feeds•HazMat Material Safety Data Sheets•Personal Medical Information (if the user allows)

Whatever solution customers buy today, must be ready to take on this new role in the future. Don’t buy legacy ‘fire sale’ technology

NG9-1-1 BEYOND TOMORROW:Location URI/URL conveyed in the SIP header

What’s Missing from this NG9-1-1 Picture?


NENA 08-003 V2 ALDR / ACDR Functional Elements

•NENA 08-003 V2 ALDR / ACDR* servers in the DMZ provide information about:

• Users• Devices• Location• Environmental Data• Event Correlation

•Additional information reference URL/URI is sent in the SIP header with a pointer to the Enterprise data relevant to the emergency call.

1. Additional Data Sent in SIP Header2. Data examined by network and PSAP for routing 3. Additional Data retrieved from the Enterprise

* NENA 08-003 V2 Functional ElementsALDR - Additional Location Data RepositoryACDR - Additional Caller Data Repository


There is NO migration to NG9-1-1

Just as there was no ‘migration’ from Rotary to Touch-Tone

Just as there was no ‘migration’ from Analog to Digital

Just as there was no ‘migration’ from Digital to IP

Just as there was no ‘migration’ from IP to SIP

Moving to NG9-1-1 will take data from your network and send it to Public Safety.

Today you will collect that data internally. When the NG9-1-1 is ready in your area, you will simply send it via SIP to the ESInet.

You can get ready today. The data formats are published, and data aggregators like Smart911 are ready to take your input now.


Best practices for your deployment - Must Have Features

No single Point of Failure

Full support of the Emergency Services functions in the Call Server

Devices and applications must connect via the approved and supported interoperability points as defined by the Avaya DevConnect program and Product Managers.

Defined roadmap to NG911 integration with NENA 08-003 V2 requirements and support for Additional Data Repository (ADLR / ACDR) functionality.

Enterprise Network Data

NG9-1-1 PSAP


Best practices for your deployment – Should Have Features

Licensing should be flexible to support a variety of configurations/devices

Virtualized solution using VMware or Equivalent

High availability architecture. Application failure should alert/report

High Availability can be achieved through hardware or Virtual Machine

Event correlation of other data with active 911 call events and sensory feeds

NG9-1-1 Solution

Flexible Licensing

Virtual Machine Based

High Availability


Best practices for your deployment – Nice to Have Functions

On Site Notification with zone based routing

On Site Notification with alert escalation on no response

Multi-modal notification including email, pager and IM

API Integration to/from alternative data sources DATA

SENT TO PSAP

Enviro Sensor Data

Video Feed

Personal Data


The moral of the story . . . . .

E9-1-1 / NG9-1-1 is NOT a magic box that you plug in and walk away from

Understand what’s really required– Categorize users and define functionality needed

– Some users need special services that others do not

Understand who actually requires the information and when – Public safety needs to get to the right building

– When they arrive, further instructions can be provided

Understand how it can be delivered– Getting the data ready in a format that is legible is key

– When NG9-1-1 is available, turn on the data flow


Thanks for your time today!

Any Questions?

RESOURCES For Additional Information

Avaya’s Public Safety Page http://www.avaya/PublicSafetyFletch’s CONNECTED Blog http://Avaya.com/FletcherFletch’s E911 Talk Podcast http://Fletch.TVFletch’s YouTube Channel http://YouTube.com/Fletch911TV

Avaya Podcast Network

http://avaya.com/APN

Technology

Lehigh Carbon NG911 / E911 Review