We treat meter operations as an operations problem, not a software problem.
Sayaç Yönetim Platformu is built by an engineering team that designs, manufactures and operates smart gas meters. The software is worked out end to end by the same people — from the firmware inside the meter to the field crew of the distribution company.
Six principles; every decision in the product rests on one of them.
We draw the boundary
Subscribers and billing stay in your system; meters and field work live in the platform. The shared key is the usage point number. Neither system knows the other's internal identifiers, which is why the integration stays light.
We put security in the architecture
The meter channel and the human channel run on separate servers, every packet from a meter is signed, critical commands need a second approval, and every action is recorded. Security is not a feature added afterwards.
We mirror the operating model
Four units, three grades, five depots: the platform reflects how a distribution company is actually organised. Nobody learns a new vocabulary — they see their own work under its own name.
We speak in standards
DLMS/COSEM, IEC 61968-9 integration messages, MID metrology records. Where a standard exists, we do not invent an alternative.
We grow with scale
It starts on a single server and continues, at a hundred thousand meters, with core nodes and a partitioned data layer. A meter is given its address once and never has to change it.
We design it to be handed over
Branding, legal texts and sender addresses come from configuration; installation is repeatable from a runbook. If the platform ever passes to another operator, the code does not change.
What we cover, and what we do not.
| In the platform | In your system |
|---|---|
| Meter communication (REST, DLMS), commands, firmware, key management | Subscriber contracts and identity verification |
| Readings, events, alarms, read quality, period index | Tariffs, invoices, collection, debt |
| Work orders, field crews, depots and calibration, inspection calendar | Call centre and subscriber app (they use the platform API) |
| Authorisation, audit log, usage ledger | Corporate identity system (optional SSO) |
What works today, what is next, and what comes after.
Four unit consoles, single sign-on with two-step verification, the five-depot model, the team grades, the usage ledger, and a separate meter core.
The Customer Data API and the master-data contract, webhooks, a developer portal and a sandbox.
The DLMS server side, the field mobile app (with Face ID / fingerprint), corporate SSO, multi-region core nodes.
For references, pilot details and commercial terms, get in touch.