ML18092B391

Rev 5 to Administrative Directive AD-2, Author Guide for Operations Dept Documents.

ML18092B391
Person / Time
Site:	Salem
Issue date:	11/10/1986
From:	Gueller J Public Service Enterprise Group
To:
Shared Package
ML18092B390	List: ML18092B389 ML18092B391
References
AD-2, NUDOCS 8701050154
Download: ML18092B391 (93)

Text

.,

-*.. /

SALEM GENERATING STATION

~* OPERATIONS DEPARTMENT DOCUMENT APPROVAL COVER SHEET

Title:

• Author's Guide for Operations Department Documents No.: AD-2 Unit: 1/2 Rev.:

Remarks: Seventy - eight pages of text, one - 9 page table, two figures, revised to' include guidence for writing EOP's in flowchart format, added additional action verbs, added figure 1 ~ example flowchart, added figure 2 - flowchart symbols.

Safety Related Review Yes No x Significant Safety Issue Yes _ _ __ No x Author Brian Connor Date 10/29/86 SRO---*------*-~------------------- Date SQR*_.,#~~.---1-,;;u-,:#---- Date Ops. Eng. __ ~-=-..1..-~l~~~~~~~-======---------------------- Date loj;9jtc, SOTS+_____ tl/~~~~------------------------------------- Date----------

• Ops. Manager_ _~*\.-~-- -=---'-)J_J..:..~

__l_k_.______ Date If /;a/rfr., I soRc chairman* *_ _ i11,...../4"'-------*f'""'r'fl9f.A~S~f ..

. . . £~R---- Date-----------

• required only for documents needing safety related review

• • required only for documents containing a Significant Safety

• Issue

+ required only for Emergency Operating Procedures Salem Unit 1/2 8701050154 AD-l-B-1 861~~--~.-~~------------------------~

"'"~~ll Rev. 7 PDR ADOCK 05000272 \

F FDR

ADMINISTRATIVE DIRECTIVE -2 AUTHOR'S GUIDE FOR OPERATIONS DEPARTMENT DOCUMENTS TABLE OF CONTENTS SECTION REFERENCE PAGE

1. 0 PURPOSE i 2.0 DOCUMENT DESIGNATIONS, NUMBERING AND LAY OUT 1 2.1 PROCEDURE DESIGNATION 1 2.2 COVER SHEETS 2 2.3 PAGE AND REVISION IDENTIFICATION 2 2.4 TEXT NUMBERING 2 2.5 ATTACHMENTS 3 2.6 FOOTNOTE NUMBERING 4 3.0 MECHANICS OF STYLE 3.1 SPELLING 5 3.2 HYPHENATION 5 3.3 PUNCTUATION 6 3.4 CAPITALIZATION 7 3.5 NUMERALS, UNITS AND TOLERANCES 11 3.6 UNDERLINING 12 3.7 SENTENCE STRUCTURE AND VOCABULARY 12 3.8 WORD USAGE 13 4.0 PRESENTATION OF MATERIAL 4.1 STYLE OF EXPRESSION 20 4.2 WRITING INSTRUCTIONAL STEPS 21 4.3 USE OF CAUTIONS, PRECAUTIONS & NOTES 27 4.4 CALCULATIONS AND FORMULAS 29

• Salem Unit 1/2 i Rev. 5

AD-2 TABLE QF CONTENTS continued

(

SECTION REFERENCE PAGE 4.5 PROCEDURE REFERENCING & BRANCHING 30 4.6 "EQUIPMENT IDENTIFICATION 31 4.7 PROCEDURE GRAPHICS 32 5.0 FORMAT REQUIREMENTS 5.1 DIRECTIVES, ADMINISTRATIVE & OPERATIONS 34 5.2 INTEGRATED OPERATING PROCEDURES 35 5.3 EMERGENCY OPERATING PROCEDURES 38 5.4 ABNORMAL OPERATING PROCEDURES 61 5.5 OPERATING PROCEDURES 65 5.6 SURVEILLANCE PROCEDURES 69 5.7 ALARM RESPONSE PROCEDURES 75

• TABLE 1 FIGURE 1 FIGURE 2 ACTION VERBS FLOWCHART EXAMPLE FLOWCHART SYMBOLS TAB 1-1 FIG 1-1 FIG 2-1

• Salem Unit 1/2 ii Rev. 5

AD-2 ADMINISTRATIVE DIRECTIVE - 2

• 1.0 AUTHOR'S GUIDE FOR OPERATIONS DEPARTMENT DOCUMENTS PURPOSE 1.1 This directive provides standardized guidelines on how to format and prepare documents and procedures so that they are complete, accurate, convenient, readable, and acceptable to their 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 provided for use in preparing the following documents:

1.2.1 Administrative Directives 1.2.2 Operations Directives 1.2.3 Integrated Operating Procedures 1.2.4 Emergency Operating Procedures 1.2.5 Abnormal Operating Procedures 1.2.6 Operating Procedures

• 1.2.7 1.2.8 1.2.9 Surveillance Procedures Periodic Inspection Surveillance Alarm Response Procedures 1.3 Although it is intended that all guidance provided within this directive is to be followed, it is not the purpose of this document to establish implementation requirements (e.g., priorities or schedules). The implementation of this guide shall be controlled by the Operations Manager.

2.0 DOCUMENT DESIGNATIONS, NUMBERING, AND LAYOUT 2.1 Procedure Designations 2.1.1 Each Operations Department document shall be uniquely identified with a combination of alpha-numerical designators.

a. This identification facilitates the administration of the process of document preparation; review; revision; distribution; use; and subsequent records handling, storage, and future retrieval

• Salem Unit 1/2 1 Rev. 5

AD-2

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

Cover Sheets 2.2.1 *All Operations Department documents shall be controlled by use of the Operations Department Document Approval Cover Sheet as specified in AD-1, Changes to Station Document.".

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 Alarm Response 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 2.3.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 iayout of the above required information is described in AD-4, "Typist 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 except in flowchart procedures.

1.0 Section Heading 1.1 Section 1.1.1 Subsection or Step

a. Step (1) Substep (a) Part

• Salem Unit 1/2 2 Rev,. 5

' AD-2

• 2.4.2 In a dual column procedure, text in the right coiumn shall be numbered as follows:

a.

(1)

Contingency Step Substep (a) - Part 2.4.3 For EOPs only, Cautions and Notes shall be numbered as steps within the step sequence.

2.4.4 The layout (e.g., spacing and indentation) associated with text numbering is described in AD-4, "Typist Guide."

2.5 Attachments NOTE The attachment requirements in~.1 and 2.5.2 do not apply to flowchart procedures. The requirements for flowchart procedure attachments are in Section 5.3.3.

2.5.1 Attachments (e.g., figures, tables, graphs, and checkoff sheets) to procedures and instructions are permitted provided that they enhance the document 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, Titl.e 4.2 Figures Figure 1, Title Figure 2, Title 4.3 Graphs Graph 1, Title Graph 2, Title

• Salem Unit 1/2 . .. Rey

• 5

AD-2

• 4.4 Check Off Sheets Check Off Sheet 1, Title Check Off Sheet 2, Title Use the word "None" if any subsection contains no

• attachments.

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

(#) and abbreviation (No.) are unnecessary and should not be used.

2.5.4 Page and revision identification of each attachment shall be as described in Section 2.3, except that page numbering shall be as follows:

a. Number each page of an attac*hment at the bottom center of the page. The page number shall identify the type of attachment, the attachment number, and the sequential page number within that attachment.

Examples:

• 2.5.5 TAB 1-1 FIG 2-2 cos 3-2 (the first page of Table 1)

(the second page of Figure 2)

(the second page of Check Off Sheet 3)

The text (if any) of each attachment should be numbered in accordance with Section 2.4.

2.6 Footnote Numbering 2.6.1 Footnotes in the text of procedures should be avoided at all times.

2.6.2 Footnotes may be used in figures, tables, and check off sheets, including* those in flowchart procedures.

2.6.3 Footnotes shall be on the page on which they are referenced and numbered for that page. Footnotes may be repeated as often as necessary.

2.6.4 Footnotes shall not be used in the body of flowchart procedures .

• Salem Unit 1/2 4 Rev. 5

AD-2

• 3.0 MECHANICS OF STYLE 3.1 Spelling 3.1.1 Spelling should be consistent with modern usage *

.When a choice of spelling is offered by a dictionary, the first spelling should be used.

3.2 Hyphenation 3.2.1 The use of hyphens should be avoided unless omission of the hyphen would result in confusion.

3.2.2 Hyphens should be used in the following circumstances:

a. In compound numerals from twenty-one to ninety-nine.

Example: one hundred thirty-four

b. In fractions.

Example: one-half

c. In compounds using the word "self."

Example: seif-contained

• d.

e.

When the last letter of the pref ix is the same vowel as the first letter of the root word.

Example: de-energize When misleading or awkward consonants would result by joining two words.

Example: bell-like

f. To avoid mispronunciation or confusion with another word.

Example: pre-position vs. preposition

g. When a letter is linked with a noun.

Example: 0-ring

h. To separate chemical elements and their atomic weight.

• Example: U-235 3.2.3 Hyphens shall not be used to mean "through" except where specifying a tolerance range *

• Salem Unit 1/2 5 Rev. 5

AD-2

• 3.3 Punctuation 3.3.1 Punctuation should only be used as necessary to aid reading and preverit 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 Punctuation should be in accordance with the following rules:

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 should be used after conditional phrases or to separate a procedure number and title in a referencing or branching statement.

d. Parentheses should be used to indicate alternative items in a procedure or instruction. They may be used to contain detailed information or data relevant to the sentence or phrase, such as equipment number or tolerances. Parentheses are also used in formulas.

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

f. A period is used at the end of a seritence except in flowcharts where a closing period is not used. Periods shall not be used to i I punctuate each item in a list of objects or multiple 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) in dual column procedures.

(1) When a decision step lists multiple conditions; a question mark should be placed at the end of t-he final condition *

• Salem Unit 1/2 6 Rev. 5

AD-2

• h.*

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

Quotation marks are used to set off procedure titles in referencing and branching statements. Always place the closing quotation mark after a period or comma.

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

• measure.

3.4 Capitalization NOTE Capitalization requirements do not apply to flowcharts, which are typed entirely in full capital letters.

3.4.1 Capitalization should conform to standard American usage.

Some examples are:

a. Names of Organizations (1) The formal names of organizations, institutions, or companies should be capitalized.

Examples:

Nuclear Regulatory Commission Public Service Electric and Gas Company (2) The informal reference to an organization or company should not be capitalized.

Examples: the commission the company

b. Documents and Publications (1) The official titles of procedures and other documents should be capitalized.

Examples:

Code of Federal Regulations Operations Department Manual EOP-FRCC-2, "Response to Degraded Core Cooling"

• Salem Unit 1/2 7 Rev. 5

AD-2

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

Example:

The American College Dictionary EOP-TRIP-1, "Reactor Trip or Safety Injection"

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

• (1) 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

• Salem Unit 1/2 11.'~***-*---

• rG

. 'I 8

Rev. 5

AD-2 3.4.2 Capitalization should also be used as a technique for emphasizing certain words, phrases, or headings and for presenting plant-specific information. Some examples are:

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

Examples:

INTRODUCTION FINAL CONDITIONS (2) The key words in subsection headings shall be capitalized.

Examples:

Containment Purging Initiation of Excess Letdown (3) When using the dual column format, fully capitalize and underline column headings.

Examples:

• b.

ACTIONS CONTINGENCY ACTIONS Document Attachments (1) Capitalize references 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.

(4) Capitalize column headings within a table .

• Salem Unit 1/2 9 Rev. 5

AD-2

• c. Operational Modes (1) Capitalize 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*Recirc 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) 1GD1TB3D (for breaker designator)

(2) When using the exact wording from nameplates, engravings, alarm windows, etc., in procedures, use full capitals.

Examples:

eves FLOW CONTROL AUTO GENERATOR 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 of actions.

Examples:

IF

• Salem Unit 1/2 AND THEN 10 Rev. 5

AD-2 f "*'

• • (2) 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 the first verb.

Examples:

CLOSE 2SJ135 VERIFY OPEN lSJl and 1SJ2 3.5 Numerals, Units, and Tolerances 3.5.1 The use of numerical values should be consistent with the following rules:

a. Numbers shall be arabic numerals and should not be spelled out with the following exceptions: (1) Spell out the number when it begins a sentence. (2) When two adjacent numbers in a sentence could cause confusion, spell out the first number, e.g.,

two 4KV buses. (3) In flowchart procedures, spell out ONE and TWO when they quantify a noun, e.g., ONE PUMP .

b. For numbers less than one, 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 display 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 436,500 = 4.365E05 0.00162 = l.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 .

• Salem Unit 1/2 11 Rev. 5

• AD-2

• 3.5.2 The use of units of measure should be consistent 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 units are used to refer to instrumentation readings, the operator should be able to relate the units to those used on the instrumentation without conversion, translation, or manipulation.

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

a. Tolerances (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 *

c. Acceptance values should be specified in such a way that addition and subtraction by the user are avoided. For example, instead of "2235+/-15 PSIG," use "2235 (2220-2250)

PSIG."

3.6 Underlining 3.6.1 Emphasis of necessary key words and phrases in a procedure shall be accomplished by underlining the entire word or phrase.

3.6.2 This practice should be used with discretion.

Too much underlining may result in reduced effectiveness; too little underlining may result in key words or phrases not standing out when necessary .

• Salem Unit.1/2 12 Rev. 5

AD-2

• 3.7 Sentence Structure and Vocabulary 3.7.1 The structuring of sentences should be consistent with the following rules:

a. Sentences, clauses, and phrases should be short and written using simple word order (subject, verb, object).

b. There should be only one main thought per sentence.

c. Action steps should be in the active voice and imperative mood. For example, state "CLOSE Valve lSJl" rather than "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 "Do not leave the valve OPEN."

3.7.2 The simplest, most 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:

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

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

c. Use concrete and specific words that describe pr~cisely 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) where quantification is possible.

f. For EOPs, use only the action verbs and logic words as prescribed in Section 3.8.2 below .

• Salem Unit 1/2 13 Rev. 5

AD-2 3.8 Word Usage 3.8.1 Use of Shall, Will, Should, and May

a. Shall denotes mandatory compliance by personnel under the direct control of the document.

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

a. Refer to Table 1 for a list of acceptable action verbs.

b. "VERIFY" should not be used as a verb in flowchart and dual column procedures. The YES/NO decision step is substituted to streamline the decision making process

• 3.8.3 Use of Logic Words NOTE Use of logic words in flowchart procedures is described in Section 5.3.5.

a. Logic words ar*e used to describe a set of conditions or to sequence action steps contingent upon conditions. *

b. Each letter of a logic word is capitalized and underlined.

c. Logic terms are limited to the following:

(1) AND (2) OR

( 3) IF ..* , THEN (4) WHEN **. , THEN

d. The use of AND and OR within the same step should be avoided. If the situation requires such use, the step should be organized to minimize ambiguity *

• Salem Unit 1/2 14 Rev. 5

AD-2

• e.

f.

Logic words should not be used to join action steps. When "and" and "or" are used in action steps as conjunctions they are not capitalized.

Rules of usage:

(1) Use of AND (a) AND is used to join two or more conditions in a li~t. The conditions shall be lettered a., b., c., or a iower 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 lettered a., b., c., or a lower level step number as appropriate.

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

• conditions.

(3) Use of IF **. , THEN (a) IF *.* , THEN is used to identify contingency actions to be taken when an action cannot be accomplished or an expected response is not obtained.

(b) IF ... , THEN shall not be used as the initial level of a decision making process. Verification or diagnostic decisions are handled using the YES/NO format for dual column procedures and the decision symbols in flowcharts. IF *.* ,

THEN.may be used during subsequent levels of the decision process _if the process must be continued in the--right column of a dual column format procedure or in the "NO" path of a flowchart.

• - Salem Unit 1/2 15 r~g.; n~T~

Rev. 5

AD-2

• (c) The IF *.* , NOT step is placed in the right column and aligned with the action step in a dual column procedure. In the single column format, *the IF *** , NOT step 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 phrase IF NOT, THEN is inadequate and should not be used.

(e) When more than one contingency is necessary, the additional IF *** , 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 decision process for performance of an

• action. It should be confined to this application and not used in place of a YES/NO type decision.

g. Examples of logic term use and format in dual column procedures are given below.

(1) Example 1:

3.12 Has SI flow been terminated as indicated by:

3.12.1 11 AND 12 Pump stopped per 3

• 3

• 2 . f.

AND 3.12.2 BIT Isolated per 3.3.2.g?

YES NO--------- a. GO TO Step 3.13.

• Salem Unit 1/2 16 Rev. 5

AD-2

• 3.12.3 (2) 3.20 GO TO Step 3.23.6.

Example 2:

Are Pzr PORVs closed?

YES NO --------- a. IF Pzr Press less than

-,- 2315 PSIG, THEN:

(1) CLOSE PORVs manually.

(2) IF PORVs cannot be closed, THEN close Block Valve.

(3) IF Block Valve cannot be closed, THEN GO TO EOP-LOCA-1, "Loss of Reactor Coolant."

(3) Example 3:

3.29 Are all of the following SI Termination criteria met?

• a. RCS subcooling greater than 10°F AND

b. Pzr level greater than 5% (10% ADVERSE)

AND

c. RCS Press stable or increasing AND

d. Heat Sink satisfied as indicated by:

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

• Salem Unit 1/2 17 Rev. 5

AD-2

• (2)

YES Greater than 10% NR in at least one SG.

NO --------- a. GO TO Step 3.30.

3.29.1 GO TO EOP-TRIP-3, "SI Termination."

(4 ) Ex amp le 4 :

3.36.4 STOP 11 and 12 RHR Pumps.

3. 36. 5 WHEN both of the*

folloWIIlg occur, THEN START 11 and 12 RHR Pumps.

a. RCS subcooling less than 10°F AND

• b* RCS Press less than' 225 PSIG (400 PSIG ADVERSE)

(5) Example 5:

3.16.2 RESET Blackout Loading a. IF any SEC fails to reset, for each Diesel THEN SEND operator to Generator. open appropriate breaker at 115 VAC Vital Instrument Cabinet in Relay Room:

(1) IA VIB24 (2) lB VIB27 (3) lC VIB9 3.9 Abbreviations, Acronyms, and Symbols 3.9.1 An approved list of abbreviations, acronyms, and symbols is provided in AD-6, "Approved Abbreviations List."

3.9.2 The abbreviations, -acronyms, and symbols used in Operations Department documents should be those familiar to the user.

Salem Unit 1/2 18 Rev. 5

AD-2 3.9.3 The use of abbreviations, acronyms, and symbols should be consistent with the following rules:

a. Capitalization of abbreviations should be uniform.

b. The period should be omitted in abbreviations 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 used to represent operations, quantities, elements, relations, and qualities.

e. Subscripts shall not be used~ for example, the chemical relationship of water should be written H20 .

f. Abbreviations, acronyms, and symbols 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 communicating mathematical ~deas.

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

3.9.4 Further guidance on the use of abbreviations and acronyms in flowchart procedures is provided in Section 5.3.5.g .

Salem Unit 1/2 19 Rev. 5

AD-2

• . 4.0 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. The author of any given document is responsible for ensuring readability (i.e., legibility and intelligibility). *with this in mind, authors 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 material,

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

f. Easily learned,

g. Retained, and

h. Used easily for instruction.

4.1.2 In writing Operations Department documents (especially technical procedures), too much detail should be avoided so that the user may effectively execute the instructions in a timely manner. To assist in determining the level of detail to be provided in any given procedure, apply the following general rules:

a. The level of detail required in an administrative procedure is the detail that the user will need to perform the administrative function described by the document without further guidance.

b. The levei of detail required in a technical procedure is the detail that a newly trained operator would require *

• Salem Unit 1/2 20

.,* .-i'* fi....~ ti *:1.\

Rev. 5

AD-2

• c. Standard practices for observing for abnormal results need not be prescribed within procedural steps. For example, observation of no~se, vibration, erratic flow, or discharge pressure need not be specified by steps that start pumps.

d~ Information on the location of equipment, controls, or 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 content.

4. 1. 4 User aides (e.g., figures, tables, graphs, and flowcharts) may be used. However, such aids must be:

a. Self-explanatory and able to stand alone,

b. Legible, and c* Readable under the expected conditions of use and within the reading precision of the user.

NOTE User aids in flowcharts are discussed in Section 5.3.4.i.

4.2 Writing Instructional Steps 4.2.1 For administrative procedures, the single column format should be used. For technical procedures, the single column, dual column, or flowchart format may be used. Format requirements for each procedure category are specified in Section 5.0.

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

a. Instruction steps should deal with only one idea.

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

• Salem Unit 1/2 21 Rev. 5

AD-2

• c.

d.

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

Objects of operator actions should be specifically stated, including 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 unless otherwise stated.

g. Identification of components and parts should be complete.

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

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

• j . 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 under~tanding and performance, describe the system response time associated with performance of the instruction.

1. When system response dictates a time frame within which the instruction must be accomplished, prescribe such time frame. If possibl~, 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 by using a Note *

• Salem Unit 1/2 22 Rev. 5

AD-2

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

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. An action step should not be used as a descriptive heading.* If an action step is used as a descriptive heading for substeps that follow, the operator may proceed in error to complete the action without following the substeps.

The "as follows" in the example below will lead the operator to the substeps that follow. If this phrase were left out, the step hierarchy could be unclear.

Example:

CONTROL SG levels as follows:

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 of Steps

a. Signoff spaces are to be used to determine whether the objective of a task or sequence of actions has been correctly achieved.

b. Procedural categories requiring signoff spaces are specified in Section 5.0 below *

• Salem Unit 1/2 Rev. 5

AD-2 4.2.5 Nonsequential Steps

a. A given step may require that an action be carried out at various interval~ througho~t 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.

NOTE In flowcharts, a nonsequential step is referred to as a retainment step described in Section 5.3.4.b(3).

4.2.6 Equally Acceptable Steps

a. Equally acceptable steps are those for which any one of several alternative steps or sequences 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 also be given the other alternatives when it is possible that the designated steps (or

• 4.2.7 sequence) cannot be done (e.g., a designated piece of equipment is unavailable).

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-Dependent Steps

a. Time-dependent steps are those that are required of the operator at some specified time interval or 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 .

• Salem Unit 1/2 24 Rev. 5

AD-2

• 4.2.9 Concurrent Steps

a. Concurrent steps are those which have to be performed at the same time. The procedure should explicitly indicate which steps are concurrent 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 operator in diagnosis, and provide clear and unambiguous guidance leading to the diagnostic decision, as well as clear and unambiguous referencing to the appropriate section of the procedure. These steps may include the use of status trees, flowcharts, graphs, or other operator aids.

4.2.11 Shift Manning

• a. Procedures should be structured so that they can be executed by the minimum control room crew as specified in the Technical Specifications.

4.2.12 Step Grouping

a. Steps should be grouped on a page such that no step carries over to the next page. If a step is too long to fit on one page, then consider making it several smaller steps.

b. Grouping is of most importance in proced~res where many actions are anticipated in a short time. Grouping and step length restrictions may be relaxed when.the pace of action approximates routine plant evolutions.

c. In flowcharts requiring multiple sheets, a series of actions that must be performed in a short time should not be split between pages *

• Salem Unit 1/2 25 Rev. 5

AD-2

• 4.2.13 Decision Steps a.

b.

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

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 and flowchart formats.

d. The decision step is structured so that the course of action resulting from a YES response is in the left column or flow path, and the course of action for a NO response is in the right column or flow path.

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 in dual column procedures.

See Section 3.8.3 for examples of decision steps in dual column procedures and Section 5.3.4.b(4) for flowchart procedures.

4.2.14 Steps Requiring Several Objects When an action requires more than one object, the objects should be stated so that the operator clearly understands the instructions. Several methods may be used.

a. When two objects are closely related or involve similar nomenclature, they may be included in the instruction statement and linked by the conjunction "and".

b. When three or more objects are designated by sequential numbers, they may be included in the instruction statement using the word "through." The variant "THRU" should be used in flowchart procedures to save space.

A hyphen shall not be used to mean "through" or "THRU."

• • Salem Unit 1/2 26 Rev~ 5

.' AD-2

• c. 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 or conditions 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.

d. In flowchart procedures, multiple objects should be listed vertically using bullets.

Lists of more than four objects of similar nomenclature (for example, all valve numbers/names) should be broken into two columns. A maximum of five dissimilar objects in a one column list is permissible.

4.2.15 Steps Performed by Another The majority of steps in a 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 operator 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 should specify the other group.

4.3 Use of Cautions, Precautions, and Notes 4.3.1 Cautions NOTE Cautions in flowcharts are discussed in Section 5.3.4.c.

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 .

• Salem Unit 1/2 27 Rev. 5

AD-2

• b* Cautions will normally take the form of an action to be taken if a specific condition occurs.

(1)

In this context, Cautions are a special type of instructional step. Use of Cautions should be limited to maintain their emphasis.

(2) Cautions may also contain information used to prevent actions by operators 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.

d. Cautions will normally be placed immediately before the step to which they refer.

Cautions may be placed immediately after the associated step if this will improve understanding of the content of the Caution.

e. Cautions should be written so that they can be read completely without interruption by intervening steps or page turning *

f. Cautions that carry over from an earlier procedure should be placed at the beginning of the subsequent pro.cedure.

g. A row of asterisks shall extend across the page at the top and bottom of the Caution or step.

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

4.3~2 Precautions

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

b. Section 5.0 identifies those procedure types that use precautions *

• Salem Unit 1/2 28 Rev. 5

..~

AD-2 4.3.3 Notes NOTE Notes in flowcharts are discussed in Section 5.3.4.d.

a. Supplementary information required to support a procedural step that is not cautionary in 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. Because they are supplemental, Notes shall not direct the user to initiate or perform any actions.

d. The word "NOTE" shall be fully capitalized, underlined, and cen.tered above the statement to which it applies. The Note itself will extend from margin to margin.

4.4 Calculations and Formulas

• 4.4.1 The use of calculations and formulas in operating procedures and especially EOPs should be minimized because of:

a. Time requirements for performing the calculations, and

b. The incre~sed 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 .

• Salem Unit 1/2 29 Rev. 5

AD-2

• 4.5 Procedure Referencing and Branching 4.5.l The practices of referencing and branching are allowed in the writing of Operations Department documents.

4.5.2 The following general rules shall apply to the practices of referencing and branching:

a. The practice 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.

b. When necessary to refer to another procedural step or even another procedure, the reference statement should be clear and concise; that is, it should state:

(1) Exactly where to go (i.e., what procedure and/or what step), and (2) Exactly what to do (complete what procedural steps, what to do with the "referring procedure," and what to.do with the "referred procedure").

c. Referencing and branching instructions for should avoid loops.

d. When branching is used, the operator should be directed to any Cautions that precede the branched step.

4.5.3 Referencing Referencing is used to designate two types of performance:

a. Using two procedures concurrently. Words such as "concurrently" or "simultaneously" should be used to indicate this type of reference.

b. Performing another procedure with the understanding that the operator will return to the initial procedure. The acronym "IAW" (in accordance with) shall be used to indicate this type of reference .

• Salem Unit 1/2 30 Rev. 5

AD-2

• 4.5.4

• Branching Branching is used to designate three types of performance:

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

b. Going backward in the same procedure. The words "RETURN TO" shall be used to direct the operator.

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

d. Returning the operator to a procedure that is already in effect. The words "RETURN TO procedure in effect" shall be used in this case.

NOTE Symbols used for branching in and out of flowchart procedures are described in Section 5.3.4.b.

4.6 Equipment Identification and Location Information 4.6.1 Equipment Identification NOTE Section 5.3.5 contains guidance--orlequipment identification in flowchart procedures.

a. For valves, state the valve number. If the valve is not readily identifiable by its number, the valve description should be stated in parentheses next to the number.

b. For annunciators 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.)

• Salem Unit 1/2 31 Rev. 5

AD-2 4.6.2 Procedures should provide operators infor~ation on the location of equipment, controls, or displays that are infrequently used, are in out of the way places,' or otherwise difficult to find. *

4. 7 Procedu*re Graphics Procedure graphics are materials that support a procedure, such as graphs, tables, flowcharts, and checklists.

4.7.1 Graphics must be:

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 terminology and units with the procedure text

e. Properly and completely labeled and identified

f. Readable under expected conditions of use and within the reading precision of the user 4.7.2 Use the following guidelines to ensure legibility of graphics:

a. Exercise caution in reproducing material directly from vendor or manufacturer manuals and other existing documentation. It is difficult 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 reduced illustrations are still

.readable.

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

• Salem Unit 1/2 32 Rev. 5

AD-2

• e. Ensure consistency between graphics and text:

(1)

(2)

Units of measure Terminology (equipment names, part numbers, etc.)

. f. 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 interpolation.

(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 items in a column are of the same unit (PSIG, gpm), include the unit in parentheses in the* heading. Do not repeat the units all the way* down the column.

(2) Columns have adequate space for entering data (if needed) *

(3) Footnotes are not designated by numbers in a table. U~a, b, c, etc., to designate footnotes, except in flowchart procedures where asterisks

(*,**) should be used.

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

h. For operator aid flowcharts, use the following guidelines:

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

• Salem Unit 1/2 33 Rev. 5 TER

AD-2 (2) The type style should be plain, 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 possibility of inadvertently jumping to an adjacent path.

i. For checklists, use the following guidelines:

(1) Each checklist should have a title.

(2) Checklists should be self-explanatory, containing instructions on how to complete them.

(3) Spaces requiring entry of data,

• (4) signature, initials, etc., should clearly specify what should be entered and be adequate for such entry.

Vertical and horizontal lines should be used as appropriate to enhance clarity.

5.0 FORMAT REQUIREMENTS 5.1 Directives, Administrative and 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 Administrative &

Operations Directive will have a unique identifier; for example, AD-1, AD-6, OD-1, OD-8, etc .

• Salem Unit 1/2 34

• <J *'), .~ *y~ ~~.

Rev. 5

AD-2

• 5.1. 2 Format Arrangement

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

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.1.3 Format Organization

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

5.2 Integrated Operating Procedures 5.2.1 Designation

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

b. A sequential number 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.

5.2.2 Format Arrangement

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

(1) The dual column approach shall begin with the Prerequisite section of the procedure (refer to Subsection 5.2.3 below).

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

• Salem Unit 1/2 35 Rev. 5

AD-2

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

actions for use when the response to the action statement is 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 (ref er 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

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

( 1) 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 space for a signature.

(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 *

• Salem Unit 1/2 36 Rev. 5

\ AD-2

• (4) Section 3.0 (a)

ATTACHMENTS LISTS This section shall identify, by listing, each attachment (e.g.,

graph, figure, table, or check off sheets) to the procedure.

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

In addition, each check off sheet shall contain a signof f space for the appropriate reviewer's signature.

(5) Section 4.0 PREREQUISITES (a) This section shall detail the requirements and conditions that must be met prior to the performance of the procedural steps (i.e., Section 5.0).

(b) Each prerequisite step shall have

• (6) Section 5.0 a signoff space for the operator to initial after completing the step.

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

(b) Each pertinent instructional step shall have a signof f space for the operator to initial after completing the step.

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

• Salem Unit 1/2 37

,*11***-**

Rev. 5

AD-2

-* (7) Section 6.0 (a)

FINAL CONDITIONS.

This section shall provide a brief *summary statement (or statements) that describes the plant condition(s) resulting from completion of the procedure.

(b) The statements provided in this section should be complementary to Section 1.0, Purpose.

5.3 Emergency Operating Procedures 5.3.1 Designation

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 designator shall identify an EOP as:

(1) Designating Critical Safety Function Status Trees (CFST) , or (2) Providing function restoration guidance for a specific situation or condition (for example, FRSM or FRHS), or (3) Applicable to a type of accident (for example, TRIP, LOCA, or SGTR), or (4) Designating an Appendix (APPX).

c. A sequential number (1, 2, 3) shall follow the second level designator to specifically identify each individual EOP as classified.

d. Each EOP number is prefixed by 1 or 2, which designates the applicable nuclear unit.

e. Thus, each individual EOP shall have a unique identifier. For example:

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

• Salem Unit 1/2 38 Rev. 5

\ AD-2

• e.

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

Procedure Title (1) EOP titles should be selected to minimize confusion among procedures dealing with similar applications.

(2) EOP titles should be a brief statement of the procedure scope.

5.3.2 Format Arrangement

a. An EOP shall consist of:

(1) 8-1/2" x 11" pages containing a cover sheet and sections as described in Section 5.3.3.a below.

(2) Flowchart(s) containing the action steps.

5.3.3 Format Organization

• a. Cover Sheet and Initial Sections (1) The cover sheet shall be standard Operations Department Document Approval Cove~ Sheet as specified in AD-1, "Changes to Station Documents."

(2) Initial sections shall be as follows:

1.0 ENTRY CONDITIONS The entry conditions shall include only those alarms, indications, operating 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, such as a reactor trip *

• Salem Unit 1/2 39 Rev. 5 1

MA

\* AD-2

• 2.0

• OPERATOR ACTIONS This section shall direct the operator to the flowchart(s).

Immediate and subsequent actions should be differentiated on the initial flowchart by a Note as described in Section

5. 3. 4. b ( 2) (b) below.

3.0 ATTACHMENTS LIST This section should be used for tables, figures, graphs, or check off sheets that are too large, lengthy, or numerous to include in the flowchart section described below. The attachments shall be listed in subsections as follows:

3.1 Tables Table 1, Title Table 2' Title

• 3.2 3.3 Figures Figure 1, Title Figure 2, Title Graphs Graph 1, Title Graph 2, Title 3.4 Check Off Sheets Check Off Sheet 1, Title Check Off Sheet 2, Title If Section 3.0 or any subsection contains no attachments, use the word "None." Attachments shall be formatted according to Sections 2.5.3, 2.5.4, and 2.5.5 of this procedure, and shall be separated by tabbed divider pages that immediately follow Section

3. 0 *

• Salem Unit 1/2 40 Rev. 5

AD-2

• b. Flowchart Section The action steps of th~ procedure shall be presented in a flowchart(s). Figure 1 contains a sample of the flowchart format.

The flowcharts contain:

(1) Entry Conditions Entry conditions on the flowcharts should be briefly stated, e.g.,

"REACTOR TRIP." The entry conditions in Section 1.0 are more detailed.

(2) Action Steps (a) The action steps shall contain those actions (both immediate and subsequent, both required and contingency) that the operators should take to return the plant to a normal, stable, or steady-state condition, or to provide for a safe, extended shutdown period under emergency conditions *

(b) The steps may be supported by Cautions, Notes, Continuous Action Summaries, and printed operator aids.

(3) Exit Criteria The flowchart shall designate exit criteria such as branching to another EOP *

• Salem Unit 1/2 41 Rev. 5

.. AD-2

• 5.3.4 Flowchart a.

~reparation Guidelines Identification and Numbering (1) A title block in the lower right corner of each flowchart sheet shall contain the EOP number, title, sheet number, revision number, and revision date; plant name; and unit number. See below.

PROCEDURE NUMBER PROCEDURE TITLE SHEET OF REV REV DATE XX/YY/ZZ SALEM GENERATING STATION UNIT (2) A title block in the upper* left corner of each flowchart sheet shall contain the procedure number and title.

See below.

1-EOP-TRIP-1 REACTOR TRIP OR SAFETY INJECTION

b. Flowchart Layout Each procedure should be contained on one or more flowchart sheets, 29"x44". Conversely, each sheet should contain only one procedure (or part of one). However, two or more procedures th~t are very brief may be placed on one 29"x44" sheet. Such procedures should be performed in sequence if possible.

In addition, the upper and lower title blocks discussed above should be retained for each procedure on a sheet. Procedures should be separated by a heavy vertical line .

• Salem Unit 1/2 42 Rev. 5

• AD-2

c. Logic Symbols NOTE Figure 2 contains the standard flowchart symbols used in EOPs.

(1) Entry Conditions (a) The entry conditions for symptoms should be brief noun phrases that initiate the EOP actions. The entry conditions should be located at the top of each flowchart within entry condition symbols. The positioning of the symbols indicate to the operator that any one of the conditions is necessary before operator actions commence. See below.

(b) Any one condition indicates action:

REACTOR TRIP '

• SAFETY INJECTION ACTION (2) Action Steps (a) In the flowcharts, action steps should be presented in an action step symbol. The steps should not be punctuated with a closing period. See below.

OPEN MAIN GENERATOR OUTPUT BREAKERS Salem Unit 1/2 43 Rev. 5 MASTER

AD-2

• (b) Immediate actions should be differentiated from subsequent actions by a Note in the flow path before the first immediate action. The Note should state:

"STEPS 1 THROUGH ARE IMMEDIATE ACTIONS--:-n-( c) Each action step symbol should contain only one action, or up to three closely related actions joined by AND or listed vertically-wlth bullets. See below.

CLEAR AND TAG BREAKER **.

WHEN BORATION IS COMPLETE, THEN:

~PEN VCT DISCHARGE STOP VALVES 1CV40 AND 1CV41

° CLOSE RWST TO CHARGING PUMP VALVES lSJl AND 1SJ2 NOTE The format for Notes in flowcharts is described in Section 5.3.4.d below .

• Salem Unit 1/2 44 Rev. 5

. . AD-2

• ( 3°) Retainment Steps A retainment step should be used to give operators conditions and contingency actions that they must remember while executing the steps that follow. These steps are phrased in a WHEN *** , THEN format. See below.

WHEN CONDITION X OCCURS, THEN PERFORM ACTION A (4) Decision Steps All decision steps require a choice between only two opposite possibilities, yes and no. These steps should be phrased as questions, but should not be followed by question marks. The YES response path always exits to the left of the decision symbol; the NO response path always exits to the right. See below.

INITIATE LOOP 21 THRU 24 MAIN STEAMLINE ISOLATION ACTION -

INSTRUCTION LEADING TO DECISION YES IS RCS NO AVERAGE TEMP LESS THAN 554°F

~DECISION

• Salem Unit 1/2 45 Rev. 5 -

AD-2

• (5) Concurrent Step~  :~

A concurrent step symbo-1 should be used when an operator is to enter another procedure while at the same time continuing in the current flow path.

The previous action step should ref er the operator to the concurrent procedure by number and title. The symbol contains the number of the additional procedure but does not contain a step number. See below.

INITIATE POST SI SYSTEM RESTORATION IAW EOP-APPX-4, "POST SI SYSTEM RESTORATION"

• EOP-APPX-4 ACTION

• Salem Unit 1/2 46 Rev. 5

,,. AD-2

• (6) Series of Steps to Accomplish a Goal When a series of specific actions is required to accomplish a goal, such as establishment of letdown flow, it is helpful to the user to know that this goal is the purpose of his/her actions.

In the EOP flowcharts, a noun phrase describing the goal is shown to the left of the first step in the series.

In addition, a dashed line brackets the series. The following example illustrates the position of the noun phrase and the dashed line.

The phrase describing the goal of the series of steps should be a noun phrase, not an action. The type size should be approximately 25% larger than that used in the steps.

THIS: SI INITIATION NOT THIS: INITIATE SI If the series of steps must be continued to the next column on the flowchart sheet, the bottom of the first column and the top of the next column should both indicate "CONTINUED" as shown below. The full noun phrase is repeated at the top of the next column. These series of steps should not be continued onto a new flowchart sheet .

• Salem Unit 1/2 47 Rev. 5

AD-2 RCP r-ccw I STATUS I y

I 1 I RCP

", ccwl I STATUS!

I CONTINUED I

I I

I l I I

I CONTINUED I l- -

First column Second column (7) Entry and Exit Points (a) An entry arrow symbol should be used to show where a procedure is entered from another step .or another procedure. If the entry is from another step in the same procedure, the symbol should state FROM STEP X, where X is the step number that was exited. If the entry is from a different procedure, then the entry symbol contains both the procedure number.and step number that were exited. The step number is placed below the procedure number. The entry arrow symbol is above and to the left of the entry point. See below.

EOP-TRIP-1 STEP XX ACTION

• Salem Unit 1/2 48 r* -~r ~~ '(_"'

., . _,. t)..iJ Rev. 5

AD-2

• (b)

NOTE The entry arrow symbol is the same as the entry condition symbol.

An exit arrow symbol should be .

used to direct the operator to leave the flow path at that point. The symbol contains the number of the procedure that must be entered. The step number to be entered is placed below the procedure number. See below for symbol positions in normal, "YES," and "NO" flow paths.

ACTION EOP-TRIP-2 STEP XX

• NORMAL FLOW PATH YES EOP-TRIP-2

.___STEP XX "YES" FLOW PATH EOP-TRIP-2 STEP XX "NO" FLOW PATH

• Salem Unit 1/2 49 Rev. 5

AD-2

• (c) Cautions (1) Cautions should be used to give the operator information needed to avoid equipment damage or personnel injury in executing the step. The~ should never be used to convey a required action

• step, but they may be used to express conditional actions. Conditional statements using IF *** , THEN can.only be used in Cautio'llsymbo~Cautions should not be punctuated with a closing period.--

(2) Cautions applicable to a step should be

• placed in the flow path above the step in a specific symbol as shown below:

CAUTION IF BLACKOUT OCCURS

-AFTER SI RESET, THEN RESET SEC ***

ACTION (3) The symbol for a Caution that must be remembered throughout a procedure has double borders as shown below:

CAUTION IF SI ACTUATION OCCURS DURING THIS PROCEDURE, THEN GO TO EOP-TRIP-1, "REACTOR TRIP OR SAFETY INJECTION," STEP 7

• Salem Unit 1/2 (4) Cautions are numbered within the step numbering scheme.

50 Rev. 5

AD-2

• d. Notes (1) Notes should be used to give the operator information to clarify* the instruction. A Note never concerns personnel or equipment hazards, nor does it contain operator actions. It should not be punctuated with a closing period.--

(2) A Note applicable to a step should be placed in the flow path above the step in a specific symbol as shown below:

NOTE STEPS 1 THRU 3 ARE

\ IMMEDIATE ACTIONS ACTION

• e.

(3) Notes are numbered within the step numbering scheme.

Functional Flow and Branching (1) Sufficient spacing should be allowed between paths so that the operator does not inadvertently enter an adjacent path*.

(2) Arrowheads should be used on connecting lines to clarify the direction of the path. Arrowheads should enter flowchart symbols from the top, not from the side except for exit arrow symbols.

• - Salem Unit 1/2 51 Rev. 5

AD-2

• f. Step Numbering Scheme (1) Action steps, Cautions, Notes, and decision steps should be numbered 1, 2, 3, etc., adjacent to the step.

(2) Substeps performed to accomplish a higher level step should normally not be numbered, except where a cross-reference must be made to a substep or series of substeps. In this case, all the referenced substeps should be numbered. For example, referenced substeps under Step 3 should be numbered 3.1, 3.2, etc.

g. Placekeeping Aid A Lsymbol should be placed near the lower left corner of each step as a placekeeping aid to the operator.

h. Readability Guidelines (1) The flowchart typeface should* be a plain, bold style, in full capitals, sized in accordance with the requirements of NUREG-0700, "Guidelines for Confrol Room Design Review."

(2) The spacing.between letters and between words should be distinct so that the flowcharts can be easily read in emergency lighting.

(3) All EOP lettering should be black type on white background for the highest possible contrast.

(4) The flowchart sheet should have Cartesian coordinates ~round the drawing border, with letters along the left and right edges and numbers along the top and bottom edges. Coordinate sequencing shall be left to right, top to bottom. Spacing between coordinates

~hould be approximately 2".

(5) Copies of flowcharts should be of high quality, that is, without fuzzy type *

• Salem Unit 1/2 52 Rev. 5

'MASTER

AD-2 (6) The flowchart sheets for EOPs should be 29" x 44".

i. Printed Operator "Aids (1) Figures (such as graphs and charts) and tables should be placed on the flowcharts to aid the operator in performing the action steps. For example, a table of values could be*

used so that a calculation is avoided.

(2) Labeling Scheme (a) Figur~s and tables should be lettered and titled in separate sequences: Figure A, Figure B, and Table A, Table B, etc.

(b) The letters and titles of figures and.tables should be placed above each figure/table and capitalized and underlined as shown below:

TABLE A

• (c)

SAFEGUARDS LOADING SEQUENCE Figures and tables should be referred to by letter within the action step.

(3) Placement (a) A figure or table should be aligned next to or below (not above) the first step that refers to it.

(b) Figures or tables that are too large or lengthy should be formatted as attachments per Section 5.3.3.a .

• Salem Unit 1/2 53 Rev. 5 ER

AD-2

• • (4) Quality Operator aids should be self-explanatory and legible under the expected conditions of use.

Specifically, (a) The typeface should be a plain, bold style, in full capitals, sized in accordance with the requirements of NUREG-0700, "Guidelines for Control Room Design Reviews."

(b) The aid should be a high-quality reproduction (or reduction) , that is, not a blurry photocopy.

(5) Consistency The nomenclature used in the aid should match that used in the procedure steps and in the control room itself. Units of measure and numerical values should be consistent with Technical Specifications and with actual control room indicators.

j. Continuous Action Summaries (1) Continuous Action Summaries (CASs) contain actions that may become

.necessary anytime during the performance of an EOP.

(2) CASs should not be used in Functional Restoration EOPs.

(3) CASs shall be placed in the upper l&ft corner of the flowchart and shall not be lettered and titled in sequence with any other operator aids.

(4) CASs shall be repeated on every sheet of a given procedure and shall be identical throughout a given procedure.

(5) Continuous actions should be limited to those items that are well known and widely used. CAS items with limited application should be supported in the

• Salem Unit 1/2 body of the procedure

• 54 Rev. 5

• ~1ASTER

AD-2

• (6)

(7)

The quality and consistency guidelines for printed operator aids shall apply to CASs except for typeface siz~.

(7) below.

• The typeface for Continuous Action See Summaries should be a plain, bold style, in full capitals, sized in accordance with the requirements of NUREG-0700, "Guidelines for Control Room Design Reviews."

(8) A CAS should be formatted as shown below:

CONTINUOUS ACTION

SUMMARY

CONDITION ACTION RCS PRESS LESS CLOSE PORVs THAN 2315 PSIG RCS PRESS LESS CLOSE MINIFLOW THAN 1500 PSIG VALVES AND BIT FLOW INDICATED LESS THAN 2 VITAL BUSES .** GO TO EOP-LOPA-1 ENERGIZED 5.3.5 Flowchart Vocabulary and Style Guidelines

a. Valve Nomenclature (1) Within a step, a valve shall be designated as "name number," e.g.,

OPEN VCT OUTLET VALVES 1CCV40 AND 1CV41 (2) Within a list, a valve shall be designated as "number (name)," e.g.,

CLOSE BIT ISOLATION VALVES:

0 1SJ4 (BIT INLET) 0 1SJ5 (BIT INLET) 0 1SJ12 (BIT OUTLET) 0 1SJ13 (BIT OUTLET)

(3) After a valve name has been used once in a step, the valve number may be used alone later in the same step

• Salem Unit 1/2 55 Rev. 5

AD-2.

• b. Unit/Train Nomenclature When a component .is designated by a unit/train number, the component nomenclature should be phrased as in the following examples:

11 RHR PUMP 11 THRU 14 RCPs ACCUMULATOR ISOLATION VALVES 21 THRU 24 SJ54 (in a sentence) 21 THRU 24 SJ54 (ACCUMULATOR ISOLATION) (in a list)

c. Use of Certain Actions Verbs (1) When another group is required to perform a step/action, the verb NOTIFY should be used, rather than REQUEST, HAVE, CONTACT, or DIRECT, to achieve consistency in the flowcharts. For example:

• • (2)

NOTIFY CHEMISTRY TO SAMPLE .**

NOTIFY I&C TO INVESTIGATE ***

When an operator at a remote location (outside the control room) is to perform an action, the verb DIRECT should be used rather than INSTRUCT.

For example:

DIRECT LOCAL OPERATOR TO CLOSE ...

(3) When an operator must be _sent to perform a local action, the verb SEND should be used rather than DISPATCH.

For example:

SEND AN OPERATOR TO DE-ENERGIZE ***

d. Use of Logic Words in Flowcharts (1) Logic words are used to describe a set

• of conditions or to sequence action steps contingent upon conditions *

• Salem Unit 1/2 56 Rev. 5

AD-2

• (2) Logic words are:

(a)

(b)

(c)

(d)

AND OR IF .** , THEN WHEN **. , THEN (3) Logic words are underlined.

(4) The use of AND or OR within the same sentence should be"""'ii'voided. To eliminate ambiguity, the step should be organized in a vertical format.

(5) When "AND" and "OR" are used as simple

• conjunctions, they are not underlined.

Example: START 11 AND 12 RCPs. .

(6) Use of AND is as follows:

(a) AND is used to join two or more conditions.

(b) If two conditions can be expressed briefly, they may be embedded in the step. If not, they should be listed vertically, with AND on a separate line and centered on the conditions.

(c) If an action is contingent on three or more conditions, the YES/NO format with decision symbols is preferable to a list of conditions in one step, except in a caution wher~ an IF **. , THEN statement is permitted-.- In such a Caution, three or more conditions should be formatted vertically as in the example below:

IF ANY OF THE FOLLOWING OCCURS:

0 RCS SUBCOOLING LESS THAN 10°F 0

PRESSURIZER LEVEL LESS THAN 5%

(10% ADVERSE) 0 SI ACTUATES THEN GO TO EOP-LOPA-3, "LOSS OF ALL AC POWER RECOVERY SI REQUIRED" Salem Unit 1/2 57 Rev. 5

AD-2

• { 7) Use of OR is as follows:

{a)

{b)

OR is .used to join two or more alternate conditions.

If two conditions can be expressed briefly, they may be embedded in the step. If not, they should be list~d vertically, with OR on a separate line and centered on the conditions.

{c) If an action is contingent on three or more alternate conditions, the YES/NO format with decision symbols is preferable to a list of conditions in one step.

(8) Use of AND and OR in Continuous Action Summaries Multiple conditions in CASs are listed vertically with the logic word centered on the conditions. See below *

• Example 1:

Example 2:

RCS PRESSURE LESS THAN 1500 PSIG AND BIT FLOW SUBCOOLING LESS THAN 10°F OR PZR LEVEL LESS THAN 5%

{10% ADVERSE)

OR I, SI ACTUATES 1, f,

(9) Use of IF **. , THEN is as follows:

{a) If *.. , THEN is used only in caution symbols to identify contingency actions to be taken when an action cannot be accomplished or an expected response cannot be obtained.

{b) The YES/NO format with decision symbols is used instead of IF *.. ,

THEN in the action steps of---:i rIOWchart procedure *

• Salem Unit 1/2 58 Rev. 5

AD-2

• (10) Use of WHEN **. , THEN is as follows:

(a) WHEN .*.* , THEN is used only in retainment steps to identify a condition upon which an action is contingent, where the condition may occur later in the procedure.

(b) The operator is to proceed in the flow path, but return to the retainment step when the condition occurs.

e. Use of Certain Terms (1) When bezels are referred -to the word "illuminated" should be used.

(2) When lights are referred to, the work "lit" should be used.

(3) The word AVAILABLE should be used in preference to OPERABLE, as in:

ARE STEAM DUMPS AVAILABLE

• f.

(4) The variant THRU should be used consistently instead of THROUGH to save space in the flowchart symbols.

YES/NO Question Format When the operator is given an action to perform followed by a question, state the desired condition in the question, not the result of the action. ~-

START 12 RHR PUMP NOT

• Salem Unit 1/2 59 Rev. 5

• l AD-2

• g. Methods of Emphasis in Flowcharts Because flowchart steps are in full capital letters, other methods of emphasis, quotation marks and* underlining should be used.

(1) Quotation Marks Quotation marks should be used when identifying alarms and positions of switches. For example:

PLACE CONTROLLER IN "AUTO" Each time the verb PLACE or POSITION is used, quotation marks should be used to highlight the object. Also, when a question in a decision symbol concerns an alarm, quotation marks should be used for the alarm title. For example:

IS "LO-LO LEVEL" ALARM LIT (2) Underlining

• 0 0

Underline IF .. ~, THEN and WHEN **. ,

THEN in al~conditional statements.

Underline logic words AND and OR when joining condition"S"Or actIOns in a step or vertical list. For example:

SUBCOOLING LESS THAN 10°F AND RCS LESS THAN 225 PSIG (450 ADVERSE) 0 Underline words and phrases that require additional emphasis.

Examples:

ARE BOTH RHR PUMPS RUNNING DO NOT EXIT THIS PROCEDURE BEFORE STEP 15

• Salem Unit 1/2 60 Rev. 5

AD-2

• h. Abbreviations and Acronyms in Flowcharts Words should not .be abbreviated unless required by space limitations. As* a guideline for formulating questions for decision symbols, the following diagram shows the maximum number of letters/spaces allowable on each line in decision symbols:

Use the following specific guidelines:

0 Acronyms commonly used by operators, such as RCP and MSIV, should be used instead of spelling out the acronym. These acronyms shall be made plural by adding a lower case "s". Example: RCPs.

0 Engineering*unit abbreviations such as GPM and PSIG should be used.

0 The abbreviation PZR is preferable to PRESSURIZER due to space limitations.

0 Any abbreviations and acronyms used shall be listed in AD-6, "List of Abbreviations and Acronyms."

5.4 Abnormal Operating Procedures 5.4.1 Designation

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 .

• Salem Unit 1/2 61 Rev. 5 MASTER*

AD-2 c* A sequential number will follow the system designator to specifically identify each individual AOP.

d. As such, each individual AOP will have a unique identifier, for example, AOP-RCS-1, AOP-CC-4.

5.4.2 Format Arrangement

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

NOTE The flowchart format described in Section 5.3 may be used for AOPs.

(1) The dual column approach shall begin with the Immediate Actions section of the procedure (refer to Subsection 5.4.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 to the action statement is not obtained and to provide supplementary information and notes. Action statements resulting from decision steps are also plac~d in the right hand column.

(2) The single column approach shall be used only for the first section of the procedure (refer to Subsection 5.4.3 below).

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

• Salem Unit 1/2 62 Rev. 5

,' AD-2

• 5.4.3 Format Organization

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

(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 will include only those alarms, indications, operating conditions, procedure referrals, or other unique symptoms that the operator is to use in decidi.ng to use the procedure. It is neither required or desired, for example, to list all alarms associated with a given condition.

(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 indications of an abnormal condition.

(b) 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~

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

(d) This section shall contain no signoff spaces.

Salem Unit 1/2 63 Rev. 5

AD-2

• (3) Section 3.0 (a)

SUBSEQUENT ACTIONS This section shall contain those

'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 abnormal conditions.

(b) This section may include supplementary information, cautionary information, or notes.

(c) This section shall contain no signoff spaces.

(4) Section 4.0 ATTACHMENTS LIST (a) This section shall identify, by listing, each attachment (e.g.,

graph, figure, or table) to the procedure.

(b) The AOP shall contain no check off sheets.

(5) Continuous Action Summary (CAS) Pages (a) Continuous Action Summary pages contain actions that may become necessary at any time during the performance of an AOP.

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

(c) CAS pages are not used opposite pages containing only Immediate Action steps of any AOP *

• Salem Unit 1/2 64 Rev. 5

'MASTER

AD-2

• (d)

(e)

CAS pages shall be identical throughout a given procedure.

A three columfi format is used for the CAS pages. The left column contains a brief summary of the action required. The middle column states the condition requiring the action.

(f) A step reference, for the procedure in use, is placed to the extreme right of the condition. If the action is not referenced 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) Carryover actions should be limited to those items 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.

5.5 Operating Procedures 5.5.1 Designation

a. The designation for Operating Procedures shall be OP.

b. A second level designator for each Operating Procedure shall immediately follow the OP acronym. This second level designator shall identify the system that the Operating Procedure is applicable to, for example, RHR; RMS, TAC, 4KV.

c. A sequential number will follow the second level designator to specifically identify each iridividual Operating Procedure as classified *

• Salem Unit 1/2 65 Rev. 5

AD-2

• d. As such, each individual Operating Procedure will have a unique identifier. As examples:

(1) Two Operating Procedures dealing with RHR system operations would be shown as OP-RHR-1 and OP-RHR-2.

(2) Three Operating Procedures dealing with FP system operations would be shown as OP-FP-1, OP-FP-2, and OP-FP-3.

5.5.2 Format Arrangement

a. The single column (i.e., standard sentence approach) format should normally be used in 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 to the action statement is not obtained and to provide supplementary information and notes.

(2) The single column approach shall 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."

• Salem Unit 1/2

~***.

66 Rev. 5

AD-2

• 5.5.3 Format Organization

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

(1) Section 1.0 PURPOSE (a) This section shall provide ~

brief and concise statement that describes what is intended to be accomplished.

(b) 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 Normal Operation of the CFCUs .

1.1. 2 Operation of the CFCUs without Service Water available.

The intent is to have Subsection 1.1 serve as an index listing those operating methods addressed by the procedure. *

(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 Subsection 1.1 and will be numbered as the next subsection.

For example:

1.2 This procedure is performed IAW the requirements of OD-71.

• Salem Unit 1/2 67 Rev. 5

AD-2

• (2) Section 2.0 (a)

INITIAL' CONDITIONS This section shall detail the requirements and conditions that must be met prior to performance of the procedural steps (i.e.,

Section 5. 0) *

(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 sheet) to the procedure.

(b) Check off sheets, when used, shall contain a signof f 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 signoff space for the appropriate 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 subsections in Section 5.0 shall be numbered so that they conform to the numbering of subsections in Section 1. For example, in the case shown above, Subsection 5.1 should read:

5.1 NORMAL OPERATION OF THE CFCUs

• Salem Unit 1/2 68 Rev. 5

' . AD-2

• The procedural steps will then start with 5.1.1 for this operating method. When all steps

, for this condition have been

• listed, a new subsection shall begin which conforms to the next operating method listed in Section 1, with the procedural steps numbered as above. The two digit subsection 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) Signof f spaces in the body of the procedure are not required nor desired.

5.6 Surveillance Procedures

• 5.6.1 Designations

a. The designation for technical specification related Surveillance Procedures assigned to the Operations Department shall be SP(O).

The designation for non-technical .

specification surveillances, called Periodic Inspection/Surveillance, shall be PI/S.

b. For Surveillance Procedures (Operations), I, the technical specification surveillance I!

requirement number (main number if more than ~

one requirement) that the Surveillance Procedure (Operations) was written to fulfill shall immediately follow the Surveillance Procedure (Operations) designator to specifically identify each individual 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 *

• Salem Unit 1/2 i*

69 Rev. 5

AD-2

• c* For Periodic Inspection/Surveillances, each shall be numbered as follows:

(1) A second level designator for each Periodic Inspection/Surveillance shall immediately follow the PI/S acronym.

This second level designator shall identify the system to which the Periodic Inspection/Surveillance is applicable, for example, FP, CA, or CN.

(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/Surveillances dealing with FP system inspections would be shown as PI/S-FP-1 and PI/S-FP-2 .

• 5.6.2 (b) One Periodiq Inspection/Surveillance dealing with a CA system surveillance would be shown as PI/S-CA-1.

Format Arrangement

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 if it more adequately presents the procedure .

• Salem Unit 1/2 70 Rev. 5

AD-2

• b* When the dual column format is used for a Surveillance Procedure (Operations) or Periodic Inspection/Surveillance:

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

(b) The right hand column shall be used to present contingency actions for use when the response to the action statement is 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) *

• 5.6.3

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

Format Organization

a. The format oiganization and content requirements for each Surveillance Procedure (Operations) and Periodic Inspection/Surveillance are as follows:

(1) Section 1.0 PURPOSE (a) This section shall provide a brief and concise statement that describes what is intended to be accomplished *

• Salem Unit 1/2 71 Rev. 5

AD-2

• (b) The purpose statement will be .

numbered so that a procedure which addresses more than one operating method of the system or component that meets the

. surveillance requirement can be readily identified, for example:

1.1 This procedure provides the instructions necessary to perform the foliowing:

1.1.1 Determine the Identified RCS Leak Rate.

1.1.2 Determine the Unidentified RCS Leak Rate.

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

(c) With regard to Surveillance Procedures (Operations), the specific technical specification surveillance requirements (i.e.,

numbers) that the procedure is written to meet shall be identified in the next subsection. The frequency requirement for the surveillance l

procedure will also be included here.

.;J.

( 2) Section 2.0 INITIAL CONDITIONS (a) The section shall detail the requirements and conditions that must be met prior to performance of the procedural steps (i.e., Section 5. O) *

• Salem Unit 1/2 72 Rev. 5

.. AD-2

• (b) Each initial condition shall have a signoff space for the operator to initial after completing the step. The "signoffs" 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.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 sheet) to the procedure.

(b) Check off sheets, when used, shall contain a signof f 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 signof f space for the appropriate 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 .

• Salem Unit 1/2 73 Rev. 5

AD-2

• (b) The subsections in Section 5.0 shall be numbered so that they conform to the numbering of subsections in Section 1. For example, in the case shown above, Subsection 5.1 should read:

5.1 DETERMINE THE IDENTIFIED RCS LEAK RATE The procedural steps will then start with 5.1.l for this operating method. When all steps for this condition have been listed, a new subsection shall begin which conforms to the next operating method listed in Section 1, with the procedural steps numbered as above. The two digit subsection headings shall be in all caps as a means of identifying that a different operating method is now being addressed.

(c) Each pertinent instructional step shall have a signoff space for the operator to initial after completing the step. The signof f s 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.

(d) This section may include supplementary information, cautionary information, and notes *

• Salem Unit 1/2 74 Rev. 5

AD-2 5.7 Alarm Response Procedures 5.7.1 Designation

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

(1) A second level designator for each Alarm Response Procedure shall immediately follow the ARP acronym.

This second level designator shall identify the system which the alarm addresses. For example:

(a) The Reactor Coolant System shall be identified as RCS.

(b) The Safety Injection System shall be identified as SJ.

An exception will be made in the case of those alarms on local panels where no system designation 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 alarms shall be identified as BZL.

(d) The auxiliary alarm typewriter alarms shall be identified as AUX *

• Salem Unit 1/2 75 Rev. 5

~1ASTER

AD-2

• (3) A fourth level designator shall be used to identify the specific alarm within a given alarm type. No specific approach shall be defined herein; however, whatever approach is used shall be used consistently. Some example approaches are:

(a) For control room overhead annunciator alarms, the grid location should be used (e.g.,

AS , C3 2 , D15 ) *

(b) For local panel annunciator alarms, the panel number should be used (e.g. 470, 104, 661). In addition, the grid location could also be specified. *

(c) For control console bezel alarms, the bezel drawing number could be used.

(d) For auxiliary alarm typewriter alarms, the computer address point should be used *

(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-Al5.

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

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

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

• Salem Unit 1/2 76 Rev. 5

AD-2

• 5.7.2 Format Arrangement

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

b. Specific guidance regarding page layout is provided in AD-4, "Typist Guide."

5.7.3 Format Organization

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

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

(2) ENTRY CONDITIONS (a) This section shall contain a list of the conditions under which the procedure is us~d.

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

(3) AUTOMATIC ACTIONS (a) This section should contain those actions that the operator should be verifying upon receipt of the alarm 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 *

• Salem Unit 1/2 77 Rev. 5

AD-2

• (5) SUPPLEMENTAL INFORMATION (a)

(b)

The inclusion of this section is optional.

This section, when included in an Alarm Response Procedure, can be used to detail such information as reference documents, bistable numbers, and equipment locations.

b. Signature or signoff spaces in Alarm Response Procedures are neither required nor desired.

END OF PROCEDURE FINAL PAGE

• Salem Unit 1/2 78 Rev. 5

AD-2 TABLE 1

• ACTION VERBS 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 DEFINITION/USAGE EXAMPLE Actuate To set into action or motion, typically an automatic action.

"ACTUATE Containment Spray."

Adjust To regulate or to bring to a more satisfactory state. *

"ADJUST Seal Pressure Control Valve 1CV71 ..* "

Align To bring into line or alignment; to come into precise adjustment or correct relative position.

"ALIGN the valves in accordance with Table l."

Allow To permit a stated condition to be achieved prior to proceeding *

"ALLOW discharge pressure to stabilize."

Announce *To make known publicly; "ANNOUNCE twice on Station PA *.. "

Arm To equip or ready for operation or action.

"ARM the POPS."

Attach To fasten one thing to another.

"ATTACH a tygon tube to the cold leg drain."

Block To introduce an electronic inhibit on a logic train; the act of obstructing.

"BLOCK SEC at 2PR1 for affected Vital Bus."

Borate To add boric acid.

"BORATE RCS."

Break To destroy the unity or completeness of; to crack, to pierce.

"BREAK Vacuum."

Bypass To detour; to use any route connecting two points other than the route normally used.

"BYPASS RH2 interlock as follows .** "

• Salem Unit 1/2 TAB 1-1 Rev. 5

AD-2

• VERB Calculate DEFINITION/USAGE EXAMPLE To determine by cqmputation.

"CALCULATE a boron addition to raise RCS boron to 100 ppm greater than the Cold Shutdown boron concentration."

Check To determine present status; to compare with a procedural requirement.

"CHECK SI Pumps as follows: *.* "

Circle To draw a circle around.

"CIRCLE items not operating properly."

Clear To move people and/or objects away from.

"CLEAR 21 through 24 SJ54 Breakers."

Close To change the physical position of a mechanical device so that it prevents physical access or flow or permits passage of electrical current.

"CLOSE Valve 1FP142."

Complete To accomplish specified procedural requirements.

"COMPLETE Steps 7 through 9 of Section 5.0."

Consult To ask for advice, to take counsel; to refer to.

"CONSULT TSC for long term recovery actions."

Continue To do or cause to do the same thing without changing or stopping.

"CONTINUE attempts to restore Secondary Heat Sink."

Control To exercise restraining or directihg influence over; to fix or adjust the time, amount, or rate of; to regulate.

"CONTROL SG levels as follows *** "

Cool Down To make or become lower in temperature.

"COOL DOWN RCS to less than 547°F using unaffected SGs."

Coordinate To bring into a commmon action, movement, or condition; to harmonize.

"COORDINATE Gas Turbine operation with Load Dispatcher."

• Salem Unit 1/2 TAB 1-2 Rev. 5 ER

AD-2

• • VERB Decrease DEFINITION/USAGE EXAMPLE To cause to grow .progressively less.

"DECREASE steam generator levels to 33%."

De-energize To remove the power supply from.

"DE-ENERGIZE affected SEC."

Defeat To prevent the successful outcome of.

"DEFEAT 2nd Level Undervolt Protection".

Degas To remove dissolved gas from a liquid.

"DEGAS RCS IAW EOP-APPENDIX-5".

Depress See PRESS.

Depressurize To release gas or fluid pressure from.

"DEPRESSURIZE all intact SGs as follows: .*. "

Determine To find out; to ascertain.

"DETERMINE required subcooling from the following table: *** "

Direct -To order or require.

"DIRECT Chemistry to sample *** "

• Discharge Drain To give outlet or vent to a fluid or other contents.

"DISCHARGE the tank to .*. "

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

Dump To release steam to the main condenser or atmosphere while bypassing the main turbine.

Ex: Dump steam to atmosphere using atmospheric relief valves 11 thru 14 MSlOs.

Energize To apply voltage to.

"ENERGIZE Source Range Channel."

Establish To make arrangements for a stated condition.

"E.STABLISH communication with the control room."

Evaluate To assess; to determine the importance, size, or nature of; to appraise; to give a value to based on collected data.

"EVALUATE Status Trees *** "

Equalize To make equal or uniform.

"EQUALIZE charging and letdown flows as follows: ..* "

Salem Unit 1/2 .TAB 1-3 Rev. 5

• - AD-2

• VERB Feed Fill DEFINITION/USAGE EXAMPLE To keep supplied.

"FEED to only 1 SG."

To raise the level of.

"FILL the Accumulator in accordance with .** "

Flush To cause to flow to cleanse or wash out.

"FLUSH the discharge piping by opening 1WL156, 1WL56, and lDRS for 2 minutes."

Go To To branch to another step, section, or procedure. To proceed to; to transport oneself to a given destination.

"GO TO Step 10.2.3."

Hold To sustain or keep as in position or amount.

"HOLD press at 1200 PSIG or greater."

Identify To determine; to establish the identity of.

"IDENTIFY affected SG."

Implement To carry out; to accomplish.

"IMPLEMENT the Functional Restoration with the highest priority."

Increase To cause to grow progressively greater.

"INCREASE power at 3% per hour or less."

Initiate To begin a process, usually involving several steps or actions.

"INITIATE RCS feed and bleed."

Inject To- introduce a new element; to drive a fluid.

"INJECT accumulators slowly as follows: "

Insert To put or thrust in, into, or through.

"INSERT control rods."

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

INSPECT visually for leaks."

Install To place and attach; to reinstall.

"INSTALL SW to AFW spoolpiece."

• Salem Unit 1/2 TAB 1-4 Rev. 5

. . Ii':

AD-2

• VERB Isolate Investigate DEFINITION/USAGE EXAMPLE To shut off or remove from service.

"ISOLATE SI Accumulators."

To search or inquire into.

"INVESTIGATE cause of leak as follows *** "

Limit To restrict to an amount or quantity established as the greatest permissible.or to the furthest extent, range, or degree.

"LIMIT flow to a maximum *** "

Log To enter into a record of operations or progress.

"LOG. the time Mode 4 was entered."

Maintain 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."

Minimize To reduce to the smallest amount or degree.

"MINIMIZE steam release from affected SG."

Monitor To watch, observe, or *check, especially for a special purpose; to keep track of, regulate, or.control the operation of.

"MONITOR Source Range Neutron leve1 while filling the RCS."

Notify To make known, give notice of, or report an occurrence.

"NOTIFY the Chemistry Department to sample the batch for boric acid concentration." I Obtain To get. I.

• I "OBTAIN current Containment hydrogen reading."

Open To change the physical position of a mechanical device, such as a valve or door, to the unobstructed position that permits access or flow or prevents passage of electrical current. *

"OPEN 11SJ49 and 12SJ49 RHR Discharge to Cold Legs."

Operate To control equipment to accomplish a specific purpose; to cause to function.

"OPERATE valves from local panel."

Salem Unit 1/2 TAB 1-5 Rev. 5

"I/ AD-2

• VERB Perform DEFINITION/USAGE EXAMPLE 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."

Place To put or set in a desired location or position.

"PLACE valves ih position required by 2RP4."

Plot To represent graphically.

"PLOT cooldown on Operations Log 4."

Position To put.in the proper or appropriate place.

"POSITION controller switch *** "

Prepare To make ready; put in readiness.

"PREPARE containment for Head Venting as follows: .** "

Press To act upon through thrusting force exerted in contact; to push.

"PRESS blower start button."

• Pressurize Prevent To apply pressure within by filling with gas or liquid.

"PRESSURIZE first stage chamber."

To keep from happening.

"PREVENT AUTO Start of 21 RHR Pump as fallows: ... "

Proceed To go on in an orderly, regulated way.

"PROCEED as directed by TSC."

Purge To make free of an unwanted substance::, such as an impurity or foreign material.

"PURGE the PRT by performing the following steps."

Realign To align again.

"REALIGN gas analyzer as follows: *** "

Record To document the specified condition or characteristic.

"RECORD discharge pressure."

• Salem Unit 1/2 TAB 1-6 Rev. 5

\..-,

AD-2

• VERB Release DEFINITION/USAGE EXAMPLE To set free from .restraint or confinement.

"RELEASE the tank to the Circulating Water System as described in Step 5.2."

Remove To take off, move away, or eliminate.

"REMOVE lockout for 21SJ54 at 2PR4."

Repeat To make, do, or perform again; to recapitulate.

"REPEAT emergency loading reset for affected SEC."

Repressurize To apply pressure again.

"REPRESSURIZE first stage chamber."

Reset To set again.

"RESET FW Isolation as follows: *** "

Restore To bring back or put back into a former or original state.

"RESTORE condenser IAW IOP-2, "Cold Shutdown to Hot Standby."

Resume To begin again after cessation or

• interruption.

"RESUME Cooldown."

Return To To go back to a previous step in the procedure in effect.

"RETURN TO Step 3.26."

Review To examine again; to go over or examine critically or deliberately.

"REVIEW the following ... " I 11 Run To operate; to maintain or control in an  !:

operating state. ' I'

! i "RUN 22 recombiner."

Run Back To reduce load on a turbine in a controlled manner.

"RUN BACK turbine load as follows: *** "

Sample To test or to judge the quality.

"SAMPLE the PRT for oxygen concentration."

Scan To look through or over, usually rapidly.

"SCAN the Primary Core Exit TCs .** "

• Salem Unit 1/2 TAB 1-7 Rev. 5

AD-2

• VERB Select DEFINITION/USAGE EXAMPLE To take or choose. by preference from a number or group.

"SELECT the tank to be recirculated on the Low Level Cutoff Selector Switch."

Send To direct, order, or reques~ to go.

"SEND HP to area of high radiation to determine cause."

Set To physically adjust an adjustable feature to a specified value.

"SET channel R22 HI alarm to 25 mr/hr."

Shift To change mode of operation.

"SHIFT 2CV134 to RCDT or VCT."

Shut Down To perform operations necessary to cause equipment to cease or suspend operation; to stop.*

"SHUT DOWN non-Safeguards header loads."

Stabilize To become stable, firm, steady.

"STABLIZE RCS Press."

• Start To originate motion of an electric or mechanical device directly or by remote control.

"START the Positive Displacement Charging Pump."

Station To assign a person to stand and remain at a certain place.

"STATION a person at the thermocouple panel."

Stop To terminate operation.

"STOP the Positive Displacement Charging Pump."

Supply To provide; to make available.

"IF any AFST level not increasing, THEN SUPPLY AFST IAW OP III-10.3.1, Auxiliary Feedwater System Operation."

_Survey To examine as to condition, situation, or value.

"SURVEY the resin discharge line to determine background radiation levels before initiating resin removal."

Salem Unit 1/2 TAB 1-8 Rev. 5

,..., AD-2

• VERB Tag DEFINITION/USAGE EXAMPLE To provide with an identifying or indicating symbol (a cardboard, plastic, or metal marker used for identification or classification); to label; to attach or connect a tag to; to mark.

"TAG 21 through 24 SJ54 breakers."

Terminate To end, especially a process or procedure.

"TERMINATE SI."

Test To put to test for analysis or diagnosis; to proof; to try.

"TEST POPS as follows: .*. "

Throttle To operate a valve in an intermediate position to obtain a certain flow rate.

"THROTTLE 2CC71 as required to maintain temperature."

Transfer To cause to pass from one to another.

"TRANSFER the boric acid solution from the Concentrate Holding Tank to the Boric Acid Storage Tanks."

Trip To manually activate a semi-automatic feature.

"TRIP the reactor."

Turn On To cause to operate or flow.

"TURN ON pressurizer heaters."

Update To revise to include latest information or data.

"UPDATE TRIS."

Use To avail oneself of; to employ; to utilize.

"USE Core Exit TCs for RCS temp."

Vent To permit a gas or liquid confined under pressure to escape at a vent.

"VENT the pump."

Verify. To observe an expected condition or characteristic.

"VERIFY discharge press is stable at 200 PSIG. II Usage: VERIFY is not used in EOPs or AOPs. The YES/NO decision step and IF .* _.,

THEN contingency are substituted to streamline the decision making process.

Salem Unit 1/2 TAB 1-9 Rev. 5

• )

AD-2 FIGURE 1 FLOWCHART EXAMPLE L !lGP*tatl'-4 5!!!!!!!!

" ** actu&ti* eaue 111111*

11111 "'8CIJU!l. tlllll

• to

• • • • • • "*'* **ac**

1811'

• Wiit 1-Cll*,

• 1111' ..

~

• lllt C8ftllU tMl5 _ . . .

,*.,....... *-'lllU&.

lllllLllU'I I -

cu1111.1t1* ~.

• D GP

--ill llCM&tl I'll! Ll'llL ti 1\1 USI* - * * -

L LU-uua.11t1 acs s.ecoa.1*

L IC&llJI * - " '

• r. J.I L

' HU& l!fl COCllllCllll5 P*

11 . . 11118 "' llCI' UV GP 11*1.J.1,"M&tl*

tOCllMI ~ OPU*ll*'

~" Pia Ll'llL !!51 ll*OClll . . . . .

Ull&IKD.

!!!.!! l'UP 111111 lttp J. I tU Sl .. I .U IJ !!' II

,..,. "' llCI' II 11181 llCI' ,,  !!! .. iuiL&&l llU L '----,----' lll"91 10 iiii I

• Salem Unit 1/2 fIG 1-1 Rev. 5

'\ ..-l)

AD-2 FIGURE 2 FLOWCHART SYMBOLS ENTRY CONDITION Contains the. condition requiring entry into and execution of this procedure.

ACTION STEP Contains the procedural actions. It also defines contingency action steps (IF *** , _THEN)

RETAINMENT STEP Contains conditions and contingency

• actions the operator must remember while performing the steps that follow.

DECISION.STEP Contains a question to which the answer determines the next step *

• CONCURRENT STEP Requires the operator to enter the designated procedure and perform the stated actions while continuing in the existing flow path.

• ENTRY ARROW Designates the entry point for this procedure when directed by the procedure in the arrow.

EXIT ARROW Requires the operator t leave the flow path at that point. If required*, it shows the procedure number and/or step that must then be entered.

OPERATOR CAUTION CAUTION Contains a specific Caution applicable to the following step *

• Salem Unit 1/2 FIG 2-1 Rev. 5

. *' ~' "' .I q

I, AD-2 i

• I FIGURE 2

• FLOWCHART SYMBOLS (continued)

Ii I

'II i

CONTINUOUS CAUTION Contains a Caution the operator must observe while performing all remaining steps.

OPERATOR NOTE

(_N-OTE_) Contains a specific Note applicable to the following step *

.*CONNECTOR SYMBOL Used at the bottom of one path and the top of the next to indicate to the operator that the procedure continues.

Connector symbols are lett~red sequentially throughout a procedure and are used between pages of the same procedure *

• Salem Unit 1/2 FIG 2-2 Rev. 5 L

MASTER