Legacy Meter Recognition & Smart Retrofit Recommendation
An application that identifies traditional meters from images and, based on the meter and display type, suggests suitable retrofit approaches for smart metering.
Project status: In development
A smart city is not created by buying a few sensors. Many municipal projects start with one attractive use case, such as smart parking, and later discover that every new application comes with its own network, its own software and its own vendor contract. The result is a patchwork that is expensive to run and hard to extend.
My approach is to design shared infrastructure first: connectivity, a data platform and clear rules for security and privacy, so that applications from street lighting to water metering can be added over time. I work as a technical consultant for municipalities, utilities and contractors, from architecture design to pilot support.
Industry challenges
Siloed departmental systems
Lighting, water and traffic departments each run their own systems, so their data never meets.
Scale and field maintenance
Thousands of measuring points across the city must run for years with as few site visits as possible.
Legacy assets
Existing meters, pumps and lighting cabinets usually have no communication interface and cannot all be replaced at once.
Privacy and public trust
Parking occupancy or household consumption data can reveal personal behavior and must be handled with care.
Vendor lock-in
Closed contracts and proprietary protocols make future expansion or a change of supplier difficult.
Technical solutions
Smart street lighting
Remote switching, scheduling and dimming of luminaires, with automatic fault reporting for lamps and cabinets.
Parking and mobility
Occupancy sensors or entry/exit counting to show free capacity and analyze usage patterns.
Air quality and environment
A dense network of low-cost stations for particulates, gases, temperature and noise, complementing official reference stations.
Water networks and leak detection
Pressure and flow monitoring in district metered areas to detect anomalies and support leak-detection campaigns.
Waste and utility metering
Fill-level sensors for route planning and automated reading of water, electricity and gas meters, including older ones.
Urban data platform
One platform with GIS maps, dashboards per department and APIs for controlled data sharing.
How I approach a smart city project
Urban projects involve many stakeholders and long lifetimes. Rather than starting from technology, I start from problems and ownership:
- Needs and stakeholders: which department owns the problem, what data exists today and who will act on new information.
- Prioritize use cases: choose applications that deliver visible value and at the same time test the shared infrastructure.
- Design shared infrastructure: operator-neutral connectivity, a data platform, a common data model and access rules.
- Limited pilot: deploy in one neighborhood or network zone, then evaluate coverage, battery life and usability for municipal staff.
- Incremental expansion: add applications and districts on the same foundation, with documentation that supports future tenders.
Why a shared data platform matters
The real value of a smart city appears when data sets meet, for example when water pressure data is compared with excavation permits, or lighting faults with public safety reports. An open platform such as ThingsBoard, combined with a map layer, can:
- store data from devices of different manufacturers in one consistent model,
- give each department its own dashboards and permission level,
- expose aggregated data to other systems through documented APIs.
A shared platform also changes procurement. Instead of buying complete vertical solutions, a city can specify open interfaces and data formats, then source sensors and applications from different suppliers over time. This keeps competition alive and protects earlier investments when technology moves on.
I discuss this in more detail in Smart city infrastructure.
Privacy and security by design
In public projects, citizen trust is the most valuable asset. Data minimization, encryption in transit, a process for device firmware updates and transparency about what is collected and why belong in the design, not in a retrofit after launch. Where metering is involved, Smart metering with legacy meters covers the practical options.
Frequently asked questions
Which network technology is best for a smart city?
There is no single answer. LoRaWAN, NB-IoT and wired networks each suit different applications. The choice depends on existing coverage, sensor power budgets, data volume and whether the city wants to operate its own network or use a provider.
Do old utility meters need to be replaced?
Not necessarily. Pulse modules or optical reading of the meter register can often digitize existing meters, leaving replacement until the end of their service life.
How is citizen privacy protected?
By collecting only what is needed, aggregating and anonymizing before display, defining strict access rights, and avoiding images or personal identifiers unless there is a clear necessity.
Where should a city begin?
With a small area and one or two use cases that have a clear owner, such as lighting on one boulevard or pressure monitoring in one water zone. The pilot also tests the shared network and platform for later applications.
