1 / 54
文档名称:

Api 570-Piping Inspection Code.pdf

格式:pdf   页数:54
下载后只包含 1 个 PDF 格式的文档,没有任何的图纸或源代码,查看文件列表

如果您已付费下载过本站文档,您可以点这里二次下载

Api 570-Piping Inspection Code.pdf

上传人:bolee65 2014/7/6 文件大小:0 KB

下载得到文件列表

Api 570-Piping Inspection Code.pdf

文档介绍

文档介绍:Piping Inspection Code
Inspection, Repair, Alteration, and Rerating
of In-service Piping Systems
API 570
SECOND EDITION, OCTOBER 1998
ADDENDUM 1, FEBRUARY 2000
ADDENDUM 2, DECEMBER 2001
ADDENDUM 3, AUGUST 2003
Piping Inspection Code
Inspection, Repair, Alteration, and Rerating
of In-service Piping Systems
Downstream Segment
API 570
SECOND EDITION, OCTOBER 1998
ADDENDUM 1, FEBRUARY 2000
ADDENDUM 2, DECEMBER 2001
ADDENDUM 3, AUGUST 2003
SPECIAL NOTES
API publications necessarily address problems of a general nature. With respect to partic-
ular circumstances, local, state, and federal laws and regulations should be reviewed.
API is not undertaking to meet the duties of employers, manufacturers, or suppliers to
warn and properly train and equip their employees, and others exposed, concerning health
and safety risks and precautions, nor undertaking their obligations under local, state, or fed-
eral laws.
Information concerning safety and health risks and proper precautions with respect to par-
ticular materials and conditions should be obtained from the employer, the manufacturer or
supplier of that material, or the material safety data sheet.
Nothing contained in any API publication is to be construed as granting any right, by
implication or otherwise, for the manufacture, sale, or use of any method, apparatus, or prod-
uct covered by letters patent. Neither should anything contained in the publication be con-
strued as insuring anyone against liability for infringement of letters patent.
Generally, API standards are reviewed and revised, reaffirmed, or withdrawn at least every
five years. Sometimes a one-time extension of up to two years will be added to this review
cycle. This publication will no longer be in effect five years after its publication date as an
operative API standard or, where an extension has been granted, upon republication. Status
of the publication can be ascertained from the API Standards Departm