ScheduleManagement
1. Schedule Management (KISS)
1.1. Structure of the schedule form
Schedule Form is an Excel document consist of tree (3) worksheets described bellow:
- “INFO” sheet - General information about the sender
- “EXTERN” sheet - Energy transactions between control zones
- “INTERN” sheet - Energy transactions within one control zone
The names of the worksheets (“INFO”, “EXTERN” and “INTERN”) are not allowed to be changed. The same words should be entered in cell “A1” of each worksheet.
You can download examples of TPS files below (note that 23 or 25-hour schedules are to be send only when the change of daylight-saving time occurs):
1.2. "INFO" Sheet
The “Info” sheet contains some general information about the sender of the file.
The date (on witch the schedule is to be valid) is entered in cell “C1”. It must be in the following format: DD.MM.YYYY, D – day, M – month, Y – year.
From line 2, down below can be entered text in free form (contact person, address, telephone, e-mail, etc.).
Here it is allowed to be used some special characters (e.g. ä, ö, ü).
1.3. Structure of EXTERN and INTERN sheets
The other two sheets “EXTERN” and “INTERN” have a different structure than the “INFO” sheet.
In these worksheets of the form columns “A” and “B” are predefined. It is not allowed to be made any changes of the contents in the cells of those two columns.
The columns on the right (“C” to “IV”) are the columns containing the data of the schedule nominations.
A data column in the worksheets has the following structure:
|
No.
|
Area
|
Line
|
Explanation
|
|
1
|
Date
|
1
|
Date for which the schedule is to be valid. The date must be expressed in the format: DD.MM.YYYY
D – day, M – month, Y - year
|
|
2
|
Out-area
|
2
|
EIC code of the control area from witch the energy is taken
|
|
3
|
In-area
|
3
|
EIC code of the control area to witch the energy is delivered
|
|
4
|
Out-party
|
4
|
EIC code of the trade responsible party that exports the energy in the transaction from the out-area to the in-area.
|
|
5
|
In-party
|
5
|
EIC code of the balance responsible party that import the energy in the transaction from the out-area to the in-area.
|
|
6
|
|
6
|
In columns “A” and “B” the row is empty. Starting from column “C” to “IV” the row contains the type of the document (e.g. for traders -TPS – Trade responsible Party Schedule)
|
|
7
|
Sender/responsible-party
|
7
|
EIC code of the trade responsible party sending the document.
|
|
8
|
Version
|
8
|
The version number of the columns. The version number starts at 1 every day. This number applies to the file name and all schedule columns. If there are any changes that have been made, the version number is increased by 1.
|
|
9
|
Capacity Contract ID
|
9
|
That is the Capacity Contract (Agreement) Identification of the capacity right.
|
|
10
|
Comments
|
10 - 14
|
Additional information concerning the transaction (type of delivery, contract for capacity rights, capacity quotas, etc.). The information may vary for the different traders.
The information is not mandatory.
|
|
11
|
Values
|
18 - 133
|
The schedule values for the valid date given in 15 minutes resolution.
|
1.4. "EXTERN" Sheet
The schedules of all energy transactions between neighboring control areas or countries are entered in the “EXTERN” sheet.
The control areas from/to which the energy is export/import are recognized by their EIC code entered in the relative fields “out-party”/ “in-party”.
The trade parties responsible for the energy transactions between the neighboring control areas or countries are recognized by their EIC codes entered in fields “out-party”/”in-party”.
1.5. "INTERN" sheet
The schedules of all energy transactions inside a control area are entered in the “INTERN” sheet.
The EIC codes in the two area fields (“out-area” and “in-area”) shall be the same and in accordance with the EIC code of the control area to witch the schedule nominations are sent.
The fields “out-party” and “in-party” describe the trade responsible parties involved into an energy transaction inside the control area. The parties are recognized by their EIC codes entered in those fields.
1.6. Instructions for filling out the form
The schedule form must be sent only for one calendar day for witch the transactions are valid, even if the schedule do not vary from day to day.
If one transaction is nominated incorrectly and have to be cancelled, the new version of the schedule must contain the same transaction but with time series zeroed.
The version number starts at 1 every day. This number applies to the file name and all schedule columns.
If any changes are made, the version number is increased by 1. This new version number applies, however, only for the file names and exclusively for the changed schedules (columns). As a result, the most recent change can always be recognized, even if there are several versions.
|
Example
|
|
|
|
|
|
|
|
Versions No.File
|
Transaction A
|
Transaction B
|
Transaction C
|
Transaction D
|
|
1st report
|
01
|
1
|
1
|
1
|
-
|
|
Transaction B changes
|
02
|
1
|
2
|
1
|
-
|
|
Transaction A changes
|
03
|
3
|
2
|
1
|
-
|
|
Transaction D is added
|
04
|
3
|
2
|
1
|
4
|
The schedule form should have file name in the following format:
YYYYMMDD_ZZZ_EIC-trader_EIC-TSO_VV.xls
Where:
- YYYYMMDD - date on which the schedule is to be valid
- ZZZ – type of schedule
TPS – for Traders (Trade responsible Party Schedule)
CAS,CAX,CBS – for System Operators
- EIC-trader - EIC code of the trade responsible party sending the form
- EIC-ESO - EIC code of the system operator to witch the schedule is sent off
- VV - Version of the schedule sent off. Starts at 1 every day.
1.7. Instructions for filling out the EXTERN and INTERN sheets
· One form per calendar day.
· Text entries must not contain any special characters (e.g. ä, ö, ü).
· The data areas must be filled out from left to right without any empty columns.
· The direction of the transactions is not identified by using a plus or minus sign but by the information "out-area", "in-area", "out-party" and "in-party". If both directions occur in the schedule, a schedule is reported for each direction.
· All values must be given in "MW" and rounded off to 3 digits after the decimal point.
· No empty cells may be given in the value area of a data column. The values must always be >= 0.
· All equations shall be deleted from the schedules before they are sent off.
· It is mandatory to use EIC codes for identification of all trade responsible parties and control areas in the schedule form.
1.8. Sending the schedule form
All schedules are exchanged in electronic way by e-mail. Please send all your schedules to the following e-mail address:
tsoplan@ndc.bgThe name put in the “Subject” field of the e-mail message should be in the following format (the same as the file name but without the file extension):
YYYYMMDD_ZZZ_EIC-trader_EIC-TSO_VV
Where:
- YYYYMMDD - date on which the schedule is to be valid
- ZZZ – type of schedule
TPS – for Traders (Trade responsible Party Schedule)
CAS,CAX,CBS – for System Operators
- EIC-trader - EIC code of the trade responsible party sending the form.
- EIC-ESO - EIC code of the system operator to witch the schedule is sent off
- VV - Version of the schedule sent off. Starts at 1 every day.
2. Schedule Management (ESS)
As of 1 Oct 2011, ESO it to start testing the cross-border schedules reconcilement module of the Market Management System (MMS)– a test involving market actors.
ESS cross-border schedules are XML files defined by ETSO Scheduling System standard - ESS.
The actual reconcilement and validation of electricity quantities at the border will be based on cross-border schedules in ESS file format to be submitted at
tsoplan@ndc.bg.