Avaya TV

The Next Generation of Emergency Services with the eCall Regulation

Today access to emergency services in most countries around the world is mostly voice orientated. As technology advances, emergency services also need to advance. Watch this video featuring Willem Van Alphen, Process Manager from 112 Emergency Services Netherlands.  Learn about the challenges faced day to day and how they plan to seize them as the eCall regulation comes into place in the EU in 2018.


[00:00:01]
>> [MUSIC]

[00:00:08]
[SOUND]

[00:00:10]
[MUSIC]

[00:00:13]
It is a fact that in most countries of the world, access to emergency services is mostly by voice only phone service.

[00:00:20]
[MUSIC]

[00:00:24]
But time is pressing.

[00:00:25]
[MUSIC]

[00:00:27]
Most mobile phone location reporting is inaccurate.

[00:00:30]
[MUSIC]

[00:00:38]
Today's omnichannel-connected world provides data. All used by citizens on a daily basis, but they are not available to public safety in case of an emergency. I'm Willem Van Alphen, Process Manager of the Emergency Number 112 in the Netherlands. Our mission at 112 is to answer all emergency calls that are made in the Netherlands.

[00:01:03]
90% within ten seconds, and, of course, we may not miss one call. The challenges on the call taking of 112 is the heavy fluctuations in volume with big incidents. And the inaccurate location information we sometimes get.

[00:01:20]
[MUSIC]

[00:01:22]
E-Call for the Emergency Number 112 is mandated by the European Parliament. E-Call, of course, will be integrated in our system by 2018, as mandated. And one of the advantages of E-Call is the much accurate location. And that will mitigate our challenge on location information that was very inaccurate until now.

[00:01:44]
The future of the Emergency Number 112 is, of course, data enhancement. Until now, we are very voice oriented.

[00:01:53]
[MUSIC]

[00:02:25]
The future will be challenging for the Emergency Number 112, but we think we are ready for the next step.

[00:02:32]
[MUSIC]
Error: There was a problem processing your request.