A CAFM system is the software platform an FM operation runs on: a set of connected modules built around a shared asset register, used by managers through a web application and by technicians on mobile. Viewed as a system, it is a database of buildings and equipment, a workflow engine that turns requests and schedules into jobs, and a reporting layer that shows whether the work met the contract.
The core modules and how they connect
Every module draws on the same location and asset hierarchy: site, building, floor, room, system, asset. That shared structure is what separates a CAFM system from a collection of separate tools, because a job, an inspection and a spare part can all be traced back to the same piece of equipment.
- Asset and location register: the master data everything else refers to
- Helpdesk and work requests: where occupants, tenants and alarms raise issues
- Work order management: triage, assignment, execution and closure of reactive jobs
- Planned preventive maintenance: schedules that generate work automatically against asset types
- Inspections and compliance: statutory and quality checklists captured with evidence
- Contracts, vendors and SLAs: service levels, rate cards and contractor performance
- Inventory and procurement: spares, stock levels and purchase requests
- Dashboards and reporting: backlog, SLA attainment, cost per asset, planned versus reactive
Users, roles and permissions
A CAFM system typically has several user types working in the same data with different permissions. Administrators maintain master data and configuration. FM managers and supervisors plan, assign and approve. Helpdesk operators log and dispatch. Technicians and subcontractors see only the jobs assigned to them. Owners, clients and tenants may have read-only dashboards or a request portal.
Role-based access matters more than it first appears. When an owner and an FM contractor share one system, the owner needs to see everything while the contractor must not be able to edit a job's timestamps after the fact, otherwise the SLA figures cannot be trusted by either side.
How data flows through the system
A typical reactive job shows the flow end to end. A tenant reports a leak through the portal. The helpdesk classifies it against the right asset and priority, which starts the SLA clock. The system assigns it to the plumbing contractor. The technician receives it on mobile, scans the asset's QR tag on arrival, records the repair with photos and closes the job. A supervisor verifies it, and the cost, time and outcome land in the asset's history and the contractor's performance report.
Planned work follows the same path, except that the PPM schedule creates the job instead of a person. Inspections work the same way again, with a failed checklist item able to raise a corrective work order automatically.
Integrations, deployment and mobile
Three decisions shape how a CAFM system fits into an organisation: what it connects to, where it is hosted, and how well it works in the field.
- Integrations: common links include the BMS (so an equipment alarm can raise a work order), the ERP or finance system (for purchase orders, invoices and cost posting), single sign-on and staff directories, and IoT sensors for meter and condition readings.
- Cloud (SaaS): hosted by the vendor, quicker to deploy, updated centrally and paid as a subscription. The usual choice for most portfolios.
- On-premise: installed on the client's own servers or private cloud. Often chosen by government entities and organisations with strict data-residency or IT security policies.
- Mobile app: the part technicians actually use. It needs to work offline in plant rooms and basements with no signal, and to support QR or barcode scanning, photo capture, checklists and customer sign-off.
Common questions
What is a CAFM system?
A CAFM system is facility management software made up of connected modules (asset register, helpdesk, work orders, PPM, inspections, contracts, inventory and reporting) that share one database of buildings and equipment. Managers use it through a web application and technicians through a mobile app.
Is a CAFM system cloud-based or on-premise?
It can be either. Most new deployments are cloud-hosted SaaS, while government bodies and organisations with strict data-residency rules often choose on-premise. Reflexion, for example, is offered in both models, with offline-capable iOS and Android apps for field teams.
What systems does a CAFM system integrate with?
The most common integrations are the building management system, the ERP or accounting system, identity and single sign-on, and IoT or metering platforms. The finance link has become more important in the UAE as e-invoicing changes how maintenance invoices and deductions are issued.
How long does it take to implement a CAFM system?
It depends mostly on the state of the asset data. Configuring the software is usually the quicker part; surveying, tagging and loading an accurate asset register and PPM schedules takes longer, particularly across several buildings. A phased rollout, starting with one site or one service line, is the common approach.