The API LRFD JOIN command requests that a nominal load joint check be performed to API LRFD design recommendations (Ref. 3).
The joints may consist of TUBE elements and/or other beam types that have been assigned tubular sections in the structural analysis.
Joints for post-processing are selected using the JOINt command in BEAMST which specifies the node numbers at joint positions. All joints are assumed ‘simple’. Elements may be excluded from the check using the SECOndary command. Yield stresses must be provided for both the chord and brace elements at a joint.
Joints are automatically classed as K, T, or Y depending on the joint geometry as follows:
The chord member is the member with the greatest outside diameter.
If two or more potential chord members have equal diameters BEAMST will consider the two with the largest wall thicknesses and for each loadcase selected will check the one most heavily stressed against all brace members.
In the case of more than two potential chord members with equal diameters and wall thicknesses, the first two encountered as shown in the Cross Check Report will be considered.
If the CHORd command is used to specify a chord member, this alone will be considered. If two chords are specified, the most heavily stressed chord will be checked against all brace members for each loadcase selected.
All members not selected as chord members are treated as brace members (unless defined as secondary), with each brace-chord pair being checked.
BEAMST selects ‘simple’ joint (brace-chord pair) ‘types’ as follows:
Brace members ‘perpendicular’ to the chord members (smaller included angle greater than or equal to 80 degrees) as T joints.
Single non-‘perpendicular’ braces are classified as K joints.
Cross or Double(DT) joints must be user specified.
In the case of user defined K and X joints, no search is performed for a second brace member in the same brace-chord plane as the first brace.
Brace members specified on joint TYPE commands are automatically selected as braces in the above brace-chord member selection process.
No conflict between CHORd command specified members and brace members specified on joint TYPE commands is allowed.
BEAMST will only check selected joints in which two or more incident members are tubular and of circular section. All other selected joints are automatically bypassed.
The user may override these classifications using the TYPE and CHOR commands. Interpolated joint classifications may be defined using the TYPE command. For K joints a gap dimension appropriate to the joint may be specified in the TYPE command. A default gap dimension may be specified using the GAPD command.
If load transfer across chords is to be checked at selected joints, additional chord data must be supplied using the CHOR EFFE command.
The API LRFD standard utilizes limit state checks with resistance coefficients to achieve the desired level of safety. In keeping with this principle, applied loads must be multiplied by appropriate factors, as defined in the code of practice (Section C, Loads), to develop the design load case combinations necessary for processing. Where non-linear pile analysis is undertaken the design loads must be applied to the pile model to account for the increased non-linearity this introduces. In situations where a non-linear pile analysis has not been carried out, the design loads may be produced using the COMB or CMBV commands utilizing the required load factors. For abnormal loading conditions the ABNO command may be used to set the resistance coefficients to unity.
Two summary reports are available.
Summary report 1 details the load case producing the highest unity check for each chord/brace pair at a joint.
Summary report 3 contains the highest unity check for each selected loadcase for each chord/brace pair at a joint.
BEAMST commands applicable to the API LRFD nominal load command are given in Table 5.11: API LRFD JOIN Commands below and are described in detail in BEAMST Command Reference. An example data file is given in Example 5.8: Example API LRFD JOIN data file.
Table 5.11: API LRFD JOIN Commands
| Command | Description | Usage | Note |
|---|---|---|---|
|
API joint check header command |
C | ||
|
Units of length and force Yield stress |
|
1 | |
|
Joint numbers to be reported Joint type and brace element definition Chord elements at a joint and associated parameters Secondary members to be ignored in checks |
|
| |
|
Defines design section properties Define default gap dimension Section profiles for use in design Tubular member’s end stub dimensions | |||
|
Abnormal loadcases Basic loadcases to be reported Define a combined loadcase for processing Define a combined loadcase for processing Select/redefine a combined/basic loadcase title Basic loadcases from response spectrum analysis Renumber a ‘basic loadcase’ |
|
| |
|
Reports to be printed Text or comment command Redefine global title | |||
|
Terminates command data block |
C |
Usage
C Compulsory command, but see notes below where applicable.
Notes
SYSTEM DATA AREA 100000
TEXT BEAMST USER MANUAL EXAMPLE STRUCTURE T0847
JOB POST
PROJECT MANU
COMPONENT PILE JACA
OPTION GOON
UNIT KN M
END
API LRFD ED1 JOIN
*
* Investigate all joints in the model except where
* only one element is connected
*
JOINT ALL
NOT JOINTS 1315 1355 5110 5150
*
* Ignore dummy elements
*
SECONDARY ELEMENTS 801 802
*
* Change tubular dimensions for one element
*
DESI TUB 1.0 0.05 ELEM 131
*
* Examine two wave cases
*
SELE 10 Extreme Wave 1 + Dead Loads + Live Loads
COMB 10 1.35 1 1.1 3 1.1 4
SELE 11 Extreme Wave 2 + Dead Loads + Live Loads
COMB 11 1.35 2 1.1 3 1.1 4
*
* Yield Value Constant for all elements
*
YIELD 3.5E05 ELEM ALL
*
* Specify the chord elements for one of the joints
*
CHORD 1130 122 123
*
* Request cross chord check for one X joint
*
TYPE.OF.JOINT X
CHORD EFFE
*
* Set some joints as being Y
*
TYPE.OF.JOINT 1130 Y 102
TYPE.OF.JOINT 1130 Y 103
*
* Ask explicitly for all reports
*
PRIN XCHK UNCK SUNI N MM SUM3 SUM1
END
STOP