IR 05000321/1982021

IE Insp Rept 50-321/82-21 on 820708-09.No Noncompliance Noted.Major Areas Inspected:Disassembly of Two safety-relief Valves

ML20062J098
Person / Time
Site:	Hatch
Issue date:	07/19/1982
From:	Herdt A, Jape F NRC OFFICE OF INSPECTION & ENFORCEMENT (IE REGION II)
To:
Shared Package
ML20062J082	List: IR 05000321/1982021 ML20062J077
References
50-321-82-21, TAC-48771, NUDOCS 8208160263
Download: ML20062J098 (8)

Text

,

sk#M0, 0 UNITED STATES yf o,, NUCLEAR REGULATORY COMMISSION 2 o REGION il 5,

, $ 101 M ARIETTA STREET, o '[ ATLANTA, GEORGIA 30303

%, * . * * * /

Report No. 50-321/82-21 Licensee: Georgia Power Comptny P. O. Box 4545 Atlanta, GA 30302 Facility Name: Hatch 1 Docket No. 50-321 License No. DPR-57 Inspector: /f-

!

F. Jape Date Signed Approved by: [l[!/[

A. R. Herdt, Chief 7//f V

/Datt Signed Engineering Inspection Branch Division of Engineering and Technical Programs SUMMARY Inspection on July 8-9, 1982 Areas Inspected This special, announced inspection involved 14' inspector-hours on site in the area of witnessing disassembly and inspection of two safety-relief valve Results No violations or deviations were identified.

r I

~

8208160263 820719 PDR ADOCK 05000321 0 PDR

. ,

REPORT DETAILS Persons Contacted Licensee Employees

• H. Nix, Plant Manager

• R. Nix, Superintendent of Maintenance S. Barr, Maintenance Foreman J. Newton, Maintenance Foreman Other Organizations Wyle Laboratories J. Napp, Senior Engineer T. Leopard, Technician Target Rock Corporation M. McKenna, Field Serviceman INP0 D. Reddy, Inspector NRC Resident Inspector

• P. Holmes-Ray, R. " Attended exit interview Exit Interview The inspection scope and findings were summarized on July 9,1982, with l those persons indicated in paragraph 1 above. The inspector stated that the

'

two safety-relief valves inspected revealed no obvious cause for the j improper operation as reported in LER 50-321/1982-6 Licensee management l concurred with this observation and stated that reassembly of the valves would begin in preparation for startup.

i I Licensee Action on Previous Inspection Findings Not inspecte . Unresolved Items Unresolved items were not identified during this inspectio . Followup of Apparent Malfunction of Safety-Relief Valves (92705)

On July 3, the Region II NRC office was notified of a reportable event, in which the eleven safety-relief valves apparently malfunctioned. (See

r o .

Figure 1 for valve arrangement.) Details of the event are reported in LER 50-321/1982-6 One of the items, agreed upon by the licensee, to assist in determining the cause of the apparent failure and to ascertain operability of the valves prior to restart, was to disassemble two to the eleven valves for examina-tion of the component The disassembly and component examination was witnessed by an NRC Inspector. No obvious evidence leading to the apparent malfunction of the valves was observed by the inspecto Representatives from Wyle Laboratories, Target Rock Corporation and Georgia Power also stated that there was no evidence of the cause for malfunction. The two valves disassembled, selected by the licensee for examination, were B21-F013E and B21-F013 The disassembly was accomplished using procedure HNP-1-6020, Main Steam Relief Valves Maintenance. The valves were physically disconnected from the main steam line and the torus relief line. The pilot actuator was also removed from the main relief body. This permitted the main valve disc, valve piston and preload spring to be examined. l inspector manually manipulated the main valve disc and found it to slida smoothly and freely without excessive force. The main valve disc was pushed upward to allow the main valve piston rings to be examined along with the main piston inser The two rings for each valve were clean and rotated freely in the piston grooves. No wear or other defects were noted on the main pistons or the inser While the valves were disassembled all of the ports and vents were checked for foreign objects, signs of rust, and corrosion. All ports and vents were found clean and clear. A light was shined through each port to ascertain opennes The main valve spring was examined and found clean and normal. From the visual examination, the spring did not appear to have a set or be mis-aligne The inspector also performed a visual examination into the main steam line safety-relief connection Nothing unusual was noted within this line.

!

l In summa ry , there were no obvious defects or clues as to why the valves

,

performed as reported. Valves B21-F013F, G and L were reported as popping above their setpoints, which are shown in Figure All other valves were reported as not popping. It was noted that the three valves that did pop were all on C main steam lin Photographs of the valve components are enclosed. Figures 2 and 3 show the main valve disc. Figure 3 also shows the main valve piston vent. Figure 4 shows a side view of the main valve piston and the piston rings. The pilot sensing port and the main valve piston vent are shown in Figure 5. Figures 6 and 7 are general views of the valve assembly. Figure 8 shows the

,

'

Two-stage Target Rock Safety-Relief Valve and indicates the view angle of Figures 2 through Within the areas inspected, no violations or deviations were identified.

L

-

- -- .: =-= . :===., =:=_- - ==g= mg....,m. .g., mg,ggym, gym y

. .

t1Alti STEAf1 RELIEF VALVES LOCATION AND SET P0lflT FIGURE 1 ftain Steam Lines C D li I; i

'

,, '

/ E F -[1050psig 10% psig Jr A 100 psig D,/

. .s 1100 psig psig s k2 (1100 psig \

C f- 1(,JO psig 'N () N /,.

N '/

y s

'

r

[ Reactor Vessel

. )1050 psig

,

,\..l0a,psig

.s ~ -/ 's% .___ . .. I, 9 f hh1010psig

. g

/,/ -

'\/

.

Valve flumber = -021-F01.~3 X = ADS FUD C TION

e

.

.

-.g ,

a j c,

p

..

-p '

..

&

n :n .-,. .. & .4 e

~

k .. : .-

. <-

i, ;

~ * * '.

..

-

• .. d r *

g ., .

,,,

-- .

- . . - . #-, , ,

-

.

. - , " . ". . '

. , , ; .

• '

. f p- * 'A -

p .s _ ,,,p

+ :.%

-

g g e' ;

.,D' .=

g

' , ., .~, z ='-

. ,

_n.'.. . - ' ,'y,

_

'

..

- _,.f f ,

'

- =

k. , '

--

T .. 0

..3

_

a q_*

'. . . ;..> %

-

.

'

".. .

y . .3,, . .

.-. .

' . - ., * '- , , .. , ' .'

,-, - , , ,,

- :,

. .. , .. ,g -> -

+

_

y' .- -

.,,g ba. . ,

.

4, .: - : -.:

F'ft

,

.

-

,

,' ., 4.' -

' L

'

,7

. "i -

_;, ; .

'

, ,.- +x e , n' . -

• .a e . - ,

-

'"# 4

. . .

'* * +

S '?/i.*4 A

• .*

. .- . j, j-g,b . , -

%

,

.

.,

--

-. S

" '

, . .

.g E'

,.'(1

. '. .*' 4 ',. .

... -. . - "

'

[_ , M, , . . -

'

< + . , .. , ,

,

'.

.'.

.

' ~.

5,, v , ,

- * *'. '

~

g

'

'.

_

^

$ ,, , i  % 4 .&

.._ . ,

^'

. ,). .,._ . >. ~.'g,., '. T ' V., y . ,

%

a', - 4 y ,

, - :..,,

. .

.

.

(

.,

-.,., .

..,

*- f_-

. ...

, ,,

.

..

?

.

, ._- ..

e .. . -  ! $. . 4 . *_ . . . J - . , . * . ' ' . . . . ' * ) '

Fig. 2

.q -

- } '

ll, .. f }l

'

c ,-.-* .

. -

-

. .- .

,,

. .e ,. . , ,

._-

n > .', , , ', -

• -

._ ' _: P

• .-

• . - #'. g , ,

- .

• ~ ,,',,

j-- - -

.

,,

- ; <,q'  ; . ;.. A .. ;.u: ,~. :

.

. - I _.s, - s

.I6

..' - % ~.

'

, 4;

+ . _ ' * ' ' : .-

\ . ~ .

^* i (%

' - -

- '.

'

.> ;.: .-

'

'-

si ' .. ... .

.

.h '..

,. . .. .;.

u.. .5:

.',pL' .- .y, '. , ' . A' , .' .*. .*- ,

. ..

.s .

-

t

,"., :. ' -- .- - . , ... ..c.' a .,

} .

'

- ; ) ' g. , ~ . ~II [p~ ' ,; I ' . .' .

5,, ,, , ,,A-- ,

.

'

. .. .

f '. .,

.. .. . .

. ./- ,

-

- ,

, w_._ r .

. -

- -

...

. .,

. % . * . - , "n .

a

-

^ '.

- -.... f

.

..

e 4 <?, o.- --'*c ~ g .

-

f,", +

.

)f 4 : vf$f3 '". .A. l -.

• "

.

's

.

+

.

. .

- -

.

".,-

,. .- y .. = ,

,

. [ .

'j -

. ..

- ., ,'y .

" '

. , pf.?

. . . 3 . ;. ,

-: - ' _ ,

.e

-

.e . ,.

. . , , * .

Fig. 3

.

i (

(

( per

, APPLIEDTECHNICALWRITING 4-1 Writing the Document I WRITING THE DOCUMENT

.

( You have gathered the information, massaged it, outlined it and selected the format. Now you are ready to write the actual documen You may never be involved in a systems development project that l

generates the many documents described. However, you may have to write one of them or a document similar to any one of them. Through k studying the requirements for each type of document, you will have a clear idea of the kind ofinformation required in each typ Many writers like to begin at the beginning and work to the en ('

lioweser, getting started is often the problem. This is when all the information gathering, massaging and outlining begins to pay off. In this text, you will see how to put together each of the technical ( documents identified in the preceding tex (

Needs Statement f Figure 3.2 showed a sample outline for a needs statene n Following that outline, the needs statement can be composed of five parts. As shown in figure 4.1, each part was represented by a Roman

[ numeralin the outlin In part 1, summarize the analysis of the present system and its problems as follows:

( Identify organizational or functional changes that could be aided by a new syste ( Document those items or processes that differ from established I procedures and are not documented elsewher . Describe how the present system works in detail, delineating what

• operations or tasks are performed and how they interrelat i 8 a. Include any data flow chart Note any existing inter-site communications, along with

[ ] operating data descriptions of the types of communications, j

" turnaround and peak time (

i

..

_ _ _ _ _ _ . _

l

g{g'

-

,.

- M .: 1

,, s

4 . .e~. . .

.

j-

• ~. . '. -

w,

,- - ^.

• 7 a y

.--i .  :.- -

_- .

' .s. ' *y ..

'

k

'

'T ,

,., .

'

-

' *

_

. . . . ., .

. *$Y

,,.

. .

'. .i . _ . ;. p .  ??

. .,', .-

' -

_ - . -

~ ~ " ~ ,

, A.; \

l

, c .. , '.,".::,,. -

-w

.

Y,. K-g i

...--1 4,np ..- ., - ,'- -

1 <.- . , r

.

, . ,_< . . . - l

' -,.

.

% _. , . e *.:.. .

'

.

" . . _ .... ' -. . 4 . 'vM*. m%

..

,..

y,,

-

, '

- ,

I - .

.

..

..

' -

. s ~,..

'

-l -

.

.

, . . _,

.- . . _

.- . .

. . ,. .... . ,

1 .

'.

,.,-i N, *

f .. *

. -g

,sg

.

-

-

.

.'

V. .

.

.g

-

, . .,+

f, q

'

$.yn '_,e _. ; , .c ;y'?y

C . . }s. ._: .

-

..

-

1. 4. gbWhQ

.

. .

.

% l Fig. 4 1 ,..

.

. . . .

. . .

O +. - ,: .,

o

. , ,

_. ..,. '[I . . , ,

_,'.,,,"- .

,

. '$ s ,

.

-

's'

-

'-

, .

._ ., ,

. x ,,

,

^

-

. . A u '-

,

.

[

. , . - -

,q- . -

_ >g -

. -g g,; , - .

'

. .c . ~

..

s '- .

.s

- .

,  ; .

, 9 g i .- * ' .,' , .

..

. ... . .

y:..-- .

, ,

-

- - -

- . . ,'t . , 4 -

-

. .

.

-.

. .

gg g * ,' ' ** '

.o q ' _

,'

• , . -

, *

• • '..

'ij f.:y *L'

'

! l' . .

- .. . _

~ . . . _

.

.

_

, .

._

~ . .- -.s

.l. : .'

-

.

,- s

.%.

.

r

.

.

. .

. x t

'

, , ,5

,

'

. * , ,

g , * ..y . - e . .

_.-'" - '

,

-

, .> -

l -

. ..

..,.. . :.E - (;  ;- ep,? ^ .. ,

.

'

+ 4 . , . . - .,. ..

, . .V

,,; .: , .

,.

7  ;-

- ~

.'

f'. f j*% ' ). , ,'.-- .. - ..

,... - , .g ~ -

.q_.. _

. ... 7

-

a ,; . .. ,- __ ~

Fig. 5

.

-,..m

(

(.

-(

APPLIED TECHNICALWRITING pc e 4-2 Writing the Document Tabulate input / output forms and files to demonstrate the

-

volumes involve (- Discuss problems of the existing syste Include informational deficiencies involving such things as:

- management information systems decision making ( deficiencies

- clerical system error rates I - specialprocessing problems b. Mention personnel factors if they are or will be part of the proble ! State any constraints on possible systems that may have been identified during information gatherin Example: If there are special reporting requirements for management, try to be as objective as possible. This will enhance the credibility of your recommendations later in the I

documen I In part II, define those requirements that any proposed system must meet to resolve the needs or problems identified in part I. Define the main design objectives from management's viewpoint as follows:

4 Identify the functions to be performed by the proposed syste Example: Record month-end disbursement for accounts payabl ( Indicate performance objectives to be met by the proposed system function ( Emphasize data base or master file constraints in quantified for ( Speak to data security and integrity consideration ( Directly address problems or needs concerning the objectives in

} pari I that are connected with information usage and require-ments. Identify what data needs to be captured to present

{ '!

E information that meets those need ,,

(

(

i

. . . _ - . . . - . . . ~ . . - - - _ . -- _- -. - - . - _ . _ - . - - _ . - - _ _ _ _ - _ _ _ _ _ . - - - - _

l-

. . .

l* .

i

>

6 I

.

.

, , . .. .. + ,, l

.

'

,

'~ .-

' , ' ,

. .I. .- .'}-' '(

\

• g ja ' - '

- Q* ' . ._ l

,4%p"_l', ..;. , s,y s

'

m

. ' n. ,, g g}. . < . 4_ ;!

'

..

• .

...u .L

,.

o '-'s

..

.

-

.t y  : , a

'

j- V , r. ~ 31 '

-

-

'j. ;s_ -/

-

'e-

, ,. ,

~2

.g , f ,  %., % 'i. k - *[

j hlf-g '; ., %

. . .

'T *

., . . ' + y ,.N . .., -

~-

for _. -a , l

.Y

, k .~ . l

, v .1 .. . , . ,. .e

.

. 4 g .1,

"

i e. .* y . .e.%p... ,. . g -

Ys,

-

.

3 ;

fT 6'

I ,

.

.

.

,

gy'. '

. , . ' ,a -k.,.

. ?

.

-

l s 3 . 'f .

.,.

. .

-

p .

, , w l

c ~ . ' . ;c; g. . v.. _.- .. y

-

l .: .

.

,  ;

,e

,

'

. .,;h '

,  %

.

.

.. . y*I i .

.

i

,

)

s V'- F \

l 7- _;l.65 [._ _

.

l

\ ...-  ; ; w ., . .: .. -,-

,

< ,. ! + 2+ .: Qg .T

-~_ g,"-# *4 ,.

l . . , . .- .

.' ( ., ,

. - , , -

-

, , . ..

- r; .

l . . : ; 2 'yeq -  : A i i ~'~ l .l l bY ' f A

- . . I L

Fig. 6 i

. .: , ,. s

,

.

~ ,

e . ,t .

'

, 7.' ~

.. .-#

.f .> e. ,  :-

.v...,y .

.

'

$ h' . Ig* .' * ^ ; -

A' .

. .

.s . . . . .

+ ,

'h#^[ <F f fh h - .- 4 ~( k

., y - . .

' -

'

,y . e-p' } $

,

g. , , r

'

.. ,

.

• f i * < , . , . . r

.._ g i., ' . - ., ,. ( f' '[

.' . . ' ^ $. , ." ' 4 j ([lWD #

'

i ..

'

- .; :- . .

. j

,

'

-

.s 9 -,t

'..a ,

g , .. ,, [ '. l( ' i .g. * ,

'Y ,' ' .y yg ' h#,,

'

f; . .!

-

' . - ,. 5 .

-

.., .

,. --

. , , . . .* '. ,

,5, p,. .y .....rtw 4,g-

,

.. .. . .

,

. . . , - -

..- t

.' . : - i

- ,

';^ .. - i

. t

.

.. ' _ . )[V - . .. s . ' - L'

_

l s . . . . . .

.

.

'..' .4

'

• l ' - fn, Y

'

.,',.-N. =s..,O -.,

. , ,.

-,

. : .. ,,. .: - . .s

, g y ...g.,.,- ,

l

,

w r s . .

-

. e

.- . . .+ .. >

..- .-

,,

qf, .-,; . .. .'- " w7 * ,,

, . , -

.

,

'

w #'

-

g ,

i - , - - ,* .. , - --., . _ . , .

"

l p '

.h. 5 6~,  :" , '____

- *

r,e; %,..3g nz .

.

- *. f:N <, .: ,', - . .

-_

..,. , , .. 7 . ,

-

_

,

I Fig. 7

.

B

.

!

, _ _ _ , _ - - - - _ _ ,- .. -- _- - -- -- . _ - -

,

t (

(.

( , APPLIED TECHNICALWRITING page Writing the Document 4-3 (

f In part 111, delineate the tangible and intangible benefits that can be realized by properly addressing the needs or problems from part 1, as follows:

( Show how the proposed objectives will produce tangible benefits

,

by looking at cost, cost avoidance and savings. Example: A 25%

reduction in cross-checking and summarizing by each account will allow a 60% decrease in their work load. This will reduce new i personnel requirements over the next two year . Show intangible benefits and emphasize improved service and

' performance. Example: More timely and accurate reports will make inventories 30% more visible. These reports will reduce

,

errors / risks in policy decisions and daily operations by 50%.

In part IV, identify the DP staff's appraisal of the project, based on the prior analysis and collected information. Try to avoid any bias that

would, at this point, favor one approach over another. Other documents will discuss alternatives and specify hardware and softwar Since the likelihood that your recommendations will be acted upon is high, pay special attention to how you phrase them. Whether they are phrased in a positive or negative manner makes a differenc Be as firm, clear, concise and explicit as possible. Keep in mind the attitude of your reader / audience. Willit be non-DP people who harbor fears and resentment toward automation? If so, you will first have to

' allay those fears - perhaps by recommending setting up a project team in walk through each step of a recommended DP consersio Conclude this section of the document by summarizing the size of

{ the organization affected, the functions involved and the interactions of the new system with the organization and its function ( As supporting data to be included in part V you might consider listing the people interviewed, the analy sis methods used, a list of the

, organizational documents consulted and any other relevani collected document ( t,

!

, E t :

(

\

(

p..__,._ _ . _ . . -

- - - - - - - - - - - -

-

e

PROT STA0lLilf R PHELOAD DISC

"O >

Y

\\\\ M w3g i

\ d 00000 '

s; -

PILOT -

,

-

-

-

4 '

}psh ;

, 1: ? rs;

e j

.

,,

$tN56NG b ct n - p 4,

. -._ - J. ,- ,. "ALLQZ H .s-q y' NN"*-p g p3' - a w s y g ,I L

, + ,- ,

.

,

'

,-

f

"

jl r

L , y Fig. 5

.

o ! b , A u .h 0, N ,E, _

ALMU5TVUdT y@~.

'

PILOT SPUIN G AIR O Q

.

O '

I O

'0 - - - I N .

AIR U !, ACTUATO9-y ,

MAIN VALVE DM- q;- ,

PRE LOAD f PalNG

'

pg 4p' iI ' * " -

3';; ,, MAIN VALVE PISION

' ~

f, WJN VALVE Ps3 TON VEN f p

i9 IP E T f;j, '

,

I s '-r" -

7 / MNN VALvL O'$C

.

,

, $

Fi9 7 p ougtT

<d*

iFig. 2 Figure 8 TM Stsp Tuget Rd Safety /afef Wn

_ _ _ - - - - - 1 __-r_-

_* flLL"3% NNYW F+*P'NW*fh .m - u- - - ,_Q* L ._