4.7Netherlands
In the current PSAP voice and data are recorded. Actual operational data can be viewed by a supervisor or real time on performance monitors. Historical data is available in a management information system. At the 112 PSAP data is logged automatically. Police, Fire Brigade and Ambulance have to log manual in their incident report system.
The data collected by the 112 PSAP call taker and by the Emergency Agencies (relevant only for mobile calls):
Table : Case file Data (Netherlands)
Data
|
112 PSAP
|
Police
|
Fire brigade
|
Ambulance
|
Name
|
1
|
X
|
X
|
X
|
Telephone number
|
X
|
X
|
X
|
X
|
Address
|
|
X
|
X
|
X
|
Location-information
|
Cell-ID
|
X
|
X
|
X
|
Call-history
|
X
|
|
|
|
4.8Romania
Table : Case file Data (Romania)
Data
|
Role
|
112 PSAP
|
Police
|
Fire brigade
|
Ambulance
|
Free text
|
Short description of incident
|
X
|
X
|
X
|
X
|
Incident address
|
Locality, municipality, Street, street no.
|
X
|
X
|
X
|
X
|
Responsibility area
|
Agencies responsibility area
|
|
X
|
X
|
X
|
Caller information
|
Name, Surname, telephone number, address
|
X
|
X
|
X
|
X
|
Victim information
|
Name, Surname, age, sex,
|
X
|
X
|
X
|
X
|
Telephone location
|
Cell id, Sector id position
|
X
|
X
|
X
|
X
|
Case index
|
Incident Classification
|
X
|
X
|
X
|
X
|
Case questions
|
Help operator to understand the incident type
|
|
X
|
X
|
X
|
MSD
|
All fields according to standards
|
X
|
X
|
X
|
X
|
EUCARIS
|
All fields according to standards
|
X
|
X
|
X
|
X
| 4.9Sweden
To be added
5General workflow
Please describe the general operational workflow for handling an eCall. This workflow should be done from an operational point of view, describing actions done by the call-taker. This general workflow should cover only a “basic” eCall, without mentioning any exceptions (call drops because a weak signal). All the exceptions will be covered in the operational procedures in a decision workflow.
Your input should be composed of a graphic representation of the workflow and a text description for all the steps in the workflow.
As example you can use the attached Romanian workflow.
5.1Croatia
Figure : eCall Operational Workflow (Croatia)
5.1.1Laboratory eCall T&V
Laboratory testing of eCall includes 7 different scenarios. Four scenarios include on site IVS units tested against mobile network infrastructure which includes eCall flag feature and PSAP, and additional three scenarios which includes remote testing from various IVS units against PSAP solution. In remote testing MNO eCall flag feature is not being tested.
Table : Laboratory eCall T&V (Croatia)
Code
|
No. of IVS units involved
|
No. of IVS units in roaming
|
eCall initiation
|
No. of repeated initiations
|
No. of tests
|
L1
|
1
|
0
|
A
|
0
|
> 1000
|
L2
|
1
|
1
|
A
|
0
|
> 1000
|
L3
|
1
|
0
|
M
|
0
|
> 1000
|
L4
|
1
|
1
|
M
|
0
|
> 1000
|
L5
|
1
|
0
|
M
|
3
|
> 1000
|
L6
|
1
|
1
|
M
|
3
|
> 1000
|
L7
|
1
|
0
|
A
|
3
|
> 1000
|
Figure : Laboratory T&V Workflow (Croatia)
5.1.2eCall communication T&V
Group testing of eCall includes four different scenarios which include eCall testing in urban and rural environment. Test will include variations in number of vehicles involved, will different eCall initiation type, and will monitor the signal strength. All data including IVS provided date besides MSD, mobile network data and PSAP logs data will be monitored and examined according to KPIs defined in D4.1.
Table : eCall Communication T&V (Croatia)
Code
|
Location
|
No. of vehicles involved
|
No. of vehicles in roaming
|
eCall initiation
|
No. of tests
|
R1
|
Zagreb Centre - urban
|
2
|
1
|
M
|
> 100
|
R2
|
Zagreb Ring/Motorway -rural
|
3
|
1
|
M
|
> 100
|
R3
|
Zagreb Ring/Motorway - rural
|
1
|
0
|
A
|
> 1000
|
R4
|
Local road (near Zagreb) - rural
|
1
|
0
|
A
|
> 1000
|
Figure : eCall Communication T&V Workflow (Croatia)
SOP testing and verification includes testing of whole eCall chain with information being forwarded to 2nd level PSAP which includes all involved emergency services as well as traffic information provider. Since this scenario is identical to General eCall workflow, figure 5.1 applies.
Table : eCall SOP T&V (Croatia)
Code
|
Location
|
No. of vehicles involved
|
No. of vehicles in roaming
|
eCall initiation
|
No. of tests
|
S1
|
Zagreb Centre – urban
|
3
|
1
|
M
|
4
|
S2
|
Zagreb Ring/Motorway – rural
|
3
|
1
|
A
|
4
|
5.1.4Position estimation for eCall T&V
There will be seven eCall equipment-independent tests of GPS vs GPS/GLONASS vs GPS/EGNOS performance in Zagreb City Centre (2), on the Zagreb - Bjelovar route (combination of motorway and local roads - 1), and Rijeka - Zagreb motorway (partially mountainous terrain, with tunnels - 4). Position samples to be taken continuously every 2 s for at least one hour.
Figure : Position estimation for eCall T&V (Croatia)
Share with your friends: |