Case study · Manufacturing & Industrial IoT

From 52 tank displays to one screen, for naval vessels

A naval instrumentation supplier’s gauges showed each tank’s level on its own small display. We built the software that puts all 52 on one screen, and made sure it can only listen.

  • ClientAn Indian naval instrumentation supplier
  • SystemTank-level display
  • Delivered2017 to 2018, live on a ship
  • StackUWP · SQLite
The outcome

52 small displays became one screen

Every tank’s level, quantity and alarm state at a glance, with the detail a touch away.

  • 52 → 1

    Tank displays to one screen
  • 4

    Alarm thresholds
  • 0

    Commands sent to a gauge
  • 5

    User roles
At a glance

Project snapshot

Client
An Indian naval instrumentation supplier
Domain
Manufacturing & Industrial IoT
Engagement
New build
Platform
Industrial panel PC, Windows 10 IoT Enterprise
Bus
RS485, listen only
Storage
SQLite on the panel PC
The story

What we built, and why it only listens

Context

Aditi IT Software Solutions built the tank-level display software for an Indian naval instrumentation supplier, for the tank gauging system of a large naval vessel. The supplier’s gauges measure the level in each of the ship’s tanks. Before this software, the readings appeared on 52 small displays, one per tank, with no single view of the ship’s tanks.

The supplier wanted one screen: every tank’s level, quantity and alarm state at a glance, with the detail of any single tank or group a touch away.

Constraint

The hardware and the protocol were fixed. The gauges talk on an RS485 bus in the supplier’s own protocol, with a central display unit as the bus master. The software had to run on an industrial panel PC under Windows 10 IoT Enterprise, reach the bus through the PC’s RS232 port, with a USB port configured as RS232 as the fallback, and work with no network at all. On a warship, a display that depends on anything outside the ship is not a display.

Decision

The software only listens. It reads the bus, shows the readings and raises alarms; it never sends a command to a gauge and never controls a tank. Control stays with the supplier’s own equipment, and a fault in the display cannot become a fault in the tanks, the same reason we built a separate system instead of sharing a server elsewhere. Programming the gauges stays in the supplier’s own application.

Readings and alarms are logged on the panel PC itself, in a local SQLite database, so history survives without a server.

Build

One screen for 52 tanks, plus single-tank views and groups the user defines; level and quantity per tank.

Alarms at four thresholds (high-high, set-high, set-low, low-low), shown on every page, with acknowledgement.

Five roles (operator, supervisor, service, master, factory), reports and printing, and a license generator.

Touch-first screens with an on-screen keyboard for data entry.

Stack: a Universal Windows Platform application, Entity Framework Core over SQLite, a .NET Framework 4.5.2 data layer; an earlier WPF and Prism version was replaced by the UWP one.

Documentation delivered: user manuals 1.0 and 1.1, code manuals 1.0 to 3.0, a software test report (05-Sep-2017), issue status reports.

An alarm is never hidden behind navigation: when a tank crosses one of its four thresholds, the indication shows on every page of the application until a user acknowledges it. Access is split across five roles, from the operator who watches the screen, through the supervisor and the service engineer (who also gets the logging reports) and a master role that can only disable service users, to the factory role, which configures the installation and activates it with a license issued by a separate generator from the panel’s device identifier.

The first version was built on WPF and Prism for .NET Framework 4.7; the delivered application replaced it with UWP, kept the data layer on .NET Framework 4.5.2 and stored everything in SQLite through Entity Framework Core. The project’s record holds 317 version-history entries and 131 work items from 2017 to 2019.

On the same panel PC today, Aditi would build it as a desktop application on current .NET, because Microsoft has since stopped adding features to UWP; the listen-only design, the serial connection and the local database would stay as they are.

Stack

What it is built on

  • Universal Windows Platform
  • Entity Framework Core
  • SQLite
  • .NET Framework 4.5.2
  • RS485
  • Windows 10 IoT Enterprise
The result

What changed

Releases ran from 2017 to 2018, and a Phase 2 specification upgrade followed on 27-Mar-2019. The software was delivered to the supplier, which fitted it to the system it supplies; 52 separate tank displays became one screen with several views. The system is live on one of the ships.

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