B
Hello there,
Yes this is another question concerning the documentation identification for a Quality Management System (ISO 9001-2015)! Here is the situation, I am in the process of implementing a Quality Management System for my company. I am currently working on the rules that will help us to properly manage the documents that will be edited (ie process description, procedures, work instruction, forms etc....). I know there has already been tons of discussion about documentation codifications etc...at the end of the day I am still wondering what is the most simple system to manage properly the documentation without it being a useless and overcomplicated set of documents codifications....Yet I dont want to have documents that are not managed (ie no owners). It seems to me that having just a small ID code somewhere at the bottom of the document will be usefull to know "who, or what process" owns it. For instance let's say that within the Design & Engineering process you use at some point a check list. That check list could have somewhere written "Form-ENG-01" to say that it is the first form of the Engineering process. For me the important point here is that this document is not an "orphan", it is connected to the Design and Engineering process, and the process owner is in charge of reviewing it, and making sure its content is appropriate. Do you think it makes sense? The only issue I think of with this system is that I connect each document with a process while sometimes a document (let's say a work instruction) can be used by several different processes.
Any feedback on how you dealt with this question would be welcome!
Yes this is another question concerning the documentation identification for a Quality Management System (ISO 9001-2015)! Here is the situation, I am in the process of implementing a Quality Management System for my company. I am currently working on the rules that will help us to properly manage the documents that will be edited (ie process description, procedures, work instruction, forms etc....). I know there has already been tons of discussion about documentation codifications etc...at the end of the day I am still wondering what is the most simple system to manage properly the documentation without it being a useless and overcomplicated set of documents codifications....Yet I dont want to have documents that are not managed (ie no owners). It seems to me that having just a small ID code somewhere at the bottom of the document will be usefull to know "who, or what process" owns it. For instance let's say that within the Design & Engineering process you use at some point a check list. That check list could have somewhere written "Form-ENG-01" to say that it is the first form of the Engineering process. For me the important point here is that this document is not an "orphan", it is connected to the Design and Engineering process, and the process owner is in charge of reviewing it, and making sure its content is appropriate. Do you think it makes sense? The only issue I think of with this system is that I connect each document with a process while sometimes a document (let's say a work instruction) can be used by several different processes.
Any feedback on how you dealt with this question would be welcome!
