
BIM Coordination & Clash Detection
Resolve Clashes on Screen, Not on Site


We federate architectural, structural and MEP models, run clash cycles to your programme, and track every issue to closure, on projects from metro stations and airports to 2M sq ft towers.
BIM coordination brings every discipline's model into one federated model and checks them against each other before anything is built. Three kinds of clash are found, assigned, fixed and re-checked in cycles, so your site team gets a model it can build from:
-
Hard clashes: two elements in the same space, such as a duct through a beam
-
Soft clashes: missing clearance for access or maintenance
-
Workflow clashes: conflicts in sequence, delivery or trade access
Proven on Airports, Metros and Towers
Noida International Airport, with Tata Projects: BIM management covering the BEP, model audit and coordination, from preliminary design through construction.
Nagpur Metro: 3D BIM and coordination for 8 stations, including an interchange.
Sikka Associates Architects: 3D BIM, September 2017 to November 2019. "The 3D BIM work assigned to MANSYCOM was performed very professionally and satisfactorily."

What You Get

Every coordination engagement is scoped in your BIM Execution Plan and delivers a clear, auditable record of what was found, who fixed it and when. You receive:
-
Federated coordination model: all disciplines in one model (NWD/NWC, RVT, IFC)
-
Clash reports: grouped by discipline, level and zone, with viewpoints and screenshots (PDF/Excel, BCF)
-
Issue log and dashboard: open vs resolved clashes by trade, week on week, for coordination meetings
-
Coordinated discipline models: routing checked for clearance and access, to the LOD agreed in your BEP
-
Coordinated drawings: combined services drawings, sections and builder's work openings (DWG/PDF)
-
Meeting minutes and decision log: who agreed what, and when
-
RFI support: RFIs raised with model views attached
-
Sign-off package: final clash-free status per zone, ready for shop drawings or fabrication
How We Work
A clear five-step workflow, run in your common data environment. Clash cycles run weekly by default, or to your programme and meeting rhythm.
-
1. Kickoff and BEP: agree the coordinate system, LOD, clash rules and tolerances, and the meeting rhythm, with roles and the CDE set up
-
2. Model audit: check each incoming model for origin, levels, naming and completeness before any clash run
-
3. Clash cycles: run the clash matrix by zone and level, then group results and filter out false positives
-
4. Resolve and track: assign each issue to a trade, review it in the coordination meeting, and re-test after the fix
-
5. Sign-off: zone-by-zone sign-off, with drawings and the model issued for construction

Tools & Standards

We work to open standards and your project's BIM Execution Plan, so every model and report fits your existing workflow.
-
Software: Autodesk Revit and Navisworks, working in your common data environment
-
Standards: PAS 1192, COBie, IFC (ISO 16739), BIMForum LOD, and your BIM Execution Plan
-
Inputs: RVT, IFC, DWG and NWC models, or 2D drawings where no model exists
-
Outputs: NWD, RVT, IFC, BCF, DWG, PDF and XLSX
Where We Use It
Coordination pays off most where services are dense, interfaces are many and rework on site is expensive:
-
Metro and rail: station boxes, concourses and dense MEP corridors (Nagpur Metro)
-
Airports: terminals with large MEP and baggage-handling interfaces (Noida International Airport)
-
High-rise and mixed-use: towers up to 2M sq ft
-
Industrial facilities: plants and process buildings with heavy services

Ways to Work With Us

Start small and scale up. Choose the engagement that fits your project and your team:
-
Coordination-risk review: send one level or zone. We federate it, run a clash test and return a prioritised clash report.
-
Dedicated coordination team: named BIM coordinators working in your CDE and your meetings, month to month.
-
Fixed-scope project: defined zones, LOD and deliverables, priced up front.
Frequently Asked Questions
Answers to the questions project teams ask us most often:
-
When should coordination start? At design development. A clash found at DD costs a model edit; found on site, it costs rework and delay.
-
How often do you run clash cycles? Weekly by default, or to your programme and meeting rhythm.
-
Can you join our coordination meetings? Yes. We run or attend them online and keep the issue log current.
-
What if we only have 2D drawings? We model the missing disciplines from your drawings first, then coordinate.

