A matrix tracking all procedures, work instructions, and documents

[Dawn]

I have created a matrix tracking all procedures, work instructions, and documents. Do I have to reference every work instruction and document in the system? Some work instructions do not specify what document number is used, and some document numbers on the matrix are not specifed in procedures and/or work instructions. In fact, some documents do not have a procedure and/or work instruction explaining what they are used for. The documentation manual explains briefly what they are used for, but that's about it. Am I in compliance?

[barb butrym]

can you get there from here? Cannot picture what you are asking...if you can get to the procedures/wi when needed to be sent there....and the revision is available for review..and under control..YA you should be Ok...unless i missed something in what you said.

[barb butrym]

You need some sort of connection that ties the system together...if procedure b is required to do any part of procedure a then procedure a has to reference how to get there ??????

[Marc]

Ya lost me too. To echo - 'Can you get there from here?'

See the http://Elsmar.com/pdf_files/ - Look for Doc_map_B.pdf

[Don Winton]

Dawn,

In fact, some documents do not have a procedure and/or work instruction explaining what they are used for.

It may be that you may be looking for a variation of the old ‘document’ tree paradigm. What I have done (FDA and ISO, not QS) is this:

Document A references document B and C. Document B references document D and E. Document C references no other documents.

You need some sort of connection that ties the system together...if procedure b is required to do any part of procedure a then procedure a has to reference how to get there

{Diagram was here}

In the printed circuit world, this follows the mother-daughter-grand daughter-great grand daughter, etc. concept.

I hope my little diagram helps illustrate. It is hard to do in a pure text world. . Of course, if a single document references more than one daughter (or grand daughter, etc.), there would be a branch in the tree. An affinity or tree diagram would probably be more specific, but that is more than can be posted here.

Am I in compliance?

Do not know. Would have to see the structure and that is not presented. Did not Marc’s document tree help?

Did my suggestion help, or did I just muddy the water.

Regards,
Don

ps. After review, the diagram doe snot seem to work. I have deleted it. Can send copy by e-mail if interested?

[This message has been edited by Don Winton (edited 02-23-99).]