V
vanputten
Re: ISO 9001:2008 Required Procedures
TXSUN:
What is a PRM? Be careful with using acronyms.
TXSUN:
What is a PRM? Be careful with using acronyms.
It would be a nightmare to control if procedures are not written. Then everybody will do it their own way, at the end of the day everybody will have different outputs. How can you cantrol that if you have not written anything. How can you justify who is doing wrong or right?Why do you think that it's necessary for a procedure for a process? Why, for example, can't a process be defined verbally? Or maybe a form used to check off and record the various steps through the process?
Just interested in the discussion as to why...
We created a flowchart specifying input, process, output.To list the processes will meet the requirements of 4.2.2.c. this is how I interpret the standard. The procedures will just make it easier to understand the process.
It would be a nightmare to control if procedures are not written. Then everybody will do it their own way, at the end of the day everybody will have different outputs. How can you control that if you have not written anything. How can you justify who is doing wrong or right?
That was one of my original questions. : )
I could not find it on the cove, so I had to turn to Google. This is what I found:
PRM: The process reference model is a logical representation of the elements of the processes that can be performed at a basic level. Using the reference model in a practical application might require additional elements suited to the environment and circumstances.
If anyone has additional information on this acronym, as it relates to ISO9001:2008, I would GREATLY appreciate it! (Especially if I am wrong!)
IMHO, processes have to be documented in such a way that we can see and figure out where we can improve. It does not have to be because ISO require or don't require. We have to document good business practices.Your points are apropos to determine if documents might be needed, but not justification in and of themselves.
I don't quite understand why you said my points are apropos.
People need to know outcomes not procedures. A Process map is sufficient for explaining the process. Most new hires get trained through on-the-job training (OJT) and are then let loose. Focus people on process outcomes, defects, and nonconformances and you will have a system to evaluate their training (6.2.2). Procedures are not required for every process but outcomes are...IMHO, processes have to be documented in such a way that we can see and figure out where we can improve. It does not have to be because ISO require or don't require. We have to document good business practices.
Also, it helps when new hires come onboard, they can refer to the written procedure. I don't quite understand why you said my points are apropos. Anyway, those are just my humble opinion, that is how I forsee it. Things will become messy and chaotic if procedures are not written. There is no way you can validate if people are doing it right or wrong.