Model Based Systems Engineering (MBSE) has become a hot topic in recent years in the general field of engineering. It is used to define a wide palate of different tools, methodologies and approaches to engineering, and is not limited to the realm of simulation. Therefore, in my experience, the process, stage of development or even outputs can’t be assumed when talking about MBSE.
This blog post is going to go over my interpretation of MBSE and how VeSyMA sits in that realm, going over the stage of development, process and outputs. I will also touch on how it can be used in wider MBSE, ModSim or Virtual Twin approaches to development.
Model based systems engineering
I’m a rather literal person, so when I read that I break that down into individual terms:
- Model Based – Breaking something down into individual sub-groups, each with their own inputs, outputs, internal mechanisms and level of fidelity.
- Systems – Looking at how a wider system interacts with each of its sub components/systems represented at an appropriate level of fidelity
- Engineering – Investigation and development to improve, optimise and/or produce something.
To me that is the perfect definition of a System Simulation, such as VeSyMA, which simulates a vehicle, with each sub-system represented by a sub model that can be varied in fidelity, and assembled into a system that represents the vehicle as a whole, to support development, investigation and optimisation of that vehicle.
But I do appreciate that most people think of MBSE in wider applications, and in that case I like the definition by Johannes Storvik, TECHNIA Chief Solutions Officer, in his 5 Minute Overview of MBSE:
“A system model is a live representation of a system or product which allows for simulation of behaviours, as well as full traceability from requirements, to validated solution. Implemented properly, MBSE bridges the gap between the engineering disciplines”.
This definition incorporates a larger range of applications and methods that need to interact with one another to contribute to overall understanding and development.
How does VeSyMA contribute to MBSE
So, this is when we need to think about where VeSyMA sits in that “requirements, to validated solution” range.
In short, at every stage.
The idea that engineers need substantiated understanding at every stage means that you need to have tools that can investigate, develop and move with that development.
VeSyMA has been designed from the ground up to cover concept to late-stage analysis investigations, with each sub-system have basic representations and high-fidelity, subject and investigation specific models.
Figure: Example of the vehicle system, with each sub-system represented by an individual model, with its own tests, templates and levels of fidelity.
At concept stage, simple 1D analysis can be used to ask the “What if?” questions, and provide things like initial system requirements, performance characteristics and investigate capabilities.
During development, it can be used to test and develop systems, providing “Like-measured” data, reacting to changes in all sub-systems including fluid, thermal, mechanical and electrical models. Tasks such as developing controllers, providing more accurate load requirements, and optimising systems are commonplace.
Finally, late stage analysis can provide full durability tests, road load analysis, failure modes, and part selections.
With architectures that allow for any level of fidelity, the models can move with development without having to use different tools at each stage.
ModSim, virtual and digital twins
In a broad definition, MBSE, ModSim, Virtual Twins and Digital Twins all occupy the similar realms, describing the virtual representation of a physical thing or system. My understanding is that the difference between them is how much each term covers.
Whether that be virtual representation of the development and testing of a product (MBSE), virtual representation of testing an as-yet unmanufactured product (Virtual Twin), virtual testing of a currently deployed product (Digital twin) or the methodology in which different simulations and development software interact during development (ModSim).
Each of these definitions require testing of a system, encapsulating the effects of the changing design of sub-systems, preferably automatically updating, so that everything is current and relevant.
VeSyMA, can be used in standalone Dymola and also in 3DExperience, the latter allowing live interaction between databases and other simulation tools, for example for CFD, CAD, FEA, requirements management and many more, providing up to date analysis of the vehicle as a system, providing targets, performance analysis, system requirements and durability analysis.
Conclusion
While my definition of MBSE may be different to others, I think a vast majority of them require a virtual representation of the dynamics of a system to test, validate and develop. This also goes for Virtual and Digital twins, that rely on such a model, where VeSyMA has libraries to support that approach of development, whether working in a ModSim style or otherwise.
Taking Model Based Systems Engineering at face value, VeSyMA seems to be the archetypal tool, but when thinking in a wider application, the inclusion of VeSyMA in 3DExperience allows for the interactive, interconnected and automated development that is required to achieve today’s expected pace of development.
Written by: David Briant – Senior Project Engineer
Please get in touch if you have any questions or have got a topic in mind that you would like us to write about. You can submit your questions / topics via: Tech Blog Questions / Topic Suggestion.