Discover millions of ebooks, audiobooks, and so much more with a free trial

Only $11.99/month after trial. Cancel anytime.

A Quick Guide to API 653 Certified Storage Tank Inspector Syllabus: Example Questions and Worked Answers
A Quick Guide to API 653 Certified Storage Tank Inspector Syllabus: Example Questions and Worked Answers
A Quick Guide to API 653 Certified Storage Tank Inspector Syllabus: Example Questions and Worked Answers
Ebook501 pages8 hours

A Quick Guide to API 653 Certified Storage Tank Inspector Syllabus: Example Questions and Worked Answers

Rating: 3.5 out of 5 stars

3.5/5

()

Read preview

About this ebook

The API Individual Certification Programs (ICP) are well established in the oil/gas/petroleum industries. API runs multiple examination sites around the world at 6-monthly intervals. The three main ICPs are: API 570: Certified pipework inspector; API 510: Certified pressure vessel inspector; API 653: Certified storage tank inspector.
  • Reviews one of API's three main ICPs: API 653: Certified storage tank inspector
  • Discusses key definitions and scope, inspection regimes and testing techniques relating to tank design, linings, welds, protection systems, repair and alteration
  • API Individual Certification Programs (ICP) are well established in the oil/gas/petroleum industries
LanguageEnglish
Release dateOct 25, 2011
ISBN9780857095275
A Quick Guide to API 653 Certified Storage Tank Inspector Syllabus: Example Questions and Worked Answers
Author

Clifford Matthews

Clifford Matthews CEng, FIMechE is Director of Matthews Engineering Training Limited, UK, which runs training courses in API 510/570/653, plant inspection, code design, pressure relief equipment and related subjects: over 4000 delegates have been trained in the past 10 years. He has worldwide experience in various industries and is the author of several books on topics relating to inspection. Matthews Training’s approach to teaching API subjects has achieved a first-time examination pass rate in the region of 90%.The company is an authorised global training provider to the American Society of Mechanical Engineers (ASME).

Related to A Quick Guide to API 653 Certified Storage Tank Inspector Syllabus

Related ebooks

Mechanical Engineering For You

View More

Related articles

Reviews for A Quick Guide to API 653 Certified Storage Tank Inspector Syllabus

Rating: 3.736842105263158 out of 5 stars
3.5/5

19 ratings1 review

What did you think?

Tap to rate

Review must be at least 10 words

  • Rating: 5 out of 5 stars
    5/5
    muy interesante , lo malo que no se puede bajar , para poder leer , estudiar con mas tiempo donde no hay intenet.

Book preview

A Quick Guide to API 653 Certified Storage Tank Inspector Syllabus - Clifford Matthews

are.

Chapter 1

Interpreting API and ASME Codes

It would help if things were different, but passing any API Inspector Certification Programme (ICP) examination is, unfortunately, all about interpreting codes. As with any other written form of words, codes are open to interpretation. To complicate the issue further, different forms of interpretation exist between code types; API and ASME are separate organizations so their codes are structured differently, and written in quite different styles.

1.1 Codes and the real world

Both API and ASME codes are meant to apply to the real world, but in significantly different ways. The difficulty comes when, in using these codes in the context of the API ICP examinations, it is necessary to distil both approaches down to a single style of ICP examination question (always of multiple choice, single-answer format).

1.2 ASME construction codes

ASME construction codes (only sections V and IX are included in the API 653 ICP body of knowledge) represent the art of the possible, rather than the ultimate in fitness-for-service (FFS) criteria or technical perfection. They share the common feature that they are written entirely from a new construction viewpoint and hence are relevant up to the point of handover or putting into use of a piece of equipment. Strictly, they are not written with in-service inspection or repair in mind. This linking with the restricted activity of new construction means that these codes can be prescriptive, sharp-edged and in most cases fairly definitive about the technical requirements that they set. It is difficult to agree that their content is not black and white, even if you do not agree with the technical requirements or acceptance criteria, etc. that they impose.

Do not make the mistake of confusing the definitive requirements of construction codes as being the formal arbiter of FFS. It is technically possible, in fact commonplace, to use an item safely that is outside code requirements as long as its integrity is demonstrated by a recognized FFS assessment method.

1.3 API inspection codes

API inspection codes (e.g. API 653) and their supporting recommended practice document (API RP 575: Guidelines and Methods for Inspection of Existing Atmospheric and Low Pressure Storage Tanks) are very different. Recommended practice (RP) documents are not formal codes and so do not share the prescriptive and ‘black and white’ approach of construction codes.

There are three reasons for this:

• They are based around accumulated expertise from a wide variety of tank applications and situations.

• The technical areas that they address (corrosion, equipment lifetimes, etc.) can be diverse and uncertain.

• They deal with technical opinion, as well as fact.

Taken together, these make for technical documents that are more of a technical way of looking at the world than a solution, unique or otherwise, to a technical problem. In such a situation you can expect opinion to predominate.

Like other trade associations and institutions, API (and ASME) operate using a structure of technical committees. It is committees that decide the scope of codes, call for content, review submissions and review the pros and cons of what should be included in their content. It follows therefore that the content and flavour of the finalized code documents are the product of committees. The output of committees is no secret – they produce fairly well-informed opinion based on an accumulation of experience, tempered, so as not to appear too opinionated or controversial, by having the technical edges taken off. Within these constraints there is no doubt that API codes do provide sound and fairly balanced technical opinion. Do not be surprised, however, if this opinion does not necessarily match your own.

1.3.1 Terminology

API and ASME documents use terminology that occasionally differs from that used in European and other codes. Non-destructive examination (NDE), for example, is normally referred to as non-destructive testing (NDT) in Europe and API work on the concept that an operative who performs NDE is known as the examiner rather than the term technician used in other countries. Most of the differences are not particularly significant in a technical sense – they just take a little getting used

Enjoying the preview?
Page 1 of 1