| Date | September/October 2000 |
| Volume | 6 |
| Issue | 5 |
| Return to Journal Index | |
September/October 2000 Inspectioneering Journal Article Index
-
September/October 2000 Inspectioneering JournalBy John Reynolds at Intertek
This article continues to outline the 101 essential elements that need to be in place, and functioning well, to effectively and efficiently, preserve and protect the reliability and integrity of pressure equipment (vessels, exchangers, furnaces, boilers, piping, tanks, relief systems) in the refining and petrochemical industry.
-
September/October 2000 Inspectioneering JournalBy Russel T. Mack at National Association of Inspection Companies (NAIC)
In the petrochemical industry, we have noticed that many separate organizations are attempting to improve the quality of engineering and inspection. For example, many readers are familiar with the efforts of ASME (Post-Construction Code Requirements for Qualification & Certification of NDE Personnel), ASNT (ACCP NDT Central Certification Program), AWS/TWI (CSWIP NDT certification program), API (initiative for certification of NDT UT shear-wave weld inspectors), and NACE (Corrosion Engineering Personnel Qualification & Certification).
-
September/October 2000 Inspectioneering JournalBy T.C. Ridgeway & Staff at TCRI
In part 1 of this article we covered the importance of quality assurance of UT data, that is, understanding for each particular application, the accuracy required of the UT data, and new ways/graphical program to analyze and show the interrelationships of data by location for trending. Part 1 article areas then included: -UT Data Reporting and Evaluation -Imaging UT Data Evaluating the Quality of Static UT Data -Visual Trending of UT data -Mathematical Trending of UT Data Now, in Part 2, we will cover data quality issue statistics and possible sources of poor quality UT data.
-
September/October 2000 Inspectioneering JournalBy Greg Alvarado at Inspectioneering Journal
In part 1 of this series the importance of keeping the RBI process as simple as possible was stressed. Software, consequence and likelihood issues were covered. Consequences were handled directly while likelihood issues were covered in discussion on damage modules and qualitative versus quantitative sections.
