Validation data for Out Of Box functionality for Creo

[lgrant]

PTC, please publish some kind of Validation data for Out Of Box functionality for Creo. We are not asking you to devolve any code or trade secrets here,  just provide evidence that all the features work as expected.

Creo tools have become a thorn in our side and a hindrance to upgrade.

Here is our problem. We upgraded from Wildfire Pro-E to Creo 2.0 and were able to Validate the basic drawing functionality but the issue is the far more complicated feature of Tolerance Stack-Up and Mass Proprieties. These are OOB tools within Creo and we (as we do not have SW engineers) have no reasonable way of validating them. The result is that cannot use those features.

For Tolerance Stack-up:

We could do a simple calculation by hand (2, 4, 5 dimensional stack-ups - positive and negative) then compare to the result from Creo, then a more complicated calculation and from that conclude that any calculation Creo makes is correct.

For Mass Properties:

Perhaps compare the actual parts built?

As you can see, nothing that looks that solid. The best solution would be if we could just point to publish data from PTC and allow PTC to keep that up to date per release/upgrade.

If anyone else has some ideas on validation of Creo it would be incredibly helpful.

[TomD.inPDX]

Other than published white papers or an in-depth description of all allowable assumptions by the algorithm will satisfy the statisticians who will take the matter to court if need be.

But you are right in that too many people blindly take the data presented and use this at the next level of evaluation.  Too many things can go wrong.  Fortunately, for matters of safety and margin, qualified and certified engineers are often required and they will use systems that are properly vetted at every level.  If someone is trained to use PTC solution for FEM solutions, for instance, they are also trained to understand how the data is interpreted by the software.  They have a vested interest to know.  Their license and their integrity is on the line at that point.

How well things transfer from one version to the next, well, that is an easy one to take PTC to task with.  If you have the old version and the new version loaded, run the same analysis on both.  If the results don't agree, PTC owes you a thorough explanation.  That is why we pay maintenance!  And if such discrepancies do exist, I would hope this would be broadcast here in the board to raise awareness to others.  Analysis of any kind must be accurate with known parameters!