C
CATERAF
Hi,
I've been searching through document control procedures in an attempt to work out how to write mine but no success so far..
My dilemma is that we have many (!) different places that documents are stored and they have different systems of approval, distribution, permissions, ownership, etc.
How do I document all these in one procedure?
Two examples are:
1. Software Documentation - We use Team Foundation Server to control our software development process. This includes requirements, design, test cases, code, etc. We do not want every document 'approved' because they'd be there all day so they just want to approve some documents, such as requirements.
2. Wiki - We use our wiki to store many process-related documents, records that are generated as part of a process, templates and forms, sales documents, software design that's not in TFS, etc. With the wiki everyone who has permission can make changes and save those changes. Some of the time we want documents 'approved' before release but other times we don't care so much and consider all changes an 'improvement' and the document can be reviewed by the document owner 'later'.
These are 2 examples but we have lots -- a production database, wiki, software program, emails, etc.
How should I co-ordinate all these differences into a single procedure? There are so many variations...
Oh, adding to that, with each 'process' we document what needs approval -- so it's almost doubling up to have it in the document control procedure.. or is it?
Also, I have problems knowing if a document is a record or not .. for example, sales orders are a document until they're set and then they're a record -- so do i need to class the accounting software (which stores them) as a document, or a record?
Any help with all of this would be very handy -- I'm really quite confused as to how to come at this. I've tried a few different ways but they aren't useful for the company, just for ISO.
Thanks!
I've been searching through document control procedures in an attempt to work out how to write mine but no success so far..
My dilemma is that we have many (!) different places that documents are stored and they have different systems of approval, distribution, permissions, ownership, etc.
How do I document all these in one procedure?
Two examples are:
1. Software Documentation - We use Team Foundation Server to control our software development process. This includes requirements, design, test cases, code, etc. We do not want every document 'approved' because they'd be there all day so they just want to approve some documents, such as requirements.
2. Wiki - We use our wiki to store many process-related documents, records that are generated as part of a process, templates and forms, sales documents, software design that's not in TFS, etc. With the wiki everyone who has permission can make changes and save those changes. Some of the time we want documents 'approved' before release but other times we don't care so much and consider all changes an 'improvement' and the document can be reviewed by the document owner 'later'.
These are 2 examples but we have lots -- a production database, wiki, software program, emails, etc.
How should I co-ordinate all these differences into a single procedure? There are so many variations...
Oh, adding to that, with each 'process' we document what needs approval -- so it's almost doubling up to have it in the document control procedure.. or is it?
Also, I have problems knowing if a document is a record or not .. for example, sales orders are a document until they're set and then they're a record -- so do i need to class the accounting software (which stores them) as a document, or a record?
Any help with all of this would be very handy -- I'm really quite confused as to how to come at this. I've tried a few different ways but they aren't useful for the company, just for ISO.
Thanks!