Using Alarm History
Introduction
The SR30.1 load and above adds the Alarm History capability to the EMS. This Application note will detail the Alarm history Capabilities of the system.
Document Number
ENG-010629
Applies To
SR30.1 and above of the Panorama PON EMS.
Feature Summary
The SR30.1 release adds several capabilities to alarms that significantly enhance the ability to diagnose issues with the system via the alarms display:
- Filters that allow filtering of alarms by Severity, Acknowledged Alarms or Probable Cause
- Ability to Acknowledge Alarms
- Alarm Tracking Notes
- Alarm Troubleshooting Notes
- Alarm History
- Alarm History Filtering by Severity, Acknowledged Alarms or Probable Cause
Alarm Filtering
The Panorama PON now supports the ability to filter alarms to enable filtering alarms down to just the subset of alarms of interest.
Alarms can be filtered by the severity of the alarm.
From the alarms display, you can select the severity button and check the list of severities that you want to see. This will filter the alarm display down to alarms of the selected severities.
When the filters are selected, they will be shown in the "Selected Filters" section of the screen and specific filters can be deleted at any time by clicking the red x on the appropriate filter.
You can also filter by the alarm type or probable cause. This is a multi-select field, so <Ctrl> click will allos seclecting multiple individual probable causes. The normal <shift> click paradigm of windows can also be used to select a group of probable causes all at once.
Alarms can now be acknowledged so that nuisance alarms can be ignored and removed from the active alarms display.
Use the right-click menu of any alarm to acknowledge the alarm.
The severity of the alarm will then turn white indicating it is acknowledged as shown below in the case of the GPON Transmitter Failure Alarm.
Acknowledged alarms can be removed from the display by clicking Unacknowledged alarms in the filter display.
Alarm History Display
The Panorama PON has also added an alarm's history display which allows viewing, sorting, and filtering alarm history. The alarm history shows all alarms that have occurred in the system in the past, shown by default in chronological order. This allows looking back into history to analyze failures that occurred in the past and seeing alarms that have been set and cleared.
Both the set and clear will appear as separate entries in the Alarm History:
The current alarms display only shows alarms that are currently set and does not show history.
The alarms can also be filtered the same way as the current alarms display. Alarms can be filtered by severity, whether or not they have been acknowledged, probable cause and date range.
The date range feature allows display of alarms within a given time frame.
There several standard date range filters:
- All: All alarms regardless of date.
- Today: Only alarms that are set or cleared today.
- Last 2 Days: Show only alarms that set or cleared in the last 2 days.
- Last 7 Days: Show only alarms that cleared in the last week.
- Custom: Define a Custom Date Range.
The Custom filter allows choice of the specific date range to display using a calendar:
Alarm Tracking and Troubleshooting Notes
The alarm display also has two new added features, Alarm Tracking Notes, and Alarm Troubleshooting Procedures.
1. Tracking Note: This field allows notes to be made in a specific alarm instance and will remain with this alarm instance. This allows tracking work done on a specific alarm to correct it. It will also end up in the alarm history and be preserved.
An alarm is shown below that has an alarm Tracking note.
2. Troubleshooting Procedure: This is an editable field that is designed to contain the default troubleshooting steps associated with that alarm type. The data is stored with that alarm type and will be shown on any alarm of that type. This allows documentation of standard practices for clearing an alarm of a specific type. Any notes will appear in any future alarms of that type and serve as guidance for personnel performing troubleshooting.