Platform for tracking the technical systems in a building from design to maintenance
Every technical system in a building — ventilation, heating, electrics, fire detection, access control — in one place: the conditions each one has to meet, its tests, its progress, and the documentation it is handed over with. It does not slow down on projects that run to thousands of systems.
The challenge
In a building the technical systems do not work in isolation: ventilation, heating, electrical, lighting, fire detection, access control and automation all have to work together. Someone has to know, at any moment, which system is finished, which is tested, and which can be handed over. On a large project that is over a thousand systems across every discipline, with specialists working on them at once — and tools for this usually slow to a crawl as the project grows.
Our approach
Most of the work went into understanding the domain — what a system is, what has to be true before it can be signed off, what the handover has to contain. That understanding shaped the data model, and the build followed on both sides of it. On the back end we redesigned the core services and moved the codebase to static types. On the front end, grids tracking a thousand-plus systems stay responsive through server-side rendering, optimized state management and data loading, and infinite scroll. We also built the real-time chat infrastructure, tied to the context of the work, and large reports generate in a stream, so project size no longer breaks anything.
The results
The client got a tool that holds a whole project in one place: every system, the conditions it has to meet, its tests, its progress, and the documentation that goes with it at handover and stays useful in maintenance. The interface still answers in under 100ms on grids of a thousand systems, big reports always arrive, — a foundation the team can keep building on without us.
What we did
- Delivered features continuously across the whole product: system tracking, checklists, reports and chat
- Redesigned the backend core services
- Modelled the data so every system carries the classification the trades already use, with its own acceptance criteria and tests
- Built fast, data-heavy interfaces: server-side rendering, optimized state management and data loading, infinite scroll
- Took part in moving the whole codebase to a statically typed language
- Built the real-time chat infrastructure, tied to the context of the project
- Built a PDF service that streams large reports instead of holding them in memory