1 Pilot operation preparation report Version number



Download 6.16 Mb.
Page11/29
Date08.05.2018
Size6.16 Mb.
#48528
1   ...   7   8   9   10   11   12   13   14   ...   29

Sweden

  1. Short description



      1. Involved parties

  1. Case file data


The scope of this is section is to give an overview of the data that is currently available in the PSAP for every 112 call. Based on this information and where it’s gathered and processed, every country will design the operational workflow by identifying the mandatory actions that must be taken by the operator.

Data

112 PSAP

Police

Fire brigade

Ambulance

Name

X










Telephone number




X







Address













Etc.














    1. Croatia


Data which is currently being collected by the 112 PSAP call taker and by the Emergency Agencies in case of traffic accident is listed in following table:

Table 6: Case file data (Croatia)



Data

112 PSAP

Police

Fire brigade

Ambulance

Name



X

X




X

Telephone number


X

X

X

X

Description


X

X

X

X

Accident location


X

X

X

X

Vehicle orientation


X

X

X

X

Number of people injured

X

X




X

Fire


X

X

X

X

Are injured people trapped in vehicle

X




X

X

Dangerous goods


X

X

X




Number of vehicles involved


X

X








    1. Czech Republic


Table 7: Case file data (Czech Republic)

Data

112 PSAP

Police

Fire brigade

Ambulance

Name

X

X

X

X

Telephone number – caller contact

X

X

X

X

Location of the caller

X










Event location

X

X

X

X

Car data – type, model, year of production

X

X

X




Accident severity

X







X


    1. Finland


Finnish PSAPs collect the following data from the caller:

Table 8: Case File Data (Finland)



From caller

Name, location of the accident, description of the accident, involved vehicle(s) information, passengers etc.

Identified from the system

Phone number, address (personal identification number), location of the cell phone


    1. Germany


In Germany with it’s over 250 different PSAPs, it is currently unclear what data is exactly collected. Depending on the local authority, PSAPs often integrate Ambulance and Fire Brigade, but not Police (which is in Germany a 110 call and is completely separated from the 112 process). However, all PSAPs collect usual address information and additional descriptions from 112 calls. This data will also be collected for 112 eCalls (which only are of interest in this document).

The PSAPs in Germany currently collect the following accident-related data:



Table 9: Case file Data (Germany)

Caller

Name, Address, telephone number

Car

Sign, Model, Colour, damage

Accident

Location, situation description, Risk (gasoline running out etc.), Number of affected cars

Car occupants

Injuries, pre-existing conditions, pregnancy


    1. Greece


Table 10: Case file Data (Greece)

Data

112 PSAP

Police

Fire brigade

Emergency Medical Help

Voice communication

X










Telephone number

X










Emergency Agency called

X

X (if another one is needed)




X (if another one is needed)

Location of the telephone (antenna coordinates, azimuth, estimated distance from antenna)

X










Names and IDs of involved persons




X

Χ

X

Complete vehicle data (number of plates, model, colour, number of licence)




X

X




Accident location and date




X

X

X

Accident type and description




X







Injuries per involved person




X







Damages




X







Data for accident reconstruction (liability, diagram with cars, braking distance, testimonies from drivers and from witnesses if needed, alcohol test in minor injuries, drugs test at a hospital in severe injury or death)




X







Transfer point of involved persons










X

    1. Italy


Table 11: Case File Data (Italy)

Data

112 PSAP

Police

Fire brigade

Ambulance

Name

X

X

X

X

Telephone number

X

X

X

X

Address

X

X

X

X

Event Category

X

X

X

X

Brief Event Description

X

X

X

X

Geographical Position

X

X

X

X

Clinical Data










X

Casualty Description




X

X





    1. Netherlands


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 12: 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











    1. Romania


Table 13: 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

    1. Sweden


To be added

  1. General 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.

    1. Croatia


Figure 14: eCall Operational Workflow (Croatia)


      1. Laboratory 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 14: 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 15: Laboratory T&V Workflow (Croatia)


      1. eCall 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 15: 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 16: eCall Communication T&V Workflow (Croatia)


      1. SOP testing and verification


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 16: 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


      1. Position 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 17: Position estimation for eCall T&V (Croatia)




    1. Download 6.16 Mb.

      Share with your friends:
1   ...   7   8   9   10   11   12   13   14   ...   29



The database is protected by copyright ©ininet.org 2024
send message
    Main page
Guide
Instructions
Report
Request
Review