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: Cost Analysis for FrameMaker From:Fabien Vais <phantoms -at- POP -dot- TOTAL -dot- NET> Date:Mon, 28 Jun 1999 17:17:30 -0500
Kari Alt wrote:
>Hello,
>I just moved into a new Technical Writing job where the TechComm department
>uses PageMaker for the majority of their technical user manuals which are on
>average 100-200 pages long. I have expressed my concern to my supervisor
>that PageMaker is not the right tool for the job and FrameMaker would be a
>better choice. She agrees with me, but before I can order FrameMaker she
>has asked me to create a cost analysis in terms of how much the department
>can save by using FrameMaker instead of PageMaker (time spent formatting,
>creating indexes, etc.). I have never done a cost analysis, and I am not
>sure what needs to be included, items to consider, etc.
>Do you have any resources, ideas, or tips that I could use?
>Thank you in advance and let me know if you need any more information....
I would say that I don't know how to do a serious cost analysis, and that
that isn't what I was hired to do. And besides, I would tell my supervisor
that there is plenty of documentation to the fact that FrameMaker is now the
industry standard for the kind of work I am doing, and I shouldn't have to
"prove" anything any more.
What your super is asking for would take you hours, if not days to
calculate, and would be based almost entirely on APPROXIMATIONS. Don't get
sucked in.