Scribd Logo
Upload

Welcome to Scribd!

  • 481 views

    Alarm Philosophy Example

    Uploaded by

    Abdul Samad
    This document discusses the ISA101 lifecycle for developing and maintaining HMIs. It covers establishing system standards like an HMI philosophy and style guide. The lifecycle includes design, implementation, operation, and continuous improvement stages. The presentation provides examples of developing an HMI philosophy document, style guide, and going through the design process, which includes requirements gathering, display design, and testing. The goal is to outline the full lifecycle process for HMIs based on ISA101 standards.

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd

    Alarm Philosophy Example

    Uploaded by

    Abdul Samad
    481 views21 pages
    This document discusses the ISA101 lifecycle for developing and maintaining HMIs. It covers establishing system standards like an HMI philosophy and style guide. The lifecycle includes design, implementation, operation, and continuous improvement stages. The presentation provides examples of developing an HMI philosophy document, style guide, and going through the design process, which includes requirements gathering, display design, and testing. The goal is to outline the full lifecycle process for HMIs based on ISA101 standards.

    Original Description:

    Alarm management document example

    Copyright

    © © All Rights Reserved

    Available Formats

    PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    This document discusses the ISA101 lifecycle for developing and maintaining HMIs. It covers establishing system standards like an HMI philosophy and style guide. The lifecycle includes design, implementation, operation, and continuous improvement stages. The presentation provides examples of developing an HMI philosophy document, style guide, and going through the design process, which includes requirements gathering, display design, and testing. The goal is to outline the full lifecycle process for HMIs based on ISA101 standards.

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd
    Download as pdf or txt
    481 views21 pages

    Alarm Philosophy Example

    Uploaded by

    Abdul Samad
    This document discusses the ISA101 lifecycle for developing and maintaining HMIs. It covers establishing system standards like an HMI philosophy and style guide. The lifecycle includes design, implementation, operation, and continuous improvement stages. The presentation provides examples of developing an HMI philosophy document, style guide, and going through the design process, which includes requirements gathering, display design, and testing. The goal is to outline the full lifecycle process for HMIs based on ISA101 standards.

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd
    Download as pdf or txt
    You are on page 1of 21

    ISA101: From Philosophy

    to Operation

    Standards
    Certification
    Education & Training
    Publishing
    Conferences & Exhibits
    About the Presenter
    Nicholas Sands, CAP, PE
    • ISA Fellow
    • Technology Fellow at DuPont
    • Alarm management and HMI best practice leader
    • 25 years of experience in chemical plants
    • Co-chair of ISA18 standard committee
    • Secretary of IEC 62682 standard committee
    • ISA Vice President of Standards and Practices

    2
    Outline

    • Background
    • HMI Lifecycle
    • HMI Philosophy
    • HMI Style Guide and Tool Kit
    • User Requirements
    • Testing
    • Training
    • Support
    • Questions
    Background: The Last Panel Board

    • Plant originally built with pneumatic controls


    • Controls migrated to Single Loop Controllers (SLCs) in
    1986
    – Panelboard HMI (Human Machine Interface)
    – Hardwired SIS (Safety Instrumented System)
    Background: The Replacement

    • New Control System


    – DCS Controller
    – DCS HMI
    – SIS
    HMI Lifecycle

    • ANSI/ISA-101 lifecycle to develop and maintain an HMI


    – ISA-101.01 HMI for Process Automation Systems
    CONTINUOUS WORK PROCESSES
    MOC Audit Validation

    ENTRY ENTRY

    New System New Display


    Major Changes Display Changes
    SYSTEM DESIGN IMPLEMENT OPERATE Continuous
    STANDARDS Improvement
    Console Design Build Displays In Service
    Philosophy
    REVIEW

    HMI System Build Console Maintain


    Style Guide Design
    Test Decommission

    Toolkits User, Task,


    Functional Train
    Requirements
    Commission
    Continuous Display Design
    Verification
    Improvement
    HMI Lifecycle – System Standards

    • For projects, start with system standards


    – HMI Philosophy document
    – Provide guiding principles and conceptual
    foundation for HMI design (includes details on
    how HMI is designed and used)
    – HMI Style Guide
    – Apply guiding principles and concepts of the
    HMI Philosophy to provide implementation
    examples and guidance
    – HMI Toolkits
    – Generate all graphical symbols and
    other supporting elements as required to
    implement the HMI Style Guide
    HMI Philosophy

    • Philosophy
    – Overall guiding document for
    HMI design and management
    – Emphasizes ergonomics and
    performance
    – Document objectives around
    situation awareness
    HMI
    – Documents requirement for ON
    MOC
    – Document other processes (task
    analysis)
    – Document “rules”
    – Defines terms
    HMI Philosophy Example – Level 3 Rules

    • The Process Display shows all important Process Level 0


    Variables, Alarms, and Controls related to a given Plant
    Overview
    Process or subsystem.
    • The purpose of the Process Display is to provide Level 1
    Area
    Operator access to operate individual objects for a Overview
    process or subsystem.
    • Many common operating tasks are performed from Level 2
    Cell/Unit
    Process Displays. Overview
    • Rules:
    Level 3
    • Level 3 Rule: Every alarm, interlock and control point Process
    is shown on a level 3 graphic. Display
    • Level 3 Corollary: If a point doe not alarm interlock or
    control it is not shown on a level 3 graphic. Level 4
    Equipment
    • Exceptions are allowed. Detail
    HMI Terminology

    • From 1 Console
    9 (multi-

    ISA101.01 Consoles station)


    Console
    (single-
    station)

    Station
    (multi-
    monitor)

    Stations

    Screen Keyboard Pointing Pointing Device


    Device ? X (Touchscreen)
    (Mouse)
    Station
    Components
    Monitor Monitor

    ? X
    Display ? X ? X Popup
    (Full-Screen)

    Displays

    ? X

    Graphic
    Display Symbols
    Components
    Graphic
    Elements
    HMI Style Guide & Toolkit

    • Style Guide
    – Vendors offer style guides
    – Designed on ASM or HPHMI
    principles
    • Toolkit
    – Display of selected and
    approved symbols
    – Started with vendor library
    – Modified or configured to meet
    user requirements
    – Control changes to the toolkit
    Design

    • Console Design
    – To provide hardware and software design for the
    Console. This includes furniture and supporting
    systems.
    • HMI System Design
    – Identify design basis for the HMI system.
    • User, Task, Functional Requirements
    – Identify primary and secondary requirements
    supported in the HMI.
    • Display Design
    – Identifies conceptual design for displays and the
    navigation hierarchy. (This may include some
    prototype displays on complex applications or
    processes).
    • Review
    Console and System Design

    • Console Design
    – Mostly vendor standards
    – Single area
    – Two stations on a desk
    – Mouse issues
    • System Design
    – Mostly vendor standards
    – User groups
    – Some modifications for user
    requirements
    • Display Design
    – Template display
    – Display and font size
    User and Task Requirements

    • Task Analysis
    – Informal method
    – Review each operating
    procedure against the
    displays
    – Verify each action can be
    taken
    – Look for ways to improve
    the execution by modifying
    display content
    – Where needed, develop
    task specific displays
    Implement

    • Build Displays
    – Complete construction of displays and supporting
    items. (User review occurs in the design stage,
    which include prototypes).
    • Build Console
    – Complete construction of console hardware and
    software. Test viewing angles, screen elevations,
    keyboard and input device placement and location
    of other elements.
    • Test
    – Integrated Test of HMI and Console.
    • Train
    – Train Users.
    • Commission
    – Final testing of HMI in Production Environment.
    • Verification
    – Verify HMI Ready to Operate.
    Build Displays and Consoles

    • Build Console
    – Time consuming to work
    through system details
    • Build Displays
    – Focus on flow and simplification
    – Built L3 displays first
    – Simple process with 6 main
    operating displays (L3)
    – Many more detailed displays
    (L4)
    – Built 1 overview display (L1/L2)
    last
    – Many iterations with toolkit
    changes
    Training

    • Operator training in 4 stages


    – DCS and HMI Basics
    – Review of all features of symbols,
    menus, faceplates…
    – Screen by screen training
    – Review each loop on each level
    display
    – Loopback simulation
    – Practice basic interfacing with simple
    models
    – Dynamic simulation on tasks
    – Startup, shutdown, repeat
    Testing, Commissioning & Verification

    • Testing
    – Completed with dynamic simulation
    – Real configuration in simulated
    controller
    • Commissioning & Verification
    – Done during shutdown
    – Completed with DCS controller
    commissioning
    – Released for operation
    ISA 101 Results

    • Much the same


    – Most steps are the same steps used in past
    projects
    • But, a few differences
    – Use of toolkit vs library
    – Deeper task analysis than P&ID approach
    – Formalization of training on philosophy
    • Benefits
    – Opportunity to standardize terminology
    – Opportunity to map activities to project
    phases
    Questions?
    Thank you for attending
    ISA PCS2015!

    21

    You might also like