Not whether the data exists, but who gets in
The metering values for an installation exist. They have been collected, validated and delivered to ElhubNational hub for metering data and market processes in the Norwegian electricity market., and they sit there regardless of who asks.
The question is a different one: who gets to see them, how much, and for how long?
That is not a technical question first. It is a question of who owns the decision, and the answer in the Norwegian market is the end user. An actor that is neither grid company nor electricity supplier for the metering pointThe fundamental unit in Elhub - the unique point in the electricity network where energy is measured and settled, identified by an 18-digit GSRN number. can gain access, but only because someone has said yes. The role code is AG, third party.
Trust sits with the issuer, not with the party asking
This is the part worth understanding, and it is easy to miss because it looks like a detail in a sign-in flow.
The end user signs in with BankIDAn electronic ID issued through the banks, used both for signing in and for signatures with legal effect. at ElhubNational hub for metering data and market processes in the Norwegian electricity market.. Not at the actor that wants the data, and not at the supplier that built the solution.
The difference is the whole point. Had the sign-in happened at the actor, the user would have had to trust a party they may never have heard of, and the actor would have carried a responsibility no one wants. Instead the confirmation happens at the hub, with an identity the user already uses to sign in to their bank.
That makes the consentThe end user's expressed permission for someone else to see or process information about them. In the power market it is the consent that gives a third party access to metering data. something the user gives to ElhubNational hub for metering data and market processes in the Norwegian electricity market. about an actor, not something the user gives to the actor. The shift moves trust from a place where it is expensive to build to a place where it already exists.
Consent is not a checkbox
A consentThe end user's expressed permission for someone else to see or process information about them. In the power market it is the consent that gives a third party access to metering data. that is merely "yes" is worth little to either party. What makes this usable is that it is bounded in three directions at once.
Scope. The user chooses what is shared, not just whether something is shared.
Which metering points. With three installations, yes to one is not yes to the others.
Time. The consentThe end user's expressed permission for someone else to see or process information about them. In the power market it is the consent that gives a third party access to metering data. has a start and an end from day one. The start is the move-in date on the metering pointThe fundamental unit in Elhub - the unique point in the electricity network where energy is measured and settled, identified by an 18-digit GSRN number., that is, the day the user actually became responsible for it. The end sits three years ahead by default.
The time limit is the most important of the three, and the one most often missing in systems not built for this. A consentThe end user's expressed permission for someone else to see or process information about them. In the power market it is the consent that gives a third party access to metering data. without an end date is not a consentThe end user's expressed permission for someone else to see or process information about them. In the power market it is the consent that gives a third party access to metering data., it is a transfer. Here it expires by itself, and can be withdrawn before that.
The expiry arrives without warning
Here is the detail that turns the time limit into a piece of work rather than just a setting: ElhubNational hub for metering data and market processes in the Norwegian electricity market. does not warn when a consentThe end user's expressed permission for someone else to see or process information about them. In the power market it is the consent that gives a third party access to metering data. is nearing its end. It lapses, and that is all.
For the end user that is usually right. A consentThe end user's expressed permission for someone else to see or process information about them. In the power market it is the consent that gives a third party access to metering data. that runs out because nobody renewed it is the mechanism working as intended.
For anyone who has built something on the data it is another matter. A data flow stops on a date nobody was watching. It surfaces as a fault, not as a deadline, and the troubleshooting starts in the wrong place: in the integration rather than in the calendar. Three years is also long enough that everyone involved when the consentThe end user's expressed permission for someone else to see or process information about them. In the power market it is the consent that gives a third party access to metering data. was given may have moved on to other work.
The responsibility for remembering therefore sits with the actor, not with the hub. That is not unreasonable, but it has to be somebody's job, and "somebody's job" is a poor plan when the date is three years out.
One more thing worth noticing
Metering points that access has already been granted to are shown as granted.
That sounds trivial. It is not: without that display a user can grant the same access twice without knowing it, and an actor can ask for something they already have. The interface that shows what has already been given is what lets the user see their own situation rather than just the form in front of them.
The entry ticket is smaller than people think
For the actor that wants to receive such consents, the requirements are modest: a GLNA Global Location Number from GS1 - thirteen digits that uniquely identify a legal entity or a place. In the power market the GLN is a participant's identity. number and a return URL whitelisted at ElhubNational hub for metering data and market processes in the Norwegian electricity market..
That is worth saying out loud, because the expectation is usually quite different. Many assume that access to metering data requires an integration project with a budget to match. For this role it does not. The threshold does not lie in the technology.
It lies in what comes after: receiving the data, understanding the format, and doing something sensible with it.
The history comes, but not immediately
Once the consentThe end user's expressed permission for someone else to see or process information about them. In the power market it is the consent that gives a third party access to metering data. is in place, historical metering values are retrieved through a separate process, BRS-NO-315The Elhub process that retrieves historical metering values for a metering point. Used, among other things, when a third party has been granted access by the end user and needs to see consumption going back in time.. It is asynchronous. The request goes in, and the values arrive when ElhubNational hub for metering data and market processes in the Norwegian electricity market. has them ready.
That has a consequence for anyone building an interface on this, and it is easy to get wrong: the screen has to say that the values are ordered and on their way. An empty graph right after the user has given consentThe end user's expressed permission for someone else to see or process information about them. In the power market it is the consent that gives a third party access to metering data. looks like a fault. It is not, but the user has no way of knowing that unless someone says so.
This is a general pattern in energy data. Much of what looks like a lookup is really an order.
Where we have built it
The AG role is the one this article is about, and TvimenningOld Norse meaning 'two bound together' - one who solves a task shoulder to shoulder with another. holds system approval in it. Without it none of the above is possible in practice: the consentThe end user's expressed permission for someone else to see or process information about them. In the power market it is the consent that gives a third party access to metering data. can be given, but there is no one on the other side able to receive it.
SAMTYGD is the integration layer that does the work, and it is not new code. The core has been in active production since 2019, was ElhubNational hub for metering data and market processes in the Norwegian electricity market.-approved in 2020, and is in production today for ElhubNational hub for metering data and market processes in the Norwegian electricity market. metering data. Towards ElhubNational hub for metering data and market processes in the Norwegian electricity market. the platform covers all nine market rolesThe nine roles Elhub divides the market into. The role says what a party does in a message exchange, not who the party is, and approval is granted per role..
This is where the article's own point lands. The threshold is not the GLNA Global Location Number from GS1 - thirteen digits that uniquely identify a legal entity or a place. In the power market the GLN is a participant's identity. number and the return URL. It is what comes after, and that is precisely the layer SAMTYGDTvimenning platform for Elhub integration - handles all message types and processes to Elhub. is: messages are translated between internal formats and the BRSElhub’s process specifications. Each BRS describes one market process step by step - who sends what, when, and what happens when something fails. formats, so that what arrives from ElhubNational hub for metering data and market processes in the Norwegian electricity market. becomes something a business system can actually use. The integrations are written by people who have done this job from the other side of the table, at energy companies.
Self-service consentThe end user's expressed permission for someone else to see or process information about them. In the power market it is the consent that gives a third party access to metering data. is in production. The end user signs in with BankIDAn electronic ID issued through the banks, used both for signing in and for signatures with legal effect. at ElhubNational hub for metering data and market processes in the Norwegian electricity market. and chooses scope, metering points and duration. Warning ahead of expiry belongs to the same job, precisely because the hub does not do it, but that part is still ahead of us.
The rest of the article is not a description of our solution. It is a description of how consentThe end user's expressed permission for someone else to see or process information about them. In the power market it is the consent that gives a third party access to metering data. works in the Norwegian market, and it holds regardless of who builds on it.