1、Developing a PipelineSupervisory Control CenterAPI RECOMMENDED PRACTICE 1113FIRST EDITION,AUGUST 2007REAFFIRMED,JUNE 2012Developing a PipelineSupervisory Control CenterPipeline SegmentAPI RECOMMENDED PRACTICE 1113FIRST EDITION,AUGUST 2007REAFFIRMED,JUNE 2012Special NotesAPI publications necessarily
2、address problems of a general nature.With respect to particular circumstances,local,state,and federal laws and regulations should be reviewed.Neither API nor any of APIs employees,subcontractors,consultants,committees,or other assignees make any warranty or representation,either express or implied,w
3、ith respect to the accuracy,completeness,or usefulness of the information contained herein,or assume any liability or responsibility for any use,or the results of such use,of any information or process disclosed in this publication.Neither API nor any of APIs employees,subcontractors,consultants,or
4、other assignees represent that use of this publication would not infringe upon privately owned rights.Classified areas may vary depending on the location,conditions,equipment,and substances involved in any given situation.Users of this recommended practice should consult with the appropriate authori
5、ties having jurisdiction.Users of this recommended practice should not rely exclusively on the information contained in this document.Sound buisiness,scientific,engineering,and safety judgment should be used in employing the information contained herein.API publications may be used by anyone desirin
6、g 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 Institute makes no representation,warranty,or guarantee in connection with this publication and hereby expressly disclaims any liability or responsibility for loss
7、or damage resulting from its use or for the violation of any authorities having jurisdiction with which this publication may conflict.API publications are published to facilitate the broad availability of proven,sound engineering and operating practices.These publications are not intended to obviate
8、 the need for applying sound engineering judgment regarding when and where these publications should be utilized.The formulation and publication of API publications is not intended in any way to inhibit anyone from using any other practices.Any manufacturer marking equipment or materials in conforma
9、nce with the marking requirements of an API standard is solely responsible for complying with all the applicable requirements of that standard.API does not represent,warrant,or guarantee that such products do in fact conform to the applicable API standard.All rights reserved.No part of this work may
10、 be reproduced,stored in a retrieval system,or transmitted by any means,electronic,mechanical,photocopying,recording,or otherwise,without prior written permission from the publisher.Contact the Publisher,API Publishing Services,1220 L Street,N.W.,Washington,D.C.20005.Copyright 2007 American Petroleu
11、m InstituteForewordNothing 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 should anything contained in the publication be construed as insuring
12、anyone against liability for infringement of letters patent.Shall:As used in a standard,“shall”denotes a minimum requirement in order to conform to the specification.Should:As used in a standard,“should”denotes a recommendation or that which is advised but not required in order to conform to the spe
13、cification.This document was produced under API standardization procedures that ensure appropriate notification and participation in the developmental process and is designated as an API standard.Questions concerning the interpretation of the content of this publication or comments and questions con
14、cerning the procedures under which this publication was developed should be directed in writing to the Director of Standards,American Petroleum 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
15、also be addressed to the director.Generally,API standards are reviewed and revised,reaffirmed,or withdrawn at least every five years.A one-time extension of up to two years may be added to this review cycle.Status of the publication can be ascertained from the API Standards Department,telephone(202)
16、682-8000.A catalog of API publications and materials is published annually and updated quarterly by API,1220 L Street,N.W.,Washington,D.C.20005.Suggested revisions are invited and should be submitted to the Standards Department,API,1220 L Street,NW,Washington,D.C.20005,standardsapi.org.iiiContentsPage1General.11.1 Scope.11.2 Purpose.11.3 How to Use This Document.12Applicable References.23Definition of Terms.24Developing System Architecture.35Developing System Reliability.46Developing Disaster Re
