Flexible workflow between SAP2000 and VIS

 

Real-world structural projects are rarely static. Geometry changes, new loads are introduced, and design criteria evolve as the project moves from preliminary design to construction documents. In this context, the ability of SAP2000 and VIS to exchange information and intelligently reuse reinforcement becomes a key productivity factor.

The process starts with an initial analysis model in SAP2000, model SAP2000 V1.0. From this model, the engineer exports to VIS:

  • Geometry 
  • Materials 
  • Internal forces 

creating the detailing model “VIS v1.0”. In the VIS v1.0 model, the engineer defines and optimizes the reinforcement: bar layout, diameters, spacing, etc. This represents a significant investment of time and specialized knowledge and should ideally serve as the basis for later project versions.

As the project evolves, the SAP2000 model is updated to version V2.0. In the example, two typical modifications are introduced:

  • Modification of beam geometry – some beams change from 30×50 to 30×70. 
  • Additional loads – on the lower story, a uniformly distributed load of 15 kN/m is added, while keeping the original beam geometry on that story.

These are common modifications in real projects, resulting from architectural revisions, owner requirements, or coordination with other disciplines.

The updated SAP2000 V2.0 model is exported again to VIS, generating the “VIS v2.0 model”, which then contains:

  • The updated geometry 
  • The new internal forces 

 

Step-by-step example

The example illustrates a complete and flexible cycle:

 

SAP2000 V1.0 model → VIS v1.0 model

  Export of geometry, materials and internal forces; definition and optimization of the reinforcement. 

SAP2000 V2.0 model

  Introduction of project modifications (geometry and loads) and new structural analysis. 

SAP2000 V2.0 model → VIS v2.0 model

  Export of the updated geometry and new internal forces. 

VIS v1.0 model → VIS v2.0 model

  Import of the reinforcement solution and verification of code requirements. 

VIS v2.0 model

  Adjustments, if necessary.

 

Reusing reinforcement between VIS versions

The key question is whether all reinforcement defined in the VIS v1.0 model has to be recreated in the VIS v2.0 model. Thanks to VIS interoperability, the answer is no.

In the VIS v2.0 model, the engineer can:

  1. Open the “Import Reinforcing” menu. 
  2. Select the original VIS v1.0 model file. 
  3. Choose which members to consider (in the example, all listed members). 
  4. Allow VIS to associate the “old” reinforcement to the new members as long as the geometry is compatible.

After this process, VIS generates an import report that clearly distinguishes:

Members where reinforcement was successfully imported

These are members whose geometry has not changed between V1.0 and V2.0. Their reinforcement layouts are now reused seamlessly in VIS v2.0. 

Members where reinforcement could not be imported

On the “Errors” tab, VIS lists members whose geometry differs from the original (three members in the example). In these cases, the V1.0 reinforcement cannot be reused directly and must be redesigned.

This mechanism confirms a fundamental principle: whenever the geometry remains unchanged, VIS allows direct reuse of existing reinforcement; when geometry changes, the engineer focuses effort only where it is truly needed.

 

New verification: same geometry, new loads

Reusing reinforcement does not mean skipping verification. Even for members whose geometry remains unchanged, loads and internal forces may have changed, so it is essential to confirm that the reused reinforcement is still adequate.

In the VIS v2.0 model, the engineer uses the “Check” command to verify all imported reinforcement under the new design conditions. In the example, beams on the first story are highlighted where:

  • The geometry has remained unchanged. 
  • Loads have increased due to the new distributed load applied on the lower story.

 

When reviewing these beams in the VIS v2.0 model:

  • The longitudinal reinforcement is identical to that used in the VIS v1.0 model. 
  • However, the new checks show that these beams no longer satisfy the design requirements, failing: 
    • In PMM checks (axial force and bending), and 
    • In shear checks.

This highlights an essential message: reinforcement may be reused, but it must always be rechecked against the updated loads and combinations.

 

To support this review, the engineer activates Demand/Capacity diagrams in VIS, which:

  • Highlight regions along the beam where demand exceeds capacity. 
  • Pinpoint the exact locations that require intervention. 
  • Help focus reinforcement modifications on specific regions, instead of redesigning everything blindly.

For demonstration purposes, the example shows increasing the flexural reinforcement until the PMM requirements are satisfied. In practice, the engineer should also review the shear reinforcement, ensuring full compliance with the applicable design code.

 

When geometry changes: redesign is required

The second scenario covered in the example involves a beam whose geometry has changed, for instance from 30×50 to 30×70. In this case:

  • VIS cannot simply reuse the previous reinforcement layout from VIS v1.0. 
  • The program proposes a fictitious (“dummy”) longitudinal reinforcement layout, automatically generated for the new section and the new internal forces.

 

This automatically generated layout:

  • Does not match the original V1.0 solution. 
  • Serves as a starting point rather than a final design.

 

The engineer must then:

  • Adjust the flexural reinforcement. 
  • Define stirrups so that shear capacity satisfies the new demands.

In summary, when geometry changes, the previously defined reinforcement can no longer be reused. The engineer must redefine it based on the new section and the new internal forces. VIS facilitates this process through its design and checking tools and, if desired, can automatically propose a new reinforcement solution for that beam using the “Design Wizard”.

 

Conclusion

Import reinforcement whenever geometry is compatible and then check and adjust it to meet the new requirements.

This workflow shows that SAP2000 and VIS can share and reuse information between versions, turning previously completed reinforcement detailing work into a reusable asset rather than a one-off effort. The result is a more efficient, more consistent design process, always supported by rigorous structural verification.