Specification: Spec. No: Discipline: Project Name: Originating Spec. SAFIRE-PC550-252 Inst.

& Control

IPCS HMI Philosophy Rev. Suffix: A Date: Page: Proj. No: Date: Aug. 2013 1 of 1 8440 Feb. 2012

San Ardo Facilities Replacement Project AE00-GEN-550-252-GUI

Cover Sheet for SAFIRE-PC550-252, IPCS HMI Philosophy ___________________________________________________________________________

Aera Energy, AE00-GEN-550-252-GUI, Feb. 2012, is accepted as SAFIRE-PC550-252, IPCS HMI Philosophy, with modifications listed below.

___________________________________________________________________________
No modifications.

Aera Energy LLC

AE00-GEN-550-252-GUI

IPCS - HMI Philosophy

Draft Date 2/2/2012

Revision History
Submitted for Review Date 2/3/2012

Final Date

Next Review Date

Version V1.0 V1.1

Author Andreas Somogyi HMIStandardization Team Review

2/9/2012 2/28/2012

2/28/2012

Date

Approvals
Version

IPCS Team Approvers

Area of Responsibility

Table of Contest

Introduction ......................................................................................................................... 3
1.1 1.2 1.3 1.4 Executive Summary _____________________________________________________________ 3 Executive Sponsors ______________________________________________________________ 3 Team Members _________________________________________________________________ 3 Scope _________________________________________________________________________ 4

2 3

HMI Fundamental Principles and Goals................................................................................. 4 Definition of Display Layers .................................................................................................. 4

3.1 3.2 3.3 3.4 3.5 3.6 3.7 3.8 3.9 3.10 3.11 Graphics_______________________________________________________________________ 5 Colors_________________________________________________________________________ 6 Layout ________________________________________________________________________ 6 Lines, Vessels, Equipment_________________________________________________________ 6 Data Display, Values, Text ________________________________________________________ 6 Process Controllers ______________________________________________________________ 7 Control & Shut-Off Valves ________________________________________________________ 7 Objects & Symbols ______________________________________________________________ 7 Alarm Behavior _________________________________________________________________ 7 Trending ______________________________________________________________________ 7 Navigation _____________________________________________________________________ 7

4 5

Security: ............................................................................................................................... 8 Testing, Installation, Commissioning, Training ...................................................................... 8

V 1.0

Page 2 of 8

Introduction
1.1 Executive Summary

This document is intended to be integrated in the Aera IPCS (Industrial Process Control System) Philosophy. The IPCS Philosophy was created for use by all Automation Specialists and System Integrators working at or for Aera Energy LLC. Using the concepts described in this document will help achieve gains in HMI software development, productivity, maintenance, safety, and usability. It is intended to provide Aera Energy with high layer guidance toward designing a Best-of-Breed Human Machine Interface (HMI). This Philosophy is based on a number of recent standard activities, global HMI studies, books, and interviews. The HMI Philosophy covers the life cycle of the HMI including design, implementation, performance monitoring, ongoing modifications, and management of change. The principles embodied in the Best of Breed HMI are communicated in the Philosophy document. It is intended to be generic and apply to multiple types of HMI systems, independent of the HMI or PLC supplier. For HMI programmers it is required to read the IPCS - HMI Programming Guide. The Philosophy document aligns with the ANSI/ISA-101 standard, and was customized according to Aera Energys need and usage.

1.2

Executive Sponsors Manager IE&C Senior Facilities Engineer

Keith Lobo Saul Hernandez

1.3

Team Members Project Lead SST CPE FAS Operations Operations PLC Plus CPE

Andreas Somogyi Pierre Boucher Paul Rogers Bob Edgar Matt Hatton Adrian Vega Vince Romero Christian San Juan

V 1.0

Page 3 of 8

1.4

Scope

The primary scope of this document is to enable Aera Energy to run the operations smoothly, safely, and efficiently, as well as help to detect, diagnose, and respond to abnormal situations, at the earliest possible moment, and with minimum adverse consequences. This document defines reference models for HMI designs in the Oil&Gas industry and terminology. It is focused on the high layer development guidance for System Integrators and other developers to comply with Aeras HMI standard activities. The document was created based on the ANSI/ISA 101 standard (draft) and aligned with a PLC programming standard (developed by Aera), which is based on the ANSI/ISA S-88 standard. Any deviation from this document requires a Request for Variance form to be completed and approved by the Aera IPCS Review Board.

HMI Fundamental Principles and Goals

.The following are three primary fundamental principle rules when developing and designing HMI. Depiction with highest possible CLARITY Depiction with highest possible CONSISTENCY: Depiction with consistent FEEDBACK:

Applying these principals will result in graphics with the following goals and attributes. The Operators attention is drawn to the most critical information Confusion and mistakes are eliminated by designing the HMI in a consistent easy to read, and intuitive manner, with proper feedback Reaction time is optimized by providing the operator information needed in a simple, logically progressive, performance-orientated HMI display structure.

Definition of Display Layers

A concept of hierarchy layers should be followed in constructing HMI displays. The primary reason is in providing different amounts of operating detail to aid the operator in performing different tasks. A secondary purpose for these layers is to allow for easier navigation. Four layers are optimum. Layer 1: Plant Overview (for situation awareness) Layer 2: Process Overview (for ongoing process manipulation) Layer 3: Operator Control (for close, detailed examination) Layer 4: Support and Diagnostics Displays (for troubleshooting) V 1.0 Page 4 of 8

To define the best display layer strategy for Aera, the standards team applied the ISA-S101 recommendations and associated the Physical Model of the ISA S-88 standard with it. By using this methodology, one can now position the graphic display layer to the plant equipment and control model, as shown below:
S 88 Layer S88 Definition S 101 Graphic Display Layer (HMI Guidelines doc) Layer1 (Plant Overview Display) Layer 1 (Plant Overview Display) Layer 1 ( Plant Overview Display) Layer 2 (Process Overview)

Enterprise Site Area

Aera Location of facility, Belridge, Midway, etc. One or more processes Dehy, Water Plant, Gas Plant Represents a collection of Units (and EMs) operating together for a common task. Group of Filters, Group of Steam Generators, WAC, SAC, Group of Co-Generators, Several FWKOs in parallel. Collection of related control and equip. modules that can carry out one or more processing activities. Filter, Pump Skid, Steam Generator, Clarifier, ISF, Free Water Knock Out, Injector Well, Softener, VRU Functional group of equip. & / or control modules that carry out a finite number of activities. Motor, Pump, Valve, Sand dump, Fin Fan, Compressor, Separator Regulating device, or state device or combination of the two (collection of sensors, actuators that are operated as a single device). Transmitter, PID, VFD

Cell

Unit

Layer 3 (Operator Control)

Equip. Module

Layer 3 (Operator Control)

Control Module

Layer 3 (Operator Control)

Layer 4 (Support/Maintenance/ Trends/Alarms)

3.1

Graphics

No gratuitous animation, such as spinning agitators or pumps, moving conveyors, and slashing liquids and sprayers. Animation should be limited, and only used to highlight abnormal situations.

V 1.0

Page 5 of 8

3.2

Colors

Light gray backgrounds are used to minimize glare and fatigue, along with a generally lowcontrast depiction <gray 3 (RGB 221,221,221) or gray 4 (RGB 192,192,192). Color is often highly overused. There should be very little use of color. Color should only be used to draw attention to important situations. Alarm colors are used only to display alarms and nothing else. Color is related to alarm priority. Every alarm priority has its own color which is used for nothing else, on any graphic, other than to depict alarm-related behavior. Areas Alarm Management Process Guide defines the following colors: Priority 1 (Highest); Red Priority 2 (2nd Highest); Yellow Priority 3 (3rd Highest); Orange

Foreground colors: a minimum number of colors should be used and quite sparingly. All use of color must be standardized and rigorously followed. Events will be captured and displayed in a separate display window. 3.3 Layout

In Aeras applications, all graphics should be developed consistent with the process flow, not necessarily with the physical location of the equipment. This design theory encourages consistent process understanding, for optimal operator training. Process flow is from left to right and preferably top to bottom, whenever possible. Wherever practical, crossing lines should be avoided. 3.4 Lines, Vessels, Equipment

Equipment and Vessels are depicted in a simple 2-D low-contrast manner, rather than brightly colored 3-D vessels with shadowing. The interior of vessels should be uniformly shaded, without gradients, and be the same as the background color. The vessels representative shape shall be shown, but without much detail. Do not use cut-away drawings detailing unchanging internals. There should be no animation associated with vessel internals. 3.5 Data Display, Values, Text

All screen resolutions should match the appropriate monitor size. Depiction of process values should be made in the context of information pertinent to the operation of the process being displayed. The information should be usable to an operator. Information is data in context made useful. Analog objects are often easier to monitor than digital objects.

V 1.0

Page 6 of 8

3.6

Process Controllers

A controller shall be embedded in the object it controls. Controllers may not just control a single valve, but also multiple elements, and even other controllers. 3.7 Control & Shut-Off Valves

Make consistent decisions, and definitions as to which controller output is a closed vs. an open valve. In some cases, its recommended to show the numerical open percentage next to the valve. 3.8 Objects & Symbols

Develop standard shapes and sizes for vessels, instrumentation, pumps, heaters, heat exchangers, interlock symbols, etc. Make use of pattern recognition, so objects can be identified at a glance. 3.9 Alarm Behavior

Color is related to alarm priority. Every alarm priority has its own color which is used for nothing else, on any graphic, other than to depict alarm-related behavior. It is recommended that every high priority alarm might also have its own unique audible alarm sound (hardware light could be substituted). All alarms should be segregated by priority and displayed in order of occurrence. Unacknowledged alarms should be distinguished from acknowledged alarms. The most common method is the flashing of the alarm indicator for the unacknowledged condition. To acknowledge alarms the operator must be logged in to the HMI application. 3.10 Trending Important information and key performance indicators (KPIs) have embedded trends. Trending is essential and should be used often. Every Layer 1 and Layer 2 display should have embedded at least one trend of the important values associated with the operation. 3.11 Navigation Navigation needs to be logical and consistent. Multiple methods of navigation should be provided. The operator should be able to go up and down through the hierarchy, side to side through the process, and call related details, trends, iBoxes, and shutdown status displays from any graphic. The system and graphics should be configured so it is never necessary for the operator to type in a point name or graphic name. The ability to get to any graphic without knowing the hierarchy should be available for users of the system; this may include an overall menu or direct clicking of a lower level graphic.

V 1.0

Page 7 of 8

Security:
HMIs need to be developed according to the Aera IPCS security program and incorporate the rules guidelines specified.

Testing, Installation, Commissioning, Training

Before installation, perform testing of the prototype graphics, preferably using a process simulator. Allow more users than those assigned to the design effort to review and participate in the testing. Operator training should be provided in the following areas: HMI operating procedures Aspects of Best of Breed HMI Philosophy relevant to operations Reasons why the HMI was changed and the expected benefits Features of the HMI alarm presentation, annunciation, and management. Navigation & Progressive Hierarchy Use of Trends Graphics for specific situations On-going HMI review, feedback, and continuous improvement

V 1.0

Page 8 of 8