Question 2.2.2
In case of different, but valid, interpretations of delivery profiles, which one has to be chosen for transaction reporting?
As an example - an off peak trade I currently build as
<deliveryProfile>
<daysOfTheWeek>WD</daysOfTheWeek>
<loadDeliveryStartTime>00:00:00</loadDeliveryStartTime>
<loadDeliveryEndTime>08:00:00</loadDeliveryEndTime>
</deliveryProfile>
<deliveryProfile>
<daysOfTheWeek>WD</daysOfTheWeek>
<loadDeliveryStartTime>20:00:00</loadDeliveryStartTime>
<loadDeliveryEndTime>00:00:00</loadDeliveryEndTime>
</deliveryProfile>
<deliveryProfile>
<daysOfTheWeek>WN</daysOfTheWeek>
<loadDeliveryStartTime>00:00:00</loadDeliveryStartTime>
<loadDeliveryEndTime>00:00:00</loadDeliveryEndTime>
</deliveryProfile>
but it could equally, legally be described as this.
<deliveryProfile>
<daysOfTheWeek>WD</daysOfTheWeek>
<loadDeliveryStartTime>20:00:00</loadDeliveryStartTime>
<loadDeliveryEndTime>08:00:00</loadDeliveryEndTime>
</deliveryProfile>
<deliveryProfile>
<daysOfTheWeek>WN</daysOfTheWeek>
<loadDeliveryStartTime>00:00:00</loadDeliveryStartTime>
<loadDeliveryEndTime>00:00:00</loadDeliveryEndTime>
</deliveryProfile>
We would prefer our version as it is clearer, does it matter? They are both schema valid and correct to our mind
Same question for NBP gas. We currently generate this
<deliveryProfile>
<daysOfTheWeek>WD</daysOfTheWeek>
<loadDeliveryStartTime>06:00:00</loadDeliveryStartTime>
<loadDeliveryEndTime>06:00:00</loadDeliveryEndTime>
</deliveryProfile>
<deliveryProfile>
<daysOfTheWeek>WN</daysOfTheWeek>
<loadDeliveryStartTime>06:00:00</loadDeliveryStartTime>
<loadDeliveryEndTime>06:00:00</loadDeliveryEndTime>
</deliveryProfile>
but equally it could be this
<deliveryProfile>
<loadDeliveryStartTime>06:00:00</loadDeliveryStartTime>
<loadDeliveryEndTime>06:00:00</loadDeliveryEndTime>
</deliveryProfile>
again, we prefer our version as being clear, again does it matter - will ACER accept both?
We would prefer ACER to accept all variants of this, otherwise ACER will have to describe a “reference” implementation for everything, which takes time to do and then time for everyone to implement and time is something that we don’t have a lot of
Answer
With regards to the electricity example:
<deliveryProfile>
<daysOfTheWeek>WD</daysOfTheWeek>
<loadDeliveryStartTime>20:00:00</loadDeliveryStartTime>
<loadDeliveryEndTime>08:00:00</loadDeliveryEndTime>
</deliveryProfile>
This would mean that delivery started on Mon 20:00 to 00:00 and Tue 00:00 to 08:00 and 20:00 to 00:00, etc . but that means it misses the period between 00:00 to 08:00 on Mon.
With regard to the code in the natural gas example:
<deliveryProfile>
<loadDeliveryStartTime>06:00:00</loadDeliveryStartTime>
<loadDeliveryEndTime>06:00:00</loadDeliveryEndTime>
</deliveryProfile>
This applies to every day delivery from 06:00 am to 06:00 am irrespective of the day.
While WD from 06:00 am to 06:00 am + WN from 06:00 am to 06:00 am may represent the same thing of all days from 06:00 am to 06:00 am, the use of the smallest possible set of information is the correct way to report such a transaction: e.g. all days 06:00 am to 06:00 am and not WD + WN.
The reporting of WD + WN profiles should be avoided when it is not needed. For example: a yearly forward contract for the delivery of gas from 06:00 am to 06:00 am every day of the year can be represented with one delivery period for all days as seen above, WD + WN profiles or it can be repeated 365 days, one per each deliver day. Since the all-day from 06:00 am to 06:00 am profile is the simplest one, this should be used.
Reporting parties that aim at a successful transaction reporting should pay attention to the trading examples reported in Annex II of the TRUM and should not deviate from it unless previously discussed with the Agency.
In addition, for electricity delivery profiles that start at 23:00, e.g. a baseload contract delivery starts at 23:00 on Sunday and delivery ends at 23:00 on Friday, this should be reported as SUtoFR from 23:00 to 23:00
<deliveryProfile>
<daysOfTheWeek>SUtoFR</daysOfTheWeek>
<loadDeliveryStartTime>23:00:00</loadDeliveryStartTime>
<loadDeliveryEndTime>23:00:00</loadDeliveryEndTime>
</deliveryProfile>
The profile WD from 23:00 to 23:00:
<deliveryProfile>
<daysOfTheWeek>WD</daysOfTheWeek>
<loadDeliveryStartTime>23:00:00</loadDeliveryStartTime>
<loadDeliveryEndTime>23:00:00</loadDeliveryEndTime>
</deliveryProfile>
would not represent the same thing and it should not be used.