How has Collision Response been tested and calibrated?
Zendrive has tested and validated the reliability of their Software Development Kit (SDK) in crash test facility at BMW (one of Zendrive’s investors). These crash tests have allowed Zendrive to refine and improve the collision detection algorithm.
The SDK has been calibrated to detect serious collisions where the car is moving at more than 20 mph prior to the impact.
Zendrive’s SDK has also been installed in other safety apps, in turn installed on millions of phones. This means thousands of real collisions have been detected and analysed, allowing continual improvements to the SDK since it was launched in 2015.
It is a state-of-the-art, mature, stable and reliable SDK with a proven track record of accurate collision detection, among other features important for driving safety.
So Zendrive has tested and validated the trip detection and collision detection of their SDK. But how has the integration into Smart24 been tested and validated by Track24?
As part of Smart24 development, our engineering team has created a ‘test mode’ within the app, which allows us to manually start Drive Mode (a necessary condition for Collision Detection to be active). In this test mode we also have added the option to ‘raise a mock’ collision—using functionality provided by Zendrive—when Drive Mode is detected. This allows us to test the background automations and use of the network.
We have also physically validated that lesser acceleration scenarios, like a dropped phone, harsh braking and emergency stop from 60 kph, do not create false collision alerts, and we have validated Trip detection over hundreds of hours of drive time and hundreds of detected trips.
Our app also has ‘app crash reporting’ built in. This means that when the app crashes, (i.e. it stops working unexpectedly) we receive detailed information on the cause of the crash. This has enabled us to drive up the overall reliability and stability of Smart24.
In the interests of transparency, Track24 has not performed a crash test, like those that Zendrive have performed in the BMW test lab.
If Collision Response is an ‘autonomous system’ then what are the safeguards in place to make sure it is working properly?
During a drive (using caution), you can check that Drive Mode is active via a ‘Drive in Progress’ banner that appears on the Smart24 home screen. This banner disappears after the end of Drive Mode.
When there is no available network connection (or if you have you have run out of data in your plan) then an orange banner appears at the Smart24 homescreen. The absence of the orange banner means that Smart24 has active access to mobile data.
You can check that the alerting system works via our Emergency button, by performing an Emergency drill in coordination with your monitoring team.
Background Location access is such a fundamental part Smart24, that if your switch off Location Services, you will see a ‘blocking’ alert on the Smart24 home screen, directing you back to Smart24 settings to switch on Location Services.
What happens if I accidentally override or cancel the Collision Alert?
In this instance, we recommend that you use the Emergency button on Smart24 as a ‘fallback’. This will alert your monitoring team in the same manner as a collision alert.
Do I need to remember to launch the app before every trip I take? Like putting on a seatbelt?
No. On Android phones, Smart24 stays running ‘in the background’ at all times once you have launched it. On iPhones, Smart24 wakes if you move significantly, so it will be running ‘in the background’ even if you have ‘force closed’ it (by swiping the app upwards from the app switcher). Drive Mode is automatically detected when Smart24 is running.
Article is closed for comments.