+91 98765 43210 | info@asav.com | Mon – Sat, 09:00 – 19:00 IST
Noida, Uttar Pradesh 201301
  1. Home
  2. Services
  3. CAD Engineering
  4. BIM
CAD Engineering

BIM

Revit modelling, clash coordination and federated model management from LOD 200 to LOD 400.

BIM — representative deliverable
Overview

BIM

BIM goes wrong in predictable ways. Models get built to a geometric standard but with no usable data, so schedules are worthless. Or every discipline models to its own origin and federation becomes a week of alignment work. Or clashes get reported in the thousands with no filtering, which is the same as not reporting them.

We model to a defined execution plan — shared coordinates, agreed levels and grids, worksets, naming, and a parameter schedule that actually populates the data you intend to extract. Clash detection is run with rule sets that suppress noise and surface the clashes that need a decision, each one assigned and tracked to closure.

Whether you need one discipline modelled from consultant drawings, a scan-to-BIM existing-conditions model, or ongoing federated coordination across a live project, the standard is the same: a model your team can query, not just look at.

What you receive

Every item below is issued in your own template, with your layer conventions, title block and revision scheme.

  • Discipline models — architectural, structural, MEP — to the agreed LOD
  • Shared coordinate setup, levels, grids and workset structure
  • Parameter schedule populated for your intended data extraction
  • Family creation and parametric content library
  • Sheet set and view production from the model
  • Quantity and material schedules extracted from model data
  • Navisworks federated model with rule-based clash detection
  • Clash report with assignment, status and closure tracking
  • 4D sequencing linkage where a programme is supplied
  • IFC export validated against your exchange requirements

Production detail

Key production parameters for BIM
Typical turnaround2–8 weeks by building size and LOD
LOD rangeLOD 200 / 300 / 350 / 400
StandardsISO 19650, BS 1192, your BEP; COBie on request
DeliverablesRVT, NWD / NWF, IFC 2x3 and IFC4, PDF sheet sets
Clash workflowRule-based grouping with assignment and closure tracking
Scan-to-BIM inputE57, RCP / RCS, LAS, structured or unstructured scans
RevisionsTwo rounds included per milestone

Software and formats

We work in your toolchain. If something you use is not listed, ask — the list below is only what we use most.

RevitNavisworks ManageAutoCADRecapCycloneDynamoSolibriBIM 360 / ACCTekla Structures

Frequently asked

Yes — scan-to-BIM is a large part of this practice. We register or ingest your registered cloud, model to the agreed LOD and report deviation between model and cloud, which matters for existing structures where nothing is truly plumb or level.

Yes where the project requires it, including the naming, container and status conventions. Where a client has their own BEP we work to that instead. If neither exists we will propose a lightweight one rather than improvising.

By configuring rule sets and tolerances so self-clashes, insulation intersections and known-acceptable conditions are filtered out, then grouping the remainder by cause rather than listing them individually. A report with sixty real issues gets resolved; one with four thousand gets ignored.

Yes — parametric families with the parameter structure and naming your library uses, tested across the type ranges you need. Several clients have had us rebuild an inherited library that was slowing their models down.

Only if the parameters are planned before modelling starts, which is why we agree the parameter schedule up front. Data added retroactively to a finished model is where most unreliable schedules come from.
Step 3 of 4 in CAD Engineering

Send one bim job and see how we work

Scope, price and programme come back in writing before anything starts. Most first projects are a single deliverable so you can judge us on output, not on a pitch.

Call an engineer