Bilateral trade reporting transition in Sweden. Guide for Swedish Balance Responsible Parties

Transcription

1 Bilateral trade reporting transition in Sweden Guide for Swedish Balance Responsible Parties

2 2 Table of Contents Table of Contents 2 1 Introduction 3 2 Schedule 4 3 Change of reporting regime 5 4 Structure updates 6 5 Messaging testing against Edielportal 7 6 Connectivity testing 8 7 Messaging testing against the production environment Structure Time interval for the messages Time schedule for the testing phase Data cleaning and structure updates 9 8 Test practices & support Additional information Contact esett 10 9 Appendix Connectivity check-list 11

3 3 1 Introduction The purpose of this document is to act as a guideline for Swedish Balance Responsible Parties (BRP s) during the transition of reporting Bilateral Trades (BIT) to esett settlement system Basse instead of Svenska kraftnät (Svk). The transition activities will be done during June September Bilateral trades must be reported to esett starting with the operational day of 26 th September This document provides information needed specifically by the Swedish BRPs during the transition. General information about NBS and Basse has been published previously and can be found from multiple sources. These documents should be used if more specific information is needed. The most important documents are referred to in this document and a list is also provided in the end of this document. In addition to general information about the transition, support etc, this document consists of four main chapters, corresponding to the four main activities in the transition phase: Structure updates Messaging testing against Ediel Connectivity Messaging testing against production environment

4 4 2 Schedule The transition phase is divided into four activities, which are mandatory to all Swedish BRP s to assure reporting readiness starting from September 26 th. The goal is to achieve full readiness before the BIT go-live. Figure 1 The transition consists of four main activities. The activities and their deadlines, as shown in Figure 1 are: Structure information delivery Deadline 30.6 o Report your bilateral trade related structure information to esett Connection information delivery Deadline 30.6 o Report your SMTP connection details to esett Testing against Ediel Deadline 11.8 o Validate your XML-messages against the Ediel portal Connectivity testing Deadline 25.8 o Verify that you can send and receive messages to and from esett settlement system Basse Testing against production environment Deadline 8.9 o Verify that you can send and receive valid messages that are corresponding to your reported structures Start date for reporting bilateral trades (for the operational day 26.9)

5 5 3 Change of reporting regime Bilateral trades in Sweden are currently reported to Svk. The matching procedure is performed by Svk and values are reported back to the market party. All messages between the market party and Svk uses the DELFOR format. After gate closure, Svk reports all bilateral trades in Sweden to esett. The process can be seen in the below figure. Svk esett BRP1 XML ENTSO-E ESS Matched Bilateral trade (BRP, MBA) TRANS Basse BRP2 DELFOR ENTSO-E ESS Bilateral handel (BRP, MBA) Matching New reporting regime means that the BRP will send the bilateral trades directly to esett. This implies that same gate closures will be applied, message will be in XML-format and the reporting will be on BRP- and RE level. BRPs will receive the matched quantity and the delta (difference of the reported quantities). Matched quantity is the quantity that has been set after correction rules has been applied (see Handbook, ) BRP1 esett XML ENTSO-E ESS Bilateral trade (BRP, RE, MBA) Basse BRP2 Matching

6 6 4 Structure updates Due to the change of reporting regime for bilateral trades within Swedish market balance areas and a harmonization with other countries within NBS, esett needs an updated structure for all bilateral trades. The harmonization means that all bilateral trades will be reported on a Retailer-level. Market participants can use the template, which can be found from the link below, in order to send all their bilateral trades. Deadline for submitting the template is Unless the template has been received by then, the balance responsible party has to submit this on the Online Service. For further information of how bilateral trades are submitted on Online Service, please see Online User guide, and section Online User Guide is shown in Online Service by pressing the help button. Please notice, the current state of the bilateral trade structure can be checked from Online Service by Data can be reported only for current structures updated in the system. Reporting data relevant to structures that are not visible in Online Service or are lacking mandatory attributes, results in rejecting the reported data and a negative acknowledgement. Link for the BRP template

7 7 5 Messaging testing against Edielportal Market participants are required to conduct both Aktörtest (AGT) and Systemtest (TGT) at the Ediel portal. Starting with TGT those can be carried out from End date for approval is set to For further information, see Ediel portal web address:

8 8 6 Connectivity testing Connectivity testing phase is required to ensure the basic connectivity toward esett s messaging service. Connectivity is established when a message is successfully sent to esett and a response has been received back to market participant s system. Connectivity testing can be initiated by the market participant as soon as they have reported their connection details to esett for verifying the firewall openings. It is expected that all Swedish market participants, that this transition involves, use the SMTP channel for messaging. As the purpose of the connectivity testing is just to verify the basic connectivity, a successful reporting of bilateral trades is not necessary for this phase. If market participant receives a rejection message from the esett messaging service, the connectivity can be considered as success. Messages are sent to address: inbox@service.esett.com

9 9 7 Messaging testing against the production environment After the preparations (connectivity & structures) have been done, the messages can be tested. Testing will be done in the Production environment; no test environment will be used regarding this test phase. The process and conditions for testing the bilateral trade messages are described in sections below. 7.1 Structure There will not be any fabricated structures used when testing the messages. The structure that is in place in Online Service should be used during this test phase. Market participants can verify the structures in Online Service from The validity period for all structures during the test phase will be set as follows: Start date: End date: Time interval for the messages All test messages can only use time interval between and This means that there will be a window open for the tests and messages with a time interval before and after will be rejected. 7.3 Time schedule for the testing phase The time period for the test phase is Data cleaning and structure updates After the test phase, esett will clean the values used in the test phase. This activity will be performed during the time period Furthermore, the End date regarding the validity period for the trades will be changed according to the provided structures. This means that the End date will in most cases be set to Undefined.

10 10 8 Test practices & support esett informs market participants about the latest news regularly via a newsletter distributed to Online Service users and via the news on the front page of Online Service. Targeted information regarding the transition is distributed via to subscribed Swedish BRPs. 8.1 Additional information - NBS Handbook: - Communication guidelines and data flow examples: - NBS Business Requirement Specification: - NBS User Guide: % pdf - Ediel portal: Contact esett If you encounter any issues or have questions after revising the supporting documents, you may contact esett customer service. Please contact esett primarily by filling in a service request at After a ticket has been created, esett will contact you once your ticket is picked up from the queue by esett. You may also contact esett by calling customer service (09-15 CET). For efficient resolution, please always create a ticket before calling. Ticket can be created in English, Finnish, Swedish or Norwegian according to your preferences. For esett to be able to investigate the issue, a detailed description of the incident and conditions under which the incident happened needs to be included. Note: When submitting support request, it is important to include information for example about: - Start the header with the phrase BIT transition - Detailed description what happened before issue - What is the issue - Client information (e.g. web browser, FTP server) - Related sample XML file (XML messages) - Screenshot - What information was tried be modified - Possible error message

11 11 9 Appendix 9.1 Connectivity check-list If you are not able to verify connectivity, check that all of the following steps have been done: 1. Deliver your connection details to esett for Firewall openings a. Connection details must be sent to esett to allow market participants access to Basse through esett firewall b. Send your connection details for your chosen channel on a template found at Please note that often Online Service may be accessed from different IP address than the Messaging Service you are using. Then two different IP addresses need to be provided to esett. i. If the external IP addresses from where you are connecting to Online Service or Messaging Service are changed, you need to report the new addresses ii. You can check your workstations external IP address for example from This IP address is used for accessing Online Service from your workstation iii. If you don t know from which address your system is connecting to Messaging Service, (via M2M interface) please contact your local IT department iv. If you are using a service provider or other operator who finally deliver the messages to Basse, then their IP address need to be provided to esett. 2. Access Online Service i. Login to Online Service with your credentials 1. One set of administrator credentials has been delivered to each company. Administrators can create additional credentials in Online Service 2. If you don t have credentials or cannot log in, contact your company administrator to check your username, phone number for 2-factor authentication and password 3. If you are the only administrator and are not able to login, contact esett 3. Check your connection details in Online Service a. Check and/or update the connection details for your preferred communication channel (FTP/SMTP/WebService) in Online Service according to the steps in Online Service User Guide, chapter (found under the help button on the front page of Online Service) i. If you don t know these details or which channel you should use, contact the administrator of your system or your IT department that sends the M2M messages to esett 4. Perform firewall openings in your own environment a. For Basse to be able to send outbound data flows to your system, you must allow incoming traffic from esett IP address (announced in Online Service front page -> esett services and addresses) i. Contact your firewall administrator to check that this address is allowed ii. Verify that your service provider has the address allowed, if applicable 5. Send a message a. Send any inbound message (BITI) via your preferred communication channel. Check the following things: i. You are sending from the environment specified in connection details in Online Service ii. You are sending from the external IP you have reported to esett iii. The message is sent according to Communication guidelines: Guidelines.pdf iv. The message structure corresponds to the data flow examples at: and BRS at v. Check that the message you are sending is reporting data only for structures that are visible in Online Service (structures, codes etc. are in line)

12 12 b. Wait for an acknowledgement i. The acknowledgement is sent (in most cases) to the address specified in outbound connection details in Online Service c. Check that the message is visible in Online Service Messaging register i. Verify that you are logged in as the same market role as which you sent the message 6. Receive a message a. Basse sends messages (e.g BICO) automatically to market participants systems via the address specified in outbound connection detail in Online Service. Check that you receive these messages b. Send an acknowledgement to the received message i. Please notice that acknowledgements are not used with data packages c. Check that the acknowledgement is visible in Online Service Messaging register Adresses Online Service address: Addresses to other services, as well as the IP address from which esett is connecting to market participants service, have been distributed to market participants separately. These addresses are also found on the Online Service front page.