100% found this document useful (2 votes)
1K views36 pages

Ovation

This document provides an overview of the Ovation control system. It describes key features such as the intelligent device manager, plant alerts, programming tools, security, and connectivity. It also outlines the network architecture, controller and I/O module components, and historian functions. Specifically, it details the network types and speeds, controller features and specifications, types of I/O modules including analog and digital, and the historical data collection and storage capabilities.

Uploaded by

anandtvr
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
100% found this document useful (2 votes)
1K views36 pages

Ovation

This document provides an overview of the Ovation control system. It describes key features such as the intelligent device manager, plant alerts, programming tools, security, and connectivity. It also outlines the network architecture, controller and I/O module components, and historian functions. Specifically, it details the network types and speeds, controller features and specifications, types of I/O modules including analog and digital, and the historical data collection and storage capabilities.

Uploaded by

anandtvr
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 36

PRESENTATION ON

OVATION
FEATURES OF OVATION:
 AMS Intelligent Device Manager
 Ovation Plant Web Alerts

 Ovation Operator Workstation

 Intuitive Programming Tools

 Ovation Network

 Ovation Process Historian

 Ovation Security Features

 Connectivity
OVATION COMPONENTS:

 Network
 Controllers

 Input / Output Modules

 Relational Database

 Enterprise Integration

 Workstations

 Historians

 Report Servers
NETWORK FEATURES:
 Real time data transmission without loss , even during
plant upsets
 Fast 100Mbps Communication

 Interchangeable Fiber-optic and copper media with UTP,


Multi-mode Fiber, and single-mode fiber for network
architecture
TYPES OF NETWORKS

Network Speed Drops Points

W1 2 MB 254 16,383

W2 2 MB 254 32,000

W3 100 MB 254 2,00,000


CONTROLLER FEATURES:

 Provides Ultimate Flexibility through open Computing


Standards
 Executes Simple or complex modulating and sequential
control strategies
 Performs data acquisition functions and interfaces to
ovation network and I/O Subsystem
 Broadcast Value and status of each point in a drop at
appropriate frequency
I /O MODULE FEATURES:
 Provides low power consumption and heat dissipation.
 Feature standard DIN rail mounting for fast and easy
installation.
 I/O Module Consists of:
 Electronic module

 Personality module

 Terminal Block

• Electronic Modules:
Converts field signals into data and sends in to the controller
• Personality Module:

Characterizes the category of type of I/O and offers the


number of protection features.
• In an I/O Module both personality and Electronic module
should be same
 Module Numbering
 LeftBranch - Top to bottom
 Right Branch- Bottom to top
• Relay I/O Module Should be mixed with standard I/O
Modules
• Controller is connected to the remote nodes through Media
Attachment Unit(MAU) and Remote node Controller.
• MAU-Converts electrical signal in to Optical Signals.
• Remote Node Controller(RNC) interfaces controller and
Remote Modules.
• MAU and RNC are connected via Fiber Optic Cable.
• 1 MAU can connect 4 RNC.
Features UTP STP Coaxial Multi Single mode
Mode Fiber Fiber
Cost Low Low Moderate High High +
Installation Simple Simple Simple Differential Differential
Capacity 100Mbps 155Mbps 500Mbps 2Gbps 50Gbps

Distance 100meter 100meter 1Km 4km 30km

EMI N/R Poor Fair Excellent Excellent


CONTROLLER OCR-400:

 A Set of Controllers
Primary Controller
Partner Controller(Redundant)
 It is called as Compact Controller.
 Capability to originate 16,000 points.
 It uses Intel Pentium processor.
 Speed for the processor is 400MHz.
 Capable of simultaneously executing as many as five process control tasks at loop
speed ranging from 10 milliseconds to 30 seconds
 Each control task is comprised of I/O process point input scan, the control scheme
execution followed by output scan
1. One scan task -1S task
2.Second scan task -100mS task
3.Three, Four ,Five - User Selectable
 Control Scheme:
 Building control Sheets with an extensive set of algorithms.
 Controller can provide execution of 6000 Control Sheets.
• Controller Redundancy:
Ovation Network Interface
Functional Processor, Memory and Network Controller

Processor Power Supply

I/O Interface

Input power Feed

I/O Power Supply

Auxiliary power Supply

Remote I/O Communication Media


Controller Specification:
ITEM CAPABILITY
Bus Structure PCI Standard
Originated Points 16,000
Process Control Task Up to 5 with different execution
rate, two defined and three user
definable

Control Task Execution Rate Every 10ms to 30sec in 10ms


increments

Processor Intel
Memory 128MB Flash &128MB RAM
NIC Ports 4*10/100 MB Ethernet
Power 24V DC 40W
CONTROLLER I/O CAPABILITIES:
ITEM CAPABILITY
Local Ovation I/O 2 Set of up to 8 independent
branches of 8 modules per
branch for a total of 128
modules
Direct wired local I/O Analog =1024 or
Maximums Digital or SOE=2048
Remote Ovation I/O Up to 8 nodes of 64 modules

Maximum number of remote 8 nodes per ovation controller


nodes
Maximum number of I/O 64(8 branches with 8 modules
Modules per remote node for each branch)
Maximum number of I/O 512(8 nodes,8 branches for
Modules per controller each node,8 modules for each
branch)
Maximum number of I/O 1024
Modules per controller
TYPES OF I/O MODULES:
 8 Channels Analog input
 8 channel HART Analog input

 8 channel Thermocouple input

 8 channel RTD input

 4 channel Analog output

 16 channel Digital input

 16 channel control input

 16 channel Digital output

 2 channel Pulse Accumulator/Counter

 16 channel Sequence of Events


I/O MODULES ADDRESSING
 D.N.B.S
 D-Device number
 1-Local Ovation
 2-Local Ovation

 3-Local Q-Line

 4-Can be

 Remote Ovation
 Remote Q-Line
 Local Q-Line
• 5-9 – Third Party Devices
 N-Node number(used for remote 1-8)
 B-Branch number
 S-Slot number
ANALOG I/O MODULES:
 Individually Isolated
 Low Power Requirements

 Analog I/O Modules include:


 13-bit AnalogInput
 14-bit Analog Input
 RTD Input
 Analog Output
• Locally powered and Field powered transmitters can
be connected in a same module
13-bit Analog Input:
 Individually isolated inputs
 8 channels per module

 Individual A/D Converter Per channel

 13 bit resolution , including sign

 10 updates per second under normal conditions

14-bit Analog Input:

 8 channels per module


 Consists of 2 groups of personality and electronic modules

providing current signal of 4-20 mA and voltage signal


of +/- 1V
 20 updates per second under normal conditions
DIGITAL I/O MODULES:
 16 channels per module
 Single ended or differential inputs

 Handling AC or DC inputs ranging from 24V to 125V

Sequence of Events:
 16 channels per module

 Supports digital, single ended or differential inputs

 Ranges include
24 VAC/VDC Single ended/Differential ended
48 VAC/VDC Single ended/Differential ended
125 VAC/VDC Single ended/Differential ended
 1/8 m sec event time tag resolution with in a controller
OCR400 PROCESSOR AND I/O
INTERFACE MODULES

NETWORK INTERFACE PORTS:


N1- Other Additional Interfaces(eg : Allen Bradlely)
N2- Single Attached Network Interfaces
N3- Dual Attached Network Interfaces
N4- Dedicated Control Synchronization
I/O INTERFACE MODULES:
R3- Supports 4 nodes of remote or 4 nodes of remote Q-Line
R4- Supports 4 nodes of remote or 4 nodes of remote Q-Line
Q5- Supports 4 create(1 node) local Q-line
SPECIAL MODULES:
 Link Controller Modules
Programming Port
 Pulse Accumulator
 Counting of pulses
 Valve Positioner
 Linear Variable Differential Transformer
 Speed Detector
HISTORIAN ARCHITECTURE
 Modular Design:
 Historian functions separated in to independent software subsystem.
 Each subsystem performs unique function like scanning , collecting,
storing , retrieving or displaying historical data.
• Client /server Architecture:
 Server portion runs on historian. Server collects the
data from ovation network, send the data to archive
storage and responds to retrieval requests.
 Client application program runs on operator or
engineer work station. It provides the functions to
display ,print or save the data collected by server.
HISTORICAL SCANNING AND COLLECTING:
 Scans or collects six type of historical data
 Real time point values and statuses

 Laboratory data

 High speed data

 Alarm messages

 Operator action messages

 Sequence of events messages

 Report files
POINT HISTORY:
 Main History:
 Continually collects process point data
 Scan up to 20,000 data points

 Multiple scan frequency defined by the user on 1sec increments

 Collection based on dead band Selection and change in point status

 Long term storage Memory:


• Collects and store process point data and retrieves data based on user request
• Scans 600 user definable points and stores the value in online storage value

• Collection based on dead band Selection and change in point status

•Dedicated storage allows information to remain online for long time


EVENT HISTORY:
 Events such as plant trips or equipment startup can be
saved.
 Once event is activated 500 user defined points are
collected at 100 ms rate and scheduled for archive.
 Scans and collects 1hr worth of data.

 OWS or EWS can generate trends or reviews of the


values collected in the event history.
POINT GROUP HISTORY:
 Itis similar to the event history capable to define up to
5 historical groups of 20 points each.
 Scan and collect information on points with in the
predefined sets at a 100ms rate for an hour.
 Collection of group data associated with common
control functions
Event History Point group
Scan Rate 100ms 100ms
Points Scanned 500 points Up to 5 group of 20
each
Collection rate 100ms 100ms
LABORATORY DATA
 Unique data collection method for handling point data ,
i.e. not acquired in real time.
 Up to 1000 individual points collected via manual entry
or by communication with external device
 Stored in to historical archive for use in trends , reports
and other retrieval functions
MESSAGE HISTORY

 Alarm History
 Receives and stores alarm sent by alarm logging drop
 Allows an operator or engineer to display , print or save to a file the
list of alarms collected
 Capability to filter the alarm list based on factors such as
 Point name
 Time period or

 Originating period.
OPERATOR EVENT HISTORY
 Records operator actions received from OWS or
ovation controller
 Data Retrieval up on client application request

 Filtering is done through time period originating drop


or event type
File History
 Saves and archive operator shift diary output and
report generator output as data files in the historian.
 File history client interface used to retrieve these data
from historian by OWS or EWS
SEQUENCE OF EVENT HISTORY

 Collects SOE data from controller ,sorts in to a list


and searches the “first-out” events.
 Interface allows the operator to view the SOE report
and filter it based on tag name , controller or “first-
out” point
 Appropriate SOE I/O modules are equipped to
perform function.
HISTORICAL DATA STORAGE AND RETRIEVAL
 Historical data scanned and collected is stored for future
retrievals
 Historian utilizes 3 storage areas
 Primary storage
 Secondary Storage

 Long term Storage

• Primary Storage
• Stores most recently collected data
• Includes information from main event point long term
histories.
• Information from primary storage transferred to secondary
storage at user selectable time.
• It allows Primary storage to clear and available for
collection of the next time period data
SECONDARY STORAGE
 Maintains a period of historical files on hard disk.
 Automatic copy of all data placed in secondary storage
to long-term storage provides redundancy
 Storage limits are determined by capacity of hard
drive(s) and size of files.
LONG TERM STORAGE
 Optical disk storage is available to store up to 5.2
gigabytes
 Disk size varies from 80GB to 400GB

Storage Summary

Type Minimum Size


Primary Hard Drive 2GB
Secondary Hard Drive 4GB+
Long term Optical Disk Drive 5.2GB/disk
Drive Jukeboxes 80-330GB
ARCHIVE MANAGER
 3 functions
 Moves Historical files
 Manages retrieval functions

 Manages redundancy and recovery functions

 Moving Historical files


Responsible for moving historical files from one
storage place to another
Files are automatically moved from primary to

secondary and from secondary to long term storage


Deletes oldest secondary files when permanently

placed in long term storage


MANAGING DATA RETRIEVALS
 Automatically locates stored historical data for
retrievals
 It can find information stored in the hard drive when
user enters the requested time.
 Automatic retrieval of information within an optical
jukebox is a unique function
Redundancy and Recovery
 Consist of two separate identical sets of computer
hardware
 Concurrent redundancy scheme in primary and
partner historians
RETRIEVAL HISTORICAL DATA
 Historical Trends
 Utilize information collected in the data histories
 Up to 8 user definable points can be trended.
 Time period can be determined by the user
 Time periods can be defined in 3 ways
 Start and End times
 End time with specified intervals

 Start time with specified intervals


Point Review
•Tabular method of displaying historical information

• Point group Review

•Allows operator to display , print or save to a file the


historical data collected from the point group history.
ALARM REVIEW
• Allows operator to display , print or save to a file the
historical data collected from the alarm history.
Operator Event History
 List of events filters the list of operator events by time period
originating drops or events
SOE Review
 Allows the operator to view SOE report generated
by SOE history.
SQL Queries
 Historical data may be recalled in response to standard SQL
data queries

You might also like