Upozornění: Text přílohy byl získán strojově a nemusí přesně odpovídat originálu. Zejména u strojově nečitelných smluv, kde jsme použili OCR. originál smlouvy stáhnete odsud
All NEMO Intraday Operational Agreement - Annex 6: Technical requirements
Confidential
All NEMO Intraday Operational Agreement (ANIDOA)
ANNEX 6
Technical requirements
1
All NEMO Intraday Operational Agreement - Annex 6: Technical requirements
Confidential
I.- Introduction
This Annex 6 (Technical requirements) to the Agreement contains technical requirements related to the
Agreement.
For the purpose of this Annex, all capitalized terms not expressly defined herein shall have the meaning
attributed to them in Annex 1 (Definition list).
Section L- Comunication Network & Rack Space
Section II. Technical provisions regarding PMI
Section II.l- PMI Interface
All NEMO Intraday Operational Agreement - Annex 6: Technical requirements
Confidential
6: The XBID PMI upgrade process shall apply in the same way for both ordinary release upgrades as emergency
upgrades.
7i All information concerning the XBID PMI upgrade shall be shared in hill transparency between all NEMOs
and the XBID System Service Provider.
8: All change requests should contain a section which will evaluate an impact on PMI for change and release
management.
Section II.2- PMI logger
The NEMOs support the usage of the monitoring tool provided that the cumulative conditions set forth in this
section are complied with.
These conditions are deemed necessary since representatives of the NEMOs will have access, for the purpose of
the monitoring of the functioning of the XBID Solution, to information about:
i) each order (price and quantity);
ii) the type of product; and
iii) the NEMO on which order was submitted.
Any access to additional information shall be subject to a NEMO ID SC decision.
This data constitutes Confidential Information, is commercially sensitive and competition law can require certain
restrictions in terms of access and usage. Specifically, any exchange of information between competitors triggers
a competition law risk that depends on the following criteria:
i) the historicity / accuracy of the data;
ii) individualised / aggregated data.
1. Authorised usage
Apart operations, the use of market data, incl. PMI logging output files, will only be authorized for the
monitoring purposes (potential additional usages shall be subject to a NEMO ID SC decision). The authorized
usage of the monitoring tool will be limited to:
i) monitoring of the performance of the XBID System;
ii) monitoring of the compliance of each Party with the prohibition to connect more than one LTS to the
XBID System; and
iii) monitoring whether only agreed fields of the messages are used.
2. Authorised users
Access shall be restricted to a list of authorized users, which need to be associated to respective working
group/role in the concerned NEMOs. The list shall be uploaded on the specific “NEMO only” section of the
online storage tool called “Projectplace” or a similar tool, where the information will be accessible to all NEMOs
at the same time.
In respect of the disclosure of data, the Parties shall comply with the provision on the disclosure of Confidential
Information set forth in Article 29 (Confidentiality) of the Agreement. In addition, any other measure of
restriction necessary to prevent the disclosure of data within each company shall apply.
3. Report
The report shall be generated in an automated way and the template shall be jointly agreed among the NEMOs.
The purpose of the report is to present the results to a wider audience (e.g. NEMO ID SC members).
The expectation is that the report shall:
i) contain only non-individualised data (NB. individualized data is not available in first instance but no
PXshould be forced to reveal it); and
ii) focus on the purpose of the reporting (eg. no reference to a specific order or any information that could
be used from a business point of view).
3
All NEMO Intraday Operational Agreement - Annex 6: Technical requirements
Confidential
4. Grace period
The duration of the grace period is 2 days, after this period this data will be available for all Operational NEMOs
at the same time.
Section III. Technical provisions regarding day to day operation
Section III.l Number of XBID-API SOB PMI Exchange Users
Except if otherwise agreed in writing between the Parties (including by way of a NEMO ID SC decision), each
Party can have only one (1) primary XBID-API SOB PMI Exchange User to connect to the XBID System as well
as only one (1) backup XBID-API SOB PMI Exchange User to be used in case of technical problems with
primary XBID-API SOB PMI Exchange User. Only one (1) XBID-API SOB PMI Exchange User can be logged
into the XBID-API SOB PMI at the same time.
Section III.2 Restriction on unsupported data use
The Parties agree not to make use of any XSD messages or message fields or fields values that are not described
in the DFS510 - AMQP Public Message Interface - Trading XBID-API SOB PMI specification. In case of breach
of this commitment by a Party, Article 30,2,9 of the Agreement shall apply.
Section III.3 Communications between the LTS and the XBID System
All communication between LTS and the XBID System shall be done in an anonymized manner. Data should be
anonymized, based on the standards used in the single day ahead market coupling and legal requirements (e. g. the
CACM Regulation).
Section III.4 Access to NEMO Central Admin
To the extent all Operational NEMOs shall be technically granted access to the SOB and SM via the Central
Admin profile it received, it is understood that only one Operational NEMO at the time shall be authorised to
perform the tasks related to the NEMO Central Admin role.
As a result of the access to the SOB and SM, each Operational NEMO has the technical possibility to access the
configuration parameters of the Parties.
Each Operational NEMO undertakes that as long as it is not performing the NEMO Central Admin role, it shall
neither access nor modify the configuration parameters of the other Parties and it shall take all necessary and
appropriate measures and shall ensure that the configuration parameters of the other Parties are not accessed nor
modified.
The NEMO performing the tasks of the NEMO Central Admin can change the configuration parameters of
another NEMO only in the cases permitted according to Annex 7 (NEMO Operational Procedures), in particular
in the document with the title ‘X B ID N E M O O T H 0 3 - XBID NEMO Admins”. The NEMO Central Admin
shall take all necessary and appropriate measures and shall ensure that the configuration parameters of the other
Parties are not changed, in other cases than those permitted according to Annex 7 (NEMO Operational
Procedures), in particular in the document with the title ‘X B I D N E M O O T H 0 3 - XBID NEMO Admins”.
Section III.5 Dispute button
The Dispute button functionality of the XBID System (Dispute management) allowing for disconnecting another
Party, will not be used.
Section IV. REMIT reporting
In accordance with Article 17,4 of the Agreement, the Parties shall take into account the table below when
fulfilling their reporting obligations under REMIT.
4
All NEMO Intraday Operational Agreement - Annex 6: Technical requirements
Confidential
Table 1 - REMIT reporting
T itle D escription
Contract naming ContractID & ContractName are unique per organised market place,as defined in
Implementing Regulation 1348/2014 of 17/12/2014 on data reporting implementing
Reporting of User article 8.2) and 8.6) of Regulation (EU) No 1227/2011 of the European Parliament and of
defined blocks the Council on wholesale energy market integrity and transparency. As each NEMO is a
separate Organised Market Place this does not have to be aligned. In case of a cross-
NEMO trade, the delivery period of the linked contract must of course be the same for
each NEMO.
User defined blocks (UDB) in the XBID System consist of a consecutive series of
underlying hourly base contracts. When reporting orders & trades for these UDB two
supported approaches are recognized:
1. Report UDB sliced to its underlying contracts
This means an order/trade on a UDB will be reported as separate orders/trades on the
hour contracts that the user defined block is constructed off
2. Report UDB as additional contracts
This means that for every unique UDB for which at least one order/trade has been
entered an extra contract is added to the REMIT report. The orders & trades on this
UDB are then linked to this contract without slicing
Trade > Unique Both options are supported in REMIT reporting. NEMOs participating in SIDC should
transaction use one of these approaches in their REMIT reporting of SIDC orders and trades on UDB.
identifier The unique transaction identifier, as defined in the annex to Implementing Regulation
1348/2014 of 17/12/2014 on data reporting implementing article 8.2) and 8.6) of
Regulation (EU) No 1227/2011 of the European Parliament and of the Council on
wholesale energy market integrity and transparency, naming convention should be aligned
between the NEMOs in case of a cross-NEMO trade.
Additionally the "additionalUtilnfo" element should be used to allow ACER to link cross-
NEMO trades, where each half trade is reported by a different Organised Market Place.
This element should contain the same value for all trades done in the XBID System.
T radeR eport/uniqueTransactionldentifier/additionalU tilnfo:
XBID
Trade > The timestamp of trades must be aligned among the NEMOs. Therefore the execution
Transaction
timestamp time as provided by the XBID System must be used
Section V. Monitoring of the performance of the XBID System
The performance of the XBID System will be closely monitored with regard to the SLA and/or system
boundaries as well as the technical capability of the XBID System.
5
All NEMO Intraday Operational Agreement - Annex 6: Technical requirements
Confidential
1. In case any underperformance is identified (at the latest based on the monthly SLA reports), the
Operational NEMOs will raise the matter and organise immediately a joint discussion among the
Operational NEMOs in order to identify measures which will ensure robust operation. All products and
product’s parameters will be subject of the discussion in the following order:The parties commit to
enter in negotiations with the XBID System Service Provider to solve the issue and find a technical
solution, covering all parameters which could be revised with the aim to achieve a robust operation.
2. If the underperformance is caused by a particular product or product’s parameter, then the Parties agree
that the products and/or modification of product’s parameters causing the underperformance will be
removed from operations as of the next delivery day and until a technical solution is reached.
6