Revit and Tekla BIM Collaboration: Bridging Connector Workflows

The Multi-Discipline Challenge

Modern construction projects involve multiple disciplines working simultaneously: architects design the building envelope in Revit, structural engineers model the frame in Tekla Structures, and MEP engineers lay out mechanical and electrical systems — often in Revit MEP, but sometimes in specialized tools like MagiCAD or Plancal Nova.

Each discipline produces BIM models in its native software format. These formats are proprietary and incompatible. A Tekla model cannot be opened directly in Revit. A Revit model cannot be loaded into Tekla without conversion. This incompatibility creates a fundamental coordination challenge: how do teams from different disciplines review each other's work?

Why Direct File Exchange Fails

Format Incompatibility

Revit uses the .rvt format. Tekla uses .tekla (and its internal database). These formats encode not just geometry but software-specific behaviors: Revit families, Tekla connections, parametric constraints, and view definitions. None of this translates directly between applications.

Data Loss During Conversion

The standard workaround is IFC export. Both Revit and Tekla can export IFC files, which can then be imported into the other tool for reference. But IFC conversion is lossy:

• Revit families may export as simplified geometry, losing parametric information
• Tekla connection details (bolts, welds, plates) may not have IFC equivalents
• Custom properties require explicit mapping to IFC property sets
• Material assignments and visual styles often do not survive the round trip

The exported IFC file is useful for visual coordination but unreliable for data-driven processes like quantity takeoff or clash detection at the connection level.

Version Synchronization

Even if the conversion is acceptable, keeping exported files synchronized is painful. Every time the structural engineer updates the Tekla model, they must re-export the IFC and share it with the architectural team. If the architect updates their Revit model at the same time, both teams end up working with outdated reference models.

File-based exchange creates a lag between the current state of each discipline's model and the version available to other disciplines. This lag is where coordination failures hide.

The Role of Connectors

Connectors solve the exchange problem by providing a direct path from the authoring tool to a neutral platform. Instead of exporting, sharing files, and importing, the workflow becomes:

1. Model in your native tool (Revit, Tekla, Archicad)
2. Click a button to upload the model and its data to the platform
3. Other team members view and review the model on the platform
4. Coordination happens on neutral ground — no one needs to install the other team's software

Connectors are plugins installed inside the BIM authoring tool. They extract both the model geometry and the associated data (properties, classifications, spatial structure) and upload it to the collaboration platform in a format the platform understands.

How Viralution Connectors Work

Revit Connector

The Viralution Revit Connector installs as an add-in inside Autodesk Revit. After installation, a Viralution panel appears in the Revit ribbon.

The upload workflow:

1. Open your Revit project
2. Click "Upload to Viralution" in the ribbon
3. Select the target space (personal or project)
4. The connector extracts geometry, properties, and spatial structure
5. The model appears on the platform within minutes, depending on size

The connector handles the format conversion transparently. The architect does not need to think about IFC settings, export configurations, or file management. They model in Revit and upload when ready.

Key capabilities:

• Full model upload: Geometry, properties, spatial hierarchy, and material assignments
• Selective upload: Upload specific views or element categories
• Version tracking: Each upload creates a new version; the platform maintains full history
• Property mapping: Revit parameters are mapped to the platform's data model automatically

Tekla Connector

The Viralution Tekla Connector works similarly, installed as an extension inside Tekla Structures. Structural engineers use it to upload their models directly from Tekla to the same platform where the architectural model lives.

Tekla-specific handling:

• Structural elements: Beams, columns, plates, and braces are uploaded with their section profiles and material grades
• Assembly information: Tekla assemblies and sub-assemblies maintain their grouping on the platform
• Connection details: Bolt groups, welds, and connection plates are preserved where possible
• Phase and status: Tekla's built-in phase and status properties transfer to the platform

Cross-Discipline Coordination Workflow

Here is how a typical multi-discipline coordination cycle works with connectors:

Week 1: Initial Model Uploads

The architect uploads the latest architectural model from Revit. The structural engineer uploads the latest structural model from Tekla. Both models appear on the Viralution platform in the same project.

Team members can now view both models in the platform's viewer — overlaying structural steel on the architectural layout to check spatial relationships.

Week 2: Review and Comment

The structural engineer reviews the architectural model and notices that a column location conflicts with a planned opening. They create a comment on the platform, tagging the specific model element and attaching a screenshot.

The architect sees the comment notification, opens the platform, and reviews the issue. They agree the column needs to move and update their Revit model accordingly.

Week 3: Updated Uploads

The architect re-uploads the updated Revit model. The platform creates a new version. The structural engineer can now compare the new version with the previous one to verify that the column location issue is resolved.

Meanwhile, the structural engineer has also updated their Tekla model to adjust connection details. They upload the new version through the Tekla connector.

Continuous Cycle

This cycle repeats throughout the design phase. Each upload triggers automated quality control checks that validate the model against project standards. Issues are caught at the point of upload, before they enter the coordination review.

Scaling Beyond Two Disciplines

Real projects rarely involve only architecture and structure. MEP engineers — mechanical, electrical, plumbing — typically join coordination during schematic design and produce some of the most clash-prone models. An HVAC duct route that conflicts with a structural beam is one of the most common coordination issues on commercial projects.

The connector-based workflow scales naturally to additional disciplines. MEP engineers upload their models through the same platform using connectors for their authoring tools or by uploading IFC files directly. All models appear in the same project space, and the platform's viewer can overlay any combination of disciplines. This means a mechanical engineer can check their ductwork against both the structural frame and the architectural ceiling in a single view, rather than requesting separate reference files from each discipline and loading them manually.

For large projects with ten or more discipline models, establishing a clear upload schedule becomes critical. Without an agreed cadence, some disciplines upload daily while others upload weekly, creating coordination gaps where teams review outdated combinations of models.

Benefits of Connector-Based Collaboration

No Software Lock-In

Team members work in their preferred tool. The architect stays in Revit. The structural engineer stays in Tekla. Neither needs to learn or install the other's software. The collaboration platform is the neutral meeting point.

Always-Current Models

Because uploading is a one-click action from within the authoring tool, teams upload more frequently. The models on the platform stay closer to the current state of design, reducing the coordination lag that file-based exchange creates.

Unified Review Experience

Instead of each discipline sending export files in different formats, everyone reviews models in the same viewer with the same interface. Comments, measurements, and annotations are consistent regardless of which authoring tool produced the model.

Audit Trail

Every upload, comment, and review action is logged. Project managers can see who uploaded what, when, and which issues were raised and resolved. This audit trail is valuable for contractual documentation and for understanding how design decisions evolved.

Automated Quality Gates

When connectors are paired with automated QC pipelines, every model upload is validated automatically. The structural engineer's Tekla upload triggers structural checks; the architect's Revit upload triggers architectural checks. Issues are flagged before the coordination meeting, making reviews more productive.

Getting Started with Multi-Discipline Collaboration

1. Install connectors: Download the Revit and Tekla connectors from the Viralution website
2. Create a project: Set up a shared project on the platform and invite team members from each discipline
3. Upload initial models: Have each discipline upload their current model through their respective connector
4. Establish an upload cadence: Agree on when each discipline will upload updated models (e.g., every Monday before the coordination meeting)
5. Set up QC pipelines: Configure automated quality checks for each discipline's model submissions
6. Review and iterate: Use the platform for coordination reviews, capturing issues as comments tied to specific model elements

The goal is to make model sharing frictionless. When uploading takes seconds and happens within the tool teams already use, it happens more often. More frequent uploads mean smaller differences between versions, which means fewer surprises during coordination.

For teams working on projects where data needs to stay on-premise, Viralution offers self-hosted deployment options that keep all model data on your organization's infrastructure while maintaining the same connector-based workflow.