SAFE Version 12.2.

0
Release Date: 2010-01-06

SAFE Version 12.2.0 is an update to Versions 12.0.0 and later, 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.
2.
3.
4.
5.
6.

Installation Instructions for SAFE Version 12.2.0

Installation Instructions for License Manager 8.0.5
File Compatibility
Significant Changes from Version 12.0.0
New Features for Version 12.0.0
Notes for Users of SAFE v8 or Earlier

1. Installation Instructions for SAFE Version 12.2.0

SAFE Version 12.2.0 is available as a full installation on DVD and from the ftp. Installing SAFE
Version 12.2.0 will uninstall previous Version 12.0.0 or later, 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 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/
ENT_SAPETBSAF /ENT_SAPSAF/ENT_ETBSAF
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 later database files (*.F2K, *.XLS, and
*.MDB). Note that once you save or run these models in Version 12.2.0, 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.2.0.

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 Release Notes (file ReleaseNotes.PDF) in the SAFE folder and available
by using the Help > Documentation command in SAFE.
Changes from Version 12.1.1 to Version 12.2.0 (issued 01/06/2010)
Enhancements Implemented
Incident 18824 (User Interface): Graphical rotation in 3-D using the mouse has been
enhanced such that rotation will occur about the point on the working plane that is at the
center of the screen.
Incidents 17523 (Modeling): Two defaults that could be unrecognized by the user and may
lead to unconservative results in those cases where they are not valid have been changed:
(1) The default rotational supports at the top of walls and columns above the slab have been
removed. The user can now explicitly assign these as needed. (2) The default to
automatically create a rigid diaphragm constraint at the top of walls and columns above the
slab has been removed. The user can now explicitly request for this to be created. When
requested to be created, it will only rigidly constrain those joints that are all at the same topmost level shorter columns and walls above the slab will not be constrained, thus avoiding
equilibrium problems.
Incident 18598 (Modeling): The Equivalent Frame Method (EFM) has been added as a tool
for designing 2-D reinforced concrete and post-tensioned frames. Standalone 2-D models
can be created, analyzed, and designed independently of the current 3-D slab/mat model.
Additionally, the geometry and basic properties for the 2-D frame can be extracted from a
straight design strip of the 3-D model.
Incidents 17518 et al. (Analysis): Meshing options have been simplified and improved to
create more efficient meshes that use less memory and increase the speed and accuracy of
the analysis and design. Meshing, when requested, is now always performed parallel to the
local axes of each encompassing object. The direction can be changed by rotating the local
axes of the encompassing objects. The localization option has been made more intelligent
and grades the mesh near supports and other point objects. The merge option adjusts the
mesh when possible to avoid unnecessary mesh lines. The default maximum mesh size is
1.2 m or 4 ft, depending on the units in use. Changing the mesh size is the primary control
affecting the overall accuracy of the results. User-defined point objects can be added
anywhere in the model to generate mesh lines or to force localization. The default settings

are to mesh using localization and merging. Models from previous versions will be set to
use localization and merging if localization of any kind had previously been chosen.
Incident 19478 (Analysis): The reported transverse (plate) shear stresses (S13, S23) and
shear forces (V13, V23) have been improved. The previous values were computed from
deformations and showed substantial gradients over the element when the twisting moment
was significant. The new implementation computes the values by equilibrium from moment
gradients. The new values are nearly constant over the element and are in better agreement
with thin-plate theory, where it applies, when twisting moments are significant. 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).
Incidents 17865 et al. (Design): Several improvements to the punching-shear design have
been made, including:
o Automatic detection of interior, edge, and corner locations of the support or load.
The user can over-write the location as desired.
o Removal of rounded corners from non-circular perimeters except for Eurocode
design.
o The effect of moments on the shear stress are now computed as specified for each
different code.
o The effect of slab openings is accounted for automatically.
o Punching shear is no longer calculated where beams and walls intersect the
punching shear perimeter.
o The user can overwrite the effective depth of slab, as well as the size and orientation
of the load or support.
See the Release Notes for more information.
Incidents 19440, 19469 (Design): The effect of post-tensioning is now considered for the
shear design of beams, leading to a more efficient design. Numerous other detailed, codebased improvements have been made to the shear design of beams, with or without posttensioning effects. See the Release Notes for more information.
Incidents 19470, 19471 (Design): The effect of post-tensioning is now considered for the
torsion design of beams, leading to a more efficient design. Numerous other detailed, codebased improvements have been made to the torsion design of beams, with or without posttensioning effects. See the Release Notes for more information.
Incidents 19441, 19472 (Design): The effect of post-tensioning is now considered for
torsion punching-shear design, leading to a more efficient design. Numerous other detailed,
code-based improvements have been made to punching-shear design, with or without posttensioning effects. See the Release Notes for more information.
Incident 20639 (Design): The Singapore National Annex to Eurocode 2 (NA to SS EN
1992-1-1 : 2008) has been implemented for concrete and post-tensioned design using
Eurocode 2-2004.
Incident 20697 (Design): The shear design for Eurocode 2 2004 has been enhanced to
optimized for angle theta in Section 6.2.3 of the code. An optimal value is now used for
any load combination that does not require which torsion design and in which seismic loads
are not present. Theta is conservatively assumed to be 45 degrees for any load combination

that does requires torsion design or that does contain seismic loads. Previously the theta
angle was conservatively assumed to be 45 degrees for all cases.
Incidents 17385, 18119 (Import/Export): Multiple enhancements have been made to the
DXF/DWG import and export:
o Strips and tendons are now imported and exported.
o Grids are now exported to DWG.
o Curved and multilinear lines are now exported as a single poly-line rather than a
series of lines.
o Curved walls are now exported.
o Plan and developed elevation are now exported; previously only 3-D views were
exported.
o Dimension lines are now imported.
See the Release Notes for more information.
Incident 18192 (Import/Export): SAFE can now import a model exported from SAP2000
V14.2.0 or later. In SAP2000, a single elevation is chosen, and all frame and area objects
connected to joints in that plane are exported as follows: (1) Horizontal frame and area
objects in the plane comprise the beam and slab system, and are imported with all properties
and loads; (2) Vertical frame and area objects that extend below the plane are treated as
columns and walls, and are imported with all properties but excluding the loads; and (3)
Vertical frame and area objects that extend above the plane are treated as columns and
walls, and are imported as equivalent loads only. Tendon objects, as well as inclined frame
and area objects, that are present in the SAP2000 model are not imported at the present
time. Linear-static, modal, and response-spectrum load cases are imported, along with their
analysis results if available, in order to represent the effect of the complete structure upon
the slab system.
Other Enhancements as detailed in ReleaseNotes.pdf.

Incidents Resolved
Incident 20573 (User Interface): An Incident was resolved in which using the object-shrink
view option could change area objects by merging together points in the object that become
too close together in the shrunken view. This would change the model. Only objects with
finely discretized curved edges were affected.
Incident 17628 (Modeling): An incident was resolved in which a beam torsional stiffness
modifier of 0.01 was being applied instead of the intended value of 0.1. This property
multiplier applies to all beams in the model.
Incident 17867 (Modeling): An Incident was resolved in which changing a material type
from rebar or tendon to concrete or steel did not change the symmetry type for the material
property (e.g., from uniaxial to isotropic) leading to obviously incorrect analysis results.
The symmetry type was correct for the original material before the material type was
changed.
Incidents 17691 et al. (Modeling): Incidents were resolved in which slab or moment
releases assigned to both sides of a line were not being applied. Releases assigned to just
one side, right or left, were being applied correctly. Now all three cases work correctly.
Incident 18731 (Modeling): An incident was resolved in which the property assigned to a
slab that has been converted from a beam using the Convert Beam to Slab edit command

was incorrect. For older models, the property assigned to slabs should be checked when this
type of editing was used to create them.
Incident 18866 (Modeling): An Incident was resolved in which changes to line spring
properties had no effect, and default values were always being used.
Incidents 17476, 18031 (Loading): Incidents were resolved in which weight modifiers
assigned to slabs and beams were not being applied.
Incident 17496 (Loading): An Incident was resolved in which line loads defined in the
global X direction were being applied in the global Z direction.
Incidents 17604, 18550 (Loading): Incidents were resolved in which a trapezoidal load
assigned to slab area was lost when model was saved.
Incident 18895, 20512 (Loading): Incidents were resolved which distributed line loads
defined over a partial length were being applied as uniform over the full length of the line,
increasing the total load applied.
Incident 19360 (Loading): An Incident was resolved in which a non-uniform line load
would be applied as a uniform line load with magnitude equal to one extreme value of the
non-uniform load. This could be conservative or unconservative.
Incidents 17351 et al. (Analysis): Incidents were resolved in which error messages or
exceptions (runtime errors) could be generated during the creation of the analysis model or
while running the analysis due to memory exhaustion for very large meshes. Memory usage
has been made more efficient, and more informative error messages have been
implemented.
Incidents 17555, 18789 (Analysis): Incidents were resolved that was causing negativemoment regions in the slab to be considered as not cracked for deflection calculations.
Cracked deflection results should be re-evaluated.
Incident 19002 (Analysis): An Incident was resolved in which the sum of individual joint
reactions did not always match the value in the Sum of Reactions table for nonlinear load
cases. This sum of the individual joint reactions was correct.
Incident 17689 (Design): An incident was resolved in which the flexural design of T-beams
was slightly unconservative when there was an axial tension acting in the beam and slightly
conservative when there was an axial compression acting in the beam. The T-beam design
was correct in absence of any significant axial force. The affected design codes were BS
8110-1997, Hong Kong CP-2004, SG CP65-1999, IS 456-2000, and Eurocode 22004. The design of rectangular beams was unaffected by this issue.
Incident 17976 (Design): The program has been modified so that the maximum strip
design-station distance is controlled by the maximum mesh size at the time of analysis. This
was previously based on the maximum mesh size at the time of drawing the strip. In
addition, design stations are now automatically introduced at all points that are explicitly
declared to be meshing points if they are close to the spine of the strip. These two changes
increase the detailed resolution of the design results. Previous results could be
unconservative if peaks were missed due to large initial mesh size.
Incident 19079 (Design): An Incident was resolved in which the concrete punching-shear
capacity was incorrect for the Eurocode 2-2004 design code. The k factor was being
calculated using incorrect units, affecting the computed concrete punching-shear capacity.
Incident 17866 (Import/Export):An Incident was resolved in which vertical distortion loads
imported from SAFE V8 were reversed in sign.
Other minor Incidents as detailed in ReleaseNotes.pdf.

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 momentcurvature 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 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.