I cannot follow you exactly,but I think issue no. is the flow code/No. of documents changing. And revision is a Letter or figure for some document changing.
Example: issue no. 200705001,200705002,...
revision A,B,C,.... or 1,2,3,... Even A.1,A.2,...B.1,B.2,...etc.
This is a very basic question but yet very difficult to reply, because both the terms "Revision" and "Issue" sounds so similar !!!!
What I have understood over the years of my experience that we set up a thershold limit of revision no.s and then go for a complete change of issue.
For example, If we have set the threshold limit of 20 revisions in the mandatory procedure of control of documents (4.2.3) and the first issue having an issue no. 01, and revision 00, then till revision no 19, the same issue no. 01 will be continued. Immwdiately the revision no. reaches 20, we will do a issue change and the current status of the document will be Issue no. 02 and revision no. 00.
It is like changing to a new car after you carry out 20 repairs to your old car.
However, if the procudure of control of documents demands change in issue no, with each change in quality objective, mission, vision and organization structure , etc. that needs to be blindly followed. Afterall it is a matter of top management decision.
If you want to make a small change you revise an existing document.
If you are making a large number of changes at the same time then the document might be better reissued (so the amendments do not make document less readable)
We used to have both issue and revision on our documents, but elected to streamline document management many years ago: Today we use issue only, and most companies around these parts have marched down the same path.
Re: How do we differentiate between the issue number & revision
We do have an issue date, and then revision numbers. If a revision is huge, changes the process completely, or otherwise pretty much changes everything, we re-issue the document and go back to rev 0. Let's say we had a manual operation, and then closed the are down and totally automated it, we would not longer need step by step instructions for the manual process, but instructions for how to control and maintain operations via computer control. The WI would still be for that process, but nothing about it would be the same. New issue date/rev 0.
Yes. All you're really trying to achieve is an answer to the questions:
[1]What is the current status of this document?
[2]How can I distinguish this particular document from another version (or revision)?
So, if the document bears something like 'Revision 1' or 'Revision 2', you can answer those questions. And identify that Revision 2 is the later and current version.
Bottom line: you choose & use a system that works for you. I generally find both version number and revision number overkill - but I've very occasionally come across highly technical, specialised systems where they actually did need both, or had a preference for that degree of technicality.
At the even simpler end of the scale, I've often successfully used a system of just identifying documents via the date, using the {savedate} function in Word (NOT printdate) to achieve that.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to the use of cookies.