ML19212A722

From kanterella
Revision as of 09:34, 5 September 2019 by StriderTol (talk | contribs) (Created page by program invented by StriderTol)
Jump to navigation Jump to search
04_01_Intro to HRA
ML19212A722
Person / Time
Issue date: 07/31/2019
From:
Office of Nuclear Regulatory Research
To:
D. Stroup 415-1649
Shared Package
ML19212A718 List:
References
Download: ML19212A722 (116)


Text

NRC-RES Fire PRA WorkshopModule IVAugust 5 -9, 2019Rockville, MDIntroduction to Human Reliability Analysis (HRA)

Introduction to HRASlide 2Fire PRA Workshop 2019, Rockville, MD ObjectivesIntroduce Human Reliability Analysis (HRA), in the context of PRA for nuclear power plants beforediscussing HRA in the context of Fire PRA.Provide students with a basic understanding of HRA:

-What is HRA?

-Where does HRA fit into PRA?

-What does HRA model?

-What are the keys to performing HRA?

-How can we understand human error?

-What guidance is there for performing HRA?

-What are the HRA concerns or issues for fire PRA?

-Is there a standard for performing HRA?

Introduction to HRASlide 3Fire PRA Workshop 2019, Rockville, MDIntroduction to HRA OutlineWhat is HRA?Where does HRA fit into PRA?What does HRA model?What are the keys to performing HRA?How can we understand human error?What guidance is there for performing HRA?What are the HRA concerns or issues for fire PRA?Is there a standard for performing HRA?Any final questions?

Introduction to HRASlide 4Fire PRA Workshop 2019, Rockville, MDHuman Reliability Analysis (HRA) -.Is generally defined as:

-A structured approachused to identifypotential human failure events (HFEs) and to systematically estimate the probabilityof those errors using data, models, or expert judgment Is developed because:

-PRA reflects the as

-built, as-operated plant

-HRA is needed to model the "as

-operated" portion (and cross-cuts many PRA tasks and products) Produces:-Identified and defined human failure events (HFEs)

-Qualitative evaluation of factors influencing human errors and successes-Human error probabilities (HEPs) for each HFE Introduction to HRASlide 5Fire PRA Workshop 2019, Rockville, MDHRA -. (continued)Requires inputs from many sources and technical disciplines, including:

-Plant information:Design information such as post

-initiating event behaviorEngineering (e.g., thermal hydraulics and room heat

-up calculations)Plant operations (procedures and how they are used)Plant hardware (ergonomics of monitoring and control interfaces, both inside and outside of the main control room)

-PRA model information:Accident progression following an initiating eventSystems and operator actions modeled in response

-HRA discipline

-cognitive and behavioral science

-Etc., etc., etc.Is performed by a multi

-disciplinary team Introduction to HRASlide 6Fire PRA Workshop 2019, Rockville, MDIntroduction to HRA OutlineWhat is HRA?Where does HRA fit into PRA?What does HRA model?What are the keys to performing HRA?How can we understand human error?What guidance is there for performing HRA?What are the HRA concerns or issues for fire PRA?Is there a standard for performing HRA?Any final questions?

Introduction to HRASlide 7Fire PRA Workshop 2019, Rockville, MDOverview of PRA ProcessPRAs are performed to find severe accident weaknesses and provide quantitative results to support decision

-making. Three levels of PRA have evolved:LevelAn Assessment of:Result 1Plant accident initiators and systems'/operators' responseCore damage frequency and contributors 2Reactor core melt, and frequency and modes of containment failureCategorization and frequencies of containment releases 3Public health consequencesEstimation of public and economic risks Introduction to HRASlide 8Fire PRA Workshop 2019, Rockville, MDPRA ClassificationInternal Hazards

-risk from accidents initiated internal to the plant-Includes internal events, internal flooding and internal fire eventsExternal Hazards

-risk from external events

-Includes seismic, external flooding, high winds and tornadoes, airplane crashes, lightning, hurricanes, etc.At-Power -accidents initiated while plant is critical and producing power (operating at >X%* power)Low Power and Shutdown (LP/SD)

-accidents initiated while plant is <X%* power or shutdown

-Shutdown includes hot and cold shutdown, mid

-loop operations, refueling*X is usually plant

-specific. The separation between full and low power is determined by evolutions during increases and decreases in power.

Introduction to HRASlide 9Fire PRA Workshop 2019, Rockville, MDPrincipal Steps in PRAAccident Sequence AnalysisRCS / ContainmentResponse AnalysisInitiating Event AnalysisAccident SequenceQuantif.Systems Analysis*Success CriteriaUncertainty

& Sensitivity AnalysisSource Term AnalysisRelease Category Character.

and Quantif.Offsite Conseq's AnalysisHealth & Economic Risk AnalysisData Analysis* Uncertainty

& Sensitivity AnalysisUncertainty

& Sensitivity AnalysisMeteorology ModelPopulation DistributionEmergency ResponsePathways ModelHealth EffectsEconomic EffectsLEVEL 1LEVEL 2LEVEL 3* Used in Level 2 as requiredLERF AssessmentHuman Reliability Analysis*Phenomena Analysis Introduction to HRASlide 10Fire PRA Workshop 2019, Rockville, MDPrincipal Steps in PRA (continued)First, we'll look at how HRA fits into Event Tree (ETs) models.

Introduction to HRASlide 11Fire PRA Workshop 2019, Rockville, MDHuman Events in Event TreesNature of event trees (and where HRA fits in)

Typically used to model the response to an initiating eventFeatures:-Generally, a unique system

-level event tree is developed for each initiating event group

-Identifies systems/functions required for mitigation

-Identifies operator actions required for mitigation

-Identifies event sequence progression

-End-to-end traceability of accident sequences leading to bad outcomePrimary use

-Identification of accident sequences which result in some outcome of interest (usually core damage and/or containment failure)

-Basis for accident sequence quantification Introduction to HRASlide 12Fire PRA Workshop 2019, Rockville, MDSimple Event Tree1. A2. AE -plant damage3. AC4. ACE -plant damage5. ACD -plant damage6. AB -transferInitiatingEvent AReactorProtectionSystem BEmergencyCoolantPump A CEmergencyCoolantPump B DPost-AccidentHeatRemoval ESuccessFailureSequence -End State/Plant Damage State Introduction to HRASlide 13Fire PRA Workshop 2019, Rockville, MDSystem-Level Event Tree Development A system-level event tree consists of an initiating event (one per tree), followed by a number of headings (top events), and sequences of events defined by success or failure of the top events Top events represent the systems, components, and/or human actions required to mitigate the initiating event To the extent possible, top events are ordered in the time-related sequence in which they would occur

-Selection of top events and ordering reflect emergency proceduresEach node (or branch point) below a top event represents the success or failure of the respective top event

-Logic is typically binary Downward branch

-failure of top eventUpward branch

-success of top event

-Logic can have more than two branches, with each branch representing a specific status of the top event Introduction to HRASlide 14Fire PRA Workshop 2019, Rockville, MDSystem-Level Event Tree Development (continued)Dependencies among systems (to prevent core damage) are identified

-Support systems can be included as top events to account for significant dependencies (e.g., diesel generator failure in station blackout event tree) Timing of important events (e.g., physical conditions leading to system failure) determined from thermal

-hydraulic (T

-H) calculationsBranches can be pruned logically to remove unnecessary combinations of system successes and failures

-This minimizes the total number of sequences that will be generated and eliminates illogical sequencesBranches can transfer to other event trees for developmentEach path of an event tree represents a potential scenarioEach potential scenario results in either prevention of core damage or onset of core damage (or a particular end state of interest)

Introduction to HRASlide 15Fire PRA Workshop 2019, Rockville, MDFunctional Event Tree IE RX-TR ST-CC LT-CCSEQ #STATE 1 2 3 4 OKLATE-CDEARLY-CDATWSInitiatingEventReactorTripShort termcore coolingLong termcore cooling Introduction to HRASlide 16Fire PRA Workshop 2019, Rockville, MDCritical Safety FunctionsExample safety functions for core and containment

-Reactor subcriticality

-Reactor coolant system overpressure protection

-Early core heat removal

-Late core heat removal

-Containment pressure suppression

-Containment heat removal

-Containment integrity Introduction to HRASlide 17Fire PRA Workshop 2019, Rockville, MDExample BWR Mitigating SystemsFunctionSystemsReactivity ControlReactor Protection System, Standby Liquid Control, Alternate Rod InsertionRCS Overpressure ProtectionSafety/Relief ValvesCoolant InjectionHigh Pressure Coolant Injection, High Pressure Core Spray, Reactor Core Isolation Cooling, Low Pressure Core Spray, Low Pressure Coolant Injection (RHR)Alternate Systems

-Control Rod Drive Hydraulic System, Condensate, Service Water, FirewaterDecay Heat RemovalPower Conversion System, Residual Heat Removal (RHR) modes (Shutdown Cooling, Containment Spray, Suppression Pool Cooling)

Introduction to HRASlide 18Fire PRA Workshop 2019, Rockville, MDExample PWR Mitigating SystemsFunctionSystemsReactivity ControlReactor Protection System (RPS)RCS Overpressure ProtectionSafety valves, pressurizer Power

-Operated Relief Valves (PORVs)Coolant InjectionAccumulators, High Pressure Safety Injection (HPSI), Chemical Volume and Control System (CVCS), Low Pressure Safety Injection (LPSI), High Pressure Recirculation (may require LPSI)Decay Heat RemovalPower Conversion System, Auxiliary Feedwater (AFW), Residual Heat Removal (RHR), Feed and Bleed (PORV + HPSI)

Introduction to HRASlide 19Fire PRA Workshop 2019, Rockville, MDSystem Success CriteriaIdentify systems which can perform each functionOften include if the system is automatically or manually actuated.Identify minimum complement of equipment necessary to perform function (often based on thermal/hydraulic calculations, source of uncertainty)

-Calculations often realistic, rather than conservativeMay credit non

-safety-related equipment where feasible Introduction to HRASlide 20Fire PRA Workshop 2019, Rockville, MDExample Success CriteriaIETransientMedium or Large LOCAReactorTripAuto Rx Tripor Manual Rx TripShort TermCoreCoolingPower ConversionSystem or1 of 3 AFWor 1 of 2 PORVsand 1 of 2 ECILong TermCoreCoolingPower ConversionSystem or1 of 3 AFW or1 of 2 PORVsand 1 of 2 ECR1 of 2 ECI1 of 2 ECRAuto Rx Tripor Manual Rx Trip Introduction to HRASlide 21Fire PRA Workshop 2019, Rockville, MDWhat does HRA do with ET information?For example, the HRA analyst:From initiating event and subsequent top events on ET:

-Identifies the procedures and procedure path that lead to successful mitigation of the initiating eventFrom success criteria:

-Determines what defines an operator failure (e.g., fewer pumps started than needed, actions performed too late in time)From plant behavior timing provided by T

-H calculations:

-Determines what plant parameters, alarms, and other indications are available to help operators:understand the plant state (initially and as the accident progresses) use procedures appropriately to respond to specific accident sequenceAny plant function

-related human failure events (HFEs) can be defined.

Introduction to HRASlide 22Fire PRA Workshop 2019, Rockville, MDWhat does HRA do with ET information?(continued)From the various branches on the event tree (combined with success criteria and timing information):

-Identifies (or confirms) what operator actions, if failed, could result in "down" branches and certain plant damage states (alone or in combination with system failures) (i.e., define an HFE)

-Identifies what specific operator actions (e.g., fails to start HPI Train A pump, turns off Safety Injection) would result in a "down" branch (i.e., define an HFE)

-Identifies what procedure paths might be plausibly taken that would result in operator failures

-Identifies what plant information (or missing information) might cause operators to take inappropriate procedure pathsThese inputs also can be as factors influencing the selection of screening valuesfor human failure events.

Introduction to HRASlide 23Fire PRA Workshop 2019, Rockville, MDPrincipal Steps in PRA (continued)Next, we'll see how HRA is included in Fault Tree (FT) models.

Introduction to HRASlide 24Fire PRA Workshop 2019, Rockville, MDHuman Events in Fault TreesCharacteristics of fault trees (and where HRA fits in)

Deductive analysis (event trees are inductive)Start with undesired event definitionUsed to estimate system failure probabilityExplicitly model multiple failuresIdentify ways by which a system can failModels can be used to find:

-System "weaknesses"

-System failure probability

-Interrelationships between fault events Introduction to HRASlide 25Fire PRA Workshop 2019, Rockville, MDHuman Events in Fault Trees (continued)Fault trees are graphic models depicting the various paths of combinations of faults that will result in the occurrence of the undesired top event.Fault tree development moves from the top event to the basic event (or faults) which can cause it.Fault tree consists of gates to develop the fault logic in the tree.Different types of gates are used to show the relationship of the input events to the higher output event.Fault tree analysis requires thorough knowledge of how the system operates and is maintained.

Introduction to HRASlide 26Fire PRA Workshop 2019, Rockville, MDSpecific Failure Modes Modeled for Each ComponentEach component associated with a specific set of failure modes/mechanisms determined by:

-Type of component (e.g., motor

-driven pump, air

-operated valve)-Normal/Standby stateNormally not running (standby), normally open

-Failed/Safe stateFailed if not running, or success requires valve to stay open Introduction to HRASlide 27Fire PRA Workshop 2019, Rockville, MDTypical Component Failure ModesActive Components

-Fail to Start*

-Fail to Run*

-Fail to Open/Close/Operate*Additional "failure mode" is component is unavailable because it is out for test or maintenance* In addition to hardware failures that have these failure modes, an operator "error of commission" (that suppresses actuation or operation, or turns off equipment) also can cause these failure modes.

Introduction to HRASlide 28Fire PRA Workshop 2019, Rockville, MDActive Components Require "Support"Signal needed to "actuate" component

-Safety Injection Signal starts pump or opens valveIf system is a "standby" system, operator action may be needed to actuate (and failure to actuate is modeled as an HFE)Support systems might be required for component to function-AC and/or DC power

-Service water or component water cooling

-Room cooling Introduction to HRASlide 29Fire PRA Workshop 2019, Rockville, MDPump segments failInjection lines failSuction lines fail PS-A failsMV1 fails closedMV3 fails closed PS-B failsV1 fails closedT1 failsECI fails to deliver

>1 pump flow MV2 fails closedSimplified Fault Tree for Failure of Emergency Coolant Injection (ECI)

Introduction to HRASlide 30Fire PRA Workshop 2019, Rockville, MDFault Tree SymbolsSymbol Description"OR" GateLogic gate providing a representation of the Boolean union of input events. The output will occur if at least one of the inputs occur."AND" GateLogic gate providing a representation of the Boolean intersection of input events. The output will occur if all of the inputs occur.Basic EventA basic component fault which requires no further development.Consistent with level of resolutionin databases of component faults.

Introduction to HRASlide 31Fire PRA Workshop 2019, Rockville, MDWhat does HRA do with FT information?From the top events and types of equipment modeled in the fault tree:

-Identify and define any human failure events (HFEs) that could result in system, train, or component failures (e.g., starting, actuating, opening/closing)From review of procedures and other documents related to testing and maintenance:

-Identify and define operator failures to restore systems, trains, or components following testing or maintenance

-Determine the frequency of testing and preventive maintenance

-Determine what post

-testing and post

-maintenance checks are performed These inputs also can be used in selecting appropriate screening values for HFEs.

Introduction to HRASlide 32Fire PRA Workshop 2019, Rockville, MDIntroduction to HRA OutlineWhat is HRA?Where does HRA fit into PRA?What does HRA model?What are the keys to performing HRA?How can we understand human error?What guidance is there for performing HRA?What are the HRA concerns or issues for fire PRA?Is there a standard for performing HRA?Any final questions?

Introduction to HRASlide 33Fire PRA Workshop 2019, Rockville, MDHuman Reliability AnalysisStarts with the basic premise that the humans can be represented as either:

-A component of a system, or

-A failure mode of a system or component. Identifies and quantifies the ways in which human actions initiate, propagate, or terminate accident sequences.Human actions with both positive and negative impacts are considered in striving for realism.A difficult task in a PRA since the HRA analyst needs to understand the plant hardware response, the operator response, the accident progression modeled in the PRA. Not everything the operator does is modeled in the PRA!

Introduction to HRASlide 34Fire PRA Workshop 2019, Rockville, MDHuman Reliability Analysis ObjectivesEnsure that the impacts of plant personnelactions are reflected in the assessment of risk in such a way that:

a)both pre-initiating event and post

-initiating eventactivities, including those modeled in support system initiating event fault trees, are addressed.

b)logic model elements are defined to represent the effect of such personnel actions on system availability/unavailability and on accident sequencedevelopment.

c)plant-specific and scenario

-specific factorsare accounted for, including those factors that influence either what activities are of interest or human performance.

d)human performance issues are addressed in an integral way so that issues of dependency are captured

.Ref. ASME RA

-Sa-2009 Introduction to HRASlide 35Fire PRA Workshop 2019, Rockville, MDCategories of Human Failure Events in PRAOperator actions can occur throughout the accident sequence:-Before the initiating event (i.e., pre

-initiator)

-As a cause of the initiating event

-After the initiating event (i.e., post

-initiator)

Introduction to HRASlide 36Fire PRA Workshop 2019, Rockville, MDCategories of Human Failure Events: Pre-Initiator HFEsSometimes called "latent errors" because they are not revealed until there is a demand for the affected system (after the initiating event).Examples:-Failure to restore valve lineup following routine system testing

-Failure to rack

-in pump breaker in following preventive maintenance

-Mis-calibration of instrumentsMost frequently relevant outside main control roomSome of these failures are captured in equipment failure data.For HRA, the focus is on equipment being left misaligned, unavailable, or not working exactly right (accounting for post

-test/post-maintenance verification).

Introduction to HRASlide 37Fire PRA Workshop 2019, Rockville, MDCategories of Human Failure Events: Initiating

-Event RelatedOperator actions can contribute to the occurrence of or cause initiating events (i.e., human

-induced initiators)In PRAs, such events are most often

-Included implicitly in the data used to quantify initiating event frequencies, and

-Therefore not modeled explicitly in the PRAOperator actions can be particularly relevant for operating conditions other than power operation

-Human-caused initiating events can have unique effects (e.g., causing drain

-down of reactor or RCS during shutdown)

-Actions that cause initiating events may also have implications for subsequent human response (i.e., dependence can be important)

Introduction to HRASlide 38Fire PRA Workshop 2019, Rockville, MDCategories Of Human Failure Events: Post-Initiator HFEsPost-initiator HFEs account for failures associated with response to an initiating eventTypically reflect failure to take necessary action (in main control room or locally)

-Failure to initiate function of manually

-actuated system

-Failure to back up an automatic action

-Failure to recover from other system failuresReconfigure system to overcome failures (e.g., align electrical bus to alternative feed)Make use of an alternative system (e.g., align fire water to provide pump cooling)Most often reflect failure to take actions called for by procedures Introduction to HRASlide 39Fire PRA Workshop 2019, Rockville, MDOther Classifications of Human Failure EventsAnother way to classify human failure events (HFEs) from the perspective of the PRA is:

-Error of omission (EOO)

-Error of commission (EOC)Errors of omission (EOOs):

-A human failure event resulting from a failure to take a required action, leading to an unchanged or inappropriately changed and degraded plant state.

-Examples: Failure to start auxiliary feedwater systemFailure to block automatic depressurization system signals Introduction to HRASlide 40Fire PRA Workshop 2019, Rockville, MDOther Classifications of HFEs (continued)Errors of commission (EOCs):

-A human failure event resulting from a well-intended but inappropriate, overt action that, when taken, leads to a change in the plant and results in a degraded plant state.

-Often, these events represent "good" operating practice, but applied to the wrong situation (especially, when understanding the situation is difficult).

-Examples:Prematurely terminating safety injection (because operators think SI is not needed; but for the specific situation, SI is needed).

Introduction to HRASlide 41Fire PRA Workshop 2019, Rockville, MDOther Classifications of HFEs (continued)Pre-initiator HFEs can be either EOOs or EOCs:

-These HFEs usually represent failures in execution (i.e., failures to accomplish the critical steps; these steps are typically already decided so no decision

-making is required).

-Executionfailures are often caused by inattention (or over

-attention) failures

-Examples:Inattention: Skipped steps (especially, following interruptions or other distractions)Over-attention: Repeated or reversed steps Introduction to HRASlide 42Fire PRA Workshop 2019, Rockville, MDOther Classifications of HFEs (continued)Most post-initiator HFEs that are modeled are EOOs:

-These HFEs can represent either failures in execution or cognitivefailures (such as failures in diagnosis of the plant condition or decision-making regarding procedure use for a particular situation).

-Most PRAs only include EOOs; however, EOCs have been involved in many significant accidents, both in nuclear power industry and others.-Later, we'll see that the fire PRA methodology for NFPA

-805 requires that certain EOCs be addressed.

Introduction to HRASlide 43Fire PRA Workshop 2019, Rockville, MDIntroduction to HRA OutlineWhat is HRA?Where does HRA fit into PRA?What does HRA model?What are the keys to performing HRA?How can we understand human error?What guidance is there for performing HRA?What are the HRA concerns or issues for fire PRA?Is there a standard for performing HRA?Any final questions?

Introduction to HRASlide 44Fire PRA Workshop 2019, Rockville, MDWhat are the keys to performing HRA?

Thekey is to-.

Introduction to HRASlide 45Fire PRA Workshop 2019, Rockville, MDWhat are the keys to performing HRA?-understand the problem.

Introduction to HRASlide 46Fire PRA Workshop 2019, Rockville, MDWhat are the keys to performing HRA?Whydo you need to "understand the problem"?

1.To be able to identify, define, and model (i.e., place appropriately in the plant logic model) HFEs such that they are consistent with, for example:the specific accident sequenceassociated plant procedures and operationsexpected plant behavior and indicationsengineering calculations that support the requirements for successful accident mitigationconsequences that are risk

-significant Introduction to HRASlide 47Fire PRA Workshop 2019, Rockville, MDWhat are the keys -? (continued) Whydo you need to "understand the problem"? (continued) 2.To appropriately select an HRA quantification method to (usually) indirectly represent how operators are expected to behave, based on, for example:their procedures and training plant-specific (and maybe even crew

-specific) styles for responding to accidents plant-specific operating experiencegeneral understanding of human error, behavior and cognitive science, human factors and ergonomicsknowledge of HRA methods and their underlying bases 3.To support and justify the HFEs and their quantification Introduction to HRASlide 48Fire PRA Workshop 2019, Rockville, MDWhat are the keys -? (continued)Howdo you develop this understanding?

-Perform an appropriately thorough qualitative analysis, performed iteratively and repeatedly throughout the entire HRA processuntil the final HRA quantification is done.How do you know when are you done?

-Usually, one or more of the following has occurred:The accident sequence analyst tells you that you should move on to a new problem/HFE (that is more risk

-significant).Your deadline has arrived.Your money is spent.

Introduction to HRASlide 49Fire PRA Workshop 2019, Rockville, MDWhat are the keys -? (continued)Increasingly, the HRA/PRA recognizes the importance of HRA qualitative analysis.More focus on qualitative analysis is appearing in recent or upcoming HRA/PRA guidance, e.g., -Joint EPRI/NRC

-RES Fire HRA guidance (NUREG

-1921/EPRI 1023001, July 2012)

-ATHEANA (NUREG

-1624, Rev. 1)

-EPRI's HRA CalculatorThis emphasis is supported or based on recent studies such as:-"International HRA Empirical Study

-Phase 1 Report" (NUREG/IA-0216, Volume 1, 2009)

Introduction to HRASlide 50Fire PRA Workshop 2019, Rockville, MDWhat are the keys to performing HRA?An important key to building an understanding of the problem is-Introduction to HRASlide 51Fire PRA Workshop 2019, Rockville, MDWhat are the keys to performing HRA?context.

Introduction to HRASlide 52Fire PRA Workshop 2019, Rockville, MDWhat are the keys to performing HRA?Contexthas long been recognized as important, e.g.,-SHARP1 (1992) discusses the importance of addressing human interactions for plant

-specific and accident sequence

-specific scenarios.However, a commonly held belief, still evident in popular accounts of incidents and reflected in how some people regard what new technologies ought to accomplish, is:

-If we could just eliminate the human, we'd never have any problems.This corresponds with the so

-called "blame culture" or "human

-as-a-hazard" view Introduction to HRASlide 53Fire PRA Workshop 2019, Rockville, MDWhat are the keys -? (continued)Of course, the "human" here is the one on the "sharp end," i.e., the last one to "touch" any equipment or try to respond to an accident.But, humans also are involved in design, planning, inspection, testing, manufacturing, software development, etc., etc., etc.Let's look at some everyday examples of what humans on the "sharp end" have to contend with as a way of understanding the impact of "context" and how we may be "set up" for failure.

Introduction to HRASlide 54Fire PRA Workshop 2019, Rockville, MDWhat are the keys to performing HRA?

Introduction to HRASlide 55Fire PRA Workshop 2019, Rockville, MDWhat are the keys to performing HRA?

Introduction to HRASlide 56Fire PRA Workshop 2019, Rockville, MDWhat are the keys to performing HRA?

Introduction to HRASlide 57Fire PRA Workshop 2019, Rockville, MDWhat are the keys - HRA? (continued)Recent research on human error and human actions involved in serious accidentshas contributed to building a new perspective on the role of humans in technology and the role of context.Examples of research/researchers include:

-James Reason, Human Error, 1990, Managing the Risks of Organizational Accidents, 1997, The Human Contribution: Unsafe Acts, Accidents and Heroic Recoveries, 2008, Organizational Accidents Revisited, 2015.-Donald R. Norman, The Design of Everyday Things, 1988.-E. M. Roth and R.J. Mumaw, An Empirical Investigation of Operator Performance in Cognitively Demanding Simulated Emergencies, NUREG/CR

-6208, 1994.

-Steven Casey, Set Phaserson Stun: And Other True Tales of Design, Technology, and Human Error, 1998.-Others, such as: Eric Hollnagel, David Woods, Micah Endsley Introduction to HRASlide 58Fire PRA Workshop 2019, Rockville, MDWhat are the keys -? (continued)Some of the key messages from this body of research are:-The operator is often "set

-up" for failure --by prior events, pre

-existing conditions, failed or misleading information, unusual and unfamiliar plant conditions and configurations, procedures that don't match the situation, and so on.

-But, he doesn't always fail--"[E]ven the best [trouble

-shooters] have bad days. It is my impression that the very best trouble

-shooters get it right about half the time. The rest of us do much worse." (Reason, The Human Contribution, page 66)

-So, he's the "last line of defense" --after all other previous designs and plans have failed.

Introduction to HRASlide 59Fire PRA Workshop 2019, Rockville, MDWhat are the keys -? (continued)Suggestions for some practical exercises on context 1.You want a book off the shelf in your living room. You even go to the living room to get the book. However, after you return to your home office, you discover that you never got the book.

2.You have a doctor's appointment. Despite reminding yourself of the location for the doctor's office while you drive away from home, you end up at your children's school instead.

3.You drive yourself to work every day on the same route, you have a good driving record, and you drive defensively. Somehow, you end up in a collision with another vehicle.All unlikely, right? Now, think about how the context might "cause" you to make one of these mistakes.

Introduction to HRASlide 60Fire PRA Workshop 2019, Rockville, MDWhat are the keys -? (continued)Suggestions for some practical exercises on context 1.In Reason's Human Error, the context was an interruption, namely knocking a bunch of books off the shelf. After picking up all the books, you forget why you were there in the first place.

2.I've done this. I got distracted by thinking about a work problem and/or was focused on the radio music. My "automatic pilot" kicked in and, instead of stopping at the doctor's office (~1 mile before the turnoff to the school), I did what I usually do 2x per day

-drove to the school. 3.This one is easy (i.e., lot of options for added context).

-Potential distractions, e.g.: Call coming in on the cell phone, passengers in car (Bring Your Child to Work Day?), etc.

-Added challenges, e.g.: Rain/ice/snow, fogged or iced up windows, road construction.

-Unexpected equipment problems, e.g.: "Fuel low" light comes on, run out of windshield washer fluid.

Introduction to HRASlide 61Fire PRA Workshop 2019, Rockville, MDIntroduction to HRA OutlineWhat is HRA?Where does HRA fit into PRA?What does HRA model?What are the keys to performing HRA?How can we understand human error?What guidance is there for performing HRA?What are the HRA concerns or issues for fire PRA?Is there a standard for performing HRA?Any final questions?

Introduction to HRASlide 62Fire PRA Workshop 2019, Rockville, MDHow can we understand human error?

Lesson 1:

Introduction to HRASlide 63Fire PRA Workshop 2019, Rockville, MDHow can we understand human error?Human error is not random.

Introduction to HRASlide 64Fire PRA Workshop 2019, Rockville, MDHow can we understand human error?But, why does human error seem random?Remember our exercise about context?-How many different possible contexts would you estimate can influence your everyday life?

-For the actions typically addressed by HRA, the range of contextshas been constrainedto:-Existing, licensed and operating nuclear power plants (NPPs)

-NPP accidents represented in Level 1, at

-power, internal events PRA-Actions taken by licensed operators

-Operator actions taken (mostly) in the control room (that has been extensively designed and redesigned, reviewed and re

-reviewed)-Operator actions that are addressed by Emergency Operating Procedures (EOPs) (that have been validated and demonstrated with decades of experience)

-Operator actions that are adequately trained

-Etc., etc., etc.

Introduction to HRASlide 65Fire PRA Workshop 2019, Rockville, MDHow can we understand human error?

Lesson 2:

Introduction to HRASlide 66Fire PRA Workshop 2019, Rockville, MDHow can we understand human error?Human error is not the "cause" of a mishap.

Introduction to HRASlide 67Fire PRA Workshop 2019, Rockville, MDHow can we understand human error?Remember-.

-The operator is often "set

-up" for failure --And, the operator is on the "sharp

-end" (i.e., simply the last one to touch "the problem").To illustrate this concept, here is Reason's Swiss Cheese model of event causation (1990 and 1997)

Introduction to HRASlide 68Fire PRA Workshop 2019, Rockville, MDThe 'Swiss Cheese' Model ofEvent CausationSome "holes" dueto active failuresOther "holes" due tolatent conditionsSuccessive layers of defenses, barriers, & safeguardsHazardsHarm Introduction to HRASlide 69Fire PRA Workshop 2019, Rockville, MDHow can we understand human error?

Lesson 3:

Introduction to HRASlide 70Fire PRA Workshop 2019, Rockville, MDHow can we understand human error?Human error can be predicted.

Introduction to HRASlide 71Fire PRA Workshop 2019, Rockville, MDHuman error can be predicted because-People's behavior is almost always rational

-adaptive -i.e., goals are achieved

-satisficing

-i.e., best under the circumstancesPeople's actions will tend to be

-practicalpeople do what "works"

-economicalpeople act so as to conserve resourcesAnd, in the case of NPPs, we have lots of rules and regulations to follow that are taken seriously; this further constrains likely behaviors and influences that HRA must model.

Introduction to HRASlide 72Fire PRA Workshop 2019, Rockville, MDHuman error can be predicted because-People follow familiar pathsMaximize use of habits (good andbad)Minimize 'cognitive strain'People use 'rapid pattern

-matching' to detect and interpret faults and errorsVery effective at detecting most problems, butNotvery effective at detecting our own errorsPeople also use-

-"shortcuts, heuristics, and expectation

-driven actions."

-efficiency

-thoroughness trade

-offs Introduction to HRASlide 73Fire PRA Workshop 2019, Rockville, MDPracticed actions become 'automatic'--whether we want them to or not.Human error' is not the cause of a mishap.

Introduction to HRASlide 74Fire PRA Workshop 2019, Rockville, MDHow can we understand human error?

Lesson 4:

Introduction to HRASlide 75Fire PRA Workshop 2019, Rockville, MDHow can we understand human error?By combining Lessons #1 through #3-Introduction to HRASlide 76Fire PRA Workshop 2019, Rockville, MDHow can we understand human error?Human errors are not isolated breakdowns, but rather are the result of the same processes that allow a system's normal functioning.

Introduction to HRASlide 77Fire PRA Workshop 2019, Rockville, MDHow can we understand human error- for HRA/PRA? First, previous PRA studies serves as guides for what types of operator actions are important to include in PRA models, what factors are the most important influences on operator performance, and so on.Second, HRA methods are developed principally for operators in NPPs; consequently, some basic understanding and expectations of NPP operator behavior, control room design, procedure use, operator training and education, etc. has been "built

-in" the methods.

Introduction to HRASlide 78Fire PRA Workshop 2019, Rockville, MDHow can we understand human error- for HRA/PRA? (continued)Third, HRA methods attempt to bridge the gap between the real operational experience in NPPs and psychology by:-filtering out behaviors, performance influences, and other factors that are not typically important for operator response to accident scenarios modeled in PRAs

-Providing the HRA analyst with a focused set of issues to address in NPP HRA/PRAFourth, the HRA analyst should perform qualitative HRA tasks (i.e., make plant

-specific assessments and observations of operator performance in order to identify which factors or issues are important for the specific plant and study).

Introduction to HRASlide 79Fire PRA Workshop 2019, Rockville, MDHow can we understand human error - for HRA/PRA? (continued)

  • As part of qualitative analysis, the HRA analyst further develops an understanding and ability to predict operator actions by addressing-The contextfor the operator acti on *The context includes both:

1.Plant/facility conditions, configuration, and behavior, and 2.Operator behavior influencing factors(sometimes called "performance shaping factors" (PSFs), performance influencing factors (PIFs), or driving factors)

Introduction to HRASlide 80Fire PRA Workshop 2019, Rockville, MDHow can we understand human error - for HRA/PRA? (continued)

  • Performance shaping factors usually capture important behavior-influencing aspects of, for example:

-Time available (often not defined as a PSF, but a veryimportant factor)

-Procedures

-Operator training

-Human-machine interfaces

-Action cues and other indications

-Crew staffing and organization

-Crew communicationThe important aspects of these factors can change with the plant/facility, NPP operation, operator action and location, etc.

Introduction to HRASlide 81Fire PRA Workshop 2019, Rockville, MDHow can we understand human error- for HRA/PRA? (continued)Then, the HRA analyst can match up the results of qualitative HRA with aspects of HRA quantification methods to predict whysuch potential operator failures might occur, e.g.,-Classifications, categories, or types of operator failures:Errors of omission and commission (dependent on the PRA model for definition)Slips/lapses, mistakes, and circumventionsSkill-, rule-, and knowledge

-based errors

-Explanations of operator failures using information processing models, e.g.,Failures in detection, situation assessment, response planning, and/or response execution

-Explanations of operator failures using a filtered set of "causes" (i.e., cause

-based models)

-Explanation of operator failures using performance shaping factors Introduction to HRASlide 82Fire PRA Workshop 2019, Rockville, MDHow can we understand human error- for HRA/PRA? (continued)Which approach for explaining operator failure do you use?-Dependson a variety of factors but, especially, the type of operation or action being modeled.

-Often helpful to use more than one way of classifying operator failure because different HRA quantification methods-Use different classification and categorization schemesEmphasize different PSFs, driving factors, or other elements of contextRepresent different types of operator actions, behavior models, and so forth

-Which approach helps to best explain why the HRA analyst thinks the operator might fail?

Introduction to HRASlide 83Fire PRA Workshop 2019, Rockville, MDHow can we understand human error?

  • So, it's important for an HRA analyst to do his best to
  • "Understand the problem" by understanding the context, operator actions and potential failures or errors, etc. (i.e., perform some HRA qualitative analysis

)*Match "the problem" to the HRA method that best represents the critical aspects of "the problem

  • In other words, HRA method selection is important and should be done after you have some "understanding of the problem," including the likely operator actions and potential operator failures ("errors").
  • In the next presentation topic, we'll provide resources for guidance on performing HRA, including the most common HRA processes and methods.

Introduction to HRASlide 84Fire PRA Workshop 2019, Rockville, MDIntroduction to HRA OutlineWhat is HRA?Where does HRA fit into PRA?What does HRA model?What are the keys to performing HRA?How can we understand human error?What guidance is there for performing HRA?What are the HRA concerns or issues for fire PRA?Is there a standard for performing HRA?Any final questions?

Introduction to HRASlide 85Fire PRA Workshop 2019, Rockville, MDHRA Guidance

-How To-. From our last presentation:

-Human error literature describes human behavior.

-Guidance, on the other hand, is a description of how-todo something-..In this presentation, we will discuss guidance for performing HRA associated with:

1.HRA processes 2.HRA quantification methods Introduction to HRASlide 86Fire PRA Workshop 2019, Rockville, MDHRA ProcessAn HRA process is a prescribed set of steps for how to perform an HRA that also identifies products of HRA, i.e., 1.Identification and definition of human failure events (HFEs), 2.Qualitative analysis that supports #1 and #2, and 3.Quantification of each HFE (i.e., assignment of human error probabilities (HEPs)),

4.Documentation of all of the above.Two examples of published stand-aloneHRA processes

-EPRI's " SHARP1

-A Revised Systematic Human Action Reliability Procedure," EPRI TR

-101711, December 1992

-NRC's "Good Practices for Implementing Human Reliability analysis (HRA)," NUREG

-1792, April 2005

  • "Stand-alone" means that they are not connected with a specific HRA quantification method.

Introduction to HRASlide 87Fire PRA Workshop 2019, Rockville, MD SHARP1Developed in 1980s as a "framework-for incorporating human interactions into PRA-" with emphasis on the iterative nature of the process.

-Structured in "stages" for systematically integrating HRA into the overall plant logic model of the PRA.

-Describes and compares selected HRA methods for quantification.SHARP1 uses three broad categories of human interactions:

-Type A: Pre

-initiating event interactions

-Type B: Initiating event interactions

-Type C: Post

-initiating event interactionsCP: Actions dictated by operating procedures and modeled as essential parts of the plant logic modelCR: Recovery actionsEmphasizes the importance of dependencies between human interactions (especially with respect to premature screening of important interactions) and defines four classes of dependencies.

Introduction to HRASlide 88Fire PRA Workshop 2019, Rockville, MDNRC's "Good Practices for HRA"Written to establish "good practices" for performing HRA and to assess the quality of HRA, when it is reviewed.Are generic in nature; not tied to any specific methods or tools.Written to support implementation of RG 1.200 for Level 1 and limited Level 2 internal event, at

-power PRAs (using direct links between elements of "good practices" and RG 1.200).Developed using the experience of NRC staff and its contractors, including lessons learned from developing HRA methods, performing HRAs, and reviewing HRAs.

Introduction to HRASlide 89Fire PRA Workshop 2019, Rockville, MDHRA Processes vs. MethodsNeither SHARP1 nor NRC's "Good Practices" specify or dictate which HRA method should be used to perform HRA quantificationSome resources provide both processes and methods:

-THERP (NUREG/CR

-1278)-ATHEANA (NUREG

-1624, Rev. 1)

-Fire HRA Guidelines (NUREG

-1921/EPRI TR 1023001)ATHEANA and the Fire HRA Guidelines provide:

-Approaches for identifying HFEs (e.g., EOCs)

-Techniques for doing certain aspects of qualitative HRA (e.g., determining if an operator action is feasibleand, therefore, suitable to be included in PRA)

Introduction to HRASlide 90Fire PRA Workshop 2019, Rockville, MDWhat are some common HRA methods?Technique for Human Error Rate Prediction (THERP)Accident Sequence Evaluation Program (ASEP) HRA Procedure-Simplification from THERPCause-Based Decision Tree Method (CBDTM) Human Cognitive Reliability (HCR)/Operator Reliability Experiments (ORE) MethodStandardized Plant Analysis Risk HRA (SPAR

-H) MethodA Technique for Human Event Analysis (ATHEANA)

Introduction to HRASlide 91Fire PRA Workshop 2019, Rockville, MDCharacteristics Addressed by HRA MethodsPlant behavior and conditions Timing of events and the time available for human action Locations of the human actionsEquipment available for use by the operators based on the sequenceIndications and cues used by the operators and changes in parameters as scenario proceedsEnvironmental conditionsRelevant training and experienceApplicability and usefulness of procedural or other guidance Introduction to HRASlide 92Fire PRA Workshop 2019, Rockville, MDFire HRA Guidelines (NUREG-1921/EPRI 1023001)First report addressing fire

-related HRA that goes beyond the screening level presented in NUREG/CR

-6850Provides a systematic process to identify and define fire HFEs, address fire

-specific PSFs, and assess HEPsStarted with existing Level 1 PRA/HRA practices, but evolved over time as fire HRA practitioners identified key differences in fire HRA and recommended strategies for addressing fire

-specific concernsContains 3 quantification methods developed for fire HRA, including a new Scoping approachProvides guidance for detailed fire HRA using specific methodsForms the basis for this training course Introduction to HRASlide 93Fire PRA Workshop 2019, Rockville, MDIntroduction to HRA OutlineWhat is HRA?Where does HRA fit into PRA?What does HRA model?What are the keys to performing HRA?How can we understand human error?What guidance is there for performing HRA?What are the HRA concerns or issues for fire PRA?Is there a standard for performing HRA?Any final questions?

Introduction to HRASlide 94Fire PRA Workshop 2019, Rockville, MDWhat are the HRA concerns or issues for fire PRA?

Introduction to HRASlide 95Fire PRA Workshop 2019, Rockville, MDWhat are the HRA concerns or issues for fire PRA?New operator actions to identify and model

-Fire response operator actions in fire procedures

-Strategy for the use in response to Fires Errors of Commission (EOCs) to identify, screen and define

-Per the Standard, the possibility that operators respond to spurious indications as if they are "real" must be considered.

-Screening provides a way to limit the number of EOCs modeled in the fire PRANew environmental hazards to model as Performance Shaping Factors (PSFs)

-Fire effects of smoke, heat, and toxic gases on operators, including transit paths

-Impact of breathing apparatus and protective gear on operator performance, including communications Introduction to HRASlide 96Fire PRA Workshop 2019, Rockville, MDWhat are the HRA concerns or issues for fire PRA? (continued)More challenging contexts

-Potentially wide variations in size, location, and duration of fires and their effects on plant systems and functionsDifferent types of operator actions

-More local actions

-Multiple tasks such as pulling fuses and then operate valve locallyOther PSFs or influencing factors

-Design of ex

-control room equipment control locations and alternate shutdown panelsBut, this, and more, will be addressed starting tomorrow.

Introduction to HRASlide 97Fire PRA Workshop 2019, Rockville, MDIntroduction to HRA OutlineWhat is HRA?Where does HRA fit into PRA?What does HRA model?What are the keys to performing HRA?How can we understand human error?What guidance is there for performing HRA?What are the HRA concerns or issues for fire PRA?Is there a standard for performing HRA?Any final questions?

Introduction to HRASlide 98Fire PRA Workshop 2019, Rockville, MDEndorsement and Guidance for PRAIn 1995, the U.S. Nuclear Regulatory Commission (NRC) issued a Policy Statement on the use of probabilistic risk analysis (PRA), encouraging its use in all regulatory matters.Regulatory Guide 1.200 issued in March 2009 is intended to be consistent with the NRC's PRA Policy Statement.It is also intended to reflect and endorse guidance provided by standards

-setting and nuclear industry organizations, such as the ASME/ANS PRA Standard (2009).

Introduction to HRASlide 99Fire PRA Workshop 2019, Rockville, MDNRC Regulatory Guide 1.200Title is "An Approach for Determining the Technical Adequacy Of Probabilistic Risk Assessment Results for Risk-informed Activities"Provides NRC staff position for one approach to determining technical adequacy of a PRA to support a risk-informed activityFor each technical element (e.g., HRA)

-Defines the necessary attributes and characteristics of a technically acceptable HRA

-Allows use of a standard in conjunction with a peer review to demonstrate conformance with staff position

-Endorses ASME/ANS standard and NEI peer review guidance (with some exceptions)

Introduction to HRASlide 100Fire PRA Workshop 2019, Rockville, MDRG 1.200 Tech Attributes and Characteristics for Level I HRA Introduction to HRASlide 101Fire PRA Workshop 2019, Rockville, MDRG 1.200 Tech Attributes and Characteristics for Fire HRA Introduction to HRASlide 102Fire PRA Workshop 2019, Rockville, MDReg Guide vs. StandardRG 1.200 scopes out what is needed in a technically acceptable PRA/HRA, and in some cases amplifies the PRA Standard requirementsASME/ANS PRA Standard defines requirements* for a quality PRA

-Specifies what you need to do.

-Requirements have been established to ensure PRA quality commensurate with the type of PRA application and/or regulatory decision

  • The use of the word "Requirements" is Standard language and is not meant to imply any regulatory requirement Introduction to HRASlide 103Fire PRA Workshop 2019, Rockville, MDASME/ANS RA

-Sa-2009Standard for Level 1/Large Early Release Frequency Probabilistic Risk Assessment for Nuclear Power Plant ApplicationsPart 2identifies Requirements for Internal Events At

-power PRAPart 4identifies Requirements for Fires At

-power PRAMany of the technical requirements in Part 2 are fundamental requirements for performing a PRA for any hazard groupFire PRA portion adds to and draws from Internal Events section, so have to satisfy elements from both Introduction to HRASlide 104Fire PRA Workshop 2019, Rockville, MDObjective (Paraphrased) from HRA Technical Element of ASME/ANS PRA StandardThe objective of the human reliability element of the PRA is to ensure that the impacts of plant personnel actions are reflected in the assessment of risk in such a way that:

-Both pre-initiating event and post

-initiating event activities addressed

-Logic model elements are defined to represent the effect of such personnel actions

-Plant-specific and scenario

-specific factors are accounted for

-Human performance issues are addressed in an integral way so that issues of dependency are captured Introduction to HRASlide 105Fire PRA Workshop 2019, Rockville, MDASME/ANS PRA StandardProvides two levels of technical requirements:

-High level requirements (HLRs)

-Supporting requirements (SRs)HLRs -provide minimum requirements for a technically acceptable baseline PRA.

-defined in general terms and reflect the diversity of approaches and accommodate future technological innovations.SRs define the requirements needed to accomplish each HLR Introduction to HRASlide 106Fire PRA Workshop 2019, Rockville, MDASME/ANS PRA Standard (continued)SR definitions acknowledge that, depending on the application, the level of detail, the level of plant specificity and the level of realism can varyThree capability categories are defined, and the degree to which each is met increases from Category I to Category IIIEach SR is defined to a different "Capability Category"Within a PRA, even the HRA element can be a mixture of capability categories.

Introduction to HRASlide 107Fire PRA Workshop 2019, Rockville, MDCapability Category DefinitionsCapability Category I:

-Scope and level of detail are sufficient to identify relative importance of contributorsdown to systemor trainlevel.-Generic data and models are sufficient except when unique design or operational features need to be addressed.

-Departures from realism

  • have moderateimpact on results.Capability Category II:

-Scope and level of detail are sufficient to identify relative importance of significant contributors down to componentlevel, including human actions

.-Plant-specific data and models are used for significant contributors

.-Departures from realism have smallimpact on results.*the degree to which the expected response of the plant is addressed Introduction to HRASlide 108Fire PRA Workshop 2019, Rockville, MDCapability Category Definitions (continued)Capability Category III:

-Scope and level of detail are sufficient to identify relative importance of contributorsdown to componentlevel, including human actions

.-Plant-specific data and models are used for allcontributors

.-Departures from realism have negligibleimpact on results.

Introduction to HRASlide 109Fire PRA Workshop 2019, Rockville, MDSRs May Differ Across Capability Categories Introduction to HRASlide 110Fire PRA Workshop 2019, Rockville, MDPRA Standard HLRs for Internal Events HRA (Part 2 Requirements)Pre-InitiatorPost Initiator HR-A Identify HFEs HR-E Identify HFEs HR-B Screen HFEs HR-C Define HFEs HR-F Define HFEs HR-D Assess HEPs HR-G Assess HEPs HR-H Recovery HFEs HR-I Document HFEs/HEPs Introduction to HRASlide 111Fire PRA Workshop 2019, Rockville, MDPRA Standard HLRs for Fire HRA (Part 4 Requirements)Post InitiatorRefers to Part 2 HRA-A Identify HFEs HR-E HRA-B Define HFEs (incorporate in PRA model)

HR-F HRA-C Assess HEPs HR-G HRA-D Recovery HFEs HR-H HRA-E Document HFEs/HEPs HR-I Introduction to HRASlide 112Fire PRA Workshop 2019, Rockville, MDExamples of ASME/ANS Standard Post

-Initiator HRA High Level Requirements (HLRs)HLR-HR-GThe assessment of the probabilities of the post

-initiator HFEs shall be performed using a well defined and self-consistent process that addresses the plant

-specific and scenario

-specific influences on human performance, and addresses potential dependencies between human failure events in the same accident sequence. HLR-HR-HRecovery actions (at the cutset or scenario level) shall be modeled only if it has been demonstrated that the action is plausible and feasible for those scenarios to which they are applied. Estimates of probabilities of failure shall address dependency on prior human failures in the scenario.

Introduction to HRASlide 113Fire PRA Workshop 2019, Rockville, MDExample of ASME/ANS Standard Post

-Initiator HRA Supporting Requirement (SR)HR-G1-Capability Category I: Use conservative estimates (e.g., screening values) for the HEPs of the HFEs in accident sequences that survive initial quantification.

-Capability Category II: Perform detailed analyses for the estimation of HEPs for risk

-significant HFEs.Use screening values for HEPs for non

-risk-significant human failure basic events.

-Capability Category III: Perform detailed analyses for the estimation of all human failure basic events.

Introduction to HRASlide 114Fire PRA Workshop 2019, Rockville, MDMeeting RG and Standard RequirementsPeer Reviews are conducted to evaluate the degree to which a PRA has met the RG and Standard requirementsFindings and Observations (F&Os) are written where deficiencies are found

-It is expected that these F&Os be addressed before a Licensee Amendment Request (LAR) is submitted for NFPA 805 transitionFire PRA/Fire HRA task interfaces are important to address for technical adequacy and standard compliance

-One could apply a different HRA method, for example, a screening HEP during the quantification of a detailed Fire PRA scenario.

-In this case, the overall quantification may be acceptable (e.g., PRA Standard Capability Category I), or it may lead to further refinement if best-estimate results (e.g., PRA Standard Capability Category II) are needed.

Introduction to HRASlide 115Fire PRA Workshop 2019, Rockville, MDGuidance from NUREG

-1921 and this CourseNUREG-1921 Fire HRA Guidelines provides assistance (but no guarantee) in meeting the PRA Standard, with emphasis on Capability Category IITable 2-1 identifies Fire PRA/Fire HRA task interfaces by PRA Standard element such as accident sequence analysis [AS] or quantification [QU] Appendix D correlates PRA Standard sections to Guidelines sections and provides a roadmap for users to perform an assessment of their own fire HRA against the PRA Standard requirementsThe Fire HRA Track presented this week will identify key HLRs and SRs in performing fire HRA/PRA.

Introduction to HRASlide 116Fire PRA Workshop 2019, Rockville, MDIntroduction to HRA OutlineWhat is HRA?Where does HRA fit into PRA?What does HRA model?What are the keys to performing HRA?How can we understand human error?What guidance is there for performing HRA?What are the HRA concerns or issues for fire PRA?Is there a standard for performing HRA?Any final questions?