Event properties
...................................................................................................................................................................................................................................
Introduction
In order to bring the event behavior in line with the chosen maintenance philosophy
event properties have to be configured. The event properties of the following events
can be configured:
• Alarms
• Autonomous Events
• Station Alarm
Important! In general we will refer to any of the three above-mentioned, as event.
Purpose
The properties of an event will determine:
• if an event will appear;
• when the event will appear;
• how the event will appear;
• when the event will disappear when the problem is solved.
Event status
An autonomous event go through a short sequence of statuses before the event is
considered solved and therefore, ready to be archived as historical data. Therefore, the
event status is the attribute that allows to monitor where in the sequence the event
finds itself at any point in time.
The sequence is the following:
• It is raised by the system;
• It gets acknowledged by a maintenance operator;
• The cause of the alarm is attended to, and the problem gets solved.
The table below describes each alarm status:
Status Description
Raised
A valid status when the conditions for alarm detection
are TRUE and that the cause has not yet been
acknowledged or resolved. The alarm can be reported
or not.
Cleared
A valid status when the conditions for the alarm
detection are no longer TRUE because the cause(s) of
the alarm has been removed. The alarm gets cleared
either by the system or by Maintenance personnel. The
alarm is then transferred and displayed in the History
Alarm list.
Alarm management
...................................................................................................................................................................................................................................
6-8
Alcatel-Lucent - Proprietary
See notice on first page
365-312-807R7.2
Issue 4, May 2007
To Next Page
Loading...
