Need a book? Engineering books recommendations...

Return to index: [Subject] [Thread] [Date] [Author]

RE: ASCE 7-05 Errors

[Subject Prev][Subject Next][Thread Prev][Thread Next]

With all due respect the justification for code
changes are frequently not clearly documented and the
documentation is often not availible to the users. All
too often I am frustrated in my ability to understand
the reason for a code provision due to the lack of

Code change proposals are often influenced by the
group dynamic of the committee and reflect political
compromises.  I have seen this up front.  The process
by which a committee drafts changes creates the
conditions which lead to mistakes. 

When the "Blue Book" was revised in 1988 an editorial
committee of 2 to 3 people went over the text to make
sure it was clear and reflected the intent of the

Given that the committee members are typically not
paid, the lack of proofing the documents has less to
do with the costs and more to do with where the
committee decided to focus its efforts.  If the
leadership of the Committee chair does not understand
the need for checking it won't happen.

Another tool that showed a potential to help
understand the logical flaws of standards was the work
done by Steven Fenves on expressing the AISC code in a
decision table format.  This work was done about 30
years ago.

******* ****** ******* ******** ******* ******* ******* ***
*   Read list FAQ at:
*   This email was sent to you via Structural Engineers 
*   Association of Southern California (SEAOSC) server. To 
*   subscribe (no fee) or UnSubscribe, please go to:
*   Questions to seaint-ad(--nospam--at) Remember, any email you 
*   send to the list is public domain and may be re-posted 
*   without your permission. Make sure you visit our web 
*   site at: 
******* ****** ****** ****** ******* ****** ****** ********