Saving Time with Computational Parts in MSC Apex

Published 2015-08-17
WRITTEN BY:

The power and cost saving aspect of using Computational Parts can be seen in this quick test.

In a quick comparison, a second assembly analysis of 8 parts took only 63% of the time compared to the initial analysis. This was made possible by the computational parts that MSC Apex creates automatically when solving assemblies.

graph

In this example of an assembly of 8 parts, it took 100 seconds from start to finish when solving the model the first time, while it only took 63 seconds to solve the complete model a second time after modifying only one of the parts.

To check how much time computational parts save you, simply access the solver log of each analysis here:

Double click on the solver status item of the relevant analysis in the study tree (you have to close the model results first).

solver log access

This will open a detailed log:

solver log

From the log, simply select the first line entry, scroll down to the last line, hold down SHIFT on your keyboard and the select the last line.

solver log2

When all the lines are highlighted, simply copy and paste the data into Excel for comparison.
The third column (second column shown here) of data shows the duration for each step, the summation of which produces the time of the complete process.

In this extract the steps during the creation of each computational part can be seen:
solver log3

In the second analysis (after only modifying one part), 7 of the 8 parts are simply re-used and only the 1 computational part re-calculated.

Modal results:
modal

Static results:
linstat

This time saving of 37% is an indication of the typical time saving achievable on similar models but may vary from model to model.

I think this is...