Human Error Flashcards
human error
a failure to perform a task satisfactorily, and that failure cannot be attributed to factors beyond the human’s immediate control.human error is…78% of aircraft incidents b/w 1959-199556% b/t 1995 to 200452% of power plant root causes38% self-reported industrial accidents88% accidents cause by an individual worker70% of anaesthetic incidents by surgeon
error descriptions & goals & outcomes
phenomenological descriptions: what the error wasvs.psychological descriptions: information processing that leads to error (i.e., the underlying causes)goals:unintentional vs intentionale.g. error on a test vs. what speeds most of us drive• recovered: error with possibility for damage but none actually occurred (e.g., patientgiven overdose, but loses prescription)• unrecoverable: error where damage could not be avoided - recovered error could turn into unrecovered error tomorrow
human error categories
• error of commission: a person performs a task or step that should not have beenperformeda.k.a. type I error/false positive/false alarm e.g., hitting thumb with hammer• error of omission: a person fails to perform a task or step a.k.a. type II error/false negative/misse.g., forgetting to unplug coffeemaker• sequential error: a person performs a task or step out of sequence e.g., lighting a fire before opening fireplace flue damper• time error: a person performs a task or step, but too early, too late, or the wrong speed e.g., going through intersection on a red light• extraneous act: a person introduces some task or step that should not have been performed (action from an unrelated series)e.g., lighting a fire, then unplugging coffeemaker
types of failures
- based on where error originates• design error: designer does not take into account human abilities• manufacturing error: system not built according to design• installation/maintenance errors: system not installed or maintained correctly • operating error: system not operated according to intended procedure
errors of execution
• slip: unintentionally performing an incorrect action e.g., stepping on a banana peel and falling down - error of action execution• mode error: performing the correct response, but while in the wrong mode of operation; a kind of slipe.g., in paint software, attempting to draw something while using the eraser tool - error of attention/memory• lapse: neglecting to perform a required action e.g., forgetting to take your medicine twice a day-error of medicine
errors of intention
• mistake: selecting an action, and carrying it out successfully–but it is the wrongactione.g., smoking banana peels to try and get high- error of planning (choosing wrong decision-making rule, or lacking backgroundknowledge)- may be due to memory/perception/cognition• violation: intentionally contravening a standard (operating procedures, codes of practice, laws, etc.)- implies a (governing) social contexte.g., sabotage- is this necessarily an error?
complete analysis of error
- Describe system goals and functions2. Describe situation3. Describe tasks and jobs4. Analyze tasks for which errors are likely5. Estimate probability of each error6. Estimate probability that the error is not corrected7. Devise means to increase reliability (to decrease error)8. Repeat steps 4 - 7 in light of changes- different types of errors may need different types of actions to prevent them
error (as opposed to human error)
error: an action (or lack of action) that violates tolerance limit(s) of the system • defined in terms of system requirements and capabilities• doesn’t imply anything about humans; may be system flaw
Error Probability aka…
aka Human Error Probability (HEP): EP = (# of errors) ÷ (total # of opportunities for error)there are HEPs of specific actions found in tables, e.g.:• select wrong control in group of labeled identical controls = .003• failure to recognize incorrect status of item in front of operator = .01• turn control wrong direction, under stress, when design violates population norm = 0.5
Calculation of HEP: THERP (Swain, 1963)
- creating a fault tree analysis- start at top with probability of correct/incorrect action- next level: probability of error, given last action- these are conditional probabilities (are not independent)- sum of partial error probabilities at bottom is overall error probabilitye.g., starting a car• capital letter = correct outcome• lower case = error• conditional probability: p (b|a) means “the probability of b given a”K = correct keyk = incorrect keyS = getting key into ignition s = missing ignitionp (S|K) is probability of getting correct key into ignition (only correct outcome) p (error) = 1 - p (S|K)
reliability
probability of a successful outcome of the system or component • is also defined in terms of system requirements• thus, to evaluate a system we must know goal and purposes of the system R = (# of successful operations) ÷ (total # of operations)(also, R = 1 - EP)In general, reliability goes down as number of components goes up (i.e., as complexity increases).
components in a series
- in a series, if any component fails, the whole system fails(e.g., four tires on a car) Rs = R1 × R2 × … × Rne.g., all components have R = .90: n = 1: Rs = .90n = 2: Rs = .9 × .9 = .81n = 3: Rs = .9 × .9 × .9 = .73 n = 10: Rs = .910 = .35!!!
active redundancy
all components operate all the time, but only one is needed e.g., Boeing 767 can fly on only one enginee.g., traffic signals have multiple lightse.g., RAID level 1: data is mirrored across two hard drives- failure occurs only when both fail: (EP1) × (EP2)
how to improve reliability
- hardware factors:• KISS (Keep It Simple, Stupid)A-10 Thunderbolt II (“Warthog”) (1977): ~33% of air fleet unavailable at any timeF-111D Aardvark (first “glass cockpit,” 1967): ~__% unavailable AH-64D Apache Longbow (1998) helicopter gunship: similar record- human factors:• use human factors knowledge in design• use human as redundant system component (Human Reliability Analysis)
Human Factors Analysis and Classification System (HFACS): overview what is it
- HFACS is a comprehensive framework for understanding error, originally developed for the U.S. Navy and Marine Corps as an accident investigation and data analysis tool