PROJECT Elmarknadshubb DATE DRAFT VERSION /1263. Elmarknadshubb. Functionality description, overview

Transcription

1 ROJECT Elmarknadshubb DATE ENGLISH ÄRENDENUMMER /1263 Elmarknadshubb Functionality description, overview

2 Updates Release Change note Date English draft version 1.0 First English version ENGLISH 1.0

3 1 About this document > The process documents for the data hub are written in Swedish. A selection of the Swedish documents will be translated into English. In the event of discrepancies between Swedish and English, the Swedish documents take precedence. > There is ongoing work to identify and specify the functionality in the data hub. The project Elmarknadshubb at Svenska kraftnät is in this work assisted by an expert group with participants from market actors. The functionality from a business perspective has been described, in current draft state, in a number of documents written in Swedish. This document includes an overview translated to English, see list and a short description about each document in Table 1. > Currently there is also ongoing work in defining the data hub's functionality from a business perspective in a number of areas, see Table 2 below. These areas are not determined to the same extent as the functionality in Table 1. To the most part the functionality in these areas are not yet included in the Information model or the documentation. ENGLISH 1.0

4 2 General comments Depending on how law and regulations will finally be specified, the data hub's functionality and information model may be affected. Explanation of the terminology in this document: > DSO - Distribution System Operator (actor) > RE - Retailer (actor) > BR - Balance Responsible arty (actor) > ESCO - Energy Service Company (actor), may also be called third party or service supplier > MGA - Metering Grid Area > List of actors ER, DSO, ESCO means that all listed actors are included in the interaction with the data hub > List of actor ER/DSO/ESCO means that one of the listed actors is included in the interaction with the data hub > esett is a company providing imbalance settlement services to electricity market participants in Finland, Norway and Sweden. > Business Requirement Specification, describes the information exchange between the data hub and one or more actors for a specific business process > Function, a description of internal function in the data hub that does not include interaction witch external actors (e.g. calculations for metering grid area settlement) ENGLISH 1.0

5 Functionality description, Table 1 Business documents Area Document Name Description Initiating actor Interaction with actors Register and dismantle metering point -SE-111 Register customer metering point This describes how a DSO registers a customer metering point, with one or two associated accounting points, with connection to a MGA in the data hub. (When the is completed, the customer can sign a contract for the registered accounting points.) DSO DSO Yes No ossible with later -SE-112 Dismantle customer metering point This describes how a DSO dismantles a customer metering point and its associated accounting points in the data hub. DSO DSO Yes No -SE-113 Register exchange metering point This describes how a DSO registers an exchange metering point with DSO Adjacent DSO Yes No connection to two MGA's in the data hub. The DSO for the adjacent metering grid area is informed about the registration. -SE-114 Dismantle exchange metering point This describes how a DSO dismantles an exchange metering point in the data hub. The DSO for the adjacent metering grid area is informed about the dismantling. DSO Adjacent DSO Yes No -SE-115 Register submetering point This describes how a submetering point is registered in the data hub. DSO DSO Yes Yes Start and end of supply -SE-116 Update submetering point This describes how an information attribute regarding a submetering point is updated in the data hub. -SE-225 Reverse action on a metering point -SE-211 Start of delivery due to customer moving in -SE-212 End of delivery, initiated by another process DSO DSO Yes Yes This describes how a DSO can reverse a previous made update on a metering DSO DSO, RE, ESCO Yes No point. The result will be that the metering point will have the same state as before the update. This describes how a RE connects a new customer to an accounting point in the data hub. This describes how an automatic end of delivery for a customer is executed in the data hub as a consequence of another process (e.g. -SE-112 Discontinue customer metering point ). RE RE, DSO, ESCO Yes No Data hub RE, DSO Yes No -SE-213 End of delivery due to customer moving out -SE-214 Start of delivery due to obligation to receive This describes how the RE registers end of supply for a customer due to moving out. This describes how the data hub connects a registered accounting point production to an existing customer and RE for the associated accounting point consumption. RE RE, DSO, ESCO Yes No Data hub RE, DSO, ESCO Yes No -SE-215 End of delivery due to customer termination of contract This describes how the RE registers end of delivery for a customer due to customer termination of contract. RE RE, DSO, ESCO Yes No -SE-216 End of delivery due to obligation to receive This describes how the data hub executes end of delivery for an accounting point production that is subject to obligation to receive. (e.g. due to -SE-213 End of delivery due to customer moving out ) Data hub RE, DSO, ESCO Yes No -SE-221 Cancel start and end of delivery, initiated by another process This describes how a future start or end of delivery for an accounting point is cancelled by the data hub as a consequence of another process. (e.g. due to -SE-213 End of delivery due to customer moving out ) Data hub RE, DSO, ESCO, previous RE Yes No -SE-222 Cancel start and end of delivery -SE-223 Reverse start of delivery due to moving in This describes how a future start or end of delivery for an accounting point is cancelled by the RE. This describes how a RE reverses a previous registration of start of delivery due to moving in. Function Create customer hub ID This function describes how the data hub creates a customer hub ID when a new customer is registered via -SE-211 Start of delivery due to moving in. RE RE, DSO, ESCO, previous RE, new RE Yes No RE RE, previous RE and DSO Yes No -SE-411 Start of delivery due to retailer switching -SE-412 Terminate ongoing contract followed by switch to designated RE This describes how a RE registers a switch of supplier on an accounting point in the data hub. This describes how a RE terminates a customers ongoing contract in the data hub. The data hub will then execute a switch to the designated RE. RE RE, previous RE, DSO Yes No RE RE, DSO, ESCO Yes No (The designated ES has been pre-registered by the DSO.)

6 Functionality description, Table 1 Business documents Area Document Name Description Initiating actor Interaction with actors -SE-413 Switch to designated RE initiated by bankruptcy or the loss of balance responsible party This describes how the data hub executes a switch to the designated RE due to current RE goes bankrupt or loses their BR. Data hub RE, designated RE, DSO Yes No ossible with later Master data -SE-511 Request master data This describes how an actor can request all types of master data on All actors All actors Yes No individual data objects (information about customer, metering points, accounting points and contracts). -SE-512 Update customer information This describes how a RE registers updated customer information in the data hub. -SE-513 Register customer metering point information -SE-514 Update energy delivery contract information -SE-517 Register exchange metering point information -SE-518 Distribute metering point information This describes how a DSO registers updated information for a customer metering point in the data hub. This describes how a RE updates energy delivery contract information in the data hub. This describes how a DSO registers updated information for an exchange metering point in the data hub. This describes how the data hub distributes updated metering point information to actors update has been registered in the data hub via -SE-513 Update customer metering point information or -SE-517 Update exchange metering point information. RE RE Yes No DSO DSO and associated actors Yes No RE RE Yes No DSO DSO and adjacent DSO Yes No Data hub RE, ESCO Yes No -SE-201 Request accounting point ID This describes how a RE can receive information about an accounting point ID by entering the accounting point address. When the RE has received the accounting point ID the RE can initiate -SE-202 Request master data before moving in. New RE New RE Yes No (This is meant to be used before the customer and the RE has signed a contract.) -SE-202 Request master data before moving in This describes how a RE can request master data for an accounting point and its associated metering point with the purpose to create an offer to the customer. New RE New RE Yes No (This is meant to be used before the customer and the RE has signed a contract.) -SE-401 Information before retailer switching This describes how a RE can request information about the customers accounting points in the data hub, the RE needs to include an customer consent (e-id) in the request. The RE can then choose one of the accounting points and receive more information about that accounting point and associated metering point with the purpose to create an offer to the customer. New RE New RE Yes No (This is meant to be used before the customer and the RE has signed a contract.) Customer consent -SE-402 Blocking of a retailer This describes how an RE, based on a request (via e-id) from the customer, can register a blocking of another RE from conducting retailer switching on the customers accounting points. (The purpose is to protect customers from dishonest ES s.) -SE-403 Request customer consent overview This describes how an RE, based on a request (via e-id) from the customer, can request an overview of registered consent for the customers accounting points. (The purpose is to present an overview for the customer)

7 Functionality description, Table 1 Business documents Area Document Name Description Initiating actor Interaction with actors -SE-404 Request overview for energy service company This describes how an ESCO, based on a request (via e-id) from the customer, can request an overview of the customers accounting points and registered consents for the ESCO. (The purpose is to present an overview for the customer) ESCO ESCO Yes Evaluated ossible with later -SE-501 Register customer agent via e- ID This describes how a RE, based on a request (via e-id) from the customer, can register a customer agent in the data hub. (The purpose of a customer agent is to give that agent access to information in the data hub about the customers accounting points.) -SE-502 Register customer agent via form This describes how a RE, based on a request (via paper form) from the customer, can register a customer agent in the data hub. (If possible the customer is to use -SE-501 Register customer agent via e- ID, but if the customer neither does not have an e-id nor is a juridical person where the articles of association states multiple signatures, the agent can be registered via form instead.) -SE-503 Register corporate agent This describes how a RE registers a corporate agent for the customer of the type corporation in the data hub. (It s meant to be used when the customer has delegated authority to administrate their accounting points to named corporate agent). -SE-505 Update customer agent via e- ID This describes how a RE, based on a request (via e-id) from the customer, can update a customer agent in the data hub. (It s meant to be used to either update the extent of a consent or to completely withdraw it.) -SE-506 Update customer agent via form This describes how a RE, based on a request (via paper form) from the customer, can update a customer agent in the data hub. (It s meant to be used to either update the extent of a consent or to completely withdraw it.) (If possible the customer is to use -SE-505 Update customer agent via e-id, but if the customer neither does not have an e-id nor is a juridical person where the articles of association states multiple signatures, the agent can be registered via form instead.) -SE-507 Update corporate agent This describes how a RE updates a corporate agent in the data hub. (It s meant to be used when the customer has delegated authority to administrate their accounting points to named corporate agent and need to update the information) -SE-515 Register energy service contract This describes how an ESCO or a RE, based on a request (via e-id) from the customer, can give one or more ESCO's the right to obtain information about the customers accounting points in the data hub. RE/ESCO RE/ESCO Yes Yes

8 Functionality description, Table 1 Business documents Area Document Name Description Initiating actor Interaction with actors -SE-516 Update energy service contract This describes how an ESCO or a RE, based on a request (via e-id) from the customer, can update a previously registered energy service contract in the data hub. RE/ESCO RE/ESCO Yes Yes ossible with later Meter value management -SE-611 Register meter value This describes how a DSO registers meter values for a metering point in the data hub. -SE-612 Distribute meter value This describes how the data hub distributes meter values to actors after the meter value has been registered in the data hub. -SE-613 Register meter value for sub metering This describes how a DSO registers meter values for a submetering point in the data hub. DSO DSO Yes No Data hub RE, ESCO Yes No Actor Actor Another actor than the DSO can be an agent for the customer with the responsibility to collect and register meter values for submetering purposes. -SE-614 Request meter value This describes how an actor can request meter values for an individual metering point or a submetering point. Function eriod summing of meter values This function describes how the data hub sums time series for meter values for a given period. Function Aggregate meter values This function describes how the data hub aggregates meter values for two or more metering points (with same delivery period and time resolution). RE/ESCO/DSO/BR RE/ESCO/DSO/BR Yes No Function eriodise annual volume This function describes how the data hub periodises a given annual volume for a customer metering point (when registered via -SE-111 Register customer metering point). The result is an hourly based consumption prognosis (there might possibly be a higher resolution in the future) and it s used in the function reliminary hourly profiled. Metering grid area settlement -SE-711 Request settlement result This describes how an actor requests settlement results from the data hub, (this can also include the data the calculations are based upon). RE/ESCO/DSO/BR /esett RE/ESCO/DSO/BR/eSett Yes No Incl quarterly settlement and management of parallel quarterly- and hourly settlement during an interim period Function Metering grid area reconciliation In the function Metering grid area reconciliation an aggregate is made based on meter values and the metering point structure in the data hub. Incl quarterly settlement and management of parallel quarterly- and hourly settlement during an interim period. Function reliminary hourly profiled In the function reliminary hourly profiled meter values for the same period last year are calculated into meter values with higher resolution based on the load profile. This is performed to enable metering grid area settlement according to desired resolution. Incl quarterly settlement and management of parallel quarterly- and hourly settlement during an interim period. Function Retailer settlement In the function Retailer settlement meter values are aggregated per retailer and MGA in order to fulfill the reporting to esett and the function Correction settlement. Incl quarterly settlement and management of parallel quarterly- and hourly settlement during an interim period.

9 Functionality description, Table 1 Business documents Area Document Name Description Initiating actor Interaction with actors Function Final hourly profiled In the function Final hourly profiled a collected meter value is calculated into higher resolution based on the reduced load profile. Incl quarterly settlement and management of parallel quarterly- and hourly settlement during an interim period. ossible with later Function Correction settlement In the function Correction settlement a basis for correction is calculated between RE's Incl quarterly settlement and management of parallel quarterly- and hourly settlement during an interim period. Structure to esett -SE-712 Inform esett about new or terminated MGA -SE-713 Inform esett about updated grid exchanges This describes how the data hub updates esett with new or terminated MGA's. This describes how the data hub updates esett with new or deleted grid exchanges. Data hub esett Yes No Data hub esett Yes No -SE-714 Register BR structure This describes the registration in the data hub regarding structure for the BR, for both consumption and production in a MGA for a RE. BR Evaluated Evaluated Grid fee -SE-715 Inform esett about updated BR structure This describes how the data hub updates BR structure to esett (structure per RE/MGA/type) Data hub esett Evaluated Evaluated -SE-811 Register grid fees This describes how the DSO registers grid fees for their metering points in DSO DSO Yes Yes the data hub. -SE-812 Distribute grid fees This describes how the data hub distributes grid fees to RE after the grid Data hub RE Yes Yes fees have been registered in the data hub. -SE-813 Request grid fees This describes how a RE or a DSO requests grid fees from the data hub. RE/DSO RE/DSO Yes Yes -SE-814 Request aggregated grid fees This describes how a RE or a DSO requests aggregated grid fees from the data hub. Function Aggregate grid fees This function describes how the data hub aggregates grid fees per MGA and RE. The purpose is to create an invoicing basis from the DSO to the RE. RE/DSO RE/DSO Data hub None (Internal hub) Yes Yes Grid tariff -SE-815 Register grid tariff This describes how a DSO registers its grid tariffs in the data hub. DSO DSO Yes Yes (A grid tariff is a price list which states the cost for using the grid.) -SE-816 Update grid tariff This describes how a DSO can update its grid tariffs previously registered in the data hub via -SE-815 Register grid tariff. DSO DSO Yes Yes -SE-817 Request grid tariff This describes how an actor can request grid tariffs from the data hub. DSO/RE/ESCO DSO/RE/ESCO Yes Yes Actor information -SE-911 Update actor information This describes how an actor can update its own actor information in the data hub. DSO/RE/ESCO/BR DSO/RE/ESCO/BR Yes No (For example a new telephone number.) -SE-912 Request actor information This describes how an actor can request actor information about an actor. (Could be information about another actor or the actors own information) DSO/RE/ESCO/BR DSO/RE/ESCO/BR Yes No -SE-913 Register actor agent This describes how an actor registers an actor agent. The agent must be registered as an actor in the data hub. The agent is given the right to perform one or more 's for the actor in the data hub. DSO/RE/ESCO/BR DSO/RE/ESCO/BR Yes No -SE-914 Actor agent overview This describes how an actor can request information from the data hub in order to present an overview of its actor agents and their rights. DSO/RE/ESCO/BR DSO/RE/ESCO/BR Yes No Actor communication -SE-915 Update actor agent This describes how an actor can update a current agent's rights in the data hub. -SE-311 Ordering of disconnection or connection This describes how a RE requests a disconnection or a connection for an accounting point from the responsible DSO. DSO/RE/ESCO/BR DSO/RE/ESCO/BR Yes No RE RE, DSO Yes Yes

10 Functionality description, Table 1 Business documents Area Document Name Description Initiating actor Interaction with actors -SE-321 Abort ordering of disconnection or connection This describes how a RE can abort an ordered disconnection or a connection of an accounting point. -SE-312 Question and answer This describes the information exchange via the data hub when an actor asks a question to another actor. The answering actor can answer the question via the data hub. There can be an unlimited number of information exchanges between the two actors. RE RE, DSO Yes Yes DSO/RE/ESCO/BR DSO/RE/ESCO/BR Yes Yes ossible with later -SE-313 Broadcasting This describes the information exchange via the data hub when an actor wants to inform other actors about a specific event. DSO/RE/ESCO/BR DSO/RE/ESCO/BR Yes Yes -SE-314 Broadcasting for a specific metering point This describes the information exchange via the data hub when an actor DSO/RE/ESCO/BR DSO/RE/ESCO/BR Yes Yes wants to inform other actors connected to a metering point about a specific event.

11 Functionality description, Table 2 Business, ongoing work Table 2 Area Document Name Description Initiating actor Interaction with actors Data removal GDR Data removal Compliance to the new general data protection regulation Functionality for the data hub to remove data based on the time regulation for data storage. For example if the customer requests access to all its information in the data hub, or utilises the possibility to be forgotten. TBD All actors Yes No ossible with later Statistics and reports functionality Statistics and reports functionality redefined data that s delivered from the data hub to various recipients on Data hub schedule. Statistics can be extracts from the data hub database. It can also be approximations of certain predefined events such as a number of retailer switches and move-ins for a certain period. This can also regard power statistics for hourly metered metering points. Authorities (Statistics Sweden ((SCB)) and Swedish Energy Agency ) Yes Yes (some parts) Security Security Routine for managing metering points with classified information and customers with protected personal information may require user permission level for managing them. TBD All actors Evaluated No Supervision Swedish Energy Markets Inspectorate (Ei) Information to Swedish Energy Agency Information to the Swedish Tax Agency Supervision Ei Electricity certificates, guarantees of origin & quota obligation Functionality for the Swedish Energy Markets Inspectorate in order to carry out market supervision in the data hub. (This will probably be carried out via the statistics and report function mentioned above.) Functionality for the Swedish Energy Agency monitoring of electricity certificates, guarantees of origin & quota obligation TBD Swedish Energy Markets Inspectorate Yes No TBD Swedish Energy Agency Evaluated Yes Information to the Swedish Tax Agency Functionality to support the Tax Agency's mission TBD Swedish Tax Agency Evaluated Yes Connection to external data bases Connection to external data bases Implement connections to external data bases in order to keep information in the data hub updated over time. Example 1: Svenska kraftnät internal system for updates of MGA information Example 2: According to the current functionality the ES is responsible to keep information about its customers updated in the data hub. The Swedish Tax Agency's SAR-register has address information for all Swedish citizens. If a connection is implemented between the data hub and the SAR-register an updated customer address could automatically be updated in the data hub and then distributed to the ES. If this is introduced, it may have a major impact on the data hub, including the information model, s and responsibilities between the actors. TBD External data bases, e.g. Svenska kraftnät internal system, SAR-register (Swedish Tax Agency), Swedish companies registration office (Bolagsverket) and property address register (Lantmäteriet) Evaluated Yes Non-concessionary grid (IKN) Non-concessionary grid Functionality that supports the use of MGA of type IKN TBD All actors Evaluated Yes Regulation object Versioning Regulation object Handling of regulation object in the data hub vs. in esett TBD RE, BR, Svk Evaluated No Versioning Some information data types in the data hub will have version management. What information attribute this applies to will be analysed and then specified in the information model. TBD All actors Yes No User interface Function User interface, general For the data hub there will be a web interface where actors can log in, view and TBD All actors Yes Yes (some parts) update information. The user interface is broken down into sections with detailed explanations per section below.

12 Functionality description, Table 2 Business, ongoing work User interface Function User interface, Administration - Hub organisation The hub organisation administrative functions identified so far include: Registration and liquidation of actors Registration and liquidation of MGA's and regulation objects (alternatively via integration to internal system at Svenska kraftnät) Visualise result of metering grid area settlement Handle a DSO's notification to the data hub if a RE does not pay its grid invoice (including inform the RE) GDR management. Additional features may be added. TBD All actors Yes Yes (some parts) User interface Function User interface, Administration - Actors The actors administrative functions identified so far include: Registration and maintenance of own actor information (all actors) Registration and maintenance of MGA information (DSO) Notify the data hub if a RE does not pay its grid invoice (DSO) Visualise result of metering grid area settlement GDR management (all actors). Additional features may be added. TBD All actors Yes Yes (some parts) User interface Function User interface, Market processes - Actors s are normally intended to be performed through AI interfaces for actors. However, there may be a need for s to be performed through a user interface. The following needs have been identified so far: A is rarely used and therefore it is not cost effective to implement AI interface in actors own systems A is considered sensitive and a backup is required to ensure it can always be performed (if AI does not work) Support small actors who do not have the same resources as major actors to implement IT systems with AI support An ongoing investigation will look into which 's needs a user interface. TBD All actors Yes Yes (some parts) User interface Function User interface, Reports - Actor and Hub organisation An investigation is being conducted into the reporting needs for the user interface. robably some form of a BI tool will be needed to support both static and dynamic reports. TBD All actors Yes Yes (some parts)