F
Re: ISO 9001 certificates for a big government entity - one certificate for each dept
I totally agree with you regarding the segmentation negative affects, actually I am feeling the heat of it right now!! and unfortunately I can not change it, I tried, but with no success. The mentality of government entities here in the Middle East are little bit dificult to deal with,,, and each department head wants to be the pioneer and to achieve the certificate before others,,, and the top management is liking that as they think this will increase the competition!!! and yeah they do not care about money!!
Thanks a lot for the reference to the IWA, it looks very useful and am going to go through it tonight
Thanks, again I was against it but could not help,,, now I need support on how to proceed with the least pain possible
nice comparison, any ideas on how to deal with such case? by the was this government entity is participating in the national quality excellence award!
I agree, thanks
Firasali, welcome to The Cove.
I sincerely hope that the organization you are referring here has a positive outcome but I am ALWAYS weary of "certification segmentation", i.e., a departmental approach to QMS implementation & certification. In my experience, it leads to ineffective and inefficient systems. All of the departments will have to identify what their "product" is and who are their customers. It is very easy to forget the end customer, the one receiving the services from this governmental institution. So, whenever I can, I would STRONGLY ADVISE against it. It might take longer, be more painful, but it would be sustainable in the long run. Departmental approach to certification, in my experience, tends to lead to more money to consultants and certification bodies, more press releases, more award ceremonies, etc....but less substance. A waste of money and effort.
Nevertheless, I would STRONGLY encourage you to familiarize yourself with the (link) document. In my opinion the document abstract alludes to the need to have a holistic approach to a system implementation. It reads:
Good luck to you.
I sincerely hope that the organization you are referring here has a positive outcome but I am ALWAYS weary of "certification segmentation", i.e., a departmental approach to QMS implementation & certification. In my experience, it leads to ineffective and inefficient systems. All of the departments will have to identify what their "product" is and who are their customers. It is very easy to forget the end customer, the one receiving the services from this governmental institution. So, whenever I can, I would STRONGLY ADVISE against it. It might take longer, be more painful, but it would be sustainable in the long run. Departmental approach to certification, in my experience, tends to lead to more money to consultants and certification bodies, more press releases, more award ceremonies, etc....but less substance. A waste of money and effort.
Nevertheless, I would STRONGLY encourage you to familiarize yourself with the (link) document. In my opinion the document abstract alludes to the need to have a holistic approach to a system implementation. It reads:
Good luck to you.
Thanks a lot for the reference to the IWA, it looks very useful and am going to go through it tonight
As soon as you start asking about a single Quality Policy, Quality Manual, Management Review, etc then it sounds like you are talking about a single system. What is the advantage to multiple systems? It will cost more, take longer, and will likely lead to suboptimal results with each department trying to optimize their results at the possible expense of the others.
Why can't they share a 'common' policy?
Have common where it makes sense, have different where it makes sense.
I do second Sidney's view, and to me, it doesn't make sense adopting this 'department by department' viewpoint. BUT it is also possible that we simply don't have the info or the knowledge that the people at the top do who made the 'go individual' decision.
'Department' in a government sounds similar but can mean quite a different thing to its meaning in a corporate environment. Here at least, a government department - at least at the State and Federal level - is perhaps best compared to an entire company which is just one of a number of companies owned and run by a holding group.
Have common where it makes sense, have different where it makes sense.
I do second Sidney's view, and to me, it doesn't make sense adopting this 'department by department' viewpoint. BUT it is also possible that we simply don't have the info or the knowledge that the people at the top do who made the 'go individual' decision.
'Department' in a government sounds similar but can mean quite a different thing to its meaning in a corporate environment. Here at least, a government department - at least at the State and Federal level - is perhaps best compared to an entire company which is just one of a number of companies owned and run by a holding group.
Yes, I too second what Sidney suggested above but as the OP reports, decision reg. deptt. by deptt. certification has already been taken. The idea of not sharing a common policy was based on the assumption that each 'deptt.' will be treated is a separate entity having no connection whatsoever with one another but in reality it may not be correct. Unlike standalone entities, they must be sharing a lot in common, so why not to share a policy or a document in common.