Reported issue ID: 02/2019
BRS for balancing
by Equinor ASA
Abstract
The business requirements specification for nomination and matching procedures is referencing the Network code on Gas Balancing of Transmission Networks but is only decribing small parts of the network code. This can create a situation where TSO's think they are compliant with the network code by implementing what is included in the nomination and matching BRS but that is only covering the nomination and matching process and is missing out on many of the other balancing parts.
Category: European
Reported issue
In our opinion the BRS is missing descriptions on how to handle the withinday obligations described in article 25, 26, 28, 29, 30, 31, and 32-39 of the network code.
Today information given to network users are many times based on information on websites instead of using edig@s. It will also be a big improvement if all processes that already is covered by edig@s is harmonised.
Concerned entities
Network Code on Gas Balancing of Transmission Networks, Commission Regulation (EU) 2014/312
- Austria
- Belgium
- Bulgaria
- Croatia
- Cyprus
- Czech Republic
- Denmark
- Estonia
- Finland
- France
- Germany
- Greece
- Hungary
- Ireland
- Italy
- Latvia
- Lithuania
- Luxembourg
- Malta
- Netherlands
- Northern Ireland
- Poland
- Portugal
- Romania
- Slovakia
- Slovenia
- Spain
- Sweden
- United Kingdom
None selected
Notified parties
None selected
None selected
Suggested actions
- ACER
- ENTSOG
- Adjustement of implementation
comments (0)
IP's concerned
IP |
---|
Informed TSO's
TSO |
---|
Informed NRA's
NRA | Country |
---|
Uploading file
Warning!
You are about to add a file to comment
Please note the file will be visible to all the users and visitors of the Platform
Do not add any confidential documents.
Press "OK" if you still want to add a file, otherwise click "Cancel"
Solution
With reference to the solution supporting documents below, it has been found that amending the existing BRS for Nomination and Matching or drafting a new BRS is not warranted at this point in time.
Adopting a Union-wide data exchange format could however bring benefits for the parties involved in the balancing processes. Therefore, ENTSOG have issued a recommendation note addressed to TSOs recommending the use of the latest version of edig@s® format, currently edig@s® 6.1 version.
ACER and ENTSOG have concluded that the recommendation note issued by ENTSOG on the adoption of edig@s® 6.1 is an appropriate solution to the issue request, given the current regulatory framework of both INT&DE NC and BAL NC allowing for different data exchange solutions.