Skip to main content

​
The problem

Every balance responsible party (BRP) and supplier exchanges messages with the market around each delivery day. Before the day, you send your schedule. After the day, the market tells you how much energy it allocated to you. As a supplier, you also take over accounting points from other suppliers. The work is the same in every market. The way you do it is not:
  • Roles: the Scheduling Area Responsible that receives your schedule is one of four TSOs in Germany, TenneT in the Netherlands, and eSett in the Nordics.
  • Formats and channels: in Germany, ESS XML for schedules and EDIFACT for supplier switches and metering data. In the Netherlands, CIM XML through the TenneT MMC Hub.
  • Identifiers: EIC codes in Germany, EAN-13 codes in the Netherlands, and a different scheme again for accounting points.
  • Rules and deadlines: when gate closure is, how the market matches your schedule against your counterparty’s, and when a value becomes final.
A company active in two markets builds and runs two integrations, and keeps two mental models.

​
Our approach

Engrate gives you one model and one API for all markets.
  • One model. Schedules, revisions, series, allocations and their finality mean the same thing in every market. Each market fills the same roles with its own parties. See Roles and areas.
  • State, not messages. You tell Engrate what you want the market to hold. Engrate sends what is necessary, reads every answer, and gives you the market’s view as state: is each series matched, which values are confirmed, how final is each volume.
  • The market’s own words, kept. Engrate keeps every market message and the market’s own codes, so you can always trace a value back to what the market said.
Only what is market-specific stays visible: identifiers, deadlines, and the market’s own reason codes.

​
What do you need to do?