Case study · Manufacturing & Industrial IoT

New devices on a live IoT platform, without breaking it

An Irish sensor maker’s tank-monitoring platform has run since 2015. Since 2022 we have added new cellular tank loggers, pressure sensors, GPS and command queuing to it, every change merged into the customer’s own releases.

  • ClientAn Irish sensor maker, through a software partner
  • SystemRemote tank monitoring
  • Delivered2022 to 2026, in production
  • StackASP.NET MVC · Azure Functions
The outcome

Four years of changes inside a live platform

Every change merged through pull requests into the customer’s own mainline.

  • 184

    Commits by Aditi’s developer
  • ~1,000

    Devices on the platform
  • 9

    Device families with command queuing
  • 2

    New cellular tank loggers
At a glance

Project snapshot

Client
An Irish sensor maker
Through
A software services partner
Domain
Manufacturing & Industrial IoT
Engagement
Extension of a live system
Platform
ASP.NET MVC 5, Azure Functions, TCP ingestion
Since
October 2022
The story

What we added, and how we kept it inside

Context

Aditi IT Software Solutions has extended the remote tank-monitoring platform of an Irish sensor maker since October 2022, working through a software services partner. The platform reads cellular loggers fitted to liquid and gas tanks and turns each reading into what the people who refill tanks need: percent full, the amount to fill, usable liquid, ullage and liquid level, on charts, a map and alerts.

The platform was not new. Its first commit is from 2015, and it already ran a web application, an API and more than fifteen Azure Function apps for reports, archiving, billing and notifications: 63 .NET projects, 74 controllers and 431 views, on .NET Framework versions from 4.0 to 4.8, with Entity Framework 6 and Dapper side by side. Every new device had to fit into all of it. Aditi’s job was to bring new hardware onto it.

Constraint

Three things could not change. The platform was live, with customers reading their tanks every day, so every change had to merge into the customer’s own repository and ship in their release. The loggers’ protocols were the manufacturer’s: the data field of a reading from one of the new loggers changes format with the device’s own settings, so the same bytes mean different things on two devices. And the loggers sleep to save battery, waking on a schedule to report, so the platform cannot reach a device whenever it wants.

Decision

Aditi worked inside the existing architecture rather than beside it. Each new device family was added through the same layers the old ones used, from TCP ingestion and packet decoding through settings, readings, charts, map, search, alerts, the API and the archive service, each change as a pull request into the customer’s master branch. A separate service for the new loggers was never on the table: the platform serves many customers from one application, and the new loggers had to appear in it beside every other device those customers already watched.

For the settings problem, each reading is decoded against the latest settings known for that device, with a defined default when none are known, rather than guessing the format from the bytes.

Build

The first new cellular tank logger (from October 2022): device type, message processing, settings, readings and charts across the platform.

The second new cellular tank logger (from February 2023) and pressure sensors (2023).

GPS packet decoding for the first new logger, with unit tests (2024 and 2025).

Modem transfer between platforms, including Sigfox and Wi-Fi devices (December 2024 to June 2025).

Command queuing (May 2025): an administrator queues a command for a list of serial numbers, each checked against the selected device type; the command waits until each logger next calls in, and uncollected commands can be withdrawn first. Nine device families are covered.

Gas tank support in the reports (2025).

Stack: ASP.NET MVC 5 on .NET Framework, SQL Server with Entity Framework 6 migrations, Azure Functions, TCP ingestion services.

Stack

What it is built on

  • ASP.NET MVC 5
  • .NET Framework
  • SQL Server
  • Entity Framework 6
  • Azure Functions
  • TCP ingestion
The result

What changed

Aditi’s work is in the customer’s mainline: 184 commits by Aditi’s developer between October 2022 and September 2026, merged through pull requests from December 2022, with production deployments recorded through October 2025. The platform serves the manufacturer’s customers today, about 1,000 devices across them.

65+ systems delivered since 2011

Named where the client has given written permission, described by sector where they have not.

See the full delivery record