Why Is Your Architect Friend Like That? 5 "Incurable Diseases" of the Design-Obsessed

I watched a YouTube video and related to this, so I decided to summarize it.

 

If you have an architect in your life—or heaven forbid, you are dating one—you’ve likely noticed a series of peculiar, often infuriating behaviors. In the media, we are portrayed as romantic, brooding leads. But the reality? It smells like spray adhesive, lukewarm energy drinks, and 3:00 AM desperation.

As a veteran who has spent two decades in this field, I can confirm that these aren't just "quirks." They are professional pathologies developed in the trenches of the design studio. Here are the five most common symptoms of the design-obsessed.

1. The Material Fetish: Wall-Stroking in Public

If your architect friend disappears during a walk, check the nearest facade. We aren't just looking; we are stroking the brickwork or knocking on panels to check for "authenticity." A hollow "thud" from cheap plastic masquerading as stone breaks our hearts.

• The Reality: We are people who realize dreams with other people's money. Since we rarely have the budget to build our own temples, these physical encounters are deeply personal.

2. Funeral Chic: The All-Black Uniform

Gather a group of architects, and it looks like a mid-range funeral. From the "G7" parties at Columbia to local studios, black is the only acceptable color.

• The Hack: It’s not just about "minimalist philosophy." When you’re running on three hours of sleep, "matching" is a luxury. Black always matches black. It’s the uniform of the weary designer.

3. The Mainstream Hater (The Design Hipster)

We have a reflex to criticize anything "Instagrammable." We enter a popular space, cross our arms, and look for flaws to maintain our professional authority.

• The Light-Speed Flip: However, if we find out a space we just trashed was designed by a "Master," our opinion pulls a 180-degree flip: "Actually, the depth of the Master is truly different. You can feel the intention now."

4. The Off-Clock Philosopher: Jargon at the Pub

You want to talk about a funny YouTube video; we want to talk about Peter Zumthor’s concept of "place-ness" while staring hauntingly at the pub's ceiling. Using terms like "spatial violence" in a casual setting is a total mood-killer, but we just can't turn "Architect Mode" off.

5. Whitening Disease (백색증): The War on 4000K+ Lighting

This is perhaps our most clinical-grade hatred. We loathe standard, cool-white overhead lighting. We would literally rather eat our delivery pizza in total darkness—illuminated only by the silhouette of the pepperoni—than turn on a "cheap" ceiling fixture.

• The Struggle: Until we can afford that $3,000 designer floor lamp, we prefer to live like monks in a cave.

---

Conclusion: A Love Letter to the Sincere

While these traits are infuriating, they stem from a genuine desire to live in spaces that actually mean something. We strip away the noise to find the essence—L'épure. It’s exactly why architects so often end up marrying each other; no one else can tolerate a partner who refuses to turn on the lights.

Which of these "diseases" have you caught? Or are you the "Patient Zero" in your friend group?

---

Source & Credit:

• Video: 왜 건축가들은 꼭 ‘이런’ 행동을 할까? (건축가들의 5가지 직업병)

The Intelligence Era: 6 Surprising Takeaways from the Revit & Inventor 2027 Release

 The Intelligence Era: 6 Surprising Takeaways from the Revit & Inventor 2027 Release

1. The Automation Pivot: Moving Beyond the Manual Grind

For decades, the BIM workflow has been defined by a persistent "manual grind"—the exhausting repetition of numbering thousands of elements, fiddling with tag leader placement, and painstakingly calculating reinforcement schedules. The 2027 release of Revit and Inventor signals a definitive pivot in Autodesk’s philosophy. We are moving away from the era of incremental tool updates and entering the Intelligence Era, where the software is designed to "think" through the relationships between model elements. As a Senior Strategist, I see this not just as a productivity boost, but as a fundamental shift toward AI-driven logic and automated workflows that allow architects and engineers to focus on design intent rather than data entry.

2. The Co-Pilot Arrives: The Autodesk Assistant (Revit & Inventor)

The most significant headline is the debut of the Autodesk Assistant, an AI agent currently in tech preview. Integrated as a palette, this agent bridges the gap between natural language and complex API commands. It is designed to assist in three high-value areas:

• Model Querying & Insights: Users can query the model directly—for instance, asking, "How many windows exceed a width of 800mm?" The Assistant performs the geometric analysis and returns the count instantly.
• Workflow Automation: In Inventor, the Assistant’s reach is even more strategic, capable of generating PDF drawing packs and scripting emails to suppliers or manufacturers. In Revit, it can suggest the most appropriate view templates based on the model context.
• Active Model Changes: The AI can now perform "bulk edits" that previously required manual selection or Dynamo scripts, such as updating sill heights for every door on a specific level or generating door schedules.

The Strategist’s Warning: Hallucinations and Efficiency While promising, the Assistant remains in its infancy. In recent testing, the agent successfully generated a door schedule but failed to apply requested formatting, such as blank lines and total counts in the Project Browser. This highlights the current risk of "AI hallucinations"—where the agent may execute a command but miss critical nuances.

"It's really new still... and I do have high hopes for it."

3. Universal Logic: The Extinction of Fragmented Numbering

The 2027 release marks the extinction of fragmented numbering workflows. The specialized rebar numbering tool has been retired and replaced by a centralized, algorithm-based Numbering Tool on the Manage tab. This represents a "Universal Logic" that applies to almost any category.

• Rule-Based Linking: Designers can now link door marks directly to room numbers (e.g., Room 101A, 101B) via a rules-based template. The logic is persistent; if you flip a door or change a host, the numbering relationship remains stable once the host is reapplied.
• Sequence Integrity: The tool features a "Remove Gaps" function, allowing users to automatically close sequence breaks in structural partitions or architectural schedules with a single click.
• Stair Documentation: This logic extends to stairs, where tread numbering can now be customized with unique graphics and text for levels above or below the cut line—a vital win for professional documentation standards.

4. Computational Reinforcement: Custom Spacing and Morphing

Structural engineering workflows have been consolidated into a new Concrete Ribbon Tab, but the real power lies in the new syntax and geometry tools.

• Proportional Syntax: A new layout rule introduces "Custom Spacing" using a percentage-based syntax: 25% at 10, 50% at 20, 25% at 10. The use of the % symbol is a strategic breakthrough, allowing for proportional distribution that automatically adjusts if the host length changes.
• 3D Path Rebar: This tool enables rebar distribution along complex, curved, or non-linear paths by following the geometric center-line of the host, a necessity for modern infrastructure projects.
• The Morph Tool & Its Limits: The "Morph Tool" allows for the rapid placement of vertical rebar in columns by clicking a bar segment. However, experts should note its current technical limitation: it cannot handle stirrups or shapes that wrap entirely around a host (such as in stairs). For these scenarios, designers must use hooks as a workaround.
• Procurement Data: A new, read-only "Reinforcement Mass" parameter simplifies weight calculations, linking design directly to procurement.

5. Frictionless Workspace: Modernized UX and Persistent Geometry

To reduce "mouse travel" and cognitive load for power users, Autodesk has initiated a major UI/UX consolidation by phasing out the Options Bar. All tool-specific settings—including "Room Bounding," "Auto Join," and "Height/Depth"—have migrated to the main Ribbon. This affects the Wall tool (including the "Place by Room" and "Place by Segment" functions), Join, Cut, Offset, and Rotate tools.

• Enhanced Tag Leaders: One of the most requested "quality of life" fixes is the new Tag Leader Clipping. New clip icons at the start and end of tags allow for "Attached Start" positioning, finally ending the era of awkward, centered leader lines that cluttered complex drawings.
• Accelerated Graphics: Now out of tech preview, the graphics engine allows for real-time section box cutting. You no longer have to release the mouse to see the result; the model cuts dynamically as you move the box.
• Persistent Steel Cutting: Reference planes are now "smarter." In previous versions, rotating a reference plane would break the cut on a steel beam. In 2027, the cutting relationship is maintained during rotation, ensuring structural models remain stable during design iterations.

6. Democratizing Automation: iLogic Code Blocks and Sustainability

The pivot toward intelligence is perhaps most visible in Inventor 2027 with the introduction of iLogic Code Blocks.

• Visual Programming: Utilizing the "Blockly" format, this allows designers without coding knowledge to build complex rules through visual blocks. The system separates input logic (values and constraints) from model actions, making troubleshooting significantly easier. For the veterans, the tool still generates standard text-based code in the background, ensuring a consistent firm-wide standard.
• The Carbon Tab: Sustainability is no longer an afterthought. A new Carbon tab within the Material Browser allows users to assign embodied carbon assets directly to materials like concrete.
• Analytical Integrity: This focus on data quality extends to the Energy Model, which now features "cleaner edges" and more precise analytical panels, reducing the "jagged" geometry of previous versions and providing more accurate results for energy optimization.

Conclusion: A New Baseline for BIM

The 2027 release signifies that "intelligence" is no longer an add-on; it is the new baseline for BIM. From AI assistants that script supplier emails to numbering tools that understand architectural relationships, the focus has shifted from manual drafting to high-level logic management.

As these tools move out of tech preview and into your daily production, the question for every lead designer is clear: Are you ready to let an AI agent handle your project's mundane scheduling, or do the risks of "hallucination" keep you clicking manually?

Construction 4.0: Navigating the Paradigm Shift from a 20-Year Veteran’s View Reflecting on the Evolution of the Industry

 I recently had the honor of presenting my analysis on the impact of the 4th Industrial Revolution on the construction industry at a professional training session. Based on 20 years of on-site experience, I examined how technologies like BIM, Drones, and AI are reshaping our field. Here is a summary of the dual nature of this digital shift.

The Bright Side: Productivity & Safety Revolution

• Productivity Leap: Prefabrication and modular construction are cutting project timelines by up to 50%, transforming a labor-intensive industry into a knowledge-based one.

• Data-Driven Quality: Using BIM and VR for pre-construction simulations minimizes errors and optimizes resources, aligning perfectly with my philosophy of "L'épure"—finding the pure essence through precision.

• Enhanced Safety: IoT and real-time monitoring are no longer optional but essential tools to predict and prevent on-site accidents.

The Challenges: The Reality of Implementation

• Labor Market Disruption: The rise of automation raises concerns about job security for low-skilled workers, necessitating a social safety net and reskilling programs.

• Investment Barriers: The high initial cost of infrastructure remains a significant hurdle for SMEs.

• Cultural Inertia: The rigid, hierarchical culture of traditional construction can act as a friction point against the fluid and creative nature of Digital Transformation (DX).

The Role of the "Finisher" in the Smart Age As a BIM CM Coordinator, I believe our mission is to blend 20 years of craftsmanship with digital intelligence. The goal is to archive only what matters—eliminating waste and building resilience. Digital transformation is not just about the tools we use; it’s about how we rethink the "essence" of space and construction.

Impact of Industry 4.0 in Construction (Selected Presentation at KBU)

 The Intersection of Experience and Education I recently completed a professional training program at the Kyungbok University (KBU) Construction Technology Education Center. It was a rigorous course designed for senior engineers, and I am proud to share that my final analysis on "Industry 4.0 in Construction" was selected as an outstanding case study for presentation.

Strategic Analysis: Pros and Cons of Digital Transformation In my presentation at KBU, I focused on how technologies like BIM, Drones, and AI are transforming our traditional labor-intensive paradigm into a data-driven one.

• The "Finisher's" Advantage: Technologies such as 3D printing and BIM-based simulations allow us to achieve near-perfect quality—the ultimate goal of my brand, L'épure.

• Addressing the Gap: However, I also emphasized the challenges, such as the initial investment costs for SMEs and the need for reskilling an aging workforce in the industry.

A New Chapter as a BIM CM Coordinator This recognition at Kyungbok University marks a significant milestone in my journey as a BIM CM Coordinator. I am more committed than ever to integrating 20 years of craftsmanship with digital intelligence to streamline construction processes globally.

The Aesthetics of Failure: What a 7-Year British Experiment Taught a Construction Expert

 

 In the world of construction, "completion" is often defined by the final inspection. But for a professional who has spent 20 years on site, space is a living organism. From 2015 to 2022, I conducted a profound architectural experiment: Cafe Trafalgar. My goal was to transplant the identity of London's Trafalgar Square into the heart of a Korean city.

[The Zenith of Planning: Architectural Integrity] Cafe Trafalgar was not just a commercial project; it was a manifestation of L'épure (the essence).

• Design Language: I obsessed over every detail—the classic moldings, the subdued navy and grey tones of London, and the open layout reflecting the plaza’s freedom.

• Craftsmanship: Leveraging two decades of experience in high-end residential projects, I ensured the quality of the "physical box" was flawless.

[The Critique: Why the "Perfect Space" Failed] Despite its aesthetic success, the project faced a cold reality. As a technical expert, I had overlooked the most critical variable: Site Strategy.

• The Flow of People: A plaza is a node of movement. My cafe, however, was an island. It required "destination appeal" that the location simply couldn't sustain.

• Technical Arrogance: I believed that "if the space is perfect, people will come." This was a romantic architect's delusion. In reality, the foundation of business is not just the concrete, but the accessibility and the flow of the market.

[The Evolution: From Space to Time] The 7-year journey of Cafe Trafalgar taught me that managing space is not about selling square footage; it’s about occupying the user's Time. Now, I am integrating this "expensive lesson" with BIM (Building Information Modeling) and Vibe Coding. By digitizing the failures of the past, I aim to create spaces that are not only beautiful but sustainable and operationally efficient.

Archive / L'épure is about refining these records to leave only the essence. My failure is now my greatest asset in the era of AI-driven construction management.

Revit Dynamo Basics: Master Get and Set Nodes for BIM Automation

 

If you've started using Revit Dynamo to reduce repetitive tasks, understanding the flow of data is your first step. Today, we’ll break down the core concepts of 'Get' (Read) and 'Set' (Write) nodes—the heart of any Dynamo workflow.

---

Q: What is the difference between Get and Set in Dynamo?

A: To put it simply, Get is for reading data from Revit, and Set is for writing data back into Revit.

• Get: Retrieves information such as element names, heights, or parameter values into the Dynamo workspace.

• Set: Applies processed or new data from Dynamo back into the actual Revit model.

---

1. Get (Reading Data): Extracting Info from Revit

Every Dynamo workflow begins with data extraction. Here are the three most frequently used nodes for "Getting" data:

• Element.GetParameterValueByName: The most versatile node. It reads specific parameters (e.g., Comments, Mark, Level) by entering the parameter name as a String.

• Element.Name: Use this to quickly identify the name of a selected element.

• FamilyInstance.GetLocation: Essential for extracting coordinates or location lines, often used as base data for placement automation.

---

2. Set (Writing Data): Updating the Revit Model

Once you have processed your data, it's time to push it back into Revit.

• Element.SetParameterByName: Think of this as the "Finish Line" of your script. It injects new values into a specific parameter of an element.

  • Input: Target Element, Parameter Name, and the New Value.

  • Result: The moment this node runs, the Revit model is physically updated.

---

3. Expert Tips to Avoid Common Dynamo Errors

To ensure your script runs smoothly, keep these three professional tips in mind:

① Match the Data Type

The data type you "Get" must match the type you "Set."

• String: Mark, Comments, Type Name, etc.

• Double / Number: Height, Length, Offsets, etc.

Pro Tip: Use the String from Object node if you need to convert numbers into text for a parameter.

② Case Sensitivity & Spacing

The parameterName must be an exact match to what is shown in Revit. "Comments" and "comments" (lowercase) are recognized as different, which will cause your script to fail.

③ Read-Only Parameters

Some parameters, like 'Area' or 'Volume' of a wall, are automatically calculated by Revit. You can Get these values, but you cannot Set them. Always check if a parameter is editable before trying to overwrite it.

---

4. Standard BIM Automation Workflow

1. Select Model Elements: Pick the objects in Revit you want to modify.

2. Element.GetParameterValueByName: Read the existing data.

3. Data Processing: Use nodes like String.Replace or Math to modify the data.

4. Element.SetParameterByName: Write the final values back into the Revit element.

---

💡 A Note from Kai Dynamo is ultimately a game of "What data to Get, how to manipulate it, and where to Set it." Mastering this flow is the key to automating 80% of your BIM manual tasks.

I hope this guide helps you boost your efficiency in Revit!

---

Search Keywords (Tags): #Revit #Dynamo #BIM #Automation #GetParameter #SetParameter #VisualProgramming #BIMManager #DynamoNodes

[Analysis] SH–Singapore Smart Construction Agreement: Can BIM Solve the Quality Crisis?

 Seoul Housing & Communities Corporation (SH) recently signed a smart construction partnership with Singapore’s JTC Corporation. As South Korea’s Ministry of Land, Infrastructure, and Transport (MOLIT) focuses on refining and realistic implementation of the BIM roadmap—ensuring field-level feasibility—this international collaboration marks a pivotal moment. From the perspective of a 20-year construction PM, here is an analysis of why this partnership matters for the future of building quality.

1. A Strategic Partnership Beyond the MOU

The significance of this agreement lies in the partner: JTC Corporation. As a Singaporean statutory board, JTC is a global leader in smart city infrastructure and digital twins.

• Knowledge Transfer: The focus is on sharing practical digital transformation cases and operational expertise rather than just high-level cooperation.

• A Proven Model: Singapore’s constraints as a small city-state led them to adopt BIM and Off-Site Construction (OSC) earlier and more systematically than almost any other nation.

2. SH’s 5-Point Smart Construction Strategy

SH is aggressively pursuing a 2030 vision where technology ensures safety and quality through five key pillars:

1. BIM (The Foundation): Digitalizing the entire lifecycle to prevent human errors and construction defects.

2. OSC (Off-Site Construction): Transitioning from field-based labor to factory-controlled assembly for uniform quality.

3. AI Integration: Utilizing artificial intelligence for design automation and predictive scheduling.

4. Construction Robotics: Deploying robots for high-risk or repetitive tasks to mitigate labor shortages.

5. Eco-friendly Construction: Integrating carbon neutrality and energy efficiency directly into the digital design phase.

3. Systemic Realities: Korea vs. Singapore

The gap between the two nations is not technical skill, but rather the ecosystem connecting policy to the field.

Dimension	Singapore’s Model	Korea’s Current Path
BIM Mandate	Fully mandated for public & private sectors with financial incentives.	Mandatory for large public projects (KRW 100B+), expanding through refined field-ready guidelines.
Financial Support	Government subsidies (BIM Fund) covered transition costs for firms.	Incentive frameworks and fee standards are being solidified under the national roadmap.
Regulatory Link	The BIM model is the actual regulatory submission for permits.	Focusing on building internal client capacity to review and verify BIM deliverables.

4. Can BIM Truly Prevent Structural Defects?

If data flows accurately across the supply chain, the answer is yes.

• Conflict Detection: Using BIM to detect clashes between underground utilities before excavation prevents ground subsidence.

• Data Verification: Comparing real-time site data with BIM design values allows managers to catch deviations in structural elements—like slab thickness or rebar spacing—before they become irreversible.

• Prerequisite: The value only exists if there is Data Continuity, meaning the model doesn’t stop at the design stage but lives through construction and maintenance.

5. Conclusion: From Policy Noise to Field Mastery

Recent adjustments to the national roadmap are not a "retreat" but an evolution toward a more implementable model. While policy becomes more precise, execution agencies like SH are taking the right step by securing global expertise to prove that these technologies work on the ground.

The technology is already here; what matters now is the culture and capability to use it. This partnership is a significant step toward a future where construction is driven by data, not just drawings.

---

#SHCorp #JTC #SmartConstruction #BIM #OSC #DigitalTransformation #ConstructionSafety #MOLIT #ConstructionAI #PropTech

BIM is a 'Promise,' Not Just a 'Drawing' - A 20-Year Veteran’s Reality Check

 

1. The Number that Changed My Perspective: 0 vs 100

In a 2D workflow, coordination errors often hit 100% at the construction site. In a true BIM environment, that number can drop to near zero. As a 50-year-old professional with over 20 years in the trenches of construction, I’ve realized that the frustration many architects feel toward BIM isn't about the software—it’s about the shift in responsibility.

2. "Why do I have to define components first?"

I recently read a comment that caught my eye: "Architects hate BIM because it forces them to define specific components before they can even play with the volume." The argument was that we need tools that let us design freely first and attach data later.

Honestly? As someone who has spent decades watching how buildings actually get built, that sentence made me incredibly uneasy.

3. My Journey from "Field Guy" to BIM Coordinator

I’ll admit it: I used to think BIM was just "Revit," a complicated 3D tool that slowed me down. But after preparing for my BIM CM Coordinator certification and fighting through the learning curve in my 50s, I saw the truth. I was struggling not because the tool was bad, but because my mindset was still stuck in "lines and faces" rather than "living data."

---

4. 3 Reasons Why "Data First" is the Only Way Forward

• Step 1: Focus on the 'I' (Information), not just the 'M' (Modeling) BIM isn't a 3D sketchbook. It’s a system where every wall and column carries "life" (data). We define them early because they dictate the cost, schedule, and, ultimately, the safety of the human beings on-site.

• Step 2: Avoid the "Attach Data Later" Trap Designing a volume and "attaching data later" is just a fancy way of saying "someone else will have to fix my mess on-site." This leads to the very double-work we are trying to escape. Front-loading the effort is a promise to the rest of the team that your design is buildable.

• Step 3: Shift from Design to 'Digital Construction' Digital transformation isn't about using a fancy hammer; it’s about speaking a universal language. If the tool feels like it’s limiting your creativity, ask yourself: "Is my design actually grounded in data, or is it just a pretty picture that can't be built?"

---

5. Start Your Transformation Today

Digital transformation is a change in attitude, not just technology. If a "field-hardened" veteran like me can embrace this shift, so can you.

Don't wait for the 'perfect' tool. Open your current project right now and ensure just one component is fully defined with accurate data (material, cost, or thermal rating). That single step is the difference between being a "drafter" and a "digital builder."

Is BIM making your life harder or easier? Let’s discuss in the comments. I’d love to hear from both the new generation and my fellow veterans.

#BIM #ConstructionTech #DigitalTransformation #Revit #AECIndustry #ProjectManagement #BIMCoordinator #BuildingInformationModeling

BIM Workflow · Navisworks · Clash Detection

Navisworks Clash Detective:
The Complete Field Guide

From setting up targeted clash tests with Search Sets to grouping results, assigning clashes, and exporting reports the design team can actually act on.

K

Kai Lee

Architect · BIM Specialist · A7 Studio

April 2026 · 12 min read

Clash Detective is where BIM coordination either works or falls apart. Run it wrong and you get thousands of irrelevant results that nobody acts on. Run it right — with targeted Search Sets, clear tolerances, and structured output — and you get a list of real problems with real owners.

⚙️

Clash Test

A defined check between two sets of elements — discipline A vs discipline B

🎯

Search Set Input

Targeted element groups replace "Entire File" — eliminates noise

📊

Results Management

Group, assign, status-track, and export clashes for resolution

📤

Report Export

HTML or XML output — shareable with teams who don't have Navisworks

PART 01 Clash Types — What You're Actually Detecting

Before setting up any test, you need to choose the right clash type. The wrong type produces either too many results or misses what matters.

Type	What it detects	Tolerance	Best used for
Hard	Physical intersection — elements are literally overlapping in 3D space	0mm	Structural vs MEP, pipe vs slab penetrations
Hard (Conservative)	Intersection based on bounding box — slightly looser than Hard	0mm	Quick first-pass check, complex geometry
Clearance	Elements are within a defined distance of each other — not touching but too close	50–200mm	Maintenance access, insulation clearance, fire rating gaps
Duplicate	Identical elements occupying the same space — usually a modelling error	0mm	QA checks, model cleanup before coordination

💡 Field recommendation: Always run Hard clashes first — these are the non-negotiables that must be resolved before construction. Run Clearance checks only after Hard clashes are resolved, using discipline-specific tolerances (MEP maintenance access typically needs 600mm minimum clearance).

PART 02 Setting Up a Clash Test — Step by Step

The difference between a useful clash test and a noise-generating one is almost entirely in how you define the input sets. Entire File vs Entire File on a large federated model can produce 50,000+ results. Search Set vs Search Set on the same model produces 200 results — all relevant.

Home → Tools → Clash Detective → Add Test → Configure → Run

1

Open Clash Detective

Go to Home tab → Tools panel → Clash Detective. The Clash Detective panel opens — keep it docked for the session.

Home → Tools → Clash Detective

2

Add a New Test

Click Add Test. A new test row appears with a default name. Rename it immediately using a consistent convention — e.g. STR vs MEP-HVAC · L3 · Hard. Good names save enormous confusion when you have 20+ tests running.

3

Set Selection A — First Discipline

In the test configuration, find Selection A. Change the dropdown from Entire File to Sets. Your saved Search Sets appear in the list. Select the appropriate set — e.g. STR - Level 3 - All Structural.

Selection A dropdown → Sets → choose Search Set

4

Set Selection B — Second Discipline

Repeat for Selection B. Select the opposing discipline set — e.g. MEP - HVAC - All Ductwork. The two sets must not overlap — if the same element appears in both sets, it will always clash with itself.

Selection B dropdown → Sets → choose Search Set

5

Set Clash Type and Tolerance

Select the Type (Hard, Clearance, Duplicate). For Clearance, set the Tolerance value in mm. For Hard clashes, leave tolerance at 0mm — or set a small positive value (e.g. 5mm) to filter out negligible model misalignments.

6

Run the Test

Click Run Test (or Run All to execute all configured tests at once). Navisworks processes the geometry intersection and populates the Results tab. Large models may take 30–120 seconds per test.

Clash Detective → Run Test / Run All

⚠️ Self-clash trap: If a Search Set contains elements from both disciplines being tested, those elements will clash against themselves and flood your results with false positives. Always verify your Search Sets don't overlap before running a test.

PART 03 Recommended Test Configuration Matrix

Here's the test matrix I use as a starting point on multi-discipline projects. Adapt the Search Set names to your project's naming convention.

Clash Test Matrix Standard BIM Coordination Setup

// ── HARD CLASH TESTS (Priority 1) ────────────────────── "STR vs MEP-HVAC · All Levels · Hard" A: STR - All - Structural Model B: MEP - HVAC - All Ductwork Type: Hard Tolerance: 0mm "STR vs MEP-PIPE · All Levels · Hard" A: STR - All - Structural Model B: MEP - PIPE - All Piping Type: Hard Tolerance: 0mm "STR vs MEP-ELEC · All Levels · Hard" A: STR - All - Structural Model B: MEP - ELEC - Cable Trays Type: Hard Tolerance: 0mm "ARCH vs MEP · All Levels · Hard" A: ARCH - All - Architecture Model B: MEP - All - MEP Combined Type: Hard Tolerance: 0mm // ── CLEARANCE TESTS (Priority 2) ─────────────────────── "MEP-HVAC vs STR · Clearance 50mm" A: MEP - HVAC - All Ductwork B: STR - All - Structural Model Type: Clearance Tolerance: 50mm "MEP-PIPE vs ARCH · Maintenance 600mm" A: MEP - PIPE - Over 150mm Diameter B: ARCH - Core - Walls and Partitions Type: Clearance Tolerance: 600mm // ── QA / DUPLICATE CHECKS (Priority 3) ───────────────── "STR - Duplicate Element Check" A: STR - All - Structural Model B: STR - All - Structural Model Type: Duplicate Tolerance: 0mm

PART 04 Managing Clash Results

Raw clash results are just a number. What matters is turning that number into an actionable list — grouped, assigned, and tracked through to resolution.

Clash Status — What Each Means

🔴

New

Just detected — not yet reviewed by anyone

🟡

Active

Reviewed and confirmed as a real issue — needs resolution

🟢

Reviewed

Under review — assigned to a responsible party

⚪

Approved

Accepted as-is — documented reason required

🔵

Resolved

Fixed in the model — verified in next run

1

Review Results in the Results Tab

After running, click the Results tab in Clash Detective. Each row is one clash instance. Click any row — Navisworks zooms to that clash in the viewport and highlights both conflicting elements.

2

Group Related Clashes

Select multiple clash rows (Ctrl+click) → right-click → Group. Give the group a meaningful name: e.g. Duct run D-03 vs Beam Grid B/3-4. Grouping consolidates related issues and makes the report readable.

Select rows → right-click → Group → name the group

3

Assign and Add Comments

Select a clash or group → in the right panel, set Assigned To (discipline responsible) and add a Comment describing the issue and required action. This information is exported with the report.

4

Update Status

Change the clash status as the resolution progresses: New → Active → Reviewed → Resolved. After the model is updated, re-run the test — resolved clashes should disappear from the New/Active count.

🎯 Coordination meeting workflow: Before each coordination meeting, run all tests → filter results to show only New and Active clashes → group related issues → assign to responsible disciplines. The meeting then focuses on resolution decisions, not on sorting through raw data.

PART 05 Exporting Clash Reports

Clash reports let you share findings with team members who don't have Navisworks — architects, engineers, or clients who need to understand what needs to be fixed.

Clash Detective → Report tab → Configure → Write Report

1

Open the Report Tab

In Clash Detective, click the Report tab (next to Results). This is where you configure what gets included in the export.

2

Select Report Contents

Check the fields to include: Clash Name, Status, Description, Assigned To, Comments, Element IDs, Viewpoint snapshot. Viewpoint snapshots (images) are essential — they show exactly where the clash is without needing Navisworks.

3

Choose Format and Export

Select format — HTML for human-readable sharing, XML for integration with other BIM tools or issue trackers. Click Write Report and choose a save location.

Report tab → Write Report → HTML or XML

💡 Naming the report file: Include the test name, date, and status filter in the filename.
ClashReport_STR-vs-MEP_2026-04-06_ActiveOnly.html
This makes it immediately clear what the report covers and when it was generated — critical when managing multiple revision cycles.

PART 06 Real-World Use Cases

🏗️

Slab Penetration Checks

Run MEP vs Structural Slab hard clash tests before structural shop drawings are issued. Catch missing sleeve locations before concrete is poured — not after.

🔩

Ceiling Space Coordination

Use clearance tests to verify ductwork, piping, and cable trays all fit within the ceiling plenum with required maintenance access — before suspended ceiling heights are fixed.

📋

Model QA Before Submission

Run Duplicate checks on each discipline model before it's appended to the federated model. Eliminate internal model errors before they become coordination clashes.

🔄

Progress Tracking

Re-run the same tests after each model update. Track the New / Active / Resolved counts over time — a falling Active count means coordination is working.

The goal isn't zero clashes in Navisworks.
It's zero surprises on the construction site.

PART 07 Clash Detective + Search Sets — The Full Workflow

Putting it all together — here's the complete coordination cycle that connects the Search Set XML workflow from the previous post directly into Clash Detective:

1

Import your standard Search Set XML

Load the team's master SearchSets_ProjectName_v1.xml into the Sets window. Everyone on the team starts from the same filter definitions.

2

Configure clash tests using those sets

Build your test matrix in Clash Detective using the imported Search Sets as inputs. Save the NWF file — the test configuration is saved with it.

3

Run all tests before each coordination meeting

Click Run All. Review new results, group related clashes, assign to responsible disciplines, add comments.

4

Export and distribute the report

Export as HTML with viewpoint snapshots. Share with all disciplines before the meeting — they can review clashes assigned to them in advance.

5

After model updates — re-run and track

When disciplines update their models, re-run the full test suite. Verified resolved clashes drop off the Active list. New issues surface automatically.

— ● —

🎯 Key Takeaways

Clash Detective is only as good as its inputs. Search Sets are the foundation — targeted inputs produce targeted results. Entire File vs Entire File produces noise.

Set up your test matrix once at the start of the project. Run it consistently before every coordination meeting. Group results, assign them, track status through to resolution. The clash count going down over time is your coordination health indicator.

This completes the three-part Navisworks coordination series: Selection Sets → Search Sets + XML → Clash Detective. In the next post, I'll cover Viewpoints and Saved Views — how to build a navigation system that makes any federated model easy to review, even for team members who didn't build it.

#Navisworks #ClashDetective #BIMCoordination #ClashDetection #SearchSets #BIMWorkflow #AEC #BIMTips #Autodesk #ConstructionTech