# False Positive Clash Filtering

*/Problems/False_Positive_Clash_Filtering*

## Problem Severity Frequency

_Illustrative — target and order-of-magnitude estimate figures, not an achieved track record (this Thing is concept-stage)._

**Severity**: 3
**Frequency**: weekly
**Budget Reality**:
- **Price Ceiling**: ~$3k–10k/yr per license — ceiling is capped by the cost of standard coordination tools like Navisworks and the fractional FTE offset
- **Who Controls Spend**: VDC Director or VP Preconstruction
- **Existing Budget Line**: true
- **Switching Cost From Status Quo**: moderate: must integrate directly into existing Navisworks or BIM 360 workflows as a plugin rather than forcing a separate standalone platform
**Regulatory Risk**: none
**Time Cost Per Event**: ~4–8 hours
**Money Cost Per Event**: ~$300–800 labor cost
**Annual Cost Per Affected Entity**: ~$20k–60k all-in wasted labor

## Problem Why Now

Recent industry mandates pushing Building Information Modeling to Level of Development 400 require trades to model exact insulation thicknesses, hangers, and flexible conduits. This granularity generates an exponential volume of raw geometric clashes that mathematically overwhelms coordination schedules. Prior solutions relied on brittle, hardcoded exclusion rules that fail entirely when confronted with the millions of unique spatial permutations found in dense commercial builds.

The specific lever making this addressable today is the commercial availability of geometric deep learning and multimodal models capable of processing 3D spatial graphs alongside metadata. Unlike three years ago, when algorithms relied purely on overlapping bounding boxes, current systems execute semantic reasoning to understand material properties and field tolerances. This allows software to recognize a flexible conduit resting on a ceiling grid as an expected field condition rather than a structural collision, resolving the manual filtering bottleneck.

## Problem Current Solutions

**Status Quo**: VDC coordinators run clash detection in federated models and visually inspect thousands of geometric collisions one by one to manually dismiss expected field overlaps. They spend hours manually grouping acceptable penetrations and flexible material intersections to bulk-approve them before actual trade coordination begins.
**Workarounds**:
- exporting clash reports to Excel for sorting
- creating custom search sets to exclude specific layers
- setting global clearance tolerances that hide tight but real clashes
- manually grouping clashes by element ID
**Named Tools In Use**:
- [Autodesk Navisworks Manage](/Products/Autodesk_Navisworks_Manage)
- [Autodesk BIM Collaborate Pro](/Products/Autodesk_BIM_Collaborate_Pro)
- [Revizto](/Products/Revizto)
- [BIM Track](/Products/BIM_Track)
**Why Insufficient**: Current coordination software relies entirely on rigid geometric boundary intersections and lacks the semantic awareness to recognize material properties or trade-specific construction tolerances. They cannot infer field routing logic, requiring humans to manually override mathematically accurate but practically irrelevant collisions.

## Problem Market Profile

**Incumbents**:
- [Autodesk Navisworks Manage](/Problems/False_Positive_Clash_Filtering/Competitors/Autodesk_Navisworks_Manage)
- [Autodesk BIM Collaborate Pro](/Problems/False_Positive_Clash_Filtering/Competitors/Autodesk_BIM_Collaborate_Pro)
- [Revizto](/Problems/False_Positive_Clash_Filtering/Competitors/Revizto)
- [BIM Track](/Problems/False_Positive_Clash_Filtering/Competitors/BIM_Track)
- [Solibri Office](/Problems/False_Positive_Clash_Filtering/Competitors/Solibri_Office)
**Substitutes**:
- Exporting clash reports to Excel for sorting
- Creating custom search sets to exclude layers
- Setting global clearance tolerances to hide tight overlaps
- Manually grouping clashes by element ID
**Position Axes**:
- Collision Logic (Strict Geometric vs. Semantic/Material)
- Resolution Process (Manual Triage vs. Automated Dismissal)
**Market Dynamics**: The VDC coordination market is shifting from disconnected desktop clash detection to centralized cloud-based issue tracking, creating massive datasets that emerging AI tools are now attempting to leverage for predictive clash grouping.
**Competition Concentration**: Incumbents heavily dominate the strict geometric and manual triage quadrant, providing highly accurate mathematical intersection data but forcing human coordinators to visually interpret and group every issue. Workarounds like spreadsheet sorting and custom search sets push further into the manual extreme to cope with the alert volume. The semantic and automated dismissal quadrant remains sparse, as existing platforms fail to natively recognize acceptable field conditions like flexible insulation compression without exhaustive manual rule configuration.

## Mint Vocabulary Bag

**Action Verbs**:
- triage
- suppress
- validate
- isolate
- resolve
- prune
- audit
**Gerund Stems**:
- triag
- suppress
- validat
- isolat
- resolv
- prun
- audit
**Abstract Nouns**:
- drift
- parity
- bias
- noise
- fidelity
- margin
- latency
**Concrete Nouns**:
- signal
- packet
- trigger
- match
- record
- alert
- payload
**Metaphor Nouns**:
- beacon
- prism
- sieve
- funnel
- anchor
- compass
- ballast
**Structure Nouns**:
- queue
- buffer
- registry
- docket
- vault
- pipeline
- matrix

## Problem Candidate Solutions

- [Ballocket](/Problems/False_Positive_Clash_Filtering/Startups/Ballocket) — Agent
- [Prunespan](/Problems/False_Positive_Clash_Filtering/Startups/Prunespan) — Software
- [Fidelitygate](/Problems/False_Positive_Clash_Filtering/Startups/Fidelitygate) — Software
- [Funnelatelier](/Problems/False_Positive_Clash_Filtering/Startups/Funnelatelier) — Service-as-Software
- [Overlap](/Problems/False_Positive_Clash_Filtering/Startups/Overlap) — Software
- [Visaudit](/Problems/False_Positive_Clash_Filtering/Startups/Visaudit) — Agent

## Problem Solution Space2x2

```mermaid
quadrantChart
x-axis Metadata-Driven --> Spatial-Driven
y-axis Hardcoded Rules --> Algorithmic Context
Ballocket: [0.2, 0.3]
Prunespan: [0.8, 0.9]
Fidelitygate: [0.85, 0.25]
Funnelatelier: [0.3, 0.8]
Overlap: [0.6, 0.6]
Visaudit: [0.4, 0.4]
```

## Problem Affected Roles

- VDC Coordinator — General Contractor
- BIM Manager — Architecture Firm
- MEP Detailer — Subcontractor
- Preconstruction Manager — Construction Management
- Project Engineer — Construction
- Field Coordinator — Trade Coordination
- Design Technology Manager — AEC Firm

## Problem Affected Companies

- General Contractors — VDC Departments
- MEP Subcontractors — Trade Coordination
- BIM Consulting Firms — Clash Management
- Architectural Design Firms — Design Coordination
- Structural Engineering Firms — Model Coordination
- Modular Construction Builders — Prefabrication

## Problem Affected Processes

- Federated Model Coordination — VDC Team
- MEP Trade Coordination — Subcontractor Alignment
- Constructability Review — Field Operations
- BIM Quality Assurance — Model Auditing
- Clash Detection Analysis — Issue Triage
- Design Verification — Engineering

## Problem Matching Opportunities

- AI Clash Triage for VDC Managers — AI Agent
- Semantic Clash Filtering for General Contractors — ML Classification
- Automated Soft Clash Resolution for MEP — Workflow Automation
- Clearance Clash Suppression for Architects — Predictive AI
- Historical Clash Classification for BIM — Data Pipeline

## Neighborhood

### Related (entails child problem)

- [Minimize Costly Structural Rework](/Problems/Minimize_Costly_Structural_Rework) — entails child problem · Problems

### Competitors

- [Autodesk BIM Collaborate Pro](/Competitors/Autodesk_BIM_Collaborate_Pro) — competes with · Competitors
- [Solibri Office](/Competitors/Solibri_Office) — competes with · Competitors
- [Revizto](/Competitors/Revizto) — competes with · Competitors
- [BIM Track](/Competitors/BIM_Track) — competes with · Competitors
- [Autodesk Navisworks Manage](/Competitors/Autodesk_Navisworks_Manage) — competes with · Competitors

### What it's used for

- [Revizto](/Products/Revizto) — used for · Products
- [Autodesk BIM Collaborate Pro](/Products/Autodesk_BIM_Collaborate_Pro) — used for · Products
- [Autodesk Navisworks Manage](/Products/Autodesk_Navisworks_Manage) — used for · Products
- [BIM Track](/Products/BIM_Track) — used for · Products

### Solves problem

- [Overlap](/Startups/Overlap) — candidate solution for · Startups
- [Fidelitygate](/Startups/Fidelitygate) — candidate solution for · Startups
- [Ballocket](/Startups/Ballocket) — candidate solution for · Startups
- [Prunespan](/Startups/Prunespan) — candidate solution for · Startups
- [Funnelatelier](/Startups/Funnelatelier) — candidate solution for · Startups
- [Visaudit](/Startups/Visaudit) — candidate solution for · Startups

### Entails child problem

- [Federated Model Cleansing](/Problems/Federated_Model_Cleansing) — entails child problem · Problems
- [Field Tolerance Analytics](/Problems/Field_Tolerance_Analytics) — entails child problem · Problems
- [Flexible Material Triage](/Problems/Flexible_Material_Triage) — entails child problem · Problems
- [Pre Coordination Validation](/Problems/Pre_Coordination_Validation) — entails child problem · Problems
- [Sleeve Allowance Processing](/Problems/Sleeve_Allowance_Processing) — entails child problem · Problems
- [Visual Clearance Verification](/Problems/Visual_Clearance_Verification) — entails child problem · Problems

### Who it serves

- [actors, producers, and directors](/CompanyTypes/actors,_producers,_and_directors) — serves · CompanyTypes

### What it addresses

- [discovering a change order was never priced until the owner asks where the money went](/Problems/discovering_a_change_order_was_never_priced_until_the_owner_asks_where_the_money_went) — addresses · Problems

### Similar Problems

- [Spatial Conflict Resolution](/Problems/Spatial_Conflict_Resolution) — similar · Problems
- [Resolve BIM Model Clashes](/Problems/Resolve_BIM_Model_Clashes) — similar · Problems
- [Resolve BIM Model Clashes](/Occupations/Architecture_and_Engineering_Occupations/Problems/Resolve_BIM_Model_Clashes) — similar · Problems
- [BIM Model Version Control](/Problems/BIM_Model_Version_Control) — similar · Problems
- [Site Rework Prevention](/Problems/Site_Rework_Prevention) — similar · Problems
- [Prevent Costly Project Rework](/Problems/Prevent_Costly_Project_Rework) — similar · Problems
- [Construction Defect Rework](/Problems/Construction_Defect_Rework) — similar · Problems
- [Architecture Fact Verification](/Problems/Architecture_Fact_Verification) — similar · Problems
- [Manual Site Photo Review](/Problems/Manual_Site_Photo_Review) — similar · Problems
- [Validate Building Code Compliance](/Occupations/Architecture_and_Engineering_Occupations/Problems/Validate_Building_Code_Compliance) — similar · Problems
- [Structural Rework Defect Correction](/Occupations/Construction_and_Extraction_Occupations/Problems/Structural_Rework_Defect_Correction) — similar · Problems
- [Safety Code Compliance](/Problems/Safety_Code_Compliance) — similar · Problems

### Similar Metrics

- [Clash Resolution Rate](/Metrics/Clash_Resolution_Rate) — similar · Metrics
- [Virtual Assembly Clash Rate](/Metrics/Virtual_Assembly_Clash_Rate) — similar · Metrics

### Similar Competitors

- [Autodesk Navisworks](/Competitors/Autodesk_Navisworks) — similar · Competitors

### Similar Startups

- [Peakarc](/Startups/Peakarc) — similar · Startups