SRS Rules - Grouping / Prediction (Doc ID 1297156.1)

Last updated on FEBRUARY 02, 2024

Applies to:

Purpose

Grouping / Prediction Related Rules

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

Grouping / Prediction Related Rules By Function

• Fuzzy call grouping
• Manual grouping
• Outage grouping thresholds
• Outage prediction / movement
• Outage upgrading
• Phase grouping
• Substation outages

• Grouping / Prediction related rules

  Rules controlling job and call grouping / prediction

  • Fuzzy call grouping

    These rules control how fuzzy calls get grouped

    • groupFuzzyCalls
    • streetXsectionOffset

  • Manual grouping

    Rules controlling manual grouping, particularly which jobs can be manually grouped.

    • completedManualGrouping
    • freezeOnManualGrouping
    • noManualGroupingCrews
    • onlyDownManualGrouping
    • PMOManualGrouping
    • transferCallTroubleCode

  • Outage grouping thresholds

    These rules control time thresholds for when calls and jobs are allowed to group

    • deadband
    • groupOutageMaxAge
    • openGroupThreshold
    • scadaOpenGroupThreshold

  • Outage prediction / movement

    These rules control the prediction and movement of jobs and calls

    • allowConsumeNonMovable
    • allowMeshManualMove
    • allowSOGrouping
    • commonStopClass
    • crewOutageCanMove
    • downgradeDOOnManualMove
    • eventDistanceDO
    • eventDistanceSO
    • eventPerRestoration
    • feederMaxOutages
    • groupByFeeder
    • movableAfterManualMove
    • moveUpIsolatedOutage
    • numPOsBeforeReGroupDO
    • numPOsBeforeReGroupDOclass
    • numPOsBeforeReGroupSO
    • numPOsBeforeReGroupSOclass
    • oneSNDPerXFM
    • onlyFirstBranchPartial
    • partialRestorationsViewOnly
    • percentCustomersBeforeGroup
    • percentOutagesBeforeGroup
    • regroupAfterManualMoveDownstream
    • stableAfterManualMove
    • traceFromOperatedDevice
    • useMaxEventDistance

  • Outage upgrading

    These rules control the upgrading of service outages to device outages

    • customerEqualsCalls
    • deviceNumCallsMoveUp
    • deviceNumCallsUpgrade
    • numCallsBeforeUpgrade
    • percentCallsBeforeUpgrade

  • Phase grouping

    These rules control whether outages are phases sensitive and whether grouping rules are phase sensitive

    • groupByPhase
    • poPhases

  • Substation outages

    These rules control how outages and grouping in substations behave

    • moveSubOutagesDown
  • copyNewRelEventFields
  • doNotAutoRelateClue
  • ertCopyPolicy
  • ertSelectionMethod
  • groupByCommonPhases
  • groupByCrossedPhases
  • makeStableDelay
  • nonOutageGrouping
  • relateEventsOnRepredictDownstream

Scope

This is intended for NMS Administrators

Details