ML20079H653

Rev 0 to Seabrook Station Writers Guide for Emergency Response Procedures

ML20079H653
Person / Time
Site:	Seabrook
Issue date:	10/31/1983
From:	WESTINGHOUSE OPERATING PLANTS OWNERS GROUP
To:
Shared Package
ML20079H582	List: ML20079H579 ML20079H606 ML20079H653
References
RTR-NUREG-0737, RTR-NUREG-737 GL-82-33, PROC-831031-01, NUDOCS 8401230520
Download: ML20079H653 (277)

Text

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ . _ _ _ _ _ _

L SEABROOK STATION WRITERS GUIDE FOR EMERGENCY RESPONSE PROCEDURES Based in part on the Westinghouse Owner's Group Generic Emergency Response Guidelines Rev. 00 October 1983 8401230520 840117 PDR ADOCK 05000443

. PDR

-~ , . . . .

l l

l ERP WRITEAS GUIDE TABLE OF CONTENTS N-Page

1. Purpose and Scope . . .. . . . . . . . . . . . . . . . . . . . . 1 .

t

2. ERP Designation and Numbering . . . . . . . . . . . . . . . . . . 1 2.1 Procedure Title . . . . . . . . . . . . . . . . . . . . . . 1 2.2 Procedure Numbering . . . . . . . . . . . . . . . . . . . . 1 2.3 Revision Numbering . . . . . . . . . . . . . . . . . . . . . 3 2 .' 4 Page Numbering and Identification . . . . . . . . . . . . . 3

3. Fo rmat . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 3

3.1 Procedure Organization . . . . . . . . . . . . . . . . . . . 3 3.2 Page Formats . . . . . . . . . . . . . . . . . . . . . . . . 3 3.3 Instructional Step Numbering . . . . . . . . . . . . . . . . 4 3.3.1 Immediate Actions . . . . . . . . . . . . . . . . . . 4 3.3.2 Continuous Steps. . . . . . . . . . . . . . . . . . . 4

4. Writing the Procedure . . . . . . . . . . . . . . . . . . . . . . 4 4.1 Cover Sheet. . . . . . . . . . . . . . . . . . . . . . . . . 4 i (' } 4.2 Operator Actions .. . . . . . . . . . . . . . . . . . . . . 5

( ,) 4.2.1 Instruction Steps, Lef t-Hand Column . . . . . . . . . 5 4.2.2 Instructions Steps, Right-Hand Column . . . . . . . . 6 4.2.3 Use of Logic Terms. . . . . . . . . . . . . . . . . . 7 4.2.4 Notes and Cautions. . . . . . . . . . . . . . . . . . 7 4.2.5 Transitions to Other Procedures or Steps. . . . . . . 8 4.2.6 Component Identification. . . . . . . . . . . . . . . 9 4.2.7 Level of Detail . . . . . . . . . . . . . . . . . . . 9 4.2.8 Figures . .. . . . . . . . . . . . . . . . . . . . . 9 4 4.2.9 Tables. . . . . . . . . . . . . . . . . . . . . . . . 10 4.2.10 Attachments . . . . . . . . . . . . . . . . . . . . . 11 4.3 Setpoint and Value Study . . . . . . . . . . . . . . . . . . 11 4.4 Operator Action Summary. . . . . . . . . . . . . . . . . . . 11

5. Status Tree Format. . . . . . . . . . . . . . . . . . . . . . . . 11

6. Mechanics of Style. . . . . . . . . . . . . . . . . . . . . . . . 12 6.1 Spelling . . . . . . . . . . . . . . . . . . . . . . . . . . 12 6.2 Puctuation . . . . . . . . . . . . . . . . . . . . . . . . . 12 6.3 Capitalization . .. . . . . . . . . . . . . . . . . . . . . 12 6.4 Vocabulary . . . .. . . . . . . . . . . . . . . . . . . . . 13

.6.5 Numerical Values . . . . . . . . . . . . . . . . . . . . . . 13 6.6 Abbreviations and Acronyms . . . . . . . . . . . . . . . . . 14 i [s_/\

m

7. Printed Format. . . . . . . . . . . . . . . . . . . . . . . . . . L4

8. Reproduction. . . . . . . . . . . . . . . . . . . . . . . . . . 14

LIST OF TABLES Title Table 1 Procedure Index With WOG Cross Ref erence 2 Abbreviations Used in Procedures 3 Action Verbs 4 Status Tree Color Legend l

O O

_...__.____..~._-_..-__...~.__.______._..-______._____._.-_--_.____ __ _ _ . . _ _

l- ,

f l 1-I l:

j- LIST OF FIGURES

! Figure Title i i

1 Pre printed Page Format  ;

2- . Pre printed Page (2-column) Format '

j 3 DELETED

4' Cover Sheet (s) - Example for E-0 ,

'S Cover Sheet (s) Example for FR-H.4 j 6 Example lustruction Steps .

7 . Example Graph i j 8 Example Table i .9 ' Example ~ ATTACHMENT

[

j 10' Example Operator Action Summary L j-f,

_ 11 Block Status Trees

! I f

i  !

)

i I

i 1.

i' t

[

l

.i i

n G  !

I i

--'-~E-__-- __ _ _____._____mm-__--_wm .---.,,,,_m,r-_rm,.,_ _

. _ , _ . . _ ,wg. _ m m wyy w ,, y

l. Purpose and Scope ,

I,_

\ _,)\ The purpose of this document is to provide administrative and technical guidance on the preparation of Emergency Response Procedures. This guide applies to both Optimal Recovery Procedures, Function Restoration Procedures, and Critical Safety Function Status Trees.

2. ERP Designation and Numbering ERPs specify operator actions to be taken during plant emergency situations to return the-plant to a safe stable condition. Each procedure ahall be uniquely identified to facilitate preparation, review , use, and subsequent revision.

2.1 Procedure Title Every separate procedure shall have its own descriptive name which summarizes the scope of that procedure, or states the event (s) which it is intended to mitigate.

2.2 Procedure Numbering Each separate ' procedure shall be identified in two ways, i.e. ; an alpha-numeric code which is identical to the Westinghouse owners Group (WOG) numbering method and the plant procedure number.

/s

()\ A description of the WOG numbering method is contained in the generic ERG set.

In order to comply with station manual procedure AQL.002 and still retain the Human Factors Engineered Systems developed by the Westinghouse Owners Group (WOG), the emergency procecures must -

undergo a change in the way they were numbered.

The procedure number =ust be in accordance with AQL.002 and will appear in the upper right-hand box of each page. (The WOG iden-tifier.will be called the procedure code and will appear in the upper left-hand box of each page.) WOG numbers must contain the same general form that appears in all WOG Procedures includin'g proper positioning of dots and dashes. For example, E-0, ES-0.1, F R-H .1 Each emergency procedure number will follow Ayl.002 with the first four positions in each of the emergency procedures being the same, '

that is OS13.

e The fif th position will correspond to the main procedures.

OS13 [j[} E-0 Procedures r- s 0S13[1_{ E-1 Procedures

\ /

v

_t-1

OS13 W E-2 Procedures OS13 W E-3 Procedures OS13 W ECA Procedures OS13 W FR Procedures and Status Trees e The sixth position will correspond to the sub procedures.

OS131 W ES-1.1 OS134 W ECA-2.1 Procedure This applies to all procedures except the FR Procedures.

e Af ter the decimal in the other procedures the number will correspond to alternate sub procedures.

OS1340. W Loss of All AC Power Recovery Without SI Required, ECA-0.1 e In the FR Procedures, the sixth position will correspond to the FR category.

OS135 W Status Trees OS135 W Sub-Criticality Procedures

, OS135 W Core Cooling Procedures OS135 W . Heat Sink Procedures e

OS135(_4j Reactor Coolant System Integrity Procedures b Containment Integrity Procedures OS135 W '

OS135 W Reactor Coolant Inventory Procedures e Af ter the decimal in the FR procedures the number will corre-spond to individual procedure in the appropriate categories. .

OS1351.[,1] Response to Nuclear Power Genera-tion /ATWS OS1352. W Response to Degraded Core Cooling

(

2.3 Revision Numbering

- fN :

i i

'- Revision numbering for the WOG code shall be handled as specified in the generic ERG set. A change in the current revision number of WOG ERG does not mandate that the code revision- number also change.

Each new revision of the WOG ERGS will be evaluated on a case-by-case basis. If the new ERG revision has sufficient merit to warrant a plant procedure revision, the ERG revision number used as a basis for the plant procedure will be updated in the code block.

Revision numbering for Errs will be handled in accordance with '

plant administrative procedures.

2.4 Page Numbering and Identification Each page of a procedure will be identified by the procedure title, alpha-numeric designator, "Rev." designator, and date in title blocks at the top of the page. Each page number will be specified as "__ of __", centered on the bottom of the page. The last page of instructions will have the word "END" folicwing the last instruction step.

3. Format The following format is to be applied consistently to all Emergency Response Guidelines:

('"'s)

' 3.1 Procedure Organization All Optimal Recovery Procedures (ORPs) will have three (3) sec-tions. The Cover Sheet will summarize procedure intent and state either entry symptoms or means of entry. The Operator Actions will comprise the bulk of each procedure and present the actual stepwise guidance. The Operator Action Su= mary appears on the back side of each page and provides inf orsation which could direct further operator action at any point in the procedure.

3.2 Page Formats All pages of the Emergency Response Procedures (ERPs) will use the same page structure. This page structure employs a pre printed border to assure all margins are correctly maintained, and pre-printed designator boxes and page cues to assure completeness and

• consistency. (See Figure 1).

The pages for presentation of operator action steps will use a two-column format within the pre printed border. The left-hand column is designated for operator action, and the right-hand column is designated for contingency actions when the expected response is not obtained. These pages will use pre printed title blocks above

/,,,\ the separate columns (including the "s tep" column) for uniformity

( ,)

(See Figure 2).

3.3 Instructional Step Numbering Procedural steps will be numbered as follows:

1. High-level step

a. Substep

1) Detailed instructions (if necessary)

Substeps are lettered sequentially according to expected order of perf o rmance . If the order of substep performance is not important, the substeps are designated by bullets (e). If the logical OR is used, both choices may be designated by bullets. This same num-bering scheme is to be used in both the right and left columns of the guidelines.

3.3.1 Immediate Action Steos For those procedures which can be entered directly based on symp toms , certain initial steps may be designated "immediate actions". This designation implies that those steps may be pertormed by the operat ar, based on his

. memo ry , wi thout reference to the written procedure. These steps should be limited to verifications, if possible.

Immediate action steps are identified by a NOTE (see

/ Section 4.2.4) prior to the first action step.

\x Example:

NOTE: Steps 1 through 10 are LMMEDIATE ACTION steps.

3.3.2 Continuous Steps Many of the operator actions provided in a procedure imply continuous performance throughout the remainder of the procedure. This intent is best conveyed by the use of appropriate action verbs such as monitor, maintain, or control.

4. Writing the Procedure The following format is to be applied consistently when writing Emergency Response Procedures (ERPs):

4.1 Cover Sheet Each cover sheet will contain two explanatory sections in addition to procedure and page designators. The first will be titled

" PURPOSE" and will briefly describe what the procedure is intended f

to do for the operator. The second section is a summa ry of those t conditions which require entry into the procedure. This section V

I

_~ will be titled " SYMPTOMS OR ENTRY CONDITIONS **. Certain procedures such as OS-1300 and OS-1340 can be entered purely based on symp toms; for these procedures, a symptom summary is suf ficient (see Figure 4). For other procedures which can only be entered by transition from previous procedures, a summary of the entry con-dicions (and procedure / step) should be provided (see Figure 5 and 6).

4.2 Operator Actions Steps directing operator action should be written in short and pre-cise language. The statement should present exactly the task which the operator is to perform. The equipment to be operated should be specifically identified, and only those plant parame ters should be specified which are presented by instrumentation available in the control room. (If possible, use of qualified instruments is desired.) It is not necessary to state expectea results of routine taaks or specify instrument usage if qualified instruments are already identified in the main control room.

All steps are assumed to be perf ormed in sequence unless stated otherwise in a preceding NOTE (see Section 4.2.4). To keep the individual steps limited to a single action, or a small number of related actions, any complex evolution should be broken down into composite parts.

i Actions required in a particular step should not be expected to be complete before the next step is begun. If assigned tasks are short, then ene expected action will probably be completed prior to continuing. HowcVer, if an assigned task is very lengthy, addi-tional steps may be perf ormed prior to completion. If a particular task must be completed prior to continuation, this condition must be stated clearly in that step or substep.

Ref er to Figure 6 as an example of the format for presenting opera-tor actions in the following sections.

4.2.1 Instruction Steps, Left-Hand Column The left-hand column of the two-column f o rma t will be used f or operator instruction steps and expected responses.

The following rules of cons truction apply:

e High Level Action steps should begin with an appropriate verb, or verb with modifier.

e Expected responses to operator actions are shown in ALL CAPITAL LETTERS.

e If a step requires multiple substeps, then each substep

- ~' '

will have its own expected response if applicable.

\

e If only a single task is required by the step, the high

,_s level step contains its own EXPECTED RSSPONSE.

(,,)

(

e Lef t-hand column tasks should be specitied in sequence as if they could be performed in that manner. The user wculd normally move down that left-hand column when the expected response to a particular step is obtained.

o When the expected response is not obtained, the user is expected to move to the right-hand column for con-tingency ins tructions.

e All procedures should end with a transition to either another guideline or to some normal plant procedure.

4.2.2 Instruction Steps, Right-Hand Column The right-hand column is used to present continge ncy actions which are to be taken in the event that a stated condition, event, or task in the lef t-hand column does not represent or achieve the expected result. Contingency actions will be specified for steps or substeps for which useful alternatives are available. The following rules apply to the right-hand column:

e Contingency actions should identify directions to override automatic controls and to initiate =anually f}

v what is normally initiated automatically.

e Contingency actions should be numbered consistently with the expected response / action for substeps only. A contingency for a single-task nigh-level step will not be separately numbered but will appear on the same line as its related step.

e If the right-hand column contains multiple contingency actions for a single high-level action in the lef t-hand column, the phrase " Perform the following:" should be used as the introductory high-level statement.

e The user is expected to proceed to the next numbered step or substep in the lef t-hand column af ter taking contingency action in the right-hand column.

e As a general rule, all contingent transitions to other procedures take place out of the righ t-hand column.

(Pre planned transitions may be =ade from the left-hand column.)

e If a contingency action cannot be completed, the user is expected to proceed to the next step or substep in

-~s the lef t-hand column unless specifically instructed

(

's

)

otherwise. When writing the procedure, this rule of usage should be consicered in wording subsequent left-hand column instructions.

f- q.

• If a contingency action must be ccapleted prior to con-

{

tinuing, that instruction must appear explicitly in the

} right-hand column subs tep.

%_/

4.2.3 Use of Logic Terms The logic terms AND, OR, NOT, IF NOT, WREN, can NOT, and THEN, are to be used to describe precisely a set of con-dicions or a sequence of actions. Logic terms will be highlighted for emphasis by capitalizing and underlining.

(See Figure 6.)

The two-column format equates to the following logic: "IF NOT the expected response in the left-hand column, TREN perf orm the contingency action in the right-hand column."

The logic terms should not be repeated in the right-hand column contingency. However, the logic terms may be used to introduce a secondary contingency in the right-hand column.

When action steps are contingent upon certain conditions, the step shall begin with the words IF or WHEN followed by a description of those conditions, a comma, the wo rd TREN, and the action to be taken.

IF is used for an unexpected, but possible condition.

7s

\ '

\

\% _/ WREN is used for an expected condition.

AND calls attention to combinations of conditions and shall be placed between each condition. If more than two conditions are to be combined, a list f o rma t is preferred.

OR implies alternative combinations or conditions. OR means either one, or the other, or both (inclusive).

IF. . .NOT or IF. . .can NOT should be used when an operator must respond to the second of two possible conditions. IF should always be used to specify the first condition.

(The right-hand column of the two-column fo rmat contains an implicit IF NOT.)

4.2.4 Notes and Cautions Because the present action-step wording is reduced to the minimum essential, certain additional inf or=ation is some-times desired, or necessary, and cannot be mercly included in a background document. This non-action information is presented as either a NOTE or a CAUTION. (See Figure 6.)

6 v

-7_

s.~ E

. m.

? 4

\  ?

3 To distinguish this inf ormation from action steps, it will g'~' extend across the entire page and will immediately precede

( j the step to which it applies. Each category (NOTE or CAUTION) will be preceded by its descriptor in. large, bold, letters. Multiple statements included u'nder a single heading shall be separately identified by noting them with bullets (e).

CAUTION' benotes some potential hazard to personnel or.

equipment associated with .the following instructional '

step. A CAUTION may also be used to provide contingent transition based on unf avorable changes in plant con- <

ditions. NOTE is used to present advisory or administra-tive information necessary to support the following action ins t ruc tion.

As a general rule, neither a CAUTION or NOTE will contain an instruction / operator action step; however, reference may be made to expected actions in progress.

4.2.5 Transitions to Other Procedures or Steps CertaIa) conditions require the use of a di$ferent proce-dureso'r step sequence. Transitions are specified by using the words "go to" followed by the procedure designa-

/'~'j tor, title (in CAPITAL LETTERS) and step number.

'~' , Transitions shall NOT contain a " return" feature (i.e. ,

p,h rf orm steps X through Y in some other procedure and the'n ceturn).

Examhle: o ,to ES-0.1, REACTOR TRIP RESPONSE, St ep' 1.'

2 Transitions to a' dif f erent ste' later in the same proce-

~

dure are specified in a similar manner.

-Example: Go to Step 20.

Transitiorsito an earlier step in a procedure are spe- '

cified by using the words " return to".

Example: Return to Step 2.

Transitions to a. step which is. preceded by a CAdTION or NOTE . shall inclade special wording to assure that the CAUTION or NOTE is observed.

Example: If conditions are NOT satisfied, THEN go to Step

22. OBSERVE CAUTION PRIOR TO STEP 22.

3 a .

_g_

k

• ~

f.

1

. &v\

-2. .

t 4.2.6 Component Identification k___ Equipment, controls and displays will be identified in

" operator language" te rms . Standard abbreviations which may be used throughout the guidelines are listed alphabe-tically in Table 2. Since similar components are used in both primary and secondary svstems, it is always necessary to clarify the location, even it the wording appears redundant.

s Example: PCCW vs. SCCW identifies primary component cooling water as distinct f rom the secondary component cooling water.

4.2.7 Level of Detail To allow an operator to ef ficiently execute the action steps in a procedure, all unnecessary detail must be removed. Any information which an operator is expected to know (based on his training and experience) should not be included. Many actuation devices (switched) in the control room are similar, even though the remotely per-f ormed functions are not, so certain action verbs listed here are recommended.

e Use " start /stop" for power-driven rotating equipment.

I i

~-

_ e Use "open/close/ throttle" for valves.

e Use " control" to describe a manually maintained process variable (flow, level, temperature, pressure).

e Use " trip /close" for electrical breakers. (LOCK OUT for breaker switchet with a pull-to-lock f eature. )

e Use " place in standby" to ref er to equipment when actuation is to be controlled by automa tic logic circuitry.

4.2.8 Figures If needed to clarify operator action instructions, figures shall be added to a procedure. Any figure used will be y constructed to fit within the pre printed page format (see Figure 1) . Certain rules of construction will apply- .

e All wording on the figure shall be at least as legible (type size and spacing) as the instruc tion steps in t

guidelines.

-9_

l l

l l

e Each figure will occupy a complete page and will be uniquely identified by a figure number and title. The q , figure number will consist of tne procedure designator, without punctuation, followed by a hyphen and an integer.

Example: Figure OS-1341.1-1 e Figure titles will explain the intent or content of the figure, o The figure number and title will be placed at the bottom of the page just above the printed borcer. l e If the figure is a graph, all the numbers and wording i will be horizontal. By convention, the independent l variable is plotted on the horizontal (X) axis. Grid line density should be consistent with the resolution expected from the draph. Any labeling required on the graph will have a white (not graph) background. Figure 7 is an example figure showing presentation of a graph.

• All figures for a procedure are numbered sequentially l and appear at the end of the procedure. Figure pages are numbered as pages or that procedure. Any figures required for an ATTACHMENT are numbered in sequence

/_ ,

with the procedure figures, but have page numbers corresponding to placement in the attachment.

4.2.9 Tables Tables may be used within the text of a procedure to clearly present a large number of separate options. A table will immediately follow the step or substep which makes use or it. Therefore, it does not require a unique number and title. Any table will be completely enclosec by a distinct outline; if necessary, it may extend into the adjacent column because of this delineation.

All information presented in a table shall be at least as legible (type size and spacing) as the instruc tion steps in the guideline.

All columns and rows of inf ormation in a table will be defined by solid lines.

All' column and row headings shall be presented in upper case type.

Absence of a table element will be indicated by a dash.

, Figure 8 presents a typical table.

~s

r.

4.2.10 Attachments (x

(,,,) Supplementary information or detailed instructions which would unnecessarily complicate the flow of a procedure may be placed in an attachment to that procedure.

' At tachments are identified by the title " ATTACHMENT" followed by a single letter desigr ator. This title is centcred at the top of a standard format page. The pre-printed title blocks will be the same as for the proce-dure, but the attachment pages will be aumbered separately (1 of 2, 2 of 2, etc....)

Physically, ATTACHMENTS will be located after any Figures belonging to procedure. Attachments will use a single-column, full page-width format. Figure 9 is an example ATTACHMENT page.

4.3 Setpoint and Value Study The "SETPOINT AND VALUE STUDY" is a listing of all setpoints and values used in the ERPs and are plant specific to Seabrook Station.

This document provides all applicable setpoints, values, curves and other parameters needed to write the ERPs.

The "SETPOINT AND VALUE STUDY" also includes ref erences, assump-

[ h tions and actual calculations used to derive setpoints and values

\s.,/ and will be maintained as a plant controlled safety related docu-ment for the life of the plant.

4.4 Operator Action Summary The operator action summary appears on the back of each procedure page and is titled "0PERATOR ACTION

SUMMARY

FOR E-X SERIES PROCEDURES". It will use a single-column, full page-width fo rmat.

Each set vf operator information will be numbered sequentially and have an explanatory title. The title will be capitalized and underlined for emphasis. This page contains those important actions which can be performed at any step in the procedures.

Refer to Figure 10,

5. Status Tree Format Critical Safety Function Status Trees are presented in the " block" version and all trees in the set use the same format. Similarly, the trees may be oriented either vertically or horizontally on a page, so long as the orien-tation is consistent over the set. Refer to Figure 11.

Color-coding and/or line pattern coding shall be used f rom each last branch s point to its terminus.

All text on the Status Trees shall be at least as legible (type size and spacing) as the instruction steps in the procedures. Refer to Table 4 for s_/

the color usage legend.

Each status tree shall have at the top of the page, a designator block identical to that used in the standard procedure format, and containing the same information.

Statements shall be worded so that the f avorable response is downward.

Termini shall be ordered so that REDS are unif ormly at the top and GREENS at the bottom. Termini crder should be RED - ORAhGE - YELLOW - GREEN if possible.

CRT presentation of status trees should conf orm to this format for consistency.

6. Mechanics of Style 6.1 Spelling All spelling should be consistent with modern usage as specified in the Oxford Dictionary of the English Language, unabridged version.

6.2 Punctuation

'x Punctuation should be used only as necessary to aid reading and s

) prevent misunderstanding. '4ord order should be selected to require

(' ' a minimum of punctuation. The following rules apply:

• Use a colon to indicate that a list of items is to follow.

Example: Stop the following equipment:

e Use a comma af ter conditional phrases for ease of reading.

Example: IF level exceeds 50%, THEN . . .

• Use parenthesis to indicate alternative items in a guideline.

e Use a period to indicate the end of complete sentences and for indicating the decimal place in numbers.

e Use a dash to separate a required action and its expected response and also to indicate a null table element.

Example: Verify S1 Pump - RUNNING.

6.3 Capitalization Capitalization shall be used in the procedures for emphasis in the

, 1 following cases:

\ ]

^

e Logic terms will be capitalized and underlined.

12 -

__--_________ \

7 s e Expected responses (lef t-hand column of instructions) are capi-talized.

(

l' . e . Titles of procedures will be completely capitalized whenever l referenced within any guideline. {

e Operator action steps may be capitalized FOR EMPHASIS.

e Abbreviations (TABLE 2) are commonly capitalized.

• Section headings on operator action summary pages are capita-lized and underlined.

6.4 Vocabulary Words used in the procedures should convey precise meaning to the trained operator. Simple words having few syllables are preferred.

These are typical of words in common usage.

Verbs with specific meaning should be used. The verb should exactly define the task expected to be performed by the operator.

A list of f requently used verbs is included as Table 3.

Some words have unique meanings as listed below:

7 s, manual (manually) - an action performed by the operator in the

( ) control room. (The word is used in contrast to

\d' an automatic action, which takes place without operator intervention.)

local (locally) - an action performed by an operator outside the control room.

Example: " Locally close valve" means directly turning a handwheel co close a valve.

Inequalities are to be ' expressed in words rather than symbols:

1.e., " greater than, less than". These words are always appropriate for comparing pressures, temperatures, levels and flowrates.

6.5 Numerical values All numerical values presented in the procedures should be con-sistent with what can be read on instruments in the control room (i.e. , consistent with ins t rument scale and range).

The nunber of significant digits presented should be equal to the reading precision of the operator.

A U

- Acceptance values should be stated in such a way that any addition

[s \

and subtraction operations c.re avoided, if possible. This is done

\ by stating acceptance values as limits. Examples: ~2500 psig maxi-mum, 350*F ainimum, between 450*F and 500*F. Tolerances can be expressed by stating the normal value followed by the acceptable range in parenthesis.

Example: 550*F (540*F to 560*F)

I Avoid: 550*F 1 10*F Engineering units should always be specified when presenting numerical values for process parameters. They should be the same as those used on the control room displays.

6.6 Abbreviations and Acronyms Abbreviations and acronyms should be limited to those commonly used by operators. Table 2 lists the most common ones necessary for these procedures. Abbreviations and acronyms should be used when-ever possible to simplify the procedures.

Abbreviations and acronyms f rom Table 2 will be uniformly capita-lized whenever they are used.

7. Printed Format (m\

l .) The final printed format of the procedures will be clear and legible.

Final approved versions may be com=e rcially printed at the option of sta-tien management.

8. Reproduction Procedure reproduction will be done on a standard copier, without signifi-cant loss of legibility. Uncontrolled copies shall be marked "FOR INFORMATION ONLY" or " UNTESTED" for those procedures which have not been validated and verified on the plant simulator or in actual practice.

O V

TA3LE 1

- SEASR00K STATION -

E*.ERCENCY RESPCNSE PROCEOCRI INOEI

/

l ) PROCEDURIl l

soc j CCet I

(/ NL'MBER I  !!*LE I l

05-1300 Reactor Trip or Saf ety injection E-0

. 0 5- L 300.1 Red 14 gnosis E3-0 0 05-1301 Reactor

• rip Response ES-0.1 0$-L302 Natural Circulation Cooldown ES-0.2 05-1303 Natural Circulation Cooldown With Stuem 7oid in 7essel ES-0.3 (dith KVLIS) 05-1304 Na' ural Circulation Cooldown With Steam Void in vessel ES-0.4 (Without RVt!S) 05-1310 Los. of Reactor or Secondary Coolant E-1 0 5-L 310.1 51 Terminatica ES-l.1 0S-1311 Post-LOCA Cooldown and Oepressurization ES-L.2 05-1312 Transfer to Cold Leg Recirculation ES-l.3 05-1313 Transfer to Mot Lea tecirculation ES-1.4 05-1320 Faulted Stesa Oenerstor Isolation h E-2 05-1330 Steam Cenerator Tube Rupture E-3 05-1331 1ost-SG*R Cooldown Using 3ackfill ES-3.1 05-1332 Post-SCTR Cooldown Osing slowdown ES- 3. 2 ,

OS-l333 PostaSCTR Cooldown Using Steam Dumo ES-3.3 0 5-L 340 Loss of All AC Power ECA-0.0 05-1340.1 Loss of All AC Power Recovery Without $1 Required ECA-0.1 05-1340.2 Loss of All AC Power Recoverv Jith 31 Recuired ECA-0.2 05-L341.1 Loss of Emergencf Coolant Recirculation ICA-1.1 05-l341.2 LOCA Outside Containment  ! ECA-1.2 OS-l342.1 Uncontrolled Depressurization of All Steam Generstors ECA-2.1

/ \ ECA-3.1

( i 05-1343.1 SG*R With Loes of Reactor Coolant - Suocooled Recovery ij Desired 05-1343.2 SCTR With Loss of Reactor Coolant - Saturated Recove ry E CA- 3. 2 Desired OS-L343.3 SCTR Without Pressurizer Pressure Control ECA-3.3 05-1350.1 Suberiticality (Critical Safety Function 3tatus Tree) F-0.1 05-1350.2 Core Cooling (Critical Saf ety Function Status Tree) F-0.2 05-1350.3 Seat Sinx (Critical Safety Function Status Tree) F-0.3 05-1350.. Integrity (Critical 3afety Function Status Tree) , F-0.4 0S-1350.5 Containment (Critical Safety Tunction Status Tree) [

F-0.5 05-1350.6 f ,enterv (Critical Safetv Function status Tree) 1 F-0.6 05-1351.1 Response to Nuclear Power ;eneration/A!VS FR-S.1 0S-1351.2 Response to Loss of Core Shutdown FR-5.2 OS-1352.1 Response to Inadequate Core Cooling FR-C.1 05-1352.2 Response to Oegraded Core Cooling TR-C.2 05-1352.3 Response to Saturated Core Cooling Condition FR-C.3 05-1253.1 Response to Loss )f Secondary Meat Sinx FR-M.1 3S-1353.2 Response to 3 team Oecerator Overpressure FR-H.2 05-1353.3 Response to steam Oenerator Hign Level FR-H.3 y 05-1353.4 Response to toss of Steam Oump :apabilities FR-d.4 05-1353.5 Response to Steam Generator Low Levei FR-4.5 OS-1354.l Response to Imminent Pressurized Thermal Shock FR-P.1 Conditions 05-1354.2 R e s pons e to Anticipated Pressurized Thermal Shock FR-P.2 Conditions 05-1355.1 Respouse to 41gh Containment Pressure  !. FR-2.1

/'~~1 05-1355.2 Response to Containment Flooding l FR-!.2

( ) 0$-1355.3 Response to dich containment Radiation Level i FR-3.3 l

I 05-1350.1 Response to High Pressurizer Level 05-1356.2 FR-!.2 OS-L350.3 Response to Low Pressurizer Level Response to voids in Reactor Vessel lFR-I.!

FR-!.3

_--._.-_-______-_..__.m. . _ . . . _

TA2LE 2 COMMON ABBREVIATIONS USED IN PROCEDURES

[\

\s,s ac EFW alternating current (electrical power) emergency feecwater ASDV - atmospheric steam dump valve ATWS -

anticipated transient without scram BA -

boric acid BAT -

boric acid (s torage) tank BIT -

boron injection tank BTRS --

boron thermal regeneration system CCP -

centrifugal charging pump CCW -

component cooling water (preceded by an S or P)

CRDM -

control rod drive mechanism CST -

condensate storage tank CVCS -

chemical and volume control system CVCT -

chemical volume control tank de -

direct current (electrical power and signals)

DG -

diesel generator DWST - demineralized water storage tank EPS -

emergency power sequencer ECCS -

emergency core cooling system HP -

high pressure HX -

heat exchanger LOCA -

loss of coolant accident LOP -

loss of power LP -

low pressure ex MCC -

motor control center (N MD -

motor driven (in reference to pumps)

MSIV -

main steamline isolation valve NIS -

nuclear instrumentatior. s' fstem NR -

narrow range (level indication)

PORV - power operated rplief valve (pressurizer only)

PDP - positive displacement pump PRT - pressurizer relief tank .

PRZR -

pressurizer RAT' - reserve auxiliary transf ormer RCP -

reactor coolant pump RCS -

reactor coolant system RHR -

residual heat removal RMO - remote manual operation (relay designation)

RPV -

reactor pressure vessel RWST -

refueling water storage tank RVLIS - reactor vessel liquid inventory system SI -

safety injection SG -

steam generator SGTR - steam generator tube rup ture I SUR -

startup rate SW - service water TA - tower actuation TC - thermocouple TD - turbine driven (in reference to pu=ps) i TSC - technical support center

('~'j y_

s UAT - unit auxiliary transformer WPB -

waste processing building WR - wide range (level indication)

TABLE 3

(-~.

x ACTION VERES Actuate To put into action or motion; commonly used to refer to automated, multi-f aceted operations.

Examples: Actuate S.I., Actuate Phase A, Actuate Containment Spray Align To arrange components into a desired configuration.

Examples: Align the system for normal charging. Align valves as appropriate.

Block To inhibit an automatic actuation.

. Example: Block Si actuation.

Check To note a condition and compare with some guideline requirement.

Example: Check PRZR level - GREATER THAN 20%.

Close To change the physical position of a mechanical device. Closing a valve pre-vents fluid flow. Closing a breaker allows electrical current flow.

Complete To accomplish specified procedure requirements.

Continue To go on with a particular process.

Example: Continue with this procedure.

Control To manually operate equipment as necessary to satisfy procedure require-ments on process parameters pressure, temperature, level, flow.

Example: Control pressurizer level.

Determine To calculate or evaluate using formula or graphs.

(s Example:

time.

Determine maximum venting

ACTION VERES (CONTINUED)

.,6

.l \ Energize To supply electrical energy to

\s_,/ ( s ome thing) . Commonly used to describe an electrical bus or other dedicated electrical path.

Examples: Energize AC emergency buses.

Energize PRZR heaters.

Enter To insert into or add to.

Establish To make arrangements for a stated con-dition.

Example: Establish normal pressurizer pressure and level control.

Evaluate To examine and decide; commonly used in reference to plant conditions and opera-tions.

Example: Evaluate plant conditions.

Initiate To begin a process.

-"s Example: . Initiate flow to all SGs.

Load To connect an electrical component or u nit- to a source of electrical energy.

May involve a "s tart" in certain cases.

. Example: Load the following equipment on AC equipment buses:

Maintain To control a given plant parameter to some procedure requirement continuously.

Example: Maintain SG level in the narrow range.

Mcnitor Similar to " check", excep t implies a con-tinuous function.

~

Open To change the physical position of a mechanical device to the unobs truc ted position. Opening a valve permits fluid flow. Opening an electrical breaker pre-vents current flow.

Place-in-standby To return a piece of equipment to an f'"'y inactive status but ready for start on

'( ) '

demand; commonly used to ref er to a mid-position on a switch labeled "AUT0".

Example: Stop the pumps and place in standby.

ACTION VERBS (CONTINUED) m

[ ] Reset To remove an active output si dnal f rom a

\, ,/ retentive logical device even with the input signal still present; commonly used in ref erence to protection /saf eguards logics in which the actuating signal is

" locked-in". The RESET allows equipment energized by the initial signal to be de-energized.

Examples: Reset $1, Roset Phase A.

Record To document specified characteristics.

Example: Record RCS average temperature.

Sample To take a representative portion for the I

purpose of examination; commonly used to refer to chemical or radiological exami-nation.

1 I

Examples: Sample for RCS boron concen- l tration. Samples for side activity.

Start To originate motion of an electrical or p -_

mechanical device, either directly or by

( remote control.

L_.);

Example: Start one RCP.

Stop To terminate motion of an electrical or mechanical device.

Example: Stop both diesels.

Throttle To operate a valve in an intermediate position to obtain a certain flow rate.

Example: Throttle flow control valve to establish desired flow.

Trip To manually activate a semi-automatic feature. Commonly, " trip" is used to ref er to component de-activation.

• Examples: Trip the reactor; trip the turbine. Trip a breake r.

Verify To observe that expected characteristic or condition exists. Typically the 7x expectation comes f rom so=e previous (v ) automatic or operator action.

Examples: Verify Reactor Trip, Verify S1 Pumps - RUNNING.

TABLE 4 LF STATUS TREE COLOR LEGEND COLOR CODE Definition )

Green The critical safety' function is satisfied - no

. operator action is called for.

Yellow The critical safety function is not fully satisfied - operator action may eventually be needed.

l Orange The critical safety function is under severe challenge prompt operator action is necessary.

l Red The critical safety function is in jeopardy -

immediate operator action is required.

l i

O

Code: Sy::1ptoc[

Title:

crucecure :o.

Revision No./Date:

I FIGURE 1 Pre-Printed Page Fo rmat

Code: . Symptom /

Title:

Procecure No.

Revision No./Date:

l STEP l l ACTION / EXPECTED RESPONSE l l RESPONSE NOT OBTAINEDl FIGURE 2 ,

Pre-Printed Page (2-Column) Format OM

O Figure 3 Intentionally Left Blank e .

O O

us a

Cods: Symptom /

Title:

Procedure No.

Revision No./ Data:

EO- REACTOR TRIP OR SAFETY INJECTION 0S-1300 Rev. 1 00 / 08/11/83

(

A. PURPOSE l_ FIGURE 4 l This procedure provides actions to verify proper response of the automatic protection systems following manual or automatic actuation of a reactor trip or safety injection, to assess plant conditions, and to identify the appropriate recovery procedure.

B.~ SYMPTOMS OR ENTRY CONDITIONS

1. The following are symptoms that require a reactor trip, if one has not occurred:

FUNCTIONAL UNIT TRIP SETPOINT A. POWER RANGE NEWRON FLUX:

1) IDW SETPOINT . ... . . . . . . . .

1 25% OF RTP

2) HIGH SETPOINT . . . . .. . . . .

1 109% OF RTP B. MWER RANGE, NEUTRON . ... . . . . .

1 5% OF RTP WITH A FLUX, HIGH MSITIVE TIME CONSTANT > 1 RATE SECONDS C. POWER RANGE, NEU1RON . . . .. . . . . .

15% OF RTP WITH A FLUX, HIGH NEGATIVE TIME QNSTANT > 1 RATE SECONDS D. INTERMEDIATE RANGE, . . . .... . . .

1 25% OF RTP NEUTRON FLUX ,

E. SOURCE RANGE, NEWRON . . .. . . . . .

i 10 5 CPS FLUX F. OVERTEMPERATURE AT . . . . . . . . . . .

1 109.95% +_ PENALTIES G. OVERPOWER AT . . . . . . . . . . . . . .

• i 109% - PENALTIES H. PRESSURIZER PRESSURE - . . . . . . . . > 1945 PSIG tow I. PRESSURIZER PRESSURE - . . . . . . . .

12385 PSIG HIGH

~

G _

1 of 26

p Cods: Symptom /

Title:

Procedure No.

Revision No./Date:

E-O ' REACTOR TRIP OR SAFETY INJECTION OS-1300 Rev. 1 00 / 08/11/83 N -

)

s. /

l- [_ FIGURE 4 CONTINUED l (cont.)

FUNCTIONAL UNIT TRIP SETPOINT J. PRESSURIZER WATER . . . . .. . . . . . < 92% OF INSTRUMENT LEVEL--HIGH SPAN K. LOSS OF FLOW . . .. . . . . . . . . . > 90% OF LOOP DESIGN FLOW L. STEAM GENERATOR WATER . . . . . . . . . > 15% OF NARROW RANCE LEVEL - LOW-LOW RAhGE INSTRUMENT SPAN j M. UNDERVOLTAGE - REACTOR . . . . . . . . > 10, 200 VOLTS AC COOLANT PUMPS N. UNDERFREQUENCY - . . . . . . . . . . . > 57.2 Hz REACTOR COOLANT PUMPS P. TURBINE TRIP

1) LOW TRIP SYSTEM . *

~> 800 PSIG f" N PRESSURE

( 2) TURBINE STOP . . . . . . . . . ALL VALVES CLOSED VALVE CLOSURE SAFETY INJECTION . . . . . . . . . . . NA INPUT FROM ESF

2. The following are symptoms of a reactor trip:

a. Any reactor trip annunciator lit,

b. Rapid decrease in neutron level indicated by nuclear instrumen-tation.

c. All shutdown and control rods are fully inserted. Rod bottom lights are lit.

R _,i -

\

2 of 26

Revision So./Date:

OS-1300 E-0 REACTOR TRIP OR SAFETY INJECTION 00 / 08/11/83

s. Rev. 1

! \ -

\ i N ,,!

l FIGURE 4 CONTINUED l

3. The following are sympt. oms that require a reactor trip and safety injection, if one has not occurred:

FUNCTIONAL UNIT SI SETPOINT A. PRESSURIZER PRESSURE - . . . . . . . . > 1350 PSIG LOW B. CONTAINMENT PRESSURE - . . . .. . . . < 4.3 PSIG LOW C. STEAMLINE PRESSURE . . . . . .. . . > 5d5 PSIG LOW f- ,

4. The following are symptoms of a reactor trip and saf ety injection:

I \

i ' a. Any SI annunciator or status lamp lit.

\_. /

b. ECCS pumps in service:

o CENTRIFUGAL CHARGING PUMP (CCP) CS-P-2A e CENTRIFUGAL CHARGING PUMP (CCP) CS-P-23 e SAFETY INJECTION PUMP (SI PUMP) SI-P-6A e SAFETY INJECTION PUMP (SI PUMP) SI-P-oB e RESIDUAL HEAT REMOVAL PUMP (RHR PUMP) RH-P-dA e RESIDUAL HEAT REMOVAL PCMP (RHR PUMP) RH-P-dB

c. Phase A containment isolation.

I h i <

\_f _

3 of 26

Cods: Symptom /

Title:

Procedure No.

Revision No./Date:

FR-H.4 RESPONSE TO LOSS OF NORMAL DUMP 0S-1353.4 Rev. 1 CAPABILITIES 00 / 08/12/83 0-A.- PURPOSE l FIGURE 5l This procedure provides actions ' to respond to a f ailure of the steam generator atmospheric steam dump valved (ASDVs) and condenser steam dump valves.

B. SYMPTOMS OR ENTRY CONDITIONS This procedure is entered from 05-1350.3, HEAT SINK Critical Safety Function Status Tree on a YELLOW condition.

m 1 of 2

Coda: symptom /

Title:

Procecure : o.

Revision No./Dato:

l l E-0 REACTOR TRIP OR SAFETY INJECTION OS-1300 Rev. 1 00 / 06/11/63 t i f\ - l STEP l l ACTION / EXPECTED RESPONSE l l RESPONSE NOT OBTAINED l l FIGURE 6 l 15 Verify ECCS Flow:

a. CCP flow indicators - a. Manually start pumps and CHECK FOR FLOW THROUGH align valves. REFER TO BIT ATTACHMENT A, ECCS VALVE ALIGNMENT - CCP VIA BIT TO RCS.

o. RCS pressure - LESS THAN b. Go to St.ep lb.

1550 PSIG e RC-PI-405 e RC-P I-403

c. SI pump flow indicators - c. Manually start pumps and CHECK FOR FLOW align valves. Refer to ATTACHMENT B, ECCS VALVE e TRAIN A ALIGNMENT - SIP T0 dCS COL 3 e TRAIN 3 LEGS.

i

d. RCS pressure - LESS THAN d. Go to Step lo.

200 PSIG

e. RHR pump flow indicators - e. Manually start pumps and CHECK FOR FLOW align valves. REFER TO ATTACHMENT C, ECCS VALVE e TRAIN A ALIGNI - Ank PLMP T0 e TRAIN B RCS COLD LEGS.

16 Verify EFW Flow - GREATER THAN Manually start pumps. E proper 470 GPM TOTAL COMBINED FLCW TO flow can NOT be established, THEN AT LEAST T40 SGs go to FR-H.1, RESPONSE TO LOSS OF SECONDARY HEAT SINK, STEP 1.

10 o f 26

'OOCE. ' SYMPTCM / TITLI. ?kCCEbUnENO.

RE'/ISION NO. / OAE ALL -

- 'RGs EOL EMERGENCY FEEDWATER ALL OS-1300 FLOW REQUIREMENTS FOR PROCEDURES CORE DECAY HEAT I4EMOVAL 00 / 09/21/83

)

r l FIGURE 7 l l

REQUIRED EFW FLOW TO REMOVE DECAY HEAT I AFTER REACTOR TRIP i i i i i iii i i i l i i ii, i i i iiiii iit itir 700 i

=C 600- - \' H'  !

~

S sco

\A  !

i I'll

.i

'h l 4gg i h,gg - I!

ace A ss '00

'l M 1 .! l ,i O

HR. .I I 10 too 1000 MIN. .6 60 600 6CCO 60p00 I

TIME AFTER SHUTDOWN -

?

NOTES: RCPs RUNNING ASSUMEO 88 : EPN EOL CONDITIONS SGs @ 1200 osia

Cods: Symptom /

Title:

Procedure No.

Rsvision No./Date:

E-0 REACTOR TRIP OR SAFETY INJECTION 0S-1300 Rev. 1 00 / 08/11/83 j (A)

V

~

I STEP l l ACTION / EXPECTED RESPONSE l l RESPONSE NOT OBTAINED l l FIGURE 8 l 18 Verify ECCS Valve Alignment - Manually align valves as PROPER EMERGENCY ALIGNMENT nece ssary .

e CCPs VIA BIT TO RCS COLD LEGS l l

VALVE NOMENCLATURE POSITION CS-V142 CHARGING ISOL. CLOSED CS-V143 CHARGING ISOL. CLOSED CS-LCV-112B CVCT CUTLET CLOSED CS-LCV-112C CVCT OUTLET CLOSED CS-LCV-112D RWST OUTLET OPEN CS-LCV-112E RWST GUTLET OPEN O

{ CS-V844 BIT INLET OPEN CS-V65 BIT INLET OPEN CS-V845 BIT INLET OPEN CS-V66 BIT INLET OPEN CS-V846 BIT BYPAbS CLOSED t

CS-V847 BIT BYPASS CLOSED CS-V165 BIT RECIRC. PUMP DISCdG. CLOSED .)

CS-V173 BIT RECIRC. ISOL. CLOSED CS-V174 BIT RECIRC. ISOL. CLOSED SI-V138 BIT OUTLET TO RCS OPEN I SI-V139 BIT OUTLET TO RCS OPEN O

12 o f 26

Code: Symptom /

Title:

Procedure No.

Revision No./Date:

l STEP l l ACTION / EXPECTED RESPONSE l l RESPONSE NOT OBTAINED I l FIGURE 9 l ATTACHMENT A, The following conditions support or indicate natural circulation flow:

e RCS subcooling - GREATER THAN 50 *F e Steam pressure - STABLE OR DECREASING e RCS ho t leg temperature - STABLE OR DECREASING e- Core exit TCs - STABLE OR DECREASING e RCS cold leg temperatures - NEAR SATURATION TEMPERATURE NR STEAM PRESS URE e Loop AT - INDICATED O

1 of 1

Code: Symptom /

Title:

Procedure No. .

Revision No./Date:

E-O' REACTOR TRIP OR SAFETY INJECTION OS-1300 Rev. 1 00 / 08/08/83 '

1 l STEP l l ACTION / EXPECTED RESPONSE l l RESPONSE NOT OBTAINED l l FIGURE 10 l OPERATOR ACTION

SUMMARY

FOR OS1300 SERIES PROCEDURES

'l.- RCP TRIP CRITERIA

. Trip' all RCPs if BOTH conditions listed below oce s

a. CCPs or SI pumps - AT LEAST ONE RUNNING b.- RCP Trip Parameter - LESS THAN 1375 PSIG

2. SI ACTUATION CRITERIA Actuate SI and go to E-0, REACTOR TRIP OR SAFETY INJECTION, Step 1, if EITHER condition listed below occurs:

o RCS subcooling based on core exit TCs - LESS THAN 30*F e Pressurizer level - CANNOT BE MAINTAINED GREATER THAN 5%

[30% FOR ADVERSE CONTAINMENT]

3.- RED PATH

SUMMARY

a. SUBCRITICALITY - Nuclear power greater than 5%

b. CORE COOLING - Core exit TCs greater eccan 1200*F

-OR-Core exit TCs greater than 700*F AND RVLIS full range less than 40% with no RCPs running c.

HEAT SINK - SG narrow range level in all SGs less than 28%

AND total feedwater flow less than 4 70 gpm i

d. . INTEGRITY - Cold leg temperature decrease greater than 100*F in last 60 minutes AND RCS cold leg temp.:rature l- less ~ than 250*F

)

e. CONTAINMENT - Containment pressure greater than 52 PS1G

4. EFW SUPPLY f1 Commence CST makeup as soon as possible to avoid low inventory problems.

E

\

a)

I

cce. Esrow mu: m e c s cu a e N o. 7 '

REVISION NO. / OATE:

F-o.2 CORE COOLING R EV.1 os-1350.2

_ STATUS TREE 0 o /10 / 2 / 8 3 J

F 3

l l FIGURE 11 l l

GO TO FR C.1 GO TO FR C.1 CORE EXir No ENTER.h rcs LEss IHAN 1200*F yee -

avuS-GREATER "O

THAN 40 % yEs COPE EXIT ' NO e GO TO

- rcsLEss THAN 700*F FR C.2 YES GO TO

/ AT LEAST No 4 FR C.2 k

CNERCP -

hvt..S. NO 9UNNING YES

- GREATER THAN 40% ygg I

GO TO sueco0UNG No FR-C.3 GREATER THAN 30'F ves GO TO

= FR-C2 RVUS-OYNAMIC No HEAD GREATER TH A N

• EE 44 N4Hces

~

30 %3RcPs GO TO 20 S2scas 13 %1 RCPs FR C.3 1 CSF SAT m

(* - . . . - . . .

..._ . ._ J

O 1

SEABROOK STATION WRITERS GUIDE FOR EMERGENCY RESPONSE PROCEDURES .

O Based in part on the Westinghouse Owner's Group Generic Emergency Response Guidelines Post Validation Program Revision January 13, 1984 O

l l

l t

l

, ERP WRITERS GUIDE TABLE OF CONTENTS P, ag,

1. Purpose and Scope . . . . . .. . .. . ... . . . . ..... . 1

2. ERP Designation and Numbering . . . . . . .. . . . . ..... . 1 2.1 Procedure Title . . .. . . . .. . . ... . . . .. .. . 1 2.2 Procedure Numbering ... . .. . . .. .. . . . . .. .. 1 2.3 Revision Numbering . . .. . .. . .. . . . . . . . . . . . 3 2.4 Page Numbering and Identification . . . .. . . .. .. . . 3

3. Format . . . . . . . . . . . . . . . . .. . . . . . . . . . . . 3 3

3.1 Procedure Organization . . . ... . . .. . . . ..... . 3 3.2 Page Formats . . . . . . . . . . .. .. . . . . . . . . . . 3 3.3 Instruccianal Step Numbering . . . . . . . . . . . . .. . . 4 3.3.1 Immediate Actions . . .. . . . . . . . . . . . .. . 4 3.3.2 Continuous Steps. . . .. . ... .. .. ..... . 4

4. Writing the Procedure . . . .. . . . . . . . .. . .!. . . . . . 4 c

s 4.1 Cover Sheet. . .. . . . . . . . . . . . . . . . ... . . . 4 4.2 Operator Actions . . . .. . . . . . .. . . . . .. . . . . 5 4.2.1 Instruction Steps, Left-Hand Column . . ....... 5 4.2.2 Instructions Steps, Right-Hand Column . . .... . . 6 4.2.3 Use of Logic Terms. . .. . . . . . . . . ..... . 7 4.2.4 Notes and Cautions. . . . . . . . . . . .. . . . . . 7 4.2.5 Transitions to Other Procedures or Steps. ..... . 8 4.2.6 Component Identification. ... .. . . . ..... . 9 4.2.7 Le ve l o f De ta il . . . . . . . . . . . . . . . . . . . 9 4.2.8 Figures . . . . . . . . . . . . . . . . ... . .. . 9 4.2.9 Tables. . . . . .. . . . . .. . . . . .. . . . . . 10 4.2.10 Attachments . . .. . . . . . . . . . . ...... . 11 4.3 Setpoint and Value Study . . . . . . . . . . . . . . . . . 11 4.4 Operator Action Summary. . . .... . . . . . ...... . 11

5. Status Tree Format. .. . . . . . . . . . .. . . . .. . . .. . 11

6. Mechanics of Style. ... . . . . . . . . . . . . . ...... . 12 6.1 Spelling . . . . . . . . . . .. . .. . . . . ... . . . . 12 6.2 Puctuation . . .. . .. . . .. . .. . .. . . . .-. . . 12 6.3 Capitalization . . . . . . . .. . . . . . . . . .. . . . . 12 6.4 Vocabulary . . .. . .. . . . . . . . . . . . ... ... . 13 6.5 Numerical Values . . . . . . . . . . . . . . . ... . .. . 13 6.6 Abbreviations and Acronyms . . . . . . . .. . . ..... . 14

() 7. Printed Format. . . . . . . . . . . . . . .. . . .. ... .. . 14

8. Reproduction. . . . . . . .. . . . . . . . . . . . ... ..

. 14

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

.__.-p._..-___- _

, , e. p '

V 4

i ,

/ / l l-1 s

6 '%

f LIST OF TABLES t

!- Table -/ Title i l

1 -l Procedure Index With WOG Cross Reference '

'2 Abbreviations Used in Procedures  !

3 Action Verbs '

Status Tree Color Legend '

4 '-

' 3 >3

\

I 3 s

[$

$ f J~ ,

i 1 I 9 I i '

j 's +

)

i I t r ,

P W

f 1

)

i +

{

I1 1 -

t l

• l a

I t.

~'

J. ...

i 1,T ,

l

-t 4

4s y

f

)a I

.1 -

t a-I. g'.

? f 3 . f[_ ,

{

, s

+

kft_'t

.4 4

s s

w e i, r ).

9.J 1 h'

...._m..__.__.____._.._____..______..__________..__.__._._-..,____,___._

~

1<

s LIST OF FIGURES O-Figure Title 1 Pre printed Page Format 2 Pre printed Page (2-column) Format

, 3 Step Numbering Example 4 Cover Sheet (s) Example for E-0 5 Cover Sheet (s) Example for FR-II.4 1- 6 Example Instruction Steps

<7 Example Graph 8 Example Table l

.' ; > 9 Example ATTACHMENT 10 Example Operator Action Summary 11 Block Status Trees O

's i

O

______O.___._

1. Purpose and'Scoge The purpose of this document is to provide administrative and technical guidance on the preparation of Emergency Response Procedures. This guide applies to both Optimal Recovery Procedures, Function Restoration Procedures, and Critical Safety Function Status Trees.

2. ERP Designation and Numbering ERPs specify operator actions to be taken during plant emergency situations to return the plant to a safe stable condition. Each procedure shall be uniquely identified to facilitate preparation, review, use, and subsequent revision.

2.1 Procedure Title Every separate procedure shall have its own descriptive name which summarizes the scope of that procedure, or states the event (s) which it is intended to mitigate.

2.2 Procedure Numbering 1.

Each separate procedure shall be identified in two ways, i.e.; an alpha-numeric code which is identical to the Westinghouse Owners l Group (WOG) numbering method and the plant procedure number.

1 [\ A description of the WOG numbering method is contained in the

[

generic ERG set.

(

In order to comply with station manual procedure AQl.002 and still retain the Human Factors Engineered Systems developed by the Westinghouse Owners Group (WOG), the emergency procedures must undergo a change in the way they were numbered.

The procedure number must be~in accordance with AQ1.002 and will appear in the upper right-hand box of each page. (The WOG iden-tifier will be called the procedure code and will appear in the upper lef t-hand box of each page.) WOG numbers must contain the same general form that appears in all WOG Procedures including proper positioning of does and dashes. For example, E-0, ES-0.1, F R-H . l . Operators will learn and use the WOG codes for procedure use. The plant specific procedure numbers will be used exclusively for document control.

Each emergency procedure number will follow AQ1.002 with the first four positions in each of the emergency procedures being the same, that is OS13.

e The fif th position will correspond to the main procedures.

OS13 (0_[ E-0 Procedures OS13(lj E-1 Procedures n . ., . . - _ _ _ _ _ _ _ _ _ _ _ _ - - ._ -

h OS13l_];t E-2 Procedures OS13 (M E-3 Procedures OS13(4] ECA Procedures 0313 W FR Procedures and Status Trees e The sixth position vill correspond to the sub procedures.

OS131 W ES-1.1 OS134 W ECA-2.1 Procedure This applies to all procedures except the FR Procedures.

e After the decimal in the other procedures the number will correspond to alternate sub procedures.

OS1340.(1] Loss of All AC Power Recovery Without SI Required, ECA-0.1 e In the FR Procedures, the sixth position will correspond to the FR category.

O Status Trees O OS135 LOJ OS135 LM Sub-Criticality Procedures OS135 W Core Cooling Procedures OS135j._3] Heat Sink Procedures OS135 W Reactor Coolant System Integrity Procedures

~

OS135 W Containment Integrity Procedures OS135 (Q Reactor Coolant Inventory Procedures e After the decimal in the FR procedures the number will corre-spond to individual procedure in the appropriate categories.

OS1351.[1] Response to Nuclear Power Genera-tion /ATWS OS1352. W Response to Degraded Core Cooling O

/'N- 2.3 Revision Numbering h

Revision numbering for the WOG code shall be handled as 'specified in the generic ERG set. A change in the current revision number of WOG ERG does not mandate that the code revision number also change.

Each new revision of the WOG ERGS will be evaluated on a case-by-case basis. If the new ERG revision has sufficient merit to warrant a plant procedure revision, the ERG revision number used as a basis for the plant procedure will be updated in the code block.

Revision numbering for ERPs will be handled in accordance with plant administrative procedures.

2.4 Page Numbering and Identification l l l t

Each page of a procedure will be identified by the procedure title, '

l alpha-numeric designator, "Rev." designator, and date in title l blocks at the top of the page. Each page number will be specified l as " of ", centered on the bottom of the page. The last page i of instructions will have the word "END" following the last instruction step.

3. Format The following' format is to be applied consistently to all Emergency Response Procedures:

O b 3.1 Procedure Organization All Optimal Recovery Procedures (ORPs) will have three (3) sec-tions. The Cover Sheet will summarize procedure intent and. state either entry symptoms or means of entry. The Operator Actions will comprise the bulk of each procedure and present the actual stepwise guidance. The Operator Action Summary appears on the back side of each page as applicable and provides information which could direct further operator action at any point in the procedure.

3.2 Page Formats All pages af the Emergency Response Proced'ures (ERPs) will use the same page structure. This page structure employs a pre printed border to ensure all margins are correctl'y maintained, and pre-printed designator boxes and page cues to assure completeness and consistency. (See Figure 1).

The pages for presentation of operator action steps will use a two-column format within the pre printed border. The left-hand column is designated for operator action, and the right-hand column is designated for contingency actions when the expected response is

. not obtained. These pages will use pre printed title blocks above the separate columns (including the " step" column) for uniformity

) (See Figure 2).

/'] 3.3 Instructional Step Numbering

%.)

Procedural steps will be numbered as follows:

1. Righ-level step

a. Substep

1) Detailed instructions (if necessary)

Substeps are lettered sequentially according to expected order of performance. If the order of substep performance is not important, the substeps are designated by bullets (e). If the logical Oft is used, both choices may be designated by bullets. This same nu_m-bering scheme is to be used in both the right and left columns of the guidelines. (See Figure 3).

3.3.1 Immediate' Action Steps For those procedures which can be entered directly based on symptoms, certain initial steps may be designated

'immediate actions". This designation implies that those steps may be performed by the operator, based on his memory, without reference to the written procedure. These steps should be limited to verifications, if possible. f Immediate action steps are identified by a NOTE (see *

(a~') Section 4.2.4) prior to the first action step.

Example:

NOTE: Steps 1 through 10 are D{ MEDIATE ACTION steps.

3.3.2 continuous Steps Many of the operator actions provided in a procedure imply continuous performance throughout the remainder of the procedure. This intent is best conveyed by the use of appropriate action verbs such as monitor, maintain, or control.

4. Writing the Procedure The following format is to be applied consistently when writing Emergency Response Procedures (ERPs):

4.1 Cover Sheet Each cover sheet will contain two explanatory sections in addition to procedure and page designators. The first will be titled

" PURPOSE" and will briefly describe what the procedure is intended to do for the operator. The second section is a summary of those

() conditions which require entry into the procedure. This section

will be titled " SYMPTOMS OR ENTRY CONDITIONS". Certain procedures O. such as E-0 and ECA-0.0 can be entered purely based on symptoms; for these procedures, a symptom summary is sufficient (see Figure 4).

For other procedures which can only be entered by transition from previous procedures, a sumaAry of the entry conditions (and procedure / step) should be provided. (See Figure 5).

4.2 Operator Actions Steps directing operator action should be written in short and pre-cise language. The statement should present exactly the task which the operator is to perform. The equipment to be operated should be specifically identified, and only those plant parameters should be specified which are presented by instrumentation available in the control room. (If possible, use of qualified instruments is desired.). It is not necessary to state expected results of routine tasks or specify instrument usage if qualified instruments are already identified in the main control room.

All steps are assumed to be performed in sequencu unless stated otherwise in a preceding NOTE (see Section 4.2.4). To keep the individual steps limited to a single action, or a small number of

_ related actions, any complex evolution should be broken down into L composite parts.

f Actions required in a particular step should not be expected to be

-()

complete before the next step is begun. If assigned tasks are short, then the expected action will probably be completed prior to continuing. However, if an assigned task is very lengthy, addi-tional steps may be performed prior to completion. If a particular task must be completed prior to continuation, this condition must be stated clearly in that step or substep.

Refer to Figure 6 as an example of the format for presenting opera-tor actions in the following sections.

4.2.1 Instruction Steps, Left-Hand Column The lef t-hand column of the two-column format will be .used for operator instruction steps and expected responses.

The following rules of construction apply:

e High Level Action steps should begin with an appropriate verb, or verb with modifier.

e Expected responses to operator actions are shown in ALL CAPITAL LETTERS.

e If a step requires multiple substeps, then each substep will have its own expected response if applicable.

O .

e If only a single task is required by the step, the high 9'~N level step contains its own EXPECTED RESPONSE.

b e Lef t-hand column tasks should be specified in sequence as if they could be performed in that manner. The user would normally move down that left-hand column when the expected response to a particular step is obtained.

e When the expected response is not obtained, the user is expected to move to the right-hand column for con-tingancy instructions.

e All procedures should end with a transition to either another guideline or to some uurmal plant procedure.

4.2.2 Instruction Steps, Right-Hand Column The right-hand column is used to present contingency actions which are to be taken in the event that a stated condition, event, or task in the lef t-hand column does not represent or achiev- the expected result. Contingency actions will be sp( *fied for steps or substeps for which useful alternatives are available. The following rules apply to the right-hand column:

o Contingency actions should identify directions to override automatic controls and to initiate manually

() what is normally initiated automatically.

e Contingency actions should be numbered consistently with the expected response / action for substeps only. A contingency for a single-task high-level step will not be separately numbered but will appear on the same line as its related step.

e If the right-hand column contains multiple contingency actions for a single high-level actiore in the left-hand column, the phrase " Perform the following:" should be used as the introductory high-level statement.

e The user is expected to proceed to the next numbered step or substep in the left-hand column after taking contingency action in the right-hand column.

e As a general rule, all contingent transitions to other procedures take place out of the right-hand column.

(Pre planned transitions may be made from the left-hand column.)

e If a contingency action cannot be completed, the user is expected to proceed to the next step or substep in the left-hand column unless specifically instructed

()

'~

otherwise. When writing the procedure, this rule of usage should be considered in wording subsequent left-hand column instructions.

(}

N ,'

s e If a contingency action must be completed prior to con-tinuing, that instruction must appear explicitly in the l right-hand column substep.

l l 4.2.3 Use of Logic Terms The logic terms AND, OR, NOT, IF NOT, WHEN, can NOT, and THEN, are to be used t2i describe precisely a set of con-ditions or a sequence of actions. Logic terms will be highlighted for emphasis by capitalizing and underlining.

(See Figure 6.)

The two-column format equates to the following logic: "IF NOT the expected response in the lef t-hand column, THEN perform the contingency action in t'he right-hand column."

The logic terms should not be repeated in the right-hand column contingency. However, the logic terms may be used to introduce a secondary contingency in the right-hand column.

When action steps are contingent upon certain conditions, the step shall begin with the words IF or WHEN followed by a description of those conditions, a comma, the word THEN, and the action to be taken.

~IF is used for an unexpected, but possible condition.

(

\ ') WHEN is used for an expected condition.

AND calls attention to combinations of conditions and shall be placed between each condition. If more than two conditions are to be combined, a list fo rmat is preferred.

OR implies alternative combinations or conditions. OR means either one, or the other, or both (inclusive).--~

IF...NOT or IF...can NOT should be used when an operator must respond Eo the second of two possible conditions. IF should always be used to specify the first condition.

(The right-hand column of the two-column format contains an implicit IF NOT.)

4.2.4 Notes and Cautions Because the present action-step wording is reduced to the minimum essential, certain additional information is some-times desired, or necessary, and cannot be merely included in a background document. This non-action information is presented as either a NOTE or a CAUTION. (See Figure 6.)

b u

(s','N To distinguish this information from action steps, it will

/

extend across the entire page and will immediately precede the step to which it applies. Each category (NOTE or CAUTION) will be preceded by its descriptor in large, bold, letters. Multiple statements included under a single heading shall be separately identified by noting them with bullets (e).

CAUTION denotes some potential hazard to personnel or equipment associated with the following instructional step. A CAUTION _may also be used to provide contingent transition based on unfavorable changes in plant con-ditions. NOTE is used to present advisory or administra-tive information necessary to support the following action instruction.

As a general rule, neither a CAUTION or NOTE will contain an instruction / operator action step; however, reference may be made to expected actions in progress.

4.2.5 Transitions to Other Procedures or Steps

• Certain conditions require the use of a dif ferent proce-dures or step sequence. Transitions are specified by using the words "go to" followed by the procedure designa-tor, title (in CAPITAL LETTERS) and step number.

O Transitions shall NOT contain a " return" feature (i.e.,

perform steps X through Y in some other procedure and then return).

Example: Go to ES-0.1, REACTOR TRIP RESPONSE, Step 1.

Transitions to a different step later in the same proce-dure are specified in a similar manner.

Example: Go to Step 20.

Transitions to an earlier step in a procedure are spe-cified by using the words " return to".

Example: Return to Step 2.

Transitions to a step which is preceded by a CAUTION or NOTE shall include special' wording to assure that the CAUTION or NOTE is observed.

L' Example: If conditions are NOT satisfied, THEN go to Step

22. OBSERVE CAUTION PRIOR TO STEP 22.

O .

-~- --r=- -~m sw

-N- wyM iry-4+.-, g. y -j--,-w.,i --w.-m --

w t.., . - - + - -t-- -+.

k 4.2.5 Component Identification

Equipment, controls and displays will be identified in

" operator language" terms. Standard abbreviations which may be used throughout the guidelines are listed alphabe-tically in Table 2. Since similar components are used in both primary and secondary systems, it is always necessary to clarify the location, even if the wording appears redundant.

Example: PCCW vs. SCCW identifies primary component l cooling water as distinct from the secondary I component cooling water.

4.2.7 Level of Detail i

To allow an operator to efficiently execute the action steps in a procedure, all unnecessary detail must be removed. Any information which an operator is expected to I

know (based on his training and experience) should not be included. Many actuation devices (switches) in the control room are similar, even though the remotely per-formed functions are not, so certain action verbs listed

.here are recommended.

o Use " start /stop" for power-driven rotating equipment.

~ V e Use "open/close/ throttle" for valves.

e Use " control" to describe a manually maintained process variable (flow, level, temperature, pressure).

e Use " trip /close" for electrical breakers. (PULL-TO-LOCK for breaker switches with a pull-to-lock feature).

e Use " place in standby" to refer to equipment when actuation is to be controlled by automatic logic circuitry.

4.2.8 Figures If needed to clarify operator action instructions, figures shall be added to a procedure. Any figure used will be constructed to fit within the pre printed page format (see Figure 1). Certain rules of construction will apply:

e All wording on the figure shall be at least as legible (type size and spacing) as the instruction steps in the guidelines.

O

t e Each figure will occupy a complete page and will be uniquely identified by a figure number and title. The figure number will consist of the procedure designator, without punctuation, followed by a hyphen and an integer.

Example: Figure E-3-1

'o Figure titles will explain the intent or content of the figure.

e The figure number and title will be placed at the top of the page just inside the printed border.

e If the figure is a graph, all the numbers and wording will be horizontal if possible. By convention, the independent variable is plotted on the horizontal (X) axis. Grid line density should be consistent with the resolution expected from the graph. Any labeling required on the graph will have a white (not graph) background. Figure 7 is an example figure showing pre-sentation of a graph.

e All figures for a procedure are numbered sequentially and appear at the end of the' procedure. Figure pages are numbered as pages of that procedure. Any figures

-(} required for an ATTACHMENT are numbered in sequence with the procedure figures, but have page numbers corresponding to placement in the attachment.

4.2.9 Tables Tables may be used within the text of a procedure to r clearly present a large number of separate options. A table will immediately follow the step or substep which makes use of it. Therefore, it does not require a unique number and title. Any table will be completely enclosed by a '.stinct outline; if necessary, it may extend into the adjacent column because of this delineation.

All information presented in a table shall be at least as legible (type size and spacing) as the instruction steps in the guideline.

All columns and rows of information in a table will be defined by solid lines.

All column and row headings shall be presented in upper case type.

, Absence of a table element will be indicated by a dash. l

\~- Figure 8 presents a typical table.

(F'T 4.2.10 Attachments V

Supplementary information or detailed instructions which l would unnecessarily complicate the flow of a procedure may  !'

be placed in an attachment to that procedure.

Attachments are identified by the title " ATTACHMENT" followed by a single letter designator. This title is centered at the top of a standard format page. The pre-printed title blocks will be the same as for the proce- I dure.

Physically, ATTACRMENTs will be located after any Figures l belonging to procedure. Attachments will use a single- l column,-full page-width format. Figure 9 is an example l ATTACHMENT page.

4.3 Setpoint and Value Study The "SETPOINT AND VALUE STUDY" is a listing of the setpoints and values used in the ERPs and are plant specific to Seabrook Station.

This document provides all applicable setpoints, values, curves and other parameters needed for the ERPs. -

The "SETPOINT AND VALUE STUDY" also includes references, assump-fs tions and actual calculations used to derive setpoints and values

.( ) and will be maintained as a plant controlled safety related docu-ment for the life of the plant. This document is updated as necessary with appropriate changes made to ERPs.

4.4 Operator Action Summary The operator action summary appears on the back of applicable pro-cedure pages and is titled "0PERATOR ACTION

SUMMARY

FOR E-X SERIES PROCEDURES". It will use a plain page format for distinction.

Each set of operator information will be numbered sequentially and have an explanatory title. The title will be capitalized and underlined for emphasis. This page contains those important actions which can be performed at any step in the procedures.

Refer to Figure 10,

5. Status Tree Format Critical Safety Function Status Trees are presented in the " block" version and all trees in the set use the same format. Similarly, the trees may be oriented either vertically or horizontally on a page, so long as the orien-tation is consistent over the set. Refer to Figure 11.

Color-coding and/or line pattern coding shall be used from each last branch point to its terminus.

O .

t

- -- l l .-

(} All text on the Status Trees shall be at least as legible (type size and s/ spacing) as the instruction steps in the procedures. Refer to Table 4 for the color usage legend.

Each status tree shall have at the top of the page, a designator block identical to that used in the standard procedure format, and containing the same information.

Statements shall be worded so that the favorable response is downward.

Termini shall be ordered so that REDS are uniformly at the top and GREENS at the bottom. Termini order should be RED - ORANGE - YELLOW - GRE~.N if possible.

CRT presentation of status trees should conform to this format for consistency.

6. Mechanics of Style 6.1 Spelling All spelling should be consistent with modern usage as specified in the Oxford Dictionary of the English Lan2uage, unabridged version.

6.2 Punctuation Punctuation should be used only as necessary to aid reading and

(} prevent misunderstanding. Word order should be selected to require a minimum of punctuation. The following rules apply:

e' Use a colon to indicate that a list of items is to follow.

Example: Stop the following equipment:

e Use a comma after conditional phrases for ease of reading.

Example: IF, level exceeds 50%, THEN . . .

o Use parenthesis to indicate alternative items in a guideline.

e Use a period to indicate the end of complete sentences and for indicating the decimal place in numbers.

e Use a dash to separate a required action and its expected response and also to indicate a null table element.

Example: Verify SI Pump - RUNNING 6.3 Capitalization Capitalization shall be used in the procedures for emphasis in the following cases:

b

\"#

e Logic terms will be capitalized and underlined.

~

e Expected responses (left-hand column of instructions) are capi-

.talized.

e Titles of procedures will be completely capitalized whenever referenced within any guideline.

o Operator action steps may be capitalized FOR EMPHASIS.

e Abbreviations (TABLE 2) are commonly capitalized.

I l

e Section headings on operator action summary pages are capita-lized and underlined.

6.4 Vocabulary Words used in the procedures should convey precise meaning to the trained operator. Simple words having few syllables are preferred.

These are typical of words in common usage.

Verbs with specific meaning should be used. The verb should exactly-define the task expected to be performed by the operator.

A list of frequently used verbs is included as Table 3.

Some words have unique meanings as listed below:

() manual (manually) - an action performed by the operator irt the control room. (The word is used in contrast to an automatic action, which takes place without operator intervention.)

local (locally) - an action performed by an operator ,outside the Control room.

Example: " Locally close valve" means directly turning a handwheel to close a valve.

Inequalities are to be expressed in words rather than symbols:

1.e., " greater than, less than". These words are always appropriate for comparing pressures, temperatures, levels and flowrates.

6.5 Numerical Values All numerical values presented in the procedures should be con-sistent with what can be read on instruments in the control room (i.e., consistent with instrument scale and range).

The number of significant digits presented should be equal to the reading precision of the operator. l I.

/

. _ _ _ _n__-._____ _

Acceptance values should be stated in such a way that any addition g and subtraction operations are avoided, if possible. This is done by stating acceptance values'as limits. E:tamples : 2500 psig maxi-mum, 350*F minimum, between 450*F and 500*F. Tolerances can be expressed by stating the normal value followed by the acceptable range in parenthesis.

Example: 550*F (540*F to 560*F)

Avoid: 550*F + 10*F if possible Engineering units should always be specified when presenting i numerical values for process parameters. They should be the same l as those used on the control room displays.

6.6 Abbreviations and Acronyms Abbreviations and acronyms should be limited to those commonly used by operators. Table 2 lists the most common ones necessary for these procedures. Abbreviations and.. acronyms should be used when-ever possible to simplify the procedures.

Abbreviations and acronyms from Table 2 will be uniformly capita-lized whenever they are used.

7. Printed Format The final printed format of the procedures will be clear and legible.

Final approved versions may be commercially printed at the option of sta-tion management.

8. Reproduction Procedure reproduction will be done on a standard copier, without signifi-cant loss of legibility. Uncontrolled copies shall be marked "FOR INFORMATION ONLY" or " UNTESTED" for those procedures which have not been validated and verified on the plant simulator or in actual practice.

O

- ~ ____ __ ______ _ . - .

TABLE 1

- SEABROCE STATION .

EMERGENCY RESPONSE PROCEDURE INDEX

,<~~

(' ) PROCEDURE WOG NUMBER TITLE CODE OS-1300 Reactor Trip or Safety Injection E-0 05-1300.1 Radiagnosis ES-0.0 OS-1301 Reactor Trip Response ES-0.1 OS-1302 Natural Circulation Cooldown ES-0. 2 OS-1303 Natural Circulation Cooldown With Steam Void in Vessel ES-0.3 (With RVLIS)

OS-1304 Natural Circulation Cooldown With Steam Void in Vessel ES-0.4 (Without RVLIS) 0S-1310 Loss of Reactor or Secondary Coolant E-1 l- OS-1310.1 SI Termination ES-1.1 l OS-1311 Post-LOCA Cooldown and Depressurization ES-1. 2 0S-1312 Transfer to Cold Leg Recirculation ES-1. 3 05-1313 Transfer to Hot Les Recirculation ES-1.4 05-1320 Faulted Steam Generator Isolation E-2 OS-1330 Steam Generator Tobe Rupture E-3 OS-1331 Post-SGTR Cooldown Using Backfill ES-3.1 OS-1332 Post-SCTR Cooldown Using Blowdown ES-3. 2 0S-1333 Post-SGTR Cooldown Using Steam Dump ES-3.3 OS-1340 Loss of All AC Power ECA-0.0 OS-1340.1 Loss of All AC Power Recovery Without Si Required ECA-0.1 OS-1340.2 Loss of All AC Power Recovery With SI Required ECA-0.2 05-1341.1 Loss of Emergency Coolant Recirculation ECA-1.1 OS-1341.2 LOCA Outside Containment ECA-1.2 OS-1342.1 Uncontrolled Depressurization of All Steam Generators ECA-2.1 0S-1343.1 SGTR With Loss of Reactor Coolant - Subcooled Recovery EC -3.1 (GJ v Desired OS-1343.2 SGTR With Loss of Reactor Coolant - Saturated Recovery ECA-3.2 Desired 0S-1343.3 SGTR Without Pressurizer Pressure Control ECA-3.3 0S-1350.1 Subcriticality (Critical Safety Function Status Tree) F-0.1 05-1350.2 Core Cooling (Critical Safety Function Status Tree) F-0.2 OS-1350.3 Heat Sint (Critical Safety Function Status Tree) F-0.3 0S-1350.4 Integrity (Critical Safety Function Status Tree) F-0.4 OS-1350.5 Containment (Critical Safety Function Statua Tree) F-0.5 0S-1350.6 Inventory (Critical Safety Function Status Tree) F-0.6 OS-1351.1 Response to Nuclear Power Generation /ATWS FR-S.1

_05-1351.2 Response to Loss of Core Shutdown FR-S.2 OS-1352.1 Response to Inadequate Core Cooling FR-C.1 OS-1352.2 Response to Degraded Core Cooling FR-C.2 05-1352.3 Response to Saturated Core Coolina Condition FR-C.3 OS-1353.1 Response to Loss of Secondary Heat Sink FR-H.1 OS-1353.2 Response to Steam Generator overpressure FR-H.2 OS-1353.3 Response to Steam Generator High Level FR-H . 3 OS-1353.4 Response to Loss of Steam Dump Capabilities FR-H.4

. OS-1353.5 Response to Steam Generator Low Level FR-H.5 05-1354.1 Response to Imminent Pressurized Thermal Shock FR-P.1 Conditions OS-1354.2 Response to Anticipated Pressurized Thermal Shock FR-P.2 Conditions OS-1355.1 Response to High Containment Pressure FR-Z.1 0S-1355.2 Response to Containment Flooding FR-Z.2 7 OS-1355.3 Response to High Containment Radiation Level FR-Z.3

(% i N-s/ 0S-1356.1 Rasponse to High Pressurizer Level FR-I.1 OS-1356.2 Res ponse to Low Pressurizer Level FR-I.2 OS-1356.3 Response to Voids in Reactor Vessel FR-1.3

TABLE 2 COMMON ABBREVIATIONS USED IN PROCEDURES r~N ac -

alternating current (electrical) k EFW -

emergency feedwater ASDV - atmospheric steam dump valve ATWS -

anticipated transient without scram BA .- boric acid BAT -

boric acid (storage) tank BIT - boron injection tank BTRS -

boron thermal regeneration system CCP -

centrifugal charging pump CCW - component cooling water (preceded by an S or P)

CRDM -

control rod drive mechanism CST -

condensate storage tank CVCS - chemical and volume control system CVCT -

chemical volume control tank l dc - direct current (electrical power and signals)

DG -

diesel generator DWST - demineralized water storage tank EPS - emergency power sequencer ECCS - emergency core cooling system HP -

high pressure HX -

heat exchanger LOCA - loss of coolant accident LOP -

loss of power LP - low pressure MCC - motor control center MD - motor driven (in reference to pumps) f)

\/

MSIV - main steamline isolation valve NIS - nuclear instrumentation system NR - narrow range (level indication)

PORV - power operated relief valve (pressurizer only)

PDP - positive displacement pump PRT -

pressurizer relief tank PRZR - pressurizer RAT -

reserve auxiliary transformer RCP - reactor coolant pump RCS -

reactor coolant system RRR -

residual heat removal RMO - remote manual operation (relay designation)

RPV - reactor pressure vessel RWST - refueling water storage tank RVLIS - reactor vessel liquid inventory system SI -

safety injection SG - steam generator SGTR -

steam generator tube rupture SUR -

startup rate SW - service water TA - tower actuation TC - thermocouple TD - turbine driven (in reference to pumps)

TSC -

technical support center UAT - unit auxiliary transformer WPB -

waste processing building ON- WR - wide range

- 1'6 -

TABLE 3 ACTION VERBS

't Actuate To put into action or motion; commonly used to refer to automated, multi-faceted operations.

Examples: Actuate S.I., Actuate Phase A, Actuate Containment Spray Align To arrange components into a desired configuration.

Examples: Align the system for normal charging. Align valves as appropriate.

Block To inhibit an automaric actuation.

Example: Block SI actuation.

Check To note a condition and compare with some guideline requirement.

Example: Check PRZR level - GREATER THAN 20%. .

O

\w- Close To change the physical position of a acchanical device. Closing a valve pre-vents fluid flow. Closing a breaker allows electrical current flow.

Complete To accomplish specified procedure ,

requirements.

Continue To go on with a particular process.

Example: Continue with this procedure.

Control To manually operate equipment as necessary to satisfy procedure require-ments on process parameters pressure, temperature, level, flow.

Example: Control pressurizer level.

Determine To calculate or evaluate using formula or g raphs .

Example: Determine maximum venting time.

O

ACTION VERBS (CONTINUED)

Energize To supply electrical energy to (something). Commonly used to describe 7-~3 an electrical bus or other dedicated

() electrical path. i Examples: Energize AC emergency buses. j Energize PRZR 'naters.

Enter To insert into or add to.

Establish To make arrangements for a stated con-dition. J Example: Establish normal pressurizer pressure and level control.

Evaluate To examine and decide; commonly used in reference to plant conditions and opera-tions.

Example: Evaluate plant conditions.

Initiate To begin a process.

Example: Initiate flow to all SGs.

Load ( To connect an electrical component or unit to a source of electrical energy.

'N May involve a " start" in certain cases.

i k'_s) l I

Example: Load the following equipment on AC equipment buses:

Maintain To control a given plant parameter to some procedure requirement continuously.

Example: Maintain SG level in the narrow range.

Monitor Similar to " check", except implies a con-tinuous function.

Open To change the physical position of a mechanical device to the unobstructed position. Opening a valve permits fluid flow. Opening an electrical breaker pre-vents current flow.

Place-in-standby To return a piece of equipment to an inactive status but ready for start on demand; commonly used to refer to a mid-position on a switch labeled " AUTO".

(' N Example: Stop the pumps and place in

(_ , standby.

Reset To remove an active output signal from a retentive logical device even with the lh input signal still present; commonly used in reference to protection / safeguards logics in which the actuating signal is

" locked-in". The RESET allows equipment energized by the initial signal to be de-energized.

Examplas: Reset 31, Reset Phase A.

Record To document specified characteristics.

Example: Record RCS average temperature.

Sample To take a representative portion for the purpose of examination; commonly used to refer to chemical or radiological exami-nation.

Examples: Sample for RCS boron concen-tration. Samples for side activity.

Start To originate motion of an electrical or mechanical device, either directly or by remote control.

g Example: Start one RCP.

Stop To terminate motion of an electrical or mechanical device.

Example: Stop both diesels.

Throttle To operate a valve in an intermediate position to obtain a certain flow rate.

Example: Throttle fl._ control valve to establish desired flow.

Trip To manually activate a semi-automatic feature. Commonly, " trip" is used to refer to component de-activation.

Examples: Trip the reactor; trip the turbine. Trip a breaker.

Verify To observe that expected characteristic or condition exists. Typically the expectation comes from some previous automatic or operator action.

Examples: Verify Reactor Trip, Verify S1 Pumps - RUNNING.

I TMM 4 L

p STATUS TREE COLOR LEGEND V i COLOR CODE Definition i

Green The critical safety function is satisfied - no l

l operator action is called for.

l Yellow The critical safety function is not fully satisfied - operator action may eventually be needed.

Orange The critical safety function is under severe challenge prompt operator action is necessary.

Red The critical safety function is in jeopardy -

immediate operator action is required.

O O /

l'

_ _ - _ - _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ m

-)

2- Cada: Sympton/

Title:

Procedura No.

, Revision No./Date:

i 1

i P

4 FIGURE 1 f

Pre-Printed Page Format

O-i i

f

(

l l

r t

l

[

I, i o- l

Cod 2 Symptom /

Title:

Proczdure No.

Revision No./Date:

_ ,_lSTEP l \ ACTION / EXPECTED RESPONSE l l RESPONSE NOT OBTAINED l FIGURE 2 Pre-Printed Page (2-Column) Format O

O-

Csdat Syrpton/

Title:

Procadura No.

Revision No./Date:

E-3 STEAM GENERATOR TUBE RUPTURE OS1330 Rev. 1 (EXAMPLE ONLY) 0 / 01/12/84

_j_ STEP l l ACTION / EXPECTED RESPONSE l l RESPONSE NOT OBTAINED l l FIGURE 3 l 17 Depressurize RCS To Minimize Break Flow And Refill PRZR: ,

a. Normal PRZR spray - AVAILABLE a. Go to Step 18. OBSERVE CAUTION PRIOR TO STEP 18.

b. Spray PRZR with maximum available spray until ANY of the following conditions satisfied:

). e BOTH of the following:

1) RCS pressure - LESS THAN RUPTURED SG PRESSURE 2). PRZR level - GREATER THAN 5% [30% FOR ADVERSE CONTAINMENT]

- OR -

l e PRZR level - GREATER THAN 80% l 4

- OR -

i e RCS subcooling based on core

, exit TCs - LESS THAN 30*F

c. Close spray valve (s)

1) Normal spray valves 1) Stop RCP(s) supplying failed spray valve.

e RC-PCV-455A RCP-lC e RC-PCV-455B RCP-1A

2) Auxiliary spray valve 2) Isolate auxiliary spray line.

d. Go to Step 20. OBSERVE CAUTION PRIOR TO STEP 20 0-

Cods: Syrptom/

Title:

Procedura No.

Revision No./Dtte:

E-0 REACTOR TRIP OR SAFETY INJECTION OS1300 Rev. .1 (EXAMPLE ONLY) 0 / 10/26/83

[ FIGURE 4i A. PURPOSE

• This procedure provides actions to verify proper response of the automatic

. protection systems following manual or autop tic actuation of a reactor trip or safety injection, to assess plant conditions, and to identify the appropriate recovery procedure.

B. SYMPTOMS OR ENTRY CONDITIONS

1. Any symptom that requires a manual reactor trip listed in ATTACHMENT A, if one has not occurred.

2. The following are symptoms of a reactor trip:

a. Any reactor trip annunciator lit.

L

b. Rapid decrease in neutron level indicated by nuclear instrumentation.'

c. All shutdown and control rods are fully inserted. Rod bottom lights are lit.

3. Any symptom that requires a manual reactor trip and safety injection listed in ATTACHMENT B, if one has not occurred.

4. The following are symptoms of a reactor trip and safety injection.

a. Any SI annunciator or status lamp lit.

b. ECCS pumps in service.

O- .

Csdas Symptor/ Titles Procatdure No.

Revision No./ Dates FR-H.4 RESPONSE TO LOSS OF NORMAL STEAM DUMP OS1353.4 CAPABILITIES (EXAMPLE ONLY) 0 / 10/11/83

_-Rev. 1 L_ FIGURE 5 l A. PURPOSE This procedure provides actions to respond to a failure of the steam generator atmospheric steam dump valves (ASDVs) and-con-denser steam dump valves.

B. SYMPTOMS OR ENTRY CONDITIONS i

This procedure is entered from F-0.3, HEAT SINK Critical Safety.

Function Status Tree on a YELLOW condition.

O o- l l

C:das Symptom /

Title:

Precadure No.

Revision No./Date:

E-0 REACTOR TRIP OR SAFETY INJECTION OS1300 Rev. 1 (EXAMPLE ONLY) 0 / 10/26/83

~

M TEPl l ACTION / EXPECTED RESPONSE l l RESPONSE NOT OBTAINED l l FIGURE 6 l 25 Check If ECCS Flow Should Be Reduced:

a. RCS subcooling based on a. DO NOT STOP ECCS PUMPS. Go core exit TCs - GREATER to Step 27.

THAN 30*F

b. Secondary heat sink: b. IF neither condition satis-fied, THEN DO NOT STOP CENTRIFUGAL CHARGING PUMPS e Total EFW flow to intact OR S1 PUMPS. Go to Step 27.

SGs - GREATER THAN 470 GPM TOTAL COMBINED FLOW CAPA-BILITY.

- OR -

e WR level in at least one intact-SG - GREATER THAN 65%

c. RCS pressure _ STABLE OR c. DO NOT STOP ECCS PUMPS. Go INCREASING to Step 27.

d. PRZR level - GREATER THAN d. DO NOT STOP ECCS PUMPS. Try 5% to stabilize RCS pressure with normal spray. Return to Step 25a.

26 Go To ES-1.1, SI TERMINATION, Step 1 27 Initiate Monitoring Of Critical Safety Function Status Trees CAUTION CST makeup should commence as early as possible to avoid low inventory problems.

_ _ _ _ _ . _ _ _ . . . _ _ _ _ _ _ _ _ . _ _ _ _ _ . _ . _ _ _ _ _ _ _ _ _ _ . ..O..

~

Codat Sy ptom/TitJe: Procedura No.

ij Revision No./Date:

FR-H.1 RESPONSE TO LOSS OF SECONDARY HEAT SINK OS1353.1

, (EXAMPLE ONLY) 0 / 01/12/84 p s 0 ~ MTEP (' .

l ACTION / EXPECTED RESPONSE l l RESPONSE NOT OBTAINED l l FIGURE 7 l FIGURE FR-H.1-1

/

i REQUIRED ECCS FLOW for CORE, BLEED AND FEED COOLING l

t f'

I 4 ' '

I i II '

g Ill ly \ !I a s '

E soc _

\

Ns lll

~

S ,

i l I

~

u= , <

v N

l ym g 20C ,

O

~ l00 R- J O

l 10 W ;OO r--I 1000 nelt- 6 60 600 6000 60p00 TIME AFTER SHUTDOWN 4

m

Codat Symptom /Titlos Preccdura No.

~

Revisica No./D:sto:

FR-H.1 RESPONSE TO LOSS OF SECONDARY HEAT SINK Osl353.1 Rev. 1 (EXAMPLE ONLY)  ! 0 / 11/03/83 O _

l U

dSTEP l l ACTION / EXPECTED RESPONSE l l' RESPONSE NOT OBTAINED l

[ FIGURE 8 l NOTE e After stopping any ECCS pump, RCS pressure should be allowed to stabilize before stopping another ECCS punp e The charging pumps and SI pumps should be stopped on alternate ECCS trains when possible.

20 Check If One CCP Should Be Stopped:

a. Two CCPs - RUNNING a. Go to Step 21.

b. Determine required RCS subcoolir.g fron table:

l-RCS SUBC00 LING (*F)

SI PUMP STATUS NORMAL ADVERSE

, CONTAINMENT CONTAINMENT U

NONE RUNNING 91* 91*

ONE RUNNING 57' 57' TWO RUNNING 50' 50*

c. RCS subcooling based on c. DO NOT STOP CCP. Go to core exit TCs - GREATER Step 23.

THAN REQUIRED SUBC00 LING

d. PRZR level - GREATER THAN d. DO NOT STOP CCP. Go to 5% [30% FOR ADVERSE Step 23.

CONTAINMENT]

e. Stop one CCP t  !

v-f

Code: Symptem/

Title:

Procedure No.

Revision No./Date:

ES-1.2 POST LOCA C00LDOWN AND DEPRESSURIZATION OS1311 Rev. 1 (EXAMPLE ONLY) 0 / 10/26/83 1 STEP l l ACTION / EXPECTED RESPONSE l l RESPONSE NOT OBTAINED l

[ FIGURE 9 [

ATTACHMENT A The following conditions support or indicate natural circulation flow:

e RCS subcooling based on core exit TCs - GREATER THAN 30*F e SG pressures - STABLE OR DECREASING e RCS hot leg temperatures - STABLE OR DECREASING e Core exit TCs - STABLE OR DECREASING e RCS cold leg temperatures - AT SATURATION TEMPERATURE FOR SG PRESSURE e Loop aT - INDICATED O

O'

(EXAMPLE ONLY) l FIGURE 10 l_.

O OPERATOR A TION

SUMMARY

FOR E-3 SERIES PROCEDURES

1. SI REINITIATION CRITERIA I Manually operate SI pumps as necessary and go to ECA-3.1, SGTR WITH LOC 3 OF REACTOR COOLANT - SUBC00 LED RECOVERY DESIRED, Step 1, if EITHER condition listed below occurs:

• e RCS subcooling based on core exit TCs - LESS THAN 30*F e PRZR IcVel - CANNOT BE MAINTAINED GREATER THAN 5% [30% FOR ADVERSE CONTAINMENT}

2. SECONDARY INTEGRITY CRITERIA Go to E-2, FAULTED STEAM GENERATOR ISOLATION, Step 1, if any SG pressure is decreasing in an uncontrolled manner or has completely depressurized, and has not been isolated, unless needed for RCS cooldown.

3. COLD LEG RECIRCULATION SWITCHOVER CRITERION Go to ES-1.3, TRANSFER TO COLD LEG RECIRCULATION, Step 1 if RWST level decreases to less than 23.5%.

4. EFW SUPPLY Commence CST makeup as soon as possible to avoid low inventory problems.

5. RED PATH SL*MMARY - ATTACHMENT A

6. KEY CAUTIONS e Maintain RCS pressure less than ruptured SG(s) ASDV setpoint.

e If a MD EFW pump is running, shut down steam driven EFW pump.

O

Code: Syrptom/

Title:

Procedure No.

R2 vision No./Date:

F-0.2 CORE COOLING STATUS TREE OS1350.2 (EXAMPLE ONLY) 0 / 01/12/84 O)V ~

l STEP l l ACTION /EXPECTE RESPONSE l l RESPONSE NOT OBTAINEDl l_ FIGURE 11 l GO TO F R-C.1 GO TO FR-C.1 CORE EXIT No avus- No ENTER % TNAN Tes ass 1200*F yts GWA ~

MAN 80% ves CORE EXIT "o -

GO TO Tes ass -

FR-C.2 THAN 700*F vas GOTO

, ir a7 uo FR C.2

( ONE RCP gg. no RUNNING ves - GREATER -

THAN 40%

O i I yg3

• GOTO RCs sueC00UNG uo F R-C.3 l GREATER -

NAN 30 1 '55 GOTO l . pg.C2 I avus-OYNAMIC No MEAD _

GREATER vts THAN 44 %4RCPs 30 w3RCPs

" TM GO TO k % Rfy v FR-C.3 O CSF SAT bv-

of 8

USERS GUIDE FOR EMERGENCY RESPONSE GUIDELINES AND BACKGROUND DOCUMENTS September 1, 1983 9

t

.-..-i_....__.7

__ . _ _ .... .._ . ~ m. - ~ _ _.

/

User's Guide For Emergency Response Guidelines O'- And Background Documents TABLE OF CONTENTS Section -

Page

1. Introduction 2

2. Control Room Usage of the Guidelin.'s 2

3. Example of Guideline Usage 8

4. Control Room Usage of Status Trees . 11

5. Example of Status Tree Usage 14  ;

6. Control Room Usage of the ERG Network 17 i i i  !

I

7. Modes of Applicability of the ERGS 21 ,

i

8. Use of Background Documents 26 8.1 Guideline Background Documer.t.s 26 8.2 Generic Background Documents 32

9. Transition Flow Charts 33

10. Application of ERG Documentation. i to Plant Specific E0P Development . 35 Tables

1. Examples of Step Sequencing 31 USERS GUIDE Septemoer 1, 1983 66898:1 1

USER'S GUIDE FOR EMERGENCY RESPONSE GUIDELINES

(~'}

V AND, BACKGROUND DOCUMENTS

1. Introduction .

The Emergency Response Guidelines (ERGS) devoloped by the Westinghouse Owners Group ( WOG), contain the technical basis far construction of plant-snecific Emergency Operating Procedures (EOPs). The two-column format used to present the ERGS contains implicit rules of usage which supplement the technical instructions. The Critical Safety Function Status Trees have their own for.T.at and rules of usage. Priorities have been established between the Optimal Recovery Guidelines (ORGs) and Function Restoration Guidelines (FRGs) which are intended to direct operator action to the most urgent operational or

. safety conditions. The background docuinents, which are presented separately from the guidelines, contain additional detail about each operator action step (and guidelines in general) which may affect the way the actual plant E0Ps are written or presented in training. The Transition Flow Chart, developed as d part of the ERG documentation, provides a graphical overview of the entire guideline network to facilitate understanding.

Each of these aspects of using the Emergency Response Guidelines is presented

~

in detail in the following sections.

2. Control Room dsage of the Guidelines Although the ERGS are not intended to be used directly,in the control room, E0Ps written in a similar manner will utilize these rules of usage. Since Optimal Recovery Guidelines and Function Restoration Guidelines are both written in similar format, the rules of usage apply to both.

Entry into an individual guideline begins at the cover sheet. The title block presents t'. unique idaa*4Fiars for each guideline, and the purpose and entry O conditions are described in separate pargraphs.

USERS GUIDE September 1, 1983 6689B:1 2

_ - _ - - - - - - - - - - - - - - - - - - - - - )

I Individual operator action steps are presented in the two-column format

()

U beginning on the following page. Certain special information is also presented, which is emphasized by not following the standard two-column format. Thist information is of two types:

o NOTES contain administrative or advisory information which supports operator action.

o CAUTIONS contain information about potential hazards to personnel or egyipment. They also advise on actions or transitions which may becomi necessary depending on changes in plant conditions.

Both NOTES and CAUTIONS are introduced by their descriptor, in bold letters, followed by the text extending across the entire page. If multiple items are included after a descriptor, each item is distinguished by a preceding bullet (o).

In ger.eral, NOTES AND CAUTIONS apply.to the step which they precede. A NOTE

_ or CAUTION which precedes the first operator action step may also apply to the entire gaideline. Two types of NOTES deserve special mention:

1) Several series of E and ECA guidelines contain a ' foldout page. 'This page presents actioris or transitions which are applicable at any step in that series of guidelines. Guidelines in these series contain a NOTE advising ,

that the foldout page should be open.

2) Several guidelines contain steps which are designated as "immediate actions." These steps are intended to be performed, if necessary, without the written guideline being available. These guidelines contain a NOTE advising which steps are "immediate action" steps.

a USERS GUIDE September 1, 1983 6689B:1 3

f)

' \s /

~ After observing any initial NOTES and/or CAUTIONS, the operator proceeds to the first action step. In the two-column format, each step in the left-hand column contains a highlighted high-level statement which describes the task to be performed. .

If the high level task requires multiple actions, then subtasks are specified. Following each task or subtask, the expected response or result is given in CAPITAL LETTERS, separated from the task by a dash.--

Example: Check Pressurizer Level - INCREASING Example: Check If SGs Are Not Faulted:

a. Check pressure in all SGs -

o NO SG PRESSURE DECREASING IN AN UNCONTROLLED MANNER

-OR-o NO SG HAS COMPLETELY DEPRESSURIZED

[v')

Expected responses are not supplied for simple control manipulations or actions.

Example: Stop All RCPs If sequence of performance is important, then the subtasks are designated by letters (or numbers if finer detail is provided). If sequence of performance is not important, the subtasks are designated by bullets (o).

Only a l'imited set of action verbs is used in the action steps. These verbs have specific meanings in the context of their usage in the ERGS.

(Refer to the verb list in the ERG Writers Guide in the Executive Volume)

Action steps are written so that the operator can proceed directly down the left-hand column only. This column contains all the expected conditions, actions, and checks required to accomplish the stated purpose

- ('~'N of the guideline. .

USERS GUIDE Septemoer 1, 1983 6689B:1 . 4 1

_ , )

If however, the expected result or response is not obtained or the action cannot be performed, the operator should move to the right-hand column for contingency instructions. This column is appropriately titled " RESPONSE NOT OBTAINED". Almost all action steps contain some contingency action statement. If one contingency action is appropriate for any of a series of left-hand column subtasks, it is simply stated once as a high level contingency. If a contingency is not provided, then the operator should proceed to the next step or substep in the left-hand column. ~

i

~

Example:

Check VCT Makeup Control Adjust controls as necessary.

System:

a. Makeup set for greater than RCS boron concentration 7s

b. Makeup set for automatic control The two column format thus equates to logical terms which would otherwise be specifically stated: H the conditions required in the left-hand column are not achieved, THEN go to the right-hand column for contingency instructions. For this reason, the first contingency action does not contain the highlighted logic terms E and THEN. Subsequent contingency actions are always expressed using the logical construction. i

• 1 Example:

Verify PRZR Level - GREATER Control charging flow to THAN (x) maintain PRZR level. I_F PRZR level can NOT be maintained, THEN manually operate SI pumps as necessary.

U USERS GUIDE September 1, 1983 66898:1 5

r

] - After taking the contingency action in the right-hand column, the operator V should proceed to the next step or substep in the left-hand column. If the contingency action cannot be per#ormed or is not successful, and further contingency instruction is not provided, the operator should again return to the next step or substep in the left hand column.

Unless otherwise specified, a required task need not be fully completed before proceeding to the next instruction; it is sufficient to begin a task and have assurance that it is progressing satisfactorily. This assures efficient implementation where steps are very time consuming. In certain cases, where local operator actions are required (outside the control room) a special NOTE may be added to reinforce this rule of procedure usage.

If a particular task must be complete prior to proc'eeding, the step containing the task will explicitly state that requirement.

"ss Transitions to other guidelines or to different steps in the same d

guideline may be made from either column. Such transitions should be made realizing that preceding NOTES or CAUTIONS are applicable. Any tasks still in progress need not be completed prior to making a transition; however, the requiement to complete the tasks is still present and must not ue neglected.

Each guideline ends with either a specific transition to another guideline, if further operator guidance is required, or with the plant being maintained in a steady-state condition. Often in the ERGS, the final transition is to " guideline and step in effect." This wording results from the symptom-dependent transitions performed in accordance with rules of usage and not lccated at a specific guideline and step.

" Step in effect" refers to whichever step was being performed when transition was made into the present guideline.

%)

USERS GUIDE September 1, 1983 66898:1 6

j

( As an example, assume an operator is performing guideline A, when symptoms

appear requiring transition to guideline B. While performing guideline B, in accordance with a CAUTION, he finds it neccessary to go to guideline C.

After completing the actions in C, he returns to the guideline and step  ;

+ from which he entered C, that is, back to guideline B. And after completing guideline B, the~ operator.would return to the guideline and step from which he entered B, in this case, guideline A. (This example assumes.that guidelines A,,B, and C, all end with the transition words "R"etuin To Guideline And Step In Effect")

Several series of guidelines have been provided with a FOLD 00T page. This

, page is located at the end of the last guideline in a series, and is intended to be available (visible) anytime any of the guidelines in the series is being performed. The FOLDOUT page contains several pieces of information or actions which are applicable at any step in any guideline of the series. The most important of these actions are guideline transitions which allow immediate response to new symptoms as they

[ appear. The placement of these transitions on the FOLDOUT page in Rev. 1 removes any sensitivity'to timing from the appearance of subsequent symptoms. .

l l E USERS GUIDE September 1, 1983 66898:1 7 m e ,--m,------u --svey,,e-,- . . , ., . , , , , , _ , , . - , ,. , , _ , , , , , _ _ , ,

r

3. Example of Guidcline Usage The actual process of working through a guideline will be illustrated by using E-2, FAULTED STEAM GENERATOR ISOLATION. It is assumed that the user was I

directed to Step 1 of this guideline by an instruction in some other guideline. ,

The user.first verifies the designator and title on the cover sheet to assure himself that he is in the proper guideline. The PURPOSE tells him that th~is 9uideline will identify and isolate a faulted steam generator. Examination of the SYMPTOMS OR ENTRY CONDITIONS list should produce the guideline from which 4 the transition to E-2 was made in this case.

. The first action step of this guideline is preceded by two CAUTIONS. Each '

y separate concern is identified by a bullet (o), and the CAUTION identifier is used only once.

4 The first CAUTION tells the operator that at least one SG must be maintained

) available for.RCS cooldown.

J f

The second CAUTION tells' the operator. that any faulted SG or secondary break should. remain isolated during subsequent recovery actions unless needed for RCS cooldown. Both ' CAUTIONS refer to the SG isolation which will take place

! in the next steps (s). The operator is expected to know that " faulted" refers to failure of the secondary pressure boundary, and " isolated" refers to closure of the steam and/or feed flow paths. The CAUTIONS have provided a specific criteria (needed for RCS cooldown) for not' isolating, or un-isolating a faulted SG.

The first action in step 1 is a check of the main steamline isolation and bypass valves on the affected SGs. The expected condition is that the valves are CLOSED. If, in fact, the-operator finds the valves closed by whatever means his training requires, he then proceeds to Step 2. If the .*alves are not. closed, or not closed on all the affected SGs, the operdor moves to the f

right-hand column where a contingency ,1struction teila him to " Manually close valves". After performing this action, the operator would return to the next j

tast in the left hand colum?, in this case, Step 2.

( '

USERS GUIDE September 1, 1983 66898:1 8 1

- -. . . . . . . . . .,a -- -- --. - ,.. . ..-,- -,-,

(r ) The Step 2 high level action is to " Check If Any SG Is Not Faulted" with a more detailed subtask describing how this is to be done: the operator is to

" check pressures in all SGs." The expected response is "ANY (SG pressure)

STABLE OR INCREASING." If any pressure is stable or increasing, the operator proceeds to the Step 3. If none of the steam generators exhibits a stable or increasing pressure, the operator moves to the right-hand column for contingency instructions. He is told, "IF all SG pressures decreasing in an

~

uncontrolled manner, THEN go to ECA-2.1, UNCONTROLLED DEPRESSURIZATION OF ALL STEAM GENERATORS, Step 1." In order to perform thts step, he has to decide if the depressurization is controlled, or not. If it is not controlled, he will leave E-2 and make the required transition to ECA-2.1. If however, the pressure decrease is under his control, in at least one steam generator, he proceeds to the next left-hand column task, Step 3.

Step 3 requires the operator to " Identify Faulted SG(s)" and the more detailed process is described in a'substep " Check pressures in all SGs". Two possible pressure responses are given which will satisfactorily identify a faulted SG:

ANY SG PRESSURE (is) DECREASING IN AN UNCONTROLLED MANNER, or ANY SG (is)

COMPLETELY DEPRESSURIZED. If either condition is observed, then the intent of the step is satisfied and the faulted SG(s) is (are)' identified. The operator moves on to Step 4. If neither condition is observed on any SG, the operator moves to the right-hand column where he is instructed to search for the [

initiating break (which must have been isolated by MSIV closure) and then to go to Step 5, i.e., skip over Step 4 since no steam generator is required to be isolated.

Step 4 tells the operator to " Isolate Faulted SG(s)" and lists several

, separate paths which should be isolated. The bullet (o) designator on the separate items implies that isolations can be done in any order. If the isolations are properly performed, the operator proceeds to Step 5. If some aspect of isolation cannot be completed, he moves to the right hand column where he is instructed to manually close the valves (from the control room),

and.if that is not successful, to dispatch a (local) operator to close the desired valve (s) or appropriate block valves (s). With the contingency

/

performed or local action initiated, the operator proceeds to Step 5.

USERS GUIDE September 1, 1983 6689B:1 9

Step 5 simply has the operator Check the present level in the condensate'

/~^)

\s_,- storage tanks. It is expected.to be - GREATER THAN (x)%. If level is as expected, the operator proceeds to Step 6. However, if level is less than expected, he moves to the right hand column where he is instructed to " Switch to alternate AFW water supply."- From his training, or from additional information supplied in the plant E0P, he will perform this tack and then proceed to the left hand column of Step 6.

Step 6'is a Check for secondary radiation. Detailed performance of the task is presented in sequential subtasks. First, the operator is to " Request periodic activity. samples of all SG(s)". This will involve a call out to a local operator, with attendant time delays for sampling and analysis. By rules of usage, the operator can proceed to the next subtask " Check unisolated secondary radiation monitors," which he should be able to do from the control room. The third subtask is the conclusion on the " Check" process, " Secondary radiation - NORMAL". 'If no abnormal radioactivity is known or detected at that time, the expected response is obtained and the operator proceeds to Step

(

\- -

7. If abnormal radiation is detected on the secondary side of any steam generator, then, by rules of usage, the operator moves to the right hand column and is instructed to "Go to E-3, etc." and so leaves the E-2 guideline.

Step 7 tells the ope.'ator to "Go to E-1, etc." and thus ends the guideline with a transition to some other appropriate guideline.

The highlighted END centered on the page emphasizes that the listing of action steps for E-2 is complete.

n-

~

USERS GUIDE September 1, 1983 6689B:1 10

j 4. Control Room Usage of Status Trees ,

V -

Status Trees are a convenient device used to evaluate the current state of predefined CRITICAL SAFETY FUNCTIONS. When the Functions are shown to be satisfied, the plant is safe. Tree format can be of two types which are technically equivalent. Both types ask a series of questions about plant conditions, and in general, each question asked depends on the answer to the

. previous question. This dependancy results in a branching pattern, which is referred to as a " tree".

There are six different trees, each one evaluating a separate safety aspect of the plant. (Critical Safety Function). At any given time, a Critical Safety Function status is represented by a single path through its tree. Since each path is unique, it is uniquely labeled at its end point, or terminus. This labeling consists of color and/or line pattern coding of the terminus and last branch line, plus a transition to an appropriate guideline if required by that safety status. If the status is normal for a particular Critical Safety Function, no transition is specified, and the condition is clarified by the words CSF SATISFIED.

Color coding can be either Red, Orange, Yellow, or Green, with Green respresenting a " satisfied" safety status. Each nor; green color represents an action priority as discussed below.

The six Status Trees are'ALWAYS evaluated in the sequence:

1) Subcriticality (S)

2) Core Cooling (C)

3) Heat Sink (H)

4) Integrity (P)

5) Containment (Z)

6) Inventory (I) l 'V)

USERS GUIDE September *, '983 6689B:1 11

l7 ,1 If identical color priorities are found on different trees during monitoring, the required action priority is determined by this sequence. The user begins monitoring with the Suberiticality tree. Entry is at the arrow at the left side of the tree. Questions are answered based on plant conditions at the time, and the appropriate branch line followed to the next question.

An individual status tree evaluation is complete when the user arrives at a color - (or line pattern -) coded terminus. With the exceptions noted below, the color and instructions of the terminus are noted (logged) and the user continues to the next tree in sequence, again entering at the left-hand side arrow.

If any RED terminus is encountered, the operator is requty.d to immediately stop any Optimal Recovery Guideline (ORG) in progress, and to perform the Function Restoration Guideline (FPG) required by the terminus.

If during the performance of any RED - condition FRG, a RED condition of

,-_x

( ) higher priority arises, then the higher priority condition should be addressed first, and the lower priority RED-FRG suspended.

If any ORAMGE terminus is encountered, the operator is expected to monitor all of the remaining trees, and then, if no RED is encountered, suspend any ORG in progress and perform the FRG required by the ORANGE terminus.

If, during the performance of an ORANGE - coded FRG, any RED condition or l ' higher priority ORANGE condition arises, then the RED or higher priority ORANGE condition condition is to be addressed first, and the original ORANGE FRG suspended.

l Once a FRG is entered due to a RED or ORANGE condition, that FRG is performed to completion, unless pre-empted by some higher priority condition. .It is

! expected that the actions in the FRG will clear the RED or ORANGE condition before all the operator actions are complete. rioweve r . chese guidelines should be completely performed to the point of th.a normal transition back to

-" guideline and step in effect."

a USERS GUIDE September 1, 1983 66898:1 12

- ('~' Tree monitoring should be continuous if any status coded ORANGE or RED is

\~ found to exist. If no condition more serious than YELLOW is encountered, monitoring frequency may be reduced to 10-20 minutes, UNLESS some significant change in plant status occurs.

Monitoring ma be terminated after the Reactor Protection System and Engineered Safeguards System are both restored to operable status (SI reset and trip breakers closed). At this point, the operatcr :.'.:uld no longer be using the ERGS. .

A YELLOW terminus does not require immediate operator attention. Frequently it is indicative of an off-normal and/or temporary condition which will be restored to normal status by actions already in progress. In other cases where RED OR ORANGE termin; are possible, the YELLOW status might provide an early indicatton of a problem developing. Following FRG implementation, a YELLOW might indicate a residual off-normal condition. The operator is allowed to decide whether or not to implement any YELLOW -condition FRG.

V f -s

~_s USERS GUIDE Septemoer 1, 1983 l 66898:1 13 I _ _ _ _ _ _ _ _ _ _ . _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ - - - . _ - - - - .

[m

\j i 5, Example of Status Tree Usage The actual process of working through the trees will be illustrated ' oy examining the " block" version of the first (Subcriticality) status tree. The user enters the tree at the left-hand arrow and is asked if the power range (NIS channels) indication is less than 5?4. -The possible answers are either "yes" or "no". If indicated power is greater than 5's, then the appropriate answer is "no", so the user would follow the "n.o". path directly to the

~

terminus and determine that:

o the response priority is RED (immediate response required) o the appropriate Function Restoration Guideline is FR-S.1 According to the Rules of Priority, the operator should suspend whichever ORG is being performed and immediately initiate the actions in guideline FR-S.1, Monitoring of the Status Trees may continue for information purposes, but by Rules of Priority, no other higher priority condition can exist. When the i actions required by FR-S.1 are complete, the operator is directed to " return to guideline and step in effect". This allows recovery actions to continue exactly where they were suspended when the RED' priority was recognized. This also signals continued monitoring of status trees. In this case, the user and/or operator would know, because of the FR-S.1 actions and checks, that the i subcriticality tree would have no status more severe than yellow.

If indicated NIS power is less than Sie, then the first question block is answered with a "yes" ar.d the user would follok the "yes" path to the next question block.

v USERS GUIDE September 1, 1983 6689B:1 14

_ _ - - - - - - . - _ .----------------_________------------_____J

/m In this second block, the user is asked whether the Intermediate Range Startup Rate is zero or negative. If the indicated rate is oositive, then the user would follow the "no" response path directly to a terminus and determice that:

o the response priority is ORANGE (prompt response required) o the appropriate Function Restoration Guideline is FR-5.1 Accordi,ng to the rules of usage, the remainder of the status trees should be monitored to determine if any RED conditions are present. In no RED status is encountered, then any ORANGE conditions would be reviewed for priority. Since subcriticality is the first status tree, the present ORANGE would be addressed first by rules of priority. Again the operator would suspend whichever ORG was being performed and initiate the actions in guideline FR-S.I. Monitoring of the status trees should continue in order to promptly identify any RED conditions which might arise and take priority. When guideline FR-S.1 is completed, the operator can again return to his normal recovery action at the point where it was suspended - unless other ORANGE conditions require attention first. Again, order of tree sequence would determine ORANGE priority.

If the answer to the second block question were "yes", the user would follow the "yes" path to a third question block.

This time the question is whether the source range is energized. This can easily be answered by checking the detector high vcitage indication, or by noting the Source Range beeper. If the Source Range is determined to be not energized, the user follows the "no" path upward to anothe" question block.

Now he is asked if the Intermediate Range startup rate ir more n,egative than

.2 DPM. If the indicated startup rate is between zero and .2 DPM, then the user would follow the "no" path directly to a terminus and find that:

o the response priority is YELLOW (action not required immediately) o the appropriate Function Restoration Guideline is FR-5.2 q

U USERS GUIDE September 1, 1983 66898:1 15

Since the status priority is YELLOW, the user would continue to monitor the remaining trees and deal with any RED or ORANGE priorities which might be encountered. If no other condition coded higher than YELLOW were present, then the operator would decide if the FRG should be performed or delayed.

Often, a YELLOW is indicative of an off-normal condition which may be restored to normal status by actions already in progress. At other times, the YELLOW status may be indicative of an abnormality in a single RCS loop - a single SG, for example and may be considered acceptable for the particular accident in progress. Whatever the case, the operator makes the decision about responding to the YELLOW. condition.

If the Intermediate Range startup rate is more negative than .2 DPM, then the user would follow the "yes" path downward to a terminus and find the condition coded GREEN, and annotated "CSF SAT;" the Critical Safety Function -

SUBCRITICALITY, is considered satisfied, so the user proceeds to evaluate the next status tree in the sequence.

O If the Source Range was found to be energized, in response to the third question block, the user would follow the "yes" path downward to another question block. This time he is askea if the Source range startup rate is negt.tive or zero. Since the source range signal is normally erratic, it will be necessary for the user to look [at a recorder trend of count rate to properly evaluate the startoo rate. If positive, the user would follow the "no" path upward to a terminus and find:

o the response priority is YELLOW o the appropriate Function Restoration Guideline is FR-S.2 The operator would again use his judgement regarding implementation of FR-S.2 while continuing recovery operations and observing the rules of usage for tho other status trees.

If the Source Range startup is observed to be negative, the user follows the "yes" path downward out of the question box and finds the condition coded GREEN, the safety function is satisfied. The user would move directly to the next tree in the sequence.

USERS GUIDE September 1, 1983 66898:1 16

_ - _ - _ _ _ _ \

6. Control Room Usage of the ERG Network While the previous sections discussed the separate usage of an-individual- ,

guideline and evaluation of status trees, this section presents the intended overall usage of this entire ERG network.

Direct entry into the Emergency Response Guidelines is, limited to two specific

' ~

conditions: I o If at any time a reactor trip or safety injection occurs OR IS I

REQUIRED, the operator will enter guideline E-0, REACTOR TRIP OR SAFETY INJECTION o If at any time a complete loss of power on the ac emergency busses takes place, the operator will enter ECA-0.0, LOSS OF ALL AC POWER.

This includes any time during the performance of ANY other ERG.

< The entry into E-0 is expected to be the one more frequently used, so is described first: I The operator proceeds through E-0, following the rules of guideline usage as described above, with two possible outcomes:

1

o. He remains in E-0 and is directed by an action step to begin f monitoring the status trees i- - OR - -

i o He transitions to some other guideline, at which point he begins to monitor the status trees.

Monitoring of the status trees takes place in accordance with its own rules of usage, in parallel with the recovery actions being performed by the operator.

The monitoring may be done directly by one of the operators in the control I room, by some other member of the snif t assigned to the control room, or by a dedicated computer routine. The only requirement of the monitoring fuction is USERS GUIDE September 1, 1983 6689B:1 17

'] .

g that the operator in charge of recovery actions be immediately informed of REO V)

(

or ORANGE priority status conditions, and regularly advised of YELLOW and

' GREEN conditions.

The ORG actions in progress are suspended if either a RED or ORANGE condition is-detected on a status tree. N_o ORG actions are to be performed while a critical safety function is being restored from a RED or ORANGE condition, unless directed by the FRG in effect.

i 1 Aft ~er restoration of any Critical Safety Function from a RED or ORANGE condition, recovery actions may continue when the FRG is complete. Most often, the FRG will return the operator to the suspended ORG. However, at times a FRG will require a transition to a different ORG because of conditions created within the FRG.

i Upon continuation of recovery actions, some judgement is required by the operator to avoid inadvertent reinstatement of a RED or ORANGE condition by undoing some critical step in a Function Restoration Guideline. The plant recovery guidelines are optimal assuming that equipment is available as required for safety. The appearance of a RED or ORANGE condition implies that some equipment or function required for safety is not available, and by implication, son:e adjustment may be required in the recovery guidelines.

An example might be the establishing of an alternate feed path to the steam generators as required by FR-H.1. With feed flow from either the main feed or condensate system, the operator would NOT want to isolate the ma-in feed line as required by ES-0.1.

Direct entry into ECA-0.0, due to loss of ac power on all (4 KV) safeguards busses is expected to be a rare occurrance. However, once in ECA-0.0, special considerations come into effect. Because none of the electrically powered safeguards equipment used to restore Critical Safety Functions is operable, none of the FRGs can be implemented. A NOTE at the beginning of guideline ECA-0.0 states "CSF Status Trees snould be monitored for information only.

{m FRGs should not be implemented." Once in ECA-0.0, the operator performs the Q)

USERS GUIDE September 1, 1982 66898:1 18

[~ 'i required actions, and is not allowed to transition to any other guideline

\ l V until some form of power is restored to the (4 KV) Safeguards busses. Even then, permission is not granted to implement FRGs until some initial status checks are performed by the operator.

Certain contingency guidelines (ECA) take precedence over FRGs because of their treatment of specific initiating events. In all such cases, this precedence is identified in a NOTE at the beginning of the ECA guidelines.-

For example: ECA-2.1 deals with depressurization, loss of level, and resultant feed flow reduction to ALL steam generators. Wnile this condition results in a RED priority on the Heat Sink Status Tree, the referenced guideline, FR-H.1, returns the operator to ECA-2.1 for the preferred treatment of the event. ECA-2.1 contains an introductory CAUTION stating the specific conditions under which FR-H.1 should be implemented.

A more dramatic example is ECA-0.0. which provides the best strategy for

( ) maintaining Critical Safety Functions satisfied and protecting barriers until

,V (4 KV) safeguards at power is restored.

One unique guideline in the ERG set has no transitions or direct entry conditions. It is used purely as an operator aid and is entered based purely on operator judgement. The guideline is ES-0.0, REDIAGNOSIS. It is intended to be used after departure from E-0, only if SI has been actuated. It provides reassurance to the operator that he is in the correct guideline, or provides the necessary transition instruction to get to the correct guideline for the existing symptoms. Operator need for this rediagnosis guidelilne is limited in the Rev. 1 ERGS, because many of the transitions needed to respond to new symptoms are included on the foldout pages. However, its presence can be reassuring to an operator af ter making several consecutive transitions due y to rapidly changing condicions.

,q

., /

USERS GUIDE September 1, 1983 66898:1 19

ERG usage always ends in one of the following ways:

o Transition to a normal (nct an E0P) plant operating procedure (stable).

o Transition to some " appropriate" procedure while on RHR at cold shutdown conditions (stable).

o , On cold leg recirculation or hot leg recirculation with longer term

. recovery actions being determined by the individual utility (stable).

l i

I l

t USERS GUIDE September 1 1983 66898:1 20

Modes of Applicability of the ERGS (n

O i

7.

The ERG network was originally written to accommodate transients occurring at a " hot" or "at power" condition. The transients envisioned would result in either Reactor Protection System or Safeguards Systems actuation, with some corresponding, or subsequent, operator action needed. The guidance for operator action is based upon having the safety-related equipment required by

. Tech Specs for MODE 1 or MODE 2 operation available for his use. For _

transients initiating during other MODES of operation, the same complement of equipment cannot be assumed available, so that the detailed instructions within the ERGS may not be applicable. Just as earlier steps in the ERGS generally involve response to the transient, later steps generally relate to getting the plant to a cold shutdown condition. If the plant is already substantially cooled and depressurized, some detailed instructions may not be

. applicable.

Critical Safety Function monitoring using the Status Trees also assumes a MODE 1 or' MODE 2 initial condition, followed by some Protection System actuation, to result in a subcritical reactor. Use oftthe trees can be extended beyond this original intent, but with an understanding of the' intent of each tree.

For example, the Heat Sink tree assumes the steam generators are available for heat removal by steaming. If all ' reactor decay heat is being removed by the RHR system, the steam generators are not required in their normal capacity. .

So SG availability really not required to be satisfied. Yet the tree would indicate a SG in wet layup to be OK, while one in dry layup would be abnormal.

~

To clarify the usability of the ERGS for transients originating during other than the assumed initial operating MODES, a detailed review of the entire

. network has been performad. The results 'are presented in tha following

- table. In some cases, slight modifications are needed to extend the ,

applicable range of a guideline beyond its original intent.

V USERS GUIDE Septemcer 1, 1983 66898:1 21 m- = - , _ _

Guideline Designator ' Applicable Modes

• Comments E 1,2,3 RHR not in service and SI operable ES-0.0 1, 2, 3, 4, ES,0.1 1, 2 (assumes trip from

" power) -

,j ES-0.2 Hot (near no load),

ES-0.3 ,

slight modification ES-0.4 I required if already in cooldown E-1 1, 2, 3 RHR not in service ES-1.I' O ES-1.2 , RHR not in service, V entry is limited by

- stated conditions

, E-2 1,2,3,4 Temp > 212*F

.j. E-3 1,2,3,4 RHR not in service ES-3.1

< ES-3.21 ES-3.3 ECA-0.0 1, 2, 3, 4 Partly hot and ECA-0.1 pressurized ECA-0.2 ECA-1.1 Specific er.try conditions provided ECA-1.2

. USERS GUIDE September 1, 1983

(

'66898:1 22

Guideline Designator Applicable-Modes

• Comments ECA-2.1 1,2,3,4 RHR not in service, hot

ECA-3.1 ,

1, 2, 3, 4 RHR not in service 7 ECA-3.2 ECA-3.3 F-0.1, Subtriticality 1-4 F-0.2, Core Cooling 1-4 f

F-0.3, Heat Sink 1-4 unless RHR in service F-0.4, Integrity 1-4 slight problem with cooldown rate in mode 4 b

v F-0.5, Containment 1-4 F-0.6, Inventory 1-4 FR-S.1 1-4 (AFW not required if on RHR)

FR-S.2 1 FR-C.1 1,2,3 Partial MODE 4 on SI FR-C.2 equipmen't availability, secondary lineup

~

FR-C.3 1-4 FR-H.1 1-4 Bleed and feed may be too soon for MODE 4

,r"'s b

USERS GUIDE September 1, 1983 66898:1 23

.

• t Guideline Designator Applicable Mocer Comments FR-H.2 1-4 FR-H.3 1-4 .except wet layup FR-H.4 1-4

. . . ., .i except dry layup

~

>m FR-H.S 1-4 FR-P.1 1 Entry may not be necessary if initial temperature was low FR-P.2 1-4' FR-Z.1 1-4 FR-Z.2 1-4 FR-Z.3 1-4 FR-1.1 1-4 Some exceptions if RHR

. in service FR-I.2 1-4 possible exception of SI initiation 51 FR-I.3 1-4 4

j USERS GUIDE September 1, 1983 fj. 66898:1 24

~~ --

i

l. ,,

O

• Operating MODES as used here has'the same definition as in Standard U Technical Specifications:

MODE , REACTIVITY THERMAL POWER AVERAGE (Keff) (% Rated, excluding COOLANT

-decay heat) TEMPERATURE

-1. Power Operation 1 0.99 >5 3 350*F

~

2. Startup 1 .99 55 3 350*F

3. Hot Standby < 0.99 0 3 350*f

4. Hot Shutdown- < G.99 0 350*F >Tavg>200*F

5. Cold Shutdown < 0.99 0 $ 200*F (Mode 6, Refueling, is not considered in the context of ERG applicability) i .

USERS GUIDE September 1, 1983 s

66398:1 25

\

d 8. Use of the ERG Background Document (s)

-Two different types of background documents are included in the~EPG Revision 1 meterial: ' background documents for individual guidelines, and background documents _on special topics which are relevant to multiple guidelines (hence

~

the name~" generic" background documents). Both types have a common objective of providing very detailed discussions, commentary, and technical data about their p. articular subject. The use of the two types of bgckground documents will be discussed separately in the following sections. . -.,

8.1 Guideline Background Documents The very detailed and consistent structure of the guideline background documents is defined in the Background Document Writers Guide, included in the ERG Revision.1 Executive -Volume. As stated in that Guide, the guideline background documents " provide the engineering and operational information to j be used in preparation of plant-specific Emergency Operating Procedures and L development of operator training programs."

Every effort has been made to assure that the background documents provide enough information to support the_ process as intended. Details about the intent and performance of each operator action are provided to ensure that actual E0Ps are consistent with intended task requirements. Discussion of plant transients and systems response are presented to give the user a more comprehensive understanding of the events for which the guidelines were written. Additional information is provided to assist in procedure writing and operator training. The intended use of detailed background items is presented below.

The first item in a guideline background document is the Introduction. This sectinn provides a brief statement about the intent of the guideline, and also entry and exit cc,nditions. This information is useful to both Training and Operations in mapping procedure use and laying out plant-specific E0Ps.

1 USERS GUIDE September 1, 1983

_.66898:1 .26

e r'~~N

(  ! The second section contains a Description of the transient being mitigated by s_/s the guideline.

The transient plots are very useful in Training by showing plant response including operatur act' ions.

The consistent format used for all plots in'tne Rev. I background documents should facilitate usage. The best estimate analyses presented in this section can also be used to qualitatively judge training simulator performance.

j. The third section is Recovery / Restoration Technique. Training can use the

• brief ove,rview of the recovery technique provided in the high-level action ~

summary to introduce the guideline to operators, or in a less detailed presentation.

The inclusion of Key Utility Decision Points presents plant operations personnel with E0P questions regarding plant policy. If the decision is of an operational nature, it may be possible to factor the decision-making criteria directly into the E0P. In other cases, the necessity of a policy decision on an emergency basis is identified, for inclusion in general plant emergency planning.

\

(N Section 4 of the guideline background document, Detailed Description of N- /

) Guideline, provides the most valuable information for the development plant specific E0Ps.

, Itconsistsofthreesubs!ectimesasd,escribedbelow:

Description Tables for Steos, Notes, and Cautions This subsection contains a one page (at leart) description of each operator ,

action step, note, and caution, comprising the guideline. The description is

' -presented in the form of a standard table, so that a consistent format is used I throughout all guidelines. This table presents first the exact wording of each high level action step (or NOTE or CAUTION). The Purpose explains the

' intent of the step. Basis provides the technical justification for the step; it explains what the step contributes to the recovery, why it is worded as it -

is, and, if appropriate, why it is located where it is in the guidelire. This explanation is extended to provide a sufficient understanding of the step intent so that an EOP writer will be able to construct his own plant-specific T

action requirements to properly accomplish that intent.

7 -- g

\

q l

t USERS GUIDE 66898:1 Septemcer 1, 1983 27 '

l

9

-() The-listing of separate Actions to be performed is merely an expansion of the

\'- / high-level instruction into de. tailed subtasks required in the reference

. plant. Included as possible subtesks are any contingent actions provided in

~that particular guideline step. While the Actions list does summarize the expected operator tasks it does not convey the relative ordering or sequencing of the tasks as the actual guideline presentation does.

The Instrumentaton and Control / Equipment sections list the general ~

cateJories of these items required in order to perform the Actions. Nothing is said about how many redundant channels of indication are actually in the plant, or how many types of controls. It is left to the E0P writer to identify the comparable instrument or control present in his control room, and then to identify it in his E0P step in a manner defined by the plant-specific E0P Writars Gruide.

The Knowledge section identifies any special type of training that might be

. required by the operator to correctly perform the intent of the step.

(A)

Vypically, no special requirement exists, since either normal E0P training, or the specific step instructions will assure proper performance.

Plant specific information repeats and explains any footnotes contained in the guideline step which call for plant-specific information. Generally this

~

information involves setpoints and some knowledge about instrument channel accuracies. (Refer to the Generic Instrumentation document in the Executive Volume for a discussion on instrument errors.) Some footnotes require further explana't ion, so it is provided in this section. Many guideline steps include subtasks such as " Enter plant specific means" or " Enter plant specific list."

If the inter.t of the step was not sufficiently explained in the Basis section, then further clarification of exactly what is required will be provided here. Certain cases might also be considered Key utility Decision Points, and so would be discussed in that background document section.

N.J USERS GUIDE Septemcer 1. 1983 66898:1 28

[Y = Step Sequence Requirements Nj This second subsection of the Detailed Description consists of a special table of the guideline high level steps showing all internal and external (entry and exit) transitions relative to the steps in which they occur. These

-transitions are indicated by double blank lines between steps or groups of steps. To the right of each guideline step is an associated " sequence number" which f ridicates the allowed sequencing of that particular step relative to .

other steps in the guideline. Although the ERGS present the action steps in a particular sequence which accomplishas the intent of individual guidelines, there are other possible sequences which might also accomplish the stated intent. For a particular utility, one of these modified sequences might be much better suited to its control room layout or staffing level. The

" sequence numbers" provide the allcwed interchangeability of guideline steps consistent with accomplishing the stated intent.

" Sequence numbers" simply specify the required / allowed order of different step

[

~

groupings. For example, in a particular guideline step sequence table, i

U several steps might have a step sequence number of 3. This means that all steps with 3 can be interchanged in any order so long as in the final E0P, all the 3 steps come after any 2 steps and before any 4 steps.

f 6 In certain cases, using again the sequence number 3 as an example, a whole

~

series of 3's might include a 3A and a 38. This notation means that the step

- with 3A and the step with 3B can be. located anywhere in the entire set of 3's, so long as the 3A step comes before the 3B step. Again, all the steps with sequence number 3 must follow (all) the steps with sequence number 2 and precede any step with sequence number 4.

These and other possible types of sequencing notation are summarized on

' Table 1.

The presence of " sequence rumoers does not convey any requirement to re-arrange guideline steps. It is anticipated that many plant specific E0Ps will use the step sequencing alreacy present in the generic guidelines.

(nV}

USERS GUIDE Septemoer 1, 1983 6689B:1 2c

e One very important concern in changing step sequence is the maintenance of all

[

internal guideline " looping", that is, transitions within a guideline. This maintenance of proper internal looping might require some rewording of guideline steps to ensure that transitions are made at the proper time and

-under the intended conditions. Reference to the Transition Flow Chart (see section 9 of this Guide) will provide a schematic presentation of the trtnsitions being affected. , ,

y o -

Detailed Logic Diagram This last' subsection contains a symbolic presentation of all guideline steps showing the logic' involved in performing the operator actions. Inis diagram is intended primarily as a training and learning aid since it restricts itself to major actions, and emphasizes the operator decisions required in the guideline.

O V o USERS GUIDE September 1, 1983 66898:1 30

~

TABLE 1 EXAMPLES 10F STEP SEQUENCING

' STEP SEQUENCE COMMENT 1 1 Steps 1 through 5 should be performed in order 2 2 and not rearranged in sequence. -

3 3 4 4 5 5 1 1 Steps 2 and 3 can be interchanged in sequence, 2 2 but other steps shculd be performed in order.

3 2 4 3

~5 4 1 1 Steps 2, 3 and 4 can be rearranged in sequence, 2 2A however step-3 should follow step 2. Other 3 28 - steps should be performed in order.

4 2

~

5 3 1 1 Step 4 can be interchanged in sequence with step 2 2 2 or 3. Other steps should be performed in-3 3 order.

4 2-3 5 4-O USERS GUIDE September 1, 1983 6689B:1 31

I

.=

(

o' The fifth background document section, Frecuent Ouestions, is again intended lprimarily for training-because it includes questions frequently asked of training in the past. Although these questions have already been answered in the expanded background document sections, they are answered again here for clarity.

The final section, References, lists any published documents which were used to gene, rate the background information, or which might be-useful in doing ~

further research into a particular topic.

8.2 Generic Background Documents These documents provide detailed background information on a particular. Topic rather than a particular guideline. Generally the information is applicable to multiple guidelines, and in some cases, to the entire ERG set. All of these documents are located in the Generic Issues section of the Executive Volume.

f~%

Because the information in these documents is very application-oriented, it is recommended that E0P writers and trainers carefully review these sections before proceeding into plant-specific applications.

i USERS GUIDE September 1, 1983 66809:1 32

e 9

/N 9. Transition Flow Charts kh The Transition Flow Charts are part .of the documentation for the Emergency Response Guidelines. They are schematic representations of the entire ERG network showing graphically all internal and external (entry and exit) transitions which can be made. Conditional transitions from CAUTIONS and FOLCOUT page transitions are included.

There are two Transition Flow Charts for the ERG Rev.1 network. The first.

contains all of the event-related guidelines (E, ES, ECA) while the second

~

contains the Critical Safety Function Status Trees and the function-related guidelines (FRG). Similar rules of construction apply to both Charts.

On the first Flow Chart, the ORGs are vertically segregated by designator:

E's on top, ES's in the middle, and ECA's at the bottom. Entry on symptoms is identified by a large arrow. All the guidelines in a series are located in a

-vertical column. A foldout page is shown at the bottom of its guideline series. Each guideline is identified by its designator (e.g. E-0, ES-1.3,

(}

ECA-3.1) just preceding the first guideline step and at the right hand side of the guideline column. All high-level steps are listed, in order, in the guideline column. Completior of a guideline is denoted by the word "END" below the last guideline step and at the right hand side of the guideline column.

Transitions are characterized as follows:

- All "go to" or entry transitions are shown as solid lines.

- All "should be in" transitions are shcwn by dashed lines.

- Transitions from a high level step are shown graphically coming out below that step.

- Transitions from the right-hand column (RNO) are shown coming out from the side of that step (either left or right side, whichever is more direct).

- Transition into a guideline step is shown at the top of that step.

- Transitions between Flow Charts is shown by an open arrow containing the guideline and step number s,s USERS ~ GUIDE September 1, 1983 6689B:1 33

Transitions going to multiple steps or guidelines are identified by a dot (junctions)

CAUTIONS with implied transitions are indicated by a small circle.

Only those FOLDOUT PAGE items which contain transitions are included.

On the second Flow Chart, the CSF Status Trees are shown on the top level, with associated FRGs displayed vertically below each tree. The FRGs are arranged in order of priority (RED, ORANGE, YELLOW) from top to bottom. -

9 O 5 i

,l -

h s

s.

USERS GUIDE September 1, 1983 6639B:1 34

-t e

/'~Nf 10. Application of ERG Documentation to ks _ l- ,

Plant Specific E0P Development It has been stated.that the ERGS provide the technical basis for plant specific E0Ps. .Similarly, many other documents comprising the ERG package are intended to support plant E0P writing. These separate items will be addressed t

here in terms of the existing INP0 guidelines on E0P generation.

Supplement I to NUREG 0737 requires the preparation of a Procedures Generation Package to describe to the NRC how each plant will implement its upgraded E0Ps. INP0 has issued an Emergency Operating Procedures Generation Package Guideline (INP0-83-007) to describe the separate elements of such a package.

The elements are defined to be the following:

o plan't-specific technical guidelines o plant-specific writers guide for E0Ps o E0P verification t

O  !

o E0P validation N- / o E0P training program .

Technical Guidelines Frequent reference is made in the literature to " plant-specific technical ~

guidelines". The ERGS are considered to be " generic technical cuidelines" for Westinghouse plants. The ERGS were written based on the systems layout and operation of " REFERENCE" (HP and LP) plants, which are thoroughly described in the Executive Volume. To convert the ERGS to plant-specific guidelines, it is necessary to document, system by system, any differences between the appropriate (HP or LP) REFERENCE plant, and a specific plant. Included in this comparison is a discussion of any control room instrumentation and/or control differences from the REFERENCE plant. As a result of this comparison, a specific plant must resolve how any differences will be accommodated in the guidelines and provide appropriate technical justification for that resolution.

O%j USERS GUIDE September 1, 1983 6689B:1 35

/] The combination of the ERGS (generic guidelines) and the specific plant /

d- REFERENCE plant comparison, satisfies the requirement for plant specific technical guidelines. It is not necesary to physically incorporate the comparison list prior to actual E0P writing.

' Writer's Guide

~

l A second major element of the Procedures Generation Package is a Writer's -

Guide. ' INP0 has generated a guideline for preparing an E0P Writers Guide (INP0-82-017) and the ERG Writers Guide is included in the Executive Volume.

Much of the information necessary tc generate plant specific E0Ps is to be discussed in the plant specific document. The numbering system to be used in the E0Ps.is spelled out, as well as the process for identifying updates and revisions. This discussion allows the E0Ps to be integrated into,the much larger plant procedure base and existing reiiew/ approval system. The ERGS contain a specific format with its own rules of usage. The Writers Guide can modify (or confirm) the format to be used, consistent with utility practice and available word processing equipment. The ERGS contain many references to v " plant-specific means" or " plant specific list." The EOP Writers Guide will clarify just how much detail is to be included in the E0Ps (lists, tables, attachments), and how references to specific control room instruments / controls

( are to be in::orporated. ,

The amount of detail to be incorporated in the final E0Ps (as specified in the E0P Writers Guide) will determine the extent of referencintj from existing E0Ps, FSAR, Tech Specs., and licensing committments. The effort to satisfy the required level of detail can be assisted by use of the Step Description Tables provided as part of each guideline background document; these tables explain the detailed intent of each step, so that the intent is not misinterpreted in EOP writing.

E0P Verification, Verification is a check that the E0Ps were written correctly. It involves a comparison of all the appropriate reference documents with the final EOPs,

[M

\ formalized by detailed documentation of the process, and coupled with some USERS GUIDE September 1, 1933 l 66898:1 36

k -

[

\

mechanism for correcting any identified deficiencies. INPO has generated a

~b comprehensive E0P Verification Guideline (INPO-83-004) to assist in this effort. The same ERG documents used in the E0P writing effort 'can again b6 used in this verification process:

-ERGS (Guidelines and Background Documents)

Reference Plant Description (HP or LP) lERGWritersGuide -

ERG Configuration Control and Approval Procedure E0P Validation Validation is an exercise performed to demonstrate that the actions specified in the E0Ps can be performed by the operators to manage plant emergencies. A detailed guideline explaining various methods of validation was generated by INPO (INPO-38-006). Included in this document is a presentation of the

" Reference Method" whereby individual plants can reference the simulator

.r s

(; validation exercise performed by.the WOG on the ERGS. An individual plant must identify differences between its E0Ps, both in format and usage, and the methods used in the generic .'alidation. The extent of applicability of the generic program to indivicual plant validation requirements is included in the -

Validation Program Final Report.

The WOG validation of the ERGS closely parallels the methodology described in

" Component Verification and System Validation" (DRAFT) NUTAC, May, 1983. The detailed planning process is included in the final WOG Validation Program Plan, and can be used in planning a plant-specific simulator validation program.

Training Several of the ERG documents contain information which is useful in-establishing a plants' E0P training program. First of all, the Validation Program developed a comprehensive training outline for presentation of s

)

J USERS GUIDE September 1, 1983 66398:1 37

e.

_( O ) ERG-based EGPs to operators. Additional comments on the effectiveness of the

program and suggestions for improvement were generated as a result of the validation exercise.

This Users Guide contains detailed instructions on the intended control room usage of the ERGS. These instructions may need to be modified to accommodate plant-specific implementation changes.

The guideline background documents contain specific Knowledoe Requirements for each action step (if any) which might not be part of the normal operator-license training /requalification program. -The documents also cor.tain discussions of the event (s) to which the guideline is responding, with-transient plots and sequence-of-events tables to enhance understanding of the entire guideline. , ,

The ERG Writers Guide contains information an E0P structure, format, and wording, which should also be factored into a training program.

l Summary This section has presented the elements of the Procedures Generation Package, as defined by INPO based on the requirements in NUREG 0737 Supplement 1.

Those separate documents included as part of the ERG Revision 1 package which are appliable in the development of a Procedures Generation Package were specifically referenced. Appropriate INPO documents to support the E0P effort were also specifically referenced.

k.

USERS GUIDE September 1, 1983 66898:1 38

O l

I i

SEABROOK STATION USERS GUIDE FOR EMERGENCY RESPONSE PROCEDURES BASED ON THE WESTINGHOUSE OWNERS GROUP USERS GUIDE FOR EMERGENCY RESPONSE GUIDELINES POST VALIDATION PROGRAM REVISION JANUARY 16, 1984 O

User's Guide for Emergency Response Procedures at Seabrook Station TABLE OF CONTENTS Section Page

1. Introduction 2

2. Control Room Usage of the Procedures 2

3. Example of Procedure Usage 5

4. Control Room Usage of Status Trees 7

5. Example of Status Tree Usage 9

6. Control Room Usage of the ERG Network 11

7. Modes of Applicability of the ERGS 13 L

c O

O

l. INTRODUCTION

( The Emergency Response Guidelines (ERGS) developed by the Westinghouse Owners Group (WOG) combined with plant specific knowledge provided by the Seabrook Station staff, has resulted in a complete' set of Emergency Respor'e Procedures (ERPs) for Seabrook Station. The two-column format used to present'the ERPs contains implicit rules of usage which supplement the technical instructions. The Critical Safety Function Status Trees have their own format and rules of usage. Priorities have been established bet-ween the Optimal Recovery Procedures (ORPs) and Function Restoration Procedures (FRPs) which are intended to direct operator action to the most urgent operational or safety conditions.

Each of these aspects of using the Emergency Response Procedures is pre-sented in detail in the following sections.

2. CONTROL ROOM USAGE OF ERPS Entry into an individual procedure begins at the cover sheet. The title block presents the unique identifiers for each procedure, and the purpose and entry conditions are described in separate paragraphs.

. Individual operator action steps are presented in the two-column format beginning on the following page. Certain special information is also pre-sented, which is emphasized by not following the standard two-column for-mat. This information is of two types:

O e NOTES contain administrative or advisory information which supports operator action.

e CAUTIONS contain information about potential hazards to personnel or equipment. They also advise on actions or transitions which may become necessary depending on changes in plant conditions.

Both NOTES and CAUTIONS are introduced by their descriptor, in bold let-ters, followed by the text extending across the entire pag.. If multiple items are included after a descriptor, each item is distincaished by a pre-ceding bullet (*).

In general, NOTES and CAUTIONS apply to the step which they precede. A NOTE or CAUTION which precedes tne first operator action step may also apply to the entire procedure. One type of NOTE in this category is described below:

1. Several procedures contain steps which are designated as "immediate actions". These steps are intended to be performed, if necessary, without the written procedure being available. These procedures con-

/

tain a NOTE advising which steps are "immediate action" steps.

After observing any initial NOTES and/or CAUTIONS, the operator proceeds to the first action step. In the two-column format, each step in the left-hand column contains a highlighted high-level statement which describes the task to be performed.

If the high level task requires multiple actions, then subtasks are spe-cified. Following each task or subtask, the expected response or result is O__ given in CAPITAL LETTERS, separated from the task by a dash.

Example: Check Pressurizer Level - INCREASING.

Example: Check if Pressure Boundary is Intact:

a. Check response in all SGs -

e NO SG PRESSURE DECREASING IN AN UNCONTROLLED MANNER

- OR -

o NO SG HAS COMPLETELY DEPRES-SURIZED Expected responses are not supplied for simple control manipulations or actions.

Example: Stop All RCPs.

If sequence of performance is important, then the subtasks are designated by letters (or numbers if fiaer detail is provided). If sequence of per-formance is not important, the suhtssks are designated by bullets (e).

I~ \ Only a limited set of action verbs is used in the action steps. These

\'-

verbs have specific meanings in the context of their usage in the ERPc.

(Refer to the verb list in the ERP Writers Guide.)

Action steps are written so that the operator can proceed directly down the 12ft-hand column only. This column contains all the expected conditions, actions, and checks required to accomplish the stated purpose of the procedure.

If however, the expected result or response is not obtained or the action cannot be performed, the operator should move to the right-hand column for contingency instructions. This column is appropriately titled " RESPONSE NOT OBTAINED". Almost all action steps contain some contingency action statement. If one contingency action is appropriate for any of a series of left-hand column subtasks, it is simply stated once as a high level con-tingency. If a contingency is not provided, then the operator should proceed to the next step or substep in the left-hand column.

~ Example:

Check CVCT Makeup Control Adjust controls as necessary.

O

,i i n - _ _ - - ___ _ _

System:

- f3 V a. Makeup set for GREATER THAN RCS BORON CONCENIRATION

b. Makeup set for AUTOMATIC The two column format thus equates to logical terms which would otherwise be specifically stated: ))[ the conditions required in the left-hand column are not achieved, THEN go to the right-hand column for contingency instruc-tions. For this reason, the first contingency action does not contain the highlighted logic terms ))[ and THEN. Subsequent contingency actions are always expressed using the logical construction.

Example:

Verify PRZR Level - GREA"ER Control charging flow to maintain THAN 17% PRZR level. IF PRZR level can NOT be maintained 7THEN manually ope-rate ECCS pumps as necessary.

After taking the contingency action in the right-hand column, the operator should proceed to the next step or substep in the left-hand column. If the contingency action cannot be performed or is not successful, and further contingency instruction is not provided, the operator should again return to the next step or substep in the left-hand column.

Unless otherwise specified, a required task need not be fully completed

( )

~

before proccuding to the next instruction; it is sufficient to begin a task and have assurance that it is progressing satisfactorily. This assures efficient implementation where steps are very time consuming. In certain cases, where local operator actions are required (outside the control room) a special NOTE may be added to reinforce this rule of procedure usage.

If a particular task must be complete prior to proceeding, the step con-taining the task will explTeitly state that requirement.

Transitions to other procedures or to different steps in the same procedure may be made from either column. Such transitions should be made realizing that preceding NOTES or CAUTIONS are applicable. Any tasks still in progress need not be completed prior to making a transition; however, the requirement to complete the tasks is still present and must not be neglected.

Each procedure ends with either a specific transition to another procedure, if further operator guidance is required, or with the plant being main-tained in a steady-state condition. Often in ERPs, the final transition is to " procedure and step in effect". This wording results from the symptom-dependent transitions performed in accordance with rules of usage and not located at a specific procedure and step. " Step in effect" refers to whichever step was being performed when transition was made into the pre-sent procedure.

>v

As an example. assume an-operator is performing procedure A, when symptoms

[ . .

appear requiring transition to procedure B. While performing procedure B, in accordance with a CAUTION, he finds it necessary to go to procedure C.

L After completing.the actions in C, he returns to the procedure and step

' from which he entered C, that is, back to procedure B. And after complet-I ing procedure B, ths operator would return to the procedure and step from which he entered B, in this case, procedure A. (This example assumes that l procedures A, B, and C all end with the transition words " Return to Procedure and Step in Effect".)

Several series of procedures have been provided with an OPERATOR ACTION

SUMMARY

page. This page is located on the back side of the previous pro-cedure page and is always visible to the operator regardless of the proce-dure step in effect. The OPERATOR ACTION

SUMMARY

contains several pieces of information or actions which are applicable at, jugt step in the proce-( dure. 'The most important of these actions are procedure transitions which allow immediate response to new symptoms as they appear. The placement of these transitions on the.0PERATOR ACTION

SUMMARY

page removes any sen-sitivity to timing from the appearance of subsequent symptoms.

3. EXAMPLE OF PROCEDURE USAGE The actual process of working through a procedure will be illustrated by using E-2, FAULTED STEAM GENERATOR ISOLATION. It is assumed that the user was directed to Step 1 of this procedure by an instruction in some other procedure.

-The user first verifies the' designator and title on the cover sheet to assure himself that he is in the proper progedure. The PURPOSE tel1 3 him that this procedure will identify and isolite a faulted steam generator.

Examination of the SYMPTOMS OR ENTRY CONDITIONS list should produce the procedure from which the transition to E-2 was made in this case.

The first action step of this procedure is preceded by two CAUTIONS. Each separate concern is identified by a bullet (*),'and the CAUTION identifier is used only once.

The first CAUTION tells the operator that at least one SG must be main-tained available for RCS cooldown.

The second CAUTION tells the operator that any faulted SG or secondary break should remain isolated during subsequent recovery actions unless needed'for RCS cooldown. Both CAUTIONS refer to the SG isolation which will take place in the next step (s). The operator is expected to know that

" faulted" refers to failure of the secondary pressure boundary, and

" isolated" refers to closure of the stem and/or feed flow paths. The CAUTIONS have provided a specific criteria (needed for RCS cooldown) for not isolating, or un-isolating a faulted SG.

The first action in Step 1 is a check of the main steamline isolation and

-bypass valves on the affected SGs. The expected condition is that the valves are CIOSED. If, in fact, the operator finds the valves closed by i

[} whatever means his training requires, he then proceeds to Step 2. If the

valves are not closed, or not closed on all the affected SGs, the operator

. moves to the right-hand column where a contingency instruction tells him to

" Manually Close Valves". After performing this action, the operator would return to the next task in the lef t-hand column, in this case, Step 2.

The Step 2 high-level action is to " Check if SG Pressure Boundary Is Intact" with a more detailed subtask describing how this is to be done:

the operator is to " Check Pressures in All SGs". The expected response is "ANY (SG Pressure) STABLE OR INCREASING. If any pressure is stable or increasing, the operator proceeds to the Step 3. If none of the steam generators exhibits a stable or increasing pressure, the operator moves to the right-hand column for contingency instructions. He is told, "IF all SG pressures decreasing in an uncontrolled manner, THEN go to ECA-2.1, UNCONTROLLED DEPRESSURIZATION OF ALL STEAM GENERATORS, Step 1". In order to perform this step, he has to decide if the depressurization is controlled, or not. If it is not controlled, he will leave E-2 and make the required transition to ECA-2.1. If however, the pressure decrease is under his control, in at least one steam generator, he proceeds to the next lef t-hand column task, Step 3.

Step 3 requires the operator to " Identify Faulted SG(s)" and the more detailed process is described in a substep " Check Pressures in All SGs".

Two possible pressure responses are given which will satisfactorily iden-tify a faulted SG: ANY SG PRESSURE (is) DECREASING IN AN UNCONTROLLED MANNER, or ANY SG (is) COMPLETELY DEPRESSURIZED. If either condition is observed, than the intent of the step is satisfied and the faulted SG(s) is (are) identified. The operator moves on to Step 4. If neither condition is observed on any SG, the operator moves to the right-hand column where he C.\ is instructed to search for the initiating break (which may have been iso-lated by MSIV closure) and then to go to Step 5, i.e., skip over Step 4 since no steam generator is required to be isolated.

Step 4 tells the operator to " Isolate Faulted SG(s)" and lists several separate paths which should be isolated. The bullet (e) designator on the separate items implies that isolations can be done in any order. If the isolations are properly performed, the operator proceeds to Step 5. If some aspect of isolation cannot be completed,-he moves to the right-hand

, column where he is instructed to manually close the valves (from the control room), and if that is not successful, to dispatch a (local) opera-tor to close the desired valve (s) or appropriate block valve (s). With the contingency performed or local action initiated, the operator proceeds to Step 5.

The CAUTION prior to Step 5 alerts the operator that EFW system operation will eventually deplete the CST and that makeup will be required. The sooner the better in this case.

Step 5 simply has the operator Check the present level in the condensate storage tank. It is expected to be - GREATER THAN 23 FEET . If level is as expected, the operator proceeds to Step 6. However, if level is less than expected, he moves to the right-hand column where he is instructed to establish CST makeup at the maximum rate. From his training, he will Ter-form this task and then proceed to the left-hand column of Step 6.

6-y ep----f n -- + y -g- - - w,v. - p ,_u ,t~e *y- -- * ' -- y

Step 6 is a Check for secondary radiation. Detailed performance of the task is presented in sequential subtasks. First, the operator is to (73,) " Request Periodic Activity Samples of All SG(s)". This will invs'ee a call out to a local operator, with attendant time delays for sampling and analy-sis. By rules of usage, the operator can proceed to the next subtask

" Check Un-isolated Secondary Radiation Monits s", which he should be able to do from the control room. The third subtask is the conclusion on the

" Check" process, " Secondary Radiation - NORMAL". If no abnormal radioac-tivity is known or detected at that time, the expected response is obtained and the operator proceeds to Step 7. If abnormal radiation is detected on the secondary side of any steam genera *;r, then, by rules of usage, the operator moves to the right-hand column and is instructed to "Go to E-3, etc." and so leaves the E-2 procedure.

Step 7 tells the operator to "Go to E-1, etc." and thus ends the procedure with a transition to some other appropriate procedure.

The highlighted END centered on the page emphasizes that the listing of action steps for E-2 is complete.

In many cases, FIGURES and ATTACHMENTS are included in the procedures to aid the operator and to remove lengthy instructions such as valve align-ments from the procedure text. For example, FIGURE E-3-1 in procedure E-3 provides a curve showing the programmed LTOP setpoint for the pressurizer PORVs. ATTACHMENT A in procedure E-3 lists conditions that show positive evidence of natural circulation flow in the RCS.

4. CONTROL ROOM USAGE OF STATUS TREES (J)

Status Trees are a convenient device used to evaluate the current state of predefined CRITICAL SAFETY FUNCTIONS. When the Functions are shown to be satisfied, the plant is safe. Trees ask a series of questions about plant conditions, and in general, each question asked depends on the answer to the previous question. This dependancy results in a branching pattern, which is refarred to as a " tree".

There are six different trees, each one evaluating a separate safety aspect of the plant. (Critical Safety Function.) At any given time, a Critical Safety Functica status is represented by a single path through its tree.

Since each path is unique, it is uniquely labeled at its end point, or ter-minus. This labeling consists of color and/or line pattern coding of the terminus and last branch line, plus a transition to an appropriate prcee-dure if required by that safety status. If the status is normal for a par-ticular Critical Safety Function, no transition la specified, and the condition is clarified by the words CSF SATISFIED.

Color coding can be either Red, Orange, Yellow, or Green, with Green repre-senting a " Satisfied" safety status. Each non green color represents an action priority as discussed below.

(O J

, _ i l

The six Status Trees are ALWAYS evaluated in the sequence:

PRIORITY STATUS TREE CODE 1 Suberiticality (S) 2 Core Cooling (C) 3 Heat Sink (H) 4 Integrity (P) 5 Contalament (Z) 6 Inventory (1)

If identical color priorities are found on different trees during moni-toring, the required action priority is determined by this sequence. The user begins monitoring with the Subcriticality tree. Entry is at the arrow at the left side of the tree. Questions are answered based on plant con-ditions at the time, and the appropriate branch line followed to the next question.

An individual status tree evaluation is complete when the user arrives at a color - (or line pattern) - coded terminus. With the exceptions noted below, the color and instructions of the terminus are noted (logged) and the user continues to the next tree in sequence, again entering at the left-hand side arrow.

'If any RED terminus is encountered, the operator is required to immediately stop any Optimal Recovery Procedure (ORP) in progress, and to perform the Function Restoration Procedure (FRP) required by the terminus.

If during the performance of any RED - condition FRP, a RED condition of higher priority arises, then the higher priority condition should be addressed first, and the lower priority RED-FRP suspended.

If any ORANGE terminus is encountered, the operator is expected to monitor all of the remaining trees, and then, if no RED is encountered, suspend any ORP in progress and perform the FRP required by the ORANGE terminus.

If, during the performance of an ORANGE - coded FRP, any RED condition or higher priority ORANGE condition arises, then the RED or higher priority ORANGE condition is to be addressed first, and the original ORANGE FRP suspended.

Once a FRP is entered due to a RED or ORANGE condition, that FRP is per-formed to completion, unless pre-empted by some higher priorit.r condition.

It is expected that the actions in the FRP will clear the RED or ORANGE condition before all the operator actions are complete. However, these procedures should be completely performed to the point of the normal tran-sition back to " Procedure and Step in Effect".

Tree monitoring should be continuous if any status coded ORANGE or RED is found to exist. If no condition more serious than YELLOW is encountered, monitoring frequency may be reduced to 10-20 minutes, UNLESS some signifi-cant change in plant status occurs.

_g_

l Monitoring may be terminated after the Reactor Protection System and Engi-

/% neered Safeguards System are both restored to operable status (SI reset and i (,,) trip breakers closed). At this point, the operator should no longer be using the ERPs.

A YELLOW terminus does not require immediate operator attention.

Frequently it is indicative of an off-normal and/or temporary condition which will be restored to normal status by actions already in progress. In other cases where RED or ORANGE termini are possible, the YELLOW status might provide an early indication of a oroblem developing. Following FRP implementation, a YELLOW might indicate a residual off-normal condition.

The operator is allowed to decide whether or not to implement any YELLOW condition FRP.

Tree monitoring can be done automatically by computer; however, the opera-tor should verify proper automatic status monitoring at least once and as early as possible. This is accomplished by comparing status tree indica-tions with hard wired MCB indicators for appropriate parameters.

5. E_XAMPLE OF STATUS TREE USAGE The actual process of working through the trees will be illustrated by exa-mining the first (Suberiticality) status tree. The user enters the tree at the left-hand arrow and is asked if neutron flux (NIS channels) indication is less than 5%. The possible answers are either "yes" or "no". If indi-cated power is greater than 5%, then the appropriate answer is "no", so the user would follow the "no" path directly to the terminus and determine fV ') that:

e the response priority is RED (immediate response required) e the appropriate Function Restoration Procedure is FR-S.I.

According to the Rules of Priotity, the operator should suspend whichever ORP is being performed and immediately initiate the actions in procedure FR-S.I. Monitoring of the Status Trees may continue for information pur-poses, but by Rules of Priority, no other higher priority condition can exist. When the actions required by FR-S.1 are complete, the operator is directed to " Return to Procedure and Step in Effect". This allows recovery actions to continue exactly where they were suspended when the RED priority was recognized. This also signals continued monitoring of status trees.

In this case, the user and/or operator would know, because of the FR-S.1 actions and checks, that the suberiticality tree would have no status more severe than YELLOW.

If indicated power is less than 5%, then the first question block is answered with a "yes" and the user would follow the "yes" path to the next question block.

In this second block, the user is asked whether the Intermediate Range Startup Rate is zero or negative. If the indicated rate is positive, then the user would follow the "no" response path directly to a termines and

() determine that:

_9_

l'

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ m

6&&

IMAG. . val.U ATION / #

M4:f/, ,.., -., < ,

, //// , g[4,,

g/g+ <-

l.0 d2 E yll RR i,i [m GE "

l.8 0

1.25 . l.4_ l.6 4 150mm >

< 6" >

1. %,, / 4 h///

thAih4

• $[$7777 ,_

oge

w the response priority is ORANGE (prompt response required) o the appropriate Function Restoration Procedure is FR-S.I.

Accordiag to the rules of usage, the remainder of the status trees shculd be monitored to determine if any RED conditions are present. If no RFD status is encountered, then any ORANGE conditions would be reviewed for priority. Since suberiticality is the first status tree, the present ORANGE would be addressed first by rules of priority. Again the operator would suspend whichever ORP was being performed and initiate the actions in procedure FR-S.I. Monitoring of the status trees should continue in order to promptly identify any RED conditions which might arise and take

priority. When procedure FR-S.1 is completed, the operator can again

return to his normal recovery action at the point where it was tuspended -

unless other ORANGE conditions. require attention first. Again, order of tree sequence would determine ORANGE priority.

If the answer to the second block question were "yes", the user would follow the "yes" path to a third question block.

This time the question is whether the source

• range is energized. This can easily be answered by checking the detector high voltage indication, or by

noting the Source Range beeper. If the Source Range is determined to be not energized, the user follows the "no" path upward to another question block. Now he is asked if the Intermediate Range startup rate is more negative than .2 DPM. If the indicated startup rate is between zero and

.2 DPM, then the user would follow the "no" path directly to a terminus and find that:

e the response priority is YELLOW (action not required immediately) e the appropriate Function Restoration Procedure is FR-S.2.

Since the status priority is YELLOW, the user would continue to monitor the remaining trees and deal with any RED or ORANGE priorities which might be l encountered. If no other condition coded higher than YELLOW were present, l

then the operator would decide if the FRP should be performed or delayed.

Often, a YELLOW is indicative of an off-normal condition which may be restored to normal status by actions already in progress. At other times, the YELLOW status may be indicative of an abnormality in a single RCS loop

- a single SG, for example and may be considered acceptable for the par-ticular accident in progress. Whatever the case, the operator makes the decision about responding to the YELLOW condition.

If the Intermediate Range startup rate is more negative than - .2 DPM, then the user would follow the "yes" path downward to a terminus and find the condition coded GREEN, the annotated "CSF SAT;" the Critical Safety Function - SUBCRITICALITY, is considered satisfied, so the user proceeds to evaluate the next status tree in the sequence.

If tue Source Range was found to be energizei, in response to the third question block, the user would follow the "yes" path downward to another question block. This time he is asked if the Source Range startup rate is m

t d

negative or zero. Since the source range signal is normally erratic, it will be necessary for the user to lo)k at a recorder trend of count rate to Oq properly evaluate the startup rare. If positive, the user would follow the "no" path upward to a terminus and find:

w the response priority is YELLOW w the appropriate Function Restoration Procedure is FR-S.2 The operator would again use his judgement regarding implementation of FR-S.2 while continuing recovery operations and observing the rules of usage for toe other status trees.

If the Source Range startup is observed to be negative, the user follows the "yes" path downward out of the question box and finds the condition coded GREEN, the safety function is satisfied. The user would move directly co the next tree in the sequence.

6. CONTROL ROOM USAGE OF THE ERP NETWORK While the previous sections discussed the separate usage of an individual procedure and evaluation of status trees, this section presents the intended overall usage of this entire ERP network.

Direct entry into the Emergency Response Procedures is limited to TWO SPECIFIC CONDITIONS:

w If at any time a reactor trip or safety injection occurs OR IS REQUIRED, N- the operator will enter procedure E-0, REACTOR TEIP OR SAFETY INJECTION.

• If at any time a complete loss of power on the AC emergency busses takes place, the operator will enter ECA-0.0, LOSS OF ALL AC POWER. This includes any time during the performance of ANY other ERP.

The entry into E-0 is expected to be the one more frequently used, so is described first:

The operator proceeds through E-0, following the rules of procedure usage as described above, with two possible outcomes:

l w He remains in E-0 and is directed by an action step to begin monitoring j the status trees.

I - OR -

w He transitions to some other guideline, at which point he begins to monitor th'e status trees.

Monitoring of the status trees takes place in accordance with its own rules of usage, in parallel with the recovery actions being performed by the operator. The monitoring may be done directly by one of the operators in the control room, by some other member of the shift assigned to the control room, or by a dedicated computer routine. The only requirement of the 0  :

l

---

r-- ,_-,.,a -

.,- - - - - -c_, ,x - , < - - - - - . - - ' - - - - - - - - - - - - -

monitoring function is that the operator in charge of recovery actions be p immediately informed of RED or ORANGE priority status conditions, and regu-Q larly advised of YELLOW and GREEN conditions.

The ORP actions in progress are suspended if either a RED or ORANGE con-dition is detected on a status tree. N_o ORP actions are to be performed while a critical safety function is being restored from a RED or ORANGE condition, unless directed by the FRP in effect.

After restoration of any Critical Safety Function from a RED or ORANGE con-dition, recovery actions may continue when the FRP is complete. Most often, the FRP will return the operator to the suspended ORP. However, at times a FRP will require a transition to a different ORP because of con-ditions created within the FRP.

Upon continuation of recovery actions, some judgement is required by the operator to avoid inadvertent reinstatement of a RED or ORANGE condition by undoing some critical step in a Function Restoration Procedure. The plant recovery procedures are optimal assuming that equipment is available as required for sefety. The appearance of a RED or ORANGE condition implies that some equipment or function required for safety is not available, and by implication, some adjustment may be required in the recovery procedures.

An example might be the establishing of an alternate feed path to the steam generators as required by FR-H.l. With feed. flow from either the main feed o'r condensate system, the operator would NOT want to 1 olate the main feed line as required by ES-0.1.

( \ -

V Direct entry into ECA-0.0, due to loss of AC power on both (4 KV) safe-guards busses is expected to be a rare occurrence. However, once in ECA-0.0, special considerations come into effect. Because none of the

! electrically powered safeguards equipment used to restote 6ritical Safety Functions is operable, none of the FRPs can be implemented. A NOTE at the beginning of procedure ECA-0.0 states "CSF Status Trees should be monitored for information only. FRPs should not be implemented". Once in ECA-0.0, l the operator performs the required actions, and is not allowed to tran-f sition to any other procedure until some form of power is restored to the l (4 KV) Safeguards busses. Even then, permission is not granted to imple-ment FRPs until some initial status checks are performed by the operator.

Certain cmergency contingency actions (ECA) take precedence over FRPs because of their treatment of specific initiating events. In all such cases, this precedence is identified in a NOTE at the beginning of the ECA '

l procedure.

For example: ECA-2.1 deals with depressurization, loss of level, and resultant feed flow reduction to ALL steam generators. While this con-dition results in a RED priority on the Heat Sink Status Tree, the referen-ced procedure, FR-H.1, returns the operator to ECA-2.1 for the preferred L

treatment of the event. ECA-2.1 contains an introductory CAUTION stating l

the specific conditions under which FR-H.1 should be implemented. -

l

A more dramatic example is ECA-0.0 which provides the best strategy for g maintaining Critical Safety Functions satisfied and protecting barriers

( ) until (4 KV) safeguards AC power is restored.

One unique procedure in the ERP set has no transitions or direct entry con-ditions. It is used purely as an operator aid and is entered based purely on operator judgement. The procedure is ES-0.0, REDIAGNOSIS. It is intended to be used af ter departure from E-0, only if SI has been actuated.

j It provides reassurance to the operator that he is in the correct proce-dure, or provides the necessary transition instruction to get to the correct procedure for the existing symptoms. Operator need for this rediagnosis procedure is limited in the Rev. 1 ERPs, because many of the transitions needed to respond to new symptoms are included in the OPERATOR ACTION

SUMMARY

. However, its presence can be reassuring to an operator after making several consecutive transitions due to rapidly changing conditions.

ERP usage always ends in one of the following ways:

w Transition to a normal (not an E0P) plant operating procedure (stable).

w Transition to some " appropriate" procedure while on RHR at cold shutdown conditions (stable).

w On cold leg recirculation or hot leg recirculation with longer term recovery actions being determined by the individual utility (stable).

i N 7. MODES OF APPLICABILITY OF THE ERPS The ERP network was originally written to accommodate transients occurring at a " hot" or "at power" condition. The transients envisioned would result in either Reactor Protection System or Safeguards Systems actuation, with some corresponding, or subsequent, operator action needed. The guidance for operator action is based upon having the safety-related equipment required by Tech Specs for MODE 1 or MODE 2 operation available for his use. For transients initiating during other MODES of operation, the same complement of equipment cannot be assumed available, so that the detailed instructions within the ERPs may not be applicable. Just as earlier steps in the ERPs generally involve response to the transient, later stepc generally relate to getting the plant to a cold shutdown condition. If the plant is already substantially cooled and depressurized, some detailed instructions may not be applicable.

Critical Safety Function monitoring using the Status Trees also assumes a MODE 1 or MODE 2 initial condition, followed by some Protection System actuation, to result in a suberitical reactor. Use of the trees can be extended beyond this original intent, but with an understanding of the intent of each tree. For example, the Heat Sink Tree assumes the steam generators are available for heat removal by steaming. If all reactor decay heat is being removed by the RHR system, the steam generators are not

, required in their normal capacity. So, SC availability is really not required to be satisfied. Yet the tree would indicate a SG in wet layup to be OK, while one in dry layup would be abnormal.

To clarify the usability of the ERPs for transients originating during.

other than the ascumed initial operating MODES, a detailed review of the

, _j entire network has been performed. The results are presented in the following table. In some cases, slight modifications are needed to extend the_ applicable range of a guideline beyond its original intent.

Procedure Designator Applicable Modes

• Comments E-0 1, 2, 3 RHR not in service and SI operable ES-0.0 1, 2, 3, 4 (Assumes trip from power)

ED-0.1 1, 2 ES-0.2 Hot (near no load),

ES-0.3 slight modification ES-0.4 required if already in cooldown E-1 1, 2, 3 RHR not in service ES-1.1 _

ES-1.2 RHR not in service, entry is limited by stated con-

[ ditions j

E-2 1,2,3,4 Temp > 212*F E-3 1,2,3,4 RHR not in service ES-3.1 ES-3.2 ES-3.3 ECA-0.0 1,2,3,4 Partly hot and pressu-ECA-0.1 rized ECA-0.2 1

ECA-1.1 Specific entry conditions ECA-1.2 provided i

ECA-2.1 1,2,3,4 RHR not in service, hot O .

I Procedure Designator Applicable Modes

• Comments ECA-3.1 1,2,3,4 RHR not in service ECA-3.2 ECA-3.3 F-0.1, Suberiticality 1-4 F-0.2 Core Cooling 1-4 F-0.3, Heat Sink 1-4 Unless RHR in service F-0.4, Integrity 1-4 Slight problem with cool-down rate in MODE 4 F-0.5, Containment 1-4 F-0.6, Inventory 1-4 F R-S .1 1-4 (AFW not required if on RHR)

' F R-S . 2 1-4 O FR-C.1 1,2,3 Partial MODE 4 on SI F R-C . 2 equipment availability, secondary lineup F R-C . 3 1-4 F R-H.1 1-4 Bleed and feed may be too soon for MODE 4 F R-H . 2 1-4

. F R-H . 3 1-4 Except wet layup F R-H . 4 1-4 F R-H . 5 1-4 Except dry layup O

Procedure Designator Applicable Modes

• Comments F R-P .1 1-4 Entry may not be neces-sary if initial tempera-ture was low F R-P . 2 1-4 FR-Z.1 1-4 FR-Z.2 1-4 FR-Z.3 1-4 F R-I .1 1-4 Some exceptions if RHR in service F R-I . 2 1-4 Possible exception of SI initiation F R-1. 3 1-4 t

t Operating MODES as used here has the. same definition as the Seabrook Technical Specifications:

I THERMAL POWER l REACTIVITY (% RATED, EXCLUDING AVERAGE

- s MODE (Keff) DECAY HEAT) COOLANT TEMPERATURE

1. Power Operation > 0.99 >5 > 350*F

2. Startup 7 0.99 <5 7 350*F

3. Hot Standby T 0.99 7 7 350*F

4. Hot Shutdown < 0.99 0 750*F>Tavg>200*F

5. Cold Shutdown < 0.99 0 < 200*F (Mode 6, Refueling, is not considered in the contect of ERP applicability.)

i i

i l

0 l O

1 I

t ERG REV. 1 l

. VALI)ATION

\

TRAIhIhG & TESTIhG 1

l i

e I

9 - - .

9

ERG REV. 1 VAllDATION TRAINING COURSE DAY l DAY 2 DAY 3 DAY 4 DAY S

0 Validation Test 4 Review e Review e Review 8 Review L Prograun 8 Secondary Breaks e SGTR e FRGs e LOCA 8 Structure of - E-1 Series - E-2 - E-3 Series - Il-Series ERGS /Trarisi t ion - ECA-1 Series - ECA-2.1 - ECA-3 Series - C-Series f F1 w Diagranis R e ICC 4 FRGs ,

e Exairiina tion 0 8 Users Guide- - FR-C.i - S-Series a Final Procedure 3 Fornu t - FR-il.1 - P-Series Checks e CSF Status Trees [ h3 8 E-0 Series 8 ECA-0 Series S 8 Introduction 4 LOCA 8 Secondary Break 4 SGTR 0 Loss of All Feedwa ter/

I - DBA - Outside CTMT - Snia l l Loss of Offsite Power 4 Rx Tr 1p H - With Switchover - Unisolable - Cooldown using e Surprise Tearsient U 8 Spurious SI 4 LOCA 8 Secondary Break "d "' ""'"E

- Inside CTMT 4 SGlR fy 8 Loss of All AC - Snul l

- With Cooldown - MSIVs fail to - DBA Close - Cooldown With b e ICC "" C "

R - Small LOCA 8 AlWS

- Without ECCS 4 SGlR/ Secondary Break O O O

DAY l CLASSROOM e VALIDATION PROGRAM OVERVIEW TRAINING TESTING G STRUCTURE OF ERGS / TRANSITION FLOW CllARTS 4 USERS GUIDE - FORMAT S CRITICAL SAFETY FUNCTIONS (CSF) STATUS TREES 0 E-0 SERIES 0 ECA SERIES SIMULATOR 8 INTRODUCTION RULES OF SIMULATOR USE OPERATOR ROTATION 0 Rx TRIP 0 SPURIOUS SI e LOSS OF ALL AC O O O A

t IMERGENCY RESPONSE GUIDELINES S '

G e

i ERG STRUCTURE (OBJECTIVES) l 0 SATISFY OVERALL ERG PROGRAM OBJECTIVES l

8 STRUCTURE FOR EMERGENCY OPERATIONS EXCEED REACTOR PROTECTION SYSTEM LIMITS EXCEED ENGINEERED SAFETY FEATURE LIMITS l 0 IDENTIFY EVENT / PLANT CONDITION AND REC 0VER PLANT 4 IDENTIFY CilALLENGES OF PLANT SAFETY STATE AND RESTORE SAFETY STATE i

e ACCOMMODATE FUTURE EVOLUTIONARY DEVELOPMENT WITil MINIMUM IMPACT l

1 O O O

---

,--,oem w

b 9

ERG PROGRAM ELEMENTS 0 OPTIMAL REC 0VERY GUIDELINES (0RGs) 8 CRITICAL SAFETY FUNCTION (CSF) STATUS TREES .

8 FUNCTION RESTORATION GUIDELINES (FRGs)

O O O

OPTIMAL RECOVERY GUIDELINES S EVENT-SPECIFIC 8 EVENT DIAGNOSTICS S OPERATOR GUIDANCE FOR PLANT REC 0VERY FROM KNOWN EVENT / CONDITION STATE 8 MAINTENANCE OF CSFs INilERENT IN GUIDELINES 8 EQUIPMENT FAILURE CONTINGENCIES AND TRANSITIONS TO FRGs O O O

STATUS TREES 8 MONITORING PLANT SAFETY STATUS TOTALLY INDEPENDENT OF ORGs e CilALLENGES TO CSFs SYSTEMATICALLY AND EXPLICITLY DIAGNOSED e APPROPRIATE FRG PRIORITIZED BY STATUS TREES O O O

=he*4 m 4

FUNCTION RESTORATION GUIDELINES S NON-EVENT-SPECIFIC 4 STATUS TREES' YELLOW, ORANGE, OR RED TERMINUS COVERED BY GUIDELINES 8 DIRECT RESPONSE TO CSFs CilALLENGES e TRANSITIONS TO ORGs AFTER SAFETY FUNCTION CllALLENGE REMOVED 9 COMPREllENSIVE COVERAGE 8 ALL CONCEIVABLE CilALLENGES TO CSFs ADDRESSED O O O A

i i

l Code: Sympto=/

Title:

Procedure No. i Revision No ./Date:

E-0 REACTOR TRIP OR SAFETY INJECTION OS-1300 Rev. 1-7 0-7 / 10/06/83 lSTEPl l ACTION / EXPECTED RESPONSE I I RESPONSE NOT OBTAINED I l

8 Verify ECCS Pu=ps Running: Manually start pu=os.

e CCPs - TRAIN A AND 3 e SI pumps - TPMN A AND 3 1

e RER pu=ps - TRAIN A AND 3 I i

9 Verif y

• CCW i Pu=ps - RUNNING: Manually start pu=os.

a. Loop A - ONE PLMP RUNNING

b. Loop 3 - ONE PLMP RCNNING

c. Ther=al barrier cooling pu=ps - AT LEAST ONE PLMP  !

RCNNING 1

10 Verify Ulti= ate Heat Sink Manually start pu=ps and align  !

Ope rati en: valves as necessary. I

a. Train A - RUNNING

1) One SW pu=p

- OR -

2) One CT pu=p AND CT fan in TA = ode

b. Train 3 - RUNNING

1) One SW pu=p

- OR -

\

2) One CT puc:p MiD CT Jan in TA = ode I

L 4 of 23

Code: Sy=ptos/

Title:

Procedure. No . I Revision No./Date:

FR-S.1 RESPONSE TO NUCLEAR MWER GENERATION /ATWS OS-1351.1 f Rev. 1-T 0-r / 10/11/83

!STEPi l ACTION / EXPECTED RESPONSE i l RESPONSE NOT OBTAINED i NOTE Steps 1 through 4 are IMdEDIATE ACTION steps.

1 Verify Reactor Trip: Manually trip reactor. IF reactor will NOT trip, TEEN ,

e Rod bottom lights - LIT sanually insert control rods . l ON DRFI e Reactor trip and bypass l breakers - OPEN e Rod position indicators -

AT ZERO ON ORPI e Neutron flux - DECREASING i

2 Veriff Turbine Trip:

a. All turbine stop valves - a. Manually trip turbine. IF,

(, CIDSED turbine will NOT trip, THEN i sanually run back turbine .

IF turbine can NOT be run-l back, THEN close nain stea=- ,

line isolation and bypass valves.

i 3 Check EFW Pumps Running:

l I a. MD pump - RUNNING a. Manually start pu=p.

b. Turbine-cciven piisp - b. Manually open steam RUNNIN G. supply valves.

l e MS -V127 e MS-V128 s

s

-w 2 of 6

Number: Titis: Rev. Issue /Date:

F-0.4 INTEGRITY HP/LP, REV.1

's Sept.,1983 o

$o v E

8 0=

T1 T2 COLD LEG TEMPERATURE rR-P ALL RCS PRESSURE NO GO TO Emmmm

- COLD LEG g FR-P.1 TEMPERATURE PolNTS TO E RIGHT OF YES LIMIT A ALL RCS NO GO TC i

l COLD LEG ee FR-P'~'

TEMPERATURES g GREATER THAN g (1)CF YES ALL RCS NO TEMPERATURE COLD LEG DECREASE NO TEMPERATURES i IN ALL COLD GREATER THAN

+ LEGS LESS (2)0F YES THAN 100cF IN THE LAST 60 YES MINUTES -

CSF

' SAT 5 rR P ALL RCS NO COLD LEG TEMPERATURES GREATER THAN (1)0F YES RCS PRESSURE NO LESS THAN COLD 8 GO TO I

OVERPRESSURE 88 FR P.2 LIMIT YES NO RCS

_ TEMPERATURE GREATER THAN (3)0F j CST YES SAT

, CSF SAT

E ' '

Number: Tule: Rev. Issue /Date:

F-0.4 INTEGRITY HP/LP, REV.1 1 Sept.,1983 ANY RCS PRESSURE - COLD LEG TEMPERATURE POINT TO LEFT OF LIMIT A TEMPERATURE DECREASE

IN ANY COLD LEG GREATER THAN 1000F IN THE LAST 60 MINtil ES ANY RCS COLD LEG TEMPERATURE LESS THAN (1)0F FR-P.1 ALL RCS PRESSURE-COLD F M M M M M M M M LEG TEMPERATURE POINTSg TO RIGHT OF LIMIT A g ANY RCS COLD LEG TEMPER ATURE LESS THAN (2)0F GOTO ALL RCS COLD LEG #####64OOOee FR-P.2 TEMPERATURES GREATER S THAN (1)0F e E J y p ALL RCS COLD LEG TEMPERATURES.,

GREATER THAN (2)0F

. g "

CSF a SAT U ANY RCS COLD LEG m T1 T2 TEMPL.1ATURE COLD LEG TEMPERATURE

• LESS THAN (1)0F mm TO RCS PRESSURE GREATER THAN g ALL RCS COLD LEG COLD OVERPRESSURE LIMIT TEMPERATURES TEMPERATURE DECREASE G GREATER THAN(1)0F GO TO IN ALL COLD LEGS RCS TEMPERA URE 446644ee LESS THAN 1000F LESS THAN (3){F FR-P.2 IN THE LAST 60 Mif.UTES l RCS PRESSURE LESS THAN COLD OVERPRESSURE LIMIT CSF RCS TEMPERATURE GREATER THAN (310F

_ _ _ _ _ -_ m --

Goofi dymp tom / Iitle: Procacure so.

Revision No./Date:

E-3 STaati GENERATOR IUdE AUPTURE 0S-1330 Rev. 1-T 0-T/ 10/07/83

?

A. PURPOSE

/ This procedure provides actions to ter=inate leakage of reactor s coolant into the secondary system following a staam generator tube rupture.

3. SYMPTOMS OR ENTRY CONDITIONS .

This procedure is entered fron:

1) E-0, MCTOR TRIP OR SAFETY INJEC'" ION , Step 23 when concenser effluent radiation or SG blowdown radiation is abnormal.

2) E-0, &CTOR TRIP Od SAFETY INJECTION , Step 29, E-1, WSS OF LCTOR OR SECONDARY COLANT, Step 4, s-2, FAULILJ stead GENEdaIOR ISOLATION , Step o, and FR-d . 3, DES PONS c. ID 5 TEAM CERATOR HIGH LEVEL, Step 7, when seconcary radiation is abnorsal.

3) t-0, REACTOR TRIP Od SAFdTY INJECTION, Step 28, E-1, WdS OF REACTOR OR SECONDARY COOLANT, Step 3, ES-1.2, P]ST-LOCA COLDOWN AND DEPRESSURI7ATION , Step 7, ES -3 .1, PJST SGTR Q0LDL3 USING BACKFILL, Step 4, ES-3.2, EST SGTR (DOLD0k'N USING BL34DOWN , Step 4, ES-3.3, PJST SGTR (DOLDOWN USING STEAM DUMP, Step 4, ECA-3.1, SGTR '41TH WSS OF REACTOR CD0LANT - SUBC00 LED RECOVERY DESIRED, Step 9, ECA-3.2, SGTR '41TH WSS OF REACTOR COOLANT - SATURATED RECOVERY OESIRED, Step 4, and ECA-3.3, SGTR WITHOUT PRESSURIZER FRESSURE QNTROL, Step 5 when any intact SG narrow range level increases in an uncon- l trolled canner.  ;

l I

4) EC4-3.3, SGTR JITHOUT PRESSURIZER FRESSURE (DSTROL, Steps 2, ,

3, and 4, when pressurizer pressure control is restored.

h 1 of 27 -

s

Symptem/

Title:

Procedure No.

l Code:

Revision No ./Date: f E-0 REACE R TRIP OR SAFETY INJECTION 0S-1300

.te v . 1-T 0 -T / 10/06/83 I dTEPI l ACTION /EXPEC"'ED RES PONSE I I RESPONSE NOT OSTAINED I l

i 28 Check SG Levels:

a. NR level - GREATER a. Maintain total EFW flow THAN 5 greater than 470 GPM to intact SGs until NR level greater than 5" in at least ,

one SG. DO NOT allow intact SG WR level to decrease below top of U-tube s .

l LEVEL A30VE SG U-TUBES l

! ADVERSE CONTM i NORMAL CONTM i, NARROW RANGE WIDE RANGE LEVEL GREATER LEVEL GREATER THAN 28% THAN 65 l

b. Control EFW flow to 5. IF NR level in any SG maintain NR level - Entinues to increase in an ,

s BETWEEN 5: AND 50% uncontrolled nanne r, THEN go to E-3, STIAM GENERATOR TUBE RUPTURE, Step 1.

! 29 Check Secondary Radiation - Go to E-3, STEAM GENERATOR l NORMAL USING REMS: TUBE RUPIURE, Step 1.

I e Main steamlines i I i

j - OR -

1 s e Condenser ef fluent l ~

i

, I I

i i

I O

14 of 23

~

l Check VCT Makeup Control Adjust controls as necessary.

1 Sys tein:

a. Makeup set for greater than RCS boron concentration

b. Makeup set for autoinatic ,

control O O O

9 Verify PRZR Level - GREATER Control charging flow to TilAN (x) iliaintain PRZR level . IF PRZR level can NOT be maintained, TilEN manually operate SI pumps ,

as necessary.

O O O

.l l, O

G N

I S

A E

R C

N

.. I l

e v

L e O

. r

. e

. z i

r

. u s

s e

r .

P

(

c e

h C

O

-- m -- m , e - .a O

I N

Q i

C) 3  %

a h C-o M

9 W

l l

l .

O

i Maintain Letdown Flow:

l

a. Open letdown orifice isolation valves as necessary

b. Adjust low pressure letdown control valve setpoint as necessary 9 A O O

f Check If SGs Are Not Faulted:

a. Check pressure in all SGs -

e NO SG PRESSURE DECREASING IN AN UNCONTROLLED MANNER

- OR -

e NO SG llAS COMPLETELY DEPRESSURIZED O O O

God;; 5ymptcmi!1tlo: Procscure tio./

Revision No./Date:

E-2 FAULTED SIEAM GENERATOR ISOLATION CS-1320 Rev. 1 - 7~ 0 -r/ 10/07/83 A. PURPOSE This procedure provides actions to identify and isolate a f aulted steam generator.

3. StiPTOMS OR ENTRY CONDITIONS:

This procedure is entered from:

1) E-0, REACTOR TRIP OR SAFETY INJECTION, Step 22 and E-1, LOSS OF REACTOR OR SECON'DARY CCOLANT, Step 2 with the following .

symptoss:

a. Any SG pressure decreasing in an uncontrolled sanner

b. Any SG completely depressurized

2) E-3, STEAM GENERATOR TUBE RUPTURE, S t ep 6, EC A-3.1, SGTR WITH LOSS OF REACTOR COOLANT - SUBC00 LED RECOVERY DESIRED, Step 3, and ECA-3.2, SGTR WITH LOSS OF REACTOR COOLANT - SATURATED ,

RECOVERY DESIRED, Step 3 when f aulted SG isolation is not

• verified.

3) FR-H.5, RESPONSE TO STEAM GENERATOR LOW LEVEL, Step 3 wnen the af f ected SG is diagnosed as f aulted.

4) Other procedures wnenever a f aulted SG is identified.

m

e Coda: Symptom /Titls: Procsdurs No./

Revision No./Date:

E-2 FAULTED STEAM GENERATOR ISOLATION 05-1320 Rev. 1-T 0 - 7/ 10/07/83

,f ' ,

! STEP l l ACTION / EXPECTED RESPONSE l l RESPONSE NOT OBTAINED l CAUTION e At least one SG must be =aintained available f or RCS f cooldown.

e Any f aulted SG or secondary break should remain isolated during subsequent recovery actions, unless needed for RCS cooldown.

1 Check Main Steamline Isolation Manually close valves.

And Bypass Valves Of Af f ected SG(s) - CLOSED 2 Check If Any SG Is Not Faul t ed:

a. Check pressures in all SGs - a. E all SG pressures de-ANY STABLE OR INCREASING creasing in an uncontrolled manner, TEEN go to ECA-2.1, UNCONTROLLED DEPRESSURIEA-TION OF ALL STEAM GENERATORS,

(- Step 1.

3 Identif y Faulted SG(s):

a. Check pressures in all SGs - a. Search for initiating break:

e ANY SG PRESSURE e Main steamlines DECREASING IN AN e Main feedlines l UNCONTROLLED MANNER e Other secondary piping

- OR - Go to Step 5.

e ANY SG COMPLETELY _

DEPRESSURIEED

Code: Symptoa/

Title:

Procedure No./ l Kevision No./Cate:

E-2 FAULTED STEAM GENERATOR ISOLATION 0S-1320 Rev. 1-T 0-r/ 10/07/83 l STEPi l ACTION / EXPECTED RESPONSE I i RESPONSE NOT OBTAINED l 4 Check Faulted OG(s) Isolated: Manually close valves. IF, valves can NOT be closed, TEEN

a. Main feedline - ISOLATED dispatch operator to locally close valves or block valves,

b. EFW flow - ISOLATED

c. Steam supply to turbine-driven EFW pump - ISOLATED e SG-A MS-V127 e SG-B MS-V128

d. SG ASDVs - CLOSED

e. Main steam drains -

GROUP A CLOSED ,

l

f. SG blowdown - ISOLATED ,

i CAUTION CST sakeup should commence as early as possible to avoid low inventory problems. ,

5 Check CST Level - GREATER Establish =akeup so CST at THAN (K-1) FEET =aximum rate.  ;

i l

l l

l c

l

- m_

s 3 of 4 l

' Coda: Sympto3/

Title:

Procsdure No./

Revision No./Date: 3 l

E-2 FAULTED STEAM GENERATOR ISOLATION 0S-1320 Rev. 1-T 0- 7/ 10/07/83 iSTEPl l ACTION / EXPECTED RISPONSE l l FESr0NSE NOT OBTAINED l 6 Check Secondary Radiation:

a. Request periodic liquid a. IF_ SG blowdown can NOT activity samples of all be reestablished, go to SGs: Step 6b.

1) Reset SI

2) Reset Phase A isolation

3) Reestablish SG blowdown for sanpling only e Locally isolate throttle valves to blowdown cara first, THEN reopen blow-down containment isola-tion valves

b. Check unisolated secondary radiation nonitors using RDMS

- e Main steamline monitors

c. Secondary radiation - NORMAL c. Go to E-3, STEAM GENERATOR TUBE RUPTURE, Step 1.

l 7 Go To E-1, LOSS OF REACTOR OR SECONDARY COOLANT, Step 1 i l \

- ENv -

l

\

i

1} SUBC1I~~ICALITY lS) 2} CORE C00LIhG (C}

3} .F EAT Slh ( i, i }

4) I\TEGRITY I, P }

5} 'CONTAIh4ENT (Z)

6) INVENTORY (I)

O O O

CSF STATUS COLOR-CODING COLOR SIGNIFICANCE GREEN e CSF SATISFIED 4 NO ACTION REQUIRED YELLOW t CSF NOT FULLY SATISFIED I

0 ACTION MAY BE NEEDED l

ORANGE 4 CSF UNDER SEVERE CilALLENGE 8 PROMPT ACTION NEEDED RED 8 CSF IN JEOPARDY 0

IMMEDIATE ACTION REQUIRED O O O A

i STATUS TREE CONSTRUCTION 8 EACil TREE REPRESENTS ONE CSF S EACH BRANCH DEFINES A CSF STATUS WITil A UNIQUE COMBINATION OF CONDITIONS 8 OPERATOR RESPONSE PRIORITIZED BY:

STATUS TREES MONITOR ORDER UNIQUE PATil COLOR UNIQUE PATil INSTRUCTIONS O O O

- t

Guideline Desicnator Acclicacility (M ces./C0mments)

O E-0 1, 2, 3, RHR not in service anc 31 OCeraCle

0. .; n. . O '., ., .t , a,

.r.<

.. s . '. ..

. i...

. .:..== ..

. . ae..

I. .;. . wn . .'.

-e.

.. (na.ar -. ., 3 -u- ) , .4 ,.

a >.

2 u.a moc1 :a:!cn -ecuirec if alreacy ES-0.4 in cooicewn

-l 1, e,  ;, -,R no; 4.n cervice sn l ES-1.1 ES-1.2 RhR 90: in service, entry is l

limitec y statec concitions

. 1, .?, 1, , Ta.mp > ? ~

r 1-r l

a. 1, c,,

a,

. , H., n not in service ES-3.1 ..

ES-3.2 E5-3.3 l

cua.-0.0 ,

i,

, 2

- ractly hot and ECA-0.1 cressurizec l

ECA-0.2 l

ECA-1.1 Scecific entry : rci ions OPOVicec ECA-1.2

cm, .,.1 1,

6, a,

, Rh-k no: in service, het ECA-3.1 1, 2, 3 , 1, RHR not in service

un,

_ _ a . _,

ECA-3.3 66398:1/100483 20

STATUS TREES Succriticality 1-4 Core Cccling 1-4 Hea: Sink 1-4, .ni ess R-R ir se v ce I r.:e g r ' :y 1-4 _ ;r: c :c'e o':n

ccicewn -ate do mece 4 containmen: 3-4 Inventory 1-4 FR-5.1 1-4, ( AFW not recuirec i# cn RHR)

FR-5.2 1-4 FR-C.1 1, 2, 3, Partial .vCCE a on SI en-C.2 equi'cment a v a i ,i ac i i i ty ,

seconcary ,ineuo i

l I

1 FR-C.3 . 1-4 FR-H.1 1-4, 31eed acc #eed may ce ce l

seen for VCCE 4 FR-H.2 1-4 rn-n.a 1-a. except we Iayuc FR-H.4 1-4 FR-H.5 1-4 except dry layuo

-, ,. 1 Ex-2*,

ntry may act 'e c necessary if initial te.mcerature was icw i

l

! FR-P.2 1-4

~

R-Z.1

R-Z.2 1-4 R-Z.3 till>-

66808:1/100483 21

p ..., ,-4,

. Scre exceptions if RHR in service

. Ocssic:e exceotien ca 3;

<-,.42..,,,

l

)

I i

i l

O' I

1 1

O 56e98:1/100433 2,

- ---- --- ___ __^ ^- - - - ' - , , , , _ . _ , _

")EFENSE IN JEPT (tUL~I3LE BARRI E1S) e FUEL VATRIX, FUEL CLAD 4 1EACTOR C00_ ANT SYSTEM 8 CONTAINMENT 4 JISTANCE 9 9 9 1

1 CRITICAL SAFETY

JNCTION l

l -

AN ACTIVITY WHICH ASSURES THE INTEGRITY OF THE PHYSICAL BARRIERS 1

AGAINST RADIATION RELEASE O O 0

I l

CRITICAL SAFETY FUNCTION SELECTION 1

l l

0 COMPLETI SET 9 LI?4ITED bUVBER

$ COMPATIBLE WITH ERG STRUCTURE 4

Pi1 EVENT BASRIER FAILURE O O O

P l

CRITICAL SAFETY FUNCTION SET l

l 8 MAINTENANCE OF SUBCRITICALITY 4 MAINTENANCE OF CORE COOLING S MAINTENANCE '0F A IIEAT SINK e MAINTENANCE OF REACTOR COOLANT SYSTEM INTEGRITY 0 MAINTENANCE OF CONTAINMENT INTEGRITY t CONTROL OF REACTOR COOLANT SYSTEM INVENTORY O O O A

SAFETY FUNCTION RELATIONS TO BARRIERS BARRIERS SAFETY FUNCTIONS S FUEL MATRIX SUBCRITICALITY 8 FUEL CLAD CORE COOLING INVENTORY 8 REACTOR COOLANT HEAT SINK SYSTEM BOUNDARY INTEGRITY INVENTORY 0 CONTAINMENT CONTAINMENT O O O

! VONITORIbG CSF STATUS 8 SYSTEVATIC 8 EXPLICIT 9 DIAGNOSIS 9 RESPONSE 9 O O

CRITICAL SAFE ~~Y FUNCTIONS 8 MONITORING -

STATUS TREES lF-0}

9 VAINTENA\CE -

FUNCTION RESTORATION

~

GUIDELINES (FRGs) i 9

O e

CRITICAL SAFETY FUNCTIONS (STATUS TREES AND FRGs)

ADVANTAGES 8 INDEPENDENT OF INITIATING EVENT S GUIDANCE BEYOND DESIGN BASIS LIMITATIONS 8 GENERALLY NOT ADEQUATE FOR PLANT REC 0VERY 8 SUPPLEMENTED BY EVENT-SPECIFIC RECOVERY GUIDELINES (0RGs)

O O O A

E-0 SERIES E-0 REACTOR TRIP OR SAFETY INJECTION ES-0.0 REDIAGNOSIS ES-0.1 REACTOR TRIP RESPONSE ES-0.2 NATURAL CIRCULATION C00LDOWN ES-0.3 NATURAL CIRCULATION C00LDOWN WITil STEAM VOID IN VESSEL (WITil RVLIS)

ES-0.4 NATURAL CIRCULATION C00LDOWN WITil STEAM V01D IN VESSEL (WITil0UT RVLIS)

O O O

ES-0.0 REDIAGNOSIS t

~

PURPOSE OF PROCEDURE METil0D FOR DETERMINING OR CONFIRMING Tile MOST APPROPRIATE POST ACCIDENT RECOVERY PROCEDURE ENTRY INTO PROCEDURE OPERATOR JUDGEMENT O O O

E-0 REACTOR TRIP OR SAFETY INJECTION PURPOSE OF PROCEDURE 9 VERIFY PROPER AUTOMATIC PROTECTION SYSTEMS RESPONSE FOLLOWING A REACTOR TRIP OR SAFETY INJECTION 8 ASSESS PLANT CONDITIONS 8 IDENTIFY APPROPRIATE RECOVERY PROCEDURE ENTRY INTO PROCEDURE 8 AFTER REACTOR TRIP G AFTER REACTOR TRIP AND SAFETY INJECTION 0 li ie> (' .,4 yyg , j , .)

ES-0.1 REACTOR TRIP RESPONSE PURPOSE OF PROCEDURE INSTRUCTIONS TO STABILIZE AND CONTROL Tile PLANT FOLLOWING A REACTOR TRIP (WITHOUT SI)

ENTRY INTO PROCEDURE AFTER REACTOR TRIP (SI NOT REQUIRED)

O O O

ES-0.2 NATURAL CIRCULATION C00LDOWN PURPOSE OF PROCEDURE e NATURAL CIRCULATION C00LDOWN AND DEPRESSURIZATION TO COLD SiluTDOWN ,

8 NO ACCIDENT IN PROGRESS 8 REQUIREMENTS PRECLUDE ANY UPPER HEAD VOID FORMATION ENTRY INTO PROCEDURE 8 ENTERED FROM ES-0.1, REACTOR TRIP RESPONSE 8 NATURAL CIRCULATION C00LDOWN REQUIRED O O 9

ES-0.3 NATURAL CIRCULATION C00LDOWN WITil STEAM V0ID IN VESSEL (WITil RVLIS) i PURPOSE OF PROCEDURE e CONTINUE PLANT C00LDOWN AND DEPRESSURIZATION TO COLD SiluTDOWN 4 NO ACCIDENT IN PROGRESS e CONDITIONS ALLOW POTENTIAL VOID FORMATION IN VESSEL UPPER llEAD REGION 0 RVLIS AVAILABLE TO MONITOR VOID GROWTil ENTRY INTO PROCEDURE AFTER COMPLETING FIRST ELEVEN STEPS OF ES-0.2, NATURAL CIRCULATION C00LDOWN O O O

ES-0.4 NATURAL CIRCULATION C00LDOWN WITil STEAM VOID IN VESSEL (WITl10UT RVLIS)

\

PURPOSE OF PROCEDURE f

e CONTINUE PLANT C00LDOWN AND DEPRESSURIZATION TO COLD SiluTDOWil -

8 NO ACCIDENT IN PROCESS 4 CONDITIONS ALLOW POTENTIAL VOID FORMATION IN VESSEL UPPER llEAD REGION 4 RVLIS NOT AVAILABLE TO MONITOR VOID GROWTil ENTRY INTO PROCEDURE AFTER COMPLETING FIRST ELEVEN STEPS OF ES-0.2, NATURAL CIRCULATION C00LDOWN O O O

E-0 REACTOR TRIP OR SAFETY INJECTION METliOD OF RECOVERY 0 VERIFY REACTOR AND TURBINE TRIP G VERIFY AC POWER AVAILABLE

, 8 SI ACTUATED OR REQUIRED (ALL SYSTEMS FUNCTIONING PROPERLY) e Sil0ULD MAIN STEAMLINES BE ISOLATED 0 CONTAINMENT SPRAY REQUIRED OR NOT e RCS liEAT REMOVAL SYSTEMS OPERATING PROPERLY e PORVs OPERATING PROPERLY e Sil0ULD RCPs BE STOPPED 0 ACCIDENT DIAGNOSTICS AND TRANSITIONS STEAM LINE BREAK SGTR LOCA (INSIDE OR OUTSIDE CTMT) e TERMINATE SI IF CRITERIA SATISFIED 2 MONITOR CSF STATUS TREES e STOP UNNECESSARY SI EQUIPME A

ES-0.0 REDIAGNOSIS l sipt>m ei r ._ r; t a fi i r, METHOD OF RECOVERY _

O CHECK FOR VULTIPLE STEAV L': 1E BREAKS i 0 CHECK FOR SI\G_E STEAM LINE BREAK t CHECK FOR SGTR 8 SHOULD BE IN LOCA PROCEDURE O O O

ES-0.1 REACTOR TRIP RESPONSE METil0D OF RECOVERY e CHECK FOR RCS llEAT REMOVAL 8 ALL RCCAs ON BOTTOM 8 STABILIZE PRZR LEVEL e STABILIZE PRZR PRESSURE 8 STABILIZE SG LEVELS 4 ADDITIONAL FOLLOW UP ACTIONS ALI. AC BUSES ENERGIZED RCP STATUS SiluTDOWN UNNECESSARY EQUIPMENT MAINTAIN STABLE PLANT CONDITIONS S NATURAL CIRCULATION C00LDOWN REQUIRED O O O

ES-0.2 NATURAL CIRCULATION C00LDOWN METil0D OF RECOVERY 9 ATTEMPT RCP RESTART e SAMPLE BORON AND BORATE AS NECESSARY 8 VERIFY CRDM FANS OPERATING e C00LDOWN RCS TO COLD SiluTDOWN 4 DEPRESSURIZE RCS e BLOCK SI ACTUATION 4 MAINTAIN SUBC00 LING 8 MAINTAIN LETDOWN AND SEAL INJECTION O PLACE RilR IN SERVICE 4 C00LDOWN INACTIVE PORTION OF RCS 9 .

O O

l ES-0.3 NATURAL CIRCULATION C00LDOWN WITil STEAM V0ID IN, VES'SEL

~

(WIT!!RVLIS) -

METil0D OF REC 0VERY 8 ATTEMPT RCP RESTART .

8

~

ESTABLISil AND CONTROL PRZR LEVEL >

s CONTINUE C00LDOWN l 8 INITIATE DEPRESSUEIZATION 8 MAINTAIN RVLIS UPPER RANGE LEVEL 8 LOCK OUT SI SYSTEM IF CRITERIA SATISFIED 8 MAINTAIN LETDOWN AND SEAL FLOW 8 PLACE RilR IN SERVICE IF CRITERIA SATISFIED e C00LDOWN TO COLD SilUTDOWN O O O A

ES-0.4 NATURAL CIRCULATION C00LDOWN WITil STEAM VOID IN VESSEL (WITil0UT RVLIS)

METil0D OF RECOVERY t ATTEMPT RCP RESTART

! O ESTABLISI-I PRZR LEVEL FOR VOID GROWTil 8 COOLDOWN AND DEPRESSURIZE RCS IN STEPS I

EQUALIZE CilARGING AND LETDOWN CllECK PRZR LEVEL LESS TilAN 90%

4 MAINTAIN SEAL INJECTION 4 LOCK 0UT SI SYSTEM WilEN CRITERIA SATISFIED 0 PLACE RilR SYSTEM IN OPERATION e C00LDOWN RCS TO COLD SiluTDOWN e C00LDOWN INACTIVE PORTION OF RCS

~

O 9 9

ECA-0 SERIES ECA-0.0 LOSS OF ALL AC POWER ECA-0.1 LOSS OF ALL AC POWER RECOVERY WI~H S.I. REQUIRED ECA-0.2 LOSS OF ALL AC POWER RECOVERY WITH S.I. REQUIRED O O O A

ECA-0.0 LOSS OF ALL AC POWER PURPOSE OF PROCEDURE ,

RESPOND TO A LOSS OF ALL AC POWER ENTRY INTO PROCEDURE e ALL MAIN AND EMERGENCY BUSSES DEENERGIZED

0 E-0, REACTOR TRIP OR SAFETY INJECTION, STEP 3, ALL AC EMERGENCY BUSSES DEENERGIZED 1

9 .

O O

m ECA-0.1 LOSS OF ALL AC POWER RECOVERY WITHOUT SI REQUIRED PURPOSE OF PROCEDURE STABILIZE PLANT CONDITIONS FOLLOWING RESTORATION AC EMERGENCY POWER WITH NORMAL OPERATIONAL SYSTEMS ENTRY INTO PROCEDURE ENTERED FROM ECA-0.0, LOSS OF ALL AC POWER, STEP 27, WHEN:

AC EMERGENCY POWER RESTORED SI NOT REQUIRED G 9 9 A

ECA-0.2 LOSS OF ALL AC POWER REC 0VERY WITil SI REQUIRED "s'.

PURPOSE OF PROCEDURE TO USE ENGINEERED SAFEGUARDS SYSTEMS FOR PLANT lEC0VERY FOLLOWING RESTORATION AC EMERGENCY POWER l

ENTRY INTO PROCEDURE 4 ENTERED FROM ECA-0.0, LOSS OF ALL AC POWER, STEP 27 WilEN:

AC EMERGENCY POWER RESTORED SI REQUIRED 8 ENTERED FROM ECA-0.1, LOSS OF ALL AC POWER RECOVERY WITil0UT SI REQUIRED, STEPS 5 AND 19 IF:

SI REQUIRED 9 9 9

ECA-0.0 LOSS OF ALL AC POWER i

METil0D OF REC 0VERY e VERIFY REACTOR AND TURBINE TRIP 0 RCS ISOLATED 0 ATTEMPT TO RESTORE AC POWER S LOCALLY ISOLATE RCP SEALS S CllECK SGs STATUS S SilED NON-ESSENTIAL DC LOADS e DEPRESSURIZE INTACT SGs -

0 CllECK SI STATUS S AC EMERGENCY POWER RESTORED 0 SELECT RECOVERY GUIDELINE 9 O O

ECA-0.1 LOSS OF ALL AC POWER REC 0VERY WITHOUT SI REQUIRED METil0D OF REC 0VERY e CilECK RCP SEAL STATUS 9 CllECK CTMT ISOLATION 0 MANUALLY LOAD EQUIPMENT ON AC EMERGENCY BUS e VERIFY SI NOT REQUIRED 0 ESTABLISil NORMAL PLANT SYSTEM OPERATIONS e VERIFY NATURAL CIRCULATION e MAINTAIN STABLE PLANT CONDITIONS S TRY TO RESTORE OFFSITE POWER e DETERMINE IF NATURAL CIRCULATION C00LDOWN REQUIRED 9 A O O

570.22 LOSS OF ALL AC POWER REC 0VERY WITil SI REQUIRED METil0D OF RECOVERY

$ MANUALLY ALIGN SI INJECTION SYSTEM e MANUALLY LOAD SAFEGUARDS EQUIPMENT 4 START CllARGING/SI PUMP IF CRITERIA SATISFIED 4 MAINTAIN INTACT SG LEVELS e ESTABLISil RCP SEAL COOLING

$ GO TO E-1, LOSS OF REACTOR OR SECONDARY COOLANT O O O A

j DAY 2 CLASSROOM e LOSS OF COOLANT ACCIDENT (LOCA)

E-1 SERIES ECA-1 SERIES S INADEQUATE CORE COOLING (ICC)

FR-C.1 FR-il .1 SIMULATOR 8 LOCA DBA WITil SWITCil0VER 0 LOCA SMALL WITil C00LDOWN 8 ICC SMALL LOCA WITil ECCS O O O

l l

l E-1 SERIES E-l LOSS OF REACTOR OR SECONDARY COOLANT ES-1.1 SI TERMINATION ES-1.2 POST LOCA C00LDOWN AND DEPRESSURIZATION ES-1.3 TRANSFER TO COLD LEG RECIRCULATION ES-1.4 TRANSFER T0110T LEG RECIRCULATION O O O L -

E-1 LOSS CF EACTOR OR SECCNDARY C0 CUNT RJPPOSE CF PTCEURE ECOEPY FTO1 LOSS E REACTCR OR SECODRY CCCUNT ENTRY INTO PROCEUPE I PRZR PCW SIUCK CPEVELCCX VAL'E C.WJT EE SHJT E-0, STEP 20 FR-H.1, STEP 24 I HIGH CIMT PADIATICN, PESSUE, RECIROjLATICN $'P LEVEL E-0, SEP 24 0 RCS PESSUE LESS TFAN SHJTCF HEAD CF LtLSI PfPS h Eh? ?

^

l

- ECA-2.1, 5fEP 6 8 RCS PESSUE EECEASES WITH AU EUT CtE CPARGIt&SI RIP STCPED ES-1.1 l 8 FAULIED SG IEENTIFIED #0 ISCLATED E-2, STEP 7 8 NOTAL INJECTIm NCE CCNDITICNS ESTAELISED ECA-0.2, STEP 9 1

0 LOCA CUTSIEE CTMT ISCLATED ECA-1.2, STEP 3 1

0 CCE CCCLIl% RESTAELISED

- FR-C.1,STEDS17AND24 g

FR-C.2, STEP 19

f E-1 LOSS OF REACTOR OR SECONDARY C00LAhff

?~~1Y TO 310CillE (CONT.)

8 SECONDARY HEAT SINK REESTABLISilED MID ALL PRZR PORVs CLOSED FR-1,1, STEP 24 4 SI HAS TO BE REINITIATED FR-I.2, STEP 4 ES-1.1, STEPS H N O 28 O O O

_ .1

ES-1.1 SI TERMINATION PURPOSE OF PROCEDURE e TERMINATE SI O STABILIZE PLANT CONDITIONS ENTRY INTO PROCEDURE SPECIFIED TERMINATION CRITERIA ARE SATISFIED E-0, STEP 26 E-1, STEP 7 O O O A

ES-1.2 POST LOCA C00LDOWN AND DEPRESSURIZATION PURPOSE OF PROCEDURE FOLLOWING LOCA C00LDOWN TO COLD SiluTDOWN CONDITION DEPRESSURIZE RCS ENTRY INTO PROCEDURE _

e RCS PRESSURE GREATER TilAN LilSI PUMP SilUT0FF HEAD E-1, STEP 13 8 RCS PRESSURE LESS TilAN lillSI PUMP SilUT0FF llEAD OR PRZR LEVEL NOT MAINTAINED BY CilARGING ES-1.1, STEP 8 OR 9 O O O

ES-1.3 TRANSFER TO COLD LEG RECIRCULATION l

PURPOSE OF PROCEDURE TRANSFER SI SYSTEM AND CONTAINMENT SPRAY SYSTEM TO RECIRCULATION MODE ENTRY INTO PROCEDURE e LOW RWST LEVEL E-1, STEP 14 ECA-2.1, STEP 8 9 RWST LEVEL REACllES SWITCll0VER SETPOINT MANY OTilER GUIDELINES t

O O O x

ES-1.4 TRANSFER TO HOT LEG RECIRCULATION PURPOSE OF PROCEDURE TRANSFER SAFETY INJECTION SYSTEM TO HOT LEG RECIRCULATION ENTRY INTO PROCEDURE SPECIFIED TIME INTERVAL ELAPSED j

E-1, STEP 18 l

l O O O

. E-1 LOSS OF REACTOR OR SECONDARY COOLANT METil0D OF RECOVERY 0 RCPs STATUS 8 SGs STATUS FAULTED RUPTURED 0 CHECK PRZR PORV/ BLOCK VALVE STATUS S CilECK SI TERMINATION CRITERIA 0 TERMINATE NON-ESSENTIAL SI EQUIPMENT e RCS C00LDOWN AND DEPRESSURIZATION REQUIRED 0 TRANSFER TO COLD LEG RECIRCULATION REQUIRED 0 REACTOR VESSEL llEAD VENT REQUIRED 0 TRANSFER TO Il0T LEG RECIRCULATION 4 EVALUATE LONG TERM PLANT STATUS

~

O O O A

1 ES-1.1 SI lt@INATION METil0D OF RECOVERY 0 RESET SI AND ESTABLISil CTMT AIR 8 STOP ALL BUT ONE CilARGING/SI PUMP 4 RCS PRESSURE STABLE OR INCREASING e ESTABLISil NORMAL CilARGING AND MAINTAIN PRZR LEVEL e Sil0ULD lillSI PUMPS BE STOPPED 4 STOP RilR PUMPS S SI REINITIATION REQUIRED 8 RCS Il0T LEG TEMPERATURE STABLE 4 STABILIZE PRESSURIZER LEVEL 6 STABILIZE PRESSURIZER PRESSURE e STABILIZE SG LEVEL 4 ALL AC BUSES ENERGIZED 4 RCP STATUS S SilUTDOWN . UNNECESSARY EQUIPMENT 4 MAINTAIN STABLE PLANT CONDITIONS I VERIFY SI FLOW NOT REQUIRED

cS-le2 POST LOCA C00LDOW, AND DEPRESSURIZA.1011 METil0D OF RECOVERY 8 RESET SI AND ESTABLISil CTMT AIR 0 AC BUSSES ENERGIZED BY OFFSITE POWER e Sil0ULD LilSI PUMPS BE STOPPED 4 RCS C00LDOWN TO COLD SilUTDOWN 4 RCS ADEQUATELY SUBC00 LED 8 SI IN SERVICE 8 REFILL PRZR (DEPRESSURIZE RCS) 4 RCP STATUS S CRITERIA FOR STOPPING SI FLOW 8 ESTABLISil NORMAL CllARGING AND MAINTAIN PRZR LEVEL 4 MINIMIZE RCS SUBC00 LING (DEPRESSURIZE RCS)

e VERIFY ADEQUATE SDM e SI FLOW REQUIRED e ACCUMULATOR ISOLATION 8 RilR OPERATION 8 EVALUATE LONG TERM PLANT STA S A

ES-1.3 TRANSFER TO COLD LEG RECIRCULATION METil0D OF REC 0VERY l

0 RESET SI e CCW FLOW TO RilR llEAT EXCllANGERS 8 SI SYSTEM ALIGNMENT FOR RECIRCULATION 8 SI SYSTEM PUMP OPERATION 8 CONTAINMENT SPRAY ALIGilMENT FOR RECIRCULATION O O O

ES-1.4 TRANSFER T0 ll0T LEG RECIRCULATION l

METil0D 0F REC 0VERY e LilSI PUMPS ALIGNMENT FOR 110T LEG RECIRCULATION 0 ALIGN lillSI PUMPS ALIGNMENT FOR ll0T LEG RECIRCULATION O O O A

ECA-1 SERIES

~

ECA-1.1 LOSS OF EMERGENCY COOLANT RECIRCULATION ECA-1.2 LOCA OUTSIDE CONTAINMENT O O O A

ECA-1.1 LOSS OF EMERGENCY COOLANT RECIRCULATION PURPOSE OF PROCEDURE e RESTORE EMERGENCY COOLANT RECIRCULATION 4 DELAY RWST DEPLETION ADD MAKEUP REDUCE OUTFLOW 4 DEPRESSURIZE RCS TO MINIMIZE BREAK FLOW ENTRY INTO PROCEDURE e COLD LEG RECIRCULATION NOT VERIFIABLE E-1, STEP 12 4 MINIMUM ONE SUMP FLOW PATil NOT ESTABLISilED OR MAINTAINED ES-1.3, STEP 3 e LOCA OUTSIDE CTMT NOT ISOLABLE ECA-1.2, STEP 3 O O O

ECA-1.2 LOCA OUTSIDE CONTAINMENT PURPOSE OF PROCEDURE 4 IDENTIFY LOCA OUTSIDE CTMT 4 ISOLATE LOCA ENTRY INTO PROCEDURE ABNORMAL RADIATION LEVEL IN AUXILIARY BUILDING E-0, STEP 3.0 O O O

ECA-1.1 LOSS OF EMERGENCY COOLANT RECIRCULATION METil0D OF REC 0VERY 8 RESTORE EMERGENCY COOLANT RECIRCULATION EQUIPMENT 4 ADD MAKEUP TO RWST 4 C00LDOWN RCS TO COLD SilUTDOWN 8 CTMT SPRAY REQUIRED e VERIFY NO BACKFLOW FROM RWST TO SUMP e ESTABLISil MINIMUM SI FLOW (0NE TRAIN) e STOP PUMPS TAKING SUCTION FROM RWST 4 MAKEUP RCS FROM ALTERNATE SOURCES S INJECT AND ISOLATE ACCUMULATORS (DEPRESSURIZE INTACT SGs) 8 STOP RCPs WilEN REQUIRED 4 PLACE RilR SYSTEM IN OPERATION O O O

ECA-1.2 LOCA OUTSIDE CONTAINMENT METil0D OF RECOVERY 4 VERIFY PROPER VALVE ALIGNMENT PATHS TO OUTSIDE CTMT 4 GO TO APPROPRIATE PROCEDURE BASED ON BREAK STATUS i

O O O A

VALIDATIOh .RAlllll1G DAY 3 CLASSR0OM e INTRODUCTION e SECONDARY SYSTEM BREAKS E-2 ECA-2.1 0 FUNCTION RESTORATION GUIDELINES (FRGs)

S-SERIES P-SERIES Z-SERIES I-SERIES SIMULATOR 4 SECONDARY BREAK OUTSIDE CTMT UNIS0LABLE e SECONDARY BREAK INSIDE CTMT MSIVs FAIL TO CLOSE 8 ATWS -

O O O 1

4 i

e ECA-2.1 UNCONTROLLED DEPRESSURIZATION OF ALL STEAM GENERATORS PURPOSE OF PROCEDURE ACTIONS FOR LOSS OF SECONDARY COOLANT AFFECTING ALL SGs 8

ENTRY INTO PROCEDURE UNCONTROLLED DEPRESSURIZATION OF ALL SGs 0CCURS ,

E-2, STEP 2

~

~

O G G A

ECA-2.1 UNCONTROLLED DEPRESSURIZATION OF ALL STEAM GENERATORS METil0D OF REC 0VERY O CilECK SECONDARY PRESSURE BOUNDARY a MINIMIZE RCS C00LDOWN (CONTROLLED FEED FLOW) s Sil0ULD RCPs BE STOPPED e Sil0ULD SI FLOW BE REDUCED e TERMINATE SI AND ESTABLISil NORMAL CilARGING FLOW G VERIFY SI FLOW NOT REQUIRED 4 MAINTAIN PLANT CONDITIONS STABLE e VERIFY AC BUSSES ENERGIZED BY OFFSITE POWER 8 SilUTDOWN UNNECESSARY PLANT EQUIPMENT e C00LDOWN AND DEPRESSURIZE RCS TO RilR SYSTEM CONDITIONS 4 PLACE RilR IN SERVICE e CONTINUE C00LDOWN TO COLD SiluTDOWN e EVALUATE LONG TERM PLANT STATUS O O O

W W 8 MOS a &

S-SERIES FR-S.1 RESPONSE TO NUCLEAR POWER l

GE\ERATION/ATWS FR-S.2 RESPONSE TO LOSS OF CORE SHUTDOWh O _

O O

FR-S.1 RESPONSE TO NUCLEAR POWER GENERATION /ATWS PURPOSE OF PROCEDURE ADD NEGATIVE REACTIVITY TO A CRITICAL CORE (EXPECTED TO BE SHUTDOWN)

ENTRY INTO PROCEDURE 4 TRIP NOT VERIFIED AND MANUAL TRIP NOT EFFECTIVE E-0, STEP 1 8 RED OR ORANGE CONDITION

~

F-0.1 O O O

_ A

FR-S.1 RESPONSE TO NUCLEAR POWER GENERATION /ATWS METil0D OF RECOVERY 8 VERIFY Rx AND TURBINE TRIP s EMERGENCY BORATE e ISOLATE ALL DILUTION PATilS e CllECK FOR UNCONTROLLED CD e MSIVs AND BYPASS VALVES ISOLATED 4 ISOLATE FAULTED SGs a REACTOR SUBCRITICAL 8 RETURN TO GUIDELINE AND STEP IN EFFECT e A e e

4 FR-S.2 RESPONSE TO LOSS OF CORE SHUTDOWN PURPOSE OF PROCEDURE RESTORE CORE TO AN ADEQUATELY SHUTDOWN CONDITION.

ENTRY INTO PROCEDURE EITilER YEL'_0W CONDITION F-0.1 9 .

O O

3-SERIES l

F13 .1 RESP 05SE TO IVVI\ ENT PRESSURIZED THERVAL SFOCK C0\DITIONS l

21-P.2 RESP 0\SE TO ANTICIPATED i

PRESSURIZED THERMAL S10CK C0\DIT".0\S O O O

FR-P.1 RESPONSE TO IMMINENT PRESSURIZED lilERMAL Sit 0CK CONDITION PURPOSE OF PROCEDURE 8 AVOID / LIMIT VESSEL TilERMAL Sil0CK OR PTS

~

S AVOID / LIMIT OVERPRESSURE CONDITIONS AT LOW TEMPERATURE ENTRY INTO PROCEDURE RED OR EITilER ORANGE CONDITION F-0.4 O O O A

, FR-P.1 RESPONSE TO IMMINENT PRESSURIZED TilERMAL SH0CK CONDITION METil0D OF REC 0VERY e TRY TO STOP ANY RCS C00LDOWN 0 Sil0ULD PRZR PORVs BE CLOSED e TERMINATE SI IF CRITERIA MET e VERIFY SI FLOW NOT REQUIRED e ISOLATE ACCUMULATORS e DEPRESSURIZE RCS (DECREASE RCS SUBC00 LING) e SOAK RCS IF REQUIRED e RETURN TO GUIDELINE AND STEP IN EFFECT O O O A

FR-P.2 RESPONSE TO ANTICIPATED PRESSURIZED TilERMAL Sil0CK CONDITIONS PURPOSE OF PROCEDURE 4 RESPOND TO A LIMITED OVERC00 LING EVENT 4 RESPOND TO OVERPRESSURE CONDITION AT LOW TEMPERATURE

! ENTRY INTO PROCEDURE EITilER YELLOW CONDITION F-0.4 O O O

9 FR-P.2 RESPONSE TO ANTICIPATED PRESSURIZED TilERMAL Sil0CK CONDITIONS METil0D OF REC 0VERY 0 TRY TO STOP ANY RCS C00LDOWN 8 SI TERMINATED e DECREASE RCS PRESSURE WITilIN NORMAL P/T LIMITS e ANY ADDITIONAL RCS C00LDOWN RESTRICTIONS REQUIRED 0 RETURN TO GUIDELINE AND STEP IN EFFECT O O O A

\

Z-SERIES l

l l

l FR-Z.1 RESPONSE T0 llIGH CONTAINMENT

. PRESSURE FR-Z.2 RESPONSE TO CONTAINMENT FLOODING FR-Z.3 RESPONSE T0 llIGil CONTAINMENT RADIATION LEVEL .

O O O e

l

FR-Z.1 RESPONSE T0 llIGil CONTAINMENT PRESSURE PURPOSE OF PROCEDURE ACTIONS TO RESPOND TO HIGil CONTAINMENT PRESSURE ENTRY INTO PROCEDURE

~

ltED OR ORANGE CONDITION F-0.5 G G 9 A

9 FR-Z.1 RESPONSE T0 llIGil CONTAINMENT PRESSURE METil0D OF REC 0VERY 8 VERIFY AUTOMATIC ACTIONS CONTAINMENT ISOLATION CONTAINMENT VENTILATION ISOLATION CONTAINMENT SPRAY CONTAINMENT FAN COOLERS RUNNING MSIVs AND BYPASS VALVES CLOSED 8 ISOLATE FW TO ANY FAULTED SG e CilECK llYDR0 GEN CONCENTRATION NOTIFY PLANT STAFF PERIODICALLY OBTAIN MEASUREMENT TURN ON llYDR0 GEN RECOMBINERS 8 RETURN TO GUIDELINE AND STEP IN EFFECT O O O

FR-Z.2 RESPONSE TO CONTAINMENT FLOODING PURPOSE OF PROCEDURE RESPOND TO CONTAINMENT FLOODING ENTRY INTO PROCEDURE AN ORANGE CONDITION F-0.5 O O O A _ _ _ _ _ _

FR-Z.2 RESPONSE TO CONTAINMENT FLOODING 4

METl!0D OF RECOVERY 8 TRY TO IDENTIFY SOURCE OF WATER e CHECK SUMP ACTIVITY LEVEL e NOTIFY PLANT STAFF e RETURN TO GUIDELINE AND STEP IN EFFECT O O O

l l

FR-Z.3 RESPONSE T0 llIGli CONTAINMENT RADIATION LEVEL PURPOSE OF PROCEDURE RESPOND T0 llIGli CONTAINMENT RADIATION LEVEL ENTRY INTO PROCEDURE A YELLOW CONDITION F-0.5 -

O O O

FR-Z.3 RESPONSE TO IIIGli CONTAINMENT RADIATION LEVEL METl!0D OF REC 0VERY t VERIFY CTMT VENTILATION ISOLATION 0 Sil0ULD CTMT FILTRATION SYSTEM BE PLACED IN SERVICE e NOTIFY PLANT ENGINEERING STAFF G RETURN TO GUIDELINE AND STEP IN EFFECT O O O 1

l I-SERIES FR-I.1 RESPONSE T0 llIGil PRESSURIZER LEVEL FR-I.2 RESPONSE TO LOW PRESSURIZER LEVEL FR-I.3 RESPONSE TO VOIDS IN REACTOR VESSEL O O O

FR-I.1 RESPONSE T0 llIGil PRESSURIZER LEVEL PURPOSE OF PROCEDURE RESPOND T0 llIGli PRESSURIZER LEVEL ENTRY INTO PROCEDURE A YELLOW CONDITION F-0.6' O O O L

FR-I.1 RESPONSE T0 llIGli PRESSURIZER LEVEL METil0D OF REC 0VERY e SI BEEN TERMINATED 8 ESTABLISil CilARGING AND LETDOWN 0 REDUCE RCS PRESSURE TO NORMAL 8 ESTABLISil PRESSURE CONTROL e MAINTAIN STABLE RCS PRESSURE WITil CilARGING/ LETDOWN 8 CilECK PRZR' LEVEL 8 RETURN TO GUIDELINE AND STEP IN EFFECT l

l l

l O O O A

FR-I.2 RESPONSE TO LOW PRESSURIZER l_EVEL PURPOSE OF PROCEDURE RESPOND TO LOW PRESSURIZER LEVEL ENTRY INTO PROCEDURE A YELLOW CONDITION F-0.6 O O O

FR-I.2 RESPONSE TO LOW PRESSURIZER LEVEL METil0D OF RECOVERY i

8 SI BEEN TERMINATED e LETDOWN ISOLATED AND CilARGING ESTABLISilED 4 RESTORE PRZR LEVEL (CilARGING FLOW) 8 MONITOR PRZR LEVEL 8 ENERGIZE PRESSURIZER llEATERS AS NECESSARY 8 RETURN TO GUIDELINE AND STEP IN EFFECT O O O A _.

FR-I.3 RESPONSE TO VOIDS IN REACTOR VESSEL PURPOSE OF PROCEDURE RESPOND TO VdIDS IN REACTOR VESSEL ENTRY INTO PROCEDURE A YELLOW CONDITION F-0.6 O O O A

FR-I.3 RESPONSE TO VOIDS IN REACTOR VESSEL METil0D OF REC 0VERY 8 SI BEEN TERMINATED e CllARGING AND LETDOWN ESTABLISilED 8 ESTABLISil STABLE RCS CONDITIONS S RCPs STOPPED 8 TRY TO COLLAPSE STEAM BUBBLE INCREASE RCS PRESSURE IF NECESSARY MAINTAIN PRZR LEVEL AB0VE IlEATERS (CilARGING/ LETDOWN)

CllECK RVLIS START RCP G OBTAIN CTMT llYDR0 GEN MEASUREMENT e BLOCK LOW PRZR PRESSURE SI e ESTABLISil STABLE RCS CONDITIONS 0 PREPARE CTMT AND VENT REACTOR VESSEL e MONITOR REACTOR VESSEL AND PRESSURIZER LEVEL e RETURN TO GUIDELINE AND STEP IN EFFECT O

A

~

G e

ERG REV. 4 VALIDATION TRAINING DAY 4 CLASSROOM 4 E-3 SERIES 4 ECA-3 SERIES SIMULATOR 8 SGTR SMALL C00LDOWN WITil STEAM DUMP METil0b e SGTR DBA C00LDOWN WITil BACKFILL 4 SGTR MULTIPLE ACCIDENT WITil ST 1 BREAK IN RUPTURED SG

l E-3 STEM CEEPATOR TUEE RUPTUE PURPOSE CF PRIEME TEFMINATE LEAFAGE FRm RCS TO SECCfDRY SYSTEM FCL!.DdING A TIEE RJPTUE ENTRY INTO PCCER!E 8 C0f0ENSER AIR EJECTCR CR SG BLCWDCW1 PADIATICN AD0f6L E-0, STEP 23 I SECCfBRY PADIATICN ABCFAL E-0, STEP 29 E-1, STEP 4 E-2, STEP 6 FR-H.3, STEP 7 8 UNCCNTRO i rn NR L9EL ITCPEASE IN ANY INTACT SG E-0, STEP 28 E-1, STEP 3 ES-1,2, STEP 7 ES-3.1, STEP 4 ES-3.2, STEP.4 ES-3.3, STEP 4 ECA-3.1, STEP 9 ECA-3.2, STEP 4 -

l -

ECA-3.3, STEP 5 l 8 PRZR PESSURE CCNTROL ESTCED l -

ECA-3.3, STEPS 2, 3 AND 4 0

E-3 STEM GENEPATCR TUEE RUPTUE i

ETKD & RECOWRY l SHOULD RCPs EE STOFED 4 IEelTIFY RUPTUED SG(s) 8 ISCLATE FUPTUED SG I PRZR PCWs AND ELCCX VAL'<ES PRCfE;LY REITICED 8 ANYSGsFAULTED 8 ESET SI AND ESTAELISH CIMF AIR S ALL AC EUSSES PCWEED FRG GFSITE t SECUE LHSI RIPS IF NOT NEEED g

O CECK RUPTURED SG(s) PRESSUE 8 CC0LDChN RCS AT MAXIPU1 PATE I RJFTUED SG PESSUE STAEE CR INCREASING '

8 RCS SUECCOLING AEETATE 8 IPESSURIZE RCS 8 SI TERMINATICN CRITERIA ET I GAEING/LEIDCWN ESTAELISHED 8 SI FLOW REWIRED 8 MINIMIZE RCS-lJ-SECONDARY EaYAE I SHJTDCWN UNNECESSARY PLWT EWIPEIT 8 GO TO AFFPCPRIATE POST-SGTR COOLIG<N EIKD O

~

ES-3.1 POST-SGTR C00LDOWN USING BACKFILL PURPOSE OF PROCEDURE e FOLLOWING AN SGTR C00LDOWN PLANT TO COLD SiluTDOWN CONDITIONS DEPRESSURIZETilEPLANk 8 DEPRESSURIZE RUPTURED SG BY.8ACKFILL FROM RUPTURED SG TO RCS ENTRY INTO PROCEDURE e PLANT STAFF SELECTS BACKFILL METHOD E-3, STEP 38 0 BLOWDOWN NOT AVAILABLE AND PLANT STAFF SELECTS BACKFIl_L METHOD ES-3.2, STEP 9 O O O k

ES-3.1 POST-SGTR C00LDOWN USING BACKFILL METil0D OF RECOVERY

$ REGAIN PRZR PRESSURE CONTROL 8 ISOLATE ACCUMULATORS IF NOT NEEDED 0 RCS SDM ADEQUATE 8 INTACT SG LEVELS IN NR e C00LDOWN RCS TO COLD SiluTDOWN 8 DEPRESSURIZE RCS TO BACKFILL FROM RUPTURED SG G PLACE RilR SYSTEM IN SERVICE e STOP RCPs WilEN REQUIRED 0 EVALUATE LONG TERM PLANT STATUS O O O

ES-3.2 POST-SGTR C00LDOWN USING BLOWDOWN PURPOSE OF PROCEDURE _

8 FOLLOWING AN SGTR C00LDOWN PLANT TO COLD SiluTDOWN CONDITIONS DEPPRESSURIZE Tile PLANT e DEPRESSURIZE RUPTURED SG BY DRAINING WITil BLOWDOWN ENTRY INTO PROCEDURE PLANT STAFF SELECTS BLOWDOWN METHOD E-3, STEP 38 9 9 9 A

ES-3.2 POST SGTR C00LDOWN USING BLOWDOWN METil0D OF RECOVERY t REGAIN PRZR PRESSURE CONTROL 4 ISOLATE ACCUMULATORS IF NOT NEEDED 4 RCS SDM ADEQUATE e INTACT SG LEVELS IN NR 8 INITIATE RCS C00LDOWN 4 MINIMIZE RCS-TO-SECONDARY LEAKAGE (RCS PRESSURE AND MAKEUP CONTROL) e ESTABLISil RUPTURED SG BLOWDOWN 4 DEPRESSURIZE RCS (MINIMIZE RCS-TO-SECONDARY LEAKAGE) s STOP RCPs WilEN REQUIRED 4 PLACE RilR SYSTEM IN SERVICE l 4 CONTINUE RCS C00LDOWN TO COLD SilUTDOWN 8 EVALUATE LONG TERM PLANT STATUS l

O O O

i ES-3.3 POST-SGTR C00LD0WN USING STEAM DUMP PURPOSE OF PROCEDURE 8 FOLLOWING AN SGTR C00LDOWN PLANT TO COLD SiluTDOWN CONDITIONS DEPRESSURIZE Tile PLANT

. 8 DEPRESSURIZE RUPTURED SG BY DUMPING STEAM l

ENTRY INTO PROCEDURE 8 PLANT STAFF SELECTS STEAM DUMP METil0D E-3, STEP 38 4 BLOWDOWN NOT AVAILABLE AND PLANT STAFF SELECTS STEAM DUMP METil0D i

ES-3.2, STEP 9 9 O O

ES-3.3 POST-SGTR C00LDOWN USING STEAM DUMP METil0D OF REC 0VERY t REGAIN PRZR PRESSURE CONTROL e ISOLATE ACCUMULATORS IF NOT NEEDED 0 RCS SDM ADEQUATE 4 INTACT SG LEVELS IN NR S INITIATE RCS C00LDOWN 0 MINIMIZE RCS-TO-SECONDARY LEAKAGE (RCS PRESSURE AND MAKEUP CONTROL) e DUMP STEAM FROM RUPTURED SG e DEPRESSURIZE RCS (MINIMIZE RCS-TO-SECONDARY LEAKAGE) e STOP RCPs WilEN REQUIRED 4 PLACE RilR SYSTEM IN SERVICE e CONTINUE RCS C00LDOWN TO COLD SilUTDOWN 4 EVALUATE LONG TERM PLANT STATUS O O O h

ECA-3 SERIES ECA-3.1 SGTR WITH LOSS OF REACTOR C00LAhT-SUBC00 LED RECOVERY DESIRED ECA-3.2 SGTR WITF LOSS OF REACTOR COOLA\T-SATURATE) RECOVERY DESIRED ECA-3.3 SGTR W::T-0UT PRESSUR..ZE1 3RESSU1E CO,5T10L e .

G G

1 l

l ECA-3.1 SGTR WITH LOSS CF REACTOR CCCLANT: SUBCCCLED ECONERY EESIED h RJRf0SE CF PfECEMPE 8 C0Ct.DChN RCS TO COLD SHJTILil CCNDITICNS 8 CEFESSURIE RCS 8 MINIMIZE LOSS CF RCS IthEECRY 8 MINIMIZE WIDIllG IN RCS ENTRY INTO PRCCEEURE I RUPTUED SG C#i10T BE ISCLATED FRCM N1Y IIRACT SG

- E-3, STEP 3 8 PRZR PCRV C#f0T EE ISCLATED BY ELCC< VALVE

- E-3, STEP 5 I RUPTUED SG PRESSURE < LrW STERINE PESSURE SI SEiF01hT O

E-3, STEP 13 9 NO INTACT SG AVAILAELE FOR RCS CCCLEChN E-3, STEP 14 0 RUPTUED SG PESSJRE EECEASES FCLLCWING CTLT,vN l -

E-3, STEP 15 i

I RCS SUEC00 LING LESS TF#1 EQUIRED E-3, STEP 16 -

l 8 RCS PESSURE DCES NOT ItCEASE AFTER CLOSItE PRZR PCR/

AND ELCC< VAL'E E-3, STEP 19 1

0 SI CANNOT EE TERilt!ATED E-3, STEP 20 g

- ECA-3.3, STEP 7

ECA-3,1 SGTR WITH LOSS CF REACTOR CCCL3hT: SLEC00L8 EC06 EESIF8 g

EN Iffic PCCEURE (CCNT,)

I SI ACCLMJLATORS CANNOT BE ISOLATE ES-3,1, STEP 2 .

ES-3,2, STEP 2 ES-3,3, STEP 2 I NON-RJPTURED SG NOT AVAILAEE FOR RCS CCCLIDN ES-3,1, STEP 5 ES-3,2, STEPS 5 AND 14 ES-3,3, STEPS 5 ATO 14 I SI FLOW E0JIFE ECA-3,3, SlEP 11 8 RCS PESSUE < MAXIM 31 TECH SEC SI ACCLMjlATOR NITRCG21 FCESSUE ECA-3,3, STEP 22 l

l 9

l I

I ECA-3.1 SGTR WITH LOSS CF EACTOR C00L41T: SUECTLED ECOVERY ESIF8 PER0D CF ECOWRY 0 ESET SI AfD ESTAELISH CTMT AIR 8 SECUE CTMT SPPAY #0 LHSI RJPS IF t0T tE8 8 E/ALUATE RMT STATUS I E/ALUATE SG STATUS 8 C00LThN RCS TO CCLD SHlfi'D0hN 4 SUEC00 LED E0hERY APPFCPRIATE 4 CEFESSURIZE RCS TO PEFILL PRZR I START RCP IF POSSIBLE 9 SECUE UNfECESS,3Y ECCS RIPS

! O ESTABLISH t0FFAL CHARGItE #0 PAltlTAIN PP2R LO/EL j 8 MINIMIZE RCS SUBCCOLIfE GEPESSURIZE RCS) l i SauCenit 8 SI FLCW E0JIED 8 ISOLATEAC01ULATORS I CECK RJPTUED SG LEEL IN NR 8 PLAE RHR IN SERVICE I 8 D/AUJATE LCNG TERi PLMIT STATUS O

ECA-3.2 SGTR WITil LOSS OF REACTOR COOLANT: SATURATED REC 0VERY DESIRED PURPOSE OF PROCEDURE e C00LDOWN RCS TO COLD SiluTDOWN CONDITIONS e DEPRESSURIZE RCS e MINIMIZE LOSS OF RCS INVENTORY ENTRY INTO PROCEDURE 4 RWST LEVEL LOW WIT 110UT CTMT SUMP LEVEL INCREASE .

ECA-3.1, STEP 12 1

0 RUPTURED SG LEVEL llIGli AND PLANT STAFF SELECTS SATURATED RECOVERY METHOD ECA-3.1, STEP 12 0 O O

ECA-3.2 SGTR WITil LOSS OF REACTOR COOLANT: SATURATED REC 0VERY DESIRED METil0D OF RECOVERY 0 STOP LHSI PUMPS IF CRITERIA MET 8 CllECK SG STATUS e INITIATE RCS C00LDOWN TO COLD SiluTDOWN 9 CilECK RCS SUBC00 LING AND SI IN SERVICE e DEPRESSURIZE RCS (REFILL PRZR) s CllECK IF RCP CAN BE STARTED 4 CilECK CRITERIA FOR STOPPING SI FLOW 9 ESTABLISil CilARGING FLOW 8 DEPRESSURIZE RCS TO SATURATION 0 VERIFY ADEQUATE SDM t SI FLOW REQUIRED-0 ISOLATE ACCUMULATORS IF CRITERIA MET 4 CilECK RUPTURED SG LEVEL IN NR 0 PLACE RilR IN SERVICE IF CRITERIA MET EVALUATE LONG TERM PLANT STAT

VALIDATION TRAINING PROGRAM DAY 5 CLASSROOM 8 FRG3 Il-SERIES 1

l -

C-SERIES e EXAMINATION 4 FINAL PROCEDURE CllECK SIMULATOR 4 LOSS OF ALL FEEDWATER 0FFSITE POWER LOST 4 SURPRISE TRANSIENT O O O

H-SERIES FRGs FR-H.1 RESPONSE TO LOSS OF SECONDARY llEAT SINK FR-H.2 RESPONSE TO STEAM GENERATOR OVERPRESSURE FR-H.3 RESPONSE TO STEAM GENERATOR llIGil LEVEL FR-H.4 RESPONSE TO LOSS OF NORMAL STEAM RELEASE CAPABILITIES l FR-H.5 RESPONSE TO STEAM GENERATOR l LOW LEVEL 9 O O A

-* w.m.

FR-il.1 RESPONSE TO LOSS OF SECONDARY HEAT SINK PURPOSE OF PROCEDURE RESPOND TO LOSS OF SECONDARY llEAT SINK IN ALL SGs ENTRY INTO PROCEDURE 1

8 MINIMUM AFW FLOW NOT VERIFIED E-0, STEP 16 0 RED CONDITION F-0.3 O O O

FR-H.1 RESPONSE TO LOSS OF SECONDARY HEAT SINK METHOD OF RECOVERY e SECONDARY llEAT SINK REQUIRED e TRY TO ESTABLISH AFW FLOW G STOP ALL RCPs e TRY TO ESTABLISit MAIN FW FLOW OR OTHER FLOW 4 IIAS SECONDARY llEAT SINK BEEN LOST e ACTUATE SI 4 ESTABLISH BLEED AND FEED e ATTEMPT TO ESTABLISil SECONDARY llEAT SINK 4 CllECK RCS TEMPERATURE DECREASING e SECURE UNNECESSARY SI EQUIPMENT e ESTABLISil CHARGING e TERMINATE.SI x

9 9 e

FR-H.2 RESPONSE TO STEAM GENERATOR OVERPRESSURE PURPOSE OF PROCEDURE ACTIONS FOR SG OVERPRESSURIZATION SG PRESSURE > HIGHEST RELIEF VALVE SETPOINT l .

l ENTRY INTO PROCEDURE YELLOW CONDITION F-0.3 O O O

g _

g FR-il . 2 RESPONSE TO STEAM GENERATOR OVERPRESSURE METil0D OF REC 0VERY 8 IDENTIFY AFFECTED SG(s) WITil OVERPRESSURE e MITIGATE OVERPRESSURE CONDITION IN AFFECTED SG(s)

ISOLATE FW CllECK SG(s) LEVEL DUMP STEAM (USE ANY AVAILABLE METil0D)

~

ISOLATE AFW C00LDOWN IF RCS TEMPERATURE T00 IIIGil e RETURN TO GUIDELINE AND STEP IN EFFECT O -

O O A

9 FR-il . 3 RESPONSE TO STEAM GENERATOR llIGil LEVEL PURPOSE OF PROCEDURE 8 RESPOND TO A SG HIGil LEVEL 8 ADDRESS SG OVERFILL ENTRY INTO PROCEDURE 4 YELLOW CONDITION F-0.3 8 AFFECTED SG NARROW RANGE LEVEL llIGil FR-il.2, STEP 3 i

O O O

FR-il . 3 RESPONSE TO STEAM GENERAiOR llIGli LEVEL METil0D OF RECOVERY 8 IDENTIFY AFFECTED SG(s) e MITIGATE AFFECTED SG llIGil LEVEL ISOLATE FW ISOLATE AFW CLOSE STEAM SUPPLY TO TURBINE DRIVEN AFW PUMP CLOSE MSIVs AND BYPASS VALVES 8 RETURN TO PROCEDURE AND STEP IN EFFECT-O O O

FR-H.4 RESPONSE TO LOSS OF NORMAL STEAM RELEASE CAPABILITIES

• PURPOSE OF PROCEDURE e RESPOND TO FAILURE SG PORVs CONDENSER DUMP VALVES ENTRY INTO PROCEDURE A YELLOW CONDITION F-0.3 e 1 e 6

FR-il . 4 RESPONSE TO LOSS OF NORMAL STEAM RELEASE CAPABILITIES METil0D OF REC 0VERY

~

8 TRY TO RESTORE SG PORVs OR CONDENSER STEAM DUMP 0 REDUCE SG PRESSURE < LOWEST SAFETY VALVE SETPOINT e RETURN TO GUIDELINE AND STEP IN EFFECT e .

9 6.

FR-H.S RESPONSE TO STEAM GENERATOR LOW LEVEL PURPOSE OF PROCEDURE 4 RESPOND TO A SG LOW LEVEL ENTRY INTO PROCEDURE A YELLOW CONDITION F-0.3 O

e e

FR-il . 5 RESPONSE TO STEAM GENERATOR LOW LEVEL METil0D OF RECOVERY

$ IDENTIFY AFFECTED SG(s) 8 MITIGATE AFFECTED SG(s) LOW LEVEL BLOWDOWN ISOLATED AFFECTED SG(s) NOT FAULTED SUFFICIENT AFW FLOW 8 CONTINUE TO FILL AFFECTED SG(s) e RETURN TO GUIDELINE AND STEP IN EFFECT 9

A 9 4

C-SERIES FRGs FR-C.1 RESPONSE TO INADEQUATE CORE C00_ING FR-C.2 RESPONSE TO DEGRADED COE C00LIhG FR-C.3 RESP 0 HSE TO SATURATED CORE C0\DITIOFS O

O e -

FR-C.1 RESPONSE TO INADEQUATE CORE COOLING l

PURPOSE OF PROCEDURE.

RESTORE CORE COOLING ENTRY INTO PROCEDURE EITHER RED CONDITION F-0.2 l

l l

9 A

9 4

FR-C.1 RESPONSE TO INADEQUATE CORE COOLING METHOD OF RECOVERY

$ SI FLOW IN ALL TRAINS 4 ACCUMULATORS OPERABLE e STATUS CORE COOLING

~

e CHECK CTMT HYDR 0 GEN CONCENTRATION 8 DEPRESSURIZE ALL INTACT SGs e ISOLATE SI ACCUMULATORS AFTER INJECTION 8 STOP ALL RCPs e VERIFY SI FLOW ND U, E N CONTINUE TO DEPRESSURIZE INTACT SGs ADEQUATE THEN GO TO E-1 e .

e e

FR-C.2 RESPONSE TO DEGRADED CORE COOLING PURPOSE OF PROCEDURE e RESTORE ADEQUATE CORE COOLING ENTRY INTO PROCEDURE EITilER ORANGE CONDITION -

F-0.2 O

e O

FR-C.2 RESPONSE TO DEGRADED CORE C00LIflG METil0D OF i. c.0VERY 8 VERIFY SI FLOW IN ALL TRAINS .

8 RCS VENT PATilS CLOSED 8 CHECK CORE COOLING e DEPRESSultIZE ALL INTACT SGs e ISOLATE SI ACCUMULATORS AFTER INJECTION 4 STOP ALL RCPs e VERIFY SI FLOW 4 CilECK CORE COOLING STATUS INADEQUATE TilEN CONTINUE TO DEPRESSURIZE INTACT SGs ADEQUATE THEN GO TO E-1 6 ,

O O

f FR-C.3 RESPONSE TO SATURATED CORE COOLING CONDITION PURPOSE OF PROCEDURE

! RESTORE ADEQUATE CORE COOLING l

l ENTRY INTO PROCEDURE EITilER YELLOW CONDITION F-0.2 6 .

O O

FR-C.3 RESPONSE TO SATURATED CORE COOLING CONDITION METil0D OF REC 0VERY 8 RilR SYSTEM llAS NOT BEEN PLACED IN SERVICE e VERIFY SI FLOW ALL TRAINS i

e RCS VENT PATilS CLOSED 8 RETURN TO PROCEDURE AND STEP IN EFFECT 6 A 0 0

4 ERG REV 1 VALIDATION TRAINING CCI'!:ENTS

/

k.

The ERG REV 1 validation testing at Seabrook, New Hampshire proved to be very successful. Much of the test week success can be attributed to the extensive planning phase. Included within the planning phase was a formalized five day training ~ course involving both classroom and simulator instruction. Despite the shortness of the course, basically all training objectives were achieved.

The operators from both teams used the procedures with very favorable results during the test week.

The training program was not void of problems. Some of the difficulties encountered are listed as follows:

1. Sufficient time was nct availabic to provide the operators with in-depth background information on procedure steps.

2. Procedures were discussed in too much detail at the beginning of the

[ course. As a result, procedure discussions later in the course had to be rushed in order to complete the course.

f

3. Course structure had to be altered to enhance operator familiarity with both procedures and equipment locations on tr.e control boards.

Basically, each course day included procedure discussions, procedure

" walk-throughs" on the simulator, and control room operations during accident conditions.

4. The materials developed for the course were quite limited. tiore support materials such as transparencies, background inforntion and student handouts would have enhanced the course.

l l

l d-0592e:1D/121383 L

i 2

The following reccomendations are suggested to improve the one week (five day) m

-Validation Training Course:

[O T

1. -Better course materials need to be developed to support both the instructors and the students. These materials should include more extensive lesson plans, transparencies or slides, background information to support the lesson plans and transparencies / slides,

' student handouts.,.and sufficient simulator scenarios.

2. The operator " walk-throughs" on the control boards with the procedures appeared to be extremely helpful. The operators could follow procedure steps on the control boards and identify pertinent switch locations and indications. This method of training reinforces classroom discussion of the precedures and allows more efficient use of the simulator for accident scenerios.

3. In a five day course, it is not possible to discuss procedurc step s background information in any detail and finish the course on time. A -

discussion involving high level action summaries from the background documents could provide the operator with sufficient information to understand the intent of each procedure. The transition flow charts could show how each procedure interrelates with the entire network of procedures.

i

! ~4. A dynamic set of simulator scenarios that fully exercise all the

( procedures discussed in.a day provides the operators with " hands on" control room and procedures experience. These scererios should also l contain events that recuire the use of procedures discussed during previous days.

In review of the recommendations, the five day course should be set up with i three daily phases. Phase I should consist of classroom presentations on

( procedures with emphasis on high level action summaries and transition flow

! charts. Phase II should consist of " walk-throughs" on a simulator or mockup

/m $ to allow the operator to become familiar with the control board /proccdure 1

1 0592e:10/121383

(

o Week 3: Consists of both classroom and simulator time. Important um procedure analyses and generic issues would be presented in the classroom. The operators should fully exercise the procedures with extensive accident scenarios. Each scenerio would contain multiple accidents and equipment failures. At the conclusion of the three weeks, the operators should be very confident and competent in using the ERGS (EOPs). The operators' knowledge of the procedures and background information should be sufficient to pass an extensive examination.

The recommended minimum background for training personnel and operations personnel involved with the three week training program is defined as follows:

o Operations Personnel R0/SRO licensed or s -

RO/SRO certified or

(

- experienced in the use of pre-ERG E0Ps o Training Personnel

- R0/SRO licensed (may also be R0/SR0 certified instructor)

- experienced in the use of pre-ERG E0Ps i

extensive knowledge of ERG (ECPs) background information (minimum l of two weeks self study or presentations) l

- familiar with three week training package l

- at least one week of simulator experience using the ERGS (EOPs) 0 0592e:10/121383 L

o. interface. Phase III should consist of extensive accident scenarios run on a

) simulator. Upon conclusion of the five day course, the operators should fully understand how to properly use each procedure during major accidents in the control room.

Many questions have arisen concerning the optimal training program for the ERGS (EOPs). The ERG REV 1 validation has shown that the guide 11nes meet all expectations of their usefulness in accident situations. However, with impicmentation of the new procedures, experienced cperators may tend to resist major changes. They are familiar with their present procedures and any major changes may be a source of confusion in a major accident situation. There-fore, these operators must be " sold" on all the attributes of the ERGS (EOPs) in order for them to willingly accept them. With these ideas in mind, a three week training program (15 days) is proposed. This program could provide all the information necessary for the operator to properly use and understand the procedures. It is recognized that many plants cannot free operators for a consecutive three week period. However, it is recommended that all operators receive at least a one week (5 day) training program similar to the ERG REV 1 V validation training program before the ERGS (EOPs) are implemented for plant f use. Important sections of the three week training program could be

~

l implemented in operator retraining programs to enhance operator knowledge of the ERGS (ECPs). .

The reccmmended three week program is discussed by week as follows:

o Week 1: Basically the same as the ERG REV 1 validation training with all recommended improvements. Trie operator should gain a good overall understanding of how to properly ust the procedures in an accident environment. Week l should prepare the operator for an extensive

~

study of ERG (EOPs) background information during the next two weeks.

o Week 2: Consists only of classroom presentations on procedure back-

. ground information. Procedure logic diagrams could be used to enhance the presentations. At the conclusion of this week, the operator should basically understand the reasons bet.ind each procedure step.

V 0592e:1D/121383' L

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

An extersive knowledge.cf ERGS (EOPs) is crucial in order for operators to effectively handle accident st.ations. It is logical in new operator trair.ing to present as much information as possible concerning the ERGS.

Therefore, theoretical information affecting the ERGS should be presented

, during the theoretical phase of new operator training. Emphasis should be placed on systems affected by the ERGS during system training. The three week ERG training program should be fully integrated in the operations training phase so that the newly licensed operator is prepared to correctly use the ERGS (EOPs).

Training is a critical part of ERG (EOP) implementation for a plant. Proce-dure writers, operators, training personnel, and operations management all need some type of ERG (EOP) training in order to optimize the effectiveness of plant E0Ps. Generic training programs such as SGTR and PTS provide a good example of how effective training programs can be developed.

O l

L l

\/

0592e:1D/121383 t

CODE: SYMPTOM / TITLE: PROCEDURE NO.

REVISION NO. / DATE:

I k'E 1-T ..SUBCRITICALITY STATUS TREE os-1350.1 00/10/2/83

^

GOT g FR S.1 l

l EEEEE R S.

NO

• NEUTRON FLUX B l LESS THAN 5% E GOTO i YES as

• • FR-S.2 )

(RTP) e g

e l E I INTERMEDIATE NO RANGE SUR l INTERMEDIATE NO l MORE -

RANGE SUR NEGATIVE l

{ ) .

ZERO OR YES THAN -0.2 DPM NEGATIVE YES ,

CSF ,

' SAT l

- NO SOURCE RANGE ENERGlZED i YES GO TO

1. 8 . CR S.2 .

9 8 .

1 NO SOURCE RANGE i

SUR ZER0 0R NEGATIVE YES l

l CSF

' 1 SAT

.~ e c . . .

F-0,2 ""8' " " d ^*

R EV.1-T CORE COOLING STATUS TREE OS-1350.2 00/!O/2/83 I

GOTO h FR C.1 FR-C.

• +

.) CORE EXIT NO l TCs LESS gy(g3 THAN12000F GREATER YES THAN 40 0/o YES NO "

CORE EXIT -

GO TO TCs LESS FR-C.2 THAN7000F GO TO

.2 NO em l

h AT LEAST ONERCP NO I l RUNNING RVLIS YES l GREATER THAN 40 0/o YES RCS GO TO SUSC00 LING NO FR-C.3-DASED ON CORE EXIT TCs GREATER THAN

' Q?R";

e _

RVLIS DYNAMIC HEAD NO GREATER THAN 44 Ob-4 RCP 30 0'a-3 RCP' YES 20 d'o-2 RCP 13 To-1 RCP FR C.

4

' CSF ,

l SAT

- == ._

vuut. . SYMPTOM / TITLE: I PROCEDURE NO.

REVISION NO./. DATE:

F-0.3 H EAT SIN K STATUS TREE os-1350.3 REV.1 -T 00/10/2/83

!R-TOTAL NO FEEDWATER

_ FLOW TO SGs GREATER

. . GPM c7 g . . . . . . .. . .@ pg;;

NARROW NO NO RANGE PRESSURE IN

. LEVELIN AT ALL SGs LESS LEAST ONE SG THAN OREATER THAN YES 1255 PSIG YES 280/o

....... 3 :::

NARROW NO RANGE LEVEL IN ALL 1 SGs LESS THAN l YES 84.5 0/o

~

. . . . . . @ ??J NO PRESSURE IN

(.

s_ ALL SGs LESS THAN 1185 PSIG YES

.: . . ...} l23 NARROW NO r RANGE LEVELIN ALL SGs GREATER THAN YES 28 oo l l

"l CSF SAT

..... wimiumi iei%. .

PMOCEDURE NO.

, REVISION NO. / OATE.

F -0.4 os-13so.4 R EV.1 -T INTEGRITY STATUS TREE 00/10/2/83 2

~

ATTACH M ENT A E . 1 m

1 E"

G g ,

l -

i 1

T1 T2 i COLD LEG TEMPERATURE -

R-P.

ALL RCS PRESSURE NO gggg GO TO  !

- COLD LEG FR-P.1 TEMPERATURE POINTS TO E.

RIGHT 0F YES  !

LIMIT A ALL RCS l NO GOTO COLD LEG ee FR P.2 1 TEMPERATURES g GREATER THAN g 2500F YES

{ j- ALL RCS NO TEMPERATURE COLD LEG DECREASE IN NO TEMPERATURES ALL RCS COLD GREATER THAN

+ LEGS LESS 280 0F YES THAN 1000F IN THE LAST 60 YES MINUTES CSF.

SAT G r & 9-l ALL RCS NO COLD LEG i ATTAC H M ENT B , TEMPERATURES GREATER THAN

, 250 0 F YES i RCS PRESSURE NO l

' LESS THAN I p COLD # GO TO OVERPRESSURE ## FR P.2 LIMIT YES NO RCS l l _ TEMPERATURE

, GREATER THAN 350of YES f l CSF N -____ .-. -

. CODE

• SYMPTOM / TITLE

• PROCEDURE NO.

REVISION NO. / DATE:

F-0.4-R EV*1-T INTEGRITY STATUS TREE os-13so.4 0G/10/2/83 T -

r ,

l

(< . .-

Ai 1 ACHMENT A l,

l

. SEABROOK STATION-O'PERATIONAL LIMITS CURVE we i

• i f 2560 psig 250 F

% s 280 F  !

t 250u" ~-- :'.:

.s. ... .:  :....... a..:

e..,

I o o..o..o..m..m.o.o..m..o..o~..~..~..~.~..o..o..~..o..o..m.o.o. . . . . .......... ...... .

ADDED 28'F TO ALL l l F  :-: NOTE: -

s 2050 psig 2000

,3 TEMPERATURES FOR }..

l w ~ , . , . . , . ~ . - . ~ . . .... .-

'? " INACCURAClES, .':

C* -

5 l

! D3 ...

i .

....~......................

(4% x 700.*F).

W ' .... ... ............ ...... . . . . . . .................... .

l .... ...........

4 %.w ..

1 . .... .. ................ ..........

._...... . ~. .. .:.  :.,. .

.:,.s.v,.....

~... ...................................................

1000 .... . ............................. ....... .............

.%. ..::. ~.. . .

.~. ............... ................

i.. .. ..

.. . .. ~ . ... . ............ ................. ...........

500 s,_ , . .....

,.., .~r..... .. . . . .... ..............

O 0 100 2bo 300 450 ' 500)

TEMPERATURE ( F)

I l l I

l 1 I. .

l.

-.* -51.

11 12 s

CCCE '. SYMPTOM / TITLE: PROCEDURE NO.

REVISION NO. / DATE*

F-0.4 R EV'1-7 INTEGRITY STATUS TREE OS-1350.4

- 00/10/2/83

. Y m

' ~ "

ATTACH M ENT B '

8 Seabrook RCS cold overp'ressure protection setpoints LTOP in 355 F PRZR PORVS

~

" = " * * " t * * *~

C" PRZR PORVS point 2385 psig i

2500 , . , , .'. , , . . 6 . , . , . . .

6 . , . . . , 6 . . . , e e e , , , , ,

4 . , a 6 . . , i e , e i e e , . .

i F e e i 4 e eee a , 6 4 e a 6 . . 6 . i 6 i . . 6 .

6 . . . 6 , . . , . . . , i 6 e . 6 . . . , j 6 eea . .

. . . .. . , , . . . , e . . . . , . . . . . . 4 . , i . / . . . . i e

. t , ,. .

• 6 6 t e i . . 6 6 . . 4 6 . . . . , ,# .

4 4 f

, . . . . , , e e 6 . , . 6 . . , i . . 4 .

e , , .t 6 i e i + ,

^ i 6 . . . . . . . 4 e . 6 . . . . , .

6 i 6 e . 1 6 - e , 4 ,

, 9 g 2000 .

t i i

', */

g .

6 4 .

, . . . 6 4 . . e 4

4 i +

i

. . . . . 6

. .i

, ,2 i e i , 4 4 , e e t .6 . . # 4 ..e , . 6 t e 6 i 4 i e 4 f) i e e i 6 e t i (

. e e i . . . . . . . . e e , . . . i . . . . e . i , . . . . . . y e . . . . . . . . i--

7 . , . . . . . . . . . . . . . . . . . . . . . . . , i i . . . , e e iA . . , . i . 4 . .

== . . 6 , . . . . . . . i i e . , . . . . 6 e i u.mme

. 4 . 4 . . . t , e /s 66 6 i 4 , . . . e

. . # . 6 . . .b . . . s . .... . . . . . . 6 . . . . e ,

O . . ....# . . j . . . . . .e . . . . . . . . . . e , . . e , . e i

. . 6

.A fl

. , e .

e . .

1 Q, q nn . . . . . i . . . . . . . . . . . . . . 6 . . e 6 e e , 6 e . . . . . e e l s e . . . e si . , 6 .

y a vu . . . . . . . . . . . . . . . . . . . . . . . . f. . . . i , , , . ,

. . . . . . . . . . . . . . i.. . . , . . i . . . . . . . . . 4 . . .

.A , e . . . .

Ud . . 6 . , . . . . i , , . ..6 . . . , e e i . , , e , e fe e i . . e . i 6 e . . .

g .

e i

6 6 . . . . ....

.,s

. ./) i , . . . i i e,

6 . . . , .

4 . . i e i e e . . . . . . .

> . . , . . . . , . . . . . . ,,. . . . . , . . . , . . . . . . . . , , , e i . . . . . . . .

...,...,. . . . . .... . . . . i i i . . . . .. . . ,ri,, e , , , . , . . . . . . . . ,

i , . . i6 . . . . . . ..... 6 , . . . . . 6 . e s . .e . . ,A . . . . 6 . , . . . . . e i . .

C) c 1000 i... ..t

. . s . ,

e

, , e ifi

. . f;'

. e , ,

. . . . . . . . . . . . . . . . . .f6 i i . , . . . ... .

i e e . . . .

t 190* F _

. . 6 . . - .

. . , / e . .

. i 6 . . . .

. .s i i . . 4 i , . . # .

-; ii.,,e , , , . . . . .., .. . . . . . , se .,,,,e , , e . , .... , , , , ,6 4 , ,

(

, . . . . . .... ......,,,,..... w . . 6 . . . . . . . 4 . . ... 6 . , , ....,

I 'A . . . . . . . . . . p. , . . , . . . . . . .

. l

(

i ,

, . . e . ... . . . ...,# ..... . . , . . . . e . . . . i e i..........i.

.z00 .. , . . . . , . . . .., . . . ... . . , . , ,

.......,. . . .. .,. . ,......,... .., ..... 6 e , , . . , , , . .

. ......... . . . . ... 6 i . . . .... 6 . . . . . ... ..... ii . e , i . , . .

. . . . . . . , ,.. . . . . .. . ... . . 6 ....... . . . .,, j

..,,..... . . . . . . 4 e .4 . . . . . . ... .. 6 . .... . . , , . , ,

00 150 200 250 300 350 400; RCS TEMPERATURE ( F)  !

Notes: I h.e- rirm -. .qi c. er , c g

.- Y. e c___ir,OI N :

VA LID r-O R i .

CONTAINS MARGINS OF 10*F AND 60 PSI .

1 FOR FOSSIELE INSTRUMENT ERRORS '

P= 500 FSIG: T d 190*F

[ .

P= 364 + 5.752 e .016ssT: T> 190*F

} - ._ - . -

? _--- ---- - --

4.- _,

Q g

r. _ _ _

_- _-- _- .II l i __ _ _ _

lI i l l

. MAX PORV. SET POINT Emb T1 Z : g9

- ~

1 _T:T 2385 psig 2400 - - - - -

-_-_- .. SPRAY LIMIT 4- - jh{-a jz y g-g - be H g:' -- _._ __ __

AT 320 F w

-Q@#(g#g*jjg: e!i a

-Qb Hp:j!?

i!ij 2300 - - - - - - --- -

i i i i inn i i

_; H W -- ~ ~ ~ --

l m W E hN@h WI I: P!'.

LTOP !J $a!th nW l - -

2200- MAWn w

wegmsdw

? c .

Y F W-l[,!y.d W. :i j.j' e -- - - - -

-'PRESSURc LIMIT

[l 18,Ms D w

~ 2l00 _n t t_ _, _ _ ,

T swmn --.

. .. ,y,

-M, _ .,

.g y~

M i^'ji; i :Hj li {M,M

""l L MAXIMUM - ----

$2 2000- -COOLDOWN LIMITS 3 - - --

1. 5'i W jl ~ ~-~ ~ - ~ - ~ ~~-'

• 0;.19001 1-INC-D

~ ~

T OPERATING H' $

!?% * *

~

-E

__f IT-N:W"1 HEAT-UP LIMIT ----, _. . _ _

'j BAND ~ J- - -

1800- (.._-_ _q__- ,}__J- N[;,g nyc g j i 7J d  :;j]M .-_

i w _6 0"_F/_h r. f

- M e__\1, 3-

Cg w., m_0__0 n yn

_F_ SU_ B CO_OL!N_G

.Ag_

f a-g700_

O W

-- fMTARGilBf T G.T: 0: D y F ---- - - ---

W$jihM2g_

t D

~ - - - - - -

1600 -

_--- -T-

~

1 1- ~1 @ OPERATING 7:

f Q _

%W '

C "^ EW M - - --- _

W 1500 .my _.__ _-

Mr..

w

$*MBANDh" rim"l";;c P WN

• 0-1400 - - ~ -

SPRAY LIMIT K W*

1 d *TP"T G  ? 9 SIMiM MW m 1300 7

.1

-7 7 320"F AT f-7:[! $.$ $ id; iikNyl.N e

I - 2- -

~~

dUdli* "W

~~~~

7 l-4---- 4 I^"*"M o 1200 'W

~

f ~I~

A ## '

"L- ~

a: LTO P- W t hMMNNii W! 4 DP ~C'P REQUIRED NESH~

.a R l10 0 - -

PRESSURE"~'

~- I m FrNTW T-:/

C- --~-

f-

~~ - ~

- m.e b!N bWN-f--

o w 1000-LIMIT

_l.p-p

/ g mw.: ., a y

I!)

3 c . 444J y ,

1. -3 ? W- M. .ijy ii :: :Tb.MV

.-M- ii -

_ _O N LI NE- - - -

F 900 g_ _ 4/_ _.c - S. A. T. U. R. A. T. I. . . .

<g .0oF/hr. - y gp*94g.i:':,W S EP e p,#

4 9 '

5

~

lIIIIIII!II 20 F/hr.h o 800 f-h.h a,.+ DM W.%j!!!!!9n g g MIN. PRESSURE

,- k--_-/---

/--.--/fh.

g 700- 407/hr.~ - -- - - - - -

qWdd!y:s: v 7-g-g- -FOR RCP OPERATION -=

7 -

/ :100 # a u -

m v '! W' qq W j 600 i .j :: g M.p Ly /

e g,T/hr-g . . . . .(A. D. M. I.N. .) . . . .

r gp3 (-_ , NORMAL

. . . ~ -

HEAT-UP-d - - - - '

500 400 - 4[a 3

S me/hr..

60 7 g

p RH N jlw%.u@.

EiS. irs .$ .. g,e%ij Mv 7 -

d d.

--t AND COOLDOWN F-- - -

l 300 200 - p Q  %{g,g(4. gig fh.. ,

YgPFIESSU RE-TEMPERATURE:7 i "; gjf.; O;i$bM V: x : CURVE REV.WiO/19/83 :--

i N"*

~ ~ - - - - ~

100~ 8 g"4 .: '!'~  ;. @"pWRD

^ " '

W -

1. -T VALID FOR 16'.0 EFP YEARS.:

dwi ~' ~

l ' '''''''' '

i i u i i u' ' t i i o i i i u i i i a' ' a' ' _ u' u' ' i i a' 0- A_u"_t__ u____250 300 .1 350 400 t

450 500 550 600 650 700 750 85100 15 0 200 RCS AV?. LOOP TEMPERATURE (*F) Ow O

r C00E: SYMPTOM / TITLE PROCEDURE NO.

CONTAlN M ENT "'S'""' ^*

F-o.5 R EV.1-T STATUS TREE os-1350.5

' 00/10/2/83 J

R-CONTAINMENT

. PRESSURE LESS

=. -

,._ _ _ _ _ _ q =

CONTAINMENT NO PRESSURE LESS YES gam O 3 PSIG _

l l

CONTAINMENT NO [

i

, BUILDING LEV _EL l I

. LESS THAN 5 FT-8 IN YES

' GO TO

~

OOO FR Z.3 {

c. .

NO ,

( CONTAINMENT

. RADIATION LESS THAN I TWICE YES l BACKGROUND I CSF SAT e

ew, --

t-gw-,geg-e--w,- ge- - y p,eqy,.+e g- , y - , - p- p4g . -. ,,s.,s ev.- ,

CCCE: SYMPTOM / '1dh1GE~. enO LF UUnr. NJ.

REVISION NO. / DATE*

06 ke9*1r INVENTORY STATUS TREE os-1aso.e 00/10/2/83 w[ J

-(3&

~

(  :-

c .

RVLIS NO INDICATES VESSEL -

LEVEL N3 GREATER YES 0

TH AN 90 /o 9

ggg GO TO FR l.1 NO

..ESee ,zE.

• LEVEL LESS FR-l.2 g

THAN 92 Fo YES 8 i

. 1

~

l PRESSURIZER LEVEL

~

N YES O R-I3 1

(( RVLIS NO INDICATES ,

VESSEL LEVEL GREATER YES 0

TH AN 90 /o CSF l

SAT l

' ~ -

~~~'m' '

.. _ _ _ _ _ . _ _ _ . _ _ _ . _ _ _ . _ _ _ _ _ _ _