ML22355A649

From kanterella
Jump to navigation Jump to search

NRC Comments on Draft Licensee-Developed Operating Test (Folder 2)
ML22355A649
Person / Time
Site: FitzPatrick Constellation icon.png
Issue date: 08/30/2021
From: Brian Fuller
Operations Branch I
To: Kelly D
Exelon FitzPatrick
References
EPID L-2021-OLL-0000
Download: ML22355A649 (1)


Text

ES-301 Operating Test Review Worksheet Form ES-301-7 Facility: Exam Date:

1 2

3 Attributes 4

Job Content 5

6 Admin JPMs ADMIN Topic and K/A LOD (1-5)

U/E/S Explanation I/C Cues Critical Scope Overlap Perf.

Key Minutia Job Link Focus Steps (N/B)

Std.

RO COO1 Perform Post Accident Monitoring Instrument Channel Check K/A 2.1.45 (4.3),

3 E

Pre-filled 2 additional values in student handout RO COO2 Manually Compute Average Drywell Air Temperature K/A 2.1.20 (4.6) 3 E

Edited initiating cue RO EC Determine Tagout Boundary For RBCLC Pump Work K/A 2.2.13 (4.1) 3 S

RO EP Conduct Emergency Announcement And Site Evacuation K/A 2.4.43 (3.2) 3 X

E Made 2 steps non-critical and truncated JPM SRO COO1 Review Post Accident Monitoring Instrument Channel Check K/A 2.1.45 (4.3),

3 E

Added detail to JPM step 4 and fixed one value in student handout

ES-301 Operating Test Review Worksheet Form ES-301-7 SRO COO2 Manually Compute Average Drywell Air Temperature, Determine Technical Specification Implications K/A 2.1.20 (4.6) 3 E

Edited initiating cue SRO EC Perform Technical Specification Evaluation and LCO Tracking for Inoperable Turbine Bypass Valves K/A 2.2.22 (4.7) 3 E

Made minor editorial changes SRO RC Determine Visitor RCA Access Requirements K/A 2.3.4 (3.7),

3 E

Clarified which portions of one step are critical and non-critical SRO EP Determine Emergency Classification and Initiate Event Notification K/A 2.4.40 (4.5),

3 S

1 Simulator/In-Plant Safety Function and K/A JPMs A

9 K/A 261000 A4.06 (3.3/3.6) 3 E

Edited initiating cue, added examiner note, added detail to one pair of steps B

4 K/A 245000 A4.06 (2.7/2.6) 3 E

Added evaluator note to one step C

6 K/A 264000 A4.04 (3.7/3.7) 3 E

Added 10 second delay to malfunction and added examiner note

ES-301 Operating Test Review Worksheet Form ES-301-7 D

7 K/A 212000 A4.14 (3.8/3.8) 3 S

E 2 K/A 206000 A4.05 (4.4/4.4) 3 E

Removed failure of high level trip F

1 K/A 201002 A4.01 (3.5/3.5) 3 E

Fixed IC and added 2 examiner notes G

5 K/A 226001 A4.03 (3.5/3.4) 3 S

H 8 K/A 400000 A4.01 (3.1/3.0) 3 S

I 1 K/A 201001 A2.04 (3.8/3.9) 3 S

J 8 K/A 286000 K1.09 (3.2/3.3) 3 S

K 5 K/A 223001 A2.01 (4.3/4.4) 3 E

Added note to ensure additional attachment given to candidates

ES-301 4

Form ES-301-7 Instructions for Completing This Table:

Check or mark any item(s) requiring a comment and explain the issue in the space provided using the guide below.

1.

Check each JPM for appropriate administrative topic requirements (COO, EC, Rad, and EP) or safety function requirements and corresponding K/A. Mark in column 1.

(ES-301, D.3 and D.4)

2.

Determine the level of difficulty (LOD) using an established 1-5 rating scale. Levels 1 and 5 represent an inappropriate (low or high) discriminatory level for the license that is being tested. Mark in column 2 (Appendix D, C.1.f)

3.

In column 3, Attributes, check the appropriate box when an attribute is not met:

The initial conditions and/or initiating cue is clear to ensure the operator understands the task and how to begin. (Appendix C, B.4)

The JPM contains appropriate cues that clearly indicate when they should be provided to the examinee. Cues are objective and not leading. (Appendix C, D.1)

All critical steps (elements) are properly identified.

The scope of the task is not too narrow (N) or too broad (B).

Excessive overlap does not occur with other parts of the operating test or written examination. (ES-301, D.1.a, and ES-301, D.2.a)

The task performance standard clearly describes the expected outcome (i.e., end state). Each performance step identifies a standard for successful completion of the step.

A valid marked up key was provided (e.g., graph interpretation, initialed steps for handouts).

4.

For column 4, Job Content, check the appropriate box if the job content flaw does not meet the following elements:

Topics are linked to the job content (e.g., not a disguised task, task required in real job).

The JPM has meaningful performance requirements that will provide a legitimate basis for evaluating the applicant's understanding and ability to safely operate the plant. (ES-301, D.2.c)

5.

Based on the reviewers judgment, is the JPM as written (U)nacceptable (requiring repair or replacement), in need of (E)nhancement, or (S)atisfactory? Mark the answer in column 5.

6.

In column 6, provide a brief description of any (U)nacceptable or (E)nhancement rating from column 5.

Save initial review comments and detail subsequent comment resolution so that each exam-bound JPM is marked by a (S)atisfactory resolution on this form.

ES-301 5

Form ES-301-7 Facility: Scenario: 1 Exam Date:

1 2

3 4

5 6

7 8

9 10 Event Realism/Cred.

Required Actions Verifiable actions LOD TS CTs Scen.

Overlap U/E/S Explanation 1

S 2

S 3

X S

4 S

5 X

S 6

X S

7 X

S 8

S

ES-301 6

Form ES-301-7 Facility: Scenario: 2 Exam Date:

1 2

3 4

5 6

7 8

9 10 Event Realism/Cred.

Required Actions Verifiable actions LOD TS CTs Scen.

Overlap U/E/S Explanation 1

E Swapped order of events 1 and 2 2

E Swapped order of events 1 and 2 3

X S

4 X

S 5

S 6

S 7

XX S

8 S

Facility: Scenario: 3 Exam Date:

1 2

3 4

5 6

7 8

9 10 Event Realism/Cred.

Required Actions Verifiable actions LOD TS CTs Scen.

Overlap U/E/S Explanation 1

S 2

S 3

S 4

X S

5 X

S 6

X S

7 X

S 8

S

ES-301 7

Form ES-301-7 Scenario 4 1

2 3

4 5

6 7

8 9

10 Explanation Event Realism/Cred.

Required Actions Verifiable actions LOD TS CTs Scen.

Overlap U/E/S 1

E Added examiner notes to event 1 2

3 X

E Added examiner notes to event 3 4

X E

Added examiner notes to event 4 5

X 6

X 7

ES-301 8

Form ES-301-7 Instructions for Completing This Table:

Use this table for each scenario for evaluation.

2 Check this box if the events are not related (e.g., seismic event followed by a pipe rupture) OR if the events do not obey the laws of physics and thermodynamics.

3, 4 In columns 3 and 4, check the box if there is no verifiable or required action, as applicable. Examples of required actions are as follows: (ES-301, D.5f) opening, closing, and throttling valves starting and stopping equipment raising and lowering level, flow, and pressure making decisions and giving directions acknowledging or verifying key alarms and automatic actions (Uncomplicated events that require no operator action beyond this should not be included on the operating test unless they are necessary to set the stage for subsequent events. (Appendix D, B.3).)

5 Check this box if the level of difficulty is not appropriate.

6 Check this box if the event has a TS.

7 Check this box if the event has a critical task (CT). If the same CT covers more than one event, check the event where the CT started only.

8 Check this box if the event overlaps with another event on any of the last two NRC examinations. (Appendix D, C.1.f) 9 Based on the reviewers judgment, is the event as written (U)nacceptable (requiring repair or replacement), in need of (E)nhancement, or (S)atisfactory? Mark the answer in column 9.

10 Record any explanations of the events here.

In the shaded boxes, sum the number of check marks in each column.

In column 1, sum the number of events.

In columns 2-4, record the total number of check marks for each column.

In column 5, based on the reviewer's judgement, place a checkmark only if the scenario's LOD is not appropriate.

In column 6, TS are required to be 2 for each scenario. (ES-301, D.5.d)

In column 7, preidentified CTs should be 2 for each scenario. (Appendix D; ES-301, D.5.d; ES-301-4)

In column 8, record the number of events not used on the two previous NRC initial licensing exams. A scenario is considered unsatisfactory if there is < 2 new events. (ES-301, D.5.b; Appendix D, C.1.f)

In column 9, record whether the scenario as written (U)nacceptable, in need of (E)nhancement, or (S)atisfactory from column 11 of the simulator scenario table.

ES-301 9

Form ES-301-7 Facility: Exam Date:

Scenario 1

2 3

4 5

6 7

8 11 Event Totals Events Unsat.

TS Total TS Unsat.

CT Total CT Unsat.

% Unsat.

Scenario Elements U/E/S Explanation 1

8 0

2 0

2 0

0 S

2 8

0 2

0 2

0 0

S 3

8 0

2 0

2 0

0 S

4 7

0 2

0 2

0 0

S Instructions for Completing This Table:

Check or mark any item(s) requiring comment and explain the issue in the space provided.

1, 3, 5 For each simulator scenario, enter the total number of events (column 1), TS entries/actions (column 3), and CTs (column 5).

This number should match the respective scenario from the event-based scenario tables (the sum from columns 1, 6, and 7, respectively).

2, 4, 6 For each simulator scenario, evaluate each event, TS, and CT as (S)atisfactory, (E)nhance, or (U)nsatisfactory based on the following criteria:

a.

Events. Each event is described on a Form ES-D-2, including all switch manipulations, pertinent alarms, and verifiable actions. Event actions are balanced between at-the-controls and balance-of-plant applicants during the scenario. All event-related attributes on Form ES-301-4 are met. Enter the total number of unsatisfactory events in column 2.

b.

TS. A scenario includes at least two TS entries/actions across at least two different events. TS entries and actions are detailed on Form ES-D-2. Enter the total number of unsatisfactory TS entries/actions in column 4. (ES-301, D.5d)

c.

CT. Check that a scenario includes at least two preidentified CTs. This criterion is a target quantitative attribute, not an absolute minimum requirement. Check that each CT is explicitly bounded on Form ES-D-2 with measurable performance standards (see Appendix D). Enter the total number of unsatisfactory CTs in column 6.

7 In column 7, calculate the percentage of unsatisfactory scenario elements:

8 If the value in column 7 is > 20%, mark the scenario as (U)nsatisfactory in column 8. If column 7 is 20%, annotate with (E)nhancement or (S)atisfactory.

9 In column 9, explain each unsatisfactory event, TS, and CT. Editorial comments can also be added here.

Save initial review comments and detail subsequent comment resolution so that each exam-bound scenario is marked by a (S)atisfactory resolution on this form.

2 + 4 + 6 1 + 3 + 5100%

ES-301 10 Form ES-301-7 Site name: Exam Date:

OPERATING TEST TOTALS Total Total Unsat.

Total Total Unsat.

Explanation Edits Sat.

Admin.

JPMs 9

0 7

9 Sim./In-Plant JPMs 11 0

6 11 Scenarios 4

0 5

4 Op. Test Totals:

0 Instructions for Completing This Table:

Update data for this table from quality reviews and totals in the previous tables and then calculate the percentage of total items that are unsatisfactory and give an explanation in the space provided.

1.

Enter the total number of items submitted for the operating test in the Total column. For example, if nine administrative JPMs were submitted, enter 9 in the Total items column for administrative JPMs.

For scenarios, enter the total number of simulator scenarios.

2.

Enter the total number of (U)nsatisfactory JPMs and scenarios from the two JPMs column 5 and simulator scenarios column 8 in the previous tables. Provide an explanation in the space provided.

3.

Enter totals for (E)nhancements needed and (S)atisfactory JPMs and scenarios from the previous tables. This task is for tracking only.

4.

Total each column and enter the amounts in the Op. Test Totals row.

5.

Calculate the percentage of the operating test that is (U)nsatisfactory (Op. Test Total Unsat.)/(Op. Test Total) and place this value in the bolded % Unsat. cell.

Refer to ES-501, E.3.a, to rate the overall operating test as follows:

  • satisfactory, if the Op. Test Total % Unsat. is 20%
  • unsatisfactory, if Op. Test Total % Unsat. is > 20%
6.

Update this table and the tables above with post-exam changes if the as-administered operating test required content changes, including the following:

  • The JPM performance standards were incorrect.
  • The administrative JPM tasks/keys were incorrect.
  • CTs were incorrect in the scenarios (not including postscenario critical tasks defined in Appendix D).
  • The EOP strategy was incorrect in a scenario(s).
  • TS entries/actions were determined to be incorrect in a scenario(s).