This article was generated by prompting our AI support agent.

The prompt provided towards the bottom can be used to generate your own, updated version of this use case as the support articles the AI is trained on change over time.

This article contains information about the following topics:

Sarah Chen oversees the digital coordination for the new Metro Transit Hub project.

With 15 years in construction technology, Sarah specializes in transforming external clash detection reports into streamlined coordination workflows within Catenda Hub using topic boards, labels, and milestone tracking.

Sarah's role centers on creating the BIM Execution Plan and establishing digital quality control processes. She works with structural engineers using Tekla, MEP teams in Revit, and architects in ArchiCAD - all requiring seamless coordination through organized topic boards with custom statuses and types.

Sarah manages multidisciplinary teams through structured topic boards, creates coordination workflows using external tools, and ensures milestone compliance through digital processes.

The Metro Transit Hub project generated over 3,000 clash detections when the team ran clash detection in Solibri Model Checker. Without proper organization, these issues would create chaos and missed deadlines.

Sarah needed separate topic boards for different disciplines, each with custom statuses (Active, In Review, Resolved, Approved) and types (Clash, RFI, Warning) to track the lifecycle of every coordination point. Labels became crucial for grouping topics by floor, priority, or technical system, significantly improving discoverability.

Topic board separation prevents information overload, custom statuses track progress, and labels enable efficient filtering and assignment.

Structural Lead Engineer

Marcus Rodriguez manages steel frame coordination using dedicated Structure-MEP topic boards.
He filters topics by assigned status and resolves structural conflicts within 48 hours using milestone tracking.

MEP Coordination Manager

Lisa Park oversees mechanical systems through MEP-specific topic boards.
She uses labels to prioritize critical issues and manages routing conflicts through custom status workflows.

Architectural Design Lead

David Kim maintains design intent through Architecture-MEP Integration boards.
He reviews clash resolutions using milestone filters and approves design modifications with proper status updates.

Site Construction Manager

Jennifer Walsh uses mobile access with label filters to focus on floor-specific issues.
She creates site-based topics and links them to existing coordination milestones.

Key takeaways

Each role works within specific topic boards, uses labels for filtering, and tracks progress through milestone integration.

The project's Level 3 Concourse required three separate topic boards:
​

Structure-MEP Coordination
Architecture-MEP Integration
Site Verification
​

Sarah configured each board with custom statuses and types matching the project's coordination process.

She implemented labels for Floor Level (L1, L2, L3), Priority (Critical, High, Medium, Low), and System Type (HVAC, Electrical, Plumbing, Structure).
This enabled teams to filter topics efficiently - MEP teams could view only "L3 + Critical + HVAC" issues.

Milestone integration linked coordination topics to project deadlines, providing real-time visibility into which issues could block progression.
Teams could assign topics directly to responsible members with clear deadlines.

Multiple topic boards organize disciplines, labels enable precise filtering, and milestone tracking ensures deadline compliance.

Sarah creates separate boards for Structure-MEP Coordination, Architecture-MEP Integration, and Site Verification. Each board receives custom configuration for statuses (Active, In Review, Resolved, Approved) and types (Clash, RFI, Warning, Coordination).

She establishes labels for Floor Level, Priority, System Type, and Responsibility. Labels become the primary filtering mechanism, allowing teams to quickly find their assigned issues using combinations like "L3 + High Priority + Structural".

Each topic board gets configured with minimum one open status and one closed status. Types are customized for each discipline - structural boards might have "Foundation Clash" and "Steel Conflict" types while MEP boards use "Routing Issue" and "Equipment Clash".

Topics get assigned directly to team members with due dates linked to project milestones. The platform tracks assignments by person and team, with filters available for "My topics," "Assigned to me," and milestone-specific views.

When importing BCF reports from Solibri, Sarah ensures they land in the appropriate topic board with correct labels and assignments. Teams can then create topics from clash results using various options - single combined topics or individual topics for each clash.

Systematic topic board setup, comprehensive labeling, and milestone integration create accountability and transparency in coordination processes.

You are a BIM Manager for a General Contractor on a high-intensity infrastructure project. You are the architect of the BIM Execution Plan (BEP) and the primary authority for digital quality control and coordination milestones.

You are a master of digital coordination who thrives during high-pressure weeks where thousands of technical and geometric clashes are identified. You understand that managing these at scale requires moving away from static PDF reports toward a centralized, live coordination hub. You know how to leverage the natural "find-and-fix" instincts of a project team by providing them with a professional, structured environment for their work.

Your objective is to transform a massive dataset into an actionable workflow by:

Separating Topic Boards:

Organizing thousands of Topics into category-specific boards to prevent data silos.

Defining Life Cycles:

Establishing clear statuses and types for every board to ensure designs follow a strict validation path.

Ensuring Accountability:

Spreading the workload across teams to ensure that milestone-blocking issues are resolved before formal reviews.

Providing Transparency:

Creating a bulletproof audit trail for every decision, revision, and approval.

The project is entering a critical coordination phase, and your clash detection software has just identified thousands of issues. To manage this in Catenda Hub, you implement the following system:

Topic Board Separation:

You create distinct boards based on discipline (e.g., Structure, MEP, Architecture) or severity. This keeps technical iterations organized and searchable.

Configuring Statuses and Types:

For each board, you configure specific types (e.g., Clash, RFI, Warning) and statuses (e.g., Active, In Progress, Resolved, Approved). This ensures that the lifecycle of every coordination point is tracked according to ISO 19650 standards.

Tracking via Milestones:

You link Topics across different boards to project milestones. This allows you to track real-time health and identify exactly which clashes will block the project's continuation if not resolved by a specific date.

Grouping with Labels:

You utilize labels to group Topics by floor, priority, or technical system. This significantly improves discoverability, allowing trades to quickly filter and find the issues they are responsible for.

Workload Distribution:

You divide responsibilities by assigning Topics to specific members or multidisciplinary teams. By linking Topics directly to BIM objects and 3D views, you ensure that the Structural or MEP lead can find, discuss, and resolve the issue without ever leaving their native authoring environment.

Your success is measured by hitting contractual milestones on time with zero manual data re-entry. You know that a decision not documented in context is a decision that didn't happen. Your goal is to provide a "clash-free" report that serves as an unalterable insurance policy for the project's history.