Dear all,
Here is my formal proposal for the creation of an “Automotive Grade Open Source” SIG within the Eclipse SDV group of the Eclipse Foundation.
This is following up the
"call-to-action"
I made during the Automotive Open Source Summit in Starnberg..
Software used within vehicles has to meet special automotive requirements to be safe and secure. This is why the automotive industry is applying standards such as Automotive SPICE
(ASPICE), Functional Safety (according to ISO2626) and long-term maintenance (compliant with UNECE regulations) to systems and software.
Implementing new features in software may sound more compelling than meeting process requirements, but the latter is essential for great products the users will like and trust.
Within Eclipse SDV we have made first important steps to meet these automotive requirements: the “SDV
Process” and the badges have recently been introduced. Eclipse ThreadX is the first Open Source Real Time Operating System certified for safety-critical applications, and it is now an Eclipse project
under the Eclipse SDV WG purview as well as at the core of the ThreadX SIG. The first goal of this SIG is maintaining its safety certification.
The
badge
concept established by Dana is an excellent example of how our community can come up with smart approaches that are fitting to automotive processes and also fun to work with. The scope of the badges
is not only to encourage Eclipse projects to improve quality and deliver additional artifacts (e.g. documentation, test and requirements) but also to showcase the availability and maturity of these artifacts to potential adopters.
We can leverage our community and I would like to encourage all of you to bring this to the next level: a comprehensive approach targeted to develop a full SDV software stack
that meets functional safety requirements.
Initial focus areas of the Automotive Grade Open Source Special Interest Group could be:
-
Foster Open-source software development in compliance with
Automotive grade maturity models
-
How can
Safety qualification (according to ISO26262) be achieved with open-source
-
Impact of
long-term maintenance (e.g. as defined by UN ECE R156) on open-source
-
IP and
legal questions when combining open source and closed source as well as related to documentation, if needed
The task for the SIG should include
-
analyze requirements from key automotive standards (ASPICE, ISO26262, UNECE) and their relevance to open-source within the scope of Eclipse SDV
-
look at ongoing activities within the Eclipse SDV WG (SDV Process, Eclipse ThreadX), and align with SIGs (Threadx SIG, Rust SIG),
-
align with initiatives outside Eclipse (such as
ELISA,
NDS zserio) and SDV Alliance
-
create a comprehensive concept on how to achieve automotive grade open source for safety qualification
-
include recommendations which group or project within or outside the Eclipse Foundation might take care of elements of this concept
-
drive and influence standardization activities in the ISO or IEC context.
The following companies have already expressed interest and the need for this SIG: BMW, Bosch/ETAS, Continental/Elektrobit, Mercedes, Volkswagen/CARIAD, ZF and AVL.
I invite other Eclipse SDV Working Group members willing to join the SIG to state their intent by replying to this email.
Best regards,
Martin
