Expand description
BDEW Rollenmodell — market-participant role configuration.
The BDEW Rollenmodell für die Marktkommunikation (V2.2, January 2026) explicitly permits a single legal entity to hold multiple market roles simultaneously. Common combinations:
| Combination | Regulatory basis |
|---|---|
| NB + gMSB | §41 MsbG — NB is grundzuständiger MSB for basic meters |
| NB + BKV | Stadtwerke managing their own balance group |
| NB + LF | Vertically integrated utility |
| LF + BKV | Supplier managing its own balance group |
§Why role-awareness matters for PID routing
Several EDIFACT PIDs are shared across process families and their correct
inbound destination depends on which role this makod instance fills:
| PID | ORDRSP semantics |
|---|---|
| 19001 (Bestellbestätigung) | → gpke-konfiguration when NB receiving from MSB |
| 19001 (Bestellbestätigung) | → wim-geraeteubernahme when nMSB receiving from NB |
| 19015 (Bestätigung Gerätewechselabsicht) | → wim-geraeteubernahme when NB receiving from nMSB |
| 13003 (MSCONS Summenzeitreihe) | → mabis-billing when BKV receiving from BIKO |
| 13003 (MSCONS Summenzeitreihe) | → MaBiS NZR handler when NB receiving from NB |
By declaring which roles a makod instance serves, the engine can register
only the PID routes that apply, preventing both silent dead-letters and
accidental misrouting.
§Conflict guard
PidRouter panics at build time if two modules register the same PID to
different workflow names. Set explicit DeploymentRoles to exclude
conflicting registrations from modules that don’t apply to this instance.
Structs§
- Deployment
Roles - The set of
Marktrolles thismakoddeployment fills.
Enums§
- Marktrolle
- A BDEW market-participant role (Marktrolle).