|
This thread is carried over and continued in the Current Elsmar Cove Forums
|
The New Elsmar Cove Forums
|
The New Elsmar Cove Forums
![]() ISO 9000:1994
![]() 4.1 Management Responsibility
|
| next newest topic | next oldest topic |
| Author | Topic: 4.1 Management Responsibility |
|
Marc Smith Cheech Wizard Posts: 4119 |
I liked some of Charlies responses here. He clarifies a few issues quite well IMHO. -----snippo----- Subject: Re: Q: Mgmt. Responsibility & Design Control/Pfrang/Scalies From: Charley Scalies > From: [email protected] (Doug Pfrang) Those companies for whom I have consulted have done two things.1. The design process owner will review his/her own system annually to ensure it continues to remain suitable and effective. He/she verifies that the review was conducted and summarizes any changes or improvements that were or will be made. 2. The internal audit function independently verifies and reports on the effectiveness and suitabilty of the design control system based upon the applicable procedures and the desired outcome of those procedures. They, too, report on any improvement opportunities. Both these "reports" make their way to the Management Rep who in turn provides the data or summaries therof to executive management for management review. > If, as you mention, no other company interprets the That's not what I meant. 4.1 does apply to the entire standard. However the management review portion does not directed that it be done paragraph by paragraph. The "common" (my customers) practice is for executive management to review performance of the system against the quality objectives and policy. In other words, if the system is achieving the objectives and leads to realization of the quality policy, it's good. If not, it needs corrective action. Those who are interested in doing more than meeting objectives will look more deeply. > To your second paragraph, I did not mean to suggest we were not auditing Based upon the reviews and audits of others (process owner and auditors) the executive management person or group will look at individual elements on an exception basis only. Remember, meeting ISO9000 is not the purpose of the quality system. The purpose is to achieve the policy and objectives. The ISO9000 system is one vehicle by which that can be done. > To your third paragraph, our design process seeks, of course, various Executive management can delve into as much detail as it wishes. If you think it's important that they examine the particular activities of improvement efforts, that's what they should do. If you think they should receive only summary reports of improvement activities, then that's what they should do. ISO9000 only requires that the results of Preventive Actions be reported and considered at management reviews. Of course, executive management should be as interested in improving the end performance of the quality system (results) as they are in improving cash flow, profits, ROI, share value, etc since one tends to impact the other. One of my accounts has, as a key element of its quality policy, "maintaining our competitive edge". Their management group has to identify how they measure this and then review to determine if it is being met. In their case, review of improvement activities, in some detail, is a must. Hope this gives you some help. IP: Logged |
|
Don Winton Forum Contributor Posts: 498 |
Marc, Agreed. I particularly like the distinctions he draws between the varying sections and their applicability. Regards, IP: Logged |
|
Dawn Forum Contributor Posts: 245 |
I have established monthly Mgmt. Review meetings until we become QS certified. From there, it will go to quarterly. Scrap costs, machine downtime, etc. are included in my repoort for the meeting. Also included are pitfalls, needed resources, and internal audits achieved since the last meeting. You can also review corrective and preventive action. You cna also swithch these items at different meetings so they don't become boring? IP: Logged |
|
Marc Smith Cheech Wizard Posts: 4119 |
I would look at it as an issue of priorities, not simply 'switching' to keep people from being bored... In your meeting you should (prior to adjournment) determine the base agenda for the next meeting based upon what comes up/came up during the meeting. The agenda can be added to or in other ways 'reprioritized, if neccessary, prior to the next meeting. IP: Logged |
|
Marc Smith Cheech Wizard Posts: 4119 |
Maybe I was a bit abrupt with this. In the pdf files directory there is a simple template for a small (I have used a derivitive for larger companies) a management review (ISO9001). It includes all the basics they want - have you taken a look at it? I guess what I'm saying is there should be a 'master' schedule which is what you are referring to by 'switching' parts of. With consideration of the basic minimums scheduled for that specific meeting, then: quote:in addition to basics scheduled for the next meeting. Have I confused you yet? 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!
