BIM, end to end. Standards-led. Vision 2030-ready.

Yes, for government building projects. The Ministry of Municipal and Rural Affairs and Housing (MOMRAH) made BIM compulsory for public-sector building projects from 1 January 2024, in line with Vision 2030's push toward data-driven delivery. In practice the major Vision 2030 giga-projects — and the consultants and contractors bidding on them — already require ISO 19650-aligned BIM regardless of sector, so for most serious work in the Kingdom BIM is now the baseline, not an option.

CAD produces drawings — lines, arcs, and text that represent a building. BIM produces an information model — objects that carry data such as material, fire rating, U-value, manufacturer, and cost, and that automatically update every plan, section, schedule, and quantity when an element changes. That data layer is why BIM can drive clash detection, quantity take-off, construction sequencing, and facilities handover, and why a flat CAD file cannot. CAD is a deliverable; BIM is a process that produces many coordinated deliverables from one model.

It means one continuous information chain from the project brief to building operation, rather than disconnected modeling tasks. End to end we author the federated model, coordinate the disciplines, generate the documentation and quantities from that model, link it to program and cost, and hand over as-built data the owner can operate from — all governed through a single Common Data Environment under ISO 19650. The opposite is piecemeal BIM, where each consultant models in isolation and the owner inherits files that don't talk to each other. We deliver the full chain across our six disciplines and the 11-stage lifecycle.

LOD (Level of Development) describes how mature an individual element is — broadly, how much geometric and data detail it carries, from generic (LOD 200) to tender-ready (LOD 300) to fabrication-ready (LOD 400). Level of Information Need is the ISO 19650 concept that goes further: it specifies, for a given deliverable and purpose, the right combination of geometric detail, alphanumeric data, and documentation — explicitly to avoid over-modeling. The point is that more detail is not automatically better; the brief should request exactly the information a decision needs, and no more. We set both in the EIR before any geometry is built.

They describe what data the model carries beyond geometry. 3D is the coordinated, clash-checked model. 4D adds time (the build sequence) and 5D adds cost (live quantities and budget) — we run both as construction-coordination workflows, explained in full on our VDC page. 6D carries sustainability and energy-performance data for analysis and reporting. 7D is the operational layer — the as-built asset data handed to facilities management at completion, which is where a BIM model becomes a digital twin. Owners rarely need all seven on every project; we scope the dimensions to the decisions you actually need to make.

No — done properly, BIM is vendor-neutral at the exchange layer. We author primarily in Autodesk Revit because it is the de-facto standard on Saudi giga-projects, but deliverables are exchanged in open buildingSMART formats — IFC for the model and BCF for coordination issues — so your data is not trapped in one vendor's file. ISO 19650 and the openBIM approach exist precisely so that an owner, a contractor, and a dozen consultants on different software can collaborate around one coordinated source of truth and so the asset data survives long after any single license expires.

Clash detection is the automated coordination check that finds where the architectural, structural, and MEP models occupy the same space — a duct running through a beam, a pipe crossing a door swing — before any of it reaches site. We federate the discipline models (typically in Autodesk Navisworks or the Construction Cloud) and run hard, soft, and workflow clash tests, resolving them at LOD 300 so the coordinated model that goes out to tender is genuinely buildable. Catching a clash in the model costs minutes; catching it on site costs weeks and a variation order — which is why clash detection is the clearest, fastest return on BIM for an owner or contractor.

Not a folder of drawings — a structured Asset Information Model (AIM). At completion we hand over the as-built federated model plus COBie-structured asset data: every space, system, and maintainable component tagged with what a facilities team needs to operate the building — manufacturer, model, warranty, and maintenance regime. That AIM satisfies the Asset Information Requirements (AIR) the owner set at the start under ISO 19650, and it is the foundation a digital twin is built on. The result is a building the owner can run from data, not from guesswork.

Look for four things. First, genuine ISO 19650-2 certification from an accredited body (not merely "familiar with" the standard) — the certification should be verifiable, as ours is (ISO 19650-2, via BSI) on our About page. Second, bilingual EN/AR delivery, because Saudi tenders and authority submissions run in both. Third, evidence of federated, multi-discipline coordination on comparable scale — ask to see how they handle clash detection and the CDE, not just pretty renders. Fourth, lifecycle depth: a consultant who can carry the model from brief through fabrication to operational handover, rather than one isolated stage. We meet all four; a short scoping call is the fastest way to test any consultant against them.

Either. Many clients engage us for a single discipline — architectural BIM, MEP coordination, scan-to-BIM, clash detection, or an ISO 19650 information-management setup — and others hand us the full federated delivery from brief to handover. Because all of it runs on the same standards backbone, a focused engagement can scale up cleanly later without rework. Send the scope you have today and a senior BIM lead will map it to the right entry point across our 11-stage lifecycle.