Case study
Equipment health monitoring platform
A production-shaped monitoring app for simulated asset telemetry, live alerts, incident history, and asset-level investigation.
What I am building
This is a full-stack monitoring application for simulated equipment telemetry. It brings live alerts, incident history, and asset-level drill-down views into one operational flow.
The aim is not another polished dashboard with no system behind it. I am structuring the project around API-backed services, containerised local development, and data that behaves more like an operational product than a static demo.
Interface direction
The main views focus on status trends, fault events, and threshold breaches. A user should be able to move from fleet-level health to the history of one asset without losing the context that brought them there.
That means treating empty, delayed, and abnormal states as primary interface work rather than leaving them for the end.
Technical shape
The application uses Next.js and TypeScript on the frontend, with Node.js and Express services backed by PostgreSQL. Docker keeps local development repeatable, while the deployment structure is being designed with AWS in mind.
Current work
The project is in progress. The next useful proof points are a complete alert-to-incident workflow, documented API contracts, and measured behaviour with a larger telemetry set.