What exactly is an FMIS, and how does it differ from a CMMS?
An FMIS (Facility Management Information System, also known as facilities software or building management software) supports the full range of facilities work: bookings, reports, contracts, cleaning, energy and tenant communication. A CMMS is narrower and focuses on the technical maintenance of installations and assets. In practice the two overlap: our clients often choose an FMIS core with a strong maintenance component. See also our page on a
CMMS maintenance management system if maintenance alone is your scope.
Do you replace Planon, Axxerion or another package?
Usually not. For mid-sized facility work, Planon, Axxerion, Vastware, MCS and ProsperaCity are simply good packages, and we often recommend them. We come into the picture when those packages no longer fit: sector-specific flows, deep integrations, multi-tenant experience or a custom tenant portal that goes beyond the standard model. We also often work alongside an existing package as a complement rather than replacing it.
Can you integrate with our Building Management System and access control?
Yes. For BMS integrations we work with BACnet, Modbus or your supplier's cloud API (Priva, Honeywell, Siemens Desigo, Schneider EcoStruxure). For access control we have experience with Salto, Nedap and Paxton. We bring events from the BMS and access control together with your FMIS data, so a fault or occupancy event immediately triggers the right follow-up: a work order, a cleaning round, or an alert to security.
Do you also work with IoT sensors?
Yes. We connect sensors for temperature, CO2, humidity, occupancy, noise level or waste fill level, via LoRaWAN, Zigbee, Modbus or the supplier's cloud API. Sensor data is visualised in dashboards, can trigger threshold-based actions (scheduling a round, sending a notification to a tenant), and is useful for predictive maintenance and energy optimisation. We also advise on which sensors make sense where, as a sensor installation without a clear purpose often generates a lot of data and little control.
Does the FMIS work across multiple sites and tenants?
The FMIS is multi-site from the start and can also run multi-tenant. Each building or tenant has its own roles, branding and flows, with central reporting and analytics for the portfolio as a whole. For facility management companies serving several clients, this is one of the reasons to choose custom development: standard packages quickly become expensive per user and are rarely multi-tenant in the sense you need.
Can we get energy and CSRD reports out of it?
We build energy dashboards based on your BMS data and smart meters, with comparisons between properties, anomaly detection and exports you can use for CSRD and EED reporting. Which metrics you can see depends on what you measure. During discovery we map which data points are available and which you may still need to unlock with sub-meters or additional sensors.
What determines the cost of an FMIS project?
Mainly the number of modules, the depth of the integrations (BMS, access control, ERP, IoT) and the extent to which you want to serve multiple tenants or locations. An add-on module for an existing package is a much smaller project than a custom FMIS core or a multi-tenant platform. During discovery we outline a scope and timeline you can steer by — if necessary with several variants, so you can choose what to do first and what comes later.
How does the implementation of an FMIS run in-house?
We always work in sprints and start small. The first sprint is deliberately limited, often one module, one building and a small group of users, so we can learn early what works in your context and what doesn't. After that we expand modularly. For the rollout per site or tenant, we draw up a runbook with you, including data migration, training and a transition period during which the old and new systems run side by side.
What about security and user management?
SSO via your existing IdP (Azure AD, Google Workspace, Okta), role-based access, audit logging as standard, and encryption in transit and at rest. For tenants or external suppliers we arrange federated login or magic links. On larger projects we carry out a DPIA and schedule a penetration test in the final sprint. For multi-tenant setups we ensure tenant data remains strictly separated, so there is no risk of information leaking between tenants through a misconfigured query.