configuring your ovation operator station

Configuring Your Ovation Operator Station

Section Title Page

Section 1. Introduction

1-1. Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-11-2. Contents of this Document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-41-3. Additional Reference Documentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-51-4. Ovation Display Terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6

Section 2. Ovation Developer Studio Overview

2-1. Section Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-12-2. Ovation Developer Studio Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1

2-2.1. Using the Studio. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-12-3. Developer Studio Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-32-4. Accessing the Configuration Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6

Section 3. Alarm Configuration

3-1. Section Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-13-2. Inserting a New Alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-33-3. Configuring Existing Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-33-4. Alarm Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-63-5. Alarm Display Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8

3-5.1. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-83-5.2. Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8

3-6. Configuring Alarm Filtering Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-123-6.1. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-123-6.2. Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-12

3-7. Alarm Collectors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-193-8. Alarm Audio Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-22

3-8.1. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-223-8.2. Audio Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-223-8.3. The Audio Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-243-8.4. Adding a New Audio File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-283-8.5. Accessing a Sample Audio File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-30

3-9. Configuring Alarms for Historical Storage. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-333-9.1. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-333-9.2. Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-33

3-10. Alarm Printing Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-353-10.1. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-353-10.2. Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-35

3-11. Alarm Colors Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-423-11.1. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-42

1/03 i WIN21 (Rev 0)Emerson Process Management Proprietary Class 2C

Table of Contents, Cont’d

Section Title Page

3-11.2. Alarm Colors Tabs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-423-11.3. Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-44

3-12. Iconic Alarming . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-653-12.1. Accessing the Iconic Folder. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-653-12.2. Inserting a New Icon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-673-12.3. Configuring Iconic Alarm Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-703-12.4. Configuring Iconic Alarm Diagrams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-72

3-13. Bitmap Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-743-13.1. The Bitmap Folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-74

Section 4. Historian Configuration

4-1. Section Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-14-2. Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-14-3. Configuration Procedure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2

Section 5. MMI Configuration

5-1. Section Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-15-2. Inserting a New MMI Window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-25-3. Configuring an Existing MMI Folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-5

Section 6. OPC

6-1. Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-16-2. Configuring OPC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1

Section 7. Configuring the Ovation Keyboard

7-1. Section Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-17-2. Ovation Keyboard Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-27-3. Adding the Ovation Keyboard to a Drop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-47-4. Configuring an Existing Ovation Keyboard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-77-5. Configuring Iconic Alarming . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-9

7-5.1. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-97-5.2. Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-9

7-6. Defining Ovation Keyboard Keys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-127-6.1. Key Definition Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-127-6.2. Alarm Group Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-22

WIN21 (Rev 0) ii 1/03Emerson Process Management Proprietary Class 2C


Section Title Page

Section 8. Process Diagram System

8-1. Section Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-18-2. Inserting New Process Diagrams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-28-3. Configuring Process Diagrams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-48-4. Inserting New Color Definitions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-58-5. Configuring Process Diagram Color Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-7

8-5.1. Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-7

Section 9. Configuring Quality

9-1. Section Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-19-2. Quality Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-29-3. Quality Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-3

9-3.1. Inserting a New Point Quality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-39-3.2. Configuring the Quality Folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-5

Section 10. Configuring Review

10-1. Section Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-110-2. Review Folder. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-3

10-2.1. Inserting a New Point Review . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-310-2.2. Configuring the Point Review Folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-4

10-3. Configuring Review Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-610-3.1. Creating a New Review Characteristics Folder . . . . . . . . . . . . . . . . . . . . . 10-710-3.2. Configuring an Existing Review Characteristics Folder . . . . . . . . . . . . . . 10-910-3.3. Inserting a New Group. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-12

Section 11. Trend Display

11-1. Section Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-111-2. Trend Configuration Folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-2

11-2.1. Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-311-3. Trend Default . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-9

11-3.1. Inserting a New Trend Default . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-911-3.2. Configuring an Existing Trend Default . . . . . . . . . . . . . . . . . . . . . . . . . . 11-1111-3.3. Trend Scale Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-13

1/03 iii WIN21 (Rev 0)Emerson Process Management Proprietary Class 2C


Section Title Page

Section 12. SCADA Server

12-1. Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-112-2. SCADA Server Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-212-3. Inserting a New SCADA Driver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-412-4. Configuring an Existing SCADA Driver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-7

12-4.1. Configuring Hardware Options for SCADA Drivers . . . . . . . . . . . . . . . . 12-812-4.2. Configuring Signal Conditions for SCADA Drivers . . . . . . . . . . . . . . . . 12-10

12-5. Configuring SCADA Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-1312-5.1. Channels. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-1412-5.2. Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-2912-5.3. Additional Mappings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-3312-5.4. Events. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-35

Section 13. Downloading

13-1. Section Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-113-2. Download Procedure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-213-3. Downloading to Multiple Drops . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-4

13-3.1. Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-4

Glossary

Index

WIN21 (Rev 0) iv 1/03Emerson Process Management Proprietary Class 2C

Section 1. Introduction

1-1. Overview

The Ovation Operator Station is a drop that enables an operator to view and controlthe current status of the plant process control system through the use of processdiagrams and other standard display utilities. The Operator Station functionsinclude monitoring and controlling alarm conditions, entering point information,and creating point trends.

This document describes the necessary steps to configure your Operator Station.The Operator Station functions are configured using the Ovation Developer Studiosoftware package. For further explanation on using the Operator Station, see“Ovation Operator Station User Guide” (WIN20). For information on using theOvation Developer Studio, see “Ovation Developer Studio User Guide” (WIN60).

1/03 1-1 WIN21 (Rev 0)Emerson Process Management Proprietary Class 2C

Figure 1-1. Connection of Operator Station (Fast Ethernet)

I/O I/O

Co

ntr

olle

r

Co

ntr

olle

r

. ...

Root Switch Backup Root Switch

Ports 2 and 3 are forswitch pair interconnection

Ports 4 through 24 are forOvation device connections

Port 1 on all switchesis for IP only traffic

Laser printer Laser printer

Typical redundantController (shownsingle attached)

Typical Windowsworkstation (showndual attached)

WIN21 (Rev 0) 1-2 1/03Emerson Process Management Proprietary Class 2C

Figure 1-2. Connection of Operator Station to Plant Processes (FDDI)

. ... . ...

RedundantController

Operator Station Co

ntr

olle

r

Co

ntr

olle

r

Ovation Network Rings

Concentrator Concentrator

Workstation

RedundantController

Co

ntr

olle

r

Co

ntr

olle

r

I/O I/O I/O I/O


1-2. Contents of this Document

1-2. Contents of this Document

This document is organized into the following sections:

Section 1. Introduction describes the contents of this document and lists otherreference documentation.

Section 2. Ovation Developer Studio Overview introduces the Ovation DeveloperStudio and explains its interface, tools, and general functionality.

Section 3. Alarm Configuration describes the procedures for configuration of theBase Alarm System, the Audio Systems, and Iconic Alarming.

Section 4. Historian Configuration describes the procedures for configuration ofthe Historian item.

Section 5. MMI Configuration describes the procedures for configuration of thedisplay parameters.

Section 6. OPC describes the procedure for configuration of the OPC item.

Section 7. Configuring the Ovation Keyboard describes the procedures forconfiguring the Ovation Keyboard.

Section 8. Process Diagram System provides information on configuring theProcess Diagram System.

Section 9. Configuring Quality describes the procedures for configuring theQuality that is displayed on the Operator Station windows.

Section 10. Configuring Review describes the procedures for configuring PointReview.

Section 11. Trend Display describes the procedures for configuring the Trendfunction.

Section 12. SCADA Server describes the procedures for configuring the SCADAitem.

Section 13. Downloading describes the download procedure.


1-3. Additional Reference Documentation

1-3. Additional Reference Documentation

Table 1-1 lists additional reference documentation which may be helpful whileusing this document.

In addition to the documents listed in Table 1-1 , this manual may refer to“applicable vendor documentation,” which is defined on a project basis. Thesedocuments may include:

• Operating system manuals.

• Peripheral device documentation.

Table 1-1. Reference Documents

DocumentNumber Title Description

WIN20 Ovation Operator Station User Guide Provides instructions for using the OperatorStation.

WIN55 Ovation Controller User Guide Provides controller configuration information.

WIN56 Ovation Simulator User Guide Provides configuration information forsimulators.

WIN60 Ovation Developer Studio User Guide Provides information on the structure andusage of the Ovation Developer Studiosoftware package.

NT-0070 eDB Historian User Guide Provides information on the collection,archival, and retrieval of process values andmessages.

WIN80 Ovation Control Builder User Guide Provides information on using the ControlBuilder software to build logic.

WIN90 Ovation Graphics Builder User Guide Provides information on the use of theGraphics Builder.

WIN91 Ovation Graphics Language User Guide Provides a reference to the graphics sourcelanguage rules and commands.


1-4. Ovation Display Terms


Table 1-2 contains a listing of common terms used in conjunction with the OperatorStation display. The terms either refer to the appearance of text or symbols on thescreen or the method of manipulating the mouse.

Table 1-2. Terms Used with the Operator Station Display

Term Definition

OK Will apply changes and dismiss the window.

Apply Button located on many data entry windows. Used to verify the data, enterinformation and start a desired operation. The window is not dismissed.

Cancel Cancels changes and dismisses window.

Close Action that requires/allows a user to quit a window. The application is terminated.

Display Area The main area of a window, usually between the Toolbar and the Task Bar.

Double click Action that requires a user to rapidly click the left mouse button twice.

Drag and Drop Window manager function that allows the user to “drag” data from one window and“drop” it into another window.

Grayed out Color of a button or entry field that indicates that a function or menu item is notavailable to the user under the present conditions.

Icon Graphical representation of a window or function.

Left-click(“Select”)

Action that requires a user to click the left mouse button once. The left mousebutton is used to select a window or an item inside a window.

Maximize Opens the window to the full size of the screen.

Menu Bar The Menu Bar is usually located at the top of the main window. Cascade buttonsare placed on the Menu Bar. A pull-down menu is associated with each cascadebutton located on the Menu Bar.

Minimize Removes the window from the screen, but does not terminate the application. Abutton on the task bar provides access to the application.

Open Double click on an icon to open the application.

Refresh Refreshes screen.

Right-click(“Menu”)

By clicking the right button on the mouse, a pop-up menu may be displayedcontaining action appropriate to the cursor position and application.

Status Bar The Status Bar is a space at the bottom of many program windows that contains ashort text message about the current condition of the program and specificapplication data.



Task Bar A small area on the screen which contains buttons for all the running applications.The task bar is usually along the bottom, but may be positioned along any edge bythe user.

Title Bar Top margin of a program window. Contains minimize, maximize and close iconsin upper right.

Toolbar The Toolbar is usually located under the Menu Bar. It is a row of on-screengraphical buttons or icons relating to application functions.

Workspace Graphical environment where menus, icons, and diagrams are located.

Table 1-2. Terms Used with the Operator Station Display (Cont’d)

Term Definition


Section 2. Ovation Developer StudioOverview

2-1. Section Overview

This section introduces the Ovation Developer Studio. The Ovation DeveloperStudio provides a mechanism to engineer an Ovation system. All of the engineeringtools are integrated and housed under this one common interface. For furtherinformation on the Developer Studio, see “Ovation Developer Studio User Guide”(WIN60).

The folowing topics are included in this section:

• Ovation Developer Studio Introduction (Section 2-2).

• Ovation Developer Studio Components (Section 2-3).

• Accessing the Configuration Tool (Section 2-4).

2-2. Ovation Developer Studio Introduction

The Ovation Developer Studio provides a package of tools necessary to build andmaintain a process control system. Using the tools available, you can build an entiresystem, import information from a previously created database into the DeveloperStudio, and edit and update attributes such as network configurations and pointinformation. Within the Developer Studio, you can configure all the OperatorStation functions.

When the Hardware view is selected, Ovation Developer Studio functions arecategorized in a Tree or hierarchal structure as illustrated in Figure 2-1. Ovationconfiguration information is specified at appropriate levels of the system hierarchy.

2-2.1. Using the Studio

Using the Developer Studio, you are able to view and establish parameters andsettings at the System, Network, Unit, Drop, and Point level. Ovation configurationsettings made at the system level default down through the System Tree, but manysettings can be adjusted at each subsequent level. All configurations defined at thelower levels override what has been defined at the higher levels.


For example, if the trend screen background color is set to black at the System level,all trend screen background colors will default to black throughout the entiresystem. If, however, a trend screen background color is changed to green at the unitlevel, trend screens in that unit, including all of the drops in that unit, will utilize thegreen background. By having defaults move down through the system,configuration information can be specified easily and customized where necessary.


2-3. Developer Studio Components


Refer to Figure 2-1 below. The Developer Studio’s interface is comprised of:

• Menu Bar — provides access to Studio functions.

• Tool Bars — provides access to Studio functions.

• Overview Window — displays the system tree and View Bars.

• View Bars — displays views of different aspects of the database.

• WorkPad Window — displays selectable folders and objects.

• Workspace Window — displays functional and document dialog boxes.

• View Buttons — change the appearance of objects in the Workpad Window.

• Status Bar — displays information about the current Studio session.

The Menu bar and Tool bars provide functionality such as Save, Open and Create.

The three function bars -- Hardware, Defaults, TrashCan-- provide views ofdifferent aspects of the database.

Figure 2-1. Developer Studio Interface



Click on a View bar to access its System Tree in the Overview window. The SystemTree is expandable to expose additional folders and files. Files stored in folders arecalled objects.

Objects are viewed as documents in the WorkPad window. Double clicking on anobject in the WorkPad window will open the database contents of that object.

Opening a file will generally spawn a function or document dialog box in theWorkspace window. Enter and edit values of object attributes in the dialog box andsave these changes to the database.

The Status bar displays menu information, identification of the drop where thedatabase resides, the drop which is servicing the current database connection, andwhether certain keyboard functions such as Caps Lock, Num Lock and Insert areoperational.

The top most level in the hierarchy is the System level. In Figure 2-1, the system isnamed “Ovation”. Each system contains folders or icons for licensing, security,ancillary custom symbols, point groups, configurations, graphics and network.Entire system attributes can be modified at this level.

Notice that the Network icon is located within the Ovation icon. The Network iconcontains icons named for each network associated with the system. For example, inthe System Tree, the first Network icon is named NET 0. Every network in a systemcontains folders or icons for Configuration, Graphics, and Unit. Network attributescan be modified within these folders or icons.

The Unit folder contains folders for each unit associated with the network. In thethe System Tree, notice the Unit 1 folder. Unit 1 is the name of a unit in thisexample, and every unit in the network has a folder. Each unit contains sub-foldersor icons for Configuration, Graphics, and Drops. Unit attributes can be modifiedwithin these items.

In each Units folder, there are Drops icons. All drops associated with a unit have anicon. Each drop or Sim drop contains folders or icons for Configuration, Graphics,and Points. Drop attributes can be modified within these items.

At the lowest level of the system tree resides the Point items, which open to revealpoint records. Point records store the information that defines the attributes of thepoint. The objects at this level contain all the information necessary to completelyspecify all the user defined fields for an Ovation point record.



Note

System wide configuration is done at thesystem level. Network wide configuration isdone at the network level. Unit wideconfiguration is done at the unit level. Dropspecific configuration must be done at thedrop level. The lowest level of configurationoverrides the higher configuration.

Most of the sample configuration procedures in this manual are done at the Systemlevel. The same procedures can be followed at the level of your choice.


2-4. Accessing the Configuration Tool


Use the following procedure to access the Configuration Tool:

1. Access the Ovation Developer Studio.

2. Use the following path to drill down (navigate) to the Configuration item:

Studio System TreeSystem Icon (or the appropriate level such as Network, Unit, or Drop)Configuration Icon

3. Select the Folder or Icon of the component you wish to configure.

• Alarm

• Historian

• MMI

• OPC

• Ovation Keyboard

• Process Diagrams

• Quality

• Review

• SCADA Drivers

• Trend

The configuration of the following folders is discussed in other Ovationmanuals. Refer to the following documentation for configuration information:

• ImageBuilder (see “Ovation Developer Studio User Guide” (WIN60))

• Point Processing (see “Ovation Developer Studio User Guide ” (WIN60))

• DDB (see “Ovation Developer Studio User Guide” (WIN60))

• NTP (see “Ovation Developer Studio User Guide” (WIN60))

• Event Log (see “eDB Historian User Guide” (NT-0070))

• Sim Controller (see “Ovation Simulator User Guide” (WIN56))



• Sim Operator Station (see “Ovation Simulator User Guide” (WIN56))

• Controller Networking, Control Task, and Devices (see “Ovation ControllerUser Guide (WIN55))

• Sim Model (see “Ovation Simulator User Guide” (WIN56))

• External System Interface (see “Ovation Developer Studio User Guide”(WIN60))

• External Network Connections (see “Ovation Developer Studio UserGuide” (WIN60))

Note

The (+) symbol before a folder denotes subfolders. Click the + symbol to view andconfigure subfolders.

4. Refer to the following sections (Section 3-3 through Section 13-3) for directionson using the Developer Studio Configuration Tool to configure the OperatorStation.


Section 3. Alarm Configuration


The Base Alarm System allows the operator to monitor and detect abnormal plantconditions. The alarms can be acknowledged, printed, and sent to the eDBHistorian. The set of alarms being displayed can be one of the following:

• A List of the current alarms with the most recent alarm first.

• A History of the most recent 15,000 alarm occurrences (all alarm occurrences,including returns, are displayed).

• A list of the oldest Unacknowledged alarms in the system. This list is generatedfrom the alarm list with the oldest of the alarms that is unacknowledgeddisplayed first.

• A Reset list of points which were returned and acknowledged from alarms.

• A list of Icons. Each icon corresponds to a group of alarms.

• The alarm system can be configured to display Remote Alarm Messages.

The plant operator can also filter out alarms based on their priority and destination.These filtering characteristics can be updated by the operator for both the normaland priority modes of operation. In addition to viewing alarm conditions on thescreen, alarms can be annunciated by playing an audio file on external speakers,printed on the local printer, and sent to the eDB Historian Station (see “eDBHistorian User Guide” (NT-0070) for more information on this drop).

For information on using the Base Alarm System, see “Ovation Operator StationUser Guide” (WIN20).

This section discusses the user interfaces that apply to the Alarm configuration ofthe Operator Station drop. The following topics are included:

• Inserting a New Alarm (Section 3-2).

• Configuring Existing Alarms (Section 3-3).

• Alarm Window (Section 3-4).

• Alarm Display Configuration (Section 3-5).

• Configuring Alarm Filtering Parameters(Section 3-6).

• Alarm Collectors (Section 3-7).


• Alarm Audio Configuration (Section 3-8).

• Configuring Alarms for Historical Storage (Section 3-9).

• Alarm Printing Configuration (Section 3-10).

• Alarm Colors Configuration (Section 3-11).

• Iconic Alarming (Section 3-12).

• Bitmap Configuration (Section 3-13).

Note

Most of the Alarm configuration examplesdiscussed in this section are configured at theSystem level. You can configure the Alarmsat any level in the System Tree. The lowestlevel of configuration overrides the higherlevel of configuration.


3-2. Inserting a New Alarm

3-2. Inserting a New Alarm

Use the following procedure to insert a new Alarm:


2. Drill down to the Alarm item by navigating through the following path:

Studio System TreeSystem Item (or appropriate level such as, Network, Unit or Drop)Configuration ItemAlarm Item (see Figure 3-1 )

3. Right-click on the Alarm item and choose Insert New. The Alarm Window willappear in the Developer Studio Workspace. The Alarm Window contains 19tabs (see Figure 3-2 ).

3-3. Configuring Existing Alarms

Use the following procedure to configure existing Alarms:



Studio System TreeSystem Item (or appropriate level such as, Network, Unit or Drop)Configuration ItemAlarm Item (see Figure 3-1 )

3. Right-click on the Alarm item and choose Open. The Alarm Window willappear in the Developer Studio Workspace. The Alarm Window contains 19tabs (see Figure 3-2 ).



Figure 3-1. Alarm Item in the Ovation Developer Studio SystemTree



Figure 3-2. Alarm Window


3-4. Alarm Window

3-4. Alarm Window

The Alarm Configuration Window contains the following tabs:

Table 3-1. Alarm Window Tabs

Tab Description

Alarm Display(Section 3-5)

General Alarm window display configuration.

Normal Mode Filtering(Section 3-6)

Normal mode priority and destination filters configuration.

Priority Mode Filtering(Section 3-6)

Priority mode priority and destination filters configuration.

Unit Filtering(Section 3-6)

Unit filtering configuring.

Alarm Collectors(Section 3-7)

Configures the machines that will connect to the remotesystems to gather the remote alarm data.

Audio(Section 3-8)

Alarm audio configuration.

Audio Files/Points(Section 3-8)

Audio files/points configuration.

Alarm Historical Storage(Section 3-9)

Alarm historical storage configuration.

Alarm Printing(Section 3-10)

Configuring the dedicated alarm printer.

Alarm Printer Colors(Section 3-10)

Configuring alarm printer colors.

Display Colors(Section 3-11)

Configuring general alarm display colors.

Unack Alarm Colors(Section 3-11)

Unacknowledged alarm colors configuration.

Ack Alarm Colors(Section 3-11)

Acknowledged alarm colors configuration.

Unack Incr Alarm Colors(Section 3-11)

Unacknowledged incremental alarm colors configuration.

Ack Incr Alarm Colors(Section 3-11)

Acknowledged incremental alarm colors configuration.


3-4. Alarm Window

Each tab can be accessed by using the horizontal scroll bar located at the bottom ofthe Alarm Window.

Unack Return Colors(Section 3-11)

Unacknowledged return colors configuration.

Ack Return Colors(Section 3-11)

Acknowledged return colors configuration.

Icon Tile Colors(Section 3-11)

Icon tile color configuration.

Remote Network Status Colors(Section 3-11)

Remote Network Status color configuration.

Table 3-1. Alarm Window Tabs (Cont’d)

Tab Description


3-5. Alarm Display Configuration


3-5.1. Overview

The Alarm Display tab contains general alarm display configuration parameters.

3-5.2. Procedure

Use the following procedure to configure the Alarm Display tab:



Studio System TreeSystem Item (or appropriate level such as Network, Unit, or Drop)Configuration ItemAlarm Item

3. Right-click on the Alarm item and choose Open. The Alarm Window willappear. If an Alarm item does not appear in the system tree, see Section 3-2.

4. Scroll to select the Alarm Display tab (see Figure 3-3 ) by using the horizontalscroll bar.

5. You can save configuration changes after each tab is configured, or you can saveall changes after all of the tabs in a window have been configured. Select Applyto save changes and leave the window open, or select Ok to save the changesand close the window.



6. The configuration changes you made will not take effect until they aredownloaded to the drop. See Section 13 for information on downloadingchanges to a drop.

Table 3-2 explains the setting options available for the Alarm Display tab.

Figure 3-3. Alarm Display Tab



Table 3-2. Alarm Display Tab

Item Description Setting Options

Alarms Processed:

Maximum Number of AlarmsRemoved

Increase Alarm Rate on FirstPass

Sets the maximum number ofalarms that will be processed everysecond by the alarm system.

Determines how many more alarmsshould be processed per second onthe first pass as opposed to normalpasses.

NoteThis parameter is not used if thealarm system is sending alarms tothe printer or the eDB on first pass.

Values from 1 through 1000Default = 30

Values from 1 through 10Default = 5

Alarm Window:

Blank Line Percent

Show Time on First Pass

Incrementals

Sets the number of blank linesdisplayed at the top of the alarm listand history list to be a percentage ofthe number of lines displayed on thescreen.

Blank Line Percent:33 (Default)(Values 0 through 100)

Determines if the time or if asteriskswill be shown on alarms detected onthe first pass

Determines whether or notincremental alarms are removedfrom their original position in theAlarm List and placed on top (at thesame time will be placed on thebottom on the UnacknowledgedList).

Show Time on First PassFalseTrue (Default)

IncrementalsMove to Top of ListReplace Original Alarmin List (Default)



Alarm Window (Cont’d)

Returns Determines whether or not returnsare removed from their originalposition in the Alarm List andplaced on top (at the same timeunacknowledged return will beplaced on the bottom on theUnacknowledged List).Additionally, Resetable Returnswill be placed at the bottom of thereset list.

ReturnsMove to Top of ListReplace Original Alarmin List (Default)

Timestamp on Incrementalsand Returns

Display Unacknowledged/Resetable Returns

Determines if the time on the AlarmList, Unacknowledged List, andReset List show the time of theoriginal alarm or the time of thereturn or incremental alarm. (This isonly used when Incrementals orReturns is set to Replace OriginalAlarm in List.)

Determines whetherunacknowledged and resetablereturn alarms should be posted onthe alarm list and theunacknowledged list.

Return/Incremental TimestampOriginal Timestamp(Default)

FalseTrue (Default)

Alarm DestinationDescription:

Identifies the additional descriptionthat will be displayed for eachdestination on the filteringwindows.

Destination A-ZDescription - corresponds to theselected destination.No Description (Default)

Table 3-2. Alarm Display Tab (Cont’d)



3-6. Configuring Alarm Filtering Parameters


3-6.1. Overview

The plant operator can filter out alarms based on their priority and destination.These filtering characteristics can be updated by the operator for both the normaland priority modes of operation.

The Normal and Priority Mode tabs identify the priority filters that an alarm mustpass in order to be displayed on each alarm screen. The Unit Filtering tab allows theuser to configure the alarm system to use the additional unit filtering criteria. Thissection will discuss the following alarm configuration tabs:

• Normal Mode Filtering (see Figure 3-4 )

• Priority Mode Filtering (see Figure 3-5 )

• Unit Filtering (see Figure 3-6 )

3-6.2. Procedure

Use the following procedure to configure the three Alarm Filtering tabs:


2. Drill down to the Alarm folder by navigating through the following path:

Studio System TreeSystem Item (or the appropriate level, such as Network, Unit, or Drop)Configuration ItemAlarm Item

3. Right-click on the Alarm item and choose Open. The Alarm Window willappear. If an Alarm folder does not appear in the system tree, see Section 3-2for information on inserting a new alarm.

4. Scroll to select the Normal Mode, Priority Mode or Unit Filtering tabs byusing the horizontal scroll bar.





See Table 3-3 for Normal and Priority Mode setting options explanation.

Figure 3-4. Normal Mode Filtering Tab



Note

The quotation marks (“) used in the followingtable are for emphasis only. Do not type thequotation marks in the value field.

Figure 3-5. Priority Mode Filtering Tab

Table 3-3. Normal/Priority Mode Filtering Tabs


Normal/Priority ModeFiltering Priorities

Shows the priority that an alarmmust have to be included on thespecified list for normal and prioritymodes.

Valid Priorities“–” (wildcard) or“1–8” (“18” means that 1 and 8 areused, “1478” = 1,4,7,8 etc.)

Normal History Priority “–” (Default)(Entry Field)

Normal List Priority“–” (Default)(Entry Field)




Normal/Priority ModeFiltering Priorities (Cont’d)

Shows the priority that an alarmmust have to be included on thespecified list for normal and prioritymodes.(Cont’d)

Normal UnacknowledgedPriority“–” (Default)(Entry Field)

Normal Reset Priority“–” (Default)(Entry Field)

Normal eDB Priority“–” (Default)(Entry Field)

Normal Print Priority“–” (Default)(Entry Field)

Priority Mode HistoryPriority“–” (Default)(Entry Field)

Priority Mode List Priority“–” (Default)(Entry Field)

Priority ModeUnacknowledged Priority“–” (Default)(Entry Field)

Priority Mode Reset Priority“–” (Default)(Entry Field)

Priority Mode eDB Priority“–” (Default)(Entry Field)

Priority Mode Print Priority“–” (Default)(Entry Field)

Table 3-3. Normal/Priority Mode Filtering Tabs (Cont’d)




Normal/Priority ModeDestinations

Shows the destination that an alarmmust have to be included on thespecified list for normal and prioritymodes.

Valid Destinations are: anycombination of“A–Z” or “–”(the wildcard)

Normal HistoryDestination: (Entry Field)

Normal List Destination: (EntryField)

Normal UnacknowledgedDestination: (Entry Field)

Normal Reset Destination: (EntryField)

Normal eDB Destination: (EntryField)

Normal PrintDestination: (Entry Field)

Priority Mode HistoryDestination: (Entry Field)

Priority Mode ListDestination: (Entry Field)

Priority Mode UnacknowledgedDestination: (Entry Field)

Priority Mode ResetDestination: (Entry Field)

Priority Mode eDBDestination: (Entry Field)

Priority Mode PrintDestination: (Entry Field)

Table 3-3. Normal/Priority Mode Filtering Tabs (Cont’d)



Figure 3-6. Unit Filtering Tab



Table 3-4 explains the Unit Filtering setting options.

Table 3-4. Unit Filtering Tab


Unit Filtering:

Scan Points From

Filtering Based on Unit

Determines whether the alarm systemwill scan all the points from the defaultunit.

Is only active when the “Scan PointsFrom” option is set to scan from allunits. This determines whether the basealarm windows have an additional unitfilter for each list, the printer and theeDB, in the normal and priority modes.

If Filtering Based on Unit is enabled,the base alarm window displays willhave the ability to filter remote alarmdata, providing the window isconfigured to receive remote alarmmessages.

All Units (Default)Default Units

EnabledDisabled (Default)


3-7. Alarm Collectors


The base alarm windows connect to the Alarm Collectors in order to receive remotealarm data. The Alarm Collectors connect to the remote data servers on the remotesystem in order to gather remote alarm data. The Alarm Collectors then disseminateall of the remote alarm messages to the base alarm windows that have connected tothem. The alarm collectors are local machines and are defined as:

• System/External System Interface

• Local/Local Alarm Collectors

Refer to “Ovation Developer Studio User Guide” (WIN60) for more information.

Note

Primary and Secondary alarm collectors mustcollect remote alarm data from the samenetworks.

Use the following procedure to configure the Alarm Collector tabs:


2. Drill down to the Alarm folder by navigating through the following path:

Studio System TreeSystem Item (or the appropriate level, such as Network, Unit, or Drop)Configuration ItemAlarm Item

3. Right-click on the Alarm item and choose Open. The Alarm Window willappear. If an Alarm folder does not appear in the system tree, see Section 3-2for information on inserting a new alarm.

4. Scroll to select the Alarm Collectors tab by using the horizontal scroll bar (seeFigure 3-7 ).




Table 3-5 explains the setting options available in the Alarm Collectors tab.

Figure 3-7. Alarm Collectors Tab

Table 3-5. Alarm Collectors Tab


Primary

Alarm Collector Name Primary alarm collector drop.

This list is populated from the previouslydefined Alarm Collector drops. SeeExternal System Interface and LocalAlarm Collectors in “Ovation DeveloperStudio User Guide” (WIN60) for moreinformation.

Pull-down menu

IP Address IP address for the alarm collector IP address of the AlarmCollector machine. This isautomatically filled in.



Secondary

Alarm Collector Name Secondary alarm collector drop

This list is populated from the previouslydefined Alarm Collector drops. SeeExternal System Interface and LocalAlarm Collectors in “Ovation DeveloperStudio User Guide” (WIN60) for moreinformation.

Pull-down menu

IP Address IP address for the alarm collector IP address of the AlarmCollector machine. This isautomatically filled in.

Table 3-5. Alarm Collectors Tab (Cont’d)



3-8. Alarm Audio Configuration


3-8.1. Overview

The Ovation Audio System is used to produce a sound whenever an alarm occurs.The sound alerts the user that a point is in alarm and attention is needed. Thismanual discusses the configuration for the audio system. For usage information, see“Ovation Operator Station User Guide” (WIN20).

Notes

The user is responsible for supplying the audiofiles that will be used. Sample files, provided byEmerson Process Management, are located in thesystem audio folder. All audio files must be .wavfiles.

3-8.2. Audio Configuration

When an alarm is received for the continuous audio system, the user-defined audiofile is sounded continuously and the configured digital is turned on until it issilenced by the operator. An audio file that corresponds to each alarm priority anda return event are configured. Each time an alarm is received, the tone for thehighest priority alarm is sounded and the highest priority digital alarm is turned on.If a higher priority alarm is received before silencing the audio, the tone willautomatically change to the higher priority tone. Additionally, the system can beconfigured to define a digital point corresponding to each alarm priority and thereturn event.

Note

Digital points must be originated by theOperator Station and must not be Alarmablepoints.



Before Configuring the Audio

The Continuous Audio System can be used by a cluster of Operator Stations in aparticular plant area. The system can be configured so that when an alarm comes in,only one Operator Station will sound initially. If the first drop to sound is notacknowledged, the second Operator Station will sound, and so on. All OperatorStation drops will “hear” the audio and be able to cancel it, eliminating the possibleechoing if all drops would sound at once.

To set up the system, each Operator Station (that will have cancel capability) mustoriginate a digital point that it will use as the cancel request point. This point isdefined by the CancelRequest parameter.

A logical “OR” logic must then be built in a Controller drop sheet that has eachCancel Request point from all of the Operator Stations OR gated together. Thepoints are passed through a Timer or One Shot (special function), and then writtento the Monitor Cancel point. The Monitor Cancel point is originated by theController and is used to set the MonitorRequest parameter. The logic allows anystation in the area to cancel the audio tone where ever it is being sounded. For furtherinformation on building logic, see “Ovation Control Builder User Guide” (WIN80).

In addition to the Control Builder logic, the Operator Station must be configured tooriginate the CancelRequest point. The redundancy capability is built into thesystem by changing the Time Delay (defined in the Time Delay parameter) on eachdrop of the Operator Station cluster. The primary Operator Station (the one that isto sound first) may have a delay of 0 or 1 second. The second Operator Station tosound can be set at 10 seconds and so on. When an alarm comes in, the firstOperator Station will sound. If no cancel is performed in 10 seconds, the secondOperator Station would begin to sound. This continues for all Operator Stationsuntil the time defined by the AutoTurnoff parameter expires or the user silences thealarm.

If the continuous audio will be running on one drop and the operator will only beable to silence the audio via that drop, then it can be configured to run in the localmode. The continuous audio is considered to be running in a local mode when thecancel point (CancelRequest) is not defined.

When the continuous audio is in the local mode, the Control Builder logic isunnecessary. The audio can only be silenced by selecting the Silence Audio button onthe Base Alarm Window or the Ovation Keyboard located on the drop where thecontinuous audio is running. Since there is no cancel point and no Control Builderlogic, only the drop that is running the continuous audio can silence it. Additionally,if a drop is running the continuous audio in the local mode, it can not silence any otherdrops running continuous audio. For further information, see “Ovation OperatorStation User Guide”(WIN20).



Audio configuration parameters are set in the Audio Tab. Audio configuration canbe done at any level in the Studio System Tree. Specific drop audio configurationmust be done at the drop level.

3-8.3. The Audio Tab

Use the following procedure to configure the Audio Tab:



Studio System TreeSystem Item (or appropriate level such as Network, Unit or Drop)Configuration ItemAlarm Item

3. Right-click on the Alarm item and choose Open. If an Alarm item does notappear in the system tree, see Section 3-2 for information on inserting a newalarm.

4. Scroll to select the Audio tab using the horizontal toolbar (see Figure 3-8 ).





Table 3-6 lists the available options for the Audio Tab.

Figure 3-8. Audio Tab

Table 3-6. Audio Tab


Audio Type Defines whether the audio is enabled ordisabled.

No Audio Defined (Default) orContinuous Audio

Time Delay Defines the number of seconds theaudio will pause before playing a newaudible.

Time Delay (secs):0 (Default)(Values from 0 through 120)

Auto Turnoff Defines the number of minutes theaudio will be permitted to sound. Afterthe audible has sounded for x numberof minutes without being silenced, theaudible will automatically be silenced.

Auto Turnoff (mins):0 (Default)(Values from 0 through 60)



The Audio Files/Points Tab (see Figure 3-9 ) is displayed by clicking through thehorizontal scroll bar.

Cancel Request Defines the digital point originated bythe host Operator Station that is used torequest a cancel audible. If no point isdefined, the continuous audio systemwill run in the local mode as describedin Section 3-8.2. If the point is definedand not originated by the station,continuous audio will exit.

Cancel RequestEntry Field

Monitor Request Defines the digital point which ismonitored for a Cancel. When set, itsilences the local audible. If thecontinuous audio is running in the localmode, Monitor Request is ignored. If itis not running in the local mode and theMonitor Request is set to Null (forexample, no point is defined), then theselection of the silence Audio Buttonwill not silence the audio.

Monitor RequestEntry Field

Table 3-6. Audio Tab (Cont’d)




Figure 3-9. Audio Files/Points Tab



Table 3-7 lists the available Options for the Audio Files/Points Tab.

3-8.4. Adding a New Audio File

Use the following procedure to add a new audio file:


2. Drill down to the Audio item by navigating through the following path:

Studio System TreeSystem Item (or appropriate level such as, Network, Unit or Drop)Configuration ItemAlarms ItemAudio Item

3. Right-click on the Audio Item and select Insert New. An Audio Wizard appears(see Figure 3-10 ).

Table 3-7. Audio Files/Points Tab


Audio Files All audio files are based on priority. Audio Files

Value Entry Field: Name of the.wav file to be sounded for eachpriority and return event.

Audio Points All audio points are based on priority.When an alarm is detected thecontinuous audio will turn on thespecified point in addition to playingthe audio file.

Audio Points

Value Entry Field: Digital pointsoriginated by the workstation (Notalarmable points).



4. Input the required information (name of audio file without the .wav extension).The Sound Recorder window appears displaying a blank .wav file.

5. Record the appropriate audio and select Finish.

6. You may also import an audio file from another source. To do this, right-clickon the Audio Files Item and select Import.

7. A Browse dialog box appears (see Figure 3-11 ). Enter the desired informationand click on the Open button.

Figure 3-10. Audio Wizard



3-8.5. Accessing a Sample Audio File

Use the following procedure to access a sample audio file:


2. Drill down to the Audio Files item by navigating through the following path:

Studio System TreeSystem ItemNetwork ItemUnit ItemFolder of the Drop # you wish to configureAlarms ItemAudio Files Item (see Figure 3-12 )

Note

Audio can be configured at the System,Network, Unit, or Drop level.

Figure 3-11. Browse Dialog Box



3. Select the Audio File from the workpad window. The Sound Recorder dialogbox will appear (see Figure 3-13 ). See Table 3-8 for further explanation of theSound Recorder dialog box.

Figure 3-12. Audio Files Icon



The following table (see Table 3-8 ) defines the Sound Recorder buttons.

Note

Save the new audio file by selecting the File> Save option. Do not use the Save Asoption.

Figure 3-13. Sound Recorder Window

Table 3-8. Sound Recorder Button Definitions

Button Definition

1 Rewind

2 Fast Forward

3 Play

4 Stop

5 Record

1 2 3 4 5


3-9. Configuring Alarms for Historical Storage


3-9.1. Overview

Alarm messages can be sent to the eDB Historian for archival and storage. Foradditional information on the eDB Historian, see “eDB Historian User Guide” (NT-0070). This section discusses the Alarm Historical Storage tab.

3-9.2. Procedure

Use the following procedure to configure the Alarm Historical Storage Tab:



Studio System TreeSystem Item (or appropriate level such as, Network, Unit, or Drop)Configuration ItemAlarm Item

3. Right-click on the Alarm item and select Open from the pop-up menu. TheAlarm window will appear. If an Alarm item does not appear in the system tree,see Section 3-2 for information on inserting a new alarm.

4. Scroll to select the Historical Storage tab using the horizontal scroll bar in theAlarm Window (see Figure 3-14 ).





Table 3-9 explains the setting options for the Alarm Historical Storage tab.

Figure 3-14. Alarm Historical Storage Tab

Table 3-9. Alarm Historical Storage Tab


Send Alarm to theeDB

Identifies whether alarms will be sentto the eDB.

Send Alarm Message to eDBFalse (Default)True

Send First PassAlarms to the eDB

Identifies whether alarms will be sentto the eDB on first pass. It is only usedif alarms will be sent to the eDB.

Send Alarm Message to the eDB on theFirst PassFalseTrue (Default)

eDB Alarm ScannerDrop

List of Stations in the System. Selectthe Station where the alarm scannersoftware is running. If this field is leftblank, then the messages will be sent tothe machine that the alarms are runningon.

Choose from the Drop pull-downmenu.


3-10. Alarm Printing Configuration


3-10.1. Overview

The Alarm Printing Tab defines the dedicated alarm system printer. This is the lineprinter that will continuously receive the alarms. This does NOT refer to thestandard Windows print functions that can be initiated from the alarm window.

Configuration for a specific drop must be done at the Drop level in the system tree.

Section 3-10 explains the following tabs:

• Alarm Printing Tab - the user enables and defines the alarm printer’s operationfrom this tab.

• Alarm Printer Colors Tab - alarm printer colors are configured using this tab.

3-10.2. Procedure

Use the following procedure to configure the Alarm Printing Tab:



Studio System TreeSystem Item (or the appropriate level such as, Network, Unit or Drop)Configuration ItemAlarm Item

3. Right-click on the Alarm item and select Open. If an Alarm item does notappear in the system tree, see Section 3-2.



4. Scroll to select the Alarm Printing tab using the horizontal scroll bar (seeFigure 3-15 ).

Table 3-10 lists available setting options for the Alarm Printing Tab.

Figure 3-15. Alarm Printing Tab

Table 3-10. Alarm Printing Tab


Alarm Printer Enable or Disable the Alarm Printer. Select Enabledor Disabled (Default).

Print Alarms on FirstPass

When the alarm system first comes on-line, it checks all the points in thesystem. This is called a “first pass.”Print Alarms on First Pass determineswhether the alarm system will print oradvance past all alarms detected duringthe first pass.

Print Alarms on First Pass:False or True (Default)

Printer Serial Port Defines the port to which the printer isconnected.

Printer Serial Port:Input Field



5. Scroll to select the Alarm Printer Colors tab to configure colors(see Figure 3-16 ).



Page Length (Lines PerPage)

Specifies the total length of the page inlines.

Lines Per Page:66 (Default)(Values from 1 through 250)

Number of AlarmMessages Printed PerPage

Specifies the total number of messageson the printer paper including theheader that is printed on the page.

Number of Alarm MessagesPrinted Per Page57 (Default)(Values from 1 through 250)

Printer Offline Timeout Specifies the time in seconds that analarm printer may be off-line before itis declared failed. This time should belong enough for the user to makeadjustments to the printer, paper, orribbon.If the printer is off-line for a longerinterval than the configured value, thenit will be declared as failed and theoutput will be re-routed to the backupprinter, if so configured.

Printer Offline Timeout:0 (Default)(Values from 0 through 7200)

Printer Speed Selects the printer speed. Printer Speed:High Speed orLetter Quality (Default)

Table 3-10. Alarm Printing Tab (Cont’d)




Figure 3-16. Alarm Printer Colors Tab



Table 3-11 lists available setting options for the Alarm Printer Colors Tab.

Table 3-11. Alarm Printer Colors Tab


Alarm Printer Colors: These parameters specify theprinter colors used for timeouts andstate changes.

Drop Timeout Color:Black (Default)Point Timeout Color:Violet (Default)Point State Change Color:Black (Default)

Priority Alarm Print Colors: These parameters specify theprinter color to be used for alarmmessages based on the point’spriority.

Priority DefaultBlack (Default)Priority 1 Alarm Color:Magenta (Default)Priority 2 Alarm Color:Violet (Default)Priority 3 Alarm Color:Yellow (Default)Priority 4 Alarm Color:Cyan (Default)Priority 5 Alarm Color:Green(Default)Priority 6 Alarm Color:Black (Default)Priority 7 Alarm Color:Black (Default)Priority 8 Alarm Color:Black (Default)



Incremental Alarm PrintColors:

These parameters specify theprinter color to be used forincremental alarm messages basedon the point’s priority.

Priority Default Incremental AlarmColor:Black (Default)Priority 1 Incremental AlarmColor:Magenta (Default)Priority 2 Incremental AlarmColor:Violet (Default)Priority 3 Incremental AlarmColor:Yellow (Default)Priority 4 IncrementalAlarm Color:Cyan (Default)Priority 5 IncrementalAlarm Color:Green (Default)Priority 6 IncrementalAlarm Color:Black (Default)Priority 7 IncrementalAlarm Color:Black (Default)Priority 8 IncrementalAlarm Color:Black (Default)

Table 3-11. Alarm Printer Colors Tab (Cont’d)




Return Printer Colors: These parameters specify theprinter color to be used for returnmessages based on the point’spriority.

Priority Default Color:Green (Default)Priority 1 Return Color:Green (Default)Priority 2 Return Color:Green (Default)Priority 3 Return Color:Green (Default)Priority 4 Return Color:Green (Default)Priority 5 Return Color:Green (Default)Priority 6 Return Color:Green (Default)Priority 7 Return Color:Green (Default)Priority 8 Return Color:Green (Default)

Table 3-11. Alarm Printer Colors Tab (Cont’d)



3-11. Alarm Colors Configuration


3-11.1. Overview

The Alarm Colors Tabs define the screen colors for the Alarm System.

Note

When configuring any color, click the downarrow next to the color to display the ColorPalette dialog box (see Figure 3-17 ). Fromthe color palette, select a color or select otherto customize the shade of color. The name ofthe color is not displayed. The actual color isdisplayed. This customizing screen alsodisplays the Red, Green, Blue (RGB) valuefor the color (see Figure 3-18 ).

3-11.2. Alarm Colors Tabs

The following Alarm Colors tabs are addressed in this section:

• Display Colors

• Unacknowledged Alarm Colors

• Acknowledged Alarm Colors

• Unacknowledged Incremental Alarm Colors

• Acknowledged Incremental Alarm Colors

• Unacknowledged Return Colors

• Acknowledged Return Colors

• Icon Tile Colors

• Remote Network Status Colors



.

Figure 3-17. Color Palette

Figure 3-18. Color Customizing Window

RGB Value



3-11.3. Procedure

Use the following procedure to configure the Alarm Colors Tabs (as listed inSection 3-11.2):



Studio System TreeSystem Item (or the appropriate level such as, Network, Unit or Drop)Configuration ItemAlarm Item

3. Right-click on the Alarm item and select Open. If an Alarm item does notappear in the system tree, see Section 3-2 for information on inserting a newalarm.

4. Use the horizontal scroll bar to select the Alarm Colors tabs (see Figure 3-19 ).

5. Follow steps 1-4 to configure the remaining Alarm Colors tabs.

Figure 3-19. Display Colors Tab



The Display Colors Tab

The Display Colors tab (see Figure 3-20 ) specifies the general window display tabs.

Figure 3-20. Display Colors Tab



Table 3-12 explains the available options in the Display Colors tab.

Table 3-12. Display Colors Tab


Default Colors:

Background Color

Foreground Color

The Display Colors tab specifiesthe general alarm window displaycolors. Background Color:

Black (Default)

Foreground Color:White (Default)

Select from a Change Color list tochange any of the default valuesbelow.

Background Colors:

State Change BackgroundColor

Drop Timeout BackgroundColor

Point Timeout BackgroundColor

Selects the background color forthe alarm displays. If any of thesevalues are set to No Color, thebackground color defined for thealarm’s display is used.

Selects the background color forstate changes.

Selects the background color fordrop timeouts.

Selects the background color forpoint timeouts.

State Change BackgroundColor:None (Default)

Drop Timeout BackgroundColor:None (Default)

Point Timeout BackgroundColor:None (Default)

NoteNone identifies that the No Colorbox has been selected for thisspecific color.



Foreground Colors:

State Change Foreground Color

Drop Timeout ForegroundColor

Point Timeout ForegroundColor

Selects the foreground color for thealarm displays. If any of thesevalues are set to No Color, thedefault Foreground color is used.

Selects the foreground color forstate changes.

Selects the foreground color fordrop timeouts.

Selects the foreground color forpoint timeouts.

State Change ForegroundColor: White (Default)

Drop Timeout ForegroundColor: Cyan (Default)

Point Timeout ForegroundColor:Magenta (Default)

Table 3-12. Display Colors Tab (Cont’d)




The Unacknowledged Alarm Colors Tab

The Unacknowledged Alarm Colors tab (see Figure 3-21 ) specifies the foregroundand background colors for unacknowledged foreground and background alarmsbased on their priority.

The following Table 3-13 explains the options available for the UnacknowledgedAlarm Colors tab.

Figure 3-21. Unacknowledged Alarm Colors



Table 3-13. Unacknowledged Alarm Colors Tab


Background Colors These parameters specify the colorthat is to be used forunacknowledged alarms based onthe alarm’s priority.

If any of these values are set to NoPriority Color, the backgroundcolor defined for the alarm displayis used.

Priority 1 BackgroundColor: Red (Default)Priority 2 Background Color:Magenta (Default)Priority 3 BackgroundColor: Yellow (Default)Priority 4 Background Color:White (Default)Priority 5 Background Color:Purple (Default)Priority 6 Background Color:Tan(Default)Priority 7 Background Color:Brown (Default)Priority 8 Background Color:Slate Blue (Default)Priority Def Background Color:Bisque (Default)

Foreground Colors These parameters specify the colorthat is to be used forunacknowledged alarms based onthe alarm’s priority.

If any of these values are set to NoPriority Color, the foregroundcolor defined for the alarm displayis used.

Priority 1 Foreground Color:Black (Default)Priority 2 Foreground Color:Black (Default)Priority 3 Foreground Color:Black (Default)Priority 4 Foreground Color:Black (Default)Priority 5 Foreground Color:Black (Default)Priority 6 Foreground Color:Black (Default)Priority 7 Foreground Color:Black (Default)Priority 8 Foreground Color:Black (Default)Priority Def Foreground Color:Black (Default)



The Acknowledged Alarm Colors Tab

The Acknowledged Alarm Colors tab (see Figure 3-22 ) specifies the foregroundand background colors for acknowledged alarms based on their priority.

Table 3-14 explains the options available in the Acknowledged Alarm Colors tab.

Figure 3-22. Acknowledged Alarm Colors Tab



Table 3-14. Acknowledged Alarm Colors Tab


Background Colors These parameters specify the colorthat is to be used for acknowledgedalarms based on the alarm’spriority.

If any of these values are set to NoPriority Color, the backgroundcolor defined for the alarm’sdisplay is used.


Priority 1 Background Color:NONE (Default)Priority 2 Background Color:NONE (Default)Priority 3 Background Color:NONE (Default)Priority 4 Background Color:NONE (Default)Priority 5 Background Color:NONE (Default)Priority 6 Background Color:NONE (Default)Priority 7 Background Color:NONE (Default)Priority 8 BackgroundColor: NONE (Default)Priority Def BackgroundColor: NONE (Default)

Foreground Colors These parameters specify the colorthat is to be used for acknowledgedalarms based on the alarm’spriority.

If any of these values are set to NoPriority Color, the foregroundcolor defined for the alarm’sdisplay is used.


Priority 1 Foreground Color:Red (Default)Priority 2 Foreground Color:Magenta (Default)Priority 3 Foreground Color:Yellow (Default)Priority 4 Foreground Color:White (Default)Priority 5 Foreground Color:Purple (Default)Priority 6 Foreground Color:Tan (Default)Priority 7 Foreground Color:Brown (Default)Priority 8 Foreground Color:Slate Blue (Default)Priority Def Foreground Color:Bisque (Default)



The Unacknowledged Incremental Alarm Colors Tab

The Unacknowledged Incremental Alarm Colors tab (see Figure 3-23 ) allowsthe user to configure the color that is to be used for unacknowledgedincremental alarm colors based on the alarm’s priority.

Table 3-15 explains the available setting options for the UnacknowledgedIncremental Alarm Colors tab.

Figure 3-23. Unacknowledged Incremental Alarm Colors



Table 3-15. Unacknowledged Incremental Alarm Colors Tab


Background Colors These parameters specify the colorthat is to be used forunacknowledged incrementalalarms based on the alarm’spriority.


Priority 1 Background Color:Red (Default)Priority 2 Background Color:Magenta (Default)Priority 3 Background Color:Yellow (Default)Priority 4 Background Color:White (Default)Priority 5 Background Color:Purple (Default)Priority 6 Background Color:Tan (Default)Priority 7 Background Color:Brown (Default)Priority 8 Background Color:Slate Blue(Default)Priority Def Background Color:Bisque (Default)

Foreground Colors These parameters specify the colorthat is to be used forunacknowledged incrementalalarms based on the alarm’spriority.


No default color is set when the NoPriority Default Color box ischecked.




The Acknowledged Incremental Alarm Colors Tab

The Acknowledged Incremental Alarm Colors tab (see Figure 3-24 ) allows theuser to configure the color that is to be used for acknowledged incrementalalarms based on the alarm’s priority.

The following Table 3-16 explains the setting options available for theAcknowledged Incremental Alarm Colors tab.

Figure 3-24. Acknowledged Incremental Alarm Colors



Table 3-16. Acknowledged Incremental Alarm Colors Tab


Background Colors These parameters specify the colorthat is to be used for acknowledgedincremental alarms based on thealarm’s priority.



Priority 1 Foreground Color:NONE (Default)Priority 2 Foreground Color:NONE (Default)Priority 3 Foreground Color:NONE (Default)Priority 4 Foreground Color:NONE (Default)Priority 5 Foreground Color:NONE (Default)Priority 6 Foreground Color:NONE (Default)Priority 7 Foreground Color:NONE (Default)Priority 8 Foreground Color:NONE (Default)Priority Def Background Color:NONE (Default)

Foreground Colors These parameters specify the colorthat is to be used for acknowledgedincremental alarms based on thealarm’s priority.


Priority 1 Foreground Color:Red (Default)Priority 2 Foreground Color:Magenta (Default)Priority 3 Foreground Color:Yellow (Default)Priority 4 Foreground Color:White (Default)Priority 5 Foreground Color:Purple (Default)Priority 6 Foreground Color:Tan (Default)Priority 7 Foreground Color:Brown (Default)Priority 8 Foreground Color:Slate Blue(Default)Priority Def Foreground Color:Bisque (Default)



The Unacknowledged Return Alarm Colors Tab

The Unacknowledged Return Alarm Colors tab (see Figure 3-25 ) allows theuser to configure the color that is to be used for unacknowledged returns basedon the alarm’s priority.

Table 3-17 explains the setting options available for the UnacknowledgedReturn Alarm Colors tab.

Figure 3-25. Unacknowledged Return Alarm Colors



Table 3-17. Unacknowledged Return Colors Tab


Background Colors These parameters specify the color thatis to be used for unacknowledgedreturns based on the alarm’s priority.

If any of these values are set to NoPriority Color, the background colordefined for the alarm’s display is used.

Priority 1 Background Color:Green (Default)Priority 2 Background Color:Green (Default)Priority 3 Background Color:Green (Default)Priority 4 Background Color:Green (Default)Priority 5 Background Color:Green (Default)Priority 6 Background Color:Green (Default)Priority 7 Background Color:Green (Default)Priority 8 Background Color:Green (Default)Priority Def Background Color:Green (Default)

Foreground Colors These parameters specify the color thatis to be used for unacknowledgedreturns based on the alarm’s priority.

If any of these values are set to NoPriority Color, the foreground colordefined for the alarm’s display is used.




The Acknowledged Return Alarm Colors Tab

The Acknowledged Return Alarm Colors Tab (see Figure 3-26 ) allows the userto set the background and foreground colors for an acknowledged return basedon priority.

Table 3-18 explains the setting options for the Acknowledged Return AlarmColors tab.

Figure 3-26. Acknowledged Return Alarm Colors



Table 3-18. Acknowledged Return Alarm Colors


Background Colors These parameters set the backgroundcolors for a PriorityX acknowledgedreturn.

If any of these background colors areset to No Priority Color, thebackground color defined for thealarm’s display is used.

NoteNone identifies that the No Color boxhas been selected for this specific color.

Priority 1 Background Color:NONE (Default)Priority 2 Background Color:NONE (Default)Priority 3 Background Color:NONE (Default)Priority 4 Background Color:NONE (Default)Priority 5 Background Color:NONE (Default)Priority 6 Background Color:NONE (Default)Priority 7 Background Color:NONE (Default)Priority 8 Background Color:NONE (Default)Priority Def Background Color:NONE (Default)

Foreground Colors These parameters set the foregroundcolors for a PriorityX acknowledgedreturn.

If any of these values are set to NoPriority Color, the foreground colordefined for the alarm’s display is used.

NoteNone identifies that the No Color boxhas been selected for this specific color.

Priority 1 Foreground Color:Green (Default)Priority 2 Foreground Color:Green (Default)Priority 3 Foreground Color:Green (Default)Priority 4 Foreground Color:Green (Default)Priority 5 Foreground Color:Green (Default)Priority 6 Foreground Color:Green (Default)Priority 7 Foreground Color:Green (Default)Priority 8 Foreground Color:Green (Default)Priority Def Foreground Color:Green (Default)



The Icon Tile Colors Tab

The Icon Tile Colors tab (see Figure 3-27 ) specifies the colors for the tile(border) around the bitmap representing the alarm group. Refer to Section 3-12for information on bitmaps in Iconic Alarming.

The following Table 3-19 explains the setting options for the Icon Tile Colorstab.

Figure 3-27. Icon Tile Colors Tab



Table 3-19. Icon Tile Colors Tab


Acknowledged TileColor

Defines the color of the tile around thebitmap for a group that contains allacknowledged alarms.

Select No Unacknowledged Tile Color ifan acknowledged tile color is not desired.

Acknowledged Tile Color:Gray80 (Default)

Unacknowledged TileColor

Defines the color of the tile around thebitmap for a group that contains at least oneunacknowledged alarm.

Select No Unacknowledged Tile Color ifan unacknowledged tile color is not desired.

Unacknowledged Tile Color:Cyan (Default)

Not in Alarm Tile Color Defines the color of the tile around thebitmap for groups that are not in alarm.

Select No Not in Alarm Tile Color if a notin alarm tile color is not desired.

Not in Alarm Tile Color:Green (Default)



Remote Network Status Colors Tab

Defines the foreground and background colors for the Remote Network Status tab.

The following Table 3-20 explains the setting options for the Remote NetworkStatus Colors tab.

Figure 3-28. Remote Network Status Colors Tab

Table 3-20. Remote Network Status Colors Tab


Background Colors

Active Status Background color used when the RemoteNetwork connection is active.

Active Background StatusColorNone (Default)

No Active Status Color If No Active Status Color checkbox isselected, the background color defined forthe alarm display is used.

Check box

Inactive Status Background color used when the RemoteNetwork connection is not active.

Inactive Background StatusColorNone (Default)

No Inactive Status Color If No Inactive Status Color checkbox isselected, the background color defined forthe alarm display is used.

Check box



Foreground Colors

Active Status Foreground color used when the remotenetwork connection is active.

Active Status ForegroundColorGreen (Default)

No Active Status Color If the No Active Status Color checkbox isselected, the foreground color of the alarmdisplay is used.

Check box

Inactive Status Foreground color used when the remotenetwork connection is inactive.

Inactive Status ForegroundColorRed (Default)

No Inactive Status Color If the No Inactive Status Color checkbox isselected, the foreground color of the alarmdisplay is used.

Check box

Table 3-20. Remote Network Status Colors Tab (Cont’d)



3-12. Iconic Alarming


Iconic alarming provides a mechanism to group alarms based on priority and plantarea. The Bitmaps that were created through the Bitmap Folder are shown whenusing Iconic Alarming. For information on creating Bitmaps, see Section 3-13. TheIconic Alarming folder identifies the following:

• Grouping criteria

• Bitmaps that correspond to a group

• Diagram(s) that can be accessed via the group

• Whether returns are maintained in the alarm group

Configuration is done through the Iconic Alarm Window and the Alarm GroupWindow. Before configuring Iconic Alarming, you must decide at what level ofconfiguration you wish to display icons.

Note

The following Iconic AlarmingConfiguration examples assume you areconfiguring at the Drop level. IconicAlarming can be configured at any level in thesystem tree.

3-12.1. Accessing the Iconic Folder

Use the following procedure to access the Iconic item.


2. Drill down to the Iconic item by navigating through the following path:

Studio System TreeDrop # ItemConfiguration ItemAlarm ItemIconic Item (see Figure 3-29 )

If an Alarm item does not appear in the system tree, see Section 3-2 forinformation on inserting a new alarm.



Figure 3-29. Iconic Folder in Studio System Tree



3-12.2. Inserting a New Icon

1. From the Iconic Item, right-click and select Insert New from the pop-up menu.

2. A New Iconic Wizard appears (see Figure 3-30 ). Enter the alarm windownumber that will contain iconic alarming and click Finish.

The Iconic Alarm Window appears (see Figure 3-31 ). The Iconic AlarmWindow specifies the overall layout and the attributes that are constant for eachgroup.

Figure 3-30. New Iconic Wizard



3. Determine the parameters for this window and fill in the entry fields. ClickApply or Ok to accept the changes.

The Alarm Display X Icon List Folder (where X is the number entered instep 2) is now displayed in the System Tree (Figure 3-29 ).

4. This procedure creates a Groups Item in the system tree.

Refer to Table 3-21 for an explanation of the setting options available for theIconic Alarm Window tab.

Figure 3-31. Iconic Alarm Window



Table 3-21. Iconic Alarm Window


Window:

Iconic Alarming

Display Icon List Only

Identifies that Iconic Alarming is enabledor disabled.

Identifies whether the alarm window willonly display the icon list or will display theicon list in addition to the standard alarmtabs.

Enable (Default) orDisable

False (Default) or True

Alarm GroupConfiguration:

Display Returns Identifies whether unacknowledged orresettable returns are added to the alarmgroup or removed from the group.

True - (Default)Unacknowledged or resettablereturns are added to the alarmgroup and treated as alarms.When the return isacknowledged and reset, it isremoved from the group.

False - All returns areimmediately removed from thealarm group.

Process Diagrams:

Display Diagrams In Identifies the process diagram window thatdisplays the requested diagram.

Display Diagrams In - choosefrom pull-down menu.

Group CharacteristicsPosition:

1-8 Identifies which characteristics thegrouping will occur on.

Check the box of position (1-8).



3-12.3. Configuring Iconic Alarm Groups

The Alarm Group Window defines the specific alarm group information such as,position, bitmaps displayed, and grouping criteria. For each group, up to 10different diagrams can be defined. A maximum of 200 groups can be defined foreach alarm window.

Use the following procedure to configure an icon group:

1. From the Groups Item, right-click and choose Insert New to display the NewGroup Wizard.

2. Enter the Group name and click Finish.

3. The Alarm Group Window appears (see Figure 3-32 ). Determine the groupparameters in this window (see Table 3-22 ).

4. Click Apply or Ok to accept these changes. A Diagrams Item is now createdunder the Group item.

Table 3-22 provides an explanation of the setting options available in the AlarmGroup window.

Figure 3-32. Alarm Group Window



Note

The quotation marks (“) used in the followingtable are for emphasis only. Do not type thequotation marks in the value field.

Table 3-22. Alarm Group Window


Position:

Row

Col

Identifies the position where the icon willbe located, row and column.

Values (1-25) Row

Values (1-8) Column

Bitmap Files:

In Alarm Bitmap

Not in Alarm Bitmap

Identifies the icon that will be displayed fora group in alarm and for a group not inalarm.

Name of the bitmap file is displayedin the value field.Enter the file name only. Do not addthe file path.

Plant Area GroupingCriteria

Defines the characteristics that a point musthave in order to be a member of the groupfor the specified position. The positions thatare enabled map back to the positions thatwere selected in the Iconic Alarm window.

Entry field positions (1-8).To specify a range, type in thecharacteristics you want to match.The “.” character can be used tospecify a range. If the user does notwant to specify a range, thewildcard “-” can be used to matchall characteristics. Examplesinclude: ABCEFG, A.G, “-”.

Priority GroupingCriteria:

Identifies the priorities that make up thegroup.

Select the priorities that will be usedin the grouping criteria.



3-12.4. Configuring Iconic Alarm Diagrams

Use the following procedure to configure the Diagram Folder:

1. Right-click on the Diagram Item, select Insert New and an Insert New DiagramWizard appears (see Figure 3-33 ).

2. Fill in the diagram name and click Finish.

3. A New Diagram screen appears (see Figure 3-34 ). Insert the appropriateDiagram Number and Function.

4. Select Apply or Ok to accept the changes.

Figure 3-33. Insert New Diagram Wizard



Table 3-23 explains the options available in the New Diagram Window.

Note

The configuration described in this sectionmust be downloaded in order for the changesto take effect. See Section 13 for informationon Downloading changes to a Drop.

Figure 3-34. New Diagram Window

Table 3-23. New Diagram Window


Diagram Function Identifies the diagram that can be viewedfrom the icon list.

Display Diagram

Diagram Number Identifies the number of the diagram thatcan be displayed.

Valid diagram numbers1 through 65,535

Group Number Identifies the Point Group number. Values 0 through 5,0000 = No Point Group


3-13. Bitmap Configuration


The Bitmap folder is used to create and define which icons will be shown whenusing Iconic Alarming. An icon is saved as a bitmap file. For further information onIconic Alarming, see Section 3-12.

3-13.1. The Bitmap Folder

Use the following procedure to configure the Bitmap Files Item:


2. Drill down to the Bitmap Files Item by navigating through the following path:

Studio System TreeSystem Item (or the appropriate level such as, Network, Unit or Drop)Configuration ItemAlarm ItemBitmaps ItemBitmap Files Item (see Figure 3-35 )

If an Alarm item does not appear in the system tree, see Section 3-2.



Sample Icons, provided by Emerson, are located in the WorkPad window.)

3. Select the icon you wish to view and the icon is launched in the Windows defaultPaint program (see Figure 3-36 ).

Note

All bitmaps must be 64 x 64. The user isresponsible for supplying bitmaps to use iniconic alarming. Samples are provided in theSystem Bitmap folder. Bitmap files are savedby using the Save option. Do not use theSave As option.

Figure 3-35. Bitmap Files



Inserting a New Icon

You may insert an icon of your choice. Use the following procedure to insert anicon:

1. Right-click on the Bitmap Files Item.

2. Select Insert New from the menu and the New Bitmap Wizard appears (seeFigure 3-37 ).

3. Enter the bitmap name (without the .bmp extension) and click the Finishbutton.

Figure 3-36. Sample Alarm Icon Displayed in the Default Paint Program



Figure 3-37. New Bitmap Wizard



Importing an Icon

You may import a bitmap file from another source.

1. To do this, right-click on the Bitmap Files item and select Import.

2. The Bitmap Browse Window appears (see Figure 3-38 ). Enter the requiredinformation and click Open.

Note

The configuration described in this sectionmust be downloaded in order for the changesto take effect. See Section 13 for informationon downloading changes to a drop.

Figure 3-38. Bitmap Browse Window


Section 4. Historian Configuration


This section discusses the configuration of the Historian.

4-2. Introduction

The Historian screen contains the configuration information required to perform theretrieval of historical data. This is where the system’s eDB is defined. Additionally,if it is required for a system, the PI Server is defined here. The Historian object isonly located at the system level (see Figure 4-1).

Figure 4-1. Historian Icon in Studio System Tree


4-3. Configuration Procedure


Use the following procedure to configure a Historian item:


2. Navigate to the Historian Item by using the following path:Studio System TreeSystem ItemConfiguration ItemHistorian Item (see Figure 4-1)

3. Double-click on the Historian Item and select a Historian from the workpadwindow.

4. A Historian configuration window appears (see Figure 4-2). Set the desiredparameters, then choose Apply or Ok to accept these changes.

Table 4-1 explains the setting options available in the Historian Configurationwindow.

Figure 4-2. Historian Configuration Window



Note


Table 4-1. Historian Configuration WIndow


eDBs 1 - 5

eDB

Host Name

IP Address

Identifies whether the system has aneDB.

Host name for the eDB machine.

IP address for the eDB machine.

Disabled or Enabled.

Must be enabled for HistoricalTrends and Historical Reviews.

PI Server

PI Server

Host Name

IP Address

Port

Identifies whether the system has a PIHistorian.

Host name of the PI Server.

IP address of the PI Server.

Port number for the PI Server. Defaultis 5450.

Disabled or Enabled

Must be enabled for HistoricalTrends.Historical Reviews are notsupported.


Section 5. MMI Configuration


This section discusses the Man Machine Interface (MMI) configuration that appliesto the Ovation displays on the Operator Station drop.

Configuration can be done at any level in the Ovation Developer Studio SystemTree. Specific drop configuration must be done at the drop level. The lowest levelof configuration overrides the higher levels of configuration.

The following topics are included in this section:

• Inserting a New MMI Window (Section 5-2).

• Configuring an Existing MMI Folder (Section 5-3).


5-2. Inserting a New MMI Window


Use the following procedure to insert and configure a new MMI window:


2. Navigate to the MMI Item by using the following path:

Studio System TreeSystem Icon (or appropriate level such as, Network, Unit, or Drop)Configuration IconMMI Item (see Figure 5-1 )

3. Right-click on the MMI Item and select Insert New from the pop-up menu.

4. A New MMI window appears (see Figure 5-2 ). Set the desired parameters, thenchoose Apply (window remains open) or Ok (dismisses window) to accept thesechanges.

Table 5-1 lists the MMI configuration parameters.



Figure 5-1. MMI Item in Studio System Tree



Refer to Table 5-1 for a list of available options for the New MMI window.

Figure 5-2. Insert a New MMI Window


5-3. Configuring an Existing MMI Folder


Use the following procedure to configure the MMI Folder in the Developer Studio:


2. Navigate to the MMI Folder by using the following path:

Studio System TreeSystem Icon (or appropriate level such as, Network, Unit, or Drop)Configuration IconMMI Folder (see Figure 5-1 )

3. Double-click to Open the MMI object in the WorkPad window. The MMIOperator Station Configuration window will be displayed (as shown inFigure 5-3 ).

4. Make the desired changes and select Apply or Ok to accept the changes.

Figure 5-3. MMI Operator Station Configuration Window



Table 5-1 lists the available Options for the MMI Operator StationConfiguration Window.

Table 5-1. Operator Station Configuration Window and New MMI Window Topics


Process Point Quality Determines how the quality of apoint will effect how the value isdisplayed. A blank value fieldmeans that value will always beshown. When the field is set to TagValues with Nongood or BadQuality, the tag character isdisplayed instead of the value.

Blank (Default)

Tag Values with NongoodQuality (any quality otherthan Good)

Tag Values with BadQuality

Quality Check Symbol Displays this character (tag) insteadof the value for the Process-PointQuality Check.

X (Default)

Show Alarm Colors Determines whether the alarmsystem colors will be used todisplay the value and status of apoint on all Operator Station UIs.

Show (Default)

Do Not Show

Alarm Color Defines the color of the value fieldto be used when a point is in alarm(providing Show Alarm Colors isset to Do Not Show). If the NoAlarm Color box is checked, thealarm color is not used.

No Alarm Color (Default)

Select from a pull-downmenu.

Value Color Defines the color of the value fieldto be used when a point is NOT inalarm (providing Show AlarmColors is set to Do Not Show). If theNo Value Color box is checked, thevalue color is not used.

No Value Color (Default)


Quality Color Sets the color of the qualitycharacter for all Operator Ovationsystems that display a value field. Ifthe No Quality Color box is checked,the quality color is not used.

Magenta (Default)




Note



Section 6. OPC

6-1. Overview

OPC (OLE for Process Controls) is a “set of standard OLE/COM interfaceprotocols intended to foster greater interoperability between automatic/controlapplications, field systems/devices, and business/offices applications in the processcontrol industry” (from “OPC Overview” by the OPC Task Force, October 1998).

OPC provides a standard mechanism to enable industrial systems from differentvendors to communicate with each other. OPC also provides communicationbetween the same vendor equipment on different networks. In OPC, servers are datasources. The data is made available to OPC clients, which connect to the servers andrequest data of interest.

OPC defines the OPC Servers that the Ovation software can be connected to.Diagonally, it will provide a mapping between an OPC tag name and a logical namethat is used in the Process Diagrams, the Graphics Builder, and the Trend System.

OPC is only configurable at the System level in the Ovation Developer Studiosystem tree.

6-2. Configuring OPC

Use the following procedure to configure OPC:

1. Drill down to the OPC icon by navigating through the following path:Studio System TreeSystem IconConfiguration IconOPC Icon



2. Double-click to open the OPC icon and the OPC Servers will appear in theworkpad window.

Figure 6-1. OPC in System Tree



3. Choose an OPC Server from the workpad window and double-click to open.The OPC Server window will appear (see Figure 6-2). Proceed to step 5.

4. If an OPC Server does not exist or you would like to add a new one, right-clickon the OPC icon and select Insert New from the pop-up menu. A New OPCServer window appears (see Figure 6-2).

5. A Browse button is located at the end of the ProgID field. Click this button tobrowse OPC Servers. A Selection window will appear (see Figure 6-3).

6. Choose an OPC Server and click Ok.

7. The OPC Server window will appear (see Figure 6-2). The ProgID and CLSIDfields will be complete.

8. Make configuration changes and select Apply or Ok to accept the changes.

Figure 6-2. OPC Server Configuration Window

Figure 6-3. Browse Selection Window

Browse Button



d

d

9. The configuration changes you made will not take effect until they aredownloaded and the drop is rebooted. See Section 13 for information ondownloading changes to a drop.

Table 6-1 explains the setting options available in the OPC Server Configurationwindow.

Table 6-1. OPC Server Configuration


Logical Name Logical name used as a mapping to thefull OPC tag name,

Node Machine name or IP address where theOPC server is loaded.

ProgID Program identification string whichidentifies an OPC Server.

Automatically entered when selectewith the Browse button.

User may also type in this field.

CLSID A Universally Unique Identifier (UUID)that identifies a type of ComponentObject Model (COM).

Automatically entered when selectewith the Browse button.

User may also type in this field.


Section 7. Configuring the OvationKeyboard


This section discusses an additional operator input device known as the OvationKeyboard (also known as the Membrane Keyboard). This device allows theOperator to access data acquisition and control applications. For additionalinformation on using the Ovation Keyboard, refer to “Ovation Operator StationUser Guide” (WIN20).

The following topics are discussed in this section:

• Ovation Keyboard overview (Section 7-2).

• Adding the Ovation Keyboard to a Drop (Section 7-3).

• Configuring an Existing Ovation Keyboard (Section 7-4).

• Configuring Iconic Alarming (Section 7-5).

• Defining Ovation Keyboard Keys (Section 7-6).


7-2. Ovation Keyboard Overview


The Ovation Keyboard configuration allows the user to configure either the stndardOvation Keybord or the Alarm Panel. The Ovation Keyboard contains 48 userdefined keys in addition to the standard keyboard functions. The Alarm Panelcontains 96 user defined keys.

The Ovation keyboard is connected to the station serial port. It allows the user toexecute a set of standard functions from the keyboard. Each key can be configuredas a custom key or an alarm group key. The backlit keys corresponding to thecustom keys do not light. To configure an Ovation Keyboard, an adapter must beused. The cable and adapter will be provided by Emerson Process Management.

The alarm group keys can be configured to blink, turn on, and turn off to identifythe alarm status information about the group. When an alarm group does not containany points in alarm, the key corresponding to the alarm group is off (not lit). Ifblinking is disabled and a group contains points in alarm, the key corresponding tothe alarm group is lit. If blinking is enabled and a group contains points in alarm,the key corresponding to the alarm group will be in one of two states:

For iconic alarming, the user also specifies:

• Whether returns are considered to be an alarm.

• Whether blinking is enabled or disabled for alarm groups.

• Grouping criteria.

BLINKING - At least one unacknowledged alarm is present in the group.

SOLID - All alarms in the group are acknowledged.



The layout of the Ovation keypad is shown in Figure 7-1 . The keypad is numberedwith the upper left key defined as custom key 1. Each row is then numberedsequentially left to right as shown below:

Figure 7-1. Layout of Custom Keypad on Ovation Keyboard

Custom Key 37

Custom Key 1

Custom Key 48

Custom Key 12


7-3. Adding the Ovation Keyboard to a Drop


Note

The keyboard can be configured at theSystem, Network, Unit, or Drop level.However, if only certain drops havekeyboards connected, then only those dropsshould be configured.

Use the following procedure to add an Ovation Keyboard to a Drop:


2. Drill down to the Ovation Keyboard item using the following path:

Studio System TreeSystem ItemNetwork ItemUnit ItemDrop ItemDrop number of your choiceConfiguration ItemOvation Keyboard Item (see Figure 7-2 )



3. Right-click the Ovation Keyboard item and select Insert New from the pop-up menu.

4. A New Ovation Keyboard Window appears (see Figure 7-3 ). Select Enabledor Disabled. Choosing Enable enables the keyboard and selecting Disableallows the user to disable the keyboard without deleting the object.

5. The Serial Port field allows you to define what serial port the Ovation Keyboardis connected to.

Figure 7-2. Ovation Keyboard Item in Studio System Tree



6. The Keyboard Type field allows you to choose to configure an Alarm Panel oran Ovation Keyboard. The Alarm Panel has 96 valid keys, the Ovation keyboardhas 48 valid keys.


8. The configuration changes you made will not take effect until they aredownloaded to the drop. See Section 13 for information on downloadingchanges to a drop

9. To continue with configuration, refer to Section 7-5.

Figure 7-3. New Ovation Keyboard Window


7-4. Configuring an Existing Ovation Keyboard


Use the following procedure to configure an existing Ovation Keyboard on a Drop:


2. Drill down to the Ovation Keyboard Item using the following path:

Studio System TreeSystem ItemNetwork ItemUnit ItemDrop ItemDrop Number of your choiceConfiguration ItemOvation Keyboard Item

3. Right-click the Ovation Keyboard item and select Open from the pop-upmenu. The Ovation Keyboard window appears (see Figure 7-4 ).

4. The Ovation Keyboard window allows you to enable or disable the OvationKeyboard. This tab allows the user to disable the keyboard without deleting theobject.

5. The Keyboard Type field The Keyboard Type field allows you to choose toconfigure an Alarm Panel or an Ovation Keyboard. The Alarm Panel has 96valid keys, the Ovation keyboard has 48 valid keys.

6. The Serial Port field allows you to define what serial port the Ovation Keyboardis connected to.





Figure 7-4. Ovation Keyboard Window


7-5. Configuring Iconic Alarming


7-5.1. Overview

The Iconic Alarm tab defines whether iconic alarming is used in conjunction withthe keyboard. It also specifies whether blinking is enabled and if returns aremaintained as part of the alarm group. The user selects which characteristicposition(s) will be used in the Plant Area Grouping criteria.

7-5.2. Procedure

Use the following procedure to configure the Iconic Alarms tab:

1. Using the Horizontal scroll bar, in the Ovation Keyboard window, scroll toselect the Iconic Alarms tab (see Figure 7-5 ).





Refer to Table 7-1 for the available options for the Iconic Alarms tab.

Figure 7-5. Iconic Alarms Tab



Table 7-1. Iconic Alarms Tab


Alarm GroupConfiguration:

Alarm Interface toKeyboard

Enable Blinking

Display Returns

This field specifies if the OvationKeyboard is enabled or disabled foriconic alarming.

Identifies whether an alarm groupkey will blink when the groupcontains unacknowledged alarms.

Identifies whether unacknowledgedor resetable returns are added to thealarm group or removed from thegroup.

Enabled orDisabled (Default)

False orTrue (Default)

False orTrue (Default)

Group CharacteristicsPositions:

Positions 1-8 Identifies which characteristicpositions the grouping will occuron.

Check box for each position.


7-6. Defining Ovation Keyboard Keys


Use the following procedure to define the Ovation Keyboard keys:


2. Drill down to the Ovation Keyboard item using the following path:

Studio System TreeSystem ItemNetwork ItemUnit ItemDrop ItemDrop number of the drop you wish to configureConfiguration Item

3. Double-click to open the Ovation Keyboard item and a Keys folder appears.

4. Right-click on the Keys folder to add custom keys.

5. Select Insert New from the pop-up menu and a Wizard window appears. If keysexist, click Open from the pop-up menu.

6. Enter the key number you want to configure (key numbers 1 - 48 correspond tothe key on the keyboard) and click Finish. A New Key Definition Windowappears (see Figure 7-6 ). This window contains two tabs: the Key Definitiontab and the Alarm Group tab.

7-6.1. Key Definition Tab

The Key Definition tab provides different fields for the particular function youselect in the tab (see Figure 7-6 ).



To configure Key Definition, use the following procedure:

1. For each function, select Alarm Key or Custom Key to define what type of keyyou desire.

2. Select Function by selecting the down arrow to display function choices. Thecustom key function choice may lead to the Key Definition tab requiringadditional information (see Figure 7-7 through Figure 7-11 ).

3. You can save configuration changes after each tab is configured, or you can saveall changes after all of the tabs in a window have been configured. Select Applyto save changes and leave the window open, or select Ok to save the changesand close the window. If Alarm Key was selected, enter the required data on theAlarm Group tab and then select Apply or Ok.


Figure 7-6. Key Definition Tab



If additional information is required, the following figures (see Figure 7-7 throughFigure 7-12 ) may appear. Function choices that require completing additional fieldsare:

• Display Diagram (Figure 7-7 )

• Trend Point (Figure 7-8 )

• Point Information (Figure 7-9 )

• Execute Program (Figure 7-10 )

• Display Diagram Window (Figure 7-11 )

Table 7-8 further explains all of the setting options available in the Key Definitiontab.



Table 7-2 explains the additional fields that require information when the DisplayDiagram function is chosen.

Figure 7-7. Display Diagram Function

Table 7-2. Display Diagram Function

Function Fields Description

Display Diagram Diagram Number

Group Number

Number of the diagram you would likedisplayed.

Defines the diagram group number0 through 5,000.0 = No Point Group.



Table 7-3 explains the additional fields that require information when the TrendPoint function is chosen.

Figure 7-8. Trend Point Function

Table 7-3. Trend Point Function

Function Field Description

Trend Point Point Name The name of the point you would likedisplayed in the trend window.



Table 7-4 explains the additional fields that require information when the PointInformation function is chosen.

Figure 7-9. Point Information Function

Table 7-4. Point Information


Point Information Point Name The name of the point you would likedisplayed in the point information window.



Table 7-5 explains the additional fields that require information when the ExecuteProgram function is chosen. Once the fields are complete in the Key Definitionwindow, the Executable Files window appears (see Figure 7-11 ).

Figure 7-10. Execute Program Function

Table 7-5. Execute Program


Execute Program Program Path

Parameters

File Name

The absolute path name of the program thatwill be initiated when the key is pushed.You can type this in, or click the Browsebutton to automatically fill this field.

Any additional parameters or argumentsfor this program.

The name of the executable file.

BrowseButton



Enter the executable File name and select Open (see Figure 7-11 ). The full pathname is now stored in the Program Path field in the Execute Program functionwindow (see Figure 7-10 ).

Figure 7-11. Executable Files

Table 7-6. Executable Files


The Browse button to theright of the Program Pathfield allows you to browsefor the program path.

File Name The name of the executable file.



Table 7-7 explains the additional fields that require information when the DisplayDiagram Window function is chosen.

Figure 7-12. Display Diagram Window Function

Table 7-7. Display Diagram Window


Display Diagram Window Window Number The number of the window (1-8) youwould like the diagram displayed in.



Table 7-8 further defines all of the setting options available in the Key Definitiontab.

Table 7-8. Key Definition Tab

Item Description Setting Option

Key Definition Defines the custom key on theovation keyboard to be used as aprogrammable button (key) or analarm key.

Custom Key (Default) orAlarm Key

Function Defines the function that the keywill perform when it is selected.

Displays a process diagram and apoint group from the keyboard.

Displays a trend point or trendgroup from the keyboard.

Enables the user to view or modifypoint data and starts the pointinformation program.

Allows you to search the databasefor points having specificcharacteristics or belonging to aparticular point group. Starts thepoint review program.

Allows you to view all points in thesystem database. Starts the pointviewer program.

Executes the user defined program.

Provides the ability to perform theAlarm Page Acknowledge function

Opens the alarm list.

Is used to identify the processdiagram window that the requesteddiagram will be displayed in.

Display Diagram

Trend Point or Trend Group

Point Information

Point Review

Point Viewer

Execute Program

Alarm Page Acknowledge

Open Alarm List

Display Diagram Window



7-6.2. Alarm Group Tab

1. Use the horizontal scroll bar to select the Alarm Group Tab (see Figure 7-13 )in the New Key Definition Window.

2. Make the appropriate changes in the Alarm Group tab (see Table 7-9 ).



See Table 7-9 for an explanation of the value field setting options for the AlarmGroup tab.

Figure 7-13. Alarm Group Tab



Note


Table 7-9. Alarm Group Tab


Plant Area Grouping:

Position 1-8

Defines the characteristics that apoint must have in order to be amember of the group for thespecified position. CharacteristicPositions that are enabled are basedon the selection made in the IconicAlarms (Ovation Keyboard) tab.The positions that are enabled mapback to the positions that wereselected in the Iconic Alarmwindow. To specify a range, type inthe characteristics you want tomatch. If you do not want to specifya range and do not want to type in allof the characters, the “.” charactercan be used to specify a range. If theuser does not want to specify arange, the wildcard “-” can be usedto match all characteristics.

Value Entry Field.For example, A.G,ABCDEFG, “-”.

NoteThe quotation marks (“) areused for emphasis only. Donot type the quotation marksin the entry field.

Priority GroupingCriteria:

Grouping Criteria 1-8 Defines the priorities that make upthe group.

Check box


Section 8. Process Diagram System


This section describes the Process Diagram System (PDS) configuration.

The Process Diagram System consists of graphical images that represent actualplant process control equipment. The operator has direct interaction with theprocess flow via system display “diagrams.” Typically, the Operator Station candisplay up to eight process diagrams or icons (which open to custom diagrams). Themethod for building process diagrams is discussed in“Ovation Graphics BuilderUser Guide” (WIN90) and “Ovation Graphics Language Reference Manual”(WIN91).

For information on viewing graphic process diagrams see “Ovation OperatorStation User Guide” (WIN20).


• Inserting New Process Diagrams (Section 8-2).

• Configuring Process Diagrams (Section 8-3).

• Inserting New Color Definitions (Section 8-4).

• Configuring Process Diagram Color Definitions (Section 8-5).


8-2. Inserting New Process Diagrams


Use the following procedure to insert new Process Diagrams:


2. Drill down to the Process Diagrams Folder by using the following path:

Studio System TreeSystem Item (or appropriate level such as, Network, Unit or Drop)Configuration ItemProcess Diagrams Folder (see Figure 8-1 )

Figure 8-1. Process Diagrams Folder in Studio System Tree



3. Right-click on the Process Diagrams folder. Select Insert New from the pop-up menu and the Process Diagrams Configuration window appears (see Figure8-2 ).

4. Make the desired changes in the Process Diagrams Configuration window. Afterthe configuration is complete, select Apply (window remains open) or Ok(dismisses window) to accept the changes.

Table 8-1 explains the setting options for the Process Diagrams ConfigurationWindow.

Figure 8-2. Process Diagrams Configuration Window


8-3. Configuring Process Diagrams

8-3. Configuring Process Diagrams

Use the following procedure to configure Process Diagrams:


2. Drill down to the Process Diagrams Folder by using the following path:

Studio System TreeSystem Item (or appropriate level such as, Network, Unit or Drop)Configuration ItemProcess Diagrams Folder

3. Right-click on the Process Diagrams folder. Select Open from the pop-upmenu and the Process Diagram Configuration window appears (see Figure 8-2 ).

4. Make the desired changes in the configuration tab. After the configuration iscomplete, select Apply or Ok to accept the changes.

Table 8-1 explains the setting options for the Process Diagrams ConfigurationWindow.

Table 8-1. Process Diagrams Configuration Window Topics


Zoom Corner Allows the selection of a specific areaof the diagram to enlarge.

False (Default)True

Disable Fixed Size Position Override the fixed size and fixedposition parameters set by the GraphicsBuilder when the diagram wascompiled.

FalseTrue (Default)

Number of Previous Views Determines the number of previousscreens that can be viewed afterzooming or after displaying newdiagrams

15 (Default)Values from 0 through 50

Number of Local Windows Number of process diagram windowsallowed on a local Operator Station.

1–84 (Default)

Raise/Lower RequestTimeout

Maximum elapsed time before anoperator must re-issue a raise/lowercommand.

60 seconds (Default)Values from 0 through 60


8-4. Inserting New Color Definitions


Note

Color definitions are only located at theSystem level.

Use the following procedure to insert new color definitions for Process Diagrams:

1. Double-click to open the Process Diagrams item in the System level in theStudio System Tree (see Figure 8-3 ). A Colors folder appears.

2. Double-click on the Colors folder and a Color Definitions folder appears (seeFigure 8-3 ).

3. Right-click on the Colors Definitions folder and select Insert New from thepop-up menu.

4. An Insert New Color Definitions wizard appears (see Figure 8-4 ).

Figure 8-3. Color Definitions Folder in System Tree



5. Enter a new color name and click Finish. A New Color Definitions windowappears (see Figure 8-5 ).

6. Choose the color from the color palette. The color palette is accessed using thepull-down menu. Select Apply or Ok to accept the change.

7. The new color is now located in the WorkPad window in the Ovation DeveloperStudio (see Figure 8-6 ).

Figure 8-4. Insert New Color Definitions Wizard

Figure 8-5. New Color Definitions Window


8-5. Configuring Process Diagram Color Definitions


Note

Configuration of Process Diagram ColorDefinition can only be done at the SystemLevel in the Developer Studio system tree.

8-5.1. Procedure

Use the following procedure to update an existing color definition for ProcessDiagrams:

1. Drill down to the Process Diagrams Folder by using the following path:Studio System TreeSystem ItemConfiguration ItemProcess Diagrams Folder

2. Double-click to open the Process Diagrams folder in the System Tree.

3. Sample color choices are located in the workpad window (see Figure 8-6 ). Thecolor may be adjusted by using the pull-down menu in the color definition tab.Choose the color of choice.



4. Select Apply or OK to accept the changes.

Table 8-2 provides an explanation of the Process Diagram Configuration topics.

Figure 8-6. Process DIagram Color Definition

Table 8-2. Color Definition Tab


Color Selection:

Color Color that is associated with thecolor name.

Choose from the color palettethat is accessed from the pull-down menu.



Note



Section 9. Configuring Quality


This section discusses the configuration of Point Quality States (see Table 9-1). TheOvation system supports four Quality States: Good, Fair, Poor, and Bad. EachQuality State indicates the condition of the point to the operator.

The system can be configured to display an additional quality reason clarifier afterthe quality description. If the reasons are to be displayed, the system must beconfigured to set the order of precedence for the quality reasons, in addition to thetext that will be displayed for each reason.

Quality configuration is done through the Ovation Developer Studio package in theQuality folder of the Studio System Tree.

For further information on Quality, refer to “Ovation Operator Station User Guide”(WIN20).


• Quality Status (Section 9-2).

• Quality Configuration (Section 9-3).


9-2. Quality Status

9-2. Quality Status

Table 9-1 defines Quality status when used with the Operator Station.

Table 9-1. Quality State Definition

Term

Quality Status TypicalDisplay

Description

Good None The data is usable as it stands.

Fair F Can be the result of two factors:1. An Operator entered the value.2. The result of a Quality CheckingAlgorithm in the application (Looppropagation).

Poor P Generated from certain algorithms if someinputs were bad and some were good.

Bad B Can be the result of four factors:1. Faulty input hardware2. Input out of specified sensor range(analog)3. The removal of a point from scan4. The result of a Quality CheckingAlgorithm (Loop propagation).

Timed Out T The point is not being updated. The dropthat broadcasts the point is probably off thehighway.

The formal definition of “quality” does notinclude the status “Timed Out”. However,window displays that contain process pointstatus usually include Timed Outinformation in the same screen location asthe four “Quality” items.


9-3. Quality Configuration


9-3.1. Inserting a New Point Quality

You can use the following procedure to insert a New Point Quality:


2. Navigate to the Quality Folder by using the following path:

Studio System TreeSystem Item (or appropriate level such as, Network, Unit, or Drop)Configuration ItemQuality Folder (see Figure 9-1)



3. Right-click on the Quality folder and select Insert New from the pop-up menu.

4. A New Quality Configuration Window will appear (see Figure 9-2)

5. Proceed with configuration by following Steps 4 through 7 in Section 9-3.2.

Figure 9-1. Quality Folder in Studio System Tree



9-3.2. Configuring the Quality Folder

You can use the following procedure to configure the Quality Folder in theDeveloper Studio:


2. Navigate to the Quality Folder by using the following path:

Studio System TreeSystem Item (or appropriate level such as, Network, Unit, or Drop)Configuration ItemQuality Folder (see Figure 9-1)

3. Double-click on the Quality object in the WorkPad window and a QualityConfiguration Window appears (see Figure 9-3 and Figure 9-4). This windowcontains two tabs:

• Quality Tab

• Quality Reasons Tab

4. Use the horizontal scroll bar to access the Quality Tab.

Figure 9-2. New Quality Configuration Window





The following Table 9-2 explains the setting options available in the Quality Tab.

Figure 9-3. Quality Tab



7. Scroll to select the Quality Reasons tab by using the horizontal scroll bar inthe Quality Configuration window (see Figure 9-4).



Table 9-2. Quality Tab


Bad Quality Character The Ovation System supports fourquality states: Good, Fair, Poor, andBad, plus the condition Timed-out.Each indicates the condition of thepoint to the Operator and to theAlgorithm

B (Default)

Bad Quality String Bad (Default)

Poor Quality Character P (Default)

Poor Quality String Poor (Default)

Fair Quality Character F (Default)

Fair Quality String Fair (Default)

Good Quality Character G (Default)

Good Quality String Good (Default)

Time Out Quality Character T (Default)

Time Out Quality String Timed Out (Default)



Q

The following table (Table 9-3) lists available options for the Quality Reasons Tab.

Figure 9-4. Quality Reasons Tab

Table 9-3. Quality Reasons Tab


uality Reasons Order of precedence. 1 being thehighest and 14 being the lowest.

Values 1-14



Q

Q

uality Reason Name Identifies the Quality Reason. Blank (no quality reasondefined)Latched QualityPoint Timed OutTagged OutHardware ErrorOscillating PointSensor CalibrateScan RemovedData Link FailureSubstituted Entered ValueAlgorithm ApplicationTest ModeUser DefinableEngineering LimitReasonability Limit

uality Reason Character Character displayed for thecorresponding quality reason name.

Entry Field

Table 9-3. Quality Reasons Tab (Cont’d)



Section 10. Configuring Review


This section discusses point review configuration. For more information on thePoint Review function, see “Ovation Operator Station User Guide” (WIN20).

The configuration of the point review is done through the Ovation DeveloperStudio, in the Review folder of the System Tree (see Figure 10-1). Configurationcan be done at any level in the Studio System Tree. Specific drop configuration mustbe done at the drop level in the Studio. The lowest level of configuration overridesthe higher level of configuration.


• Review Folder (Section 10-2).

• Configuring Review Characteristics (Section 10-3).



Figure 10-1. Review Folder in System Tree


10-2. Review Folder

10-2. Review Folder

The Point Review function provides information on a set of points that meetoperator-specified criteria (characteristics and/or current status). It allows the userto examine points on the Ovation Data Highway that have matching characteristicsand/or matching statuses. These reviews can be printed or viewed on the screen.

10-2.1. Inserting a New Point Review

Use the following path to insert a New Point Review (see Figure 10-2):


2. Drill down to the Review folder using the following path:Studio System TreeSystem Item (or appropriate level such as, Network, Unit, or Drop)Configuration ItemReview Folder (see Figure 10-1)

3. Right-click on the Review folder and select Insert New from the pop-up menu.The New Point Review Window appears (see Figure 10-2).

4. Make the desired changes and select Apply (window will remain open) or Ok(closes window) to accept the changes. Refer to Table 10-1 for a description ofthe available options. A Review Characteristics folder is now created andlocated beneath the Review folder in the system tree.

Figure 10-2. New Point Review Window


10-2. Review Folder

10-2.2. Configuring the Point Review Folder

Use the following procedure to update an existing Point Review Window:


2. Drill down to the Review folder by navigating through the following path:Studio System TreeSystem Item (or appropriate level such as, Network, Unit, or Drop)Configuration ItemReview Folder (see Figure 10-1)

3. Right-click on the Review folder and select Open from the pop-up menu. ThePoint Review Window appears (see Figure 10-3).

4. Make the desired changes and select Apply or Ok to accept the changes.

Figure 10-3. Point Review Window


10-2. Review Folder

Table 10-1 explains the options available in the Point Review window.

Table 10-1. Point Review Window Configuration Topic


Background Color Selects the background color ofthe Point Search windows.

Grey80 (Default)Select from a pull-down menu.

Foreground Color Selects the foreground color ofthe Point Search windows.

Black (Default)Select from a pull-down menu.


10-3. Configuring Review Characteristics


The Review Characteristics folder defines the available Point Search characteristicsand their definitions. It also includes the definitions for up to 700 groups (sets ofcharacteristics).

Each process point can be associated with a set of eight alphanumeric characterscalled the point characteristics. Each character within the set defines somecharacteristic of the point, such as the plant area or type of equipment. The meaningof each characteristic is dependent on the character and its position. The firstcharacteristic is always used as the “destination” (for alarm functions) and is oftendefined as the plant area. The other positions may be defined in any way.

Each point review group consists of up to eight predefined characteristics. By usinggroups, the user can select all eight characteristics at once by selecting a groupinstead of selecting one characteristic at a time. A maximum of 700 groups can bedefined.

The following sample table shows a hypothetical listing of characteristics.

CharacterPosition

(maps to tabposition 1-8) Description

Character(maps to the characteristics

for each value)Definition

(maps to the description for each value)

1 Plant Area ABCD

E - MNOPQ

R - Z

Unit 1 Air SystemUnit 1 BoilerUnit 1 CondensateUnit 1 GeneratorUnit 1 SpareUnit 2 Air SystemUnit 2 BoilerUnit 2 CondensateUnit 2 GeneratorUnit 2 Spare

2 Subsystem GSWOE

GasSteamWaterOilElectrical



10-3.1. Creating a New Review Characteristics Folder

Use the following procedure to create the Review Characteristics Folder:

1. Navigate to the Review Folder using the following path:Studio System TreeSystem Item (or appropriate level such as, Network, Unit, or Drop)Configuration ItemReview Folder

2. Right-click on the Review folder and select Insert New from the pop-up menu.A New Review Characteristics window appears (see Figure 10-4). The NewReview Characteristics Window contains eight Position Tabs. Position tabs givedefinitions for valid characters for a specific position within the character set.You can access these Tabs by using the horizontal scroll bar at the bottom of thewindow (see Figure 10-4). Values are accessed by using the vertical scroll barin this window.

3 Equipment PILVF

PumpIP TurbineLP TurbineValveFan

4 Designator ABCDEW12

ABCDEastWest12

5 Parameter TPVF

TemperaturePressureVoltsFlow

6 - 8 Spare

CharacterPosition

(maps to tabposition 1-8) Description

Character(maps to the characteristics

for each value)Definition

(maps to the description for each value)





5. See Table 10-2 for an explanation of the setting options for the New ReviewCharacteristics window.

Figure 10-4. New Review Characteristics Window

VerticalScroll Bar

Scroll BarHorizontal



10-3.2. Configuring an Existing Review Characteristics Folder

Use the following procedure to update an existing Review Characteristic:

1. Navigate to the Review Characteristics Folder using the following path:Studio System TreeSystem Item (or appropriate level such as, Network, Unit, or Drop)Configuration ItemReview Folder

2. Double-click to open the Review folder and the Review Characteristics folderappears.

3. Right-click on the Review Characteristics folder and select Open from thepop-up menu. The Review Characteristics window appears (see Figure 10-5).



4. The Review Characteristics Window contains eight Position Tabs. Position tabsgive definitions for valid characters for a specific position within the characterset. You can access these Tabs by using the horizontal scroll bar at the bottomof the window (see Figure 10-5). Values are accessed by using the vertical scrollbar in this window.


Figure 10-5. Review Characteristics Window

VerticalScroll Bar

HorizontalScroll Bar




Table 10-2 provides an explanation of the setting options for the ReviewCharacteristics Window.

Table 10-2. Review Characteristics Window and New Review Characteristics Window(Contains Eight Position Tabs)


Values (1-36):

Characteristic (A-Z) and (0-9)

Position 1 tab = Characteristics(A-Z)

Position 2 - 8 tabs =Characteristics (A-Z and 0-9)

Position 1 defines up to 26values.

Positions 2-8 defines up to 36values.

Characteristic in the searchcriteria. Definescharacteristics for eachvalue.

Pull-down menu used to select thespecific characteristics thatcorrespond to the value.

For example, Position 1 values 1-26map to the valid characters A-Z inthe first position of thecharacteristics field.

Position 2 values 1-36 map validcharacteristics A-Z plus 0-9 in thesecond position of thecharacteristics field, and so on.

Description Description for eachCharacteristic value. Thiscannot exceed 30 characters.

Entry field



10-3.3. Inserting a New Group

Defining a group allows you to define a set of characteristics to be used as searchcriteria. You may insert a new group by accessing the Group Folder in the Studiosystem tree.

Procedure

Use the following procedure to insert a new Group:


2. Drill down to the Groups folder by navigating through the following path:Studio System TreeSystem Item (or appropriate level such as, Network, Unit, or Drop)Configuration ItemReview FolderReview Characteristics Folder

3. Double-click on the Review Characteristics folder in the Studio System Tree(see Figure 10-1). A Group folder appears under the Review Characteristicsfolder.

4. Right-click on the Group folder and select Insert New from the pop-up menu.

5. A New Groups Wizard appears (see Figure 10-6). Enter the group number(1 -700) and click Finish.

6. A New Groups Window appears (see Figure 10-7). Enter a value for the groupdefinition characteristic and description and select Apply or Ok to accept thechanges.

Note

You can edit an existing Group by right-clicking onthe Group folder and selecting Open from the pop-up menu (see Step 4). Proceed by following Step 6above.



Figure 10-6. New Groups Wizard



The following Table 10-3 explains the options available in the New GroupsWindow.

Note

The configuration described in this section must bedownloaded in order for the changes to take effect.See Section 13 for information on downloadingchanges to a drop.

Figure 10-7. New Groups Window

Table 10-3. New Groups Window (Group Definition Tab)


Characteristics Characteristics used as the searchcriteria. This cannot exceed 8characters.

Entry field

Description Description of the character set.This cannot exceed 30 characters.

Entry field


Section 11. Trend Display


The Trend Display allows the user to examine data samples collected for points overvarious intervals on a graphical or tabular display. The display is updatedcontinuously with live information at a predetermined collection rate.

This section discusses the Trend Configuration Folder and the Trend Default Folderin the Ovation Developer Studio. Configuration can be done at any level in theStudio System Tree. Specific drop configuration must be done at the drop level inthe Studio. The lowest level of configuration overrides the higher level ofconfiguration.


• Trend Configuration Folder (Section 11-2).

• Trend Default (Section 11-3).


11-2. Trend Configuration Folder


The Trend Configuration user interface defines colors and default scales for digitalpoints to be used in the Trend Display window.

For more information on using the Trend Display function, see “Ovation OperatorStation User Guide” (WIN20) and “eDB Historian User Guide” (NT-0070).

Figure 11-1. Trend Configuration Folder in System Tree



11-2.1. Procedure

Use the following procedure to configure the Trend Configuration window:


2. Drill down to the Trend Item by navigating through the following path:

Studio System TreeSystem Item (or appropriate level such as, Network, Unit, or Drop)Configuration ItemTrend Item (see Figure 11-1)

3. Right-click on the Trend item and select Open from the pop-up menu. TheTrend Configuration window will appear (see Figure 11-2). If no Trend ispresent, right-click and select Insert New.

The Trend Configuration window contains two tabs:

• Trend Configuration

• Point Colors





Table 11-1 explains the setting options available in the Trend Window tab.

Figure 11-2. Trend Window Tab



Table 11-1. Trend Configuration WIndow


Tabular Trend Tabular Trend Order specifies thechronological order of the data in which thetabular trend values are printed.

Tabular Trend OrderForwardReverse (Default)

Scales Default High Scale defines the top limit ofthe trend scale for digital points not listed inthe default file.

Default Low Scale defines the bottom limitof the trend scale for digital points not listedin the default file.

Default High Scale3.0 (Default)

Default Low Scale-1.0 (Default)

Window Colors Background selects the background colorof the Trend Display windows.

Foreground selects the foreground color ofthe Trend Display windows.

Grid selects the color to be used for the gridlines on the Trend Display windows.

BackgroundBlack (Default)

ForegroundGrey80(Default)

GridMistyrose (Default)

Select from the Color Palette tochange any of the default valuesabove.



Point Colors Tab

The Point Colors Tab allows the user to define the colors used to plot the first eightpoints on the trend when they are in good quality and when they are in non-goodquality.

1. The Point Colors tab is accessed by using the horizontal scroll bar in the TrendConfiguration Window (see Figure 11-3).

2. Colors can be adjusted by clicking on the down arrow next to the color youwish to customize. See Section 3-11 for further information on customizingcolors.

Figure 11-3. Point Colors Tab





The following Table 11-2 explains the setting options available in the Point Colortab.

Table 11-2. Point Colors Tab


Good Quality Colors These parameters select the colorto be used for the plot of point X onthe trend when the quality of pointX is good.

Point 1 (GOOD)Red (Default)Point 2 (GOOD)Cyan (Default)Point 3 (GOOD)Green (Default)Point 4 (GOOD)Deep SkyBlue1 (Default)Point 5 (GOOD)Magenta (Default)Point 6 (GOOD)Orange (Default)Point 7 (GOOD)Plum (Default)Point 8 (GOOD)Tan (Default)

Select from the Color Palette tochange any of the default colorsabove.




Non-Good Quality Colors These parameters select the colorto be used for the plot of point X onthe trend when the quality of pointX is NOT good.

Point 1 (Not GOOD)Yellow (Default)Point 2 (Not GOOD)HotPink (Default)Point 3 (Not GOOD)PeachPuff4 (Default)Point 4 (Not GOOD)Azure2 (Default)Point 5 (Not GOOD)Black (Default)Point 6 (Not GOOD)DarkSeaGreen (Default)Point 7 (Not GOOD)Aquamarine2 (Default)Point 8 (Not GOOD)DarkGoldenrod (Default)

Select from the Color Palette tochange any of the default valuesabove.

Table 11-2. Point Colors Tab (Cont’d)


11-3. Trend Default

11-3. Trend Default

The Trend Default item allows you to define the process point data which is storedin mass memory for the trend data collection function. Configuration of trenddefaults is done through the Trend Default item The maximum number of defaultpoints is 1000. If a point has been entered into the Trend Default Configurationwindow, the trend screens can display all the data that has been collected for thatpoint. The trend is then continually updated with current information. See “eDBHistorian User Guide” (NT-0070) and “Ovation Operator Station User Guide”(WIN20) for more information on trends.

11-3.1. Inserting a New Trend Default

You can insert a new trend default by using the following procedure:


2. Drill down to the Trend Default folder by navigating through the following path:

System Item (or appropriate level such as, Network, Unit, or Drop)Configuration ItemTrend ItemTrend Defaults Item

3. Right-click on the Trend Defaults item and select Insert New from the pop-upmenu.

4. A New Trend Defaults wizard appears (see Figure 11-4). Enter a point name inthe value field and click Finish.

5. A Trend Defaults Definition window appears (see Figure 11-6). Enter therequired scale values and select Apply or Ok to accept the changes. The NewTrend Default now appears in the WorkPad window (see Figure 11-5).

6. After all of the Trend Defaults have been added, you must Download. SeeSection 13 for information on downloading.

See Table 11-3 for an explanation of the Trend Defaults Definition window.


11-3. Trend Default

Figure 11-4. New Trend Defaults Wizard

Figure 11-5. New Trend Default in WorkPad Window


11-3. Trend Default

11-3.2. Configuring an Existing Trend Default

You can configure an existing Trend Default by using the following procedure:


2. Drill down to the Trend Default item by navigating through the following path:

System Item (or the appropriate level such as Network, Unit, or Drop)Configuration ItemTrend ItemTrend Default Item

3. Double-click to open the Trend item and the Trend Default item appears.

4. Double-click to open the Trend Default item and a Trend Default Definitionwindow appears (see Figure 11-6).

5. Make the desired changes and select Apply or Ok to accept theses changes.

6. After updating all of the Trend Defaults, you must Download. See Section 13for information on downloading.

Figure 11-6. Trend Default Definition Window


11-3. Trend Default

Table 11-3 lists the parameters used to configure the Trend Defaults DefinitionWindow.

Table 11-3. Trend Defaults Definition Configuration Parameters


High Scale Value Top boundary of the trend display. Floating point value.Blank (Default)

Low Scale Value Bottom boundary of the trend display. Floating point value.Blank (Default)

Trend Duration Length of time appearing on a single“page” of the trend display.

Choose from pull-down menu.

Duration - Rate10 minutes (Default) - 1 second30 minutes - 3 seconds100 minutes - 10 seconds5 hours - 30 seconds10 hours - 60 seconds30 hours - 180 seconds100 hours - 600 seconds200 hours - 1200 seconds25 days - 3600 seconds33.3 days - 4800 seconds

Scale Linear or Logarithmic Linear (Default)Logarithmic


11-3. Trend Default

11-3.3. Trend Scale Examples

This example shows the effects of high and low scale values on trends.

Figure 11-7 illustrates the effects of different high and low scale values on trends ofanalog points.

Point A is scaled between 10.0 and -10.00, while Point B is scaled between 20.00and -5.00.

Figure 11-7. Trend Scale Using an Analog Point

A

B


11-3. Trend Default

Figure 11-8 illustrates the effects of different high and low scale values on trends ofdigital points. Point A is scaled between 5.00 and -5.00, while Point B is scaledbetween 10.00 and 0.00.

Digital points differ from analog points in that digital points always have a value of0 (off) or 1 (on). The high and low scale values specified for digital points indicatethe position of the trend line on the window and the height of the trend.

Figure 11-8. Trend Scale Using Digital Point

A

B


Section 12. SCADA Server

12-1. Overview

This section discusses the configuration of Ovation SCADA drivers and options.The following topics are included in this section:

• SCADA Server Introduction (Section 12-2).

• Inserting a new SCADA Driver (Section 12-3).

• Configuring an Existing SCADA Driver (Section 12-4).

• Configuring SCADA Options (Section 12-5).


12-2. SCADA Server Introduction


The Ovation SCADA Server is used to interface an Ovation system with anIntellution iFix SCADA Server. Ovation points can be mapped to SCADA tags toallow for the exchange of information such as current value, high and low limits,and so forth. Additionally, Ovation can retrieve event information from the SCADAsystem.

The Intellution iFix SCADA Server Software, when used in the context of theOvation SCADA Service is responsible for interacting with the numerous devicedrivers supported by the product. Data blocks are stored in the iFix SCADAdatabase and interact with the device drivers to transfer processed data to and fromthe devices.

The Ovation SCADA Server is responsible for reading and writing informationbetween the Ovation highway and the SCADA Database. It also sends Historicaland Fault Drop Events from the SCADA System to Ovation. The Ovation SCADAConfiguration File defines the mapping and event information of interest.

Figure 12-1 provides a diagram of the Ovation SCADA Server logical components.



Figure 12-1. SCADA Diagram


12-3. Inserting a New SCADA Driver


Use the following procedure to insert a new SCADA driver:

1. Drill down to the SCADA Drivers icon by navigating through the followingpath:Studio System TreeSystem IconConfiguration IconSCADA Drivers Icon (see Figure 12-2)

Figure 12-2. SCADA Drivers in System Tree



2. Right-click on the SCADA Drivers icon and select Insert New from the pop-upmenu. An Insert New SCADA Driver Wizard appears (see Figure 12-3).

3. Complete the Name and SCADA value fields and press Finish.

4. A New SCADA Driver window will appear (see Figure 12-4). Table 12-1explains the options in the New SCADA Drivers window.

5. Complete the fields and click Apply or Ok to save the configuration changes.

6. The New SCADA Driver will now appear in the System Tree under the SCADADrivers icon.

Note

SCADA Drivers are only configurable at the Systemlevel in the Ovation Developer Studio System Tree.

Figure 12-3. New SCADA Driver Wizard



Refer to Table 12-1 for an explanation of the fields in the New SCADA Driverwindow.

Figure 12-4. New SCADA Driver Window


12-4. Configuring an Existing SCADA Driver


Use the following procedure to configure an existing SCADA driver:


2. Right-click on the SCADA Driver in the workpad window and select Openfrom the pop-up menu. A SCADA Driver window will appear (see Figure 12-4).

3. Complete the fields and click Apply or OK to save the changes.


Refer to Table 12-1 for descriptions of the options in the SCADA Drivers window.

Table 12-1. New SCADA Drivers and Existing SCADA Drivers


Name Display name of the SCADADriver

This field can only be edited when theobject is initially installed. After theinitial installation, it is grayed-out.

SCADA Value Actual name of the SCADADriver. The SCADA value mustcorrespond to a driver known andinstalled on the Intellution system.The name value can be arbitrary,however, the SCADA valuecannot.

This field can only be edited when theobject is initially installed. After theinitial installation, it is grayed-out.

I/O Address Syntax Hint Driver specific syntax used foraccessing information. Refer tothe specific Driver manual formore information.

Entry field

Demand I/O Address SyntaxHint

Driver specific syntax used forforcing I/O on demand. Refer tothe specific Driver manual formore information.

Entry field



12-4.1. Configuring Hardware Options for SCADA Drivers

Each SCADA Driver may contain a set of Hardware Options. Hardware Optionsspecify the device control addressing format used to communicate with thehardware.

Procedure


2. Double-click to open the SCADA Driver.

3. Hardware Options and Signal Conditions will appear under the SCADA Driverin the System Tree.

4. Left-click the Hardware Options icon and the Hardware Options will appearin the workpad window.

5. Double-click to open the Hardware Option from the WorkPad window.Proceed to Step 7.

6. If a Hardware Option does not exist, or you want to create a new option, right-click and select Insert New from the pop-up menu. An Insert New HardwareOptions Wizard will appear (see Figure 12-5).

7. Complete the Name and SCADA Value fields in the wizard and click Finish.

8. A Hardware Options window will appear identifying the attribute name andvalue. These fields are grayed-out (see Figure 12-6).



Table 12-2 explains the options available in the Hardware Options Configurationwindow.

Figure 12-5. Insert New Hardware Options

Figure 12-6. Hardware Options Configuration



12-4.2. Configuring Signal Conditions for SCADA Drivers

Each SCADA Driver may contain a set of Signal Conditions. Signal Conditionsconvert raw data from drivers into a more useful format, for example, percent orgallons.

Procedure


2. Double-click to open the SCADA Driver.

3. Hardware Options and Signal Conditions will appear under the SCADA Driverin the System Tree.

4. Left-click the Signal Conditions icon and the Signal Conditions will appear inthe workpad window.

5. Double-click to open the Signal Condition from the workpad window. Proceedto step 6.ORIf a Signal Condition does not exist or you want to insert a new option, right-click and select Insert New from the pop-up menu. A New Signal ConditionsWizard will appear (see Figure 12-7).

6. Complete the Name and SCADA Value fields and click Finish.

Table 12-2. Hardware Options

Item Description

Name Name of the Hardware Option that is displayed on the userinterface.

SCADA Value Value of a hardware option known to the specific driver. Consult thespecific Driver manual for more information. It is written to theconfig file.



7. A Signal Conditions window will appear identifying the Attribute Name andValue. These fields are grayed-out (see Figure 12-8).

Table 12-3 explains the setting options available for the Signal Conditions window.

Figure 12-7. Insert New Signal Condition Wizard

Figure 12-8. Signal Conditions



Table 12-3. Signal Conditions

Item Description

Name Name of the Signal Condition that is displayed on the user interface.

SCADA Value Value of a Signal Condition known to the specific driver. Consultthe specific Driver manual for more information. It is written to theconfig file.


12-5. Configuring SCADA Options


SCADA Options are configured at the Drop Level in the Ovation Developer StudioSystem Tree (see Figure 12-9). These options include:

• Channels (see Section 12-5.1)

— Channel Points

— Devices

— Device Points

• Groups (see Section 12-5.2)

— Group Points

• Additional Mappings (see Section 12-5.3)

• Events (see Section 12-5.4)

— History Tags

— Fault Drop Tags

Figure 12-9. SCADA Options at the Drop Level in Studio System Tree



12-5.1. Channels

A Channel is a set of point mappings that share a common path to the data. Channelsare comprised of points and devices.

Drill down to the Channels icon by navigating through the following path in theStudio system tree:

Drop LevelConfiguration IconSCADA IconChannels Icon

To insert a new Channel:

1. Right-click on the Channels icon and select Insert New. If a Channel exists,select Open from the right-click menu.

2. An Insert New Channels Wizard will appear (see Figure 12-10). Enter aChannel Name and select an I/O Driver from the pull-down menu and click Ok.

3. A New Channels window will appear (see Figure 12-11). Complete the fieldsand click Ok.


Figure 12-10. New Channels Wizard



t

Table 12-4 explains the setting options available in the New Channel window.

Figure 12-11. New Channels Window

Table 12-4. New Channels Window


Name

Channel Name Name of channel that was defined in theWizard window.

Automatically entered. Unable to editthis field.

Driver

I/O Driver

I/O Address SyntaxHint

Driver to be used with the channel.

Driver specific syntax used for accessinginformation.

Choose from the pull-down menu. Lisis populated from data defined in theSCADA Driver section of the StudioSystem Tree.




Retry

Auto Group

Demand Retry Count

Demand Retry Period(Seconds)

When checked, a point group is madecontaining all of the points contained in thischannel and all child devices.

The number of times to retry upon error ademand read of input points in point groupsmaintained by this channel.

Time period to wait between retries ofdemand reads for groups maintained by thischannel.

Check box

Entry field

Entry field

Failure Retry

Failure Retry Count

Failure Retry Period(Seconds)

Recovery Retry Period(Seconds)

The number of times the SCADA server willretry communications before failing over tobackup channel.

Time to wait before retrying.

How often to retry establishingcommunication with the primary after youfailed over to backup.

Entry field

Entry field

Entry field

Table 12-4. New Channels Window (Cont’d)




Point

Demand Point

Enable Point

Enable I/O Address

Status Point

Status I/O Address

Optional Ovation point name. This pointwill be monitored, and when the valuetransitions from zero to a non-zero, ademand read will be performed of all inputpoints in the channel.

Optional name of an Ovation point. Thispoint can be used to enable and disable thechannel.

This field can be an Intellution I/O address,in which case the value of the Ovation pointdefined in the previous field is sent out tothat address. It is assumed that this addressrefers to a field which actually enables/disables this channel. Otherwise, thekeyword CALCULATE is used to signifythe server should implement its own form ofenabling/disabling the channel. Whendisabled, the server will remove from scanall of the iFix blocks associated with thischannel, and all of its associated devices. Itwill not attempt to read or write any of thevalues.

Optional name for an Ovation point,originated at the SCADA server, which willbe used to represent the communicationstatus of the channel.

This field is either an Intellution I/O addresswhich represents the status of the channel.When the CALCULATE keyword is used,the SCADA server will determine thechannel status by monitoring all of the datapoints associated with this device It will beassumed that if any of the data points on thedevice are available, the channel status isgood.

Enter an Ovation point


Entry field


Entry field

NoteNot all drivers offer Enable Point orStatus Point functionality. The SCADAServer can provide this functionality.

Table 12-4. New Channels Window (Cont’d)




Channel Points

Channel Points allow for controlling and monitoring the channel. These points areusually driver specific, and can be useful in obtaining statistical information aboutthe channel.

Use the following procedure to insert a new channel point:

1. Right-click on the Channel Points icon and select Insert New from the pop-upmenu. If Channel Points exist, select Open from the pop-up menu.

2. An Insert New Channel Points Wizard window will appear (see Figure 12-12).Complete the Value field with a valid Ovation point name and click Ok.

3. A configuration window will appear (see Figure 12-13). Complete the desiredfields and click Apply or Ok to save the configuration changes.


Figure 12-12. New Channel Point Wizard



Table 12-5 contains the setting options available in the Channel Point ConfigurationWindow.

Figure 12-13. Channel Point Configuration Window

Table 12-5. Channel Point Configuration


Name

Point Name

Type

Name of the point that was defined inthe wizard. This must be a previouslydefined Ovation point.

Type of point such as Analog Input,Analog Output, Digital Input, orDigital Output.


Pull-down menu

Mapping

Ovation Field Field the data will be mapped to. Ifnot specified, it will go to the defaultfield for that point type.

Pull-down menu



Driver

I/O Driver

I/O Address Syntax Hint

I/O Address

I/O Signal Condition

I/O Hardware Options

Demand I/O Address Hint

Demand I/O Address

Inherited from the channel.

Driver specific syntax used foraccessing driver information. Seespecific Driver manual for moreinformation.

Driver address to map to Ovationpoint.

Will appear if it was designated at theDriver level. If none was selected,default behavior will occur.

Will appear if it was designated at theDriver level. If none selected, defaultbehavior will occur.

Driver specific syntax used forforcing I/O on demand.

Driver address to force the value to beread if the driver allows it. Seespecific Driver manual for moreinformation.



Entry field

Pull-down menu

Pull-down menu


Entry field

Processing

Process By Exception

Scan Time (Milliseconds)

Allow Initial Write

When checked, you will receiveupdates if the value has changed.Driver may not allow this.

If not using the Process by Exception,this is a periodic update rate.

When checked, it forces the initialvalues to the devices upon startup foroutput points only.

Check box

Entry field

Check box

Table 12-5. Channel Point Configuration (Cont’d)




Devices

Devices are a collection of points that originate in a common physical device. Thepoints are where the process data is mapped.

Use the following procedure to insert a New Device:

1. Right-click on the Devices icon and select Insert New from the pop-up menu.If a Device exists, select Open from the pop-up menu.

2. An Insert New Devices Wizard window will appear (see Figure 12-14). Enter avalue and click Finish.

3. A New Devices window will appear (see Figure 12-15). Complete the desiredfields and click Apply or Ok.


Limits

EGU Low Limit

EGU High Limit

Low limits assigned to the SCADAdatabase block.

High limits assigned to the SCADAdatabase block.

Entry field

Entry field

Figure 12-14. Insert New Device Wizard

Table 12-5. Channel Point Configuration (Cont’d)




Table 12-6 contains the setting options available in the New Device window.

Figure 12-15. New Device Window

Table 12-6. New Device Window


Name

Device Name Name of the device was defined in the Wizardwindow.

Automatically entered. Unable toedit this field.

Driver

I/O Driver

I/O Address SyntaxHint


Driver specific syntax used for accessinginformation.





Retry

Auto Group

Demand Retry Count

Demand RetryPeriod (Seconds)

When checked, a point group is madecontaining all of the points contained in thisdevice.

The number of times to retry (upon error) ademand read of input points in point groupsmaintained by this device.

Time period to wait between retries ofdemand reads for groups maintained by thisdevice.

Check box

Entry field

Entry field

NoteWhen the value is set at -1, thechannel values will be used.

Failure Retry

Failure Retry Count

Failure Retry Period(Seconds)

Recovery RetryPeriod (Seconds)

The number of times the SCADA server willretry communications before failing over tobackup channel.

Time to wait before retrying.

How often to retry establishingcommunication with the Primary after thedevice failed over to Backup.

Entry field

Entry field

Entry field

Table 12-6. New Device Window (Cont’d)




Point

Demand Point

Enable Point

Enable I/O Address

Status Point

Status I/O Address

Optional Ovation point name. This point willbe monitored, and when the value transitionsfrom zero to non-zero, a demand read will beperformed of all input points in a device.

Optional name of an Ovation point. This pointcan be used to enable and disable the device.

This field can be an Intellution I/O address, inwhich case the value of the Ovation pointdefined in the previous field is sent out to thataddress. It is assumed that this address refersto a field which actually enables/disables thisdevice. Otherwise, the keywordCALCULATE is used to signify that theserver should implement its own form ofenabling/disabling the device. When disabled,the server will remove from scan all of the iFixblocks associated with this device. It will notattempt to read or write any of the values.

Optional name for an Ovation point,originated at the SCADA server, which will beused to represent the communication status ofthe device.

This field is either an Intellution I/O addresswhich represents the status of the device fromthe driver, or the keyword CALCULATE.When the CALCULATE keyword is used, theSCADA server will determine the devicestatus by monitoring all of the data pointsassociated with this device It will be assumedthat if any of the data points on the device areavailable, the device status is good.


Entry field

Entry field

Entry field

Entry field

NoteNot all drivers offer Enable Pointor Status Point functionality. TheSCADA server can provide thisfunctionality.

Table 12-6. New Device Window (Cont’d)




Device Points

Device Points are where the process data is mapped to Ovation Points.

Use the following procedure to insert a New Device Point:

1. Right-click on the Device Point icon and select Insert New from the pop-upmenu.

2. An Insert New Device Points Wizard window will appear (see Figure 12-16).Enter a value and click Finish.

3. The configuration window will appear for that device point (see Figure 12-17).This must be a valid Ovation point name. Complete the fields and click Applyor Ok to accept the changes.


Figure 12-16. Device Points Wizard



Table 12-7 provides an explanation of the options available in the Configure DevicePoints window.

Figure 12-17. Configure Device Points



Table 12-7. Configure Device Points


Name

Point Name

Type

Status

Name of the point that was defined inthe wizard. Must be an Ovation point.

Point type, such as Analog Input,Analog Output, Digital Input, andDigital Output. Choices are based onthe point type. Analog Input andDigital Input points must beoriginated by the drop that theSCADA Server is configured on.

Choose this point to be the Primary orBackup path to this mapping.


Pull-down menu

Primary or Backup

Partner

Location Path to the Backup or Primarypartner.


Mapping

Ovation Field Field the data will be mapped to. Ifnot specified, it will go to the defaultfield for that point type.

Pull-down menu



Driver

I/O Driver

I/O Address Syntax Hint

I/O Address

I/O Signal Condition

I/O Hardware Options

Demand I/O Address Hint

Demand I/O Address


Driver specific syntax used foraccessing driver information. Seespecific Driver manual for moreinformation.

Driver address to map to Ovationpoint.

Choices will appear if it wasdesignated at the Driver level. If nonewas selected, default behavior willoccur.

Choices will appear if it wasdesignated at the Driver level. If noneselected, default behavior will occur.

Driver specific syntax used forforcing I/O on demand.

Driver address to force the value to beread if the driver allows it. Seespecific Driver manual for moreinformation.



Pull-down menu

Pull-down menu

Pull-down menu

Entry field

Entry field

Processing

Process by Exception

Scan Time (Milliseconds)

Allow Initial Write

When checked, you will receiveupdates if the value has changed.Driver may not allow this.

If not using the Process by Exception,this is a periodic update rate.

When checked, it forces the initialvalues to the devices upon startup foroutput points only.

Check box

Entry field

Check box

Table 12-7. Configure Device Points (Cont’d)




12-5.2. Groups

Groups are sets of points. If any of the output points of the group are written, all ofthe input points of the group are to be immediately read (if the driver allows demandpolling).

Use the following procedure to Insert a New Group:

1. Right-click on the Groups icon and select Insert New from the pop-up menu. Ifa Group exists, select Open from the pop-up menu.

2. An Insert New Groups Wizard will appear (see Figure 12-18). Enter a value andclick Finish.

3. A New Groups window will appear (see Figure 12-19). Complete the desiredfields and click Apply or Ok to save the changes.


Limits

EGU Low Limit

EGU High Limit

Low limits assigned to the databaseblock.

High limits assigned to the databaseblock.

Entry field

Entry field

Figure 12-18. New Groups Wizard

Table 12-7. Configure Device Points (Cont’d)




Table 12-8 explains the setting options available in the New Groups window.

Figure 12-19. New Groups WIndow

Table 12-8. New Group Window


Name

Group Name Name of the group was defined inthe wizard window.

Automatically entered. Grayed-out.

Retry

Demand Retry Count

Demand Retry Period (Seconds)

The number of times to force ademand read of input pointsmaintained by this group.

Time period to wait between readsfor points maintained by thisgroup.

Entry field

Entry field

Point

Demand Point Ovation point used to trigger ademand poll of the pointsassociated with the group.

Entry field



Group Points

Group Points are points which are associated with a particular group. Group Pointsare Ovation points that must be defined as a Device Point.

Use the following procedure to insert a new group point:

1. Right-click on the Groups Points icon and select Insert New from the pop-upmenu.

2. An Insert New Group Points Wizard will appear (see Figure 12-20). Select apoint name from the select list. Click Finish.

Figure 12-20. New Group Points Wizard



3. A New Group Points window will appear (see Figure 12-21). All of the fields inthis window are grayed-out, and cannot be edited.


Table 12-9 explains the settings in the New Group Points window.

Figure 12-21. New Group Points Window

Table 12-9. New Group Point


Name

Point Name

Device Point Location

Ovation point defined in the Wizardwindow. This point must also be definedas a Device Point.

Identifies the path to the device point.



Mapping

Ovation Fields If not specified, it is the default field. Automatically entered. Unable to editthis field.



12-5.3. Additional Mappings

Additional Mappings allow the mapping of existing iFix database blocks to Ovationpoints.

Use the following procedure to insert a new additional mapping:

1. Right-click on the Additional Mappings icon and select Insert New from thepop-up menu.

2. An Insert New Additional Mappings Wizard will appear (see Figure 12-22).Enter a value and click Finish. The value must be a valid Ovation Point.

3. An Additional Mapping window (see Figure 12-23) will appear for the specifiedpoint. Enter the desired information and click Apply or Ok to accept thechanges.


Figure 12-22. Additional Mappings Wizard



Table 12-10 explains the options available in the Additional Mappings window.

Figure 12-23. Additional Mappings Window

Table 12-10. Additional Mappings


Name

Point Name

Type

Ovation point defined in the Wizardwindow.

Type of point such as Analog Input,Analog Output, Digital Input, orDigital Output. Input Points must beoriginated by the drop.

Automatically entered. Grayed-out.

Choose from the pull-down menu.

Mapping

Ovation Field

SCADA Tag

SCADA Field

If not specified, it is the default field.

Intellution database block.

Field of the database block you aremapping.

Pull-down menu

Entry field

Entry field



12-5.4. Events

Events allow for the configuration of event data. The priority, message types, andpoint-to-event mappings can all be defined for both Historian events and Fault Dropevents. There are three filters for each iFix event which determine whether the eventis reported to Ovation. All three filters must be satisfied for the action to occur. Thethree filters are: message type, priority, and Ovation point names (see History Tagsand Fault Drop Tags).

Use the following procedure to Open Events:

1. Right-click on the Events icon and select Open from the pop-up menu.

2. An Event window appears. This window contains two tabs: Historian (seeFigure 12-24) and Fault Drop (see Figure 12-25).

3. Scroll to select each tab by using the horizontal scroll bar in the Event window.

Processing

Allow Initial Write When checked, it forces the initialvalues to the devices upon startup foroutput types.

Check box

Table 12-10. Additional Mappings (Cont’d)




4. You can save configuration changes after each tab is configured, or you can saveall changes after all of the tabs in a window have been configured. Select Applyto save changes and leave the window open, or select Ok to save changes andclose the window.

Table 12-11 explains the setting options available in the Historian Tab.

Figure 12-24. Historian Tab



Table 12-11. Historian Tab


Messages Handled

Typical Alarm

Hardware I/O Alarm

Network Notification

System Alert Notification

User Defined Message

Ack Notification

Manual Delete Notification

Operator Action

Recipe Message

Event Message

Generic Text Message

Generic or Unknown fromV6xNodes

Auto Alarm Manager Message

SQL Message

iFix messages. When an event isreceived, it will be checked against thislist. Only if the event is found checkedin this list will a message be sent to theHistorian. The other two filters, tagnames and priority, will also bechecked before the action is performed.

Check box

Priority

Priority Defines the lowest priority of messagesto be sent to the Historian. A priority isspecified and any messages of thatpriority or higher will allow the actionto occur.

Pull-down menu



Table 12-12 explains the setting options available in the Fault Drop Tab.

Figure 12-25. Fault Drop Tab



Table 12-12. Fault Drop Tab


Messages Handled

Typical Alarm

Hardware I/O Alarm

Network Notification

System Alert Notification

User Defined Message

Ack Notification

Manual Delete Notification

Operator Action

Recipe Message

Event Message

Generic Text Message

Generic or Unknown fromV6xNodes

Auto Alarm Manager Message

SQL Message

iFix messages. When an event isreceived, it will be checked against thislist. Only if the event is found checked inthis list will a message be sent to the faultdrop. The other two filters, tag names andpriority, will also be checked before theaction is performed.

Check box

Priority

Priority Defines the lowest priority of messagesto cause a fault drop. A priority isspecified and any messages of thatpriority or higher will allow the action tooccur.

Pull-down menu



History Tags

History Tags are Ovation points for which event messages are to be checked. Theseare accessible in the system tree under the Event icon. The Ovation points that areconfigured as History Tag Points must also be defined as a Channel Point, DevicePoint or Additional Mapping Point.

Use the following procedure to insert a new History Tag:

1. Right-click on the History Tags icon and select Insert New from the pop-upmenu.

2. An Insert New History Tag Wizard will appear (see Figure 12-26). Select a pointfrom the select list and click Finish. The value must be a valid Ovation Point.

3. A Configuration window will appear (see Figure 12-27). Fields in this windoware automatically complete. You are unable to edit these fields.

To configure existing History Tags, use the following procedure:

1. Double- click to open the Event icon. History Tags and Fault Drop Tags appearbeneath the Event icon.

2. Left-click the History Tag icon and the History Tags will appear in the WorkPadwindow.

3. Double-click to open the History Tag. A configuration window will appear (seeFigure 12-27).



4. The fields in this window are automatically entered. The user is not able to editthese fields.

Figure 12-26. New History Tag WIzard

Figure 12-27. History Tag



Fault Drop Tags

Fault Drop Tags are Ovation points for which event messages are to be checked.These tags are accessible in the system tree under the Event icon. The Ovationpoints that are configured as drop fault tag points must be defined as a ChannelPoint, Device Point, or an Additional Mapping Point.

Use the following procedure to insert a new Fault Drop Tag:

1. Right-click on the Fault Drop Tags icon and select Insert New from the pop-upmenu.

2. An Insert New Fault Drop Tag Wizard will appear (see Figure 12-28). Select apoint from the select list and click Finish. The value must be a valid OvationPoint.

3. A Configuration window will appear (see Figure 12-29). Fields in this windoware automatically complete. You are unable to edit these fields.

Use the following procedure to configure an existing Fault Drop Tag:

1. Double click the Event icon. History Tags and Fault Drop Tags appear beneaththe Event icon.

2. Left-click the Fault Drop Tags icon and the Fault Drop Tags will appear in theWorkPad window.

3. Double-click to open the Fault Drop Tag. A configuration window will appear(see Figure 12-29)



4. The fields in this window are automatically entered. The user is not able to editthese fields.

Note

The configuration described in this section must bedownloaded in order for the changes to take effect.See Section 13 for information on downloadingchanges to a drop.

Figure 12-28. New Fault Drop Tag Wizard

Figure 12-29. Fault Drop Tag


Section 13. Downloading


The download function allows the user to download the process diagrams, audiofiles, bitmap files, and configuration changes onto target drops. This sectionexplains the download procedure that must be applied to all configuration changes.Upon completion of the downloading and rebooting process, all configurationchanges will take effect. The Download function can be performed at the System,Network, Unit, or Drop level.

For Controllers, the user can also download the Ovation software.


• Download Procedure (Section 13-2).

• Downloading to Multiple Drops (Section 13-3).


13-2. Download Procedure


Use the following procedure to download the changes to the drop of your choice:


2. Expand the system tree to the Drop level.

3. Right-click on the item of the drop where you wish to view the changes andselect Download from the pop-up menu. If the drop is redundant, the DropSelection window will appear (see Figure 13-1). Select the drop to downloadand continue with Step 4.

4. The Download Preview window appears (see Figure 13-2). The DownloadPreview window lists any files that may have been altered during configuration.This window also identifies any diagrams, audio files, bitmap files, andcontroller software that need to be downloaded. You can select which of thesefiles that you would like to include in the download process by placing a checkin the box next to the file.

5. If the information in the Download Preview window is acceptable, select theDownload Check Box if it is deselected, and select the Ok button. This willdownload the changes. When both Download and Reboot are selected, thedrop will download the changes and the machine will restart.

Note

Reboot the Drop in order for the configurationchanges to take effect. You can reboot the drop byselecting Reboot from the right-click pop-up menuor by checking Reboot in the Download Previewwindow as described in Step 5 above.

Figure 13-1. Drop Selection Window



6. Downloading is now complete.

Table 13-1 explains the options available in the Download Preview window.

Figure 13-2. Download Preview Window

Table 13-1. Download Preview Window

Item Description

Select All Selects all of the files previewed in this window.

Clear All Deselects all of the files previewed in this window.

Download When checked, this action downloads all of the previewed files afterpressing the Ok button.

Reboot When checked, this action shuts down the workstation and thenrestarts the drop after the OK button is selected.

Abort Aborts the download process and returns to the Ovation DeveloperStudio without executing any commands.

Ok Executes the settings and closes the window.

Skip to Next Drop This button advances to the next drop for file preview. (The currentdrop is not downloaded.)


13-3. Downloading to Multiple Drops


This procedure allows the user to download to multiple drops. Multiple drops canbe downloaded at the System, Network or Unit level in the Developer StudioSystem Tree.

A download at the System level will allow the user to select any of the drops underthe system to be downloaded. A download at the Network level will allow the userto select all of the drops under the network to be downloaded. A download at theUnit level allows the user to select all of the drops under the unit to be downloaded.

13-3.1. Procedure

You can download to multiple drops using the following procedure:

1. Access the Ovation Developer Studio

2. Expand the System Tree to the System <Name> Folder level.

3. Right-click on the System Name item (or appropriate level such as NetworkName or Unit Name)

4. Select Download from the right-click pop-up menu. A Drop Preview windowappears (see Figure 13-3).

Note

The Drop Preview window contains a list of dropsthat fall under the selected level in the hierarchy. Forexample, if you choose to download from the Systemlevel, all drops in that System will appear in the DropPreview window. If you choose to download from theUnit Level, all drops under that Unit will appear inthe Drop Preview window.

5. Select the Drops you would like to Download by placing a check in the box nextto the Drop number. You may select all drops by choosing Select All or you maydeselect all drops by choosing Clear All.

6. Select Ok to download these Drops. You may abort the download by choosingAbort in the Drop Preview window (see Figure 13-3).

7. Proceed with downloading by following Steps 4 and 5 in Section 13-2.



Note

Process Diagrams downloads can also bedone by right-clicking on the Diagramsfolder at any level in the Studio System Treeand selecting Download. This will downloadthe changed process diagrams to multipledrops.

Changed process diagrams must be loaded inorder to be viewed in the Process DiagramsSystem (see “Ovation Operator Station UserGuide” (WIN20)) for more information.

Figure 13-3. Drop Preview Window


Index

AAbort 13-3Acknowledged Return Alarm Color

Configuration 3-59Action Buttons 2-7Additional Mappings 12-33Alarm Audio Configuration 3-28Alarm Color 5-6Alarm Colors Configuration 3-42Alarm Colors Tabs

Acknowledged Return 3-42Acknowledged Return Colors 3-42Icon Tile Colors 3-42Remote Network Status Colors 3-42Unacknowledged Incremental Alarm 3-42Unacknowledged Return Colors 3-42

Alarm Configuration 3-14Alarm Display Tab 3-9Alarm Filtering 3-12

Normal Mode 3-12Priority Mode 3-12Unit 3-12

Alarm Group Tab 7-22Alarm Group Window 3-70Alarm Historical Storage 3-34Alarm Key 7-13Alarm Page Acknowledge 7-21Alarm Printer

Port 3-36Alarm Printer Configuration 3-36Alarm Printing

Alarm Printer Colors Tab 3-35Alarm Printing Tab 3-36Alarm Rate

First Pass 3-10Alarm System Colors 5-6Alarm Window 3-3, 3-10

Tabs 3-6Alarm Window Tabs

Alarm Display Tab 3-8Alarm Filtering Tabs 3-12Alarm Historical Storage Tab 3-33Alarm Printer Colors Tab 3-37Alarm Printing Tab 3-35Audio Tab 3-24Audio/Files Tab 3-26

Alarms 3-1Alarms Removed 3-10

Apply 1-6Audio 3-22

Adding to a drop 3-28Audio Files/Points Tab 3-26Audio Tab 3-24AutoTurnoff 3-23, 3-25Continuous 3-23Silence 3-23Time Delay 3-25

BBackup Printer 3-37Base Alarm Configuration 3-1Bitmap

Bitmap Files 3-71Bitmap Folder 3-74Iconic Alarming 3-74

Blank Line Percent 3-10Blinking

Alarm Blinking 7-2Alarm Solid 7-2

CCancel Button 1-6Cancel Request 3-23, 3-26Channel 12-14Channel Points 12-18Character

Character Position 10-6character set 10-14

Characteristic (0-9) 10-11Characteristic (A-Z) 10-11Close button 1-6Color

RGB Value 3-42Color Palette 3-42Common Printer Colors 3-39Configuration 2-6Configuration Folder 2-6Configuration Tool 2-6Configuring the Ovation Keyboard 7-1Continuous Audio

local mode 3-23Continuous Audio system 3-22Custom Key 7-13

1/03 Index-1 WIN21(Rev 0)Emerson Process Management Proprietary Class 2C

Index

DDemand I/O 12-28Developer Studio 2-1

components 2-3function bars 2-3system tree 2-1using 2-1

Developer Studio Components 2-3menu bar 2-3Overview window 2-3status bar 2-3WorkPad window 2-3Workspace window 2-3

Device Points 12-25Devices 12-21Digital Default High Scale 11-5Disable Fixed Size Position 8-4Display Area 1-6Display Colors 3-42Display Diagram

Window 7-21Display Diagrams 3-69Display Icon List 3-69Display Returns 3-69Double click 1-6Download Preview window 13-2Download Procedure 13-2Downloading

multiple drops 13-4Drag and drop 1-6Driver 12-28

I/O 12-28Drop Timeout

Background Color 3-47Foreground Color 3-48

EeDB 11-9

First Pass 3-34Events 12-35Execute Program 7-21

FFailure 12-23Fault Drop Tags 12-42First Pass 3-10, 3-36Function bars 2-3

GGood Quality Colors 11-7Grayed out 1-6Group Characteristics Position 3-69Group Folder 10-12Group Points 12-31Groups 12-29

HHardware Options 12-8High Scale 11-12Historian 4-1Historical Storage 3-34History Priority 3-15History Tags 12-40Horizontal Scroll Bar 10-7, 10-10

II/O 12-28Icon 1-6Icon Tile Color

Acknowledged 3-62Not in Alarm 3-62Unacknowledged 3-62

Iconic Folder 3-65iFix 12-2iFix Messages 12-37Increase Alarm Rate on First Pass 3-10

LLeft click ("Select") 1-6Limits 12-29List Priority 3-15Low Scale 11-12

MMan Machine Interface

MMI 5-1Mapping 12-27Maximize button 1-6Maximum Number of Alarms Removed 3-10Membrane Keyboard. See Ovation KeyboardMenu Bar 1-6Menu bar 2-3Minimize button 1-6MonitorRequest 3-23

WIN21(Rev 0) Index-2 1/03Emerson Process Management Proprietary Class 2C

Index

NNew Audio 3-28New Group 10-12Non-Good Quality Colors 11-8Normal eDB Destination 3-16Normal History Priority 3-14Normal List Priority 3-14Normal Print Priority 3-15Normal Unacknowledged Destination 3-16Normal Unacknowledged Priority 3-15Normal/Priority Mode Destinations 3-16Normal/Priority Mode Filtering Priorities 3-15Normal/Priority Mode Priorities 3-15Number of Previous Views 8-4

OOffline Timeout 3-37OK button 1-6OPC 6-1

CLSID 6-4Logical Name 6-4Node 6-4ProgID 6-4Server 6-3

Open 1-6Open Alarm List 7-21Operator Station 1-1Ovation Developer Studio 2-1Ovation Keyboard 7-1

adding to a drop 7-4Iconic Alarming 7-9Keys 7-12

Ovation NT Developer Studio 2-1Overview window 2-3

PPI Server 4-1Plant Area Grouping Criteria 3-71Point

Demand 12-24Device 12-25Enable 12-24Status 12-24

point characteristics 10-6Point Group Number 3-73Point Information 7-21Point Quality 5-6Point Quality States 9-1

Point Review 7-21, 10-3point review group 10-6Point Timeout

Foreground Color 3-47, 3-48Point Viewer 7-21Position

Col 3-71Row 3-71

Position Tabs 10-7, 10-10Print

Alarms on First Pass 3-36Destination 3-16Lines Per Page 3-37Priority 3-15

Print Destination 3-16Print Speed

letter quality 3-37Printer Color

Drop Timeout Color 3-39Point State Change Color 3-39Point Timeout Color 3-39Priority Mode Print Colors 3-39Priority X Alarm Color 3-39, 3-40, 3-41Priority X Incremental Alarm Color 3-39, 3-

40, 3-41Printer Offline Timeout 3-37Printer Port

alarm 3-36Printer Speed

high speed 3-37Priority Colors

Acknowledged Alarm 3-42Acknowledged Incremental Alarm 3-56Acknowledged Return 3-60Background 3-50Unacknowledged Alarm 3-42, 3-49, 3-50Unacknowledged Incremental Alarm 3-54Unacknowledged Return 3-53, 3-58

Priority X Background Color 3-52, 3-54, 3-56,3-58, 3-60

Priority X Foreground Color 3-50, 3-52, 3-54,3-56, 3-58, 3-60

Process Diagram ConfigurationTopics 8-8

Process Diagram System 8-1Process Diagrams

configuring 8-4Insert New 8-2

1/03 Index-3 WIN21(Rev 0)Emerson Process Management Proprietary Class 2C

Index

New Color Definitions 8-5Number of Local Windows 8-4Number of Previous Views 8-4

Process Point Quality 5-6

QQuality 9-2Quality Check Symbol 5-6Quality Color 5-6Quality Folder 9-5Quality Reasons 9-8

Character 9-9Name 9-9

RRaise/Lower Request Timeout 8-4Reboot 13-2Reference Documentation 1-5Refresh 1-6Returns 3-11Review Characteristics 10-5, 10-6Review Characteristics Folder 10-10Review Folder 10-3review groups 10-6Right click 1-6

SSCADA 12-7

Driver 12-4, 12-7Server 12-2Signal Conditions 12-10

Scale Type 11-12Scales

Digital Default High Scale 11-5Digital Default Low Scale 11-5Linear or Logarithmic 11-12

Send Alarm Message to eDB 3-34Show Alarm Colors 5-6Show Time on First Pass 3-10Signal Conditions 12-10Sound Recorder 3-32State Change

Background Color 3-47Foreground Color 3-48

Status Bar 1-6Status bar 2-3

TTabular Trend Order 11-5tag character 5-6Task Bar 1-7Time Delay 3-23Timestamps

on Returns and Incrementals 3-11Title Bar 1-7Toolbar 1-7Trend Configuration Folder 11-2Trend Defaults Definition 11-11Trend Display 11-1Trend Duration 11-12Trend Point or Trend Group 7-21Trend scale examples 11-13Trend Window Colors 11-5

Background Color 11-5Foreground Color 11-5Grid 11-5

VValue Colors 5-6Value field

color 5-6Vertical Scroll Bar 10-7, 10-10

WWorkPad window 2-3Workspace 1-7Workspace window 2-3

ZZoom Corner 8-4

WIN21(Rev 0) Index-4 1/03Emerson Process Management Proprietary Class 2C