Analytic Events

Itron Analytics closes analytic events automatically when it receives reading data indicating that the conditional thresholds which initiated the analytic event are no longer present.

Occasionally, service points that are no longer being used can remain in the field because the utility did not remove it or set it to an inactive status. If these service points had met conditions that initiated an analytic event, Itron Analytics can continue reporting the analytic event indefinitely.

To prevent this reporting anomaly, Itron Analytics automatically closes any analytic event that has remained open for longer than 45 days, and for which it has received no reading data within the same time frame.

If you want to change the default threshold value for the number of days analytic events remain open without Itron Analytics receiving reading data for the effected service point, contact your Itron administrator.

• Leak.  Creates an event if the usage is greater than two gallons per hour over a two-day period.

  Tip: Leak thresholds in Itron Analytics are different from leak thresholds in the ChoiceConnect solution. Itron Analytics does not use the flag from the 100W ERT module. Instead, Itron Analytics evaluates a leak based on threshold values and consumption data.

• NoUsageActive. Creates an event if the service point status is active and the usage is less than 10 gallons per day over a three-day period. The usage also must be a positive value.

• ReverseFlow. Creates an event if the usage in any hour is less than negative one gallon, or at least two reverse flow device events are submitted via CEF file or OpenWay Collection Manager API since the last event analysis.

• UsageInactive. Creates an event if the service point status is inactive usage is greater than one gallon per day.

An Outage event's start time is the first Power Down event. More than one Power Down event may occur before a Power Up event is received.

An Outage event's end time is the first Power Up event after the corresponding Power Down event. More than one Power Up event may occur after a service point has been re-energized.

If no Power Up event exists in the import batch, an Open Outage flag is enabled, and the Outage is considered an open event. During subsequent data imports, Itron Analytics searches service points with Open Outage flags for a Power Up event or interval readings. If either are found, the event's end time is set, the Open Outage flag is disabled, and the Outage is considered a closed event.

An Outage event's duration is the difference of its start and end times. Depending on the duration and a threshold configured in the Admin Portal, Outage events are presented to the user as either Momentary Outages or Sustained Outages. For more information on this threshold, see Editing the momentary or sustained outage threshold.

When children of a piece of equipment experience outage events within three minutes, the event "rolls up" to become an equipment outage. For example, if all the service points connected to a transformer have outages at the same time, the transformer reports an outage. If all the transformers connected to a feeder section have outages, the feeder section reports an outage. This rollup can extend from transformers to substations. The percentage or count of children required to be out before rolling up can be configured. Service points that are members of the NonOutageReporting group are excluded from roll up calculations.

Outages are also rolled up by phase for singlephase service points. For example, if all service points connected to Phase A of a transformer have outages at the same time, but not all service points connected to other phases are affected, the transformer reports an outage for Phase A only. If the phase for some connected service points is unknown, all service points of a given phase and all service points with unknown phase must experience outages for the event to roll up.

Outages can also roll down from DTM meters on equipment to their children. For example, if a transformer DTM meter reports an outage on all phases, all child service points are assumed to have an outage.

Low Voltage (LV) and High Voltage (HV) events are initiated by device events when the measured voltage crosses thresholds defined in the meter configuration. The LV event is created when one or more intervals at a service point experiences voltage below the low threshold during a day. The HV event is created when one or more intervals at a service point experiences voltage above the high threshold during a day. A single event is created whether one interval, some intervals, or every interval crosses the threshold. When consecutive days experience events, they are combined into a single LV or HV event with a duration of multiple days.

Theft is a category that includes several types of events.

• UsageInactive. This event is triggered if usage above <x> occurs for <y> days on a service point set to inactive.

  ...where <x> and <y> are components of the threshold defined in the Admin Portal.

• NoUsageActive. This event is triggered if usage below <x> occurs for <y> days on a service point set to active. The usage also must be a positive value.

  ...where <x> and <y> are components of the threshold defined in the Admin Portal.

• Tamper. This event is triggered if a tamper device event is received. This is defined in the CEF file or OpenWay Collection Manager API.

• Outage. This event is triggered when a Power Down event is followed by a Power Up event. For more information, see the Outage Events section.

• Inversion. This event is triggered if a Power Down event is followed by removal, a tilt, and a Power Up event.

• Removal. This event is triggered if a Power Down event is followed by removal and a Power Up event.