<img height="1" width="1" src="https://www.facebook.com/tr?id=1599948400306155&amp;ev=PageView &amp;noscript=1">

Breakfast with Experts Recap: How ALM is Transforming Automotive Design

Intland Software is working with leading innovators in the digital mobility sector, and our solutions are used by the top 5 German automotive OEMs. As part of our commitment to driving the future of automotive systems engineering, we recently threw a Breakfast with Experts event in Sweden. Read on for a quick recap!

Through events like our Breakfast with Experts: How ALM is Transforming Automotive Design event on 22 Sep in Göteborg, Sweden, we aim to facilitate the sharing of knowledge among those driving the future of digital mobility. Due to the pandemic, we offered limited seats for live attendees, but are proud to share details of the successful event in this blog post. For this event, we were joined by leading Swedish automotive technology supplier Veoneer, and US-based Product Line Engineering experts BigLever. Read short interviews with the speakers from both innovators below!

ALM Use Cases and Migration Experiences

02-IMG_1686Veoneer’s Director of Engineering Tools Dag Abrahamsson gave a talk titled 'ALM Use Cases and Migration Experiences in Automotive Engineering'. We talked to Mr Abrahamsson about Veoneer’s path to integrated ALM!

Please describe Veoneer’s journey that led to the selection of codeBeamer ALM at the company!

Dag Abrahamsson: Before switching to our modern ALM solution, our teams had been relying on a toolset that can be considered typical in the automotive industry. Our teams used a number of standalone tools for requirements management, task and issue management, test management, etc. We felt that our toolset was limiting innovation because of outdated user interfaces and partial coverage of the entire V-model.

When you’re trying to ensure adequate quality management and compliance with ASPICE, ISO 26262, and IATF guidelines, you quickly realize suitable tooling is essential. You need traceability, you need clear connections in your entire development chain, and you need to know what you’re basing your design decision on. That’s the key reason we wanted to reduce the number of tools we used, and that’s why we needed a modern tool that combined all these aspects of product delivery.

Veooner found codeBeamer ALM to be the best choice mainly because of its flexibility. We also appreciate working with an independent vendor where you know you’re not one of thousands of customers: you really have a chance to influence product development. Finally, we knew that codeBeamer was built from the ground up with bridges and connections to other tools, which needless to say is very important in such a complex development environment.

What were your experiences about the process of migrating to codeBeamer ALM?

DA: When you have a number of parallel-running projects, you can’t just switch to ALM overnight. We spent about a year gathering requirements for our future tool and evaluating vendors’ offerings. Then another half a year on a pilot project before a decision was made, followed by another 6 months of rollout and configuration work. My estimate is that the whole ALM implementation project from end to end takes about 3-4 years altogether – which makes sense if you consider that it’s a decision of strategic importance and long-term benefits.

While it was a lengthy process, it didn’t mean a disruption to our processes. We weren’t forced to change tried and tested processes, and were able to rely on a combination of out-of-the-box integrations, built-in data migration facilities, and Integration-as-a-Service solutions to tackle the migration of development data internally.

Overall, as a result of this transition to ALM, we see major improvements in being able to tie together all parts of the development process. This gives us the traceability that helps us fulfil functional safety and security standards. codeBeamer ALM has also helped us align our development processes within the company, giving us a chance to advance our Agile transition.

ALM+PLE: Unifying Feature-based Product Line Engineering in Automotive Development

Brekfast-with-Experts-BigLever-Charles-KruegerCharles Krueger, CEO of BigLever talked about Feature-based Product Line Engineering (PLE) & ISO 26580 Compliance with the Intland codeBeamer ALM/BigLever Gears Bridge. We asked him how he saw the role of integrating ALM and PLE in the future of system-of-systems development.

What’s the role of Product Line Engineering in automotive systems development?

Charles Krueger: PLE has always been seen as a “nice to have”, but not necessarily a “need to have” capability. Some organizations still think they can get away with ad-hoc methods in an increasingly competitive market environment.

Consider this: when an organization is building complex systems, the amount of time spent managing product variations consumes about 2/3 of the time of engineering teams. This has a huge impact. Imagine what you could do if you could remove all that low-value work from your engineering teams’ daily activities, and have them focus on high-value work instead!

The same applies to traceability, good requirements, good processes, which is the domain of Application Lifecycle Management platforms. When using a system like codeBeamer ALM to improve the formality of their lifecycle, organizations reap a return on investment that is much greater than the time required to roll out and maintain such a solution.

How do you see ALM and PLE working together in complex systems engineering?

CK: It’s that complete umbrella of systems engineering processes that need to work together, incorporating electrical, mechanical, and software development. Almost all the different engineering tools used over different parts of the lifecycle have some way of dealing with variability in artifacts in product families. But each of them have their own notion of the truth of what variability is, and how it impacts the lifecycle.

What PLE tools do is that they provide a single, authoritative source of truth about the variation that exists in the product family. The role of integrating ALM and PLE is to provide a common concept that can be used across all the different tools used in managing requirements, code, design, documentation, etc across the entire systems engineering lifecycle.

What are the tangible benefits of taking this approach to unify the lifecycle?

CK: Based on BigLever’s experience, we find that when engineers adopt this approach, their defect rates can be reduced by 80% or more. Development velocity, or the amount of work that engineers can get done over a period of time (adding new capabilities and just getting products out the door) can be tripled by removing manual, ad-hoc, informal processes. This allows teams to focus on creative, innovative work that’s not happening today because you’re focusing on error-prone manual activities.

Another big benefit organizations see is related to regulatory compliance: by following formailzed good practices, developers eliminate opportunities for errors and omissions. They can reduce risks to safety and eliminate misunderstanding across the lifecycle, and that has enormous impact on improving ISO 26262 and ASPICE effectiveness. I’m part of the INCOSE (International Council on Systems Engineering) team developing ISO 26580, the upcoming international guidance on feature-based Product Line Engineering.

 

Let us say thank you to our speakers delivering powerful talks, as well as all those in attendance at Intland Software’s Breakfast with Experts event! To learn more about how ALM is being used by leading mobility innovators, browse our automotive case studies, or watch a quick video about our ISO 26262 & ASPICE Template below: