DCS Mannual

OVOV-215WIN Ovation 3.1（OCR_400) (Aug.2008)

Course Objectives Upon successful completion of this course the student will be able to: •

Identify the major components of an Ovation system

•

Define the Ovation Drop Types

•

Define and Demonstrate Ovation Controller Functions and Capabilities

•

Describe and Outline the Ovation Fast Ethernet Network

•

Describe and Demonstrate Ovation Point, Control and Graphics Creation

•

Describe and Interrogate Ovation Point Types, I/O Modules and Control Algorithms

•

Demonstrate Basic Operator Functions

•

Demonstrate Data Retrieval

•

Describe and Manage Ovation Security

•

Implement Ovation System Backup

•

Demonstrate the ability to effectively use Ovation documentation

1

Emerson Process Management Power & Water Solutions Co., Ltd. All rights reserved.

Module 1: Ovation System Overview Module 2: Discuss the Hierarchy and Right Click Functions within the Ovation Developer Studio Module 3: Start with the Ovation Data Acquisition Module 4: Demonstrate Basic Operator Functions Module 5: Build & Maintain Ovation Control Module 6: Understand Typical Ovation Algorithms Module 7: Ovation Graphic Builder Module 8: Ovation Data Retrieval Module 9: Manage Ovation Security Module 10: Backup Ovation System 2


Module 1: Ovation System Overview • Examine the typical Ovation DCS • Understand the roles of different MMIs • Describe the function of Ovation controller drops • Describe the function of Ovation network • Address the Ovation I/O modules

3


Database Software Server DB/SS/EWS

Ethernet Switch

OPH Historian

OVATION NETWORK High Speed Ethernet 100(Mbps) Megabits / sec. Up to200,000 points Up to 254 Drops

Operator Workstation OWS

Ethernet Backup Switch

Redundant Controller Pair -Each with equal capability for control or backup -Scan inputs -Limit check points -Execute control -Send new control values to output devices -Multicast points onto the Ovation highway

4

Controller 1/51


Ovation Operator Workstation (OWS)

The Operator Workstation is the drop that allows us to communicate with plant processes via the Ovation network and to monitor normal and abnormal plant conditions. The Ovation Applications links are accessed from: • Ovation Applications folder on the workstation desktop • Start menu • Icons on the task bar (if configured)

5


OWS Monitoring

Interface to Control

• • • • • • • •

• Software driven Manual/Auto Stations • Control tuning

6

Alarm Management Process Graphics Point Information Point Review Historical Review Trends Viewer Error Log


Ovation Engineering Workstation (EWS) The Engineering Workstation is the drop that allows the engineers or a technician to make necessary software changes to the Ovation system. This drop contains the Ovation Developer Studio software. The Ovation Developer Studio allows users to: Configure Ovation drops Add or Manage drops Modify alarm configurations Create and modify Global Trends (Trend Groups) Build or change software Points Control Sheets Graphics Pass software changes to all drops in the system Load Download Reconcile

7


Ovation Developer Studio

Each engineering workstation is also a fully functioning operator workstation.

8


Database Software Server (DB/SS/EWS) The Database Software Server is the drop that contains the master Oracle database. Master Database - Contains the majority of Ovation System Data. It is used for creating, modifying and verifying control strategies and process points. It matches Ovation system points up with the System IDs (SIDs). All system graphics and AutoCAD drawing files are stored on the DB/SS. It also manages the network licenses for the maximum allowable system drops, Developer Studios, Graphics Builders, and Control Builders. The database server is typically DROP200 and there is only one database server per Ovation system. It can perform all the functions of an Engineering Workstation and an Operator Workstation. This drop is routinely backed up and the error log is checked on a regular basis. 9


Domain Controller With Ovation 2.4 and later releases the Ovation DCS introduces the Domain Controller. This machine manages security within the domain. A domain is a logical collection of computers and users on a network that share a common security database. The Domain Controller can either be a stand alone machine or it can be the Database/Software server. Functions of the Domain Controller: • Manage Ovation users • Manage password for users • Enforce policies and security for all drops on domain • Prevent unauthorized logins The domain controller can control security for a single or multiple separate Ovation systems. This is true whether or not the multiple systems are set up as a multi-network system. The Windows Server 2003 operating system runs the Domain controller whether it is stand alone or tied in with the Database/Software Server.

10


Ovation Process Historian (OPH) The OPH collects and stores historical data for • Process point values • Alarm history data • Operator events • Sequence of events (SOE) data • System messages Typically, the OPH is a drop on the Ovation network. Data such as point values, alarm information, and sequence of events are sent from workstations defined as OPH scanners. These scanner machines collect a predefined set of data and send it to the OPH for storage. Scanner drops have a binoculars icon in the lower right hand corner of the screen. The OPH allows operators to perform historical data retrieval for applications like historical trends or point reviews.

11


Functions of the OPH • Organize real-time process data • Perform the calculation of summary values • Support on-line storage and off line archival • Successfully respond to any retrieval requests.

Typically, the OPH is packaged with the Crystal Reports software package. This software provides custom viewing, sorting, and filtering of data that can be output to printers or files in a variety of formats such as Microsoft Word, Excel, HTML, “.csv,” and text. These reports can be executed on demand or at a scheduled time.

12


Ovation Controller – Major Functions • Provides alarming and command word processing for originated points • Originates and receives process points • Adds, deletes, and modifies points off-line • Reads I/O modules and converts data to process points • Reads process points and writes data to I/O modules • Executes control algorithms • Adds, deletes, and modifies control off-line • Runs Self-Test Diagnostics • Broadcasts point data to the Ovation DCS The controller both originates and receives process points. Points can either be hardware (wired to the module) or software points (values on a control sheet). Other Ovation drops obtain point values from the controller.

13


Ovation Controller Features The Controller in the plant is typically one or more cabinets containing input and output modules connected to the field devices by wires. These modules monitor each device for changes in the device's condition. When detecting a change (input), the Controller reads the change and tells the device (output) to perform an appropriate action as determined by the controller. This action has been programmed into the Controller by control sheets (signal diagrams) that are created in the Ovation Control Builder. The Control Builder sheets consist of algorithms arranged in a logical pattern that define in detail what action to take when certain events occur in a device. • Up to 32,000 points per controller (4000 direct-wired I/O points) • Scalable flash memory to store operating system, logic, and points • Pentium processor • Automatic failover to Backup Controller

14


Ovation OCR400 Controller The OCR 400 controller is the newly packaged Ovation controller for use with Ovation 3.0 systems and newer. The picture below shows the primary and backup controller with two I/O modules on each branch. The interfaces to the controller are located on the top of the controller as shown below.

15


Processor Module Interface Ports

16


Processor Module Indicator LEDS • P： power indicator, green • N1～N4 each Ethernet port has two indicator LEDs – first LED: green and flash, the module is linked with the network on that port. – second LED: yellow and flash, the module is receiving or transmitting data on that port.

17


I/O Interface Module Interface Ports

18


I/O Interface Module Indicator LEDS

19


Ovation I/O Modules The Ovation Distributed Control System provides modulating control, sequential control, and data acquisition for a variety of system applications. This system consists of a configurable mix of functional Input/Output (I/O) modules that communicate on the I/O bus to the Ovation Controller. I/O modules provide an interface between the Ovation Controller and the processes in the plant. Ovation I/O modules are “plug-in” components with built-in fault tolerance and diagnostics. They are able to operate on a wide range of signals and perform a multitude of functions. The standard modular components are “hot swappable” and typically consist of the following: Base Unit (containing the field terminations) Electronics module (Emod) -- two slots per Base Unit Personality module (Pmod) -- two slots per Base Unit The relay output modular components consist of the following: Electronics module Base Unit (containing the field terminations) 20


I/O Modules • • • • • • • • • •

8 Channel Analog Input 8 Channel HART Analog Input 8 Channel TC Input 8 Channel RTD Input 4 Channel Analog Output 16 Channel Digital Input 16 Channel Contact Input 16 Channel Digital Output 2 Channel Pulse Accumulator/Counter 16 Channel Sequence of Events

21


I/O Card Indicators • Standardized Status Indicating Scheme • Red indicates abnormal condition • Green indicates normal condition or status P Power (Green) C Communication (Green) E External Error (Red) I Internal Error (Red) Channel Status Indicators 1 Digitals - Green = ON 2 Analog - Red = Channel Error 22


Addressing The Ovation I/O Modules Addressing Format: D.N.B.S • D = Device number assigned to the PCI card 1. Local Ovation 2. Local Ovation 3. Local Q-Line 4. Can be one of the following: None Remote Ovation Remote Q-Line Local Q-Line 5-9 Third Party devices • N = Node (only used in Remote I/O; 1 through 8). • B = Branch (1 through 8). • S = Slot where module is located (1 through 8 for Ovation I/O)

23


w

w

P C E I 1 2 3 4 5 6 7 8 9 10 11 12 13 1 4 15 16

w

P C E I 1 2 3 4 5 6 7 8 9 10 11 12 13 1 4 15 16

w

w

P C E I 1 2 3 4 5 6 7 8 9 10 11 12 13 1 4 15 16

w

w

w

P C E I 1 2 3 4 5 6 7 8 9 10 11 12 13 1 4 15 16

w

w

P C E I 1 2 3 4 5 6 7 8 9 10 11 12 13 1 4 15 16

w

P C E I 1 2 3 4 5 6 7 8 9 10 11 12 13 1 4 15 16

w

P C E I 1 2 3 4 5 6 7 8 9 10 11 12 13 1 4 15 16

w

w

w

P C E I 1 2 3 4 5 6 7 8 9 10 11 12 13 1 4 15 16

w

P C E I 1 2 3 4 5 6 7 8 9 10 11 12 13 1 4 15 16

P C E I 1 2 3 4 5 6 7 8 9 10 11 12 13 1 4 15 16

w

P C E I 1 2 3 4 5 6 7 8 9 10 11 12 13 1 4 15 16

P C E I 1 2 3 4 5 6 7 8 9 10 11 12 13 1 4 15 16

w

P C E I 1 2 3 4 5 6 7 8 9 10 11 12 13 1 4 15 16

c w

w

w

w w

w

w

w

w

w

w

w

d

w w

w

w

w

w

w

w

w

W

PC I 13 1 2143 15 4 516 6 7 8 9 10 14315 P C11E12 I 13 1 2143 4 6 7 8 9 10 11E12I 13 P C E I 1 2 3 4 5 6 7 8 9 10 PC 11E12 I 13 1 2143 15 4 516 6 7 8 9 10 PC 11E12 I 13 1 2143 15 4 516 6 7 8 9 10 11E12 P 11 C E12I 13 12 4 516 6 7 8 9 10 PC 11E12 I 13 1 2143 15 4 516 6 7 8 9 10 15516 PC 1 214315 4 516 6 7 8 9 10 11 12 13 14 15 16

Power Supply

w

w

Cabinet 1 (see Controller)

I 13 1 214 3 415516 6 7 8 9 10 1 P C E I 1 2 3 4 5 6 7 8 9 10 PC 11E12 I 13 1 2143 15 4 516 6 7 8 9 10 PC 11E12I 13 1 214315 4 516 6 7 8 9 10 PC 11E12 I 13 1 2143 15 4 516 6 7 8 9 10 PC 11E12 I 13 1 2143 15 4 516 6 7 8 9 10 PC 11E12 I 13 1 2143 15 4 516 6 7 8 9 10 PC 11E12I 13 1 214315 4 516 6789P 10C11E12

w

P C E I 1 2 3 4 5 6 7 8 9 10 PC 11E12 I 13 1 2143 15 4 516 6 7 8 9 10 PC 11E12I 13 1 214315 4 516 6 7 8 9 10 P C11E12 I 13 1 2143 4 15516 6 7 8 9 10 PC 11E12I 13 1 214315 4 516 6 7 8 9 10 PC 11E12I 13 1 214315 4 516 6 7 8 9 10 P C11E12 I 13 1 214 3 415516 6 7 8 9 10 1511 1612 13 14 15 16

W

w

w

w

P C E I 1 2 3 4 5 6 7 8 9 10 11 12 13 1 4 15 16

w P C E I 1 2 3 4 5 6 7 8 9 10 11 12 13 1 4 15 16

w P C E I 1 2 3 4 5 6 7 8 9 10 11 12 13 1 4 15 16

w

P C E I 1 2 3 4 5 6 7 8 9 10 11 12 13 1 4 15 16

w

P C E I 1 2 3 4 5 6 7 8 9 10 11 12 13 1 4 15 16

Power Supply

P C11E12 I 13 1 2143 4 6 7 8 9 10 P 11 C E12I 13 12 4 516 6 7 8 9 10 PC 11E12I 13 1 214315 4 516 6 7 8 9 10 15516 PC 1 214315 4 516 6 7 8 9 10 P 11 C E12I 13 12 4 516 6 7 8 9 10 15516 P C E I 1 2 3 4 5 6 7 8 9 10 14315 P C11E12 I 13 1 2143 4 6 7 8 9 10 11E12I 13 P C11E12 I 13 1 214 3 415516 6 7 8 9 10 14315

w

w P C E I 1 2 3 4 5 6 7 8 9 10 11 12 13 1 4 15 16

w P C E I 1 2 3 4 5 6 7 8 9 10 11 12 13 1 4 15 16

w P C E I 1 2 3 4 5 6 7 8 9 10 11 12 13 1 4 15 16

w P C E I 1 2 3 4 5 6 7 8 9 10 11 12 13 1 4 15 16

w P C E I 1 2 3 4 5 6 7 8 9 10 11 12 13 1 4 15 16

w

w P C E I 1 2 3 4 5 6 7 8 9 10 11 12 13 1 4 15 16

w P C E I 1 2 3 4 5 6 7 8 9 10 11 12 13 1 4 15 16

b P C E I 1 2 3 4 5 6 7 8 9 10 11 12 13 1 4 15 16

w

w P C E I 1 2 3 4 5 6 7 8 9 10 11 12 13 1 4 15 16

P C E I 1 2 3 4 5 6 7 8 9 10 11 12 13 1 4 15 16

FFFF

P C E I 1 2 3 4 5 6 7 8 9 10 11 12 13 1 4 15 16

w

w P C E I 1 2 3 4 5 6 7 8 9 10 11 12 13 1 4 15 16

w

w

24 P C E I 1 2 3 4 5 6 7 8 9 10 11 12 13 1 4 15 16

A

P C E I 1 2 3 4 5 6 7 8 9 10 11 12 13 1 4 15 16

Local I/O Addressing Example Cabinet 2

Power Supply

W Power Supply

W

FFFF

I/O is monitored from Controller Device #1


A = Address 1.1.4 Device 1 Branch 1 Slot 4 B = Address 1.4.2 Device 1 Branch 4 Slot 2 C = Address 1.5.3 Device 1 Branch 5 Slot 3

D = Address

25

What is the I/O Address? Why?


Controller Cabinet Module Address Example(1) Controller Cabinet

Module A address = 1.1.2 Module B address = 1.2.4 Module C address = 1.3.6

26


Controller Cabinet Module Address Example(2) Extended I/O Cabinet

Module D address = 1.5.6 Module E address = 1.6.1 Module F address = 1.8.8

27


Controller Cabinet Module Address Example(3) Remote Node Cabinet Note: Assume the Node is in MAU position 1

Module G address = 4.1.1.3 Module H address = 4.1.3.5

28


Installing Ovation I/O modules

29


Guidelines for Replacing, Adding, or Combining Ovation Modules • Make sure that the replacement module is the exact replacement for the I/O module, both the Electronic module and the Personality module. • Modules are placed from top to bottom on the left side of a cabinet and from bottom to top on the right side of a cabinet. • If Relay Output modules are mixed with Standard I/O modules on the same branch, the Standard I/O module base must ALWAYS start in an odd-numbered module position on the branch . • Ensure proper Auxiliary voltage is available for all modules contained within the configuration. • Every I/O branch must be terminated using one of the following: — Left terminator — Right terminator — MAU base module (right or left side) 30


Ovation Network The Ovation network is the 100 Mbps data highway used to allow all the drops and devices to communicate. The Ovation highway uses Cisco switches and routers as shown below:

Switches • Used to connect drops, other switches, printers, PLCs, and routers • 24 ports each designated for certain devices • Many different configurations - Root Switch, Backup root, IP Traffic, Fan-out, etc • Connects devices with CAT5e Ethernet cables or Fiber • Ovation ports forced to 100 Mbps/Full Duplex • Diagnostics viewable on switch LEDs

31


Below is an example of a single tier network:

32


Below is an example of two tier network: The Ovation network is designed so that there are multiple paths for data. Each root and fan-out switch has a redundant partner so that if any one switch fails network communication can continue.

33


Module 2: Discuss the Hierarchy and Right Click Functions within the Ovation Developer Studio • Access the Ovation Developer Studio • Understand Ovation Record Types • Use the right click menu in the Developer Studio to Load controllers • Understand recommendations when loading controllers • Understand data movement in an Ovation system

34


Ovation Developer Studio • The Ovation System Database manages all items in the system – – – –

Input, output and calculated points Control modules Process graphics System configuration

• The Developer Studio was designed in a tree (or system hierarchy) structure including following folders – – – – – 35

Systems Folder Networks Folder Unit folder Drops folder Points Folder Emerson Process Management Power & Water Solutions Co., Ltd. All rights reserved.

Resizing Ovation Developer Studio Windows

window RESIZE locations Hint: Watch for the cursor to change to “bars”

36


Developer Folders Opens Ovation License Manager, License user details Enables you to establish multiple user security groups. View Ancillary Label attributes Configure System defaults. (alarms, trends, diagram colors, etc.) View, create, delete, modify symbols used in diagrams. View, create, delete, modify graphics and macros. Configure Network defaults View, create, delete, modify graphics and macros Configure Unit specific defaults View, create, modify graphics and macros

.

Configure Contoller devices, controller networking, etc

View existing point detail in Oracle, Add, delete, modify points.

Define I/O module types, physical location View existing Control logic. Add, delete, modify control sheets.

37


Ovation Record Types Record Type Abbr. Monitor status of: Drop record DU Ovation MMI’s & Controllers Node record RN Power supplies / remote nodes

Example Name break down DROP200, DROP1 D002P1 Drop2Device1 D001P2N4 Drop1Device2Node 4 Module rec. RM Configured I/O modules D001P1B4L3 Drop1PCI1Branch4Slot3 ♦Digital LD Digital points, two possible values (1 or 0), software and hard wired. ♦Analog LA Points with a range of values. (0-100%, 0-3000 PSIG, etc.) ♦Packed LP 16 digital bits that are treated as a single point or “word”. Long control LC Long Control or Algorithm points are created while building and modifying control sheets using Ovation Control Builder. See Control Builder Users Guide for more information on algorithm point names. ♦ Note: There are no “standard” Emerson Process Control Power & Water Solutions point names for these record types and therefore, no examples are given.

38


Make these common changes and use these guidelines for building and modifying ALL points in class.

39

CONTROLLER PAIR

CHARACTERISTICS

ALARM PRIORITY

1 / 51

A-------

8

2 / 52

B-------

7

3 / 53

C-------

6


Drop Load Recommendations • Read all bullets prior to loading controllers. • Use the Developer Studio to perform a consistency check on the controller pair prior to actually loading the controllers. Fix all items that are listed that may cause problems during/after the Load. • Use the Developer Studio to perform a Reconcile on the controller prior to actually loading the controllers. ONLY RECONCILE THE CHANGES YOU KNOW ARE VALID. IF YOU ARE NOT SURE ASK OTHERS. • Load the controller in control first. DO NOT ASSUME! Use your system status graphic to verify which controller is in control and back up. • Only load the backup controller after you verify proper operation of the points and controls. • Drop Load after making a relatively small number of changes – Don’t Stockpile. • Make sure you have the authority and permission to Drop Load when the unit is in operation. 40


Ovation Data Movement Diagram :

Backup (Backup) Flash Disk

Primary (Control)

Redundant Controller Pair

Flash Disk

③ ④

RAM

② ① ① ⑥

⑤⑤ ⑥ ④ ⑦

RAM

LOAD

DEVELOPER STUDIO RECONCILE

CONTROL BUILDER RECONCILE

DOWNLOAD

ON-LINE CHANGES

PROPAGATIO N MULTICAST POINT DATA

Database Software Server Ovation Database “disk” •Ovation points •Ovation control data

Ovation Config “disk” •Ovation system configuration •Graphics •Control sheets (AutoCAD) •much more

Ovation Live Data “disk” •Run time graphics and signal diagrams •Trends •Point Information •Point Review •many others

Operator Work Station(s) Ovation Live Data “disk” •Run time graphics and signal diagrams •Trends •Point Information •Point Review •many others


41

① ② ③ ⑥ ⑤ ④ ⑦

Ovation Developer Studio “Right Click” Menu Reference the Developer Studio User Guide for Ovation for more information on right click functions.

42


Module 3: Start with Ovation Data Acquisition • Configure additional Ovation I/O modules •Utilize the Ovation Developer Studio to create and modify analog points • Utilize the Ovation Developer Studio to create and modify digital points • Utilize the Ovation Developer Studio to create and modify packed points • Replace fault Ovation I/O modules 43


Configure additional Ovation I/O modules 1. Insert a New I/O Module using the Ovation Developer Studio 2. Create a new module point in the Ovation Developer Studio 3. Build a point using the Ovation Developer Studio

44


1. Inserting a New I/O Module using the Ovation Developer Studio (General / Nonspecific)

45


a)

b)

c)

d)

e) 46

In the Ovation Developer Studio, drill down through the System → Network → Unit → Drops → DropX/Drop5X to the I/O Devices folder. Expand the I/O Devices → Device? → Branch? → Slot? to see the Ovation Module folder (The “?” is dependent upon where the I/O module is or will be installed). The folder should be read “Empty”. Right click on the Ovation Module folder and select Insert New… Use the pull down arrow to select the correct module type from the list. (Use caution because many modules are similar.) Select Finish. Tabs: Config Tab: Module Record Point Name will populate when we build a module record; Module Tab: configure as needed. The Module tab is different for each module type. Analog and Digital tab fields are grayed out. You cannot modify the grayed out fields. Click OK to save the I/O module configuration. Emerson Process Management Power & Water Solutions Co., Ltd. All rights reserved.

Define and Configure Analog Input Module －4~20mA Analog Input

47


4~20mA Analog Input

48


Define and Configure Analog Input Module －TC Module

49


TC Module

50


Define and Configure Analog Input Module －RTD Module

51


RTD Module

52


Define and Configure Analog Output Module －4~20mA Analog Output

53


4~20mA Analog Output

54


Define and Configure Digital Input Module －Compact Contact Digital Input

55


56


Define and Configure Digital Output Module －DOC or DOX Module

57


DOC or DOX Module

58


Define and Configure Digital Input Module －SOE Module

59


2. Inserting a New Module Point (General / Nonspecific)

60


a) b) c)

d)

e)

61

In the Ovation Developer Studio, drill down through the System → Network → Unit → Drops → DropX/Drop5X to the Points folder. Expand the Points folder to see the Module Points folder. Right click on the Module Points folder and select Insert New… Give the point a valid Ovation point name and frequency. Click Finish. Reference the Ovation Developer Studio User Guide for point name rules. (A common naming convention for module points is D001P1B1L5 where D001 is the left controller-Drop1, P1 is PCI Device 1, B1 is branch 1, and L5 is location 5.) Modify the point as necessary. Fields commonly changed are the description, security, I/O module, and bit information on the display tab. Click OK to save the point.


3. 1 Insert new Analog points

62


Inserting New Tank level point (Analog Input) (1)

Point name：（：（LI1-XXX）（）（XXXyour drop number））：（）（

Point：： Description：Tank level XXX input signal Characteristics：L------Security：： at least select one security group Hardware：： IO type：Ovation IO module： (select IO module according to I/O address ) IO channel：1 IO task index：2 Alarm：： Priorities：set alarm priorities

63


Instrumentation：： Low sensor：0.0038； High sensor：0.0205； Low operating range：0； High operating range：100； Field transmitter low value：4； Field transmitter high value：20； Conversion type：Linear； Conversion coefficient 1-2：

These four fields are used to perform conversion coefficient Calc

Limits：： Low alarm limit 1：10；

Low alarm deadband：1

High alarm limit 1：90；

High alarm deadband：2

Display：： Engineering units：INCH Summary Diagram：50XX Minimum Scale：0； Maximum Scale：100； Digits Displayed：2； 64


(2)

Valve position output signal：（：（Analog Output））：（

Point name：：（LV1-XXX）（）（XXXyour drop number）））（ Description：valve-XXX position output signal； Characteristics：L------Security：： at least select one security group Hardware：： IO type：Ovation； IO module： IO channel：1 IO task index：2 Alarm：： Priorities：set alarm priorities

65


Instrumentation：： Bottom output scale：0 Top output scale：100 Limits：： Low alarm limit 1：10；




Display：： Engineering units：% Summary Diagram：50XX Minimum Scale：0； Maximum Scale：100； Digits Displayed：2；

66


(3) Build TC point：（：（TC1-XXX）（）（XXXyour drop number））：（）（ 1））Build Cold Junction Compensation Point for each TC module: (Ninth Channel point) CJC1-XXX（（ XXX- your drop number ） Hardware：： IO type：Ovation； IO module： IO channel：9 IO task index：(according to TC points task index on this module) Instrumentation：： Low sensor：-10； High sensor：100； Field Transmitter Type：blank Transmitter Temperature Units：：C Conversion type：X=Y

67


68


2)

Build TC temperature point：（：（TC1-XXX）（）（XXXyour drop number））：（）（

Point：： Description：TC xxx temperature point； Characteristics：T------Security：： at least select one security group Hardware：： IO type：Ovation； IO module： IO channel：1(1~8) IO task index：2 Alarm：： Priorities：set alarm priorities

69


Instrumentation：： Low sensor：-0.0205； High sensor：0.0205； Low operating range：0； High operating range：500； Field Transmitter Type：TE Transmitter Temperature Units：C Conversion type：5th order； Conversion coefficient 1-6：(REF-1150) CJ compensation name： CJC1-XXX CJC temperature units：C CJC conversion coefficient 1-2：(REF-1150) Limits：： Low alarm limit 1：100；




Display：： Engineering units：C Summary Diagram：50XX Minimum Scale：0；

Maximum Scale：500；

Digits Displayed：2； 70


(4)

Build RTD point：（：（RTD1-XXX）（）（XXX-your drop number））：（）（

Point：： Description：RTDXXX； Characteristics：T------Security：： at least select one security group Hardware：： IO type：Ovation； IO module： IO channel：1 IO task index：2 Instrumentation：： Low sensor：118 High sensor：172 Low operating range：120； High operating range：170； Field Transmitter Type：RN Transmitter Temperature Units：C Conversion type：5th order； Conversion coefficient 1-6：（Use Ovation Sensor Calibrate. to Cal.） 71


120 OHM - Nickel RTD Manufacturer: Minco Products (No. S4-60) Alpha = .0081 Westinghouse Part No. 774A759H01 red

red white white

Minco S4 - 60 Nickel 120 OHMS AT 0 Deg. C

white white

Temperature Range Information Deg. F 32.0 57.0 81.0 104.0 127.0 158.0

72

Deg. C 0.0 13.89 27.22 40.00 52.78 70.0

Ohms 120.0 130.01 139.95 149.79 159.99 170.17

RN = Nickel RDT RC = Copper RDT RP = Platinum RDT


Cal. Conversion Coefficient on-line using Sensor Calibrate 1.

Open Sensor Calibrate. Start → All Programs → Ovation → Ovation Utilities → Sensor Calibrate.

2.

SensorCalibration window point name: RTD1-XXX (press enter key) （Note：：1. Before enter point name, point must be loaded into Controller； 2. Define proper Conversion type ； 3.Sensor Calibrate will remove the point from scan, causing BAD quality, as well as put the point into calibrate mode. Take any precautions necessary to prevent problems!

3.

Enter the information as listed in the table below； TRAINING RTD DATA

73

EXPECTED VALUES

ACTUAL FIELD READING (OHMS Ω)

°F

°C

120.0

32.0

0.0

130.01

57.0

13.9

139.95

81.0

27.2

149.79

104.0

40.0

159.99

127.0

52.8

170.17

158.0 70.0 Emerson Process Management Power & Water Solutions Co., Ltd. All rights reserved.

Step2

step3

74


4. Click Calc Coeff button；

5.

Select Plot Point Tab，confirm curve；

6.

If ok, go back to Sensor Calibration Tab；click Store Coeff button； Then new Coeff. will be Stored into Controller;

7.

File – Exit (Note：when exit, point go back to on scan status automatically）

8.

Reconcile Conversion Coefficients into the Ovation Database Launch on Developer Studio System → Network → Unit → Drops → Controller# → right click → Reconcile → select point name rtd1 → OK 75


76


Cal. Conversion Coefficient off-line using Coefficient Calc

77


3.2 Insert new Digital points

选择完成

填写表格中数据

78


(1)

Pump Feedback Signal point：（：（DI1-XXX）（）（XXXyour drop number））：（）（

Point：： Description：Pump XXX Feedback Signal； Characteristics：A------Config：： Status checking type：Alarm on Zero Security：： at least select one security group Alarm：： Priorities：set alarm priorities Hardware：： IO type：Ovation； IO module： IO channel：1 IO task index：2 Display：： Set description：RUN Reset description：STOP Summary Diagram：50XX

79


(2) Pump open/close command point：（：（DO1-XXX）（）（XXXyour drop#））：（）（ Point：： Description：pump open command point Characteristics：A------Config：： Status checking type： No Status Checking； Security：： at least select one security group Hardware：： IO type：Ovation； IO module： IO channel：1 IO task index：2 Display：： Set description：OPEN Reset description：blank Summary Diagram：50XX

80


3.3 Control Application for Packed Point Output of a PACK16 algorithm is a packed point. Each bit represents the status of a digital input point. The PBPT output of control algorithms are packed points.

81


Common Uses of Packed Points • Mode words for control algorithms • Status feedback for motors, pumps, valves, etc • Permissive for starting, stopping, and controlling field devices

82


Packed Point in the Ovation Developer Studio

83


Packed Point in Point Information

84


Packed Point Exercise: (LP1-XXX）） 1. In the Ovation Developer Studio, drill down through the System → Network → Unit → Drops → DropX/Drop5X to the Points folder. 2. Expand the Points folder to see the Packed Points folder. Right Click to insert new packed point. 3. Type point name LP1-XXX in your controller. Frequency is S; 4. Define the point, if needed, as noted in the table below BIT #

BIT DESCRIPTION

0

MRE Output Signal

TRUE

FALSE

1

Xmtr Malfunction Alarm

TRUE

FALSE

2

Inhibit Control DevCheck MRE

TRUE

FALSE

3

Xmtr A Quality Alarm

TRUE

FALSE

4

Xmtr B Quality Alarm

TRUE

FALSE

5

Mode Select Made by TMOD

TRUE

FALSE

6

Xmtr Alarm Dev Signal

TRUE

FALSE

7

Average Mode

TRUE

FALSE

8

Lower Mode

TRUE

FALSE

9

Higher Mode

TRUE

FALSE

10

Xmtr A Mode

TRUE

FALSE

11

Xmtr B Mode

85

SET DESCRIPTION

RESET DESCRIPTION

TRUE FALSE Emerson Process Management Power & Water Solutions Co., Ltd. All rights reserved.

Replace Fault Ovation I/O modules 1. Find fault card hardware address on Point Information window 2. According to the application of channel points on fault I/O card, Make proper action to ensure the safety of system control 3. Enter the channel point name in the Point Information Window one by one, then make the following operation: a) Force the Quality to Good b) Scan off the point 4. Pull out the fault I/O card，plug in the new I/O card with the same type 5. Release all points one by one on Point Information Window a) Scan on the point b) Test mode off the point 6. Recover whole control system

86


Module 4: Demonstrate Basic Operator Functions •

Demonstrate and Explain the basic data acquisition operator functions

•

Monitor Point Information and Point Review details

•

Understand the Alarm functions of Ovation system

•

Implement a Digital and Analog Trend

•

Use Point Viewer to list points

•

Monitor the Ovation Error log for errors and warnings

87


OPERATOR TO CONTROLLER INTERFACE

Operator Station Ethernet Switch #1

Hi-Speed Ethernet Highway

Ethernet Switch #2

Redundant Controller Pair

PROCESS ( Power plants, Blast Furnaces, Waste Treatment plants,etc.)

88


OVATION APPLICATIONS FOLDER

89


Ovation Point Information Point Information is the Ovation application used to bring up information on any individual point. Information is presented in a tabular fashion. Ways to bring up information on an individual point: 1. Type the point name in the white text box and press ENTER 2. (1.) Click on the “Search” button (2.) Select the Network, Unit or Drop (3.) Choose your point (4.) Click Apply or Hit ENTER or Double Click 3. Right click on Graphic, Trend, Alarm, or Point Review 4. Drag and drop from Graphic, Trend, Alarm, or Point Review Points can be filtered so that only interested points in appear in the list. Filtering can be based on any one or combination of the following: Point Name * Point Alias * Description * Record Type Frequency 90


Point Information Search Window Use the left window to define the level you want to search. Searches can be done at the Drop, Unit, or Network level. Use the right window, via the “Filter” pull down menu on the Find Points window, to narrow the search using wild cards and/or pull down options. * = Point Information multicharacter wild card ? = Point Information single character wild card

91


The following table shows common record fields of interest to operator (1) Record Field

Abbreviation

Description

Point Info Tab

Point Name

PN

16 Character Name of Process Point

All

Point Description

ED

30 Character Description of the Point

All

Engineering Units

EU

Units of Measurement For the Point

All

Analog Value

AV

Current Value of an Analog Point

All

Record Type

RT

Type of Point (Analog, Digital, Packed, Module, etc.)

Point

Characteristics

KR

Plant Specific Information Regarding Point Location

Point

Originating Drop

DO

Drop in which the Point is Located

Point

First Status Word

1W

Information About the Point

Value/Status

Second Status Word

2W


Value/Status

Third Status Word

3W


Value/Status

Sensor Calibration

SN

Displays the analog value

Mode

Status Checking

AR

Alarm Status Checking for Digital Point (state point will alarm)

Alarm

Alarm Cutout

CX

Digital Point that when Set will Remove Alarm Check from Current Point Loaded in Point Info

Alarm

Destination

AY

First Character in Characteristic Field (Plant Area)

Alarm

Card Value

FV

Displays a point’s volts or amperage

92

Hardware


The following table shows common record fields of interest to operator (2) Record Field

Abbreviation

Description

Point Info Tab

Minimum Scale Value

BV

Lowest Value the Point Should Reach (Default Low on Trend)

Instrumentation

Max Scale Value

TV

Highest Value the Point Should Reach (Default High on Trend)

Instrumentation

Sensor Low Limit

LS

Lowest Volts/Amps Allowed on Card

Instrumentation

Sensor High Limit

HS

Highest Volts/Amps Allowed on Card

Instrumentation

Low Alarm Deadband

DJ

Deadband for Low Alarms

Limits

High Alarm Deadband

DB

Deadband for High Alarms

Limits

Low Alarm Limit #1

LL

First Low Alarm Limit

Limits

High Alarm Limit #1

HL

First High Alarm Limit

Limits

Low Inc Alarm Limit

ZM

Low Incremental Alarm Value

Limits

High Inc Alarm Limit

ZI

High Incremental Alarm Value

Limits

Set State Description

ST

Description of a Digital Point = 1

Display

Reset State Description

RS

Description of a Digital Point = 0

Display

For more information on each record field and record type, refer to the Ovation Record Types Manual (REF_1140). 93


Quality Quality of a process point is generated by the controller based on the operational readiness of a process point. The one letter abbreviation of the current quality of the point is shown following the English description. It is also shown in the Quality row on the Value/Status tab. The following table describes each of the five possible qualities. Quality

Description

1W 98

Good

On Scan, within Sensor Limits, within Engineering and Reasonability Limits, Power Ok or Test Mode on

00

Fair

Forced or Entered Value, Algorithm Propagation, or Test Mode on

01

Poor

Out of Engineering Limits, Over-range on AI module, some special algorithm, Algorithm Propagation, or Test Mode on

10

Bad

Off Scan, Out of Sensor Limits, out of Reasonability Limits, Power Bad on a Digital point, Bad Card, Algorithm Propagation, or Test Mode on

11

Timed Out

94

The point is not being updated, the drop that broadcasts the point is probably off the network

N/A Bit 15 = 1


Ovation Point Review Point Review allows the Ovation user to see the current status and checking configuration for points. The user can specify the parameters they want to search and then have the Point Review tool help them find points meeting the specified criteria. Once the search is complete, the user has the option of modifying attributes on any or all points. You can base a review on point characteristics that define plant areas, or other userdefined sorting criteria such as equipment or subsystems. In addition to characteristics and point groups, a review can also be based on status conditions, such as points in alarm, points for which scan has been disabled, or points in sensor alarms. Point Review is a very important operator tool. It is suggested at a shift turnover because is can quickly identify unexpected plant status. Results of a point review can be changed from Review → “Modify Point Attributes” window.

95


1

Point Review Window 2

96


Point Review Filters Window Common filter search items, as shown below, are Alarm Check Removed, Limit Check Removed, Scan Removed, Test Mode, and Entered Values.

3

4

97


Point Review Modify Attributes Window 5

8

9 7

98


Using Point Review (see screen captures from previous pages) 1. Open Point Review. 2. Select the “Filter” button on the toolbar. 3. Check the items you want to search for (see example on p. 15) 4. Click OK. 5. Click the “GO” button on the toolbar. After the search is complete, points meeting any of the search criteria will be on the screen. 6. NOTE: Proceed only if you are sure of your actions. 7. Select any points you wish to modify attributes. 8. Click the “MODIFY POINT ATTRIBUTES” button on the toolbar. 9. Select attributes you want to modify on ALL selected points. Click OK 10. The Point Review window will update status as point attributes are changed

99


Point Viewer The Point Viewer allows you to view all points in the system database. Points can be displayed by network, unit or drop. Operators can filter points for specific characteristics, such as record type, characteristics, and point frequency. By selecting specific filters, a review contains points with only the desired attributes. The following diagram shows a point view of all the points in DROP3.

The main purpose of this application is to print out lists of point within the database. 100


Ovation Alarm System The Ovation Alarm System is the application for detecting and displaying abnormal plant conditions such as: Points out of range Drop time outs Digital state changes Points getting better Points getting worse Module errors Alarms are sent to: Workstation alarm window Historian (if configured to) Alarm printer The alarms history buffer will retain last 15000 alarms. Older alarms are stored on the historian such as an OPH. 101


Alarm Status The alarm status of the point is displayed in the Alarm Type column. Analog Points: Analog points have up to 5 high and 5 low alarm limits HIGH1 → HIGH4 and a HUD (High User Defined) LOW1 → LOW4 and a LUD (Low User Defined) Incremental Alarms (HI WRS, HI BET, LOW WRS, LOW BET) Digital Points: Digital points can be configured to alarm 5 different ways Alarm on 1 Alarm on 0 Alarm on 1 → 0 transition Alarm on 0 → 1 transition State change (1 → 0 or 0 → 1) State change type alarms are listed in the History view only. Any point that has returned from its alarm state to normal will be listed as RETURN. This indicates that the point is no longer in alarm. 102


Other Common Types of Alarms: SENSOR - Data exceeded the sensor limits of device. HI WRS - Highest defined alarm (i.e. HIGH4) has been reached and the point’s value is getting further from normal. HI BET - Highest defined alarm (i.e. HIGH4) has been reached but the point’s value is getting closer from normal. TIMEOUT - Point has timed out, meaning it is expected but not received.

Alarm Priority All alarms have a priority assigned to it. There are eight total priorities available in the Ovation system. The priority value is displayed in the AP column. 1 - Highest, most crucial alarm 8 - Lowest, least crucial alarm

103


Priorities Are Color Coded (Default) 1. Red 2. Magenta 3. Yellow 4. White 5. Purple 6. Tan 7. Brown 8. Slate Blue Points will change to the alarm status “RETURN” if the point has returned from an alarm state. By default, all returns are green. User defined alarms can have a priority associated with them. However, once any other limit has been reached, the higher priority will supersede.

Alarming Dead Band If security allows, the operator has the ability to alter the alarm dead band. Dead bands are set up to limit nuisance alarms. By creating a dead band a point will stay in alarm until the value has returned to normal past the dead band value. The altering of dead bands and alarm limits is performed in the Point Information Ovation application.

104


Typical Alarm Configuration The number of alarm limits is determined when the point is built. Alarm limits can be added or removed; however, this function would be done at an Engineering Workstation. Operators, security allowing, can alter dead bands, change the alarm limit, and take points off alarm check. These functions are all performed in the Point Information Ovation application. The following table is a typical setup for an analog point. In this example, four HIGH and four LOW are defined along with an incremental alarm.

105


Acknowledging and Resetting Alarms An Alarm or a Return can be acknowledged, if the operator has permission. An Alarm Return can be reset if: The Return has been acknowledged AND The alarm point has remained normal AND The operator has permission to do so. Alarms can be acknowledged and reset individually, by groups of points, or by page. Drop alarms can be acknowledged and MUST be cleared through the System Status display.

106


the Base Alarm Window

107


Trend Display System The Trend application enables you to display data samples collected for live points on the Ovation Network in graphical or tabular trends. Six hundred data samples display for every collection interval. Trend data such as point names, scale limits, and collection intervals must be specified. Notes about Trends: •

Analog and Digital points can be trended

•

Permanent Trends are available through Trend Groups or locally saved trends Trend Groups - Predefined trends built in Developer Studio Saved Trends - Saved on local machine or on network drive by operator

•

Right Click will bring up the point menu

•

600 Samples per point displayed on each trend

•

8 points per Trend Group

•

Unlimited points per user defined trend

•

Multiple trend windows can be open simultaneously

•

Points can be dragged and dropped into trend from Graphics, Point Review, and Alarms

•

Right click on a trend brings up cursor

•

Historical trends will access data from historian for specified time period 108


Trend Chart View

109


Trend Tabular View & Trend Both View

110


TREND MENUS

111


TREND TOOLBAR

Help Print

Chart Zoom Chart Reset View Tabular Chart Stop

Both

Groups Properties Points New 112


Creating Trends

113


Configuring Trends

114


Ovation Error Log The OvationError.log file contains error, warning, and informational messages generated by the various Ovation services and applications. The Ovation Error Log Viewer reads the OvationError.log file and displays the information in a list-oriented display. This is a technician’s screen more than an operator’s. In general, it is of little interest to the operator.

115


Module 5: Building & Maintaining Ovation Control 1: Monitor Existing Control Schemes 2: Tune and Calibrate Existing Control 3: Modify Existing Control Sheets using Developer Studio 4: Use Miscellaneous Developer Studio Functions

116


Control Diagrams The two types of control flow are analog and digital.

Analog Control - Inputs top → outputs bottom Logic (digital) - Inputs left → outputs right

117


Accessing Real Time Functional Diagrams Using the Point Menu: 1.In a process or monitor graphic, place the mouse pointer over a points value. 2.Right click to access the point menu:

3. Select “Signal Diagram” from the point menu.

Using the Application Menu: 1.From the applications menu: 2.Left click on the Signal Diagram tab to access the CBViewer program:

118


3. The CBViewer will launch and open without a control sheet. Select the in the Sheet Browser section and expand, select and expand, select Drop and expand, select Task and expand, which will show all the configured control sheets. Select the control sheet you desire. CBViewer will open and display the sheet in real time.

119


Understanding colors for Algorithms • • • • • •

Analog algorithms Green - algorithm is tracking. Orange Red - algorithm is in manual mode. Cyan (blue green) - algorithm is in local mode. Purple - algorithm has reached its low limit. Magenta - algorithm has reached its high limit. Gold - algorithm is off scan.

Digital algorithms • Red - output is high • White - output is low • Cyan - output is calculated by the application, not feedback from the Controller.

120


Understanding colors for Signals Analog Signals • Hot Pink - Point is in alarm. • Yellow - Point is off scan. • Light Red (tomato) - Analog value has changed by a value greater than 1 since the last time the value changed. • Light Green (spring green) - Analog value has changes by a value less than 1 since the last time the value changed. • White - no change in the analog value. Digital Signals • Yellow - Point is off scan - False • Orange - Point is off scan - True • Orange Red - Point is in Alarm - False • Orange - Point is in Alarm - True • White - No change - False • Red - No change – True Packed Signals • Magenta - Point is in alarm • Blue - Point is stable • Orange - Point is off scan • 121 Green - Point has changed Emerson Process Management Power & Water Solutions Co., Ltd.

All rights reserved.

Tuning and Calibrating Existing Control •

ACCESS the properties summary window for algorithms

•

EXPLAIN the restrictions that may be imposed by System Security settings on the ability to tune a control diagram

•

EXPLAIN where the physical control process is executed and the impact on plant operations due to various component failures

•

MODIFY tuning parameters in an operating control sheet

•

DESCRIBE the purpose of each tuning parameter in the following algorithms: - SETPOINT - HIGHMON - PID - ONDELAY - MASTATION

•

EXPLAIN how tuning changes are saved by the system.

122


Exercise: Tune PID parameters 1. Access PID Logic：Signal Diagram – Sheet Browser– select PID control sheet- double click

123


2.

Select PID algorithm – Properties Summary ，tune parameters (INTG, PGAIN, DGAIN, DRAT)： then click Commit button。

1

2

3

124


3. Reconcile tuned parameters into the Ovation Database：Launch on Developer Studio-select desired controller – right click – select Reconcile – select tuned algorithms- ok 4. Launch on Developer Studio, open the control sheet，display Update Tuning parameters window automatically， Select the tuned parameters to Reconcile, to ensure the consistency between CB file and Oracle database ;

选中上传算法

125


Opening an Existing Control Sheet 1. 2. 3. 4. 5. 6. 7. 8.

Open the Ovation Developer Studio. Drill down into the Systems folder in the Hardware Root. Drill down into the Network folder. Drill down into the desired Unit folder. Drill down into the desired Controller Drop folder. Drill down into the Control Tasks folder. Drill down into the desired Control Task. Double click the desired sheet from the workpad (bottom) pane.

9. 10.

Control Builder will launch. Wait… The control sheet is loaded. 126


Ovation Control Builder Menus The File Tab:

127

The Edit Tab:


Ovation Control Builder Menus The View Tab:

The Draw Tab:

The Tools Tab:

128


Ovation Control Builder Toolbars Zoom window view Move selected items Add control algorithm Save file Open file

delete

Add control pin

Draw algorithm value Build control signal

I/O Algorithms

Standard Algorithms

129


Creating a New PID Analog Control Sheet 1. Open the Ovation Developer Studio. 2. Drill down into the Systems folder in the Hardware Root. 3. Drill down into the Network folder. 4. Drill down into the Unit folder. 5. Drill down into the desired Controller Drop folder. 6. Drill down into the Control Tasks folder. 7. Right Click on the desired Control Task. 8. Choose “Insert New”.

130


9. The “New Control Sheets window will appear:” 10. Supply an appropriate Sheet Name (maximum 38 characters), Sheet Number (maximum 3 characters). 11. Control Builder will launch. WAIT……a Control Builder canvas will initialize with a blank screen. 12. Build an analog control scheme that uses the some basic elements of analog control: PID, SETPOINT, MASTATION and MAMODE algorithms. • Add analog input, PID, SETPOINT, MASTATION and FIELD algorithms. • Connect the algorithms with signal lines. • Edit the algorithms to use the PA10X(where X is your assigned number) for an input and a M10X(where X is your assigned number) for an output.

131


13. Using Control Builder, select the Floppy Disk icon after making changes to a control sheet. This will: A. Saves the control sheet drawing (.svg) file B. Saves all control related database changes into Oracle C. Saves the control sheet drawing for MMI

Control Builder Directories & Files Database/Software Server Master Diagrams(.svg): Control Builder is configured for the Signal Diagram Folder to be at the System level: Drive :\Ovdata$\\on-line\ Control Sheet(.svg): Drive :\OvptSvr\\\\ControlFunctions On-Line Graphics Files (.svg) CBViewer Drive :\Ovation\CrtlBldr\On-Line 132


14. Using the Developer Studio, perform a Drop Load to the controller by rightclicking on the desired controller drop folder then selecting “Load”. For redundant controllers, load the drop which is currently in Control Mode first (use the System Status diagram to determine), then load the drop currently in Backup Mode. This step will load all of the pending Oracle database changes into the controller. 15. Using Developer Studio, Download the graphic files to Ovation Stations by rightclicking on the folder for the desired Unit then selecting “Download” and picking the Workstation-type drops only. Alternately, right-click on the folder for an individual Workstation then select “Download”. This will place copies of the updated .svg files in the appropriate path for access via the Control Signal Diagram windows (C:\Ovation\MMI\CrtlBldr\On-Line) 16. Test your circuit. Does if perform as you expect? Is it Direct or Indirect control? Tune the PID for an error dead band that ensures the process will stabilize.

133


Modifying Existing Control Schemes Using Developer Studio 1. Update Database and Control files to reflect online tuning changes made to controllers (Reconcile, Audit Sheet) 2. Open an existing control sheet in the Developer Studio 3. Use the pan and zoom functions to view specific areas of a sheet 4. Modify existing control sheets using the Control Builder -ADD or DELETE sheet inputs and outputs -ADD, MODIFY or DELETE algorithms -ADD or DELETE algorithm parameters, point and signal tags -MOVE individual algorithms -ADD or DELETE and MOVE pins -ADD, MODIFY, MOVE or DELETE notes on a sheet -MODIFY the Title Block data

5. Save and Implement changes made to control sheets 6. Update the real time functional diagrams displayed in the Process Diagram windows to properly reflect the changes made to control

134


Exercise: Page Connectors •

Objective: Build an analog control scheme that includes page connectors and a tie back simulation.

• Steps: 1. Open the PID analog control sheet in your controller. 2. Use an analog output connector instead of the FIELD algorithm, and dummy point names for the analog input connector and the output connector. 3. Save, Load and Download.

135


4. Create another new control sheet in your controller. 5. Create an analog control scheme that includes an analog input, LEADLAG, GAINBIAS and analog output algorithms. Use the dummy point name used in the output of the MASTATION in the previous sheet as the output of the analog input for this sheet, and the output of the analog output on the previous sheet as the output of the GAINBIAS on this sheet. This will create the tie back: 6. Save. 7. Reopen the previous control sheet and Save. 8. Load to the controller and Download to MMI. 9. Test the page connectors – do they work as expected?

136


Using Miscellaneous Developer Studio Functions • • • • •

137

EXPORT and IMPORT full and partial control sheets using the Library functions BUILD and USE a control macro RECOGNIZE the impact of algorithm and control sheet execution order MODIFY the execution order of algorithms within a control sheet and of multiple control sheets within a control task area DESCRIBE and DEMONSTRATE the control options


Export control logic to a library 1. Open a control sheet and use the cursor to select the portion of the drawing that you want to export to a library; 2. File Menu –

3.

Define the path

and enter a name for the file 4. Select the Save button

5. Left-click to select an insert point.

138


Import a library into a control sheet 1. Open a control sheet, File Menu :

2. Find the desired library file and press the Open button; Note: if there are point names that may be duplicated, a dialog box appears, select Yes;

139


3.

A Point Edit dialog box appears, make the necessary changes

to the points and select OK to commit the changes.

4. Use the cursor to position the control elements; 140


Create a new Control Macro 1. Open a Macro work sheet in Control Builder. From the main Control Builder window, pull down the File menu and select New. Pull right and choose Control Macro from the menu that displays.

141


2. Build a simple circuit that has two digital inputs, a FLIPFLOP, an ONDELAY, a NOT gate and a digital output algorithm.

Note：：1. The following algorithms are not recommended for use in macros: KEYBOARD， MASTAION, XMA2, 2XSELECT, MEDIANSEL,SETPOINT, Other Macros; 2. You must create a ControlMacros folder under your System folder to store all your macros. This step is only performed once, but you must complete it before you create any macros. Under the System folder, create a folder called ControlMacros. Location: c:\OvPtSvr\\ControlMacros It must be defined as one word, with no spaces, and a capital "M" -- ControlMacros. DO NOT create the ControlMacros directory under a Drop folder. It must be under the System folder. 3. Do not define points in Macros; 142


3. Define Input/Output Pin：

Solution one： (1) Click on the input/output connector

(2) At the Input Mnemonic field, enter a name for the input. ฀ At the Function Description field, enter a description for the input.

Empty! Do not define point name in macros. 143


Solution two：use the Control Builder Macro Interface Editor window

Make the desired change. When finish, select OK to Commit the changes;

144


4. Add Macro Parameter function

(1) Right-click on the desired algorithm (for example: flipflop algorithm) and select Add Macro Parameter . (2) Go to the Property Editor and define: ฀ Source -- original name of the parameter as defined for the algorithm. ฀ Interface Parameter Name -- new name given to the parameter as displayed when the macro is used. The interface parameter name should be four to six characters in length. ฀ Description -- new description for the parameter. Descriptions should be less than 31 characters in length.

145


5. Save the macro to the ControlMacros directory. When you save the macro, it is automatically audited. Any errors result in the macro not being saved.

C:\OvPtSver\\ControlMacro\TEST2.svg

146


6. create a symbol for the macro (1) Open Control Builder– File Menu – New – Algorithm Symbol – CONTROL MACROS – TEST2(macro name)

147


(2) Use Draw toolba r(rectangle) to create the symbol (3) Select Algorithm-function layer, define the symbol name on the symbol; Modify symbol color

(4) Add desired control pin;

148


7. Save the Symbol;

The new symbol is saved to a Symbols folder that the Control Builder automatically created under the System folder;

149


To add a macro to a control sheet: 1. Add Algorithm toolbar icon, Expand the Control Macros folder and select the symbol you created for your macro. Place the macro on the sheet at the desired location.

2. Build any additional control logic into your sheet. 3. Save the control function. 4. Loading sheets in a Controller and Downloading MMIs. 5. Access a signal diagram to test the function of macro.

150


To modify a macro: 1.

Open Control Build - File menu - OPEN:

151


2. Find the macro (.svg file) in the Control Macro directory, and open it in the Control Builder. 3. Edit the macro as desired. You can use the Property Editor to edit parameter values or the drawing canvas to edit graphic entities. 4. Save the macro. CAUTION! Any modification made to a macro may have adverse effects on the sheets containing the macro. Reload those sheets into the Controller and test your control before you add them to your Ovation system.

152


To display macros in signal diagrams: 1. Access a signal diagram and display a sheet that contains a macro.

Macro

Macro parameters

153


2. Right-click on the macro. Select Explode Macro from the pop-up menu.

3. Another window appears that displays all the internal components of the macro. In this way you can observe the macro's performance in the online environment. The signal diagram allows you to toggle back and forth between a sheet and the macro.

154


Modify the execution order of algorithms within a control sheet 4 Use the up or down arrow icons on the Object Browser to move;

1 Select algorithm folder

2 Select ordering type: manual

155

3 Select the algorithm which you want to change the order


Order control sheets within a control task area 1

Open Control Builder window;

2

Tool Menu – Order Sheets

3. Open icon, select the directory where the sheets Reside and press the OK button;

4. Select Drop and Control Task window appears; 5. Select a control task area and select the OK button; 7 Move the selected sheet(s);

6 Select the sheet(s);

8 When finish ordering sheets, select the OK button to save the new sheet order;

156


Exercise: Execution Order Objective: Build a control scheme and alter the sheets execution order to demonstrate its effect. 1. 2.

157

Build the following control scheme using the default execution order: Save, Load, Download and test the logic.


3. Reopen the control sheet and alter it’s execution order to match the order show below: 4. Save, Load, Download and test the logic. Does it perform as expected, and if not why not?

158


Backup CB files 1. Use the export operation to backup control function files : *.svg （1）From the main control builder window, pull down Tools Menu－> operations－>Export operation or launch on Developer Studio，select any controller, any control task area, right click to select control options – export operation：（2）Export operation window appears，select control function files which you want to export；（3）Select Next button, Configure operation window appears, Enter the destination which you want to save, append Extra information to the exported file and select the type of file: SVG （4）Select the Next button, Confirmation window appears, after Verifying the information, press Next to export；（5）Completed window appears，showing the status of the export； 2. Backup CB Macro files copy ControlMacros folder from the path: OvPtSvr\\ControlMacros

3. Backup CB symbol files copy symbols folder from the path: OvPtSvr\\symbols or OvPtSvr\\\symbols

159


160


161


Restore CB files 1. Restore CB macro files （1）copy CB macro files back to the existing Ovation system； The path is: OvPtSvr\\ControlMacros （2）compile these restored CB macro files Go to OvPtSvr\\ControlMacros folder，open anyone macro file, CB window appears, select Tools menu －>operations－>Compile select these restored CB macro files to compile； 2. Restore CB symbol files copy CB symbol files back to the existing Ovation system; The path is: OvPtSvr\\symbols or OvPtSvr\\\symbols

162


Restore CB files (Cont.) 3. Use import operation to restore Control function files: *.svg （1）From the main control builder window, pull down Tools Menu -> operations -> import operation： or launch on Developer Studio，select any controller, any control task area, right click to select control options – import operation：（2）The Import Operation window appears, at the Data Directory section, use Browse to select the folder which you backup; （3）From the directory structure displayed on the window, select the CB files which you want to import; （4）Select the Next button, the Configure operation window appears，Use the Browse button to enter the Destination of the import, The path is: OvPtSvr\\\\ControlFunctions （5）Enter a drop number, these sheets are imported to this drop ID; Enter a task number, these sheets are imported to this task ID; Enter a Base sheet number here if you want to change the actual sheet number; （6）If desired, enter the full path name of the point map file to use; （7）If desired, select the create undefined point to create all undefined user points that are found on the compiled sheet; （8）Select the Next button, confirmation window appears, after verifying, select Run button to import; （9）check the Completed window； 163


164


165


Module 6: Typical Ovation Algorithms DESCRIBE the functions of the following basic logic (digital) and modulating (analog) algorithms used in typical control strategies:

166

- AND

- KEYBOARD

- SETPOINT

- OR

- HIGHMON

- PID

- NOT

- LOWMON

- MASTATION

- FLIPFLOP

- FUNCTION

- MAMODE

- ONDELAY

- TRANSFER

- FIELD

- OFFDELAY

- 2XSELECT


FLIPFLOP

? S = Output remains in the same or previous state. ? --- TYPE=SET, ?=“1” TYPE=RESET, ?=“0”

167


HIGHMON

IF IN1 > HISP THEN OUT = TRUE ELSE IF IN1 < (HISP - HIDB) THEN OUT = FALSE

LOWMON

IF IN1 < LOSP THEN OUT = TRUE ELSE IF IN1 > (LOSP + LODB) THEN OUT = FALSE

HIGHLOWMON

IF IN1 > HISP OR IN1 < LOSP THEN OUT = TRUE ELSE IF IN1 < (HISP - HIDB) AND IN1 > (LOSP + LODB) THEN OUT = FALSE

168


ONDELAY

169


OFFDELAY

170


KEYBOARD

For the Δ and ฀∇, and ↓ and ↑ keys, the output maintains a TRUE signal for as long as the key is pressed. For all other keys, the output of this algorithm is a pulse (TRUE signal) of variable length. The pulse length is determined by the LENGTH (LENG) parameter, which specifies the pulse length in loops. If LENGTH is equal to 0 or 1, the pulse is 1 loop long. The LENGTH parameter may specify a pulse length up to 255 loops.

171


PID：： Some Tuning Parameters:

172


173


SETPOINT

Some Tuning Parameters:

174


MASTATION

Some Tuning Parameters:

175


MAMODE

Algorithm Definitions

176


2XSELECT：：

177


TRANSFER

Function: IF FLAG = TRUE THEN OUT = (IN2 x IN2 GAIN) + IN2 BIAS ELSE OUT = (IN1 x IN1 GAIN) + IN1 BIAS IF OUT ≥ TPSC THEN OUT = TPSC ELSE IF OUT ≤ BTSC THEN OUT = BTSC

178


Function:

The FUNCTION algorithm generates a piecewise-linear function that is determined by elements of a 12-element X-Y breakpoint array. Each Y-array element (dependent variable) has a respective X-array element (independent variable), thereby portraying the desired function. The number of breakpoints specifies the size of the array.

179


Module 7: Ovation Graphic Builder • Access the a graphic window and perform basic operator tasks • Demonstrate to build a new graphic • Copy and Paste between multiple GB sessions • Utilize various drawing techniques to create and modify perspective type graphics • Backup and Restore Graphic files

180


Ovation Process Diagrams The Graphics Display System is used to view graphic diagrams at the Operator Station. These graphics represent the process control system of the plant and you can perform some tuning functions on these graphics. Left clicking on an active area (poke field) can change the graphic, set control to an MA Station, switch from auto to manual, load a trend, silence an alarm, etc. Right clicking on a process point field will bring up the Point Menu which allows navigation to the following: • Point Information - Loads that point into the Point Information application • Trend - Builds a trend with the selected point • Signal Diagram - Will bring up the control diagram of the originating sheet • Summary Diagram - Process graphic containing point (if configured) • Point Search - Control Logic Navigator will search for sheets where the point is received.

181


Diagrams numbering convention: Process graphics are generally numbered in accordance with the following chart:

182


Access the Custom Graphics Solution 1: Load Diagram icon on the toolbar

183


Solution 2: Homepage icon on the toolbar

Solution 3: Favorite icon on the toolbar or Favorites Menu

184


Solution 4: Point Menu & select Summary Diagram

Note: Must define the Point’s Diagram number First by using Point Builder Tool Solution 5: Ovation Keyboard (customed key)

185


GRAPHICS TOOLBAR

Pull Down Menu Help Print the Active Document Recall Forward. Recall Backward Page Left Page Right Page Down Page Up Full Screen Go To Favorites Home Page

Load Diagram File

186


GRAPHICS MENUS

187


Example Process Diagram with Pop Up Window

188


OPERATOR POKE FIELDS PROCESS POKES CONTROL POKES

MORE PROCESS POKES

DIAGRAM POKES 189


System Status

190


Drop Details

191


Build a simple Graphic 1. Open Ovation Developer Studio 2. Select system - - Graphics - Diagrams

192


3. right-click – Insert New 4. Enter Diagram number 5. Configure Graphics Screen

193


6. Build your diagram - PROCESS_PT: access of Analog record fields (AV, ED, EU, etc.) 7. Save (& Comply) 8. Download *.diag files on your local MMI 9. Utilize Graphics Application to Display (the updated diagram in Graphic window) Note: if need to modify your diagram, go back to step6

194


Conditional Expressions • Simple Expressions • Compound Expressions • Case Expressions • Quality Expressions • Set Expressions

195


Simple Expression: Syntax: (operand1 rel_op operand2) [ logic_op (operand1 rel_op operand2) ... ] Examples: COLOR FG cyan (A100 AV < 50) yellow COLOR FG red ((A100 AV > 50) AND (A100 1W = HDWRFAIL) OR (D200 = ALARM)) blue

196


Operands: A100 AV = 10 SET2 = 20 A200 LL > 100.45 A100 AS = ALARM D200 DS = RESET A100 RT = LA D200 RT = LD Set5 > 50 Set20 = A100 GS A100 AV > $CONST1 197


Compound Expression: Syntax: { simple_expression1 conditional_value1 simple_expression2 conditional_value2 ... simple_expressionN conditional_valueN } Examples: COLOR FG magenta {(A100 AV > 50) blue (A100 1W = HDWRFAIL) red} BG white

198


Case Expression: Syntax: (CASE) pt_name rec_fld initial_val increment count cond_val

Example: COLOR FG magenta (CASE) A100 AV 1 2 3 green blue red

if A100 < 3 magenta if 3 <= A100 < 5 green if 5 <= A100 < 7 blue if 7 <= A100 < 9 red if A100 >= 9 magenta

199


Quality Expression: Syntax: (QUALITY) pt_name fair_quality_cond_value poor_quality_cond_value bad_quality_cond_value timedout_quality_cond_value Example: COLOR FG cyan (QUALITY) D200 green yellow red blue

200


Set Expression: Syntax: (SETx) N conditional_values Example: COLOR FG red (SET2) 4 green blue black white if SET2=1 or SET2>5 red if SET2=2 green if SET2=3 blue if SET2=4 black if SET2=5 white

201


Building & Implementing Control Interface Graphics 1. Design and Implement a soft Manual/Auto Station – interface to Modulating Control using the following poke fields and application programs: •Poke type 7 (application program poke) •Program 6 (CONTROL_POKE application) •Poke type 23 (control poke) •Program 30 (UPSET application) •Program 31 (DOWNSET application) •Program 32 (MANUAL application) •Program 33 (AUTO application) •Program 34 (RAISEOUT application) •Program 35 (LOWEROUT application)

202


2. Create a generic control macro using macro pointers 3. Import macros into main screen graphic 4. Design and Implement a soft Start/Stop Station-logic control interface using the following poke fields and application programs: •Poke type 7 (application program poke) •Program 6 (CONTROL_POKE application) •Poke type 23 (control poke) •Program 28 (DIGITON/START_PC application) •Program 29 (DIGITOFF/STOP_PC application) •Program 32 (MANUAL application) •Program 33 (AUTO application) 203


Exercises: Build logic control interface

204


Macros - naming macroN.diag, macroN.src, macroN.bmp, macroN.notes where: n = the macro number (1 through 65,535)

205


Macros - substitutions • $Dn pointers are used to tag substitutable process point names, where n = 1 through 99. • “$Tn” strings are used to tag substitutable text strings in the background section of a graphic, where n = 1 through 50. • “$Tn” strings are used to tag substitutable text strings in the foreground, trigger, and/or keyboard sections of a graphic, where n = 1 through 50. • $SETn variables are used to tag substitutable set numbers, where n = 1 through 256. • $CONSTn variables are used to tag substitutable integers/real numbers, where n = 1 through 256. • $STATUS variables are used to tag substitutable status words, where n = 1 through 256. 206


Poke Field Types Used to Run Application Programs:

207


CNTRL_POKE (6) POKE_FLD x y w h state poke_type num_of_progs prog_num diag_num num_of_args point1 point2 trig_num set_num setval where: x, y, w, h, state, = Standard POKE_FLD parameters. See POKE_FLD reference pages for more information. poke_type = Poke type (7 is required for application program). num_of_progs = Number of programs to be executed (usually 1, unless additional application programs are linked to this poke field). prog_num = Application program number. For this application program, 6 will be entered in the command line. diag_num = Diagram to display (0 is required if no other diagram is called). For this application program, 0 will be entered on the command line. 208


num_of_args = Number of arguments. For this application program, 5 will be entered on the command line. point1 = Algorithm point name and ID record field for programmable key functions 1 through 4, RAISE SETPOINT, LOWER SETPOINT, START, and STOP. point2 = Algorithm point name and ID record field for programmable key functions 5 through 8, AUTO MODE, MANUAL MODE, RAISE OUTPUT, and LOWER OUTPUT. trig_num = Trigger number to be executed when selected. Valid range = 1 through 254. set_num = Set variable number (used in the trigger). Valid range = 1 through 255. setval = Integer value to be assigned to the set variable in the trigger. Valid range = 0 through 32,767. If 2 is selected, the previous set will be reset to 1.

209


DIGITON/START_PC (28) POKE_FLD x y w h state poke_type num_of_progs prog_num diag_num num_of_args where: x, y, w, h, state = Standard POKE_FLD parameters. See POKE_FLD reference pages for more information. poke_type = Poke type (7 is required for this application program). num_of_progs = Number of programs to be executed (usually 1, unless additional application programs are linked to this poke field). prog_num = Application program number. For this application program, 28 will be entered in the command line. diag_num = Diagram number to be displayed (0 is required if no other diagram is called). For this application program, 0 will be entered on the command line. num_of_args = Number of arguments. For this application program, 0 will be entered on the command line. 210


DIGITOFF/STOP_PC (29) POKE_FLD x y w h state poke_type num_of_progs prog_num diag_num num_of_args where: x, y, w, h, state = Standard POKE_FLD parameters. See POKE_FLD reference pages for more information. poke_type = Poke type (7 is required for this application program). num_of_progs = Number of programs to be executed (usually 1, unless additional application programs are linked to this poke field). prog_num = Application program number. For this application program, 29 will be entered in the command line. diag_num = Diagram number to be displayed (0 is required if no other diagram is called). For this application program, 0 will be entered on the command line. num_of_args = Number of arguments. For this application program, 0 will be entered on the command line. 211


MANUAL (32) POKE_FLD x y w h state poke_type num_of_progs prog_num diag_num num_of_args where: x, y, w, h, state = Standard POKE_FLD parameters. See POKE_FLD reference pages for more information. poke_type = Poke type (7 is required for this application program). num_of_progs = Number of programs to be executed (usually 1, unless additional application programs are linked to this poke field). prog_num = Application program number. For this application program, 32 will be entered in the command line. diag_num = Diagram number to be displayed (0 is required if no other diagram is called). For this application program, 0 will be entered on the command line. num_of_args = Number of arguments. For this application program, 0 will be entered on the command line.

212


AUTO (33) POKE_FLD x y w h state poke_type num_of_progs prog_num diag_num num_of_args where: x, y, w, h, state = Standard POKE_FLD parameters. See POKE_FLD reference pages for more information. poke_type = Poke type (7 is required for this application program). num_of_progs = Number of programs to be executed (usually 1, unless additional application programs are linked to this poke field). prog_num = Application program number. For this application program, 33 will be entered in the command line. diag_num = Diagram number to be displayed (0 is required if no other diagram is called). For this application program, 0 will be entered on the command line. num_of_args = Number of arguments. For this application program, 0 will be entered on the command line. 213


UPSET (30) POKE_FLD x y w h state poke_type num_of_progs prog_num diag_num num_of_args where: x, y, w, h, state = Standard POKE_FLD parameters. See POKE_FLD reference pages for more information. poke_type = Poke type (7 is required for this application program). num_of_progs = Number of programs to be executed (usually 1, unless additional application programs are linked to this poke field). prog_num = Application program number. For this application program, 30 will be entered in the command line. diag_num = Diagram number to be displayed (0 is required if no other diagram is called). For this application program, 0 will be entered on the command line. num_of_args = Number of arguments. For this application program, 0 will be entered on the command line. 214


DOWNSET (31) POKE_FLD x y w h state poke_type num_of_progs prog_num diag_num num_of_args where: x, y, w, h, state = Standard POKE_FLD parameters. See POKE_FLD reference pages for more information. poke_type = Poke type (7 is required for this application program). num_of_progs = Number of programs to be executed (usually 1, unless additional application programs are linked to this poke field). prog_num = Application program number. For this application program, 31 will be entered in the command line. diag_num = Diagram number to be displayed (0 is required if no other diagram is called). For this application program, 0 will be entered on the command line. num_of_args = Number of arguments. For this application program, 0 will be entered on the command line. 215


RAISEOUT (34) POKE_FLD x y w h state poke_type num_of_progs prog_num diag_num num_of_args where: x, y, w, h, state = Standard POKE_FLD parameters. See POKE_FLD reference pages for more information. poke_type = Poke type (7 is required for this application program). num_of_progs = Number of programs to be executed (usually 1, unless additional application programs are linked to this poke field). prog_num = Application program number. For this application program, 34 will be entered in the command line. diag_num = Diagram number to be displayed (0 is required if no other diagram is called). For this application program, 0 will be entered on the command line. num_of_args = Number of arguments. For this application program, 0 will be entered on the command line. 216


LOWEROUT (35) POKE_FLD x y w h state poke_type num_of_progs prog_num diag_num num_of_args where: x, y, w, h, state = Standard POKE_FLD parameters. See POKE_FLD reference pages for more information. poke_type = Poke type (7 is required for this application program). num_of_progs = Number of programs to be executed (usually 1, unless additional application programs are linked to this poke field). prog_num = Application program number. For this application program, 35 will be entered in the command line. diag_num = Diagram number to be displayed (0 is required if no other diagram is called). For this application program, 0 will be entered on the command line. num_of_args = Number of arguments. For this application program, 0 will be entered on the command line. 217


Backup and Restore Graphic files Export Graphic files: Developer studio -- system -- Graphics – right-click & Export -- select Destination Folders – click Export button Import Graphic files: Developer studio -- system -- Graphics – right-click & Import -- select – click Import

218


Module 8: Ovation Data Retrieval Configure scan groups and Add points to scan groups Use Historical review to Retrieval: - Point - Alarm - Operator event - SOE messages Create a Historical trend

219


Configuring a point for collection 1. 2. 3. 4. 5. 6.

7. 8. 9.

Access Developer Studio and drill down into: system, configuration, historians, Ovation Process Historians folder. R/C on the historian workstation (i.e. DROP160) and select engineer. R/C scanner drop and select new group. For an existing group, double click. Modify scan Frequency, Dead band Algorithm and Dead band value as needed. Select the “<
220


Step7： Step7： Step8： Step8： Step1： Step1：

Step2： Step2：

Step4： Step4：

Step3： Step3：

Step5： Step5：

Step5： Step5：

Step6： Step6：

Step9： Step9：

221


To Access Historical Review •

Navigate to Start -> Ovation-> Ovation Applications -> Historical Review. The historical review main window is displayed:

• Navigate the six data type displays by using the folder tabs on the bottom of the historical review window, or the toolbar icons:

222


Historical Point Review

223


Historical Alarm Review

224


Operator Event Review

225


SOE Review

226


ASCII Messages Review

227


Historical Review and Historical Trends The Historical Review is a tool that provides the user with the ability to retrieve historical data. The Historical Review Application provides the following six different types of reviews: Point, Alarm, SOE, OpEvent, ASCII and Common. For each review, the Start, end time and specific filter criteria can be defined. Historical Reviews can be sent to a printer or saved as a text file. The Historical Trend enables you to display data samples collected for points on the Ovation Network in graphical or tabular trends. Six hundred data samples are displayed for the requested Trend interval. Specify trend data such as point names, scale limits, and trend intervals. Select a single point or multiple points to create a trend. The number of points on a Historical Trend is limited to 16 points based on a single retrieval limitation.

228


Module 9: Manage Ovation Security • Define user accounts • Create or edit a user accounts • Delete, disable or enable a user accounts • Reset a user’s password • Define Ovation Function for user

229


Create a new user account 1. Open the OSM from Developer Studio. 2. Click on Manage Users. 3. Right click and choose new or click on New from the tool bar. The new user dialog box will appear.

230


4. Provide General Information (not required) and a logon name. click on the password section and on the ellipse, the password editor window appears. 5. Provide a password. 6. Click on the Group Policy and on the ellipse, the Policy Selection Dialog Box will appear. Choose a policy and choose ok.

231


7. Reopen the user and under Roles click on an available network and on the ellipse and the Role Selection dialog box will appear. 8. Uncheck the None check box and choose the appropriate Ovation role (assign Ovation Function to user ) and choose OK and OK again.

232


Delete or disable a user accounts

233


Enable a user accounts

234


Reset a user’s password

235


Define Ovation Function for user 1. 2.

Open the OSM from Developer Studio. Click on Manage Ovation roles.

3.

To remove an Ovation role right click on the role and choose delete. To add a role right click and choose new (Roles can also be removed or added through the toolbar) Provide a name, description and network association.

4. 236


Edit Ovation Rules and Point Security Groups in Defined Roles: 1. Open the OSM from Developer Studio. 2.

Click on Manage Ovation roles.

3.

Double click on the Ovation Role you wish to modify, go to the Rules tab and Operator sub-tab and then scroll to Point Security Groups Tab.

4.

Highlight a rule, and check the checkbox to enable the rule, or uncheck the check box to disable the rule.

237


Module 10: Backup Ovation System 1. Prepare for Ovation system Backup • Save and Record all software that arrives with your system - all CDs, floppy disks, available files - system licenses, domain name - Important Users’ Security • Reconcile all controllers and control files • Close all Configuration Windows 2. Backup current machine software/hardware configuration for each machine start – All Programs – Accessories – system tools – system Info File menu – Save (.nfo file) 3. Copy the following files on Database Software Server c:\Windows\system32\Drivers\etc c:\OvptSvr 4. Full export of Ovation Database on Database Software Server a) Create a new folder: c:\BACKUP b) Open CMD window: start ---- Run ---- cmd c) cd \BACKUP d) Export the contents of the Oracle database with the following command: exp USERID=`sys/wdpf as sysdba` FILE= FULL=Y LOG= 238


5. Export Partial Database on Database Software Server a) Create a new folder: c:\BACKUP b) Open CMD window: start ---- Run ---- cmd c) cd \BACKUP d) Run the command: OvPtExport -u ptadmin/ptadmin@ptdb -o 6. Open Developer Studio to backup all control sheets Developer studio -- controller – right-click & Control Options --- select Export Control Sheets -- select Destination Folder -- click Export button 7. Backup Domain controller (see the next page)

239


Backup Domain Controller a. At your Windows Server 2003 domain controller, select Start -> All Programs ->Accessories -> System Tools -> Backup. b. The Wizard window appears. Select Advance Mode to change the settings used for backup. c. Select Backup Wizard (Advance) from the advance mode. d. Select Next. e. Select only backup the System State data. This will backup the following: • COM/COM+ Class Registration database • System Boot Files • Certificate Services Database • Registry • Cluster Database Information f. Enter a name for the backup file. Select Browse to choose the folder where you want to save the backup file. g. Select Next. h. Select Finish. The Wizard will close and the backup process will begin.

240


Database Tools and Descriptions TOOL

DESCRIPTION

DBID (Emerson Tool)

Microsoft Access graphical interface used to create points in a text (ASCII) file that can then be imported into the Master Database.

OvPtImport (Ovation Tool)

Imports data from a text file (for example, a DBID produced file) into Master Database. Can be used to restore database (using data from a previous OvPtExport file).

OvPtExport (Ovation Tool)

Exports data from the Master Database and produces a text file. This file does not contain SIDs or a point's network interface information.

imp (Oracle Tool)

Can be used to restore a database after a catastrophic failure (such as a disk crash). Operates on the binary file produced by exp.

exp (Oracle Tool)

Can be used to backup a system. Produces a binary file.

241


DCS Mannual

Recommend Documents