View Full Version : Contract Review Procedures
overloaded intern 5th June 2006, 04:06 PM I just finished my FIRST year in undergrad for aerospace engineering and am working at an internship for the summer. My boss decided AS9100b certification would be a good task for me to work on. My company started the ISO certification process a few years ago but never completed it. They did outline/reference several documents to cover the AS9100b requirements however these documents were either lost or never actually written. Going from that list, I'm supposed to write a document titled "Contract Review Procedures". Looking through the standard I'm thinking this includes everything in 7.2 but I'm not sure what else. In other words, I dont know what Im supposed to write about. Do you have any ideas as to what requirements I could compile under this title? Thanks
michelle8075 5th June 2006, 04:18 PM I am not familiar with the AS91000 standard. I am however very familiar with QS-9000 TE and ISO-9001:2000. You can probably look up some previous threads on this site under QS and ISO and see what kind of ideas you can get.
The section 7.2 in AS-91000 may call out some related elements. If it doesn't think of Contract review starting the moment your company thinks it might start get a job. Usually, a company gets a request for quote in which your estimator/quoting department reviews customer requirements, customer specifications, plant layout (do you have the area to produce the product the customer wants), manpower - resource management, feasibility of making the product, cost, etc.
So read through the standard and start to see the coorelation between the other elements and "shalls" in section 7.2. I'm sure that many other elements will influence how you write your contract review procedure.
BadgerMan 5th June 2006, 04:20 PM “Contract” review is only one part of the process described in section 7.2, IMO.
I would start by studying the process, beginning with receipt of the RFP/RFQ all the way through flow down and implementation of the resulting contract requirements. Then sketch a flow chart to help you develop an outline for your procedure.
RosieA 5th June 2006, 04:22 PM Yikes, sounds like a pretty intense project for a first year intern. :eek: Good luck!
morgand 5th June 2006, 04:27 PM Find out how you really do things first. Then map them back against you standard. Fill in the gaps that appear and everything should be :)
overloaded intern 5th June 2006, 06:15 PM Thanks everybody. I'll see what I can learn. Then I'll be back with more questions. :rolleyes:
Sidney Vianna 5th June 2006, 06:45 PM I would start by studying the process, beginning with receipt of the RFP/RFQ all the way through flow down and implementation of the resulting contract requirements. Then sketch a flow chart to help you develop an outline for your procedure.
Find out how you really do things first. Then map them back against you standard. Fill in the gaps that appear and everything should be :)
Yes, one can do that. However, if the existing process is ineffective, "broken" and/or dysfunctional, then you just perpetuate an AS9100 compliant (but ineffective, broken or dysfunctional) process.
Not easy for an intern to solve this, but to document what you do might just perpetuate intrinsic problems. Intern, if you can, interview the people associated with the process, and enquire them why things get done the way they do. Further, ask the process-involved people if and how the process could be improved. At the end of the day, you want to have a lean, streamlined process which addresses all regulatory, customer and self driven mandates.
overloaded intern 5th June 2006, 07:32 PM So I read through a contract and broke it down into about 7 different areas (funding, info rights, subcontracting, etc.). I'm compiling a list of each area and who is responsible for each. I guess I'm then going to get info from each person on what each area involves and then compile it into my "Contract Review Procedures" document. Any other suggestions?
Al Rosen 5th June 2006, 10:42 PM So I read through a contract and broke it down into about 7 different areas (funding, info rights, subcontracting, etc.). I'm compiling a list of each area and who is responsible for each. I guess I'm then going to get info from each person on what each area involves and then compile it into my "Contract Review Procedures" document. Any other suggestions?Yes, post it here for us to review! We might be able to help.
Wes Bucey 5th June 2006, 11:05 PM Some important things I like to consider include:
capability and capacity
(can we really do this? do we have the capacity to fulfill the contract without overextending ourselves or shorting any other customers?)
Acceptance criteria
(do customer and we have instrumentation and expertise to confirm product meets specs? Do we agree on how to do inspection?)
Mechanism in event customer rejects a shipment
(How do we confirm a nonconformance? Do we have an arbitration or 3rd party expert we agree about now - before the need arises?)
Pricing
(What happens if OUR suppliers raise prices?)
Customer penalty if he does not schedule full order within reasonable time
(Many prices have quantity breaks - what happens if customer takes million piece price, but only schedules 10 thousand pieces?)
Our penalty if we do not meet schedule with acceptable product, apart from force majeur?
Raptorwild 9th June 2006, 06:09 PM Maybe I am missing something, overloaded intern was asked to write a procedure for Contract Review. I think you are on the right track by digging into how this process is actually being done now and write it down. Later...you can tweek it until it is effective. JMO :)
|
|