Alftek runs multi-discipline model federation and clash detection on Qatar construction projects — catching architectural, structural and MEP conflicts on-screen before they become rework on site. Using Navisworks, Revizto and Solibri, we deliver clear resolution reporting that keeps every discipline aligned.
Get a Free Coordination QuoteOn fast-moving Qatar projects — metro and rail, aviation, healthcare, hospitality and high-rise developments — an unresolved clash between structural, MEP and architectural elements can stall a site team for days. Coordinating disciplines in the model, before construction, is one of the highest-value BIM activities on any project.
Headquartered at Alfardan Centre on Grand Hamad Street in Doha and operating since 2018, Alftek federates discipline models and runs structured clash-detection passes using Navisworks, Revizto and Solibri, producing resolution reports that design teams and contractors can act on directly.
From model federation to a resolved, construction-ready coordinated model.
Architectural, structural and MEP models combined into a single coordinated federated model.
Explore 4D & 5D BIM in Qatar →Structured clash-detection passes in Navisworks, Revizto and Solibri, scoped by discipline and priority.
Clear, actionable clash reports the design and site team can track through to sign-off.
Underlying discipline modeling to LOD 100–500, so coordination is checking real, build-ready geometry.
Explore BIM Services →Clash detection is often described as if it were a single button press. In practice the value comes from running a disciplined, repeating cycle — and from what happens after the clash report is produced, which is where most coordination processes break down.
Before the first run, the team fixes the model exchange schedule, the shared coordinate system, discipline naming conventions and the clash matrix — which disciplines are tested against which, and at what tolerance. Skipping this stage is the single most common reason coordination produces thousands of meaningless clashes that nobody acts on.
Discipline models are combined into a single federated model at the agreed exchange point. Models are checked for correct positioning and completeness first — a discipline model delivered in the wrong coordinate system will generate a clash against nearly every element in the building and invalidate the run.
Tests are run according to the clash matrix rather than everything against everything. Hard clashes (physical intersection), clearance clashes (insufficient access or maintenance space) and workflow clashes (elements correct in space but wrong in sequence) are separated, because each needs a different kind of resolution.
Raw clash counts are close to useless. Results are de-duplicated and grouped by root cause, so that a single mis-routed duct producing forty individual clashes is presented and resolved as one issue rather than forty. This is the step that turns a report into something a design team can act on.
Each grouped issue is assigned to a responsible discipline with a due date, and tracked to closure. Issues are exported in an open, trackable format (BCF) so they can move between different software without losing their history or their screenshots.
The following cycle verifies that closed issues are genuinely resolved and have not introduced new conflicts. Coordination is iterative by nature — clash counts should fall steadily cycle over cycle, and that trend is the real measure of whether the process is working.
Treating every conflict as the same type of problem is why some coordination reports are ignored. Each category has a different cost of being missed and a different route to resolution.
| Clash type | What it is | Consequence if missed |
|---|---|---|
| Hard clash | Two elements physically occupy the same space — a duct running through a beam | Direct rework on site; the most expensive and most visible failure |
| Clearance / soft clash | Elements do not intersect but violate required access, insulation or maintenance space | Equipment installed but not maintainable; frequently discovered only at handover |
| Workflow / 4D clash | Elements are correct in space but conflict in construction sequence or access | Programme delay and trade stacking rather than physical rework |
A clash matrix is easiest to understand as a grid. Each row is a pairing of discipline models that is worth testing, and each column records how that test is set up. The example below is an illustrative starting point, not a fixed standard. The pairings, tolerances and priorities are agreed per project in the BIM Execution Plan.
| Test (model A vs model B) | Clash type | Tolerance approach | Priority |
|---|---|---|---|
| Structure vs architecture | Hard | Small tolerance, to ignore modelling overlaps at joints | High |
| Structure vs MEP (ducts, pipes, cable trays) | Hard | Zero or near-zero, since any penetration needs a coordinated opening | High |
| MEP vs MEP (between services) | Hard | Tight, set per service pairing | High |
| MEP vs ceilings and walls | Hard | Moderate, allowing for finishes and fixings | Medium |
| Plant and equipment vs access zones | Clearance / soft | Maintenance and access space modelled as a clearance volume | Medium |
| Temporary works and sequence vs permanent works | Workflow / 4D | Checked against the construction programme, not geometry alone | Project-specific |
How the matrix runs in software: in Navisworks, each row becomes a Clash Detective test between two saved selection sets. In Solibri, the same pairings are expressed as rulesets. The grouped results are then tracked as issues through to closure and exchanged in BCF. The matrix is the part that makes the software useful. Without it, the same tools simply produce a longer list.
There is no separate product called "clash matrix software". The matrix is a set of agreed tests, and each coordination platform turns those tests into something it can run. The three platforms Alftek works in do this differently, and they are strongest at different points in a project.
| Software | How the clash matrix is set up | Where it is strongest | Typical use on a project |
|---|---|---|---|
| Navisworks (Clash Detective) | Each row of the matrix becomes a clash test between two saved selection or search sets, with its own test type (hard or clearance) and tolerance. The test list can be exported and re-imported, so one project's matrix becomes the template for the next. | Large federated models from mixed formats, fine control over each test, and grouping results before they are issued | Formal coordination runs at each model exchange |
| Solibri | The pairings are written as rulesets that check components against each other. Rulesets can also check model quality, such as missing, duplicate or misplaced elements, in the same run. | Rule-based checking of IFC models, and catching model-quality problems that would otherwise create false clashes | Checking incoming models before federation, and checks against BIM Execution Plan requirements |
| Revizto | Clash tests run on the combined model and feed straight into a shared issue tracker, so clash groups can be turned into issues and assigned. | Getting issues in front of the whole team, including people who do not use desktop BIM tools, and tracking them to closure | Coordination meetings, issue assignment and follow-up between runs |
Which one should a project use? Usually more than one. A common pattern is to check incoming models in Solibri, run the matrix in Navisworks, and manage the resulting issues in Revizto. Issues move between them in BCF, so nothing is retyped and screenshots and history are kept. The software choice matters less than the matrix itself: the same tool run without an agreed matrix simply produces a longer list.
Alftek runs coordination in Navisworks, Revizto and Solibri, and matches the platform to the one your project team already uses. If your Qatar project already has a coordination setup, we work inside it rather than replacing it.
The commercial case for clash detection rests on a simple asymmetry: the cost of resolving a conflict rises sharply the later it is found. A clash resolved by moving a duct in the model costs design time. The same clash found after installation costs demolition, rework, materials, re-inspection and programme — and often triggers a variation claim.
Coordination works best when it starts early. Running the first federation at concept or early developed design — when moving a service route is still a drawing change — captures far more value than a single pre-construction check once the design is effectively fixed.
Multi-platform coordination experience paired with the underlying modeling capability to fix what clash detection finds.
Standardised, auditable information management so coordination findings are traceable end to end.
Navisworks, Revizto and Solibri coordination, matched to what your project team already uses.
The same team that finds a clash can remodel the fix — no handoff delay between detection and resolution.
Explore As-built Drawings in Qatar →Metro & rail, aviation, healthcare, hospitality, high-rise, education and infrastructure.
Clash detection is the process of overlaying architectural, structural and MEP BIM models to identify physical conflicts between building elements before construction starts, so they can be resolved on-screen instead of on site.
Yes. Alftek runs multi-discipline model federation and clash detection on Qatar projects using Navisworks, Revizto and Solibri, with resolution reporting to keep design teams aligned.
Alftek uses Navisworks, Revizto and Solibri for multi-discipline model federation, clash detection runs and resolution reporting.
A hard clash is a physical intersection — two elements occupying the same space, such as a duct passing through a beam. A soft or clearance clash is where elements do not intersect but violate a required buffer, such as insufficient maintenance access around a plant item or inadequate insulation clearance. Soft clashes are missed more often and frequently surface only at handover.
As early as models are exchangeable — typically concept or early developed design. Starting early captures far more value, because at that stage resolving a conflict is a drawing change. A single pre-construction check once the design is effectively fixed catches problems at the point where they are most expensive to fix.
Coordination is iterative rather than one-off. Cycles are usually tied to the model exchange schedule agreed in the BIM Execution Plan, commonly fortnightly or monthly during active design. What matters more than the interval is that clash counts fall steadily cycle over cycle — that trend is the real indicator the process is working.
A clash matrix defines which discipline models are tested against which, and at what tolerance. Without one, tests run everything against everything and generate thousands of results nobody acts on. The matrix is agreed at the start of the project as part of the coordination framework.
The matrix is a set of agreed tests rather than a separate product. In Navisworks each pairing becomes a Clash Detective test between two saved selection sets, and in Solibri the pairings are expressed as rulesets. Alftek runs these tests in Navisworks, Revizto and Solibri, and exchanges the resulting issues in BCF format.
They do different jobs, so most projects use both. Navisworks Clash Detective is built for running the clash matrix on large federated models, test by test, with a tolerance per test. Solibri checks IFC models against rulesets, which also catches model-quality problems such as duplicate or misplaced elements. Revizto is often added to track the resulting issues across the team. Alftek works in all three.
A grouped and filtered issue report rather than a raw clash count — de-duplicated and organised by root cause, with each issue assigned to a responsible discipline and a due date. Issues are exported in BCF format so they can move between different software without losing history or screenshots, alongside the federated model itself.
Alftek is headquartered at Alfardan Centre, 2nd Floor, Grand Hamad Street, Doha, Qatar, and delivers BIM services nationwide including Doha, Lusail, Al Khor and Al Wakrah.
Talk to Alftek's Doha-based BIM team about federating and coordinating your project models. Get a free consultation and a tailored scope and quote.
Request a Free Quote