Managing Assignments wrt Change Management

[HugoHermans]

Hi,

We wonder how companies work with long lists of assignments of problem reports, change requests, notices, tasks?

How do you manage these lists? Set priorities? Get an overview of things done and to be done? Change your mind and switch a problem report from one ECR to another? Or divide an existing ECR into two separate ones? And a lot more little and not so little everyday situations.

We are getting up to speed with the implementation of change management in part of our R&D department, approx. 25 people are involved now. ECR's are sometimes initiated by problem reports, sometimes not. Some ECR's have only one ECN with only one Task, other ECR's are very complex structured. In total, there are over 600 running tasks!

We created a workable environment for all thisby somein housemade reporting and manipulation. Is this common practice? Or are we over demaning? Or maybe we don't understand what PTC was up to?

I appreciate all considerations, Hugo.

<< ProE WF3 M190 - PDMLink 8.00 M040 >>

[MikeLockwood]

Executing a lot of changes is a lot like managing a production line with highly variable orders.

Windchill doesn't seem to lend itself well to managing work - like job shop software does for example. In addition to the open jobs, there is need for understanding how loaded each of the workers is and what kind of skills are needed for each job, etc. We've tried to pull open changes and also work requests (we created a subtype of change request that we can work request) from Excel, then combine and manipulate all that info relative to the available work force, in order to try and optimize work assignment.

We've been trying to develop a variety of query builder reports for this purpose for several months - with varying degrees of usefulness. Happy to share what we have.