Production, coordination and governance to ISO 19650, delivered as a full BIM team for consultants, contractors and developers. No internal hire, no management overhead.
Design and detail packages produced to your specification and checked against it before issue, so your review cycles shorten instead of multiplying.
Explore Build-sideCoordinated construction models and trade shop drawings for industrial and infrastructure builds, with deviation caught in the model rather than at the installation front.
Explore Owner-sidePortfolio-wide information discipline: one standard, one CDE protocol, and asset data at handover your operator can verify rather than take on trust.
ExploreStuttgart engineers to fine tolerances. So does our QA.
In an industrial and automotive region, your reviewers expect the last package to match the first, so we remove the variance before issue. 260+ engineers, and three signatures on every file: Author, Checker, Approver. The deliverable is inspected before it ships, and the inspection record ships with it.




























Each service runs through identical QA gates and carries an identical evidence record, so quality never depends on which service you bought.

Architecture, structure and MEP modelled and coordinated to your LOD specification, issued as drawing sets your site team can build from without interpretation.
Explore service
4D sequencing and 5D cost built from the federated model, so programme risk and budget drift surface in planning rather than in claims.
Explore service
CDE setup, naming conventions and exchange workflows run to ISO 19650, so your information manager governs the project instead of policing file names.
Explore
Asset models structured for operation from handover day, carrying the data your FM contractor needs rather than everything the authoring tool exports.
Explore
Quantities taken from the coordinated model and mapped to your cost structure, so estimating, procurement and claims reference one source.
Explore
Point cloud to record model for existing stock: retrofit, conversion and documentation of buildings that have outlived their drawings.
ExploreEight capabilities from one team and one QA system, so your project never coordinates across multiple BIM vendors.
Multidiscipline Revit and Civil 3D production with Navisworks federation, run to a single modelling standard across every package.
Parametric Revit families to your LOD and naming specification, from facade components to plant-room equipment.
4D programme simulation and 5D cost on the coordinated model, with 6D performance data where your brief calls for it.
Trade shop drawings coordinated against the federated model and issued at construction tolerance, ready for your site office.
Scan to BIM for the renovation pipeline: point clouds converted into reliable as-built models for retrofit and conversion work.
Archive 2D drawings rebuilt into coordinated 3D models, giving older assets a single current source of truth.
Asset data structured to COBie or your CAFM schema at handover, so operations starts with information instead of a search.
Model-based quantity take-off mapped to your cost codes, keeping tender, procurement and variations on one number.
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.
Remove the inspection and the defects ship: clashes surface during installation, drawing revisions contradict each other, and the handover dataset fails its first audit. On JES work no file leaves without its three signatures.
Airports, metro systems and industrial-scale developments coordinated to ISO 19650 across the Gulf, with the QA records to match. The Ortenberg office brings that method to Germany.

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 caseCoordinated drawing sets issued against the programme from a clash-checked federated model. Site queries drop because the answers are already modelled.
Author-Checker-Approver sign-off on every file, visible in ERP dashboards. You read where each deliverable sits instead of writing chasing emails.
ISO 19650 structure from kick-off: EIR interpreted, BEP written, CDE configured. The audit trail builds as the project runs.
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. We produce the models, drawings and coordination, and we govern the information through BEP authorship, the CDE and the ISO 19650 gate. One accountable team owns both, not a consultancy advising beside a shop that draws. In a region that expects the fiftieth package to match the first, that single ownership is what keeps the tolerance consistent across the programme.
Yes. A delivery lead owns your programme and embeds in your coordination, backed by 260+ engineers producing to a fixed method. Every file carries three signatures, Author, Checker and Approver, so the variance your industrial reviewers watch for is caught before issue. Capacity scales with the programme rather than sitting on your payroll, and one name stays accountable throughout.
Yes. Our consultants embed in your delivery, author the BEP, hold your LOD and check each package against your specification before it ships. Your review cycles shorten rather than multiply, because the inspection happens on our floor first. One named lead is accountable to ISO 19650 across the programme, so the fine tolerance your region works to is met on every issue.
Yes. We laser scan the existing facility, register the point cloud and produce a coordinated record model measured against what stands, useful for industrial and plant refurbishment. That verified base is what architecture, structure and MEP coordinate against, so deviation is caught in the model rather than at the installation front. It removes the measurement uncertainty before design begins.
Architecture, structure and MEP, authored in Revit and federated in Navisworks for regular clash cycles on one model. For industrial and infrastructure builds, deviation is caught in the model rather than at the installation front. Every file passes the Author-Checker-Approver gate against your BEP, and the inspection record ships with it, so your site team builds from a checked set.
Scope, disciplines, LOD and programme length drive it. A tightly checked industrial model to a high LOD carries more hours than a single package, so we scope to the actual work rather than a flat rate. The clearest way to judge the QA before committing is a zero-cost pilot on one package, inspection record included, so you see the gate in action.
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.