Professional Documents
Culture Documents
I t d ti
Introduction
Introduction to ANSYS
Mechanical
– Training Courses are also available covering the use of other Workbench modules
(e g DesignModeler,
(e.g. DesignModeler Design Exploration,
Exploration etc.)
etc ) .
ANSYS, Inc.
• Developer of ANSYS family of products
• Global Headquarters in Canonsburg, PA - USA (south of Pittsburgh)
– Development and sales offices in U.S. and around the world
– Publicly traded on NASDAQ stock exchange under “ANSS”
– For additional company information as well as descriptions and
schedules for other training courses visit www.ansys.com
• Managing
M i simulation
i l ti data
d t reduces
d engineering
i i costs
t
– Eliminate wasted time looking for prior simulation data
– Enable re-use of existing data
• Managing simulation processes and workflows
– Enables a collaborative environment for distributed simulation
®
11100101100001
01110100101
0101010
ACCESS MANAGEMENT
ANSYS, Inc. Proprietary Release 12.1
© 2010 ANSYS, Inc. All rights reserved. 1-10 January 2010
Introduction
ANSYS EKM - A User Scalable Solution Training Manual
EKM
Work
Knowledge Capture,
EKM Group
es top
Desktop Data Management,
(Single User)
Automated Protect Intellectual
Workflows Property
Organization/Process Maturity
Native Application
pp
Data Integrated Application
† Note,the active ANSYS license dictates what functionality is available to the user. Not all
features listed are covered in this Introductory course.
• Mechanical Application
– The environment for simulation automation and ease of use combined
with the full power of the ANSYS solver technology.
– Formerly called Simulation
• Network licensing capabilities are used for all ANSYS and ANSYS
Workbench products.
• In this example a Static Structural analysis type is selected for the project
schematic.
• From the toolbox the selection can be dragged and dropped onto the
schematic
h ti or simply
i l double
d bl clicked.
li k d
• Notice too each system block is given and alphabetic designation (A,
B, C, etc.).
• R
Refresh
f h required:
i d upstream
t data
d t has
h changed.
h d Need
N d to
t refresh
f h cell
ll (update
( d t will
ill
also refresh the cell).
• Update
p required:
q the data has changed
g and the output
p of the cell must be
regenerated.
• Up to date.
• Input changes pending: cell is locally up to date but may change when the next
update is performed due to upstream changes.
• Directory Structure:
– dpn: this is the design point directory. This
essentially is the state of all parameters for a
particular
ti l analysis.
l i In I the
th case off a single
i l analysis
l i
there will be only one “dp0” directory.
– global: contains subdirectories for each application
in the analysis.
analysis In the example at right the “Mech”
Mech
directory will contain the database, and other
associated files from the Mechanical application.
– SYS: the “SYS” directory will contain subdirectories
for each system type in the project (e.g. Mechanical,
Fluent, CFX, etc.). Each system subdirectory
contains solver specific files. For example the
MECH subdirectory would contain the results file file,
the ds.dat file, solve.out file and so on.
– user_files: contains input files, user macro files etc.
that mayy be associated with a p project.
j
• With the available licenses displayed, the activation and “use order”
can be specified using the up/down arrows.
– 0 = off, 1 = on
– License
Li order
d represents
t the
th preference
f order
d for
f license
li use.