Administrative Procedure ADM 98, 'Emergency Usage Procedures … · 2019-12-27 · ADM-98 Page 1...

V!'RG!N!A ELECTRIC ANV POWER COMPANY SURRY 'PCXl!:R ST A T1 ON

1'ROCEVUR:

ADMINISTRATIVE PROCEDURE

TITLE: EMERGENCY USAGE PROCEDURE WRITERS GUIDE

LIST O'F cmm VE RE V!S! 01\!S:

SEITTO>J tJATE

Table of Contents MAY 1 8 1983

1.0 MAY 1 8 1983

2.0 MAY 1 8 1983

3.0 MAY 1 8 1983

4.0 MAY 1 8 1983

5.0 MAY 1 8 1983

6.0 MAY 1 8 1983

7.0 MAY 1 8 1983

8.0 . MAY l 8 1983

TABLE 1 MAY 1 B 198J

TABLE 2 MAY 1 8 1983

TABLE 3 MAY 1 8 1983

QUALITY CONTROL REVIEW:

~~~

i'ROCE'PURE ( l) IIIUMB:R: ADM 9 8

'PAT:: MAY 1 8 1983 (2 )

(3) UNIT f: 1 & 2

( !; )

( 5)

(6)

{7) (8)

'PATE:

(9) (10)

'PATE:. ~-/g--f3

Ai'P'ROVEt> STAT"1 NLJCLE~R /?AFETY ~ 01'ERA 111,JG COMM1ITEE: ( ll)

c:y .!\ nA- 'PA TE:

( 1.2)

1/iAY 1 8 1983

1~8307120392 830701. \PDR ADOCK 05000280 _,F PDR

•

1.

2.

3.

4.

..

SECTION

i

VIRGINIA ELECTRIC AND POWER COMPANY

SURRY POWER STATION

UNITS 1 AND 2

EMERGENCY USAGE PROCEDURE WRITERS GUIDE

FOR REFERENCE ONLY TABLE OF CONTENTS

ADM-98 05-18-83

PAGE

REFEREN'CES • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • 1

PURPOSE ••••••• ~ •••••••••••••••••• ~ • • • • • • • • • • • • • • • • • • • • • • • • • 1

SCOPE ••••••••••••••••••••••••••• -. • • • • • •. • • • • • • • • • • • • • • • • • • • • 1

DEFINITIONS ••••••••••••• ·• • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • 1

5. DESIGNATION AND NUMBERING

5.1 PROCEDURE DESIGNATOR ................................ 2

5 • 2 PROCEDURE NUMBER • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • 3

5 • 3 REVIS ION NUMBER • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • 3

5.4 INDICATION OF REVISION LOCATION••••••••••••••••••••• 3

6. FORMAT

6.1 COVER SHEET FORMAT .................................. 4

6.1.1

6.1.2

6.1.3

6.1.4

OPR: Supt. Operations

"' Procedure Identification••••••••••••••••••• 4

Page Num.ber • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • 5

Purpose and User

Entry Conditions

...........................

........................... 5

5

SECTION

6 .1.5

6.1.6

ii

TABLE OF CONTENTS

(continued)

ADM-98 . 05-18-83

PAGE

Revision Record............................ 5

Approval • . • • . . • • . . • • . . • . • • • . • . . . . . • . . • . . • . . 5

6.2 PROCEDURE INSTRUCTION FORMAT........................ 7

6.2.1

6.2.2

Page Identification and Numbering.......... 7

Instruction Steps and Step Numbering....... 9

6 • 3 ATTA~ FORMAT • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • 9

6.3.1

6.3.2

"Attachment Identification and Numbering.... 10

Attachment Revision Level and Page Numbering 11

7. WRITING INSTRUCTIONAL STEPS ·

7 .1 DUAL COLUMN FORMAT • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • 14

7.2 ACTION/EXPECTED RESPONSE COLUMN••••••••••••••••••••• 15

7.3 RESPONSE NOT OBTAINED COLUMN•••••••••••••••••••••••• 16

7.4 STEP NUMBERING AND INDENTATION•••••••••••••••••••••• 18

7. 5 STEP LENGTH AND CONTENT • • • . • • • • • • • • • • • • • • • • • • • • • • • • • 19

7.6 LEVEL OF DETAIL••••••••••••••••••••••••••••••••••••• .20

7.7 INSTRUCTION TENSE AND VOICE••••••••••••••••••••••••• 23

7.8 USE OF ACTION VERBS••••••••••••••••••••••••••••••••• 24

7.9 OBJECTS OF ACTION VERBS••••••••••••••••••••••••••••• 25

7.10 CONDITIONAL STATEMENTS AND LOGIC WORDS.............. 27

7.11 CAUTION STATEMENTS•••••••••••••••••••••••••••••••••• 31

7.12 NOTES •••••••••••••••••••••••••••••••••••••••••••••••. 34

7 • 13 E!!E>HAS IS • • • • • • • • • • • • • • • • • • • • . • • • • • • • • • • • • • • • • • • • • • • • 35

7.14 CHECK-OFF PROVISIONS•••••••••••••••••••••••••••••••• 36

7.15 SYSTEM RESPONSE••••••••••••••••••••••••••••••••••••• 38

FOR REFERENCE ONLY

•

iii

TABLE OF CONTENTS

(continued)

SECTION

7.16 IDENTIFICATION OF EQUIPMENT, CONTROLS, AND DISPLAYS

7.17 PLANT INSTRUMENTATION VALUES

7.18 CALCUL.ATIONS •••• c- • ••••••••••••••••••••••••••••••••••

7.19 LOCATION INFORMATION • • e e e e e e e D e O e e e e e • e • • e e • • e e e e e • a

7.20 STEP SEQUEN'CE •••••••••••••••••••••••••••••••••••••••

7.21 REFERENCING AND BRANCHING ........................... 7.22 PRINTED USER AIDS ............ • ...................... .

8. MECHANICS OF STYLE

8.1 SPELLING •.•...•••••••••.•••••••••.•.••••••••••••••••

8.2 HYPHENATION .......................................... 8.3 PUNCTUATION .........................................

8.3.1 Apostrophe ................................. 8.3.2 Brackets ................................... 8.3.3 Colon ...................................... 8.3.4 Comma ...................................... 8.3.5 Dash •••••••••••••••••••• ~ ••••••••••••• • • • • •

8.3.6 Parenthesis ................................ 8.3.7 Period ..................................... 8.3.8 Quotation Marks ............................ 8.3.9 Semicolon ................................. .

8.3.10 Slant Line ................................ .

8.4 VOCABUL.ARY ••••••••••••••••••••••••••••••••••••••••••

8.5 NUMERICAL VALUES .................................... 8.6 UNITS OF MEASURE ....................................

ADM-98 05-18-83

PAGE

39

41

43

44

45

46

50

52

52

53

53

53

54

54

54

54

55

55

55

55

55

58

59

FOR REFERENCE ONL V

•

•

•

iv

TABLE OF CONTENTS

(continued)

SECTION

8.7 ABBREVIATIONS, LETTER, SYMBOLS, AND

ADM-98 05-18-83

PAGE

ACRONYMS • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • 5 9

8.8 C~ITALIZATION •• ~ ....••••••..•••.•••••.••••••.••.••.

8.8.1

8.8.2

8.8.3

8.8.4

8.8.5

8.8.6

8.8.7

8.8.8

8.8.9

Organization, Institutions,

Companies, and Associations

Titles of Written Material •••••••••••••••••

·Titles of an Organization Structure ••••••••

Systems and Components •••••••••••••••••••••

Headings and Subheadings•••••••••••••••••••

Engravings and Legends •••••••••••••••••••••

System, Component, and Device

Identifiers •••••••••••••••••••••••••••••••.

Modes of Operation

Tables and Figures

9. MISCELLANEOUS ITEMS

9.1

9.2

9.3

9.4

9.5

10. TABLES

STATUS TREES ........................................ FOLDOtJTS ••••••••••••••••••••••••••••••••••••••••••••

TRANS·ITIONS •••••••••••••••••••••••••••••.••••••••••••

IMMEDIATE ACTIONS •••••••••••••••••••••••••••••••••••

REPRODUCTION ........................................

60

60

61

61

62

62

62

63

64

64

65

67

67

68

68

TABLE 1. Action Verb List ••••••••••••••••••••••• ~......... 1-1

TABLE 2. Abbreviation and Acronym List•••••••••••••••••••• 2-1

TABLE 3. Methods of Emphasis•••••••••••••••••••••••••••••• 3-1

TABLE 4. Unique Vocabulary•••••••••••••••••••••••••••••••• 4-1

f OR REFERENCE ONl Y

•

•

ADM-98 Page 1 05-18-83

1.0 REFERENCES

1.1 ADM 60

1.2 NUREG-0899, Guidelines for the Preparation of Emergency

Operating Procedures

1.3

1.4

1.5

INPO 82..;017, Emergency Operating Procedure Writing Guideline

WOG Writers Guidecfor Emergency Response Guidelines (Rev. O)

WCAP 10204, Emergency Response Guidelines Validation Program

2.0 PURPOSE

3.0

This writers guide provides guidance applicable to procedures intended

for use during other than normal conditions. Its purpose is to provide

administrative and technical guidance on the preparation of the Emergency

Response Procedure set (ERP) and Emergency Plan Implementing Procedures

(EPIPs).

SCOPE

This writers guide applies to the writing of all Emergency Procedures

(EPs) and their subprocedures, Function Restoration Procedures (FRPs),

Emergency Contingency Actions (ECAs), and Emergency Plan Implementing

Procedures (EPIPs). This scope may be extended at a future date.

4.0 DEFINITIONS

4.1 EMERGENCY USAGE PROCEDURES - as used in the guide, Emergency

Usage Procedures control or guide the actions of station

personnel responding to off-normal and stressful conditions.

These include, but are not limited to EPIPs, EPs, ECAs, and

FRPs.

4.2 EMERGENCY RESPONSE PROCEDURES - the set of Surry specific

procedures derived from the WOG Emergency Response guideline

set. These include EPs, ECAs, and FRPs and were developed in

response to NUREG-0737.

f OR REFERENCE ONLY

•

•

ADM-98 .Page 2 05-18-83

4.0 DEFINITIONS (continued)

4.3 EMERGENCY PROCEDURES - provide guidance for diagnosis and

recovery from design basis emergency conditions.

4.4 FUNCTION RESTORATION PROCEDURES - guide actions to address

challenges to plant critical safety functions.

4.5 EMERGENCY CONTINGENCY ACTION - offer guidance to address

specific events beyond design basis conditions.

4.6 EMERGENCY PLAN IMPLEMENTING PROCEDURES - station procedures

which govern actions to be taken by Surry Power Station

personnel for assessment and control during emergency or

specific off normal conditions.

5.0 DESIGNATION AND NUMBERING

5.1 PROCEDURE DESIGNATORS

Procedures of the Emergency Response Set will be written for

common usage by either unit. Emergency Plan Implementing

Procedures detail station actions 1 thus unit designators will

not be used. Procedures will be designated as follows:

a. Emergency Procedures - EP

b. Function Restoration Procedures - FRP

c. Emergency Contingency Actions - ECA

d. Emergency Plan Implementing Procedures - EPIP

Unit specific procedures may be developed and utilize this

writers guide IAW ADM 60. Uttit designators will be a single

digit number placed prior to the procedure number and separated

by a dash •

FOR REFERENCE ONLY

l

• 5.0

•

DESIGNATION AND NUMBERING (continued)

5.2 PROCEDURE NUMBER

ADM 98 Page 3 MAY 1 8 t983

A sequential number will follow the procedure designitor and

will consist of one digit, a decimal point, and two more digits.

Example: EPIP 1.01

2-AP-10.1

i 1~----~----Sequence Number

~-------------------Procedure Designator

Unit Designator ------------5.3 REVISION NUMBER

Two digits along with the abbreviation "Rev." will be used to

designate the revision level of the procedure.

Example: REV. 01

j T ...... ___________ Revision Level

l ...... ___________________ Abbreviation

5.4 INDICATION OF REVISION LOCATION

For use with the two column format addressed in this guide, the

location of a revision made in the left hand column of text will

be indicated by placing a change bar in the left hand margin

along side the change, and ~n the right hand column by placing a

change bar in the right hand margin along side the change.

FOR REFERENCE ONL V

• 6.0

•

•

FORMAT

ADM-98 Page 4 05-18-83

The following format is established for all Emergency Usage Procedures

to insure consistency.

The procedure will be organized in three basic sections, which are:

(1) the cover sheet, (2) the procedure instructions, and (3) the

attachments.

Although not precluded, the procedure should not contain any check-off,

signature, or initial spaces for the individual steps. A procedure

completion sign-off should be provided at the end of the procedure.

6.1 COVER SHEET FORMAT

Every Emergency Usage Procedure will have a cover sheet {see

Figure 1). The purposes for this cover sheet are: (1) to

identify the procedures, (2) to identify the revision level of

the procedure, (3) to state the purpose of the procedure, (4) to

identify the user of the procedure, (5) to detail the entry

conditions for use of the procedure, (6) to identify the dates

and scope of the most recent revision, and (7) to show the

proper approval of the procedure.

The cover sheet will consist of a preprinted form with

designated areas in which the above information can be inserted.

6.1.1 Procedure Identification

To identify the procedure, a descriptive title will be

used which should a!so designate the scope or covered

event. The procedure will also be identified by a

unique procedure designator and sequence number. A

unit designator will be included if requi!ed for unit

specific procedures •

FOR REFERENCE ONlY

• 6.0

•

•

ADM-98 Page 5 05-18-83

FORMAT (continued)

6.1.2

6.1.3

6.1.4

6.1.5

6.1.6

PAGE NUMBER

The cover sheet shall be numbered as Page 1 of ---PURPOSE AND USER

The purpose of the procedure will be stated in a short

descriptive paragraph which is concise and

comprehensive. The user of EPIPs will preferably be

identified by emergency title. If that is not

appropriate for other procedures, normal position/job

title will be used.

ENTRY CONDITIONS

A statement of entry conditions will be provided to

give the user a means for confirming he has chosen the

appropriate procedure for the given emergency

conditions.

REVISION RECORD

A revision record of the most recent revisions will be

used which will identify: (1) revision number, (2)

affected pages, and (3) date of the revision.

APPROVAL

The person responsible for maintenance of the procedure

will recommend approval by signing the procedure. QA

representative will~indicate approval by signing the

appropriate block. The Chairman of the Station Nuclear

Safety and Operating Committee will show approval by

signing and dating the procedure •

FOR REFERENCE ONLY

•

• '

' '

• i

NO. 97887240 REV.A

NUMBER

PURPOSE

USER

.

ENTRY CONDITIONS

REVISION RECORD

-

APPROVAL RECOMMENDED

ac REVIEW

FIGURE 1

VIRGINIA ELECTRIC AND POWER COMPANY SURRY POWER STATION

EMERGENCY USAGE PROCEDURES -- -

PROCEDURE TITLE

.,. '

(SAMPLE COVER SHEET)

FOR REFERENCE ""

APPROVED

- - ...

ADM 98 Page 6 MAY 1 8 1983

REVISION

PAGE

-

'

ONLY

DATE

CHAIRMAN STATION NUCLEAR SAFETY AND OPERATING COMMITTEE

• 6.0

•

•

f OR REFERENCE OMl ~ ADM-98 Page 7 05-18-83

FORMAT (continued)

6.2 PROCEDURE INSTRUCTION FORMAT -

Emergency Usage Procedure instructions will be written in dual

column format. The left hand column is designated for user

actions and expected responses. The right hand columri is

reserved for contingency actions to be taken if the preferred

actions cannot be performed or the expected response is not

obtained.

The procedure will not normally contain any check-off,_initial,

or signature spaces associated with the instructions, but these

are not precluded. Procedure sign-on date and time spaces may

be provided at the beginning or elsewhere in the procedure if

appropriate. Procedure completion sign-off, date, and time,

spaces will be provided at the end of the procedure. The

procedure may contain spaces to record required data.The.

procedure instructions will be typed on a preprinted form (see

Figure 2) which will also: (1) identify the procedure, (2)

identify the revision level of the page, and (3) identify the

page number.

6.2.1 Page Identification and Numbering

Each procedure instruction page will be identified by:

(1) the procedure designator and sequence number, (2)

the procedure titl~ (3) the revision number, and (4)

the page number specified as Page ____ of ___ • Unit

designator will be used as appropriate. This

information

will be typed in the areas provided at the

top of the preprinted form.

FOR REFERENCE ON[

' No. 97887210

NUMBER

STEP __ ..,.

FIGURE 2

PROCEDURE TITLE

-

ACTION/EXPECTED RESPONSE RESPONSE NOT OBTAINED

SAMPLE PROCEDURE PAGE

ADM 98 Page 8 MAY 1 I 1983

REVISION

PAGE

FOR REFERENCE ONLY

• 6.0

•

ADM-98 Page 9 05-18-83

FORMAT (continued)

6.2 PROCEDURE INSTRUCTION FORMAT (continued) .·

6.2.2 Instruction Steps and Step Numbering

The instruction steps should be short, concise,

identifiable instructions that give appropriate ~

directions to the user. They will consist of a high

level action statement followed by any specific

substeps needed to perform the high level action

statement.

Instruction steps will be numbered and indented as

follows:

1. HIGH LEVEL ACTION STATEMENT:

a) Substep

1) Substep

Every effort should be made to avoid using more than

the 1) level of indenting.

6.3 ATTACHMENT FORMAT

Attachments to a procedure may be used to provide supplemental

information needed by the user in the performance of the

procedure. Attachments may consist of either (1) figures, (2)

tables, (3) forms, or (4) subprocedures. A figure is

information presented in the form of a drawing or graph. A .;,

table is information presented in columnar arrangement. A form

is used to collect information by having items checked or ·

blanks completed.

f OR REfEREHCE ONLY

ADM-98 Page 10 05-18-83

6.0 FORMAT (continued)

6.3

.· ATTACHMENT FORMAT (continued)

Attachments will be placed at the end of the procedure using a

preprinted form (see Figure 3A & 3B) which will: (1) identify

the procedure, (2) identify the attachment, (3) identify the

revision level of~the attachment, and (4) identify the page ~

number of the attachment •.

6.3.1 Attachment Identification and Numbering

The procedure of which the attachment is a part will be

identified by using the procedure designator and

sequence number. A unit designator will be added to

unit specific procedures as required.

Attachments will be numbered sequentially by an arabic

number with sequence corresponding to the order of

reference in the instructional steps. The symbol"#"

and the abbreviation "No." are unnecessary and should

not be used. The number alone suffices. Example:

Attachment.!., Attachment 1,, etc.

Each attachment will be identified with a title which

is sufficient to describe the scope of the attachment.

Example: Table of Emergency Telephone Numbers, Initial

Notification Form., etc.

FOR REFERENCE ONLY

• 6.0

•

ADM-98 Page 11 05-18-83

FORMAT (continued)

6.3 ATTACHMENT FORMAT (continued)

6.3.2 Attachment Revision Level and Page Numbering-

The attachment will be identified by the revision

number. ~

The page number of the attachment will be specified as

Page~~ of ~~with these numbers being the number

of pages in the attachment, not the number in the

procedure.

FOR REFERENCE ONLY

No.97887220

NUMBER

• ATTACHMENT

•

•

FIGURE 3A

ATTACHMENT TITLE

(SAMPLE ATTACHMENT PAGE)

I

ADM 98 Page 12 MAY 1 8 1983

REVISION

PAGE

f OR REF EREt~Cf Ofil Y

.l NO 97887280

NUMBER

• ATTACHMENT

STEP __ _.

•

•

FIGURE 3B

ATTACHMENT TITLE

ACTION/EXPECTED RESPONSE

( SAMPLE ATTACHMENT PAGE)

ADM 98 Page 13 MAT l 8 1983

REVISION

PAGE

RESPONSE NOT OBTAINED

FOR REFERENCE ONLY

•

•

7.0 WRITING INSTRUCTIONAL STEPS

ADM-98 Page 14 05-18-83

Write short, concise, identifiable instructions that give appropriate

directions to the user and comprehension under stressful conditions.

Instructions are sometimes presented in the form of paragraphs

consisting of several action statements along with explanations,

descriptions, and conditional information associated with the actions.

The result is often a complex grouping of information that must be

unraveled by the user before it is understandable. Reading speed and

comprehension of written instructions are improved and the probability

of user error is reduced if instructions are presented in

well-structured, short, concise sentences of sentence fragments.

Ordinarily a step should contain a single action verb. The more

actions a step contains, the more likely it is that an action will be

overlooked •

7.1 DUAL COLUMN FORMAT

Emergency Usage Procedures will be written in dual column

format. This format presents instructional steps in short,

precise statements. The left hand column is designated for

preferred action steps and expected responses. The right hand

column is designated for contingency action steps to be taken if

the preferred actions step cannot be performed or if the

expected response is not obtained.

FOR REFERENCE ONl Y

7.0

•

ADM-98 Page 15 05-18-83

WRITING INSTRUCTIONAL STEPS (continued)

7.1

.· DUAL COLUMN FORMAT (continued)

An example of dual column format is:

Action/Expected Response

1 • IDENTIFY EVENT:

a) Event - FIRE

1) Initiate AP-XX,

Fire

AND

Continue with this

procedure

Response NOT Obtained

a) IF NOT fire, GO TO

Step 2.b of this

procedure.

Dual column format is a flow chart presented in words, with the

left hand column normally being the "yes" branch and the right

hand column normally being the "no" branch.

The same step numbering scheme is to be used for both right and

left columns of the instructions.

Parallel construction of paragraphs between columns of each step

of substep will be used.

7.2 ACTION/EXPECTED RESPONSE COLUMN

The left hand column in dual column format is the

"Action/Expected Response" column. The instructional steps to

be followed by the user to perform the procedure upder normal,

expected conditions are contained in this column •

FOR REFERENCE ONLY

7.0

• ADM-98 Page 16 05-18-83


7.2 ACTION/EXPECTED RESPONSE COLUMN (continued)

Steps in this column consist of a high level action ~tatement,

which describes the action to be performed. If required, the

high level statement is followed by substeps which give more

detail on how to perform the high level action statement

function. The following rules apply:

a. Expected responses to verification or check actions are

in all capital letters

b. If a verification or check step has multiple substeps,

then each substep will have its own expected response

c. If only a single task is required in a step, then the

high level action statement may contain its own

instruction or expected response.

d. The user should normally move down the left-hand column

if the expected response is obtained.

e. When the expected response is not obtained, the user

is expected to move to the right-hand column for

contingency actions.

7.3 RESPONSE NOT OBTAINED COLUMN

The right hand column in dual column format is the "Response Not

Obtained" column. The instructional steps in this column are

contingency actions to be performed if the normal action cannot

be performed or if the expected response is not obtained.

FOR REFERENCE ONLY

• 7.0

•


7.3 RESPONSE NOT OBTAINED COLUMN (continued)

ADM-98 Page 17 05-18-83

The steps in this column will not have a high level action

statement listed, since they are associated with the high level

action statement already listed in the left hand column • .,.

The following rules apply:

a. Contingency actions should identify directions to

override automatic controls and initiate manually what

are normally automatic functions.

b. The user is expected to proceed to the next numbered

step or substep in the left hand column after taking

contingency action in the right-hand column.

c. As a general rule, all contingent transitions to other

procedures take place out of the right-hand column.

Pre-planned transitions may be made from the action

column.

d. If a contingency action cannot be completed, the user

is expected to proceed to the next step or substep in

the left-hand column unless specifically instructed

otherwise. This rule should be considered in wording

subsequent left-hand column instructions.

e. If a contingency action must be completed prior to

continuing, that m~st be prescribed in the right-hand

column substep.

FOR REFERENCE ONLY

ADM-98 Page 18 05-18-83

7.0 WRITING INSTRUCTIONAL STEPS (continued

.· There should be contingency actions (or substeps) listed in this

column whenever a substep in the Action/Expected Response (left

hand) column calls for equipment operation, verification,

observation, confirmation, monitoring, or an other action which

"" might not be achieved. Obvious contingency actions need not be

listed.

7.4 STEP NUMBERING AND INDENTATION

Steps should be numbered to aid the operator in finding and

maintaining the correct sequence. Caution must be exercised in

using indentation as too much indentation can cause loss of

writing space and present vast "white" spaces to the user.

Also, the user may lose track of the subordination level when

the page is turned. Taken to an extreme, indentation can result

in one word lines and extensive hyphenation. Vertical reading

and reading of the text with excessive hyphenation is error

prone.

The following numbering and indentation scheme should be used:

1. HIGH LEVEL ACTION STATEMENT

a) Substep

1) Substep

Every effort should be made to avoid using more than the 1)

level of indenting.

• 7.0

••

WRITING INSTRUCTIONAL STEPS (continued

7.5 STEP LENGTH AND CONTENT

ADM-98 Page 19 05-18-83

Instruction steps should be concise and precise. Conciseness

denotes brevity; preciseness means exactly defined. Thus,

instructions should be short and exact. This is easily stated, ~

but not so easily done.

Guidelines which support these objectives are as follows:

a. Instruction steps should deal with only one idea.

b. Short, simple sentences or sentence fragments should be

used in preference to long, compound, or complex

sentences.

c. Complex evolutions should be prescribed in a series of

steps, with each step made as simple as practicable.

d. For instructional steps that involve an action verb

relating to three or more objects, the objects should

be listed.

e. Maintaining sequence of steps is assumed unless

otherwise stated.

f. Identification of components and equipment should be

sufficient for the knowledge level of the user.

g. Instruction content should be written to communicate to

the user.

h. Expected results anj performance method of routine

tasks need not be stated.

i. It is assumed that completion of a step is not required

to begin a subsequent step unless expresll1d. f \l\\ \\lfl~t\\tl ij

• 7.0

•


7.6 LEVEL OF DETAIL

ADM-98 Page 20· 05-18-83

Procedural detail shall be sufficient to support the user's

instructional needs and knowledge level. There is a fine line

between providing too much and too little detail.

Little benefit is~gained by providing the user instructions

concerning details that are within the scope of his training.

Some tasks are performed often enough that the detailed actions

required need not be stated. There is adequate assurance, for

instance, that the instruction "Verify AFW Pump () - FW-P-3B

RUNNING" to a Reactor Operator is sufficient, and any further

detail will merely detract from reading speed. Other tasks

associated with an emergency response may be performed so

infrequently that more detailed instructions should be provided

by the procedure.

Fewer errors of interpretation or omission result from

instructions with a high degree of detail. The more general

(low degree of detail) an instruction, the more the user will be·

forced to rely upon memory and training to perform actions.

Therefore, under the stress of an emergency, the users actions

can be subject to error.

The determination of the degree of detail required in a given

instruction is a function of the following factors: ""

a. criticality of task

b. user experience

c. level of stress anticipated

FOR REFERENCE ONLY

•

ADM-98 Page 21 05-18-83

7.0 WRITING INSTRUCTIONAL STEPS (continued)

7.6

.· LEVEL OF DETAIL (continued)

In a "layered" procedure (a procedure with both a higher and

lower degree of detail) the high level task (critical task) is

normally followed by sub-tasks with an increased degree of

detail.

The following guidance on level of detail is given:

a. The desired level of detail is one in which enough

details are presented that the user has all the

information needed, but not so many details that the

user become confused by superficial or redundant

information.

b. Avoiding too much detail is an important consideration

for procedures because of the need for timely response

and to minimize confusion.

c. Objects must be adequately identified to forestall

errors of identification or oversight.

d. Any limits on the actions should be stated

quantitatively, if possible.

e. Write procedures at a skill level appropriate for users

with the minimum expected skill.

f. The tier approach to level of detail may satisfy the

skill level requirement for plants with a good mix of ""

experienced and inexperienced users.

FOR REFERENCE ONLY

•

ADM-98 Page 22 05-18-83


7.6

.· LEVEL OF DETAIL (continued)

The determination of the proper level of detail is subject to

the writer's judgement. The following examples are intended to

reflect the matter of judgement:

Example 1 - I;adequate detail

a) Verify valve line-up

Example 2 - Adequate detail

a) Verify ventilation valve positions:

OPEN

HVC-27

HVC-28

CLOSED

HVC-31

HVC-18

Example 3 - Excessive detail

a) On Ventilation Control Panel

located on the backboards in

the Control Room (North side),

verify ventilation valve

positions by observing the

red "open" lights on HVC-27

and HVC-28, and the green

"closed" lights on HVC-31 and

HVC-18

FOR REFERENCE ONLY

-----. ----·-.···. ~


7.6 LEVEL OF DETAIL (continued)

ADM-98 Page 23 05-18-83

Example 4 - Tier approach utilizing two levels of-detail

a) REPORT EMERGENCY TO STATE

AND COUNTIES:

a) Use Insta-Phone

b) Read Message section

of Attachment l,

exactly as written

c) Record time message

completed on Attachment l 7.7 INSTRUCTION TENSE AND VOICE

a) IF NOT operable,

use commercial

telephone

Instructions are directive and need to be explicit. To be so,

care is needed in selection of tense and voice of verbs.

Tense of verbs generally indicates time. Selection of verb

tense should ensure that the indicated time is consistent with

the desired meaning.

Voice refers to the classification of verbs as active or

passive. The passive voice is made with the past participle and

some form of the verb "be". All other verb forms are active.

FDR REFERENCE DNl )'

• 7.0

•


7.7 INSTRUCTION TENSE AND VOICE (continued)

ADM-98 Page 24 05-18-83

Use the active voice whenever the instruction is directing the

user to perform an action. In the active voice, a person-action

goal pattern is expressed. The instruction is directive to the

person. The passive voice is recommended whenever the object,

or goal, is considered more important that the doer. Passive

voice tends to be more wordy than active and should not be used

for providing direction to a person.

7.8 USE OF ACTION VERBS

Use action verbs that are commonly used and understood by the

user. Select one verb to express a particular action and use it

consistently.

The verb is one of the foundation words of a sentence. Action

verbs express physical or mental action. The action verbs used

in a procedure must have the same connotation to every user.

Uniformity of the language used in procedures, especially the

verbs in action statements, will facilitate uniform and rapid

comprehension of written instructions. Because oral

communications are ordinarily required in order to perform a

procedure, the verbs used should be consistent with the oral

communication requirements. Verbs that sound alike but have

different meanings should be~avoided.

A list of action verbs has been developed (see Table 1). This

list presents the action verbs selected for use in all

Emergency Usage Procedures and provides their definitions.

I

FOR REFERENCE ONLY

• 7.0 WRITING INSTRUCTIONAL STEPS (continued)

7.9 OBJECTS OF ACTION VERBS

ADM-98 Page 25 05-18-83

When there are three or more objects of an action verb, list

them rather than imbed them in a sentence.

If the action verb in a step has three or more objects, (for ~

instance, valves to be operated), listing them separately from

the written text will reduce the potential of overlooking some

of the objects. The following guidance is provided:

a. If objects number three or more, list them in subgroups

to facilitate ease of reading and retention. In

general, limit subgroups to four items.

b. If lists are very long, consider the use of checklists

in tabular form, either within the instructions or as a

tabular attachment.

c. Spaces can be provided alongside object identifiers so

users can make marks to track completion of the action.

FOR REFERENCE ONLY

• 7.0

•

•


7.9 OBJECTS OF ACTION VERBS (continued)

The following are examples of poor practice:

ADM-98 Page 26 05-18-83

Example 1. - Number of objects in a sentence exceeds three

7. Open ventilation valves HVC-23, HVC-24, HVC-26, and

HVC-27.

Example 2. - Subgroup exceeds four items. Not easily

tracked for completion of action.

9. Close following ventilation valves:

HVC-24

HVC-26

HVC-27

HVC-30

HVC-31

HVC-34

HVC-35

The following are examples of good practice:

Example 1. - Recasting of poor example 1 to list form.

7. Open following ventilation valves:

HVC-23

HVC-24

HVC-26

HVC-27

f OR REfEREMCE ONl l .

• 7.0

•


7.9 OBJECTS OF ACTION VERBS (continued)

ADM-98 Page 27 05-18-83

Example 2. - Recasting of poor example 2 to subgroups not

exceeding four items with optional spaces for

tracking.

9. Close following ventilation valves:

HVC-23 HVC-30

HVC-24 HVC-31

HVC-26 HVC-34

HVC-27 HVC-35

7.10 CONDITIONAL STATEMENTS AND LOGIC TERMS

Use a consistent format for presenting conditional directions,

ensuring that the action statements follows the conditional

statement •

Procedures require that some decisions be made based on symptoms

and indications. These contingency or conditional decisions

must be written into the procedure to clearly identify to the

user the conditions that must be satisfied prior to taking the

required user action. This information can be presented most

clearly when the opening statements containing the conditional

symptoms use the logic terms IF, IF NOT, and WHEN.

The conditional statements should appear first, before the

action statements. If an action instruction precedes the ~

description of the conditions, there is an increased probability

that the user will perform the action without noting the

qualifying conditions.

FOR REFERENCE ONLY

• 7.0

•

I


7.10 CONDITIONAL STATEMENTS AND LOGIC TERMS (continued)

ADM-98 Page 28 05-18-83

In some instances, the performance of an action depends upon the

presence of several conditions or combinations of conditions.

Describing them together can result in confusing, complex

sentences. The instructions should be simplified by listing the

conditions and proper use of the logic terms IF, AND, OR, THEN,

NOT, IF NOT, and WHEN.

The dual column format used automaticly equates to the logic, IF

NOT the expected response in the left-hand column, THEN follow

. the contingency prescribed in the right-hand column.

The logic terms are understood but may be used for emphasis, for

example," IF RCS pressure is less than 1600 psig, THEN trip

running RCPs 11 •

Use logic terms as follows:

a. When attention needs to be called to combinations of

conditions, the word AND shall be placed between the

description of each condition. The word AND shall not

be used to join more than three conditions. If more

than four conditions need to be joined, a list format

shall be used.

b. The work OR shall be used when calling attention to

alternative combinations of conditions. The use of the

word OR shall always be in the inclusive sense. To

specify the exclusive II OR" the following may be used:

11 either A ORB, but not both 11

FOR REFERENCE ONLY

• 7.0

•

ADM-98 Page 29 05-18-83


7.10 CONDITIONAL.STATEMENTS AND LOGIC TERMS (continued) :

c. When action steps are contingent upon certain

conditions or combination of conditions, the step

should begin with the words IF, or WHEN followed by a ~

description of the condition or conditions (the

antecedent), a comma, the word THEN, followed by the

action to be taken (the consequent).

WHEN, is used for an expected condition. IF is used

for unexpected but possible condition •.

d. Use of IF NOT, should be limited to those cases where

the user must respond to the second of two possible

conditions. IF should be used to specify the first

condition.

e. THEN shall not be used at the end of an action step to

instruct the user to perform the next step, because

it runs actions together.

f. The use of AND and OR within the same action should be

avoided. When AND and OR are used together, the logic

can be very ambiguous. When they must be used

together, their relationship should be clearly defined.

The following guidance for conditional statements is

provided:

a. Write conditional statements so that the description

of the condition appears first, followed by the action

instruction.

FORREFERENCE ONL V

• 7.0

•

•


7.10 CONDITIONAL STATEMENTS AND LOGIC TERMS (continued)

ADM-98 Page 30 05-18-83

b. If three or more conditions must be described before an

action is directed, list the conditions separately from

the action instruction.

c. Emphasize logic words by using location, full

capitalization, and underlining.

The following are examples the use of logic words and

conditional statements:

Example 1 - Incorrect ordering of information

c) Close Main Feedwater Valves

IF feedwater header is ruptured.

Example 2 - Correct ordering of information

c) IF feedwater header is ruptured,

THEN close Main Fee~water

Valves.

Example 3 - Incorrect listing of conditions in

sentence format; complex and easily misunderstood

b) IF containment pressure OR

containment radiation OR

containment sump levels

indicate high OR increasing

readings, THEN GO TO EPIP-X.XX ...

FOR REFERENCE ONLY··

• 7.0

•

•

ADM-98 Page 31 05-18-83


7.10 CONDITIONAL STATEMENTS AND LOGIC TERMS (continued) _.

7 .11

Example 4 - Listing of conditions in list format;

easily understood and recommended

b) IF any of following conditions

high~or increasing:

Containment pressure,

OR

Containment radiation,

OR

Containment sump level,

1!!fil! GO TO EPIP-X.XX

CAUTION STATEMENTS

Cautions are a procedural means for drawing attention to

situations and actions than can result in injury or

equipment damage. A user should be informed regarding hazards

that can be reasonably anticipated. Cautions should describe

the hazardous conditions and consequences of actions. If,

however, cautions are overused, their effectiveness will be

diminished.

A caution statement must be presented to the user in the order in

which it is needed. If the user needs cautionary information

before performing a specific action, it must be presented before ""

the statement directing the action. Otherwise, there is a high

probability (particularly in a stress situation) that the action

FOR REFERENCE ONLY

• 7.0

ADM-98 Page 32 05-18-83


7.11 ·cAUTION STATEMENTS (continued)

.· will be performed without the cautionary information being taken

into consideration. Dividing a caution between pages can

contribute to errors in reading and the overall impact of the

caution is dimini~hed. All of the instruction to which it

applies.

The following guidance is provided:

a. The caution statement will be identified with the

heading "CAUTION":.If several caution statements

precede instructions, only one caution heading is

required. However, each caution.statement shall appear

as a separate paragraph.

b. The caution statement will be made distinguishable from

steps by framing them with lines of asterisks above and

below the statement.

c. The caution statement text should~ be printed in all

capitals because this is more difficult to read than

normal printed text.

d. The caution statement will be printed across the entire

width of the page.

e. Use concise sentences to describe the hazardous

conditions.

f. Place cautions directly ahead of the steps to which

they apply, unless they apply to the entire procedure.

In this case, list them together ahead o( the

instructions. Use only one caution heading for the

entire list.

FOR REFERENCE ONL \.

• 7.0

•


7.11 CAUTION STATEMENTS (continued)

ADM-98 Page 33 05-18-83

g. Make sure that all of the text of a caution is on one

page and that it is on the same page as the step to

which it applies.

h. Cautionseshall contain no action steps.

i. Cautions shall not be presented within a step.

The following example illustrates proper wording and emphasis of

cautions. It avoids directing user actions; rather, warns of

hazardous conditions or consequences of actions.

Example 1.

Action/Expected Response Response Not Obtained

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

CAUTION: Seal injection flow should be maintained to all

RCPs to reduce seal degration.

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

30. CHECK IF CHARGING/SI PUMP

SHOULD BE STOPPED:

a) IF Charging/SI Pumps are

running

AND

RCS pressure is LESS

THAN 1600 psig, THEN

stop all RCPs

a) IF conditions NOT

satisfied, DO NOT

stop RCPs.

f OR REFERENCE ONLY

• 7.0

•


7.12 NOTES

ADM-98 Page 34 05-18-83

NOTES are a means for providing explanatory information in a

procedure without encumbering the procedural steps. When

descriptive or explanatory information is· provided within a

step, it can make"' the step lengthy and difficult to. read.


a. NOTES shall contain no action steps. They should be

expressed in the passive voice.

b. Present information to the user in the order in which

it is needed. Otherwise, the information can be

overlooked during the performance of the step,. If the

information in the note is intended to aid the

performance of a step, place it ahead of the step. If

if pertains to the results of a step (observing a

change as a result of a step), place it after the step.

c. NOTES should be presented on the same page as the step

to they apply.

d. NOTES shall be identified with the heading "NOTE:". If

several notes precede instructions, only one note heading is

required. However, each note should appear as a separate

paragraph.

e. NOTES shall not be presented within a step. "'

f. NOTES should be indented to start at the same point as

high level action statements.

FOR REFERENCE ONl Y

• I

• 7.0

•


7.12 NOTES (continued)

The following example is provided:

Example 1.

Action/Expected Response .,.

ADM-98 Page 35 05-18-83

Response Not Obtained

NOTE: Wind direction is the compass point, such as

ENE, the wind is blowing from.

5. RECORD METEOROLOGICAL

DATA:

7 .13 EMPHASIS

a) Record wind speed from

Recorder SR-MM-lOlA in

Item 3 of Attachment 1

b) Record wind direction

from Recorder ZR-MM-

101A in Item 3 of

Attachment 1

a) IF NOT operable, use

Recorder SR-MM-lOlC.

b) IF NOT operable, use

Recorder ZR-MM-lOlC.

The procedure can be enhanced if certain types of words,

phrases, or nomenclature are always emphasized by use of

capitals, underlining, or other methods. Additional emphasis

may be used as specific requirements dictate.

The method of emphasis used should be used consistently and

sparingly. The key is to us.e the least emphasis possible.

Table 3 gives the methods of emphasis which should be used.

FOR REFERENCE ONLY

• 7.0

•


7.13 EMPHASIS (continued)

The following examples of emphasis are given:

Example 1 - Method of emphasis of high level action

statement, equipment name, logic word, and expected

response.

33. VERIFY CHARGING FLOW:

a) One OR more Charging/SI

pumps - RUNNING

AND

Charging flow -

INDICATED

Example 2 - Method of emphasis of high level action

statement, logic word, and step number.

40. RELOCATION:

a) IF in TSC, GO TO

Step .il_

·ADM-98 Page 36 05-18-83

Example 3 - Method of emphasis of caution statement.

* * * * * * * * * * * * * * * * * * * * * * * * * * *

CAUTION: Opening valve will result in high

radiation levels.

* * * * * * * * * * * * * * * * * * * * * * * * * * *

7.14 CHECK-OFF PROVISIONS

A means can be provided as necessary for the user to check-off

equipment status, valve positions, and other items to aid in

keeping track of the status of the procedure. Check-off

provisions for procedure steps are not mandatory •

FOR REFERENCE ONLY

•

•

ADM-98 Page 37 05-18-83


7.14 CHECK-OFF PROVISIONS (continued)

.· Spaces for entering checkmarks, notations, or data can aid the

user in keeping track of his place in the procedure.

Spaces can be marked for check-off provisions as shown in the

following examples:

Example 1.

1. COLLECT NOTIFICATION DATA:

a) Obtain Attachment.!.~

Attachment 2 of this

procedure

b) Complete following items

on Attachment l• obtaining

data from Station Emergency

Manager

Example 2.

Item 1

Item 2

Item Sa

Item Sb

Item Sc

Item Sd

Item Se

3. Verify ventilation valve

positions

OPEN

HVC-27

HVC-28

CLOSED

HVC-31

HVC-18

I

FOR REFERENCE ONLY

I,;.

• 7.0

•

• - ·-:,·· . ·~-· -·


7.15 SYSTEM RESPONSE

ADM-98 Page 38 05-18-83

For applicable procedures, the content should be consistent with

plant system response to the actions prescribed by the

procedure. Expected system response may be described by the ~

procedure when considered beneficial to the user's understanding

and application of the instructions. The following guidance is

given:

a. Expected results of routine tasks need not be

prescribed.

b. Standard practices for observing for abnormal results

need not be prescribed within procedural steps. For

example, observation of noise, vibration, erratic flow,

or discharge pressure need not be specified by steps

that start pumps.

c •. When actions are required based upon receipt of an

annunciated alarm, the setpoint of the alarm should

listed for ease of verification.

d. When requiring resetting or restoration of a function,

listing the expected results immediately following the task

statement can be beneficial.

e. When considered beneficial to the user for proper

understanding.and performance, describe the response time

associated with performance of the instruction.

f. When system response dictates a time frame within which

the instruction must be accomplished, prescribe such

time frame •

FOR REFERENCE ONl Y


7.15 SYSTEM RESPONSE (continued)

ADM-98 Page 39 05-18-83

g. When anticipated system response may adversely affect

instrument indications, a note can be used to describe

the conditions that may introduce instrument error.

h. When additional confirmation of system response is

considered necessary, identify the backup readings to

be made.

7.16 IDENTIFICATION OF·EQUIPMENT, CONTROLS, AND DISPLAYS

Use nomenclature that will assist the operator in accurately and

quickly identifying equipment, controls, and displays. Several

methods of establishing nomenclature exist. The most common

are: 1) verbatim name plate; 2) word matching the name plate;

and 3) "common usage". Each method has advantages and

disadvantages and implies a degree of user option. Using

verbatim name plate identification nomenclature, including mark

numbers, gives the user no option but to use the equipment

identified. It is the most restrictive method and, because of

the abbreviations and potential long numbers that are common

with equipment, could be confusing.

The method of word matching the name plate eliminates the

potential confusion that could be generated by use of the

verbatim method. However, this method causes potential long

identification names which might generate confusion in

restricted space formats. This method allows user choice

between like equipment of a number designator is not used. The

FOR REFERENCE ON~ v

• 7.0

ADM..-98 Page 40 05-18-83


7.16 IDENTIFICATION OF EQUIPMENT, CONTROLS, AND DISPLAYS (continued) .·

"common usage" method potentially gives the most identifiable

description to the user, but is highly plant-specific. As with

the word matching method, "common usage" nomenclature can be

used to allow user options between like equ_ipment.

The following guidance for identification of equipment,

controls, and displays is given:

a. For major pieces of equipment which are well known to

the user, use the common usage name of the equipment.

b. Where a specific piece of equipment, control, or

display must be operated or read, use the equipment

name followed by the mark number.

c. Use abbreviations only when certain that the user is

familiar with the abbreviation.

The following examples of identification of equipment, controls,

and displays are given:

Example 1 - Use of common usage name giving the user an

option.

c) Start a Charging/SI Pump

Example 2 - Identification of a specific display using a

nameplate engraving.

a) Read wind speed from

recorder

MAIN TOWER UPPER

WIND SPEED (SR-MM-lOlA).

FOR REFERENCE ONLY

i


ADM-98 Page 41 05-18-83

7.16 IDENTIFICATION OF EQUIPMENT, CONTROLS, AND DISPLAYS (continued)

Example 3 - Use of an abbreviation.

b) Determine level in SG "An

7.17 PLANT INSTRUMENTATION VALUES

At all times instrumentation values will be presented using the

same units of measurement as those displayed on the users

instrument. To avoid error and increase efficiency,

instrumentation values should be easily readable by the user.


a. Specify the same units that appear on user

instrumentation.

b. Use limits and setpoints for control which are

compatible with technical guidelines, and user training

and experience.

c. Use setpoints for alarms and trips as presented in PLS

or other references.

d. Use tolerance band if need exists for clarity.

e. Use values readable by user from plant information.

f. Avoid values which require interpolation by the user.

Generally, users can easily interpret values mid-way

between scale markings.

g. Use of clarifying phrases to define intention are

desirable, for example "Rapidly (up to 200°F/hr)

Cooldown the RCS".

FOR REFERENCE ONl ~

7.0

•

•


7.17 PLANT INSTRUMENTATION VALUES(continued)

ADM-98 Page 42 05-18-83

The tolerance requirements for parameter values and trends often

vary with conditions in effect. Although words such as

"slow/fast", "high/low", and "normal" are subjective in nature,

they communicate a desired function because of experience and

training. Operators when given a controlling setpoint tend to

think a band around the point. By not specifying exact values

we can allow some flexibility of control during adverse

transient conditions.

Setpoints for alarms and trips have their tolerance "built-in"

by electronic means. When called for, these values will be

given as they are presented in PLS or other reference documents •

Often conditions require that single ended limits be placed in

parameters, for example, "SG level greater that 17%." In this

case concern is that water level is above 17%; how far above is

not overly significant. Personnel, through training and common

sense, understand other bounds exist to limit large deviations

from these points. If a specific bound exists it will be given.

For this type of condition, only the bounding value will be

given.

If requirements for strict control of a parameter exist., then a

setpoint and a tolerance should be provided. This will normally

be expressed as a setpoint with a band or purely a band.

Requiring personnel to calculate a band or convert units will be

avoided •

• 7.0

•

•

------- ---


7.17 PLANT INSTRUMENTATION VALUES(continued)

The following are example of good tolerance practice:

Example 1

ADM-98 Page 43 05-18-83

Maintain water level at 27 ft. (26ft, 9in to !:]_ft, 1.in)

Example 2

Maintain water level from 26ft, 9in to J]_ft, 3in

7.18 CALCULATIONS

Calculations should be minimized as much as possible; however,·

if they are needed, provide sufficient space for the user to

perform the needed calculations and record the results.

This provision is intended to increase the accuracy of

performing calculations and, by leaving a record of data entries

and computations, to facilitate verification of the res~lts.

For accuracy, units consistent with instrumentation should be

used.


a. If the calculation is short and only needs to be

performed once, provide space within the step requiring

the calculation.

b. If calculations are performed repeatedly or require

plotting, provide space and/or graphs on an attachment

to the procedure.

FOR REFERE CE ONLY

•

•


7.18 CALCULATIONS(continued)

ADM-98 Page 44 05-18-83

c. Mathematical calculations should be avoided in

emergency operating procedures. If values must be

determined to perform steps, a chart or graph should be

used where possible.

d. Calculations should be minimized as.much as possible.

However, some calculations are absolutely necessary,

especially in EPIPs •

. e. Provide conversion factors, formulas, or other

guidance, as required, so that the user can obtain the

answer in the correct units.

Example

Record Feed Pump Suction Pressure: P = __psig

Record Feed Pump Suction Temp: T = °F

Look Up Vapor Pressure at T: VP = __psig

NPSH = (P: ) - (VP: ) --------------- = ft of head

(9216)

7.19 LOCATION INFORMATION

Provide location information in the procedure, if required, to

aid users in finding equipment, controls, or displays.

Emergency usage procedures can involve relatively unfamiliar

tasks. Valves, monitors, instruments, or other items referred

to in the procedure might be time-consuming to find because they

are located in infrequently accessed area or their use is

limited to other than normal conditions •

• ,t .· .....

------·--- ·--····

• 7.0

•


7.19 LOCATION INFORMATION (continued)

The following guidance on location information is given:

ADM-98 Page 45 05-18-83

a. The procedure writer must consider user experience, the

tasks, and the equipment involved to determine whether

location ""information would aid the user in the performance

of the procedure. If it is judged that loss of .time can be

avoided by provision of location information, it should

be used.

b. Procedures can be evaluated for adequacy of location

information during a user walk-through of the/procedure.

c. When the location information is used. present it last

to prevent interference with the action instructions.

The following example of location information is given:

Example 1.

a) Obtain telephone headsets located in simulator room

closet

7.20 STEP SEQUENCE

By nature, a written procedure presents steps in a sequence. It

is expected that this sequence will be adhered to. To allow

flexibility, it should be understood that some deviation may be

acceptable. In many cases, because of equipment and personnel

location and/or availability, actions may be performed

concurrently or in alternate sequences to achieve the same

desired result. This variation is acceptable unless technical

necessity dictates strict adherence to sequence.

-··· ···-- ---·- .. - ---~~-.· -· --~-.

• 7.0

•


7.20 STEP SEQUENCE (continued)

ADM-98 Page 46 05-18-83

It is not expected that step actions be totally completed prior

to beginning the following sequence step. If total completion

of a step is mandatory before continuing a sequence, it will be

so prescribed.

Steps which demand absolute attention to sequence will be

identified. There are relatively few such steps, which are

commonly high level in nature •. All high level steps will have

identifying numbers for reference.

For non-fixed sequence substeps, asterisks may be used to

denote that sequential actions are not required.

7.21 REFERENCING AND BRANCHING

Within the body of the steps of the procedure, minimize·

references to other steps and to other procedures. Also,

minimize branching to the procedures.

When the term "referencing" is used in connection with another

procedure, it implies that the referenced procedure will be used

a supplement to the procedure presently being used.

a. Referencing other pages or steps within a procedure can

result in user error. Excessive forward and backward

referencing can be confusing and lead to the user

skipping steps, particularly since the referenced steps

may not return the user to the directing step.

Important notes or cautions preceding a referenced step

can be missed and so must be referred to whom required

during referencing •

FOR REFERENCE ONLY

•

ADM-98 Page 47 05-18-83


7.21 REFERENCING AND BRANCHING (continued)

b. Referencing to other procedures to be used concurrently

should also be minimized, but is acceptable when required.

If users are required to use several procedures at the same

time, th;re is a risk that the referenced information may

not be obtained and used. Another risk is that the user

might forget the exit point from the original procedure, and

it is not always clear when or where the user is to return

to the original procedure. Critical steps might be missed

as a result.

When the term "branching" is used in connection with another

procedure, it signifies that the procedure being used is to be

terminated and the new procedure is to be used in its entirety.

a. Branching is an acceptable method of entering another

procedure. The problems associated with referencing are

basically eliminated.

b. Procedures entered as a result of branching

considerations should always make it clear when to

branch back to the original procedure or to some other

procedure.

The following guidance on referencing and branching is given.

In determing whether to reference another part of the procedure

for instructions, or to repeat the instructions within the

procedure, consider the following factors:

FOR REFERENCE ONL 'f

• 7.0

•

•


7.21 REFERENCING AND BRANCHING (continued)

ADM-98 Page 48 05-18-83

a. If the referenced instructions can be repeated without

greatly increasing the length of the procedure, repeat

them.

b. If the procedure splits into two or more optional paths

references to other steps may be unavoidable.

c. Be sure there is a means of returning the user to the

correct step in the procedure after using the

reference.

d. Referencing steps before or ahead of the present step

creates a problem if the user has to return to the next

step •

In determining whether to reference another procedure or to

provide the instructions within the procedure being written,

consider the following factors:

a. The compatibility of the procedure being used and the

procedure being referenced.

b. The total number of procedures should be considered and

minimized as much as possible.

c. If the information in question is material that is part

of the expected knowledge of the adequately trained

user, a reference is not necessary.

d. If a sequence of actions is covered completely by an

existing procedure, and if the existing procedure is

used in full, consider using a reference •

f OR REFERENCE ONl Y - -- -· .,....- ····-·· -~ ·----.. ·-·-·--·., .... ,-· --- .....

7.0

•


7.21 REFERENCING AND BRANCHING(continued)

ADM-98 Page 49 05-18-83

e. If the information to be referenced can be included

in a procedure without greatly increasing its length, a

reference should not be used.

f. When referencing to another procedure, reference

specific sections or pages; if possible, to reduce

search time.

g. Consider use of a procedure attachment instead of

referencing if statements are too long to be included

in the text or difficulty in identifying referenced

steps within other procedures arises.

The following examples are given:

Example 1 - Unacceptable reference to a step within the

procedure.

c) Reposition all valves operated in Step .2_

Example 2 - Presentation of actual data instead of

referencing.

c) Return Sample System valves

to original line-up:

OPEN

l-SS-185

l-SS-186

l-SS-187

CLOSED

l-SS-184

FOR REFERENCE ONL V

• 7.0

•

ADM-98 Page 50 05-18-83


7.21 REFERENCING AND BRANCHING (continued) -·

Example 3 - Acceptable referencing and branching.

b) IF NOT lit, position valves

to proper positions as listed

in Attachment 2

c)

AND

GO TO to Step f.

IF flow NOT verified after - --· valve alignment, THEN GO TO

EPIP-7.01

7.22 PRINTED USER AIDS

Printed user aids supporting procedures must be compatible with

the procedure.

Printed user aids can take the form of figures, charts, tables,

and graphs. They can increase the accuracy and speed of

determining causes, identifying procedures and actions,

coordinating emergency responses, and performing calculations.

They must be consistent with the values required by the

procedure and instrument values obtainable by the user.

Misinterpretation of graphs, charts, tables, and figures has

resulted from inadequate original construction or inadequate

reproduction. When copies of procedures or attachments are many

generations removed from the original or master copy, lines,in

graphs, charts, tables, and figures deteriorate or disappear,

making it difficult for a user to extract or interpolate values

accurately. Letters and numbers undergo similar deterioration •

ONLY

• 7.0

•

ADM-98 Page 51 05-18-83


7.22 PRINTED USER AIDS (continued) _.

Materials reduced in size can further impair readability.

The following guidance for printed user aids is given:

a. The aid should be of sufficient size to be legible and

readable under expected conditions of use.

b. Values used should correspond to values the user will

obtain from calculations or plant instrumentation.

c. The essential message of the user aid should be clear

and self-explanatory. Descriptive titles should be

used.

d. Grid lines on graphs should be clearly distinguishable.

e. Numbered grid lines should be bolder than unnumbered

grid lines.

f. Labeling of items within a figure should be accompanied

by arrows pointing to the item.

g. The figure or graph should be oriented naturally. For

example, height on a graph should be along the vertical

axis.

h. All graphs in a family of graphs should be drawn and

oriented similarly.

i. Where possible, the user aid should be oriented such

that the page does not have to be rotated when being

used.

j. The aid should be presented such that needed values can

be extracted or interpreted to required accuracy •

FOR REFEllEHCE ONLY ··- .. -··-·-· ···-·- . ···-- ...... --

••

•

•

.8.0 MECHANICS OF STYLE

8. 1 . SPELLING

ADM-98 Page 52 05-18-83

Spelling should be consistent with modern usage. When a choice

of spelling is offered by a dictionary, the first spelling

should be used.

8.2 HYPHENATION

Hyphens are used between elements of a compound word when usage

calls for it. The following rules should be followed for

hyphenation:

a. When doubt exists, the compound word should be

restructured so as not to require hyphenation.

b. Hyphens should be used in the following circumstances:

1.

2.

In compound numerals from twenty-one to

ninety-nine.

Example: one hundred thirty-four

In fractions.

Example: one-half, two-thirds

3. In compounds with self.

Example: self-contained, self-lubricated

4. Where the first member of the compound ends in the

same vowel that the second member begins with. As

an alternative, two words may be used.

Example: fire-escape or fire escape.

5. Where misleading or awkward consonants would result

by joining the words.

Example: bell-like

FOR REFERE~lCE ONLY ···-- ·---·----:-- ··-.··· - - - ... . ··-··--·· ..... -·· ..

• 8.0

•

••

ADM-98 Page 53 05-18-83

MECHANICS OF STYLE (continued)

8.2 HYPHENATION (continued)

8.3

6. To avoid confusion with another word.

Example: re-cover to prevent confusion with

recover

pre-position to avoid confusion with

preposition

7. Where a letter is linked with a noun.

Example: X-ray, 0-ring, U-bolt, I-beam

8. To separate chemical elements and their atomic

weight

Example: Uranium-235, U-235

PUNCTUATION

Punctuation should be used only ~s necessary to aid reading and

prevent misunderstanding. Word order should be selected to

require a minimum of punctuation. When extensive punctuation is

necessary for clarity, the sentence should be rewritten and

possible made into several sentences. Punctuation will be in

accordance with the following rules.

8.3.1

. 8.3.2

Apostrophe

Use an apostrophe to indicate possessive forms of

nouns. For example, The Company's audit plan ••• Do

not use an apostrophe to indicate plural of acronyms.

For example: PMs, Form 4s •

Brackets

Do not use brackets as punctuation •

f OR REFERENCE ONLY

• 8.0

•

•

ADM-98 Page 54 05-18-83


8.3 PUNCTUATION (continued)

8.3.3

8.3.4

8.3.5

8.3.6

Colon

Use a colon to indicate something is to follow. For

example: Restore cooling flow as follows:

Comma

Use of many commas is a sign the instruction is too

complex and needs to be rewritten. Use commas for the

following:

Dash

a. Before "and" or "or" in a series of three or

more.

Example: a, b, and c

b. To separate four or more digits •

Example: 14,500 - 1,600,000

c. After introductory or conditional words,

phrases, or clauses when necessary for clarity

or ease of reading.

Example: When level decreases to 60 inches,

start pump

Do not use dashes except in procedure and components

numbers or prior to an expected response.

Parenthesis

Parenthesis should be used for indicating alternative

or supplementary items in an instructions, or around

equipment mark numbers •

r:nR. 0~E-·f[R' -E~ 1C· E: n· t~;,l'' uJi rt Lli N- • uai <'

• 8.0

•

•

ADM-98 Page 55 05-18-83


8.3 PUNCTUATION (continued)

8.3.7

8.3.8

8.3.9

8.3.10

Period

Use a period at the end of complete sentences and for

indicating the decimal place in numbers. Periods are

normally not used following phrases and clauses in the

left-hand side of a two column format.

Quotation Marks

Avoid using quotation marks.· Where common usage or

figurative language must be used, the first use only

should be set off with quotation marks.

Semicolon

Favor periods and commas over semicolons. Do not use

semicolon where usage calls for colons.

Slant Line

Use a slant line to indicate an "either-or" situation

and as a substitute for "per" in units of measure.

Examples: either/or, ft/sec, lbs/hr.

8.4 VOCABULARY

Words used in procedures should convey precise understanding to

the trained person. The following rules apply:

a. Use simple words. Simple words are usually short words

of few syllables. Simple words are generally common

words.

b. Use common usage if it makes the procedure easier to

understand •

• 8.0

•

•


8.4 VOCABULARY (continued)

ADM-98 Page 56 05-18-83

c. Use words which are concrete rather than vague,

specific rather than general, familiar to the user

rather than formal, precise rather than blanket.

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

one sense.

e. Avoid using verbs that are unfamiliar, vague, or that

can be misinterpreted.

f. Eliminate superfluous words.

g. When repeating a long technical term or word shortly

after its first use, use "it, "this item", "this

method", etc., instead of the difficult or long terms •

h. The use of shall, will, should, and may.are as follows:

1. Shall. Mandatory requirement.

2. Will. Mandatory requirement.

3. Should. Non-mandatory preferred or desired method.

4. May. Acceptable or suggested method.

i. · Verbs with specific meaning should be used. Examples

are listed in Table 1.

j. See Table 4 for a listing of unique vocabulary.

k. Equipment status will be denoted as follows:

f OR REFERENCE OHl Y

8.0

•

•

ADM-98 Page 57 05-18-83



1. Operable/operability. These words mean that a

system, sub-system, train, component, or device is

capable of performing its specified function(s).

Implicit in this definition should be the

assumption that all necessary attendant

instrumentation, controls, normal and-emergency

electrical power sources, cooling or seal water,

lubrication or other auxiliary equipment that are

required for the system, sub-system, train,

component, or devi~e to perform its function(s) are

also capable of performing its function(s) •

Emergency conditions may dictate use of equipment

which is not operable by strict definition.

2. Operating. This word means that a system,

sub-system, train, component, or device is in

operation and is performing its specified

function(s).

3. Available. This word means that a system,

sub-system, train, component, or device is operable

and can be used as desired; however, it need not be

operating •

• __ _._,.__ _, __ _ ·--

FOR REFERENCE Of~l Y

•

8.0 MECHANICS OF STYLE (continued)


·ADM-98 Page 58 05-18-83

1. Avoid all-inclusive words unless the absolute meaning

is real. All-inclusive words include: never, all,

always, every, and.none.

m. State acceptance criteria in specific terms. Where

acceptance criteria are based on subjective evaluation,

state the criteria in descriptive phrases which cover

specific meaning. User familiarity with criteria thru

training and experience can make words such as satisfactory,

normal and adequate valid.

8.5 NUMERICAL VALUES

The use of numerical values should be consistent with the

follo~ing rules:

a. Arabic numerals should be used.

b. For numbers less than unity, the decimal point will be

preceded by a zero.

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

number of significant digits available from the

display.

d. Acceptance values should be specified such that mental

calculation by the user is avoided. This can· generally

be done by stating acceptance values as limits.

Examples: 510°F maximum, 300 psig minimum, 580° to

600°F. For calibration points, statement of setpoint

and its lower and upper limits would accomplish the

same purpose. Example: 10 milliamperes (9.5 to 10.5).

• 8.0

•


8.6 UNITS OF MEASURE

ADM-98 Page 59 05-18-83

Qnits of measure are defined by the United States National

Bureau of Standards (NBS). Units of measure will be consistent

with NBS definitions.

In procedural text, figures, tables, and attachments,

engineering units of measurements should be given for numerical

values which represent measurement data or calculation results.

They should be the same as those used on displays.

8.7 ABBREVIATIONS, LETTER SYMBOLS, AND ACRONYMS

The use of non-standard abbreviations should be minimized

because they may be confusing to those who are not thoroughly

familiar with them. Abbreviations may be used, where necessary,

to save time and space and where their meaning is unquestionably

clear to the intended reader. If not commonly familiar to the

user, their full meaning should be written in before the first

use of an abbreviation and whenever in doubt. Consistency

should be maintained throughout the procedure. See table 2.

Capilization of abbreviations should be uniform. If the

abbreviation is comprised of lower-case letters, it should

appear in lower case in a title or heading. The period should

be omitted in abbreviations, except in cases where the omission

would result in confusion.

Letter symbols may be used to represent operations, quan~ities,

elements, relations, and qualities. A symbol is preferred to an

abbreviation.

FOR. REFERENCE ONLY

•

•

ADM-98 Page 60 05-18-83


8.~ ABBREVIATIONS, LETTER SYMBOLS, AND ACRONYMS (continued)

8.8

Acronyms are a type of symbol that are formed by the initial

letter or letters of each of the successive parts or major parts

of a compound term. Acronyms may be used if they are defined or ""

commonly used. See Table 2.

Abbreviations, symbols, and acronyms should not be overused.

Their use should be for the benefit of the reader. They can be

beneficial by:

a. Saving reading time

b. Ensuring clarity when space is limited

c. CoDDDunicating mathematical ideas

CAPITALIZATION

It should be recognized that no one set of rules for

capitalization can be universally applicable or all

encompassing. The following guidelines will be applied in

principle to areas not strictly defined.

8.8.1 Organizations, Institutions, Companies, and

Associations

Full titles of organizations, institutions,

companies, and associations and their departments

are capitalized, but such words as "school" or

"company" are lower-cased when used alone.

Examples: Surry Power Station, North Anna

Simulator, Virginia Electric and Power Company,

Nuclear Regulatory Commission, the company, the

coDDDission, the station.

FOR REFERENCE ONLY

8.0

•

•

ADM-98 Page 61 05-18-83


8.8.2

8.8.3

Title of Written Material

The first letter of nouns, pronouns, adjectives,

verbs, adverbs, and subordinate conjunctions are

capitalized. Articles, Coordinate conjunctions,

and prepositions, regardless of length, unless they

are the first or last words of the title or

subtitle, are lower case. Titles will be

underlined.

Examples: Code of Federal Regulations

Surry Operating Procedure l-OP-1.4

Surry Technical Specifications

Titles of an Organizational Structure

Staff positions and titles, when they refer to an

individual with specific authority, duties, and

responsibilities, are capitalized. General

categories or groups of people identified within

the organization structure are not capitalized.

Examples: Station Manager

Superintendent Maintenance

Operations Coordinator

Shift Supervisor

Control Room Operator

electrician

mechanic

operator

FOR REFERENCE O I

I I I I

•

•

ADM-98 Page 63 05-18-83


8.8 CAPITALIZATION (continued)

8.8.6

8.8.7

Engravings and Legends (continued)

Examples: Verify CHARGING FLOW CONTROL VALVE

(FCV-()122) in the AUTO mode

RC PUMP IA TRIP alarm is received •••

Open valve MOV-()381 by placing its

control switch to OPEN, then releasing

the switch to spring return to

NORM.

When the pump READY light comes on •••

System, Component, and Device Ide~tifiers

CAPITALIZATION should be used for all letters of

component mark numbers including device designations,

and system acronyms. When unit designator is not used,

then() will be used.

Examples: l-SS-185

TV-SS-206B

FCV-() 122

Noted exceptions to this guideline are:

Examples: dP - designator for differential

pressure

pH - chemical symbol for hydronium ion

concentrate

•

•

•

ADM-98 Page 64 05-18-83


8.8 CAPITALIZATION (continued)

8.8.8

8.8.9

Modes of Operation

Modes of operations should be capitalized as they apply

to a specific configuration of the plant or of a

system.

Examples: Mode 3

Cold Shutdown

Power Operations

Tables and Figures

CAPITALIZATION should be used for reference to tables

and figures, titles of tables and figures within text

materials, and column headings within a table •

Example 1. Refer to Figure 201 for •••

Example 2. • •• as shown in Table 201,

Example 3. Equipment Power Supplies, the •••

·.-~=·· .-. -· ...... -· , ..

• 9.0

•

•

MISCELLANEOUS ITEMS

9.1 STATUS TREES

ADM-98 Page 65 05~18-83

Critical Safety Function (CSF) Status Trees may be presented in

either block or branch versions (See Figure 4), but all trees in

a set must use the same format.

The block version~is more convenient to evaluate since a single

judgement is required to determine the relationship between

plant status and prerequisite parameter value. This form

approximates the logic which would be programmed for computer

evaluation.

The branch version is preferable for display of final tree

status after evaluation.

The following CSF Status Tree guidance is presented:

a. Color-coding or line pattern coding, if branch used,

shall be used from branch points to termini (See Figure

4).

b. Trees may be oriented vertically or horizontally on a

page, but orientation must be consistant within a set.

c. Each CSF Status Tree shall have a designator block

consisting of: tree number, tree title, revision

number and revision date

d. CST Status Trees shall have legibility criteria

consistant with procedure instructional steps.

FOR REFERENCE o· LY

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

•

•

•

.. 1~ ._ . / ....

BLOCK TYPE.

MCS SUIIICOOLING 18ASED ON COIIE EXIT TC.,

GMEAfEA JHAN !.!]°F

RCS SU8COOLING IBASED DN CORE EXIT TC.I

COIIE EXIT TC.

GREATEII THAN 1200°F

A

C

ADM 98 Page 66

MAY 1 8 t983

LESS JHAN UJ°F · B AT LEAST ONE fief' . E

'IIUNNING

COflE EXn TC.

LEGntAN.uoo9F D . :-.'.

ALLIIIOI --F ST~D

B

alRE EXIT Tts L£SS THM

--.. 1zoc-,

C I

11D .

D

· .. .l·· •.

····:·J'

: .· . . ~ •, . . :-'~

. . . .· ,. ·: . :. ~ . . ·?·:_:~._.: .:::

.. ···-· .

~. -. ·-

··1-.

-

Figure q

-...

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

·. ~ .. : _: .· : : .. . . . -:. ~· (_ ..

. .. ~- :.-. -. . ~-

RCS SUBCOOl.lNG ------~GREATER ~ - ...... -.. ;-:-·-·

·, .. (1) ·~

A E

FOR REFERENCE ONLY -·. . :-·-. ··. -- ---,·-.

• 9.0

•

•

MISCELLANEOUS ITEMS (continued)

9.2 FOLDOUT PAGE

ADM-98 Page 67 05-18-83

A single fold out page will be provided with all EP and ECA

series procedures as required to convey information. The fold

out page will summarize information which requires continual

operator referal. Such an item may be SI reinitiation and

termination criteria.

The fold out page will not have a bordered-page format. It is

intended to summarize only information which an operator should

have for continuous reference, so page content will vary by

procedure. Each fold out page will be titled at the top "FOLD

OUT FOR E-X SERIES PROCEDURES". The sheet will be numbered as

the final page of the procedure to which it applies. The

procedure will still be captioned with END after the last

instructional step.

Each set of operator .information will be numbered sequentially

and have an explanitory title. Sequence does not always imply

priority. The set title will be capitalized and underlined for

emphasis.

9.3 TRANSITIONS

Contain conditions will require use of a different procedure or

step sequence. These transitions are made in the following

manner:

a. Procedure transitions are made by using the words "GO

TO" followed by the procedure designator, title and

step number.

Example: GO TO EP-1.0 Reactor Trip/SI, Step l•

FOR REfERE!

9.0

•

ADM-98 Page 9& 05-18-83

MISCELLANEOUS ITEMS (continued)

.. b. A forward step transition is made by using the words

"GO TO" and the step number.

Example: GO TO Step 22.

c. A transition, to an earlier step is made by using the

words "return to" and the step number.

Example: Return to Step ~-

9.4 IMMEDIATE ACTIONS

9.5

There is no differentiation made within the procedures between

immediate and subsequent actions. For training purposes,

immediate action step are identified by enclosing the step

number in brackets.

REPRODUCTION

Reproduction should be done on a standard copier with no

enlargement or reduction. Copies are to be single sided only.

Use of colored paper should be guided IAW ADM 51.

FOR REFERENCE ONLY

• VERB .

Adjust

Align

Allow

Block

Check

• Close

Complete

Control

Decrease

Determine

•

ADM-98 05-18-83

TABLE 1 ACTION VERBS

MEANING/APPLICATION

To physically set a regulating device to a specific value, for example, "adjust EDG speed control to obtain 900 rpm."

To arrange a group of components into a desired configuration, for example, "align the system for normal charging flow"

To permit a stated condition to be achieved prior to proceeding, for example, "allow pressure to stabilize"

To inhibit an action, for example, "block SI actuation"

To note a condition and compare to a requirement, for example, "check prz level - GREATER THAN 20%"

To change the physical position of· a mechanical device to prevent physical access or flow, OR to permit passage of electrical current. Closing a valve prevents fluid flow. Closing a breaker allows electrical current flow.

To accomplish specified requirements, for example, "complete valve checkoff list"

To perform manual operation of equipment to satisfy predetermined requirements, for example, "control Prz level at NOL"

Cause to become less, reduce. Should be avoided in action statements because of problems with verbal communication. Can be used· effectively in verification steps

To acquire definite knowledge of, for example, "determine wind speed"

FOR REFERENCE ONLY 1-1

•

•

Verb

Establish

Increase

Initiate

Inspect

Isolate

Lower

Maintain

Monitor

Obtain

Open

Raise

ADM-98 05-18-83


(continued)

MEANING/APPLICATION

To make arrangements for a stated condition, for example, "establish communications with control room"

To cause to become greater. Should be avoided in action statements because of problems with verbal communication. Can be used effectively in verification steps.

To begin a process; bring into use, for example., "initiate SI"

To measure., observe or evaluate a feature for comparison with specified limits, for example, "visually inspect for lea}cts"

To set apart by physical barrier., for example, "isolate letdown"

To decrease or reduce, for example., "Lower prz level"

To continuously control a given parameter to some requirement, for example, "maintain SG level in the narrow range"

Similar to "check" but implies a repeated function, for example, "monitor CST level"

To gain physical possession of, or acquire by some action, for example, "obtain Attachment!"

To change the physical position of a mechanical device to the unobtructed position. Opening a valve permits full fluid flow. Opening an electrical breaker prevents current flow

To cause to rise or increase, for example, "raise prz level"


·1 ·,

•

•

•

Verb

Record

Start

Stop

Terminate

Throttle

Trip

Vent

Verify

ADM-98 05-18-83


(continued)

MEANING/APPLICATION

To document specific conditions or characteristics, for example, "record RCS pressure"

To originate motion of an electrical or mechanical device either directly or by remote control, for example, "start one RCP"

To terminate motion of an electrical or mechanical device, for example, "stop EDGs"

To end a process or stop a function, for example, "terminate SI"

To place a valve in an intermediate position to obtain a desired flow rate, for example, "throttle Charging/SI pump discharge MOVs"

To manually activate a semi automatic function. Normally "trip" refers to equipment deactivation, for example, "trip the turbine"

To perform a controlled release of pressurized gas or liquid, for example, "vent the Reactor Vessel head"

To observe that an expected characteristic or condition exists, for example, "verify Rx tripped"

FOR REFERENCE ONL y 1-3

• ac

ACC

ADM

AE

A/E

AFW

Amp

ANSI

AOD

AP

APP

• Assist

ATWT

Auto

Aux

Avg

BAST

BATP

BD

BIT

Bkr

Bldg

B & W

BYP

TABLE 2 ABBREVIATION AND ACRONYM LIST

ADM-98 05-18-83

alternating curr~nt (electrical)

Accumulator

Administrative Procedure

Air Ejector

Architect/Engineer

Auxiliary Feedwater

ampere (electrical)

American National Standards Institute

Air Operated Damper

Abnormal Procedure

appendix

assistant

Anticipated Transient Without Trip

automatic

auxiliary

average

Boric Acid Storage Tank

Boric Acid Transfer Pump

Blowdown System

Boron Injection Tank

breaker (electrical)

building

Babcock and Wilcox

bypass


•

•

•

CAT

cc

ccw

Ckt

cm

CN

Cont

COVRERP

cpm or CPM

cps or CPS

CR

CRDM

CRO

cs

CSD

CSF

CST

eves

ADM-98 05-18-83


(continued)

Chemical Addition Tank

Cubic Centimeter

Component Cooling Water System

circuit (electrical)

Centimeter

Condensate System

Containment

Commonwealth of Virginia Radiological Emergency Response Plan

Counts per minute

Counts per second

Control Room

Control Rod Drive Mechanism

control Room Operator

Containment Spray System

Cold Shutdown

Critical Safety Function

Condensate Storage Tank

Chemical and Volume Control System

FOR REFERENCE ONl Y

2-2

,I

•

•

DBA

DBE

de

Disch

DOE

d/p

dpm or DPM

d/t

EAL

ECA

ECC

ECCS

EDG

EHC

Emer

ENS

EOF

EP

EPC

EPIP

EPZ


(continued)

Design Basis Accident

Design Basis Earthquake

direct current (electrical)

Discharge

Department of Energy

differential pressure

disintegrations per minute

differential temperature

Emergency Action Level

ADM-98 05-18-83

Emergency Contingency Action

Emergency Control Center

Emergency Core Cooling System

Emergency Diesel Generator

Electro-hydraulic Control System

emergency

NRC Emergency Notification System

Emergency Operations Facility

Emergency Procedure

Emergency Planning Coordinator

Emergency Plan Implementing Procedure

Emergency Planning Zone

ESFs Emergency Safeguards Features

,. ·'l .~

,J

•

•

FP

FRP

FSAR

FW

Gen

gpm or GPM

GW

GT

H2

HCV

Hdr

HHSI

Htr

HX

HP

HP Tech

HPN

HSB

HSD


(continued)

ADM-98 05-18-83

Fire Protection System

Function Restoration Procedure

Final Safety Analysis Report

Feedwater System

Generator

gallons per minute

Gaseous Waste System

Gas Turbine

Hydrogen

Hand Control Valve

Header

High Head Safety Injection

Heater

Heat Exchanger

Health Physics or high pressure

Health Physics Technician

Health Physics Network ( communications)

Hot Standby

Hot Shutdown

Heating, Ventilation and Air Conditioning

• :

IA

IAW

I & C

ICC

Inst

Intlk

IR

IRAP

IRPI

Isol

ISRS

IX

LCO

LHSI

LOCA

LP

LS

LVDT


(continued)

Instrument Air System

ADM-98 05-18-83

In accordance with

Instrumentation and Control

Inadequate Core Cooling

instrument (ation)

interlock

Intermediate Range (NIS)

Interagency Radiological Assistance Plan

Individual Rod Position Indication

isolation

Inside Recirculation Spray System

Ion Exchanger

Limiting Condition of Operation

Low Head Safety Injection

Loss of Coolant Accident

low pressure

limit switch

linear Variable Differential Transformer

level

Liquid Waste System

I

0

MCR

MCV

MD

MFP

MFW

MG

MOD

MOV

Mph

MR/hr

MS

MSL

MSR

MSTV

N2

Neg

NIS

NOL

Norm

NPSH

NR

NRC

NRV

NSSS

ADM-98 05-18-83


(continued)

2-6

Main Control Room

Medical College of Virginia

Motor Driven (reference to pumps)

Main Feedwater Pump

Main Feedwater System

Motor Generator

Motor Operated Damper

Motor Operated Valve

Miles per hour

milli REM per hour

Main Steam System

Mean Sea Level

Moisture Separator/Reheater

Main Steam Trip Valve

Nitrogen

Negative

Nuclear Instrumentation System

Normal Operating Level

normal

Net Positive Suction Head

narrow range (indication)

Nuclear Regulatory Commission

Nonreturn Valve

Nuclear Steam Supply System

•

•

OEES

QBE

02

OI

oos

OP

Ops

Opx

osc

OSRS

ADM-98 05-18-83


(continued)

2-7

Office of Emergency and Energy Services (State of Virginia)

Operational Basis Earthquake

Oxygen

Operating Instruction

out of service

Operating Procedure

Operations (dept;.)

Off-premises exchange (communications)

Operational Support Center

Outside Recirculation Spray System

•

••

PAGs

PAM

PBX

PDT

PDTT

Pf

PGW

PORV

Pos

PR

Press

PRT

PRZ

Psi

PTS

Pwr

QC

TABLE 2 ABBREVIATION AND ACR

(continued) NYM LIST

Protective Action Guides

Post Accident Monitoring

Private Branch ex~han (communicat· ) ge · ions

Prima D ry rain Tank

ADM-98 05-18-83

Primary D rain Transfer Tank

Power factor

Primary G rade Water System

Power Operated Reii~f Valve

positive

Power Range (NIS)

pressure

Pressurizer Relief Tank

Pressurizer

pounds per square inch

Pressurized Thermal Shock

power

Quality Control

fOR RtfEREN&£ O~ll ~

2-8

•

•

.·

RCCA

RCP

RCS

Recirc

Ref

Reg-Guide

REM

RHR

R/hr

RMP

RMS

RO

RPI

RPV

RS

RSS

RTD

RV

RVLIS

RWST

RX

ADM-98 05-18-83


, (continued)

Rod Control Cluster Assembly

Reactor Coolant Pump

Reactor Coolant System

recirculate (ation)

reference

Regulatory Guide

Roentgen Equivalent Man

Residual Heat Removal

REM per hour

Remote Monitoring Panel

Radiation Monitoring System

Reactor Operator

Rod Position Indication

Reactor Pressure Vessel

Recirculation Spray

Reserve Station Service

Resistance Temperature Detector

Relief Valve

Reactor Vessel Liquid Inventory System

Refueling Water Storage Tank

Reactor

FOR REFERE CE OHL Y 2-9

"

SA

SAT

SCBA

S/D

SEM

SEP

SFP

SG

SGTR

SI

SNSOC

SPDS

SPS

SR

SRO

ss

STA

Stm

Str

SUR

Supt

- Supv

sv

•


(continued)

Service Air System

satisfactory

ADM-98 05-18-83

Self Contained Breathing Apparatus

shutdown

Station Emergency Manager

Surry Emergency Plan

Spent Fuel Pit

Steam Generator

Steam Generator Tube Rupture

Safety Injection

Station Nuclear Safety and Operating Conunittee

Safety Parameter Display System

Surry Power Station

Source Range (NIS)

2-10

Senior Reactor Operator

Shift Supervisor or Sampling System

Shift Technical Advisor

steam

strainer

Startup Rate

Superintendent

Supervisor

()

,.

SW

s & w

Sys

Tavg

Tc

T/C

TD

TG

Th

THY

TK

TLD

Tref

TRNEE

TS or Tech

TSC

Turb

TV

UC

UFSAR

UHF

UNSAT

Spec

ADM-98 05-18-83


(continued)

,;:; ~ Ii'! Ii;]

Service Water System

Stone and Webster

System

Average Temperature

RCS Cold Leg Temperature

Thermocouple

Turbine Driven (reference to pumps)

Turbine Generator

RCS Hot Leg Temperature

Thyroid_

Tank

Thermoluminescent Dosimeter

Reference Temperature

Trainee

Technical Specification

Technical Support Center

Turbine

Trip Valve

Micro Curie

Updated Final Safety Analysis Report

fs ~._

Ultra High Frequency (communications)

Unsatisfactory

2-11

()

•

-·

V

VAC

VCT

Vent

VEPCO

w

WGDT

WR

WT

Wtr


(continued)

Volts (electrical)

Volts ac

Volume Control Tank

Ventilation

ADM-98 05-18-83

Virginia Electric and Power Company

Westinghouse

Waste Gas Decay Tank·

Wide Range (indication)

Water Treatment System

Water

2-12

: I

/

•

(_)

•

ITEM

High Level Action Statements:

Major Equipment Names: e

Expected Response:

Setpoints, Values, Step Numbers, and Attachment Numbers:

Logic Words:

Train or Component Identifiers:

Document Name:

Legends, Engravings, Annunciation Windows, Labels, and Signs:

NOTES:

Cautions:

TABLE 3 METHODS OF EMPHASIS

METHOD OF EMPHASIS

All capitals. Example: OBTAIN DATA:

Initial capitals. Example: Charging/SI Pump

All capitals.

ADM-98 05-18-83

Examples: DECREASING, CLOSED.

Underlined. Examples: 500 psig, Step 4.b, Attachment!•

All capitals, and underlined. Examples: IF, IF NOT, GO TO, and OR. - ---

Capital and quotation marks Examples: Train "A", Reactor Coolant Pump "lB".

Initial capitals and·underlined. Example: EPIP-1.01, Emergency Manager Controlling Procedure.

All capitals. Example: AUTO

Note headers in all capitals and underlined, with body of note extending width of page

Caution headers in all capitals and underlined. Body of caution extending full width of page and framed in asterisks.

FOR 3-1

• .. WORD

Faulted

Intact

Local (locally)

Manual (manually)

Ruptured

TABLE 4

ADM-98 05-18-83

UNIQUE VOCABULARY LIST

FOR

4-1

MEANING/APPLICATION

When used in context with steam generators, "faulted" implies loss of secondary integrity.

When used in context with steam generator, "intact" implies that SG is neither "faulted" or "ruptured".

An operator action which is performed outside the control room.

An operator action which is performed within the control room. (Used in contrast to an automatic action).

When used in context with steam generators, "ruptured" implies a primary to secondary tube leak. The leak size is defined as greater than or equal to one (1) sheared tube.

Date post:	02-Jun-2020
Category:	Documents
Upload:	others
View:	0 times
Download:	0 times

Administrative Procedure ADM 98, 'Emergency Usage Procedures … · 2019-12-27 · ADM-98 Page 1...

Documents