What the evaluation committee asks.

Questions that come up in every engagement. The answers here are the same ones that appear in the technical proposal — not marketing copy.

• Where is our data stored?

  Three options: our cloud, as the system runs today; a server inside your own infrastructure; or the application on our cloud with the data in your database. The second and third are technically supported but have not yet been deployed for a client, and each is scoped as a separate deployment project. If you have a data-residency requirement, it is settled before the contract, not after.

• Does it align with the Essential Cybersecurity Controls (ECC)?

  It is built on an ECC compliance matrix with an automated guard that blocks any claim of a control that is not actually active. What the matrix says is tied to what is actually applied in the database, not to what is written in a document.

• How is our data isolated from another client?

  Isolation lives in the database itself, not in the interface — so a request that bypasses the interface does not bypass the isolation. It is tested automatically before every release.

• Does it work offline?

  Partly. Previously opened pages may stay viewable without a connection, but creating a new incident, changing status and any save require a connection. The system is an app installed once on phone and desktop.

• Who does the client contract with?

  A registered freelance entity under Naif Ahmed Farghal, holding two valid documents used to issue invoices and sign contracts. Both document numbers are published on this site for direct verification with the issuing authority.

• Is any organisation using Idrak today?

  An operational build of the system has been technically deployed since 31 May 2026; this is not evidence of an external paying customer. The names, logos and data screenshots of any organisation are never published — not on this site and not in the demo. Any mention of the developer’s professional experience describes that experience alone: it is not a customer claim, and not an endorsement by an employer. What is offered during evaluation is a written reference with its owner’s permission, not a name on a page.

• How is it different from a conventional CMMS?

  The action happens where the work happens: the technician issues the spare part and takes custody of equipment from inside the incident screen, not from another screen. Friction is not a comfort question — a system that costs more attention than the ad-hoc way gets filled in late and approximately, and that produces reports that look correct and are false.

• What is fixed at no charge, and what is priced?

  If the system does not do what it is documented to do, that is a defect: fixed at no charge and with no work order. Anything beyond the documented behaviour is a change request with a scope, an estimate and written approval. That line is written before the contract, not after the first dispute.

• What happens if the developer stops working on it?

  One developer today — stated plainly, because the procurement committee will ask. What answers it is written into the contract: handover of source and data in open formats, and the client’s right to continue without depending on any individual.