Skip to main content

Reporting Events

Report Energy Management System (EMS) control actions that alter your resource's default behaviour to improve forecast accuracy.

What are Events?​

Events are EMS control actions that change how your resource normally operates. For example:

  • Solar panels curtailed due to negative day-ahead prices
Important

Do not report deviations caused by Powernaut activations. Only report events initiated by your local optimisations.

Why Report Events?​

Our forecasting models predict normal resource behaviour without interventions. To provide accurate forecasts, we need to know when these interventions occur so we can:

  • Train models on clean data (excluding intervention periods)
  • Account for planned changes in our predictions
  • Improve forecast accuracy over time

How to Report Events​

API Endpoint​

POST /v1/connect/resources/{id}/events

Request Format​

Each event report includes:

  • event_type: The type of control action
  • payload: Event-specific data (timing, parameters, etc.)

Example Request​

{
  "event_type": "PV_CURTAILMENT_SCHEDULED",
  "payload": {
    "start": "2025-09-19T08:00:00Z",
    "end": "2025-09-19T17:00:00Z"
  }
}

Supported Event Types​

Photovoltaic Curtailment​

Event Type: PV_CURTAILMENT_SCHEDULED

Report when photovoltaic generation is curtailed for a specific time period (e.g., due to negative day-ahead prices).

Payload:

  • start: ISO 8601 timestamp when curtailment begins
  • end: ISO 8601 timestamp when curtailment ends

When to Report: Report before the curtailment occurs so we can account for it in forecasts.

Example:

{
  "event_type": "PV_CURTAILMENT_SCHEDULED",
  "payload": {
    "start": "2025-09-19T08:00:00Z",
    "end": "2025-09-19T17:00:00Z"
  }
}
Best Practice

Report events as soon as you know they will occur. This gives us the most time to adjust their predictions accordingly.

Last updated on