Test & Migration
Elhub has established a separate sub-project that will manage and assist Market Parties with data migration and system adaption and test towards Elhub. We encourage all Market Parties to create their own projects to implement their preparations for the introduction of Elhub.
Important activities for Market Parties
The figure below illustrates the main activities for Market Parties in the Test and Migration part of Elhub. Each milestone has its own requirements for the passage.
When Elhub is live in the market, all data that currently rests with Grid Owners and Balance Suppliers must be collected and transferred to Elhub. We call this data migration. Below are key activities related to the migration process.
h4 Continuously data cleansing and data maintenance
Continuously continuation of data cleansing. Obtaining personal identity number from Folkeregisteret*. Correcting inconsistencies between Grid Owners and Balance Suppliers.
Data extraction to DAM
Extraction of data to migration file format and upload of the migration files to DAM in specified dates. Correcting previously submitted data.
System adaption and test
The introduction of Elhub causes Market Parties to adapt their systems for new market processes and technical changes. Below are key activities related to the adaptation and testing of the systems.
Market Parties’ system vendors’ adaptation of the system according to the current market processes and message formats for Elhub.
System certification in the Ediel portal
Certification of an IT system in the Ediel portal for all current roles a Market Party will have. Note that in cases where multiple systems are involved in the message exchange with Elhub, for example where core systems communicate with Elhub via an integration party or a central system, the system certification will include both the core system and the central system / integration party.
System approval in Elhub
Full functional end-to-end test of a Market party’s IT system towards Elhubs test environment. Note that in cases where multiple systems are involved in the message exchange with Elhub, for example where core systems communicate with Elhub via an integration party or a central system, the system approval will include both the core system and the central system / integration party.
Market party test
Market Party certification in the Ediel portal
Certification in the Ediel portal of each Market Party for the roles the Market Party will hold.
Market Party approval in Elhub
End-to-end test of the Market Party’s ability to exchange messages with the Elhub test enviroment in correct format i accordance to the relevant role.
Go Live test
Rehersal of Go Live Process with all Market Parties.
Go Live process
Implementation of Elhub Go Live process.