ML061980074

CNS Notification 10295021

ML061980074
Person / Time
Site:	Cooper
Issue date:	02/11/2004
From:	Cuser B Nebraska Public Power District (NPPD)
To:	Office of Nuclear Reactor Regulation
References
FOIA/PA-2006-0007, R4-5A26
Download: ML061980074 (5)

Text

SM i rDkiniay-PM Nvotification:- condition DG'S6~1;1E Report ii.9iS T ~

~~jI~~__IIJj..

f§ I I IljiIisI e' I I IIiI~IIIHIN,l ItIjIffIfIflWI!,

Ii Mi in I1

'I~litnIer grobup- utIJN ,'IIjI

-ICNS ri .lt .f u-'8i ~Plannilng 'De iilq~;P:h

pt .- !l

iI lfjliI ,I -I'4 tL :SJ', -'It

Ml~aln,.worCtr '! I~PSIP$ j *dt,?,JM§it .9!'OPS MANGOERkYSELECTEDSTAFFiOSa User ro ibi nsJ",

..... ..i I . ,-'N a ) 1 , ,':111 l,,2 *I : i1.., HFPO

.i*. .. ;

:i)l.;:.llltlI*i liV 777l."!:" " *;lll i-:¢** ,*  :,% J:l,;:il~  :'

rasp  ! l~  !  :{ **':.*li' II I

Prhits th~WIhdows content~

P~-

~ -

- .A-

02/11/2004 04:15:19 btcuser (BTCUSER)

DESCRIPTION OF CONDITION:

WHILE PERFORMING A VALVE LINE-UP ON THE SERVICE WATER GLAND WATER SYSTEM, SW GLAND WATER SUBSYSTEM B WAS FOUND LINED UP TO SERVICE WATER SYSTEM A. SW-V-28 WAS .CLOSED AND SW-V-1479 & 1480 WERE OPEN. IT APPEARS THIS LINEUP WAS NOT PROPERLY RESTORED FOLLOWING MAINTENANCE ON B ZURN.STRAINER.

REQUIREMENT NOT MET:

SW GLAND WATER SUBSYSTEM B WAS LEFT MISALIGNED TO.SERVICE WATER SUBSYSTEM FOLLOWING RESTORATION OF B ZURN STRAINER.

METHOD OF DISCOVERY:

PERFORMING AVALVE.LINE UP ON SERVICE WATER GLAND WATER TO DETERMINE CAUSE OF LOWER GLAND WATER SUPPLY PRESSURE.

IMMEDIATE ACTIONS TAKEN:

RESTORED PROPER SW GLAND WATER LINEUP PER PROCEDUR 2.2.71.

RECOMMENDATIONS:

DETERMINE CAUSE AND CORRECT LOCATION OF EVIDENCE:

IS-903-SSWP ROOM FUNCTIONAL LOCATION (IF KNOWN):

EQUIPMENT (IF KNOWN):

SERVICE WATER GLANDWATER REPORTED BY:

JRWEISS WORK CENTER:

OPS SUBMITTED BY:

j rweisss SUPERVISO R:

BRIAN MURPHY DEFICIENCY TAG:

N/A

IS THIS AN EQUIPMENT ISSUE?

[X] YES, CONTACT THE SENIOR REACTOR OPERATOR (SRO) IN THE WORK CONTROL CENTER (WCC) OR THE CONTROL ROOM.

J ]'NO IF THE CONDITION IS EXPECTED TO BE INCLUDED IN THE CORRECTIVE ACTION PROGRAM, INDICATE IF YOU WOULD LIKE TO EVALUATE THE ACTIONS TO BE TAKEN FOR THE CONDITION?

[ I YES

[X] NO ADDITIONAL COMMENTS:

02/11/2004 10:17:05 Jerry J. Long (JJLONG)

SW SUBSYTEM 'B', DG-2 AND CREFS WERE DECLARED !INOPERABLE. LINE UP WAS RESTORED AND SW SUBSYTEM 'B', DG-2 AND CREFS WERE DECLARED OPERABLE.

- 1 -

02/11/2004 018:41:00 Peter J. Donahue (PJDONAH)

OPERATIONS REVIEWOF NOTIFICATION Is the condition an immediatemnuclear or personnel safety concern?

[ ] YES - Immediately notify Shift Manager

[X NO Is the condition reportable or potentially reportable per 10CFR20, IOCFR26.73, IOCFR50.72, 10CFR50.73, or 10CFR73.71 (reference Procedure 2.0'.5 and NUREG 1022)?

]

I YES - Immediately notify Shift Manager

[X] NO Does the condition affect or potentially affect any of the SSC(s) described in Attachment 4? Also consider generic concerns and common mode failures, when applicable. For significant programmatic issues, determine if a basis for Reasonable Assurance of Safety per Procedure 0.5,'BCO is required.

[ X I YES - Immediately notify Shift Manager

[NO - NOT IN SCOPE OPERABILITY VERIFICATION Does the ýcondition call ýthe SSC(s) performance into question?

[ I NO - Basis:

[,X Y] ES -Declare SSC(s) inoperable and document a basis for Reasonable Assurance of Safety if TRM or ODAM LCO 3.0.3 is :entered

[ I YES- Document a: reasonable expectation of OPERABILITY on the Notification AND-Perform:INFORMATION GATHERING Does the condition Call the SSC(s) qualification into question?

I NO- Basis:

[ X ] YES - Declare SSC(s) inoperable -and document a basis for Reasonable Assurance of Safety if TRM or ODAM LCO 3.0.3 is entered

[ J YES- Document a reasonable expectation of OPERABILITY on the

,Notification AND Perform INFORMATION GATHERING Does the condition describe an:existing but previously unanalyzed condition or accident?

[x NO

[ I YES - Declare SSC(s) inoperable and document a basis for Reasonable Assurance of 'Safety if TRM.'or ODAM LCO 3.0.3 is entered

[ YES - Document a reasonable expectation of OPERABILITY on the Notification AND Perform INFORMATION-GATHERING

-- 1 -

02/12/2004 07.:44:08 Coy L. Blair (CLBLAIR)

PER NUREG 1022 REV 2 "AN LER IS REQUIRED IF A CONDITION EXISTED FOR A TIME LONGER THAN PERMITTED BY THE TECHNICAL SPECIFICATIONS [I.E.

GREATER THAN THE ALLOWED QUTAGE TIME (OR COMPLETION TIME IN ISTS)] EVEN IF THE CONDITION WAS NOT DISCOVERED UNTIL AFTER THE ALLOWABLE TIME HAD ELAPSED AND THE CONDITION WAS RECITIFIED IMMEDIATELY UPON DISCOVERY.

THIS GUIDANCE IS CONSISTENT WITH THAT PREVIOUSLY GIVEN. (FOR THE PURPOSE OF THIS DISCUSSION, IT IS ASSUMED THAT THERE WAS FIRM EVIDENCE THAT A CONDITION PROHIBITED BY TECHNICAL SPECIFICATIONS EXISTED BEFORE DISCOVERY, FOR A TIME LONGER THAN PERMITTED BY TECHNICAL SPECIFICATIONS." THE CONDITION DESCRIBED IN THIS NOTIFICATION EXISTED FROM 01/21/2004 UNTIL DISCOVERED ON 02/11/2004. THIS CONDITION RESULTED IN DG2 AND CREFS EXCEEDING THE -ALLOWED 7 DAYS. LER DUE DATE 04/12/2004.