February 2019 Section Meeting - ... 351 25 6.0 21 0.45 0.9 200 90 F. in.H2O A2ID Stall A2FD Stall...

download February 2019 Section Meeting - ... 351 25 6.0 21 0.45 0.9 200 90 F. in.H2O A2ID Stall A2FD Stall Fans

of 39

  • date post

    17-Jul-2020
  • Category

    Documents

  • view

    1
  • download

    0

Embed Size (px)

Transcript of February 2019 Section Meeting - ... 351 25 6.0 21 0.45 0.9 200 90 F. in.H2O A2ID Stall A2FD Stall...

  • February 2019 Section Meeting

    HMI Usability and Performance ISA TR101.02

  • Thank You to All of Our Sponsors!

  • Upcoming Section Events

    March 12 – Virtualization in Industrial Automation – Sponsored by Champion Technology Services

    April 2 – Compressor Surge Modeling and Control – Guest Speaker Greg McMillan

    May 7 – Section Tour – Michelli Calibration Lab – Lunch, Tour, Presentation, and Demonstrations

    May 31 – Exhibition and Symposium – Hilton Garden Inn Convention Center

    June 1 – District 7 Leadership Conference – Hilton Garden Inn Convention Center

    Control System Engineering PE Review Course - TBD

    Check for updates and register to attend events at https://neworleansisa.org/events/

    https://neworleansisa.org/events/

  • ISA Technical Report 101.02 HMI Usability and Performance

  • ISA 101 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

    ANSI/ISA-101.01-2015 Human Machine Interfaces for Process Automation Systems • Approved July 9, 2015

    Over 300 Voting Members • Integrator, Engineering & Construction 35% • End User 27% • Vendor/Supplier 25% • General (Academic, Government, Consultant etc.) 13%

    • Worldwide participation in review process

  • The Purpose of ISA 101

    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

    Standards are the “What” Technical Reports and Recommended Practices are the “How”

  • 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 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) • Co-chairs; David Lee and Lothar Lang

    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) • Co-chairs; David Board and Ruth Schiedermayer

    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) • Co-chairs; Mark Nixon and Peder Brandt

    WG4 – HMI for On-Machine Applications • Develop technical report(s) to effectively implement a machine-level HMI utilizing an operator

    interface terminal • Co-chairs; Arlen Jacobs and David Board

  • ISA TR101.02 Content

    1 – Scope 2 – References 3 – Definition of terms and acronyms 4 – HMI usability and performance 5 – Usability 6 – Performance 7 – HMI Effectiveness Annex A (Informative) – HMI effectiveness measurements Annex B (Informative) – A case study of effective HMI design for increasing usability

  • HMI Lifecycle

    DESIGNSYSTEM STANDARDS

    OPERATEIMPLEMENT

    CONTINUOUS WORK PROCESSES

    Continuous Improvement

    R E

    V IE

    W

    Philosophy

    Style Guide

    Toolkits

    In Service

    Maintain

    Decommission

    Continuous Improvement

    Build Displays

    Build Console

    Test

    Train

    Commission

    Verification

    Console Design

    HMI System Design

    User, Task, Functional

    Requirements

    Display Design

    New Display Display Changes

    New System Major Changes

    ENTRYENTRY

    MOC Audit Validation

  • Example testing of HMI modifications

    Method 1: Newly created/modified displays available only on the engineering console.

    Operators are directed to familiarize themselves with the modified displays on the engineering console. After familiarization and any corrections made based on feedback, the modified displays replace the versions on the operator’s console.

    Method 2: Newly created/modified and renamed version of displays available only on the operator's console.

    Limit access to these by requiring that they be called up via direct name entry rather than incorporation into the HMI navigation, or make them selectable in a secured access "TEST" section of the HMI navigation. Direct the operators to use these graphics for testing and familiarization. When completed, delete the original displays and rename the modified ones to those original names, thus ensuring their proper access in the existing HMI navigation and links to other displays.

    Method 3: Prior to deployment, newly created/modified displays only available on a training system.

    In some cases, testing, familiarization, and operator training is carried out on a system completely separate and isolated from the actual process to avoid any chance of the testing affecting the process. For thorough testing, simulation of the process is possible.

  • Usability – HMI Design - Color

    8% of men and 0.5% of women are red-green color impaired

  • High Contrast Color and Redundant Coding

    Use of color should be standardized for certain functions (ie Red for Alarms and Yellow for Warnings)

  • Effective Displays

  • Effective Displays

  • Effective Displays

  • Effective Displays

  • Radar Chart Examples

  • Startup and Inhibitors Table / Checklist

    The main points that make this figure a good table for imparting information are as follows:

    a) conditions requiring action are differentiated and highlighted;

    b) conditions that are resolved are grayed out making it easier to sense progress;

    c) good alignment of condition status texts improves readability;

    d) consistent vertical padding in rows increases readability; and

    e) descriptions are left justified and use mixed-case text to improve readability.

  • Startup and Inhibitors Table / Checklist

    The main points that make this figure a good table for indicating equipment states are as follows:

    a) increased reading dynamic by grouping A2 items and B2 items on separate rows;

    b) limited grid formatting with a low contrast line separator; c) generous margins, padding and spacing which increases

    readability; and d) abnormal equipment status notification is provided by

    redundant means. In the example in Figure 16 the color of the square encompassing the equipment, the number and the symbol clearly indicate where an abnormal condition is and its severity.

  • Clear Messaging Methods

    When showing information to the operator in text form, the text should be legible from the expected operator position(s).

    Invisible states that appear to the operator only on specific contexts should be avoided.

    The operator should be able to fully confirm the current state anytime, meaning that an invisible object cannot represent a state (since it cannot be differentiated from no object at all).

    Example: BLOWN FUSE visible and highlighted to indicate a blown fuse and not visible to indicate normal state is incorrect. Text should read BLOWN FUSE to indicate a blown fuse and FUSE OK to indicate normal state.

  • Trend Examples

  • Trend Examples

  • Trend Recommendations

    Trends make use of color to distinguish between several values being trended. The complexity of the trend display can be managed by the following recommendations:

    a) no greater than 12 traces per trend;

    b) ability to distinguish traces by way of symbols and/or ability to "hide" and "show" specific traces without deleting the trace; and

    c) ensure color choices for traces do not compete with the other potential 11 traces on the trend, nor the background color of the trend.

  • Level 1 Display – Overview of the operator’s entire span of control

  • Level 1 Display – Overview of the operator’s entire span of control

  • Level 1 Display – Overview of the operator’s entire span of control

  • Level 2 Display – Primary operating display during normal operations

  • Level 3 Display – Process diagnostics and task execution support

  • Level 4 Display – Diagnostic, informational displays,