Posts

Showing posts with the label QMS documented information

Numbering System for ISO documentation based on ISO 9001:2015

Image
As far as I know ISO 9001:2015 do not mandates a specific numbering system for control documents. Is it true that the organization is left open to adopt one that suits it's organizational needs? Also I am interested to know the best practices for the numbering system . Yes, that's right - ISO 9001:2015 does not mandate a specific numbering system for control of documents. Here is an example of the documented information number structure that has been proven in practice: 1. Abbreviation that identifies the document type in accordance with the Documented information structure adopted by the Organization. For example: QSP = Quality System Procedure.  QSF = Quality System Form 2. ISO 9001:2015 clause number the group of documents is relevant to. Example : 7.1 - , a group of documents relevant to resources. 3. Index number of the document in the group. Example : -003 means this is a document #3 in the group. 4. Sometimes it is relevant to give the document...

Procedures vs. Work Instructions

Image
Procedures vs . Work Instructions I was recently working with a process owner to modify one of his procedures. And part of the conversation was that, in my opinion, his procedure looked more like a work instruction. He felt that those details were necessary to perform the job and my answer was that those could be written in a work instruction for the specific task. What has been your experience in this situation? Many spears were broken when arguing on this comprehensive issue. Here below we express only an opinion. 1. It is not a good idea to argue about terminology, but worth agreeing upon it . This fully applies to the names of the QMS documented information. Each organization sets its own documented information ‘pyramid’. The requirements of ISO 9001:2015, as well as the 2008 guidelines of ISO 10017 and the recommendations 176 TC reports give full freedom to the organization. Therefore, it is better not to talk about the requirements, but better about good pra...