The Elsmar Cove Business Standards Discussion Forums More Free Files Forum Discussion Thread Post Attachments Listing Elsmar Cove Discussion Forums Main Page
Welcome to what was The Original Cayman Cove Forums!
This thread is carried over and continued in the Current Elsmar Cove Forums

Search the Elsmar Cove!

Wooden Line
This is a "Frozen" Legacy Forum.
Most links on this page do NOT work.
Discussions since 2001 are HERE

Owl Line

The New Elsmar Cove Forums   The New Elsmar Cove ForumsThe Elsmar Cove Forums
  17025, Guide 25, A2LA (Cal., Meas., and Test)
  document and data control

Post New Topic  Post A Reply
profile | register | preferences | faq

UBBFriend: Email This Page to Someone! next newest topic | next oldest topic
Author Topic:   document and data control
hazel
unregistered
posted 23 July 2001 04:23 PM           Edit/Delete Message   Reply w/Quote
Can anyone provide me with an example of how to deal with the document and data control section of the manual. I am hitting a road block when setting up a master list and a distribution list.
Thank you

IP: Logged

David Mullins
Forum Contributor

Posts: 284
From:Adelaide, South Australia, Australia
Registered: Nov 1999

posted 23 July 2001 08:55 PM     Click Here to See the Profile for David Mullins   Click Here to Email David Mullins     Edit/Delete Message   Reply w/Quote
Personally I tend to deal with these issues as follows:

1. Include (document) master list in manual, 'cause everyone needs to know what docs there are and what the current date is (so they know they're reading the current version).
DocumentNumber Title IssueDate

2. Distribution lists merely need to identify who holds what documents.


------------------

IP: Logged

hazel
unregistered
posted 24 July 2001 11:10 AM           Edit/Delete Message   Reply w/Quote
Mr. Mullins,
Thank you for the response! Do you include the listing of your test methods and sop's in the same binder as the manual or seperately?

IP: Logged

David Mullins
Forum Contributor

Posts: 284
From:Adelaide, South Australia, Australia
Registered: Nov 1999

posted 24 July 2001 08:54 PM     Click Here to See the Profile for David Mullins   Click Here to Email David Mullins     Edit/Delete Message   Reply w/Quote
System Level Procedures I include in with the manual, but test methods/instructions I keep separate as I consider it lower level documentation, which probably gets used more.

If you're 17025, or heading that way, it's tidier to keep them separate, but if you're org is small, or don't have much diversity of methods, then there is nothing to prevent you have everything together.

------------------

IP: Logged

Marc Smith
Cheech Wizard

Posts: 4367
From:West Chester, OH, USA
Registered:

posted 26 July 2001 05:04 PM     Click Here to See the Profile for Marc Smith   Click Here to Email Marc Smith     Edit/Delete Message   Reply w/Quote
See Doc_Matrix.pdf and Doc_Structure.pdf

in /pdf_files/

for a few ideas.

Also, don't forget /gif/doc-pyramid.gif

IP: Logged

All times are Eastern Standard Time (USA)

next newest topic | next oldest topic

Administrative Options: Close Topic | Archive/Move | Delete Topic
Post New Topic  Post A Reply
Hop to:

Contact Marc Smith | The Elsmar Cove Home Page

Please Visit the new Elsmar Cove Forums! All these threads are there and much more!

Main Site Search
Y'All Come Back Now, Ya Hear?
Powered by FreeBSD!Made With A Mac!Powered by Apache!