The transition to model-based system engineering (MBSE) is a key step for organisations seeking to improve the efficiency of their teams, the traceability of the work and collaboration in their engineering projects. However, migrating to MBSE is not just about adopting new tools – it also requires a transformation in the way that organisations approach their systems development. Many teams jump into using MBSE expecting instant improvements, but without proper preparation and guidance, they will encounter many challenges in the process.
Are you ready for MBSE? This post will help you answer that question by outlining the key aspects you should consider, such as organisational culture, team capabilities, integration with existing processes and tool selection. Evaluating these factors can make a huge difference in a successful transition to MBSE.
By Paloma Maestro Redondo, System Engineer and Project Manager
How do I know if my team is ready?
Before implementing MBSE, we recommend you assess several key factors, with support from experienced users, if available.
Firstly, evaluate the complexity of the project to determine whether a model-based approach is justified. MBSE provides the greatest value when dealing with intricate, multi-disciplinary systems where traceability and system integration are critical. If your new projects involve changing requirements, multiple stakeholders and a complex system life cycle, MBSE can significantly enhance the efficiency and the quality of the work to be done. However, simpler projects might not require such an extensive framework, especially in the early stages.
It is just as important to consider the readiness of your team. Shifting to a model-based approach involves moving away from traditional document-driven processes and this can present challenges. Team members must be willing to embrace change, learn how to use new tools and collaborate more proactively within a digital environment. Without adequate training and sustained support, resistance and misunderstandings can slow down progress.
The existing structure and organisation of a company or a team can also play a crucial role. MBSE demands a structured yet flexible approach to processes to ensure the new modelling activities integrate seamlessly with existing engineering workflows and tasks. Organisations should assess whether they have the right mechanisms in place to maintain model consistency, version control and data integrity across teams and departments.
Laying the groundwork for implementation
After you have assessed your team’s readiness, the next step is preparing for the transition. A structured plan will make the change easier. The key steps are:
- Set clear goals – Decide what you want to achieve with MBSE. Do you want better traceability, streamlined design processes or improved collaboration? Having specific goals helps align efforts across teams.
- Invest in your team’s training – Give your team(s) the skills they need by offering workshops and training sessions tailored to their needs. MBSE adoption is not just about the tools, it’s about developing a new way of thinking, so you might need to give newcomers some initial time to adapt.
- Choosing the right toolset – Tools like CDP4-COMET and Capella offer various functionalities suited for different kinds of projects. When making your choice, consider how easy or difficult they are to use compared with your team’s experience, how well they can be integrated and how their use can be extended in future phases.
- Begin on a small scale – Start with a pilot project or a simple concept to test the approach. This will help the team to get used to the new way of working and make sure that everything is done properly before introducing it more widely.
- Getting all stakeholders on board – For MBSE to be adopted successfully, it requires support from leadership and senior management teams, as well as alignment across different departments. It’s important to clearly communicate the benefits and challenges from the beginning to ensure everyone is committed and has a clear scope.
Overcoming challenges along the way
Resistance to change is one of the most common problems when adopting MBSE. Many teams are used to working with documents and may be unsure about switching to digital models. But if you get the right people involved early in the process and demonstrate how it can benefit them, they’ll be more likely to feel confident about it.
Another challenge is the learning curve associated with MBSE tools. While some of these tools are really powerful, they require proper training and continuous support to make sure teams can make the most out of them. It is a good idea to invest in training courses and to encourage people within the company to become MBSE specialists and create an internal community, as this will smooth the learning process.
Finally, organisations must think carefully about the initial costs of MBSE and how it will benefit them in the long term. While the costs of training and using the tools might seem high at first, the benefits – such as fewer mistakes, better traceability, faster development and better decision-making – usually make up for that.
What do we model first?
Once you have the required IT infrastructure in place to apply MBSE and the teams are trained and organised, you can get started with the modelling activities.
It’s important that engineers don’t work in isolation because they will need to exchange ideas in order to come up with the right design decisions. We therefore recommend starting with an agreement on the concept of operations, as this will lead the development of the requirements and the design. You need to get a clear understanding of the objectives to define a clear ‘functional decomposition’ (breaking down complex needs and processes into individual functions – the new sub-functions – that are more manageable and easier to understand).
Some of questions you can ask the engineers, customers or any other stakeholder to guide the initial design are:
- What should my system do?
- What are the main requirements and design drivers?
- What will drive the performance of my system?
- Do we need to consider any rules, norms or standards for the design?
- Are there any operational or environmental constraints? Do we need to consider external factors?
- What are the critical systems and interfaces?
When creating the first draft of the model, you can use sketches or diagrams to ensure that you can get feedback from other users or stakeholders who won’t participate in the modelling activities. This will be then translated into the first shared baseline model that should be developed jointly as a team. You can include simple elements at first, such as engines, structure, power storage, main functions and so on. And you can also start considering a few options and discarding others.
Once you have completed the first steps, you can start new iterations of the product tree and refine the high level requirements initially identified. The next task would be to populate the model with data and create some computational budgets, as well as rules and mechanisms for automated verification of the design and requirements. This process will lead to new iterations and trade-offs that should be reported and discussed within the teams.
In summary
Here are three key points to remember:
- Adopting MBSE shouldn’t be a technical decision made by managers – it’s a strategic change that impacts every aspect of a project, from concept development to operations.
- Also, MBSE isn’t just about using a different tool – it’s about transforming existing processes, rethinking workflows and fostering a new engineering culture.
- Understanding your organisation’s readiness before you dive in can help you avoid costly mistakes and ensure long-term success in future projects.
By evaluating your project’s complexity, team readiness, process maturity and tool readiness, you can decide whether MBSE is right for your project and/or organisation. A phased approach – perhaps starting with one or more pilot projects – investing in training and fostering a culture of collaboration, can make the transition smoother and more effective. This will ensure your teams get used to the new methodologies and tools, and allows time for any existing processes to be adapted and integrated with the new approach.
At Starion, we specialise in helping organisations to navigate the complexities of MBSE adoption. Are you ready to move from documents to models and unlock the full potential of MBSE? Let’s find out together!
Find out more
Follow Starion Group on LinkedIn to find out when new posts are published.
Find out more about MBSE at Starion.