UBC 1997 and API 650 11th Ed.
UBC 1997 and API 650 11th Ed.
(OP)
I have come across this situation many times lately and I would like to hear your opinion. Most of the designers, when writing specs for steel tanks, use "generic" specs just becasue they are not familar with API 650 or AWWA D100-05 Standards. When specifying the seimic design requirements, all they mention is that it shall be in accordance with the UBC 1997.
As you all know, UBC specifies seismic zones (1, 2, 3 , 4 and 5) while API 650/AWWA D100-05 now specifies seimic use groups (I, II and III). I understand that API and AWWA incorporate by reference the seismic design criteria presented in ASCE 7. However, the criteria presented in ASCE 7 is quite different to that presented in UBC 1997. How are you meeting the requirements of both codes (UBC 1997 and API 650)? The current design code here in Puerto Rico is the UBC 1997. Should I continue designing tanks as per UBC 1997 or should I design them per Appendix E? Which do you think is more strict?
As you all know, UBC specifies seismic zones (1, 2, 3 , 4 and 5) while API 650/AWWA D100-05 now specifies seimic use groups (I, II and III). I understand that API and AWWA incorporate by reference the seismic design criteria presented in ASCE 7. However, the criteria presented in ASCE 7 is quite different to that presented in UBC 1997. How are you meeting the requirements of both codes (UBC 1997 and API 650)? The current design code here in Puerto Rico is the UBC 1997. Should I continue designing tanks as per UBC 1997 or should I design them per Appendix E? Which do you think is more strict?
Jorge L. Ramos, Jr., MSCE, PE
Alonso & Carus Iron Works, Inc. (www.alonsocarus.com)
Euro-American Steel Co., Inc. (www.euroamericansteel.com)





RE: UBC 1997 and API 650 11th Ed.
RE: UBC 1997 and API 650 11th Ed.
Yes, so often individuals that write the specs do not know that conflicts exists between stds. I believe this is simply because they do not know or care to read the stds/ref's. Chances are that you may not get a timely or adequate response from your client.
Short of getting a response from the client, find out which std has precedence and adhere.
My opinion only - me being a cautious individual, choosing the most technically sound choice (less risky) is preferred.
Good Luck!
pmover
RE: UBC 1997 and API 650 11th Ed.
RE: UBC 1997 and API 650 11th Ed.
Is there any correlation between seismic zones and seismic use groups? I know that there is a correlation table in AWWA D100-05 between occupancy catergories and SUGs.
Jorge L. Ramos, Jr., MSCE, PE
Alonso & Carus Iron Works, Inc. (www.alonsocarus.com)
Euro-American Steel Co., Inc. (www.euroamericansteel.com)
RE: UBC 1997 and API 650 11th Ed.
Most of the applications I've dealt with always required the "latest revision" of whatever I was working with. And in some codes, this is required, either by the code itself, or by a replace-this-page updating which effectively destroys your "old" code anytime you update. ASME B&PV is a good example of this.
It was recently pointed out to me in the Structural Forum that in fact most governmental building codes are not set up this way. A city or state will require a specific year of the UBC or IBC codes. That code in turns specifies a specific year of the ASCE 7 and other standards. ASCE 7 then specifies a specific year of AWWA or API standards. But this conflicts with the information included in the standards themselves. So using the latest standard may seem the thing to do, but you could just as easily be asked, "Why didn't you comply with this building code that required the 19xx Standard?" You also lose a couple of years in each reference, so the building code in 2008 will be the IBC from 2005, which requires ASCE 7 from 2002, which requires API from 1999, which references ASTM A36 from 1996, and so on down the line.
In actual practice, I haven't had any trouble with consultants or owners or plan reviewers questioning what version was used for design. It may help to note that API itself specifies when the new standard becomes effective, so anything that requires an older version is automatically contradicted by the standard itself.
RE: UBC 1997 and API 650 11th Ed.