11:09
EM.411 meeting Eric Rebentisch System Engineering
Model based engineering
Model-based systems engineering
Common frameworks
SysML
OPM
UML
Doors NG
Common tools
OPCloud
Matlab
Modelica
Microsoft visio
3D experience
Etc
Similar to Generative design
Airbus
Digital design manufacturing and simulation
Roller coaster tycoon seems like a pretty good system model
Or simulator
NASA JPL created a total integration environment
OpenMBEE
integrated things like
Github
Jira
Jupyter
Cameo simulation
Docker
Turn the systems engineering V into a Diamond
The real world V gets mirrored in a parallel digital pipeline
Are we modeling the product or the process?
Either, both
Model process to model a product…?
Often the process is the product
In software, the gradient between model and product is more blurry
Maybe that also makes it harder to justify modeling, it feels more productive to focus on the product directly
But the product is essentially a robust model
First do system engineering, then build a model
Musk’s Principles of System Design
Make requirements less dumb
Delete the part or process
Simplify or optimize the design
Modeling is when the place you document is the same as the place you think about and examine
“Documenting with style”
Model based enterprise
Digital twin
Digital thread
requirements are typically how engineers communicate
Communication between organizations should be the flow of requirements
System engineer delivers system technical solution
System architecture delivers system concept and plan
Program manager delivers value to the system stakeholders