CCV18

RS3t
Console
Configuration
Manual
Software Version 18, Release 2
August 1994
U.S. Manual PN: 1984-2643-1801
A-4 Size Manual PN: 1984-2643-1811
1984-2643-5006
1984-2643-5016
E 1987--1999 Fisher-Rosemount Systems, Inc.
All rights reserved.
Printed in the U.S.A.
Components of the RS3 distributed process control system may be protected by U.S. patent Nos. 4,243,931; 4,370,257; 4,581,734. Other
Patents Pending.
RS3 is a mark of one of the Fisher-Rosemount group of companies. All other marks are property of their respective owners. The contents
of this publication are presented for informational purposes only, and while every effort has been made to ensure their accuracy, they are
not to be construed as warranties or guarantees, express or implied, regarding the products or services described herein or their use or
applicability. We reserve the right to modify or improve the designs or specifications of such products without notice.
Fisher-Rosemount Systems, Inc.

8301 Cameron Road
Austin, Texas 78754--3895 U.S.A.
Telephone: (512) 835--2190

FAX: (512) 834--7313
Comment Form
RS3t Manuals
Console Configuration Manual 1984-2643-18x1
Please give us your feedback to help improve this manual.

Never Rarely Sometimes Usually Always
1. Do you actually use this manual when
you are:
D configuring ______ ______ ______ ______ ______
D making changes or enhancements ______ ______ ______ ______ ______
D operating the system ______ ______ ______ ______ ______
D troubleshooting ______ ______ ______ ______ ______
D other __________________________ ______ ______ ______ ______ ______
2. Does this manual answer your questions? ______ ______ ______ ______ ______
3. What could be changed in this manual to make it more useful?
Errors and Problems: Please note errors or problems in this manual, including chapter and page number,
if applicable; or send a marked-up copy of the affected page(s).
May we contact you about your comments? j Yes j No
Name ______________________________________________
Company ______________________________________________
Phone ______________________________________________
Date ______________________________________________
Fisher-Rosemount FAX #: (512) 834--7200 Thank you!
Name
Place
Company stamp
here
Address

Technical Documentation
8301 Cameron Road
Austin, Texas 78754--3895
U.S.A.
Seal with tape.

CC: v
RS3t
Console Configuration Manual
About This Manual
This manual describes the operations performed at the RS3 console.

The manual is divided into seven chapters:
D Chapter 1 Configuring operating characteristics of the RS3

console, including the Console Configuration
screen, node and plant ownership, and keyboard
control switching.
D Chapter 2 Describes the operating characteristics of the
process graphics system, including color
configuration, creating shapes, and combining
and editing objects.
D Chapter 3 Operation and configuration of reports, which feed
back vital process variable information to the
screen or to a printout.
D Chapter 4 Information about trending data from a process,
including storing, organizing, and accessing that
data.
D Chapter 5 A comprehensive table of the commands used on
the RS3 command line, including commands that
perform operations, and commands that call up
screens.
D Chapter 6 Management of alarms generated by the RS3,
including alarm types, alarm display, alarm
acknowledgment, separation and storing of
alarms, alarm history, and alarm animation.
D Chapter 7 Password Security for the RS3. Contains logging
functions, as well as password system
configuration and troubleshooting.
RS3: Console Configuration Manual About This Manual

CC: vi
Changes for This Release
D Added information on the Menu Command Console Screen

( CC:1-1-2)
D Changed functionality of Join/Split commands ( CC:2-2-60)
D Added information on the Link Editor Field ( CC:2-3-10)
D Added information on the Link Count Field ( CC:2-3-3)
D Updated information on Trending capabilities (CC:4, Section 1)
D The pagination and format of this book have changed in order to
match the DOCVUE documentation library, a CD--ROM version
of the RS3 manual set.
Version 18 Release 1 also added:

D A new chapter on Password Security (Chapter 7)
D Information on the Graphic Link Editor ( CC:2-3-9)
D Additional details to explain trending update algorithms
( CC:4-3-9).
Revision Level for This Manual
For This Refer to This Document:

Software
Version: Title Date Part Number
18R2 Console Configuration Manual August 1994 1984-2643-18x1
18R1 Console Configuration Manual October 1993 1984-2643-18x1
17 Console Configuration Manual August 1992 1984-2643-17x1
16 Console Configuration Manual January 1992 1984-2643-16x1
15 Console Configuration Manual January 1991 1984-2643-15x1

CC: vii
References to Other Manuals
References to other RS3 user manuals list the manual, chapter, and
sometimes the section as shown below.
Sample Entries:
For ..., see CC: 3. For ..., see CC: 1-1.
Manual Title Chapter Manual Title Chapter-Section
Abbreviations of Manual Titles

AL = Alarm Messages
BA= ABC Batch
CB= ControlBlock Configuration
CC= Console Configuration
DT = Disk and Tape Functions
IO = I/O Block Configuration
OP= Operator’s Guide
OV= System Overview and Glossary
PW= PeerWay Interfaces
RB= Rosemount Basic Language
RI = RNI Release Notes and Installation Guide
RP = RNI Programmer’s Reference Manual
SP = Site Preparation and Installation
SR = System Resource Unit (SRU)
SV = Service

CC: viii
Reference Documents
Prerequisite Documents
You should be familiar with the information in the following documents

before using this manual:
System Overview Manual and Glossary 1984-2640-18x1
Software Release Notes, Version 18 1984-2818-01xx
Related Documents
You may find the following documents helpful when using this manual:
ABC Batch Software Manual 1984-2654-18x1
Alarm Messages Manual 1984-2657-18x1
ABC Batch Quick Reference Guide 1984-2814-11xx
Configuration Quick Reference Guide 1984-2812-08xx
Console Configuration Manual 1984-2643-18x1
ControlBlock Configuration Manual 1984-2646-18x1
I/O Block Configuration Manual 1984-2645-18x1
Operator’s Guide 1984-2647-18x1
PeerWay Interfaces Manual 1984-2650-18x1
Rosemount Basic Language Manual 1984-2653-18x1
RNI Programmer’s Reference Manual 1984-3356-01x1
RNI Release Notes and Installation Guide 1984-3357-01x1
Service Manual, Volume 1 1984-2648-18x1
Service Manual, Volume 2 1984-2648-18x2
Site Preparation and Installation Manual 1984-2642-xxx1
Software Defects for Version 18 1984-2818-03xx
System Resource Unit (SRU) Manual 1984-2651-18x1
User Manual Master Index 1984-2641-18x1

Contents
Chapter 1: Configuring Operating Characteristics
Section 1: Configuring Console Operations . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1-1

The Menu Command Console Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1-2
Configuring the Command Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1-3
Console Configuration Screen Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1-5
Configuring Access to an Alternate Console Disk over the PeerWay . . . . . . . 1-1-12
Configuring Consoles to Switch Keyboard Control . . . . . . . . . . . . . . . . . . . . . . 1-1-14
Configuring 16--Character Block Tags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1-15
Tags Affected . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1-15
Splitting and Masking Tags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1-15
Taking Advantage of Masking and Splitting Options . . . . . . . . . . . . . . . . . . . . . 1-1-16
Split Tags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1-17
Where Tags Are Automatically Split . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1-17
Specifying Where to Split Tags—Tag Row Break . . . . . . . . . . . . . . . . . . . . . 1-1-18
Masking Tags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1-19
Where Masking Does Not Apply . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1-19
Specifying a Mask . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1-20
Turning Masking On and Off . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1-21
How Tag Splitting and Masking Interact . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1-22
Node Ownership and Plant Unit Ownership . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1-23
Configuring Node Ownership . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1-24
Configuring Plant Unit Ownership . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1-25
Operator Change Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1-26
Hints for Configuring Console Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1-28
Configuration Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1-28
Configuration Tips . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1-29
Configuring Refresh and Advance Request Rates . . . . . . . . . . . . . . . . . . . . . . . 1-1-30
Screen Refresh Rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1-31
Field Refresh Rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1-32
Section 2: Configuring Color . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2-1

Master Color Selection Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2-2
Color Configuration Screens . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2-3
Hints for Configuring Colors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2-8
RS3: Console Configuration Manual Contents

CC: x
Section 3: Configuring Operating Displays . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3-1

Configuring Group Displays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3-2
Group Directory Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3-2
Group Display Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3-3
Configuring Unit Displays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3-5
Unit Directory Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3-5
Unit Display Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3-6
Configuring Overview Displays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3-7
Overview Directory Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3-7
Overview Display Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3-8
Section 4: Configuring Callup and Display Buttons . . . . . . . . . . . . . . . . . . . 1-4-1

Configuring Callup Buttons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4-2
Configuring a Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4-3
Configuring a Callup Button Number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4-4
Configuring Alarm Annunciation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4-5
Callup Buttons Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4-7
Display Buttons Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4-8
Hints for Callup Buttons and Display Buttons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4-9
Section 5: Configuring Message Pairs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5-1

Standard and User Message Pairs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5-2
The Message Pairs Screens . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5-3
Hints for Using Message Pairs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5-9
Section 6: Configuring the Block Print Function . . . . . . . . . . . . . . . . . . . . . . 1-6-1
Section 7: Multinational Characters and Russian Console . . . . . . . . . . . . . 1-7-1

Multinational Characters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7-1
Russian Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7-1
Chapter 2: Process Graphics
Section 1: Introduction to Process Graphics . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1-1

How are Process Graphics Stored? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1-2
How are Process Graphics Created and Accessed? . . . . . . . . . . . . . . . . . . . . . . . 2-1-3
Creating a Process Graphic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1-4
Calling Up the Viewing Mode of a Process Graphic . . . . . . . . . . . . . . . . . . . . . 2-1-4
Calling Up the Configuration Mode of a Process Graphic . . . . . . . . . . . . . . . . . 2-1-6

CC: xi
Section 2: Process Graphics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-1

Creating Process Graphics Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-2
Object Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-5
How Objects Appear in Viewing and Configuration Modes . . . . . . . . . . . . . . . . . . 2-2-7
Creating Shapes
Circles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-9
Boxes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-10
Triangles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-11
Arcs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-12
Lines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-13
Lines with Different Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-14
Shape Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-15
Library Symbols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-17
New Symbols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-19
Shapes that Fill Up in Response to a Block Variable . . . . . . . . . . . . . . . . . . . . . 2-2-21
Multicolor Shapes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-23
Creating Objects That Display Block Information:
Tag, Blkdes, Mode Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-25
Creating Objects That Display Block Variable Information in
Character Form: Links, Units, Disc Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-28
Graphic Form: Hdev, Vdev, Ticbar Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-31
How the Hdev and Vdev Objects Are Displayed . . . . . . . . . . . . . . . . . . . . . . . . 2-2-33
How the Ticbar Object is Displayed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-35
Creating Objects That Display Faceplates:
Group, Unit, Overview Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-37
Displaying a Faceplate from a Process Graphic Object . . . . . . . . . . . . . . . . . . . . . 2-2-40
Creating Objects That Display Trend Information: Trend Object . . . . . . . . . . . . . 2-2-41
How the Trend Object is Displayed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-44
Creating Displayed Text: Text Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-46
Displaying Alarms: Alarm Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-48
Creating Data Entry Fields: Disc Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-53
Configuring The Appearance of Objects to Change, Depending on the
State of a Discrete Block Variable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-54
Configuration Tools
Moving and Copying Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-56
Deleting Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-57
Stacking Objects—Top and Bottom Operations . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-58
Example of Stacking Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-59
Grouping Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-60
Grouping Objects—Area Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-61
Grouping Objects—Group and Join Operations . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-63
Joining Single Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-63
Joining Groups of Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-64
Grouping Objects—Merge Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-66
Using the Link Editor Field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-67
Splitting an Object from a Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-69
Undoing the Previous Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-70

CC: xii
Configuring Display Characteristics

Process Graphics Fabric Coordinates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-71
Changing the Panning Limits and Origin Point . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-72
Creating Assists for Display Manipulation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-73
Objects that Call up Other Displays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-74
Objects that Call up Another Part of the Same Display . . . . . . . . . . . . . . . . . . 2-2-75
Display Targets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-77
Hiding Parts of the Display Using an Icon Object . . . . . . . . . . . . . . . . . . . . . . . . 2-2-79
Copying a Process Graphic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-82
Creating Objects That Display Batch Task Data:
Bface Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-83
Alarm Annunciation on Graphics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-85
Alarm Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-85
Icon Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-85
Configuring User--defined Characters
That Have Been Converted from Character Graphics . . . . . . . . . . . . . . . . . . . . . . 2-2-86
Section 3: Optimizing Graphics Performance . . . . . . . . . . . . . . . . . . . . . . . . . 2-3-1

Process Graphic Limits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3-2
Link Count Field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3-3
Using Funnel Blocks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3-4
Merging Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3-5
Other Methods of Optimizing Graphics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3-6
Preconfigured Process Graphics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3-7
Screen Refresh and Field Refresh . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3-8
Graphics Link Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3-9
Calling Up the Link Editor Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3-10
Procedure: Editing Link Addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3-11
Chapter 3: Reports
Section 1: Introduction to Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1-1
Section 2: The Report File Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2-1

The Report Read Directory Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2-3
The Report File Contents Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2-4
The Report Read/Scan Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2-5
The Report Config Directory Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2-6
The Report Status Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2-8
Section 3: Designing a Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3-1

Assembling Information for a Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3-1
Dimensions of a Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3-2
Formatting the Report for Printing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3-3

CC: xiii
Section 4: Configuring a Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4-1

The Report Configuration Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4-2
Report Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4-5
Using Report Objects to Configure Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4-8
Editing the Body of a Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4-9
Configuring How a Report is Printed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4-10
How to Determine Report Print Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . 3-4-10
How to Begin a New Report Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4-11
Configuring Text in a Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4-12
How to Print Regular--sized Text . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4-12
How to Print Oversized Text . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4-13
Configuring Operator Comments in a Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4-14
Configuring Block Information in a Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4-15
How to Configure a Block Tag . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4-15
How to Configure a Block Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4-16
How to Configure a Block Descriptor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4-17
How to Configure a Block Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4-18
How to Configure a Block Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4-19
How to Configure Block Units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4-20
How to Configure Block Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4-21
How to Perform Calculations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4-22
How to Configure Trend File Information in a Report . . . . . . . . . . . . . . . . . . . . . . . 3-4-26
How to Use an Accumulator with a Trend Log Object . . . . . . . . . . . . . . . . . . . . 3-4-31
Configuring Time and Date Information in a Report . . . . . . . . . . . . . . . . . . . . . . . . 3-4-32
How to Configure the Current Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4-32
How to Configure the Current Date . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4-33
Configuring Console Lists in a Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4-34
Configuring the List Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4-35
Formatting a List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4-35
How to Configure Another Report in a Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4-37
Generating Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4-39
How to Generate a Report Based on Time and Date . . . . . . . . . . . . . . . . . . . . 3-4-39
How to Generate a Report Based on Alarms or Events . . . . . . . . . . . . . . . . . . 3-4-41
How to Generate a Report from the Report Configuration Screen . . . . . . . . . 3-4-42
How to Print a Report When it is Generated . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4-43
Section 5: Saving a Report to Disk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5-1
Section 6: Hints for Configuring and Using Reports . . . . . . . . . . . . . . . . . . . 3-6-1

Configuration Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6-2
Marking Lines in Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6-3

CC: xiv
Chapter 4: Trending
Section 1: Trending Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1-1

Console Trending Capabilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1-2
Multitube Command Consoles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1-3
How Trend File Information is Stored . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1-4
What Block Variables Can be Trended . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1-5
Using Trending Screens . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1-5
Enabling and Disabling Trending . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1-6
Trending Condition upon Console Restart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1-6
Section 2: Configuring Trend Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2-1

The Trend File Setup Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2-2
Configuring a Trend File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2-5
Determining When and How Often Data is Stored
(Frequency and Duration Fields) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2-7
Section 3: Configuring Trend Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3-1

The Trend Group Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3-1
Trend Group Displays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3-5
Using the Slidewire . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3-6
Trend Group Scaling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3-7
Viewing Trend Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3-8
How Often Trend Group Displays Update . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3-9
Section 4: Archive Trend Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4-1

How a Backup Trend File is Saved . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4-2
Restoring and Reading Trend Archive Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4-3
Restoring and Reading Trend Archive Data from Tape . . . . . . . . . . . . . . . . . . . 4-4-3
Section 5: Hints for Configuring Trending . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5-1

Copying Trend Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5-1
Determining Trend Group Update Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5-1
Chapter 5: Commands
Section 1: Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1-1

Symbols Used . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1-2
Section 2: Hints for Using Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2-1

CC: xv
Chapter 6: Alarm Management
Section 1: Managing the Number of Alarm Messages on the PeerWay . . 6-1-1

Configuring Which Nodes Are Sent Alarms from a ControlFile,
Console, or SRU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1-2
Using CAB to Reduce Message Load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1-4
Inhibiting Alarms from Generating on the PeerWay . . . . . . . . . . . . . . . . . . . . . . . . 6-1-7
Using ControlBlock Logic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1-7
Using the ControlFile Status Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1-7
Effects of Inhibiting Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1-7
Section 2: How Alarms Get Stored in Console RAM . . . . . . . . . . . . . . . . . . . 6-2-1
Section 3: Separating and Sorting Alarms at a Console . . . . . . . . . . . . . . . . 6-3-1

Alarm Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3-2
Alarm Areas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3-3
Disabling and Enabling an Alarm Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3-5
Disabling an Alarm Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3-5
Enabling an Alarm Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3-5
Alarm Suppression . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3-6
Suppressing an Alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3-7
Unsuppressing an Alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3-7
Configuring Alarm List and Event List Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3-8
The Alarm List Configuration Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3-8
RS3 Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3-11
User-defined Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3-12
Configuring the Event List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3-13
Section 4: Alarm History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-4-1

Configuring Log Display Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-4-2
Displaying Information from the Alarm Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-4-6
Disabling and Enabling the Alarm Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-4-9
Section 5: Configuration and Display Topics . . . . . . . . . . . . . . . . . . . . . . . . . . 6-5-1

Alarm Configuration Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-5-2
Alarm Configuration Screen—Automatic Alarm Deletion . . . . . . . . . . . . . . . . . 6-5-7
Alarm Regeneration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-5-10
Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-5-10
When Do Alarms Regenerate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-5-10
How Consoles Regenerate Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-5-10
Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-5-10
Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-5-10
Alarm Priority . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-5-11
Alarm Type Priority . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-5-11
Alarm Priority Numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-5-11

CC: xvi
Alarm Display Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-5-12

Alarm Banner Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-5-12
Alarm Summary Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-5-12
Determining the Alarm Display Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-5-13
Section 6: Alarm Animation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-6-1

Tags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-6-3
Tags on Trend Group Displays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-6-14
Block Variable Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-6-15
Plant Units and Area Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-6-26
Graphic Alarm Objects and Icon Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-6-37
Alarm Message Source Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-6-48
Section 7: Hints for Alarm Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-7-1

Configuration Tips . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-7-1
Chapter 7: Password Security
Section 1: Version 18 Changes to Current System . . . . . . . . . . . . . . . . . . . . . 7-1-1

Changes to Current System Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1-2
New Access Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1-4
Changes to Console Configuration Screen—Page 1 . . . . . . . . . . . . . . . . . . . . . 7-1-4
Changes to Disk and Tape Activities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1-5
Modifications to Operator Change Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1-6
Section 2: Accessing a Password Secure System . . . . . . . . . . . . . . . . . . . . . 7-2-1

Logging on to the System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2-2
Changing a Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2-4
Logging Off the Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2-6
Section 3: Configuring Password Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3-1

Initial Password System Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3-1
Configuring Factory-shipped Password System . . . . . . . . . . . . . . . . . . . . . . . . . 7-3-2
Logging in and Configuring Primary and Backup Nodes . . . . . . . . . . . . . . . 7-3-3
Changing User and Login Names and Completing Configuration . . . . . . . 7-3-4
Defining Password Security with a Configuror’s Key . . . . . . . . . . . . . . . . . . . . 7-3-5
Configuring Primary and Backup Nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3-5
Adding a System Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3-6
Logging In . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3-7
System-wide Password Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3-8
Defining System-wide Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3-10
Saving the Console Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3-11
User Profile Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3-12

CC: xvii
Plant Unit Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3-14

Plant Unit Access and Plant Unit Configuration . . . . . . . . . . . . . . . . . . . . . . . . . 7-3-15
Defining Plant Unit Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3-16
Changing Plant Unit Access Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3-18
User Name Detail Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3-19
Adding Users to the Password System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3-22
Changing User Name Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3-23
Changing a Configuror to a System Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3-24
Section 4: Password Security Hints and Troubleshooting . . . . . . . . . . . . . 7-4-1

Scenario 1: Handling Primary and Backup Nodes . . . . . . . . . . . . . . . . . . . . . . . . . 7-4-2
Scenario 2: Using Passwords with Keylock and Secure Interfaces . . . . . . . . . . . 7-4-3
Scenario 3: Using Passwords with a Standard KBI . . . . . . . . . . . . . . . . . . . . . . . . 7-4-4
Scenario 4: Using Key and Password Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-4-5
Scenario 5: Loss of $$PASSWD File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-4-6
Scenario 6: Console Configuration File Not Found . . . . . . . . . . . . . . . . . . . . . . . . 7-4-7

CC: xviii
List of Figures
Figure 1.1.1. Menu Command Console Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CC:1-1-2

Figure 1.1.2. Command Console Configuration Screen—Page 1 . . . . . . . . . . . . . . . . . . . . . . . . . . CC:1-1-3
Figure 1.1.3. Command Console Configuration Screen—Page 2 . . . . . . . . . . . . . . . . . . . . . . . . . . CC:1-1-4
Figure 1.1.4. Console Configuration Screen—Page 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CC:1-1-4
Figure 1.1.5. Access to Alternate Console Disk over the PeerWay . . . . . . . . . . . . . . . . . . . . . . . . . CC:1-1-13
Figure 1.1.6. Console Configuration Screen Switch Keyboard Examples . . . . . . . . . . . . . . . . . . . CC:1-1-14
Figure 1.1.7. Examples of Split Tags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CC:1-1-17
Figure 1.1.8. Splitting Character Tags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CC:1-1-18
Figure 1.1.9. Masking Character Tags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CC:1-1-20
Figure 1.1.10. Interaction of Tag Splitting and Masking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CC:1-1-22
Figure 1.1.11. Plant Status Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CC:1-1-24
Figure 1.1.12. Plant Unit Configuration Field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CC:1-1-25
Figure 1.1.13. Operator Change Log Screen Entries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CC:1-1-27
Figure 1.1.14. Advance Request Concept . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CC:1-1-34
Figure 1.2.1. Master Color Selection Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CC:1-2-2
Figure 1.2.2. Color Configuration Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CC:1-2-3
Figure 1.3.1. Group Directory Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CC:1-3-2
Figure 1.3.2. Group Display Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CC:1-3-3
Figure 1.3.3. Unit Directory Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CC:1-3-5
Figure 1.3.4. Unit Display Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CC:1-3-6
Figure 1.3.5. Overview Directory Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CC:1-3-7
Figure 1.3.6. Overview Display Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CC:1-3-8
Figure 1.4.1. Multitube Callup and Display Buttons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CC:1-4-1
Figure 1.4.2. Alarm Annunciation Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CC:1-4-2
Figure 1.4.3. Option Keyboard Callup Button Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CC:1-4-4
Figure 1.4.4. Alarm Annunciation Screen Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CC:1-4-6
Figure 1.4.5. Callup Buttons Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CC:1-4-7
Figure 1.4.6. Display Buttons Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CC:1-4-8
Figure 1.5.1. Faceplates and Message Pairs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CC:1-5-1
Figure 1.5.2. Standard Message Pairs Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CC:1-5-4
Figure 1.5.3. User Message Pairs Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CC:1-5-5
Figure 1.6.1. Block Print Setup Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CC:1-6-2
Figure 2.1.1. Example of a Process Graphic Display Fabric . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CC:2-1-1

CC: xix
Figure 2.1.2. Process Graphics Folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CC:2-1-2

Figure 2.1.3. Using [EXCH] to Move Between Viewing and Configuration Modes . . . . . . . . . . . . CC:2-1-3
Figure 2.2.1. Creating a Process Graphics Object—Top Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . CC:2-2-2
Figure 2.2.2. Creating a Process Graphics Object—Object Menu . . . . . . . . . . . . . . . . . . . . . . . . . . CC:2-2-3
Figure 2.2.3. Creating a Process Graphics Object—Edit Object Menu . . . . . . . . . . . . . . . . . . . . . . CC:2-2-4
Figure 2.2.4. Viewing Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CC:2-2-7
Figure 2.2.5. Configuration Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CC:2-2-8
Figure 2.2.6. Creating a Circle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CC:2-2-9
Figure 2.2.7. Creating a Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CC:2-2-10
Figure 2.2.8. Creating a Triangle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CC:2-2-11
Figure 2.2.9. Creating an Arc . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CC:2-2-12
Figure 2.2.10. Creating a Line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CC:2-2-13
Figure 2.2.11. Edit Object Menu for the Line Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CC:2-2-14
Figure 2.2.12. Edit Object Menu for Shapes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CC:2-2-15
Figure 2.2.13. Adding a Library Symbol to a Process Graphic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CC:2-2-18
Figure 2.2.14. Creating a New Symbol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CC:2-2-20
Figure 2.2.15. Edit Object Menu for Creating a Shape that Fills Up in Response to a
Block Variable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CC:2-2-22
Figure 2.2.16. Examples of the Ways that Shapes Can Be Used . . . . . . . . . . . . . . . . . . . . . . . . . . CC:2-2-22
Figure 2.2.17. Multicolor Shape and Edit Object Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CC:2-2-23
Figure 2.2.18. Example of a Multicolor Shape with Edit Links Menu . . . . . . . . . . . . . . . . . . . . . . . . CC:2-2-24
Figure 2.2.19. How the Tag, Blkdes, and Mode Objects Appear in Configuration Mode . . . . . . . CC:2-2-26
Figure 2.2.20. Edit Object Menu for the Tag, Blkdes, and Mode Objects . . . . . . . . . . . . . . . . . . . . CC:2-2-27
Figure 2.2.21. How the Link, Units, and Disc Objects Appear In Configuration Mode . . . . . . . . . CC:2-2-29
Figure 2.2.22. Edit Object Menu for the Link, Units, and Disc Objects . . . . . . . . . . . . . . . . . . . . . . CC:2-2-30
Figure 2.2.23. How the Hdev, Vdev, and Ticbar Objects Appear in Configuration Mode . . . . . . . CC:2-2-32
Figure 2.2.24. How the Hdev and Vdev Objects Appear in Viewing Mode . . . . . . . . . . . . . . . . . . . CC:2-2-33
Figure 2.2.25. Edit Object Menu for the Hdev, Vdev, and Ticbar Objects . . . . . . . . . . . . . . . . . . . . CC:2-2-34
Figure 2.2.26. How the Ticbar Object Appears in Viewing Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . CC:2-2-35
Figure 2.2.27. Edit Object Menu for the Hdev, Vdev, and Ticbar Objects . . . . . . . . . . . . . . . . . . . . CC:2-2-36
Figure 2.2.28. How the Group, Unit, and Overview Objects Appear in Configuration Mode . . . . CC:2-2-38
Figure 2.2.29. Edit Object Menu for the Group, Unit, and Overview Objects . . . . . . . . . . . . . . . . . CC:2-2-39
Figure 2.2.30. Displaying a ControlBlock Faceplate from a Process Graphic Object . . . . . . . . . . CC:2-2-40
Figure 2.2.31. How the Trend Object Appears in Configuration Mode . . . . . . . . . . . . . . . . . . . . . . CC:2-2-41
Figure 2.2.32. Edit Object Menu for the Trend Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CC:2-2-42
Figure 2.2.33. How the Trend Object is Displayed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CC:2-2-44
Figure 2.2.34. Slidewire Feature of the Trend Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CC:2-2-45
Figure 2.2.35. Edit Object Menu for the Text Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CC:2-2-46

CC: xx
Figure 2.2.36. How the Alarm Object is Displayed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CC:2-2-48

Figure 2.2.37. Example of Alarm Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CC:2-2-49
Figure 2.2.38. Examples of Criteria Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CC:2-2-52
Figure 2.2.39. Example Data Entry Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CC:2-2-53
Figure 2.2.40. Configuring the Edit Object Menu for Conditional Display of Objects . . . . . . . . . . CC:2-2-54
Figure 2.2.41. Moving and Copying an Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CC:2-2-56
Figure 2.2.42. Deleting an Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CC:2-2-57
Figure 2.2.43. Stacking Objects Using the Top and Bottom Operations . . . . . . . . . . . . . . . . . . . . . CC:2-2-58
Figure 2.2.44. Creating an Object Superimposed on Another Object . . . . . . . . . . . . . . . . . . . . . . . CC:2-2-59
Figure 2.2.45. Joining Objects into Groups with the Area Operation . . . . . . . . . . . . . . . . . . . . . . . . CC:2-2-62
Figure 2.2.46. Joining Single Objects into Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CC:2-2-63
Figure 2.2.47. Joining Groups of Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CC:2-2-64
Figure 2.2.48. Joining Groups of Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CC:2-2-65
Figure 2.2.49. Merging a Group into a Permanent Thing Object . . . . . . . . . . . . . . . . . . . . . . . . . . . CC:2-2-66
Figure 2.2.50. Using the LinkEd Option to Link an Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CC:2-2-67
Figure 2.2.51. Splitting an Object from a Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CC:2-2-69
Figure 2.2.52. Undoing an Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CC:2-2-70
Figure 2.2.53. Fabric Coordinates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CC:2-2-71
Figure 2.2.54. Changing a Panning Limit or the Origin Point . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CC:2-2-72
Figure 2.2.55. Edit Object Menu for Pagefrwd and Pageback Objects for Display Manipulation CC:2-2-74
Figure 2.2.56. Use of Anchor Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CC:2-2-75
Figure 2.2.57. Edit Object Menu for Anchor Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CC:2-2-76
Figure 2.2.58. Example Use of Anchor Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CC:2-2-76
Figure 2.2.59. Example Use of Target Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CC:2-2-77
Figure 2.2.60. Edit Object Menu for Target Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CC:2-2-78
Figure 2.2.61. How the Icon Object is Displayed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CC:2-2-80
Figure 2.2.62. Edit Object Menu for Icon Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CC:2-2-80
Figure 2.2.63. Copying a Process Graphic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CC:2-2-82
Figure 2.2.64. How the Bface Object Appears in Configuration Mode . . . . . . . . . . . . . . . . . . . . . . CC:2-2-83
Figure 2.2.65. Edit Object Menu for the Bface Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CC:2-2-84
Figure 2.2.66. Configure Character Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CC:2-2-87
Figure 2.3.1. Using the Link Count Field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CC:2-3-3
Figure 2.3.2. Funnel Block Concept . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CC:2-3-4
Figure 2.3.3. Link Editor Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CC:2-3-10
Figure 3.2.1. Report Folders and Report Screens . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CC:3-2-2
Figure 3.2.2. Report Read Directory Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CC:3-2-3
Figure 3.2.3. Report File Contents Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CC:3-2-4

CC: xxi
Figure 3.2.4. Report Read/Scan Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CC:3-2-5

Figure 3.2.5. Report Configuration Directory Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CC:3-2-7
Figure 3.2.6. Report Status Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CC:3-2-8
Figure 3.3.1. Report Sample Layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CC:3-3-1
Figure 3.3.2. Visible Report Screen Dimensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CC:3-3-2
Figure 3.3.3. Sizing a Report Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CC:3-3-3
Figure 3.4.1. Report Configuration Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CC:3-4-2
Figure 3.4.2. Report Configuration Screen with Report Configuration Window . . . . . . . . . . . . . . . CC:3-4-5
Figure 3.4.3. Report Configuration Window with Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CC:3-4-8
Figure 3.4.4. Report Configuration Screen with Print Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CC:3-4-10
Figure 3.4.5. Report Configuration Screen with Newpage Object . . . . . . . . . . . . . . . . . . . . . . . . . . CC:3-4-11
Figure 3.4.6. Report Configuration Screen with Text Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CC:3-4-12
Figure 3.4.7. Report Configuration Screen with Banner Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . CC:3-4-13
Figure 3.4.8. Report Configuration Screen with Comment Object . . . . . . . . . . . . . . . . . . . . . . . . . . CC:3-4-14
Figure 3.4.9. Report Configuration Screen with Tag Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CC:3-4-15
Figure 3.4.10. Report Configuration Screen with Address Object . . . . . . . . . . . . . . . . . . . . . . . . . . CC:3-4-16
Figure 3.4.11. Report Configuration Screen with Descriptor Object . . . . . . . . . . . . . . . . . . . . . . . . . CC:3-4-17
Figure 3.4.12. Report Configuration Screen with Function Object . . . . . . . . . . . . . . . . . . . . . . . . . . CC:3-4-18
Figure 3.4.13. Report Configuration Screen with Mode Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . CC:3-4-19
Figure 3.4.14. Report Configuration Screen with Unit Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CC:3-4-20
Figure 3.4.15. Report Configuration Screen with Value Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CC:3-4-21
Figure 3.4.16. Report Configuration Screen with Value and Accumulator Objects . . . . . . . . . . . . CC:3-4-23
Figure 3.4.17. Report Configuration Screen with Value Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . CC:3-4-24
Figure 3.4.18. Report Configuration Screen with Accumulator Object . . . . . . . . . . . . . . . . . . . . . . CC:3-4-25
Figure 3.4.19. Report Configuration Screen with Trend Log Object . . . . . . . . . . . . . . . . . . . . . . . . CC:3-4-26
Figure 3.4.20. Sample Trend Log Object Configuration Window and Resulting Report . . . . . . . . CC:3-4-27
Figure 3.4.21. Sample Trend Log Object Configuration Window and Resulting Report . . . . . . . . CC:3-4-28
Figure 3.4.22. Report Configuration Window with Trend Log Object and Accumulator . . . . . . . . CC:3-4-31
Figure 3.4.23. Report Configuration Screen with Time Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CC:3-4-32
Figure 3.4.24. Report Configuration Screen with Date Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CC:3-4-33
Figure 3.4.25. Report Configuration Screen with List Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CC:3-4-35
Figure 3.4.26. Report Configuration Screen with Generate Object . . . . . . . . . . . . . . . . . . . . . . . . . CC:3-4-37
Figure 3.4.27. Generating a Report Based on Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CC:3-4-39
Figure 3.4.28. Generating a Report Based on Date . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CC:3-4-40
Figure 3.4.29. Generating a Report Based on Alarms and Events . . . . . . . . . . . . . . . . . . . . . . . . . CC:3-4-41
Figure 3.4.30. Report Configuration Screen with Generate this Report Command . . . . . . . . . . . . CC:3-4-42
Figure 3.4.31. Report Configuration Screen with Auto Print Field . . . . . . . . . . . . . . . . . . . . . . . . . . CC:3-4-43

CC: xxii
Figure 4.1.1. Trend Group Screen Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CC:4-1-1

Figure 4.1.2. Example of Allocating Trend Files to Multitube Command Consoles . . . . . . . . . . . . CC:4-1-3
Figure 4.1.3. The Trending Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CC:4-1-4
Figure 4.2.1. Trend File Setup Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CC:4-2-2
Figure 4.2.2. Trend File Configuration Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CC:4-2-5
Figure 4.2.3. Trend File Configuration Screen with Frequency and Duration Fields . . . . . . . . . . . CC:4-2-7
Figure 4.3.1. Trend Group Configuration Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CC:4-3-2
Figure 4.3.2. Trend Group Screen with Slidewire . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CC:4-3-6
Figure 4.3.3. Trend Group Screen with Scaling Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CC:4-3-7
Figure 4.3.4. Trend Group Screen with Fields that Determine Data Points and Time . . . . . . . . . CC:4-3-8
Figure 4.3.5. Update Time Algorithm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CC:4-3-9
Figure 4.3.6. Update Time in Even Seconds . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CC:4-3-10
Figure 4.3.7. Update Time in Fractions of Seconds . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CC:4-3-10
Figure 4.4.1. The Process of Saving a Trend File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CC:4-4-2
Figure 4.4.2. Restoring and Reading a Trend File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CC:4-4-3
Figure 6.1.1. Configure Alarm Broadcast Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CC:6-1-3
Figure 6.1.2. Comparison of Message Traffic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CC:6-1-4
Figure 6.1.3. Effect of Partitioning into Logical Sections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CC:6-1-5
Figure 6.3.1. Area Name Configuration Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CC:6-3-3
Figure 6.3.2. Alarm List Configuration Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CC:6-3-9
Figure 6.3.3. Event List Configuration Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CC:6-3-14
Figure 6.4.1. Log Display Configuration Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CC:6-4-2
Figure 6.4.2. Examples of Criteria Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CC:6-4-5
Figure 6.4.3. Using the Alarm Log Display Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CC:6-4-7
Figure 6.5.1. Alarm Configuration Screen—Page 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CC:6-5-2
Figure 6.5.2. Automatic Alarm Deletion Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CC:6-5-7
Figure 6.5.3. Example of an Alarm Banner . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CC:6-5-12
Figure 6.5.4. Example of an Alarm Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CC:6-5-12
Figure 6.6.1. Example Portion of an Animation Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CC:6-6-2
Figure 7.1.1. Operator Change Log Entries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CC:7-1-7
Figure 7.2.1. Login Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CC:7-2-3
Figure 7.2.2. Changing a Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CC:7-2-4
Figure 7.3.1. Console Configuration Screen—Page 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CC:7-3-9
Figure 7.3.2. User Profile Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CC:7-3-13
Figure 7.3.3. Plant Unit Access Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CC:7-3-17
Figure 7.3.4. User Name Detail Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CC:7-3-19
Figure 7.3.5. Changing Configuror to System Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CC:7-3-24

CC: xxiii
List of Tables
Table 1.1.1. Command Console Configuration Screen Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CC:1-1-5

Table 1.1.2. How Node Ownership and Plant Unit Ownership Work Together . . . . . . . . . . . . . . . . CC:1-1-23
Table 1.1.3. Printer Interface Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CC:1-1-29
Table 1.2.1. Color Configuration Screen Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CC:1-2-4
Table 1.3.1. Group Display Entries for Faceplates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CC:1-3-4
Table 1.4.1. Command Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CC:1-4-3
Table 1.4.2. Special Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CC:1-4-3
Table 1.4.3. How to Configure Alarm Annunciation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CC:1-4-5
Table 1.5.1. Message Pair Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CC:1-5-2
Table 1.5.2. Preconfigured Standard Message Pairs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CC:1-5-6
Table 1.5.3. Preconfigured User Message Pairs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CC:1-5-8
Table 1.6.1. Block Print Setup Screen Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CC:1-6-3
Table 2.2.1. Process Graphic Object Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CC:2-2-5
Table 2.2.2. Screen Fields on the Edit Object Menu for Shape Characteristics . . . . . . . . . . . . . . . CC:2-2-16
Table 2.2.3. Objects that Display Block Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CC:2-2-25
Table 2.2.4. Screen Fields on the Edit Object Menu for the Tag, Blkdes, and
Mode Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CC:2-2-27
Table 2.2.5. Objects that Display Block Variable Information in Character Form . . . . . . . . . . . . . . CC:2-2-28
Table 2.2.6. Screen Fields on the Edit Object Menu for Link, Units, and Disc Objects . . . . . . . . . CC:2-2-30
Table 2.2.7. Objects that Display Block Variable Information in Graphic Form . . . . . . . . . . . . . . . CC:2-2-31
Table 2.2.8. Screen Fields on the Object Edit Menu for the Hdev, Vdev, and
Ticbar Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CC:2-2-34
Table 2.2.9. Screen Fields on the Edit Object Menu for the Hdev, Vdev, and
Ticbar Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CC:2-2-36
Table 2.2.10. Objects that Display Faceplates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CC:2-2-37
Table 2.2.11. Screen Fields on the Edit Object Menu for the Trend Object . . . . . . . . . . . . . . . . . . CC:2-2-43
Table 2.2.12. Screen Fields on the Edit Object Menu for the Text Object . . . . . . . . . . . . . . . . . . . . CC:2-2-47
Table 2.2.13. Screen Fields on the Edit Object Menu for the Alarm Object ................. CC:2-2-50
Table 2.2.14. Grouping Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CC:2-2-60
Table 2.2.15. LinkEd Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CC:2-2-68
Table 2.2.16. Display Manipulation Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CC:2-2-73
Table 2.2.17. Screen Fields on the Edit Object Menu for Target Object . . . . . . . . . . . . . . . . . . . . . CC:2-2-78
Table 2.2.18. Screen Fields on the Edit Object Menu for Icon Object . . . . . . . . . . . . . . . . . . . . . . . CC:2-2-81
Table 2.2.19. Screen Fields on the Edit Object Menu for the Bface Object . . . . . . . . . . . . . . . . . . CC:2-2-84
Table 2.3.1. Parameter Limits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CC:2-3-2

CC: xxiv
Table 3.4.1. Report Configuration Screen Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CC:3-4-3

Table 3.4.2. Report Object Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CC:3-4-6
Table 3.4.3. Editing Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CC:3-4-9
Table 3.4.4. Trend Log Field Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CC:3-4-29
Table 3.4.5. List Object Configuration Screens . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CC:3-4-36
Table 3.4.6. Generate Field Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CC:3-4-38
Table 4.2.1. Trend File Setup Screen Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CC:4-2-3
Table 4.2.2. Trend File Configuration Screens . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CC:4-2-6
Table 4.3.1. Trend Group Configuration Screen Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CC:4-3-3
Table 5.1.1. Symbols Used in Command Lines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CC:5-1-2
Table 5.1.2. Commands that Call Up Screens . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-13
Table 5.1.3. Commands that Perform Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-114
Table 5.1.4. Commands that Perform Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-115
Table 6.1.1. Comparison of Alarm Inhibiting Logic Step Functions . . . . . . . . . . . . . . . . . . . . . . . . . CC:6-1-7
Table 6.2.1. How Node Ownership and Plant Unit Ownership Work Together to
Determine Alarm Storage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CC:6-2-1
Table 6.3.1. Alarm Type Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CC:6-3-2
Table 6.3.2. Area Name Configuration Screen Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CC:6-3-4
Table 6.3.3. Alarm List Configuration Screen Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CC:6-3-10
Table 6.3.4. Reserved Event Numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CC:6-3-11
Table 6.3.5. Event List Configuration Screen Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CC:6-3-15
Table 6.4.1. Log Display Configuration Screen Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CC:6-4-3
Table 6.4.2. Alarm Log Display Screen Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CC:6-4-8
Table 6.5.1. Alarm Configuration Screen Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CC:6-5-3
Table 6.5.2. Alarm Configuration Screen----Automatic Alarm Deletion Fields . . . . . . . . . . . . . . . . CC:6-5-8
Table 6.6.1. Tag Animation Hardware Alarms Have More Priority than%Crit
Unacked, Cleared Alarm%ISA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CC:6-6-4
Table 6.6.2. Tag Animation Hardware Alarms Have More Priority than%Adv
Table 6.6.3. Tag Animation Hardware Alarms Have More Priority than%Batch
Table 6.6.4. Tag Animation Hardware Alarms Have More Priority than%System
Table 6.6.5. Tag Animation Hardware Alarms Have More Priority than%Disk or None
Table 6.6.6. Tag Animation Hardware Alarms Have More Priority than%Crit
Unacked, Cleared Alarm%RMT or Color . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CC:6-6-9
Table 6.6.7. Tag Animation Hardware Alarms Have More Priority than%Adv
Table 6.6.8. Tag Animation Hardware Alarms Have More Priority than%Batch

CC: xxv
Table 6.6.9. Tag Animation Hardware Alarms Have More Priority than%System
Table 6.6.10. Tag Animation Hardware Alarms Have More Priority than%Disk or None
Table 6.6.11. Block Variable Value and Trend Group Display Tag Animation
Hardware Alarms Have More Priority than%Crit
Hardware Alarms Have More Priority than%Adv
Hardware Alarms Have More Priority than%Batch
Hardware Alarms Have More Priority than%System
Hardware Alarms Have More Priority than%Disk or None
Table 6.6.21. Plant Unit and Area Name Animation

CC: xxvi

Table 6.6.31. Alarm and Icon Object Animation
Table 6.6.41. Alarm Message Source Description Animation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CC:6-6-48
Table 7.1.1. Commands that Call Up Screens . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CC:7-1-3
Table 7.2.1. Login Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CC:7-2-3
Table 7.3.1. Console Configuration Screen Fields—Page 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CC:7-3-9
Table 7.3.2. User Profile Directory Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CC:7-3-13
Table 7.3.3. Plant Unit Access Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CC:7-3-17
Table 7.3.4. User Name Detail Screen ................................................ CC:7-3-20

1984-2643-7102
1984-2643-7112
RS3t
Chapter 1:
Configuring Operating Characteristics
Section 1: Configuring Console Operations . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1-1

The Menu Command Console Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1-2
Configuring the Command Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1-3
Console Configuration Screen Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1-5
Configuring Access to an Alternate Console Disk over the PeerWay . . . . . . . 1-1-12
Configuring Consoles to Switch Keyboard Control . . . . . . . . . . . . . . . . . . . . . . 1-1-14
Configuring 16--Character Block Tags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1-15
Tags Affected . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1-15
Splitting and Masking Tags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1-15
Taking Advantage of Masking and Splitting Options . . . . . . . . . . . . . . . . . . . . . 1-1-16
Split Tags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1-17
Where Tags Are Automatically Split . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1-17
Specifying Where to Split Tags—Tag Row Break . . . . . . . . . . . . . . . . . . . . . 1-1-18
Masking Tags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1-19
Where Masking Does Not Apply . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1-19
Specifying a Mask . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1-20
Turning Masking On and Off . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1-21
How Tag Splitting and Masking Interact . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1-22
Node Ownership and Plant Unit Ownership . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1-23
Configuring Node Ownership . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1-24
Configuring Plant Unit Ownership . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1-25
Operator Change Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1-26
Hints for Configuring Console Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1-28
Configuring Refresh and Advance Request Rates . . . . . . . . . . . . . . . . . . . . . . . 1-1-30
Screen Refresh Rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1-31
Field Refresh Rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1-32
Section 2: Configuring Color . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2-1

Master Color Selection Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2-2
Color Configuration Screens . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2-3
Hints for Configuring Colors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2-8
RS3: Configuring Operating Characteristics Contents

CC: ii
Section 3: Configuring Operating Displays . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3-1

Configuring Group Displays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3-2
Group Directory Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3-2
Group Display Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3-3
Configuring Unit Displays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3-5
Unit Directory Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3-5
Unit Display Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3-6
Configuring Overview Displays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3-7
Overview Directory Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3-7
Overview Display Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3-8
Section 4: Configuring Callup and Display Buttons . . . . . . . . . . . . . . . . . . . 1-4-1

Configuring Callup Buttons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4-2
Configuring a Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4-3
Configuring a Callup Button Number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4-4
Configuring Alarm Annunciation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4-5
Callup Buttons Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4-7
Display Buttons Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4-8
Hints for Callup Buttons and Display Buttons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4-9
Section 5: Configuring Message Pairs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5-1

Standard and User Message Pairs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5-2
The Message Pairs Screens . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5-3
Hints for Using Message Pairs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5-9
Section 6: Configuring the Block Print Function . . . . . . . . . . . . . . . . . . . . . . 1-6-1
Section 7: Multinational Characters and Russian Console . . . . . . . . . . . . . 1-7-1

Multinational Characters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7-1
Russian Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7-1

CC: iii
List of Figures
Figure Page
1.1.1 Menu Command Console Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1-2
1.1.2 Command Console Configuration Screen—Page 1 . . . . . . . . . . . . . . . . 1-1-3
1.1.3 Command Console Configuration Screen—Page 2 . . . . . . . . . . . . . . . . 1-1-4
1.1.4 Console Configuration Screen—Page 3 . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1-4
1.1.5 Access to Alternate Console Disk over the PeerWay . . . . . . . . . . . . . . 1-1-13
1.1.6 Console Configuration Screen Switch Keyboard Examples . . . . . . . . . 1-1-14
1.1.7 Examples of Split Tags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1-17
1.1.8 Splitting Character Tags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1-18
1.1.9 Masking Character Tabs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1-20
1.1.10 Interaction of Tag Splitting and Masking . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1-22
1.1.11 Plant Status Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1-24
1.1.12 Plant Unit Configuration Field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1-25
1.1.13 Operator Change Log Screen Entries . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1-27
1.1.14 Advance Request Concept . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1-34
1.2.1 Master Color Selection Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2-2
1.2.2 Color Configuration Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2-3
1.3.1 Group Directory Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3-2
1.3.2 Group Display Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3-3
1.3.3 Unit Directory Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3-5
1.3.4 Unit Display Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3-6
1.3.5 Overview Directory Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3-7
1.3.6 Overview Display Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3-8
1.4.1 Multitube Callup and Display Buttons . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4-1
1.4.2 Alarm Annunciation Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4-2
1.4.3 Option Keyboard Callup Button Example . . . . . . . . . . . . . . . . . . . . . . . . . 1-4-4
1.4.4 Alarm Annunciation Screen Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4-6
1.4.5 Callup Buttons Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4-7
1.4.6 Display Buttons Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4-8
1.5.1 Faceplates and Message Pairs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5-1
1.5.2 Standard Message Pairs Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5-4
1.5.3 User Message Pairs Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5-5
1.6.1 Block Print Setup Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6-2

CC: iv
List of Tables
Table Page
1.1.1 Command Console Configuration Screen Fields . . . . . . . . . . . . . . . . . . 1-1-5
1.1.2 How Node Ownership and Plant Unit Ownership Work Together . . . . 1-1-23
1.1.3 Printer Interface Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1-29
1.2.1 Color Configuration Screen Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2-4
1.3.1 Group Display Entries for Faceplates . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3-4
1.4.1 Command Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4-3
1.4.2 Special Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4-3
1.4.3 How to Configure Alarm Annunciation . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4-5
1.5.1 Message Pair Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5-2
1.5.2 Preconfigured Standard Message Pairs . . . . . . . . . . . . . . . . . . . . . . . . . 1-5-6
1.5.3 Preconfigured User Message Pairs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5-8
1.6.1 Block Print Setup Screen Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6-3

CC: 1-1-1
Section 1:
Configuring Console Operations
This section shows how to configure the Console Configuration screen,

node ownership and plant unit ownership, and keyboard control
switching. This section also describes the Operator Change Log, and
provides hints for configuring console operations.
RS3: Configuring Operating Characteristics Configuring Console Operations

CC: 1-1-2
The Menu Command Console Screen
The Menu Command Console Screen is the Main Menu from which you
can select other directories and configure your console.
Figure 1.1.1 shows the Menu Command Console Screen.
- To call up: - To access other screens:

D Type MCC [ENTER] at the command line.
D [PAGE AHEAD] to see Page 1 of the
D [PAGE AHEAD] from Page 3 of the Console Console Configuration Screen.
Configuration Screen
D [PAGE BACK] to see Page 3 of the
D [PAGE BACK] from Page 1 of the Console Console Configuration Screen.
Configuration Screen
MENU COMMAND CONSOLE 16-Dec-93 15:22:10

Process Graphics Directory Disk Directory PeerWay
Overview Directory Disk Directory
Unit Directory Configure Command Console
Group Directory Plant Status
Trend Group Directory Process Active Alarms
Tuning Display Directory Alarm List Configuration
Report Read Directory Operator Log
Copyright E 1981-1994 Fisher-Rosemount Systems, Inc
FULL CONFIG 1
- To select a Directory on the MCC screen:

D Place the cursor over the desired
directory and press [SELECT].
Figure 1.1.1. Menu Command Console Screen

CC: 1-1-3
Configuring the Command Console
The Console Configuration screen is used to configure command

console operating characteristics. The Console Configuration screen
consists of two screen pages of fields. To move between pages, you
press either [PAGE AHEAD] or [PAGE BACK].
Figure 1.1.2 shows an example of page 1 of the Console Configuration

screen. Figure 1.1.3 shows an example of Page 2 of the Console
Configuration screen. Figure 1.1.4 shows an example of Page 3 of the
Console Configuration screen. Table 1.1.1 gives the parameters and
descriptions of the fields on the screen.

D Type CCC [ENTER] at the command line. D [PAGE AHEAD] to see Page 2 of the
D [PAGE AHEAD] from Command Console Console Configuration screen.
Menu. D [PAGE BACK] to see Menu Command
D [PAGE BACK] from Multitube Configuration. Console Screen.
CONSOLE CONFIGURATION 25-July-92 12:07:37

This is Node 32 MTCC Date Þ24-Dec-90 Time Þ12:08:36
Prgm Revision 15.xx PX ENG 68020 MTCC
Boot Revision 9.08 Peerway # Þ2 Slot widthÞ30
Last Restarted 24-July-92 09:02:47
Logs: Batch >Disable Maint > Disable Time Correction ®.00 Sec./day
Alarm >Disable Op Chg ÞDisable
ASCII Keyboard >Configuror Keyclass for Reports ÞOPER
Key Click >yes
Mark Key >no Reboot Menu ®13
Graphics Menu Key >no
Speaker Volume ®Med Printer/Modem Config
Alarm Speaker ®yes
Grp Blk ID for Oper ®descriptors Printer ÞFujitsu >Reset
Tags or Addresses Þtags
PID Proportional ÞGain Baud Þ4800 Print Node Þ28
Tape Auto Load Þno
Configuration File FF Þyes L/Pg Þ66
Name Update Þyes Autodial Þno
Volume Name : TMP
File Name : GRP-WDAY1
CONFIG 1
Figure 1.1.2. Command Console Configuration Screen—Page 1

CC: 1-1-4
- To access other screens:

D [PAGE AHEAD] to see Page 3 of the
Console Configuration Screen.
D [PAGE BACK] to see Page 1 of the Console
Configuration Screen.
CONSOLE CONFIGURATION 27-Jul-92 09:44:23

Keyboard Nodes>0 >0 >0 Tag Mask XXXXXXXXXXXXXXXX Tag Position: 16
Keyboard Revisions Use Tag Mask >N >INITIALIZE TAG MASK
KBI 4.1
TB 4.1 Tag Row Break >0
DISPPNL
OPTPNL1 1.4 Change Tag Size >Y Old>8 New>16
OPTPNL2 WARNING: WHILE ’Change Tag Size’ IS SET (Y),
OPTPNL3 TAG OBJECTS CONFIGURED IN REPORTS AND IN
Tape Drive Type RS3*T1 45S PR. GRAPHICS MAY BE CHANGED IN SIZE
Backup Disks WHEN CONFIG SCREEN FOR EITHER IS ACCESSED.
Overlay Backup Node >None Volume > In Use>no
General Backup Node >None Volume > In Use>no
Keyclass for Loop Tuning >SUPER
Keyclass for Ignore Interlock >SUPER
Field Refresh >0.5 secs Screen Refresh > 1.0 Advance Requests >3
FULL CONFIG 1
Figure 1.1.3. Command Console Configuration Screen—Page 2

D [PAGE AHEAD] to view the Menu D [PAGE BACK] to view Page 2 of the
Command Console Screen. Console Configuration Screen.
CONSOLE CONFIGURATION 12-Mar-93 10:56:05
System-wide Password Management

Title For Login Screen *Fisher-Rosemount Systems, Inc.
Primary Volume For $$PASSWD *Node_88
Backup Volume For $$PASSWD *Node_88
Current Volume For $$PASSWD >Node_88
Figure 1.1.4. Console Configuration Screen—Page 3

CC: 1-1-5
Console Configuration Screen Fields
Table 1.1.1 describes the fields on Pages 1, 2, and 3 of the Console

Configuration screen.
Table 1.1.1. Command Console Configuration Screen Fields
Field Description
Specifies the maximum number of outstanding data request messages

to a controller that a console will allow at one time. The data
requested is used to update block links and data points in process
graphics and group displays. Allowable values are from 1 to 5
Advance Requests requests. The default value is 3 requests.
NOTE: Advance Request can affect the performance of the PeerWay
and controller. For more information on Configuring Refresh and
Advance Request Rates, see 1-1-30.
Specifies if the console alarm speaker is functioning. Press [ENTER]

to change the entry. Alarm speaker volume is determined by the
Alarm Speaker “Speaker Volume” field.
D Yes specifies that the alarm speaker produces sound.
D No specifies that the alarm speaker does not produce sound.
Specifies whether the configuror keyboard operates as an enhanced

keyboard or as a normal configuror keyboard. Press [ENTER] to
change the entry.
D Enhanced specifies that the keyboard operates as an
ASCII Keyboard
enhanced keyboard. For more information about enhanced
keyboard displays, see OP.
D Configuror specifies that the keyboard operates as a normal
configuror keyboard.
Specifies whether or not a modem is used to generate a print request

to a remote printer. This field only applies if the printer is connected to
Autodial
this node. Entries are yes and no. Press [ENTER] to change the
entry.
Backup drive where the $$PASSWD file resides; cannot be an SRU.

Enter up to 10 alphanumeric characters that match a valid disk drive
Backup Volume for $$PASSWD name.
NOTE: A primary name that is blinking in yellow indicates that this
node has been out of service at some time since configuration.
Specifies the communication speed (bits per second) between the

console and the printer. This field only applies if the printer is
Baud connected to this node.
Entries are 300, 600, 1200, 2400, 4800, and 9600.
Displays the revision level of the Boot ROM on the console processor
Boot Revision
board.
(continued on next page)

CC: 1-1-6
Table 1.1.1. Command Console Configuration Screen Fields (continued)
Field Description
Determines whether tag objects should change size in process

graphics and reports. The “Old” and “New” fields appear only if the
Change Tag Size value of “Change Tag Size” is “Y”.
Old and New This feature is useful when upgrading from an earlier version console
software. For more information on changing tag size, see the
Software Upgrade Notes.
Drive where the $$PASSWD file is currently being stored.

Current Volume For $$PASSWD Enter up to 10 alphanumeric characters that match a valid disk drive
name.
Specifies the current date on all PeerWay nodes. Changes to one

console will change all nodes.
Date NOTE: Under a password security system, this field is designated with
an asterisk (*), and may only be changed by a system manager
(sysmgr).
Specifies whether or not a form feed is generated on the printer after a

FF print has finished. This field only applies if the printer is connected to
this node. Entries are yes and no.
Specifies the maximum rate at which the console can refresh a graphic
Field Refresh object field. Allowable refresh rates are from 0.5 to 4 seconds. The
default refresh rate is 0.5 seconds.
Displays the file name of the console configuration file that is loaded
File Name
from console battery backup memory if the console is rebooted.
General Backup Node Specifies a backup node for process graphic files.
Specifies whether or not the [HOME/MENU] key calls up the

user--configured $$MENU graphic file. Press [ENTER] to change the
entry.
D Yes specifies that the $$MENU graphic file is called up if the
Graphics Menu Key
[HOME/MENU] key is pressed at the command line (or pressed
twice from anywhere on a screen).
D No specifies that the [HOME/MENU] key does not call up a
graphic file.
Specifies if tags/addresses or descriptors are displayed when group

displays are called up and an operator key is inserted in this console.
Press [ENTER] to change the entry.
Grp Blk ID for Oper D Tags/Addrs specifies that tags or addresses are displayed.
(The “Display Tags“ field determines whether the tag or the
address is displayed.)
D Descriptors specifies that a descriptor is displayed.
Resets the tag mask back to its default state in which no characters
Initialize Tag Mask
are masked.
Keyboard Nodes Specifies the console node to which the keyboard is connected.

CC: 1-1-7
Field Description
Displays keyboard revision numbers for the following keyboard

hardware:
KBI (Keyboard Interface software) for
use with the console.
TB (Track Ball keyboard) for cursor and
Keyboard Revisions CRT Control.
DISPPNL(Display Panel keyboard) of operator functions. Also
referred to as the Operator’s keyboard.
OPTPNL (Options keyboard) with panels
1, 2, and 3 for calling up user--defined
sets of commands and graphic displays.
Specifies the access level for configuration of the following PID

ControlBlock fields on the Tuning Display screen:
— Integral Time
Key class for Loop Tuning
— Derivative Time
— Cont Gain/Prop Band
— FF Gain
Specify the access level for configuration of the following discrete

motor and valve function ControlBlock field on the Continuous
Key class for Ignore Interlock Faceplate screen:
— Ignore Interlock
Specifies the key class required to read and print reports.

D Oper specifies that operators, supervisors, and configurors can
read and print reports.
Key class for Reports
D Super specifies that supervisors and configurors can read and
print reports.
D Config specifies that configurors can read and print reports.
Specifies whether or not an audible sound is produced when a

keyboard button is pressed. The key click volume is determined by
Key Click the “Speaker Volume” field. Press [ENTER] to change the entry.
D Yes specifies that there is a key click.
D No specifies that there is no key click.
Specifies the number of lines printed on each page. This field only
L/Pg
applies if the printer is connected to this node. Entries are 0 to 127.
Last Restarted Displays the time when the console was last restarted.

CC: 1-1-8
Field Description
Specifies whether or not the particular log is enabled or disabled.

Logs:
Press [ENTER] to change the entry.
Batch
Batch =Batch log
Alarm
Alarm=Alarm log
Maint
Maint =Smart transmitter maintenance log
Op Chg
Op Chg =Operator change log
Specifies whether or not the [RECALL] button marks screens for

recall. Press [ENTER] to change the entry.
D Yes specifies that screens can be marked for recall.
D No specifies that screens cannot be marked for recall. The
Mark Key [RECALL] key only calls up the previous screen.
A screen is marked for recall by pressing [ENTER] from the command
line when that screen is displayed. A screen is recalled by pressing
the [RECALL] key and specifying the number of the screen (1--5) to be
recalled. After a screen has been recalled, the mark function for that
screen is removed.
Specifies whether or not the Configuration Volume Name and File

Name are updated. The Configuration Volume Name and File Name
determine which file is used to boot up the console.
D Yes specifies that the “Volume Name” and “File Name” fields
Name Update
change to show the last console configuration file that is loaded
or saved at this console.
D No specifies that the “Volume Name” and “File Name” fields do
not change.
Specifies a backup node on which screen overlays are stored.

Overlay Backup Node NOTE: Overlay Backup Node must be the same as the console which
it backs up (e.g. 68020=68020; 68040=68040)
Specifies the number of the PeerWay that is connected to the console

(1 -- 31). It is recommended that no PeerWay be designated as
PeerWay 31.
PeerWay #
If you change the PeerWay number, you should press [ENTER] twice
to verify the change.
Do not change this field if your process is running.
Specifies whether controller gain (Gain) or proportional band (Band) is

PID Proportional used at this console for PID blocks. Press [ENTER] to change the
entry.
Displays information about the console software.

Revision level — xx.xx
Graphics — PX (Pixel) or CHAR (Character)
Prgm Revision Language — ENG (English), FREN (French), or
GERM (German)
Processor — 68000 or 68020
Console type — MTCC or CC

CC: 1-1-9
Field Description
Primary drive where the $$PASSWD file resides; cannot be an SRU.

Enter up to 10 alphanumeric characters that match a valid disk drive
Primary Volume For $$PASSWD name.
NOTE: A primary name that is blinking in yellow indicates that this
node has been out of service at some time since configuration.
Specifies the node number to which print requests are sent. This
Print Node should be the node number of the console to which the printer is
connected. Entries are 0 to 992.
Specifies the type of printer. This field only applies if the printer is
connected to this node.
D TI810 should be used for the Texas Instruments model 810
Printer printer.
D Fujitsu should be used for a Fujitsu printer.
D Other should be used for any other printer.
Specifies the number of the enhanced keyboard software menu that

appears when the console reboots. The menu numbers are from the
Reboot Menu MENUS menu. This field only applies if “ASCII KeyboardÞEnhanced”
is configured. For more information about enhanced keyboard
software, see OP.
Resets the printer subsystem. In addition, you may have to turn the
Reset printer off and on to reset successfully.
To reset the printer, cursor to the field and press [ENTER].
Specifies the maximum rate at which the console can request data
from a controller. Allowable refresh rates are from 0.25 to 20.0
seconds. The default refresh rate is 0.25 seconds. Screens refresh is
used by the following screens:
D Process Graphics
Screen Refresh D Group Display
D Unit Display
D Overview Display
NOTE: The screen refresh rate can affect the performance of the
PeerWay and controller. For more information on Configuring Refresh
and Advance Requests Rates, see 1-1-30.
Specifies a time width used to tune PeerWay performance.

NOTE: Under a password security system, this field is designated with
Slot width (sysmgr).
This field must not be changed without the
supervision of Fisher--Rosemount personnel.
Specifies the speaker volume, which is used for audible alarm

Speaker Volume annunciation, key click, and entry errors at the console. Entries are
None, Low, Med, and High. Press [ENTER] to change the entry.

CC: 1-1-10
Field Description
Specifies whether blocks are identified by tag or by address on screen

displays at this console. Press [ENTER] to change the entry.
Tags or Addresses
D Tags specifies that blocks are identified by tag.
D Addresses specifies that blocks are identified by address.
Specifies portions of 16--character tags that do not appear on screens.

Tag Mask Hiding redundant or extraneous parts of the tag can make it easier for
the operator to identify blocks while viewing screens.
The “Tag Position” field appears only when the cursor is resting in the
Tag Position
“Tag Mask” field. It specifies the position of that character in the tag.
Specifies where a tag should be split if the default split is not

Tag Row Break
acceptable.
Specifies whether or not tapes are automatically loaded when inserted.

D Yes specifies that tapes are automatically loaded when inserted.
Tape Auto Load D No specifies that a manual tape load procedure must be
performed to load a tape.
If you are configuring a Multitube Command Console, configure this
field the same for all CRTs on the console.
Displays the tape drive on a console acting as a Master Node.

Possible displays are:
D RS3*T1 45S (Scorpion qic--24 format)
Tape Drive Type D RS3*T2 60S (Viper 2060S qic--24 format)
D RS3*T3 150S (Viper 2150S qic--150 format)
For more information about tape drive types and specifications, see
DT:1.
This is Node Displays the node number and console type.
Displays the current time on all PeerWay nodes. Changes to one

console will change all nodes.
Time NOTE: Under a password security system, this field is designated with
(sysmgr).
For HIA use only. Used with the highest--addressed operator interface
on the local Peerway to synchronize the HIA (Highway Interface
Time Correction
Adapter) tic master. Only a time correction on the tic master affects
the system.
Title for the system login screen.

Title for Login screen
Enter up to 40 alphabetic characters including spaces.

CC: 1-1-11
Field Description
Turns masking on or off. If masking is off, link displays show all

Use Tag Mask
characters in the block tag.
Displays the volume name of the console configuration file that is

Volume Name loaded from the console battery backup memory if the console is
rebooted.

CC: 1-1-12
Configuring Access to an Alternate Console Disk over the

PeerWay
Purpose
In rare circumstances, a console hard disk may fail. If that happens,

you can still access group displays, but you cannot access displays that
require the hard disk, such as process graphics.
However, you may still need to maintain operator control from that
console for a short period of time. You can configure a console so that
it accesses an alternate console disk over the PeerWay if its own hard
disk fails. You should correct the disk problem as soon as possible.
This feature is only available on the Multitube Command Console.
Configuration
The alternate console disk feature is configured on the Multitube

Configuration screen (see Figure 1.1.5). Each CRT node of the
Multitube Command Console is configured separately.
Overlay alternate disk
The overlay alternate disk provides access to overlays. Overlays are

the base structure of most system displays, and are stored on the hard
disk. Any console on the PeerWay that is the same console type and is
running the same console software as the console you are configuring
can be used as the overlay alternate disk.
General (graphic) alternate disk
The general alternate disk provides access to process graphic files.

The general alternate disk can be any disk drive on the PeerWay. Since
graphic displays use overlays, you must also configure an overlay
alternate disk if you want to configure a general alternate disk.
Events that cause a switch to the alternate disk

D When the local console cannot read its hard disk.
D When the user changes the “In Use” field on the Multitube
Configuration screen to “yes”. This action should only be done if
you want to test the alternate node.
Events that cause a switch back to the local disk
The local console does not automatically switch back to the local hard
disk when the disk becomes available. The console switches back to
the local hard disk when one of the following events occurs.

CC: 1-1-13
D When the user changes the “In Use” field on the Multitube
Configuration screen to “no”.
D The next disk access after the alternate disk fails.
D When a console configuration is loaded into the local console.
D When the local console restarts.

- To call up:
D [PAGE AHEAD] to see Menu Command
D [PAGE AHEAD] from Console Configuration
screen, Page 1. Console.
D [PAGE BACK] from Menu Command D [PAGE BACK] to see page 1 of the
Console. Console Configuration screen.
Specifies an alternate disk for NOTE: If you specify an alternate disk

overlays. Enter either the node that is part of a Multitube Command
number or the volume name. Console, the node number of the bus
The alternate disk node must be master appears in the field.
running the same console software
as the local node.


KBI 4.1
DISPPNL
OPTPNL1 1.4 Change Tag Size >N
OPTPNL2
OPTPNL3
Tape Drive Type RS3*T1 45S
Backup Disks
Overlay Backup Node >26 Volume >CS13 In Use>no
General Backup Node >28 Volume >CS17 In Use>no
Graphic Refresh >0.5 secs Screen Refresh > 1.0 Advance Requests >3
FULL CONFIG 1
Specifies an alternate disk for Indicates whether or not the alternate
process graphics files. Enter disk is in use (yes, no). You can also
either the node number or the change the entry manually.
volume name.
Figure 1.1.5. Access to Alternate Console Disk over the PeerWay

CC: 1-1-14
Configuring Consoles to Switch Keyboard Control
Multitube Command Consoles can be configured so that keyboard

control can be switched among Multitube CRTs on a PeerWay. The
keyboard switching is configured from the Multitube Configuration
screen.
Figure 1.1.6 shows two sample Multitube switching configurations. The

[CRT] button is used to switch keyboard control.
- To call up the Multitube Configuration screen:
1. Call up the Command Console Configuration screen, type
CCC [ENTER] at the command line.
2. Press [PAGE AHEAD] to call up page 2 of the Console
In this example, the keyboards can be switched between nodes 26 and 28. An
entry of 0 is configured in the unused field.
If [CRT] is pressed at a keyboard controlling node 26, control is switched to node
28. When [CRT] is pressed again, control is switched back to node 26.

Keyboard Nodes Þ 26 Þ 28 Þ 0
In this example, the keyboards can be switched between nodes 28, 30, and 26.
If [CRT] is pressed at a keyboard controlling node 30, control is switched to node 26.
When [CRT] is pressed again, control is switched to node 28. If [CRT] is pressed
again, control is switched back to node 30.

Keyboard Nodes Þ 28 Þ 30 Þ 26
Figure 1.1.6. Console Configuration Screen Switch Keyboard Examples

CC: 1-1-15
Configuring 16--Character Block Tags
RS3 software can accept ControlBlock tags and I/O block tags up to 16
characters, as well as only 8 character tags or fewer. The longer tags
allow you to use more descriptive tags to name blocks. The longer tags
can improve the operator interface.
As you work with the tags over eight characters, keep in mind:
D Tags are never truncated by the system. (However, a configuror
can specify a mask that causes a tag to appear truncated.)
D All printed output (other than screen prints) shows complete,
unmasked tags. This feature ensures that printed records
indicate the exact block to which a tag refers.
Tags Affected
ControlBlock tags and I/O block tags are the only tags that can use 16
characters. The Batch and SQC subsystems and the PLC and SMART
controllers use the term tag; however, these tags will remain 8
characters long.
Splitting and Masking Tags
The longer tags give you as configuror more flexibility in designing tags.
Two options on the Console Configuration screen, splitting tags and
masking tags, provide additional flexibility.
Splitting tags
On a few screens, tags are automatically split to fit on the screen. You
can override the default split and specify a split that makes your tags
easier to read and understand.
Masking tags
You might decide that not all information in a longer tag needs to be
displayed at all times. You can specify that part of the tag be masked
on displays to improve readability.

CC: 1-1-16
Taking Advantage of Masking and Splitting Options
As you design 16--character tags, you can use the new configuration
options most effectively if you keep these hints in mind:
D Devise tags that will split to separate general plant information on
one line, and specific device information on the other. To control
the split, use spaces, hyphens, or periods within the first 8
characters of a tag; or combine spaces with masking. (See “Split
Tags” on page 1-1-17 and “Masking Tags” on 1-1-19)
D Put repeated information in the same location in every tag. That
way you can mask the redundant information, and highlight
specific devices. (See “Masking Tags” on 1-1-19)
D Put information that might confuse operators or prevent them
from taking quick action in the same location in every tag. The
confusing information can be masked. (See “Masking Tags” on
1-1-19)
D Structure tag names so they are concise and useful for everyday
plant operation.
D Avoid trailing spaces.

CC: 1-1-17
Split Tags
On a few displays, 16--character tags are split to make them fit on the
screen. Tags are split into two rows of up to 8 characters each, one
below the other.
Where Tags Are Automatically Split
The software applies the following default rules when it splits tags:
D Tags of 8 or fewer characters are centered and displayed on one
line.
D Tags of more than 8 characters are split at the first space, period,
or hyphen that is found by scanning backwards from the eighth
character.
D If no space, period, or hyphen is found, or if a split using them
would result in a second line of more than 8 characters, then the
first line is filled with 8 characters and the remaining characters
are centered on the second line.
D Each row of a split tag is centered.
D A tag row break configured on the Console Configuration screen
takes precedence over a split defined by these rules.
Figure 1.1.7 shows examples of tags split using these rules.
Tag Text:
blower-228 plant 7 fan 3 STK1--A11Sensor 2 fan 24 valve.flow
Split Tag
Appearance:
12345678 12345678 12345678 12345678 12345678

blower-- plant 7 STK1--A1 fan 24 valve.
228 fan 3 1 flow
Sensor 2
Figure 1.1.7. Examples of Split Tags

CC: 1-1-18
Specifying Where to Split Tags—Tag Row Break
You can choose to override the default tag splitting rules and specify a
character position where tags should be split. Figure 1.1.8 shows an
example of splitting character tags.
NOTE:
1. If the position you specify would make the second line of the tag
longer than 8 characters, the default tag--splitting rules are used
instead.
2. The character position used by the system is based on the
unmasked tag. (See “How Masking and Splitting Interact” on
page 1-1-22 .)
- To call up, type: - To specify where to split the tag:

1. CCC [ENTER] at the command line. 1. Cursor to the “Tag Row Break” field.
2. [PAGE AHEAD] from Console Configuration 2. Type a number from 1 to 8 and press
screen to display page 2. [ENTER].
The number represents a character
- To save the configuration: position from 1 to 8 starting from the left.
D When you finish configuring tag splitting and The number 0 is the default, and can be
tag masking, be sure to save your typed in this field, but causes tags to split
configurations on disk (in the CC file). using the default tag--splitting rules.
For specific steps, see DT: 2--4. Tags will now split following the position
you typed.

KBI 4.1
DISPPNL
OPTPNL2
OPTPNL3
Tape Drive Type: RS3*t3 150S (qic-150)
Backup Disks
FULL CONFIG 1
Figure 1.1.8. Splitting Character Tags

CC: 1-1-19
Masking Tags
At each console, you can specify that portions of 16--character tags do

not appear on screens. By temporarily hiding redundant or extraneous
parts of the tag, this feature can make it easier for the operator to
identify blocks while viewing screens. (Note that the operator can
toggle between viewing the masks or not by using the TTM command.
See “Turning Masking On and Off” on page 1-1-21.)
Where Masking Does Not Apply
Masking affects only displays, and applies in almost all cases. It does
not apply in the following instances:
D The full 16--character tag must be typed in all enterable fields.
(That is, you cannot type just the unmasked portion of the tag in
a field that requires you to enter a tag.)
D The tag of the block being configured is not masked on
configuration screens. Examples include continuous and
discrete ControlBlock:
— Faceplate displays
— Diagram displays
— Link displays
D Tags are not masked on printed output (other than screen prints).
This includes:
— Alarm lists
— Reports
— Batch reports
— RBL script listings

CC: 1-1-20
Specifying a Mask
You can specify or modify a mask on the Command Console

Configuration screen. Figure 1.1.9 shows an example of masking
character tags.
If you are not satisfied with the mask for some reason, you can initialize
the mask to return it to the default setting and start over.
- To call up, type: - To Mask the tag:

1. CCC [ENTER] at the command line. 1. Cursor to the “Tag Mask” field.
2. [PAGE AHEAD] from Console Configuration 2. Place the cursor on a character position
screen to display page 2. that you want hidden and press [ENTER].
(The character position is indicated in the
- To save the configuration: “Tag Position” field.)
D When you finish configuring tag splitting and The character position appears in normal
tag masking, be sure to save your video, indicating that the position will
configurations on disk (in the CC file). appear blank on displays.
For specific steps, see DT: 2--4. To unmask a masked (normal video)
character position, cursor to that position
and press [ENTER].
- To initialize the mask: 3. Repeat step 4 until you are satisfied with
D Cursor to the “Initialize Tag Mask” field and the mask.
press [ENTER]. The “Tag Mask” field is reset
to its default state in which no characters are
masked.

KBI 4.1
DISPPNL
OPTPNL2
OPTPNL3
Tape Drive Type RS3*T1 45S
Backup Disks
FULL CONFIG 1
Figure 1.1.9. Masking Character Tags

CC: 1-1-21
Turning Masking On and Off
Both configurors and operators can turn masking on and off. Use either
of two methods to toggle between masking and no masking.
- To toggle between masking and no masking:
D From page 2 of the Command Console Configuration screen,
cursor to the “Use Tag Mask” field and press [ENTER]. (The
value in this field is saved as the new default setting when you
save your configuration.)
or
D From the command line, type TTM (for Toggle Tag Mask) and
press [ENTER].

CC: 1-1-22
How Tag Splitting and Masking Interact
Tag splitting and masking interact to produce the tag display. When the
software splits and masks tags, it applies the following rules in the
following order:
1. If you specified a character position in the “Tag Row Break” field,
tags are split accordingly.
2. If you specified a mask, the tags are masked.
3. If you did not specify a character position in the “Tag Row Break”
field, the default tag splitting rules are applied.
Figure 1.1.10 shows examples of splitting and masking.
Example 1: Example 2:
1234567890123456 1234567890123456
Tag Tag STK1-A1Sensor 2
STK1-A1Sensor 2
1234567890123456 1234567890123456
Tag Mask XXXXXXXXXXXXXXXX Tag Mask XXXXXXXXXXXXXXXX
Tag Row Break: position 7 Tag Row Break: position 7
12345678 12345678
Tag split STK1-A1 Tag split STK1-A1
with mask off Sensor 2 with mask off Sensor 2
12345678
Tag split A1 Tag split 12345678
with mask on Sensor 2 with mask on Sensor 2
Example 3: Example 4:
1234567890123456 1234567890123456
Tag Tag STK1-Valve AB2
STK1 Sensor A
1234567890123456 1234567890123456
Tag Mask Tag Mask XXXXXXXXXXXXXXXX
XXXXXXXXXXXXXXXX
Tag Row Break: none specified Tag Row Break: none specified
12345678 12345678
Tag split STK1 Tag split STK1-Val
with mask off Sensor A with mask off ve AB2
12345678
Tag split Tag split Valve
12345678
with mask on Sensor A with mask on AB2
Figure 1.1.10. Interaction of Tag Splitting and Masking

CC: 1-1-23
Node Ownership and Plant Unit Ownership
Node ownership and plant unit ownership are defined at each console.
These two features work together to determine:
D Which blocks, batch tasks, and nodes the console can configure
and control, and
D Which alarms the console stores.
Table 1.1.2 shows how node ownership and plant unit ownership work
together.
Table 1.1.2. How Node Ownership and Plant Unit Ownership Work Together
If... then... only if the console...
the console stores alarms from

a block or batch task has a the block or task, and can
owns the plant unit number.
non--zero plant unit number, configure and control the block or
task,

a block or batch task has a plant the block or task, and can
owns the source node.
unit number of zero, configure and control the block or
task,

the source is not a block or batch the source, and can configure owns the source node.
task,
and control the source,

CC: 1-1-24
Configuring Node Ownership
Node ownership is configured on the Plant Status screen

(See Figure 1.1.11)
- To call up, type: - To access other screens:

D PS [ENTER] at the command line D [EXCH] to see PeerWay Overview
D [PEERWAY STATUS]
D [EXCH] from PeerWay Overview
Specifies the types of nodes displayed. Use the PeerWay number of

[NEXT OPTION] button to step through the displayed nodes.
choices.
PLANT STATUS 24-Jul-92 07:30:45

First Node Listed> 1 Peerway Number> ALL
Node Type Displayed > OWNED AND EXISTING NODES
Node Node Node Node
1 CTL Norm 20 MTCC
2 MTCC 22 MTCC
4 MC 26 MTCC
6 MTCC 28 MTCC
8 MTCC 30 CC
10 CTL Norm
12 MTCC
16 MTCC
Displays the node type:

CC Pedestal Command Console
CTL ControlFile -
DI Diogenes Interface To own a node:
HIA Highway Interface Adapter An owned node is backlighted. Cursor to
MC MiniConsole the field and press [ENTER] to toggle
MTCC Multitube or Hardened between the owned and not--owned state.
Command Console
RFI Rosemount Factor Interface
SCI Supervisory Computer Interface
SRU System Resource Unit
VAX MicroVAX to Peerway Interface
Figure 1.1.11. Plant Status Screen

CC: 1-1-25
Configuring Plant Unit Ownership
Plant unit ownership is configured on the Plant Unit Configuration

screen (see Figure 1.1.12).
- To call up: - Access other screens:

D PUC [ENTER] at the command line. D None
D [SELECT] from “Unit Ranges” field on
Area Name Configuration.
Owned plant units are followed by *.
PLANT UNIT CONFIGURATION 23-Jul-92 11:47:12
1 17 33 49 65 81 97 113 129 145 161 177 193 209 225 241

2 18 34 50 66 82 98 114 130 146 162 178 194 210 226 242
3* 19 35* 51 67 83 99 115 131 147 163 179 195 211 227 243
4* 20 36 52 68 84 100 116 132 148 164 180 196 212 228 244
5* 21 37 53 69 85 101 117 133 149 165 181 197 213 229 245
6* 22 38 54 70 86 102 118 134 150 166 182 198 214 230 246
7 23 39 55 71 87 103 119 135 151 167 183 199 215 231 247
8 24 40 56 72 88 104 120 136 152 168 184 200 216 232 248
9 25 41 57 73 89 105 121 137 153 169 185 201 217 233 249
10 26 42 58 74 90 106 122 138 154 170 186 202 218 234 250
11 27 43 59 75 91 107 123 139 155 171 187 203 219 235 251
12 28 44 60 76 92 108 124 140 156 172 188 204 220 236 252
13 29 45 61 77 93 109 125 141 157 173 189 205 221 237 253
14 30 46 62 78 94 110 126 142 158 174 190 206* 222 238 254
15 31 47 63 79 95 111 127 143 159 175 191 207 223 239 255
16 32 48 64 80 96 112 128 144 160 176 192 208 224 240 256
Set range ®3,6 Clear range ®

CONFIG 4
- To own a range of plant units: - To own a single plant unit:

D Cursor to the ”Set range” field, type a D Cursor to the plant unit number and
range of numbers separated by a comma press [ENTER] to toggle between
(for example ”3,6”), then press [ENTER]. the owned and not--owned state. An
owned plant unit number is followed
by *.
- To no longer own a range of plant units:
D Cursor to the ”Clear range” field, type a
range of numbers separated by a comma
(for example ”3,6”), then press [ENTER].
Figure 1.1.12. Plant Unit Configuration Field

CC: 1-1-26
Operator Change Log
The Operator Change Log is a record of operator activities at the local

console and at any nodes owned by this console. Activities include
changes made to the block mode, setpoint, inputs, outputs, and
adjustable parameters, as well as key insertion and withdrawal. In
password systems, login name or user number replace the source and
key fields. The Operator Change Log screen cannot be altered.
To log an activity, the console initiating the activity must have a key
inserted, and the “Op Chg” field of the Console Configuration screen
must be configured as “Enable”.
The Operator Change Log is stored in console RAM. The size and
printing properties of the Operator Change Log are configured on the
Alarm List Configuration screen (see CC:6-3-8).
Figure 1.1.13 shows an example of this screen with field descriptions. It

shows the screen as seen in password systems, and shows the screen
format for SCI and QBI.

CC: 1-1-27

D OL [ENTER] from the command line. D [PAGE BACK] to see Event List 10.
D [PAGE AHEAD] from Event List 10.
Occur = Time that the activity occurred Old = Initial value of the block parameter
PU = Plant unit New = New value of the block parameter
Location = ControlBlock tag Source = Console type and node of the
Parameter = Block parameter that was changed console initiating the activity
Key = Key type (operator, configuror,
supervisor) and number
OPERATOR CHANGE LOG 25-Jul-92 12:07:37

Occur PU Location Parameter Old New Source Key
14:46:34 1 :PIC-112/LS Input B .0 35.0 CC=4 OPER 6
14:46:26 104 :PIC-112 Block Mode LOCAL AUTO CC=4 OPER 6
14:45:45 0 :FIC-104/LS Input B .0 55.0 CC=4 OPER 6
14:44:59 0 :PIC-104/LS Input B .0 55.0 CC=4 OPER 6
14:44:27 0 Oper Chged Key No Key OPER 6 CC=4
14:44:20 0 Oper Chged Key CONFIG 3 35.0 CC=4
20:42:29 0 :FQ-32708 Block Mode AUTO MANUAL CC=4 CONFIG 3
* End *
Screen Layout with Keylock System
MakeConsoleKeylock System* OPERATOR CHANGE LOG 12-Mar-93 11:01:41
--Occur---PU------Location-----Parameter----Old------New-----Login Name-------
------------------- 12-Mar-93
11:00:45 175 :=49A-15/PV Input A .00 .60 kenta
11:00:13 175 :=49A-17 Block Mode AUTO MANUAL kenta
11:01:28 0 Login Change kenta No User
11:01:28 0 Login Change ******* *******
10:59:40 175 :=49AA502 Block Mode AUTO MANUAL joew
10:59:33 175 :=49AA502 Block Out .00 .50 joew
Screen Layout with a Password System
Login Name = User name as User No. = User Number as

configured on the configured on
User Name Detail User Name
Screen Detail Screen
Occur PU Location Parameter Old New User No.

-------- ---- ---------------- ------------ -------- -------- ------- --------
hh:mm:ss #PU >TAG4567890123456 Parameter012 OldValue NewValue User No.
Screen Layout with an SCI or QBI Interface
Figure 1.1.13. Operator Change Log Screen Entries

CC: 1-1-28
Hints for Configuring Console Operations
This section discusses some problems that you may encounter when
configuring console operations, along with some helpful configuration
tips.
Configuration Problems
Listed below are possible problems that might occur when configuring
console operations along with possible solutions.
- There is no console speaker sound even though I have a
“Speaker Volume” configured.
“Alarm SpeakerÞyes” must be configured on the Console
Configuration screen to get any sound.
- After I mark a screen for recall and then recall the screen once,
I can’t recall the screen again.
The mark function only lets you recall a screen once.
- The printer does not reset after I perform the reset function.
To reset a printer fully, you may have to turn the printer off and on.
To reset a printer from a console node that is not connected to the
printer, the console you are at must own the console node that is
connected to the printer.
- My alarm lists don’t print at the right print node.
Alarm lists print at the print nodes specified on the Alarm List
- The printer is functioning properly, but I can’t get a console
screen print.
The cause of this problem could be one of many sources:
— Call up the Console Configuration screen and see if you have
the correct “Print Node” field entry.

— If the “Print Node” field is backlighted, you need to restore the
printer. Call up the Alarm List Configuration screen, cursor to

the “Restore Primary Printer Nodes” field, and press
[ENTER].
— You may need to reset the printer.
- The “Print Node” field on the Console Configuration screen is

backlighted.
You need to restore the printer. Call up the Alarm List Configuration
screen, cursor to the “Restore Primary Printer Nodes” field, and
press [ENTER].

CC: 1-1-29
Configuration Tips
- How to configure the printer for specific tasks

Table 1.1.3 lists configuration parameters for some useful printer
instructions.
Table 1.1.3. Printer Interface Instructions
Task Performing the Task
1. Set “FF” to yes.

To print alarm and event lists. 2. Set “L/Pg” to 66 (for 8 1/2 by 11
paper) or 69 (for A4 or 210 by 297
mm paper).
1. Set “FF” to no.

To print blocks or full screens (two screens per page). 2. Set “L/Pg”to 33 (for 8 1/2 by 11
paper) or 34 (for A4 or 210 by 297
mm paper).
Set “Autodial” to yes. When “Autodial” is

To generate a print request to a remote printer. (This feature set to yes, the “DialÞ” field comes up to
requires that a modem be connected to the printer port.) indicate that a phone number (xxx--xxxx)
should be entered.
To designate the type of printer being used. Enter an option in the “Printer” field.
Enter an option in the “Baud” field. The

entry must match the communication
To set the console communication rate between the console rate set at the printer. The
and the printer.
recommended rate for TI--810 and
Fujitsu printers is 4800.

CC: 1-1-30
Configuring Refresh and Advance Request Rates
The following fields control the rate at which console graphics and block
displays can request data from controller processors:
D Screen Refresh Rate
D Field Refresh Rate
D Advance Request
Refresh rate differs from advance request in that refresh rate specifies
how often request messages are generated, whereas advance request
specifies how many request messages can be generated
simultaneously. However, when used improperly, both refresh rate and
advance request can have a similar disruptive effects on system
performance. By generating too many messages too fast, high advance
request and refresh rates have the potential to flood the PeerWay and
overwhelm the Coordinator Processor (CP) and controller processors.
Optimum communications between consoles, CPs, and controller

processors require a balance between refresh rate and advance
request. The appropriate balance varies depending on the
configuration and demands of the system. For every system condition,
there is the maximum rate at which the console and controller processor
can communicate without causing disruption or drain on PeerWay
resources. As a general rule, you should use the lowest refresh rate
and advance request number that your system can efficiently
accommodate. Some experimentation may be required to find the
optimum values.

CC: 1-1-31
Screen Refresh Rate
Screen refresh refers to the maximum rate at which a console can

request data from a controller for refreshing the following screens:
D Process Graphics
D Group Display
D Unit Display
D Overview Display
A console requests data by generating request messages. The refresh

rate enables you to slow the generation of request messages to better
match processing speed of the controller or prevent multiple consoles
from overloading a single controller with data requests.
If the screen refresh rate is too high, these screens will request input
data faster than the scan time of the controller processor; that is, the
rate at which the controller can process and update data. At best, this
situation is an inefficient use of memory; at worst, it is a potentially
disruptive situation in which excessive messages can flood the
PeerWay and overwhelm the CP and controller processor.
Allowable screen refresh rates are from 0.25 to 20.0 seconds.

However, if the Controller cannot respond to data requests at the
specified refresh rate, the actual refresh rates will be slower. A screen
cannot refresh until it has received data for all data points requested. A
general recommendation is to use the slowest refresh rate your process
can accommodate (1 to 2 seconds or slower for infrequently used
consoles).
The optimum refresh rate depends on the configuration and peak

demand of your system.

CC: 1-1-32
Field Refresh Rate
The field refresh is used as a supplement to screen refresh for

refreshing individual objects on process graphic displays. The object or
field is refreshed by positioning the cursor on it.
The field refresh rate gives you a means for controlling the refresh rate
of individual objects on the graphic. You typically want to use a faster
speed for the field refresh rate than for the screen refresh rate. A fast
field refresh rate for a single object is less likely to upset process
performance than a fast screen refresh rate for an entire graphic.
Allowable field refresh rates are from .5 to 4 seconds. However, field

refresh rate should meet two criteria:
D The field refresh rate should be at least a half of a second faster
than the screen refresh rate. For example, a field refresh of 0.5
will offer little advantage over a screen refresh rate of 0.75.
D The field refresh rate should not exceed the scan time of the
controller processor. Otherwise, the console will generate
request messages faster than the controller processor can
respond.
The advance request number specifies the maximum number of

outstanding data request messages that a console can send to a
controller at one time. Each time the console receives a reply to an
outstanding message, it can generate another message to bring the
number of outstanding messages back up to the number specified by
the advance request.
A single request message can contain data requests for multiple links
for the same controller processor. For example:
=1A--2
=1A--3
=1A--53
=1A--45
However, a request message cannot contain multiple data requests for

different controller processors. For example:
=1A--2
=1B--54
=31C--5

CC: 1-1-33
From a practical point of view, advance request specifies the number of

controller processors with which a graphic or group display can
communicate simultaneously. Allowable advance request numbers are
from 1 to 5 (the default is 3). This means that a console can
communicate with up to 5 controllers at a time. A high advance request
number may be advantageous on a small system where only one
console communicates with several controller processors. However, on
a large system where multiple consoles access the same controller, a
high advance request number can overwhelm the CP and controller
processor with excess messages.
NOTE: An advance request number of 1 or 2 will enable a console to

adapt to system slowdowns caused by communications across
PeerWays and loading of CP and controller processor images.
Figure 1.1.14 shows how the advance request number determines

outstanding data requests.

CC: 1-1-34
Refresh Advance
Rate Request Process Graphic
=1A--2
1 second 2
=1A--3
Queue =1A--53
(outstanding
messages) =1A--45
Message #1 =1B--54
PeerWay
CONTROLLER Message #2 =1B--45
=31C--1
=31C--2
=31C--5
=31C--10
Process Graphic
=1A--2
Queue =1A--3
(outstanding
messages) =1A--53
Message #2 =1A--45
PeerWay
CONTROLLER Message #3
=1B--54
=1B--45
=31C--1
=31C--2
=31C--5
=31C--10
NOTE:
D The specified advance request allows 2 outstanding messages.
D As each outstanding message is answered, the queue frees up space for a new
message.
D The screen refresh rate is 1 second. The process graphic must receive data for all
links before it can begin a new refresh cycle.
Figure 1.1.14. Advance Request Concept

CC: 1-2-1
Section 2:
Configuring Color
Command console screen colors are configurable. The Master Color

Selection screen is used to configure the foreground and background
color combinations used in the system. The Color Configuration
screens are used to assign the color combinations to system display
components such as alarms, variables, and screen titles.
This section describes how to configure the Master Color Selection

screen and Color Configuration screens.
RS3: Configuring Operating Characteristics Configuring Color

CC: 1-2-2
Master Color Selection Screen
The background/foreground color combinations are configured on the

Master Color Selection screen. Figure 1.2.1 shows an example of a
Master Color Selection screen with default colors.
- To call up, type: - To access other screens, type:

D CCP [ENTER] at the command line. D [PAGE AHEAD] to see the first Color
D [PAGE AHEAD] from the last Color Configuration.
Configuration. D [PAGE BACK] to see the last Color
D [PAGE BACK] from the first Color Configuration.
Configuration.
A color combination is configured as foreground color (the

text color) and background color (the screen color). Sixteen
color combinations can be configured. Background colors
must be chosen from the configured foreground colors. As an Color intensity is adjusted for a high,
example, blue cannot be used as a background color unless med, or low level. Each foreground
blue is configured as one of the sixteen foreground colors. color has an individual intensity
In addition to the colors listed on the screen, these colors are adjustment. The background
also available: intensity of a color matches the
foreground intensity of that color.
blue--2 cyan--2 salmon--2 aqua--2 orange--2
MASTER COLOR SELECTION 14-Jul-92 10:11:05

Foreground Background Foreground Background
1 Þwhite Þhigh Þblack Þlow 9 Þbrown Þhigh Þblack low
2 Þgreen Þhigh Þblack low 10 Þlt green Þhigh Þblack low
3 Þblue Þhigh Þblack low 11 Þyellow Þhigh Þblack low
4 Þcyan Þhigh Þblack low 12 Þaqua Þhigh Þblack low
5 Þmagenta Þhigh Þblack low 13 Þgray Þhigh Þblack low
6 Þorange Þhigh Þblack low 14 Þtan Þhigh Þblack low
7 Þsalmon Þhigh Þblack low 15 Þred Þhigh Þblack low
8 Þpurple Þhigh Þblack low 16 Þblack Þlow black low
CONFIG 3
Figure 1.2.1. Master Color Selection Screen

CC: 1-2-3
Color Configuration Screens
Color Configuration screens are used to assign color combinations to

system display components, such as alarm messages and console
screen titles. Figure 1.2.2 shows an example of a Color Configuration
screen. Table 1.2.1 describes the system display components on the
Color Configuration screens.

D CCU [ENTER] at the command line. D [PAGE AHEAD] to see other Color
D [PAGE AHEAD] from Master Color Selection. Configuration screens.
D [PAGE BACK] to see Master Color
Selection.
The color palette is shown on every Color Colors are assigned or changed in the
Configuration screen as a reference. ”Color” field. In this example, all
advisory alarms are assigned color
combination 11n, yellow text on a black
The Color Usage list changes for background.
each Color Configuration screen.
COLOR CONFIGURATION 14-Jul-92 10:30:45

Color Usage Color
Normal Reverse
1n white 1r black Date Þ2n
2n green 2r black
3n blue 3r black Default Values Þ2n
4n cyan 4r black
5n magenta 5r black Cursor/Prompt/Entry Þ10n
6n orange 6r black
7n salmon 7r black Events Þ2n
8n purple 8r black
9n brown 9r black System Alarms Þ1n
10n lt green 10r black
11n yellow 11r black Advisory Alarms Þ11n
12n aqua 12r black
13n gray 13r black Critical Alarms Þ15n
14n tan 14r black
15n red 15r black Hardware Alarms Þ5n
16n black 16r black
Batch Alarms Þ6n
CONFIG 3
Figure 1.2.2. Color Configuration Screen

CC: 1-2-4
Table 1.2.1. Color Configuration Screen Fields
Color Usage Field Name Description Default Color
1st screen
Date Date displayed in the upper right corner of screen. 2n
Default Values Enterable fields on the console screens. 2n
Cursor/Prompt/Entry Cursor. 10n
Events Operator logs, event lists. 2n
System Alarms System alarm messages. 1n
Advisory Alarms Advisory process alarm messages. 11n
Critical Alarms Critical process alarm messages. 15n
Hardware Alarms Hardware alarm messages. 5n
Batch Alarms Batch alarm messages. 6n
2nd screen
Process Variables The A input of a ControlBlock. 2n
Setpoints The B input of a ControlBlock. 4n
Remote Setpoints The C input of a ControlBlock. 8n
Feed Forward The D input of a ControlBlock. 14n
Output Value The Q output of a ControlBlock. 6n
Input E The E input of a ControlBlock. 2n
Input F The F input of a ControlBlock 2n
Input G The G input of a ControlBlock. 2n
Input H The H input of a ControlBlock. 2n
3rd screen
Auto Mode Auto mode on blocks. 2n
Manual Mode Manual mode on blocks. 2n
Remote Mode Remote mode on blocks. 2n
Local Mode Local mode on blocks. 2n
Computer Mode DDC or Comp SP mode on blocks. 2n
Trend Color 1 Color 1 on all trend group displays. 5n

CC: 1-2-5
Table 1.2.1. Color Configuration Screen Fields (continued)
4th screen
Continuous Function Not used. 9n
Discrete Function Not used. 13n
Sub--Title Color Group titles on unit and overview operating displays. 6n
Message--pair Color 1 C1 on a STD or a User Message Pairs screen. 2n
5th screen
Outline color for a selected key on the keypad of the

Arbitrary Color 2n
Display Buttons screen.
I/O Block Mode 1 Not used. 1n
Screen Titles The name of the console screen. 8r
Report configuration fields on a Report Configuration

Report Color 1 4n
screen.
Report Color 2 Report body on a Report Configuration screen. 12n
Report Color 3 Window on a Report Configuration screen. 11n
Report Color 4 Not used. 7n
6th screen
Graphics View Background Background on a Process Graphic screen. 4n
Graphics View Select Outline Outline of the selected Process Graphic screen. 6n
Graphics Config Background Grid on the Process Graphic Generation screen. 10n
Graphics Config Menu

Menu window on the Process Graphic Generation screen. 11n
Window

CC: 1-2-6
Graphics Config Area Background color on the Process Graphic Generation

11r
Background screen.
7th screen
Batch Program Batch program line after it has been entered. 1n
Batch Error An incorrect line entry. 15r
Batch Modified Batch line currently being typed. 11r
Batch End End of the batch script. 3r
Batch Current Line Currently executing batch line. 4r
Comments of batch script. This entry only takes effect

when the Batch Program color is 1r. If the Batch
Batch Comments 6n
Program color is anything else, then the batch comments
are the same color as the Batch Program color.
8th screen
SQC Background Background of an SQC chart. 16n
SQC Upper Limit Upper limit lines on an SQC chart. 2n
SQC Lower Limit Lower limit lines on an SQC chart. 2n
SQC Center Limit Centering limit and range limit lines on an SQC chart. 2n
SQC Points Points on an SQC chart. 1n
SQC Line (Pt to Pt) Plotted line on an SQC chart. 15n
SQC Spec Limits Spec limits on an SQC chart. 1n
9th screen
Material Hist Color1 The 1st point on a Material History Display. 4n
Material Hist Color2 The 2nd point on a Material History Display. 11n
Material Hist Color3 The 3rd point on a Material History Display. 15n
Material Hist Color4 The 4th point on a Material History Display. 2n

CC: 1-2-7
10th screen
ABC Icon Complete Execution of recipe icon complete. 2n
ABC Icon Active Currently executing recipe icon. 11n
ABC Icon Not Started Recipe icon has not been executed. 4n
ABC Icon Error A recipe icon runtime error. 15n
ABC Icon Skipped Recipe icon skipped without executing. 12n
ABC Icon Highlight Recipe icon highlighted with [SELECT] key. 1n
ABC Static Node Mark Recipe execution complete up to mark. 15n
ABC Block Step Mark Recipe execution blocked at mark. 6n
11th screen
Inhibit Alarms Block tags that are inhibited at the block level. 7n
Disable Alarms Block tags in alarm areas that are disabled. 13n
Suppressed Alarms Block tags and alarms that are suppressed. 12n
Plant Unit Plant unit numbers on Plant Unit Configuration screen. 2n

CC: 1-2-8
Hints for Configuring Colors
This section discusses problems you may have when configuring

colors.
- Why can’t I get black as a background color?

On the Master Selection screen, black must be configured as a
foreground color in order to use it as a background color.

CC: 1-3-1
Section 3:
Configuring Operating Displays
This section shows how to configure operating displays. Operating

displays contain ControlBlock faceplates, which facilitate operator
control and monitoring of processes. A faceplate often represents a
control loop.
D Group displays contain up to 8 faceplates. Plant processes can
be controlled and monitored from group displays.
D Unit displays contain up to 4 groups (up to 32 faceplates). Plant
processes can only be monitored from unit displays.
D Overview displays contain up to 2 units (up to 64 faceplates).
Plant processes can only be monitored from unit displays.
RS3: Configuring Operating Characteristics Configuring Operating Displays

CC: 1-3-2
Configuring Group Displays
D Group display titles are configured on the Group Directory

screen.
D Groups are configured on the Group Display screens.
Group Directory Screen
The Group Directory screen shows the list of group displays. Group
display titles must be configured on the Group Directory screen.
Figure 1.3.1 gives an example of a Group Directory screen.

D GD: [ENTER] at the command line. D [PAGE AHEAD] and [PAGE BACK] to see
other directory pages
D [SELECT] on group title to see Group
Display
D Groups 1--80 for MiniConsoles; D A title can contain up to 20 characters,

groups 1--200 for command consoles. including spaces.
D Group titles 71--80 on MiniConsoles D If no title is listed, “Group #” is
and 181--200 on command consoles displayed at the top of the Group
can be configured with an operator Display screen.
key. D To delete a title, press [ENTER].
GROUP DIRECTORY 25-Jul-92 12:20:11

Group Title Group Title Page 1
1 ÞPLANT MASTER 11 Þ
2 Þ1 BOILER CONTROL 12 Þ
3 Þ2 BOILER CONTROL 13 Þ
4 Þ8 STOKER CONTROL 14 Þ
5 Þ2 FUEL CONTROL 15 Þ
6 Þ 16 Þ
7 Þ 17 Þ
8 Þ 18 Þ
9 Þ 19 Þ
10 Þ 20 Þ
CONFIG 1
Figure 1.3.1. Group Directory Screen

CC: 1-3-3
Group Display Screen
A group display contains up to eight ControlBlock faceplates. Plant

processes can be monitored and controlled from a Group Display
screen. Figure 1.3.2 shows an example of a Group Display screen.
You can label each faceplate on a group display with a 16--character

tag. Tags that are longer than 8 characters appear on two lines on this
screen.

D G: (group #) [ENTER] at the command line D [PAGE AHEAD] and [PAGE BACK] to see
D G [ENTER] at the command line from a other Group Displays
block configuration screen D [SELECT] on faceplate to see block
D [SELECT] from group on Group Directory, faceplate screen
Unit Display, or Overview Display
Group faceplates are added

and deleted in the Tag field.
2: MIX 25-Jul-92 12:17:38

Tag Þ Þboiler Þ Þ Þ Þ Þ
Þ Þcontrol Þ ÞKCB-MC Þ Þ ÞKCB-MC
Units TEMP OPERATOR .00
PV-A *405. start .00
LSP-B *410. stop .00
RSP-C --AUTO-- .00
FF-D start
stop
100
---------
75
on cfrm
50 off cfrm
tripped
25
-OUTPUT-
0 run .00
13.8 STOP
failed
AUTO OPERATOR OPERATOR
CONFIG 1
Figure 1.3.2. Group Display Screen

CC: 1-3-4
- To add a faceplate on a Group Display screen:

1. Cursor to the Tag field.
2. Type the tag or address of the faceplate according to Table 1.3.1.
3. Press [ENTER].
Table 1.3.1. Group Display Entries for Faceplates
Enter this in the

To get this faceplate...
“Tag” Field
Standard faceplate
----Continuous faceplate for continuous
function ControlBlocks tag or address
----Discrete faceplate for discrete function
ControlBlocks
Nonstandard faceplate
----Discrete faceplate for continuous
function ControlBlocks #tag or #address
----Continuous faceplate for discrete
function ControlBlocks
Continuous faceplate +tag or +address
Discrete faceplate --tag or --address
- To delete a faceplate on a Group Display screen:

1. Cursor to the faceplate so that it is highlighted.
2. Press [NEXT OPTION] or type “none”.
3. Press [ENTER].

CC: 1-3-5
Configuring Unit Displays
D Unit display titles are configured on the Unit Directory screen.

D Unit displays are configured on the Unit Display screen.
Unit Directory Screen
The Unit Directory screen lists Unit Displays. Unit display titles must be
configured on the Unit Directory. Figure 1.3.3 gives an example of a
Unit Directory screen.

D UD: [ENTER] at the command line. D [PAGE AHEAD] and [PAGE BACK] to see
other directory pages.
D [SELECT] on unit title to see Unit Display.
D A title can contain up to 20 characters,

including spaces.
D If no title is listed, “Unit #” is displayed
Units 1--80 for at the top of the Unit Display screen.
command consoles
D To delete a title, press [ENTER].
UNIT DIRECTORY 14-Jul-92 02:33:11

Unit Title Unit Title Page 1
1 ÞHeat & Preheat Zones 11 Þ
2 ÞSoak Zone & Misc Controls 12 Þ
3 ÞDesalination Control 13 Þ
4 ÞDesalination Startup 14 Þ
5 ÞDemethanizer Control 15 Þ
6 ÞINDUSTRIAL POWER DEMO 16 Þ
7 Þ 17 Þ
8 Þ 18 Þ
9 Þ 19 Þ
10 Þ 20 Þ
CONFIG 3
Figure 1.3.3. Unit Directory Screen

CC: 1-3-6
Unit Display Screen
A unit display contains up to four group displays on one screen. Tags

that are longer than 8 characters appear on two lines on this screen.
Figure 1.3.4 shows an example of a Unit Display screen.

D U: (unit #) [ENTER] at the command line. D [PAGE AHEAD] and [PAGE BACK] to see
other Unit Displays.
D [SELECT] on faceplate to see Group
D Type the group number in the “Group” Display.
field.
D To delete a group, press [NEXT OPTION]
or type “none”.
Unit #1 27-Jul-92 10:10:42

Group >1 Line 1 Tank 5
STACK 2 STACK 2 STACK 2 STACK 2 STACK 2
VALVE E1 MCC-E1 Sensor E VCC-E2 VALVE E2
| run | | open | |
| STOP | | close | |
| failed | | failed | |
STACK 2 STACK 2 STACK 2 STACK 2 STACK 2 STACK 2 STACK 2 STACK 2
VALVE F1 MCC-F1 Sensor F VCC-F2 VALVE F2 VALVE F3 VALVE F4 VALVE F5
| run | | open | | | |
| STOP | | close | | | |
| failed | | failed | | | |
STACK 2 STACK 2
VALVE G1 MCC-G1
| run |
| STOP |
| failed |
.
VALVE H1 MCC-H1 Sensor H VCC-H2 VALVE H2
| run | | open | |
| STOP | | close | |
| failed | | failed | |
FULL CONFIG 1
Figure 1.3.4. Unit Display Screen

CC: 1-3-7
Configuring Overview Displays
D Overview display titles are configured on the Overview Directory

screen.
D Overview displays are configured on the Overview Display
screen.
Overview Directory Screen
The Overview Directory allows you to configure titles for Overview

Displays. Figure 1.3.5 shows an example of an Overview Directory
screen.

D OD: [ENTER] at the command line. D [PAGE AHEAD] and [PAGE BACK] to see
other directory pages.
D [SELECT] on overview title to see Overview
Display.
D A title can contain up to 20 characters, including
spaces.
D If no title is listed, “Overview #” is displayed at
Overviews 1--80 for the top of an Overview Display screen.
command consoles. D To delete a title, press [ENTER].
OVERVIEW DIRECTORY 18-Jul-92 07:33:31

Overview Title Overview Title Page 1
1 ÞReheat Furnace Overview 11 Þ
2 ÞDesalination Overview 12 Þ
3 ÞDemethanizer Overview 13 Þ
4 Þ 14 Þ
5 Þ 15 Þ
6 Þ 16 Þ
7 Þ 17 Þ
8 Þ 18 Þ
9 Þ 19 Þ
10 Þ 20 Þ
CONFIG 2
Figure 1.3.5. Overview Directory Screen

CC: 1-3-8
Overview Display Screen
An overview display monitors group displays by configuring unit

displays. Tags that are longer than 8 characters appear on two lines on
this screen. Figure 1.3.6 shows an example of an Overview Display
screen.

D O: (overview #) [ENTER] at the command D [PAGE AHEAD] and [PAGE BACK] to see
line. other Overview Displays.
D [SELECT] on faceplate to see Group
Display.
D Type the unit number in the “Unit” field.
D To delete a group, press [NEXT
OPTION] or type “none”.
Overview #1 27-Jul-92 10:11:16

Unit >1 Unit #1
VALVE E1 MCC-E1 Sensor E VCC-E2 VALVE E2
| failed | | L| | | |
STACK 2 STACK 2 STACK 2 STACK 2 STACK 2 STACK 2
VALVE F1 MCC-F1 Sensor F VCC-F2 VALVE F2 Valve F3
| | | | | | | |
VALVE G1 MCC-G1 Sensor G VCC-G2 VALVE G2
| | | | | |
VALVE H2 MCC-H1 Sensor H VCC-H2 VALVE H2
L| failed | L| failed | L|
Unit >2 Unit #2
VALVE P1 MCC-P1 Timer P VCC-P2 VALVE P2
| failed | | | failed | |
VALVE Q1 MCC-R1 Timer Q VCC-Q2 VALVE Q2
L| | | | |
STACK 4 STACK 4
VALVE R1 MCC-R1
| |
VALVE S1 MCC-R1 Timer S VCC-S2 VALVE S2
| | | | |
FULL CONFIG 1
Figure 1.3.6. Overview Display Screen

CC: 1-4-1
Section 4:
Configuring Callup and Display Buttons
This section shows how to configure callup and display buttons to call
up group displays, graphic displays, reports, alarm lists, and other
information. Figure 1.4.1 shows the location of the callup and display
buttons on the Multitube Command Console keyboard.
Callup buttons
Display buttons
Figure 1.4.1. Multitube Callup and Display Buttons
RS3: Configuring Operating Characteristics Configuring Callup and Display Buttons

CC: 1-4-2
Configuring Callup Buttons
Callup buttons are configured on the Alarm Annunciation screen.

Figure 1.4.2 shows an example of an Alarm Annunciation screen.
You configure commands, assign them to callup buttons, and configure

alarm annunciation characteristics for them.
The Callup Buttons screen is useful for testing and troubleshooting

callup buttons. See the “Callup Buttons Screen” on page 1-4-7 for
more information.

D AAC [ENTER] at the command line. D [PAGE AHEAD] to see other commands.
D [EXCH] from Callup Buttons. D [EXCH] to see Callup Buttons.
To access a command number, enter the

number in the “No.” field.
ALARM ANNUNCIATION 02-Aug-92 12:45:32
No. COMMAND Push

Button Associated Unit/Area/Block Ad-
dresses
Þ1 Þ
Þ Þ Þ
LAMP
Þ Þ Þ
Þ Þ
Þ Þ
Þ Þ
Þ Þ
Þ Þ
Þ Þ
Þ Þ
Þ
None
2 LAMP
YES
Figure 1.4.2. Alarm Annunciation Screen

CC: 1-4-3
Configuring a Command
A command is a set of keystrokes that is executed from the command

line when the associated callup button is pressed. You configure the
command in the “Command” field on the Alarm Annunciation screen.
Some command examples are listed in Table 1.4.1.
You can configure special commands to perform specific functions.

These special commands are listed in Table 1.4.2.
Table 1.4.1. Command Examples
Command Result
G:1* Calls up group #1.
PG:,Boiler * Calls up the process graphic Boiler.
RR:,Daily * Calls up the report Daily.
Table 1.4.2. Special Commands
Special Characters Description
* Represents the [ENTER] button.
#(block input) Changes the status of an input.

For example, the command ”#FIC--101/@a” changes the input FIC--101/@a to
its opposite state. This command might be used as a fast way to stop
equipment in case of an alarm.
Used at the beginning of a command to prevent the keystrokes from being

executed on the command line.
~ Can be used to configure callup buttons as individual keyboard keys. For
example, ~K would cause a callup button to insert the letter K wherever the
cursor happened to be on the screen when the button was pressed.
#ÙC Performs a console restart.
#ÙH Moves the cursor to the left.
#ÙJ Moves the cursor down.
#ÙK Moves the cursor up.
#ÙL Moves the cursor to the right.

CC: 1-4-4
Configuring a Callup Button Number
You can assign a callup button to a configured command. When the

callup button is pressed, the command is executed.
D You use the “Push Button” field on the Alarm Annunciation
screen to assign a callup button to a command.
D The callup button number consists of two numbers separated by
a period. The first number specifies the bank of callup buttons.
The second number specifies the number of the button on the
bank.
D The callup button bank numbering is also shown on the Callup
Buttons screen.
Figure 1.4.3 shows examples of callup button numbers.
If “None” is entered in the “Push Button” field, the command is executed

only when a block listed in the Associated Block Addresses field is in
alarm, “LampÞYes” is configured, and the [ACTIVE ALARM] button is
pressed.
Button 1.17 Button 2.6
RS3
FISHER--ROSEMOUNT
Figure 1.4.3. Option Keyboard Callup Button Example

CC: 1-4-5
Configuring Alarm Annunciation
D Blocks, plant units, and alarm areas can be configured in the

“Associated Unit/Area/Block Addresses” field on the Alarm
Annunciation screen. Examples are shown in Table 1.4.3.
D If a configured address is in alarm and “LampÞYes” is
configured, then the callup button LED lights. If the alarm is
unacknowledged, the LED also blinks.
D If a configured block is in alarm, “LampÞYes” is configured, and
you press [ACTIVE ALARM], the configured command is
executed. (Remember that the [ACTIVE ALARM] key calls up
screens according to time of alarm.)
Figure 1.4.4 shows an example of a callup button configuration.
Table 1.4.3. How to Configure Alarm Annunciation
For example:
To configure.. Enter...
Type... And it appears as...
the block tag LI--101 LI--101

a block or or or
address =2C--22 =2C--22
a plant unit the plant unit number 4 #4
an alarm area the alarm area name Boiler $Boiler

CC: 1-4-6
If one of the configured blocks is in alarm,

If you press callup button 1.1, the LED on callup button 1.1 lights.
Group Display #5 is called up.
ALARM ANNUNCIATION 02-Aug-92 12:45:32
No. COMMAND Push Associated Unit/Area/Block Addresses

Button
Þ1 ÞG:5* Þ=2C-3 Þ=2C-5
Þ1.1
LAMP Þ=2C-6 Þ=2C-7
Þ Þ=2C-10 Þ=2C-12
Þ Þ
Þ Þ
Þ Þ
Þ Þ
Þ Þ
Þ Þ
2 None
LAMP
YES
Figure 1.4.4. Alarm Annunciation Screen Example

CC: 1-4-7
Callup Buttons Screen
The Callup Buttons screen shows the commands that are configured for
the buttons. The callup button commands are assigned using the Alarm
Annunciation screen. Figure 1.4.5 shows an example of a Callup
Button screen with field descriptions.
- - To access other screens, type:

To call up, type:
D CCB [ENTER] at the command line. D [PAGE AHEAD] to see other commands for
callup buttons keyboard 1 and to see
D [EXCH] from Alarm Annunciation. commands for other callup buttons
keyboards.
D [EXCH] to see Alarm Annunciation.
D The box on the left shows the callup
D Cursor to button number on left or right,
buttons numbering scheme. The callup
[SELECT], then [EXCH] to call up Alarm
button number corresponds to the “Push
Annunciation for that button.
Button” field on the right.
D If you cursor to a number and press D The “Command” field shows the
[ENTER], the configured command is commands that are configured for the
executed. callup buttons. Press [PAGE AHEAD] to
D If you cursor to a number and press display more buttons and to see other
[SELECT], the number appears at the top callup buttons keyboards.
of the right column. D If you cursor to a number and press
[SELECT], the number appears at the top
of the column.
CALLUP BUTTONS 02-Aug-92 16:43:22
OPTIONS Set No. 1 Push

Button COMMAND
1 9 17 25 1 G:1*
2 G:2*
2 10 18 26 3 G:7*
4
3 11 19 27 5
6 TAFC-101*BD*
4 12 20 28 7
8
5 13 21 29 9 PG:,BOILER*
10 PG:,BATCH*
6 14 22 30 11
12
7 15 23 31 13
14 CFS*
8 16 24 32 15
16
(MORE)
CONFIG 3
Figure 1.4.5. Callup Buttons Screen

CC: 1-4-8
Display Buttons Screen
The Display Buttons screen is used to configure commands for the

display buttons of a Multitube Command Console. The display buttons
are located at the left side of the Operator keyboard (see Figure 1.4.1).
The display buttons function the same as the callup buttons, except that
they have no lights for alarm annunciation. Figure 1.4.6 shows an
example of a Display Buttons screen.

D CDB [ENTER] at the command line D None
D The box on the left shows the display - To configure a command for a display
buttons numbering scheme. The callup button:
button number corresponds to the 1. Cursor to the “Button” field, type the button
“Button” field on the right. number, and press [ENTER].
D If you cursor to a number and press or
[ENTER], the configured command is
executed. Cursor to the display number on the left side
of the display and press [SELECT].
D If you cursor to a number and press
[SELECT], the button number appears at 2. Enter the desired command. For information
the top of the column on the right. about commands, see the “Configuring a
Command” heading on page 1-4-3.
DISPLAY BUTTONS 02-Aug-92 16:43:22
Button COMMAND
Þ7 Þ
STATUS
1
P Way C F C B 2 o:
3 td:
DISPLAYS 4 el:*
5 del*
6 sp*
7
1 7 13 8 u:
9 tg:
2 8 14 10 ol*
11. ddp*
3 9 15 12 da*
13
4 10 16 14 g:
15 pg:,
5 11 17 16 rr:,
17 ~%
6 12
Figure 1.4.6. Display Buttons Screen

CC: 1-4-9
Hints for Callup Buttons and Display Buttons
This section discusses some problems you might have when

configuring callup buttons and display buttons, along with some
configuration tips.
- After I programmed a callup button, I tried to use it. When I

push the callup button, nothing happens and the Button Not
Programmed message appears.
Remember that the “Push Button” field on the Alarm Annunciation
screen determines which callup button is assigned to a command.
The “Command” field does not perform this function.
An easy way to see what command is configured for a button is to
go to the Callup Buttons screen, cursor to the picture on the left of
the button you want, press [SELECT] and then press [EXCH]. The
Alarm Annunciation appears with the command that contains that
callup button at the top of the display.
- I have configured a command to callup a group display, but
some of the blocks in the group display are not listed in the
“Associated Addresses” field on the Alarm Annunciation
screen.
If you have added or deleted blocks from a group display, the
changes are not reflected in the “Associated Addresses” field. You
can update the field by deleting the command and reentering it.

CC: 1-4-10
Configuration Tips
- Tips for keeping track of callup button numbers and command

numbers
It is a good idea to keep the command number and the callup button
number consistent. For example, assign callup button 1.1 to
command 1, callup button 1.2 to command 2, and so on.
- How to configure a command without assigning a callup button
to it
If you want to configure a command without a callup button,
configure a command number larger than the largest callup button
number on your console. Each console has a few more commands
that can be configured than callup buttons. The command is then
executed only when a block listed in the “Associated Addresses”
field is in alarm, “LampÞYes” is configured, and the [ACTIVE
ALARM] key is pressed. (Remember that the [ACTIVE ALARM] key
calls up screens according to time of alarm.)
- If you configure commands to call up group displays
When you configure a command to call up a group display, the
blocks that are currently in that group display are automatically put
in the “Associated Addresses” field.
- If you change blocks in a group display after configuring a
command to call up that group display
If you have added or deleted blocks from a group display, the
changes are not reflected in the “Associated Addresses” field. You
can update the field by deleting the command and reentering it.
- If you change the “Associated Addresses” field entries for a
command that calls up a group display
If you alter the “Associated Addresses” field entries for a command
that calls up a group display, you must be careful. The blocks must
appear in the same order in the “Associated Addresses” field as they
do on the group display.
You can delete blocks from the “Associated Addresses” field, but the
ones that remain must be in the same order as they appear on the
group display.

CC: 1-5-1
Section 5:
Configuring Message Pairs
This section shows how to configure message pairs. Each console

stores text items called message pairs. Message pairs are used
throughout the system to represent discrete states. A message pair
consists of one message for the on (1) state and one message for the
off (0) state of a discrete variable. Figure 1.5.1 shows an example of a
message pair.
OPERATOR
> start
> stop
---AUTO--
START When the discrete variable
stop has a 1 state, the true
message is displayed.
---------
ON CFRM
off cfrm
tripped
-OUTPUT- STD MESSAGE PAIRS
RUN
stop
failed Pair True Atr False Atr Pair
OPERATOR *21 ÞCONFIRM ÞC4 Þconfirm ÞC1 *31
> start
> stop *22 ÞON CFRM ÞC4 Þon cfrm ÞC1 *32
---AUTO-- *23 ÞLO CFRM ÞC4 Þlo cfrm ÞC1 *33
start *24 ÞHI CFRM ÞC4 Þhi cfrm ÞC1 *34
STOP
*25 ÞFWD CFRM ÞC4 Þfwd cfrm ÞC1 *35
---------
*26 ÞREV CFRM ÞC4 Þrev cfrm ÞC1 *36
on cfrm When the discrete
OFF CFRM variable has a 0 state, *27 ÞOFF CFRM ÞC4 Þoff cfrm ÞC1 *37
tripped
the false message is *28 ÞOPN CFRM ÞC4 Þopn cfrm ÞC1 *38
-OUTPUT- displayed.
run *29 ÞCLS CFRM ÞC4 Þcls cfrm ÞC1 *39
STOP
failed *30 ÞRUN CFRM ÞC4 Þrun cfrm ÞC1 *40
Figure 1.5.1. Faceplates and Message Pairs
RS3: Configuring Operating Characteristics Configuring Message Pairs

CC: 1-5-2
Standard and User Message Pairs
The system includes standard message pairs and user message pairs.
Table 1.5.1 lists message pair characteristics.
Table 1.5.1. Message Pair Characteristics
Item Standard Message Pairs User Message Pairs
Quantity 100 155
Configurable? Yes Yes
Preconfigured?* All Some
Max # of characters 8 8
* Preconfigured message pairs are used in the system to represent discrete states. You should take care
when changing preconfigured message pairs so that unwanted system changes do not occur.

CC: 1-5-3
The Message Pairs Screens
Standard message pairs are configured on the Std Message Pairs

screens (see Figure 1.5.2). User message pairs are configured on the
User Message Pairs screens (see Figure 1.5.3).
The preconfigured standard message pairs are listed in Table 1.5.2.

The preconfigured user message pairs are listed in Table 1.5.3.
User message 101, called “Tag”, can be assigned on a Discrete Links

screen as a message on input or output blocks. For an example of
using this message, see “Hints for Using Message Pairs” on page
1-5-9.
- To configure non-- English characters in a message pair:
D Scroll through the foreign character options by typing a character,
then pressing the [CTRL] and [A] keys simultaneously.

CC: 1-5-4

D MPS [ENTER] at the command line. D [PAGE AHEAD] and [PAGE BACK] to see
other standard message pairs and user
message pairs.
Standard message pairs are numbered

1 -- 100 and are identified with an asterisk (*).
Attributes C1 through C6 determine the color

(text and background) of the message. True and False correspond to
Attributes are assigned on the Color the on/off states of a discrete
Configuration screen. action.
STD MESSAGE PAIRS 18-Jul-92 11:35:11

Pair True Atr False Atr Pair True Atr False Atr
*1 ÞON ÞC4 ÞOFF ÞC1 *11 ÞAUTO ÞC1 ÞOPERATOR ÞC5
*2 ÞSTART ÞC4 Þstart ÞC1 *12 ÞENABLE ÞC4 Þenable ÞC1
*3 ÞLOW ÞC4 Þlow ÞC1 *13 ÞPUMP ÞC4 Þpump ÞC1
*4 ÞHIGH ÞC4 Þhigh ÞC1 *14 ÞAGITATE ÞC4 Þagitate ÞC1
*5 ÞFORWARD ÞC4 Þforward ÞC1 *15 ÞTRANSFERÞC4 Þtransfer ÞC1
*6 ÞREVERSE ÞC4 Þreverse ÞC1 *16 ÞDRAIN ÞC4 Þdrain ÞC1
*7 ÞSTOP ÞC5 Þstop ÞC2 *17 ÞWASH ÞC4 Þwash ÞC1
*8 ÞOPEN ÞC4 Þopen ÞC1 *18 ÞPROCEED ÞC4 Þproceed ÞC1
*9 ÞCLOSE ÞC5 Þclose ÞC2 *19 ÞDISABLE ÞC5 Þdisable ÞC2
*10 ÞRUN ÞC4 Þrun ÞC1 *20 ÞDISABLEDÞC5 Þdisabled ÞC2
CONFIG 1
Figure 1.5.2. Standard Message Pairs Screen

CC: 1-5-5

D MPU [ENTER] at the command line. D [PAGE AHEAD] and [PAGE BACK] to
see other user message pairs and
standard message pairs.
User message pairs are numbered 1--155.
Attributes C1 through C6 determine the color

(text and background) of the message. True and False correspond to
Attributes are assigned on the Color the on/off states of a discrete
Configuration screen. action.
USER MESSAGE PAIRS 18-Jul-92 11:35:11

Pair True Atr False Atr Pair True Atr False Atr
1 Þ ÞC1 Þ ÞC1 11 Þ ÞC1 Þ ÞC1
CONFIG 1
Figure 1.5.3. User Message Pairs Screen

CC: 1-5-6
Table 1.5.2. Preconfigured Standard Message Pairs
Standard Standard
Message True False Message True False
Pair (on) (off) Pair (on) (off)
Number Number
*1 ON OFF *26 REV CFRM rev cfrm
*2 START start *27 OFF CFRM off cfrm
*3 LOW low *28 OPN CFRM opn cfrm
*4 HIGH high *29 CLS CFRM cls cfrm
*5 FORWARD forward *30 RUN CFRM run cfrm
*6 REVERSE reverse *31 SHUTDOWN shutdown
*7 STOP stop *32 INTERLOK interlok
*8 OPEN open *33 RESET reset
*9 CLOSE close *34 POSN ’A’ posn ’A’
*10 RUN run *35 POSN ’B’ posn ’B’
*11 AUTO OPERATOR *36 ’A’ CFRM ‘A’ cfrm
*12 ENABLE enable *37 ’B’CFRM ’B’ cfrm
*13 PUMP pump *38 OPERATOR operator
*14 AGITATE agitate *39 ----AUTO---- ----auto----
*15 TRANSFER transfer *40 STATUS status
*16 DRAIN drain *41 FAILED
*17 WASH wash *42 ON FAIL on fail
*18 PROCEED proceed *43 LO FAIL lo fail
*19 DISABLE disable *44 HI FAIL hi fail
*20 DISABLED disabled *45 FWD FAIL fwd fail
*21 CONFIRM confirm *46 REV FAIL rev fail
*22 ON CFRM on cfrm *47 OFF FAIL off fail
*23 LO CFRM lo cfrm *48 OPN FAIL opn fail
*24 HI CFRM hi cfrm *49 CLS FAIL cls fail
*25 FWD CFRM fwd cfrm *50 RUN FAIL run fail

CC: 1-5-7
Table 1.5.2. Preconfigured Standard Message Pairs (continued)
Standard Standard
Message True False Message True False
Pair (on) (off) Pair (on) (off)
Number Number
*51 IGNORE ignore *76 PMP CFRM pmp cfrm
*52 FAILED failed *77 DRN CFRM drn cfrm
*53 SW FAIL sw fail *78 WSH CFRM wsh cfrm
*54 TRIPPED tripped *79 SETPOINT setpoint
*55 LOCKOUT lockout *80 NEXT next
*56 MCC OFF mcc off *81 ON off
*57 TRAVEL travel *82 ON off
*58 ABORT abort *83 STOP stop
*59 ABORTED *84 START stop
*60 NOT USED not used *85 RUN stop
*61 CLS TRP cls trp *86 RUN stop
*62 RUN TRP run trp *87 OPEN close
*63 RETRY LM retry lm *88 --OUTPUT-- --output--
*64 MCC ALRM mcc alrm *89 ALARM ok
*65 V TRAVEL v travel *90 ALARM ok
*66 FORWARD forward *91 ON OFF
*67 REVERSE reverse *92 ON OFF
*68 HOLD hold *93 START STOP
*69 HOLD *94 START STOP
*70 STATUS status *95 RUN STOP
*71 PROCEED *96 RUN STOP
*72 RUN *97 OPEN CLOSE
*73 ACTIVE active *98 OPEN CLOSE
*74 INACTIVE inactive *99 ALARM OK
*75 STP CFRM stp cfrm *100 ALARM

CC: 1-5-8
Table 1.5.3. Preconfigured User Message Pairs
User
True False
Message Pair
(on) (off)
Number
151 AUTOTUNE AutoTune
152 AUTOENTR AutoEntr
153 ADJ.GAIN adj.gain
154 ADJ. TI adj. Ti
155 ADJ. TD adj. Td

CC: 1-5-9
Hints for Using Message Pairs
This section discusses message pair configuration tips.
Configuration Tips
- How to configure non-- English characters in a message pair

Scroll through foreign character options by typing a character, then
pressing the [CTRL] and [A] keys simultaneously.
- How to configure a tag as a message pair
You can configure a block tag as a message pair by using user
message 101. You must configure the block as a discrete input or
output with a message pair of 101. The message pair for that input
or output then consists of the block tag. The tag is backlighted for
an on (1) condition and is not backlighted for an off (0) condition.

CC: 1-6-1
Section 6:
Configuring the Block Print Function
The block print function allows you to produce system documentation by

printing block configuration screens. The block print function is
configured on the Block Print Setup screen (see Figure 1.6.1).
Table 1.6.1 shows the Block Print Screen Setup screen fields.
- To perform a block print:
1. Call up the Block Print Setup screen.
2. Configure the fields as desired.
3. Cursor to the “Start Print” field and press [ENTER].
As the block print is performed, the block configuration screens
that are being printed appear on the CRT. Also, the message
“BP Busy” is displayed in the lower left of the display.
You cannot perform other tasks while the block print function is
active. However, the block print function can be stopped and
restarted at any time.
It may take several hours to print all block screens for a plant.
- To stop the block print:
D Press any console key.
- To restart the block print function:
1. Return to the Block Print Setup screen.
2. Cursor to the “Resume Print“ field and press [ENTER].
RS3: Configuring Operating Characteristics Configuring the Block Print Function

CC: 1-6-2

D BP [ENTER] at the command line. D None.
- To do a block print:
1. Cursor to the “First Block” field and type in the 3. To select field options, cursor to
block address or range of block addresses each field and press [NEXT
separated by a comma. OPTION]. Then, press [ENTER].
2. Press [ENTER]. The tags align themselves in
the appropriate columns.
BLOCK PRINT SETUP 21-Jul-92 08:00:58

Block
First Block, Last Block Faceplates Links Logic Alarms Ref:
1Þ =1A-1, =1A-5 Þboth Þboth Þyes Þyes Þno
2Þ =2A1, =2D-99 Þboth Þboth Þyes Þno Þno
3Þ =4A-1, =7H-99 Þboth Þboth Þyes Þno Þno
4Þ
5Þ
6Þ
7Þ
8Þ
9Þ
Start Print
CONFIG 4
4. Begin the block print function by

cursoring to the “Start Print” field. Press
[ENTER].
Figure 1.6.1. Block Print Setup Screen

CC: 1-6-3
Table 1.6.1. Block Print Setup Screen Fields
Field Description Entries
Specifies the blocks to be printed. Blocks can be referenced by

tag or address. Blocks can be listed singly (e.g., =1A--1) or in a Tag or address;
Block Range
range (e.g., =1A--1,=1A--5). Control blocks or input/output single or range
blocks can be printed.
Analog, Discrete,
Faceplates Specifies the block faceplates to be printed.
Both, Neither.
Analog, Discrete,
Links Specifies the block links that are printed.
Both, and Neither
Logic Specifies whether or not defined block logic steps are printed. Yes, No
Specifies whether or not block variable alarm configuration

Alarms Yes, No
screens are printed if the variables are in alarm.
Block Ref: Specifies whether or not block references are printed. Yes, No

CC: 1-7-1
Section 7:
Multinational Characters and Russian Console
The RS3 offers multinational characters and a Russian console option

for console software.
Multinational Characters
You can include multinational characters (such as à, é, ö, ñ, and ç) in

most user--entered text, such as in descriptors.
- To enter a multinational character:
1. Type the base character (the letter in ASCII closest to the
multinational character). For example, to get ñ, type n.
2. Use CTRL A to scroll through the options available for
multinational characters associated with the base character, until
the one you want appears.
NOTE: You cannot include multinational characters in block tags or in

reserved words such as in logic prologue. Multinational characters can
be used in logic prologue comments (text between quotation marks),
batch tags, batch comments, block descriptors, block input units,
message pairs, file descriptors, report text and banners, and text in
process graphics.
Russian Console
Fisher--Rosemount offers a Russian console. The field names,

messages, etc., are in Russian. You can enter text in fields in either
Cyrillic or Roman characters, and it is possible to toggle back and forth.
Similarly, you can issue commands on the command line with either
Russian or English mnemonics. Again, you toggle back and forth
between English and Russian. It is possible to be in English mode for
text entry and Russian for command line options, or vice versa, or in
English for both, or in Russian for both.
- To toggle between English and Russian text entry:
D [CTRL] [A] on a text--entry field.
- To toggle between English and Russian for commands:
D [CTRL] [A] in the HOME position (first row, first column).
RS3: Configuring Operating Characteristics Multinational Characters and Russian Console

CC: 1-7-2
Mixing Cyrillic and Roman in Screen Fields
Tags, block descriptors, and input units can be in either Cyrillic or

Roman characters. You can set these fields for either Cyrillic (Russian)
or Roman (English) on the second page of the Console Configuration
(CCC) screen. For example, you can select Roman for tags and Cyrillic
for the units and descriptors, or some other combination.
If you intend to mix Cyrillic and Roman, Fisher--Rosemount

recommends that you set up a uniform strategy for what items will be in
what character sets, throughout the PeerWay or plant. If a ControlFile
was configured with a console set with a specific combination of Cyrillic
and Roman options, that ControlBlock can only be viewed correctly on a
console set with the same combination of options. Otherwise, the
information will appear scrambled. (This scrambled display does not
affect controller functionality.)
NOTE:
D Logic prologue and block addresses must be in Roman
characters.
D Call--up buttons can be programmed in either Cyrillic or Roman.
Note that the call--up buttons will work only if the command line is
toggled to the same mode (Cyrillic or Roman) as the call--up
button.
Printer
To print Cyrillic in plain text mode you need a Fujitsu model DL2600 or
later. A Cyrillic font will be downloaded automatically at power up.
If the Cyrillic printer font is lost for any reason, the Cyrillic font can be
manually downloaded again using the reset field in the printer box on
the CCC screen. On the first [ENTER], the print output in the console
will clear and the system displays a message asking for an optional
second [ENTER] to start the actual font downloading to the printer.
RS3: Configuring Operating Characteristics Multinational Characters and Russian Console

RS3t
Chapter 2:
Process Graphics
Section 1: Introduction to Process Graphics . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1-1

How are Process Graphics Stored? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1-2
How are Process Graphics Created and Accessed? . . . . . . . . . . . . . . . . . . . . . . . 2-1-3
Creating a Process Graphic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1-4
Calling Up the Viewing Mode of a Process Graphic . . . . . . . . . . . . . . . . . . . . . 2-1-4
Calling Up the Configuration Mode of a Process Graphic . . . . . . . . . . . . . . . . . 2-1-6
Section 2: Process Graphics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-1

Creating Process Graphics Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-2
Object Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-5
How Objects Appear in Viewing and Configuration Modes . . . . . . . . . . . . . . . . . . 2-2-7
Creating Shapes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-9
Circles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-9
Boxes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-10
Triangles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-11
Arcs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-12
Lines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-13
Lines with Different Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-14
Shape Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-15
Library Symbols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-17
New Symbols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-19
Shapes that Fill Up in Response to a Block Variable . . . . . . . . . . . . . . . . . . . . . 2-2-21
Multicolor Shapes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-23
Tag, Blkdes, Mode Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-25
Character Form:
Links, Units, Disc Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-28
Graphic Form:
Hdev, Vdev, Ticbar Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-31
How the Hdev and Vdev Objects Are Displayed . . . . . . . . . . . . . . . . . . . . . . . . 2-2-33
How the Ticbar Object is Displayed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-35
Group, Unit, Overview Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-37
Displaying a Faceplate from a Process Graphic Object . . . . . . . . . . . . . . . . . . . . . 2-2-40
Creating Objects That Display Trend Information:
Trend Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-41
How the Trend Object is Displayed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-44
RS3: Process Graphics Contents

CC: ii
Creating Displayed Text:

Text Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-46
Displaying Alarms:
Alarm Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-48
Creating Data Entry Fields: Disc Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-53
Configuring The Appearance of Objects to Change, Depending on the
State of a Discrete Block Variable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-54
Configuration Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-56
Moving and Copying Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-56
Deleting Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-57
Stacking Objects—Top and Bottom Operations . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-58
Example of Stacking Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-59
Grouping Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-60
Grouping Objects—Area Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-61
Grouping Objects—Group and Join Operations . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-63
Joining Single Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-63
Joining Groups of Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-64
Grouping Objects—Merge Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-66
Using the Link Editor Field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-67
Splitting an Object from a Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-69
Undoing the Previous Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-70
Configuring Display Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-71
Process Graphics Fabric Coordinates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-71
Changing the Panning Limits and Origin Point . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-72
Creating Assists for Display Manipulation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-73
Objects that Call up Other Displays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-74
Objects that Call up Another Part of the Same Display . . . . . . . . . . . . . . . . . . 2-2-75
Display Targets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-77
Hiding Parts of the Display Using an Icon Object . . . . . . . . . . . . . . . . . . . . . . . . 2-2-79
Copying a Process Graphic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-82
Bface Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-83
Alarm Annunciation on Graphics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-85
Alarm Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-85
Icon Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-85
That Have Been Converted from Character Graphics . . . . . . . . . . . . . . . . . . . . . . 2-2-86
Section 3: Optimizing Graphics Performance . . . . . . . . . . . . . . . . . . . . . . . . . 2-3-1

Process Graphic Limits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3-2
Link Count Field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3-3
Using Funnel Blocks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3-4
Merging Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3-5
Other Methods of Optimizing Graphics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3-6
Preconfigured Process Graphics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3-7
Screen Refresh and Field Refresh . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3-8
Graphics Link Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3-9
Calling Up the Link Editor Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3-10
Procedure: Editing Link Addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3-11

CC: iii
List of Figures
Figure Page
2.1.1 Example of a Process Graphic Display Fabric . . . . . . . . . . . . . . . . . . . . 2-1-1
2.1.2 Process Graphics Folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1-2
2.1.3 Using [EXCH] to Move Between Viewing and
Configuration Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1-3
2.2.1 Creating a Process Graphics Object—Top Menu . . . . . . . . . . . . . . . . . . 2-2-2
2.2.2 Creating a Process Graphics Object—Object Menu . . . . . . . . . . . . . . . 2-2-3
2.2.3 Creating a Process Graphics Object—Edit Object Menu . . . . . . . . . . . 2-2-4
2.2.4 Viewing Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-7
2.2.5 Configuration Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-8
2.2.6 Creating a Circle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-9
2.2.7 Creating a Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-10
2.2.8 Creating a Triangle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-11
2.2.9 Creating an Arc . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-12
2.2.10 Creating a Line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-13
2.2.11 Edit Object Menu for the Line Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-14
2.2.12 Edit Object Menu for Shapes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-15
2.2.13 Adding a Library Symbol to a Process Graphic . . . . . . . . . . . . . . . . . . . 2-2-18
2.2.14 Creating a New Symbol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-20
2.2.15 Edit Object Menu for Creating a Shape that Fills Up in
Response to a Block Variable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-22
2.2.16 Examples of the Ways that Shapes Can Be Used . . . . . . . . . . . . . . . . . 2-2-22
2.2.17 Multicolor Shape and Edit Object Menu . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-23
2.2.18 Example of a Multicolor Shape with Edit Links Menu . . . . . . . . . . . . . . . 2-2-24
2.2.19 How the Tag, Blkdes, and Mode Objects Appear in
Configuration Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-26
2.2.20 Edit Object Menu for the Tag, Blkdes, and Mode Objects . . . . . . . . . . . 2-2-27
2.2.21 How the Link, Units, and Disc Objects Appear In
2.2.22 Edit Object Menu for the Link, Units, and Disc Objects . . . . . . . . . . . . . 2-2-30
2.2.23 How the Hdev, Vdev, and Ticbar Objects Appear in
2.2.24 How the Hdev and Vdev Objects Appear in Viewing Mode . . . . . . . . . . 2-2-33
2.2.25 Edit Object Menu for the Hdev, Vdev, and Ticbar Objects . . . . . . . . . . 2-2-34
2.2.26 How the Ticbar Object Appears in Viewing Mode . . . . . . . . . . . . . . . . . . 2-2-35

CC: iv
2.2.27 Edit Object Menu for the Hdev, Vdev, and Ticbar Objects . . . . . . . . . . 2-2-36
2.2.28 How the Group, Unit, and Overview Objects Appear in
2.2.29 Edit Object Menu for the Group, Unit, and Overview Objects . . . . . . . 2-2-39
2.2.30 Displaying a ControlBlock Faceplate from a Process
Graphic Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-40
2.2.31 How the Trend Object Appears in Configuration Mode . . . . . . . . . . . . . 2-2-41
2.2.32 Edit Object Menu for the Trend Object . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-42
2.2.33 How the Trend Object is Displayed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-44
2.2.34 Slidewire Feature of the Trend Object . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-45
2.2.35 Edit Object Menu for the Text Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-46
2.2.36 How the Alarm Object is Displayed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-48
2.2.37 Example of Alarm Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-49
2.2.38 Examples of Criteria Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-52
2.2.39 Example Data Entry Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-53
2.2.40 Configuring the Edit Object Menu for Conditional
Display of Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-54
2.2.41 Moving and Copying an Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-56
2.2.42 Deleting an Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-57
2.2.43 Stacking Objects Using the Top and Bottom Operations . . . . . . . . . . . . 2-2-58
2.2.44 Creating an Object Superimposed on Another Object . . . . . . . . . . . . . . 2-2-59
2.2.45 Joining Objects into Groups with the Area Operation . . . . . . . . . . . . . . 2-2-62
2.2.46 Joining Single Objects into Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-63
2.2.47 Joining Groups of Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-64
2.2.48 Joining Groups of Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-65
2.2.49 Merging a Group into a Permanent Thing Object . . . . . . . . . . . . . . . . . . 2-2-66
2.2.50 Using the LinkEd Option to Link an Area . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-67
2.2.51 Splitting an Object from a Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-69
2.2.52 Undoing an Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-70
2.2.53 Fabric Coordinates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-71
2.2.54 Changing a Panning Limit or the Origin Point . . . . . . . . . . . . . . . . . . . . . 2-2-72
2.2.55 Edit Object Menu for Pagefrwd and Pageback Objects for
Display Manipulation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-74
2.2.56 Use of Anchor Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-75
2.2.57 Edit Object Menu for Anchor Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-76
2.2.58 Example Use of Anchor Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-76
2.2.59 Example Use of Target Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-77
2.2.60 Edit Object Menu for Target Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-78
2.2.61 How the Icon Object is Displayed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-80

CC: v
2.2.62 Edit Object Menu for Icon Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-80

2.2.63 Copying a Process Graphic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-82
2.2.64 How the Bface Object Appears in Configuration Mode . . . . . . . . . . . . . 2-2-83
2.2.65 Edit Object Menu for the Bface Object . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-84
2.2.66 Configure Character Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-87
2.3.1 Using the Link Count Field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3-3
2.3.2 Funnel Block Concept . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3-4
2.3.3 Link Editor Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3-10

CC: vi
List of Tables
Table Page
2.2.1 Process Graphic Object Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-5
2.2.2 Screen Fields on the Edit Object Menu for Shape
Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-16
2.2.3 Objects that Display Block Information . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-25
2.2.4 Screen Fields on the Edit Object Menu for the Tag, Blkdes,
and Mode Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-27
2.2.5 Objects that Display Block Variable Information in
Character Form . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-28
2.2.6 Screen Fields on the Edit Object Menu for Link, Units,
and Disc Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-30
2.2.7 Objects that Display Block Variable Information in
Graphic Form . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-31
2.2.8 Screen Fields on the Object Edit Menu for the Hdev, Vdev,
and Ticbar Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-34
2.2.9 Screen Fields on the Edit Object Menu for the Hdev, Vdev,
and Ticbar Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-36
2.2.10 Objects that Display Faceplates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-37
2.2.11 Screen Fields on the Edit Object Menu for the Trend Object . . . . . . . . 2-2-43
2.2.12 Screen Fields on the Edit Object Menu for the Text Object . . . . . . . . . 2-2-47
2.2.13 Screen Fields on the Edit Object Menu for the Alarm Object . . . . . . . 2-2-50
2.2.14 Grouping Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-60
2.2.15 LinkEd Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-68
2.2.16 Display Manipulation Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-73
2.2.17 Screen Fields on the Edit Object Menu for Target Object . . . . . . . . . . . 2-2-78
2.2.18 Screen Fields on the Edit Object Menu for Icon Object . . . . . . . . . . . . . 2-2-81
2.2.19 Screen Fields on the Edit Object Menu for the Bface Object . . . . . . . . 2-2-84
2.3.1 Parameter Limits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3-2

CC: 2-1-1
Section 1:
Introduction to Process Graphics
A process graphic display is a pictorial representation of plant

conditions. It can show pictures of tanks, valves, pipes, and other
equipment, along with numerical and bar--graph representations of
current process data. A process graphic display can also allow
operators to enter data, change controller modes, and perform other
functions directly on the display.
You construct a process graphic display with objects, piecing them

together to build the desired features of the process graphic display.
Objects can be physical shapes, displays of current values, operator
entry fields, trend information, faceplates, and other items.
Each process graphic display is constructed on a fabric. The console

display can only show a portion of the process graphic fabric at a time,
as shown in Figure 2.1.1. You can move the trackball to see other
areas of the process graphic fabric.
The actual size of a process graphic display is limited by factors such as

the number and type of configured objects, the complexity of each
object, and the number of defined links.
Portion of fabric visible on screen
Figure 2.1.1. Example of a Process Graphic Display Fabric
RS3: Process Graphics Introduction to Process Graphics

CC: 2-1-2
How are Process Graphics Stored?
Process graphics are stored as files on the Command Console hard

disk. Each process graphic display has a unique file name and is
stored in the Process Graphics folder on the hard disk. Figure 2.1.2
shows the Disk Directory screen with the Process Graphics folder boxed
in.
When a Command Console is initially used, the Process Graphics folder

does not exist. The folder is created the first time that a process
graphic display is created.
DISK DIRECTORY 22-Feb-89 16:42:25

Console Node 32
Disk Name CC32 At Node 32 On Drive 1
Created 21-Oct-87 Capacity (bytes) 33554176
RemarksÞ
Folders on Disk
R R
Plant Prog Console Prog
1 10 2 4
Plant Config Trend Data Console Config Report Config
12 12 58
Reports Process Graphics Process Symbols

CONFIG 1
Figure 2.1.2. Process Graphics Folder

CC: 2-1-3
How are Process Graphics Created and Accessed?
A process graphic can be displayed in two modes: viewing mode and

configuration mode. The [EXCH] key can be used to transfer from one
mode to the other, as shown in Figure 2.1.3.
D Viewing mode is used to display the process graphic for plant
operation.
D Configuration mode is used to create and modify the process
graphic.
This section contains procedures for creating and calling up process

graphic displays. For more information about calling up and using
graphic displays, see OP: 3.
Viewing (Operating) Mode
Graphics Viewing
Configuration Mode
Process Graphic Generation
EXCH
Figure 2.1.3. Using [EXCH] to Move Between Viewing and Configuration Modes

CC: 2-1-4
Creating a Process Graphic
- To create a process graphic, type:

PGG (volume,filename) [ENTER]
If the volume that the Process Graphic resides on is the default volume
(usually the console disk drive), the volume entry can be omitted. For
information about default volumes, see the DT Manual.
If the process graphic does not exist on the volume, the following
message appears at the top of the screen, and a blank Process Graphic
Generation screen appears:
Requested Filename Not Found
The process graphic has now been created and may be configured.
Leaving the configuration display writes the process graphic
configuration to disk.
Calling Up the Viewing Mode of a Process Graphic
- To call up the viewing mode display of a process graphic:

D From the volume containing the graphic:
1. Type:
DD: [ENTER]
The Disk Directory screen for the console hard disk appears.
2. Cursor to the Process Graphics folder and press [SELECT]. The
Process Graphics Directory screen for the Process Graphics
folder appears.
3. Cursor to the desired process graphic file name and press
[SELECT]. The process graphic viewing mode display appears.
or
D From the command line:
PG: (volume,filename) [ENTER]
If the volume that the Process Graphic resides on is the default
volume (usually the console disk drive), the volume entry can be
omitted. For information about default volumes, see the DT
Manual.

CC: 2-1-5
message appears at the top of the screen, and a blank Graphics
Viewing screen appears:
or
D From the process graphic configuration mode display:
Press [EXCH].

CC: 2-1-6
Calling Up the Configuration Mode of a Process Graphic
- To call up the configuration mode display of a process graphic:

D Type:
PGG (volume,filename) [ENTER]
If the volume that the process graphic resides on is the default
volume (usually the console’s own disk drive), the volume entry
can be omitted. For information about default volumes, see the
DT Manual.
message appears at the top of the screen, and a blank Process
Graphic Generation screen appears:
The process graphic has now been created and may be

configured.
or
D Press [EXCH] from the process graphic viewing mode display.

CC: 2-2-1
Section 2:
Process Graphics
This section explains how to create and configure process graphics.
RS3: Process Graphics Process Graphics

CC: 2-2-2
Creating Process Graphics Objects
A process graphic is constructed by configuring objects on the process

graphic fabric. Process Graphics uses menus to accomplish
configuration tasks. A process graphic display can contain no more
than 24 Kbytes of memory.
- To create an object:
1. Move the cursor to the location on the fabric where you want the
object to appear.
2. Press [SELECT]. The Top Menu appears on the screen, as
shown in Figure 2.2.1. The “TypeÞNone” field indicates that no
object has been configured for this location on the fabric.
PROCESS GRAPHIC GENERATION 02-Feb-89 09:49:12
Top Menu
TypeÞNone
X
Limits
Area
Close Files
Figure 2.2.1. Creating a Process Graphics Object—Top Menu

CC: 2-2-3
3. Move the cursor to the “Type” field on the Top Menu so that the
field is highlighted. Press [SELECT]. The Object Menu appears
superimposed over the Top Menu, as shown in Figure 2.2.2. The
Object Menu lists the object types that can be configured.
NOTE: To move any menu, cursor to the menu name and press
[SELECT]. Use the trackball to move the menu to the desired location.
Press [SELECT] again.
Top Menu
TypeÞNone Object Menu
TEXT
Limits TAG GROUP PAGEFRWD
LINE LINK UNIT PAGEBACK
BOX DISC OVERVIEW ANCHOR
X CIRCLE
ARC
Close
Files
MODE
UNITS
TREND
BFACE
TARGET
HDEV
TRIANGLE BLKDES TICBAR VDEV
Close Symbol
Figure 2.2.2. Creating a Process Graphics Object—Object Menu

CC: 2-2-4
4. Move the cursor to the desired object type on the Object Menu
so that the object type is highlighted. Press [SELECT]. The Edit
Object Menu appears and the Top Menu and Object Type Menus
disappear, as shown in Figure 2.2.3.
5. Each type of object has its own Edit Object Menu. An item on
the Edit Object Menu can be configured by moving the cursor to
the desired field and pressing [SELECT]. Another menu appears
that allows the field characteristics to be configured.
Edit Object Menu

Type TEXT OptionÞNormal
CondÞ
ColorÞWhite 1n BlinkÞNO
Command
X FontÞNormal Edit Text
Close Top Menu
Figure 2.2.3. Creating a Process Graphics Object—Edit Object Menu

CC: 2-2-5
Object Types
Table 2.2.1 provides brief descriptions of objects that can be used to

configure a process graphic display. They are explained in more detail
later in this chapter.
Table 2.2.1. Process Graphic Object Types
Object Type Description
Shapes
Circle Displays a circle.
Line Displays one or more lines.
Arc Displays an arc.
Triangle Displays a triangle.
Box Displays a box.
Block information
Tag Displays a block tag.
Blkdes Displays a block descriptor.
Mode Displays the mode of a block.
Block variable information
Link Displays the value of a block variable.
Units Displays the units of a block variable.
Disc Displays one line of a discrete faceplate.
Displays a horizontal line that travels along a vertical axis. The line shows
Ticbar
the value of a block variable.
Displays a bar with horizontal travel that shows the difference between two
Hdev
block variables.
Displays a bar with vertical travel that shows the difference between two
Vdev
block variables.
Permanent Faceplates
Group Displays a continuous or discrete faceplate.
Unit Displays a continuous or discrete faceplate from a unit display.
Overview Displays a continuous or discrete faceplate from an overview display.

CC: 2-2-6
Table 2.2.1. Process Graphic Object Types (continued)
Text—Text Displays user--configured text. Can also be used to execute a command.
Object Type Description
Alarm Information—Alarm Provides access to alarms from a process graphic.
Displays graphic trend information for a block variable from a configured

Trend Information—Trend
trend file.
Batch Input Displays batch messages and input prompts. For more information, see
Window—Bainputw BA: 4--1.
Batch Recipe Viewing Displays a window version of the Batch Working Recipe screen for
Window—Barcpw monitoring the Working Recipe. For more information, see BA: 4--1.
Batch faceplate—Bface Displays a batch faceplate for use on the graphic display.
Display Manipulation
Pagefrwd Executes command when [PAGE AHEAD] is pressed.
Pageback Executes command when [PAGE BACK] is pressed.
Anchor Provides pointer for Pagefrwd, Pageback, and Text objects.
Target Provides target for quick cursor positioning on a large fabric.
Icon Provides the ability to display or hide another object or a group of objects.

CC: 2-2-7
How Objects Appear in Viewing and Configuration

Modes
Most object types appear differently in viewing mode and configuration

mode. Figure 2.2.4 shows a portion of a graphic display in viewing
mode. The graphic display includes a block tag and a block variable
value.
Figure 2.2.5 shows the same portion of the graphic display, this time in
configuration mode. The block tag is represented by the shaded box
labeled Tag, and the block variable is represented by the shaded box
labeled Link.
GRAPHICS VIEWING 02-Feb-88 09:49:12
FCC-101
35.7
Figure 2.2.4. Viewing Mode

CC: 2-2-8
TAG
LINK
Figure 2.2.5. Configuration Mode

CC: 2-2-9
Creating Shapes:
Circles
- To create a circle:
1. Move the cursor to the desired location of the center of the circle.
Press [SELECT]. The Top Menu appears.
2. Move the cursor to the “TypeÞNone” field and press [SELECT].
The Object Type Menu appears.
3. Move the cursor to the “Circle” field and press [SELECT]. The
Edit Object Menu appears.
4. Move the cursor to change the size of the circle, as shown in
Figure 2.2.6. When the circle is the desired size, press
[SELECT]. The circle is now entered on the fabric.
5. If you want, modify the characteristics of the circle using the Edit
Object Menu. For more information on shape characteristics,
see “Creating Shapes: Shape Characteristics” on page 2-2-15.
Edit Object Menu

Type CIRCLE OptionÞOutline
CondÞ
Resize
Close Undo Top Menu
Figure 2.2.6. Creating a Circle

CC: 2-2-10
Creating Shapes:
Boxes
- To create a box:
1. Move the cursor to the desired location of one corner of the box.
3. Move the cursor to the “Box” field and press [SELECT]. The Edit
Object Menu appears.
4. Move the cursor to change the size of the box, as shown in
Figure 2.2.7. When the box is the desired size and shape, press
[SELECT]. The box is now entered on the fabric.
5. If you want, modify the characteristics of the box using the Edit
Edit Object Menu

Type BOX OptionÞOutline
CondÞ
Resize Rotate
Close Undo Top Menu
Figure 2.2.7. Creating a Box

CC: 2-2-11
Creating Shapes:
Triangles
- To create a triangle:
1. Move the cursor to the desired location of one corner of the
triangle. Press [SELECT]. The Top Menu appears.
3. Move the cursor to the “Triangle” field and press [SELECT]. The
4. Move the cursor to the desired location of the second corner of
the triangle. Press [SELECT].
5. Move the cursor to change the size of the triangle, as shown in
Figure 2.2.8. When the triangle is the desired size and shape,
press [SELECT]. The triangle is now entered on the fabric.
6. If you want, modify the characteristics of the triangle using the
Edit Object Menu. For more information on shape
characteristics, see “Creating Shapes: Shape Characteristics” on
page 2-2-15.
Edit Object Menu

Type TRIANGLE OptionÞOutline
CondÞ
Resize Rotate
Close Undo Top Menu
Figure 2.2.8. Creating a Triangle

CC: 2-2-12
Creating Shapes:
Arcs
- To create an arc:
1. Move the cursor to the desired location of one end of the arc.
3. Move the cursor to the “Arc” field and press [SELECT]. The Edit
4. Move the cursor to the desired location of the other end of the
arc. Press [SELECT].
5. Move the cursor to change the size of the arc, as shown in
Figure 2.2.9. When the arc is the desired size, press [SELECT].
The arc is now entered on the fabric.
6. If you want, modify the characteristics of the arc using the Edit
Edit Object Menu

Type ARC OptionÞOutline
CondÞ
Resize Rotate
Close Undo Top Menu
Figure 2.2.9. Creating an Arc

CC: 2-2-13
Creating Shapes:
Lines
- To create a line:
1. Move the cursor to the desired location of one end of the line.
3. Move the cursor to the “Line” field and press [SELECT]. The Edit
4. Move the cursor to the desired location of the other end of the
line. Press [SELECT]. The line is now entered on the fabric.
Multiple lines can be drawn with the same LINE object. Each
subsequent line begins where the previous line ended.
5. To finish drawing lines, move the cursor to the “End Line” field
and press [SELECT], as shown in Figure 2.2.10.
Edit Object
Type LINE OptionÞLine
CondÞ
LinkÞ Edit Links
Resize Rotate
Close End Line Top Menu
- To end a line or a series

of lines:
D Cursor to the ”End Line”
field and press
[SELECT].
The last line is not
entered on the fabric.
Figure 2.2.10. Creating a Line

CC: 2-2-14
Creating Shapes:
Lines with Different Characteristics
The characteristics of the line, such as the color in which it is to appear

or its ability to blink, can be modified using the Edit Object Menu and
the Edit Links Menu. These characteristics are described in more detail
in Table 2.2.2. Figure 2.2.11 shows the Edit Object Menu with options
for configuring a line.
- To select a display option for a line:
1. Cursor to the desired field and press [SELECT]. Another menu
appears that allows the field to be edited.
2. Move the cursor to the desired field on the new menu and press
[NEXT OPTION]. Then press [ENTER].
A line can be configured to fill or flow in

response to a block variable. The “Option” field determines
the display option:
The “Link” field determines the tag or
address of the block variable that the D Line
edit links come from. D Dashed
The “Edit Links” field determines the D Sm Dash
color and action in the segments of the D Dotted
line. See “Creating Shapes: Multicolor
Shapes” on page 2-2-23 for
information on the Edit Links Menu. Edit Object
Type LINE OptionÞLine
CondÞ
LinkÞ Edit Links
Resize Rotate
Close End Line Top Menu
Figure 2.2.11. Edit Object Menu for the Line Object

CC: 2-2-15
Creating Shapes:
Shape Characteristics
The characteristics of a shape are determined by the fields on the Edit

Object Menu, as shown in Figure 2.2.12 and Table 2.2.2.
- To configure shape characteristics:
1. The Edit Object Menu for the object must be displayed. Move
the cursor to the desired field and press [SELECT]. Another
menu appears that allows the field to be edited.
2. Move the cursor to the desired field on the new menu. The field
entry can be changed by using the [NEXT OPTION] key, if
possible, or by typing the desired entry. Press [ENTER].
Edit Object
Type BOX OptionÞLine
CondÞ
ColorÞwhite 1n BlinkÞNO
Resize Rotate
Close Undo Top Menu
- To increase the size:

D Enter a number >1. For example, an entry
of 3 triples the size.
- To decrease the size:
D Enter a fractional number between zero and
one, or a negative number. For example, an
entry of .25 or an entry of --4 reduces the size
to 1/4.
Figure 2.2.12. Edit Object Menu for Shapes

CC: 2-2-16
Table 2.2.2. Screen Fields on the Edit Object Menu for Shape Characteristics
Field Description
Blink Determines whether or not the object blinks.
Determines the color. The color choices are configured on the Master Color
Color
Selection screen ( [C] [C] [P] command).
Determines a condition that affects how the object is displayed. See “Configuring the
Cond
Appearance of Objects to Change” on page 2-2-54
Determines the display option:

D Line, Dashed, Displayed as an outline with the
Sm Dash, Dotted indicated border style.
D Solid Displayed as a solid shape.
Option D FillN, FillS, FillE, FillW Displayed as a solid object the size of which is
determined by the value of a linked variable. See
“Creating a Shape That Fills Up” on page 2-2-21.
D MultiN, MultiS Displayed as a solid multicolored object. See
“Creating Shapes: Multicolor Shapes” on page
2-2-23.
Resizes the object:

D H Size Changes the horizontal size.
Resize
D V Size Changes the vertical size.
D H+V Size Changes the horizontal and vertical sizes equally.
Rotate Rotates the object in one of five ways.

CC: 2-2-17
Creating Shapes:
Library Symbols
A symbol is a combination of one or more objects that represents a

commonly used graphic feature. Symbols reside in the Process
Symbols folder on the console disk. A standard library of symbols
resides in the Process Symbols folder. You can also create symbols
and add them to your own library.
Figure 2.2.13 shows how to add an existing symbol to a process

graphic. A symbol is added to a process graphic by reading it from a
disk. A symbol is read from the same volume as the currently
displayed process graphic.
- To access the list of available symbols:
D Call up the Disk Directory screen, cursor to the Process Symbols
folder, and press [SELECT]. The contents of the folder are the
available symbol files. Press [EXCH] to view the descriptions of
the symbol files.
D In step 5 of Figure 2.2.13, use the [NEXT OPTION] key to scroll
through the available symbols.

CC: 2-2-18
Top Menu
TypeÞNone
Object Menu - To add a library symbol to a
process graphic:
Limits TEXT TAG GROUP PAGEFRWD
LINE LINK UNIT PAGEBACK 1. Cursor to the desired fabric
BOX DISC OVERVIEW ANCHOR location and press [SELECT].
CIRCLE
Files MODE TREND TARGET
ARC UNITS BFACE HDEV 2. Cursor to the “Type” field and
Close press [SELECT]. The Object
TRIANGLE BLKDES TICBAR VDEV
Close Symbol Type Menu appears.
3. Cursor to the “Symbol” field
and press [SELECT]. The
Process Graphics Symbols
Menu appears.
4. Cursor to the “Symbol File” field.

5. Use the [NEXT OPTION] button to
scroll through the available
symbols, or type the name of the
desired symbol. Press [ENTER].
Process Graphics Symbols NOTE: Less memory is used if a symbol
is added to a graphic only once and then
Symbol FileÞPUMP-1 copied as often as desired, than if the
symbol is added to the graphic
Close Object Type repeatedly.
Figure 2.2.13. Adding a Library Symbol to a Process Graphic

CC: 2-2-19
Creating Shapes:
New Symbols
A symbol is a combination of one or more objects that represents a

commonly used graphic feature. Symbols reside in the Process
Symbols folder on the console disk. A standard library of symbols
resides in the Process Symbols folder. You can also create symbols.
A combination of objects is made into a symbol so that it can be easily

retrieved without having to be recreated. Objects must be grouped with
an Area command, Group and Join commands, or Merge command
before being made into a symbol. (For more information about grouping
objects, see “Configuration Tools: Grouping Objects” on page 2-2-60.)
The objects are then written to a Process Symbols folder as a symbol.
A symbol can be written to any Command Console on the PeerWay.
Figure 2.2.14 shows how to create a symbol.
NOTE: The Process Graphics folder contains five files of commonly

used graphic icons, such as valves, motors, boilers, and other process
symbols. You can select preconfigured icons from the following files to
create process symbols:
D $Readme
D $Stdsym
D $SymbolS1
D $SymbolS2
D $SymbolS3

CC: 2-2-20
Top Menu
TypeÞTHING -
Move Group To create a new symbol:
Copy 1. Select one object in a
Limits LinkEd group.
Delete Top
Undo Bottom 2. Cursor to the “Files” field
Area and press [SELECT].
Close Files
3. Cursor to the “Symbol” field.

4. Type in a comma (,) and the
File Operations desired symbol name.
ReadÞvolume,filename.pg A symbol can be copied to
another disk by entering:
WriteÞvolume,filename.pg volume,symbolname
SymbolÞ
Close Link Count
The “Link Count” field displays the
number of blocks/addresses that
are configured on the graphic.
Figure 2.2.14. Creating a New Symbol

CC: 2-2-21
Creating Shapes:
Shapes that Fill Up in Response to a Block Variable
The Box, Circle, Arc, and Triangle shapes can be configured as solid
shapes that fill up in response to a block variable. Other objects can be
placed on top of a shape, and shapes can be combined to fill up a
complex shape, as shown in Figure 2.2.16.
- To create a shape that fills up in response to a block variable:
1. Call up the Edit Object Menu for the shape. Cursor to the
“Option” field and press [SELECT]. The Option Menu appears,
as shown in Figure 2.2.15.
2. Use the [NEXT OPTION] key to access the “Option” field
choices. Enter the desired option. Close the menu.
— FillN indicates that the object fills from bottom to top.
— FillS indicates that the object fills from top to bottom.
— FillE (Box only) indicates that the object fills from left to right.
— FillW (Box only) indicates that the object fills from right to left.
When one of the fill options is configured, the “Link”, “Empty”,
and “Full” fields appear on the Edit Object Menu.
3. Cursor to the “Link” field and press [SELECT]. The Link Menu
appears. Enter the desired block variable. Close the menu.
4. The default scaling values are “EmptyÞ.00%” and
“FullÞ100.00%”. If other “Empty” or “Full” values are desired,
cursor to one of those fields and press [SELECT]. The Scaling
Menu appears.
The “Empty” field indicates the percent value of the block
variable that is shown as an empty shape. For example, if
“EmptyÞ25.00%” is configured, the shape appears empty (no
shape is shown) until the block variable value is 25.00% of the
block variable range.
The “Full” field indicates the percent value of the block variable
that is shown as a full shape. For example, if “FullÞ75.00%” is
configured, the shape appears full (the entire shape is shown)
when the block variable value is 75.00% of the block variable
range.

CC: 2-2-22
Determines the fill option.
Determines the tag or Edit Object

address of the block
variable that is linked Type BOX OptionÞFillN
to the fill function. CondÞ
LinkÞ
EmptyÞ.00% FullÞ100.00%
Resize Rotate
Close Undo Top Menu
Determine the scaling of
the fill function.
Figure 2.2.15. Edit Object Menu for Creating a Shape that Fills Up in Response to a Block Variable
Other objects can be

configured on top of the fill
shape.
PRODUCT
Arc object with

“OptionÞFillN”
Multiple fill shapes can be “FullÞ100.00%”
put together to form an “EmptyÞ75.00%”
intricate fill function.
Box object with

“OptionÞFillN”
“FullÞ75.00%”
“EmptyÞ25.00%”
Arc object with

“OptionÞFillN”
“FullÞ25.00%”
“EmptyÞ.00%”
Figure 2.2.16. Examples of the Ways that Shapes Can Be Used

CC: 2-2-23
Creating Shapes:
Multicolor Shapes
The Box, Circle, Arc, and Triangle shapes can be configured to fill in
more than one color. One multicolor object is configured from one
ControlBlock variable.
Figure 2.2.17 and Figure 2.2.18 show an example of configuring a

multicolor shape with the Edit Object Menu and the Edit Links Menu.
Box object with

“Multi N” option.
Determines the multicolor options:

· Multi N to indicate that the object fills from bottom to top.
· Multi S to indicate that the object fills from top to bottom.
Edit Object
Determines the tag or
address of the block Type BOX OptionÞMulti N
variable that the edit links CondÞ
come from.
BlockÞ Edit Links
Resize
Rotate
Determines the scaling of Close Undo Top Menu
the fill function.
Determines the order and

color of the layers in the
object.
Figure 2.2.17. Multicolor Shape and Edit Object Menu

CC: 2-2-24
Highlight “Edit Links“ and press

[SELECT] to call up the Edit
Links Menu.
Edit Object
Type BOX OptionÞMulti N
CondÞ Up to 15 continuous links from one
block variable can be selected on the
BlockÞ9A-99 Edit Links Edit Links Menu.
Resize Rotate
Close Undo Top Menu Edit Links
Color InputÞ2n Scaling InputÞA
Color InputÞ5n Scaling InputÞE
The “Color Input“ can be a Color InputÞG Scaling InputÞF
normal color combination
from the Master Color Color InputÞ Scaling InputÞ
Selection screen or the
color of a continuous block Color InputÞ Scaling InputÞ
input (A through O).
Close Next
The “Scaling Input“ must be a continuous

block input (A through O). Links are
configured on the Continuous Links
screen of the ControlBlock. Scaling
Inputs are layered in the order in which
they are configured on the Edit Links
Menu.
As an example, if the tank is configured as 0--200

gallons:
Link A (with a value of 150 gallons) is listed first.
Link E (with a value of 50 gallons) is listed second.
Link F (with a value of 30 gallons) is listed third.
Figure 2.2.18. Example of a Multicolor Shape with Edit Links Menu

CC: 2-2-25

Tag, Blkdes, Mode Objects
Block information such as tag, descriptor, and operating mode can be

displayed on a process graphic. Table 2.2.3 describes the objects that
display block information.
Table 2.2.3. Objects that Display Block Information
Object Description
Displays the descriptor of a block, for example “INLET FLOW VALVE”, “Product
Blkdes
temperature”.
Mode Displays the mode of a block, for example “>AUTO”, “>MANUAL”.

CC: 2-2-26
- To create the Tag, Blkdes, or Mode object:

1. Move the cursor to the desired location of the object. Press
[SELECT]. The Top Menu appears.
3. Move the cursor to the appropriate field and press [SELECT].
The Edit Object Menu appears. Figure 2.2.19 shows how the
Tag, Blkdes, and Mode objects appear in configuration mode.
4. If you want, modify the characteristics of the object using the Edit
Object Menu.
TAG
BLKDES
MODE
Figure 2.2.19. How the Tag, Blkdes, and Mode Objects Appear in Configuration Mode

CC: 2-2-27
- To configure the Tag, Blkdes, and Mode object characteristics:

1. The characteristics of an object are determined by the fields on
the Edit Object Menu, as shown in Figure 2.2.20 and Table 2.2.4.
Move the cursor to the desired field and press [SELECT].
Another menu appears.
2. Move the cursor to the desired field. The field entry may be
changed by using the [NEXT OPTION] key, if possible, or by
typing the desired entry. Press [ENTER].
Edit Object Menu
Type Tag Num ColÞ 8

CondÞ
ColorÞ White 1n BlinkÞ No
BlockÞ SplitÞ No
FontÞ
Close Top Menu
Figure 2.2.20. Edit Object Menu for the Tag, Blkdes, and Mode Objects
Table 2.2.4. Screen Fields on the Edit Object Menu for the Tag, Blkdes, and Mode Objects
Field Description
Determines the tag or address of the block that provides the information for the
Block
object.
Color
Cond
Appearance of Objects to Change” on page 2-2-54.
Determines the font size of the displayed characters

Font D “Normal” indicates normal size.
D “Small” indicates half--size—half the width and half the height.
Determines the width of the object, in columns. A column is the width of a standard
Num Col
character.
Lets you determine whether a tag should be split. If you choose not to split the tag,
Split the window displays the “Num Col” field, and you must then specify the number of tag
characters to display.

CC: 2-2-28
Creating Objects That Display Block Variable

Information in Character Form:
Links, Units, Disc Objects
Block variable information can be displayed on a process graphic in

character form as text. Table 2.2.5 describes the objects that display
block variable information in character form.
Table 2.2.5. Objects that Display Block Variable Information in Character Form
Object Description
Link Displays the value of a block variable.
Units Displays the units of a block variable, for example “GPM”, “DEG C”.
Displays one line of a discrete faceplate. If the line is operator--enterable on the

Disc faceplate, it is also operator--enterable on the graphic display. For an example on the
use of the Disc object, see “Creating Data Entry Fields” on page 2-2-53.

CC: 2-2-29
- To create the Link, Units, or Disc object:

Link, Unit, and Disc objects appear in configuration mode.
Object Menu.
LINK
UNITS
DISC
Figure 2.2.21. How the Link, Units, and Disc Objects Appear In Configuration Mode

CC: 2-2-30
- To configure the Link, Units, and Disc object characteristics:

the Edit Object Menu, as shown in Figure 2.2.22 and Table 2.2.6.
Move the cursor to the desired field and press [SELECT].
Edit Object Menu

Type Disc Num ColÞ8
CondÞ
BlockÞ IndexÞ
FontÞNormal
Close Top Menu
Figure 2.2.22. Edit Object Menu for the Link, Units, and Disc Objects
Table 2.2.6. Screen Fields on the Edit Object Menu for Link, Units, and Disc Objects
Field Description
Determines the tag or address of the block or link that provides the information for the
Block
object.
Cond
Determines the font size of the displayed characters.

(Disc only) Determines which of the 17 lines in the discrete faceplate is displayed. If
a line on the discrete faceplate is operator enterable, the same line displayed on the
Index
Process Graphic is also operator enterable. See “Creating Data Entry Fields” on
page 2-2-53.
Num Col Determines the maximum number of characters to be displayed.

CC: 2-2-31
Creating Objects That Display Block Variable

Information in Graphic Form:
Hdev, Vdev, Ticbar Objects
Block variable information can be displayed on a process graphic in

graphic form. Table 2.2.7 describes the objects that display block
variable information in graphic form.
Table 2.2.7. Objects that Display Block Variable Information in Graphic Form
Object Description
Displays a bar that travels horizontally from a center vertical axis. The bar represents
Hdev
the difference between two ControlBlock variables.
Displays a bar that travels vertically from a center horizontal axis. The bar represents
Vdev
the difference between two ControlBlock variables.
Displays a horizontal line with travel along a vertical axis. The line shows the value of
Ticbar
a block variable.

CC: 2-2-32
- To create the Hdev, Vdev, or Ticbar object:

Hdev, Vdev, and Ticbar objects appear in configuration mode.
Object Menu.
HDEV
HDEV
VDEV
T
I VDEV
C-
B
A
R
Figure 2.2.23. How the Hdev, Vdev, and Ticbar Objects Appear in Configuration Mode

CC: 2-2-33
How the Hdev and Vdev Objects Are Displayed
Figure 2.2.24 shows how the Hdev and Vdev objects are displayed on a
process graphic.
The Hdev object displays Graphics Viewing

a bar. The bar represents
the difference between
The Vdev object
two block variables.
displays a bar. The bar
represents the
difference between two
block variables.
A bar to the right of the center line

A bar to the left of the center line represents a positive deviation
represents a negative deviation value. (Plus Input > Minus Input)
value. (Plus Input < Minus Input)
Hdev
A bar that extends to the

edge of the object represents The outline represents the
a value of 50% of the size of the object. The outline
“Range” field. is not visible in the viewing
mode.
Vdev A bar above the center line

represents a positive deviation
value. (Plus Input > Minus Input)
A bar below the center line represents

a negative deviation value.
(Plus Input < Minus Input)
Figure 2.2.24. How the Hdev and Vdev Objects Appear in Viewing Mode

CC: 2-2-34
The characteristics of an object are determined by the fields on the Edit

- To configure the Hdev and Vdev object characteristics:
1. Move the cursor to the desired field and press [SELECT].
Edit Object Menu

Type HDEV SizeÞ Þ
CondÞ
BlockÞ
OffsetÞ.00% RangeÞ100.00%
Plus InputÞB Minus InputÞA
Close Undo Top Menu
Figure 2.2.25. Edit Object Menu for the Hdev, Vdev, and Ticbar Objects
Table 2.2.8. Screen Fields on the Object Edit Menu for the Hdev, Vdev, and Ticbar Objects
Field Description
Block Determines the tag or address of the block that provides the variable values.
Color
Cond
Determines the range of the deviation. The range is specified as a per cent value of
Range the Plus Input block variable range. A range of 100% displays a deviation of 50% of
the Plus Input block variable range in each direction.
Determines the minus input.

Minus Input
The object displays: (Plus Input) - (Minus Input)
Offset Determines the percent value that the deviation is offset from 0.
Determines the plus input. The object displays:

Plus Input
(Plus Input) - (Minus Input)
Determines the size of the object.

D “Num Col” indicates the width of the object in number of columns. A column is
Size the width of a standard character.
D “Num Row” indicates the height of the object in number of rows. A row is the
height of a standard character.

CC: 2-2-35
How the Ticbar Object is Displayed
Figure 2.2.26 shows how the Ticbar object is displayed on a process

graphic.
Graphics Viewing
The Ticbar object displays

a horizontal line. The line
represents the value of a
block variable.
The outline represents the

size of the Ticbar object.
A horizontal line at the top of
The outline is not visible in
the Ticbar object represents
the viewing mode.
the ”Full” field value
configured on the Ticbar Edit
Object Menu.
A horizontal line at the bottom of

the Ticbar object represents the
”Empty” field value configured on
the Ticbar Edit Object Menu.
Figure 2.2.26. How the Ticbar Object Appears in Viewing Mode

CC: 2-2-36

- To configure the Ticbar object characteristics:
Edit Object Menu

Type TICBAR SizeÞ Þ
CondÞ
LinkÞ
Close Undo Top Menu
Figure 2.2.27. Edit Object Menu for the Hdev, Vdev, and Ticbar Objects
Table 2.2.9. Screen Fields on the Edit Object Menu for the Hdev, Vdev, and Ticbar Objects
Field Description
Color
Cond

Size D “Num Col” indicates the width of the object in number of columns.
D “Num Row” indicates the height of the object in number of rows.
Determines the percent value of the block variable range that represents the top of
Full
the Ticbar object.
Determines the percent value of the block variable range that represents the bottom
Empty
of the Ticbar object.
Link Determines the tag or address of the link that provides the variable values.

CC: 2-2-37

Group, Unit, Overview Objects
Faceplates can be configured as permanent parts of a process graphic

display. Table 2.2.10 describes the objects that display faceplates.
Table 2.2.10. Objects that Display Faceplates
Object Description
Group Displays a full--sized ControlBlock faceplate, as shown on a group display.
Unit Displays a ControlBlock faceplate from a unit display.
Overview Displays a ControlBlock faceplate from an overview display.

CC: 2-2-38
- To create the Group, Unit, or Overview object:

The Edit Object Menu appear. Figure 2.2.28 shows how the
Group, Unit, and Overview objects appear in configuration mode.
Object Menu.
OVERVIEW
OVERVIEW
UNIT
UNIT
GROUP UNIT
GROUP UNIT
GROUP
GROUP
GROUP
GROUP
GROUP
GROUP
GROUP
GROUP
Figure 2.2.28. How the Group, Unit, and Overview Objects Appear in Configuration Mode

CC: 2-2-39

Object Menu, as shown in Figure 2.2.29.
- To configure the Group, Unit and Overview object
characteristics:
Determines a condition that determines Determines the type of faceplate:

whether the object is displayed. See
“Configuring the Appearance of Objects D “Analog” indicates the block continuous
to Change” on page 2-2-54. faceplate.
D “Discrete” indicates the block discrete
faceplate.
Edit Object Menu

Type Group OptionÞAnalog
Determines the tag or CondÞ
address of the block
that provides the BlockÞ
faceplate.
Close Top Menu
Figure 2.2.29. Edit Object Menu for the Group, Unit, and Overview Objects

CC: 2-2-40
Displaying a Faceplate from a Process Graphic Object
A process graphic object that is interactive with a ControlBlock can be

used to display the ControlBlock faceplate temporarily, as shown in
Figure 2.2.30. If a ControlBlock is interactive with a process graphic
object, the faceplate for that block can be displayed by cursoring to the
object and pressing [SELECT]. The Continuous Faceplate screen for
the ControlBlock can be called up by pressing [SELECT] again.
A ControlBlock faceplate can be displayed from the following graphic

objects: Tag, Blkdes, Mode, Link, Disc, Ticbar, Hdev, Vdev, Group, Unit,
Overview, Trend, and Target. A faceplate can also be displayed from
Box, Circle, Triangle, and Arc objects that have a fill option configured.
GRAPHICS VIEWING
FLV-2A
FLV-2A
GPM
Flow Temperature #1 76.00
73.00
>AUTO 0.00
0.00
- 99.0
To display the faceplate for the block:
D Cursor to the object and press [SELECT]. Gallons
AUTO
The faceplate appears on the side of the graphics screen. PRO1PU004
The [EXCH] key can be used to view the other block
faceplate.
- To call up the Continuous Faceplate screen for the

block:
D Cursor to the faceplate and press [SELECT].
Figure 2.2.30. Displaying a ControlBlock Faceplate from a Process Graphic Object

CC: 2-2-41
Creating Objects That Display Trend Information:

Trend Object
Block variable information from a trend file can be displayed on a

process graphic using the Trend object.
- To create the Trend object:
1. Move the cursor to the location on the fabric where the object
should be. Press [SELECT]. The Top Menu appears.
Trend object appears in configuration mode.
4. If you want, edit the characteristics of the object using the Edit
Object Menu.
TREND TREND
TREND TREND
TREND TREND
TREND TREND
Figure 2.2.31. How the Trend Object Appears in Configuration Mode

CC: 2-2-42

- To configure the Trend object characteristics:
Edit Object Menu

Type Trend SizeÞ Þ
CondÞ
LinkÞ FileÞ
LowÞ HighÞ
Freq.Þ SlidewireÞ
Close Top Menu
Figure 2.2.32. Edit Object Menu for the Trend Object

CC: 2-2-43
Table 2.2.11. Screen Fields on the Edit Object Menu for the Trend Object
Field Description
Color
Cond
Determines the trend file that contains the desired information. Expressed as:
File
node # / trend file # (for example, =28/1).
Determines how often data is added to the Trend object. This value can be greater
Freq than or equal to the ”Frequency” field on the Trend File Configuration screen for the
block variable.
Determines the percent value of the block variable range that represents the top of
High
the Trend object.
Link Determines the link that provides the trend values.
Determines the percent value of the block variable range that represents the bottom
Low
of the Trend object.

D “Num Col” indicates the width of the object in number of columns. A column is
Size the width of a standard character.
D “Num Row” indicates the height of the object in number of rows. A row is the
height of a standard character.
Determines the slidewire group. All trend objects with the same slidewire number are
Slidewire linked together. If a slidewire is used on one object, a slidewire shows on all objects
in the group.

CC: 2-2-44
How the Trend Object is Displayed
Figure 2.2.33 shows how the Trend object is displayed on a process

graphic. Figure 2.2.34 shows how the Trend object slidewire feature
operates.
Graphics Viewing
The Trend object displays a line. The line

represents block variable values from a
trend configuration file.
The outline represents the The “High” field on the Edit Object Menu determines
size of the Trend object. The the value of the top of the Trend object. The “High”
outline is not visible in the field entry is expressed as a percentage of the block
viewing mode. variable range, which is specified on the ControlBlock
Links screen.
The “Freq” field on the Edit Object

Menu determines how frequently The “Low” field on the Edit Object
data values are entered on the Menu determines the value of the
Trend object. bottom of the Trend object. The
“Low” field entry is expressed as a
percentage of the block variable
range, which is specified on the
ControlBlock Links screen.
The amount of time displayed by
a Trend object is equal to the
“Freq” field times number of
columns wide.
Figure 2.2.33. How the Trend Object is Displayed

CC: 2-2-45
SLIDEWIRE: a feature that

allows the user to view numeric Graphics Viewing
trend data for a Trend object.
08:32:33
Along with the
slidewire, a time and
numeric value are also
233.5 displayed.
When the cursor is moved
into the Trend object, the
slidewire appears.
All Trend objects with the

same “Slidewire” field entry
on the Edit Object Menu are When a slidewire is used on one of
grouped together. these objects, slidewires appear on all
objects in the group.
08:32:33 08:32:33 08:32:33
233.5 51.3 1225
Figure 2.2.34. Slidewire Feature of the Trend Object

CC: 2-2-46
Creating Displayed Text:

Text Object
Text can be displayed on a process graphic with the Text object. The
Text object consists of one line containing up to 72 characters.
- To create the Text object:
1. Move the cursor to the desired location where the text should
begin. Press [SELECT]. The Top Menu appears.
3. Move the cursor to the “Text” field and press [SELECT]. The Edit
Object Menu appears. Even though the Text object is now
created, nothing appears on the screen until characters are
entered in the “Edit Text” field of the Edit Object Menu.
4. Type the characters to go into the text next to the “Edit Text” field.
Object Menu.
- To configure the Text object characteristics:
The characteristics of an object are determined by the fields on the
Edit Object Menu, as shown in Figure 2.2.35 and Table 2.2.12.
Edit Object Menu

Type Text OptionÞNormal
CondÞ
CommandÞ
FontÞNormal Edit Text
Close Top Menu
Figure 2.2.35. Edit Object Menu for the Text Object

CC: 2-2-47
Table 2.2.12. Screen Fields on the Edit Object Menu for the Text Object
Field Description
Color
Cond
Determines a command that is executed if [SELECT] is pressed when the cursor is

on the object. The command can be any combination of keystrokes that can be
Command
entered at the command line, or the number of an Anchor object. See the “Creating
Objects That Call Up Other Displays” heading in this section.
Edit Text Allows text to be entered.

Determines how the text is displayed:

Option D “Normal” indicates that the text covers any object below it.
D “Clear” indicates that objects below the text show through.

CC: 2-2-48
Displaying Alarms:
Alarm Object
The Alarm object provides access to alarms from a process graphic.

The operator can view and acknowledge alarms from the graphic. You
can configure the Alarm object to read console RAM lists, including the
Event Lists.
- To create the Alarm object:
Alarm object appears in configuration mode.
Object Menu.
Figure 2.2.37 shows how the Alarm object is used in a process graphic.
Table 2.2.13 describes the fields on the Alarm object Edit Object Menu.
For more information about configuring alarms, see CC: 6.
ALARM
Figure 2.2.36. How the Alarm Object is Displayed

CC: 2-2-49
- To see a specific alarm:

D Cursor to TOP# and
- To see more alarms: enter the row no. (from 1
D Cursor to DN and to the scan limit) of the
press [SELECT] desired alarm.
to see the previous - To see the last alarm:
alarms. D Cursor to TOP# and
D Cursor to UP and enter a row no. that is
press [SELECT] larger than the current
to see the next alarms. no. of alarms, but less
- To acknowledge one than the scan limit.
displayed alarm: GRAPHICS VIEWING
The Alarm object title
D Cursor to the alarm and shows the alarm condition
press [a]. of the highest priority
-
alarm in the object.
To acknowledge all
displayed alarm:
D Cursor to ALARMS 2
[ALARM ACK]
and press [a]. ALARM ACK UP DN TOP# 1
Occur Tag
- 18:46:11 =19A Controller Not Backed Up
To call up the faceplate 18:45:40 =19A Controller Not Backed Up
for a block: 18:45:18 =18 Alarm logging Enabled
D Press [SELECT] 18:45:16 =18 Trend Recording Disabled
on the process alarm. 18:45:04 =18 Node Restarted
18:44:42 LIC-20/PV Drum Level High Critical 12.64Ft.
18:43:30 =19A Controller Not Backed Up
***MORE***
- To suppress an alarm: When the cursor is inside the alarm

D Cursor to the alarm and window on the [ALARM ACK] key, the
press [s]. [ALARM ACK] key acts only on the
alarms in the window.
- To unsuppress (or enable)
an alarm when viewing
suppressed alarms:
D Cursor to the alarm and
press [e].
Figure 2.2.37. Example of Alarm Object

CC: 2-2-50
Table 2.2.13. Screen Fields on the Edit Object Menu for the Alarm Object
Field Description
Blink Specifies whether or not the object blinks.
Specifies the normal color of the object. The color choices are configured on the
Color
Master Color Selection screen ([C] [C] [P] command).
Cond Specifies a condition that affects how the object is displayed.
Specifies display parameters.

Ack Time Specifies whether the acknowledge time appears in alarm entries.
Clear Time Specifies whether the clear time appears in alarm entries.
Date Specifies whether the date appears in alarm entries.
Desc Specifies whether the block descriptor appears in alarm entries.
List Specifies when the alarm list appears.
Active =When there are active alarms in the alarm list.
Any =When there are any alarms in the alarm list.
Always =Always.
Display Format
NOTE: Never is no longer an option. If the alarm List option was
previously configured as Never, Never will appear until you
reconfigure the alarm List option.
Occur Time Specifies whether the occur time appears in alarm entries.
Tag Specifies whether the tag appears in alarm entries.
Title Specifies when the title appears.
Never =never
Active =only when there are active alarms in the alarm list
Any =only when there are any alarms in the alarm list
Always =always
Specifies the filter parameters of alarms to be excluded from the Alarm object display.
If no parameters are configured, all alarms are included. The alarm area containing
the Alarm object must be enabled for the alarm to be displayed.
Filter parameters:
unit = plant unit (1--255)
area = area name
FILT Criteria blk = block tag
pri = priority (ControlBlock: 0--15; I/O block: 0--3)
type = alarm type (hard, proc, crit, adv, batch, sys, disk, el1--el10)
state = alarm state (active, clear, unack, ack)
node = node number
Figure 2.2.38 shows some examples of criteria configurations.

CC: 2-2-51
Table 2.2.13. Screen Fields on the Edit Object Menu for the Alarm Object (continued)
Field Description
Specifies which information is included in the Alarm object display. If no parameters

are configured, all nonsuppressed alarms are included. The alarm area containing
the Alarm object must be enabled for the alarm to be displayed.
Find parameters:
area = area name
FIND Criteria blk = block tag
pri = priority (ControlBlock: 0--15; I/O block: 0--3)
type = alarm type (hard, proc, crit, adv, batch, sys, disk, el1--el10)*
state = alarm state (active, clear, unack, ack, suppr)*
node = node
ctime = cutoff time (format=dd--mm--yy/hh:mm:ss)
Specifies the maximum number of matched entries of alarm information for which the
Scan Limit alarm list is scanned. The highest allowable entry is 5000. The alarm list is scanned
until either the scan limit or the end of the alarm list is reached.
The title that appears at the top of the alarm list. The title can be up to 26 characters
Title
long.
Specifies how big the alarm object is when the alarm list is displayed. The maximum
size is 82 columns wide and 20 rows high. The Alarm object that appears on the
Process Graphic Generation screen shows the upper left location of the Alarm
Window Size object—it does not represent the actual size of the object.
NOTE: In order to enter a number in the TOP# field, or to use [a] to acknowledge
alarms, [s] to suppress an alarm, or [e] to unsuppress an alarm, the Alarm object
must be at least 40 columns.

CC: 2-2-52
This configuration specifies that the Alarm

Find Crit>unit=1-7; object displays all alarms from plant units 1
through 7.
This configuration specifies that the

Find Crit>area=boiler1,boiler2 Alarm object displays all alarms from
alarm areas “boiler1” and “boiler2”.

Find Crit>area=boiler1& type=crit object displays all critical alarms from alarm
area boiler1.
The & represents a logical and operation.
Find Crit>area=boiler1 | blk=TEMP1
Both of these configurations specify the

same criteria—that the Alarm object
Find Crit>area=boiler1
displays all alarms from alarm area boiler1
| >blk=TEMP1 and from block TEMP1.
The | represents a logical or operation.
| >
FIND:
Find Crit>unit=1-6;
| >
| > object displays all alarms from plant units 1
FILTER: through 6, but excludes unacknowledged
Filt Crit>state=unack alarms.
| >
| >
Figure 2.2.38. Examples of Criteria Configurations

CC: 2-2-53
Creating Data Entry Fields: Disc Object
The configuror can use the Disc object to create fields on the process
graphic display that allow the operator to enter data and to turn devices
on and off. The Disc object displays a line from a ControlBlock discrete
faceplate. If the line is operator--enterable on the faceplate, it is also
operator--enterable on the process graphic.
Figure 2.2.39 shows two examples of Disc objects used as data entry
fields. The top DISC object allows the operator to start a motor
controlled by a DMC ControlBlock. The lower Disc object allows the
operator to change a bias setting.
Edit Object Menu

Type DISC Num ColÞ8
CondÞ
DMC--4 BlockÞDMC-4 IndexÞ2

FontÞNormal
1 OPERATOR Close Undo Top Menu
2 > start
3 > stop
4
5 --AUTO--
6 start
7 stop GRAPHICS VIEWING
8
9 ------- BIAS--1
10 on cfrm
11 offcfrm >start
12 tripped 1
13 2 112.55
14 -OUTPUT- 3 GPM
15 run 4
16 STOP >12.00 5
17 failed 6 > 12.00
7 GPM BIAS
8
9
10
11
12
13
Edit Object Menu 14
15
Type DISC Num ColÞ8 16
CondÞ 17
BlockÞBIAS-1 IndexÞ6
FontÞNormal
Close Undo Top Menu
Figure 2.2.39. Example Data Entry Fields

CC: 2-2-54
Configuring The Appearance of Objects to Change,

Depending on the State of a Discrete Block Variable
Most process graphics objects can be configured to appear in two

forms, depending on the true/false condition of a discrete block variable.
Figure 2.2.40 shows how to configure the appearance of an object to

change.
- To configure an object to change:

1. Call up the Edit Object Menu for the
object. Move the cursor to the “Cond”
field and press [SELECT].
Edit Object
CondÞ
Condition
Close Top Menu
CondÞFIC-101/a
Close
2. The Condition Menu appears. Enter a 3. Close the Condition Menu.

true/false block variable condition in
the “Cond” field.
For example, =1A--3/b indicates that

the condition is met when logic step b
of ControlBlock =1A--3 is true.
The entry =1A--3/b indicates that the

condition is met when logic step b of
ControlBlock =1A--3 is false. The
block variable can be entered by
address or tag.
Figure 2.2.40. Configuring the Edit Object Menu for Conditional Display of Objects

CC: 2-2-55
4. When the “Cond” field is configured, the “Chg” field

appears on the Edit Object Menu.
To change any of these display characteristics:

D Cursor to the “Color”, “Blink”, or “Chg” field and press
[SELECT]. The Select Color Menu appears.
Configure the true and false conditions as you want
them to appear.
Edit Object
CondÞ ChgÞ--erase--
These fields determine the

display characteristics of the CloseSelect Color Top Menu
object when the condition is
met. ColorÞwhite 1n BlinkÞNO
Chg -Þ-erase-- BlinkÞNO
Close
These fields determine the display

characteristics of the object when the
condition is not met.
The default condition is “----erase----”, which
means that the object is not displayed at all
when the condition is not met.
The Group, Unit, Overview, Pagefrwd, and
Pageback objects do not have a ”Chg” field.
If the condition is not met, the object is not
displayed.
Figure 2.2.40. Configuring the Edit Object Menu for Conditional Display of Objects (continued)

CC: 2-2-56
Configuration Tools:
Moving and Copying Objects
Figure 2.2.41 shows how to move and copy graphic objects.
NOTE: If you copy an Area that includes overlapped objects, the

top/bottom arrangement of the objects may change.
- To move or copy an object:

1. Call up the Top Menu for the object. GRAPHIC GENERATION
PROCESS 02-Feb-89 09:49:12
2. Move the cursor to the desired
operation (Move or Copy). Press
[SELECT]. Top Menu
3. Move the cursor to the desired
location of the new object. The TypeÞTAG
outline of the object follows the Move Group
Copy
cursor. Press [SELECT]. Limits LinkEd
4. To undo the last operation, move the Delete Top
cursor to the “Undo” field on the Top Undo Bottom
Menu and press [SELECT]. Area
Close Files
TAG
Figure 2.2.41. Moving and Copying an Object

CC: 2-2-57
Deleting Objects
Figure 2.2.42 shows how to delete graphic objects.
- To delete an object: PROCESS GRAPHIC GENERATION 02-Feb-89 09:49:12

1. Call up the Top Menu for the object.
2. Move the cursor to the “Delete” field.
Press [SELECT]. The object is now Top Menu
deleted and the Top Menu with
TypeÞTAG
“TypeÞNone” is displayed. Move Group
- To undo the last operation: Copy
Limits LinkEd
D Move the cursor to the ”Undo” field on the Delete Top
Top Menu and press [SELECT]. Undo Bottom
Area
Close Files
TAG
Figure 2.2.42. Deleting an Object

CC: 2-2-58
Stacking Objects—Top and Bottom Operations
You can place an object at the top or bottom of a stack using the top
and bottom operations. Figure 2.2.43 shows how the top and bottom
operations are used. Figure 2.2.44 shows an example of two Box
objects in a stack to form a tank.
Top Menu
TypeÞTAG
Move Group
Copy
Limits LinkEd
Delete Top
TAG Undo Bottom
TAG Area
Close Files
Top Menu
TypeÞTAG
Move Group
Copy
Limits LinkEd
Delete Top
TAG Undo Bottom
TAG Area
Close Files
Figure 2.2.43. Stacking Objects Using the Top and Bottom Operations

CC: 2-2-59
Example of Stacking Objects
- PROCESS
Example: Configuring a tank by stackingGRAPHIC
one GENERATION 02-Feb-89 09:49:12
object on another :
1. Select a point on the fabric.
Edit Object Menu
2. Create a Box object with “OptionÞOutline”.
3. Close the Edit Object Menu. Type BOX OptionÞOutline
CondÞ
ColorÞcyan BlinkÞNO
Close Undo Top Menu
4. Move the cursor back to the Box object.

5. Press [SELECT] so that the Box object is
selected.
6. Press [SELECT] again so that the Top Menu
displays “TypeÞNONE”.
PROCESS GRAPHIC
7. Create a Box object with “OptionÞFillN”. Enter GENERATION 02-Feb-89 09:49:12
a block variable in the “Link“ field.
Two objects have been created in the same
location to create a tank that fills up in response Edit Object Menu
to an input. One object forms the outline, the
other forms the solid shape. Type BOX OptionÞFillN
CondÞ
LinkÞFIC-101/A
Close Undo Top Menu
Figure 2.2.44. Creating an Object Superimposed on Another Object

CC: 2-2-60
Grouping Objects
Process graphics contains tools for grouping objects together.

Table 2.2.14 lists the operations that can be used to group graphic
objects and the typical uses for each operation.
Table 2.2.14. Grouping Operations
Operation Description
The Area operation draws a box around the objects that are to be grouped
together. The objects are grouped together for one operation only.
Area The Area operation is typically used when only one operation is to be performed
on the set of objects, or when the set of objects is so large that using the Group
and Join operations are cumbersome.
The Group operation identifies an object as the first object in a group. The Join
operation joins other objects to the group. Once joined in a group, objects
remain in the group until the Split operation is used to split them from the group.
Group and Join Multiple operations can be performed on the group.
The Group and Join operations are typically used when multiple operations are
to be performed on a set of objects, or when other operations may be
performed on the set of objects in the future.
The Merge operation is used to join a set of shape objects into a single object
Merge called a Thing.
The Merge operation is typically used to create symbols.

CC: 2-2-61
Grouping Objects—Area Operation
A set of objects can be put into a temporary group with the Area
operation to perform display operations more efficiently, as shown in
Figure 2.2.45. Objects that are grouped with an Area operation are
treated as a group only for the next operation. If a Move, Copy, or
Delete operation is performed on one object in a group, the operation is
performed on all objects in the group. After the operation is performed,
the objects are no longer in a group (unless the next operation is an
Undo, in which case the Undo operation applies to the group). If an
Area operation is attempted on a Thing object, all components of the
Thing must be included in the Area.

CC: 2-2-62
- To join objects into a temporary group:

1. Cursor to a location that will be one
Top Menu corner of the area and press
X TypeÞNONE
[SELECT].
2. Cursor to the “Area” field on the Top
LINK Menu and press [SELECT].
Limits
TAG
Area
Close Files
3. Move the cursor to the opposite

corner of the desired area, drawing
a box around the desired objects.
Top Menu Press [SELECT].
TypeÞNONE NOTE: If an object is part of a permanent
+ group, all objects in that group must be
included in the box. Otherwise, no part of
LINK Limits that group will be included in the area.
TAG
Area
Close Files
Figure 2.2.45. Joining Objects into Groups with the Area Operation

CC: 2-2-63
Grouping Objects—Group and Join Operations
Objects can be joined into permanent groups with the Group and Join
operations to perform display operations more efficiently. If a Move,
Copy, or Delete operation is performed on one object in a group, the
operation is performed on all objects in the group. There are different
menu paths for joining single objects or joining groups of objects.
Joining Single Objects
Once the Group command has been invoked, a single graphic object
will always display the Top Menu with the Join command, while grouped
objects will display the Split command in the same field. Join single
objects to a group as shown in Figure 2.2.46.
- To join single objects into a group:

Top Menu 1. Cursor to the first object that is to
TypeÞLINK be part of the group and press
Move Group [SELECT].
LINK Copy 2. Cursor to the “Group” field on the
Limits LinkEd Top Menu and press [SELECT].
Delete Top
TAG Bottom
Area
Close Files
3. Cursor to the next object that is to be

part of the group. Press [SELECT].
Top Menu 4. Cursor to the “Join” field on the Top
Menu and press [SELECT]. The object
TypeÞTAG is now joined to the group of objects.
Move Group
Copy Join 5. Repeat steps 3 and 4 for all objects that
Limits LinkEd are to be part of the group.
LINK Delete Top NOTE: Single objects can be added to the
Bottom group at a later time by doing steps 1 and 2
Area
Close Files for any existing object in the group, and then
TAG doing steps 3 and 4 for the new object.
Figure 2.2.46. Joining Single Objects into Groups

CC: 2-2-64
Joining Groups of Objects
To join two or more groups of graphic objects, you must join them as
individual elements, as shown in Figure 2.2.47 and Figure 2.2.48.
Group
TAG
- To join groups of objects together:
TEXT Top Menu 1. For each object in one group,
cursor to each object and press
TypeÞLINK [SELECT].
Move Group
Group Copy Split 2. Cursor to the “Split” Field on the
Limits LinkEd Top Menu and press [SELECT].
LINK Delete Top
Bottom NOTE: To minimize the number of
Merge Area commands, you should split the smaller
TAG Close Files group.
Group 3. Cursor to one element of the larger

group and press [SELECT].
TAG
Top Menu 4. Cursor to the “Group” field on the
TEXT Top Menu and press [SELECT].
TypeÞTAG NOTE: Always use the Group command
Move Group at the destination, and not at the element
Copy Split
Group Limits LinkEd you wish to group.
LINK Delete Top
Bottom
Merge Area
TAG Close Files
Figure 2.2.47. Joining Groups of Objects

CC: 2-2-65
Group
5. Return to the group you split. For
TAG each element you wish to connect
to the larger group, cursor to the
Top Menu “Join” field and press [SELECT].
TEXT
TypeÞTAG
Move Group
Copy Join
Limits LinkEd
Delete Top
LINK Bottom
Area
Close Files
TAG
Figure 2.2.48. Joining Groups of Objects

CC: 2-2-66
Grouping Objects—Merge Operation
A group of shape objects can be merged into a Thing object. To be

merged, a set of shape objects must have been joined into a permanent
group using the Group and Join operations. The objects must have
similar configuration characteristics, such as “Color” and “Cond” fields.
Thing objects are typically used to create symbols (see “Creating

Symbols” on page 2-2-19 for more information). A set of objects that
are merged into a Thing object takes up less memory than the same set
of objects that are joined into a group.
When the Merge operation has been performed on a group of shape

objects, a Thing object has been created. The individual shape objects
that were used to create the Thing object no longer exist and cannot be
split apart. The Thing object has one Top Menu and one Edit Object
Menu.
Figure 2.2.49 shows how to merge a group of shape objects into a

Thing object.
Top Menu
TypeÞBox
Move Group
Copy
Limits Split
Delete Top
Undo Bottom
Merge Area
Close Files
- To merge objects into a permanent group (a Thing object):

1. Cursor to an object in the group and press [SELECT].
2. Move the cursor to the “Merge” field of the Top Menu and
press [SELECT].
Figure 2.2.49. Merging a Group into a Permanent Thing Object

CC: 2-2-67
Using the Link Editor Field
The LinkEd field allows portions of process graphics to be linked to

different ControlBlock addresses. You can use the LinkEd option to
assign part of a process graphic to a different controller. The LinkEd
option makes it easy to duplicate a new unit, such as a reactor, or an
Area containing several units. Select the original, copy it, and use a
LinkEd to change the controller(s) that are used in the copy. See
Figure 2.2.50 for an example of the LinkEd field. Table 2.2.15 describes
the LinkEd functions
The LinkEd option is different from other options in the following way:
D The Move field moves objects on the same fabric.
D The Link Editor screen (see CC:2-3-9) allows whole graphics
fabrics (rather than just pieces) to be linked elsewhere.
D The LinkEd field on the Top Menu allows objects or areas to be
linked to different ControlBlock addresses. It otherwise performs
the same functions as the Link Editor screen.
PROCESS GRAPHIC GENERATION 20-DEC 93 08:22:13
+
- To link a selected object or area
with LinkEd:
Top Menu 1. Cursor to the object and press
[SELECT], or bound the area that
TypeÞNONE is to be linked.
Move
Copy
Limits
X
LinkEd
2. Cursor to the “LinkEd” field on the
Top Menu and press [SELECT].
Delete
Area
Close Files
Figure 2.2.50. Using the LinkEd Option to Link an Area

CC: 2-2-68
PROCESS GRAPHIC GENERATION 20-DEC 93 08:22:13
3. Cursor to the Source field

and enter the source range
of address and press
[ENTER].
4. Cursor to the Destination
field and key in the start tag
or address, then press
[ENTER].
5. Cursor to Proceed and press
[SELECT], or Close to
Cancel the operation.
Top Menu
6. Verify that the new links are
TypeÞNONE correct.
Move
Copy
Limits LinkEd
Delete
LinkEd
SourceÞ1A--3, =1A--5
Area
Close Files
DestinationÞ=12B--6
Close Proceed
- The operation above performs the following D 1A--3 becomes 12B--6

operations:
D 1A--4 becomes 12B--7
Changes the matching links in the bounded area:
D 1A--5 becomes 12B--8
Figure 2.2.50. Using the LinkEd Option to Link an Area (continued)
Table 2.2.15. LinkEd Functions
Field Description
Source Specifies the range of addresses to be changed. Separate ranges with a comma.
Destination Specifies the start of the changed (new) block addresses.
Close Closes the LinkEd menu without saving.
Proceed Changes the references to the Block(s) you specified.
NOTE: The LinkEd field changes only references to block links in the
process graphic file. It has no effect on actual block links in the specified
controllers.

CC: 2-2-69
Splitting an Object from a Group
Objects can be split from a group using the Split operation, as shown in
Figure 2.2.51. The Split operation removes only the selected object
from the group. To break up a group completely into its individual
objects, each object must be separately split from the group using the
procedure in Figure 2.2.51.
- To split an object from a group:

Top Menu 1. Cursor to the object that is to be
split from the group and press
TypeÞTAG [SELECT].
Move Group 2. Cursor to the “Split” field on the
Copy Split Top Menu and press [SELECT].
Limits LinkEd
LINK Delete Top
TAG Undo Bottom
Files
LINK Close
TAG
Figure 2.2.51. Splitting an Object from a Group

CC: 2-2-70
Undoing the Previous Operation
The Undo operation on the Top Menu undoes Move, Copy, Delete,
Group, Join, Split, Top, Bottom, or Merge operations. The Undo
operation also undoes operations made in the Edit Object Menu. You
must perform the Undo operation immediately after the operation that is
to be undone. Figure 2.2.52 shows an example of undoing a Delete
operation.
Top Menu
In this example, an
TypeÞTAG object has been deleted.
Move Group
Copy
Limits
Delete Top
LINK Undo Bottom
Area
Close Files
Top Menu
TypeÞTAG By selecting the Undo operation, the
Move Group Delete operation has been undone.
Copy
TAG Limits
Delete Top NOTE: The Undo operation must
Undo Bottom immediately follow the operation that is to
LINK
Area be undone.
Close Files
Figure 2.2.52. Undoing an Operation

CC: 2-2-71
Configuring Display Characteristics:

Process Graphics Fabric Coordinates
The fabric of a process graphics display is 16000 pixels high x 16000

pixels wide, as shown in Figure 2.2.53. A console screen display is 640
pixels wide x 448 pixels high.
0/0 0/16000
Coordinates of the
Process Graphic
fabric
16000/0 16000/16000
640 pixels wide
Graphics Viewing Dimensions of

one console
display
448 pixels high
Figure 2.2.53. Fabric Coordinates

CC: 2-2-72
Configuring Display Characteristics:

Changing the Panning Limits and Origin Point
A process graphic has display characteristics that can be configured for

the viewing mode. When the viewing mode of a process graphic is
called up, the origin point is the fabric location in the upper left corner of
the display. The default origin point is 0/0. That is, when the process
graphic is initially called up, fabric location 0/0 is in the upper left corner
of the display.
The panning limits are the top, bottom, left, and right edges of the
process graphic that the user is allowed to access when in viewing
mode. The default panning limits are TopÞ0, LeftÞ0, RightÞ640, and
BottomÞ448. They are the same size as a console display.
Figure 2.2.54 shows how to change the panning limits and the origin
point.
- PROCESS
To change a panning limit or GRAPHIC GENERATION
the origin 02-Feb-89 09:49:12
point:
1. Move the cursor to the desired point on Top Menu
the fabric (for example, the new top
edge). Press [SELECT]. The Top TypeÞNONE
Menu appears.
2. Move the cursor to the “Limits” field. Limits

Press [SELECT]. The Set Limits Menu
appears.
Files
Set Limits
Close
3. Move the cursor to the desired field and
press [SELECT]. The current cursor Origin Þ0/0
Top Þ25
position appears in the field as the new Bottom Þ448
limit. Left Þ0
Numbers cannot be entered into the Set Right Þ640
Limits Menu fields. When the cursor is Close
moved to a field and [SELECT] is
pressed, the new cursor location
coordinate is automatically entered into
the field.
LINK TAG
25/532
The first coordinate is the current vertical

location of the cursor, and it is associated with In the example, the user places the
the “Top” and “Bottom” fields. cursor on the “Top” field and presses
The second coordinate is the current [SELECT]. The current vertical
horizontal location of the cursor, and it is coordinate, 25, appears in the “Top” field.
associated with the “Left” and “Right” fields.
Figure 2.2.54. Changing a Panning Limit or the Origin Point

CC: 2-2-73
Creating Assists for Display Manipulation
The Pagefrwd, Pageback, and Text objects can be used to call up other
displays or, when used with the Anchor object, to move to another part
of the same process graphic. Table 2.2.16 describes the Pagefrwd,
Pageback, and Text objects.
In viewing mode the Pagefrwd and Pageback objects are not displayed,
but they still exist.
D When the [PAGE AHEAD] key is pressed, the command of the
Pagefrwd object nearest the upper left corner of the current
display is executed.
D When the [PAGE BACK] key is pressed, the command of the
Pageback object nearest the upper left corner of the current
display is executed.
Table 2.2.16. Display Manipulation Objects
Object Description
Can be configured to call up a display or move to another part of the same display if
Pagefrwd
the [PAGE AHEAD] key is pressed.
Can be configured to call up a display or move to another part of the same display if
Pageback
the [PAGE BACK] key is pressed.
Can be configured to call up a display or move to another part of the same display by
Text moving the cursor to the Text object, and pressing [SELECT]. The creation of the
Text object is described in the “Creating Text” heading in this section.

CC: 2-2-74
Creating Assists for Display Manipulation:

Objects that Call up Other Displays
- To create an object that calls up other displays:

1. Move the cursor to the desired location on the fabric. Press
2. Move the cursor to the “Type” field and press [SELECT]. The
Object Type Menu appears.
3. Move the cursor to the desired field (Pagefrwd, Pageback, or
Text) and press [SELECT]. The Edit Object Menu appears.
Figure 2.2.55 shows the Edit Object Menu for the Pagefrwd and
Pageback objects. The Text object Edit Object Menu is
described in the “Create Text” section on page 2-2-46.
Determines a command that is executed Edit Object Menu

when the associated key ( [PAGE AHEAD]
or [PAGE BACK] ) is pressed. Type PAGEBACK
The command can be any combination of
keystrokes that can be entered at the
command line. The command may also CommandÞ
be the number of an Anchor object.
For example, the command “G:1*” Close Top Menu

executes the keystrokes [G] [:] [1]
[ENTER] and calls up group display 1.
(The asterisk executes the [ENTER] key.)
For a list of command line options, see

Chapter 5 of this manual.
Figure 2.2.55. Edit Object Menu for Pagefrwd and Pageback Objects for Display Manipulation

CC: 2-2-75

Objects that Call up Another Part of the Same Display
The Anchor object allows part of a process graphic to be called up from

another part of the same graphic. The Anchor object is assigned a
number. If a Pagefrwd, Pageback, or Text object is configured with the
“Command” field entry the same as the Anchor object number, the
Pagefrwd, Pageback, or Text object calls up the part of the process
graphic with the Anchor object at its center, as shown in Figure 2.2.56.
In addition, the anchor number can be used in the command line to call
up a process graphic. For example, the command “PG:,PLANT.3” calls
up the part of the process graphic Plant with anchor number 3 at its
center.
1. When [PAGE AHEAD] is

pressed and the nearest
Pagefrwd object is linked to
Anchor number 1,
2. A new viewing area is
displayed that has Anchor
object number 1 at its center.
PAGEFRWD 1
ANCHOR 1
The Pagefrwd and Anchor objects

exist on the Process Graphic but are
not displayed.
Figure 2.2.56. Use of Anchor Object

CC: 2-2-76
- To create objects that call up another part of the same display:

1. Create one or more Pagefrwd, Pageback, or Text objects that will
be used to call up the desired part of the process graphic. (See
“Creating Objects That Call Up Other Displays” on page 2-2-74.)
2. Move the cursor to the center of the viewing area that will be
called up. Press [SELECT]. The Top Menu appears.
3. Move the cursor to the “Type” field and press [SELECT]. The
4. Move the cursor to the ANCHOR field and press [SELECT]. The
Figure 2.2.57 shows the Edit Object Menu for the Anchor object.
Figure 2.2.58 shows an example of using a Pageback object and
an Anchor object to call up another part of a display.
Determines the number of the Anchor Edit Object Menu

object. A Process Graphic should not
contain multiple Anchor objects with the Type ANCHOR
same number.
NumberÞ
To have the part of the Process Graphic
with this Anchor object in the center
called up, a Pagefrwd, Pageback, or Text
object must have this Anchor number
specified in its “Command” field. Close Top Menu
Figure 2.2.57. Edit Object Menu for Anchor Object
Edit Object Menu Edit Object Menu

Type ANCHOR Type PAGEBACK
NumberÞ3 CommandÞ3
Close Top Menu Close Top Menu
As an example, a graphic display is configured with one

Pageback object that has “CommandÞ3”.
The graphic display also has an Anchor object with
“NumberÞ3”.
When the [PAGE BACK] key is pressed, the console displays
the portion of the process graphic fabric that includes the
Anchor object. The Anchor object is at the center of the
screen.
Figure 2.2.58. Example Use of Anchor Object

CC: 2-2-77

Display Targets
The Target object enables quick cursor positioning on a process

graphic. The Target object consists of one alphanumeric character that
is displayed on the graphic. Whenever the key for that character is
pressed while viewing the process graphic, the cursor moves to the
Target object. The Target object operates regardless of what portion of
the process graphic is displayed.
Figure 2.2.59 shows an example of a process graphic display that uses

Target objects to easily move around the display.
Target objects are used in this example to provide quick access to

objects on the Process Graphic.
When a number is pressed, the cursor moves to that number and
displays that part of the fabric.
1
2
3
4
5
Figure 2.2.59. Example Use of Target Objects

CC: 2-2-78
- To create a display target:

1. Move the cursor to the desired location of the Target object.
2. Move the cursor to the ”Type” field and press [SELECT]. The
3. Move the cursor to the Target field and press [SELECT]. The
Figure 2.2.60 shows the Edit Object Menu for the Target object
and Table 2.2.17 explains the fields on the screen.
Edit Object Menu

Type TARGET CharÞ
CondÞ
BlockÞ
Close Top Menu
Figure 2.2.60. Edit Object Menu for Target Object
Table 2.2.17. Screen Fields on the Edit Object Menu for Target Object
Field Description
Block Determines the tag or address of the block that is displayed if the object is selected.
Char Determines the single alphanumeric character that forms the target.
Color
Cond

CC: 2-2-79

Hiding Parts of the Display Using an Icon Object
The Icon object allows you to hide a group of objects from view until the
operator chooses to display the group. The Icon object appears as a
line of text. It can be grouped or joined with any number of other
objects. When you cursor to the Icon object and press [SELECT], the
group of objects appears. Pressing [SELECT] again causes the objects
to disappear.
NOTE: If you move an object that is grouped with an Icon object, all of
the objects in the group also move.
- To create an icon:
1. Move the cursor to the desired location of the Icon object. Press
2. Move the cursor to the “TypeÞNONE” field and press [SELECT].
Icon object appears in configuration mode.
Object Menu.
5. If you want, use the Group and Join operations on the Top Menu
to create the desired group of objects. Include the Icon object in
the group. See “Grouping Objects—Group and Join Operations”
on page 2-2-60.

CC: 2-2-80
ICON
Figure 2.2.61. How the Icon Object is Displayed
Figure 2.2.62 shows the Edit Object Menu for the Icon object and
Table 2.2.18 explains the fields on the screen.
Edit Object Menu

Type ICON
CondÞ
Initial View ModeÞOFF
Title of the Alarm FontÞNormal Edit TextÞ
object to which the
Al Obj Tanklev
Icon object is linked—
Tanklev Close Top Menu
Figure 2.2.62. Edit Object Menu for Icon Object

CC: 2-2-81
Table 2.2.18. Screen Fields on the Edit Object Menu for Icon Object
Field Description
Blink Determines whether or not the group of objects blinks.
Color
If the Icon object is linked to an alarm, the Icon object has the color configured for the
alarm, not to be confused with the color configured for the Alarm object.
Determines whether the objects grouped with the Icon object are displayed in the on
Initial View Mode
state or off state when initially called up. The default is Off.
Determines a condition that affects how the object is displayed. This refers to the
display of the Icon object only, not the display of the objects that might be grouped
Cond with the Icon object. See “Configuring the Appearance of Objects to Change” on
page 2-2-54.
When the condition is false, the Icon object is not displayed.
Edit Text Allows text to be entered.

Title of the Alarm object to which the Icon object is linked, if any. This field is for
Al Obj display only; it is not enterable. This field is displayed only when an Alarm object is
joined with an Icon object.

CC: 2-2-82
Copying a Process Graphic
A process graphic can be copied to the same volume or to another

volume. Figure 2.2.63 shows the procedure.
Top Menu - To copy a graphic:

TypeÞNone 1. Cursor to any location on the
fabric and press [SELECT].
2. Cursor to the “Files” field and
Limits press [SELECT]. The File
Area Operations Menu appears.
Close Files
3. Cursor to the “Write” field.

4. Type in the volume and filename
of the new Process Graphic.
Press [ENTER]. The new
File Operations graphic has been created.
5. Reenter the volume and
ReadÞvolume,filename.pg
filename of the current Process
WriteÞvolume,filename.pg Graphic. Press [ENTER].
CAUTION
Close If the volume and filename are not
changed back to the current
graphic, any changes made from
this point until the user leaves the
graphics generation screen are
written to the new file and not to the
current graphic file.
Figure 2.2.63. Copying a Process Graphic

CC: 2-2-83

Bface Object
Batch task information can be configured as part of a process graphic

with the Bface object. The Bface object allows the user to perform
Batch Run screen functions from a process graphic. For information
about the Bface object characteristics, see BA: 1.
- To create the Bface object:
3. Move the cursor to the “Bface” field and press [SELECT]. The
Edit Object Menu appears. Figure 2.2.64 shows how the Bface
object appears in configuration mode.
Object Menu.
BFACE
BFACE
BFACE
BFACE
BFACE
BFACE
Figure 2.2.64. How the Bface Object Appears in Configuration Mode

CC: 2-2-84
- To configure the Bface object characteristics:

the Edit Object Menu, as shown in Figure 2.2.65 and
Table 2.2.19. Move the cursor to the desired field and press
[SELECT]. Another menu appears.
Edit Object Menu

Type BFACE SizeÞ4 Þ1
CondÞ
TaskÞ30:1 Edit Items
Close Undo Top Menu
Figure 2.2.65. Edit Object Menu for the Bface Object
Table 2.2.19. Screen Fields on the Edit Object Menu for the Bface Object
Field Description
Determines the color of the data in the Bface object. The color choices are
Color
configured on the Master Color Selection screen ( [C] [C] [P] command).
Determines a condition that determines the object is displayed. See “Configuring the
Cond
Determines the items that are included in the Bface object. When this item is
selected the Batch Edit Items Menu appears. Moving the cursor to an arrow on the
menu and pressing [NEXT OPTION] shows the possible entries for the Bface object.
Edit Items
The entries are parameters for the specified task. For more information about Bface
objects and the parameters, see BA: 1.
Determines the size of the Bface object and how the data lay out.
D Num Col determines the number of columns of information (1--3).
Size
D Num row determines the number of rows of information (1--10). The actual
size of the Bface object is two rows more than the Num row field.
Task Determines the batch task in the form “node:task”.

CC: 2-2-85
Alarm Annunciation on Graphics
The way that alarms are announced on graphics varies for different
types of graphic objects.
Alarm Object
The Alarm object title shows the alarm condition of the highest priority
alarm in the Alarm object.
Icon Object
The alarm annunciation for an Icon object depends on whether the Icon
object is linked to an Alarm object.
D If a group containing an Icon object also contains one Alarm
object, the Icon object shows the alarm condition of the Alarm
object.
D If a group containing an Icon object also contains more than one
Alarm object, the Icon object shows the alarm condition of the
Alarm object that is configured in the “Al Obj” field of the Icon Edit
Object Menu.

CC: 2-2-86

That Have Been Converted from Character Graphics
The Configure Character screens are useful only for users who have
converted from earlier software version character graphics to pixel
graphics. If a process graphic is converted from character graphics to
pixel graphics, you must also convert any user--defined characters used
in the graphic. However, the user--defined characters may not appear
the same in pixel graphics as they did in character graphics. The
Configure Character screens allow the user to reconfigure the
user--defined characters. Figure 2.2.66 shows a blank Configure
Character screen.
Pixel graphics does not allow the user to add any user--defined
characters to a graphic. The Configure Character screens ([P] [G] [C]
command) are provided for those users who want to continue using the
user--defined characters that are already configured in their graphics. If
the appearance of a process graphic changes after conversion to pixel
graphics because user--defined characters have changed, the process
graphic can be modified in two ways:
D Method 1—preferred method. Use pixel graphics to recreate the
desired graphic shape. Instead of reconfiguring the user--defined
characters, simply delete them and use the pixel graphics shape
objects to configure the desired shape.
D Method 2—Use the Configure Character screens to reconfigure
the shape of each user--defined character used in process
graphics.
It is usually easier to reconfigure the desired part of a display
with the added functionality of pixel graphics than it is to
reconfigure each user--defined character.
NOTE: In documentation for earlier software versions, pixel graphics

were sometimes referred to as vector graphics.

CC: 2-2-87
A character is made up of pixels. The pixel is the smallest portion

of the screen that can be discretely displayed. Each pixel is either
displayed or not displayed to create a character.
- To clear the character
(no pixels displayed): - To change whether or not
D Press [ENTER]. a pixel of a character is
-
displayed:
To fill the character (all Shows how the
pixels displayed): D Move the cursor to the
desired location and character appears on
D Press [ENTER]. press [ENTER]. a graphic display.
CONFIGURE CHARACTER 25-Feb-89 1:47:12

Character Number >355 Set 6:35 Character
Clear Fill
Þ Þ Þ Þ Þ Þ Þ Þ
Þ Þ Þ Þ Þ Þ Þ Þ Composite Display
Þ Þ Þ Þ Þ Þ Þ Þ ® ® ® ® ®
Þ Þ Þ Þ Þ Þ Þ Þ ® ® ® ® ®
Þ Þ Þ Þ Þ Þ Þ Þ ® ® ® ® ®
Þ Þ Þ Þ Þ Þ Þ Þ ® ® ® ® ®
Þ Þ Þ Þ Þ Þ Þ Þ ® ® ® ® ®
CONFIG 1
Figure 2.2.66. Configure Character Screen

CC: 2-3-1
Section 3:
Optimizing Graphics Performance
The size of the graphic file and refresh rates can affect the performance
of the process graphic. Anything you can do to make the process
graphic smaller or more consistent with the response time of the CP
and controller processors will improve its performance.
RS3: Process Graphics Optimizing Graphics Performance

CC: 2-3-2
Process Graphic Limits
Table 2.3.1 list process graphic parameters and their corresponding

limits. You should be aware that running a process graphic near the
parameter limits reduces console memory available for graphic
performance.
Table 2.3.1. Parameter Limits
Parameter Limit
Graphic Fabric 16000 pixels high by 16000 pixels wide
Graphic File 25 Kilobytes (24 Kilobyte maximum practical size)
Block Links 64 block links
Object Overhead 32 bytes
Field Refresh Rate 0.25 to 2 seconds
Screen Refresh Rate 0.25 to 20.0 seconds

CC: 2-3-3
Link Count Field
To determine how many ControlBlock links exist in a process graphic,

use the Link Count field.
Top Menu
TypeÞTHING -
Move Group To use Link Count field:
Copy 1. Press “select” anywhere
Limits LinkEd on the graphic.
Delete Top
Undo Bottom 2. Cursor to the “Files” field
Area and press [SELECT].
Close Files
File Operations 3. Cursor to the “Link Count”

field.
ReadÞvolume,filename.pg
4. Select.
WriteÞvolume,filename.pg The number of block links
used by the graphic will
appear at x.
SymbolÞ
Close LinkCount x
Figure 2.3.1. Using the Link Count Field
You may have up to 64 block links per graphic. For graphics with many
links to the same ControlFile, consider optimizing by using
funnel blocks.

CC: 2-3-4
Using Funnel Blocks
You can use a ControlBlock called a funnel block to reduce the number
of ControlBlock links per process graphic. A funnel block brings links
from several different blocks in to the process graphic. The process
graphic counts all registers from the funnel block as one link, so that
only one out of 64 links are consumed. Figure 2.3.2 shows how
funneling works.
NOTE: Funnel blocks are most useful if the links being funneled are for
blocks in the same ControlFile as the funnel block. When ControlBlocks
are in other ControlFiles on the PeerWay, the advantage of funneling is
offset by the use of valuable PeerWay links.
The Process Graphic counts all registers of

the funnel block as one link.
ControlBlock Process Graphic

Continuous Links
Tag> Funnel Funnel/A
A > =99A-01
B > =99A-05 Funnel/B
C > =99A-20 File Operations
D > Funnel/C
E > Read > DOC,LINK_GR
F > Write> DOC,LINK_GR
G >
Close Link Count 1
Figure 2.3.2. Funnel Block Concept

CC: 2-3-5
Merging Objects
You can merge a group of objects together to create a complex object

called a Thing object. A set of objects that are merged into a Thing
object take up less memory than the same objects would take up
individually. Using fewer objects also reduces the screen refresh time.
Individual objects are assigned 32 bytes of overhead and additional

space for the object description. The Thing object reduces overhead by
32 bytes for each object merged. Objects copied from the Thing object
use even less memory, because the copied objects share the same
description with the original Thing object.
Individual objects do not need to be visually connected on the screen to

be merged together into a Thing object. You can merge objects scattered
around the screen. See page 2-2-66 for more merge information.
NOTE: Since you cannot separate merged objects, you might want to
save a copy of the unmerged objects in a separate file for editing.

CC: 2-3-6
Other Methods of Optimizing Graphics
The following are recommendations for constructing and maintaining

graphics to use console memory efficiently:
Wide lines There are two ways to construct lines that are more
than one pixel wide:
D Draw multiple lines parallel to each other.
D Configure a narrow box as a solid shape.
A box line uses less memory than multiple lines. If

you use multiple lines, merge them into a Thing
object.
Invisible Use invisible objects sparingly. Invisible objects are

objects often useful for hiding pieces of other objects, but
increase the byte size of the graphic. Wherever
possible, construct objects differently to reduce the
number of objects required.
Unused Remove unused objects from the process graphics.

graphics It is easy to overlook text and link objects that do
not have any size, since these objects are indicated
on the screen by only a single pixel. To find these
objects, press the [NEXT OPTION] key to move
from one object to another.

CC: 2-3-7
Preconfigured Process Graphics
The Process Graphics folder contains five files of commonly used

graphic icons, such as valves, motors, boilers, and other process
symbols. These icons have been designed to provide you with
preconfigured process graphics with a minimum waste of space and
graphics capabilities.
You can select preconfigured icons from the following files to create
graphic symbols:
D $Readme
D $Stdsym
D $SymbolS1
D $SymbolS2
D $SymbolS3
For information on creating symbols, see “Creating Shapes: New

Symbols” on page 2-2-19.

CC: 2-3-8
Screen Refresh and Field Refresh
Refresh rates specify the maximum rate at which the console can
request data from the controller. Screen Refresh refers to length of time
required to refresh all data points on the graphic. Field refresh refers to
the length of time required to refresh data for a particular data point or
field on the process graphic.
The screen refresh and field refresh rates are set on the Console
Configuration screen. The screen refresh rate is intended to slow data
requests to prevent excess data request messages from overwhelming
the controller and flooding the PeerWay. You can set the field refresh
rate to a higher speed than the screen refresh rate to maintain faster
response times for select data items.
- To refresh individual fields:
D Move the cursor to that field. The field thus selected will refresh
at the field refresh rate instead of the screen refresh rate.
For more information on refresh rates, see “Configuring Refresh and
Advance Request Rates” on page 1-1-30.

CC: 2-3-9
Graphics Link Editor
The Graphics Link Editor is used to edit block link addresses in process
graphics files. The Link Editor screen is useful for:
D Changing process graphic links so that you can use the same
graphic with different controllers.
D Maintaining duplicate process graphics on different PeerWay
nodes.
D Updating graphics to match address changes in the PeerWay or
ControlFile. (For example, you would use this if HIAs are used to
split a single Peerway into two PeerWays.)
You can change a range of block link addresses using the “Address
Range” and “New Address” fields. For example:
D Change PeerWays: =1,=1H--99
to =33
D Change PeerWay Nodes: =1A,=1A--99
to =2A
D Change controller cards: =1A,=1H--99
to =2A
D Change ControlBlocks: =1A--10,=1A--10
to =1A--40
NOTE:
D The Link Editor changes only references to block links in the
process graphic file. It has no effect on actual block links in the
specified controllers.
D You cannot change the range of an I/O card cage.

CC: 2-3-10
Calling Up the Link Editor Screen
Figure 2.3.3 shows the Link Editor screen.

- To call up the Link Editor screen, type:
L E
or
L E (node) [:] (drive)
Source File. Name of the file used to Address Range. Current address range of
modify block link references. links to be edited or listed. You can specify a
range by PeerWay node and controller
processor card numbers.
Destination File. The file in which the New Address. New address range of links
block link references are actually modified. after editing. You can specify a range by
Unless otherwise specified, the destination PeerWay node and controller processor card
file is the same as the source file. numbers.
LINK EDITOR 07-Mar-92 14:35:19
Console Node 68
Disk Name WINI Unmodified Address
At Node 60 On Drive 1
LINK:,=1A-01
Source File Þ Plant_X Process Graphics LINK:,=1A-02
LINK:,=1A-03
Destination File Þ Plant_X LINK:,=1A-10
LINK:,=10A-50
Address Range Þ 1A-1,1A-99
New Address Þ 2A
Operation Edit Graphic Display
Edit Mode Þ List
Þ Press <ENTER> to Begin
Edit Mode. The Link Editor has two operation modes: These addresses appear on
the screen in “List” mode only.
Modify Changes the address of the “Address Range” field
as specified in the “New Address” field.
Press [SELECT] on the “Process
List List the block links used in the process graphics file Graphics” field to call up the
in the ‘unmodified address’ window on the right. Process Graphics Directory.
Figure 2.3.3. Link Editor Screen

CC: 2-3-11
Procedure: Editing Link Addresses

- To edit link addresses:
Step Operation Description
1 Action: Call up the Link Editor screen. Type:

L E (node) [:] (drive)
Response: The Link Edit screen appears.
2 Action: Enter the name of a process graphic file in the “Source File” field.
Comments: · To scroll through available filenames in the Process Graphics folder, press the
[NEXT OPTION] key on the field.
· The name of the process graphic file appears in both the “Source File” field
and the “Destination File” field.
· To call up the process graphic file, press [SELECT] on the “Source File” field.
3 Action: If you do not want to use the source file as the destination file, enter a different
process graphic file in the “Destination File” field.
Comments: Choosing a different destination file is useful if you are maintaining duplicate
process graphics on different PeerWay nodes.
4 Action: Enter the current link address range for the process graphic file in the “Address
Range” field.
Comments: The address range consists of the PeerWay node and controller processor card
numbers. Use the format:
=1A (where 1 is the PeerWay node and A is the controller processor card.)
The address range must match the actual address range used by the process
graphic file.
5 Action: Enter the new link address range for the process graphic file in the “New
Address” field.
Comments: The address range consists of the PeerWay node and controller processor card
numbers. Use the format:
=1B (where 1 is the PeerWay node and B is the controller processor card.)

CC: 2-3-12
- To edit link addresses:

Step Operation Description
6 Action: Cursor to the “Edit Menu” field. Press the [NEXT OPTION] key to toggle the “Edit
Mode” field between two operations, “Modify” or “List”.
Comments: Edit Mode operations:
List Lists the current block links used in the process graphic file. The list
appears in a pop--up window in the upper--right corner of the screen.
Modify Changes the address of the “Address Range” field as specified in
the “New Address” field.
NOTE: If the address range in the “Address Range” field does not match the
actual address range used by the process graphic, the Edit operation will fail.
The following message is displayed:
No update: Address is out of range
7 Action: Cursor to the “Press <ENTER>” field and press [ENTER] to execute the
operation specified in the “Edit Menu” field.
The operation is complete when the “Press <ENTER>” field reappears.

RS3t
Chapter 3:
Reports
Section 1: Introduction to Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1-1
Section 2: The Report File Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2-1

The Report Read Directory Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2-3
The Report File Contents Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2-4
The Report Read/Scan Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2-5
The Report Config Directory Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2-6
The Report Status Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2-8
Section 3: Designing a Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3-1

Assembling Information for a Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3-1
Dimensions of a Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3-2
Formatting the Report for Printing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3-3
Section 4: Configuring a Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4-1

The Report Configuration Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4-2
Report Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4-5
Using Report Objects to Configure Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4-8
Editing the Body of a Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4-9
Configuring How a Report is Printed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4-10
How to Determine Report Print Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . 3-4-10
How to Begin a New Report Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4-11
Configuring Text in a Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4-12
How to Print Regular--sized Text . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4-12
How to Print Oversized Text . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4-13
Configuring Operator Comments in a Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4-14
Configuring Block Information in a Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4-15
How to Configure a Block Tag . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4-15
How to Configure a Block Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4-16
How to Configure a Block Descriptor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4-17
How to Configure a Block Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4-18
How to Configure a Block Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4-19
How to Configure Block Units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4-20
How to Configure Block Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4-21
How to Perform Calculations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4-22
RS3: Reports Contents

CC: ii
How to Configure Trend File Information in a Report . . . . . . . . . . . . . . . . . . . . . . . 3-4-26

How to Use an Accumulator with a Trend Log Object . . . . . . . . . . . . . . . . . . . . 3-4-31
Configuring Time and Date Information in a Report . . . . . . . . . . . . . . . . . . . . . . . . 3-4-32
How to Configure the Current Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4-32
How to Configure the Current Date . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4-33
Configuring Console Lists in a Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4-34
Configuring the List Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4-35
Formatting a List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4-35
How to Configure Another Report in a Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4-37
Generating Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4-39
How to Generate a Report Based on Time and Date . . . . . . . . . . . . . . . . . . . . 3-4-39
How to Generate a Report Based on Alarms or Events . . . . . . . . . . . . . . . . . . 3-4-41
How to Generate a Report from the Report Configuration Screen . . . . . . . . . 3-4-42
How to Print a Report When it is Generated . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4-43
Section 5: Saving a Report to Disk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5-1
Section 6: Hints for Configuring and Using Reports . . . . . . . . . . . . . . . . . . . 3-6-1

Marking Lines in Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6-3

CC: iii
List of Figures
Figure Page
3.2.1 Report Folders and Report Screens . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2-2
3.2.2 Report Read Directory Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2-3
3.2.3 Report File Contents Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2-4
3.2.4 Report Read/Scan Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2-5
3.2.5 Report Configuration Directory Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2-7
3.2.6 Report Status Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2-8
3.3.1 Report Sample Layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3-1
3.3.2 Visible Report Screen Dimensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3-2
3.3.3 Sizing a Report Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3-3
3.4.1 Report Configuration Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4-2
3.4.2 Report Configuration Screen with Report Configuration
Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4-5
3.4.3 Report Configuration Window with Fields . . . . . . . . . . . . . . . . . . . . . . . . 3-4-8
3.4.4 Report Configuration Screen with Print Object . . . . . . . . . . . . . . . . . . . . 3-4-10
3.4.5 Report Configuration Screen with Newpage Object . . . . . . . . . . . . . . . . 3-4-11
3.4.6 Report Configuration Screen with Text Object . . . . . . . . . . . . . . . . . . . . 3-4-12
3.4.7 Report Configuration Screen with Banner Object . . . . . . . . . . . . . . . . . . 3-4-13
3.4.8 Report Configuration Screen with Comment Object . . . . . . . . . . . . . . . . 3-4-14
3.4.9 Report Configuration Screen with Tag Object . . . . . . . . . . . . . . . . . . . . . 3-4-15
3.4.10 Report Configuration Screen with Address Object . . . . . . . . . . . . . . . . . 3-4-16
3.4.11 Report Configuration Screen with Descriptor Object . . . . . . . . . . . . . . . 3-4-17
3.4.12 Report Configuration Screen with Function Object . . . . . . . . . . . . . . . . . 3-4-18
3.4.13 Report Configuration Screen with Mode Object . . . . . . . . . . . . . . . . . . . 3-4-19
3.4.14 Report Configuration Screen with Unit Object . . . . . . . . . . . . . . . . . . . . . 3-4-20
3.4.15 Report Configuration Screen with Value Object . . . . . . . . . . . . . . . . . . . 3-4-21
3.4.16 Report Configuration Screen with Value and Accumulator
Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4-23
3.4.17 Report Configuration Screen with Value Objects . . . . . . . . . . . . . . . . . . 3-4-24
3.4.18 Report Configuration Screen with Accumulator Object . . . . . . . . . . . . . 3-4-25
3.4.19 Report Configuration Screen with Trend Log Object . . . . . . . . . . . . . . . 3-4-26
3.4.20 Sample Trend Log Object Configuration Window and
Resulting Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4-27
3.4.21 Sample Trend Log Object Configuration Window and
Resulting Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4-28

CC: iv
3.4.22 Report Configuration Window with Trend Log Object

and Accumulator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4-31
3.4.23 Report Configuration Screen with Time Object . . . . . . . . . . . . . . . . . . . . 3-4-32
3.4.24 Report Configuration Screen with Date Object . . . . . . . . . . . . . . . . . . . . 3-4-33
3.4.25 Report Configuration Screen with List Object . . . . . . . . . . . . . . . . . . . . . 3-4-35
3.4.26 Report Configuration Screen with Generate Object . . . . . . . . . . . . . . . . 3-4-37
3.4.27 Generating a Report Based on Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4-39
3.4.28 Generating a Report Based on Date . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4-40
3.4.29 Generating a Report Based on Alarms and Events . . . . . . . . . . . . . . . 3-4-41
3.4.30 Report Configuration Screen with Generate this Report
Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4-42
3.4.31 Report Configuration Screen with Auto Print Field . . . . . . . . . . . . . . . . . 3-4-43

CC: v
List of Tables
Table Page
3.4.1 Report Configuration Screen Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4-3
3.4.2 Report Object Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4-6
3.4.3 Editing Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4-9
3.4.4 Trend Log Field Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4-29
3.4.5 List Object Configuration Screens . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4-36
3.4.6 Generate Field Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4-38

CC: 3-1-1
Section 1:
Introduction to Reports
Reports are user--configured displays of information that provide

pertinent information about system process variables. A report
consists of report configuration and report generation. Up to 200
reports can be configured on a single command console. Each
configured report can have up to 100 report generations. The
maximum number of reports on a console varies depending on the
amount of available memory. Reports may be generated on the basis
of time, alarms, events, or operator commands.
Reports are usually configured to be printed, but they may be simply

displayed on the console screen. A report may be printed
automatically when it is generated, or several copies of a report may be
accumulated on the disk and printed when requested by an operator.
For information about SQC report objects, see SR:3.
RS3: Reports Introduction to Reports

CC: 3-2-1
Section 2:
The Report File Structure
Two disk folders are used by the report subsystem:

D The Report Config folder stores the configuration entries for all
reports to be generated by the console.
D The Reports folder stores the report generations.
When a configured report is generated, a corresponding report file

appears in the Reports folder. The Report Config folder is created the
first time a report configuration is saved to the disk. A Reports folder is
created the first time that a report is generated. Figure 3.2.1 shows the
relationship between the Report Config and the Reports folders and the
corresponding report screens.
Configured report activity and generated report activity is contained on

the Report Status screen.
RS3: Reports The Report File Structure

CC: 3-2-2
- To access the next level:

1. Highlight the folder or report file selection and press [SELECT].
The Reports Config folder on The Reports folder on the Disk

the Disk Directory PeerWay Directory PeerWay screen
screen contains configuration contains report generation files.
Report Config Reports
files for each report.
The Report Config REPORT The Report Read

Directory screen REPORT CONFIG Directory contains a list
DIRECTORY READ
contains a list of the DIRECTORY of report generation files.
report configuration files. SCREEN
SCREEN
REPORT FILE The Report File

CONTENTS Contents screen
SCREEN contains a single
report’s generation
history.
The Report Config REPORT REPORT The Report

screen contains a CONFIG READ/SCAN Read/Scan
configured report. SCREEN SCREEN screen contains
a generated
report.
Figure 3.2.1. Report Folders and Report Screens

CC: 3-2-3
The Report Read Directory Screen
The Report Read Directory screen provides a list of all reports that have
been generated. Figure 3.2.2 shows an example of a Report Read
Directory screen with field descriptions.
- To call up the Report Read Directory screen:
D Highlight the Report folder on the Disk Directory screen and

press [SELECT].
or
D Type:
RRD: [ENTER]
Sort Criterion = Sorts the directory to one
of the directory columns
Disk Name= Disk where volume is currently located Sort Order = Ascending or descending
At Node = Node number where volume is currently located files
On Drive = Drive number where volume is currently located Start = Searches for file
Free Bytes= Space available in folder name—enter a number
or /xxx/, where xxx is one
or more characters
Report Read Directory 04-Aug-92 18:06:09
Disk Name WINI-C55 At Node 18 On Drive 1

Free Bytes 1958656
Sort Criterion Þ Filename Sort Order ÞAscending StartÞ1
Filename Size Modification Time Max# Node Autoprint# Rpts Unprint
------------------------------------------------------------------------------
#1B-LOG1 48384 04-Feb-89 17:31:50 32 6 Y 1 0
Blr-MnRun 33280 01-Feb-89 09:40:29 10 0 N 10 10
SNY 3584 03-Jan-89 09:41:46 63 2 N 1 1
* END *
CONFIG 3
Autoprint = If “Y“, a report is printed and

Filename = User--assigned filename saved to disk when generated; if
Size = Size in bytes of the file “N“ the report is written to disk.
Modification Time Last time and date file was modified, #Rpts = Number of report generations
if ever Unprint = Reports that are generated but
Max = Maximum number of report generations not printed
Node = Print node
Figure 3.2.2. Report Read Directory Screen

CC: 3-2-4
The Report File Contents Screen
The Report File Contents screen lists all generations of an individual

report. Figure 3.2.3 shows an example of a Report File Contents
screen with field descriptions.
- To call up the Report File Contents screen:
D Highlight a report file on the Report Read Directory screen and
press [SELECT].
or
D Type:
RFC ( , report_name) [ENTER]
Disk Name = Disk where the volume is currently located

At Node = Node number where volume is currently located
On Drive = Drive number where volume is currently located
Report Name = User--configured report name
Created on = Date and time file was first written to disk
Last Modified = Last date and time file was changed
Last Backup time =Last time and date file was backed up, if ever
#Ent = Latest report generation (1) to earliest report generation
Prted? = Specifies if the report was printed
Node = Print node
Size = Size in bytes of the report configuration file
Pages = Number of pages of a report
Lines = Number of lines in a report
Generated = Date and time the report started generation
Completed = Date and time the report completed generation
Report File Contents 04-Aug-92 18:06:09

Report Name> Size15360
Created on 01-Feb-89 17:24:22 Last Modified 02-Feb-89 11:09:45
Last Backup Time 02-Feb-89 12:12:36
#Ent Prted? Node Size Pages Lines Generated Completed
-----ENTER-to-print--------------SELECT-to-read----------CTRL-d-to-delete-------
1 Yes 6 46768 5 308 02-Feb-89 03:12:15 02-Feb-89 06:15:24
2 No 6 45555 5 300 01-Feb-89 05:12:15 01-Feb-89 06:15:24
3 No 6 46000 5 302 01-Feb-89 03:12:15 01-Feb-89 04:15:24
4 Yes 6 46768 5 308 01-Feb-89 02:12:15 01-Feb-89 02:15:24
**END**
CONFIG 3
Figure 3.2.3. Report File Contents Screen

CC: 3-2-5
The Report Read/Scan Screen
The Report Read/Scan screen contains a copy of a generated report.

Figure 3.2.4 shows an example of a Report Read/Scan screen with field
descriptions. If a report is very long, the Report Read/Scan screen may
not be able to display all the lines of the report.
- To call up the Report Read/Scan screen:
D Highlight a report file on the Report File Contents screen and
press [SELECT].
or
D Type:
RR: ( , report name) [ENTER]
Filename = User--configured report name

Print entry = Entry number on the Report File
Contents screen
Generated on = Date and time the report was generated
Lines = Number of lines in the report
Report Read/Scan 02-Aug-92 14:23:47

Filename : Þnode 44-1 Print entry #Þ1 (1 = newest, 99 = oldest entry)
Generated on 02-Feb-89 from 14:22:21 to 14:22:22 Lines : 8
********* END-OF-FILE *********
Figure 3.2.4. Report Read/Scan Screen

CC: 3-2-6
The Report Config Directory Screen
The Report Config Directory screen provides a list of all reports that
have been configured. A report listed on this screen can be selected
and copied to be used as a format for multiple reports. Figure 3.2.5
shows an example of a Report Config Directory screen with field
descriptions.
Individual report configuration screens are called up from the Report

Config Directory screen. For more information about the Report
Configuration screen, see page CC:3-4-2
- To call up the Report Config Directory screen:
D Highlight the Report Config folder on the Disk Directory screen
and press [SELECT].
or
D Type:
RCD [ENTER]
- To call up a Report Configuration screen:
D Cursor to a selected report file on the Report Config Directory
screen and press [SELECT].

CC: 3-2-7
Sort Criterion = Sorts the directory to one

of the directory columns
Disk Name = Disk where volume is currently located Sort Order = Ascending or descending
At Node = Node number where volume is currently files
mounted Start = Searches for file name----
On Drive = Drive number where volume is currently enter a number or
mounted /xxx/where xxx is one or
Free Bytes = Space available in folder more characters
Report Config Directory 04-Aug-92 15:32:16

Free Bytes 1968128
Sort Criterion Þ Filename Sort Order ÞAscending StartÞ1
Filename Size Modification Time Max# Node Autoprint Active
-------------------------------------------------------------------------------
#1B-LOG1 4352 04-Feb-89 14:25:12 32 6 Y Y
#1B-LOG2 3072 03-Feb-89 09:40:29 32 6 Y Y
#1B-LOG3 3072 03-Feb-89 09:41:46 32 6 Y Y
#2B-LOG1 2816 03-Feb-89 09:42:37 32 6 Y Y
#2B-LOG2 2816 03-Feb-89 09:43:52 32 6 Y Y
#2B-LOG3 3072 03-Feb-89 09:44:43 32 6 Y Y
#3B-LOG1 2816 03-Feb-89 09:45:23 32 6 Y Y
#3B-LOG2 3072 03-Feb-89 09:46:12 32 6 Y Y
#3B-LOG3 3072 03-Feb-89 09:47:34 32 6 Y Y
#4B-LOG1 2816 03-Feb-89 09:52:17 32 6 Y Y
#4B-LOG2 3072 03-Feb-89 09:53:29 32 6 Y Y
#4B-LOG3 3072 03-Feb-89 09:54:35 32 6 Y Y
#5B-LOG1 2816 03-Feb-89 09:55:26 32 6 Y Y
#5B-LOG2 3072 03-Feb-89 09:56:28 32 6 Y Y
#5B-LOG3 3072 03-Feb-89 09:57:24 32 6 Y Y
* MORE *
CONFIG 1
Filename = User--configured report name Autoprint = If “Y”, a report is printed and

Size = Size in bytes of the file written to disk when generated;
Modification Time =Last time and date file was if “N”, a report is written to disk
modified, if ever Active = If “Y”, a report is generated at
Max = Maximum number of report specified times or alarms/events; if
generations “N”, a report is generated only on
Node = Print node operator command
Figure 3.2.5. Report Configuration Directory Screen

CC: 3-2-8
The Report Status Screen
The Report Status screen shows the activity of configured and

generated reports. The Report Status screen shows up to 18 entries.
Each new entry appears at the bottom of the screen and the oldest
entry is scrolled off the top of the screen. Figure 3.2.6 shows an
example of a Report Status screen with field descriptions.
- To call up the Report Status screen, type:
RS [ENTER]
Current state = If “Enabled”, the report system is running; if “Disabled”, the

report system is not running
Disk Owner = Specifies which Multitube Command Console generates the
report
Filename = User--configured report name
Action = Report status messages
Time = Date and time the action took place
Report Status 04-Aug-92 15:32:16
Current state ;ÞEnabled Disk Owner: yes Running

Filename Action Time
#1B-LOG2 Report generation completed 09:47:02 04-Feb-89
#1B-LOG2 AUTO-PRINT kicked off to node 16 09:47:02 04-Feb-89
#1B-LOG2 Report has been scheduled (alarm) 09:48:24 04-Feb-89
#1B-LOG2 Starting report generation 09:48:24 04-Feb-89
#1B-LOG2 Deleting existing report entry #3 09:48:25 04-Feb-89
#1B-LOG2 Deleting existing report entry #3 09:49:47 04-Feb-89
#1B-LOG2 was modified, is active awaiting alarm 09:51:12 04-Feb-89
#1B-LOG Deleting existing report entry #3 09:51:14 04-Feb-89
CONFIG 3
Figure 3.2.6. Report Status Screen

CC: 3-3-1
Section 3:
Designing a Report
Reports can be designed for viewing on a CRT screen and for printing.
This section gives guidelines for designing and formatting reports.
Assembling Information for a Report
Reports can be assembled with information from ControlBlocks, I/O

blocks, or trend files. The appearances of a report will vary depending
on the type of information that is included. Before starting the
configuration process on a console screen, it may be helpful to
approximate the appearance and size of report by doing a layout on a
grid worksheet. Figure 3.3.1 shows a sample layout of a report.
Report Configuration 28-Jul-92 09:32:16
****************** START OF REPORT ******************
BANNER
Date Time
Process Narrative
Variables Process Descriptions Process Descriptions Process Descriptions
Total (accumulator)
CONFIG 1
Figure 3.3.1. Report Sample Layout
RS3: Reports Designing a Report

CC: 3-3-2
Dimensions of a Report
Report dimensions include the visible size of a report on a screen and

the maximum size of a report. Information can be configured in one
report that spans several pages, or configured in several reports that
are one page each.
D The visible size of one report on the screen is 80 columns wide
by 30 rows long.
D The maximum size of one report is 160 rows wide by 30,000
rows long.
Figure 3.3.2 shows the visible report body with dimensions.
The body of the report begins here.
****************** START OF REPORT ******************
30 rows long visible on the screen
80 columns wide visible on the screen
CONFIG 1
Figure 3.3.2. Visible Report Screen Dimensions

CC: 3-3-3
Formatting the Report for Printing
Figure 3.3.3 shows how to lay out a single--page report so that it fits
properly on an 8½I´ 11I sheet of paper. A page of a printed report
should be 60 lines with a 3--line margin at the top of the page and a
3--line margin at the bottom of the page.
If a report requires more than one page, a newpage object must be

configured in a report. For information about the newpage object, see
page CC:3-4-11.
Edge of paper Edge of display

Console inserts 3--line margin at top
of first page when report is generated
Allow at least
66 lines 6--column left
total margin for Contents of report
in an hole--punching should occupy no
11--inch more than 60 lines or
sheet 74 columns per page
Allow at least 3--line bottom margin
Figure 3.3.3. Sizing a Report Page

CC: 3-4-1
Section 4:
Configuring a Report
Each report is configured on a Report Configuration screen. This

section describes the Report Configuration screen and describes
configuring report objects.
RS3: Reports Configuring a Report

CC: 3-4-2
The Report Configuration Screen
Figure 3.4.1 shows an example of a Report Configuration screen with

field descriptions. Table 3.4.1 gives brief descriptions of the fields that
are configured at the top of the Report Configuration screen.
- To call up a Report Configuration screen, type:
RG ( , filename) [ENTER]
NOTE: If the filename already exists, the Report Configuration screen

for that file appears. If the filename is new, a blank Report
Configuration screen appears.
Use the fields in the shaded area Configure the format and
of the screen to configure how, content of the report in the
where, and when to generate and area below the START OF
print the report. REPORT.
REPORT CONFIGURATION 21-Aug-92 14:18:04

Description :Þ
Created : never
Filename : Þ Size :0 Last saved : never
STATUS : new file Free Space :100 Backed up : never
Auto Print ?Þyes Max number of reports :Þ3 Print node :Þ16 Active ? Þno
Generate on alarm/event from : ÞRPTTEST Þ Þ
Þ Þ
Month : any
Day/month: any
Day/week : any
Hour : any
Minute : never
ÞTIME ENTRY :Þ
Command : Þ
****************** START OF REPORT ******************
CONFIG 1
Figure 3.4.1. Report Configuration Screen

CC: 3-4-3
Table 3.4.1. Report Configuration Screen Fields
Field Description Allowable Entries
Determines whether or not the “Generate on alarm/event yes,

Active ?
from” field is active. no
Determines whether or not a report is printed and saved to yes,

Auto Print ?
disk when it is generated. no
Date and time when configuration file was last copied to

Backed Up Display only
another disk or tape.
Used to execute one of the following commands:

1) Save this configuration to disk
1) Save to disk
2) Generate a copy of this report 2) Generate this report
Command
3) Clear the configuration of the body of this report 3) Clear Configuration
4) Load from disk
4) Load from disk the report configuration screen for the
file currently entered in “Filename”
Created Date and time when report was first configured. Display only
Days of the month in which a report is to be generated.

(any = every day) An entry is made after the arrow next to
Day/month the “Time Entry” field. For more information, see “How to any, or 1--31
Generate a Report based on Time and Date” on page
3-4-32.
Days of the week in which a report is to be generated.

(any = every day) An entry is made after the arrow next to
the “Time Entry” field. For more information, see “How to any, 1--7, or Sun to Sat
Day/week
(1=Sun)
3-4-32.
Up to 59 alphanumeric
Description Description of the report.
characters
Up to to 9 alphanumeric
Filename Name of the report configuration file.
characters
Free Space Percent of report’s configuration file space not yet used. Display only
Generate on Determines block variable alarms and events that trigger

alarm/event report generations. Refer to “Generating Reports” on page Any existing variable’s
tag or address.
from 3-4-39 for more information.
Hours at which a report is to be generated.

(any = every hour) An entry is made after the arrow next to
Hour the “Time Entry” field. For more information, see “How to any, or 0--23
3-4-32.
Date and time when report was last saved to disk, either by
Last Saved Display only
exiting the screen or entering a “Save to disk” command.
Max Number of Number of report generations to be saved on the disk. The

1 to 99
Reports most current generations are saved.

CC: 3-4-4
Table 3.4.1. Report Configuration Screen Fields (continued)
Minutes on the clock at which report is to be generated. An

entry is made after the arrow next to the “Time Entry” field. never or
Minute
For more information, see the “How to Generate a Report 0--55 in 5 min. intervals
based on Time and Date” on page 3-4-32.
Months in which a report is to be generated.

(any = every month) An entry is made after the arrow next
to the “Time Entry” field. For more information, see “How to any, 1--12, or Jan to Dec
Month
(1=Jan)
3-4-32.
Node where the report is to be printed. This must be the

same entry as the “Print Node” field entry on the Console Any node number where
Print Node
a printer is connected.
Size Size in bytes of the configuration file. Display only
new file = file being configured for the first time

modified = configuration modified since last saved to
disk
Status unchanged = configuration unchanged since last saved to Display only
disk
exists = name of an existing file has been entered in
“Filename”.
Used to select any one of the time parameters for entry.

Month, Day/month,
Select the desired time parameter. Cursor to the arrow
Time Entry Day/week, Hour and
immediately to the right and enter the desired value. Repeat
Minute
for each time parameter.

CC: 3-4-5
Report Objects
A report is configured with various objects. You configure each object

and place it in the body of a report. Each object is configured in a
Report Configuration Window. Figure 3.4.2 shows an example of a
Report Configuration Window with the procedure for selecting a report
object. Table 3.4.2 gives descriptions of report objects that can be
selected. For information about SQC report objects, see SR:4.
- To select a report object: 2. Press [SELECT]. A

1. Position the cursor in the body Report Configuration
of the report where the object Window appears.
should be.
****************** START OF REPORT ******************
Type :Þvalue Color :Þ1n white Row :Þ26 Col :Þ13

Tag :Þnone CREATE DELETE
Accum :Þnone
CONFIG 1
3. To select an object, cursor 4. Configure the remaining

to the “Type” field and fields in the Report
press [NEXT OPTION]. Configuration Window.
Then press [ENTER].
Figure 3.4.2. Report Configuration Screen with Report Configuration Window

CC: 3-4-6
Table 3.4.2. Report Object Types
Report Object Function
Displays a result calculated from several value objects, such as a column total. The
accumulate form of the calculation depends on the operation (+, --, ´, or ¸) selected for each
value object.
addr Displays the address of the specified block.
Displays a large--type banner or heading. Each character will be 10 lines high and 8
ban1
columns wide. Maximum of 10 characters across an 80--column page.
Displays a large--type banner or heading. Each character will be 10 lines high and 16
ban2
columns wide. Maximum of 5 characters across an 80--column page.
Allows the operator to enter up to 70 characters in a report before the report is

comment
generated.
date Inserts the current date whenever the report is generated.
descriptor Displays the descriptor of the specified block.
func Displays the block function configured for the specified block.
generate Allows another generated report to be incorporated into the report being configured.
list Inserts the current contents of an alarm or event list into the report.
mode Displays the current mode of the specified block.
newpage Directs the printer to execute a form feed
Permits entry of a hexadecimal code to control the operation of the printer, permitting
print
use of special features such as type font and color selection. (See printer manual).
SQC Cent Type Displays the type of the specified centering chart.
SQC CL Displays the centering limit of the specified centering chart.
SQC Disp Type Displays the type of the specified dispersion chart.
SQC In Contrl Displays the percentage of points that are in control for the specified dispersion chart.
SQC LCL Displays the lower centering limit of the specified centering chart.
SQC LRL Displays the lower range limit of the specified dispersion chart.
SQC Mean Displays the mean of the specified centering chart.
Displays the specified SQC data for the specified range chart, beginning at the
SQC Report specified time and for the specified duration, or beginning at the specified population
for the specified range.
SQC RL Displays the range limit of the specified dispersion chart.
SQC Std Dev Displays the standard deviation of the specified dispersion chart.

CC: 3-4-7
Table 3.4.2. Report Object Types (continued)
Report Object Function
Displays the total number of samples and the number of samples that are out of
control for the specified range chart, beginning at the specified time and for the
SQC Summ Rpt
specified duration, or beginning at the specified population for the specified sample
range.
SQC Title Displays the title of the specified control chart.
SQC UCL Displays the upper centering limit of the specified centering chart.
SQC URL Displays the upper range limit of the specified dispersion chart.
tag Displays the tag of the specified block.
text Displays up to 40 characters of text.
time Inserts the current clock time whenever the report is generated.
Creates a table of periodic readings of one or more variables over

trend log
a specified time span.
units Displays the engineering units legend associated with the specified variable.
value Displays the value of the specified continuous or discrete variable.

CC: 3-4-8
Using Report Objects to Configure Reports
Some fields appear in Report Configuration Windows for all report

objects. Figure 3.4.3 shows a Report Configuration Window with
descriptions of those fields that appear in all Report Configuration
Windows.
Report objects can be displayed

(but not printed) in various colors.
A location on the body of the report is
Select different colors for objects
identified as the intersection of a row and a
by pressing [NEXT OPTION] in the
column, as indicated by the ”Row” and ”Col”
”Color” Field.
fields.
Type :Þvalue Color :Þ1n white Row :Þ26 Col :Þ13value

CREATE DELETE
CONFIG 1
A report object is selected in the CREATE is used to create text or values for the
“Type” field. generate object and the trend log object. CREATE is
also used with other report objects to copy text or
values. To copy text or values, select the object and
location, then cursor to CREATE and press [ENTER].
DELETE is used to delete a single object. To delete an
object, select the object and location, cursor to
DELETE and press [ENTER]. Or, press [SELECT] on
the left end of the object, then cursor to DELETE and
press [ENTER].
Figure 3.4.3. Report Configuration Window with Fields

CC: 3-4-9
Editing the Body of a Report
Table 3.4.3 gives editing instructions to use when configuring the body
of the report.
Table 3.4.3. Editing Instructions
Editing Tasks Action
To delete a line or row of objects Cursor to the line to be deleted and press the [CNTL] and [D]
keys at the same time.
To delete a space (to the left of an Cursor to the line containing the object and press the [CNTL]
object) and [F] keys at the same time.
To delete an object Cursor to the left end or upper left corner of the object and press
[ENTER].
To insert a line (above an object) Cursor to the line containing the object and press the [CNTL]
and [I] keys at the same time.
To insert a space (to the left of an Cursor to the line containing the object and press the [CNTL]
object) and [E] keys at the same time.
To page through the report D To page forward, press the [CNTL] and [G] keys at the
same time.
D To scroll up one line, press the [CNTL] and [J] keys at the
same time.
D To scroll down one line, press the [CNTL] and [K] keys at
the same time.
To print the report Press [CNTL] and [P] keys at the same time.
To read the report from a disk Press the [CNTL] and [R] keys at the same time.
To write the report to disk Press the [CNTL] and [W] keys at the same time.

CC: 3-4-10
Configuring How a Report is Printed
The print object determines the font style, size and color of the text in
which the report is printed. The newpage object causes a page break in
the report.
How to Determine Report Print Characteristics
The print uses a hex code to determine the report print characteristics.
The hex code remains in effect until the next print object is inserted in a
report. See the printer manual for printer hex codes. Figure 3.4.4
shows the procedure for configuring a print object in a report.
NOTE: The print object in the Report Configuration window does not
determine when and if the report is printed.
- To configure a print object in a report:

1. Select print as the object type.
Report Configuration 02-Aug-92 15:31:16

ENERGY PRODUCTION REPORT
Generated at 14:27:42 on 02-Feb-89
TOTAL TOTAL TOTAL TOTAL AVERAGE
STEAM FLOW FW FLOW GAS FLOW OIL FLOW EFFICIENCY
(KLB) (KLB) (KSCF) (GALLON) (%)
BOILER #1 .089 .903 .442 .96 .54
BOILER #2 .087 .877 .368 .65 .69
BOILER #3 .077 .857 .314 .21 .34
- - - - - - - - - - - - - - - - - - - - - - - - - - -
SUBTOTAL ACCUM #1 ACCUM #2 ACCUM #3 ACCUM #4 ACCUM #5
print
Type :Þprint Color :Þ1n white Row :Þ30 Col :Þ45
CREATE DELETE
Hex code : Þ
CONFIG 1
2. Enter a hex code as 3. Press [ENTER]. Text

indicated in the printer following the print command
specifications. has the designated print style.
Figure 3.4.4. Report Configuration Screen with Print Object

CC: 3-4-11
How to Begin a New Report Page
The newpage object causes a new report page to begin four lines after
the newpage object has been inserted. Figure 3.4.5 shows the
procedure for configuring the newpage object in a report.
- To configure a new page:

1. Select newpage as the object type.

BOILER #1 .089 .903 .442 .96 .54
BOILER #2 .087 .877 .368 .65 .69
BOILER #3 .077 .857 .314 .21 .34
- - - - - - - - - - - - - - - - - - - - - - - - - - -
>
newpage
Type :Þnewpage Color :Þ1n white Row :Þ30 Col :Þ88
CREATE DELETE
CONFIG 1
2. Press [ENTER]. A The new report page appears on

prompt > appears. the fourth line (with a top margin of
three lines).
Figure 3.4.5. Report Configuration Screen with Newpage Object

CC: 3-4-12
Configuring Text in a Report
This section explains how to configure text to appear in a report.
How to Print Regular--sized Text
Regular--sized text can be used in a report body for titles, labels,

column headings, and comments. A text object may be created in
either of two ways. Figure 3.4.6 shows the procedures for configuring
text in the body of a report.
- To configure text in the body of a report:

1. Select text as the object type.

****************** START OF REPORT ******************
Production Report for 02:Feb:89
Production Report for
text
Type :Þtext Color :Þ1n white Row :Þ13 Col: : Þ5
CREATE DELETE
Text :ÞProduction Report for
CONFIG 1
or 1. Cursor to the desired

2. Type in text in the “Text” 3. Press [ENTER]. The text location in the report body, type in
field. appears in the body of the text, and press [ENTER].
report.
Figure 3.4.6. Report Configuration Screen with Text Object

CC: 3-4-13
How to Print Oversized Text
Oversized characters are called banners. You can use banners in a

report as titles or headers. Banner styles include ban1 and ban2
objects. Ban1 uses letters 8 columns wide and 10 rows high. Ban2
uses letters 16 columns wide and 10 rows high.
To center the banner on the report page, you need to calculate the
column location of the left edge. For example, if ban1 is selected, and
the banner uses six characters, use this formula:
6 letters ´ 8 columns per letter = 48 columns total width

80 columns × 48 columns = 32 columns unused
32 columns ¸ 2 = 16 columns on either side of banner
Begin banner in column 17.
Figure 3.4.7 shows the procedure for configuring a banner object.
- To configure a banner object:

1. Select ban1 or ban2 as the object type.

****************** START OF REPORT ******************
REPORT
ban1
Type :Þban1 Color :Þ1n white Row :Þ13 Col: : Þ6
CREATE DELETE
Text :ÞREPORT
CONFIG 1
2. Type in the text to be 3. Press [ENTER]. The

used as a banner. banner appears in the
body of the report.
Figure 3.4.7. Report Configuration Screen with Banner Object

CC: 3-4-14
Configuring Operator Comments in a Report
The comment object allows an operator to configure comments in a

report without a configuror’s key. Comments must be added to a report
configuration screen in order to be included in a generated report.
Figure 3.4.8 shows the procedure for configuring comments in a report.
- To configure comments in a 2. Determine the length of the

report: comment in the “Length”
1. Select comment as the object field.
type.

****************** START OF REPORT ******************
comment Row :Þ13 Col: : Þ6

Type :Þcomments CREATE DELETE
Length:Þ70
Text :Þ
CONFIG 1
3. Type in the text (up to 4. Press [ENTER]. The

70 characters). comment appears in the
report.
Figure 3.4.8. Report Configuration Screen with Comment Object

CC: 3-4-15
Configuring Block Information in a Report
Information from Controlblocks or I/O blocks can be configured in a

report.
How to Configure a Block Tag
You can use block tags as labels in a report to identify the tag of a
specified block. Figure 3.4.9 shows the procedure for configuring a
block tag in a report.
- To configure a block tag in a report:

1. Select tag as the object type.

****************** START OF REPORT ******************
MCIN-1U
CON-1U
tag
Type :Þtag Color :Þ1n white Row :Þ26 Col :Þ13
Tag :ÞCON-1U CREATE DELETE
CONFIG 1
2. Type the tag or the 3. Press [ENTER]. The tag

address of the tag in the appears in the body of
“Tag” field. the report.
Figure 3.4.9. Report Configuration Screen with Tag Object

CC: 3-4-16
How to Configure a Block Address
You can use block addresses as labels in a report to identify the

address of a specified block. Figure 3.4.10 shows the procedure for
configuring a block address in a report.
- To configure a block address in a report:

1. Select addr as the object type.

****************** START OF REPORT ******************
=1AA101
=1AA201
addr
Type :Þaddr Color :Þ1n white Row :Þ26 Col :Þ13
Tag :Þ=1AA201 CREATE DELETE
CONFIG 1
2. Type the address or the 3. Press [ENTER]. The

tag in the “Tag” field. address appears in the
body of the report.
Figure 3.4.10. Report Configuration Screen with Address Object

CC: 3-4-17
How to Configure a Block Descriptor
You can use block descriptors to provide additional information about a

block in a report. Block descriptors can contain up to 24 characters.
Figure 3.4.11 shows the procedure for configuring a descriptor in a
report.
- To configure a descriptor in a report:

1. Select descriptor as the object type.

****************** START OF REPORT ******************
Tank 3 Level 726.26 liters

Tank 4 Level 425.48 liters
descriptor
Type :Þdescriptor Color :Þ1n white Row :Þ26 Col :Þ13
CONFIG 1
2. In the “Tag” field, type the 3. Press [ENTER]. The

tag or address of the block descriptor appears in the
whose descriptor is to be body of the report.
displayed.
Figure 3.4.11. Report Configuration Screen with Descriptor Object

CC: 3-4-18
How to Configure a Block Function
You can use block functions as descriptions in a report to identify the

function of a specified block. Figure 3.4.12 shows the procedure for
configuring a block function in a report.
- To configure a block function in a report:

1. Select func as the object type.

****************** START OF REPORT ******************
=1AA101 I/O BLOCK

=1AA201 PI Controller
func
Type :Þfunc Color :Þ1n white Row :>26 Col :>18
CONFIG 1

tag or address of the block function appears in the
whose function is to be body of the report.
displayed.
Figure 3.4.12. Report Configuration Screen with Function Object

CC: 3-4-19
How to Configure a Block Mode
You can use block modes in a report to describe the mode of operation
of a specific block. Figure 3.4.13 shows the procedure for configuring a
block mode in a report.
- To configure a block mode in a report:

1. Select mode as the object type.

****************** START OF REPORT ******************
=1AA101 MANUAL
=1AA201
mode
Type :Þmode Color :Þ1n white Row :>26 Col :>18
CONFIG 1
2. In the “Tag” field, type the tag 3. Press [ENTER]. The mode
or address of the block appears in the body of the
whose mode is to be report.
displayed.
Figure 3.4.13. Report Configuration Screen with Mode Object

CC: 3-4-20
How to Configure Block Units
You can use block units as labels for specified blocks. Figure 3.4.14
shows the procedure for configuring block units in a report.
- To configure block units in a report:

1. Select unit as the object type.

****************** START OF REPORT ******************
MCIN-1U
GALLONS
5679
unit
Type :Þunit Color :Þ1n white Row :Þ30 Col :Þ22
Tag :ÞMCIN-1U CREATE DELETE
CONFIG 1

tag or address of the tag units appear in the body
whose units will be of the report.
displayed.
Figure 3.4.14. Report Configuration Screen with Unit Object

CC: 3-4-21
How to Configure Block Values
You can configure block values in the body of a report. Values can also
be added, subtracted, multiplied and divided in a report. Figure 3.4.15
shows the procedure for configuring block values in a report.
- To configure block values in a report: 2. In the “Tag” field, type the tag
1. Select value as the object type. or address of the tag whose
value will be displayed.

****************** START OF REPORT ******************
GALLONS
MCIN-1U 5679
MCIN-2U 1234
value
Type :Þvalue Color :Þ1n white Row :Þ30 Col :Þ68
Tag :ÞMCIN-2U CREATE DELETE
Accum :Þ +1
CONFIG 1
3. If the value is to be combined in a 4. Press [ENTER]. The

calculation, type in the accumulator value appears in the
number with a mathematical operator body of the report.
(+, --, *, / ) in the “Accum” field.
Figure 3.4.15. Report Configuration Screen with Value Object

CC: 3-4-22
How to Perform Calculations
In a report, any number of value objects can be added, subtracted,

multiplied, and divided together. The results of these calculations are
placed in accumulators, or storage areas. A report can use up to 20
accumulators. Accumulate objects are used to configure accumulators.
The “Accum” field in the value object Report Configuration Window

designates if the value is to be part of a calculation and in what
accumulator the result of the calculation will be stored.
NOTE: Value objects in accumulators are processed on the basis of

location: top to bottom, left to right.
- To configure an accumlulator:
1. Enter an accumulator number (1--20) with a mathematical
operator (--, +, *, / ) in the “Accum” field of the value object Report
Configuration Window.
NOTE: Depending on how the accumulator is specified,
subtraction (--) and division (/) operators are placed before or
after the accumulator number. For example, 5/ means that
accumulator #5 is divided by the value; /5 means that the value is
divided by accumulator #5. Addition (+) and multiplication (*)
operators can be entered before or after the accumulator
number. For example, *5 or 5* will give the same result.
2. Configure the accumulate object.
As an example, Figure 3.4.16 and Figure 3.4.17 show how to
obtain a steam flow total and a mean average of the total.
Figure 3.4.18 shows the procedure for configuring an accumulate
object for an accumulator.

CC: 3-4-23

BOILER #1 .089 .903 .442 .96 .54
BOILER #2 .087 .877 .368 .65 .69
BOILER #3 .077 .857 .314 .21 .34
-----------------------------------------------------------------
value
Type :Þvalue Color :Þ1n white
Tag :ÞMCIN-1U
Accum :Þ +1, +2
Individual values can be
configured to be part of
a calculation. In this
example, the three value
values in the Total Type :Þvalue Color :Þ1n white
Steam Flow column are Tag :ÞMCIN-2U
configured to be added Accum :Þ +1, +2
together. The result of
this addition is placed in
accumulator #1 and value
accumulator #2. Type :Þvalue Color :Þ1n white
Tag :ÞMCIN-3U
Accum :Þ +1, +2
Type :Þaccumulate Color :Þ1n white

Accumulator #1 is Accum:Þ 1 Clear ? Þyes
configured. Decimal Point : Þ3
Figure 3.4.16. Report Configuration Screen with Value and Accumulator Objects

CC: 3-4-24

BOILER #1 .089 .903 .442 .96 .54
BOILER #2 .087 .877 .368 .65 .69
BOILER #3 .077 .857 .314 .21 .34
-----------------------------------------------------------------_____________
__________________________
SUBTOTAL ACCUM #1 ACCUM #4 ACCUM #5 ACCUM #6 ACCUM #7 3
AVERAGE ACCUM #2
value
Type :Þvalue Color :Þ1n white
Tag :ÞNUM-3U
Accum :Þ2/
A mean average of the value in accumulator #2 can

be obtained by dividing the contents of accumulator
#2 by 3. The value “3” must be first be configured in
a block.
Type :Þaccumulate Color :Þ1n white

Accumulator #2 is Accum:Þ 2 Clear ? Þyes
configured. Decimal Point : Þ3
Figure 3.4.17. Report Configuration Screen with Value Objects

CC: 3-4-25
- To configure an accumulate object: 5. Press [ENTER]. The

1. Select accumulate as the object type. accumulator appears in the
body of the report.

BOILER #1 .089 .903 .442 .96 .54
BOILER #2 .087 .877 .368 .65 .69
BOILER #3 .077 .857 .314 .21 .34
- - - - - - - - - - - - - - - - - - - - - - - - - -
Type :Þaccumulate Color :Þ1n white Row :Þ30 Col: Þ66

Accum:Þ 1 Clear ? Þno
Decimal Point :Þ
CONFIG 1
2. Type an accumulator 3. Designate the number 4. If “yes” is entered in the

number (1--20) in the of decimal places (up to “Clear” field, the
“Accum” field. 4) in the “Decimal Point” accumulator resets to zero
field. after the result is displayed.
Figure 3.4.18. Report Configuration Screen with Accumulator Object

CC: 3-4-26
How to Configure Trend File Information in a Report
The trend log object allows trend data to be included in a report.

Figure 3.4.19 shows the trend log Report Configuration Window with
default values. Table 3.4.4 describes the trend log configuration fields.
Figure 3.4.20 and Figure 3.4.21 show examples of trend log objects and
the resulting reports.
Select trend log as the object

type.
REPORT CONFIGURATION 21-Jul-92 14:18:04

****************** START OF REPORT ******************
Detail :Þy
Type :Þtrend log Color :Þ1n white Row :Þ38 Col :Þ15 Time : Þy
Data : Þy
File Name:Þtrf1 Trend Node :Þ28 CREATE DELETE Mean :Þy Þy
Total :Þy Þy
Scaled :Þ1 Accumulator :Þnone Tag Þnone Minimum:Þy Þy
Maximum Þy Þy
Time :Þ00:00:00 Duration :Þ10 hr Interval :Þ1 day MM Time:Þy
CONFIG 1
CREATE must be used to create or to modify

a trend log object.
Figure 3.4.19. Report Configuration Screen with Trend Log Object

CC: 3-4-27
The left column determines whether or not the information

is included in each column.
In this example, each column includes interval values
(detail), mean, total, maximum, and minimum.
Detail :Þy
Data : Þy
File Name:Þtrf1 Trend Node :Þ28 CREATE DELETE Mean :Þy Þy
Total :Þy Þn
Scaled :Þ1 Accumulator :Þnone Tag Þtab/A Minimum :Þy Þn
Maximum :Þy Þn
Time :Þ00:00:00 Duration :Þ10 hr Interval :Þ1 hr MM Time :Þn
The right column determines which columns are

included in the report.
Time Data Mean
column column column In this example, the report includes the time,
data, and mean columns.
REPORT
01:00:00 85.06 84.98
02:00:00 86.05 84.96
03:00:00 83.45 84.76
04:00:00 85.67 84.89
05:00:00 84.35 84.94 Detail----
06:00:00 85.90 84.76 Determines whether or not
07:00:00 86.23 84.50 interval values are included
08:00:00 84.78 84.88
09:00:00 87.23 84.82
10:00:00 88.01 84.81
Mean 84.95 84.31
Total 941.68 932.61
Minimum 83.45 82.11
Maximum 88.01 86.34
Figure 3.4.20. Sample Trend Log Object Configuration Window and Resulting Report

CC: 3-4-28
In this example, the report includes

the detail and total rows.
Detail :Þy
Data : Þn
File Name:Þtrf1 Trend Node :Þ28 CREATE DELETE Mean :Þn Þn
Total :Þy Þn
Scaled :Þ1 Accumulator :Þnone Tag Þtag/A Minimum :Þn Þy
Maximum :Þn Þn
In this example, the report includes

the time and minimum columns.
Minimum
REPORT
01:07:34 1699.60
02:07:34 1699.20
03:07:34 1666.60
04:07:34 1697.50
05:07:34 1699.40
06:07:34 1698.70
07:07:34 1695.70
08:07:34 1690.00
09:07:34 1697.60
10:07:34 1685.80
Total 101755.20
Figure 3.4.21. Sample Trend Log Object Configuration Window and Resulting Report

CC: 3-4-29
Table 3.4.4. Trend Log Field Description
Field Description
Accumulator Represents a mathematical expression of the trend data applied to a report

accumulator. Accumulators in trend log objects can accumulate one column of trend
data.
The mathematical operators available are: + (addition)
-- (subtraction)
/ (division)
* (multiplication)
When using an accumulator, only one column of data (“Mean”, “Total”, “Minimum”, or
“Maximum”) can be included in the trend object type.
NOTE: For information on configuring an accumulate object, see “How to Perform
Calculations (Accumulate Object)” on page 3-4-22.
Data Represents the instantaneous value of the “Tag” being trended. The yes/no field
specifies whether or not a column of instantaneous data is included in the report.
Detail Represent interval values. The yes/no field specifies whether or not rows of interval
values are included in the report.
Duration The length of time of the trend log data that is included in the report.
File Name Trend file names trf1 through trf9, or SRU file names 5 sec, 1 min, 10 min, or 1 hr.
Interval The time interval of trend log entries in the report. For example, an “Interval” entry of
1 hr provides trend data for every hour of the “Duration” time period. Figure 3.4.20
shows an example of a duration and an interval.
Maximum Represents the maximum value. The first yes/no field specifies whether or not a row
of maximum values is included in the report. The second yes/no value specifies
whether or not a column of maximum values is included in the report.
Mean Represents the mean average. The first yes/no field specifies whether or not a row
of mean values is included in the report. The second yes/no value specifies whether
or not a column of mean values is included in the report.
Minimum Represents the minimum value. The first yes/no field specifies whether or not a row
of minimum values is included in the report. The second yes/no value specifies
whether or not a column of minimum values is included in the report.
MM Time The yes/no field indicates whether or not a minimum time and maximum time is
calculated over the “Duration” for the trend data.
If more than one minimum or maximum occurred, the first minimum or maximum is
displayed.
Scaled Scaling factor for the trend values. All trend values shown on the report for the object
type are multiplied by the “Scaled” factor.
Tag Tag of the trended variable. This field must have a value other than “none” entered.

CC: 3-4-30
Table 3.4.4. Trend Log Field Description (continued)
Field Description
Time The beginning time of the trend log data that is included in the report. The time can
be entered in the following ways:
--DD/HH:MM:SS specifies day and time--for example, 10/10:15 specifies that the
report includes tend log data starting at 10:15 AM on the 12th day
of the month.
HH:MM:SS specifies at time—for example, 16:00:00 specifies that the report
includes trend log data starting at 4 P.M.
-- HH:MM:SS specifies an amount of time previous to the report generation
time—for example, --8:00:00 specifies that the report includes
trend log data starting 8 hours before the report generation time.
block variable specifies a number of seconds previous to the report generation
time—for example, a block variable with a value of 120 specifies
that the report includes trend log data starting 120 seconds before
the report generation time.
NOTE: You can only enter up to eight characters. If you specify a day of the month,
you may not have enough space to specify seconds.
Time Represents the time values of instantaneous data and the labels of the other value
fields (Mean, Total, Maximum, Minimum, MM Time). The yes/no field specifies
whether or not the Time column is included in the report.
Total Represents the total value. The first yes/no field specifies whether or not a row of
total values is included in the report. The second yes/no value specifies whether or
not a column of total values is included in the report.
Trend Node Node on which the trend file resides.

CC: 3-4-31
How to Use an Accumulator with a Trend Log Object
The accumulate object is used to accumulate one column of data from a

trend file. Figure 3.4.22 shows examples of using an accumulator with
a trend log object. In both examples, the trend log object is used to get
data from trend file trf1.
In this example, the trend data value is subtracted from the value in accumulator 3 and the
result is put into accumulator 3.
For example, if the trend data is 173.50 and the value in accumulator 3 is 92.75, the
calculation becomes: 92.75 -- 173.50 = --80.75. The value --80.75 is put into accumulator 3.
Detail :Þn
Type :Þtrend log Color :Þ1n white Row :Þ38 Col :Þ15 Time : Þn
Data : Þy
Total :Þn Þn
Scaled :Þ1 Accumulator :Þ3- Tag Þtag/A Minimum :Þn Þn
Maximum :Þn Þn
In this example, the value in accumulator 3 is subtracted from

the trend data value and the result is put into accumulator 3. NOTE: In both examples, the
trend log object must contain
only one column of data.
For example, if the trend data is 173.50 and the value in
accumulator 3 is 92.75, the calculation becomes: 173.50 --
92.75 = 80.75. The value 80.75 is put into accumulator 3.
Detail :Þn
Type :Þtrend log Color :Þ1n white Row :Þ38 Col :Þ15 Time : Þn
Data : Þy
Total :Þn Þn
Scaled :Þ1 Accumulator :Þ3- Tag Þtag/A Minimum :Þn Þn
Maximum :Þn Þn
Figure 3.4.22. Report Configuration Window with Trend Log Object and Accumulator

CC: 3-4-32
Configuring Time and Date Information in a Report
This section explains how to configure a report so that the time and date
it was generated automatically appear in the report.
How to Configure the Current Time
The time object shows the current hour, minutes, and seconds
(hh:mm:ss) in a report. The time displayed in a report is the same as
the time displayed in the top corner of the CRT screen. Figure 3.4.23
shows the procedure for configuring a time object in a report.
NOTE: The time object does not determine what time a report is
generated.
- To configure a time object in a report:

1. Select time as the object type.
Report Configuration 02:Aug:92 09:31:16

****************** START OF REPORT ******************
Report generated at 09:30:05
time
Type :Þtime Color :Þ1n white Row :>26 Col :>25
CREATE DELETE
CONFIG 1
2. Press [ENTER]. A time object that displays the current

hour, minutes, and seconds appears in the body of the
report.
Figure 3.4.23. Report Configuration Screen with Time Object

CC: 3-4-33
How to Configure the Current Date
A date object shows the day, month, and year (dd:mm:yy) in a report.
The date displayed in a report is the same as the date displayed in the
top corner of the CRT screen. Figure 3.4.24 shows the procedure for
configuring a date object in a report.
NOTE: The date object does not determine when a report is generated.
- To configure a date object in a report:

1. Select date as the object type.
Report Configuration 02:Aug:92 09:31:16

****************** START OF REPORT ******************
Report generated on 02:Feb:89
Type :Þdate Color :Þ1n white Row :>26 Col :>25

CREATE DELETE
CONFIG 1
2. Press [ENTER]. A date with the current day,

month, and year is displayed on the report.
Figure 3.4.24. Report Configuration Screen with Date Object

CC: 3-4-34
Configuring Console Lists in a Report
Console lists can be inserted into a report generated by that console.

Console lists include alarm lists, event lists, status lists, and the
operator change log. The advantages of including console lists in a
report is that reports can be configured to include narrative text as well
as being configured to generate on a regular basis.
You can configure a console lists to generate a printout at a certain

trigger point. A trigger point is configured on the Alarm List
Configuration and the Event List Configuration screens. Once a list has
been printed out the information is no longer available to be included in
a report.
When inserted into a report, the contents of a list may be “filtered” to

include only a specified range of block addresses, or entries after a
specified time. The report list object does not receive data until the
report is generated.
NOTE: The report can includes entries from a console list for
approximately 7 days (or 9999 minutes).

CC: 3-4-35
Configuring the List Object
Figure 3.4.25 shows the Report Configuration Window with list object
entries. Table 3.4.5 gives the Configuration Window field descriptions.
Formatting a List
A console list occupies 80 columns.
Select list as the object type.

****************** START OF REPORT ******************
LIST: lst=System Status, tm=0, hdr=no, #1n=0, bk1=any, bk2=any
list
Type :Þlist Color :Þ1n white Row :Þ26 Col :Þ2
List :ÞSystem Status Hdrs :Þ no CREATE DELETE
Time Period :Þnone # lines ;Þ none Blk1 :Þ any
Alarm Format :Þ 80C Blk2 :Þ any
CONFIG 1
Figure 3.4.25. Report Configuration Screen with List Object

CC: 3-4-36
Table 3.4.5. List Object Configuration Screens
The column width of the report. The maximum column

Alarm Format width is 132 characters. Use the [NEXT OPTION] or 80O, 80C, 132
[LAST OPTION] key to step through options.
The lowest--numbered block for which data is to be

included.
Any block address lower
Blk1* NOTE: If information other than the default value is than Blk2 entry.
entered in this field, it must agree with the block range in
the specified list.
The highest--numbered block for which data is to be

included.
Any block address higher
Blk2* NOTE: If information other than the default value is than Blk1 entry.
entered in this field, it must agree with the block range in
the specified list.
Hdrs Determines if a full header will be printed with the list. yes, no
The number of lines from the list to be included in the

report, beginning with the most recent entry. If “none”, all
lines that otherwise qualify will be included. 1--2000
lines*
NOTE: If information other than the default value is
entered in this field, it must agree with the number of
lines in the specified list.
none,
Batch Alarm List
Process Alarm List,
Identifies the specific list to be inserted into the report. Critical Alarm List,
Advisory Alarm List
Use the [NEXT OPTION] or [LAST OPTION] key to step Hardware Alarm List,
List* through options. System Status List,
If you select the Alarm Area List entry, the “Area Name” Disk Event List,
field appears for you to enter the desired area name. Operator Change Log,
Event Lists #1--10,
Alarm Area List,
Suppressed Alarm List
Plant Area
Counts back in minutes from the time the report is

generated. If “none”, the report will go back to the last
available alarm information.
NOTE: To use this field, the time must agree with the 1--9999 min
Time Period*
alarm time period in the specified list. For example, if 45
minutes is entered in the “Time Period” field, and the
alarm period of the list is 60 minutes, 15 minutes of the
alarm list will not be included.
* List entries that meet the conditions specified in all of these fields are included in the list object.

CC: 3-4-37
How to Configure Another Report in a Report
The generate object allows a generated report to be included in another

report. Figure 3.4.26 shows the generate object default entries and
how to configure the generate object. Table 3.4.6 lists the generate
object Report Configuration Window fields.
- To configure the generate object: Cursor to the “CREATE” field

1. Select generate as the object type. and press [ENTER].
Press [ENTER].

****************** START OF REPORT ******************
Type :Þgenerate Color :Þ1n white Row :Þ38 Col :Þ15

Include:Þ , CREATE DELETE
After this time : 25-Jul-92 Þ08:30:04 Mark :Þno Only UnprintedÞno
Last number of files :Þ0 Header :Þno File Number :Þ0
CONFIG 1
Figure 3.4.26. Report Configuration Screen with Generate Object

CC: 3-4-38
Table 3.4.6. Generate Field Descriptions
Field Description
Include The volume and filename of the generated report that is included in this object. Only
generated reports can be included in another report.
After this time* The beginning date and time of reports that can be included in this object. Reports
generated after this date and time can be included in this object.
Mark* Indicates whether or not the included reports have already been included in reports.
If “Yes” is entered, the system checks to see if the report is marked. If the report is
marked, it will not be included. If the report is not marked, the report will be marked
and included.
If “No” is entered, the report is included.
Only Unprinted* Indicates whether or not to include only unprinted reports in this object.
Last number of Indicates a specific number of the most recently generated reports to include in this
files* object. For example, an entry of 3 in this field indicates that the last three generated
reports (1, 2, and 3) are included in this object.
An entry of 0 (default entry) disables this field.
Header Indicates whether or not the header information from the included report file is
included in this object.
File Number* Indicates a specific report file number to be included in this object. The report file
numbers are listed on the Report File Contents screen for each filename.
An entry of 0 (default entry) disables this field.
* Any report generation that meets the values specified in these fields is included in the generate object.

CC: 3-4-39
Generating Reports
Reports can be configured to generate and print automatically using

fields on the Report Configuration screen.
How to Generate a Report Based on Time and Date
Reports can be configured to generate automatically on a time and date

basis. Figure 3.4.27 shows the procedure for entering time parameters
on the Report Configuration screen to control generation of a report. In
this example, the report will be generated at 12:05 AM, 8:05 AM, and
4:05 PM every day. Entries made in the “Time Entry” field are displayed
on the appropriate line above the entry area.
Figure 3.4.28 shows the same report modified to print only on weekdays
(Monday -- Friday). The same procedure can be used for the “Month”
and “Day/month” fields. For additional information on entering time
parameters, see Table 3.4.1.
Generate on alarm/event from:Þ

Month : any Generate on alarm/event from :Þ
Day/month: any Generate on alarm/event from :Þ
Day/week : any Month : any
Hour : any Day/month: any Month : any
Minute : never Day/week : any Day/month: any
Hour : 0,8,16 Day/week : any
ÞTime Entry :Þ Minute : never Hour : 0,8,16
Minute : 5
ÞHour :Þ0,8,16
Command : Þ ÞMinute :Þ5
Command : Þ
Command : Þ
- To enter time
parameters: 2. Enter hours when
1. Use [NEXT OPTION] report should be 3. Repeat procedure for
to select desired time generated. ”Minutes“ entry.
parameter. Then (Example: midnight, (Report generates at
press [ENTER]. 8AM, 4PM). Then 12:05AM, 8:05AM, & 4:05 PM)
press [ENTER].
Figure 3.4.27. Generating a Report Based on Time

CC: 3-4-40
Generate on alarm/event from :Þ

Month : any
Entries are displayed as a series of Day/month: any
values regardless of the entry Day/week : Mon,Tue,Wed,Thu,Fri
format. Day/week can be entered Hour : 0,8,16
as any of the following: Minute : 5
D 2--6 ÞDay/week:ÞMon,Tue,Wed,Thu,Fri
D Mon--Fri
D Mon,Tue,Wed,Thu,Fri Command : Þ
Figure 3.4.28. Generating a Report Based on Date

CC: 3-4-41
How to Generate a Report Based on Alarms or Events
Alarms or events from ControlBlocks or input blocks can be configured

to generate a report automatically. Figure 3.4.29 shows the procedure
for configuring alarms and events on the Report Configuration screen.
Figure 3.4.29 also shows examples of alarm and event entries.
NOTE: To generate a report, the alarm or event must be received by

the console. In other words, the block that generates the alarm or event
must be in a plant unit that has been assigned to the console or, if plant
units are not used in your system, the node containing the block must
be owned by the console. For information about plant units and node
ownership, see Chapter 1 of this manual.
NOTE: If a report is configured to generate on a ControlBlock logic step

event, the logic step must have “LogÞNone” configured for the report to
generate from the event.
NOTE: If a report is configured to generate on an event, the associated

event number must be configured in a console event list. For
information about event lists, see Chapter 6 of this manual.
- To configure alarms and events on the Report Configuration screen: 2. Press [ENTER].
1. Cursor to the “Generate on alarm/event” field and enter the tag or
address of the variable in any of the four entry fields.
REPORT CONFIGURATION
Description :Þ
Created : never
Filename : ÞSize :0 Last saved : never
Auto Print ?Þyes Max number of reports :Þ3 Print node :Þ16 Active ? Þyes
Generate on alarm/event from : Þ2C12 Þ=3A-9/PV Þ=2A-20/a Þ=5A-10
Any hardware
alarm, process Any process alarm
alarm or event from from a ControlBlock
an input block continuous output
Any process alarm Any process alarm,

from a ControlBlock hardware alarm, or event
continuous input from a ControlBlock
discrete step
Figure 3.4.29. Generating a Report Based on Alarms and Events

CC: 3-4-42
How to Generate a Report from the Report Configuration Screen
A report can be generated from the Report Configuration screen. If

changes have been made to the configuration of the body of the report,
the report must first be saved to disk so that the changes are included in
the generated report. Figure 3.4.30 shows the procedure for generating
a report from the Report Configuration screen.
- To generate a report from the Report Generation screen: 2. Press [ENTER]. A

1. Cursor to the “Command” Field and press [NEXT OPTION] to report is generated.
get the “Generate this Report” command.

Description :Þ
Created : never
Filename : ÞSize :0 Last saved : never
Generate on alarm/event from :ÞRPTTEST Þ Þ Þ
Month : any
Day/month: any
Day/week : any
Hour : any
Minute : never
ÞTIME ENTRY :Þ
Command : Þ Generate this Report
Figure 3.4.30. Report Configuration Screen with Generate this Report Command

CC: 3-4-43
How to Print a Report When it is Generated
A report can be configured to print automatically when it is generated.

Figure 3.4.31 shows the procedure for configuring the Auto Print
function.
- To configure the Auto Print function:

1. Cursor to the “Auto Print” field and type in “yes”
to receive a printout of the report when the
report is generated.

Description :Þ
Created : never
Filename : Þ Size :0 Last saved : never
Figure 3.4.31. Report Configuration Screen with Auto Print Field

CC: 3-5-1
Section 5:
Saving a Report to Disk
Initially, entries made on the Report Configuration screen are stored in

RAM memory. The configuration entries made in the body of a report
will not take effect until the report configuration has been written to the
disk. A report configuration is written to disk in two ways:
D Whenever the configuror exits the Report Configuration screen,
the configuration is automatically written to disk, if changes have
been made.
D A “Save to Disk” operation can be executed using the
“Command” entry field in the top portion of the Report
Configuration screen. Select the operation using [NEXT
OPTION], then press [ENTER].
RS3: Reports Saving a Report to Disk

CC: 3-6-1
Section 6:
Hints for Configuring and Using Reports

configuring reports, along with some configuration tips.
RS3: Reports Hints for Configuring and Using Reports

CC: 3-6-2
- I’m having trouble selecting objects.

To select an object, you must put the cursor at the upper left corner
of the object.
- The screen doesn’t display all lines of a report.
There is a limit to how much of a report can be displayed at a
console. The limits are listed below. These limits only affect the
display of a report; they do not affect the printing of a report.
Console type Limit
68000 console 40,000 characters or 2174 lines
68020 console 92,000 characters or 2174 lines

CC: 3-6-3
Configuration Tips
- How to move an object

When you delete or create an object, the object is kept in a buffer.
You can then recreate the object.
Therefore, to move an object:
1. Delete the object.
2. Cursor to the new location, and press [SELECT].
3. Cursor to the Create field and press [ENTER]. The object is now
in the new location.
- How to copy an object
When you delete or create an object, the object is kept in a buffer.
Therefore, to copy an existing object:
1. Delete the object.
2. Create the object again by moving the cursor to Create and
pressing [ENTER].
3. Cursor to the location where you want the copy, and press
[SELECT].
4. Cursor to the Create field and press [ENTER]. The object has
been copied in the new location.
5. Repeat steps 3 and 4 as many times as you need.
To create a new object and make copies of it:
1. Create the object.
2. Follow steps 3 through 5 in the previous procedure.
Marking Lines in Reports
You can use the [CTRL] [G] function to mark two places in a long report
to move quickly from one line in the report to another. To mark a line,
you move the cursor to that line and press [CTRL] and [G]. Then you
move the cursor to another line in the report and press [CTRL] and [G]
to mark that line. Each time you press [CTRL] [G], the cursor will move
between these two lines until you physically move the cursor to another
line and mark it with the [CTRL] [G] function.

RS3t
Chapter 4:
Trending
Section 1: Trending Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1-1

Console Trending Capabilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1-2
Multitube Command Consoles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1-3
How Trend File Information is Stored . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1-4
What Block Variables Can be Trended . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1-5
Using Trending Screens . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1-5
Enabling and Disabling Trending . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1-6
Trending Condition upon Console Restart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1-6
Section 2: Configuring Trend Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2-1

The Trend File Setup Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2-2
Configuring a Trend File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2-5
(Frequency and Duration Fields) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2-7
Section 3: Configuring Trend Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3-1

The Trend Group Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3-1
Trend Group Displays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3-5
Using the Slidewire . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3-6
Trend Group Scaling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3-7
Viewing Trend Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3-8
How Often Trend Group Displays Update . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3-9
Section 4: Archive Trend Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4-1

How a Backup Trend File is Saved . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4-2
Restoring and Reading Trend Archive Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4-3
Restoring and Reading Trend Archive Data from Tape . . . . . . . . . . . . . . . . . . . 4-4-3
Section 5: Hints for Configuring Trending . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5-1

Copying Trend Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5-1
Determining Trend Group Update Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5-1
RS3: Trending Contents

CC: ii
List of Figures
Figure Page
4.1.1 Trend Group Screen Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1-1
4.1.2 Example of Allocating Trend Files to Multitube Command Consoles . 4-1-3
4.1.3 The Trending Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1-4
4.2.1 Trend File Setup Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2-2
4.2.2 Trend File Configuration Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2-5
4.2.3 Trend File Configuration Screen with Frequency and Duration Fields 4-2-7
4.3.1 Trend Group Configuration Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3-2
4.3.2 Trend Group Screen with Slidewire . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3-6
4.3.3 Trend Group Screen with Scaling Fields . . . . . . . . . . . . . . . . . . . . . . . . . 4-3-7
4.3.4 Trend Group Screen with Fields that Determine Data Points and Time 4-3-8
4.3.5 Update Time Algorithm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3-9
4.3.6 Update Time in Even Seconds . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3-10
4.3.7 Update Time in Fractions of Seconds . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3-10
4.4.1 The Process of Saving a Trend File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4-2
4.4.2 Restoring and Reading a Trend File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4-3

CC: iii
List of Tables
Table Page
4.2.1 Trend File Setup Screen Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2-3
4.2.2 Trend File Configuration Screens . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2-6
4.3.1 Trend Group Configuration Screen Fields ....................... 4-3-3

CC: 4-1-1
Section 1:
Trending Operations
Trending is a process used to store data so that it can be accessed and

analyzed. The trend data may reside on any console on the Peerway.
Trending information is organized in trend files that reside on the

console hard disk. Trend files determine the frequency, duration, data
type, and other information about the trend data. Block variables from
trend files can be configured in trend group displays.
Figure 4.1.1 shows an example of a Trend Group screen.
For information about SRU trending, see SR:4.
4: No. 3 Boiler Drum 28-Jul-92 16:13:50
>200.00 >100.
100.00 50.
KLb/Hr %
>0.00 >0.
16:04:54 16:06:34 16:08:14 16:09:54 16:11:34 Current
>STACK 1 FCC-A
Time Scale >10 >Minutes >Start Time > 16:13:14 > 28-Jan-89
Data Pts >240 Value at
Tag Descriptor 28-Jan-86 16:08:00 Units Eng. Min Eng. Max
Stack 1 SENSOR A Drum Level 0.00 Inches -25.00 25.00
STACK 1 FCC-A Flow 160.00 KLb/Hr 0.00 200.00
STACK 1 DPR-A Drum Press 200.0 PSIG 0.0 600.0
STACK 1 FCC-B Steam Flow 150.00 KLb/Hr 0.00 200.00
CONFIG 1
Figure 4.1.1. Trend Group Screen Example
RS3: Trending Trending Operations

CC: 4-1-2
Console Trending Capabilities
Trend data is stored in trend files.

D Up to 10 trend files can be configured for each Command
Console. Fisher--Rosemount recommends trending only be done
from the master node.
D Up to 200 block variables can be configured per console.
Fisher--Rosemount recommends only 200 per disk to avoid
performance slowdowns.
D Up to 80 block variables can be configured in one trend file.
Trend data consists of block variable values.

D Trend data is stored on the console hard disk.
Each ControlBlock variable that is configured for trending takes up

available trend space on the associated Controller Processor.
D Each MPCI allows 40 links
D Each MPCII allows 80 links (see CB: 3--4 for more information)
D Each MPCI has 1856 bytes available for trending.
D Each MPCII has 4600 bytes available for trending.
D Each continuous block variable configured with a trending
frequency of a 5--second multiple (5 seconds, 10 seconds, 15
seconds, etc.) uses 14 bytes. Any other block variable uses 46
bytes.
Trend variables can be configured in trend groups so that trend data

can be displayed.
D Each trend group can contain up to 4 trend variables.
D Each 68020 Command Console node can contain up to 400
trend groups. Each 68000 Command Console node can contain
up to 100 trend groups.

CC: 4-1-3
Multitube Command Consoles
The CRT nodes of a Multitube Command Console share trend data files
that are stored on a console disk. Each CRT node can have a trend file
0. Any CRT node can display any trended variable, regardless of the
node on which the variable is stored.
To make the best use of the available disk space, allocate different
trend files to each Multitube Command Console. Trend files 1--9 cannot
be allocated to more than one CRT node. Figure 4.1.2 shows an
example of allocating trend files.
Assign trend files to each Multitube Command Console CRT node.

In this example:
Node 28 owns Node 30 owns Node 32 owns

trend files 1 -- 3. trend files 4 -- 6. trend files 7 -- 9.
Console Disk
Figure 4.1.2. Example of Allocating Trend Files to Multitube Command Consoles

CC: 4-1-4
How Trend File Information is Stored
Trend files are stored in the Trend Data Folder on a console disk. You
should configure the disk to provide enough storage space for the
configured trend data. (For information about configuring the disk, see
DT:3.)
One of the trend files (1--9) may be used to generate a system alarm
notifying the user to back up the Trend Data Folder. If a trend file is not
backed up, the file is deleted when the disk becomes full. Section 3
describes how to configure a Trend Overflow Warning, and Section 4
describes how trend files can be backed up to tape or disk.
Figure 4.1.3 shows how trend files are processed and how trend file
information is stored.
A trend file is configured. Trend File

Configuration
screen
Once the file is configured, trending Console

begins. The 60 most current data Buffer
points are stored in the console buffer Memory
memory.
When trending is enabled for the first

time after a trend file is configured, the
trend file is created on the disk. The trf# file
trend file name is trf# where # is the
number of the trend file, (e.g., trf1 to
trf9).
When the trf# file is full, the file is

renamed trf#b and a new trf# file is
created. An alarm message to back up
trf#b file
the trf#b file is displayed when this
process occurs. The trf#b file can be
backed up to tape or to another disk.
Figure 4.1.3. The Trending Process

CC: 4-1-5
What Block Variables Can be Trended
Trend files can include the following types of block variables:

D I/O block values
D ControlBlock continuous input values
D ControlBlock continuous output value
D ControlBlock discrete output values
Using Trending Screens
You can configure and display console trend files using the following
screens:
D Trend File Setup Displays information about a trend file.
D Trend File Allows configuration of a trend file.
Configuration
D Trend Group Allows configuration of a trend group.
Configuration
D Trend Group Displays graphic trend information about the
block variables in a trend group.
D Trend Group Displays titles of all configured console trend
Menu groups and the variables within each, with a
maximum of 400 groups allowed.

CC: 4-1-6
Enabling and Disabling Trending
You must enable trending for trend data to be stored on the console
hard disk. You must disable trending to perform operations such as
configuring trend files. When you disable trending, data is stored in the
console buffer memory but not on the console disk.
- To enable or disable trending from the Trend File Setup screen:
1. Cursor to the “Trend Status” field.
2. Select Enable or Disable.
3. Press [NEXT OPTION], then [ENTER].
- To enable trending from the command line, type:
ET [ENTER]
- To disable trending from the command line, type:
DT [ENTER]
Trending Condition upon Console Restart
If the console restarts, then the initial trending enabled/disabled

condition after restart depends on the trending condition when the
console configuration was saved.
If the console configuration was saved with trending enabled, and if the
console restarts, then trending is initially enabled after restart. If the
console configuration was saved with trending disabled, and if the
console restarts, then trending is initially disabled after restart.

CC: 4-2-1
Section 2:
Configuring Trend Files
This section describes how to set up and configure trend files. Because
trend files share a finite amount of console disk space, some
considerations should be made when configuring trend files. For more
information about trending restrictions, see Section 1 of this chapter.
RS3: Trending Configuring Trend Files

CC: 4-2-2
The Trend File Setup Screen
The Trend File Setup screen displays information about the trend files
at a console. Figure 4.2.1 shows the Trend File Setup screen.
Table 4.2.1 describes the fields on the screen.
- To call up the Trend File Setup screen, type:
TFS [ENTER]
The trending function can be enabled and disabled in

the “Trend Status” field.
TREND FILE SETUP 28-Jul-92 16:13:50

Trend Volume:>CC26 Trend Status:ÞEnabled History Volume:>CC26
--> Trend Overflow Warning uses file no. Þ5 at Þ4 hr before full.
Variables Disk
Warning File No. Freq. Data Type Duration Max Used Used Status
0 1 sec sample 1 min 10 6 0%
1 1 sec average 5 hrs 10 8 3% Good
2 10 sec average 1 day 25 23 3% Good
3 30 sec average 1 day 35 20 2% Good
4 1 min average 1 day 30 25 1% Good
--> 5 1 min average 7 days 50 38 7% Good
6 1 sec sample 1 min 0 0 0% Good
ÞReset Trending (press ENTER) Total : 150 20%

Operator Configurable File Þ0 Maximum : 200 100%
CONFIG 1
File Number Zero (0) is not

written to disk; it is used for To call up a Trend File Configuration screen, cursor
visual display only. to the file number and press [SELECT].
Figure 4.2.1. Trend File Setup Screen

CC: 4-2-3
Table 4.2.1. Trend File Setup Screen Fields
Type of data to be trended:

“average”= average of values is used for
Data Type Display only
trending.
“sample” = actual value is used for trending.
Percentage of disk space (1--100%) used by the

trend file. The percentage is based on the disk
Disk Used Display only
configuration, the frequency, the duration, and
the maximum number of variables.
Length of time the data is stored on the disk if

Duration the “Variables Max” field matches the “Variables Display only
Used” file.
Number of the trend file.

File No. NOTE: Trend File 0 is not written to disk. It Display only
stores real--time data only, and no history data is
available.
Freq. Time between trend data values. Display only
Volume name of the disk from which trend data

may be recalled for display. Under normal Up to 10 alphanumeric
History Volume:
characters
operation, this is the same as the Trend Volume.
Maximum number of variables allowed and the

Maximum: Display only
total percentage of available disk space.
One trend file that can have tags configured by

Operator Configurable the operator. A value of 0 indicates that no 0 to 9
File
trend files can be configured by the operator.
Allows initialization of configured trend data.

Reset Trending Trending must be reset when the console is [ENTER]
reloaded.
Status of the trend file:

“Error”= indicates that the file structure
(“Duration”, “Frequency”, and
“Variables Max” fields) does not match
Status Display only
the structure of the file currently on the
disk.
“Good”= indicates that the file is present on the
disk.
Sum of variables in the “Variables Max” field for

all four files, and the total percentage of disk
Total: Display only
space used by all files based on “Variables Max”
field.

CC: 4-2-4
Table 4.2.1. Trend File Setup Screen Fields (continued)
Two fields used to provide a warning that disk

trend space is low. The “Trend Overflow file no. Þ 1 to 9
Warning” message is generated when the trend
Trend Overflow file specified in the “file no.” field is within the
Warning time period specified in the “at” field of being full. at Þ 1--999 m (mins)
If the file is not backed up and the disk becomes 1--999 h (hrs)
full, data will be overwritten. For more 1--999 d (days)
information, see Section 4 of this chapter.
Disabled,
Trend Status: Status of the trending function on that console.
Enabled
Volume name of the disk on which trend data is Up to 10 alphanumeric

Trend Volume:
being recorded. characters
Maximum number of variables that can be

Variables Max Display only
configured for the file.
Number of variables currently configured for the

Variables Used Display only
file.

CC: 4-2-5
Configuring a Trend File
Trend files are configured on the Trend File Configuration screen. Up to

80 block variables can be configured for a trend file. Up to 10 trend files
can be configured on a console.
Figure 4.2.2 shows a Trend File Configuration screen. Table 4.2.2
describes the fields on the Trend File Configuration screen.
- To call up a Trend File Configuration screen, type:
TFC [file number] [ENTER]
- To page through the Trend File Configuration screens:
D Press [PAGE AHEAD] and [PAGE BACK].
A non--zero value must be entered in this

field in order to configure trend variables.
TREND FILE CONFIGURATION 27-Jul-92 10:16:47

Variables Disk
File No. Frequency Data Type Duration Max Used Used
>1 >5 secs >sample >5 days >10 4 7 %
Tag Descriptor
1 >STACK 1 SENSOR A Level
2 >STACK 1 VALVE A Valve
3 >STACK 1 VCC-A Valve controller
4 >STACK 1 FCC-A Flow
5 >
6 >
7 >
* MORE *
FULL CONFIG 1
- To call up a ControlBlock Faceplate screen or an I/O Block Configuration screen:

D Cursor to the variable and press [SELECT].
Figure 4.2.2. Trend File Configuration Screen

CC: 4-2-6
Table 4.2.2. Trend File Configuration Screens
Displays the average or sample data type to be

trended.
“Average” indicates a rolling average taken every
second. The result is sent to the console at the time
specified in the “Frequency” field. For example, if the
frequency is 5 seconds, an average of trending data is
Data Type taken once a second for 5 seconds. The composite average, sample
result is sent to the console from the Controller
Processor.
“Sample” indicates one sample of data. For example,
if the frequency is 43 seconds, one sample of trending
is taken every 43 seconds. The result is sent to the
console from the Controller Processor.
The descriptor for the block from which the variable is

Descriptor Display only
obtained.
Percentage of disk space used by the file based on

Disk Used Display only
the maximum number of variables.
Length of time data is stored on the disk. The

specified duration is accurate only if the “Variables
Max” field matches the “Variables Used” field. For 1--999 m,h,d
Duration*
example, if the “Duration” is 1 hour, the “Variables (minutes, hours, days)
Max” field is 10, and the “Variables Used” field is 1,
then the duration will actually be10 hours.
File No. Number of the trend file. 0--9
1--999 s (seconds)
Frequency* Sampling time between data. 1--59 m (minutes)
1 h (hour)
Any existing tag or

Tag Tag or address of the block variable to be trended.
address
Maximum number of variables to be stored in the file.

Variables Max* NOTE: You must enter a non--zero number in this 0--80
field in order to enter information in the “Tag” field.
Variables Used Number of variables currently configured for the file. Display only
* This entry is dependent on the disk space available at the time of entry.

CC: 4-2-7

(Frequency and Duration Fields)
You configure the sampling frequency and the length of time that data is
to be saved individually for each trend file on a Trend File Configuration
screen. Sampling frequency is designated in the “Frequency” field. The
length of time data is to be saved is designated in the “Duration” field.
The combination of “Frequency” and “Duration” field values for the trend
files determine the total number of trend values that are configured to
be stored on the console. You must must ensure that enough disk
space has been configured for these trend values. For more
information on configuring disk space, see DT:3.
Figure 4.2.3 shows the Trend File Configuration screen with the
“Frequency” and “Duration” fields.
“Frequency” determines how often a data sample is taken.

“Duration” determines how often data is saved. In this
example, data will be averaged every 30 seconds for 1 day.
TREND FILE CONFIGURATION 27-Jul-92 10:16:47

Variables Disk
File No. Frequency Data Type Duration Max Used Used
>1 >5 secs >sample >5 days >10 4 7 %
Tag Descriptor
1 >STACK 1 SENSOR A Level
2 >STACK 1 VALVE A Valve
3 >STACK 1 VCC-A Valve controller
4 >STACK 1 FCC-A Flow
5 >
6 >
7 >
* MORE *
FULL CONFIG 1
Figure 4.2.3. Trend File Configuration Screen with Frequency and Duration Fields

CC: 4-3-1
Section 3:
Configuring Trend Groups
A trend group contains up to four block variables that have been

configured in trend files. This section describes how to configure a
trend group and a trend group display in order to view trending data.
The Trend Group Configuration
Each trend group is configured on a Trend Group Configuration screen.

Up to 400 trend groups can be configured for one Command Console
CRT node.
Figure 4.3.1 shows the Trend Group Configuration screen. Table 4.3.1
describes the fields on the Trend Group Configuration screen.
- To call up the Trend Group Configuration screen:
D Type TGC [group number] [ENTER]
or
D Press [EXCH] while viewing a Trend Group screen.
RS3: Trending Configuring Trend Groups

CC: 4-3-2
- To add a variable to a tag group: - To call up a Trend Group Configuration screen

1. Cursor to the “Tag” field. for another group:
2. Type in the tag or address of the variable, D Change the number in this field and press
and press [ENTER]. [ENTER] or press [PAGE AHEAD] or [PAGE
BACK].
TREND GROUP CONFIGURATION 28-Jul-92 16:13:50

Trend Group Number >4
Group Description >No. 3 Boiler Drum
Tag Descriptor Node File Freq. Type State
> LC-204/PV Drum Level >32 >3 30 secs average Good
> FC-205/PV FW Flow >1 >3 1 sec average Good
> PI-204/PV Drum Press >* >3 5 secs average Good
> FI-210/PV Steam Flow >2 >3 1 sec average Good
Data Pts>240 Time Scale>1 >Minutes

Vertical Graph Scaling (default)
Trend number >1 Min >0. % Max >100. %
CONFIG 1
- To access a ControlBlock Faceplate

screen:
Fields that determine the
D Cursor to a selected tag and press engineering units scaling of the
[SELECT]. graph on the Trend Group screen.
“Data Pts” field is displayed on consoles

with pixel graphics.
Figure 4.3.1. Trend Group Configuration Screen

CC: 4-3-3
Table 4.3.1. Trend Group Configuration Screen Fields
The current status of the variable or file. The status conditions

include:
Bad Kind= Input block variable has been changed since

originally listed in the file. This condition
sometimes can be cleared by re--entering the tag
or address.
Block Cfg= Block not found.
Good= Data is available for display
Currently Initial = This message may appear prior to “Good” to Display Only
indicate that the first piece of data is being
received.
New Trend = Variable was just added to the file and no data
has been received yet.
No Data = Communication error just occurred affecting the

transfer of trend data.
No Room= Limit of 1856 bytes for the Controller Processor

has been reached.
File Cfg= The variable is not configured in the specified file.
No Node= Node not found.
Node Cfg= The variable is not configured on the specified

node.
Data points being displayed. Trend Group screen defaults to this

Data Pts 60, 120, 240, 480
entry.
Descriptor Descriptor for the block from which the variable is obtained. Display only
File Trend file number where the variable trend data is stored. 0--9
Sampling frequency from the “Frequency” field on the Trend File

Freq. Display only
Configuration screen
Group Maximum of 20
User--assigned display title.
Description characters
Node where the trend file containing variable trend data exists. A
2--992
console can display trend data stored at any console on the
Node (even numbers
PeerWay. An asterisk in this field indicates that the default disk
only)
drive is searched for the trend data.
Up to 16
Tag Tag or address of a block variable that is configured in a trend file. alphanumeric
characters

CC: 4-3-4
Table 4.3.1. Trend Group Configuration Screen Fields (continued)
Desired time scale of the graph. Trend Group screen defaults to 1--99, Minutes,
Time Scale
this entry. Hours, or 366 Days
Trend Group
Number of the trend group being configured. 1--400
Number
Trend data type from the “Data Type” field on the Trend File
Type Display only
Default engineering units scale of the graph on a Trend Group

screen. The default engineering units are displayed each time you
call up the Trend Group screen. Vertical Graph Scaling fields
consist of the “Trend Number”, “Min”, and “Max” fields:
Trend number: 1--4
1 4
Trend Number of the block variable that has its
Vertical Minimum:
Number= engineering units displayed on the left side of the
Graph 0--999999
graph.
Scaling Maximum:
Min= Minimum percent engineering units value 0--999999
displayed on the right side of the graph.
Max= Maximum percent engineering units value

displayed on the right side of the graph.

CC: 4-3-5
Trend Group Displays
The Trend Group screen displays graphic trend information about the
block variables in a trend group. The Trend Group screen displays 60
samples of data on a console with character graphics and 60 to 480
samples of data on a console with pixel graphics. The most recent
information is on the right side of the graph and the oldest information is
on the left side of the graph. Figure 4.3.2 shows an example of a Trend
Group screen.
- To call up the Trend Group Screen
D Type TG [group number] [ENTER]
or
D Press [EXCH] while viewing a Trend Group Configuration screen.

CC: 4-3-6
Using the Slidewire
The cursor can be moved into the graph on the Trend Group screen
and used as a slidewire. Figure 4.3.2 shows the use of the slidewire.
The variable values at the slidewire location are shown at the bottom of
the screen. To get the most recent values to appear again, move the
slidewire to the far right of the graph.
NOTE: The accuracy of these values is approximately 0.5% from --12%

to 112% of the range.
NOTE: On consoles with pixel graphics, move the cursor vertically to

make fine adjustments. When the cursor is at the top half of the screen,
the reading will be to the right of the cursor. When the cursor is at the
bottom half of the screen, the reading will be to the left of the cursor.
Slidewire
>200.00 >100.
100.00 50.
KLb/Hr %
>0.00 >0.
16:04:54 16:06:34 16:08:14 16:09:54 16:11:34 Current
>STACK 1 FCC-A
Time Scale >10 >Minutes >Start Time > 16:13:14 > 28-Jan-89
CONFIG 1
“Data Pts” field is displayed on consoles

Variable values
with pixel graphics.
Figure 4.3.2. Trend Group Screen with Slidewire

CC: 4-3-7
Trend Group Scaling
The graph on the Trend Group screen has two adjustable scaling areas.
The scaling area to the right of the graph shows scaling as a percent of
the engineering units. For example, a value of 100 represents the “Eng
Max” value of a variable. A value of 0 represents the “Eng Min” value.
The left side of the graph shows the engineering units of one of the
trend group variables. The engineering units are associated with the
values on the right side of the graph.
The default scaling values on the right side of the graph are determined
by the “Min” and “Max” fields on the Trend Group Configuration screen.
The default variable engineering units displayed on the left side of the
graph are the units of the variable defined in the “Trend Number” field
on the Trend Group Configuration screen.
Figure 4.3.3 shows the Trend Group screen with fields used for scaling.
Engineering units scaling Percent scaling of the
of the trend variable trend variable
>100.
>25.00
00.00 50.
Inches %
>-25.00 >0.
16:04:54 16:06:34 16:08:14 16:09:54 16:11:34 Current
>STACK 1 DPR-A
Time Scale >10 >Minutes >Start Time > 16:13:14 > 28-June-92
CONFIG 1
- To change the variable that has its units displayed on

Variable tag/address
of current scaling the left side of the graph:
D Press [NEXT OPTION] to scroll through tags until the
appropriate tag appears., then [ENTER].
Figure 4.3.3. Trend Group Screen with Scaling Fields

CC: 4-3-8
Viewing Trend Data
The graph on the Trend Group screen displays trend data. The Trend
Group Display screen defaults to the current trend group display.
Figure 4.3.4 shows the fields of the Trend Group screen that are used
to configure the graph on a Trend Group screen.
Data Pts= Number of data points being displayed (Format: 60, 120, 240, 480).
Time Scale= Desired time scale of the graph ( Format: 1--366, Minutes, Hours, or Days).
Start /End = Time and date of the newest or oldest data on the graph. If a time is entered in this
field, the field displays a “History” status and the graph does not update. (Format: Time
is HH:MM:SS; Date is DD--MM--YY)
“Start” Time is shown on the right side of the graph and all data viewed is older than the start time.
“End” Time is shown on the left side of the graph and all data viewed is newer than the end time.
>22.00 >100.
00.00 50.
Inches %
>-25.00 >0.
16:04:54 16:06:34 16:08:14 16:09:54 16:11:34 Current
>STACK 1 DPR-A
Time Scale >10 >Minutes >Start Time > 16:13:14 > 28-June-92
CONFIG 1
- Current/History status
To turn a trend on or off:
Current indicates that the graph is
D Cursor to the tag of the trended link
showing the most current data and
and press [ENTER]. While the trend
that the graph is continually updating.
is turned off, “*OFF*” appears in the
“Value at” field. History indicates that the graph is
showing data from a past time and
that the graph is not updating.
Figure 4.3.4. Trend Group Screen with Fields that Determine Data Points and Time

CC: 4-3-9
How Often Trend Group Displays Update
In order to reduce request message load on controllers, trend groups

use an update algorithm to determine how often to refresh the display.
Trend groups determine update time as a function of the time scale and
the number of trend data points.
Figure 4.3.5 shows the update algorithm that trending uses to calculate
the update time. You can use this algorithm to assess the impact of
“Time Scale” and data points on update time. For additional information
about the Trend Group Display, see page 4-3-5.
NOTE: The formula that is shown in Figure 4.3.5 is used by the display
only and does not affect how the data is stored on the disk.
If: Time Scale % Data Points = 0

Time Scale
Update Time =
Data Points
or
If: Time Scale % Data Points = Fraction of a Second

Time Scale
Update Time =
Data Points ∙ n
Where Data Points and n are:

Data Points n
480 8
240 4
120 2
60 1
NOTE:
D The update time is in the units of time specified in the “Time Scale” field: hours or minutes.
D The operator % stands for the mathematical function modulus.
Figure 4.3.5. Update Time Algorithm

CC: 4-3-10
The trend group displays can update only in even seconds. If the
update time, as computed by the above formula (Time Scale % Data
Points), contains a fraction of a second, the trend group will multiply the
result by the “n” (see formula) to round off the update time to an even
second.
D In Figure 4.3.6, 480 data points and a time scale of 40 minutes
result in an update time of 5 seconds.
40 minutes = 5 seconds
480
NOTE: The trend data requires 5 seconds to update. In this case,
Time Scale
Update Time =
Data Points
Figure 4.3.6. Update Time in Even Seconds

D In Figure 4.3.7, 480 data points and a time scale of 41 minutes
result in an update time of 5.125 seconds. Because the update
time contains a fraction of a second (0.125), the display must
wait 41 seconds (that is a multiple of eight 5.125 update times)
before it can update.
41 minutes = 5.125 seconds

480
NOTE: The trend data requires 41 seconds (5.125 * 8) to update. In this case,
Time Scale
Update Time =
Data Points ∙ n
Figure 4.3.7. Update Time in Fractions of Seconds

CC: 4-4-1
Section 4:
Archive Trend Data
This section describes how to save trend files, how to view historical
trend data, and how to reload previously configured trend files from
tape.
The Disk and Tape Functions Manual gives instructions for saving a
trend file to tape or disk, reloading the file from tape or disk, and
restoring a tape.
NOTE: When you save a trend file, you should also save the
console trend file configuration and trend group configurations.
When you restore the trend data, these configurations should also
be restored. Otherwise, you will not be able to view the restored
trend data.
RS3: Trending Archive Trend Data

CC: 4-4-2
How a Backup Trend File is Saved
When a trf# file becomes backup trend file trf#b, an alarm message is
displayed notifying the user to save the file. The backup trend file can
be saved to tape or disk within the time that is shown in the “Duration”
field on the Trend File Configuration screen. If the file is not saved, the
contents are deleted and the data is lost.
Figure 4.4.1 shows the process for saving a trend file to tape or disk.
trf# file
When the trf# file is full, the file is

renamed trf#b, a backup file. The
backup trend file can be saved to tape, trf#b file
floppy disk, or another hard disk.
A backup trend file is saved to disk or

tape on a Disk Activity screen. To
avoid duplicate file names, rename a
file when it is saved to tape or disk.
The first four characters of the trend Disk Activity Screen
file, trf#, must remain the same.
Rename by adding one or more
characters to this trend file name.
Figure 4.4.1. The Process of Saving a Trend File

CC: 4-4-3
Restoring and Reading Trend Archive Data
Restoring and reading trend archive data can be performed by reading

backup trend file tapes, or by directly reading the file over the PeerWay.
Restoring and Reading Trend Archive Data from Tape
Figure 4.4.2 shows the process of restoring a trend file tape and
reading the trend data on a Trend Group screen.
- To restore a trend file tape:

1. Load the archive tape to the
console disk.
The Tape Directory screen lists all TAPE DIRECTORY

files that are on the tape. SCREEN
2. Restore the files using the Disk DISK ACTIVITY

Activity screen. SCREEN
3. Call up the Trend Group

screen. Specify the time
of the trending data in Time Scale >10 >Minutes Start Time>22:48:14 >05-Jan-89
the “Start Time/End
Time” field. The archive
trend data is displayed
on the trend graph.
Figure 4.4.2. Restoring and Reading a Trend File

CC: 4-5-1
Section 5:
Hints for Configuring Trending

configuring trending.
- Why doesn’t the block tag on a Trend Group display show the
alarm condition of the block?
The block tag only shows the alarm condition of the trended
variable.
- On the Trend Group Configuration screen, the “Currently” field
displays Bad Kind for a variable.
You may be able to clear the condition by reentering the variable in
the “Tag” field.
Copying Trend Files
If you copy a trend file (using the Disk Activity screen), the copy file is
not functional until you enable and disable it. The processor will
continue to write to the original file until you enable and disable the new
file.
Determining Trend Group Update Time
In order to reduce excess data request messages to controllers, trend

groups use update time to determine how often to update trend data.
The trend group computes update time as a function of time scale and
the number of trend data points. For more information on how update
time works, see “How Often Trend Group Displays Update” on
page 4-3-9.
RS3: Trending Hints for Configuring Trending

RS3t
Chapter 5:
Commands
Section 1: Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1-1

Symbols Used . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1-2
Section 2: Hints for Using Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2-1
RS3: Commands Contents

CC: ii
List of Tables
Table Page
5.1.1 Symbols Used in Command Lines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1-2
5.1.2 Commands that Call Up Screens . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1-3
5.1.3 Commands that Perform Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1-14
5.1.4 Commands that Perform Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1-15
RS3: Commands Contents

CC: 5-1-1
Section 1:
Commands
This section provides the list of commands that can be entered on the
RS3ä CRT to call up screens and perform operations. Commands are
entered on the command line, which is the top line of the CRT screen.
Table 5.1.1 explains the symbols and text used in Table 5.1.2 and
Table 5.1.3. Table 5.1.2 lists commands that call up screens.
Table 5.1.3 lists commands that perform operations.
RS3: Commands Commands

CC: 5-1-2
Symbols Used
The Entry column in Table 5.1.2 and Table 5.1.3 lists the keyboard
entries that must be made on the command line to call up the desired
screen or to perform the desired operation.
Special symbols and text are used to describe what keyboard entries
you need to make. Table 5.1.1 provides explanations of the symbols
and text.
Table 5.1.1. Symbols Used in Command Lines
Symbols or Text Explanation
Indicates that the entry is mandatory.

Uppercase and/or
DD: For example, you must type DD: to call up the Disk
bold letters
Directory.
Indicates that the entry is optional.

( ) Parentheses For example, (node# : drive #) means that you can
optionally type the node number and drive number.
Indicates that the text represents a single key.

[ ] Brackets For example, [ENTER] means press the ENTER key;
[R] means press the R key.
Indicates that the text represents one or more characters.

For example, (area name) means type in an area name;
(volume or node #) means enter the volume name or the
tag Italic
node number.
An entry that is both in bold and italics indicates the entry
is mandatory and variable in characters.
Indicates the space bar.

sp This is a special notation that represents the space bar.
For example, [sp].
RS3: Commands Commands

CC: 5-1-3
Table 5.1.2. Commands that Call Up Screens
Screen Called Up Entry Command Line Text
Alarm and Event Lists
Active Batch Alarms BAAA [ENTER] BATCH Active Alarms
Alarm Annunciation AAC [ENTER] Alarm Annunciation Cnf:
Active Hardware Alarms HA [ENTER] Hardware Active Alarms
Active Process Alarms AAL [ENTER] Alarm Active List
Active Process Alarms PA [ENTER] Process Active Alarms
Active Suppressed Alarms ASA [ENTER] Alarm Suppressed Actv
Active System Status SSA [ENTER] System Status Active
Advisory Active Alarms ADAA [ENTER] ADV Actv Alrms
Advisory Cleared Alarms ADCA [ENTER] ADV Clrd Alrms
Cleared Batch Alarms BACA [ENTER] BATCH Cleared Alarms
Cleared Hardware Alarms HC [ENTER] Hardware Cleared Alarms
Cleared Process Alarms PC [ENTER] Process Cleared Alarms
Cleared Suppressed Alarms ASC [ENTER] Alarm Suppressed Clrd
Cleared System Status SSC [ENTER] System Status Cleared
Critical Active Alarms CRAA [ENTER] CRIT Actv Alarms
Critical Cleared Alarms CRCA [ENTER] CRIT Clrd Alarms
Disk Event List DEL [ENTER] Disk Event List
Event List EL: (event list#) [ENTER] Event List:

CC: 5-1-4
Table 5.1.2. Commands that Call Up Screens (continued)
Alarm and Event Lists (continued)
Plant Area (ACTV) AN: [area name] [ENTER] Area Name:
Plant Area (ACTV) AAA (area name) [ENTER] Actv Area Alms:
Plant Area (CLRD) CAA [area name] [ENTER] Clrd Area Alms:
Alarms and Events
Alarm Configuration AC [ENTER] Alarm Configuration
Alarm List Configuration ALC [ENTER] Alarm List Configuration
Alarm Log Display ALD (alarm log filename) [ENTER] Alm Log Disp:
Alarm Log Display ALS (log display configuration name) [ENTER] Alm Log Search:
Configure Alarm Broadcast CAB [ControlFile node#] [ENTER] Cnfg Alarm Broadcast
Event List Configuration ELC [ENTER] Event List Configuration
Log Display Configuration LDC [ENTER] Log Display Config:
Alarm Areas
Area Name Configuration ANC [ENTER] Area Name Config:
Graphic for specified area ANG [area name] [ENTER] Area Name Graphic:
Batch & RBLC
BAQ (task tag) [ENTER] or

Batch Acquire Queues BATCH Queues:
BAQ (node#: task#) [ENTER]
Batch Configuration BAC: [ENTER BATCH Config:

CC: 5-1-5
Batch & RBLC (continued)
BACR (filename) [ENTER] or

Batch Control Recipe Config BATCH Control Rec:
BACR (batch id) [ENTER]
BAI (task tag) [ENTER] or

Batch Input BATCH Input:
BAI (node#: task#) [ENTER]
BAL: (volume , filename) [ENTER] or

Batch Log BATCH Log:
BAL: (node#, filename) [ENTER]
Batch Master Recipe Config BAMR (filename) [ENTER BATCH Master Rec:
Batch Material Properties BAMP [ENTER BATCH Mat Prop
Batch Materials Table BAMT (filename) [ENTER BATCH Material Tbl:
BAM: (task tag) [ENTER] or

Batch Monitor BATCH Monitor:
BAM: (node#: task#) [ENTER]
Batch Operations Table BAOT (filename) [ENTER BATCH Oper Tbl:
BAO: (task tag) [ENTER] or

Batch Overview BATCH Overview:
BAO: (node#: task#) [ENTER]
Batch Plant Unit Status BAP [ENTER] BATCH Plant Unit
BAR: (task tag) [ENTER] or

Batch Run BATCH Run:
BAR: (node#: task#) [ENTER]
BAS: (volume , filename) [ENTER] or

Batch Script BATCH Script:
BAS: (node#, filename) [ENTER]
Batch Units Table BAUT (filename) [ENTER] Batch Unit Tbl:

CC: 5-1-6
Batch & RBLC (continued)
Batch Working Recipe BAWR (tag) [ENTER] BATCH Working Rec:
RBL Directory (Batch) BAD (node# or volume name) [ENTER] BATCH Directory:
RBL Directory (RBL) RBLD (node# or volume name) [ENTER] RBL Directory:
BAF (volume , filename) [ENTER] or

RBL File Contents (Batch) BATCH File Cont:
BAF (node#, filename) [ENTER]
RBL File Transfer FT [ENTER] File Transfer
RBLF (volume , filename) [ENTER] or

RBL File Contents (RBL) RBL File Contents:
RBLF (node#, filename) [ENTER]
RBLC Monitor RBLM (block tag or address) [ENTER] RBLC Monitor
RBLS (volume , filename) [ENTER] or

RBLC Script RBLC Script:
RBLS (node#, filename) [ENTER]
Block
Block Directory CBD: (Controller Processor address) [ENTER] Cont Block Directory:
Block Print Setup BP [ENTER] Block Print
Block References BR (tag or address) [ENTER] Block References:
Block Status CBS (Controller Processor address) [ENTER] Cont Block Status:
Continuous Diagram BD (tag or address) [ENTER] Block Diagram:
Continuous Faceplate BF (tag or address) [ENTER] Block Faceplate:
Continuous Links BL (tag or address) [ENTER] Block Links:

CC: 5-1-7
Block (continued)
Group Display screen or

TA (tag or address) [ENTER] Tag/Address:
CB Continuous Faceplate
Callup Buttons
Alarm Annunciation AAC (command#) [ENTER] Alm Annunciation Cnf:
Callup Buttons CCB (option keyboard#) [ENTER] Config Callup Buttons
Calls up the screen or performs the

operation that is assigned to a callup CUB: [button#] [ENTER] Call Up Button:
button.
Display Buttons CDB (button#) [ENTER] Config Display Buttons:
Color
Color Configuration CCU [ENTER] Config Color Usage
Master Color Selection CCP [ENTER] Config Color Palette
Console Configuration
Console Configuration CCC [ENTER] Config Command Console
MiniConsole Configuration CM [ENTER] Configure Miniconsole
Multitube Configuration CCC [ENTER] [PAGE AHEAD] Config Command Console
Console Menu
Menu Command Console MCC [ENTER] Menu Command Console
Menu MiniConsole MM [ENTER] Menu Miniconsole

CC: 5-1-8
ControlFile and I/O
ControlFile Dump CFD node# or Controller Processor# [ENTER] Cont File Dump:
ControlFile Dump or Node Dump ND node# [ENTER] Node Dump:
ControlFile Links CFL (ControlFile#) [ENTER] Cont File Links:
ControlFile Status CFS (ControlFile#) [ENTER] Cont File Status:
Field I/O Status FS (Controller Processor address) [ENTER] Field I/O Status:
TL (volume , filename) [ENTER] or

Transmitter Maint Log Trans Log:
TL (node#, filename) [ENTER]
Diagnostics
Background Diagnostics MCT [ENTER] Menu Confidence Tests
Memory Dump MD node#, (filename) [ENTER] Memory Dump
Memory View MV [ENTER] Memory View
Diogenes Interface
Diogenes I/F Configuration CDI (node#) [ENTER] Configure Diogenes I/F:
Disk and File
Calls up specified file DDF [ENTER] Disk Dir File:
CDS (volume , filename) [ENTER] or

Configure Download Script Cfg Dnld Script:
CDS (node#, filename) [ENTER]
Disk Activity (last screen) DA [ENTER] Disk Activity

CC: 5-1-9
Disk and File (continued)
Disk Directory DD: (node#: drive#) [ENTER] Disk Dir:
Disk Directory PeerWay DDP [ENTER] Disk Dir PeerWay
Disk Folder Configuration DC: (node#) [ENTER] Disk Configure:
Graphics
Configure Character PGC [ENTER] Pr Graph Char
PG: [volume , filename] [ENTER] or

Graphic Viewing Pr Graph:
PG: [node#, filename] [ENTER]
Link Editor LE (node) : (drive) Link Edit:
PGG (volume , filename) [ENTER] or

Process Graphics Generation Pr Graph Gen:
PGG (node#, filename) [ENTER]
Process Graphics Symbol generation PGS (volume , filename) [ENTER] or

Pr Graph Sym:
screen PGS (node#, filename) [ENTER]
HIA
Configure HIA CH (node #) [ENTER] Config HIA:
Login
User Name Detail UND (login_name) [ENTER] User Name Detail
Plant Unit Access PUA (filename) [ENTER] Plant Unit Access
User Profile Directory UPD [ENTER] User Profile Directory
Login CUP [ENTER] Change User Password

CC: 5-1-10
Login (continued)
Login LI [ENTER] Log In :
Log out LO [ENTER] Log Out :
Material History
Material History MH: (material history display#) [ENTER] Material History:
Material History Configure MHC (material history display#) [ENTER] Material History Config:
Message Pairs
STD Message Pairs MPS [ENTER] Message Pairs Std
User Message Pairs MPU [ENTER] Message Pairs User
Operating Displays
Group G: (group number) [ENTER] Group:
Group Directory GD: [ENTER] Group Directory:
Overview O: (overview number) [ENTER] Overview:
Overview Directory OD: [ENTER] Overview Directory:
Unit U: (unit number) [ENTER] Unit:
Unit Directory UD: [ENTER] Unit Directory:
Operator Log
Operator Change Log OL [ENTER] Operator Log

CC: 5-1-11
PeerWay and Plant
PeerWay Node PN (node#) [ENTER] PeerWay Node:
PeerWay Overview PO (PeerWay#) [ENTER] PeerWay Overview:
PeerWay Performance PP [ENTER] PeerWay Performance
Plant Status PS (node#) [ENTER] Plant Status:
Plant Unit Configuration PUC [ENTER] Plant Unit Configuration
PLC
Configure PLC CP [ENTER] Configure PLC:
Reports
RG (volume , filename) [ENTER] or

Report Configuration Reprt Gen:
RG (node#, filename) [ENTER]
Report Configuration Directory RCD (node#) [ENTER] Reprt Config Directory:
RFC (volume , filename) [ENTER] or

Report File Contents Reprt File Contents:
RFC (node#, filename) [ENTER]
RRD: (volume , filename) [ENTER] or

Report Read Directory Reprt Read Directory:
RRD: (node#, filename) [ENTER]
RR: (volume , filename) [ENTER] or

Report Read/Scan Reprt Read:
RR: (node#, filename) [ENTER]
Report Status RS (node#) [ENTER] Reprt Status:

CC: 5-1-12
RFI
Configure RFI CR: (node#) [ENTER] Configure RFI:
RNI
Configure RNI CRN (node#) [ENTER] Configure RNI:
RNI Status CRN (node#) [ENTER] [EXCHANGE] Configure RNI:
SCI
Configure SCI CS (node#) [ENTER] Configure SCI:
SRU & SQC
SQC (SQC chart tag) [ENTER] or

SQC Configuration SQC Chart Conf:
SQC (node#: chart#) [ENTER]
SQC Display SQD (node#: chart#) [ENTER] SQC Display:
SQC Titles SQT (node#) [ENTER] SQC Titles:
SRU Status Display SRS [ENTER] SRU Status:
SRU Trend Config SRT [ENTER] SRU Trend Config:
Trend
Trend File Configuration TFC (trend file#) [ENTER] Trend File Config:
Trend File Setup TFS (trend group#) [ENTER] Trend File Setup
Trend Group TG: (trend group#) [ENTER] Trend Group:
Trend Group Configuration TGC [ENTER] Trend Group Config:

CC: 5-1-13
Trend (continued)
Trend Group Menu TGD: (menu page#) [ENTER] Trend Group Directory
Trend Group Menu TGM (menu page#) [ENTER] Trend Group Menu
Tuning Displays
Tuning Display TD: (tuning display#) [ENTER] Tuning Display
Tuning Display Directory TDD [ENTER] Tuning Display Directory
VAX
Host Mode HM (node#) [ENTER] Hostmode:
VAX RPQNA Status Display VS (node#) [ENTER] VAX Status:

CC: 5-1-14
Table 5.1.3. Commands that Perform Operations
Operation Performed Entry Command Line Text
Alarm and Event Lists*
Active Process Alarms List—Print

P [sp] PA [ENTER] Pr Process Alarm List
Cleared Process Alarms List—Print
Active Process Alarms List— Print

P [sp] AA [ENTER] Pr Alarm Active List
Cleared Process Alarms List—Print
Active System Status Alarms List—Print

P [sp] SSA [ENTER] Pr System Status Active
Cleared System Status Alarms List—Print
Active Hardware Alarm List—Print

P [sp] HA [ENTER] Pr Hardware Alarm List
Cleared Hardware Alarm List—Print
Active Batch Alarms List—Print

P [sp] BA [ENTER] Pr BATCH Alarm List
Cleared Batch Alarms List—Print
Disk Event List—Print P [sp] DEL [ENTER] Pr Disk Event List
Event List—Print P [sp] EL [:] event list# [ENTER] Pr Event List:
* If you perform one of these print operations from the command line, the information
is printed at the node configured in the “Backup Printer Node” field on the Alarm List
Configuration screen. In addition, the alarm list unprinted count does not change.
CC: 5-1-15
Table 5.1.4. Commands that Perform Operations
Alarms and Events
All alarms on a screen—acknowledge

SA [ENTER] Screen Acknowledge
(cannot be used on all screens)
Alarm area—Disable AD: area name [ENTER] Area Disable:
Alarm area—Enable AE: area name [ENTER] Area Enable:
Alarm banner mode

ASD [ENTER] Alarm Summary Disable
(bottom line of display)
Alarm summary mode

ASE [ENTER] Alarm Summary Enable:
(bottom line of display)
Alarm logging—Disable DLA (node#) [ENTER] Disable Logging Alarms:
Alarm logging—Enable ELA (node#) [ENTER] Enable Logging Alarms:
Alarm regeneration—Initiate AR (SRU node#) [ENTER] Alarm Regen:
Batch
Batch—Disable DBAS (node#) [ENTER] Disable Batch System:
Batch—Enable EBAS (node#) [ENTER] Enable Batch System:
Batch Bubble memory—Initialize BAW (node#) [ENTER] BATCH Wipe:
Batch Log—Disable DBAL (node#) [ENTER] Disable Batch Log:
Batch Log—Enable EBAL (node#) [ENTER] Enable Batch Log:
Console
Eject a floppy disk EF (node#) [ENTER] Eject Floppy:
Reboot the console RBC [ENTER] Re--Boot Console

CC: 5-1-16
Table 5.1.4. Commands that Perform Operations (continued)
Console (continued)
Shut down operation of disk DS: (node#) [ENTER] Disk Shutdown
Console Screens
Mark—remove RM mark# [ENTER] Remove Mark:
Next page—call up PF [ENTER] Page Forward
Previous page—call up PB [ENTER] Page Backward
Recall the previous screen R: (node#) [ENTER] Recall:
ControlFile
Kill operation of Controller Processor KC Controller Processor address [ENTER] Kill Controller:
Nonvolatile memory—Eliminate areas of

nonvolatile memory that are reserved for FB (node#) [ENTER] Free Bubble
non--existent blocks
Nonvolatile memory—Initialize
IC (ControlFile address) [ENTER] Init CF Nvmem Config:
configuration information
Wipe bubble memory WB (ControlFile address) [ENTER] Wipe Bubble:
Diagnostics (See SV:9)
Stop memory dump before it finishes KMD Kill Memory Dump
Captures RAM memory of a

MD (node#), (filename) [ENTER] Memory Dump:
node in a file
Operator Log
Operator Log—print P [sp] OL [ENTER] Pr Operator Log

CC: 5-1-17
Reports
RP (volume , filename) [ENTER] or

Print a report Reprt Prt:
RP (node#, filename) [ENTER]
P [sp] R [volume , filename] [ENTER] or

Print a report Pr Report:
P [sp] R [node#, filename] [ENTER]
Reports—Disable DR [ENTER] Disable Reports
Reports—Enable ER [ENTER] Enable Reports
Screen print
Character print of screen SC (node#) [ENTER] Screen Char Print:
Graphic print of screen SG (node#) [ENTER] Screen Graph Print:
Configured mode print of screen SP (node#) [ENTER] Screen Print:
SRU & SQC
SQC control charts—Disable DSQ (node#) [ENTER] Disable SQC:
SQC control charts—Enable ESQ (node#) [ENTER] Enable SQC:
Wipe SQC bubble memory SQW (node#) [ENTER] SQC Wipe:
Transmitter Log
Trans Maintenance Log—Disable DML (node#) [ENTER] Disable Maint Log:
Trans Maintenance Log—Enable EML (node#) [ENTER] Enable Maint Log:

CC: 5-1-18
Trending
Trending—Disable DT (node#) [ENTER] Disable Trending
Trending—Enable ET (node#) [ENTER] Enable Trending

CC: 5-2-1
Section 2:
Hints for Using Commands
This section discusses some tips for using commands.

- You can use the [NEXT OPTION] and [LAST OPTION] keys to
scroll through the commands in (mostly) alphabetical order.
- You can type a letter and then use the [NEXT OPTION] and
[LAST OPTION] keys to scroll through commands.
For example, if you know that a command starts with the letter C,
but you aren’t sure of the exact combination of letters, you can type
[C] and [NEXT OPTION] to scroll through the commands from C
onward.
RS3: Commands Hints for Using Commands

RS3t
Chapter 6:
Alarm Management
Section 1: Managing the Number of Alarm Messages on the PeerWay . . 6-1-1

Configuring Which Nodes Are Sent Alarms from a ControlFile,
Console, or SRU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1-2
Using CAB to Reduce Message Load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1-4
Inhibiting Alarms from Generating on the PeerWay . . . . . . . . . . . . . . . . . . . . . . . . 6-1-7
Using ControlBlock Logic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1-7
Using the ControlFile Status Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1-7
Effects of Inhibiting Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1-7
Section 2: How Alarms Get Stored in Console RAM . . . . . . . . . . . . . . . . . . . 6-2-1
Section 3: Separating and Sorting Alarms at a Console . . . . . . . . . . . . . . . . 6-3-1

Alarm Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3-2
Alarm Areas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3-3
Disabling and Enabling an Alarm Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3-5
Disabling an Alarm Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3-5
Enabling an Alarm Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3-5
Alarm Suppression . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3-6
Suppressing an Alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3-7
Unsuppressing an Alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3-7
Configuring Alarm List and Event List Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3-8
The Alarm List Configuration Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3-8
RS3 Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3-11
User-defined Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3-12
Configuring the Event List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3-13
Section 4: Alarm History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-4-1

Configuring Log Display Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-4-2
Displaying Information from the Alarm Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-4-6
Disabling and Enabling the Alarm Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-4-9
RS3: Alarm Management Contents

CC: ii
Section 5: Configuration and Display Topics . . . . . . . . . . . . . . . . . . . . . . . . . . 6-5-1

Alarm Configuration Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-5-2
Alarm Configuration Screen—Automatic Alarm Deletion . . . . . . . . . . . . . . . . . 6-5-7
Alarm Regeneration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-5-10
Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-5-10
When Do Alarms Regenerate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-5-10
How Consoles Regenerate Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-5-10
Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-5-10
Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-5-10
Alarm Priority . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-5-11
Alarm Type Priority . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-5-11
Alarm Priority Numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-5-11
Alarm Display Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-5-12
Alarm Banner Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-5-12
Alarm Summary Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-5-12
Determining the Alarm Display Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-5-13
Section 6: Alarm Animation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-6-1

Tags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-6-3
Tags on Trend Group Displays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-6-14
Block Variable Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-6-15
Plant Units and Area Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-6-26
Graphic Alarm Objects and Icon Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-6-37
Alarm Message Source Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-6-48
Section 7: Hints for Alarm Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-7-1

Configuration Tips . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-7-1

CC: iii
List of Figures
Figure Page
6.1.1 Configure Alarm Broadcast Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1-3
6.1.2 Comparison of Message Traffic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1-4
6.1.3 Effect of Partitioning into Logical Sections . . . . . . . . . . . . . . . . . . . . . . . . 6-1-5
6.3.1 Area Name Configuration Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3-3
6.3.2 Alarm List Configuration Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3-9
6.3.3 Event List Configuration Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3-14
6.4.1 Log Display Configuration Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-4-2
6.4.2 Examples of Criteria Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-4-5
6.4.3 Using the Alarm Log Display Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-4-7
6.5.1 Alarm Configuration Screen—Page 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-5-2
6.5.2 Automatic Alarm Deletion Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-5-7
6.5.3 Example of an Alarm Banner . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-5-12
6.5.4 Example of an Alarm Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-5-12
6.6.1 Example Portion of an Animation Table . . . . . . . . . . . . . . . . . . . . . . . . . . 6-6-2

CC: iv
List of Tables
Table Page
6.1.1 Comparison of Alarm Inhibiting Logic Step Functions . . . . . . . . . . . . . . 6-1-7
6.2.1 How Node Ownership and Plant Unit Ownership Work
Together to Determine Alarm Storage . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2-1
6.3.1 Alarm Type Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3-2
6.3.2 Area Name Configuration Screen Fields . . . . . . . . . . . . . . . . . . . . . . . . . 6-3-4
6.3.3 Alarm List Configuration Screen Fields . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3-10
6.3.4 Reserved Event Numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3-11
6.3.5 Event List Configuration Screen Fields . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3-15
6.4.1 Log Display Configuration Screen Fields . . . . . . . . . . . . . . . . . . . . . . . . 6-4-3
6.4.2 Alarm Log Display Screen Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-4-8
6.5.1 Alarm Configuration Screen Fields ............................. 6-5-3
6.5.2 Alarm Configuration Screen----Automatic Alarm Deletion Fields . . . . . 6-5-8
6.6.1 Tag Animation
Hardware Alarms Have More Priority
thanÞCrit Unacked, Cleared AlarmÞISA . . . . . . . . . . . . . . . . . . . . . . . . 6-6-4
6.6.2 Tag Animation
thanÞAdv Unacked, Cleared AlarmÞISA . . . . . . . . . . . . . . . . . . . . . . . . 6-6-5
6.6.3 Tag Animation
thanÞBatch Unacked, Cleared AlarmÞISA . . . . . . . . . . . . . . . . . . . . . . 6-6-6
6.6.4 Tag Animation
thanÞSystem Unacked, Cleared AlarmÞISA . . . . . . . . . . . . . . . . . . . . 6-6-7
6.6.5 Tag Animation
thanÞDisk or None Unacked, Cleared AlarmÞISA . . . . . . . . . . . . . . . . 6-6-8
6.6.6 Tag Animation
thanÞCrit Unacked, Cleared AlarmÞRMT or Color . . . . . . . . . . . . . . . 6-6-9
6.6.7 Tag Animation
thanÞAdv Unacked, Cleared AlarmÞRMT or Color . . . . . . . . . . . . . . . 6-6-10
6.6.8 Tag Animation
thanÞBatch Unacked, Cleared AlarmÞRMT or Color . . . . . . . . . . . . . 6-6-11
6.6.9 Tag Animation
thanÞSystem Unacked, Cleared AlarmÞRMT or Color . . . . . . . . . . . . 6-6-12
6.6.10 Tag Animation
thanÞDisk or None Unacked, Cleared AlarmÞRMT or Color . . . . . . . 6-6-13

CC: v
6.6.11 Block Variable Value and Trend Group Display Tag Animation
Hardware Alarms Have More Priority thanÞCrit
Unacked, Cleared AlarmÞISA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-6-16
Hardware Alarms Have More Priority thanÞAdv
Hardware Alarms Have More Priority thanÞBatch
Hardware Alarms Have More Priority thanÞSystem
Hardware Alarms Have More Priority thanÞDisk or None
Unacked, Cleared AlarmÞRMT or Color . . . . . . . . . . . . . . . . . . . . . . . . . 6-6-21
6.6.21 Plant Unit and Area Name Animation

CC: vi

6.6.31 Alarm and Icon Object Animation
6.6.41 Alarm Message Source Description Animation . . . . . . . . . . . . . . . . . . . . 6-6-48

CC: 6-1-1
Section 1:
Managing the Number of Alarm Messages on the
PeerWay
Normally, an alarm condition generates an alarm message on the

PeerWay for each node in the system. You can reduce the number of
alarm messages on the PeerWay in the following ways:
D If you have multiple PeerWays connected, or if the performance
of the PeerWay has declined, you may want to reduce the
number of nodes that get ControlFile, Console and SRU alarm
messages. You can do this with the Configure Alarm Broadcast
screens.
D If you do not want alarms from a ControlBlock to generate under
certain conditions, you can inhibit alarms from generating with
ControlBlock logic.
D If you do not want alarms from a Controller Processor to
generate under certain conditions, you can automatically inhibit
alarms from generating with ControlBlock logic or manually inhibit
alarms from generating with the ControlFile Status screen.
RS3: Alarm Management Managing the Number of Alarm Messages on the PeerWay
CC: 6-1-2
Configuring Which Nodes Are Sent Alarms from a

ControlFile, Console, or SRU
If you have multiple PeerWays connected together, or if PeerWay

performance has declined, you may want to limit the amount of
PeerWay traffic by using the Configure Alarm Broadcast feature.
Configure Alarm Broadcast (CAB) is used to reduce unnecessary alarm
messages and alarm acknowledge traffic on the PeerWay.
Normally, if an alarm occurs or is acknowledged in a ControlFile,

Console, or SRU, an alarm message is sent to every existing node on
all connected PeerWays. However, you can use the Configure Alarm
Broadcast screens to specify which nodes are sent alarms from a
specific ControlFile, Console, or SRU (see Figure 6.1.1). Each
ControlFile, Console, and SRU has its own alarm broadcast
configuration.
Configure Alarm Broadcast screens are used to filter the sending of

alarms, while the Plant Status and Plant Unit screens are used for
receiving them. The CAB for Consoles and SRUs is saved in the
Alarm/Event configuration portion of the Console or SRU Configuration
file. The CAB for one or more ControlFiles can be saved to a Plant
Config file (type CAB). To save and restore the Alarm Broadcast
Configurations, see the Disk and Tape Functions Manual.
NOTE: When you configure which nodes are sent alarms with CAB,
make sure that you select the node that you are configuring. Otherwise,
you will not receive alarm messages generated by that node.
CC: 6-1-3

D C A B (node #) [ENTER] D [PAGE AHEAD] and [PAGE BACK]
at the command line to see other ControlFile node
numbers.
Each ControlFile, Console,
- To select or deselect a single node:
Nodes that are sent and SRU must have its own
alarms are backlighted. CAB screen configured. D Cursor to the node number and press
[ENTER].
Node® 116 Configure Alarm Broadcast 23-Jul-92 11:47:12
1 17 33 49 65 81 97 113 129 145 161 177 193 209 225 241

2 18 34 50 66 82 98 114 130 146 162 178 194 210 226 242
3 19 35 51 67 83 99 115 131 147 163 179 195 211 227 243
4 20 36 52 68 84 100 116 132 148 164 180 196 212 228 244
5 21 37 53 69 85 101 117 133 149 165 181 197 213 229 245
6 22 38 54 70 86 102 118 134 150 166 182 198 214 230 246
7 23 39 55 71 87 103 119 135 151 167 183 199 215 231 247
8 24 40 56 72 88 104 120 136 152 168 184 200 216 232 248
9 25 41 57 73 89 105 121 137 153 169 185 201 217 233 249
10 26 42 58 74 90 106 122 138 154 170 186 202 218 234 250
11 27 43 59 75 91 107 123 139 155 171 187 203 219 235 251
12 28 44 60 76 92 108 124 140 156 172 188 204 220 236 252
13 29 45 61 77 93 109 125 141 157 173 189 205 221 237 253
14 30 46 62 78 94 110 126 142 158 174 190 206 222 238 254
15 31 47 63 79 95 111 127 143 159 175 191 207 223 239 255
16 32 48 64 80 96 112 128 144 160 176 192 208 224 240 256
Set range ®3,6 Clear range ® Local Pway Initialize

CONFIG 4
- To deselect a range of nodes: Uninitialize indicates that alarms

D Cursor to the ”Clear range” field, type a are sent to all active nodes.
range of numbers separated by a Initialize indicates that alarms are
comma (for example “3,6”), then press only sent to the selected nodes.
[ENTER].
- This field is not used on the CAB
To select a range of nodes: screen for Consoles and SRUs.
D Cursor to the ”Set range” field, type a range - To select all the nodes on the local
of numbers separated by a comma (for PeerWay
example “3,6”), then press [ENTER].
D Cursor to the “Local Pway” field and press
[ENTER].
Figure 6.1.1. Configure Alarm Broadcast Screen
CC: 6-1-4
Using CAB to Reduce Message Load
Continuous alarms or bursts of alarms (which often peak at start--up or

shutdown) can be caused by too many unnecessary, redundant alarms
and alarm acknowledge messages traveling between too many nodes.
Redundant alarms and alarm acknowledge messages can substantially
slow down responses and obscure more significant events, especially in
large systems.
Figure 6.1.2 shows an example of the decrease in message traffic if one

destination is removed from the coordinator processor using the CAB
screen, and only one console is allowed to acknowledge the alarms.
Coordinator Coordinator Coordinator Coordinator

Processor Processor Processor Processor
Console 1 Console 3
Console 1 Console 3 (Acking) (Non--acking)
Console 2
Console 2
3 consoles acknowledge alarm 1 console acknowledges alarm

12 message sets created 5 message sets created
Figure 6.1.2. Comparison of Message Traffic
As a configuror, you must reduce the number of unnecessary messages

in order to optimize the performance of your system. To minimize
waste, you are strongly encouraged to use these techniques:
D Reduce the amount of alarm message traffic that travels to other
Peerways across the HIA.
D In large systems, use one console to receive alarms from other
Peerways, but not to receive alarm message traffic from its own
Peerway. Use other consoles on the Peerway to handle this
console’s Peerway alarm message traffic.
CC: 6-1-5
D As your plant grows, divide it into logical sections corresponding

to one to three ControlFiles. Have one section report to one to
three consoles, only one of which acknowledges alarms, to avoid
duplicate acknowledge messages for the same alarm. Examples
of logical sections could be the power area of a plant, a storage
area, or an area where a portion of a process takes place.
Use the CAB screen to ensure that alarm message traffic is limited only
to nodes in that logical section. The ideal scheme would have minimal
message traffic across section boundaries. Figure 6.1.3 shows an
example of message traffic before and after partitioning using the CAB
screen.
CP CP CP CP
Console Console Console Console
Each alarm at a CP creates message sets = 4 to 7 ´ number of alarms

Each alarm ack at a console creates message sets = 3 ´ number of console acks
CP CP CP CP
block
links
North South
Section Section
Console Console Console Console
Each alarm at a CP creates message sets = 2 to 3 ´ number of alarms

Each alarm ack at a console creates message sets = 1 ´ number of console acks
Figure 6.1.3. Effect of Partitioning into Logical Sections
CC: 6-1-6
The CAB screen allows you to reduce the number of redundant

messages by allowing you to limit the number of nodes that receive
alarms and alarm acknowledge messages from your console. The CAB
screen affects alarms, events, and alarm acknowledge messages
before messages are sent on the Peerway, substantially reducing
Peerway, node, and HIA load.
The Plant Status and Plant Unit Configuration screens are not as
effective as using the CAB screen to limit message traffic, because they
only filter out unwanted messages after they have already been sent.
This means that the unwanted messages are sent and received, using
up Peerway resources, and then are discarded after the resources have
already been used.
You should not configure HIAs or coordinator processors as

destinations from the CAB screen, because these just discard received
alarms and alarm acknowledge messages. (However, selected
coordinator processors running Batch should be sent alarms for on
traps.) You should only configure a few consoles or logging nodes in
the same Peerway as console and SRU CAB destinations.
CC: 6-1-7
Inhibiting Alarms from Generating on the PeerWay
You can inhibit alarms from a ControlBlock and from a Controller

Processor.
Using ControlBlock Logic
You can use ControlBlock logic to inhibit ControlBlock alarms and

Controller Processor alarms from generating and being sent on the
PeerWay. Table 6.1.1 compares the inhibit logic step functions. For
more information about these logic steps, see CB: 6.
Table 6.1.1. Comparison of Alarm Inhibiting Logic Step Functions
This logic step

Affects: And it lasts:
function:
Only as long as the function is executed.
inhibit* ControlBlock alarms That is, alarms are inhibited only for
those evaluation cycles in which the
inhibit function is executed.
Until the opposite function is executed.

Alarms that originate in a Controller That is, once a function is executed, that
inha and enba
Processor condition remains in effect until the
opposite condition is executed.
* Does not work on MPCI consoles.
Using the ControlFile Status Screen
In addition, you can use the “Alarm Inhib” field on the ControlFile Status
screen to inhibit Controller Processor alarms from generating and being
sent on the PeerWay.
Effects of Inhibiting Alarms
When a ControlBlock or Controller Processor is inhibited, the following

tasks occur:
D The ControlBlock or Controller Processor sends a clear message
on the PeerWay for each uncleared alarm.
D All alarms from the ControlBlock or Controller Processor are
inhibited from generating and are not sent on the PeerWay.
CC: 6-2-1
Section 2:
How Alarms Get Stored in Console RAM
A console receives alarm messages from the PeerWay. The console

stores some of these alarms in RAM on the console OI Processor card
and discards the rest. The console determines whether or not to store
an alarm based on the configured node ownership and plant unit
ownership at the console.
Table 6.2.1 describes how node ownership and plant unit ownership
work together to determine alarm storage. For more information on
node ownership and plant unit ownership, see 1-1-23.
The “Total Entries” field on the Alarm List Configuration screen displays
the number of alarm and event messages that can be stored in console
RAM. For more information on the Alarm List Configuration screen, see
Section 3.
Table 6.2.1. How Node Ownership and Plant Unit Ownership Work Together to
Determine Alarm Storage
If: Then: Only if the console:
a block or batch task has a the console stores alarms from

owns the plant unit number.
non--zero plant unit number, the block or task,
a block or batch task has a plant the console stores alarms from
unit number of zero, the block or task,
the source is not a block or batch the console stores alarms from
task, the source,
RS3: Alarm Management How Alarms Get Stored in Console RAM

CC: 6-3-1
Section 3:
Separating and Sorting Alarms at a Console
Alarms that are stored in console RAM are separated and sorted in the
following ways. The following sorting methods are described in this
section:
D Alarms are automatically sorted by alarm type into alarm type
lists.
D Alarms are also sorted by configurable alarm area into alarm
area lists. Alarm areas can be disabled.
D Alarms can be separated from the alarm type lists and alarm
area lists (suppressed).
In addition, this section describes how to configure alarm list and event
list properties.
RS3: Alarm Management Separating and Sorting Alarms at a Console

CC: 6-3-2
Alarm Types
Each alarm belongs to one and only one alarm type. All alarms stored
at the console are automatically separated by alarm type into alarm type
lists. The alarm types and alarm type lists are listed in Table 6.3.1.
The alarm type lists include all alarms stored at the console, except:
D Suppressed alarms
D Alarms from disabled alarm areas
Table 6.3.1. Alarm Type Lists
Alarm Type Alarm Lists
Active Advisory Process Alarm List

Cleared Advisory Process Alarm List
Advisory Process Alarms
Active Process Alarm List*
Cleared Process Alarm List*
Active Batch Alarm List

Batch Alarms
Cleared Batch Alarm List
Active Critical Process Alarm List

Cleared Critical Process Alarm List
Critical Process Alarms
Active Process Alarm List*
Cleared Process Alarm List*
Disk Event Messages Disk Event List
Active Hardware Alarm List

Hardware Alarms
Cleared Hardware Alarm List
Active System Status Alarm List

System Status Messages
Cleared System Status Alarm List
* The Process Alarm lists are a combination of the Advisory Process and Critical
Process alarm lists.

CC: 6-3-3
Alarm Areas
You can configure alarm areas. Alarm areas are helpful in grouping
alarms from certain areas of the plant. Each alarm area is associated
with one or more plant units. Alarms from the specified plant units are
sorted into alarm area lists.
Plant units can belong to more than one alarm area. As a result, alarms
can reside in more than one alarm area list.
Alarm areas are configured on the Area Name Configuration screen
(see Figure 6.3.1). Table 6.3.2 describes the fields on the screen.

D A N C [ENTER] at the D [PAGE AHEAD] and [PAGE BACK] and scroll
command line with trackball to call up other alarm areas
D [EXCH] on Unit Ranges field to show
Descriptor field and number of alarms
D [SELECT] on Area Name entry to see area
alarm list
D [SELECT] on Graphic entry to see process
graphic
D [SELECT] on Unit Ranges field heading to
see Plant Unit Configuration
AREA NAME CONFIGURATION 25-Jul-92 12:07:37
Area Name: Status: Graphic: +------------Unit Ranges-----------+

>
1ÞBoiler >Enable ÞBoiler1 Þ1-4,6,9-12 |
2ÞArea 2 >Enable Þ Þ1-10 |
3Þ > Þ Þ |
4Þ > Þ Þ |
5Þ > Þ Þ |
6Þ > Þ Þ |
7Þ > Þ Þ |
8Þ > Þ Þ |
9Þ > Þ Þ |
FULL CONFIG 3
Figure 6.3.1. Area Name Configuration Screen

CC: 6-3-4
Table 6.3.2. Area Name Configuration Screen Fields
Field Description
> Enter the number of the next area name that you want displayed.
Indicates whether there are more units to be displayed. | indicates all the
units have been displayed. > indicates there are more units to the right. <
|
indicates there are more units to the left. <> indicates there are more units in
both directions.
Specifies the alarm area name. The area name can contain up to 12
characters. Each console can contain up to 99 area names.
Area names are used throughout the PeerWays. When you enter an area
name, the console searches the PeerWays to see if the area name has been
defined on another console. If it has, the console brings the already--defined
“Graphic” and “Unit Ranges” field entries to your console.
Area Name CAUTION: The information on the Area Name Configuration screen is part
of the configuration of this console only. As a result, if you make changes to
the “Graphic” or “Unit Ranges” fields of an area name, the changes are only
made to the local console configuration. The changes are not propagated to
other consoles. To make those changes at other consoles, you must go to
each console that contains that area name in node number order, delete
the area name, and reenter it.
Specifies a descriptor for the alarm area. The descriptor can contain up to
35 characters. The far right of the display shows the number of alarms for
Descriptor the area.
Pressing [EXCH] switches between displaying the “Unit Ranges” and
“Descriptor” fields for the configuror.
Specifies a process graphic on the local hard disk that is associated with an
area. The operator can cursor to the graphic name and press [SELECT] to
Graphic call up the graphic.
You can also call up the graphic with the command
A N G (area name) [ENTER].
Specifies the status of the area (Enabled or Disabled).

When you enter the area name, the area is enabled. The area must be
Status enabled for the console to display area alarms. For information about
disabling and enabling alarm areas, see “Disabling and Enabling an Alarm
Area” on page 6-3-5.
Specifies the plant units for the alarm area. You can enter single plant units
and ranges of plant units.
If the console does not own the plant unit, the plant unit appears backlighted
in the advisory alarm color.
Unit Ranges
If the displayed list of plant units is longer than the available space, you can
press [NEXT OPTION] on this field to see the rest of the plant units.
Pressing [EXCH] switches between displaying the “Unit Ranges” and
“Descriptor” fields for the configuror.

CC: 6-3-5
Disabling and Enabling an Alarm Area
If you do not want to see alarms from certain areas of the plant, you can
disable a console alarm area. While the area is disabled, the following
conditions exist:
D The alarms from that area are not shown in the alarm type lists.
(If a plant unit is listed in more than one area on a console, then
all areas with that plant unit must be disabled for alarms from that
plant unit not to be shown in the alarm type lists.)
D You cannot use [PAGE AHEAD] and [PAGE BACK] to access the
alarm lists for that area.
D If you call up the alarm area lists, a message states “Disabled
Area List”.
The “Key Classes for area status” field on the Alarm Configuration
screen determines the key access level required to disable or enable
alarm areas. For more information on the Alarm Configuration screen,
see page CC:6-5-2.
Disabling an Alarm Area
NOTE: If you want to disable an area, the same area must be enabled
in at least one other console.
- To disable an alarm area from the Area Name Configuration
screen:
1. Call up the Area Name Configuration screen
(press A N C [ENTER] from the command line).
2. Cursor to the “Status” field for the desired area. Press
[NEXT OPTION] until “Disabled” appears. Press [ENTER].
- To disable an alarm area from the command line:
D Press A D : (area name) [ENTER]
Enabling an Alarm Area
- To enable an alarm area from the Area Name Configuration

screen:
1. Call up the Area Name Configuration screen
(press A N C [ENTER] from the command line).
2. Cursor to the “Status” field for the desired area. Press
[NEXT OPTION] until “Enabled” appears. Press [ENTER].
- To enable an alarm area from the command line:
D Press A E : (area name) [ENTER].

CC: 6-3-6
Alarm Suppression
You can suppress active block alarms at a console. You suppress

alarms when there are a lot of alarms coming in. Suppression is
different from disabling. One reason you might disable alarms is if you
don’t want to know about them because they are in a part of the plant
that is not your concern.
Suppressed alarms characteristics

D When you suppress an active alarm from a block, all active
alarms from that block that are of the specified alarm types are
suppressed.
D Suppressed alarms do not appear on alarm type lists or alarm
area lists.
D Suppressed alarms appear in active and cleared suppressed
alarm lists.
D Suppressed alarms appear in a configured color.
D If an active suppressed alarm clears, the alarm goes into the
cleared suppressed alarm list.
D If the console regenerates alarms, the suppressed alarm lists are
not rebuilt. Instead, regenerated alarms that were in the
suppressed alarm lists appear in the alarm type lists.
Unsuppressed alarm characteristics

D When you unsuppress an alarm, all active suppressed alarms
from that block are moved back to the alarm type lists. All
cleared alarms from that block are deleted.
Which alarm types can be suppressed

You configure which alarm types can be suppressed with the
“Suppressed Type” field on the Alarm Configuration screen. When you
suppress an active alarm from a block, all active alarms from that block
that are of the specified alarm types are suppressed.
For example, if you configure “Suppressed TypeÞHard,Adv,System”

and suppress an alarm, then all active hardware, advisory, and system
status alarms from that block are suppressed. For more information on
the Alarm Configuration screen, see page CC:6-5-2.
Which key access level can suppress alarms

You determine the key access level required to suppress alarms with
the “Key Class for suppress alarms” field on the Alarm Configuration
screen.
For more information on the Alarm Configuration screen, see

page CC:6-5-2.

CC: 6-3-7
Suppressing an Alarm
- To suppress an active alarm:

1. Call up an alarm list that contains the alarm that you want to
suppress.
2. Cursor to the alarm. Press S.
Unsuppressing an Alarm
- To unsuppress an alarm:
1. Call up an alarm list that contains the alarm that you want to
unsuppress.
2. Cursor to the alarm. Press E.

CC: 6-3-8
Configuring Alarm List and Event List Properties
You can configure the printing properties and size of some alarm lists
and event lists.
Size of alarm lists and event lists
Each console has a maximum number of alarms and events that can be
stored. The maximum number is displayed in the “Total Entries” field on
the Alarm List Configuration screen (see Figure 6.3.2).
You configure the size of some alarm lists and event lists. The sum of
the sizes of all lists must not exceed the “Total Entries” value. You must
keep track of the sum of the sizes yourself.
Batch-- generated alarms and events
Each batch--generated alarm uses 2 entries. For example, if the

Process list type has a size of 200, it can hold 100 batch--generated
process alarm messages.
Console restart
All alarm and event lists are cleared if the console is restarted.
The Alarm List Configuration Screen
The Alarm List Configuration screen is used to configure size and

printing properties of alarm type lists. Figure 6.3.2 shows an example of
an Alarm List Configuration screen. Table 6.3.3 describes the fields on
the Alarm List Configuration screen.

CC: 6-3-9

D A L C [ENTER] at the D [PAGE AHEAD] to see Event List
command line Configuration
D [PAGE BACK] to see Automatic Alarm
Deletion
- To change an entry:
1. Cursor to the field, type in the new entry, and press [ENTER].
New entries are displayed in a contrasting color.
2. The changes do not take effect until you initialize all the lists.
When you have made all the changes to the screen that you
want, initialize the list by cursoring to the “Initialize Lists” field
and pressing [ENTER].
NOTE: This will clear all alarm and event lists.
ALARM LIST CONFIGURATION 01-Aug-92 11:44:24

+---Print---+
List Type Size Trigger Node
¯
Hardware Þ200 Þ50 Þ32
Process Þ200 Þ100 Þ20 External Alarm ÞNC
Batch Þ200 Þ50 Þ20 Backup Printer Node Þ20
System Status Þ100 Þ50 Þ32 Restore Primary Printer Nodes
Disk Events Þ50 Þ25 Þ32 Alarm PrintÞNormal
Operator Log Þ100 Þ50 Þ32 Last Initialize Time
28-Oct-88 07:11:38
Suppressed 2860 ** **
Total Entries (All Lists, including Events) 3850

ÞInitialize Lists (press ENTER)
WARNING: This will Clear ALL Alarm and Event Lists
FULL CONFIG 1
The difference between the “Total Entries” size

Shows the maximum number of
and the sum of the configured alarm type list
alarms and events that can be
and event list sizes is automatically reserved for
stored in console RAM.
the suppressed alarm lists.
Figure 6.3.2. Alarm List Configuration Screen

CC: 6-3-10
Table 6.3.3. Alarm List Configuration Screen Fields
Field Description
Determines how the alarm list is printed.

Alarm Print Normal = Prints an alarm list with a heading on a new page (form feed).
Single Line = Prints an alarm list without a heading and without a form feed.
Specifies a backup printer node for printing lists. This field must specify the
node of a printer.
Backup Printer Node
This field is used as a backup for printer nodes specified on the Alarm List
Configuration, Event List Configuration, and Console Configuration screens.
Specifies the type of console contacts used if the console is connected to an

external annunciator. Contacts are actuated when a process or hardware alarm
occurs and are deactuated by pressing the [ALARM ACK] button.
External Alarm NC = normally closed (open on alarm)
NO = normally open (closed on alarm)
Off = non--functioning
Initializes (clears) all alarm and event lists. To initialize lists, cursor to the
Initialize Lists “Initialize Lists” field and press [ENTER]. New entries to the Alarm List
Configuration screen are not implemented until the list is initialized.
List Type Displays the list types.
Node Specifies the console node where the list is printed.
Restores the primary printer if it is available. This field is used as a backup for
printer nodes specified on the Alarm List Configuration, Event List Configuration,
Restore Primary and Console Configuration screens. If a printer node entry on one of these fields
Printer Nodes is backlighted, there has been a printer problem. You can attempt to restore the
primary printer by cursoring to the “Restore Primary Printer Node” field and
pressing [ENTER].
Specifies the number of entries that are saved in a list. Once the “Size” value is
Size reached, each new entry added to the list causes the oldest entry to be taken off
the list.
Specifies the number of entries of a list that trigger the printing of the list. For
example, if “TriggerÞ24” is configured, the list is printed after 24 entries have
occurred. To print all alarms, the “Trigger” value must be less than or equal to
Trigger the “Size” value.
If a list type has active and cleared lists, both are printed when the trigger is
reached.

CC: 6-3-11
RS3 Events
RS3 offers 255 event types that perform one of the following tasks:
D Send a message to one of ten user-defined event lists.
D Initiate the printing of a user-defined or system-defined event list.
Event types are identified by a number between 1 and 255:

D Event types 1 to 240 are user--definable.
D Event types 241 to 255 are reserved to initiate the printing of a
list as explained in Table 6.3.4.
Table 6.3.4. Reserved Event Numbers
Event Event
Initiates printing of... Initiates printing of...
Number Number
241 Hardware Alarm Lists 249 Event List 5
242 Process Alarm Lists 250 Event List 6
243 System Status List 251 Event List 7
244 Disk Event List 252 Event List 8
245 Event List 1 253 Event List 9
246 Event List 2 254 Event List 10
247 Event List 3 255 Operator Change Log
248 Event List 4

CC: 6-3-12
User-defined Events
User-defined events can be generated from a ControlBlock logic step,

from a batch script, or from a host application.
D When you generate an event from a ControlBlock logic step, you
use the Discrete Diagram screen to specify the following:
— The event type (a number between 1 and 240)
— The message type (Evt)
— The ControlBlock variable that contains the value that you
wanted printed in the event list entry (continuous inputs A
through O, discrete inputs a through p, or discrete outputs @a
through @o)
— The logic step action that you want to generate the event
(rise, one, fall, off, or change)
For more information about configuring events, see CB: 6.
D When you generate an event from a batch script, you use a
Rosemount Basic Language instruction to specify the following:
— The event type (a number between 1 and 240)
— The priority of the message (a number between 0 and 15 with
0 indicating a high priority and 15 a low priority)
— The message text (up to 21 characters)
For more information about configuring events, see RB.
D When you generate an event from a host application, you use the
ALM_generateEvent function. For more information about
configuring events, see Rosemount Network Interface (RNI)
Programmer’s Manual (RP: 4).

CC: 6-3-13
Configuring the Event List
The Event List Configuration screen allows you to perform the following
tasks from an RS3 console:
D Assign event types 1 to 240 to one, and only one, of the 10 event
lists. One approach is to configure List 1 with events 1 to 24, List
2 with events 25 to 48, etc.
D For each of the 10 event lists, you also define the following:
— The number of entries to save; after the list reaches that size,
the oldest entry is always deleted when a new entry comes in.
— The number of entries to trigger a printout of the list; each
subsequent printing lists only entries that occurred since the
last print-out.
— The console node where the list is to be printed.
The Event List Configuration screen is shown in Figure 6.3.3. The

screen fields are described in Table 6.3.5.

CC: 6-3-14

D E L C [ENTER] at the D [PAGE AHEAD] to see Alarm Configuration
command line D [PAGE BACK] to see Alarm List Configuration
- To change an entry:
1. Cursor to the field, type in the new entry, and press [ENTER].
New entries are displayed in a contrasting color.
2. The changes do not take effect until you initialize all the lists.
When you have made all the changes to the screen that you
want, initialize the list by cursoring to the “Initialize Lists” field
and pressing [ENTER].
NOTE: This will clear all alarm and event lists.
EVENT LIST CONFIGURATION 21-Jul-92 08:00:58

+---Print---+
Event List Size Trigger Node +------------Event Ranges------------+
1 Þ20 Þ18 Þ10 Þ1,7 Þ9 Þ11,21 Þ Þ
2 Þ100 Þ90 Þ28 Þ101,195 Þ8 Þ37 Þ200,202 Þ0
3 Þ0 Þ0 Þ0 Þ0 Þ0 Þ0 Þ0 Þ0
4 Þ0 Þ0 Þ0 Þ0 Þ0 Þ0 Þ0 Þ0
5 Þ20 Þ18 Þ2 Þ45,50 Þ61 Þ84 Þ89,100 Þ38
6 Þ0 Þ0 Þ0 Þ0 Þ0 Þ0 Þ0 Þ0
7 Þ0 Þ0 Þ0 Þ0 Þ0 Þ0 Þ0 Þ0
8 Þ0 Þ0 Þ0 Þ0 Þ0 Þ0 Þ0 Þ0
9 Þ0 Þ0 Þ0 Þ0 Þ0 Þ0 Þ0 Þ0
10 Þ0 Þ0 Þ0 Þ0 Þ0 Þ0 Þ0 Þ0
Figure 6.3.3. Event List Configuration Screen

CC: 6-3-15
Table 6.3.5. Event List Configuration Screen Fields
Field Description
Event Lists Displays event list numbers 1 to 10.
Specifies the event types that are included in the event list. The event types
can be listed individually or as a group. Figure 6.3.3 shows some example
Event Ranges
entries. Up to five ranges of event types can be specified for each event list.
Events 1 to 240 can be specified in only one list.
Node Specifies the console node where the list is printed.
Specifies the number of entries that are saved in a list. Once the “Size” value
Size is reached, each new entry added to the list causes the oldest entry to be
taken off the list.
Specifies the number of entries of a list that trigger the printing of the list. For
example, if “TriggerÞ24” is configured, the list is printed after 24 entries have
Trigger
occurred. To print all events, the “Trigger” value must be less than or equal to
the “Size” value.

CC: 6-4-1
Section 4:
Alarm History
Alarm history is provided with the alarm log. The alarm log stores alarm
messages in a file on the console disk. You configure how the alarm log
information is sorted and displayed at the console.
This section describes:

D Configuring log display configurations
D Displaying information from the alarm log
D Disabling and enabling the alarm log
RS3: Alarm Management Alarm History

CC: 6-4-2
Configuring Log Display Configurations
You configure log display configurations that specify how the alarm log
information is sorted and displayed on the Alarm Log Display screen.
Log display configurations are part of the console configuration file.
Up to 30 log display configurations can be configured at a console.
You configure the log display configurations on the Log Display

Configuration screen (see Figure 6.4.1). The fields on the screen are
described in Table 6.4.1.

D L D C [ENTER] D [PAGE AHEAD] and [PAGE BACK]
at the command line to see other configurations
D [SELECT] on CNFG from Alarm D [SELECT] on LOG to see Alarm
Log Display Log Display
LOG DISPLAY CONFIGURATION 25-Jul-92 12:07:37

LOG Logging Criteria >log1 Configuration File :console18
HELP: unit area blk pri type state node ctime
SORT:
Sort Crit>pri, blk
Direction>Ascending SORT Status >ON
FIND:
Find Crit>unit=1-4
| >
| >
FILTER
Filt Crit>
| >
| >
FULL CONFIG 1
Figure 6.4.1. Log Display Configuration Screen

CC: 6-4-3
Table 6.4.1. Log Display Configuration Screen Fields
Screen Location Description

LOG = Cursor to this word and press [SELECT] to see the Alarm Log
Display.
Logging Criteria = Specifies the name of this log display configuration. You can
Top of screen
[PAGE AHEAD] and [PAGE BACK] to other log display
configurations. To delete a configuration, press [ENTER].
Configuration File = Displays the current console configuration file.
The parameters in this location are used in the Sort, Find, and Filter locations to
specify the logging criteria. They are listed on the screen as a helpful reminder. You
can cursor to each of these words and press [ENTER] for a short description of the
parameter.
The available parameters are:
area = area name
blk = block tag or address (sort by address only)
pri = priority (ControlBlock®0--15; I/O block®0--3)
type = alarm type (hard, proc, crit, adv, batch, sys, disk, el1--el10)
state = alarm state for Find and Filter (active, clear, unack, ack, suppr)
HELP
state = alarm order for “Sort Crit” field (yes, no)
yes specifies alarms in the order:
—active unacknowledged
—cleared unacknowledged
—active acknowledged
—cleared acknowledged
no specifies alarms in the order:
—cleared unacknowledged
—active unacknowledged
—cleared acknowledged
—active acknowledged
node = node number
ctime = cutoff time (format=dd--mm--yy/hh:mm:ss)
The fields in this location are used to specify the sort criteria.
Sort Crit = Specifies how to sort the alarm log display. As an example, the
configuration in Figure 6.4.1 will sort the log by alarm priority and
will sort each priority by block address. You cannot sort by area
or ctime.
SORT Direction = Specifies ascending or descending sort order.
SORT Status = Specifies the state of the sorter. OFF specifies that the alarms
cannot be sorted. ON specifies that the alarms can be sorted.
With ON specified, new alarms are not added while the Alarm Log
Display screen is displayed. To change the entry, cursor to the
field and press [ENTER].

CC: 6-4-4
Table 6.4.1. Log Display Configuration Screen Fields (continued)
Screen Location Description

Specifies which information is included in the alarm log display. If no parameters are
FIND configured, all alarms are included.
Specifies which information is excluded from the alarm log display. If no parameters
FILTER are configured, no alarms are excluded.

CC: 6-4-5
This configuration specifies that the alarm log

Find Crit>unit=1-4 displays all alarms from plant units 1 through 4.
This configuration specifies that the alarm log

Find Crit>blk=boiler1,boiler2 displays all alarms from blocks “boiler1” and
“boiler2”.
This configuration specifies that the log displays

Find Crit>blk=boiler1&type=crit all critical alarms from block boiler1.
The “&” represents a logical and operation.
Find Crit>blk=boiler1|unit=1-5
Both of these configurations specify the same

Find Crit>blk=boiler1 criteria—that the log displays all alarms from
block boiler1 and all alarms from plant units 1--5.
| >unit=1-5
The “|” represents a logical or operation.
| >
FIND:
Find Crit>unit=1-4
| >
This configuration specifies that the log displays
| > all alarms from plant units 1 through 4, but
FILTER: excludes cleared alarms.
Filt Crit>state=clear
| >
| >
Figure 6.4.2. Examples of Criteria Configurations

CC: 6-4-6
Displaying Information from the Alarm Log
The Alarm Log Display shows information from the alarm log file
according to the criteria defined in the log display configuration. You
can temporarily modify the log display configuration from the Alarm Log
Display screen.
The alarm log file resides in the Logs folder on the console and contains
up to 65,535 alarm messages. When the alarm log file is full, the
newest message overwrites the oldest message. The initial name of
the alarm log file is $$ALARM.
You configure which alarm types are stored in the alarm log with the
“Alarm Log Types” field on the Alarm Configuration screen. For more
information about the Alarm Configuration screen, see Section 5 in this
manual.
Figure 6.4.3 shows an example of an Alarm Log Display. Table 6.4.2

describes the fields on the screen.

CC: 6-4-7

D A L D (node) (log file name) D [PAGE AHEAD] and [PAGE BACK]
[ENTER] at the command line to see more alarms
D A L S (log display config) [ENTER] D [SELECT] on CNFG to see Log Display
at the command line Configuration
D [SELECT] on the LOG button from Log D [EXCH] to toggle between alarm
Display Configuration formats of occur and current.
[EXCH] above the top alarm to toggle
all alarms on the screen.
[EXCH] on one alarm to toggle that one
alarm.
If the log display configuration specifies

that the sort state is on, then the
display is not sorted until you cursor to
the “Sort” field and press [ENTER].
Specifies a log display This is true each time that you call up
configuration. The Alarm Log the Alarm Log Display screen.
Display shows alarms according
to the log display configuration. Alarm format that is currently
displayed—either occur or current.
ALARM LOG DISPLAY 25-Jul-92 12:07:37

File Name :vol12,console18 CNFG FIND FILT SORT LPRT PPRT
Cnfg’d Log: OCCUR Entry Count:7
Logging Criteria >log1 Top Entry #>1 Last Entry :7
Find Crit: node=16-20
Filt Crit:
Occur S Source Description Sum
05-Dec-91
18:46.11:685 >=19A 0-1 Controller Not Backed Up ?-OK
18:45.18:190 >=18 0-1 Alarm logging Enabled ?-OK
18:45.16:135 >=18 0-1 Trend Recording Disabled ?-OK
18:45.04:245 >=18 0-175 Node Restarted ?-OK
18:45.00:686 >=16 0-1 Node Restarted ?-OK
FULL CONFIG 5
Figure 6.4.3. Using the Alarm Log Display Screen

CC: 6-4-8
Table 6.4.2. Alarm Log Display Screen Fields
Field Meaning
Specifies the state of the alarm log. Appending alarms to the list is the normal state.
Inserting means a regeneration is happening and the alarms have to be inserted in
Cnfg’d Log
the correct time order if they are not already on that console. NA (not applicable) is
shown if the log is not enabled.
The text of the alarm messages which varies by alarm type and the method used to
Description
generate the alarm. For more information, see AL: 1.
Specifies the number of displayed entries. The highest value shown is 1600, even if
Entry Count
more than 1600 entries are displayed.
File Name Displays the name of the current console configuration file.
Filt Crit Displays the current filter criteria for the display.
Can be used to modify the log display configuration temporarily. The modifications
are only in effect as long as the Alarm Log Display appears. Press [SELECT] to call
FIND, FILT, SORT
up the corresponding configuration window. For information about display
configuration, see “Log Display Configuration” on page 6-4-2.
Find Crit Displays the current find criteria for the display.
Last Entry Displays the number of the last entry in the sublog.
Specifies the name of the log display configuration that determines which alarm log
Logging Criteria
information is displayed and how it is displayed.
Prints the alarm log according to the current display criteria. Press [SELECT] on this
LPRT
field to print. The alarms are printed in 132 column format.
PPRT Prints a page of the currently displayed screen. Press [SELECT] on this field to print.
The state of the block at occurrence time: D means the alarm belonged to a disabled
S area when it occurred. S means the alarm is from a suppressed block and does not
belong to a disabled area. * means the alarm is late and is not from a suppressed
(Occur mode) block or a disabled area. “ ” means the alarm is not from a suppressed block or a
disabled area or late.
The state of the block at clear time: D means the alarm belonged to a disabled area
S when it occurred. S means the alarm is from a suppressed block and does not
belong to a disabled area. * means the alarm is late and is not from a suppressed
(Current mode) block or a disabled area. “ ” means the alarm is not from a suppressed block or a
disabled area or late.
Source Tag of the block that the alarm came from.
A--The alarm is acknowledged but not cleared. ?--OK Alarm is cleared but not
Summ acknowledged. A--OK Alarm is acknowledged and cleared. ?-- The alarm is
unacknowledged and is not cleared.
Top Entry Specifies the number of the log entry that is shown at the top of the display.

CC: 6-4-9
Disabling and Enabling the Alarm Log
You can disable the alarm log. When the alarm log is disabled, new
alarms are not added to the log. When the alarm log is enabled again,
alarms that occurred while the log was disabled are put into the log (if
the alarms are stored at the console).
- To enable or disable the alarm log from the Alarm Configuration
screen:
D Cursor to the “Alarm Log” field and press [NEXT OPTION] to
make the desired entry. Press [ENTER].
- To enable the alarm log from the command line:
D Type E L A [ENTER].
- To disable the alarm log from the command line:
D Type D L A [ENTER].

CC: 6-5-1
Section 5:
Configuration and Display Topics
This section describes other alarm management issues such as the

Alarm Configuration screen, alarm regeneration, alarm priority, and
alarm display mode.
RS3: Alarm Management Configuration and Display Topics

CC: 6-5-2
Alarm Configuration Screen
The Alarm Configuration screen is used to configure parameters for

alarm management. Figure 6.5.1 shows the Alarm Configuration
screen.
Table 6.5.1 describes the fields on the screen.

D A C at the command line D [PAGE AHEAD] to see Automatic Alarm
D [PAGE AHEAD] from Event List Configuration Deletion
D [PAGE BACK] from Automatic Alarm Deletion D [PAGE BACK] to see Event List
Configuration
ALARM CONFIGURATION 25-Jul-92 12:07:37

Alarm Log ÞEnabled Alarm log fileÞfilename Alarm log size Þ3850 entries
Actual Log Size 142K
Alarm Log Types ÞSystem, Disk, Hard, Crit, Batch, Adv, EL1-EL10, Proc
Alarm Summary >Enabled Hardware alarms have more priority than ÞCrit
Alarm Regeneration : NOW Read Console Lists Þ16,18
Suppressed Types ÞSystem, Hard, Batch, Proc, Crit, Adv
Key classes:
suppress alarms ÞCONFIG screen ackÞCONFIG area status ÞCONFIG alarmviewÞCON-
FIG
Remote can Silence Þno Local Silence Time ®0 secs Alarm Speaker
®yes
Ack/Horn ÞSilence, then Ack Ack=Screen Ack? Þno External Alarm ÞOFF
Unacked, Cleared alarm ÞISA
Replace yellow on printout Þ5n brown Default priority for CB: Þ5 IOB: Þ2
Trend: Backup and File full alarms ÞEnabled Alarm View Toggle:>FULL
FULL CONFIG 11
Figure 6.5.1. Alarm Configuration Screen—Page 1

CC: 6-5-3
Table 6.5.1. Alarm Configuration Screen Fields
Field Description Field Entries
Specifies the effect on the console alarm horn (and any external
alarm contacts) of pressing the [ALARM ACK] key.
Silence then Specifies that, if the console horn is on, the
Ack first push silences the horn (and deactivates
any external alarm contacts) and the second
Silence, then Ack
push acknowledges the alarm.
Ack/Horn Silence and Ack
Silence and Ack Specifies that one push both silences the horn
No Silence
(and deactivates any external alarm contacts)
and acknowledges the alarm.
No Silence Specifies that pushing the key has no effect on
the console alarm horn (or any external alarm
contacts).
Specifies whether or not the [ALARM ACK] key performs a screen

acknowledge function on the following screens when the alarm
summary is enabled. The screen acknowledge function is
summarized below.
D Group and Unit—only acknowledges process alarms on
Ack=Screen points that are visible on the display. For example, if a
group faceplate does not show tag/A, then process alarms Yes, No
Ack?
on tag/A will not be acknowledged.
D Alarm lists—acknowledges all alarms visible on the
screen and those unacknowledged alarms that are an exact
match.
NOTE: This acknowledges alarms not visible on the screen.
Actual Log Displays the maximum size of the alarm log, in bytes. This value
Display only
Size is determined by the entry configured in the “Alarm Log Size” field.
Specifies whether the alarm log is Enabled or Disabled. When the

alarm log is disabled, new alarms are not added to the log. When
the alarm log is enabled again, any new alarms are put into the log
(if they are stored in console RAM).
If you disable the alarm log from the Alarm Configuration screen
Alarm Log Enabled, Disabled
and the field displays Shutdown, it indicates that the console is
inserting alarms in the alarm log.
While the field displays Shutdown, you cannot perform any actions
on the alarm log so that the console can finish its present task.
When the console is finished, the field displays Disable.
Specifies the maximum number of entries in the alarm log. If you

Alarm Log change the log size, the alarm log is cleared.
3850--65535
Size An alarm generated in a batch script uses 2 entries in the alarm
log.
NOTE: Bold text indicates default selections.

CC: 6-5-4
Table 6.5.1. Alarm Configuration Screen Fields (continued)
a=Advisory
Specifies which alarm types are included in the alarm log. b=Batch
To specify alarm types, type the first letter of the alarm types that c=Critical
you want to include. For example, “phb” indicates that process, d=Disk
Alarm Log hardware, and batch alarms are included in the alarm log.
h=Hardware
Types For event lists, specify the number of the event list. For example,
“1--5” specifies event lists 1 through 5. “0” specifies event list 10. p=Process
“1--0” specifies all event lists. s=System status
To specify all alarm types, enter “*”. 1--0=all event lists
*=all types listed
Causes a regeneration of console alarms. To regenerate alarms,

Alarm press [ENTER]. For more information about alarm regeneration, Now
Regeneration
see “Alarm Regeneration” on page 6-5-10.
Specifies whether or not the console alarm horn is activated.

Alarm speaker volume is configured in the “Speaker Volume” field
Alarm Speaker on the Console Configuration screen. yes, no
The “Alarm Speaker” field also appears on the Console
Specifies whether the alarm summary mode is Enabled or

Alarm Disabled. When the alarm summary mode is disabled, the alarm
Enabled, Disabled
Summary banner mode is enabled. For more information about alarm
display modes, see “Alarm Display Mode” on page 6-5-12.
Specifies whether the alarm animation is set to full or focused

mode. Full mode allows all the animation to be displayed
Alarm View including suppressed, disabled, and inhibited. Focused mode Full, Focused
Toggle
masks out the animation of suppressed, disabled, and inhibited
alarms.
Specifies default alarm priorities for ControlBlocks (CB) and I/O

CBÞ0--15
Default priority blocks (IOB). The default priorities are used when blocks are
IOBÞ0--3
for CB: IOB: created at this console. For more information about priorities, see
(0=high)
“Alarm Priority” on page 6-5-11.
Specifies the type of console contacts used if the console is

connected to an external annunciator. Contacts are actuated
when a process or hardware alarm occurs and are deactivated
when the console horn is silenced.
External Alarm D NC = normally closed (open on alarm) NC, NO, Off
D NO = normally open (closed on alarm)
D Off = non--functioning
The “External Speaker” field also appears on the Alarm List

CC: 6-5-5
Hardware Specifies the relative priority of hardware alarms. The entry

CRIT, ADV, BATCH,
alarms have specifies which alarm type follows hardware alarms in the system
SYSTEM, DISK,
more priority priority scheme. For more information about alarm priorities, see
NONE
than “Alarm Priority” on page 6-5-11.
Key class: Specifies the key access level required to toggle between full and CONFIG,
alarm view focused alarm views. SUPER, OPER
Key class: CONFIG,

Specifies the key access level required to enable/disable areas.
area status SUPER, OPER
Key Class: Specifies the key access level required to perform a screen CONFIG,
screen ack acknowledge function. SUPER, OPER
Key Class: Specifies the key access level required to suppress alarms. CONFIG,
suppress
alarms SUPER, OPER
Specifies the length of time (in seconds) that the console horn can
Local Silence be silenced with S H command line option, or with the [SIL] key.
0 to 300
Time New alarms will not reactivate the horn until the time period has
expired.
Specifies which consoles are searched for alarm messages upon

Read Console alarm regeneration. For more information about alarm Console node
Lists numbers
regeneration, see “Alarm Regeneration” on page 6-5-10.
Remote Can Specifies whether or not an alarm acknowledge at another

yes, no
Silence console silences the local console alarm horn.
Replace Specifies a color that replaces yellow when a screen is printed. a console color
yellow on Yellow is often difficult to see when printed. Use [NEXT OPTION] (a number 1--16
printout with to see the color choices. and n or r)
a=Advisory
Specifies which alarm types can be suppressed. b=Batch
To specify alarm types, type the first letter of the alarm types that c=Critical
Suppressed you want to include. For example, “sha” indicates that system h=Hardware
Types
status, hardware, and advisory alarms can be suppressed. p=Process
To specify all possible alarm types, enter “*”. s=System status
*=all types listed

CC: 6-5-6
Specifies whether or not Trend File Overflow, Trend File Overflow

Warning, and Trend File trfx Ready for Backup alarm messages
are included in the alarm log.
Trend: Backup
and File full NOTE: If you disable Trend Backup and File Full alarms, you will Enabled, Disabled
alarms not receive any trend overflow warnings in the Alarm Log.
Enabled specifies that the messages are included.
Disabled specifies that the messages are not included.
Specifies how alarms animate. Each entry specifies a different set

Unacked, of alarm animation characteristics. For more information about ISA, RMT, color
Cleared alarm
alarm animation, see Section 6,“Alarm Animation”.

CC: 6-5-7
Alarm Configuration Screen—Automatic Alarm Deletion
Figure 6.5.2 shows the Automatic Alarm Deletion screen. Table 6.5.2
describes the fields on this screen.
The Automatic Alarm Deletion screen deletes alarms from console RAM
when the conditions you specify are met.

D A C [ENTER] at the command line, D [PAGE AHEAD] to see Alarm List
then [PAGE AHEAD] Configuration
D [PAGE BACK] from Alarm List Configuration D [PAGE BACK] to see Alarm Configuration
AUTOMATIC ALARM DELETION 25-Jul-92 02:05:12

Delete Alarms/Events ÞDisabled Time (DD/HH:MM) Þ00/00:02
Types ÞCRIT, ADV, BATCH, HARD, EL1-EL10
Deletion Criteria
-------------------------------------------------
Types Acknowledged Logged Printed Priorities
CRITICAL Þyes Þyes Þyes Þ0-15
ADVISORY Þyes Þyes Þyes Þ0-15
BATCH Þyes Þyes Þyes Þ0-15
HARDWARE Þyes Þyes Þyes Þ0-15
SYSTEM Þyes Þyes Þyes Þ0-15
DISK Þyes Þyes Þyes Þ0-15
EVENT Þyes Þyes Þ0-15
Initialize Deletion Criteria for all types (Press ENTER)
The types appear when they are

configured in the Types field.
Figure 6.5.2. Automatic Alarm Deletion Screen

CC: 6-5-8
Table 6.5.2. Alarm Configuration Screen----Automatic Alarm Deletion Fields
Specifies whether or not alarms of this type must be

Acknowledged yes, no
acknowledged before they can be deleted.
Specifies whether the alarm delete process is enabled or

disabled.
The alarm delete process automatically deletes entries from
the alarm lists and event lists if the entries:
Delete D are cleared Enabled,
Alarms/Events Disabled
D are of the types configured in the “Types” field
D are older than the time configured in the “Time” field
D meet the “Acknowledged”, “Logged”, “Printed”, and
“Priorities” fields configured requirements
Initialize Deletion Pressing [ENTER] on this field clears the Deletion Criteria
[ENTER]
Criteria for all types table.
Specifies whether or not alarms of this type must be logged

before they can be deleted.
To be logged, all information known about an alarm at the
console must also be in the alarm log. For example, if an
alarm that is in the alarm log is cleared, the cleared
information must be entered in the alarm log before the alarm
Logged can be deleted. yes, no
If the heading Logged is blinking, then an alarm type is
configured with a Logged value of Yes, even though the alarm
type is not configured in the Alarm Log Types field on the
Alarm Configuration screen (page 1). This means that the
alarms of that type will not be logged and, therefore, will not
be deleted.
Specifies whether or not alarms of this type must be printed

before they can be deleted.
Printed yes, no
If the heading Printed is blinking, then there is a printer
problem that is preventing alarms from being printed.
Specifies the alarm priorities that can be deleted.

Priorities An entry can be a single number (for example, 7) or a range 0--15
of numbers separated by a dash (for example, 5--15).

CC: 6-5-9
Table 6.5.2. Alarm Configuration Screen----Automatic Alarm Deletion Fields (continued)
Specifies a time interval for the alarm delete process. All

alarms older than the specified time can be deleted.
For example, an entry of 00/12:00 specifies that all alarms a time in the form
Time (DD/HH:MM) more than 12 hours old can be deleted in the alarm delete dd/hh:mm
process. 00/00:00
For a description of the alarm delete process, see the “Delete
Alarms” field.
a=Advisory
Specifies the types of alarms that can be deleted in the alarm b=Batch
delete process.
c=Critical
To specify alarm types, type the first letter of the alarm types
that you want to include. For example, “sha” indicates that d=Disk
Types system status, hardware, and advisory alarms can be deleted. h=Hardware
To specify all possible alarm types, enter “*”. p=Process
For event lists, specify the number of the event list. For s=System status
example, “1--5” specifies event lists 1 through 5. “0” specifies
event list 10. “1--0” specifies all event lists. 1--0=all event lists
*=all types listed

CC: 6-5-10
Alarm Regeneration
This heading describes alarm regeneration.
Purpose
If a console quits functioning or is rebooted, alarms stored in console

RAM are lost. When the console becomes functional again, the alarm
lists can be regenerated from other consoles.
When Do Alarms Regenerate
Alarms are automatically regenerated when the console restarts. You

can also manually regenerate alarms.
How Consoles Regenerate Alarms
You specify which consoles are searched during alarm regeneration.

When alarm regeneration occurs, the regenerating console searches
the specified consoles for alarms.
If the source of an alarm in another console is owned by the
regenerating console, the regenerating console retrieves the alarm. For
more information about ownership criteria, see “How Alarms Get Stored
in Console RAM” on page 6-2-1.
Configuration
The “Read Console Lists” field on the Alarm Configuration screen is

used to specify which consoles are to be searched during alarm
regeneration. The “Alarm Regeneration” field is used to regenerate
alarms manually. For more information about the Alarm Configuration
screen, see “Alarm Configuration Screen” on page 6-5-2.
Restrictions
D Alarm regeneration does not work with 68000--based consoles.

In addition, none of the nodes specified in the “Read Console
Lists” field should be 68000--based consoles.
D The console can only regenerate alarms if they are present at the
specified consoles. If the other consoles have rebooted,
initialized their alarm lists, or otherwise lost their alarms, the
console cannot recover the desired alarms.

CC: 6-5-11
Alarm Priority
Alarms are prioritized by alarm type, and by alarm priority number within
each alarm type. Alarm priorities determine which unacknowledged
alarm message is displayed in alarm banner mode when more than one
unacknowledged alarm exists. The unacknowledged alarm messages
are displayed according to the following criteria:
1. Alarm type priority
2. Alarm priority number
3. Time of alarm (newest first)
Alarm Type Priority
The alarm types are prioritized in the following order:

D Hardware[
D Critical Process
D Advisory Process
D Batch
D System Status
D Disk Event
[ This is the default priority. You can configure the relative priority of
hardware alarms with the “Hardware Alarms Have More Priority Than”
field on the Alarm Configuration screen. For more information about the
Alarm Configuration screen, see “Alarm Configuration Screen” on
page 6-5-2.
Alarm Priority Numbers
Each alarm message is assigned a priority number. The priority

numbers are used to determine priority within an alarm type.
D When you configure a block, you assign the priority number for
alarms from that block.
D All other alarms have a priority number of 0 (highest priority).
You can configure the default priority levels for blocks with the “Default
priority for CB” and “Default priority for IOB” fields on the Alarm
Configuration screen. For more information about the Alarm
Configuration screen, see “Alarm Configuration Screen” on
page 6-5-2.

CC: 6-5-12
Alarm Display Mode
The bottom of the console screen displays alarm information. You

determine whether the alarm information is presented in alarm banner
mode or alarm summary mode. For information on setting the alarm
mode, see 6-5-13. For information about using the alarm display
modes, see OP: 6 and the Alarm Messages Manual.
Alarm Banner Mode
Alarm banner mode displays the alarm banner of the unacknowledged

alarm with the highest priority. The alarm banner provides information
about the alarm. Figure 6.5.3 shows an example of an alarm banner.
18:46:11.685 >=19A LIC-200/PV Drum Level High Critical ?-OK LEVEL
Figure 6.5.3. Example of an Alarm Banner
Alarm Summary Mode
Alarm summary mode displays a summary of alarm type information,

including the number of active and unacknowledged alarms. The alarm
types are also annunciated. Figure 6.5.4 shows an example of an
alarm summary.
FULL Crit 0/0 Adv 0/0 Batch 0/0 Hard 2/3 Sys 0/5 CONFIG 1
Number of Number of
active alarms unacknowledged
alarms
Figure 6.5.4. Example of an Alarm Summary

CC: 6-5-13
Determining the Alarm Display Mode
- To change the alarm display mode from the Alarm

Configuration screen:
D Cursor to the “Alarm Summary” field. Press [NEXT OPTION]
until the desired entry appears. Press [ENTER].
- To enable the alarm summary mode (disable the alarm banner
mode) from the command line:
D Press A S E [ENTER].
- To disable the alarm summary mode (enable the alarm banner
mode) from the command line:
D Press A S D [ENTER].

CC: 6-6-1
Section 6:
Alarm Animation
What is alarm animation?
Alarm animation consists of visual cues on RS3 displays that indicate

alarm information. Animation can involve color, blinking, and
backlighting.
There are two types of alarm animation:

D Focused Mode
D Full Mode
Focused mode means that certain objects are not highlighted when they
have been disabled, suppressed, or inhibited, or when the object plant
unit is unowned.
Full mode means that tags that are disabled, suppressed, or inhibited
will highlight in the disabled, suppressed, or inhibited color. In addition,
values from continuous block variables from unowned nodes or plant
units will continue to animate.
The animation modes only affect the animation of tags and values.
They do not affect any other type of object, and they do not affect
animation on alarm lists or the alarm log display.
You can set the animation mode on the Alarm Configuration screen or
from the command line with Alarm View Toggle. For more information
on how to set the animation mode, see page 6-5-1.
What parts of RS3 displays animate?
Many displays include items that animate alarm conditions. This

section groups together items that animate alarms in the same way:
D Tags
D Tags on Trend Group Displays
D Block values
D Plant Units and Alarm Areas
D Graphic Alarm objects and Icon objects
D Alarm message source descriptions
RS3: Alarm Management Alarm Animation

CC: 6-6-2
Animation tables
Most of this section consists of animation tables like the one shown in
Figure 6.6.1. The tables are designed for you to copy and use in your
plant. The tables show how the alarms work with the Full Animation
Mode. For information on the Focused Animation Mode, see
page 6-6-1.
For example, Table 6.6.1 through Table 6.6.10 are the animation tables
for tags. Each of these tables describes alarm animation for one set of
configuration parameters. You can select the table that matches your
configuration, write in the colors you have configured for your plant, and
make copies for the users of your system.
Item animated
Configuration parameters
valid for this table
Table 6.6.1. Tag Animation
Hardware Alarms Have More Priority than ÞCrit
Unacked, Cleared Alarm ÞISA
Color Configuration Plant Color Meaning
D If unblinking
-- active hardware alarm and no
unacked alarms
Hardware Alarms D If blinking
-- active hardware alarm and an
unacked alarm, or
-- unacked hardware alarm
D Plant unit is not disabled.
D Block is not inhibited.
D If unblinking
-- active critical alarm, and no active
hardware alarms, and no unacked
Critical Alarms alarms
D f blinking, no active or unacked hardware
alarms, and
-- active critical alarm and an unacked
alarm or
-- unacked critical alarm
Lists the field on the Color Blank area where you can Alarm information that
Configuration screen that write in the color you have can be determined if this
determines the animation color configured for your plant color is displayed
Figure 6.6.1. Example Portion of an Animation Table

CC: 6-6-3
Tags
Screens that animate tags

D ControlBlock Directory screen
D ControlBlock Faceplate screens
D ControlBlock Status screen
D Group Display
D Loop Tuning Display
D Overview Display
D Process Graphics
— Overview object
— Pop--up faceplates
— Tag object
— Unit object
D Unit Display
Animation tables
Table 6.6.1 Hardware Alarms Have More Priority thanÞCrit
Unacked, Cleared AlarmÞISA
Table 6.6.2 Hardware Alarms Have More Priority thanÞAdv
Table 6.6.3 Hardware Alarms Have More Priority thanÞBatch
Table 6.6.4 Hardware Alarms Have More Priority thanÞSystem
Table 6.6.5 Hardware Alarms Have More Priority thanÞDisk or None
Unacked, Cleared AlarmÞRMT or Color

CC: 6-6-4
Table 6.6.1. Tag Animation Hardware Alarms Have More Priority thanÞCrit
Color Configuration Meaning Plant Color

Inhibit Alarms* D Block is inhibited.
D All areas with this plant unit are disabled.
Disable Alarms*
D Block alarms are suppressed and no active or unacked
Suppressed Alarms* alarms exist for suppressed type exceptions.
D Plant unit is not disabled. Block is not inhibited.
D If not blinking
-- active hardware alarm and no unacked alarms
D If blinking
Hardware Alarms
-- active hardware alarm and an unacked alarm, or
-- unacked hardware alarm.
D If not blinking
-- active critical alarm, and no active hardware alarms,
and no unacked alarms
Critical Alarms D If blinking, no active or unacked hardware alarms, and
-- active critical alarm and an unacked alarm or
-- unacked critical alarm.
D If not blinking
-- active advisory alarm, and no active hardware or
critical alarms, and no unacked alarms
D If blinking, no active or unacked hardware or critical
Advisory Alarms alarms, and
-- active advisory alarm and an unacked alarm, or
-- unacked advisory alarm
D If not blinking
-- active batch alarm, and no active hardware, critical,
or advisory alarms, and no unacked alarms
D If blinking, no active or unacked hardware, critical, or
Batch Alarms advisory alarms, and
-- active batch alarm and an unacked alarm, or
-- unacked batch alarm
D If not blinking
-- active system alarm, and no active hardware,
critical, advisory, or batch alarms, and no unacked
alarms
System Alarms D If blinking, no active or unacked hardware, critical,
advisory, or batch alarms, and
-- active system alarm and an unacked alarm, or
-- unacked system alarm
* In Focused Mode, the tags for alarms that are inhibited, disabled, or suppressed will not animate.

CC: 6-6-5
Table 6.6.2. Tag Animation Hardware Alarms Have More Priority thanÞAdv

Disable Alarms*
D If not blinking
D If blinking
Hardware Alarms
D If not blinking
D If not blinking
D If not blinking
D If not blinking
alarms

CC: 6-6-6
Table 6.6.3. Tag Animation Hardware Alarms Have More Priority thanÞBatch

Disable Alarms*
D If not blinking
D If blinking
Hardware Alarms
D If not blinking
D If not blinking
D If not blinking
D If not blinking
alarms

CC: 6-6-7
Table 6.6.4. Tag Animation Hardware Alarms Have More Priority thanÞSystem

Disable Alarms*
D If not blinking
D If blinking
Hardware Alarms
D If not blinking
D If not blinking
D If not blinking
D If not blinking
alarms

CC: 6-6-8
Table 6.6.5. Tag Animation Hardware Alarms Have More Priority thanÞDisk or None

Disable Alarms*
D If not blinking
D If blinking
Hardware Alarms
D If not blinking
D If not blinking
D If not blinking
D If not blinking
alarms

CC: 6-6-9
Table 6.6.6. Tag Animation Hardware Alarms Have More Priority thanÞCrit
Color
Meaning Plant Color
Configuration

Disable Alarms*
D Block alarms are suppressed and no active or

unacked alarms exist for suppressed type exceptions.
Suppressed Alarms* D Plant unit is not disabled.
D Active hardware alarm

D If blinking, unacked alarm
Hardware Alarms D If not blinking, no unacked alarms
D Active critical alarm
D No active hardware alarms
Critical Alarms
D If not blinking, no unacked alarms
D Active advisory alarm
D No active hardware or critical alarms
Advisory Alarms
D Active batch alarm

D No active hardware, critical, or advisory alarms
Batch Alarms
D Active system alarm
D No active hardware, critical, advisory, or batch alarms
System Alarms
D Plant unit is not disabled
D Block is not inhibited
A) Blinking in some
other color A) Unacked, Cleared AlarmÞRMT only
B) Color on B) Unacked, Cleared AlarmÞColor only
Unacked, Cleared D Unacked, cleared alarm
Alarm field on D No active alarms
Alarm D Plant unit is not disabled
Configuration D Block is not inhibited
screen

CC: 6-6-10
Table 6.6.7. Tag Animation Hardware Alarms Have More Priority thanÞAdv

Disable Alarms*

unacked alarms exist for suppressed type
Suppressed Alarms* exceptions.


Critical Alarms

Advisory Alarms

Batch Alarms

D No active hardware, critical, advisory, or batch
alarms
System Alarms D If blinking, unacked alarm
A) Blinking in some A) Unacked, Cleared AlarmÞRMT only

other color B) Unacked, Cleared AlarmÞColor only
B) Color on Unacked, D Unacked, cleared alarm
Cleared Alarm field D No active alarms
on Alarm D Plant unit is not disabled
Configuration screen D Block is not inhibited

CC: 6-6-11
Table 6.6.8. Tag Animation Hardware Alarms Have More Priority thanÞBatch

Disable Alarms*



Critical Alarms

Advisory Alarms

Batch Alarms

alarms


CC: 6-6-12
Table 6.6.9. Tag Animation Hardware Alarms Have More Priority thanÞSystem

Disable Alarms*



Critical Alarms

Advisory Alarms

Batch Alarms

alarms


CC: 6-6-13
Table 6.6.10. Tag Animation Hardware Alarms Have More Priority thanÞDisk or None

Disable Alarms*
Critical Alarms
Advisory Alarms
Batch Alarms
alarms


CC: 6-6-14
Tags on Trend Group Displays
The Tag field on the Trend Group Display animates the same as block
variable values.
Animation tables
See Table 6.6.11 through Table 6.6.20.

CC: 6-6-15
Block Variable Values
Screens that animate block variable values

D ControlBlock Faceplate screens
D Group Displays
D Loop Tuning Displays—discrete faceplates only
D Process Graphics
— Disc object
— Group object
— Link object
— Pop--up faceplate
— Unit object
— Overview object
D Unit Displays
D Overview Display
Animation tables

CC: 6-6-16
D If not blinking
D If blinking
Hardware Alarms
-- active hardware alarm and an unacked alarm,
or
D If not blinking
-- active critical alarm, and no active hardware
alarms, and no unacked alarms
D If blinking, no active or unacked hardware alarms,
Critical Alarms
and
-- active critical alarm and an unacked alarm
or
D If not blinking
Advisory Alarms
alarms, and
-- active advisory alarm and an unacked alarm,
or
D If not blinking
-- active batch alarm, and no active hardware,
critical, or advisory alarms, and no unacked
alarms
Batch Alarms D If blinking, no active or unacked hardware, critical, or
advisory alarms, and
-- active batch alarm and an unacked alarm,
or
D If not blinking
alarms
-- active system alarm and an unacked alarm,
or
NOTE: In Focused Mode, block variable values will not animate unless the plant units are owned and the
block is not disabled or suppressed.

CC: 6-6-17
D If not blinking
D If blinking
Hardware Alarms
or
D If not blinking
Critical Alarms
and
or
D If not blinking
Advisory Alarms
alarms, and
or
D If not blinking
alarms
or
D If not blinking
alarms
or

CC: 6-6-18
D If not blinking
D If blinking
Hardware Alarms
or
D If not blinking
Critical Alarms
and
or
D If not blinking
Advisory Alarms
alarms, and
or
D If not blinking
alarms
or
D If not blinking
alarms
or

CC: 6-6-19
D If not blinking
D If blinking
Hardware Alarms
or
D If not blinking
Critical Alarms
and
or
D If not blinking
Advisory Alarms
alarms, and
or
D If not blinking
alarms
or
D If not blinking
alarms
or

CC: 6-6-20
D If not blinking
D If blinking
Hardware Alarms
or
D If not blinking
Critical Alarms
and
or
D If not blinking
Advisory Alarms
alarms, and
or
D If not blinking
alarms
or
D If not blinking
alarms
or

CC: 6-6-21

Hardware Alarms D If blinking, unacked alarm
D If unblinking, no unacked alarms

Critical Alarms

Advisory Alarms

Batch Alarms

System Alarms alarms
A) Blinking in some
B) Color on Unacked, B) Unacked, Cleared AlarmÞColor only
Cleared Alarm field D Unacked, cleared alarm
on Alarm D No active alarms

CC: 6-6-22


Critical Alarms

Advisory Alarms

Batch Alarms

A) Blinking in some

CC: 6-6-23


Critical Alarms

Advisory Alarms

Batch Alarms

A) Blinking in some

CC: 6-6-24


Critical Alarms

Advisory Alarms

Batch Alarms

A) Blinking in some

CC: 6-6-25


Critical Alarms

Advisory Alarms

Batch Alarms

A) Blinking in some

CC: 6-6-26
Plant Units and Area Names
Screens that animate plant units

D Plant Configuration screen
D Area Name Configuration
(only plant units immediately to the right of the area name)
Screens that animate area names

D Area Name Configuration screen
Animation tables

CC: 6-6-27

D Plant Unit:
-- all areas with this plant unit are disabled
D Area Name:
Disable Alarms -- area is disabled
-- all plant units in this area are disabled. Plant units
can exist in more than one area. The plant unit
must be disabled in all areas to be truly disabled.
D If not blinking
D If blinking
Hardware Alarms
D Plant unit or area name is not disabled
D If not blinking
D If not blinking
D If not blinking
D If not blinking
alarms

CC: 6-6-28

D Plant Unit:
D Area Name:
D If not blinking
D If blinking
Hardware Alarms
D If not blinking
D If not blinking
D If not blinking
D If not blinking
alarms

CC: 6-6-29

D Plant Unit:
D Area Name:
D If not blinking
D If blinking
Hardware Alarms
D If not blinking
D If not blinking
D If not blinking
D If not blinking
alarms

CC: 6-6-30

D Plant Unit:
D Area Name:
D If not blinking
D If blinking
Hardware Alarms
D If not blinking
D If not blinking
D If not blinking
D If not blinking
alarms

CC: 6-6-31

D Plant Unit:
D Area Name:
D If not blinking
D If blinking
Hardware Alarms
D If not blinking
D If not blinking
D If not blinking
D If not blinking
alarms

CC: 6-6-32

Plant Unit:
Area Name:
-- all plant units in this area are disabled. Plant
units can exist in more than one area. The
plant unit must be disabled in all areas to be
truly disabled.
Hardware Alarms
Critical Alarms D If blinking, unacked alarm
Advisory Alarms D If blinking, unacked alarm
Batch Alarms D If blinking, unacked alarm
alarms
System Alarms
Cleared Alarm field
Configuration screen D Plant unit or area name is not disabled

CC: 6-6-33

Plant Unit:
Area Name:
truly disabled.
Hardware Alarms
alarms
System Alarms
Cleared Alarm field

CC: 6-6-34

Plant Unit:
Area Name:
truly disabled.
Hardware Alarms
alarms
System Alarms
Cleared Alarm field

CC: 6-6-35

Plant Unit:
Area Name:
truly disabled.
Hardware Alarms
alarms
System Alarms
Cleared Alarm field

CC: 6-6-36

Plant Unit:
Area Name:
truly disabled.
Hardware Alarms
alarms
System Alarms
Cleared Alarm field

CC: 6-6-37
Graphic Alarm Objects and Icon Objects
Items that animate

D Alarm object window title
D Icon object that is grouped with one or more Alarm objects
(has same animation as the Alarm object configured in the
Al Obj field)
Animation tables

CC: 6-6-38

D If not blinking
-- active hardware alarm or active disk alarm and no
Hardware Alarms unacked alarms
Disk Alarms* D If blinking
-- unacked hardware alarm or unacked disk alarm
D If not blinking
Critical Alarms
D If blinking, no active or unacked hardware alarms, and
D If not blinking
Advisory Alarms D If blinking, no active or unacked hardware or critical
alarms, and
D If not blinking
D If not blinking
alarms
System Alarms
D If blinking, no active or unacked hardware, critical,
* Disk Alarms use the configured Hardware alarm color.

CC: 6-6-39

D If not blinking
D If not blinking
Critical Alarms
D If not blinking
alarms, and
D If not blinking
D If not blinking
alarms
System Alarms

CC: 6-6-40

D If not blinking
D If not blinking
Critical Alarms
D If not blinking
alarms, and
D If not blinking
D If not blinking
alarms
System Alarms

CC: 6-6-41

D If not blinking
D If not blinking
Critical Alarms
D If not blinking
alarms, and
D If not blinking
D If not blinking
alarms
System Alarms

CC: 6-6-42

D If not blinking
D If not blinking
Critical Alarms
D If not blinking
alarms, and
D If not blinking
D If not blinking
alarms
System Alarms

CC: 6-6-43

D Active hardware alarm or active disk alarm

Hardware Alarms
Disk Alarms*

Critical Alarms

Advisory Alarms

Batch Alarms

System Alarms
A) Blinking in some
Cleared Alarm field
D Unacked, cleared alarm
on Alarm
Configuration D No active alarms
screen
* Disk alarms use the configured Hardware alarm color.

CC: 6-6-44


Hardware Alarms
Disk Alarms*

Critical Alarms

Advisory Alarms

Batch Alarms

System Alarms
A) Blinking in some
Cleared Alarm field
on Alarm
screen

CC: 6-6-45


Hardware Alarms
Disk Alarms*

Critical Alarms

Advisory Alarms

Batch Alarms

System Alarms
A) Blinking in some
Cleared Alarm field
on Alarm
screen

CC: 6-6-46


Hardware Alarms
Disk Alarms*

Critical Alarms

Advisory Alarms

Batch Alarms

System Alarms
A) Blinking in some
Cleared Alarm field
on Alarm
screen

CC: 6-6-47


Hardware Alarms
Disk Alarms*

Critical Alarms

Advisory Alarms

Batch Alarms

System Alarms
A) Blinking in some
Cleared Alarm field
on Alarm
screen

CC: 6-6-48
Alarm Message Source Descriptions
What is an alarm message source description?
An alarm message usually contains a tag or address that indicates the

source of the alarm.
Screens that animate alarm message source descriptions

D Alarm lists
D Graphics Alarm object
Table 6.6.41. Alarm Message Source Description Animation
D If blinking, alarm is unacked

Any color
D If backlighted and not blinking, alarm is active

CC: 6-7-1
Section 7:
Hints for Alarm Management

configuring event lists, along with some configuration tips.
- Some entries on event lists do not include all of the event
information.
Because of the limited size of event entries, some information may
be truncated or left off.
- Some entries on event list printouts do not include dates.
Dates do not appear on event list printouts when the event lists are
automatically generated.
Configuration Tips
- Using alarm broadcast configurations with batch systems
If you have batch scripts that use alarm traps, be sure to include the
associated Batch ControlFile nodes in the alarm broadcast
configurations. Otherwise, the alarm messages that you want to
trap on will never reach the Batch CPs.
- How to configure alarm lists so that alarms are printed one at a
time without a form feed command or a header.
Configure “Alarm PrintÞSingle Line” and “TriggerÞ1” on the Alarm
List Configuration screen for the desired alarm lists.
- How to configure Alarm Logs for good system performance.
Alarm Logs are designed to provide flexibility and versatility.
However, using this flexibility to its fullest can reduce system
performance. For example, alarm logs can contain over 65,000
entries. However, alarm logs over 15,000 entries can decrease
console performance.
In general, keep in mind that alarm log activities (logging, displaying,
filtering, and so on) are disk processes. The console must perform
these functions in addition to trending, reports, graphics, and other
disk activities. If the console disk is heavily loaded, console
performance may suffer.
RS3: Alarm Management Hints for Alarm Management

RS3t
Chapter 7:
Password Security
Section 1: Version 18 Changes to Current System . . . . . . . . . . . . . . . . . . . . . 7-1-1

Changes to Current System Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1-2
New Access Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1-4
Changes to Console Configuration Screen—Page 1 . . . . . . . . . . . . . . . . . . . . . 7-1-4
Changes to Disk and Tape Activities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1-5
Modifications to Operator Change Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1-6
Section 2: Accessing a Password Secure System . . . . . . . . . . . . . . . . . . . . . 7-2-1

Logging on to the System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2-2
Changing a Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2-4
Logging Off the Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2-6
Section 3: Configuring Password Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3-1

Initial Password System Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3-1
Configuring Factory-shipped Password System . . . . . . . . . . . . . . . . . . . . . . . . . 7-3-2
Logging in and Configuring Primary and Backup Nodes . . . . . . . . . . . . . . . 7-3-3
Changing User and Login Names and Completing Configuration . . . . . . . 7-3-4
Defining Password Security with a Configuror’s Key . . . . . . . . . . . . . . . . . . . . 7-3-5
Configuring Primary and Backup Nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3-5
Adding a System Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3-6
Logging In . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3-7
System-wide Password Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3-8
Defining System-wide Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3-10
Saving the Console Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3-11
User Profile Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3-12
Plant Unit Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3-14
Plant Unit Access and Plant Unit Configuration . . . . . . . . . . . . . . . . . . . . . . . . . 7-3-15
Defining Plant Unit Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3-16
Changing Plant Unit Access Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3-18
User Name Detail Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3-19
Adding Users to the Password System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3-22
Changing User Name Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3-23
Changing a Configuror to a System Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3-24
RS3: Password Security Contents

CC: ii
Section 4: Password Security Hints and Troubleshooting . . . . . . . . . . . . . 7-4-1

Scenario 1: Handling Primary and Backup Nodes . . . . . . . . . . . . . . . . . . . . . . . . . 7-4-2
Scenario 2: Using Passwords with Keylock and Secure Interfaces . . . . . . . . . . . 7-4-3
Scenario 3: Using Passwords with a Standard KBI . . . . . . . . . . . . . . . . . . . . . . . . 7-4-4
Scenario 4: Using Key and Password Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-4-5
Scenario 5: Loss of $$PASSWD File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-4-6
Scenario 6: Console Configuration File Not Found . . . . . . . . . . . . . . . . . . . . . . . . 7-4-7

CC: iii
List of Figures
Figure Page
7.1.1 Operator Change Log Entries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1-7
7.2.1 Login Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2-3
7.2.2 Changing a Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2-4
7.3.1 Console Configuration Screen—Page 3 . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3-9
7.3.2 User Profile Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3-13
7.3.3 Plant Unit Access Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3-17
7.3.4 User Name Detail Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3-19
7.3.5 Changing Configuror to System Manager . . . . . . . . . . . . . . . . . . . . . . . . 7-3-24

CC: iv
List of Tables
Table Page
7.1.1 Commands that Call Up Screens . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1-3
7.2.1 Login Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2-3
7.3.1 Console Configuration Screen Fields—Page 3 . . . . . . . . . . . . . . . . . . . . 7-3-9
7.3.2 User Profile Directory Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3-13
7.3.3 Plant Unit Access Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3-17
7.3.4 User Name Detail Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3-20

CC: 7-1-1
Section 1:
Version 18 Changes to Current System
RS3 Version 18 provides password security for 68020 and 68040

consoles. This enhancement gives the RS3 control system more
adaptability where tighter security is required.
One system can handle up to 991 users with each one being given
unique plant unit access. This password system provides an electronic
signature for each user and, in general, meets the requirements of a
signature on paper.
The most efficient implementation of password security requires a new

keyboard interface that has no physical key for accessing the system.
The existing keyboard interface that allows use of the physical key can
be configured for password security by following special instructions
that are explained on page CC:7-3-5.
CAUTION
In order to minimize the risk of losing the $$PASSWD file,
be sure that you make a backup copy of the file that was
shipped with your system before you do any password
system configuration.
It is also recommended that you read Section 4 in this
chapter before you attempt to configure your password
security.
RS3: Password Security Version 18 Changes to Current System

CC: 7-1-2
Changes to Current System Operation
The password security system required access level changes,

modifications to existing screens, and five new screens.
Access levels changed for disk activities and for fields on Page 1 of the
Console Configuration screen. For details, see the following sections:
D New Access Level ( 7-1-4)
D Changes to Console Configuration Screen ( 7-1-4)
D Changes to Disk and Tape Activities ( 7-1-5).
The console now includes five new screens that manage password
security functions:
D Login screen (See Logging on to the System, CC:7-2-2).
D Console Configuration (See System-wide Password Parameters,
CC:7-3-8).
D User Profile Directory screen (See Using the User Profile
Directory, CC:7-3-12).
D Plant Unit Access screen (See Defining Plant Unit Access,
CC:7-3-14).
D User Name Detail screen (See User Name Detail Screen,
CC:7-3-19).
Table 7.1.1 lists the new commands for accessing these screens and
the command to log off the system.
New instruction have been added to the Rosemount Basic Language to

handle security requirements for batch applications. See the RBL
Manual for details.

CC: 7-1-3
Table 7.1.1. Commands that Call Up Screens
Screen Entry Command Line Text
User Name Detail UND (login_name) [ENTER] User Name Detail
Plant Unit Access PUA (filename) [ENTER] Plant Unit Access
User Profile Directory UPD [ENTER] User Profile Directory
Login CUP [ENTER] Change User Password
Login LI [ENTER] Log In :
Log out LO [ENTER] Log Out :

CC: 7-1-4
New Access Level
In addition to the existing access levels (Configuror, Supervisor,

Operator, Recipe Manager, and None), a new security privilege has
been added:
D System Manager (SYSMGR) is the level required to set up
password security and to perform certain disk and tape
operations.
Changes to Console Configuration Screen—Page 1
On page 1 of the Console Configuration screen, the field that resets the
clock time and date can only be changed by a SYSMGR. The field
“slotw” can be edited only by a system manager. This change enables
those with HIAs to adjust the PeerWay as needed.

CC: 7-1-5
Changes to Disk and Tape Activities
Several disk and tape operations now require system manager

privileges. The actual operations have not changed, only the level of
access.
Only a system manager is allowed to perform disk operations on the

$$PASSWD file in the Console Configuration folder.
In addition, only a system manager is allowed to perform these

operations:
D Configure the hard disk.
D Delete a Console Configuration folder.
D Initialize the disk.
If any user other than a system manager attempts to perform these

activities, no enterable fields appear on the screen.

CC: 7-1-6
Modifications to Operator Change Log
Messages in the Operator Change Log have been modified to indicate

users who are logged in. These changes are also shown in
Figure 7.1.1.
D The source, which states the type of console, the node number,
and the key value, are not listed when the login names are
identified.
D The new Operator Change Log includes a “Login Name” field
that shows all 16 characters of the login name if all 16 are used.
Other screens show only the first eight characters.
D The “Login Name” appears in place of the “Key” field. If the
value in the “Key” field is 2, then the preceding number is a user
number and not a node number.
D The batch log shows the name of the user instead of the key
value.

CC: 7-1-7
OPERATOR CHANGE LOG 12-Mar-93 10:49:18
--Occur---PU------Location-----Parameter----Old------New-----Source---Key-----
------------------- 12-Mar-93
08:49:33 175 :=49A-16/PV Input A .00 .50 MTCC=88 SUPER 1
08:48:46 175 :=49A-15 Block Mode AUTO MANUAL MTCC=88 SUPER 1
08:48:00 0 Key Changed No Key SUPER 1 MTCC=88
08:47:50 0 Key Changed OPER 6 No Key MTCC=88
08:47:06 175 :=49A-17 Block Mode AUTO MANUAL MTCC=88 OPER 6
08:46:53 175 :=49A-17/PV Input A .00 .10 MTCC=88 OPER 6
08:45:17 0 Key Changed No Key OPER 6 MTCC=88
08:35:14 0 Key Changed CONFIG 1 No Key MTCC=88
08:34:25 175 :=49AA501 Block Mode MANUAL AUTO MTCC=88 CONFIG 1
Operator Change Log Format with Keylock System
MakeConsoleKeylock System* OPERATOR CHANGE LOG 12-Mar-93 11:01:41
--Occur---PU------Location-----Parameter----Old------New-----Login Name-------
------------------- 12-Mar-93
11:00:45 175 :=49A-15/PV Input A .00 .60 kenta
11:00:13 175 :=49A-17 Block Mode AUTO MANUAL kenta
11:01:28 0 Login Change kenta No User
11:01:28 0 Login Change ******* *******
10:59:40 175 :=49AA502 Block Mode AUTO MANUAL joew
10:59:33 175 :=49AA502 Block Out .00 .50 joew
10:54:58 0 Login Change No User joew
10:54:27 0 Login Change ******* *******
10:59:18 175 :=49AA503 Block Mode MANUAL AUTO johnp
Operator Change Log Format with Password System
Occur PU Location Parameter Old New User No.

-------- ---- ---------------- ------------ -------- -------- ------- --------
hh:mm:ss #PU >TAG4567890123456 Parameter012 OldValue NewValue User No.
New Operator Change Log Format for SCI and QBI
Figure 7.1.1. Operator Change Log Entries

CC: 7-2-1
Section 2:
Accessing a Password Secure System
This section explains how all users can gain access to a password--
secure RS3 distributed control system.
The login process differs slightly depending on the console state:

D A cold login occurs if the console is initializing with an existing
$$PASSWD file after a reboot or power--up situation. Following
the entry of a valid login name and password, the console
displays the Menu Command Console screen.
D A warm login occurs after a user has logged off a console that is
still in a normal operating condition. Following the entry of a
valid login name and password, the last screen that the previous
user was viewing appears; however, if a system manager was
the last one logged in, the Menu Command Console screen is
displayed.
CAUTION
If you press the [CRT] button to move to another console,
your privileges become those of the person logged in to
that console.
RS3: Password Security Accessing a Password Secure System

CC: 7-2-2
Logging on to the System
The Login screen shown in Figure 7.2.1 allows you to log into the
system based on additional criteria:
D If “Automatic Update” for the system is set to “Yes” and that
update time has expired, you are prompted to define a new
password before gaining access to the console.
D If you have a login that is restricted by days and hours, the
system verifies the current time before allowing you to access the
console.
D If your password has been set to “Canceled” and you attempt to
log in, you receive a “Login Incorrect” message and cannot
access the console.
Table 7.2.1 explains the fields on the Login screen.

- To log in to the console:
1. From the command line, type
LI [ENTER]
NOTE: The name of the last person logged in automatically appears in

the “Login” field; however, if this person has a time-restricted login, the
“Login” field becomes blank.
2. Cursor to the “Login” field; type your login name as defined by
the system manager, and press [ENTER].
3. Type your password, and press [ENTER].

CC: 7-2-3
- To access the Login screen:

D On the command line, type
LI [ENTER]
Change Password 12-Mar-93 10:47:51
Login
Password :
Silence Horn: (press ENTER)

Copyright E 1981-1994 Fisher-Rosemount Systems, Inc.
Figure 7.2.1. Login Screen
Table 7.2.1. Login Screen
Valid login name for this user. 4 to 16

Login NOTE: If the user was the last one logged into this console, no alphanumeric
entry in the “Login” field is required. characters
Valid password for the user whose name was entered in the
“Login” field. 6 to 16
Password NOTE: The password is case sensitive. If you are logging in alphanumeric
for the first time, you must type “Cleared” in upper and lower characters
cases as shown here.
Allows user to silence the horn generated by alarms that have

occurred while no one is logged onto the console.
Silence Horn:
NOTE: Pressing [ENTER] on this field has the same effect as [ENTER]
(press Enter)
pressing [ACK] the first time to silence an alarm; pressing
[ACK] after you log in actually acknowledges the alarm.
Next Password
Indicates next time that you must change your password. Display only
Update

CC: 7-2-4
Changing a Password
Changing a password involves three basic steps:

D Confirming your old password
D Entering a new password
D Verifying the new password by entering it a second time.
The following situations allow (or require) you to change your password:
D You are logged onto the system and know that you must update
your password before you log on again.
D Your password is defined as “Cleared”.
D You are logged off and the password update time has passed.
In the first situation, you can begin changing your password from the
command line. In the other two situations, you are prompted to change
your password when you attempt to log in.
Change Password 12-Mar-93 10:47:51
Login SYSMGR
Old Password :
Login SYSMGR
New Password :
Login SYSMGR
Repeat Password :
Figure 7.2.2. Changing a Password

CC: 7-2-5
- To change a password while logged onto the console:

1. On the command line, type
CUP [ENTER]
The Login screen appears as shown in Figure 7.2.2.
2. Cursor to the “OLD PASSWORD” field; type the current
password, and press [ENTER].
The field changes to “NEW PASSWORD”.
3. Type a new password with 6 to 16 characters, and press
[ENTER].
The field changes to “REPEAT PASSWORD”.
4. Type the new password again, and press [ENTER].
If both entries (Steps 2 and 3) match, the console recalls the
display that was on the screen before you issued the “CUP”
command.
- To change a password without first logging onto the console:
LI [ENTER]
The Login screen appears with a message that indicates the
password must be updated.
2. Cursor to the “OLD PASSWORD” field; type the current
password, and press [ENTER].
The field changes to “NEW PASSWORD”.
3. Type a new password with 6 to 16 characters, and press
[ENTER].
The field changes to “REPEAT PASSWORD”.
4. Type the new password again, and press [ENTER].
If both entries (Steps 2 and 3) match, the console recalls the
display that was on the screen.
CAUTION
If the backup node for the $$PASSWD file is down when
you change your password, you should contact the system
manager to copy the file from the primary to the backup
node.

CC: 7-2-6
Logging Off the Console
Logging off a console can occur in one of two ways:

D If you are assigned an automatic log off, the system logs you off
if the console remains untouched for the period of time specified
on your User Name Detail screen.
D You can log yourself off the console from the command line.
- To log off the console:
D From the command line, type
LO [ENTER]
The Login screen appears and the user name on the bottom line
of the screen is “NO USER”.

CC: 7-3-1
Section 3:
Configuring Password Security
This section explains the initial configuration process and the following
tasks that a system manager performs to maintain password security:
D Defining primary and backup disks for the $$PASSWD file that is
stored in the Console Configuration folder.
D Defining user names, login names, and login and password
update times.
D Defining plant unit access for each user.
Only a system manager can view and edit the following screens related
to password security:
D User Profile Directory screen
D Plant Unit Access screen
D User Name Detail screen (This screen can also be viewed by a
configuror.)
Initial Password System Configuration
You can receive an RS3 password-secure system in either of two ways:
If your system is being ¼ then follow the directions in ¼
Shipped from the factory with a new “Configuring Factory-shipped

keyboard interface, Password System”, on page 7-3-2.
Upgraded from an existing system with a “Defining Password Security with a

previous version of the RS3 keyboard Configuror’s Key”, on page 7-3-5.
interface,
RS3: Password Security Configuring Password Security

CC: 7-3-2
Configuring Factory-shipped Password System
New password systems from the factory include the following:

D A default $$PASSWD file on the hard disk
D A default configuration for the $$PASSWD file, which has the
primary and backup nodes set to “mynode”.
D A known login name and password.
Using the login name and password that is shipped with this system, a
designated system manager can log in and redefine the necessary
defaults. The following procedures included on this page and the next
allow you to complete this task:
D Log in.
D Configure primary and backup nodes.
D Change user and login names.
D Change password and complete initial configuration.

CC: 7-3-3
Logging in and Configuring Primary and Backup Nodes
- To log in:
LI [ENTER]
2. Enter the login name and password that were shipped with your
system (login name = rs 3 and password = systest).
NOTE: You must type the login name and password exactly as
they are shown above; all login names and passwords are
case-sensitive.
- To configure primary and backup nodes:
CAUTION
The systems that you want to define as primary and backup
should be running during this initial set--up so that the
configuration files can be saved to the appropriate disks.
1. To call up page 3 of the Console Configuration screen, type
CCC [ENTER] [PAGE AHEAD] [PAGE AHEAD]
2. Enter the name of a valid console node in the “Primary Volume
for $$PASSWD” field.
3. Enter the name of another valid console node in the “Backup
Volume for $$PASSWD” field.
4. Save the console configuration, and copy it to all affected
consoles.
For additional details about primary and backup nodes, see
“Defining System-wide Parameters” on page 7-3-10.

CC: 7-3-4
Changing User and Login Names and Completing Configuration
- To change your user and login names:

UND rs 3
The User Name Detail screen appears with the access level
defined as SYSMGR. See “User Name Detail Screen” on
page 7-3-19.
2. Cursor to the “User Name” field; type your name (up to 32
characters), and press [ENTER].
3. Cursor to the “Login” field; change “rs 3” to your login name (4 to
16 characters); ensure that the access level is SYSMGR; and
press [ENTER].
The password is automatically reset to “Cleared”.
4. Type the following to save the $$PASSWD file:
[Ctrl] W
5. Cursor to the command line and log out by typing
LO [ENTER]
- To complete the initial configuration:
LI [ENTER]
2. Enter your new login name.
Because your password is currently “Cleared”, you are
automatically prompted to change it.
3. Cursor to the “OLD PASSWORD” field; and enter “Cleared”.
NOTE: You must type the password exactly as it is shown
above; all passwords are case-sensitive.
4. Enter a new password with 6 to 16 characters.
5. Enter your new password again.
6. Delete the default $$PASSWD files from the nodes that are not
primary or backup.
You are now the system manager and can create plant unit access files
(see page 7-3-14) and add new users (see page 7-3-19).

CC: 7-3-5
Defining Password Security with a Configuror’s Key
If you have an existing RS3, you can still set up and maintain password
management.
Using a configuror’s key in your existing keyboard interface, a

designated system manager can redefine your current system for
password security. The following procedures included on this page and
the next allow you to complete this task:
D Configure primary and backup nodes.
D Add a system manager on the User Name Detail screen.
D Log in to the console.
Configuring Primary and Backup Nodes
- To configure primary and backup nodes:
CAUTION
The systems that you want to define as primary and backup
should be running during this initial set--up so that the
configuration files can be saved to the appropriate disks.
1. To call up page 3 of the Console Configuration screen, type
2. Enter the name of a valid console node in the “Primary Volume
for $$PASSWD” field.
3. Enter the name of another valid console node in the “Backup
Volume for $$PASSWD” field.
4. Save the console configuration, and copy it to all affected
consoles.
For additional details about primary and backup nodes, see
“Defining System-wide Parameters” on page 7-3-10.

CC: 7-3-6
Adding a System Manager
- To add a system manager:

1. As a configuror, call up the User Name Detail screen by typing
UND [ENTER]
The User Name Detail screen appears with the access level
defined as SYSMGR. See “User Name Detail Screen” on
page 7-3-19.
2. Cursor to the “User Name” field; type your name (up to 32
characters), and press [ENTER].
3. Cursor to the “Login” field; type your login name (4 to 16
characters); ensure that the access level is SYSMGR; and press
[ENTER].
The password is automatically reset to “Cleared”.
4. Type the following to save the $$PASSWD file.
[Ctrl] W
5. Reboot the console.
Following this reboot, the console operates as a
password--secure system and the physical keys no longer
function.

CC: 7-3-7
Logging In
- To log in:
LI [ENTER]
2. Enter your new login name.
Because your password is currently “Cleared”, you are
automatically prompted to change it.
3. Cursor to the “OLD PASSWORD” field; and enter “Cleared”.
NOTE: You must type the password exactly as it is shown
above; all passwords are case-sensitive.
4. Enter a new password with 6 to 16 characters.
5. Enter your new password again.
You are now the system manager and can create plant unit access files
(see page 7-3-14) and add new users (see page 7-3-19).

CC: 7-3-8
System-wide Password Parameters
The Console Configuration screen, page 3, allows you to define

system-wide password parameters that determine the following:
D Primary node for storing the $$PASSWD file.
D Backup node for storing the $$PASSWD file.
CAUTION
To minimize the risk of losing access to the $$PASSWD file,
you must configure both primary and backup disks. It is
recommended that you also copy the console
configuration containing the system-wide parameters to a
third console and then configure additional primary and
backup volumes for storing the $$PASSWD file.
Figure 7.3.1 shows Page 3 of the Console Configuration screen, and

Table 7.3.1 describes the fields. This screen can be viewed when no
one is logged on to the console. Only a system manager can edit the
fields on this screen; however, a configuror can edit the screen during
the initial conversion from a keylock to a password system.
When a primary node goes down, the system automatically goes to the
backup node for the $$PASSWD file. After the primary node has been
restored to operation, you must manually reset the console to look at
the primary node.
- To reset the console to its primary node:
1. Call up Page 3 of the Console Configuration screen as explained
in Figure 7.3.1.
2. Cursor to the field that shows the name of the “Current Volume
For $$PASSWD”, and press [ENTER].
NOTE: If a primary or backup volume goes down, the name blinks in

yellow on the Console Configuration screen. If you made any changes
to the $$PASSWD file while either the primary or backup was not
running, you must ensure that you are using the most recent file and
that the files on both nodes match. This requires that a system
manager must delete the old file and copy the latest one to the
appropriate node(s).

CC: 7-3-9
- To access the Console Configuration screen:

CONSOLE CONFIGURATION 12-Mar-93 10:56:05
System-wide Password Management

Title For Login Screen *Fisher-Rosemount Systems, Inc.
Primary Volume For $$PASSWD *Node_88
Backup Volume For $$PASSWD *Node_88
Current Volume For $$PASSWD >Node_88
Figure 7.3.1. Console Configuration Screen—Page 3
Table 7.3.1. Console Configuration Screen Fields—Page 3
Up to 40 alphabetic
Title for Login characters including
Title for the system login screen.
screen
spaces
Primary Volume Primary drive where the $$PASSWD file resides; cannot characters that match a
For $$PASSWD be an SRU.
valid disk drive name.
Backup Volume Backup drive where the $$PASSWD file also is used; characters that match a
For $$PASSWD cannot be an SRU.
Current Volume characters that match a
Drive where the $$PASSWD file is currently being stored.
For $$PASSWD
NOTE: A primary or backup name that is blinking in yellow indicates that this node has been out of service
at some time since configuration.

CC: 7-3-10
Defining System-wide Parameters
The first step in setting up system-wide password management is to

define parameters on page 3 of the Console Configuration screen.
CAUTION
You must define the “Primary Volume for $$PASSWD” and
“Backup Volume for $$PASSWD”. The other fields on this
screen have default values that you do not have to change.
- To define the system-wide password parameters for each
console:
1. Log in as a system manager.
2. To call up page 3 of the console configuration screen, type
3. Cursor to the “Primary Volume for $$PASSWD” field, and enter
the name of a valid console node that you want to use for storing
the $$PASSWD file.
4. Cursor to the “Backup Volume for $$PASSWD” field, and enter
the name of a valid console node that you want to serve as a
backup for storing the $$PASSWD file.

CC: 7-3-11
Saving the Console Configuration
- To save the Console Configuration:

1. To call up the Disk Activity screen, type
DD: [ENTER]
2. Cursor to the Console Configuration folder, and press [SELECT].
3. Cursor to the file containing the console configuration you want
to save, and press [ENTER].
The Disk Activity screen appears with Disk Console Save in the
“Operation” field.
4. Cursor to the “Config Types” field; press [NEXT OPTION] until
“All” appears, and then press [ENTER].
5. Cursor to the “Press Enter to Begin” field, and press [ENTER].

CC: 7-3-12
User Profile Directory
The User Profile Directory screen shown in Figure 7.3.2 allows a

system manager to view all users that have been defined in the system
and to move to the User Name Detail or Plant Unit Access screens for a
selected user. This screen can be viewed only by a system manager
who is logged in.
The fields on this screen are a subset of those on the User Name Detail
screen and include the following, which are described in Table 7.3.2.
The User Profile Directory screen has two selectable areas for each
user:
D User number through the access level fields
D PUA field
- To access the User Profile Directory:
UPD [ENTER]
2. To view additional users in the User Profile Directory, press
[PAGE FORWARD] or [PAGE BACKWARD].
- To move to the Plant Unit Access screen from the User Profile
Directory:
1. Locate the user whose plant unit access screen you want to view,
and position the cursor anywhere on the PUA field.
2. Press [SELECT].
- To move to the User Name Detail screen from the User Profile
Directory:
1. Locate the user whose User Name Detail screen you want to
view, and position the cursor anywhere between the user number
and the access level fields.
2. Press [SELECT].

CC: 7-3-13
- To access the User Profile Directory screen:

UPD [ENTER]
- To move to another part of the
User Profile Directory: - To move through the list of users in the User
D Position cursor here, and type Profile Directory:
user number [ENTER] D Press [PAGE FORWARD] or [PAGE BACKWARD]
User Profile Directory 12-Mar-93 11:03:52
Login User Name Access PUA Filename

26 oper 26 OPER
27 oper 27 OPER OperPUA
28 oper 28 OPER
29 johnp John Powers CONFIG Configu PUA
29 oper 29 OPER
30 oper 30 temp OPER
31 dave Dave Owen CONFIG ConfigPUA
32 kents Kent Smith OPER
33 annl Ann London OPER
34 kenta Kent Anders SYSMGR SysMgrPUA
35 donm Don Miller OPER
36 joew Joe Wilson OPER
37
38
39
- To move to the User Detail screen for a - To move to the Plant Unit Access
highlighted user: screen for a highlighted user:
D Place the cursor anywhere between the user D Place the cursor anywhere on the
number and the access level, and press PUA field, and press [SELECT].
[SELECT].
Figure 7.3.2. User Profile Directory
Table 7.3.2. User Profile Directory Fields
Field Description
(Column 1) User number
Login Name that user enters when logging in
User Name User’s full name
Access Defines level of system access (OPER, SUPER, CONFIG, SYSMGR, RCPM, NONE)
Name of file that lists the plant units that this user can access.
PUA filename
See “Defining Plant Unit Access” on page 7-3-14.

CC: 7-3-14
Plant Unit Access
The Plant Unit Access screen allows a system manager to create the
files that define which plant units a user can operate.
Each console has its own plant unit configuration, which is combined
with the plant unit access configuration to allow different operators to
have control of different parts of a plant.
The plant-unit access (PUA) information is stored in the $$PASSWD file.

The same filename can be assigned to multiple users; however, no
more than 991 files (one for each user) can be defined.
NOTE: A PUA filename must have been configured on the Plant Unit
Access screen before you can enter it on the User Name Detail screen.
The suggested procedure, therefore, is to create the necessary PUA
filenames before you add users to the password system.

CC: 7-3-15
Plant Unit Access and Plant Unit Configuration
The Plant Unit Access file provides the same basic functionality as the
Plant Unit Configuration:
D Each console has a Plant Unit Configuration (PUC) that specifies
which plant units send alarms to that console.
D Each operator has a Plant Unit Access (PUA) filename that
specifies which plant units send alarms to that operator.
The Plant Unit Configuration and Plant Unit Access information must
both show ownership of a particular plant unit before an operator can
modify blocks or acknowledge alarms for that plant unit:
If the operator and the console then this operator at this console can
PUA specifies ¼ PUC specifies ¼ see and ack alarms for ¼
1 -- 10 1 -- 30 1 -- 10
15 -- 30 1 -- 30 15 -- 30
10 -- 40 15 -- 30 15 -- 30
CAUTION
The Plant Unit Configuration and Plant Unit Access
information work together to define which alarms can be
acknowledged by a particular operator at a particular
console. If an alarm from plant unit 15 (based on the first
example above) is on the banner line when the operator
logs in, that operator cannot acknowledge the alarm on the
banner line. That acknowledgement must be done by an
operator at a console where both the PUC and operator
PUA include plant unit 15.

CC: 7-3-16
Defining Plant Unit Access
Figure 7.3.3 and Table 7.3.3 explain the fields on this screen that can be
viewed and changed only by a system manager. An asterisk to the right
of a plant unit number indicates that this plant unit has been enabled for
a user or users who have been associated with this file.
- To define a new plant-unit access file:
1. With system manager access, call up the Plant Unit Access
screen, by typing
PUA [ENTER]
The screen appears a shown in Figure 7.3.3.
2. Cursor to the “PUA filename” field; enter a valid filename, and
press [ENTER].
3. Configure the plant units that users with this PUA filename can
access by doing one of the following:
— Cursor to each plant unit that this user should be able to
access, and press [ENTER].
— Cursor to the “Set range” field, enter two numbers separated
by a comma, and then press ENTER].
— Clear an enabled field by pressing [ENTER] again on a plant
unit number or by entering values in the “Clear range” field.
4. To save the $$PASSWD file after you enter appropriate values in
all necessary fields, type
[Ctrl] W

CC: 7-3-17
- To access the Plant Unit Access screen:

PUA [filename] [ENTER]
Plant Unit Access 15-Mar-93 13:20:25
PUA Filename > OperPUA

1 17 33 49 65 81 97 113 129 145 161 177 193 209 225 241
2 18 34 50 66 82 98 114 130 146 162 178 194 210 226 242
3 19 35 51 67 83 99 115 131 147 163 179 195 211 227 243
4 20 36 52 68 84 100 116 132 148 164 180 196 212 228 244
5 21 37 53 69 85 101 117 133 149 165 181 197 213 229 245
6 22 38 54 70 86 102 118 134 150 166 182 198 214 230 246
7 23 39 55 71 87 103 119 135 151 167 183 199 215 231 247
8* 24 40 56 72 88 104 120 136 152 168 184 200 216 232 248
9 25 41 57 73 89* 105 121 137 153 169 185 201 217 233 249
10 26 42 58 74 90 106 122 138 154 170 186 202 218 234 250
11 27 43 59 75 91 107 123 139 155 171 187 203 219 235 251
12 28 44 60 76 92 108 124 140 156 172 188 204 220 236 252
13 29 45 61 77 93 109 125 141 157 173 189 205 221 237 253
14 30 46 62 78 94 110* 126 142 158 174 190 206 222 238 254
15 31 47 63 79 95 111 127 143 159 175 191 207 223 239 255
16 32 48 64 80 96 112 128 144 160 176 192 208 224 240
Set Range > Clear Range >
- To move through plant unit access files in the

order in which they were created:
Indicates that the user who is assigned this
PUA filename can access Units 8, 89, and 110. D Press [PAGE FORWARD] or [PAGE BACKWARD]
Figure 7.3.3. Plant Unit Access Screen
Table 7.3.3. Plant Unit Access Screen
File name associated with a particular user to define

which plant units that user can access. Up to 9 alphabetic
PUA filename
characters
A maximum of 991 filenames can be defined.
Press [ENTER] to toggle

Plant units Asterisks indicate which units this user can access.
asterisk on and off.
Allows you to specify a range of plant units to enable for

Set range 1 to 255*
this user.
Allows you to specify a range of plant units to disable

Clear range 1 to 255*
for this user.
* To specify a range of values, enter two numbers separated by a comma and press [ENTER]: “3,55”
[ENTER].

CC: 7-3-18
Changing Plant Unit Access Definitions
Plant unit access definitions cannot be deleted, but the filename and
plant unit assignments can be changed.
- To change information in an existing Plant Unit Access file:
1. With system manager access, call up the Plant Unit Access
screen and do one of the following:
— On the command line, type
PUA filename [ENTER]
— In the User Profile Directory, cursor to the name of the file you
want to change, and press [SELECT].
2. To clear any previously enabled plant units, do one of the
following:
— Cursor to a plant unit marked with an asterisk that you do not
want this user to access, and press [ENTER].
— Cursor to the “Clear range” field; enter a single number or two
numbers separated by a comma, and then press ENTER].
3. To enable the appropriate fields, do one of the following:
— Cursor to each plant unit that this user should be able to
access, and press [ENTER].
— Cursor to the “Set range” field; enter a single number or two
numbers separated by a comma, and then press ENTER].
4. To cancel changes and recall the original plant unit access
configuration, type
[Ctrl] R
[Ctrl] W

CC: 7-3-19
User Name Detail Screen
The User Name Detail screen shown in Figure 7.3.4 allows a system
manager to add users to the password management system. This
screen can be edited only when a system manager is logged in, but it
can be viewed by a configuror.
- To access the User Name Detail screen:

UND [login_name] [ENTER]
User Name Detail 12-Mar-93 10:41:34
Number *1 Fisher-Rosemount Systems, Inc.

User Name *Joe Brown
Login Name *Joeb
Access *SYSMGR GLOBAL SYSTEM PARAMETERS
PUA Filename *SYSMGRPUA Password
Login/Logout Times Change Required Every *10 Days
Days *any Change not allowed for *0 Days
Start/End Time *00:00 *00:00 hh:mm Inactive User Logout *00:00 hh:mm
Inactive User Logout *00:00 hh:mm NEW SYSMGR:
Password *Cleared Raise to SYSMGR: (press ENTER)
Last Change 02-Jul-93 11:04:10
Next Change 12-Jul-93 11:04:10
- To move through user name detail screens in

numerical order:
D Press [PAGE FORWARD] or [PAGE BACKWARD]
Figure 7.3.4. User Name Detail Screen

CC: 7-3-20
Table 7.3.4. User Name Detail Screen
Field Description Allowable Entries *
Number User number that is automatically assigned when a user 1 to 991

is added; a value can be entered in this field to call up
the User Name Detail screen for the user who was
assigned that particular number.
User Name User’s full name Up to 32 alphanumeric

characters
(spaces are allowed)
Login Name Name that user enters when logging into the console. 4 to 16 alphanumeric
characters
(spaces allowed)
Access Defines level of system access NONE, OPER, SUPER,

RCPM, CONF, SYSMGR
PUA Filename Name of file that lists the plant units that this user can Up to nine alphanumeric
access. characters that represent
See “Defining Plant Unit Access” on page 7-3-14. an existing file.
Login/Logout Times
Days Indicates the days of the week that this user is allowed to Mon, Tue, Wed, Thu, Fri,
log in. You can indicate the days in a list separated by Sat, Sun, any
commas (Mon, Wed, Fri) or as a range (Mon--Thu); or
you can press [ENTER] to indicate “any”.
Start/End Time Indicates the hours during which the user is allowed to 00:00 to 23:59
log in; this assumes that the user works the same hours
each day.
Inactive User Indicates how long the console can remain untouched 00:01 to 23:59
Logout before the user is automatically logged out.
00:00 means that a user is never logged out. The default
is based on the GLOBAL SYSTEM PARAMETER,
Inactive User Logout on the right-hand side of this
screen.
Password Indicates the status of this user’s password; one of the Canceled, Cleared
following appears in the field:
D “Valid Password” indicates that this user has
defined a password.
D “Cleared” indicates that this is a new user who has
never defined a password or one who has
forgotten a password and needs to define a new
one.
D “Canceled” indicates that this user is no longer
allowed to log in.
Last Change Indicates last time this user changed his/her password. Display only
* Bold indicates the default value.

CC: 7-3-21
Table 7.3.4. User Name Detail Screen (continued)
Field Description Allowable Entries *
Next Change Indicates when this user must change his/her password; Display only
this field appears only if value in “Change Required
Every” field is greater than 0.
GLOBAL SYSTEM PARAMETERS
Password
Change Indicates how often passwords must be changed. The 0 to 365 days
Required Every default, 0, indicates that passwords never have to be
changed.
Change not Indicates how long any password must be in effect 0 to 365 days
allowed for before it can be changed; that is, another password
change is not allowed for this period of time. This value
cannot be greater than the “Change Required Every”
field.
Inactive User Indicates how long the console can remain untouched 0:01 to 23:59
Logout before the user is automatically logged out.
Default value, 00:00, means that a user is never logged
out. The value entered in this field determines the
default for all users.
NEW SYSMGR The following fields are used only when a configuror must See “Changing Configuror
be redefined as a system manager. to System Manager” on
D Raise to SYSMGR: (press ENTER) page 7-3-24 for additional
information.
D Additional user
D Password
* Bold indicates the default value.

CC: 7-3-22
Adding Users to the Password System
Only a system manager can add users to the system from the User
Name Detail screen. The information on this screen is stored in the
$$PASSWD file in the Console Configuration folder.
You define the following fields for each user:

D User Name
D Login
D Access level: OPERATOR, SUPER, RCPM, CONFIG, or
SYSMGR
D Optional name of file containing plant unit access
All other fields on the User Name Detail screen have default values and,
therefore, do not require additional entries.
- To add a new user to the system:
1. With system manager access, call up the User Name Detail
screen, by typing
UND [ENTER]
The User Name Detail screen, and the next available user
number is automatically assigned.
2. Cursor to the “User Name” field, and enter up to 32 characters.
3. Cursor to the “Login Name” field, and enter between 4 and 16
characters that this user can use to log in.
4. Cursor to the “Access” field; press [NEXT OPTION] until the
appropriate access level appears; and then press [ENTER].
5. Cursor to the “PUA Filename” field, and enter up to 9 characters
that define the name of a file containing this user’s plant-unit
access privileges.
6. Cursor to other fields that you want to define, and enter
appropriate values as listed in Table 7.3.4.
[Ctrl] W

CC: 7-3-23
Changing User Name Profiles
Once assigned a user number, a user can never be specifically deleted

from the system. You can deny someone future access to the system,
by setting the password to “Canceled”, or you can change a user name
to reassign a particular user number to someone else.
- To change information on the User Detail screen:
1. With system manager access, call up the User Name Detail
screen and do one of the following:
— On the command line, type
UND login_name [ENTER]
— In the User Profile Directory, cursor to the name of the user
whose profile you want to change, and press [SELECT].
2. Cursor to the fields as explained on page 7-3-22, and enter the
appropriate values for fields that you want to modify.
3. To remove changes and recall the original user profile, type
[Ctrl] R
[Ctrl] W

CC: 7-3-24
Changing a Configuror to a System Manager
If an existing system manager is unavailable, it may be necessary to

assign system manager privileges to another user. The access level of
an existing configuror can be raised to a system manager under the
following conditions:
D The configuror is currently logged in.
D Another configuror or supervisor is available to approve the
change.
Such a change is only temporary unless as a system manager, the

configuror changes the access level on his or her user name detail
screen and saves that configuration to the $$PASSWD file. If the
change is not permanently made to the $$PASSWD file, the system
manager status is valid only as long as the configuror is logged in.
User Name Detail 12-Mar-93 10:41:34
Number *1 Fisher-Rosemount Systems, Inc.

User Name *Joe Brown
Login Name *Joeb
Access *SYSMGR GLOBAL SYSTEM PARAMETERS
PUA Filename *SYSMGRPUA Password
Login/Logout Times Change Required Every *0 Days
Days *any Change not allowed for *0 Days
Start/End Time *00:00 *00:00 hh:mm Inactive User Logout *00:00 hh:mm
Inactive User Logout *00:00 hh:mm NEW SYSMGR:
Password *Valid Password Raise to SYSMGR: (press ENTER)
Last Change 02-Jul-93 11:04:10
NEW SYSMGR:
Raise to SYSMGR: (press ENTER) Cursor to “Raise to
SYSMGR” field, and
Additional User > press [ENTER].
Password
Figure 7.3.5. Changing Configuror to System Manager

CC: 7-3-25
- To change a configuror to a system manager:

1. As a configuror, log in to the system and call up the User Name
Detail screen, by typing
UND (your_login_ name) [ENTER]
NOTE: You can raise yourself to a system manager from any
User Name Detail screen.
2. With another configuror or supervisor immediately available,
cursor to the “Raise to SYSMGR: (press ENTER)” field; and
press [ENTER].
3. Cursor to the “Additional User” field, and allow the other
configuror or supervisor to enter his or her name.
4. Cursor to the “Password” field, and allow the other configuror or
supervisor to enter his or her password.
The configuror who was originally logged in now has the access
level and privileges of a system manager until he or she logs off.
- To make the system manager access level permanent:
1. Cursor to the “Access Level” field on the User Name Detail
screen for the new system manager.
2. Press [NEXT OPTION] until SYSMGR appears, and then press
[ENTER].
3. Cursor to any other fields that need updating, and make the
necessary changes.
4. To save the $$PASSWD file after updating the appropriate fields,
type
[Ctrl] W
The configuror who was originally logged in now has permanent
system manager status.
NOTE: If you move to the User Name Detail screen for the configuror
who has been raised to a SYSMGR, the access level is highlighted in
yellow. The access level for such a configuror is also highlighted in
yellow on the User Profile Directory.

CC: 7-4-1
Section 4:
Password Security Hints and Troubleshooting
This section describes some security situations and explains how to

handle them using the Version 18 password management system. Five
scenarios are described with suggested solutions and preventive
measures.
The following general guidelines are suggested to maintain the integrity

of your password management system.
D Configure more than one set of primary and backup nodes for
storing the $$PASSWD file.
D Make regular backups of files in your console configuration
folder, especially the $$PASSWD file.
D Store a spare configuror’s key and standard keyboard interface
(KBI) in a restricted area; this keyboard can then be used if no
other means of access is available.
RS3: Password Security Password Security Hints and Troubleshooting

CC: 7-4-2
Scenario 1: Handling Primary and Backup Nodes
Situation:
On a system using only secure keyboard interfaces, the primary and
backup nodes disappear.
Result:
The password file can no longer be accessed and no one can log on
to the system. If no one is currently logged in and only one set of
primary and backup nodes were defined, nothing can be done.
Preventive Measures:
To minimize the risk of this situation ever occurring, do one of the
following:
- Maintain a tape backup of the latest $$PASSWD file.
- Define a second set of primary and backup nodes.
CAUTION
If you define a second set of primary and backup nodes,
you must ensure that all $$PASSWD files are always
identical.
- Maintain a spare standard KBI with a configuror’s key.
1. See Scenario 2, 7-4-3 for the initial steps in correcting the
problem.
2. When everything is backed up and running, remove the standard
KBI and replace it with the secure keyboard interface.
Correction:
If and only if a configuror or system manager is logged in, he or she
can replace the file from tape.
- To reload tape:
1. If a configuror is logged in, raise the configuror to a system
manager. (See Section 3, 7-3-24).
2. Replace the $$PASSWD file from tape, and then reconfigure the
primary and backup nodes.
NOTE: If a console using the standard KBI has power cycled and the
primary and backup volumes cannot be found, then this console will
come up as a keylock system. Using a secure KBI will not generate this
problem although you will not be able to log in.

CC: 7-4-3
Scenario 2: Using Passwords with Keylock and Secure

Interfaces
Situation:
A system has both a keylock and secure keyboard interface. How
can this system be made as secure as possible?
Solution:
You can configure standard KBI keyboards to operate with password
security.
- To configure a system with both keylock and secure keyboard
interfaces.
1. On page 3 of the Console Configuration screen, specify consoles
with the secure keyboard interface as primary and backup nodes.
Note: You may need to perform this configuration using a
configuror’s key on a system with the standard KBI.
2. Ensure that all consoles (including those with a standard KBI)
specify primary and backup nodes that use the secure keyboard.
3. On the “User Name Detail” screen, define a system manager by
entering at least one login name (the first name entered is always
defined with system manager access).
4. Reboot all consoles.
All consoles are now set up for login access only.

CC: 7-4-4
Scenario 3: Using Passwords with a Standard KBI
Situation:
A system has only keyboards with the standard KBI. How can you
use this system as a secure password system?
Solution:
You can configure the standard KBI to use passwords instead of
keys.
- To configure a standard KBI for password security:
1. Using the configuror’s key, modify page 3 of the Console
Configuration screen to specify primary and backup nodes for the
$$PASSWD file.
2. On the “User Name Detail” screen, define a system manager by
entering at least one login name (the first name entered is always
defined with system manager access).
3. To save the $$PASSWD on the primary and backup nodes, type
[Ctrl] w
4. Configure all consoles with these same primary and backup
nodes, and then reboot each console.
The system returns with a login screen, and the access level
is set to ‘NO USER’. You can now log in with SYSMGR
access, change your password, add additional users, etc.

CC: 7-4-5
Scenario 4: Using Key and Password Access
Situation:
A system uses key access on some consoles and password access
on others. How can this system be made as secure as possible?
Result:
Very little can be done to provide limited access when keys are still
available.
Solution:
You have two possible means of providing better security.
- To configure all keyboards to serve as a password system:
D See Scenario 2, 7-4-3.
- To restrict use of the consoles with standard KBIs:
1. Use the consoles with a standard KBI in restricted areas where
fewer people have access to them.
2. Use the password consoles in more generally accessible areas.

CC: 7-4-6
Scenario 5: Loss of $$PASSWD File
Situation:
The $$PASSWD file is lost.
Solution:
Recovery of the $$PASSWD file depends on the overall system
configuration:
- To retrieve the $$PASSWD file in a system in which only secure
keyboard interfaces are used and a system manger was logged
in:
D Restore the file from tape as explained in Scenario 1, 7-4-2.
- To retrieve the $$PASSWD file in a system in which only
standard KBIs are used:
1. Reboot the console.
2. Insert the configuror’s key.
3. Restore the file from tape as explained in Scenario 1, 7-4-2.

CC: 7-4-7
Scenario 6: Console Configuration File Not Found
Situation:
A console has power cycled and cannot find its console
configuration file.
D If this console is using a standard KBI, it will come up as a
keylock system.
D If this console is using a secure KBI and was not configured as a
primary or backup volume for the $$PASSWD file, no one can log
in.
NOTE: To determine if the console configuration file cannot be
found, check page one of the Console Configuration screen to see if
the name of the console configuration file appears in yellow.
Solution:
- To retrieve the $$PASSWD file:
1. Log in as system manager to another console and copy the
$$PASSWD file to the console that could not find its console
configuration file.
2. If using a secure keyboard interface, log in to the console which
will then use this new copy of the $$PASSWD file;
or
If using a standard KBI, reboot the console and then log in.
3. Load the console with the correct console configuration file.

CC: Index-1
RS3t
Index
Symbols display, 6-4-6– 6-4-8

display configurations, 6-4-2– 6-4-5
enabling, 6-4-9
$$PASSWD file, 7-4-1 Alarm Log Display screen, 6-4-6– 6-4-8
lost, 7-4-6, 7-4-7 alarm management
hints, 6-7-1
troubleshooting, 6-7-1
A alarm messages
managing message load, 6-1-1
reducing message load, 6-1-1, 6-1-4– 6-1-5,
access levels, 7-1-2 6-1-7
changes for password security, 7-1-4 alarm object, process graphics, 2-2-48– 2-2-52,
accumulate object, reports, 3-4-22, 3-4-25, 3-4-31 2-2-85
accumulators, reports, 3-4-20, 3-4-31 alarm summary mode, 6-5-12
adding users to password system, 7-3-22 alarm, storage in console RAM, 6-2-1
address object, reports, 3-4-16 alternate disk access, 1-1-12–1-1-13
Advance request rate, configuring, 1-1-30 arc object
advisory process alarms, 6-3-2 characteristics, 2-2-16
alarm fill option, 2-2-21– 2-2-22
priority, 6-5-11 process graphics, 2-2-12
regeneration, 6-5-10 archive trend data, 4-4-1– 4-4-3
separating and sorting at a console, 6-3-1– attributes, message pairs, 1-5-4– 1-5-5
6-3-7, 6-3-8– 6-3-12
suppression, 6-3-6
type priority, 6-5-11
types, 6-3-2
B
alarm annunciation on graphics, 2-2-85
Alarm Annunciation screen, 1-4-3 backup nodes, $$PASSWD file, 7-3-3, 7-3-5, 7-3-8,
calling up screen, 1-4-2– 1-4-6 7-4-2
configuring alarm annunciation, 1-4-3 backup trend file, 4-4-2
configuring callup button, 1-4-2 ban1 object, reports, 3-4-13
alarm area, 6-3-3– 6-3-6 ban2 object, reports, 3-4-13
configuring, 6-1-1– 6-1-2, 6-3-3 banners, reports, 3-4-13
disabling, 6-3-5 batch alarms, 6-3-2
enabling, 6-3-5 batch information, process graphics, 2-2-83– 2-2-84
alarm banner mode, 6-5-11 batch task data, process graphics, 2-2-83– 2-2-84
alarm broadcast configuration, 6-1-2– 6-1-4 bface object, process graphics, 2-2-83– 2-2-84
restoring, 6-1-5 blkdes object, process graphics, 2-2-25– 2-2-27
saving, 6-1-5 block information objects
Alarm Configuration screen, 6-5-2– 6-5-3 blkdes object, 2-2-25– 2-2-27
alarm display mode, 6-5-12– 6-5-13 disc object, 2-2-28– 2-2-30, 2-2-53
alarm list hdev object, 2-2-31– 2-2-34
properties configuration, 6-3-8 link object, 2-2-28– 2-2-30
size, 6-3-8 mode object, 2-2-25– 2-2-27
Alarm List Configuration screen, 6-3-8– 6-3-10 tag object, 2-2-25– 2-2-27
alarm log, 6-4-1– 6-4-9 ticbar object, 2-2-31– 2-2-32
disabling, 6-4-9 units object, 2-2-28– 2-2-30
RS3: Console Configuration Manual Index

CC: Index-2
block information reports Configure Alarm Broadcast screen, 6-1-2– 6-1-3

address, 3-4-16 Configure Character screen, pixel graphics, 2-2-87–
descriptor, 3-4-17 2-2-88
function, 3-4-18 configuring
mode, 3-4-19 block print function, 1-6-1– 1-6-3
tag, 3-4-15 callup and display buttons, 1-4-1– 1-4-10
units, 3-4-20 color, 1-2-1– 1-2-3
values, 3-4-21 console operations, 1-1-1–1-1-12, 1-1-15–1-1-31
block links, limits, 2-3-2 console operations hints, 1-1-28–1-1-31
Block Print function, 1-6-1– 1-6-3 message pairs, 1-5-1– 1-5-9
Block Print Setup screen, 1-6-2 operating displays, 1-3-1– 1-3-8
block tags (16 character), configuring, password security, 7-3-1–7-3-7
1-1-15–1-1-22 configuror, changing to system manager,
block variable information 7-3-24–7-3-25
displayed in character form, 2-2-28 console configuration
displayed in graphic form, 2-2-32 not found, 7-4-7
process graphics, 2-2-28– 2-2-31 saving, 7-3-11
block variables, trending, 4-1-2, 4-1-5 Console Configuration screen, 1-1-3–1-1-5
bottom operation, 2-2-58 changes for password security, 7-1-4
box object page 3, 7-3-8–7-3-10
characteristics, 2-2-16 console lists, reports, 3-4-34, 3-4-35
fill option, 2-2-21– 2-2-22 console operations
process graphics, 2-2-10, 2-2-16, 2-2-21– configuring, 1-1-1–1-1-12, 1-1-15–1-1-31
2-2-24 configuring hints, 1-1-28–1-1-31
console screen display coordinates, 2-2-71
console trending capabilities, 4-1-2– 4-1-3
C coordinates
console screen display, 2-2-71
process graphics fabric, 2-2-71
CAB--type Plant Configuration file, 6-1-5 copying a process graphic, 2-2-82
calculations, performed in reports, 3-4-22, 3-4-25 copying objects
calling up a process graphic, 2-1-4– 2-1-5 process graphics, 2-2-56
callup buttons, keyboard, 1-4-1 reports, 3-6-3
Callup Buttons screen, 1-4-7 creating a process graphic, 2-1-4
Changing a Configuror to a System Manager, 7-3-24 creating objects, 2-1-1– 2-1-3
changing configuror to system manager, criteria configurations, 6-4-5
7-3-24–7-3-25 critical process alarms, 6-3-2
changing password, 7-2-4– 7-2-5
character graphics
configuring user--defined characters, 2-2-86
conversion to pixel graphics, 2-2-86
D
circle object
characteristics, 2-2-16 data entry fields, process graphics, 2-2-53
fill option, 2-2-21– 2-2-22 date object, reports, 3-4-33
process graphics, 2-2-9, 2-2-16, 2-2-21– delete operation, process graphics, 2-2-57
2-2-24 descriptor objects, reports, 3-4-17
color, 1-2-1– 1-2-8 designing a report, 3-1-1, 3-3-1, 3-3-3
Color Configuration screen, 1-2-3– 1-2-7 dimensions of a report, 3-3-2
combining objects, 2-2-60– 2-2-64 disable trending command, 4-1-6
command, configuring, 1-4-2 disabling an alarm area, 6-3-5
command console, configuring, 1-1-3–1-1-5, disc object, process graphics, 2-2-28– 2-2-30,
1-1-12–1-1-13 2-2-53
commands, 5-1-1 disk and tape activities, changes for password
changes for password security, 7-1-3 security, 7-1-5
comment object, reports, 3-4-14 disk event messages, 6-3-2
conditional display, process graphics, 2-2-54– display
2-2-55 alarms, 2-2-48
configuration mode hiding parts of object, 2-2-79– 2-2-80
calling up, 2-1-6 trend group, 4-3-5– 4-3-8
display, 2-1-3 display buttons, 1-4-1, 1-4-8
objects, 2-2-8 Display Buttons screen, 1-4-8

CC: Index-3
display of objects, appearance dependent on grouping objects

discrete block var., 2-2-54 area operation, 2-2-61– 2-2-62
display targets, 2-2-77– 2-2-78 description, 2-2-60– 2-2-64
duplicate process graphics, maintaining, 2-3-9 group operation, 2-2-63
join operation, 2-2-63
merge operation, 2-2-66
E split operation, 2-2-69
undo operation, 2-2-70
edit object menu, 2-2-4

editing the body of a report, 3-4-9
enable trending command, 4-1-6
H
enabling and disabling alarm areas, 6-3-5
event list, size, 6-3-8 Hardware alarms, 6-3-2
events, disk switch, 1-1-12 hdev object, process graphics, 2-2-31– 2-2-34
hiding parts of the display, 2-2-79
hints
alarm management, 6-7-1
F configuring trending, 4-5-1
reports, 3-6-1, 3-6-3
fabric, 2-1-1 using commands, 5-2-1
process graphic coordinates, 2-2-71
process graphic description, 2-1-1
viewing, 2-2-72 I
faceplates
disc object, 2-2-53
Group Display screens, 1-3-2– 1-3-3 icon object, process graphics
group object, 2-2-37– 2-2-39 alarm annunciation, 2-2-85
overview object, 2-2-37– 2-2-39 hiding display, 2-2-79– 2-2-80
process graphics, 2-2-37– 2-2-39 inhibit alarms, 6-1-7
unit object, 2-2-37– 2-2-39
with message pairs, 1-5-1
field refresh rate J
configuring, 1-1-32
limits, 1-1-32, 2-3-2 joining objects, 2-2-63
process graphics, 2-3-8
file structure, reports, 3-2-1– 3-2-8
fill object, process graphics, 2-2-21
formatting, 3-3-3 K
function object, reports, 3-4-18
funnel block, 2-3-4 keyboard, 1-4-1
keyboard interface, 7-1-1
keylock interface, with passwords, 7-4-3, 7-4-5
G
general (graphic) alternate disk, 1-1-12
L
generate object, reports, 3-4-37
generating a report layout, report sample, 3-3-1
from the Report Configuration screen, 3-4-42 library symbols, 2-2-17– 2-2-18
manually, 3-4-42 line object, process graphics, 2-2-13– 2-2-14
using alarms and events, 3-4-41 Link Count field, 2-3-3
using time and date, 3-4-39 Link Editor, 2-3-9, 2-3-10
graphic fabric, limits, 2-3-2 screen, 2-3-10
graphic file, limits, 2-3-2 link object, process graphics, 2-2-28– 2-2-30
graphic links, changing, 2-3-9 links, editing, 2-3-9
Graphics Link Editor, 2-3-9– 2-3-11 list object, reports, 3-4-35
graphics performance, optimizing, 2-3-1– 2-3-4 Log Display Configuration screen, 6-4-2– 6-4-3
Group Directory screen, 1-3-2 log display configurations, 6-4-2– 6-4-5
Group Display screen, 1-3-2– 1-3-3 logging off console, 7-2-6
group object, process graphics, 2-2-37– 2-2-39 logging on to console, 7-2-2

CC: Index-4
Login screen, 7-2-2 removing from group, 2-2-69

loss of $$PASSWD file, 7-4-6, 7-4-7 splitting from a group, 2-2-69
stacking, 2-2-58– 2-2-59
which display faceplates, 2-2-37– 2-2-39
M operating displays, 1-3-1– 1-3-8
Operator Change Log, 1-1-26
operator change log, changes for password security,
masking tags, 1-1-15–1-1-16, 1-1-19–1-1-22 7-1-6
Master Color Selection screen, 1-2-2 optimizing graphics performance, 2-3-1– 2-3-4
Menu Command Console screen, 1-1-2 origin point, process graphics, 2-2-72
merging objects, 2-2-66, 2-3-5 overlay alternate disk, 1-1-12
message pairs, 1-5-1– 1-5-9 Overview Directory screen, 1-3-7
mode object Overview Display screen, 1-3-8
process graphics, 2-2-25– 2-2-27 overview object, process graphics, 2-2-37– 2-2-39
reports, 3-4-19
modem interface to printer, 1-1-29
moving objects P
process graphics, 2-2-56
reports, 3-6-3 pageback object, process graphic, 2-2-73– 2-2-79
multinational characters, 1-7-1 pagefrwd object, process graphic, 2-2-73– 2-2-79
Multitube callup and display buttons, 1-4-1 panning limits, process graphics, 2-2-72
Multitube Command Console password
alternate disk access, 1-1-12–1-1-13 adding users to system, 7-3-22
control switching, 1-1-14 changing, 7-2-4– 7-2-5
trending, 4-1-3 with keylock and secure interfaces, 7-4-3
Multitube Configuration screen with keylock interface, 7-4-4
alternate disk access, 1-1-12–1-1-13 password file, 7-4-1
control switching, 1-1-14 lost, 7-4-6, 7-4-7
password security, configuring, 7-3-1–7-3-7
password system, accessing, 7-2-1
N pictorial representation of plant conditions, 2-1-1
pixel graphics, 2-2-86– 2-2-87
Plant Configuration file (type CAB), 6-1-5
newpage object, reports, 3-3-3, 3-4-11 Plant Status screen, 1-1-24
node ownership plant unit access, 7-3-14–7-3-18
configuration, 1-1-23–1-1-24 plant unit configuration, with plant unit access,
determining alarm storage, 6-2-1 7-3-15
non--English characters, 1-5-3 Plant Unit Configuration screen, 1-1-25
plant units
configuration, 1-1-25–1-1-26
O console alarm storage, 6-2-1
ownership, 1-1-25
preconfigured process graphics, 2-3-7
object menu, process graphics, 2-2-3 primary and backup nodes, 7-4-2
object overhead, limits, 2-3-2 $$PASSWD file, 7-4-2
object types configuring, 7-3-3, 7-3-5
process graphics, 2-2-5 resetting, 7-3-8
reports, 3-4-6 print object, reports, 3-4-10
objects printer configuration tips, 1-1-29
appearance dependent on discrete block var., printing
2-2-54– 2-2-55 report configuration, 3-4-11
calling up another part of same display, 2-2-75– report when generated, 3-4-43
2-2-77 process graphic
calling up other displays, 2-2-74 accessing, 2-1-3
copying, 2-2-56 area, 2-2-61– 2-2-62
deleting, 2-2-57 block variable information
displaying batch task data, 2-2-83– 2-2-84 character form, 2-2-28
grouping, 2-2-60– 2-2-64 graphic form, 2-2-31
joining objects, 2-2-63 text form, 2-2-28– 2-2-29
merging, 2-2-66 bottom, 2-2-58
moving, 2-2-56 calling up, 2-1-6

CC: Index-5
configuration mode, 2-1-6 configuring text, 3-4-12

configuration tools, 2-2-56– 2-2-66 configuring time and date, 3-4-32, 3-4-33
copying graphic file, 2-2-82 configuring trend information, 3-4-26, 3-4-31
copying objects, 2-2-56 designing, 3-3-1, 3-3-3
creating graphic file, 2-1-4 dimensions, 3-3-2
creating object, 2-2-2– 2-2-4 editing, 3-4-9
creating shapes, 2-2-21– 2-2-22 file structure, 3-2-1– 3-2-8
deleting objects, 2-2-57 formatting for printing, 3-3-3
description, 2-1-1 generating, 3-4-39, 3-4-43
fabric coordinates, 2-2-71 hints, 3-6-1, 3-6-3
files, 2-1-2 introduction, 3-1-1
grouping objects, 2-2-63 operator comments, 3-4-14
introduction, 2-1-1– 2-1-5 print appearance, 3-4-10
joining objects, 2-2-63 saving to disk, 3-5-1
library symbols, 2-2-17– 2-2-18 troubleshooting, 3-6-1, 3-6-3
limits, 2-3-2 Russian Console, 1-7-1
merging objects, 2-2-66
moving objects, 2-2-56
new symbols, 2-2-19– 2-2-20 S
object types, 2-2-5– 2-2-6
origin point, 2-2-72 scaling, Trend Group screen, 4-3-7
panning limits, 2-2-72 screen
preconfigured, 2-3-7 Console Configuration page 3, 7-3-8–7-3-10
shape characteristics, 2-2-15– 2-2-16 Link Editor, 2-3-10– 2-3-11
splitting objects from group, 2-2-69 Login, 7-2-2
storage, 2-1-2 User Name Detail, 7-3-19–7-3-21
Top Menu, 2-2-58 User Profile Directory, 7-3-12–7-3-13
undoing operation, 2-2-70 screen commands, changes for password security,
viewing mode, 2-1-4 7-1-3
process graphic (pixel graphics), calling up, 2-1-4 screen refresh rate
Process Graphic Generation screen, 2-1-4 configuring, 1-1-30
process graphic links, changing, 2-3-9 limits, 1-1-31, 2-3-2
process graphics, 2-2-1– 2-2-81 process graphics, 2-3-8
process graphics folder, 2-1-2 secure keyboard interface, with passwords, 7-4-3
selecting a report object, 3-6-2
shapes
R creating arcs, 2-2-12
creating boxes, 2-2-10
creating circles, 2-2-9
reducing message requests, 4-3-10 creating lines, 2-2-13
refresh rate, configuring, 1-1-30 creating lines with different characteristics,
report, 3-1-1 2-2-13, 2-2-14
Report Config Directory screen, 3-2-6– 3-2-7 creating shape characteristics, 2-2-15– 2-2-16
Report Configuration screen, 3-4-2, 3-4-3 creating triangles, 2-2-11
Report Configuration window, 3-4-5, 3-4-8 library symbols, 2-2-17– 2-2-18
report dimensions, 3-3-2 new symbols, 2-2-19– 2-2-20
Report File Contents screen, 3-2-4 which fill up, 2-2-21– 2-2-22
report objects slidewire
types, 3-4-6 Trend Group screen, 4-3-6
using, 3-4-5 trend object, 2-2-43– 2-2-46
Report Read Directory screen, 3-2-3 splitting an object from a group, 2-2-69
Report Read/Scan screen, 3-2-5 splitting tags, 1-1-15–1-1-16, 1-1-17–1-1-18
Report Status screen, 3-2-8 SQC report objects, 3-1-1
reports, 3-2-1, 3-3-3, 3-4-1, 3-5-1, 3-6-1 stacking objects, 2-2-58
assembling information for, 3-3-1 standard KBI, with passwords, 7-4-4
configuring, 3-4-1, 3-4-43 standard message pairs, 1-5-2– 1-5-4
configuring a report in a report, 3-4-37 symbols, 5-1-2
configuring block information, 3-4-15, 3-4-25 process graphics, 2-2-17– 2-2-20
configuring console lists, 3-4-34 system manager, changing from configuror,
configuring oversized text, 3-4-13 7-3-24–7-3-25
configuring print appearance, 3-4-10 System Status messages, 6-3-2

CC: Index-6
T hints, 4-5-1
operations, 4-1-1– 4-1-6
process graphics, 2-2-41– 2-2-44
tag object screens, 4-1-5
process graphics, 2-2-25– 2-2-27 troubleshooting, 4-5-1
reports, 3-4-15 trf#, 4-1-4, 4-4-2
tags trf#b, 4-1-4, 4-4-2
masking, 1-1-15–1-1-16, 1-1-19–1-1-22 triangle object
splitting, 1-1-15–1-1-16, 1-1-17 configuring characteristics, 2-2-16
target object, process graphic, 2-2-77– 2-2-78 fill option, 2-2-21– 2-2-22
text object process graphics, 2-2-11
calling up other displays, 2-2-74– 2-2-77 troubleshooting
process graphics, 2-2-46– 2-2-47 alarm management, 6-7-1
reports, 3-4-12, 3-4-13 callup and display buttons, 1-4-9
thing object, process graphics configuring colors, 1-2-8
grouping objects, 2-2-66 configuring console operations, 1-1-28
merging objects, 2-3-5 configuring trending, 4-5-1
ticbar object reports, 3-6-1
configuring characteristics, 2-2-32
process graphics, 2-2-31– 2-2-32
alarm annunciation, 2-2-85
time object, reports, 3-4-32
U
tips
configuring callup and display buttons, 1-4-10 undoing the previous operation, process graphics,
configuring console operations, 1-1-29 2-2-70
message pairs, 1-5-9 Unit Directory screen, 1-3-5
Top menu, process graphics, 2-2-2, 2-2-56– 2-2-66 Unit Display screen, 1-3-6
top operation, 2-2-58– 2-2-59 units object
trend data process graphics, 2-2-28– 2-2-30, 2-2-37–
archiving, 4-4-1– 4-4-3 2-2-39
viewing, 4-3-8 reports, 3-4-20
Trend Data Folder, 4-1-4 update time, configuring, 4-3-10
trend file updating graphics, 2-3-9
backup, 4-4-2 user message pairs, 1-5-1– 1-5-3, 1-5-5, 1-5-8
configuring, 4-2-1– 4-2-7 User Message Pairs screen, 1-5-5
storage, 4-1-4 User Name Detail screen, 7-3-19–7-3-21
Trend File Configuration screen, 4-1-5, 4-2-5– user name profile, changing, 7-3-23
4-2-7 User Profile Directory screen, 7-3-12–7-3-13
Trend File Setup screen, 4-2-2– 4-2-3 user--defined characters, 2-2-86
trend group
capabilities, 4-1-2
configuring, 4-3-1– 4-3-9
example, 4-1-1
V
updating, 4-3-10
Trend Group screen, 4-3-5– 4-3-8 value object, reports, 3-4-21
trend information, process graphics, 2-2-41– 2-2-42 vdev object, process graphics, 2-2-31– 2-2-34
trend log object, reports, 3-4-26 viewing mode
trend object, process graphic, 2-2-44 calling up, 2-1-4
trending display of objects, 2-2-7
enabling and disabling, 4-1-6 displaying, 2-1-3

CCV18

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

CCV18

Uploaded by

Copyright:

Available Formats

RS3t

Software Version 18, Release 2

Fisher-Rosemount Systems, Inc.

Telephone: (512) 835--2190

Console Configuration Manual 1984-2643-18x1

Please give us your feedback to help improve this manual.

3. What could be changed in this manual to make it more useful?

May we contact you about your comments? j Yes j No

Fisher-Rosemount Systems, Inc.

Seal with tape.

About This Manual

This manual describes the operations performed at the RS3 console.

D Chapter 1 Configuring operating characteristics of the RS3

RS3: Console Configuration Manual About This Manual

Changes for This Release

D Added information on the Menu Command Console Screen

Version 18 Release 1 also added:

Revision Level for This Manual

For This Refer to This Document:

18R2 Console Configuration Manual August 1994 1984-2643-18x1

18R1 Console Configuration Manual October 1993 1984-2643-18x1

17 Console Configuration Manual August 1992 1984-2643-17x1

16 Console Configuration Manual January 1992 1984-2643-16x1

15 Console Configuration Manual January 1991 1984-2643-15x1

RS3: Console Configuration Manual About This Manual

References to Other Manuals

Manual Title Chapter Manual Title Chapter-Section

Abbreviations of Manual Titles

RS3: Console Configuration Manual About This Manual

You should be familiar with the information in the following documents

RS3: Console Configuration Manual About This Manual

Chapter 1: Configuring Operating Characteristics

Section 1: Configuring Console Operations . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1-1

Section 2: Configuring Color . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2-1

RS3: Console Configuration Manual Contents

Section 3: Configuring Operating Displays . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3-1

Section 4: Configuring Callup and Display Buttons . . . . . . . . . . . . . . . . . . . 1-4-1

Section 5: Configuring Message Pairs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5-1

Section 6: Configuring the Block Print Function . . . . . . . . . . . . . . . . . . . . . . 1-6-1

Section 7: Multinational Characters and Russian Console . . . . . . . . . . . . . 1-7-1

Chapter 2: Process Graphics

Section 1: Introduction to Process Graphics . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1-1

RS3: Console Configuration Manual Contents

Section 2: Process Graphics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-1

RS3: Console Configuration Manual Contents

Configuring Display Characteristics

Section 3: Optimizing Graphics Performance . . . . . . . . . . . . . . . . . . . . . . . . . 2-3-1

Section 1: Introduction to Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1-1

Section 2: The Report File Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2-1

Section 3: Designing a Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3-1

RS3: Console Configuration Manual Contents

Section 4: Configuring a Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4-1

Section 5: Saving a Report to Disk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5-1

Section 6: Hints for Configuring and Using Reports . . . . . . . . . . . . . . . . . . . 3-6-1

RS3: Console Configuration Manual Contents

Section 1: Trending Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1-1

Section 2: Configuring Trend Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2-1

Section 3: Configuring Trend Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3-1

Section 4: Archive Trend Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4-1

Section 5: Hints for Configuring Trending . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5-1

Section 1: Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1-1

Section 2: Hints for Using Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2-1

RS3: Console Configuration Manual Contents

Chapter 6: Alarm Management