Volume NOVITA. Scheduling System. Scheduling System Manual for Market Participants

Transcription

1 Volume S3 NOVITA Scheduling System Scheduling System Manual for Market Participants

2 S C H E D U L I N G S Y S T E M Scheduling Web Client Manual Novita d.o.o. Pot za Brdom 32 SI-1000 Ljubljana info@novita.si Tel (0) Fax +386 (0) Draft Ver. EMS/2.0

3 Table of Contents APPLICATION BASICS... 1 SILVERLIGHT... 1 System Requirements... 2 Installation Instructions... 2 LOGGING IN... 3 SCHEDULES AND ALLOCATIONS... 4 BALANCE RESPONSIBLE SCHEDULES... 4 ACKNOWLEDGEMENT DOCUMENTS... 6 ANOMALY REPORTS... 7 CONFIRMATION REPORTS... 8 ALLOCATIONS... 8 TRANSMISSION RIGHTS PORTFOLIO... 9 DOCUMENT IMPORT... 9 SECONDARY MARKET INTRADAY CAPACITY AVAILABLE TRANSFER CAPACITY ATC RESERVATION REQUESTS ATC RESERVATION RESULTS REMARKS... 11

4 Application Basics Scheduling Web Client is a web based application. It is available on: Scheduling-Client. Scheduling Web Client functionalities are implemented according to documents and definitions produced by the ENTSO-E Electronic Data Interchange (EDI) Working Group. Links to particular documents are available bellow, but you can check the entire EDI Library. Silverlight When Scheduling Web Client application initially attempts to run and there is no Silverlight plugin installed on the client machine, the download will be offered. Before proceeding check the System Requirements chapter and make sure you are running a Silverlight compatible Windows operating system and browser and that you have uninstalled any previous version of Silverlight. Detailed installation instructions are available in Installation Instructions chapter. 1

5 System Requirements Scheduling Web Client Silverlight application is compatible with the following operating systems and browsers: Operating System Internet Explorer 11 Internet Explorer 10 Internet Explorer 9 Internet Explorer 8 Internet Explorer 7 Firefox 12+ Windows Windows Windows 7 - Windows Vista - - Windows XP SP Minimal system requirements for Windows are x86 or x GHz or faster processor with minimum 512 MB of RAM. Installation Instructions The browser will prompt you to either run or save the installation file (Silverlight.exe). Click Run to start the download. When the download is finished, the browser prompts you again to run the installer. Click Run to start the installation. Note that you must have sufficient administrative privileges to install Silverlight. If you are running the Windows 7 or later operating system, you will be prompted for security permissions. To continue, you need to approve. Click Install now to install Silverlight. If you have had a previous version of Silverlight installed, or are using Mozilla Firefox, you will need to restart your browser. 2

6 Logging in The user is required to use an electronic certificate (cryptographic hardware token) and Scheduling Web Client User Account (username and password logon). Dialog with the username and password field is displayed, you need to enter values assigned by system operator. Once you are logged in, the applicaton will be downloaded and synchronized with the server. You can follow the proces in the right corner bellow. When Scheduling Web Client application is used for the first time, the application storage needs to be increased. Click Increase Storage and then confirm it once again. 3

7 Schedules and Allocations Balance Responsible Schedules A Schedule document provides the position of a Party or a Domain related to some market information (i.e. Document Type). It includes a set of time series schedules. It is required, that one schedule document (attributes checked are: Domain, In/Out Area, In/Out Party, Capacity Contract Type and Capacity Agreement Identification) is exchanged for a date and role, which means that if there are additions, modifications or suppressions to the set of time series within the schedule document, the document identification remains unchanged but the version number must be increased. In Scheduling Web Client the version number is automatically increased, when user changes and confirms schedule document. Most of the data required by ESS standard is already pre-entered and cannot be changed. Message identification is generated automatically, but can be changed by the user (for example, when an organization sends multiple balance responsible schedules for the same time period). Schedule time series entry is available on the Time Series tab. Users can create a new one with Create button or edit an existing with Edit button. On the Schedule Time Series dialog some data are entered automatically and cannot be changed according to ETSO rules. Time series identification is also generated automatically, but may be changed by the user. Time series quantity 4

8 entry is available on Intervals tab. User can type values directly or use option Add, to add capacity quantity at once. On Add capacity Interval dialog, time interval is set as predefined on General tab. If you are updating existed capacity interval quantities, option Quantities entered as difference can be used, and entered quantities will be added to the existing. Specify quantity in the input dialog box on the right and use Set button to prepare interval quantities for desired hour interval. Once quantities are prepared and reviewed, you can confirm it with OK button and transfer it to time series Interval tab. Capacity Contract Type (CCT) and Capacity Agreement Identification (CAI) are mandatory information, when Business type A03 (External trade explicit capacity) is selected. Schedule messages without required or with irregular data will be rejected. See ESS Implementation Guide for more information about Schedule documents. 5

9 Domain 34Y-ESS-CRP----0 and Object aggregation A03 (Party) are mandatory information when Business type A04 (Consumption) is selected. Schedule messages without required or with irregular data will be rejected. Domain 34Y-ESS-PRP----7 and Object aggregation A03 (Party) are mandatory information when Business type A01 (Production) is selected. Schedule messages without required or with irregular data will be rejected. Acknowledgement Documents The Acknowledgement document is used in conjunction with the transmission of all electronic documents defined in the ETSO process for technical or application acknowledgement. A document is checked by the system in two levels: It is first controlled at system level to detect syntax errors (XML parsing errors, file, processing errors, etc.); It is then controlled at the application level to detect any semantic errors (invalid data, wrong process, etc.). If there is a problem encountered at the first level then a technical acknowledgement may be sent to inform the originator of the problem. If errors are encountered at the second level or if the 6

10 application can successfully process the information then an application acknowledgement may be sent to inform the originator of the situation. See ESS Implementation Guide and EAD Implementation Guide for more information about Acknowledgements documents. With the Web Client all of acknowledgement documents sent to particular party in question can be reviewed. On the General tab detailed information about original document, parties, date/time and acknowledgement reason (A01 Message fully accepted or A02 Message fully rejected) are displayed. Time Series Rejections tab can provide more information about rejected time series and the reasons of the rejections. Anomaly Reports An Anomaly report contains the time series that have been identified as being in error (mismatched) for the party in question. It is generated as soon as the system operator has all the necessary information in his possession. Time series found to be in error need to be resent via the retransmission of the applicable schedule message (with a new message version) containing the corrected time series (with the version number of the retransmit message). The retransmitted schedule message will also include all the non-erroneous time series that were sent with the message. These should maintain the version number of their last clean transmission. See ESS Implementation Guide for more information about Anomaly reports. With the Web Client all of anomaly reports sent to a particular interconnection trade responsible (ITR)/Balance Responsible Party (BRP) can be reviewed. On the General tab sender, receiver and date/time information are available. Time series tab provides detailed information about time series in error. 7

11 Confirmation Reports The Confirmation report contains all the time series that have been sent in the schedule document. It may include one or several time series that the system operator has imposed on the market participant in compliance with market rules. Balance responsible schedule can either be globally confirmed, or in the case of discrepancies, you will be informed of what aspects of your time series have been accepted. System generates intermediate confirmation reports and final confirmation report (after cutoff time). See ESS Implementation Guide for more information about Confirmation reports. On the General tab information about sender, receiver, date/time and confirmation reason (A06 Schedule accepted, A07 Schedule partially accepted or A08 Schedule rejected) are displayed. Time series tab provides detailed information about confirmed series and decreased quantities in case of mismatches. Allocations Allocations option provides Rights document with document type A23: Allocations, business type A33: Authorised AAC and it informs Capacity trader about the allocated transmission capacity rights. A Rights Document is used in various contexts within the ECAN process. In general it identifies the capacity transmission rights that a Capacity Trader has in their portfolio for 8

12 a given border. Only rights allocated by the local system operator (EMS) are shown here. See ECAN Implementation Guide for more information about Rights documents. Transmission Rights Portfolio Transmission Rights Portfolio (TRP) option provides Rights document with document type A22: Transmission Rights Portfolio, business type A34: Capacity rights and it informs Capacity trader about the allocated capacity rights. The document is created upon user request, and user can request new document with Request New button. If there is already TRP created for the day in the question, a new version of already existed document will be created. The document contains a complete portfolio of transmission capacity rights, whether allocated by EMS or by any of the counter system operators bordering on EMS (only if rights documents have been transmitted to EMS). By pressing Request New button Status Request document is send to the system. It is possible to send Status Request document also as XML document via . See ETSO Status Request Implementation Guide for more information about Status Request documents. Document Import Web Client supports importing the XML document and sending it to the System operator, although XMLs can also be sent via . XML document file should be selected and uploaded by clicking on in the Document import menu. Web Client will dispay file name, document identification and version, time interval, document and process type, sender, receiver and the whole XML content. Once you checked your data, you can upload it by clicking the Send button. 9

13 Secondary Market Currently not supported. Intraday Capacity Available Transfer Capacity Available Transmission Capacity (ATC) is the part of NTC that remains available after the allocation procedure, and is used for further commercial activity. ATC is calculated by the following equation: ATC=NTC-AAC, where NTC (Net Transfer Capacity) corresponds to the maximum exchange between two areas and AAC (Already Allocated Capacity) to the total amount of allocated transmission rights. In this section user can also review nominated quantities. 10

14 ATC Reservation Requests Currently not supported. ATC Reservation Results Currently not supported. Remarks Access to Scheduling Web Client is only allowed to Balance Responsible Parties (BRPs) according to national Grid Code and Market Code. Market roles used is the Manual are in case of EMS included in role of BRP. 11