ML20215J264

From kanterella
Jump to navigation Jump to search

Procedure AP.2.24, Emergency Operating Procedures Writers Guide
ML20215J264
Person / Time
Site: Rancho Seco
Issue date: 02/05/1987
From:
SACRAMENTO MUNICIPAL UTILITY DISTRICT
To:
Shared Package
ML20215H764 List:
References
AP.2.24, TAC-44335, NUDOCS 8706240381
Download: ML20215J264 (12)


Text

.

EFFECTIVE DAT'E

, , 02-05-87 Original WP0936P 0-0026P AP.2.24 EMERGENCY OPERATING PROCEDURES WRITERS GUIDE 1.0 PURPOSE The purpose of this document is to provide administrative and technical ,

guidance in the preparation of E0Ps and to facilitate a simple '

consistent format that can be easily read and followed by the operator. i This procedure is a supplement to the Rancho Seco Writer's Guide, j AP.2.10 and may supercede AP.2.10 in areas peculiar to E0Ps. j i

2.0 REFERENCES

2.1 Guidelines for the Preparation of Emergency Operating Procedues NUREG {

0899 2.2 Emergency Operating Procedures Writing Guideline INPO 82-017, July 1982 2.3 Rancho Seco Writer's Guide, AP.2.10, Rev. 0 2.4 Verification of Emergency Operating Procedures, AP.2.05, Rev. 0 2.5 Validation of Emergency Operating Procedures, AP.2.06, Rev. 0 3.0 DEFINITIONS E0Ps-procedures that govern the plant operation during emergency conditions and specify operator actions to be taken to return the plant to a stable condition.

Contingency action - operator actions that should be taken in the event a stated condition, event or task does not produce the expected result.  ;

4.0 PREREQUISITES None 5.0 PRECAUTIONS None i

l AP.2.24-1 8706240381 870616 PDR ADOCK 05000312 F PDR 1

6.0 PROCE000E "?-

6.1 _'OP E Desionation and Numbering This identification Each plant procedure shall be uniquely identified. ,

permits easy administration of the process of procedure preparation, review, revision, distribution, and operator use.

6.1 .1- Procedure Designation Designation of the emergency operating procedure shall be E.

6.1 .2 Procedure Numbering '

A sequential number will follow the procedure designator and will consist of two digits.

Example: " Procedure Designator 4 E 01 + Sequence Number" 6.1 .3 Revision Numbering and Designation Two digits following the abbreviation "Rev" will be used to 6.1 .3.1 designate the revision level of the emergency operating procedure.

Example: " Abbreviation + Rev 01 + Revision Level" To identify revicions to the text of an E0P, a change arrow 6.1 .3.2 will be located in the left margin alongside the text change, preceded by the Rev. number.

.3.3 Upon issuance of a new revision, the arrows in the margin of 6.1 the previous revision will be omitted.

6.1 .4 Page Identification and Numbering Each revised page shall be numbered with the alpha numeric A identification of the procedure followed by the page number. A period will separate the alpha numeric identifica number.

6.1 .5 Title The title shall be a clear unique title that inc procedure, and will be located at the top of each operator act page of the procedure and preceded by its E0P number. I i

AP.2.24-2 l

l

i PROCEDURE ~ (Continued) ,

6.2 Format A two page format will be used except for E.01, "Immediate Actions". l

.The right page will contain the actual procedural steps which are to be l performed by the plant operators in order to control and mitigate plant transients. The left page will contain supplemental information which I is not required for the performance of the procedure, but may enhance the operator's undestanding of it.

6.2 .1 Cover Page 6.2 .l.1 The cover page will contain the emergency procedure alpha  !

numeric designator and title at the' tcp of the page.

6.2 .l.2 The cover page may show a figure of a typical SPDS trace for a heat transfer upset which would require the use of the procedure. Procedures which are not entered as a result of an SPDS trace, such as E.06 "SGTR", will have no figure on the front.

6.2 .l.3 E.01, "Immediate Actions" consists of only one page and will not have a cover sheet. f 6.2 .2 Information Page 6.2 .2.1 The lef t page in the two page format will be labeled "Information Page" at the top of the page.

6.2 .2.2 The information page will contain information which is useful as training material, provides supplementary information about procedural steps, highlight applicable rules, and display figures which illustrate SPDS traces typical of those accompanying the applicable transients.

6.2 .2.3 The informational steps will be located directly across the '

page from the procedural step it relates to, as much as possible. They will also be numbered to match the precedural step to which they apply.

6.2 .3 Operator Actions Page 6.2 .3.1 The right page in the two page format will be labeled at the top of the page with the alpha numeric designation of the procedure and the procedure title.

6.2 .3.2 The required operator action will be provided on the right page. The steps will be provided in short, concise, .

identifiable instructions that give appropriate directions to the user.

AP.2.24-3

PROCEDURE (Continued) 6.2 .3.3 The main steps of the procedure will be printed in RED extra p large capital letters. The more detailed substeps will be t; . ' I printed in normal size letters with black ink. The intent of the large red lettering is to allow a licensed operator to monitor procedural progress without searchin'g through all I the detailed substeps. The substeps are written in more detail should the operator need that to perform the main step.

6.2 .3.4 Cautions shall be printed in blue capital letters with a blue box enclosing the caution. This emphasizes the caution and decreases the possibility of it being overlooked if the reader branches to a step af ter the caution.

6.2 .3.5 Headings and status information will be on the right page with a line above and below them. They will be in all-capital letters.

6.2 .3.6 Steps will be numbered in arabic numerals with indentation for each level of substeps.

EXAMPLE: 1. Start an HPI pump.... ,

1. IE...............
2. THEN.............
2. Verify...............

6.3 Writing Instructional Steps 6.3 .1 Instruction Step Length and Content Instruction steps will be concise and precise. Conciseness denotes brevity; preciseness means exactly defined. Thus, instructions should be short and exact. This is easily stated, but not so easily achieved. General guidelines to be used in meeting these objectives are as follows:

6.3 .1.1 Instruction steps should deal with only one idea.

6.3 .1.2 Short, simple sentences should be used in preference to i long, compound, or complex sentences.

6.3 .1.3 Three or more evolutions should be prescribed in a series of steps, with each step made as simple as practicable.

6.3 .1.4 Objects of operator actions should be specifically stated.

This includes identification of exactly what is to be done and to what.

AP.2.24-4 l

t l

l PROCEDURE (Continued)

. 6.3 .1.5 For instructional steps that involve an action verb relating to three or more objects, the objects will be listed.

6.3 .1.6 Limits should be expressed quantitatively whenever possible.

6.3 .1.7 Mandatory sequence of steps is assumed unless otherwise '

stated.

6.3 .1.8 Identification of components and parts should be complete.

List the noun name, number and verify that they agree with Control Room labeling. '

6.3 .1.9 Instruction content should be written to communicate to the user.

6.3 .l.10 Expected results of routine tasks need not be stated.

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

6.3 .1.12 When requiring resetting or restoration of an alarm or trip, list the expected results immediately following the resetting or restoration if it would be beneficial to the '

opera tor.

6.3 .1.13 When considered beneficial to the user for proper understanding and performance, describe the system response time associated with performance of the instruction.

6.3 .1.14 When system response dictates a time frame within which the instruction must be accomplished, prescribe such time frame. If possible, however, avoid using time to initiate operator actions. Operator actions should be related to plant parameters.

6.3 .1.15 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 within the procedural steps or with a caution statement.

6.3 .1.16 When additional confirmation of system response is considered necessary, prescribe the backup readings to be made.

AP.2.24-5

l PROCEDURE (Continued) 6.3 .2 Contingency Actions 6.3 .2.1 Contingency actions will be presented, when applicable, following detailed action. The need for contingency action occurs in conjunction with tasks involving verification, observation, confirmation, and monitoring.

Contingency actions will most frequently be in an "!F-THEN' format. Exceptions to this format will need written justification for the procedure history file.

6.3 .3 Use of Logic Terms 6.3 .3.1 The logic terms AND, OR_, N01, E, IF NOT, WHEN, and THEN are often necessary to describe precisely a set of conditions or sequence of actions. When logic statements are u3ed, logic

. terms will be highlighted so that all the conditions are clear to the operator. Emphasis will be achieved by using capitalization and underlining. All letters of the logic terms shall be capitalized and the words will be underlined, if they are used within a sentence. Logic terms that stand by themselves will be capitalized only.

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

6.3 .4 Use of Cautions 6.3 .4.1 Cautions shall extend across the page prior to the steps to I which they apply. A caution cannot be used instead of an I instructional step (it cannot contain an action step). It i

should be used to denote a potential hazard to equipment or i personnel associated with the subsequent instructional step. )

i 6.3 .5 Use of Notes i 6.3 .5.1 If additional information other than cautions is desired to support an action instruction, a note may be used. A note shall present information only, not instructions, and shall be entered on the information page opposite the procedural step. The note should be numbered to match the step that it relates to.

6.3 .6 Calculations 6.3 .6.1 Mathematical calculations shall not be used in E0Ps. If a value has to be determined in order to perform a procedural step, a chart or graph shall be used.

AP.2.24-6

~-

PROCEDURE (Continued)

.- 6.3 .7 Plant Instrumentation Values 6.3 .7.1 When presenting instrumentation values, provide a band-if possible (tolerance or limit). Values shall be presented in the same units as those displayed on the instrument to be used and should be compatible with the oDerators ability to read the instrument. '

6.3 .7.2 Always use conservative values within the precision of the operator to read it. {

Example: If an upper engineering limit is 22.75 psig, however the operator can only read 22.7 or 23 psig on the meter with precision, then use the limit of 22.5 ,

6.3 .8 Component Identification I With respect to identification of components, the following rules are to be followed:

I 6.3 .8.1 Equipment, controls, and displays will be identified by their noun names and by their equipment identification number, 6.3 .8.2 The names of plant system titles are emphasized by iritial 4 capitalization. When the word " system" is deleted from the >J title because of brevity and is saderstood because of the context, the title is also emphasized by initial '

capitalization.

6.3 .8.3 If the component is seldom used or it is felt that the component be given in may be difficult parentheses to find, the following location information identification, or may\

in i

an information page note.

6.3 .9 Use of Underlining '{

6.3 .9.1 Underlining will be used for emphasis, primarily for logic terms.

6.3 .10 Referencing and Branching to Other Procedures or Steps 6.3 .10.1 Referencing (Refer to, In Conjunction with...) 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. When only a few steps are involved in the referencing, the steps should be stated in the procedure wherever they are needed.

AP.2.24-7

l PROCEDURE (Continued) l 6.3 .10.2 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 step and not return until directed. i i

6.3 .10.3 Use quotation marks to emphasize the title of the referenced or branched procedure. l Example: Go to E-01, "Immediate Actions", i 6.3 .11 Level of Detail 6.3 .11.1 Too much detail in E0Ps 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 deta'l that a recently licensed operator would desire during an emergency condition.

6.3 .12 The following action VERB INSTRUCTIONS should be used in writing E0Ps.

6.3 .12.1 For power-driven rotating equipment, use Start, Stop.

6.3 .12.2 For valves, use Open, Close, Throttle Open, Throttle Close, Throttle.

6.3 .12.3 For power distribution breakers, use Synchronize and Close, Open.

6.3 .12.4 For control switches with a positional placement that establishes a standby readiness condition, the vero " Place" should be used, along with the engraved name of the desired position. Positional placements are typically assoc'1ated with establishing readiness of automatic functions and are typically labeled AUTO or NORMAL.

Example: " Place the GLAND SEAL AIR COMPRESSOR Control Switch (S15) in AUTO."

6.3 .12.5 For multiposition control switches that have more than one position for a similar function, placement to the desired position should be specified.

Example: " Place DIESEL FIRE PUMP SELECTOR Switch to TEST No.

2."

6.3 .12.6 Standard practices 'or observing for abnormal results need not be prescribed ithin procedural steps. For instance, observation of no:se, vibration, erratic flov, or dischtrge pressure need not be specified by steps that start pumps.

AP.2.24-8 I

+

' {

PROCEDURE '(Continued) i 6.3 .13 Graphs,- Tables, etc.

l 6.3 ~.13.1 When information is presented using graphs, charts, tables. l and figures, these aids must be self-explanatory, legible, j and readable under the expected conditions of use and within j the reading precision of the operator in units common to i

' operator and his instrumentation. *

{

6.3.. 14 Units of Measure. ]

6.3 .14.1' Units of measure on figures, tables, and attachments should be given for numerical values that represent observed .  !

measurement data, or calculated results. A virgule (slant I line) should be used instead of "per". (

, Examples: ft/sec. Ibs/hr. .The objective is to ensure that l conversions do not have to be made by the operator, y 1

6.3 .15 Titles and Headings I 6.3 .15.1 Capitalization should be used for references to tables and ,

figures, titles of tables and figures within text material, )

and column headings within a table. i Examples: Refer to. Figure'201 for.............

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

6.3 .16 Figures, Table, and Attachment Numberirig

y t )

6.3 .16.1 Sequential arabic numbers should be assigned to figures, f tables, and attachments in separate series. The sequence should correspond with the order of their reference in the text. The symbol "#" and abbreviation "No," are unnecessary i

  • and should not be used. The number alone suf fices.  !

-}

Examples: Figure.1, Table 1, Attachment 1.

3e 6. .16.2 Page identification for attachments should consist of a I "

block of information that identifies.(1) procedure number, (2) attachment number (3) page number, and (4) revision 3 number. Page numbe;ing of attachments should meet the I requirements of 3.2.4.

g 9. > ' ' !;

AP.2,24-9

=

A e

~

PROCEDURE'(Continued) 6.4 Nech'anics of Style ,

6.4' .1 Punctuation {

. I 6.4 .1.1 -

Punctuation should be used only as necessary to aid reading and'orevent misunderstanding, Word order should be selected to r6 quire a minimum of punctuation ^. When extensive punctuation is necessary for clarity, the sentence should be rh ritten and possibly.made into several sentences. l I

6.4 .2 Numerical Values i The use of numerical values should be consistent with the following rules:

6.4 .2.1 For numbers less than unity, the decimal point should be i preceded by a zero,  !

Example: 0.1. .

6.4 .2.2 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.

6.4 .2.3 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 limits.

Examples: 510*F maximum, 300 psig minimum, 580* to 600*F.

Avoid using i.

6.4 .2.4 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.

Example: psig instead of psi.

6.5 Typino Format 6.5 .1 General Typing Instructions For emergency operating procedures, the following general requirements are to be followed.

6.5 .1.1 Paper size should be 8-1/2 x 11 inches ("A' size).

6.5 .1.2 White paper is to be used.

6.5 .1.3 Procedures are to be typed, or prepared on a plotter.

AP.2.24-10

l h

PROCEDURE (Continued) r

  • . 6.5 .l.4 Character size shall be consistent between headings, [

cautions, substeps, etc. Characters may be scaled to fit in j graphs and other special areas. They should be sized for [

optimum clarity. J 6.5 .2 Page Arrangement e

6.5 .2.1 Page margins are set from the paper edge. 1/2 inch should be maintained between the text and paper edge except for the I 1

binder side where 1-1/2 inch should be used. j q

6.5 .2.2 Page identification information (refer to Subsection 2.4) .I should be centered and 3/4 inch above the bottom of the page. I 6.5 .2.3 Horizontal lines shall be inserted between procedural steps to aid the operator's movement through the procedure.

(

6.5 .2.4 Line spacing shall be configured for optimum clarity. 1 1

6.5 .3 _ Graphs, Tables, etc.

Figures include graphs, drawings, diagrams, and illustrations. The 1 following rules are established.

6.5 .3.1 The figure number and its title are placed above the figure field.

6.5 .3.2 The figure field should be of sufficient size to offer good readability.

6.5 .3.3 The essential message should be clear; simple presentations are preferred.

6.5 .3.4 Grid lines of graphs should be a minimum of 1/8-inch apart.

6.5 .3.5 Labeling of items within the figure should be accompanied by arrows pointing to the item.

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

6.5 .3.7 fn general, items within the figure should be labeled.

6.5 .3.8 All line in figures should be reproducible.

6.5 .4 Tables should be produced using the following rules.

AP.2.24-11

. PROCEDURE (Cantinued) 6.5 .4.1 Type style and size should be the same as that for the rest of the procedure. (O l 6.5 .4.2 The table number and title should be located above the table field.

6.5 .4.3 A heading should be entered for each co'lumn and centered within the column; the first letter of words in the column headings should be capitalized.

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

6.5 .4.5 Tabular headings should be aligned as follows:

6.5 .4.5.1 irizontally by related entries 6.5 .4.5.2 vertically by decimal point for numerical entries 6.5 .4.5.3 vertically by first letter for word entries; however, run-over lines should be indented three spaces 6.5 .4.6 Spacing between horizontal entries suffices to segregate such entries.

6.5 .4.7 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.6 Special Instructions 6.6 .1 The E0P author should thoroughly review the references in Section ~

2.0. A working knowledge of NRC, INPO and Rancho Seco guidelines is essential to the. production of a successful E0P.

7.0 RECORDS ,

.. i None .p. ,

8.0 ENCLOSURES . _: -

None ,

END  !

AP . 2. 24 -12 i

l