The Implementation of Driverless Cars
When is the last time that another driver cut you off?
Is that the only use case for driverless cars on our roads? No, it isn’t, but as you sit there at your computer reading this, is it a good one? Yes, it is a good use case for the overall implementation of driverless cars. And yes, the police often ticket reckless drivers, and having more cameras allows for greater enforcement, but at some point, does that matter?
The more time the police spend chasing, apprehending and monitoring risky drivers, the less time they have to focus on other aspects of their jobs overall. However, there are many additional use cases. Parents of children can appreciate the scary reality of the late night call that your child has been involved in a car accident. That is a call all parents dread, but driverless cars will reduce those calls.
Delivery services will greatly enjoy the experience of offering food and other delivery services without requiring a human being. Several universities are experimenting with delivery drones and delivery vehicles that provide an interesting view of what will be possible. That is a use case that is both cost saving and increases the capacity use case for driverless delivery vehicles.
In fairness though, to show and discuss both sides of this issue, you have to consider the downsides of driverless cars. And the first problem is deployment. The race to driverless starts with less than one percent of all deployed vehicles being driverless. There will be a long time when driverless cars are not the only cars on the road, or for that matter, even the majority of cars on the road.
The tipping point for driverless vehicles will probably be between 50 and 60 percent of all cars on the road. Or a faster tipping point would be to make it illegal to drive a car and offering a free retrofitted system for all cars. Even though that gets them to the overall goal faster, is that the best way to go forward?
Before the tipping point, the overall software solution will have to be better in the beginning than it will be later. Once the tipping point pushes the number of driverless cars higher and the number of human-driven cars lower, the software can focus less on the variables like other human drivers, and more focused on improving the experience.
The last downside is the human being. In the past six months, there have been reports of some problems like accidents involving the driverless cars run by Lyft and Uber. Additionally, there was a fatality involving a driverless car and a pedestrian. Beyond the bad news, there is a negative impression regarding driverless cars. The “my car” is a freedom attitude, so it is the “it’s my car” that remains a blocker to the eventual deployment of driverless cars.
First, collision protection systems are available on many cars built after 2015. And collision detection is the first step towards driverless cars. But collision detection does not reduce the human impact on cars. The reality of the system overall is that they notify you when another driver is too close. However, they don’t reduce the reality of aggressive drivers.
While collision detection reduces the number of rear-end collisions and lane change accidents, it doesn’t remove the reality of distracted and impaired drivers from the road. The question is should humans still be driving?
If humans don’t drive anymore, that driver who wove in and out of traffic and cut you off won’t be driving anymore, either.
By Scott Anderson
Scott Andersen is the managing partner and Chief Technology Officer of Creative Technology & Innovation. During his 25+ years in the technology industry Scott has followed many technology trends down the rabbit hole. From early adopter to last person selecting a technology Scott has been on all sides. Today he loves spending time on his boat, with his family and backing many Kickstarter and Indiegogo projects.