MSC - SuperModel Version 2006 User's Guide

MSC.
SuperModel
Version 2006
User’s Guide
Main Index
Corporate
MSC.Software Corporation
2 MacArthur Place
Santa Ana, CA 92707 USA
Telephone: (800) 345-2078
Fax: (714) 784-4056
Europe
MSC.Software GmbH
Am Moosfeld 13
81829 Munich, Germany
Telephone: (49) (89) 43 19 87 0
Fax: (49) (89) 43 61 71 6
Asia Pacific
MSC.Software Japan Ltd.
Entsuji-Gadelius Building
2-39, Akasaka 5-chome
Minato-ku, Tokyo 107-0052, Japan
Telephone: (81) (3) 3505 0266
Fax: (81) (3) 3505 0914
Worldwide Web
www.mscsoftware.com
Disclaimer
This documentation, as well as the software described in it, is furnished under license and may be used only in accordance
with the terms of such license.
MSC.Software Corporation reserves the right to make changes in specifications and other information contained in this
document without prior notice.
The concepts, methods, and examples presented in this text are for illustrative and educational purposes only, and are not
intended to be exhaustive or to apply to any particular engineering problem or design. MSC.Software Corporation
assumes no liability or responsibility to any person or company for direct or indirect damages resulting from the use of
any information contained herein.
User Documentation: Copyright  2006 MSC.Software Corporation. Printed in U.S.A. All Rights Reserved.
This notice shall be marked on any reproduction of this documentation, in whole or in part. Any reproduction or
distribution of this document, in whole or in part, without the prior written consent of MSC.Software Corporation is
prohibited.
The software described herein may contain certain third-party software that is protected by copyright and licensed from
MSC.Software suppliers.
MSC, MSC/, MSC., MSC.Dytran, MSC.Fatigue, MSC.Marc, MSC.Patran, MSC.Patran Analysis Manager, MSC.Patran
CATXPRES, MSC.Patran FEA, MSC.Patran Laminate Modeler, MSC.Patran Materials, MSC.Patran Thermal, MSC.Patran
Queue Manager and PATRAN are trademarks or registered trademarks of MSC.Software Corporation in the United
States and/or other countries.
NASTRAN is a registered trademark of NASA. PAM-CRASH is a trademark or registered trademark of ESI Group.
SAMCEF is a trademark or registered trademark of Samtech SA. LS-DYNA is a trademark or registered trademark of
Livermore Software Technology Corporation. ANSYS is a registered trademark of SAS IP, Inc., a wholly owned
subsidiary of ANSYS Inc. ABAQUS is a registered trademark of ABAQUS Inc. ACIS is a registered trademark of Spatial
Technology, Inc. CATIA is a registered trademark of Dassault Systemes, SA. EUCLID is a registered trademark of Matra
Datavision Corporation. FLEXlm is a registered trademark of GLOBEtrotter Software, Inc. HPGL is a trademark of
Hewlett Packard. PostScript is a registered trademark of Adobe Systems, Inc. PTC, CADDS and Pro/ENGINEER are
trademarks or registered trademarks of Parametric Technology Corporation or its subsidiaries in the United States and/or
other countries.Unigraphics, Parasolid and I-DEAS are registered trademarks of Electronic Data Systems Corporation or
its subsidiaries in the United States and/or other countries. All other brand names, product names or trademarks belong
to their respective owners.
Main Index
MSC.SuperModel User’s Guide
Contents 3 Options Close
C O N T E N T S
1
Introduction ■ Purpose , 12
■ Overview , 13
■ Key Features , 14
■ User Interface , 16
■ Run-Time Access , 19
2
CAE File ■ Introduction, 22
Management ■ Overview, 23
■ Glossary, 27
■ Frequently Asked Questions, 29
■ Hierarchy, 31
■ Repository and Workspace, 33
■ File Types and States, 35
■ File History and User Access, 40
■ Functions and the User Interface, 42
■ File Manager Customization, 69
3
Modeling and ■ Introduction to Modeling and Simulation, 76
Simulation ■ Element Quick Create, 77
■ Loads Tools, 83
■ Property Data Plots, 122
■ Mass Properties Management, 130
4
Assembly and ■ Introduction to Assembly and Configuration, 158
Configuration ■ Model Merge, 159
■ Configurations, 181
■ Reduced Stiffness and Mass Modeling, 200
Main Index
Contents 4 Options Close
C O N T E N T S
■ Assembly Definition and Analysis, 233

■ Model Unmerge, 252
5
Results ■ Introduction to Results Visualization, 264
Visualization
■ Bar/Spring Forces and Moments, 265
■ Bar End Loads , 275
■ Shear Panel Plots, 284
■ Max/Min Results Sorting, 292
6
SM Tools ■ Introduction to SuperModel Tools, 302
■ Model Contents, 303
■ Multi Hardcopy, 316
■ Results Titles, 331
A
File Manager ■ Outline, 338
Administrator’s
■ Overview, 339
Guide
■ Requirements, 348
■ General Installation, 350
■ NT Installation, 350
■ UNIX Installation, 350
■ General Customization, 359
■ File Manager Functions Customization, 369
■ Function Summary, 374
■ User Interface, 375
■ Copying MSC.SuperModel Installation, 383
Main Index
Sales & Support 5 Options Close
Preface
■ About MSC
■ Technical Support
■ MSC Web Site
■ MSC Institute of Technology
■ MSC Partners
■ Documentation Conventions
■ Permission to Copy and Distribute MSC Documentation
Main Index
About MSC
MSC.Software Corporation is the largest single provider of finite element modeling and
analysis (FEA) solutions to the computer-aided engineering (CAE) market. MSC’s products are
marketed worldwide through offices in the United States, Europe, and Asia Pacific, and are
available for use on systems ranging from PCs to workstations and supercomputers.
Technical Support
If you need help installing or using an MSC product, we encourage you to first refer to the
technical documentation. If you need further assistance, please contact the technical support
center nearest you. See Contacting Technical Support (p. 7) for contact information, and see
Information for Technical Support (p. 6) for information that you should provide to support
personnel.
We can assist you in using product features, checking code errors, program installation, and in
choosing elements, materials, or procedures. We can give both general information on using the
code and advice on specific analyses. If you have concerns about an analysis, we suggest that
you contact us at an early stage.
Technical Support on the World Wide Web

You can also find a wide variety of support resources including application examples, technical
application notes, available training courses and documentation updates at the MSC Support,
Training, and Documentation web page, www.mscsoftware.com/support. See MSC Web Site
(p. 8) for more information.
Information for Technical Support

Please have the following information ready before calling customer support, or include it in
your fax or email. This information will help support personnel assist you efficiently.
Personal Information System Information

First Contact: • Manufacturer (Sun, SGI, IBM, Digital
• Name UNIX, HP)
• Phone number • Model or chip (r10000 for SGI...)
• Email address • OS Version (Solaris 2.5, IRIX 6, AIX...)
• Company name and address • Graphics board (for graphics problems)
Subsequent Contacts:
• RAM (for hardware problems)
• Available disk space (for hardware
• Personal Identification Number (PIN) problems)
Product Information Problem Description
• Name of product you are using • Brief description of the problem
(MSC.Patran, MSC.Mvision, etc.)
• Version number of the product
(V7.5, V8...)
Main Index
Contacting Technical Support

You can contact Support Services by telephone, fax, or email.
Telephone and Fax:
United States Frimley, Camberley

MSC.Patran Support Surrey, United Kingdom
Telephone: 1-800-732-7284 Telephone: (+44) - 1276 - 67 1000
Fax: 714-979-2990 Fax: (+44) - 1276 - 69 1111
MSC.Nastran Support Tokyo, Japan

Telephone: 1-800-336-4858 Telephone: 81 - 3 - 3505 - 0266
Fax: 323-259-4999 Fax: 81 - 3 - 3505 - 0914
Munich, Germany Paris, France

Telephone: (+49) - 89 - 43 19 87 0 Telephone: (+33) - 1 - 69 36 69 36
Fax: (+49) - 89 - 43 61 716 Fax: (+33) - 1 - 69 36 45 17
Rome, Italy Gouda, The Netherlands

Telephone: (+39) - 6 5 91 64 50 Telephone: (+31) - 182 - 543700
Fax: (+39) - 6 5 91 25 05 Fax: (+31) - 182 - 543707
Moscow, Russia Madrid, Spain

Telephone: (+7095) - 236 - 61 - 77 Telephone: (+34) - 915 - 560919
Fax: (+7095) - 232 - 3575 Fax: (+34) - 915 - 567280
Email:
You can email a detailed description of the problem to the e-mail address below that
corresponds to the product you are using. You should receive an acknowledgment that your
message was received, followed by an email from one of our Technical Support Engineers.
MSC.Patran Support mscpatran.support@mscsoftware.com

MSC.Nastran Support mscnastran.support@mscsoftware.com
MSC.Nastran for Windows Support mn4w.support@mscsoftware.com
MSC.Dytran Support mscdytran.support@mscsoftware.com
MSC.Nastran Support mscmvision.support@mscsoftware.com
MSC.Abaqus Support mscabaqus.support@mscsoftware.com
MSC.Aries Support mscaries.support@mscsoftware.com
MSC.Fatigue Support mscfatigue.support@mscsoftware.com
MSC.SuperForge Support mscsuperforge.support@mscsoftware.com
MSC.DropTest Support mscdroptest.support@mscsoftware.com
MSC Institute Course Information msctraining.support@mscsoftware.com
Main Index
MSC Web Site

MSC.Software Corporation’s World Wide Web home page is at www.mscsoftware.com. At our
web site you can:
• Get detailed information on MSC products and services and industry-specific
solutions.
• Visit the MSC Bookstore.
• Download product patches, utilities, and updates for all MSC products.
• Get product-specific support information.
• Review the most recent Technical Application Notes.
• Work through step by step exercises for a variety of engineering problems.
• Obtain the MSC Institute of Technology schedule and course description.
MSC Institute of Technology

The MSC Institute of Technology provides basic and specialized training in the use of MSC’s
MCAE software products, as well as in general analysis subjects such as thermal analysis, finite
element modeling, and fatigue-life prediction. We offer the world’s largest selection of
engineering analysis and design training courses, with more than 50 different courses. More
than 4,500 engineers attend the MSC Institute annually.
The MSC Institute of Technology is located at:
2 MacArthur Place
Santa Ana, CA 92707
Phone: (714) 444-5155, (714) 444-5160
The Institute maintains state-of-the-art classroom facilities and individual computer graphics
laboratories at training centers throughout the US. All of our courses emphasize hands-on
computer laboratory work to facilitate skills development.
Courses can be taught on-site, and can even be customized to meet your business’ specific needs.
We also offer video courses and a specialized instructor’s program.
For detailed course descriptions and schedule information, call (800) 732-7211 or send email to:
msctraining.support@mscsoftware.com.
How to Register
To register for a class, call the Seminar Coordinator in Santa Ana, California at (800) 732-7211,
access the Online Registration Form, or leave a message with the automated message and
information system at (800) 732-7211 ( select MSC Institute Course Information). You can use this
system to register, leave messages, and obtain course information 24 hours a day.
Please be prepared to provide the following information:
• Course name and number.
• Location of the course.
• Your company name, mailing address, and telephone number.
• Payment information.
Main Index
MSC Partners
MSC works in partnership with other internationally respected technology organizations,
including the world’s leading CAD, analysis software, and computer hardware companies.
CAD Partners Hardware Partners

Unigraphics Solutions, Inc. Accel Graphics
Dassault Systemes Adaptec
Parametric Technology Dell
Compaq/Digital
Analysis Partners Cray Research
nCode International Dynamic Pictures
AEA International Hewlett-Packard
SAMCEF IBM
ZONA Technologies Intel
Intergraph
Silicon Graphics
Sun Microsystems, Inc.
Documentation Conventions
This guide uses several font styles to denote computer filenames, system messages, user input,
and other documentation conventions:
• File names appear in monospaced font in a line of text: /usr/netls.
• System messages or prompts also appear in monospaced font and appear on a separate
line:
-r--r--r-- 1 bin bin 40 Nov 2 1991 .pwrshd
• User input appears in bold monospaced font on a separate line:
# openwin -dev /dev/cgtwelve0 defdepth 24
• The “#” command prompt indicates that root or superuser access is required to issue
the command.
• The “%” command prompt signals that a general user can issue the command.
Example Models
Example exercises for creating various models are available from the
MSC.SuperModel training manual. These exercises can help you build
models, merge Submodels and extract Submodels from Supermodels.
Main Index
Permission to Copy and Distribute MSC Documentation

If you wish to make copies of this documentation for distribution to co-workers, complete this
form and send it to MSC.Software Corporation. MSC will grant written permission if the
following conditions are met:
• All copyright notices must be included on all copies.
• Copies may be made only for fellow employees.
• No copies of this manual, or excerpts thereof, will be given to anyone who is not an
employee of the requesting company.
Please complete and mail to MSC.Software Corporation for approval:

2 MacArthur Place
Santa Ana, CA 92707
Name:_____________________________________________________________
Title: ______________________________________________________________
Company: _________________________________________________________
Address:___________________________________________________________
__________________________________________________________________
Telephone:_________________Email: __________________________________
Signature:______________________________ Date: ______________________
Please do not write below this line.

APPROVED: MSC.Software Corporation
Name:_____________________________________________________________
Title: ______________________________________________________________
Signature:______________________________ Date: ______________________
Main Index
➤ ■ Done
➤➤ ➤
Introduction ❚ 1-11 Options
the MSC/SuperModel User’s Manual
1
Introduction
■ Purpose
■ Overview
■ Key Features
■ User Interface
■ Run-Time Access
Main Index
➤ ■ Done
➤➤ ➤
1.1 Purpose
MSC.SuperModel supports the processes typically used in the design of large
structures comprised of multiple components typical of aircraft, automobiles, jet
engines, satellites and launch vehicles. The engineering design and analysis of
these large assembly structures is often conducted at the component level with
multiple project engineers or project teams each responsible for a given
component. In addition to modeling and simulating the performance of each
individual component, the assembled vehicle performance must be verified.
MSC.SuperModel provides an integrated engineering environment that greatly

facilitates the coordination and communication of engineering modeling and
analysis results data among the project teams. MSC.SuperModel is a powerful
CAE process and data management system with engineering tools for advanced
modeling and simulation.
MSC.SuperModel supports significant productivity gains by enabling

simultaneous modeling and simulation of large structures by any number of
engineers. Project engineers or teams are more efficient in modeling and
simulation activities through an integrated engineering environment where
important data such as geometry, materials, loads and components interface
control point are readily available.
The tedious, time consuming responsibility of managing project engineering data

is simplified through the CAE data management capabilities of MSC.SuperModel.
Easy-to-use modeling and simulation tools help engineers represent complex
structures and understand the external environment in which their structure
operates. Advanced analysis results tools help engineers readily understand
structural responses such as internal loads and dynamics.
Main Index
➤ ■ Done
➤➤ ➤
1.2 Overview
MSC.SuperModel is more than just a software package — it’s an engineering
solution. MSC.SuperModel directly addresses the following structural simulation
and analysis challenges:
•Division of engineering labor and model management of large structures

•Management and tracking of varying structural designs
•Simulation of structures with highly varying materials and properties
•Simulation and understanding of the complex loading environment
•Assessment of analysis results
The MSC.SuperModel system is comprised of MSC.Nastran, MSC.Patran and the

MSC.SuperModel module. This tightly integrated system provides solutions for
commonly encountered problems in simulating and analyzing large aerospace
structures.
The MSC.SuperModel module is an umbrella over MSC.Nastran, the aerospace

standard for analysis, and MSC.Patran, thus providing users with superior
Computer Aided Design (CAD) geometry access, meshing and results
postprocessing functionalities. MSC.Nastran is automatically invoked for
structural analysis. Additionally, key aspects of MSC.Nastran, allow users to
represent structural components as self-contained models, are also available
through an easy-to-use graphical user interface.
While MSC.SuperModel operates as an umbrella over MSC.Nastran and

MSC.Patran, it can also serve as the CAE data server to a company’s Product Data
Management (PDM) system.
Main Index
➤ ■ Done
➤➤ ➤
1.3 Key Features

MSC.SuperModel contains three different types of functionalities:
• Modeling and Simulation

• Assembly and Configuration
• File Management
Individually each of these provides immediate customer benefit and as a whole,

coupled with MSC.Nastran and MSC.Patran, they provide an engineering
solution.
MSC.SuperModel offers a suite of Modeling and Simulation tools that aid in the
representation, analysis and results visualization of large, complex structures.
Customer-developed applications are easily integrated with the standard set of
tools delivered with MSC.SuperModel.
These tools include:
•Quick creation of finite elements

•Running loads plots
•Summation of applied loads
•Equivalent load representation
•Property data plots
•Mass property management
•Detailed model information
•Max/min sorting and display of results
•Bar and spring force and moment results displays
•Bar end load calculations, adjusted for adjacent shear panel forces
•Shear panel results display
MSC.SuperModel allows engineers to model and analyze large structures as an

assembly of components. The ability of MSC.SuperModel to assemble component
models in an automated procedure allows project teams to more easily manage
structural modeling tasks. MSC.SuperModel allows engineers to analyze multiple
structural configurations as defined on a single model.
The Assembly and Configuration module includes:
•Reduced stiffness and mass modeling

•Automated analysis of a structure comprised of multiple components
•Multiple design configuration support
•Inventory and recall of previous analysis jobs
•Automated merging of large structural component models
•Extraction of component models and their analysis results from the assembled
structure
Main Index
➤ ■ Done
➤➤ ➤
MSC.SuperModel can help engineers manage their CAE data. The File Manager
uses client-server technology and a large suite of tools to support and maintain
engineering models and associated data files.
The following is a summary of the functionality:
•User-defined hierarchy up to ten levels for managing engineering data by

program, project, engineering discipline, configuration, component, sub-
component, etc.
•Integrated engineering environment where access to common project data such
as geometry, materials and component interface points may be shared among all
engineers at all levels of the hierarchy. If desired, custom templates containing
common data can be configured for different levels in the hierarchy.
•Data access control allows for security measures to be implemented on
engineering data in the File Manager. Limited access is supported. Only one user
at a time is allowed write access to a file while multiple users are allowed to read
the data.
•Automatic history tracking records all file operations. A history file is
automatically associated with each logical file entry in the File Manager. Users
may add their own comments to the history file.
•Logical file constructs allow a grouping of physical file into a single logical file.
File Management operations occur on the logical files; thus, a move or copy
operation would operate on all the physical files associated with the logical file.
•Comprehensive suite of data management tools, including external
communication of data (e.g., to and from UNIX or PDM systems), data
compression, data locking, move/copy, file-type filtering, automatic file-state
recognition.
•A hierarchy contents report may be generated.
•Support across heterogeneous servers and computer systems
Each of the MSC.SuperModel functionalities listed above is described in detail in

the following sections of this manual.
Main Index
➤ ■ Done
➤➤ ➤
1.4 User Interface

The MSC.SuperModel user interface is shown below. You can access
MSC.SuperModel through three locations located on the top menu bar:
1. File Manager pulldown - FM

2. SuperModel Tools pulldown - SM Tools
3. SuperModel application - SuperModel
MSC.SuperModel Version 200x
FM Group Viewport Viewing Display Preferences Tools Insight SM Tools Help
♦ Geometry♦ FEM ♦ LBCs♦ Matls♦ Properties♦ Load Cases♦ Fields♦ Analysis♦ Results♦ Insight ♦ XYPlot♦ SuperModel
$# Session file patran.ses.01 started recording at 25 SuperModel Main Menu

$# Recorded by MSC.Patran 03:36:58 PM
$# NetLS Initialization complete. Acquiring license(s)...
MSC.SuperModel
Version 200x
Main Menu
Modeling and Simulation
Element Quick Create
Loads Tools
Property Data Plots
Mass Property Management
Assembly and Configurations

Configurations
Reduced Stiffness and Mass
Assembly and Analysis
Model Unmerge
Results Visualization
Bar/Spring Force & Moment
Bar End Loads
Shear Panel Plots
Max/Min Results Sorting
Main Index
➤ ■ Done
➤➤ ➤
FM
FM replaces File on the MSC.Patran menu.
SM Tools
SM Tools is a pulldown menu and all functionality under this selection may be
concurrently accessed.
SuperModel
The MSC.SuperModel Main Menu is accessed by selecting the MSC.SuperModel

application (SuperModel ). This menu is replaced by the user interface to the specific
tool selected on the main form (e.g., Reduced Stiffness and Mass). Only one
functionality may be accessed at a time.
Main Index
➤ ■ Done
➤➤ ➤
Reduced Stiff. and Mass

Action: Create
Object: RSM Definition
Method: Manual
Existing RSM Definitions

* Filter
test
RSM Definition Name

test1
RSM Definition Type

◆ Write ◆ Read
DOF List Definition...
Matrices to Create
◆ Stiffness Only
◆Stiffness and Mass
Select Output File...
DOF Axis Mapping
RSM Axis To Model Axis
X Axis to: +X
Y Axis to: +Y
Z Axis to: +Z
-Apply- Cancel
If another application is selected while the MSC.SuperModel Main Menu or

specific functionality accessed from the main menu is open (e.g., Geometry), the
MSC.SuperModel form is closed. After returning to the MSC.SuperModel
application, control is returned to the previously selected MSC.SuperModel
functionality.
Apply and Cancel
The user interface to the selected functionality has an Apply and Cancel button at
the bottom, as illustrated below. Apply causes the desired action to be performed.
Cancel closes the specific tool and returns control to the MSC.SuperModel main
menu.
Main Index
➤ ■ Done
➤➤ ➤
1.5 Run-Time Access

MSC.SuperModel contains three different modules:
•Modeling and Simulation

•Assembly and Configurations
•File Management
Each of these is individually licensed and optionally accessible at run-time.
To enable or disable each module, the following commands can be placed in the
p3smdl_midilog.pcl file.
abu_call_start.start_fm (<logical>)
abu_call_start.start_cae (<logical>)
abu_call_start.start_prepost (<logical>)
where <logical> = TRUE or FALSE
and “start_fm”, “start_cae” and “start_prepost” refer to the File Manager,

Assembly and Configurations, and Modeling and Simulation modules,
respectively.
Main Index
➤ ■ Done
➤➤ ➤
Main Index
➤ ■ Done
➤➤ ➤
CAE File Management ❚ 2-21 Options
2
CAE File Management
■ Introduction
■ Overview
■ Glossary
■ Frequently Asked Questions
■ File Hierarchy
■ File Repository and Workspace
■ File Information and States

■ File History and User Access
■ Functions and the User Interface
■ File Manager Customization
Main Index
➤ ■ Done
➤➤ ➤
2.1 Introduction
File Manager is accessed from the FM pulldown located on the MSC.Patran main
form.
FM Group Viewport Viewing Display Preferences Tools Insight SM Tools
♦ Geometry ♦ FEM ♦ LBCs♦ Matls♦ Properties ♦ Load Cases♦ Fields ♦ Analysis ♦ Results ♦ Insight ♦ XYPlot ♦ SuperModel
$# Session file patran.ses.01 started recording at 25

Fundamental to MSC.SuperModel is its ability to support multiple structural

components and designs. The capabilities of this system support the division of
engineering labor, management of large structural models, and tracking and
configuration control of varying structural designs. At the heart of these
capabilities is the File Manager.
The File Manager addresses CAE process management issues. Engineering data is
stored in a hierarchy customized to the customer’s way of doing business — for
example, by project or engineering discipline. Users are no longer encumbered
with operating system knowledge requirements as the graphical interface is easy
to use, form driven and uses basic text description to locate engineering data. File
Manager includes a security system which allows for limited access to and controls
over engineering model data and project files. A resource manager is available to
maximize storage efficiency through techniques such as file compression and
archival.
Main Index
➤ ■ Done
➤➤ ➤
2.2 Overview
File Manager supports the management of large structural models. Engineering
labor is easily divided through a wide variety of tools that organize, manage and
track various structural designs. File Manager provides a concurrent working
environment for users who must share and exchange engineering information,
without imposing the need for users to know operating systems (e.g., UNIX)
commands.
File Manager functionality represents a departure from the conventional ways that
MSC.Patran users have to manage database, journal, neutral, and result files. This
overview conveys the new philosophy. Additional details are provided in
subsequent sections of each of the File Manager components.
Chapter Overview
The following table displays a brief description of each of the major sections
presented in this chapter.
❏ Introduction Discusses the general architecture of the File Manager and

points out the critical differences between it and working with
the conventional MSC.Patran file interface to UNIX.
❏ Overview Gives general overview of MSC.SuperModel.
❏ Glossary Lists terms used throughout this document to describe the new
features and functions associated with the File Manager.
❏ Frequently Asked Lists Frequently Asked Questions and their respective answers.
Questions This section provides a good starting point if you are uncertain
about some aspect of the File Manager.
❏ File Hierarchy Describes the file system hierarchy levels and branches.
❏ File Repository and Details the mechanism by which concurrent engineering is
Workspace supported in File Manager.
Main Index
➤ ■ Done
➤➤ ➤
❏ File Information and Provides general information regarding how files are identified
States by the File Manager. Describes the default file types that are
supplied with File Manager: what they are, how they are used,
and why they are important. Also discusses the important
concept of File Templates.
Outlines the features of File Manager that assist in managing the
system resources associated with each file in the system.Presents
the different levels of security that each file can be assigned,
including both automated security features and
user/administrator controlled security.
❏ File History and User Describes the File Manager mechanisms for recording file
Access operations and user interactions with the hierarchy.
❏ Functions and the Lists each of the functions available under the File Manager
User Interface menu. Includes a description of the capabilities as well as
hyperlinks to the associated forms used to perform each
operation.
Depicts and describes each of the user interface forms presented
by File Manager. (The Functional Summary section provides
hyperlinks to each of these for easier browsing.)
❏ File Manager Lists the functions and what you can do to customize the file
Customization manager functions.
Technical details have been spared as much as possible from this documentation.
This is intended to help the user become familiar with and fully utilize the features
of the File Manager. For additional information, including: installation,
customization, and trouble shooting, refer to the File Manager Administrator’s Guide
(p. A-337).
Main Index
➤ ■ Done
➤➤ ➤
2.2.1 Files
File Manager offers several features that are intended to relieve the user of many
burdens associated with handling the quantity and size of files associated with
engineering data.
Logical and Physical Files

The File Manager is designed to work with collections of files that might be
required to perform an operation. For example, the MSC.Patran database is
generally accompanied by a journal file. File Manager groups these individual files
into a single logical file. File Manager eliminates the burden of dealing with each
of the physical files and instead presents information only about the logical file. In
general, only the system administrators need to worry about this relationship and
therefore throughout this document we refer to files (always implying a logical
collection of physical files) except when a distinction must be made for clarity.
File Descriptions
Conventional file names have been superseded with file descriptors in File
Manager by more flexible file descriptions. Unlike file names, these may contain
embedded blanks, special characters, and can be up to 80 characters in length. Due
to the graphical interface for browsing the file system as well as the powerful file
filtering capability, cryptic names and file extensions can be eliminated.
File Types
Each of the files in the File Manager has an associated type which helps to identify
its contents and intended use. By default, File Manager is set up to work with the
MSC.SuperModel application and supports four file types, namely submodels,
SuperModels, general elements, and job definitions. In general, each file type can
imply a different set of physical files, but all logical files of a given type are
guaranteed to have the same set of physical files. Additional information can be
found under File Types (p. 2-36).
File Templates
In addition to the four standard file types, a template file is also supported. This
file can be added by the system administrator and is used as the starting point
when new file types, as the four described above, are created. Additional
information can be found under File Types (p. 2-36).
Main Index
➤ ■ Done
➤➤ ➤
File States
The physical state of a file refers to how a file is stored and on which permanent
media it is stored. File Manager can recognize different storage methods (e.g.,
compressed versus uncompressed) and different locations (e.g., disk versus tape)
and provide access to all files regardless of the physical state. Additional
information can be found under File States (p. 2-38).
File Security
The security state of a file refers to the access privileges that are given to the user
community for viewing or modifying a file. File security is maintained by the File
Manager based on a clearly defined set of rules intended to assure data integrity
for all files. Additional information can be found in Security States (p. 2-38).
Main Index
➤ ■ Done
➤➤ ➤
2.3 Glossary
The following terms are used throughout this MSC.SuperModel User’s Manual.
Due to the slight departure from conventional nomenclature when dealing with
files, it is important to understand the distinctions. The following terms are
presented in alphabetical order.
Association Relationship between two files. The two files involved in the relationship
are referred to as the Source and Target. By convention, the source is said
to depend on the target. Both the system and users may create and destroy
these relationships (see Strong Association and Weak Association
respectively).
Association Special designator that conveys the relationship between two logical files.
Type
File Type Special designator for each logical file that conveys its intended use and
the rules by which the system operates on the file.
Hierarchy Collection of branches used to store all of the files managed by the system.
Logical File Collection of physical files that are treated as a single unit by the system.
Logical files are designated by a text description of up to 80 characters.
Logical files are the basic unit that the user sees. The File Manager
transparently manages the individual physical files to the users.
Physical File Conventional file. These comprise the logical files.
Physical State A combination of designators that convey how a logical file is currently
stored on the system. Possible states include: Uncompressed and
Compressed.
Read Only A mode of accessing a file that precludes the user from saving any changes
to the original file. The user may still save the changes as a new file in the
system.
Repository Generally used when referring to the physical directories which provide
the actual file storage facility. This can also be used as another name for the
file hierarchy.
Security State Designator that conveys the current accessibility of a logical file. Possible
states include: Unlocked/Locked, Working/Released.
Strong Association created by the File Manager system is termed Strong and
Association cannot be broken by individual users. These types of relationships convey
a dependency that the rest of the MSC.SuperModel application requires
for some of its functionality.
Main Index
➤ ■ Done
➤➤ ➤
Weak File associations created by individual users are termed Weak and are
Association generally used to provide additional pedigree information. For example, a
submodel could be associated to a CAD part file which provided the initial
geometry. Weak associations may be broken by users without impacting
the functionality of the MSC.SuperModel application.
Workspace Disk/directory resources established on the local machine that are used to
maintain copies of the files which a user is currently accessing.
Write Access Mode of accessing a file that allows the user to save any changes back to
the original file. Only a single user may acquire write access at a time.
Main Index
➤ ■ Done
➤➤ ➤
2.4 Frequently Asked Questions

The following lists a synopsis of the most frequently asked questions regarding
File Manager. This is perhaps the best place to look when you require clarification
about some aspect of the File Manager. If you do not find the information you
need, please try the general help that is available for the form with which you are
concerned and then finally with the overview section of this document.
Databases, Journal Files, and Much More

What happened to the .db You no longer have to think in terms of databases and journal files.
extension for database These have been combined under File Manager and the naming
names? conventions replaced with a more flexible file description. The
software now takes on the burden of knowing the proper file
extensions.
When I open a file with File Because you are really working with a copy of the file you requested,
Manager, the model window File Manager chooses a temporary name that is a combination of
banner contains a rather your login-id and the unique file-id. This is what you see in the
cryptic file name instead of banner (along with the good old .db extension).
the description. What is this?
Why am I unable to choose a File Manager is intended to help groups of users work together
template database when under the guidance of an administrator. Every time you request a
creating a new file? new file from File Manager, the template used is determined by the
current location in the hierarchy and the chosen file-type. For more
information on templates, please see the appropriate discussion
under File Types in this chapter.
File Types, States and Security

What is a submodel? What is A submodel is simply a MSC.Patran database, its journal file, and a
a SuperModel? What’s the history file. These three physical files move together as a single
difference? logical file. It is the type of file that you most frequently encounter. A
SuperModel on the other hand is a collection of submodels that have
been assembled, analyzed, and the results stored in the database.
This type of file is created by using the Job Definition capabilities of
SuperModel.
Main Index
➤ ■ Done
➤➤ ➤
Workspace and the Repository

Where are the files in File The term repository refers to a collection of file directories which the
Manager stored? File Manager uses to house all of the files available to the user. The
location of the directories is established by your administrator and
not required to be known by the general user.
What is the workspace and The term workspace refers to a file directory designated by the
why is it necessary? administrator to provide you with disk resources that provide
optimum efficiency when working with any of the files managed by
the system. Generally, this is a directory local to your machine’s hard
drive. Access of any file in File Manager starts by bringing a copy of
that file to the workspace for your personal use.
Main Index
➤ ■ Done
➤➤ ➤
2.5 Hierarchy
File Manager organizes and maintains files in a hierarchy. This hierarchy is flexible
and can be customized to reflect different projects and their tasks, engineering
discipline organization, etc. Similar to the concept of directories (or folders), File
Manager provides up to ten levels in which branches may be created for holding
files. Taken together, the branches form the hierarchy tree in which users may
freely work. Additional information can be found under File Repository (p. 2-31).
Levels
A level is simply an indication of the depth into the directory structure. Each level
is labeled to convey general information about branches in the hierarchy tree.
Branches
At each level, a set of branches can be created that hold the files. As with the levels,
each branch can be labeled to provide a key to its contents. The branches are
synonymous with the directories and folders that users are familiar with from
other file systems.
File Repository
The File Manager hierarchy provides a convenient view into what is termed the
File Repository. The repository is simply the physical storage locations used by
File Manager to house all users’ files.
Main Index
➤ ■ Done
➤➤ ➤
A representative hierarchy is graphically depicted in Figure 2-1.
Project: Configuration: Component: Team: Level Labels
Fighter F-XX Preliminary ...
Prototype Fuselage ...
}
Wing Strength
Dynamics
Branch Labels
Loads
Weights
Horiz-Stabilizer ...
Vert-Stabilizer ...
Landing Gear ...
...
Four Level Deep Hierarchy
Figure 2-1
The File Manager hierarchy is completely customizable to best suit each

customer’s needs. The level labels can be based on project, engineering discipline,
etc. Branch labels can be added at a later time, after the level labels are established.
Main Index
➤ ■ Done
➤➤ ➤
2.6 Repository and Workspace

In order to provide efficient operations, concurrent access, and improved “what if”
capabilities, File Manager introduces the concepts of a repository and workspace.
In general, these components are invisible to the user and are briefly discussed
here for completeness. Detailed information associated with the user’s workspace
can be found in the following Workspace section. For additional information
regarding the repository please refer to the File Manager Administrator’s Guide.
Repository
The repository is the physical disk location(s) used to hold all of the files under the
control of the File Manager. In effect, the hierarchy is a view into the repository.
Workspace
The workspace is a local holding place for files that are currently accessed. Access
to a file in File Manager is actually accomplished by copying the original file from
the repository to the workspace. The benefits of providing this working file are:
•Improved performance by eliminating the need to transmit changes via the

network (we pay only for the initial copy and any forced saves).
•Concurrent access by providing multiple copies and controlling the user’s ability
to move the copy back into the repository.
•Enhanced “what if” capability by allowing the local copy to be thrown away and
replaced by a fresh copy from the repository.
The workspace provides local disk resources for working with a file from the File
Manager repository (which most likely is not resident on the user’s machine and
may have high overhead associated with accessing it via a network). This
workspace is invisible to the user and is maintained by the File Manager, including
its clean-up following a session. The workspace serves as the home for a working
copy of a file that is maintained by File Manager.
Working Copies
Access to files in the repository are provided only through working copies. This is
done to ensure that no two users can make simultaneous, and quite possibly
conflicting, modifications to the same original file. In addition, this allows files in
the repository to be maintained in the most convenient physical state (e.g.,
compressed) without the users being burdened with the task of changing that state
every time they access the file (the File Manager simply supplies the copy and then
modifies its state automatically).
Main Index
➤ ■ Done
➤➤ ➤
Because workspaces can potentially be shared between users, a naming

convention has been adopted for working copies that eliminates the chance of two
working copies of the same original existing in the same workspace. The name is
composed of the user-id and unique file-id in the form:
<users id>-<file id>.<ext> (e.g., jones-1432.db)
This provides the added benefit of presenting the unique file-id to the user while
accessing a file. The above name appears in the MSC.Patran model window banner
allowing the user to identify the file-id.
As previously mentioned, the filename extension (.<ext>) is managed by the File

Manager for each of the physical files. Users do not have to concern themselves
with the extension.
Main Index
➤ ■ Done
➤➤ ➤
2.7 File Types and States

Each file in the hierarchy is uniquely identified by two methods:
1. The combination of hierarchy location and file description.

2. A numerical file-ID.
Usually, the user does not need to be concerned with the file-ID and interacts with
all files via the description.
File Descriptions
File descriptions are user-supplied text strings of up to 80 characters. They are
presented in the user interface to identify each logical file. Because the user’s view
of the file system is based on the hierarchy, these descriptions must be unique in
any given branch.
File IDs
The file-ID is valuable to the user when performing system diagnostics. File-IDs
help the MSC.SuperModel administrator identify and resolve any problems. The
file-ID is presented in the banner of the modeling window as part of the working
copies name. Files may be accessed through the user interface by their ID. See the
Workspace section for information on working copies.
Main Index
➤ ■ Done
➤➤ ➤
2.7.1 File Types

File types are typically differentiated by providing unique extensions to the name
(e.g., *.db, *.db.jou, *.ses). File Manager provides a slightly more flexible
mechanism by allowing for the definition of types with full text descriptions. Each
file in File Manager is associated with one of these defined types and can be easily
filtered based on the type.
The File Manager is installed with four default file types: Submodels,
SuperModels, Job Definitions, and General Elements. Additional file types may be
added by the system administrator. Each file type is associated with one or more
supporting template files, one of which is used as the basis for opening a new file.
Default File Types

The four default file types installed with the File Manager are described in the
following table.
Submodel The file type that you will most frequently encounter is the submodel.
This logical file is composed of a MSC.Patran database, journal file, and
an additional history file. It is used for most general modeling needs.
SuperModel SuperModel file type is similar to a submodel with the addition of a Job
Definition file and the inclusion of results in the MSC.Patran database.
This file type cannot be explicitly created by the user, but instead is the
result of submitting an analysis using the SuperModel Job Definition
functionality. Modifications to a SuperModel are prohibited in order to
ensure the model and its results remain consistent.
Job Definition A Job Definition contains the information required to assemble,

configure and submit a SuperModel analysis. After completion, the Job
Definition file is part of the SuperModel and provides a means of
reconstructing the analysis.
General Element General Element files contain MSC.Nastran specific definitions of either
reduced stiffness matrices, reduced mass matrices, or both.
Nastran XDB MSC.Nastran direct access results file.
Main Index
➤ ■ Done
➤➤ ➤
Template Files
Each file type — Submodel, SuperModel, Job Definition, and General
Element — is associated with one (or more) supporting template files. The
template file serves as the starting point for the user when a new file of a given type
is requested. This process is transparent to the user, but is important to understand
because it influences the appearance and contents of new files.
When a request for a new file is received by File Manager, a search is initiated for
a template that matches the file type desired. This search begins in the current
branch of the hierarchy and proceeds up the hierarchy tree until a suitable
template is found. If the search fails, a default template is used. This process is
transparent to the average user. Important information (e.g., common model data
such as geometry and materials) can be part of a template file and ultimately
contained in a newly-opened file; this provides an automated mechanism for data
sharing. The administrator of the File Manager is able to create a template file for
any given type at any location in the hierarchy. In this way, it is within the
administrator’s power to provide common data and default settings that can be
utilized for all models of a given type in a subsection of the hierarchy tree. For
further information about this type of customization please refer to the File Manager
Administrator’s Guide (p. A-337).
Main Index
➤ ■ Done
➤➤ ➤
2.7.2 File States
Physical State
The physical state of any file can be thought of as a combination of ON/OFF

switches that record how and where a file is currently stored in the repository. Any
combination of the states listed below can be applied to a file.
Compression Compression addresses the “how” aspect of the physical state. Files may be
in either an uncompressed or compressed state. Additionally, the state may
be by any number of different methods (e.g., compress, gzip, etc).
Compressed files can be directly accessed and File Manager can implicitly
uncompress them for the user (and recompress them when the user finishes
with the file).
Online Online describes if the file currently resides in the hierarchy or offline in an
alternative storage media. This is useful to save space in limited disk
resource situations. The offline storage technique is completely customizable.
The action associated with each of these states can be completely customized by
the administrator through a series of state scripts. Default scripts are provided
with the system that implement the standard compression algorithm used by
UNIX as well as an FTP mechanism for archival. Please refer to the File Manager
Administrator’s Guide (p. A-337) for further details regarding the customization of
state scripts.
Security States
Several file security states are supported and are mutually exclusive. Unlike
physical states these cannot be combined. Every file in the File Manager system is
in one of the following security states.
Unlocked An unlocked file is available to all users for WRITE access.
Locked A locked file is available to all users for READ access and only available to
the owner for READ/WRITE access.
Released A released file is available to all users for READ access only. The release
mechanism is intended to provide the ability to freeze the engineering data.
Working Although not a true security state, the term working is used to describe any
files that are not released. This provides a filtering mechanism as a
convenient means of identifying all locked and unlocked files.
Main Index
➤ ■ Done
➤➤ ➤
The locked/unlocked security states are controlled indirectly by the user through
requests to retrieve files with either Read Only or Write privileges. The system
validates the availability (i.e., current security state of the file) and proceeds
accordingly. The ability to change the security state to released is provided
through the user interface. This operation is restricted to File Manager
administrators.
Additional security states cannot be added to the File Manager, but the release
mechanism does provide for customization. This customization is in the form of a
release script that can be modified by the administrator. The intent of this script is
to allow for a connection to be established between the File Manager and a Product
Data Management (PDM) system. This topic is more fully discussed in the File
Manager Administrator’s Guide (p. A-337).
Main Index
➤ ■ Done
➤➤ ➤
2.8 File History and User Access

The File Manager maintains information related to the files that it manages and the
users accessing them. Most of this tracking is accomplished through a history file.
In addition, the File Manager maintains a record of the last file that has been
accessed by each user of the system.
History Files
File Manager guarantees the existence of a history file for each file that is stored in
the repository. This physical file is used to log the operations that are performed
with respect to the associated logical file. The following table lists the actions that
automatically generate history record entries and the format of that entry. The
<DTU> prefix denotes a preceding date-time-user entry.
Action History Entry
NEW <DTU> Created: template id# <template file id>

OPEN - Write <DTU> Accessed for Modification
SAVE AS <DTU> Saved from FileManager: file id# <original file id>
COPY (from UNIX) <DTU> Copied from UNIX: <original file name>
COPY (to UNIX) <DTU> Copied to UNIX: <new file name>
COPY (from FM) <DTU> Copied from FileManager: file id# <original file id>
MOVE (from UNIX) <DTU> Moved from UNIX: <original file name>
MOVE (to UNIX) <DTU> Moved to UNIX: <new file name>
MOVE (from FM) <DTU> Moved from FileManager: file id# <original file id>
COMPRESS <DTU> Compressed: method# <compression method>
UNCOMPRESS <DTU> Uncompressed: method# <compression method>
ONLINE <DTU> Online: method# <online method>
OFFLINE <DTU> Offline: method# <offline method>
ASSOCIATE (source) <DTU> Associated: target file id# <target file id>
ASSOCIATE (target) <DTU> Associated: source file id# <source file id>
UNASSOCIATE (source) <DTU> Unassociated: target file id# <target file id>
UNASSOCIATE (target) <DTU> Unassociated: source file id# <source file id>
RELEASE <DTU> !!! RELEASED !!!
UNRELEASED <DTU> !!! UNRELEASED !!!
Main Index
➤ ■ Done
➤➤ ➤
In addition to the above automated history entries, the user is presented with the
opportunity to add additional comments whenever a file is accessed with write
privileges. Multi-line comments are supported and each line is set off by the
greater than (>) character to designate it as user added. Below is a simple example
of a history file that shows several interactions with and without user added
comments.
13-Feb-96 14:32:56 john_smith
Created: template id# 1
14-Feb-96 08:14:22 jane_doe
Opened for Modification
> Updating material properties.
14-Feb-96 10:49:00 john_smith
Opened for Modification
> Creating element properties using new material definitions
> Importing load definitions
16-Feb-96 07:42:21 bob_jones
Copied from FileManager: file id# 1342
> Copy obtained to perform mass property analysis
...
User Access
File Manager records the last file that each user accessed for modification (i.e., the
last file which was being worked on). After restarting the File Manager, the user is
placed at the hierarchy location that contains the file, even if it has been moved by
another user since the last session. In the event that this file has been deleted from
File Manager, the user is placed back at the top of the hierarchy tree (this is
intended to serve as an immediate indication of the deletion).
Main Index
➤ ■ Done
➤➤ ➤
2.9 Functions and the User Interface

Numerous file operations are provided by the File Manager. This section presents
the default interface for each of these operations. Each interface can be customized
by the administrator. You may encounter additional options (especially where file
types are concerned) or slight differences (in the case of the hierarchy levels and
branches). The forms shown here provide the necessary information to get the
desired result from each file operation. The File Manager is accessed from the top
menu bar, under FM, as shown below.

New...
♦ Geometry ♦ FEM ♦ LBCs♦
CTRL
♦
N Properties
Matls ♦ Load Cases♦ Fields ♦ Analysis ♦ Results ♦ Insight ♦ XYPlot ♦ SuperModel
Open... CTRL O
Submit... CTRL T
Recent Files CTRL R
$# Session file.ses.01 started recording at 25
Close
$# Recorded by MSC/PATRAN CTRL W
03:36:58 PM
$# NetLS Initialization complete.
Save Acquiring
CTRL S license(s)...
hp, 2 CTRL A
Save As...
Recover
Abort
Utilities
Administration
Unix Import
Export
Session
Print
Images...
Report
Quit CTRL Q
Main Index
➤ ■ Done
➤➤ ➤
2.9.1 Function Summary

When File Manager is running, the conventional File menu of the MSC.Patran
main form is replaced by a menu labeled FM. Selecting this menu displays a pull-
down menu that lists the file functions. These functions are presented and
described below in the order in which they appear on the menu.
Menu Option Description

❏ New... Creates a new file.
❏ Open Opens an existing file for either Read Only or Write access.
❏ Submit... Opens an empty database for the purpose of beginning an
assembly of component models and subsequent analysis job
submission.
❏ Recent Files... Shows a list of recently opened models.
❏ Close Closes the currently open file.
❏ Save Saves the current working version of the file and
reviews/annotates its history (see also Review History).
❏ Save As... Saves the current working version as a new file.
❏ Recover Recovers from abnormal termination of a session.
❏ Abort Allows for a temporary exit from SuperModel when system
encounters difficulties (typically if the File Manager server is
shut down). Users may then re-enter and Recover the last
working session.
❏ Utilities >
❏ Delete... Deletes an existing file.
❏ Move/Copy... Moves or copies files into, out of, or in the hierarchy.
❏ Rename... Renames an existing file.
❏ Compress...
Alters an existing file to be stored as compressed or
uncompressed.
❏ Online... Move selected file offline or back online.
❏ Associate... Creates associations between files.
❏ FM Import ... Imports Patran database stored in the File Manager into the
current database.
❏ Review History... Reviews all history annotations/comments for a file.
❏ Administration >
Main Index
➤ ■ Done
➤➤ ➤

❏ Release... Precludes (releases) or allows (unrelease) further changes to a
file. May additionally migrate the file out of or into the
system.
❏ Lock... Locks or unlocks a file (over-riding the current security).
❏ Modify File Type... Modifies an existing file type.
❏ Branches... Modifies the system configuration by creating and/or
deleting hierarchy branches.
❏ File Types... Modifies the system configuration by creating and/or
deleting file types.
❏ Hierarchy List... Lists the hierarchy to a file.
❏ Convert... Converts all model databases to the current version.
❏ Convert File
Converts selected model to current version.
❏ UNIX Import... Imports an MSC.Patran database into the current database
using the standard MSC.Patran import user interface.
❏ Export... File functions that have not yet been migrated to the File
❏ Session Manager are still provided through the conventional UNIX
❏ Print... interface. These are more fully described under the
❏ Images... conventional MSC.Patran on-line documentation.
❏ Report...
❏ Quit Quits the current session of MSC.Patran.
Note: The administrative forms are described in the File Manager Administrator’s
Guide (p. A-337).
Main Index
➤ ■ Done
➤➤ ➤
2.9.2 System Interface

Before covering the actual file operations, it is important to discuss two aspects of
interfacing with the system that are common. Traversing the hierarchy and file
filtering together control the user’s view of the repository and access to any given
file. These forms are accessible from all of the file operation forms and serve a
supporting role. After discussion of the hierarchy and file filtering, the File
Manager user interface forms are presented in alphabetical order.
File Hierarchy
The File Hierarchy form allows users to traverse the current file repository. This
form provides the user’s current location in the hierarchy tree as well as visual
reminders of where files are located.
Level labels (determined by the administrator at installation time).
File Hierarchy
Project
Branch labels associated with the user’s current
location in the hierarchy. Selecting a level places
the user ONE BRANCH higher and provides a list
Configuration of its sub-branches in the listbox below.
Component
File marker indicates that files are present in this
X branch of the hierarchy.
Team
Select Project
List of sub-branches available from the current

hierarchy location. The title above this list reflects
the current level being moved into.
Hides the form from view.

Close
Main Index
➤ ■ Done
➤➤ ➤
File Filter
The File Filter form provides control over which files at a given hierarchy location
are visible and available for selection. Controls for file descriptions (string
matching), file type, physical state, and security state are all provided.
Physical state filters occur in pairs. For any pair, the user may
select one or both states for filtering.
File Filter String filter for file descriptions. (UNIX

Description Filter convention, i.e., * = ALL)
*
File type filter. Default types include: All,
Type Filter Submodel Submodel, SuperModel, Job Definition, General
Element, and Nastran XDB. Other types can be
Physical State Filters added by the system administrator.
Compressed
◆ ◆ Yes ◆
◆ No ◆ Both
Compression state filters.
Offline
◆ ◆ Yes ◆
◆ No ◆ ◆ Both
Security state filters. Valid states include: Locked,
Unlocked, Working, Released, All & Accessed.
Security Filter Unlocked
These buttons provide a convenient means of

Default Settings changing all the controls to affect the Default
Settings, as shown above, and All Files. These
All Files only change the settings, they DO NOT force the
Apply.
Apply Cancel
Selecting Cancel discards the form without

Selecting Apply updates the influencing the list.
current list on the association
file form.
Main Index
➤ ■ Done
➤➤ ➤
File Operation Forms

Forms associated with file operations are presented in alphabetical order. Most of
the file forms provide the same generic file selection mechanism. This is presented
prior to the actual forms and only the unique functionality and interface
characteristics of each form is fully described in the later sections.
Generic File Selection

This form provides for selecting the file from the list of visible file descriptions. The
list of descriptions is controlled by both the current hierarchy location (controlled
through the subordinate hierarchy form) and the current file filter (controlled
through the subordinate filter form).
Access to the file hierarchy and file filter The current hierarchy location
forms are provided as well as selection of and filter settings are conveyed as
file by internal ID number. text strings.
File descriptions associated with the current hierarchy location and file filter settings are
displayed. The full 80 characters allowed for these descriptions is visible. Selecting a file is
accomplished by picking it from the available list. The selection is highlighted and
becomes the target for the intended operation.
File Type can be changed by selecting the file filter button located at the top of the form.
Main Index
➤ ■ Done
➤➤ ➤
2.9.3 File Manager
New
This form provides for creating a new file in the File Manager hierarchy. The user
can specify the desired file type and designate the description.
The user may request any of the available file types for this new file.
File New
Existing Files
File Hierarchy ... File Filter ... File By ID ... Refresh List
Current Hierarchy: MSC Air Series 100

Current Filter: * Submodel Uncompressed | Compressed | Online Unlocked
File Descriptions
component 1
component 2
component 3
lb test
three component
ud test
xdb test
New File
Template Type Submodel Display Matching Files
File Description
OK Cancel
See Generic File Selection To update the File Description list, select
(p. 2-47) for details. the Refresh List button.
Selecting a file from the list above causes its description to be entered. This
provides a convenient means of following any naming methodology that may be
established at your site. Modify or directly type the new file description.
Main Index
➤ ■ Done
➤➤ ➤
Open
The Open function allows users to access existing files stored in the File Manager
hierarchy.
Submit
Submit is a shortcut for users that want to create a new SuperModel file for
subsequent assembly and analysis. The new file is created and users are taken
directly to the submodel selection form in the Assembly and Configuration
module.
Recent Files
Recent Files provides users with a method for quickly finding recently accessed
files.
Close
Close terminates the current workspace model, but leaves MSC.SuperModel

system running.
Save
Save writes the current workspace model to the hierarchy and leaves the existing
model open.
Main Index
➤ ■ Done
➤➤ ➤
Save As
Changes made to a file accessed for either Read Only or Write can be saved to a
new file in the system using the following form:
See Generic File Selection (p. 2-47) for details.
File Save As
Existing Files
File Hierarchy... File Filter ... File By ID ... Refresh List
Current Hierarchy: MSC Air Series 100 Wing
File Descriptions
Aileron: LHS
Flap: LHS
New File
File Description
Wing Torque Box: LHS
OK Cancel
Type the description for the new file being created. Alternatively, select a file from the
listing above and modify the description.
Main Index
➤ ■ Done
➤➤ ➤
Recover
Recover automatically returns the user to the current working session (local files)
in the event of an unplanned interruption of an MSC.SuperModel session.
Abort
The most common use for this function is if the File Manager Server shuts down
while the user has a database open and the user gets an error when attempting to
save or close a file.
The Abort function does the following: It quits MSC.Patran without doing
anything to the File Manager Local Workspace and without telling the File
Manager server to Unlock the current file. This is almost equivalent to manually
killing the MSC.Patran session, but more graceful. After the user has aborted a
session, the user can launch MSC.SuperModel. When the File Manager server is
back up and correctly working, use the Recover option from the File Manager
menu. This returns you to the same place you were in MSC.SuperModel before the
Abort command.
Utilities
The File Manager Utilities options are described in the following section.
Administration
The File Manager Administration options are described in the MSC.Patran

documentation. These options include:
• Unix Import
• Export
• Session
• Print
• Images
• Report
• Quit
Main Index
➤ ■ Done
➤➤ ➤
2.9.4 File Manager - Utilities
Delete
This form provides for deleting an existing file in the File Manager hierarchy. The
user can select multiple files for deletion.
File Delete
Existing Files
File Hierarchy ... File Filter... File By ID ... Refresh List
File Descriptions
component 1
component 2
component 3
lb test
three component
ud test
xdb test
Apply Cancel
Main Index
➤ ■ Done
➤➤ ➤
Move/Copy
This form provides for transferring files into, out of, and in the File Manager
hierarchy. Move deletes the original file and Copy maintains the original file.
Subordinate forms for selecting the source and destination files can be reached through
these buttons. The form used for selecting a UNIX file is identical to the conventional
MSC.Patran interface. For File Manager a Generic File Selection (p. 2-47) form is
provided.
The source file location can be specified For transfers into the File Manager
as either File Manager or UNIX. from UNIX, the file type must be
specified.
File Move/Copy
Source File
UNIX Select File ...
Path:
File Name:
Destination File
File Manager Select File ... File Type Submodel
Hierarchy:
Description:
Move Copy
Cancel
File names and description selections Switches provide a means of either

are reflected even after the selection moving or copying the selected files.
forms are dismissed.
The destination file location can be specified as either File Manager or UNIX. If
UNIX is specified, the file is moved out of the File Manager hierarchy.
Main Index
➤ ■ Done
➤➤ ➤
Rename
This form provides for renaming (or redescribing) an existing file in the File
Manager hierarchy.
File Rename
Existing Files
File Hierarchy... File Filter ... File By ID ... Refresh List
File Descriptions
component 1
component 2
component
lb test
three component
ud test
xdb test
Rename File
File Description
Apply Cancel
Select a file from the list enters the description. Modify this to the new description for
the selected file.
Main Index
➤ ■ Done
➤➤ ➤
Compress
This form provides for altering the physical state of an existing file in the File
Manager hierarchy, namely whether or not the file is stored in a compressed or
uncompressed state. Multiple files can be selected for compression.
File Compress
Existing Files
File Hierarchy ... File Filter... File by ID ... Refresh List
File Descriptions
Aileron: LHS, Final Sizing, w/Configurations
Flap: LHS, Final Sizing, w/Configurations
Wing Torque Box: LHS, Final Sizing
Compress Uncompress
Cancel
Switches provide either compressing or uncompressing the selected files. These

switches are activated after a file selection is made.
Main Index
➤ ■ Done
➤➤ ➤
Online
This form allows the user to move a file out of the hierarchy to an offline storage
media and to retrieve a file online back into the hierarchy.
File Online
Existing Files
File Hierarchy... File Filter ... File by ID ... Refresh List
Current Filter: * All Uncompressed | Compressed | Online | Offline All
File Descriptions
Job definition for Merged Model 1
Job definition for Merged_Model_Land-Roll-Straight_OrigNum_XDB
Job definition for Merged_Model_Land_Offset 100k
Job definition for Merged_Model_Land_Offset 100k (1)
Job definition for Merged_Model_Land_Offset 200k
Job definition for Merged_Model_Roll_Offset 200k
Job definition for Merged_Model_Straight_Offset 300k
Job definition for Merged_Model_Straight_OrigNum
Job definition for Merged_Model_Straight_OrigNum (1)
Job definition for X
Job definition for component 1
Job definition for component 1 (1)
Offline Online
Cancel
Switches
Switches provide
provide either
either Offline
Offline or
or Online
Online operation
operation ofof the
the
selected file.
selected file. These switches are activated after a file is
selected.
Main Index
➤ ■ Done
➤➤ ➤
Associate
This form provides for manipulating associations between logical files. The ability
to create, break, and show user-defined associations is supported.
Selection of the source file is provided through a subordinate form that presents the
generic file selection interface. To display the form, choose the Select File button. The
description of the selected file is then echoed in the accompanying databox situated
immediately below the Select File button.
Switches provide a means of changing The available user-definable association
the actions to be taken. types are presented in an option menu.
Selection of the constituent or target file follows the source file.
Subforms for selecting the source and target files can be accessed by selecting
either of these buttons. The Generic File Selection (p. 2-47) form is provided in
either case.
Main Index
➤ ■ Done
➤➤ ➤
FM Import
This form permits the user to import a Patran database stored in the File Manager
into the current database. The MSC.Patran DB Options and Equivalence Options
subforms are identical to those provided for normal Unix database import.
User selects from the file descriptions which MSC.Patran

databases to import. User selection is highlighted and
description is shown below.
User can specify which entities contained in the selected database will be
imported as well as how duplicate entities will be equivalenced by accessing
either of these subforms.
Main Index
➤ ■ Done
➤➤ ➤
Review History
The history of any file maintained by the File Manager may be reviewed by
selecting it from the following form.
Select File for History Review
Existing Files
Current Hierarchy: MSC Air Series 100 Wing

File Descriptions
Aileron: LHS
Flap: LHS
Selected File
File Description
OK Cancel
The description for the file of interest may be selected from the
available list or directly typed.
Main Index
➤ ■ Done
➤➤ ➤
After selection, the physical file that contains history information is read and
displayed in the following form.
System generated history comments and user comments (denoted by > )

are displayed in chronological order, with the most recent entries at the
bottom of the text list.
A review of the history comments always accompanies a request to Save a file. Under
those circumstances, the Append Text databox displays permitting the user to append
additional comments to any system generated messages.
Main Index
➤ ■ Done
➤➤ ➤
2.9.5 File Manager - Administration
Release
Release and Unrelease functions removes or returns a file to working status.
Releasing a file prohibits any further changes to the file and it is only accessible for
Read access.
Release is available to the system administrator and is located under

Administration - Release. Component models and associated results may be
Unmerged from Released files.
Unreleasing a file establishes write access privilege.
File Release
Existing Files
File Descriptions
component 1
component 2
component 3
lb test
three component
ud test
xdb test
Release Unrelease
Cancel
Main Index
➤ ■ Done
➤➤ ➤
Lock
Lock/unlock is a security feature. Locking a file prevents a file from being write-
accessed. Components may not be Unmerged from Locked files. This
administrative functionality is sometimes useful if an unexpected exit from
MSC.SuperModel has left one or more files in a locked state.
Unlocking a file allows users write access.
File Lock
Existing Files
Current Hierarchy: Exercises
File Descriptions
component 1
component 2
component 3
lb test
three component
ud test
xdb test
Lock Unlock
Cancel
Main Index
➤ ■ Done
➤➤ ➤
Modify File Type

Modify File Type allows users to modify the type of any existing file. The only
restriction is that files may not be modified to a new type of “Supermodel”.
User selects from existing file descriptions which is then highlighted.
User can alter the file type by accessing the option file type option list.
Information on the file selected by the user displays here.
Main Index
➤ ■ Done
➤➤ ➤
Branches
New hierarchy branches may be added or deleted by the system administrator.
The user interface is described below.
Branches The Action can be either Create or

Delete so you can create or delete a
Action: Create hierarchy branch.
Project
MSC Air
The user works down the hierarchy
Configuration
to the level where a new branch is to
Series 100 be created or deleted. In this case,
the new branch is to be created at
Component the Team level under the hierarchy
Vertical Tail path Project: MSC Air /
Configuration: Series 100 /
Team Component: Vertical Tail.
Select Team
Create Team Branch
Apply Cancel
Main Index
➤ ■ Done
➤➤ ➤
File Types
New file types, in addition to those provided by default, may be added or deleted
by the system administrator. The user interface is described below.
File Types
The Action can be either Create or
Action: Create Delete so you can create or delete a
file type.
Existing Types
All
General Element
Job Definition Existing file types.
Submodel
Supermodel
New Type New file type name must be supplied or

select the file type to be deleted.
Default Template... A template file (see below)

must be identified for each new
file type.
Apply Cancel
Some files have related files.
This also allows these files to
be deleted. The default is to not
delete the related file types.
The designation of a template file is performed through a UNIX

file widget. This file and all files in the same directory with the
same base name (see the discussion on Logical Files) is copied to
the root of the hierarchy to serve as the starting point for users
who request a new file of this type. The selection of a default
template is very important. Review the discussion on Logical and
Physical Files before defining a new file type.
Main Index
➤ ■ Done
➤➤ ➤
Hierarchy List
The contents of the File Manager hierarchy may be listed and stored in a file. Users
may specify the starting point to generate the hierarchy list. The file system path
names are printed to the hierarchy listing as well.
Hierarchy List
Create Hierarchy List
Project
MSC Air
Configuration The user works down the hierarchy

to the level where the hierarchy list
Series 100 is to begin. In this case, the list
begins at the Component level
Component
under the hierarchy path Project:
Vertical Tail MSC Air / Configuration: Series 100
/ Component: Vertical Tail.
Team
Select Team
List Component Branch
Vertical Tail
Identify the output file name

Select Output File... and location where the
hierarchy list is printed.
Apply Cancel
Main Index
➤ ■ Done
➤➤ ➤
Convert
The contents of the File Manager hierarchy may be converted to the next version
of the MSC.Patran database. The user identifies a hierarchy starting point and all
MSC.Patran databases below that point are converted to the current version.
Covert Databases Stored in File Manager
Select Starting Location ...
Scan Hierarchy Update Hierarchy
<No Starting Location Selected>
Messages
to the level where a convert is to be
initiated. In this case, the branch
where the convert is to begin is at
the Component level under the
hierarchy path Project: MSC Air /
Component: Vertical Tail.
Save Messages to File Clear Messages
Cancel
Main Index
➤ ■ Done
➤➤ ➤
Convert File
MSC.Patran databases below that point are converted to the current version.
The user works down the file hierarchy and selects the file description
that will be converted to the next version of MSC.Patran. The user
selection is highlighted and all relevant information is displayed in the
lower portion of the form.
User can review history of the file chosen for conversion by selecting
this switch. The review history form (2-58) displays.
Main Index
➤ ■ Done
➤➤ ➤
2.10 File Manager Customization
Overview
MSC.SuperModel provides additional customization capabilities in the File
Manager. Users may now develop PCL functions that are called by the File Manger
during certain file operations. The customized actions can be defined to occur
before or after the File Manager has completed its specified task. In addition,
customized error handling functions may be added that are invoked if File
Manager has difficulty performing its intended operation. This allows users to
perform any necessary clean up operations if the failure affects their customized
tasks.
Details
File Manager has been extended to allow user-defined functions to be a regular
part of performed file operations; similar to the "user_db_open" and
"user_db_close" functions of MSC.Patran. These can be used to perform tasks such
as enabling and disabling custom PCL menus. MSC.SuperModel now provides a
method for custom operations in addition to the normal File Manager tasks.
MSC.SuperModel does not limit the number of users that can customize a feature;
it provides opportunities for custom operations before or after File Manager
completes its task and allows for custom error handling.
Functions That Support Customization

The following File Manager functions now support user customization:
NEW
OPEN
SAVE
SAVE_AS
CLOSE
ABORT
RECOVER
RELEASE
UNRELEASE
QUIT
Main Index
➤ ■ Done
➤➤ ➤
Sequence of Custom Function Calls

File Manager can be instructed to invoke a user-supplied function either:
•Prior to executing the standard File Manager task (designated as "PRE"),

•After successfully completing the standard File Manager task (designated as
"POST"), or
•In the event an error occurs while attempting the standard operation (designated
as "ERROR").
Together, this collection of functions allows users the ability to interact with File
Manager operations robustly and cleanly.
Supporting Multiple Customization

MSC.SuperModel allows multiple users to "register" their own function names
with a particular File Manager operation. During registration, the operation
sequence of functions is specified -- “PRE”, “POST”, or “ERROR”.
There is no limit to the number of functions that can be registered. The File
Manager calls all registered functions at the appropriate operation sequence.
Custom Function Return Status and Process Interruption

User functions that operate prior to File Manager’s own operation (i.e., those
registered as “PRE” tasks) are allowed to terminate the file operation. This is
accomplished by returning a non-zero value in the status argument of any custom
function. After File Manager receives a non-zero status, all subsequent operations
are terminated, including additional custom functions that are yet to be invoked,
File Manager standard process functions, and any registered “POST” or “ERROR”
functions. An error message is posted for the user and all file states remain as is
prior to the operation.
Main Index
➤ ■ Done
➤➤ ➤
Registering Custom Functions

The following PCL is required to register custom functions with the File Manager:
smdl_fm_customize.register(<my_function>, <FM_OPERATION>,
<FM_SEQUENCE>)
where,
•<my_function> is the name of a custom PCL function which are executed as part
of the File Manager's operation.
•<FM_OPERATION> is a string constant which designates the operation which
will invoke `my_function'. Acceptable values are: “NEW”, “OPEN”, “SAVE”,
“SAVE_AS”, “ABORT”, “RECOVER”, “CLOSE”, “QUIT”, “RELEASE”, and
“UNRELEASE”.
•<FM_SEQUENCE> is a string constant which designates the operation sequence
for the custom function. Acceptable values are: “PRE”,” POST”, and “ERROR”.
Both stand-alone and class-method functions are supported. The user is

responsible for ensuring the argument compatibility of the registered functions
with the data to be passed by File Manager (see "Shared Information from File
Manager" below).
For example, the following lines would tell the File Manager to execute two
custom functions. The first is called after the File Manager has finished an Open
file operation and is a stand-alone (or globally defined) function. The second is
called if File Manager encounters an error while performing a Close file operation.
smdl_fm_customize.register("my_open_post", "OPEN", "POST")
smdl_fm_customize.register("my_custom_class.close_error", "CLOSE", "ERROR")
These calls should be placed in the p3smdl_epilog.pcl file that is automatically

loaded by MSC.SuperModel during initialization. This file is similar to the
MSC.Patran p3epilog.pcl file that is assumed to reside:
Current directory
User’s home directory
P3HOME directory
Sharing Information With the File Manager

To allow custom functions to properly operate with the File Manager, a predefined
set of arguments are passed to any registered function. This intentionally limits the
user’s knowledge of the file system to maintain data security and integrity.
Main Index
➤ ■ Done
➤➤ ➤
In addition, each function is expected to return a status as an integer value. This

status is always the last argument present. “PRE” functions may use the status to
terminate the file operation (see Custom Functions Return Status and Process
Termination).
The information passed to any given function depends on the associated standard
File Manager operation, as shown in the table below.
Function ID Description Hierarchy Type Access Status
New 1+ 2+ 3+ 4+ 5*
Open 1* 2* 3* 4* 5+ 6*
Save * 2*
Save As 1, 2@ 3+ 4+ 5*
Close 1* 2*
Quit *
Release 1* 2*
Unrelease 1* 2*
Abort *
Recover 1+ 2+ 3+ 4+ 5+ 6*
where
ID = Unique integer that the system uses to identify a file
Description = String which identifies a file
Hierarchy = String array of branch names where the file resides
Type = String label which designates the file's type.
Access = String which denotes the ability of the user to modify the contents of a file
# - Designates the order of the arguments passed (1,2,3,4,5)
* - Argument is valid for PRE, POST & ERROR calls
+ - Argument is valid for POST calls only
[blank] - Argument NOT passed
@ - SAVE AS receives two file ids; for the original and copy (the copy is only valid
Main Index
for the “POST” task)
➤ ■ Done
➤➤ ➤
For example, a custom function for handling SAVE_AS operations would have the
form:
my_custom.save_as(orig_file_id, save_file_id, save_desc, save_hier)
Main Index
➤ ■ Done
➤➤ ➤
Main Index
➤ ■ Done
➤➤ ➤
Modeling and Simulation ❚ 3-75 Options
3
■ Introduction
■ Element Quick Create
■ Loads Tools
■ Property Data Plots
■ Mass Properties Management
Main Index
➤ ■ Done
➤➤ ➤
Introduction to Modeling and Simulation

MSC.SuperModel offers modeling and simulation tools commonly utilized in
aerospace: Element Quick Create, Loads tools, Property Data Plots, and Mass
Property Management. Modeling and Simulation is accessible from the
MSC.SuperModel main menu.

SuperModel Main Menu
MSC.SuperModel
Version 200x
Main Menu
Loads Tools
Property Data Plots

Configurations
Model Unmerge
Bar End Loads
Shear Panel Plots
Main Index
➤ ■ Done
➤➤ ➤
3.1 Element Quick Create

MSC.SuperModel contains several ease-of-use tools, including Finite
Elements/Quick Create. For users manually creating finite elements (i.e., not
auto-meshing), they can now simultaneously assign element properties to the
elements as they are created. In addition, the user can create properties on the fly
and assign these to any elements generated using Quick Create.
The Element Quick Create form is accessed from the MSC.SuperModel main
menu.


MSC.SuperModel
Version 200x
Main Menu
◆Element Quick Create

Loads Tools
Property Data Plots

Configurations
Model Unmerge
Bar End Loads
Shear Panel Plots
Main Index
➤ ■ Done
➤➤ ➤
After selecting the Element Quick Create option from the MSC.SuperModel main
menu, the following form displays.
The user has the option of creating either

elements or properties on the fly. Presently,
materials are not supported.
Select this switch to choose which existing

element properties to assign to the elements that
are to be created. After a property has been
selected, the name displays in the form. Note:
elements can be created without any properties
being selected.
If the user sets this toggle, then the element

properties are displayed for the selected property
set.
User specifies the element shape, topology and

formulation.
User specifies the nodes that define the element

connectivity.
Important: Element property values cannot be deleted or modified using the Quick Create
functionality. Quick Create can only reference previously created element properties.
Main Index
➤ ■ Done
➤➤ ➤
Elements
To assign an existing Element Property set to any newly created elements, select
the Existing ... button. After doing this, the following form appears provided the
Show Properties toggle is set on the main form (see previous page). If a property
is not selected for automatic assignment to created elements, the main form
displays Property: None Selected.
All of the available property sets are lists when the Existing
button is selected on the main form. The user selection is
highlighted and appears on the main form simultaneously.
The associated properties with

the selected property sets are
displayed provided the Show
Property Values toggle has
been set on the main form.
Main Index
➤ ■ Done
➤➤ ➤
As shown in Input Properties, when an existing element property set is selected,

the appropriate Input Data form is presented. Element property values may not be
altered. After the Element Property set is selected, the Quick Create form is
updated to reflect the currently selected property set, as shown in the following
form.
This element property set is

automatically assigned to all 2D
elements created using Quick Create.
If elements are created and no existing Element Property set is identified for
automatic assignment, then the elements are simply created without reference to
any Element Property set.
Main Index
➤ ■ Done
➤➤ ➤
Properties
Provides access to create Element Properties without having to access the

MSC.Patran properties application. For creating Properties, the following form is
provided within Quick Create.
User specifies property set

name, type and formulation.
Select this to input the element

properties.
Main Index
➤ ■ Done
➤➤ ➤
Materials
Provides access to Create Materials without having to access the MSC.Patran

Materials application. Presently this function is not enabled.
Main Index
➤ ■ Done
➤➤ ➤
3.2 Loads Tools

The Loads Tools in the Loads Browser module allows users the ability to create
either Running Loads Plots or perform Load Summations. Loads Tools is
accessible from the MSC.SuperModel main menu.

MSC.SuperModel
Version 200x
Main Menu
◆ Loads Tools
Property Data Plots

Configurations
Model Unmerge
Bar End Loads
Shear Panel Plots
Main Index
➤ ■ Done
➤➤ ➤
Overview
Create
Loads Tools
Modify
Action: Plot ?
Delete
Object: Results
Plot
Method: Running Loads
Region
Region Chain
Running Loads Force
Load Summation LBCs
Equiv Vector Load Cases

Results
When Loads Tools is selected, the first form displayed is Create Region. Shown
adjacent to the form above are all of the different Actions, Objects, and Method
Options available.
Not all combinations of Action and Object are valid for this form. The Method
option menu is only available when the Action is set to Plot.
Most of the Loads Tool forms are shown and annotated in this chapter. The
Actions are grouped within this chapter as follows:
• Create (Region, Region Chain and Force)

• Modify (Region and Region Chain)
• Delete (Region and Region Chain)
• Plot - Running Loads (LBCs, Load Cases, and Results)
• Plot - Load Summation (LBCs, Load Cases, and Results)
Loads Tools
Following is a list of the Loads Browser forms and subforms related to the Loads
Main Index
Tools.
➤ ■ Done
➤➤ ➤
• Create/Region
• Create/Region Chain
• Create/Force/Equiv Vector
• Modify/Region
• Modify/Region Chain
• Delete/Region
• Delete/Region Chain
• Plot/LBCs/Running Loads
• Plot/Load Cases/Running Loads
• Plot/Results/Running Loads
• Plot/Running Load Subforms
• Plot/LBCs/Load Summation
• Plot/Load Cases/Load Summation
• Plot/Results/Load Summation
Introduction
Creation of Running Loads plots and Load Summations requires the identification
of a section of the model over which the plot is to be created. This section can be
described using a Region, Region Chain or on-the-fly through interactive node and
element selection.
Visualizing resultant loads along the bending axis of a wing can be very helpful for
verifying that the correct loads have been applied to a model. MSC.FlightLoads
and Dynamics provides a set of XY Plotting capabilities that allow for plotting
overall vehicle applied shear, bending moment, and torque (SBMT) diagrams
based on the applied loading. This functionality allows for plotting overall vehicle
applied SBMT diagrams along different axes for different regions of the structures.
Load Summation provides a convenient method of summing the applied vehicle

loads about a spatial location.
Main Index
➤ ■ Done
➤➤ ➤
The following picture illustrates the methodology behind the Running Load plots.
Chained region 1
Z’ Chained region 2
Y’
Z’’ Y’’
5 10
15 20
X’ 25
30
X’’ 25
20
15
5 10
-5 0
Sample XY Plot: List of regions in chain
SBMT Plot for region(s):

Inner_wing, Outer_wing
50
Load type (Force, Moment) Condition_Component:

40 Air_Load_Mx
Fuel_Mx
30
Moment
Plotted together by
20 component, for this example
10
0 10 20 30 40 50 60
X Location
Load Summations can be performed using previously defined Regions or

on-the-fly selection of nodes and elements.
Both Running Loads and Load Summation support the following kinds of external
loads:
•Forces and Moments

•Pressure
•Inertia
•Distributed Edge Loads
Typically, Force and Moment loads are evaluated as these appear in the
Aerodynamic/Aeroelastic database and Aeroelastic analysis results files.
Main Index
➤ ■ Done
➤➤ ➤
Create Region
This form describes the creation of model Regions. These can describe either
aerodynamic or structural regions. A Region should only pertain to either the
structural or aerodynamic model and not both.
Main Index
➤ ■ Done
➤➤ ➤
The following form is used to create a Region:

Loads Tools
Action: Create
Object: Region Region
Region Chain
Existing Regions Force

* Filter
Region Name
Use to enter a new region name.
Region Definition...
Defines the region’s reference coordinate frame.
Reference Coordinate Frame
-Apply- Cancel
Define Region
User selects which groups to include in the
region definition.
If this toggle is set, then all of the entities

associated with the groups that define the
region will be highlighted in the graphics
viewport.
Main Index
➤ ■ Done
➤➤ ➤
Create Region Chain
Two or more Regions can be chained together and referenced as a Region Chain.
A Region Chain can describe Regions with a discontinuity at their intersections
(i.e. two Regions that follow a wing spar break). Region Chains can be referenced
in Running Load plots. The following form is used to combine individual Regions
into a Region Chain that can be plotted in a single graph.
Loads Tools
Previously created region chains.
Current regions in the model.
Defines the regions in the chain and the

order in which they are to be plotted. Loads
from these regions are calculated from the
maximum X of the last chained region back
to the minimum X of the first chained region.
Loads from regions further out on the chain
are added to regions further in on the chain
at the maximum X after they are transformed
to the new coordinate system.
Clears all the items in the Chained

Region(s).
Main Index
➤ ■ Done
➤➤ ➤
Create Force
The Create Force functionality enables a user to create an equivalent force vector
that is derived from all of the nodal forces within any combination of existing load
cases. The user has the ability to define the load summation point where the
equivalent force is applied as well as the region over which the load summation is
performed. The resultant force can either be used to replace the contents of an
existing load case or to create an entirely new load case.
Main Index
➤ ■ Done
➤➤ ➤
Available Load Cases in the database

currently open. Load Cases selected by the
user for load summation are highlighted.
User has the option to either create a new

load case or replace the data in an existing
load case. The form that is displayed for the
later option is shown on the next page.
User specifies the name used for any new

load cases.
User specifies the coordinate frame that will

be used to define the components of the
equivalent force vector. The default is the
global rectangular.
User specifies those entities over which the

load summation is performed. The user
must ensure that the load cases selected
have nodal loads that are applied to the
selected entities else an equivalent force will
not be created. Consequently, element base
forces such as pressures are ignored.
User specifies the node where the

equivalent force will be applied. Only a
single node may be specified. Any additional
nodes will be ignored.
Main Index
➤ ■ Done
➤➤ ➤
The following form is displayed if the user selects the load disposition switch to
enable the Replace Data in Load Case option. This option will cause all of the loads
contained in the selected load case to be replaced with the newly created
equivalent force.
Main Index
➤ ■ Done
➤➤ ➤
Modify Region
Previously created Regions can be modified. The following form is used to modify
a Region:
Loads Tools
Action: Modify
Object: Region
Existing Regions
* Filter
Used to enter a new Region name, or to modify the

name of the selected Region.
Rename Region As
Define Region
Groups
Region Definition... * Filter
Reference Coordinate Frame

default_group
Highlight Selected Entities
-Apply- Cancel OK Cancel
Used to select the Groups to be

included in the Region definition.
Defines the Reference

Coordinate Frame of the region.
Main Index
➤ ■ Done
➤➤ ➤
Modify Region Chain
The following form is used to modify previously created Region Chains.
Previously created region chains are listed

here. The region chain selected for
modification is highlighted.
The user has the option to change the name

of the region chain being modified.
All of the current regions that exists in

model. User selects those regions that will
be contained in the revised region chain
definition.
When a region chain is selected, all of the

regions that comprise that chain are initially
displayed. To remove a region, press the
clear selection button which removes all of
the regions. Then select those regions that
will be included in the revised chain
definition. The revised list of regions display
in the order they were selected.
Modifies the region chain definition.
Closes the form without modifying the region

chain unless the Apply switch is pressed
beforehand.
Main Index
➤ ■ Done
➤➤ ➤
Delete Region
The following form is used to delete previously created Regions.
Loads Tools
Action: Delete
Object: Region
Existing Regions
Inner_wing
Outer_wing
Winglet Select Region and Apply to delete region.
Regions to Delete
-Apply- Cancel
Main Index
➤ ■ Done
➤➤ ➤
Deleting Region Chains
The following form is used to delete previously created Region Chains.
Loads Tools
Action: Delete
Object: Region Chain
Existing Region Chains

Inner_wing
Outer_wing
Winglet Select Region Chain and Apply to delete
chain.
Region Chains to Delete

Inner_wing
-Apply- Cancel
Main Index
➤ ■ Done
➤➤ ➤
Plot Running Loads

To Plot Running Loads, set the Action to Plot on the Loads Tools form. The form
layout is set up so that the user sets up the plot in a logical order from the top of
the form to the bottom. Several subforms are also used to define the parameters of
the plots to be generated. Users have the optional choice of writing this
information to a report file.
Loads Tools
Action: Plot
Object: Results LBCs
Method: Running Loads Load Cases

Results
Running Loads
Load Summation
After identifying that a Running Load plot is desired, the model’s nodes and
elements must be identified either by membership to a Region, Region Chain or
Selected on-the-fly.
Loads Tools
Action: Plot
Object: Results
Option: Region Selected Entities

Region
Region Chain
Main Index
➤ ■ Done
➤➤ ➤
Plot/LBCs/Running Loads
One or more MSC.Patran Loads/Boundary Conditions can be integrated over a model to produce a
Running Load plot.
Loads Tools
Action: Plot
Object: LBCs
Region
Option for Region and Region Chain are very similar.
Option
Select Region
* Filter All available regions or region chains are listed. User

selections are highlighted.
reg1
LBC(s)
aileron_force
axial force
edge_pressure
flap_force
Refer to the Plot Options form in this section for more
pressure_wing information on this selection.
tip_load
Select File Name is only active when Output to Text

File switch is enabled.
This displays the standard File Name Definition form.
Options ...
Output to Text File All running loads plots and any corresponding XYPLOT
windows are deleted from the database.
Select File Name ...
Delete existing plots
-Apply- Cancel
Main Index
➤ ■ Done
➤➤ ➤
The following form will be displayed when the option is changed to Selected
Entities. This option enables the user to produce more refined running loads plots
that encompass specific entities as well as relative to a specific coordinate frame.
Nodes or specific element types may be

specified.
The coordinate frame is specified for

determining how force and moment
components are defined.
All existing LBCs contained in the model

are listed. Any combination of LBCs
may be specified. User selections are
highlighted.
Refer to the Plot Options form in this

section for more information on this
selection.
All running plots any corresponding

XYPLOT windows are deleted from the
database.
Main Index
➤ ■ Done
➤➤ ➤
Plot/LoadCases/Running Loads
One or more MSC.Patran Load Cases, which may reference multiple LBCs, can be
integrated over a model to produce a Running Load plot.
Available options include:

Selected Entities (see next page)
Region
Region Chain
This portion only appears if the Region

option is selected. Multiple regions may be
selected and these will be highlighted.
All available load cases are listed here.

Multiple load cases may be selected and
these will be highlighted.
Refer to the Plot Options form in this

section for more information on this
selection.
Select File Name is only active when

Output to Text File switch is enabled.
This switch will then display the standard
FIle Name Definition Form.
All Running Loads Plots and any

corresponding XYPLOT windows are
deleted from the database.
Main Index
➤ ■ Done
➤➤ ➤
The following form is displayed when the option is set to Selected Entities. The
user can select either individual nodes or particular types of elements when
creating a running loads plot for a combination of load cases.
Nodes or specific element types

may be specified.
The coordinate frame is specified

for determining how force and
moment components are defined.
Refer to the Plot Options form in

this section for more information
on this selection.
Main Index
➤ ■ Done
➤➤ ➤
Plot/Results/Running Loads
One or more Results can be integrated over a model to product a Running Load
plot. For MSC.FlightLoads and Dynamics Version 1, an XDB results file is
automatically created by attachment to an Aerodynamic/Aeroelastic database.
Therefore, Running Loads plots of this loads data require "Results" selection.

Selected Entities
Region
Region Chain
All existing regions are listed. User selections are

highlighted.
All available Results Cases are listed. Multiple

Results Cases may be selected and these will be
highlighted.
Only the nodal vector results contained in the

selected Results Cases are displayed. If a Result
Case contains no nodal results, then all running
loads plots will be displayed as a value of zero that
runs the full length of the regions. The same behavior
will be exhibited for selected entities and region
chains.
Refer to the Plot Options form in this section for

more information on this selection.
Select File Name is only active when Output to Text

File switch is enabled. This switch will then display
the standard FIle Name Definition Form.
All Running Loads Plots and any corresponding

XYPLOT windows are deleted from the database.
Main Index
➤ ■ Done
➤➤ ➤
Plot Running Loads - Plot Options
The following forms are used to set up the parameters for a running loads plot.
This subform is accessed from the Running Loads main form and controls the
appearance of the XY plot, as well as the status of previously created plots.
These are the components that are reported in

Plot Options
the Running Load plot. By default, these are all
Load Components
ON.
Fx Fy Fz
Mx My Mz Number of evaluation points for each Region.
The default is 10 points.
Pressure to Load Algorithm
Default
Manual
Auto
Minimum Value and Maximum Value are active

when option “Integration Axis Range” is Manual;
otherwise, these are greyed out for Auto.
Plot Settings
Evaluation Points
10 Individually
Integration Axis Range:

Together By Load
Auto Together, By Component
Minimum Value 10.0 All Together
Maximum Value 20.0

Multiple curves can be Individually plotted to
Multiple Curves Plotted:
separate XY windows, plotted Together by
All Together
Load/Set, plotted Together by Component or
Previously Created Curves: all plotted on one XY plot.
As Is
Restore Default Values

As is
Remove All
OK Cancel
Previously created Running Load plots can
be left "As Is" or automatically deleted
Options include: Default (Remove All).
User
Main Index
➤ ■ Done
➤➤ ➤
A default algorithm is used to convert pressures to concentrated loads or users

may supply their own algorithms. The following form is used to select an alternate
algorithm.
Pressure Load Conversion

Algorithm: User Another algorithm option is Default. The Default
algorithm is used by MSC.Nastran for
Bilinear conversion of pressures to point loads.
CFD_algorithm
Default
Quadratic Select the user-defined algorithm to
be used for the conversion of
pressures to point loads.
OK
For a user-defined algorithm to appear on the pressure conversion algorithm form,

several conditions must be satisfied. First, a function that converts pressure loads
to nodal loads must be created. This function must have the exact arguments listed
below.
classname.function_name (xyz, pdata, nnodes, nforc)
Function
This function must have the following input and output.
Input:
REAL(3, nnodes) xyz XYZ coordinates of the corner nodes of the element
REAL(nnodes) pdata Pressure data at the corner nodes of the element
INTEGER nnodes Number of nodes in the element (3 or 4)
Output:
REAL(3, nnodes) nforce Force vector data at the corner nodes that was calculated by
the function.
INTEGER <Return Value>
The .plb file containing the user created PCL function for pressure conversion
must then be read into MSC.Patran using the !!INPUT command. Finally, the
pressure conversion algorithm must be registered on the form using the following
PCL function.
Main Index
➤ ■ Done
➤➤ ➤
airdata_pressure_register.register_alg (new_alg_name)
Function
Register a new algorithm for element pressure to nodal forces conversions.
Input:
STRING[] new_alg_name Algorithm name to be added to the user algorithm list. This
string must include the classname and function name.
Output:
None.
After the parameters for the plot have been defined, choose Apply to produce the
requested XY plots. For these plots, the first region is plotted using its X
coordinates directly. The next chained regions are included by adding their X
value onto the end. The origin of the second system locates its value in the first
coordinate system.
For example, suppose a first chained region is defined from X’=5 to X’=32, and the
second chained region covers X’’=-3 to X’’=23. The origin of the second chained
region is located at X’=29 in the first coordinate system.
Main Index
➤ ■ Done
➤➤ ➤
Data from the first chained region occupies the graph from x=5 to x=32, and the
second chained region are plotted over x=26 to x=51, as shown below.
Principal region
Z’ Chained region 1
Y’
Z’’ Y’’
5 10
15 20
X’ 25 X’’ 25
30 20
15
10
0 5
-5
List of regions in chain

Sample XY Plot:
SBMT Plot for region(s):

Inner_wing, Outer_wing
50
Load type (Force, Moment) Condition_Component:

40 Air_Load_Mx
Fuel_Mx
30
Moment
Plotted together by
20 component, for this example
10
0 10 20 30 40 50 60
X Location
Main Index
➤ ■ Done
➤➤ ➤
3.2.1 Running Loads - Theory and Methodology

This section covers the theory and methodology behind the creation of Running
Load (SBMT) plots.This section also shows the overall mathematical procedure
that is used to generate the data for SBMT plots.
SBMT Regions
The first item to be defined is the SBMT region. The SBMT region consists of finite
elements and a reference coordinate system (see figure below).
Reference
z Coord Aft
Z’ System Inboard
Outboard
Y’ Forward
y
X’
x
Global
Coord
System
SBMT Region
All data reported on a SBMT plot for this region is given in terms of the reference
coordinate system. The SBMT region covers a certain range of the reference
coordinate system. This range is from the minimum X axis value in the reference
coordinate system of the FEM nodes in the region to the maximum X axis value in
the reference coordinate system of the FEM nodes in the region.
Main Index
➤ ■ Done
➤➤ ➤
SBMT Chains
SBMT chain may be defined. The SBMT chain consists of an ordered list of SBMT
regions. These regions should be adjacent and attached pieces of structure for an
SBMT plot to give realistic results. There are no checks in MSC.SuperModel that
prevents SBMT chains from containing unattached pieces of structure (see
Figure 3-1).
Chained SBMT load region 1

RCS,
Chained SBMT region 1 Chained SBMT load region 3
Z’
RCS,
Y’ Chained SBMT region 2
Z’’ Y’’
X’
X’’
X’’’ Y’’’
Chained SBMT load region 2 Z’’’
RCS = Reference Coordinate System RCS,

Chained SBMT region 3
Figure 3-1
SBMT Plots
The procedure for generating the SBMT plot data consists of summing the loads
from the maximum X axis location in the last SBMT region in the SBMT chain back
to the minimum X axis value of the first SBMT region in the SBMT chain. These
summed loads are known as running loads.
Main Index
➤ ■ Done
➤➤ ➤
Running loads are calculated at the evaluation points for each region. The number
of points at which applied loads are summed and reported is determined by the
evaluation points box on the plot form. This number is the same for all of the
regions. Loads applied to the model that lie within the X-axis region of the
specified coordinate system(s) is included in the running load plot (see Figure 3-2).
Planes / Evaluation points

for chained region 2
Planes / Evaluation points Chained
for chained region 1 Region 2
. N
Chained .
Region 2 . = Load point
5 .
3 4
2 = Evaluation point
1
Figure 3-2
The equations used to sum the loads together for an evaluation point are as
follows.
loads
F x, eval = ∑ F x, i
i=1
Main Index
➤ ■ Done
➤➤ ➤
loads
F y, eval = ∑ F y, i
i=1
loads
F z, eval = ∑ F z, i
i=1
loads
M x, eval = ∑ M x, i + F y, i Z i + F z, i Y i
i=1
loads
M y, eval = ∑ M y, i + F x, i Z i + F z, i ( x i – x eval )
i=1
loads
M z, eval = ∑ M z, i + F x, i Y i + F y, i ( x i – x eval )
i=1
To find the beginning running load (load at the maximum evaluation point) for a
region, the running load at the minimum evaluation point of the next region in the
chain is transformed from the reference coordinate system of the next region in the
chain to the reference coordinate system of the current region and then translated
to the maximum evaluation point of the current region. If the region is the last
region in a chain then the beginning running load is zero for all terms.
Main Index
➤ ■ Done
➤➤ ➤
For the reporting of SBMT region data on SBMT plots, the first region is plotted
using its x coordinates directly. The next chained regions is included by adding
their X value onto the end of this, with the origin of the second system locating its
value in the first coordinate system.
For example, a first chained region is defined from X’=5 to X’=32, and the second
chained region covers X’’=-3 to X’’=23. The origin of the second chained region is
located at X’=29 in the first coordinate system. Data from the first chained region
occupies the graph from x=5 to x=32, and the second chained region is plotted over
x=26 to x=51.
It is very likely that two adjacent regions contain identical nodes. Therefore, the
code checks to see if SBMT regions next to each other in a SBMT chain contain
identical nodes and place forces attached to those nodes only in the region
appearing first in the list. This prevents double counting of the forces applied to
these nodes. This check is only done for adjacent SBMT regions in a SBMT chain.
No check is done for duplicate elements, therefore pressures applied to elements
present in more than one SBMT region in an SBMT chain is summed twice in the
running load calculation.
Main Index
➤ ■ Done
➤➤ ➤
3.2.2 Example of Usage

Visualizing resultant loads along the bending axis of a wing can be very helpful for
verifying that the correct loads have been applied to a model. This section gives an
example of the usage of the SBMT plotting capabilities. This example uses a
simplified wing model to illustrate the use of the SBMT plotting application.
The following figure shows the simplified wing model that was used for this
example. This model has pressure loads applied to the top surface of the wing.
Z
Y
1 X
Z Z
Y Region 1 Y Region 2
X X
Z
Y
2 X
X
Z 3 Y
Z Z
Y Region 3 Y Region 4
X X
Preparing the Model
The first step in generating an SBMT plot is to decide how many individual
integration regions are required to cover all of the wing. In this example, three
distinct integration regions with different integration axes can be identified. To
prepare the model to create these three SBMT Regions, the FEM and nodes to be
contained in each SBMT region must be put into groups and coordinate systems
with x axes corresponding to the desired integration axes.
Main Index
➤ ■ Done
➤➤ ➤
Creating Running Load (SBMT) Regions
After the model has been prepared, the Running Load regions may now be
created. This is done from the Running Loads form, accessed from the
MSC.SuperModel main menu. Set the Action to Create and the Object to Region.
To create an SBMT Region:
1. Enter the name to be assigned to the SBMT region in the SBMT Region name
box — inner_wing, outer_wing, and winglet for the three SBMT regions in
this example.
2. Press the Define Region Button
•Select the group or groups that are to make up the SBMT region being
defined.
•When the groups are selected the elements that are part of the SBMT
region are highlighted on the model. Check to make sure that the
correct elements are highlighted.
•Press the OK button to accept the region definition.
3. Select the coordinate system to define the integration axis.
4. Press the Apply button to create the SBMT region. For this example, this
procedure must be done for all three SBMT regions.
Creating Running Load (SBMT) Region Chains

After the SBMT regions have been created, the individual SBMT regions can be
chained together to fully define the integration axis. In general the order of the
regions in an SBMT chain is from the wing root (where all of the load in the wing
is transferred to the fuselage to the wing tip).
On the Running Loads form, set the Action to Create and Object to Region Chain.
To create an SBMT chain:
1. Enter the name to be assigned to the SBMT chain in the SBMT chain name
box.
2. Select the first SBMT Region inner_wing to be in the SBMT chain from the
SBMT Regions listbox. The SBMT Region should appear in the Chained
SBMT Regions listbox.
3. Repeat step 2 for all other SBMT Regions to be included in the SBMT chain.
Make sure that the order in the Chained SBMT Regions listbox is
inner_wing, outer_wing, and winglet.
4. Press the Apply button to create the SBMT chain.
Main Index
➤ ■ Done
➤➤ ➤
Creating a Running Load (SBMT) Plot
After the SBMT Regions and SBMT Chains have been created, SBMT plots can be
generated. From the Running Loads form, set the Action to Plot, Object to Applied
Loads, and the Method to Screen XY Plot.
Creating an SBMT Plot
1. Select SBMT Chain from the first option menu.

2. Select the SBMT Chain/Region total_wing from the first listbox to generate
an SBMT plot.
3. Select the toggle button Fz of the components to be plotted.
4. Press the Select Load Cases/Sets button.
•Select the individual load sets (LBCs) to be plotted from the top listbox.
In this example, no sets were selected.
•Select the Load Cases to be plotted from the bottom listbox. In this
example the Load Case containing all of the pressure loads on the wing
was selected. A curve is generated for each item selected on this form.
•Press the OK button to accept selections.
5. Enter the number of evaluation points for each SBMT region in the
Evaluation Points databox (20).
6. Indicate that Individually plotted curves is created on the same SBMT XY
plot using the option menu under the Multiple curves plotted label.
7. Using the option menu under Previously Created, select As Is for any
previously created plots.
8. Press the Apply button to generate the SBMT Plots.
Main Index
➤ ■ Done
➤➤ ➤
After the Apply button has been pressed, MSC.SuperModel calculates the SBMT
diagram data and generate the requested SBMT plots. The resulting SBMT plot
from this example can be seen below:
Condition--Component--Region:
SBMT Plot for Regions: load case 1--Fz--inner wing
inner wing, outer wing, winglet load case 1--Fz--outer wing
load case 1--Fz--winglet
0.
-15000.
-30000.
Force
-45000.
-60000.
-75000.
-90000.
-2.34 10.0 22.5 34.9 47.4 59.8 72.3
X Location (Integration Axis)
Main Index
➤ ■ Done
➤➤ ➤
Plot/LBCs/Load Summation
Load Summations are accessed by setting the Plot Method to Load Summation.
These may be performed using Entire Model, Region, or Selected Entities, but they
may not be performed over Region Chains.
LBCs
Load Tools Load Cases
Action: Plot
Results
Object: LBCs
Method: Load Summation

Entire Model
Option Region
Selected Entities
Select Region Region
Default
* Filter
User
Options
Load Components
LBC(s)
Fx Fy Fz
pressure
Mx My Mz
Default
Options ... Coordinate System
Output Coordinate Frame

Reference Point
Coord 0
[0. 0. 0.]
Sum Loads For:

Given
-Apply- Cancel OK
Reference point defines the location Given

that load summations will be
performed relative to. May be either Opposite XY Side
a physical location or a node.
Opposite YZ Side
Opposite XZ Side
Main Index
➤ ■ Done
➤➤ ➤
Plot/Load Cases/Load Summation
Load Tools
Action: Plot
Object: Load Cases

Entire Model
Method: Load Summation Selected Entities
Target: Region
Region
Select Region
Default
* Filter
User
Options
LoadCase(s) Load Components

Default
Fx Fy Fz
Mx My Mz
Default
Coordinate System
Options ...
Output Coordinate Frame
Coord 0
Reference Point
[0. 0. 0.] Sum Loads For:

Given
OK
-Apply- Cancel
Given
Opposite XY Side
Opposite YZ Side
Opposite XZ Side
Main Index
➤ ■ Done
➤➤ ➤
Plot/Results/Load Summation
Load Tools
Action: Plot
Object: Results
Method: Load Summation Entire Model
Option Region
Region
Selected Entities
Select Region
* Filter
test
Result Case(s)
Options
Load Components
Fx Fy Fz
Mx My Mz
Nodal Vector Results Pressure to Load Algorithm

Default
Default
User
Options ... Coordinate System
Reference Point Output Coordinate Frame
[0. 0. 0.] Coord 0
Sum Loads For:

Given
-Apply- Cancel
OK
Given
Opposite XY Side
Opposite YZ Side
Opposite XZ Side
Main Index
➤ ■ Done
➤➤ ➤
Selecting the Apply button from any of the previous Load Summation menus
results in the display of the following spreadsheet.
The name of the load case or load The components of the equivalent load vector
set is displayed in the first column. are displayed in the remainder of the columns.
Load Summation
Case/Set Fx Fy Fz Mx My Mz
force.1 0. 0. -7800. -2.9176E+5 2.319E+5 0.
force.11 0. 0. 3941.6 1.357E+5 -1.1702E+5 0.
force.12 0. 0. 7800. 1.9912E+5 -2.3233E+5 0.
force.13 0. 0. -1970.8 -67849. 58512. 0.
force.16 0. 0. -5850. -1.4169E+5 1.7425E+5 0.
force.19 0. 0. -3900. -1.1486E+5 1.1617E+5 0.
force.20 0. 0. -7883.2 -2.714E+5 2.3405E+5 0.
Output Coordinate System = Coord 0
Ref Point ( Coord 0 ) X = 0.00000 Y = 0.00000 Z = 0.0000
Cancel Save
The Output coordinate frame and Select Cancel to Select Save to write the load sum
the coordinates of the reference close the window. information to the Patran report
point are displayed at the bottom of file "load_sum.rpt".
the window.
Load Summation - Calculation
For forces, the load summation calculation is simply the summation of the force
vector components (transformed if necessary). The moments are calculated by
determining the cross product of the force vector and the moment arm vector
where the moment arm vector is a vector from the reference point to the node on
which the force vector is applied.
Mx dx
My = Fx F y F z × d y (Eq. 3-1)
Mz dz
Main Index
➤ ■ Done
➤➤ ➤
For pressure loads, the equivalent nodal loads must be calculated. The first step is
to transform the element face to a local coordinate system whose normal, the
vector w , is defined by the cross product of a vector from node1 to node 2, the
vector u , of the face and a vector from node 1 to node 4,
1-2
ux v x
u y = v 1-2 y (Eq. 3-2)
uz v
1-2
z
and
wx ux
wy = v 1-4
v
1-4
v
1-4 × uy . (Eq. 3-3)
x y z
wz uz
The second local direction, the vector v , is defined by taking the cross product of
w and u ,
vx ux
v y = wx wy wz × uy . (Eq. 3-4)
vz uz
The transformation matrix, λ , is created from the direction cosines between the
local system and the global system. The nodal coordinates are then multiplied by
the transformation matrix.
The pressure load, like the displacements in an isoparametric finite element, is

defined anywhere in the element (or on the element face for 3D elements) by
n
q(u, v) = ∑ qi ψi (Eq. 3-5)
where
q(u, v) = the spatial distribution of the pressure load in the local element coordinate
system.
q i = the pressures at the nodes
ψ i = the element interpolation functions.
The equivalent nodal forces are calculated from the exact integral evaluated using
Gauss-Legendre quadrature
Main Index
➤ ■ Done
➤➤ ➤
M N
q = ∫ q(ξ, η) dξ dη ≅ ∑ ∑ q(ξI, ηJ)det(J)WI WJ (Eq. 3-6)

ΩR I = 1J = 1
where
ξ, η = the element’s parametric coordinates.
q(ξ, η) = the pressure distribution in the element’s parametric coordinate system.
det(J) = the determinate of the Jacobian.
q(ξ I, ηJ) = the pressure at the integration points ξ I, η J .
W I, W J = the Gauss-Legendre integration weights.
After calculation, the nodal loads are transformed into the global system using the
transpose of the transformation matrix.
Limitations
Presently, load summation excludes any of the following types of loads:
1. Inertial loads
2. Pressures applied to the faces of 3D elements
3. Edge pressures applied to 2D elements
4. Distributed loads applied to either 1D or 2D elements.
Main Index
➤ ■ Done
➤➤ ➤
3.3 Property Data Plots

Element Property data vs. spatial location can be represented as XY plots. This
feature is useful for reviewing the variation of physical properties in the modeled
structure. Only scalar properties can be plotted.
The following Element Properties may be plotted.
•0-D elements (springs):

Stiffness K1, K2
Damping coefficients GE1, GE2
Stress coefficients S1, S2
•1-D elements (rods / bars / beams):
Area
Bending / torsion properties I11, I22, I12, J
Shear stiffness factors K1, K2
Nonstructural mass
•2-D elements (shells / plates / membranes / shear panels):
Thickness
Bending factor, transverse shear factor
Nonstructural mass
Offset
Fiber distance 1, 2
•3-D elements (solids):
No properties available for plotting
Properties not available for plotting includes:
•MATERIAL PROPERTIES and DERIVED PROPERTIES

No properties available for plotting
Main Index
➤ ■ Done
➤➤ ➤
3.3.1 Description of User Interface

Plot types for element properties are analogous to those used for making XY plots
of element results, but the X variable is limited to some type of distance.
Property Data Plots is accessible from the MSC.SuperModel main menu.

MSC.SuperModel
Version 200x
Main Menu
Loads Tools
◆ Property Data Plots

Configurations
Model Unmerge
Bar End Loads
Shear Panel Plots
Main Index
➤ ■ Done
➤➤ ➤
The forms used to create the Property Data Plots are shown below.
Property Plots
Action: Plot Airdata
Object: Element Prop
Method: Prop Vs Dist May be X,Y,Z coordinates or accumulated
Options of XY Plot
Select the global direction to be
X-Var: used as the X variable for the plot.
Dist X Y Z
Select elements for which properties are to
be plotted. A select bar should show up if
Element Ids this box is selected. The order that the
elements appear in the listbox are in the
order that they are plotted.
Property(Y)... Choose the property to be used as the Y variable

for the plot. The line below shows the currently
Selected Property(Y):
selected property.
-Not Selected-
Target Windows
* Filter
Select the target window the curves are placed

in. The user may select from the existing XY plot
Selected Window windows or type in a new name to create a new
XY plot window.
Previously created curves:

As is Determines what are done with the curves
that currently exist in the target window: As
Is or Remove.
-Apply- Cancel
Main Index
➤ ■ Done
➤➤ ➤
The user selects the element properties to be plotted from the following form,
which is updated based on the element type.
Plot Airdata
Property Types
Thickness
List of all scalar element property data

available in the current database.
OK Cancel
Main Index
➤ ■ Done
➤➤ ➤
3.3.2 Theory of Property Data Plots

This section covers the methodology and assumptions used for plotting element
properties vs. location.
Element Location Data
In this application, all location data that is put on the plots is for the centroid of the
element. The distance between elements is calculated between centroids. The X, Y,
and Z locations reported on a plot are the centroid components.
Scalar Element Property Data
If the scalar element property is the same for the entire element, then that data
value is reported on the Property Data Plot.
If the scalar element property is different for different nodes of the element, then
the code warns the user and calculate an average value. If a finite element Field is
used to define the scalar element property, then the code averages all of the node
data together to obtain a value. If the Field is any other type, the code evaluates the
Field at the centroid location of the element and report this value on the plot. The
functions used to evaluate the field are the same ones used by MSC.Patran to
evaluate Fields, as a result the interpolation methods specified for the Field are
used to evaluate that Field.
Main Index
➤ ■ Done
➤➤ ➤
3.3.3 Limitations
1. Bar and beam properties, as defined using the Beam Section capabilities, are
not supported. Specifically, if the beam "Dimensions" option is used to
derive the properties on-the-fly, these may not be plotted. If, however, the
beam "Properties" option is used to calculate beam properties from a section
definition, then these properties may be displayed. (If the beam properties
are grayed out on the Element Property - Input Data form, they may not be
used for Property Data Plots.)
2. Material properties are not supported.
3. Derived properties are not supported.
Main Index
➤ ■ Done
➤➤ ➤
3.3.4 Example Of Usage

Visualizing the properties of elements verses a spacial variable can be helpful in
verifying the simulation model. This section gives an example of the usage of the
properties vs. location plotting capabilities. This example uses a simplified wing
model to illustrate the use of the property XY plotting application.
The following figure shows the simplified wing model that was used for this
example. This model has varying thicknesses for the plate elements that make up
the wing.
Z
Y
X
Property Data Plots is accessed from the MSC.SuperModel main menu. After the
Property Data Plot is visible, set the Action to Plot action, Object to Element Prop,
and the Method to Prop Vs. Dist.
To create a Property Data Plot:
1. Select the X variable to plot properties against. Use the radio buttons to make
the choice. For this example, Dist is chosen the first time.
2. Select the elements, whose properties are to be plotted, in the order they are
to be plotted. In this example, select the highlighted elements in the
following figure. These elements should be selected from left to right one at
a time using the SHIFT and mouse click method.
Z
Y
X
Figure 2
Main Index
➤ ■ Done
➤➤ ➤
3. Press the Property(Y) button:

•From the listbox that appears on the Properties form, select the
property to be plotted Thickness.
•Press the OK button to close the form.
4. In the Selected Window databox enter the name of the window that the
curves are plotted to — Thickness XY Plot.
5. Select the way curves currently in the Selected XY plot window are to be
handled using the option menu — As Is.
6. Press the Apply button to generate the curve.
For this example, the above procedure is repeated, except in Step one X is selected
instead of Dist. After this is finished the XY plot should appear as follows:
Legend
Thickness-vs-Dist
Thickness-vs-X
12.0
10.0
8.00
6.00
4.00
2.00
0.
0. 15.0 30.0 45.0 60.0 75.0 90.0
Main Index
➤ ■ Done
➤➤ ➤
3.4 Mass Properties Management
Overview
The Mass Properties Management tool helps engineers estimate the weight of a
structure from its finite element model and to fine tune the model weight
distribution. It accomplishes this by allowing you to specify mass factors for the
model to modify its weight, and then adding quantities of element nonstructural
mass based on the factors. Factors can be applied both to groups that represent
individual structural components and to larger assemblies in the model.
Main Index
➤ ■ Done
➤➤ ➤
Access
Mass Properties Management is accessed from the MSC.SuperModel main menu.

♦ Geometry♦ FEM ♦ LBCs♦ Matls♦ Properties♦ Load Cases♦ Fields♦ Analysis♦ Results♦ Insight♦ XYPlot
SuperModel Main♦Menu
SuperModel

MSC.SuperModel
Version 200x
Main Menu
Loads Tools
Property Data Plots
◆ Mass Property Management
Configurations
Model Unmerge
Bar End Loads
Shear Panel Plots
Main Index
➤ ■ Done
➤➤ ➤
3.4.1 Procedures
Adding Mass Properties to the Model By Group
This procedure should be used to create a number of regions which have the same
mass factors.
Mass Properties Open the Mass Properties Management form by selecting it from the
Management MSC.SuperModel main menu. Set the Action to Create and Object to Mass
Prop Region. Select the By Groups method.
Group Select the groups from which the mass properties regions are to be created
in the Group frame.
Description Enter a description of the Mass Properties Region in the Description
listbox.
Mass Factors Enter the factors in the Mass Factors scroll frame. For each mass factor,
select the Enter Value option and enter the value of the factor in the
databox. The Parameter List option is available only if the Mass Properties
function has been customized by the user (see Mass Properties
Customization and Mass Factor Customization sections). The date and
time the factor was entered are recorded automatically.
Accept Select Accept to create the Mass Properties Region. The Mass Properties
Region always has the same name as the group from which it was created.
Adding Mass Properties to the Model By Selection
This procedure should be used when a number of groups need to be combined into
one region.
MSC.SuperModel main menu. Set the Action to Create and Object to Mass
Prop Region. Select the By Selection method.
Mass Properties Enter the Mass Properties Region name in the Region Name databox.
Region
Region Definition Select the Region Definition button to display a subform which are used to
select the groups which are used to create the Mass Properties Region.
Groups Select the groups which comprises the Mass Properties Region from the
Groups listbox in the Define Region subform. Select OK to accept the
groups selected.
Main Index
➤ ■ Done
➤➤ ➤
Description Enter a description of the Mass Properties Region in the Description

listbox.
Mass Factors Enter the Mass Factors in the Mass Factors scroll frame. For each mass
factor, select the Enter Value option and enter the value of the factor in the
databox. The Parameter List option is available only if the Mass Properties
function has been customized by the user (see Mass Properties
Customization and Mass Factor Customization sections). The date and
time the factor was entered and recorded automatically.
Accept Select Accept to create the Mass Properties Region.
Main Index
➤ ■ Done
➤➤ ➤
Modifying Existing Mass Properties

MSC.SuperModel main menu. Set the Action to Modify and Object to
Mass Prop Region.
Mass Properties Select the Mass Properties Region which is to be modified.
Region
Region Definition Select the Region Definition button to bring up a subform which allows
you to change the group or groups from which the region is created.
Groups can be added to or removed from the Mass Properties Region.
Mass Factors Use the Mass Factors scroll frame to change the Mass Factors. For each
mass factor to be changed, select the Enter Value option and enter the new
value of the factor in the databox. The Parameter List option is available
only if the Mass Properties function has been customized by the user (see
Mass Properties Customization and Mass Factor Customization sections).
The date and time the factor was changed are recorded automatically.
The Mass Properties Region description cannot be changed.
Accept Select Accept to modify the Mass Properties Region.
Deleting Mass Properties Regions from the Model

MSC.SuperModel main menu. Set the Action to Delete and Object to Mass
Prop Region.
Mass Properties Select the Mass Properties Region which is to be deleted.
Region
Accept Select Accept to delete the Mass Properties Region.
Applying the Mass Properties to the Model

MSC.SuperModel main menu. Set the Action to Apply and Object to Mass
Factors.
If desired, select Elements Must Have Factors in the Application Options:

frame.
Weights can be changed only by using Nonstructural Masses.
Accept Select Accept to apply the Mass Factors.
Main Index
➤ ■ Done
➤➤ ➤
Deleting Mass Factors Applied to the Model

MSC.SuperModel main menu. Set the Action to Delete and Object to Mass
Factors.
Accept Select Accept to delete the Mass Factors.
Displaying Existing Mass Properties

MSC.SuperModel main menu. Set the Action to Show and Object to Mass
Prop Region.
Mass Properties Select the Mass Properties Region which is to be displayed.
Region
Region Definition Select the Region Definition button to bring up a subform which displays
the group from which the region is created.
Mass Factors Use the Mass Factors scroll frame to view the Mass Factors. The date and
time the factor was created or changed are displayed
Requirements
Before using the Mass Properties Management function, the finite elements to
which mass factors are applied must be grouped into regions that share factors.
Material density for all elements with factors must also be defined.
Before customizing the Mass Properties Management function, the user must
program forms and algorithms for parameter lists. A separate function is required
for each type of mass factor.
Main Index
➤ ■ Done
➤➤ ➤
3.4.2 Description of Mass Properties Management Forms

A number of forms are used in the Mass Properties Management function. All of
these forms are accessed from the MSC.SuperModel main menu.
Creating a Mass Properties Region Using Selected Entities

Create
Modify
Mass Properties Delete
Action: Create Apply

Object: Region Show
Method: By Selection Note: The Mass Properties Action options: Create,
Modify and Show use similar forms.
Existing Regions
*spar* Filter Merges all selected groups into a single region
spar2-1.web using By Groups or By Selection.
spar2-1.capl
spar2-1.capu
Region name:
spar2-1.capu
Region Definition ...

Brings up form to define region (see form Define
Mass Factors Region).
- Mass Factor #2 -
From: Enter value
The number and names of mass factors.
Factor: 1.15
Date: 31-Aug-95 09:08
Adjustment
1.02
Description
-Apply- Cancel
Main Index
➤ ■ Done
➤➤ ➤
Creating A Mass Properties Region Using Groups
This is a user-customized form.
Mass Properties
Action: Create
Object: Region Region name is created automatically to be the same as
Method: By Groups the group name, with one region for each group.
Existing Regions
* Filter
spar2-1.web
spar2-1.capl
spar2-1.capu
Group
*spar2-1* Filter
wing.spar2-1.capu
wing.spar2-1.capl
wing.spar2-1.web
Mass Factors
Factors may be defined either by using a customized
- Part Mass Factor -
parameter list or by entering the factor manually.
From: Param List
Brings up a list of available algorithms that can be used
Algorithm: sheet metal ... to calculate the factor (see form Select Algorithm).
List: rib ... Brings up a list of available parameter lists for the above
Upper cap ...
algorithm. (See form Select List)
Assign:
Factor: 0.98 If a parameter list is used, options on form for the

assignment of the factor are updated by the parameter
Updated: 31-Aug-95 09:08 list, e.g. for Sheet Metal: Global, Upper/Lower Cap,
Upper/Lower Skin, Web. (see form Assignment Type)
Description
Factor: 1.15
Updated: 31-Aug-95 09:08

-Apply- Cancel
The user is given Adjustment:
the option to make a 1.02
manual adjustment
to the calculation.
Main Index
➤ ■ Done
➤➤ ➤
Subforms for Selecting a Custom Algorithm, List, and Assignment Type
The following are examples of subforms using the ability to assign factors by
customized parameter list calculations.
Select Algorithm
Available Algorithms Available parameter list algorithms,
sheet_metal_part read from a registry of algorithms.
machined_part
cast_part
OK Select Param List

Available Param Lists
rib 1
rib 2
skin
Available parameter lists for the
current algorithm.
Select Assign Method

Available Assign Method
OK
Global
Lower Cap
Lower Skin
Upper Cap
Upper Skin
Web
Available assignment types

for the current algorithm.
OK
Main Index
➤ ■ Done
➤➤ ➤
Defining a Mass Properties Region
User selects groups to be used to

create a single region. All selections
are highlighted.
If this switch is set, then all of the

entities associated with the groups
that are selected will be highlighted
in the current Viewport.
Main Index
➤ ■ Done
➤➤ ➤
Deleting a Mass Properties Region
Mass Properties
Region
Action: Delete
Mass Factors
Object: Region
Existing Regions
*spar* Filter
spar2-1.web
spar2-1.capl
spar2-1.capu
Select regions to be deleted. Updates the

FEM field used to define Mass Properties
assignments. Only those elements
associated with the region are removed
from the field or recalculated if elements are
referenced by multiple regions.
Apply Cancel
Main Index
➤ ■ Done
➤➤ ➤
Deleting Mass Factors
Mass Properties
Action: Delete Remove field created when applying
Object: Mass factors mass factors.
Change weight using:
Nonstructural Mass
For information only. Needed to know
Last Applied: which field to remove.
31-Aug-95 09:08
-Apply- Cancel
Main Index
➤ ■ Done
➤➤ ➤
Applying Mass Factors
Mass Properties
Action: Apply
Object: Mass Factors
Change weight using:

Determines how factors are implemented.
Nonstructural Mass Another option, Density Modification are added
when fields can be created for density.
Last Applied:
31-Aug-95 09:08 Keep track of the last time factors were
applied to the model.
Application options:
◆
◆ Verify factors updated Options for implementing factors. Choosing
◆ Elements must have factors the Verify Factors option (which is not
available at this time) searches through the
Mass Properties regions and verifies that at
-Apply- Cancel least one factor has been updated since the
last application. The other option determines
whether an error is flagged if an element
does not have a factor applied.
Main Index
➤ ■ Done
➤➤ ➤

The following example illustrates the basic usage of the Mass Properties
Management function. Figure 3-3 represents a section of a wing structure, that is
constructed utilizing three spars. The elements of the wing have been grouped
based on the structural components modeled. This example concentrates on spar
number 3 (Figure 3-4 and Figure 3-5), that has been grouped as spar3. The spar has
been further broken down into upper and lower spar caps (Figure 3-6), grouped as
spar3.capu and spar3.capl, a spar web (Figure 3-7), grouped as spar3.web, and
the effective portions of the upper and lower skins (Figure 3-8), grouped as
spar3.skinu and spar3.skinl. The remaining spars are similarly grouped.
The goal of this example is to apply mass factors to these groups.
Figure 3-3 Three Spar Wing Structure
Main Index
➤ ■ Done
➤➤ ➤
Figure 3-4 Spar Number 3
Figure 3-5 Spar Number 3
Main Index
➤ ■ Done
➤➤ ➤
Figure 3-6 Spar 3 Upper and Lower Caps
Figure 3-7 Spar 3 Web
Main Index
➤ ■ Done
➤➤ ➤
Figure 3-8 Spar 3 Upper and Lower Effective Skins
Create the Mass Properties Regions

1. Open the Mass Properties Management from the MSC.SuperModel main
menu.
2. Set the Action to Create, Object to Mass Prop Region, and Method to By
Groups.
3. Select the spar3.capu group in the Group frame.
4. Enter Spar3 Upper Cap in the Description listbox.
5. For each mass factor type, select the Enter Value option and enter the value
of the factor in the databoxes in the Mass Factors scroll frame. The date and
time the factor was entered are recorded automatically.
6. Select Accept to create the spar3.capu Mass Properties Region.
7. Repeat steps 3 through 6 to create four more Mass Properties Regions from
the remaining groups of spar3 (spar3.capl, spar3.web, spar3.skinl and
spar3.skinu).
Main Index
➤ ■ Done
➤➤ ➤
Modify Existing Mass Properties Regions

1. Open the Mass Properties Management from the MSC.SuperModel main
menu.
2. Set the Action to Modify, Object to Mass Prop Region, and Method to By
Groups.
3. Select the spar3.web Mass Properties Region in the region selection frame.
4. Use the Mass Factors scroll frame to change the Mass Factors. For each mass
factor to be changed, select the Enter Value option and enter the new value
of the factor in the databox. The date and time the factor was modified and
recorded automatically.
5. Select Accept to modify the spar3.web Mass Properties Region.
Main Index
➤ ■ Done
➤➤ ➤
3.4.4 Mass Properties Management Customization

Users can integrate their own custom method for calculating mass factors into
MSC.SuperModel, and then store that data in their database. This section describes
the use of a registration class to transfer data between the custom class and existing
routines. The user data documentation should be referred to for information about
storing data in the database. Forms used to enter the custom data can be registered
using the user Action-Object-Method (AOM) server.
Information about algorithms available, types of factors calculated by those

algorithms, instances of calculated factors, and the factor values themselves must
be passed back and forth between the forms for defining the Mass Properties
regions and the classes defined to manage the factor calculation algorithms. A
Registry Class was set up as an intermediary between the forms and the
algorithms to allow flexibility in the number of algorithms available in any given
MSC.SuperModel installation. Algorithms and their available assignment types
must be registered with this class so they can be displayed as available means of
assigning factors. This class is also used to get the current status of available factor
lists and the factor values themselves.
To start the data transfer process, two calls to the registry class are made when the
Algorithm Class is initialized, one to register the name and class of the algorithm,
and the other to register the types of factors available for that algorithm.
Algorithm list needed by Class X: User’s Custom

Class X Registry Class (RC) Algorithm Class (AC)
INIT:
alg name, - register algorithm
alg class name and class
register_alg: RC.register_alg
- place alg name, alg
class name into
class variables
give_alg_names:
RC.give_alg_names - obtain list of algs
.
in class variable
Done. - return alg list
Alg list,
num of algs
Figure 3-9 Transfer of Algorithm Name
Main Index
➤ ■ Done
➤➤ ➤
Factor type list needed by Class X: Custom

INIT:
Alg name,
Type array, - register factor
num types types for alg
register_asg: RC.register_asg
- Store type names in
class variable for
specified alg
Alg name
RC.give_asg_names give_asg_names:
. - obtain list of
. factor types for
. specified alg
Done. - return types
Factor type list,
num of types
Figure 3-10 Transfer of Factor Assignment Types
Instance list needed by Class X: Custom

Alg name
RC.give_1st_names give_1st_names:
. - Find class for alg
. in registry
. exec_func(AC,
. give_lists) give_lists:
. .
. - get latest list of
. instances from
. .
. user data
. - Register lists
. .
. RC.register_1st
. Alg name,
. .
. latest lists,
. num of lists
. .
Done. - return lists
List of lists,
num of lists
Figure 3-11 Transfer of the List of Available Algorithm Names
Main Index
➤ ■ Done
➤➤ ➤
Factor needed by Class X:

Alg name,
List instance,
Factor type
RC.give_factor give_factor:
. - Find alg in registry
. - Finds class AC in
. registry
. - Place instance in
. class variable
. exec_func(AC,
. send_factors:
send_factors)
. - obtain instance
. RC.give_param_list
. . List instance
. - obtain factors for
. instance
.
. . - send factors to
. . registry
. RC.receive_factors
. .
. .
. .
. - determine which
. factor to return
. - return factor
Done.
Factor
Figure 3-12 Transfer of Mass Factor Value
Outline of a User Data Management Class for an Algorithm
The following example serves as a skeleton for a class a user would need to set up
to define a new algorithm. The functions listed are required and should perform
the functions listed by the comment portions of the code:
#include massprop_appstrings.p
#DEFINE CLASSNAME user_algname

#DEFINE CLASSNAME_QUOTED "user_algname"
CLASS CLASSNAME
/*
* The algorithm data management class handles all work
* involved in storing and retrieving data associated with
* an algorithm and its associated parameter lists. It:
* - registers its availability and associated factor
* types in a registry class
* - interacts with the GUI used to set up the parameter
* lists to store and retrieve list instances
* - calculates and stores mass factors at the request of
* the mass region, via a "registry class"
Main Index * - gives a list of available parameter lists, at the
➤ ■ Done
➤➤ ➤
* request of the mass region via a "registry class"

* - provides mass factors as requested
*/
FUNCTION init()
/*
* Purpose:
* - Register algorithm in registry class:
* - Register types of factors in registry class
* - Create user data templates, if they don’t exist
*
* Input:
* (none)
* Output:
* (none)
*
* Side Effects:
* - Lets mass region GUI know that a new algorithm is
* available, and will thus appear on the list of available
* algorithms.
* - Sets up templates for later data storage
*
* External Dependencies:
* Need user data functions to store data
* Need registry class to keep track of available
* algorithms.
*
* General Description:
* To be called in the init.pcl when starting up PATRAN,
* or any other customized PATRAN initialization
*/
REGISTER_CLASSNAME.register_alg( @
/* algorithm name STRING */ algorithm_name, @
/* current class name STRING */ CLASSNAME_QUOTED)
REGISTER_CLASSNAME.register_asg( @
/* algorithm name STRING */ algorithm_name,@
/* factor types STRING ARRAY */ fact_types,@
/* number factor types INTEGER */ num_types)
IF( !template exists) ud_create_template(...)
END FUNCTION /* init */
/*
* A series of routines will follow here to manage the
* data, as needed by the GUI and the various templates
* associated with the algorithm. At minimum, this
* will include store,delete, and get functions for the
* parameter list.
*/
Main Index
➤ ■ Done
➤➤ ➤
FUNCTION store_data
END FUNCTION /* store_data */
FUNCTION delete_data
END FUNCTION /* delete_data */
FUNCTION get_data
END FUNCTION /* get_data */
FUNCTION calculate_factors ()
/*
* Purpose:
* - Needed only if it is necessary to be able to
* initiate factor calculation from the mass region
* form.
* - Calculate massproperty factors
* - Store factors in the parameter list used to
* calculate them
*
* Input:
* (none)
* Output:
* (none)
*
* Side Effects:
* - Modifies parameter list instance
*
* - Called by mass region class
* - Calls routine in mass region class to get current
* instance
*
* The calc factors function is called by the Mass Properties
* region when a factor is needed, using
* ui_exec_function(smdl_algname,"calculate_factors").
* It calls back to the Mass Properties region to get the
* name of the instance for which the factor is to be
* calculated, and then calls the algorithm to calculate
* the factors. It stores the factors in the parameter
* list once they are calculated.
*/
smdl_mass_region.give_current_instance(current_instance)
/*
* Calculate factors using whatever functions are needed.
* This can be done here or another call can be made.
*/
/*
* Store factors in the parameter list. As with
Main Index
➤ ■ Done
➤➤ ➤
* calculation, this can be done here or in another

* function, e.g. the calculation function.
*
* The class that calls this function can then get the
* factor through the registry class and the send_factor
* function in this class.
*/
END FUNCTION /* calculate_factors */
FUNCTION send_factor ()
/*
* Purpose:
* - Provide Mass Properties factors to registry class
*
* Input:
* (none)
*
* Output:
* (none)
*
* Side Effects:
* (none)
*
* Called by registry class. Uses functions in that class:
* give_param_list -- gets instance name for which factors
* are needed
* receive_factors -- sends factors back to registry class
*
* Factors will be given to the Mass Properties region
* via a call to the registry function. The mass region
* will make a call like:
* ui_exec_function(ALG_CLASS,send_factor)
* This class then gets the param list name from the
* registry class, retrieves factors for that list, and
* sends the factors back to the regisrty class.
* The registry class then provides the factor to the
* requesting function.
*/
REGISTER_CLASSNAME.give_param_list(instance)
/*
* from the specified instance, get the factors
*/
ud_get_instance(template,instance,r_data,s_data)
factor=r_data
date=s_data(n)
REGISTER_CLASSNAME.receive_factors(factor_array,date)
Main Index
➤ ■ Done
➤➤ ➤
END FUNCTION /* send_factor */
FUNCTION give_lists ()
/*
* Purpose:
* - Provide to registry class a list of available instances
* for algorithm
*
* Input:
* (none)
*
* Output:
* (none)
*
* Side Effects:
* - Registers list of parameter list instances
*
* Called by registry class
*
* This function gets a list of the current instances and
* registers it in the registry class. It is called by
* the registry class when a request is made to it for
* a list.
*/
ud_get_all_instances(template, list, num)

REGISTER_CLASSNAME.register_lst(algname, list, num)
END FUNCTION/* give_lists*/
END CLASS /* smdl_algname */
Main Index
➤ ■ Done
➤➤ ➤
3.4.5 Mass Factor Customization

The number and names of the mass factors displayed in the Mass Properties
Management forms are set by calls to the function smdl_uil_massprop_setup.
Users may customize the mass factors by writing their own function of the same
name and reading it in so that it replaces the standard function. The text of the
standard function follows as a template for customization:
FUNCTION smdl_uil_massprop_setup(num_props,names)
$
$ Purpose:
$ Establish the number and names of mass factors
$
$ Input:
$ <none>
$
$ Output:
/* Number of mass factors */ INTEGER num_props
/* Names of the mass factors */ STRING names[]()
$
$ Side Effects:
$
$ External Dependencies:
$
$ General Description:
$
$ Notes:
$ Mass factor names must be 32 characters or fewer
$
INTEGER retval = 0
write("Initializing Mass Factor variables")
/*
* Change this number to increase the number of factors
* The maximum number of factors is 10
*/
num_props = 3
IF ( num_props <= 0 ) THEN

retval = -1
ELSE
sys_allocate_array(names,1,num_props)
/*
* The number of names should correlate with num_props
*/
names(1) = "- Factor #1 -"
END IF
RETURN retval
END FUNCTION
Main Index
➤ ■ Done
➤➤ ➤
Main Index
➤ ■ Done
➤➤ ➤
Assembly and Configuration ❚ 4-157 Options
4
Assembly and Configuration
■ Introduction
■ Model Merge
■ Configurations
■ Reduced Stiffness and Mass Modeling
■ Assembly Definition and Analysis
■ Model Unmerge
Main Index
➤ ■ Done
➤➤ ➤
Introduction to Assembly and Configuration

MSC.SuperModel offers assembly and configuration tools commonly utilized in
aerospace. Assembly and Configuration is accessible from the MSC.SuperModel
main menu.

MSC.SuperModel
Version 200x
Main Menu
Loads Tools
Property Data Plots

Configurations
Model Unmerge
Bar End Loads
Shear Panel Plots
Main Index
➤ ■ Done
➤➤ ➤
MSC.SuperModel allows engineers to model and analyze large structures as an

assembly of components. The ability of MSC.SuperModel to assemble component
models in an automated procedure allows project teams to more easily manage
structural modeling tasks. MSC.SuperModel allows engineers to analyze multiple
structural configurations as defined on a single model. This chapter discusses the
Assembly and Configuration capabilities of MSC.SuperModel.
4.1 Model Merge

MSC.SuperModel uses the ability of MSC.Patran to merge databases. As assembly
models (SuperModels) are more conveniently distributed among several
component models (submodels), a global analysis of the entire structure requires
the ability to join component models. MSC.SuperModel supports a batch mode of
database merge through the Analysis Management and Job Definition
functionality.
Merging components to form an assembly structure for analysis lies at the heart of
MSC.SuperModel. Sometimes, numbering and naming schemes are desired to
more easily identity the location and source of a modeling entity.
For example, in a multi-company partnership, the prime contractor may use finite
element node and element ID’s 0 through 99,999 while subcontractor A uses
100,000 through 199,999, subcontractor B uses 200,000 through 299,999, etc. Each
team member is typically responsible for a number of components. The numbering
schemes may be further refined by component. For example, if subcontractor A is
responsible for five components, the entity numbering scheme may be evenly
divided among the five components (e.g., 100,000 - 119,999, 120,000 - 139,999,
140,000 - 159,999, 160,000 - 179,999, 180,000 - 199,999). Naming conventions may
follow the rule where unique model attributes (e.g., special component loadings)
have unique names while common model attributes (e.g., materials) have common
names. The model merge capability in MSC.Patran supports these scenarios.
Main Index
➤ ■ Done
➤➤ ➤
4.1.1 Model Merge - Interactive

The interactive model merge functionality can be accessed from two locations
under the File Manager menu: Utilities - FM Import and the UNIX Import option
on the File Manager menu.
New... CTRL N
Open CTRL O
Submit... CTRL T
$# Session file.ses.01 started recording at 25
Recent
$# Files...
Recorded by MSC/PATRAN CTRL R PM
03:36:58
$# NetLS
Close Initialization complete.
CTRL W license(s)...
Acquiring
hp, 2
Save CTRL S
Save As... CTRL A
Recover
Abort
Utilities
Administration
UNIX Import...
Export...
Session
Print...
Images...
Report...
Quit CTRL Q
Main Index
➤ ■ Done
➤➤ ➤
The following form is the FM-Utilities-FM Import form. Currently the only file
type that can be imported using this form is a PATRAN database. Other file types
(CAD geometry, PATRAN Neutral File, MSC.Nastran input file, etc.) must be
accessed using the UNIX Import option.
FM Import
Existing Files Import Options
File Hierarchy... File Filter... . File ID... Refresh List Object:Model
Current Hierarchy: MSC Air Series 100 Wing Source:MSC.Patran DB
Current Filter: * Submodel Uncompressed | | Online Unlocked
File Descriptions Current Group
Aileron: LHS, Final Sizing, w/Configurations lower skin
Flap: LHS, Final Sizing, w/Configurations MSC.Patran DB Options...
Equivalence Options...
Preview PATRAN DB...
Import File
File Description
OK Cancel
The following form is the UNIX Import form accessed directly from the FM menu.
This is the standard MSC.Patran import form.
Import
Filter Object: Model
/okinawa/user/smith/*.db Source: MSC.Patran DB
Directories PATRAN Databases Current Group

/smith/. [ ]
/smith/. default_group Displays the Current
/smith/cable.db Group into which the
/smith/Exercises
/smith/Mail MSC/PATRAN DB Options... model is imported. If a
/smith/model.db group name that does
/smith/model.out Equivalence Options...
not exist is entered, a
Preview PATRAN Database... new group is created
Import File Enable NFS Access
and identified as the
/okinawa/user/smith/ Current Group.
- Apply - Filter Cancel
Main Index
➤ ■ Done
➤➤ ➤
From the File Manager UNIX Import form, set the Object selection to Model and
Source selection to MSC.Patran DB. The Import form updates to reflect the
database import options, as well as present the available MSC.Patran databases in
each directory structure.
MSC.Patran always initializes a database to contain the group default_group.

This group is commonly used to contain the entire model’s contents while
additional groups divide the model based on functionality, user’s preference, etc.
If default_group is to contain the whole model, then it should be designated as the
Current Group on the Import form. When a submodel is imported, all the entities
are stored in the Current Group; if this group does not exist, is automatically
created.
During the import of a submodel, at least one new group is created, that contains
the incoming model’s contents. Typically this group is designated SM_XXX where
SM stands for submodel and XXX is a three-digit identifier representing the
number of components currently imported into the database (e.g., the fifth
component would result in the creation of group SM_005 that contained all of the
component’s entities).
Several automated modeling functionalities are optionally available during model

import, including naming and numbering conventions, merging of similar model
information, filtering of entities access, geometric and finite element
equivalencing. The incoming database can be previewed prior to import. Each of
these functionalities is discussed in more detail in the following sections.
Main Index
➤ ■ Done
➤➤ ➤
MSC.Patran Database Import Options

The MSC.Patran DB Import Options form is a multi-purpose spreadsheet that
allows for the specification of entity types and selected groups to be imported,
shows the minimum/maximum ID ranges of each numbered entity type in the
current database, and provides options for defining offsets and prefixes for
resolving conflicts between numbered entities and named entities, respectively.
MSC.Patran DB Import Options
Numbered Entity Offset Defaults Named Entity Prefix Defaults
Increment * Submodel = Default Offset Prefix // Submodel = Default Prefix
10000 1 10000 SM_ 001_ SM_001_
Duplicate Entity Merge Options:

Entities to Merge Upon Duplication Real Number Equality Criteria
Material Load/BC Field 3
Compare Names 0.XXXE+-YY
Element Property Load Case Group Significant Digits
Compare Names
DOF List
Specify Entities to Import and their ID Offsets and/or Name Prefixes:

Current Database Ranges
Import? Minimum ID Maximum ID Offset Name Prefix
Point All 1 250 10000 Not Used
Curve All 1 45 10000 Not Used
Surface All 1 31 10000 Not Used
Solid All 1 1 10000 Not Used
Coordinate Frame All 0 5 10000 Not Used
Plane All 1 5 10000 Not Used
Vector All 1 25 10000 Not Used
Node All 1 1231 10000 Not Used
Element All 1 1112 10000 Not Used
MPC All 1 7 10000 Not Used
User Data All *Auto Not Used

Material All Not Used Not Used Not Used SM_001_
Element Property All Not Used Not Used Not Used SM_001_
Load/BC, Load Case All Not Used Not Used Not Used SM_001_
Field All Not Used Not Used Not Used SM_001_
DOF List All Not Used Not Used Not Used SM_001_
Superelement All Not Used Not Used Not Used SM_001_
Group All Not Used Not Used Not Used SM_001_
Reset
OK Cancel
Main Index
➤ ■ Done
➤➤ ➤
Entity Numbering Control

Entity numbering control can serve two purposes:
•Resolve numbered ID conflicts between multiple databases.

•Support a process where submodels are assigned numbered ID ranges.
The second purpose is discussed in detail.
Numbered entity ID’s (geometry, finite element data) may be assigned based on
specified ranges. These ranges may vary between companies jointly working on a
product and even within a particular company, possibly based on product
component. While each individual component in an assembly may have ID’s that
begin at one, they may have to be reset to an assigned range when merged into the
assembly model. The MSC.Patran DB Import Options form supports three
methods of ID offsets: Default, Automatic and Input.
Default Offsets
Fixed increments that reflect the number of submodels previously imported. For
example, if components of an assembly are to have ID increments of 10,000 then
the first component imported would start at 10,000, the second at 20,000, etc.
Default offset schemes are specified at the top of the options form as shown below.
It is important to note that both the Increment and Submodel numbers may be
overridden; the final Default Offset is the product of the Increment and Submodel
number.
Define the offset increment for each submodel. This

is the amount the default offset is increased following
each successful import.
The default offset is the

increment times the
submodel number.

10000 1 10000 SM_ 001_ SM_001_
The submodel number is

incremented following each
successful import. This value
can be changed by the user.
Main Index
➤ ■ Done
➤➤ ➤
The Default numbering scheme may be used for one or more of the numbered
entity types. To apply the Default Offset to all numbered entities, select the ID
Offset heading cell.

Import? Minimum ID Maximum ID ID Offset Name Prefix
Material All 1 250 10000 Not Used
The Offset Options form appears. Select the Default Offset Option and choose the
Apply button. All the numbered entity offsets uses the Default Offset numbering
scheme.
Offset/Prefix Options
Offset Option
◆ Default
◆
◆ Automatic Set the Offset Option to Default. Choose the
Apply button to use the Default numbering
◆
◆ Input scheme defined at the top of the form.
Offset Value
The Offset Value box is disabled for the
Default method (i.e., no input is required).
Reset
-Apply- Close
If a Default numbering scheme is desired for selected entity types, select one or
more databoxes and select the Default method.
Main Index
➤ ■ Done
➤➤ ➤
Automatic Offsets
Use the next highest entity number available as a starting point. Therefore, all
entities appears sequentially numbered with no ID gaps to distinguish
components. Automatic Offsets may be applied to all entity IDs or selected entity
types, just as with the Default Offset previously described. To apply an Automatic
numbering scheme, select the Automatic Offset Option and press the Apply
button.
Offset Option
◆
◆ Default
◆ Automatic Set the Offset Option to Automatic and press
the Apply button.
◆
◆ Input
Offset Value
The Offset Value box is disabled for the
Automatic method (i.e., no input is required).
Reset
-Apply- Close
Main Index
➤ ■ Done
➤➤ ➤
Input Offsets
Allow the user to manually specify the ID offset value. One application of Input
Offsets would be if components are originally numbered not starting with one but
rather at their desired offset value as when assembled into the final configuration;
in this case, an Input Offset of zero is required to indicate that the imported entity
ID’s are to remain unchanged. As with Default and Automatic Offsets, an Input
Offset may be applied to all entity IDs or selected entity types. To apply an Input
numbering scheme, select the Input Offset Option, supply the Offset Value and
press the Apply button.
Offset Option
◆ Default
◆
◆ Automatic Set the Offset Option to Input, provide the
Offset Value and press the Apply button.
◆ Input
Offset Value
Type the offset value in this databox.
Reset
-Apply- Close
Named Entity Prefix

Entity naming control can serve two purposes:
•Resolve entity name conflicts between multiple databases.

•Support a process where submodels are distinguished through a naming
convention.
The later purpose is discussed in detail.
Element properties, materials, loads/boundary conditions, groups, fields and

Load Cases are all named entities. Depending on modeling practices, it may be
desirable to distinguish the source of named entities in an SuperModel (e.g., by
contractor, project engineer, submodel, etc.). The MSC.Patran DB Import Options
form supports two methods of distinguishing named entities by name prefixes:
Default and Input.
Main Index
➤ ■ Done
➤➤ ➤
Default Prefixes
Typically a combination of fixed leading text concatenated with the imported

submodel number (i.e., SM_005_ for the fifth imported submodel). These prefixes
is always be applied unless the optional merge duplicate toggle is enabled for one
or more named entities (see discussion below). Default prefix schemes are
specified at the top of the options form. It is important to note that both the
Increment and Submodel numbers may be changed.
The default prefix is a

The alphabetic portion of the default prefix (need
concatenation of the
only start with a letter). The default, SM_,
prefix and submodel
indicates submodel.
specifications.

10000 1 10000 SM_ 001_ SM_001_
The submodel number is The submodel number in the form of a

incremented following each string. The user may change this value
successful import, but may be or nullify it, but it is updated whenever
changed by the user. the integer form of the submodel
number is changed.
The Default naming scheme may be used for one or more of the named entity
types. To apply the Default Prefix to all named entities, select the Name Prefix
heading cell.

Material All Not Used Not Used Not Used SM_001_
Main Index
➤ ■ Done
➤➤ ➤
After selection of one or more cells under Name Prefix, the following prefix control
form appears.
Prefix Option
◆ Default Set the Prefix Option to Default and press the

Apply button to use the Default naming
◆
◆ Input scheme defined at the top of the form.
Prefix Value
The Prefix Value box is disabled for the
Default method (i.e., no input is required).
Reset
-Apply- Close
If a Default numbering scheme is desired for selected entity types, select one or
more databoxes and select the Default method.
Main Index
➤ ■ Done
➤➤ ➤
Input Prefixes
Allows the user to manually specify the Prefix. An application of the Input value
is to enter a blank value because the named entity types already reflect their
source, etc., in the respective submodels (i.e., their names are already unique at the
submodel level). As with Default Prefixes, an Input Prefix may be applied to all or
selected named entity types. To apply an Input naming scheme, select the Input
Prefix Option, supply the Prefix and press the Apply button.
Set the Prefix Option to Input, supply the

Prefix Option prefix value and press the Apply button.
◆ Default
◆ Input
Prefix Value
Enter the Input Prefix Value here or leave the
box blank. This box is only available for the
Prefix Option “Input”.
Reset
-Apply- Close
Submodel Numbering
As previously discussed, numbered and named entities may be distinguished by
a default convention that involves a submodel numbering scheme. The submodel
number is a count of successful database imports. It is, however, extracted from the
prefix used on the groups from previous successful imports. For example, if Group
default_group was previously imported with prefix SM_003_, then the new group
is named SM_003_default_group. That prefix is subsequently used to determine
the submodel number for the next import, where the maximum is tracked for all
groups. So, the SM_003_ prefix indicates the maximum submodel number is 3;
therefore the submodel number for the next import is 4. As a result, if the user
chooses to blank out the submodel portion of the prefix, or uses a non-numeric
convention, then the submodel number will always be one.
Main Index
➤ ■ Done
➤➤ ➤
Duplicate Entity Merge Options

Submodels comprising a SuperModel typically have common modeling attributes,
including materials, element properties, loads/boundary conditions, and Load
Cases. It is highly desirable to provide a mechanism for merging these common
model attributes during the assembly of a SuperModel. The reasons for merging
include database storage efficiency and assimilation of loads/boundary
conditions for subsequent analysis.
Groups, Element Properties, Materials, Fields, loads/Boundary Conditions and

Load Cases may all be optionally merged during submodel import. The default
operation for each of these data types is to merge common data. The following
criteria must be satisfied for two submodel data attributes to be merged:
Attribute Merge Criteria
Group Same name.

Element Property Same name.
Same type (e.g., 2D-Membrane).
Same data values within specified significant digit criteria.
Any associated Fields must have the same type.
Material Same name.
Same type (e.g., Isotropic).
Same data values within specified significant digit criteria.
Any associated Fields must have the same name and type.
Loads/Boundary Same name.
Condition
Same type (e.g., Force).
Same LBC scale factor value.
Equivalent LBC coordinate system (cartesion, cylindrical, spherical).
Must have all scalar and vector data defined using either constants or
fields— if a mixture of constant scalar, vector and/or fields exists, the
merge is not allowed.
For LBCs with only constant scalar/vector data, these data values
must be equal within the specified significant digit criteria.
For LBCs with only field data: (a) Fields must be of the same type; (b)
Non-discrete finite element fields must have identical contents.
Load Cases Same name.
Same type (e.g., Static).
Main Index
➤ ■ Done
➤➤ ➤
Attribute Merge Criteria
Field Same name.

Same type.
Identical contents.
The MSC.Patran DB Import Options form contains a section for controlling the
optional merge operation. The following shows that each named entity type has an
ON/OFF toggle. By default, these toggles are ON.
Duplicate Entity Merge Options:

Entities to Merge Upon Duplication Real Number Equality Criteria
Material Load/BC Fields 3
Compare Names
Element Property 0.XXXE+-YY
Load Case Group
Compare Names Significant Digits
DOF List
If a merge toggle is OFF, or the merge attempt fails, then the specified entity prefix
is inserted in front of the name, and a new database entity is created to hold the
data.
The Real Number Equality Criteria is used to determine when two real properties
(scalar or vector components) are close enough in value to be assumed equal. Near
equality is determined by comparing digits of the two numbers in normalized
exponential form, from left to right and discarding leading zeroes, up to the
specified number of significant digits. Of course, if the two numbers do not share
the same exponent, then they are not considered equal. For example, if Significant
Digits is set to 3, then 0.234516E+08 and 0.234925E+08 are considered equal,
whereas 0.233925E+08 and 0.234925E+08 are not.
Main Index
➤ ■ Done
➤➤ ➤
Entity Filtering During Import

Entities of different types (e.g., geometric surfaces, finite elements, groups) may be
entirely or partially imported or excluded from import. The import column
indicates which entities of a given type are to be imported from the import
database. The options are All, None or List.
If the Import? cell or multiple cells from the Import column are selected, the values
for those cells are toggled from All to None, or vice-versa.
If a single cell is selected, the user then has the additional ability to specify which
numbered or named entities to import by using the Input toggle.
Import Filter Options Indicate whether All, None, or an Input list of the
corresponding entity types is to be imported. If
Entities to Import the switch is set to Input, then the <entity> List
◆ All
databox is enabled, so a list may be manually
input. The spreadsheet cell is updated with a
◆
◆ None return or Apply selection.
◆ Input
<entity> List
The <entity> List label is modified, depending on
the entity type (e.g. Point List). Specify a list of
Point 1:10
entities of the current type to be imported.
Preview PATRAN Database...

Select this button to preview the contents of the
MSC.Patran Database. If no file name has been
Reset
selected in the Import form, then an intermediate
form is displayed, asking for a database to be
-Apply- Close
selected.
Main Index
➤ ■ Done
➤➤ ➤
Current Minimum ID and Maximum ID Information

The Minimum ID and Maximum ID columns show the range of IDs for the
corresponding entity type in the current database. These values may be used to
decide what offset values are most appropriate for that entity type; this would
typically be the case when the Input method of specifying entity numbers was
being used versus the more automated Default numbering convention.

There is no similar information for named entities.
Main Index
➤ ■ Done
➤➤ ➤
Automatic Finite Element Node and Geometry Equivalencing

Submodel integration requires that, at minimum, finite element nodes on the
boundary be stitched together with the other previously imported submodels.
Automatic equivalencing of finite element nodes and geometry between
submodels may be invoked during submodel import through the Equivalence
Options form, accessible from the Import/PATRAN DB form.
Equivalence Options
Equivalence Nodes/Geometry
Nodes
Indicates whether nodes and/or geometry are to
Geometry be automatically equivalenced during import.
Tolerance Method
◆ Tolerance Cube Indicate the tolerancing method to be

◆ Tolerance Sphere employed. This applies only to nodal
equivalencing. The default is Cube.
Tolerance Source
◆ Current Database (.005)
◆
◆ Import Database (.003) Define the tolerance value by choosing either
the current database value, the import
◆
◆ Input Value
database value, or manually entering a new
Tolerance value. Note that the import database value is
only shown if a preview has been done on the
import database.
Only entities that are common between the current model and the import
submodel are considered for equivalencing. If duplicate entities in either model
are found, but none of those duplicates belong to the opposing model, then no
action is taken. Equivalencing does not occur between entities originally from the
current database or import submodel.
The finite element nodes that are equivalenced during submodel import are
highlighted on successful import completion. A text report detailing the
equivalenced entities can be requested on the Equivalence Options form.
Main Index
➤ ■ Done
➤➤ ➤
Loads and Boundary Condition Merge Rules

A special set of rules and options have been implemented for the case when two
or more Loads/Boundary Conditions are to be merged and nodes from the current
model and import submodel belonging to a merged LBC set are also to be
equivalenced. See Figure 4-1.
LBC: F1 LBC: F1
1
10
2
11
Current Model 3
(Primary) 12
Import Submodel
(Secondary)
Figure 4-1
In Figure 4-1, nodes 1 and 10, 2 and 11, 3 and 12 are to be equivalenced.
Additionally, the LBC set F1 from the two models is to be merged. The discrete
forces applied to the boundary nodes are intentionally shown as unique at each
node. This example is referenced in subsequent discussions explaining the merge
rules.
The only LBC data that is considered for combination in this particular example is
when it is defined using Fields. Fields other than Discrete Finite Element must be
identical in their definition, but not necessarily their name (i.e., they must have the
same PCL function describing the field); as their contents must be identical, nodes
along the boundary remains unchanged and therefore present a trivial condition.
The more interesting condition is when a discrete finite element field exists along
a boundary with differing values.
Main Index
➤ ■ Done
➤➤ ➤
LBCs that contain only constant scalar or vector data, not defined with fields, are
not combined when nodes are equivalenced. Rather, the application regions in all
effected LBCs are updated to reflect the equivalenced node numbers. This design
limitation is intentional because resolving constant valued LBCs when nodes are
equivalenced along a boundary would require the creation of a new LBC to model
the LBC along the submodels interface.
If LBCs satisfying the rules in the equivalence table previously discussed exist and
they contain boundary nodes that are to be equivalenced and the LBC data is
described using discrete finite element fields, then a set of LBC merge rules is
followed. These merge rules are accessed from the Import/PATRAN DB
Equivalence Options form.
Equivalence DFEM Loads/BCs/Props This toggle must be enabled to allow the LBC
Combine DFEM Fields merge criteria for Discrete Finite Element
Fields to be used during nodal equivalencing.
DFEM Boundary Conditions
◆ Use primary BCs only Controls displacement boundary conditions.
◆ Add coincident node BCs
DFEM Vector Loads
◆ Use primary loads only Controls vector load conditions.
◆ Add coincident node loads

DFEM Scalar Loads Controls scalar load conditions.
◆ Use primary loads only
◆
◆ Add coincident node loads
◆ Average all data
OK Cancel
Two options are available for both displacement boundary condition and load
condition data defined using vectors in a discrete finite element field.
•Primary vector overwrites the secondary - useful when displacement boundary

conditions are modeled along submodel boundaries.
•Primary and secondary vectors are added - useful when an applied load is
initially divided along submodel boundaries.
For loads and boundary condition data defined by scalar data in a discrete finite
element field, three options are available:
Main Index
➤ ■ Done
➤➤ ➤
•Primary scalar overwrites the secondary.

•Primary and secondary scalars are added.
•Primary and secondary scalar values are averaged.
A special case is accounted for when the option for vector data is add and for scalar
data is either add or average. This is the case where the nodes to be equivalenced
both exist in the same discrete finite element field. In this case, the add or average
logic is ignored and the overwrite logic is always applied.
Main Index
➤ ■ Done
➤➤ ➤
Determination of Analysis Coordinate System at Equivalenced

Nodes
A special set of rules have been implemented to determine the analysis coordinate
system at equivalenced submodel boundary nodes. The existence of LBCs at one
or both nodes to be equivalenced affects the final analysis coordinate system.
Table 4-1 Coordinate System Merge Rules
Analysis CS at Primary Analysis CS at Analysis CS at Warning/Fatal
Node Secondary Node Equivalence Node Message Type
Global Global Global None
Local-1 Local-1 Local-1 None
Global without BC Local without BC Global Warning
Global without BC Local with BC Local None
Global with BC Local without BC Global Warning
Global with BC Local with BC Fatal
Local without BC Global without BC Local Warning
Local without BC Global with BC Global Warning
Local with BC Global without BC Local None
Local with BC Global with BC Fatal
Local-1 without BC Local-2 without BC Local-1 Warning
Local-1 without BC Local-2 with BC Local-2 Warning
Local-1 with BC Local-2 without BC Local-1 Warning
Local-1 with BC Local-2 with BC Fatal
The following terminology is used in the Coordinate System Merge Rules table: (a)
Local -1 = Local coordinate system, (b) Local-2 = Local coordinate system other
than Local-1, (c) Local = any local coordinate system.
Main Index
➤ ■ Done
➤➤ ➤
MSC.Patran Database Preview

Prior to submodel import, the MSC.Patran database contents may be previewed;
currently, the information provided includes the number of each entity type, and
for numbered entities their minimum and maximum IDs. This information may be
accessed from the Import form, from the numbered entity ID Offset Options form,
or from the named entity Prefix Options form.
The database name is retrieved from the Import form. If a valid name has not been
provided, the user is prompted for a proper database name.
A spreadsheet displaying the quantity, minimum

ID, and maximum ID for each entity type.
Preview PATRAN Database
PATRAN Database File Name

/local/users/smith/part2.db
Entity Type Quantity Minimum ID Maximum ID

Point 250 1 250
Curve 45 1 45
Surface 31 1 31
Solid 1 1 1
Coordinate Frame 5 1 5
Plane 5 1 5
Vector 25 1 25
Write to Report File
Report File OK
patran.rpt
Indicate whether to generate a report file with this

information when the form is closed, and the name
of the report file.
Main Index
➤ ■ Done
➤➤ ➤
4.2 Configurations
Overview
The Assembly and Configuration module is used during analysis to manipulate

parts of a structure into new positions without changing the original model. This
can be used to analyze any structure with moving components, such as an aircraft
with control surfaces or an actuated arm on a back-hoe. The transformations are
performed automatically when a job is submitted and the results are viewed on the
undeformed model.
Procedure
1. From the SuperModel main menu, select Configurations.
2. Set the Action to Create and Object to Configurations.
3. Define the configuration from: the group to be transformed, the load cases to
be moved with it, and how the transformation is to take place. Any
intermediate structure MUST be a subset of the group being transformed.
Give it a name and select Apply. Repeat until you have created all the
configurations you need for your job.
4. From the Configurations form, set the Action to Associate and Object to
Configurations.
5. Link the configurations you have defined to the load cases by selecting the
load case and then the configurations associated with it. Use the switch
labeled Configure Automatically to turn on and off automatic manipulation
of the model during job submittal. If the switch is disabled, a type of check
run is performed where all the appropriate subcases are formed, but none of
the defined configurations occur. Only one analysis job is submitted for this
check run versus one for each configuration if the switch is enabled. Select
Apply to save the configuration to load case link and the setting of the
Configure Automatically switch.
6. Configuration of the model is performed on a copy of the database when the
job is submitted. The results are read back into the baseline model (initial
configuration).
Main Index
➤ ■ Done
➤➤ ➤
Requirements and Limitations

1. If you are submitting a merged model, the configurations must be defined in
the submodels that have the rotating and/or translating pieces.
2. Any intermediate structure MUST be a subset of the group being
transformed. The intermediate structure connects the moving structure to
the static structure (i.e., an actuator of a wing flap). It also must be a single
element, connecting the rotating structure to the parent structure; i.e. any
actuators must be modeled using a single bar element. There is currently no
check to confirm either of these circumstances. In addition, element
properties of intermediate structure do not get rotated along with the
elements, so property definitions for the intermediate elements should be
valid for any position in the rotation plane. For example, when bar
properties are defined, the vector used to orient the beam should be parallel
to the rotation axis.
3. Geometry in the intermediate structure is not reconnected along with the
FEM. This makes the model look different than what you would expect
when you watch it move during an interactive submittal, but does not affect
the finite element run.
4. You must have the switch Configure Automatically toggled ON (from the
Associate Configuration action and object on the SuperModel form) for the
configuration to be performed automatically.
5. The module does not currently have a capability to perform chained
rotations, i.e. transformations of parts of larger pieces that are themselves
transformed. Examples of this would be a trim tab on an airplane flap or a
claw on the end of a rotating arm.
6. Loads and boundary conditions on rotating components MUST be carefully
applied. LBCs applied to the finite element mesh are correctly transformed.
LBCs applied to the geometry, that is not part of the transformed group, is
not properly applied to the transformed finite element mesh. In addition, the
LBC set name used for the loads on the component must be unique so that it
does not get renamed during the merge.
7. Currently, the capability does NOT exist to preview the transformation. If
you want to check the transformation, you need to submit the job and watch
it take place, or create a new model from the MSC.Nastran results file.
Main Index
➤ ■ Done
➤➤ ➤
4.2.1 Technical Operation

When you submit a job through SuperModel (action Submit on the Analysis form),
the configuration module looks at the load cases for any associated configurations.
Based on the configurations, a job is created for the different combinations of
configurations. For example, if you submit an analysis of an airplane with the
following subcases (load cases) and the listed associated configurations:
Load Case: Takeoff Landing Pull up Cruise 1 Cruise 2

Configs: flaps_up flaps_down flaps_up (none) (none)
gear_down gear_down
The above job would result in four analysis decks:
•One deck containing the no-configuration subcases (Cruise 1 and Cruise 2)

•Three other decks, each containing one of the other load cases.
This is done because no two other load cases share common sets of configurations.
If you are running MSC.Patran outside of File Manager, the configuration routines
make a copy of the database before submitting the job and do all manipulations in
this copy. If you are using File Manager, then the module opens the database for
read-only privileges so that it is automatically deleted when closed. The routines
redefine the job so that only the required load cases are run in the analysis, submit
the job, and delete the database copy (outside File Manager). Instructions are sent
to the Analysis Manager to read the results back into the original (initial
configuration) database.
Component Transformation
The configuration module performs component transformation using the Group

Transformation functionality in MSC.Patran. The module uses settings in this
function to delete the original group and use original entity ID’s where possible,
and also transforms the Element Properties. You are given the option to copy or
transform Loads and Boundary Condition sets along with the group, as well as the
opportunity to specify those specific load sets that is affected. However, this is
currently only valid for vector-type loads, such as forces and moments.
Main Index
➤ ■ Done
➤➤ ➤
Configuration Synchronization
If you have PCL functions to integrate with the configuration process, they must
be registered. An example of this would be a function to check the load balance on
a model before and after transformation, and to apply a corrective load to maintain
the balance. Functions can be called both immediately before and after the
configuration. The following call is used to register those functions:
cgsa_submdl_sync_mgr.register (when, user_class_name, user_func_name)
Function
Function called to register a function for execution. Execution will be performed via a
ui_exec_function(user_class_name, user_func_name)
Input:
STRING[] when When to execute function (BEFORE or AFTER)
STRING[] user_class_name Class in which to execute function
STRING[] user_func_name Function to execute
Output:
INTEGER <Return Value> Zero for success, nonzero for error
Because information cannot be passed when the configuration class calls your
function, you must call back to it to get information about the transformation. The
following function can be used to get that information.
cgsa_submdl_sync_mgr.get_config_info (config_name, group, method, params,

load_sets, num_load_sets, lbc_movement,
load_cases, num_load_cases)
Input:
None.
Output:
STRING[] config_name Name of configuration
STRING[] group Group being transformed
STRING[] method Method used for transformation (POSITION or ROTATE)
STRING[] params Parameters for transformation
STRING[]() load_sets Load sets involved in transform
INTEGER num_load_sets Number of load sets
STRING[] lbc_movement How LBCs are moved (COPY or TRANSFORM)
STRING[]() load_cases Load cases being analyzed (add any corrective LBCs to these)
INTEGER num_load_cases Number of load cases
INTEGER <Return Value> Zero for success, nonzero for error
Main Index
➤ ■ Done
➤➤ ➤
In the routine from which you call this function, you should include the file
jobdef_appstrings.p and declare your arguments as follows:
STRING config_name[MAX_CONFIG_NAME_LEN]
STRING group[MAX_GROUP_NAME_LEN]
STRING method[VIRTUAL]
STRING params[VIRTUAL](TRANSFORM_PARAMS)
STRING load_sets[MAX_LBC_NAME_LEN](VIRTUAL)
INTEGER num_load_sets
STRING lbc_movment[MAX_MOVE_LEN]
STRING load_cases[load case_LEN]
If the jobdef_appstrings.p include file is not available, the following values may
be used:
MAX_CONFIG_NAME_LEN 32
MAX_GROUP_NAME_LEN 32
TRANSFORM_PARAMS 6
MAX_LBC_NAME_LEN 32
MAX_MOVE_LEN 9
LOADCASE_LEN 80
Main Index
➤ ■ Done
➤➤ ➤
4.2.2 Description of User Interface Forms

The Configurations menu is available from the MSC.SuperModel main menu, as
shown below.

MSC.SuperModel
Version 200x
Main Menu
Loads Tools
Property Data Plots

◆ Configurations
Model Unmerge
Bar End Loads
Shear Panel Plots
The forms and the functions they perform are described on the following pages.
Main Index
➤ ■ Done
➤➤ ➤
Creating a Configuration
The following form is used to create a new configuration, which must then be
associated with a load case to be performed.
Configurations
Create
Action: Create
Modify
Object: Configuration Delete
Associate
Available Configurations
* Filter
flaps_10deg_down
flaps_15deg_down List of currently defined configurations.
flaps_5deg_up
New Configuration Name

flaps_10deg_up Enter a name for the configuration.
Target Group to Transform

flap_and_actuator
Group to be transformed during the
Change Target Group... configuration.
Intermediate Structure Group
actuator Structure for which nodal connections are to
be reset after transformation, such as
Intermediate Structure... actuators. This group must be contained by
the target group.
Associated LBC’s
Movement: Transform Loads and boundary conditions to be moved
along with the target group. Movement
* Filter determines whether forces are rotated along
flap_load_10deg_down with the structure (Transform) or follow it while
flap_load_15deg_down maintaining their orientation (Copy).
wing_load
Define Transformation
Apply Cancel
Main Index
➤ ■ Done
➤➤ ➤
Modifying a Configuration
The following form is used to modify an existing configuration, which must be

associated with a load case to be performed.
Configurations
Action: Modify
Object: Configuration
* Filter Select a configuration to modify from a list
flaps_10deg_down of those currently defined.
flaps_15deg_down
flaps_5deg_up
New Configuration Name Enter a new name for the configuration

flaps_10deg_up being modified.

flap_and_actuator Change other information as desired, and
select Apply to take effect.
Change Target Group...

actuator
Intermediate Structure...
Associated LBCs
Movement: Transform
* Filter
flap_load_10deg_down
wing_load
Apply Cancel
Main Index
➤ ■ Done
➤➤ ➤
Deleting a Configuration
The following form is used to delete an existing configuration.
Configurations
Action: Delete
* Filter
flaps_10deg_down
flaps_15deg_down
flaps_5deg_up
Select configurations to delete from
a list of those currently defined.
To be deleted
flap_load_15deg_down A list is kept of the selected configurations.
wing_load To remove a configuration from the To Be
Deleted list, select and apply.
Apply Cancel
Main Index
➤ ■ Done
➤➤ ➤
Defining a Target Group for Transformation
The following subform is available from the Create/Modify Configuration forms,

and is used to select the target group to be transformed.
Use this form to select the group you are going to transform.
Change Target Group
Select Target Group
* Filter
Actuators
Flap
Flap and actuators
Lower Skin
Upper Skin
Wing
Cancel
Main Index
➤ ■ Done
➤➤ ➤
Defining a Group Representing Intermediate Structure
The following subform is available from the Create/Modify Configurations forms,

and is used to select the intermediate structure to be reconnected after the
configuration.
Select a group containing elements connecting the transformed group to the rest of
the structure. The intermediate structure MUST be a subgroup of the target group
being transformed, and also MUST be a single element connecting the transformed
structure to the parent structure. Properties for the element do not get
transformed, therefore, make sure that the property definition is either non-
directional or is defined in such a way that it is still correct after the transformation
takes place. With bars, this can be done by making the vector used to define the bar
orientation parallel to the rotation axis.
Intermediate Structure
Select Intermed Structure
* Filter
Actuators
Flap
Flap and actuators
Lower Skin
Upper Skin
Wing
Cancel
Main Index
➤ ■ Done
➤➤ ➤
Defining a Transformation - Position
The information defined for each transformation technique correlates to that

required for the MSC.Patran Group/Transform.
Position
Technique: Position
Rotate
Original Position
Point 1 [0 0 0]
Point 2 [0 0 0]
Point 3 [0 0 0]
Destination Position
Point 1 [0 0 0]
Point 2 [0 0 0]
Point 3 [0 0 0]
OK Cancel
Main Index
➤ ■ Done
➤➤ ➤
Defining a Transformation - Rotate
The information defined for each transformation technique correlates to that

required for the MSC.Patran Group/Transform.
Technique: Rotate
Reference Coord. Frame
CoordinateFrame 0
Axis
Coord 0.3
Rotation Parameters
Rotation Angle 90.0
Offset Angle 0.0
OK Cancel
Main Index
➤ ■ Done
➤➤ ➤
Associating Configurations to a Load Case
Configurations
Action: Associate
Available Loadcases
* Filter
Abort_landing
Landing
Take_off
Roll
Select a load case, then make selects
in the configuration list to indicate the
Associated configs associated configurations.
flaps_10deg_down
flaps_15deg_down
flaps_5deg_up
airbrake_up
Configure automatically Determines whether the configuration is

performed when the job is submitted.
Apply Cancel
Apply saves the current state of the associations.
Main Index
➤ ■ Done
➤➤ ➤
Example
Figure 4-2 shows an example on how to rotate the flap structure attached to the
wingbox on the right side of the model. The flap will be rotated down 10 degrees
about the hinge line axis defined by points (85, 80, 0) and (100, 80, 0).
Figure 4-2 Wing Before Configuration
Main Index
➤ ■ Done
➤➤ ➤
Configurations
Action: Create
* Filter
STEP 1: Type in
flap_down under New Change Target Group
Configuration Name.
New Configuration Name Select Target Group
flap_down * Filter
Actuator
flap_and_actuator STEP 2: Select the target Flap
Truss
group flap_and_actuator. default_group
Change Target Group... flap_and_actuator
flap_top
Actuator
Intermediate Structure...
STEP 3: Select the
Associated LBCs intermediate structure Intermediate Structure
Movement: Transform group Actuator. Select Intermed Structure
* Filter * Filter
flap_load_-25 Actuator
Flap
Truss
default_group
flap_and_actuator
flap_top
-Apply- Cancel
More ➠
Main Index
➤ ■ Done
➤➤ ➤
Intermediate Structure... STEP 4: Set the Movement

option to Transform.
Associated LBC's
Movement: Transform
* Filter
STEP 5: Select the LBC
flap_load_-25 flap_load_-25.
STEP 6: Select this button to access

Define Transformation the Define Transformation form.
-Apply- Cancel
STEP 9: Click Apply to Define Transformation

create the configuration.
Technique: Rotate
Reference Coord. Frame

CoordinateFrame 0
Axis
Cancel
STEP 7: Define the rotation {[85. 40. 0.][100. 40. 0.]}
axis {[85. 80. 0.] [100. 80. 0.]}
Rotation Parameters
STEP 8: Define the Rotation Rotation Angle -10.0

Angle of -10 degrees.
Offset Angle 0.0
OK Cancel
Main Index
➤ ■ Done
➤➤ ➤
Configurations
Action: Associate STEP 10: Change Action to Associate.
Available Load Cases

* Filter
Default STEP 11: Select load case wing_load_-25 to

wing_load_-25
wing_load_0 associate to the flap_down configuration.
Associated configs
flap_down
STEP 12: Select flap_down configuration.
Configure automatically STEP 13: Make sure the Configure

Automatically switch is toggled ON.
-Apply- Cancel
STEP 14: Select Apply to create the

association between load case wing_load_-25
and configuration flap_down. MSC.SuperModel
then automatically performs the configuration if
the load case is used in an analysis.
Main Index
➤ ■ Done
➤➤ ➤
If you submit the job interactively, you will be able to see the model transform to
reflect the analyzed configuration model for evaluation. Answers for the
configured model are read back into the original database (initial configuration). If
you want to view the reconfigured model, you must create a new model by
reading the results and model information from the results file into an empty
database.
Figure 4-3 Wing After Configuration
Main Index
➤ ■ Done
➤➤ ➤
4.3 Reduced Stiffness and Mass Modeling

Design studies often focus on changes to a single component (i.e., aircraft wing)
while the remaining components retain a constant design (e.g., the fuselage,
vertical tail, etc.). Each design study requires a structural analysis or analyses to
understand the effect of the changes. Depending on model sizes and computing
costs, a high penalty on throughput and costs can be realized by analyzing
structure that does not change between design studies. To increase throughput
and potentially decrease computing costs, users may employ the reduced stiffness
and mass modeling technology offered in MSC.SuperModel.
Reduced stiffness and mass modeling can substantially decrease model analysis
time by reducing the total number of degrees of freedom. Reduced stiffness and
mass models created from one or more components can be used during analysis as
a boundary condition to the attached structure. For example, a stiffness matrix can
be generated for an aircraft fuselage and subsequent design studies and re-analysis
of the wing model can use this reduced model as the boundary condition at its root
and eliminate the need and time necessary to redundantly analyze the fuselage
structure.
Use of the current MSC.SuperModel reduced stiffness and mass models is similar
to the MSC.Nastran Superelement technology, but more simplified. Less
bookkeeping is associated with its use; however results cannot be recovered from
elements in the reduced structure.
A reduced stiffness matrix (RSM) represents the stiffness matrix of a component at

degrees of freedom specified by the user, and a reduced mass matrix (RMM)
performs the same function for mass information.
MSC.SuperModel provides a set of user interface forms that allow for the creation
and inclusion of reduced stiffness and mass models in an analysis. The actual
RSM/RMM data is stored in physical files, named by the user. These RSM/RMM
files use (by default) the MSC.Nastran OUTPUT4 format. However, the OP2 and
DMIG file format is also supported. A new entity is created and stored in the
model database; its definition contains all of the information needed to create and
include RSM/RMM in subsequent models.
A reduced stiffness or mass matrix definition consists of an ordered list of degrees

of freedom that are contained in the stiffness/mass matrix, the filename containing
the matrix, the type of matrix (stiffness or mass), and the degrees of freedom map.
When a new RSM is created, MSC.SuperModel creates a model file, with the
extension .gnl, and a companion file with the extension .gnl.def.
Main Index
➤ ■ Done
➤➤ ➤
4.3.1 RSM Procedure

This section discusses the procedure of first creating an RSM and then its
subsequent usage. Brief references to user interface forms are made, which are
described in the following section. A detailed example follows the user interface
discussion.
The following picture is used to describe RSM creation and usage.
Applied Load
1 17 16 15
Connection
C 14 Points
L 2
A
M RSM 13 12 11 1001
P 3 FEM
E 10 1002 Adjacent
D
Structure
4 5 6 7 8 9 1003
Symmetric or Anti-symmetric
Boundary Condition
The figure above can be used to discuss several key points with respect to RSM
creation and usage.
•Nodes 1-4 are always fixed. These are not required to be included in the
boundary description of the RSM; rather, the user must verify that the proper
elements attached to these nodes are included. Additionally, the clamped
boundary condition must be included in the RSM “analysis” job to permanently
constrain these nodes.
Warning: While permanent constraints are supported, these are not always
recommended as node constraints such as rigid bars and multi-point constraints
can introduce singularities into the stiffness matrix. The most safe modeling
technique is a “free-free” structure where nodes 1-4 are included in the RSM
boundary description and the clamped boundary condition is applied when the
RSM is included in an analysis with the adjacent structure. For more information
on inclusion of boundary conditions on a free-free structure, please see note 4
below.
Main Index
➤ ■ Done
➤➤ ➤
•Nodes 9 - 11 must be included in the RSM boundary description. The user is

asked to define the degrees-of-freedom to be used at each node; typically this is
all 6 DOF’s.
•Nodes 15 - 17 have an applied load condition. These nodes must also be included
in the RSM boundary description. Typically all 6 DOF’s at each node are
included. Multiple load conditions are supported and must be included in the
analysis where the RSM is attached to the adjacent structure.
•Nodes 5 - 9 have an applied, variable boundary condition. Therefore, these nodes
must be included in the RSM description. Typically all 6 DOF’s at each node are
included. Multiple boundary conditions are referenced in the subsequent
analysis where the RSM is attached to the adjacent structure. If a “static”
boundary condition is also present (like the clamped condition shown above), the
boundary condition for each analysis would include both the clamped and
variable condition, as shown above.
•Nodes 12 - 14 are not required to be included in the RSM boundary definition.
To create an RSM requires three steps:
1. Create an RSM definition. All new RSMs are “manually” created and are of
type “Write”.
2. Activate (queue-up) an RSM definition. Only one RSM may be activated.
3. Submit an analysis job. The queued RSM is automatically included in the
analysis job, resulting in the creation of an RSM. An actual analysis is not
submitted as MSC.SuperModel automatically detects the presence of an
activated RSM and take appropriate actions.
Note: If multiple RSMs are to be created from an original database, steps 1 - 3 must
be repeated for each RSM. Step 1 can be performed for each RSM prior to the
remaining steps. Steps 2 and 3 must be performed once for each RSM.
To create an RSM definition from a finite element model, as shown above, use the
following procedures.
1. Create a “manual”, type “Write” RSM.

2. Identify the boundary nodes in any order, along with their associated DOF’s.
3. Specify whether the stiffness or stiffness and mass representation is to be
created.
4. Identify a file name where the RSM data is to be stored.
To activate an RSM definition, or queue an RSM definition for a subsequent

analysis job, use the following procedures.
1. Activate an RSM by selecting it from the list of RSMs. This queues the RSM
definition to be included in the next analysis job, creating an RSM.
2. Only one RSM may be activated (queued) for creating in the analysis step.
Main Index
➤ ■ Done
➤➤ ➤
To create an RSM from an RSM definition, use the following procedures.
1. Go to the MSC.Patran Analysis form. The action can be either Submit or

Analyze. Submit - Single Model is recommended.
2. If a permanent boundary condition is to be included, select the appropriate
Load Case. Only one Load Case may be submitted for “analysis”.
3. If the RSM is to be created from a portion of a larger finite element model,
select the appropriate groups for analysis. For example, make the RSM
Group current and then use the “Current Group” option.
4. Submit the analysis. Three physical files are created and stored under the
single logical file name defined during the RSM definition phase.
To use an RSM in an analysis requires four steps:
1. Load the RSM into the opened adjacent structure database. Use the “From
File” Method. An RSM definition should only be loaded into one “adjacent
structure” database; multiple references results in an error condition.
2. Activate (queue-up) one or more RSM definitions.
3. Apply any required load and boundary condition definitions.
4. Submit the analysis job. This analysis may include multiple defined
configurations, in addition to multiple RSMs.
To load an RSM definition, use the following procedures.
1. Create an RSM Definition in the adjacent structure database by using the

Method “From File”.
2. Select the appropriate RSM entry in either the File Manager hierarchy or
from the proper UNIX directory. If a UNIX selection is used (i.e., the File
Manager is not in use), the RSM definition file (rsm_name.gnl.def) is
selected.
3. Specify any required rotations about the global coordinate system axes.
These rotations are required to be in 90 degree increments.
4. Press the Apply button to load the RSM definition. The following items
should be noted:
•MSC.SuperModel automatically detects the RSM attach points in the
adjacent structure based on the user-defined tolerance. If the adjacent
structure attach points have associated analysis coordinate systems that are
in conflict with the incoming RSM. The RSM analysis coordinate systems
overrides the adjacent structure definitions.
•If nodes are not present in the adjacent structure database where the RSM
connection points are located, they are automatically created.
To activate an RSM definition, use the following procedures.

Main Index
➤ ■ Done
➤➤ ➤
1. Set the RSM menu Action to Activate.

2. Select one or more RSM definitions that have been previously loaded into the
adjacent structure database. Please note the following:
•Not all loaded RSM definitions must be activated.
•Multiple “adjacent structure” databases may exist, each with activated
RSMs.
•Activating one or more RSMs in an adjacent structure database queues
these up for inclusion in the next analysis job that contains the adjacent
structure database.
To apply load and boundary conditions to RSMs, use the following procedures.
1. After the RSMs are either defined or activated in the adjacent structure
database, the previously identified boundary nodes are present. The node
numbers are most likely be different than when first defined because they
are identified by spatial location and not physical node number.
2. Create load and boundary conditions definitions on the boundary nodes, as
is customary in a standard MSC.Patran modeling session. The associated
Load Cases must be identified during analysis job submittal.
To use one or more RSMs in an analysis, use the following procedures.
1. Go to the MSC.Patran Analysis form, either directly or from the

MSC.SuperModel main menu. The Analysis Action must be Submit.
2. Either a “Single” or “Merged Model” may be submitted.
3. Select the appropriate Load Cases.
4. Submit the analysis. Any activated RSMs in the submodels included in the
analysis are used.
Recall from the above discussion, the most common method to first create an RSM
definition is using the Method “Manual” and Type “Write”. If this has been
previously done, and for some reason the RSM definition file (rsm_name.gnl.def)
does not exist, reconstruct the RSM definition. Use the following procedure when
“manually” creating an RSM definition by using the option Type = “Read”.
1. Set the RSM action to Create, Object to RSM Definition and Method to
Manual.
2. Set the Type to Read.
3. Select the boundary nodes in sorted (ascending) order. Recall the selection
order when creating an RSM Definition using Type = “Write” was not
important. The order is important after the RSM exists because MSC.Nastran
sorts the nodes in ascending order prior to creation of the RSM file and RSM
Definition file.
Main Index
➤ ■ Done
➤➤ ➤
4. For each selected node, identify the DOF’s used in the original RSM
definition.
5. Note that the analysis coordinate systems at each node must also correspond
to those from the original definition.
6. Select the original RSM file (rsm_name.gnl).
7. Create the RSM definition.
The user interface to the functionality described above is described in the

following pages.
Main Index
➤ ■ Done
➤➤ ➤
4.3.2 MSC.SuperModel Description of User Interface

The Reduced Stiffness and Mass Modeling capability is accessible from the
MSC.SuperModel main menu, as shown below.
MSC.Patran SuperModel Version 200x

MSC.SuperModel
Version 200x
Main Menu
Loads Tools
Property Data Plots

Configurations
◆ Reduced Stiffness and Mass
Model Unmerge
Bar End Loads
Shear Panel Plots
Main Index
➤ ■ Done
➤➤ ➤
Create Reduced Stiffness and Mass Model Definition
To first create a reduced stiffness and mass model definition, set the Action to
Create, Object to RSM and Method to Manual. The other available Method is From
File; this is used to load a previously created RSM definition into its “adjacent
structure” database; this is discussed later.
Create
Modify
Delete
Show
Activate
User can either create a RSM by directly entering
data or from an existing RSM definition file.
List box displays all RSM definitions that currently

exist in the database.
Enter a new and unique RSM definition name.
Specify whether a RSM is either a Read or Write

type. RSM type must be set to Write when first
creating an RSM from the database that contains
the original FEM entities associated with the RSM
definition.
Accesses the subform used to define the RSM
attachment points and associated DOFs.
Used to define if reduced stiffness and mass or

only stiffness models are to be created.
This is where the RSM file name is designated.
This section is only valid when the RSM type is

Read (see next page).
Choose to define additional planes of symmetry or

use the reduced mass/stiffness matrices as set.
Symmetry options include: XY Symmetry Plane,
XZ Symmetry Plane, YZ Symmetry Plane.
Closes out the form and restores all data entries

that were present when the form was opened or
last refreshed.
Creates the RSM when selected.
Main Index
➤ ■ Done
➤➤ ➤
NOTE: When the RSM Type is set to Write (create a new stiffness/mass matrix), the
order of the list of degrees of freedom and the mapping of the degrees of freedom
is ignored (MSC.Nastran ASET cards are not order dependent). The order of the
RSM/RMM created by MSC.Nastran are in increasing node ID, based on the
matched nodes at the defined spatial locations.
Main Index
➤ ■ Done
➤➤ ➤
If an RSM definition file is lost, but the associated RSM file is present, the definition
file can be reconstructed. The following shows the Create/RSM/Manual form
using the RSM Type Read.
Reduced Stiff. and Mass User can either create a RSM by directly entering
data or from an existing RSM definition file.
List box displays all RSM definitions that currently

exist in the database.
Enter a new and unique RSM definition name.
Specify whether a RSM is either a Read or Write

type. RSM type must be set to Write when first
creating an RSM from the database that contains
the original FEM entities associated with the RSM
definition.
Accesses the subform used to define the RSM

attachment points and associated DOFs.
Used to define if reduced stiffness and mass or

only stiffness models are to be created.
This is where the RSM file name is designated.
Determines how the axes of the RSM is mapped to

the model axes. When the nodes of the RSM are
created in the model and the associated DOF’s of
the RSM are read in, the original axes of the RSM
are mapped to the axes in the model as defined
here.
Choose to define additional planes of symmetry or

use the reduced mass/stiffness matrices as set.
Symmetry options include: XY Symmetry Plane,
XZ Symmetry Plane, YZ Symmetry Plane.
last refreshed.
NOTE: When the RSM Type is set to Read, the degrees of freedom order and
mapping are used to determine the MSC.Nastran DMIG card sequencing. The
selected nodes must exactly match the ascending order of the originally selected
boundary nodes. Additionally, the associated nodal DOF’s and analysis
coordinate system must exactly match the original definitions.
Main Index
➤ ■ Done
➤➤ ➤
The following form is used to define the DOF list associated with a RSM and
appears when the DOF List Definition button on the Create (and Modify) form is
selected.
Spreadsheet containing the current
attachment locations, associated
DOF’s, and the reference
coordinate system that defines
their orientation. Individual cells
may be selected, enabling the user
to modify their content. Individual
rows can be selected and either
deleted or moved using the shift
entry keys.
User can either add, modify, or

delete any entry in the DOF entity
list by activiating the appropriate
toggle.
Shifts the position of any row in
the DOF entity list.
If set, then nodes are

automatically added to the DOF
entity list as they are selected
from the graphics viewport.
User can select the analysis
coordinate system used at each
nodal location in order to define
the orientation of the DOF’s.
Selects the nodal degrees of
freedom.
Displays all of the DOF’s in the
DOF entity list on the model in the
current view port. This display
consists of arrows at the locations
indicating the DOF directions that
are included in the list.
Closes the form and restores the
DOF entity list data that was
present when the form was opened
Selects the spatial [X,Y,Z] or last refreshed.
locations for the RSM boundary
Clears out all entries in the DOF
where the RSM attaches to the
adjacent components. Either entity list.
spatial coordinates or node IDs Saves the data entered in the DOF
may be entered. entity list and uses it to
create/modify the RSM definition.
Main Index
➤ ■ Done
➤➤ ➤
The following form appears when the Select Output (or Input) File button on the
Create/RSM/Manual form is selected. This form is used to select the input or
output matrix filename for the RSM definition. The RSM/RMM OP4 file by
convention should have a .gnl extension. When entering a name for the
RSM/RMM input file the .gnl extension should be added by the user.
Select Output Matrix File

Existing Files
File Hierarchy... File Filter... File by ID... Refresh List
Current Filter: * General Element Uncompressed | Compressed | Online Unlocked
File Descriptions
Selected File
File Description
OK Cancel
Accepts the file in the selection box Restores the previous value of the
as the RSM/RMM file for the current RSM/RMM file to the current RSM
RSM definition. definition.
Main Index
➤ ■ Done
➤➤ ➤
To use one or more RSMs in an analysis, they must be included in an “adjacent

structure” database. The method to include these previously constructed RSMs is
described. Set the Action to Create, Object to RSM Definition and Method to From
File. Any new nodes and coordinate systems needed for the RSM definition is
automatically generated. The Create/From File form appears as follows:
Enter a new RSM name.
Use this subform to select the appropriate RSM

definition file, either from the File Manager
hierarchy or from a UNIX directory.
Defines how the axes of the RSM will be mapped to

the model axes. When the nodes of the RSM are
created in the model and the DOF’s of the RSM are
read into the model, the original axes of he RSM
are mapped to the axes in the model as defined.
Optional definition of additional planes of symmetry

or use the reduced mass/stiffness matrices as is.
Symmetry options include: XY Symmetry Plane, XZ
Symmetry Plane, YZ Symmetry Plane.

last refreshed.
Main Index
➤ ■ Done
➤➤ ➤
The following form appears when the Select RSM Definition File button on the
Create/RSM/From File form is selected, when the File Manager is in use. This
form is used to select the RSM/RMM companion file to be used to generate the
RSM definition.
Select RSM Definition File

Existing Files
File Hierarchy... File Filter... File by ID... Refresh List
Current Filter: * RSM Uncompressed | Compressed | Online Unlocked
File Descriptions
Selected File
File Description
OK Cancel
Accepts the file in the selection box Restores the previous value of the
as the RSM/RMM companion file to RSM/RMM companion file.
be used to generate the RSM
definition.
A similar form is presented when the File Manager is not in use for selection of an
RSM Definition file from a UNIX directory.
Main Index
➤ ■ Done
➤➤ ➤
Modify Reduced Stiffness and Mass Model Definition
The Modify/RSM Definition form only allows for manual modification of a RSM
definition.
Select an existing RSM definition to Modify.
Enter a new RSM name, modify the existing

name, or use the existing name.
Used to specify the type of RSM definition that

will be created.
Access the form to define the DOF list.
Used to specify which matrices are stored in the

output file or read into the model.
Access the form to define the Output File where the
RSM mass/stiffness matrices are stored for a write
RSM or the INput FIle where the matrices are
extracted from for a read RSM.
Defines how the axis of the RSM will be mapped to
the model axis when the RSM type is read. (Not
used in write RSM type definition form). When the
RSM is read into the model, the original X DOFs in
the RSM are mapped to the DOFs selected by the
option menu.
Options for defining additional planes of symmetry

or using the reduced mass/stiffness matrices as is.
Symmetry options include: XY Symmetry Plane, XZ
Modifies an existing RSM definition Symmetry Plane, YZ Symmetry Plane.
when selected.
Closes out the form and restores all data entries that were
present when the form was opened or last refreshed.
Main Index
➤ ■ Done
➤➤ ➤
Delete Reduced Stiffness and Mass Model Definition
The Delete form is used to remove RSM definitions from the database.
List box containing all existing RSM definitions in the

database. User selects those RSM definitions to be
deleted. More than one item may be selected.
Removes the highlighted RSM definitions in the

above list box from the database.
Closes out the form and restores all data entries that
were present when the form was opened or last
refreshed.
Main Index
➤ ■ Done
➤➤ ➤
Show Reduced Stiffness/Mass Model Definition
The Show form is used to display information on an RSM definition.

Names of all existing RSM’s are listed. User

selects which RSM definition for attribute
display.
When an item is selected in the above list box,

the data contained in the selected RSM
definition is displayed here.
The DOF’s associated with the selected RSM
definition is also displayed in the current
graphics viewport.
Use this subform to displays the DOF entity list for

the RSM selected.
Main Index
➤ ■ Done
➤➤ ➤
Activate Reduced Stiffness/Mass Model Definition
RSM Definitions are activated for several reasons:
•To first create an RSM.

•To include previously created RSMs in an analysis.
•To change the DMAP alters used to read or write RSMs.
•To change the format where RSM matrices are stored or read in from.
Main Index
➤ ■ Done
➤➤ ➤
Activating an RSM is equivalent to queueing it up for use in the next analysis job
submittal. Note that when first creating an RSM (Manual, type Write), only one
type Write RSM may be activated (queued) for a subsequent analysis job, while
multiple read type RSMs may be activated. Multiple RSMs may be activated for
actual use in an analysis.
The Activate RSM form appears as follows.
List of all activated Read RSMs in the database.

Multiple Read RSMs may be activated in an analysis.
List of all activated Write RSMs in the database. Only

one Write RSM may be activated. Read and Write
RSMs may never be activated simultaneously.
Change Current Activation enables the user to alter

the RSM activation selection by opening up
MSC.Nastran Activation subform (see next page).
Closes the form and restores all data entries that

were present when the form was opened or last
refreshed.
Applies the changes in the Activated Read/Write

RSM Definitions lists to the database. If this button is
not pressed, then any changes to the Activate RSMs
lists are lost when the form is closed.
Main Index
➤ ■ Done
➤➤ ➤
Select Change Current Activation on the previous

Activate RSM Definition subform to open the
MSC.Nastran Activation subform. Default activation
type is set to Write RSM. Other activation types
include Read RSM and User Defined Alter.
Select only one Write RSM to activate. Selection is

highlighted.
Select to open the Options subform that enables the
user to select which RSM matrices to write as well
as the form in which the matrices are stored.
Closes out the form. If OK is not pressed, then any

changes made to Write RSM’s activation list is lost
when the form is closed.
Press OK to change the Write RSM activation to
reflect the selection made above. The selected
Write RSM displays in the Active Write RSM
Definitions list box in the main Activate RSM
Definitions form.
The activation type changes to Read RSM.
List box shows all READ RSMs that are available.

Each Read RSM selected by the user appears in
the Active list box below. Multiple Read RSMs may
be chosen in any single analysis.
All Read RSM’s selected for activation are listed.
Select to open the Options subform that enables

the user to select which RSM matrices are read as
well as the form that the matrices are stored in
(see next page).
Closes out the form. If the OK switch is not

pressed, then any changes made to the Read
RSMs activation list is lost when the form is
closed.
Press OK to change the Read RSM activation to

reflect the selection made above. The Read RSMs
selected display in the Active Read RSM
Definitions list box in the main Active RSM
Definitions form.
Main Index
➤ ■ Done
➤➤ ➤
Select where to read or write a stiffness matrix or

both a stiffness and mass matrix.
User can specify the format that the mass/stiffness

matrices are read or written to. Options include:
Binary Output2, Binary Output4, or ASCII DMIG
Tables.
Set to print all of the interface loads at the boundary

positions for a Read or Write RSM.
Closes out the form. If OK is not pressed, then any

changes made to the Options are lost and the
settings revert to all data entries that were present
when the form was opened or last refreshed.
Press OK to enable all of the options selected by

the user for the matrices that are either read in or
written out.
Main Index
➤ ■ Done
➤➤ ➤
The activation type changes to User Defined Alter.
Press to open the Select Alter File subform which

enables the user to select which DMAP alter to use for
reading or writing.
Alter file selected is displayed here.
After a DMAP alter is selected, this switch is activated.

This enables viewing the contents of the alter file.
List box shows all READ RSMs that are available. All
Read RSMs selected by the user appear in the Active
List box below. Multiple Read RSMs may be chosen in
any analysis.
All Read RSMs selected by the user for activation are

listed here. The mass/stiffness matrices associated
with the RSMs will be read using the DMAP alter
specified above.
User selects which Write RSM to activate. Selection is

highlighted. Only one Write RSM may be selected. The
mass/stiffness matrices associated with the RSM will
be written using the DMAP alter specified above.
Select this button to open the Options subform that

enables the user to select which RSM matrices are
read or written as well as the format of the matrices
(see previous page).
Closes the form. If OK is not pressed, then any

changes made to the Read or Write RSMs activation
list as well as the DMAP alter selection is lost when the
form is closed.
Press OK to change the Read or Write RSM activation

to reflect the selections made above. The Read RSMs
display in the Active Read RSM Definitions list box and
the Write RSM in the Active Write RSM Definitions list
box in the main Active RSM Definitions form.
Main Index
➤ ■ Done
➤➤ ➤
Filter box enables

the user to specify
alternate directories
for SuperModel
alters.
List box displays

available directories
submodels.
Directory selection
is highlighted.
List box containing

all of the available
alters in the
directory selected.
Closes the form. If

the OK button is not
pressed, then any
changes made to
the alter selection
are lost. Instead the
default alters will be
used for a Read or
Press OK to specify the DMAP alter Write RSM.
that will be used to either read or write Press to list all of the alters contained in
the mass/stiffness matrices. The Alter the directory specified in the filter path.
chosen displays in the MSC.Nastran
Activation subform with User Defined
Alter as the activation type (see
previous page).
Main Index
➤ ■ Done
➤➤ ➤
Introduction
MSC.Nastran has the ability to reduce a model’s stiffness and mass information to
a specified set of DOF’s. These DOF’s are specified in the MSC.Nastran ASET
cards. The reduced stiffness matrix assembled at these DOF’s (e.g., a fuselage
model reduced to the DOF’s where the wing is attached) can be written out to a
file. It is later read in and added to the stiffness matrix for an associated structure
(e.g., the wing model) using DMIG cards and appropriate DMAP alters. This
technique stores the minimum information needed to account for the boundary
conditions at the attachment. The analysis of the following simplified portion of a
canopy and fuselage illustrates the above discussion.
The goal with this model is to analyze the canopy separately from the fuselage.
Loads and boundary conditions include both symmetric and anti-symmetric
cases, axial compression (symmetric) and up- or down- bending (anti-symmetric
about XY plane).
LOADED Combined Fuselage/ Canopy Model
EDGE SYMMETRY
Canopy
Z SYMMETRY
Fuselage Canopy
X Attachment
Points
SYMMETRY or ANTISYMMETRY
Main Index
➤ ■ Done
➤➤ ➤
Creating the RSM/RMM File
The fuselage model is created by itself in a database (See Figure 4-4). The boundary
conditions are applied only where they will not change. At the corner nodes (44,
48, 33, 11), where a constant boundary condition meets a load or boundary
condition that will change, no constraints should be applied. These constraints will
be applied in the canopy model. None of the loads will be applied to this model so
they can be changed when analyzing the canopy.
Fuselage Model
Boundary conditions on these
DOF’s provide edges are applied directly to the
load points for fuselage model, because they
canopy will be the same in all analysis
submodel. 48 runs of the canopy.
44
DOF’s provide
43 boundary stiffness for
39 canopy submodel.
Z 38
34
31 32 33
29 30
Y 27 28
23
X 12
11
9 10
6 7 8
1 3 4 5
2 B.C.’s not defined on fuselage model,
because use of DOF’s provides ability
to run canopy model with multiple
boundary conditions on fuselage.
Figure 4-4 Fuselage Model
After the model has been created, the RSM must be created. This is done from the
Create/RSM form.
To create an RSM:
1. Enter the RSM name fuselage in the RSM name box.

2. Select the Write toggle for the RSM Type.
3. Press the DOF List Definition button.
•Select all of the DOF toggles.
•Select the DOF coordinate system (Coord 0)
•Select the nodes 1:11, 12, 23, 27, 34,38,39,43,44,48 to be added to the
RSM definition. For the Write RSM Type the order that the nodes
Main Index
appear in the list is ignored.
➤ ■ Done
➤➤ ➤
•Press the Display Current List button and check that the correct
locations have been selected. The model should look like Figure 4-5.
•Press the OK button to accept the DOF list.
Fuselage Model With DOF Markers Shown

Boundary conditions on these
DOF’s provide load edges are applied directly to
points for canopy the fuselage model, because
submodel. they will be the same in all
runs of the canopy.
DOF’s provide
boundary stiffness for
canopy submodel.
Z
B.C.’s not defined on fuselage model,

because use of DOF’s provides
= DOF Markers ability to run canopy model with
(Marker’s appearance may differ in MSC.Patran) multiple boundary conditions on
Figure 4-5 Fuselage Model with DOF Markers
4. Select the Stiffness Only toggle. If a dynamic analysis is to be performed, a

mass representation is also required.
5. Press the Select Output File button.
•Input the name fuselage.gnl for the file to contain the RSM/RMM
data. (In general this filename should have an .gnl extension.)
•Press the OK button to accept this filename.
6. Press the Apply button. This defines the RSM.
After the RSM has been created, it must be selected from the Activate RSM form
for use in an analysis run.
Main Index
➤ ■ Done
➤➤ ➤
To select the RSM definition:
1. Press the Change Current Activation button to open the MSC.Nastran

Activation subform.
2. Set the Activation Type to Write RSM.
3. Select the RSM fuselage from the list box.
4. Select the Options button.
5. Select the matrice to write as well as the format of the matrices.
6. Press OK to make selections and close the Options Subform.
7. Press OK to make selections for Write RSM to Create and close the form.
8. Confirm that the RSM fuselage appears in the Active Write RSM Definitons
list box located on the Active RSM Definition main form.
9. Press Apply to activate.
10.Press OK to make selection and close out form.
11.Confirm that the RSM fuselage appears in the Active Write RSM Definitions
list box located on the Activate RSM Definition main form.
12.Press Apply to enable activation.
Now that the RSM has been selected, an MSC.Nastran job must be run to generate
the RSM/RMM file. This is done using the same procedure to run any job. The job
must consist of only one subcase that contains any boundary conditions and loads
that are to be applied to the model. The solution sequence must be SOL 101, if the
RSM is to produce only a stiffness matrix, or SOL 103, if the RSM definition is to
produce both stiffness and mass matrices.
Main Index
➤ ■ Done
➤➤ ➤
Using the RSM/RMM File
Manual Option
The canopy model is created by itself in a database. The boundary conditions are
applied to the model as needed. At node 29 the top symmetry conditions are
applied and at node 44 right side symmetry conditions are applied because these
were not applied to the fuselage model at these nodes (see Figure 4-6).
Canopy Model
Boundary conditions
Loads are applied to are applied here for
these points. the canopy model.
22
29
15
30
Z
8
31
Y 7
4 5 6
32 1 2 3
X 43 44
33 41 42
39 40
36 37 38
34 35
Boundary conditions
are applied here for
= Isolated Nodes the fuselage.
Figure 4-6 Canopy Model
After the model has been created, the RSM must be created. First, the order that the
nodes appears in the DOF’s list must be determined. When a RSM/RMM file is
created the order of the nodes in the file is determined by the node numbering. The
order is from the lowest node number to the highest node number. When a
RSM/RMM file is read in, this order must be maintained. To be able to read in the
RSM/RMM file correctly, the model that generated the RSM/RMM file must be
compared to the model that reads in the model. The order of the nodes in the new
DOF’s list is determined by matching the order of the nodes in the original model
to the corresponding nodes in the new model.
Main Index
➤ ■ Done
➤➤ ➤
In this example the following correspondences between nodes are found:
Fuselage Model Canopy Model Fuselage Model Canopy Model
node 1 node 34 node 27 node 1
The list gives the order that the nodes must be in for the canopy model to correctly
read in the RSM/RMM file. This order must be used when defining the RSM.
Now an RSM must be created. This is done from the Create RSM form.
To create a RSM:
1. Enter the name fuselage.

2. Select the Read toggle for the RSM Type.
3. Press the DOF List Definition button. (This brings up the Define DOF List
Form.)
•Select the all the DOF toggles.
•Select the DOF coordinate system (Coord 0)
•Select the nodes 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 44, 33, 32, 1, 2, 3, 4,
5, 6, 7, 31, 8, 30, 15, 29, 22 to be added to the RSM Definition. For the
Read RSM Type the order that the nodes appear in the list must be the
same as the order of the corresponding nodes in the RSM/RMM file.
Main Index
➤ ■ Done
➤➤ ➤
•Press the Display Current List button and check that the correct nodes
have been selected. The model should look like the following figure.
Canopy Model with DOF Markers Shown

Boundary conditions
Loads are applied to
are applied here for
these points. the canopy model.
Boundary conditions are

applied here for the
fuselage.
= DOF Markers
(Marker’s appearance may differ in MSC.Patran)
•Press the OK button to accept the DOF list.

4. Select the Stiffness Only toggle.
5. Press the Select Input File button.
•Select the RSM/RMM filename fuselage.gnl
6. Set the DOF mapping to the appropriate settings. When a RSM/RMM file is
generated, the order of the DOF’s is UX, UY, UZ, RX, RY, RZ. This option lets
you change this order. If the global coordinate system is oriented the same
way relative to the model in both the database that generated the
RSM/RMM file and the database that reads in the RSM/RMM file, then the
DOF mapping should be X to X, Y to Y, and Z to Z. If the orientation is not
the same, then the mapping needs to be different. For this example the
mapping is X to X, Y to Y, and Z to Z.
7. Press the Apply button. This defines the RSM definition.
Main Index
➤ ■ Done
➤➤ ➤
From File Option
For this option, create the canopy model and all the nodes to be loaded or have
Boundary conditions applied to them. Do not create any of the isolated nodes that
are part of the RSM and do not have LBC’s applied to them. These nodes are
automatically created when the job is submitted to MSC.Nastran. After the canopy
model is created, the RSM must be generated. This is done for the Create/From
File form.
To create the RSM definition:
1. Enter the name fuselage.

2. Press the Select General Definition File button.
•Select the RSM/RMM companion file generated previously,
fuselage.gnl.def.
3. Set the DOF Axis mapping to the appropriate settings. When the RSM/RMM
file is generated, the order of the DOF’s is UX, UY, UZ, RX, RY, RZ and the
RSM/RMM companion file has the node locations of the DOF’s in the
coordinates of the original model. This option lets you change the orientation
of the RSMs global axis relative to the model’s global axis that is reading it
in. If the global coordinate system is oriented the same way relative to the
model in both the database that generated the RSM/RMM file and the
database that reads in the RSM/RMM file, then the DOF Axis mapping
should be X to +X, Y to +Y, and Z to+ Z. If the orientation is not the same,
then the mapping needs to be different. For this example the mapping is X to
+X, Y to +Y, and Z to +Z.
4. Press the Apply button. This defines the RSM.
After the RSM is created, the nodes that were part of the RSM and not part of the
canopy exists. The boundary conditions shown in Figure 4-6 should be applied to
the model.
Activate the RSM
After the RSM has been created, it must be selected for use in an analysis run. This
is done from the Activate RSM form.
To activate the RSM:
1. Press Change Current Activation to open the MSC.Nastran Activation

subform.
2. Set Activation Type to Read RSM.
3. Select the RSM fuselage from the list box.
Main Index
4. Select the Options button.
➤ ■ Done
➤➤ ➤
5. Select the matrice to write as well as the format of the matrices. Note that
these selections must match the types and format of the matrices that are
contained in the .gnl file when the general element was created.
6. Press OK to make selections and close out the Options subform.
7. Press OK to make selections for the Read RSM’s that are to be activated and
to close the form.
8. Confirm that the RSM fuselage displays in the Active Read RSM Definiton
list box located on the Active RSM Definition main form.
9. Press Apply to enable RSM activation.
Now that the RSM has been activated, the job includes the RSM/RMM file when
it is run. This job may be run using the same procedure used to run any job.
Currently only structured solution sequences (SOL >100) are supported, but
results may not be accurate for any solution sequence except linear statics (SOL
101) and normal modes (SOL 103), because RSM/RMM files contain only a linear
approximation of the structure they represent.
Main Index
➤ ■ Done
➤➤ ➤
4.3.4 Warnings and Pitfalls

This section covers modeling situations that must be avoided to prevent problems
from occurring when using RSM/RMM files.
Creating Partial Model Analysis Runs
If an analysis is run with the Current Group option, then all of the nodes that are
contained in the DOF lists of the activated RSMs must be part of the current group.
Use of Dynamic Reduction with RSM/RMM Files.
When a Normal Modes solution is run with the RSM/RMM file reference,
Dynamic Reduction must be disabled. The Perform Dynamic Reduction toggle on
the Dynamic Reduction subform must be set to the off position.
Selecting Output Matrices
For dynamic analyses, both mass and stiffness matrices must be requested. Failure
to do so will result in a Patran fatal error at the the time of model translation and
generation of the Nastran bulk data file.
Note selection of which output matrices to read to write must be made on both the
SuperModel RSM definition main form as well as on the RSM Activation Options
subform. Selecting both mass and stiffness on the main form and stiffness only on
the Options subform will result in only in stiffness matrices being written or read.
Main Index
➤ ■ Done
➤➤ ➤
4.4 Assembly Definition and Analysis

The Assembly Definition and Analysis functionality allows engineers to model
and analyze a large structural model using smaller components. This allows a
team of engineers to work separately on individual components (submodels) by
providing the means to merge those components together into a larger model,
analyze it, and break it apart for postprocessing of results.
Main Index
➤ ■ Done
➤➤ ➤
4.4.1 Assembly Definition

The Assembly Definition provides the means by which SuperModels are analyzed.
Users are provided a convenient means of combining submodels from separate
databases and analyzing them as an assembly. Templates of previous jobs can
serve as starting points for additional analyses; these are referred to as Job
Definition files. The assembly of submodels is performed during job submittal. As
part of the analysis process, the module performs group translations and rotations
defined by Configurations. When the analysis job is finished the results are read into
the SuperModel database.
The Assembly Definition and Analysis form is accessed from the

MSC.SuperModel main menu. Selecting this option automatically invokes a
modified version of the MSC.Patran Analysis form. (Another way to access this
form is to select the MSC.Patran Analysis application and set the Action to
Submit). The Action on the Analysis form must be set to Submit.
Procedure
You access the Assembly Definition and Analysis functionality from either the
MSC.SuperModel main menu or by selecting the MSC.Patran Analysis application
and setting the Action to Submit. In either method, the Action must be set to
Submit on the Analysis form to create a SuperModel analysis job.
1. For new jobs, skip to step 2. However, if you are submitting a job or would
like to use an existing job definition as a starting place, read in the job
definition from which you wish to start using the Read Job Definition...
button.
2. Skip to step 4 if you are submitting a single model. Otherwise, select
submodels to be merged, or verify the submodel merge list defined by the
job definition. If you are merging models you must start with an empty
database.
3. Modify parameters for the merge process. You may choose to skip this step
and accept the default parameters.
4. Review the load cases coming in from the submodels to ensure that
everything is correct (optional).
5. Define your job as you normally would.
6. Use the Run button at the bottom of the Analysis form with the Submit action
to start off the SuperModel submittal process. Submittal of the job via any
other method (e.g., the Analyze action on the Analysis form or the Submit
action on the Analysis Manager form) WILL NOT result in a SuperModel
run. A dialog box asks you whether the analysis or analyses should be run
interactively or in batch mode.
Main Index
➤ ■ Done
➤➤ ➤
NOTE: Full job submittal functionality is available only if you choose the Full Run
method. Other methods may be used, but you have to manually read answers into
the database and register it as a SuperModel.
Main Index
➤ ■ Done
➤➤ ➤
4.4.2 Requirements
When merging submodels:
1. You must start from an empty database whether or not you use an existing
job definition as a starting point.
2. The submodels must be individually complete — i.e. contain properties,
loads/boundary conditions, configuration definitions, etc. Loads/boundary
condition sets with duplicate names are combined during the merge.
3. Submodels must be meshed in a way that boundary nodes between
submodels coincide in space. The models will become connected by
performing a nodal equivalence, using a tolerance value and method
specified on the Submodel Merge Parameters subform.
For both merge lists and single models:
1. The Job Definition functionality is currently limited to the MSC.Nastran

preference.
2. When submitting jobs, you must use the Run button at the bottom of the
Analysis form with the Submit action. Use of the Analyze action on the
Analysis form or the Submit action from the Analysis Manager form does
not result in a SuperModel submittal.
3. If you submit a job in batch mode, enough MSC.Patran licenses must be
available to start another session.
Main Index
➤ ■ Done
➤➤ ➤
4.4.3 Technical Operation
Interactive and Batch Submittal
You may submit SuperModel analyses either interactively or in batch mode. In

interactive submittal, all operations (merging and configuration of models,
analysis job submittal, etc.) take place in the current MSC.Patran session. The
current database is only closed if configurations are used. For batch jobs, the
current database is closed and a batch session of MSC.Patran is spawned to
perform the job submittal. Currently, this requires another MSC.Patran license. In
the batch session, the job submittal takes place in the same manner as if the user
had submitted the job interactively.
Configuration
When configurations are associated with a job, the current database is closed and
a working copy is made, or if using File Manager the database is opened for
reading only. The transformations are made in the copy, that is used for the
submittal and subsequently deleted. If different transformations are specified for
different load cases, then one job is submitted for each unique combination of
transformations.
Main Index
➤ ■ Done
➤➤ ➤

The Assembly Definition and Analysis menu is available from the
MSC.SuperModel main menu.

MSC.SuperModel
Version 200x
Main Menu
Loads Tools
Property Data Plots

Configurations
◆ Assembly and Analysis
Model Unmerge
Bar End Loads
Shear Panel Plots
This selection automatically invokes a modified MSC.Patran Analysis application

form. The Action should be set to Submit on the Analysis application.
Main Index
➤ ■ Done
➤➤ ➤
A number of forms are available to define a SuperModel job. You can access all of
these through the Submit action on the Analysis form.
Submitting a Merged Model
The Submit action adds buttons not available from the Analyze action on the
Analysis form, allowing you to read old job definitions and define submodels to
merge. If you are submitting an assembly model (i.e., multiple component
submodels), you must start with an empty database and select submodel
databases so that, when combined, they form a completely defined model,
including properties, load cases, and configurations. Start with an empty database.
Analysis There are more options in addition to Submit.
Action: Submit
These options have been inherited from Patran
and are available to use. Most of the time Submit
Object: Merged Model
is the only option you will need.
Method: Full Run
Can be Merged Model or Single Model. If Merged
Code: MSC.Nastran Model, then you must start with an empty database.
Type: Structural
Study: Same methods found on standard Analysis form
(Full Run, Check Run, Analysis Deck, and Model
Available Jobs
Only).
Job Name
femwts_proto_v5
Job Description
MSC.Nastran job created on
24-Jan-96 at 10:19:36
Use to read in a previous job definition.

Read Job Definition File ...
Select Submodels ...
Use to select submodels to merge. Other buttons
are disabled until submodels have been selected.
Show Load Cases ...
Translation Parameters...
To review which load cases came
Solution Type... from which component submodels.
Direct Text Input...
Subcases... You are asked whether to run the job interactively or
Subcase Select... in batch mode. Batch submit mode spawns a
separate process to merge the models and submit
Analysis Manager...
the analysis job. Interactive submit mode merges
the models in the current session so you can verify
Run
each configuration.
Main Index
➤ ■ Done
➤➤ ➤
Submitting a Single Model
This is the form for submitting a SuperModel run from a single model. It is
identical to the standard Analyze action except that the user is given the option to
read in a job definition.
Analysis
Action: Submit
Object: Single Model If you don’t need to merge submodels,
you can use this form to submit a job. It
Method: Full Run
differs from the normal MSC.Patran job
Code: MSC.Nastran submittal in that:
Type: Structural • A job definition file is written

• Configurations are performed
Study:
• Results are automatically merged
Available Jobs
Job Name
femwts_proto_v5
Job Description
MSC.Nastran job created
on 24-Jan-96 at 10:19:36
Read Job Definition File ... Use this to read and duplicate a job
definition from an earlier run.
Translation Parameters...
Solution Type...
Direct Text Input...
Subcases...
Subcase Select...
Analysis Manager...
Run
Main Index
➤ ■ Done
➤➤ ➤
Reading a Job Definition File (Outside File Manager)
You can use the following form to read an existing job definition if the File
Manager is not licensed.
Read Job Definition File
Select Job Definition File
Filter
/okinawa/user/smith/*.jdl
Directories Files
/smith/. template.jdl
/smith/.. wing1.jdl
/smith/.fminit2.0 wing2.jdl
/smith/Exercises
/smith/Mail
/smith/Part_2_basic_functions
/smith/Part_4_FEM
Job Definition File Name

wing2.jdl
OK Filter Cancel
You must start from an empty database if you are reading in a job definition that
includes definition of submodels. The job definition file creates jobs in the current
database corresponding to those used for the run from which the file was written.
If load cases are needed for the job, they are created in name only for the database.
Main Index
➤ ■ Done
➤➤ ➤
Reading a Job Definition File (File Manager)
If the File Manager is licensed, you can use this interface to choose a job definition
file to read.
Read Job Definition File

Existing Files
File Hierarchy... File Filter... File By ID... Refresh List
Current Filter: * Job Definition Uncompressed | Online All
File Descriptions
Merge Airframe - Center Fuselage & Wing: Final Sizing
Selected File
File Description
OK Cancel
You must start from an empty database if you are reading in a job definition that
includes definition of submodels. The job definition file creates jobs in the current
database corresponding to those used for the run from which the file was written.
If load cases are needed for the job, they are created in name only for the database.
Main Index
➤ ■ Done
➤➤ ➤
Selecting Submodels to Merge (Outside File Manager)
You can use the following form to choose a list of submodels to merge for a run.
This is accessed by selecting the Select Submodels button on the Submit: Merged
Models analysis form.
Submodel Selection
Existing Submodels
Filter
/user/smith/*.db
Directories Submodels
/user/smith/. flaps.db
/user/smith/.. fuselage.db
/user/smith/.fminit2.0 lower_skin.
/user/smith/Exercises
/user/smith/Mail rib_1.db
/user/smith/Part_2_basic_functions rib_2.db
/user/smith/Part_4_FEM rib_3.db
Submodel Selected
Add to List Filter
Selected Submodels
/user/smith/fuselage.db
/user/smith/lower_skin.db
/user/smith/spar_1.db
/user/smith/spar_2.db
/user/smith/rib_1.db
/user/smith/flaps.db
Remove Move up Move down Clear
Merge Parameters... OK Cancel
Choose the submodels to merge by selecting them individually and selecting Add
to List in the middle of the form or by double clicking on the name. It is then moved
into the box of selected models. After a model is in the Selected Submodels list, its
status can be modified by selecting the name and selecting Remove to delete it
from. A Submodel’s position in the list can be altered using Move Up or Move
Down; this alters its entity numbering and naming in the assembled Supermodel.
Clear deletes the entire list of selections.
Main Index
➤ ■ Done
➤➤ ➤
Models are merged in the listed order. To change the parameters used to merge the
databases, select Merge Parameters. Default parameter values are provided and
any changes are optional.
When you select OK at the bottom of the form after selecting the models, each
database are opened and its LBC set names are created in the current database. Full
database merging does not occur until the job is submitted.
Selecting Submodels to Merge (File Manager)
You can use the following form to choose a list of submodels to merge for a run.
This is accessed by selecting the Select Submodels button on the Submit: Merged
Models analysis form.
Submodel Selection
Existing Files

Current Filter: * Submodel Uncompressed | Compressed | Online Working
File Descriptions
Selected Submodels
Remove Move Up Move Down Clear
Merge Parameters... OK Cancel
Main Index
➤ ■ Done
➤➤ ➤
Choose the submodels to merge by selecting them from the list. It can then be
moved into the list of selected models. After a model is in the Selected Submodels
list, its status can be modified by selecting the name and selecting Remove to delete
it from the list or by selecting Move Up or Move Down to change its position. Clear
deletes the entire list of selections.
Models are merged in the listed order. To change the parameters used to merge the
databases, select Merge Parameters. Default parameters’ values are provided; any
changes are optional.
When you select OK at the bottom of the form after selecting the models, each
database are opened and its LBC set names are created in the current database. Full
database merging does not occur until the job is submitted.
Modifying Merge Parameters

This is the form to define parameters for the merge operation. It is not required to
enter this form as appropriate defaults are used.
Submodel Merge Parameters
Select a submodel or a column label to change merge parameters.
Entities Tolerance Method ID Offset Prefix Sig Dig’s
upper_skin.db Both 0.005 Cube 1000 SM_001_ 3
lower_skin.db Both 0.005 Cube 2000 SM_002_ 3
spar_1.db Both 0.005 Cube 3000 SM_003_ 3
spar_2.db Both 0.005 Cube 4000 SM_004_ 3
rib_1.db Both 0.005 Cube 5000 SM_005_ 4
flaps.db Both 0.01 Sphere 8000 SM_008_ 3
Modify merge parameters for submodel:

File Path: /users/m123456/p3cgsa
File Name: flaps.db
Entities to Merge: Merge Tolerance Merge Tolerance Method:
◆FEM & Geom ◆ FEM Only ◆ Default ◆ Input 0.01 ◆ Cube ◆ Sphere
◆
Numbered Entity Offset: Named Entity Prefix:
◆
◆ Default (SM # * Offset)
Enter Offset:
◆ Default (SM_#)
◆ User
1000 ◆ Input
◆ Auto (Last ID + 1)
Property Merge Real Number Equality Criteria

3
0.123E+nn
Significant Digits
Reset OK Cancel
Main Index
➤ ■ Done
➤➤ ➤
Select a model in the left column, and its merge data is copied to the lower area to
alter. A single parameter can be changed for all models by selecting it at the top of
a column. Entities to be merged can include FEM or FEM and geometry. Other
merge parameters are described more fully in the help pages for Model Merge -
Interactive (p. 4-160).
The form may be reset to its default settings by selecting the Reset Default button.
Displaying Load Cases From Submodels
After the submodels are chosen, load case information from each of the models is
assembled. After this process is complete, the information can be viewed by
choosing the Show Load Cases button on the Analysis form. This form is for
informational purposes only. The following form shows how each of the
submodels are listed in the left column. Each load case to be created is listed across
the top row as a number with the associated name displayed in the Available Load
Cases box. If the Load Case is defined in a submodel, the corresponding
spreadsheet entry indicates Yes.
01 - Abort_landing
02 - Landing
03 - Pull-up
04 - Roll
Load Cases contained in the Submodels Selected

1 2 3 4
uppr_skin.db Yes Yes
lowr_skin.db Yes Yes Yes
spar_1.db Yes Yes
spar_2.db Yes
rib_1.db Yes Yes Yes
rib_2.db Yes Yes
rib_3.db Yes Yes
flaps.db Yes Yes
load case: Landing

File Path: /users/m123456/p3cgsa
Close
Main Index
➤ ■ Done
➤➤ ➤
4.4.5 Example
You are to submit an analysis of an airplane model (Figure 4-7) assembled from a
series of submodels, including a fuselage submodel (Figure 4-8), a wing submodel
(Figure 4-9), and a tail submodel (Figure 4-10). To do this, you must merge these
submodels together, define subcases for the analysis, and submit the run. Each
submodel has load cases titled landing_load, 6g_pull_up, and 2g_push_over,
which are composed of load sets applied to individual components in that
submodel, such as air pressure loads on external surfaces, fuel loads on fuel cells,
ground loads on landing gear, etc.
Figure 4-7 Merged Aircraft Model “airplane.db”
Main Index
➤ ■ Done
➤➤ ➤
Figure 4-8 Fuselage Submodel “fuselage.db”
Figure 4-9 Wing Submodel “wing.db”
Main Index
➤ ■ Done
➤➤ ➤
Figure 4-10 Tail Submodel "tail.db"
Submitting a New Merged Model

1. Begin the analysis by opening a new database.
2. Access the Assembly Definition and Analysis functionality. Verify the
Action is Submit and Object is Merged Model on the Analysis form. Your
method should be Full Run if you want to have results read into the current
database.
3. Select the Select Submodels button to bring up that form. Select each model
to be merged in the order they are to be merged (fuselage.db, wing.db,
tail.db), selecting OK (from the middle of the form) after each selection to
move it to the list of models to be merged.
4. (This step is optional; if it is skipped, basic default settings are used.) To
change any parameters used in the merge process, select the Merge
Parameters button. On the displayed subform, you can either accept the
default settings or change parameters as desired. For example, you can
change the merge tolerance for all submodels (say to a user input value of
0.01) by selecting the title at the top of the Tolerance value column and
making an appropriate change in the data entry area. Alternatively, data for
a single model can be updated by selecting the model in the row title on the
left and making changes in the data entry area. Detailed descriptions of all
the merge settings are available in the Model Merge - Interactive (p. 4-160)
portion of the help. To go back to the default settings at any time, you may
select the Reset Defaults button on the bottom of the form. The OK button
will take you back to the last form.
Main Index
➤ ■ Done
➤➤ ➤
5. After the merge parameters for the submodels are correct, selecting OK at
the bottom of the Submodel Selection form causes each of the submodels to
be queried for load case information. When this operation is complete, all
load cases defined in the submodels are created (in name only) in the current
database. In the case of this airplane model, load cases called landing_load,
6g_pull_up, and 2g_push_over would be present in the current empty
database, each with no associated load sets.
6. You can verify that each submodel has subcases defined by selecting the
Show Load Cases button on the Analysis form. This brings up a spreadsheet
showing the names of all the load cases and in which submodels they are
defined. From this point, you can go back and revise the submodel list if
necessary.
7. Define the analysis as for a standard MSC.Patran job, defining the translation
parameters, solution type, subcase selections, etc. The only change in this
procedure is that the job MAY NOT be submitted using the Submit action on
the Analysis Manager form. The configuration for the Analysis Manager
(e.g. memory requested for the job) can be changed, but you must save the
settings and exit the form.
8. Submit the job by selecting the Run button at the bottom of the form. Use of
the Submit action on the Analysis Manager form will not result in a
SuperModel submittal. A dialog box asks whether the submittal is to be
interactive or batch. If a batch job is submitted, the current database is closed
and a separate MSC.Patran session is spawned to submit the job. If
configurations are used (see next section), then the database is closed
regardless of which choice is made.
9. The job can be monitored using the Analysis Manager. When it is complete,
answers have been read into the database. If the File Manager is registered,
it also has been registered as a SuperModel.
Submitting a New Single Model

1. Retrieve a complete model to submit.
2. Access the Assembly Definition and Analysis function. Verify the Action is
Submit and the Object is Single Model on the Analysis form. Your method
should be Full Run if you want to have results read into the current database.
3. Proceed as for a merged model, skipping steps 3-6.
Main Index
➤ ■ Done
➤➤ ➤
Resubmitting a Previous Job

1. Start from an appropriate database, empty for a merged model or a fully
defined model for a single model submittal.
2. Open the Analysis form and select action Submit and select an appropriate
object (Merged Model or Single Model). Your method should be Full Run if
you want to have results read into the current database.
3. Select the button labeled Read Job Definition File and select a job definition
file to read. Selecting OK causes that file to be read and the job defined. On
the Analysis form, select the newly defined job to populate the subforms
with those job parameters.
4. If necessary, change job parameters as described in the procedure for
submitting a new model. Submit the job as before.
Main Index
➤ ■ Done
➤➤ ➤
4.5 Model Unmerge

The Model Unmerge functionality provides the tools needed to extract component
models and their associated results from a large structural model. Along with Job
Definition and Submodeling, this allows a team of engineers to work separately on
individual submodels by providing the means to merge those submodels together
into a larger model, analyze it, and break it apart for postprocessing of results.
4.5.1 Unmerge
During a Job Definition in File Manager, all submodels used in the job definition
become groups in the resulting SuperModel. Model Unmerge gives the user a
convenient means of extracting submodels or groups along with result cases from
a SuperModel and postprocess the selected results for only the smaller portion of
the model.
The Model Unmerge functionality is available from the MSC.SuperModel main

menu. From the larger model, the user selects one or more desired groups and
result cases.
You must start with an empty database when extracting components from a larger
model. The selected component groups and result cases are stored in the new
database. The model database is then closed and the starting database containing
the extracted groups and result cases remain open.
Procedure
The Model Unmerge functionality is available from the MSC.SuperModel main

menu.
1. Start with an empty database when extracting components and results from
a larger model.
2. Use the Select Source Database button to bring up the file selection form.
3. Select the model database from which the Unmerge is to be performed.
4. Select the groups or submodels to be extracted from the model.
5. Select the results to be extracted from the model.
6. Use the Apply button at the bottom of the form to initiate the Unmerge
process. Any MSC.SuperModel and MSC.Patran results postprocessing tools
can now be applied on the component model extracted from the larger
structure.
Main Index
➤ ■ Done
➤➤ ➤
4.5.2 Requirements and Limitations

The following are the current known requirements and limitations of Model
Unmerge:
1. You must start with an empty database when extracting submodels or

groups and results from a model.
2. Results are extracted for only those entities which are members of the
selected groups.
3. Freebody calculations performed at adjacent structure boundaries of the
selected groups are incorrect.
Main Index
➤ ■ Done
➤➤ ➤

The Model Unmerge functionality is accessible from the MSC.SuperModel main
menu.

MSC.SuperModel
Version 200x
Main Menu
Loads Tools
Property Data Plots

Configurations
◆ Model Unmerge
Bar End Loads
Shear Panel Plots
The form has a button to select the model database from which the extraction is to
be made and listboxes for the selection of the desired groups and result cases to be
extracted.
Main Index
➤ ■ Done
➤➤ ➤
Selecting a Source Model Database
The Model Unmerge main form contains a button that allows the user access to a
file selection interface. You must start with an empty database and select the model
database from which the data is to be extracted. The user can extract data by either
group or by submodel. The user may also extract both model and results data or
just model data only as shown on the next page.
Model Unmerge
Model and results or model only data may be

extracted.
Data extraction can be by either group or
submodel.
By selecting this button, the user can access the

file selection interface and choose the
MSC.SuperModel database used for data
extraction.
A list of available groups or submodels may be

filtered.
The user selects those groups or submodels

from the display list that will be unmerged.
Multiple selections are permitted and these are
all highlighted.
If the model and results option is enabled, then all

of the available Results Cases contained in the
SuperModel used for data extraction will be
displayed. Multiple Results Cases may be
selected and these will be highlighted.
The Cancel button removes the display of this

form from the screen.
The Apply button initiates the process of

extracting and unmerging the selected data.
Main Index
➤ ■ Done
➤➤ ➤
If only model data is being extracted, then the following form will be displayed.
Model Unmerge
Data extraction can be by either group or

submodel.
By selecting this button, the user can access the

file selection interface and choose the
MSC.SuperModel database used for data
extraction.
A list of available groups or submodels may be

filtered.
The user selects those groups or submodels from

the display list that will be unmerged. Multiple
selections are permitted and these are all
highlighted.
The Cancel button removes the display of this

form from the screen.
The Apply button initiates the process of

extracting and unmerging the selected data.
Main Index
➤ ■ Done
➤➤ ➤
Selecting a SuperModel from File Manager
You use the Select SuperModel form to choose a SuperModel file from which to
extract the desired data.
Select Supermodel
Existing Files
Current Filter: * Supermodel Uncompressed | Compressed | Online Unlocked
File Descriptions
Airframe - Center Fuselage & Wing: Final Sizing
Selected File
File Description
OK Cancel
Main Index
➤ ■ Done
➤➤ ➤
Selecting a Model Database from Outside File Manager
You use the Select Model form to select a model database if the File Manager is not
licensed.
Select Model
Select Model File
Filter
/okinawa/user/smith/*.db
Directories Files
/smith/. template.db
/smith/.. wing1.db
/smith/.fminit2.0 wing2.db
/smith/Exercises
/smith/Mail
/smith/Part_2_basic_functions
/smith/Part_4_FEM
File Name
wing2.db
OK Filter Cancel
Main Index
➤ ■ Done
➤➤ ➤
4.5.4 Example
An analysis of an airplane wing model Figure 4-11 has been performed. This
analysis contains different structural groups and different results cases. You wish
to generate a display of one results case applied to only one portion of the model
(the flap) Figure 4-12. To do this, you must extract the flap and the results for the
desired case.
Figure 4-11 Aircraft Wing Model
Main Index
➤ ■ Done
➤➤ ➤
Figure 4-12 Flap Submodel
Figure 4-13 Flap Submodel with Results Displayed
Main Index
➤ ■ Done
➤➤ ➤
Unmerging a Portion of a Model

1. Begin the analysis by opening a new database.
2. Open the MSC.SuperModel main menu and select Model Unmerge.
Currently, the only Object choice is Submodel.
3. Select the Select Source Database... button to bring up the file selection form.
The form displayed depends on whether the File Manager is licensed
Selecting a SuperModel from File Manager (p. 4-257) or not Selecting a Model
Database from Outside File Manager (p. 4-258) Select the database from which
the structural groups and results cases are to be extracted. Select OK.
4. Select the desired structural groups and results cases. Select Apply. The
selected groups and results cases are placed into the empty starting database.
5. You may now generate the desired results display using only the selected
structural groups and results cases Figure 4-13.
Main Index
➤ ■ Done
➤➤ ➤
Main Index
➤ ■ Done
➤➤ ➤
Results Visualization ❚ 5-263 Options
5
■ Introduction
■ Bar/Spring Forces and Moments
■ Bar End Loads
■ Shear Panel Plots
■ Max/Min Results Sorting
Main Index
➤ ■ Done
➤➤ ➤
Introduction to Results Visualization

MSC.SuperModel offers advanced results visualization tools commonly utilized in
aerospace. Results Visualization is accessible from the MSC.SuperModel main
menu.

MSC.SuperModel
Version 200x
Main Menu

Loads Tools
Property Data Plots

Configurations
Model Unmerge
Bar End Loads
Shear Panel Plots
These include max/min sorting across multiple result cases, bar shear and
moment displays, bar end load calculations and shear panel force display. Each of
these capabilities are discussed in the following documentation.
Main Index
➤ ■ Done
➤➤ ➤
5.1 Bar/Spring Forces and Moments

Bar/Spring Forces and Moments displays 1D element forces and moments at each
end of 1D elements (rods, beams and springs).
The Bar End Loads results application is accessible from the MSC.SuperModel
main menu.

hp, 2
MSC.SuperModel
Version 200x
Main Menu

Loads Tools
Property Data Plots

Configurations
Model Unmerge
◆ Bar/Spring Force & Moment
Bar End Loads
Shear Panel Plots
Main Index
➤ ■ Done
➤➤ ➤
Symbols indicating the force and moment vectors directions are displayed.
678.1
1174.3
636.7
For Bar/Spring Forces and Moments, the Element Force Table produced during an
MSC.Nastran analysis is required.
If the elements have properties, the XY plane definition is used to determine the
element directions.
v
yelem Plane 1 xelem
wb
Grid Point GB
θx
θy
Plane 2
θz zelem
wa
Grid Point GA
Main Index
➤ ■ Done
➤➤ ➤
The positive results directions for the shear forces and moments are according to
the MSC.Nastran convention, see Figure 5-1. If a value is negative, the vectors are
plotted in the positive directions with negative values.
yelem v1
T Μ1a Fx T
x
Fx Μ1b
a b
Plane 1
v1
zelem v2
Μ2a
x
Μ2b
a b
Plane 2
v2
Figure 5-1
Main Index
➤ ■ Done
➤➤ ➤
The Bar/Spring Forces and Moments main form appears as below.
Bar Force Plot Displays any load/results cases and their

subcases. If listbox is empty, then no results exist
Result Cases
in the database. If the selected results case does
5.1-LOADCASE2, Static Subcase not have Grid Point Force data and Element Force
data then Apply generates an error message
explaining which result type was missing.
Accesses a form to manipulate the format of the

displayed results. In this form you can choose to
display the results as components or resultants,
change the color, modify the scale of the vectors,
and other display functions.
Display Options... Controls the displacement of the vector base from

the bar node. Offsets the display from element
.20 nodes and element edges toward the element
center. 0.0 indicates the label will be plotted on the
Vector Position Shrink corners and 1.0 indicates all the labels will be
plotted on the element centers.
Selection Method
Elements Groups
Changing the Selection Method from the default
Elements to Groups replaces the select elements
Auto Execute
box with a list of groups. If a group is selected that
Select Elements does not contain bar elements, a warning is
displayed.
Enable this toggle if you want the displayed

Write Report File
information written to a report file. If so, you also
have to go to the FM (or File) application to
designate the Report name (see Report ... ).
Auto Reset Graphics
Erases the Bar Forces Plot and the titles. The Auto
Reset Graphics Reset Graphics toggle controls whether the
graphics from the previous Bar Forces Plot are
Apply Cancel automatically erased.
Controls whether the bar/spring forces and moments are plotted on

selected bar elements or bar elements in selected groups.
Main Index
➤ ■ Done
➤➤ ➤
The Display Options button on the previous form accesses a form for the
modification of the Bar Forces and Moment Plots display.
Options for the display of the force and/or moment are

Component or Resultant.
Options are: Force, Moment, Force/Moment and Force

Springs.
Moment
Bar Forces Options Component Force/Moment
Show: Force Resultant Springs

Display As: Component
The components change based on your option
selection for Show.
Fx Fy Fz Selecting the toggle next to the component controls
whether that component is displayed. If depressed
◆ Scale Arrows ◆ Constant
◆ (default), the component is displayed. The color
boxes next to the component control the plotting
Length 0.1 color of the component. Selecting the color
Hide Results Near Zero displays a palette of colors.
Zero Tolerance 0.01

If the Hide Results Near Zero toggle is selected,
Display Values results with an absolute value of less than the Zero
◆ Exponential ◆ Fixed Tolerance are not displayed.
2
Significant Digits
Display Title Values are plotted alongside the arrow. The format
of the values is controlled by selecting Exponential
or Fixed and by specifying the significant digits.
Close
The scale of the arrows can be either Constant or Scaled based on the
magnitude of the value. The Length parameter scales relative to the
screen dimensions if Constant and scales relative to the maximum
value and the screen dimensions if Scale Arrows is selected.
Main Index
➤ ■ Done
➤➤ ➤
A sample component plot appears in Figure 5-2.
Figure 5-2 Sample Component Plot
Main Index
➤ ■ Done
➤➤ ➤
Force
Select Resultant from the Display As menu to toggle from Component to

Resultant.
Bar Forces Options
Show: Force
Display As: Resultant
Force
◆
Length 0.1
Hide Results Near Zero
Zero Tolerance 0.01
Display Values
◆ Exponential ◆ Fixed
◆
2
Significant Digits
Display Title
Close
Main Index
➤ ■ Done
➤➤ ➤
Moment
Select Moment from the Show menu plots only the moment components.
Bar Forces Options
Show: Moment
Display As: Component
Mx My Mz

◆
Length 0.1

Zero Tolerance 0.01
Display Values Note: As shown here, if the Display Values

toggle is turned OFF, the parameters for
the values display are hidden.
◆
Bar Forces Options
2 Bar Forces Options
Significant Digits
Show: Moment
Display Title Display As: Resultant
Moment
Close
◆
Length 0.1

Zero Tolerance 0.01
Display Values
◆
2
Significant Digits
Display Title
Close
Main Index
➤ ■ Done
➤➤ ➤
Force/Moment
Select Force/Moment plots both the forces and the moments.
Bar Forces Options
Show: Force/Moment
Display As: Resultant
Force Moment
◆
Options for the display of the Force/Moment is
Length 0.1 Component or Resultant.
Zero Tolerance 0.01 Bar Forces Options
Display Values
◆ Display As: Component
2
Significant Digits
Display Title
Fx Fy Fz
Mx My Mz
Close
Scale Arrows Constant
Length 0.1
Zero Tolerance 0.01
Display Values
Exponential Fixed
2
Significant Digits
Display Title
Close
Main Index
➤ ■ Done
➤➤ ➤
Springs
Select Springs to plot the springs internal forces.
Bar Forces Options
Show: Springs
Display As: Component Note: Springs internal loads may only be
displayed as a component mode.
Fx Fy Fz
Mx My Mz
Scale Arrows Constant
Length 0.1
Zero Tolerance 0.01
Display Values
Exponential Fixed
2
Significant Digits
Display Title
Close
Main Index
➤ ■ Done
➤➤ ➤
5.2 Bar End Loads

Bar End Loads plots the bar end loads as calculated from the grid point and
element forces. This function requires the existence of a Grid Point Force Balance
Table and Element Force Table as produced during an MSC.Nastran analysis.
Main Index
➤ ■ Done
➤➤ ➤
The Bar End Loads results application is accessible from the MSC.SuperModel
main menu.

MSC.SuperModel
Version 200x
Main Menu
Loads Tools
Property Data Plots

Configurations
Model Unmerge
◆ Bar End Loads
Shear Panel Plots
More ➠
When the Bar End Loads application is selected on the MSC.SuperModel main
menu, the following form is displayed.
Main Index
➤ ■ Done
➤➤ ➤
All of the Results Cases that exist in the current database

are shown. If the listbox is empty, then no results exist in
the database. If the selected results case does not have
Grid Point Force data and Element Force data, then press
Apply to generate an error message explaining which
result type was missing. Only one result case may be
selected and this is highlighted.
Press the Display Options button to display the following

form in order to enable further plot control.
Setting this toggle will result in all inplane shell forces

being incorporated in the calculation of bar end forces.
The entities on which to display bar end loads results may

be specifically selected or identified by Group
membership.
For the Elements Selection Method, if no bar or 2D

elements are selected, then all currently posted bars and
2D elements are selected by default.
The bar end loads and shear panel flows may be written
to a text report file.
Clears all the Bar End Load plots from the current
graphics viewport.
Main Index
➤ ■ Done
➤➤ ➤
Display Options
Element Labeling
Bar end load values may be enabled or disabled. If
Plot Bar End Loads enabled, the color of the labels can be controlled
through a palette of available colors.
0,0
Load Label Position Shrink
Plot Shear Flow Offsets the display from element nodes and element
edges toward the element center. 0.0 indicates the
0,0 label will be plotted on the corners and 1.0 indicates
all the labels will be plotted on the element centers.
Shear Label Position Shrink
Format Type
Fixed Point Associated shear panel flows may be enabled or
Exponential disabled. If enabled, the color of the labels can be
controlled through a palette of available colors.
0
User can select display results in either fixed pointk
Displayed Precision or scientific notation format.
Display Title
Moving slide bar to right increases the number of
significant digits displayed.
OK
Main Index
➤ ■ Done
➤➤ ➤
5.2.1 Requirements
There are certain requirements that must be met in order for the bar end forces to
be plotted.
1. The MSC.Nastran analysis must be run with GPFORCE=ALL and

FORCE(SORT1, REAL, BILIN)=ALL in the Case Control for all subcases.
PARAM,POST,-1 must appear in the Case Control or Bulk Data Section of
the input file to ensure that the Grid Point Force Balance Table is written to
an OUTPUT2 file. This is automatic when MSC.Patran is used to create the
input deck.
2. The existence of two results quantities in the database is required for the
execution of the Bar End Loads application. The name of these results can be
seen in the Results application. They must not be altered or deleted. The
labels are:
•Grid Point Forces, Elements
•Bar Forces, Translational
Main Index
➤ ■ Done
➤➤ ➤
5.2.2 Description of Calculations

Figure 5-3 is a simple model that is used to show a sample calculation. It is fixed on
the left side and loaded with 1000 lbs. force distributed to the 3 nodes on the right.
All the elements are in the XY plane.
333.33
12
8
17 333.33
11
9 23
7
6
16 333.33
14 10
8 22
6
21
15
5
11 4 13
7
3
5
19 20
2 10 12
3
2 4
18
1 9
Figure 5-3 Bar End Loads Example
Main Index
➤ ■ Done
➤➤ ➤
For the example calculations, Elements 12 and 20 are used. Element 20 is a quad
element with membrane properties. Element 12 is a bar element with CBAR
properties.
8
(33.7346, 28.3195)
7
13.821
6.915
7
5 12
20
Direction Cosine
<0.765, 0.643, 0.0>
4
8.297
14.679 (22.4923,18.8797)
4
This Bar End Loads and Shear Panel Flow calculation requires the Grid Point Force
data to be aligned along the panel element edge. For each element node, a matrix
of the direction cosines of the two adjacent edges and the normal to those
directions is inverted.
Direction Cosines8 Matrix of Direction Cosines Inverted Matrix

<-0.812, -0.583, 0.0> Node 4 Node 4
13
5 0.765 -0.009 0.0 1.316 -0.012 0.0
<0.009, 0.999, 0.0>
7
5 0.643 -0.999 0.0 0.846 -1.008 0.0
20
<-0.009, -0.999, 0.0> 0.0 0.0 -1.0 0.0 0.0 -1.0

12
3
<0.765, 0.643, 0.0>

4
Main Index
➤ ■ Done
➤➤ ➤
The inverted matrix is then multiplied by the Global Grid Point Force for that
element at that node.
Grid Point Force Data Inverted Matrix GPF GPF

-93.5 8
Lower Left Node Global Aligned
5 -50.4
1.316 -0.012 0.0 184.0 242.6
13
-378.4
287.8 7 0.846 -1.008 0.0 -33.3 189.3
5
20
-124.3 0.0 0.0 -1.0 0.0 0.0

207.9
12
3
184.0 4
-33.3
These transformed values are used for the remaining calculations in which Grid
Point Force data is required.
The Bar End Loads are calculated using the Bar Force loads from the results file.
The Bar Force results contain the element axial load values. The Grid Point Force
for each end of the bar element is subtracted from the axial load for each element.
These become the bar end loads for that bar element.
Aligned Grid Point Forces

Bar End Loads
242.6 -380.4
BEL = Axial Load - GPF
N1 N2 BEL1 = -1477 -242.6 = -1729.6 lb
Axial Load = -1477.0
BEL2 = -1477 -(-380.4) = -1096.6 lb
BEL1 = -1729.6 BEL2 = -1096.6
Main Index
➤ ■ Done
➤➤ ➤
A plot of this example appears in Figure 5-4.
Figure 5-4
Main Index
➤ ■ Done
➤➤ ➤
5.3 Shear Panel Plots

Shear Panel Plots can be displayed either as the shear flow along all four edges or
the element average shear flow.
The Shear Panel Plots application is accessible from the MSC.SuperModel main
menu.
MSC.SuperModel
Version 200x
Main Menu

Loads Tools
Property Data Plots

Configurations
Model Unmerge
Bar End Loads
◆ Shear Panel Plots
Main Index
➤ ■ Done
➤➤ ➤
Shear Panel Plots extracts the edge shears from shear elements and plots them at
the element edge locations. The Average Shear Flow plot is the average of the four
edge shears displayed at the element centroid.
The orientation of these values are shown in Figure 5-5.
q3
G4 G3
q2
q4
G2
q1
G1
Figure 5-5 Shear Panel Flow
Main Index
➤ ■ Done
➤➤ ➤
The Shear Panel Plots main form appears as follows.

Shear Element Plot
Select Result Cases

5.1-LOADCASE2, Static Subcase
Displays any load/results cases and their
subcases. If this listbox is empty, then no results
exist in the database. If the selected results case
does not have Element Force data then Apply
generates an error message explaining which
result type was missing.
Press the Display Options button to display the

following menu for further plot control.
Display Options...
Selection Method
Elements Groups The entities on which to display shear results may be

specifically selected or identified by Group
membership.
Auto Execute
Select Elements
A text report file can be generated for shear panel

Write Report File flow values.
Auto Reset Graphics
Erase the Shear Element Plot.

Reset Graphics
Apply Cancel
Main Index
➤ ■ Done
➤➤ ➤
Offsets the display from element nodes and

element edges toward the element center. 0.0
indicates that the label is plotted on the corners
and 1.0 indicates all the labels are plotted on
the element centers. This is useful in
differentiating the edge shears of adjacent
elements.
Force
Stress
Determines whether to display the element

shear forces as is or convert to stress.
Plot Edge Shear plots the edge shears on

each edge whereas Plot Average Shear plots
the average shear calculated by averaging the
four edge shears. The label colors can be
controlled using the available color palettes.
Main Index
➤ ■ Done
➤➤ ➤
A Shear Element Plot of forces with Plot Average Shear selected results in
Figure 5-6.
Figure 5-6 Average Shear Flow Plot
Main Index
➤ ■ Done
➤➤ ➤
A Shear Element Plot of forces with Plot Edge Shear selected results in Figure 5-7.
Figure 5-7 Edge Shear Flow Plot
Main Index
➤ ■ Done
➤➤ ➤
Note that in Figure 5-7, edge shears on adjacent edges are difficult to differentiate.
Changing the Label Position Shrink offsets the edge shears so that the shears on
adjacent edges can be seen in Figure 5-8.
Figure 5-8 Modified Edge Shear Flow Plot
Main Index
➤ ■ Done
➤➤ ➤
5.3.1 Requirements
To make a Shear Panel Plot, Element Forces must be requested when submitting
the analysis. The shear element results data is imported from the MSC.Nastran
results file, creating a result type of Shear Panel Forces, Shear. The result contains
four values for each Shear Panel element. The values represent the q1, q2, q3, and
q4 edge shears.
Main Index
➤ ■ Done
➤➤ ➤
5.4 Max/Min Results Sorting

The Max/Min Results Sorting postprocessing utilities permit sorting of results
across multiple load cases based on a user-specified criteria. The results of the sort
are displayed on each element with the load case and the maximum (or minimum)
value.
Max/Min Sort is accessible from the MSC.SuperModel main menu.

MSC.SuperModel
Version 200x
Main Menu
Loads Tools
Property Data Plots

Configurations
Model Unmerge
Bar End Loads
Shear Panel Plots
◆ Max/Min Results Sorting
This is the main Max/Min Results Sorting form. If you are operating from within
the File Manager, results can be compared between submodels with different
numbering schemes. If the File Manager is not running, then the numbering
schemes are assumed identical among the models.
Main Index
➤ ■ Done
➤➤ ➤
The Max/Min results sorting capabilities of MSC.SuperModel are accessed

through the main form shown below. This form enables the user to compare
results obtained in other databases as well as across multiple results cases. In
addition, the user can sort results for either selected elements or nodes as well as
by groups or current viewport. Results obtained from any Max/Min sort may also
be saved to a Patran ASCII report file.
Select to enable Max/Min sorting across

multiple databases (see next page).
Max/Min Result Sorting
Select to specify which results for a
Compare Other Models... Max/Min sort. You can select results in any
of the databases previously specified.
Select Results...
Controls ... After the results are specified, select to

specify how the results of a Max/Min sort
Max-Absolute
are displayed.
Sort As:
Select By: Entities Type of Max/Min sorting can be varied.

Options include: Max-Algebraic, Max-
Absolute, and Min-Algebraic.
Select Elements
Specify which entities are to be included in

the Max/Min results sort. Options include
selecting by node/element ID, group or
viewport. For multiple databases only
Write Report File
elemental results may be specified.
Reset Graphics Toggles to enable results of a Max/Min

sort to be written to a standard Patran
Apply Cancel report file.
Resets the display to remove any Max/Min

plot markers.
Closes the form and restores the settings

that were present since the last refresh.
Performs a Max/Min sort and displays the

results in the current graphics viewport as
well as in a report file, if requested.
Main Index
➤ ■ Done
➤➤ ➤
If you are using the SuperModel File Manager, then the following form displays
when you select Compare Other Models on the main Max/Min Result Sorting
form.
Supermodel Selection
Existing Files
Current Hierarchy: proj1 conf1 comp1 team1

Current Filter: * Supermodel Uncompressed | Compressed | Online Working
File Descriptions By default, all SuperModels

with results are displayed.
complex wing
complex wing with position transform for aileron Select which SuperModel
merged model of complex wing with 3 subcases for comparison.
merged model of complex wing with 3 subcases and 1.5 load factor
merged model of complex wing with position transfers for aileron
telescope with panel configurations
telescope with panel configurations using op2 file Selects all of the available
models.
Removes all model

selections.
User SuperModel
Select All Select None selections are displayed
here as they are selected.
Selected Databases
Selecting an entry removes
36:merged model of complex wing with 3 subcases it from the list box. The
numeric on all databases is
the SuperModel internal ID
in the file manager.
Closes out the form without

recording and model
selections made by the
user. By default, Max/Min
sorting will be restricted to
the database currently
opened provided the
database is a SuperModel
OK Cancel with results.
Records all model

selections made for
Max/Min results
comparison and closes out
the form.
Main Index
➤ ■ Done
➤➤ ➤
If you are not using the SuperModel File Manager, the following form displays
when Compare Other Models is selected from the main Max/Min Result Sorting
form.
All Patran
databases in the
working directory
are displayed. Any
selected models
are highlighted.
You must manually

add the databases
to the select list
box below.
Selecting an entry
removes it from
the box.
Closes out the

form without
recording and
model selections
made by the user.
By default,
Max/Min sorting
will be restricted
to the database
currently opened
provided the
database is a
SuperModel with
results.
Records all model

selections made
for Max/Min
results
comparison and
closes out the
form.
Main Index
➤ ■ Done
➤➤ ➤
If you choose Select Results on the main Max/Min Result Sorting form, the
following menu displays. Select which results cases to compare from either the
current or multiple models as well as the specific result type.
All of the Result Cases contained in the

selected models to be compared are
listed. Selected Result Cases are
highlighted. The numeric prefix in the
result case label is of the form:
Supermodel ID:Load case ID.Subcase ID
Only the results types that exist in all of the

selected subcases for the currently
displayed model are listed. The selected
result type is expected to exist in all of the
other databases selected for comparison.
If not, a Patran fatal error is issued and a
comparison in not performed.
Depending on the result type, additional

elemental position and component
switches may display.
Closes out the form without recording and

results selections made by the user.
Records all results selections made for

Max/Min comparison and closes out the
form.
Main Index
➤ ■ Done
➤➤ ➤
Result Values
The Result Value option menu choices offered are determined by the type of result
selected. If the result is a tensor, the following options are displayed. Sort options
for a tensor (stress or strain) result.
XX
YY
ZZ
XY
YZ
XZ
Von Mises
Max Shear
Major 2D
Major 3D
Intermdt
Minor 2D
Minor 3D
If the selected result is a vector (forces or displacements), only the components are
available.
Magnitude
X Component
Y Component
Z Component
Main Index
➤ ■ Done
➤➤ ➤
Display Options
If Control was selected from the main Max/Min for, the Display Options form
displays. In the Display Options form, the user can change the default display
properties of the Max/Min sorted results.
Display Options
Select the color-filled box to display a palette of

colors. Depress and hold the mouse button, scroll
over to the desired color and then release the
mouse button. This becomes the color that is used
to identify the result case and value labels that
appear in the Max/Min Results plot.
Alters the format and precision of the displayed

results.
Varies the position and size of vectors when

displaying vector results.
Set to display Results Titles in the Max/Min Sorted

plots for the current viewport.

None
CID
Projected CID
Global
Default
Material
Element IJK
Specify where results are plotted on elements.

Options include:
Centroid
Node
All
Records all settings and closes out the form.
Main Index
➤ ■ Done
➤➤ ➤
Max/Min Legend
In MSC.SuperModel, the Critical Results Cases legend is presented to the user with
all the Load Case names that satisfy the Max/Min Sort criteria. The user may then
select those results associated with particular Load Cases to display in the graphics
viewport. The default is to display the results associated with all critical load cases.
This functionality is particularly useful if a large number of load cases satisfy the
Max/Min Sort criteria, but only a limited set are associated with the current region
of the model. The extraneous information may be disabled resulting in an
uncluttered display of the key results of interest.
Select this to deselect all of the load cases

contained in the list box.
All Critical Load Cases satisfying the Max/Min

sort criteria are initially highlighted. Those that
are not desired to appear in the display may be
unhighlighted. The numeric prefix in the result
case label is of the form:
SuperModel ID:Load Case ID.Subcase ID.
Select Apply to enable any changes made by
the user and these changes immediately
display in the viewport.
Select Cancel to close out the form and save

any changes that were made provided Apply
has been pressed prior to closing the form. If
not, then all previous setting are restored when
the form is closed.
Select OK to close out the form and enable

changes made by the user for any subsequent
Max/Min plots.
Select Save to File to save the contents of the

Critical Results Cases list box to a Patran
ASCII report file.
Main Index
➤ ■ Done
➤➤ ➤
The results of the Max/Min Sort are displayed graphically on each selected
element of the model. The maximum (minimum) result for the selected elements
or elements in the selected groups from the selected load cases maybe displayed at
either the element centroid, nodal or both positions. Nodal results are always
displayed at the nodes as shown below.
Percentage of selected elements

Max/Min Criteria. that have Max/Min value caused by
each load condition.
Critical condition information Load case identification, the

includes number of identified
bracketed number corresponds to
conditions from initial list and the load cases identified in the
names of selected critical
legend.
conditions.
Main Index
➤ ■ Done
➤➤ ➤
SM Tools ❚ 6-301 Options
the MSC/SuperModel User’s Guide
6
SM Tools
■ Introduction
■ Model Contents
■ Multi Hardcopy
■ Results Titles
Main Index
➤ ■ Done
➤➤ ➤
Introduction to SuperModel Tools

The SuperModel Tools are accessed from the SM Tools pulldown located on the
MSC.Patran main form.
♦ Geometry ♦ FEM ♦ LBCs♦ Matls♦ Properties ♦ Load Cases♦ Fields ♦Model ♦ Results ♦ Insight ♦ XYPlot ♦ SuperModel
Contents...
Analysis
Multi Hardcopy...
Results Titles...
Main Index
➤ ■ Done
➤➤ ➤
6.1 Model Contents

The Model Contents tool is accessed from the SM Tools pulldown located on the
MSC.Patran main form.
♦ Geometry ♦ FEM ♦ LBCs♦ Matls♦ Properties ♦ Load Cases♦ Fields ♦ Analysis

Model♦ Contents...
Results ♦ Insight ♦ XYPlot ♦ SuperModel
Multi Hardcopy...
Results Titles...
Main Index
➤ ■ Done
➤➤ ➤
The Model Contents tool creates a spreadsheet summary at three levels of

resolution. The lowest level of resolution is displayed in the main summary shown
below. At this level, only the number of entities of a particular type are displayed.
A more refined summary is obtained by selecting any one of the main category
buttons or any one of the cells in the spreadsheet where the contents of each group
are summarized.
The general contents of the current database are summarized into different
categories. A detailed listing of all of the contents of any category may be obtained
by selecting the button associated with that category. Then another form displays
giving an expanded summary as shown in the following pages.
User selects any one of the cells to obtain a Element summaries may be given by overall
refined summary of the elements, nodes or shape or by particular type by enabling the
MPCs contained in a given group. After appropriate toggle.
selecting a cell, another form displays
containing a detailed summary (see next Cancel closes the form and no further action
page). is performed.
Queries the database and updates the
spreadsheet to reflect any further changes.
Main Index
➤ ■ Done
➤➤ ➤
Groups
If the user selects a cell in the group summary contents spreadsheet under the
column labeled Elements, then either one of the following forms display. The
format of the element summary depends on whether the Shape or Type toggle is
set in the main form. For summary by shape, the following form is displayed.
Main Index
➤ ■ Done
➤➤ ➤
If a summary by Type is requested, then the following form is displayed. Any

MSC.Nastran element type not supported by MSC.Patran is listed as Other. A
complete listing of the MSC.Nastran element types supported may be found in the
MSC.Patran online documentation.
To obtain a listing
of the specific
element IDs,
select a cell
containing a
summary count
(see next page).
Main Index
➤ ■ Done
➤➤ ➤
If a cell in the group element summary form is selected, the following form is
displayed giving a listing of all the element IDs for a particular element type or
shape. The user also has the ability to highlight the elements contained in the list
box in the current graphics viewport.
List box contains all of the element

IDs for a particular type or shape
that exists in the group being
examined.
User can either highlight or unhighlight all of the

element IDs in the current graphics viewport.
If the user selects a cell in the group summary contents spreadsheet under the
column labeled Nodes, then the following form is displayed giving a listing of all
the node IDs contained in the group. The user may either highlight or unhighlight
the nodes in the current graphics viewport.
The nodes listed may either be highlighted or

unhighlighted in the current graphics viewport.
Main Index
➤ ■ Done
➤➤ ➤
Similarly, selecting a cell in the column labeled MPCs results in the following form
being displayed. To obtain a listing of the specific MPC IDs associated with a given
type, select any cell that has a nonzero count.
User can either highlight or unhighlight

MPCs listed in the current graphics
viewport.
Main Index
➤ ■ Done
➤➤ ➤
Properties Summary
If the Properties button on the main Model Contents form is selected, then the
following form is displayed giving a detailed summary of all of the property types
contained in the model. The summary includes the property name as well as the
MSC.Nastran type. Any property type not currently supported by MSC.Patran
will be classified as Other. A complete listing of all of the MSC.Nastran property
types currently supported may be found in the MSC.Patran online documentation.
Cancel closes the form and no further action is taken.
Main Index
➤ ■ Done
➤➤ ➤
Material Summary
If the Materials button on the main Model Contents form is selected, then the
following form is displayed giving a detailed summary of all of the material types
contained in the model. The summary includes the material name as well as the
MSC.Nastran type. Any material type not currently supported by MSC.Patran will
be classified as Other. A complete listing of all of the MSC.Nastran material types
currently supported may be found in the MSC.Patran online documentation.
Main Index
➤ ■ Done
➤➤ ➤
Coordinate Frame Summary
If the Coord. Frames button on the main Model Contents form is selected, then the
following form is displayed giving a detailed summary of all of the coordinate
frames contained in the model. The summary includes the coordinate frame name
as well as the MSC.Nastran type.
Main Index
➤ ■ Done
➤➤ ➤
Field Summary
If the Fields button on the main Model Contents form is selected, then the
following form is displayed giving a detailed summary of all of the MSC.Patran
Fields contained in the model. The summary includes the field name as well as the
MSC.Patran type.
Main Index
➤ ■ Done
➤➤ ➤
Loadcase Summary
If the Load Cases button on the main Model Contents form is selected, then the
following form is displayed giving a detailed summary of all of the load cases
contained in the model. The summary includes the load case name only. The
contents of any load case can be accessed by selecting the Load Cases application
radio button located in the MSC.Patran main form.
Main Index
➤ ■ Done
➤➤ ➤
LBC Summary
If the LBCs button on the main Model Contents form is selected, then the following
form is displayed giving a detailed summary of all of the LBC types contained in
the model. The summary includes the LBC name, the MSC.Nastran type, as well
as whether or not the LBC is static or dynamic (i.e. time dependent). Any LBC type
not currently supported by MSC.Patran will be omitted. Any association to Load
Cases is not accessible through the summary. Rather it may be obtained by
selecting the Load Cases application radio button located in the MSC.Patran main
form. A complete listing of all the MSC.Nastran LBC types currently supported
may be found in the MSC.Patran online documentation.
Main Index
➤ ■ Done
➤➤ ➤
Resultcase Summary
If the Result Cases button on the main Model Contents form is selected, then the
following form is displayed giving a detailed summary of all of the Result Cases
contained in the model. The summary includes the Result Case name only as well
as whether it contains static or dynamic (i.e., time dependent) results. The contents
of any Result Case can be accessed by selecting the Results application radio
button located in the MSC.Patran main form or any of the Results Visualization
radio buttons located on the SuperModel main form.
Main Index
➤ ■ Done
➤➤ ➤
6.2 Multi Hardcopy

Below is a brief description of each of the major sections presented in the following
Multi Hardcopy section of this chapter.
❏ Overview Discusses the general architecture of the Multi Hardcopy

function and points out the critical differences between it and
working with the conventional MSC.Patran Printer interface.
❏ User Interface Depicts and describes each of the user interface forms presented
by Multi Hardcopy functionality. (The Functional Summary
section provides hyperlinks to each of these for easier browsing!)
Main Index
➤ ■ Done
➤➤ ➤
6.2.1 Overview
The Multi Hardcopy functionality provides a method to generate similar plots for
many results cases on the same model. By defining the desired plot once, it can be
used by each result case that contains similar data, and it is displayed in a
consistent manner.
Result Case Filter

The result case filter is used to reduce the number of results and load cases
displayed in the spreadsheet to the set of interest.
Main Index
➤ ■ Done
➤➤ ➤
Plot Types
Several plot types are provided, including a combined plot that posts any subset
of the available plot types. The supported plot types for Results are: Combined,
Load Case, Deformed, Fringe, Tensor, and Vector. The supported plot types for
Load Cases are: Combined, Load Case, Vector.
Combined
Uses the functions defined for each subsequent plot type to post a series of plots
all at once and then submit the plot to the printer.
Load Case
This column behaves differently for Results or Load Cases. For Results, it allows
any of the Load Cases currently defined in the database to be plotted to the screen.
For Load Case rows, it plots the load case of that row.
Deformed
Allows for the creation of MSC.Patran Deformed plots. Deformation Results are
used to govern the display attributes. Only results types with Displacement in the
title are available to select for this plot type. This column is not available for Load
Case rows.
Fringe
Allows for the creation of MSC.Patran Fringe plots. The Fringe Plot is used to
govern the display attributes. On the Type and Component form, the results can
only be displayed as Scalar; therefore, if the result type is a tensor, then the proper
transformations for creating a scalar value are presented. This column is not
available for Load Case rows.
Tensor
Allows for the creation of MSC.Patran Tensor plots. Only results that are in the
form of tensors are available to be plotted. Tensor results are used to govern the
display attributes. This column is not available for Load Case rows.
Main Index
➤ ■ Done
➤➤ ➤
Vector
A results row allows for the creation of MSC.Patran Vector plots. Only results that
are vectors or tensors are available to be plotted. Vector results are used to govern
the display attributes. The Type and Components form are set for the result type
selected to transform the result to a vector. For a Load Case row, you can plot any
of the markers associated with the load case.
Print Options
The Print options are set up once for the entire set of plot definitions. The print
options form reads the printer.def file and uses the MSC.Patran Page Setup and
Printer Options forms.
Save Plot Definitions

The Save Plot Definitions button writes the current plot definitions to a file. The
filename is SuperModel_Hardcopy.def. If there is an existing file in the current
working directory or $HOME directory, then it is overwritten. If the file does not
exist, then a new file is created in the current working directory.
Restore Plot Definitions

The Restore Plot Definitions button reads the current plot definitions from a file.
The file name is SuperModel_Hardcopy.def. The file must exist either in the current
working directory or in the $HOME directory.
Main Index
➤ ■ Done
➤➤ ➤
6.2.2 User Interface

The Multi Hardcopy menu is in the SM Tools pulldown menu on the MSC.Patran
main form.
♦ Geometry ♦ FEM ♦ LBCs♦ Matls♦ Properties ♦ Load Cases♦ Fields ♦Model ♦ Results ♦ Insight ♦ XYPlot ♦ SuperModel
Contents...
Analysis
Multi Hardcopy...
Results Titles...
Multi Hardcopy uses a spreadsheet to display all the plot types available. Only the
load cases and results cases selected in the Filter Results Cases form is presented
in the spreadsheet on the main form. Each row of the spreadsheet is associated
with a load case or result case. Each column in the spreadsheet is associated with
a plot type. Selecting spreadsheet cells opens a form for defining the plot type. For
a load case row, the Deform, Fringe, and Tensor columns are not available.
Main Index
➤ ■ Done
➤➤ ➤
.
Selecting a spreadsheet cell opens a form for
Row Labels correspond to defining a plot. The type of plot corresponds
Results Case names or Load to the label found at the top of each column.
Case names in the database. Selecting a column label defines the plot
settings for all of the cells in a column.
Retrieves the Printer settings, creates each of Reads plot definitions from the file
the defined plots in the entire spreadsheet, SuperModel_Hardcopy.def. This file must
and outputs them to a file or printer. exist or an error message results.
Removes all plot definitions only from those
cells selected in the spreadsheet. Opens the MSC.Patran Print Options form.
Opens the Results and Load Case Filter form. Writes the current plot definitions to the file
This form enables the user to remove or add SuperModel_Hardcopy.def. in the current
rows to the spreadsheet. directory.
Displays the plot definition in a selected cell in
All plot definition information for a selected cell the graphics viewport. This switch is disabled
is displayed here. until a cell has been selected.
Main Index
➤ ■ Done
➤➤ ➤
Selecting any of the cells to display the plot control form associated with that
column. It also causes the contents of the associated row to be displayed in the
Print Information listbox. If the value is not blank, then the Print Preview button is
Enabled.
After defining a plot in the plot control forms, a value is placed in the selected
spreadsheet cell. The cell indicates the result and result type to be plotted.
When the Apply button on the main form is pressed, it retrieves the print options,
and all the plots that were defined, and then creates the plots one at a time. After
the function has created a plot, the print function is called to send the viewport to
the printer. This is done for all the defined plots.
Result Case Filter
When the Multi Hardcopy form is first opened, the user is presented with the
following form. This form is used to select the number of results cases and load
cases available for plot definitions.
Text filter for filtering the list of Results and

Load Cases displayed in the list box.
Lists all Results and Load Cases found in the

database. Load cases are identified by the
label LC. All user selections are highlighted.
The user can either select or deselect all of

the Results and Load Cases shown in the
listbox.
Closes out the form with no modification made
to the Results and Load Cases previously
selected.
Updates the list of Results and Load Cases that are available in
the Batch Hardcopy Setup main form based on the selections
made in this form.
This form can be later opened by pressing the Filter Results Case button. For the
load cases and results cases that are retained, if they had plot definitions prior to
the filtering, then the plot definitions are also retained. For plot definitions that are
filtered out, they are erased.
Main Index
➤ ■ Done
➤➤ ➤
Combined Plot
Selecting a cell in the Combined column opens the Combined Plot definition form.
Listed in the Select Plots listbox are the titles of all the other available Plot Types
that are supported. If the user only selects a single plot type, then no Combined
plot definition will be created in the main spreadsheet. Only by selecting two or
more plot types results in a spreadsheet entry being created. When the print job is
submitted, the plot types to be combined are plotted based on the definitions in
columns associated with those plot types. If a combined plot references a plot type
that is undefined, an error message is generated and no combined plot is made.
All of the Plot Types that are available for

combined plots are listed. User selections are
highlighted. However, there are no checks
made that definitions exist at the time of
selection.
Enabling this toggle results in only the

combined plot being generated, which is the
default.
Plot Only Combined Plot

Closes the form and no plot definition is
created.
Verifies that more than one plot type was selected. If so, then
a combined plot entry is created in the spreadsheet
indicating which plot types were selected. Otherwise an error
message is generated and no entry is created. The form is
also closed and can only be redisplayed by selecting a cell in
the column labeled Combine.
Main Index
➤ ■ Done
➤➤ ➤
Load Case Plot
When the Load Case column is selected for a Result Case row, the Load Case
Selection form is displayed. It contains a list of all the Load Cases in the database.
When one is selected, the value is stored in the spreadsheet cell. The load case does
not need to be the load case that created the result case.
Load Case Selection
Select Load Case
Default
LC_FORCE List s all Load Cases currently defined in the
LC_PRESS database.
Leaves the spreadsheet unchanged.

OK Cancel
Creates an entry in the spreadsheet

indicating which load case was selected.
Main Index
➤ ■ Done
➤➤ ➤
Deform Plot
When a cell in the Deform column is selected, the Result Type Selection form
appears. A similar form is also used for the Fringe, Tensor and Vector columns.
The differences are with the results types that are displayed and the result tools.
For Deform, only results types with Displacement in the name are available to be
selected.
Deform
List of all of the available Result types for the

current Results Case that satisfy the criteria
for Deformation plots.
List of all of the deformation tools that have

been previously created with the MSC.Patran
Results application. If no plot tools have been
created, then an error message will be issued
when the OK button is selected.
.Closes the form without creating an entry in

the spreadsheet.
Closes the form and creates an entry in the

spreadsheet indicating which result type and tool was
selected.
Main Index
➤ ■ Done
➤➤ ➤
Fringe Plot
When a cell in the Fringe column is selected, the Result Type Selection form
appears. The Select Fringe Result listbox is filtered to contain only results that can
be made into a fringe plot. Currently all result types can generate a fringe plot.
Fringe
List of all of the available result types for the

for Fringe plots.
Opens the Type and Component form and set

sit to display as a scalar.
This button displays whenever an element

based result type is selected. Selecting this
button opens the Select Positions form.
Closes the form without creating an entry in

the spreadsheet.
Closes the form and creates an entry in

the spreadsheet indicating which result
type and tool was selected.
User specifies at which element position to

create Fringe plots. Only one position can
be selected and must be compatible with the
result type being plotted. Otherwise an error
message will be issued and no entry will be
created in the spreadsheet.
Closes the form and records the position

setting selected.
Main Index
➤ ■ Done
➤➤ ➤
Tensor Plot
When a cell in the Tensor column is selected, the Tensor form is displayed. The
listbox is filtered to include only tensor results.
Lists all of the available results types for the

for Tensor plots.
List of all the Tensor tools that have been

previously created with the MSC.Patran


the spreadsheet.
Closes the form and creates an entry

in the spreadsheet indicating which
result type and tool was selected.

create Tensor plots. Only one position can
be selected and must be compatible with
the result type being plotted. Otherwise an
error message will be issued and no entry
will be created in the spreadsheet.

setting selected.
Main Index
➤ ■ Done
➤➤ ➤
Vector Plot
When a cell in the Vector Column is selected for a Load Case row, the Load Case
Selection form appears. The current load case name and type are listed on the form.
All the LBCs associated with this load case are listed and available for selection.
Load Case name for the load case of the

first selected spreadsheet row.
Load Case type for the current load case.
List of all the loads and boundary

conditions associated with the current load
If the All Groups toggle is set, then all of the

groups in the model are listed whereas the
Current Viewport toggle restricts selection
to only those groups posted in the current
viewport.
The user selects those groups that are

associated with the Load Case Vector Plot.
The plot, however, will only be properly
made if all of the groups selected are
posted. Selection of a group does not
automatically post it.
Closes the form without creating an entry

in the spreadsheet.
Creates an entry in the spreadsheet

indicating that a Marker Plot will be
created for this load case as well as for
which loads and boundary condition
types. .
Main Index
➤ ■ Done
➤➤ ➤
When a cell in the Vector column is selected, the Result Type Selection form
appears. The Results Types listbox is filtered to contain only results that can be
made into a vector plot. For results in tensor form, the Type and Component form
is used to define how the tensor results are converted to a vector.
Lists all of the available results types for the

current Results Case that meet the criteria for
Vector plots.
List of all the Vector tools that have been

previously created with the MSC.Patran


the spreadsheet.
Closes the form and creates an entry

in the spreadsheet indicating which
result type and tool was selected.

create Tensor plots. Only one position can
be selected and must be compatible with
the result type being plotted. Otherwise an
error message will be issued and no entry
will be created in the spreadsheet.

setting selected.
Main Index
➤ ■ Done
➤➤ ➤
Print Options
The printer options are set once for each multiple plot job. The primary Print
Options form behaves similar to the standard print form, and the subforms are the
same forms as the standard print form.
The Print Options button displays the following form. The Destination databox
overrides the settings selected from the Available Printers listbox. The two buttons
Page Setup and Options open the MSC.Patran Print form. The settings are read
once for each Multiple Condition Print job.
Print
Current Viewport
Available Printers
Postscript Default Select the Current Printer. The list of Available
PatranHard Default Printers is defined by the Printer Configuration
CGM Default File (Ch. 2) in MSC.Patran Reference Manual,
HPGL Default
HPGL2 Default Part 2: Basic Functions. This file can be system
wide. but is usually user specific.
Device Device
Driver HPGL2
Name of printer where files are sent.
Destination Engineering
Subordinate form appears when this button is

Page Setup... pressed. Options on this form change with the
Current Printer.
Options...
When this button is pressed the subordinate
form with the Driver specific options displays.
Close Selections change with the Current Printer.
The Page Setup and Options Subforms are the same as used in standard
MSC.Patran.
Limitations
1. Fringe plot spectrum displays may not be disabled.
Main Index
➤ ■ Done
➤➤ ➤
6.3 Results Titles

The Results Titles provides a convenient method of customizing result titles in the
viewport.
The Results Titles application is accessed from the SM Tools pulldown located on
the top of the MSC.Patran main form. The only menu item for the Results Titles is
Results Titles.
Model Contents...
Multi Hardcopy...
$# Session file patran.ses.01 started recording at 25 Results Titles...
Main Index
➤ ■ Done
➤➤ ➤
When Results Titles is selected under SM Tools, the following form is displayed:
You can edit the title by placing the cursor anywhere

in the text box and add comments or delete The keyword list contains
keywords. To add a keyword, place the cursor in the variables that are substituted
textbox where the keyword should be placed and when printing the title.
then select the keyword.
Results Titles Template Editor

Title Keywords
MSC.Patran Version
<Result Case><Result Type>, <Component>, <Layer> Analysis Code
<Transformation Method><Scale Factor>, <Extrapolation Method>, Database Name
<Averaging Domain> File Manager File Name
Job Name
Plot Type
Results Title
Clear Defaults Formats ...
Apply Activate Reset Close
Clears all Keywork Activate invokes the Defaults sets the title Date and Time
selections made in RTD tool and toggles to to the default values. formats are set here.
the text box. "Deactivate".
Results Titles can include user-supplied text as well as keywords, which are
substituted with the information pertaining to the associated results display.
Keyword information includes File Description, Analysis Code, Database Name,
Job Name, Plot Type, Results Title, Result Case, Result Type, Component,
Transformation Method, Extrapolation Method, Averaging Domain, Averaging
Method, Layer, Scale Factor, Time, Mode, Frequency, Current Group, Date, Clock
Time. The defaults are Result Case, Result Type, Component, Layer,
Transformation Method, Scale Factor, Extrapolation Method, Averaging Domain.
Main Index
➤ ■ Done
➤➤ ➤
The Format button displays a window for changing the time and date format of the
currently selected object.
Formats
Date Format
◆ 31-Jan-96
◆
◆ 01/31/96
◆ 01-31-96
Time Format
◆ 01:30 PM
◆ 13:30
◆
◆ 01:30:20 PM
◆ 13:30:20
Reset
OK Cancel
Main Index
➤ ■ Done
➤➤ ➤
6.3.1 Usage
The Results Titles Description tool allows users to define custom results titles
using keywords to automatically generate the correct display. The Title textbox is
best seen as a template that are filled for each plot. This method automatically
replaces any titles to be displayed. The Results Titles Description must be activated
prior to results plotting. The template is then filled in by the results data used to
create the current plot tool. Currently, only one line of Results Titles Description is
allowed. The steps are as follows:
1. Open the Results Titles Description form.

2. If desired, make changes to the Title template using the keywords, or by
typing in your own title. The keywords are replaced by values from the
results data. If there is no data for a keyword, it is left blank. For example, if
the template was "Component: <Component>" and the results plot tool was
a Fringe plot of von Mises stresses, the title would be
"FRINGE: Component: von Mises".
3. Select "Activate" from the Results Titles Description form. After completion
of this task, the form may be closed.
4. Generate Results application plot tools.
5. To disable the Results Titles Description tool, open the form and select
"Deactivate".
Main Index
➤ ■ Done
➤➤ ➤
The result appears in the viewport when the Preview button is selected.
Limitations
A maximum of 72 characters can be displayed in any user defined Results Titles.
Any additional characters are truncated and will not be displayed.
Main Index
➤ ■ Done
➤➤ ➤
Main Index
➤ ■ Done
➤➤ ➤
File Manager Administrator’s Guide ❚ A-337 Options
A
File Manager Administrator’s Guide
■ Outline
■ Overview
■ Requirements
■ General Installation
■ General Customization
■ File Manager Functions Customization
■ Function Summary
■ User Interface
■ Copying MSC.SuperModel Installation
Main Index
➤ ■ Done
➤➤ ➤
Outline
The following table describes each of the major sections presented in the File
Manager Administrator’s Guide.
❏ Overview Discusses the general architecture of the File Manager from an

architecture and installation perspective.
❏ Requirements Presents the resource and system requirements for installing and
accessing File Manager.
❏ General Installation Details the installation process required to install and run File
Manager. Identifies key opportunities for customization.
❏ General Gives an overview of all of the customizations that File Manager
Customization supports. Each of the subsections presents in detail the required
steps to take advantage of this flexibility.
❏ File Manager Describes the process to add custom functions that operate
Functions either before or after the standard File Manager functions (i.e.,
Customization
Open, etc.).
❏ Function Summary Lists each of the functions available under the File Manager
Administrative submenu. Includes a description of the
capabilities as well as hyperlinks to the associated forms used to
perform each operation.
❏ User Interface Depicts and describes each of the user interface forms presented
by the File Manager Administrative submenu. The Function
Summary (p. A-374) section provides hyperlinks.
❏ Copying Describes a method to archive (backup) an entire hierarchy and
MSC.SuperModel re-installation.
Installation
This document is intended to serve as the technical reference manual for installing
and maintaining the MSC.SuperModel File Manager system. The System
Administrator should thoroughly review this manual.
Main Index
➤ ■ Done
➤➤ ➤
Overview
MSC.SuperModel File Manager is a software system composed of multiple
components that work together to provide a user-friendly layer on top of the UNIX
file system. A thorough understanding of all of its components assists you to install
and maintain MSC.SuperModel. This overview includes an introduction to the
philosophy behind File Manager as well as the architecture of the software system.
Main Index
➤ ■ Done
➤➤ ➤
Philosophy
The interface and operation of File Manager may be very familiar to you because
it is similar to most other file systems, some underlying principles make it unique
and you need to read about these differences. Specifically, File Manager introduces
the concept of Logical Files.
A logical file is a collection of related files that share a common cause. The best
example of this is familiar to MSC.Patran users.
The MSC.Patran database is generally accompanied by a journal file. This file

provides a record of the commands issued in MSC.Patran that could assist in the
reconstruction of the database. The MSC.Patran application expects these files to
always be found together and issues a warning message to the user when this
expectation is not met.
File Manager deals with this situation by treating the two files as one. It does this
in a very simple way: it collectively operates on all files of the same base name (i.e.,
a file name minus any extension). This is important from an administrative
standpoint because you may be required to provide files to the system under
certain circumstances, such as defining a new file type.
File Manager anticipates that all files at a given location with the same base file
name are to be treated as one. This assumption is always followed, in the
repository, in local and remote workspaces, and even when dealing with other
UNIX directories.
When a distinction must be made, the individual files that make up this type of
collection are referred to throughout this document as physical files. In general,
however, when a file or files are referenced they are understood to be addressing
a logical file.
Although file extensions are ignored by File Manager, there are several which are
reserved in order to support the standard operations of the software. These are
outlined in Table A-1.
WARNING: You should avoid introducing files into the system with the extensions listed in
Table A-1 that do not adhere to the intended use! Doing so can result in the disruption of File
Manager services such as maintaining file histories.
Main Index
➤ ■ Done
➤➤ ➤
The following table lists the Reserved File Extensions used by the File Manager:
Table A-1
Reserved File Extension Description
❏ .hst History File. Every logical file introduced into the File
Manager system has a history file generated. This is an
automatic procedure and this file’s existence is imperative to
the basic functionality of File Manager.
❏ .db MSC.Patran database file. This is the conventional file used to
hold FEM data for use in the MSC.Patran application. Both
submodel and supermodel file types contains a file with this
extension.
❏ .db.jou MSC.Patran database journal file. This file is the counterpart
to the database and is generally expected to exist although
this is not a firm requirement by MSC.Patran or File Manager.
❏ .db_m MSC.Patran database marker file. This file is only used when
the repository, or a portion of it, is housed on an NFS
mounted directory with respect to the client installations.
In addition to Table A-1, the MSC.SuperModel module of MSC.Patran has

identified additional extensions which should be considered reserved if you are
using File Manager in conjunction with MSC.SuperModel as follows:
SuperModel Related
Description
Reserved File Extension
❏ .gnl Reduced Stiffness Matrix (RSM) or Reduced Mass Matrix
(RMM) file. These files are used to contain the MSC.Nastran
required input data for generating ASET and DMIG entries
used in an analysis.
❏ .gnl.def RSM definition file. Contains information required to
reconstruct the RSM or RMM file.
❏ .jdf Job Definition file. Instruction sets for creating a supermodel
are stored in this file. Although File Manager does not enforce
the existence of this file for every supermodel, the
functionality in MSC.SuperModel does expect it in this file.
❏ .xdb MSC.Nastran direct access results file.
Main Index
➤ ■ Done
➤➤ ➤
Finally, several extensions are reserved for future use by the File Manager in
anticipation of added capabilities or in an effort to avoid the introduction of vague
extensions which could cause problems with customization activities as follows:
Reserved File Extension

Description
(For Future Use)
❏ .txt General text data.
❏ .bin General binary data.
File extensions not listed above are available for customization at your local site.
As the administrator of the system, it is important to work with any groups that
wish to introduce additional file types and extensions into the system in order to
avoid conflicts.
Main Index
➤ ■ Done
➤➤ ➤
Architecture
This section provides the working details of the system. The system architecture is
divided into four principle components:
1. Client & server software.

2. Database maintaining information about all files in the system.
3. Repository (i.e., directory structure) for housing the user files.
4. Local & remote workspaces that provide disk resources for working with
files accessed from the system.
These are collectively depicted in Figure A-1 in a graphic representation of a

system. This is comprised of a server, two clients, workspaces, repository, and a
dumb terminal that hosts an additional user from one of the clients.
Server Workstation
Repository Remote
smdl_fm_server executable (user files) Workspace
Client Workstation Dumb Terminal Client Workstation

(slaved to client)
FM Module of MSC.Patran FM Module of MSC.Patran
Local Workspace Local Workspace

(working directory/files) (working directory/files)
Legend
mount (direct or nfs) to disk
network connection
Figure A-1
Main Index
➤ ■ Done
➤➤ ➤
Client / Server
File Manager utilizes a client/server architecture in order to provide a central

controlling agent for the files being generated and accessed by your user
community. A single machine (the server) is responsible for maintaining
information about the files location (as well as other pieces of data) and for
providing that information to each machine (client) which requests access.
NOTE: This architecture does not preclude a user from accessing files while on the
server machine. In this instance the server machine is actually also a client and
behaves in exactly the same fashion as any other (it actually calls itself and answers
back).
The clients and server communicate via a mechanism called Remote Procedure
Calls (RPC). Essentially, an application on a client machine calls the server
machine and requests access to another resident application. The server checks to
see if the requested application is running, if not, it starts it and establishes a
connection between the two. This connection provides the means for the two
applications to exchange information. In the case of File Manager, the two
applications are:
•An MSC.Patran customization (FM Module) that provides the client side.
•An executable named smdl_fm_server that provides the server side.
For future discussions, we refer to these as the client and server, with the
understanding that we are really talking about the applications involved.
Multiple clients are supported by the server on a first-come, first-served basis.

Therefore, it is possible for a large volume of server requests to generate a queue
of pending requests and result in a performance degradation. In general, every
effort has been made to reduce the number of requests that each client makes to the
server.
Because the File Manager relies on network connections and must share the
limited network resources with other applications (e.g., ftp, rcp, and telnet), its
performance is in direct relation to the performance of the network.
Server
As previously mentioned, the server is an executable which can be started
automatically by the hosting machine. Its sole responsibility is to process requests
from the clients with regard to the logical files contained in the repository. It does
this by accessing and modifying the database.
A few of the requests that the server responds to are given. This is not a
comprehensive list, but does help to convey the responsibility of the server.
Main Index
•Lists all the files at a particular location in the hierarchy.
➤ ■ Done
➤➤ ➤
•Gives a file description and returns the base filename and UNIX path.
•Determines the physical/security state of a given file.
•Registers a file as Locked by a given user.
Important: It is important to understand that the server does not manipulate the physical
files in any way. It provides information about the file to the client and registers changes to
that data on behalf of the client.
Client
Unlike the server (which answers questions), the client takes a very active role in
fulfilling the desires of the user.
The most apparent assistance that is provided is the user interface which takes
information that is meaningful to the user and processes it into the correct server
requests to fulfill a useful task (e.g., opening a file for modification).
Not as apparent, but equally important are the operations that the client performs
behind the scenes. These include:
•Copying the physical files between the repository and workspaces.

•Ensuring that the physical files are in a workable state (e.g., uncompressed).
•Providing for the customization of many of File Manager’s features by spawning
scripts.
NOTE: This workload may seem excessive, but remember that the server may be
busy handling information requests from every client.
Database
In order to maintain information about all of the files generated by users, File
Manager utilizes a database especially designed for this job. While very different
in architecture, it is based on the same technology as the MSC.Patran database and
therefore requires no additional licensing.
NOTICE: A possible point of confusion arises when discussing databases. It is important to
note that the database associated with File Manager is not an MSC.Patran database. Instead, it
actually contains information about where to find MSC.Patran databases.
Main Index
➤ ■ Done
➤➤ ➤
The following table provides an overview of the information contained in the File
Manager database. This is presented only to help you understand the overall
system. You are not required to interface directly with the database at any time
during your position as administrator.
Files Information is maintained about a file’s:

• Name (80 character description)
• Location (full pathname to directory)
• Type (see file types below)
• Physical state (provides resource management)
• Security (provides access restrictions)
Hierarchy Information about the hierarchy is maintained:

• Level labels (customizable at installation)
• Branch labels (customizable at any time)
File Types Information that provides for categorizing all of the files in the system is
maintained and may be customized at any time.
Associations A list of file associations is maintained. This provides cross-referencing files

that are related. Additional associations may be added at any time.
Users For every user who accesses the system, a record of where they were last is
maintained. This provides a means of returning them to the same location the
next time they need to work in File Manager.
Repository
The file repository is a collection of UNIX directories where the user files are
stored. A directory exists for every branch of the hierarchy that you create
following the installation of the File Manager software. However, the correlation
between the directory name and the branch label is not discernible. Instead, the
database maintains this relationship in order to eliminate some potential problems
associated with path name lengths under UNIX.
The directories for the repository are hidden from the casual user of the system in
order to provide a degree of security. This is accomplished via the hidden file
naming convention allowed under UNIX. Every repository directory is named
following the convention .nX where X is an integer value assigned at the time the
directory is created. This convention alleviates the path length problem and serves
to hide the directory structure (through the ambiguity of the name and the use of
the “.” prefix) to make it invisible to conventional listings.
Main Index
➤ ■ Done
➤➤ ➤
As administrator, you are required to specify a location (directory path) which

serves as the base of the repository structure. From this point, the server manages
the directory structure for you. During certain situations it may be necessary for
you to intervene in this process. If the physical disk that hosts the repository
becomes exhausted, it is necessary to expand the directory structure to provide
additional space. This process is outlined under General Customization (p. A-359).
Workspaces (Local & Remote)
In order to provide concurrent access to the files in the repository, File Manager
establishes workspaces (with your help) for every client machine. A workspace is
a reserved directory location that can be used to hold working copies of a file being
accessed from the repository.
After the client has established the location of a file (through a request to the
server), the file is copied to the local workspace. This copy is named so that its
origin and owner can be distinguished in the event that the software is interrupted.
This naming convention is evident in the banner of the modeling window for the
cases when an MSC.Patran database is copied and is also presented:
<user name>-<file id>.<file extension>
where,
<user name> System name of the user who has requested the file.
<file id> Unique integer identifier that the server uses to refer to this file.
<file extension> Any of a number of extensions used to denote the intended use of the
physical file (see the previous discussion on the philosophy of the File
Manager).
Main Index
➤ ■ Done
➤➤ ➤
Requirements
System and resource requirements are placed both on the server machine and on
each of the client machines. These requirements are summarized in the following
tables with additional details provided in subsequent subsections as needed.
GENERAL REQUIREMENTS
Server Installation
•Must be successfully completed prior to undertaking any client installations
Client and Server Installations
•Require root privileges!
•Are Dependent on a pre-existing MSC.Patran installation
SYSTEM REQUIREMENTS
Server Installation
•Must have either a direct or NFS mount to the repository directory
Client Installations
•Must have network access to the server machine
•Must have either a direct or NFS mount to:
The repository directory
Local workspace directory
The remote workspace directory
Main Index
➤ ■ Done
➤➤ ➤
RESOURCE RECOMMENDATIONS
Server Machine
•Dedicated to File Manager (this is due to the potential volume of requests that
will most likely result for even a moderately sized group of users)
•At least 128M of RAM
Repository
•At least 2G of dedicated disk space (this is a general estimate of the approxi-
mate disk space required and will vary based on the number of users your
installation will support and their level of activity)
Workspace (Local or Remote)
•At least 250M dedicated to that directory space (this is a general estimate
based on typical file sizes and scratch space required for running analyses)
Main Index
➤ ■ Done
➤➤ ➤
General Installation
File Manager installation is composed of several steps that must be performed
sequentially in order to provide a stable system for the users. In addition, there are
opportunities during the installation for customizing the software in order to meet
the specific needs of your site. It is highly recommended that you completely read
through this section on installation as well as the next section on customization
before installation.
The File Manager is based on the Client/Server software model and requires
installation methods.
NT Installation
How to Install
To run the MSC.SuperModel Installation CD, load it into your CD player. It

automatically starts and you can follow the directions. If it does not automatically
start, navigate to the setup.exe file and click on it.
How to Uninstall
To uninstall, navigate to the Control Panel, Add/Remove Programs option. Select

MSC.SuperModel and click Add/Remove. Your program is now uninstalled.
UNIX Installation
How to Uninstall
An initial installation can be restarted by performing the following manual

operations. (This procedure is valid ONLY for an initial installation.)
1. Delete the file $p3_home/Filemanager/install/Defaults (NOT the file

FM_Defaults).
2. Delete any files created under the repository or workspaces. Note that
because this is a new installation there should be no user data in the
hierarchy. In particular, the file smdl_fm.database in the hierarchy must be
deleted.
Main Index
➤ ■ Done
➤➤ ➤
Server Installation
This section provides details regarding the installation of the server software for
File Manager. It is not necessary to understand every installation type
immediately. After you have performed an initial installation, the subsequent
installations only deviate slightly (although these deviations may be critical). The
installation types are briefly described in the following table.
Initial Installations The first installation of File Manager. This requires the most work
associated with customization and initialization.
File Manager Upgrade Enhancements to the File Manager software are straight forward,
but there are some important WARNINGS.
Four basic steps are required for server installation, with slight modifications to
each based on the installation type.
1. Loading the software.

2. Customizing the software.
3. Installing the software.
4. Initializing the File Manager executable.
Each of these steps is detailed in the following subsections.
Loading the Software

Currently, the File Manager software is loaded as part of the MSC.SuperModel
delivery. Regardless of the media, unloading MSC.SuperModel results in the
creation of a Filemanager subdirectory in your MSC.Patran installation directory
(typically identified as P3_HOME).
Initial Installations
No additional effort is required for loading the software during initial installation.
In the event that the Filemanager directory is not present it is necessary to reload
the MSC.SuperModel software.
Main Index
➤ ■ Done
➤➤ ➤
File Manager Upgrades
The reloading of either MSC.SuperModel or File Manager software on the server

machine requires special attention (this is not true of software reloads on client
machines). In order to allow a proper reload to occur the File Manager server must
first be stopped causing service disruption to any users that are currently in an
MSC.SuperModel session. Therefore, the following steps should be followed when
upgrading a File Manager (or MSC.SuperModel) installation.
1. Ensure that there are no MSC.SuperModel sessions currently running.

2. Stop the File Manager server process by identifying the process ID and
killing the process by using the following commands:
$ ps -ef | grep smdl_fm_server
$ kill <pid>
3. Reload the software as described below.
For upgrades to MSC.SuperModel you can now safely follow the installation
instructions provided.
If only File Manager is being upgraded, you have received a separate installation
set. This consists of a single tar file (usually delivered on tape or through direct ftp
transfer) that should be copied to $P3_HOME/Filemanager and then expanded
using the command:
$ tar -xvf <tar_file>
where <tar_file> is usually a filename of the form smdl_fm_vX.X.tar. This

operation replaces the previous existing files required by File Manager with the
latest (X.X) version.
Customizing the Software

There is one feature to customize for File Manager that MUST be addressed prior
to the initialization of the server. Specification of the hierarchy depth and level
labels should be made at this time if the default is not acceptable for your user
community. The default settings are:
1. A hierarchy depth of four.

2. The level labels: Project, Configuration, Component, and Team (in
descending order).
Please refer to the subsection in customizing associated with the hierarchy for
information on how to make changes to these default settings.
Main Index
➤ ■ Done
➤➤ ➤
In addition to the limitation that changes to this aspect of File Manager can only be
accomplished at this phase of the server installation, you should be aware of
significant differences in your ability to perform this customization depending on
the installation type.
For initial installations, the administrator should make changes to the default
settings listed above in order to provide a hierarchy which is best suited to their
users’ needs. There are no restrictions besides those listed in the subsection
regarding hierarchy customization.
Upgrades to the File Manager software DO NOT require or support changes made
to the previous hierarchy specifications. All other system customizing is
supported, but an attempt to redefine the hierarchy depth or level labels may
result in corruption of File Manager’s database. This would leave File Manager in
an unusable state and would result in an inability to identify and locate the user
files that the system had been tracking.
Installing the Software
Software installation requires a thorough understanding of the File Manager

system and how it maps to the administrators network. In particular, the
installation script prompts the administrator for following pieces of information:
1. Type of installation being performed (client or server).

2. Name of the machine that hosts the server executable.
3. Program number which refers to this client/server application.
4. Directory which serves as the respository.
5. Directory used as the local workspace for the server.
6. Directory used as the remote workspace for all clients.
The host machine is generally the machine on which the software is being loaded.
More complicated software loads (i.e. those which would have the software reside
on a machine other than the one which would be executing it) are not currently
described in this manual and the administrator should contact their local MSC
Application Engineer for assistance.
Main Index
➤ ■ Done
➤➤ ➤
The program number is a unique integer number which is recognized by the

system when it receives requests to establish client/server communications. This
number is written to two system files ( inetd.conf and rpc) and the installation
script prompts the administrator to execute commands intended to help ensure the
uniqueness of this choice. The default value provided (539117062) is as good as any
other selection unless you know it already is being used or you have been assigned
a number by your system administrator.
The directories requested (respository, local workspace, and remote workspace)

must be carefully chosen so that they comply with the system requirements in
terms of both server and client accessibility. In addition, their choice should also
be based in part on the recommended space required for each. See the
Requirements section of this chapter.
With the information readily available, the installation of the software can be
accomplished by executing the following commands:
$ cd $P3_HOME/Filemanager/install
$ ./fm_install
After responding to the questions sited above, the script provides additional
commands associated with initializing the server.
Warning: Before executing these commands consult the following section regarding
initializing the server. Failure to do so could irrevocably damage a pre-existing installation.
For initial installations no additional actions or restrictions apply.
When upgrading an existing installation, answers to the questions listed above

must match the existing installation EXACLY. The install script should provide the
original responses as the default, but if anything looks incorrect it would be best to
abort the operation and double check your information.
Note: The install script obtains it’s default information from one of two locations.
The file $P3_HOME/Filemanager/install/Defaults is sought and should be found
if you are upgrading. Otherwise, $P3_HOME/Filemanager/install/FM_Defaults
will be used under the assumption that an initial installation is required or
Defaults has somehow been deleted.
Main Index
➤ ■ Done
➤➤ ➤
Initializing the Server
The first few commands provided by fm_install are checks to ensure that the
client/server application will be properly recognized by your system. If any of the
commands or the files they operate on are unfamiliar, you should contact either
your local system administrator or MSC Application Engineer to assist you in
understanding the output of these commands.
The final command provided actually performs the initialization of the server
(hence the name initialize_server). For completeness, the command is also
provided here:
$ ./initialize_server
Warning: Initialization of the File Manager server must ONLY be attempted for initial
installations of the software! Performing this operation at any other time could result in the
loss of files previously being accessed through File Manager.
Note that the command MUST be executed from the install directory of File
Manager (which you should already be in after completing the software load).
The above command invokes a MSC.Patran session in batch mode in order to

properly configure File Manager for use. The output of this command provides
you with indications of its success or failure. In particular you should expect to see
the following lines if the initialization proceeds correctly:
$$$ SUCCESSFULLY INITIALIZED FILEMANAGER $$$
$$$ SUCCESSFULLY DEFINED DEFAULT FILE TYPES $$$
If you encounter error messages, please consult with your local MSC Application
Engineer for assistance.
Again, this is the only time when initialization should be attempted!
The initialization of the File Manger should never be attempted for this type of
installation (see the previous warning).
Main Index
➤ ■ Done
➤➤ ➤
Under rare circumstances, the loading of a software upgrade results in errors

reported regarding an inability of the client to communicate with the server. This
is a known problem on the HPUX 10.20 operating system for instance. Invoking
the above commands WILL NOT rectify these situations. You should consult your
local MSC Application Engineer if you experience any difficulty with the
installation process.
Main Index
➤ ■ Done
➤➤ ➤
Client Installation
Unlike the server installations, all client installations and upgrades are performed
identically. However they must only be attempted after a successful server
installation has been accomplished.
The steps involved in performing a client installation are:
1. Loading the software.

2. Installing the software.
3. Testing the installation.
Neither customization nor initialization is required for the client installation.
Loading the Software
Unlike the server installation, the software for a client installation is not provided
on the delivery media. Instead, it is generated by the server installation and
packaged into the file: $P3_HOME/Filemanager/install/fm_client.tar. This file
should be copied to the $P3_HOME directory of each client machine and expanded
using the following command:
$ tar -xvf fm_client.tar
In the event that the above file is not available, it is possible to load the client
software from the original media and then upgrade it to match the server
installation. To accomplish this, the following steps must be taken:
1. Unload the File Manager software per the instructions given in the Server
Installation section.
2. Copy the file $P3_HOME/Filemanager/install/Defaults from the server to
the client machine ( this may require an ftp transfer).
Either of these methods provide the necessary files for the client installation to
proceed.
Installing the Software
Software installation on a client machine requires some of the same decisions

associated with server installation. In particular, for each client machine you must
identify the directory to be used for the local workspace. This choice should be
based on the system requirements and recommendations in the Requirements
section of this chapter.
Main Index
➤ ■ Done
➤➤ ➤
In addition, it is important that the responses to the remaining question asked by

the install script match those given during server installation. This is the reason for
the previously mentioned tar file or alternatively the copying of the Defaults file
from server to client.
After the location of the local workspace has been decided, proceed with executing
the install script using:
$ cd $P3_HOME/Filemanager/install
$ ./fm_install
Then the same list of questions previously encountered during the server
installation is displayed. These are reiterated, with an indication of those questions
for which the defaults should match the previous installation (thus allowing you
to simply accept their values).
1. Type of installation being performed (client or server) [client}

2. Name of the machine that will host the server executable [default]
3. Program number which will refer to this client/server application [default]
4. Directory which will serve as the respository [default]
5. Directory which will be used as the local workspace for the server
6. Directory which will be used as the remote workspace for all clients [default]
As with a server re-installation, if the default values (with the exception of the local
workspace) do not seem to agree with how you believe the server is configured,
you should abort this process and resolve those concerns before re-running the
install script.
Testing the Installation
Even though the server initialization provides an adequate check that the
installation was performed correctly, the only way to check a client installation is
to start MSC.SuperModel and attempt to access the File Manager functionality.
This test should be performed as a non-root user and any errors which might be
encountered should be reported to your local MSC Application Engineer for
assistance in identifying and correcting the problem.
Main Index
➤ ■ Done
➤➤ ➤
General Customization
File Manager provides for a great deal of customizing both during and after the
installation process. This distinction is an important one and serves as the primary
organization for this section.
Some features of File Manager can be customized either before or after installation,
and the procedures may be slightly different. These features are identified by a
notice (similar to the one shown here) at the start of each subsection. It is important
that you reference the correct section in order to ensure that your changes are
recognized by File Manager.
NOTICE: Following installation, customization should be accomplished by the method
outlined in Post-Installation Customization (p. A-365).
Regardless of the degree of customizing that you anticipate for your installation of
File Manager it is important to review all of the options available and to have a
well-thought-out plan for implementing this system at your site. In some
instances, after the system is in use, you cannot return to the previous installation
without a great deal of effort.
Main Index
➤ ■ Done
➤➤ ➤
Pre-Installation Customization
This section covers areas of customization that should be addressed following the
software load but prior to the actual installation. The critical nature of the timing
has to do with the fact that the database, that File Manager uses to maintain
information on the file system, must be initialized during installation to match the
specific architecture that you desire for your site.
Hierarchy Layout
WARNING: This step of customizing cannot be changed after installation!
The hierarchy layout refers to the depth of the tree structure where your users
operate as well as the generic labels that each of these levels contain. File Manager
allows up to ten levels in depth to be defined and used for file storage.
Customizing is controlled using a configuration file which can be found in the

installation directory after you load the software. This file is called:
P3_HOME/Filemanager/install/smdl_fm_hierarchy
The general rules for editing this file are:
•Each line contains the label to be assigned to the next level in the hierarchy.
•Levels proceed from top (most general) to bottom (most specific).
•Comment lines may be entered by starting the line with a dollar sign ($) and can
occur throughout the file (although partial line comments are not supported).
The following is a sample customization file that establishes the default hierarchy.
$: FileManager Hierarchy Definition
$:
$: This file provides the mechanism for customizing the hierarchy
$: layout for your installation of FileManager. You may change
$: the number of levels and the labels for each to best suit your
$: needs (up to a maximum of 10 levels).
$:
$: Replace the default configuration below with the desired levels!
$:
$: Entry format: (example shows a three deep hierarchy structure)
$:<level-label>
$:<next_level-label>
$:<last_level-label>
$:
$: Reminders:
$:YOU ARE LIMITED TO TEN (10) LEVELS FOR YOUR HIERARCHY!
$:ONCE INSTALLATION IS COMPLETE CHANGES CANNOT BE MADE WITHOUT
$:RE-INSTALLING AND THUS DESTROYING THE EXISTING SYSTEM!
Main Index
➤ ■ Done
➤➤ ➤
$:
Project
Configuration
Component
Team
Administrative Privileges

outlined at the Section Post-Installation Customization (p. A-365).
Several functions provided under File Manager are restricted from use by the
general user community. These are found through the Admin... option from the
File Manager menu. In general, these operations can make drastic changes to the
system and its files and should be performed only by a select group of users that
have a thorough understanding of the system. These users are referred to as
administrators and are recognized by the system through the use of two
configuration files. Prior to installation, the file:
P3_HOME/Filemanager/install/smdl_fm_administrators
can be used to identify users who are allowed access to the additional capabilities
listed under Function Summary (p. A-374).
1. Each line contains the user-name (not user-ID) of an administrator.

2. Comment lines may be entered by starting the line with a dollar sign ($) and
can occur throughout the file (although partial line comments are not
supported).
Note that root is always given administrator privileges and there is no need to
include it in the customization file.
The following is a sample customization file that establishes the user big_kahuna
as the sole administrator.
$: FileManager Administrative User List
$:
$: To permit a user to have access to administrative functions
$: within FileManager, include their user-id on a separate line.
$:
$: Changes to this list may be made post-installation, HOWEVER they
$: must be made on the version which is placed with the FileManager
$: database! (located in <smdl_fm_repository>/smdl_fm_administors)
$:
$: Entry format: <user-id>
big_kahuna
Main Index
➤ ■ Done
➤➤ ➤
As mentioned in the header of this file, after installation the copy resident in the
installation directory is no longer the official version. This is because the file must
be copied to a location that is globally available to every client that starts File
Manager. To accomplish this, the installation process copies the file to:
<smdl_fm_repository>/smdl_fm_administrators
where, <smdl_fm_repository> is the directory name that you provide during the
installation procedure for holding the database and directory structure known
collectively as the repository.
File Associations
outlined at the Section Post-Installation Customization (p. A-365).
File associations (the ability to relate two files to one another) are an important part
of the File Manager system. After established, an association allows a user to get to
one file based on the relationship it has to another.
For example, the File Manager could be configured to hold not only FEM related
files (such as MSC.Patran databases), but also the geometry files typically used as
the starting point for FEM modeling (like CATIA or Unigraphics files). By also
providing an association labeled Parent Geometry, the user would be able to link
the geometry file imported to the FE model file that received the data. This
provides traceability to the engineering process (and potential support for
automating updates between related files).
Customization is controlled through a configuration file which can be found in the

installation directory after you load the software. That file is called:
P3_HOME/Filemanager/install/smdl_fm_associations
•Each line contains three fields delimited by colons (:). These fields hold
information about a single association:
1. Association ID - a unique integer number assigned to this association.
2. Association label - the text string by which users refer to this association.
3. Association strength.
•Comment lines may be entered by starting the line with a dollar sign ($) and can
occur throughout the file (although partial line comments are not supported).
Association strength provides a means of defining associations which are

unavailable to the user community, but can be relied on by other software
Main Index
customizations. Two options are available: Strong and Weak.
➤ ■ Done
➤➤ ➤
Strong associations are reserved for software customizations that must rely on
their existence (i.e., the user is never allowed to build or break these associations
except throughout the intended customization software). In addition, file deletions
are prohibited on files that have these types of relationships because this would
presumably render the customized software useless. These are designated in the
configuration file by entering the string Strong in the third field.
Weak associations are those to which the users have direct access. They may be
built and broken through the conventional File Manager interface and have no
affect on file deletion. These are designated in the configuration file by entering the
string Weak in the third field.
A sample customization file is shown, that establishes two file associations. The
first follows the example previously given and allows the user community to
establish pointers between FEM files and geometry files. The second is intended to
be used by a software add-on that provides a simple fastener strength check based
on inputs associated with the FEM model. The input file for this analysis can be
stored in File Manager and related to the FEM file from which the data was
gathered.
$: FileManager Association Customization File
$:
$: database, located in <smdl_fm_repository>/smdl_fm_associations.
$:
$: Entry format <assoc-id>:<assoc-label>:<assoc-strength>
$: (for more info refer to the File Manager Administrators Guide
$:
$: Warning: EXISTING ENTRIES SHOULD NOT BE CHANGED!
$: =======================================
$:
1 : Parent Geometry : WEAK
2 : Fastener Check : STRONG
WARNING: The File Manager stores information about associations based on the
association-ID. These should never be changed after established. You may add additional IDs
and even change association-labels and association-strengths, but a change to the ID may
render the system unusable!
As mentioned in the header of this file, after installation has occurred the copy
resident in the installation directory is no longer the official version. This is
because the file must be copied to a location that is globally available to every client
that starts File Manager. To accomplish this, the installation process copies the file
to:
<smdl_fm_repository>/smdl_fm_associations
Main Index
➤ ■ Done
➤➤ ➤
where, <smdl_fm_repository> is the directory name that you provide during the
installation procedure for holding the database and directory structure known
collectively as the repository.
Main Index
➤ ■ Done
➤➤ ➤
Post-Installation Customization
This section covers areas of customization that can be addressed following the
installation of File Manager. Many of these operations are also configurable prior
to installation, and doing so alleviates some of the confusion associated with
finding the correct configuration files.
Repository
Following installation, any administrator is capable of adding and removing
branches to the hierarchy being managed by File Manager. This must be
accomplished through the user interface described in the section Function Summary
(p. A-374).
The UNIX directory structure, used to hold the user files and referred to as the
repository, should not be changed without first consulting your MSC.Software
Application Engineer for guidance. File Manager starts with the directory name
which is supplied at initialization and builds subdirectories in a very regimented
manner. Relocating any of these UNIX directories makes it impossible for File
Manager to recognize any of the files being moved.
Administrative Privileges
NOTICE: Prior to installation, customization should be accomplished by the method
outlined at the Section Pre-Installation Customization (p. A-360).
Following installation, the file:

<smdl_fm_repository>/smdl_fm_administrators
where, <smdl_fm_repository> is the directory name that was provided during the
installation procedure, can be used to identify users who should be allowed access
to the additional functions listed under Function Summary (p. A-374). As with pre-
installation customization, additional administrators can be registered by adding
their user names to the file.
The following is a sample customization file that establishes the user big_kahuna
as the sole administrator.
$: FileManager Administrative User List
$:
$: To permit a user to have access to administrative functions
$: within FileManager, include their user-id on a separate line
below.
$:
Main Index
➤ ■ Done
➤➤ ➤

$: database! (located in <smdl_fm_repository>/smdl_fm_administors)
$:
$: Entry format: <user-id>
big_kahuna
File Associations
NOTICE: Prior to installation, customization should be accomplished by the method
outlined at the Section Pre-Installation Customization (p. A-360)
Following installation, the file:

<smdl_fm_repository>/smdl_fm_associations
where, <smdl_fm_repository> is the directory name that was provided during the
installation, can be used to identify the file associations supported for use by both
the user community and customized software.
The following is a sample customization file that establishes two file associations.
The first allows the user community to establish pointers between the FEM files
and geometry files. The second is intended to be used by a software add-on that
provides a simple fastener strength check based on inputs associated with the FE
model. The input file for this analysis can be stored in File Manager and related to
the FEM file from which the data was gathered.
$: FileManager Association Customization File
$:
$: database, located in <smdl_fm_repository>/smdl_fm_associations.
$:
$: Entry format <assoc-id>:<assoc-label>:<assoc-strength>
$: (for more info refer to the File Manager Administrators Guide
$:
$: Warning: EXISTING ENTRIES SHOULD NOT BE CHANGED!
$: =======================================
$:
1 : Parent Geometry : WEAK
2 : Fastener Check : STRONG
Scripts
Several scripts are provided for you to modify in order to customize the behavior
of File Manager functionality. The following table lists each of the scripts available
for modification and the subsequent sections give details. Scripts provide the
ability to do and undo an operation. These are listed together in the following table
with the undo script in parenthesis.
Main Index
➤ ■ Done
➤➤ ➤
Script Name Description
compress_XX Allow for site specific resource management through file

(uncompress_XX) compression.
offline_XX Allow for site specific resource management through file

archival, via an offline procedure.
(online_XX)
release Provide a mechanism for connecting File Manager to a
(unrelease) commercial PDM.
The first two scripts (those associated with compression and offline) actually
provide for multiple pairs of scripts. This is done by appending a numerical ID to
the script name allowing for improved methods to be implemented in the future
without losing the ability to deal with legacy operations.
For example, you may decide to utilize a new compression utility that is more
efficient at saving disk space. Both the original and new utility must be supported
(until you are absolutely certain that all files in the system are no longer
compressed with the old one). These scripts would be named compress_1 and
compress_2 respectively. In conjunction with an environment variable (see the
following section) the user may choose either method. In addition, the system
automatically knows which undo script is required to revert a file back to the
original.
After established, the numerical IDs must not be changed because File Manager
maintains information about each file’s state based on these values. Changing the
number on the script results in the inability to undo changes made to files in the
system. Of course, you can also add new scripts and associated IDs.
Environment Variables
The following table describes the environment variables that can be used to
influence the operation of the File Manager.
Main Index
➤ ■ Done
➤➤ ➤
Environment Variable Default Description
SMDL_FM_LIST_DELAY 10 Delay in seconds between refreshes of file

listings. This influences overall
performance.
SMDL_FM_COMPRESS_MODE 1 Default mode of compression to use.
Unless altered, the default method
associated with a value of 1, is the UNIX
compress/uncompress utility.
SMDL_FM_ARCHIVE_MODE 1 Default mode of archival to use. Unless
altered, the default method associated
with a value of 1, is the UNIX tar utility.
SMDL_FM_DEBUG <none> If set (to any value) turns on additional
text output to the XTERM which echoes
the operations being performed.
As originally installed, the default values provided by the system are sufficient to
allow users to begin using the system and all of it’s features. If you provide any
customization to the scripts previously mentioned, it may be necessary to ensure
that all users define the two MODE settings in order to get the correct
functionality.
Hierarchy Directory Structure

Following installation, any administrator is capable of adding and removing
branches to the hierarchy being managed by File Manager. This must be
accomplished through the user interface described in the section Function Summary
(p. A-374).
Main Index
➤ ■ Done
➤➤ ➤
File Manager Functions Customization
Overview
MSC.SuperModel provides additional customization capabilities in File Manager.
Users may now develop PCL functions that are called by the File Manger during
certain file operations. The customized actions can be defined to occur before or
after the File Manager has completed its specified task. In addition, customized
error handling functions may be added that are invoked if File Manager has
difficulty performing its intended operation. This allows users to perform any
necessary clean up operations if the failure affects their customized tasks.
Details
File Manager has been extended to allow user defined functions to be a regular
part of performed file operations. Similar to the "user_db_open" and
"user_db_close" functions of MSC.Patran. That can be used to perform tasks such
as enabling and disabling custom PCL menus, MSC.SuperModel now provides a
method for operations in addition to the normal File Manager tasks.
MSC.SuperModel does not limit the number of users that can customize a feature;
it provides opportunities for custom operations before or after File Manager
completes its task and allows for custom error handling.
Functions Which Support Customization

The following File Manager functions now support user customization:
NEW
OPEN
SAVE
SAVE_AS
CLOSE
ABORT
RECOVER
RELEASE
UNRELEASE
QUIT
Main Index
➤ ■ Done
➤➤ ➤
Sequence of Custom Function Calls

File Manager can be instructed to invoke a user-supplied function either:
•Prior to executing the standard File Manager task (designated as “PRE”),

•After successfully completing the standard File Manager task (designated as
“POST”), or
•In the event an error occurs while attempting the standard operation (designated
as “ERROR”).
Together, this collection of functions allows users the ability to interact with File
Manager operations robustly and cleanly.
Supporting Multiple Customization

MSC.SuperModel allows multiple users to register their own function names with
a particular File Manager operation. During the registration, the operation
sequence of the functions are specified as ”PRE”, ”POST”, or ”ERROR”.
Custom Function Return Status and Process Interruption

User functions that operate prior to File Manager’s own operation (i.e., those
registered as ”PRE” tasks) are allowed to terminate the file operation. This is
accomplished by returning a non-zero value in the status argument of any custom
function. When File Manager receives a non-zero status, all subsequent operations
are terminated, including additional custom functions that are yet to be invoked,
File Manager standard process functions, and any registered ”POST” or ”ERROR”
functions. An error message is posted for the user and all file states remain as is
prior to the operation.
Main Index
➤ ■ Done
➤➤ ➤
Registering Custom Functions

The following PCL is required to register custom functions with the File Manager:
smdl_fm_customize.register(<my_function>, <FM_OPERATION>,
<FM_SEQUENCE>)
where,
•<my_function> is the name of a custom PCL function that is executed as part of

the File Manager's operation.
•<FM_OPERATION> is a string constant that designates the operation which
invokes `my_function'. Acceptable values are:
NEW
OPEN
SAVE
SAVE_AS
CLOSE
ABORT
RECOVER
RELEASE
UNRELEASE
•<FM_SEQUENCE> is a string constant which designates the operation sequence
for the custom function. Acceptable values are:
PRE
POST
ERROR
Both stand-alone and class-method functions are supported. The user is

responsible for ensuring the argument compatibility of the registered functions
with the data to be passed by File Manager (see "Shared Information from File
Manager" section).
For example, the following lines tell the File Manager to execute two custom
functions. The first is called after the File Manager has finished an Open file
operation and is a stand-alone or globally defined function. The second is called if
File Manager encounters an error while performing a Close file operation.
smdl_fm_customize.register("my_open_post", "OPEN", "POST")
smdl_fm_customize.register("my_custom_class.close_error", "CLOSE", "ERROR")
Main Index
➤ ■ Done
➤➤ ➤
These calls should be placed in the p3smdl_epilog.pcl file that is automatically

loaded by MSC.SuperModel during initialization. This file is similar to the
MSC.Patran p3epilog.pcl file because it is assumed to reside in:
•Current directory
•User’s home directory
•P3HOME directory
Shared Information from the File Manager

To allow custom functions to properly operate with the File Manager, a predefined
set of arguments is passed to any registered function. This intentionally limits the
user’s knowledge of the file system to maintain data security and integrity.
In addition, each function is expected to return status as an integer value. This

status is always the last argument present. “PRE” functions may use the status to
terminate the file operation (see Custom Functions Return Status and Process
Termination sections).
The information passed to any given function depends on the associated standard
File Manager operation, as shown in the table below.
Function ID Description Hierarchy Type Access Status
New 1+ 2+ 3+ 4+ 5*
Open 1* 2* 3* 4* 5+ 6*
Save * 2*
Save As 1, 2@ 3+ 4+ 5*
Close 1* 2*
Quit *
Release 1* 2*
Unrelease 1* 2*
Abort *
Recover 1+ 2+ 3+ 4+ 5+ 6*
where
ID = Unique integer that the system uses to identify a file
Description = String that identifies a file

Main Index
➤ ■ Done
➤➤ ➤
Hierarchy = String array of branch names where the file resides
Type = String label that designates the file's type.
Access = String that denotes the ability of the user to modify the contents of a file
# - Designates the order of the arguments passed (1,2,3,4,5)
* - Argument is valid for PRE, POST & ERROR calls
+ - Argument is valid for POST calls only
[blank] - Argument NOT passed
@ - SAVE AS receives two file IDs; for the original and copy (the copy is only valid
for the “POST” task)
For example, a custom function for handling SAVE_AS operations would have the
form:
my_custom.save_as(orig_file_id, save_file_id, save_desc, save_hier)
Main Index
➤ ■ Done
➤➤ ➤
Function Summary
Selecting the File Manager Menu from the MSC.Patran main form displays a pull
down menu listing the file functions. In addition, a submenu is provided which
contains the functions associated with administration duties. These are located
under the Admin... menu option and are briefly described in the following table:

❏ Admin >
❏ Release/Unrelease... Removes or returns a file to working status. Released files
may not be accessed for modification by any user. The default
setting for files is working (i.e., unreleased).
❏ Lock/Unlock... Locks or unlocks a file (over-riding the current security).
❏ Modify File Type... Modifies an existing file type.
❏ Branches... Provides File Manager configuration controls for Branches.
Creation and deletion is provided.
❏ File Types Modifies the system configuration by creating and/or
deleting file types.
❏ Hierarchy List Lists the hierarchy to a file.
❏ Convert Provides a conversion utility that recursively finds and
converts all MSC.Patran databases below a specified branch of
the hierarchy.
Main Index
➤ ■ Done
➤➤ ➤
User Interface
User Interface section presents the interface to administrative functions. The
following sections give detail regarding the intended use and information on
available options and controls.
For a table of each of the available operations see Function Summary (p. A-374).
Release/Unrelease
Release and Unrelease functions removes or returns a file to working status.
Releasing a file prohibits any further changes to the file and it is only accessible for
Read access.
Release is available to the System Administrator and is located under

Administration - Release. Component models and associated results may be
Unmerged from Released files.
File Release
Existing Files

File Descriptions
component 1
component 2
component 3
lb test
three component
ud test
xdb test
Either function invokes the associated scripts described under Customization. By

default, the scripts for release and unrelease perform no action other than to
announce their execution.
Main Index
➤ ■ Done
➤➤ ➤
Regardless of the actions taken by the script, a file that is released is barred from
further modification by ANY user. Unreleasing the file returns it to a working state
Write access by the user community.
Main Index
➤ ■ Done
➤➤ ➤
Lock/Unlock
Locks or unlocks a file providing a security feature. Locking a file prevents a file
from being write-accessed. Components may not be Unmerged from Locked files.
This administrative functionality is useful if an unexpected exit from
MSC.SuperModel has left one or more files locked.
File Lock
Existing Files
Current Hierarchy: Exercises
File Descriptions
component 1
component 2
component 3
lb test
three component
ud test
xdb test
Lock Unlock
Cancel
Neither locking nor unlocking invokes scripts to perform their respective tasks.
WARNING: Lock and unlock files with extreme caution. Many operations performed by
MSC.SuperModel require restricted access to files being managed by File Manager. This
administrative feature disrupt those operations if targeted at a file being accessed. The feature
should only be used after obtaining a thorough understanding of what caused the locked or
unlocked situation to occur!
Main Index
➤ ■ Done
➤➤ ➤
Modify File Type

Modify File Type allows users to modify the type of any existing file. The only
restriction is that files may not be modified to a new type of Supermodel.
Modify File Type
Existing Files
File Hierarchy... File Filter... Refresh List
Current Filter: * Supermodel Uncompressed | Compressed | Online Unlocked
File Descriptions
component 1
component 2
component 3
lb test
three component
ud test
xdb test
Modify File Type

Current File Type: New File Type: Submodel
File Information
File Description:
File Type:
File Locked By:
Created:
Modified:
Associated Data::Definition
::GENEL Constructor
::GENEL Usage
OK Cancel
Main Index
➤ ■ Done
➤➤ ➤
Branches/File Types
Creating and deleting hierarchy branches and file types are controlled through the
following form. The forms appearance is controlled by the upper-most option
menus that allow the administrator to select the desired action and the object of
that action. For clarity, the Create form is shown for both of the available objects.
Delete forms vary slightly.
Branches
The following form allows the administrator to modify the hierarchy.
Branches
Action: Create Create
Delete
Project
MSC Air
The administrator works down the
Configuration
hierarchy to the level where a new
Series 100 branch is to be created. In this case,
the new branch is to be created at
Component the Team level under the hierarchy
Vertical Tail path Project: MSC Air /
Select Team
Create Team Branch
Apply Cancel
Main Index
➤ ■ Done
➤➤ ➤
File Types
The following form allows the administrator to add new file types to those that are
available by default. Deleting customized file types is also supported, however
deleting any of the default file types results in an error message being posted.
File Types
Action: Create Create
Delete
Existing Types
All
General Element
Job Definition Lists existing file types.
Submodel
Supermodel
New Type
Supply a New file type name.
Default Template... Identify a template file (see

below) for each new file type.
Apply Cancel
The name chosen for a new file type is the descriptive string that displays
throughout the user interface and should be descriptive but of moderate length
(less than 20 characters is recommended).
The designation of a template file is performed through a UNIX file widget. This
file and all files in the same directory with the same base name (see the discussion
on Logical Files) is copied to the root of the hierarchy to serve as the starting point
for users who request a new file of this type.
NOTICE: Selecting a default template is very important. Review the discussion on Logical
files and the paragraph above before defining new file types.
Main Index
➤ ■ Done
➤➤ ➤
Hierarchy List
The contents of the File Manager hierarchy may be listed and stored in a file. Users
may specify the starting point to generate the hierarchy list. The file system path
names are printed to the hierarchy listing also.
Hierarchy List
Create Hierarchy List
Project
MSC Air
Configuration The user works down the hierarchy

to the level where the hierarchy list
Series 100 is to begin. In this case, the list
begins at the Component level
Component
under the hierarchy path Project:
Vertical Tail MSC Air / Configuration: Series 100
/ Component: Vertical Tail.
Team
Select Team
List Component Branch
Vertical Tail

Select Output File... and location.
Apply Cancel
Main Index
➤ ■ Done
➤➤ ➤
Convert
MSC.Patran databases at that point and below is upwardly converted to the
current version.
Database Convert
Convert Databases in Hierarchy
Project
MSC Air
Configuration
to the level where a convert is to be
Series 100 initiated. In this case, the branch
where the convert is to begin is at
Component
the Component level under the
Vertical Tail hierarchy path Project: MSC Air /
Select Team

Convert Component Branch and location.
Vertical Tail
Apply Cancel
Main Index
➤ ■ Done
➤➤ ➤
Copying MSC.SuperModel Installation
UNIX Instructions
Use the following steps to move an entire File Manager Hierarchy from the present
location to new location.
Requirements
All actions must be performed with root authority.
Step 1: Login as Root
Step 2: Determine location of File Manager Hierarchy
# cd $P3_HOME/Filemanager/install
# more Defaults
The Defaults file looks similar to the following:

#1 : What is the name of the server machine: medan
#2 : What is the program number assigned to the server: 123456789
#3 : Where does the hierarchy reside:
/medan/users2/Filemanager_hierarchy
#4 : Where does the remote workspace reside:
/medan/users2/Filemanager_remote_ws
#5 : Where does the local work space reside:
/medan/users2/Filemanager_local_ws
Step 3: Temporarily shutdown the server
# ps -ef | grep smdl_fm_server

# kill <pid>
where <pid> is the smdl_fm_server process ID.
Main Index
➤ ■ Done
➤➤ ➤
Step 4: Backup the hierarchy on tape.
# cd <fm_dir>
# tar cvf /dev/tape ./
where <fm_dir> is the File Manager Hierarchy location, as obtained in Step 2.
Step 5: Restart the server if necessary.
Step 6: Go to the destination machine.
Step 7: Install MSC.Patran and MSC.SuperModel.
Step 8: Temporarily shutdown the server
# ps -ef | grep smdl_fm_server

# kill <pid>
where <pid> is the smdl_fm_server process ID.
Step 9: Expand the hierarchy and File Manager database from the tape.
# cd <dir_path>
# rm -rf ./*
# tar xvf /dev/tape
where <dir_path> is the File Manager Hierarchy location specified in the

installation in Step 7.
Main Index
➤ ■ Done
➤➤ ➤
Step 10: Modify the File Manager database to reference its new location.
# /usr/interbase/bin/qli
Welcome to QLI
Query Language Interpreter
QLI> ready smdl_fm.database
QLI> list adp_info (to review value of root_dir)
QLI> Update adp_info -
CON> set root_dir = ‘dir_path/hier’
QLI> list adp_info
QLI> quit
Do you want to rollback updates for QLI_0? yes
where dir_path is the File Manager Hierarchy location specified in the installation
in Step 7.
Step 11: Restart the server, if necessary.
Main Index
➤ ■ Done
➤➤ ➤
Main Index
➤ ■ Done
➤➤ ➤
Index ❚ 387 Options
# A B C D E F G H I J K L M N O P Q R S T U V W X Y Z
I N D E X
I N D E X
A E
abort, 43, 51 element force, 266, 275
administration, 43 entity filtering, 173
analysis coordinate system at equivalenced entity numbering control, 164
nodes, 179 equivalencing, 175
associating configurations to a load case, 194 example, 195, 247, 259
association, 27
association type, 27
automatic offsets, 166 F
file & user history, 24, 40
B history files, 40
user access, 41
bar end loads, 275 file associate, 43, 57
bar force and moment plots, 265 file descriptions, 25, 35
branches, 31, 379 file filter, 46
create, 64 file ids, 35
file manager
user interface, 24, 42
C file manager administrator’s guide, 338
architecture, 343
client, 344
customization, 359
close file, 43
function summary, 374
combined plot, 323
general requirements, 348
component transformation, 183
installation, 350
compress file, 43, 55
overview, 339
configuration, 181, 237
philosophy, 340
limitations, 182
resource recommendations, 349
requirements, 182
system requirements, 348
user interface, 186
user interface, 375
configuration synchronization, 184
file manager customization, 69, 369
convert, 44, 67, 382
calling sequence, 70, 370
copy file, 43, 53
details, 69, 369
creating a configuration, 187
Function Return Status, 70, 370
current group, 162
functions, 69, 369
multiple customizations, 70, 370
D overview, 69, 369
registering functions, 71, 371
database, 345 shared information, 372
default file types, 36 sharing information, 71
default_group, 162 file manager import, 162
deform plot, 325, 330 file manager upgrade, 351
delete file, 43, 52 file security, 26
deleting a configuration, 189 file selection, 47
duplicate entity merge options, 171 file states, 26
file templates, 25
Main Index
➤ ■ Done
➤➤ ➤
I N D E X
file types, 24, 25, 27, 36, 44, 379
create, 65
M
frequently asked questions, 29 max/min sort, 292
fringe plot, 326 maximum id, 174
merge criteria, 171
merge parameters, 245
G minimum id, 174
model merge, 159
grid point force balance, 275 model unmerge, 252
limitations, 253
requirements, 253
H user interface, 254
hierarchy, 23, 27, 31, 45 modify file type, 44, 63, 378
branches, 31, 44 modifying a configuration, 188
levels, 31 move file, 43, 53
hierarchy list, 44, 66, 381 MSC/PATRAN database
import options, 163
preview, 180
I multiple condition hardcopy, 316
import file, 43
initial installation, 351
interactive and batch submittal, 237
N
intermediate structure, 191 named entity prefix, 167
new file, 43, 48
newlink smdl_jdl_read_fm, 242
J
job definition, 234
procedure, 234
O
requirements, 236 offsets, 163
job definition and submittal, 233 automatic offsets, 166
configuration, 181 default offsets, 164
user interface, 238 input offsets, 167
job definition file, 241, 242 open file, 43, 56
operation, 237
L
load case, 246
P
load case plot, 324 physical file, 25, 27, 340
loads and boundary condition merge rules, 176 physical states, 27, 38
lock, 44, 62, 377 compression, 38
logical file, 25, 27, 340 plot types, 318
Main Index
➤ ■ Done
➤➤ ➤
I N D E X
post-installation customization, 365 security states, 24, 27, 38
administrative priviledges, 365 locked, 38
environment variables, 367 released, 38
file association, 366 unlocked, 38
hierarchy directory structure, 368 working, 38
repository, 365 selecting a model database from outside file
scripts, 366 manager, 258
postprocessing, 22, 76, 158, 264, 302 selecting a source model database, 255
bar end loads, 275 selecting a supermodel from file manager, 257
bar force and moment plots, 265 selecting submodels, 243, 244
max/min sort, 292 server, 344
multiple condition hardcopy, 316 server installation, 351
shear panel results, 284 file manager upgrade, 351
prefixes, 163 initial installation, 351
default prefixes, 168 shear panel results, 284
input prefixes, 170 strong association, 27
pre-installation customization, 360 submitting a merged model, 239
administrative priviledges, 361 submitting a single model, 240
file associations, 362 submodel numbering, 170
hierarchy layout, 360
print options, 319, 330
procedure, 252 T
target group for transformation, 190
Q template files, 37
tensor plot, 327
quit, 44 transformation - position, 192
transformation - rotate, 193
R
read only, 27 U
real number equality, 172 utilities, 43
recover, 43, 51
release, 44, 61, 375
rename file, 43, 54
repository, 27, 31, 33, 346
V
vector plot, 328
reserved file extension, 341, 342
result case filter, 317, 322
results text description, 331
review history, 43, 59 W
weak association, 28
workspace, 28, 33, 347
S working copies, 33
write access, 28
save as, 43, 50
save file, 43
Main Index
➤ ■ Done
➤➤ ➤
I N D E X
Main Index

MSC - SuperModel Version 2006 User's Guide

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

MSC - SuperModel Version 2006 User's Guide

Uploaded by

Copyright:

Available Formats

MSC.

■ Assembly Definition and Analysis, 233

Technical Support on the World Wide Web

Information for Technical Support

Personal Information System Information

Contacting Technical Support

Telephone and Fax:

United States Frimley, Camberley

MSC.Nastran Support Tokyo, Japan

Munich, Germany Paris, France

Rome, Italy Gouda, The Netherlands

Moscow, Russia Madrid, Spain

MSC.Patran Support mscpatran.support@mscsoftware.com

MSC Web Site

MSC Institute of Technology

CAD Partners Hardware Partners

Permission to Copy and Distribute MSC Documentation

Please complete and mail to MSC.Software Corporation for approval:

Please do not write below this line.

the MSC/SuperModel User’s Manual

MSC.SuperModel provides an integrated engineering environment that greatly

MSC.SuperModel supports significant productivity gains by enabling

The tedious, time consuming responsibility of managing project engineering data

•Division of engineering labor and model management of large structures

The MSC.SuperModel system is comprised of MSC.Nastran, MSC.Patran and the

The MSC.SuperModel module is an umbrella over MSC.Nastran, the aerospace

While MSC.SuperModel operates as an umbrella over MSC.Nastran and

1.3 Key Features

• Modeling and Simulation

Individually each of these provides immediate customer benefit and as a whole,

These tools include:

•Quick creation of finite elements

MSC.SuperModel allows engineers to model and analyze large structures as an

The Assembly and Configuration module includes:

•Reduced stiffness and mass modeling

The following is a summary of the functionality:

•User-defined hierarchy up to ten levels for managing engineering data by

Each of the MSC.SuperModel functionalities listed above is described in detail in

1.4 User Interface

1. File Manager pulldown - FM

FM Group Viewport Viewing Display Preferences Tools Insight SM Tools Help

$# Session file patran.ses.01 started recording at 25 SuperModel Main Menu

Assembly and Configurations

FM replaces File on the MSC.Patran menu.

The MSC.SuperModel Main Menu is accessed by selecting the MSC.SuperModel

Reduced Stiff. and Mass

Existing RSM Definitions

RSM Definition Name

RSM Definition Type

If another application is selected while the MSC.SuperModel Main Menu or

Apply and Cancel

1.5 Run-Time Access

•Modeling and Simulation

Each of these is individually licensed and optionally accessible at run-time.

where <logical> = TRUE or FALSE

and “start_fm”, “start_cae” and “start_prepost” refer to the File Manager,

the MSC/SuperModel User’s Manual

■ File Information and States

MSC.SuperModel Version 200x

FM Group Viewport Viewing Display Preferences Tools Insight SM Tools

$# Session file patran.ses.01 started recording at 25

Fundamental to MSC.SuperModel is its ability to support multiple structural

❏ Introduction Discusses the general architecture of the File Manager and