Introduction: Why Interdisciplinary Collaboration Matters in Structural Engineering

Complex building and infrastructure projects demand seamless coordination between structural engineers and disciplines such as architecture, mechanical, electrical, plumbing (MEP), civil, and geotechnical engineering. When these teams work in silos, the result is often costly rework, schedule delays, and compromised design quality. RISA software, with its comprehensive suite of structural analysis and design tools, offers a powerful platform to bridge these gaps. However, the software alone is not enough—teams must adopt deliberate practices to maximize its collaborative potential. This article provides actionable, field-tested tips to help structural engineers and their cross-disciplinary counterparts work together more effectively using RISA. By implementing these strategies, you can reduce errors, improve data consistency, and deliver projects that meet all performance and regulatory requirements.

Understanding RISA’s Capabilities: A Foundation for Collaboration

Before any cross-disciplinary workflow can succeed, every team member must understand what RISA can and cannot do. RISA offers several integrated products—RISA-3D, RISAFloor, RISAFoundation, RISAConnection, and RISASection—each tailored to specific structural tasks. Knowing these tools allows non-structural disciplines to frame their requests and inputs in ways that align with RISA’s data structure.

Key Modules and Their Collaboration Relevance

  • RISA-3D: General-purpose 3D structural analysis. It supports multiple material types (steel, concrete, timber, aluminum) and can import loads from MEP equipment, snow, wind, and seismic sources. Its flexible load-case management makes it easy to share load combinations with other disciplines.
  • RISAFloor: Designed for lateral and gravity analysis of floor systems. It directly integrates with RISA-3D for combined analysis. Civil teams can use it to coordinate slab edge geometry with site grading.
  • RISAFoundation: For designing footings, mats, and pile caps. Geotechnical engineers can provide soil bearing capacities and settlement criteria that feed directly into foundation models.
  • RISAConnection: For bolted and welded connection design. Steel detailers and fabricators can use the same model to verify connections before shop drawings.
  • RISASection: Custom section builder. Useful when architectural or MEP requirements demand non-standard member shapes.

Hold a kickoff workshop to walk all stakeholders through these modules and their data input/output capabilities. This prevents unrealistic expectations and identifies integration points early.

Establishing Clear Communication Channels

While RISA models serve as a single source of truth for structural data, they are only useful if everyone knows how to access and interpret them. Communication breakdowns are the leading cause of interdisciplinary friction, especially when structural models change without notice.

Use a Common Data Environment (CDE)

Adopt a cloud-based platform such as Autodesk BIM 360 or Trimble Connect to host RISA models, exported files, and shared reports. Ensure that version control is enforced—every update to the RISA model triggers a notification to the wider team. Avoid emailing files; they lead to confusion over which version is current.

Regular Coordination Meetings

Schedule weekly or bi-weekly “model sync” meetings where the structural lead presents the latest RISA model using visualization tools. Invite MEP, architectural, and civil leads to point out potential clashes. For example, an MEP engineer might spot a large duct that conflicts with a transfer beam. By reviewing the model together in a live session, the team can resolve issues before they compound.

Centralized Issue Tracking

Integrate RISA outputs with issue management systems like Jira or BIMcollab. Every time a structural change impacts another discipline, create a tracked item with a clear owner and deadline. This formalizes communication and creates an audit trail.

Integrating Data Across Disciplines

Structural models must accommodate inputs from mechanical (equipment loads), electrical (cable tray loads), civil (roadway surcharges), and geotechnical (soil properties) disciplines. Rather than manually re-entering data, use RISA’s data exchange capabilities to pull information directly from other software.

Load Integration from MEP

MEP engineers typically calculate equipment weights in spreadsheets or within Revit MEP. Using RISA’s Excel import function, you can map those load values to specific nodes or members in your RISA model. Automate this with a simple script that reads the MEP load schedule and updates the model. This eliminates manual transcription errors and ensures load updates are reflected immediately.

Civil and Geotechnical Data

Civil engineers often produce ground surface models in AutoCAD Civil 3D or MicroStation. Export those as DXF or LandXML and import them into RISAFoundation to automatically adjust footing elevations and soil spring stiffness. For geotechnical parameters, create a shared template with standard soil layers (fill, sand, clay) and assign allowable bearing capacities. The geotechnical engineer can fill out a simple table that RISA reads via Excel import.

Revit Integration Workflow

For projects using Revit as the central BIM authoring tool, export the Revit structural model to RISA-3D via the RISA-Revit Link or by using IFC. Ensure that Revit elements are mapped to RISA’s member definitions (e.g., beam, column, brace). After analysis, push design results (member sizes, reactions) back to Revit. This two-way link keeps the architectural and structural models synchronized.

Pro Tip: Use RISA’s “Model Reconciliation” tool to compare the imported model with the current RISA model. This highlights differences in geometry, loads, or member properties, allowing you to accept or reject changes in bulk.

Standardizing Modeling Practices Across Disciplines

When multiple engineers touch the same model, inconsistency is inevitable unless strict standards are enforced. Develop a modeling protocol document that everyone agrees to follow. This is especially important when non-structural team members need to review or modify structural models.

Naming Conventions

Define a consistent naming scheme for all elements: beams (B1, B2…), columns (C1, C2…), braces (BR1…), and load cases (DL, LL, WL, EQ, MEP_Equipment, etc.). Include discipline prefixes where needed (e.g., “MEP_L_Panel_A” for a mechanical load on panel A). Avoid generic names like “Load Case 1.”

Units and Coordinate System

Agree on a project coordinate system (e.g., project north vs. true north) and ensure all imported models align. Use RISA’s “Set Coordinate System” feature to lock the origin. For units, choose a consistent set (kips-ft or kN-m) and enforce it via the model’s unit settings. If civil engineers use meters and structural uses millimeters, coordinate conversions in advance.

Model Organization in RISA

Use layers (groups) in RISA-3D to separate structural elements from non-structural items. For example, create groups for “Steel Framing,” “Concrete Walls,” “MEP Loads,” and “Architectural Grids.” This allows you to filter views for discipline-specific reviews without altering the underlying model.

Using Shared Templates and Libraries

Every project benefits from having a single source of truth for commonly used materials, sections, and load patterns. RISA allows you to create template files (.r3t) that contain all these definitions. Share these templates across the team so that everyone starts from the same baseline.

Material Libraries

Create a project-specific material database that includes steel grades (A992, A572 Gr50), concrete strengths (4 ksi, 6 ksi), reinforcing bars (Grade 60, 420 MPa), and even proprietary composite deck profiles. The geotechnical engineer can supply soil spring stiffness values (k-coefficients) that are added as “spring materials” in the RISA foundation module.

Section Libraries

Standardize on a set of W-shapes, HSS, and channel sizes to avoid unnecessary variation. For concrete buildings, define standard beam/column cross-sections and slab thicknesses. MEP team members may request specific openings or blockouts—add these as “opening” members in RISAFloor using library-based shapes.

Load Combination Templates

Use project-specific load combination templates in RISA. Include all required code combos (ASCE 7, IBC, local codes) as well as serviceability combos for deflection checks that other disciplines care about. For example, the architect needs to know the deflection under live load; share that combination as a named output.

Leveraging RISA’s Interoperability Features

RISA’s strength lies in its ability to exchange data with a wide range of engineering tools. Go beyond basic IFC or DXF—explore the more advanced integrations that save time and reduce manual rework.

Revit Integration

The RISA-Revit Link (available in RISA-3D and RISAFloor) supports two-way sync. Use it to coordinate floor slab openings for MEP risers and to update member sizes after analysis. The link also transfers reaction loads to Revit for foundation design. Ensure both software versions are compatible; check RISA’s official integration documentation for the latest details.

AutoCAD Integration

Export RISA-3D models to AutoCAD DXF for dimensional verification by architects. Better yet, use the AutoCAD plugin included with RISA to directly edit geometry—for example, adjusting column locations to match architectural grids without leaving RISA.

SAP2000 and ETABS Exchange

Sometimes a subcontractor uses SAP2000 for dynamic analysis or ETABS for concrete building design. RISA supports SAP2000 .s2k file import and export. Use this to transfer geometric stiffness and mass for modal analysis results. Similarly, RISA can read and write ETABS .e2k files for slab design and gravity load takedown.

Excel Integration for Custom Workflows

Many non-structural teams prefer to work in Excel. RISA’s “Export to Excel” feature allows you to create custom reports that include member internal forces, reactions, and deflections. You can also import Excel tables to define load cases, member properties, and even node coordinates. This is particularly useful when civil engineers provide boring log data in a spreadsheet—simply map the columns to RISA’s template and import.

Conducting Joint Review Sessions

One of the most effective collaboration techniques is the structured model review. Instead of relying solely on static drawings, use RISA’s real-time visualization and reporting capabilities to walk through the model with all disciplines present.

Setting Up a Review Session

Open the RISA model on a large screen or share it via remote access. Use the “Section Cut” tool to display internal forces at critical locations. For example, show the architectural team the deflected shape under wind load to ensure that cladding gaps are adequate. For MEP, use the “Clash Detection” feature within RISA (or an integrated tool like Navisworks) to identify pipe/duct penetrations through beams or shear walls.

Using Physical Reports

Generate PDF reports from RISA that summarize input assumptions and results. Distribute these before the meeting so everyone can review. During the session, focus on discrepancies between disciplines. For instance, if the electrical team added a heavy transformer on a roof, verify that the structural model includes that point load and that deflections are within limits.

Action Items

End each review with a clear list of modifications, owners, and due dates. Use RISA’s annotation tools to mark up the model directly—add notes to members or nodes indicating required changes. These annotations are visible the next time the model is opened, preventing forgotten tasks.

Documenting and Sharing Best Practices

Knowledge retention is a major challenge in engineering firms. When collaboration workflows are not documented, lessons from one project are lost for the next. Create a live document that evolves with each project.

Collaboration Playbook

Write a concise guide that covers: project setup steps, data exchange protocols, meeting cadence, and troubleshooting common interoperability issues. Include screenshots and examples of RISA model organization. Store this in a shared repository (Confluence, SharePoint) and update it after every major project.

Training Onboarding

New team members should not have to guess how to interact with structural models. Provide hands-on training sessions that cover the basics of RISA’s interface, how to import loads from MEP, and how to run joint reviews. Encourage engineers from other disciplines to attend RISA webinars or internal courses.

Post-Project Debriefs

After project completion, hold a debrief with all engineering disciplines. Discuss what worked and what didn’t in terms of RISA collaboration. Capture concrete suggestions—for example, “We should standardize load combination naming across all RISA models” or “The Revit export loses some member release data; we need to manually verify.” Implement those changes in the playbook.

Additional Strategies for Smooth Collaboration

Beyond the core techniques above, several smaller but impactful practices can prevent friction.

Early Involvement of All Disciplines

Invite non-structural engineers to the initial RISA model setup. When the architecture team sees how their gridlines and floor elevations become the basis of the structural model, they become invested in maintaining consistency. Similarly, MEP engineers can note their preliminary equipment locations so that penetrations are accounted for from day one.

Role Clarity and Delegation

Define who “owns” the master RISA model. Usually, the lead structural engineer is the gatekeeper. Other disciplines can check out copies or work in separate RISA files that are later merged. For example, the foundation engineer might work in RISAFoundation while the superstructure engineer uses RISA-3D, then they combine via the “Combine Models” feature. Clear ownership avoids conflicting edits.

Version Control and Rollback

Use the versioning features built into RISA or your CDE. Before any major change, save a snapshot. If an MEP import inadvertently overwrites existing loads, you can revert. Label versions with dates and a brief description (e.g., “2025-02-18_After_Arch_Grid_Shift”).

Conflict Resolution Protocol

When a clash between structural and MEP elements cannot be resolved in a review meeting, escalate to a structured decision process. Have a pre-agreed hierarchy: first, the structural engineer reduces member size if code allows; second, MEP reroutes; third, the architect adjusts space. RISA’s parametric modeling tools make it easy to test multiple member sizes quickly.

Conclusion: Moving Toward Seamless Interdisciplinary Workflows

Effective collaboration using RISA is not a one-time effort but a continuous practice that improves with each project. By investing time in understanding RISA’s capabilities, standardizing modeling practices, integrating data from other disciplines, and conducting regular joint reviews, structural engineers can transform their role from a solitary designer to a central coordinator. The result is fewer RFIs, shorter design cycles, and higher-quality deliverables that all stakeholders can trust.

Implement the tips outlined in this article one project at a time. Start with the most impactful step—perhaps a joint review session—and build from there. Over time, your team will develop a collaborative culture that makes the most of RISA’s interoperability strengths. For further reading, consult RISA’s technical notes on integration workflows and explore community forums where engineers share their own experiences. The future of engineering is collaborative; RISA is your tool to get there.