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 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 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.
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.
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.
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.
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.
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.
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, 15th 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.
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:
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.
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.
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.
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.
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 18.104.22.168.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.
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.
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.