Structural Analysis Interface Sai-Sp User Guide
Structural Analysis Interface Sai-Sp User Guide
SAI-SP
User Guide
AVEVA Solutions Limited
Disclaimer
1.1 AVEVA does not warrant that the use of the AVEVA software will be uninterrupted, error-free or free from
viruses.
1.2 AVEVA shall not be liable for: loss of profits; loss of business; depletion of goodwill and/or similar losses; loss of
anticipated savings; loss of goods; loss of contract; loss of use; loss or corruption of data or information; any
special, indirect, consequential or pure economic loss, costs, damages, charges or expenses which may be
suffered by the user, including any loss suffered by the user resulting from the inaccuracy or invalidity of any data
created by the AVEVA software, irrespective of whether such losses are suffered directly or indirectly, or arise in
contract, tort (including negligence) or otherwise.
1.3 AVEVA's total liability in contract, tort (including negligence), or otherwise, arising in connection with the
performance of the AVEVA software shall be limited to 100% of the licence fees paid in the year in which the user's
claim is brought.
1.4 Clauses 1.1 to 1.3 shall apply to the fullest extent permissible at law.
1.5 In the event of any conflict between the above clauses and the analogous clauses in the software licence under
which the AVEVA software was purchased, the clauses in the software licence shall take precedence.
Copyright
Copyright and all other intellectual property rights in this manual and the associated software, and every part of it
(including source code, object code, any data contained in it, the manual and any other documentation supplied
with it) belongs to, or is validly licensed by, AVEVA Solutions Limited or its subsidiaries.
All rights are reserved to AVEVA Solutions Limited and its subsidiaries. The information contained in this document
is commercially sensitive, and shall not be copied, reproduced, stored in a retrieval system, or transmitted without
the prior written permission of AVEVA Solutions Limited. Where such permission is granted, it expressly requires
that this copyright notice, and the above disclaimer, is prominently displayed at the beginning of every copy that is
made.
The manual and associated documentation may not be adapted, reproduced, or copied, in any material or
electronic form, without the prior written permission of AVEVA Solutions Limited. The user may not reverse
engineer, decompile, copy, or adapt the software. Neither the whole, nor part of the software described in this
publication may be incorporated into any third-party software, product, machine, or system without the prior written
permission of AVEVA Solutions Limited, save as permitted by law. Any such unauthorised action is strictly
prohibited, and may give rise to civil liabilities and criminal prosecution.
The AVEVA software described in this guide is to be installed and operated strictly in accordance with the terms
and conditions of the respective software licences, and in accordance with the relevant User Documentation.
Unauthorised or unlicensed use of the software is strictly prohibited.
Copyright 1974 to current year. AVEVA Solutions Limited and its subsidiaries. All rights reserved. AVEVA shall not
be liable for any breach or infringement of a third party's intellectual property rights where such breach results from
a user's modification of the AVEVA software or associated documentation.
AVEVA Solutions Limited, High Cross, Madingley Road, Cambridge, CB3 0HB, United Kingdom.
Trademark
AVEVA and Tribon are registered trademarks of AVEVA Solutions Limited or its subsidiaries. Unauthorised use of
the AVEVA or Tribon trademarks is strictly forbidden.
AVEVA product/software names are trademarks or registered trademarks of AVEVA Solutions Limited or its
subsidiaries, registered in the UK, Europe and other countries (worldwide).
The copyright, trademark rights, or other intellectual property rights in any other product or software, its name or
logo belongs to its respective owner.
SAI-SP User Guide
Revision Sheet
Contents Page
SAI-SP
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:1
Assumptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:1
Features of SAI-SP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:1
Guide Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:1
1 Introduction
The Structural Analysis Interface (SAI-SP) is a two way interface. It outputs the structural
model in PDMS into a STD file, ready to be used by Staad Pro. The interface will also accept
a STD file and convert the information into a PDMS structural model.
1.1 Assumptions
This document provides guidance to the structural engineer on how to prepare the structural
models for successful transfer to Staad Pro using the Staad Pro STD format and how to
make use of a STD file to create the PDMS structural model. Workout examples are given
with steps for the user to follow.
Model Preparation the Designer and Engineer Checks are used to check for
foreseeable output errors.
Loads and End Loads and members' end properties which can be created
Conditions and stored in the database.
In this section, the concepts of the transfer of PDMS model to Staad Pro will be discussed.
3.2 Connections
All SCTNs must be connected correctly. Staad Pro nodes are derived from PDMS SNODs
and PNODs for connected SCTN elements, and SCTN's POSS or POSE for free ends. For
Support in Staad Pro, Fixity attribute of the PNODs are set to FIXED or PINNED to define
the end as a fixed/pinned support for free ends.
When using the Beams & Columns application to create braces, care must be taken in
ensuring correct snodes creation. Braces is preferably be created by Bracing Configurations
which will ensure the correct snode creation.
When a SCTN span through other SCTNs element, the split utilities must be used to split
the SCTN, otherwise the connections between the intersection points will not be created in
the Staad Pro output resulting in an error.
3.3 Hierarchy
The SCTN is set as COLUmns, BEAMs or BRACes by using the PURP attribute. During
output, the user can define the hierarchy used. The hierarchy may be defined as SCTN,
SBFR, FRMW or STRU. Only SCTN that have the 'purp of hierarchy' set as COLU, BEAM
or BRAC are extracted. The processing of the extraction is highlighted in the section on
PDMS model extraction.
For example, use FRMW as the hierarchy; the hierarchy setting should be like this:
3.4 Justification
The interface recommends that NA is used as the Justification of columns and braces. TOS
is used as the Justification of beams.
In Staad Pro, the centre line is used as reference. Hence the output from the model will have
all profiles string together assuming the line between nodes lies along the centre.
The offset switch will output with offset to compensate for the justification of the beam if
required. Only the height is compensated with offset. The following figure shows the Model
output without Output Offset.
Nodes that are too close can be merged into one node while outputting the model. The user
can define the tolerance of the nodes in the Settings page of the SAI application.
For example, if there is a beam connected to a column and a brace connecting to the same
column but with a different SNODE, the 2 SNODEs will be merged if their distance is less
than the node tolerance. The following figure shows SNODs of Braces are merged to
SNODs of Beams.
Plates can be meshed manually by using the Mesh utilities provided in the Staad Pro
interface and they can be output as well.
If the Staad Pro Mesh Generator is used, the user will need to create the nodes along the
members supporting the plate manually. Using the Staad Pro interface manual mesh
generator, the extra nodes along the member is created during the output.
3.8 Catalogues
Section profiles must be mapped correctly between PDMS and Staad Pro. Besides standard
profile, UPT and Prismatic profile can also be used by setting the design parameters and
mapping file accordingly. Refer to SAI-SP Administration Guide.
3.9 Materials
Refer to SAI-SP Administration Guide.
4 Getting Started
4.1.1 Settings
The settings page consists of three sections. The sections are:
Header Section
Information from this section will be output as the header information in the STD file. Current
only SI units and SPACE structure is supported.
Tolerances Section:
The Tolerances section consists of tolerance information. These tolerances are used for
node merging. Hence it avoids very short members in the exported STD file. Very short
members may cause problems in Staad Pro calculations.
Selecting the Check boxes will display more details on the errors and the user can go to the
problematic element by selecting the error and correcting them.
Engineer Check
Unlike the Designer Check, this check focuses on the output. The Engineer checks for
correctness in Load definition, duplicate numbers of sctns and nodes if the model was
output previously. This page also allows the Engineer to set whether a SCTN is a Column,
beam or brace type if the hierarchy is not properly separated. These utilities scan the
elements in the Output List.
Step 1:
Fill the information in the setting page
Step 2:
Select the Designer Check page, select the "/EQUIPRACK/MAIN" hierarchy and select CE.
Click the Check All button. The result should be all checks have passed.
In the SAMPLE project, there are some SCTN not properly defined. Both ends of SCTN /
E3E4-1/HA1-SUPP are connecting to the same SNOD. The start of this SCTN should be
disconnected to the connecting SNOD, otherwise the output for the SCTN will be zero
length.
Step 3:
Select the Output page, select the "/EQUIPRACK/MAIN" hierarchy and select Add CE.
Step 4:
Click the Check All in Output List button. The result should be all checks have passed.
Select the Set SCTN Type to scan the hierarchy and set the SCTN purp to the correct
section type.
Set SCTN Type will set the purpose attribute of the vertical SCTNs to COLU, horizontal
SCTNs to BEAM, and the oblique SCTNs to BRAC. SCTNs with angles with the horizontal
direction less than the input box besides the button will also set to BEAM.
The programme will read the purpose attribute of the selection of the Hierarchy list to judge
the type of the SCTN.
4.3.5 Output
Step 5:
Select Output to output and the Staad Pro STD file will be created.
Prefix Setting
Prefix is the prefix of the output STD file. The name of the file will be the
prefix+outfrompdms.std.
Click the Q button to check what prefixes have already been used. All output will be sent to
the%xyzSAISP% or %SAISP% directory.
Query
The query panel allows the user to do a check on the SCTN and node numbers generated
by the output.
The SCTN Numbers form allows the user to check the number of the SCTNs and their start/
end node numbers. Select the Select Current SCTN button to navigate to a SCTN in the
list.
The information shown in the SCTN Numbers form comes from the STD file with the prefix
input in the Prefix panel.
Files
The output from the tutorial can be read into Staad Pro using the Open STD File like a
normal Staad Pro Analysis file.
5 Model Preparation
During Model Preparation, the Designer Checks and Engineer Check is used to check for
foreseeable output errors introduced during modelling.
The checks will be displayed in the following form and the user can navigate to an element
by picking a report item. Some of the checks allows the user to delete or correct the errors
found by selecting the options below. Errors are written to the errors.txt file, which can be
found in the output directory.
If the user clicks No, all the zero length SCTNs will be listed in the Checking Models form,
and the Delete Zero Length SCTN button is active. The user can click this button to delete
all the zero length SCTNs in the list, or click the lines in the list to navigate to the SCTN,
delete it manually.
The user can use the function Position > Align Secondary Nodes in the Beams &
Columns Application menu to realign the nodes.
Loads and members' end properties can be created and stored in the PDMS database.
These are analysis information and include the following:
• Member and Nodal loads;
• Member release
• Supports
All loads created must be associated with Load Cases. Loads without load cases will not be
output.
Create will create a new STRU in the current hierarchy and Apply will set the storage area
to the selected STRU.
The Load Case Name must be unique in the project. Load Case Type can be D for Dead
Load, L for Live Load and W for Wind Load. Load Case Description is optional.
Update the Load Case information and select Modify when done.
Select the Load Case and the SCTN using the options provided in the Select By.
The Start/End position and the global axis will be displayed on the SCTN selected. Input the
various values. "d1" is the distance from the connected SNOD to the Load point. Force and
Moments are based on the global co-ordinate system. Use Preview to check the position of
the Load created.
To use this form, select the loads and then use the Modify, Copy or Delete button to edit the
load.
Input the Force and Moments based on Global Co-ordinate and select the Load Case.
Select Apply and the user will be prompted to pick the SNODs. Press ESC to end the
consecutive picking will have the load created for the nodes.
Input the displacement and rotations based on Global Co-ordinate and select the Load
Case. Select Apply and the user will be prompted to pick the SNODs. Press ESC to end the
consecutive picking will have the displacements created for the nodes.
To use this form, select the nodes and then use the Modify, Copy or Delete button to edit the
load.
The Load list is populated by selecting the Filter method.
The Release can be set as Partial or Fully Release. The user selects the SCTN element by
the different Select By. If the SCTN element has got release information, it will be displayed.
The user can modify the parameters and save the information. If it is not set already,
selecting Apply will create the information.
6.6 Display
The Display panel allows a graphical display of the members and nodes information.
7 Other Features
Select Structure Simplification and the following form is used for this simplification.
Navigate to the area to storage the replacement SCTN. Click CE to set the storage area.
Note: The storage area should use a hierarchy whose Purpose attribute is set to BEAM.
Select all the SCTNs in the roof graphically. Click the Add Selection button in the form. All
the SCTNs selected are listed in the SCTNs list.
Click the Derive points from graphic picks button and then pick the upper end of one of
the columns connecting to the roof.
The Start and End position of the replacement SCTN is now listed in the SCTN's Position
list.
Press Escape on the keyboard to escape the EDG mode.
Click the Create button to create the replacement SCTN.
The replacement SCTN uses the default specification chosen in the Beams & Columns
Toolbar.
Connection SCTN
The replacement SCTN will not connect automatically. So the user needs to use the
Connect > Connect function to set the connection between the replacement SCTN and the
columns.
Output
Enter the Output page and add the roof structure to the output list, a Question form will
display.
If the user clicks Yes in the form, the hierarchy of the roof will be added to the output list.
If the user clicks No in the prompt form, this replacement SCTN will be added to the output
list. Now the roof hierarchy cannot be added to the output list any more.
Select the PANE or FLOOR in PDMS, using the Pick Panel button, after selecting the PANE
or FLOOR, the Height and Thickness will be read from the attributes into the form.
Click the Create button on the Meshed PAND List panel to create a new meshed plate
element;
Note: When the user selects Projection to Panel in the Vertex Position list, the elevation
of the meshing points will be at the position projected to the panel. Otherwise they
will be at the position picked by the user.
Click Confirm to add the plate element to the Meshed Panel List.
Note: If the plate is at the edge of a column, the user can pick the point at the position line
of the column to avoid the node of the plate to be an orphan node when it is too far
away from the position line of the column.
Note: In the output function of SAI, the original PANE or FLOOR will not be output if the
plate elements (DRAWI) are found.
To modify the position of a meshing point, the user can select the points in the Meshing
Point list, snap a new vertex and then click Confirm to modify
Do the mapping of the load cases between Staad Pro and PDMS if the user wants to import
the Staad Pro loads. Select the Staad Pro and PDMS load cases in the Lcase in STD and
Lcase in PDMS lists, click the Match button to indicate which load cases in the STD file will
be imported as which PDMS load case.
The load cases without mapping in the STD file will not be imported.
The mapping result can be saved to the file with the path input and be restored next time.
Ignore errors while inputting - if this option is not chosen, no model will be import if there
is unmatched specification in the Staad Pro model.
Trim to Pline - this option allows the user to determine whether the imported model will be
trimmed to the connecting SCTNs or not.
Section Pline Realign Rule Definition - click this button to open the Section Pline
Realign Rule Definition form, this form allows the user to set the justification line of the
imported SCTNs to the Top/NA/Bottom Pline of the SCTN
Adjust SCTN Position while updating Pline - while the beams are updating the
justification line according to the Section Pline Realign Rule, the appearance of the beams
will change (See Picture 1).
If this option is chosen, the position of the beams will be also changed to keep the beams
looking the same when the justification line of the beams are changed (See Picture 2).
Note: This will make the position of the model different from the one in Staad Pro.
Braces Connect to NA of Beams - if this option is chosen, the braces will connect to NA of
the beams. Otherwise the braces will connect to the justification line of the beams.
Save Logic SCTNs to file While Adjusting - In Staad Pro, the sections are split by the
nodes. These sections will be merged into a whole one according to some rules while they
are importing to PDMS.
In this case, there will be only one section number store in the PDMS database. This option
will let the user store those numbers of the merged sections into a text file.
When the user outputs the model imported previously, the user can check the Read Logic
SCTNs box, and input the text file of the numbers of the merged sections. Thus the output
function can read and output the model with the number same as the STD file imported.
Note: When outputting the model, the program will judge the numbers of the split SCTNs
by their start and end nodes. If the SCTN is changed, the SCTN may renumber.
Import Group - the group information in Staad Pro could be imported when this box is
checked. Groups will be stored in a GPSET element in PDMS. The user should create the
GPWL and GPSET elements by the Create > Group function in the PDMS menu before the
STD model is imported.
When the user outputs the model import previously, the user can also output the groups
after choose the GPSET element imported before.
Note: The logic SCTN number file and the GPSET must be the ones that import with the
same model.
In the Jusline Rule Definition form, the user can define the rule of all kinds of sections, the
programme will process the rules to find the matching rules for the import sections, and set
the Justline for the sections accordingly.
The Create and Remove button can add or remove a rule.
Seq define the sequence of the rule in the rules. The programme will process the rules in
the ascending order and stop when find the first matching rule.
A rule can use the Styp attribute of the SCTN, the Spref attribute of the SCTN, or the name
of the Spec hierarchy of the Spref attribute of the SCTN. The text box left bank means the
condition is ignored.
UD Express is a user defined expression that returns true or false. The programme will
navigate to the SCTN element (means the Current Element is the SCTN) and run the
expression. The expression could be a PML expression or a PML Function. For example, in
the picture above, " !!PLCMMJLIsHorizontal() " is a PML Function, and " purp of owner eq
'BRAC' " is a PML expression. Here is an example of a PML Function to check if the SCTN
is a vertical one:
define function !!PLCMMJLIsVertical() is boolean
!element = !!ce
if(!element.badref() or !element.type neq 'SCTN')then
return false
endif
!Posstart = !element.Posstart
!Posend = !element.Posend
if(!Posstart.north eq !Posend.north and !Posstart.east eq
!Posend.east)then
return true
else
return false
endif
endfunction
Note: These example functions will be provided with SAI in the %PMLLIB% folder.
Select which Pline is going to use for this profile. The user can select TOP/NA/Bottom and
the programme will check and set the appropriate Pline for the SCTN according to the Pline
of the SCTN. Or the user can input a specific Pline name in the text box.
Note: If there is a SCTN doesn't match any of the rules in the list, its jusline will be set to
NA as default.
Rules of Import
While importing the model, the program will follow some rules:
Horizontal braces will be imported into the BEAM hierarchy when the angle between the
direction of the brace and the orthogonal directions are less than 15 degrees.
When the bottom of a vertical SCTN is connecting to a BEAM, this SCTN and the
connecting vertical SCTNs will be imported to the BRAC hierarchy.
When merging SCTNs, the programme will follow the following rules:
• First merge all the columns.
• Secondary merge all the beams connecting to the columns.
• Then merge the rest of the beams. The beams with bigger size will be first merged, and
the smaller beams will connect to the bigger beams.
• Finally merge the braces.
Braces will connect to the column if the node is belonged to a column, even if it's at column/
beam connections.
Computer works may not cover all of the situations of the structural model. Some of the
model may need to be modified manually.
7.3.5 Utilities
The Utilities page provides some additional features to help the user modify the imported
model.
Align Beams - The user can click the Align Beams button to adjust the justification line of
the SCTNs after import the model. The adjust action will follow the rules defined in the
Jusline Rule Definition form. The Adjust SCTN Position while updating Pline option in
the Settings page will also affect this function.
Retrim Sections to Pline - The SCTNs will be trimmed to the connecting Pline again when
this box is checked.
Import Load - Read the STD file and create the member and nodal loads to the imported
model. To use this feature Save Logic SCTNs to file While Adjusting must be checked
when importing the structure model. Otherwise this function will not run.
Import Release - Read the STD file and create the member release information to the
imported model. To use this feature Save Logic SCTNs to file While Adjusting must be
checked when importing the structure model. Otherwise this function will not run.
Import Support - Read the STD file and create the PNOD elements at the bottom of the
columns in the imported model, and add the support information to the PNODs. To use this
feature Save Logic SCTNs to file While Adjusting must be checked when importing the
structure model. Otherwise this function will not run.
Merge - The feature to update the model. Refer to Merge.
7.3.6 Merge
When the model in the Staad Pro is changed, the user can import the new model to PDMS
again, and save the new model in a different hierarchy. This model will be the "reference
model" in PDMS. The user can use the Merge function to update the original PDMS model
to match the new Staad Pro imported. With this function, the user can always maintain the
origin model, to keep the consistency of the structural model.
Click the Merge button in the Import Model from to show this form.
Select the origin model and the update model, compare model and then the program will list
the changed elements, the user can choose the elements to accept update.
Note: The Origin Model this function compares should be a model import by the Import
Model Function, or a model which has been output by this interface once (this means
the SCTNs and the nodes are already numbered).
When CE option has been selected on the form, the program will search the hierarchies with
Purpose attribute set to "COLU", "BEAM", "BRAC" and "PANE". If CE is a STRU, the
program will search the FRMW hierarchies below. If CE is a FRMW, the program will search
the SBFR hierarchies below.
When comparing the two models, the program will only compare the elements with Purpose
of hierarchies are set.
With this function, the user will always maintain the original PDMS model. The new model
imported will be treated as the reference model.
This function will update the information as follow:
1. New SCTNs;
2. SCTNs whose position, specification or beta angle changed;
3. SCTN loads;
4. Member Releases;
5. Supports;
6. New panels;
7. Panels whose position or thickness has changed.
Rules of Comparing
The rules of comparing the SCTNs are:
1. If there is a SCTN in the origin model has an identical number (number attribute) is the
reference model, these two SCTNs will be considered as matched.
2. If the number attribute of the SCTN in the origin model is 0 or there's no SCTN with the
same number in reference model, then the program will search a SCTN in reference
model whose orientation and the start or the end position is the same as the one in the
origin model.
3. If a pair of SCTNs match the situation in 1) or 2), the program will compare the start and
end position of those SCTN, as well as beta angle, specification and design
parameters to see if it needs updating...
4. If a SCTN in the origin model does not have a match the situation in 1) or 2), the SCTN
will be consider as a "Deleted" SCTN. When doing the update, this SCTN will be
deleted.
5. If a SCTN in the reference model does not have a match the situation in 1) or 2), the
SCTN will be consider as a "New" SCTN. A new SCTN will be created when doing the
update.
For the member loads:
1. The program will check each concentrated loads and distributed loads between the two
matched SCTNs. If the load case and position of the two loads are identical, these two
loads will be considered as matched. Then the program will compare the force and
moment of these loads.
2. If a load in the origin model has no matched load, the load will be considered as a
"Deleted" load.
3. If a load in the reference model has no matched load, the load will be considered as a
"New" load.
The member releases and support information are similar to the member loads.
For the panels:
1. If there is a panel in the origin model has an identical number (number attribute) in the
reference model, these two panels will be considered as matched.
2. If the number attribute of the panel in the origin model is 0 or there's no matched
number in the reference model, then the program will search if there is a panel with an
identical origin and identical positions of three consecutive points. These two panels
will be considered as matched.
3. If a pair of PANELs match the situation in 1) or 2), the program will compare the
thickness and the positions of the corners
4. If a panel in the origin model does not match the situation in 1) or 2), the panel will be
consider as a "Deleted" panel.
5. If a panel in the reference model does not match the situation in 1) or 2), the panel will
be consider as a "New" panel.
Select the original STD file output and the SCTN file (prefix SCTN) from PDMS and the
modified file. The files will be compared and profiles that are modified will be shown in the
Modified SCTNs' list when the Compare Files is selected.
When the new profile modified in Staad Pro has no matching profile, the SCTN status may
be manually marked as Modified or Unmodified.
8 Workout Example
This chapter will output the structure /EQUIPRACK in the SAM project as an example.
To output this model, setup the Purpose attribute to indicate which hierarchy is used for
columns, beams, braces or panels respectively. (Refer to Hierarchy for more information).
Set the Purpose of these SBFR as follows:
Panels of this model will also be output. So set the Purpose of their owner. However, the
type of the owners of the panels is FRMW. In this example, SBFR is chosen as the
hierarchy to classify SCTNs, it is best to output all elements under the same owner type as
SBFR. So create two SBFR elements, set their Purpose attribute to PANE, and use the
Include function to move the two panels into those two SBFR elements.
Click the third line in the checking report: "Error: Stand and End of /E3E4-1/HA1-SUPP
connect to the same node." The 3D view will navigate to the SCTN /E3E4-1/HA1-SUPP.
Both ends of this SCTN are connecting to the same SNOD, use Connect > Disconnect to
remove the connection of the start of this SCTN.
In line 7 to 14, it is reported that the 8 SCTNs listed have displacement between the end of
the SCTN and the connecting SNOD that the distances are over the value in the input box in
the Designer Check.
For example, in line 13 it's report that "/E3E4-2 has displacement at START, value is 103.4
mm". In the picture below, we can see the SNOD is on the top of the column. However, the
beam in red is actually using NA as the positioning line. So use the Position > Align
Secondary Nodes of the Beams & Columns Application to realign the SNOD to the beam.
The next error reported is 2 SCTNs unconnected. These two SCTNs are actually hanging in
the air, this error can be ignored.
Then the program reports there are empty SNODS or SJOIs that are not connecting to
SCTNs. Use the Delete > Tidy Joints and Delete > Tidy Nodes function to remove those
SNODs and SJOIs
The last thing reported is there is an SNOD outside its owning SCTN. But this SNOD is
already deleted.
Now click the Check All button again. The checks fixed above are passed. Now another
error reports: 3 SNODs have a very near SNOD in their owning SCTNs, all of the
displacement are less than 1.
In this case, use Modify > Hierarchy > Include to move the SJOIs from one of the SNOD
into the nearing SNOD. Then select Tidy Nodes again to remove the empty SNODs.
Select Position picked in the Vertex Position drop-down menu. Click the Derive points
from graphic picks to pick the meshed points for this PANE.
The panels should be meshed according to the frames of the model. In this example, the
panel should be meshed into four parts.
When output the panels, the program will scan for the nearest node within the thickness of
the plate and use that node as the nodes for the plate.
If there are beams under the panel, the nodes of the meshed panels should be created at
the position of the SNODs of the beams connected. Then the nodes of the panel output can
be merged to the nodes of the SCTNs. Otherwise the nodes of the panels maybe output as
an orphan node.
So, when selecting the points of the panels, always use the position of the SNODs If
possible. In this example, four SNODs of the beams connecting are picked.
Here use type Element in the Positioning Control for picking SCTNs.
Pick the SCTN near the SNOD, the program will get the position of the SNODs and add to
the point list.
Note: If the user selects Projection to Panel in the Vertex Position drop-down menu, the
elevations of the vertexes are still on the panel, not the SNODs.
In the fourth panel, there is a penetration for staircase. An enclosed panel is drawn for
simplification.
Note: The elevations of the beams of PANEL 4 are higher than the others. And there are
two SNODs in the column that connecting to those beams. In this example, choose
the lower SNODs for PANEL 2 and PANEL 3, and choose the higher SNODs for
PANEL 4.
Similarly, mesh the panel on the second floor into three panels.
Note: Set the Panel Tolerance to 200 so that the program can scan the SNODs in the
columns. Because the elevations of the vertexes created in the Panel Meshing tool
are not the same as the SNODs.
Click the Output Load Case Setting button to add the load case just created to the Output
Load Case list.
Note: The Hierarchy can also set to SCTN here. Select the Set SCTN Type to scan the
hierarchy and set the SCTN and PANE purp to the correct section type.
8.2.4 Output
Input the prefix of the output file. Select Output to output and the Staad Pro STD file will be
created.
Now there is a reference model, the model displays two new braces.
Select Merge in the form to show the Merge Imported Model form.
Because there are new braces in the imported model, create a new SBFR under the "/
EQUIPRACK/MAIN" hierarchy, and set the purpose attribute of the SBFR to BRAC to
storage the updated brace.
Click the CE button to set the Origin Model and Update Model in the form, and click
Compare Model, the compare result is as shown:
In this example, the panels in the origin model are on the top of the beams. The nodes of the
panels are merged to the nodes of the beams where first outputted. But the beams are
output using the NA Pline, so the nodes of the panels imported will also be on the elevation
of the NA of the beams. So the nodes of the panels are not the same with the origin model
in PDMS. The panels will not be updated here.
Select the 1st, 2nd and 3rd lines and click Update Selected to update those three lines.
Then, check that the two new braces in the SBFR have created, and the specification of the
column /A-3 is updated.