几何尺寸与公差论坛

 找回密码
 注册
查看: 619|回复: 0

asd or lrfd for connection design reactions

[复制链接]
发表于 2009-9-7 13:32:38 | 显示全部楼层 |阅读模式
asd or lrfd for connection design reactions
do you use asd or lrfd when specifying the connection reactions on structural plans to be used by the fabricator for connection design?  i realize that they should be able to design by both methods.  i have designed the structure using lrfd.  is it acceptable to mix design procedures (lrfd for member sizing – asd for connection design)?   
i would not mix up the methods. essentially the two methods typically yield about the same connection designs and braced beam selections. what is your live to dead load ratio?? the 13ed aisc asd/lrfd manual uses an l/d=3 which corresponds to lrfd/1.50 = asd value.  
give them the service loads and let them do the factoring.  then they're free to use whichever method they want.
if you "heard" it on the internet, it's guilty until proven innocent. - dcs
i agree with swearingen, service loads are the best way to go.
i disagree 100% with swearingen.  are you going to give them reactions for every load case (dead, live, wind in one direction, wind in the other direction, component and cladding wind, same for seismic, etc) and expect them to figure out which load combination produces the worst result?  good luck in getting the "right" answer.
the aisc code of standard practice says the engineer of record is to provide data pertaining to loads (which i suppose would make swearingen's proposal "acceptable") and which methodology (asd or lrfd) to use.  if you've designed the building with lrfd, i can't think of any reason not to use lrfd for the connection design forces.
to answer the original questions:
we use whichever one we used to design the building.
and
it could very well be acceptable, but i would think it best to use the same method for both.
您需要登录后才可以回帖 登录 | 注册

本版积分规则

QQ|Archiver|小黑屋|几何尺寸与公差论坛

GMT+8, 2025-1-11 06:43 , Processed in 0.036157 second(s), 20 queries .

Powered by Discuz! X3.4 Licensed

© 2001-2023 Discuz! Team.

快速回复 返回顶部 返回列表