SuspendAOFResult
Change Log
| Date | Author | Comments |
|---|---|---|
30.05.2024 |
Bent Atle Bjørtomt |
Reviewed and removed Draft notes. |
Introduction
Suspend AOF result is a check that all Nordic TSOs must exchange with each other, to confirm or reject AOF Result. By default, a positive exchange is expected. If message is not received before order BSP activations process (between QH-13 to QH-9) then it will be perceived as a positive response, in other words an acceptance of the AOF Result.
If a negative exchange from one or more TSOs, then each TSOs must use a fallback solution,see <<Definitions>
Business process
The SuspendAOFResult BRS is connected to the main process For scheduled activation in AOF with its sub process Activation and Validation of AOF Result
Following subsections describe the process flow for SuspendAOFResult.
|
Please note that a Sanity Check should always send SuspendAOFResult message to Confirm or reject. |
The AOF Result from Nordic Libra is published T-13 minutes before activation time. SuspendAOF should be returned between T-12 to T-10 minutes, this not yet decided and can be subject for change.
Use case and scope for SuspendAOFResult
Following diagram show the two use cases that can be exchanged with SuspendAOFResult TSO Message.
It is an answer on the result from AOF(MOL AOF) or an absent result from AOF.
Business process model
This is an overall draft of the business processes and the usage of SuspendAOFResult.
Requirements
| Req.no. | Message Object | Sending frequency | Resolution | Period | Area | Comments |
|---|---|---|---|---|---|---|
BR-SAR-1 |
Each MTU, event |
PT15M |
15 Min |
Synchronous Area |
Must be provided by each TSO after each MOL AOF(QH-13) before BSP activation (QH-9). |
What can lead to a negative Suspension of AOF Result:
Following reasons should be covered.
-
If at least one TSO is missing AOF result.
Correspond to Suspend Reason code 002 in list below. -
If AOF Norodic Libra send specific problem statement documents to all TSOs
Correspond to Suspend Reason code 003 in list below.-
A control area is disconnected/decoupled and the PSD for this is received later than T-30.
-
The Libra Optimization Module (LOM) fails
-
The LOM doesn’t return unconstrained (UC) result
-
-
If one of the following sanity check fail for at least one TSO:
Correspond to Suspend Reason code 004 in list below.-
Cross border flow for a bidding area connection is less or equal to ATC sent in by TSO
-
Sum of satisfied and unsatisfied demand for a bidding area is equal to mFRR request sent in by TSO
-
Sum of activation in one Bidding Zone(BZ) is equal to sum of satisfied demand and export to other BZ
-
Sum of selected bid volume from one BZ is less or equal to bid volume available for AOF
-
The marginal price of a bidding area with upward activation shall be equal to or higher than the most expensive bid selected within the respective bidding area (reverse in case of downward activation)
-
-
Manual suspend if operator identify that wrong data is used as input.
Correspond to Suspend Reason code 004 in list below.
Actions if rejected AOF Result
What is 1. level fall-back?
Each TSO:
-
Select bids from own control area.
-
Cover own demand for next quarter-hour.
-
mFRR request shall be adjusted with energy exchange from/to other control area in current quarter-hour.
-
Energy exchange to be used is from scheduled activation result for current quarter-hour and is limited by ATC for next quarter-hour.
When to revert to normal and start use AOF?
-
If suspension is due to reason 3 (code 004) or 4 (code 005), revert to normal is a manual decision coordinated between all TSOs and CSP.
-
If suspension is due to reason 1 (code 002) or 2 (code 003), all TSO will automatically (try to) use AOF result for next quarter-hour.
-
If suspension is due to reason 1 (code 002) or 2 (code 003) and the same reason caused suspension in the previous quarter-hour, revert to normal is a manual decision coordinated between all TSOs and CSP.
When to go to 2. level fall-back?
-
If it is not possible to continue 1. level fallback due to the situation in the power system, and it is not possible to start using the AOF again, than all TSO must go to 2. level fall-back.
What is 2. level fall-back?
-
Select bids from own control area.
-
Cover own demand for next quarter-hour.
-
mFRR energy exchange can be manually agreed bilateral.
Reasons for 1. level fallback and criteria for suspension:
-
Automatic response for the first quarter-hour.
-
Keep energy exchange: to minimize stress on power system from sudden large changes in energy exchange.
-
Reduce the number of messages and "hand-shakes compared to previous suggested solutions:
-
Minimize probability for suspension due to communication issues when all TSOs has received AOF-result.
-
Avoid unnecessary message exchange.
-
Change Log
| Ver | Changed by | Date | Changes |
|---|---|---|---|
1 |
Bent Atle Bjørtomt |
2024.05.30 |
PSD document verified ok and removed status text "Draft". |
More details can be found here,Suspend AOF Result.
A short overview of the PSD produced by Nordic Libra. The codes used are as follows:
-
type=A34: Escalation
-
type=A35: Trouble shooting
-
code=B11: Cooperation area problem
-
code=A91: Expected data not received
-
code=B18: failure
| TSO rule | Result in SuspendAOF | Event | Time of sending | To | Type | expected_MarketDocument | Reason | ||
|---|---|---|---|---|---|---|---|---|---|
type |
processType |
code |
example |
||||||
DK: |
NO |
A control area is disconnected/ decoupled (planned) |
T-50 |
All |
A35 |
A35 |
A47 |
B11 |
<Reason> |
DK: |
YES |
A control area is disconnected/ decoupled on-the-fly |
change time |
All |
A35 |
A35 |
A47 |
B11 |
<Reason> |
DK: |
YES |
A control area has been implicitly decoupled. (The ATC has been set to 0 in the input message) |
Gate Closure (std setup T-10) |
All |
A35 |
A35 |
A47 |
B11 |
<Reason> |
DK: |
NO |
Monitored input not received. Normally the TSO will monitor ATC, mFRR Request, mFRR Bids. |
Gate Closure (std setup T-10) |
Input responsible |
A34 |
A31 |
A47 |
A91 |
<Reason> |
YES |
Gate Closure (std setup T-10) |
Input responsible |
A34 |
A31 |
A47 |
A91 |
<Reason> |
||
YES/NO |
Gate Closure (std setup T-10) |
Input responsible |
A34 |
A31 |
A47 |
A91 |
<Reason> |
||
NO? |
ACK on monitored output not received |
Start activation phase (std setup T-7:30) |
All |
A34 |
A34 |
A47 |
B11 |
<Reason> |
|
NO? |
Negative ACK on monitored output received |
Negative ACK received |
All |
A34 |
A66 |
A47 |
B11 |
<Reason> |
|
YES |
The LOM fails |
Clearing (std setup T-10 ++) |
All |
A34 |
A34 |
A47 |
B18 |
<Reason> |
|
YES |
The LOM doesn’t return unconstrained(UC) result |
Clearing (std setup T-10 ++) |
All |
A35 |
A35 |
A47 |
B18 |
<Reason> |
|
Example
<?xml version="1.0" encoding="UTF-8"?>
<ProblemStatement_MarketDocument xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="urn:iec62325.351:tc57wg16:451-5:problemdocument:3:0" xsi:schemaLocation="urn:iec62325.351:tc57wg16:451-5:problemdocument:3:0 xsd/iec62325-451-5-problem_v3_0.xsd">
<mRID>478b5b4a016a4b118371f551e3ba7874</mRID>
<revisionNumber>1</revisionNumber>
<type>A34</type>
<sender_MarketParticipant.mRID codingScheme="A01">10V1001C--000284</sender_MarketParticipant.mRID>
<sender_MarketParticipant.marketRole.type>A35</sender_MarketParticipant.marketRole.type>
<receiver_MarketParticipant.mRID codingScheme="A01">10X1001A1001A264</receiver_MarketParticipant.mRID>
<receiver_MarketParticipant.marketRole.type>A04</receiver_MarketParticipant.marketRole.type>
<createdDateTime>2021-08-30T08:37:31Z</createdDateTime>
<period.timeInterval>
<start>2021-08-30T08:45Z</start>
<end>2021-08-30T09:00Z</end>
</period.timeInterval>
<expected_MarketDocument.type>A34</expected_MarketDocument.type>
<expected_MarketDocument.createdDateTime>2021-08-30T08:35:00Z</expected_MarketDocument.createdDateTime>
<expected_MarketDocument.process.processType>A47</expected_MarketDocument.process.processType>
<domain.mRID codingScheme="A01">10Y1001A1001A91G</domain.mRID>
<Reason>
<code>B11</code>
<text>Acknowledgement for OUT_OFFERS_NEEDS_ACTIVATION_SETTLEMENT sent to 10X1001A1001A264 has not been received.</text>
</Reason>
<Reason>
<code>B11</code>
<text>Acknowledgement for OUT_OFFERS_NEEDS_ACTIVATION_SETTLEMENT sent to 10X1001A1001A248 has not been received.</text>
</Reason>
<Reason>
<code>B11</code>
<text>Acknowledgement for OUT_OFFERS_NEEDS_ACTIVATION_SETTLEMENT sent to 10X1001A1001A38Y has not been received.</text>
</Reason>
<Reason>
<code>B11</code>
<text>Acknowledgement for OUT_OFFERS_NEEDS_ACTIVATION_SETTLEMENT sent to 10X1001A1001A418 has not been received.</text>
</Reason>
</ProblemStatement_MarketDocument>Document types, message types, process types and business types
| MessageObject | Document | Schema | Message type | Definition | Process type | Definition | Business type | Definition | Comments |
|---|---|---|---|---|---|---|---|---|---|
NBM StatusMarketDocument |
Status_MarketDocument |
B32 |
Operational state document |
A47 |
Manual frequency restoration reserve |
- Not in use - |
Code list
Codes to be used with suspendAOF message.
Suspend AOF Result codes
Codes to be used for NBM SuspendAOFResult
SuspendAOFResult codes |
||||
001 |
OK |
The AOF result will be used |
Run as Normal |
suspend_Reason.code |
002 |
Missing AOF Result |
One or more TSOs are missing the AOF result |
Suspend AOF result for all TSOs. Normally go to 1.Level fallback |
suspend_Reason.code |
003 |
PSD |
Problem Statement document is received. AOF Result will not be used. |
Suspend AOF result for all TSOs. Normally go to 1.Level fallback |
suspend_Reason.code |
004 |
Sanity Check failed |
One or more sanity checks failed |
Suspend AOF result for all TSOs. Normally go to 1.Level fallback |
suspend_Reason.code |
005 |
Manual Override |
Suspend AOF result for all TSOs. Normally go to 1.Level fallback |
suspend_Reason.code |
|
.. |
.. |
.. |
suspend_Reason.code |
|