· ( ,··· .. -:,, :..-;::··.·· 1 salem generating station operations department document...

224
,··· ( .. :,, :..-;::··.·· 1 SALEM GENERATING STATION OPERATIONS DEPARTMENT DOCUMENT APPROVAL COVER SHEET Title: · Author's Guide for Operations Department Do cum.en ts No.: AD--2 Unit: 1/2 Rev.: ------ ------ ----- __ o_f __ t_e_x_t_,_,_o_n_e; ..... - __ __ __ revised to upgrade existing guide for EOP writing · .·considerations •. Safety Related Review Yes· ---- ·No x · Significant Safety Issue Yes ---- No x Author - . ____ .. _. -. -----------·Date k: SQR* + ,.il.7 . ·· .. · Date o<f/01 {w. ops. Eng. ···· SOTS+ rik Wj/, . . · .Date# Dat.e {ii- . Ops. Manager b )j Jk ··tf ;·, J/i'C. I SORC Chairman**-· __ . _........ , ........ _________ Date * required only for documents needing. safety related review /. ** required only for documents containing a Significant Safety Issue \ + required only for Emer.gency Operating Procedures Salem Unit 1/2 . . ADO K PDR MASTER ·-;--.... _______________________ ---' AD-1-B-1 .

Upload: others

Post on 09-Jul-2020

5 views

Category:

Documents


0 download

TRANSCRIPT

  • ,··· ( ..

    -:,, :..-;::··.··

    1

    SALEM GENERATING STATION

    OPERATIONS DEPARTMENT DOCUMENT APPROVAL COVER SHEET

    Title: · Author's Guide for Operations Department Do cum.en ts

    No.: AD--2 Unit: 1/2 Rev.: ------ ------ -----Remarks:~_F_i_f_t~y_-_s_e_v_e_n_·~p-a_g~e_s __ o_f __ t_e_x_t_,_,_o_n_e;.....-__ e_i_·g~h_t __ -~p_a.g_e __ t_a_b_l_e~,-· ~-

    revised to upgrade existing guide for EOP writing

    · .·considerations •.

    Safety Related Review Yes· ---- ·No x · Significant Safety Issue Yes ---- No x Author t)~~~ - Date•·4-1f~

    . SR~ -·-~t~ ~_b ____ .. _. -. -----------·Date ~4~1 k: SQR* + ,.il.7 . ·· .. · Date o

  • :' .•

    ADMINISTRATIVE DIRECTIVE - 2 AUTHOR'S" GUIDE,FOR OPERATIONS DEPARTMENT DOCUMENTS

    1 ~- 0 PURPOSE

    1.1 This directive provides standardized guidelines on how to format and prepare documents and procedures so that they are complete, .. accurate, conv~nient, readable,. and acceptable to.:th~ir users •

    . . ·.; · .. . :_-. . :-:;. . .. ~ ~ ~~·;.' ';:;,

    1.2 The scope of this ·directive encompasses all documents under the cognizance of the Operations Department. In particular, however, the guidance has been pr

  • (

    :• '\

    ,

    AD-2

    2.1.2 The unique identifier assigned to each document above is provided in the respective subsections of Section 5.0 below.

    2.2 Cover Sheets

    2.2.1 All Operations Departmen~ documents shall be controlled by use of the Operations Department· Document Approval Cover Sheet as specified in AD-1, Changes to Station Documents.

    2.2.2 With the exception of Alarm Response Procedures, each individual procedure and instruction shall have a separate Document Approval Cover Sheet.

    2.2.3 For AlarmResponse Procedures, the .Document Approval Cover Sheet will also be used but may be used to control the procedures on either an individual or group basis providing that there is adequate traceability.

    2.3 Page and Revision Identification

    2c3.1 Each page ·of the document shall have the procedure designator, the page number, the revision number, and the unit number to which the procedure is applicable. ·

    2. 3. 2 The layout of the above required informatio_n is described in AD-4, Typis_t Guide.

    2;.4 Text Numbering

    2.4.1 The text of the various Operations Department documents presents guidance and instructions. To accommodate the presentation of this type of information, the following numbering/lettering system shall be used. -

    Salem. Unit 1/2

    1.0 Section heading

    1.1 Section (Section number is underlined in EOP's only).

    1.1.1 Subsection or Step

    a.· Step

    (1) Substep

    (a) Part

    2 Rev. 4 ·

  • ( .•.

    •••• (_

    / • :

    •'. ·--c:. .... -.

    AD-2

    2.4.2 Text in the right column shall be numbered as follows:

    . a. Con ting.ency Step

    (1). Substep

    . (a) Part

    2.4.3 For EOPs only, cautions shall be numbered as steps within the step sequence •.

    2.4.4 The layout (e.g. spacing, indentation, etc.) associ_a ted with text· number is described in. AD-4, Typist Guide. ·

    2.5 Attachments ·

    2.5.1 Attachments (e.g. figures, tables, graphs and checkoff sheets) to procedures and instructions are permitted provided that they (3nhance the dc;>cument by containing. only the relevant information needed- to clarify-, provide documentation, or accomplish the purpose· referenced in the text. If the information presented in an attachment can be presented in the text of the document, then it should be presented in the text.

    2.5.2 Section 4.0 shall list attachment sections and their contents as follows:

    4.1 · Tables

    Table 1, Title Table 2, Title

    4~2 . Figui-e s

    Figure 1, Title Figure 2' Title

    4. J. Graph~

    Graph 1, Title Graph 2' Title

    Salem Unit 1/2 3 Rev. 4

  • (

    ·:•

    4:. 4 Check Off Sheets

    Check Off Sheet 1, Title Check Off Sheet 2, Title

    AD-2

    Use the.word "None .. if any subsection contains no attac~ents.

    2.5.3 Attachments shall be numbered sequentially according to type and corresponding to their order of reference within the text.. The symbol.

    ·

  • 1-

    (

    ,...

    AD-2

    3.0 MECHANICS OF STYLE

    3. 1 Spe·lling

    3.1e1 Spelling· should be consistent with ·modern usage. When a·choice of spelling is offered by a dictionary, the fir~t spelling should be used.

    3o2 Hyphenation

    3. 2o1 The u-se of hyphens should be avoided unless its omission would result in: confusion.

    3 .. 2.2 Hyphens should be used in the following circumstances.

    a. In compound numerals- from twenty-one to ninety-nine1 _

    ,Example: . one hundred thirty-four

    b~ In fractions1 Example: · one-half

    c. -In compounds using the word "self"1 · Example: self-contained·

    d. When the last letter of the first word is the same vowel as the first letter of the second word1 Example: fire-extinguisher

    e. When misleading or awkward consonants would result by joining two words1 . Example: bell-like ·

    f. To avoid mispronunciation or confusion with another word; Example: . pre-position vs~ preposition

    . g. Wh~n a· letter ·is linked with a noun1 Example: 0-ring ..

    h. To separate chemical ·elements and their ·atomic weight; Example: u;..235

    3.2a3 Hyphens shall riot be used, to mean "through", except where specifying a tolerance range.

    Salem Unit 1 /2 5 Rev. 4

  • (.

    AD-2

    3.3· Punctuation

    3.3.1 Punctuation should only be used 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.

    3.3.2 Punctua-tion should be· in accordance with the following rules~

    Salem Unit 1/2

    a. Brackets should not be used except in. formulas.

    · b.. A colon should be used to· indicate that a .list of items_is to follow.

    · c·. A comma snould be used after conditional phrases , or to separate a procedure number and title in a referencing or branching ·.

    d.

    statement.. ·

    Parentheses should be used to indicate alternative items in a procedure or instruction. They can also be used to contain detailed information or data· relevant to the sentence or phrasei such as equipment number, tolerances, etc.· Parentheses are u·sed in formulas.

    e. An· apostrophe is to. be used to indicate the possessive case.

    f. A period is used at the end of a sentence. Periods shall not be used to· punctuate each item· in a list of objec;:ts ,. or mu·ltiple conditions.within a decision step. ·

    g. A question mark is used as closing punctuation for decision steps (i.e., steps followed by YES and NO paths)~- -

    (1). When a d~cision step lists multiple conditions, a question mark should be placed at the end of the f .inal condition.

    (2) When a decision step includes a list, the question mark is placed at the end of the question itself i not the list.

    6 Rev. 4

    "'

  • /

    ~ ..

    !. . · ..

    . AD-2.

    h. . Quotation marks are used to set off procedure t~tles in referencing and branching· statements• Always. place the· closing quotation mark after a per.iod or comma.

    i. Use slants to denote "per' with units of measure.

    3 • 4 Capi taliza.tion .

    3. 4 .1 Capita-lization should conform to standard American English usage.

    Salem Unit 1/2

    Some.examples are:

    a. Names of Organizations

    (1) The formal names of organizations., institutions, or companies should be capitalized. Examples:.· NU.clear Regulatory Commission Public Service Electric~nd Gas Company

    (2) The· informal reference to an organization or company should be lower cased. Examples: the commission

    the company

    b. Documents and Publications

    · (1) The official titles of procedures and · .. other documents should· be capitalized~

    Examples:

    ·,Code of: Fe!ieral ·Regulations Operat:lons·Depa~tment. Manual EOJ?~FRCC-2, "·Response to Degraded

    · Cooling" · Core.

    (2) Do not capitalize articles and prepositions in a title unless used ~s .the first word.

    Example:

    ·The American College Dictionary·. EOP.;;.TRIP-1, "Reactor Trip or Safety

    . I11j ection."

    7 Rev. 4

  • •• '\.

    (.

    c.

    AD-2

    Titles in an Organizational Structure . '

    (1) Capitalize official staff positions and titles. Examples: Operations Manager Senior Shift Supervisor

    ( 2) -·Do not capitalize general classifications or groups of personnel. Examples: operator electricians

    d. Systems and Components

    (l) Capitalize the titles of plant systems.

    Examples:

    Residual Heat Removal System Reactor Coolant System

    (2) Capitalize the names of major plant components.

    Examples:

    Charging Pump· No. lA Diesel Generator-

    3.4.2 Capitalization, in addition to 3.4.1 above, should be used as a technique for emphasizing certain words, phrases, or headings and- for''. presenting plant specific information. Some examples. are:·

    a ...

    Salem Unit 1/2

    Text Headings

    (1) The major section headings in the text · of documents shall be in full capitals.

    (2)

    Examples: INTRODUCTION FINAL CONDITIONS

    The keywords in subsection heading shall be capitalized.

    Examples: Containment Purging Initiation of Excess Letdowfi'.'}

    8 Rev. 4

    - ~· . .

  • / . \ •"'"··-. ~ .. -'·-

    \ ::~~~-·-. ·· - .

    ;· . .. --~ : : - -

    ••• .. ! . . ·.·: :.:i"' /.:. . ; ... Salem Unit 1/2 ·

    · · (3) When using the dual column format, fully capitalize and underline column

    . headings.

    Examples: ACTIONS CONTINGENCY ACTIONS

    b. Document Attachments·

    U l Capitalize re·ferences to tables, figures.,· etc.

    (2) .Capitalize the titles of attachments· when used within: the text.

    (3) Fully capitalize a title when it heads a table, figure, etc.

    (:4J . Capitalize column. headings within a table.

    ·c. Operational Modes

    - .·.

    (1) Capitalize the modes of operation as they apply to a. specific plant condition (i.e. combination of core reactivity condition, power level, · · and average reactor coolant temperature) •

    . Examples: Hot Standby Cold Shutdown

    (2) .· Capitalize modes of operation as they .apply_ to a specific system configuration •.

    Examples: ·Hot Leg Recir.c Cold Leg Injection

    d. System, Component, .. and Device Identifiers

    (1) Capitalize all letters of system acronyms,. and- ·the letters in component .and device codes.· .

    Examples:

    RHR (for Residual Heat Removal System) 21SJ54 (for valve ··designator) .lGDl TB3D (for breaker designator)

    9 Rev. 4

  • ( "·

    ••

    (2) When using the exact wording from .·nameplates' engravings' alarm windows' etc.·in procedur.es, it shall be fully capitalized.

    Examples:

    eves FLOW CONTROL AUTO ~ENERATOR PROTECTION TURB TRIP

    e. Logic Words and Action· Verbs

    (1) Fully_ capitalize all logic words when used in text to describe to the user a precise set of conditions or sequence o~ actions.

    (2)

    Examples.:

    IF: AND THEN

    Fully capitalize the main action verb in a statement. When two action verbs are used-together capitalize both. When the action verbs are· split in .the. statement capitalize only t~e first verb.

    ·Examples:

    CLOSE 2SJ135 · . VERIFY OPEN lSJl and 1SJ2

    · 3 .S ·Numerals, Units,. and' Tolerances

    3.5.1 ·'!'he use of numerical values should be consistent with.the following rules:

    Salem Unit 1/2

    a. Numbers shall be arabic numerals and should not.normally be spelled out except when the

    ·number begins a sentence or when two adjacent numbers in· a sentence could cause confusion •

    10 Rev. 4

  • .. ~· ' :~~ ..

    3.5.2

    AD-2

    b.. For numbers less than unity, the decimal point should be preceded by a zero (e.g. 0. 3) • .

    C·. The number of significant digits should be equal to the number of significant digits available from the di.splay· and the reading precision of· the operator:~~·-_.

    d •. ·When it is necessary to· use''exponents, the "E" format should be utilized.

    Examples: 10,000 = l.OE04 . 416,500 = 4~365E05 0.00162 = 1.62E~03

    e. When numerals are used to refer to instrumentation readings, the operator should be able to relate those numerals to those used on the instrumentation without conversion, translation, .. · or manipulation ..

    The. use. o-f. Urii ts. of measure· S?hould:. be. consisteD.t with the following rules.:

    a. Units- of measure used should be familiar to the· person using the document.

    b. When instrument parameters are referenced, the units of measure should be included.

    c. When uni ts are used to refer to , ins.trumentation readings, the operator should be able to relate the units to those used on the·instrumentation without conversion, translation, or mani·pulation.

    3.5.3. The use of tolerances should be consistent with the following rules:

    a. Tolerance (high and low) should be specified whenever applicable to bound numerical values and to avoid· approximations •

    . b.. The units in which tolerances are expressed should be the same as the units on the display or control to which they refer •

    Salem Unit 1/2 11 Rev. 4

  • 3.6

    c.

    Underlining

    AD-

    Acceptan~e values should. be specified in such a way that addition and subtraction by the user is avoided.; For example, do not use 2235±15 psig, instead use 2220 to 2250 · psig.

    · 3. 6. l Empba.sis of necessary key words and p}1rases in a procedure shall be accomplished by underlining the entire word or phrase~.

    3. 6. 2 This practice should be used with dis_cretion. Too much underlining may result in reduced effectiveness: too little underlining may result in key words or phrases not standing out when necessary~-

    3 .7 Sentence Structure and vocabulary

    3·. 7 .1 · The· structuring0 of sentences should be consistent with the following rules: ·

    a.

    b.

    SentenCE!S, clauses; and phrases should. be'i short and written using. simple word order· (subject, verb, object). ·

    There should be only one.main thought per sentence.

    c. .Action steps should: be in the active voice. and imperative mode. For example, state CLOSE valve lSJl rather than stating valve lSJl should be closed·.

    d. Action· steps should be in the positive form rather.than the negative form. For example, state CLOSE the valve rather than stating do not leave the valve OPEN. ·

    3 ~·7 ~ 2 The. simplest, mo.st ·familiar, and most specific words that accurately convey the intended meaning should be used.· The user should understand all words-used in the procedures. To-achieve this overall objective, the following guidance should be· followed:

    Salem Unit 1/2

    . a. Use short words and words that are common in ordinary conversation.

    12 Rev. 4

    I

    I l

    I ' . j

    I I

  • \

    •• (,

    , . '

    b.

    AD-~

    Use nomenclature that the user is trained to . use and which are standard in the nuclear power industry.

    c. Use concrete and specific words that describe. precisely what the user is to do or observe.

    d.· Use words and meanings consistently throughout the procedures.

    e. Avoid using adverbs that are difficult to define in a precise manner ·{e.g. frequently, slowly).·

    f,;. For EOPs, use only the·· action. verbs and logic words as prescribed in 3.8 below.

    3. 8 Word· ·Usage

    3:. 8 .. 1 Use of Shall, .Will, Should, and May

    a-.

    b.

    Shall den.ates mandatory compliance by· personnel under the direct control of the document.

    Will denotes expected compliance by personnel or equipment not under the direct· control of the document.

    c. Should denotes.the best or expected but_ not mandatory choice in·an option situation.

    d~ May denotes. permission but not requirement •. ·

    .3.8.2 Use of Action Verbs.

    Refer· to Table l for the list of acceptable . actions.verbs.

    3.S.3 Use of L~gic Words

    Salem Unit 1/2

    a. Logic· words ae·used to· describe a set of conditions, or to sequence action steps contingent upon conditionsa

    b. '.Each letter of a Logic word is capitalized and underlined.

    13 Rev. 4

  • ·-· . ·~.-·.· ... ·~· .• ~ r

    Salem Unit 1/2

    AD-2

    c. Logic terms are limited to the following:

    (1) AND (2) OR (3) IF ••• , THEN (4) WHEN •.•• , THEN

    d.

    e.

    The use of AND and should be avoided.

    . requires such use, organized so as to

    Logic words should action steps. When in action steps as capitalized~

    OR within the same step If the situation

    the step should be minimi.ze logic ambi.gui ty.

    not be used to. join "and" and "or" are used conjunctions they are not

    f. Rules of usage:

    (l) Use of AND

    (a) AND is used. to join two or more conditions . in a list •. The· conditions shall be lettered a., b., c., or a lower level step· number as appropriate.

    (b) AND is placed on a separate line between conditions and is centered on the conditions.

    (c)-. EXCEPTION: AND may be placed within a condition when joining components that are a part ·of the condition. ·

    (2) Use of OR

    (a) OR is used to join alternate conditions in a list •. The conditions shall be letted a., b., c., or a lower .level. step numbe~ . as appropriate.

    (b) OR is placed on a separate line between conditions and is centered on the conditions.

    ( 3 )· US«:! of IF~ •• , THEN

    (a) IF •• _.,. THEN is used to identify contingency actions to be taken when an action can not be. accomplished, or an expected response is not obtained.

    14 Rev. 4

    . ··1

    .. I

  • ( ·. .....

    r

    Salem Unit 1/2

    . AD-2

    (b) IF ••• , THEN shall not be used as.the initial level of a d'ecision making process. Ver if icat.ion or diagnostic dec~sions are handled using the YES/NO format. IF ••• , THEN may be used during subsequent levels of the decision process if the process must be continued in the right hand column of a dual column format procedure.

    (c) The IF ••• , NOT step is placed in the right hand column and aligned with the action s.tep. In the single column format the IFeo.,NOT is used as a substep to the action step it supports •.

    (d)· The IF is followed by a clarification of when additional action is required. In this context the phase IF NOT, THEN is inadequate and will not be used.

    (e) When more than one contingency is necessary, the additional IF.o., THEN steps are placed immediately after the first contingency and are numbered on the same order as the first contingency.

    (4) Use of WHEN ••• , THEN

    (a) WHEN ••• , THEN is used to identify a condition upon which an action is contingent, where the condition may occur at any.time during 'the procedure.

    (b) WHEN ••• , THEN by its nature provides a decisipn process for performance of an action~ It should be confined to this application and not used in place of a YES/NO type decision.

    15 Rev. 4

  • .... ~ .

    (_.

    ( ·.

    ' '

    AD-2

    g. Examples of Logic Term use and format.

    (1) Example 1:

    3.12 - Has SI flow been terminated as indicated ·by:.

    3.12.1 11° AND 12 Pump stopped.

    AND

    3.12.2 BIT Isolated.

    YES ~

    NO--------- a. GO TO step 3.13.

    3.12.3 GO TO step 3.23.6~

    (2) Example 2 :

    3 G 20 .Are Pzr PORVs closed? -· YES ~

    NO --------- a. IF Pzr Press less than .· 2315 PSIG·, THEN:

    . I

    I .

    Salem Unit 1/2 16

    ('!.)'.~~-- MANUALLY CLOSE PORVs.

    (2 V IF PORVs can not be ·closed, THEN close

    ···•Block Valveo

    (3.) IF ·Enock valve can not be closed, THEN GO TO EOP-LOCA-1, "Loss _of · · Reactor Coolant. '' "'"'· . _

    · .. ·.. ~

    ... ·,

    . :·· : .. ~.: .

    Rev. 4

  • •• ( . · ..

    (J) Example ~: ·

    3.29 Are all SI Termination criteria met?

    a. RCS sub cooling greater than 10°F •.

    AND -· b. Pzr level greater

    than 5%. (10% ADVERSE)

    ··AND -· c. ECS Press stable or

    increasing.

    -d. Heat Sink satisfied

    as indica.ted· · }?y:

    (1) Total AFW flow greater than 24E04 lb/hr.

    OR

    ("2 )" Greater than 10% NR in at least one SG.

    ; .,

    YES. ~-.

    NO· .;. ___ a9____ a·o GO TO step 3. 30 .,

    GO TO EOP-TRIP-3. ·- ..• :·_· .

    . -.·. (4):. ··Example 4·: ·

    3 •. 36. 4 STOP 11. and 12 RHR Pumps.

    Salem Unit 1/2

    "SI Termination.It

    17 Rev. 4

    . l l

  • / \ ..

    ( .• ; '· .~-

    3. 36. 5 WHEN both .of the_ following occur, ~ start 11 and 12 RHR Pumps.·

    a.. RCS. subcooling less· than 10°F.

    'b.

    AND

    Res· Press less than · 225 PSIG (400 PSIG ADVERSE)

    ( 5) .. Example 5:

    3 • 16·. 2 .. RESET Blackout Loading for each·Diesel Generator ..

    AD-2

    IF and SEC fa-ils to reset, THEN de-energize affected ~at 115 VAC Vital Instrument Cabinet in Relay Room:

    · (1) lA VIB24 •. (2) lB VIB27. ( 3 ). lC VIB9 • ·

    Abl;:>reviations, Acronyms·, and Symbols

    3.9.1

    3.9.2

    : ~

    Salem Unit 1/2

    ·.,_~··_

    An approved listing of abbreviations, acronyms, and symbols is provided in Administrative Directive 6.

    The abbreviations, acronyms, and symbols used in Operations Department documents should be those familiar to the user so that there· :is normally no need for the user to refer to Administrative·Directive-6.

    18 Rev. 4

    I

    I I

    l ! I

    l !

    . I ,

  • 3.9.3·

    (

    (. Salem Unit 1/2

    ·--··

    AD-2

    The.use.of abbreviations, acronyms, and symbols should be consistent with the· . following rules:

    a.· Capitalization of abbreviations shquld be uniform.

    b. · ·, :TP._e period should be omitted in ·•·· ~l:?pr.eviations except in cases ·. where the omission would result

    in confusion.

    c. Acronyms may be used if they are •defined or commonly.used.

    d. Symbols common to the user may be utilized to· represent operations, quantities, elements, relations, arid qualities.

    f.

    g.

    Subscripts shall not be used1 for example, the chemical .t

    ·relationship of water should be written H20.

    Abbreviations, acronyms, and symbois should be used for the benefit of the user not the writer. That is,·for saving reading time, ensuring clarity when space is limited, and in communi.cating mathematical ideas.

    When abbreviations, acronyms., or symbols are used to identify labels or equipment parts, the operator should be.able to immediately recognize .the. identity and location of the• label or equipment part.

    19 Rev. 4

    ·1 .. i l

    ... :

  • /

    ( '-· .. __ _

    (. ·.

    . 4·. 0

    .' AD-2

    PRESENTATION OF MATERIAL

    4 .1 Style of Expression

    4.1.1 All Operations Department documents should be written in a style that presents the information in a simple, familiar, specific, and unambiguous manner. As such, the author of ·any given .document is responsible for ensuring readability, (ie •. legibility and intelligibility). With this in mind, author's shall strive to generate

    ·documents that can· be:·

    a. Easily read,

    b~ Read. rapidly without interruption.,.

    ·c. Precisely understood,

    d. Understood without the aid of additional matei:ia+, . ·

    e. With regard to the information presented,/be accepted· by the user, .

    £. Easily learned,

    qg Retained, and

    h. Used easily for instruction.

    4·.1.2 In writing Operations Department documents (i.e. especially•technical procedures), too much detail should be avoided in the ·interest of the user. being able to effectively execute the instructions in a timely manner. To assist in determining the level of detail to be provided in any g.iven procedure, the fo+lowing general rules will apply:

    a~ The level of detail required in an administrative type procedure is the detail that the user will need to perform the

    .administrative function described by the document without further guidance.

    b. The level of detail required in a technical type procedure is the detail that a newly trained opera~or would desire.

    Salem Unit 1/2 20 Rev. 4

    I . ~

  • c-.

    '· .··~·. ··'>"..:·'-·

    AD-2

    Standard practices for observing for abnorinal 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.

    d. Information on the location of equipment, controls, o:r; displays that are infrequently used, are in out of the way places, or are otherwise difficult to find should, as a minimum, be provided.

    4.1.3 Procedures of· a given· category shall be consistent in organization, format, style, and contente

    4.1.4. User aides (e.g. figures, tables, graphs, flow charts, etc .. ) may_be utilized. However, when utilizing such aids they must_ be:

    a. Self-explanatory and stand alone,

    b. . Legible, and

    c. Readable under the expected conditions of use and within the reading precision of the user.

    4.2- Writing Instructional Steps

    4 -~ 2 .1 For administrative type procedures, the single column format should be used. For technical procedures, either the single column or a dual column format may be used. Format requirements for each procedure category are specified in section 5.0o ·

    4.2.2 For technical procedures especially, the instructional steps shall be as concise and precise as, possible. General guidelines to be followed are:

    Salem Unit 1/2

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

    b. Short, simple sentences. should be used in preference to long, compound, or complex sentences·.

    21 . Rev. 4

    -1

  • ·-·:-::·

    .-

    ( -· '·· ..

    Salem Unit 1/2

    c.

    AD-2

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

    d. Objects 0£ ~perator actions should.be specifically stated. This includes identification of exactly what is to be done and to what.

    e. Limits should be expressed quantitatively whenever possible.

    f. Mandatory sequence of steps is assumed uriless otherwise stated.

    g. Identification of components and parts should be complete.

    h. Expected results of routine tasks need not be stated.

    i.

    j.

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

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

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

    L When system response dictates a time frame wi.thin 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.

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

    22 Rev. 4

  • .-.:". . '~ ----..~- ....

    AD-~

    c:• n. When Adverse Containment conditions (4 PSIG and gJ;eater) will affect the accuracy of an instrument, then provide a dual setpoint with the following format: ·

    (. \ ..

    i. (

    (1) Is SG NR level greater than 5% (15% ADVERSE)

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

    p. ·Ensure that the hierarchy of steps is clear to the operator. If an action step is used as a descriptive heading for substeps that follow, the operator may proceed to complete the action without following· the substeps.

    Example:

    3.31 CONTROL SG levels as follows:

    The "as follows" in the example will key the operator in that substeps will follow. If

    · this were left out, the step hierarchy could be unclear.

    4.2.3 Sequencing Steps

    a. As the overriding. consideration, tasks and actions in instructional steps should be sequenced according to technical necessity.

    b. The physical layout and organization of the control room (or other plant areas) should be considered in sequencing.steps •

    . . 4. 2. 4 ·. Verification Steps

    Salem Unit 1/2

    a. Verification steps, or sign off spaces, are to be used to determine whether the

    · objective of a task or sequence of actions · has been correctly achieved.

    b. "VERIFY" shall not be used as a verb in the left column of EOPs. The YES/NO decision step is substituted to streamline the decision making process.

    c. Procedural categories requiring sign off spaces are specified in section 5.0 below.

    23 Rev. 4

    l l

    l j i

  • ••• \ \.

    .,.;,: ... _.::.~--

    AD-2

    4.2.S No~sequential Steps

    a. A· given step may require thatan action. be carried out at various intervals throughout a procedure. These nonsequential steps should be written into procedures using an approach that clearly identifies to the operator where and when these steps apply, the conditions under which they apply, and/ or the time·· sequence required for their performance.

    4. 2. 6. Equally Acceptable Steps

    a. Equally acceptable steps are those for which any one of several alternative steps or sequence of steps may be equally correct. For·these steps, the operator should always be directed to carry out one of the . alternative steps (or. sequences), but should. a·lso be given· the other alternatives when -.it

    ·.is possible that the designated steps (or · sequence) cannot be done (eeg., a designated piece.of equipment is unavailable).

    4. 2 .• 7 Recurrent Steps

    a. Recurrent steps are those that require the· operator to repeatedly perform a given . action~ ·typically, monitoring or controlling some plant ·parameter. (e.g., "CHECK AFWST level every 30 minutes"). For these.steps,

    .the operator should be told-when or how often the steps are to be performed, be reminded to perform the. steps, and be told the conditions for which the steps should no longer be carried out.

    4. 2. 8 Time_;Dependerit Steps

    Salem Unit 1/2

    a.· Time dependent steps are those that are required of the operator at some specified time interval~ o~ some· time after an action. has taken place. . A means should be provided to assist the operator in performing the step ( s) within. the required time frame •

    24 Rev. 4

    J

  • ,., •.

    / ..•

    AD-2

    4.2~9 ·Concurrerit Steps.

    a. Concurrent step~'are tho'se which have to be performed at the same time. The procedure should explicitlr indicate which steps are concurrerit so that operators can easily refer to both (or all) sets of steps. The maximum number of .concurrent steps should. not be· beyond the capability of the control room staff to perform them •.

    4. 2 .10: Diagnostic Steps·

    a.. Diagnostic steps are those which lead the operator ·to. the· appropriate. section: of the · procedure. These steps·should assist the 6per~tcir in diagnosis, and provide ·clear· and unambiguous guidance leading to the diagnostic decision, as well as clear and · unambig.uous referencing to the appropriate section of the procedµre. These steps may include. the use of status trees, flow diagrams,' graphs or other operator aids.

    4.2.11 Shift manning

    Procedures should be structured so that they can be executed by ·the miniritu.nt· control· room· _ crew as specified in the Technical Specifications. .,..,.

    4-. 2. 12 Step Grouping

    Salem Unit 1/2

    a·~ Steps should be grouped on a page·. such tha:t -no step carries over to the next page. · Tf a step is too long to fit on 'one pag~, then consider making it several smaller steps.

    - . . - . . : . - .

    b ._ Grouping is of most importance . in procedures -where '.mariy actions are· anticipated in a short time. Grouping and step length restrictions may be relaxed when the pace of action approximates routine plant evolutions.

    25 Rev. 4

    ·. '•

    ··::..

  • --·

    \.. ........ ·

    AD-2

    4.2.13 Decision steps

    a. Decision steps take the form of a question with a yes or no answer.

    b. The question should be worded in the same way it would be asked orally of an operator.

    c. Decision steps are used only in procedures using -the dual column format.

    d. The decision step is structured so that the course of action resulting from a YES evaluation is in the left.hand column, and actions for a NO evaluat~on is in the right hand column.

    e. Decision steps are generally used in place of verify and check actions to simplify the decision process.

    f. The YES and NO shall be fully capitalized and underlined. See Section 3.8.3 for examples of decision steps.

    4.2.14 Steps Requiring Several Objects

    SalemUnit 1/2

    When an action requires more than one object, the object~ should be stated so that the operator 6learly ~nderstands _the instr~ctions. Several methods may be used.

    a. When two objects are closely related or ·involve-similar nomenclature, they may be inclµdE:!d in the instruction statement and

    >l:j.:pked by the conjunction· "and". -~i'. ·' ;:,< .,,

    - -_.-:::··:1 -.. ·, - .

    15.-, -- ··When three or more objects are designated by

    c.

    sequential numbers, they may· be included in the instruction-state:rcient using the word "thr6ugh". A hyphen shall not be used to mean "through".

    In most cases where an action requires more than one object, the objects should be listed vertically using the same numbering scheme as steps with one exception: A list -of objects 6r donditions following a higher level (two-digit) step should not be numbered using the three-digit scheme. The operator, who expects a discrete action step .at this level, may be confused by nonaction items labeled with the three-digit scheme.

    26 Rev. 4

    1· !

  • ( .• '·

    /. '· ..

    AD-2

    4.2.15 Steps Performed by .Another

    The majority of .steps in Ci procedure are performed by the operator(s) in the control room and are addressed to the operator(s}. However, if the person performing the action is not an operator in- the control room', the step should specify that person.

    a. When an operatqr must be sent to a remote location to perform an action or determine the cause of a problem,. the step should specify what the operator. should do,

    . reference a supporting procedure if any, and state the location if needed.·

    b. When another group must perform the action, the step sh~uld specify the other group •.

    4. 3 use of· Cautions., Precautions, and Notes

    4 .• 3. 1 Cautions

    Salem Unit 1/2

    a.; Cautions contain.information that the operator must be aware of to avoid personal injury, loss of life, a long term health hazard, or damage to equipment.

    b. Cautions will normally take the form of an action tD be taken when a specific condition occurs.

    ll) In this-context cautions are a special t~pe of instructional step. Use of Cautions should be lim·ited ·.to maintain th~ir emphasis.

    '

    (2). Cautions may also contain information ~sed to prevent actio~s by 6perators that could lead to unsafe conditions.

    c. Cautions shall extend across both columns of a dual column procedure to set the caution

    · apart from normal steps. ·

    a. Cautions will normally be plac.ed immediately before the step to which they refer. Cautions may be placed imrn~diately after the associated step if this will improve unde.rstanding of the content. of the caution.

    27 Rev. 4

    . ' ~ .

  • .... ( \ · ...

    \ -..

    AD-2

    Cautions should be written so that they can be read comple_tely without interruption by intervenirig steps or page turning~

    f.; Cautions -that carry over from an earlier procedure should be placed at the beginning of the subsequent procedure and/or.: placed on the_ Continuous Action Summary· page'~·~- if used.

    g.. A row of asterisks shall extend acro~s the page at the top and bottom of the caution statement or step. ·

    h.. The word "CAUTION" shall be ful·ly capitalized, underlined, and centered above the statement or step to which it applies.

    4.3.2 Precations

    a. Cautionary information that should be reviewed before commencing a procedure is-grouped together into a Precautions section.

    ·b. Section 5.0 of AD-2 identifi¢s those procedure types that utilize precautions.

    4.3.3 Notes

    Salem Unit 1/2

    a. Supplementary information requi_red to support a procedu~al step that is not cautionary iri nature should be presented as a Note.

    b. Notes.precede the procedural step to which they apply. In some ·cases a Note may be more appropriately placed after ·the applicable procedural step.

    c. . Beca:use they are supplement.al, Notes shall not direct thE? user to initiate or.perform any actions. ·

    d.. For all documents except EOPs, the word "NOTE", ~hall be fully capitalized, underlined, and centered above the statement to which it applies. ~he hofe itself ~ill extend from margin· to margin.

    28 Rev. 4

  • .. ·.-

    (.

    ' \.._

    e .. ·

    AD-

    For EOl>s, notes shall be presented in the column of the step to .which they apply in· the following format:

    NOTE: Xxxxxxxxxxxxxxxxxxxxxxxxxx xxxxxxxxxxxxxxx

    When more than one note is necessary for a given step; the notes shall be listed numerically as·follows:

    NOTES: 1. Xxxxxxxxxxxxxxxxxxxxxx 2 •. Xxxxxxxxxxxxxx

    4 .-4 .Calculations and Formulas

    4. 4 .1 ·.The use of calculations and formulas in operating procedures and especially Emergency Operating Procedures should be minimized because o.f :.

    a. Time requirements for performing the calculations, and ·

    . . The increased possibility of· operator error.

    4.4.2 If a value has to be determined in order to perform a procedural step, a graph, chart, or similar operator aid should be provided when possible.

    4.4.3 When.calculations or formulas are required they should be as simple·as possible and adequate space should be provided for entry of any required data and for recording the results.

    4.5 Procedure.Referencing and Branching

    4~5.1 The practices of referencing and branching ·are allowed in the .writing of Operatio.ns Department documents. · · · ·

    4.S.2 The following ~eneral rules shall apply to the practices of referencing and branching:

    Salem Unit 1/2

    a. The pradtice of referencing- should be minimized. When possible, the. information or steps that could be referred to should be incorporated into the procedure where the information or steps are.required.

    29 Rev. 4

  • ···-·

    (

    ,.

    b.

    AD-2

    When necessary to -refer to· another procedural step or even another procedure, the reference statement should be clear and concise. That is:

    (1) Exactly where to go (i.e. what procedure and/or what step) , and

    (2)· Exactly what to do (complete what procedu~al steps, what to do with the "referring procedure" and what to ·do with the "referred procedure~) •

    c. Check referencing and. branching instructions for endless loops.

    d. When branching is used, be sure to direct the operator to any cautions that precede the branched step.

    · 4. 5 •. 3 Referencing

    ·.Referencing is used to designate two types of performance.

    a. Using two p·rocedures concurrently. The words "concurrently" or "simultaneously" shall be used to indicate this type of reference. ·' ·

    b.. ~erforming another procedure with the understariding that the operator will return to the· initial procedure. The· acronym "IAW" (in accordance with) shall b~ used to indicate this type of reference.

    4. 5. 4 B~anching .

    Salem Unit 1/2

    Branching is used to designate three types of perforinance~

    a. Going forward in the same procedure and skipping intervening steps. · The. words "GO TO" shall be used to direct the operator.

    b. Exiting the procedure with. no intent of returning to the present procedure. The words "GO TO" shall be Used to direct the operator. In this case,. do not state that the procedure should not be· returned to.

    30 Rev. 4

  • (.

    (

    ,•

    c.

    AD-2

    Returning the op·erator to a procedure that i~ already in effect. For EOPs, this shall only be us~d in Function Restoration procedures. The words "RETURN TO procedure in effect" shall be used in this case.

    4.6 Equipment Identification and Location Information

    4.6.1 Equipment Identification

    a. For valves, state the va.lve number. If the valve is not readily identifi~ble by its number, the valve description should be stated in parentheses next to the number.

    b. · For a!lnunciators and alarms, use· nomenclature exactly as it appears on the alarm window in full capital letters.

    c. For other equipment,. use the specific equipment name in upper/lower case letters (or full capitals if an acronym.)

    4·. 6. 2 Procedures should. provede operators information on the location of equipment, controls, or d~splay that are infrequently used,· are in ou~-of-the-way places or other~ise difficult to find.

    4.7 Procedure Graphics

    Procedure graphics are materials that support a procedure, such.as graphs, tables, folowcharts, and checklists.

    4.7.1 Graphics must be:

    Saiem Unit 1/2

    a. Appropriate for the intended use

    b. Self:...explanatory and able to stand alone

    c. Legible even after reduction (if any) and ·reproduction

    d~ Consistent in terminol.ogy and units ·with the . procedure . text ·

    e. Properly and completely iabeled and identified

    f. Readable under expected conditions of use arid within the reading precision pf the user

    31 Rev. 4

  • 1.

    AD-'2

    4.7~2 Use th~·foll6wing guidelines to ensure legibility of graphics:

    Salem Unit 1/2

    a. Exercise caution in ~eproducing material directly from vendor or manufacturer manuals and other existing documentation. It is diffic~lt to get a legible copy, and the reduction. usually required may make the type unreadable.

    b •. Use artwork. with crisp black lines to retain detail through generations of photocopying.

    c • Ensure that reduqed illustrations are still. readable.

    d. Ensure that oversized art is reduced enough to fit within standard page margins.

    e. Ensure consistency between graphics and· text:

    f.

    · (l) Uni ts of measure

    (2) Terminology (equipment names, part numbers, etc.)

    When using graphs, ensure that:

    (1) Lines on the graph paper are clearly .reproducible.

    (2) Scales, are consistent with the. accuracy ·needed by the user and do_not require extensive approximation or int:erpolation.

    (3) Grid lines on the graph are lighter in weight than.the axes and the data being presented.

    g·. . When using _:tables, ensure that:

    · · (1) Each column has a heading. If all the .i terns in a column are of the same unit (PSIG, gpm)., include.the unit in parentheses in th~ headinq. Do not repeat the units all the way down the column.

    {.2) Columns have adequate s·pace for entering data (jf needed) .

    32 Rev. 4

  • ,. ( ,

    /. \ ,

    Salem Unit 1/2

    . AD-2

    (3 ): Footnotes are not designated by numbers in a table. Use a, b, c, etc., to designate footnotes.

    (4) Tables meet all the requirements of AD-4, "Typing Guide".

    · -h. For flowcharts such as the status trees in EOP-CFST-1, "Critical Safety Function Status Trees," use the following guidelines.

    (1) Wording within the symbols should be brief but not so cryptic that it may be misunderstood.

    (2) The type style should be plan, bold, and in full capital letters.

    ( 3) The flowchart wording, abbreviations, units, etc .. , should be consistent with

    . the procedure text. -

    (4'), Different line patterns (solid, dashed, dotted) may be used to indicate different types of flow paths.

    (5) Paths should be spaced adequately so that there is no danager of inadvertently jumping to an adjacent path.

    i~ For checklists, use the following guidelines:

    .(lJ,

    ( 2)

    ( 3)

    ( 4 ,,

    Each checklist should have a· title~

    Checklists should be self-explanatory, containing insttuctions on ho~ to complete them. .

    Spaces requiring entry of data, signature~ initials, etc., should clearly specify what should. be entered an,d be adequate for such entry.

    Vertical and horizontal lines sh~uld be used as appropriate to, enhance clarity.

    33 Rev. 4

  • AD-2

    5.0 FORMAT REQUIREMENTS

    5.1 Directives, Administrative arid Operations

    5.1.1 Designation

    a. The designation for Administrative Directives shall be AD. The designation for Operations Directives shall be OD.

    b. A sequential number will follow the AD or OD designator to specifically identify each individual directive.

    c. As such, each individual. AaIDinistrative & Operations Directive will have a.unique identifier;· for example·, AD-1, AD-6, OD-1, OD-8, etc.

    5.1.2 ·Format Arrangement

    b.

    The single column (i.e. standard sentence approach) format should· be utilized in. preparing ADs and ODs~

    Specific guidance regarding page layout, text numbering1 etc. is provided in Section 2.0 of this directive and in AD-4, Typist Guide.

    5.1.3 Format Organization .

    a. No specific format organization requirements have been established for Administrative or Operations Directives so the administrative guidelines and.information to be included can be presented in a manner that.fits· the need.

    5. 2 Integrated. Operating Proc·e.dures

    5.2.1 Designation

    Salem Unit 1/2

    a. The designation for Integrated Operating .Procedures shall be IOP~ ·

    . b. A sequential nurober will follow the IOP designator to specifically identify each individual IOP .

    c. As such, each individual IOP will .have a unique identifier; for example, · IOP-1, ·.·· IOP-4, etc~

    . 34. Rev. 4 :·.,.

  • (. "~- ·- .·

    AD-2

    5~2.2 Format Arrangement

    a.- The duai column format should-be used in preparing IQPs.

    (1) The dual column approach shall begin with the PrereqUisite s·ection of the procedure· (refer to subsection 5. 2 •. 3 below).

    · -(a) The left hanq column shall be used for operator actio~ stateITI.ents.

    (b)' . The. right hand·. column shall be -used· to. ·present contingency actions for use when the response to the action statements are not

    . obtained and to provide supplementary information and notes.

    (2) The single column approach should be used only for the first three.sections of the procedure (refer to subsection

    .5.2.3 below).

    b. Specific guidance regarding page layout, text numbering, etc. is provided in Section .2 ~-0 of this· directive and in AD-4, Typist Guide.· ·

    5.2 •. "3 Format ·organization

    Sale'm Unit 1/2

    a. The format organization and content requirements for each IOP are as. follows:

    (ll Directly underneath. the title of. the IOP on the first page,.· there shall be three lines. as follows: START TIME TERMINATION TIME COMPLETION TIME Each line shall be accompanied by a space. for the. date ·and a ~pace:for a signature·•

    35 Rev. 4

  • (

    I ·.·

    / •. Salem Unit 1/2

    AD-2

    (2) Section 1.0 PURPOSE

    (a) This section shall provide a brief and concise statement that describes what is intended to be accomplished.

    (3) Section 2.0 PRECAUTIONS

    (a) This section shall detail pertinent cautionary information that is generally applicable to the entire procedure.

    (4) ·section 3.0 ATTACHMENTS LISTS

    (a) This section shall identify, by listing, each attachment (e.g. graph, figure, table, check off sheets, etc.) to the procedure.

    {b) Check Off Sheets, when used, shall contain a sign off space for the operator to initial after· completion of each major step. In addition, each check off sheet shall contain a sign off space for the appropriate reviewer's signature.

    (5) Section 4.Q PREREQUISITES . .

    This section shall detail fhe requiiements and ~onditions that must ·be met prior -t;:o · the . performance qf the· procedural steps . ( i .-e:·· s.~ct:i_on 5. O) •.

    .. ·· ..

    (bl . Each.·p.re:i-~'qu:isite step. shall have a· sl.gn:>off ·space for the operator to initial after completing the step.

    (6) Section 5.0 PROCEDURE

    {~)~ This section shall contain the

    ,;·.· ..

    · instructional steps and. applicable contingency actions

    cthat are necessary to meet the purpose of· the procedure.

    36 Rev'. 4

  • ('• '.:,.

    ··c•

    . AD-2

    {b) . Each pertinent instructi6nal step shall have a si~n off spabe for the operator to initial· after.· completing the step.

    (c1 This section may include supplementary information, cautionary information, and. notes.

    (7) Section 6.0 FINAL CONDITIONS

    . (a) This section shall provide a brief summary statement or

    ·statements that describes the plant condition (s). that the

    . completion of ·the procedure re·sulted in.

    (b) The statements provided in this section should be complimentary to Section 1. 0,. Purpose:.

    5.3 Emergency Operating Procedures

    5.l.l Designation

    Salem Unit 1/2

    ·.a~·· · · The'' designation for ·Emergency Operating Procedures shall be EOP.

    · b. A second level designator for each EOP shall immediately follow the EOP acronym. This

    . second level d~signator shall identify an E.OP as:

    (1) Applicable to a type of accident (e.g. TRtP, LOCA, SGTR, etc.)., or

    (2) Providing. function restoration guidance for· a· specific situation or condition (e.g. FRSM, FRHS, etc.), or

    .(3) Designating Critical Safety Function Status Trees (e.g., CFST), or

    (!1) Designating an Appendix.

    c. A sequential number will follow the second level designator to specific~lly identify each individual EOP as classified.

    37 Rev. 4

  • (

    ,. .• \ · ..

    AD-2

    d. As such, each individual EOP will have a . unique identifier. As· examples:

    (1) Two EOPs dealing with a LOCA would be shown as EOP-LOCA-1 and EOP-LOCA-2.

    (2) Two EOPs that provide function-restoration guidelines associated with Inadequate Core Cooling would be shown as.EOP-FRCC-1 and EOP-FRCC-2.

    e. Procedure Titles

    (1) Procedure titles will be selected to minimize confusion among procedures dealing with simi.lar applications •.

    (2) Titles in general, and EOP titles in particular, should be· in the form of a brief statement of the scope of the procedure.

    5.3.2 Format Arrangement

    a.

    Salem Unit 1/2

    The dual column format shall be used in preparing EOPs.

    (1) ·The dual column· approach shal_l begin ·with the Immediate Actions section of the procedure (refer to subsection 5.3.3 below).

    a.

    b.

    The left hand column shall be used for operator action steps and decision steps (questions followed by YES and NO paths) •

    The right.hand column shall be us~d to present eontingeney actions for use when the response to the action steps are not obtained. Action steps resulting from decision steps are also _placed in the right hand column.

    38 ·Rev. 4

  • ( -

    / \.

    AD-2

    (2) The single column approach shall be used only for Section 1.0, Entry Conditions, and Section 4.0, Attachments List.

    a. Specific guidance regarding page layout, text numbering, etc. is provided in Section 2.0 of this directive and in AD-4, Typist Guide.

    5.3.3 Format Organization

    Salem Unit 1/2

    a. The format organization and content requirements for each EOP are as foll.ows:

    (1) Section 1.0 ENTRY CONDITIONS

    (a) This section shall contain a list of the conditions under which the procedure is used.

    (b) The entry conditions shall include only those alarms, in4ications, oper~ting conditions, procedure referrals or other unique symptoms that the operator is to use in deciding to use the procedure. It is neither required nor desired, for example; to.list all alarms associated with a given condition {e.g~ re~ctor trip).

    (2) Section 2.0 IMMEDIATE ACTIONS

    (a) This section shall contain those actions (both automatic and.

    - - manual, both required and contingency) that the operator should either be.verifying or taking immediately when there are

    . (b)

    indications of an emergency. · !

    This section should include only those actions that stop further-degradation of existing · -conditions, to mitigate their consequences, and to allow · operators to evaluate the situation.

    39 Rev. 4

  • / ·' \

    (

    . ( · ..

    Salem. Unit 1/2

    AD-2

    (c) This section may incluae supplementary information, cautionary information, afid notes.

    (d) This section shall contain rio sign o·ff spaces.

    (e) If no immediate actions are required, the word "None", shall be entered under the title.

    (3) Section 3.0 SUBSEQUENT ACTIONS

    (a) This section shall contain thos~ actions (both required and contingency) that the operators should" take to return the.plant to a normal, stable, or a steady-state condition or to provide for a safe, extended shutdown period under emergency conditions •..

    (b) This.section may include s·upplementary information, cautionary information, or n9tes.

    {c) This section shall contain no sign off spaces.

    (4) Section 4. 0 ATTACHMENTS LIST

    (a) This section shall list e~ch .attachment in accordance with the directions in Section 2.5 of this document.

    (b) The EOP should contain no Check Off Sheets.

    (c) The EOP shall contain a tabbed divider page for each attachment used in the procedure.

    (d) ·section 4.0 shall contian no signoff spaces •

    40 Rev. 4 .

  • ( . "· ....

    I •

    Salem Unit 1/2_

    AD-2

    (5) Continuous Action Summary_ pages (CAS)

    (a) Continuous Action Summa:r:y pages contain acti6ns that may become necessary at any time during the performance of an EOP.

    _ (b) CAS pages are placed on the reverse side of the respective ~OP pages so that they are facing the next page.

    (c) CAS pages, are not used in Functional Restoration EOPs or opposite pages containing attachments~ - -

    (d) -CAS pages shall be identical. throughout a given procedure.

    (e) A three column format is used for the CAS pages. ·The left column contains a br.ief summary of the action required. The middle column states the condition requiring" the action.

    (f) A step referenqe, for the procedure in use, is plac~d to the extreme right of the condition. If the action is not refer~nced in the procedure, then two dashes (-"'."') are used in place

    · of the step reference. This would apply to Continuous Actions that carry over from previous

    .procedures.

    (g) Carry over actions should be limited to those itines -that are well known and. widely used. CAS items with limited application should be supported in the text of the procedure.

    (·h) CAS -pages are not included in the numbering scheme of the procedure. -

    41 Rev. 4

  • : ~ .

    (

    AD-2

    · 5. 4 · Abnormal Operating Procedures. ·

    5 • 4. 1 D.es igna tion

    a. The designation for Abnormal Operating Procedures shall be AOP.

    b. A second level designator for each ·AoP. shall immediately follow the AOP acronym. This second level identifier shall identify the system affected by the AOP.

    c. A sequential number will ·follow the system designator to·specifically .identify each individual AOP.

    . . .

    do· .As such, each individual AOP will have a . unique identifier~ for example, AOP-RCS-1, AOP-CC-:-4 ,. etc. .

    5. 4 .• 2 Format Arrangement

    Salem Unit 1/2

    a. The dual column format should be used in preparing AOPs.

    (1) The dual column approach shall l?egin . with the Immediate Actions section of the procedure (refer to subse·ction 5.4.3 below).

    (a)

    (b)

    The left hand. colilrnn shall be used for 6perat6~ actiori statements. · ·

    The right hand column shall be used to present ~ontingency actions for use when the response to·the action statemeil.ts are not

    · . obtained.· and to provide supplementary'· information· and notes. Action statements r~sulting from decision steps are also placed in the right hand column~

    . ·._:.,

    42 Rev. 4

  • i ,,

    AD-2

    (2)- 'l;'he single column approach shall be used only for ·the £lr~t section of the procedure (refer to subsection 5.4.3 below).

    (a) Specific guidance regarding page layout, t~xt numbering, etc. is provide~ ~n section 2.0 of this directive and in AD-4, Typist Guide.

    5. 4. 3 Forma·t Organization

    Salem Unit 1/2

    ao .The format organization and content requirements for·each AOP are as follows:

    (1) Section i . 0 ENTRY CONDITIONS

    (a) This section shall contain a list of the conditions under which the

    . procedure is used •

    (b) . The entry· conditions will include orily those alarm·s, indications,· operating conditions, procedure referrals, or other unique symptoms that the operator is to use in deciding to us~the . ·~-procedure. It is neither required or desired, for example',. to· list all alarms associated · with a given condition~

    (20) Section 2. 0 IMMEDIATE ACTIONS

    (a) This section shall contain thos~ actions (both automatic and manual~ both required and continge11cy)· that the operator should either be verifying cir .·· taking immediately when there are indications of an abnormal condition.

    (b) .. This section shoulO. include only those actions· that stop further · degradation of existing conditions, to mitigate their consequences, and to allow operators to evaluate the situation.

    43 Rev. 4

  • (····

    •• c· .... "· ._,: • ·,· -"

  • (

    ( d)

    AD-2

    CAS pages shall be identical throughout agiven procedure.

    (e) A tjree column format is used for the CA$ pages. The left column contains a brief summary of the action required. The middle ·co'lumn states the condition requiring the action.

    (f) A step reference, for the procedure in use, is placed to the extrem~ right of the condition. If the action is not referenced in' th~ procedure, then

    . (g).

    'two dashes (--) are used in place ~f the step referenc~~ This would apply to Continuous Actions that carry over from previous procedures .

    Carry over actions should be limited to those items that are. well known and widely used. CAS items with li~ited application should be supported in the text of the procedure. ·

    (h) CAS 'pages are not included in the numbering scheme of the procedure.

    ~.5 .Operatinq Procedures

    5. 5 •. 1 · Designation

    Salem Unit 1/2

    a. The designation for Operating Procedures shall be OP.

    ·. b ~. A< second level des ignato;i::-. for each Opera ting ·Procedure shall immediately follow the OP acronym .. This second level designator shall identify the system·that the Operating· Procedur·e is .applicable to. For examples; RHR, RMS, TAC, 4KV, etc. . .

    . c. ·A sequential number will follow.the second level designator to specifically identify each individual OpArating Procedure as classified. ·

    , 45 Rev. 4

  • . , .. - I

    \.. ·· ...

    d.

    AD-2.

    As such, each individual Operating Procedure will have a unique_ identifier. As examples!

    (1) Two Operating P~ocedures dealing with .. · RHR system operations would be shown as OP-RHR-1 and OP-RHR-2. .

    (2) Three Operating Procedures dealing W-i;tl:i FP system operations would be shown as: .. :':". OP-FP-l, OP-FP-2, and OP-FP-3. -- . - - - "

    5.5.2 Format Arrangement

    Salem Unit 1/2

    a._ The single column (i.e. standard sentence approach) format should normally be used i.n preparing Operating Procedures. The dual column format, however, may be used if it more adequately presents the procedure.

    - · b. . _When the dual column format is used for Operating Procedures:

    (1) The dual column approach shall begin· with' the Procedure section of the Operating Procedure (refer to subsection 5.5.3 below) •

    (a) The left· hand column shall be : used for operator action statements.

    -(b) The right hand column shall be used to present contingency

    - actions for use when the response ~o-the act~on statements are not obtained and to provide supplementary information and notes.

    (2 l The single. co-iumn approach si1all then -be used for the first four sections of the procedure (refer to subsection 5. 5 .3 below) •

    . (c) · Specific guidance regarding page layout, text numbering,. etc. is provided in Section 2.0 of this directive and in AD-4, Typist Guide.

    46 Rev. 4

  • ... .(

    (

    ,. \ ........... -··

    AD-2

    5.5.3 Format Organization·

    .. '. :~

    Salem Unit 1/2

    a~ The format organ.izatton and content requirements for each Operating Procedure are as follows:

    (1) Section l.o· PURPOSE

    (a)

    (b)

    This section shall provide a brief and concise statement that describes what is intended to be accomplished.

    ThE;! purpose statement will be numbered so that a procedure which addresses more than one operating method of the system or component can be readily identified; for example:

    1.1 This procedure provides the instruction necessary for·:

    1.1.1

    1.1. 2

    Normal Operation of · the CFCU's.

    Operation of the . CFCU's without Service Water . available.

    The intent is to have the purpose statement sub-section 1.1 serve as an index, listing those operating methods addressed by the procedu:r;e.

    {c) In those cases where the procedure is· performed to meet some requirement, · such as. Administrative requirements, this. information shall be included in the purpose statement after sub-secti-0n 1.1 and will be numbered as the next sub-:section. For·example:

    1. 2

    47

    This procedure is performed IAW the requirments of OD~71.

    Rev. 4

  • •• (

    •• ! \ ·· ...

    Salem Unit 1/2

    AD-2

    ( 2) ·· Section 2 ~ 0 INITIAL CONDITIONS

    (a) the sectio~ shall detail th~ requirements and conditions that must be met prior to the · performance of the procedural steps (i.e. section s.o)~

    (3) Section 3.0 PRECAUTIONS

    (a) This section shall detail pertinent cautionary information that is generally applicable to the entire procedure.

    (4) Section 4.0 ATTACHMENTS LIST

    (.a) This section shall identify, by listing, each attachment (e.g. graph, figure, table,, check off sheets, etc.) to the procedure.

    (b} Check off sheets, when used, shall contain·a sign off space for the operator to initial after completion of each major step. In addition, the last page of each Check off sheet shall contain a sign off space for the appropriat_e reviewer's signature.

    (.5) Section 5.0 PROCEDURE

    (a)- This section shall contain· the instructional steps and applicable contingency actions that are necessary to meet the purpose of the procedure.

    (b) The sub-sections in Section 5 shall be numbered so that they conform to the numbering of sub-sections- in· Section 1. For example in the case shown above, sub-section 5 .1 will read:

    5. 1 NORMAL OPERATION OF ·THE · CFCU'S

    48 Rev. 4

  • ------ ----

    AD-2

    ( The procedural steps will then

    (

    I (

    start ~ith 5.1.1 for ·this operating method. When all steps for this condition have been listed, a new sub-section shall begin which conforms to the next operating method listed in Section 1, with the procedural steps numbered as above. The two digit sub-section headings shall be in all caps as a means of identifying that a different operating method is now being .addressed.

    (c). This section may include supplementary information, cautionary information, and notes.

    (d) Sign off spaces in the body of the procedure are not required nor desired.

    5.6 Surveillance Procedures

    5.6.1 Designations

    Salem Unit 1/2

    a. The designation for technical specification related Surveillance Procedures assigned to the Operations Department shal.l be SP(O). The desi.gnation for non-technical specification surveillances,_called Periodic Inspection/Surveillance, shall be PI/S.

    b. For Surveillance Procedures (Operations), ·the technical specification surveiilance requirement number (main number if more than one requirement) that the Surveiliance Procedure (Operations) was- written to fulfill shall immediately follow the Surveillance Procedure (Operations) designator to specifically identify each ~1dividual procedure.

    (1) As such, each individual Surveillance Procedure will have a unique identifier~ for example, SP(0)4.4.6.3, SP(0)4.5.2(b), SP(0)4.9.4, etc.

    49 Rev. 4

    J ! l

    J

  • • AD-2

    c •. ·For Periodic Inspection/Surveillances; each shall be numbered as follows:

    (1) A second level designator foi each Periodic Inspection/Surveillance ~hall immediately follow the PI/S acronym. -This second level des'ignator shall identify the system that the Periodic Inspe.ction/Surveillance is applicable to. For examples; FP, CA, CN, etc.

    (2) A sequential number will follow the second level designator to specifically

    ·identify each individual Periodic Inspection/Surveillance as classified.

    (3) As such, each Periodic Inspection/Surveillance will have a unique identifier. As examples.:

    (a) Two Periodic Inspection/Surveillanc~s dealing with FP system inspections would be showri as PI/S-FP..;1 ·and PI/S-FP-2.

    (b) One Periodic Inspection/Stirveillance dealing

    .with a CA system surveillance would be shown as PI/S-CA-1 •.

    5.6.2. Format Arrangement

    Salem Unit 1/2

    a. The single column (i.e. standard sentence approach) format should normally be used in preparing Surveillance Procedures (Operations) and Periodic Inspection/Surveillances~ The dual column format, however, may be used i·f it more adequately presents the procedure.

    ·50 Rev. 4

    I .

    i

    1 ·

    ! ;

  • ·(···

    •• ( . -·~ ... ,

    / .• ' \ ... _ .. ~

    b· •.

    c.

    AD-2.

    When the dual. column format. is used for a Surveillance Procedure (Operations) or Peiiodic Inspecticin/Surveillarice:

    (1) The dual column approach shall begin with the Procedure section of the procedure (refer to subsection 5.6.3. below)·.

    (a) The left .hand column shall be used for operator action statements.

    (bl . The right hand column shall be used to present contingency

    . actions for use when the· response to the action statements are not obtained and to provide supplementary information and notes.

    (2) The single column approach shall be used for the first four.sections to the procedure (refer to subsection 5.6.3 below)~ ·

    Specific guidance regarding page layout·, text number, etc. is provided in Section 2.0 of this directive and in AD-4, Typist.Guide.

    5. 6. j.. Format Organization

    Salem Unit 1/2

    a. The format organization and content . requirements for each Surveillance Procedure (Operations) , and Period.ic · · Inspection/Surveillance· are as follows:

    (1) Se6tion.l.O PURPOSE

    (al ·· This.~edtion shall prbvide a brie-f and concise statement that de.scribes what is. intended to be accomplished.

    51 Rev. 4

  • (·· . .

    -·· ( . ·· ....

    (. Salem Unit 1/2

    (b)

    . (c)

    AD-2

    The ~urpose statement will be numbered so that a procedure which addresses more than one operating method of the system or component which meets the surveillance requirement can be readily identified, for example:

    1.1 This procedure provides· the instructions necessary to perform the following:

    1~1.1 Determine the Identified RCS Leak Rate •.

    1 .1 • .2 Determine the Unidentified RCS Leak Rate.

    The intent is to have the purpose statement sub-section 1.1 serve. as an index, listing those operating methods- for meeting the surveillance requirements addressed by the procedure.

    With regard to Surveillance Procedures (Operations), the specific technical specification _ survei1fance requirements (i.e. numbers) that the procedure is written to meet shall be identified in the next sub-section. The frequency

    _ requirement for the surveillance procedure will also be included ·here.

    (2) Section.2.0 INITIAL CONDITIONS

    (a) _.-The s~ction shall detail the requirements and conditions that must be met prior to the performance of the_ procedural steps (i.e. se~tion 5.0)~

    52 Rev. 4

  • ( ....... :"

    Salem Unit 1/2

    AD-2

    (b) Each initial condition shall have a sign off space f6r the ope~ator · to initial after completing the step. The "sign offs" may be included directly in the body of the procedure or in a check off sheet whichever approach better lends itself to the procedure and to records storage considerations.

    (-3) Section 3 • O- PRECAUTIONS

    (a) This section shall detail pertinent cautionary information that is generally applicable·. to the entire pro6edure.

    (4) Section.4.0 ATTACHMENTS LIST

    (a) This section shall identify, by listing, each attachment (e.g. graph, figure, table, check off sheets, . etc.) to the procedure •.

    (b) Check off sheets, when used,. shall contain a sign off space for the operator to initial, after completion of each major

    'step. tn addition, the.last page of each Check off sheet shall cdntain a si~n off space for the appropriate reviewer's signature.

    (5) Section 5.0 PROCEDURE

    (a) This section shall contain the i~structional steps and . . applicable contingency. actions · that are necessary to· meet tha purpose of the procedure.

    (b) The sub~sections in Section 5 shall be numbred so that they conform to the numbering of .. sub-sections in Secti6n·1. For exci:mple in the case shown above, sub.:..section 5.1 will read:

    5.1 DETERMINE THE UNIDENTIFIED LEAK RATE.

    53 Rev. 4

    ' . ·' I

  • /. \ •, · .....

    (c)

    (d)

    AD-2.

    Th~ procedural steps will then ~tart with 5.1.1 for this operating method. ·when ail. steps for this condition have been listed, a new sub-section shall

    ·begin which conforms to the next .. operating method listed in Section 1, with the procedural steps numbered as above. The two. digit sub-sectionheadings shall be.in. all caps as. a means of identifying.that a different operating method is now being addressed. ·

    Each pertinent instructional step· · shall have a sign off space for the operator to initial after completing the step. The "sign offs 11· may be included directly in the body of the procedure or in a. check off sheet which ever · ~pproach better lends itself to the procedure and to records . storage con.siderations ..

    This section may include supplementary information, cautionary information, and notes~

    5.7 Alarm Response Procedures

    ~.7.1 Designation

    . ·.·,

    Salem Unit 1/2

    a. The general designation for all Alarm Response Procedures shall be ARP •

    (1) A second level designator for each Alarm Respon~e Procedute shall immediately follow the ARP acronym.· This second level designation shall identify the system which the alarm addresses. For example:

    (a) The Rea,ctor Coolant Sys.tern shall be identified as· RCS ·

    . (b.) ·The ~afety Injection System shall be identified as SJ

    54 Rev. 4

  • / \_

    ( ....

    ( : .• ' \ -• .. ·

    Salem Unit 1/2

    AD-2

    An exception will 9e made in the case of those alarm_s -on local panels where -no system_desig!).ation will be necessary.

    (2-) A third level designator for each Alarm 'Response Procedure shall immediately follow the system designator. This. third level designator shall identify the type of alarm. For example:

    {a} The control room overhead annunciator alarms shall be identified as OHA. ·

    (b) The local panel annunciator alarms shall be identified as _PNL.

    (c) The control console bezel a_larms shall be identified as BZL.

    (d) The auxiliary ala,rm typewriter -_- . alarms shall be identified_ as

    AUX.

    (3) A_ fourth level designator· shall be used -· -t.o~ iqetft..ify the· specific alarm within a

    .given-alarm type. No specific approach

    .shal:"I be defined herein~ however,_ ·:whatever approach is ·used it- shall be

    used

  • .•,.;

    < .·· .

    . ,/

    :

    AD-2

    ( 4) ·As such, each Alarm Response· Procedure will have a unique identifier. For example:

    (a) Overhead annunciator alarms ARP-SJ-OHA-D26, ARP-RCS-OHA-A15 etc.

    (b) Local panel alarms, ARP-PNL-470 or ARP-PNL-470-A4, etc.

    (c) Control console bezel alarms, ARP-RCS-BZL-202060-1 ARP-RCS-BZL-20 2060-2· ARP-SJ-BZL-228507-1, etc.

    (d) Auxiliary alarm typewriter alarms, ARP-AUX-072, ARP-AUX 332, etc.

    5o7.2 Format Arrangement

    a. A formal format arrangement (i.e .• single or dual column) is not specified for alarm response procedures.

    b. Specific guidanc~ regarding page layout is provided in.AD-4, Typist Guide.

    5.7.3 Format Organization

    Salem Unit 1/2

    a. The format organization and content requirements for each Alarm Response Procedure is as follows:

    (1)

    ( 2)

    ALARM

    . (a) The exact wording ·of the alarm as it is .displayed on the annunciator, bezel, etc. shall be provided.

    ENTRY CONDITION

    (a) This section shall contain a lLst. of the conditions under which the procedure is used.

    (b) The entry conditions shall include alarm setpoints, and may include indications, operating conditions, procedure referrals, etc .

    . 56 Rev. 4

  • ••

    (

    Salem Unit 1/2

    (3)

    AD-2

    AUTOMATIC ACTIONS

    . (a) This section should coritain those actions that the operator should be verifying upon receipt of the a·larm or initiation of the procedure.

    (4) MANUAL ACTIONS

    (a) This section should contain those actions that the operator should take to return the abnormal condition to a normal condition.

    (5) SUPPLEMENTAL INFORMATION.

    (a) The inclusion of this section is optional.

    (b) This section., when included in an Alarm Response Procedure, can be used to d~tail such information as reference documents, bistable numbers, equipment locations, etc-.

    b. Signature or sign off spaces in Alarm Response Procedures ~re neither required nor desired.

    END.OF PROCEDURE

    FINAL PAGE

    57 Rev. 4

  • ••• ./ l ..

    ···-

    (. " r"•• ·~···

    P..D-2

    TABLE 1

    ACTION VEFBS

    The following list of action verbs are intended to be used for all Operations Department Documents. Action verbs used in EOPs shall be limited solely to the verbs in this list.

    VERB

    Actuate

    Adjust

    Align

    Allow

    Announce

    Arm

    Attach

    Block

    Borate

    Break

    Bypass.

    Salem Unit 1/2

    PEFINITION/USAGE EXAMPLE

    .Tb·"·;~~t into action. or motion, typically an automatic action. "'ACTUATE Containment Spray:

    · To regulate or to bring to a more satisfactory state .

    . "ADJUST Seal Pressure Control Valve 1CV71 ••• II

    To bring irito line or alignment; or come into precise adjustment or correct relative position. · . "ALI

  • VERB

    Calc.ulate.

    Check

    Circle

    Close

    Complete

    Consult

    \ ...

    Continue

    Control

    coordiria te .·

    Decrease

    Deenergize

    Salem Unit 1/2

    AD-2

    DEFINITION/USAGE EXAMPLE

    To determine by computation. "CALCULATE a boron ·addition to raise RCS boron to 100 ppm greater than the Cold Shutdown boron concentration".·

    To determine present status; to compare with a procedural requirement. "CHECK SI Pumps ·as follows: •.• "

    To draw a circle around. "CIRCLE items not operating properly."

    To chang~ the physical position of a mechanical device so that it prevents physical access or flow or permits passage of electrical current; "CLOSE valve 1FP142".

    To accomplish specified procedural requirements.· . · "COMPLETE steps 7 through 9 of Section 5.0".

    To ask· for advice, to take· counsel; to refer to. "CONSULT TSC for long-term recovery actions".

    To do or cause to do the same thing without changing or stopping. "CONTINUE attempts to restore Secondary Heat S . ki' in ·-=·-=,;:

    To exercise restraining or directing influence over; to fix or adjust th~ time, amount, or rate of; to regulate. "CONTROJ~ SG levels as follows ••• "

    To· bring· in to a commrnon act ion, · movement , ·or condition; to harmonize. "COORDINATE Gas Turbine operation with Load Dispatcher."

    To cause to grow progressively less. "DECREASE steam generator ·levels to 33%".

    To remove the power supply from. "DEENERGIZE affected SEC".

    TAB 1-2 Rev. 4

  • VERB

    Defeat

    Degas

    Depressurize

    · Determine

    Direct

    Discharge

    Drain

    ( Energize

    Establish

    Evaluate

    Equalize

    Feed

    ·Fill

    Flush

    Salem Unit 1/2

    · AD-2

    DEFINITION/USAGE EXAMPLE

    To prevent the succ~ssful outcome of. "DEFEAT 2rtd Level Undervolt Protection".

    To remove dissolved gas from a liquid~ "DEGAS' RCS IAW EOP-APPENDIX-5".

    To release gas or fluid pressure from. "DEPRESSURIZE all intact SGs as follows: .•. "

    To find out; to ascertain. . "DETERMINE required subcooling from the follo~ing table: .•• "

    To order o~ require. "DIRECT Chemistry to sample ••• "

    To give outlet or vent to a fluid or other contents. nDISCHARGE the tank to .•• " •.

    To draw off {liquid). gradually or completely "DRAIN the water from the reactor cavity

    " . •·. 0 Q

    To apply voltage to. "ENERGIZR Source Range Channel ....

    To make arrangements for a stated condition. "ESTABLISH communication with the control room".

    To assess: to determine the importance, size, or nature of; to appraise; to give a value to based on collected data. "EVALUATE Status Trees •.• "

    To make equal or uniform. "EQUALIZE· charging and letdown flows as follows: •.• "

    To keep supplied. "FEED to only 1 SG".

    To raise the level of. FILL the Accumulator in accordance with ... ".

    To cause to flow to cleanse or wash out. "FLUSH the discharge piping by opening lWI,156, 1WL56, and 1DR5 for· two minutes".

    TAB· 1-3 Rev.· 4

  • ..

    ··.·• VERB Go To

    ·Identify·

    Implement

    Increase

    Initiate

    Insert

    . Inspect

    Install.

    Isolate

    Investigate

    . Limit

    Maintain

    ,.··· Minimize f.. '-.

    Salem Unit 1/2

    AD--2

    DEFINITION/USAGE EXAMPLE

    To-branch to another step, section, or procedure. To proceed to; to transport ·oneself to a given destination. wGO TO step 10.2.3".

    To determine; to establish the identity of. "IDENTIFY affected SG.".

    To carry out; to accomplish. "IMPLEMENT the Functional Restoration with the ·highest priority".

    To cause to grow progressively greater. "INCREASE power at 3% per hour· or less".

    To begin a process; usually involving several steps or actions. "INITIATE RCS feed and bleed" •

    . To put or thrust in,. into, or .through. "INSERT control rods 11·•

    To observe or evaluate a feature or characteristic for comparison with specified limits; method of inspection should be included.

    ·INSPECT visually for leaks".

    To place and attach; to reinstall. ."INSTALL SW to AFW spoolpiece".

    To shut off or remove from service. "ISOLATE SI Accumulators".

    To search or inq~ire into. "INVEST I GATE cause of leak as fol lows~ ... "

    To restrict to an amount or quantity e~tablished as the greatest permissible or

    · to· the furthest e_xtent, range, or degree. "LIMIT flow to a maximum ••. "

    To hold or keep in any particular state or condition,.especially in a state of efficiency or validity. "MAINTAIN total AFW flow greater than 44E04 lbm/hr".

    To reduce to the smallest amount or degree. "MINIMIZE steam release from affected SG".

    TAB 1-4 Rev. 4

    . I

  • ,.-· ~- .

    ( f

    VERB

    Monitor

    Notify

    Obtain

    Open

    Operate

    Perform

    Place

    Plot

    Position

    Prepare

    Press

    Salem Unit 1/2

    AD-2

    DEFINITION/USAGE EXAMPLE

    To watch, observe, or check especially for a special purpose or to keep track of, regulate, or control the operation. ~MONITOR Source Range Neutron level while ~illing the RCS".

    To.make known or to give notice of or report an occurrence. "NOTIFY the Chemistry [)epartment to sample the batch for boric acid concentration".

    To get or attain. "OBTAIN -current Containment hydrogen reading".

    To change the physical position of a mechanical ·dev1ce, such as valve or door to the unobstructed po~ition that permits access or flow or prevents passage of ele9trical current. "OPEN 11SJ49 and _12SJ49 RHR Discharge to Cold Legs".

    To control equipment to accomplish a specific -purpose; to cause to function. "OPERATE valves from local panel"-.

    To do, carry out, or bring about; to accomplish;· to effect; to reach an objective~

    ·· "WHEN HP determines cause of radiation, THEN :PERFORM step 3.33".

    To put or set in a desired location or position. "PLACE valves-in position required by 2RP4".

    To r~present gtaphically. · "PLOT cooldown on Operations Log 4".

    To put in the proper or appropriate place. "POSITION controller switch ••• "

    To make ready; ~ut in readiness~ ·"PREPARE _containment for Head Venting as fol lows: ••• "

    To act upon through thrusting force exerted in contact; to push. "PRESS blower start button".

    TAB 1-5 Rev. 4

  • -• VERB Pressurize Prevent

    Proceed

    Purge

    Real:j.gn

    Record

    Release / I,, '•, .

    Remove

    Repeat

    Repr_essurize

    Reset

    Restore

    Resume

    Salem Unit 1/2

    AD-2

    DEFINITION/USAGE EXAMPLE

    Tb apply pressure within by filling with 9as or liquid. "PRESSURIZE first stage chamber".

    To keep from happening. "PREVENT AUTO Start of 21 RlIR Pump as. follows: ••• "

    To· go on in an orderly, regulated way. "PROCEED ~s directed by TSC".

    To make free of an unwanted substance as an impurity or a foreign material. "PURGE the PRT by performing the -following steps".

    __ To align again. "REALIGN gas analyzer as follows: ••• "

    To-document the specified condition or characteristic. ''RECORD discharge pressure".

    To-set free from restraint or confinement. "RELEASE the tank to the Circul~ting Water System as described in step 5.2".

    'To take off, move away,. or eliminate. "REMOVE lockout for 21SJ54 at 2PR4".

    To make, do, or perform again-: to - recapitulate.

    "REPEAT-emergency loading reset for affected SEC".

    To-apply pressure again. "REPRESSURIZE first stage chamber". -

    'ro set again. "RESET FW Isolation as follows: •.. "

    To b::r::ing back or put back into a former or original state. "RESTORE condenser IAW IOP-2, Cold shutdown to Hot· Stai:idby.

    To begin again after cessation or interruption. "RESUME Cooldown".

    TAB 1-6 Rev. 4

  • ·(·· \ VERB Review

    Sample

    Select

    Send

    Set

    Shift

    Stabilize

    ( ·· ......

    Start

    Station

    Stop

    Tag

    • Terminate· Salem Unit 1/2

    AD-2

    DEFTNITION/USAGE EXAMPLE -

    To examine again; ·to go over or examine critically or deliberately. "REVIEW the f b llowing .•• "

    To test or to judge the quality. Example: "SAMPLE the PRT for Oxygen concentration".

    To take or choose by preference trom a number or group. "SELECT the tank to be recirculated on the

    ·Low Level Cutoff Selector Switch".

    To direct, order,, or request to go. "S~ND HP· to area of high radiation to determine cause".

    To.physically adjust to a specified value an adjustable featµre. "SET channel R22 HI alarm to 25· mr/hr" •

    . -To: change. mode of operation. "SHIFT 2CV134 to RCDT or VCT" •.

    To· become stable, firm, steady. "STABLIZE RCS. press.

    To originate motion of an.electric or mechanical device directly or by remote control~ "START the Positive Displacement Charging

    . Puni.p 11 •

    Tb a~sign a person to stand and remain at a certain place •. "STATION a person·at the thermocouple panel".

    . .· . ··.·· . . .: : ...

    Tc) ·term±nate operation .•. "STOP th~ Positive Displacement Charging Pump"·.

    To provide with an identifying or indicating symbol (~ cardboard~ plasiic, or metal marker used for identification or classification·); to label; to attach or connect a tag to; to mark. ·"TAG. 21 through 2.4 s~TS4 breakers II •

    To.~nd, e~peciall~ a process or procedure. "TEHMINATE