Transcript MATLAB TUTORIAL - International Institute of Information

Alarms and Events
Processing
Group No. 2
Project Guide:
Prof. N.D.R.Sarma
Introduction
 Alarm/Event processing –a key component of SCADA system.
 User is notified of the alarm generated and allows to take
necessary action
 It adds security to the SCADA system.
 It traces the exceptional behaviors in devices and their values
like current and voltage.
 It allows remote monitors and control the field devices.
Alarm Requirements
 Alarms are raised at any ‘point’ in the SCADA





system, when the value exceeds a particular range.
The range can be dynamically changed depending
on conditions.
There should be stages of severity and categories of
alarms.
Alarms are displayed online.
Alarms needs user intervention.
Alarm may be enabled, disabled or scheduled for a
particular time .
Alarm Requirements
 Alarm are moved from unacknowledged list to
acknowledged list as soon as they are processed by
the user
 An alarm should not be erased before the user takes
appropriate actions
 Alarms should be sorted according to order of priority
before displaying it.
 Display of historical and current alarms.
Alarm Categorization and Priority
 Alarms are classified as acknowledged/unacknowledged.
 Depending on the value we can prioritize the alarm.
 Alarm can be categorized based on Current , Voltage ,
Transformer ,substation , feeder level etc .
 Alarm categorization based on severity or priority .
Level 1 Alarms → Audible + Onscreen Display in Red
(very very high alarm or very very low alarm )
Level 2 Alarms → Onscreen Display in Blue
(very high alarm or very low alarm )
Level 3 Alarms → Onscreen Display in Green
(high alarm or low alarm )
Event Requirements
 Events are also like alarms but can be generated





even when the value is within the ‘safe’ range.
Events should be logged into the database
Events are in fixed format.
Events are stored with date, time etc. into the
database and does not need user intervention or
acknowledgement .
Events in the past can be searched.
Events don’t have priorities.
System Design Modules




Generator Module
Alarm and Event Monitoring and Control
Alarm/Event Reporting and Processing ( GUI )
Alarms/Events Logging (Database)
System Design
Generator Module
 A data generating routine ( a simulator of the field
values received from RTU) used to feed the data.
 Generates random values of Device ID , Event ID ,
Value , SCADA-point etc . according to some
format (Lit-ID) : V_065_IIIT_001_30/09/2004_12:00
V,I
Can be V/I etc
V → Voltage
I → Current
065
Voltage level (65 KV here)
IIIT
Substation name
001
Unique identifier
30/09/2004
Date
12:00
Time
Alarm and Event Monitoring and
Control
 Reads values generated by simulator in fixed time
interval .
 The value is checked for the limits and status,
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 and logged into database .
Alarm and Event Monitoring and
Control
 Controls and coordinates the Generator, GUI and
database .
 It runs the simulator, handles interfaces between
modules .
 Refreshes the GUI periodically .
 Addition and Updating of the database are done
through it.
Alarm/Event Reporting and Processing
( GUI )
 Automatically report alarms/events to the interface with their
category, severity, time-stamp etc .
 Dynamically updating a display window with time varying data.
 Allows user to perform alarm processing like




Searching for alarm and event depending on their types ,
categories, time-stamp etc .
Update the limits for detection
Acknowledge / Delete specific or all alarms
Display the events for various time periods, by a particular
SCADA point, priority etc.
Alarms/Events Logging (Database)
 The database acts as a repository of each generated
values which are later analyzed and displayed for
decision making mechanisms or search queries .
 The data 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.
Alarms/Events Logging (Database)
 Database stores


Limits
Alarms and its related data like
 Alarm Date and Time ,Acknowledgement Date
Message ,Value , Alarm Type , Alarm Id , Device
Name or ID , Alarm status , acceptor name

Events and its related data like
 Event Date and Time , Message, Value, Event
Type , Device Name or ID , Event Id etc
Summary
 Alarm/Event monitoring system periodically collects




the data from the Generator .
Control system checks the values and sends to GUI.
Values are logged into the database depending upon
their range.
GUI shows current alarms and events by getting
values every n seconds
User performs multiple processing on alarms.
QUESTIONS
?