Custom smart building software development
Appfront builds custom software that makes the data from your building usable: HVAC systems, energy meters, occupancy sensors, access control and lighting come together in a single view per building, floor and zone. Not a dashboard for the sake of a dashboard, but a system that flags deviations, passes faults on to maintenance and turns consumption into something you can actually steer. Get in touch if you would like to talk through your situation.
What is smart building software?
Smart building software is the layer on top of your building systems. A building usually already has a building management system for climate, a separate access control installation, energy meters from the grid operator and perhaps occupancy sensors from a pilot. Each system has its own screen and its own supplier. The software we build pulls in those sources, maps them to a single data model and turns them into one view.
The difference from an IoT platform lies in the scope. An IoT platform is generic: register devices, receive data, run rules, regardless of where those devices are. Smart building software is explicitly built around the building as a unit — floors, zones, rooms, installations and the people who work in them. That structure is part of the model, not a generic tag structure you have to invent yourself.
Appfront builds this as custom software, with open protocols towards your installations and API integrations with your maintenance and property systems. That way you remain the owner of your building data instead of it being locked into a single installer's portal.
One model for the whole building
Floors, zones, rooms and installations in a single structure, so every measurement has a place and you can compare across zones, buildings and years.
Deviations instead of meters
Not yet another screen full of numbers, but alerting: this zone is consuming outside office hours, this air handling unit is working against itself, it has been too warm here for three days.
Passing it on to maintenance
A signal is only useful if someone acts on it. Alerts are automatically sent as work orders to your maintenance contractor or property management system.
Smart building or IoT platform? Drawing the line
In practice the two often overlap, and Appfront has a page on each. The distinction is not technical but organisational: it depends on where your challenge lies.
The building as the starting point
You manage one or more properties and want to be able to control comfort, energy consumption, occupancy and faults at building level. The data model follows the layout of the building, and the users are facility managers, property managers and maintenance contractors.
Devices as the starting point
You have a fleet of devices or machines, wherever they are, and want to read and control them. In that case, see building an IoT platform or, for the industrial side, AI & IoT solutions.
Our development process for your building software
A building can't be opened up all at once. We start with the sources that already exist and build on from there.
We map out which installations, meters and sensors there are, which protocols they use, who owns which system and what data can actually be extracted. That last point often turns out to be harder than expected, and we would rather know up front.
We design the building model, the alerting rules and the screens for managers and users, and determine which integrations are needed with maintenance, property and reporting systems.
We build in short iterations with automated tests, structured logging and monitoring. You see working versions along the way and steer based on what your team actually needs in practice, rather than on a specification written months ago.
A controlled go-live with validation and a safety net, followed by ongoing management, monitoring and further development as your building portfolio or installation base changes.
What custom smart building software delivers in practice
What makes sense differs per portfolio. These are the components we build most often.
Integration with building installations
Reading out climate, lighting and access installations via the protocols your installer supports, or via the API of the existing building management system. An integration with an IWMS such as Spacewell is part of this too.
Energy and consumption insight
Consumption per building, floor and zone, set against opening hours, outdoor temperature and occupancy. This shows which part of the consumption is truly necessary and which part simply keeps running.
Occupancy and space utilisation
Insight into which rooms are actually used, as a basis for reorganising, giving up square metres or adjusting cleaning and climate regimes.
Fault alerting
Rules that recognise abnormal behaviour — an installation that keeps running, a zone that is structurally out of range — and automatically turn it into an alert with context.
User reports
A simple entry point for employees to report a fault or a comfort complaint, linked to the zone they are in, so that a report immediately belongs to the right installation.
Reporting and accountability
Reports on consumption, comfort complaints and fault resolution, useful for internal management and for energy-registration and sustainability obligations.
Typical use cases in practice
Smart building software pays off most where multiple properties, multiple systems and multiple stakeholders come together.
Office portfolios
Organisations with multiple office locations that want to compare comfort and consumption across buildings and find out which square metres are actually being used.
Property managers
Managers who operate properties on behalf of multiple owners and need to be able to account, per property, for how installations perform and how quickly faults are resolved.
Healthcare and education
Institutions with many rooms, fluctuating occupancy and strict comfort requirements, where climate complaints have a direct impact on the primary process.
Industry and logistics
Buildings where climate, cooling and energy consumption are tied to the production process, and where a fault costs more than just comfort.
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 we use
Smart building software lives or dies by its ability to pull in data from systems that were never designed for it. The exact choice depends on your processes, the systems to be integrated and your hosting preferences. We deliberately choose a stack that your own team can manage and develop further, without dependence on per-user licences.
Why Appfront for your building software?
Appfront builds custom software for a wide range of organisations in the Netherlands. With building software, the work does not start with the dashboard but with the question of what can actually be extracted from your installations. We do that assessment first, because that is where most projects fall apart.
We deliberately build on open protocols and with your data in your own environment. A building lasts for decades and installers change; your building data should not move away with the supplier who happened to unlock it first.
On every project we write clear documentation and make sure your own team, or a future supplier, can understand and manage the system. No black box, but transparent code and clear agreements on monitoring, alerting and maintenance. You own the solution and pay no per-user licence.
Also take a look at our broader services around custom software, an IoT platform and property management software. Unsure about the approach? Get in touch.
Security and privacy in your building software
Building systems are an attractive target because they often run for years without updates and are sometimes connected directly to the internet. Appfront builds according to the OWASP ASVS and keeps the integration with installations strictly separate from the user layer, with least-privilege access and network segmentation as a starting point.
Occupancy and access data can constitute personal data as soon as they can be traced to an employee. We design so that traceability exists only where it is functionally necessary, document the data flows for your processing register and take into account the GDPR and the consent rights of the works council.
More about our approach to security: information security policy and CVD policy.
- Encryption in transit (TLS 1.2+) and at rest
- Role-based access following least privilege
- Audit trail of views and changes
- Secrets in a secure vault, not in code
- Documented data flows for your processing register
- Separate network path to building installations
Frequently asked questions about building smart building software
Answers to the questions we get asked most often.
Software that brings together the data from your building installations, meters and sensors into a single model per building, floor and zone, and turns it into usable signals: abnormal consumption, comfort outside the acceptable range, installations not doing what they should. It is the layer above the installations, not the control system itself — that stays with your building management system.
No, and that is usually not advisable either. A building management system controls the installations and is certified for that. We build the layer above it: retrieving data, combining it with other sources, flagging issues and passing them on. Control is possible in consultation with your installer, but we start with reading data — that delivers value fastest and does not affect the safety of the installation.
Often, yes, but it is the first question we investigate. Some installations speak an open protocol, some have an API and some reveal nothing without the installer's involvement. In that last case there are usually alternatives, such as separate meters or sensors. We map this out before anything is built, so you don't pay for an integration that turns out to be impossible.
That differs per building and we don't make promises about it. What we see in practice is that the first insight almost always uncovers something nobody knew: systems that run through the night, a zone that has been heating and cooling against itself for months, rooms that are structurally empty. What that is worth depends on what you do with it.
Occupancy sensors that only count whether a room is occupied do not process personal data. As soon as workstations can be traced back to individuals, through login, badge or camera, they do, and GDPR rules apply, including the duty to inform and sometimes the consent of the works council. We prefer to design so that traceability is not needed.
That is often the most appreciated feature. A simple way to report that it is too cold or that the lighting is not working, linked to the zone where someone is sitting, produces better reports than an email to the facilities mailbox, and it shows whether complaints coincide with what the sensors measure.
Yes, and that is usually the whole point. The model is built at portfolio level, so you can compare buildings with each other on consumption, comfort complaints and fault handling. You add new buildings without any development work.
There are good platforms, and if your installations are modern and uniform, you can get a long way with them. Custom software pays off when your portfolio is mixed, when you want to integrate with systems such a platform doesn't know, or when you don't want to depend on a single supplier for access to your own building data. If an off-the-shelf package suits you better, we'll say so.
Ready to build your smart building software?
Tell us which buildings are involved, which installations they have and what you can't see right now. We're happy to think along on scope, integrations and the first version. A no-obligation first conversation gives you a clear picture of the possibilities and whether custom software pays off in your situation.