Академический Документы
Профессиональный Документы
Культура Документы
GE Energy
g
© 2005 General Electric Company, USA.
All rights reserved.
This document presents standards of style and usage adopted by the Documentation
Design team at GE Energy, Salem, VA. It is intended to help writers and editors maintain
consistency within and across products. These guidelines represent their expertise and
opinions of what best serves GE Salem documentation teams and their customers.
Fax No.
Your Company’s Name and Address Job Site
Phone No.
GE Requisition No.
E-mail
Your Job Function / How You Use This Publication Publication No.
Address
General Rating
Excellent Good Fair Poor Additional Comments
Contents { { { { ____________________________________________________________
Organization { { { { ____________________________________________________________
Technical Accuracy { { { { ____________________________________________________________
Clarity { { { { ____________________________________________________________
Completeness { { { { ____________________________________________________________
Drawings / Figures { { { { ____________________________________________________________
Tables { { { { ____________________________________________________________
Referencing { { { { ____________________________________________________________
Readability { { { { ____________________________________________________________
Specific Suggestions (Corrections, information that could be expanded on, and such.)
Page No. Comments
_____ _________________________________________________________________________________
_____ _________________________________________________________________________________
_____ _________________________________________________________________________________
_____ _________________________________________________________________________________
_____ _________________________________________________________________________________
_____ _________________________________________________________________________________
Other Comments (What you like, what could be added, how to improve, and such.) ________________________________________________
__________________________________________________________________________________________
__________________________________________________________________________________________
__________________________________________________________________________________________
__________________________________________________________________________________________
__________________________________________________________________________________________
__________________________________________________________________________________________
Overall grade (Compared to publications from other manufacturers of similar products, how do you rate this publication?)
{ Superior { Comparable { Inferior { Do not know Comment ____________________________________________
____________________________ Place
stamp
____________________________ here.
____________________________
GE Energy
Documentation Design, Rm. 293
1501 Roanoke Blvd.
Salem, VA 24153-6492 USA
Introduction
This document provides style guidelines for documents created at GE Energy,
Salem, VA that are intended for customers. These guidelines are directed at those
responsible for the documents, in order to maintain consistency within and across
products. This includes Technical Sources who supply technical inputs, and the
Technical Authors/Editors who produce the final publication.
The purpose of these guidelines is twofold: to help expedite the documentation cycle
through standardization and to create functional documents.
Standardizing reduces cycle time because it pre-defines publication content and
format. For the Technical Sources and Authors, this eliminates time spent “re-
inventing the wheel” for each new product publication. For the user, the resulting
consistency in organization and presentation simplifies the task of finding and under-
standing written instructions for complex products.
Functional publications are documents designed specifically as tools that supplement
the product(s) they cover. Their sole purpose is to provide accurate, complete, and
needed information about a product in a form easy to use and understand. This is
achieved by applying professional technical writing standards, which includes con-
sistent organization, format, and style.
Document Organization
This document includes the chapters defined below.
Chapter 1 – Overview. Briefly defines the purpose and contents of the document,
and how to use it.
Chapter 2 – Style Guidelines. Provides guidelines for readability, word usage,
punctuation, and typefaces.
Chapter 3 – Document Format. Defines page layout, text format, and guidelines
for online documents.
Chapter 4 – Document Structure. Defines document and page structure and how
to defne graphics
Appendix A. Defines the documentation numbering scheme.
Appendix B. Describes how to create an Adobe Acrobat .pdf file.
Introduction
Style is a standardized method of presenting printed material to achieve consistency.
This includes word usage, punctuation, spelling, typography, and arrangement. For a
business creating technical documents, style is a writing tool used to convey a
professional image and indicate the quality of its products. Disorganized, poorly
and/or incorrectly written documents suggest that second-rate practices may be used
in other areas of a company, as well.
For additional or more This chapter defines a style for Salem, GE Energy technical documents. This style
detailed information, there follows the GE Corporate Identity Program's guidelines for printed material. Addi-
are many commercial tionally, it incorporates principles of professional technical writing, modern English,
technical writing manuals electronic publishing, and Microsoft guidelines.
available.
This chapter cannot substitute as a complete style manual or teach grammar and
technical writing. Its purpose is to present basic direction to an author along with
specifics for commonly misused words and construction.
Note When style rules in other guides differ with this one, this document's instruc-
tions should be used.
Section Page
Document Format.....................................................................................................2-2
Readability................................................................................................................2-2
Grammar...................................................................................................................2-3
Punctuation...............................................................................................................2-4
Number Usage..........................................................................................................2-6
Abbreviations and Acronyms ...................................................................................2-7
Word Usage............................................................................................................2-10
Spelling and Compounding ....................................................................................2-15
Typestyle ................................................................................................................2-19
Warnings, Cautions, and Notes ..............................................................................2-20
Readability
An author must know two factors when producing documentation:
• The type of audience (the users)
• The different mediums used to present the information (paper, online, web)
The users of GE technical documents are culturally diverse with varying degrees of
technical training. Therefore, to improve readability, narrative text should be written
to a 10th grade reading level.
To do this, use the following guidelines:
• Keep words short and simple. The average word length should be about 1.6
syllables.
• Keep sentences short, avoiding compound sentences. Average sentence length
should equal 17 words.
• Use words familiar to the general population. For technical terms, use those
most easily understood by technicians trained in that field.
• Be consistent with use of terms. For example, the door, the front, and the panel
might be the same item on a drive, but you should refer to it only by one of
those terms.
• Avoid jargon and slang. Keep in mind that some readers may not understand
such terms and phrases. Additionally, jargon and slang are difficult to accurately
translate into foreign languages.
• Do not use non-English expressions, such as i.e., e.g., and etc. Use their English
equivalents: that is, for example, and so on.
• Use tables instead of narrative text to compare three or more items with
common characteristics.
• If multiple items or ideas need to stand out, list them (see Chapter 3, section
Lists/Steps).
Even when the information is written simply, readability is affected by the viewing
medium. Words and graphics displayed mainly on a computer monitor are visually
different than that printed on a standardized and familiar piece of paper. Therefore,
do not vary the style of presentation and provide the best solution that works best for
all mediums.
Quotation Marks
Use quotation marks sparingly. Use them for:
• Direct quotations (which are seldom needed in technical documents.)
• Technical terms used in a special or nonstandard way. When necessary, it is
better to use a standard technical term in a non-standard way than to coin a new
term that may not be understood.
Do not use quotation marks for:
• Terms such as named, called, and known as (use italics). For example:
In the toolbox, block, macro and module parameters are called pins.
The controller window is created with the default name, uc1.
• Using words as words or letters as letters (use italics).
• Emphasizing a word (use bold).
The second example makes A period should always fall within the closing quotation mark, unless the period -
clear that the user does not could be mistaken for part of the term within the marks. For example:
type in the period along with
• The wire is marked “L1 ”
the letters
• Type “START”.
Apostrophes
Apostrophes are used to indicate possessive form, except with the word it. Its forms
the possessive while it's is a contraction for it is. Do not use an apostrophe before the
s to indicate plural forms of acronyms. For example: LEDs, MMIs, GTOs
Form the possessive
the box’s contents
Burns’s poems
Berlioz’s opera
an OEM’s product
the Joneses’ computer
Number Usage
Generally, spell out numbers below 10; use figures for 10 and above.
When 2 or more numbers appear in a sentence and 1 of them is 10 or more, use fig-
ures for each number.
Use figures for units of measurement and time. A unit of measure does not affect the
use of figures and other numerical expressions in a sentence. For example:
The 15-inch unit includes two pushbuttons and eight LEDs.
Use figures for serial numbers. For example:
pages 5 and 6, drive 1, bits 0 – 15
A sentence must begin with a spelled-out number and not with a figure.
Misused Words
This section covers the following words, which are commonly misused in technical
documents:
a, an Use the article a before a word that begins with a consonant sound. Use the article
an before a word that begins with a vowel sound.
Change: The spare boards include a DSPX, a FOSB, a IGPH, and a CTBC.
To: The spare boards include a DSPX, an FOSB, an IGPH, and a CTBC.
affect, effect Affect is a verb that means influence. Effect is a noun that means result. (Effect is
also a verb that means bring about, but usage is restricted and should be avoided in
technical writing.)
Change: The number of drops on the LAN effects message speed.
To: The number of drops on the LAN affects message speed.
Change: Dust has a negative affect on hardware.
To: Dust has a negative effect on hardware.
Or to: Dust can negatively affect hardware.
annunciate, enunciate Annunciate means to announce. Enunciate also means to announce, but implies
speaking.
Change: Trip or State faults are enunciated on the front panel display.
To: Trip or State faults are annunciated on the front panel display.
Or to (better): Trip or State faults are shown on the front panel display.
comprise, include Comprise means include. In other words, the whole comprises the parts, the parts do
not comprise the whole.
Change: The five boards comprise the module.
To: The module comprises the five boards.
Or to (better): The five boards make up the module.
Accuracy
Make sure that the product name is spelled and written correctly and consistently
throughout a technical document. The printed document, online help, dialog boxes,
and screens should all be the same. When creating a technical document:
Check for correct presentation. For example:
• DLAN+, not Dlan+
• ISBus, not ISBUS, IS-Bus, or IS Bus
Make sure that the name or term used is the correct name and consistent with other
documentation. For example:
For legal implications, see • DLAN+, not ARCNET (DLAN+ is the correct name for the GE Industrial
the next section. Systems drive LAN that uses ARCNET protocol).
• Control System Toolbox is referred to as toolbox, not tool.
• ISBus is not the Insynch bus.
Use only the official name, not the internal slang or shortened version. For example:
• GE Industrial Systems, not GEIS or GE-IS
• Low Voltage AC drives, not PWM2
Refer to the product by what it actually is, not by its type (which is usually a descrip-
tive adjective). For example:
• the DC2000 drive, not the DC2000
• the Lodtrak module, not the Lodtrak
However, when the acronym or abbreviation includes the product (the noun), it can
be used to represent the product. For example:
• IOS means Intelligent Operator Station; use the IOS not the IOS station
• SDB means System Database; use the SDB not the SDB Database
• RAM means random-access memory; use RAM not RAM memory
• HMI means Human-Machine Interface; use HMI not HMI interface
a lot alot
alphanumeric alpha numeric, alpha-numeric
ARCNET arcnet, Arcnet
autotune auto tune, auto-tune
backplane back plane
back up (verb) backup, back-up
backup (noun, adj.) back up, back-up
baud Baud, Baud, baud-per second
bus, buses buss, busses
callout (noun, adj.) call out
call out (verb) callout, call-out
canceled cancelled
center-tapped center tapped
coordinate co-ordinate
daisychain (noun, verb) daisy chain, daisy-chain
data type datatype
daughterboard daughter board
desktop desk top, desk-top
DIRECTO-MATIC Directomatic, directomatic
DC-300 DC300, DC 300
DC2000 DC-2000, DC 2000
DLAN+ D-LAN plus, dlan+
dual-ported dual port, dual ported
feedback (noun, adj.) feed back, feed-back
feed back (verb) feedback, feed-back
fiber-optic fiber optic
flammable inflammable, flameable
flowchart flow chart, flow-chart
Genius (the product) genius
handtight, handtighten hand tight, hand-tight
heatsink heat sink, heat-sink
keyboard key board, key-board
lefthand (adj.) left hand, left-hand
lineup (noun) line up, line-up
line up lineup, line-up
lockout lock out, lock-out
Note All documents that contain a GE number (GEH, GEI) must receive legal
review and approval.
Because Warnings and Cautions have a clear and legally-binding meaning, do not
use those terms for other situations or conditions.
Change: When a runtime error is detected, the software displays a warning on the
screen.
To: When a runtime error is detected, the software displays an error indication (or
fault) on the screen.
Introduction
This documentation design is This chapter defines a standard format for documents to streamline the process of
a deliberate composition creating both printed and online documents for Windows applications. This format
based on studies of includes document layout, page layout, text style, and conventions selected for
readability and effective Salem, GE Energy software documents.
online presentation.
Section Page
Introduction ..............................................................................................................3-1
Before You Begin.....................................................................................................3-2
Text Format/Styles ...................................................................................................3-3
This is Heading 2......................................................................................................3-3
This is Heading 3...............................................................................................3-3
Typestyles/Conventions ...........................................................................................3-4
Documenting Software......................................................................................3-4
Cover Components ...................................................................................................3-5
Balancing/Forcing Page Breaks ........................................................................3-6
Table of Contents ..............................................................................................3-7
Chapter Page Numbering ..................................................................................3-8
Lists/Steps .........................................................................................................3-9
Adding Callouts...............................................................................................3-10
Tables ..............................................................................................................3-10
Margin Notes...................................................................................................3-10
Dialog Boxes and Menus........................................................................................3-11
Defining a Dialog Box ....................................................................................3-11
Defining Menus and Commands .....................................................................3-12
Screen Shots ...........................................................................................................3-12
Inserting Picture Files.............................................................................................3-13
Safety Symbols.......................................................................................................3-15
Page Footer.............................................................................................................3-15
Notes.......................................................................................................................3-16
Click the Tools menu, Options… and the View tab. If you ever open a .doc and all your figures display as blank
boxes, clear the option Picture placeholders.
This is Heading 2
This is Heading 3
This is Body Text.
Convention Meaning
Arial Used for all headings, commands, tables, callouts and file
path extensions and names.
Times New Roman Used for all basic text.
Software Conventions
When documenting a software application that contains a Windows-based platform,
some explanation may be needed, but do not go into great detail in explaining the
Windows environment. Refer the reader to the appropriate document. The
following list can be used to present some basic guidelines for working with menus:
A command that ends in an ellipsis (…), means there is another dialog box that asks
you to supply more information.
If a command turns a feature on and off, a check mark ( ) displays by the command
name when the feature is on.
When you select a command that ends with an arrow ( ), the menu cascades to
display more command names.
If a command name is grayed, it indicates that the command does not apply to the
current situation or that you need to make a selection or complete another action
before selecting the command.
g
GEH-6676
GE Energy
The document number
The sidebar graphic is must be in Arial, bold,
WordArt and can be 10 pt. and align left
edited in the headers/ with the GE company
footers view. Double– name. If the document
click the graphic and a is a revision, add the
box displays to edit the Supersedes number
text below in parenthesis.
Tip Use this procedure for every page to control the text from falling on an
opposite page.
Click OK.
Table of Contents
Refer to the table of contents The style and field code for master table of contents (GEH) is generated
in this document. automatically with the wizard when you create a document and apply Heading 1, 2,
and 3. However, a chapter or a GEI table of contents style must be created.
To create a table of contents style and field codes
This style has already been 1. Create a style called TOChead: select TOC Base + Font; Arial, Bold, Italic,
created in the revised Indent: Left 2", Border: Bottom (Single solid line, ½ pt Line width), Border
template for Salem, GE spacing: 1 pt, Tabs: 6.75" right flush.
Industrial Systems.
2. Type the words, Section Page and select the style TOChead. Place the
cursor in front of the word Page and press Tab. The word Page becomes flush
right (see the example below).
3. To create a new line, press Enter (the cursor moves to a new line), and press
Ctrl+Shift B (to insert the style, Body Text).
4. With the cursor on this line (see example below), press Ctrl+F9.
Two brackets { } are created.
The numbers "2-3" refer to 5. Place the cursor between the two brackets { } and type, TOC \o "2-3". (This is
Heading 2 and Heading 3. your field code for the automatically generated table of contents.) To include the
chapter number with the page number, type TOC \o "2-3" \s Chapter.
6. To automatically generate the table of contents, place the cursor within this field
code (area turns gray) and press F9.
Section Page
Step 2 and 3 above
{TOC \o "2-3"}
Step 4 and 5 above
Tables
Use the style, Caption Tables should be formatted using the style, Body Text Table (Arial, 9 pt) and the
for the table title. following guidelines:
All table headings should Example of a Table
be in bold.
Heading Heading Heading
A ½ pt. line separates
the heading and table Body Text Table Body Text Table Body Text Table
text, and ends the table. column column column
Center large tables and text text text
extend the entire width of
the page (Normal style). When formatting a table, avoid dividing a table between two pages. If a table is
continued on another page, repeat its title followed by (-continued) in the title.
Repeat its column headings. If a table is very long, break the information into
logically related sub tables. Use rules between rows of common information or if the
table is long. Keep the spacing between columns minimal, so rows are easier to read
across the width of the page.
Margin Notes
Notes can be inserted in the left margin, of a document created in Doc-To-Help.
Insert Margin Note These margin notes can be used to define a word in the paragraph or place an
button annotation, comment, or small graphic. The margin notes do not appear in the Help
unless you explicitly link them to the text, in which case they become popup
Insert Link to Margin definitions. For specific instructions on how to insert margin notes and link to a
Note button margin note in the Help, see the User’s Guide to Doc-To-Help, and the section
Margin Notes.
Note Do not abuse this feature. Too many margin notes and jumps can become
annoying to the reader.
Screen Shots
To create a screen shot
1. Select the desired window or dialog box.
2. Press Alt + Print Screen.
3. From the Edit menu, select Paste Special and proceed as indicated below:
Uncheck
Select Picture
Note Do not edit drawings, photos, and figures in Word. If the picture needs to be
edited, use the .vsd file and edit in Visio.
Uncheck
Select Picture
1" 3.75"
The Note and Tip use
the style Note, which Note Indicates an essential or important procedure or statement.
has a 2" indention.
All text in a Tip should
be italicized. Tip Provides essential information that is not normally defined in regular use but
from an experienced user.
Page Footer
The page footer must contain the following information (see footer on this page):
• Document number and name (inside on page format)
• Chapter title and page number (outside on page format)
Use the following guidelines when creating a page footer:
• 9 pt. Arial, italics
• Information must be flush right or left as applicable to an odd or even page
• If the chapter ends on an odd number page, create an even number last page so
the new chapter begins on an odd number page (see the section,
Balancing/Forcing Page Breaks).
Introduction
This chapter defines a standard structure for a typical Salem GE Energy document.
Because of the number and variation in products, this standard can serve only as a
guideline for creating customer documentation. However, all documents should
follow as closely as possible the organization defined in this manual.
Section Page
Introduction ..............................................................................................................4-1
Determining Documentation Needs .........................................................................4-1
Document Structure..................................................................................................4-2
Small Documents .....................................................................................................4-3
Document Content....................................................................................................4-4
Outline of User Guide ..............................................................................................4-5
Outline of Installation/Startup Guide........................................................................4-7
Outline of Maintenance and Troubleshooting ..........................................................4-9
Outline of System Guide – Volume I .....................................................................4-10
Outline of System Guide – Volume II....................................................................4-12
Outline of I/O Packs/Boards (GEI) ........................................................................4-12
Outline of Software Applications ...........................................................................4-13
Note Any variations in content and organization should be defined in the initial
document planning stages by the documentation leader, responsible technical author,
and technical source.
Type of Document
Before you begin a document, A document’s format is partly determined by the type of document it is. Document
consider its content and types differ mainly in length and format, which are determined by the complexity of
length. the product and amount of data provided. Smaller type documents, such as GEIs, do
not require front-matter that is standard or needed in longer documents. However,
they do require important information such as copyright and issue date, and
proprietary information shown in this chapter.
Content Organization
A typical document should include the following:
For examples, refer to the • Cover (includes document title and number)
pages in this document.
• Copyright, trademark page (includes legal matter and issue date)
• Safety symbol legend page
• Standard and special warnings and cautions for particular document
• Reader Comment Form
• Table of Contents
• Chapter 1 Overview
• Appropriate chapters defined in this chapter
• Glossary of Terms
• Index
Identification
Every official GE technical document requires a documentation number that
identifies it. This number is controlled and assigned by the Documentation group.
These numbers include
• Three-letter alphabetic prefix
For more information, refer • Numerical base number for that particular prefix
to Appendix A.
• Alphabetic suffixes to show revision and language, if applicable
g GE Energy GEI-100600
Note The following sections define a basic outline of the structure of Salem NPI
documentation. Obviously, variations may be required, based on the product
differences. However, the basic structure should still be followed.
Chapter 1 Introduction
Equipment Overview Hardware Overview
This chapter should briefly Software Overview
introduce the user to the Technical Characteristics (specifications)
control and its features, Technical Assistance
define the manual, and Related Documentation
provide quick important
reference information (such
as the related publications
and the GE Post Sales
Service phone number).
Chapter 3 Introduction
Printed Wiring Boards Control Boards
Overview I/O Terminal Boards
Bridge and Protection Boards and Modules
Power Supply Boards and Modules
Related Board Publications
Chapter 4 Introduction
Terminal Board I/O and Power Connections and Analog I/O
Equipment Connections Customer Contact I/O
Terminal board and customer Power Supply Inputs
connections (Board I/O Line Filter Connections
typically covered in board Exciter Internal I/O
GEIs) De-Excitation
Crowbar
Field Ground Detector
Field Flashing
Shaft Voltage Suppressor
Data Highway Connections
Control System Toolbox Connections
Appendix A Introduction
Warranty and Renewal Parts Identifying the Part
This standard chapter should Warranty Terms
be the same for all controls. How to Order Parts
Its purpose is to tell the user
how to identify and order a
part.
Glossary of Terms
Index
Chapter 1 Introduction
Overview How To Use this Document
This chapter should briefly Equipment Covered
introduce the user to the Applications
document and its features, Related Documents
and provide quick important Acronyms and Abbreviations
reference information (such
as the related publications
and the GE Post Sales
Service phone numbers).
Chapter 2 Introduction
Installation Planning Installation Support
Mounting Equipment
Chapter 3 Introduction
Handling and Mounting Handling Procedures
Guidelines
Chapter 4 Introduction
Cabling and Connections Regulator Control External Connections
This chapter that should be Grounding and Cable Entry
the same for all cabling and Control and converter Power
connections. It describes Exciter Field Connections
practices that should be Signal Communications and Cabling Guidelines
followed when setting up Regulator Control Internal Connections
the installing cabling. It is Preventing Cable Damage
included as a reference for
installation personnel, who
need to ensure proper
installation.
Chapter 5 Introduction
Cable Separation and Equipment/Material Needed
Routing Securing Equipment for Safety
This standard chapter Hardware Checks
should be the same for all
controls. It describes
practices that should have
been followed when setting
up the installation site
before the control arrives. It
is included as a reference
for installation personnel,
who need to ensure proper
installation.
Appendix A Introduction
Understanding Equipment Data Nameplate
Drawings Identifying the Equipment
Drawing Numbers
Outline Drawings
Panel Drawings
Elementary Diagrams
Appendix B Introduction
Cable Separation and Low-Level Signals (Level L)
Routing Medium-Level Signals (Level M)
High-Level Signals (Level H)
Power (Level P)
Class Codes
Cableway Spacing Guidelines
Appendix C Introduction
Installing Fiber-Optic Cable Cable Characteristics
Handling Guidelines
Environmental Guidelines
Cable Assembly
Glossary of Terms
Index
Chapter 1 Introduction
Overview Equipment/Material Needed
This chapter should briefly How to Get Help
introduce the user to the Related Documents
maintenance and Using Toolbox Help for Reference and
troubleshooting procedures Troubleshooting
and to provide quick
sources to additional
reference material.
Chapter 2 Introduction
Preventative Maintenance Maintenance Schedule
This chapter should be a Maintenance Record
tutorial maintenance Maintenance Procedures
schedules, maintenance Short-Circuit Damage
records and proper
procedures.
Chapter 3 Introduction
Parts Replacement Safety Precautions and Replacement Guidelines
This chapter should be an Control /module
introduction to safety Standard and Optional Modules
guidelines and proper
methods of parts
replacement.
Chapter 4 Introduction
Troubleshooting General Troubleshooting
This chapter should be a Specific Fault Troubleshooting
guide to proper ACLx Specific Errors
troubleshooting methods
ranging from general to
specific procedures.
Chapter 5 Introduction
Hardware and Verifications Preliminary Checks
Checks Toolbox Downloads
This standard chapter Bridge Output and Operation checks
should be the same for all
controls. Its purpose is to
tell the user how to identify
and order a part.
Glossary of Terms
Index
Chapter 1 Introduction
Overview Related Documents
This chapter should briefly How To Get Help
introduce the user to the Acronyms and Abbreviations
control and its features,
define the manual, and
provide quick important
reference information (such
as how to get help and
useful acronyms and
abbreviations).
Chapter 2 Introduction
System Architecture System Components
This chapter should be a Levels of Redundancy
tutorial on how the control Control and Protection Features
functions. It should provide Turbine Protection
basic information to help a Reliability and Availability
user understand system Third Party Connectivity
components, controls and
protection features,
reliability and third party
connections.
Chapter 3 Introduction
Networks Network Overview
This chapter focuses on Data Highways
network communications IONet
and the various types Ethernet Global Data
communication systems. Modbus Communications
Ethernet Serial Slave
Serial Modbus Slave
Ethernet GSM
PROFIBUS Communications
Fiber-Optic Cables
Time Synchronization
Chapter 4 Introduction
Codes, Standards and Safety Standards
Environment Electrical
Environment
Introduction
Chapter 5 Installation Support
Installation and Equipment Receiving and Handling
Configuration Weight and Dimensions
Power Requirements
Installation Support Drawings
Grounding
Cable Separation and Routing
Cable Specifications
Connecting the System
Startup Checks
Startup and Configuration
Chapter 7 Introduction
Maintenance, Diagnostic, Maintenance
and Troubleshooting Component Replacement
Alarms Overview
Process Alarms
Diagnostic Alarms
Totalizers
Troubleshooting
Chapter 8 Introduction
Applications Generator Synchronization
Overspeed Protection Logic
Power Unload Unbalance
Early Valve Actuation
Fast Overspeed Trip in VTUR
Compressor Stall Detection
Ground Fault Detection Sensitivity
Glossary of Terms
Index
This document defines all the boards/packs within a system. This information is
also defined in individual GEI documents, as described below
Functional Description
This section defines the board/pack functions. This document should provide basic
information to help the user operate, maintain and troubleshoot. It is not intended as
an engineering document with formulas and technical details.
Installation
This section gives a brief description of the installation of the pack or board. There is
usually a basic diagram of the board/pack and supporting figures showing
connectivity in the system.
Operation
This section deals primarily with the basic operation of the board/pack.
Specifications
This section list specifications specific to the board/pack the document is describing.
Diagnostics
This section lists specific diagnostic procedures for the board/pack.
Configuration
This section provides connectivity instructions.
Alarms
This section covers generic as well as specific alarms for the board/pack covered in
the document
Renewal/Warranty
This section provides warranty information on the board/pack described in the
document.
Replacement
This section describes the handling and replacement procedures for the board/pack
described in the document.
Part 1
Part 2
Chapter 8 Working Online with a Mark VIe
Chapter 9 General
Chapter 10 Hardware
Chapter 11 Software
Chapter 12 Dynamic Data Recorder (DDR)
Chapter 13 Ethernet Global Data
Chapter 14 Modbus Slave
Chapter 15 Mark VIe Tools
Chapter 16 Reference
Glossary of Terms
Index
Introduction
Every official GE document requires a documentation number that identifies it. The
document also requires revision identification by the publication number and issue
date. This chapter defines the documentation number scheme, including revisions.
To obtain a number contact the Documentation leader
Salem document numbers are assigned as follows:
• For external (customer) documents use GEHs, GEIs, GEJs, GEKs and GEUs
• For internal documents use GIIs or GIZs
GEH-0000A(F)
Language
Revision
Unique number
Document type
E = external I = Internal
General Electric Company
Identifying Supplements
Supplements are pages with corrections or additional information for an existing
document, which are included in the document as an insert. They must be identified
as such. For example, Supplement to GEH-5834 identifies the first supplement for
GEH-5834. Supplement no. 2 to GEH-5834 identifies the second supplement for
GEH-5834. Supplement 1A to GEH-5834 identifies the first revision to the first
supplement, identified above.
Introduction
The .pdf document cannot be The purpose of creating a .pdf file is to produce an easily navigated online document
edited. It can be printed by that is identical in appearance to the paper copy. Minimum software requirements
page or the entire document. include:
• Microsoft Word 2000
• Adobe® Acrobat® 5.0
• HP LaserJet 5 printer with PostScript capability
These procedures are described in detail in the following sections.
Section Page
Introduction ................................................................................................................. 1
Adobe Acrobat 5.0 Settings......................................................................................... 2
General Tab .......................................................................................................... 3
Compression Tab.................................................................................................. 3
Fonts Tab.............................................................................................................. 4
Color Tab ............................................................................................................. 4
Saving Settings..................................................................................................... 5
Printer Settings ............................................................................................................ 6
PDFMaker Settings ..................................................................................................... 7
Creating the .pdf Document ........................................................................................ 9
Manually Creating the .pdf Document ................................................................. 9
Making the .pdf Document User-Friendly................................................................. 10
Notes.......................................................................................................................... 12
GIZ-5006B Documentation Guide Appendix B Creating an Adobe Acrobat (.pdf) File • B-1
Adobe Acrobat 5.0 Settings
Open Acrobat Distiller by selecting Start, Programs, Acrobat Distiller 5.0.
B-2 • Appendix B Creating an Adobe Acrobat (.pdf) File GIZ-5006B Style and Content
General Tab
Compression Tab
GIZ-5006B Documentation Guide Appendix B Creating an Adobe Acrobat (.pdf) File • B-3
Fonts Tab
Color Tab
B-4 • Appendix B Creating an Adobe Acrobat (.pdf) File GIZ-5006B Style and Content
Saving Settings
Before closing the Job Options dialog box, you must save the previously set tab
settings as follows:
1. From any tab, select Save As. The Save Job Options As dialog box displays.
Select ScreenOptimized.joboptions
and select the Save button.
GIZ-5006B Documentation Guide Appendix B Creating an Adobe Acrobat (.pdf) File • B-5
Printer Settings
Change the Distiller Printer Document properties so that the graphic resolution is
300 dpi. You can access the Document Properties dialog box from either the PC
Start menu or from within your Word document.
B-6 • Appendix B Creating an Adobe Acrobat (.pdf) File GIZ-5006B Style and Content
PDFMaker Settings
From your Word document menu bar, select the PDFMaker icon . Select the
following tab options:
GIZ-5006B Documentation Guide Appendix B Creating an Adobe Acrobat (.pdf) File • B-7
When all
settings are
complete,
select Create
to create your
.pdf file.
B-8 • Appendix B Creating an Adobe Acrobat (.pdf) File GIZ-5006B Style and Content
Creating the .pdf Document
To create a pdf file
1. With the .doc file open, from the File menu, select Print Preview or click .
Check the entire document format for correct pagination, word wrapping, and
graphic placement. Make any final format adjustments.
In a multiple file document (where there is a master and other files), all .doc files
must also create a .pdf file using Adobe Acrobat. After all individual pdf files are
created, you must combine them into a single .pdf file.
To create a .pdf file from multiple .pdf files
1. With one of the .pdf files open in Adobe Acrobat, select the Document menu
and Insert Pages.
2. Select the .pdf file to insert and follow the instructions on the dialog boxes as to
where to insert it within the document.
3. Save the document to a new name and continue to add all pdf files.
Note Refer to the Adobe Acrobat documentation or online help for instructions on
adding, deleting, and replacing pages.
Tip It is more manageable 1. With your .doc file open, from the File menu, select Print Preview or click.
to have a separate directory, Check the entire document format for correct pagination, word wrapping, and
such as GEH-xxxx .pdf to graphic placement. Make any final format adjustments.
create and manage your pdf 2. From the File menu, select Print. The File Print dialog box displays.
files.
3. From this Print dialog box, select Distiller Assistant from the drop-down
list box as your printer name.
4. Click OK to print the .doc to a .pdf file.
Note Refer to the Adobe Exchange documentation or online help for instructions on
adding, deleting, and replacing pages.
GIZ-5006B Documentation Guide Appendix B Creating an Adobe Acrobat (.pdf) File • B-9
What to Bookmark
For additional reference, Technical documents include chapter and section headings to assist the reader in
refer to Adobe Acrobat finding specific content. Use the following list for determining what to bookmark:
online help.
• Safety Symbol Legend page
• Contents
• Heading 1 (chapter and appendix headings)
• Heading 2 and Heading 3 (section headings)
• Glossary of Terms
Remember the following rules and refer to the Acrobat Exchange documentation or
online help for instructions:
• Nest Heading 2 and 3 bookmarks by indenting subheadings under their main
heading
• Exchange places a right arrow next to a heading that has hidden subheadings,
and a down arrow next to a heading when the subheadings are displayed
• Based on the writer’s judgment, bookmark any tables, graphics, or other parts of
the document that may be especially important to a reader.
• When bookmarks are complete, hide all subheadings so that only the main
headings are displayed when the .pdf file is opened.
B-10 • Appendix B Creating an Adobe Acrobat (.pdf) File GIZ-5006B Style and Content
When you have multiple .doc files (for example, different chapters), create multiple
.pdf files and then combine the pdfs using Adobe Acrobat. (Refer to the Adobe
Acobat help file.)
To set the view options
1. Go to the first page of your document.
2. Select the File menu, Document Properties and Document Open
Options.
3. Select the following options.
GIZ-5006B Documentation Guide Appendix B Creating an Adobe Acrobat (.pdf) File • B-11
Notes
B-12 • Appendix B Creating an Adobe Acrobat (.pdf) File GIZ-5006B Style and Content
Index
D
Dashes, 2-5
Dialog box
callouts, 3-10
A conventions, 3-12
Abbreviations document
accronyms, 2-7 organization, 1-2
Abbreviations, 2-8 Document
Active voice, 2-3 board outline, 4-9
Apostrophes, 2-4 foreign language editions, A-3
identification, 4-2
Installation and Startup, 4-7
B
number, 4-2
Board document outline, 4-9 organization, 4-2
Bookmarks, B-10 prefix, A-2
Breaks small, 4-3
page, 3-6 structure, 4-2
suffix, A-3
C supplements, A-3
tables, 3-10
Callouts, 3-10 User's Guide, A-2
Cautions, 3-15 Documenting
Chapter Software, 3-4
numbering, 3-8 Drawing
Commas, 2-5 callouts, 3-10
Compound words, 2-15
Conventions, 3-4
F
Cover, 3-5
Create Footers, 3-15
callouts, 3-10, 3-11 Foreign Language Editions, A-3
cover, 3-5 Format, 2-2, 3-1, 3-4
footers, 3-15 styles, 3-3
headings, 3-3 Functional documents, 1-1
lists, 3-9
margin notes, 3-10
pdf document, B-9 G
pdf manually, B-9
steps, 3-9 GEH
table of contents, 3-7 numbering, A-1
thumbnails, B-10 GEI
user-friendly pdf, B-10 numbering, A-1
Grammar, 2-3
H
Headings, 3-3
Hypens, 2-5