Data Needs

The general concept of data needs is explained in the EDDIE documentation.

AIIDA supports two types of data needs: inbound and outbound. Outbound data needs are used to define the data that AIIDA should provide to EPs, while inbound data needs are used to define the data that AIIDA should consume from EPs.

Fields

Field	Type	Description
type	String	Type of the data need, either outbound-aiida or inbound-aiida.
id	String	Unique id that can be used to reference this data need.
name	String	Short memorable name of the data need that may be presented to the customer.
description	String	Multiline string that describes this data need in a human readable form to be shown in the UI.
purpose	String	Multiline string that describes the purpose of this data need.
policyLink	URL	URL to the data policy that applies to this data need.
enabled	boolean	Enables or disables a data need.
duration	Object	Describes the timeframe for this data need.
transmissionSchedule	String	Cron expression that defines how often the data should be sent or received.
allowedPermissionCommands	String[]	Permission commands the EP may send to remotely control transmission. See Permission Commands. Default [].
acknowledgementRequired	boolean	Whether an acknowledgement is required for the data transmission. See Acknowledgement.
schemas	String[]	Schemas that define the structure and format of the data, e.g. standardized schemas such as CIM or custom schemas.
asset	String	The asset that the data need is associated with, linking the data to specific physical or logical assets.
dataTags	String[]	Data tags that further specify the type of data that is expected.
contexts	String[]	Contexts for permission request that AIIDA can use to provide additional functionality, e.g. flexible connection agreements.

Outbound

NOTE

AIIDA → EP

{
  "type": "outbound-aiida",
  "id": "5dc71d7e-e8cd-4403-a3a8-d3c095c97a84",
  "name": "FUTURE_NEAR_REALTIME_DATA_OUTBOUND",
  "description": "Near realtime consumption data from the smart meter",
  "purpose": "purpose",
  "policyLink": "https://example.com/toc",
  "duration": {
    "type": "relativeDuration",
    "start": "P0D",
    "end": "P10D"
  },
  "transmissionSchedule": "*/5 * * * * *",
  "allowedPermissionCommands": [],
  "acknowledgementRequired": false,
  "schemas": [
    "SMART-METER-P1-RAW",
    "SMART-METER-P1-CIM-V1-04",
    "SMART-METER-P1-CIM-V1-12"
  ],
  "asset": "CONNECTION-AGREEMENT-POINT",
  "dataTags": [
    "1-0:1.8.0",
    "1-0:1.7.0"
  ]
}

TIP

Outbound AIIDA data needs may also include inbound data schemas like MIN-MAX-ENVELOPE-CIM-V1-12 and OPAQUE. This will inform AIIDA that an inbound data source should be selected to forward such messages to the eligible party.

Inbound

NOTE

EP → AIIDA

{
  "type": "inbound-aiida",
  "id": "f7698978-b9fe-40c8-aebe-c997f7f58f2f",
  "name": "FUTURE_MIN_MAX_ENVELOPE_INBOUND",
  "description": "Inbound reference energy curve min-max operating envelopes for flexible connection agreements",
  "purpose": "purpose",
  "policyLink": "https://example.com/toc",
  "duration": {
    "type": "relativeDuration",
    "start": "P0D",
    "end": "P10D"
  },
  "transmissionSchedule": "*/5 * * * * *",
  "allowedPermissionCommands": [],
  "acknowledgementRequired": true,
  "schemas": [
    "MIN-MAX-ENVELOPE-CIM-V1-12",
    "OPAQUE"
  ],
  "asset": "CONNECTION-AGREEMENT-POINT",
  "dataTags": [],
  "contexts": [
    "FLEXIBLE-CONNECTION-AGREEMENT"
  ]
}

Acknowledgement

If the acknowledgementRequired field is set to true, the receiving party (either AIIDA or the EP) is expected to send an acknowledgement message back to the sender after successfully receiving and processing the data. This acknowledgement message serves as a confirmation that the data has been received and processed correctly, and can be used to ensure reliable communication between AIIDA and EPs.

The acknowledgement is available in the outbound connector being used.

For more details, see:

• Acknowledgement Market Document
• EP Subscribing to Acknowledgement

Permission Commands

The allowedPermissionCommands field lists the permission commands the EP may send to remotely control transmission for the permission. A transmission-controlling command is accepted only if it is listed; otherwise it is rejected. The available commands are:

• SET_TRANSMISSION_ENABLED - enables or disables transmission.
• UPDATE_TRANSMISSION_SCHEDULE - adjusts the transmission schedule (capped at the data-need frequency).

For example, "allowedPermissionCommands": ["UPDATE_TRANSMISSION_SCHEDULE", "SET_TRANSMISSION_ENABLED"] allows both commands. If the field is empty (the default []), all transmission-controlling commands are rejected. The TERMINATE command is always accepted, regardless of this field.