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: Operator vs. User From:"Steve Hudson" <steve -at- wright -dot- com -dot- au> To:"TECHWR-L" <techwr-l -at- lists -dot- raycomm -dot- com> Date:Wed, 16 Jan 2002 12:32:27 +1100
Ok - in very formal terms (multi-national / gov / mil), the hierarchy of HCI
candidates goes like this:
The lowest of the low is the User. For telecoms equipment, this is the dude
SENDING or RECIEVING the transmission. In Computer terms, they are
restricted to several applications, have no OS authority other than R/W to
data dirs and regularly must be restricted within the application they are
using. They know nothing about the equipment or processes that provide their
business functions, but know a lot about the business function and its
purpose.
Next comes the Operator. They operate the equipment or maintain the
processes that provide the business result. Common duties include power
on/off, backup/restore, start/stop functionalities, broadcast notifications
and act as 2nd level support. They have a modicum of OS access, and very
little application access other than to the config sections. They usually
know little about the business processes that the equipment or processes
support.
Then comes the Administrator. They have mega access to both App and OS, and
understand both intrinsically.
So, depending on the complexity of the equipment, you may have to have a
Users Guide, Operator Guide and Admin Guide.
Now, lets use a simple example.
Your product is a big PABX with handsets and a fiber port. Your User Manual
talks about using the handsets and how to place calls to the outside world
by dialing 0 first etc. The Operator Manual discusses how to shut the PABX
off and on, and what the little error lights mean, and how to fix them. The
Administrators guide discusses installing and configuring the PABX and the
handsets, and provides a guide for maintaining the system.
ITTH (I Know This Helps <snigger>),
Steve Hudson , HDK List MVP
Principal Technical Writer
Wright Technologies Pty Ltd (Aus)
EyeSpring - the future of graphics has been created.
Hello all out there!!!
A little help needed. As a non native English speaker (I'm Greek), I have a
small question:
What is the difference between a USER and an OPERATOR? My company produces
telecommunications equipment to be sold to large telecommunications operator
companies (France Telecom, etc.) as well as consumer products (i.e.
telephone sets) to be sold to private persons like you and me. We produce
both, Hardware and Software products. When shall we call a manual a User's
Guide or User's Manual and when Operator's Manual?
Last question: Is it User's/Operator's Manual or User/Operator Manual
(without 's)?
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Collect Royalties, Not Rejection Letters! Tell us your rejection story when you
submit your manuscript to iUniverse Nov. 6 -Dec. 15 and get five free copies of
your book. What are you waiting for? http://www.iuniverse.com/media/techwr
---
You are currently subscribed to techwr-l as: archive -at- raycomm -dot- com
To unsubscribe send a blank email to leave-techwr-l-obscured -at- lists -dot- raycomm -dot- com
Send administrative questions to ejray -at- raycomm -dot- com -dot- Visit http://www.raycomm.com/techwhirl/ for more resources and info.