Skip to content

Knowledge

How does a BSP in the Netherlands find out the BRP of each connection?

Short answer: For aFRR, and as far as we can see mFRRda, TenneT needs the BRP of every connection in a BSP's pool, before the first registration. For FCR it does not. A BSP cannot look the BRP up on its own. It gets it from a partner supplier or BRP, by mapping each connection's supplier to its BRP (the household can share the supplier through Het Normo since 2026), or by correcting what BRPs flag. For wholesale demand response, the Energiewet also requires an agreement with every BRP involved.

Author: Rainer Notter, Product Director at Engrate.

Which products need the BRP per connection?

Product
BRP per connection
Why
FCRNoTenneT verifies with allocations, measurements and baselines per unit or group. No imbalance correction for FCR energy
aFRR, classic routeYesTenneT corrects each BRP's imbalance after activation, using the pool configuration
aFRR, Crowd Balancing PlatformYesThe BRP is given when each grid connection point is registered
mFRRdaAs far as we can see, yesTenneT's BRP messages are set up to carry mFRRda as well

Where it goes in the messages

  • Classic aFRR: the BSP sends a pool configuration to TenneT over the MMC-hub. Each connection (EAN18) carries its BRP's EAN13 in the field ResourceProvider, which is mandatory. Watch out: in the messages TenneT sends to the BRP, the same field carries the BSP.
  • CBP: each grid connection point is registered with its EAN18 and the BRP's EAN13. The CBP builds the pool configuration every day at 12:00.

If a BRP finds a connection that is not theirs, it contacts the BSP, and the BSP has to get it corrected with TenneT.

Who may look up the BRP?

The connection register records, per allocation point, which BRP is active there. Access is for the parties active on the connection. A BSP has no general right of its own. Whether an aggregator that registers itself as active on an allocation point also receives the BRP through the system processes is not settled yet. The draft data regulation under the Energiewet records the BRP for each allocation point, but the market participants it lets register as active there do not include demand response aggregators or BSPs. Its consultation closed on 4 October 2026, and no date of entry into force is set.

Wholesale demand response needs a contract with every BRP

The Energiewet (article 2.41) says that a market participant that is not also the supplier on an allocation point may only provide demand response there with an agreement with that allocation point's BRP, based on a reasonable offer the BRP must make on request. This does not apply when the market participant provides services to the transmission or distribution system operator for system needs, such as balancing for TenneT.

How Engrate does it

Engrate keeps the BRP per connection right for BSPs: consent at sign-up, a maintained supplier-to-BRP map, and clean handling of BRP corrections. As a registered TenneT IT carrier we send the BSP messages in the BSP's name. More: Energy Market Communication.

Sources

Questions

Short answers

Does a BSP need the BRP per connection for FCR?

No. TenneT checks FCR through allocations, measurements and baselines per unit or group, and does not correct the BRP's imbalance for FCR energy.

Where does the BRP go in TenneT's aFRR messages?

In the classic route, in the pool configuration per connection, in the field ResourceProvider (the BRP's EAN13). On the Crowd Balancing Platform, when registering each grid connection point.

Can a BSP look up the BRP in the connection register?

Not on its own account. Since 2026, a household can consent through Het Normo's portal to share connection data with a service provider, but Het Normo's data products name the supplier, not the BRP.

Does an independent aggregator need an agreement with each BRP?

For demand response on the wholesale market, yes: the Energiewet requires an agreement with the BRP on each allocation point. Not when the aggregator provides services to TenneT or a grid operator for system needs.

We use cookies for analytics, session recordings and advertising measurement: which pages get read, and whether a visit leads to a conversation. Nothing is stored on your device unless you accept. Privacy policy