Today's automotive OEMs and Tier 1s are taking advantage of rich Open Source software platforms to deliver the best In-Vehicle-Infotainment (IVI) experiences for consumers. The pitfalls of Open Source platforms need to be understood in order to design secure and highly functioning solutions. Compliance issues beyond licensing for these platforms such as Android will be revealed to assist automotive companies with future IVI product development including standard boot times, security of the system, and storefront maintenance and the overall management of application development eco-system.
With the technology available, automotive manufacturers and suppliers still struggle to develop, test, deploy, and support IVI products and services across multiple car models and generations. On top of this is the added complexity of enabling 3rd party application vendors to deliver content to the vehicle without distracting the driver. It can take up to three to four years for an OEM to build a new infotainment platform into a new automobile model. Aftermarket providers can offer a new infotainment system to the market in one-year. A common software architecture that can be applied can go far to alleviate many of these concerns and to streamline time-to-market with such strenuous development cycles.
This whitepaper leverages Teleca's primary research and experiences with Open Source partners and customers to deliver solutions to the largest OEMs and suppliers around the world along with secondary research in the industry. The problem being addressed is how automotive companies can take advantage of the latest Open Source software platforms while maintaining compliance with licensing, coding and feature standards.