SAFE Version 12.3.

1
Release Date: 2010-12-16

SAFE Version 12.3.1 is an update to Versions 12.0.0 and later, and is available as a full installation on DVD or from the ftp.

PLEASE READ THIS FILE!

It contains important information that may be more current than what is in the Manuals.

Contents
1. 2. 3. 4. 5. 6. Installation Instructions for SAFE Version 12.3.1 Installation Instructions for License Manager 8.0.5 File Compatibility with Older Versions Significant Changes from Previous Version New Features in SAFE Version 12 Notes for Users of SAFE Version 8 or Earlier

1. Installation Instructions for SAFE Version 12.3.1

SAFE Version 12.3.1 is available as a full installation from DVD or downloaded from the ftp. Installing SAFE Version 12.3.1 will uninstall previous Version 12.0.0 through 12.3.0, if present, but will not uninstall older versions of SAFE (Version 8 and earlier.) The installation instructions are available in three places: The SAFE Installation Card link on the SAFE DVD browser. A printed document included with the program package. In the file SAFE_Install_Instructions.pdf in the root folder of the DVD. The instructions include information about the software protection system used and installation options and instructions. You can choose between a Standalone or Network installation. Silent installation is also available for the Standalone and Workstation installations. Please contact CSI Technical Support if you need further information. A new key driver is available for users who have licenses tied to a USB hardware key. For Standalone installations the new driver is available in the SAFE 12\KeyDriver\ folder. For Network installations the new driver is available in the SAFE 12 Server \License Manager\KeyDriver\ folder. If your key is not recognized, please install the new key driver.

Windows User Account Control (UAC) For recent versions of the Windows operating system (Windows 7, Vista, and XP SP3), User Account Control (UAC) is enabled by default. When UAC is turned on, you must explicitly give permission to any program, such as SAFE or the installer, that wants to use "Administrative" privileges. Any program that tries to use Administrative privileges without your permission will be denied access. Standalone, Server, and Workstation installations for SAFE require "Administrative" privileges to run. When installing SAFE with UAC enabled, you should expect to be prompted to allow the installer access to system folders and the Windows registry. Please allow it to continue so that the installation can complete.

2. Installation Instructions for License Manager 8.0.5

The information in this section does not apply if you are using standalone licenses. For new Network installations, see the System Administrator's Help for more detailed information about the License Manager and the License Manager Administration program WlmAdmin.exe. This installation contains Sentinel RMS License Manager 8.0.5. If you are currently running Version 8.0.5 or higher of SentinelLM you do not need to reinstall License Manager. If you are currently running a version that is older than 8.0.5 then you must install version 8.0.5 or later. Uninstall the older version prior to installing this version. IMPORTANT! All commuter licenses should be checked in before uninstalling the old version. Note that Sentinel RMS License Manager 8.0.5 will recognize older licenses for Computer and Structures products. Please refer to the SAFE Installation Card or the SAFE_Install_Instructions file for information on how to do this. If you are serving licenses on a Windows Vista system, you will need to use Sentinel RMS License Manager 8.1.1, which is available from Computers and Structures, Licensing Department, upon request. This version cannot be locked to a disk ID, but instead requires a computer ID key. Note that version 8.1.1 is only required when the license server is running on Vista. It does not matter what operating system is used to run SAFE. To speed up finding a network license when SAFE is launched, you can do either or both of the following: Create a text file, LEVEL.TXT, and enter the ProgramLevel in a single line. The ProgramLevel should be one of the following: ANY/STANDARD/STANDARDC/STANDARDI/ PT/PTC/PTI Save this file to the folder where SAFE is installed. This file will cause the program to find the license faster. Note that this file will be included when a new license is sent. Create a text file, LMHOST.INI, and enter the network name or static IP address of the machine that is running the License Manager. If you are serving licenses on more than one

machine, enter each name or static IP address on a separate line of text. Save this file to the folder where SAFE is installed. As an alternative to using the LEVEL.TXT file, you can specify the program level as a commandline option. To do this, use the Windows Run command or create a shortcut pointing to SAFE.exe in the installation folder. Add the following text to the command line after SAFE.exe /L ProgramLevel where ProgramLevel is one of the values listed above for the LEVEL.TXT file. Specifying ProgramLevel on the command line will supersede the value in the LEVEL.TXT file. If you experience problems with the license please refer to the appropriate License Trouble Shooting Guide... located in the SAFE program folder.

3. File Compatibility with Older Versions

SAFE v12 can open model files (*.FDB) from older versions of SAFE, as well as import older SAFE V8 text files (*.F2K) and SAFE V12.0.0 and later database files (*.F2K, *.XLS, and *.MDB). Note that once you save or run these models in Version 12.3.1, they will not be usable by older versions of the program, so you may want to save them under a new name after opening or importing them in Version 12.3.1.

4. Significant Changes from Previous Version

Most changes do not affect most users. We have listed significant changes here. For a complete list of changes, please see the Release Notes (file ReleaseNotes.PDF) in the SAFE folder and available by using the Help > Documentation command in SAFE. Changes from Version 12.3.0 to Version 12.3.1 (issued 12/16/2010) Enhancements Implemented Incident 26699 (Analysis): The sign of all results for hyperstatic load cases has been reversed to be consistent with common usage. There has been no change in the magnitude of the results, except as may occur due to the changes under Incident 26700. Hyperstatic load cases calculate the secondary forces due to the support reactions present in another (parent) load case. With the new sign, the primary response can be obtained by subtracting the hyperstatic response from the parent load case. Load combinations containing hyperstatic load cases for models made prior to v12.3.1 should be checked for the correct sign. Similarly, design using these combinations should be re-verified. Incident 27418 (Design): The National Annex to Eurocode 2 has been implemented for Denmark, Finland, Norway, Slovenia, and Sweden for reinforced and post-tensioned concrete design using Eurocode 2-2004. Incident 29711 (Design): The Chinese concrete design code has been updated from GB 50010-2002 to GB 50010-2010. Incident 30046 (Design): The Australian code "AS 3600-2009" has been added for the design of reinforced- and prestressed-concrete beams and slabs.

Other Enhancements as detailed in ReleaseNotes.pdf.

Incidents Resolved Incident 26700 (Analysis): An incident was resolved that fixed a few problems with the results for hyperstatic load cases: (1) The small internal stiffnesses used to stabilize the structure during a hyperstatic analysis were too large in some models, thereby reducing the hyperstatic response. This tended to affect models where large stiffness values were used for supports. (2) Joint reactions and base reactions reported for hyperstatic load cases were and are not meaningful, and are now set to zero. (3) The sign of the results for hyperstatic load cases has been reversed to be consistent with common practice. This latter change is further described under Incident 26699. Incident 27652 (Design): An incident was resolved where the strip design results were incorrect if the area objects included in the strip had rotated local axes. The strip design results for models containing rotated area object local axes should be re-verified. Other results were not affected by this problem. Incident 28680 (Design): An incident was resolved where there were a number of limitations in the implementation of the response-spectrum load cases imported from ETABS: (1) Not all of the loads associated with the additional eccentricity specified in response-spectrum load cases were being exported from ETABS. This has been fixed in ETABS v9.7.2 and is documented in its release under Incident 30570. (2) Some responsespectrum load cases were not being added into automatically generated design load combinations. (3) Strip forces for response-spectrum load cases were reported as zero in the database table output. (4) Load combinations that included response-spectrum cases were not being treated as being double-valued and therefore only showed the maximum values in plots and only used the maximum values in design. The minimum values were not getting used. Incident 30472 (Design): An Incident was resolved in which automated load combinations generated for design for loading code AS 3600-01 had the following issues: (1) For clause AS/NZS 1170.0-02, 4.2.2(g), the scale factor for dead load was taken as 1.0 when it should have been 1.2. This load combination is only present with snow load. (2) For clause AS/NZS 1170.0-02, 4.2.2(d), the load combination 1.2D +/- 1.0 W was not being created because it had been assumed to be included in the combination 1.2D +0.4L +/- 1.0W. The omitted load combination rarely governed. (3) For prestressing design, the initial service load combinations 1.15D + 1.15 PT and 0.8D + 1.15 PT were not being created. The omitted load combinations rarely governed the initial service condition. Incidents 27489, 29277 (Results Display and Output): The reported transverse (plate) shear stresses (S13, S23) and shear forces (V13, V23) have been changed for the slab element. Under previous Incident 19478, the stresses had been changed to be computed from equilibrium with the moment gradients rather than from shearing deformations. While this improved some results, other results became less accurate. As a result, the transverse shear stresses are now reverted to being calculated from shearing deformation. However, the stresses will now be reported as constant over the element to eliminate spurious gradients that were the reason for the previous change. The net result is stresses that are of low order, as expected, but that converge correctly with mesh refinement. There is no substantial change in the results where the twisting moment is small. This change only affects the reported transverse shear values. There is no change to the stiffness of the element, to the

computed deformations, nor to the reported membrane forces, plate moments, and in-plane stresses (S11, S22, S12. Other minor Incidents as detailed in ReleaseNotes.pdf.

5. New Features in SAFE Version 12

For a full list of features, capabilities, and enhancements, please visit the SAFE v12 news page at www.csiberkeley.com/SAFE_news/v12/

6. Notes for Users of SAFE Version 8 or Earlier

Users of SAFE v8 or earlier should be aware of several significant changes in SAFE v12 modeling of slabs for analysis and design: 1. The analytical model is a full three-dimensional model with 6 degrees of freedom at each joint. This allows for consideration of in-plane forces due to post-tensioning and a better model for consideration of lateral-load effects. 2. The slab and beams can be modeled at the right locations vertically with interaction of inplane and bending behavior due to variation in thicknesses and eccentricities. T-beam effects are automatically included when these eccentricities are considered. If no posttensioning is present these vertical offsets can be ignored and the T-beam effect can be explicitly modeled. The program default is to ignore the vertical offsets when no posttensioning is present. 3. The columns and walls are now explicitly included in the analytical model rather than being included as springs. This allows for better modeling of lateral loads. 4. For SAFE v12 it is not necessary to export distortions from ETABS to account for lateral loads. The loads can be exported directly and the columns and walls modeled in SAFE will account for the correct distribution of moments to the slabs. Back-calculation of the loads from the distortions is sensitive to the differences in stiffness modeled in SAFE and ETABS and is no longer needed. 5. Only the thick shell finite element is used in SAFE v12 as it includes shear deformation, which is important for getting the right amount of shear in adjoining beams. 6. As a general mesh is now possible and strips can be arbitrarily placed, only the WoodArmer method is available for obtaining the design moments. The nodal method is discontinued. 7. A general mesh option is available and the rectangular meshing has been considerably improved by use of internal edge constraints. The effects of irregularities are now localized and do not affect the whole mesh.

8. The concept of a Load Pattern is introduced. The Static Load Cases are now simply called Load Cases and can contain one or more scaled Load Patterns. The Load Cases can be of type Static Linear, Static Nonlinear, Modal, or Response Spectrum (when imported from ETABS). The Load Combinations are the usual combinations of the responses from the individually analyzed Load Cases.