DH-200 Metering data processing
The diagram above outlines the data structure of metering data. In Datahub, there are three kinds of metering points: accounting points, exchange points and production units (NBS’ Production Unit/PU). Metering data relates to all metering points but a metering time series can only relate to a single metering point. It is possible to report reactive energy input and output measurements for all metering points. It is not possible for an accounting point to have two (active energy) metering time series that are used in billing and imbalance settlement. As an example, in sites where accounting point consumption consists of several metering time series, only one (sum) time series is reported to Datahub.
An exchange point can have one to four metering time series depending on whether electricity can be transmitted in both directions and whether reactive energy of the exchange point is also forwarded. Each exchange point must include data specifying either the direction of the electricity transmission at the exchange point or specifying that electricity can be transmitted in both directions.
A production unit’s own consumption is reported for a consumption accounting point created specifically for that purpose with sub-type production unit’s own consumption. For each exchange point a metered data responsible MGA is defined. Metered data responsible MGA refers to the metering grid area that is managed by the metering responsible DSO of the exchange point. The metering responsible DSO reports energy transmitted in different directions at an exchange point (from a metered data responsible MGA to parallel MGA and vice versa) separately using two active energy metering time series, and if needed with two reactive energy metering time series. Metering data does not deal with readings; instead all metering data must be converted into time step energy (= average hourly power for an hourly metering).
Metering values can be reported to Datahub and retrieved from Datahub using the desired unit (Wh, kWh, MWh, GWh or varh, kvarh, Mvarh, Gvarh). Metering data can be delivered with an accuracy of at most 1 Wh. For accounting points at which the fuse size or corresponding electric power is max. 3x63 A, it is recommended to provide metering data with an accuracy of 1 Wh. The minimum requirement is 10 Wh. For accounting points where the fuse size or the corresponding electric power is greater than 3x63 A, the minimum requirement for the accuracy of metering data is 1 kWh. When reporting metering data, attention must be paid to the number of decimal places. For example, kilowatt-hours (kWh) must be reported with at least two and at most three decimal places for an accounting point of max. 3x63 A. When searching for metering data, please specify the units you would like the search to return.
A DSO must report metering data using the time step that is specified in the law and that is used in the imbalance settlement. The Finnish electricity retail market will move from hourly metering to a 15-minute metering with a transition period starting from 1 January 2023. The Nordic countries moved from an hourly settlement to a 15-minute balance settlement (quarterly balance settlement) from 22 May 2023. Because of this, Datahub will support different time steps for metering data (e.g. 15 minutes and 1 hour). Metering data can still be retrieved from Datahub using the desired time step (e.g. 15 minutes, hour, month). If no time step has been submitted for the search, Datahub will return the metering data using the unit provided by the DSO.
Datahub supports the audit-trail function, meaning that all changes made to metering data are recorded in the history data.
The DSO must report metering data timestamp, metering value and metering data status in its metering data report. In addition to these, Datahub maintains information about the edit time, editor and the reception time for metering data. The time of update is determined based on the time at which Datahub stores the data in its database. The editor attribute keeps track of which process or user has edited the information at the edit time. In general, only the DSO can update metering data with metering data reports. The Datahub operator edits metering data only at the request of the market parties in special error situations, and the edited data will be forwarded to the parties entitled to it. Datahub also registers separately the storage time of the metering data, which can be used to accurately verify afterwards at what time Datahub received the metering data.
Only positive values are processed in Datahub. E.g., consumption and production should always be separately reported. Metering data is processed in accordance with official Finnish time. When moving clocks forwards and backwards to account for daylight saving time, the length of day is either 23 or 25 hours accordingly.
Processing reading metering and unmetered sites
Datahub does not receive or process reading metering readings. The DSO must calculate or otherwise compile reading metering profiles by accounting point and report them to Datahub. In Datahub, profiles should be created according to the type user group 1 reference curve set out in the current metering decree. This procedure requires changes to the content of the metering decree. The profile will be created based on an annual use estimate for the accounting point. There will be a move away from the use of a so-called balancing energy forecast calculated for type user group 2 and the related temperature adjustments which are currently used.
Profiles calculated by DSOs based on an annual consumption estimate are reported to Datahub with status ‘Uncertain’. Status ‘OK’ is used for profiles when the DSO reads the readings from a meter and then, based on the reading, calculates an adjusted profile up to the previous reading time. As such, the same status rules apply to reading metering as for other metering. If a DSO adjusts the status of a profile reported as ‘OK’, the adjusted metering data must be reported with the status ‘Corrected OK’.
There are some accounting points at which there is no energy metering. These are usually referred to as unmetered accounting points and constant power sites. The DSO must also report metering data in time-series format for these sites. The DSO may compile a profile for an unmetered accounting point in the manner it sees fit, such as reporting the same energy for each time step or by using the aforementioned type user group 1 reference curve. Metering data from an unmetered accounting point is assigned the ‘Estimated’ status and adjustments are made using the status ‘Corrected OK’.
The profiles for reading metering sites and constant power time series are reported in Datahub in the same manner and with the same time limits and validations as for other metering data.
Correction of metering data
The DSO must correct erroneous metering data in Datahub for the entire time during which the metering data is stored in Datahub (6 years). Corrected metering data is sent to all parties entitled to the data in accordance with their rights. As such, parties can receive corrected metering data for the entire time during which the metering data is stored in Datahub. Corrected time series data for a supplier’s agreement period will not be forwarded to the supplier of the accounting point if the supplier’s agreement has ended more than six weeks before the data reporting date.
Corrections to metering data may relate to the correction of a customer’s billing if the customer has already been billed based on erroneous data. In these cases, Finnish Energy’s guidelines are applied in Datahub: a metering data correction is reported to Datahub when the customer has been notified or an agreement has been reached with the customer about the correction of metering data. Thus the customer’s correction invoicing is done, on the part of metering data changes, by the suppliers who on the date of the metering error correction report have a valid agreement or an agreement that has ended at most six weeks ago from the date of metering data correction report on the accounting point for which the metering data is corrected. For a supplier change of agreement, i.e., a new agreement by the current accounting point supplier where at least one customer remains the same, does not free the supplier from the responsibility to make corrections. This is described in more detail in the figure below.
The DSO is always responsible for invoicing corrections related to its own grid service and related to sales agreements that ended over 6 weeks before the metering data correction report (corrections to customers B and C in the figure above). Metering data corrections are taken into account in correction of balance deviations and the balance deviation is always recorded for the effective time of metering error when the invoicing correction of sales agreement is the responsibility of the supplier.
Processing reactive energy data
Datahub allows the reporting and retrieval of metering data on reactive energy input from the grid (inductive) and output to the grid (capacitive) to accounting points, production units and exchange points. With regard to reactive energy, Datahub acts solely as a data transmitter. As such, Datahub does not carry out calculations for reactive energy metering data or monitor reports of this data. Only the validation of negative values and status transitions will be carried out for reactive energy metering data, since grid input and output must be reported in their own time series. Reactive energy data is not automatically transmitted to suppliers. An information field will be added to the accounting point, indicating that reactive energy metering data is available for the accounting point. Based on this information, the supplier may order the transmission of reactive energy metering data in the Datahub interface. Information concerning the availability of reactive energy metering data is updated by Datahub depending on whether the DSO has reported new reactive energy metering data in the last month.
Processing exchange point and production unit metering
Exchange point and production unit metering data is required in Datahub in order to calculate a DSO’s imbalance settlement. This metering data is reported in the same way as other metering data and metering data can also be corrected outside the balance window. However, balance deviations are not registered based on metering data corrections for exchange points and production units. Instead, possible monetary corrections caused by these corrections will be handled privately between the metering responsible party and its counterpart (another grid owner).
Exchange points and production units have similar connection status information as accounting points have. Grid operator can temporary remove production unit or exchange point from use by changing the connection status to ‘under construction’. In this case, no metering data needs to be reported to these metering points.
It is the obligation of the metering responsible party of the metering point to report exchange point metering data to Datahub. As such, the transmission system operator and regional grid companies, for example, must report exchange point metering data if the imbalance settlement for the exchange point’s other metering grid area is processed in Datahub. The validation and processing of exchange point and production unit metering correspond to the processing of other metering data where applicable.
Netting and energy community calculation
Datahub performs netting and energy community calculations for the metering points included in the calculations, based on the reported metering data.
Metering data events