1 Pilot operation preparation report Version number

Czech Republic

1. eCall reception and visualisation

2. Event form opening

3. Proposal of data interpretation

Even in case that this information cannot be confirmed by voice communication with passengers, interpretation is as follows:

• 
  eCall was activated automatically – it is probably a traffic collision
  
• 
  eCall was activated manually – it can be ether traffic collision or other type of incident
  
• 
  eCall is test call – event classification is predefined as technological test
  
• 
  if position credibility is impeached, then automatisms are stopped
  

4. Process automation

1. Automatic matching caller position with event position

Automatic activation = Yes

Position Can Be Trusted = True

2. Automatic classification

Automatic activation = Yes

Test call = No

System automatically set up predefined classification “traffic accident” for all rescue forces (Fire Rescue, Ambulance, and Police)

Automatic activation = Yes

Test call = Yes

3. Automatic regionalisation

5. GIS visualisation

6. Manual classification

1. Event position determination

• 
  By means of line topography if probable road is known
  
• 
  If probable road is not found, then event position is determined as a call position point + urban area, to which the call position point belongs – it means determination by the help of address topography
  
• 
  Call taker application switches over topography folds according to the event position determination
  

8. Regionalisation

9. Additional information

• 
  communication level (communicates / doesn’t communicate)
  
• 
  call back number (alternative to IVS number)
  
• 
  other remarks (e.g. caller name)
  

10. Event saving and dispatch

11. Request SEND MSD

1. 
   Operator evaluates the data in the MSD are inadequate, or otherwise applying the update (e.g. corrupted data, the position is marked as unreliable).
   
2. 
   Operator notifies the caller that voice communication will be interrupted.
   
3. 
   Operator presses "Request MSD" button.
   

• 
  In call sub-form a running MSD query is signalised
  
• 
  call is automatically routed to the IVR (disappears from the phone software)
  
• 
  after MSD is received, call is routed back to the operator workplace, where the call was originally handled - in SW phone call is ringing
  
• 
  this call is indicated by the Call Agent as a call from the previously adopted and broken eCall
  
• 
  data from the IVR are processed by eCall Centre module meanwhile, this module informs dispatching application which reads the updated data
  
• 
  operator will answer call automatically – thus voice communication with the caller will be restored
  

4. 
   Operator notifies the caller in distress to restore voice communication.
   

12. PSAP Call back

Procedure description:

1. 
   Operator uses the option from the context menu item above telephone number in the property grid with call properties and chooses "Call back" option.
   
2. 
   After creating a connection is set up, application automatically connects an outgoing call to the event.
   
3. 
   Operator has dispatcher has now again possibility to seek re-sending MSD.
   
4. 
   MSD received will be appended to the original call.
   

Figure 18: eCall Operational Workflow (Czech Republic)