Api standar 662

Solo disponible en BuenasTareas
  • Páginas : 21 (5141 palabras )
  • Descarga(s) : 0
  • Publicado : 13 de marzo de 2012
Leer documento completo
Vista previa del texto
~

A P I STD*bb2 95

0 7 3 2 2 9 0 O550836 577

Plate Heat Exchangers For General Refinery Services

API STANDARD 662 FIRST EDITION, DECEMBER 1995

American Petroleum Institute

COPYRIGHT American Petroleum Institute Licensed by Information Handling Services

~

~

A P I STD*bb2 95

m 0732290 0550837 403 m

Plate Heat Exchangers For General Refinery ServicesManufacturing, Distribution and Marketing Department

API STANDARD 662 FIRST EDITION, DECEMBER 1995

American Petroleum Institute

COPYRIGHT American Petroleum Institute Licensed by Information Handling Services

A P I STDxbb2 95

= 0732290 0550838
SPECIAL NOTES

34T

API publications necessarily address problems of a general nature. With respect to particular circumstances, local, state, andfederal 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 federal laws. Information concerning safety and health risks and proper precautionswith respect to particular 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 product covered by letters patent. Neither shouldanything contained in the publication be construed 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 anoperative API standard or, where an extension has been granted, upon republication. Status of the publication can be ascertained from the API Authoring Department [telephone (202) 682-8000]. A catalog of API publications and materials is published annually and updated quarterly by API, 1220L Street, N.W., Washington, D.C. 20005. This document was produced under API standardizationprocedures thatensure appropriate notification and participation in the developmental process and is designated as an API standard. Questions concerning the interpretation of the content of this standard or comments and questions Concerning the procedures under which this standard was developed should be directed in writing to the director of the Manufacturing, Distribution, and Marketing Department, AmericanPetroleum Institute, 1220 L Street, N.W., Washington, D.C. 20005. Requests for permission to reproduce or translate all or any part of the material published herein should also be addressed to the director. API publications may be used by anyone desiring to do so. Every effort has been made by the Institute to assure the accuracy and reliability of the data contained in them; however, the Institutemakes no representation, warranty, or guarantee in connection with this publication and hereby expressly disclaims any liability or responsibility for loss or damage resulting from its use or for the violation of any federal, state, or municipal regulation with which this publication may conflict. API standards are published to facilitate the broad availability of proven, sound engineering andoperating practices. These standards are not intended to obviate the need for applying sound engineering judgment regarding when and where these standards should be utilized. The formulation and publication of API standards is not intended in any way to inhibit anyone from using any other practices. Any manufacturer marking equipment or materials in conformance with the marking requirements of an API...
tracking img