Operations / Dispatch
Understanding Dispatch Instructions
Depending on the market, Flexibility Service Providers (FSPs) will receive dispatch instructions via Piclo. This article explains how dispatch works on Piclo, the key differences between markets, and the actions FSPs need to take.
Markets with dispatch
| Market (Region - SO - market) | When | Action required |
| UK - NESO - LCM intra-day | SO evaluates bids between 10:00 and 13:00 UK local time | FSP needs to accept/request dispatch within 1h |
| UK - NESO - LCM day ahead | SO evaluates bids between 18:00 and 21:00 UK local time | FSP needs to accept/request dispatch within 1h |
| UK - SPEN - Month ahead | When SO evaluates bids in the third week of the given month | FSP needs to accept/request dispatch within 48h excluding weekends/holidays |
| UK - SPEN - Long term | Dispatch instructions are uploaded to Piclo | No action required as dispatches were agreed off-platform |
| CT - Eversource and UI (Operational utilisation) | As and when SO issues dispatches based on contract | FSP needs to accept/request dispatch within 4h |
Receiving dispatch instructions
Dispatch instructions are sent via email, either individually or as a summary. The can also be retrieved via API or webhook.
Which Email are dispatch instructions sent to?
Dispatch instructions (both individual and summary emails) are sent to the organisation’s email address provided during registration. To update this email address, please contact support at support@piclo.energy.
Accepting or rejecting dispatch instructions
For markets requiring a response, FSPs can log in to their Piclo account to view all upcoming dispatches. Dispatches can be accepted or rejected in bulk using the UI or API.
If a dispatch instruction is not responded to within the required time frame, it will expire.
Stop instructions
System Operators may issue stop instructions for accepted dispatches. In such cases, FSPs are notified via email, and the UI and webhook/API will be updated accordingly to remove the upcoming instruction.
What to do if you can no longer fulfil a dispatch?
FSPs can update their asset's availability by declaring Unavailability (Manage > Contractual Obligations > Send unavailability notification). This sends an email to the System Operator to notify them.
Key tips:
- Test dispatch and build automations using Piclo's experience environment.
- Ensure dispatch instructions are sent to the correct email address.
- Monitor the time frames for accepting or rejecting dispatches to avoid automatic expiry.
- Keep your asset availability updated to prevent any issues fulfilling dispatch instructions.