Access is not the problem
A company that wants metering values from ElhubNational hub for metering data and market processes in the Norwegian electricity market., but is neither the grid company nor the supplier for the metering points, has a way in. The role code is AG, third party, and it rests on 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. from the end user: specific metering points, specific data types, a specific period. 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 withdrawn, and access then ends.
That mechanism is in place and works. Even so, it is not unusual for a company in this situation to receive its data through an EDIElectronic Data Interchange - standardised electronic exchange of business documents between systems. platform, meaning through one more link, in 2026.
It is worth understanding why, because the reason is not the one you would expect.
Who this applies to
The typical party is a power producer. It wants two things back from ElhubNational hub for metering data and market processes in the Norwegian electricity market.: its own consumption, and its own production. Both exist there, and both are available with the right 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..
The same holds for industry and other sectors with a genuine need for metering values from their own installations, without holding any role in the power market as a result.
The common thread is not the industry. It is that none of them run a customer information system built with ElhubNational hub for metering data and market processes in the Norwegian electricity market. integration as part of the concept, because they were never the target audience for such a system.
The system has time series, but no hub connection
This is where the real work lies, and it is easy to underestimate.
The system meant to use the data usually has exactly what is needed to store it. It has time seriesMeasurements of the same quantity repeated over time. The order and the timestamp are part of the data, not decoration.. It can hold consumption and production per 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. over time and do something sensible with them. It is not missing a data model.
What it is missing is a way to receive. The system was built to read a file format that existed long before national hubs, and that is still the format it understands. Often MSCONSEDIFACT message format for exchange of metering data in the electricity market - used in Elhub to transmit hourly, daily and monthly values between market participants. or UTILTSThe six characters in UTILMD, INVOIC and CONTRL are not abbreviations someone invented locally. Each message type is its own standard in the UN EDIFACT directory, and the name is a six-character mnemonic..
So the gap is not access versus no access. It is XMLExtensible Markup Language - universal markup language for structured data, standard in Elhub's Ediel messages. versus EDIFACTElectronic Data Interchange For Administration, Commerce and Transport - UN standard for electronic data exchange..
The translator that stayed
This explains something that otherwise looks like inertia: why the EDIElectronic Data Interchange - standardised electronic exchange of business documents between systems. platforms did not disappear from the Norwegian market when ElhubNational hub for metering data and market processes in the Norwegian electricity market. went live in 2019.
When the hub entered service, very few of the dominant customer systems supported it. An EDIElectronic Data Interchange - standardised electronic exchange of business documents between systems. platform, by contrast, could pull from ElhubNational hub for metering data and market processes in the Norwegian electricity market.'s outgoing queue and deliver onwards as MSCONSEDIFACT message format for exchange of metering data in the electricity market - used in Elhub to transmit hourly, daily and monthly values between market participants. or UTILTSThe six characters in UTILMD, INVOIC and CONTRL are not abbreviations someone invented locally. Each message type is its own standard in the UN EDIFACT directory, and the name is a six-character mnemonic., in the format the receiving system already read. Nobody on the receiving side had to change anything.
As the system vendors built ElhubNational hub for metering data and market processes in the Norwegian electricity market. support themselves, the need fell away for those who got it. For everyone else it did not. The translator role is the same today as it was then: convert from the hub's format to the format the recipient understands.
That is a perfectly real job. It is just not the job EDIElectronic Data Interchange - standardised electronic exchange of business documents between systems. was originally built for.
Elhub is not the only counterparty
One more thing makes the picture less simple than "do you still need EDIElectronic Data Interchange - standardised electronic exchange of business documents between systems. towards ElhubNational hub for metering data and market processes in the Norwegian electricity market.".
For several parties the same messaging layer also runs elsewhere. Bids to the power exchange can be sent and received through it. Basis data to eSettThe company performing imbalance settlement for balance responsible parties across the Nordics, jointly owned by the four transmission system operators., which performs imbalance settlementProcess where the difference between planned and actual power exchange is reconciled - essential for the power market to function. for Norway, Sweden and Finland, can be sent in the format eSettThe company performing imbalance settlement for balance responsible parties across the Nordics, jointly owned by the four transmission system operators. accepts.
That means the question "does an ElhubNational hub for metering data and market processes in the Norwegian electricity market. integration cover my whole need" has a different answer from company to company. For some, ElhubNational hub for metering data and market processes in the Norwegian electricity market. is the entire picture. For others, ElhubNational hub for metering data and market processes in the Norwegian electricity market. is one of three counterparties, and then the messaging layer does not disappear by solving one of them.
What decides whether the need goes away
Two questions decide it, and neither is about ElhubNational hub for metering data and market processes in the Norwegian electricity market..
Has your system gained ElhubNational hub for metering data and market processes in the Norwegian electricity market. support, or is it going to? If your vendor has built it, the translator is redundant for that part. If not, someone has to keep translating, whoever that someone is.
How many counterparties do you have? One hub is one integration. A hub plus an exchange plus an imbalance settlementProcess where the difference between planned and actual power exchange is reconciled - essential for the power market to function. operator is three, and they do not necessarily share a format.
The answers differ from company to company, and that is the whole point. There is no single answer to whether the EDIElectronic Data Interchange - standardised electronic exchange of business documents between systems. layer is still needed in Norway, because the question was never about the country, but about the system landscape inside each individual building.