|
This thread is carried over and continued in the Current Elsmar Cove Forums 
|
|
|
This thread is carried over and continued in the Current Elsmar Cove Forums
|
The New Elsmar Cove Forums
|
 The New Elsmar Cove Forums
 ISO 9001/4:2000
 7.1 Planning of Realisation Processes
|
 UBBFriend: Email This Page to Someone! |
next newest topic | next oldest topic |
| Author | Topic: 7.1 Planning of Realisation Processes |
|
Andy Bassett Forum Contributor Posts: 274 |
posted 21 September 2000 03:37 AM
   
In planning the processes for realization of the product the organization shall determine the following as appropiate; A) quality objectives for the product, project or contract.' ____________________________________________ Would i be right in thinking that in a prototype/project environment, as opposed to mass production, it is very difficult to set quality objectives?. Regards ------------------ IP: Logged |
|
AJPaton Forum Contributor Posts: 73 |
posted 21 September 2000 08:06 AM
Andy, I wouldn't think so, of course, our prototypes end up getting shipped to our customer anyway. But our engineering staff wants the material built to their drawings/designs. One quality objective. Our customers want the designs created to meet their specifications. Another quality objective. And not only that, but everything is supposed to be at the correct rev level. I know that corrections go out to the floor, from the customer, etc. So you still have quality objectives. The specifics just change from project/design to project/design. Just my experience. AJP IP: Logged |
|
Andy Bassett Forum Contributor Posts: 274 |
posted 22 September 2000 02:49 AM
Thanks for the reply AJPaton. I sort of took building a product to the specification required and using the materials defined as a standard requirement, not really a quality objective. Do you have any other thoughts what could be a quality objective in this environment? Regards ------------------ IP: Logged |
|
Al the Elf Forum Contributor Posts: 18 |
posted 22 September 2000 06:13 AM
Andy A possible example : Your contract/specification may require delivery in 12 weeks, however your objective is to deliver it in 10 weeks, as this will generate a higher satisfaction for your customer. In our case we are actively trying to get our customers to tell us relatively what is more important - speed/cost/flexibility/responsiveness. We find this very difficult to embody in a contract, as defined customer requirements, as by there nature they are difficult to make tangible in the way that the dimensional specifications of a prototype would be. However getting the right balance of the above, can be clearly indicated as a Quality objective and if we get a clear steer from our customers, the measurement of performance on this objective should be inexorably linked to customer satisfaction. Our other quality objectives stem from management policy - e.g. policy is to be more profitable, objective for prototype is to deliver it with 25% less labour. Hope these thoughts help.... Cheers, Al. IP: Logged |
|
Alan Cotterell Forum Contributor Posts: 120 |
posted 23 September 2000 05:19 PM
It's been my experience that a large number of problems seem to come from an inability to identify a prototype. In one factory in which I worked, we made twelve trailers as a prototype batch, every one was different. In another company it was declared 'we are not in the business of making prototypes', yet every item was 'custom built'. I suggest we should 'make our mistakes' on prototypes, not on 'production' items. IP: Logged |
All times are Eastern Standard Time (USA) | next newest topic | next oldest topic |
  |
Hop to: |
Your Input Into These Forums Is Appreciated! Thanks!
Main Site Search 
