Text

Emergency Operating Procedures Writers Guide
	ML20114D508
Person / Time
Site:	Hope Creek
Issue date:	12/18/1984
From:	; GENERAL PHYSICS CORP.
To:	;
Shared Package
ML20114D498	List: ML20114D496; ML20114D506; ML20114D508;
References
	PROC-841218, NUDOCS 8501310385
	Download: ML20114D508 (30)
	v • d • e

. ..

EMERGENCY OPERATING PROCEDURES WRITER'S GUIDE Prepe. red for:

Public Service Electric and Gas Company Hope Creek Generating Station l

December 18, 1984 l

GENERAL PHYSICS CORPORATION COLUMBIA, MARYLAND ,

0 6

.. l l

TABLE OF CONTENTS PAGE

1. In trod u ctio n . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . I 1.1 P ur po se . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . I 1.2 Scope ............................................I

2. EOP Designation and Numbering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 2.1 D ef ini tion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 2.2 EOP Identi fication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 2.3 E OP Con ten t s . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 2.4 Procedure N umbering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 2.5 R e vision Num bering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 2.6 Revision Identification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 2.7 Page Identification and Numbering . . . . . . . . . . . . . . . . . . . . . . 4

3. Procedure Form at . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 3.1 - Format..........................................3 3.2 P age l, ayou t . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

4. Flowchar t G uidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 4.1 - Identification Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 4.2 C on t en t . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

'4.3 S ymbol C oding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 4.4 Nonenclature/ Punctuation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 4.5 Functional Flow and Branching . . . . . . . . . . . . . . . . . . . . . . . . 10 4.6 R eadability/S tyle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 47 E ase o f U se . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 1 4.8 S t ep N um be ring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 1 1

r. ,-

5 Flowchart Instruction Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 5.1. Flowchart Instruction Step I.cngth and Content . . . . . . . . . . . . 13 r 3.2 . Use of L ogic Terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 53 Co m m an ds . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 5.4 Component Identification . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 5.5 L evel of De tail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

6. Mechanics of S tyle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 6.1 S pelling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . > l 7 6.2 H yphenation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 6.3' Punctua tion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 6.4 Vocabulary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 6.5 ' N ume rical V alues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 6.6 . Abbreviations, Letter Symbols, and Acronyms . . . . . . . . . . . . . 19

- Attachment 1 Sample Title Page Attachment 2 Sample Table of Contents Attachment 3 Flow Chart Symbols Attachment 4 Abbreviation List 11

1 l

l SECTION 1. INTRODUCTION l

1.1 Purpose l The purpose of this document is to provide specific, detailed administrative instructions for the preparation of the EOPs from the Hope Creek PSTG to insure j consistency of format, usage and technical presentation among all EOPs and revisions.

1.2 Scope This writer's guide is applicable only to the production and revision of the Hope Creek EOPs.

l l

l 1 1 t

-l

..._.____.__...________________.___._________________________-___...__J

[

t

+

r SECTION 2. EOP DESIGNATION AND NUMBERING 2.1 _

Definition EOPs are procedures that provide the operator with directions to mitigate the

. consequences of a broad range of accidents and multiple equipment failures without the I '

need to diagnose specific initiating events and to return the plant to a stable condition.

2.2 - EOP Identification Each EOP shall be uniquely identified. This identification permits easy

~-administration of the process of procedure preparation, review, revision, distribution, and operator use. A descriptive title is to be used that also designates the scope.

2.3 EOP Contents -

EOP control and contingency procedures shall have a Title Page, a Table of

~

Contents page, and will contain information (1) to identify the procedures, (2) to identify the authorized revision, (3) to define the purpose of the procedures, (4) to document 'the procedure references, (5) to provide definition of -key words--and, (6) to delineate '

procedure responsibilities.

The procedure steps will be provided in the form of a flowchart.

4 The EOP support procedures (i.e., bypassing interlocks, special equipment lineups, etc.) will be written in the System Operating Procedure (SOP) format, in accordance with

' OP-AP.22-001 (Q), Preparation and Approval of Operations Department . Procedures, Attachment 2.

t 2.4 Procedure Numbering The numbering scheme described below shall be used for all Emergency Operating procedures. The form shall be AA-BB.CC-XYZ(M), and is described below:

2

p u

f. .

, AA - This group identifies the originating department which is also responsible for all changes and reviews, as necessary. For EOPs the Operations Department

[

designator of "OP" shall be used.

1 -

! _ BB - This category is used to identify the procedure type. For EOPs, the "EO"

designator shall be used.

l '

l: .

CC - This field is used to determine the applicable plant system designator. Since l I

no system is applicable to EOPs, the designation "ZZ" shall be used.

XYZ - Sequential procedure number. The EOPs will be sequentially identified in three distinct groups. The 100 series (i.e., 101, 102, etc.) will include the basic f control procedures- (i.e., .R/PV Control, Containment Control, etc.). The 200 series will contan the contingency procedures (i.e., Level Restoration, RPV ;

- Emergency Depressurization, etc.). The 300 series will contain the required l X support procedures (i.e., bypassing interlocks, special equipment ilneups, etc.). _

r i

. (M) - Denotes classification of the procedures. Safety-related procedures and ,

l- procedures on equipment effecting safety-relating systems are designated by the letter "Q". ;

t Utilizing this scheme, the EOP identification will be:

OP-EO.ZZ-101(Q) ;

i !

2.5 Revision Numberina ,

e ,

Two digits following the "Rev" abbreviation will be used to designate revision f

' levels after approval by the Operations Manager.

Rev 01 r t

3

, 3-

m -

s

. 1 All prior revisions (i.e., development phase) will be identified by using sequential alphabetical designators.

RevA 2.6 Revision Identification I

Changes incorporated after Rev 01 will be described in the " Remarks" section of the procedure cover sheet.

2.7 Page Identification and Numbering The procedure number shall be in the upper right and lower left corners of each page, including attachments and tables. Additionally, the bottom center of the page ,

shall have the page number, and the bottom right corner will identify the revision number.

All pages of the procedure text shall be numbered sequentially with the last page of the text being identfled "(LAST PAGEF Just to the right of the page number.

All attachments and tables shall be numbered independently with the number

~

.. appearing at the top and bottom of the page. Each attachment / table shall use the page numbering style X and Y, where X is the page number and Y is the total number of pages :

,making up the " attachment / table. The attachment / table number shall appear on all applicable pages.

i l

s .

m e

SECTION 3. PROCEDURE FORMAT 3.1 Format Each procedure shall be prepared in accordance with the format described below, with the various elements of the procedure arranged in the sequence shown.

- The Title Page shall be in the format shown in Attachment I and shall include the procedure number, title, and revision. The title shall be a descriptive phrase to identify the main purpose of the proedure. Also, a remarks section may be used to summarize the changes made in the current revision.

The Table of Contents shall always be page 1 of the procedure and shall be in the format shown in Attachment 2. The page number of each section and each major division should be listed. 'l The procedure .shall include each of the below listed elements in the order. j specified

a. Purpose Gection 1.0) - A clear statement defining the intent and scope of 1 the procedure.

b. References $ection 2.0) - A comprehensive list of all references used to develop the procedure including name,: numbers, and revision .of each document when applicable. If there are no references, the. word "None" shall be entered in the section.

i

c. Definitions $ection 3.0) - A list of terms needing clarification as to how they apply within the procedure. If there are no definitions, the word

! "None" shall be entered in the section.

d. Responsibilities Gection 4.0) - A brief summation of those duties, by position title, necessitated by the procedure.

5

_-_n

e-4*

e. Procedure (Section 5.0) - For the 100 and 200 series of the EOPs, this will be the flowchart. For the 300 series, this section will contain the written procedural steps.

f. Attachments and Tables - Those supplements, checkof f sheets, etc., needed to implement the procedure or provide a concise way of transmitting information. Attachments may include forms, diagrams, special instructions, etc.

Tables may include lists and tabulations. Attachments and tables shall be added at the end of the procedure text in the order mentioned within the text. They shall also be listed in the Table of Contents.

Forms, where used, shall be included and identified in the procedure as an

j. attachment. A form developed for a particular procedure should have a

, . designator that pertains to that procedure (e.g., Form OP-EO.ZZ-101(Q)-1).

( 32 Page Layout .

All procedure pages should be 81/2" X 11" in size. The left hand margin of all text shall have adequate space (approximately 3/4 inch) to permit hole punching without obilterating copy.

6 c.

r- -

SECTION 4. FLOWCHART GUIDELINES 4.1 Identification Information 4.1.1 Information Suf ficiency i

a. The procedure number and title shall appear in the lower right hand corner of each flowchart,

b. . The date of revision and revision number shall appear in the lower right hand corner of each flowchart.

4.1.2 Information Consistency

a. The location / format of identification information shall be consistent for each flowchart.

4.2 Content 4.2.1 Clarity and Conciseness l

a. Flowpath actions shall be written as short, concise statements.

b. Contingency action statements shall be clear and concise, ,

'l

c. Questions in decision steps shall be written clearly.

d. Adverbs and articles shall be used as little as possible in flowpaths.

e. The use of double negatives shall be avolded. 1 4.2.2 Consistency of Terminology

a. Terms within and among flowcharts shall be consistent.

i 7 .

1

i

. l

, b. Caution statements shall not deliver commands.

j c. Action blocks shall contain action instructions as specific verbs.

d. All decision steps shall require a choice of one of two opposite possibilities, i.e., yes/no, high/ low, etc.

4.2.3 Complexity

a. The number of actions called out per action block shall be minimized.

b. Decision steps using "and/or" logic should be avoided.

c. Numerous objects or actions appearing in an action block shall be listed and bulleted for ease of identification.

4.2.4. Sufficiency and Appropriateness of Information

a. Any graphs or tables that are included in the flowcharts shall be.

adequate for readability and extraction of values,

b. Values utilized in the flowcharts shall correspond to the values that the operator will obtain from the plant Instrumentation.

/

4.3 Symbol Codins 4 3.1 Standardization - l

a. Flowchart symbols shall be those that are listed in Attachment 3.

4.3.2. Ease of identification 8

1

r.

r .

p b a. Major symbol blocks (action steps, decision steps, retainment steps) shall be readily detected and discriminable.

b. Symbols shall be used to ald the operator in finding the correct entry and exit point into and out of a flowchart (Procedure-to-Procedure symbols), and they shall be adequately coded for ease of identification.

c. Symbol coding shall be used consistently.

. 4.4 Nomenclature / Punctuation 4.4.1 Use of logic words

a. Conditional statements shall be written so that the description of the condition appears first, followed by the action instructions.

4.4.2 Abbreviations

a. Abbreviations shall be used with discretion and shall be supported by '

an abbreviation list included as Attachment 4.

b. Abbreviations . shall be used consistently within and among flowcharts.

l 4.4.3 Punctuation

a. Punctuation shall be used in flowcharts to aid the user.

[_ L4.4.4 Methods of Emphasis

a. Conditional statements shall be underlined.

b. Commands shall be bold type.

p 9 E

~

l

> 1 4.5 Functional Flow and Branching 4.5.1 Grouping of Paths ;

a. The spacing of paths shall be sufficient to allow operators easy and accurate movement through flowchart branches.

b. The direction of flow shall be apparent through the use. of directional arrows.

4.5.2 Flowpath Branching

a. All exits from a flow path shall be designated through the use of the symbol presented in Attachment 3. All exit arrows will be directed to the right side of the procedure and will include the procedure number and step to be entered.

b. All entries into a flowpath when directed from other flowpaths shall be designated through the use of the symbol presented in Attachment 3. All entrances shall be from the lef t side of the procedural step, and shall contain the procedure number and step which was exited. ,

4.6 Readability / Style 4.6.1 Character Size

a. Character size shall be sufficient to permit rapid and accurate !

recognition under conditions of normal and emergency lighting.

1 4.6.2 Character Style .

I

a. The character style shall meet human factors standards.

I 10 L.

I l

b. The spacing between letters and words shall provide for rapid and accurate character recognitions 4.6.3 Contrast a.~ To ensure' adequate contrast, dark (black) characters on a light (white) background shall be used. I 4.6.4 Reproduction Clarity l

a. Flowchart copies will be complete and of high quality.

4.6.5 Glare

a. Protective coverings (or display surfaces) for flowcharts shall minimize the possibility of glare.

4.7 Esse of Use i 4.7 1 Verification provisions 1 l

a. The flowcharts shall be designed to permit tracking of movement i

' through its branches.

4.7.2 -Size of Flowcharts

a. Flowcharts shall be sized to permit ease of use, 1

I 4.8 Sten Numberina i i

1

~4.8.1 Muttiple branch EOPs )

l

a. ' Multiple branch procedure steps will use the AA/B-C format:

11

i f

1. AA - will be the procedure designator.

l

2. B - will be the branch of the procedure.

3. C - will be the sequential step number.

I

4. Example - Reactor Control, level branch step 3 RC/L-3.

4.8.2 Single Branch EOPs ;

1 i a. Single branch procedure steps will use the AA-B format.

1. AA - wl!! be the procedure designator.

2. B - will be the sequential step number.

t

3. Example - Level Restoration step 5 - LR-5.

4.8.3 . Place Keeping i

l

a. A L- will be placed next to each step as a place keeping aid to tte operators.

I 12

l 1

l b

SECTION 5. FLOWCHART INSTRUCTION STEPS

31. Flowchart Instruction Sten Length and Content .

1 I

Flowchart instruction steps will be succinct and precise. General rules to be used in meeting these objectives are as follows: 7 i

a.- Instruction steps should deal with one idea only.

1

b. Short, simple sentences should be used.

- c. Complex evolutions should be described in a series of steps, with each step - j made simple.

d. Objects of operator actions should be specifically stated,

e. Limits should be expressed quantitatively.

f. Identification of components and parts should be technically correct and complete. *

g. When actions are required based upon receipt of an annunciated alarm, the j

' alarm set point should be listed. l l

l

h. If required for proper understanding, describa the system response time j associated with performance of the instruction. 4

1. -When system response dictates a time' frame within which the instruction p

must be accomplished, denote the time frame. However, avoid using time i to initiate operator actions, as operator actions should be related to plant

, t parameters.

P 13 1

e l

l l

J. When anticipated system responses may adversely affect instrument j indications, (1) describe the conditions that will likely introduce instrument error and, (2) describe a means of determining if instrument error has occurred by using a CAUTION. j

k. When additional confirmation of system response is considered necessary, prescrlhe the backup readings to be made.

5.2 - Use of Loalc Terms When logic statements are used, logic terms will be highlighted so that all the conditions are clear to the operator. Highlighting will be achieved by underlining. Use logic terms as follows: ;

a. Avoid the use of AND and OR within the same action. When AND and OR are used together, the logic can be very ambiguous,

b. 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 four conditions. If five or more .l conditions need to be joined, a list format shall be used. l

c. . 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. H

d. - When action steps are contingent upon certain conditions or combinations ;

e, of conditions, the step shall begin with the words IF,or WHEN followed by a description of the condition or conditions, a comma, and the word THEN followed by the action to be taken. WHEN is used for an expected I condition. ,lf,is used to determine the specific course of action based upon plant conditions.

2

e. Use of IF NOT should be avolded.

1 14 1

j l

f, . I s 5.a Commands Commands shall be highlighted by the use of bold type.

3 5.4 Component Identification

'L

' .The folloplag ru'es are to be foll' owed with regard to component identification:

s

a. Equipment, controls, and display will be identified in operator language (commt,n usage) terms.

s I

_ b. When the engraved names and numbers on legend plates and alarm windows are specifically the item of concern in the procedure, the engraving should be quoted verbatim.

c. If the component is seldom used or difficult to locate, location information should be given. If the control is located on a local pnel, give local panel number (example 10C076).

1.evel of Detail 5.5 The level, of detali required is the detail that a newly trained and licensed operator would desire during;an emergency condition. To assist in determining the level

^

of detail, the following cules apply:

- a. For control circuitry that, executes an entire function upon actuation of the control switch, tne action verb appropriate to the component suffices

~

without further amplification of how to manipulate the control device; recemmended action verbs to be utilized are:

- 1. For power-driven rotating equipment: Start, Stop

2. For valves: Open, Close, Throttle Open, Throttle Close, Throttle

.3. Eor power distribution breakers: Synchronize and Close, Trip.

o 15

.y .

-1

. . , . , [

.. . . . .- .. . - . - . .. . . . ~. . .-...= . .

e

' /

n.

,e..

t

- b. . - For multiposition control switches that have more than one position for a-similar function: placement to the desired position should be specified ;

?

7 5.<

! , s S

?r a

Y.

W

. T:

_t

. 7 t

.h

~

16-

" b' E' tI *S'99" $ g- 4:- g-n, * -

r w y gae-- y9e y-eq 7,,-., e,.mrg,9_gyy,q,g,g 7,, ,g , ,,p9 ,,,gg,_g +, g,g,,_ ,,,, p.,. .,,,,,4p-,

d e

SECTION 6. MECHANICS OF STYLE 6.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.

t 6.2 Hyphenation Hyphens are used between elements of a compound word when usage calls for it.

The following rules should be followed for hyphenation:

a. ~ When doubt exists, the compound word should be restructured to avoid -

hyphenation.

b. Hyphens should be used in the following circumstances

1

1. In compounds with "self" -

2. When the last letter of the first word is the same vowel as the first .

letter of the second word.

. 3. When misleading or awkward consonants would result by joining the words.

4.~ To avoid confusion with another word. -

When a letter is linked with a noun. -

~

- 5.

- 6.3 .- Punctuation Punctuation : should be used only .as necessary to . aid reading and _' prevent

misunderstanding. Punctuation should be in accordance with the following rules:

6.3.1 Brackets Brackets are not to be used.

E 17 w' w +- - - eg-b-g-- p- * *+4 t-* -'* -7T 9 @'=P - - '

47- N* B8T---' --

WP+----- - N F tw-

9 6.3.2 Colon Use a colon to indicate that a list of items is to follow.

6.3.3 Parentheses Parantheses shall be used to indicate system designators.

6.4 Vocabulary Words used in procedures should convey the proper understanding to the trained person. The following rules apply:

a. Utilize simple words (i.e., short words of few syllables).

b. Utilize common usage,

c. Utilize words that are concrete rather than vague, specific rather than general, familiar rather than formal, precise rather than blanket.-

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

e. Verbs with specific meanings should be used.

- 6.5 ~ Numerical Values l

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

I

a. Arabic numerals should be used.

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

c. The . number of significant digits should .be equal to the ' number of 7

significant digits available from the display (and required by the necessary _

, reading precision of the operator).

d. Acceptance values should be specified in such a way that addition and.

subtraction by the user is avoided if.possible. This can be done by stating a acceptance values as limits.

e. . . Engineering units should always .be specified for . numerical values .of

- process variables,~ and should be consistant with the units predominantly displayed to the operator.

L18

_ ..., -.-.e. ,_- .-,. .. .., -- _. . . . .. _ . , - . + .

6.6 - Abbreviations, Letter Symbols, and Acronyms The use of abbreviations should be minimized. Abbreviations may be used where necessary to save time and space, and when their meaning is unquestionably clear to the

- intended reader. Consistency should be maintained throughout the procedure.

/

l-l.

t i.

[_.

19

ATTACHMENT 1 Sa4nple Title Page l

1

HOPE CREEK GENERATING STATION OP-EO.ZZ-Remarks:

L Prepared By:

Date Reviewed By:

Operating Engr - Hope Creek Date ALARA Review:

Radiation Protection Dept. Date Reviewed By:'

SQAE- Date SORC' Review:

Chairman Date . Mtg. No.

Approved By:

Operations Mgr - Hope Creek Date e,

4 -

OP-EO'ZZ-

. _ Rev.

i~ _

ATTACHMENT 2 Sample Table of Contents l

I l

i

_ . - . . . . . .-- . . - . = _ _ - .. .. _ . . .

OP-EO.ZZ-d TABLE OF CONTENTS SECTION TITLE PAGE 1.0 PURPOSE 2

2.0 REFERENCES

2 3.0 DEFINITIONS 2 4.0 ~ RESPONSIBILITIES 4 5.0 PROCEDURE- (see flowchart)

ATTACHMENTS None

(

t k

r e

i r

r 4

5

- OP-EO.ZZ- - 1 Rev. ,

gg:.

_ -. .: J._. ..__...-.,_.1...._,,.. . _ _ . . . . . = . . . . . . . ~ . , _ . . . - _ - _ . . . . . . , .

OP-EO.ZZ-ATTACHMENT 3 Flow Chart Symbols l

t i

I

.o a

ENTRY CONDITION -

Contains the condition which requires entry into, and execution -

of, the appropriate procedure (only applies to 100 series).

)

l I

ACTION STEP -

Contains the procedural actions to be implemented. It may i also be used to define contingency action steps, i.e., IF_ . . l

- THEN.... )

i l

I RETAINMENT STEP -

Contains information and/or contingency action conditions which must be retained in the operator's memory throughout the execution of the procedural steps which follow.

DECISION STEP -

Contains interrogative information, the results of which will determine future actions.

EXIT ARROW -

N Requires the operator to leave the flowpath at that point. If OP-EO. ZZ-XXX / required, it will also contain the procedure number and/or step WW-Y which then must be entered.

EXECUTE CONCURRENTLY -

Requires the operator to enter the designated procedure and

} perform the stated actions while continuing in the existing flowpath.

ENTRY ARROW -

Designates the point at which the procedure is entered when O P- EO. Z E -XXX) directed by the procedure step listed within the arrow.

~

OPERATOR CAUTION -.

Designates that a specific caution is applicable to the step.

XX The number (s) contained within the circle correspond to an explanation of the caution which is provided on the procedure.

r OP-EO.ZZ-ATTACHMENT 4 Abbreviation List

f4=

OP-EO.ZZ-I ADS -