Custom app development for plant room installation inspections
A building automation system has to notify the facility manager when losses occur. That makes the alert only the start: someone has to go to the plant room, see what is going on and record what they did. That part is usually handled by phone and from memory today, and it is exactly the part you need to be able to demonstrate later.
Where the alert gets stuck
The system raises the alert. Someone drives to the building, walks down to the basement and finds a valve stuck. They free it, report it to the manager by phone and drive on to the next building. What was done is recorded nowhere. The next time an alert comes in for the same installation, the investigation starts again from zero.
Then there is the technical space itself. A boiler room is in the basement, an air handling unit is on the roof behind a steel door, and neither has any signal. An app that only works with a connection won't be used in exactly those places. So it goes back to a note on a phone, which is the last place anyone will look for it.
The third issue is the readings that don't come from the installation. Not everything is connected: an older gas meter, a water meter in a separate room, a sub-meter that was never linked up. Those readings are currently jotted on a piece of paper and retyped later, with the errors that brings. For analysing consumption, though, these are the figures that complete the picture.
If an inspector visits, they have their own survey and their own deadline for registering it. See the app for on-site EPBD inspections.
How we build this
The app follows an engineer's route through the building. Anything that holds them up along the way costs usage, and therefore records.
A code on the boiler, the cabinet or the meter opens the right record straight away. Searching a list of fifty installations in a dark basement is something you only do once.
A checklist that doesn't match the installation gets ticked off without looking. We walk the round ourselves before we put it on a screen.
Basements and rooftop plant rooms have no coverage. The app keeps working locally and syncs later, preserving the original timestamp.
What the engineer finds and fixes goes back to the alert it came from. Without that loop, the system keeps repeating alerts that have already been resolved.
What the app actually does
The round with its recording carries the whole thing. What you add on top depends on how many buildings you manage and who does the work.
Open an installation by scanning
A code on the boiler or the air handling unit opens the right record with that unit's history. No searching through a list in poor light.
Alerts with a resolution
The alert from the system arrives as a job and is closed with a note of what was done. An alert without a resolution doesn't count as resolved.
Meter readings without retyping
Readings that aren't connected are recorded on site with a timestamp and the meter. They go to the consumption overview via an integration. A piece of paper that gets retyped later costs errors and usually a day's delay.
Works in the basement
Everything is recorded locally and synced as soon as there is signal again. The original timestamp is preserved, which matters for the consumption overview.
A picture with the finding
A leak, a taped-over grille or a valve that is stuck: you record it where you see it. That saves a second visit to work out what exactly was meant.
Rounds across multiple buildings
Anyone visiting four buildings in a day wants to know what is outstanding at each one before they arrive. See also the work order app.
Who we build for
Who walks the round varies widely, and that shapes the design. Four situations.
Owners with multiple properties
The gain lies in comparing what happens at each building. An installation that raises the same alert every month is an investment question, not a maintenance question.
Healthcare and education
An in-house technical team with fixed rounds. Here it is less about reporting and more about demonstrating that the round was carried out as intended.
Maintenance providers with contracts
You work for several clients and must be able to show each one what was done. That is also the basis for the traceability your client needs themselves.
Managers of mixed property portfolios
Complexes with both residential and office or commercial space. The installations overlap while the obligations differ, and you want to be able to separate them per part.
Test your idea first: a working prototype in 1 day
With OneDayBuild, we make your idea tangible in a single day for €1,150, so you know whether further development is worth the investment. Decide to go ahead with the full build? Then we deduct the cost in full.
View OneDayBuild →Technology and integrations
Rounds and installations change more often than software does. Everything to do with checklists, installation types and reporting rules should be configurable.
Why Appfront
There is no signal in the plant room
We build offline-first. An app that only works upstairs won't get used in the basement, and that's where the work happens.
A report needs to be closed
We build the loop back to the source. Without that loop, the system repeats reports that have already been resolved, and people stop looking.
Walk the round first
A checklist that doesn't match the installation gets ticked off without looking. That's worse than having no list.
What has been done belongs with the installation
We attach the history to the unit rather than to the report. At the next fault, that's the first thing anyone wants to see.
Security and privacy
An app that shows, per building, which installations are there and when nobody is present holds more sensitive information than it seems. We set access per building and per period, give an external maintenance party only its own assets, and let that access expire automatically.
For the record, the timestamp is the evidence. A round that can be entered on a different day after the fact says nothing about whether it was actually walked, and that is exactly the question in a contract dispute or a damage claim. We record entries immutably with their original timestamp, even when synchronisation happens later, and show a correction alongside the old value. How we handle security ourselves is set out in our information security policy; reports from outside go through our CVD policy.
Frequently asked questions about the building management app
No. The control system keeps doing what it does: controlling and signalling. This app is about the person who responds to the alert and about recording what happened on site. We link the two, so that a report is closed with a reason rather than with silence.
The obligation concerns the system that tracks consumption, analyses it and informs the building manager; that is covered on the page about the building automation obligation. This app is the side that follows from it. For demonstrability, what matters most is that something was done with an alert.
Yes, and that is deliberately the starting point. Boiler rooms are in basements and air handling units on roofs behind steel doors. Everything is recorded locally and synchronised later, keeping the original timestamp.
Yes, and that is often the quickest win. Not every meter is connected, and the readings that are currently on a slip of paper are exactly the figures that complete the consumption picture. Recording at the meter saves retyping and the errors that come with it.
Yes. We give an external party access to its own assets and period, so it records its work in the same environment. That is usually what your contract requires too, because otherwise you have to request the evidence from them.
Usually, yes. If your installation records are in a maintenance system, we pull that data in rather than creating a second list. Two registers of the same installations always drift apart.
Yes, and you need to. Installations differ from building to building, and a checklist that doesn't fit gets ticked off without anyone looking. That's why we treat checklists as a setting per installation type, so changing one doesn't require any development work.
That depends on the number of buildings, whether your installations are already coded, and whether external parties are involved. The round with logging and meter readings is usually quick to get working; the integration with the analytics system takes more effort. We give a well-founded estimate after the discovery phase.
Want to know what happens to a report?
Take a fault from last month and try to find out who went out to it and what they did. If that takes more than a few minutes, that's where the gap is. We build this as a standalone app and as part of a broader app development project.