cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Showing results for 
Search instead for 
Did you mean: 

Strategies for utilizing OOTB Change Notices

Level 7

Strategies for utilizing OOTB Change Notices

We are in the process of planning and implementing Change Management in our Windchill environment.  The goal is to utilize as much OOTB configuration as possible, and minimize customization to start.

Two area's we are looking for insight on are:

1)  How to handle additional (uncaptured) changes
Lets say a user is assigned a change task (after Implementation plan approval),  While implementing change to resulting objects, the user identifies additional changes (required and/or improvements) that are not captured in existing change objects. 

Some ideas are we are considering:
a) amend the change notice + (Send to CIB for re-approval OR send directly to Audit depending on impact of change)
b) create new PR/CR and incorporate change at next release

2) Content of a change notice and change task

How have you structured change tasks and notices?  We are debating guidelines for the amount of affected objects a change notice/task should contain and also the number of changes
When applicable, we are considering
a) 1  change notice per change detail (i.e change a screw for all affected objects VS change a screw for several parts + change the length of an extruded part)
b) 1 change task per part number VS 1 change task for all affected PNs

Just looking to see if there are any strategies that folks have found beneficial or detrimental.

Looking forward to discussing.