Production, coordination and governance to ISO 19650, delivered as a full BIM team for consultants, contractors and developers. No internal hire, no management overhead.
High-volume design production for practices holding NEOM scopes, modelled to the package BEP and returned with the compliance evidence attached.
Explore Build-sideCoordination, fabrication-level detail and information deliverables for contractors entering giga-project supply chains, where rejection at the gate stalls payment and programme.
Explore Owner-sideFor delivery partners and package owners: one enforced information standard across your subcontracted modelling chain, with a named approval trail on every file.
ExploreNEOM packages are accepted through data review. JES files are built to pass it.
Package deliverables are specified, reviewed and accepted against information requirements before anything physical exists. JES runs Qiddiya, Rua Al Madinah and Red Sea coast packages through one ISO 19650 system today: named approvals, complete audit trails, machine-checkable deliverables.




























Everything JES issues into a giga-project carries ACA sign-off, ERP traceability and ISO 19650 alignment, reviewed against the package specification before issue.

Discipline models and drawings produced to exacting LOD and naming specifications, validated before issue rather than corrected after rejection.
Explore service
4D and 5D models for builds without precedent, so logistics and cost get tested in the model before they are committed on the ground.
Explore service
Information management for data-first delivery: CDE workflows, exchange protocols and compliance reporting run as a service.
Explore
Asset data structured for operations from the outset, because on a greenfield programme the operational model is a contract deliverable, not an afterthought.
Explore
Quantities derived from validated models, giving package owners measurement they can defend up the chain.
Explore
Scan-verified records reconciling built work to the model at each stage, keeping the record continuous from early works onward.
ExploreThe full BIM scope, delivered into NEOM packages by a team already producing for the Kingdom's largest programmes.
Multidiscipline modelling to tight LOD and classification specifications, checked by machine and by named engineers before issue.
Custom content built to package data requirements, with parameters structured for downstream automation.
Construction simulation for sequences without precedent, surfacing logistics conflicts while they are still theoretical.
Fabrication-level detailing coordinated in the federated model, for off-site manufacture as much as on-site assembly.
Point-cloud verification reconciling early works to the model, anchoring the programme's data to measured conditions.
Legacy and reference 2D information restructured into compliant model data instead of being carried as flat files.
Operational data architecture from the first model, so the asset's twin grows with construction instead of being assembled at the end.
Model-derived quantities with full traceability from number back to element, the way giga-project commercial teams require.
Every JES deliverable moves through a fixed Author-Checker-Approver gate, tracked in the CDE. The same standard whether it's engineer 3 or engineer 250.
On a conventional project a weak file costs rework. In a giga-project supply chain it costs more: non-compliant deliverables are rejected at the gate, package payments stall, and a supplier's position in the chain comes under review. JES files arrive with their Author-Checker-Approver history attached, so compliance is demonstrated on the file itself.
JES produces packages for Qiddiya, Rua Al Madinah, Six Senses Red Sea and the Red Sea Marine Life Institute. The same system stands behind NEOM supply-chain work.

Terminal-scale design packages for Dar Al-Handasah on Dubai World Central's next…
Read the case
MEP modelled and coordinated across Blue Line stations and depots for MNG Esmas,…
Read the case
Over 100 people at peak across MEP, structural and interior fit-out packages on …
Read the case
Every N+1 and 2N redundancy path verified in 3D against Tier-rating requirements…
Read the case
Mechanical, electrical and plumbing threaded through Foster + Partners' steel-fe…
Read the case
Shop drawing release synced to the tower pour cycle on AFE's fast-track golf-fac…
Read the case
Every consultant and contractor on Al-Futtaim's master-planned villa and low-ris…
Read the caseDeliverables validated against the package specification before issue, so they pass the gate the first time.
Every file's status, author and approval history visible in ERP, ready for whatever audit the programme runs.
ISO 19650 as the baseline, with naming, CDE and exchange discipline tuned to the stricter requirements giga-projects layer on top.
Why "coordinated" models still cause site rework, and the handoff that fixes it.
ReadThe difference between a filed document and a working agreement is five sections.
ReadZero hard-clash is table stakes. Here is the tolerance standard we hold a federated model to before sign-off.
ReadWhen quantities come straight from the model, variations stop being arguments and become deltas.
ReadRetrofitting an as-built at practical completion is a tax. Updating it weekly is a habit.
ReadBoth. JES is a BIM services company that produces the models and drawings and governs the standards they are reviewed against, which matters where packages are accepted through data review before anything is built. We author the BEP, run the CDE and hold the Author-Checker-Approver gate on every file, so you get machine-checkable deliverables and the governance behind them from one accountable team rather than a consultancy plus a drafting shop.
Yes. We embed as a dedicated, outsourced BIM team under one delivery lead, running your NEOM supply-chain packages through one ISO 19650 system with named approvals and complete audit trails. Qiddiya, Rua Al Madinah and Red Sea coast packages have run through that floor, so your project joins a proven system with capacity scaled to the package rather than waiting on a recruitment cycle.
Yes. Our BIM consultants embed in your delivery and hold it to ISO 19650, setting the LOD and naming specifications the package requires and validating every file against them before issue. One named lead stays accountable across the programme, so a deliverable reviewed against information requirements arrives with its compliance already built in rather than corrected after rejection.
Yes. We laser-scan the works, register the point cloud and model it into a scan-verified record that reconciles built work to the model at each stage. That keeps the record continuous from early works onward, which is exactly what a giga-project supply chain needs when each stage has to close with evidence before the next one is accepted.
We model architectural, structural and MEP to the exacting LOD and naming specifications the package sets, coordinating them on one federated model and running regular clash cycles. Every discipline is validated before issue rather than corrected after rejection. A deliverable entering data review is machine-checkable and reconciled across trades from the file itself.
Cost follows scope, the disciplines involved, the LOD you need and the programme length, so a district package carries far more than a single building. We scope each engagement to the actual work rather than a flat rate. The zero-cost pilot on one package lets you see the validated, review-ready output before committing to the supply-chain programme.
The full ACA framework PDF, the Responsibility Matrix template, and the EIR / BEP checklist we use on every project.
We'll walk you through a live ERP dashboard from an active project and you'll walk away with our ACA template, whether or not we work together.
We run the ACA framework on a single package. You get ERP visibility from day one. Zero-cost pilot, capped scope, clear exit.