API Recommended Practice 1165 is the pipeline industry's guidance for designing the SCADA displays that controllers use to run hazardous liquid and gas transmission pipelines. It exists because a controller's ability to see and interpret a developing problem depends heavily on how information is presented on screen. This guide explains what API RP 1165 covers and where it fits in pipeline operations.
API RP 1165 in one line: API RP 1165 is a recommended practice titled Recommended Practice for Pipeline SCADA Displays. It provides human-factors guidance for designing consistent, legible, and unambiguous control-room displays so pipeline controllers can quickly detect abnormal conditions, understand system state, and respond correctly. It addresses layout, color, symbology, navigation, alarms, and display hierarchy rather than the underlying SCADA hardware.
API RP 1165 focuses squarely on the human-machine interface for pipeline SCADA: the graphics a controller stares at for a twelve-hour shift. It sets out principles for a consistent display hierarchy, from an overview of the whole pipeline down to detailed schematics of individual stations, so a controller can navigate predictably and never lose situational awareness.
The practice gives concrete guidance on the elements that make displays reliable: restrained and meaningful use of color (reserving high-saturation colors like red for genuine alarms), consistent symbology for valves, pumps, and tanks, legible text sizing, uncluttered layouts, and clear indication of data quality when a value is stale or unavailable. The goal is that the display never misleads the controller about the real state of the line.
Investigations of pipeline releases repeatedly found that controllers had the data they needed but could not interpret it in time because displays were cluttered, inconsistent, or used color and alarms poorly. Poor display design turns a subtle leak signature into noise the controller cannot distinguish from normal operation.
API RP 1165 codifies the human-factors lessons from those events into design rules. It is closely tied to control room management expectations: US pipeline operators must have a Control Room Management plan under PHMSA regulation 49 CFR 192.631 and 195.446, and well-designed displays following RP 1165 support the fatigue, alarm-management, and situational-awareness elements of that plan.
RP 1165 applies specifically to transmission pipeline control rooms rather than to a single field facility, and it pairs with API RP 1167 (pipeline SCADA alarm management) and API RP 1168 (control room management). Together these form the pipeline industry's human-factors triad: displays, alarms, and the operating discipline around them.
For operators, RP 1165 is the reference an integrator uses when building or auditing controller graphics. It does not dictate a vendor or protocol; it dictates that whatever platform draws the picture must draw a clear, consistent, honest one. That is why display standardization projects are common whenever pipelines merge systems or migrate to a new SCADA platform.
No. API RP 1165 governs how SCADA displays present information to pipeline controllers, while alarm management for pipelines is addressed by API RP 1167. They overlap because alarms appear on displays, but 1165 is about the visual design and hierarchy of graphics, and 1167 is about which conditions should alarm, how they are prioritized, and how alarm floods are prevented.
It is written for pipeline SCADA control rooms operating hazardous liquid and gas transmission pipelines. Its human-factors principles, such as consistent symbology, disciplined color use, and clear data-quality indication, are good practice for any facility HMI, but the document itself is scoped to pipeline control-room displays and is referenced in the pipeline control room management context.
Yes. RP 1165 is about display design, not a specific technology, so its principles apply equally to a browser-based cloud SCADA interface. A platform like Merobix that presents pipeline and facility data over protocols such as Modbus, DNP3, and OPC UA can build graphics that honor RP 1165's guidance on hierarchy, color discipline, and data-quality indication.
This page references the protocol specifications published by the organizations below. Editions, product capabilities, and documentation change over time - confirm current requirements and specifications directly with the source.
Last reviewed: July 27, 2026. Merobix is not affiliated with, endorsed by, or sponsored by these organizations; their names are used only to identify the standards and products discussed.
Merobix reads your field devices into a cloud SCADA - the real thing behind these terms, live in days from any browser.