Christoph Hinrichs

Clear MBSE strategy and thorough testing of the tools

Webasto did not want to leave anything to chance when entering MBSE. Therefore, a clearly structured modelling process was defined (MBSE Meta-Model), the language to be used was defined (SysML) and the appropriate tool was selected in a very elaborate back-to-back comparison. “We were not satisfied with our previous solution and in a very open and selective tool comparison, Enterprise Architect clearly convinced us with the best cost-benefit ratio,” Hinrichs describes. The continuous responsiveness of the LieberLieber team with regard to open questions also left a very positive impression: “Since we always want to have the latest tools in use, we quickly switched to Enterprise Architect 16. LieberLieber supported us very well in this and also updated LemonTree promptly so that we could continue to use the whole tool chain.” In the end, LieberLieber’s recommendations regarding the tool chain were adopted, but Git was replaced by IBM RTC.

Dr Konrad Wieland, Managing Director of LieberLieber, comments: “We are very pleased that Webasto has chosen the path towards MBSE together with us. Christoph Hinrichs is approaching this major task in a very clearly structured way and gave us interesting insights into his pioneering work at the MBSE Summit 2022. We are united by the common goal of communicating the benefits and advantages of MBSE in a comprehensible and practice-oriented way and thus successfully convincing people. In this way, we are creating a good and robust basis for the continued economic success of the outstanding family-owned company Webasto!”

Communicating the benefits of MBSE throughout the company

For Hinrichs, it is clear that the greatest benefit of MBSE only comes when the process has been rolled out throughout the company and is working. This is confirmed by scientific studies and practical experience alike. “As usual, we first launched pilot projects to show what is possible with MBSE and what benefits arise from it. The experience gained is then processed – as in the Business Unit Batteries Department – and shared with the business units. Now we have to scale these experiences and anchor them in the business sections. For this, however, we still have to do a lot of convincing with the support of LieberLieber,” explains Hinrichs.

The most important advantages of MBSE were defined as:

• Transparency – recognition of dependencies, Defined starting point for cooperation.
• Traceability
• Visualisation – common language and the appropriate tool for each case
• Reusability and automation – Multiple use of artefacts and models; Automated consistency check of models
• Quality – Higher product maturity through semi-automated validation; Fewer errors
• Processes – Standardised processes facilitate collaboration; Certifications more quickly attainable

“The faster we integrate these points in the company, the more benefits we can derive from MBSE,” Hinrichs knows. However, it is important not to take any hasty steps, but to first check exactly what the current situation is in a department. Based on this, MBSE can be introduced in a well-controlled process without losing the necessary participation of all those involved by overtaxing them.

MBSE maturity level of a department is assessed in advance

In order to make the introduction of MBSE in other departments as smooth as possible, Hinrichs is developing an ever more detailed maturity model. Currently, there are very few publications and contributions that attempt to support the introduction of MBSE in a systematic and structured way, such as the work of Andreas Vogelsang. “There are studies on the collection of MBSE maturity levels, but no one talks about what effort it takes to reach a level or what benefits can be achieved with a level. In the practical test, for example, we found that the levels have to be as small and solution-oriented as possible so as not to trigger excessive demands, otherwise we would lose interest in MBSE or even meet with resistance. If we want to change something in the processes, methods or tools, we need a team that sticks together and pursues a common goal,” Hinrichs explains.

Key user as communicator for MBSE

As a central point of contact, a “key user” should be found in each department who is available as a multiplier and communicator for MBSE. The fundamental basis for scaling MBSE is the tool setup adapted to the needs as well as the configuration management. Hinrichs supports and disseminates MBSE within the company through internal training. This should help generate enthusiasm for the MBSE initiative at Webasto, establish initial contact and build up a network. If detailed expert knowledge is then required, or if the key user team encounters challenges in the tool, LieberLieber is available for this at any time. “Currently, three pilot projects are running in parallel, one of which is also already at a next higher level in the maturity model. So we are working intensively on establishing and scaling MBSE in the company. There is still a lot of work ahead of us and it is reassuring to know that we can always call in the experts from LieberLieber to solve difficult questions together if necessary,” explains Hinrichs.