Analysis Techniques For Man-Machine Systems Design
Analysis Techniques For Man-Machine Systems Design Analysis Techniques For Man-Machine Systems Design
NATO UNCLASSIFIEDAC/243(Panel 8)TR/7 - 88 -Volume 2on the measurement of subjective workload to verify that system performance requirements will be met. As noted inVolume 1, detailed considerations of the use of prototyping, simulation and field trials are outside the scope of thisreview. The links between analytical techniques and other approaches are discussed where possible.human tasks & task sequences,pacing times &events. & performance requirements4 -task tasks associate with high/ow tmes or erormanceanalysisredictinpf noperatoreoper \ act ignsequene \ acins \ tms/ features/Of tsks \ dictated by byh/diaeytaskF inputs & R a the between operato macoutputs, timesd o inte rface ad wo pormace d ifrequencies,\\ //performancerequirements6 -A variety of approaches are -available -to predict operator performance analytically (Meister. 1985). Most of them usethe concept of operator "workload" rather than a measure of performance itself (Hart & Wickens, 1990). Someestablished techniques such as the time Line analysis of workload (5.1) are normative, based on a single task analysissequence. Network simulations of operator tasks, such as PERT. SAINT and MicroSAINT (5.2) can be madestochastic so that the external mission events, and the task times and sequences, are drawn from a distribution oftimes and probabilities. Network simulations can link workload to system performance because they can produceestimates of task success in terms of percentage of tasks completed. or time to complete, using models of humanperformance, as well as producing estimates of operator workload (Chubb, Laughery & Pritsker, 1987). NATOAC/243 Panel 8/RSG.9 has reviewed and reported on those techniques and on a variety of models of humanperformance (McMillan et al., 1989, 1991). One specific approach, SIMWAM (5.3) is included here, because of theextensive use made of it for weapon systems development.Performance predictions can also be made using subjective workload measurement techniques (5.4). For example,although the SWAT technique (5.5) was developed for the evaluation of an existing, or simulated, system, it can beapplied pomjecavely (Pa-SWAT) to the prediction of operator workload based on a task analysis. The NASA TaskLoad Index (TLX) (5.6) can be applied projectively also.In following either a simulation modelling approach or a subjective workload approach to predicting operatorperformance, it must be remembered that the relationship between workload and performance is not straightforward.As task demands vary with time, the operators may increase or decrease their effort to compensate, or their effort maydecline due to fatigue (Fig. 5.2). Thus at the outset of a mission, the task demand may lie within an operator'sNATO UNCLASSIFIED- 88 -
NATO UNCLASSIFIED- 89 - AC/243(Panel-8)TR/7Volume 21 iniscapability, whereas at the end of a mission, the same level of task demand may exceed the operator's capability. Hart& Wickens,.(1990) discuss the Performance Resource Functions (PRF) which relate workload, performance, andoperator effort in different situations.-AC c v ~pilot capability-0.;efell tactical fligh ,en-routetransittake-offapproach & landingmission task demandsTime -At point A, pilot capability exceecs mission task demands by 25%At point B. pilot capability barely exceeds same level of task demandsFigure 5.2: Example of the relationship between mission task demandsand operator capability (after Tepper & Haakanson, 1978);e Error analysis is another aspect of performance prediction. A variety of approaches have been taken to error analysis(Lepiat et al., 1990; Rasmussen, Duncan & Lcplac, 1987). Some approaches use fault tree analysis or failure modeseffects analysis to identify those operator actions which could result in a system-critical incident or situaion. TheTechnique for Human Error Prediction (THERP) reviewed by NATO AC/243 Panel-8/RSG.9 (McMillan et al.,1991), is the most well known example. Other approaches attempt to identify design features which are associatedwith human error. In that context, many of the established human engineering design recommendations are intendedto control "design induced error." Woodson (1981) provides examples of lists of quantitative and qualitativeapproaches to analysing designs for human error. It should be noted, however, that the whole subject of operator erroris a contentious one. There are many problems with the definition and classification of human error. For example,error is context dependent and accident and incident analysis require value judgements to be made (Ridley, 1991).Because of such problems, only a simple generic approach to error analysis based on actual application is reviewedhere (5.7). The prediction of human error requires a data base for associated probabilities of occurrence. An approachwhich has been applied to the collection of data from accidents is also reviewed (5.8).IyNATO UNCLASSIFIED- 99 -
- Page 152 and 153: NATO UNCLASSIFIEDAC/243(Panel 8)TR/
- Page 154 and 155: NATO UNCLASSIFIEDA-AC/243(Panel 8)T
- Page 156 and 157: NATO UNCI ASSIFIEDC/-43(Panel 8)TR/
- Page 158 and 159: NATO UNCLAS.SIFIEDAC/243(Panel 8)TR
- Page 160 and 161: NATO UNCLASSIFIED 2AC/243(Panei 8)T
- Page 162 and 163: NATO UNCLASSIFIEDAC/243(Panel 8')TR
- Page 164 and 165: NATO UNCLASSIFIEDAC/243(Panel 8)TR/
- Page 166 and 167: NATO UNCLASSIFIEDAC/243(Panel 8)TR/
- Page 168 and 169: NATO UNCLASSIFTEDAC/243(Panel 8)TR/
- Page 170 and 171: NATO UNCLASSIFIEDAC/243(Panel 8)TR/
- Page 172 and 173: NATO UNCLASSIFIEDAC/243(Panel 8 TR/
- Page 174 and 175: NATO UNCLASSIFIEDAC/24 3 (6PanelVol
- Page 176 and 177: NATO UNCLASSIFIEDAC/243(Panel 8)TR/
- Page 178 and 179: NATO UNCLASSIFIEDAC/243(Panel 8'tTR
- Page 180 and 181: N ATO UNCLASSIFIEDAC/243(Panel 8')T
- Page 182 and 183: NATO UNCLASShi Ih I t LUAC/243(Pane
- Page 184 and 185: NATO UNCLASSIFIED,AC/243(Panel 8 TR
- Page 186 and 187: NATO UNCLASSIFIEDAC/243(Panel 8)TR/
- Page 188 and 189: NATO UNCLASSIFTEDAC/243(Panel 8')TR
- Page 190 and 191: NATO UNCLASSIFIEDAC/243(Panel 8')TR
- Page 192 and 193: NATO UNCLASSIFIEDAC/243(Panel 8)TR/
- Page 194 and 195: NATO UNCLASSIFIEDAC/243(Panel 8)TR/
- Page 196 and 197: NATO UNCLASSIFIEDAC/243(Panel 8')TR
- Page 198 and 199: NATO UNCLASSIFIEDAC/243(Panel 8ITR/
- Page 200 and 201: NATO UNCLASSIFIUEUAC/243(Panel 8)TR
- Page 204 and 205: NATO UNCLASSIFIEDAC/243(Panel 8)TR/
- Page 206 and 207: t NATO UNCLASSIFlEDAC/243(Panel 8)T
- Page 208 and 209: NATO UNoCLASSIFIEDAC/243(Panel 8)TR
- Page 210 and 211: NATO UNCLASSIFIEDAC/243(Panel 8)TR/
- Page 212 and 213: NATO UNCLASSIFIEDAC/243(Panel 8)TR/
- Page 214 and 215: NATO UN CL A S SIFIEDAC/243(Panel 8
- Page 216 and 217: NATO UNCLAS.SIFI.EDAC/243(Panei 8Vo
- Page 218 and 219: NATO UNCLASSIFIEDAC/243(Panel 8)TR/
- Page 220 and 221: fl1106AC/243(Panel 8'TR/7- 106Volum
- Page 222 and 223: NATO UNCLASSIFIED -AC/243(Panel 8)T
- Page 224 and 225: .N AI U N C L A Itt110iAC/243(Panel
- Page 226 and 227: NATO UNCLASSIFIEDAC/243(Panel 8)TR/
- Page 228 and 229: NATO UNCLASSIFIEDAC/243(Panel 8)TR/
- Page 230 and 231: NATO UNCLASSIFIEDAC/243(Panel 8)TR/
- Page 232 and 233: NATO UNCLASSIFIEDAC/243(Panel 8)TR/
- Page 234 and 235: ] NATO UNCLASSIFIEDAC/243(Panel 8)T
- Page 236 and 237: VNATO UNCLASSIFIED;-AC/243(Panel 8'
- Page 238 and 239: NATO UNCLASSIFIED1111wAC/243(Panel
- Page 240 and 241: NATO UNCLASSIFIEDAC/243(Panel 8)TR/
- Page 242 and 243: NATO UNCLASSIFIEDAC/ 24 3 (Pane l 8
- Page 244 and 245: NATo I UNCLASSIFEDAC/243(Panel 8'IT
- Page 246 and 247: NATO ITNCLASSIUI:EDAC/243(panel 81T
- Page 248 and 249: NATO U.NCLASSIFIEDAC/243(Panel 8)TR
- Page 250 and 251: NATO INCLASSIFIEDAC/243(Panel- 8LTR
NATO UNCLASSIFIED- 89 - AC/243(Panel-8)TR/7Volume 21 iniscapability, whereas at the end of a mission, the same level of task demand may exceed the operator's capability. Hart& Wickens,.(1990) discuss the Performance Resource Functions (PRF) which relate workload, performance, andoperator effort in different situations.-AC c v ~pilot capability-0.;efell tactical fligh ,en-routetransittake-offapproach & landingmission task demandsTime -At point A, pilot capability exceecs mission task demands by 25%At point B. pilot capability barely exceeds same level of task demandsFigure 5.2: Example of the relationship between mission task demandsand operator capability (after Tepper & Haakanson, 1978);e Error analysis is another aspect of performance prediction. A variety of approaches have been taken to error analysis(Lepiat et al., 1990; Rasmussen, Duncan & Lcplac, 1987). Some approaches use fault tree analysis or failure modeseffects analysis to identify those operator actions which could result in a system-critical incident or situaion. TheTechnique for Human Error Prediction (THERP) reviewed by NATO AC/243 Panel-8/RSG.9 (McMillan et al.,1991), is the most well known example. Other approaches attempt to identify design features which are associatedwith human error. In that context, many of the established human engineering design recommendations are intendedto control "design induced error." Woodson (1981) provides examples of lists of quantitative and qualitativeapproaches to analysing designs for human error. It should be noted, however, that the whole subject of operator erroris a contentious one. There are many problems with the definition and classification of human error. <strong>For</strong> example,error is context dependent and accident and incident analysis require value judgements to be made (Ridley, 1991).Because of such problems, only a simple generic approach to error analysis based on actual application is reviewedhere (5.7). The prediction of human error requires a data base for associated probabilities of occurrence. An approachwhich has been applied to the collection of data from accidents is also reviewed (5.8).IyNATO UNCLASSIFIED- 99 -