Oracle Utilities Network Management System Configuration Rules
Below is the list of configuration rules in the Oracle Utilities Network Management System, which control AMR-related functionality. These rules are not directly used by the Oracle Utilities Network Management System MultiSpeak Adapter.
amrInterfacesEnabled
This rule enables AMR processing in JMService. Its value indicates the AMR processing types that are available. AMR processing is disabled if this rule is set to 0 (default value).
Available types of AMR processing:
The rule value is a bitmask, which allows any combination of AMR processing types to be enabled. For example, if the rule is set to 9 then Outage Detection and Restoration Verification will be enabled.
meterOffThreshold
Maximum probability of meter having power when meter is still assumed to be "off". Default value is 0.
meterOffTroubleCode
Trouble code to be used when a call should be created because of information received from AMR system.
meterOnThreshold
Minimum probability of meter having power when meter is still assumed to be "on". Default value is 100.
meterQueryThreshold
This parameter is used to determine if a meter can be queried when an active request exists. When a new request is made, existing requests will be evaluated to see if any contain meter(s) from the new request. If a match is found, and the difference between the time the request was received and current time is less than value of this rule in seconds, that meter will be rejected from the new request. If set to -1 (default value), this rule will not be enforced.
meterPingPercentage
This parameter governs the percentage of meters to ping for an AMR action. When set to 100, it will ping all AMR meters downstream from the outage device. When set to -1, it will ping one AMR meter on each SND. When set to any other number between 1 and 99, JMService will attempt to ping the specified percentage of meters for each transformer affected by the outage (the resulting number of meters is rounded up so that at least one meter per transformer is pinged). It is possible to configure this rule differently for different device classes. Default value of this rule is 100.
useMeterTimeForDetection
This configuration rule determines if meter read time reported by AMR system should be used as call time for incidents created by outage detection functionality.
Valid values:
useMeterTimeForRestoration
This configuration rule determines if meter read time reported by AMR system should be used to adjust outage restoration time as part of outage restoration verification functionality. Outage restoration time is only updated if restoration time calculated from AMR data is earlier then the current restoration time.
Valid values:
no - outage restoration time will not be modified
latest - outage restoration time will be updated with the latest meter read time amongst the meters which reported power on for the restored outage (this is the default behavior)
earliest - outage restoration time will be updated with the earliest meter read time amongst the meters which reported power on for the restored outage
percentile - outage restoration time will be updated with the earliest meter read time which covers the desired percentile of meters which have reported power on. Percentile value is specified using rule_value_2 field. It should be in the range from 1 to 99 (inclusive).
Meter read times preceding outage start time or past current time are ignored.
Example of ‘percentile’ setting.
rule_value_1 = 'percentile'
rule_value_2 = 50
This configuration corresponding to using median value from the all meter read times for meters, which reported power on. Given following four meter read times
00:00:10
00:00:11
00:00:20
00:00:30
the median value would be 00:00:11 (second value out of four).
meterRequestSendDelay
This configuration rule is used to control how long the outage prediction engine should wait before sending a meter ping request to the MultiSpeak adapter. This rule is only applicable for PSO Verification, PDO Verification, and Restoration Verification requests.
meterRequestTTL
This configuration rule is used to control the "time-to-live" (TTL) for meter ping requests. This is the period of time NMS will wait for a responses from AMR system. Automated meter ping requests (PSO Verification, PDO Verification, and Restoration Verification) are considered completed when TTL expires. Manual meter ping requests, which were not explicitly completed or cancelled by the user, are automatically cancelled when TTL expires.
TTL is configurable per request type. It can either be a fixed value (for example, the PSO Verification request can remain active for 15 minutes) or it can be calculated based on the number of meters in the request combined with minimum and maximum values. If TTL is set to 0, then automated meter ping requests remain active until the first response is received. Manual meter ping requests in this case remain active until explicitly completed or cancelled by the user.
meterPingSuppress
This configuration rule can be used to suppress sending meter ping requests to the AMR system based on the request type.