MCC BDEW-API for suppliers, grid operators, and MSBs
Scenario for on-premises operation of the MCC BDEW API – also available as a service at DARZ (© MTG AG)
Operating Models: On-Premises and Managed Service
The solution offers maximum flexibility in deployment and adapts to the individual infrastructure and security requirements of market participants:
On-Premises Operation
For customers – such as grid operators – who prefer to operate and control the MTG CryptoController (MCC) and its associated components within their own IT infrastructure.
Managed Service (energy@Web-API Services at DARZ)
Alternatively, the BDEW Web API is available as a full-service solution. Operations take place in the highly secure data center of our long-standing partner, DARZ GmbH. This approach minimizes the customer’s own operational and maintenance efforts while ensuring maximum regulatory compliance.
BDEW Web API Identifiers API 0001, API 0002, and API 0003
In accordance with Federal Network Agency specification BK6-22-128, the BDEW has specified a Web API and a directory service. The goal is to standardize the exchange of information in the energy sector in a manner that complies with data protection regulations and ensures interoperability. Communication is based on certificates from the Smart Metering PKI (SM-PKI) in accordance with the requirements of the corresponding Certificate Policy (CP).
The MTG CryptoController (MCC BDEW-API) fully implements these regulatory requirements and extends the system and its interfaces to meet new market demands.
Core Functional Components of the Web API
The MCC extension covers the key energy industry processes and API identifiers:
- API0003 (LFW24): Secure retrieval of the MaLo ID as part of the accelerated 24-hour supplier switch.
- API0001 & API0002: Secure and compliant transmission of switching commands by suppliers and grid operators to the responsible metering point operator (MSB) in accordance with the universal processes (BK6-22-128).
- Future-proof: API identifiers and extensions specified by the BDEW in the future can be flexibly integrated into the MCC platform.
Architecture and Integration Concept
The MCC’s architectural approach is based on a strict separation of the application and security layers. All cryptographic and regulatory requirements are centrally encapsulated by the MCC middleware.
MCC in the OSI Reference Model according to BSI TR-03109 in the BDEW Web API (© MTG AG)
Advantages of this architecture
Low complexity: Existing applications (e.g., ERP systems for supplier switching or grid control center and management applications) connect to the MCC via simple, standardized interfaces.
Focus on process logic: Line-of-business applications do not need to implement complex SM-PKI functionalities or security mechanisms themselves.
Centralized security: The MCC handles TLS-secured communication, certificate validation, signature verification, and the necessary encryption and decryption processes in accordance with BDEW specifications and the Smart Meter PKI Certificate Policy.
Flexibility in the Directory Service
The MCC’s integrated directory service ensures that market participants can manage and retrieve the address and certificate data required for interoperable information exchange in compliance with the BDEW API. The architecture offers maximum flexibility for different IT infrastructures and service scenarios:
Integrated BDEW API Directory Service
Support for Third-Party Systems (External Services)
Intelligent Redirection (Redirect Function)
Multi-provider scenarios for market partners