ML20209H311

Emergency Operating Procedure Writer'S Guide

ML20209H311
Person / Time
Site:	Oyster Creek
Issue date:	10/31/1985
From:	Fiedler P GENERAL PUBLIC UTILITIES CORP.
To:	Zwolinski J Office of Nuclear Reactor Regulation
References
RTR-NUREG-0737, RTR-NUREG-737 PROC-851031, NUDOCS 8511110068
Download: ML20209H311 (37)

Text

,. ,

l l

l l

6-

' OYSTER CREEK NUCLEAR STATION EMERGENCY OPERATING PROCEDURE WRITER'S GUIDE 9

+

8511110068 85 219

.em \ u PDR ADOCK PDR R

's

1.0 INTRODUCTION

1.1 PURPOSE The purpose of this document is to provide administrative and technical guidance on the preparation of Emergency

. Operating Procedures (EOP's). s 1.2 SCOPE This writer's guide applies to the writing of all EOP's.

2.0 EOP DESIGNATION AND NUMBERING EOP's are procedures that govern the plant operation during emergency conditions and specify operator actions to be taken to return.the plant to a stable condition.

Each plant procedure shall be uniquely identified. This iden-tification permits easy administration of the process of pro-cedure preparation, review, revision, distribution, and oper-ator use. The GPUN Corporate Policy and Procedures Manual de-fines the numbering scheme to be utilized.

2.1 COVER SHEET Every EOP shall have a cover sheet (see Figure 1). The

. primary purposes of this cover sheet are (1) to identify the procedure and (2) to identify the authorized revision.

2.2 PROCEDURE DESIGNATION ,

Designation of the emergency operating procedure shall be EMG.

2.3 PROCEDURE NUMBERING A subject code follows the designator which identifies J1009 L

the procedures as applying to Oyster Creek Plant Opera-tions, Following the subject code is a sequential number which consists of two digits.

Example: EMG - 3200 . 01 Sequence Number x Subject Code Procedure Designator 2,4 REVISION NUMBERING AND DESIGNATION The abbreviation "Rev" followed by a digit (s), will be used to designate the revision level of the emergency operating procedure..

Example: Rev. 1 Revision Level Abbreviation To identify revisions to the text of an-EOP, a change bar should be located in the right margin alongside the text change.

2.5 PAGE IDENTIFICATION AND NUMBERING Each page of the procedure will be identified by (1) the procedure title, (2) the procedure designator and number, (3) the revision number, (4) the page number specified as "Page of "

, and (5) the effective date. This information will be together at the top of each page, as shown'in Figure 2.

i J1009

3.0 FORMAT The following format is to be applied consistently for all EOP's.

3.1 PAGE FORMAT Instructions to the operator may be written across the s

. width of the page. The words IF, THEN, WHEN, AND, OR, UNTIL, OTHERWISE and BEFORE in bold typeface should be used, where possible, to separate the step into logical components on the page. If the instruction can be formu -

lated into an IF portion and a THEN portion, the IF por-tion should be'placed on the left hand side of the page l and the THEN portion should be placed on the right hand side of the page. In this way a dual column format can be utilized. The logic of using a dual column format is that if the conditions described in the IF portion of the statement cannot be met or do not apply, the THEN portion l

does not have to be read. The operator should skip.down to the next same level step. Substeps will not be separ-ated by a line across the page but major steps will be.

l I

3.2 TABLES AND GRAPHS Where multiple systems may be utilized to accomplish the specified actions a table should be used. A table may be tabbed for easy reference outside the body of the J1009 k

procedure or may be left within the procedure. The factors tha't determine this decision should be:

(1) familiarity of the information to the operator

-(2) criticality of the information to the operator

_(3)- length of the table ,

(4) frequency of use of the table.

It is generally advantageous to tab the table outside the body of the procedure since it shortens and gives greater clarity to the procedure itself. If'the operator is al-ready familiar with what actions to take, he will not be

' distracted by a table within the text -

If a table is tabbed outside the bo'dy of the procedure,

. the systems should be listed followed by a reference to the table. Tables should be presented in a dual column format. Systems are listed on the left and Operating Details are listed on the right.- The level of detail should be geared to licensed operators with the lowest ,

I level of experience and skill. Bold typeface is utilized for IF, THEN, WHEN, AND, OR, UNTIL, OTHERWISE'and BEFORE. Names of systems and components should be the same as labeled in the control room and the name the

operator is familiar with. Figure 3 gives an example of correct format for a table.

?

4

'J1009 1

< .- n- , , , - - - , - - - - , + , , ,...--., ---- --n -.,-,------,-v-- , - , , , , . - - - - - - - - , , , - , - - - - - , = - - . - - - . , , + - , - - - , - - - , - ~ ,

- -- . - - ~ --- . .

Graphs should be easily readable and understandable.

Instrumentation should be available in the control room to take the readings required to use the graph. The in-strumentation should accommodate the reading accuracy required by_the graph and/or procedure. Unite specified s

.on the graph should be the same as on the instruments in the control room. In conjunction with using a graph 4

_ tabbed at the back of the procedure, a short table may be sprovided to the operator within the body of the pro-cedure. This table should contain several significant points which give guidance to the operator about the be-havior of the line or curve. If there are no conditional statements for a procedure and graphs are utilized to a-great extent within the procedure, graphs may be put on-the~left hand.page.

More information is provided in Section 4.10 PRINTED OPERATOR AIDS.

3.3 PROCEDURE ORGANIZATION The'following division headings will be used in the be-ginning of' unique procedure numbers. For example: dry-

[

well temperature, EMG 3200.02, has its division headings under containment control, EMG 3200.02.

1. PURPOSE--The purpose will be descriptive of the intended use of the EOP.

J1009 s

L

, - - - - - - . , , - _ . _ _ , , - - , - . _ _ . , . . . . _ . - , , _ _ _ , - _ , - . - , , . _ . . .--_.__,-.,,_.,_,._. , -_ ._.,_,,,.,,- ,-- - - _ . - - . . . ~_. , . -

2. ENTRY CONDITIONS--The entry conditions _will include only.those alarms, indications, operating condi-a tions, automatic system actions, or other unique symptoms that the operator is to use in deciding to use the procedure. .g

3. OPERATOR ACTIONS--The operator actions will be short, concise, identifiable instructions that give appropriate directions to the user.

3.4 SECTION NUMBERING Section Numbering shall be done in such a way as to fa-

.cilitate operator use and understanding of the Emergency  :

Operating Procedures. For instance in the following ex-ample, bullets are used to designate division titles and an alpha / numeric system is used for operator actions and subsections. Letters are used as section designators.

EXAMPLE:

SUBJECT:

RPV Control Procedures DIVISIONS: Purpose Entry Conditions RC-1 Operator Actions SECTIONS: RC/L RPV Water Level Control RC/P RPV Pressure Control RC/Q RPV Power Control SUB-SECTIONS: RC/L-1 (First Instructional Step) f'

. J1009 s

INSTRUCTION STEP NUMBERING 3.5 Step numbers should be in bold typeface and underlined.

This effectively calls attention to the step. Up to three levels of steps'may be utilized but'every effort should be made to minimize the number of levels used. ,

Example:

RC/L Monitor & Control RPV Level RC/L-1 Actions RC/L-1.1 Contingency Actions RC/L-1.1.1 Contingency Action Support Instructions 3.6 CONDITIONAL STATEMENTS l Conditional statements are used to define a set of cir-cumstances which constitute a reason for exiting one pro-cedure and entering another or for performing additional actions.- Conditional statements are statements put 'on the left hand pages, opposite the procedural steps to which they apply. The statements.should conform to the IF, THEN format and should apply to all steps on the right hand page. Any time that the operator performs one of the steps on the right, and he meets one of the

" conditions" on the left, he shoald go to the conditional statement and follow it. The " conditions" are printed in f-a' smaller bold typeface than IF, THEN, WHEN, AND, OR, UNTIL, OTHERWISE and BEFORE.

J1009 s

- This smaller bold print in the conditional statements serves to emphasize the " condition" to be alert for. If

'the operator is referred to another procedure in the con-

i. '

ditional' statement, the name of the procedure will be printed in all capital letters. Likewise, if the opera- -

tor is referred to a graph, the name of the graph will be printed in all capital letters. The title of a graph in-

, the procedure text itself should not be all capital letters. Only the first letter of each word should be capitalized. Figure 4 is an example of a conditional statement page.

4.0 WRITING INSTRUCTIONAL STEPS

, 4.1 INSTRUCTION STEP LENGTH AND CONTENT Instruction steps will be concise and precise. Concise-ness denotes brevity; preciseness means exactly defined.

- Thus, instructions should be short and exact. The General Rules to be used in meeting these objectives are as follows:

. Instruction steps should deal with only one idea. l 1

. Short, simple sentences should be used in prefer-- l I

ence to long, compound, or complex sentences, j

. Complex evolutions should be prescribed in.a series of steps, with each step made as simple as prac-ticable.

i J1009.

s 4

4

/

. Objects of operator actions should be specifically stated. This includes identification of exactly what is to be done and to what.

. For instructional steps that involve an action verb relating to three or more objects, the objects will be listed with a bullit preceding the object. If operator checkoff is required a table should be provided with space preceding the object.

. Limits should be expressed quantitatively whenever possible (refer to Subsection 5.5).

. Mandatory sequence of steps is assumed unless otherwise stated.

. The listing of systems, components, or conditions should be utilized in tables as well as in the pro-cedure. When order is not important bullets should be used.' When proper sequence should be followed numbers should be used.

. Identification of components and parts should be sufficient to allow easy and correct operator recognition.

. Instruction content should be written to communi-cate to the user.

. Expected results of routine tasks need not be stated.

J1009 s

I

r-

. When actions are required based upon receipt of an annunciated alarm, list the setpoint of the alarm for ease of verification.

. When considered beneficial to the user for proper

~

understanding and performance, describe the system g response time associated with performance of the instructions.

. When system response dictates a time frame within which the instruction must be accomplished, pre-scribe such time frame. If possible, however,

. avoid using time to initiate operator actions.

Operator actions should be related to plant para-meters.

. When anticipated system response may adversely af-fect instrument indications, describe the condi-tions that will likely introduce instrument error by using a NOTE or CAUTION.

. When additional confirmation of system response is considered necessary, prescribe the backup readings to be made. l 4.2 USE OF LOGIC TERMS The logic terms IF, THEN, WHEN, AND, OR, UNTIL, OTHERWISE and BEFORE are often necessary to describe precisely a setoof conditions or sequence of actions.

J1009 s

l

l 1

Logic terms will be emphasized by the use of bold type-face so that all the conditions are clear to the operator.

l Use logic terms as follows:

. When action steps are contingent upon cer-b tain conditions or combinations of condi- g -

tions, the step shall begin with the words IF or WHEN followed by a description of the condition or conditions, the word THEN, followed by the action to be taken.

. WHEN is used for an expected condition. IF-is used for an unexpected but possible con-dition.

. THEN shall not be used at the end of an action step to instruct the operator to perform the next step because it runs ac-tions together.

. The use of AND and OR within the same ac-tion shall be avoided. When AND and OR are '

used together, the logic can be very am-biguous.

. When attention should be called to combina-tions of conditions, the word AND shall be placed between the description of each con-dition. The word AND shall not be used to J1009 s

L

\

g j join more than three conditions. If four or more conditions need to be joined, a

, list format shall be used.

. The word OR shall be used when calling at-tention'to alternative combinations of con- s ditions. The use of the word OR shall al-ways be in the inclusive sense. To specify the exclusive "OR," the following may be used: "either A OR B but not both."

. UNTIL signifies to the operator the condi-tion (s) under which he should stop perform-ing a previous instruction.

. OTHERWISE should be used in cases where if

~

4 the IF statement does not apply the' opera-l tor should not drop down to the next step.

OTHERWISE catches him and gives him other instructions.

. The word BEFORE shall be used when operator action is to be taken prior to reaching a limit, but may be'done at any earlier time at the operator's discretion.

4.3 USE OF CAUTIONARY INFORMATION AND NOTES Cautionary information can be considered in two funda-mental categories: those that apply to the entire pro-cedure and those that apply to a portion or a specific I

J1009 s

)

. _.14 _

step of the procedure. Those that apply to the entire procedure are called " PRECAUTIONS" and may be covered in operator training. Those that apply to a portion of a procedure are called " CAUTIONS" and are placed immediate-ly before the procedural steps to which they apply. ,

Cautions shall extend across the entire width of the step (s)-for which they apply or, if an IF, THEN state-ment, two column format is being utilized, the caution should only extend across the THEN statement.

. This is so that the operator does not have to read the caution if the IF statement does not apply. Format for~a caution is illustrated in Figure 2.

Placing the caution before the step helps ensure that the procedure user observes the caution before performing the step.

A caution cannot be used instead of an instructional step. It should be used to denote a potential hazard to equipment or personnel associated with or consequent to the subsequent instructional step.

If additional information other than cautions is neces-sary to support an action instruction, a note should be used. A note should present information only, not in-structions, and should be placed before the procedural steps to which they apply. A note, like a caution, may e

J1009

s l

_ ., ,.,. ..__m _

l l

1 extend across the width of the page or only across the )

l right hand column.. Format for a note is illustratad in -l 1

Figure 5.

1 4.4 CALCULATIONS Mathematical. calculations should be avoided in EOP's. If 3 ,

a value has to be determined in order to_ perform a pro-cedural step, a chart or graph should be used whenever possible.

4.5 BRANCHING AND CONCURRENT PERFORMANCE OF STEPS When more than one procedure or parts of a procedure are to be followed concurrently, the direction to do so will be stated explicitly.

When it is required to branch from one procedure, or step in a procedure, and perform the actions specified in another procedure or step, the instructions to do so shall be stated explicitly and will conform to.the fol-lowing rules.

A. BRANCHING TO ANOTHER PROCEDURE Use the Key Word " Enter Procedure" followed by the Procedure Number, Name, and Step No. as appropriate.

Example:

Enter Procedure EMP 3200.01 RPV CONTROL'at Step RC/L-3 J1009

, s

D'

\

cr .B. BRANCHING BACKWARD IN THE'SAME' PROCEDURE

/*

Use the Key Words " Return to" followed by.the Step

.. No.

Example:

., Return to Step RC/L-3 s C. BRANCHING FORWARD IN THE SAME PROCEDURE Use the Key Words " Continue in this procedure.at" followed by the Step No.

Example:

_, Continue in this procedure at Step RC/L-3

4. 6' COMPONENT IDENTIFICATION Withrespecttoidentificationofcomponents,theJollow-ing rules are to be followed:

. Equipment, controls, and displays will be identi-fled in operator language (common usage) terms.

. . When the engraved names and numbers on panel A

placards and alarm windows are specifically the -

'N i item of concern in' the procedure, the engraving -

.i should be quoted. verbatim.  ;

. The-namesofplants[stemtitlesareemphasizedby i l

initial capitalization'. When the word " system" is  !

-1 deleted from the' title because of brevity and is -

understood because of the context, the title is also emphasized by initial capitalization. s J1009 1

k. e i

\

o

.-[,.___.-._._._-_-~. . _ _ _ _ _ _ . _ _ . , , , , _ _ , _ . _ _ _ _ . . . . _ , , . _ . . . , . , . . _ . - . _

l

. If the component is seldom used or it is' felt that 1 the component would be difficult to find, location' information should be given in parentheses follow-ing the identification.

4.7 PRINTED OPERATOR AIDS v When information is presented using graphs, charts,

-tables, and figures, these aids must be self-explanatory, legible, and readable under the expected conditions of use and within the reading precision of the operator.

4.7.1 Units of Measure Units of measure on figures, tables, and attach- .

ments should be given for numerical values that 1

represent observed, measurement data, or calcu-lated resnits. A virgule (slant line) should be used instead of "per"; examples: ft/sec, lbs/hr.

4.7.2 Titles and Headings t

Capitalization should'be used for references to tables and figures,. titles of tables and figures within text material, and column headings within 4-a table. The first letter of each word should be capitalized. Onthetablepagetitlesshoukd be capitalized.

4.7.3 Figure, Table, and Attachment Numbering Sequential arabic numbers should be assigned to J1009

~

t

c:

i tables and attachments, which are not included as an. integral part of the text of the procedure. The sequence should correspond with the order of their reference in the text. The symbol "#" and abbrevi-ation "No " are unnecessary and should not be s used. The number alone suffices. Figures are dif-ferentiated from tables by the use of a sequential letter rather than number.

Examples: Fig. A, Fig. B, etc.

Table 1, Table 2, etc.

,, Attachment 1, Attachment 2, etc.

' Page identification for attachments should con-i

'sist of a block of information that identifies (1) procedure number, (2) attachment number, (3) page number, and (4) revisio'n number. Page num-berir," of attachments should meet the require-eat ~ of Subsection 2.5.

Section numbering for attachments should be in accordance with Subsection 3.3. l 4.7.4 Flowcharts may be utilized to augment operator I understanding of an entire procedure or pro-cedure section. ,

5.0 MECHANICS OF STYLE l

5.1 SPELLING 1

J1009 s s

~

Spelling should be consistent with modern usage. When a choice of spelling is offered by a dictionary, the first spelling should be used.

5.2 HYPHENATION Hyphens are used between elements of a compound word when ,

usage calls for it. The following rules should be fol-lowed for hyphenation.

. When doubt exists, the compound word should be re-structured to avoid hyphenation.

. Hyphens should be used in the following circum-stances:

a. in compound numerals from twenty-one to ninety-nine; example: one hundred thirty-four

b. in fractions; examples: one-half, two-thirds

c. in compounds with "self'; examples: self-con-tained, self-lubricated

d. when the last letter of the first word is the same vowel as the first letter of the second word--as an alternative, two words may be used; example: fire-escape or-fire escape

e. when misleading or awkward consonants would re-sult by joining the words; example: -bell-like

f. to avoid confusion with another word; examples: re-cover to prevent confusion with recover, pre-position to avoid confusion with preposition J1009

c

g. when a letter is lirked with a noun; examples:

X-ray, 0-ring, U-bolt, I-beam

h. to separate chemical elements and their atomic weight; examples: Uranium-235, U-235 5.3 PUNCTUATION g J

Punctuation should be used only as necessary to aid read-ing and prevent misunderstanding. Wor'd order should be selected to require a minimum of punctuation. When extensive punctuation is necessary for clarity, the sentence should be' rewritten and possible made into several sentences. Punctuation should be in accordance with the following rules.

5.3.1 Brackers -

Do not use brackets.

5.3.2 Comma Use of many commas is a sign the instruction is too ,

complex and needs to be rewritten. Therefore, evaluate the number of commas to ensure the in-struction is not too complex. A comma should be

.used only to prevent misunderstanding.

5.3.3 Parentheses ,

Parentheses shall be used to indicate alternative items or designations in a procedure, instruction, or equipment numbers.

J1009 b

l

21 -

5.3.4 Period' A' period need only be used to separate a_ complete.

sentence from another sentence or to indicate the ,

decimal place in numbers.

5.4'  : VOCABULARY .

Words used in procedures should convey precise under-standing to the trained person. The following rules-apply.

..Use simple words. Simple words are usually short words of few syllables. Simple words are generally common words.

. Use common usage if it makes the procedure easier to understand.

. Use words that are concrete rather than vague, specific rather than general, familiar _rather than formal, precise rather than blanket..  ;

. Define key words that may-be understood in more than one sense.

. Verbs with specific meaning should be used.

Examples are listed in Table'1.

. Equipment status should be denoted as follows:

a. Operable / operability--These words mean that a system, subsystem, train, component, or device l is capable of performing its specified function (s) in the intended manner. l l

J1009

.l

~

L

-~ - - . . , . . , ,

b. Operating--This word means that a system, subsystem, train, component, or device is in operation and is performing its speci-fled functions (s), and that conditions do not prevent it from maintaining that ser- s vice.

c. Available--This word means that a system, subsystem, train, component, or device is operable and can be used as desired; how-ever, it need not be operating.

An example of this would be the main con-densers, which can be operable in that all associated pump, valves, and components are operating or operable but may not be avail-able because the main steam system is iso-lated.

9 J1009 s

.a- w" -t e +4

d. ..

23 -

Table 1. Action Verbs Verb Application

'Close To change the physical position:of a mechanical device so that it prevents physical access or flow or permits passage of electrical current, for ex- s ample, "close valve V-14-35" Decrease Do not use because of oral communication problems.

Establish To make arrangements for a stated condition, for example, " establish communication with control room" Execute To accomplish specific procedural requirements, for example, execute Steps RC/Q-4 and RC/Q-5 concur-rently.

Increase Do not use because of oral communication problems.

Maintain -To control a parameter within certain limits, for example, " maintain RPV water level between +138 in TAF (low lev 31 scram setpoint) and +176 in TAF (high level turbine trip setpoint)

Open To change the physical position of a mechanical device, such as valve or door to the unobstructed position that permits access or flow, for example, "open valve V-14-35" Record To document specified condition or characteristic, for example, " record discharge pressure" J1009 s

L 4

Table 1. Action Verbs (Continued)

Verb Application Set To. physically adjust to a specified value an ad-justable feature, for example, " set diesel speed to

. . . ' rpm'" ,

Start To originate motion of an electric or mechanical device directly or by remote control, for example,

" start . . . pump" Stop To terminate operation, for example, "stop . . .

pump" Throttle To operate a valve in an intermediate position.

Trip To manually activate a semi-automatic feature, for example, " trip breaker . . .

vent To permit a gas or liquid confined under pressure to escape at a vent.

5.5 NUMERICAL VALUES The use of numerical values should be consistent with the following rules:

. Arabic numerals should be used.

. For numbers less than unity, the decimal point should be preceded by a zero; for example: 0.1.

. The number of significant digits should be' equal to the number of significant digits available from the display and the reading precision of the operator.

1 J1009 s

__, , , ,,, ... - .,-,-- .~~,. --....-- -. -- .,, - - - - , -

L

. Acceptance values should be specified in such a way

. that addition and s'btraction u by the user'is avoided, if possible. 'This can be done by stating '

acceptance values as limits. For example:

J Maintain RPV' level between.+138 in. (low level g.

scram setpoint) and +176 in. (high level turbine trip setpoint).

. Engineering units should always be specified for numerical values of process variables. They should be the same as those used on the control room dis-plays, for example: GPM instead of LBM/HR 5.6 ABBREVIATIONS, LETTER SYMBOLS, AND ACRONYMS The use of abbreviations should be minimized because they may be confusing to those who are not thoroughly familiar with them. Abbreviations may be used where necessary to save time and space, and when their meaning.is.unques-tionably clear to the intended reader. Consistency should be maintained throughout this procedure.

Capitalization of abbreviations should be uniform. If the abbreviation is comprised of lowercase letters, it I should appear in lowercase in a title or heading. The period should be omitted in abbreviations except in cases where the omission would result in confusion.

Letter symbols may be used to represent operations, quantities, elements, relations, and qualities.

J1009 s

I

t ,-

'An acronym is a type of symbol formed by.the initial letter or. letters of each of the successive parts or major parts of a compound term. Acronyms may be used if they are defined or-commonly used.

Abbreviations, symbols, and acronyms should not be over- su used. Their use should-be for the benefit of the reader. They can be beneficial by saving reading time, ensuring clarity when space is limited, and communicating mathematic ideas.

6.O TYPING FORMAT ~

6.1 GENERAL TYPING . INSTRUCTIONS For emergency operating procedures, the following general requirements are to be followed.

. Paper size thould be 8-1/2 x 11 inches.

. The following color paper should be used for these procedures:

1. RPV Level Control - Blue

2. Level Restoration - Blue

3. Spray Cooling - Blue

4. RPV Pressure Control - Pink

5. Emergency Depressurization - Pink

6. RPV Power Control - Yellow

7. Steam Cooling - Pink

8. Alternate Shutdown Cooling - Pink

9. RPV Flooding - Blue J1009 s

4

- 10. Containment Control - White

11. Torus Temperature Control - White

12. Drywell Temperature Control - White

13. Primary Containment Pressure Control - White

14. Torus Level Control - White

. Courier, pitch 10, print element is to be used.

6.2 PAGE ARRANGEMENT

. Page margins are 3/4 inch margin on left and ,

right. In Elite type (12 characters per inch),

this represents 8 characters.

. Page identification information (refer to Subsec-tion 2.4) will be located-in the appropriate blocks at the head of the page.

. The 8-1/2 inch edges shall constitute top and bot-tom of pages and text. Tables and figures shall be readable with the page so arranged. Rotation of printed matter should be avoided for emergency operating procedures. Refer to Subsection 6.5 if rotation is absolutely necessary.

6.3 BOLD TYPEFACE The following list will be in bold typeface with tne specified type size:

1. procedure title - 14 pt. bold

2. purpose, entry conditions, cperator actions - 12 pt. bold with underscore

3. If - then - 12 pt bold J1009

I l

1 1

I 4.: conditional statements (following if - then, such I

as procedure name and parameter) - 10 pt. bold

5. all numbers - in body or in conditional statement -

12 pt. bold

6. .all headings - cautions, notes, table headings, ,;

procedure step numbers (in body of procedure) - 12 pt. bold

7. procedure number - 10 pt. bold 6.4' BREAKING OF WORDS Breaking of words shall be avoided to facilitate operator reading.

6.5 . ROTATION OF PAGES If pages need to be rotated, these rules shall be fol-lowed.

. The top of the page with rotated print is the normal left-hand edge.

. The page margins do not rotate.

. Page identification and numbering will not be ro-tated.

6.6 PRINTED OPERATOR AIDS Figures include graphs, drawings, diagrams, and illustra-tions. The following rules are established.

. The figure is placed three line spaces above the figure field (refer to subsection 4.10). (Figures which appear as an integral part of the procedure text will not be numbered but will have a title.)

J1009

. The figure number and title should be in bold type-face, 14 point Boston bold caps.

. . The figure field must not violate specified page margins.

. The figure field should be of sufficient size to .

' offer good readability.

. The essenEial message.should be' clear; simple

-presentations are preferred.

. Grid lines of graphs should be at 1' east 1/8-inch apart; numbered grid lines should be bolder than unnumbered grid lines.

. Labeling of items within the figure should be ac-companied by arrows pointing to the item.

. The items within the figure should be oriented naturally insofar.as possible. For example, height on a graph should be along the vertical axis.

. In general, items within the figure should be

-labeled. Typed labels should use courier type, 3

pitch 10. Handwritten labels should be printed, using all capitals, with letters and numbers at least 1/8-inch high. ,

. All lines in figures should be reproducible.

2 Tablea should be typed using the following rules.

I . Type style and size should ba the same as that for l

l P the rest of the procedure. I I J1009 1

. . . ,_,. , ,, ___...... . - .-. _ _ . . . _ , _ . . . , , , . _ . - , , - _ _ , , , . - , ~ .-- .__ _ _ _ . , _ _ . . ._ . _ _ _ . - _ . . _ .

. The table number and title should ha in bold type-face, 14 point Boston bold caps, and located above the table field and three line spaces below preced- '

ing text. (Tables which appear as an integral part of the procedure test will not be numbered but will g

~

have a title.)

. . A heading should be entered above each column in

' bold typeface, 14 point Boston bold caps.

For example: SYSTEM and DETAILS, which should be centered in the column.

. Horizontal lines should be placed above and below the column headings; vertical lines, while desir-able, are not necessary or required.

. Double spacing between horizontal entries suffices to segregate such entries, although horizontal lines may also be used if desired.

If used, double horizontal-lines should be used above and below the column headings.

. There should not be a vacant cell in the table. If no entry is necessary, "N.A." should be entered to indicate not applicable.

6.7 USE OF FOLDOUT PAGES i

When used, a foldout page is treated as a single page.

It should follow the same format as a standard page l

J1009

~

I i

4 h

1

)

1 except the width is different. The page should be folded so that a small margin exists between the fold and the right-hand edge of standard pages. This will reduce wear of the fold.

6.8 USE OF OVERSIZED PAGES s oversize pages should not be used. They should be re-organized or reduced to a standard page. If this cannot be done, a foldout page should be used.

6.9 USE OF REDUCED PAGES Reduced pages should be avoided whenever possible. Final size of reduced pages should be standard page size.

Reduced pages should be readable and need not conform to the type size requirements.

7.0 REPRODUCTION Reproduction will be done on a standard copier.

J1009

~

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

- ~

L OYSTER CREEK NUCIZAN GENERATINCT h 7 ' STATION PROCEDURE EMG - 3200.01 Title RPV CONTROL (LEVEL) Revieson No.

~

1 A;;"- " :// Scope Responsible Office EMERGENCY OPEhtATING PROCEDURE. FOR OYSTER CREEK IO 2200 This documentis important to safety 8 Yes O No Effoctive Date (9/1/84) 9/30/84 Ust of Effective Pages PAGE REVISION I 1 2 0 3 0 4 0 5 1 6 0 7 1 Figure 1 8 0 9 1 10 0 11 1 12 1 13 'l 14 0

~

. .. t-

). ('} yf 3 ', (i..; L / J i * :"; ONLY

. 1 i Signature Concurnng Organization Element Date Onginator ((9j , hfA N Concurred by kkM _gAJ MANAGER - OPERATIONS ENGINEERING PLANT ENGINEERING DIRECTOR _#

[ /P4 PRG CHAIRMAN Flh M MANAGER O.C. OA MOD / OPS 9 kkh t

e

! O

< I i

~ Approved by 3 M A A B * ,f/ VICE PRESIDENT AND DIRECTOR, O.C. mj g, u i I [Y' R j-F F fffW !

, EOOOTOS1 2 84

- _ - _ . e

rea:eewe na no. .

3 CONTAINMENT CONTR3L' EM 2-3200.o2  % of Pages TOR /T TORUS %n o..

l TEMPERATURE FIGURE 2 TOR /T Monitor and control Torus Water Temperature TOR /T-1 Close any stuck-open relief valve using the following techniques:

1 TOR /T-1.1 Cycle the controller for the stuck-open relief valve open and closed multiple times TOR /T-1.2 IF The valve (s) fail to receat THEN Remove the control power.

fuses in cabinet ER18A or' B in the 480V switchgear room for the stuck-open relief valve CAUTION Removing the control power fuses from both NR108A and NR108B defeats ADS for all valves See Table 5 for fuse designations TURN PAGE

• P'"*"* J Proc.

• r. no. ,

m2-32oo.o2  % 6, ,,,,

CONTAINMENT CSNTROL TOR /L TORUS LEVEL 1

FIGURE 3 CORE SPRAY SYSTEM LINE-UP SYSTEM OPERATING DETAILS Core Spray System I 1. Confirm stopped I System I Core Spray -

pumps NZOlA, NZOlC, NZO3A and NZO3C

2. Close torus suction valves V-20-3 and V-20-32 l

3. Open CST supply valves V-20-1, V-20-5 1 and V-20-34 l

4. Start a System I core spray pump ( *NZO1A or NZOIC) and booster pump

( NZO3A or rNZO3C)

5. Confirm open flow path to torus via V-20-27

6. When the torus water level is greater than

-1.9 in but less than 10.9 in, secure the System I pump (s) started in step 4 above

7. Close V-20-1,

'V-20-5.

V-20-34 V-20-27

8. Open V-20-3 and V-20-32 i

I TURN PAGE '

s

i P m ure Procedure No. ----- - ---

CONTAINMENT CONTROL EMG-3200.02 Page.. O of Pages l PC/P PRIMARY CONTAINMENT nov, n uo. .

one PRESSURE .

FIGURE /. '. -

PC/P-3 IFTorus Pressure cannot be main- THEN EMERGENCY RPV DEPRES-tained below the Torus Pressure SURIZATION IS REQUIRED; Limit, Fig G enter Procedure EMG-3200.01 RPV CONTROL at step RC-1, and execute it concurrently with this procedure l 1

FIGURE G. TORilS PRESStiRE LIMIT 55 A -IA /

" r  ! g P .'

R . .

E 45 ----~----'-----

-- ----~- - - ------- - --

S

• S .'

U . .

R '

E l l 40 i i p . . . .

s  : l l l I . . . .

A 35 - - - - -l - - - - - ---

-j--- - ----------

---

l----------

. . . . 4

. . e .

30 - I -

I I I o tao a40 aso 480 TORUS WATER LEVEL (IMCHES3

.~

I

- _ _..,.-,-.-__.-___ -,.. --_...- -..__... _--. ..- ----_.~ .---

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

m m m. ag; 2

"r

- RPV CENTROL 'YE-sagar: - y."y  %  ?

RC/ POWER CONTROL a- =. o.= n l  ;

E FIGURE 5 I i

RC/Q-5.4.3 Confirm open the SDV Vent and Drain Valves RC/Q-5.5 ,

NOTE ,

Control rods of highest reactivity should be selected first .

1 Individually open the scram test switches for control Rods not inserted to at least position 02.

When a Control Rod is not moving inward close the. associated scram test switch. Remain at this step in the procedure until all control rods not inserted tb position 02 have been ,

individually scrammed.

RC/Q-5.6 Reset the Reactor Scram RC/Q-5.6.1 -

IF The scram cannot be THEN Start available CRD Pump reset AND Close V-15-52 (CRD charging water supply valve)

RC/Q-5.6.2 IF No CRD Pump can be THEN Go to step RC/Q-5.7.1 started ss

GPU Nuclear Corporation

. NNOIME 100 Interpace Parkway Parsippany. New Jersey 07054-1149 (201)263-6500 TELEX 136-482 Wnter's Direct Dial Number:

October 31, 1985 Mr. John A. Zwolinski, Chief Operating Reactors Branch No. 5 Division of Licensing U.S. Nuclear Regulatory Commission Washington, D. C. 20555

Subject:

Oyster Creek Nuclear Generating Station Docket No. 50-219 NUREG-0737, Supplement 1 Emergency Operating Procedures (E0Ps)

The enclosure to this letter is the Writer's Guide utilized in the development of the E0Ps for Oyster Creek. Tnis completes the submittal of the procedures generation package required by the subject NUREG.

If you should have any questions, please contact Mr. Michael W. Laggart, Manager, BWR Licensing at (201) 299-2341.

Very truly yours, Vice President and Director Oyster Creek 1r/1968f.

cc: Dr. Thtmas E. Murley, Administrator Region I U.S. Puclear Regulatory Commission 631 Park Avenue King cf Prussia, Pa. 19406 NRC Resident Inspector Oyster Creek Nuclear Generating Station-Forked River, N. J. 08731 0 00

s. ;,

GPU Nuclear Corporation is a subsidiary of General Pubhc Utilities Corporation I

_ __J