ML112590507

From kanterella
Jump to navigation Jump to search

NRC Comments on Draft Licensee-Developed Exam (Operating) (Folder 2)
ML112590507
Person / Time
Site: Three Mile Island Constellation icon.png
Issue date: 07/11/2011
From:
Operations Branch I
To:
Exelon Nuclear
JACKSON D RGN-I/DRS/OB/610-337-5306
Shared Package
ML110030671 List:
References
TAC U01829
Download: ML112590507 (9)


Text

May 9,2011 TMI T-75 DAY EXAM OUTLINE SUBMITTAL REVIEW COMMENTS Comments were provided to the facility exam developer (Greg Hoek) via telecom 5/5 and 5/9.

Written Outline A number of the proposed SRO KIA topics do not appear to be SRO level topics per 10 CFR 55.43: Questions topics - 76, 78, 79, 80, 81, 82, 84, 89, 92, 94, 97, 98, and 99.

A number of RO KIA topics may be over simplistic: Question topics - 1, 2, 3, 4, 11, 14, 28 31, 40, 46, 55, and 74.

SRO Admin JPM Topics:

  • Topic A.1.2, Calculate ECP- directly from bank - please change conditions e.g. time after shutdown so that calculated outcome is different.
  • Topic A.2, Determine Post Maintenance Test - taken directly from bank - please consider modifying task.
  • Topic A.3, Review RB Survey Log Would prefer something more operationally and license oriented - this is more an RP task. Prefer reviewing and approving gaseous or liquid discharge permit.
  • Topic A.4 - Proposed JPM an event classification taken directly from the bank.

Licensee will significantly modify JPM so not directly from bank also make it more complex and challenging by adding other parts to it.

RO Admin JPM Topics:

  • Topic A.1.2, Calculate ECP- directly from bank - please change conditions e.g. time after shutdown so that calculated outcome is different.
  • Topic A.2, Use Station Drawing to Predict Consequences of failure - directly from bank and used on last 2 NRC exams - recommended revising component or perform blocking and tagging for an electro-mech. component.
  • Topic A.4, Perform State and Local Event Notification - directly from bank - please significantly modify task to change conditions and errors to identify.

Simulator JPMs - cautioned licensee regarding overlap with scenarios - if testing the same systems must test distinctly different system flow paths i.e., manipulating different components.

  • JPM "A" - turbine trip greater than 45% pwr - RPS push buttons and diverse scram don't work need to kill power to trip bkrs - seems like it is ok check during validation.
  • ..IPM "S" - Pzr level controller failure - overlaps with scenario #2 event 3. Licensee plans to revise scenario.
  • JPMs "E" and "G" - may overlap with a scenario may need to be replaced. Also alternate paths maybe questionable.

Scenarios General Comments:

1) Very few meaningful Instrument failures on scenario set Le., requiring substantive actions.
2) CTs - several are questionable - not well defined regarding crew actions taken to mitigate and failure criteria - consider better defining CTs using NUREG 1021, Appendix "D", 4 factors.

For example, scenario #2 has one stuck rod after scram CT-23 has the applicant's borating. I pointed out that the plant is already analyzed for the most reactive single rod stuck out of the core. The licensee suggested revising the scenario to then stick 2 rods and I pointed out that even with 2 stuck rods where is the safety significance of not borating the core when there would probably still be adequate sId margin even with 2 stuck rods. The question comes down to what is the safety significance of sticking 2 rods - it may be satisfactory as an event but not a CT?

3) Overall between some overly simplistic events and questionable CTs the scenarios may need to be beefed up further.

Scenario #1

  • Event 4 - Overlap with ..IPM must replace ..IPM or alter scenario licensee recommended replacing with Hi moisture separator level but not safety significant.
  • Event 8 - EF-P2A does not auto start - does not complicate mitigative strategy after MT as written - examiner standards suggests events that occur after the MT should complicate the crews response. Licensee plans to revise scenario so that EF-P-1 trips at MT so that if you don't start EF-P-2A, the operating motor driven pump "S" will trip on pump runout. Licensee must verify this occurs in the simulator. I pushed back that the applicants could simply chose to throttle the discharge valve on the "S" pump in lieu of starting "2A" pump - still making this event to be unnecessary and meaningless in post MT space.

Scenario #2

  • Event 3 - Overlap with JPM "S". Licensee will consider replacing with PZR pressure instrument failure high to make for a more challenging task and avoid overlap.
  • Event 5 - see scenario general comment 2) above - needs work event will not result in a safety significant CT 23 not valid as written.
  • Event 7 - why not fail EDG as written this malfunction occurs after the MT and doesn't complicate the recovery. Consider failing the SBO EDG with a fuel leak and later restore it resulting in a SBO.
  • CTs 10 & 12 are redundant one set of actions satisfies both of these CTs.

Scenario #3

  • Event 1 - does not result in a line break of ICCS weak Instrument failure - prefer a dynamic failure that challenges the crew to take actions to mitigate.
  • Event 4 & 5 - one event tube leak requires a down power.
  • CT 7 - verify safety significance - ensure that crew actions are required to take actions mitigate or it will result in plant degradation.

Scenario #4

  • No instrument failures or major electrical plant challenges in this scenario general LOD of this scenario is low - too easy needs beefing up.
  • Event 2 - too simplistic.
  • Event 3 - too simplistic
  • Event 5 - important to safety but very straightforward lacks finesse.
  • Event 6 - important to safety but very straightforward lacks finesse
  • CT controlling FW in this scenario does not appear to be a CT - need to specify required crew actions that if not taken will result in plant degradation, possible injury to plant personnel or dose to public?

OPERATING EXAM DRAFT SUBMITTAL REVIEW COMMENTS Comments were provided to the facility exam developer (Rich Megill) via telecom 7/21/11.

Licensee's Audit exam - operating exam portion be administered the week of 7/25/11 and written audit exam the week of 8/1/11.

SRO Admin JPM Topics:

  • Topic A.4, Provide completed declaration forms for answer keys.

Simulator JPMs - Which of these JPMs, if any, can be performed in parallel?

  • JPM "A" - very Simplistic exercising normal immediate actions for an ATWS recommending replacing this JPM
  • JPM "0" - Why is step 2 critical - no adjustment necessary? Why aren't steps 5&8 critical?
  • JPM "E" - Oid not provide OP-TIVI-MAP-F0103 as a reference? Why aren't steps 14, 17 and 18 critical?
  • JPM "G" - Why isn't step 5 critical to secure AH-E-19A?

Scenarios

  • Scenario #1 - Event 4 & 5 may only count as one since little to no actions in event #4.

Recommend allowing more time for isolation actions, etc.

  • Scenario #2 - Make station blackout delay restoration of EOG and carry out SBO procedure and allow some plant degradation before allowing restart of an EOG. Event 6 need to script required actions on page 30" OP-TM-864-901 to restore 4160 bus for SBO EOG.
  • Scenario #3 - Replace Event #5 with loss of ICS power. Also for "B" OTSG allow release to get to a significant level of WB dose of 500 mr or 1.5 R thyroid forcing the crew to isolate the OTSG.
  • Scenario #4 - Event #4 no scripted actions for URO to initiate Rx sid.

~~-----

JPM A r~eplacedJPM

  • Note added prior to Performance Step 7 to state that the student may choose to perform an JPMC additional step lAW Guide 21 prior to performing the Alternate Path - no impact to JPM.

~--~----~~--

r_

u

. Edited Task Number.

  • __ Typo fixed in Initial Conditions, Evaluator and Student copies ("being feed" now "being fed").
  • Removed Bullet from Initial Conditions - Student Copy (repeat of who they were).

JPM F

  • Note added prior to Performance Step 16 to tell the candidate which MU pump is the ES l---_ _seL~cted pump if asked.

I

  • Edited Notes for Performance Steps 6,7,10, and 11 for clarity.

JPM G I.u 9hanged bolded font throughout JPM for uniformity.

. Changed typos (SR-P-1C to SR-P-1A and SR-V-1C to SR-V-1A) in Performance Steps 3,6, and 7.

1- -

JPM H *_ E__dited Evaluator Notes prior to Performance Step 13 and Standard for Performance Step 13 1--_ _~for accuracy.

r--___~_-:-_ __,_l__. _____Edited Terminating Cue for better understanding.

I

  • Added better indications to explain operations of IC-V-4 in Performance Steps 6 and 7.

JPM I

  • Edited Task Number.

r JPM J

  • y~rified no PPE required for JPM. _ _ _ _- _ _ _

- *_u ".

Signed off procedure accurately to ensure JPM is performed as written.

  • ___ Moved Examiner Cues from Performance Steps 3,4, and 5 to the Initial Conditions (Bu"ets JPM K r ____ 3, 4, and 5 on Evaluator and Student copies).

1---- _ _ _ _ _ _ _ _ _ _--'-----., __ J~:dited name of JPM to represent JPM actions.

f-I I

RO A1-1 f: Cb~l"lged Initial Conditions to state "You are a Shift Reactor Operator".

Edited typo on Performance Step 3 (> 2.5 changed to <2.5).

~~- RO A1-2

~ -----

  • Removed Evaluator Cue prior to Performance Step 1 (was a cut/paste error from the SRO I version).

)

'<'i.

~._Edited Initial Condition to remove confusion of actual f,lerformance.

ROA2

  • AddecL91earance and Tagging Manual as a reference.

.\

.**i .i*/i , .iii' i .i*. 'i I. '. .i" " i', '*i.

ROA4

  • Added Evaluator Cue to Performance Steps 7 and 9.

.. ..,....... . . i , . .i.

II .. ' 'I..** ."

SRO A1-1 Added addi!ional information to Attachments 3-8 ~eek 1, Next Cycle info}.

I* .'. . .... ,., ,

..~

SRO A1-2 i

._.* Properly labeled Attachment 1 (Header/Footer typo)

  • Moved Evaluator Cue from Performance Step 1 to Initial Conditions to state that a plan was 1--_~~rQyed based on information.

I SROA3

  • Edited Evaluator Note prior to Performance Step 3 to state that only 1 of 4 similar forms needs to be filled out for credit.

i

'. i i' i

}

r-' *i i _. .

Corrected_Answer Key SROA4

  • Added Release in Progress determination to Critical Task criteria (Evaluator Note after Performance Step 9).

'I* .i '

'i(,ii 'I. , ..

'i' Changed JPM A information to reflect the agreed to change of JPM.

ES 301-2

  • Edited JPM 8 title to match JPM.
  • Edited JPM K title to match JPM.

'i )

~ . . .- .

I'

  • Edited to reflect a roved scenario line-u s/order. -------------------------

ES-301-5

  • Edited to reflect crew com liments.
  • Edited to reflect Post-NRC validation chan

!Edited to reflect a~~roved scenario line-u~s/order.

ES-301-6

  • Edited to reflect crew com liments.
  • Edited to reflect Post-NRC validation chan es incor orated as indicated below.
  • Page 1, Event #1: Added additionallCS component fault (Turbine Header Pressure) along with the drift of an NI to ive the crew time to react rior to a reactor tri
  • Pa e 1, Event #4: Edited descri tion of URO actions.
  • Pa e 1, Event #5: Edited descri tion of ARO actions.
  • Page 2, Scenario

Description:

Edited Event 1 Description to include the addition of the Turbine Header Pressure instrument failure.

  • Page 6, Procedure Sup~ort: Added Turbine Header Pressure instrument failure to Event #1 .

Scenario 1

  • Page 7, Scenario Setup: Added Turbine Header Pressure Instrument Failure, added a 61 second dela to NI-5 both Event #1
  • Page 9, Event #1: Edited Indications Available to match after addition of Turbine Header Pressure Instrument Failure.
  • Pa e 11, Event #1: Edited Note to Examiner for re uirements to a to Event #2.
  • Pa e 13, Event #3: Added location to Booth Operator Note for clarity.
  • Page 24, Event #6,7,8: Added Notes 1) to Examiner for EFW valve control, and 2) Booth Operator for actions to take if called.

Page 1, Events 7,8: Rearranged Events 7 and 8 due to Station Blackout, removed EF-P-1 asOOS.

Page 2,

Description:

CT-8 edited to include "when Maintenance has fixed the

_problem". ---

P?ge 6, Procedure Su~~ort: Rearranged Events 7 and 8 due to Station Blackout.

Page 7, Scenario Setup: Removed EF-P-1 OOS setup, Removed Triggers 7 and 10 to accommodate Station Blackout.

Page 8, Event #1: Added Examiner Note that MU-P-1 B may be placed in PTL lAW Alarm page 13, Event #2: Added Booth O~erator Note for action to take if needed.

Page 14, Event #2: Added Note to Examiner to ex~lain PTL actions taken for SBO Diesel.

Page 15, Event #2: Added additional Tech S~ec.

Page 16, Event #3: Edited page number to turn to for alternate actions (Examiner Note),

Adde~LExaminer Note to explain that PORV may be blocked as a conservative action.

  • Page 22, Event #4: Edited Pump identification to LO-P-8A (typo), Added/Edited Notes to Examiner to eXRlain--- seguence of transition to Event #5.

Scenario 2 Page 23, Event #5: Edited Booth Operator Note to explain transition into Event #5, Added Examiner Note to address possibility of an additional step taken by crew lAW alarm

~~W

_response.

Page 25, Event #5: Edited Note to Examiner to clarify when to go to Event #6.

~g~ 28, Event #6,7,8: Added steps lAW OP-TM-226-901 age 29, Event #6,7,8: Added steps lAW OP-TM-226-901, Added steps lAW OP-TM-AOP 20,_$ection 4.0 $jation Blackout. -

age 30, Event #6,7,8: Removed step for attachment 5 (step is applicable in a rev after ass' procedl.j!e freeze date.

age 31, Event #6,7,8: Added Note to Examiner to address when the Emergency Diesel lenerator may be returned to service, Added Booth Operator Note to create Trigger #7 to 1I0"",for start of E~-Y-1A, Added steps lAW OP-TM-861-901

  • Page 32, Event #6,7,8: Added steps lAW OP-TM-AOP-020 and OP-TM-EOP-01 0, Guide 1 Natural eirc.
  • Page 33, Event #6,7,8: Edited Follow-up Question (EAL call) due to addition of Station Blackout.
  • Page 37, Event #2 Info: Added Effects of Loss of 1E 4kV bus, listed at end of scenario for Examiner information. ---- -----
  • Page 2, Scenario

Description:

CT-22 Edited to include isolation of OTSG based on offsite dose rates.

  • Page 17, Event #2: Edited Notes to Examiner to clarify requirement to go to Event #3.
  • Page 27 Event #6,7:: Added Note to Examiner to clarify what Cooldown rate should be prior to offsite dose rates being called in, Added procedure note for clarification, Added Note to Examiner to clarify that an 1MT step will not be performed until offsite dose rates are called in. I
  • Page 30, Event #6,7: Added Booth Operator Note to call in offsite dose rates, Added Note to Examiner to explain procedure path after offsite dose rates are called in, added procedure IMR step to isolate OTSG when conditions are met.

Scenario 3

  • Page 31, Event #6,7: Added steps lAW OPO-TM-EOP-005, Attachment 1B to isolate B OTSG.
  • Added additional steps lAW OP-TM-EOP-005 that may be performed while waiting for offsite dose rates to be called in, Added Note to Examiner to explain the added steps, added steps lAW OP-TM-826-901.
  • Page 33, Event #6,7: Added steps lAW OP-TM-826-901, Added steps lAW OP-TM-EOP 010, Rule 5, Emergency Boration.
  • Page 34, Event #6,7: Added additional steps JAW OP-TM-EOP-005 that may be performed while waiting for offsite dose rates to be called in, Added steps lAW OP-TM-EOP-01 0, Rule 5, Emergency Boration.
  • Page 1, Scenario Outline: Added name for MU-V-36 for clarification.

Scenario 4

  • Page 10, Event #1: Added Notes to Examiner to address requirements to go to Event #2.
  • Page 16, Event #3: Added Booth Operator Notes based on validation call-ins to the field.
  • Page 32, Event #7,8: Updated EAL call for post-scenario discussion.