SAP2000 Version 15.0.

0
Copyright Computers and Structures, Inc., 2011

Release Date: 2011-06-10

SAP2000 Version 15.0.0 is a major upgrade from Version 14.2.4, 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.0.0 Installation Instructions for License Manager 8.4.1 New Features for SAP2000 Version 15 File Compatibility with Older Versions Significant Changes from Versions 14.2.4

1. Installation Instructions for SAP2000 Version 15.0.0

SAP2000 Version 15.0.0 is available electronically as a full installation from a web download, or on DVD by request. Installing SAP2000 Version 15.0.0 will not uninstall older versions of SAP2000. 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 is 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.0.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.0.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.0.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 Versions 14.2.4

Significant changes that have been made from Version 14.2.4 are listed here. 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 V14.2.4 (Released 2010-12-21)
License and Installation Enhancements Implemented Incident 30054 Description Licensing has been changed for SAP2000 v15. There are now four levels: Basic, Plus, Advanced, and Ultimate. Separate module licenses have been removed. The features of the Basic, Plus, and Advanced levels are the same as for v14. The Ultimate level is the same as the Advanced level, but also includes the features from the v14 Offshore and StagedConstruction modules. The v14 Bridge module features are no longer available in SAP2000, but have been moved to product CSiBridge with expanded capabilities.

User Interface and Display Enhancements Implemented Incident 29785 29795 Description A new graphical user interface is implemented using tabbed windows that provide more control over the sizing and placement of the display windows. Menus and toolbars have been updated for the new user interface. Layout and functionality have not been significantly changed. Shortcut keys have been expanded and modified for consistency. The shortcuts can be seen from the menus themselves. User customization of the toolbars is now saved in the SAP2000v15.INI file rather than a separate .TB3 file as before.

Graphics and Drafting Enhancements Implemented Incident 29792 Description DirectX graphics, drafting, modeling, and display have been added in addition to the classical GDI+ graphics, and the previous OpenGL graphics has been removed. DirectX graphics generally provide better hidden-line display and faster 3-D operations, such as rotate and zoom, on systems that have video boards with good DirectX capabilities. For lesser systems, the GDI+ graphics should be used.

Modeling Enhancements Implemented Incident 33756 Description The Bridge Modeler has been removed from SAP2000 v15, and is now available in the companion product CSiBridge v15 with expanded features. As part of this change to SAP2000: Bridge modeling, bridge loading, the bridge scheduler, and bridge design have been removed. Design load types used for bridge design have been removed from load patterns and load cases. The load type "BRIDGE LIVE" has been renamed to "VEHICLE LIVE". Bridge design load combinations have been removed. AASHTO steel frame and concrete frame design have been removed. One-dimensional moving-load analysis has been retained, and is found under the Define menu. This is similar to the previous capabilities of SAP2000 v14 without the bridge modeler. General vehicles can be defined; they have no width, length effects, or code-specific features. Vehicle response components have been removed. Lanes are now called paths and are defined by a sequence of frame objects, with optional eccentricity. Vehicle loading is only applied to the frame objects making up the path. Influence lines can be plotted. Moving load analysis by influence line (moving-load case) and step-by-step (vehicle live load pattern) analysis is available. If a model from SAP2000 version 14 or earlier is opened in SAP2000 v15, and that model contains bridge objects or components, those bridge entities will be retained when possible, but are not accessible in SAP2000 v15. It is strongly recommended instead that such models be imported into CSiBridge so that the data is accessible.

Loading Enhancements Implemented Incident 32351 32354 34724 Description Automated lateral loading has been added according to the ASCE 7-10/IBC 2009 code. This includes wind loads, seismic loads, and response-spectrum functions. Automated lateral loading has been added according to the NBCC 2010 code. This includes wind loads, seismic loads, and response-spectrum functions. Automated Response-Spectrum functions have been implemented for the Italian NTC 2008 code, including the database of seismic parameters based on latitude and longitude or island name.

Analysis Enhancements Implemented Incident 34120 Description CSiLoadOptimizer has been added as a new tool to determine the optimal application of loads, including the tightening of cables, to achieve specified goals in a structure. Any number and types of loads can be applied in a linear static, nonlinear static, or stagedconstruction load case. CSiLoadOptimizer will determine the scale factors on these loads to satisfy the goals. The goals can include response quantities such as displacements or generalized displacements, superstructure forces and moments, member forces or moments, and/or joint reactions. If the number of loads that can be varied is greater than

Incident

Description the number of goals sought, an optimization problem is solved to determine the least cost of the load application; an optimization problem may also include limits, specified as response inequalities, that must be satisfied. If the number of loads that can be varied is the same as the number of goals sought, a determinate problem is solved to determine the unique solution. If the number of load that can be varied is less than the number of goals sought, a best-fit (least-squares) problem is solved to determine the solution with the maximum benefit (smallest error). Iteration is applied as needed to optimize nonlinear response. The final result is a load case that applies the loads optimally to achieve the stated goals. This optimized load case becomes part of the model and can be used like any other load case for further analysis and for design.

Frame Design Enhancements Implemented Incident 14513 Description Steel frame design has been added for Indian code "IS 800:2007". Limit State design has been implemented, including seismic design (Chapter 12). Class 4 (Slender) section design and special provisions for Angle sections are not included. The Singapore National Annex to Eurocode 3 (NA to SS EN 1993-1-2: 2009) has been implemented for steel frame design using Eurocode 3-2005. Steel-frame design has been implemented for the Australian design code "AS 41001998". This covers the analysis methods and checking of members subjected to bending, axial compression, axial tension, and combined actions. Steel frame design using the "Eurocode 3-2005" code has been enhanced to now consider the design of Class 4 cross sections. Steel frame design using the New Zealand code "NZS 3404-1997" has been added. Concrete frame design using the "Hong Kong CP-04" code has been updated to incorporate the 2007 supplement. Steel frame design has been added according to the Canadian code "CSA S16-09". The Eurocode national annexes for Germany have been added for Eurocode 2-2004 concrete frame design and Eurocode 3-2005 steel frame design. The Eurocode national annexes for Portugal have been added for Eurocode 2-2004 concrete frame design and Eurocode 3-2005 steel frame design. The national annex for Eurocode 8-2004 has also been implemented for seismic loading. Concrete frame design has been added according to the Australian code "AS 3600-09".

20666 24495

25340 31733 31932 32869 33016 33886

34262

Results Display and Output Enhancements Implemented Incident 34241 Description Axial stresses in frame objects are now available for graphical display and for output in the database tables. The axial stresses are the S11 components due to axial force plus bi-axial bending moment, and are provided for all load cases except influence-based moving-load cases. Stresses are computed at all critical points in the cross section, plus at the centroid, and these values can be plotted or tabulated for each station along the frame length. For Section Designer and general sections, the stresses are computed at the four corners of the bounding box and at the centroid. Stresses are calculated for the elastic base material, and do not account for modular ratio or the yielding of hinges. Stresses are computed for the section property assigned to the frame object, and do not account for the possibility that the section has been changed during staged construction. The stresses used for design are

Incident

Description computed separately and are not affected by this enhancement.

Loading Incidents Resolved Incident 33123 Description An issue was resolved where the cable diameter used when calculating open structure auto wind loads on cable objects may be incorrect leading to incorrect loads being applied to the cable. The diameter was usually too large, causing the load to be overestimated. An incident has been resolved where the point of application of the user-defined automated quake (seismic) loads on the diaphragm could be incorrect. This only affects the statically applied quake loads of type "User Loads" where the loads were specified to be applied with respect to the center of mass of the diaphragm. The center-of-mass location was approximate and was not being correctly calculated from the assembled mass matrix from analysis. This has been corrected.

34732

Frame Design Incidents Resolved Incident 30638 Description An incident was resolved for steel frame design using the "Eurocode 3-2005" code in which the capacity value Ncr,T was being calculated in N-mm units regardless of the database units of the model. The effect could be conservative or unconservative, depending on the model units. Several minor corrections and improvements have been made to steel frame design using the "Eurocode 3-2005" code in order to better match standard published example problems. The effects of these changes are generally small. However, users should consider re-verifying designs performed with previous versions of the software. (1) The shear areas, Av, for the major and minor directions were previously calculated using standard formulas. Now they are calculated using the detailed formulas of the design code. The previous values tended to be slightly smaller, and hence overconservative. This change could have a small effect on moment capacity as part of moment-shear interaction. (2) The calculation of the tension-capacity value Nu,Rd was missing the factor of 0.9. The effect was under-conservative when this controlled. (3) The value of Chi (for flexural buckling) was previously set to 1.0 when the axial force was less than 4% of the Ncr, as permitted by the code. Now this check has been removed and the calculated value of Chi is always used, even if the axial force is small. The effect is very small. (4) The buckling curve used for welded pipe sections was taken as c or b depending on whether d/t <= 30 or d/t > 30, respectively. Now for welded pipe sections, the buckling curve is taken as c regardless of the value of d/t. The effect is small, but was previously under-conservative. (5) The value of AlphaLT for rolled-I sections was previously being calculated as 0.34 and 0.49 for the cases where h/b <= 2 and h/b > 2, respectively. Now it is taken as 0.21 and 0.34, respectively, for these two cases. The effect is small, but was previously overconservative. (6) The upper limit of 1.0 is now imposed on the value of ChiLT. Previously, without this

30640

Incident

32130

34570

34908

Description limit, the moment capacity for the LTB (lateral torsional buckling) case could be slightly overestimated. The effect is small, but previously under-conservative. (7) The value of ChiLT was previously set to 1.0, and the moment capacity for LTB (lateral torsional buckling) taken as the unreduced value, when the unbraced length was small (represented by LambdaLT < LambdaLT0), as permitted by the code. Now this check has been removed and the calculated value of ChiLT is always used, regardless of whether LambdaLT is less than, equal to, or greater than LambdaLT0. The effect is small. (8) The LTB (lateral torsional buckling) moment capacity was not previously calculated for box sections, as this rarely governs. Now this capacity is calculated for all box sections. The effect is small, but was previously under-conservative. (9) The calculation of Cm was incorrect for certain units, and in some cases could assume a negative value. The effect of this was small, but could be over- or underunconservative. (10) In version 14.2.3, a new check had been introduced to determine if the member was susceptible to torsional deformation. When NcrT < min(Ncry, Ncrz), the member was assumed to be susceptible to torsional deformation and Table B.2 was used, otherwise Table B.1 was used. This check has been changed: now if It < max(Iy, Iz), the member is assumed to be susceptible to torsional deformation and table B.2 is used. The effect is small, but may have been under-conservative for v14.2.3 for certain cases. An incident was resolved where in a particular model file the indexing of steel design data was corrupted. The design was done correctly and was displayed correctly on screen and in the tables, but would show an incorrect frame object name in the design details. This has now been trapped and corrected in the opening of files. A message is given if such corruption of indexing is found. An incident is resolved for steel frame design using code "AS 4100-1998" where the parameter lambda_n as specified in section AS 6.3.3 was incorrectly calculated. The term fy/250 was taken to the fourth root rather than to the square root. This could underestimate lambda_n in the common case where fy is greater than 250 MPa, which would then overestimate the nominal member capacity (Nc) and be under-conservative. An incident was resolved for steel frame design using the Australian code "AS 41001998" in which the compactness criteria for the web of I sections, box, channel, doublechannel, and T-sections could be incorrectly computed for major and minor direction bending. The b/t ratio being checked for the web was actually taken as the b/t for the flange. Here web means the portion of the section that is parallel to the local 2 axis of the member, regardless of the direction of bending. Results were unaffected for compact sections. For non-compact and slender sections, the classification, and hence the moment capacities, could be unconservative in the case where the b/t ratio for the web is larger than that for the flange.

Results Display and Output Incidents Resolved Incident 34828 Description An incident was resolved where, in some rare cases, the request for Section Cut forces would result in a runtime error or cause incorrect results to be reported. The problem was due to an indexing error that could only be triggered if line constraints were present due to incompatible area or solid meshes, and even then it was uncommon. Only user-defined or drawn Section Cut results were affected, no other results were affected. Section cuts that are internally created to calculate bridge forces and stresses for design, display, and output were not affected. This issue affected versions 12.0.1 to 14.2.4.

External Import/Export Incidents Resolved Incident 30642 Description An incident was resolved for the export to SAFE where the wall loads were not being exported when the "Loads from above" option was selected. This had no effect on the results in SAP2000, and was obvious in the model imported to SAFE.