ISA101 Hmiworkshop PDF

ISA101andHMIWorkshop
BridgetA.Fitzpatrick WoodGroupMustang
MESAKNOWS
SUSTAINABILITY&ECOEFFICIENCY LEAN METRICS&PERFORMANCEMANAGEMENT INFORMATIONINTEGRATION SAFETY ASSETPERFORMANCEMANAGEMENT B2MML QUALITY&COMPLIANCE PRODUCTLIFECYCLEMANAGEMENT AUTOMATION
Doyouknow MESA?
Topics
Industry yGuidelinesandStandards ISA101Status,Purpose,Scope ISA101Lifecycle KeyHumanFactorsIssues DisplayTypes UserInteraction Performance T i i Training Questions
2
Copyright2012,MESAInternational
ThepowerofknowingwhatMESAKNOWS
Bridgets Bridget sbackground

WoodGroupMustang,~9years
PracticeLeadforHMI,AbnormalConditionManagementandHuman FactorsEngineering ResponsibleforQualityonallHMI(515kdisplaysperyear)
CelaneseAG, AG ~15 15years

OptimizationEngineer EnergyTeamLead ControlSectionLead ControlEngineer ProcessDesignEngineer
ISAVolunteer,>20 0years
ISA101VotingMember,ClauseLeader(2clauses) ISA18VotingMember,WG6Cochair ISA84and106,InformationMember
3
Guidelines/StandardsonHMI
ISA101HumanMachineInterfacesforProcessAutomationSystems(draft) API1165RecommendedPracticeforPipelineSCADADisplays ASMConsortiumGuidelinesRev32008EffectiveOperatorDisplayDesign ANSI/HFES1002007HumanFactorsEngineeringofComputerWorkstations ANSI/HFES2002008HumanFactorsEngineeringofSoftwareUserInterfaces ISO9241Ergonomicrequirementsforofficeworkwithvisualdisplayterminals ISO11064Ergonomicdesignofcontrolcentres EEMUA201Processplantcontroldesksutilisinghumancomputerinterfaces:a guidetodesign,operationalandhumancomputerinterfaceissues NUREG0700Rev.22002HumanSystemInterfaceDesignReviewGuidelines
4
ISA101StandardCommittee
ThecurrentcochairsofISA101HMICommitteeare:
Dr. D M Maurice i Wilki Wilkins(Yokagawa) (Y k )and dG GregL Lehmann h (URS)
Clause 0 1 2 3 4 5 6 7 8 9 Title General Scope Normative References Definition of Terms and Acronyms HMI System Management Human Factors/Ergonomics Display Types User Interaction Performance Documentation and Training
5
Leaders Maurice Wilkins, Yokagawa Maurice Wilkins, Yokagawa Nick Sands, Dupont & Dale Reed, Rockwell Nick Sands, Dupont & Dale Reed, Rockwell Bridget Fitzpatrick Fitzpatrick, Wood Group Mustang & Ian Nimmo, UCDS, Inc. Beth Vail, URS & Traci Laabs, Pfizer Dave Lee, UCDS, Inc. & J h B John Benitz, i Applied A li d Control C l Engineering E i i Bridget Fitzpatrick, Wood Group Mustang & Alan Bryant, Oxy Inc. Mark Nixon, Emerson Dawn Schweitzer, Eastman Kodak
StatusofISA101Standard
Editorsreviewing gandresolving gcommentsfromDraft31. CommitteeconsensusthatthiswillbeaStandard. TechnicalReportsandRecommendedPracticeswillbe developedaswarranted.
6
PurposeoftheStandard
Addressthedesign, g ,implementation, p ,andmaintenanceof humanmachineinterfaces(HMIs)forprocessautomation systems. Use U of fthis thi standard t d dshould: h ld
Provideguidancetodesign,build,operate,andmaintaineffective HMIswhichresultinsafer,moreeffective,andefficientcontrolofthe process,inbothnormalandabnormalsituations. Improvetheusersabilitiestodetect,diagnose,andproperlyrespond toabnormalsituations.
7
ScopeoftheStandard
ThisstandardaddressesHMIsforequipmentandautomatedprocesses. Ifthestandard,recommendedpractices,andmethodologyarefollowed, theresultshouldenabletheuserstobemoreeffectiveinyielding:
improvedsafety, quality, productionand reliability. y
Thepracticesinthisstandardareapplicabletocontinuous,batch,discrete processes,andanyprocessusinganHMIforinterfacingtoacontrolled system.
8
IntendedAudience
Users
Responsibleforsafeandproductiveoperationofequipmentand facility
Integrators, Integrators Designers, Designers Engineers

DesignandbuildtheHMIapplications
Vendors
DevelopthesoftwaretoolsneededtobuildtheHMIapplication Developtheinterfaces/driversneededforanHMItotransferdata and a dinformation o at o toand a dfrom o multiple u t p esources sou ces
9
BenefitsofStandards
Consistency yinexecution
Easiertoimplementnewapplications Easiertohandofftothirdpartydevelopers
Lesstime L ti t totrain t i users Lessoperatorerrorasaresultofconsistenteffectivedesign EasiertomovebetweenplatformsorversionsofanHMI Savestimeandmoney!
10
WhytheConcernaboutHMIs?
11
11
HMIintheNews2
BPTexasCity3/23/05
The h control lboard b ddisplay d l didnotprovideadequate informationonthe imbalanceofflowsinand outof fthe h towertoalert l theoperatorstothe dangerouslyhighlevel.
Texaco,MilfordHaven,UK 7/24/94
Controlpanelgraphicsdid notprovidenecessary processoverviews overviews.
BesttokeeptheHMIoutof thenews!
12
HMIBasicDefinitions
Definitionsinclude:
Console, Station, PointingDevice, Device Keyboard, Display, Popup, GraphicSymbols, Graphic p Elements.
13
PotentialComplianceRequirements
Documentsrequired q
HMIPhilosophy HMIStyleGuide HMIToolkit HMIDesignDocumentation HMITrainingMaterials
Workpracticesthatalignwiththelifecyclestagesdefinedin thestandard
Testing, Testing Commissioning Commissioning,Training ManagementofChange
14
ISA101LifeCycleforHMI
15
LifeCycleConcept Stages
SystemStandards
DocumentsthatsetthefoundationforallHMIdesigndecisions
Design
Allhardware a d a eand a dsoftware so t a easpectsof o the t eHMI(review) (e e )
Implement
CreationoftheHMIinthetargetplatformandhardwarefrom buildingthroughtest,train,commissionandqualify
Operate
Includesthenormaloperationandmaintenance,aswellas decommissioning
Continuous
Managementofchange,AuditandValidation
16
KeyDocuments Documents inSystemStandards

HMIPhilosophy HMIStyleGuide HMIToolkit(Documentation)
17
WhatisanHMIPhilosophy?
TheHMIPhilosophy p yisastrategic g documentaddressing gthe guidingprinciplesthatgovernthedesignstructureoftheHMI. Definesthealignmentwith:
humanfactors, user,taskandfunctionalrequirementsforallmodesofoperationthat requireHMIsupport, designstandards,and workpracticesforthedevelopmentandmanagementoftheHMI.
Provideafoundationofconceptssuchthatnewdevelopers anduserscangrasptheunderlyingprinciplesandtechnical rationales.

18
WhyAllModes?3
CATASTROPHICLOSS ESDFails UnitShutdown EmergencyShutdownSystem(ESD)Acts EmergencyOperations Significantefficiencyandqualityissues Significantequipmentdamage Injuries,environmentaldamage Significantlossofproduction
OPERATORINTERVENTI ION
UpsetOperations Large L efficiency ffi i and dquality lit issues i Minorequipmentdamage NormalOperations Someefficiencylossesinrawmaterialsandenergy Someoffspecorlowerqualityproduct OptimalOperations Peakefficiencyandquality
19
ConsiderWhattoShowCarefully3
RealtimeOptimization andManufacturingExecutionSystems RTO/MES ExpertorOther Advisory Systems KnowledgebasedControl
OPERATORUPSETKNOW WLEDGE
Multivariable Control(DMC)
NeuralNetworks orOthers Models
MultivariableControl
Feedforward Control BasicLoop Control
Code Control
Logic Blocks ControlScheme Monitoring
EnhancedControl
LoopTuning
BasicControl
Field Indication
DCS Indication 20
Field Fi ld(Local) L l) Controllers
Fi ldControl Field C t l
WhatisanHMIStyleGuide?
AStyle y Guidewillincludegeneral g design g principles p p forthe displaysandimplementationstandards. ShouldreinforcetheguidingprinciplesfromthePhilosophy, i l di support including tfor: f
humanfactors, users,taskandfunctionalrequirements,and designstandards.
Alsoincludes:
Work W kpractices ti recommended d dto t managethe th HMI, HMI Guidanceondisplaytypesandtheirpreferreduse, GuidanceonexpectedHMIperformancetargets.
21
HMIToolkit
Typicallyplatformdependent
SomayhavemorethanoneToolkit
May ybevendorsupplied, pp ,customdeveloped, p ,ora combinationofthetwo p andexamples p ofallnecessary y Includestemplates graphicsymbolsandelementstoimplementanHMI applicationthatmeetstheStyleGuiderequirements
22
SystemStandardsStage
Activity Objectives Inputs Outputs HMI Philosophy Provides guiding principles and conceptual foundation for HMI design. This includes details on how th HMI is the i used d and d designed. d i d (Independent of platform). User Experience, Conceptual User Functional Requirements, Best Practices, Standards, Guidelines and H Human F Factors t Engineering E i i Considerations.
HMI Phil Philosophy h Document
HMI Style S l Guide
Turns the guiding principles and concepts of the HMI Philosophy and turns them into implementation examples and guidance. (This does HMI Philosophy, not include all technical details, Platform experience and expertise (to though the style guide needs to be confirm feasibility; develop early proof of feasible in all target platforms). concept designs). Generate all requirement graphical symbols and other supporting elements as required to implement th St the Style l G Guide. id
HMI Style Guide Document HMI Toolkit
HMI Toolkit
HMI Style Guide Document, Platform experience and expertise, Conceptual U User, T Task, k Functional F ti l Requirements. R i t 23
(Platformspecific). ifi )
DesignSteps
ConsoleDesign
Whathardwareandsoftwarewillbeinuse (thisisiterativewithrequirements)
HMISystemDesign
Useraccounts accounts,operatingsystems systems,toolkits toolkits, network,etc.
User,Task,FunctionalRequirements
Oncethebasicuserrolesand requirementsaredefined,theactualtasks tobeperformedbytheusersarecaptured, reviewedandpotentiallyoptimized.
DisplayDesign
Finally,theactualdisplays
24
User,Task,FunctionalRequirements
Avarietyofsimpleandmorecomplextechniquescanbe used:
HierarchicalTaskAnalysis
Acomprehensivelistofthetasksthatmakeupajoborfunctionare clustered l t d/grouped dt toshow h th therelationships l ti hi for f decision d i i making. ki
TimelineAnalysis
Tasksarebrokendownintoeventsandshownonachartoverthetime horizon.
LinkAnalysis
Demonstratesthefrequencyoflinkagebetweentasks.Usefulfor streamliningtasksandoptimizingdisplaycontent.
OthermoreadvancedtechniquessuchAbstractionHierarchical Analysis,CognitiveWorkAnalysisandEcologicalAnalysisexistbut may requireHumanFactorsEngineering(HFE)expertiseto complete.

25
DesignStage
Activity User, Task and Functional Requirements Objectives Identify primary and secondary requirements that must be supported in the HMI. Inputs HMI Phil Philosophy, h HMI St Style l Guide, Console Design, User, Task and Functional Requirements Analysis. User, , Task, , Functional Requirements. Control System Design Standards, Network Design Standards, Preliminary Network Design. Outputs Requirements document(s).
HMI System Design
Console Design
Display Design
.Identify design basis for the HMI system. T provide To id h hardware d and d software ft design for the Console. This includes .User, Task, Functional Requirements; Vendor furniture and supporting systems Specifications, Human Factors .Console design (phone, radio, LAN PC, cameras, etc.). Engineering Design Standards. documents. Identifies conceptual design for HMI Philosophy, HMI Style displays and the navigation hierarchy. (This may include some prototype Guide, User, Task, Functional displays on complex applications or Requirements document(s), Display design processes). User Input in Review(s). document(s). 26
HMI system design documents.
ImplementSteps
BuildDisplays
Yes,really,finally
BuildConsole
Thesystem y torunthemon
Test
Doesitwork?
Train
Makesureitreallyworks
Commission
Put P titto t work. k
Qualification
Extrapaperworkinsomeindustries.
27
ImplementStage
Activity Objectives Inputs Outputs Build Displays Complete construction of displays and supporting items. Complete construction of Build Console console hardware and software. Display design documents. Displays.
Test
Integrated Test of HMI and Console.
Train Train Users.
Console design documents. User, Task, Functional Requirements documents, Usability and performance standards standards. Console and Displays. HMI Philosophy, HMI Style Guide, Display design documents. Console and Displays.
Console HMI Ready to Commission Testing Commission, documents. Training materials, Training records, Trained Users. HMI Ready to Qualify (as required), Commissioning documents. Qualification documents, HMI Ready to Operate.
Commission
Final testing of HMI in Production Environment.
Console, Displays, User Manuals and Online Help (as required). Qualification Plan, Commissioning documents. 28
Qualification Verify HMI Ready to Operate.

OperateSteps
InService
Finally!
Maintain
E Errorfixes, fi tweaking t ki after ft patches t h to t maintainfunctionality
Decommission
Partialdecommissioningprobablythe mostrisky BUT, ,weg generally yfind~30%abandoned inplace0
29
OperateStage
Activity Objectives Inputs Commissioning/Qualification Approval, User Manuals and Online Help. Outputs
In Service HMI In Service.
HMI in Service.
Maintain
Ensure HMI is V lid and Valid dR Reflects fl t Current Process Conditions.
Approved Change Management t to t fix fi errors or to t add dd requests enhancements or updates to reflect changes in the process.
Management of Change L Logs, U Updated d t d HMI HMI, U User Manuals, Training Materials and Online Help. HMI (or part of HMI) removed from use, archived for approved records period.
HMI Removed from Service Decommission (End of Life).
Change Management Change Requests.
30
ContinuousWorkProcesses
MOC
Managementofchange(mainlyoutsidethescope)
Audit
Nokidding,thisshouldhappen
Validation
Formalstepsrequiredinsomeindustries
31
ContinuousWorkProcesses
Activity Objectives Manage change, ensuring consideration of all impacts. Inputs Changes in process or User, Task and Functional Requirements Outputs Change completed following the approved work practices Audit Records, Change q to Correct any y requests Deviations, Updates (as needed) to HMI Philosophy, HMI Style Guide HMI Toolkits and Guide, Related Documents Validation System, Validation Records
Management of Change (MOC)
Audit
Verify V if th that t the th HMI is being managed under the approved work practices
HMI Philosophy, HMI Style Guide, Related Documents
Validation
Verify HMI meets User, Task and Functional Requirements
Validation Plan
32
WhatelseisintheStandard?
HumanFactorsEngineering g g&Ergonomics, g , DisplayTypes, UserInteraction, Performance, Training.
33
HumanFactorsEngineering
Generalprinciples p p Operatorprocessinteractionmodel Usersensorylimits Usercognitivelimits
34
HMIoperationshouldbeintuitivetotheuser.
Relationshipofeachdisplayanditsfunctionalityshouldbecleartothe user.
TheHMIshouldsupporttasksrelatedtoallcommonly expectedmodesofoperation.
Nounnecessaryinformationorcontrols. Useseparatedisplaysforinformationrequiredonlyintermittently ForcomplextasksrequiringHMIinteraction,followthenormalwork flowindisplayoperationasmuchasispossible.
35
Presentinformationinformsorformatsthatareappropriate totheusersgoals. Controloptionsshouldincludethecommonlyexpectedrange ofuseractions. actions
Supportforallpotentialactionsshouldbeprovided,thoughnon routineactionscanbesupportedonseparatedisplays.
Itemssupportingthemostfrequenttasksshouldbereadily availabletotheuser.
Procedures andinstructionsusedtostartup papiece p ofequipment, q p ,or startabatchprocess.
36
SituationAwareness
Situationawarenessisdefinedas:
Therelationshipbetweentheoperator'sunderstandingoftheplant's conditionanditsactualconditionatanygiventime.
Thereareanumberofcommonfactorsthatundermine situationawareness,suchas:
Attentiontunneling. Shorttermmemorytrap. Workload,anxiety,fatigue,andotherstressors. Dataoverload.Overwhelming gamountsofdatacanreduceSA. Misplacedsalience. Complexitycreep.
37
Operator ProcessModel4
Reference/ Objective OperatorSubSystem Deviation Detect Diagnose Respond Action Process/ P / System Disturbance/ Malfunction
Measurement
Rememberthattheoperator p hastoDetect Diagnose g Respond. p ThenAssessiftheactionhasaddressedtheissue!
38
PerformanceShapingFactors
Detect
Operatorsexperience Trainingandexperience Fatigue Redundantcoding(e.g.color,shape&location) Alarmeffectiveness Detectionmechanisms Displayeffectiveness(howwellinformationisbeingpresented) Console, ,station, ,andscreenlayout y Environmentalfactors Displaydensity
39
Diagnose g
Console,station,andscreenlayout Displayorganizationandnavigation Displaylevels Trainingandexperience Directionprocessistrending Relianceonshorttermmemory Howwelltheoperatorsmentalmodelmapstotheprocess Displaycalluptimes Environmentalfactors Fatigue Displaychangetime
40
Respond p
OperatingProcedures Training Fatigue Operatormessaging HelpDisplay Expertsystems SystemResponsiveness Crew Environmentalfactors
41
Assess
Writetime Writerefreshtime ControlStrategy Operatorsmentalmodel Processresponsetime
42
UserSensoryLimits
Visualconsiderations
Ambientlightingandscreenluminance Color Informationdensity Visualdynamics(animation)
Auditoryconsiderations
Designbasics Considerationofpartialhearingimpairmentandlocalconditions
43
AWordonColor
Thechosencolorsshouldbedistinguishablefromeachother,generally involvingusabilitytesting. Asageneralrule,colorshouldbeusedforemphasizingkeyinformation suchasalarmsandabnormalconditions.
Colorsusedfordisplaydesignshouldbeconsistentwiththefacilitysalarm philosophy. Colorsusedforalarmpresentationshouldbereservedandnotusedforany otherpurposeinordertostrengthentheircognitivemeaningandspeedup operatorresponsetoalarms.
Thesalienceof colorsusedonadisplayshouldreflecttheimportanceof theinformationbeingpresented. presented
44
MoreWordsonColor
Colorcanbeusedforemphasisandclarity;however,coloraloneshould notbereliedupontoconveymeaning.
Colorgradientsshouldnotbeusedforstaticornondynamicelementsonthe display,butmaybeusedtohighlightadynamicelement.
Colorshouldbeusedconservativelyandconsistently. Colorperceptiondeficienciesandcolorcombinationsshouldbe consideredduringdesign. Colorand/orflashingofsymbolsshoulddirecttheoperatorsattentionto newlydevelopingsituations.
45
Colorblindness
SignificantIssue
Oneofthedriversforlesscolor Other,ofcourse,isusingcolorsparingly tomakeitactuallyMEANsomething InNorthAmericanOperatorpopulation canbeashighas30%
EasytoDesignAround
Needtoruntheanalyses Canoptimizethebackgroundcolorto getsomeoffset
46
46
CommonColorExamples
Normal
Protanopia
Deuteranopia
Tritanopia
47
47
OtherOptionsforValves
Hollow/Gray
Type Normal Protanopia Deuteranopia Tritanopia Color 450 401 403 400 Brightness 135 134 135 135
White/Green
T Type Normal Protanopia Deuteranopia Tritanopia C l Color 637 520 531 458 B i ht Brightness 180 149 161 157
Hollow/Green
Black/Green
48
PracticalAdvice
Thefancy yLPthatoptimizes p thecolorseparation p and optimizesthecolorshiftoffneutralforthebackgroundisall wellandgood,but
Thevideocardandmonitorhaveahugeimpact. impact Asdoestheambientlightinginthecontrolcenter. Checkthetheoryinreality!
49
AnEmbarrassingStory
Thereisnewresearchtosuggest gg thatthechromatic aberrationthatcomeswiththeagingoftheeye(lens yellowing)happensearlier.
Weusedtothinkonlytheretiredoldgeezershadanissue. issue
Iusedtothinkthattheolderoperatorswerewhiny,when theysaidthatcouldnotreallyseesomeofthebluePVson grayorthepurpleabnormalongray.

ButIamgettingolderandIcanseetheirpoint. Don Dont tgetmestartedaboutmynewbifocalseither!
50
AlarmColorsonGray
Normal
CRITICAL
Protanopia
CRITICAL
Deuteranopia
CRITICAL
Tritanopia
CRITICAL
WARNING1
WARNING1
WARNING1
WARNING1
WARNING2
WARNING2
WARNING2
WARNING2
WARNING3
WARNING3
WARNING3
WARNING3
ADVISORY SO
ADVISORY
ADVISORY
ADVISORY
ABNORMAL
ABNORMAL
ABNORMAL
ABNORMAL
51
AlarmColorsonTan
Normal
CRITICAL
Protanopia
CRITICAL
Deuteranopia
CRITICAL
Tritanopia
CRITICAL
WARNING1
WARNING1
WARNING1
WARNING1
WARNING2
WARNING2
WARNING2
WARNING2
WARNING3
WARNING3
WARNING3
WARNING3
ADVISORY
ADVISORY
ADVISORY
ADVISORY
ABNORMAL
ABNORMAL
ABNORMAL
ABNORMAL
52
Doesnt Doesn tHavetobeGray
53
53
UserCognitiveLimits
Ausersp performanceandtheunderlying y gcognitive g p processes areaffectedbytheworkloadlevel,situationawareness,and taskcompatibility. We W likely lik l know k this, thi but b titis i important i t tto t remember b th that t understress,cognitivelimitsareimpairedfromnormal.
54
CognitiveLimitConsiderations
Informationdisplayed p y indirectly yusableformat( (nomath!). ) Shouldnotrelyonrecallmemoryforcodesorcomplex commands. Usethesimplestdesignthatconsistentwithfunctionaland taskrequirements. Foritemsneededonlyintermittently intermittently,provideeasyaccess, access but donotclutterthemaindisplay. Useadesignthatfitstheusersmentalmodelofthesystem.
55
DisplayTypes&Styles
Display p ytypes yp definehowinformationisp presentedand organizedtoconveyinformationinaconsistentmanner. Displaystylesrefertohowtheinformationonasingledisplay i presented. is t d
56
SelectionofTypeofDisplay
Selectionmay ybeimpacted p by yfunctional, ,technological g and physicallimitationsoftheHMIused. Forexample: Positionofthedisplay, Physicalsizeofthescreen, Densityofinformationthatcanbehandledbytheuser. user
57
DisplayStyles
ListStyles y ProcessStyles OverviewStyles TopologyStyles GraphStyles HierarchicalStyles DashboardStyles LocationStyles y GroupStyle PointDetailDisplayStyle LogicMonitorStyles SequenceStyles ProcedureStyles Health/DiagnosticsStyles
58
PlanViewExample
59
PlanViewDrillDown
60
Fire&GasDisplays
Clearvisualdistinctionofconfirmedeventversussensor issue. Broadoverviewalwayscleartoshowanyescalation. Chattysensorsneedtobeclearlydepicted. Dotheengineeringefforttomaketheseeffectivetoolsinreal time. time
Consideranoffshoreplatform,wherethereisalsoaneedto understandthelevelsoftheplatform.
61
WasteWaterOperator Operators sFavorite
62
PlanViewMassiveFail
Thingsthatmattered:
Outfallpermits,mixofinstantaneousanddailytotals Disposalwellpermits Disposalwellsteadinessofpressureandflow Totalvolumeleftforwasteandrainwater,mixofvolumeandtimeatcurrent rates Bugsdyingornot,reactorsandtheoutfall
Eurekamomentofplanviewwithroadsandtanks
Fancyalarmgroupingsandeasydrilldownnavigation
Failedbecausethatwasnothowtheoperators p envisionedthep plant Movedtofunctionalgroupingoverview
63
ExampleFunctionalGrouping5
Boxesforareas Keycontrolsandindication Bestsymbols
64
AWordonDisplayHierarchy
Commonlyafourleveldisplayhierarchyisrecommendedtonotdiminish theoperatorsperformanceonmanagementactivities. Eachlevelisdefinedaccordingtothetypeandlocationofdisplayalong withtheinformationcontentofthedisplay. Informationcontentwillconveyincreasinglevelsofdetailandfocus,with Level1havingthebroadestscopeandLevel4havingthemostfocused scope. Althoughhierarchicalinnature,displaylevelsarenotnecessarilyaligned withanavigationhierarchywhichmayhavefewerormorelevels.
65
AFewThoughtsonNavigation
Thebestnavigation g depends p onthenatureofthep process andthelevelofinstrumentation. Oldersystemmaynothaveenoughinstrumentationto support tmultiple lti l levels l l of fd drill illdown. d
Particularlyiftheshutdownsystemisrelaybasedandverylimited troubleshootingbroughtintothesystem.
Level14isnottheonlyandmaynotbethebestconceptfor yourprocess
66
Navigation g NetworkDesigns g
Hierarchical Thisisthemostcommonly yusedstructure.
Inahierarchicalstructure,informationisorganizedlikeaninvertedtreein whichthelowerbranchesprovideincreasinglyspecificinformationrelatedto theupperbranchesandbackbone. Thereisextensiveresearchinhierarchicalstructuresandthedepthand breadthrecommended.
Relational Relationaldisplaynetworkstructureshave multiplelinksbetweennodes,whicharebasedonavarietyof relationships. Sequential Asequentialdisplaynetworkorganizesdisplay pagesinaseries.Thiscanbeeffectiveinbatchenvironments wheretheprocessflowssequentialthroughalogical structure.

67
67
UserInteraction
SoftwareMethods
Dataentrymethods, Navigationmethods, Erroravoidancemethods, Useraccesssecurity, Offsystemmessaging.
HardwareInterfaces
HMIDevices, Monitorsand UserInputDevices Devices.
68
UserInteractionDesign
Keydesignprinciplestoconsiderinclude:
consistencyinexecutionacrossallmodesofinteraction, timelyfeedbackfordataentryandcontrolactions, streamlineduserinteraction(minimizednumberof selectionsoramountoftyping), useof fappropriate i salience li for f errormessagesand dli limited i d useofcomplexmodalmethods.
69
DataEntryMethods
Consistentp presentationofdataentry. y
Commonconventionsinclude:insetentryfields,clearindicationofcurrent selection,grayeditemsthatarenotavailableforentry,andhandcursor presentation. Itisalsoeffectivetogivetheoperatorvisualcluesastotheformatofthe entryifthisisnotknown.
Informationispresentedinaconsistentmannerforalltypes ofinteractions.
Commonoperatorinteractionneedsshouldbecontainedonthedisplayorin apopuporfaceplatestyledisplaythatonlychangesaportionofthescreen. Theoperatorshouldonlyberequiredtochangescreensornavigatedeeper intotheHMIstructurefornonroutineandnoncriticalinteractions.
70
NumberPresentationandEntry
Thefontselectedshouldbediscernablefromthenormal operatorposition. Numberswithdecimalformattingshouldbejustifiedwith respect tto t the th decimal d i lpoint. i t Presentation P t ti should h ldfollow f ll the th appropriatedecimalformatresolutionrequiredbyusers.
Range g 100 - 9999.9 10 - 99.99 1 - 9.999 0 - 0.9999 Display p y Format XXXX XX.X X.XX X.XXX
Ifautomaticrescalingofthedecimalformatisused,care shouldbetakentosuppressrapidchangesindecimal formattingtoavoidrepetitiveshiftingofthedecimalpoint. point

71
CriticalOperatingRanges
Whereappropriate, pp p ,numbersshouldbereferencedtonormal andcriticaloperatingranges. Thereferencetonormalandcriticalcanbeaccomplishedina variety i t of fmanners,including i l di the th useof fanabnormal b lcolor l or referencecurvesandlines. Criticalvaluescanbereferencedinasimilarmanner, ,with clearindicationofimpendingoractualcriticalrange violations.
72
TextPresentationandEntry
Textshouldbeleftjustifiedwitharaggedrighthand edge.
MIXEDCASELETTERINGHASBEENSHOWNTOBEEASIERTOREADTHAN UPPERCASEANDSHOULDBEGENERALLYUSED. USED Ifaparagraphis required,the textwidth shouldbeat least50 characterswide forrapid scanning scanning.
73
Avoid hyphen ationif poss ible.
TextPresentationandEntry
Abbreviationsandacronymsshouldbeavoidedunlesstheyarepart of fth thenormal loperator t language. l Underliningforemphasisshouldnotbeused.Itisrecommended thatunderlinedtextbereservedforhyperlinks. Displayoftextshouldbeorientedhorizontallyunlessunavoidable orforclarity. Thefontselectedshouldhaveclearcharactersdefinition(themost commonissuerelatedtothepresentationof1,IandL). Affirmativestatementsratherthannegativestatementsshouldbe used. Activevoiceshouldbeemployed. p y Instructionsthatmustbeexecutedinordershouldbepresentedin order.
74
CommandEntry
Forsimple p commands, ,any yformatsupported pp by ythelanguage g g andtrainingoftheuserislikelytobeappropriate. Allinputstoandeffectsofagivencommandshouldbevisible t the to th userwhere h possible. ibl Usersshouldbeincommandoftheentryprocessatalltimes, withaclearmeansforcancelling gtheoperation p orrecovering g quicklytopriorconfiguration.
75
ComplexCommands
TheHMIshouldsupportmultipleselectionsbytheuser,followedby aconfirmation fi ti of fthe th i intended t d dcomposite it action. ti Ifselectionlistsarelong,artificialgroupingsshouldbeconstructed toallowforeasiernavigation,scanningandidentificationofdesired selection. selection Commanddialogsshouldbedesignedtosupporttheexpected workprocessoftheuser. Feedbackandhelpshouldbeprovidedforallcomplexsteps. Feedbackshouldbeprovidedforallentriesthatareoutsideofan expectedrange.
Ifaninputiscritical,acceptablelimitsonentryshouldbeenforced.
76
Buttons
Buttonsshouldbeusedonlywhensuitableforthetask. Labelsshouldbecleartotheusers. Buttonsshouldbesizedlargeenoughtoallowuserstoselect themrapidlyandaccuratelywiththepointingdeviceinuseon theconsole. Buttonsthatinteractdirectlywiththeprocessshouldbe distinctfrombuttonsthatprovidenavigationlinkagesor launchapplications. Anybuttonsthatareunavailableshouldindicatetheir temporaryunavailabilitywithconsistentvisualcoding.
77
Navigation g Methods
Thenavigation g design g isoneofthemostimportant p parts p of theoverallHMIdesign,sinceitdirectlyimpactsthespeed and accuracy withwhichtheoperatorcaninterveneandrespond toprocessneeds needs. Multiplenavigationmethodsshouldbeprovidedfor robustnessandtofacilitateaccesstodisplaysthatis: quick, logical, direct,and consistent.
78
78
Navigation g MethodExamples p
Navigationmethodstoconsiderinclude: EmbeddedHyperlinksandDisplaySymbolswithHyperlinks, MenusandToolBars/Ribbons, Dashboard/Taskpanel, panel Buttonsonthedisplays, Customkeyboardbuttons(functionandothercustombuttons), Context C Menu( (e.g.,mouseb buttonright i h clicks li k for f adrop d down d menu), ) Show/hidemechanismsfordetailedinformation, LinkstoDirectoriesofDisplays,FilesorTrends, DisplayTransferButtons, Voicecommands, Yoking. Yoking
79
79
Navigation g Guiding gPrinciples p

Displayaccessshouldbedesignedtominimizetheoperator keystrokeequivalentactions.
12keystrokesshouldbethemaximumrequiredtoviewanycriticalorhighpriority alarmincontextwiththeassociatedprocess. 23keystrokesareacceptableforallotherinformation.
Itshouldnotbenecessaryforanoperatortotypeinthe displaynameorpointidentification,thoughsupportforthat interactionshouldbeprovided.
80
80

TheHMImustsupportworkflowfornormalandabnormal conditions. Displaysymbolsthatarenavigationtargetshaveconsistent anddistinctvisualcoding. coding Displaysymbolsthatareselectablehaveconsistentand distinctvisualcoding.
81
81

Displays p y shouldbeimplemented p inastandardizedcontent structurethatsupportsprogressiveexposureofdetailed information. Where Wh useful f land dappropriate, i t advanced d dHMItechniques t h i can beemployedtoautomaticallydisplayrelevantinformation. Thisautomaticdisplay p yiscommonly ycalled"yoking" y g andcan includesuchitemsas:
otherdisplaysinamultiwindowHMI, faceplate, p , trending,and relateddetaileddisplays.
82
82
ExampleDisplayHierarchy
Level1
Overviewofoperatorsentirespanofresponsibility
Level2
Typicallytheoperatorsmaincontrolinterface Visibility b l of frelevant l alarms; l esp.high h hpriority
Level3
Detaileddisplays,usedfornonroutineoperations May M be b moret task kb based dfor f line li changes, h startup, t t etc. t Visibilityofallalarms
Level4
Rarelyusedfordiagnosticandtroubleshootingpurposes Interlockandpermissiveinformation(couldbeLevel3) Procedureandhelpdisplays(couldbeLevel3)
83
BatchNavigationExample
Plant Overview
Area Overview
Reactor1 Display
Reactor2 Display
Reactor3 Display
Reactor1 Trend
Reactor2 Trend
Reactor3 Trend
Reactor1 Alarms
Reactor2 Alarms
Reactor3 Alarms
84
MoreComplexNavigationExample
Navigate g horizontally yandvertically. y
85
ErrorAvoidanceMethods
Considerationshouldbeg giventoerroravoidancetechniques q andconfirmationstepsforimportantitems. Theitemsshouldbelimitedtoavoiddilutingtheimportance of fthe th method. th d Forsafetycriticalitems,theerroravoidanceshouldbe executedinthecontrolsystem y application pp itself, ,ratherthan theHMI.
TheStyleGuideshouldclearlydefineerroravoidanceandtheuseof customscriptingintheHMI. HMI
86
ErrorAvoidanceMethods
Theerroravoidancemethodsshouldnotexcessively hampertheoperatorsabilitytomakechangesrapidly, whereappropriate. Toavoidlossofeffectiveness,thesemethodsshouldbe usedsparinglyandbecarefullydesigned. Simpleconfirmationstepswithayestoconfirmhave beenshowntobesomewhatineffectiveatimproving accuracy.
Yes,yes,yes,yes.oops!
Itisalsoimportant p toensurethattheconfirmation employedisconsistentinlanguageandensurethatthe reasonfortheconfirmation,particularlywhenconfirming entriesoutsideofanexpectedrange.

87
OffSystemMessaging
Offsystem y messaging g gmethodsareusedtohelp ptheoperating p g teammanagetheprocess. Theseoffsystemmessagingmethodsinclude:
Autodialervoicemessages, Remotealarms, Pagers, Digitalmessagepagers, Textmessages, Emails. Emails
88
OffSystemMessaging
Careshouldbetakeninthedesign g ofthesesystems y toensure thatadequaterobustnessispresenttosupportthefunctional requirements. Ataminimum, i i the th systems t should h ldbe b automatically t ti ll monitoredforavailability. Inmorecriticalsystems, y ,abackup psystem y shouldbeinp placeto providetherequiredfunctionalityintheeventofanoutage.
89
UserAccessSecurity
TheHMIsystem y g generally yhassomelevelofHMIapplication pp specificsecurity. Theoperatorenvironmentisdesignedtoberesistanttousers d damaging i th theprogramsord data t present tonthat th tworkstation, k t ti orgainingaccesstounintendedapplications. Thedegree g ofrestrictionisoftenuserconfigurable, g ,sothat theHMIisalsosuitableforusebytrustedandhigherskilllevel users. This Thi scopedoes d notinclude i l d the h overall lluseraccount management,whichiscoveredbyANSI/ISA99.
90
UserAccessSecurity
HMIspecific p considerationsinclude:
TemporaryLogOver(abilitytoincreaseuserrightswithoutloggingoff completely)forspecifictasks, Conceptofmultiplerolesandprivilegeswithinanapplication(role basedrestriction), Locationbasedcontentrestriction, Useofelectronicsignatures, signatures Authenticationnotes(requirementofausertoaddareasonfora controlaction), Use U of fother h biometrics. bi i
91
Hardware:HMIDevices
Monitorscanvary yfromhandhelddevicestoindoorand outdoormonitorsofvaryingsizestolargerpostorwall mountedmonitors. Selection S l ti should h ldinclude i l d consideration id ti of fviewing i i angles l and d resolutionforcolorperceptionandreadability,physicalreach forinputdevices,andrelatedenvironmentalfactors. Whenafixedworkstationisdesired,someconsiderationof sittingandstandingoptionsshouldbemade. With Wi hportable bl d devices, i the h battery b lif lifeand druggedness d are likelytobekeyconsiderations.
Wirelessdeviceshavespecialsecurityandreliabilityconsiderationsthatare outsidethescopeofthisstandard(seeISA100).
92
DesignNotByFurnitureSalesRep
Keypoint,decidewhatyou need,thenpickthefurniture!
93
UserInputDevices
Considersounddesignforuseandselectionof:
Keyboards(QWERTYorotherindustrialtype), Keyboardswithprogrammablekeys, PointingDevices(mouse,trackball,etc.), Oth custom Other t k keyboards, b d Touchscreens, Videowallcontrols, Handwritinginputdevices devices, Voiceinput, Barcodescanners, RFIDs, Cameras, Pushbuttons/toggleswitches Others(biometricreadersforsecurity,etc.).
94
Performance
PerformancebyHMICategories HMIDutyFactors HMIPerformanceShapingFactors
95
HMICategories
Considerationinthestandardfor:
HighSpeedMachineControl SmallSystems ProcessSystems SCADA GeographicallyWidespreadRTUsystems
96
HMIDutyFactors
Maximum Times (all units in seconds unless otherwise stated) HMI Category Process System y 10 5 3 6 5 5-15 5 5 3 5 1 5-15 Metric Call-up Time (Note 1) Display Refresh Rate (Note 2) Display yp Type Level 1, 4 Level 2, 3 Faceplate Yoke Trend History Level 1, 4 Level 2, 3 Faceplate Yoke Trend History Applies to all display types Machine Control 2 1 1 6 5 5-15 1 1 1 1 1 5-15 Small System y 10 5 3 6 5 5-15 2 3 3 2 1 5-15 SCADA System y 10 5 3 6 5 5-15 5 5 3 5 1 5-15 RTU System y 10 5 3 6 5 5-15 5 5 3 5 1 5-15 Based on dial up schedule and bandwidth Based on network topology (i.e. (i e may have to dial a modem) <5 minutes for very large systems 1
Write Time
Applies to all display types Write Refresh Time (Note 3)
3 Access to alarm l displays Alarm summary Alarm lists such as suppressed alarms Critical displays Non-critical displays Alarm summary System diagnostics Switching operators Language change 1
5 1
5 1
5 1
Recommendedmaxtimesfor: CallupTime, DisplayRefreshRate, WriteTime,, WriteRefreshTime, Access toAlarms. Also considers: Navigation, Switchingusers, Changing language.
5 1-2 clicks 3 clicks 1 click 1-2 clicks 5 5
5 1-2 clicks 3 clicks 1 clicks 1-2 clicks 5 5
5 1-2 clicks 3 clicks 1 click 1-2 clicks 5 5
Navigation (Note 4)
System state changes (Note 5)
97
TheprinciplesbehindPerformanceShapingFactorsare:
controlsystemoperatordisplaysshouldbeaneffectivetoolforthe safeandefficientcontroloftheprocess,inbothnormalandabnormal situations, theHMIshouldassistintheearlydetection,diagnosis,andproper responsetoabnormalsituations, theHMIshouldbestructuredtoaidoperatortoprioritizeresponseto majorormultiplesimultaneoussystemupsets, the th HMIis i designed d i dfor f the th useof fthe th operator t in i running i the th process. ProperHMIdesignisthereforenotcompromisedforanyspecialuse purposesofmaintenance,engineering,staff,ortraining, failureofadisplayoritemsonthedisplayshouldbeimmediately apparenttotheoperator, aclear,butnotoverwhelming,indicationthatthegraphicisnot connectedtoorcommunicatingwiththesystemitislinkedto.
98
Training
UserTraining
Operations, Maintenance, Engineering, Administrators, Management.
Documentation
99
HMITraining
Adequatetrainingisabsolutelyessentialtosafeand effectiveoperationoftheHMI Materialsfortraining gshouldbeg generatedatthe DesignandImplementationStages gmaterialsshouldbeverifiedduring gthe Training TestingandCommissioningsteps Materialsshouldbeinaformatthatisconsistent withexistingproceduresandiseffectiveforthe audience
Paper,onlinehelptools,fullsimulation&testing
100
Documentation
ApplicationspecificdetailsofHMIimplementation, generatedduringDesignStage:
Displayindexes, Displayfunctionaldescriptions, Navigationdiagrams,etc.
TheinformationneededtoreconstructtheHMI applicationifnecessary.
101
ConcludingThoughts
Theresimplyisnosilverbullet.
Askhardquestionstoanyonethatsuggeststhatthereis
Wellconsideredandwellexecuted,theHMImaybethe h d engineering hardest i i that h youeverd do.
102
References
1. 2. 3. ISAS101Draft:ISA,May2012. USChemicalSafetyandHazardIdentificationBoard,InvestigationReportBP TexasCity,TXRefineryExplosionandFire,Report200504ITX,March2007. Fitzpatrick,B.A.(2005).Section4.11:Managementofabnormalconditions.InB. Liptak(Ed.),InstrumentEngineers'Handbook:ProcessControl (pp.706718). Stamford,CT:CRCPress. Swain,A.andGuttman,H.,HandbookofHumanReliabilityAnalysiswith E h i onNuclear Emphasis N l Power P Plant Pl Applications A li i (Fi (Final l R Report) ),Washington, W hi DC DC: UnitedStatesNuclearRegulatoryCommission,1983. Tharanathan,A.,Bullemur,P.,Laberge,J.,Reising,D.,Mclain,R.,Functional VersusSchematicOverviewDisplays: p y Impact p onOperator p SituationAwarenessin ProcessMonitoring,presentedat54thAnnualHFESMeeting,September2010.
4.
5.
103

ISA101 Hmiworkshop PDF

Încărcat de

Informații document

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

ISA101 Hmiworkshop PDF

Încărcat de

Drepturi de autor:

Formate disponibile

ISA101andHMIWorkshop

Bridgets Bridget sbackground

CelaneseAG, AG ~15 15years

Thepracticesinthisstandardareapplicabletocontinuous,batch,discrete processes,andanyprocessusinganHMIforinterfacingtoacontrolled system.

Integrators, Integrators Designers, Designers Engineers

Lesstime L ti t totrain t i users Lessoperatorerrorasaresultofconsistenteffectivedesign EasiertomovebetweenplatformsorversionsofanHMI Savestimeandmoney!

KeyDocuments Documents inSystemStandards

Provideafoundationofconceptssuchthatnewdevelopers anduserscangrasptheunderlyingprinciplesandtechnical rationales.

NeuralNetworks orOthers Models

Feedforward Control BasicLoop Control

Logic Blocks ControlScheme Monitoring

Field Fi ld(Local) L l) Controllers

HMI Phil Philosophy h Document

HMI Style S l Guide

HMI Style Guide Document HMI Toolkit

OthermoreadvancedtechniquessuchAbstractionHierarchical Analysis,CognitiveWorkAnalysisandEcologicalAnalysisexistbut may requireHumanFactorsEngineering(HFE)expertiseto complete.

HMI System Design

HMI system design documents.

Integrated Test of HMI and Console.

Train Train Users.

Final testing of HMI in Production Environment.

Qualification Verify HMI Ready to Operate.

In Service HMI In Service.

Ensure HMI is V lid and Valid dR Reflects fl t Current Process Conditions.

HMI Removed from Service Decommission (End of Life).

Change Management Change Requests.

Management of Change (MOC)

HMI Philosophy, HMI Style Guide, Related Documents

Verify HMI meets User, Task and Functional Requirements

Rememberthattheoperator p hastoDetect Diagnose g Respond. p ThenAssessiftheactionhasaddressedtheissue!

Thesalienceof colorsusedonadisplayshouldreflecttheimportanceof theinformationbeingpresented. presented

Colorshouldbeusedconservativelyandconsistently. Colorperceptiondeficienciesandcolorcombinationsshouldbe consideredduringdesign. Colorand/orflashingofsymbolsshoulddirecttheoperatorsattentionto newlydevelopingsituations.

Iusedtothinkthattheolderoperatorswerewhiny,when theysaidthatcouldnotreallyseesomeofthebluePVson grayorthepurpleabnormalongray.

Doesnt Doesn tHavetobeGray

WasteWaterOperator Operators sFavorite

Failedbecausethatwasnothowtheoperators p envisionedthep plant Movedtofunctionalgroupingoverview

Relational Relationaldisplaynetworkstructureshave multiplelinksbetweennodes,whicharebasedonavarietyof relationships. Sequential Asequentialdisplaynetworkorganizesdisplay pagesinaseries.Thiscanbeeffectiveinbatchenvironments wheretheprocessflowssequentialthroughalogical structure.

Ifautomaticrescalingofthedecimalformatisused,care shouldbetakentosuppressrapidchangesindecimal formattingtoavoidrepetitiveshiftingofthedecimalpoint. point

Avoid hyphen ationif poss ible.

Navigation g Guiding gPrinciples p

Itshouldnotbenecessaryforanoperatortotypeinthe displaynameorpointidentification,thoughsupportforthat interactionshouldbeprovided.

Navigation g Guiding gPrinciples p

Navigation g Guiding gPrinciples p

Itisalsoimportant p toensurethattheconfirmation employedisconsistentinlanguageandensurethatthe reasonfortheconfirmation,particularlywhenconfirming entriesoutsideofanexpectedrange.

Applies to all display types Write Refresh Time (Note 3)

5 1-2 clicks 3 clicks 1 click 1-2 clicks 5 5

5 1-2 clicks 3 clicks 1 clicks 1-2 clicks 5 5

5 1-2 clicks 3 clicks 1 clicks 1-2 clicks 5 5

5 1-2 clicks 3 clicks 1 click 1-2 clicks 5 5

5 1-2 clicks 3 clicks 1 clicks 1-2 clicks 5 5

System state changes (Note 5)

Wellconsideredandwellexecuted,theHMImaybethe h d engineering hardest i i that h youeverd do.

S-ar putea să vă placă și