Continue to Site

Eng-Tips is the largest engineering community on the Internet

Intelligent Work Forums for Engineering Professionals

  • Congratulations KootK on being selected by the Eng-Tips community for having the most helpful posts in the forums last week. Way to Go!

is that useful to read the code ? 1

Status
Not open for further replies.

engahmedbahgat

Mechanical
Feb 20, 2014
40
I want to know , is that useful to read the code or standard as ASME B31.3 or ASME B31.8 from cover to cover as I read a book ?
my idea it will not be useful, but I still need to discover the code, knowing what chapters and sections talking about.
I know there are a courses introduced for that job , but I talking about useful personal effort can be made, in case of no way to these courses for some reason.

thank you in advance
 
Replies continue below

Recommended for you

I think it's very useful.
Then you know what chapter you are looking for when you need the code.
 
No, it is not a good idea - with the proviso below.
It depends totally on what your role is ?

If you are an Engineer then understanding design calculations (for example)is very important.
If you are an Inspector then there is absolutely no reason for you to look at the theory behind design calculations.

I could go on and on but IMHO the best way forward is this.
Focus on the parts of the codes or standards that are important to you in your role.
Good luck,
Regards,
DD
 
I find reading the code from front to back to be impossible. Every time I start, I get to a "this must be done in accordance with Section ___" so I pop over to that section and it has a requirement to go to some other section and I pop over there. I tried to read B31.8 that way by putting post-its at each exit point and numbering them. I got to the end of the 8th redirect without being sent to a 9th, so I went back to #7 and the next line sent me somewhere else. I gave up.

In my classes I tell people to go to the code with a specific question and rigorously follow the re-directs as you come to them, and chase the chain to the end. Then start over with the next question. 10-12 questions later you have read the whole damn thing and more importantly have some context to make all those words real for you.

[bold]David Simpson, PE[/bold]
MuleShoe Engineering

In questions of science, the authority of a thousand is not worth the humble reasoning of a single individual. Galileo Galilei, Italian Physicist
 
I agree with ZDAS04.

It is probably worthwhile reading the introduction, scope and general sections to understand a bit of the history, what the code covers and what it doesn't and how it approaches certain issues.

After that you really need some specific example or usage and then it's worth reading it carefully, looking up exactly what the symbols mean and what the definitions are (they can vary a LOT between codes).

Have a good look at the index and maybe read the chapters saying something like "DESIGN", e.g chapter IV of B 31.8 - the first 5 or 6 pages give you quite a good insight into the whole idea before it starts to get too specific or INSTALATION

Remember - More details = better answers
Also: If you get a response it's polite to respond to it.
 
I find it useful to read a new code just to see what's between the covers. Then, once the general layout is understood, it is easier to find an answer to a specific question. However, one does not read a code as if it were and epic novel. As mentioned, it is easiest to learn how to navigate a code by trying to find answers to specific questions. Then as mentioned by several posts, it a game of follow the bouncing ball, going from one provision to another in succession as directed by the code. In some cases, the code will branch off in two directions and one must follow each thread to the bitter end to see if it applies to your particular circumstance. In some case, after an hour of following the thread, you discover it doesn't apply and one must follow the other branch to see where it leads you.

Best regards - Al
 
@Zdas04,
When I joined piping 20 years back in a company, my seniors told me I have to read ASME B31.3. I started it with enthusiasm and when I got into this labyrinth of ...as per para... I gave up. I could not simply do it. That is why, I still have not read it cover to cover, but know my way around how to find what I need there.
.
@Littleinch,
You are right, we (piping engineers) should read at least chapter DESIGN of ASME B31.3.

Else as noted above, it is not novel, you simply CANNOT read it cover to cover.

Enjoy piping.
 
Best compromise for me has been to skim Codes cover to cover. That way, when I get a problem that requires reference to the Code, I remember approximately where to start looking.
 
I would like to add that it is useful to understand the nature the ASME codes are organised. There's a clever thinking put into that. Once you get that basic idea, you'll be able understand other B31 codes more quickly, or at least know how to navigate through them when you start exploring a new B31 code like a newbie.
 
While I have probably read the Code from cover to cover, it was done as needed for the work involved at any one time. In short it was done through many years. After a time one simply knows where to look for the information needed, especially as major changes are made to the Code.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor