What is an IT carrier for TenneT, and which IT carriers can a Dutch BRP use?
Short answer: An IT carrier sends and receives a BRP's daily messages with TenneT, such as nominations, allocations and imbalance data. TenneT registers every carrier, so it knows who acts for which BRP. The BRP stays responsible for the data. Several companies act as carriers for Dutch BRPs; they differ in API, scope and price.
What does an IT carrier do?
Every BRP exchanges messages with TenneT every day, through the MMC-hub web service in XML. An IT carrier takes over that connection. It builds and runs the integration, holds the transport certificates, follows TenneT's changes, and passes the data on to the BRP's own systems.
TenneT is clear on one point: the BRP remains responsible for the data at all times. A carrier is a service, not a transfer of responsibility.
How does registration work?
TenneT keeps a register of IT carriers. You tell TenneT which carrier works for you with the IT carrier registration form; the conditions are in TenneT's IT carrier leaflet on MyTenneT. Certificates split cleanly:
- Signing certificates (S/MIME): provided by the BRP.
- Transport certificates (SSL): provided by the IT carrier.
Do you need one?
You can connect to the MMC-hub yourself. Then you build the web service client, order four certificates, pass all qualification scenarios and keep up with every change TenneT makes. That makes sense with your own development team and a long horizon. Most new BRPs, and most battery and flexibility companies, use a carrier so their team can focus on trading and assets.
Carrier or own integration?
Provider | Covers | Integration | Notes |
|---|---|---|---|
| Engrate | Nominations, allocation, settlement, reconciliation, GLDPM; also DE and SE | REST API, console | Runs the TQF qualification scenarios for the BRP |
| Own integration (DIY) | Everything you build | Direct MMC-hub client | Full control, full maintenance |
How to choose
Four questions decide it:
- API or files? If your trading and asset systems are software, you want an API, not a portal with uploads.
- Which processes? Trade-only BRPs need fewer processes than BRPs with grid connections and GLDPM.
- Who runs the qualification? Some carriers leave the TQF scenarios to you. Some run them.
- One country or several? If Germany or Sweden is next, one platform saves a second project.
Switching later is possible. See how to switch IT carrier without downtime. What Engrate covers as IT carrier: Energy Market Communication.