I will respectfully disagree with you that blaming the tool is naive for the examples I provided.
The change I am trying to make on a model is not visible on any drawing, it's not related to the products form, fit or function.
If I am adding a new coordinate system for the purpose of aiding a Validation Software such as Geomagic Quality in creating a report requested by QA, I should be able to open the model and add that coordinate system. The coordinate system has nothing to do with the product and it's not tied to any downstream or upstream components.
"Can Windchill change any object in the database, if you want it too -- but do you really want it too?" For the examples I am refering too, the answer is yes. They have no baring on the product, the documentation, the drawing, etc.
Others have provided some great ideas on how to manage these situations and I will investigate which method works best for us.
Thanks
In Reply to Patrick Perry:
In most situations released data should not be changed -- there is legal ramification for this (think OSHA certification). To blame the tool is being a bit naive. The problem is users are depending on the tool and NOT checking things as well as they should (or are being pressed to get things done more quickly than humanly possible). If a datum is visible on a drawing and that drawing was pushed to release, it is not the fault of the tool. If the corporation's process is objects should not be modified when they reach a released state, that is not the fault of the tool.
When I first started in PDM the vendor told me a two very wise statements. What is the best thing about a PDM tool, it can do whatever you want it to do. What is the worst thing about a PDM tool, it can do whatever you want it to do.
Windchill is very flexible, best practices through going to several companies has put limits on some freedoms. Can Windchill change any object in the database, if you want it you -- but do you really want it to? Can Windchill be designed to allow a group of users (other than Administrators) to change released objects -- it certainly can. My question would be in I am making several changes at released I maybe need to look at my process because certain steps are being missed. For the gentleman that need a coordinate system for verification, why not make that part of the process so that every model has that -- it no verification is required no harm. If verification requirement comes after release, then no change is required.
This discussion should not be about Windchill, Windchill is just a tool. This discussion should be about the process of getting objects to be production ready and what is the best way to insure those objects are ready for anything.
"Too many people walk around like Clark Kent, because they don't realize they can Fly like Superman"
