|
This thread is carried over and continued in the Current Elsmar Cove Forums
|
The New Elsmar Cove Forums
|
The New Elsmar Cove Forums
![]() Documentation
![]() Document Matrix's. Can the Server be used?
|
| next newest topic | next oldest topic |
| Author | Topic: Document Matrix's. Can the Server be used? |
|
Andy Bassett Forum Contributor Posts: 274 |
Looking at a subject on another thread jogged my memory about a problem i have had in the back of my mind for some time. I have never yet seen a company that gets any benefit out of a Document Matrix (I know the theorey behind it, but thats the reality). If i am using a EDP System, can i not simply say that the latest documentation can always be found on the server, and if necessary do a screen shot of the server as evidence for the auditor.? The only documentation that may then need to be in a matrix is externally supplied documents. Delivery Notes etc ------------------ IP: Logged |
|
Spaceman Spiff Forum Contributor Posts: 64 |
That is exactly how I re-constructed the document system at my company. Thus far, the assessor did not have any problems with this method. I do need to state that the IT Administrator and I are the only two with Read & Write access to the Documentation System drive. IP: Logged |
|
Sam Forum Contributor Posts: 244 |
I implemented the same process using ISO-x-Pert at a previous company. Worked great, auditors had no problem with it. IP: Logged |
|
Brenda Mundroff Forum Contributor Posts: 18 |
So, why do we need a document matrix? The only benefit I see is for the auditor or the MR to be able to identify who owns what and where it is located. Outside of that, the technicians know where there doc is located. Other benefits I might be missing? IP: Logged |
|
Marc Smith Cheech Wizard Posts: 4119 |
quote:Yup - you sure can say the 'latest' documentation is on the server. And your document 'matrix' can be a directory listing. On the other hand, many companies use a matirx to define retention times and such. In fact, many companies have multiple document matrices. IP: Logged |
|
Sam Forum Contributor Posts: 244 |
Did we confuse "Document Matrix" with "Master List" A master list being a list of documents,document numbers, location and rev. level. A document matrix being a matrix of functions down one side and types of documents across the top with the responsibility for approval and release as the filler. IP: Logged |
|
Marc Smith Cheech Wizard Posts: 4119 |
There is no requirement for a document matrix (per your definition) that I know of. There is no requirement for a document list (per your definition as well), either. quote: quote:Note that the 2000 version says nothing about a master list. IP: Logged |
|
Sam Forum Contributor Posts: 244 |
Marc, As usual you are absolutly right. Those were my "personal" definitions based on previous "wants/needs" of the auditor. The real requirements were "stretched" a little. In our system we are still required to have the master list as required by QS9000. IP: Logged |
|
Marc Smith Cheech Wizard Posts: 4119 |
quote:Where does QS9000 require a master list? quote: IP: Logged |
|
Sam Forum Contributor Posts: 244 |
Again you are correct, however, Master list or equivalent.... Somehow I don't see the difference, other than to add fuel for comentary between auditor/auditee. IP: Logged |
|
Marc Smith Cheech Wizard Posts: 4119 |
It says: "...equivalent document control procedure...". You can state in your procedure that "...a summary of documents can be obtained by doing a directory listing..." or whatever. All they want is that you can show what documents you have and that they are in control. Yeah - rev level, etc., but technically you can get that from the document. The point is if you design your systems to satisfy what an auditor feels is a satisfactory system you can quickly loose control. Having a master list and matrix is a typical expectation of an auditor. That doesn't mean that is the requirement. If an auditor started telling me I have to have a master list or matrix and I used a different methodology which fulfills the requirement, I'd fight for my system. IP: Logged |
|
barb butrym Forum Contributor Posts: 637 |
marc is absolutely right...no need to go any further...as usual IP: Logged |
|
Bob Lurker (<10 Posts) Posts: 4 |
At our military aircraft and component overhaul facility, we are setting our system to the ISO 9000:2000 requirements and are blending in the AS9100:1999 requirements. AS9000 has added two additional requirements to our 5.5.6 Control of Document system. They are 5.5.6(b) (i) Document change incorporation: the organization shall establish a process to ensure the timely review, distribution, implementation and maintenance of all authorized and released drawings, standards, specifications, planning, and changes. The organziation shall maintain a record of change incorporation and, when required, shall coordinate these incorporations with the customer and/or regulatory authority. (from AS9100:1999. para. 4.5.3). and 5.5.6(h) When customer furnished digital data is used for design, production and/or inspection, the Depot shall establish system controls in accordance with customer requirements. (from AS9100:1999. para. 4.5.3). While we know that a "Master Document List" is NOT an ISO or AS requirement, the standard basically requires that documents be controlled and retrievable. We have chosen to use an on-line approach that just happens to appear as a list of documents that the users can click and open. People, by nature, like lists. The added plus with our on-line DCS system is that you can do a "keyword" search to help you sort things out. Also, as we proceed down the document pyramid to the actual work documents, the level of control (open loop vs. closed loop) increases. ------------------ IP: Logged |
|
Andy Bassett Forum Contributor Posts: 274 |
OK folks. So i guess for my EDP documents i dont need a matrix or a master list. I can point at the Server and describe how it is managed in a controlled manner to ensure that the latest documents are available. But what about drawings from the customer. The company in question (small electronics assembler) has a good system with a SINGLE file for each product and a golden rule that when a new document is inserted the old one is MARKED and stored in the obsolete section. If you want the latest issue document you look in these files. Can i get away with this?. Can i use the same technique for other documents such as Standards/Parts Specifications/Supplier catalogues etc.? Living in hope ------------------ 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!
