Reviews run for a minimum of one week. The outcome of the review is decided on this date. This is the last day to make comments or ask questions about this review.
Eclipse SDV-LVL
SDV has become an overused buzzword in the automotive industry with ambitions and capabilities declared by industry stakeholders as "software-defined" drastically differing. The ambiguity of the language hurts conciseness of discussion.
Eclipse SDV-LVL (Eclipse Software-Defined Vehicle Levels of Value & Lifecycle) provides a vendor-neutral framework for assessing the maturity of software-defined vehicles. This taxonomy establishes a common and stable terminology for classifying the technical capabilities of software-intensive vehicles and their impact on the customer experience. Additionally, it offers insights into key enablers—both technical and organizational—that influence architecture, development processes, and business structures essential for building such vehicles.
Just as the SAE Levels of Autonomy helped to level-set discussion on autonomous driving, the Eclipse SDV-LVL defines a common terminology/taxonomy for capabilities of SDV. In the field of highly automated driving the industry has converged to a concise language, where there is a universal understanding of what constitutes a Level 3 function. This project defines a comparable language.
To support industry-wide adoption, all descriptions and visuals developed in this project are made accessible and usable for day-to-day communication.
As a consequence of the primary goal (definition of taxonomy and stable language), Eclipse SDV-LVL maintains stability in the structure and semantics of its levels. When adaptations are necessary, the focus is on extensions and clarifications rather than altering fundamental meanings. Meanwhile, the perspective on enablers and key characteristics of software-defined vehicles will evolve over time to keep pace with technological and organizational advancements.
Furthermore, the project favors brevity and conciseness over completeness. Any taxonomy will exhibit grey areas which are expected. Rather than expanding the levels to cover a multitude of “shades of grey”, simplicity is favored. This also holds true to the section of enablers where a complete and unequivocal list is impossible to create.
The Eclipse SDV project scope provides the perfect set of stakeholders to agree on common terminology. Governance in the context of the Eclipse Foundation creates a low entry barrier for engaging into the discussion.
The existing content has already been used by other parties in various formats with suggestions for extensions or alterations. The Eclipse Foundation creates exactly the required discussion space.
The initial contribution will be provided in ASCII doc format for use of review and reusability and to keep the content clean of any company-specific branding. Existing visual assets are currently under review whether they can be contributed as well. Otherwise, some stakeholders already offered to create new license-free visuals. The initial contribution will be provided under the cc-by-sa 4.0 license.
- Log in to post comments
Just as the SAE Levels of Autonomy helped to level-set discussion on autonomous driving, the Eclipse SDV-LVL defines a common terminology/taxonomy for capabilities of SDV. In the field of highly automated driving the industry has converged to a concise language, where there is a universal understanding of what constitutes a Level 3 function. This project defines a comparable language.
To support industry-wide adoption, all descriptions and visuals developed in this project are made accessible and usable for day-to-day communication.
As a consequence of the primary goal (definition of taxonomy and stable language), Eclipse SDV-LVL maintains stability in the structure and semantics of its levels. When adaptations are necessary, the focus is on extensions and clarifications rather than altering fundamental meanings. Meanwhile, the perspective on enablers and key characteristics of software-defined vehicles will evolve over time to keep pace with technological and organizational advancements.
Furthermore, the project favors brevity and conciseness over completeness. Any taxonomy will exhibit grey areas which are expected. Rather than expanding the levels to cover a multitude of “shades of grey”, simplicity is favored. This also holds true to the section of enablers where a complete and unequivocal list is impossible to create.
- Log in to post comments