Smart energy infrastructure, built and run at scale
From the grid connection to the single reading: batteries, data centers, homes, and the meters and market messages that tie them together. I've run 500,000+ smart meters and about 10 million market messages a week. Scroll to walk the path with me.
01. The grid
Generation, transmission, substation, transformer, a house. Yellow squares are power, blue are data. Utilities run both, and the data side is where rollouts stall.
TRAFO: transformer
02. The battery site
A grid-scale battery (BESS) soaks up surplus power and returns it at the peak. Its energy management system takes orders from the market and the grid operator. Behind a large consumer's grid connection, metering and settlement rules decide whether it may also sell into the market. I've worked that out for Japan.
BESS: battery energy storage system; PCS: power conversion system; EMS: energy management system; TRAFO: transformer
03. The data center
A data center can draw as much as a small city, around the clock, and AI is making them bigger. Grid connections take years, so operators now pair them with batteries, flexible load and waste-heat reuse. A battery behind the same connection needs its own meters to trade, and each of those links is a data and market integration.
UPS: uninterruptible power supply; GEN: backup generator; TRAFO: transformer
04. The metering point
Meter cabinet, rooftop PV, home energy management, an EV charger. Regulation (§14a EnWG, MsbG) now expects all of it to be controllable and billable. I've worked on the rollout side of that.
DSO: distribution system operator; EV: electric vehicle
05. The meter cabinet
Meter, gateway and sub-meters, signed by a security module. I run gateway lifecycle at scale on DLMS/COSEM (IEC 62056) and BSI TR-03109, from commissioning to certification per operator.
WAN: wide-area network; GW: gateway; SUB: sub-meter
06. One reading
A single reading, field by field. The same standard sits under German gateways and Japanese AMI, and I've mapped ECHONET Lite to DLMS/COSEM for a client. Cross-border data access is a protocol problem first.
HDR: header; ADDR: address; OBIS: object identification code; CRC: checksum
Work with me
Remote, or on-site when it's worth it. Bring me a metering, storage, market or grid-data problem. A first call is 30 minutes, no pitch.
9+ years · 500k+ meters · ~10M messages/week · BNetzA / BDEW / VDE FNN committees
- Battery storage (BESS) metering and market access, incl. behind-the-meter sites in Japan
- Smart metering platform architecture and rollout operations
- Market communication (MaKo, EDIFACT/AS4) automation and regulatory mapping
- Gateway (SMGW) lifecycle and DLMS/COSEM integration
- Technical due diligence, and EU–Japan data-access studies
Japanese smart-metering data access, 2025
For a Japanese energy consultancy: mapped the B-route data pipeline and SMDSA intermediary access to EU conventions, identified the ECHONET Lite ↔ DLMS/COSEM translation requirements, and delivered a working proof of concept for HES/MDMS integration. Also compared METI/ANRE AMI policy with the EU SMGW governance model.
Behind-the-meter battery in Japan, 2026
Worked out whether a large battery behind a consumer's grid connection can also sell into the market, checked across TEPCO, Kansai and Chubu: the interconnection requirements, which metering the Measurement Act allows (certified child meters with agreed allocation, not differential metering), and how charging and discharging split across two balancing groups for JEPX and imbalance settlement.
Gateway management for commercial metering operators
Built MakoFlow on DLMS/COSEM: a multi-tenant platform running about 500,000 smart meters for 6–7 commercial metering operators, including a company of Octopus Energy Group and Inexogy, with regulatory certification per operator.
Acquisition by Hausheld, 2025
Mako365 and Mako Software, two sister companies I co-founded, were acquired together by Hausheld AG in November 2025. I ran the technical and operational due diligence.