ML20071Q738

Emergency Operating Procedures Generation Package

ML20071Q738
Person / Time
Site:	Prairie Island
Issue date:	05/31/1983
From:	NORTHERN STATES POWER CO.
To:
Shared Package
ML20071Q731	List: ML20071Q728 ML20071Q738
References
RTR-NUREG-0737, RTR-NUREG-737 GL-82-33, PROC-830531, NUDOCS 8306090239
Download: ML20071Q738 (16)

Text

.

t k'

EMERGENCY OPERATING PROCEDURES GENERATION PACKAGE PRAIRIE ISLAND NUCLEAR GENERATING PLANT NORTHERN STATES POWER COMPANY l

l l

l l

l' l

l l

l

! C306090239 830531

PDR ADOCK 05000282

! F PDR I

EMERGENCY OPERATING PROCEDURES GENERATION PACKAGE

1.0 INTRODUCTION

1.1 Purpose The purpose of the Procedures Generation Package is to describe the emergency operating procedure upgrade program at Prairie Island.

2.0 PROGRAM DESCRIPTION 2.1 General The Westinghouse Emergency Response Guidelines, Basic Revision, dated July 5, 1982, will be used for the initially drafted upgraded emergency procedures. As revisions are made to the Westinghouse Guidelines, revisions will be made to the upgraded emergency pro-cedures, as appropriate.

2.2 References

• Westinghouse Emergency Response Guidelines

• USAR e Technical Specifications e Existing Emergency Procedures e Plant Flow and Logic Diagrams 2.3 Writing Procedures e The upgraded emergency procedures will as closely follow the Westinghouse Guidelines as possible, while still inputting plant specific information. The attached Writers' Guide will be followed.

• While writing the plant cpecific emergency procedures, plant specific background information will be generated for all steps. This will help assure complete and accurate inclusion of plant specific and generic steps.

2.4 Verification The upgraded emergency procedures will be compared to the reference version of the Westinghouse Guidelines from which they are developed, in order to assess their com-pleteness, technical adequacy and adherence to the intended structure of the guidelines.

l

2 '. S Review .

' The upgraded emergency procedures will be reviewed by the operating shifts during normal requalification training sessions for technical and presentation accuracy. These comments.will be factored into revision prior to proce-dure implementation. Additional Plant Operations Committee review will, in accordance with plant adminis-trative directives, be performed before implementation.

2.6 Validation

~

The validation process for the emergency procedures will be performed as part of the Control Room Design Review process.

2.7 Training Since the procedure upgrade project has been underway for i

some months, considerable training on the revised proce-dures has been conducted and is currently in progress.

The basic areas addressed include:

1. Format familiarization

2. Scope of Procedure coverage

3. Content of Upgraded Procedures

4. Background Information for Upgraded Procedures l During the selection process of an appropriate format i

type, the operators were exposed to the selected format in detail. Advantages of the chosen format were illus-(

i trated as well as how to use the new format.

[ Beneficial training was received by the operators during l review of the draft upgraded emergency procedures. The operating crews were made part of the review cycle for two reasons; one, to get operator review and input early in the upgrade program; two, provide operator training on the content and the coverage provided by the new l procedure set.

l The operator review provides a good check on the presen-tation and content of action steps. Specifically, the operators comments provides further information on whether or not the particular action step is understood by the operator and that the operator can perform the action as stated. To perform this review the operators had to review the transient involved and the available background information. This type of review is excel-lent training. It also provides the operator with good training on the content of the procedures.

I l

Beginning in May, 1983, the draft upgraded procedures will be'used by the requal shifts at a simulator. This will provide the first good validation for the operator, that the procedures will work on accident conditions.

Comments received from the simulator training will be further input into the final draft of the procedures before implementation.

Additional classroom training will be given as final draft procedures are generated to provide further training on the procedures prior to implementation.

Early involvement of the operating crews in the develop-ment of upgraded procedures through review of draft .

procedures, simulator experience on the new procedures and classroom ^ training during normal requalification is providing excellent results in enhancing operator knowledge of the transients and procedures, and ultimately providing the best possible procedures for implementation.

WRITERS GUIDE FOR EMERGENCY OPERATING PROCEDURES

1.0 INTRODUCTION

1.1 Purpose The purpose of this section is to provide administrative and technical guidance en the preparation of Emergency Operating Procedures (EOPs).

1.2 Scope This writers guide applies to the writing of all EOPs.

2.0 EOP DESIGNATION AND NUMBERING EOPs 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 EOP shall be uniquely identified. This identification permits easy administration of the process of procedure preparation, review, revision, distribution, and operator use.

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 revi-sion. To identify the procedure, a descriptive title is to be used that also designates the scope.

2.2 Procedure Designation and Numbering 2.2.1 Main EOPs shall be designated by the letter E followed by a sequential number O, 1 . . .,

l e.g. E-0.

l 2.2.2 Procedures subordinate to the main procedures shall be designated by the letters ES (event specific) followed by the main procedure number and a sequential subset number .1, .2, . . .,

e.g. ES-0.1.

l i 2.2.3 Emergency contingency actions shall be desig-nated by the letters ECA followed by a sequential number 1, 2 . . ., e.g. ECA-1.

Page 2 2.2.4 Function restoration guidelines shall be desig-nated by the letters FR and the letter of the particular Critical Safety Function to which the guideline applies (S for subcriticality, P for RCS integrity, C for core cooling, I for RCS inventory, H for core heat sink, or Z for containment integ-rity) followed by a sequential number 1, 2 . . .,

e.g. FR-H.l.

2.3 Revision Designation and Numbering Two numbers following the abbreviation "Rev" will be used to designate the revision level of the EOPs, e.g. Rev. 01.

To identify the latest revisions to the test of an EOP, a vertical change bar in the left margin alongside the text change shall be used to indicate a change in the left column, and a bar in the right column. Previous revision change bars shall be deleted.

2.4 Page identification and Numbering Each page of the procedure will be identified by (1) the procedure designator and number, (2) the unit number and procedure title, and (3) the revision number and date.

This information will be at the top of each page as shown in Figure 2. The page number shall be specified "

of " and centered at the bottom of each page as shown in Figure 2.

3.0 FORMAT I

The following format is to be applied consistently for all EOPs.

! 3.1 Page Format

(

A dual-column format will be used. The left-hand column j is designated for operator actions, and the right-hand j column is designated for contingency actions to be taken when the expected response is not obtained. A sample page format is presented in Figure 2.

3.2 Procedure Organization The procedure will be sectionalized only by having the immediate operator action step numbers circled.

I

Page 3 3.3 Instruction Step Numbering Instruction stops will be numbered and indented as follows:

1 High Level Action Step

a. Detailed substep (1) Detailed substep For response not obtained (right hand column) the high level step number will not be used but che substep num-bering will be.

4.0 WRITING INSTRUCTIONAL STEPS 4.1 Instruction Step Length and Content Instruction steps will be concise and precise. Concise-ness denotes brerity; preciseness means exactly defined.

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

e Instruction steps should deal with only one idea.

e Short, simple sentences should be used.

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

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

, e For instructional steps that involve an action verb relating to three or more objects, the objects will be listed with space provided for operator checkoff.

l .

• Limits should be expressed quantitatively whenever i possible, e.g. 62 (60 to 64)%.

• Steps that are numbered or lettered should be performed l

l in sequence, unless otherwise stated. Steps marked with I a bullet (e) can be performed in'any order.

e Instruction content should be written to communicate to the user.

• Expected results of routine tasks need not be stated.

4.1.1 Instruction Column The left-hand column of the dual-column format will contain the operator instructional steps. The following rules are established for this column, in addition to'the general rules above.

6 Page 4

• Expected indications should be presented in this column.

• Operator actions in this column should be appro-priate for the expected indications.

4.1.2 Contingency Actions Column Contingency actions will 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.

Contingency actions will be specified for each cir-cumstance in which the expected results or actions might not be achieved. The contingency actions should identify, as appropriate, alternatives for achieving the desired result.

4.2 Use of Logic Terms The logic terms AND, OR, NOT, IE 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 will be highlighted so that all the conditions are clear to the operator. This highlighting will be done by capitalizing and underlining all letters of the logic terms.

The use of AND and OR within the same action shall be avoided.

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

Use other logic terms as follows:

• 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.

• The word OR shall be used when calling attention to l 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 I

l

- - , .-r _#

4 A

Page 5 e When action. steps are cont'ingent upon certain conditions or combination 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. [F is used for an unexpected but possible condition.

• 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 con-dition.

e 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 fundamen-tal 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 i

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 procedural steps to which they' apply.

l

Cautions shall extend across the entrie page and shall be highlighted as shown in Figure 2. This placement of I cautions 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 per-sonnel associated with or consequent to the subsequent instructional step.

If additional information other than cautions is nec-essary to support an action instruction, a NOTE should be used. A NOTE should present information only, not in-structions, and should extend across the entire page and should be placed immediately before the portion of the procedure to which it applies (see Figure 2).

4.4 Calculations Mathematical calculations should be avoided in EOPS. If

! a valve has to be determined in order to perform a pro-

{ cedural step, a chart or graph should be used whenever possible.

1 l

Page 6 .

~

4.5 Use of Underlining Underlining will be used for emphasis of logic terms only.

4.6 Referencing and Branching To Other Procedures Or Steps Referencing implies that an additional procedure or addi-tienal steps will be used as a supplement to the procedure being used. Referencing other steps within the procedure being used, either future steps or completed steps, should be minimized. When only a few steps are involved in the referencing, the steps should be stated in the procedure wherever they are needed.

To minimize potential operator confusion, branching will be used when the operator is to leave one procedure or step and use another procedure or step. Use the key words "go to". Therefore, the operator will know to leave the present steps and not return until directed.

Use capitalization to emphasize the title of the refer-enced or branched procedure; e.g., Go to E-1, LOSS OF REACTOR COOLANT, STEP 20.

4.7 Component identification With respect to identification of components, the follow-ing rules are to be followed:

• Equipment, controls, and displays will be identified in operator language (common usage) terms. These terms may not always match engraved names on panels but will be complete. .

• When the engraved names and numbers on panel placecards and alarm windows are specifically the item of concern in the procedure, the engraving should be quoted verba-tim and emphasized by using initial capitalization and quotation marks.

• The names of plant system titles are emphasized by initial capitalization. When the word " system" is deleted from the title because of brerity and is under-stood because of the context, the title is also empha-sized by initial capitalization.

• If the component is seldom used or it is felt that the component would be difficult to find, location infor-mation should be given in parentheses following the identification.

T., 7 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 de-tail that a newly trained and licensed operator would desire during an emergency condition.

Infrequently performed or complex evolutions shall be delineated with a high level of detail. Routine tasks should not require amplifying instructions.

4.9 Printed Operator Aids 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.9.1 Units of Measure Units of measure should be given for numerical values that represent observed, measurement data, or calculated results. A virgule (slant line) should be used instead of per, e.g. ft/sec.

4.9.2 Titles and Headings Initial capitalization should be used for refer-ences to tables and figures, titles of tables and figures within text material, and column headings within a table.

l l

Examples: Refer to Figure 1 for . . .

. . . as shown in Table 2, Equipment Power Supplies, the . . .

4.9.3 Figure and Table Numbering Sequential arabic numbers ~hould be assigned to figures and tables in separate series. The se-quence should correspond with the order of their reference in the text. The symbol "#" and l abbrviation "No." are unnecessray and should not I

be used.

Examples: Figure 1, Figure 2, etc.

Table 1, Table 2, etc.

c--+-- v - . - - . - - - - - - _ _ _ _ . _ _ _ _ _ _ _ . _ _ _ _ _

Page 8 Page identification should consist of (1) proce-dure numbar, (2) figure or table number, (3) page number, and (4) revision number.

5.0 MECAHNICS OF 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 Hypenation Hyphens are used between elements of a compound word when usage calls for it. When doubt exists, the compound word should be restructured to avoid hyphenation.

5.3 Punctuation Punctuation should be used only as necessary to aid read-ing and prevent misunderstanding. Word crder should be selected to require a minimum of punctuation. When exten-sive punctuation is necessary for clarity, the sentence should be rewritten and possibly made into several sen-tences. 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 or suboridnate steps are to follow a high level action step.

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 in-struction is not too complex.

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

Page 9 -

5.3.4 Parentheses Parentheses should be used to indicate alternative items.

5.3.5 Period Use a period at the end of sentences and for indi-cating 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.

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

• Use words that are concrete rather than vague, speci-fic rather than general, familiar rather than formal, precise rather than blanket.

• Define key words that may be understood in more than one sense (see Table 1).

• Verbs with specific meaning should be used and used consistently.

TABLE 1 Word Application Available This word means that a system, subsystem, train, component, or device is operable l and can be used as desired; however, it need not be operating.

• Locally This word means to take an action outside the control room.

i Manually This word means to perform an action in the control room.

Operable / These words mean that a system, subsystem, operability train, component, or device is capable of performing its specified function (s) in the intended manner. Implicity in this definition is the assumption that all support systems for the system, subsystem, train, component, or device are operable.

Operating This word means that a system, subsystem, train, component, or device is in opera-tion and performing its specified function (s), and conditions do not pre-vent it from maintaining that service.

_ . . _ - ~. . . _ _

Page 10 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, e.g. O.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.

.i e Acceptance values should be specified in such a way that addition and subtraction by the user is avoided.

. This can generally be done by stating acceptance values as limits, e.g. 50 (45 to 55)%-

e Engineering units should always be specified for numerical values of process variables and should be

, the same as those used on the control room dispaly.

5.6 Abbreviations 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 necessry to save time and space, and when their meaning is unquestion-ably clear to the intended reader. Consistency should be maintained throughout the procedure.

Capitalization of abbreviations should be uniform. The period should be omitted in abbreviations except in cases where the omission would result in confusion.

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 and acronyms should not be overused.

I e

3 t

E-O R:v. 1 Retention: 5 Yrs.

UNIT 1 REACTOR TRIP OR SAFETY INJECTION

.I OPERATIONS COMMITTEE REVIEW:

REVIEWED BY: DATE APPROVED BY: DATE i

I

! Page 1 of 11 l

l FIGURE 1 COVER SHEET EXAMPLE l ---, . . . _ . . _ _ . - _ _ . . _ _ _ _ _ . _ . . _ . . - . . - _ - _ - . - _ . . . . -

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

Guadeline series Guideline ::tle Revision nu::ber/date and num=er

• eft-hand eclumn

- casic action sequence

% === a he M Rigne-hand column

~

ntingencies and 15-0.1 REACTOR TRIP RECOVERY .,.ansitacns 1 5.ev. 19e1 --

a CAC"ICN-critical and H STEP l l ACTION / EXPECTED SE5PONSE l l RESPONSE NOT OSTAlteED H precautaonary infcrmation fanp*m 11SIscruanon occurs at any tone. immennerely go to E 0, RL4 CTOR TRIP OR SAFETY L4]ECTION STEP 3.

- NOTE - advisory 8001E FoMour page shouM be oPen. iniormation 1 Qank ICS Aserees T __

s. T- _ _ .. . - DECREASING 70 a. oume s. .

roo op

~

U **'"**"*""*'""

!fign-level action

"" step - bold type manuedy asen steem genererer PORVs.

g ., _ Oeta:1ed steps - how to do nign-level

b. Temeerature - LIIS THAN gr 'F 2 acta:n

1) Verify feedester Mow conmd vehus - CL0so es

c. Temooremre - STAalu2I5 AT c. Stas dumsong steem.1 g8 'F casessen connnues. ~NEN dose man steeneme isosonen verves. ,

.0ntingency action -

2 losehemb Afgr flee, wnen expected

,, g g response not Obta ned

6. Aligm AM verwes - CPEN 04 CLOSE A5 APM0PRtATE 'd' Transition to anct..e

c. Verrfy AM flow c. J AM 8 tow g verified, g go guidel ne - numce; to R-H.1. LOSS OF SECONDAa7 and :: tie HEAT SINK.

3 Venfy A8 Cassed tems fedy inserved. f awo or more contros rods g N#y ciertos. NEN anergency borate go noen for escfi contres rod not %dy N Ogic statement emonast:ed - :7 l toe == wova e m w,

-,u ,y- -

to=-.,,.,.,,,. "-

so cme m m e w ,,

~ t-a o.aw m.au w.

'73 $48p psaH .p.nfle Se g es -

I t e6 7 Plant-specif c data recuired - f:ctncte num=er Tcctnotes - define , Page number -

requ; red plant- accounts for all specific data pages Figure 2 Format Example

~

O.

Battelle Report

=

Y a

/ 1 g i l- I

-) i 5

f

-; 1 i ._ .

f -

g l I ""

F.

T r\

Nbw England Marine Research Laboratory 1

i,,

e

.\

5 m _ _ _ _ _ _ _ . _ - - . - _ . - -