SAP2000 Version 15.1.

0
Copyright Computers and Structures, Inc., 2011

Release Date: 2011-10-27

SAP2000 Version 15.1.0 is an intermediate update to Versions 15.0.0 and 15.0.1, and is distributed electronically by download from the internet.

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. Installation Instructions for SAP2000 Version 15.1.0 Installation Instructions for License Manager 8.4.1 New Features for SAP2000 Version 15 File Compatibility with Older Versions Significant Changes from the Previous Version

1. Installation Instructions for SAP2000 Version 15.1.0

SAP2000 Version 15.1.0 is available electronically as a full installation from a web download, or on DVD by request. Installing SAP2000 Version 15.1.0 will uninstall previous version 15.0.0 or 15.0.1, but will not uninstall versions of SAP2000 prior to v15. The installation instructions are available in three places: By a separate link available on the web download page The SAP2000 Installation Card link on the installation browser In the file SAP2000_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. For more information, please visit wiki page https://wiki.csiberkeley.com/x/nIBa, or contact CSI Technical Support. A key driver is available for users who have licenses tied to a USB hardware key. For Standalone installations the driver is available in the SAP2000 15\KeyDriver\ folder. For Network

installations the driver is available in the SAP2000 15 Server\License Manager\KeyDriver\ folder. If your key is not recognized, please install the 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 SAP2000 or the installer, that wants to use "Administrative" privileges. Any program that tries to use Administrative privileges without your permission will be denied access. The installation of the Standalone, Server, and Workstation configurations for SAP2000 require "Administrative" privileges to run. When installing SAP2000 with UAC enabled, you should expect to be prompted to allow the installer access to system folders and Windows registry. Please allow it to continue so that the installation can complete.

2. Installation Instructions for License Manager 8.4.1

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.4.1. If you are currently running Version 8.4.1 or higher of Sentinel RMS you do not need to reinstall License Manager. If you are currently running a version that is older than 8.4.1 then you must install version 8.4.1 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.4.1 will recognize older licenses for Computer and Structures products. Please refer to the SAP2000_Install_Instructions file for information on how to do this.

To speed up finding a network license when SAP2000 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: BASIC / PLUS / ADVANCED / ULTIMATE / BASICC / PLUSC / ADVANCEDC ULTIMATEC / ADVANCEDI / ULTIMATEI Save this file to the folder where SAP2000 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 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 IP address on a separate line of text. Save this file to the folder where SAP2000 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 SAP2000.exe in the installation folder. Add the following text to the command line after SAP2000.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 SAP2000 program folder.

3. New Features for SAP2000 Version 15.0.0

SAP2000 v15.0.0 was a major new release, and significant new features have been added or enhanced since Version 14. For a full list of features and capabilities, please visit the SAP2000 v15 news page at http://www.csiberkeley.com/sap2000/news-V15.

4. File Compatibility with Older Versions

SAP2000 Version 15.1.0 can open model files (*.SDB) from older versions of SAP2000, as well as import older SAP2000 database files (*.S2K, *.$2K, *.XLS, and *.MDB.) Note that once you save or run these models in Version 15.1.0, they will not be usable by older versions of the program, so you should save them under a new name after opening or importing them in v15.1.0. Models from versions prior to SAP2000 v15 that contain Bridge Modeler data, lanes defined from bridge layout lines, or vehicles with code-dependent features should use product CSiBridge instead of SAP2000. These models can be opened in SAP2000 v15, but not all of the bridge-related data will be accessible or retained, as follows: If bridge objects are detected, you will be asked whether or not you wish to retain Bridge Modeler data. o If Yes, this data will be protected, but will not be accessible within SAP2000. You should import this model into CSiBridge to access the data. o If No, this data will be deleted. If Bridge Modeler data is detected but no bridge objects are found, all Bridge Modeler data will be deleted.

Lanes defined from frames will be retained, but lane-width data will be removed. Lanes defined from bridge layout lines will be deleted. In SAP2000 v15, lanes are now called paths. Code-based standard vehicles will be deleted. General vehicles will be retained, but codebased features, length effects, and width effects will be removed. See the CSi Analysis Reference Manual, chapter Moving Load Analysis, for more information on the features supported in SAP2000 and CSiBridge.

5. Significant Changes from the Previous Version

For a complete list of changes, please see the separate file ReleaseNotes.PDF in the SAP2000 folder and available by using the Help > Documentation command in SAP2000. Note that most changes do not affect most users. Significant Changes from V15.0.1 (Released 2011-08-05)
Modeling Enhancements Implemented Incident 38691 Description The definition of material properties has been enhanced as follows (for additional details, see the file ReleaseNotes.PDF): (1) Code-specified and other pre-defined material properties are now defined in the installed files "CSiMaterialPropertyLibrary*.xml" located in subfolder "Property Libraries" under the SAP2000 installation folder. Additional material property libraries may also be added by the user to this subfolder and/or to subfolder "Property Libraries" under the user settings folder where the "SAP2000v15.ini" file is located. (2) Within each file, properties are grouped under user-defined Regions (e.g., China, Europe, or USA). Within regions, properties are grouped under user-defined Standards (e.g., ASTM A572). Within Standards, individual materials are defined to be of a certain type (concrete, steel, aluminum, cold-formed, rebar, tendon, or other) and identified by a user-defined label called Grade.. (3) When adding a new material to a model in the graphical user interface (GUI), these pre-defined materials may be chosen by Region, type, Standard, and Grade. Once the new material is defined, its properties may be modified by the user. (4) A built-in Region, Standard, and Grade called "User" are also available for each material type. The corresponding properties can be directly edited by the user and do not make use of the pre-defined materials in the property libraries.

Frame Design Enhancements Implemented Incident 30367 Description Chinese design has been updated to the 2010 specifications for seismic load patterns, response-spectrum functions, load combinations, concrete frame design, and the seismic provisions for steel frame design. These enhancements are consistent with the following specifications: GB50011-2010 Code for seismic design of buildings, GB 50010-2010 Code for design of concrete structures, and JGJ 3-2010 Technical specification for concrete structures of tall building. Models from previous versions that are opened in the

Incident

34264

Description current version will have the code specified for the following items changed to Chinese 2010 if it was previously Chinese 2002: seismic load, wind load, response-spectrum functions, concrete frame design code, and steel frame design code. Because of this, results may change to reflect the new code provisions. No changes were actually made to the wind load except for the name. Concrete frame design has been added according to Turkish standard "TS 500-2000", including Seismic Design Code 2007.

External Import/Export Enhancements Implemented Incident 19173 Description Data transfer between SAP2000 v15.1.0 and Revit Structure 2012 is now supported using the same .EXR file format that is used to transfer data between ETABS and Revit Structure. The export from SAP2000 to import a new model into Revit Structure, and the export from Revit Structure to import a new model into SAP2000, are both available. The option to update an existing model in one product with changes made to the model in the other product is not supported in this release like it is for ETABS.

Analysis Incidents Resolved Incident 38427 Description An incident was resolved where cable forces were not being correctly reported for movingload analysis based on influence lines. The influence value was being taken as zero at all but the last load point. In most cases this resulted in zero or a very small response. Stepby-step moving-load analysis was not affected. No other response (displacement, force, or stress) was affected. Only versions 15.0.0 and 15.0.1 were affected.

Frame Design Incidents Resolved Incident 38261 Description An incident was resolved for Eurocode 2-2004 concrete frame design in which the design moment for unbraced members was using the equivalent first-order moment. The equivalent first-order moment should not be used in this case and could result in unconservative results if one of the end moments is zero or near zero. The equivalent first-order moment is now ignored when an unbraced member is detected.