Alarms and Events Processing and Logging

Download Report

Transcript Alarms and Events Processing and Logging

Alarms and Events Processing and Logging
Project Mentors
Suneel Kumar
Venugopal Vanga
Components of Alarm and Event
Detection System






Value Generation (Simulation of field values)
Alarm and Event Monitoring
Alarm and Event Limit Check (Control)
Alarm and Event Reporting
GUI or Interface
Database and Data Logging
Field Values Simulation

Values are generated by a random generator
program (a simulator for the RTU). It
generates random values according to the
following format.

V_055_IIIT_001_24/02/2004_11:50
V,I
Can be V/I etc
V → Voltage
I → Current
055
Voltage level (55 KV here)
IIIT
Substation name
001
Unique identifier
24/02/2004
Date
11:50
Time
Categorization of alarms/events:
Depending on the value we can prioritize the alarm.
 Alarm levels of severity or Priority
Level 0 Alarms → Audible + Onscreen Display in Red
Level 1 Alarms → Onscreen Display in Blue
Level 2 Alarms → Onscreen Display in Green

Red
Very Very High Alarm
Very Very Low Alarm
Blue
Very High Alarm
Very Low Alarm
Green
High Alarm
Low Alarm
Display of alarms
Storage structure of Alarms in
database









Alarm Date and Time
Acknowledgement Date and Time
Message
Value
Alarm Type
Alarm Id
Device Name or ID
Alarm status (Acknowledge / Unacknowledged)
Name of the acceptor
Storage structure of Alarms in
database









Alarm Date and Time
Acknowledgement Date and Time
Message
Value
Alarm Type
Alarm Id
Device Name or ID
Alarm status (Acknowledge / Unacknowledged)
Name of the acceptor
Storage structure of Events in
database







Event Date
Event Time
Message
Value
Event Type
Device Name or ID
Event Id
Format of the file storing limits

The file will have several lines of data. Each line
would be of the form
Scada
Point
Name
Voltage/ Current
etc.
Alarm/Event
Limit
Priority of
substation
Priority for the
alarm
Alarm/Event Monitoring


The monitor program checks for
alarms/events after every 2 seconds.
It transfers the value to the Limit Check
module.
Alarm/Event Limit Checks



Checks for the limits associated with
alarms/events.
Depending on weather and other parameters
limit checks are performed.
If it is an alarm/event message is given to the
GUI to display it
Alarm/Event Reporting




Automatically report alarms/events in the
interface.
Automatically updates the interface.
Maintaining the log report or record of the
Events and Alarms of past days or weeks.
The name of the operator who accepted the
alarm along with date and time of clearance.
Alarm and Event Control System


Functionalities or conditions for occurrences
of Alarms and Events are defined , to
detect the Alarm
The alarm may be enabled or disabled for a
particular time period or scheduled.
GUI:








Display alarms/events according to priority and time as and when
they arrive with their values.
Allow user to acknowledge specific or all alarms.
Allow user to attach messages or comment with each
alarm/event he acknowledges or the alarms/events previously
present into the database.
Allow users to display the events for various time periods, by a
particular SCADA point, priority etc.
Allow users to sort alarms/events according to a category.
Allow users to update the limits and store it in a file.
Online help will be provided.
User can search for alarms and events depending on their type.
Example of Sample Interfaces for Displaying
Alarm
Database and Data Logging





The database acts as a repository of each generated values and
timestamp is fixed to each entry in database and these values
are later analyzed and displayed for decision making
mechanisms.
The data coming from field is analog and stored in the database
as both analog and digital with their type defined.
Storage of Events related data in user defined format in
database in minute , hourly , daily , weekly basis with its status
The common practice for record keeping is to capture the
Pre selected datasets at periodic intervals
System Design diagram
Value generator(Simulator)
R
T
U
System
Alarm/Event
Monitor Module
Alarm/Event Limit check
Database
Load Limits
GUI
PROCESSING:







Login and Password Authentication
Accept the username and password and validate it.
Start the alarm/event simulator.
Alarm/Event monitoring system collects the data from the
Alarm/Event generator system after every 2 seconds.
Limit Check module then checks the values and send it to GUI
and logged into the database depending upon the range.
GUI shows current alarms and events by getting values every
two seconds.
User acknowledges alarms and attaches messages to events
and alarms.
The following things can be done after the above steps



User edits limits and stores them back to the file
User searches for alarms and events.
User can update information already present
Tools Used:



GUI: VC++ 6
Programming: C++
Database: MS Access
Thank you
Group 16
Arvind Tiwary
Ashutosh Parida
L. Jagannathan
Nitin Gupta