SAFE Version 12.1.

1
Release Date: 2009-03-05

SAFE Version 12.1.1 is an update to Versions 12.0.0 and 12.1.0, and is available as a full
installation from 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. Installation Instructions for SAFE Version 12.1.1

2. Installation Instructions for License Manager 8.0.5
3. File Compatibility
4. Significant Changes from Version 12.0.0
5. New Features for Version 12.0.0
6. Notes for Users of SAFE v8 or Earlier

1. Installation Instructions for SAFE Version 12.1.1

SAFE Version 12.1.1 is available as a full installation on DVD and from the ftp. Installing SAFE
Version 12.1.1 will uninstall Version 12.0.0 or 12.1.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.

When installing the Standalone version on a Vista system with UAC (User Access Controls)
enabled, you should expect to be prompted twice to allow the installation of the following
components: “SAFE 12” and “SafeTrialLicense”. Please allow these to continue so that the
installation can complete.
When installing the Workstation version on a Vista system with UAC enabled, you should expect
to be prompted three times to allow the installation of the following components: “SAFE 12 WS”,
“SafeTrialLicense”, and “Caspol.exe”. Please allow these 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 re-
install 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/PT/STANDARDC/PTC/STANDARDI/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 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
SAFE is installed.

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

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 12.1.0 database files (*.F2K, *.XLS, and
*.MDB). Note that once you save or run these models in Version 12.1.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.1.1.

4. Significant Changes from Version 12.0.0

Most changes do not affect most users. We have listed significant changes here. For a complete list
of changes, please see the separate file ReleaseNotes.PDF in the SAFE folder and available by
using the Help > Documentation command in SAFE.

Changes from Version 12.1.0 to Version 12.1.1 (issued 03/05/2009)

Incidents Resolved
• Incident 17358 (User Interface): An incident was resolved in which using the command
Edit > Add/Edit Tendons > Edit Vertical Profile and changing the displayed span (either by
clicking on the picture or by selecting a new span in the drop-down box) generated an
exception (runtime error). This problem was introduced in Version 12.1.0 and did not affect
Version 12.0.0.
• Incident 17373 (User Interface): An Incident was resolved in which soil supports were also
being applied to wall elements, affecting models having mat foundations and walls. This
problem was introduced in Version 12.1.0 and did not affect Version 12.0.0.

Changes from Version 12.0.0 to Version 12.1.0 (issued 02/25/2009)

Enhancements Implemented
• Incident 16765 (User Interface): A significant enhancement has been implemented that
allows you to specify mixed or consistent dimensional units that are to be used for all input
and output quantities in the program. These units can be set when starting a new model, and
can be changed at any time. Internally, all quantities are stored in either consistent metric or
U.S units. Consistent units are also used when importing or exporting to database tables in
text-file and Access-database format. For all other usage, the user-specified
mixed/consistent units are used.
• Incidents 16580, 16604 (Drafting): A complete DirectX graphics mode has been added for
performing all graphical functions, including drafting, selection, editing, and display of
results. You can switch between Standard and DirectX graphics in the Options menu.
DirectX is faster than Standard graphics for 3-D operations when used on a capable
machine with a better graphics card. Settings are provided to optimize DirectX for your
system. Standard graphics are still the default, and you should use this if your machine does
not utilize the DirectX mode well.
• Incident 16722 (Drafting): Several significant enhancements have been implemented to
increase the ease, speed, and capability of the Architectural Layer import from DXF/DWG
files: (1) A new option to add new entities within existing entities, or to remove existing
 entities and then add new entities. (2) A new option to give the origin, angle, and scale
when importing architectural layers. (3) Generated wall mid-lines now account for existing
lines in the same layer. (4) Mid-line snaps are now turned off when the architectural layer is
turned off. (5) The import of arcs. (6) The import of the CAD circle entity. (7) The import
of text, including TEXT and MTEXT entities.
• Incident 16630 (Modeling): A new feature has been implemented that allows temperature
load assignments to slabs. Temperature loads are specified as changes in temperature. Each
load assignment may include a different temperature change at the top and the bottom of the
slab, resulting in a temperature gradient. Temperature units are also added as part of this
enhancement. When creating the analysis model the specified slab temperature loads are
automatically applied to associated beams. Below the bottom of the slab, the temperature
change in beams is constant at the bottom of slab value. Above the top of the slab, the
temperature change in beams is constant at the top of slab value.
• Incident 16740 (Modeling): The rules for determining the actual section used for beam
analysis and design have been clarified. The actual section used may be different from that
specified by the user, depending on settings chosen by the user and interaction with the slab.
These rules are generally obvious. Details are described in ReleaseNotes.pdf.
• Incident 16725 (Analysis): Long-term and short-term cracked section deflection analysis
now uses stiffness modifiers calculated from moment-curvature relationships. The moment-
curvature relationships account for cracking, creep, shrinkage, and effects of axial loads and
generally follow the procedure given in “Concrete Structures – Stresses and Deformation,”
by A. Ghali, R. Favre, and M. ElBadry. Previously this feature was incomplete.
• Incident 16582 (Design): A new feature has been implemented that allows you to draw
user-defined reinforcement layout anywhere in the model, including specification of region,
bar size, length, cover, etc. Design will then provide the additional reinforcement needed
beyond what you have defined. The Detailer will show the total reinforcement.
• Incident 16643 (Design): Chinese design has been implemented according to codes GB
50010-2004 for concrete structures, JGJ 92-2004 for prestressed concrete structures with
unbonded tendons, and JG 140-2004 for seismic design of prestress concrete structures.
• Incident 16645 (Design): Punching shear design has been enhanced to account for edges
and corners according to the different design codes. Design overwrites for punching-shear
calculation have been implemented for user control. Further details are described in
ReleaseNotes.pdf
• Incidents 16815, 16777 (Design): Middle and column design strips have been completely
separated for reinforce concrete design. Previously all design strips were full-width column
strips with portions simply identified as middle and column. Full-width column strips are
still used for P/T design.
• Incident 16844 (Design): One-way shear design has been implemented for all codes when
using strip-based design. Previously only slab punching shear was being checked.
• Incident 16846 (Design): FEM-based strength design has been enhanced to now consider
the effect of P/T. Previously this effect was not being accounted for. FEM-based design is
an effective alternative to strip-based design where strips cannot be easily or reasonably
defined.
• Other minor enhancements as detailed in ReleaseNotes.pdf.
 Incidents Resolved
• Incident 16750 (Modeling): An Incident was resolved in which the stiffness modifiers
assigned to the slab were not active.
• Incident 17147 (Modeling): An Incident was resolved in which distributed loads applied to
slabs were inadvertently also being applied to supporting walls.
• Incident 16784 (Analysis): An Incident was resolved in which the rectangular meshing, in
certain complicated geometries, would leave very small triangular mesh gaps.
• Incident 16894 (Analysis): An Incident was resolved in which the error message “Cannot
unmarshall callback interface” was generated when running the analysis out-of-process,
either explicitly or automatically for large models.
• Incident 16869, 16887, 17037 (Analysis): Incidents were resolved in which uplift analysis
was unable to run in certain models and instead returned an error message.
• Incident 16911 (Analysis): An Incident was resolved in which pattern-live load in a load
combination was producing incorrect values for range maximum and minimum, and hence
the combination results were incorrect.
• Incident 17103 (Analysis): An Incident was resolved in which the following assignments
were lost or not handled correctly when meshing slabs and beams. For Slabs: property
modifiers and temperature loads. For Beams: property modifiers, end releases, cardinal
points, point loads, and distributed loads.
• Incident 16871 (Design): An Incident was resolved in which the punching shear was not
being checked for loads coming from above, such as in base-mats and footings.
• Incident 17220 (): An Incident was resolved in which the rebar produced for P/T design was
incorrect for Eurocode EC2. The results were usually over-conservative.
• Incident 16578 (Detailing): An Incident was resolved in which the Bill of Quantities was
not correct and did not change with different models.
• Other minor Incidents as detailed in ReleaseNotes.pdf.

5. New Features for Version 12.0.0

SAFE v12 is a completely new program for designing and detailing reinforced and post-tensioned
concrete floor and foundation systems.

For the full list of features and capabilities, please visit the SAFE v12 news page at
www.csiberkeley.com/SAFE_news/v12/
6. Notes for Users of SAFE v8 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 in-
plane and bending behavior due to variation in thicknesses and eccentricities. T-beam
effects are automatically included when these eccentricities are considered. If no post-
tensioning 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 post-
tensioning 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 Wood-
Armer 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.