Ridar Systems is a cloud-based mobile solution which allows two-wheelers to turn their smartphone into a beacon through which drivers can better detect them before an interaction occurs. Our solution utilizes a cloud-based algorithm to manage the location of driver & rider thus providing a real-time predictive notification to the driver when a rider is ~5 seconds from the driver's location.
While the Garmin RTL 510 performs very well in detecting drivers and providing that notification to the cyclist, Ridar Systems works at alerting drivers of an approaching two-wheeler.
In developing our mobile solution, we found that about 75% of accidents involving drivers and bicycles/motorcycles were a direct result of the driver not seeing the much-smaller two-wheeler. As a result of our development, we developed a mobile solution that does not require additional hardware and it has the ability to detect two-wheelers when they are not in a clear line of sight to the driver: around corners, around structures and even when hidden behind other vehicles.
What happens to Ridar when riding through an area with no reception?
When a 'dead zone' is encountered, Ridar Systems will announce to the driver that the reception has been lost and to watch for riders. When the signal has been regained, Ridar will announce that it is back online.
How does Ridar handle congested urban environments without overwhelming drivers and riders with alerts?
In the future version of Ridar, we will integrate a solution that detects multiple cyclists/motorcyclists, etc so that an announcement will indicate "Bicycles Ahead", "Motorcycles to the Right", etc. based upon proximity of two-wheelers to other two-wheelers.
Also, with urban areas, there are bike lanes (whether protected or lanes). These lanes can be geo-fenced so that drivers do not get a notification for those cyclists. Where those lanes open up into an intersection (and, where the majority of accidents occur), drivers would receive a notification.
When too many riders are detected, the system will detect this and indicate: "Many Riders Nearby--Drive with Caution".
As the algorithm determines that the number of riders has 'thinned out', it will reinitialize, looking for riders and providing the notifications to drivers.
*One element that I want to clarify is that Ridar Systems currently sends notifications to drivers ONLY. There are discussions about providing notifications to cyclists in the future, especially where there is light automobile traffic.
Yeah, I just came back from Paris and it was crazy!! I imagine Ridar being the most use on open 2-lane roads with cars whizzing past my bicycle or them trying to left turn in front of my motorcycle. Isn't that the most common scenario for motorcycle fatalities? Someone in a car doesn't perceive you on a two-lane road and turns in front of you?
Exactly @Chris! In locations that have far too many riders in relation to drivers (scooters, mopeds, bicycles, etc), Ridar would not be effective as you would be receiving notifications overload or simply alerted that there are too many riders nearby to track effectively.
Locations such as Southeast Asia or other countries whose population relies mainly upon two-wheels for transportation would not be a good fit for our mobile solution.
In developing urban areas that are utilizing bicycle lanes, Ridar Systems would shine as we would not be notifying the driver of these riders while they are utilizing those lanes. Only when those cyclists approach an intersection would the driver be notified.
Drivers turning left across the path of a motorcycle is the most common and dangerous scenario for a rider and frequently results in severe injury or death.
Ridar wants to change that.
How would geofencing work with bike lanes, divided highways, and bridges?
Geofencing would omit those areas/locations that we do not want Ridar Systems to consider.
With bike lanes, we would not consider cyclists who might be sending us a signal while they are in that geofenced bike lane. But, when they leave that bike lane (especially at an intersection) that is where we do want Ridar Systems to alert the driver.
On divided highways, as long as there is a physical barrier between the two roads, we would not notify the driver of a rider on the other side of this highway.
But, if this were an undivided highway/road, we would notify the driver of an approaching two-wheeler because there is the opportunity for a potential collision between the two.
Bridges & off ramps would also be geofenced so that we can work to minimize any false-positives.
Does Ridar detect a collision and if so could it send an alert to emergency services?
If Ridar were to partner with companies already in the crash detection/emergency messaging space then, yes, we could incorporate that technology into our mobile solution. That is certainly an option.
For the driver, we will be working with Automobile Insurers to provide a premium discount to those subscribers who download the Ridar app through the insurer's portal and allow this technology to run in the background on their smartphone when driving. By obtaining this discount, the subscriber would need to allow their information to be shared back to their Insurer. This data would also contribute to UBI (usage-based insurance) where several elements are obtained from drivers to generate a score which, in turn, determines one's insurance costs.
Other means of getting Ridar into the driver's seat is to work with Telcos (cellular carriers), Automobile OEMs and Tier 1 Suppliers to the automotive segment to integrate the Ridar solution into the cockpit.
This data would also contribute to UBI (usage-based insurance) where several elements are obtained from drivers to generate a score which, in turn, determines one's insurance costs.
Usage-based insurance for drivers makes a lot of sense as an incentive. Is this something you are working on or planning in the future?
It is certainly something that could be used as one of the many elements that help score one's driving and adjust their insurance accordingly.
Ridar Systems is in discussions with automobile insurers as we estimate that there is approximately $41B paid out by insurers each year in the U.S. for motorcycle ($16B) and bicycle ($25B) accidents.
Not only could we prevent numerous accidents resulting in injury & death but insurers could easily incentivize their subscribers by saving money in the process.
All of this would, in turn, provide for safer roads for all involved.
There's really nothing that can prevent Google or Waze maps from adding such functionally. We would hope that we could collaborate with them in such an effort.
Our business model is to license our mobile solution to Automobile Insurers, Telcos, Automobile OEMs and Tier 1 Suppliers--those groups who would benefit most by preventing such accidents and saving lives & saving money.
Pedestrians? I guess anyone with a cell phone, right?
Technically, yes. As ridar currently looks 360 degrees around a driver, the technology would need to be developed to look directly ahead of the driver while geofencing the sidewalks and providing a faster notification to the driver (~1 second).
Hey Drue! The best way that Ridar Systems can get more support is to help us conduct some mini pilots where we can get end-users testing the system and provide us with feedback. This can consist of small groups testing with riders (cyclists, motorcyclists, etc) and drivers who also have the app running. This would help us better develop the system and gather additional data on usage. Reach out to us if you need assistance coordinating such an effort!
The current app serves both the 2-wheel and 4-wheel--simply select which you are using the app for.
As this is an MVP (minimal viable product), future iterations will include auto-start with the ability to detect driver (4-wheels) or rider (motorcycle, bicycle, scooter).
We will certainly do a thread in the Vendor's Forum on ADVRider to keep all updated on our progress!
It is currently available in the US & Canada through the App Store & Google Play. It is FREE and is an MVP version (minimally-viable product/Beta). As posted in the ADVRider Forum, this is a manually-started version for which we are looking for testers and feedback