IPCS Hmi Philosophy

8/13/2019 IPCS Hmi Philosophy

1/9

Specification: IPCS HMI Philosophy

Spec. No: SAFIRE-PC550-252 Rev. A Date: Aug. 2013

Discipline: Inst. & Control Suffix: Page: 1 of 1

Project Name: San Ardo Facilities Replacement Project Proj. No: 8440

OriginatingSpec.

AE00-GEN-550-252-GUI Date: Feb. 2012

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.


2/9

Aera Energy LLC AE00-GEN-550-252-GUI

IPCS - HMI Philosophy

Revision HistoryDraft Date Submitted for Review

Date

Final Date Next Review Date Version Author

2/2/2012 2/3/2012 2/9/2012 V1.0 Andreas Somogyi

2/28/2012 2/28/2012 V1.1 HMI-Standardization

Team Review

ApprovalsDate Version IPCS Team Approvers Area of Responsibility


3/9

V 1.0 Page 2 of 8

Table of Contest

1 Introduction ......................................................................................................................... 3

1.1 Executive Summary _____________________________________________________________ 3

1.2 Executive Sponsors ______________________________________________________________ 3

1.3 Team Members _________________________________________________________________ 3

1.4 Scope _________________________________________________________________________ 4

2 HMI Fundamental Principles and Goals ................................................................................. 4

3 Definition of Display Layers .................................................................................................. 4

3.1 Graphics _______________________________________________________________________ 5

3.2 Colors _________________________________________________________________________ 6

3.3 Layout ________________________________________________________________________ 63.4 Lines, Vessels, Equipment _________________________________________________________ 6

3.5 Data Display, Values, Text ________________________________________________________ 6

3.6 Process Controllers ______________________________________________________________ 7

3.7 Control & Shut-Off Valves ________________________________________________________ 7

3.8 Objects & Symbols ______________________________________________________________ 7

3.9 Alarm Behavior _________________________________________________________________ 7

3.10 Trending ______________________________________________________________________ 7

3.11 Navigation _____________________________________________________________________ 7

4 Security: ............................................................................................................................... 8

5 Testing, Installation, Commissioning, Training ...................................................................... 8


4/9

V 1.0 Page 3 of 8

1 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 theIPCS - 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

Keith Lobo Manager IE&C

Saul Hernandez Senior Facilities Engineer

1.3 Team Members

Andreas Somogyi Project Lead

Pierre Boucher SST

Paul Rogers CPE

Bob Edgar FAS

Matt Hatton Operations

Adrian Vega Operations

Vince Romero PLC Plus

Christian San Juan CPE


5/9

V 1.0 Page 4 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.

2 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 easyto read, and intuitive manner, with proper feedback

Reaction time is optimized by providing the operator information needed in asimple, logically progressive, performance-orientated HMI display structure.

3 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)


6/9

V 1.0 Page 5 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)

Enterprise Aera Layer1 (Plant Overview Display)

Site Location of facility, Belridge, Midway, etc. Layer 1 (Plant Overview Display)

Area One or more processes Dehy, Water Plant, Gas

Plant

Layer 1 ( Plant Overview

Display)

Cell 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.

Layer 2 (Process Overview)

Unit 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

Layer 3 (Operator Control)

Equip.

Module

Functional group of equip. & / or control

modules that carry out a finite number of

activities. Motor, Pump, Valve, Sand dump, Fin

Fan, Compressor, Separator


ControlModule

Regulating device, or state device orcombination of the two (collection of sensors,

actuators that are operated as a single device).

Transmitter, PID, VFD


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.


7/9

V 1.0 Page 6 of 8

3.2 Colors

Light gray backgrounds are used to minimize glare and fatigue, along with a generally low-

contrast depiction


8/9

V 1.0 Page 7 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 percentagenext 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 alarmsound (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 shouldhave 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 ordirect clicking of a lower level graphic.


9/9

V 1.0 Page 8 of 8

4 Security:

HMIs need to be developed according to the Aera IPCS security program and incorporate

the rules guidelines specified.

5 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

IPCS Hmi Philosophy

Documents

Transcript of IPCS Hmi Philosophy