Under Construction

Under Construction

When using the foundation support, I am required to give the subgrade modulus and supply a direction. I have always used Y as the direction. However, I am interested in knowing what would occur if I choose Y-only. Is there some type of weak spring placed in X & Z directions, is it completely restrained, or is it somewhere in between?

If X or Y or Z is specified for direction, then,

a) a spring support is generated in that direction 
b) the other two translational directions are fully restrained
c) the associated rotational degre of freedom is fully restrained
d) the other 2 rotational degrees of freedom are treated as unrestrained

Example :

plate-list PLATE MAT DIR Y SUBGRADE 0.4

FX is fixed
FY gets a spring
FZ is fixed
MX is free
MY is fixed
MZ is free

If XONLY or YONLY or ZONLY is specified, then, a spring support is generated in that direction. All the remaining 5 degrees of freedom are treated as unrestrained.

Example :

plate-list PLATE MAT DIR YONLY SUBGRADE 0.4

FX is free
FY gets a spring
FZ is free
MX is free
MY is free
MZ is free

Overview

RAM Elements can automatically save a single compressed zip archive file including the primary Ram Elements file (.retx), the analysis results (.fem) and any custom sections, materials or other database information required. 

Steps

To do this go to File - Save-as - Browse and choose the .zip format and select the desired file name and location.

Always send such a zip file or a BugReport file when submitting any service request, especially when the file includes custom data. 

See Also

[[Creating a Bug Report]]

The following article will provides steps for creating a bug report that is useful for troubleshooting purposes.

Background

When troubleshooting a program issue, additional information about the computer, operating system, and installation of the program can be quite useful for determining a cause. RAM Elements and RAM Connection both provide a utility called Create Bug Report which compiles this information. The next section provides two ways for running this utility.

Steps to Accomplish

Option 1: Run "Create Bug Report" directly

1. Select from the Windows Start menu one of the following selections depending on the program:
   All Programs -> Bentley Engineering -> RAM Elements -> Create Bug Report
   All Programs -> Bentley Engineering -> RAM Connection -> Create Bug Report
   

2. A window will appear. Optionally enter a description of the problem encountered. You may also change the location where the report is saved if necessary. By default, it will be saved to the desktop.

3. Click the OK button.
   

4. A dialog will display once the report has been generated. Click the Close button, and close the Create Bug Report utility. The resulting file is saved as BugReport.zip and that can be sent to technical support through a service request or forum post.

    

Option 2: Run "Create Bug Report" from within RAM Elements/Connection

1. From within RAM Elements or RAM Connection, open the menu in the upper left corner, and select "Create bug report" at the very bottom.

   V8i "e" File menu	CONNECT Edition File menu

   
   
   

2. Proceed through steps 2-4 as shown above in Option 1.

See Also

[[Zipping a Model]]

[[SELECTsupport TechNotes and FAQs]]

Release Date: Coming Soon

Version: ISM Revit Plugin CONNECT Edition

Version Number: 10.03.00.08

 
Download Instructions

The ISM Revit Plugin can be downloaded from the Bentley store here. For Bentley SELECT subscribers, the ISM Revit Plugin can be downloaded from Bentley Cloud Services here. After signing in to the CONNECTION Center, select Software Downloads under My Support. Once on the Software Fulfillment page, ISM Revit Plugin installers can be located by performing a search on "ISM Revit".

Special Notices

The installation of ISM Revit Plugin CONNECT Edition will automatically uninstall any previous versions that were installed. This version of ISM Revit Plugin can be run in Revit 2017, 2018, and 2019.

ISM Revit Plugin requires ISM and Structural Synchronizer (both of which are installed with Structural Synchronizer). More information on ISM and Structural Synchronizer can be found here.
 

New Features

The following enhancements were added to ISM Revit Plugin 10.3.

Support for Revit 2019

Support for Autodesk® Revit version 2019 has been added. This release is compatible with Revit 2017, 2018, and 2019, and is no longer compatible with Revit 2016. This release requires Structural Synchronizer CONNECT Edition Update 1 or a later version.

Export of Isolated Foundations

The ISM-Revit Plugin now allows the import of Isolated Foundation (Rectangular Surface Members with only 1 column support) to be imported as the Revit Family- Isolated Foundation as opposed to previously imported Foundation Slab. This enhancement allows easier production of foundation schedules in Revit. The imported rebars are Structural Rebar Objects and can be tagged for drawing production purpose.

Error Corrections

Revit floor/deck span direction not exported to ISM, all decks have R-axis = 1,0,0– Evident in models containing slab with one way floor type other than 0 degrees. (907723).

Repository path field does not reflect the changes done by means other than file picker– Found in Operation Settings page of ISM file input field. (923278).

About ISM Revit Plugin

The ISM Revit Plugin enables a round trip exchange between Revit^® and Bentley’s Integrated Structural Modeling (ISM) format, therefore also enabling a round trip exchange between Revit and any other ISM-enabled application. RAM Structural System, RAM Concept, and STAAD.Pro are examples of applications that are ISM-enabled and can interoperate with Revit with the help of the ISM Revit Plugin.

The ISM Revit Plugin adds commands to Revit that allow ISM repositories to be created and updated from Revit, and allow Revit to create and update ISM repositories. The ISM Revit Plugin is dependent on ISM and thus Structural Synchronizer must be installed on the computer.

Release Date: Coming Soon

Release Name: Structural Synchronizer CONNECT Edition Update 3

Release Version: 10.03.00.18

Download Instructions

Structural Synchronizer can be downloaded at the link here, or from Bentley Cloud Services. After signing into the CONNECTION Center, select Software Downloads under My Support. Once on the Software Fulfillment page, the installer can be located by performing a search on “Structural Synchronizer”.

Special Release Notices

Structural Synchronizer CONNECT Edition Update 3 installs both the Structural Synchronizer application and the Integrated Structural Modeling (ISM) framework. As with Structural Synchronizer 10.01.00.32, this release of Structural Synchronizer creates ISM 6.0 format repositories. There will be no upgrade required to ISM repositories published with Structural Synchronizer 10.01 after installing Structural Synchronizer 10.02. Repositories created with earlier versions of Structural Synchronizer will be upgraded to the ISM 6.0 when making changes to the repository contents.

New Features

This release of Structural Synchronizer includes the enhancements described below.

Improved Node Generation

Improved accuracy of nodes generated via ISM's internal node generation methods.

ProjectWise Integration Improvements

Improve reliability of ProjectWise workflows involving ISM Repositories and publishing of iModels. 

Bug Fixes

This release of Structural Synchronizer includes the enhancements described below.

• Update procedure. Surface member location shown as null. (808094).
• Status bar shows "Path" instead of proper title for different project types (930318).
• Cannot publish iModel files from ProjectWise (936282).

RAM Structural System CONNECT Edition Update 11 Release 15.11 Release Notes

Released Date: October 4, 2018

This document contains important information regarding changes to the RAM Structural System. It is important that all users are aware of these changes. Please distribute these Release Notes and make them available to all users of the RAM Structural System.

Occasionally last-minute changes or corrections are not included in these release notes. Updated release notes can be found at:

     https://communities.bentley.com and search for “v15.11”.

RAM Structural System CONNECT Edition Update 10 Release 15.10.

In order to avoid confusion between “Release 15.01” and “Release 15.10”, both internally in the program and externally with users, there is no version Release 15.10.

Bentley CONNECT:

Bentley is in the process of requiring all users to sign-in in order to use any Bentley programs. This is being done now in anticipation of the implementation of powerful and customized features intended to better help users perform their jobs. Moving to this sign-in requirement now better facilitates our implementing those new features.

If you do not already have a Bentley ID, go to http://www.bentley.com/profile and select the Sign Up Now link.

Bentley CONNECT already offers several benefits, and the value continues to increase. Listed here are three key features:

CONNECT Advisor

CONNECT Advisor provides links to pertinent articles, short training videos, courses and webinars. It can be accessed by selecting the Bentley Cloud Services – CONNECT Advisor command in the RAM Manager, or by selecting the CONNECT Advisor icon from the tool bar in any of the modules.

CONNECTION Center

When you sign in to your Bentley account you now have easy access to CONNECTION Center. This personalized portal gives you access to Usage reports, site configuration information, downloads, and Learning information on webinars, seminars and events, and includes a transcript listing the Bentley courses that you have completed. Your personal portal also lists your recent projects with a portal into analytics on that project. CONNECTION Center can be accessed by selecting the Bentley Cloud Services – CONNECTION Center command or by selecting the Sign In command in the upper right corner of the RAM Manager screen.

CONNECTED Projects

All of Bentley’s CONNECT Edition programs, including RAM Structural System, allow models to be associated with a project. Multiple models, from any of the Bentley products, can be associated with a given project. This simplifies the process of keeping track of work done for a project, and will enable analytics to be performed and reported for the project.

A ProjectWise Projects portal enables you and your project teams to see project details required to evaluate team activity and understand project performance.

• View project activity by site, application and user
• Gain insights into the users who are working on your projects and their effort
• Register and manage your CONNECTED Projects
• Access ProjectWise Connection Services including ProjectWise Project Sharing, ProjectWise Project Performance Dashboards and ProjectWise Issue Resolution Administration

When a model is Saved in this version the program will ask for a Project to which the file is to be associated. Projects can be registered (created) from your Personal Portal, or from the Assign Project dialog by selecting the + Register Project command.

Tutorial:

Except for minor corrections, the Tutorial Manual has not been updated but is still valid. The appearance of some parts of the program in this version may differ from that shown in the Tutorial.

Important Notices:

This version automatically converts databases created in previous versions to the new database format. Note that a backup file is created automatically when a database is converted; the name of the database is the same, with “Orig” and the version number appended to the name. The file has an extension of “.zip” and is located in the same directory as the original database.

The previous steel tables and load combination templates supplied with the program will be replaced with new tables and templates of the same name. If you have customized any Master or Design tables or load combination templates supplied with the program without changing the file names, those file names should be renamed from the original RAM table names prior to installation to prevent your changes from being lost.

Installation Instructions:

If you have enabled the CONNECTION Client you will automatically be notified of the newest version and will be able to update through that service by simply selecting the update command.

Otherwise, this version can be found on the Bentley Software Fulfilment web page by logging into the Personal Portal or the Enterprise Portal and selecting the Software Downloads icon. Perform a search for “RAM Structural System”, select any of the RAM Structural System modules (e.g., RAM Modeler; they all use the same installer), and select the latest version of the RAM Structural System.

Product Licensing FAQ:

Appendix A at the end of these Notes contains a document describing features available in the RAM Structural System to help prevent inadvertent use of unlicensed modules. Refer to that document for more information.

Security Risk Advisory:

Not applicable to this release. Every effort is made to ensure that there are no security risks in the software. There are no known security issues, no issues were addressed in this version.

New Features and Enhancements:

For details on these new features and enhancements, refer to the manual .pdf files available from the Help menu in each module or from the Manuals folder on your hard drive.

AISC Steel Tables

The design tables based on the steel shapes listed in the AISC Steel Construction Manual, 15^th Edition, have been updated. This includes the Master, Beam, and Column tables for both the standard and the SI Equivalent shapes. Changes include new shapes and minor changes to a few geometric dimensions and section property values. Some minor corrections to ordering and grouping were also made. These new tables will replace the existing tables in the program Tables directory but will not automatically replace the tables in existing models; to replace those tables, if desired, use the Criteria – Master Table and Criteria – Design Steel Tables commands in the Manager.

Canada CAN/CSA S16-14 Update

In RAM Steel and RAM Frame Steel Design modules CAN/CSA S16-14 has been implemented as options for the design of steel members. For the member code checks performed by the program the differences between CAN/CSA S16-09 and CAN/CSA S16-14 are nominal.

Data Integrity

In rare cases, model data corruption so serious that the model could not be accessed or recovered was reported. When it occurred it was usually for very large models. The database is composed of many individual model and results files; the way the databases are saved during a Save command has been modified to better protect the essential model files even if there is corruption of the results files. This should result in a significant reduction in the number of cases of file corruption and loss.

SidePlate Connection Updates and Enhancements

Working closely with the engineers at SidePlate, the implementation of the SidePlate connections has been significantly updated and enhanced:

1. New SidePlate connection types have been added. Previously the engineer had the choice of selecting either R = 8 or R = 3. Now the user selects from a list of connection types: Field Bolted SMF, IMF or OMF; Field Welded SMF; or Bolted Moment Frame (R=3).
2. SidePlate has provided updated analysis and design parameters for the values provided with the program previously, resulting in more accurate and economical designs.
3. Ability to model and check biaxial SidePlate connections for square HSS. Rectangular HSS will be implemented in the future. In addition to the biaxial interaction equation, the Strong Column – Weak Beam check is reported for both the Major and Minor axes.
4. The Take-Off report has been updated to list the number of beam end connections as well as the total number of connections. Previously the quantities given for the plate material was approximate, the values are now more precise.

Data Check for Slab Edges

Two new Data Check items have been implemented to report potential problems with slab edges. When modeling slab edges they can be modeled associated with beams or walls, or free-form at any points around the perimeter of the structure. They can be offset from the reference line, or the slab edge can coincide with the reference line (no offset). This generally works very well, but in obscure cases slab edges with offsets in one-way decks that do not precisely align with the intended beam or wall can result in errors in loading. This condition may occur, for example, if a slab edge is laid down by snapping to a snap-point that is very close but not right on the intended beam, or if the framing is reconfigured and moved away from the slab edge. Although in the vast majority of cases these perform properly, the potential for unconservative loads warranted that Data Check items be added to find and warn of these conditions.

The program now checks each slab edge (and slab opening) – if it has an Offset – to see if its reference line aligns precisely with a beam or wall; if not it will give a message “Slab edge is not associated with a beam or wall”, with the coordinates of the slab edge.

Another condition that has been found to work incorrectly in a few obscure cases is a slab edge that spans multiple beams or walls. The program now checks each slab edge (and slab opening) – if it has an Offset – to verify that it starts and ends on the same beam or wall; if not it will give a message “Both ends of slab edge do not reference the same beam or wall”.

It may not be necessary to make any changes, the program may be handling the conditions correctly, but if corrections to the slab edge aren’t made you should verify that the loads on the beams in the vicinity of that slab edge are correct. Best practice when the deck is one-way deck and the slab edges and openings are defined with an Offset is to have the reference lines coincide with beams and walls, and to start and stop each segment on the same beam. Note that in the Modeler the Whole Perimeter command and the In Bay command will automatically correctly do this, and the Add command will automatically correctly break the slab edge into segments for each beam or wall if it is laid down correctly along a line of beams or walls.

Spread Footings with Large Overturning

The algorithms used to optimize spread footing dimensions have been refined, especially for the case of large overturning moments. Previously, some spread footings supporting frame columns were sized larger than necessary; these are now more economically designed.

Data Extractor – Technology Preview

The Data Extractor feature has been completely overhauled. This feature allows the user to extract model geometry, member properties, analysis results, and design information from the model. The extracted data can be saved to an Excel file, Access database, SQLite database, or XML file. It is called using the Post-Processing – Extract Data command in the RAM Manager. This feature is a Technology Preview feature, so it should be used cautiously. Rigorous testing has not been completed, and the feature – including the file formats – are subject to change based on user feedback. Please provide us with any feedback that you have from using the feature so that we can complete the feature to meet your needs. See Appendix B for details on using the Data Extractor.

Error Corrections:

Some program errors have been corrected for this version. Corrections made to graphics, reports, Modeler functions, program crashes, etc., that were considered minor are not listed here. The noteworthy error corrections are listed here in order to notify you that they have been corrected or to assist you in determining the impact of those errors on previous designs. These errors were generally obscure and uncommon, affecting only a very small percentage of models, or had no impact on the results. The errors, when they occurred, were generally quite obvious. However, if there is any question, it may be advisable to reanalyze previous models to determine the impact, if any. In each case the error only occurred for the precise conditions indicated. Those errors that may have resulted in un-conservative designs are shown with an asterisk. We apologize for any inconvenience this may cause.

RAM Manager

CONVERTED MODELS: Models older than v14.05 may have had their column data corrupted when converted to a newer version.

Effect: When it occurred, the model could not be opened.

RAM Steel Beam

ASSIGNED SIZED IGNORED: User-assigned beam sizes on stories other than the topmost occurrence of a typical floor layout were overridden by an optimized size during the Design All process.

Effect: When user sizes were assigned to the topmost occurrence of a typical floor layout type and a Design All command then performed, the user assigned size was respected. However, if the size assignment was made to a beam at any occurrence of that typical floor layout other than the topmost occurrence, the Design All process overrode the assigned beam size with the optimized beam size for all stories with that layout type.

CSA/CAN S16-09 HSS SHEAR CAPACITY*: The shear capacity for a Rectangular HSS was incorrect.

Effect: In calculating the shear capacity of a Rectangular HSS, the depth of the shear plane should have been reduced by 4 times the thickness of the web rather than 2 times the web thickness. A less conservative shear capacity was reported. For designs governed by shear, a member may have passed the shear check when it should have been failed.

CAN/CSA S16-09 CLASS 4 HSS: The flexural capacity calculated for Class 4 HSS sections designed according to CAN S16-09 was incorrect

Effect: The design and reported flexural capacity for Class 4 HSS was incorrect. The reported capacity was conservative. Designs which should have otherwise passed, may have been reported as failed.

RAM Steel Column

CSA/CAN S16-09 HSS SHEAR CAPACITY *: The shear capacity for a Rectangular HSS was incorrect.

Effect: In calculating the shear capacity of a Rectangular HSS, the depth of the shear plane should have been reduced by 4 times the thickness of the web rather than 2 times the web thickness. A less conservative shear capacity was reported. For designs governed by shear, a member may have passed the shear check when it should have been failed.

CAN S16-09 AXIAL CAPACITY: The reported axial capacity according to CAN S16-09 was incorrect when members were uniaxially loaded in flexure. The reported axial ratio may also have been incorrect.

Effect: While members were correctly designed according to CAN S16-09, the reported axial capacity and ratio may have been incorrect for members under uniaxial bending loads. The critical axial ratio may have been incorrectly reported. Crx or Cry may have been reported rather than Cr, the governing capacity. This was a report error only.

CAN/CSA S16-09 CLASS 4 HSS: The flexural capacity calculated for Class 4 HSS sections designed according to CAN S16-09 was incorrect

Effect: The design and reported flexural capacity for Class 4 HSS was incorrect. The reported capacity was conservative. Designs which should have otherwise passed, may have been reported as failed.

RAM Concrete Analysis

ASSIGN – COLUMNS – EFFECTIVE LENGTH: When trying to assign Column Effective Length (K factor), an unsupported operation message would be displayed.

Effect: Concrete Column K factor values could not assigned or changed.

RAM Concrete Column

ACI 318-14 SLENDER COLUMNS: When determining amplified moments per ACI 318-14 6.6.4.5.4 for slender columns, the program considered the minimum moment in each axis simultaneously. The code specifies that the minimum should be considered separately for each axis.

Effect: This was unduly conservative.

ACI 318-08 SMF JOINT CHECK: The SMF joint code check report referenced ACI 318-99 in the controlling code section rather than ACI 318-08.

Effect: When ACI 318-08 was the design code, the SMF joint check design was correct but the references given were from ACI 318-99.

RAM Concrete Shearwall

SHEAR CAPACITY*: When a horizontal bar layout was modified in View/Update, the shear capacity calculation was based on the original assigned bar pattern rather than the updated bar sizes.

Effect: Shear capacity was incorrect.

RAM Frame – Analysis

WALL RIGID LINKS AT BEAM-TO-WALL LOCATIONS*: If the option "Include Rigid Link at Fixed Beam-to-Wall Locations" is selected and if certain conditions are met, it enforces wall rigid links at locations of beams framing into wall. The program mistakenly applied the same condition even for walls sitting on beams. In this case, it enforces wall rigid links for walls sitting on beam.

Effect: Analysis results are not valid if the option is selected and if the model includes lateral walls sitting on lateral beams.

DIAPHRGAM FORCES FOR SLOPED SEMI-RIGID DIAPHRAGM: The program failed to calculate diaphragm forces if diaphragm was sloped.

Effect: The Diaphragm Forces report was not produced if diaphragm force calculation was called for a sloped diaphragm

IS1893-16 RESPONSE SPECTRA LOAD CASE: The program did not allow creation of IS 1893-16 Response Spectra load case.

Effect: The load case was in the list, but would not function; the load case was not available for analysis.

RAM Frame – Shear Wall Forces

WALL SECTION CUTS: Could not create section cuts that started and ended in an opening on a single wall.

Effect: Could not review forces between wall openings and wall edges.

RAM Frame – Steel Standard Provisions

AISC 360-16 DOUBLE ANGLE HORIZONTAL BRACES*: The program crashed when a code check of double angle horizontal braces was performed according to AISC 360-16.

Effect: While all other horizontal brace shapes could be designed according to AISC 360-16, double angle horizontal braces caused the program to crash. The error did not occur when designing per any of the other design codes.

CSA/CAN S16-09 HSS SHEAR CAPACITY *: The shear capacity for a Rectangular HSS was incorrect.

Effect: In calculating the shear capacity of a Rectangular HSS, the depth of the shear plane should have been reduced by 4 times the thickness of the web rather than 2 times the web thickness. A less conservative shear capacity was reported. For designs governed by shear, a member may have passed the shear check when it should have been failed.

CAN S16-09 AXIAL CAPACITY: The reported axial capacity according to CAN S16-09 was incorrect when members were uniaxially loaded in flexure. The reported axial ratio may also have been incorrect.

Effect: While members were correctly designed according to CAN S16-09, the reported axial capacity and ratio may have been incorrect for members under uniaxial bending loads. The critical axial ratio may have been incorrectly reported. Crx or Cry may have been reported rather than Cr, the governing capacity. This was a report error only.

CAN/CSA S16-09 CLASS 4 HSS: The flexural capacity calculated for Class 4 HSS sections designed according to CAN S16-09 was incorrect

Effect: The design and reported flexural capacity for Class 4 HSS was incorrect. The reported capacity was conservative. Designs which should have otherwise passed, may have been reported as failed.

RAM Frame – Steel Seismic Provisions

Emh FOR COLUMN DESIGN*: Column code checks performed according to AISC 341, Section D1.4a were incorrect when beam ends were not modeled exactly at supporting column coordinates or modeled outside the tolerance for detecting supported beams at columns.

Effect: In a rare condition where beam ends were modeled outside the tolerance for detecting members framing into the tops of columns (which could occur, for example, when the members aren’t modeled cleanly in some other program and then imported into the Modeler), code checks incorrectly calculated Emh because the framing beams were not found. The design and report axial loads for columns where the framing beam was not detected was incorrect. When lateral beams were modeled correctly at column supports, the error did not occur and code checks were correctly performed according to AISC 341.

AISC 358 IMF Cpr: When AISC 358 provisions with a specified value of Cpr not equal to 1.1 was specified for the "Other" checkbox selection, reports for Intermediate Moment Frames (IMF) did not correctly show the user specified Cpr value.

Effect: Although IMFs were correctly designed using the user specified Cpr value, the report incorrectly listed a Cpr of 1.1 when the AISC 358 provisions were selected and the specified Cpr was Other (Eg. WUF-W). The defect was a report error only.

RAM Foundation

OVERTURNING SAFETY FACTORS: In some cases the calculated values of the overturning safety factors were incorrect, based on previous iterations of size rather than the final size.

Effect: Report error and unnecessarily conservative design.

OVERTURNING SAFETY FACTOR: In the design criteria of the Foundation module there is an option to consider the moment due to shear (for all three footing types). When calculating the safety factor for overturning, the moment due to shear was considered even if this option was deselected. In addition, when computing this safety factor, the moment due to shear was double counted when the option was selected.

Effect: The overturning safety factor value was incorrect (conservative).

RAM Connection Link

CONVERTED MODELS: RAM Structural System models that had a RAM Connection link file (.rcsx extension) were not keeping that file when converting from version 15.08 to version 15.09.

Effect: File would no longer be in the 15.09 model, but it was still in the backup file created during convert. The file would need to be manually copied from the backup to the new 15.09 files to restore it.

 After analysis , I get the following warning in the output file :

**ERROR** PLATE NO. 2448(JOINTS 2017 - 2088 - 2160 - 2089)

IS BADLY SHAPED, WARPED, NOT CONVEX, OR NOT NUMBERED COUNTER-CLOCKWISE.
 

 Plate element should be modeled using some rules. A plate element’s aspect ratio should be as near to 1:1 as possible. Aspect ratio is defined as the ratio of the length of the shortest side to the longest side of the element. Aspect ratios in excess of 1:4 should be avoided. When assigning nodes to an element in the input data, the nodes must be specified either in clockwise or  counterclockwise order around the perimeter of the element. Kindly find the link to the document which explains the rules for proper modeling of plate elements.

http://communities.bentley.com/products/structural/structural_analysis___design/m/structural_analysis_and_design_gallery/257477.aspx

Problem Description

Structural Synchronizer is installed and the Synchronizer Viewer can be used to view an existing repository, but using Create Repository or New from Repository from any ISM enabled application produces an error such as the one below from Ram Manager (Version 15.08):

Background ISM error ("Could not create ISM interface 5.0")  at Bentley.IsmRssLink.BackgroundIsmStartup.CheckErrorMessage()

   at Bentley.IsmRssLink.BackgroundIsmStartup.CheckShutdown()

   at Bentley.IsmRssLink.BackgroundIsmStartup.get_IsmApi()

   at Bentley.IsmRssLink.IsmData.get_Api()

   at Bentley.IsmRssLink.IsmRssLink._CreateRepository()

With Revit 2017 the error is something similar, but referencing “ISM interface 6.0”

The problem occurs because one of the .dll files installed with Structural Synchronizer Update 2 was not properly "signed" and hence does not get installed correctly on some machines. 

Steps to Resolve

Install version 10.03.00.08 (released October 2018) or later.

See Also

[[Error - Could not start a responsive Engine]]
[[RAM Manager Crashes when using ISM - New From Repository]]

Problem Description

When trying to access Connection design within STAAD.pro SELECT Series 6, you may be stopped with an error, No license for Ram Connection is available. Only simple Beam-Column connections available for usage."

Solution

STAAD.Pro CONNECT Edition 

Once you start the software, you will find the following License Configuration set up in bottom right-hand corner. Check the box for RAM Connection. 

You will get a warning message about 'Additional License Selected:" informing you that if you do not own a license of RAM Connection, you will incur a over-usage bill later. Select yes if you agree with it. 

STAAD.Pro V8i SS6

From inside the start-up page of STAAD.Pro, on the License Configuration, check the box for RAM Connection as shown here. 

You will get a warning message about "Additional License Selected"; this informs you that if you do not own a license of RAM Connection, you will incur a over-usage bill later.

Select 'Yes' if you own a license for RAM Connection or you are okay with the charge.

Now, go to the Misc. Options tab, make sure the box for "Use Ram Connection Product License" is checked if you have selected 'yes' in the last warning message.

P.S. There have been few cases, where the license selection in License Configuration has not saved the selection. Try un-checking / re-checking it. Then go to the Misc. Options and check the box for 'Use RAM Connection License" and clicking Apply followed by Accept. If the information is not getting saved and it has remained checked ; uninstall STAAD.Pro and reinstall it with full administrative privileges (right-click on the installation file and select the option "Run as administrator", though you are logged in as the administrator). Now go to the configuration, uncheck the box, click on apply and then re-check it , click on apply, followed by accept. Now RAM Connection should work fine.

See Also

Error getting a RAM Connection License

Tips for Using RAM Connection within STAAD.Pro [TN].

[[How do I prevent access to the RAM Connection tab within STAAD.Pro?]]

Problem

Missing or incorrect loads on perimeter beams, or excessive loads on the first interior beams.

Explanation

Since the advent of free form slab edges in RAM Structural System, there have been a some framing and slab edge configurations that can lead to missing gravity loads on the perimeter beams, and usually some excessive load on the next interior beams.

In the image below, the slab edge is very slightly skewed to the perimeter beam, and crosses it at one point. Consequently beam 8 is assumed to be outside of the slab edge and will not receive loads from the one-way deck. beam 14 receives all the load from the deck west of it instead.

Another situation that can cause problems is a perimeter where the beams perpendicular to the edge all cantilever out but there is no perimeter member between the cantilevers defined. In this case, the cantilevers won't be loaded by the deck as intended and the load will be applied to the supporting girder instead.

Small gaps in the perimeter framing can also cause problems.

Avoidance

The best way to avoid the problem when using one-way decks is to align the slab edge with the perimeter beams and use at least a 1" outboard overhang. Using the Layout - Slab - Slab Edge command with the "Whole Perimeter" option is a fairly reliable way to make sure the deck is aligned to the perimeter framing.

Furthermore, make sure the perimeter framing creates a closed loop around the diaphragm. 

Starting with version 15.11 we enhanced the Ram Modeler - Integrity - Data Check (Gravity) to check for some of these conditions and give warnings when the slab edge is slightly divergent from the associated perimeter framing or set 0" away. See V15.11 Release Notes.

See Also

RAMSS Common Framing Table Errors

[[Failed to Create Slab Edge load Polygons]]

[[Effects of Changing Deck Type]]

Problem

During the framing table process a model may produce a warning indicating:

Warning
---------------------------
Failed to Create Slab Edge Load Polygons for diaphragm # on Layout Type #LayoutName.
Slab edge loads will not be applied to any beams around the perimeter of that diaphragm.Disregard this warning if the slab edge is Two-way deck.

Explanation

In Ram Structural System, during the framing tables process the program calculates the loads from one way decks that are to be applied to all the beams. In order for this to work there needs to be a continuous outer slab edge loop (polygon) with deck filling the slab area. Furthermore, any framed openings inside of that loop need to be closed loops using the slab opening tools. Occasionally users will accidentally model open edges using the slab edge tool, rather than the slab opening tool and this leads to various errors in the program.

In addition to the warning noted above, it might also cause the Steel beam design process to crash for specific beams. 

Avoidance

Always model complete slab edges using the Layout - Slab - Slab Edges tools and openings using the Slab Openings tools.

By default slab openings are true green, while opening edges are an olive green color for clarity, though the pen colors can be changed by the user.

Starting with version 15.11 the Ram Modeler - Integrity - Data Check (Gravity) was enhanced to check for some of these conditions and give warnings when the slab edge is slightly divergent from the associated perimeter framing or set 0" away. See V15.11 Release Notes.

See Also

RAMSS Common Framing Table Errors

[[Missing or incorrect loads on perimeter beams]]

Download the Latest Version of the ISM Revit Plugin

See the release notes located HERE for the features in this version.

What is the ISM Revit Plugin?

Integrated Structural Modeling (ISM) is an interoperability workflow allowing design change management, revision history, and visualization of shared structural information among different specialized applications on the desktop. You can enable Revit Architecture and Revit Structure models to participate in ISM workflows. This enables you to confidently share data from Revit with ISM-enabled structural design and analysis applications such as RAM Structural System, RAM Concept, STAAD.Pro, ProStructures and AECOsim Building Designer using Bentley’s Revit Plugin.

* Requires a full version of Revit. Revit LT does not support 3rd party add-ins. 

Engineering Workflows using Revit and ISM

VIDEO: Designing Rebar in RAM and Documenting in Revit

www.youtube.com/watch

VIDEO: Round Trip Interop Between Revit and RAM Concept (click HERE to view full playlist)

www.youtube.com/watch
 

VIDEO: Creating Spread Footing Schedules in Revit Using an ISM model

communities.bentley.com/.../Creating-Footing-Schedules-in-Revit-from-an-ISM-Mode-_2800_Condensed_2900_-_2800_1280x720_2900_.mp4

TECH TALK: Managing Revisions to Structural Engineering Models Using ISM

www.youtube.com/watch

Related Products

ISM and Structural Synchronizer (required for ISM Revit Plugin)

RAM Concept (structural engineering of structural slabs)

RAM StructuralSystem (structural engineering of multi-story buildings)

Structural Navigator (mobile review of ISM models)

It has been reported that for some users, when starting STAAD.Pro an assembly that should be started, ‘Bentley.SXP.Core’, fails the strong name validation. This prevents use of the Physical Model workflow.

It has been found that there are 3 dlls included in the installation that do not meet the Windows Strong Name convention. If the Windows operating system has been configured to test for the Strong Name convention, then this will prevent the dlls from loading. Typically, a default Windows installation is not set to check for Strong Name convention.

If this is a problem with your installation, please download the attached zip file and extract the included dlls. The zip file includes three dlls which should replace the ones installed by STAAD.Pro in the sub folders of your installation (typically C:\Program Files\Bentley\Engineering\STAAD.Pro CONNECT Edition):-

• Bentley.SXP.Core.dll replace existing files in:
  • …\STAAD\SPPM\Program
  • …\STAAD\RamConnection

• Bentley.Str.Dep.MathExtensions.dll replace existing files in:
  • … \STAAD\SPPM\Program
  • … \STAAD\RCDesigner
  • … \STAAD\SProStaad
  • …\STAAD\RamConnection

• Bentley.Str.Dep.UnitConversions.dll replace existing files in:
  • …\STAAD\SPPM\Program
  • …\STAAD\SProStaad

Note that there are no changes in the content of these files, only the requirements for strong names has been addressed.

communities.bentley.com/.../Updated-dlls.zip

The TechNotes, FAQs and Support solutions cover various topics that pertain to the CONNECT Edition of STAAD.pro, version 21.00.00.57 specifically. 

Release News

New Release STAAD.Pro CONNECT Edition (21.00.00.57)

New Release - STAAD.Pro CONNECT Edition Update 1 (21.00.01.12)

Installation and Licensing

[[User ID Missing from the Output Report]]

[[The .std files are not showing up with the STAAD.Pro CE icon]]

General

[[Error Unhandled Exception when trying to open the editor in STAAD.Pro Connect Edition]]

[[Existing custom steel section databases cannot opened in the STAAD.Pro Connect Edition]]

Exception message reported when startins STAAD.Pro CE

Graphical User Interface 

[[Black Force Diagrams, Fonts or Color Changes]]

[[Run Analysis option is greyed out]]

[[Error when trying to create analytical model from the physical model]]

[[When trying to import an ISM repository into STAAD.Pro, the Run option is grayed out]]

A "Failed to save document" error reported while creating a new model

[[The Parametric Models Fails to Generate Mesh]]

[[Crash when defining beam offsets]]

[[Members/Surfaces cannot be copied unless corresponding nodes are selected]]

Modeling

[[The Latitude parameter(IBC 2012) is being incorrectly set to zero]]

Analysis and Design

[[Unity ratio displayed for only one member when designed as per AISC 360-16]]

See Also

STAAD.Pro Support Solutions

Can I start a model with a template?

A new model created using File - New has all the criteria and defaults set based on the information in the Ramis.ini file, which can be configured using Ram Manager - Tools - Ram Defaults utility. For more on this see: Ram SS Installation FAQ 

Alternatively, you can take any model that you have set up the way you like, delete all the stuff in the model (layouts, grids, stories) and then use that like a template to start new models using File - Save-as. Some users prefer this approach to starting new files based on the defaults utility settings because you can

• Create several templates for different building types, design codes, etc.
• Pre-populate the template models with standard concrete beam and column shapes, common deck and load properties, etc.

See also: Do You Like to Start With a Template?

What is the Working directory?

A RAM Structural System model file (e.g. filename.rss) is literally a Zip file and within any .rss file you should find many component files of the same name with a wide range of extensions including (but not limited to) .b3d, .ram and .uid. These files are extracted from the model file and put into the working directory when opened in RAM Manager (in older versions of the program all of these files were simply saved together in the model directory). In some cases a zip repair utility can be used to open a .rss or .backup file that won't otherwise open.

For this reason the working directory should always be on the local drive and in a place in which the “user” has administrative rights. It’s also important for the user to have the rights to add, modify and delete files in the model directory.

Note: the working directory is set the first time the program is run, to confirm or edit the working directory location go to C:\ProgramData\Bentley\Engineering\RAM Structural System and double click the Ramis.ini file (c:\windows\ramis.ini prior to version 14). This should bring up the Ramis.ini file in Notepad (or other text editor). Look for the line that begins

working=path to working directory.

You can edit this path to the working directory here. Spaces are allowed as are references to mapped drives, but for the reasons mentioned above, a local drive should be used.

Also in the [Directories] section you will find the paths for other installation directories like the Tables folder where the program looks for all the tables and the default reports directory for saved reports.

For more information on the contents of the Ramis.ini file, refer to the RAM Defaults Guide [TN] and the RamSS Installation FAQ. 

Are RAM Structural System models backwards compatible?

Regretfully Ram SS models are not backward compatible. Typically with each major release there are changes in the model data base format. Once models are converted to the new version they can no longer be used in prior versions.

When a model is converted a backup of the original file is automatically created in the same folder with the same name and appended with the original file version, e.g. MyFile_Orig_14_7.zip, in case there is any need to revert to the prior version.

Note, though version 14.06.01 is generally considered a minor release, file conversion from version 14.06.00 is required. See the 14.06.01 Release Notes for details.

When I open a model I get a warning, “This file appears to be currently opened by: User Name…”

If the listed user really is in the file, they need to exit the program normally to release the model so that you can open it (RAM SS models do not allow for concurrent use).

If that user is not currently in the file or unavailable, you should navigate to the directory where the model is saved and look for a file of the same name with the file extension “.usr”. This is a lock file that was created when the user last accessed the model. The .usr file is normally deleted when the model is closed, but if the program terminated irregularly, the file might persist. Simply delete the .usr file and the .rss file can then be opened.

When I open a model I get a warning, “A temporary backup file has been found for this database (path to file), which indicates that the program abnormally terminated…”

If you select the “Most Recent Database” you are telling the program to reload the files from the working directory which should be the same as they were just before the crash. In such cases, we suggest that you immediately use the file – save-as feature to turn this into a new model file.

Clicking “Backup Database” deletes the working files and restores the files from the saved model whenever it was last saved. “Cancel” leaves everything alone. If your not sure when the last save occurred, click cancel and then check the modified date of the model file through an explorer window before returning to pick either option.

Starting with version 14.06 an additional backup file is created for models that crash and are then re-opened. A copy of the rss file with the extension .ssr is created if you reopen a model that is already expanded to the working directory indicating a previous crash or incomplete closure. Like the .backup file, the .ssr file can be renamed with a .rss extension to restore that version of the file.

When I open a model I get a warning, “Could not delete RAM model: filename. Working files in directory \path to working directory\, please use the explorer to delete these files.”

There are two situations where this message might appear. The first is a restriction to the working directory or the model directory. The user needs to have the rights to add, modify and delete files from both locations (preferably administrative rights). See above for more on the working directory.

The second problem is a corrupt or partial model file. If the model file is missing any of the critical component files it will not open correctly and the same message will appear. To investigate, rename the model file, changing the extension form .rss to .zip and double-click it to see what inside. You should see a series of files all with the same name but with a wide range of extensions including (but not limited to) .b3d, .ram and .uid. When a model file does not contain a complete set of component files it is unusable. It is a mystery what causes a file to become this way, but it seems that something must have interrupted the save process. A virus scanner may also be responsible.

At this point the backup file should be used, see below.

When attempting to load a module, I receive a message that a "File already exists" with a db.sdf extension.

The error may be caused by an installation issue with a database component included with RAM Structural System. Removing and reinstalling the component may resolve the issue. To do this, perform the following steps:

1. Open the Control Panel from the Windows Start menu (Windows XP/Vista/7) or Windows Start screen (Windows 8).
2. Open Add or Remove Programs (Windows XP) or Programs and Features (Windows Vista/7/8).
3. If running RAM Structural System 14.06.00 or earlier, remove Microsoft SQL Server 2005 Compact Edition. If running RAM Structural System 14.06.01 or later, remove either Microsoft SQL Server Compact 4.0 or Microsoft SQL Server Compact 4.0 (x64).
4. Locate and open the RAM Structural System installer (e.g. ramm14060100en.exe or ram6414060100en.exe), often stored in the Downloads folder.
5. Click the Install button next to Microsoft SQL Server Compact Edition, and proceed through the installation to restore the component.

In rare cases, we are seeing initial settings for some computers (Windows 10) are causing this issue. If all of the above steps do not resolve the issue, please create a service request ; attach the machine.config file with the service request and give the path of it.

See also [[Unable to find the requested .NET framework data provider]]

Something is wrong with my model file, is there an automatic backup?

Yes, in the directory where the model file is saved, there should be another file of the same name with the extension, “.backup”. Rename this file something.rss (you won’t be able to use the same name of the original model file unless you move or rename it first). The backup file should be a complete version of the model from the previous time it was saved. If your not sure when that was, simply check the modified date.

Note: when backing up your own files, it is only the .rss model file that you need to save. When restoring backup files or old files from a backup CD or tape, make sure the files are not read-only. If you attempt to open a RAM model that is read-only, you will get another warning, “Failed CopyRssFileToWorkingDir:…”, “Failed DeleteRssInWorkingDir:…”, or “File error 2,6”.

How can I reduce the size of my files?

A RAM Structural System model (file.rss) is already a compressed zip file, but the size of that file can become quite large, especially when the analysis and design results are saved with the file. In RAM Manager under the File menu is an option to ZIP the model. When zipping models using that command you will have the opportunity to purge the model of some unnecessary results (which can be regenerated later just by running the file again). The optional results are:

• Include the RAM Frame Wall Forces results
• Include other RAM Frame Analysis results
• Include RAM Concrete Analysis results
• Include the RAM Concrete Column Interaction Surfaces
• Include the RAM Concrete Shear Wall results.

See Also

[[Unable to find the requested .NET framework data provider]]

RAM Defaults Guide [TN]

RAM SS File-Open Troubleshooting [TN]

RAM Table Editing [FAQ]

Ram SS Installation FAQ 

Note:  Version 14.06.01 is now available for download. Instructions for downloading installation files can be found here:

Software Download Instructions 

RAM Frame In-Core Direct Solver

Problem:  Analysis time with the In-Core Direct Solver (selected in RAM Frame - Criteria - General, see figure below) is significantly slower in v14.06 than in earlier versions.

Work Around:  Analyze using the In-Core Direct Sparse Solver.

Resolution:  This issue was resolved in v14.06.01.

RAM Concrete Shear Wall Performance

Problem:  In the 64-bit version, models take a significant amount of time to load into the module. Other operations, like assigning wall groups and running the designs, are significantly slower.

Work Around:  Install the 32-bit version. Note that this can affect integration with RAM Concept. See following web page:

RAM Concept-RAM SS Integration

Resolution:  This issue was resolved in v14.06.01.

Fixed Braces and Calculated Reactions and Story Shears

Problem:  If braces are not pinned, the moment and shears in the brace member is not accounted for in the calculated reactions, frame story shears, and building story shears.

Work Around: None.

Resolution:  This issue was resolved in v14.06.01.

Column and Footing DXF

Problems:  When changing the Color/Layer options in the Footing Schedule tab, a crash occurs. When attempting to create the dxf, an “Error Opening Master Table” error appears:

After clicking Ok and trying to generate the DXF again, a series of “Key Already Present…” errors similar to the one below appears:

After clicking OK to bypass these errors and generate the DXF again, no file is created.

Work Around:  None

Resolution:  This issue was resolved in v14.06.01.

CAN/CSA S16-09 Minimum Composite

Problem:  The S16-09 Specification permits a percent composite as low as 40% when using composite action for the strength requirements, but the program was using a minimum of 50%.

Work Around:  None.

Resolution:  This issue was resolved in v14.06.01.

CAN/CSA S16-09 Modular Ratio, n_s

Problem:  In the calculation of shrinkage deflection the modular ratio n_t is used in S16-01 but the modular ratio n_s is used in S16-09. These values are quite different. The program allows for the user to specify n_t in Criteria – Canada Parameters in the RAM Manager but there is nowhere to specify n_s. The program, without indicating so in the user interface, is using the value specified for n_t for n_s when designing per S16-09.

Work Around:  When designing per S16-09, input the correct value of n_s where n_t is input. Note that S16-09 doesn’t use n_t, so there is no conflict with inputting the one value for the other.

Resolution:  This issue has been resolved in v14.06.01. The program will internally calculate n_s, it will not need to be specified by the user.

Defaults Utility setting for Snow vs. Roof Live load reversed

Problem:  If the option "Consider Snow Loads, Ignore Roof Live Loads" is selected in the default utility, then roof live loads are incorrectly considered and snow loads are ignored in new models. If the option "Consider Roof Live Loads, Ignore Snow Loads" is selected in the default utility, then snow are considered and roof live loads are ignored in new models. In other words, the setting works in reverse.

The selected setting for each model under Criteria - Member Loads works correctly, it is only the default setting for new models that is reversed. 

Resolution:  This issue was resolved in v14.06.01.

ISM - Update Repository Does Not Add New Items

Problem:  When updating an ISM repository from RAM SS, members or properties that were added to the RAM SS file are not added to the repository. This includes new beams, braces or composite beam stud zones to name a few.

Work Around:  This issue was resolved in v14.06.01.

When I try to create a new file, I get an error regarding tables.

Problem: When I try to create a new file, I get the following error:

"The specified Default Castellated Smartbeam Table (ramuk) could not be found, and neither was the table corresponding to the current setting from RAM Defaults (ramuk)."

Solution:

• Go to tools - Ram Defaults Utility (click OK if you get a message)
• Scroll down to Steel Beam defaults
• Double Click Steel Beam Tables options
• Make sure you have a valid selection, then click next and next until done with the tables part.

Note, with version 14.06.00.00 tables now get saved with the file which is a new thing. If you try to convert a model from an older version and the custom tables used with the original file are not present on the PC converting the file you can get similar error.

When I convert a v14.05 file with embedded Concept files, all design strips are missing.

Problem:  Embedded RAM Concept files are deleted during file conversion when v14.05 are opened in RAM Concept for both 32-bit and 64-bit versions. This removes all design strips and any other modified data, like changes made to slab areas or beams, that were saved with the file.

Work Around:   

1. Open the file in v14.06 and convert the file to the new version format.

2. Open Windows Explorer and find the .zip file with "Orig v14.5" at the end of the file name that is automatically created during the conversion process. Double click on the file. Find the embedded .cpt files. The file name will be same as ram model with .cpt###E at the end. Copy the files to the clipboard.

3. In Windows Explorer, navigate to the working directory (C:\Program Data\Bentley\Engineering\RAM Structural
System\Data\Working). Paste the embedded .cpt files from the v14.5 backup into this folder.

4. Launch RAM Concept from RAM Manager.

Resolution:  This issue was resolved in v14.06.01.

See Also

RAM SS V14.06.01 Release Notes

[[SELECTsupport TechNotes and FAQs]]

Problem Description

A COM Surrogate Has Stopped Working error occurs during a process, like opening an existing file or designing concrete columns.

Reason

Virus scan software is preventing one of the program EXE files from executing the command.

Solution

Exclude the RAM Structural System EXEs from virus protection. These file are saved in the Prog folder of the root RAM Structural System program files directory (C:\Program Files\Bentley\Engineering\RAM Structural System\Prog. In the case of concrete column design, other files are saved in C:\Program Files (x86)\Common Files\Bentley\Engineering\BiaxialInteraction

STAAD.Pro CONNECT Edition Update 3 was released on Oct 1st 2018 with lots of new enhancements and features. One important enhancement added in this release is that one can add load cases, combinations directly from within the Physical Modeling interface as opposed to just adding the load groups which was available before. However not all the loads can be generated at this point of time in the physical modeler.

Some of the loading options that are currently NOT handled by the Physical Modeler are

• Load generations like Wind/Seismic/Moving/Snow/Time History etc.
• Dynamic loads like Response Spectrum/Time History
• Automatic generation of Load Combinations
• Generation of REPEAT LOADs

Depending on what type of loading is essential for modeling, user should choose the most appropriate option from the ones listed below

Option 1: User has an existing model with loads (may include dynamic loads), load generations, REPEAT LOADs etc. created using the analytical modeler

Users who used the analytical modeling in STAAD.Pro CE Update 2 or older versions of the product, would be able to open their models in the analytical modeler of STAAD.Pro CE Update 3 and continue working in the new version without any problem. All existing load cases, combinations, load generations, REPEAT LOADs, dynamic load cases will be migrated to the CE Update 3 just fine.  

Option 2: User has used the physical modeler to build the model and has load cases and combinations (no REPEAT LOADs) in it. There are no load generations (wind/ equivalent seismic/moving load etc.) and there are no dynamic loads in the model (like response spectrum/time history)

On opening the model in CE Update 3 physical modeler, user will be presented with the dialog box as shown below to update the model to the new physical modeler file format.

If the update option is chosen, the file format for the physical model would be updated. If the Drop Physical Model option is chosen, then the connection between the analytical and physical model is removed and one can then add and edit the structure and loads in the analytical modeling environment using the GUI or the STAAD Editor. The Cancel option would not update the model and would not open the file in STAAD.Pro CE Update 3.

When the update option is chosen, the loads and combinations would be read into the physical modeler. Any further addition of loads or combinations or modifications to those would have to be handled through the physical modeler only as these options are not going to be available anymore in the analytical modeler. The loading commands would be locked in the input editor inside the analytical modeler and cannot be edited (as seen below)

One should also be aware that once the physical model with loads/combinations are read into the CE Update 3, load generation options, REPEAT LOADs and/or dynamic loads cannot be added to the model henceforth using the analytical modeler. So, if there is a need to add these to the model at a later stage, it would be advisable to either

1. drop the physical model and then proceed with the analytical modeler which supports load generation/dynamic load inputs

OR

2. continue to use the STAAD.Pro CE Update 2 or earlier as in these versions load generations and dynamic loads can be handled through the analytical mode.  

NOTE: When a physical model, created in an older version of the STAAD.Pro CE, is opened in STAAD.Pro CE update 3 after updating the file format, the updated file cannot be opened in older versions of STAAD.Pro unless the physical model is dropped. Hence before updating or dropping the physical model, it is recommended that one makes a backup of the existing physical model files. One can manually do this using Windows Explorer or use the Archive feature in STAAD.Pro to create a STAAD archive (.stz) for the related files.

Option3: User has used physical modeler to build the existing model and the model has REPEAT LOADs and/or load generation (wind/ equivalent seismic/moving load etc.) and/or dynamic loads (response spectrum/time history) in it.

As in option 2, the user would be presented with the option to update or drop. Drop works the same way as mentioned under option 2 above.

If the update option is chosen, the file format will be updated. Any REPEAT LOADs would be removed. Any existing load definitions will be retained in the analytical modeling interface (the .std file), but they will be non-editable and any assignments of those loads from within the Load Case Details will be removed. Any dynamic load cases like Time History or Response Spectrum will also be removed from the file

So, if the existing model has REPEAT LOADs, load generation commands or dynamic loads, it would be advisable to either

1. drop the physical model and then proceed with the analytical modeler which would support all the loading options

OR

2. continue to use the STAAD.Pro CE Update 2 or earlier as in these versions, REPEAT LOADs, load generations and dynamic loads can be handled through the analytical mode.  

Option4: User is creating a new model and considering using the physical modeler

New models created using the physical modeler can have load cases and combinations consisting of any manually created load items available in the physical modeler. The features like REPEAT LOADs, load definition, load generation, automatic load combination generation, dynamic loads, that are available in the analytical modeler, are currently NOT available in the physical modeler.

So, if these options are required to be included, one may consider using one of the following options

1. create an analytical model in STAAD.Pro CE Update 3
2. create a physical model to begin with in STAAD.Pro CE Update 3 and subsequently drop the physical model
3. continue to use the STAAD.Pro CE Update 2 in which one can create the physical model and load groups using the physical modeler while the rest of the loading can be created using the analytical modeler.

It is important to note that all of the loading options are going to available inside the STAAD.Pro physical modeler in the subsequent releases of the STAAD.Pro CE and so all of the workflows suggested above are temporary and aimed at providing the user with guidelines on how to proceed for now, depending on their requirement.