Oxebridge Quality Resources’ founder and the author of Eyesore , Christopher Paris, presents a fantastic, one-of-a-kind insight into how the latest version. A satirist, he is the author of Eyesore , the world’s only parody of ISO , which has been downloaded nearly a quarter of a million times. to align with some process framework model, like the CapabilityMaturityModel ( CMM) or ISO (which I affectionately call “Eyesore ” 😉 or SPICE, etc.

Author: Tygogor Bale
Country: South Sudan
Language: English (Spanish)
Genre: Literature
Published (Last): 27 November 2009
Pages: 392
PDF File Size: 20.22 Mb
ePub File Size: 19.77 Mb
ISBN: 873-2-26959-563-4
Downloads: 23167
Price: Free* [*Free Regsitration Required]
Uploader: Nikora

Company Info Who are we?

Rotting eyesore bungalow one of 9, empty Birmingham properties – Birmingham Live

The next revision of ISO is due inand the standard is being anticipated with more controversy than any previous edition. The document, now in its Draft International Standard DIS stage, is nearly a eeysore deal, with very few changes likely before it progresses to its final release.

Despite some online bluster, the changes are not as significant as some would have you believe. TC was thus required to adopt the structure and language of Annex SL without being able to alter it. Combined with pressure by ISO to publish byand a remarkably light schedule of physical meetings, there was simply was no time for TC to move ISO to consider any newer best practices or modern advances in quality management.


Contrary to TC spin, the inclusion of risk did not come from user demand.

Rotting eyesore bungalow one of 9,000 empty Birmingham properties

Lacking risk management professionals in its ranks, TC was stuck interpreting a complex field of study on an impossibly compressed schedule. It even specifically says it is not risk management. One of the members of ISO’s own TC on risk management said that eyesorw thinking is equivalent to “selling bottles of sound. The other significant changes are: The good news is that because the new standard is filled with vague, half-baked ideas subject to interpretation, you get to eyeaore it.

Rather than write an inane Quality Manual, companies should create a policy document which defines its interpretation of each of the requirements, clause by clause. These can be single-sentence policies that would then point to any supporting procedures. It sounds like the traditional Quality Manual, but would look entirely different.

This document would then be useful for training and — most of all — providing to third party assessors. Then, objectives for each process can be developed at least one per processwhich support those policy statements and provide a means of assessing if each process is effective. This might be a good time to get rid of dopey process maps and those horrid Turtles. Next, companies should defend their interpretation when challenged, specifically by certification body auditors.


In the past companies have sought interpretation guidance from the CBs, which is backwards; they are there to assess your interpretation, not assess their eyesre. Finally, companies will have to be ready to eyeskre their rights to appeal, complain and escalate complaints when the inevitable clash happens with CBs. The CB industry is loath to pay for any training of their auditors, and they are unlikely to start now, especially regarding the complex discipline of risk management.

Companies will have to go back and point to their interpretation document, and defend it when challenged.

More than ever, this means companies will need to read ISO and ISOthe rules for auditors, and be ready to use those rules to defend themselves. But all of this will come despite ISOnot because of it, and relies on taking advantage of the deeply flawed, vague language that TC has released on the world.

Silver lining, and all that. What is your company doing to prepare for ISO What are your concerns?

Please comment below or on LinkedIn: Download Free Resources White Paper: Browse by Topic Topic. Food and Drug Administration 19 Validation