Hi Jim,
Thanks for taking the time to review it and respond. I respect your demonstrated knowledge and experience relating to ISO.
I'd be pleased to address your questions.
1) Your perceptions are reasonable, considering you're not hearing the narrative that goes along with the Model. I'd be pleased to provide it to anyone who wants to call and hear it.
Anticipating erroneous or compromised "perceptions" of the Model, I put in a brief explanation of the "INPUT" and "OUTPUT" arrows before the Model, to enhance people's understanding, but, I'll repeat it hear. The arrows represent
directional flow of inputs and outputs...
So, for example:
1) The System-oriented processes (the outer track, if you will), are audited and/or monitored and measured, and data analyzed (i.e. process OUTPUT).
2) The results are INPUT into Management Review.
3) Management Review then OUTPUTS CA/PA or Continual improvement into the involved Processes.
Similarly,
For the customer-oriented processes (Product Realization, Change Control and Control of N.C. Product & Materials)
1) The processes are implemented.
2) The results of implementation (output) are monitored, measured and analyzed.
3) That OUTPUT is INPUT into Management Review.
4) Management Reviews the findings and determines appropriate CA/PA or CI and outputs it back into the process from which it originated. ...so yes, Corrective Action feeds INPUT into Change Control, if appropriate
The Model clearly demonstrates how the Management Processes interface with all the other system processes.
It's all very simple...it clearly demonstrates the PDCA cycle for all processes. While it may not appear simple at the outset, it is in fact quite focused, comprehensive and refined...
and the ISO model remains ambiguous, incomplete and inaccurate, which are reasons enough for removing it, if not replacing it.
And not to belabor a previous discussion, but almost all the Sequence and Interface Models I've seen here on the Cove fail to do this. They all focus on Product Realization, and that's not what 4.1.a and b are asking for.
2) Why not use text instead of a diagram?
Good question...I don't have a problem with narratives, but we all know what is wrong with narratives...no one reads them, and if they do, they don't all necessarily come away with a universal understanding. This pictures is worth more than a thousand words.
I think this Model takes out all the guess-work, and the wasted repetitious attempts to "say the same thing, differently".
...and it can be applied to any ISO organization, with a simple refinement of aspects like:
1) Phases of Product Realization
2) Structure of System Documentation
3) Hierarchy of Management Review.
4) System requirements (ISO/ISO-TS/ISO 14000, Customer-specifics, etc.)
Other than that...every ISO system should operate according to the dynamics of the Model....and audits should be able to confirm that. Believe me, Managers who are introduced to and utilize this Model have a much better comprehension of the Standard and it mechanics, and are proud "owners" of their system...and are able to articulate its mechanics.
I've added another attachement that also captures the essence of the ISO standard (but is not totally comprehensive in demonstrating all the sequences and interfaces)...and might be used for audiences that are intimidated by the Model. It, too, focuses on the Management System, and not Product Realization.
Thanks again for the feedback Jim.
Patricia Ravanello