How do we propose code changes?

[jike]

Many times, we talk amongst ourselves about a particular code issue but how often does our concerns ever get expressed to the proper committees that are responsible for the codes? I believe there is a real need to open up this line of communication.

If we have a specific suggestion or problem about a particular code issue, what procedure can we use or who do we need to contact to propose a change or express our opinion?

I know that there is, generally, a review period during which most code committees solict comments before finalizing the code. However, it is not until a particular jurisdiction adopts that code and the architects and engineers start using it, that we really dig into the details of it. Then the code complexities, inconsistencies and omissions become more apparent.

It would be great if we could put together a list of contacts for particular codes.

Some codes that come to mind:

IBC 2000
ASCE 7
ACI 318
ACI 530
AISC
NDS

Wouldn't it be great if we could automate this procedure and send on series of relevent posts to a particular committee or committee member by checking a box?

 

[JoeTank]

I am a member of a few codes and standard committees maintained by the American Petroleum Institute and the American Society of Mechanical Engineers. Both employ processes that are wide open and available to interested parties. Those that are truly interested come and participate. Those that are just interested don't. We are all better off when there are more people that are truly interested than those that are just interested.

As a practical matter, sending these posts as-is to a code or standard committee probably would not be of much value. The problem is not one of indifference on the committee's part, it's just the practical problem of time limititations in most cases.

We are all volunteeres who are truly interested in what we are doing and there are not always enough of us. Although our employers typically pick up all the expenses and the actual time at the meeting, the time necessary to keep up with committee activities is normally taken from our personal time... like weekends and nights.

What would be useful is to receive informative feedback from the document users that identify a problem and it's impact. Recommendations for revisions are most helpful and often heeded. Even the little stuff helps too. For example, if you note that there is an obvious editorial mistake in the code I recommend that you fire off an email to the organization indentifying the problem. It will be fixed.

It also helps if you become truly intereted and become a participant. Don't wait until it's published before getting involved.

Steve Braune
Tank Industry Consultants

http://www.tankindustry.com

 

[jike]

Steve:

I agree that it would be more useful to send info. on a code problem, its impact and a recommended solution.

For many of us, our employers will not pick up travel expenses or meeting time and so this prevents our involvement.

We certainly can and are willing to send off an email, but we need to know who and where to send it. Where can we get this info.?

The review periods for these codes are not always made known to the professional community. How can the notification of these review periods be more widely distributed to the professional community?