Every wall, slab, opening, and finish modeled to LOD 300 with material, manufacturer, and performance data — then taken to LOD 400 for fabrication-ready shop drawings. Federated with structural and MEP, ISO 19650-compliant, tender-clean.
When the model is treated as a render-only artifact, contractors get sheets that don't match. RFIs spike. Variations multiply. The cost is paid in site time.
A wall with no material, no manufacturer, no fire rating, no acoustic spec is just a rectangle. Without parametric data the model can't feed BOQ, schedules, or compliance — defeating the point of BIM.
Architectural elements modeled separately from structural and MEP guarantee clashes at site. The federated model has to be the single source of truth from LOD 300 onwards.
Most projects only need LOD 300 to tender. Some — heritage restoration, premium hospitality, prefab-heavy structures — push to LOD 400 for fabrication. We deliver both, and the transition is seamless because it's the same model maturing.
Tender-ready federated model. The deliverable contractors price from.
Shop-drawing-ready. The deliverable fabricators build from.
We don't open Revit until the information requirements are written. The EIR (Exchange Information Requirements) and BIM Execution Plan come first. That up-front rigour is what makes LOD 300 → LOD 400 flow without rebuilds.
Information requirements written before any geometry — what the owner needs at handover dictates how the model is built from day one.
Architectural, structural, and MEP teams co-author the same shared coordination model. Weekly clash detection. No "throw it over the fence" handoffs.
Construction drawings, schedules, and specifications all extract directly from the LOD 300 model — version-controlled, automatically synced, tender-ready.
For elements that go to fabrication — façades, joinery, complex assemblies — the model matures to LOD 400 with manufacturer families and shop-drawing automation.
90,000 m² pavilion + operational building. Architectural BIM authored at LOD 300, coordinated with MEP across both blocks, delivered to Royal Commission Riyadh and Freyssinet Contractors. Saudi Arabia's flagship cultural destination — modeled, coordinated, and tender-released through our delivery.
LOD 300 means the model element is geometrically accurate, identifiable, and has correct quantity, size, shape, location, and orientation — sufficient for tender documents and clash coordination. LOD 400 adds detailing, fabrication, assembly, and installation information so the element can be manufactured directly. For a curtain wall: LOD 300 shows the panelisation grid and frame depth; LOD 400 shows mullion sections, gasket profiles, anchor clips, and fabrication splices. Most Saudi giga-projects tender at LOD 300 and require LOD 400 only for façade and joinery packages.
Autodesk Revit is our primary authoring platform for architectural models — it's the de-facto standard on Saudi giga-projects and integrates cleanly with our MEP and structural workflows in the same federated environment. Navisworks Manage handles federation and clash detection across disciplines. We also use Revit add-ons (Dynamo for parametric modeling, Enscape for real-time visualisation, MagiCAD where MEP packages require it). For specific deliverables we may add Rhino/Grasshopper for facade geometry, then bake into Revit families.
Parametric workflow: Rhino/Grasshopper to define the underlying geometry rule (panel size, curvature, perforation pattern), then auto-generate Revit families that respect the rule and update when the rule changes. This is how we modeled the Visitors Pavilion at King Salman Park — the curved aluminum facade has 1,400+ unique panels, all driven by a single parametric definition. Without this approach, the facade alone would have been 3-4 months of repetitive Revit work; with it, two weeks.
Yes. LOD 400 fabrication-ready families include: parametric profiles (so the fabricator can extract CAM-ready geometry directly), embedded type catalogs for material/finish variants, parameter mapping to the contractor's BoQ system, and fabrication-stage sub-elements (e.g., a curtain wall family with separate sub-families for the mullion, transom, gasket, anchor clip, glazing). We've delivered LOD 400 facade and joinery packages on 8 projects to date.
Federated authoring: each discipline owns its own Revit model in the shared CDE (Autodesk BIM 360). Weekly federation in Navisworks runs clash detection across all three disciplines + the previous federation snapshot, so we catch new clashes immediately. Issues are filed via BCF (BIM Collaboration Format) and assigned to the discipline that owns the geometry. We track resolution in BIM 360 issue management. Stage gates require zero priority-1 (e.g., structural steel through MEP duct) and zero priority-2 (e.g., MEP through architectural ceiling void) clashes before the model can advance LOD.
Drop your details — a senior BIM lead will reach out.
60 seconds — name, email, scope brief.
A senior BIM lead reads your scope and replies — bilingual EN/AR.
Real conversation. EIR + BEP scope outline. ISO 19650 aligned.