@Adnim, Re: Do
"Do vehicles really *need* to communicate with the manufacturer? "
Yes and no.
For commercial vehicles, the answer is yes. They need to be able to communicate with the fleet management company as well as feedback information to the manufacture / dealer. Of course the feedback is two different types. One needs to know the location to make sure the driver is where he is supposed to be and is doing his job. The other needs to monitor the engine and other elements of the car in order to determine alerts and service calls.
The manufacturer can take the information over a series of vehicles and determine how a specific engine is handling. (This is a good example of IoT and Big Data.)
The downside is that they can also capture data like the routes, times and distances driven. Also along with your driving patterns. That would be a bit invasive. (Just like those who use Uber all the time... never use them for a booty call, or an extra marital affair...)
The third issue is safety and security. OnStar alerts if the airbag is deployed or some other emergency occurs.
Fourth, software updates done automatically. So you don't have to go in to the repair shop to get a software update to your engine.
But the larger problem... Tying the wifi and hotspot features in to the controls of the car. (e.g. remote stop or remote control of the car by a law enforcement agency.) That's a bit scary because of hacking concerns.
There are other advantages ... e.g using your car to monitor traffic. This could be a good idea because the car's navigation could automatically alert you to traffic jams ahead and suggest alternate routes.
Do you need this? No, you need air, water, food and shelter. Is it a nice to have? Sure, if they can stop hackers from taking over the car.
Do you trust Microsoft or IBM? Not so much... I would hate to have to have my car stall out and reboot in the middle of the 101 during rush hour.
Biting the hand that feeds IT
