Alabama A&M University Procedure No.: 4.2 Contract Review and Approval Process Page 2 of 2 of the OGC’s receipt of the resubmitted Agreement. Procedure Contract Review P7.2-2 Rev. Flowcharted procedure and updated review for ISO 9001:2000. Contract Review 7.2.2 Rev. K- Change Orders. What is Contract Review? A process for the determination of customer requirements prior to the supply of a product and the proof that the organization. This text is from the second edition of ISO 9001, The Standard Companion. It is based on the now obsolete 1987 version of the ISO 9001. 4.3 Contract Review. 4.3.2 Review Before submision of a tender, or at the acceptance of a contract or order the tender, contract, order shall be reviewed by the supplier to ensure that: The requirements are adequately define and documented: where no written statement or requirement is available for an order receive by verbal means, the supplier shall ensure that the order requirements are agreed before their acceptance; How will be the best way to implement this clause? Having a writen confirmation from the customer on each order will comply? ![]() Please share some ideas of implementation of this clause with in your company. We are a medium size company; we receive about 100 orders a day (different parts). Arturo Rosales. Arturo, I am not certain there is a 'best way.' The methods must be applicable to your method of operation and best business practices. But, I would not suggest 'written confirmation' for 100 orders per day. Anyway, my $0.02 worth. Section 4. Common be instrumental rar. 3.2 basically applies to how you determine if order requirements are 'adequately defined and documented.' If an order is received in a hard copy, this is a review of the requirements submitted by the customer and a determination if your company can fulfill the requirements of the order. If your facility receives orders by verbal means, then as orders are received, Sales (or whoever) fills out a 'matrix' type of form that completely describes the customer's requirements. This form is submitted to manufacturing for fabrication. This is a relatively simple method of compliance with 4.3.2 and also meets the requirements of 4.3.4. Iso Contract Review FormRegards, Don [This message has been edited by Don Winton (edited 12-01-98).]. Subject: Re: Contract Rev Requirements/Order Confirmation /Eberhardt/Schoffman Date: Thu, 8 Jul 1999 16:06:12 -0600 From: ISO Standards Discussion From: ASchoffm Subject:RE: Contract Rev Requirements/Order Confirmation /Eberhardt/Schoffman >Bill Eberhardt wrote: Many of our customers fax order requests which are incomplete: 'Send me 1000 ' widgets'. We construct the order based on previous order history with success. My questions to the group for opinions are: * Per ISO 900X, do we need to confirm the info with our customers? * Is a 'fax-back'- complete order information faxed back to the customer adequate or do we need to speak directly with the purchasing authority? * If our customers prefer us not to call, isn't this flying in the face of the standard- not giving the customer what he wants/expects?> > RESPONSE Bill, your final question is one that is the key to the answer. Many people in their (well-intentioned) zeal to conform to the ISO 9000 specs forget that customer satisfaction is not only the cornerstone of ISO 9000 but also the fundamental factor in running a business. Fm 2005 complete r. If you have to 'convert' your customer's orders to state what you know they want, you should document that internally. If you can fax back that info to the customer, so much the better. But suppose the customer just doesn't want to be bothered with any confirmation. That does not make it contrary to ISO specs. Your procedures may indicate that your company will confirm the customer's orders. There can always be exceptions. These can be documented explicitly or your requirements can be generalized. But ISO should never and never has to be structured to put your relationship with your customer in jeopardy. Internally, you have to state what your procedures are and follow them. But that's it. Perhaps an analogy would be a customer who comes to the same restaurant for dinner 3-4 times a week, gets the same table and the same waiter and begins with the same libation every time. He orders 'the usual'. If the waiter continuously confirms that he wants 'a dry Beefeater martini with two olives' every time he orders, the customer may get upset and state 'I said the usual. Don't you know what that is by now?' You state ' We construct the order based on previous order history with success.'
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |