One single simulation model in development deployed broadly across organization is beneficial in order to reduce effort in maintenance, and to ensure consistency, and possibly multi fidelity.
To run simulation over multiple simulation environments one needs to separate the model from the execution environment.
Remedy is separation of model and execution environment:
so that one model supports multiple execution environments
and one execution environment can be used by multiple models, these models can be multi fidelity
Define one model (modeling = cost), and deploy it broadly (deployment = benefit)
One model is good to reduce effort in maintenance and to ensure consistency
Cost for model consists of maintenance of model, and data base (cost for maintaining data base is Klomps cost).
After having one model, having one data set is to support multiple models is second best
Modelon can support by delivering models in various formats
Executable, with or without execution environment
FMIE
FMIT
FMI .NET or FMIL
CarMaker
Batch simulations etc. Here we should mention jenkins and others
OTT
Model authoring environment, for generation of executables
If one OEM has two models, one high fidelity and one medium fidelity, they can both be applied in Matlab/Simulink. What would it take to make them available broader and what would the value be? Other applications include:
Execute models in Microsoft Excel, can easily be customizable to support various engineers standard work
Batch/cluster simulations for DoE, variant management and more
Connect to CarMaker for virtual test driving
Run in Matlab for custom analysis control design
Steady state/performance optimization
Driver-in-the-loop
Virtual test (KnC and others)
Topology built in VDL based on standard components
Default data
Swap in components with data access
Data read at runtime, no recompile needed to change data