Skip to content

Energy companies and distribution companies

Make meter data readable for commercial consumers

Energy supply and distribution companies work with large volumes of meter data. GenieBlocks turns data from OSOS, Turkey’s automated meter reading system, and from field metering into consumption, reactive power and capacity views a commercial consumer can understand, and the platform can connect to the company’s own systems through a REST API and MCP.

How the platform addresses them

The modules that map to these problems. All modules run on one data backbone, in the same interface.

  • Data Quality

    Tracking of missing data and offline meters.

  • Metering Points

    Catalogue of meters and metering points.

  • Meter Replacement Log

    Serial number and reason for each replaced meter.

  • Device Mapping

    Mapping a field device to a metering point.

  • Reactive Power & Penalty Risk

    Power factor, compensation threshold and likely penalty.

  • Installed Power & Capacity

    Allocated power, peak demand and night-time base load.

  • Energy Baseline

    Deviation of consumption from the baseline period.

  • Deep Analytics

    Analysis of 15-minute power, temperature and occupancy.

  • Reports

    Ready-made energy reports.

  • Carbon & Sustainability

    Scope 2 location-based and market-based emissions.

  • Users & Roles

    Role-based access; a tenant sees only their own data.

  • MCP Integration

    The platform opens up to external AI tools such as Claude through MCP.

Related capabilities

  • Multi-source data integration

  • AMR/OSOS (automatic meter reading)

See all modules

Where the data comes from

You start without replacing your existing systems. Today the platform takes data from:

  • OSOS
  • REST API
  • MCP
  • Modbus (RTU / TCP)

Connected in the setup project: M-Bus · IEC 62056-21 · RS-485 · Pulse output · Analogue (4-20 mA, 0-10 V) · MQTT · Databases on your own servers

Explore integrations

If your device isn't listed, we add it together.

Example use case

How it works: Tracking quality in meter data

  1. The platform lists gaps in OSOS readings and offline meters in the Data Quality module.

  2. A replaced meter’s serial number and reason are recorded in the Meter Replacement Log, and the new meter is linked to its metering point with Device Mapping.

  3. If the data isn’t reliable, automatic actions stop, and the missing periods show up on the Data Quality screen.

  4. The company’s own systems access the same data through the REST API or MCP.

This is an example use case; it does not describe a specific organisation or result.

Let’s talk about your facility

Join the early access list; in the demo we show the platform and work out together how to start with the meters and systems you already have.