CLIENT DELIVERY · LEGACY TAKEOVER

Residential BMS Portal

Extending an existing ASP.NET Framework portal used to manage and analyze a large residential common-area building-management system.

Role: Inherited application owner
Status: In use
Data: Hourly aggregated BMS values
Stack: ASP.NET Framework · SQL

Context

The BMS vendor already collects field data over Modbus TCP and writes aggregated values into a database. The original application developer was no longer available, so I took over the existing portal codebase rather than replacing the system.

Application Work

I build on top of the vendor-collected database data to add electricity-cost estimation and selected equipment-point trend analysis in chart and table form.

Historical Data

The application currently works mainly with hourly aggregated values rather than claiming ownership of raw telemetry ingestion. Supporting data-cleaning and aggregation work handles the historical-data lifecycle needed by reporting.

Boundary

Field acquisition remains the BMS vendor's responsibility. My responsibility begins at the persisted data and existing ASP.NET application layer: calculations, reporting, presentation, and maintaining the inherited codebase.

What this demonstrates

Legacy application takeover, working inside a vendor ecosystem without rewriting it, SQL-backed reporting, domain calculations, and clear ownership boundaries.