Learn More
Start the MBSE journey by defining an integrated product architecture
During large development programs, problems are mostly introduced at the crossing between domains, organizations, disciplines, and more, for misalignment due to using different tools and processes, or for not clearly understanding the overall requirements when making decisions on subsystem-level. OEMs can only address such challenges properly if they take control from the beginning of each development cycle, at the concept stage. With MBSE, they can do so by generating an integrated product architecture, an early blueprint of the machine that defines how various subsystems will interact with each other and with systems in their environment. Starting from this architecture, they can cascade down requirements from the top level to all domains, while keeping both levels linked. MBSE will make everyone’s role in the wider picture clearer and avoid confusion about the exact signification of requirements on subsystem level, making objectives less open-ended.
Continuous verification and validation of complex multi-domain systems
It’s important to keep this integrated view throughout the entire development process, especially when designing the new generation of software-driven, electrified, highly connected machines. Those generally have a greater variety of subsystems and more and stronger interactions between those. Deploying an MBSE approach will help OEMs to get all stakeholders in the development program on board to work on the common goals and develop a strategy for continuous verification and validation of the overall system using dedicated testing scenarios. Having all stakeholders make subsystem-level decisions based on system simulation while monitoring their impact on the overall requirements, as enabled by MBSE, will avoid errors because of inconsistencies or incompatibilities at the interfaces. And even if mistakes would still slip through the net, the odds of catching them early enough are much higher thanks to continuous verification and validation using MBSE.
Connect all development stakeholders through MBSE, including suppliers
New digital technologies and software are very different from what most OEMs are familiar with and often come from suppliers that are new to their ecosystem. Moreover, when OEMs are operating globally, they usually even engage with various suppliers for one and the same component. To do this confidently, they need an efficient machine development methodology that lets them guarantee compliance and compatibility across the board – for all possible configurations, regardless of the supplier. Through MBSE, OEMs can establish a dynamic digital connection with suppliers through which they can share portions of their system models with them - obviously with full protection of intellectual property (IP) - and through which they can receive all types of information regarding supplier subsystems. As such, MBSE helps OEMs and suppliers align their processes and continuously collaborate, thereby helping them achieve their common goals more effectively.
Leverage MBSE to design for reliability and sustainability
Because of growing machine complexity and continuous software updates, it’s becoming increasingly necessary for OEMs to focus on reducing the risk for compatibility and compliance issues as well as other problems that may occur during any stage of the product lifecycle. By following an MBSE approach, OEMs can better protect the overall quality of their machines. MBSE lets them consider core requirements like reliability, availability, maintainability, and safety along with other design priorities, including sustainability, already at the concept stage, when they can still have an influence on architectural choices. Besides, MBSE also dramatically reduces the risk for introducing mistakes by using a unified data model at the interfaces across domains. Finally, MBSE allows OEMs to manage and track all activities for continuous verification and validation of the machine design for compliance to the overall requirements, both during machine development and beyond.
