Transcript Alarms and Events Logging

Alarms and Events Logging
Project Mentors:
Suneel Kumar
Venugopal Vanga
‘Alarms’ Requirements
• Alarms are raised at any ‘point’ in the
SCADA system, when the value exceeds a
particular range.
• The range can be dynamically varied
depending on weather.
• There should be stages of severity of
alarms.
Alarms Contd.
• Alarms are displayed online and need not
be stored in the database.
• An alarm should not be erased before the
user takes appropriate action
• Alarms should be sorted according to
order of priority before displaying it.
• Alarms can be edited
‘Events’ Requirements
• Events are also like alarms but can be
generated even when the value is within
the ‘safe’ range.
• Events need to be logged into the
database
• Events are in fixed format.
• Events cannot be edited
Events Contd.
• Events are written with the date and time
into the database and does not need user
intervention.
• Search for events that occurred years
back.
System Design diagram
R
T
U
System
Alarm/Event generator
Alarm/Event
Monitor Module
Control System
Database
GUI
Prerequisites and Outstanding
Issues
• All information like limits associated with
SCADA points are stored in the database
previously.
• Only events are logged. Alarms are not
entered into the database.
• Alarms are lost once the system is shut
down. No recovery is possible.
Steps In processing
1. The Event/Alarm monitor program
2.
3.
continuously checks for events/alarms.
As soon as one is raised, it informs the control
system about the point in the SCADA system in
which it is raised, the value at the point.
The control system analyses the event/alarm
and compares with the limits that are in the
database.
Steps Contd.
• For the alarms two types of lists are
maintained Acknowledged/
Unacknowledged.
• As noted in the requirements the severity
of the alarms, the priority for the SCADA
point, present weather are all used to
appropriately position the alarm in the
unacknowledged list.
Steps Contd.
• Events are first logged into the database
before informing the user
• They are persistent.
• There is no need for user
acknowledgement of events.
Plan of the design
• Generating program though external to
the system is a part of the project.
• The monitor system, generating program,
the control system form the major part
and would be independently developed.
• The database and the GUI will be
developed simultaneously with the other
parts.
Questions?
Nitin Gupta
Arvind Tiwary
L. Jagannathan
Ashutosh Parida
Thank You