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 am a lone tech writer in a small company. We are currently
Involved in a large engineering project for a huge corporation
(which shall remain nameless).
We have to become ISO 9000 certified by the end of the summer, and
we're just starting now!
As part of this effort, I have been asked to take over, re-think and
implement a new configuration management strategy.
Currently, we have a good system for managing software releases, but
not for documents. I have already set up a paper strategy for
controlling releases and other documents, and am looking at PDF for
digital copies of formal releases.
BUT, I am having trouble with organization. Our numbering system is
sadly lacking, and right now we track everything (documents of all
types, drawings, release notes etc.) on separate paper logs. Clearly
there has to be a better way!
I have looked at some of the configuration management software
packages briefly, but they seem to be far more than we need, both in
features and price.
Our options are wide open, and I could get some money if I needed to,
but I would rather adopt a simple, yet scaleable strategy. (Most of
the systems available seem to need weeks of training, and
professionals to implement them.)
This is open ended, but I'm hoping someone else on this list has gone
through the same process, and has some input on configuration
managements strategies that work for ISO, and are simple to
implement.
