SRS Rules - Alarming-related Functionality
(Doc ID 1296493.1)
Last updated on FEBRUARY 02, 2024
Applies to:
Oracle Network Management for Utilities - DMS - Version 1.12.0.3 and laterOracle Utilities Network Management System - Version 1.12.0.3 and later
Information in this document applies to any platform.
Purpose
Alarming Related Rules
For previous releases, refer to the documentation in the Configuration Assistant.
The purpose of this page is to describe JMService rules that can be configured. For each rule, there are the following values to specify:
- set_name
- A name used to identify what set a rule should belong to. This value,
along with the rule_name value, comprise the primary key for the srs_rules
table. If not using the defaultRuleSet rule, then
you should have at least one set of rules called "normal", as that is what
set JMService will attempt to use in that case.
If a set_name value is specified in a rule description, then no deviation should be made from that name in the configuration. If a set_name is not specified, or a * is listed, specify this rule as needed for each rule set that can be changed in the Authority tool. - rule_num
- An integer value, used in conjunction with set_name to comprise the primary key for the srs_rules table.
- rule_active
- This should be set to either 1 or 0. A value of 1 would indicate that the rule is actively in use in the rule set. Specifying a value of 0 is a way to deactivate a rule in a set without having to remove it from the population script.
- incident_type
- See each individual rule description for valid value for this column.
- rule_name
- A character string. The name of the rule itself.
- rule_value_1
- A character string. See each individual rule description for valid and default values, if applicable.
- rule_value_2
- An integer value. See each individual rule description for valid and default values, if applicable.
- ncg_cls
- Used in conjunction with the ncg_idx value to narrow the application of a rule to a specific control zone, if desired. Only a small subset of the rules are eligible to use these values -- see the individual rule descriptions. A value of 0 should be specified if a) ncg_cls and ncg_idx do not apply to a rule or b) it is desired to have the rule values apply to all control zones.
- ncg_idx
- Used in conjunction with the ncg_cls value to narrow the application of a rule to a specific control zone, if desired. Only a small subset of the rules are eligible to use these values -- see the individual rule descriptions. A value of 0 should be specified if a) ncg_cls and ncg_idx do not apply to a rule or b) it is desired to have the rule values apply to all control zones.
- zone
- Name of the control zone, derived from the combination of ncg_cls and ncg_idx.
- rule_value_integer_1
- An integer value. See each individual rule description for valid and default values, if applicable.
- rule_value_integer_2
- An integer value. See each individual rule description for valid and default values, if applicable.
- rule_value_integer_3
- An integer value. See each individual rule description for valid and default values, if applicable.
- rule_value_integer_4
- An integer value. See each individual rule description for valid and default values, if applicable.
- rule_value_integer_5
- An integer value. See each individual rule description for valid and default values, if applicable.
Class-based rules
There are a number of rules (such as commonStopClass
and openGroupThreshold)
which can be specified for multiple device classes. rule_value_1 for these
rules can either be the name of a device class or a special class combination
using + to specify a class and all its descendants and - to omit a class.
Examples:
- class1
- Specifies class1
- class1+
- Specifies class1 and all its descendants
- class1+,-class1
- Specifies all the descendants of class1 but not class1 itself
- class1,class2
- Specifies class1 and class2. Identical to configuring two instances of the rule (one for class1 and one for class2).
- class1+,-class2
- Specifies class1 and all its descendants except class2
- class1+,-class2+
- Specifies class1 and all its descendants except class2 and class2's descendants
Alarming Related Rules By Function
- Crew contact alarms
- Critical customer timed alarms
- Estimated restore time alarms
- Feeder threshold alarms
- Priority crew assignment alarms
Alarming related rules
Timed Alarm Types
Timed alarms are alarms that are scheduled for issue at a later time. They can be scheduled when the outage is created (the outage was created with certain characteristics that match a rule definition), when the outage is modified (the outage may not have originally possessed certain characteristics that matched a rule definition when it was originally created, but now it does), or when the SRS rule set changes (the new rule set may contain rule definitions that match characteristics of outages whose characteristics didn't match any definitions in the old rule set).
There are currently five types of timed alarms:
- Critical customer alarms
- Critical customer alarms are created when there is an outage that affects critical customers. These alarms occur at a rule-defined interval after the outage, and, once triggered, recur at another rule-defined interval. These alarms will not occur if a crew is enroute to the outage.
- Customer alarms
- Customer alarms are created when there is an outage that affects a number of customers in a given range. There can be multiple alarm definitions for customer alarms, all with separate messages and alarm times. These alarms occur at a rule-defined interval after the outage and do not recur. One feature of these alarms is that they can define a "limited service time" in which certain alarms will not be issued. These alarms will not occur if a crew is enroute to the outage.
- Feeder alarms
- Feeder alarms are created when there is an outage that affects a breaker. The class of the breaker has to be specified in a rule. It triggers an alarm at a rule-defined interval after the outage is created, and the alarm does not recur. This alarm will not occur if a crew is enroute to the outage.
- Estimated restore time alarms
- Planned outage alarms are created when a planned outage (i.e. an outage created by an active switching order) exceeds its estimated restore time. Estimated outage alarms are created for any active outage when current time exceeds configured threshold with relation to the estimated restore time.
- Outage duration alarms
- Duration alarms are created when outage duration exceeds rule-defined value. Once this alarm was created for given outage it will not be recreated again for the same outage.
Crew contact alarms
These rules control the generation of crew contact alarms. When turned on, these alarms are generated at a specific time (called the next contact required time) for each crew in the enroute or on-site state
Critical customer timed alarms
Critical customer alarms are created when there is an outage that affects critical customers. These alarms occur at a rule-defined interval after the outage, and, once triggered, recur at another rule-defined interval. These alarms will not occur if a crew is enroute to the outage.
Estimated restore time alarms
Planned outage alarms are created when a planned outage (i.e. an outage created by an active switching order) exceeds its estimated restore time. Estimated outage alarms are created for any active outage when current time exceeds configured threshold with relation to the estimated restore time.
Feeder threshold alarms
These alarms are generated a specified amount of time after the start of an outage affecting a feeder breaker.
Priority crew assignment alarms
These rules control the Priority Assignment alarms. These alarms are issued when a priority assignment has not been acknowledged by a crew (indicated by the event transitioning to an event state)
- alarmTooltipMaxRows
- crewIncAlarm
- criticalIncAlarm
- DDSAlarmsMaxHistoric
- disableTimedAlarms
- feederLimitAlarmAttributes
- feederLimitAlarmsEnabled
- feederLimitModeAttribute
- maxDDSAlarms
- NMS_ALARMS_ENABLED
- NMSAlarmsAllowMainAlarmListClosure
- NMSAlarmsDisplayUponNewUnackAlarm
- NMSAlarmsMaxActive
- NMSAlarmsMaxHistoric
- outageDurationAlarm
- outageSizeAlarm
- outageThresholdAlarm
- priorityIncAlarm
- priorityIncTimedAlarm
- ScadaMaxAudit(2)
- timedStateTransition
Scope
This document is intended for NMS system administrators.
Details
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |