Skip to main content

Civil & Utilities BIM Services

Infrastructure and site modeling including grading, utilities, and coordination for horizontal construction projects.

Civil & Utilities BIM Services

The Site the Building Has to Sit On

Horizontal work fails quietly. A grading surface that does not tie to the building finished floor level, or a duct bank routed under a pile cap, stays invisible until the excavator finds it. We model the site, the buried services and the road and drainage network as one coordinated set, referenced to the project survey control.

We work to your civil engineer's design inside your template and BIM Execution Plan. Design authority, calculations, code compliance and sealing stay with your professionals of record; we produce the model, the data and the documentation behind them.

Civil & Utilities Scope

Surfaces, buried services and the coordination that ties the site to the building.

Site and grading

Existing and proposed surfaces built from the survey, with the tie-ins, retaining conditions and earthwork volumes the rest of the design depends on.

Existing and proposed surfaces
Corridor and pad grading
Retaining walls and slope tie-ins
Cut and fill volume surfaces
Survey control and coordinate setup
Building-to-site level tie-ins
Site and grading

Underground utilities

Buried services modelled as solids with real inverts, cover and bedding, including the recorded existing runs nobody wants to find with an excavator bucket.

Water, sewer and storm networks
Gas, electrical and telecom duct banks
Manholes, chambers and structures
Invert levels and cover depths
Existing utility records and survey data
Service crossing and clearance checks
Underground utilities

Roads and drainage

Carriageway geometry and the drainage network modelled together, because the kerb line and the gully positions are one problem rather than two.

Horizontal and vertical alignments
Pavement build-ups and cross sections
Kerbs, footways and crossings
Gullies, channels and outfalls
Detention and attenuation structures
Network connectivity and fall checks
Roads and drainage

Civil–structure coordination

The site model federated with the building models, so foundations, basements and buried services are checked against each other while a change is still a drawing revision.

Shared coordinate alignment
Foundation and utility conflict checks
Basement and podium interfaces
Penetration and sleeve coordination
Civil-to-building level reconciliation
Federated model issue tracking
Civil–structure coordination

How a civil package runs

From survey control and the engineer's design through to files issued into your CDE.

Scope and standards intake

We read your EIR or BEP, template, shared parameters and naming convention, then confirm in writing what we will model, at what Level of Development, and every assumption we had to make.

Template and content check

Your template is tested before we rely on it: worksets, view templates, filters, host behaviour and schedule drivers. A fault here multiplies across every sheet, so it is cheapest to find now.

Pilot package

One representative level, zone or system is produced end to end under full production QA, so you judge the real service before committing volume.

Discipline modelling

Architectural, structural, MEP and civil elements built to the agreed LOD in your template, with the geometry and data your downstream uses actually need.

Interdisciplinary check

Models are federated and reviewed against each other as we go, so conflicts surface during production rather than at the coordination milestone.

Documentation and data

Sheets, schedules and parameter data generated from the model, named and structured to your convention.

Three-gate QA

A modeller self-check against the project checklist, an independent reviewer who did not build it, then a lead sign-off against your standards and LOD.

Delivery into your CDE

Native and exchange files issued into ACC, BIM 360 or wherever you work, purged and audited, with the QA record attached.

What you actually get

What changes when the site model is coordinated with the building rather than delivered beside 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.

Your template, not ours

We work inside your template, shared parameters, naming convention and BIM Execution Plan. Nothing comes back needing to be re-mapped to your standard.

Modelled for the use, not the picture

Elements are built to the agreed Level of Development with the data your schedules and downstream trades actually need, so the model survives past the render.

Cross-discipline checks during production

We federate and check as we go rather than waiting for the coordination milestone, so conflicts are found while they are still cheap to fix.

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

Civil 3D for surfaces, alignments, corridors and pipe networks, Revit where the site has to federate with the building models, and Navisworks for checking the two together. Deliverables come as DWG, IFC, LandXML for surfaces and alignments, and NWC for federation. The exchange format is agreed at the start rather than converted at handover.

Through shared coordinates and the project survey control, established before anything is modelled. We take the coordinate system, benchmark and rotation from your survey, apply the same base point across every discipline, then verify a known point in the federated model. Most civil-to-building conflicts turn out to be coordinate errors rather than design errors.

We model what the evidence supports: record drawings, utility surveys, GPR results and any as-built data you hold, with the source and confidence recorded per run. Where a service is undocumented we flag it as an unknown rather than draw a plausible line. Invented geometry in a utility model is worse than a documented gap.

The BIMForum LOD Specification covers site elements less fully than building elements, so we agree a written table instead of citing one number. Networks are typically modelled at LOD 300 with true inverts and sizes, structures at LOD 300 to 350, and surfaces carry a stated accuracy and data source rather than an LOD at all.

Yes, and we list what the drawings do not resolve before starting. Missing invert levels, spot heights that conflict between sheets, and tie-ins shown on one drawing and not another are raised as RFIs on paper rather than assumed in the model. That list usually shortens the review cycle more than the modelling itself does.

Your civil engineer of record. We produce modelling, coordination and documentation against their design, while hydraulic calculations, code compliance, permitting and sealing stay with them. Our review is architect-led, so interface and constructability questions come back to you, but nothing we issue carries a professional seal or replaces the engineer's judgement.

Need a site and utilities model coordinated?

Send the survey, the civil drawings and the building models, and we will scope it.