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.
Subject:RE: Repair Parts List Organization From:"Nuckols, Kenneth M" <Kenneth -dot- Nuckols -at- mybrighthouse -dot- com> To:"TECHWR-L" <techwr-l -at- lists -dot- techwr-l -dot- com> Date:Thu, 4 Aug 2005 10:44:57 -0400
Tom asked....
>
> Good morning,
>
> Here's a question for non-software writers.
>
> If you were designing a list of parts for a complicated machine, how
would
> you organize the list?
>
> [snip]
>
> Now, all the parts are in a database and I have the task of designing
the
> parts list (for printed copies) and I wonder how we can make the
> information more accessible. Although it is broken down by assembly,
the
> lists seem almost random and I can't imagine trying to locate a
particular
> part in the list to find out what I need to buy to fix my machine.
>
> I'm assuming we'll organize the list by assembly/system, but should we
> sort by our part number or manufacturer or part name (description) or
the
> manufacturer's part number. Due to different numbering schemes, the
last
> option does not seem at all reasonable.
>
> Our products aren't hugely complex (like the space shuttle), but the
parts
> lists have several hundred items in total.
>
If I'm understanding correctly you're looking for organization methods.
The first two options that come to mind are organizing by each nested
sub-system from largest to smallest within the machine or organizing by
what sub-systems are (historically) most prone to needing
repair/replacement.
Take a car for example. You could organize the Electronics by starting
with "Engine Controls" as a major sub-system with "Fuel Injector
Controls" "Exhaust sensors" "Timing Controls" etc. as nested
sub-systems.
Or you could start with a list of systems that include the most commonly
replaced parts: changeable filters, tires and brakes, exterior lamps,
and the like.
CONFIDENTIALITY NOTICE: This e-mail may contain information that is privileged, confidential or otherwise protected from disclosure. If you are not the intended recipient of this e-mail, please notify the sender immediately by return e-mail, purge it and do not disseminate or copy it.
Now Shipping -- WebWorks ePublisher Pro for Word! Easily create online
Help. And online anything else. Redesigned interface with a new
project-based workflow. Try it today! http://www.webworks.com/techwr-l
---
You are currently subscribed to techwr-l as:
archiver -at- techwr-l -dot- com
To unsubscribe send a blank email to leave-techwr-l-obscured -at- lists -dot- techwr-l -dot- com
Send administrative questions to lisa -at- techwr-l -dot- com -dot- Visit http://www.techwr-l.com/techwhirl/ for more resources and info.