Desktop and Web Software Development

What we do

We build the software that turns data produced by field devices into something usable: desktop programs that read meters, allocation software that turns readings into shared costs, and web-based panels where the data is monitored remotely.

What sets this service apart is that we also write the device end of the chain. The team that knows which telegram carries the data, why a meter failed to answer and which error counters the line keeps is the same team that designs the interface. A "not read" row on a reading screen is not a guess here; it is what the protocol underneath actually reported.

Desktop software

For reading work done inside or next to the building we develop Windows desktop programs. Two of our own products show the scope of this service:

• M-Bus meter reading program. Reads the meters on a wired M-Bus line through a serial port. The line can be scanned where addresses are unknown, the meter list is imported from and exported to Excel, and each meter's past readings are kept in a local database. The program was built with Python 3 and the Qt interface toolkit.
• Cost allocation and invoicing program. Turns reading results into period consumption and the building's cost distribution, and produces the output as documents. This program was also written with Python 3 and Qt.

On the desktop side the recurring requirements are these: serial port and timeout settings, two-way data exchange with Excel, local history in a database, backup and restore, hardware-bound licensing, updates verified by signature, and a bilingual interface.

Web and panel

Installations that carry data away from the building need a web interface. On our own platform, the management side sees period consumption and the cost distribution, while a resident can follow their own daily consumption and invoices on their own screen. That separation is what we work on most on the web side: showing the same data at different levels of detail to different levels of authority.

The typical scope of a panel project covers receiving and validating data from the devices, the period and building hierarchy, user permissions, export and document generation, and summary screens for the management.

How we work

We discuss the data model first: if the relationship between building, apartment, meter, period and reading is modelled wrongly, every later screen carries that mistake. Once the model holds, the interface is built around the order in which people actually work — a single table for the reading crew, a period summary for the management, their own consumption for the resident.

We supply software and device infrastructure to many meter reading companies in Turkey, and systems built on that infrastructure cover more than five million homes. That scale taught us one thing: the hard part of this software is not reading, it is working with missing and faulty data.

Scope and limits

• Whether a meter brand can be read depends on its protocol and its documentation; the brands that can be read are listed before installation.
• In calculations governed by regulation, the method is configured according to the customer's management plan and the rules in force; we do not set the calculation rule.
• Cloud hosting, backup arrangements and data retention periods are defined separately in the contract.