While working at VMIC/GE Fanuc (1998-2003), I began as part of a team of six writers
and eventually began doing the work that the entire group of writers previously
performed. As writers would leave, the company did not replace them. This required that
I be a very efficient worker, since short deadlines and time management were a way of
life. In addition to writing software documentation driver documentation (my primary
task), I also wrote and produced the hardcopy documentation and online help for the I/O
Works software-based control suite of products (three large user guides and
approximately ten help files). In addition to my documentation tasks, I regularly made
suggestions regarding the software interfaces and dialog box layout in software
products.
I typically worked with other departments and performed tasks such as writing
specifications and reviewing their documents from other departments. One of my most
rewarding experiences was converting documentation from Apple software to PC-
based files and producing a documentation CD containing PDF files of the documents.
I was assigned to head up this project and interfaced with my manager, the head of our
documentation configuration department, other writers, the public relations department
and hardware manufacturing. Among the tasks I performed were: finding an acceptable
software product for converting Apple software documents to PC format with minimal
cleanup; defining, documenting and providing a process for preparing the documents
for PDF generation; creating the interface for accessing the documentation from a CD;
creating the layout of the CD and maintaining the CD content.
Technical communication, by its nature, is a discipline in which complex items must be
conveyed into easy to understand instructions. My work with the I/O Works suite of
products is an excellent example. This product allows users who are programmers to
create schematic-like drawings that will be translated into instructions that may be used
to control industrial automation hardware. I maintained a tutorial that led users through
an example of creating a program, which eventually became its own getting started
guide when the product grew and became too complex to be explained with a simple
tutorial. I wrote the getting started guide while consulting with a software certification
analyst. I wrote an outline of what I wanted to do and how it should be performed, after
which she would review my work and make suggestions based on her experience with
customers.
PDF files require Adobe® Reader®. Click on the following icon to download the
software.
and eventually began doing the work that the entire group of writers previously
performed. As writers would leave, the company did not replace them. This required that
I be a very efficient worker, since short deadlines and time management were a way of
life. In addition to writing software documentation driver documentation (my primary
task), I also wrote and produced the hardcopy documentation and online help for the I/O
Works software-based control suite of products (three large user guides and
approximately ten help files). In addition to my documentation tasks, I regularly made
suggestions regarding the software interfaces and dialog box layout in software
products.
I typically worked with other departments and performed tasks such as writing
specifications and reviewing their documents from other departments. One of my most
rewarding experiences was converting documentation from Apple software to PC-
based files and producing a documentation CD containing PDF files of the documents.
I was assigned to head up this project and interfaced with my manager, the head of our
documentation configuration department, other writers, the public relations department
and hardware manufacturing. Among the tasks I performed were: finding an acceptable
software product for converting Apple software documents to PC format with minimal
cleanup; defining, documenting and providing a process for preparing the documents
for PDF generation; creating the interface for accessing the documentation from a CD;
creating the layout of the CD and maintaining the CD content.
Technical communication, by its nature, is a discipline in which complex items must be
conveyed into easy to understand instructions. My work with the I/O Works suite of
products is an excellent example. This product allows users who are programmers to
create schematic-like drawings that will be translated into instructions that may be used
to control industrial automation hardware. I maintained a tutorial that led users through
an example of creating a program, which eventually became its own getting started
guide when the product grew and became too complex to be explained with a simple
tutorial. I wrote the getting started guide while consulting with a software certification
analyst. I wrote an outline of what I wanted to do and how it should be performed, after
which she would review my work and make suggestions based on her experience with
customers.
 | VMISFT-566x Fibre Channel Drivers Installation Manual (PDF) | |
| Common RFM2g API and Command Line Interpreter for VMISFTIRFMG2 Drivers | |
| Installation Manual (PDF) - This manual contained common commands shared between the drivers for the IRIX®, Linux® and VxWorks operating systems. I also created user guides for each of these operating systems. | ||
| 64-channel Isolated Digital Input Board with Multifunctional Intelligent Controller | |
| (PDF) - I reformatted and updated this existing VMIC manual to conform to GE Fanuc standards. |
PDF files require Adobe® Reader®. Click on the following icon to download the
software.
 | |  | |  | |  | |  |
Example Documents: VMIC/GE Fanuc
Other Example
Documents:
Avocent Corporation
CW Government Travel
Documents:
Avocent Corporation
CW Government Travel