Skip to main content

VDC & BIM Consulting

Strategic BIM implementation, execution planning, and workflow optimization tailored to your organization's needs and project goals.

VDC & BIM Consulting Services

Advice You Can Put Into a Contract

Most BIM problems are decided before anyone opens a model: an EIR nobody read, a template that cannot produce the schedules the owner asked for, a CDE where nobody can tell shared from published. This is advisory work that fixes those decisions while they are still cheap — the BEP, the standards, the exchange cycle and the acceptance criteria.

Your team keeps ownership throughout. We draft, review and recommend; you approve and issue. The engagement is written to end with your BIM lead running the process without us, and with a standards document they can hand to the next person who joins.

Consulting Services

The decisions worth making before production starts, made in the right order.

BIM Execution Planning

We turn an EIR into a BEP your task teams can actually follow, written around how this project is procured rather than a template with the names changed.

EIR interpretation and gap review
Pre-appointment and delivery BEP drafting
Information delivery plan and milestones
LOD matrix per the BIMForum specification
Task team responsibility matrix
Model origin, units and level strategy
BIM Execution Planning

Standards & Template Setup

The template, the parameters and the naming rules decided once, at the start, because every one of them is expensive to change after production begins.

Project template build and review
Shared parameter schema and classification
Naming convention for information containers
Workset and view discipline structure
Sheet, title block and annotation standards
Written standards document your team keeps
Standards & Template Setup

CDE & Workflow Setup

A common data environment configured so the status of every information container is obvious, and so issuing a model is a routine act rather than an email.

CDE structure and permission model
Work in progress, shared, published states
Approval and authorisation routing
Model exchange cycle and file formats
BCF issue workflow between task teams
Handover and archiving rules set up front
CDE & Workflow Setup

Coordination Facilitation

We set up and chair the coordination cycle, then hand it over. Your team runs it; we make sure it runs the same way every week.

Clash matrix and tolerance definition
Federation cycle and naming discipline
Coordination meeting agenda and cadence
Issue triage, ownership and escalation rules
Model health review against the BEP
Handover of the process to your BIM lead
Coordination Facilitation

How the coordination process we set up runs

The cycle we configure and then hand over: federation, a clash matrix, triage and sign-off you can evidence.

Inputs and coordination scope

We collect the discipline models, the BEP, the clash matrix if you have one, and the tolerances that matter on this project. If no matrix exists, we propose one and you approve it.

Model federation

Discipline models are assembled into a federated model on a defined cycle, with origins, levels and grids verified so clashes are real rather than alignment artefacts.

Clash testing

Hard, soft and clearance tests run to the agreed matrix and tolerances, rather than one indiscriminate all-versus-all run that buries the real issues.

Triage and classification

Raw results are filtered into genuine issues, grouped by cause and assigned an owner and priority. You receive decisions to make, not a five-thousand-clash report.

Constructability review

Beyond geometry: access for installation, maintenance clearances, routing sense and sequencing problems a clash engine cannot see.

Issue rounds

Issues are exchanged as BCF or in your issue tracker, re-tested each cycle, and tracked to closure with an auditable history.

Sign-off

A zone is released only when its open issues are closed or formally accepted, recorded against the agreed acceptance criteria.

Coordination record

Federated model, issue log, clash reports and the sign-off record, issued into your CDE.

What you actually get

How this differs from a BEP template with your project name pasted into it.

Reviewed by a registered architect

Aercon is architect-led — a registered architect oversees delivery, so your model is questioned on design and constructability, not only geometry. Sealing and professional responsibility stay with your professionals of record.

A clash matrix, not an all-versus-all run

Tests are defined per discipline pair with agreed tolerances. An indiscriminate run produces thousands of results and hides the handful that matter.

Constructability, not just geometry

We look at installation access, maintenance clearance, routing sense and sequencing — the problems a clash engine cannot see and site finds first.

Issues tracked to closure

Every issue is classified, owned, exchanged as BCF or in your tracker, and re-tested each cycle with an auditable history rather than a fresh report each week.

A QA record, not a QA claim

Three gates before anything leaves: modeller self-check, an independent reviewer who did not build it, then lead sign-off. The signed checklist ships with the deliverable.

Your drawings stay yours

NDA before we receive anything, access limited to the named project team, and we never reuse a client's models, families or drawings for anyone else.

Industries We Serve

Delivering BIM excellence across diverse sectors with tailored solutions.

Commercial
Residential
Healthcare
Hospitality
Education
Industrial
Infrastructure
Retail

Frequently Asked Questions

The EIR is the appointing party's statement of what information they need, when, and in what form. The BEP is the delivery team's answer: how that information will be produced, by which task team, in which software, to which standard. We can write either side, and we will tell you plainly where an EIR is too vague for anyone to price against.

Your team does. We advise, draft and recommend, and you approve. Standards, software choices and project protocols are issued under your name and stay under your control. We do not seal, stamp or certify any drawing or model, and design authority remains with your licensed professionals of record throughout.

ISO 19650 terminology for information management, the BIMForum LOD Specification for element definition, and whichever national annexe or owner standard your contract names. On the tool side we set up Revit, Navisworks, Solibri, ACC and BIM 360 environments, and we will configure the stack you already own rather than recommend a migration you do not need.

Both, and the documents are worth little alone. We run working sessions with your modellers and BIM lead against the actual project template, so the standard is learned on live content rather than read in a PDF. The written standard then exists as the reference your team returns to when a new person joins mid-project.

Technical issues go into your issue tracker or are exchanged as BCF, tied to a model element rather than described in prose. Process decisions are logged in a running decision register with a date, an owner and the reasoning. When the engagement ends you keep both, so the next person to ask why can find the answer.

Yes, and it is often the cheaper engagement. We read the BEP against the EIR and against how the project is actually resourced, then report where the two do not meet: undefined LOD, unowned information containers, exchange formats nobody can produce, or milestone dates with no production time behind them. You get findings and recommended wording, not a rewrite you did not ask for.

Have an EIR you need a BEP against?

Send the EIR and your current template. We will tell you where the gaps are before you commit to a scope.