AI-Powered Facility Management for Smart Buildings, Assets & Maintenance

Facility management software is a system for managing buildings, assets and maintenance operations in one place. It holds the asset register, schedules preventive maintenance, raises and tracks work orders, manages technicians and contractors, and reports on cost, compliance and service levels.

CAFM stands for Computer-Aided Facility Management. It focuses on the building and the space — floor plans, rooms, occupancy, moves, and the assets within those spaces — alongside maintenance and service requests.

CMMS stands for Computerised Maintenance Management System. It concentrates on maintenance execution: the asset register, preventive maintenance schedules, work orders, spare parts and maintenance history.

CMMS is maintenance-led and asset-centric; CAFM is building-led and space-centric. CMMS answers "is this equipment maintained?", CAFM also answers "how is this building used?". Most enterprise deployments today need both, which is why the Swedish Technology platform covers maintenance, assets, space and service requests together.

Yes. The hierarchy runs organisation, country, city, site, building, floor, zone, room and asset. Each site keeps its own operating detail while group management compares SLA, cost, energy, asset health and contractor performance across the estate.

Yes. Schedules can be driven by date, frequency, runtime hours, meter readings, usage, season, manufacturer recommendation or contract requirement, and each occurrence generates its work order, checklist, assignment, parts and SLA automatically.

Yes, where the supporting data exists. Prediction needs condition data from sensors or controllers, a reasonable history of faults and work orders, and consistent asset identification. Without those inputs we start with condition monitoring and build toward prediction rather than claiming it from day one.

Yes. A sensor event is evaluated against a rule or model, becomes an alert with a severity, and raises a work order against the correct asset with the technician assigned — without anyone watching a screen.

Yes, subject to what the BMS exposes. Integration typically uses BACnet, Modbus, OPC, MQTT or a vendor REST API. Whether a given system can be read from, or written to, depends on the controller generation and the vendor's access policy, so this is confirmed by survey. The FM platform complements a BMS rather than replacing it.

Yes. Revit and IFC data can be linked so assets carry their model location and metadata into operations, and technicians can find equipment in 3D, open its history and see open work orders against its real position.

Yes. GIS integration is used for outdoor and distributed assets — streetlights, pumping stations, utilities, parks, signage and remote buildings — and for campus and multi-building visualisation.

Yes. Assets can carry QR, barcode or RFID identity. Scanning opens the asset record with its manuals, maintenance history, open work orders, warranty status and recent sensor readings.

Yes. Technicians receive work orders, scan assets, view history and manuals, run checklists, record readings and parts, attach photos and signatures, and close or escalate jobs from the field.

Offline job access, cached asset data, checklists and photo capture with sync on reconnection are configured per deployment. Plant rooms and basements rarely have coverage, so we scope offline behaviour against your actual sites rather than assuming it everywhere.

Yes. Requests can come from a web portal, mobile app, QR code in the room, call centre, email, WhatsApp Business, kiosk or API, and a tenant portal can expose status tracking, documents, announcements and satisfaction rating.

Yes, through the official WhatsApp Business platform with approved message templates. A message is classified, matched to a site and raised as a ticket, with status updates returned on the same thread. We do not automate personal WhatsApp accounts.

Yes. Contractors, contracts, scope, SLA, insurance, trade licence, certifications and work permits are tracked, with assigned jobs, performance scoring, penalties and invoice status, plus expiry alerts on every document.

Yes. Part catalogue, stores and bins, minimum stock and reorder levels, reservation against work orders, issue and return, consumption history, supplier and cost — with optional barcode or RFID identification.

Yes. Odoo integration typically covers purchase requests, vendors, stock, invoices and cost centres. It is built as an API or custom integration and scoped against your Odoo version and modules.

Yes, via API or middleware, commonly for purchase orders, materials, vendor master data, asset finance information and cost allocation. We do not describe these as pre-certified native connectors; scope is confirmed against your versions, licences and network access.

Yes. Cloud, private cloud, UAE-hosted, on-premises and hybrid deployments are all supported, and the available functionality does not change with the hosting model. Government and regulated customers frequently choose on-premises for data residency.

Yes. Arabic and English interfaces with right-to-left layout are supported, which matters where field and technician teams work in Arabic while management reports in English.

Yes. Electricity, water, gas, district cooling and solar can be monitored with consumption, cost, peak demand, baseline variance and energy per square metre, and AI can flag abnormal overnight use, HVAC running outside schedule and equipment drifting from its own baseline.

Yes to both. The copilot answers questions about assets, work orders, SLA failures and repeated faults in plain language, and manuals, SOPs and procedures can be indexed so technicians retrieve the relevant procedure instead of searching a long PDF. Retrieval respects existing user permissions, and can run on private or on-premises AI infrastructure.

Yes — from Excel, CSV, a legacy CMMS or CAFM, ERP asset lists, BIM/Revit data, GIS databases, or platforms such as Maximo where export or API access permits. The migration path is discover, clean, map, import, validate, go live. The common constraint is legacy data quality rather than the transfer itself.

Look for Arabic and English interfaces, deployment options that satisfy your data-residency position, multi-site hierarchy, mobile working that survives poor coverage in plant rooms, integration with your existing ERP and building systems, and honest scoping of what integration actually requires. Statutory inspection regimes and contractor documentation control also matter more here than generic feature lists suggest.