ML17215A849

Rev 2 to Procedure Qi 5-PR/PSL-2, Writers Guide for Emergency Operating Procedures.

ML17215A849
Person / Time
Site:	Saint Lucie
Issue date:	03/25/1985
From:	Sager D FLORIDA POWER & LIGHT CO.
To:
Shared Package
ML17215A846	List: ML17215A845 ML17215A847 ML17215A849
References
QI-5-PR-PSL-2, NUDOCS 8504190317
Download: ML17215A849 (46)

Text

ATTACHMENT 1 ST ~ LUCIE PLANT WRITERS GUIDE FOR EMERGENCY OPERATING PROCEDURES 8504198317 888418~

PDR ADOCK 05000335 F PDR '(

FOR INFOHlNATION 0tH.Y QI 5-PR/PSL-2 This document is not controlied. Befbto~, Revision 2 verify information with a controlfisd docu'men}.

March - 1985 Page 1 of 36 FLORIDA POWER & LIGHT COMPAiiY NUCLEAR ENERGY DEPARTMENT ST ~ LUCIE PLANT WRITERS GUIDE FOR EMERGENCY OPERATING PROCEDURES 1+0 APPROVAL:

Reviewed by Facility Review Group October 12 1983 Approved by J . H. Barrow (for) Plant Manager October 13 1983 Revision 2 Reviewed by F R G N~r~L i4 19FS Approved by Plant Manager 4 44 19 V

2.0 PURPOSE

2.1 This document is intended to provide administrative guidance in the preparation of Emergency Operating Procedures (EOPs).

3+0 SCOPE:

3'1 This guide applies to the preparation of all EOPs.

4.0 RESPONSIBILITIES

4.1 Each person drafting or revising an EOP is responsible for using the format described in Appendix A of this procedure. I 4.2 The Plant Manager is responsible for approving each EOP.

4.3 Each EOP shall be verified for technical accuracy and written correctness using QI 5-PR/PSL-3, "EOP Verification Procedure", prior.

to implementation.

4.4 Each EOP shall be validated for usability and operational correctness using QI 5-PR/PSL-4, "EOP Validation Procedure", prior to implementation.

5.0 INSTRUCTIONS

5.1 The format and instructions for preparing EOPs is contained in Appendix A of 'this procedure.

QI 5-PR/PSL-2 Revision 2 March - 1985 Page 2 of 36 APPENDIX A FLORIDA POWER & LIGHT COMPANY ST ~ LUCIE PLANT WRITERS GUIDE FOR EMERGENCY OPERATING PROCEDURES

J l QI 5-PR/PSL-2 Revision 2 March 1985 Page 3 of 36 TABLE OF CONTENTS Section ~Pa e INTRODUCTION ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ o ~ ~ ~ o ~ ~ ~ ~ ~ ~ ~ ~ ~ o5 lol PURPOSE ~ o ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ 5 1.2 SCOPEo ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ o5 EOP DESIGNATION AND NUMBERING ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ o ~ ~ ~ ~ ~ o5 2.1 COVER SHEET ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ o ~ ~ ~ 5 2o2 PROCEDURE DESIGNATION ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ o ~ ~ ~ oo ~ ~ o ~ ~ ~ ~ ~ ~ .5 2.3 PROCEDURE NUMBERING ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ .~~ ~ ~ ~ ~ ~ ~ ~ ~ ~ 7 2o4 REVISION NUMBERING AND DESIGNATION ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ 7 2 ' PAGE IDENTIFICATION AND NUMBERING ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ o ~ ~ ~ ~ ~ ~ o ~ ~ ~ ~ ~ ~ ~ 7 2 ' PROCEDURE ACCESSIBILITY ~ ~ ~ ~ ~ ~ o ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ o ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ .8 FORMAT ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ 10 3.1 PAGE FORMAT ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ o ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ 10 3.2 PROCEDURE ORGANIZATION ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ 10 3.3 SECTION iVUMBERING ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ' ~ o ~ ~ ~ ~ ~ ~ ~ ll 3.4 INSTRUCTION STEP NUMBERING ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ . ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ 11 3.5 OPERATOR AIDS NUMBERING ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ . ~ ~ ~ ~ ~ ~ ~ ~ ~ 11 WRITING INSTRUCTIONAL STEPS ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ 11 4ol CONVERSION OF CEN 152 TO PLANT SPECIFIC PROCEDURES ~ ~ ~ ~ ~ ~ ~ oil 4.2 IVi STRUCTION STEP LENGTH AND CONTENT ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ o' ~ ~ ~ ~ 14 4 .2.1 GENERAL GUIDES ~ ~ o ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ o ~ ~ 14 4 ' ' INSTRUCTION COLUMN ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ . ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ 16 4 '.3 CONTINGENCY ACTIONS COLUMN ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ 17 4.2 USE -OF LOGIC TERMS ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~

' ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ l7 4.3 USE OF CAUTIONARY INFORMATION AND NOTES ~ ~ ~ ~ ~ ~ . ~ ~ ~ ~ ~ . ~ ~ ~ ~ ~ .18 4.4 CALCULATIONS ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ 19 4 5 USE OF UNDERLINING ~ o ~ ~ ~ ~ ~ ~ ~ ~ o ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~

'o

~ ~ ~ ~ ~ ~ ~ ~ o ~ ~ ~ ~ ~ ~ ~ 19 4 ' REFERENCING A%) BRANCHING TO OTHER PROCEDURES OR STEPSON o ~ 20 4o7 COMPONENT IDENTIFICATION ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ 20 4.8 LEVEL OF DETAILS ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ . ~ 21 4.9 PRINNTTED OPERATOR AIDS ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ' ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ .22 4 'ol UNITS OF MEASURE ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ . ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ 22 4.9.2 TITLES AND HEADINGS ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ .~. ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ 23 4.9.3 FIGURE e TABLEe AND ATTACHMENT NUMBERING ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ 23

QI 5-PR/PSL-2 Revision 2 March 1985 Page 4 of 36 TABLE OP CONTENTS (Continued)

Section ~Pa e I

ME CHAN CS 0 P STYLE ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ 24 5 .1 PUNCTUATION'~

SPELLING ~ o ~ ~ ~ ~ o ~ o ~ ~ ~ ~ o ~ ~ ~ ~ ~ ~ ~ ~ oo ~ ~ ~ ~ ~ ~ ~ oo ~ o boffo'o ~ ~ ~ ~ ~ ~ ~ ~ .24 5.2 'YPHENATION.. ~ ....... .......~ ~ ~ ~ .os . ~ .o.. ~ ...oooo'o ~ . ~ ~ 25 5.3 . ~ ooo ~ o.... ~ ~ o.... ~ ~ ~ ~ ~ ~ o ~ ~ ~ ooo ~ ..o ~ . ~ ~ ~ . ~ ~ .25 5 'ol BRACKETS ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ 25 5 .3 2 COLON..............................................25 5 ~3 ~3 COMMAo ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ 25 5 o3 o4 PARE N THE SE S ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ o 25 5 .3.5 PERIOD ~ ~... .. ~ ~ . ~... ~...... ~ . ~ . o. o o o. ~ . o o ~......'. o ~ 26 5.4 VOCABULARY ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ o ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ 26 5 ~5 NUMERICAL VALUES ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ o ~ ~ ~ ~ ~ ~ ~ ~ ~ o ~ o 30 5 ~6 ABBREVIATIONS~ LETTER SYMBOLS ~ AND ACRONYMS ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ o30 6 TYPING FORMAT ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ o ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ o ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ o31 6.1 GENERAL TYPING PAGES'INSTRUCTIONS ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ o ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ o31 6.2 PAGE ARRANGEMENT.o ~ ~ ooo.o...oo ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ o ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ o32 6.3 HEADING AND TEXT ARRANGEMENT ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~

o.oooo'

~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ o32 6o4 BREAKING OP WORDS ~ ~ o ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ o32 6.5 ROTATION OF .. ~ ...o...o. .o..o.o.o......o...oo...

~ ~ ~ ~ o3 3 6.6 PRINTED OPERATOR AIDS .. ~.... ~......

~ ~ ~ ~ . ~ ~ .. ~...... ~ ~ ~ ~ . ~ .33 6.7 CAUTIONS AND NOTES ~ oo ~ o ~ ..o. .........oo..oooo'

~ ...35 6.8 USE OF POLDOUT PAGESoo.o.................. ~ oo ~ .oo.........36 6 ' USE OF OVERSIZED PAGES...........o........oo.........o....36 6 '0 USE OF REDUCED PAGES......................................36 7 UALITY OF REPRODUCTION ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ 36 8 REVISIONS TO EOPS ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ o ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ 36 FIGURES FIGURE 1 COVER SHEET.o..... .o.o...o..ooo..oooo. oooo...+.6 FIGURE 2 PAGE FORMAT. ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ .9 FIGURE 3 DOCUMENTATION SHEET............................13 TABLES TABLE 1 - ACTION VERBS..........................+.........28

QI 5-PR/PSL-2 Revision 2 March 1985 Page 5 of 36 INTRODUCTION 1.1 PURPOSE This document is intended to provide administrative guidance in the 1

preparation of Emergency Operating Procedures, (EOPs) ~

The CE Emergency Procedures Guidelines (CEN 152) shall be used as a format and technical guide during this preparation. I 1.2 SCOPE This guide applies to the preparation of all EOPs.

EOP DESIGNATION AND NUMBERING F 1'OVER SHEET Each EOP shall have a cover sheet (see Figure 1) which will identify the procedure and the authorized revision.* To identify the procedure, a title should be used that is sufficiently short and descriptive of the emergency condition or purpose for which the procedure is applicable.

2.2 PROCEDURE DESIGNATION The emergency operating procedure designator shall be EOP. The applicable unit shall be signified by the number 1 or 2 preceding EOP. Each unit shall have its own EOPs.

~ ~

~ I I'

~ ~

QI 5-PR/PSL-2 Revision 2 March 1985 Page 7 of 36 2.3 PROCEDURE NUMBERING A sequential number shall follow the procedure designa'tor and should consist of one or two digits.

Example I I I Sequence Number I I Procedure Designator I

Applicable Unit 2.4 REVISION NUMBERING AND DESIGNATION Revisions to EOPs shall follow the same flow path as Off-Normal and Operating procedures during the revision process.

One or two digits following the abbreviation "Rev" shall be used to designate the revision level of the EOP.

Example Rev 1 I I Revision Level I

Abbreviation To identify revisions to the text of an EOP, a change bar shall be located in the right margin, alongside the text change.

A 5 in the left margin shall indicate the text contains a licensing commitment and should not be revised without licensing approval.

I 2.5 PAGE IDENTIFICATION AND NUMBERING Each page of the procedure will be identified by:

a) The procedure designator and numbers.

b) The revision number.

c) An abbreviated title.

d) The page number, specified as "Page of "~ This information will be together and located in the upper right hand corner of each page. (See Figure 2) ~

QI 5-PR/PSL-2 Revision 2 Harch 1985 Page 8 of 36 2 ' PROCEDURE ACCESSIBILITY (1) All EOPs used in the Control Room shall be contained in a uniquely labeled or configured binder, i.e., Day Glow Orange, Red Striped, et c.

(2) Each procedure in the EOP binder shall have a major tab or separator labeled with the procedure number and abbreviated title.

(3)'ndividual procedures shall be broken down by minor tabs, i.e.,

Entry Conditions, Operator Actions, and Operator Aids.

I I Qi 5-PR/PSL-2 Revision 2 Harch 1985 Page 9 of 36

~=>l

~

I I V2" I

I I < I Ii I'trIRe - ~vice 1

>> I I

~ ~

I I I I RNVe I 4 I [2 IlNtttt tCtIt!NdtttltXttMRI I' I ll Pere@ IOOZ at 23

}2. Rasaoc Pcuer be ~Meed

~

I Rd I I I R) I I3 (came ua I I I I3 I I I I .I4~ I I I I I~ I I I Dat~cns Od I I). Im Rsecccc w RctIs I IP I le, Oepass stacch I l~ Sahecc ~

-} 2)a I I I i ( I (2 spaces)

~)

22 I

~,s I I I <P~) I I I i I J5'3 I I I I I I I I

I

>> i I I

I I I i I

I

-u2.-

I I

31 I I I I

324 I I I I i 34 I I I I I I I I 32 I I (

388 I' I I 4O I I  !

I I ( I I I I I

I' I I

j I I 4R I I i

.'Od I 32 Sd Ii2 cigure 2. Page Formac

Ql 5-PR/PSL-2 Revision 2 March - 1985 Page 10 of 36 3 FORMAT The following format is to be applied consistently for all EOPs.

3'1 PAGE FORMAT A dual-column format shall be used. The left-hand column is designated for operator actions, and the right-hand column is designated for contingency actions to be, taken when the expected response is not observed. A sample page format is presented in Figure 2.

3.2 PROCEDURE ORGANIZATION The following section headings will be used for all EOPs.

(1) title shall TITLE The be stated for operator association with the

'ENTRY CONDITIONS' (2) PURPOSE This section shall state the purpose of the procedure in sufficient detail for the operator to understand the procedure's scope and intent. The purpose section shall contain the expected operational mode at the procedures termiriation.

(3) ENTRY CONDITIONS The entry conditions shall include only those alarms, indications, operating conditions, automatic system actions, or other unique symptoms that the operator is to use in deciding to use the procedure.

(4) EXIT CONDITIONS (a) The exit conditions shall include the conditions that will allow termination of the procedure.

OR (b) The conditions that shall require branching to another procedure.

QI 5-PR/PSL-2 Revision 2 March 1985 Page ll of 36 (5) OPERATOR ACTIONS The operator actions shall be short, concise, identifiable instructions that give appropriate directions to the user.'6)

OPERATOR AIDS Graphs, Charts, Data Sheets, Tables, and Figures that could aid the operator during the use of the procedure.

3.3 SECTION NUMBERING Arabic numerals will be used for numbering sections and subsections in the decimal format. (See Figure 2, Page Format) 3.4 INSTRUCTION STEP NUiMBERING Instruction steps in a section or subsection shall be numbered and indented as follows:

1. Verify

a. Check .

The same step number scheme shall be used in both the right and left columns of the procedure.

3.5 OPERATOR AIDS NUMBERING Operator aids for a procedure shall be numbered sequentially and located immediately after the instruction step pages ~

WRITING INSTRUCTIONAL STEPS 4.1 CONVERSION OF CEVIL-152 TO PLANT SPECIFIC PROCEDURES 4~1 ~ 1 Preparation

a. The writer shall obtain and review the following plant specific technical information (EOP Source Documents)

QE 5-PR/PSL-2 Revision 2 March 1985 I

Page 12 of 36 Combustion Engineering Emergency Procedures Guidelines, CEN-152 latest revision (2) FUSAR St. Lucie Plant Unit 1 and Unit 2 (3) Technical Specifications for St. Lucie Plant Unit 1 and Unit 2 (4) The most correct revision of existing EOPs (5) As-Built Plant Drawings Writing Plant Specific EOPs from Combustion Engineering CEN 152 a~ The writer shall follow CEN 152 step-by-step, adding bracketed information where designated. Concurrently, the writer shall review appropriate EOP source documents

b. Plant specific technical information or analysis resulting from plant unique design shall be included in the EOPs.

c. Deviations from, and additions to the generic guidelines (CEN 152) will be fully documented on the Documentation Sheet (Figure 3) ~

The Documentation Sheet will be a part of the review process for procedure approval.

d. A copy of the Documentation Sheet shall be kept in the Q.C. Vault with the copy of the EOP and shall be revised when the procedure is revised.

QZ 5-PR/PSL-2 Revision 2 i!arch 1985 Page 13 of 36 EOP Ticle DOCVHENTATIOH SKEET ROP Hunbec Rove (Plane-Speritic Technical Guidelines) Page ct STEP JVSTIFICATIOH OF HlDegR CRH l52 DIFFKRRHCKS SICHATVRE/DATE I I I I I I I . I I

I I I

=I I.

I I I I I I I

I I I I I I I I I

I I I I I I I I

FICVRE 3

QI 5-PR/PSL-2 Revision 2 March 1985 Page 14 of 36 4.2 INSTRUCTION STEP LENGTH AND CONTENT 4.2.1 General Guides Instruction steps shall be concise and precise. General guides to be used in meeting these objectives are as follows:

(1) Each instruction step should deal with only one idea.

(2) Short, simple sentences should be used in preference to long, compound, or complex sentences.

(3) Complex evolutions should be prescribed in a series of steps, with each step made as simple as practicable.

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

(5) Por instructional steps that involve an action relating to three or more objects, the objects should be listed with space provided for operator checkoff.

(6) Limits should be expressed quantitatively whenever possible (refer to Subsection 5.5). I (7) Each step should have a check off to indicate that the following were either observed or performed:

(a.) -

Symptoms (b.) Automatic Actions (c.) Operator Actions (8) Mandatory sequence of steps's assumed unless otherwise stated.

(9) Identification of components and parts should be complete.

Ql 5-PR/PSL-2 Revision 2 March 1985 Page 15 of 36 (10) Instruction content should be written to communicate to the operator.

(ll) Expected results of routine tasks need not be stated.

(12) When actions are required based upon receipt of an annunciated alarm, the setpoint of the alarm should be given for ease of verification.

(13) When resetting or restoration of an alarm or trip is required, the expected results immediately following the resetting or restoration should be given if it would be beneficial to the operator.

(14) When considered beneficial to the operat'or for proper understanding and performance, describe the system response time associated with performance of the instruction.

(15) When system response dictates a time frame within which the instruction should be accomplished, prescribe such time frame. If possible, however, avoid using time to initiate operator actions'perator actions should be related to plant parameters.

(16) When anticipated system response may adversely affect instrument indications, describe the conditions that will likely introduce instrument error and means of determining if instrument error has occurred by using a ViOTE.

(17) When additional confirmation of system response is considered necessary, prescribe the backup readings needed.

(18) An instruction step shall not continue to a second page. If required start the step on a new page.

0 QI 5-PR/PSL-2 Revision 2 Harch - 1985 Page 16 of 36 (19) Steps that are performed more than once during a procedure shall be restated each time they are needed. Steps of this nature shall have a block to record conditions or time.

(20) Steps that imply continuous performance throughout the procedure should be prefaced with the appropriate action verb, such as monitor, maintain, or control. These steps also should have a block to record time and/or conditions, e.g., safety system parameter monitoring.

(21) Steps shall be numbered in the expected order of performance. If the order of performance is. not important or alternative actions are equally acceptable the steps shall be designated by bullets (0). If the logic OR is used both choices shall be designated by bullets.

(22) All steps shall be assumed to be performed in sequence unless stated otherwise in a preceding NOTE. Steps that are performed concurrently with other steps shall be. prefaced with a note to that effect.

(23) All,steps, whether individually or concurrently performed shall be within the capability of the minimum shift crew as specified in Technical Specifications. l (24) If steps can be performed by more than one job title they should be assigned by position, i.e., RCO "A", NWE, ANPS, etc. This should be done to reduce overlap of responsibility in the control room and inadvertent duplication of steps'.2.2 Ins truction Column The left-hand column of the dual-column format shall- contain the operator instructional steps. Expected indications should be presented in this column.

QI 5-PR/PSL-2 Revision 2 March 1985 Page 17 of 36 4.2.3 Contingency Actions Column Contingency actions shall be presented in the right-hand column of the dual-column format. Contingency actions are operator actions that should be taken in the event a stated condition, event, or task does not represent or achieve the expected result. The need for contingency action occurs in conjunction with tasks involving verification, observation, confirmation, and monitoring. Contingencies should be written so that the conditional statement precedes the action statement. "If. .Then......."

~ ~ ~ ~

Contingency actions should be specified for each circumstance in which the expected results or actions might not be achieved. The contingency actions should identify, as appropriate, directions to override automatic controls an'd to initiate manually what is normally automatically initiated.

4e3 USE OF LOGIC TERMS The logic terms ~RVO ~OR ~NOT ~IF IF NOT ~WHEN and THEN are often necessary to describe precisely a set of conditions or sequence of actions. When logic statements are used, logic terms shall be highlighted so that all the conditions are clear to the operator. Emphasis shall be achieved by using capitalization and underlining. All letters of the logic terms shall be capitalized and the words will be underlined.

,The use of AND and OR within the'ame action shall be avoided. When AND and OR are used together, the logic can be very ambiguous.

The dual-column format used equates to the logic; IF NOT the action in the left-hand column, THEN follow the action specified in the right hand column.

Use other logic terms 'as follows:

(1) When attention should be called to combinations of conditions, the word AND shall be placed between the description of each condition. The word AND shall not be used to join more than three conditions. If four or more conditions need to be joined, a list format shall be used.

QI 5-PR/PSL-2 Revision 2 March - 1985 Page 18 of 36 (2) The word OR shall be used when calling attention to alternative combinations of conditions. The use of the word OR shall always be in the inclusive sense. To specify the exclusive "OR," the following may be used: "either A OR B but not both."

(3) When action steps are contingent upon certain conditions or combinations of conditions, the step shall begin with the words IF or WHEN followed by a description of the condition or conditions, a comma, 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 condition.

(4) Use of IF NOT should be limited to those cases in which the operator must respond to the second of two possible conditions.

IF should be used to specify the first condition.

(5) THEN shall not be used at the end of an action step to instruct the operator to perform the next step because it runs actions together.

4.3 USE OF CAUTIONARY INFORMATION AND NOTES Cautionary information can be considered in two fundamental categories: those that apply to the entire procedure and those that apply to a portion or a specific step of the procedure. Those that apply to the entire procedure are called "PRECAUTIONS" and are covered in operator training. Those that apply to a portion of a procedure are called "CAUTIONS" and are placed immediately before the action statements to which they apply.

F Cautions shall extend across the entire page and shall be highlighted as shown in the Example CAUTION. This placement of cautions helps ensure that the procedure user observes the caution before performing the step. A caution cannot be used instead of an action statement. It should be used to denote a potential hazard to equipment or personnel associated with or consequent to the subsequent action statement.

QI 5-PR/PSL-2 Revision 2 Narch 1985 Page 19 of 36 Cautions should be used to alert personnel to displays based on secondary sensing modes. For example, when a light indicates a circuit is energized and not the position of a valve.

If additional information other than cautions is necessary to support an action statement, a NOTE should be used. A NOTE should present information only, not instructions, and should be located in the right-hand column as as close to the applicable action statement as possible.

(1) The following examples illustrate these instructions.

(a.) Example NOTE:

I NOTE I Break identification chart (Figure 1) may be helpful in evaluatin the situation

b. Example CAUTION:

• • • • • • • • • • • • • • • • • • • A********************A******x***************

CAUTION Overfeeding the Steam Generators may cause excessive cooldown.

• Do not exceed 75'F/Hr cooldown rate. *

• • • • • Kc************A********A***********************************

4.4 CALCULATIONS Mathematical calculations should be avoided in EOPs. If a value has to be determined in order to perform a procedural step, a chart or graph should be used whenever possible.

4+5 USE OF UNDERLINING .

Underlining should be used for certain headings, emphasis of logic terms and CAUTION.

QI 5-PR/PSL-2 Revision 2 inarch 1985 Page 20 of 36 4.6 REFERENCING AND BRANCHING TO OTHER PROCEDURES OR STEPS Referencing implies that an additional procedure or additional steps will be used as a supplement to the procedure presently being used. Referencing other steps within the procedure being used, either future steps or completed steps, should be minimized. The steps shall be restated in the procedure each time they are needed.

To minimize potential operator confusion, branching should be used when the operator is to leave one procedure. or step and use another procedure or step. Use the key words "GO TO." This will alert the operator to leave the present step and not return until directed.

Use quotation marks to emphasize the title of the referenced or branched procedure; examples: GO TO E-l, "Loss of Reactor Coolant", Step 5.2.

4.7 COMPONENT IDENTIFICATION With respect to identification of components, the following rules are to be follows:

(1) Equipment, controls, and displays will be identified in operator language (common usage). This language may not always match engraved names on panels but will be recognizable.

(2) When the engraved names and numbers on panel placards and alarm windows are specifically the item of concern in the procedure, the engraving should be quoted verbatim and emphasized by using all capitals.

(3) The names of plant system titles are emphasized by initial capitalization. When the word "system" is deleted from the title because of brevity and is understood because of the context, the title is still emphasized by initial capitalization.

\

qI S-PR/PSL-2 Revision 2 March " 1985 Page 21 of 36 (4) If the component is seldom used or it is felt that the component would be difficult to find, location information should be given in parentheses following the identification.

4.8 LEVEL OF DETAIL Too much detail in EOPs should be avoided in the interest of being able to effectively execute the instructions in a timely manner. The level of detail required is the detail that a newly trained and licensed operator would desire during an emergency condition.

To assist in determining the level of EOP detail, the following general rules apply'1)

For control circuitry that executes an entire function upon actuation of the control switch, the action verb appropriate to the component suffices without further amplification of how to manipulate the control device; for example, "Close FCV-07-1A, FCV-07-1B." Recommended action verbs are as follows:

(a.) For power-driven rotating equipment, use Start, Stop.

(b.) For valves, use Open, Close, Throttle Open, Throttle Close, Throttle.

(c.) For power distribution breakers, use Synchronize and Close, Open.

(2) For control switches with a positional placement that establishes a standby readiness condition, the verb "Set" should be used, along with the engraved name of the desired position. Positional placements are typically associated with establishing readiness of automatic functions and are typically named AUTO or NORMAL; for example, "Set the GLAND STEAM EXHAUSTER Control Switch in AUTO."

QI 5-PR/PSL-2 Revision 2 Harch 1985 Page 22 of 36 (3) For multiposition control switches that have more than one position for a similar function, placement to the desired position should be specified; for example, "Place FIRE pump SELECTOR Switch to TEST NO ~ 2 ~"

(4) Standard practices for observing for abnormal results need not be prescribed within procedural steps. For example, observation of noise, vibration, erratic flow, or discharge pressure need not be specified by steps that start pumps.

(5) Alignment instructions should contain all the following:

(a.) Each item requiring alignment is individually specified. (Do I

not reference previous steps I (b.) Each item is identified with a unique'umber or name.

(c.) The position in which the item is to be placed is specified.

(d.) The position in which the item is placed is verified.

4 ~9 PRINTED OPERATOR AIDS When informal,ion is presented using graphs, charts, data sheets, 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.

Data sheets should designate the frequency of use. If the action step must be repeated every 15 minutes, the data sheet should contain enough spaces to comply with the action.

4.9.1 Units of Measure Units of measure on figures, tables, and attachments should be given for numerical values that represent observed, measurement data, or calculated results. A slant line should be used instead of "per"; examples: f t/sec, lbs/hr.

QI 5-PR/PSL-2 Revision 2 Harch 1985 Page 23 of 36 4.9.2 Titles and Headings Capitalization should be used for references to tables and figures, titles of tables and figures within test material, and column headings within a table.

Examples: Refer to Figure 201 for

. as shown in Table 201, Equipment Power Supplies the ~ ~ ~ ~

4.9.3 Figure, Table, and At tachment Numbering Sequential arabic numbers should be assigned to figures, tables, and attachments in separate series. The sequence should correspond with the order of their reference in the text. The symbol "/7" and abbreviation, "No." are unnecessary and should,not be used. The number, alone suffices.

Examples: Figure 1, Figure 2, etc.

Table 1, Table 2, etc.

Attachment 1, Attachment 2, etc.

Page identification for attachments should consist of a block of information that identifies (1)'procedure number, (2) abbreviated title, (3) attachment number, (4) page number, and (5) revision number. Page numbering of attachments should meet the requirements of Subsection 2.5.

Section numbering for attachments should be in accordance with Subsection 3.3 ~

ql 5-PR/PSL-2 Revision 2

Ãarch 1985 Page 24 of 36 MECHANICS OP STYLE 5.1 SPELLING 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 followed for hyphenation.

(1) When doubt exists, the compound word should be restructured to avoid hyphenation.

(2) Hyphens should be used in the following circumstances:

(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-contained, 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 result 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

QI 5-PR/PSL-2 Revision 2 Harch 1985 Page 25 o'f 36 (g.) when a letter is linked 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 Punctuation should be used only as necessary to aid reading and prevent misunderstanding. Word order should be selected to require. a minimum of punctuation. When extensive punctuation is necessary for clarity, the sentence should be rewritten and possibly made into several sentences.

Punctuation should be in accordance'with the following rules.

5.3.1 Brackets Do not use brackets.

5.3.2 Colon Use a colon to indicate that a list of items is to follow. For example, Restore cooling flow as follows:

5.3.3 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 instruction is not too complex.

Use a comma after conditional phrases for clarity and ease of reading.

Example: WHEN level decreases to 60 inches, THEN start. pump .

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

QI 5-PR/PSL-2 Revision 2 March - 1985 Page 26 of 36 5.3.5 Period Use a period at the end of complete sentences and for indicating the decimal place in numbers.

5.4 VOCABULARY Mords used in procedures should convey precise understanding'to the trained person. The following rules apply.

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

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

(3) Use words that are concrete rather than vague, specific rather than general, familiar rather than formal, precise rather than blanket.

(4) Verbs with specific meaning should be used. Examples are listed in Table l.

(5) Equipment status should be denoted as follows:

(a.) Operable/operability These words mean that a system, subsystem, train, component, or device is capable of performing its specified function(s) and when all necessary attendant instrumentation, controls, electrical power, cooling or seal water', lubrication or other auxiliary equipment that are required for the system, subsystem, train, component or device to perform its function(s) are also capable of performing their related support function(s).

(b.) Operating This word means that a system, subsystem, train, component, or device is in operation and is performing its specified function(s).

QX 5-PR/PSL-2 Revision 2 March 1985 Page 27 of 36 (c.) Available This word means that a system, subsystem, train, component, or device is operable and can be used as desired; however, it need not be operating.

QI 5-PR/PSL-2 Revision 2 March 1985 Page 28 of 36 Table 1. Action Verbs Verb A lication Allow To permit a stated condition to be achieved prior to proce'eding, for example, "allow discharge pressure to stabilize" Check To perform a comparison with a procedural requirement "Check if SI can be terminated" 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 example, "close, valve V2530" Complete To accomplish specified procedural requirements, for example, "complete valve checkoff list 'A,'" "complete data report QA-1,"

"complete steps 7 through 9 of Section III" Decrease Do not use because of oral communication problems.

Establish To make arrangements for a stated condition, for example, "establish co'mmunication with control room" Increase Do not use because of oral communication problems.

Inspect To measure, observe, or evaluate a feature or characteristic for comparison with specified limits; method of inspection should be included, for example, "visually inspect for leaks" Lower -To decrease, as in setpoint, flow, pressure, etc.

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 V1114"

QI 5-PR/PSL-2 Revision 2 Harch - 1985 Page 29 of 36 Table 1 ~ Action Verbs (Continued)

Verb A lication Raise To increase, as in setpoint, flow, pressure, etc.

Record To document specified condition or characteristic, for example, "record discharge pressure" Set To physically adjust to a specified value an adjustable 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 to obtain a certain flow rate, for example, "throttle valve V6550 to 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, for example, "vent ~ .. pump" Verify To observe an expected condition or characteristic, for example, "verify discharge pressure is stable"

,I

~ c 0

QI 5-PR/PSL-2 Revision 2 March - 1985 Page 30 of 36 5,5 NUMERICAL VALUES The use of numerical values should be consistent with the following rules:

(1) Arabic numerals should be used.

(2) For numbers less than unity, the decimal point should be preceded by a zero; for example: 0.1 (3) 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.

(4) Acceptance values should be specified in such a way, that addition

.and subtraction by the user is avoided if possible. This can generally be done by stating acceptance values as 510'F maximum; 300 psig minimum; 580'o 600'F. For limits'xamples:

calibration points, statement of the midpoint and its lower and upper limits for each data cell would accomplish the same purpose; for example, 10 milliamperes (9.5 to 10.5). Avoid using +.

(5) Engineering units should always be specified for numerical values of process variables. They should'be the same as those used on the control room displays, for example: psig instead of psi.

5.6 ABBREVIATIONS, LETTER SYMBOLS, AND ACRONYHS 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 unquestionably clear to the intended reader. The full meaning of the abbreviation, other than the abbreviations listed in AP0010137, should be fully written before the first use of the abbreviation and whenever in doubt. Consistency should be maintained throughout the procedure.

)

QI 5-PR/PSL-2 Revision 2 March 1985 Page 31 of 36 Capitalization of abbreviations should be uniform. If the abbreviation is comprised of lowercase letters, it 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.

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 overused. 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 mathematical ideas.,

TYPIViG FOR.fAT 6.1 GENERAL TYPING INSTRUCTIOiVS For emergency operating procedures, the following general requirements are to be followed.

(1) Paper size should be 8-1/2 X 11 inches.

(2) Paper with preprinted borders should be used (See Figure 2)

(3) Procedures should be typed on a word processor.

(4) Prestige Elite 12, 82052 WP printwheel should be used.

~ l p QI 5-PR/PSL-2 Revision 2 March 1985 Page 32 of 36 6 o2 PAGE. ARRANGEMENT (1) Page margins are specified by the printed borders. Two type spaces are to be maintained between the text and borders. (See Figure 2)

(2) Page identification information (refer to Subsection 2.4) will be one line space below the top page printed border and one line space to the left of the right printed border.

(3) The 8-1/2 inch edges shall constitute top and bottom of pages and texts 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 HEADING AND TEXT ARRANGEMENT Block style, as illustrated in Figure 2, shall be used. First-level section headings shall be in full capita1s, with an underscore; second-level section headings shall be in full capitals without an underscore; and third-level section headings shall be placed in initial capitals without an underscore (refer to Subsection 3.3 for its numbering).

(1) Section numbers shall begin two spaces from the left-hand printed border.

(2) Three line spaces shalJ. be allowed between headings and respective text.

(3) Three line spaces shall be allowed between paragraphs.

(4) Text shall be typed using one-and-a-half line spacing.

6.4 BREAKING OF WORDS Breaking of words shall be avoided to facilitate operator reading.

QI 5-PR/PSL-2 Revision 2 March - 1985

'age 33 of 36 6.5 ROTATION OF PAGES If pages need to be rotated, these rules shall be followed:

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

(2) The page margins do not rotate.

(3) Page identification and numbering will not be rotated.

6+6 PRINTED OPERATOR AIDS Figures include graphs, drawings, diagrams, and illustrations. The following rules are established.

(1) The figure number and its title are placed three line spaces above, the figure field (refer to Subsection 4.9).

(2) The figure number and title should be of Prestige Elite 12, 82052 WP type" (3) The figure field must not violate specified page margins.

(4) The figure field should be of sufficient size to offer good readability (5) The essential message should be clear; simple presentations are preferred.

(6) Grid lines of graphs should be at least 1/8-inch apart; numbered grid lines should be bolder than unnumbered grid lines.

(7) Labeling of items within the figure should be accompanied by arrows pointing to the item.

QI 5-PR/PSL-2 Revision 2 March 1985 Page 34 of 36 (8) The items within the figure should be oriented naturally insofar as possible. For example, height on a graph should be along the vertical axis.

(9) In general, items'ithin the figure should be labeled. Typed labels should use Prestige Elite 12, 82052 WP printwheel.

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

(10) All lines in figures should be reproducible.

/

Tables should be typed using the following rules.

(11) Type style and size should be the same as that for the rest of the procedure.

(12) The table number and title should be located above the table field and three line spaces below preceding text.

(13)A heading should be entered for each column and centered within the column; the first letter of words in the column headings should be capitalized.

(14) Horizontal lines should be placed above and below the column headings; vertical lines, while desirable, are not necessary or required.

(15) Tabular headings should be aligned as follows:

(a.) horizontally by related entries (b.) vertically by decimal point for numerical entries (c.) vertically by first letter for word entries; however, run-over lines should be indented three spaces

QI 5-PR/PSL-2 Revision 2 Narch - 1 985 Page 35 of 36 (16) 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.

(17) 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 CAUTIONS AND NOTES All notes and cautions should be distinguishable from the rest of the text by using the following format.

(1) The applicable heading "NOTE" and "CAUTION" should be capitalized, centered, and placed three line spaces below the preceding text.

(2) The text of the note or caution should be block format, line-and-a"half spaced. The caution text should be indented five spaces from the left-hand printed margin and begun one-and-a-half line spaces below the heading. The text for notes should begin 10 spaces from the column dividing line.

(3) A caution statement should not continue to a second page, unless unusually lengthy.

(4) The right"hand margin of the text of the note or caution should be five spaces to the left of the right-hand printed margin.

(5) CAUTIONS shall be further highlighted by a'line of asterisks one-and-a-half spaces above the heading and one-and-a-,half spaces below the last line of the text.

(6) Examples are presented in Subsection 4.3,

QI 5-PR/PSL-2 Revision 2 8arch 1985 Page 36 of 36 6.8 . USE OF FOLDOUT PAGES When used, a foldout page is treated as a single page. It should follow the same format as a standard page 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.9 USE OF OVERSIZED PAGES Oversize pages should not be used. They should be reorganized or reduced to a standard page. If this cannot be done, a foldout page should be used.

6 '0 USE OF REDUCED PAGES Reduced pages should be avoided whenever possible. Final'ize of reduced pages should be standard page size. Reduced pages must be readable.

7 UALITY OF REPRODUCTION Reproduction shall be done on a standard copier, single-sided copy only.

All copies shall be checked to ensure .readability. All copies shall be checked to ensure that all four (4) borders are visible.

8. REVISIONS TO EOPs Revisions to EOPs resulting from ma5or changes in the plant design, Technical Specifications, CEN 152 or the Writer's Guide shall require verification valication and training of operators.

Item in Draft Safety Location of Response Evaluation Report

1. Page 4 Item (1) PGP Page 3 Sect 2.2.3

2. Page 4 Item (2) PGP Page 3 Sect 2.2.3

3. Page 4 Item (3) FGP Page 3 Sect 2.2.4

4. Page 5 Sect 2.2 Item 1. Writers Guide Page 15 Para 4.2 (18)

Page 35 Para 6.7 ( 3)

5. Page 5 Sect 2.2 Item 2. Writers Guide Page 11 Para 3.5

6. page 5 Sect 2.2 Item 3a. Writers Guide Fage 16 Para 4.2 (19)

Writers Guide Page 16 Para 4.2 (20)

7. Page 6 Sect 2.2 Item 3b. Writers Guide Page 16 Para 4.2 (21)

8. Page 6 Sect 2.2 Item 3c. Writers Guide Page 16 Para 4.2 (22)

9. Page 6 Sect 2.2 Item 4a. Writers Guide Fage 16 Para 4.2 (23)

10. Page 6 Sect 2.2 Item 4b. Writers Guide Page 16 Para 4.2 (24)

11. Page 6 Sect 2.2 Item 4c. Writers Guide Page 16 Para 4.2 (24)

32. Page 6 Sect 2.2 Item 4d.. Writers Guide Page 16 Para 4.2 (24)

13. Page 6 Sect 2.2 Item 5. Writers Guide Page 8 para 2.6

14. Page 7 Sect 2.2 Item 6. Writers Guide Page 36 Para 7

15. Page 7 Sect 2.2 Item 7. Writers Guide Page 36 Para 8

16. Page 8 Sect 2.3 Item 1. PGF Page 9 Sect 4.3

17. Page 8 Sect 2.3 Item 2. PGP Page . 11 Sect 5. 3

18. Page 8 Sect 2.3 Item 3. PGP Page 11 Sect 5.3

19. Page 8 Sect 2.3 Item 4. PGP Page 12 Sect 5;4

20. Page 8 Sect 2.3 Item 5. PGP Page ll Sect 5.3

21. Page 9 Sect 2.3 Item 6. Writers Guide Page 36 Para 8

22. Page 9 Sect 2.3 Item 7. Writers Guide Page 5 Para 2.2

23. Page 9 Sect 2.4 Item 1. PGP Page 16 Sect6.2.3

24. Page 9 Sect 2.4 Item 2a. PGP Page 15 Sect 6.2.2

25. Page 9 Sect 2.4 Item 2b. PGP Page 15 Sect 6.2.2

26. Page 9 Sect 2.4 Item 2c. P('P Page 15 Sect 6.2.2

27. Page 9 Sect 2.4 Item 3. PGP Page 15 Sect 6.1

C