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.
----- Original Message -----
From: <Brijesh_Bhaskaran -at- i2 -dot- com>
To: "TECHWR-L" <techwr-l -at- lists -dot- raycomm -dot- com>
Sent: Wednesday, July 23, 2003 6:15 PM
Subject: Re: Partnumbers
>
> Part Number are usually part of the manufacturing process...in this case
> documentation press process.
> Some companies who have their own Documentation PRESS unit, create Part
> Number for every documentation deliverable released for a version.
>
> So In due course when a customer requests for a documentation set, it
> becomes easier to retrieve the documentation from the config management
> tool and send it to print.
> Also, the part numbers can provide pointers to information like:
> - Version / Release Number
> - Year of Release
> - Associated documentation set
> etc etc
>
> HTH
> Brijesh.
<<Guru
Yes, this sounds right! We follow this process as well. Typically, the
prefix of a document part number represents the product/bundle/document
product (document deemed as a product). However, as far as my knowledge
goes, a part number does not necessarily provide information on the year of
release and stuff like that.
NEED TO PUBLISH FRAMEMAKER CONTENT ONLINE? "Mustang" is a NEW single
sourcing tool for FrameMaker that lets you easily publish your content
online. No macro language required! http://www.ehelp.com/techwr-l3
Mercer University's online MS Program in Technical Communication Management:
Preparing leaders of tomorrow's technical communication organizations today.
See www.mercer.edu/mstco or write George Hayhoe at hayhoe_g -at- mercer -dot- edu -dot-
---
You are currently subscribed to techwr-l as:
archive -at- raycomm -dot- com
To unsubscribe send a blank email to leave-techwr-l-obscured -at- lists -dot- raycomm -dot- com
Send administrative questions to ejray -at- raycomm -dot- com -dot- Visit http://www.raycomm.com/techwhirl/ for more resources and info.