Register of capacity guarantees

The rules of the capacity mechanism, in their version adopted on 29 November 2016, strengthen transparency arrangements on the exchange of capacity guarantees. Thus, the new rules provide that the prices, volumes and effective dates of all transactions carried out are made public; only the identity of the parties to these transactions remains secret in order to protect the confidentiality of commercially sensitive information. These attributes of the transfer of capacity guarantees, derived from the Register of Capacity Guarantees maintained by RTE (<https://rega-rte.fr>), are available on the Open Data website. The capacity guarantees correspond to a standard unit capacity of 0.1 MW/GC and are valid for a given delivery year (calendar year). A transfer of capacity guarantees (CC): * Occurs through a movement of guarantees from a receivable account (capacity owner) to a creditor account (capacity buyer) * May be effective on the date of seizure or at a later due date (so-called “terms”) * Can be carried out at a price defined between the two parties (capacity transaction) or, under certain conditions, without price (capacity transfer) * In the case of a transaction, the associated price may be a fixed price (in Euro per capacity guarantee) or an indexed price (e.g. on the result of future auctions) Meaning of the STATUT column: the status of a capacity guarantee transfer determines its status in the delivery process. A transaction has “Accounted” status. A forward sale (term transfer or forward transaction) has several possible statutes: * Validated not completed (term transfer validated by both parties but not reached by its due date) * Non-delivered (divestiture validated by both parties, reached its maturity date but not reconciled with a cash transfer) * Completed and delivered (deferral validated by both parties and reconciled with a cash transfer) **This dataset is updated once a week on average: due to excessive downloads of data from the registry of robot capacity guarantees at frequencies disproportionate to the frequency of update of the dataset, a quota of 50000 API calls per user per month has been set up. If you notice any concerns regarding access to the data following the introduction of this quota, please contact us at [[email protected]](mailto: [email protected] )** * * *