Core Team - Who gets listed as part of the "Core Team" in a control plan

[qakid]

Who is listed as part of the "Core Team" in a control plan? I am developing a control plan for an existing manufacturing process where no procedures exist. I am new to the organization so I am interviewing people from all departments. Would I list all people involved with providing me information, or just one person responsible for each department? I worked a lot with the Operators actually doing the work--would I list them? Some people are funny about having their name on documents.

[Duke Okes]

Core team for most manufacturing companies would typically be quality engineer, process engineer, production/operations personnel and in some cases design and purchasing personnel.

[Jim Wynne]

In Reply to Parent Post by qakid

Who is listed as part of the "Core Team" in a control plan? I am developing a control plan for an existing manufacturing process where no procedures exist. I am new to the organization so I am interviewing people from all departments. Would I list all people involved with providing me information, or just one person responsible for each department? I worked a lot with the Operators actually doing the work--would I list them? Some people are funny about having their name on documents.

There are two schools of thought on how to go about this. One way is to do what you're doing and talk to people one-on-one, which has the advantage of making it more likely that people who might be reticent in a group setting will speak up. The disadvantages lie in what you're experiencing now--identifying the team and in having to assimilate all of the disparate information into something that makes sense.

On the other hand, the way it's usually done is in meetings, with the relevant team members identified beforehand. The advantage of meetings is that there's a better opportunity to weed out ideas that probably won't work and there's group responsibility for the output. I like the team approach myself.

[trainerbob]

I agree with Jim. Any part of the organization that has a stake in the product/project need to be involved in the meetings to write the necessary documentation. Not necessarily everybody from every area - but at least representation from each area who are familiar with the functions and needs from their veiwpoint.

[SteelMaiden]

I think it is important to realize that being on the core team does not necessarily mean that you know everything about everything. It is ok for someone on the core team to perform some research and that research could mean interviewing an operator. That doesn't mean the operator is now a part of the core team, only that his expertise was used by the core team.