Skip to content

Model Based System Engineering

Model Based System Engineering

Today, tools and modeling languages supporting MBSE are not developed to deliver configurable models that can dynamically produce digital twins in pace with the real products to be delivered and lifecycle-managed.

Despite significant advances in modeling languages like SysML 2.0, current MBSE solutions have serious problems providing support for capabilities essential to navigate complexity such as system and product variability.

While transitioning from document-based to model-based systems engineering may be a significant step for many, it is indeed high time to take the next step. The new big thing that significantly impacts MBSE is that models in the form of digital twins, reflecting the real product throughout its lifecycle, need to be created and managed in a scalable manner.

Today, tools and modeling languages supporting MBSE are not developed to deliver configurable models that can dynamically produce digital twins in pace with the real products to be delivered and lifecycle-managed.

The Requirement, Functional, Logical, and Physical (RFLP) approach, often used in MBSE is aiming to translate customer requirements more effectively into specifications for physical realizations. However, the RFLP is a waterfall methodology and was developed at a time when a significant portion of the definition model didn’t need to be dynamic, supporting their digital twins with configuration and simulation knowledge throughout their entire lifecycle.

Furthermore, the approach was clearly developed at a time when software and servitization didn’t dominate the development to such a high extent.

In this increasingly complex world, MBSE must now assume a much greater responsibility to deliver and manage dynamic models throughout their lifecycle in a scalable manner. Moreover, MBSE must take on the responsibility of configuration management in an increasingly software-focused world, where traditional 150% Bills of Materials (BOMs), designed for physical products, fall short.


From now on, MBSE must be based on robust modeling capability enabling dynamic and model-centric handling of system requirements, design, configuration, simulation, verification, and validation of products and services, including their digital twin counterparts, throughout their lifecycle. This can only be achieved with the help of new metagraph technology that can handle abstractions, configurations, and multi-dependencies in a much more effective manner.

About MBSE

Model Based Systems Engineering (MBSE) is an approach to systems engineering that emphasizes the creation and use of models as primary artifacts to support system requirements, design, analysis, verification, and validation activities throughout the system lifecycle. Compared to previous systems engineering approaches, which primarily relied on document-centric methods, MBSE has resulted in several improvements, including visualization, collaboration, and reusability. 

Let’s start the
conversation!

Let’s start the
conversation!

Through comprehensive data integration, enhanced metadata management and improved data quality inorigo® reinvents Data Governance. Secure data sharing is facilitated, promoting transparency and accountability.