FrameWorks Plus Write/Read for SAP2000

A number of new utilities have been developed that allow the exchange of model information between Intergraphs FrameWorks Plus (FWP) and AP!"""# A model created in FWP ma$ now be exported to AP!"""% where it can be modified% anal$&ed and designed% and changes to the frame section properties ma$ be imported back into FWP from AP!""" to update the model# ome of the highlights of the model exchange are as follows' Ph$sical (embers ) AP!""" will recogni&e a FWP Ph$sical (ember% including tart*+nd ,ocation% (ember -rientation% +nd .eleases% +nd .estraints% and ection Properties# Ph$sical (embers are assigned /roup 0ames within AP!""" to ensure consistent Ph$sical (ember design Ph$sical Arcs (aterial Properties ,oads and ,oad 1ases% including all ,oads on Ph$sical (embers ,oad 1ombinations (embers ma$ be exported based on a AP!""" Filter election et (odel ma$ be exported in an$ set of ,ength and Force 2nits

+xport Attached (odel ) tructure and ,oads from Attached (odels will be included in AP!""" Anal$sis file# In addition to exporting this information% design changes from AP!""" can be imported back into the FWP model set

Application Programs

3he five (4) FWP application program files (and their corresponding dialog boxes) that make up the FWP* AP!""" interface are as follows' ap!"""#ma ) SAP2000 master menu bar ap5exp#ma ) FWP to SAP2000 model export dialog box ap5des#ma ) SAP2000 to FWP section import dialog box (section updates) ap5seca#ma ) FWP section database dialog box (creates a user controlled sections database readable by SAP2000) ap5filt#ma ) FWP to SAP2000 filter dialog box (user controlled filter options) ee Appendix 6 for information on how to configure $our workspace so that FWP can locate the AP!""" applications#

Write SAP2000 Input

3he File 7 Anal$sis 7 Write AP!""" command activates the AP!""" master menu bar# AP!""" provides an interface for exporting and importing with FrameWorks Plus# elect 8+xport9 to start the process of creating interface files for AP!""" containing :

FWP geometr$ and loads (see below)#

When $ou select 8+xport9% the model export dialog box will appear# 3his is the dialog box where the user has control over which options are used to write out the AP!""" interface files# 3he user can create files for the entire FrameWorks P,2 model or a subset using the selection set option# If a FrameWorks P,2 model has attached models% the attached models ma$ be included in the export# As a minimum% the export option will write AP!""" interface files containing members% member geometr$% member releases and member supports# 3he FWP Ph$sical (ember name will be utili&ed to create a AP!""" /roup 0ame even when splitting up the members into elements for the anal$sis # NOT ! 3he AP!""" interface will not write out data for solid members ) it will write data for arc members#

Prefi" for "port #apping Files Title

Prefix for all of the interface files created for AP!"""# 3he ;ob title is used b$ AP!""" as an identifier for the problem to be run and appears on printed output# !

#odel Origin
3he origin of the AP!""" model can be specified either as 81oincident9 or 8-ffset b$ Point9# If offsetting b$ a point% $ou ma$ either t$pe in the coordinates of the data point in the FWP design file that is to become the origin point ("%"%") of the AP!""" model% or $ou ma$ select 8<efine hift 1oordinates b$ ,ast <ata Point9#

$engt% &nits
3he AP!""" model can be created using an$ of the following length units' Feet% Inches% (eters% 1etimeters% and (illimeters# 3he selected length units can be different from the FWP model length units#

Force &nits

3he AP!""" model can be created using an$ of the following force units' Pounds% =ips% 0ewtons and =ilo0ewtons#

#atc% FrameWorks $engt% ' Force &nits

3his item will be marked with 8x9 if the units selected match those of the FWP model# 3he interface alwa$s starts with the FWP units ) if different units are selected the 8x9 is removed# 3o return to the FWP units% simpl$ reselect the box#

"port $oadings
If selected% this option will write out all ,oads% ,oad 1ases and 1ombinations to the AP!""" interface files# If attached models are being exported% the processing of loads will be done in the following manner' <uring the initial export% if a load case is found which is not in the primar$ model% it will be placed in the primar$ model at the time and a notation will be written into the #log file# If load case properties in attached models conflict with the primar$ model load cases% the primar$ model properties will be utili&ed and the conflict will be noted in the #log file# ,oad cases are identified from one model to another b$ name onl$ (precise*consistent spelling is imperative>)# It is important that the primar$ model contain all load cases and it is desirable that attached models contain all load cases as well# ,oad combinations from the primar$ model are the onl$ load combinations exported# NOT ! ,oad case and combination names ma$ not be changed# 3he$ must first be deleted and then recreated% and the$ cannot be deleted if existing member loads are associated with the name#

(reate (%eck Plot

3his toggle enables or disables the creation of check plot graphics# 3his plot is simpl$ a view of how FWP interprets the splitting of members for an anal$tical model# AP!""" ?

ma$ actuall$ split the Ph$sical (embers differentl$ from FWP% and will most probabl$ use different I< numbers for nodes and elements# 3his option is meant to provide onl$ an approximation of the anal$tical model# If selected% the 8 how* et Plot $mbolog$9 button will appear whereb$ $ou can define the level and s$mbolog$ of the check plot as shown below'

1heck plot graphics ma$ onl$ be viewed when the levels containing the graphics are turned on for viewing% and are best viewed in a 8non@FWP view9# 3o do this% open a non@defined view (or drop a FWP view)# 3urn on the plot levels and turn off FWP levels# 3he check plot graphics are simpl$ 8non@intelligent9 (icro tation graphics which can (an t$picall$ should) be deleted with (icro tation delete commands after the$ have been viewed# If saving the check plot graphics is important% it is suggested that the graphics be 8file@fenced9 to a separate file and then deleted from the FrameWorks Plus file as the$ take up substantial space# 3his options allows the AP!""" interface files to be written for either all members and arcs or for ;ust those previousl$ selected using the selection utilit$ ( ee 2tilities 7 1reate election et with Filter elector on the AP!""" +xport*Import <ialog box)# If $our FWP model has other attached models within the same pro;ect% $ou ma$ select 8Process Attached (odels9 and the geometr$ and loads for the attached models will also be included in the AP!""" interface files#

"port Scope

"port FWP )eometr* ' $oadings

-nce all of the parameters have been set and a title for the AP!""" files have been entered ($ou must enter a title for the 8+xport A9 button to become active)% this button ma$ be pressed to generate AP!""" interface files# -nce the 8+xport ##9 button has B

been pressed% a number of binar$ files containing the model data for import into AP!""" will be created in the interface 8I039 folder under the pro;ect folder# For a complete list of these files% please see Appendix A# Please note that when creating a model containing Ph$sical Arc members% FWP will not allow these members to have loads% end releases or ;oint supports# If the writing of the AP!""" interface files is successful% the following dialog box will appear'

3his same information is written into a #log file#

(reating Section Properties

Prior to importing the FrameWorks Plus model into AP!"""% $ou will need to create a file containing the section properties used in the FWP model which can be read in b$ AP!"""# 3his is done b$ utili&ing the 2tilities 7 1reate ection Propert$ File from Active FrameWorks ,ibraries as shown below'

electing this item will result in the displa$ of the following dialog box' 4

Section Propert* File Prefi"

3his is the name to be given to the file (binar$) containing section properties which will be used b$ AP!"""#

Select Pro+ect $i,rar*

1licking on this button allows $ou to select from an$ number of section libraries for inclusion in $our AP!""" section propert$ file# Cou ma$ also include $our user librar$ if defined#

Section Filter
3he criteria allows $ou to filter specific elements into the AP!""" section propert$ file#

(reate Section Propert* File

-nce a pro;ect librar$ has been selected and a prefix for the file name specified% this button will become active and pressing it will generate a binar$ file containing the section properties (see Appendix A for file list)# In addition to the binar$ file% a #txt file will also be created which lists all of the section names#

Importing FWP model into SAP2000

After +xporting the FWP /eometr$ and ,oading% as well as 1reating a ection Propert$ File% the FWP model ma$ now be imported into AP!"""# 3o do this% start AP!"""% and go to the File 7 Import 7 FrameWorks Plus menu item on the main menu bar% as shown below'

When AP!""" imports the model% it will perform the following tasks' tart a 0ew (odel# If $ou make changes to $our FWP model% $ou cannot update $our AP!""" model b$ doing another import ) an import into AP!""" will overwrite an$ existing AP!""" model# Please see below for the AP!""" editing options# All Ph$sical (embers will be divided into Frame finite elements as needed from an anal$tical standpoint# 0on@prismatic Ph$sical (embers ma$ be imported into AP!"""% but AP!""" will not sub@divide these elements further for anal$sis# All Ph$sical Arcs will be divided into multiple 8linear9 Frame finite elements for anal$sis# All the anal$tical finite elements in a single Ph$sical (ember or Arc will be assigned a single design group name consistent with the Ph$sical (ember*Arc naming# All design optimi&ation and checking will be performed on the Ph$sical (ember*Arc so as to be consistent with FWP# If ,oad 1ase and ,oad 1ombination names are more than E characters long the$ will be truncated to E characters# If there is a duplicate name% the duplicate will be renamed with the same name truncated to F characters plus a number to make it uniGue# F

-nce the model has been imported% $ou ma$ perform the following activities' <efine /rids Add loads to Frame members Add (ass to Hoints Add ,oad 1ases and ,oad 1ombinations .e@mesh Ph$sical (embers Add new elements to the model 1hange Frame section assignments .un the Anal$sis and <esign% including optimi&ation

"porting &pdated Sections to FWP

An$ time after the (odel has been imported into AP!"""% the Frame section properties of the FWP Ph$sical (embers*Arcs can be exported back to the binar$ files created b$ FWP b$ selecting File 7 +xport 7 FrameWorks Plus# 3he export is performed onl$ if Frame elements are acceptable as checked against the FWP Ph$sical (embers*Arcs in the following manner' 1heck that one or more Frame elements full$ define the FWP Ph$sical (embers*Arcs# 0-3+' 3he user needs to be careful not to edit the structure in such a wa$ that there is no longer at least one Frame element that full$ defines the FWP Ph$sical (embers*Arcs# All Frame elements that define a Ph$sical (ember*Arc have the same local axis orientation# All Frame elements that define a Ph$sical (ember*Arc have the same section properties# -nl$ the end of the Frame elements which define the start and end points of the Ph$sical (embers*Arcs have end releases# NOTE' -nl$ the section properties assigned to existing FWP Ph$sical (embers*Arcs ma$ be updated# An$ new elements% loads% changes to geometr$% changes to materials% changes to non@prismatic sections% etc# done within AP!""" cannot be imported back into FWP at this time# In addition% onl$ sections available within the FWP ection ,ibrar$ ma$ be used when updating the FWP model#

Read SAP2000 Results

3he File 7 Anal$sis 7 .ead AP!""" .esults command activates the AP!""" master menu bar# elect 8Import9 to read in the results of the Ph$sical (embers*Arcs selection (design optimi&ation) process and update the FWP model# In general% the five steps for creating a FWP model to be anal$&ed and designed in AP!""" are as follows' :# 6uild the structural model using FrameWorks Plus% appl$ing anal$tical attributes E

such as Ph$sical (ember*Arc properties% loads% load cases and combinations# !# From within FWP% create AP!""" interface files using the Write AP!""" Input command as discussed above# ?# Import the interface files into AP!"""% and modif$ the model as needed# .un the anal$sis and design options within AP!"""# B# -nce the anal$sis and design are complete% run the File 7 +xport 7 FrameWorks Plus% which will update the binar$ files in the 8I039 director$ under the pro;ect folder as needed# 4# From within FWP% run the File 7 Anal$sis 7 .ead AP!""" .esults command#

After executing step number 4% the following menu bar will appear'

electing 8Import9 will cause the 8Import AP!""" ection 1hanges9 dialog box to appear# Pressing the 8 elect F1 (apping File9 button will result in the following file location dialog box'

Files

pecifies the map file name associated with the AP!""" interface files which now contain the revised AP!""" frame section properties#

-irectories

Identifies the director$ where the models listed in the Files list box are located# I

$ist Files of T*pe

,imits the files displa$ed in the Files list box# 3he default filter is J#sfc#

O.

.eads the selected map file# FrameWorks Plus first verifies that the interface files contain valid AP!""" frame section properties and that the AP!""" interface files correspond with the active and attached FWP models# -nce the -= button is pressed% the updated 8Import AP!""" ection 1hanges9 will appear (see below)# 3his box reports the comparison between the section si&es for the Ph$sical (embers*Arcs stored in the results files and those in the model database% as well as for those members stored in the attached models#

If sections si&es have changed% $ou ma$ update $our FWP primar$ model b$ selecting the 8Import AP!""" ection 1hanges9 button (this button will become active if the (ain (odel has an$ members that reGuire updating)# If $ou have attached models% $ou ma$ update these as well on a model b$ model basis# NOTE' 2sing the above procedure% $ou ma$ update attached models in a non@ automated manner# Kowever% $ou ma$ update $our main model and attached models in a single 8automated9 step if $ou have loaded the sections import dialog box ( ap5des#ma) via the load 2tilities 7 (<, Applications rather than from the main AP!""" menu bar# ee Appendix 6 for additional information on loading (<, applications# 1aution should be exercised when selecting this method as all models will be updated in an automated c$cle 3he process will begin with attached models reGuiring changes and end with the primar$ model# :"

Appendi" A
3he following is the list of binar$ interface files that are created when exporting a FWP model /eometr$ and ,oadings as input for AP!"""' Prefix for +xport (apping Files# Prefix for +xport (apping Files# Prefix for +xport (apping Files# Prefix for +xport (apping Files# Prefix for +xport (apping Files# F1 PF AF P, ) Created only if loads are exported ,1 ) Created only if loads are exported

An A 1II results file% Prefix for +xport (apping Files#,-/% is also created and should be checked for information regarding the success of the model export# 3he following binar$ file is created when creating a ection Propert$ File' ection Propert$ File Prefix# 1

along with the accompan$ing text file% ection Propert$ File Prefix#txt# All of these files are located in the 8I039 director$ of the pro;ect folder#

Appendi" /
3the FWP* AP!""" write*read commands are supported directl$ within the menu structure of FWP ?#!# Kowever% users with an older version of FWP ma$ access the AP!""" interface files via manual execution of the AP!""" master menu bar application# Whether the execution is through the FWP menu structure or manual% the five mdl applications must reside in a director$ pointed to b$ the (icro tation ( 5(<,APP environment variable# Please see $ou (icro tation reference materials for etting*(odif$ing the +nvironment Lariable# For users of FWP ?#! and later% use of the FWP menu command is highl$ recommended (unless automatic import is being utili&ed)# Kowever% the AP!""" (<, application program files can be manuall$ activated in the following wa$s'

.e*in
3o manuall$ activate the AP!""" master menu bar% ke$in the following mdl l SAP2000# imilarl$% ke$in mdl l SAP_DES if $ou wish to update $our FWP sections from AP!""" in the automatic mode# If the application is not found% $our environment variable has not been configured correctl$#

#icroStation #enu Application

Lia the (icro tation top menu bar under 2tilities 7 (<, Applications# croll down the available applications to 3ask I< 8 AP!"""9 ) highlight AP!""" and then click on the load button# 3he following master menu bar will appear' ::

If $ou are unable to locate AP!""" in the 3ask I< list under 2tilities 7 (<, Applications% $our environment variable has not been configured correctl$#

:!