Master Data Processing

What it does

Master data describes what is being metered: the meters, the metering points they serve, the network areas those points sit in and the contracts that apply. Master Data Processing keeps this foundation in the platform up to date from the standard messages your asset or customer system already produces, so that every downstream process, from VEE to billing, works on a correct and dated picture of the installation.

How it works

1. Receive. A source system sends an IEC 61968-9 (CIM) message: MeterConfig for a meter, UsagePointConfig for a metering point, CustomerAgreementConfig for a contract and MasterDataLinkageConfig for the relation between a meter, a metering point and a network area. The messages arrive through the platform's regular ingestion paths.
2. Map and store. The message fields are mapped onto the platform data model: a meter or a metering point becomes a datasource, its attributes become tags with a validity period, so history is kept whenever something changes.
3. Link. A linkage message relates a meter to its delivery and redelivery metering points and records the direction of each channel. It can also place a metering point in a network area such as a transformer, a feeder or a substation. Meter installation and removal and network connection and disconnection are the recognised reasons; a removal closes the relation but keeps its history, so the question "which metering points belonged to this transformer on that date" can always be answered.
4. Validate contracts. The tariff named in a customer agreement must exist as a time-of-use definition (timeslice group) in the platform. If it does not, a task is created on the Invalid tariff task board so the contract can be corrected before billing needs it.
5. Acknowledge. The sender receives an acknowledgement for every processed message, so the exchange can be reconciled on both sides.

What you see

The Meter Overview dashboard answers the questions an asset or metering team asks every day:

• Orphan meters: meters without a metering point, as a count and as a list.
• Switched-off meters, as a count and as a list.
• Non-communicating meters: meters with an active contract but no recent data, as a count and as a list.
• Metering points not related to a transformer, as a count and as a list.

Contract problems appear as tasks of type Tariff on the Invalid tariff task board.

What you can configure

• Field mappings for your own message variants and additional attributes, through the transformation configurations.
• The network-area types in use (transformer, feeder, substation or your own) follow from the messages themselves.
• Whether and where acknowledgements are sent, through a messaging topic per namespace.
• The validity dates of relations and attributes are taken from the messages, so late or back-dated changes land on the right date.

Verified behaviour

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

• creating a meter and a metering point from their configuration messages, and the tags that result;
• linking a meter to its delivery and redelivery metering points, including a meter whose two directions are served by different metering points;
• deleting a linkage, and linking the meter again;
• connecting a metering point to a transformer and disconnecting it again, and rejecting a linkage message with an unknown reason;
• an invalid tariff name producing a task;
• the dashboard queries for orphan, switched-off, non-communicating and not-related-to-transformer meters.

Standard rules in this module

Rule	What it does
Standard Tariff Name Validation	Checks that the tariff of a customer agreement exists as a timeslice group, and creates a task when it does not.
Standard Update Linkage Storage	Creates or updates the relation and direction tags on the meter and the metering point, and closes a relation when a linkage is deleted.
Standard Acknowledge Forwarding	Sends an acknowledgement message for a processed message.
Standard Map Values Transform, Standard To Date Transform	Translate message values and dates onto the platform's data model during ingestion.

Extending the module

• Add message types or attributes with a transformation configuration, without code.
• Add your own checks, for example completeness checks before a meter is taken into operation.
• Reuse the dashboard queries in your own reporting through the platform's analytics.

Installation and updates: standard-packages.