crystal river unit 3 fault tree model saphire 6.0 … · the crystal river unit 3 plant risk model...

CRYSTAL RIVER UNIT 3 FAULT TREE MODEL SAPHIRE 6.0 DATABASE September 22, 1998

CRYSTAL RIVER UNIT 1

FLORIDA POWER CORPORATION

LEVEL 1

PROBABILISTIC RISK ASSESSMENT DATABASE

FOR USE WITH SAPHIRE WINDOWS 6.0

Richard D. Fowler

September 22, 1998

This database was developed in accordance with the requirements of the NRC's Plant Database Development for SAPHIRE project: Job Code Number (JCN) W6241).


FAULT TREE MODEL

SAPHIRE 6.0 DATABASE

September 22, 1998

NOTICE

This report was prepared as an account of work sponsored by an agency

of the United States Government. Neither the United States Government

nor any agency thereof, nor any of their employees, makes any

warranty, express or implied, or assumes any legal liability or

responsibility for any third party's use, or the results of such use,

of any information, apparatus, product, or process disclosed in this

report, or represents that its use by such third party would not

infringe privately owned rights. The views expressed in this report

are not necessarily those of the U.S. Nuclear Regulatory Commission.


CRYSTAL RIVER UNIT 3 SAPHIRE 6.0 FAULT TREE MODEL

If problems, errors, or discrepancies are encountered when using this database, you are encouraged to call Ms. Erasmia Lois of the U.S. Nuclear Regulatory Commission's office of Regulatory Research at (301) 415-6560 or R. D. Fowler or Mr. T. J. Leahy at the Idaho National Engineering and Environmental Laboratory (INEEL) at (208) 526-1257 and (208) 526-4944, respectively. We are interested in any feedback that you may have, whether positive or negative.

BACKUP THE DATABASE

You are encouraged to ensure that the database is backed up to prevent unintentional destruction or modification of the original database.

SAPHIRE CODE

The Windows Version 6.57 of the Systems Analysis Programs for Hands-on Integrated Reliability Evaluations (SAPHIRE) was used in creating this database. This database must be used with this (or a later) version of the code. If code related problems are encountered, you may call those persons noted above, or the developer of SAPHIRE, Mr. Kenneth D. Russell at (208) 526-9592.


CONTENTS

1. INTRODUCTION .......... ............... 1.1 Purpose ......... .............. 1.2 Objective ......... ............. 1.3 Scope ........... ...............

2. SAPHIRE CODE .......... ...............

3. PRA RELATED INFORMATION .........

4. CRYSTAL RIVER UNIT 3 PRA MODEL ... ......

5. SAPHIRE DATABASE ........ ............. 5.1 Dominant Accident Sequence Results 5.2 Change Sets and Flag Sets ........

6.0 QUALITY ASSURANCE CHECKS ........

7. DATA PROBLEMS AND MODIFICATIONS ........ 7.1 Event Tree Data ....... .......... 7.2 Fault Tree Data ....... .......... 7.3 Basic Event Data ......... 7.4 Fault Tree Gate Data ....... 7.5 Uncertainty Data ......... 7.6 System Cut Set Results ......

8. GUIDANCE FOR USING THE DATABASE ........

9.0 REFERENCES .......... ...............

APPENDIX A: SAPHIRE SEQUENCE RESULTS FOR THE CRYSTAL RIVERUNIT 3 FAULT TREE MODEL

TABLE

Table A-I. SAPHIRE FAULT TREE CUT SETS FOR CRYSTAL RIVER UNIT 3 ............. ..................

ii

2 2 2

2

2

3

3 3 4

4

4 4 4

5

6

6

8

A-2

A-2

O O

Q • I O


1. INTRODUCTION

This letter report documents the development of the Crystal River Unit 3 fault tree model for use with the U.S. Nuclear Regulatory Commission's (NRC) Systems Analysis Programs for Hands-on Integrated Reliability Evaluations (SAPHIRE) probabilistic risk assessment (PRA) code. The SAPHIRE database is based on the Florida Power Corporation's (FPC's) updated PRA Level I fault tree model. The Individual Plant Examination report for the Crystal River Unit 3 plant dated March 1993 (Reference 1) was used in part for some of the needed data (e.g., system acronyms, component names, and failure mode codes).

The database was developed using the version 6.57 of the SAPHIRE code. This version, or a later version, of the code must be used with this database.

Initially, this database was created for specific NRC needs. The database has since been finalized for inclusion in the NRC's library of plant databases for use with SAPHIRE. Primarily, the database was cleaned up (e.g., where possible, added missing basic event and gate descriptions, and broke up (using the SAPHIRE "page" routine) the larger fault trees into smaller pieces for purpose of readability, quality checked for obvious errors, and rerun to verify reproducibility of the fault tree and sequence results.

The core damage frequency (CDF) associated with solving the SAPHIRE fault tree model using a truncation value of 1E-10 is 1.432E-04/year without recovery, and 1.450E-05/year after recovery and updating the cut sets to 1E-10. A listing of the FPC's accident sequence cut sets for the fault tree model were not available, nor were they solicited from the FPC. Thus, a comparison of the results are not provided in this report. Also, because the fault tree model is a more recent plant model, the results for the fault tree model should not be compared directly with the IPE results. The CDF generated using the fault tree model reasonably reproduces the 1.45E-005/year total CDF reported in the IPE. The IPE uses event trees that are linked to the appropriate system fault tree models.

I


1.1 Purpose

The purpose of the NRC's "Plant Database Development for SAPHIRE project [Job Code Number (JCN) W6241] is to load plant specific PRA and IPE data and information into the NRC's library of plant databases.

1.2 Oblective

Objectives of JCN W6241 are (1) to provide databases containing data and information from selected PRAs/IPEs in a format suitable for NRC applications, and (2) to provide guidance and assistance to other NRC programs.

1.3 Scope

The Crystal River Unit 3 database associated with this report is a revised model of a database completed for another NRC project. The database associated with this report was generated at the request of

the NRC Project Manager (Reference 2), and verbal directions via the telephone.

2. SAPHIRE CODE

The Crystal River database associated with this report was developed

using the Windows version 6.57 of the SAPHIRE Code. The database must

be used with this version (or a later version) of SAPHIRE. The database may not work correctly with earlier versions, and any results generated may be corrupt.

3. PRA RELATED INFORMATION

The Crystal River Unit 3 plant is a Babcock and Wilcox (B&W) loweredloop (LLP) pressurized water reactor (PWR) with a dry ambient type

containment. The plant began commercial operation on March 13, 1977

and is licensed for 2544 MWt operation.

Initially, the Crystal River plant fault tree related SAPHIRE model

was created for specific NRC needs. This database has since been

finalized for inclusion in the NRC's library of plant databases for

use with SAPHIRE. Primarily, the database was cleaned up (e.g., where

2


possible, added missing basic event and gate descriptions, and broke up (using the SAPHIRE "Page Tree" option) the larger fault trees into smaller pieces for purpose of readability, quality checked for obvious errors, and rerun to verify reproducibility of the fault tree and sequence results.

4. CRYSTAL RIVER UNIT 3 PRA MODEL

The Crystal River Unit 3 plant risk model is made up of a master logic diagram (MLD) and associated basic event data. This MLD is a single large fault tree containing 3,732 gates and 4,257 basic events. All failure branches from the accident sequences in the event trees are combined into a single fault tree with top gate CD (Core Damage).

5. SAPHIRE DATABASE

The CAFTA-related MLD model (fault tree top is CD) for Crystal River Unit 3 was reformatted and loaded into SAPHIRE. Problems or modifications required to correctly handle the database in SAPHIRE is in Section 7. A guide to the use of this database is provided in Section 8.

The CDF calculated using the SAPHIRE model for the Crystal River plant is 1.450E-05/yr (with recovery events applied). A cut set "update" with a truncation value of 1E-10 yields a total of 6,903 cut sets.

5.1 Dominant Accident Sequence Results

After loading the initial database, the database was rerun to ensure that the sequence results could be reproduced. The database was cleaned up to the extent possible and the fault trees were paginated (reduced to smaller pieces to enhance viewing on screen or printed copies). Again, the database was run to ensure that the results could be reproduced. Finally, the accident sequence results were generated to a truncation level of 1E-10. A "base case update" was then done to transfer the "current case" results to the "base case." Thus, both cases are identical. The top 158 cut sets above a truncation value of 1E-08 are provided in Appendix A for purpose of reference. These cut sets are equivalent to approximately 70%of the total CDF; i.e., 1.01E05 versus 1.45E-05.

3


FAULT TREE MODEL SAPHIRE 6.0 DATABASE September 22, 1998

5.2 ChanQe Sets and FlaQ Sets

There are no "change sets" or "flag sets" associated with the Crystal River Unit 3 database.

6.0 QUALITY ASSURANCE CHECKS

Quality assurance (QA) checks of the database were restricted to the

limited amount of data available. The data checks made concentrated

on the basic event descriptions, gate descriptions, event tree and

fault tree linking, etc.) It was also verified that the database

consistently reproduced the results.

7. DATA PROBLEMS AND MODIFICATIONS

This section discusses those problems and discrepancies encountered when developing the Crystal River Unit 3 SAPHIRE database. Also, any

modifications to the data or logic models are discussed.

7.1 Event Tree Data

There are not event trees associated with this model.

7.2 Fault Tree Data

The FPC's fault tree is a single large model that includes 3,732 gates

and 4,257 basic events. The primary fault tree (top event is CD)

models the- sequences and associated system/component failures.

This single large fault tree model was reduced to smaller segments

using the SAPHIRE "Page" routine to enhance viewing on the screen or

for transport to a printer. First, the fault tree was manually paged

at the initiator level; MINSEQl through MINSEQ7. Next, the specific

sequences were manually "paged;" AU, AX, MU, MX, RBU, RBX, RU, RXZ,

SU, SX, TBL1U, TBL1L2X, TBLIWX, TBQU, TBQX, TQU, and TQX. This set

the initiator and sequence gates to subtree top gates. Once the

sequences were manually paged the SAPHIRE "Auto Page" option was used

to further reduce the remaining fault tree logic to smaller segments.

The single large fault tree was reduced to 1,721 subtrees.

7.3 Basic Event Data

4


Some changes made to the basic events include the addition of error factors and correlation codes, and setting the calculation type for some events. A report of the affected basic events and related settings can be extracted from the database using the "Report" feature of SAPHIRE. Select the "Report," "Basic Events," and "Probability" menu options for a report of the basic event probability related data (including calculation type). Select the "Report," "Basic Events," and "Uncertainty" menu options for a report of the uncertainty data.

Flag events XFLAG, LUFLAG, RBFLAG, and TBUFLAG were added to the fault tree logic for proper inclusion of recovery events. Given that a certain combination of events occur, the flag event is used as a key for adding the appropriate recovery event.

7.4 Fault Tree Gate Data

The following changes were made to the fault tree logic in the SAPHIRE database. As mentioned above, the fault tree model (CD) was paginated using the SAPHIRE "Page Tree" option; i.e., the fault tree was reduced to smaller pieces to enhance viewing on the screen or hard copies sent to a printer.

Many fault tree gate descriptions are missing from the database. The missing descriptions were not available, nor were the descriptions solicited from the FPC.

7.5 Uncertainty Data

As previously noted in Section 7.3, some changes made to the basic events include the addition of error factors and correlation codes. A report of the basic events and the related uncertainty data can be extracted from the database using the "Report" feature of SAPHIRE. Select the "'Report," "Basic Events," and "Uncertainty" menu options for a report of the uncertainty data. Uncertainty results were generated in the SAPHIRE database. Again, no uncertainty results were available for the FPC model with which to compare.

5


7.6 System Cut Set Results

No system cut set results were available for the FPC's fault tree model with which to compare the SAPHIRE model results. Thus, the original database used to develop the model associated with this report was run to verify that the initial results could be reproduced. The model was again run after breaking up ("paging") the fault trees to ensure the results were consistent with the earlier runs. No changes were noted.

Using a truncation of 1E-10, and after applying recovery events, a total of 13,444 sequence cut sets were generated that yielded a total CDF of 1.45E-05/year. After doing a cut set update using a truncation of 1E-10, the number of cut sets was reduced to 6,903. The top 158 cut sets above 1E-08 are provided in Appendix A for purpose of reference. These cut sets are equivalent to approximately 70%of the total core damage frequency; i.e., 1.010E-05/1.450E-05.

As noted in Section 7.3 flag events XFLAG, LUFLAG, RBFLAG, and TBUFLAG were added to the fault tree logic for proper inclusion of recovery events. Given that a certain combination of events occur, using special rules the flag event is used as a key for adding the appropriate recovery event. These flags will be included as basic events in the cut set results whenever the associated fault tree logic is affected. Because the flags were given a probability of 1.0 they do not contribute to the CDF, but, they may show up as major contributors when solving for basic event importance. Thus, care must be exercised.

8. GUIDANCE FOR USING THE DATABASE

The Crystal River Unit 3 database is basically a large fault tree model (D).

The results for this database can be reproduced simply by solving the fault tree (CD). There are no event tree sequences associated with the database. The total CDF results listed below are dependent upon the truncation value used.

6


Using a truncation value of 1E-08, the CDF results are: 1.273E-04 648 cut sets w/o recovery events applied. 1/027E-05 349 cut sets w/recovery events applied, but without

doing a cut set update. 1.01E-05 158 cut sets w/recovery events applied, and a cut

set update at 1E-08.

Using a truncation value of 1E-10, the CDF results are: 1.432E-04 22,918 cut sets w/o recovery events applied. 1.458E-05 13,444 cut sets w/recovery events applied, but

without doing a cut set update. 1.450E-05 6.903 cut sets w/recovery events applied, and a

cut set update at 1E-10.

The CDF reported in the Crystal River Unit 3 IPE is 1.4E-05/yr. This value was derived by solving the SGTR sequences using a truncation of 1E-09, and all other sequences at a truncation of 1E-08. Although the CDF's listed above for the fault tree model are in reasonable agreement (esp., the 1.45E-05 frequency quantified to 1E-10) with the IPE, the cut set results should not be compared directly because the fault tree model involves data and system models that have been updated since the release of the IPE.

As noted in Section 7.6, some flag events will show up in the cut sets when solving certain logic branches of the fault tree. Because the flags were given a probability of 1.0 they do not contribute to the CDF, but, they may show up as major contributors when solving for basic event importance. Thus, care must be exercised.

7


9.0 REFERENCES

1. Florida Power Corporation, "Crystal River Unit 3 Individual Plant

Examination," March 1993.

2. E-mail, "Technical Direction," July 28, 1998.

8


APPENDIX A

SAPHIRE SEQUENCE RESULTS FOR THE CRYSTAL RIVER UNIT 3

FAULT TREE MODEL

A-1


FAULT TREE MODEL


September 22, 1998

APPENDIX A: SAPHIRE SEQUENCE RESULTS FOR THE CRYSTAL RIVER UNIT 3

FAULT TREE MODEL

Following is a list of those accident sequence cut sets that

contribute 0.1% or more to the total CDF. This includes 158 cut sets above a truncation value of 1.OE-08.

Table A-I. SAPHIRE FAULT TREE CUT SETS FOR CRYSTAL RIVER UNIT 3 (Cut Sets above a truncation of 1.OE-008)

Family-> CRYSTAL-RIVER Fault Tree-> CD Mincut Upper Bound -> 1.450E-005

Cut % Cut No. Set Frequency Cut Sets

2.OOOE-006 7.009E-007 5.042E-007 5.OOOE-007 4.444E-007 4.444E-007 2.756E-007 2.249E-007 1.998E-007 1.998E-007 1.325E-007 1.325E-007 1.325E-007 1.325E-007 1.119E-007 1. 111E-007 1. 111E-007 1. 051E-007 1.006E-007 9.350E-008 9.003E-008 9.003E-008 9.003E-008 9.003E-008 8.915E-008 8.548E-008 8.548E-008 8.548E-008 8.548E-008

S, XFLAG, XHPR12H AC024H, ADGCCFTR, T3, TBUFLAG AC024H, ADGES3AF, ADGES3BF, T3, M, XFLAG, XHPR12H HNOMAINT, LMVSVCCF, S, XFLAG HNOMAINT, LMVRVCCF, S, XFLAG AC024H, ADGCCFTS, T3, TBUFLAG AC024H, ADGES3AF, ADGES3BM, T3, AC024H, ADGES3AA, ADGES3BF, T3, AC024H, ADGES3AF, ADGES3BA, T3,HNOMAINT, HNOMAINT, HNOMAINT, HNOMAINT, HNOMAINT, HNOMAINT, HNOMAINT, LRV0069N,

LMVDV12N, LMV0042N, LMV0043N, LMVDV11N, LPMCCFTS, LMVSVCCF, LMVRVCCF, LRV0070N,

S, SPMDHCAM S, SPMDHCBM S, SPMDHCAM S, SPMDHCBM S, XFLAG M, XFLAG

M, XFLAG

LUFLAG, R

TBUFLAG

TBUFLAG TBUFLAG TBUFLAG

XFLAG XFLAG XFLAG XFLAG

AC0512H, ADGCCFTR, T3, XFLAG A, XALPRH HNOMAINT, LMVDV12N, LPM001AM, S, XFLAG HNOMAINT, LMV0043N, LPM001AM, S, XFLAG HNOMAINT, LMVDV11N, LPM001BM, S, XFLAG HNOMAINT, LMV0042N, LPM001BM, S, XFLAG AC024H, ADGES3AA, ADGES3BM, T3, TBUFLAG HNOMAINT, LMV0042N, LMV0043N, S, XFLAG HNOMAINT, LMV0043N, LMVDV11N, S, XFLAG HNOMAINT, LMVDV11N, LMVDV12N, S, XFLAG HNOMAINT, LMV0042N, LMVDV12N, S, XFLAG

A-2

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29

13.8 4.8 3.5 3.5 3.1 3.1 1.9 1.6 1.4 1.4 0.9 0.9 0.9 0.9 0.8 0.8 0.8 0.7 0.7 0.7 0.6 0.6 0.6 0.6 0.6 0.6 0.6 0.6 0.6

CRYSTAL RIVER UNIT 3 FAULT TREE MODEL

SAPHIRE 6.0 DATABASE September 22, 1998

30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77

ACO24H, ADGES3AA, ADGES3BA, T3, TBUFLAG ACO512H, ADGES3AF, ADGES3EF, T3, XFLAG RRVRC9SC, T6, XFLAG, XHPR12H RRVRC8SC, T6, XFLAG, XHPR12HLSPSCRNP, S, XFLAG ACOS12H, ADGCCFTS, T3,

0.6 0.5 0.5 0.5 0.3 0.3 0.3 0.3 0.3 0.3 0.2 0.2 0.2 0.2 0.2 0.2 0.2 0.2 0.2 0.2 0.2 0.2 0.2 0.2 0.2 0.2 0.2 0.2 0.2 0.2 0.2 0.20.2 0.2 0.2 0.2 0.2 0.2 0.2 0.2 0.2 0.2 0.2 0.2 0.2 0.1 0.1 0.1

LMVDV11N, LMVDV12N, I2MVOO42N, 1XVOO43N, LMVDV11N, LMVOO43N, LMVDV12N, LMV0O42N,

I

I

I

I

I

I

I

I

XFLAG SPMRW3BM, SPMRW3AM, SPMRW3BM, SPMRW3AM, SPNDHCBM, SPMDHCAM, SPMDHCAM, SPMDHCBM,

7 .921E-008

7.237E-008 6. 466E-008 6. 466E-008 4. 400E-008 3. 956E-008 3. 876E-008 3. 876E-008 3. 876E-008 3. 876E-008 3. 314E-008 3. 314E-008 3. 314E-008 3. 314E-008 3. 229E-008 2. 968E-008 2. 96SE-008 2. 926E-008 2. 926E-008 2. 926E-008 2. 869E-008 2. 869E-008 2. 798E-008 2. 577E-008 2.577E-008 2 .577E-008

2. 577E-008 2.577E-008 2. 577E-008 2. 577E-008 2. 455E-008 2. 455E-008 2. 455E-008 2.455E-008 2. 332E-008 2. 332E-008 2 .251E-008 2 .251E-008 2 .251E-008 2. 251E-008 2. 170E-008 2. 137E-008 2.137E-008 2 .137E-008 2.137E-008 1. 911E-008 1 . 911E-008 1. 911E-008

HNOMAINT, LPMCCFTS, M, XFLAG HNOMAINT, LPMOO1BA, S, SPMDHC HNOMAINT, S, SPNDHCAM, SPbdP1I HNOMAINT, LPMOO1AA, S, SPMDHCI HNOMAINT, S, SPMDHCBM, SPMRW31 HNOMAINT, S, SPMDHCBM, SPNDP1. HNOMAINT, HPMOO1CA, S, SPMDHC HNOMAINT, 5, SPNDHCAM, SPNRW3~ HNOMAINT, 5, SAVD178K, SPMDHC HNOMAINT, S, SAVDC18R, SPMDHC HNOMAINT, S, SAVDC17R, SPMDHCI HNOMAINT, S, SAVD177K, SPHDHCI HOO13OM, LMVOO43R, LUFLAG, R HOO13OM, LMVOO42R, LUFLAG, R HNOMAINT, LMVOO42N, LPMOO1BM, HNOMAINT, LM4VOO43N, LPM001AM, HNOMAINT, LMVDV12N, LPMOO1AM, HNOMAINT, LM4VDV11N, LPMOO1BM, ACO24H, DBTALBCX, T3, TEUFLAGHNOMAINT, HNOMAINT, HNOMAINT, HNOMAINT, LMVOO41N, LMVOOO3N, LMVOOO4N,

LMVOO43N, LMVOO42N, LMVDV11N, LMVOO42N, PAVM411C, PAVM412C, PAVM412C,

XFLAG XFLAG XFLAG XFLAG XFLAG XFLAG XFLAG XFLAG

T3, XFLAG

T3, XFLAG T3, XFLAG

%M,

3A,

3M,

3A,

LMVDV11N, M, LMVOO43N, M, LMVDV12N, M, LMVDV12N, M, R, WPMDW1AM, R,WPD1M R, WPbDW1AM,

XFLAG XFLAG XFELAG XFLAG XFLAG XFLAG XFLAG XFLAG XFLAG XFLAG XFLAG

)(FLAG XFLAG XFLAG XFLAG

XFLAG XFLAG XFLAG XF'LAG WPMDW1BM WPNDW1BM WPNDW1BM

A-3

HNOMAINT HNOMAINT HNOMAINT HNOMAINT HNOMAINT HNOMAINT HNOMAINT HNOMAINT AC 0512H, HOO13OM, HOO 13 OM, HNOMAINT [email protected] HNOMAINT AC 5 12H, ACO512H,

ADGES3AF, ADGES3BM, LMVOO42X, LUFLAG, R LMVOO43X, LUFLAG, R LPMCCFTR, S, XFLAG S, SPMR3CFS, XFLAG S, SPMDCCFS, XFLAG

ADGES3AA, ADGES3BF, .ADGES3AF, ADGES3BA,


FAULT TREE MODEL


September 22, 1998

78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125

0.1 0.1 0.1 0.1 0.1 0.1 0.1 0.1 0.1 0.1 0.1 0.1 0.1 0.1 0.1 0.1 0.1 0.1 0.1 0.1 0.1 0.1 0.1 0.1 0.1 0.1 0.1 0.1 0.1 0.1 0.1 0.10.1 0 .1

0.1 0.1 0.1 0.1 0.1 0.1 0.1 0.1 0.1 0.1 0.1 0.1 0.1 0.1

1 . 911E-008 1. 911E-008 1. 911E-008 1.892E-008 1. 892E-008 1. 750E-008 1.750E-008 1.750E-008 1 .750E-008 1 .750E-008 1.750E-008 1.750E-008 1. 668E-008 1 .668E-008 1. 668E-008 1. 668E-008 1 .662E-008 1. 662E-008 1. 662E-008 1. 662E-008 1. 662E-008 1. 662E-008 1. 662E-008 1. 662E-008 1. 662E-008 1. 662E-008 1 .662E-008 1. 662E-008 1 .662E-008 1 .662E-008 1. 584E-008 1. 584E-008 1. 584E-008 1.584E-008 1.584E-008 1.584E-008 1.584E-008 1. 584E-008 1. 437E-008 1 .437E-008 1. 437E-008 1.437E-008 1. 385E-008 1 .385E-008 1.385E-008 1 .385E-008 1. 385E-008 1. 385E-008

LMVOOO3N, LMVO0004N, LMVOO41N, HNOMAINT, HNOMAINT, HNOMAINT, HNOMAINT, HNOMAINT, HNOMAINT, HNOMAINT, HNOMAINT, HNOMAINT, HNOMAINT, HNOMAINT, HNOMAINT, HNOMAINT, HNOMAINT, HNOMAINT, HNOMAINT, HNOMAINT, HNOMAINT, HNOMAINT, MNOMAINT, HNOMAINT, HNOMAINT, HNOMAINT, HNOMAINT, HNOMAINT, HNOMAINT, HNOMAINT, HNOMAINT, HNOMAINT, HNOMAINT, HNOMAINT, HNOMAINT, HNOMAINT, HNOMAINT, HNOMAINT, HNOMAINT, HNOMAINT, HNOMAINT, HNOMAINT, HPMO00iBM, HFMOO1BM, HPMOO1CH, Hpmo 01CM, HPMOO1AM, HPMOO1AM,

PAVM411C, PAVM411C, PAVM412C, S, SHXDC11 S, SHXDC1I LPM0O lAM, LPMOO1AM, LPM0O1AM, LPMOO1BM, LPMOO1AA, LPMO001BM, HPMO00iCA, LPMO01BM, LPM001AM, LPM0O1BM, LPM0O1AM, LMV0O42N, HPMO00iCA, LMVDV12N, LMVDV12N, LMV0042N, LMVDV11N, LMVOO42N, LMVO 04 3N, LMVDV11N, LMV0 04 3N, HPMO001CA, LMVO 04 3N, LMVDV11N, LMVDV12N, LMVDV12N, LMVDV11N, LMVDV12N, LMVOO42N, LMV0042N, LMVDV11N, LMV0O43N, LMVO 04 3N, LMVRVCCF, LMVSVCCF, LMVSVCCF, LMVRVCCF, LMVRVCCF, LMVSVCCF, LMVRVCCF, LM4VSVCCF, LMVRVCCF, LMVSVCCF,

A-4

R, WPMDW1AM, R, WPHDW1AM, R, WPMDW1AM,I 3F, SPbMHCAM, kF, SPMDHCBM, LPMOO1BA, S, S, SPbMP1BA, S, SPMRW3BA, S, SPHDP1AA, LPMOO1BM, S, S, SPMRW3AA, LPMOO1AM, S, S, SAVD177K, S, SAVD178K, S, SAVDC17R, S, SAVDC18R, LPMOO1BA, S, LMVDV11N, S, S, SPMRW3AA, S, SPMDPlAA, S, SPbMPlBA, LPMOO1BA, S, S, SPMRW3BA, S, SPMRW3AA, S, SPMRW3BA, LPMOO1AA, 5, LMVOO42N, 5, S, SPMDP1AA, S, SPbMPlBA, LPM001AA, S, S, SAVD177K, S, SAVD178K, S, SAVDC17R, S, SAVDC18R, S, SAVD178K, S, SAVDC18R, S, SAVD177K, S, SAVDC17R, RRVRC8SC, T6, RRVRC8SC, T6, RRVRC9SC, T6, RRVRC9SC, T6, S, XFLAG S, XFLAG S, XFLAG S, XFLAG S, XFLAG S, XFLAG

W7PNDWlBM 4PNDW1BM qPNDW1BM KFLAG KFLAG (FLAG KI~FAG KFLAG XFLAG (FLAG (FLAG KFLAG KFLAG KFLAG KFLAG (FLAG XFI.AG (FLAG KFLAG KFLAG KFLAG (FLAG (FLAG (FLAG (FLAG (FLAG (FLAG (FLAG (FLAG (FLAG (FLAG (FLAG (FLAG (FLAG KFLAG KFLAG KFLAG (FLAG XFLAG XFLAG XFLAG XFLAG


FAULT TREE MODEL


September 22, 1998

126 127 128 129 130 131 132 133 134 135 136 137 138 139 140

141

142 143 144 145 146 147 148

149

150

151

152

153

154

155

156

157

158

ACO24H, ACB32O9C, ADGES3BF, T3, TEUFLAG ACO24H, ACB321OC, ADGES3AF, T3, TEUFLAG HNOMAINT, LPMOO1AM, S, SHXDC1BF, XFLAG HNOMAINT, LPMOO1BM, S, SHXDC1A.F, XFLAG QAVMS26C, RRVRC8LC, T5, XFLAG, XHPR12H QAVMS26C, RRVRC9LC, T5, XFLAG, XHPR12H ACO512H, ADGES3AA, ADGES3BM, T3, XFLAG LRVOO69N, LRV0O7ON, LUFLAG, S HNOMMINT, LMVDV11bT, S, SHXDC1BF, XFLAG HNOMAINT, I.MVOO43N, S, SHXDC1AF, XFLAG HNOMAINT, LMVDV12N, S, SHXDC1AF, XFLAG HNOMAINT, LMVOO42N, S, SHXDC1BF, XFLAG A, LMVIVCCF ACO512H, ADGES3AA, ADGES3BA, T3, XFLAG

0.1 0.1 0.1 0.1 0.1 0.1 0.1 0.1 0.1 0.1 0.1 0.1 0.1 0.1 0.1

0.1

0.1 0.1 0.1 0.1 0.1 0.1 0.1

0.1

0.1

0.1

0.1

0.1

0.1

0.1

0.1

0.1

0.1

1. 323E-008 1. 323E-008 1.285E-008 1.285E-008 1. 285E-008 1. 285E-008 1.280E-008 1 .237E-008 1 .220E-008 1. 220E-008 1.220E-008 1.220E-008 1.215E-008 1. 137E-008 1. 126E-008

1 . 122E-008

1. l00E-008 1. 069E-008 1. 044E-008 1. 044E-008 1. 044E-008 1. 044E-008 1. 012E-008

1. 012E-008

1. 012E-008

1. 012E-008

1. 012E-008

1. 012E-008

1. 012E-008

1. 012E-008

1.012E-008

1. 012E-008

1. 003E-008

LUFLAG, R, SHXHE1BM, SHXHE1DM

LUFLAG, R, SHXHE1AM, SHXHE1CM

LUFLAG, R, SHXHElAM, SHXHE1BM

LUFLAG, R, SHXHElAM, SHXHE1DM

LUFLAG, R, SHXHE1BM, SHXHE1CM

LUFI.AG, R, SHXHE1AM, SHXHElCM

LUFLAG, R, SHXHE1AM, SHXHElDM

LUFLAG, R, SHXHE1AM, SHXHE1BM

LUFLAG, R, SHXHElBMd, SHXHE1DM

HNOMAINT, HPMCCFTS, LUFLAG, R

A-5

HMVOO53C, LUFLAG, R ATAES3AF, LUFLAG, R LSPSCRNP, RMVRC1 iC, HPMOO1AM, HPMOO10M, HPMO 01 CM, HPM001AM, HPMOO1CH, SPN'DHCAM HPMOO lAM, S PNDHCBM HPMOO1CM, S PHD HCAM HPMOO1CM, S PNDHCAM HPMOO1AM, SPMDHCBM HPMOO1AM, S PMDHCBM HPMOO1AM, SPMDHCBM HPMOO1CM, SPbDHCAM HPMOO1AM, SPbDHCBM HPMO 01CM, SPbDHCAM HMVOO73N,

HMVO257C, HNOMAINT, H00630M

DACPWRNR, HNOMAINT, HOPINJAY

M, XFLAG RSVRC1OC, T4, XFLAG, XHPR12H HPMRCPTY, SPMDHCBM, T10, XFLAG HPMRCPTY, SPMDHCAM, T10, XFLAG HPNRCPTY, SPMDHCAM, TIO, TBUFLAG HPHRCPTY, SPMDHCBM, T10, TBUFLAG LUFLAG, R, SHXHE1BM, SHXHElCM

crystal river unit 3 fault tree model saphire 6.0 … · the crystal river unit 3 plant risk model...

Documents