We're finally moving from Creo Elements Pro WF5 to Creo 3 (with WC 10.1)...Taking a close look at all processes and configurations.
Since first starting to use Windchill, we've always had a process that seems to be required but is a terrific nuisance. Wondering if it's different (haven't tested yet) in Creo 3 and wondering if there is a smarter way in general to handle.
SITUATION
- Family Table with different Revisions allowed for each instance (not all companies allow this but many do)
- In general, Generic and all Instances Released; approved change must be made
- User assigned to make the change
- Revises the Instance(s) that are changing and so can Modify them at In Work
- Does not Revise the generic
- Cannot Verify the family table with modified instance(s) without Modify permission on the generic
CURRENT PROCESS
- A user with needed permission temporarily Sets State of the generic to In Work
- User assigned to make the change does so, including family table verification and check in of the generic and instance(s) being Revised and modified
- User with needed permission Sets State of the generic back to Released
- The instance(s) being changed are released via the Change Notice workflow
PROBLEMS
- Difficult to make sure that the generic always gets set back to Released
- Not good to have a group that can bypass controls and processes by being able to Set State to Released
How do others handle this?
Appreciate any input from PTC - especially if already documented somewhere.
thanks in advance