Electricity retail market business processes in Datahub

Save this PDF as:
 WORD  PNG  TXT  JPG

Size: px
Start display at page:

Download "Electricity retail market business processes in Datahub"

Transcription

1 Electricity retail market business processes in

2 TABLE OF CONTENTS Table of Contents... 2 Figures... 6 Tables... 8 Definitions and abbreviations Introduction General Development in retail market exchange Business operations in the environment Suppliers Distribution system operators Customers Third parties operator Data protection Process map The content of this document How to read UML descriptions Common notation Class diagrams Sequence diagrams 's data model and parties' rights to data Description of conceptual model Parties' rights to data Data storage period Description of market processes Management of customer and metering point data Maintenance of metering point data (233)

3 3.1.2 Maintenance of customer Retrieval of customer and metering point data Contract processes Contract Reporting new agreements Reporting changes to agreements Reporting the ending of an agreement Cancelling an agreement and correcting errors Other types of agreement Processing metering data Metering data Reporting metering data Processing reading metering and unmetered sites Correction of metering data Processing reactive energy data Processing connection point and production unit metering Disconnection and connection processes General description Process descriptions Distribution system operator's imbalance settlement Rules Calculations Data reported to esett Supplier's imbalance settlement data Distribution system operator's imbalance settlement data Management of balance errors Maintenance and retrieval of product and invoice row Product Invoice row Authorisations Authorisations granted by the customer Authorisations granted by the parties Forwarding party Customer access to own (233)

4 3.11 System availability Users associated with system administration System support service model Scheduled service interruptions Description of events General Validation Event cancellation and error correction Process map explanations DH100 Customer and metering point data maintenance processes DH110 Customer maintenance DH120 Metering point data maintenance DH130 Customer and metering point data request DH200 Metering data maintenance processes DH211 Metering data report DH212 Reminder of metering data report DH220 Metering data request DH300 Contract processes DH310 New contract DH320 Contract update DH330 Contract termination DH340 Contract cancellation DH400 Connection and disconnection processes DH410 Connection DH420 Disconnection DH500 Imbalance settlement DH510 Calculation and notification of imbalance settlement data DH520 Imbalance settlement data request DH 600 Balance deviation correction DH611 Balance Deviation Report to Supplier DH612 Balance deviation data report to DSO DH700 Product and invoicing maintenance processes DH710 Product update (233)

5 4.8.2 DH720 Product request DH730 Notification of invoice row DH740 Invoice row request DH800 Authorisations DH810 Notification of customer authorisation DH900 Party DH910 Notification of party DH920 Party request Source list (233)

6 FIGURES Figure 1 Process map Figure 2 Example of a class diagram Figure 3 Example diagram of alternative flow in a sequence diagram Figure 4 Example diagram of optional flow in a sequence diagram Figure 5 Example of parallel flow in a sequence diagram Figure 6 Example of a loop in a sequence diagram Figure 7 Conceptual model Figure 8 Class diagram for accounting point data Figure 9 Accounting point status diagram Figure 10 Process description for an accounting point data update Figure 11 Customer class diagram Figure 12 Process diagram for a customer update Figure 13 Class diagram for sales agreement Figure 14 Class diagram for grid agreement Figure 15 Process diagram for reporting a new agreement Figure 16 Process diagram for terminating a sales agreement Figure 17 Process diagram for terminating a grid agreement Figure 18 New supplier reports customer moving out Figure 19 Sales agreement cancelled by the customer before the agreement begins (1) and after it has begun (2) Figure 20 The situation after a reported cancellation by the customer when there is no preceding supplier Figure 21 Cancellation by supplier before agreement starts. The situation after cancellation has been reported (4) and the situation after the possible refusal of the preceding supplier to restore a contract (5) Figure 22 Supplier cancellation after a contract has begun. The situation after cancellation (6) and the situation after the possible refusal of the preceding supplier to restore a contract (7) Figure 23 Cancellation by the supplier when there is no preceding supplier Figure 24 Class diagram for metering data Figure 25 Time limits for reporting metering data. The red text shows the metering responsible party's time limits for submission to and the green text shows 's time limits for submission to esett (233)

7 Figure 26 Disconnection process initiated at the supplier's request Figure 27 Connection process initiated at the supplier's request Figure 28 Disconnection process initiated at the DSO's request Figure 29 Connection process initiated at the DSO's request Figure 30 Data used in imbalance settlement calculation Figure 31 Imbalance settlement calculation for the metering grid area Figure 32 Supplier's MGAspecific imbalance settlement data Figure 33 DSO's MGAspecific imbalance settlement data Figure 34 Process diagram for correcting balance errors Figure 35 Product data category diagram Figure 36 Invoice row category diagram Figure 37 Authorisations reported to Figure 38 Party stored in Figure 39 Customer access to its own Figure 40 A description of performing a event Figure 41 Process map explanations Figure 42 Customer and accounting point data maintenance processes Figure 43 Metering data maintenance processes Figure 44 Agreement processes Figure 45 Connection and disconnection processes Figure 46 Imbalance settlement processes Figure 47 Correction processes for balance errors Figure 48 Product and invoicing maintenance processes Figure 49 Authorisation processes Figure 50 Maintenance processes for party (233)

8 TABLES Table 1 UML relationship types used in this document Table 2 Descriptions of entities in 's data model Table 3 Parties' rights to data in Table 4 Accounting point statuses and their meanings Table 5 Distribution of by customer and contract Table 6 Differences in agreement reporting in and in current state Table 7 's decisionmaking concerning the reasons for reported new agreements Table 8 Various situations when reporting new agreements Table 9 Reasons for ending a contract Table 10 Metering data validation Table 11 Metering statuses used in Table Metering grid areaspecific total calculations calculated by Table 13 Imbalance settlement data communicated to esett on a supplier and metering grid areaspecific basis Table 14 NBS exchange documents used by Table 15 Data reported to esett Table 16 Purposes of authorisations Table 17 Authorisation needs between parties Table 18 Example table for an event description and its progress with explanations Table 19 Description of a customer update by the supplier Table 20 Description of a customer update by the DSO Table 21 Description of accounting point creation Table 22 Description of an update of accounting point data by the DSO Table 23 Description of the deletion of an erroneous accounting point Table 24 Description of accounting point data retrieval by a DSO Table 25 Description of accounting point data request by a 3rd party Table 26 Description of metering data report Table 27 Description of a reminder about a metering data report Table 28 Description of metering data retrieval Table 29 Description of notification of a new contract to the accounting point (233)

9 Table 30 Description of grid agreement confirmation Table 31 Description of updating sales agreement Table 32 Description of updating grid agreement Table 33 Description of the notification of an accounting point without a supplier Table 34 Description of notification of the ending of a sales agreement Table 35 Description of notification by the new supplier about the moving out of a customer Table 36 Description of notification of the ending of a grid agreement Table 37 Description of the notification of the cancellation of a sales agreement Table 38 Description of notification of a cancellation of a grid agreement Table 39 Description of refusal to restore a sales agreement Table 40 Description of the ending of a grid agreement in a cancellation situation Table 41 Description of a supplier's supply connection request Table 42 Description of a DSO's notification of supply connection Table 43 Description of notification of connection delay Table 44 Description of a supplier's supply disconnection request Table 45 Description of a DSO's notification of supply disconnection Table 46 Description of notification of connection or disconnection delay Table 47 Description of imbalance settlement data report to DSO Table 48 Description of notification of imbalance settlement data to the supplier Table 49 Description of imbalance settlement data request by a supplier Table 50 Description of imbalance settlement data retrieval by a DSO Table 51 Description of retrieval of consumption and production registered as losses Table 52 Description of report of balance deviation data to the supplier Table 53 Description of report of balance deviation data to DSO Table 54 Description of product data update Table 55 Description of product data request Table 56 Description of notification of invoice row Table 57 Description of invoice line request Table 58 Description of notification of customer authorisation Table 59 Description of notification of party Table 60 Description of party request (233)

10 DEFINITIONS AND ABBREVIATIONS Accounting point. A data set related to a physical location, for example, a dwelling, which connects a customer to a DSO and electricity supplier through a grid and sales agreement, and in which the consumption or production of electricity can be measured. (Distribution system operator's) imbalance settlement. An imbalance settlement concerning a DSO and its metering grid areas, as specified in the Electricity Market Act and Metering Decree. (Electricity) balance. Hourly (or based on another time step used in imbalance settlement) data specified in an imbalance settlement about the difference in an operator s electricity production and acquisition and in its consumption and supply. (Electricity) grid agreement. A contract between the DSO and customer regarding the grid service the customer requires. (Electricity) product. A sales or grid service product. (Electricity) purchase agreement. A contract by which the customer sells and the supplier buys the customer s smallscale production of electrical energy. (Electricity) sales agreement. A contract by which the customer buys and the supplier sells electrical energy. Electricity retail sales are regarded as the sale of electricity through the distribution grid directly to users of electricity or indirectly to users through the internal grid of a property or a corresponding group of properties. (Electricity) supplier. Any person, organisation or company that sells electricity or buys it (in this context, smallscale customer production). (Electricity) supply agreement. An electricity supply agreement is a contract between a seller and a customer, in which the seller also assumes responsibility for the grid service. If necessary, the seller agrees with the DSO on the grid service. (Electricity) supply. Refers to the delivery of electricity to be used or resold. (Market) process. A business process between operators described in this document, which concerns the exchange of between the parties. The processes include contract processes, such as moving or switching suppliers, the delivery of metering data and imbalance settlements. (Metering data) time stamp. The timerelated register marking of metering data, which indicates which period of time the data concerns. (Metering data) validation. Refers to verifying the quality of metering data collected from 10 (233)

11 remotely read metering instruments. It usually takes place in the metering data management or reading system. Typical validations include verifying that data is missing, verifying negative values, verifying an unusually high hourly output and verifying long series of zero values. (Metering grid area) balance deviation. The total amount of electricity (including losses) supplied to the metering grid area or transmitted from it. If the reported data is correct, the result of the calculation is zero (specified in the esett Handbook). A connection point is a point on the border between two electricity grids at which the transmission of electricity between these grids is specified. Authorisation. Permission given to a customer or operator to obtain data about itself from. The party concerned should have proof (for example, a power of attorney) about the authorisation given by the customer. Balance. Information about a metering point that tells which electricity supplier has valid balance responsibility for which time period. With regard to the correction of balance errors, balance data also includes hourly metering data for the abovementioned time period. Balancing calculation. A calculation currently in use concerning reading metering locations, in which the difference in energy entered in the electricity balance using the type loading curve method set in the Metering Decree and the difference in energy noted in measuring are established. Before starting to use the, the DSO is responsible for carrying out the calculation. The DSO invoices or refunds the supplier based on the calculation. Business process. A group of tasks linked to each other, which are done in order to achieve a set target, for example, the switching of a customer's supplier. CET. Central European Time. Connection point metering is a metering related to a connection point. Consumer. A customer, who is a natural person and acquires or produces electricity mainly for a purpose that is not connected to a business enterprise. Contract. Information about a metering point that tells which electricity supplier has a valid sales agreement for which time period. Contract process. A market process related to the conclusion and notification of a sales agreement, the maintenance of contract, and the termination or cancellation of a contract. Corporate customer or company. A customer that is not a consumer. In general, a corporate customer is a customer that acquires or produces electricity as part of business operations. Corporate customer may also mean, however, some other juridical person, 11 (233)

12 such as an association or public body. Cost passthrough. A measure, in which a supplier or a distribution system operator invoices another party for its services, which the latter then invoices the customer for. Current supplier. An electricity supplier with which a customer has a valid electricity sales agreement at a metering point connected to a contract process when the process begins. Customer. A person or company with a contract for electricity sales, electricity supply and/or electricity purchasing with a supplier and/or a grid agreement with a DSO and which acquires or produces electricity mainly for its own use. is a centralised exchange solution for the electricity retail market. Dissolving a contract. The immediate unilateral dissolving of an contract as a result of breach of contract by one party or some other occurrence entitling the party to dissolve it. Distribution system operator (DSO). An organisation or company that manages the distribution grid and practises licensed electricity grid operation in the grid. ebix is short for the European forum for energy Business Data exchange. A European organisation, which develops exchange for the energy sector. Electricity Market Act. The most significant legislation regulating the electricity market (588/2013). esett. An organisation responsible for the Nordic Balance Settlement. esett maintains the handbook for the Nordic Balance Settlement. Finnish Energy (ET) is an organisation for the industrial and labour market policy of the energy and district heating sector. GLN (Global Location Number). A GS1 system code that specifies a party in. A GLN code is a 13character code, which comprises a GS1 company ID, freely selectable numbers (35 of them) and a control number. Grid service product. An electricity product used by the DSO in the grid service. GS1. An international organisation that distributes individual organisationspecific codes. Finland s country code is 64. The country code and companyspecific ID linked to it granted by GS1 Finland Oy s customer service is called the GS1 Company Prefix. With the company ID, it is possible to form other codes, such as GLN and GSRN codes. GSRN (Global Service Relation Number). A GS1 system code, which specifies a metering point in. A GSRN code comprises a GLN code, a serial number and a control number. Hourly data. Data connected to hourly metering, which includes a timestamp, metering 12 (233)

13 value and status data. Hourly metering. Refers to the hourly metering (by hourly time steps) of electrical energy and registering the measured data in the memory of metering equipment. Hourlymetered metering point. Metering point at which an installed energy meter registers and forwards hourly data. Imbalance settlement window. A period during which changes can be made to hourly data before the closing of the electricity balances. Imbalance settlement. Refers to studying the electricity transactions made during each imbalance settlement period. As a result of this study, the electricity balance of each electricity market party can be determined. Input area. A metering grid area, which is interpreted negatively as a direction of transmission of electricity in the reporting of connection point metering data (from output area to input area). Meter. A device or combination of devices, which registers the consumption or production of electricity. A meter might also include an integrated or separate control device, which can control electrical devices at a metering point or, for example, other indicators in an apartment block. Metering data. Data produced from a meter, on which imbalance settlement or customer invoicing is based. Metering decree. A government decree prescribed under the Electricity Market Act, concerning the clarification and metering of the supply of electricity (66/2009). Metering grid area. Logic data used in the Nordic Balance Settlement, which is used in the imbalance settlement of a DSO. The physical counterpart of a metering grid area is a distribution grid or highvoltage distribution grid connected to the Finnish electricity system or separate from it in accordance with the Electricity Market Act. Metering point. A point at which the consumption, production or transmission of electricity can be specified. This specification may take place by metering, based on assessment or based on calculation. A metering point may also be an accounting point, connection point or production unit. A metering point has two translations in Finnish terminology. For this reason the term accounting point is used to separate the entity defined in e.g. in contracts from the entities where energy products are measured or computed. Metering register. A logical or physical entity contained in a meter, which registers a certain measurement parameter, such as the output of active power, or the input of reactive power from the grid. The register may include hourly data or cumulative readings from reading measurements. Metering responsible party. A party, which is responsible for the collection of metering 13 (233)

14 data from a certain metering point and for reporting it to. For metering points, this party is always the distribution grid owner. Movein location. A metering point to which a customer is moving. Moveout location. A metering point from which a customer is moving. New supplier. An electricity supplier, which initiates a contract process for a certain metering point. A new supplier may also be the current supplier of the metering point. Open supplier. An operator that supplies its customers with all the electricity they need, or balances the customer s production and acquisition of electricity and the difference between its use and supply, by supplying the amount of electricity that is lacking or by receiving the surplus during each hour (in connection with this, contrary to the above customer may also mean operator ). Operator. An electricity supplier, DSO or metering responsible party. Output area. A metering grid area, which is interpreted positively as a direction of transmission of electricity in the reporting of connection point metering data (from input area to output area). Party. An operator or third party. Preceding supplier. A supplier of electricity whose sales agreement has ended at the metering point as a result of a new sales agreement reported by the new supplier. Processing of balance deviations. A process in which a monetary supplier and metering grid areaspecific correction is carried out after the closing of the balance settlement window, as a result of corrected metering errors and balance data. Production unit. A data set used in the Nordic Balance Settlement, which relates to production dealt with on the production balance side. Profile. An (hourly) time series based on metering data used in imbalance settlement or an annual usage estimate, which comprises those measuring points at which electrical consumption, production or transmission are not registered hourly (or through another time step used in imbalance settlement). Reading (or meter reading). A cumulative reading registered by metering equipment. Reading metering. Metering that registers cumulative readings without timestamp data. Sales product. An electricity product used by an electricity supplier in its own service. Smallscale production grid service agreement. A separately made contract between the DSO and customer concerning the supply of electricity to the distribution system 14 (233)

15 operator s grid. Smallscale production. An entity formed by a smallscale production unit or several production units, which is dealt with on the consumption balance side in the imbalance settlement. At present, on the consumption balance side, production units are dealt with that have a nominal capacity of up to 1 MVA. Status of metering data. Refers to the status registered for hourly data that illustrates to the recipient how reliable the collected data is. Metering data statuses used include "missing", "uncertain", "estimated", "OK" and "corrected OK". Terminating a contract. The termination of a contract by one of the parties in accordance with the terms and conditions specified in the contract. Third party. A party operating in the electricity retail market, which provides a service for operators and customers. Time stamp. Data concerning metering, which indicates the moment in time at which measured energy is registered. Time step. Data that indicates to what level of time accuracy a meter registers metering data. The current time step used in imbalance settlements is one hour. At the time of writing, studies are underway to move to 15 minute time steps in imbalance settlements. Transmission product. see Grid service product. 15 (233)

16 1 INTRODUCTION 1.1 General During 2014 Fingrid carried out a study concerning a future solution for the exchange of on the electricity retail market. The study recommended the establishment of in Finland. The Ministry of Employment and the Economy examined the study during the spring, and in a letter dated the ministry requested Fingrid to initiate the implementation of the centralised exchange solution described in the study. Detailed specification work relating to began with a description of current business processes relating to the exchange of on the retail market. At Fingrid's request, Finnish Energy appointed 12 specialists in retail market exchange and business processes to electricity suppliers' and distribution system operators' process work groups. The specification work described current processes and operating methods commensurably and as comprehensively as possible. The aim was to identify and confirm all of the most significant retail market business processes, their exceptions and alternative process costs. Another aim was also to identify processes that will be necessary in the future environment and which are not currently carried out using messaging. The completed specification work was important groundwork for process work. On a document draft was sent for comments from the industry. The document was commented on by 13 operators. Autumn's process work began with work groups examining comments received from the industry and making the necessary changes to the document. The final document "Current electricity retail market business processes" was published on In autumn, the process work groups continued work by specifying business processes for the environment. Process work was scheduled and distributed to electricity suppliers' and DSOs' work groups, depending on which party initiates the process or holds primary responsibility for it. For example, switching suppliers was primarily dealt with in the suppliers' work group while the delivery of metering data was dealt with in the grid companies' work group. With regard to the effective progression of process work, it was extremely important for us to receive industry comments for examination by the work groups as soon as possible, thereby making it possible to keep to the target schedule. The target schedule for process work and the commenting schedule for topics were published for the industry and we requested the industry to reserve time in their calendars to comment on the process drafts. Topics for commenting were published on Fingrid's website, sent to addresses provided as PRODAT and MSCONS contact details in the electricity market contact details table maintained by Fingrid, and also sent to persons who submitted their s to the mailing list. Approximately 20 operators actively commented each topic. For each topic, Fingrid drew up a summary of the comments and published it on its website. The entire Electricity retail market business processes in document was sent to the industry for comments on Fingrid organised process orientation events for the industry on in Vantaa, in Oulu and in Jyväskylä. 16 (233)

17 Comments on the overall document were sent to Fingrid by Process work groups met to examine the comments and made the necessary changes to the document between The final documentation was completed , after which the document was translated into English. The technical specialist group began work on The technical group specified technical descriptions in accordance with data models and business processes described by the process work groups. This work produced technical documentation outlining 's exchange and this documentation was also given to the industry for comments. The documentation was released to the industry for comments The commenting schedule for the document was the same as for the market processes. Close cooperation with the industry has been a fundamental prerequisite for the success of the specification work and for costeffective operations. Work group members have also formed an important link between the process work and the industry, bringing the industry's wide range of both perspectives and skills to the task at hand. The members of the electricity suppliers' process work group: Tarja Juntunen, Loiste Sähkönmyynti Oy Kirsi Kuusisto, Helen Oy Vesa Mäkilä, Satapirkan Sähkö Oy (Paikallisvoima ry) Riitta Vaissalo, Fortum Markets Oy Sari Wessman, Jyväskylän Energia Oy (also represents Lahti Energia, Kokkolan Energia, Oulun Energia Oy/Oulun Sähkönmyynti Oy, Kemin Energia Oy, Tornion Energia Oy) Kaisa Ylipeura, Energiapolar Oy The members of the distribution system operators' process work group: Kristian Finell, Herrfors Nät Verkko Oy Ab (Paikallisvoima ry) Jari Jaakola, PohjoisSuomen Energiatieto Oy Tiina Leppälahti, Helen Sähköverkko Oy Tomi Mäkelä, Elenia Oy Jari Rusanen, Loiste Sähköverkko Oy Elina Säiläkivi, Caruna Oy Fingrid's members in process work groups: Minna Arffman Marko Juslin Esa Pietarinen Marjut Puukangas Laura Koskikallio, Talent Base Oy (workshop facilitation) Members of the technical specialist group: 17 (233)

18 Jari Arve, Satapirkan Sähkö Oy Ari Hallikainen, Enoro Oy (workshop facilitation) Mikko Horsmanheimo, Caruna Oy Arttu A. Lahtinen, Fortum Markets Oy Joni Räsänen, Tieto Oyj Merja Toikko, Enfo Zender Oy Fingrid's members in the technical work group: Jari Hirvonen 1.2 Development in retail market exchange The most important improvements and changes will bring compared with existing exchange are set out below. Centralised synchronous exchange will result in a transition to centralised exchange from current exchange, which involves the exchange of from operator to operator based on telecommunications operators. In the future, all data will be reported to, where it will be processed and forwarded on to other operators entitled to the data. The most significant difference to the current practice is that all exchange will take place via a single point, enabling all of the improvements to the existing practice that are set out in this section. One of the most significant developments offered by is the transition from the existing asynchronous exchange, which is based primarily on batch processing runs, to synchronous exchange. In practice, this means that will respond immediately to an operator's notifications. For example, in the future a supplier will not have to wait for confirmation from a DSO after reporting a sales agreement; instead the about the agreement's approval or rejection will be returned to the supplier in realtime directly from. Together with carefully compiled processes, this feature will reduce the need for clarification between parties. Possible problems with new contracts can be handled immediately with the customer during the same customer contact. Consistent customers in grid and sales agreements Customers often differ from one another in current grid and sales agreements. A couple can take out a sales agreement together while a grid agreement is only in the husband's name. There is a strong view in the industry that these agreements should be consistent with regard to customers in order to avoid various problematic situations. In practice, the achievement of this target requires uniform contract practices. In the future, DSOs will receive notification of a sales agreement made for an accounting point and the customers linked to it. The DSO will draw up its own grid agreement for the accounting point with the customers involved in the sales agreement and confirm the grid agreement in. This operating method ensures that future grid and sales agreements will pertain to the same customers. 18 (233)

19 This method is in line with Finnish Energy's current valid procedural guidelines, meaning that the customer should always be directed to contact the supplier first. This method also requires that new contracts are always drawn up for customers of full legal capacity. DSOs cannot be required to act in a manner which conflicts with this principle. Corporate customers' business ID numbers and consumer customers' personal identification numbers must always be given in new contracts. Exceptions are only permitted in those cases wherein an individual does not hold a Finnish personal identification number. Transfer of distribution system operators' imbalance settlement to In the future, DSOs' losses and supplierspecific total deliveries, which are currently calculated and announced in imbalance settlement by the DSO, will be calculated in. also calculates supplierspecific corrections to balance errors and notifies the DSO of supplierspecific balance errors for supplier invoicing. Thanks to, there is no need for the DSO to carry out the aforementioned calculations in its own system, nor does it have to maintain data on accounting point suppliers for imbalance settlement calculations. will submit the necessary imbalance settlement data to esett and with regard to the retail market, operators will contact rather than the esett system in matters concerning imbalance settlement. Suppliers and DSOs can monitor their own imbalance settlement data, including total delivery data and balance error data via the interface. also reports accounting points without suppliers to DSOs so that the DSO can disconnect electricity to these accounting points. Increasing the effectiveness of supervision In current exchange, situations arise wherein operators do not always act in accordance with agreed rules. Supervisory tools will be created in to help supervise operators' actions. The aim of supervision is to collect material with which to indicate any possible misuse and breaches of agreed rules and thereby to intervene in such behaviour. Exchange of product and invoicing Current messaging is not used to exchange accounting point specific product and invoicing. allows for the maintenance and exchange of sales and transmission products. This means that operators can take into account a product selected for an accounting point by another party, such as a supplier or DSO, in its own product selection and therefore offer uniform products to customers with regard to both the transmission and sale of electricity. also allows for invoicing rows to be relayed. Operators can, if they wish, report invoicing rows to, where they can be retrieved by the accounting point's supplier, DSO, and any 3rd party authorised to access data for the given accounting point. This will facilitate the utilisation of various invoicing service providers in business operations and offer customers a single invoice containing the grid service and energy sales. Utilisation of service providers 19 (233)

20 will facilitate the utilisation of various service providers in operators' business operations. Standardised interfaces and a centralised exchange solution reduce exchange costs as service providers, or third parties, do not need to arrange data communications connections separately with each operator. Comprehensive and highquality data content In connection with the specification of processes, all data required by operators' business operations that should be exchanged between suppliers, DSOs and third parties was mapped. This signifies a broadening in the data content to be exchanged in comparison with current exchange. In the future, data concerning e.g. the remote connection possibilities for a given accounting point will be available in the accounting point data. The quality of the data will also be higher in than it is currently. Validation and supervision will be built into to prevent insufficient data and data which is not in the correct technical format from being stored and transmitted. The most significant improvements will apply to the maintenance of codes which uniquely identify customers (personal identification numbers and business ID numbers), to metering data and to address. The improvement in data quality should begin as soon as possible and the project will provide assistance, guidance and tools for this "data cleanup". Metering data based on hourly data Finland has made the transition to comprehensive hourly metering and the number of remaining traditional reading metering is continuously decreasing. 's functionalities are specified such that the special processing of reading metering is only taken into account where absolutely unavoidable. As a result of, exchange will not support the transmission of cumulative readings. DSOs must form accounting point specific hourly time series concerning reading metering and unmetered locations for imbalance settlement and data transfer. There will also be a move away from carrying out existing temperature adjustments, which are specified in the metering decree, to hourly profiles. The aforementioned operating method also rules out the need to carry out separate balancing calculations. Further specifications to reading metering profiles in in connection with meter reading will be taken into account in balance deviation processing. Support for statutory reporting Comprehensive data pertaining to accounting points, customers and contracts will be imported into. This data content can be utilised in the generation of operators' statutory reporting. Services for third parties facilitates business operations for various service providers. It will be possible for a third party authorised by a customer, supplier or DSO to obtain accounting pointspecific and customerspecific data, including metering data, from one and the same place. For this 20 (233)

21 reason 3rd parties must make an agreement with which obligates the party to comply with agreed rules. A more customeroriented service All of the aforementioned developments aim at a more efficient and more customeroriented service. 's contract processes reduce errors and problems and the customer experiences the result as better service. The aforementioned services for third parties will also increase the range of various customer services. The principle is that acts as a shared background system for the industry which allows companies in the field the opportunity to offer their customers better customer service, but nevertheless in such a way that the customer is not aware of 's existence. Development of business operations will also play a significant role in the development of various business operations. Public discussion increasingly highlights different visions for the future of the electricity retail market. Key themes in this discussion include consumers' demand response, electric car recharging, and various energy efficiency and management services. allows for and aids the development of various new services and their required exchange. 1.3 Business operations in the environment Suppliers Below is a rolebyrole account of how will change operators' daytoday business operations. Suppliers' primary tasks in are the initiation of contract processes and the maintenance of customer. Contract processes include reporting new contracts as customers move home and switch suppliers, changes to contracts during delivery and the ending of contracts. enables suppliers to provide increasingly customeroriented and customerfriendly service. For example, a supplier authorised by a customer can check valid accounting point, grid service product 1 and metering data before drawing up a contract. In this way, the supplier can tailor the sales agreement to the customer. Before reporting a contract, the supplier can check whether the customer has for the accounting point a valid fixedterm sales agreement or a sales agreement containing exceptional termination conditions which could prevent the creation of a new agreement. The supplier cannot, however, be authorised to obtain for an accounting point for which its customer does not yet have a contract. This refers to e.g. an accounting point to which the customer is moving. The supplier can also check the accounting point's connection status and notify the 1 including detailed on the allocation of time at a product componentlevel 21 (233)

22 customer of any possible connection fees in the event of a quick move. More realtime exchange will reduce various problems and related investigative work, which will improve the customer's service experience. Nowadays suppliers also face the challenge of deciding whether they are dealing with a change of supplier or a customer moving house. Reports sent using the wrong code always require manual processing. In the future, the supplier will not have to make such decisions as will always contain on the customer situation at the accounting point Distribution system operators Customers Distribution system operators' (DSO) primary tasks in include the maintenance of accounting point, grid agreement and grid agreement product data, as well as the maintenance of structural data required for imbalance settlement, such as connection points and production units. In addition to the aforementioned, a DSO must also report metering data to on a daily basis, whereupon the data will be transmitted to the entitled parties. Although the status of metering data and its use are also validated in, the DSO will continue to be responsible for the accuracy of metering data. As such, DSOs must continue to carry out their own metering data validation in the future. As a result of the change brought by, a DSO can, if desired, move away from carrying out its own imbalance settlement, balance error/balancing and loss calculations. Invoicing for balance errors will still be carried out by DSOs even though the calculations take place in. As a result of the implementation of, the significance of accounting pointspecific supplier data to the DSO will decrease but not disappear entirely. There will continue to be situations in the future wherein the DSO should directly contact the accounting point's supplier, though this should occur less than is currently the case. The DSO will continue to receive about completed new sales agreements and the accounting point's supplier for drawing up its own grid agreement and for, e.g. concerning the reading of reading metering sites. As a result of improved exchange, the need for clarification of various problematic situations with customers and suppliers will also decrease for DSOs. The transmission of metering data takes place via, meaning that the DSO does not need to agree separately on the transmission of data with all parties. This especially concerns metering data transmitted to third parties and the management of authorisation from their customers. 's online service, described below, will cover the DSO's current statutory obligation to report metering data to customers. From the customers' perspective, will primarily be a background system used by electricity retail market operators and its use will not be directly visible to the customer. The customer will experience the implementation of and renewed market processes as improved customer service and quicker processing times for contract events. allows for the customer to take on a more active role as an electricity consumer and producer. In particular the increased availability of to third parties will increase the number of different services offered to customers. allows for more 22 (233)

23 1.3.4 Third parties comprehensive services relating to a customer's own electricity use and the overall perspective offered to customers, even in situations wherein a customer's multiple accounting points are covered by different suppliers or are located in metering grid areas managed by different DSOs. The customer will have the opportunity to check its own stored in using a separate online service. This service will be implemented via existing operators' online services. The service will cover DSOs' current statutory obligation to report to its own customers. The customer can add and remove thirdparty authorisations for its own using the service, and can also check individual data retrievals carried out by the authorised parties in. The authorisation issued by the customer will be accounting pointspecific and timerestricted. In order to safeguard the customer's interests, openended authorisations will not be permitted and an authorisation will only be valid for a maximum of two years at once. As set out above, will facilitate third parties' business operations as a result of the increased availability of. will require third parties to sign a service agreement. The service agreement will specify the service for which the party may use the and the terms of use of the service. will not collect concrete evidence or powers of attorney concerning the customer's authorisations. The third party must separately report authorisation it receives via the interface, or the party can obtain authorisation based on a report submitted by the customer using the online service. It is the party's responsibility to present proof of authorisation and powers of attorney where necessary. In general, a third party can be any party registered with which holds an agreement with a operator. As such, a supplier or DSO that otherwise would not be entitled to access a customer's may act as a third party operator will result in the creation of a new operator on the electricity retail market. The primary task of the operator is to maintain the system and to provide technical support to operators' main users. Other tasks include the provision of general guidance to the industry, the supervision of compliance with the terms of 's service agreements and agreed rules, investigative work required by various operators concerning errors and problems, and the development of and exchange in close cooperation with the industry. 1.4 Data protection An essential part of managing customer and accounting point is the protection of belonging to individuals registered with. This refers to the protection of people's private lives. The design of and market processes was carried out on the premise that all that can be linked to a customer is personal. This is personal regardless of whether the can be linked to an individual person in. For example, the address of an accounting point is personal regardless of whether the name of the person or a person's 23 (233)

24 identification number is stored in. What makes the accounting point address personal is the fact that the customer's address is relatively easy to find out. This also applies to situations in which the customer does not live at the accounting point address. Market processes are designed in such a way that only necessary for market processes is stored in, and parties may only search for or receive relayed in accordance with their predefined permissions. These permissions depend on the party's role, agreement status and existing authorisations. 1.5 Process map The following picture shows an upperlevel process map of the processes specified during process work. A more detailed level process map is attached to this document. 24 (233)

25 Figure 1 Process map 25 (233)

26 1.6 The content of this document Chapter 2 depicts the requirements that market processes place on 's internal data model and provides descriptions of master data sets. It also outlines each party's rights to. Chapter 3 outlines the electricity retail market's business processes and operating models supported by. This description contains principles and rules as to how parties search for in and report to, and how data is relayed to other parties as part of market processes. The outline contains descriptions of entire processes from the parties' business perspective. Chapter 4 describes in further detail the individual interaction events between parties and that constitute entire processes. The description contains validation rules and descriptions of the that is relayed between parties and. 1.7 How to read UML descriptions This document uses activity diagrams to describe business processes. The flow of market processes is depicted using sequence diagrams and the data content of reports and other descriptions of data models are depicted using class diagrams. When interpreting this document, please remember that although UML notation is largely standardised, this does not mean that UML models are completely closed to interpretation. Large entities can always be modelled from various perspectives and UML is often used for a wide range of applications (e.g. software development vs. business processes) which require different kinds of interpretation. Some individual diagrams in particular may only present part of the background entity. There are always a number of alternative methods to present matters and there is always room for interpretation. This document does not aim at the highest level of orthodoxy from a UMLtechnical specification viewpoint, but instead aims to present matters in the most illustrative and understandable manner as possible. MagicDraw software (No Magic Inc.), which is the same as the software used in Nordic Energy Regulators' harmonisation project and in ebix, was used to create diagrams and models of the electricity retail market in this document. Below is a short introduction to interpreting UML diagrams. More about UML can be found online, especially in English. Wikipedia 1 and the website, to name just two examples, were used in the making of this document. More and a link to official UML documentation can also be found on the UML website run by Object Management Group, which manages UML development (233)

27 1.7.1 Common notation Text written inside <<>> marks is known as a stereotype, the purpose of which is to further define the type of object to be modelled (e.g. an entity or relationship). This document strives to use stereotypes in a manner that is as illustrative as possible in order for them to be selfexplanatory. Any type of line between two objects to be modelled denotes a relationship of some sort. The relationships used in this document are set out in the table below. 27 (233)

28 Table 1 UML relationship types used in this document Type of connection Definition Generalisation: The object to which the arrow is pointing is a generalisation of the source at the tail of the arrow. Association: a relationship between two objects that has an equivalent in reality. If there is an arrow at the end of a line, in this document it denotes the direction in which the relationship is read, (e.g. "includes"). Composite aggregation: the entity on the end without a diamond is an essential part of the entity with a diamond. For example, customer details are an inseparable part of a contract. Dependency: The source is somehow dependent on the object. In this document, this type of relationship is always used with a specifying text or stereotype Class diagrams Class diagrams consist of "entities", the relationships between the entities, and the data contained within the entities. An entity represents a certain physical or logical (data) entity. Examples of entities include accounting point and sales agreement. Examples of entities occurring in messaging are shown in the picture below. The names of the entities are written in bold at the top of the box describing the entity. The entity's attributes, or data fields, are listed below the line underneath the name. The square brackets following the attributes define the attribute's multiplicity, or as to how many values a data field can or will contain. For example, [0..1] means that the field is optional (or only compulsory in certain situations) and [1] means that the value is compulsory. If there can be an unspecified number of values, the * sign is used. The same kind of notation is also used to denote relationships between entities. For example, in the picture below there is not necessarily a sales agreement for an accounting point. This is marked by writing 0..1 at the sales agreement end of the relationship between these two entities. If no multiplicity value is given separately at the end of a connection, the multiplicity will by default be (233)

29 Figure 2 Example of a class diagram Sequence diagrams Sequence diagrams depict the progress of a process and, in particular, the exchange of between operators. The various roles of a process are marked along the horizontal axis while the vertical axis shows time. In this document, every exchange of between roles is numbered. In principle, messages occur chronologically according to the numbered order. Exceptions to this are possible using subsequences. The "alt", "par", "opt" and "loop" subsequences used in this document are explained below. In the diagrams, time limits inside {} parentheses are periods of 24 hours unless otherwise separately mentioned in the diagram; The notation {earliest..latest} is used inside the {} parentheses. N.B.! It is also possible that only one of the limits is specified. If the earliest or latest limit is not given, there is no corresponding binding time limit; Negative time limit numbers refer to time before delivery begins and before a change of contract or other change comes into effect, while positive numbers correspondingly refer to time after these events. 29 (233)

30 Alternative flows Figure 3 Example diagram of alternative flow in a sequence diagram In a sequence diagram, a process' alternative flow is depicted using an alt subsequence. The flow that will be realised is dependent on predetermined terms. In the above example, party 1 will send message 1 to party 2 when the term written inside the square brackets is met. Otherwise party 2 will send message 2 to party 1. It is worth noting that there can be more than one message on both sides of the dashed line. Optional flow Figure 4 Example diagram of optional flow in a sequence diagram 30 (233)

31 A process' optional flow is denoted using an opt subsequence. In the example above, party 1 always sends message 1 to party 2, but party 2 only sends message 2 if [term] is met. Parallel flow Figure 5 Example of parallel flow in a sequence diagram Par subsequences are used to depict flows completed in parallel. In the example, messages 1 and 2 can be sent in parallel or in any order. This does not, however, mean that either of the messages can be left unsent. Loop A loop subsequence is repeated for as long as a given term written inside square brackets is valid. An example of a loop is set out in the picture below. Figure 6 Example of a loop in a sequence diagram 31 (233)

32 2 DATAHUB'S DATA MODEL AND PARTIES' RIGHTS TO DATA 2.1 Description of conceptual model This section describes 's internal data model on a conceptual level, i.e. the structure onto which data supplied by parties to and data generated by is stored. The data model does not describe 's physical database, nor is it a complete description of the upcoming data model, but instead we aim here to outline the most important data sets with regard to market processes and their relationships. Master data set attributes are listed in data model figures attached to section 3 of this document. A more specified definition of each attribute can be found in a separately published Excel spreadsheet ("data standard"). When reading the figures, special attention should be paid to the fact that data marked as optional in the figure may be compulsory depending on other data. For example, fuse size at an accounting point is compulsory if the electrical power is not given. The content of data sent by parties to and vice versa in processes is depicted in section 3.9 of this document using eventspecific class diagrams. Figure 7 Conceptual model 1 1 An accounting point may only have one valid grid and sales agreement at once, but it may have several consecutive agreements over time. 32 (233)

33 Master data sets (entities) and the relationships between them are set out below. Not all master data sets in the table are in the abovementioned conceptual model, but they occur in more detailed data model diagrams in chapter 3. Table 2 Descriptions of entities in 's data model Entity Definition Synonyms Relationships Party A company or organisation that operates in one or more roles on the electricity retail market. The Party must have an agreement with. Electricity Market Party A Party can have one or more roles (supplier, DSO, 3rd party). Supplier A Party which acts as a supplier on the electricity retail markets. The Supplier has an electricity sales and/or purchase agreement with a Customer. The Supplier may be an open supplier or deliver a fixed amount of electricity ("fixed delivery"). Electricity Supplier Distribution System Operator A party which manages one or several distribution grids or high voltage distribution grids and practices licensed electricity grid operation in the grid. DSO Grid Company A DSO manages one or more Metering Grid Areas in the grids it controls and therefore manages all Accounting Points as well as other Metering Points in the Metering Grid Area. 3rd party A Party that is not a Supplier or DSO that has an agreement with and who acts in a certain role on the electricity retail market with the authorisation of a Supplier, DSO or Customer. Metering Grid Area An area defined in the grid managed by a DSO to which Accounting Points and other Metering Points are connected. MGA Grid (Area) A Metering Grid Area is always managed by one DSO, but over time the DSO for the Metering Grid Area may change due to e.g. mergers. Customer A natural person, company or organisation with a contract for electricity sales, electricity supply and/or electricity purchasing with a Supplier and/or a Grid Agreement with a DSO and which acquires or produces electricity mainly for its own use. Electricity User End User A Customer may have one or more Sales and/or Grid Agreements. Metering Point A general term for points on the grid where metering are carried out. Accounting Points are one kind of Metering Point, others are Connection Points and Production 33 (233)

34 Points, which are required Accounting Point A data set related to a physical location, for example, a dwelling, which connects a customer to a DSO and electricity supplier through a Grid and Sales Agreement, and in which the consumption or production of electricity can be measured. There can only be one valid Sales Agreement and one valid Grid Agreement for an Accounting Point at any given time. The Accounting Point belongs to only one Metering Grid Area and therefore is only managed by one DSO. The Accounting Point can be connected to another Accounting Point whereupon it is possible to tell if the physical address contains both consumption and production Accounting Points. Sales Agreement A contract by which the Customer buys and the Supplier sells electrical energy. Electricity retail sales are regarded as the sale of electricity through the distribution grid directly to users of electricity or indirectly to users through the internal grid of a property or a corresponding group of properties. In the data model and exchange, purchase agreements are processed as Sales Agreements which are linked to a production Accounting Point. A Sales Agreement can only be linked to a single Accounting Point. One or more Customers can be connected to a Sales Agreement. Grid Agreement A contract between the DSO and Customer regarding the grid service the Customer requires. In the data model and exchange, smallscale production Grid Agreements are processed as Grid Agreements connected to a production Accounting Point. Transmission Agreement A Grid Agreement can only be connected to a single Accounting Point. One or more Customers can be connected to a Grid Agreement. Address Addresses stored in relate either to an Accounting Point, Customer or Sales and Grid Agreements. The official address for an Accounting Point and Customer takes the format of a postal address. Contractspecific invoicing addresses can either be postal addresses or electronic addresses. An Accounting Point can have one or more addresses (corner buildings, language versions). Customers have a single, official address. Sales and Grid Agreements can each have one invoicing address, which also may be an electronic address. Contact Person Contractspecific contact person details which must be exchanged A Sales or Grid Agreement can have one or more Contact 34 (233)

35 between parties. Persons. 2.2 Parties' rights to data The following table contains a summary of the rights of parties to each of 's master data sets. More detailed roles and rights of 3rd parties will be specified during 's internal functional specification. Rights depend on the party's role, the accounting point's contract status and authorisations held by the party. Table 3 Parties' rights to data in Party Customer Accounting point data Contract Metering data Current supplier Rights during its own sales agreement Rights to data during its own sales agreement Data concerning its own sales agreement Rights to grid agreement during its own sales agreement Accounting point consumption, production and reactive power metering: rights during its own sales agreement Production unit metering data: rights if production unit supplier New supplier Has rights only when authorised by customer Rights to basic data(*) for the accounting point or, with customer authorisation, to all data if the accounting point is the customer's current one. Rights to contract status with customer authorisation (**) Accounting point consumption, production and reactive power metering: rights during its own sales agreement or with customer authorisation Old supplier Rights during its own sales agreement Rights to data during its own sales agreement Data concerning its own sales agreement Rights to grid agreement during its own sales agreement Accounting point consumption, production and reactive power metering: rights during its own sales agreement Production unit metering data: rights during its own agreement if supplier of the production unit. 35 (233)

36 DSO Rights during own grid agreement Rights to accounting point data for its own metering grid area Grid agreement Rights to supplier data in a sales agreement Rights to all metering point metering data in its own metering grid area. 3rd party authorised by customer During authorisation During authorisation and agreement period No rights During authorisation and agreement period 3rd party DSO's service provider 3rd party supplier's service provider According to role According to role According to role According to role According to role According to role According to role According to role * Basic accounting point data refers to the accounting point identification, accounting point address, accounting point status and concerning remote connectability. ** The right to contract status is set out in more detail in section Data storage period Data is stored in as necessary to meet the needs of parties' processes. However, data cannot be stored in indefinitely. The storage period for metering data in 's operative database is six years, and this time also steers the storage of data that has become obsolete with regard to other processes. When a customer's contract ends, the customer and contract are removed from 's operative database after the same sixyear period when the last metering data relating to the customer is deleted. Anonymised statistical data concerning metering data is nevertheless stored even after this period of time ends. 36 (233)

37 3 DESCRIPTION OF MARKET PROCESSES 3.1 Management of customer and accounting point data Customer and accounting point data is the most essential basic data exchanged between parties and stored in 's database. This section outlines the principles for maintaining and retrieving this data in Maintenance of accounting point data Accounting point data to be stored in is outlined in the diagram below. Figure 8 Class diagram for accounting point data Data for accounting points and more broadly for all metering points, is data owned by the DSO. As such, the maintenance of accounting point data in is the responsibility of the DSO. It is the responsibility of the DSO to create new accounting points, update data and report accounting points as removed from use. The life cycle of an accounting point and its possible statuses throughout its lifetime are set out in the diagram below. 37 (233)

38 Figure 9 Accounting point status diagram Accounting points should be created in as soon as they are established in the DSO's system. 's unique, GS1 systembased GSRN code should be reported for the accounting point. An accounting point can be created in while still in the construction phase, whereupon its status will be "under construction". This data is meant to inform the supplier that a contract can be made and reported to, but for the time being delivery to the site cannot begin. Delivery cannot begin, for example, if the accounting point is new and no meter has been installed yet. When the accounting point is "metered" that is, delivery can begin, the DSO activates the accounting point by updating its status to "connected" or "disconnected" depending on whether or not delivery is initiated. The DSO can temporarily make the accounting point passive by changing its status to "under construction". This takes place at e.g. renovated sites, when it is temporarily not possible for delivery to begin to an accounting point. A valid sales agreement is not automatically terminated when an accounting point's status is changed to "under construction"; instead, the supplier must come to an agreement with the customer on the matter as necessary. When it is possible to begin delivery to an accounting point as normal, its status in is "connected" or "disconnected". For accounting points with these statuses, contracts can be made and delivery can begin immediately ("connected") or as soon as the accounting point is connected ("disconnected"). The DSO sets the status of the accounting point as "removed from use" in when the accounting point is permanently taken out of use, such as when the DSO dismantles a connection. The DSO must ensure that termination of the accounting point's contracts has been reported to before reporting the removal of an accounting point. Once an 38 (233)

39 accounting point is reported as removed from use, it is no longer possible to make contracts for that accounting point. Accounting points that are erroneously created in must be removed from. If the error is noticed before other events are created for the accounting point, the creation of the accounting point can be cancelled using the general cancellation event, which restores the situation to how it was before the erroneous creation of the accounting point. If events have been made for the accounting point before the error is noticed, these events must first be cancelled, after which the accounting point should be set to "removed from use". This will mean that the accounting point identification in question cannot be used again. Contracts can be made for the accounting point as soon as its data appears in. If a new sales agreement is made for an accounting point while the point's status is still "under construction", but delivery cannot begin on the start date marked on the agreement, the start date in the sales agreement and the actual date of connection will differ from one another. If the supplier wishes to change the start date in accordance with the connection date announced by the DSO, the supplier must first cancel the previously reported agreement and then report a new agreement with the correct date. The table below sets out a summary of accounting point statuses during a accounting point's life cycle and their meanings. Table 4 Accounting point statuses and their meanings Status Agreements Delivery start Status at accounting point Under construction Can be made Cannot begin Unmetered Connection undergoing maintenance Connected Can be made Can begin Default electricity connected Disconnected Can be made Can begin Removed from use Default electricity not connected Cannot be made May not begin Connection cancelled In addition to the accounting point status, the DSO should also update other data for its accounting points in. The exception is the accounting point identification, which may never be updated. Data should be updated as soon as it changes in the DSO's own system. saves accounting point history data this means that the accounting point data's time of creation or modification is always saved in and these times are taken into account in data retrievals in accordance with parties' rights. The supplier also has the opportunity to report changes to accounting point data. Accounting point data reported to by the supplier is not automatically updated in however, and instead is forwarded to the DSO which then carries out the update. The DSO is to respond to an update request by sending to the accounting point data update, which includes either data reported by the supplier (the DSO approves the 39 (233)

40 data provided by the supplier), or accounting point data in the grid owner's own system (the DSO rejects the data proposed by the supplier). If the DSO does not respond to an update request within 2 working days, will send a daily reminder to the DSO until the grid owner responds to the request. The diagram below outlines the process description for an accounting point data update. Figure 10 Process description for an accounting point data update Consumption and production accounting points can be located in the same physical location, but they are processed in as separate accounting points. With regard to the functionality of contract processes, there is need to maintain a more secure manner of linking these accounting points together in addition to address. Linking takes place by reporting the identification code for the production/consumption accounting point with which the consumption/production accounting point is physically located in the same place when the consumption/production accounting point in question is created or updated. How a worksite, event or other temporary accounting point is processed within the DSO's internal processes has no bearing on 's functionality. DSOs employ various operating methods for processing temporary accounting points. If a DSO always establishes a new accounting point in its own system for a temporary accounting point, the new accounting point will be reported to in accordance with the normal creation process. If, on the other hand, the DSO uses a single accounting point identification and 40 (233)

41 only updates the accounting point address in accordance with where the temporary accounting point is located at a given time, corresponding changes in address must be reported to using the accounting point update event. In such cases the DSO must ensure that the accounting point is not reported to as removed from use for as long as it will be reused Maintenance of customer Customer to be stored in is outlined in the diagram below. Figure 11 Customer class diagram Customer maintenance in operates on the premise that a customer is only created once and then the customer's basic is distributed amongst all the operators with whom the customer has a contract. The customer's basic only encompasses the which, from a market perspective, needs to be updated in a centralised manner and other is maintained as part of contract on an operatorspecific basis. At a high level, the division is such that name, identification, contact and address are considered to be customer. Contractspecific, on the other hand, consists of invoicing and contact person. A customer extension code can also be given for a contract and can be a company or municipal department. 41 (233)

42 Table 5 Distribution of by customer and contract Customer Name Code Official address Contract Invoicing address Contact person Contact person's contact details (telephone number, address) Contact details (telephone number, address) There are two types of customer in : consumer and corporate customers. All legal persons (companies, organisations, public operators) are processed as corporate customers and all natural persons are processed as consumer customers. Customers are uniquely identified in using a code which, depending on the type of customer, is either a personal identification number, a business ID number (or VAT code for foreign companies) or an association ID. As such, contracts may only be reported to if the customer includes such a code. If a contract is made in the names of several customers, the of all customers and related codes will be reported, whereupon the contract will be linked to multiple customers in. If the matter concerns a foreign customer who does not yet possess a Finnish personal identification, the contract can under special circumstances be reported without an ID, but the customer's date of birth is nevertheless required. In addition, the party's own identification ("other" identification), which is formed of a supplier identification and supplier's customer identification, is also reported to. Based on this, the supplier can later identify the customer in. If a customer has a foreign personal identification or equivalent, it can be reported to using the customer's additional field. A party that reports such a contract is under obligation to update the customer's in as soon as a personal identification is available. Foreign customers are the only exception which allows for a contract to be reported to without a customer ID. The creation of customers without identification in will be monitored. Private traders are personally responsible for their contracts and so in these cases it must also be possible to enter a personal identification for a corporate customer. In these cases, 's data model allows for the same personal identification to be separately reported for both a corporate and a consumer customer, and for both a personal identification and business ID to be reported for a corporate customer if both IDs are used by a private trader. In these cases, the personal identification is given as the private trader's unique identifier and the business ID is provided in the customer's additional identification field. 42 (233)

43 Parties are responsible for the accuracy of the customer that they report to. does not carry out internal data validation, such as checking whether a customer's name and business ID correspond to one another. Later on in the project instructions will be created on e.g. how parties are to ensure that a corporate customer's name is saved in its official format as it is on the official register (YTJ). A customer is only created in as part of contract processes. If a customer in a contract notifications submitted by a party cannot be found in using an identification, it should be created in as a new Customer record. If the customer can be found in using an identification, the contract to be reported is attached to the existing Customer record. In addition, the customer's is updated to correspond to the customer provided. If a contract with several customers is reported, meaning that the party's contract notification contains several contract partners, several Customer records will be linked to the contract in. It is generally the supplier's responsibility to update customer data in. Customer can be updated by those suppliers who have a valid contract with the customer. Customer can be updated as part of contract processes or using a separate notification. In addition, the DSO can send a customer update request to which is then sent to the supplier which last held a contract with the customer. This supplier then updates the customer because it is assumed to have the most recent customer. The supplier can refuse to update the if it considers the update request to be unfounded or erroneous. The supplier is to respond to the update request by sending a customer update to containing either reported by the DSO (the supplier approves the reported by the DSO) or customer found in the supplier's own system (the supplier rejects the proposed by the DSO). If the supplier does not respond to the update request within 2 working days, will send a daily reminder to the supplier until it responds to the request. An identification (personal identification, business ID, association ID can be added to a customer in the update, but this identification may never be updated. Customer that has been changed is forwarded to all parties that hold contracts with the customer. In the event that sales and grid agreements are in different customers' names (the situation for contracts made before the implementation of and whose data was imported to via migration), the grid's customer can be directly updated if the customer has no sales agreement at all. The process diagram below outlines a customer update. 43 (233)

44 Figure 12 Process diagram for a customer update allows for the completion of private customers' processes. If a customer's contains a nondisclosure marking, is forwarded to the DSO as normal during agreement processes. Information about nondisclosure is also sent to the DSO for along with the customer linked to this notification. Authorisations are not permitted for customers marked as private, which prevents the customer's from being relayed in all processes to other parties. This also applies to situations in which operators authorise third parties to act on their behalf. 's migration work resulted in instructions as to how customers who do not currently have IDs in operators' systems can be uniquely identified during the migration phase. The unique identification of customers of new agreements made after the implementation of should be carried out as described above Retrieval of customer and accounting point data Parties' needs regarding the retrieval of customer and accounting point data primarily relate to agreement processes. As such, a search function will be constructed for which will always return accounting point data, data on customers linked to the accounting point via agreements and data concerning the accounting point's agreement status. The search will return the data in accordance with the rights set out in section 2.2. The search is outlined in more detail in agreement processes in section (233)

45 The supplier must provide the accounting point identification and customer identification when searching for customer and accounting point data. There is a separate search for finding an accounting point identification that makes it possible to retrieve the accounting point identification and its basic data using the accounting point's address. The supplier has the right to customer and accounting point data for the duration of the validity period of its own agreement. The supplier has the right to maintain data in from the time that the agreement is reported, throughout its validity period and also for another 6 weeks after the agreement has come to an end. A search carried out after the agreement's validity period has ended will, however, only return data from the agreement's validity period. The period of 6 weeks is determined based on the supplier's obligation to correct the customer's invoicing and the Electricity Market Act's requirements on sending final invoices in accordance with the existing operating method. Contrary to what is written above, a supplier is also able to retrieve customer and accounting point data without a valid agreement as long as the supplier is authorised to do so by the customer. Authorisation principles are set out in further detail in section 3.8. Distribution system operators have the rights to accounting point data in their own metering grid areas and therefore they also have the rights to customer linked to the accounting points via grid agreements. An accounting point data search carried out by a DSO will always return customer and agreement in addition to accounting point data. 3.2 Contract processes This section will outline the processes relating to accounting point sales and grid agreements. As a rule, whenever a supplier makes a new agreement in its own system, the agreement will be reported to. The DSO confirms its own agreement in when necessary, but whenever it does this, it will always be based on the supplier's notification. If the supplier or DSO make changes to the agreement stored in, the changes shall be reported to and will relay them on to the other party. When the agreement ends, each party terminates its own agreements and the completed agreement termination is sent via to the other party. It is not possible for an accounting point to have more than a single sales agreement and a single grid agreement valid at any one time, so whenever a new agreement is reported for an accounting point will automatically terminate the previous agreement and send the concerning the terminated agreement to the party whose agreement was terminated Contract Sales and grid agreement stored in include such as agreement dates, invoicing address and contact details for contact persons. When parties report agreements that they have made to, the customer submitted in the notification is stored in 's Customer entity (or in several if there is more than one customer in the agreement), and the agreement is linked to a customer (or customers) and the specified accounting point in 's internal data structure. 45 (233)

46 Invoicing channel is stored in agreement, and as such the appropriate invoicing address details (including invoicing (postal) address, invoicing address or einvoicing address) must be linked to the agreement. The invoicing address a customer provides when making a new agreement with a supplier is sent from the supplier to the DSO via. This data does not, however, bind the DSO to the use of the invoicing channel in question if the DSO is unable to provide said channel. The DSO reports the invoicing channel it uses in the agreement to as part of the grid agreement. A customer may also wish for the DSO to send invoices to a different address to the one stated on the sales invoice. In such cases, the customer should contact the DSO in order to change the invoicing address. The DSO will report changes to invoicing addresses to. 's data model allows for separate invoicing addresses to be used in sales and grid agreements at the same accounting point; that is, invoicing address data is stored on a contractspecific basis. It is worth noting that current rules prohibit consumer einvoicing data from being sent from one party to another. Nevertheless, it is possible to add a note in the invoicing channel field explaining that the customer wishes to use this particular invoicing channel. It is possible to add contact persons to agreements in addition to the actual customer. The customer is the agreement partner that is legally responsible for the agreement. Contact persons are persons linked to the agreement whose contact details are required by the parties in customer service situations. For example, the recipient of an invoice may be reported as the contact person for a contract if the recipient differs from the actual customer. Similarly, contact persons for agreements may vary between sales and grid agreements. The contact person provided to a supplier by a customer when making a new agreement with the supplier is stored in sales agreement and sent to the DSO. The DSO may use this as the contact person for its own agreement. It is worth noting that parties may have many different kinds of contact persons in their own customer and agreement, but the contact persons whose must be exchanged between parties are reported to. At least one contact person must always be reported for corporate customers. Separate contact persons are only reported for private customers when necessary, such as if the customer's contact details are insufficient. The sales and grid agreement stored in is set out below in separate diagrams. An accounting point can have several consecutive agreements over time, but only one sales and one grid agreement can be valid at any one time. Agreement sent in processes is set out in more detail in agreement events in section (233)

47 Figure 13 Class diagram for sales agreement 47 (233)

48 Figure 14 Class diagram for grid agreement Reporting new agreements Information concerning agreements made with a customer must be reported to. The supplier always initiates the report of a new agreement to. This does not, however, prevent the DSO from making a grid agreement with the customer before the customer has made a sales agreement with a supplier. If the DSO makes a grid agreement before the new sales agreement is reported to, the DSO must wait for the new sales agreement to be reported to and only then confirm the grid agreement in in accordance with the normal process. As provides an overview of the agreement and customer status for an accounting point, the supplier does not need to inform as to whether the matter concerns a customer's change in address, a change of supplier or the renewal of a contract with the current supplier. Based on the accounting point's customer and agreement, 48 (233)

49 will decide which of the above applies and then register the new agreement accordingly. The differences between current messaging codes indicating the reason for changes in address and supplier and the new codes registered by are set out below. Table 6 Differences in agreement reporting in and in current state New sales agreement for the customer's new accounting point ("Moving in") New sales agreement for the customer's existing accounting point with a new supplier ("Change of supplier") New sales agreement for the customer's existing accounting point with the current supplier ("Change of agreement") Customer changes (current code "Move") The customer makes a contract for an accounting point at which it is not yet a customer, for example in connection with moving into a new home. One of the existing grid and/or sales agreement customers is also involved in the new sales agreement, which is not with the current supplier One of the grid and/or sales agreement customers is also involved in the new sales agreement, which is with the current supplier Customer does not change (current code "Change of supplier") (Not possible) The customer switches supplier at the accounting point The customer makes a new agreement with the current supplier The aim is for the codes to better illustrate the real reasons behind new sales agreements. The new term "Change of agreement" will be taken into use in. This means that a new sales agreement is made for the customer's existing accounting point with the current supplier. will register the reason for making a new agreement depending on whether the customers stated in the new agreement differ from the customers stated in the valid agreements for the accounting point stored in ; that is, whether the customer or customers in the new agreement have sales or grid agreements for the accounting point at the time the agreement is made. If the customers at an accounting point change entirely with regard to both sales and grid agreements, the situation usually concerns a move in or out. In these cases, it is permitted to report the agreement as quickly as on the day in question. A contract can also be reported for the same day if the accounting point has no supplier. In all other cases, a period of 14 days shall be followed, taking the agreements' fixed terms into account. The time limits are the same for both the current and new supplier for the accounting point. The following table contains a summary of how decides the reason for which new agreements are registered. 's assignment of the aforementioned reasons is primarily used for statistical purposes. 49 (233)

50 Table 7 's decisionmaking concerning the reasons for reported new agreements Situation Changes at MP Remains the same at MP Reason 1 Customer moves to the accounting point All customers Sales and grid agreement DSO Moving in 2 The customer makes a new agreement with the current supplier for the existing accounting point. Sales agreement (Grid agreement) DSO Supplier All customers Change of agreement 3 The customer wishes to change (add/remove/change) parties to a contract in the event of e.g. divorce. At least one customer Sales agreement (Grid agreement) DSO Supplier At least one customer Change of agreement 4 The customer puts its electricity agreement out to tender and makes a contract with a new supplier. Supplier Sales agreement (Grid agreement) DSO All customers Change of supplier 5 The customer puts its electricity agreement out to tender and the parties to the new agreement are different from the parties to the existing agreement for the accounting point (added/removed/changed) Supplier At least one customer Sales agreement (Grid agreement) DSO At least one customer Change of supplier Special cases, such as reporting changes in the estate of a deceased person, depend on how estates are dealt with in the supplier's own processes. If an estate receives a business ID or if a contract is transferred in the name of beneficiaries (personal identification) the new agreement for the estate is reported to where it is registered as a move in. If the supplier or DSO only changes the customer's name and the agreement continues under the personal identification of the deceased, the change can be reported as a change of agreement (please see chapter 3.2.3). If in this situation a new agreement is nevertheless made, the new sales agreement will be reported to where it will be registered as a change of agreement. Before a new agreement is reported, the supplier may retrieve the accounting point data from. Rights to data are set out in chapter 2.2 of this document. The purpose of requesting preliminary data is to help the supplier to gain an idea of the kind of accounting point agreement it is possible to make for the customer in question. The accounting point identification and customer(s) identification are entered when requesting preliminary data. In addition to the customer and accounting point data, the supplier will also receive on the accounting point's agreement status as follows: Does the customer have a valid sales agreement for the accounting point or not If the customer has a sales agreement, will be returned as to whether the customer or customers are exactly the same as the customers which will be party to the new agreement. 50 (233)

51 Whether an existing sales agreement for an accounting point (if there is one) prevents a customer from making a new agreement for the accounting point when the customer remains the same and: a) The sales agreement is fixedterm. In addition, the end date for the fixed term if it is within 90 days from the moment of data retrieval b) The sales agreement has an exceptional termination condition. If the upcoming ending of a contract has already been reported for an accounting point, this date will be returned so that the supplier can agree on the start date of a new agreement without breaks in the delivery of electricity. If a new agreement has already been reported as due to start at an accounting point, this date will be returned so that the supplier can make a contract only for the time before the previously reported agreement (see example 3 in section ) Does the customer have a valid grid agreement for the accounting point or not If the customer has a grid agreement, will be returned as to whether the customer or customers are exactly the same as the customers which will be party to the new agreement. Of customer, the search will only return for the customer or customers for whom an identification was given. If a contract has other customers, a search will only return indicating that the agreement contains other customers, but the for these customers will not be returned. Corresponding validation will also be carried out when a supplier reports a new agreement to. Henceforth the term "customer" will also refer to all customers of a contract whenever there is more than one customer. It is also worth noting that customers and changes in customers at an accounting point are identified in based on customer identification (personal identification, business ID, association identification, party's own identification), not purely by name Making a grid agreement will decide whether a new grid agreement is necessary based on data reported by the supplier and on the accounting point's customer and agreement status at the given time. If the matter concerns a move in, a new grid agreement is always made. If the matter concerns a change in supplier or agreement, a new grid agreement is required in those situations wherein the valid grid agreement for an accounting point is held by a customer that differs from the customer in the upcoming sales agreement. This practice ensures that, in the future, accounting point sales and grid agreements are made for the same customers. If a new grid agreement is required, will create new grid agreement based on the supplier's notification with the status "unconfirmed". will inform the 51 (233)

52 DSO of the new grid agreement, which the DSO will confirm with its own notification to. The distribution grid owner may already have made a contract with the customer, whereupon the agreement is sent at this stage as confirmation to. Information from the DSO's confirmation is also sent to the supplier, whereupon the supplier is made aware of the necessary grid agreement, such as product data. The DSO will connect electricity to the accounting point as necessary on the delivery start date. The supplier does not need to send a separate connection request. Instead, the DSO connects the electricity based on the new agreement notification. It is operators' responsibility to always check that the customer is of full legal capacity before making a contract and reporting it to. Responsibility for checking always lies with the party which makes the agreement with the customer. Only validation which prevents the reporting of a contract for an underage customer will be built into. The DSO has the right to refuse to make a grid agreement with a customer based on a notification from the supplier. In such cases, the DSO notifies that it will not confirm the grid agreement and provide a reason as to why confirmation could not be given. This will be sent to the supplier Process description The creation of new accounting point agreements is depicted in the following process diagram. The process diagrams are also attached to this document for better readability. 52 (233)

53 Figure 15 Process diagram for reporting a new agreement

54 Rules In, a contract's start date refers to the date from which the supplier has the right to metering data and from which the supplier is responsible for accounting point consumption or production in its own balance sheet. In practice, this date also corresponds to the date from which the supplier has the right to invoice the customer. will also validate the length of the fixed term created for the consumer from this date. This term cannot be longer than two years. Reports of new sales agreements made for the same accounting point on the same or very close dates currently cause a great deal of investigative work. In, there will be clear rules concerning the terms and time periods for reporting new sales agreements for an accounting point. The rule of thumb is that there cannot simultaneously be two or more valid sales agreements for a single accounting point on the same date. The agreements are always valid for full periods of twentyfour hours, so a contract comes into effect at 00:00 on its start date and ends at the end of the 24hour period. The rules for submitting notifications for the same accounting point are as follows: 1. The start of a new sales agreement can always be reported for the current day if the accounting point has no supplier. 2. Movein reports should always be submitted no later than on the moving day and no earlier than 90 days before the agreement starts. 3. In all other cases besides the two aforementioned and in which the reporter of the new agreement is not the current supplier, the new sales agreement must be reported at least 14 days in advance and no earlier than 90 days before the agreement start date. 4. A sales agreement which is successfully reported to will automatically terminate any sales agreement that is valid on the date on which the new sales agreement comes into effect such that the existing sales agreement terminates one day prior to the entrance into force of the new agreement (this also applies to situations in which the previous customer has reported that it is moving out at a later date, whereupon the end date is modified to an earlier date). 5. A sales agreement containing a fixed term or exceptional termination condition for an accounting point will, for as long as it is valid, block the new sales agreements reported by a new supplier in which the customer or even one of the customers is the same as for the sales agreement valid for the accounting point. 6. A change in customer at the accounting point automatically cancels all new sales agreements for existing customers due to begin on the same date as the change of customer or at a later date (chapter example 4). 7. It is not possible to report two new agreements as starting on the same day, and the agreement that is reported later will be rejected (chapter example 2). One

55 exception is the rule in section 6 whereby the first new agreement made for a given day for the existing customer will be cancelled if a contract for the accounting point is reported in which even one customer changes. 8. Before a previously reported new sales agreement for an accounting point comes into effect, a new sales agreement can be reported for the "inbetween" period, but in such cases the end date of the agreement must be reported and cannot be later than the start date of the previously reported agreement (chapter example 3). The rule in section 6 is the exception. 9. Agreements may only be reported retrospectively in cases of error correction. All notifications of sales agreements starting, ending or being updated which lead to overlapping sales agreements and which are not separately mentioned above shall be rejected Examples The following examples aim to describe how reports of closeproximity or overlapping sales agreements are processed in to prevent the creation of overlapping agreements. Example 1: accounting point agreements reported with different start dates come into effect consecutively regardless of whether the supplier reports them on the same day or on different days. 55 (233)

56 Example 2: An accounting point agreement previously reported with the same start date as a new agreement prevents the new agreement from coming into effect on the same day; rejects the latter notification (B) from the supplier. Example 3: An upcoming agreement reported for the accounting point prevents the creation of a contract that would be valid until further notice and would begin before the upcoming agreement. This kind of situation may occur when e.g. a lessor wishes to renovate an apartment before a new tenant moves in and the tenant has already made an upcoming agreement for the accounting point. In this case, it is only possible to make agreement (B) for the "inbetween" period in, and the agreement will end before the start date of the earlier agreement (A). The notification for the new agreement (B) must include the agreement end date. The supplier is made aware of agreement A's start date when it requests preliminary accounting point data before reporting a new agreement. The notification informs the supplier of the date on which agreement B must end. 56 (233)

57 Example 4: A report of moving in to an accounting point cancels all previously reported upcoming changes of supplier or agreement. Situation before agreement B is reported: 57 (233)

58 Situation after agreement B is reported: Fixedterm sales agreements The fixed term of a sales agreement is reported to by submitting the end date of the agreement's fixed term. It is worth noting that in 's data model, this is different data from the agreement's end date, which is always the true end date of a contract and which is only stored once the agreement has ended. Sales agreements' fixed terms will be accounted for in in accordance with the same principles that are currently in use in the existing model. The general rule is that a fixedterm agreement can be terminated prematurely if a customer moves away from the accounting point. In, agreements are always checked by accounting point, so even if the supplier and customer have agreed on the continuation of a fixedterm agreement at the customer's new accounting point, from 's perspective these are two separate agreements for different accounting points and the first agreement can be terminated in. In, a fixedterm agreement prevents a supplier from making a new sales agreement in situations in which even one customer of the sales agreement valid for an accounting point is the same as the parties to the new sales agreement (section table cases 4 and 5). The customer may agree with the current supplier on agreement changes and new terms of agreement in a flexible manner. As such, a new customer can agree on the addition and removal of its agreement's parties with the existing seller in the event of e.g. divorce, even if the customer's existing agreement is a fixedterm agreement. The fixedterm nature of the valid agreement nevertheless prevents a new supplier's agreement from being reported to. The following table lists the time limits valid in different situations for reporting agreements to, the effect of their fixedterm nature and the reason registered by for reporting a new agreement. 58 (233)

59 Table 8 Various situations when reporting new agreements Situation Fixedterm nature of agreement Report to Reason 1 Customer moves to an accounting point No effect on changes to agreement No earlier than 90 days before the agreement comes into force and no later than on the day Moving in 2 The customer makes a new agreement with the current supplier for the existing accounting point. No effect No earlier than 90 days before the agreement comes into force and no later than on the day Change of agreement 3 The customer wishes to change (add/remove/change) parties to a contract in the event of e.g. divorce. No effect No earlier than 90 days before the agreement comes into force and no later than on the day Change of agreement 4 The customer puts its electricity agreement out to tender and makes a contract with a new supplier. Prevents a new agreement from being reported No earlier than 90 days and no later than 14 days before the agreement comes into effect Change of supplier 5 The customer puts its electricity agreement out to tender and the parties to the new agreement are different from the parties to the existing agreement for the accounting point (added/removed/changed) Prevents a new agreement from being reported No earlier than 90 days and no later than 14 days before the agreement comes into effect Change of supplier Rules for processing fixedterm agreements in : 1. A fixedterm agreement is deemed by default to continue as valid until further notice if the end date or renewal of a fixed term are not separately reported to. 2. The end date of a fixed term in a fixedterm sales agreement made for a consumer customer cannot be more than two years after the start date. 3. If the current seller wishes to terminate a valid fixedterm agreement and continue the agreement with a new one, the fixedterm nature of the valid agreement must be removed by updating the agreement, after which time the new agreement can be reported to. 4. The renewal of a fixedterm agreement is carried out with a contract update event (chapter 3.2.3), for which the supplier reports a new fixed term end date which will come into effect when the change is reported. 59 (233)

60 Exceptional termination conditions A supplier may agree on exceptional termination conditions for a contract that is not for a consumer customer. In accordance with the data model described above, the sales agreement contains on whether the agreement features exceptional termination conditions. In agreements wherein the customer's period of notice is longer than the usual term (14 days), the supplier must report this exceptional termination condition. For other exceptional termination conditions, either the date from which the new sales agreement can begin or the interval during which a new sales agreement can begin must be reported. If necessary, the supplier must update this data every day. If the supplier has, for example, a contract which can be terminated on the 5th of every month, the supplier must continually update the data to correspond to the next possible date that a new sales agreement can begin in accordance with the notice period. The date (or interval) provided must correspond to precisely the date on which a new sales agreement can begin, not the date on which the customer has the right to terminate the agreement. In the example case, the date can be given as an interval in which the start and end dates are the same. In accordance with its own terms, an exceptional termination condition in a contract prevents a new sales agreement from being made for the customer's existing accounting point in the same way that the accounting point's existing fixedterm sales agreement does. For exceptional termination conditions, the new supplier is made aware of the first possible start date for a contract even when it is more than 90 days away. However, it is not possible to report a contract earlier than 90 days in advance, even in this case Reporting changes to agreements Whenever a party makes changes in its own system to data that will be stored in, the changes must be reported to. Changes made to agreements are reported to in accordance with the following rules: 1. It is not possible to add or remove customers from agreements using an update event; instead a new sales agreement must be reported. 2. The start or end dates of a sales agreement can be changed before these dates (that is, not retrospectively) in only by first reporting the cancellation of the original notification to and then making a new notification with a new date. 3. Changing the start and end dates of a sales agreement once delivery has already begun or ended is set out in section Changes to a contract's content wherein a party updates in an existing agreement is carried out with a contract update event. Changes to the content of a contract include e.g. product changes, changes which affect invoicing details or a change to the fixedterm nature of a sales agreement (removal or renewal). 5. The end date of a contract's fixed term can be updated using the agreement update event. The end date of the fixed term in a consumer's agreement may not be extended using the agreement change event to exceed two years from the 60 (233)

61 agreement's start date. After this time, the supplier must report a new agreement to. Parties may also update customer such as the customer's name or contact details while delivery is ongoing. This can be reported to as part of a change to agreement or as a separate customer update. Agreement cancellation and correction processes are set out in more detail in section Reporting the ending of a contract As set out above, the report of a new sales agreement terminates the previous agreement at an accounting point automatically on the day preceding the start of the new agreement. In addition to this it is also possible to report the end of a contract to separately. In these cases, the rule of thumb is that a notification which terminates a contract in that is, records the end date of a contract is made by the party whose agreement is ending. will send a notification of the termination of the agreement to the other party who will then (in accordance with its own processes) terminate the agreement in its own system and then report this to using its own termination report. It is, however, also possible for the supplier of the customer's new accounting point to report the ending of a customer's agreement via, whereupon the report of termination is sent to the accounting point's DSO which will then terminate the agreement in as if the customer had notified the DSO itself that it is moving out. The ending of a contract is always reported to using the same termination report and the reason for termination is given using the reasons set out in the table below. 61 (233)

62 Table 9 Reasons for ending a contract Situation Customer moves out from an accounting point The customer or supplier terminates the sales agreement, also in situations wherein a fixedterm agreement is terminated and there is no desire for it to continue as valid until further notice. The supplier or DSO dissolves its agreement due to breach of agreement by the customer. Reason Moving out Terminating a contract Dissolving a contract Rules for terminating agreements at an accounting point: 1. In situations concerning a move out or the dissolving of a contract, agreements may be terminated on the day or at a later date. 2. The termination of a contract must be reported no later than 14 days before the date on which the agreement ends. 3. The termination of a contract in any situation may not be reported earlier than 90 days before the date on which the agreement ends. 4. A sales agreement may not be terminated on a date on which the upcoming new sales agreement is already in effect. 5. The act of moving out by a customer will automatically cancel all of the customer's upcoming new sales agreements (as in example 4 in section ). 6. Agreements may only be terminated or cancelled retrospectively in cases of error correction Process descriptions The following diagrams show the agreement termination processes taken by the supplier and DSO. 62 (233)

63 Figure 16 Process diagram for terminating a sales agreement 63 (233)

64 Figure 17 Process diagram for terminating a grid agreement Separate movein and moveout reports A move in reported for an accounting point will terminate any possible existing sales agreement for the accounting point. After this, the current supplier may, however, report a separate move out no later than the day preceding the move in. If the move out is reported for an earlier date than the earlier reported move in, the agreement's end date will be updated to correspond to the moving out notification. In this case, a period of time not covered by a contract will remain between the move in reported earlier and the move out reported later. will notify the DSO of this period. If a separate move out has been reported, the customer that is moving out will not be returned to the current supplier if the new agreement is cancelled. Situation before moveout notification: 64 (233)

65 Situation after moveout notification: Separate moveout notification as part of the customer's movein When a customer moves, it must be possible to serve the customer such that the customer can terminate the agreement at the moveout location by reporting it only to the supplier of the movein location. To allow this, features its own event through which the supplier of the movein location can report the customer's moveout from the moveout location to. This notification is sent from to the moveout location's DSO, who then terminates the grid agreement and reports this to in the same way as if the customer would have notified the DSO of the moveout itself. As a result of this process, the notification on agreement termination is then sent from to the supplier of the moveout location. The supplier of the movein location must provide at least one customer identification in its notification. The DSO can contact the customer if the supplier of the movein location has not reported all of the agreement's customers. 65 (233)

66 Figure 18 New supplier reports customer moving out The customer disputes a sales agreement The customer's right to dispute the validity of an electricity sales agreement will be made possible in in accordance with an upcoming decree to be issued by the Ministry of Employment and the Economy. For situations wherein a customer disputes a new sales agreement and the supplier does not agree to cancel or terminate the agreement, the cancellation or termination of the sales agreement must be made possible via a notification from the DSO for the accounting point. During the first phase, however, no functionality to send notifications of a dispute and terminate agreements will be built in. During the first phase, situations will be dealt with manually such that the DSO will provide a written notification of a dispute to the operator who will then cancel the disputed agreement and send this 66 (233)

67 on to the supplier. The field will be monitored as to how much customers dispute agreements and based on this, a decision will be made as to whether a functionality for handling disputes is required Cancelling a contract and correcting errors Agreements are cancelled for the purpose of correcting erroneous agreements and when the customer exercises its statutory cancellation right in home and distance sales. In addition to the cancellation of agreements, it is possible to correct erroneous data arising solely from parties' mistakes by reporting the start or end of agreements retrospectively. Retrospectively means that the start date of a reported agreement or the date on which a terminated agreement ended falls on any day preceding the date on which the notification was made. In general, retrospective change refers to a change which changes any validity of a sales agreement in the past. With regard to retrospective changes it is essential that both the validity of imbalance settlement (balance data) and the validity of the sales agreement (agreement ) are separately maintained by accounting point in. Balance data indicates the supplier on whose balance sheet the accounting point's consumption or production is calculated in 's imbalance settlement calculations. Changes outside of the balance window that are included in balance data will be accounted for in balance error correction. Agreement indicates which supplier has the right to accounting point data in (including metering data). Agreement corresponds to the time during which the supplier has the right to invoice the customer. In normal situations, balance data corresponds to agreement. Discrepancies between the balance sheet and agreement may occur when corrections are made retrospectively Cancelling a sales agreement Sales agreements are cancelled when a customer cancels a contract using its statutory cancellation right or in error situations wherein a sales agreement and any possible resulting grid agreement are made for an incorrect accounting point or otherwise erroneously. Cancellation may be carried out before the agreement starts or retrospectively after the agreement starts. The cancellation process for these two events are processed in in different ways. The supplier must report the cancellation of the agreement to. In most situations, when the sales agreement to be cancelled was originally reported, it terminated the preceding supplier's sales agreement at the accounting point. There is agreement in the field that the previous supplier should take the customer back unless the matter concerns a customer's fixedterm agreement that has already ended. There is not always a preceding supplier at movein sites and naturally therefore, the agreement cannot be returned in these situations. In its cancellation notification, the supplier must provide as to whether the agreement was cancelled by the customer or the supplier. Cancellation by the customer may, for example, involve a cancellation based on the customer's cancellation rights or a cancellation based on erroneous provided by the customer. In retrospective customer cancellations that is, cancellations made after the agreement has started the 67 (233)

68 supplier retains the invoicing right/agreement from the beginning of the agreement until the balance window has closed. The diagrams below depict a customer cancellation before the agreement begins (1) and a retrospective cancellation (2). Figure 19 Sales agreement cancelled by the customer before the agreement begins (1) and after it has begun (2). If there is no preceding supplier at the accounting point in connection with the customer's cancellation, the supplier will retain invoicing rights until the date of cancellation as shown in diagram 3. The supplier receives as to whether the situation is as for diagram 2 or 3 by checking the confirmation of the sales agreement notification to find out whether the sales agreement to be cancelled is registered as a move in or as a change of supplier. Figure 20 The situation after a reported cancellation by the customer when there is no preceding supplier Supplier cancellations arise from various erroneous situations caused by the supplier. In these cases, sends the data concerning the cancellation of a sales agreement to the (possible) previous supplier of the accounting point and the previous sales agreement will automatically be restored. If there is no preceding supplier and a retrospective 68 (233)

69 cancellation occurs, the accounting point will remain without a supplier from the date following the date of cancellation. Based on a relayed cancellation notification, the preceding supplier can report the termination of its own sales agreement to without the 14day time limit if cancellation is made during the business day following the cancellation notification. If cancellation occurs before a contract begins, the date of termination may not be earlier than the start date of the cancelled agreement. If cancellation occurs after the agreement's start date, the date of termination may not be earlier than the date on which cancellation is reported. The diagrams below show how sales agreements cancelled by the supplier before the start date are processed in. Diagram 4 depicts a situation wherein supplier B cancels its agreement before the agreement begins and supplier A's agreement is restored by default. Diagram 5 depicts a situation wherein supplier A reports the cancellation of its own agreement to based on a report by supplier B. Figure 21 Cancellation by supplier before agreement starts. The situation after cancellation has been reported (4) and the situation after the possible refusal of the preceding supplier to restore a contract (5). In, cancellations made after a contract has begun are processed such that supplier B's agreement is cancelled on the same day the cancellation is reported. Supplier A receives a report on the cancellation of the agreement and without further action, supplier A's ended agreement is restored in. Once it has received the report, supplier A can, as set out above, terminate its own sales agreement without time limit validation (such as that for a move out) no later than on the following business day. Supplier A may not, however, terminate its agreement retrospectively; it can only do so by the end of the day or on a later date. After the following business day has passed, normal time limits for termination will apply to supplier A's agreement. Diagram 6 below shows a situation in which supplier B cancels its agreement in after the agreement has begun and supplier A does not terminate its own agreement. 69 (233)

70 Balance data is only corrected for supplier A within the balance window. Diagram 7 outlines the corresponding situation in which supplier A terminates its own agreement. The accounting point is left without a supplier in accordance with supplier A's termination notification. notifies the DSO of the accounting point without a supplier. Figure 22 Supplier cancellation after a contract has begun. The situation after cancellation (6) and the situation after the possible refusal of the preceding supplier to restore a contract (7). If, regarding retrospective cancellation by a supplier, there is no previous sales agreement for an accounting point, the accounting point will remain without a supplier for the entire period after cancellation. Supplier B is, nevertheless, responsible for balances until the date of cancellation in accordance with diagram 8. If supplier B becomes aware of a customer that has used electricity at the accounting point during this time, supplier B can retrospectively report the start of a sales agreement after reaching agreement with the customer. Figure 23 Cancellation by the supplier when there is no preceding supplier 70 (233)

71 The cancellation of sales agreements may also lead to the cancellation of the grid agreement. The DSO must cancel confirmation of a grid agreement in if the grid agreement was originally confirmed based on a cancelled sales agreement. The old grid agreement will be automatically restored in based on a cancellation if this grid agreement was created in in connection with the creation of the sales agreement that is to be cancelled. If the previous supplier does not take the customer back and reports this as termination of a contract in, the DSO must terminate the grid agreement in via its own notification Retrospective error correction Retrospective changes to agreement start and end dates may only be made in clear cases of error. The rule of thumb for retrospective corrections is that the balance data is determined according the supplier that made the error, and agreement is determined based on who will have the right to invoice the customer. The principle is that the supplier which made the error is responsible for the balance sheet even if it does not have the right to invoice the customer. The supplier reports the retrospective start of a sales agreement using the same notification used to report an upcoming sales agreement. The report of a new retrospective sales agreement progresses like a normal process if there are no other suppliers' agreements valid for the accounting point after the date on which the reported sales agreement begins. In other cases, a sales agreement that begins retrospectively will not progress as a normal process and instead locks the process and responds with negative confirmation to the notification of a sales agreement which is to begin retrospectively. In order for the processing of the sales agreement to continue, the reporting supplier must manually process the data in 's interface. The supplier must provide an explanation in the interface as to why the agreement should begin retrospectively and submit the processor's contact details for clarification. After this, will notify the current supplier of the new supplier's explanation and contact details by and create a retrospective start approval request for the current supplier in 's interface. The current supplier must approve the retrospective start in the interface in order for processing of the retrospective sales agreement to continue. If the current supplier approves the retrospective start, the agreement process continues as normal. Upon rejection by the current supplier, negative confirmation will be sent to the new supplier that reported the retrospective agreement. If the current supplier neither approves nor rejects the retrospective start, will send a reminder to the current supplier after 2 business days and, if necessary, the operator will contact the current supplier directly. After a retrospective sales agreement has been approved, the agreement and balance data for an accounting point are determined based on the new supplier's notification as shown in the figure below. 71 (233)

72 If between the start date of a contract that begins retrospectively and the time of reporting there are valid sales agreements from more than one different supplier, the aforementioned procedure cannot be applied. In this case, the operator will investigate the details of all parties and guide them in resolving the matter amongst themselves. After the parties have come to a decision on a solution, the operator will make the necessary changes in. The retrospective termination of agreements must primarily be carried out using a retrospective agreement start date, which automatically terminates the previous sales agreement. This procedure should be followed if, for example a bankrupt company's agreement is retrospectively transferred to the bankrupt's estate. If in the given situation this is not a rational option, the sales agreement can be terminated retrospectively via a separate notification. In these cases, however, the use or production of electricity at the accounting point is recorded in the reporting supplier's balance sheet until the end of the day on which the report was submitted and the balance data for the accounting point is recorded accordingly as shown in the diagram below. In addition to the aforementioned cases, there may be situations in which there is a need to retrospectively change the start or end dates of a previously reported agreement. The principles mentioned above shall be followed in these situations. The start and end dates of agreements cannot be changed using a data update in. Instead, the earlier notification must first always be cancelled and then a new notification should be made with a corrected date. The aforementioned correction procedures should only be used in cases of error. Retrospective changes are monitored and possible misuse will not be tolerated. If the 72 (233)

73 situation requires an accounting point's balance data to be recorded in a manner other than that specified above, the operator or operators must contact the operator, which will make the necessary changes based on a written request Other types of agreement Smallscale production purchase agreements In accordance with existing practices, smallscale production sites are assigned their own accounting points in and their own individual processes are initiated. Smallscale production agreements are processed in the same way as traditional consumption accounting point agreements, meaning that there are no differences between agreement processes for smallscale production accounting points and consumption accounting points. In, agreements linked to a production accounting point are considered to be purchase agreements or smallscale production grid service agreements. If a production accounting point is connected to a consumption accounting point and the consumption accounting point's sales agreement is terminated with the reason "moving out", this will be sent to the DSO and to the purchase agreement's supplier. The linking of consumption and production accounting points also makes it possible for a supplier making a new agreement to use a preliminary search to find out whether the accounting point is connected to a production accounting point Electricity delivery agreements Electricity delivery agreements do not set any special requirements for. In, electricity delivery agreements are processed as a separate sales and grid agreement. The supplier must, nevertheless, inform that the matter concerns an electricity delivery agreement so that the DSO knows not to send grid agreement confirmation to the customer when it receives about the new agreement from. Correspondingly, if an electricity delivery agreement is converted into separate agreements, the DSO knows based on this that it should send a separate grid agreement confirmation to the customer. Information concerning an electricity delivery agreement may also be used to investigate the quantity and relative proportion of such agreements. The default supplier has the right to obtain as to whether the customer comes under the scope of default supply or not in accordance with the obligation to deliver set out in section 21 of the Electricity Market Act. In addition, the default supplier also has the right to receive, in the form of total energy data, to indicate how much of the customer base covered by the scope of default supply are supplied by other suppliers. will provide this data to the default supplier via 's user interface. 73 (233)

74 3.3 Processing metering data Metering data Figure 24 Class diagram for metering data The diagram above outlines the data structure of metering data. In, there are three kinds of metering points: accounting points, connection 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 not possible for an accounting point to have two metering time series with the same metering type. As an example, in sites where accounting point consumption consists of several metering time series, only one (total) time series is reported to. Production units and connection points can only have one metering time series. A production unit's own consumption is reported for an accounting point created specifically for that purpose. Energy transmitted in different directions at a connection point are reported using the corresponding mathematical signs. 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). It is possible to report to and retrieve from metering values using the desired unit (Wh, kwh, MWh, GWh or varh, kvarh, Mvarh, Gvarh). For an accounting point at which the fuse size or corresponding electrical power is max. 3x63 A, metering data must be reported to an accuracy of 10 watthours. Otherwise, metering data must be reported to an accuracy of at least one kilowatthour. When reporting metering data, attention must be paid to the number of decimal places concerning the aforementioned accuracies. For example, kilowatthours (kwh) must be reported to at least two decimal 74 (233)

75 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. allows different time steps for metering data (e.g. 15 minutes, 30 minutes and 1 hour). The DSO must report its metering data using a time step that is legally regulated and used in imbalance settlement. Metering data can be retrieved from using the desired time step (e.g. 15 minutes, hour, month). If the time step submitted for the search is shorter than the time step that the DSO used to report the metering data to, will return the metering data using the unit provided by the DSO. supports the audittrail function, meaning that all changes made to metering data are recorded in the history data. In, metering data contains a timestamp, metering value, metering data status and the most recent update to the metering data. The date of update is determined based on the time at which stores the data in its database. For points that are not connection points, only positive values are processed in, so 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 Reporting metering data The rule of thumb is that only new and changed metering data should be reported to. There is no need to report metering data for entire 24hour periods, but will always send data as periods of 24 hours. Changes in status are also interpreted as a change to metering data, even if the metering data itself remains the same. The resubmission of unchanged data will not be rejected, but systematic action that places unnecessary load on will not be tolerated. The necessary tools will be built to monitor this. It is usually the obligation of the metering responsible party at the metering point to report data to. At accounting points, the metering responsible party is always the DSO. The metering responsible party is often different from the DSO, for example, at connection points where the metering responsible party could be the main grid owner Time limits for reporting metering data Time limits for reporting metering data to will be determined in accordance with the metering decree. In this document, time limits are currently determined based on Nordic Balance Settlement time limits, but the time limits will be updated to correspond to the new metering decree. 's time limits do not distinguish weekday public holidays and weekends, which corresponds to the Nordic Balance Settlement practice. Preliminary metering data for the previous day must be reported to by midnight on the following day. In accordance with the imbalance settlement schedule, a DSO's final imbalance settlement data must be reported to esett for a delivery date of 13 days ago no later than 1:00 pm Finnish time, after which time the balance window for the delivery date in question will close. In practice, requires a little time to carry out imbalance 75 (233)

76 settlement calculations before data is submitted to esett. As such, final metering data should be submitted to in sufficient time before the balance window closes. A rule of thumb is that requires four hours to carry out imbalance settlement calculations. During this time, processes and validates metering data, carries out calculations and submits the data to esett. Sufficient time should be reserved for these actions in order to comply with imbalance settlement time limits in all situations. Figure 25 Time limits for reporting metering data. The red text shows the metering responsible party's time limits for submission to and the green text shows 's time limits for submission to esett. It is not permitted to report future metering data or very old metering data (more than 6 years) Metering data validation The responsibility for validating metering data and submitting accurate metering data to lies with the metering responsible party. carries out simple validation for metering data in cases where the DSO's validation is not at a sufficient level. The most significant validation carried out by is status validation, the rules for which are set out in section only performs validation on negative and excessive values, depending on the type of metering point. A value is deemed to be excessive if it is more than ten times the electrical power for the fuse size at the accounting point. If the fuse size is not reported to, the electrical power should be reported, whereupon electrical power will be used in validation in place of fuse size. Metering time series data rejected in validation will not be stored in the database and will return time seriesspecific rejection. The table below lists validations carried out by by metering type. 76 (233)

77 Table 10 Metering data validation Metering type Accounting point consumption Accounting point production Reactive power output/input Connection point metering Production unit metering Grounds for rejection Erroneous status, negative values, values which exceed electrical power by a factor of 10. Erroneous status, negative values, values which exceed production capacity by a factor of 10. Negative values Erroneous status Erroneous status, negative values, values which exceed production capacity by a factor of Status processing The table below outlines the statuses used in from weakest to strongest and also the time limits according to which the status must be replaced with a stronger status. Table 11 Metering statuses used in Status Missing Uncertain Estimated Explanation Used if no data has been obtained from the meter and preliminary data is sent as zero use. The status of data denoted as "Missing" must always be replaced with a stronger status within 5 days. Used when it is assumed that data may become more detailed or change later on. The "Uncertain" status is most typically used when it is necessary to estimate missing hourly data, but it is assumed that the measured data will be obtained later on. Data assigned an "Uncertain" status must primarily be replaced with a stronger status before the balance window closes 1. Also used for reading metering profiles when the profile is calculated based on an annual use estimate. Used when it is necessary to estimate hourly data and it is known that no measured or more detailed data will be obtained later on. Permitted replacement statuses Uncertain, Estimated or OK Estimated or OK (As necessary) Corrected OK 1 In exceptional situations, the "Uncertain" status may remain even after the balance window has closed [2]. 77 (233)

78 OK Corrected OK Used for hourly data obtained from the meter, if there is no reason to assume that the meter value is erroneous. Also used for reading metering profiles when hourly values are calculated from the meter reading. Used when hourly data previously sent with an "OK" or "Estimated" status nevertheless has to be corrected. (As necessary) Corrected OK Values may be changed, but it is not possible to replace the status with a weaker status. will not reject metering data if the status is not within the time limits set out above. will however reject metering data if attempts are made to replace metering data with a weaker status. Monitoring will be constructed for with which to identify and take action to stop operators who deviate from the abovementioned rules. In total calculations, such as when calculating a supplier's metered total delivery, the status of the total time series is determined in accordance with the time series that has the weakest status of all of the time series used in the calculations Monitoring of metering data reports will send reminders to the metering responsible party if parties fail to comply with the reporting time limits and status processing instructions set out above. Reminders will be sent when Preliminary metering data for the day of delivery (the previous day) has not been reported at all by the end of the day Data assigned a "Missing" status has remained unestimated for 5 days after delivery or There is still metering data with an "Uncertain" status after the balance window has closed. In the first two cases set out above, reminders will be sent once a day until metering data is corrected or submitted. In the last case, a reminder will be sent only once, because in some situations there is reason to retain an "Uncertain" status even after the balance window has closed. Reminders will only be sent once the relevant time limit has been exceeded. The industry will largely trust the DSOs to comply with agreed rules and to implement the necessary processes for these purposes in their own system. The purpose of reminders is to draw attention to noncompliance with rules. If a DSO does not change its operating methods despite repeated reminders, action will be taken against such activity. 78 (233)

79 Transmitting metering data All new and changed metering data is automatically transmitted to all parties entitled to receive the data. If for some reason a party does not require automatic data transmission in its own operations, the party can opt out of data transmission in the user interface. In such cases the party can use the separate metering data retrieval event (DH220) Processing reading metering and unmetered sites 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. In, 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 socalled 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 use estimate will be reported to with the status "Uncertain". The status "OK" will be reported 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 timeseries 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 hour 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 in the same manner and with the same time limits and validations as for hourly metering data Correction of metering data The DSO must correct erroneous metering data in for the entire time during which the metering data is stored in (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. Corrections to metering data may relate to the correction of a customer's invoice if the customer has already been invoiced based on erroneous data. In these cases, Finnish Energy's guidelines [1] will be followed as usual. The DSO must check the data for an accounting point in 's interface to find the suppliers who have held sales 79 (233)

80 agreements during the period affected by the error. After this, the DSO must inform each supplier that is obligated to correct its customer invoicing. The notice must include the time period from which the supplier must carry out the correction. Metering data adjustments are also accounted for in the correction of balance errors Processing reactive energy data allows the reporting and retrieval of metering data on reactive power input from the grid (inductive) and output to the grid (capacitive). With regard to reactive energy acts solely as a data transmitter. As such, does not carry out calculations for reactive energy metering data or monitor reports of this data. Only the validation of negative values 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. A data field will be added to the accounting point that indicates that reactive energy metering data is available for the accounting point. Based on this, the supplier may order the transmission of reactive energy metering data in the interface. Information concerning the availability of reactive energy metering data is updated by depending on whether the DSO has reported new reactive energy metering data in the last month Processing connection point and production unit metering Connection point and production unit metering data is required in in order to calculate a DSO's imbalance settlement. This metering data is reported in the same way as other metering data. It is not, however, possible to correct connection point metering data that falls outside of the balance window. Possible errors in connection point metering data will be corrected by the metering responsible party and its counterpart (another grid owner) amongst themselves. It is the obligation of the metering responsible party of the metering point to report connection point metering data to. As such, the transmission system operator and regional grid companies, for example, must report connection point metering data if the imbalance settlement for the connection point's other metering grid area is processed in. The validation and processing of connection point and production unit metering correspond to the processing of other (active energy) metering data where applicable. 3.4 Disconnection and connection processes General description From 's perspective, connections and disconnections are changes in accounting point status which are carried out in conjunction with agreement processes and during delivery with regard to parties' debt collection processes or modification work carried out at the accounting point. forwards the supplier's requests for a change in accounting point status to the DSO and sends data on the completed status change from the DSO to the supplier. 80 (233)

81 Time limits for connection and disconnection requests are determined based on the part of the overall process for which the procedure is performed. When connection or disconnection occurs as part of a moving process, no separate connection or disconnection request is made, and instead the DSO connects or disconnects the accounting point's electricity as necessary at the end of the agreement process, whereupon the time limits for exchange are determined in accordance with agreement processes. As such, in cases concerning a move in, it may be possible under certain conditions to achieve connection at an accounting point on the same day (a more detailed description can be found in agreement processes). The operating model for reconnection differs by grid company. The supplier must make the connection or disconnection requests relating to the debt collection process no later than one week before the desired date. Once the customer pays the outstanding invoice, good customer service dictates that reconnection should take place as quickly as possible. forwards the request in real time to the DSO, which then carries out reconnection in line with its own processes. By default, the DSO reports the completed connection or disconnection as soon as the is available in the DSO's own system, as is the case for any other accounting point data update. If the matter concerns a site where connection or disconnection is carried out manually, there may be a delay in updating the data in the DSO's system and therefore to. The maximum permitted length of the delay is one week. Accounting point connection and disconnection requests are not validated based on status in, since status could be temporarily erroneous due to the delay. The supplier can always send connection or disconnection requests based on 's status. The DSO has the correct status, so it is able to correctly handle the supplier's requests in its own processes. One example of the operating method is a situation in which a supplier has first requested disconnection due to debt collection and the DSO manually disconnects electricity from the accounting point in the morning of the day on which the request was made. The customer informs the supplier that it has paid the invoice as soon as the electricity is disconnected, but the supplier does not see the correct accounting point status in since the DSO does not yet have the in its own system due to the manual disconnection. Even though the accounting point's status in is connected, the supplier may send a connection request to which the DSO can send on to an engineer. If the DSO is unable to carry out the requested disconnection on the date requested by the supplier, the electricity delivered to the accounting point must be included in the DSO's balance sheet. The DSO must report this delay to the supplier via. The DSO usually charges a fee for disconnections and connections carried out at short notice, outside of business hours or without remote connection. In these cases, the DSO invoices either the supplier or the customer, depending on which party has requested the connection or disconnection. DSOs' price lists will be collected in a predefined table in order for the supplier to be able to easily provide the customer with additional concerning the costs of connections and disconnections. These situations most often relate to moving processes in which the move in takes place quickly. Using the DSO's pricelist as an aid, it is easier to agree the start date of a contract with the customer and to inform the customer of any costs arising due to the rapid schedule. 81 (233)

82 During delivery, the customer may also require connection or disconnection to the accounting point due to e.g. renovation. In these cases, the customer should contact the DSO. In situations wherein disconnection of an accounting point leads to the disconnection of a production accounting point in the same physical location, the DSO must report the completed disconnection to both accounting points Process descriptions The following figures describe disconnections and connections requested by the supplier as well as the overall processes for disconnections and connections reported by the DSO. Figure 26 Disconnection process initiated at the supplier's request 82 (233)

83 Figure 27 Connection process initiated at the supplier's request 83 (233)

84 Figure 28 Disconnection process initiated at the DSO's request 84 (233)

85 Figure 29 Connection process initiated at the DSO's request 3.5 Distribution system operator's imbalance settlement According to the new Nordic Balance Settlement model, an imbalance statement by a DSO is calculated by metering grid area. DSOs can divide their grids into one or more metering grid areas. However, DSOs usually have only one metering grid area. This subsection describes the DSO's imbalance settlement calculations performed in and imbalance settlement data notifications to esett. After implementation, will handle imbalance settlement reporting to esett on behalf of the DSO. This will apply to all data. For this purpose, tools will be created in, also for maintenance of socalled structural. will also send the DSO data about metering grid area balance discrepancies calculated by esett. The DSO is responsible for reporting the settlement data required to calculate the imbalance settlement described in this section to in accordance with the agreed rules and deadlines. is responsible for performing the imbalance settlement calculations and sending these to esett in compliance with the rules of the Nordic imbalance settlement model. Imbalance settlement data can also be retrieved from by parties entitled to this data. 85 (233)

86 3.5.1 Rules Calculations In a normal situation, accounting point consumption (production) is calculated to the balance of the supplier for the accounting point. Exceptions are situations in which the supplier requests disconnection for the accounting point within the agreed time limits, but the DSO cannot for one reason or another disconnect the electricity. In this case, consumption (production) is calculated as the DSO's losses. This also applies to situations in which the accounting point remains without a supplier but the DSO cannot disconnect the electricity. Balance data is transferred to the DSO (more accurately, it has no supplier) on the day following the supplier's disconnection request. Balance data is transferred back to the supplier at the start of the hour of connection reported by the DSO. After the implementation of, the DSO may not necessarily have about the accounting point supplier in the current manner. For this reason, will send a notification to the DSO when an electricity sales agreement for the accounting point ends, so that the DSO knows when to disconnect the electricity. also informs the DSOs separately if accounting points have no supplier and disconnection has not been reported for them. In addition to the previous, (still) provides DSOs with a separate retrieval event, which allows a DSO to obtain about accounting pointspecific consumptions/productions that have been calculated as losses for the DSO. Imbalance settlement calculations also affect terminations occurring in agreement processes and retroactive changes to electricity sales agreements. These practices are described in section Initial calculation data The figure below presents the data used as the basis for imbalance settlement calculations in. With the exception of electricity sales agreement, the DSO is responsible for maintaining this data. 86 (233)

87 Figure 30 Data used in imbalance settlement calculation The foundation for imbalance settlement calculations is the metering data from the metering points: accounting points, connection points and production units. The DSO maintains accounting point data by means of the events in section The connection point and production unit is maintained via the interface. This must be created via the interface before the metering data for the metering points in question is reported. The DSO also maintains the about the production unit supplier. The metering data for these metering points is reported in accordance with section The DSO must also use the interface to maintain about which suppliers are responsible for the open supplier and loss supplier roles for the metering grid area (balance deviation). Electricity sales agreements and their validity are determined according to the events in section 3.2. In accordance with the esett rules, specifies the supplierspecific and metering grid areaspecific total data that it reports according to accounting point type and metering method. 87 (233)

88 Calculated data The table below presents the metering grid areaspecific total calculations calculated by. The data on the blue background is reported to esett for imbalance settlement. The data that is not on a blue background are intermediate results needed for calculating the DSO's losses. It is not necessary to save the intermediate results for imbalance settlement, but this data may be useful for checking calculations and other utilisation. Table Metering grid areaspecific total calculations calculated by # Data calculated Supplier's measured total delivery Supplier's profiled total delivery Supplier's smallscale production total Supplier's own consumption total Connection point total Total delivery measured for the metering grid area Profiled total delivery for the metering grid area Smallscale production total for the metering grid area Auxiliary power sum for the metering grid area Production unit total for the metering grid area Description The supplier's hourly measured total of measuring time series for consumption accounting points in the metering grid area, divided on an hourly basis. The supplier's total of measuring time series for the profiled (reading measured and nonmeasured) consumption accounting points in the metering grid area, divided on an hourly basis. The supplier's hourly measured total of measuring time series for smallscale production accounting points in the metering grid area, divided on an hourly basis. The supplier's hourly measured sum of measuring time series for the production unit's own consumption accounting points in the metering grid area, divided on an hourly basis. The connection point total between two metering grid areas calculated from connection point metering. Combined total deliveries in section 1. Combined total deliveries in section 2. Combined smallscale totals in section 3. Combined auxiliary power totals in section 4. Sum of all production unit metering in the metering grid area. 88 (233)

89 11 12 Overall connection point total for the metering grid area Metering grid area losses Sum of connection point totals in section 5 that are part of the metering grid area being calculated. Calculated on the basis of sections 6 11 using the formula The chart below presents a diagram of how the calculations described above are calculated in and how the DSO's imbalance is calculated by esett. Figure 31 Imbalance settlement calculation for the metering grid area 89 (233)

90 3.5.3 Data reported to esett This section describes how imbalance settlement data can be reported from to esett using the current interface specifications (available at Thus, the data exchanges presented below do not apply to DSOs, and reports this on behalf of the DSOs. However, the DSO must for its part maintain the data described in section in so that this data can be compiled and reported to esett. and esett can also agree on exchange that is based on interface specifications other than those outlined above Time series data reports the belowmentioned time series to esett on a supplier and metering grid areaspecific basis: Table 13 Imbalance settlement data communicated to esett on a supplier and metering grid areaspecific basis Data NBS Information exchange document BusinessType Code Settlement MethodCode Measured total delivery Aggregated Data per MGA for Settlement Responsible from MDA Consumption (A04) Non profiled Profiled total delivery Aggregated Data per MGA for Settlement Responsible from MDA Consumption (A04) Profiled Measured total own consumption Aggregated Data per MGA for Settlement Responsible from MDA Production Units own consumption (B36) Non profiled MGA losses 1 (must be allocated to a single supplier) Aggregated Data per MGA for Settlement Responsible from MDA Losses (A15) Non profiled In addition to the above, reports to esett the production data for individual production units (PU), supplierspecific smallscale production sums by MGA and connection point totals between grids. creates a virtual production unit (PU) for the supplier's MGA smallscale production total, for which the data is reported. The exchange documents that can use to report this to esett are listed below. 1 including losses 90 (233)

91 Table 14 NBS exchange documents used by Data Supplier's smallscale production total Production unit's production Connection point total NBS Information exchange document Validated data for Aggregator from MDR Validated data for Aggregator from MDR Aggregated Data per neighbouring grid MeteringPoint TypeCode Production Production Exchange Structural reports socalled structural to esett separately before the metering data can be reported. Structural includes about which supplier operates in a certain MGA. For example, when a new supplier registers with, this is reported to esett. Technically speaking, the smallscale production total will also be processed as a socalled virtual production unit and it will be separately created for each supplier on an MGAspecific basis. will report the following structural to esett for the DSO's imbalance settlement: Table 15 Data reported to esett Data Connection point data Supplier operating in the MGA Production unit data NBS Information exchange document Area Specification Document Party Master Data Document Resource Object Master Data Document For the supplier operating in the MGA, includes the following in its notification to esett: MGA, consumption type (BusinessTypeCode), imbalance settlement method (SettlementMethodCode) and validity data. The consumption type/imbalance settlement method combination for each supplier must be reported as separate data to esett in accordance with Table Table Supplier's imbalance settlement data calculates imbalance settlement time series data for the supplier and the MGA. The diagram below presents the supplier's MGAspecific imbalance settlement data. The new and changed imbalance settlement data calculated by is reported to the 91 (233)

92 suppliers on a daily basis until the first day outside the balance window. In addition to the notification, the suppliers can also retrieve this data separately from. Figure 32 Supplier's MGAspecific imbalance settlement data Distribution system operator's imbalance settlement data The DSO has the right to both the abovementioned supplier's imbalance settlement data and the MGA imbalance settlement data. The new and changed imbalance settlement data calculated by is reported to the DSOs on a daily basis until the first day outside the balance window. In addition to the notification, the DSOs can also retrieve this data separately from. Figure 33 DSO's MGAspecific imbalance settlement data 92 (233)

93 3.6 Management of balance errors Management of balance errors in is based on the Finnish Energy's instructions "Taseisiin jääneiden virheiden käsittely taseiden sulkeutumisen jälkeen (Handling of balance deviation after balance window closure) [1]. Balance deviation occur as a result of metering data corrections and retroactive electricity sales agreement terminations and other retroactive corrections to electricity sales agreement validity performed outside the balance window. Changes in the validity of electricity sales agreements may also occur due to changes to the validity of the accounting point made by the DSO. Handling of retroactive terminations and changes in electricity sales agreement validity periods is described in section Balance errors will be corrected retroactively for a period of three years on an accounting pointspecific basis twice a year in accordance with the Finnish Energy instructions. Calculation of balance errors can also be initiated at the specific request of an operator if the balance error is large and the operator wants to handle it quickly. Following calculation, the outlined in appendix 3 of the instructions for handling balance errors [1] will be reported to the parties. DSOs use this to perform supplierspecific invoicing and the suppliers can use this to check their balance error calculations. Rather than performing separate balancing calculation in, reading metered sites will be managed like hourly metered accounting points. In practice, balance error correction will always take place in reading metered sites. 93 (233)

94 Figure 34 Process diagram for correcting balance errors Correction of balance errors functions in in accordance with the above diagram. maintains two types of accounting pointspecific balance data for the supplier: balance data reported /previously corrected for imbalance settlement and balance data in accordance with the at the time of calculation. In addition to the specification in section 3.2.5, balance data is in this context also considered to be the accounting point's hourly energies for a period corresponding to the time that the supplier has balance responsibility. In practice, the balance data that constitutes the grounds for all correction invoicing is saved as historical data for inspection purposes. Thus, always has the about what was originally reported for imbalance settlement and how this data has been corrected later for each time period. initially calculates the supplier's balance data using the data available at the time of calculation. In practice, the calculation result is then compared to either the data reported for imbalance settlement or the data corrected earlier (depending on whether the balance data for the time period has been corrected). Possible differences in comparison are recorded as balance errors and the supplier's correction is obtained by multiplying the hourly difference by the NordPool Spot area price for Finland. After this, the balance data initially calculated at the time of calculation is saved as historical data with which the calculation result performed the next time is compared. Finally, creates MGA 94 (233)

95 specific correction invoicing material for the supplier and sends this to the DSO, which performs the actual refund/correction invoicing for the supplier. In conjunction with calculation of balance errors, the DSO's losses are also calculated using the difference calculation principle described above and changes in losses are recorded to the loss supplier for the MGA. 3.7 Maintenance and retrieval of product and invoice row Product data enables the maintenance and transfer of product data for different needs. In order for suppliers to be able to make an electricity sales agreement with a product that corresponds to the accounting point grid service product, the DSOs must maintain the data for their own transmission products according to the structure below. Suppliers also need grid service product data for electricity delivery agreement invoicing. Suppliers can maintain sales product data in accordance with their own needs and agreements signed with other operators. The sales product is not forwarded to the DSO or third parties without separate consent from the supplier. Price for the product components is communicated between operators only when the invoicing method in the accounting point agreements is equivalent to combined invoicing and the operator has provided the other party with authorisation to this. The customer cannot provide a third party with authorisation for price. This must be reported and it can be retrieved via an automated interface in accordance with DH700 events. Only the product identification and product name are reported when retrieving accounting point data and in agreement processes, in which case the abovementioned interface must be used to clarify the complete product structure. If necessary, several products can be reported for a contract. The only product data that can be updated is the names of the product and product components, calendar and price. A new product must be created for other updating needs. Figure 35 Product data category diagram 95 (233)

96 In the above structure, the product can be, for example, "Timed transmission", which has two product components: "Day transmission" and "Night transmission". A calendar time series is a time series in which the hour value can be 0 or 1. When the value is 1, the product component in question is applied for the hour in question. A calendar time series must be compiled separately for each year, because a calendar can vary according to public holidays falling on weekdays that occur at different times each year. The calendar time series must also take changes between daylight savings and standard time into consideration, as well as the extra day in leap years. Calendar time series must be reported by the end of September at the latest. A pricetime series indicates the price for each hour Invoice row If desired, operators can communicate invoice row via. Invoice row is reported according to the structure below. In the same manner as pricing, invoice row is only communicated between actors when the invoicing method in the accounting point agreements is equivalent to combined invoicing and the operator has authorised the other party for this. The customer cannot provide a third party with authorisation for invoice row. Figure 36 Invoice row category diagram The invoice rows described above can be retrieved on the basis of time interval. In this case, the search retrieves all the invoice rows for which the time interval cuts across the time interval reported in the search. For example, a search for the interval could retrieve invoice rows for the time period of and In general, must enable communication of invoice row in accordance with the Decree on Invoices (836/2000). 3.8 Authorisations The rights of parties are managed by means of authorisations. There are two types of authorisations: 96 (233)

97 1. Authorisations granted by the customer, in which the customer provides consent to personal and electricity consumption data. The principle of these authorisations is described under the number 1 in the figure below. 2. Authorisations that parties grant to each other, by which the parties give other parties the right to handle a task in accordance with a certain role. The principle of these authorisations is described in the figure below under the numbers 2 (authorisations granted by the supplier) and 3 (authorisations granted by the DSO). Figure 37 Authorisations reported to Authorisations granted by the customer The customer authorises a party to use its own for a specific purpose. The following table presents examples of the most common purposes for authorisations. 97 (233)

98 Table 16 Purposes of authorisations Purpose of authorisation Authorised party Validity of authorisation Rights provided by the authorisation 1a The customer authorises the supplier to view its so that the supplier can provide a better offer in a competitive bidding situation. New supplier 24 hours from the time the supplier reports receiving the authorisation. Customer, accounting point data and metering data retrieval. 1b The customer agrees with a consultant concerning competitive bidding and authorises the consultant to view the customer and accounting point data. 3rd party For the duration of the competitive bidding process. Customer, accounting point data and metering data retrieval. 1c The customer authorises a consultant to handle all its matters related to electricity use. 3rd party Max. 2 years Customer, accounting point data and metering data retrieval. Authorisations granted by the customer are always specific to an accounting point and they must be given a period of validity that is a maximum of two years. The validity must correspond to the purpose. For example, purposes 1b and 1c in the table entitle a third party to the same but the validity periods of the authorisations differ because the purposes are different. The customer grants authorisation to an authorised supplier or DSO, which reports the authorisation to via a separate event, after which the party can retrieve the specified from. As a general rule, trusts the authorisation sent by suppliers and DSOs and the authorised party is responsible for being able to verify the authorisation received from the customer in accordance with the terms of the agreement with if necessary. Use of authorisations will be monitored by means of measures to be planned later in the project. When a customer authorises a third party, the customer must grant the authorisation to as an identified user. The third party must be provided with access to the service described in section 3.9. If an accounting point has more than one customer, each customer must grant authorisation in order for a third party to obtain the right to accounting point and metering data. The customer will be given the opportunity to manage the authorisations that it grants as described in section (233)

99 3.8.2 Authorisations granted by the parties Authorisations that the parties grant to each other allow the service providers of suppliers and DSOs to have a direct connection with. These service providers must have an agreement with, after which they receive user rights to the system interfaces. The following table presents examples of the most common purposes for authorisations between parties. Table 17 Authorisation needs between parties Purpose of authorisation Authorised party Validity of authorisation Rights provided by the authorisation 2a A separate invoicing service provider handles the supplier's invoicing. 3rd party A period specified by the supplier. Customer, metering data, agreement and product data retrieval. 3a A metering data collector for the DSO delivers metering data directly to. 3rd party A period specified by the distribution grid owner. Delivery and retrieval of metering data. 3b A service provider handles management of the distribution grid owner's balance errors. 3rd party A period specified by the distribution grid owner. Retrieval of invoicing for balance errors. 3c A separate invoicing service provider handles the distribution grid owner's invoicing. 3rd party A period specified by the distribution grid owner. Customer, metering data, agreement and product data retrieval. The distribution grid owner authorises a supplier to retrieve connection point metering. Supplier A period specified by the distribution grid owner. Retrieval of connection point metering data. Authorisations between parties can be granted on a data setspecific and/or eventspecific basis. If a supplier or distribution grid owner has outsourced a function to a service provider, it uses authorisation to inform which party is entitled to which (for example, customer and accounting point data and their retrieval) and to initiate which event (for example, metering data delivery). The authorised party receives rights to and processes (such as metering data delivery) according to the details of the authorisation. The operators use the interface to manage authorisation. 99 (233)

100 The parties can authorise any party with which it has an agreement for handling some task. Thus, an authorisation can be granted to another supplier, DSO or a third party, in which case each party can function in several different roles with regard to. 100 (233)

101 3.9 Forwarding party notifies all parties of the registration of new parties, termination of parties and updating of parties'. Party is maintained via the interface. In conjunction with the notification, the DSO also receives the necessary for sending balance error invoices. Figure 38 Party stored in 3.10 Customer access to own Customer access to its own in is technically arranged via the customer service portal of the electricity supplier and/or DSO. A link added to the operator's customer service portal allows the customer to access the service provided by. The customer sees the service as part of the supplier's or DSO's customer service portal. The service interface opens for the customer, who can, for example, see the companies, and time periods for which authorisations have been granted. If desired, the customer can change this. The customer can also see the metering data for its accounting point sites and all of its other own. The customer sees its own regardless of which grid company's area its accounting points are located in or who sells electricity to them. 101 (233)

102 The process described below shows how a customer is provided with access to the service provided by and subsequently to the customerspecific contained in. Figure 39 Customer access to its own The customer can access its own via the following stages: 1. Registering with the customer service portal of the supplier or DSO by means of the existing practice. 2. The customer is identified so that the customer's identification data is unambiguous (identity number or similar). Identification takes place by means of strong identification methods offered in the supplier's or DSO's customer service portal. 3. Once in the customer service portal, the customer opens the "My electricity " service, which is an embedded interface (Web) in the customer service portal. Access to the "My electricity " service requires strong electronic identification confirmed by the Finnish Communications Regulatory Authority. If a customer has already registered in stage 1 described above using strong electronic identification, transition to the service can, when possible, be implemented without separate identification. A party that will have a statutory obligation to provide access to the service described above will be specified later prior to implementation of the service System availability As a general rule, the system is always available 24/7 unless disturbances occur or the system has scheduled service interruptions. The system environment (facilities, equipment) will be a highavailability (usability) environment, which means that it is designed so that availability with regard to the environment is 99.9%. In other words, interruptions in use caused by the environment will 102 (233)

103 statistically be a maximum of nine hours during a oneyear period. The system must also have the readiness to support high availability with regard to security and ICT. In terms of the target response times and solution times for disturbances, the operating support service for the system environment is at a level that supports the desired availability level. These solutions are aimed at creating the best possible conditions to ensure that the system is available and that it is in use and a possible disturbance situation is not caused by equipment or environment factors. System use, or the way in which the actual applications are used in, requires disturbance and user support and an organisation prepared to provide it that handles communication between the user organisations of different parties and service provider organisations. Support ensures that disturbances observed by users or situations related to assisting users are solved within the framework of the response times agreed with the industry. Disturbances are classified according to severity level and a solution time is specified for each level. For example, disturbances can occur in the application interfaces with which the system is used or in the exchange interfaces between various systems and the system Users associated with system administration Users associated with system management and disturbance clearance are: The main users designated by the DSOs and electricity suppliers, who are responsible for transmitting data between the metering and customer systems of the DSOs and suppliers and the system or who use the system directly via an interface or are responsible for its functionality. The companies are responsible for keeping the about the main user (main users) up to date in the system. The main users designated by other service providers, who are responsible for transmitting data between their own systems and the system or who use the system directly via an interface or are responsible for its functionality. Main users administering the Fingrid system System support service model A disturbance situation in which the support service is needed can occur at any user level. For example, it can be visible to the customer so that a process used to create a new electricity agreement and connect electricity to a new accounting point does not run and thus the new agreement and connection cannot be confirmed. A disturbance can be caused by: Inoperability or incorrect operation of the system, 103 (233)

104 Inoperability or incorrect operation of the connections, transmission services or applications used to communicate between and the systems of the supplier or DSO, Inoperability or incorrect operation of the system that communicates with the of the supplier or DSO, A denialofservice attack from a party that is outside the scope of system use. For example, a disturbance in the delivery of a single DSO's data and a process disturbance can affect operation of the entire system and the completion of processes. The system support service model has three levels: 1. Level 1: The customer (consumer/company) contacts the supplier/dso's customer service/support. This also includes the actual portal used to process in, questions and guidance related to use. 2. Level 2: The main users/support persons designated by the supplier/dso contact Fingrid's support service if the disturbance cannot be resolved in Level 1 support. 3. Level 3: Fingrid's support service contacts the system application support service if the disturbance cannot be resolved in Level 2 support Reporting disturbances The system has a separate system for managing disturbances to which main users can report any disturbances that they observe. The company's main user classifies the severity of the disturbance (1 4). Fingrid's main user can edit the severity for the disturbance if necessary. Information about such a change goes to the person who reported the disturbance. If necessary, the main users can also use other methods to make contact about the disturbance. The main users of the companies can only see and follow the progress of disturbance clearance in relation to disturbances reported by their company. Severity classifications for disturbances: 1. System use is completely prevented or use of a single critical element is completely prevented. 2. System use is partially prevented and there is no alternative route that allows use or use of a single element is completely prevented. 3. A system disturbance interferes significantly with use but an alternative route allows use. 4. A system disturbance interferes slightly with use. 104 (233)

105 Oncall support The system's oncall support must be available at all levels on weekdays from 7 am 7 pm. Furthermore, disturbance clearance in a critical situation will continue until 10 pm in Level 3 support. After this, disturbance clearance will continue at 7 am on the next weekday. In the worst case scenario, the system would not be available during a long weekend. Oncall support at all three levels (including the support level for market parties) must be available at short notice to assist in disturbance clearance. The response time, or reaction to the problem, must be hour from the time of detecting and reporting the disturbance. After this, disturbance clearance and its eventual solution continues without interruption with support people from the different levels within the framework of the response times outlined above Scheduled service interruptions Users must be notified of scheduled service interruptions well before the planned interruption, in which case they can be performed each day between midnight 4/6 am. However, service interruptions cannot be done during the following limited times: At the turn of the year ( ), the beginning and end of the school years ( and ) At the turn of the month: The last three days and the first three days of each month On the first weekday of a week During the daytime 6 am midnight The parties associated with must stop data transmission between their own systems and the system during service interruptions or buffer the events in their own systems. 105 (233)

106 4 DESCRIPTION OF DATAHUB EVENTS 4.1 General will be built on a foundation consisting of different events (services). An event is a single interaction between the parties and, usually a request, notification or data update event comprising the steps presented in the figure below. Figure 40 A description of performing a event 1. The party initiates an event by making a change to its own system, which sends an event request to the interface. The request must include the required to perform the event. can also initiate an event. 2. validates the format, content and other eventspecific rules for the request it receives. If validation is unsuccessful, the event is interrupted and its progress moves to stage 5. The validation levels are described in more detail in the next section. 3. If necessary, processes in accordance with event specification (for example, various calculations). 4. The validated and any data possibly created or updated during processing is stored in the database. 5. The party initiating the event receives acknowledgement of the success or failure of the event. After receiving a failed acknowledgement, the party must correct the error and send the request again. 6. After a successful event, the is sent to a possible other party in accordance with the specifications. The other party may send a new request on the basis of the it receives, in which case the original event turns into a chain of several events, also known as a process. 106 (233)

107 In accordance with the description above, the following table is compiled for each event to describe performance of the event. Table 18 Example table for an event description and its progress with explanations Event description Definition Parties Event initiation Begins when Information to be reported Validation Rights to Rules Interrupting events Time limits Processing A definition of the event including the desired end result. The parties that are associated with the exchange related to the event (the party to which can be sent according to the rights is listed in brackets). A third party refers to a party authorised by the customer. Parties authorised by the operators can function in the roles of DSO and electricity supplier. A business event launches a event. At least the needed to successfully perform the event. The parties' rights to update and receive. Eventspecific validation rules that target content. Events that, when initiated, interrupt this event or events already in progress, which prevent performance of this event. Conditions for when an event must/can be initiated. A description of the processing performed by. Information storage Information reported Processed Return/relaying of Return of Relaying of Errors and cancellations Significant errors and consequences Cancellation conditions Information obtained directly from the parties and stored in. Information stored on the basis of processing. Information that is returned/acknowledged to the party initiating the event. Information that is transmitted to possible other parties to the event. Significant errors that may occur during an event, especially in the to be reported, and the possible consequences resulting from them. The conditions within the framework of which an event can be cancelled ( retrievals cannot be cancelled). 107 (233)

108 4.1.1 Validation A sequence of events in accordance with the above description can form more complicated processes, such as switching of supplier or moving processes. For the most part, the events will be automatically initiated when a party updates in its own system. Each party is responsible for ensuring that the is in the format required by. validates on three levels: syntax validation, data model validation, and eventspecific validation. Syntax validation refers to the general technical structure of exchange and validating the correctness of the format of the attributes included in the exchange. For example, syntax validation includes validation of the lengths of text fields. Data model validation refers to compliance with the dependence rules specified for the data model and checking the necessity of an attribute. Examples of such rules are that the accounting point identification must be unique and that the customer type (consumer or company) may not be changed. These validation rules are specified in a separate data model table (in the data standard). Eventspecific validation includes validation of compliance with certain business rules. Examples of these are checking the time limits or user rights for certain events, such as switching suppliers. The table above only contains these eventspecific validations Event cancellation and error correction It must be possible to correct that is reported incorrectly to. It is most important to ensure that no incorrect remains in for any time period. Information correction is done in different ways depending on the event being corrected. A separate cancellation notification is used when cancelling a request for accounting point creation or supplier's disconnection or connection request, and when cancelling agreement events. When updating all metering, accounting point, customer, product and invoice row and in the DSO's disconnection and connection notifications, incorrectly reported is corrected by means of new updating events and a separate cancellation is not made. In this case, the corrected must be reported using the same effective date as the incorrect was originally sent in order to prevent the wrong from remaining in. A separate cancellation notification includes a reference to the original notification that is now being cancelled. Situations in which other events have already been started on the basis of incorrect cause problems in cancellations. The main rule is that accounting point events can only be cancelled if the accounting point in question has not received updates from other parties after the arrival of the original notification. The cancellation rules in the agreement processes contain more details and these are described in conjunction with event descriptions. 108 (233)

109 4.1.3 Process map explanations The process maps linked to event descriptions summarise the events that are included in each process part. In the map, the events are not presented in order of performance; this is described in the process descriptions in section 3. If an event can be performed alone, it is not presented in the process images. Figure 41 Process map explanations 109 (233)

110 4.2 DH100 Customer and accounting point data maintenance processes Figure 42 Customer and accounting point data maintenance processes 110 (233)

111 4.2.1 DH110 Customer maintenance DH111 Customer update Table 19 Description of a customer update by the supplier Event description Definition Parties The supplier updates the customer in. Supplier,, (DSO), (3rd party). Event initiation Begins when Information to be reported A customer reports a change to the supplier, who updates the in its own system. Customer ; name, address, identity number/date of birth or business ID/association ID/VAT number, language code, contact ( , phone number, official postal address). Date when the changed takes effect. Validation Rights to Rules Interrupting events Time limits The supplier must have a contract with the customer that is either reported for the future, valid at the time, or has been terminated a maximum of six weeks earlier. The date it takes effect may not be in the past. The customer must be found in. None The customer's updated is exported to immediately after being updated in the supplier's system. Processing No processing Information storage Information reported Processed The customer reported by the supplier and about the date it takes effect. Old is stored in. No processing Return/relaying of Return of Relaying of Notification of a successful or rejected customer update. Changed customer is communicated to all parties that have agreements with the customer in question and to the third party with consideration to user rights. If the customer is private, the updated is only sent to the DSO. Errors and cancellations Significant errors and consequences The customer's address is incorrectly reported Possible mail (incl. invoices) is sent to the wrong address, especially if the agreement does not have a separate invoicing address. The customer's contact is incorrectly reported It is impossible to contact the customer. 111 (233)

112 Cancellation conditions Information is corrected by means of a new update. Sequence diagram 1 Customer update by the supplier 112 (233)

113 Class diagram 1 Updated and forwarded customer DH112 Customer update request Table 20 Description of a customer update by the DSO Event description Definition The DSO updates customer in its own system, which then notifies. If the customer in question only has a grid agreement in, the is updated directly to on the basis of the DSO's notification. If the customer has electricity sales agreements, the is sent to the accounting point supplier, which performs the actual update in because it is responsible for updating customer in. Parties Event initiation Begins when Information to be reported Validation Rights to Rules Interrupting events Time limits Processing DSO,, (Supplier). A customer reports a change in to the DSO and the DSO updates the in its own system. Customer ; name, address, identity number/date of birth or business ID/association ID/VAT number, language code, contact ( , phone number, official postal address); Date when the changed takes effect. The DSO must have a grid agreement with the customer in question. The customer is found in and the date the change takes effect may not be in the past. None The customer's updated is reported to immediately after being updated in the DSO's system. checks whether the customer has an electricity sales agreement (supplier with the rights to customer ). If it does not, updates the after receiving notification from the DSO. If it does have a contract, relays the to the supplier rather than storing it. 113 (233)

114 Information storage Information reported Processed Return/relaying of Return of Relaying of Errors and cancellations Changed customer and the date of the change if the customer only has a grid agreement. Old is stored in. No storage of processed. Notification of successful or rejected customer update or relay to supplier. The update request is relayed to the supplier that made the most recent agreement with the customer in question. Significant errors and consequences Cancellation conditions The customer's address is incorrectly reported Possible mail (incl. invoices) is sent to the wrong address, especially if the agreement does not have a separate invoicing address. The customer's contact is incorrectly reported It is impossible to contact the customer. None Sequence diagram 2 Customer update request by the DSO 114 (233)

115 Class diagram 2 Customer that can be updated 115 (233)

116 4.2.2 DH120 Accounting point data maintenance DH121 New accounting point Table 21 Description of accounting point creation Event description Definition Parties A DSO creates a new accounting point in. DSO,. Event initiation Begins when Information to be reported A DSO creates a new accounting point and enters the required by into its own system. Accounting point (necessity of the data depends on the status of the accounting point); address of the accounting point, and the metering grid area to which the accounting point belongs. Validation Rights to Rules Interrupting events Time limits No requirements. The accounting point identification may not exist in and the accounting point must be in the DSO's metering grid area. None The new accounting point must be reported as soon as the required has been stored in the DSO's own system. Processing No processing Information storage Information reported Processed All reported is stored in the database. No processing. Return/relaying of Return of Relaying of Notification of successful or rejected creation of an accounting point. The rejection message includes the reason for the rejection. None Errors and cancellations Significant errors and consequences The address of the accounting point is incorrectly reported or a faulty accounting point is created (for example, the accounting point does not exist) A contract is made for the wrong accounting point. Other accounting point data is incorrectly reported The supplier makes a contract with the customer on the wrong grounds (product/price list is 116 (233)

117 Cancellation conditions incorrect) An electricity sales agreement has not been made for the accounting point Sequence diagram 3 Information exchange for accounting point creation 117 (233)

118 Class diagram 3 Information required to create an accounting point 118 (233)

119 DH122 Accounting point data update Table 22 Description of an update of accounting point data by the DSO Event description Definition Parties Event initiation Begins when Information to be reported Validation Rights to Rules Interrupting events Time limits Processing No processing Information storage Information reported Processed The DSO reports an update of accounting point data. The update changes the basic accounting point data and the status of the accounting point. DSO,, (Supplier), (3rd party). A DSO makes changes to an accounting point and updates the in its own system and sends a notification of this to. The date when the changes take effect; accounting point data. The accounting point must be in the DSO's metering grid area. The accounting point must be found in and its status may not be "Removed from use" None The update must be reported as soon as the DSO makes the change in its own system. All reported is stored in the database. Previous accounting point data is stored in. No processing. Return/relaying of Return of Relaying of Errors and cancellations Significant errors and consequences Cancellation conditions Notification of a successful or rejected accounting point update. At least the changed is reported to the other parties associated with the accounting point with consideration to the parties' rights to. Information is incorrectly reported Suppliers and 3rd parties can make incorrect agreements with a customer or incorrect measures in, for example, imbalance settlement or load control. Information is corrected by means of a new update. 119 (233)

120 Sequence diagram 4 Information exchange for update of accounting point data 120 (233)

121 Class diagram 4 Information to be reported and forwarded during an accounting point update DH123 Accounting point deletion Table 23 Description of the deletion of an erroneous accounting point Event description Definition Parties Event initiation Begins when Information to be reported Validation Rights to A DSO permanently removes an accounting point from use, after which agreements can no longer be made for the accounting point. Accounting points that are used again (such as worksites) must not be deleted if the same accounting point identification will be used again later. DSO,. A DSO dismantles a connection or an accounting point is permanently removed from use for some other reason. The accounting point identification and date when the accounting point is removed from use. The accounting point is in the DSO's metering grid area. 121 (233)

122 Rules Interrupting events Time limits Processing None Information storage Information reported Processed The accounting point is found in and its status is "active" or "nonactive". The accounting point has valid agreements. Notification must be made as soon as the DSO updates the in its own system. The status of the accounting point is changed to "removed from use". None Return/relaying of Return of Relaying of Errors and cancellations Significant errors and consequences Cancellation conditions Notification of successful or rejected removal from use of an accounting point. Notification of removal from use of the accounting point is sent to any other agreement parties for the accounting point who have the rights to accounting point data. The DSO removes from use the wrong accounting point or removes from use the right accounting point on incorrect grounds Incorrect agreement terminations must be clarified after the fact. Information is corrected by means of a new update of the accounting point data. Sequence diagram 5 Information exchange when a DSO removes an accounting point from use 122 (233)

123 Class diagram 5 Information to be provided when removing an accounting point from use 123 (233)

124 DH124 Accounting point data update request Table 7 Description of an update to accounting point data made by the supplier Event description Definition Parties A supplier sends accounting point changes reported by the customer to the DSO. The DSO decides whether to change this in its own system and launches the actual update event on the basis of the supplier's notification. The purpose of this event is to ensure that certain accounting point data is as current as possible. Supplier,, (DSO). Event initiation Begins when Information to be reported A customer notifies the supplier of a change in accounting point data, after which the supplier relays about the change to the DSO via. The date that the changes take effect; the address of the accounting point; tax category, user group; estimate of annual use; controlled load; production device; storage device; freeform text/explanation: the customer's report/reason for the change in. Validation Rights to Rules Interrupting events Time limits The supplier must have the rights to the accounting point (a reported agreement that has not ended). The accounting point must be found in and its status may not be "removed from use". None As soon as the supplier learns about the changes. Processing No processing Information storage Information reported Processed No storage. No processing. Return/relaying of Return of Relaying of Notification of a successful or rejected relay of accounting point data. At least the changed must be reported to the DSO for the accounting point. Errors and cancellations Significant errors and consequences The user group is reported incorrectly Official reporting is incorrect. The annual use estimate is reported incorrectly Imbalance settlement 124 (233)

125 Cancellation conditions calculation contains a large deviation in comparison to actual use at reading metering sites. None Sequence diagram 6 Information exchange when a supplier reports a change in accounting point data Class diagram 6 Accounting point data for which a supplier can report changes to the DSO 125 (233)

126 4.2.3 DH130 Customer and accounting point data request DH131 Accounting point identification request Event description Definition Parties A supplier searches for an accounting point identification on the basis of an address. The supplier needs the accounting point identification so that it can find more detailed accounting point and customer in. New supplier / current supplier, Event initiation Begins when Information to be reported A supplier begins to make a new agreement with a customer. Accounting point address or part of it. Validation Rights to Rules Interrupting events Time limits Processing Information storage Information reported Processed Return/relaying of Return of Relaying of The basic for the accounting point in accordance with the class diagram presented below. The search retrieves a limited number of accounting points found on the basis of the address. No relayed. Errors and cancellations Significant errors and consequences Cancellation conditions 126 (233)

127 Sequence diagram 7 Information exchange when a supplier requests for accounting point ID Class diagram 7 Information to be provided when requesting an accounting point ID 127 (233)

128 Class diagram 8 Information returned when an accounting point identification is requested 128 (233)

129 DH132 Accounting point and customer request current supplier Event description Definition Parties Event initiation Begins when Information to be reported Validation Rights to Rules Interrupting events Time limits Processing Information storage Information reported Processed Return/relaying of Return of Relaying of Errors and cancellations Significant errors and consequences Cancellation conditions A supplier requests accounting point, customer and agreement for one of its own contracts. Current supplier,. The supplier checks the related to a specific accounting point in. The accounting point number for the accounting point and the supplier's own contract ID. The supplier must have a valid contract for the accounting point. The accounting point must be found in on the basis of the accounting point identification provided. Full accounting point data, electricity sales agreement, customer related to the electricity sales agreement, and about the grid service product. If several agreements are found with an accounting point IDagreement ID combination, the for all of these agreements is reported. 129 (233)

130 Sequence diagram 8 Information exchange when a supplier requests accounting point and customer Class diagram 9 Information to be provided when accounting point and customer is requested 130 (233)

131 Class diagram 10 Accounting point, customer and contract returned to the current supplier 131 (233)

132 DH133 Accounting point and customer request new supplier Event description Definition Parties A supplier requests the from about the accounting point, the customer, and the customer's contract situation at the accounting point that is needed to make a contract. New supplier,. Event initiation Begins when Information to be reported A supplier begins to make a new contract with a customer. The accounting point number for the accounting point, customer ID. If the agreement is made for several customers, the for all customers is reported. Validation Rights to Rules The new supplier must have authorisation from at least one customer of the accounting point. The accounting point must be found in on the basis of the accounting point identification provided. Interrupting events Time limits Processing Information storage Information reported Processed Return/relaying of Return of 1. The search retrieves customer about the customers that were entered and for whom the supplier has reported authorisation to. 2. The following about the accounting point is retrieved: a. the customer does not have a contract for the accounting point Basic accounting point data b. the customer has a contract for the accounting point Full accounting point 3. The following about the agreement situation at the accounting point is retrieved: a. The customer does not have a contract for the accounting point i. If an upcoming agreement termination has already been reported for the accounting point, this date is retrieved so that the supplier can agree on starting a 132 (233)

133 new agreement without a disconnection in delivery. ii. If a new moving in has already been reported for the accounting point, this date is retrieved so that the supplier can make a contract starting on the moving in date iii. Grid and electricity sales agreement : agreement fully with the customer/agreement partially with the customer/no agreement with the customer b. The customer has a contract for the accounting point in addition to the above, about the fixed term or an exceptional termination condition for the valid electricity sales agreement. The ending date of a fixed term is retrieved if it is a maximum of 90 days from the time of inquiry. Relaying of Errors and cancellations Significant errors and consequences Cancellation conditions Sequence diagram 9 Information exchange when a supplier requests accounting point and customer 133 (233)

134 Class diagram 11 Information to be provided when accounting point and customer is requested Class diagram 12 Accounting point, customer and agreement returned for the new supplier 134 (233)

135 DH134 Accounting point and customer request DSO Table 24 Description of accounting point data retrieval by a DSO Event description Definition Parties Event initiation Begins when Information to be reported Validation Rights to Rules Interrupting events Time limits Processing Information storage Information reported Processed A DSO retrieves accounting point data in order to perform various checks. In addition to accounting point data, the search retrieves about the accounting point customer and agreement if they exist. DSO,. Return/relaying of Return of Relaying of Errors and cancellations Significant errors and consequences Cancellation conditions A DSO wants to retrieve accounting point data for a certain time. Accounting point ID; the date for which retrieval is desired. The accounting point must be in the DSO's metering grid area. The accounting point is found in. Accounting point data, customer for the grid agreement, about the grid agreement, and about the accounting point supplier and sales products if the supplier has provided authorisation for product data. 135 (233)

136 Sequence diagram 10 Information exchange for DSO's accounting point data request Class diagram 13 Information to be provided when accounting point and customer is requested by DSO 136 (233)

137 Class diagram 14 Accounting point, customer and contract returned to the DSO 137 (233)

138 DH135 Accounting point and customer request 3rd party Table 25 Description of accounting point data request by a 3rd party Event description Definition Parties Event initiation Begins when Information to be reported Validation Rights to Rules Interrupting events Time limits Processing Information storage Information reported Processed Return/relaying of Return of Relaying of Errors and cancellations Significant errors and consequences Cancellation conditions A 3rd party retrieves accounting point and customer via authorisation. 3rd party,. A 3rd party needs customer and accounting point data in its customer service. Accounting point ID; customer ID; the date for which retrieval is desired. The 3rd party must have the rights to the via authorisation from the customer or another party. The accounting point is found in. Accounting point data and customer for the accounting point and about the grid service product. If more than one customer is linked to the agreement, customer is only retrieved for those customers for whom the party has authorisation. 138 (233)

139 Sequence diagram 11 Information exchange for accounting point data retrieval when a 3rd party requests 139 (233)

140 Class diagram 15 Accounting point and customer returned to a 3rd party 140 (233)

141 4.3 DH200 Metering data maintenance processes Figure 43 Metering data maintenance processes 141 (233)

142 4.3.1 DH211 Metering data report Table 26 Description of metering data report Event description Definition Parties Event initiation Begins when Information to be reported Validation Rights to Rules Interrupting events Time limits Processing Information storage Information reported Processed Return/relaying of Return of Relaying of Errors and cancellations Significant errors and consequences Cancellation conditions A party responsible for metering (the DSO for accounting points) reports the metering data for a metering point (accounting point, connection point or production unit) to. Metering responsible party,, (supplier), (DSO), (3rd party). The Metering responsible party has collected and validated the metering data and reports it to. Metering pointspecific metering data (incl. metering point identification), metering data interval. The metering point belongs to the metering grid area and metering responsibility of the metering responsible party. Validation of metering pointspecific metering (see ); the metering point is found in ; the reported interval is not in the future and not more than six years in the past. No (the time limits in section must be observed, but corrections are permitted throughout the storage period for the metering data). The metering data for the metering points and the interval that applies to the metering data. Positive or negative acknowledgement for each metering point. New and changed metering data for complete days is relayed to the suppliers and 3rd parties that have the rights to the. Possible metering errors and subsequent balance errors are processed in accordance with section and section 3.6. Metering data is corrected by means of a new notification event. 142 (233)

143 Sequence diagram 12 Information exchange in metering report 143 (233)

144 Class diagram 16 Information provided in the DSO's metering data report 144 (233)

145 4.3.2 DH212 Reminder of metering data report Table 27 Description of a reminder about a metering data report Event description Definition Parties Event initiation Begins when Information to be reported Validation Rights to notifies the metering responsible party regarding incorrect or unreported metering data (the DSO for accounting points)., metering responsible party. Deficiencies in the DSO's metering data are observed in 's daily validations. reports the interval and metering point identification on a time series basis for those metering points for which the metering data is incorrect or deficient. The DSO is responsible for metering. Rules In accordance with section Interrupting events Time limits In accordance with section Processing Information storage Information reported Processed Return/relaying of Return of Relaying of Errors and cancellations Significant errors and consequences Cancellation conditions requires acknowledgement from the DSO. 145 (233)

146 Sequence diagram 13 Information exchange in a reminder about metering data Class diagram 17 Information content of the reminder sent to a DSO 146 (233)

147 4.3.3 DH220 Metering data request Table 28 Description of metering data retrieval Event description Definition Parties Event initiation Begins when Information to be reported Validation A supplier retrieves metering data for which it has rights from. Supplier/DSO/3rd party,. In addition to the fact that relays all of the DSO's new and changed metering data that the supplier is entitled to, a party has a need for separate metering data retrieval. If desired, a retrieval can be restricted on the basis of metering grid area, accounting point, connection point or production unit ID; interval; unit and time step in which the data is retrieved. Rights to In accordance with section 2.2. Rules Interrupting events Time limits Processing Modification of a unit and/or time step from an internal unit to a unit and time step requested by the supplier. In the retrieved, the time step can at its shortest be a time step stored in for the metering point. Metering data retrieval is implemented asynchronously due to the large data mass. prioritises synchronous calls ahead of the retrieval, and metering data retrieval is processed in the background. The duration of processing depends on the amount of data retrieved. Information storage Information reported Processed Return/relaying of Return of Forwarding of Errors and cancellations Significant errors and consequences The metering data for the retrieved metering points or rejection of retrieval. 147 (233)

148 Cancellation conditions Sequence diagram 14 Information exchange in metering data request Class diagram 18 Information to be provided for metering data request 148 (233)

149 Class diagram 19 Information returned by metering data retrieval 149 (233)

150 4.4 DH300 Contract processes Figure 44 Agreement processes 150 (233)

151 4.4.1 DH310 Contract creation DH311 Notification of a new contract Table 29 Description of notification of a new contract to the accounting point Event description Definition Parties A supplier reports a new electricity sales agreement, which it has signed with a customer for the customer's accounting point. New grid agreement is created in if necessary, and the DSO receives about the new agreement. New supplier / current supplier,, (DSO), (current supplier) Event initiation Begins when Information to be reported A customer signs a new agreement with a supplier for the customer's existing or a new accounting point. Accounting point identification, customer and agreement, including agreementspecific invoicing addresses and contact person. Validation Rights to Rules Interrupting events The accounting point is found in and has not been removed from use. The notification will not be approved if the customer has agreements for the accounting point stored in, and a new agreement cannot be made if: The accounting point has a valid, fixedterm sales agreement and the agreement includes one of the same customers as in the new agreement notification (the starting date must be later than the final date of the fixed term of the earlier agreement if such an agreement exists). The valid agreement for the accounting point has an exceptional termination condition and the agreement includes one of the same customers as in the new agreement notification and the dates of the exceptional termination condition do not permit a new agreement for the accounting point. These rules can be deviated from if the current supplier reports a new agreement for the accounting point that includes one of the same customers as in the valid agreement for the accounting point. A previously reported electricity sales agreement with the same agreement starting date for the same accounting point. 151 (233)

152 Time limits If one of the customers reported by the supplier for the new agreement have an electricity sales or grid agreement at the accounting point or is a party in some agreement, the notification must be sent 14 days prior to the starting date of the agreement at the latest (change of supplier situation). If the customer or customers do not have valid agreements (sales and/or grid agreement) for the accounting point or the customer is one of the parties in an agreement, the notification must be sent during the starting date for the agreement being reported at the latest (moving in situation). If there is no valid agreement for the accounting point at the time of notification ("without supplier" status), the notification can still be sent during the starting date of the agreement being reported. At the earliest, the notification can be sent 90 days prior to the starting date of the agreement being reported. Processing Creating a customer Terminating a current agreement Creating a grid agreement Processing a start retroactively If the customer for a contract being reported is not found in, it is created in. terminates the valid agreement for the current supplier at the accounting point on the day preceding the starting date of the new agreement. If a new grid agreement is needed, creates the for the new grid agreement (starting date same as for the sales agreement, grid agreement status "unconfirmed"). In conjunction with creating a new grid agreement, terminates the valid grid agreement on the preceding day. Rules for conclusion: Responsibility for agreements does not change (the same customer or customers are responsible for the new agreement as for the agreement valid at the time of reporting), which is a case of a simple switching of suppliers or a new agreement with the current supplier A new grid agreement is not needed. The responsibility for agreements changes (one or more agreement party changes, parties are added or removed) A new grid agreement is needed in order to make the same customers responsible for the agreements. At the time of notification, the grid agreement is already in the name of the customer making a new agreement, but the sales agreement customer changes A new grid agreement is not needed. The agreement valid at the time of notification is a comprehensive delivery agreement and the new agreement is not. The DSO must confirm the new agreement A new grid agreement is needed. A sales agreement reported as beginning retroactively is processed according to section 152 (233)

153 Terminating a reported agreement If a supplier reports a new agreement so that after the starting date of the agreement the same accounting point has a sales agreement beginning that was reported earlier and registered under the reason "moving in", will automatically terminate the agreement reported by the new supplier on the last day of the fixed term reported by the new supplier. will notify the new supplier of termination of the new agreement by means of a message in compliance with DH Information storage Information reported Processed New sales agreement is created on the basis of the reported and linked to the accounting point indicated in the notification. The customer contained in the notification is updated in the customer. The end date of the current sales agreement and the reason for agreement termination The end date of the current grid agreement and the reason for termination if the customers change. Information about the created grid agreement (status="unconfirmed"). Information about the created new customer. Return/relaying of Return of Relaying of Notification of successful or rejected notification. If the notification is successful, the reason for the new agreement registered in is returned (moving in, switching suppliers, and change of agreement). Agreement rejection includes about the reason for rejection. A possible current accounting point supplier is notified of the termination of the current sales agreement. The DSO for the accounting point is notified of the new grid agreement if a grid agreement is created in the process. In other cases, the DSO receives about the new sales agreement at the accounting point. If notification of a new sales agreement updates the of a customer already in, the updated is relayed to all parties with rights to the. Errors and cancellations Significant errors and consequences Cancellation conditions A sales agreement is reported for the wrong accounting point A customer's current agreement is terminated at the wrong accounting point without cause. Prior to the starting date of the agreement. Cancellation of a valid agreement is handled in accordance with section (233)

154 Sequence diagram 15 Information exchange when a supplier reports a new sales agreement 154 (233)

155 Class diagram 20 Information content for notification of a new sales agreement 155 (233)

156 Class diagram 21 Information about a new agreement forwarded to the DSO 156 (233)

157 DH312 Grid agreement confirmation Table 30 Description of grid agreement confirmation Event description Definition Parties A DSO confirms a new grid agreement in. Information about the grid agreement is relayed to the supplier. DSO,, (current supplier). Event initiation Begins when Information to be reported A DSO has received about a new grid agreement created in, after which it uses this to create a new agreement in its own system and confirms this to. Accounting point identification, grid agreement including agreementspecific invoicing addresses and contact person, (the supplier's event reference). Validation Rights to Rules Interrupting events Time limits The accounting point is found in and has not been removed from use. The accounting point sales agreement has been cancelled. The DSO must confirm the grid agreement as quickly as possible. Processing Terminating a current agreement terminates the valid grid agreement on the day preceding the starting date of the new agreement. Information storage Information reported Processed Grid agreement. The ending date of the current grid agreement. Information about the new grid agreement (status="confirmed"). Return/relaying of Return of Relaying of Notification of successful or rejected notification. Grid agreement to the accounting point supplier. Errors and cancellations Significant errors and consequences Cancellation conditions Prior to the agreement taking effect. 157 (233)

158 Sequence diagram 16 Information exchange when a DSO confirms a grid agreement Class diagram 22 Information content for a grid agreement confirmation 158 (233)

159 4.4.2 DH320 Contract update DH321 Sales agreement update Table 31 Description of updating sales agreement Event description Definition Parties Event initiation Begins when Information to be reported Validation Rights to Rules Interrupting events Time limits Processing No processing Information storage Information reported Processed Return/relaying of Return of Relaying of Errors and cancellations Significant errors and consequences Cancellation conditions A supplier updates agreement in. Supplier,, (DSO). A supplier makes changes to an existing sales agreement. Accounting point identification, agreement changes, date the change takes effect. A sales agreement is a supplier agreement. The accounting point is found in and is not removed from use. This notification may not be used to report the starting and ending dates of the agreement, instead they must be corrected by first sending a cancellation and then a new agreement notification. The changed agreement. Notification of successful update. The updated is relayed to the DSO (if desired, the DSO updates the in its own system). Information is corrected by means of a new update. 159 (233)

160 Sequence diagram 17 Information exchange when a supplier updates sales agreement Class diagram 23 Information content for an update of sales agreement 160 (233)

161 DH322 Grid agreement update Table 32 Description of updating grid agreement Event description Definition Parties Event initiation Begins when Information to be reported Validation Rights to Rules Interrupting events Time limits Processing No processing Information storage Information reported Processed Return/relaying of Return of Relaying of Errors and cancellations Significant errors and consequences Cancellation conditions A DSO updates grid agreement in. DSO,, (supplier). A DSO makes changes to an existing grid agreement. Accounting point identification, agreement changes, date the change takes effect. The accounting point is in the DSO's metering grid area. The accounting point is found in and is not removed from use. This notification may not be used to report the starting and ending dates of the agreement, instead they must be reported by means of a new agreement notification. The changed agreement. Notification of successful update. The changed agreement is relayed to the supplier. Information is corrected by means of a new update. 161 (233)

162 Sequence diagram 18 Information exchange when a DSO updates grid agreement Class diagram 24 Information content for a grid agreement update 162 (233)

163 DH323 Notification of an accounting point without a supplier Table 33 Description of the notification of an accounting point without a supplier Event description Definition Parties Event initiation Begins when Information to be reported Validation Rights to Rules Interrupting events Time limits Processing Information storage Information reported Processed notifies the DSO of an accounting point without a supplier so that the DSO can terminate its own agreement and/or disconnect the electricity at the accounting point if desired., DSO. Return/relaying of Return of Relaying of Errors and cancellations Significant errors and consequences Cancellation conditions Whenever 's internal processing finds an accounting point that does not have a valid sales agreement but the accounting point status is connected. Notification is sent on a daily basis if necessary. Accounting point identification, date in the past from which the accounting point has been without a supplier and the accounting point status is "connected". The accounting point is in the DSO's metering grid area. The DSO must acknowledge the notification as received. 163 (233)

164 Sequence diagram 19 Information exchange when notifies the DSO of an accounting point without a supplier Class diagram 25 Information content for notification of an accounting point without a supplier 164 (233)

165 4.4.3 DH330 Contract termination DH331 Notification of sales agreement end Table 34 Description of notification of the ending of a sales agreement Event description Definition Parties A supplier reports the ending of a sales agreement to. Supplier,, (DSO). Event initiation Begins when Information to be reported A supplier terminates a sales agreement after a customer reports moving out, a customer wants to terminate its sales agreement with the supplier or the supplier has terminated a customer's agreement, or the supplier receives a DSO's moving out notification from. The ending date of the agreement, possible final invoicing address, and the reason for the ending of the agreement (moving out, dissolving of a contract, termination of a contract). Validation Rights to Rules The agreement that is being ended must be valid at the time of notification. Interrupting events Time limits The reason is "Moving out" or "Dissolving": The day in progress 90 days onward. The reason is "Termination": days onward. Processing Retroactive termination If a contract is terminated retroactively, the balance data for the accounting point is recorded until the end of the day of termination. Information storage Information reported Processed The ending date of the sales agreement, possible final invoicing address and the reason for ending the agreement. Balance data for the accounting point when retroactively terminated. Return/relaying of Return of Relaying of Information about a successful event or rejected notification. If a grid agreement is valid, the DSO is notified of the ending of a sales agreement, the possible final invoicing address and the reason for ending the agreement. 165 (233)

166 Errors and cancellations Significant errors and consequences Cancellation conditions The wrong agreement is terminated The DSO may disconnect electricity at the wrong accounting point and errors have to be corrected. The notification must be cancelled on the termination date at the latest. Sequence diagram 20 Information exchange when a supplier reports the ending of a sales agreement 166 (233)

167 Class diagram 26 Information content for notification of the ending of a sales agreement DH332 Notification of customer moving out by new supplier Table 35 Description of notification by the new supplier about the moving out of a customer Event description Definition Parties Event initiation Begins when Information to be reported Validation Rights to Rules Interrupting events Time limits Processing The new supplier for a customer notifies the DSO of the customer's moving out to the current accounting point. New supplier,, (DSO). A customer requests its new supplier to provide notification of moving out from the current accounting point. Accounting point identification, customer's unique identifier and name, moving out day, invoicing address for final invoice. The accounting point can be found and is not removed from use, and the customer has a sales and grid agreement for the accounting point. The day in progress 90 days onward. 167 (233)

168 Information storage Information reported Processed Return/relaying of Return of Relaying of Errors and cancellations Significant errors and consequences Cancellation conditions Information about successful notification of. The reported is relayed to the DSO for the accounting point, which reports the actual moving out in accordance with section Sequence diagram 21 Information exchange when a new supplier reports a customer moving out 168 (233)

169 Class diagram 27 Information content for a moving out notification made by a new supplier 169 (233)

170 DH333 Notification of grid agreement end Table 36 Description of notification of the ending of a grid agreement Event description Definition Parties A DSO reports the ending of a grid agreement to. DSO,, (supplier). Event initiation Begins when Information to be reported A DSO terminates a grid agreement when a customer reports moving out to the DSO or a DSO terminates a grid agreement after receiving notification from that a supplier has terminated a sales agreement or otherwise cancels a grid agreement. The ending date of the agreement and the reason for the ending of the agreement (moving out, termination, dissolving), an invoicing address for the final invoice. Validation Rights to Rules The accounting point is in the DSO's metering grid area. The agreement that is being terminated must be valid at the time of notification. The accounting point is found in and is not removed from use. Rules for termination in accordance with the grid service terms. Interrupting events Time limits The day in progress 90 days. Processing No processing Information storage Information reported Processed The ending date of the grid agreement, possible final invoicing address and the reason for the ending of the agreement. Return/relaying of Return of Relaying of Information about a successful event or rejected notification. If a sales agreement is valid, the supplier is notified of the ending of a grid agreement, the possible final invoicing address and the reason for the ending of the agreement. Errors and cancellations Significant errors The wrong agreement is terminated Errors have to be corrected. 170 (233)

171 and consequences Cancellation conditions The notification must be cancelled on the ending date at the latest. Sequence diagram 22 Information exchange when a DSO reports the ending of a grid agreement 171 (233)

172 Class diagram 28 Information content for a notification of the ending of a grid agreement 172 (233)

173 4.4.4 DH340 Contract cancellation DH341 Notification of sales agreement cancellation Table 37 Description of the notification of the cancellation of a sales agreement Event description Definition Parties Event initiation Begins when Information to be reported Validation Rights to Rules A supplier reports the cancellation of a sales agreement at the accounting point. New supplier,, (DSO), (previous supplier). A customer notifies the supplier that it is cancelling a sales agreement on the basis of its statutory right of cancellation or a supplier or customer notices an incorrectly reported sales agreement. Accounting point identification, agreement identification, the starting date of the agreement being cancelled, possible explanation of the reason for cancellation, cancellation reason code (cancellation by customer/supplier). The supplier has reported an earlier sales agreement that it is cancelling. The agreement being cancelled is valid at the time of cancellation. Interrupting events Time limits Processing Agreement and balance data for the accounting point are registered in accordance with section Information storage Information reported Processed Return/relaying of Return of Relaying of Errors and cancellations Significant errors and consequences The agreement situation and balance data for the accounting point are registered in accordance with section Information about a successful reception of the notification or a rejected notification. Cancellation for the sales agreement is relayed to the DSO. A possible previous supplier for the accounting point is notified of cancellation of the ending of its sales agreement. The cancellation message is sent for the wrong accounting point and agreement The customer's experience may be poor and the matter will 173 (233)

174 Cancellation conditions have to be clarified by . The notification cannot be cancelled. Sequence diagram 23 Information exchange for sales agreement cancellation Class diagram 29 Information content for notification of a sales agreement cancellation 174 (233)

175 DH342 Notification of grid agreement cancellation Table 38 Description of notification of a cancellation of a grid agreement Event description Definition Parties Event initiation Begins when Information to be reported Validation Rights to Rules A DSO reports the cancellation of a grid agreement. DSO,, (supplier). A DSO has received cancellation for a sales agreement and the DSO cancels the grid agreement made on the basis of this sales agreement or the DSO notices confirmation of an incorrect grid agreement. Accounting point identification, agreement identification, the starting date of the agreement being cancelled, possible explanation of the reason for cancellation, cancellation reason code (cancellation by customer/supplier). The agreement being cancelled belongs to the DSO. The agreement being cancelled is valid at the time of cancellation. Interrupting events Time limits Processing The grid agreement is cancelled in the system and a possible previous grid agreement is restored to valid status if this has been decided in an automatically cancelled agreement process. Information storage Information reported Processed Return/relaying of Return of Relaying of Errors and cancellations Significant errors and consequences Cancellation conditions Grid agreement cancellation and possible restoration of the valid status of a previous grid agreement. Information about successful reception of the notification or a rejected notification. Grid agreement cancellation is relayed to the supplier to which the grid agreement confirmation (DH312) was originally relayed. The cancellation message is sent for the wrong accounting point and agreement The customer's experience may be poor and the matter will have to be clarified by . The notification cannot be cancelled. 175 (233)

176 Sequence diagram 24 Information exchange for a cancellation of a grid agreement Class diagram 30 Information content for notification of a cancellation of a grid agreement 176 (233)

177 DH343 Notification of Refusal of Sales Agreement Restore by Former Supplier Table 39 Description of refusal to restore a sales agreement Event description Definition Parties Event initiation Begins when Information to be reported Validation Rights to Rules A supplier reports to regarding the termination of a sales agreement that was restored in a cancellation process. Previous supplier,, (DSO). The supplier receives that a sales agreement termination has been cancelled but does not want to continue sales to the accounting point and customer in question. Information corresponding to the notification of the ending of an agreement DH331. The restored terminated agreement belongs to the supplier making the notification. The termination date can be the ongoing day at the earliest. Interrupting events Time limits Processing On the weekday following reception of "DH3413 Relaying of sales agreement cancellation to the previous supplier" message at the latest. Agreement and balance data for the accounting point are registered in accordance with section Information storage Information reported Processed Return/relaying of Return of Relaying of Errors and cancellations Significant errors and consequences stores the sales agreement termination. Agreement and balance data for the accounting point are registered in accordance with section Information about successful reception of the notification or a rejected notification. The sales agreement termination is reported to the DSO. The supplier accidentally terminates a contract that it would have wanted to continue If necessary, the supplier contacts the customer and reports a new sales agreement to. 177 (233)

178 Cancellation conditions Cannot be cancelled. Sequence diagram 25 Information exchange in a situation in which the previous supplier does not take the accounting point back into its sales Class diagram 31 Information content for the previous supplier's refusal to restore service (equivalent to termination of a contract in a normal situation) 178 (233)

179 DH344 Notification of Grid Agreement End In the Case of Cancellation Table 40 Description of the ending of a grid agreement in a cancellation situation Event description Definition Parties Event initiation Begins when Information to be reported Validation Rights to Rules Interrupting events Time limits Processing Information storage Information reported Processed Return/relaying of Return of Relaying of Errors and cancellations Significant errors and consequences Cancellation conditions A DSO reports the ending of a grid agreement in a cancellation process. DSO,, (supplier). A DSO terminates its grid agreement on the basis of a DH3432 message received from a supplier. Information corresponding to notification of the ending of an agreement DH333. The grid agreement belongs to the DSO. stores the sales agreement termination. Information about successful reception of the notification or a rejected notification. Termination for the grid agreement is relayed to the accounting point supplier for which the grid agreement was confirmed earlier by means of a DH3121 message. The grid agreement is incorrectly terminated The situation can require clarification by and telephone. Prior to storage of the new grid agreement or grid agreement outline for the accounting point. 179 (233)

180 Sequence diagram 26 Information exchange during notification of the ending of a grid agreement in a sales agreement cancellation situation Class diagram 32 Information content for notification of the ending of a grid agreement in a sales agreement cancellation situation (equivalent to notification of the ending of a grid agreement in a normal situation) 180 (233)

181 4.5 DH400 Connection and disconnection processes Figure 45 Connection and disconnection processes 181 (233)

182 4.5.1 DH410 Connection DH411 Supply connection request Table 41 Description of a supplier's supply connection request Event description Definition Parties Event initiation Begins when Information to be reported Validation Rights to Rules Interrupting events Time limits Processing A supplier reports a request for accounting point supply connection to. Supplier,, (DSO). A supplier asks the DSO to connect supply when a customer pays an overdue invoice or corrects some other violation of the agreement. Date of connection, accounting point status (="disconnected"), accounting point ID. The supplier must have a valid sales agreement for the accounting point at the time the request is made and on the date of connection. The accounting point is not in "removed from use" status. The connection date for the connection request may not be in the past. Information storage Information reported Processed Return/relaying of Return of Relaying of Notification of successful or rejected connection request. The connection request is relayed to the DSO for the accounting point. Errors and cancellations Significant errors and consequences The connection request is reported for the wrong accounting point or the wrong day Depending on the DSO's business processes, the DSO contacts the customer unnecessarily in order to ensure safe connection. Cancellation Cancellation must be done prior to the DSO's notification in section (233)

183 conditions Sequence diagram 27 Information exchange when a supplier requests supply connection Class diagram 33 Information to be reported when a supplier requests supply connection 183 (233)

184 DH412 Notification of supply connection Table 42 Description of a DSO's notification of supply connection Event description Definition Parties Event initiation Begins when Information to be reported Validation Rights to Rules Interrupting events Time limits Processing No processing Information storage Information reported Processed Return/relaying of Return of Relaying of The DSO reports the electricity reconnection at the accounting point to. DSO,, (supplier), (3rd party). A distribution grid owner connects the electricity at the accounting point when renovation work at the accounting point is completed the customer pays an overdue invoice to the distribution grid owner Customer asks the DSO to connect the electricity. The time of connection to an accuracy of one hour, connection status of the accounting point (="connected"), accounting point ID. The accounting point is in the DSO's metering grid area. The accounting point status is not "removed from use". Connection must be reported to immediately after connection when the is available in the DSO's system. If, for example, the for manually connected sites is not available immediately after connection, the notification must in these cases be sent to within one week of when the customer's electricity supply has been connected if the customer's annual estimate is less than 1 GWh and, at the latest, on the following working day after connection for a customer with consumption of 1 GWh or more per year. Information about connection is still accepted after this period but there will be intervention in the case of notifications that are sent late on a repetitive basis. All reported is stored. Notification of successful or rejected notification. A change in accounting point connection status is reported to the possible 184 (233)

185 Errors and cancellations Significant errors and consequences Cancellation conditions supplier and/or 3rd party. Connection is reported for the wrong accounting point or otherwise incorrectly Depending on the supplier's business processes, the supplier may unnecessarily contact the customer or initiate other extra clarification. An incorrect notification is corrected by a disconnection notification for the same time. 185 (233)

186 Sequence diagram 28 Information exchange when a DSO reports supply connection Class diagram 34 Information to be reported for supply connection by a DSO 186 (233)

187 DH413 Notification of connection delay Table 43 Description of notification of connection delay Event description Definition Parties A DSO responds to a connection request by indicating that the measure is not possible on the requested date. DSO,, (supplier). Event initiation Begins when Information to be reported A DSO cannot implement connection on the date requested by the supplier. Accounting point ID; possible reason why the measure cannot be implemented on the requested date or that the measure cannot be performed at all at the accounting point; Possible date when the measure can be performed at the earliest. Validation Rights to The accounting point must be in the DSO's metering grid area. The supplier must have a valid agreement for the accounting point. Rules Interrupting events Time limits A section notification cannot have been made for the original request. At the latest, on the weekday following the connection date requested by the supplier, if a section notification has not yet been made for the request in question. Processing Information storage Information reported Processed Return/relaying of Return of Relaying of Notification of successful or rejected notification. The reported by the DSO is relayed to the supplier that sent the request. Errors and cancellations Significant errors and consequences Cancellation conditions 187 (233)

188 Sequence diagram 29 Information exchange for a delayed connection Class diagram 35 Information reported in the DSO's notification of connection delay 188 (233)

189 4.5.2 DH420 Disconnection DH421 Supply disconnection request Table 44 Description of a supplier's supply disconnection request Event description Definition Parties Event initiation Begins when Information to be reported Validation Rights to Rules Interrupting events Time limits Processing A supplier reports a request for accounting point delivery disconnection to. Supplier,, (DSO). A supplier asks the DSO to disconnect delivery when a customer fails to pay the supplier's invoices or otherwise violates the agreement Date of disconnection, accounting point status (="disconnected"), accounting point ID. The supplier must have a valid sales agreement for the accounting point at the time the request is made and on the date of disconnection. The accounting point is not in "removed from use" status. The request must be reported at least one week prior to the desired disconnection date. From the day following the requested disconnection date, electricity use at the accounting point is calculated to the DSO's balance (electricity use is once again calculated to the supplier's balance after the date of the connection notification). Information storage Information reported Processed Return/relaying of Return of Relaying of Errors and cancellations Significant errors and consequences Balance data for the accounting point. Notification of successful or rejected disconnection notification. The disconnection request is relayed to the DSO for the accounting point. The disconnection request is reported for the wrong accounting point or the wrong day The DSO disconnects the customer's delivery on the wrong 189 (233)

190 Cancellation conditions grounds (consequences are equivalent to an unexpected electricity outage). Cancellation must be done prior to the DSO's notification in section Sequence diagram 30 Information exchange when a supplier requests supply disconnection Class diagram 36 Information to be reported when a supplier requests supply disconnection 190 (233)

191 DH422 Notification of supply disconnection Table 45 Description of a DSO's notification of supply disconnection Event description Definition Parties Event initiation Begins when Information to be reported Validation Rights to Rules Interrupting events Time limits Processing Information storage Information reported Processed Return/relaying of Return of Relaying of Errors and cancellations Significant errors and consequences The DSO reports the electricity disconnection at the accounting point to. DSO,, (supplier), (3rd party). A DSO disconnects the electricity at the accounting point when, for example, the accounting point has no supplier renovation work is being performed at the accounting point a customer fails to pay the DSO's invoices the customer asks the DSO to disconnect the electricity. The time of disconnection to an accuracy of one hour, connection status of the accounting point (="disconnected"), accounting point ID. The accounting point is in the DSO's metering grid area. The accounting point status is not "removed from use". The disconnection must be reported to immediately after disconnection and as soon as the is available from the DSO's system. If, for example, the for manually disconnected sites is not available immediately after disconnection, the notification must in these cases be sent to within one week of when customer's electricity delivery has been disconnected if the customer's annual estimate is less than 1 GWh and, at the latest, on the following working day after disconnection for a customer with consumption of 1 GWh or more per year. Information about disconnection is still accepted after this period but there will be intervention in the case of notifications that are sent late on a repetitive basis. All reported is stored. Notification of successful or rejected notification. A change in accounting point connection status is reported to the possible supplier and/or 3rd party. Disconnection is reported for the wrong accounting point or otherwise incorrectly Depending on the supplier's business processes, the supplier may unnecessarily contact the customer or initiate other extra clarification. 191 (233)

192 Cancellation conditions An incorrect notification is corrected by a connection notification for the same time. Sequence diagram 31 Information exchange when a DSO reports about supply disconnection Class diagram 37 Information to be reported for supply disconnection by a DSO 192 (233)

193 DH423 Notification of disconnection delay Table 46 Description of notification of connection or disconnection delay Event description Definition Parties A DSO responds to a disconnection request by indicating that the measure is not possible on the requested date. DSO,, (supplier). Event initiation Begins when Information to be reported A DSO cannot implement disconnection on the date requested by the supplier. Accounting point ID; possible reason why the measure cannot be implemented on the requested date or that the measure cannot be performed at all at the accounting point; Possible date when the measure can be performed at the earliest. Validation Rights to The accounting point must be in the DSO's metering grid area. The supplier must have a valid agreement for the accounting point. Rules Interrupting events Time limits A section notification cannot have been made for the original request. At the latest, on the weekday following the connection or disconnection date requested by the supplier, if a section notification has not yet been made for the request in question. Processing Information storage Information reported Processed Return/relaying of Return of Relaying of Notification of successful or rejected notification. The reported by the DSO is relayed to the supplier that sent the request. Errors and cancellations Significant errors and consequences Cancellation 193 (233)

194 conditions Sequence diagram 32 Information exchange for a connection or disconnection delay Class diagram 38 Information reported in the DSO's notification of connection or disconnection delay 194 (233)

195 4.6 DH500 Imbalance settlement Figure 46 Imbalance settlement processes 195 (233)

196 4.6.1 DH510 Imbalance settlement data calculation and reporting DH514 Imbalance settlement data report to DSO Table 47 Description of imbalance settlement data report to DSO Event description Definition Parties Event initiation Begins when Information to be reported Validation Rights to Rules Interrupting events Time limits Processing Information storage Information reported Processed reports the imbalance settlement data that it has calculated to the DSO., DSO. Return/relaying of Return of Relaying of Errors and cancellations Significant errors and consequences Cancellation conditions has calculated the imbalance settlement data and received the results of balance deviation calculation for the metering grid areas from the esett system. Imbalance settlement data for each metering grid area, data interval (the first day that the balance window is closed the previous day). The metering grid area belongs to the DSO. The DSO must acknowledge the data as received. 196 (233)

197 Sequence diagram 33 Information exchange for imbalance settlement data report to DSO Class diagram 39 Information content of the imbalance settlement data reported to a DSO 197 (233)

198 DH515 Imbalance settlement data report to supplier Table 48 Description of notification of imbalance settlement data to the supplier Event description Definition Parties Event initiation Begins when Information to be reported Validation Rights to Rules Interrupting events Time limits Processing Information storage Information reported Processed Return/relaying of Return of Relaying of Errors and cancellations Significant errors and consequences Cancellation conditions reports the imbalance settlement data that it has calculated to the supplier., supplier. has calculated the imbalance settlement data and received the results of balance deviation calculation for the metering grid areas from the esett system. Imbalance settlement data for each metering grid area, data interval (the first day that the balance window is closed the previous day). The supplier has imbalance settlement data for the period. The supplier must acknowledge the data as received. 198 (233)

199 Sequence diagram 34 Information exchange for imbalance settlement data report to supplier Class diagram 40 Information content of the imbalance settlement data reported to a supplier 199 (233)

200 4.6.2 DH520 Imbalance settlement data request DH521 Imbalance settlement data request supplier Table 49 Description of imbalance settlement data request by a supplier Event description Definition Parties Event initiation Begins when Information to be reported Validation Rights to Rules Interrupting events Time limits Processing Information storage Information reported Processed Return/relaying of Return of Relaying of Errors and cancellations Significant errors and consequences Cancellation conditions A supplier retrieves imbalance settlement data from. Supplier,. A supplier needs imbalance settlement data from for its activities. Metering grid area identification, data interval. The supplier has imbalance settlement data for the metering grid area and interval being retrieved. The retrieval interval is not in the future. Supplier's imbalance settlement data for the metering grid area. 200 (233)

201 Sequence diagram 35 Information exchange when a supplier retrieves imbalance settlement data Class diagram 41 Information provided by the supplier for imbalance settlement data request 201 (233)

202 Class diagram 42 Information returned to the supplier in imbalance settlement data retrieval 202 (233)

203 DH522 Imbalance settlement data request DSO Table 50 Description of imbalance settlement data retrieval by a DSO Event description Definition Parties Event initiation Begins when Information to be reported Validation Rights to Rules Interrupting events Time limits Processing Information storage Information reported Processed A DSO retrieves imbalance settlement data from., DSO. Return/relaying of Return of Relaying of Errors and cancellations Significant errors and consequences Cancellation conditions A DSO needs imbalance settlement data from in its activities, for example, to check results. Data interval, data being retrieved (metering grid area and/or supplierlevel totals). The metering grid area belongs to the DSO. The retrieval interval is not in the future. Supplier and/or DSO imbalance settlement data for the metering grid area. 203 (233)

204 Sequence diagram 36 Information exchange when a DSO retrieves imbalance settlement data Class diagram 43 Information provided by the DSO for imbalance settlement data request 204 (233)

205 Class diagram 44 Information returned to the DSO in imbalance settlement data retrieval 205 (233)

206 DH523 Consumption and production registered in losses request Table 51 Description of retrieval of consumption and production registered as losses Event description Definition Parties Event initiation Begins when Information to be reported Validation Rights to Rules Interrupting events Time limits Processing Information storage Information reported Processed A DSO retrieves from concerning consumption and production recorded as losses at accounting points. DSO,. Return/relaying of Return of Relaying of Errors and cancellations Significant errors and consequences Cancellation conditions A DSO needs from concerning consumption and production recorded as losses at accounting points in its activities. Metering grid area identification, data interval. The metering grid area belongs to the DSO. The retrieval interval is not in the future. Metering data and the starting and ending time of the period without a supplier for all accounting points that are completely or partially without a supplier for the interval reported in the retrieval. 206 (233)

207 Table 37 Information exchange in retrieval of consumption and production registered as losses Class diagram 45 Information provided in retrieval of consumption and production registered as losses 207 (233)

208 Class diagram 46 Information returned in retrieval of consumption and production registered as losses 208 (233)

209 4.7 DH 600 Balance deviation correction Figure 47 Correction processes for balance errors DH611 Balance Deviation Report to Supplier Table 52 Description of report of balance deviation data to the supplier Event description Definition Parties Event initiation Begins when Information to be reported Validation Rights to Rules Interrupting events Time limits Processing Information storage Information reported Processed Return/relaying of Return of Relaying of Errors and cancellations reports the results of balance deviation calculation to the supplier for checking., supplier. has performed balance deviation calculation for one or more of the supplier's accounting points. Accounting pointspecific balance deviation data specified at the metering grid area and supplier level. The supplier's accounting pointspecific balance deviation data with consideration to agreement and balance data. The supplier must acknowledge the notification as received. 209 (233)

210 Significant errors and consequences Cancellation conditions Balance error calculation is performed and the data reported incorrectly The DSO invoices suppliers on the wrong grounds. Sequence diagram 38 Information exchange in report of balance deviation data to the supplier Class diagram 47 Balance deviation data reported to the supplier 210 (233)

211 4.7.2 DH612 Balance deviation data report to DSO Table 53 Description of report of balance deviation data to DSO Event description Definition Parties Event initiation Begins when Information to be reported Validation Rights to Rules Interrupting events Time limits Processing Information storage Information reported Processed reports the results of balance deviation calculation to the DSO., DSO. Return/relaying of Return of Relaying of Errors and cancellations Significant errors and consequences Cancellation conditions has performed balance deviation calculation for one or more of the DSO's accounting points. Accounting pointspecific balance deviation data specified at the metering grid area and supplier level. The metering grid area belongs to the DSO. The DSO must acknowledge the notification as received. Balance error calculation is performed and the data reported incorrectly The DSO invoices suppliers on the wrong grounds. 211 (233)

212 Sequence diagram 39 Information exchange in reporting of balance deviation data to DSO Class diagram 48 Balance deviation data reported to DSO 212 (233)

213 4.8 DH700 Product and invoicing maintenance processes Figure 48 Product and invoicing maintenance processes 213 (233)

214 4.8.1 DH710 Product data update Table 54 Description of product data update Event description Definition Parties Event initiation Begins when Information to be reported Validation Rights to Rules Interrupting events Time limits Processing Information storage Information reported Processed A supplier or DSO reports its own product data to. Supplier, DSO,. A supplier makes changes to existing products, removes products or creates new products. Party ID; product data. Only one price/pricetime series can be valid at any given time. Product data. Return/relaying of Return of Relaying of Errors and cancellations Significant errors and consequences Cancellation conditions Approval or rejection of. Product data is reported incorrectly An automated invoicing process can produce incorrect invoices or the wrong may be given to a customer. Product data is corrected by means of a new update. 214 (233)

215 Sequence diagram 40 Information exchange when a party reports product data Class diagram 49 Product data reported by a party 215 (233)

216 4.8.2 DH720 Product data request Table 55 Description of product data request Event description Definition Parties Event initiation Begins when Information to be reported Validation Rights to Rules Interrupting events Time limits Processing Information storage Information reported Processed Return/relaying of Return of Relaying of Errors and cancellations Significant errors and consequences Cancellation conditions A supplier, DSO or 3rd party retrieves another party's product data from. Supplier/DSO/3rd party,. A supplier, DSO or 3rd party needs product data in its business. The search can be restricted by one or more party IDs, which identify the parties whose is being retrieved. The suppliers' product data and price for all parties is only returned if the retrieving party has been given authorisation to the by the product owner. The party's product data (see rights to above). 216 (233)

217 Sequence diagram 41 Information exchange when a party retrieves product data Class diagram 50 Information reported for request of product data 217 (233)

218 Class diagram 51 Information returned in retrieval of product data 218 (233)

219 4.8.3 DH730 Invoice row data report Table 56 Description of notification of invoice row Event description Definition Parties Event initiation Begins when Information to be reported Validation A supplier or DSO reports its own invoice rows to. Supplier/DSO,. A supplier or DSO performs invoicing and forms invoice rows in its system and reports these to. Accounting point identification, party identification, agreement identification, invoice row. Rights to According to the accounting pointspecific rights in section 2.2. Rules Interrupting events Time limits Processing Information storage Information reported Processed Return/relaying of Return of Relaying of Errors and cancellations Significant errors and consequences Cancellation conditions The accounting point has not been removed from use for the period being reported. Invoice row. Approval or rejection of. The invoice row is reported incorrectly The invoicing process produces incorrect invoices. 219 (233)

220 Sequence diagram 42 Information exchange when a party reports invoice row Class diagram 52 Information content for notification of invoice row 220 (233)

221 4.8.4 DH740 Invoice row data request Table 57 Description of invoice line request Event description Definition Parties A supplier, DSO or 3rd party retrieves invoice row from. Supplier/DSO/3rd party,. Event initiation Begins when Information to be reported A supplier, DSO or 3rd party needs invoice rows in its business. Time interval for which the is desired; searches can be limited by accounting point, party for which the invoice row is retrieved or by the agreement identification of the agreement being invoiced. Without limits, all for which the party has rights will be returned. Validation Rights to Rules The party has authorisation from the invoicing owner party. Invoice rows exist for the period being retrieved. The retrieved accounting point has not been removed from use for the period being reported. Interrupting events Time limits Processing Information storage Information reported Processed Return/relaying of Return of Relaying of All invoice rows corresponding to the limiting conditions and for which the time interval cuts across the interval reported in the search. Errors and cancellations Significant errors and consequences Cancellation conditions 221 (233)

222 Sequence diagram 43 Information exchange when a party retrieves invoice row Class diagram 53 Information reported for request of invoice row 222 (233)

223 Class diagram 54 Information returned in retrieval of invoice row 223 (233)

224 4.9 DH800 Authorisations Figure 49 Authorisation processes DH810 Notification of customer authorisation Table 58 Description of notification of customer authorisation Event description Definition Parties Event initiation Begins when Information to be reported Validation Rights to Rules Interrupting events Time limits Processing A supplier, DSO or other 3rd party registered in requests the right to customer. Supplier/DSO/3rd party,. The party has a business need and authorisation from the customer to obtain the right to the customer's in. The IDs for customers who have granted authorisation; the IDs of the accounting points for which authorisation was granted 1 ; date on which the authorisation begins; date on which authorisation ends; reason/purpose of authorisation (list), and optional explanation. The party must be registered in. The reported customers and accounting points are found in. If the reported customers do not have agreements for the accounting point associated with the authorisation, only the right to customer is created. 1 Authorisation cannot be reported for all of the customer's metering points without specifying them in order to prevent abuse. This type of authorisation need can be handled in accordance with the service described in section (233)

225 Information storage Information reported Processed Storage of authorisation. Recording authorisation either for customer only or also for accounting point. Return/relaying of Return of Relaying of Acknowledgement of approval/rejection of the notification. If the right to accounting point cannot be granted, the notification is "partially approved". Errors and cancellations Significant errors and consequences Cancellation conditions Authorisation is reported for the wrong accounting points The party receives for which it has no rights. The party must cancel the authorisation and delete the that it has already retrieved from. A party reports authorisations without actually receiving authorisation from the customers The party is criminally liable for its actions in cases of abuse. No restrictions. Sequence diagram 44 Information exchange when a 3rd party reports authorisation 225 (233)

226 Class diagram 55 Information content for authorisation 226 (233)

227 4.10 DH900 Party Figure 50 Maintenance processes for party 227 (233)

1 SERVICE DESCRIPTION

1 SERVICE DESCRIPTION 1 (5) 1 SERVICE DESCRIPTION According to the Electricity Market Act, Fingrid is tasked with developing the information exchange required for electricity trade and imbalance settlements. Fingrid's information

More information

TERMS OF ELECTRICITY SALES 2010. as recommended by Finnish Energy Industries

TERMS OF ELECTRICITY SALES 2010. as recommended by Finnish Energy Industries TERMS OF ELECTRICITY SALES 2010 as recommended by Finnish Energy Industries Content: A. General, concluding an electricity sale contract, the prerequisites for electricity sales, commencement of electricity

More information

Business Requirement Specification

Business Requirement Specification Nordic Ediel Group Business Requirement Specification for a Harmonised Nordic Retail Market Business processes, message format, content and interface Status: Final version, including comments after public

More information

Harmonised Model for Supplier Switching. Report 4/2013

Harmonised Model for Supplier Switching. Report 4/2013 Harmonised Model for Supplier Switching Report 4/2013 1 Harmonised Model for Supplier switching Report 4/2013 NordREG c/o Norwegian Water Resources and Energy Directorate Middelthunsgate 29, 0301 Oslo,

More information

SERVICE AGREEMENT ON THE ELECTRICITY MARKET INFORMATION EXCHANGE SERVICE

SERVICE AGREEMENT ON THE ELECTRICITY MARKET INFORMATION EXCHANGE SERVICE 1 (5) SERVICE AGREEMENT ON THE ELECTRICITY MARKET INFORMATION EXCHANGE SERVICE 1 PARTIES TO THE AGREEMENT NN, business ID xxx (hereinafter "the Electricity Market Party") Address [Supplier's party ID:]

More information

Nordic Imbalance Settlement Handbook. Instructions and Rules for Market Participants 12.12.2014

Nordic Imbalance Settlement Handbook. Instructions and Rules for Market Participants 12.12.2014 Nordic Imbalance Settlement Handbook Instructions and Rules for Market Participants Business process: Nordic Imbalance Settlement Version: 2.0 Status: For implementation Date: December 12st, 2014 2 Foreword

More information

Nordic Balance Settlement

Nordic Balance Settlement Nordic Balance Settlement Handbook for Market Participants (DRAFT) 17.12.2013 Business process: Nordic Balance settlement Version: 0 Status: For review and comments Date: December 17st, 2013 Nordic Balance

More information

Nordic Imbalance Settlement Handbook

Nordic Imbalance Settlement Handbook Nordic Imbalance Settlement Handbook Instructions and Rules for Market Participants Business process: Nordic Imbalance Settlement Version: 2.01 Status: For implementation Date: April 24th 2015 2 Foreword

More information

ELECTRICITY MARKET ACT

ELECTRICITY MARKET ACT 1 NB: Unofficial translation Ministry of Trade and Industry, Finland ELECTRICITY MARKET ACT (386/1995; amendments up to 1172/2004 included) In accordance with a decision by Parliament, the following is

More information

THE HARMONISED ELECTRICITY MARKET ROLE MODEL

THE HARMONISED ELECTRICITY MARKET ROLE MODEL 1 THE HARMONISED ELECTRICITY MARKET ROLE MODEL ASSOCIATED ORGANISATIONS: 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 Table of Contents 1 INTRODUCTION... 8 2 ABOUT THE ROLE MODEL... 8 3 PROCEDURES

More information

[BRP] Imbalance Settlement Agreement Main Agreement [29.5.2015]

[BRP] Imbalance Settlement Agreement Main Agreement [29.5.2015] [BRP] Imbalance Settlement Agreement Main Agreement [29.5.2015] 2 Table of contents 1 Parties 3 2 Definitions 3 3 Contract Documents 5 4 Background and purpose 5 5 BRP's Rights and Obligations 6 6 esett's

More information

TUPAS Identification Service. Identification Principles

TUPAS Identification Service. Identification Principles TUPAS Identification Service Version 2.0b Table of contents 1 Introduction... 4 1.1 General description... 4 1.2 Document name and specification data... 5 1.3 Parties... 5 1.3.1 Banks... 5 1.3.2 Service

More information

General card terms for corporate customers

General card terms for corporate customers Page 1 / 9 General card terms for corporate customers Valid from 16.2.2014 1. Scope and definitions These General Terms and Conditions for Corporate Cards apply to cards issued by (referred to herein as

More information

Nordic Imbalance Settlement. Agreement on Pledge and Right of Disposal of Cash Account. between. [name of Balance Responsible Party] and.

Nordic Imbalance Settlement. Agreement on Pledge and Right of Disposal of Cash Account. between. [name of Balance Responsible Party] and. Nordic Imbalance Settlement Agreement on Pledge and Right of Disposal of Cash Account between [name of Balance Responsible Party] and esett Oy and [name of Settlement Bank] based on agreement template

More information

Data security regulations as well as preparations for malfunction and other exceptional situations Decision of Euroclear Finland s CEO

Data security regulations as well as preparations for malfunction and other exceptional situations Decision of Euroclear Finland s CEO Data security regulations as well as preparations for malfunction and other exceptional situations Decision of Euroclear Finland s CEO To: Account operators Issuer agents Clearing parties Reference to

More information

Valid as of January 29, 2013

Valid as of January 29, 2013 1 (10) Contractual terms of RAY Valid as of January 29, 2013 These contractual terms replace the contractual terms of RAY that entered into force on August 28, 2012. These terms shall also be applied to

More information

the disposal of the account holder or authorised user, excluding, however, transactions related to the crediting of deposit interest.

the disposal of the account holder or authorised user, excluding, however, transactions related to the crediting of deposit interest. General terms and conditions for corporate accounts These General terms and conditions for corporate accounts were adopted on 15 November 2012. These terms and conditions will be applied to companies account

More information

SPECIAL CONDITIONS OF PRIVATE CLOUD Version dated 08/06/2011

SPECIAL CONDITIONS OF PRIVATE CLOUD Version dated 08/06/2011 SPECIAL CONDITIONS OF PRIVATE CLOUD Version dated 08/06/2011 DEFINITIONS : Cloud: Technology that uses remote resources and storage. Host Server: Physical Server with a memory load and a processor load.

More information

TERMS AND CONDITIONS OF CASH TRANSACTIONS IN DOMESTIC TRANSACTIONS AT PKO BP SA BANK

TERMS AND CONDITIONS OF CASH TRANSACTIONS IN DOMESTIC TRANSACTIONS AT PKO BP SA BANK TERMS AND CONDITIONS OF CASH TRANSACTIONS IN DOMESTIC TRANSACTIONS AT PKO BP SA BANK TABLE OF CONTENTS Section 1... 1 GENERAL PROVISIONS... 1 I. Acceptance and execution of the payment order by the Bank...

More information

VPO NOK Rules. Rules for the Central Securities Settlement. in Norwegian Kroner

VPO NOK Rules. Rules for the Central Securities Settlement. in Norwegian Kroner Entry into force: 29. April 2015 Version: 1.1 Published 27. April 2015 VPO NOK Rules Rules for the Central Securities Settlement in Norwegian Kroner This document is a translation from the original Norwegian

More information

Nordic Imbalance Settlement Model

Nordic Imbalance Settlement Model Nordic Imbalance Settlement Model Contents Executive Summary Nordic Imbalance Settlement Model Settlement Structure Management Metering Settlement Data Reporting Imbalance Settlement Invoicing Communication

More information

General Terms of Public Procurement in Service Contracts JYSE 2014 SERVICES

General Terms of Public Procurement in Service Contracts JYSE 2014 SERVICES General Terms of Public Procurement in Service Contracts January 2015 Contents Introduction...3 Issues to be observed in applying...5 General Terms of Public Procurement in Service Contracts ()...9 1 Definitions...9

More information

General Terms of Public Procurement in service contracts JYSE 2009 SERVICES

General Terms of Public Procurement in service contracts JYSE 2009 SERVICES General Terms of Public Procurement in service contracts November 2009 Contents Introduction........................................................................................................................................3

More information

NordREG Common Nordic end-user market

NordREG Common Nordic end-user market NordREG Common Task Force Balance Settlement Outline for a common Nordic Balance Settlement (NBS) Consultation Paper May 17 th, 2010 Content 1 Introduction... 3 2 Main requirements for a Nordic Balance

More information

Energy Efficiency Agreement for Industries Company Accession Document for the Action Plan for Energy Production

Energy Efficiency Agreement for Industries Company Accession Document for the Action Plan for Energy Production 1(4) Unofficial translation Energy Efficiency Agreement for Industries Company Accession Document for the Action Plan for Energy Production 1. Company (Name of Company) joins the Energy Efficiency Agreement

More information

General Terms of Public Procurement in Supply Contracts JYSE 2014 SUPPLIES

General Terms of Public Procurement in Supply Contracts JYSE 2014 SUPPLIES General Terms of Public Procurement in Supply Contracts January 2015 Contents Introduction...3 Issues to be observed in applying...5 General Terms of Public Procurement in Supply Contracts ()...8 1 Definitions...8

More information

Payment requirements with combined billing

Payment requirements with combined billing Payment requirements with combined billing FINAL REPORT 30.4.2013 Marika Bröckl, Laura Hakala, Erkka Ryynänen, Iivo Vehviläinen Gaia Consulting Oy Index Executive Summary... 3 1 Introduction... 6 1.1 Background...

More information

Terms and conditions of agreement on the provision of payment services to subscribers

Terms and conditions of agreement on the provision of payment services to subscribers Terms and conditions of agreement on the provision of payment services to subscribers Contents 1. Scope of the terms and conditions of agreement... 4 2. Definitions... 4 3. Provider of payment services...

More information

COMPANY... 3 SYSTEM...

COMPANY... 3 SYSTEM... Wisetime Ltd is a Finnish software company that has longterm experience in developing industrial Enterprise Resource Planning (ERP) systems. Our comprehensive system is used by thousands of users in 14

More information

Finnish Energy Industries draft answer to CEER public consultation The future role of DSOs

Finnish Energy Industries draft answer to CEER public consultation The future role of DSOs Finnish Energy Industries draft answer to CEER public consultation The future role of DSOs Respondents information Name Ina Lehto Name of organisation Finnish Energy Industries Type of organisation Other

More information

Netaxept Agreement Agreement for epayment Service Merchants

Netaxept Agreement Agreement for epayment Service Merchants Netaxept Agreement Agreement for epayment Service Merchants Return address Nets ecommerce and MOTO Finland ecommerce-support-fi@nets.eu Netaxept ID Processing date Version EN 4.0 m Processor Please complete

More information

RHODE ISLAND. Electronic Business Transactions (EBT) Standards. for Electronic Data Interchange (EDI) in a Restructured Electric Industry

RHODE ISLAND. Electronic Business Transactions (EBT) Standards. for Electronic Data Interchange (EDI) in a Restructured Electric Industry RHODE ISLAND Electronic Business Transactions (EBT) Standards for Electronic Data Interchange (EDI) in a Restructured Electric Industry PREPARED BY: THE NARRAGANSETT ELECTRIC COMPANY AUGUST 1999 TABLE

More information

National Report 2015 to the Agency for the Cooperation of Energy Regulators and to the European Commission

National Report 2015 to the Agency for the Cooperation of Energy Regulators and to the European Commission Ref: 1842/601/2015 10.7.2015 National Report 2015 to the Agency for the Cooperation of Energy Regulators and to the European Commission Finland National Report 2015 - Energy Authority, Finland 1 CONTENT

More information

DK HOSTMASTER S GENERAL CONDITIONS FOR THE ASSIGNMENT, REGISTRATION AND ADMINISTRATION OF.DK DOMAIN NAMES

DK HOSTMASTER S GENERAL CONDITIONS FOR THE ASSIGNMENT, REGISTRATION AND ADMINISTRATION OF.DK DOMAIN NAMES DK HOSTMASTER S GENERAL CONDITIONS FOR THE ASSIGNMENT, REGISTRATION AND ADMINISTRATION OF.DK DOMAIN NAMES 31 January 2016 Under Section 12(1) of Danish Act No. 164 of 26 February 2014 on Internet Domain

More information

CHAPTER I I. Formation of a limited liability company CHAPTER I. GENERAL PROVISIONS

CHAPTER I I. Formation of a limited liability company CHAPTER I. GENERAL PROVISIONS Law of the Republic of Kazakhstan dated April 22, 1998 220-I On limited liability companies and additional liability companies (with alterations and amendments as of 29.12.2014) CHAPTER I. General provisions

More information

Licensor: Deveo Oy Customer: [address line 2] LICENSE NUMBER:

Licensor: Deveo Oy Customer: [address line 2] LICENSE NUMBER: 1/8 DEVEO SOFTWARE LICENSE AGREEMENT COVER PAGE LICENSE CERTIFICATE AND LICENSE NUMBER Licensor: Deveo Oy Customer: [address line 1] [address line 2] Product Deveo on-premises Software version License

More information

Nordea Bank Finland Plc s General 1 (11) Terms Governing Electronic Services for Companies

Nordea Bank Finland Plc s General 1 (11) Terms Governing Electronic Services for Companies Nordea Bank Finland Plc s General 1 (11) Information about the service provider The main service provider referred to in these terms is Nordea Bank Finland Plc, a commercial bank from the city of Helsinki.

More information

Act on Investment Firms 26.7.1996/579

Act on Investment Firms 26.7.1996/579 Please note: This is an unofficial translation. Amendments up to 135/2007 included, May 2007. Act on Investment Firms 26.7.1996/579 CHAPTER 1 General provisions Section 1 Scope of application This Act

More information

ORDER to promulgate the Act on Prevention of Late Payment (ZPreZP)

ORDER to promulgate the Act on Prevention of Late Payment (ZPreZP) Legal notice All effort has been made to ensure the accuracy of this translation, which is based on the original Slovenian text. All translations of this kind may, nevertheless, be subject to a certain

More information

Act. on Strong Electronic Identification and Electronic Signatures (617/2009)

Act. on Strong Electronic Identification and Electronic Signatures (617/2009) NB: Unofficial translation; legally binding texts are those in Finnish and Swedish Act on Strong Electronic Identification and Electronic Signatures (617/2009) Chapter 1 General provisions Section 1 Scope

More information

Invitation to Tender

Invitation to Tender Invitation to Tender Provision of Training in Technology Transfer and Related Areas for The Southern Africa Innovation Support Programme 1. Drawing up the tender The tender must be submitted in writing

More information

National Report 2014 to the Agency for the Cooperation of Energy Regulators and to the European Commission

National Report 2014 to the Agency for the Cooperation of Energy Regulators and to the European Commission Ref: 1602/601/2014 10.7.2014 National Report 2014 to the Agency for the Cooperation of Energy Regulators and to the European Commission Finland National Report 2014 - Energy Authority, Finland 1 CONTENT

More information

NordREG s work towards a harmonised Nordic retail market - Roadmap update and national implementation monitoring

NordREG s work towards a harmonised Nordic retail market - Roadmap update and national implementation monitoring NordREG s work towards a harmonised Nordic retail market - Roadmap update and national implementation monitoring NordREG Report 5 2014 Published: 2014-09-08 1 NordREG s work towards a harmonised Nordic

More information

Rights and obligations of DSOs and suppliers in the customer interface

Rights and obligations of DSOs and suppliers in the customer interface Rights and obligations of DSOs and suppliers in the customer interface Report 4/2011 Rights and obligations of DSOs and suppliers in the customer interface Nordic Energy Regulators 2011 Report 4/2011

More information

Nordic Balance Settlement (NBS)

Nordic Balance Settlement (NBS) Nordic Balance Settlement (NBS) Common Balance & Reconciliation Settlement Design December 22 nd, 2011 Content Terminology...4 Executive Summary...6 1 Introduction... 8 1.1 Scope of the Nordic Balance

More information

Rules of Alternative Trading System organised by the BondSpot S.A.

Rules of Alternative Trading System organised by the BondSpot S.A. Rules of Alternative Trading System organised by the BondSpot S.A. text according to legal condition at 1 January 2013 Only the Polish version of these documents is legally binding. This translation is

More information

* * * Document created on12 February 2013 This translation is for information purposes only 1/12

* * * Document created on12 February 2013 This translation is for information purposes only 1/12 AMF position recommandation 2013-04 AMF guidelines on the concept of third party introducer with regard to the fight against money laundering and terrorist financing Background regulations: Articles L.561-7

More information

TheFinancialEdge. Configuration Guide for Accounts Receivable

TheFinancialEdge. Configuration Guide for Accounts Receivable TheFinancialEdge Configuration Guide for Accounts Receivable 101711 2011 Blackbaud, Inc. This publication, or any part thereof, may not be reproduced or transmitted in any form or by any means, electronic,

More information

GENERAL TERMS AND CONDITIONS

GENERAL TERMS AND CONDITIONS 1 DEFINITIONS 1.1 Account: the customer name used by the Customer to access the System of VEVIDA Services BV. 1.2 Email Address: an address code set up in the Customer s name for exchanging electronic

More information

GENERAL TERMS AND CONDITIONS FOR NETS PAYMENT TERMINALS AND PAYMENT TERMINAL SERVICES

GENERAL TERMS AND CONDITIONS FOR NETS PAYMENT TERMINALS AND PAYMENT TERMINAL SERVICES GENERAL TERMS AND CONDITIONS FOR NETS PAYMENT TERMINALS AND PAYMENT TERMINAL SERVICES 1 APPLICATION OF THE TERMS AND CONDITIONS OF CONTRACT These general terms and conditions of contract for payment terminals

More information

www.consumerfocus.org.uk

www.consumerfocus.org.uk The aim of this information is to help you understand how to change your energy supplier. It should all go smoothly, but it s a great help if you can provide accurate information to your new supplier,

More information

LAW ON PAYMENT SERVICES

LAW ON PAYMENT SERVICES LAW ON PAYMENT SERVICES Part I INTRODUCTORY PROVISIONS Subject matter Article 1 This Law regulates the conditions and manner of providing payment services, electronic money, payment systems and supervision

More information

The Norwegian-Swedish Electricity Certificate Market ANNUAL REPORT 2013

The Norwegian-Swedish Electricity Certificate Market ANNUAL REPORT 2013 The Norwegian-Swedish Electricity Certificate Market ANNUAL REPORT 2013 2 Contents Preface 3 The Nordic electricity market 5 Key figures for 2013 6 How the electricity certificate market works 7 Goal fulfilment

More information

Electricity Trading RULES

Electricity Trading RULES Electricity Trading RULES Chapter 1 GENERAL PROVISIONS Article 1. These rules define: 1. Electricity trading rules at freely negotiated prices; 2. Transition from trade at regulated prices to trade at

More information

ELECTRONIC TRADING FACILITIES SUPPLEMENTAL TERMS AND CONDITIONS OF TRADING

ELECTRONIC TRADING FACILITIES SUPPLEMENTAL TERMS AND CONDITIONS OF TRADING ELECTRONIC TRADING FACILITIES SUPPLEMENTAL TERMS AND CONDITIONS OF TRADING This Supplemental Terms and Conditions of Trading is supplemental to and forms part of the terms and conditions set out in the

More information

DEFINITIONS. Order entry. Attachment 2

DEFINITIONS. Order entry. Attachment 2 Attachment 2 DEFINITIONS member authorised connection a direct technical connection that enables a non member firm to access TradElect directly under a member firm s trading codes. Orders submitted in

More information

Rules of Procedure of Statistics Finland

Rules of Procedure of Statistics Finland 1(7) Rules of Procedure of Statistics Finland General provisions Operational organisation By virtue of Sections 3 and 4 of the Statistics Finland Act (48/1992), and amendments thereto (901/2002), the Director

More information

Pseudo-regulation F: EDI communication in the electricity market 64884-10. March 2011. Version 2.0 1.0 2.0. Slettet: June.

Pseudo-regulation F: EDI communication in the electricity market 64884-10. March 2011. Version 2.0 1.0 2.0. Slettet: June. Pseudo-regulation F: EDI communication in the electricity market March 2011 Version 2.0 Slettet: June Slettet: 0 Slettet: 1 1.0 16-6-2010 24-6-2010 25-6-2010 DATE BOO MBN JHH NAME 2.0 25-2-2011 8-3-2011

More information

Agreement concerning Fimnet authentication service. Address: Contact person: E-mail:

Agreement concerning Fimnet authentication service. Address: Contact person: E-mail: Company: Business ID: Address: Postcode: Town or city: Contact person: E-mail: Telephone: Person/company in charge of technical matters, plus contact details: Invoicing details Company: Business ID: Invoicing

More information

PAYMENT SERVICES AND SYSTEMS ACT (ZPlaSS) CHAPTER 1 GENERAL PROVISIONS SUBCHAPTER 1 CONTENT OF THE ACT. Article 1. (scope)

PAYMENT SERVICES AND SYSTEMS ACT (ZPlaSS) CHAPTER 1 GENERAL PROVISIONS SUBCHAPTER 1 CONTENT OF THE ACT. Article 1. (scope) Legal notice All effort has been made to ensure the accuracy of this translation, which is based on the original Slovenian text. All translations of this kind may, nevertheless, be subject to a certain

More information

GENERAL CONDITIONS FOR THE SALE OF ELECTRICITY USED IN BUSINESS OPERATIONS OR OTHER SIMILAR ACTIVITIES

GENERAL CONDITIONS FOR THE SALE OF ELECTRICITY USED IN BUSINESS OPERATIONS OR OTHER SIMILAR ACTIVITIES 1 (6) GENERAL CONDITIONS FOR THE SALE OF ELECTRICITY USED IN BUSINESS OPERATIONS OR OTHER SIMILAR ACTIVITIES GENERAL CONDITIONS prepared by Svensk Energi 1. Introductory provisions 1.1 These general conditions

More information

Issues and corporate actions in the book-entry system Decision of Euroclear Finland s CEO. To: Issuers Account operators Issuer agents

Issues and corporate actions in the book-entry system Decision of Euroclear Finland s CEO. To: Issuers Account operators Issuer agents Issues and corporate actions in the book-entry system Decision of Euroclear Finland s CEO To: Issuers Account operators Issuer agents Reference to the Rules: 2.1.13, 3.1.11, 3.1.12,3.1.13, 3.1.14, 3.1.19

More information

USER REQUIREMENTS CHAPTER 16 STATIC DATA REQUIREMENTS

USER REQUIREMENTS CHAPTER 16 STATIC DATA REQUIREMENTS USER REQUIREMENTS CHAPTER STATIC DATA REQUIREMENTS TS Project Team Reference: TS-0-0 Date: July 00 Version:. Status: Draft TS User requirements - Chapter - Static data requirements TABLE OF CONTENTS 0

More information

LAW. ON ELECTRONIC SIGNATURE (Official Gazette of the Republic of Montenegro 55/03 and 31/05)

LAW. ON ELECTRONIC SIGNATURE (Official Gazette of the Republic of Montenegro 55/03 and 31/05) LAW ON ELECTRONIC SIGNATURE (Official Gazette of the Republic of Montenegro 55/03 and 31/05) I GENERAL PROVISIONS Article 1 This Law shall regulate the use of electronic signature in legal transactions,

More information

MANAGEMENT SYSTEM FOR A NUCLEAR FACILITY

MANAGEMENT SYSTEM FOR A NUCLEAR FACILITY GUIDE YVL A.3 / 2 June 2014 MANAGEMENT SYSTEM FOR A NUCLEAR FACILITY 1 Introduction 5 2 Scope of application 6 3 Management system 6 3.1 Planning, implementation, maintenance, and improvement of the management

More information

GENERAL TERMS OF ORDERS AND DEFINITIONS FOR A PROFESSIONAL INVESTOR. April 2007

GENERAL TERMS OF ORDERS AND DEFINITIONS FOR A PROFESSIONAL INVESTOR. April 2007 1 I. SCOPE OF APPLICATION OF THE GENERAL TERMS OF ORDERS AND DEFINITIONS 1 Purpose and scope of application of the Terms of Orders These Terms of Orders shall be applied to the Order Relationship on the

More information

Invitation for participating in consultation for a joint Nordic Balance Settlement

Invitation for participating in consultation for a joint Nordic Balance Settlement CONSULTATION NBS DESIGN REPORT 1 (2) Date 2011-01-26 Invitation for participating in consultation for a joint Nordic Balance Settlement The Nordic TSOs hereby invite your organisation to a consultation

More information

The Bratislava Stock Exchange IPO Overview

The Bratislava Stock Exchange IPO Overview The Bratislava Stock Exchange IPO Overview Bratislava Stock Exchange (hereinafter referred to as BSSE ) was founded in 1991, in conformity with a decree of the Ministry of Finance of the Slovak Republic

More information

YOUR CONTACT WITH ELECTRICITY COMPANIES

YOUR CONTACT WITH ELECTRICITY COMPANIES YOUR CONTACT WITH ELECTRICITY COMPANIES page 2 Electricity options available to you page 4 Your electricity consumption (meter reading facts) page 6 You re moving in (what to do with your contracts) page

More information

1. "Bill Payment" means our service that allows you to pay or transfer funds to designated Payee(s) in connection with our Home Banking Service.

1. Bill Payment means our service that allows you to pay or transfer funds to designated Payee(s) in connection with our Home Banking Service. I. HOME BANKING AND BILL PAYMENT SERVICES. This Home Banking Agreement ( Agreement ) is between Arizona Federal Credit Union (hereinafter we, us, our or Credit Union ), and each member who has enrolled

More information

Additional terms and conditions Enterprise to the conditions of use for d.vinci easy

Additional terms and conditions Enterprise to the conditions of use for d.vinci easy Additional terms and conditions Enterprise to the conditions of use for d.vinci easy 1. General information These Enterprise conditions of use supplement the general conditions of use for the software

More information

Estonian Health Insurance Fund Act

Estonian Health Insurance Fund Act Issuer: Riigikogu Type: act In force from: 23.03.2014 In force until: 31.12.2016 Translation published: 02.04.2014 Amended by the following acts Passed 14.06.2000 RT I 2000, 57, 374 Entry into force 01.01.2001,

More information

Latvian Central Depository Regulation No. 15 On DVP settlement in foreign currencies

Latvian Central Depository Regulation No. 15 On DVP settlement in foreign currencies Latvian Central Depository Regulation No. 15 On DVP settlement in foreign currencies APPROVED by Latvian Central Depository Supervisory Board Meeting on February 27, 2004 AMENDMENTS APPROVED On 29.05.2007.;

More information

Rules of Alternative Trading System organised by the BondSpot S.A.

Rules of Alternative Trading System organised by the BondSpot S.A. Rules of Alternative Trading System organised by the BondSpot S.A. The Rules adopted by the Management Board by Resolution No. 103/2009 dated 4 November 2009, as amended by the Management Board: by Resolution

More information

Adlib Hosting - Service Level Agreement

Adlib Hosting - Service Level Agreement Adlib Hosting - Service Level Agreement June 2014 This service level agreement (SLA) applies to the Adlib Hosting services provided by Axiell ALM Netherlands BV, and includes the activities and facilities

More information

Standard conditions of electricity supply licence

Standard conditions of electricity supply licence Gas and Electricity Markets Authority ELECTRICITY ACT 1989 Standard conditions of electricity supply licence SECTION A: STANDARD CONDITIONS FOR ALL SUPPLIERS Standard conditions 1 to 6: General arrangements

More information

Our Customer Relationship Agreement IINET VDSL2 SERVICE DESCRIPTION

Our Customer Relationship Agreement IINET VDSL2 SERVICE DESCRIPTION Our Customer Relationship Agreement IINET VDSL2 SERVICE DESCRIPTION iinet Limited ACN 068 628 937 Phone: 13 22 58 Westnet Pty Ltd ACN 086 416 908 Phone: 1300 786 068 1/502 Hay Street, Subiaco WA 6008 20

More information

Information Security Policies. Version 6.1

Information Security Policies. Version 6.1 Information Security Policies Version 6.1 Information Security Policies Contents: 1. Information Security page 3 2. Business Continuity page 5 3. Compliance page 6 4. Outsourcing and Third Party Access

More information

Limited Liability Companies Act Finland

Limited Liability Companies Act Finland [UNOFFICIAL TRANSLATION Ministry of Justice, Finland 2012] Limited Liability Companies Act Finland (624/2006; amendments up to 981/2011 included; osakeyhtiölaki) PART I GENERAL PRINCIPLES, INCORPORATION

More information

ENTSO-E Network Code on Emergency and Restoration

ENTSO-E Network Code on Emergency and Restoration ENTSO-E Network Code on Emergency and Restoration Notice 25 March 2015 This Network Code represents ENTSO-E s final proposals in line with the ACER Framework Guidelines on Electricity System Operation

More information

THE BUDAPEST STOCK EXCHANGE LTD. REGULATIONS ON THE USE OF REMOTE TRADING

THE BUDAPEST STOCK EXCHANGE LTD. REGULATIONS ON THE USE OF REMOTE TRADING THE BUDAPEST STOCK EXCHANGE LTD. REGULATIONS ON THE USE OF REMOTE TRADING Date and reference no. of approval/modification resolutions by the Board of Directors: Date and reference no. of approval by Supervisory

More information

PRAXIS INTERPRETING + STANDARD TERMS & CONDITIONS

PRAXIS INTERPRETING + STANDARD TERMS & CONDITIONS PRAXIS INTERPRETING + STANDARD TERMS & CONDITIONS General These Standard Terms and Conditions apply to the provision of all interpreting and translation services provided by Praxis Interpreting + (PI+).

More information

Business and technical conditions of electricity supply for customers connected to the public distribution of LV electricity valid for the year 2005

Business and technical conditions of electricity supply for customers connected to the public distribution of LV electricity valid for the year 2005 Business and technical conditions of electricity supply for customers connected to the public distribution of LV electricity valid for the year 2005 ARTICLE I GENERAL PROVISIONS 1. These business and technical

More information

Documentation. M-Bus 130-mbx

Documentation. M-Bus 130-mbx Documentation M-Bus 130-mbx Introduction The mx M-Bus module is part of the mx Smart Slot communications family. With the integrated SmartSlot technology, mx systems ag offers automatic consumer data read-out

More information

Agreement No On Electronic Service of Current Accounts

Agreement No On Electronic Service of Current Accounts Agreement No On Electronic Service of Current Accounts Yerevan " '' 20 This Contract was signed by and between the entities mentioned below, (further respectively referred to as Party or Parties ). : Ameriabank

More information

2. Principle of "first come, first served" and acceptable domain names

2. Principle of first come, first served and acceptable domain names ANNEX 3: General terms and conditions of the contract between the domain name registrar and registrant as part of registering, renewing, and administering domain names Version: 1.0 Last Updated: June 2006

More information

PART I GENERAL. Chapter 1. General provisions. Section 1. General scope of application of the Act

PART I GENERAL. Chapter 1. General provisions. Section 1. General scope of application of the Act 1(49) Unofficial translation Amendments up to 258/2013 included 746/2012 Issued in Helsinki on 14 December 2012 Securities Markets Act Pursuant to the decision of Parliament, the following is enacted:

More information

Walmart Stores, Inc. Getting Started with EDI Implementation Guideline Document version: 1.0 Published November 2011

Walmart Stores, Inc. Getting Started with EDI Implementation Guideline Document version: 1.0 Published November 2011 Walmart Stores, Inc. Getting Started with EDI Implementation Guideline Document version: 1.0 Published November 2011 5 0 1 0 Business Usage: The following packet was created to speed-up your EDI implementation.

More information

-«Trustee Authority»: Entity that defines and regulates the conditions of assignment and use of Domain Names, applying to each particular Extension.

-«Trustee Authority»: Entity that defines and regulates the conditions of assignment and use of Domain Names, applying to each particular Extension. NETIM - GENERAL TERMS AND CONDITIONS OF DOMAIN NAMES CG-ND version 2.1-15 th November 2015 NETIM, limited liability company under french law, with head office located 165 avenue de bretagne 59000 LILLE

More information

Contractor s liability and tax number in the construction sector

Contractor s liability and tax number in the construction sector Contractor s liability and tax number in the construction sector 2 Introduction This guide provides information on the contractor s obligation to check and the tax number used at construction sites. Construction-related

More information

BUSINESS TERMS AND CONDITIONS FOR PROVISION OF ELECTRONIC BANKING SERVICES FOR INDIVIDUALS

BUSINESS TERMS AND CONDITIONS FOR PROVISION OF ELECTRONIC BANKING SERVICES FOR INDIVIDUALS BUSINESS TERMS AND CONDITIONS FOR PROVISION OF ELECTRONIC BANKING SERVICES FOR INDIVIDUALS UniCredit Bank Czech Republic and Slovakia, a.s., Želetavská 1525/1, 140 92 Prague 4 Michle, Company Registration

More information

Non-legally binding translation from Danish

Non-legally binding translation from Danish Rules for the Supply of Upgraded Biogas (Bio Natural Gas) into the Danish Gas System (Rules for Bio Natural Gas) (Version 1.0) Non-legally binding translation from Danish Effective from 1 May 2013 Contents

More information

BULLETIN ON PAYMENT SERVICE

BULLETIN ON PAYMENT SERVICE 1 st. of April 2016 This bulletin contains general advance information on payment services which the Bank must provide to a consumer customer before entering into a master agreement (hereinafter the "Bulletin

More information

Corporate Policy. Data Protection for Data of Customers & Partners.

Corporate Policy. Data Protection for Data of Customers & Partners. Corporate Policy. Data Protection for Data of Customers & Partners. 02 Preamble Ladies and gentlemen, Dear employees, The electronic processing of virtually all sales procedures, globalization and growing

More information

Message exchange with. Finnish Customs

Message exchange with. Finnish Customs Message exchange with Finnish Customs Introduction to message exchange with Finnish Customs Finnish Customs 3.6.2015 Message Exchange Support Contents Introduction... 3 1 Electronic services of Finnish

More information

Data Exchange and Protocol Process Flows for Electric Deregulation in The State of New Jersey

Data Exchange and Protocol Process Flows for Electric Deregulation in The State of New Jersey Data Exchange and Protocol Process Flows for Electric Deregulation in The State of New Jersey Prepared by: The Consumer Process Working Groups July 17, 2000 Version 1.2 Table of Contents Table of Contents...

More information

SMART GRIDS PLUS INITIATIVE

SMART GRIDS PLUS INITIATIVE Demand Response for residential customers -business opportunity for utilities ERA-NET SMART GRIDS PLUS INITIATIVE Sami Sailo, There Corporation Energy markets in Finland Supplier A Supplier B Settlement

More information

Tasks for which the efaktura connection unit is responsible are performed by Nets Norway AS (Nets) on behalf of the bank.

Tasks for which the efaktura connection unit is responsible are performed by Nets Norway AS (Nets) on behalf of the bank. A. Introductory provisions 1. Brief description of the service efaktura B2C is a service for the electronic transmission and presentation of payment claims and invoices in the invoice recipient s (payer

More information

GENERAL CONDITIONS FOR SALE OF ELECTRICITY TO DOMESTIC CONSUMERS

GENERAL CONDITIONS FOR SALE OF ELECTRICITY TO DOMESTIC CONSUMERS 27 February 2015 1 (9) GENERAL CONDITIONS FOR SALE OF ELECTRICITY TO DOMESTIC CONSUMERS GENERAL CONDITIONS prepared by Svensk Energi following agreement with the Swedish Consumer Agency. 1. Introductory

More information

Unofficial translation. The Electricity (Capacity) Market Rules

Unofficial translation. The Electricity (Capacity) Market Rules Chapter I General Provisions Article 1. Scope of Activity Unofficial translation The Electricity (Capacity) Market Rules These Rules regulate: a) Functioning of Electricity and Guaranteed Capacity Market

More information