1. eCall for Powered Two Wheelers Opportunities and Challenges
European Motorcyclists Forum,
Working session 3:
“Opportunities and Challenges”
6 March 2014, Brussels
eCall for PTW: the OPPORTUNITIES may seem obvious – positive contribution to reduce fatalities and consequences of severe due to reduce time in recue operations. The CHALLENGES may not seem obvious at a first glance: eCall will be introduced for cars soon, so one could assume there is already best practise and things will be fairly simple.

2. How eCall for Cars works
MSD & VOICE
MSD & VOICE
VOICE
VOICE
Network
VOICE
I also suppose, most of you know how eCall works. Nevertheless lets have a look at the eCall scenario:
explain scenario
Now it seems all set and we only need to replace the car in the scenario with a motorcycle?
Let do so
Traffic Information

3. How PTW eCall works TRIGGERING? Traffic Information Explain scenario
MSD & (VOICE?)
MSD & (VOICE?)
(VOICE?)
(VOICE?)
Network
TRIGGERING?
VOICE
Explain scenario
Voice connection is a difference – explain in next chart details
Triggering main issue will explain more details later
Traffic Information

4. Motorcycle eCall a new & different challenge?
Difference
Motorcycle and rider separate
Forces vary to vehicle & rider post crash
Location vehicle & rider vary post crash
Accident recognition is complex
Stability criteria
Sensor types
Omni directional sensing
Voice connection likely unreliable
Ambient noise
Distance rider-vehicle
Common
Rescue chain
Communication Standards
Requirement power supply
Infrastructure / business case

5. Triggering- main challenge
eCall triggering usually with airbag/acceleration sensors
Decades of experience with triggering
Well defined accident scenarios with corresponding parameters
eCall triggering not defined (no best practise)
Accident scenarios are not well defined and quite complex
Rider & motorcycle will be separated after crash (injuries?)
Substantial Unsolved Issues
FOCUS: define minimum requirements
As we can see, the main difference is complexity of accident scenarios. Consequently recognizing an accident creating injuries to the rider is the main challenge

6. PTW eCall is most complex
OEM / maker is liable for its product:
OEM produces (PTW) vehicles
eCall system needs to be in the vehicle (liability & quality& supply chain)
Systems not linked to vehicle are out of OEM control and responsibility
eCall is complex: and therefore, allow me a personal remark:
“I am a motorcyclist and a car driver at the same time. For me like so many other bikers in the end eCall is supposed to call help if we are unable to do so by our self, regardless car or motorcycle.
Since MC eCall is more complex, as a Biker I expect to understand beforehand what the system can do and what not. “
Since the motorcycle maker is only liable for his own products and the communication to users for his own product, it can only be the vehicle and its components itself.
Research: Limitations and Minimum requirements

7. PTW Industry Strategy
Definition of a PTW eCall system and its requirements
ACEM research proposal to EC to define Standards for PTW eCall
Participation of OEM’s in Horizion 2020 project call for PTW safety

8. Minimum requirement – General
To make sure that:
Users understand what system can do and what not
Manufacturers are to supply a simple but robust functionality (PTW eCall standards)
Base for test and conformity requirements are necessary
The OEM - responsible only for the components and functionality of his own system on the vehicle, not for the overall function
The borderlines for false calls - to be discussed with relevant stakeholders

9. Minimum requirement - System components
Automatic & manual triggering system
eCall box or components with the necessary software (depending on the structure of the specific system/concept) and wiring
eCall button for termination
Indicators for the actual status and the current process step of an activated eCall
Geo location system (GPS)
Network Access Device
The MSD + eCall flag (standard for MSD for the transmission via 112)

10. Indicative Motorcycle eCall Roadmap
1. Define minimum requirements
2. Define open issues
3. Evaluate potential solutions
DONE
ONGOING
4. Discussion with stakeholders
NEXT STEP
5. RESEARCH
6. Standardisation
7. Technical concept development
8. Market information
9. Series development
10. Market introduction
FOLLOWING

11. Robust & Reliable PTW eCall
Thank you for your attention!
Still a stretch of road ahead of us