Methodology |
Trimmed Body |
Single file vehicle |
Multi-include vehicle |
True full-vehicle |
Features |
Trimmed body |
Some suspension FE |
Keep subsystem FE in its own include |
An object-based assembly environment |
|
Test based loads on body |
Some PT FE |
Assemble the right includes to form vehicle model |
Seamlessly manage multiple representation |
|
Test based PT and suspension |
Typically do not include tire or driveline |
Only a crude assembly definition exists |
Seamlessly manage multiple connection states |
|
|
|
|
Seamlessly manage ID conflicts |
|
|
|
|
Functionality to create reduced representations |
|
|
|
|
Manage loadcase |
|
|
|
|
Manage hardware and analysis configuration |
|
|
|
|
Manage job submission and job history |
Advantages |
Able to iterate on trimmed body |
Able to iterate on suspension and PT somewhat |
Able to iterate on suspension and PT somewhat |
Able to iterate on all details of a full vehicle |
|
|
|
Subsystem handling is somewhat modularized |
Subsystem handling is fully modularized |
|
|
|
|
Can easily mix detailed and reduced representations |
|
|
|
|
Can quickly customize model setting based on loadcase needs |
|
|
|
|
Can quickly review and rerun past analysis |
Disadvantages |
Cannot iterate on suspension and PT changes |
Very difficult to connect subsystems given the details |
Difficult to manage ID conflicts between subsystems |
|
|
|
Have to keep one model for each loadcase |
Difficult to manage conflicts between detailed FE and reduced models |
|
|
|
Very difficult to update or tune subsystem models |
Difficult to check for errors |
|