OSTACOLO is an Autodesk Revit add-in designed to manage clash detection, tracking, and resolution directly inside the Revit environment. Instead of relying entirely on external coordination platforms and repeated export/import workflows, OSTACOLO keeps clash identification and issue management within the active project model. It stores clash data persistently in the Revit file using Extensible Storage while also maintaining a structured JSON database for sharing and offline coordination.
Core Purpose
The primary purpose of OSTACOLO is to turn clash coordination into an in-model workflow. Traditional clash detection often requires moving data between Revit and separate coordination applications, which can create extra steps, disconnected issue records, and coordination overhead. OSTACOLO addresses this by detecting clashes, placing visual markers, storing issue data, and managing clash status changes without requiring users to leave Revit.
Detection Protocols
OSTACOLO detects geometric conflicts using five configurable discipline protocols. These include Structural vs MEP, Architecture RC versus Structural and MEP, Architecture WD versus Structural and MEP, MEP Internal, and a combined All protocol. This structure allows users to target specific coordination scenarios rather than running only broad, unfocused clash tests.
The Architecture RC protocol focuses on roof, floor, and ceiling elements, while the Architecture WD protocol focuses on windows and doors. MEP Internal checks conflicts within MEP disciplines, and the All protocol provides a broader combined coordination review. Each protocol can be configured to suit the coordination goals of the project team.
Hard Clash and Clearance Modes
Each detection protocol supports two clash modes. Hard Clash mode identifies physical intersections between element solids, flagging situations where elements overlap in the model. Clearance mode identifies elements that do not intersect but fall within a user-defined minimum distance, measured in millimetres. This allows teams to detect both direct conflicts and spacing violations that may affect constructability, maintenance access, code compliance, or coordination requirements.
Visual Clash Markers
When a clash is detected, OSTACOLO places a visual Clash Sphere family instance at the clash location. This marker provides an immediate model-based reference point that users can see and navigate to inside Revit. The Clash Sphere family is automatically loaded on first run, helping make the setup process more efficient and ensuring a consistent visual representation of issues across the project.
Clash Record Data
Each Clash Sphere is linked to a complete clash record. The record includes a global project ID, a building-local ID, the detection workflow used, the current clash status, the element IDs of both clashing objects, the intersection coordinates, the calculated clash volume, the creation date, and the username of the person who detected the clash. This structured data helps teams track each issue consistently from discovery through resolution.
Persistent Dual Storage
OSTACOLO stores clash information in two locations at the same time. Extensible Storage keeps the clash data persistent inside the Revit model, supporting an in-model coordination workflow. A structured JSON database stores the same information externally, making it possible to share clash data with coordinators, reviewers, or project leads who may not have access to Revit. This dual-storage strategy supports both model-based issue management and offline coordination.
Clash Dashboard
The View Clashes dashboard provides a central interface for browsing, filtering, navigating, and managing detected clashes. Users can filter records by status, workflow, building, or date, making it easier to focus on open items, specific discipline checks, or issues from a particular building. The dashboard also allows users to navigate directly to a clash in a 3D view, reducing the time required to locate and understand coordination problems.
Clashes can be managed through a four-state workflow: Open, In Progress, Closed, and Ignored. This status structure gives teams a simple but effective way to track the lifecycle of each coordination issue. Open items represent unresolved clashes, In Progress indicates active review or correction, Closed marks resolved clashes, and Ignored allows teams to document clashes that are intentionally left uncorrected or are not considered actionable.
Multi-Building Coordination
For larger projects made up of multiple buildings or linked Revit models, OSTACOLO includes a cross-building Clash Reviewer. This reviewer aggregates clash records from multiple linked models that share the same project name, allowing project leads to review coordination issues at a broader scheme level. This is especially useful for campus, multi-building, residential, healthcare, industrial, and phased development projects where clash resolution needs to be monitored across several model files.
JSON Manager and Non-Destructive Sync
The JSON Manager supports controlled data exchange between the Revit model and external JSON files. Users can pull status updates from a JSON file that has been reviewed or edited offline, or push current model data out to JSON for sharing. The sync process is non-destructive, meaning it updates relevant status information without overwriting the original detection records. This protects the integrity of the clash history while supporting collaboration with people outside the Revit model.
Key Features
- Provides five discipline-specific detection protocols covering Structural, Architecture, and MEP coordination scenarios.
- Supports Hard Clash detection for physical intersections and Clearance detection for configurable spacing violations.
- Places visual Clash Sphere markers at detected intersection points in the Revit model.
- Stores clash records persistently using both Revit Extensible Storage and a structured JSON database.
- Tracks clashes through four statuses: Open, In Progress, Closed, and Ignored.
- Includes a View Clashes dashboard for filtering, navigation, and status management.
- Supports multi-building coordination through a cross-building Clash Reviewer.
- Provides non-destructive JSON sync with Update Model from JSON and Update JSON from Model workflows.
Requirements and Project Configuration
OSTACOLO requires an active Revit project. Detection runs on the open model and any loaded Revit link instances, allowing teams to analyze both host and linked model content. Results are stored per building and per project using the names configured in the File Config settings, so consistent project and building naming is important for reliable clash organization and cross-building review.
Practical Value
OSTACOLO provides a practical in-Revit coordination workflow for teams that want to detect, document, and manage clashes without relying entirely on external coordination software. By combining clash detection, visual markers, persistent model storage, JSON-based sharing, dashboard filtering, and status tracking, it helps BIM teams maintain a clear record of coordination issues from discovery through closeout. Its multi-protocol detection options and multi-building review capability make it especially useful for complex projects where coordination needs to be both detailed and traceable.
Advertisement
No comments:
Post a Comment