How to Use Navisworks for Clash Detection: A BIM Master Guide
Anyone can press Run All and produce a report with 3,000 clashes on it. That report is not coordination, it is raw material, and handing it to a design team achieves nothing. The skill this guide teaches is the part that comes after: turning thousands of geometric intersections into a short, grouped, assigned list that people can actually act on.
Clash detection in Navisworks is the automated process of finding physical and clearance conflicts between discipline models combined into one federated model. It runs in the Clash Detective module, which is available in Navisworks Manage only and not in Simulate or Freedom. The workflow has four phases: export each discipline to NWC and federate; build discipline selection sets and rules; configure one test per discipline pair with the right clash type and tolerance; then run, group, assign and report, usually as BCF so issues round-trip back into Revit or Autodesk Construction Cloud. Navisworks finds clashes but cannot fix them, because geometry is corrected in the authoring tool and the test is then re-run.
Clash Detective isolating a single hard clash: duct through beam. The panel on the left is the deliverable people argue about; the viewpoint on the right is what actually gets it fixed. [REPLACE with your own screenshot from a project or training file.]
- TL;DR
- What is clash detection in BIM?
- Navisworks Manage vs Simulate for clash detection
- Hard, soft and workflow clashes
- The four-phase workflow
- Phase 1: the federated model, NWC vs NWD
- Phase 2: selection sets and rules
- Phase 3: the discipline test matrix
- Phase 4: run, triage and assign
- The clash triage problem
- How to create a clash report
- Top causes of clashes on Indian projects
- Best practices
- The Gulf BIM coordinator market
- Glossary
- FAQs
- Sources
TL;DR
Key takeaways
- Clash detection finds conflicts between discipline models before construction, in a federated model that combines architecture, structure and MEP.
- Clash Detective exists only in Navisworks Manage. Simulate has federation and 4D TimeLiner but no clash detection at all, and Freedom is a viewer.
- Three clash types: hard (physical overlap), soft or clearance (violates a required access zone), and workflow or 4D (two trades needing the same space at the same time, which geometry alone cannot find).
- Four phases: federate with NWC → build selection sets and rules → configure one test per discipline pair → run, group, assign and report.
- Use NWC, not NWD, for live coordination. NWC refreshes when the source model changes; NWD is a fixed snapshot for issuing.
- A raw clash count is not a deliverable. Reducing thousands of intersections to a prioritised, grouped, assigned list is the entire job.
- Navisworks cannot fix a clash. Geometry is corrected in Revit, the NWC is refreshed, and the test is re-run to confirm.
- Export issues as BCF when they need action, because BCF carries the viewpoint and status back into Revit or Autodesk Construction Cloud. HTML is for human-readable summary reporting.
What Is Clash Detection in BIM?
Clash detection is the automated process of identifying physical or logical conflicts between building elements in a federated BIM model, before construction begins. Separate discipline models are combined into a single view, and software compares selected sets of geometry to find where they interfere. For foundational context on how the model is built before coordination begins, see our guide on what is BIM.
Detection is not coordination
These two words are used interchangeably and should not be. Detection finds the problem. Coordination resolves it. Detection is an automated process that takes minutes; coordination is a human process involving several disciplines, competing priorities, design intent and often commercial consequences, and it takes weeks. A great many "BIM coordinators" are in practice clash detectors: they run the test, export the report and move on. The value sits in the second half, in chairing the coordination meeting, deciding which service moves, and holding the resolution to a close-out.
The cost argument, stated honestly
Published estimates of construction rework generally put it at around 5% of contract value, with ranges cited from roughly 5% to 12%, and a meaningful share of that traces to coordination failures that clash detection can catch. You will also see much higher figures quoted, up to 30%, from broader studies of construction inefficiency that include many causes beyond coordination.
Be careful with these numbers in a client conversation. The honest claim is that clash detection addresses one specific and well-evidenced slice of rework: spatial conflicts between disciplines. It does not address material waste, workmanship defects, late design changes or scope creep. Overstating it invites a procurement manager to test the claim, and the arithmetic will not survive.
Navisworks Manage vs Simulate for Clash Detection
If your role involves clash detection, you need Navisworks Manage. Simulate cannot run clash detection at all. This is the single most common purchasing mistake made by teams new to coordination.
| Capability | Freedom | Simulate | Manage |
|---|---|---|---|
| Cost | Free | Paid subscription | Paid, higher tier |
| View published NWD | Yes | Yes | Yes |
| Create a federated model | No | Yes | Yes |
| Markup, viewpoints, sectioning | View only | Yes | Yes |
| TimeLiner 4D simulation | Playback only | Yes | Yes |
| Quantification | No | Yes | Yes |
| Clash Detective | No | No | Yes |
| Clash management and reporting | No | No | Yes |
| For a BIM Coordinator role, Manage is the minimum viable version. Simulate is a review and simulation tool, not a coordination tool. | |||
Licensing note for Indian firms
Both Simulate and Manage are available as standalone subscriptions or within the Autodesk AEC Collection, which is how most Indian firms actually hold them, since the Collection also carries Revit and Civil 3D. Simulate typically costs materially less than Manage, which is exactly why it gets bought by mistake by teams who assume clash detection is included. Autodesk changes pricing and packaging periodically, so verify current terms on Autodesk's own product comparison before purchasing, rather than relying on any third-party figure including this article's.
Master Navisworks & BIM Coordination
Learn Revit MEP modeling, clash detection setup, discipline matrix, BCF reporting, and full coordination workflows — structured for India and GCC BIM roles.
Hard, Soft and Workflow Clashes
Three categories, and they are found in different ways and resolved by different people.
| Type | Definition | Example | Resolution approach |
|---|---|---|---|
| Hard | Two elements physically occupy the same space | An HVAC duct passing through a structural beam | Non-negotiable. Reroute the service, or if unavoidable, formally request a structural penetration and have it engineered |
| Soft / clearance | Elements do not touch but one violates a required clearance zone | A cable tray placed too close to a fan coil unit valve set to allow it to be operated | Depends on an agreed tolerance. Move the offending service or formally accept the reduced clearance in writing |
| Workflow / 4D | Two trades need the same space at the same time | Ceiling grid installation scheduled while MEP first fix is still live in the same zone | Not a geometry problem. Requires 4D sequencing to detect and a programme change to resolve |
| Duplicates | The same element modelled twice, often across files | A wall modelled by both the architect and the structural engineer | Model hygiene, not coordination. Resolve at source and exclude from live tests |
Why soft clashes cause more argument than hard ones
A hard clash is not debatable. The duct is inside the beam, and the building cannot be built. A soft clash depends entirely on a number that a human chose, and the moment a discipline lead is asked to move an installed-cost service because of a 50 mm clearance rule, the first question will be "who decided 50 mm and why?". If the answer is "it was the default", you lose the argument. Record the basis of every clearance tolerance in the BIM Execution Plan: maintenance access, code requirement, insulation thickness, or a client standard. A clearance you can justify is a coordination instruction. A clearance you cannot is an opinion.
The Four-Phase Clash Detection Workflow
Clash detection in Navisworks runs in four phases: federate the discipline models, define selection sets and rules, configure a test matrix of discipline pairs, then run, triage and assign the results. Each phase depends on the one before it, and skipping the second is why most first attempts return an unusable number of clashes.
New to Navisworks? A Beginner's Clash Detection Tutorial in Four Sentences
Start here if this is your first clash test
In plain language, before the detail. Phase 1: collect everyone's models into one file so they can be seen together. Phase 2: tell the software which elements belong to which discipline, so you can test one trade against another instead of everything against everything. Phase 3: set up the individual tests and tell each one how close is too close. Phase 4: run the tests, tidy the results into a short list, and send each item to the person who has to fix it. That is the whole process. Everything below is detail on those four steps.
Phase 1: Preparing the Federated Model (NWC vs NWD)
Use NWC for live coordination and NWD only for issuing a fixed snapshot. Getting this the wrong way round is the most common setup error, and it fails silently. If you haven't set up the tool yet, see our guide on how to install Navisworks before starting this phase.
The third format, and the one you actually work in
NWC and NWD get all the attention, but the file you have open while coordinating is usually neither. NWF is the working coordination file. It references the linked NWC files rather than embedding geometry, and it stores your coordination data: the clash tests themselves, search sets, viewpoints and TimeLiner schedules. That is why an NWF is small and why it is useless without the NWC files it points at. The practical rule: federate and save as NWF, keep the NWCs alongside it, and publish to NWD only when issuing. Losing the NWF means losing every clash test you set up, which is a genuinely painful way to learn the distinction.
The failure this causes
Federate from NWD files and your coordination model stops updating without telling you. The structural engineer moves a beam on Monday, you run tests on Wednesday against last month's geometry, and you issue a report full of clashes that no longer exist and missing the ones that now do. Nobody gets an error message. The first sign is a coordination meeting where the design team says "we fixed that three weeks ago", and your credibility takes the hit.
Model organisation before you federate
- Agree file naming first. Follow the ISO 19650 naming convention, or whatever the project's BIM Execution Plan specifies. On multi-party Indian and joint-venture projects with several subconsultants, a federated model assembled from inconsistently named files becomes unmanageable within two coordination cycles.
- Confirm a shared origin. Every discipline must publish to the same project base point and survey point. Models federating with an offset are the second most common setup failure, and they produce either zero clashes or an unusable number.
- Check units and levels. Level naming should match across disciplines, because you will group clashes by level later and mismatched names make that impossible.
- Verify parameters survived export. Open a few elements and confirm the properties you plan to build search sets on actually came across from Revit.
Phase 2: Selection Sets and Rules
Build search sets, not selection sets, wherever possible. The distinction matters more than it sounds.
- A selection set is a saved list of specific objects. Refresh the model with new geometry and the set does not include it.
- A search set is a saved rule, for example Category = Ducts AND Level = L03. Refresh the model and it automatically picks up everything that now matches, including elements added since.
On a live project where models update weekly, search sets are the difference between a coordination model that maintains itself and one you rebuild every cycle. Create one per discipline at minimum: Architecture, Structure, Mechanical, Electrical, Plumbing and Fire Protection.
Rules: suppressing what you do not want to see
Clash Detective's Rules tab exists to remove intersections that are expected and are not coordination issues. The standard ones suppress clashes between items in the same layer, the same group or block, or the same file. Beyond the defaults, add project-specific rules for known expected conditions: fixings passing through the elements they fix, services passing through the builder's work openings created for them, and elements deliberately embedded in others. Every rule you add should be documented, because a rule that hides a real problem is worse than no rule at all, and six months later nobody will remember why the filter is there.
Phase 3: The Discipline Test Matrix
Never run one test between two whole models. Create a separate test for each discipline pair. This is what makes results assignable, because a clash in the "Mechanical vs Structure" test already tells you who needs to be in the room.
Click any cell to see what that test catches, its priority, and the settings it normally uses.
| Priority | Test (Selection A vs B) | Clash type | Tolerance | Why it ranks here |
|---|---|---|---|---|
| P1 | Mechanical vs Structure | Hard | 0 to 10 mm | Highest volume and least negotiable. Ducts are the largest services and structure cannot move |
| P1 | Plumbing vs Structure | Hard | 0 to 10 mm | Drainage runs to gradient and often cannot reroute, so penetrations must be engineered early |
| P1 | Plumbing vs Mechanical | Hard + Clearance | 25 to 50 mm | Both large, both constrained, competing for the same congested plenum |
| P1 | Fire Protection vs Mechanical | Hard + Clearance | 25 to 50 mm | Sprinkler heads must reach approved positions; a duct can compromise coverage, not just fit |
| P2 | Electrical vs Structure | Hard | 0 to 10 mm | Containment is the most flexible service, so more rerouting options exist |
| P2 | Fire Protection vs Structure | Hard | 0 to 10 mm | Rises in priority where sprinkler coverage is being demonstrated to an authority |
| P2 | Mechanical vs Architecture | Hard + Clearance | 25 mm | Tests whether services actually fit the drawn ceiling void |
| P2 | Electrical vs Mechanical | Clearance | 25 to 50 mm | Rarely intersect outright, frequently too close to install or maintain |
| P2 | Plumbing vs Electrical | Clearance | 50 mm+ | Safety dimension: water above electrical equipment is prohibited by many client standards |
| P3 | Architecture vs Structure | Hard | 10 mm | Usually well coordinated early, but slab openings versus risers matter |
| P3 | Electrical vs Architecture | Hard | 10 mm | Run before ceiling and drywall packages are released |
| P3 | Plumbing vs Architecture | Hard | 10 mm | Check risers against shaft sizes |
| P3 | Fire Protection vs Architecture | Hard | 10 mm | Confirm heads land in the ceiling grid, not on tile joints |
| P3 | Fire Protection vs Electrical | Clearance | 25 mm | Low volume, but keep separate so results stay assignable |
| P3 | Fire Protection vs Plumbing | Hard + Clearance | 25 mm | Low volume, high genuineness: both systems have limited flexibility |
| Fifteen tests, not one. Each is assignable to a discipline pair the moment it returns a result. | ||||
Read the matrix as a running order, not just a list
The colours are a sequence. Run every P1 test first, resolve those, and only then move to P2. The reason is that resolving a P1 clash frequently creates or removes P2 and P3 clashes: move a duct out of a beam and it may now conflict with a cable tray that was previously fine. Working in priority order means you resolve each conflict once. Working through a single undifferentiated list means resolving the same zone three times, and this is the most common reason coordination cycles overrun.
Phase 4: Run, Triage and Assign
Running the tests takes one click. Everything that gives the output value happens after it.
Clash statuses, and what they actually mean
| Status | Meaning | Who sets it |
|---|---|---|
| New | Found in this run and not present in the previous run | Set automatically |
| Active | Found in this run and also present previously. Still unresolved | Set automatically |
| Reviewed | A human has looked at it and confirmed it is a genuine issue to be actioned | The coordinator |
| Approved | Examined and accepted as acceptable, so it will not be actioned | Discipline lead or coordinator, with a recorded reason |
| Resolved | Was present previously and is not found in this run | Set automatically after re-run |
The status that gets abused
"Approved" means "we have decided not to fix this, and here is why." It does not mean "we do not want to look at it." On projects under schedule pressure, Approved becomes a bin for anything inconvenient, and because the status suppresses the clash from future reports, the problem disappears from view without disappearing from the building. Every Approved clash needs a written comment giving the reason and the person who accepted it. If your project has a large Approved count with no comments, you do not have a coordinated model, you have a quiet one.
Assignment conventions on Gulf projects
On UAE, Qatar and Saudi projects, coordination reporting is usually more formalised than on typical Indian domestic work, and knowing the conventions matters if you are targeting those roles:
- A fixed coordination cycle written into the BEP, commonly weekly or fortnightly, with model upload deadlines that are enforced rather than aspirational.
- Issues raised in the common data environment, usually Autodesk Construction Cloud, BIM 360 or Aconex, rather than circulated by email. The clash report is the input; the CDE issue is the record.
- Named responsible parties per issue, not "MEP contractor". Gulf consultants generally expect a named individual and a due date against each clash group.
- Close-out evidence. A clash is not closed because someone said it was fixed; it is closed when a re-run shows it Resolved and the viewpoint confirms it. Many clients require the before-and-after viewpoint pair.
- ISO 19650 information management as the framing standard, with the EIR defining what coordination deliverables are due and when.
The Clash Triage Problem
This is the section most guides skip, and it is the one that separates a coordinator from a button-presser.
A first run on a single commercial floor routinely returns several thousand clashes. That number is meaningless. Below is what happens to it when it is processed properly.
all pairs, default settings
same-file, same-group filters
model hygiene, not coordination
clearances set to real needs
by level, zone and grid
what the team receives
Illustrative figures showing the shape of a triage process, not measured project data. Actual reduction ratios vary widely with model quality, discipline count and how well rules were set up beforehand.
Why grouping produces the biggest reduction
The largest single drop above comes from grouping, and the reason is that clashes are not independent events. A single duct running the wrong side of a beam line generates a clash at every beam it crosses, so one design decision appears as forty separate rows. Clash Detective can group by level, grid intersection, or the clashing item itself, and a well-grouped report says "this duct run on Level 3, grid C to F, conflicts with the beam line, please reroute below" rather than listing forty coordinates. The engineer receiving the second version can act on it in ten minutes. The first version gets ignored, and reasonably so.
How to Create a Clash Report in Navisworks
Triage and group the clashes first, then open the Report tab in Clash Detective, choose the fields and statuses to include, pick a format, and write the report. Format choice matters more than most people expect: BCF for anything requiring action, HTML for a readable summary. The mechanics, then the choice of format.
- Triage first. Group your clashes and set statuses before exporting. Exporting a raw list wastes everyone's time, including yours.
- Open the Report tab in Clash Detective, with the relevant test selected.
- Choose contents. Tick the fields to include: clash name, status, distance, grid location, date found, assigned to, and comments. Include the grid location, because without it the recipient cannot find the clash in the building.
- Choose which clashes. Filter by status so you export only what needs action, typically New and Active, rather than everything including Approved and Resolved.
- Choose the format. HTML (Tabular) for a readable summary, XML for data exchange, and BCF for anything requiring action.
- Write Report and save with a name that carries the project, discipline pair, and date, for example PRJ-C2_MEC-vs-STR_2026-08-01. Report files with names like "clash report final v2" become unusable within a month.
- Distribute through the CDE, not by email, so the issue history stays attached to the project record.
| Format | Contains | Use it when |
|---|---|---|
| HTML (Tabular) | Readable table with embedded viewpoint images | Summary reporting to a client or for a coordination meeting pack |
| XML | Structured clash data without images | Feeding another system or building your own tracking spreadsheet |
| BCF | Issue, status, comments, responsible party and a saved camera viewpoint | Anything that needs someone to act. The open standard for round-tripping issues |
| Text | Plain list | Rarely. Quick internal checks only |
BCF into BIM 360 and Autodesk Construction Cloud
This is the workflow step that makes clash detection stick. A BCF file carries the issue and the camera position, not the geometry, so it is small and it opens the model exactly where the problem is. Export BCF from Clash Detective, then import it into Autodesk Construction Cloud or BIM 360 as issues, where each becomes a tracked item with an owner, a due date and a status visible to the whole project. From there the responsible engineer can open the issue in Revit through a BCF plugin and land directly on the offending element rather than searching for it from a written description. That difference, between "duct clashes with beam near grid D4" and a click that puts the camera on the exact duct, is most of why coordination issues get closed on time.
Navisworks Clash Detection on Indian Projects: The Four Root Causes
Running Navisworks clash detection on Indian projects surfaces the same four root causes repeatedly, and three of the four are process failures rather than modelling failures.
- MEP versus structure in a tight ceiling void. The dominant cause on Indian commercial work. Ducts, drainage, cable tray and sprinkler mains all compete for the plenum, and where floor-to-floor height has been optimised for saleable area the void left for services is genuinely marginal. Coordinate the services zone at design stage rather than discovering it at clash stage, because by then the structural grid is fixed and only the services can move. Our duct design guide covers the depth implications in detail.
- Late model uploads. Teams working in silos and uploading close to the coordination meeting, so the federated model is assembled from mismatched vintages. Fix: a BEP-mandated upload deadline with a stated consequence, typically that a discipline missing the deadline is coordinated against its previous model and owns whatever that produces.
- Models below LOD 300. Clash detection against generic placeholder geometry produces confidently wrong results. Hard clashes may be roughly right; soft clashes are meaningless, because the clearance is being measured to an object that is not the real size. Set LOD 300 as the entry requirement for coordination.
- Poor naming and no shared origin. Unstructured file naming makes a federated model unmanageable, and a discipline published to a different origin makes it useless. Both are one-line entries in the BEP that prevent days of rework, and both are routinely skipped.
Clash Detection Best Practices
Seven habits separate a coordination process that closes issues from one that generates reports: schedule it in the BEP, work in priority order, justify every tolerance, group before reporting, re-run after every model update, archive a dated NWD each cycle, and comment every Approved clash.
- Schedule it in the BEP, never run it ad hoc. Coordination on a fixed cycle with fixed upload deadlines. Ad hoc clash detection produces ad hoc coordination.
- Work in priority order. MEP versus structure first, then MEP versus MEP, then architecture. Resolving high-priority clashes changes the low-priority ones, so doing it the other way round means doing it twice.
- Justify every tolerance. Record in the BEP why each clearance value is what it is, whether that is maintenance access, insulation thickness, a code requirement or a client standard. A tolerance you can defend survives the coordination meeting.
- Group before you report, always. Never issue an ungrouped list. Group by level, zone or grid so each entry is one decision rather than one intersection.
- Re-run everything after every model update. Resolved clashes reappear. A beam moves in week 4 and reintroduces a conflict closed in week 3, and nothing warns you except a re-run.
- Save a dated NWD at each cycle close. This is your coordination audit trail. When someone asks in month nine what was resolved and when, the dated snapshots answer it.
- Comment every Approved clash. No reason recorded, no approval.
Clash Detection and the Gulf BIM Coordinator Market
The skill gap is specific and it is why this role pays. A large number of Indian AEC graduates can model competently in Revit. Far fewer can set up a discipline test matrix, defend a tolerance, triage three thousand clashes into sixty actions, and run a coordination meeting to close-out. The first is a software skill; the second is a professional one.
That gap is most visible in the Gulf, where UAE, Qatar and Saudi projects run formal ISO 19650 information management and expect coordination deliverables on a contractual cycle. Roles are advertised on NaukriGulf, Bayt, GulfTalent and LinkedIn, and a large share of Gulf hiring of Indian candidates happens through recruitment consultancies handling overseas packages for Indian contractors and through the regional offices of international consultancies.
Published averages for BIM Coordinator roles in the UAE cluster broadly around AED 220,000 to 307,000 per year depending on the survey, roughly AED 18,000 to 25,000 per month, with entry into the market often below the average. Packages usually include accommodation, transport and annual flights, so compare total packages rather than basic salary.
We cover the career path, salary bands and job channels in more depth in our guide to BIM job roles explained from modeler to manager.
Glossary
- Clash detection
- The automated process of identifying physical or logical conflicts between elements from different discipline models in a federated BIM model, before construction begins.
- Hard clash
- A conflict where two elements physically occupy the same space, such as a duct passing through a structural beam. Non-negotiable.
- Soft clash (clearance clash)
- A conflict where elements do not intersect but one violates a clearance zone required by another, such as insufficient maintenance access around a valve. Depends on a defined tolerance.
- Workflow clash (4D clash)
- A scheduling conflict where two trades need the same space at the same time. Requires a 4D model to detect, because geometry alone cannot see it.
- Federated model
- A single combined view assembled from separate discipline models that remain individually owned and authored. The basis for coordination.
- NWC
- Navisworks cache file, exported from an authoring tool. Refreshes automatically when the source changes, which makes it the correct format for live coordination.
- NWD
- Published Navisworks file holding geometry and review data as a fixed snapshot. For issuing and archiving, not for live coordination.
- NWF
- The working coordination file. References linked NWC files rather than embedding geometry, and stores the clash tests, search sets, viewpoints and TimeLiner schedules. This is the file you save while coordinating.
- BCF
- BIM Collaboration Format. An open format carrying an issue, its status, comments and a saved viewpoint, allowing clash issues to round-trip between Navisworks, Revit and a common data environment.
- Search set
- A saved rule-based selection defined by properties rather than by picking objects, so it updates automatically when the model refreshes. Preferred over a static selection set.
- Clash grouping
- Combining related clashes into a single actionable issue, usually by level, grid or clashing item, so one design decision appears once rather than forty times.
Frequently Asked Questions
Sources
- Autodesk Navisworks product comparison, autodesk.com, for the feature differences between Navisworks Manage and Simulate, including the availability of Clash Detective. Verify current pricing and packaging directly, as Autodesk changes these periodically.
- Autodesk Navisworks documentation for Clash Detective configuration, rules, clash grouping, status values and report formats.
- buildingSMART International, BIM Collaboration Format and its technical documentation, for the BCF open standard. BCF transfers XML-formatted issue data referencing a view captured as an image plus model element identifiers, which is why the file is small and the viewpoint reopens exactly on the problem.
- ISO 19650 series for information management, naming conventions, EIR and BEP concepts referenced throughout.
- Published research and industry analysis on construction rework, which places rework commonly at around 5% of contract value with cited ranges of roughly 5 to 12%. Higher figures exist in broader studies of construction inefficiency that include causes beyond coordination, and should not be attributed to clash detection alone.
Basis of the figures in this article
The discipline test matrix priorities and tolerance ranges are typical practice on commercial projects, not a standard. Priorities shift with project type: on a hospital, medical gas and fire protection rise sharply; on a data centre, electrical containment dominates. Set your matrix from the project's own risk profile and record it in the BEP. The clash triage funnel figures are illustrative, chosen to show the shape of a triage process; real reduction ratios vary widely with model quality, discipline count and how well rules were configured beforehand. Salary figures are indicative published ranges and vary by employer, city and experience. Software capabilities and packaging change between releases, so verify against Autodesk's current documentation before making a purchasing decision.
This article was last reviewed on 1 August 2026.
Ready to Start Your HVAC Engineering Career Journey?
Investing in structured training is one of the best ways to set yourself apart in MEP engineering. Our MEP Design and Drafting Course offers comprehensive instruction in HVAC, electrical, and plumbing design—key skills every MEP engineer needs to excel.
Master tools like HAP software and build expertise that sets you apart in the competitive engineering landscape.