|
This thread is carried over and continued in the Current Elsmar Cove Forums
|
The New Elsmar Cove Forums
|
The New Elsmar Cove Forums
![]() ISO 9001/4:2000
![]() Documentation Element 6.6
|
| next newest topic | next oldest topic |
| Author | Topic: Documentation Element 6.6 |
|
Andy Bassett Forum Contributor Posts: 274 |
I was asked to give a plain English summary of the ISO 9000:2000 documentation guidelines. So here it is, i would be very happy if anybody has time to read it and make any comments before i ship it. Regards Andy What are the basic requirements of ISO 9000:2000 in terms of document control? First of all what can be defined as a Document and what can be defined as a Record? My own definition of a document is something (in paper or electronic format) that has the possibility to influence the quality of the product. The obvious item is of course a drawing, or maybe a Job Card, but in fact it could include many other items such as the Customers Orders, any changes to the customers orders, Delivery Notes etc. Also included in this area are documents related to the Quality Management System ie Procedures and Work Instructions etc. This may seem like hard-work to some companies whose QMS describes just the outline of the processes, and any possible influence on the product quality is hard to see, but it cannot be escaped. My own definition of a record is something (in paper or electronic format) that shows the result of a product inspection. The obvious item is an Inspection Report, but there are many other possibilities, including Test Reports, Analysis Reports etc, It was once explained to me that essentially a blank cheque could be classed as a Document, whilst a filled-out cheque would be a Record. Section 5.6.6a asks that documents are 'approved for adequacy prior to release' 5.6.6b asks that 'documents are reviewed, updated as necessary and re-approved'. Quite what they want here is not clear, if they are simply asking that when documents are updated, this should somehow be seen on the document, and that any changed documents go through the same checking procedure, then this is no big problem.
5.6.6d You have to ensure that 'obsolete documents are removed from all points of issue, or otherwise controlled to prevent unintended use'. Again no problem if you are using a computer system, simply put the new documents into the relevant folder, and put the old ones into the 'old/unused' folder. If you are using hardcopies somebody will probably have to physically remove the old copies and insert the new ones, again this can be a discipline problem. 5.6.6e It is requested that 'any obsolete documents retained for legal or knowledge-preservation purposes are suitably identified'. If you are using a computer system simply ensure that obsolete documents are moved into a folder marked 'obsolete documents'. If you are using hardcopies you will need to ensure that the obsolete documents are marked in some way and filed in a 'Obsolete Folder'. And here is the clincher; A master list or an equivalent document control procedure, identifying the current revision status of documents, shall be established and be readily available to preclude the use of invalid or obsolete documents. The problem with a Document Matrix is that it is never read by company personnel, and only ever updated the day before the audit. Lastly it is requested 'that documents shall be legible, readily identifiable and retrievable. Applicable documents of external origin shall be identified and recorded'. ANY COMMENTS? IP: Logged |
|
kheldar Lurker (<10 Posts) Posts: 2 |
Only a sugg. regarding the doc. matrix. We can easily do this using Excel or Access and using links to made an automatic update of the revision. (no need to make it the night before audit - hehe). And I think this is one of the most comprehensive explanation regarding this particular point. ------------------ IP: Logged |
|
isodog Forum Contributor Posts: 51 |
Documents preceed production. records are after. IP: Logged |
|
Phil Saunders Lurker (<10 Posts) Posts: 1 |
Document: information and its support medium. Record: a document stating results achieved or providing evidence of activities performed. [This message has been edited by Phil Saunders (edited 01 July 2000).] IP: Logged |
|
isodog Forum Contributor Posts: 51 |
Good summary. One suggestion on the cheque example. The cancelled check is the record (it is proof that the operation took place). To carry it one step further, the statement is a report not a record (only one record of each transaction) and doesn't have to be controlled. ------------------ IP: Logged |
All times are Eastern Standard Time (USA) | next newest topic | next oldest topic |
![]() |
Hop to: |
Your Input Into These Forums Is Appreciated! Thanks!
