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.
---Scott Havens <SHavens -at- ELCOTEL -dot- COM> wrote:
>
> Kate,
>
> In that case, I'd say that your customer ("COTS") documentation should
> include whatever descriptive, operational, maintenance, and
> troubleshooting information your customers might reasonably be
> expected to use or need.
>
Wrong. That puts you on the hook for whatever the customer says they
want or need. For example. Suppose your COTS manual includes
troubleshooting to a board or group of boards, and no further. You
expect the customer to return the boards to you for repair. If they
think they need troubleshooting to a component on the board should you
supply it? No, unless they want to pay extra for it.
At some point the customer shuold have looked at the documentation and
decided this was the unit he wanted, and he knew what the
documentation was like. If he wants more?--he pays for it!
Your company set a price on the COTS equipment based on your standard
COTS manuals. If you have to spend time re-writing or adding to and
modifying the manuals someone has to pay for it.
Generally MIL-SPEC Manuals cost more. If they want MIL-SPEC manuals,
let them pay for them.
Be careful what you promist without talking it over with your
financial and legal people.
Cam Whetstone
_________________________________________________________
DO YOU YAHOO!?
Get your free @yahoo.com address at http://mail.yahoo.com
