ML16280A453

From kanterella
Revision as of 01:17, 8 November 2018 by StriderTol (talk | contribs) (Created page by program invented by StriderTol)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search
River Bend - 2016-09 Draft Op Test Comments
ML16280A453
Person / Time
Site: River Bend Entergy icon.png
Issue date: 09/30/2016
From: Vincent Gaddy
Operations Branch IV
To:
Entergy Operations
References
Download: ML16280A453 (3)


Text

Attachment 10 Page 1 of 3 OBDI 202 - I OLE Process RB 2016-09 DRAFT OPERATING TEST COMMENTS ADMIN JPM S JPM# 1. Dyn (D/S) 2. LOD (1-5) 3. Attributes

4. Job Content Errors 5. U/E/S 6. Explanation (See below for instructions)

IC Focus Cues Critical Steps Scope (N/B) Over- lap Job-Link Minutia RO (A1) NRC wrote the op test

-all comments were resolved during validation.

RO (A2) RO (A3) RO (A4) SRO (A 5) SRO (A6) SRO (A7) SRO (A8) SRO (A9) 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.

Attachment 10 Page 2 of 3 OBDI 202 - I OLE Process R B-2016-09 DRAFT OPERATING TEST COMMENTS CONTROL ROOM/IN

-PLANT SYSTEM S JPM S JPM# 1. Dyn (D/S) 2. LOD (1-5) 3. Attributes

4. Job Content Errors 5. U/E/S 6. Explanation (See below for instructions)

IC Focus Cues Critical Steps Scope (N/B) Over- lap Job-Link Minutia S 1 NRC wrote the op test

-all comments were resolved during validation.

S 2 S 3 S 4 S 5 S 6 S 7 S 8 P1 P2 P3 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.

Attachment 10 Page 3 of 3 OBDI 202 - I OLE Process R B-2016-09 DRAFT OPERATING TEST COMMENTS SCENARIO S Scenario Set 1. ES 2. TS 3. Crit 4. IC 5. Pred 6. TL 7. L/C 8. Eff 9. U/E/S 10. Explanation (See below for instructions) 1 NRC wrote the op test

-all comments were resolved during validation.

2 3 4 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.