The increasing complexity of cyber-physical products and their development involving interdisciplinary and distributed teams, raises the importance of modelbased processes, methods, and tools. In Model-Based Systems Engineering (MBSE), the system model serves as the single-point-of-truth for the product description across all engineering domains.
Industry has adopted formal modeling languages such as SysML (Systems Modeling Language) to create system models in MBSE. However, this leads to challenges when it comes to connecting authoring tools seamlessly with neighboring disciplines like Requirements Management (RM) or Product Lifecycle Management (PLM) systems. Additionally, access to the model content is difficult for stakeholders from engineering domains as well as management due to the need of an authoring tool.
SysML v2, the next generation of the Systems Modeling Language, is designed to support the evolving practice of model-based systems engineering (MBSE) and to address the challenges posed by increasing system complexity and technological changes.
Participating organizations dealing with Systems Engineering now must develop a strategy for the near future, while there is already significant interest in the adoption of SysML v2 and planning of pilot projects within the industry. Depending on the current situation, if the organization is already working with MBSE, the following two scenarios have been identified and detailed based on use cases and requirements:
Scenario 1: Introduction of MBSE
If an introduction of model-based development, or Model-Based Systems Engineering in particular, is planned or ongoing, the decision for a modelling language is a crucial point. Since the modelling language is in principle independent from the selection of the modelling tool and the method, in practice the selection of these so-called Three Pillars of MBSE is not free of mutual constraints. None of the available tools at the market can work with every language, thus there are technically limited combinations of tool and language. Additionally, the selected tool (and hence the modelling capabilities) and the language pose significant implication to the applied method
Scenario 2: Migration
If a company already has profound knowledge of MBSE and possesses a significant amount of digital data stored in models (e.g. SysML v1 or a tool-vendor-proprietary language), a strategy whether at all and if so, how to migrate to SysML v2. Both the timing and the selection for a tool accompanied by the assessment of necessary changes to the method are important points. A readiness assessment should first evaluate the organization’s current MBSE maturity, as organizations currently struggling with foundational SysML v1 practices may find the transition premature.
SysML v2 is the new standard notation for MBSE and eliminates some of the main shortcomings of SysML v1 (and to some extent of other non-SysML based languages) through a more formalized, expressive, and integrative language, aligned with modern software engineering practices. Organizations planning to adopt SysML v2 must consider the introduction not only as a pure technological upgrade, but as an organizational change process requiring strategic planning, tool chain integration and investments in tools and Human Resources. Thus, the prostep IVIP organization started a new project group on SysML v2 and all members are invited to join the working group to enhance processes and methods to drive innovation, develop systems and collaborate successfully in future using MBSE
The challenge in initiating the new working group in 2025 was on the one hand side to generate interest and ensure the participation of companies in the following year. On the other hand, it was necessary to jointly coordinate and approve the scenarios, use cases, and tasks as a mandate for the project work in future.
SysML v2, the next generation of the Systems Modeling Language, is designed to support the evolving practice of model-based systems engineering (MBSE) and to address the challenges posed by increasing system complexity and technological changes. SysML v2 will increase the effectiveness and adoption of MBSE and enhance the way engineers conceptualize, design, and manage complex systems.
The SysML v2 project group gathers industrial requirements and use cases regarding modeling and tools, prioritizes them and offers recommendations for their implementation. Based on practice-oriented use cases, it examines how SysML v2 can be used best in industry and what needs to be done in the future in terms of collaboration. It is intended that the results be incorporated in best practices for collaboration between development partners (e.g. OEMs and suppliers in aero or auto industry) and be submitted to the respective committees for enhancing SysML v2 language on one hand side and tool vendors on the other hand side.
In order to establish new working group, joint initiatives (e.g. workshops, round table discussions and panel discussions at Symposium) including support from different stakeholders (e.g. board members, other project coordinators, engaged members) were actively supported to prepare the ground for SysML v2 working group in 2026.
“SysML v2 tackles the challenges of system complexity of cyber-physical and software-defined products.” Sven Kleiner, :em AG
We are eager to help you with any questions concerning your project or selection of publications
TELEPHONE HOTLINE
+49 6151 9287-336
For more inspiration, news and information about prostep ivip.
