Meter Events Processing

What it does

Smart meters report events: power down and power up, cover removal, phase or current reversal, missing neutral, battery and communication problems, firmware changes. Meter Events Processing stores these events with the meter, keeps the switched-off status of the metering point current, and turns the events that need a human into tasks, so that tampering and outages are followed up instead of being buried in logs.

How it works

1. Receive. The head-end system sends an end-device-event message (IEC 61968-9 EndDeviceEvents). The module ships a ready-made mapping for the standard message.
2. Store. Each event is stored on the meter's events channel with its timestamp and its event type, so the event history of a meter is visible in the console next to its readings.
3. Translate event codes. The standard IEC event type codes are translated into readable event types with a built-in dictionary of 40 event types, 15 of which are flagged as critical out of the box: among them terminal cover and meter cover removed, power-down, phase sequence reversal, missing neutral, current reversal, local disconnection, battery replacement, modem and SIM card failures and a failed firmware activation.
4. Update the switched-off status. A power-down event marks the metering point as switched off and a power-up event clears it. Meter Reads Processing uses this status to estimate zero consumption for switched-off periods instead of flagging them as gaps.
5. Create tasks. A critical event is annotated on the meter and creates a task of type event on the End Device Event task board, assigned to the configured operator.

What you see

The Device events dashboard shows:

• the number of datasources with critical events by day;
• the list of datasources with critical events for today;
• the number of events by event type by day;
• the top 10 datasources with most events.

The companion Meter events dashboard reports the number of commands executed in devices by day, the result of Device Control Transactions. Critical events are worked from the End Device Event task board.

What you can configure

• Which event codes map to which event types, and which of them are critical.
• Who is assigned the tasks and on which board they land.
• Differences in your head-end's message format, through the transformation configuration.

Verified behaviour

The package ships with automated acceptance scenarios that run against a live environment. Among others, they cover:

• a message with several events producing the expected task, annotations and tags on the meter;
• a power-down event on an existing meter;
• a power-down and a power-up arriving in separate messages, with the switched-off status set and cleared accordingly.

Standard rules in this module

Rule	What it does
Standard Update MP Switched Off Status Storage	Applies the on and off status changes from power events to the switched-off tag of the metering point.
Standard Annotate Critical Event Validation	Annotates critical events on the meter and creates a task for them on the configured task board.

Extending the module

• Correlate events with your own rules, for example repeated power-downs within one feeder, and raise a single task for the pattern.
• Notify external systems or people by email or messaging from a rule.
• Extend the event dictionary for meter brands with vendor-specific codes.

Installation and updates: standard-packages.