ISA 101: What It Is and Why It Is Needed Status Update and ...isawwsymposium.com/wp-content/uploads/2016/07/WWAC2016-Lehmann...ISA 101: What It Is and Why It Is Needed – Status Update

Standards

Certification

Education & Training

Publishing

Conferences & Exhibits

ISA 101: What It Is and

Why It Is Needed – Status

Update and Current Activities

2016 ISA Water / Wastewater and Automatic Controls Symposium

August 2-4, 2016 – Orlando, Florida, USA

Greg Lehmann, CAP

Process Automation Technical Manager

AECOM

Co-Chair, ISA 101 Committee

VP-Elect, ISA Image and Membership Department

[email protected]

2016 ISA WWAC Symposium

Aug 2-4, 2016 – Orlando, Florida, USA

Process Automation Technical Manager for

AECOM in the Denver, Colorado office.

30+ years of experience in process control,

instrumentation, automation, HMI design,

construction, and operations in the oil & gas,

mining, manufacturing, food & beverage, and

water treatment industries.

Co-Chair of the ISA 101 Standard Committee

VP-Elect, ISA Image and Membership Department

Director, ISA Standards and Practices Board

2

Greg Lehmann, CAP


Aug 2-4, 2016 – Orlando, Florida, USA 3

Presentation Outline

• ANSI/ISA-101.01-2015 Human Machine Interfaces for

Process Automation Systems Standard Committee

– Purpose, Scope, Leadership, Voting Members

• Progress and current status

• What is the ISA 101 Standard and what does it contain?

• Current activities on the Standard Committee



ISA 101 Standard Committee

• Committee formed in 2006 to establish standards,

recommended practices, and/or technical reports for

designing, implementing, using, and/or managing human

machine interfaces in process automation applications

• Committee makeup

– As of July 1st, 2016 – members 243

– Producer (Supplier) 29.6%

– User 25.5%

– Integrator, Eng & Construction 33.7%

– General (Academic, Government, Consultant etc.) 11.2%

– Worldwide participation in review process



Purpose of the Standard

• Address the design, implementation, and maintenance of

human machine interfaces (HMIs) for process

automation systems, to:

– Provide guidance to design, build, and maintain HMIs which

result in more effective and efficient control of the process, in

both normal and abnormal situations

– Improve the user‟s abilities to detect, diagnose, and properly

respond to abnormal situations

– Look at the HMI holistically – not just the display

• A Standard is the “What”

• A Technical Report is the “How”



Scope of the Standard

• Addresses HMI‟s for automated processes to improve safety, quality, and

productivity

• Identifies documentation and design practices that will lead to more effective

and maintainable HMI implementations

• Practices defined in ISA 101 are intended to be applicable to continuous,

batch, and discrete processes

• Devices excluded – the committee agreed to limit the scope to hardware of

a minimum size

– No PDA‟s, smart phones, hand held devices included in this version of the

standard (see later)

• NOTE: The standard cannot recommend the use of commercial standards

or documents such as the ASM Guidelines, texts, etc.



Who cares about HMI Standards?

• Users

– Responsible for safe and productive operation of equipment and facility

– Live with the HMI and support it for it‟s lifetime

• Integrators, Designers, Engineers

– Design and build the HMI applications

– Commission the HMI, and the associated process

• Suppliers

– Develop the software and hardware needed to build the HMI

– Develop the interfaces/drivers needed for an HMI to transfer data and

information to and from multiple sources



ISA 101 Standard Committee - Leadership

The Co-Chairs of the ISA 101 HMI Committee are: Dr. Maurice Wilkins (Yokogawa) and Greg Lehmann (AECOM)

The draft standard was organized into the following sections:

Clause Title Leaders

0 General Maurice Wilkins, Yokogawa & Greg Lehmann, AECOM

1 Scope Maurice Wilkins, Yokogawa & Greg Lehmann, AECOM

2 Normative References Nick Sands, Dupont & Dale Reed, Rockwell

3 Definition of Terms and Acronyms Nick Sands, Dupont & Dale Reed, Rockwell

4 HMI System Management Bridget Fitzpatrick, Wood Group Mustang & Ian Nimmo, UCDS, Inc

5 Human Factors/Ergonomics Beth Vail, AECOM & Traci Laabs, Pfizer

6 Display Styles and Hierarchy Dave Lee, UCDS, Inc & John Benitz, Gray Matter Systems

7 User Interaction Bridget Fitzpatrick, Wood Group Mustang & Alan Bryant, Oxy Inc.

8 Performance Mark Nixon, Emerson Process Management

9 Documentation and Training Dawn Schweitzer, Eastman Kodak



ISA 101 Standard Committee - Voting

• Based on established voting rules

– 20 % of committee – to manage the numbers

– 30% for PR, US, AE and 10% for others

– 24 month window of participation

– Weighted toward individual input to standard

– Last review was in May 2014

• ISA 101 has 34 voting members – which is not 20% of

the committee (243) but, based on the rules…34

qualified



Progression of the ISA 101 Standard

• The Draft of the Standard began life as a topic based outline

document, and the outlined topics eventually evolved to become the

subjects of the Standard Clauses.

• The outline document became a smorgasbord of topics with only the

outline format holding it together in structure.

• The Committee F-2-F meetings in Indianapolis in 2009 began to

give the document its current structure, that went on to become the

basis for the approved Standard.

– HMI terminology and interrelationship diagram

– HMI Lifecycle concept

• First draft (R0) out for Review and Comment in May 2010. Received

almost 700 comments from 25 Reviewers.



Status of ISA 101 Standard

• Four more drafts followed and were reviewed by Committee over the

next three years.

• The final, Draft 4, was sent out for a one month review by the full

committee at the end of June 2013

– This was a „should‟/‟shall‟ requirements survey

– There were 20 requirements (shall) & 285 recommendations (should)

suggested

– 67 committee members responded

– The overall average was 85% acceptance of the

requirements/recommendations as written

• After discussions at F-2-F meetings during ISA Automation Week in

November 2013, the draft was „polished‟ by a small team of Clause

Leaders and prepared for ballot as a standard.




• The voting member roster was updated and finalized based on

participation over the past 2 years

• On May 27th, 2014 the draft was sent to the committee for a one-

month ballot as ISA-d101-01_CDV1

– The ballot was provisionally approved with 31 votes in favor, 2 votes

against and one voter not responding

– 42 committee members submitted 1162 comments consisting of 829

editorials, 19 major technical and 314 minor technical

– The Clause Leaders began working through the comments after which

time the draft was to be re-submitted for a short ballot period to give the

voting members a chance to change their vote if they wished

– It took two face to face meetings and until March 2015 to resolve these

comments




• A short re-ballot was needed to see if anyone wanted to change their

vote – per ISA procedures

– The 2 (from 34) who voted against, changed their vote to positive, so the

end result was unanimously in favor

• ISA 101 was approved by the ISA Standards & Practices board in

early 2015

• ISA 101 subsequently became a nationally recognized ANSI/ISA

standard with ANSI approval in July, 2015

• Formal name: ANSI/ISA-101.01-2015, Human Machine Interfaces

for Process Automation Systems



What Is ISA 101?



HMI Basic Definitions

• Fundamental standard

terminology

– Console

– Operator Station

– Monitor

– Screen

– Display

– Pop-up

– Element

• Necessary to enable

common understanding

19

X?X?

X?

X?

Console

Display

Graphic

Elements

Mouse

(Pointing

Device)

Station

Monitor

Graphic

Symbols

Popup

Full-Screen

Display

X?

Pointing

Device

(Touchscreen)

Screen



HMI Life Cycle Concept

• The life cycle model is a foundation for the standard

DESIGNSYSTEM STANDARDS

OPERATEIMPLEMENT

CONTINUOUS WORK PROCESSES

Continuous Improvement

RE

VIE

W

Philosophy

Style Guide

Toolkits

MOC Audit Validation

In Service

Maintain

Decommission

Continuous Improvement

Build Displays

Build Console

Test

Train

Commission

Qualification

Console Design

HMI System Design

User, Task, Functional

Requirements

Display Design

New DisplayDisplay Changes

New SystemMajor Changes

ENTRYENTRY



Life Cycle Concept - Stages

• System Standards

– Documents that set the foundation for all HMI design decisions

• Design

– All hardware and software aspects of the HMI

• Implement

– Creation of the HMI in the target platform and hardware

• Operate

– Includes the ongoing maintenance, training, and management of

change functions



System Standards Stage

• The basic requirements for any HMI application

Activity Objectives Inputs Outputs

Define HMI

Philosophy

Provide guiding principles

for HMI design,

independent of vendor

platforms

Human Factors

Engineering guidelines,

Standards, Best Practices,

Functional requirements,

experience

HMI Philosophy Document

Develop HMI Style

Guide

Provides HMI

implementation details

based on the HMI

Philosophy, feasible on all

target platforms

Requirements documents,

Control System and

Network design standards

HMI Style Guide

HMI Toolkit Provide required graphical

elements to implement

displays based on the Style

Guide

HMI Style Guide,


vendor supplied elements,

experience

HMI Toolkit; Platform

Specific



Design Stage

• Identification of requirements

• Initial designs for all HMI components Activity Objectives Inputs Outputs

User, Task and

Functional

Requirements

Identify activities that

must be supported by the

HMI

Process Functional

Requirements, User Task

Analysis, HMI Philosophy

Requirements Documents

HMI System Design Identify platforms for HMI,

control, interfaces, and

communication


Control System and

Network design standards

HMI System Design

specification

Console Design Define complete hardware

and software required,

including all furniture and

supporting systems


HFE design standards,

vendor specifications

Console design documents

Display Design Identification of all displays

needed, and navigation

scheme

HMI Philosophy, HMI Style

Guide,

Requirements documents

Display design

documentation, ready for

implementation



Implement Stage

• Detailed work to actually build the HMI


Build Displays Completion of all displays

and supporting items

Display Design documents Displays,

User Documentation

Build Console Assembly of all console

hardware and software

Console Design documents Console

Test Integrated test of HMI and

Console

User, Task, Functional

Requirements, Test Plan

HMI ready to commission,

Testing documents,

updated User

Documentation

Commission HMI operational in

production environment

Console, Displays, User

documentation

HMI ready to operate

Train Train all users relative to

their responsibilities

User Documentation,

Requirements Documents,

HMI Philosophy, HMI Style

Guide, as appropriate

HMI ready to operate



Operate Stage

• Life with the HMI


In Service HMI in use Commissioning,

Qualification Approval,

User Documentation

Effective HMI

Maintain Ensure HMI reflects current

process requirements

Management of Change

process

Updated, requalified HMI

application, user

documentation, training

materials

Decommission HMI removed from service,

in part or whole

Requirements,

Management of Change

process

HMI (or parts thereof)

removed, archived for

appropriate period



Continuous Improvement Activities

• Activities and procedures to maintain the HMI


Management of

Change

Implement changes,

ensuring consideration of

all impacts

Changes in Process

Changes in User, Task or

Functional Requirements

Changes implemented

following approved work

practices to ensure safe

and effective operation

Audit Verify that HMI is being

managed under approved

work practices

HMI Philosophy,

HMI Style Guide

HMI Toolkits

Audit records, MOC,

updates to relevant

Standard documents

Validation Verify HMI meets current

User, Task and Functional

Requirements

Validation Plan Validated system and

appropriate records



ISA 101 Standard – Current Activities

• The committee met in Louisville at the 2015 ISA FLM and chartered three

working groups

– WG1 - HMI Philosophy & Style Guide Development

– This technical report will describe example applications of the Philosophy and

Style Guide to various Process Automation Systems use cases, and will be

platform independent (41 members)

– WG2 – HMI Usability and Performance

– This technical report(s) will be used to assess the effectiveness of the HMI

application, and how the use of the standard will assist in improving related

metrics (29 members)

– WG3 – HMI for Mobile Devices

– Develop technical report(s) to evaluate and define the use of mobile devices as

HMI stations and how to effectively implement an HMI for use on a mobile device

(21 members)

• Work is well underway on all three Working Groups, please send me an

email if you‟d like to get involved.

• ISA 101 will meet at the 2016 ISA FLM (Sept)



NEW ISA 112 Committee – SCADA Systems

SCADA Systems Scope

Develop a series of ISA standards and technical reports to improve the overall reliability of

SCADA system design, installation, integration, and operation of the infrastructure for pipelines,

water and wastewater, power, oil and gas, and other industries to improve the

overall integrity and reliability of these systems.

Note: Existing standards address the individual components (controllers, human-machine

interface, alarming, etc.) and associated protocols (DNP, IEC 61850, etc.), which represent

various aspects of SCADA systems. However, there are no documents to address the need for

consistent definition and implementation of the infrastructure to connect these elements to

create, operate, and maintain a SCADA system throughout its life cycle.

SCADA Systems Purpose

The standards and technical reports will provide guidance on how to implement effective

reliable SCADA systems by documenting best practices in a range of industries. The

anticipated plan is to develop one or more standards to be supplemented by technical reports

expanding on implementation details and industry-specific guidelines.



QUESTIONS??

Wrap Up

Greg Lehmann, CAP

[email protected]