CAFM software in Saudi Arabia: the questions to ask before you sign

Updated by HITEK AI

In short

Ask any CAFM vendor in Saudi Arabia for seven answers in writing: the country holding the database and backups, whether the interface mirrors fully for Arabic or only translates labels, how many points on a job are measured, whether service levels differ per contract and priority, which modules are included rather than add-ons, what data is needed before go live, and where support sits.

A demo shows you the software working. A contract shows you what happens when it does not. Most of the distance between those two sits in questions that never come up in a demo, not because anyone is hiding them, but because they are not on the slide.

If you are buying CAFM for a portfolio in the Kingdom, these are the questions worth asking before you shortlist, and what a solid answer to each one sounds like.

1. Where will our data be held, and where are the backups?

Ask for a country. Not a region.

“The Middle East region” is a cloud provider’s name for a group of data centres. It is not an answer to a contract clause. If your contract says client data stays in the Kingdom, you need a vendor who will write down the country where the database sits, the country where the backups sit, and the country the system is administered from. Those three can be different places, and often are.

Ask for it in writing before the commercial proposal rather than after. A vendor who will answer it in an email will answer it in a contract. A vendor who keeps moving the question to a later call has told you something.

Ask what happens if you would rather hold everything yourself. Some systems install on your own servers, some are cloud only, and several publish nothing either way.

A weak answer: “We use Azure.” A good answer: a named country for each of the three, in writing, before anyone talks about price.

2. Does the interface run in Arabic, or are the labels translated?

Not the same thing, and the difference shows up in week two rather than in the demo.

A translated interface swaps English words for Arabic ones on a layout that still runs left to right. A mirrored interface flips the whole thing: menus, tables, forms, the asset tree, and the column order in a report. If your technicians and helpdesk staff work in Arabic, the second one is what you are buying.

Test it instead of asking about it. Put the system into Arabic during the demo, then open a work order list, a form with several fields, and the asset tree. Print a job card. Printed output is where half-finished Arabic support usually shows itself.

Worth knowing before you shortlist: several widely sold CAFM platforms do not list Arabic among their supported languages at all, and others publish nothing about it either way. We went through eight of them and recorded what each vendor’s own site says.

3. How many points on a job are actually measured?

Most systems record two. When you responded, and when you closed it.

Two timestamps are enough to tell a client that a target was missed. They are not enough to tell anyone why. Say a job ran eleven hours against a four hour target. The difference between “we could not get anyone to site for six hours” and “we made it safe in forty minutes and then waited a week for a part” is the entire conversation you are about to have. On a two timestamp system those two look identical.

Ask how many points the system records between the request arriving and the job closing, and whether each one can be reported on separately.

4. Can service levels differ per contract, and per priority inside each contract?

If you run more than one client, you have more than one set of targets.

A hospital on 24 hour cover and an office tower on Sunday to Thursday, eight to five, cannot sit on the same clock. Ask whether rules are set per contract, whether each priority inside a contract can carry its own target, and whether each one can have its own operating days and hours. Then ask what the clock does outside those hours.

Ask who is able to change a target, and whether the change is logged. If anyone can edit a target after the job closed, the report built on it is worth less than it looks.

5. What is included, and what becomes an add-on at renewal?

Ask for the module list with the word “included” or “add-on” printed beside every line.

This is the question most likely to cost you money later and the easiest to answer badly in a demo, because in a demo everything is switched on. Two things are commonly priced separately and are worth naming out loud: performance or KPI scoring, and anything described as AI. Both are often sold as an upper edition rather than as part of the system you were just shown.

Ask what the price does at renewal, and what happens to it when you add sites or users.

6. What do you need from us before go live, and when?

The software is rarely what delays a mobilisation. The asset register is.

Ask for the list of data the vendor needs, and the date they need it by, in writing, before you sign. If they already publish that list, take it as a good sign. If they cannot produce it until after the contract is signed, your go live date is a guess.

Then ask the practical version. Can assets be loaded in bulk from a spreadsheet. Can they be corrected in bulk later, when you find the errors you are definitely going to find. Can the annual maintenance plan be uploaded the same way. Entering several thousand assets one screen at a time is how a mobilisation date quietly slips.

Further Reading: CAFM Implementation: What to Prepare Before Go Live

7. Who answers when something breaks, and in which time zone?

Ask where support sits, what hours it runs, and in which languages.

A local office is not automatically better. But a vendor with no presence in the region, no Arabic support, and a help desk eight time zones away is a different proposition when a chiller fails on a Thursday afternoon.

Ask for the escalation path in writing. Ask what the vendor commits to for their own support response, which is a separate thing from the service levels you offer your own clients. Those two get confused more often than you would expect.

Two things people assume, and should not

Hijri dates. Some teams need them, some have never asked. Do not assume a system has them, and do not assume it cannot be arranged. Ask whether it works out of the box or is configured on request, and get that answer before it becomes a surprise in week three.

Invoicing. Most CAFM systems do not issue invoices, and that is normal rather than a gap. Invoicing, and the compliance that goes with it, usually sits in your finance system or ERP. So the question is not whether the CAFM system issues invoices. It is how procurement and work order data gets from the CAFM system into the system that does.

The short version

Take this into the demo:

  • Which country holds the database, the backups, and the administration. In writing.
  • Arabic tested live on a list, a form, the asset tree, and a printed job card.
  • How many measured points exist on a job.
  • Whether targets can differ per contract and per priority, with their own hours.
  • The module list with “included” or “add-on” beside each line.
  • The go live data requirement, with a date, before signing.
  • Support location, hours, languages, and the escalation path.

Any vendor can answer all seven. The useful signal is how quickly they do it, and whether they will put it in writing before they talk about price.


Disclosure: HITEK AI publishes CAFMTEK, one of the CAFM systems sold in the Kingdom. This guide is written to be used with any vendor, ours included. Our answers to these seven questions are on the CAFMTEK Saudi Arabia page.