How to choose CAFM software in the UAE

Most CAFM buying decisions go wrong in the same way. A team watches four demos, every system looks capable, and they pick the one with the best presentation. Two years later they are still chasing technicians for job updates on WhatsApp.

The software is rarely the problem. The mismatch between the software and how the buildings are actually run is the problem. Here is how to avoid that.

What CAFM software actually does

CAFM stands for computer-aided facility management. In plain terms, it is the system that holds your asset list, receives job requests, sends work to technicians, schedules planned maintenance and keeps the record of what was done.

If your team currently runs on spreadsheets, printed job cards and WhatsApp groups, CAFM replaces all three with one record.

Start with your portfolio, not a feature list

Before you speak to any vendor, write down the shape of the job.

• How many buildings, and in which emirates
• How many assets you need to track, roughly
• How many technicians, and whether they are in house or subcontracted
• Who raises requests: tenants, a helpdesk, building owners, or your own supervisors
• What you are contractually required to report, and to whom

This page of notes is worth more than any feature comparison. It tells you which demo questions matter.

A team running two towers with ten technicians needs something very different from a team running ninety sites across the UAE for a mix of landlords. Software that suits one will frustrate the other.

Decide which jobs the system must do first

Every CAFM system claims to do everything. Rank what you need.

Reactive work orders and planned maintenance are the core. Almost every system handles both, so the question is not whether it can, but how many taps it takes a technician to close a job.

After that, decide which of these you need in year one and which can wait: asset register and history, spare parts and stores, contractor and SLA management, a tenant or helpdesk portal, energy monitoring, inspections and checklists.

Buying everything at once is the most common way to end up with a system nobody uses. Pick the two or three areas that hurt most now.

Checks that matter in the UAE

Some of these do not come up in generic buying advice, but they decide whether the system survives contact with a real UAE portfolio.

Language. Ask whether the technician app supports Arabic and any other languages your crews use. Ask to see it, not just hear about it.

Signal in plant rooms. Technicians work in basements, riser shafts and rooftop plant rooms where mobile signal drops. Ask what happens to a job update when the connection goes. If the answer is vague, ask for a live test.

Multi-site structure. If you manage buildings for different owners, check how the system separates them. You need reporting per building and per client without giving one client sight of another.

BMS and IoT links. Many UAE towers have a building management system controlling HVAC, lighting and pumps. If you want faults from the BMS to create work orders automatically, ask exactly how that connection is made and who builds it.

Data hosting. Government and semi-government clients often ask where data is stored. Ask the vendor which region hosts your data, and get it in writing if it matters to your contracts.

Statutory records. Fire systems, lifts and pressure vessels carry inspection and certificate requirements. Ask how the system stores certificates and warns you before one expires. Check the specific rules that apply to your buildings with your own compliance consultant rather than relying on a vendor’s summary.

Support hours. Check that support runs on a UAE working week and in a time zone that overlaps your day.

Test it with your own data

Ask each shortlisted vendor to load a slice of your real data into a trial: fifty of your assets, with your naming, your locations and one of your PPM schedules.

Then run your own test rather than watching theirs.

1. Raise a job the way a tenant would.
2. Assign it to a technician.
3. Have someone complete it on a phone, ideally standing in an actual plant room.
4. Pull the report you would send to the client.

If step four takes more than a few minutes, or produces something you would be embarrassed to send, that is your answer. Every system demos well. Not every system survives your own workflow.

Ask hard questions about AI features

Most CAFM vendors now advertise AI. Some of it is useful and some is a label on an old report. Three questions separate them.

What data does it need before it works? Predictive features learn from history. Ask how many months of data it needs before the output is worth reading.

Can I see why it made a recommendation? If the system says a chiller is likely to fail, it should show which readings led to that. A score with no explanation is not something you can act on or defend to a client.

What happens when it is wrong? Ask how a technician disagrees with a suggestion, and whether the system learns from that.

Work out the real cost

The licence fee is the part you get quoted. The rest you find later.

Ask for written numbers on implementation and configuration, data migration, integrations with BMS or ERP, training for each user type, ongoing support and annual increases, and the cost of adding users or sites in year two.

Also ask what happens to your data if you leave. Can you export the full asset register and job history, in what format, and at what cost? Do this before signing, not three years in.

Plan the implementation before you sign

The work that decides success mostly happens before go live.

Someone has to build a clean asset register. Someone has to tag assets physically so technicians can find them in the system. Someone has to set the PPM schedules. Someone has to train supervisors, who then train technicians.

Ask the vendor who does each of these, you or them, and what it costs. Then ask who from your side will own the project. A CAFM rollout with no internal owner drifts, whatever the vendor promises.

Mistakes that cost money later

Buying for the wrong user. The person signing usually wants dashboards. The person who decides whether it succeeds is a technician with dusty hands and a cracked phone screen. If the app annoys them, they will go back to WhatsApp.

Migrating a messy asset register. Bad data in an old system becomes bad data in a new one, and now you have paid for it. Clean the list first.

Skipping the offline test. Teams discover the connectivity problem in month two, after the contract is signed.

Treating training as a one off. Crews change. Ask whether training materials and refresher sessions are included, or charged each time.

A scoring sheet you can copy

Rate each shortlisted system from 1 to 5, and weight the rows that matter most to you.

Score it straight after each demo, while it is fresh. Comparing four systems from memory a month later is how teams end up choosing on presentation quality.

Where CAFMTEK fits

CAFMTEK is HITEK AI’s CAFM system. It covers work orders, planned maintenance, asset history and mobile job completion, and its AI features for fault detection, predictive maintenance and suggested PPM intervals are included as standard rather than sold as add-ons.

If you want to check it against the list above, the CAFMTEK fact sheet sets out what it does in plain terms, and the documentation covers the AI features and what implementation involves.

Use the scoring sheet on CAFMTEK the same way you would on any other system. A vendor confident in the product has no reason to ask for softer treatment.