Techbanq

Real estate · a buyer’s guide

Facilities technology has three acronyms and one buying decision

CMMS, CAFM and IWMS describe genuinely different tools wearing confusingly similar brochures, and the estates that buy badly usually bought the wrong category, not the wrong product. This guide separates the categories, the sensors worth paying for, and the questions to settle before a contract is signed.

Serving Saudi Arabia from our Riyadh office and our engineering hubs in Lahore and Karachi

Engineers in safety equipment inspecting plant machinery
  1. 01

    Market

    Saudi Arabia

  2. 02

    Written for

    COO, Procurement

  3. 03

    Decision

    Choose the right category of facilities technology before choosing a product

  4. 04

    Languages

    EN · AR

Enterprise delivery credentials

  • ISO

    ISO/IEC 27001

    ISO/IEC 27001 certified

Certifications & registrations

The categories

CMMS, CAFM and IWMS are three answers to different questions

The names overlap in marketing and diverge in practice. The honest distinction is the core record each one is built around — and buying a broader category than your operation needs is paying for modules that become shelfware.

OptionThe core record it is built aroundWho lives in it dailyWhat it deliberately leaves outThe integration burden it bringsBest for
CMMS — maintenance firstThe work order and the asset: what broke, what is due, what it cost to fix.Maintenance teams and their supervisors — the tool of the workshop, not the boardroom.Space, leases, moves, capital planning — anything that is not keeping equipment running.Light: finance for costs, stores for parts — a manageable surface.Operations whose problem is maintenance discipline, not estate administration.
CAFM — the facility around the maintenanceThe facility itself: spaces and floor plans, the assets within them, the services and bookings against them.The FM office — helpdesk, planners, contract supervisors — with technicians on its mobile edge.Deep finance, HR and property functions — it coordinates with them rather than replacing them.Moderate: finance, building systems and identity each usually connect.Estates run as services to occupants, with helpdesks, SLAs and contractors to manage.
IWMS — the whole workplace portfolioThe portfolio: real estate and leases, capital projects, space, maintenance and sustainability in one suite.Corporate real estate and workplace teams across many properties — several departments, one system.Little by design — which is the trap: every module bought is a module to implement, integrate and feed.Heavy: ERP-grade programmes measured in quarters, with data governance to match.Large occupiers and portfolio owners consolidating several functions deliberately, with the programme muscle to carry it.

Sensors and IoT

A sensor pays where a visit is expensive and a failure is quiet

The economics of facilities IoT are simple even when the brochures are not: a sensor earns its keep where it replaces a costly routine visit or catches a quiet failure before it becomes a loud one. Water leak detection in risers and plant rooms pays because the failure it catches is silent, fast and ruinous. Remote tank, filter and plant monitoring pays where the alternative is a technician driving across a large estate to look at a gauge. Condition monitoring on the handful of assets whose failure stops the business — chillers, main pumps, lifts — pays through earlier, cheaper interventions. Occupancy sensing pays in estates that clean, cool and staff by schedule when usage actually varies, because it converts fixed routines into demand-driven ones.

The corollary deserves equal weight: instrumenting everything because a platform makes it cheap produces dashboards nobody opens and alerts everybody mutes. The filter question for any proposed sensor is operational, not technical — which specific decision or work order changes when this reading arrives, and who acts on it. A reading that triggers a work order in the FM system is an investment; a reading that populates a chart is a subscription. Estates already holding a BMS should also exhaust what it measures before buying parallel devices, which is a survey question rather than a purchasing one.

Before you sign

Four integration questions that decide whether the platform will actually fit

Integration is where FM platform implementations go over budget and under expectation, and every one of these questions is cheaper to ask before the contract than after it.

01

Which system masters the asset register

The FM platform, the finance system’s fixed-asset ledger and any BMS all hold asset lists, and they will diverge unless one is declared the master and the others subscribe. Decide this before data is loaded anywhere — merging three registers later is a project of its own.

02

How work-order costs reach finance

If completed work, parts and contractor charges do not flow to the finance system, someone re-keys them monthly forever — and the cost-per-asset reporting both systems promise is built on that person’s patience. Ask to see the finance integration running, not listed.

03

Whether it can hear the buildings

A BMS alarm that automatically raises a prioritised work order is the difference between a fault attended tonight and one discovered on the morning round. Establish which building systems the platform can listen to, over which protocols, and what each connection costs.

04

How contractor identities are granted and revoked

Outsourced estates put hundreds of external technicians in the system, and each needs an account that exists exactly as long as the contract does. If joiner and leaver flows are manual, the platform accumulates ghost users with live access — an audit finding waiting to be written.

The selection path

Choosing facilities technology by the way the estate is actually run

The sequence matters: each step narrows the field before the next spends effort on it, and the vendor demo arrives at the end of the path rather than the start.

STAGE 01

Name the operating model first

An in-house operation needs deep planning, stores and workforce tools; an outsourced one needs contract, SLA and evidence management with contractor portals; a mixed estate needs both to meet on one record. The model, not the org chart’s ambitions, sets the requirement. A requirements list that reflects who actually does the work.

STAGE 02

Shortlist the category before any product

Decide whether the problem is maintenance discipline, facility service management or portfolio consolidation — CMMS, CAFM or IWMS territory respectively — and refuse to let a vendor demo upgrade you a category. The commonest expensive mistake is buying IWMS breadth for a CMMS problem. Two or three candidates in the right category, not eight across three.

STAGE 03

Put the shortlist in technicians’ hands

The people who decide adoption carry tools and phones, not opinions about dashboards. Have real technicians run real jobs through each candidate’s mobile flow — in Arabic and English, in a basement with no signal — and weight their verdict above the feature matrix. A field verdict before a commercial one.

STAGE 04

Price the integrations, not just the licences

Put the four integration questions to each finalist in writing, and cost the connections to finance, buildings and identity as part of the deal — because that is where the budget overruns live, and a vendor’s answers harden usefully when they are contractual. A total cost that includes the joins.

STAGE 05

Pilot on one building with exit criteria

Run the chosen platform on one building for a defined period with agreed pass criteria — jobs actually flowing, evidence actually captured, costs actually reaching finance — before the estate-wide rollout, so a wrong choice costs a quarter instead of a programme. Evidence before commitment.

Our role

What we contribute to an FM technology decision without selling a platform

  1. 01

    Selection without commission

    We resell no FM platform and take no referral fee, so the category recommendation and the shortlist scrutiny serve one interest — the estate’s. Where a packaged product fits, that is the advice, in writing.

  2. 02

    The joins the platform needs

    We engineer the integrations the guide keeps returning to — finance, building systems, identity, the BMS alarm that becomes a work order — because they are software engineering, and they are where implementations actually struggle.

  3. 03

    Custom software where the category ends

    Every estate has workflows no packaged product models — a giga-project’s phased handovers, a heritage site’s permit regime, a mixed-use estate’s owner structures. We build those edges against the platform’s records rather than beside them.

The platform contract, the FM operation and the service levels promised to occupants stay with the estate and its suppliers; we make sure the technology decision is made on evidence and the systems actually connect once it is made.

Common questions

What buyers ask

Is an IWMS overkill for a single large estate?+

Usually, yes — even a very large one. The IWMS proposition is consolidating functions across a portfolio: many properties, lease administration, capital projects, space and maintenance under one suite. A single estate, however big, typically needs the CAFM core — helpdesk, work orders, SLAs, contractors, space — done excellently, with strong links to finance and its buildings, and gains little from lease-administration and capital-project modules that sit unimplemented while their licences renew. The exception is an estate that is genuinely a portfolio in one place — a giga-project district with multiple asset classes, operators and ownership structures — where portfolio-grade tooling can be justified. Even there, the honest sequencing is to prove the operational core first, because an IWMS programme that starts everywhere finishes nowhere.

Does outsourcing our FM change which facilities system we should buy?+

It changes both the emphasis and, more importantly, who should own the system. An outsourced operation needs the platform to be strong exactly where an in-house one barely uses it: contract scopes, SLA measurement per supplier, evidence-based invoice reconciliation and contractor identity management. But the deeper question is ownership. When the FM contractor brings its own system, the estate’s asset histories, failure patterns and performance records accumulate inside a supplier’s tenant — and walk away at retender, taking the estate’s memory and its negotiating evidence with them. Our consistent advice is that the estate owns the system and the data, and contractors work inside it; where that is not immediately possible, the contract must at minimum guarantee complete, structured data export and make the register and history the estate’s property. The system outlasting any one supplier is the point.

What makes technicians actually use a workforce app instead of working around it?+

The app has to cost less effort than the workaround, every single time. That means a job opens in two taps and closes in a handful more; photos, checklists and part scans replace typing wherever typing can be replaced; the interface works properly in the technician’s own language; and — non-negotiable on real estates — everything keeps working in a basement plant room with no signal, syncing later without losing a thing. It also means the app gives before it takes: the asset’s history, the manual, the location and the previous fix visible on the job beat any argument about compliance. And supervision has to hold the line — the job assigned through the app, not through a phone call that bypasses it — because the day dispatch goes back to WhatsApp is the day the record forks. Where those conditions hold, adoption is unremarkable; where they do not, no amount of training compensates.

A selection conversation that starts from your operating model and ends with a shortlist of categories — before any vendor demo is booked.

Walk it through your estate