open source lessons learned click to edit master title style · 2017-11-07 · • lessons learned...
Post on 12-Jun-2020
3 Views
Preview:
TRANSCRIPT
-
• The need for change
• A new mindset
• Lessons Learned• Community• Empowerment• Value add• Collaboration vs
competition
Embracing Open Source in the Auto IndustryALS – 2011Smethurst
Click to edit Master title style
Graham SmethurstGENIVI President
BMW Group
1Copyright © GENIVI Alliance 2011
Open Source Lessons Learned From GENIVI28th November 2011
Automotive Linux Summit 2011
-
• The need for change
• A new mindset
• Lessons Learned• Community• Empowerment• Value add• Collaboration vs
competition
Embracing Open Source in the Auto IndustryALS – 2011Smethurst
The Infotainment Challenge Facing The Automotive Industry.
Revenues
Costs
Market Revenue
Develop - ment Costs
Market Revenue
Shorter ProductLife in the Market
Rising costs of innovation
0
Develop - ment Costs
2Copyright © GENIVI Alliance 2011
-
• The need for change
• A new mindset
• Lessons Learned• Community• Empowerment• Value add• Collaboration vs
competition
Embracing Open Source in the Auto IndustryALS – 2011Smethurst
Headunit prices have plateaued. New development / business model needed.
2000 2003 2005 2008 2011 2012 2013 2014 20150
200
400
600
800
1000
1200
1400
RadioEntry MediaEntry NavigationHigh Navigation
Architectural integration
3Copyright © GENIVI Alliance 2011
-
• The need for change
• A new mindset
• Lessons Learned• Community• Empowerment• Value add• Collaboration vs
competition
Embracing Open Source in the Auto IndustryALS – 2011Smethurst
In the 20th century, the automobile redefined the very concept of mobility. In the 21st century the automobile industry is finding it increasingly difficult to keep pace with consumer mobility trends.The infotainment functionality its possible to offer and sustain from within an isolated automotive eco-system is reaching its limits.
The key to meeting customer expectations in future is inheritance and interoperability with consumer eco-systems
Continuing to meet customer infotainment expectations demands a fundamental shift.
4Copyright © GENIVI Alliance 2011
-
• The need for change
• A new mindset
• Lessons Learned• Community• Empowerment• Value add• Collaboration vs
competition
Embracing Open Source in the Auto IndustryALS – 2011Smethurst
Middleware OS
Hardware
Applications
MMI
Middleware OS
Hardware
Applications
MMI
Entry MID
Middleware OS
Hardware
Applications
MMI
Profi
Automotive Middleware
Headunit
MMICustomer value add
“Ground hog day” in head unit development:• Development of commodity content x3.• OEMspecifics re-implemented x3.• Product validation x3• Problems solved with one supplier re-occur with others.• Limited time for innovation and new customer features.• HMI x1
5Copyright © GENIVI Alliance 2011
The need to control development costs and increase innovation demands software inheritance & re-use across the automotive industry.
-
• The need for change
• A new mindset
• Lessons Learned• Community• Empowerment• Value add• Collaboration vs
competition
Embracing Open Source in the Auto IndustryALS – 2011Smethurst
The search for the IVI General Purpose OS. Technical and Supply chain considerations.
Functionality
ProfiMidRadio Entry
Desk topNetbookSmart phone
Consumer
Automotive
Media Player
Software scalability across the full product portfolio is a must.
• In product development multi-sourcing and customisation is a must.
• Competition / alternatives stimulate innovation and results in a fair / sustainable price.
6Copyright © GENIVI Alliance 2011
HardwareHardware
Hardware
LINUX Automotive Middleware
Customer value add
-
• The need for change
• A new mindset
• Lessons Learned• Community• Empowerment• Value add• Collaboration vs
competition
Embracing Open Source in the Auto IndustryALS – 2011Smethurst
Open source code in the car, are you crazy?
7Copyright © GENIVI Alliance 2011
-
• The need for change
• A new mindset
• Lessons Learned• Community• Empowerment• Value add• Collaboration vs
competition
Embracing Open Source in the Auto IndustryALS – 2011Smethurst
Re-alignment of automotive infotainment. Lessons Learned from adjacent industries.
• Architected, structured
• Common OS – Linux
• Common Middleware (e.g. CGL)
• Common HW Standard (e.g. ATCA)
• Differentiation in core competencies
Solution Creation
Telecom
• Vendor Lock-in • Hard to Innovate• Expensive
Development• Long Dev. Cycle• Lack of Standards• Some
Differentiation at all levels –> outside core competency
Vertical Point Solutions
• Choice is fragmented
• Some innovation, still costly
• Few middleware or HW standards
• Differentiation outside core competency
Experiments
1998 2002 2007
Widespread Adoption
• Cost optimization
• Revenue maximization
• Innovation and differentiation
Automotive 2006 2009 2012 2016
-
• The need for change
• A new mindset
• Lessons Learned• Community• Empowerment• Value add• Collaboration vs
competition
Embracing Open Source in the Auto IndustryALS – 2011Smethurst
Community
9Copyright © GENIVI Alliance 2011
-
• The need for change
• A new mindset
• Lessons Learned• Community• Empowerment• Value add• Collaboration vs
competition
Embracing Open Source in the Auto IndustryALS – 2011Smethurst
Membership SummaryCommon mission drives continued growth
23%
48%
29%
Asia / Pacific
Europe / Middle East /Africa
North /South America
10Copyright © GENIVI Alliance 2011
-
• The need for change
• A new mindset
• Lessons Learned• Community• Empowerment• Value add• Collaboration vs
competition
Embracing Open Source in the Auto IndustryALS – 2011Smethurst
OEMs
Renesas
The GENIVI Alliance Membership (www.genivi.org)
First Tiers
OSV, Middleware, Hardware, and Services Suppliers
Silicon
-
• The need for change
• A new mindset
• Lessons Learned• Community• Empowerment• Value add• Collaboration vs
competition
Embracing Open Source in the Auto IndustryALS – 2011Smethurst
Empowerment
12Copyright © GENIVI Alliance 2011
-
• The need for change
• A new mindset
• Lessons Learned• Community• Empowerment• Value add• Collaboration vs
competition
Embracing Open Source in the Auto IndustryALS – 2011Smethurst
Historical GENIVI Structure
Strategy Council
Frederic Bourcier(PSA)
Technical Council
Markus Boje(BMW)
Marketing Council
Joel Hoffman(Intel)
GENIVI Board of Directors
Process
Legal
Internet Office
Auto– motive
System Infra-
structure
CE &Multi-Media
Out -reach Comms
Plan - ning
Board
Council
Work Group
ReferenceSystem
GENIVI Alliance March 2009 – October 2010“You learn by your mistakes”
13Copyright © GENIVI Alliance 2011
-
• The need for change
• A new mindset
• Lessons Learned• Community• Empowerment• Value add• Collaboration vs
competition
Embracing Open Source in the Auto IndustryALS – 2011Smethurst
Click to edit Master title style
GENIVI Alliance activitiesHow it works.
• Aligned IVI requirements across a broad base of OEMs.
• Identified software interfaces / components that meet the agreed requirements.
• A compliance specification & assessment program against which commercial offerings can be certified.
• Modification / creation of software components
• GENIVI originated code
• GENIVI development baselines
Alignment Execution
Maintenance
• A code baseline that “demonstrates” the requirements and “proves” the compliance spec
14Copyright © GENIVI Alliance 2011
-
• The need for change
• A new mindset
• Lessons Learned• Community• Empowerment• Value add• Collaboration vs
competition
Embracing Open Source in the Auto IndustryALS – 2011Smethurst
GENIVI Working Model.Structure vs. Activities.
System
Architec ture T
eam
Baseline Integration Team
Alignment Execution
Project Maintain
er
Project Maintain
er
Project Maintain
er
Programme Management Office
Expert Groups
Expert
GroupExpert
GroupExpert
Group
Expert
GroupExpert
GroupExpert
Group
Maintenance
Domain Lead Architect
System Infrastructure BMW (Boje) Magneti-Marelli (Galgani)Automotive Telemotiv (Ancel) Visteon (Konopelko) Media & Graphics Renault (Alidra) Delphi (Jalics) Location Based Services PSA (Colliot) XSe (Residori)
Networking BMW (Kurzeder) Alpine (Hahn)CE Connectivity JLR (Virk) TATA ELXSI (Borawar)
• Aligned IVI requirements across a broad base of OEMs.
• Identified software interfaces / components that meet the agreed requirements.
Execution Team
Execution Team
Execution Team
Execution Team
Execution Team
Execution Team
Execution Team
Execution Team
Development Baselines• A code baseline that “demonstrates” the requirements and “proves” the compliance spec
• Modification / creation of software components
• A compliance specification & assessment program against which commercial offerings can be certified.
• GENIVI originated code
• GENIVI development baselines
15Copyright © GENIVI Alliance 2011
-
• The need for change
• A new mindset
• Lessons Learned• Community• Empowerment• Value add• Collaboration vs
competition
Embracing Open Source in the Auto IndustryALS – 2011Smethurst
Knowing your value add
16Copyright © GENIVI Alliance 2011
-
• The need for change
• A new mindset
• Lessons Learned• Community• Empowerment• Value add• Collaboration vs
competition
Embracing Open Source in the Auto IndustryALS – 2011Smethurst
An open source based automotive headunit.Determining the pre-competitive content.
Cus
tom
er F
eat u
re /
Inno
vat io
n po
tent
ial
Automaker Specific
Conventionally purchased code(e.g. Navigation, speech
recognition)
Automaker Code(e.g User Interface, USPs)
CommunityCode
(e.g. PersistencyMgr, PwrMgr, Layer Mgr, AudioMgr, UserMgr,
Lifecycle Mgr…)
Module and interface standardisation(e.g. Autosar, IP-based Vehicle Networking)
Automaker Code(e.g. Flashing, Diagnostics,
Provisioning/Coding, software update)
17Copyright © GENIVI Alliance 2011
GENIVI Focus
-
• The need for change
• A new mindset
• Lessons Learned• Community• Empowerment• Value add• Collaboration vs
competition
Embracing Open Source in the Auto IndustryALS – 2011Smethurst
18Copyright © GENIVI Alliance 2011
Hardware
Apps
Solution Stack
GENIVI Development
Baselines
GENIVI Code
80%
15%
5%
Automotive Specific Code Extended Community code
Community CodeUser
Interface
Create
Adapt
Adopt
Upstream projects and
compliant free distributions
The GENIVI Operating PrincipalEnabling automotive on an open source base.
-
• The need for change
• A new mindset
• Lessons Learned• Community• Empowerment• Value add• Collaboration vs
competition
Embracing Open Source in the Auto IndustryALS – 2011Smethurst
The relationship between GENIVI and product development
GENIVI Alliance Product Development
• Specification of non-differentiating requirements.
• Architecture / Component definition.
• Component selection, modification, code implementation.
• Development baseline
• Compliance programme
• Product definition.
• Commercial partner contracts.
• Mandated GENIVI compliance
• GENIVI code re-use.
• Implementation & integration of OEM specifics.
• Upstreaming of enhanced / bug fixed code.
• Donation of new code.
• Product delivery
19Copyright © GENIVI Alliance 2011
-
• The need for change
• A new mindset
• Lessons Learned• Community• Empowerment• Value add• Collaboration vs
competition
Embracing Open Source in the Auto IndustryALS – 2011Smethurst
The relationship between GENIVI Alliance activity, a member reference and product.
GENIVI Development baseline
Hardware
Apps
80%15%
5%
User Interface
Hardware
Apps
User Interface
GENIVI compliant member reference
Hardware
Apps
User Interface
GENIVI compliant product
GENIVI Compliance
Optimisation / functional showcase
Optimisation / customised OEM
productCopyright © GENIVI Alliance 2011
-
• The need for change
• A new mindset
• Lessons Learned• Community• Empowerment• Value add• Collaboration vs
competition
Embracing Open Source in the Auto IndustryALS – 2011Smethurst
Product Hardware Development
BSP
Product Hardware Development
BSP
Product Hardware Development
BSP
Entry Product Mid Product Profi Product
Applications
Reference Hardware Development(s)
IVI Systems Integration
IVI Systems Validation
Applications
BSP
Demonstrator
Human-Machine Interface
OEM middleware extensions
HMI
Product Development
IVI Systems Integration
IVI product Validation
IVI Product Integration
IVI Systems Validation
IVI Product Integration IVI Product Integration
IVI product Validation IVI product Validation
Middleware & Operation System with Automotive Industry ExtensionsGENIVI
Middleware
Reduced validation cost
Reduced integration cost
Application re-use
Community Middleware
Hardened / customised
OEM re-use
OEM open source based product . Evolved development model based on GENIVI.
OEM re-use
21Copyright © GENIVI Alliance 2011
-
• The need for change
• A new mindset
• Lessons Learned• Community• Empowerment• Value add• Collaboration vs
competition
Embracing Open Source in the Auto IndustryALS – 2011Smethurst
The consumer sector continues to increase in functionality and decrease in price increasing the competitive pressure on the automotive OEM.
The infotainment functionality its possible to offer and sustain from within an isolated automotive eco-system is reaching its limits.
To confront the challenge, the automotive industry is re-aligning to take full advantage of “open source”.
GENIVI has provided the community within which the automotive industry is transitioning to an open source approach in infotainment product development.
Involvement of the entire supply chain, worldwide. New mind set around identification, development and delivery of the
pre-competitive components A desire to understand and willingness to contribute to a broad
community effort
GENIVI`s continued success depends on increased collaboration with established open source projects and a willingness to consider automotive needs within their scope.
SummarySummary. The role of Open Source in Automotive IVI.
22Copyright © GENIVI Alliance 2011
-
• The need for change
• A new mindset
• Lessons Learned• Community• Empowerment• Value add• Collaboration vs
competition
Embracing Open Source in the Auto IndustryALS – 2011Smethurst
Thankyou
Differentiation based on a strong community platform.
Join us : http://www.genivi.org/ 23Copyright © GENIVI Alliance 2011
http://www.genivi.org/
Slide 1The Infotainment Challenge Facing The Automotive Industry.Slide 3Slide 4Slide 5Slide 6Slide 7Slide 8Slide 9Membership Summary Common mission drives continued growthSlide 11Slide 12Historical GENIVI StructureSlide 14GENIVI Working Model. Structure vs. Activities.Slide 16Slide 17Slide 18Slide 19Slide 20Slide 21SummaryThankyou
top related