1、Recommended Practice forPipeline SCADA DisplaysAPI RECOMMENDED PRACTICE 1165FIRST EDITION, JANUARY 2007REAFFIRMED, JULY 2012Recommended Practice forPipeline SCADA DisplaysPipeline SegmentAPI RECOMMENDED PRACTICE 1165FIRST EDITION, JANUARY 2007REAFFIRMED, JULY 2012SPECIAL NOTESAPI publications necess
2、arily 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 expre
3、ss or implied, with 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, subcont
4、ractors, con-sultants, or other assignees represent that use of this publication would not infringe upon pri-vately owned rights.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;
5、 however, the Institute makes 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 authorities having jurisdiction with which this publi-catio
6、n may conflict.API publications are published to facilitate the broad availability of proven, sound engineer-ing and operating practices. These publications are not intended to obviate the need for applying sound engineering judgment regarding when and where these publications should be utilized. Th
7、e 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 conformance with the marking requirements of an API standard is solely responsible for complying with all the applicable re
8、quirements of that standard. API does not represent, warrant, or guarantee that such prod-ucts do in fact conform to the applicable API standard.All rights reserved. No part of this work may be reproduced, stored in a retrieval system, or transmitted by any means, electronic, mechanical, photocopyin
9、g, 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 Petroleum InstituteFOREWORDNothing contained in any API publication is to be construed as granting any
10、right, by impli-cation 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 anyone against liability for infringement of letters patent.The colors used in this pub
11、lication are provided only as examples and are not intended to be exact.This document was produced under API standardization procedures that ensure appropriate notification and participation in the developmental process and is designated as an API stan-dard. Questions concerning the interpretation o
12、f the content of this publication or comments and questions concerning 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
13、 or translate all or any part of the material published herein should 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 publ
14、ication can be ascertained from the API Standards Department, telephone (202) 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
15、 and Publications Department, API, 1220 L Street, NW, Washington, D.C. 20005, standardsapi.org.iiiCONTENTSPage1 SCOPE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11.1 Purpose. . . . . . . . . . . . . . . . . . . . . .
16、 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11.2 Scope Limitations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12 REFERENCES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
17、. . . . . . . . . . . .13 DEFINITIONS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .24 HUMAN FACTORS ENGINEERING CONSIDERATIONS IN DISPLAY DESIGN 34.1 Short-term Memory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
18、 . . . . . . . . . . . . . . . . .34.2 Signal-to-Noise Ratio . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .44.3 Eye Scan Pattern . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .44.4 Consistency . . .
19、. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .54.5 Coding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .55 DISPLAY HARDWARE . . . . . . . . . . . . . . . . . . . . . . . .
20、. . . . . . . . . . . . . . . . . . . . . . . . .55.1 General Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .55.2 Display Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .65.3 Dis
21、play Response. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .65.4 Controller Input Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .66 DISPLAY LAYOUT AND ORGANIZATION. . . . . . . . . . . . . . . . .
22、 . . . . . . . . . . . . . . .76.1 General Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .76.2 Display Hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .76.3 Window Management Issues
23、. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .87 DISPLAY NAVIGATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .97.1 General Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
24、. . . . . . . . . .97.2 Navigation Techniques . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .97.3 Zoom, Pan, and Overlays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .108 OBJECT CHARACTERISTICS. . . . . . . . . . . .
25、 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .108.1 General Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .108.2 Color. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
26、 . . . . .108.3 Symbols and Shapes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .118.4 Animation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .128.5 Text. . . . . . . . . . . . . . . . . .
27、. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .129 OBJECT DYNAMICS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .139.1 General Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
28、 . . . . . . . . . . .139.2 Data Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .139.3 Data Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1410 CONTROL AND SELECTION T
29、ECHNIQUES. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1510.1 Object Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1510.2 Command Execution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
30、. . . .1610.3 Error Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16vPage11 ADMINISTRATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1611.1 Consistency within a Company . . . . . .
31、. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1611.2 Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1611.3 Consistency between Control Centers and Remote Locations . . . . . . . . . . . . . .1611.4 MOC (Management o
32、f Change). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1712 SAMPLE DISPLAYS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17APPENDIX A EXAMPLES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
33、. . . . . . . . . . 19APPENDIX A1 EXAMPLE SYMBOL DYNAMICS. . . . . . . . . . . . . . . . . . . . . 21A1-1 Pumping Units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22A1-2 Non SCADA Controllabe Valves . . . . . . . . . . . . . . . . . . . . . . . . . .
34、. . . . . 23A1-3 SCADA Controllable Valves. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24A1-4 4 Way Valves. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25A1-5 3 Way Valves. . . . . . . . . . . . . . . . . . . . . . . . . . . .
35、. . . . . . . . . . . . . . . . . . . 26A1-6 Tank Mixers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27APPENDIX A2 DISCRETE STATE POINTS. . . . . . . . . . . . . . . . . . . . . . . . . . . 29APPENDIX A3 NUMERIC POINTS . . . . . . . . . . . . . . .
36、 . . . . . . . . . . . . . . . . . . . 31APPENDIX A4 SAMPLE STATION DISPLAY. . . . . . . . . . . . . . . . . . . . . . . . . .33APPENDIX A5 SAMPLE SUMMARY DISPLAYS. . . . . . . . . . . . . . . . . . . . . . 35A5-1 Alarm Summary Displays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
37、 . . . . 36A5-2 Event Summary Displays. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37A5-3 Communications Summary Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38A5-4 Database Summary Displays. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
38、. . . 39APPENDIX A6 DETAILED POINT DISPLAYS . . . . . . . . . . . . . . . . . . . . . . . . . .41APPENDIX A7 TREND DISPLAYS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43APPENDIX A8 SPECIAL APPLICATION DISPLAYS. . . . . . . . . . . . . . . . . . . . 451Recommended Practice
39、for Pipeline SCADA Displays1 Scope1.1 PURPOSEThis Recommended Practice (RP) focuses on the design and implementation of displays used for the display, monitoring, and control of information on pipeline Supervisory Control and Data Acquisition Systems (SCADA). The primary purpose is to doc-ument indu
40、stry practices that provide guidance to a pipeline company or operator who want to select a new SCADA system, or update or expand an existing SCADA system.This RP assists pipeline companies and SCADA system developers in identifying items that are considered best practices when developing human mach
41、ine interfaces (HMI). Design elements that are discussed include, but are not limited to, hardware, navi-gation, colors, fonts, symbols, data entry, and control / selection techniques. 1.2 SCOPE LIMITATIONSThis RP was created by an API Cybernetics Subcommittee task force, based on industry practices
42、 used on liquid pipeline SCADA systems. Most participants operate crude, product, chemical, and natural gas pipeline systems.It is recognized that each pipeline company has unique operating philosophies and SCADA systems; therefore, not all elements of this recommended practice may be applicable. Fo
43、r example: Some pipeline control centers are a combination of several different SCADA systems. Some of these SCADA systems may not have the developer tools necessary to implement the recommended practices. Some operators may have existing display techniques that bridge over into unique operating phi
44、losophies. This RP is not all-inclusive. It is intended to cover best practices and provide examples for display techniques only, not dictate operational control philosophy or overall SCADA system functionality. The reader should have a good working knowledge of pipeline operations and display techn
45、iques, and may have to refer to other publications for background or additional information.This RP compliments but does not replace other procedures and effective display techniques or industry standards that are used for software development and implementation. Regulatory and individual company st
46、andards are not addressed in this publica-tion.2 References1. ASM Consortium GuidelinesEffective Operator Display Design. Version 2.01, July 28, 2000.2. Galitz, W. O. (1993). User-interface screen design. New York, NY: John Wiley it hurts because it makes it more difficult to find the important item
47、s.Displays should not have elements without purpose. Display design principles indicate that as much useful information as possi-ble should be put on each display, but useless items should not be included.4.3 EYE SCAN PATTERNThe locations where objects are placed on a display, as well as their size,
48、 determine their relative importance to the viewer. Larger objects and objects placed on the top and the center of the display tend to have more importance than others. Studies have shown that the initial eye scan pattern of the monitor tends to concentrate on certain areas of the display (see Figur
49、e 1). The information that is important to the controller and needs to be picked up on the initial scan of the display should be located in the upper left and lower right of the display. This does not mean that data placed elsewhere on the display will be missed by the controller. After the initial eye scan, the controller will look at the entire display. Figure 1Initial Eye Scan Pattern on a Displayi Upper Right Quadrant Lower Right Quadrant Upper Left Quadrant Lower Left Quadrant Eye Starts Here Eye Finishes Here Monitor Initial Eye Scan Pattern on a Display RECOMMENDED PRACTICE
