TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
I think the key with document numbering is to set a standard and stick to
it, and to have one person in charge of assigning those numbers. We have two
different types of document numbering schemes where I work. Any type of
literature that is included with a product (i.e. manuals, dataplates, etc.),
and which are thus tracked in inventory like any other component, are given
a six digit part number that starts with the numbers 145. When we run out of
145xxx numbers, we'll move to 146xxx, etc. For literature that is not
tracked in our standard inventory system (primarily catalog sheets), we use
a numbering scheme starting w/ 201xxx. This system really works well for
us...it assures that all literature is easily trackable and identifiable,
and since no literature can be ordered without a part #, and only one person
can assign part #'s, it assures that any literature produced has gone
through the appropriate review process.
I believe this whole system is part of ISO 9001 procedures (it falls under
our design control process).
Marketing Services Manager
Plymouth Products, Inc. Sheboygan, WI
jjelinek -at- plymouthwater -dot- com
> -----Original Message-----
> From: Steve Arrants [SMTP:SArrants -at- DATAFUSION -dot- NET]
> Sent: Friday, March 27, 1998 3:04 PM
> To: TECHWR-L -at- LISTSERV -dot- OKSTATE -dot- EDU
> Subject: Internal Document numbering
> I've been asked to take over the management of internal
> documentation--specs, requirement documentation, etc. Does anyone have
> any references or web referrals for document numbering? Right now the
> developers and engineers give the documents their own document
> number--there's no rhyme or reason to this--the number doesn't seem to
> mean anything.
> I'd also appreciate any tips/information on setting up standards and
> procedures for the documents.
> steve arrants
> Stephen Arrants, Jr.
> DATAFUSION, Inc.
> 139 Townsend Street Suite 100
> San Francisco, CA 94107-1922
> 415.836.7843 fax 415.836.9050
> sarrants -at- datafusion -dot- net