Short answers, with links to the pages that go deeper.

It reads smart gas meters, watches their alarms, sends commands and firmware; it runs the work of the distribution company's field, depot and technical units through work orders; and it hands validated index values to your billing system. It does not issue invoices and does not collect payment.

HES (head-end system) is the layer that talks to the meter: protocol, commands, keys. MDM (meter data management) brings the collected data up to operational quality: binding it to the usage point, validation, estimation, period index. The platform provides both together.

No. The platform replaces the reading-file and disconnection-list interfaces you use today. A company that wants more can also use the REST API and webhooks.

No — the subscriber app is your system, under your brand. The platform provides an API that returns meter status, consumption and events by subscriber or usage point number, and your app uses it.

REST-based meters and meters that speak DLMS/COSEM (IEC 62056). It runs over NB-IoT, with an adapter layer for different manufacturers.

Only the meter core; the address is given to your company during commissioning. The human consoles sit on a separate server, so congestion or an attack on the meter channel does not reach them.

Yes. The core also opens an unencrypted REST door; packet integrity and identity are carried by the signature and HMAC produced in the meter. Newer models connect over TLS.

A specialist prepares the command and a unit manager approves it; the server signs the command and the meter verifies the signature. Every command sits in the audit log with who, when and why.

Meter alarms, field findings, subscriber requests and company lists all land in one pool: General Operations. From there they are routed to a unit; the unit manager assigns to a team and the team chief to a person.

Five: Intake, Inspection, Calibration, Supplier Return and Scrap. Every meter removed from the field passes through Inspection; it cannot go to the manufacturer or to scrap unexamined, and a meter needed as evidence is locked.

Each meter has its validity date on record; expired and approaching meters are listed, a bulk removal work order is opened, the laboratory result is entered, and a meter that passes returns to stock.

The minimum: usage point, subscriber number, address; contact details only if you provide them. No national identity numbers, invoices or debt. Your company is the data controller and the platform operator is the processor.

Accounts opened by invitation, passwords of 12+ characters checked against known breaches, two-step verification with an authenticator app, brute-force lockout, single sign-on, an idle timeout, and a full audit log.

On the roadmap: per-company SSO over OIDC/SAML with optional SCIM sync. Today there are local accounts with two-step verification.

The distribution company’s. Gas meters carry a verification cycle set by national metrology rules — ten years in Türkiye — and a meter whose period has expired must be removed and replaced with one holding a valid verification. The subscriber has no duty to notify or to pay. The platform does not take the obligation on; it lists the meters coming due, opens the removal work order, records the laboratory result and keeps the chain ready for audit.

For Türkiye, two texts: the Ministry of Industry and Technology regulation on the verification of electricity, water and gas meters, and the EPDK Natural Gas Market Distribution and Customer Services Regulation. On the meter side the frame is MID MI-002, OIML R137 and EN 14236.

No. OSOS is a definition in EPDK’s electricity market legislation; gas distribution has no such system definition. The platform is designed for gas distribution companies and works to gas regulation.

The audit log and the API usage ledger are exportable; per meter, the verification history, the removal reason, the laboratory result and the seal record sit in the same chain. That is the traceability tenders and certification audits ask for.

HES (head-end system) is the layer that talks to the meter: protocol, commands, keys. MDM (meter data management) brings the collected data up to operational quality: binding to the usage point, validation, estimation, period index.

Vm is the volume the meter measures; Vb is that volume converted for temperature and pressure. Which one a company bills on is its own setting, and changing it requires an e-mailed confirmation.

The single shared key between the platform and your system. Neither side knows the other’s internal identifiers, which is why the integration stays light.

The meter’s cumulative volume reading. The legal forward index is monotonic: under no condition does it go backwards.

Confirmation by an authorised laboratory that the meter measures correctly. For gas meters the cycle is ten years in Türkiye, and following it belongs to the distribution company.

The international standard for meter communication (IEC 62056). The platform supports it alongside signed REST.

Low-power, wide-area cellular communication. The path by which meters reach the core server.

The consumption series a meter records at fixed intervals. Loss investigation and consumption analysis run on it.

An annual platform licence based on the number of meters; API usage is measured in the usage ledger and can be priced as a package or per call. Pilots have their own terms.

If the master data file is ready, the company definition and first load happen the same day; the first period close with a pilot meter group within a month.

The platform is offered as a cloud service. For large-scale projects a dedicated installation is considered separately.