When defining the scope for implementing model-based system engineering (MBSE) methodologies in new projects, it is essential that companies and all relevant stakeholders first assess the challenges of adopting a new approach and define possible solutions to help mitigate the associated risks.
Some of the challenges or risks might be particular to specific industries or projects, while others are common to most MBSE practices. In this post, we explain the most common challenges and outline potential ways to overcome them, based on experience and lessons learned from the application of MBSE to new domains and across multiple organisations.
By Paloma Maestro Redondo, System Engineer and Project Manager
Tackling cultural resistance and skills gaps
Any change of environment presents a challenge and this is particularly true when we start to apply new methodologies. Even if not viewed as one of the most significant barriers, it is usually one of the first impediments we encounter at the beginning of a project.
Why is this? Typically, teams who are used to traditional system engineering methods may be reluctant to change because they think the new approach will be an extra burden. Engineers and managers might be used to working using a document-centric approach, and to following standards and guidelines that cannot be directly applied in an MBSE context.
To integrate new ways of working, we recommend first ensuring effective communications within the teams – and with the top management involved in projects. It is usually also important to offer leadership support from the beginning, together with comprehensive training programmes, to ensure everyone is aware of the new approach.
To build the required skills among all team members, they should take part in workshops and training sessions, which will help them to become familiar with the method and the new tools. In cases where there are big differences in the skills of those involved, we typically organise them into teams that include both experienced modellers and traditional engineers to facilitate knowledge transfer and collaboration.
Integrating MBSE with existing processes
MBSE requires specialised tools for modelling and simulation. Sometimes these may not work seamlessly with the systems and software already in use within an organisation. This can lead to inefficiencies and frustration among users, which might cause delays in delivering results.
To avoid this happening, it’s essential to carefully evaluate the MBSE tools being considered to ensure they align with your organisational needs and existing workflows. We recommend opting for tools that offer robust integration capabilities, have good interoperability and are compatible with the other tools being used.
One solution is to consider incremental adoption and gradually introduce the tools. An approach typically followed by large organisations is to start with one or more pilot projects, during which the teams identify and resolve potential integration issues before the methodology is deployed for other projects. Our advice in this case would be to invest initially in defining proper integration strategies and develop clear transition plans to facilitate the required shift in the way of working.
Managing complexity
MBSE is designed to help manage system complexity, but the modelling process itself can become complex and unwieldy, particularly in the context of large-scale projects.
Before a project starts, the core team must define the scope clearly in terms of what needs to be designed and developed, as well as the extent to which the methodology and tools are to be used.
Clear modelling guidelines and conventions also need to be defined and agreed early in a project to prevent the need for additional modifications at a later stage. The first steps include breaking the system down into manageable components and using modular modelling approaches.
Dealing with data management and maintenance
One challenge that is not specific to MBSE but still needs to be considered is how to deal with the management of data and how to reduce the risks related to version control.
Models usually need to be maintained and updated by different people, not only within an organisation but also when collaborating with external entities. The methodologies followed should therefore implement effective change management processes and you should always ensure that mechanisms are in place to update and maintain models as the system evolves.
We recommend using tools that support efficient data management and implementing robust version control and configuration management practices in all engineering teams for the complete project life cycle.
Encouraging collaboration
MBSE is designed to facilitate collaboration between multiple stakeholders. However, teams might not be homogeneous in terms of their domain-specific knowledge and expertise in the MBSE methods and tools being used. In addition, interdisciplinary collaboration might be a challenge for new teams. Both factors are why it is important to select the right managers and leaders from the beginning of a project as they should be responsible for organising the teams and promoting collaboration by taking the lead.
We also advise selecting tools that support collaboration; if possible, even allowing team members to work and review models concurrently. When working with larger teams, it is crucial to promote a common understanding of ‘the model’ among them and between teams.
(Later in this series, we’ll publish a blog post dedicated to collaboration in MBSE, so stay tuned to find out more on this topic.)
In summary
The transition to MBSE represents a significant shift in approach that promises substantial benefits in the management of complex systems. However, there are a number of challenges to be addressed, including cultural, technical and financial obstacles. By fostering a culture of continuous learning, selecting and integrating tools wisely, addressing skills gaps, managing costs strategically and breaking down system complexity, organisations can successfully transition to a model-based approach and reap its rewards.
We have summarised some of the most common challenges here and the recommended practices to overcome them. You might need to adapt the solutions depending on the context of your organisation and the project, but it is important to use a clear approach and have all the required tools to anticipate to potential problems.
If you would like to discuss any of these issues or ask about others, please get in touch with our digital engineering experts.
Find out more
If you want to learn more about the MBSE methodology and tools, follow Starion Group on LinkedIn to find out when new posts in this blog series are published.
Discover our range of MBSE services and solutions.
