3.1 Standard cases for reporting events
The following table gives an overview of the standard cases for reporting events:
Reporting Object | Status as proposed by REMIT | Status according to PRISMA | Further Details |
Order (Trade Proposal) | new | open | - FCFS / CFO only
- Order report is sent when the trade proposal has been published on the platform
|
modify | N / A | - It is not possible to modify a trade proposal after it has been published on the platform
|
N / A | fulfilled | - A trade proposal has the status fulfilled if the offered / requested capacity of the trade proposal is completely covered (runtime and amount) by trades that have the status finished
- No further order report is needed since all information will be provided within the trade report
|
Reporting Object | Status as proposed by REMIT | Status according to PRISMA | Further Details |
Order (Response) | new | (no explicit status) | - CFO only
- order report is sent after the response has been submitted by the responding Shipper
|
modify | N / A | - It is not possible to modify a response after it has been submitted to the platform by the responding shipper
|
Trade | modify | N / A | - Not applicable; a trade cannot be modified
|
new | finished | - A trade report will be sent after the trade has been approved by the Transmission System Operator(s) and therefore has changed its status to finished
|
According to REMIT an order / trade report will also be required to be transferred to ACER in the event of
- a modification of details of a previous trade or order report (amendment of one or more terms of the original agreement or any other information previously reported), which will be identified as ‘modify’;
- a cancellation of a wrongly submitted trade or order report, which will be identified as ‘error’; and
- an early termination of an existing contract or order to trade, which will be identified as ‘cancel’.
Since status changes executed on the PRISMA Platform may be designated using the same terms TEMIT is referring to, there might still be difference with respect to understanding.
3.2 Error cases for reporting events
The following table gives an overview of the status of error cases for which reporting is required as proposed by REMIT set against the respective status of the reporting object on the PRISMA Platform.
Reporting Object | Status as proposed by REMIT | Status according to PRISMA | Further Details |
Order (Trade Proposal) | error | cancelled | - Cancellation due to technical problem
|
cancel | withdrawn | - FCFS / CFO only
- A trade proposal has the status withdrawn after the initiating shipper withdraws the trade proposal. A trade proposal can only be withdrawn until one of the corresponding trades has a final status or until a response has been accepted, either by the initiating shipper (CFO) or the platform (FCFS)
|
cancel | expired | - FCFS / CFO only
- A trade proposal has the status expired after the date of trade proposal expiration as defined by the Initiating Shipper has been reached without any corresponding trades being created and approved by all involved Transmission System Operator(s)
|
cancel | rejected | - FCFS / CFO only
- A trade proposal has the status rejected if the Transmission System Operator(s) do not accept the trade proposal. A trade proposal can only be rejected until at least one corresponding trade was approved
|
Reporting Object | Status as proposed by REMIT | Status according to PRISMA | Further Details |
Order (Response) | error | cancelled | - Cancellation due to technical problem
|
cancel | withdrawn | - CFO only
- The response has been withdrawn by the responding shipper
|
cancel | expired | - CFO only
- A response has the status expired if the trade proposal has been fulfilled by another response (which has been accepted by the initiating shipper and the respective trade has been approved by all involved Transmission System Operator(s)) or after the date of trade proposal expiration as defined by the initiating shipper has been reached without any corresponding trades being approved by all involved Transmission System Operator(s)
|
cancel | rejected | - The response has been rejected / not accepted by the initiating shipper
|
Reporting Object | Status as proposed by REMIT | Status according to PRISMA | Further Details |
Trade | error | cancelled | - Cancellation due to technical problem
|
cancel | rejected | - The trade has been rejected by the Transmission System Operator(s)
|
cancel | expired | - A trade has the status expired if the response has not been accepted by the initiating shipper until either the initiating shipper acceptance deadline or the trade proposal expiration date was reached, the corresponding trade proposal is fulfilled, or the trade has not been approved / rejected by the Transmission System Operator(s) before the end of the trade validation period.
|
3.3 Lifecycle overview
The following picture summarises all reporting lifecycle events:
