ML090790361

DC-2009-02-Draft of OP Test Comments

ML090790361
Person / Time
Site:	Diablo Canyon
Issue date:	02/06/2009
From:	Brian Larson Operations Branch IV
To:
References
50-275/09-301, 50-323/09-301, DC-2009-02
Download: ML090790361 (4)

Text

DC - FEB - 2009 DRAFT OPERATING TEST COMMENTS ADMIN JPMS

4. Job Content

1. 2. 3. Attributes 6.

Errors 5.

JPM# Dyn LOD Explanation U/E/S (D/S) (1-5) IC Cues Critical Scope Over- Job- Minutia (See below for instructions)

Focus Steps (N/B) lap Link

1. Identify by A1 to A5 Renumbered as A4 1 2. Task Standards are past tense Fixed

3. Include completed Attachment 11.1 in Initial Conditions Done

1. Identify by A1 to A5 Renumbered as A5

2. Identify SAE in Task Standard Done

3. Step 3.2 - range is 0.01, not 0.1 Updated 2 4. Step 4.2 - change range to 2.29-2.30 Done

5. Step 5.6 - change range to 34.5-35.2 Done

6. Steps 5.7, 5.9, 5.10 - verify ranges are accurate Revised from +/- to actual range

7. Answer Key - include circles where directed to circle one Done

1. Identify by A1 to A5 Renumbered as A1

2. More specific Task Standard Done 3 3. Steps 4.3, 4.5, 4.7 are Critical Steps Corrected

4. Steps 4.4, 4.6 are not Critical Steps Corrected

1. Identify by A1 to A5 Renumbered as A2 4 2. KA should be 2.1.40 with IR of 3.9

3. More specific Task Standard Done

1. Identify by A1 to A5 Renumbered as A3

2. Required Materials - wrong revision number for Figure R23-1F-1 Fixed 5 3. More specific Task Standard Done

4. Step 5.3 - Lower AFD Limit should be 25% not 22% Fixed Instructions for Completing Matrix This form is not contained in or required by NUREG-1021. Utilities are not required or encouraged to use it. The purpose of this form is to enhance regional consistency in reviewing operating tests. Additional information on these areas may be found in Examination Good Practices Appendix D. Check or mark any item(s) requiring comment and explain the issue in the space provided.

1. Determine whether the task is dynamic (D) or static (S). A dynamic task is one that involves continuous monitoring and response to varying parameters. A static task is basically a system reconfiguration or realignment.

2. Determine level of difficulty (LOD) using established 1-5 rating scale. Levels 1 and 5 represent inappropriate (low or high) discriminatory level for the license being tested.

3. Check the appropriate box when an attribute weakness is identified:

• The initiating cue is not sufficiently clear to ensure the operator understands the task and how to begin.

• The JPM does not contain sufficient cues that are objective (not leading).

• All critical steps (elements) have not been properly identified.

• Scope of the task is either too narrow (N) or too broad (B).

• Excessive overlap with other part of operating test or written examination.

4. Check the appropriate box when a job content error is identified:

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

• Task is trivial and without safety significance.

5. Based on the reviewer=s judgment, is the JPM as written (U)nacceptable (requiring repair or replacement), in need of (E)ditorial enhancement, or (S)atisfactory?

6. Provide a brief description of any U or E rating in the explanation column.

7. Save initial review comments as normal black text; indicate how comments were resolved using blue text so that each JPM used on the exam is reflected by a (S)atisfactory 0 Page 1 of 4 OBDI 202 - IOLE Process

resolution on this form. 0 Page 2 of 4 OBDI 202 - IOLE Process

DC - FEB - 2009 DRAFT OPERATING TEST COMMENTS CONTROL ROOM/IN-PLANT SYSTEMS JPMS

4. Job Content

1. 2. 3. Attributes 6.

Errors 5.

JPM# Dyn LOD Explanation U/E/S (D/S) (1-5) IC Cues Critical Scope Over- Job- Minutia (See below for instructions)

Focus Steps (N/B) lap Link

1. Step 2.2 not required Fixed S1 E 2. Step 4.1 - remove May Fixed S2 S S3 S S4 S S5 E 1. Add a direction from the SFM to the Initiating Cue Fixed

1. Identify what steps in the procedure have been completed Fixed S6 E 2. Step 2.3 - add places to record SG pressure and Required Temp Done

3. Step 6.2 is not required Removed S7 E 1. Task Standard - remove informing SFM of status (not a Critical Step) Fixed

1. Step 3.2 is not a Critical Step Fixed P1 E 2. Steps 5.2, 6.2 are not Critical Steps Fixed P2 U Non-discriminatory - replace Done P3 U Non-discriminatory - replace Done Instructions for Completing Matrix This form is not contained in or required by NUREG-1021. Utilities are not required or encouraged to use it. The purpose of this form is to enhance regional consistency in reviewing operating tests. Additional information on these areas may be found in Examination Good Practices Appendix D. Check or mark any item(s) requiring comment and explain the issue in the space provided.

1. Determine whether the task is dynamic (D) or static (S). A dynamic task is one that involves continuous monitoring and response to varying parameters. A static task is basically a system reconfiguration or realignment.

2. Determine level of difficulty (LOD) using established 1-5 rating scale. Levels 1 and 5 represent inappropriate (low or high) discriminatory level for the license being tested.

3. Check the appropriate box when an attribute weakness is identified:

$ The initiating cue is not sufficiently clear to ensure the operator understands the task and how to begin.

$ The JPM does not contain sufficient cues that are objective (not leading).

$ All critical steps (elements) have not been properly identified.

$ Scope of the task is either too narrow (N) or too broad (B).

$ Excessive overlap with other part of operating test or written examination.

4. Check the appropriate box when a job content error is identified:

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

• Task is trivial and without safety significance.

5. Based on the reviewer=s judgment, is the JPM as written (U)nacceptable (requiring repair or replacement), in need of (E)ditorial enhancement, or (S)atisfactory?

6. Provide a brief description of any U or E rating in the explanation column.

7. Save initial review comments as normal black text; indicate how comments were resolved using blue text so that each JPM used on the exam is reflected by a (S)atisfactory resolution on this form. 0 Page 3 of 4 OBDI 202 - IOLE Process

DC - FEB - 2009 DRAFT OPERATING TEST COMMENTS SCENARIOS Scenario 1. 2. 3. 4. 5. 6. 7. 8. 9.

10. Explanation (See below for instructions)

Set ES TS Crit IC Pred TL L/C Eff U/E/S

1. Put Events 1 and 2 on different rows of D1 Done

2. Event 8 - no corrective actions. Remove credit for Component failure. Done 1 E 3. Put Target Quantitative Attributes on D1 Done

4. Add procedure references throughout D2s Done

1. Move Event 1 to Event 4 Done

2. Identify all positions given credit in the Event Type column Done 2 E 3. Put Target Quantitative Attributes on D1 Done

4. Add procedure references throughout D2s Done

2. Identify all positions given credit in the Event Type column Done 3 E 3. Put Target Quantitative Attributes on D1 Done

4. Add procedure references throughout D2s Done

1. Identify as Scenario 4, not BU Done

2. Identify all positions given credit in the Event Type column Done BU E 3. Put Target Quantitative Attributes on D1 Done

4. Add procedure references throughout D2s Done Instructions for Completing Matrix This form is not contained in or required by NUREG-1021. Utilities are not required or encouraged to use it. The purpose of this form is to enhance regional consistency in reviewing operating test scenario sets. Additional information on these areas may be found in Examination Good Practices Appendix D. Check or mark any item(s) requiring comment and explain the issue in the space provided.

1. ES: ES-301 checklists 4, 5, & 6 satisfied.

2. TS: Set includes SRO TS actions for each SRO, with required actions explicitly detailed.

3. Crit: Each manipulation or evolution has explicit success criteria documented in Form ES-D-2.

4. IC: Out of service equipment and other initial conditions reasonably consistent between scenarios and not predictive of scenario events and actions.

5. Pred: Scenario sequence and other factors avoid predictability issues.

6. TL: Time line constructed, including event and process triggered conditions, such that scenario can run without routine examiner cuing.

7. L/C: Length and complexity for each scenario in the set is reasonable for the crew mix being examined, such that all applicants have reasonably similar exposure and events are needed for evaluation purposes.

8. Eff: Sequence of events is reasonably efficient for examination purposes, especially with respect to long delays or interactions.

9. Based on the reviewer=s judgment, rate the scenario set as (U)nacceptable (requiring repair or replacement), in need of (E)ditorial enhancement, or (S)atisfactory.

10. Provide a brief description of problem in the explanation column.

11. Save initial review comments as normal black text; indicate how comments were resolved using blue text so that each JPM used on the exam is reflected by a (S)atisfactory resolution on this form. 0 Page 4 of 4 OBDI 202 - IOLE Process