Ostacolo - Clash Detection & Tracking
Win64, EnglishGeneral Usage Instructions
1. Launch Autodesk Revit and open a project.
2. Navigate to the Add-Ins tab in the Revit ribbon and locate the Ostacolo panel. The panel contains four main buttons and a slide-out utility button.
3. Before running detection for the first time, expand the slide-out by clicking the small arrow at the bottom of the Ostacolo panel, then click File Config. Enter a Project name that groups all buildings in the same scheme (for example, "Tower Complex A") and a Building name that identifies this specific Revit model — this defaults to the document title. Click Save.
4. Click the Find Clashes button to open the clash detection setup form.
5. Select a detection protocol from the available options:
— Structural vs MEP: detects clashes between structural framing, columns, and foundations against pipes, ducts, conduit, cable tray, and MEP equipment.
— Architecture RC vs Structural & MEP: checks roofs, floors, and ceilings against structural and MEP elements.
— Architecture WD vs Structural & MEP: checks windows and doors against structural and MEP elements.
— MEP Internal: checks MEP distribution elements against each other.
— All: runs all protocols in sequence.
6. Select the detection mode. Hard Clash detects physical intersections between element solids. Clearance detects elements that come within a specified minimum distance (enter the distance in millimetres).
7. Click Run. OSTACOLO will extract elements from the active model and all loaded Revit link instances, run geometry intersection checks, and place a Clash Sphere family instance at each detected intersection point. A summary dialog confirms the number of clashes found and how many are new.
8. Click View Clashes to open the clash dashboard. The dashboard lists all detected clashes with their ID, status, workflow, detection date, and element information.
9. Use the filter controls to narrow the list by status (Open, In Progress, Closed, Ignored), workflow, or building.
10. Click the Navigate button on any clash row to fly the active 3D view to that clash location in the model.
11. To update a clash, select it in the dashboard, change the status using the dropdown, add a description note if needed, and save.
12. To run detection again after a model update, click Find Clashes and run the same protocol. Existing clashes with assigned statuses are preserved — only new clashes are added.
13. To share clash data or sync status updates made outside Revit, click JSON Manager. Select Update JSON from Model to push current model data to the project JSON file. Select Update Model from JSON to pull status changes from an updated JSON file back into the model without overwriting detection records.
14. To review clashes across multiple buildings in the same project, click Review Clashes. This opens the cross-building Clash Reviewer, which aggregates records from all buildings sharing the same Project name set in File Config.
Notes:
• File Config must be completed on every new model before running detection. Detection results will not be stored if the project/building mapping is missing.
• Keep the Project name identical across all building models in the same scheme so the Clash Reviewer can aggregate them.
• Close Revit before running the installer when updating to a new version.
• The Clash Sphere Revit family is loaded automatically on the first detection run. No manual family loading is required.
• Running Find Clashes on a model with existing clash records does not delete those records. Only new clashes are added; existing clashes retain their current status.
Commands
| Ribbon/Toolbar Icon | Command | Command Description |
|---|---|---|
|
Find Clashes |
Runs a geometry intersection analysis across the active model and all linked Revit files. Before the analysis begins, a setup dialog lets the user choose: One or more clash protocols — predefined category pairings: All Structural vs MEP (Pipes, Ducts, Conduit, Cable Trays) Architecture RC vs Structural + MEP Architecture WD (Windows & Doors) vs Structural + MEP MEP Internal Which linked documents to include in the check The engine uses an octree spatial index to efficiently compute intersections. For each new clash found it places a Clash Sphere family instance at the intersection point in the model, sets its radius and label, pins it, and stores all clash metadata in Extensible Storage. Duplicate clashes (same element IDs already recorded) are automatically skipped. The run produces a diagnostic log of what was found, placed, and skipped per protocol. If the project has not been configured yet it redirects to Settings first. |
|
View Clashes |
Opens a persistent modeless dashboard listing every clash recorded in the model. The panel stays open while the user works in Revit. Features: DataGrid showing all clashes with ID, description, status, workflow, and creator Status filter (All / Open / Closed) to narrow the list Live counters — total, open, and closed clash counts Section Box — crops the 3D view to the selected clash location for precise inspection Isolate — isolates the clashing elements in the view Reset — clears the active crop and isolation Resolve / Reopen — changes the clash status directly from the dashboard Delete / Merge / Solve — management actions wired to ExternalEvents so they execute safely within Revit's transaction model Cross-references the historical JSON file to align model state with the stored record |
|
Review Clashes |
Opens a graphical reporting panel that renders a visual summary of all clashes read from the JSON data file. It organises clashes by: Project and Building (selected via dropdowns at the top) Category charts — colour-coded breakdown by clash category rendered as bitmaps Circle diagrams — each clash shown as a circle sized by count or severity Date timelines — creation and closure date distributions Clicking a category or circle in the rendered charts navigates Revit to the corresponding clash sphere in the model via an ExternalEvent. It is designed for protocol review meetings — giving a quick visual status of what is open, resolved, and when clashes were created and closed across the entire project. |
|
JSON Manager |
Opens a bidirectional sync dialog between the JSON clash data file on disk and the Extensible Storage embedded in the Revit model. Two operations: Update Model from JSON — pulls status changes written externally (e.g., by a coordinator editing the JSON) into the model's Extensible Storage. Treats Closed in JSON as the authoritative truth to prevent reopening clashes that have already been resolved. Update JSON from Model — pushes the current Extensible Storage state out to the project JSON file, making the file reflect what is in the model. A log panel shows what was synced, updated, or skipped for each operation. Requires the project to be configured (redirects to Settings if not). Safe to run multiple times — changes are only written when the data actually differs. |
Installation/Uninstallation
The installer that ran when you downloaded this app/plug-in from the Autodesk App Store will start installing the app/plug-in. Simply double-click the downloaded installer to install the app/plugin. Make sure that Autodesk Revit is completely closed when running the installer.
To uninstall this plug-in, exit Autodesk Revit if currently running, then rerun the installer and select the "Uninstall" button. Alternatively, go to Control Panel > Programs > Programs and Features (Windows 10/11) and uninstall as you would any other application.
Additional Information
The Clash detection tool is a sample development to display Avant Leap's capabilities to develop cutting-edge workflows and automation for BIM project management. As we receive increasing user consumption of this tool or particular development solicitudes we'll extend and empower its capabilities.
Here is the Quick Guide: Quick Guide Clash Detection | Avant Leap
Known Issues
No known critical issues in this version.
Detection on very large models with many linked files may take several minutes depending on available system memory and the number of elements in the selected categories. Using a specific protocol (e.g., Structural vs MEP) rather than All will reduce run time significantly.
If you encounter any issues, please contact us at
info@avantleap.com
Contact
Author/Company Information
Support Information
For support, questions, or feedback, please contact us at:
Email: info@avantleap.com
Website: www.avantleap.com
Quick Guide: www.avantleap.com/quickguide-ostacolo
We aim to respond to all support requests within 2 business days.
Version History
| Version Number | Version Description |
|---|---|
|
2.0.0 |
Initial release of OSTACOLO. Includes five clash detection protocols (Structural vs MEP, Architecture RC vs Structural & MEP, Architecture WD vs Structural & MEP, MEP Internal, All), Hard Clash and Clearance detection modes, visual Clash Sphere markers, dual Extensible Storage and JSON persistence, four-status tracking workflow, cross-building Clash Reviewer, and JSON Manager sync. Supports Revit 2021 through 2026 in a single installer. The second component is a dynamic database that records the clash data in .json files located in a folder generated automatically for each project analyzed by the tool. The third component is a Clash Sphere Revit Family that will be loaded and placed over each clash detected in the model. |
|
1.0.4 |
This version of the AvantLeap Clash Detection Tools consists of three main components. The first is a toolbar with 5 Buttons that run the following commands: Find Clashes, Delete Clashes, Merge Clashes, Solve a Single Clash and Solve Multiple Clashes. The second component is a dynamic database that records the clash data in .json files located in a folder generated automatically for each project analyzed by the tool. The third component is a Clash Sphere Revit Family that will be loaded and placed over each clash detected in the model. |
|
1.0.3 |
This version of the AvantLeap Clash Detection Tools consists of three main components. The first is a toolbar with 5 Buttons that run the following commands: Find Clashes, Delete Clashes, Merge Clashes, Solve a Single Clash and Solve Multiple Clashes. The second component is a dynamic database that records the clash data in .json files located in a folder generated automatically for each project analyzed by the tool. The third component is a Clash Sphere Revit Family that will be loaded and placed over each clash detected in the model. |