Commandments of ProE- 2nd attempt

In Reply to Dean Long:

I personally like the new method of handling failures for a number of reasons.

1. No more Click, click, click, click, click. Feature 1 done. Click, click, click, click, click. Feature2 done.Click, click, click, click, click. Feature3 done.Click, click, click, click, click. Feature4 done...etc...........................................................

2. I can now see how much pain I have to look forward to. If I see 3 or 4 red features in the tree, I attack! If I see 50, well I take a rest room break, get a fresh coffee, sharpen my sword and then attack.

3. Moving back and forth between my before failure model and my current model evaluating featuresis much faster.

🐵

Second that!

Chris,

I find it very useful to "Save As" before I make any changes to my parts. Next time save your part, XXXXXX_B4. This way you can avoid the whole "failed model in session" deal and just have a second part open. Flip back and forth between windows and see the failed features as they were before the failures. Another great benefit of this method is the ID's, feature numbers and refsare the same from part to part. Now if you delete and/or add features it's easy to see the differences.

Assemblies get a bit more tricky and laboriousbut the same philosophy holds true.

Dean

In Reply to Christopher Gosnell:

Your last statement brought up the most painful thing about repairing
failures.



When significant failures happen in my models I end up opening a
'pre-failed' version of the model alongside the failed version, prevent
it from regenerating, and then walk through the features to resolve the
failure. This is no fun really unless you have two licenses of Pro-E
running, and then hope you have dual monitors.



I'm working in WF5 M090 or (Creo-Elements-Pro) and the ability to see
what the feature looked like before it failed (ala Solidworks) would be
a tremendous help in resolving failures. But at least I can suppress
and move on quickly.



And as long as the system warns me that I have unresolved failed
features, and/or suppressed features, I have no problems saving those
files. Now, I would hope that there is a trigger in Windchill,
Interlink, or whatever not to let me promote that model to available,
shared, or ready for use status without resolving the issues. I don't
use these systems, but Modelcheck will let you know that features are
suppressed, or failed, etc...



Usually with failures, I am trying to do drastic things to a model, or
assembly. Maybe I'm adapting it to a new situation, etc... Having to
stop to resolve regen issues immediately, really screws up my thought
processes.





Christopher F. Gosnell



FPD Company

124 Hidden Valley Road

McMurray, PA 15317

I use a similar method as Dean.

I normally don't do a save-as when making some major changes to a model, but if I get to a point were it's hard to understand the original features references. I simply open the model with the versions filters on and open the version before the current model. Pro/E will tell you that a model with that name exist, would you like to rename. I this point I name the model Verify.

Pro/E opens the "Verify" version of the model and now I can see how the original features were made in comparison. The great thing about this method is that when I am done, I don't ever save the "Verify" model that is in session, so I never create extra files.

"Too many people walk around like Clark Kent, because they don't realize they can Fly like Superman"

It seems that the explanation I gave on my method is confusing some people. I created a Youtube video to demonstate what I am doing. I don't know if this would work when using Intralink or Windchill. I am in the process of implementing Windchill 10, so I will need to see how this would change if at all.

http://goo.gl/Kvbtk

"Too many people walk around like Clark Kent, because they don't realize they can Fly like Superman"