Model-Based Systems Engineering

Model-Based Systems Engineering creates a unified model for your project. Everyone can easily find the information relevant for him/her in their own, customized view and is informed about the whole project without handling more than one tool environment.

What is Model-Based Systems Engineering (MBSE)?

MBSE is the future of Systems Engineering. It will save two of today’s most important resources – time and people. Guiding through a project can be intuitively and simple.

In the development phase of a product there is a continuously growing complexity. To cope with this huge amount of information, MBSE helps with easy navigation through the used tool and speed up the information flow to every department. The SE process becomes more dynamic and manageable.

The shift from document-centric to model-based working processes involves:

  • Model structuring
  • Support requirements from system level down to components level, e.g. Hardware
    • Higher- and lower-level Design
    • Safety, Security, and virtual analyses
    • Verification and validation activities

The complex phases of MBSE

Phase 1

Think of the complexity of your development process like a family. It starts with the simple life of the child: You define, in your development process, what the expected outcome is.

Phase 2

In the main part, parents take over the process and manage the relationships between the 4 complex areas, calculate the risks, e.g. with FMEA/TARA, FTA, HARA and perform virtual analysis to find the best way for their child – your product.

  • This is also a shift in complexity that is being driven into hardware and software.
  • The complexity of policies is the continual increase in requirements, e.g., security and cybersecurity concerns, create a huge volume of documents and data under ever-evolving policies.
  • The consequences are increased complexity of system elements and increased complexity of sub-systems of systems embedded in their networked environment.

Phase 3

In the end, we come to the grandparents who doubt the process and cite the performance of a test as evidence.

A project can involve hundreds or thousands of people, all of whom need an overview, understand the system architecture, and deal with various change requests. How are you going to manage the family – the big complexity?

At this point, MBSE helps your organization to one view for each member, when a change occurs, engineers are able to adapt their work faster.

The Evolution of Systems Engineering

Document-based, Document-centric
  • The team focuses on writing, reviewing, updating, and releasing sequential steps
  • Limited traceability of changes and design concepts
  • Huge number of documents
  • Retraceability must be established with multiple tools
  • Documentation is dependent on personal skills
  • Needs clear information processing in detail to organize the project
Model-supported, model-centered
  • Knowledge is contained in models and documents
  • Trained in systems engineering process
  • Relevant people are trained in systems architecture modeling, e.g. SysML
  • Less information is contained in documents
  • Everything is linked via multiple tools
  • Navigating through the project via documents and project experience
Model-Based Systems Engineering
  • Documents do not contain important knowledge for the project, but some documents may still exist
  • Trained in the use of Model-Based Systems Engineering
  • The process has a clear universal data set
  • Process has different perspectives for departments, based on the model used
  • Use of a defined toolchain with multiple perspectives for each department to manage the vast information
  • Use as an interface “gateway” to transfer relevant information
  • Changes are visible to everyone who is affected

How INVENSITY supports you on your way according to your status quo

Option 1
INVENSITY figures out your status on the evolution towards MBSE
  • We take a close look at your development process
  • We interview your relevant stakeholders, process experts and development managers to create a common understanding
  • We uncover potential in your development process and the toolchain you use
Option 2
INVENSITY trains your relevant members in using MBSE
  • Develop a MBSE coaching based on your current situation
  • Support the understanding through a basic example
  • Work out next steps for your development
  • Training in system modeling language SysML.v1/v2
Option 3
INVENSITY supports during the implementation of MBSE on a project
  • We execute organizational change for you with our Center of Excellence “Process Transformation”
  • We support you in change issues
  • We support you in methodological and technical issues in the project
  • We develop an MBSE approach with a/your tool setup

Project References

Do you have questions about Systems Engineering, or are you considering hiring external support?

Please feel free to contact me at any time. Click on the button below and easily choose a time slot so that we can discuss your project without obligation and free of charge.

Jan Zutter
Head of Systems Engineering