几何尺寸与公差论坛

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

-bracing and the seismic overstrength factor

[复制链接]
发表于 2009-9-16 23:41:12 | 显示全部楼层 |阅读模式
x-bracing and the seismic overstrength factor
i used to work for a metal building company that used an omega equal to 1 for the x-bracing in sesismic categories a through c.  now, the company i work for uses omega equal to 3 for all applications of x-bracing.  which is correct?  
check out our whitepaper library.
using 3 sure makes life, and spread sheets, simple. sometimes it's harder to be correct than safe.
old ca se
omega = 3, just don't forget to design your connections by multiplying the forces by cd = 3.  while the   
isn't cd a deflection amplification factor? what implications will it have on a connection design strength?
the concept behind seismic detailing is to pick a fuse member and then make sure that all other members around it are stronger than the fuse. this way the designated yielding   
sorry....let me try again...
you should really just be using the coefficients in the  asce 7-05 ch 12.  but lets say you don't feel like it ...
i am assuming when you designed the structure, you used an r = 3.  if that is the case, then you should be using an omega = 3 (to be conservative) for connections.  you could probably use omega = 2 and no one would complain.  i do not recommend using an omega = 1 unless....
if you designed the structure using an r = 1 and assumed the whole thing to remain elastic, then you could use an omega = 1.

let's all move to florida where all one needs to worry about is wind!
it sounds like the company you are working for now is classifying their buildings as "steel systems not specifically designed for seismic resistance"
r=3
omega=3
be careful b/c this is allowed in seimic design categories greater than c.
in essence, this is equivalent to penpal's last post.  you've divided your seismic forces by 3 (r=3) then amplified your seismic forces by 3 (omega=3).
you're taking the full seismic load.
in connections, your designing your brace to yield (yield not fail) with your connection being strong enough, and in some cases, flexible enough, to withstand the force which causes the brace to buckle and/or elongate.  tihs is the "fuse" slickdeals is talking about
chipb - didn't you mean:  "be careful b/c this is notfff"> allowed in seisfff">mic design categories greater than c.
??

i realize that this question is a month old, but i think there needs some clarification. the question first posed asked about designing for design category c and for r=3 which refers to table 12.2-1 from asce 7-05, sfrs-"h"(steel systems not specifically detailed for seismic resistance ...) note, this is in chapter 12 "building structure systems" and not chapter 15, "... requirements for non-building structures". however, there is a reference back to chapter 12 in 15.4.1a  to allow you to select a system from either table but specifically refers you to the table in 15 for the appropriate r, cd, and omega values. since there is no "h" in the table from chapter 15 it does leave it open to interpretation if "h" is allowed for a non-building structure, say an open structure supporting process equipment. it does give values for pipe racks and would not allow you to use a higher r value than 1.0 without utilizing asce 341-05.
anyway, that's another topic.  in many of the responses to the question, it was stated that you needed to design the connections using omega=3, or essentially using r=1. while this may be prudent, it is not required by asce 7-05, aisc 360-05 (re  
jae,
sorry missed your post previously.
yes,fff"> that is what i meant!  see?  you're keeping me straight again!
chip
please do the same for me ok?

d9stuct:
what about where ibc 06 (section 1605.1) refers you to section 12.10.2.1 of asce 7 and it tells you that collector elements, splices, and their connections need to resist the load combinations with omega?
您需要登录后才可以回帖 登录 | 注册

本版积分规则

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

GMT+8, 2024-5-6 21:36 , Processed in 0.036473 second(s), 19 queries .

Powered by Discuz! X3.4 Licensed

© 2001-2023 Discuz! Team.

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