06.10.2020 Views

atw - International Journal for Nuclear Power | 10.2020

Description Ever since its first issue in 1956, the atw – International Journal for Nuclear Power has been a publisher of specialist articles, background reports, interviews and news about developments and trends from all important sectors of nuclear energy, nuclear technology and the energy industry. Internationally current and competent, the professional journal atw is a valuable source of information. www.nucmag.com

Description

Ever since its first issue in 1956, the atw – International Journal for Nuclear Power has been a publisher of specialist articles, background reports, interviews and news about developments and trends from all important sectors of nuclear energy, nuclear technology and the energy industry. Internationally current and competent, the professional journal atw is a valuable source of information.

www.nucmag.com

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

<strong>atw</strong> Vol. 65 (2020) | Issue 10 ı October<br />

ENVIRONMENT AND SAFETY 500<br />

2.5 Procedure<br />

Be<strong>for</strong>e crews started their first<br />

scenario, they were introduced to the<br />

ISV, they provided written consent not<br />

to give any in<strong>for</strong>mation on scenarios<br />

to anyone not involved during the day.<br />

The crews then practiced handling the<br />

tablet computers: They filled in the<br />

questionnaires assessing the situation<br />

awareness and coordination on a<br />

test basis and practiced the workload<br />

rating. The tablet computers were<br />

then taken to the work places of the<br />

operators.<br />

In each trial be<strong>for</strong>e the simulation<br />

was started, all crew members were<br />

provided with two sheets. The first<br />

contained all in<strong>for</strong>mation on the<br />

starting conditions <strong>for</strong> the scenario,<br />

such as actual nuclear power and<br />

unavailable components. The second<br />

sheet was provided <strong>for</strong> notes concerning<br />

any occurring inconsistencies<br />

during the subsequent trial, e.g. in the<br />

OM or on displays.<br />

The simulation started when the<br />

operators had settled in at their work<br />

places. The trial then followed the<br />

predefined target path.<br />

Workload was assessed every<br />

20 minutes using the operators’ tablet<br />

computers at the work stations.<br />

For each scenario at three predetermined<br />

moments the simulation<br />

was briefly stopped. During these<br />

“freezes” the crews had to take their<br />

tablets and leave the FSS <strong>for</strong> about<br />

10 minutes. In an adjacent room,<br />

the tablet computers were used to<br />

collect data on situation awareness<br />

and coordination. After the freezes,<br />

the operators went back to their<br />

workplaces and the simulation was<br />

resumed.<br />

The trials ended at predefined<br />

DIMs or plant states. After each trial, a<br />

systematic debriefing was carried out<br />

in the FSS, in which the test crews<br />

were asked about specific behavioural<br />

patterns and give their feedback<br />

on any inconsistencies concerning<br />

the OM or other system parts. The<br />

debriefing then continued without<br />

the operators to initially evaluate<br />

task per<strong>for</strong>mance and human error<br />

together with all observers.<br />

3 Measurement<br />

of variables<br />

3.1 Task per<strong>for</strong>mance<br />

Task per<strong>for</strong>mance was the primary<br />

evaluation aspect. It considered the<br />

correctness and completeness with<br />

which the shift crews fulfilled their<br />

tasks. To determine the task per<strong>for</strong>mance,<br />

global success criteria (which<br />

were valid <strong>for</strong> all scenarios), scenario<br />

specific success criteria and task per<strong>for</strong>mance<br />

key nodes were defined.<br />

Success criteria<br />

At the end of a scenario it was evaluated<br />

whether the following three<br />

global success criteria were met:<br />

(1) no un<strong>for</strong>eseen escalation of<br />

the scenario, (2) no damage of major<br />

equipment during the scenario,<br />

(3) and no relevant delay during<br />

the scenario should be caused by<br />

behaviour of the crew. In addition,<br />

three to five scenario specific success<br />

criteria were defined <strong>for</strong> each scenario.<br />

Task per<strong>for</strong>mance key nodes<br />

Furthermore, four to eight critical<br />

points or decisions in the process were<br />

identified (‘key nodes’) <strong>for</strong> each<br />

scenario to evaluate the task per<strong>for</strong>mance.<br />

The expected behaviour at<br />

these key nodes was predefined.<br />

An example of a key node and<br />

related scenario specific success<br />

criteria: During scenario B, an alarm<br />

occurred at a seal of a reactor coolant<br />

pump (RCP). The crew was expected<br />

to make the decision to manually shut<br />

down the RCP be<strong>for</strong>e an automatic<br />

shutdown occurred. The task per<strong>for</strong>mance<br />

key node here is “manual<br />

trip of the RCP”. The two scenario<br />

specific success criteria associated<br />

with this problem are “After trip<br />

of reactor coolant pump: start<br />

decreasing the power to 0 %” and<br />

“No attempt to restart the RCP”.<br />

The generic assessment questions<br />

as to task per<strong>for</strong>mance were:<br />

p Does the crew behave as expected<br />

at the task per<strong>for</strong>mance key nodes?<br />

p Are pre-defined scenario-specific<br />

success criteria reached?<br />

p Are the global success criteria<br />

reached?<br />

Data collection was done during the<br />

simulator sessions by observers <strong>for</strong><br />

key node per<strong>for</strong>mance criteria and<br />

after the session during debriefing <strong>for</strong><br />

scenario-specific and global success<br />

criteria. Data collection was done by<br />

operational experts and by human<br />

factors experts. If one of the success<br />

criteria was not met, the scenario trial<br />

was considered failed.<br />

3.2 Human error<br />

Based on a phenotype-oriented<br />

approach of human errors, errors of<br />

omission and errors of commission<br />

were identified based on direct observation<br />

of the operators' be haviours<br />

and related to the predefined target<br />

path <strong>for</strong> the scenario. If an operator deliberately<br />

deviates from specifications,<br />

e.g. from the OM, then this is not<br />

evaluated as an error, but as a deviation<br />

(and thus a topic of task per<strong>for</strong>mance<br />

and not of human error). Beside the<br />

occurrence of errors, we observed<br />

whether the errors were detected by<br />

the operators and whether they were<br />

corrected. If an error was discovered<br />

and corrected in due time, it was not<br />

used <strong>for</strong> the evaluation of the pass/fail<br />

criteria.<br />

If errors occurred that were not<br />

detected and not corrected, the<br />

severity of these errors was classified<br />

by the validation team as high,<br />

medium, or low. The impact of each<br />

error was evaluated case by case,<br />

with focus on the probability of<br />

con sequences be<strong>for</strong>e the error was<br />

detected and corrected, and the<br />

consequences of the error on plant<br />

safety and integrity.<br />

No errors with high severity<br />

should have been left undetected and<br />

uncorrected by the shift team. The<br />

amount of errors with medium and<br />

low severity, which were not detected<br />

and not corrected had to be evaluated<br />

by the validation team if it was<br />

acceptable. For the evaluation of<br />

acceptability, the length of a scenario,<br />

the number of tasks and the type of<br />

operating procedure (NOP, AOP, EOP)<br />

had to be taken into account.<br />

3.3 Situation awareness<br />

In safety research, the concept of<br />

situation awareness was developed to<br />

describe the adequate understanding<br />

of the present state and the <strong>for</strong>eseeable<br />

future as a prerequisite <strong>for</strong> any<br />

safe operation. Its assessment is either<br />

focused on an individual’s situation<br />

awareness or on the shared situation<br />

awareness between two or more<br />

agents, from which one can anticipate<br />

important future states. For the<br />

ISV, the concept of shared situation<br />

awareness was adopted, meaning that<br />

situation awareness was ensured as<br />

soon as at least one member of the<br />

crew was aware of the present state<br />

and was able to act accordingly. To<br />

assess situation awareness, a multimethod<br />

approach was adopted:<br />

Method 1 – SAGAT<br />

A comprehensive and well-established<br />

method <strong>for</strong> the assessment is the<br />

Situation Awareness Global Assessment<br />

Technique (SAGAT) [5] which<br />

allows <strong>for</strong> a real-time assessment by<br />

freezing a simulated environment and<br />

in the freeze ask agents about their<br />

understanding of the situation.<br />

After the questioning, the answers<br />

obtained in the test are compared<br />

Environment and Safety<br />

Are They Ready <strong>for</strong> Operation? How to Assess the Control Room System of a New NPP ı Rainer Miller, Rodney Leitner, Sina Gierig and Harald Kolrep

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!