Please insert at least 3 characters

FAQs on fundamental data and inside information – Question III.4.1.9

Thank you for the clarifications made in the FAQ on REMIT fundamental data and insider information collection.

Related to question 5.1.8 I have another question. According to the answer, all events shall be reported as per affected unit. This means that one event that affects three units shall be reported in three unique web feed messages.

Now considering the case of an event affecting one unit but with a time varying capacity (e.g. three different values for capacity for the different time frames). Shall this event also be reported as three separate web feed messages each containing only one capacity value?

Our proposal earlier was in this case was to only report the lowest capacity value. That solution would mean that one event maps to one web feed message. Depending on your answer to the question above, the alternative would be to map one event with three web feed messages when we have time varying capacity. In any case, our design is highly dependent on a clarification of the raised point and I hope you are able to give some guidance on this matter.


Answer:

The Agency has discussed possible solutions on how to report the above mentioned event during the Inside Information Platforms roundtable meetings and concluded the following guidance for the reporting of planned and unplanned unavailability:

Planned unavailability: three separate UMMs are published for each of the three intervals.

The three messages should be published with the same timestamps unless they are different events.

Unplanned unavailability: one UMM is published (e.g. at 10 am). The UMM will be updated at 11:30 am and 12:30 pm. The three messages should have different timestamps.

RSS_Icon Last update: 15/11/2016  

FAQs on fundamental data and inside information – Question III.4.1.10

Does the Agency need to be aware about the point direction for which the affected capacity is announced? If yes, how this information shall be provided through XML based on UMM Schema No 2 “Unavailabilities for gas facilities”?

The format for the XMLs for “Unavailabilities for gas facilities” (Schema No2) does not contain attribute for the point direction.

In the context of publication of unavailabilities for gas facilities, an “Affected asset or units” could be the connection point (cross-border, interconnection point, delivery point, measurement point etc.). In case that the affected point is bidirectional, the point capacity is direction dependent, respectively the values of the UMM Schema No2 attributes: Technical capacity, Available capacity and Unavailable capacity depend on the point direction.

In summary, the technical, available and booked capacities in normal circumstances are different for the different point direction. This means that during an event of unavailability both sites of a point could be affected and respectively – the affected capacities are different per point direction.


Answer:

The point direction shall be identified via field (15/b) Balancing zone in case that the affected point is bidirectional. The field allows for multiple EIC codes identifying balancing zones and the point direction will be determined by the order of EIC codes in the XML schema. The first EIC code should refer to the ENTRY point (IN= Balancing Zone where the flow starts), and the second EIC code should refer to the EXIT point (OUT= Balancing Zone where the flow ends).

When a connection point between a transmission system and LNG terminal or transmission system and Storage facility, or transmission system and TSO from a non-EU country is affected, the submission of IN and OUT balancing zones should reflect the direction of the flow with the above IN/OUT logic applied to the facilities.

For example: if the outage is related to the flow from an LNG facility towards the Gas Transmission Network, the first EIC should represent the LNG facility and the second the Balancing zone. Example:

W EIC LNG facility= Entry point

Y EIC Balancing zone= Exit point

The same applies to storage facilities and bidirectional interconnection points.

For complex cases when one point connects more than two balancing zones, the following logic shall apply:

If the direction is from Entry Point (EIC 1) to several exit points, the first EIC code represents the entry point, the second (EIC 2) and third (EIC 3) /fourth (EIC 4) EICs represent the exit points. If the outage occurs at EIC 1 then the first code will be EIC 1 and then all the possible EICs affected zones should be reported after that. Example:

Reporting party: TSO 1

EIC 1 = Entry point

EIC 2= Exit point

EIC 3 = Exit point

EIC 4 = Exit point

If the outage is at the exit point (e.g. EIC 4) the report should indicate two points as the TSO/operator of EIC 4 will not be able to publish any information about EIC 2 and EIC 3. Example

Reporting party: TSO 4

EIC 1 = Entry point

EIC 4 = Exit point

Or in case or reverse flow:

If the outage is at the entry point (e.g. EIC 4) the report should indicate two points as the TSO/operator of EIC 4 will not be able to publish any information about EIC 2 and EIC 3. Example

Reporting party: TSO 4

EIC 4 = Entry point

EIC 1 = Exit point

If the outage is at the exit point (e.g. EIC 2) the report should indicate two points as the TSO/operator of EIC 2 will not be able to publish any information about EIC 4 and EIC 3. Example:

Reporting party: TSO 2

EIC 1 = Entry point

EIC 2 = Exit point

 

RSS_Icon Last update: 15/11/2016  

FAQs on fundamental data and inside information – Question III.4.1.11

Particular situations of gas transmission unavailability – Example 1.

How should the event be properly presented by using the available daily capacity units (kWh/d)?

How to calculate and correctly publish the amount of available and unavailable capacity?

The Agency’s guidance and the format for the XMLs for “Unavailabilities for gas facilities” allow the usage of kWh/day or mcm/day as the only acceptable units for events related to gas transmission system unavailabilities.

Example: Publication of UMM in case of unavailability of gas transmission for an event that lasts several hours during a single gas day.

Case:

    • Event start: 2015-11-06 08:00
    • Event stop: 2015-11-06 14:00
    • Technical capacity in normal circumstances: 1000 kWh/h
    • The event lasts 6 hours during a single gas day and the value of the affected capacity is constant during the whole event

Description of the event and the capacity unavailability:

Gas day: 2015-11-06
Gas hour: Available kWh/h Unavailable kWh/h
6 1000 0
7 1000 0
8 50 950
9 50 950
10 50 950
11 50 950
12 50 950
13 50 950
14 1000 0
15 1000 0
16 1000 0
17 1000 0
18 1000 0
19 1000 0
20 1000 0
21 1000 0
22 1000 0
23 1000 0
24 1000 0
1 1000 0
2 1000 0
3 1000 0
4 1000 0
5 1000 0

Answer:

The new schema “REMITUMMGasSchema_V1.xsd” (available from: https://documents.acer-remit.eu/remit-reporting-user-package/mop-on-data-reporting/viii-xml-schema-for-inside-information-reporting/) contains also “kWh/h” as an allowed unit and the schema can be already used for gas inside information reporting.

The previous schema REMITUMMGasSchema_V1_OLD.xsd without the “kWh/h” unit is still supported by ARIS and can be used for gas inside information reporting. If the old schema is used the below conversion from kWh/d to kWh/h applies. In the future (expected time: 2019/2020) the Agency will discontinue using the OLD version of the schema. Provided example represents one event and is reportable with following elements:

Event start: 2015-11-06 08:00 – Event stop: 2015-11-06 14:00

  • the unavailable capacity is 950 kWh/h = 950*24 = 22800 kWh/d
  • the available capacity is 50 kWh/h = 50*24 = 1200 kWh/d

Technical capacity is 1000 kWh/h= 1000*24= 24000 kWh/d.

RSS_Icon Last update: 08/01/2019  

FAQs on fundamental data and inside information – Question III.4.1.12

Particular situations of gas transmission unavailability – Example 2.

How should the event be properly presented by using the daily capacity units (kWh/d) and how should the changing capacity values during the different hourly sub-periods be published?

By publishing one UMM message for the whole period – 3 days?

By publishing one UMM message for each gas day?

By publishing one UMM message for each of the sub-periods?

How to calculate and correctly publish the amount of available and unavailable capacity?

The Agency’s guidance and the format for the XMLs for “Unavailabilities for gas facilities”, allow the usage of kWh/day or mcm/day as the only acceptable units for events related to gas transmission system unavailabilities.

Example: Publication of UMM in case of unavailability of gas transmission for an event that lasts more than one gas day and contains sub-periods that differ in the number of the affected hours and the values of the available and unavailable capacity per day and per hour.

Case:

  • Event start: 2015-11-06  01:00
  • Event stop: 2015-11-08 18:00
  • Technical capacity in normal circumstances: 1000 kWh/h
  • The event lasts 3 gas days and contains 3 sub-periods that differ in the number of the affected hours and the values of the available and unavailable capacity per day and per hour, as follows:
    • 5 hours during the 1st gas day, the unavailability is 950 kWh/h
    • 24 hours during the 2nd gas day, for 20 hours the unavailability is 900 kWh/h and for 4 hours the unavailability is 850 kWh/h
    • 6 hours during the 3rd gas day, the unavailability is 850 kWh/h
    • The values of the available and unavailable capacity could vary each sub-period

Description of the event and the capacity unavailability:

Gas day: 2015-11-06 2015-11-07 2015-11-08
Gas hour: Available kWh/h Unavailable kWh/h Available kWh/h Unavailable kWh/h Available kWh/h Unavailable kWh/h
6 1000 0 100 900 150 850
7 1000 0 100 900 150 850
8 1000 0 100 900 150 850
9 1000 0 100 900 150 850
10 1000 0 100 900 150 850
11 1000 0 100 900 150 850
12 1000 0 100 900 1000 0
13 1000 0 100 900 1000 0
14 1000 0 100 900 1000 0
15 1000 0 100 900 1000 0
16 1000 0 100 900 1000 0
17 1000 0 100 900 1000 0
18 1000 0 100 900 1000 0
19 1000 0 100 900 1000 0
20 1000 0 100 900 1000 0
21 1000 0 100 900 1000 0
22 50 950 100 900 1000 0
23 50 950 100 900 1000 0
24 50 950 100 900 1000 0
1 50 950 100 900 1000 0
2 50 950 150 850 1000 0
3 50 950 150 850 1000 0
4 50 950 150 850 1000 0
5 50 950 150 850 1000 0

Answer:

The new schema “REMITUMMGasSchema_V1.xsd” (available from: https://documents.acer-remit.eu/remit-reporting-user-package/mop-on-data-reporting/viii-xml-schema-for-inside-information-reporting/) contains also “kWh/h” as an allowed unit and the schema can be already used for gas inside information reporting. The previous schema REMITUMMGasSchema_V1_OLD.xsd without the “kWh/h” unit is still supported by ARIS and can be used for gas inside information reporting. If the old schema is used the below conversion from kWh/d to kWh/h applies. In the future (expected time: 2019/2020) the Agency will discontinue using the OLD version of the schema.

The provided example consists of three events to be reported.

1) Event start: 2015-11-06 22:00 – Event stop: 2015-11-07 06:00:

  • the unavailable capacity is 950 kWh/h = 950*24 = 22800 kWh/d
  • the available capacity is 50 kWh/h = 50*24 = 1200 kWh/d

2) Event start: 2015-11-07 06:00 – Event stop: 2015-11-08 02:00:

  • the unavailable capacity is 900 kWh/h = 900*24=21600 kWh/d
  • the available capacity is 100 kWh/h = 100*24 = 2400 kWh/d

3) Event start: 2015-11-08 02:00 – Event stop: 2015-11-08 12:00:

  • the unavailable capacity is 850 kWh/h = 850*24=850*24=20400 kWh/d
  • the available capacity is 150 kWh/h = 150*24 = 3600 kWh/d

Technical capacity is 1000 kWh/h = 1000*24=24000 kWh/d.

RSS_Icon Last update: 08/01/2019  

FAQs on fundamental data and inside information – Question III.4.1.13

Particular situations of gas transmission unavailability – Example 3.

 

How should the event be properly presented by using the daily capacity units (kWh/d) and how should the changing capacity values during the different hourly sub-periods be published?

By publishing three UMM messages – one for each of the sub-periods as follow:

UMM 1_001= The 1st gas day (13:00-6:00) -> 950×17/24 = 672.9 kwh/d

UMM 2_001= The 2nd gas day (6:00-6:00) -> 950×24/24=950 kwh/d

UMM 3_001= The 3rd gas day (6:00- 18:00) -> 950×12/24 = 475 kwh/d

or

By publishing one UMM message for the whole period – 3 days?

UMM 1_001= [The 1st gas day (13:00-6:00) + The 2nd gas day (6:00-6:00) + The 3rd gas day (6:00- 18:00)] / 3 = (672.9 kwh/d +950 kwh/d +475 kwh/d) /3= 699.3 kwh/d

How to calculate and correctly publish the amount of available and unavailable capacity?

The Agency’s guidance and the format for the XMLs for “Unavailabilities for gas facilities”, allow the usage of kWh/day or mcm/day as the only acceptable units for events related to gas transmission system unavailabilities.

Example: Publication of UMM in case of unavailability of gas transmission for an event that lasts several gas days.

Case :

  • Event start: 2015-11-06 13:00
  • Event stop: 2015-11-08 18:00
  • Technical capacity in normal circumstances: 1000 kWh/h
  • The event lasts 3 gas days and contains 3 sub-periods, as follows:
    • 17 hours during the 1st gas day, the unavailable is 950 kWh/h
    • 24 hours during the 2nd  gas day,  the unavailable is 950 kWh/h
    • 12 hours during the 3rd gas day, the unavailable is 950 kWh/h

Description of the event and the capacity unavailability:

Gas day: 2015-11-06 2015-11-07 2015-11-08
Gas

hour:

Available kWh/h Unavailable kWh/h Available kWh/h Unavailable kWh/h Available kWh/h Unavailable kWh/h
6 1000 0 50 950 50 950
7 1000 0 50 950 50 950
8 1000 0 50 950 50 950
9 1000 0 50 950 50 950
10 1000 0 50 950 50 950
11 1000 0 50 950 50 950
12 1000 0 50 950 50 950
13 50 950 50 950 50 950
14 50 950 50 950 50 950
15 50 950 50 950 50 950
16 50 950 50 950 50 950
17 50 950 50 950 50 950
18 50 950 50 950 1000 0
19 50 950 50 950 1000 0
20 50 950 50 950 1000 0
21 50 950 50 950 1000 0
22 50 950 50 950 1000 0
23 50 950 50 950 1000 0
24 50 950 50 950 1000 0
1 50 950 50 950 1000 0
2 50 950 50 950 1000 0
3 50 950 50 950 1000 0
4 50 950 50 950 1000 0
5 50 950 50 950 1000 0

Answer:

The new schema “REMITUMMGasSchema_V1.xsd” (available from: https://documents.acer-remit.eu/remit-reporting-user-package/mop-on-data-reporting/viii-xml-schema-for-inside-information-reporting/) contains also “kWh/h” as an allowed unit and the schema can be already used for gas inside information reporting.

The previous schema REMITUMMGasSchema_V1_OLD.xsd without the “kWh/h” unit is still supported by ARIS and can be used for gas inside information reporting. If the old schema is used the below conversion from kWh/d to kWh/h applies. In the future (expected time: 2019/2020) the Agency will discontinue using the OLD version of the schema.

The provided example represents one event with following elements:

Event start: 2015-11-06 13:00 – Event stop: 2015-11-08 18:00

  • the unavailable capacity is 950 kWh/h = 950*24 = 22800 kWh/d
  • the available capacity is 50 kWh/h = 50*24 = 1200 kWh/d

Technical capacity is 1000 kWh/h = 1000*24=24000 kWh/d.

RSS_Icon Last update: 08/01/2019  

FAQs on fundamental data and inside information – Question III.4.1.14

Unavailability of unit EIC for gas consumption units (inside information).

Field 16 requires an EIC for the identification of a physical asset. We received the information from market participants that the EIC issuing body for gas consumption units in Germany is not able to provide those codes before the end of 2016 or beginning of 2017. Therefore, it is rather likely that those codes are not available.

The issue does not refer to power production, storage or consumption units where code availability is no problem.

The respective field 16 would remain empty. We suggest to allow us to provide the inside information without EIC on a temporary basis.


Answer:

The above proposal is reasonable. Once the EIC codes are available they should be provided in the UMMs collected by the Agency.

RSS_Icon Last update: 15/11/2016  

FAQs on fundamental data and inside information – Question III.4.1.15

When will the Agency start collecting inside information web feeds from individual Market Participants’ websites?


Answer:

The Agency will not be collecting web feeds from Market Participants’ websites until further notice.

RSS_Icon Last update: 18/05/2017  

FAQs on fundamental data and inside information – Question III.4.1.16

How should this particular event be presented for inside information reporting on LNG deliverability restrictions (within UMM)?

Case: the event lasts more than one gas day.

  • Event start: 2015-11-06 01:00 (am)
  • Event stop: 2015-11-08 18:00

The event lasts 3 gas days and contains 3 sub-periods that differ in the number of the affected hours and the values of the availability and unavailability per day as follows:

Technical availability in normal circumstances: (6,78 GWh/h*24h) = 162,72 GWh per gas day

o 5 hours during the 1st gas day, the unavailability is 33,9 GWh

o 24 hours during the 2nd gas day, for 24 hours the unavailability is

162,72 GWh

o 12 hours during the 3rd gas day, the unavailability is 81,36 GWh

The values of the availability and unavailability could vary each sub-period.

Gas day: 2015-11-06 2015-11-07 2015-11-08
Gas

hour:

Availability

GWh/h

Unavailability

GWh/h

Availability

GWh/h

Unavailability

GWh/h

Availability

GWh/h

Unavailability

GWh/h

6 6,78 0 0 6,78 0 6,78
7 6,78 0 0 6,78 0 6,78
8 6,78 0 0 6,78 0 6,78
9 6,78 0 0 6,78 0 6,78
10 6,78 0 0 6,78 0 6,78
11 6,78 0 0 6,78 0 6,78
12 6,78 0 0 6,78 0 6,78
13 6,78 0 0 6,78 0 6,78
14 6,78 0 0 6,78 0 6,78
15 6,78 0 0 6,78 0 6,78
16 6,78 0 0 6,78 0 6,78
17 6,78 0 0 6,78 0 6,78
18 6,78 0 0 6,78 6,78 0
19 6,78 0 0 6,78 6,78 0
20 6,78 0 0 6,78 6,78 0
21 6,78 0 0 6,78 6,78 0
22 6,78 0 0 6,78 6,78 0
23 6,78 0 0 6,78 6,78 0
24 6,78 0 0 6,78 6,78 0
1 0 6,78 0 6,78 6,78 0
2 0 6,78 0 6,78 6,78 0
3 0 6,78 0 6,78 6,78 0
4 0 6,78 0 6,78 6,78 0
5 0 6,78 0 6,78 6,78 0
=128,82 GWh = 33,9 GWh = 0 GWh = 162,72 GWh = 81,36 GWh = 81,36 GWh

According to the Manual of Procedures (MoP) on data reporting: ANNEX VI Fundamental data reporting, VI.V XML SCHEMA FOR LNG DATA document, presentation of this event for LNG data on unavailability (within the fundamental data reporting to ACER) is:

Case:

  • Event start: 2015-11-06 01:00 (am)
  • Event stop: 2015-11-08 18:00

o 5 hours during the 1st gas day, the unavailability is 33,9 GWh

o 24 hours during the 2nd gas day, for 24 hours the unavailability is

162,72 GWh

o 12 hours during the 3rd gas day, the unavailability is 81,36 GWh

Then unavailability = (33,9 GWh + 162,72 GWh + 81,36GWh)/3 gas days = (277,98 GWh)/3 gas days = 92,66 GWh/d

Unavailability = average per gas day is 92,66 GWh/d

According to the Manual of Procedures (MoP): ANNEX VII Data fields for inside information reporting, UMM schema II. and FAQs on REMIT fundamental data and inside information collection (3rd edition, 15 November 2016) documents, the presentation of this event for inside information reporting on LNG deliverability restrictions (within UMM) should be:

There are three events and three UMMs are published:

The first UMM: 001_001

  1. Event start: 2015-11-06 01:00 (am) – event end: 2015-11-07 05:59:
  • the unavailability is 6,78 GWh/h * 5h = 33,9 GWh
  • the availability is 6,78 GWh/h * 19h= 128,82 GWh

The unavailability for the first gas day is 33,9 GWh

The second UMM:002_001

2) Event start: 2015-11-07 06:00 – event end: 2015-11-08 05:59

  • unavailability is 6,78 GWh/h * 24h = 162,72 GWh
  • the availability is 6,78 GWh/h * 0h= 0 GWh

The unavailability for the second gas day is 162,72 GWh

The third UMM:003_001

3) Event start: 2015-11-08 06:00 – event stop: 2015-11-08 18:00:

  • the unavailability is 6,78 GWh/h *12h=81,36 GWh
  • the availability is 6,78 GWh/h *12h =81,36 GWh

The unavailability for the second gas day is 81,36 GWh

Conclusion:

For this particular event:

  • ACER receives information within fundamental data reporting that the unavailability is, on average, 92,66 GWh per gas day for the whole event.

The market within UMM publications (and ACER within RSS for UMMs) receives information that the unavailability is respectively: 33,9 GWh (for the first gas day), 162,72 GWh (for the second gas day) and 81,36 GWh (for the third gas day).


Answer:

  1. Fundamental Data reporting

MoP on data reporting: The unavailability report is used to report any planned or unplanned unavailability of a facility for a gas day or period within a gas day. The unavailableCapacity shall be reported with a GWh/d unit.

In the example provided above one lngUnavailabilityReport shall be sent to the Agency:

lngUnavailabilityReport

  • unavailabilityStart: 2015-11-07 01:00 – unavailabilityEnd: 2015-08-18:00
  • unavailableCapacity: 6,78 GWh/h*24h/d=162,72 GWh/d

2. Inside Information

This is one event:

  • Event start: 2015-11-07 01:00 – Event stop: 2015-11-08 18:00
  • the unavailable capacity is 6,78 GWh/h = 6,78 GWh/h*24h/d = 162,72 GWh/d

Please note the recent update of the MoP on data reporting v 4.0; the GWh/d unit can be selected for LNG deliverability restrictions events.

 

RSS_Icon Last update: 18/05/2017  

FAQs on fundamental data and inside information – Question III.5.1.1

Are message versions 100% immutable or not? Is it possible to update the status of a message by updating the status of the latest thread item?


Answer:

Published versions of the messages are 100% immutable and any change that may occur needs to be published as a new updated version. Any update or change in the data fields – including Data Field (2) Event Status – will result in a new message, with a new ‘Version number’.

RSS_Icon Last update: 31/03/2016  

FAQs on fundamental data and inside information – Question III.5.1.2

Shall the version number – that is part of the ‘Message ID’ – be incremented with any update to the UMM thread? If so, will the increment of version number always result in a new UMM published to RSS/Atom feed?


Answer:

As explained in the MoP Annex VII each ‘Message ID’ includes 29 characters in total and consists of 3 parts:

  • ‘UMM thread ID’ – 25 characters
  • One underscore (‘_’)
  • ‘Version number’ – 3 characters

Underscores (‘_’) should not be used within the 25 characters of the UMM thread and also it shall not be possible to submit a message with a ‘Message ID’ of less than 29 characters in total.
Any change in the UMM results in a change on the ‘Message ID’. If the same UMM thread is considered, the change will impact the last part of the ID which is the UMM ‘Version number’. It is the responsibility of the reporting parties to put in place appropriate arrangements ensuring proper sequencing of this number.

RSS_Icon Last update: 31/03/2016  

RSS_Icon Subscribe to this Category’s RSS