ML20114E006

Nonproprietary WCAP-13486, Grafter:Microcomputer-Based Code Sys Construct & Quantify Fault Trees

ML20114E006
Person / Time
Site:	05200003
Issue date:	08/31/1992
From:	Sloane B, Wallace I WESTINGHOUSE ELECTRIC COMPANY, DIV OF CBS CORP.
To:
Shared Package
ML20012G055	List: ET-NRC-92-3738, Forwards Nonproprietary & Proprietary WCAP-13486 & WCAP-11693,Rev 3, Grafter:Microcomputer-Based Code Sys to Construct & Quantify Fault Trees. Proprietary WCAP-11693, Rev 3 Withheld (Ref 10CFR9.17(a)(4)) ML20114D963 ML20114E006
References
PROJECT-676A WCAP-13486, NUDOCS 9209100308
Download: ML20114E006 (22)

Text

- . . _ - - - - ~~'T-- - - - - - - .

o ..

~. .

a M

j: a

(

4.-

l

.*' [ g  ?

8

- r, ,.

.yf .

y

• _.

g j  !

f Y

~

.\ l

- , m_x -

h &

[gunwar

, , a i '

l r

_ L_ 1 t

k m ^

3 '

khk ims .l j ,

w ,, , ,.c ,

c .

c

- o  ; ,

I .ll ,

-j pi AnC1 O ** .- ..

t _S " .___ -

ppgenwwwm

-kmp %m

r. wwwwwhw  :

-r ~y n + mm r ,m

=g]y%w yU- s

? Cm 8

s..em

, MW > x, c .m:yo ~ : Ay ; m. +

w_J <u e r4 w:A p i N.:' Q t ,sN,sn'v g--;e ,

r +,a

.?.

,~p q

+<a i

- l;

.x 77 ., n ~ : . pt 8p; , , s. ,

9: ; . ;

Q r rt

-aMM Y

.g N Ak1 - Y s - .r '?

p s .

a.

.f h

g A

,9

• gi Q' , +

-;gg 4;f t:

4 , , , , ,

. .j j

. Qi1 ' '

&,,s -

,, , , ; . :...,,> - . ...., b. , . ,', w 9

~

_; Ir , n;mg m =r p ,

n - -

n o 4, i:

. 4,s.

. u 3,WECiPROPRIETARYs,CG,SSt33*1n s ip:

,9 >q*.-

71.s  ;

4~ -

n

, , c .;p%

p .gacw um y.*,

g

t,

~

x _9

,n i.

m s 4 y: , ,, -A . =) y1 u- -

• 4 1

./r ;L * ,.c. , g. 4 U 4 . tp; ; .! +s 7s s m vp( 3 tre 4, i, i ) y w M< w.7

,, y ,- /r. p

-L 4, mjr3 *i ,

• , i j 4 pt.c _: s .- 6 1y n [e. v e

s 3 ,,s m x-

--a 3

9>2 ( ,l o~ a -'s r' 6

. . up 7s3 i I. m s - .p ,;4, 1c- s ~i ;,4- y a; $t . . i . -4 w h. .

'_~

3_ s 4 4 a we ,

., , - ; ; , - e. $.9 - v. ,  % c.

r

• ],,a

, . 3

)  : 1P  % c~ "Q-

~@%m ,; '" .m, J y

-( t  :

.,m [ G .

g .

1; .,,,

,-- m s e aov' s , , 4

-.a . ,

m? V '

• a h

j.NL ,, .  ; -ib .

> W_ , Yawig&n '

' ~

s

< J. e

'?:,-

' L^

. l a

,?}4

^', Q y, @y. ' h H:p nn,u;a A

- , , seca:L;;www

+g

,x < w ha x% % , , Q;,:t_ , x p, +~,<;,> ~,

M ,[k', 9:

dd j&b M.[ , . ' b ,

W 3g T *

> ,1 s n m , . . ,

v f

a W~ . . a3 , g Q 4' 3.,

n t

+

, f"q. ;:>- Q y

a __ .y ,-. {z _-

=b,

[_

ff' E y

y ~.Mp p&l.

a .

4 f ." , - -- ----: = , <

lN hm r --

. y;$ htw- e. + mlGj %Q w,

c~

i. tga-sy4.-

% we >

c :'S.,. ,.,

D.'-

til n

vm L,

e s

.g 9

m' '

, 2 , ,

'T,.vtf d'-

i ef' i "2,~' )

N L 4  : .

. :. a A .-_Ig 9I .r , 4 n : i. 6 Nd -[ -

N; ,' ( .i.C h.glyhI). ,N' h[' ,

a " .f ' , '

. . '4 4 N *. .( S v p 'k lghghy;. , m . ps y 4 i. - .

1. -h ' -(( '$

q  ; g -, y * ',, %y; ,dq _g -

y m gb.c .y f jt .

,A p . q w ,L 3. . f:h; .q vr. , ,y s:;j, t yn ;Q M

$' l, E N

• l s'; ,M (Y ['u-

j. ;a;'] *

' '?_~ '

4/ 3 ...__

v.

{=

OI 1 Q ay,w ' nd 4 b , . .

p11 aL ;Ny:@e: "[o[ R V, . ,

< 4 6

, .3u po

= sr ,- ,

( .: Ys.9:4 3 V AC g- Wi 'su ,;

- p?

h^ - ',f.R.

, ^ff, ' e s , > , ;, .4  :. }'

Qt ' L Yi% iA

%y,msAm ' ug ;  %" ,'

ne x;

}, O

- ;';e y >

.:;;i %W)9- .miie

'yt m. . % u e 3, .

. . s.,w. - ,,

-x e-T, s . -

gt n ,, ,u,_

=

MN ,M g[. V7 s ed MM MQM;k. _ x 'sqqq [ w ,'_

-j y  ;  %, g g y hD , -

b , ]{"I " ["" 7 y n, - ,

N# "[T@ c.

myy.

A.

w wWM&pp nwDJ %n, ^n,f/ '

4 f., ,s ,* s O

~~ ,

• 3 M

Wi -P g ,

y ,

s < L , s i6: , p b

_i n y u A L. , p i,b .1/ ,,c.

. , h. r a y < 7 L

-- at migest , aon, ~ r ~  % ,c5-": e . s , ,~ ' ,WO 'A>qN d

T%n;M i L.gN. d b.A 4 ,% % - w NU '

W, ,. -[ a s t

Of' g:; ,( * ,

,+

Of i. d i

4 n& 4>,4p'pb,jq%yan1'. v mi i M' 1o-

~

~,gM , W. s. 4[ .f.s ,W "e[ , c *"g w

5

< n ~, mJ~+

r .

u'<

1

v. i. w,a, m c e 4

i bn q; -

y b, . 3. . . " -t U ,

M,, ,

, , , yt

<p"'

' n. s Mj .

s A 4 Q) mb s i R.i t

• , < , y*., , }WTs 3 4# f fs Ul l

' ~

f - l}$ ', r

}_

v

~s n [~U 3 ; w,"L: ~ ,y 3,g ., , ,~.,c nn, -

s ,7 +

~

+ p , c.

s y >: a . .  ;,_ , ,n

• y p d,

k.w, ;%y > - g ,m f e o.- ,. ,n %s a ,p;. A,wo q- ,.,,4 -, .-3y;v. ; e , s qua .. , .. ru (

~- r q o

' < C 9,/ p/ x..

,.,~,

-%h 7 (.k 7  ;

J f,. , $mf ' w

• gsi M 6 d M Y Y j a ,'_'w[, ' d . .-

5 >

+j g s .7 ,

m' ].

g'g ,? e, m ,,

' % W, ,y. 4

==m

+

e g wg ; y1W ,

p Qk]>h Wp; s

Nh% N $N

-M -

[s "

e N b,. bh ee awwn.u.e w +aan . -mu ax s

== n c yWy w&m, .M~ 4 as.: .

gi me r

- g: >i w$ a/.

. u .~ -

07 w '.

n o qi +

x m ge w 8,s:> , -. c -

'Dxr ,hl'p?4emO? $_W '3 a[&: f,f_ .

Y' ,r/. k, ~Nd < h!Vg ( Rh i- N .w Oh }y '*

_x ym .f . r y% O Y. -a AQiq

_3, WMW c MW.

as1 y$. , %r. -

9 &. ", k,3.-p.

a7 f< n . J

.9 -

M e e

n, n_ .m. mM,n'3 - 3. 6+a ' $. 6 ^,-

n

@. f . 5 -.3- ,t .n' '. ' .se. m.w h, sa 4A "'  ! '

m wd y k l ,:L &

~. . -

.w iM a3 i e qh,T' '

=- ,

m'~ &w; A )yg :MgM)n% . fy s nd D

3 ; ?..

a V L N&M+:;%,& M a,v%yWMW  % ' ' '.' ,

I t- >  : ,

9 MW- %,.p ho% m &y I; s o Mg.!- d

.-'egM@%e s: ne,m.u m%;p~

\

.c . ~.

.a s

axmm - h 1 we

w 1 mm m me u e sco' m-er 1

~wt %w .e... %m . Mgas 4 m t, ,

Ass < . ,

+

m.

v h

• Ih y[ .h

}4 .f M:P' r f

k [ f i ..

, ,th i Ay-i.,.,

9~ p. s yr r?p3Y:t y N e y2 sq 1

<?

m

%.4 y. w';;f

w. qms % p& i f n?.:. u- < . s  ?, r N% 1

- 23 i'*-vJm

~

, +m:. amg?:?. w, ,my4%,yl:f_: x ww.') s: m w',' ' t zs t k nc a. m ~ d f..,uR

.mn )-

* - * %i '(5  !>

k Y 'I N Y.

-3 i t  % $ ,E cw 1

] 4 _,

m q j- r l^ ~ ~ \_m ' ";q ' ;

y g_. -' p'. u w' v a.g- -w, y  %.

- t -

g y. , ' Y 'Ik' q g r, i g, n}N f, e'gsy ,?l &gg'A'Q

• I',&

N ,

c p31fx .g; qh :s gu .. me y ? . ywtn %e( a:9 lg%s

' c'

-l Q 7

,n }% ,,

d'Qlps#,l*# , j &- . -w. y 3me3,' N

}

%u wm ' n t.

q W R.

• l ,

%, ~

1 O w, ye  % y

&- ._ ,as ..e +;

4 QY - - -i

' % "%,bw_ ;F '

k t?.31 Q hyn N *) , _. 1 My#rf['n WMb .[Q.? . Nd;[i Y '

_.  ; /J hk /<M, ' hy[ M, h Q h,+ 4 3 5

UN P- ..

Mk ,

_p g.

p _ rq_+?, . .& >

r.... '

3 s y

. h t+

t _?g f-(p

+ ./t e :n h

f 0

)i

. R'vn,-

?

h gi,; ~_- { f f -a

[~h sh'. ,, m f <g'q.&;

>%q e M _

.% n; A <

f y@w:,Y n & O f< w s

,-yOg 4:w J ~Q+y% wp ' W.4 3 % s 4.. -O1

+ g~ 1s s a'" s ,

7

&, [.m CM. g  ; v fM

. . ' ^

i . ' d[W % - ,4VK &," 'i xym -

s% , .s gj# '[

33

$ nn

} y A' ,,I-[ %f V,latn .

-)

r. ,.fs.

m i;; ' 7e .n

'yy

.a.'.'.i s' y s

I m.,, . . ,

gh. <, ,p 3

.. p

' n'lO r e,1 .k

. %pgg~ ',6

&# i

d. *[-' e'gf q

%J

'~ * ' c %- f" 1 -44' ' i Yh* Jj

=W

&. gpN'$ ,, p, &'

• N. J

> .x 4

-W w'

.?.

, D , ti e . _ ' "J .

V > 4 )c'

• 2:\ y ', t ns > ,

> < -m

(

'f b N- -

6

'~ b

'(kA .p .w  ;' h' <3

% 1 ,s.

> a p" ,

W M, n,s , [ 's'p c a s w

.=j ..

J E -

s --A. .;a

- 3 ;

4,314 3..v s

~

@. g,; m pig 3 "3~'N**s&g x yg J j g. j ( ' , 4g7 .

j ,' ;g g3 , i

(.

'&g y m w 3 q k ' m%g',

L y -M - ~

>&c

,M ' ,+

4 hg' ' n an w#

g/

E Mi C ,

Dib

&,1;$dl9 M 2 k

4 [' [ fD.y.) ~ r 4 l pp ' *' ' " W[ mp sQ 2% hM h 6M.[L C'W h# Qi4Ms ?QyE ( -# % 4} , *.< ,

f 9209100308 920828 +

s jf ..  ? 9 2 4 PDR _ADOCK 052***** g r. @N '

4 lf d r6 s @< " T p W, . 5 3 g yJ..'ih Wi' s

A PDR -

g., g> p<4 39 ^ -

,g ' J - -y wn e,wr-m w ym w mo W W, a,*s ',m W- e,

.1 s . qv e m % . ...w u, " . . . - , - .. . m m'. . . . , , , 4 w , M,n." :&wyJ y,x, p' .,: ' , m_

-- < w~ ,- - J.A.

.a. J, .

w bnt .LL. , y ns! \ m

. .n 3 R

- WESTINGHOUSE PROPRIETARY CLASS 3

WCAP 134865 GRAFTER: A Microcomputer-Based Code System to Construct and Quantify Fault Trees

. Prepared by

- Barry D, Sloane Isaac T.Wallace August 1992 g-l Westinghouse Electric Corporation :

' Risk Management and Operations improvement

. P.O. Box 355 Pittsburgh, PA 15230-0355 Copyright

• 1989 -

. Westinghouse Electric Corporation .

. Allrights reserved.

suj TABLE OF CONTENTS 1 INTRODUCTION . . 1 1.1~ 8ackground Information About the G RAFTER Code System - Version 1.6 1 1.2 Fault Tree Analysis , , 1 1.3 GRAFTER Operation . . .. . . . I 1.4 Computer Equipment Required ... 2 1.5 Code Installation . . . . .. . . 2 1.6 File Structures , . . 2 1.7 Modeling Capabilities . 3 1.8 New Featuresin Version 1.6 . 3 1.9 Reporting Code Problems . . , 4 1.10 Formulas . .. .-. . . . . . 4 1.11 Conventions Used in This Manual . 5 2 OPERATING INSTRUCTIONS , 7 2.1 General .. , 7 2.2 Keyboard Function Keys .. . . 7 2.3 Running the GRAFTER Code System . . . 9 2.4 - Construction and Quantification of a New Fault Tree . . . 9 2.5 Preparation and Editing of a Master Data File , 12 2.6 Printing the Fault Tree Structure . . 15 2.7 Printing the Master Data File .. 15 2.8 Printing Other Information . , 15 2.9 Editing an Existing Fault Tree . . 16 2.10 Editing a Fault Tree Data File . .... . 16 2.11 Preparation of Additional Cases . . , 17 2.11.1 Case With Different Data File informa* ion . . . 17 2.11.2 Simulated Failure of a Portion of the Fault Tree . 18 2.11.3 Requantifications Usir Sifferent Parameters .. 18 2.12 GRAFTER Code System Files . , . . . 19 2.12.1 Input Files . . . . . 19 23444/111389 GRAFTER Code system user Manual Versson 1.6; Revusson 0 10/89

sw s i:

TABLE OF CONTENTS (continued) 2.12.2 Files Generated by Computer Activity . 19 2.12.3 Files That May Be Printed 19 2.13 List of Selected GRAFTER Commands . 20 3 CODE OUTPUT . . . .. , 27 3.1 Option 1: Print Tree Data Summary , 27 _

3.2 Option 2: Print Cutset and Probability Results . 27 3.3 Option 3: Print Component importance Results 27 3.4 Option 4: Print Tree Data and All Results . 28 3.5 Other O.Jtput Cptions . . . . 28 4 RUNNING THE FAULT TREE CODES EXTERNAL TO THE MENU SYSTEM 33 4.1 GRAFTER 2 - Code for Fault Tree Construction / Editing . . 33 4.2 SIMONS-Code for Data input . . 34 4.3 WESLGE - Code for Fault Tree Quantification .. . .. . 35 4.4 COMP 2 - Code for Component importance Ranking 37 5 BATCH QUANTIFICATION AND PRINTOUT . .. .. 39 6 FAULT TREE EDITOR , . , 43 6.1 Constructionof FaultTrees . . .. . . . . . . . 43

- 6.2 Function Keys .. . .. . 51 6.3 Symbols .. .. . . . ... . 52 6.4 Modules . . . . . . . . . 55 6.5 Fault Tree Printing ... . . . . 56 7 DATA FILE PREPARATION . . . 57 7.1 Introduction . . . . 57 7.2 File Format . . . . .. . . 57 8 MASTER DATA FILE PREPARATION . . . .. 61 8.1 Introduction . . . . . . . 61 23444/111389 GRAFTER Code System User Manuel Veesson 1.6; Revision (

70/B$

1 J

w.s 1

i l

TABLE OF CONTENTS (continued) \

8.2 File Format . . . . . . . .. . 61 9 GRAFTER UTILITY CODES . .. . 67 9.1 - Introduction . . . . . . .. 67 9.2 - TREPLT: Fault Tree Plotting . . . . . 67

9.3 COMPTRE

Fault Tree Plotting for CALCOMP'" Plotters . 68 9.4 SET 5tN2: GRAFTER to SETS File Conversion . . . 71 9.5 BAYES 3 Bayesiar5 Updating' .... . . . 77

9.6 LOGNOR

Lognormal Distribution Calculations . . . 93 9.7 SDE: Simon Master Data File Editor . . . 96

9.8 SIMED

Fault Tree Data File Editor . . . . .. , 102 9,9 DBPRINT/DBREAD: Fault Tree to ASCll File Conversion . .. . . 108 9.10 SCE: System Cutset Editor . . . .. . . ... . . 110 9.11 CUTDES: Cutset Descriptive Text Code . . 118 App A FO RM U LAS , . . . .. , . . .. . . . . . 123 AppB ERROR ME55 AGES ..... . . . . . 127 App C ERROR PEPORTING .... .. . .. . . ,. . 133 D0126:10-020890 GRAFTER Code Systern User Manual Version 1.6; Revosion 1 02/90

,.7 LIST OFILLUSTRATIONS 2-1 GRAFTER Code System Flow Chart Showing Various Screens and Menus 25 6-1 Screen Displays and Menus 44 6-2 Full screen in Edit Mode , 47 6-3 Screen Displaying Fault Tree Symbols 53 6-4 Sample Fault Tree Module 55 234MI111389 GRAFTER Code System User Manual Venson 1.6; Revssion 0 10/89

sv-9 LISTOF TABLES 2-1 Sample FTA.DAT File 13 3-1 Cutsets and Unavailability 29 3-2 Component importance . .

32 Sample Batch and Response Files 41 5-1 7-1 Sample Data File input . . 59 7-2 Sample Data File Output 60 8-1 Sample Master Data File input .

63 8-2 Sample Master Data File Output . . 65 9.31 COMPTRE Prompts and Sample Responses .

70 9.5-1 BAYES 3.IN File for Default Lornormal Option 1 .

81 9.5-2 Screen Display and input for Option 1 (Sample Problem 1) 85 9.5-3. Screen Display and input for Option 2 (Sample Problem 2) . 86 9.5-4 Input File for Sample Problem 3 . ..

88 9.55 Output File for Sample Problem 1 .

. 89 9.5-6 Output File for Sample Problem 2 . . . 92a 9.5-7 Output File for Sample Problem 3 92c 9.5-8 BAYES 3 Warning Messages- .

92d 9.6-1 LOGNOR Menu Options and Screen Output . . 94 -.

9.6-2 . LOGNOR Output File .,.. . 95 9.7 1 Sample (SIMON) Master Data File input .. . 97 9.8-1 Sample Fault Tree Data File input . 103 9.9-1 DBPRINT Prompts and Responses . ... . . 109 9.9-2 DBREAD Prompts and Responses . 109 9.10-1 ' Example COMP 5 File for SCE . . . . . . 112 9.10-2 Example MODES File for SCE , .. . 112 9.10 3 Example input File for SCE . . . 114 9.10-4 Example Output File from SCE . 115 9.10-5 Example Output Report File from SCE , . 116 9.11 1 Sample CUTDES input File . . . . . 119 9.11-2 Sample Output File from CUTDES . . . . . 120 GRAFTER Coda System User Manual Version 1.6; Revision 1 D0126:10-020890 02/90

s M.11 LIST OF EFFECTIVE PAGES Page Revision Date Page Revision Date fm1 1 02/90 12 0 10/89 fm2 - - 13 0 10/89 fm3 0 10/89 14 0 10/89 fmd 0 10/89 15 0 10/89 fm5 1 02/90 16 0 10/89 fm6 - - 17 0 10/89 fm7 0 10/89 18 0 10/80 fm8 - - 19 0 10/89 fm9 1 02/90 20 0 10/89 fm10 - - 21 0 10/89 fm11 1 02/90 22 0 10/89 fm12 1 02/90 23 0 10/89 fm13 1 02/90 24 - -

fm14 1 02/90 25 0 10/89 1 0 10/89 26 - -

2 0 10/89 27 0 10/89 3 0 10/89 28 0 10/89 4- 0 10/89 29 0 10/89 5 0 10/89- 30 0 10/89 6 - - 31 0 10/89 0 10/89 32 0 10/89 7

8 0 10/89 33 0 10/89 0 10/89 34 0 10/89 9

0 10/89 35 0 10/89

-10 0 10/89 36 0 10/89 11 GRAFTER Code system user Manual Vernon 1.6; Revtson 1 00126:10 '20890 02/90

FM 12 _

LIST OF EFFECTIVE PAGES Page Revision . Da+t .- Page Revision Date 37- 0 10/89 62 0 10/89 38 -0 ,

10/89- 63 0 10/89 39 0 10/89 64 0 10/89 40 0 10/89 65 0 10/89 41 0 10/89 66 - -

42 - - 67 0 10/89-43 0 10/89- 68 0 10/89 44 0 10/89 69 0 10/89 45 0- 10/89 70 0 10/89-

46. 0 10/89 71 0 10/89

47. 0 10/89 72 0 10/89

-48 0 10/89 73 -0 10/89 49 0 10/89 74 0 10/89 50 0 10/89 75- 0 10/89 51 ~' 0 - 10/89 76 1 02/90

52. 0. 10/89 77 1 02/90 53 0~ 10/89 78 1 02/90 54 ~ 0- 10/89 79- 1 02/90 55 0 10/89- 80 1 02/90 i

!. 56 0 10/89 81~ 1 02/90-l -

L 57 0 10/89 82 1 02/90 l'

'58. 0 -10/89 83 1- 02/90

-59 0 10/89 - 84 1 02/90 g 60 . 0 10/89 - -85 1 02/90 61- .0 10/89 86 1 02/90 L-l1 ~ 00126:10 020890 GRAFTER Code System User Manual versson 1.6; Revision 1 I(7c 02/90

. _ ~- , -

s v.13 ,

LIST OF EFFECTIVE PAGES Page Revision Date Page Revision Opit 87 1 02/90 108 0 10/89 88 1 02/90 109 0 10/69 89 1 02/90 110 0 10/89 90 1 02/90 111 0 10/89 91 1 02190 112 0 10/89

• 2- 1 02/90 113 0 10/89 92a 1 02/90 114 0 10/89 92b 1 02/90 115 0 10/89 92c 1 02/90 116 0 10/89 92d 1 02/90 117 0 10/89 l 93 0 10/89 118 0 10/89 94 0 10/89 119 0 10/89 95 ') 10/89 120 0 10/89 96 ) 10/89 121 0 10/89 97 0 10/89 122 - -

98 -0 10/89 123 0 10/89 99 0 10/89 124 0 10/89 100 0 10/89 125 0 10/89 101 0 10/89 126 - -

102 0 10/89 127 0 10/89 103 0 i 10/89 128 0 10/89 104 0 10/89 129 0 10/89 105 0 10/89 130 0 10/89 106 0 10/89 131 0 10/89 107 0 10/89 132 - -

D0126:10 020090 GRATTER Code system user Manual version 1.6; Revision 1 02!90

n 14 LIST OF EFFECTIVE PAGES Page Revision Date Page Rev{:; ion Date 133 0 10/89 137 0 10/89 134 - - 138 - -

135 0 10/89 139 0 10/89 136 - - 140 - -

D0126:10-020890 GRAFTER Code System User Manual Version 16; Revision 1 02/90

1 1 INTRODUCTION

1.1 BACKGROUND

INFORMATlON ABOUT THE GRAFTER CODE SYSTEM - VERSION 1.6 The GRAFTER Code System is a menu driven system of computer codes used to assist in the construction, quantification, and documentation of fault tree analysis. The code system functions in an interactive manner using an IBM AT or PS/2 microcomputer (and some compatibles).

This manual documents the GRAFTER Code System and gives instructions for using it. This manual is not meant to provide detailed instruction in fault tree analysis techniques, nor to define the terms used; it is assumed that the user has this knowledge. The user should also be familiar with the operating system and general operation of a personal computer, and the GRAFTER Code System should already be properlyloaded on the computer and,if possible, tested by a Westinghouse representative.

1.2 FAULT TREE ANALYSl$

A fault tree is a quantified logic diagram showing the various paths of failures and combinations of failures that can lead to an undesired event (top event) for the system being studied. The fault tree analysis determines the probability of occurrence of each path, as well as the logical sum ofinese probabilities, which is the probability of failure of the undesired event of the system as a whole. TF $

analysis also identifies the dominant failure paths and ranks the importances of the individual fail-ures. The fault tree maylead to the discovery of complex failure conditions of significant probability which may not be recognized otherwise.

In constructing the fault tree logic diagrarn, the effects of failures progress from the bottom of the structure (terminal nodes) upward through logic gates to the top undesired event (root node). Stan-dard symbols depict the events and logic Cates. Fauit trees may consist of a few gates and events or several hundred or more, depending on the design cf the system and the level of detail of the analy.

sis. This collection of events, gates, values and labels are the features necessary to describe a fault tree; The GRAFTER Code System facilitates rapid construction and quantification of fault trees.

1.3 GRAFTER CODE SYSTEM OPERA (10N The GRAFTER Code System is structured as a menu driven program that guides users through the desired fault tree operations (construction. quantificaticn, etc.). However, for more experienced users, the routines that perform these operations can be executed individually, or in a batch mode, to speed the process. The main GRAFTER Code System routines are as follows:

e FTA11 - This is the menu routine, which is normally executed via the FTA batch file. (See Section 2).

e- GRAFTER 2 -The fault tree construction and editing routine. (See Section 6).

• SIMONS - The routine that creates fault tree data files and updates fault tree basic event failure rates via the master data file (See Section 7).

23444:111389 GRAFTER Code System user Manual Vemon 1.6; Revmon 0 10iS9

2 I

e WESCUT/W5ESLGE - The f ault tree quantification routines. The main routine is WESLGE; WESCUT allows quantification of smaller f ault trees (up to 300 gates / basic events) when less than 580 kBytes of RAM are available (e g., when a network or other special device driver are installed). (See Section 8) e UTILITIES and EDITORS- w m e a number of special function utilities routines and screen >

editors that allow for fi.4 - : ta manipulation, master data file preparation, pnnting and plotting of fault trees and iesults, and so forth. A "cutset editor" routine (SCE)is also included to allow rapid sensitivity studies without full quantifications. The individual routines are described in Section 9.

1.4 COMPUTER EQUIPMENT REQUIRED The GRAFTER Code System operates with the following recommended computer configuration: IBM.

AT or PS/2 (model 50 or above) with 640K memory, hard disk, and DOS 3.0 or above. The computer configuration must also have a color graphics board. An Epson FX 286 or FX 1050 dot matrix printer is required for printing f ault trees from within the faul; tree edito* but other printers and plotters can be used for external file and tree pnnting.

Contact Westir ghouse Risk Management and Operatior.s Improvement for information about other computer equipment configurations.

1.5 CODE INSTALLATION The GRAFTER Code System must be installed in a directory called CODES, under the root directory of any logical drive (for example, C:\ CODES). The CODES directory must be included in the PATH statement in the system's AUTOEXEC. BAT file (refer to the DOS manual); the CONFIG.5YS file must contain the statements FILES = 20 and BREAK = ON, and must n,.ojinclude the DEVICE = AMt.SYS driver. When quantifying fault trees, the code requires most of the computer's availabit - . dom access memory; it may be necessary to remove other memory resident software from memory before quantifying.

1.6 FILE STRUCTURES The GRAFTER Code System utilizes a series of data files for representation of fault trees, fault tree event probabilities, and failure rate libraries. For a typical project, the following files are created by the user; e A master data file (SIMON.DAT) containing failure rates (mean and variance) for each failure mode for each component expecteo to be encountered in the project analysis.

• Fault tree files (treename.DAT and treename.TXT), one set for each f ault tree created, which represent the fault tree picture and text.

• Fault tree data files (treename.5IM), which contain information linking the f ault tree basic events to corresponding master data file entries; there can be several different data files for a given tree, representing different cases for quantification.

. Fault tree quantification results files.

~

l:

2344M111389 GRAFTER Code system user Manual Verstora l.6; Revtsson 0 10tB9

]

These files are further described in section 2.

ti MODEUNG CAPABILITIES The following fault tree size / structure limitations apply when using the GRAFTER Code System:

e A fault tree may have up to 2000 gates and basic events (combined total) dunng f ault tree construction.

e For quantification and cutset identification, the limit is a combined total of 640 basic events and gates per fault tree. Dunng quantification the code internally restructures the fault tree so that each gate has, at most, two inputs; combination gates t *,.1 transfers are also expanded.

Therefore,in most cases, the number of user specified gates will be automaticallyincreased; this expanded sum is limited to 640 gates.

e The maximum number of cutsets (failure combinations) allowed for each gate is 2000.

However, this maximum is inversely proportional to the number of basic events in the tree (See appendix B).

e Names of basic and system (undeveloped) events may be up to 16 characters in length.

e Basic event names may include blanks or special characters except for period (.), but three names are reserved; components cannot be named "END," "STOP " or "PMIN."

1.8 NEW FEATURE 51N VER510N 1.6 The following new features have been added to the GRAFTER Code System.

. GRAFTER now allows creation and quantification of fault trees with event identifiers of up to 16-characters (instead of the old limit of 10) for basic and undeveloped events Files created with previous versions of the code will work with Version 1.6 without modification.

e The G RAFTER Utilities (the data handling, file preparation, and print / plot routines that had previously been issued as prototypes) have been expanded and configured, and can now be accessed via the menu system Included in these are specialized text editors for use in preparing fault tree data files and master data files in the proper format, and a "Cutset Editor" for use in performing fault tree results sensitivity studies without requantifying. These utilities are described in Section 9 of this manual.

e The menu system has been enhanced to provide additional fun:tions and software integration.

A " command line" feature has been added to allow execution of any valid DOS command, including other programs such as text editors, spreadsheet programs, and so forth; a " file directory" feature has been added to allow searches for files (with wildcards if desired)in any directory or drive; and a " view / print file" feature allows scanning or printing of any ASCil file on the computer without leaving the program.

e A number of user-requested enhancements have been made to the fault tree editor (GRAFTER 2), in addition to the 16-character identifier capability. These enhancements allow greater functionality for fault tree linking, and should eliminate those situations that 234 w 111.189 GRAFTER Code system User Manual Versron 1.6:Rension 0 10/89

4 I

occasionally arose where data was lost if the wrong function key was pressed. Among the enhancements are:

- Automatic checking of event and transfer identifiers as they are entered, with a display notification if the identifier has been used in the tree previously;

- Ability to use duplicated event identifiers instead of transfers, and ability to create trees with transfer mismatches (e.g., transfer in without matching transfer s,a) when desired, with notification on screen and in any quantification files created;

- An option allowing "save full tree as subtree* from any gate in the tree;

- Improvements in the Find option to allow use of upper and lower case search entries, and a better display of find failure messages; On screen display of the pathnames of both the full fault tree file and the last accessed subtree file; A " confirm print" feature to prevent unwanted printing if the F7 or F9 keys are inadvertently pressed, and a " pause printing" feature to allow halting f ault tree printout initiated via the F7 or F9 keys without booting out of the editor or losing unsaved data; and

- Removal of the annoying " beep" and delay experienced when attempting to move the tree cursor in a direction where the limit had been reached.

In addition, the editor displays a banner message indicating the version, and a configuration control message can be displayed for QA purposes by pressing the F2 key, e A second quantification routine (WESCUT) has been added, to allow quantification of smaller f ault trees (up to 300 gates / basic events) when available memory is less than the 590 kilobytes of random access memory (RAM) required for the main quantification routine (WESLGE);

WESCUT requires only about 400 kilobytes of RAM, and so can typically be run with network or other device driversinstalled, e Two GRAFTER routines are now shared with the Westinghouse WLINKtm Fault Tree Linking Code System for efficiency. These are COMPLNK, which replaces COMP 2 as the GRAFTER component importance calculation routine, and SCE, the cutset editor.

1.9 REPOR11NG CODE PROBLEMS 11is Westinghouse policy to encourage identification and reporting of code problems. Appendix C of this manual contains some troubleshooting suggestions and information about reporting problems in the GRAFTER Code System.

1.10 FORMULAS The key formulas used in the quantification of the fault trees are presented in appendix A.

23444:111389 GRAFTER Code system UserManual version 1.6; Revtsion 0

\

10i*9 l i

S 1.11 CONVENTIONS USED IN THIS MANUAL Angle beackets surround the names of keys: for example, < CTRL > and < F7>. Also, names of keys are shown in all capitalletters. Square brackets surround the names of optier.s and commands selected from the menus, unless these options and commands are otherwise set of f from normal text.

Notes are indented 1 inch frcm both margins, and cautions are indented 1 inch from both margins and set in italic type.

]

The tables showing sample screens are reproductions of the screens, not actual screens, due to the limitations met in producing the manual. For example,in the first section of table 3-1, the type has J

been reduced in size and shown in a slightly different type style than that normally viewed on the j screen. The information shown is accurate, however.

]

l 23444/111389 GRAFTER Code $ystem User Manual . Version 1.6; Revwon 0 10/89

(a.c)

'l Pages 7 through 132 WlV4%1M*2792 i

. . . . . . - ..-.--_,..,,,,_._.._~,..;_-_,....---,...-....-..,,_...,...._.--_...,,-_..._.

133 APPENDIX C: REPORTING CODEPROBLEMS If you have a problem with the GRAFTER Code System, the difficulty could be due to any of several reasons, typically involving one or more of the following:

e Hardware / system problem e Software problem o Operator / user error if a problem is encotantered, all three of these areas should be investigated carefully by reviewing the app!! cable section of this user manual. If, after reviewing these areas of concern, the problem ;till exists,the prob!em should be reported to Westinghouse Risk Management and Operations improvement technical support either by phone or on the enclosed form. Initial reporting may be done by phone. However,if the problem is not resolved on the phone, the enclosed form should be used to document the problem.

Before notifying technical support (either the designated Westinghouse engineer or your normal risk management contact), please do the f ollowing:

e Attempt to solve the problem by ref erring to the applicable section this manual.

e Review your PC, printer, cables, and all necessary peripherals to ensure that they are installed as described in this manual.

e Review all applicable input and output files to ensure that their format matches the sample files included in this manual.

If the problem is to be reported in writing, please complete a copy of the enclosed form (attach additional sheets if necessary) and mailit to the address shown on the form. Document all key strokes leading to the error. Applicable files should be recorded both as a hard copy and on a 51- or 3f-inch diskette; submit with the form so that the error can be recreated. (if requested, your diskette will be returned to you upon resolution of the problem.)

When the problem is resolved by technical support, you will be notified either by phone or in writing (as appropriate) concerning the cause and resolution of the problem.

If the problem cannot be readily resolved (if an error in the software has been detected as a result of the problem report), the Westinghouse engineer responsible for the GRAFTER Code System will notify all registered users of both the problem and the recommencied resolution, per Westinghouse Risk Management procedures. If such a problem has been reported by a user outside of Westinghouse, a Westinghouse engineer will be assigned to investigate the extent of the problem, if such a problem is identified by a Westinghouse user, it is that person's responsibility to investigate the extent of the problem.

I X1269'082792 GRAFTER Code system user Manual version 16; Revision 0 10/89

135 WESTINGHOUSE GRAFTER CODE SYSTEM PROBLEM REPORTING FORM Submitted by: Date:

Company:

Address: Phone:

GRAFTER Code System Version Number:

Does this problem have a potentialimpact on plant safety or licensing?

Does this problem result in nonconservative analysis results?

Detailed description of the problem (attach additional sheets if necessary):

)

List attached sample files:

List files on attached diskette:

Send form to: Westinghouse Risk Management and Operations improvement AtMntion: GRAFTER Retoonsible Engineer P. O. eok RS, Ma!!StrT 3-09E Pitts'ourgh. PA W220-0355 X1269!082792 GRAFTER Code system user Manual Verston 16; Revision 0 10:89

137 WESTINGHOUSE GRAFTER CODE SYSTEM PROBLEM REPORTING FORM Submitted by: Date:

Company: _

Address: Phone:

GRAFTER Code System Version Number: ,

Does this prot,iem have a potentialimpact on plant safety or licensing?

Does this problem result in nonconservative analysis results?

Detailed description of the problem (attach additional sheets if necessary):

List attached sample files:

List files on attached diskette:

l

- Send form to: Westinghouse Risk Management and Operations improvement Attention: GRAFTER Responsible Engineer P O. Box 355, Mail Stop 3-09E Pittsburgh, PA 15230 0355 X1269/082792 GRAFTER Code $ptem user Manual Version 1.6; Revision 0

-10/89

139 WESTINGHOUSE GRAFTER CODE SYSTEM PROBLEM REPORTING FORM Submitted by: Date:

Company:

Aodress: Phone:

GRAFTER Code System Version Number:

Does this problem have a potential impact on plant safety or licensing?

Does this problem result in nonconservative analysis results?.

Detailed description of the problem (attach additional sheets if necessary):

Un attachad sample files:

Ust files on attached diskette:

Send form to: Westinghouse Risk Management and Operations improvement Attention: GRAFTER Responsible Engineer P. O. Box 355, Mail Stop 3-09E Pittsburgh, PA 15230-0355 Xt269:082792 GRAFTER Code system user Manual version 1.6; Revision 0 10:89

.-