|
|
 |

13th November 2000, 04:18 PM
|
 |
Courtesy Access
Registration Date: Aug 1999
Location: Rochester, NY US
|
|
Posts: 759
Thanks Given to Others: 3
Thanked 17 Times in 15 Posts
Karma Power: 70
|
|
Anyone have a good example of a T/E company control plan?
Anyone have a good example of a T/E company control plan? I'm envisioning one that can get modified slightly, depending on the job, but about 80% of the standard can be covered by it. For example, receiving inspection, in-process inspection (after controls build, before debug), all the way through the 50/20 and MQ runs. This would be for a custom automated machinery manufacturer.
I'm working on one that I think will work out great....just wondered if I'm reinventing a wheel.
Thanks in advance,
Laura
|

1st December 2000, 07:56 AM
|
|
|
As a TE supplier, we do not have a "Control Plan" as shown in the APQP manual, we have a project file which covers all the topics - our project managers have checklists to ensure they cover all the requirements and our customer requirements / standards determine our inspections which are designated on our build prints by a box around the measurement required to be within a certain tolerance with an area for the employee checking the tolerance to list the calibrated tool used, date inspected, his/her initials. The measurement taken is noted next to the box denoting the critical measurement. We have totally done away with the "standard" Control Plan form. We still do FMEAs but control our time with a microsoft project timeline showing scheduled (budgeted) hours vs actual hours, so we can make up for overruns in a previous area. Seems to be working fine and passing audit.
Good luck.
|

1st December 2000, 05:18 PM
|
|
|
|
Laura,
The PCP (I call it the Build Process CP)is something I sit down with the 1) project manager, 2) plant manager, 3) quality guy (me), 4) other ket personnel as necessary. You want everyone there who has a stake in the process (don't forget purchasing).
I facilitate it(otherwise nothing gets done). We walk through the build process and try to jot down all key events, key characteristics, safety requirements, environmental stuff, long lead purchase/fab items (both in-house and outsourced), R&M stuff, reviews as necessary, production status meetings (can be the same as reviews), inspection events, shipping/delivery, etc.
It looks much like the project manager's timeline (Microsoft Project)if you look at the line items only. The difference is that you do the breakdown columns on tolerance/spec, eval tech, control method, and action plan (this is a biggy, the auditor always looks for it).
If you have "product families", just develop a CP for the family and then use it (change the header info), adding to it if anything changed. I have a typical "Build Process CP" that can be used to start off any customized build project. Saves me time.
The trick is to get the right people to sit down with you, limit the interruptions, and to be sure no important events are left out.
Hope this helps.
|

11th December 2005, 06:37 AM
|
 |
Your Elsmar Cove Host
Registration Date: Jan 1996
Location: West Chester, Ohio - USA
Age: 59
|
|
Posts: 15,859
Thanks Given to Others: 1,895
Thanked 1,569 Times in 1,020 Posts
Karma Power: 605
|
|
Any current comments?
__________________
A Search is a terrible thing to waste!
One Test is Worth 1000 Expert Opinions - The plural of anecdote is not data.
We can't solve problems by using the same kind of thinking we used when we created them. - Unknown
|
Lower Navigation Bar
|
|
|
|
Visitors Currently Viewing this Thread: 1 (0 Registered Visitors and 1 Unregistered Guests)
|
|
|
| Thread Tools |
Search this Thread |
|
|
|
| Display Modes |
Rate Thread Content |
Linear Mode
|
|
Posting Settings
|
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
HTML code is Off
|
|
|
|
|