ML20195C320

Rev 0 to Administrative Procedure 4.06, Emergency Operating Procedure Development & Implementation

ML20195C320
Person / Time
Site:	Palisades
Issue date:	05/23/1986
From:	CONSUMERS ENERGY CO. (FORMERLY CONSUMERS POWER CO.)
To:
Shared Package
ML18052A450	List: ML20195C299 ML20195C320
References
4.06, NUDOCS 8605300224
Download: ML20195C320 (65)

Text

1 ATTACHMENT 3 Consumers Power Company Palisades Plant Docket 50-255 1

PALISADES PLANT ADMINISTRATIVE PROCEDURE 4.06 EMERGENCY OPERATING PROCEDURE DEVELOPMENT AND IMPLEMENTATION May 23, 1986 pg53 4 860523 P

K 05 5

37 Pages OC0586-0020S-NL01

?r:: N:..%

Revision 0 r

PALISADES NUCLEAR PLANT Date 5/2/86 ADMINISTRATIVE PROCEDURE Revision and Approvat Summary TITLE: EMERCENCY OPERATINC PROCEDURE DEVELOPMENT AND IMPLEMENTATION 1.

Prepared 2.

QA Concurrence 0

'/lZ4kb Respomrible' IndKvidual Date Y

de

_ktA

' Da'e t

3.

Recomune Agproval/Q-List No 4

PRC Reviewed 09 h A

~ a.L s~-/ -V6, Responsible DepaVtm#nt Head Date J/3 y Date 5.

Approved 6.

ATMS Incorporated

% /.c

< / / L.

&2 -M.

n.3 Final Approver

~Date Date 7.

Biennial Review Date Date l

Date Date Date I

l i

ado 386-0008n-93 i

1

PALISADES MUCLEAR PLANT Proc No 4.06 ADMINISTRATIVE PROCEDURE Rsvision 0 Page i TITLE EMERGENCY OPERATING PROCEDURE DEVELOPEMENT AND IMPLEMENTATION Table of Contents fagg 1.0 PURPOSE 1

2.0 SCOPE L

3.0 REFERENCES

1 4.0 RESPONSIBILITIES.

2 4.1 OPERATIONS SUPERINTENDENT

.................... 2 4.2 EMERGENCY OPERATING PROCEDURE PERSONNEL 2

5.0 DEFINITIONS 2

6.0 PROCEDURE 2

6.1

SUMMARY

DESCRIPTION OF E0P PROGRAM................ 2 6.1.1 E0P Personnel 2

6.1.2 Interfacina Procedures.

3 6.2 PLANT SPECIFIC TECHNICAL CUIDELINES 3

6.2.1 Ceneral 3

6.2.2 Source Documents...

3 l

6.3 FUNCTION AND TASK ANALYSIS....................

3 6.4 E0P WRITER GUIDELINES 4

6.4.1 Numberina. Headinas and Format 4

j 6.4.2 Writ== Instructional Steps 5

i 1

6.4.3

": '- *cs of Style.......................

11

(

6.4.4 Ceneral Appearance.......................

15 t

6.5 TECHNICAL NOTEBOOK.......................

17 6.5.1 Basis Document Development 16 6.5.2 Basis Documents Format

. 17 ado 386-0008m-93-89 l

PALXSADES NUCLEAR PLANT Proc No 4.06 ADMINISTRATIVE PROCEDURE Revision 0 Page ii TITLE EMERCENCY OPERATINC PROCEDURE DEVELOPEMENT AND IMPLEMENTATION Table of Contents i

6.5.3 Basis Document Content 17 6.5.4 Review and Approval 17 6.5.5 Document Control and Distribution 17 6.5.6 Revision Requirements

. 17 6.6 E0P VERIFICATION........................

18 6.6.1 Ceneral 18 6.6.2 Documentation 19 6.7 E0P VALIDATION.........................

19 6.7.1 General 19 6.7.2 Validation Methodolony

. 19 6.7.3 Validation Responsibilities

.........20 6.7.4 Validation Tess

......................20 6.7.5 Validation Process.

21 6.8 EOP TRAININC..

......................22 6.8.1 Program Description 22 6.8.2 Progras Obiectives.......................

22 6.8.3 EOF Trainina Process.

22 6.8.4 TEGEM N 05 E0P REVISIONS (AFTER INITIAL E0P IMPLEMENTATION).

23 6.9 USE AND NAINTENANCE OF E0P' S..................

23 6.9.1 Ceneral Availability

.........23 6.9.2 Number of Copies..

........24 6.9.3 Accessibility

.........................24 6.9.4 Document Control of E0Ps 24 ado 386-0008a-93-89

PALISACES NUCLEAR PLANT Proc No 4.06 ADMINISTRATIVE PROCEDURE Revision 0 Page iii TITLE:

EMERCENCY OPERATING PROCEDURE DEVELOPEMENT AND IMPLEMENTATION Table of Contents fage 6.9.5 Controlled Copies of EOPs

.................... 24 6.9.6 Periodic Review........................

24 6.9.7 EOP Revision...................

. 25 6.10 WAIVERS 25 7.0 ATTACHMENTS AND RECORDS

. 25 7.1 ATTACHMENTS..........................

25 7.2 RECORDS

..........................26 ATTACHMENTS Attachment 1, " Component Identification" Attachment 2, " Action Verbs" Attachment 3, " Abbreviations, Letter Symbols, and Acronyms" Attachment 4, " Cover Sheet for Basis Document" Attachment 5, " Quality Assurance Review Checklist" Attachment 6, " Technical Review Checklist" Attachment 7, "EOP Validation Evaluation Criteria" Attachment 8, "EOP Validation Form" Attachment 9, " Checklist for Table-Top / Walk-Through Methods of Validation" 0, " Checklist for Simulator Method of Validation" 1, " Function and Task Analysis" t

l l

l ado 386-0008m-93-89

PALICADES NUCLEAR PLANT Proc No 4.06 ADMINISTkATIVE PROCEDURE Revision 0 Page 1 of 26 TITLE: EMERCENCY OPERATIkG PROCEDURE DEVELOPMENT AND IMPLEMEhTATION 1.0 PURPOSE To describe the general requirements and methods for development, verification, validation and implementation of Palisades Plant Emergency Operating Procedures.

2.0 SCOPE This procedure applies to the initial upgrade of Palisades Plant Emergency Operating Procedures as required in NUREC 0737, Supplement 1 and to any subsequent updates or revisions to the Emergency Operating Procedures.

3.0 REFERENCES

3.1 Palisades Administrative Procedure 10.41, " Procedure on Procedures" 3.2 Palisades Technical Specifications 3.3 NUREC 0737, Supplement 1 3.4 Emergency Operating Procedure Verification Guidelines, INPO 83-004 3.5 Emergency Operating Procedure Validation Cuideline, INPO 83-006 3.6 Emergency Operating Procedure Implementation Guideline, INPO 82-016 3.7 Emergency Operating Procedure Writing Guideline, INPO 82-017 3.8 Combustion Engineering Emergency Procedures Guidelines, CEN-152 3.9 NODS-A04, " Preparation and Control of Procedures" 3.10 Palisades Administrative Procedure 10.42, " Procedure / Document Matrix" 3.11 NUREC 0899, Guidelines for the Preparation of Emergency Operating Procedures" l

3.12 Polisades Administrative Procedure 10.43, " Document Distribution and l

Control" l

3.13 Nuclear Assurance Department Procedure V-2, " Quality Assurance Reviews" 3.14 Palisades Administrative Procedure 4.05, " Operator Training" l

l ado 386-0008a-93-89 l

44 PALYSADES NUCLEAR PLANT Proc No 4.06 ADMINISTRATIVE PROCEDURE Revisicn 0 Page 2 of 26 TITLE! EMERGENCY OPERATINC PROCEDURE DEVELOPMENT AND IMPLEMEhTATION 4.0 RESf M IBILITIES 4.1 OPERATIONS SUPERINTENDENT The Operations Superintendent has overall responsibility for the Emergency Operating Procedure (EOP) Upgrade project and subsequent revisions to the Emergency Operating Procedures.

Primary responsibilities in addition to those specified in Reference 3.1 includes Assign personnel to perform EOP writing, verification and a.

validation.

b.

Approve document revision requests to EOPs during and subsequent to the EOP Upgrade project, and ensure timely implementation.

f Ensure training is conducted prior to implementation of EOPs c.

generated durics the EOP Upgrade project and also for subsequent major revisions.

d.

Approve any waivers to the EOP development and implementation process for EOP revisions subsequent to the EOP Upgrade project.

4.2 EMERCENCY OPERATINC PROCEDURE PERSONNEL Personnel involved with Emergency Operating Procedure development and implementation shall comply with the requirements of this procedure.

5.0 CEFINITIONS Estrgency Operating Procedures (EOPs) - EDPs are procedures that dirtet operator actions necessary to mitigste consequences of transients and accidents which cause plant parameters to exceed reaccor protection setpoints, engineered safety feature setpoints, or othee appropriate technical limits.

6.0 PA M 6.1 SIM W DESCRIPTION OF EOP PROGRAM 6.1.1 EOF Personnel EOPs will be developed and implemented by personnel assigned by the Operations Superintendent. Members will be selected based on their previous related esperience (eg, contract personnel) or level of qualification (eg, licensed SRO or RO; human factor espect, etc).

ado 386-0008a-93-89

PALISADES KUCLEAR PLANT Proc No 4.06 ADMINISTRATIVE PROCEDURE Revision 0 Page 3 of 26 TITLE: EMERGENCY OPERATINC PROCEDURE DEVELOPMENT AND IMPLEMENTATION 6.1.2 Interfacina Procedures Changes to other plant procedures which are necessary to ensure continuity of the EOPs with the supporting plant and system procedures shall be recommended and peccessed as part of this program.

6.2 PLANT SPECIFIC TECHNICAL CUIDELINES 6.2.1 Ceneral Because of the similarity between Palisades and the generic plant used in the Combustion Engineering (CE) Emergency Procedure guidelines (Referecce 3.8), Palisades will use Revision 2 of Reference 3.8 to upgrade existing plant emergency procedures. The source documents indicated belcw constitute the plant specific technical guidelines required by Reference 3.3.

Future approved revisions to Reference 3.8 will be incorporated into the E0Ps using the established revision, review and approval process and this procedure for development and implementation.

6.2.2 Source Documents EOP writers will use the following source documents to prepare upgraded EOPs.

a.

Administrative Proctdures (References 3.1, 3.10,'3.12, 3.14 and this procedure) b.

CE Emergency Procedure Guidslines (Reference 3.8) c.

Function and Task Analysis Report (see Section 6.3) l d.

Technical Specifications (Reference 3.2) e.

Existing Emergency Procedures f.

FSAR 3

Licensing Comeitment Letters Related to EOPs h.

As Built Plant Drawings 6.3 FUNCTION AND TASK ANALYSIS Function and task analysis for the initial upgrade shall be completed per Attachment 11. This analysis provides an additional source document for the EOP writers which specifies the plant specific tasks required to accomplish the designated safety functions. Revisions to the function and task analysis report which are required due to the ado 386-0008a-93-89 L

PALXSADES NUCLEAR PLANT Proc No 4.06 ADMINISTRATIVE PROCEDURE Revision 0 Page 4 of 26 TITLE EMERCENCY OPERATING PROCEDURE DEVELOPMENT AND IMPLEMENTATION EOF verification and validation process should be processed in a timely manner but need not be completed prior to E0P implementation.

6.4 EOP WRITER CUIDELINES 6.4.1 Numberina. Headings and Format a.

Title Block Information Title block information shall be in accordance with Reference 3.1.

b.

Numbering Alpha-Numeric designation shall be in accordance with References 3.1 and 3.10.

c.

Section and Subsection Headings Headings shall be in accordance with Reference 3.1.

d.

Format 1.

Page Format Format of the EOP shall, in general be a single column format for the procedure body. A dual column format is allowed for E0P 1 (Standard Post Trip Actions) procedural body and for Safety Status Checklists to E0Ps.

EXAMPLES:

Example 1 - Single-Column Format 5.4 IF the pressurizer level cannot be maintained above 20%,

THEN 30 to Step 5.10.

5.5 IF containment pressure is greater than 4.4 psig, THEN ensure Containment Isolation per Attachment 1.

ado 386-0008a-93-89

a-PALISADES NUCLEAR PLANT Proc No 4.06 ADMINISTRATIVE PROCEDURE Revision 0 Page 5 of 26 TITLE EMERCENCY OPERATINC PROCEDURE DEVELOPMENT AND IMPLEMENTATION 3

Example 2 - Dual-Column Format Instructions Contingency Actions 5.4 Check Pressuriser levelt 5.4 IF Pressure level a.

Above 20%

cannot be maintained above 20%, THEN to to Step 5.10.

5.5 Monitor containment 5.5 If containment pressure pressure exceeds 4.4 psig, a.

Containment pressure THEN, ensure containment isolation per Attachment 1.

2.

Procedure Organisation The following section headings shall be used for all E0Ps 1 TITLE / PURPOSE The title and purpose secticn shall be written in a manner such that the scope of the procedure is defined.

2 ENTRY CONDITIONS Contain those plant symotoms/ events (including automatic system actions) which are espected to aid in identifying the emergency conditions.

3 OPERATOR ACTIONS Contain concise instructions and contingency actions for operatort l.- Immediate Action (Required for Standard Post Trip Actions only) 2.

Subsequent Action (Labeled as "Operatcr Actions" in all E0Ps) 6.4.2 Writtaa Instructional Steps a.

Instruction Step Length and Centent Instruction steps shall be short and or.act. General rules to be l

used in meeting these objectives are'as followst 1.

Instruction steps should deai with only one ides.

2.

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

ado 386-0008a-93-89

~'

PALISADES NUCLEAR PLANT Proc No 4 06 IDMINISTRATIVE PROCEDURE' Revision 0 Page 6 of 26 IITLE: EMERGENCY OPERATING PROCEDURE DEVELOPMENT ARD IMPLEMENTATION 3.

Cceplex evolutions should be prescribed in a series of steps.

4.

Objects of operator actions should be specifically stated when appropriate.

5.

Instructional steps that involve an action verb shall be listed with space provided for operator checkoff in the left hand margin, except for those steps which require continuous or repeated operator actions, which shall be denoted with an asterisk (*) next to the step number.

6.

Mandatory sequence of steps is assumed unless otherwise stated.

7.

Instruction content should be written to communicate to the minimum expected operator experience and knowledge level and are structured to be executed by the minimum shift staffing required by Technical Specifications.

8.

Action steps and corresponding Notes / Cautions / Warnings shall start and end on the same page.

9.

Expected results of routine tasks need not be stated.

10.

Minimize use of articles (the, a, an) unless they are needed for clarity.

11.

When actions are required based upon receipt of an annunciated alarm, list the setpoint of the alars.

12.

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

13.

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

14.

When system response dictates a time frame within which the instruction must be accomplished, prescribe such time frame.

If possible, however, avoid using time to initiate operator actions. Operator actions should be related to Plant parameters.

15.

When anticipated system response may adversely affect instrument indications, describe the conditions that will likely introduce instrument error and means of determining if instrument error has occurred by using a NOTE.

ado 386-0008a-93-89

PALRSADES NUCLEAR PLANT Proc No 4.06 ADMINISTRATIVE PROCEDURE Revisioti 0 Page.7 of 26 TITLE: EMERCENCY OPERATINC PROCEDURE DEVELOPMENT AND IMPLEMENTATION 16.

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

17.

Steps should be written to-be consistent with the roles and responsibilities of the operators involved with the task.

18.

Actions steps should be structured to minimize the mover $ent of personnel around the Control Room while completing procedural steps.

19.

Actions steps should be structured to avoid unintentional duplication of tasks.

20.

Steps used to verify whether the objective of a task or a sequence of actions has been achieved should meet one of the following guidelines a)

Checking that an action has resulted in a command signal to a piece of equipment. The operator should not rely on this type of check, if possible, but should use a more positive indication.

b)

Checking that an action has resulted in a positive indication that the equipment has responded to a command.

i c)

Checking that an operator has correctly performed an

[

action or has carried out a series of steps.

21.

Nonsequential steps should be written into procedures using an approach that ' Curly identifies to the operator where and when these 5tep a; ply, the conditions under which they apply, and4r ne ' me sequence required for their performanc% 74 s steps shall be notated with an asterisk

(*) nest to the stsp number.

22.

For equally acceptable steps (eg, any one of several alternative steps or sequence of steps may be equally correct) 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 sequence) cannot be:done (eg, a designated piece of equipment is unavailable) in order of preference.

23.

Concurrent steps are those which have to be performed at the same time. The EOPs should explicitly indicate which steps l

are concurrent so that operators can easily refer to both (or all) sets of steps. The maximum nanber of concurrent l

ado 386-0008a-93-89

PALISADES NUCLEAR PLANT Proc No 4.06 ADMINISTRATYVE PROCEDURE Revision 0 Page 8 of 26 TITLE: EMERGENCY OPERATING PROCEDURE DEVELOPMENT AND IMPLEMENTATION l

steps should not be beyond the capability of the Control Room staff to perform them.

24.

Diagnostic steps should assist the operator in diagnosis, and provide clear and unambiguous guidance leading to the diagnostic decision, as well as referencing to the appropriate section of the E0P.

These steps may include the use of flow-diagrams, graphs or other operator aids.

b.

Use Of Logic Terms The logic terms AND, OR, NOT, I{, IF NOT, WHEN, and THEN are oftan necessary to describe precisely a set of conditions or sequence of actions. When logic statements are used, logic terms shall be capitalized and underlined. The use of AND and OR within the same actica shall be avoided. When AND and OR are used together, the logic can be very ambiguous. No other logic terms, except those described above, shall be used.

Use logic terms as follows:

1.

When attention should be called to combinations of condi-tions, the word AND shall be placed between the description of each condition. The word AND shall not be used to join more than three conditions. If four or more conditions need to be joined, a list format shall be used.

2.

The word OR shall be used when calling attention to alter-native combinations of conditions. The use of the word OR shall always be in the inclusive sense. To specify the exclusive "OR", the following may be used:

"either A OR B, but not both".

3.

When action steps are contingent upon certain conditions or combinations of conditions, the step shall begin with the words 1[ 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 an unexpected but possible condition.

4.

Use of IE NOT should be limited to those cases in which the operator must respond to the second of two possible condi-tions. IE should be used to specify the first cendition.

5.

THEN shall not be used at the end of an action step to instruct the operator to perform the next step, because it runs actions together.

ado 386-0008a-93-89

j e'

_ PALISADES MUCLEAR_ FLAN _T Proc No 4.06

' ADMINISTRATIVE PROCEDURE Eavision 0 Page 9 of 26 l

TITLE EMERGENCY OPERATING PROCEDCRE DEVELOPMENT AND IMPLEMENTATION l

c, Use Of Cautionary Information And Metes j

Cautionary information can be considered in two fundamental categories: those that apply to the entire procedure and those that apply to a portion or a specific step of the procedure.

Those that apply to the entire procedure are called " PRECAUTIONS" and are covered in operator training.

Those that apply to a portion of a procedure are called " CAUTIONS" and are placed immediately before the procedural steps to which they apply.

A caution shall not be used instead of an Instructional s:ep.

If additional information other than cautions is necessary to support an action instruction, a WOTE shbuld be used. A NOTE should present information only, not instructions, and saould be located as close to the applicable instruction as possible.

d.

Calculations Mathematical calculations should be avoided in ECPs. If a value has to be determined in order to perform a procedural step, a chart or graph should be used whenever possible.

e.

Use of Underlining Underlining shall be used for emphasis of logic terms, CAUTIONS, WARNINGS AND NOTES.

I f.

Capitalization Certain words should be capitalized for increased emphasis. See Sections 6.4.2 (b, h, i 4 j), 6.4.3.e and 6.4.4.c.

g.

Referencing And Branching To Other Procedures Or Steps Referencing impliss that an additional procedure or additional stspo shall be used as a supplement to the procedure presently being used. Referencing other steps within the procedure being seed, either future steps or completed steps, should be minimized.

When only a few steps are involved in the referencing, the steps should be stated in the procedure sharever they are needed.

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

I l

ado 386-0008a-93-89

~.

PALISADES NUCLEAR PLANT Proc No 4.06 ADMINISTRATIVE PROCEDURE Revision 0 Page 10 of 26 TITLE!

EMERCENCY OPERATINC PROCEDURE DEVELOPMENT AND IMPLEMENTATION Use quotation marks to emphasize the title of the referenced or branched procedurel examples: Co to Step 10 of E0P 1, " Reactor Tri p.

h.

Component Identification j

l Component identification shall be in accordance with Reference 3.1 i

and che following requirementst 1.

Equipment, controls, and displays shall be identified in operator language (cosuson usage) teres as listed on

).

2.

When the engraved names and numbers on panel placards and

. stars windows are specifically the ites of concern in the procedure, the engraving should be quoted verbatim and emphasized by using all capitals.

3.

The names of Plant system titles shall be emphasized by initist capitalization, 4.

If the component is seldom used or it is felt that the component would be difficult to find, location information should be given in parenthesis following the identification.

i. Level Of Detail Too much detail in E0Ps should be avoided in the interest of being able to effectively maecute the instruction in a timely fnanner.

The level of detail required should be the detail that a newly trained and licensed operator would desire during an emergency condition.

To assist in determining the level of detail, the following general rules apply.

1.

For contrct circuitry that executes an entire function upon

-actuation of the control switch, the action verb appropriate to the component suffices without further amplification of how to manipulate the control devices for example, "Open 58UTDOWW C00LINC RETURN (**MO-3016)",

Recommended action verbs are as follows:

a)

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

b)

For valves, use Open, Close, Throttle Open, Throttle close, Throttle.

c)

For power distribution breakers, use Synchronize and Close, Trip.

ado 386-0008a-93-89

~_

PALISADES _ NUCLEAR PLANT Proc No 4.06 ADMINISTRATIVE PROCEDURE Revision 0 Page 11 of 26 TITLEt ENERCENCY OPERATING PROCEDURE DtVELOPMENT AND IMPLEMENTATION 2.

For control switches with a positional placement that establishes a standay readinast condition, the verb " Set" should be used, along with the engraved name of the desired position. Positional placements are typically associated with establishing readiness of automatic functions and are typically named AUTO or NORMALI for example, " Set PRESSURIZER SPRAY (**CV-1057) in AUTO".

3.

Standard practices for observing abnormal results need not be presce'ibed within procedural steps. For example, observation of noise, vibration, erratic flow, or discharge pressure need not be specified by steps that start pumps.

j. Printed Operator Aids When information is presented using graphs, charts, tables and figures, these aids must be self-explanatory, legible, and readable under the expected conditions of use and within the reading precision of the operator. In addition they must 1.

Be easily located when referenced to in the text.

2.

Se easily identified from the text information.

3.

Contain only the relevant information needed to accomplish the purpose referred to in the text.

a)

Units of Measure Units of measure used in plotted values should be compatible with divisions shown on the graph. That is, if plotted values progress in units of five (5, 10, 15) it is better to separate the values by five lines than by four lines.

b)

Titles and Headinas l

Initial capitalization should be used for references to tables and figures, titles of tables and figures within text material, and column headings within a table.

6.4.3 Mechanics of Style a.

Hyphenation Hyphens are used between elements of a compound word when usage I

calls for it.

The following rules should be followed for hyphenation.

ado 386-0008a-93-89

PALXSADES NUCLEAR PLANT Proc No 4.06 ADMINISTRATIVE PROCEDURE Revision 0 Page 12 of 26 TITLE: EMERGENCY OPERATINC PROCEDURE DEVELOPMENT AND IMPLEMENTATION 1.

When doubt exists, the compound word should be restructured to avoid hyphenation.

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; examples: one-half, two-thirds.

c)

In compounds with "self"; examples: self-contained, self-lubricated.

d)

When the last letter of the first word is the same vowel as the first letter of the second word - as an alternative, two words may be used; example:

fire-escape or fire escape.

e)

When misleading or awkward consonants would result by joining the words; example:

bell-like.

f)

To avoid confusion with another word; examples:

re-cover to prevent confusion with recover, pre position to avoid confusion with preposition.

g)

When a letter is linked with a noun; examples:

X-ray, 0-ring, U-bolt, I-beam h)

To separate chemical elements and their atomic weight; examples: Uranium-235, U-235.

b.

Punctuation Punctuation should be used only as necessary to aid reading and prevent misunderstanding. Word order should be selected to require a minimum of punctuation. When extensive punctuation is necessary for clarity, the sentence should be rewritten and possibly made into several sentences.

Punctuation should be in assordance with the following rules.

1.

grackets Do not use brackets.

2.

Colon Use a colon to indicate that a list of items is to follow, for example:

Restore cooling flow as follows:

ado 386-0008a-93-89

PALISADES NUCLEAR PLANT Proc No 4.06 ADMINISTRATIVE PROCEDURE Revision 0 Page 13 of 26 TITLE: EMERCENCY OPERATING PROCEDURE DEVELOPMENT AND IMPLEMENTATION 3.

Comme Use of many commas is a sign.the instruction is too complex and needs to be rewritten. Therefore, evaluate the number of commas to ensure the instruction is not too complex.

Use a comma after conditional phrases for clarity and ease of reading. Example: WHEN level decreases to 60 inches, THEN start pump...

4.

Parentheses Parentheses shall be used to indicate alternative items in a procedure, instruction, or equipment numbers.

5.

Period Use a period at the end of complete sentences and for indicating the decimal place in numbers.

6.

Slant Line Use a slant line to indicate an "either-or" situation and as a substitute for "per" in units of measurel examples:

ft/sec, lbs/hr, gal / min.

c.

Vocabulary Words used in procedures should convey precise understanding to the trained person. The following rules apply:

1.

Use simple words. Simple words are usually short words of few syllables. Simple words are generally common words.

2.

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

3.

Use words that are concrete rather than vague, specific rather than general, familiar rather than formal, precise 3(pi c rather than blanket.

l 4.

Define key words that may be understood in more than one l

sense.

l 5.

Action verbs with specific meaning should be used. Examples are listed in Attachment 2.

ado 386-000Sa-93-89 l

I

PALISADES NUCLEAR PLANT Proc No 4.06 ADMINISTRATIVE PROCEDURE Revision 0 Page 14 of 26 TITLE:

EMERGENCY OPERATING PROCEDURE DEVELOPMENT AND IMPLEMENTATION 6.

Equipment status should be denoted as follows:

a)

Operable / Operability - These words mean that a system, subsystem, train, component, or device is capable of l

fulfilling its design function (s).

b)

Operating - This word means that a system, subsystem, train, component, or device is in operation and is performing its designed function (s).

c)

Available - This word means that a system, subsystem, train, component, or device can be used as desired; however, it need not be operating nor fully operable.

d.

Numerical Values t

The use of numerical values should be consistent with the following rules:

1.

Arabic numberals should be used.

2.

For numbers less than unity, the decimal point should be proceeded by a zerol for example 0.1.

3.

The number of significant digits should be consistent with the reading precision of the operator.

4.

Acceptance values should be specified by stating acceptance values as limits. Example 580* to 600*F.

For calibration points, statement of the midpoint and its lower and upper limits for each data cell would accomplish the same purpose:

for example, 10 milliamperes (9.5 to 10.5).

Avoid using 1.

5.

Engineering units should always be those used on the Control Room displays.

Abbreviations, Letter Symbols And Acronyms e.

Mer use of abbreviations should be minimised because they may be semissing to those who are not thoroughly familiar with them.

Abbreviations may be used where necessary to save time and space, and when their meaning is unquestionably clear to the intended reader. The full meaning of the abbreviation should be written in before the first use of the abbreviation or whenever in doubt.

Consistency should be maintained throughout the procedure.

See for cosusonly used abbreviations, letter symbols, and acronyms. Capitalisation of abbreviations should be uniform.

If the abbreviation is comprised of lowercase letters, it should appear in lowercase in a title or heading. The period t'aculd b2 ado 386-0008a-93-89 l

PALISADES NUCLEAR PLANT Proc No 4.06 ADMINISTRATIVE PROCEDURE Rovision 0 Page 15 of 26 TITLE:

EMERCENCY OPERATING PROCEDURE DEVELOPMENT AND IMPLEMENTATION omitted in abbreviations except in those cases where the omission would result in confusion.

Abbreviations, symbols and acronya's should not be overused. Their use should be' for the benefit of the reader. They can be beneficial by saving reading time, ensuring clarity when space is limited, and communicating mathematical ideas.

6.4.4 Ceneral Appearance a.

Breaking of Words Breaking of words should be avoided to facilitate operator reading.

b.

Printed Operator Aids 1.

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

a)

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

b)

The essential message should be cleart simple presentations are preferred.

c)

Crid lines of graphs should be at least 1/8" apart; numbered grid lines should be bolder than unnumbered grid lines.

d)

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

e)

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

2.

Tables should be typed using the following rules:

a)

Type style and size should be the same as that for the rest of the procedure.

b)

A heading should be entered for each column.

c)

There should not be a vacant cell in the table.

If no entry is necessary, "N/A" should be entered to indicate not applicable.

ado 386-0008a-93-89 e

m

~

,d-e

--7.-.--

-.--r

-w-..--._,r.

PALISADES MUCLEAR PLANT Proc No 4.06 ADMINISTRATIVE PROCEDURE Revision 0 Page 16 of 26 TITLE: ENERCENCY OPERATINC PROCEDURE DEVELOPMENT AND IMPLEMENTATION c.

Cautions, Warnings And Notes All notes and cautions shall be distinguishable from the rest of the text by using the format required by Reference 3.1.

In addition all of the text of a CAUTION or WARNING shall appear on the same page, along with the first step of the instruction to which it applies.

d.

Use Of Foldout Pages When used, a foldout page is treated as a single page.

It should follow the same format as a standard page except the width is different. The page should be folded so that a small margin exists between the fold and the right-hand edge of standard pages.

This will reduce wear of the fold.

1 e.

Use Of Oversized Pages Oversise pages should not be used. They should be reorganized or reduced to a standard page.

If this cannot be done, a foldout page may be used. Oversized pages may be used for posted operator sids (eg, PCS pressure-temperature curve).

f.

Use Of Reduced Pages Reduced pages should be avoided whenever possible. Final size of reduced pages should be standard page size. Reduced pages shall be readable.

g.

Typing Format EOPs shall be produced using the current Plant Word Processing Equipment. In general, Word Processing Equipment is designed to enhance readability of the documents it creates, however, the EOP writer shall ensure that the margins and spacing of lines used does not obscure the readability of the information presented.

h.

Reproduction Reproduction of E0Ps for controlled copies will be on a yellow paper from a standard copier, single-sided copy only.

i ado 386-0008a-93-89

=

PALISADES NUCLEAR PLANT Proc No 4.06 ADMINISTRATIVE PROCEDURE Ravision 0 Page 17 of 26 TITLE: EMERGENCY OPERATING PROCEDURE DEVELOPMENT AND IMPLEMENTATION 6.5 TECEBICAL NOTE 800E The EOF writer (s) shall maintain a Technical Notebook (handwritten is acceptable) which documents the justification for each Operator Action in the applicable E0P. The justification in the Technical Notebook any reference appropriate documents including the bases sections of Reference 3.8.

In addition, any deviation from the guidelines in Reference 3.8 is documented and justified in the Technical Notebook.

Applicable portions of the Tschnical Notebook shall accompany the E0P revision, etc for Technical Review. The reviewed and revised documents may then be used by the Training Department to develop training material.

6.5.1 Basis Document Development Basis documents may be developed to incorporate Technical Notebook material and formalise information. Should basis documents be prepared, they shall be developed as described in the following sections.

6.5.2 Basis Documents Format Each EOP basis document will utilize Attachment 4 as a cover sheet to document review and approval. Basis documents shall contain the following sectionst 1.0 Description i

2.0 References 3.0 Evaluation 6.5.3 Basis Document Content Each basis document shall contain an itemized list of each EOP step and its technical justification (eg, Step 4.2 - Trip two, leave two PCP strategy, Reference CEN 268 for basist or, Step 4.10, Maintaining pressuriser level between 40% and 70% based cn..... (Plant Specific Justification).....). Also, Reference 3.8 guidance which is not insiedad in the applicable E0P shall be justified (eg, Step 5 of CEB 132 LOCA guideline not incorporated since RVLMS system is not lasts 11ed at Palisades).

6.5.4 Review and Acoroval The Basis Document shall receive one level of technical review. The Operations Superintendent (or his designate) shall approve the Basis Document which also constitutes approval of appropriate technical reviews. Reviews and approvals shall be documented on the Basis Document Cover Sheet (Attachment 4).

ado 386-0008a-93-89

_ =,_ - - - -._

PALISADES NUCLEAR PLANT Proc No 4.06 ADMINISTRATIVE PROCEDURE Revision 0 Page 18 of 26 TITLE: EMERCENCY OPERATING PROCEDURE DEVELOPMENT AND IMPLEMENTATION 6.5.5 Document Control and Distribution The master copy of the approved Basis Document shall be sent to Document Control for filing with the master copy of the E0P. Document control shall maintain an index (including current revisions and approval date) and issue controlled copies to designated individuals.

6.5.6 Revision Reautrements Each Basis Document shall be reviewed for continued applicability and revised if necessary whenever the associated E0P is revised or periodically reviewed (see Steps 6.9.2 and 6.9.7).

6.6 EOF VERIFICATION 6.6.1 Ceneral a.

E0P verification is the evaluation performed to confirm the written correctness of the procedure and to ensure that applicable generic and plant-specific technical information has been incorporated properly. This evaluation also checks that the human factors aspects presented in the writer's guide for E0Ps have been applied.

b.

Reviews of E0Ps will be accomplished per References 3.1 and 3.10 with the following additional restrictions / guidance:

1.

Quality Assurance Review - This review will be accomplished using Reference 3.13 and Attachment 5 and will ensure that the E0Ps conform to the writer's guideline section of this proceudre.

2.

Technical Review - will be accomplished by a licensed individual (SRO or RO) using Attachment 6 and will ensure:

a)

That the E0Ps are technically correct and reflect the technical guidelines and other EOP source documents.

b)

Correspondance exists between the procedure and the Control Room / Plant Hardware.

c)

The language and level of detail of information presented in the E0Ps is compatable with the qualifications, training, and experience of the operating staff.

3.

Control Room Walkthrough

• will be accomplished by a licensed individual (SRO or RO) and will ensure that information presented in the EOP is compatible with Control ado 386-0008a-93-89

PALXSADES NUCLEAR PLANT Proc No 4.06 ADMINISTRAT1VE PROCEDURE Revision 0 Page 19 of 26 TITLE: EMERCENCY OPERATING PROCEDURE DEVELOPMENT AND IMPLEMENTATION Room Hardware. This is performed during the Technical Review above, but may be performed by a separate individual.

6.6.2 Documentation Completed Attachments 5 and 6 and related Document Review Sheets (Form 3110s) shall be maintained in the procedure working file which is forwarded to Document Control per Reference 3.1.

6.7 E0P VALIDATION 6.7.1 Ceneral EOP validation is the evaluation performed to determine if the Control Room operators can effectively manaSe emergency conditions in the Plant using the EOPs. E0Ps will be evaluated with regard to the following principles a.

Usability - The EOPs provide sufficient information that is understandable to the operator.

b.

Operational Correctness - The E0Ps are compatible with Plant responses, Plant hardware, and the shift manpower.

6.7.2 Validation Methodolony Simulator validation shall be the primary methodology to validate E0Ps. Additional validation methods listed below shall be used if simulator validation cannot be accomplished (eg, simulator modeling problems) or if simulator validation is not appropriate (See Step 6.7.3)

Validation methods are Simulator Validation - Method of validation whereby' Control Room a.

Operators perform actual control functions on the Palisades Simulator during a scenario for an observer / review team.

b.

Table-Too Validation - Method of validation whereby personnel esplain and/or discuss procedure action steps for an observer /

reviewer in response to a scenario or as part of an actual industry operating experience review.

Walk-Throuah Validation - Method of validation whereby Control c.

Room Operators conduct a step-by-step enactment of their actions in the Control Room or the simulator during a scenario for an observer / review team without carrying out the actual control functions.

ado 386-0008a-93-89

PALISADES NUCLEAR PLANT Proc No 4.06 ADMINISTRATIVE PROCEDURE Revision 0 Page 20 of 26 TITLE: EMERCENCY OPERATING PROCEDURE DEVELOPMENT AND IMPLEMENTATION 6.7.3 Validation Responsibilities a.

Operations Superintendent The Operations Superintendent shall be responsible for the following:

1.

Managing the validation program and es.suring its smooth coordination with the training program.

2.

Determining if validation is needed and its scope.

3.

Selecting the validation method or methods.

4.

Appointing and indoctrinating an observer / reviewer team.

5.

Completing applicable portions of the EOP Validation Form (Attachment 8).

6.

Arranging for rotating operating crews through the training / validation sessions.

7.

Arrange for simulator training time for validation purposes as appropriate.

8.

Reviewing discrepancies and approve resolutions forwarded to him by observer / review personnel.

b.

Validation Participants Responsibilities of validation participants are specified'in the checklist for the validation method (Attachments 9 and 10).

6.7.4 Validation Team The Operations Superintendent will designate personnel to participate in EOF validation. Validation team members includes

a. *Euman Factors Specialist - Should be qualified to NUREG 0801 Sostion 2.1.

b.

• Simulator Instructor c.

Other Observers / Evaluators - Minimum of one required.

d.

Operator Participants (ie, minimum Control Room staffing).

1.

Shift Supervisor 2.

Shift Engineer ado 386-0008a-93-89

PALISADES NUCLEAR PLANT Proc No 4.06 ADMINISTRATIVE PROCEDURE Revision 0 Page 21 of 26 TITLE!

EMERGENCY OPERATINC PROCEDURE DEVELOPMENT AND IMPLEMENTATION 3.

Control Room Operator - 2 required 4.

Auxiliary Operator - 1 required (Not required for simulator validation)

Required only during simulator validation (Human Factors Specialist may be used in walk-through validation).

6.7.5 Validation Process Regardless of the validation method, the EOP validation process can be described by the four phases of preparation, assessment, resolution and documentation.

a.

Preparation Each validation method will use the applicable evaluation criteria presented in Attachment 7, and the scenario to be used will be recorded on Attachment 8.

Further specific guidance in preparation for each validation method is presented in the checklist for the validation method (Attachments 9 & 10).

b.

Assessment Specific guidance for assessment using each validation method is presented on the checklist for each validation method (Attachments 9 & 10).

c.

Resolution Resolution will be accomplished by reviewing discrepancies and comments presented on the Discrepancy / Comment section of.

The observer / reviewer will propose solutions, if needed, and forward to the Operations Superintendent for approval, with any other appropriate documentation. The Operations superintendent will determine if additional validation testing is necessary (ie, significant descrepancies which result in meseptance criteria not being met - reference Attachment 7).

d.

Documentation The documented items needed to provide a history of the validation program are specified on each validation method checklist (Attachments 9 and 10). These items will be maintained in the procedure working file which is forwarded to Document Control per Reference 3.1.

ado 386-0008s-93-89 e

.,_..---...-.p,_e_

..-__-.-,.w_

-,,____--_.v..,,__--7

PALISADES NUCLEAR PLANT Proc No 4.'06 ADMINISTRATIVE PROCEDURE Revision 0 Page 22 of 26 TITLEt EMERGENCY OPERATINC PROCEDURE DEVELOPMENT AND IMPLEMENTATION 6.8 EOF TRAINING 6.8.1 Proares Description The training program described herein is comprised of both classroom and simulator training.

6.8.2 Pronras Objectives The training program has four major objectives a.

To enable the operator to understand the structure and format of E0Ps.

b.

To enable the operator to understand the technical basis of the EOPs.

c.

To enable the operator to have a working knowledge of the technical content of the E0Ps.

d.

To give the operator experience in using the E0P under simulated control room conditions.

6.8.3 E0P Trainina Process a.

Classroom Presentation and Discussion Instruction will be given ont 1.

Use of the format of the E0Ps.

2.

Standard post trip actions.

3.

Each event specific E0P.

4.

When and how to use the functional recovery EOP.

b.

80mstator training at the Palisades simulator shall provide the Es& lowings 1.<

" Team" concept used in that each operator is trained in the role that he is expected to take in case of an actual emergency.

2.

A wide variety of scenarios should be used to expose the operators to multiple (simultaneous or sequential) failures while using the E0Ps.

3.

Each licensed operator shall receive simulator training on

~

all E0Ps.

ado 386-0008a-93-89

PALISADES NUCLEAR PLANT Proc No 4.06 ADMINISTRATIVE PROCEDURE Revision 0 Page 23 of 26 TITLE: EMERCENCY OPERATINC PROCEDURE DEVELOPMENT AND IMPLEMENTATION NOTE Simmistor training may occur coincident with E0P validation as described in Section 6.7.

c.

Examinations:

1.

Tests will be administered at the conclusion of the classroom presentation and will meet the requirements of periodic emans specified in Reference 3.14.

2.

Operator performance evaluations on the E0P simulator training will be performed as described / required in Reference 3.14.

6.8.4 TRAINING ON E0P REVISIONS (AFTER INITIAL EOP IMPLEMENTATION)

Training on minor procedure revisions may be conducted through a program of required readings (self-taught), preshift briefings, or lectures in the requalification program and may occur coincidental with implementation.

Training on major revisions shall be conducted by the use of classroom instruction and walk-throughs in the control room or on the Palisades plant-specific simulator. If operational considerations do not allow control room walk-throughs, and the plant-specific simulator is not available, training on major revisions shall be conducted during classroom instruction.

In any event, training on major revisions shall be completed prior to implementation.

6.9 USE AND MAINTENANCE OF EOPS The purpose of this section is to provide guidance on the use and maintenance of E0Ps, including their periodic review and revision.

6.9.1 Ceneral Availability The location of E0Ps within the Control Room is primarily dictated by Control' Room layout. E0Ps should be located so that they are imensistely accessible to operators while they perform their Control i

Regpidaties. Also, E0Ps should be usable without interfering with l

wedhVtsetion activities and without covering up controls and displays.

Finally, all relevant procedures should be available at all locations in the Plant where equipment is to be manually operated under l

emergency conditions.

l ado 386-0008a-93-89 l

1

PALISADES NUCLEAR PLANT Proc No 4.06

~'

ADMINISTRATIVE PROCEDURE Revision 0 Page 24 of 26 i

TITLE:

EMERCENCY OPERATING PROCEDURE DEVELOPMENT AND IMPLEMENTATION 6.9.2 Number of Costes An adequate number of controlled copies of E0Ps available in the Control Room, and at other locations where the EOPs may need to be referred to (eg, Technical Support Center). Distribution of controlled copies will be per Reference 3.12.

6.9.3 Accessibility i

Accessibility refers to the ease with which the operator can identify and access the relevant Emergency Operating Procedures. E0P 4

controlled copies shall be bound in a yellow highlighted binder, and individual procedures tabbed to allow prompt access.

6.9.4 Document control of E0Ps E0Ps shall be controlled per Reference 3.12.

6.9.5 Controlled Conies of E0Ps i

(

All controlled copies of E0Ps should be clearly legible. When it is l

necessary to replace the entire procedure or parts of the procedure because of revisions, use, wear, etc, the quality of the replacement l

copy should be equal to that of the original. Personnel who reproduce pages should ensure that when copies are made, the entire page is l

reproduced (ie, that no instructions or parts of instructions are omitted).

6.9.6 Periodic Review E0Ps shall be periodically reviewed (every two years) per Reference 3.1.

The Periodic Review shall include the following considerations (in addition to those of Reference 3.1):

Evaluation of the technical adequacy of the E0Ps in light of a.

operational esperience and use, training experience, and any simulator esercises and Control Room walk-throughs.

b.

Ess&eation of the organisation, format, style, and content as a reewit of using the procedures during operations, training, simulator esercises, and walk-throughs.

c.

Evaluation of staffing and staff qualifications relevant to using L

the E0Ps.

ado 386-000ga-93-89 i

PALISADES NUCLEAR PLANT Proc No 4.06 ADMINISTRATIVE PROCEDURE Revision 0 Page 25 of 26 TITLEt EMERCENCY OPERATINC PROCEDURE DEVELOPMENT AND IMPLEMENTATION 6.9.7 EOF Revision When changes occur in the Plant design, Technical Specifications, Technical Guidelines, other Plant procedures or Control Room hardware that will affect the E0Ps, the EOPs should be revised on a timely basis to reflect these changes.

In addition, when operating and training experience, simulator exercises, Control Room walk-throughs, or other information indicate that incorrect or incomplete information esists in the EOPs, the E0Ps should be revised on a timely basis.

These changes should be reviewed to ensure consistency with the Technical Guidelines and this procedure.

Revisions to E0Ps are accomplished through the same review and approval process as for new procedures. The Technical Notebook (or Basis Document) shall also be reviewed for continued applicability and revised if appropriate (see Section 6.5).

Procedure changes may be accomplished through the Plant temporary procedure change mechanism (Reference 3.1).

The operations Superintendent is responsible to direct Technical Notebook (Basis Document) review or revision as appropriate.

6.10 WAIVERS Waivers to the requirements of the EOP development and implementation process shall be approved by the Operations Superintendent. General procedure review waiver criteria are specified in Reference 3.1.

Specific waivers in other areas (eg, validation, training, etc) shall also be documented per the general requirements of Reference 3.1 and justified (eg, " simulator and classroom training not conducted this revision since only minor editorial changes were made.")

7.0 ATTACHMENTS AND RECORDS i

i 7.1 ATTACHMENTS 7.1.1 Attachment 1, " Component Identification" 7.1.2 Atta ht 2, " Action Verbs" 7.1.3 Attachment 3, " Abbreviations, Letter Symbols, and Acronyms" 7.1.4 Attachment 4, " Cover Sheet for Basis Document" 7.1.5 Attachment 5, " Quality Assurance Review Checklist" 7.1.6 Attachment 6, " Technical Review Checklist" 7.1.7 Attachment 7, "EOP Validation Evaluation Criteria" ado 386-0008a-93-89

PALISADES NUCLEAR PLANT Proc Na 4.06

~

ADMINISTPATIVE PROCEDURE Revision 0 Page 26 of 26 TITLE:

EMERCENCY OPERATINC PROCEDURE DEVELOPMENT AND IMPLEMENTATION 7.1.8 Attaahamat 8, "EOP Validation Fora" 7.1.9 Attachment 9, " Checklist for Table-Top / Walk-Through Methods of Validation" 7.1.10 Attachment 10 " Checklist for Simulator Method of Validation" 7.1.11 Attachment 11, " Function and Task Analysis" 7.2 RECORDS None 1

i l

l ado 386-0008a-93-89

Proc No 4.06 Revision 0 Page 1 of 9 COMPONENT IDENTIFICATION COMP 0NErr #

DESCRIPTION AE-0203 Boronometer

• C-2A Inste Air Compressor C-28 Instr Air Compressor C-2C Instr Air Compressor CV-1048 Quench Tk De Viv

• CV-0152 Quench Tk Vent Viv

• CV-0155 Quench Tk Spray Vlv

• CV-0437A T-102 Outlet Viv

• CV-04378 T-102 Outlet Viv

• CV-0501 MSIV For S/C 8

• CV-0510 MSIV For S/C A

• CV-05LL Turbine Bypass Valve

• CV-0521 Alt Sta Supply to P-88 From S/C "B" CV-0522A Alt Sta Supply to P-88 From S/C "B" CV-05228 Norm Sen supply to P-88 From S/C "A" CV-0569

1. 1 Stop Valve

• CV-0571

1. 2 Stop Valve

• CV-0573

1. 3 Stop Valve

• CV-0575

1. 4 Stop Valve

• CV-0594 Reheat Sta to MSR "A"

• CV-0595 Reheat Sta to MSR "B"

• CV-0596 Reheat Sta to MSR "C"

• CV-0597 Reheat Sta to MSR "D"

• CV-0701 Feed Reg Viv to S/C A

• CV-0703 Feed Reg Viv to S/C 8

• CV-0710 "B" Feed Pump Recirc Viv

• CV-0711 "A" Feed Pump Recirc Viv

• CV-0729 Hoewell 6" Hakeup Viv

• CV-0730

• Condensate Recirc From Ctand Sem Condenser CV-0731 Condensate Reject Vlv CV-0732 Hoewell 3" Makeup Vlv CV-0734 Feed Reg Viv 8ypass to S/C 8

• CV-0735 Feed Reg Viv Bypass to S/C A

• CV-0736A Aux Feed Flow to S/C 8

• CV-0737A Aux Feed Flow to S/C "A"

• CV-0738 S/C "B" Blowdown to Blowdown Tk t

CV-0739 S/C "A" Blowdown to Blowdown Tk CV-0742 Feed Reg Block Viv to S/C A CV-0744 Feed Reg Stock Viv to S/C 8 CV-0767 S/C A Botton Slowdown Viv CV-0768 S/C 8 Botton Slowdown Viv CV-0770 S/C 8 Botton Blowdown Viv CV-0771 S/C A Botton Blowdown Vlv CV-0779 Atmospheric Dump From S/C 8 CV-0780 Atmospheric Dump From S/C 8 CV-0781 Atmospheric Dump From S/C A j

Component Numbers need not be used in conjunction with these component descriptions I

pa0386-0008b-93-89 l

l

Proc No 4.06 Attachment L Revision 0 Page 2 of 9 COMPOWENT IDENTIFICATION COMPONENT f DESCRIPTION CV-0782 Atmospheric Dump from S/G A CV-0824 Containment Air Coolers Serv Water Return CV-0825 East ESS Room Cooler Serv Wtr Outlet CV-0847 Containment Air Coolers Serv Wtr Supply CV-0861 Containment Air Cooler VHX-1 Serv Wtr Outlet CV-0864 Containment Air Cooler VHI-2 Serv Wer Outlet CV-0867 Containment Air Cooler VHX-4 Serv Wer Outlet CV-0873 Containment Air Cooler VHX-3 Serv Wtr Outlet CV-0878 West ESS Room Cooler Serv Wer Inlet CV-0879 ESS Pump Seal Cooling Serv Wer Supply CV-0880 ESS Pump Seal Cooling Serv Wtr Supply CV-0910 CCW Inlet Isol CV-0911 CCW Return Isol CV-0913 ESS Pumpe Seal Cooling CCW Supply CV-0937 SDC HI CCW Inlet CV-0938 SDC HZ CCW Inlet CV-0939 Shield Cooling Surge Tk Isol 4

CV-0940 CCW Return Isol CV-0944 CCW Supply to Evaporators CV-0944A Spent Fuel Pool CCW Shutoff CV-0945 CCW HI "A" Inlet CV-0946 CCW HI "B" Inlet CV-0947 West ESS Pumps CCW Supply CV-0948 East ESS Pumps CCW Supply CV-0949 ESS Pumps Seal Cooling Isol CV-0950 ESS Pumps CCW Return CV-0951 ESS Pumps Cooling Serv Wer Return CV-09778 CCW Return From Evaporators CV-1001 Primary Sys Dr Tk Recire Isol CV-1002 Primary System DR Tk Outlet Isol CV-1004 CWRT Inlet Isol CV-1007 Primary Sys Tk Outlet Isol CV-1036 CWRT Recire Isol CV-1037 CWRT Recirc Isol CV-1034 CWRT Recire Isol CV-1044 CWRT Outlet Isol CV-1045 CWRT outlet Isol CV-1049 3" RW Disch to Mixing Basin CV-1051 1" RW Disch to Mining Basin CV-1057 Par Spray Viv tros Loop 2A CV-1059 Par Spray Viv From Loop 18 CV-1064 CWRT Vent Isol CV-1065 CWRT Vent Isol CV-1101 Containment Vent Hdr Isol CV-1102 Containment Vent Hdr Isol CV-1103 Containment Susp Dr Isol

• Component Numbers need not be used in conjunction with these component descriptions-pa0386-0008b-93-89 i

my Proc No 6.06 Revision 0 Page 3 of 9 COMPONENT IDENTIFICATION CONPONENT #

DESCRIPTION CV-1104 Containment Sump Dr Isol CV-1113 Waste cas surge Tk to Stack CV-1123 Waste Cas Decay Tk to Stack CV-1211 Inste Air Isol CV-1212 Serv Air Isol CV-1358 Nitrogen Supply Isol CV-1359 Non Critical Serv Wtr Isol CV-1501 Containment Hts Sta Return Isol CV-1502 Containment Hts Sta Return Isol CV-1503 containment Hts Sta Supply CV-1805 Containment Purge Exhaust Isol CV-1806 Containment Purge Exhaust Isol CV-1807 Containment Purge Exhaust Isol CV-1808 Containment Purge Exhaust Isol CV-1813 Air Room Supply Isol CV-1814 Air Room Supply Isol CV-1910 Primary Sys Sampling Isol CV-1911 Primary Sys Sampling Isol CV-2001 Letdown Stop Valve CV-2002 Letdown Orifice Bypass Valve CV-2003 Letdown Orifice Stop Viv CV-2004 Letdown Orifice Stop Viv CV-2005 Letdown Orifice Stop Valve CV-2009 Lecdown Containment Isol CV-2083 Controlled Bleedoff Containment Isol CV-2111 Charging Line Stop Viv CV-2113 Charging Loop 1A Stop Vlv CV-2115 Charging Loop 2A Stop Viv CV-2117 Aux Spray Viv l

CV-2130 BAST "5" Recire CV-2136 BAST "A" Recire CV-2155 Makaup Stop Viv CV-2165 PMW Nakeup Control CV-3001 Containment Spray Hde Isol CV-3002 Containment Spray Hde Isol l

CV-3006 SDC EX Bypass Vlv i

CV-3025 SDC EX Outlet Viv CV-3027 SIRWT Rectre Viv CV-3029 Containment Sump Isol CV-3030 containment Sump Isol CV-3031 SIRWT Outlet l

CV-3037 HPSI P-66A Discharge Hdr CV-3038 T-82D Press Control CV-3042 T-82A Press Control i

CV-3046 T-828 Press Control CV-3047 T-82C Press Control

• Component Numbers need not be used in conjunction with these component descriptions pa0386-0008b-93-89 l

l

i 4

~

Proc N3 4.06 Attachment I tevision 0 Page 4 of 9 COMPONENT IDENTIFICATION COMPONENT #

DESCRIPTION CV-3051 T-82D Vent CV-3055 LPSI Pump Disch Crossover CV-3056 SIRWT tecire Viv CV-3057 SIRWT Outlet CV-3059 HPSI P-665 Disch HDR CV-3063 T-82C Vent CV-3065 T-828 Vent CV-3067 T-82A Vent CV-3069 SIT De to Primary Sys Dr Tk CV-3070 HPSI P-668 SubcoolinB CV-3071 HPSI P-66A Subcooling CV-8206 Condensate Domin Bypass CV-8207 Condensate Domin Outlet CV-8208 Condensate Domin Inlet E-50A S/G A

• E-508 S/C B

• EA-11 Bus 1C

• EA-12 Bus 10

• EC-2 C-2 Panel

• EC-13 C-13 Panet

• EC-33 C-33 Panet

• EC-51 C-51 Panet

• EC-105 C-105 Panel

• EC-126 C-126 Panel

• Ex-15 Par Hte Transformer 15

• EY-10 Pref AC Bus 1

• EY-20 Pref AC Bus 2

• EY-30 Pref AC Bus #3

• EY-40 Pref AC Bus 4

• F-14 Blowdown Filter FI-0301A Containment Spray Hde Flow FI-03015 Containment Spray Hde Flow FI-0302A Containment Spray Hde Flow FI-03028 Containment Spray Hde Flow FI-0307A LPSI Flow to Loop 1A FI-03078 LPSI Flow to Loop 1A FI-0304A HPSI Flow to Loop 1A FI-03088 HPSI Flow to Loop 1A FI-0309A LPSI Flow to Loop 15 FI-03098 LPSI Flow to Loop 18 FI-0310A HPSI Flow to Loop 18 FI-03108 HPSI Flow to Loop 1B' FI-0311A LPSI Flow to Loop 2A FI-03115 LPSI Flow to Loop 2A FI-0312A HPSI Flow to Loop 2A FI-03128 HPSI Flow to Loop 2A

• Component Numbers need not be used in conjunction with these component descriptions pa0386-0004b-93-89 1

r-Proc No 4.06 Attcchment 1 Revision 0 Page 5 of 9 COMPONENT IDENTIFICATION COMP 0NDrr #

DESCRIPTION FI-0316A HPSI Train 2 Cold' Leg Flow FI-0317A HPSI Train 1 Cold Leg Flow FIC-0306 SDC HI Bypass Control Flow FIC-0736A S/C 3 Aux FW Control FIC-07368 S/C 8 Aux FW Control FIC-0737A S/C A Aux FW Control FIC-07378 S/C A Aux FW Control HIC-0526 "A" Feed Pump Speed Control HIC-0529 "B" Feed Pump Speed Control HIC-0701 S/C A FW Control HIC-0703 S/C 8 FW Control HIC-0736A S/C "B" Aux FW Control HIC-0780A Atmospheric Dump Control HIC-07808 S/C 8 Atmospheric Dump Control HIC-07818 S/C A Atmospheric Dump Control HIC-0881 CCW KK Serv Wtr Outlet HIC-0882 CCW KK Serv Wer Outlet HIC-3003 T-82D Drain HIC-3004 T-82C Drain HIC-3039 T-82A Drain HIC-3043 T-828 Drain HS-1221 Air Supply From FWP HS-1801 Control Room Isol Dampers K-2 Turbine Turning Cear

• K-6A D/C 1-1

• K-68 D/C 1-2

• K-7A Feedwater Pump Turbine K-78 Feedwater Pump Turbine K-8 Aux Feed Pump Turbine LI-0702 S/C A Level

• LI-0704 S/C 8 Level

• LI-0757A S/C A Wide Range Level

• LI-07578 S/C A Wide Range Level

• LI-0758A S/C 8 Wide Range Level

• LI-07588 S/C 8 Wide Range Level

• LI-1107A West ESS Ra Sump LI-11078 West ESS Ra Sump LI-1110A East ESS Ra Sump LI-11108 East ESS Ra Sump LIA-0116 Quench Tank Level LIA-0331 SIRWT Level LIA-0358 Containment Susp Level LIA-0359 Containment Susp Level LIA-0365 T-82A Level

• l LIA-0368 T-828 Level

• r LIA-0372 T-82C Level *

• Component Numbers need not be used in conjunction with these component descriptions

(

pa0386-0008b-93-89 L

.3 Proc No 4.06 Revision 0 Page 6 of 9 COMPONENT IDENTIFICATION COMPOWENT #

DESCRIPTION LIA-0374 T-82D Level

• LIA-1400 T-10 Level LIA-1416 D/G 1-1 Day Tk Level LIA-1417 D/G 1-2 Day Tk Level LIA-2021 T-2 Level LIA-2022 T-2 Level Ho-0501 S/G B HSIV Bypass Viv

• HO-0510 S/G A HSIV Bypass Viv

• HO-1042A PORY Isol Viv HO-1043A PORY Isol Viv HO-2087 VCT Outlet H0-2140 Boric Acid Pumped Feed HO-2160 SIRWT to Charging Pump Suction H0-2169 Boric Acid Gravity Feed NO-2170 Boric Acid Gravity Feed Ho-3007 HPSI Loop 1A HO-3008 LPSI Loop 1A N0-3009 HPSI Loop 18 HO-3010 LPSI Loop 1B HO-3011 HPSI Loop 2A HO-3012 LPSI Loop 2A 1

MO-3013 HPSI Loop 28 MO-3014 LPSI Loop 28 HO-3015 Shutdown Cooling Wtr Return MO-3016 Shutdown Cooling Wtr Return HO-3041 T-82A Outlet Ho-3045 T-828 Outlet HO-3049 T-82C Outlet l

HO-3052 T-82D Outlet HO-3062 HPSI Loop 28 Train 2 MO-3064 HPSI Loop 2A Train 2 MO-3066 HPSI Loop 15 Train 2 MO-3068 HPSI Loop 1A Train 2 HO-3080 HPSI Train 2 Cold Les NO-3081 HPSI Train 1 Cold Les HO-3082 HPSI Train 2 Hot Les HO-3083 HPSI Train 1 Hot Leg l

HO-3189 P-678 Inlet, LPSI HO-3190 P-678 Inlet, Shutdown Cooling H0-3198 P-67tfInlet, LPSI HO-3199 P-67A Inlet, Shutdown Cooling l

HO-5301 West Water Box Inlet Viv Ho-5302 East Water Box Inlet VLv Ho-5326A Basin "A" Blowdown Line Viv Ho-53268 Basin "B" Blowdown Line VLv P-1A Main Feed Pump *

• Component Numbers need not be used in conjunction with these component descriptions pa0386-0008b-93-89 i

L

r..

Proc No 4.06 Attcchment 1 Revision 0 Page 7 of 9 COMPOWENT IDENTIFICATION COMPONENT f DESCRIPTION P-15 Main Feed Pump

• P-2A Condensate Pump

• P-28 Condensate Pump

• P-5 Wars Wer Recirc Pump P-7A Serv Wtr Pump

• P-75 Serv Wer Pump

• P-7C Serv Wer Pump

• P-84 Motor Driven Aux' Feed Pump

• P-8B Steam Driven Aux feed Pump

• P-4C Motor Driven Aus Feed Pump

• P-10A Heater Dr Pump

• P-108 Heater Dr Pump

• P-39A Cooling Tower Pump

• P-395 Cooling Tower Pump

• P-40A Dilution Wtr Pump

• P-408 Dilution Wtr Pump

• P-45A Turbine Bldg Sump Pump P-458 Turbine BLd3 Sump Pump P-50A Primary Coolant Pump

• P-508 Primary Coolant Pump

• P-50C Primary Coolant Pump

• P-50D Primary Coolant Pump

• P-51A Fuel Pool Cooling Pump P-518 Fuel Pool Cooling Pump P-52A CCW Pump

• P-528 CCW Pump

• P-52C CCW Pump

• P-54A Containment Spray Pump

• P-548 Containment Spray Pump

• P-54C Containment Spray Pump *'

P-55A Charging Pump

• P-558 Charging Pump

• P-55C Charging Pump

• P-56A Boric Acid Pump

• P-565 Boric Acid Pump

• P-66A HPSI Pump

• P-665 HPSI Pump

• P-67A LPSI Pump

• P-678 LPSI Pump

• PI-0783 Aus Feed Pump Disch Press PI-1106 ESS Rm Sump Pumps Disch Press PI-1108 ESS Em Sump Pumps Disch Press PI-1805 Containment Press PIA-0116 Quench Tk Press PIA-1814 Containment Press PIA-1815 Containment Press

• Component Numbers need not be used in conjunction with these component descriptions pa0386-0008b-93-89

Proc No 4.06' Revision 0 Page 8 of 9 COMPONENT IDENTIFICATION COMPOWENT #

DESCRIPTION FIC-0101A Par Press Control PIC-0101B Par Press Control PIC-0202 Intermediate Letdown Press Control PIC-0334 T-82D Press Control PIC-0342 T-82A Press Control PIC-0344 T-82B Press Control PIC-0347 T-82C Press Control PIC-0511 Turbine Bypass Viv Control PCV-0521A Aus Feed Pump Sta Supply control PCV-6003 Blowdown Tk Relief Control PCV-6004 Blowdown Tk Outlet Control PRC-0101A Par Press control 1

PRC-01015 Par Press Control PRV-19428 PORV*

PRV-10438 PORV*

PRV-1047 Reactor Vent Viv PRV-1044 Reactor Vent Viv PRV-1969 Par Vent Viv PRV-1070 Par Vent Viv PRV-1071 Vent Viv to Containment Atmosphere PRV-1072 Vent Viv to Quench Tk

]

PS-0104 Par Press 1

RIA-0202 Failed Fuel Monitor RIA-0631 Off Ces Monitor RIA-0707 Radweste Liquid Disch Monitor RIA-1113 Waste ces Disch Monitor RIA-1805 containment Isol Monitor l

RIA-1806 Containment Isol Monitor i

RIA-1807 Containment Isol Monitor RIA-1808 Containment Isol Monitor RIA-2319 Stack Cas Monitor RIA-5710 Penetration & Fan Room Monitor i

RV-1039 Par Code Safety Viv*

l RV-1040 Par Code Safety Viv*

l RV-1941 Par Code Safety Viv*

j SMN-0114 Subcooling Margin Monitor l

SMM-0124 Subcooling Margin Monitor SV-0505A S/C 8 MSIV i

SV-05055 5/C A MSIV l

SV-0507A S/C 8 MSIV l

l SV-05078 S/C A MSIV i

T-2 Condensate Storage Tk

• l T-3 CCW Surge Tk

• T-10 Diesel Oil Storage Tk T-26A Feedwater Turbine Dr Tk T-268 Feedwater Turbine Dr Tk

• Component Numbers need not be used in conjunction with these component descriptions pa0344-0008b-93-89

c Proc No 4.06 Attachment i Revision O' Page 9 of 9 COMPONENT IDENTIFICA*fION COMP 0FENT,f DESCRIPTION T-29 Blowdown Tk T-58 SIRWT

• T-60 Dirty Waste Drain Ik T-64A-D Clean Waste Receiver Ik

• T-81 Prinsey Sys Makeup Tk T-82A Safety Injection Ik

• T-828 Safety Injection Tk

• T-82C Safety Injection Tk

• T-82D Safety Injection Tk

• T-90 Primary Maktsup Wtr Storage Tk T-92A Misc Waste Hold-up Tk T-928 Misc Wasta Hold-up Tk T-92C Misc Waste Hold-up Tk T-102 Hydrazine Tk T-104 Blowdown Domin T-939 Domineralized Utr Storage Tk TI-0115C Loop 1 Cold Led Temp

• TI-0125C Loop 2 Cold Les Temp

• TI-0912 SDC HX "A" Outlet Temp

• TI-0913 SDC EX "B" Outlet Temp

• TIA-0106 Relief & Safety Viv Disch Temp

• TIA-0107 Relief & Safety Viv Disch Temp

• TIA-0108 Relief & Safety Viv Disch Temp

• TIA-0109 Relief & Safety Viv Disch Temp

• TIA-0116 Quench Tk Temp

• V-1A Containment Recire Fan V-18 Containment Recire Fan V-2A Containment Recire Fan V-28 Containment Recire Fan V-3A Containment Recirc Fan V-38 Containment Recirc Fan V-4A Containment Recire Fan' V-48 Containment Recirc Fan V-69 Aux Bldg' Addition Fuel Handling Area Supply Fan V-70A Aux Bids Addition Fuel Handling Area Exhaust Fan V-708 Aux Bldg Addition Fuel Handling Area Exhaust Fan 042-1 EPS RPS Clutch Power Supply 042-2 RPS RPS Clutch Power Supply 152-0102CS P-40A Dilution Pump control Switch

• l l

{

• Component Numpers need not be used in conjunction with thesa component descriptions pa0386-0008b-93-89

r Proc No 4.06 Revision 0 Page 1 of 1 ACTION VERBS Verb Application Allow To permit a stated condition to be achieved prior to proceeding Check To perform a comparison with a procedural requirement Close To change the physical position of a mechanical device so that it prevents physical access or flow or permits passage of electrical current Complete To accomplish specified procedural requirements Decrease Do Not use because of oral communications problems (use " Lower" or " Reduce" instead)

Establish To make arrangements for a stated condition Increase Do Not use because of oral communications problems (use " Raise" instead)

Inspect To measure, observe, or evaluate a feature or characteristic for comparison with specified limital method of inspection should be included Open To change the physical position of a mechanical device, such as valve or door to the unobstructed position that permits access or flow Record To document specified condition or characteristic Set To physically adjust to a specified value on adjustable feature Shut DO NOT use.

(Use "Close" instead)

Start To originate motion of an electric or mechanical device directly or by remote control Stop To terminate operation Throttle To operate a valve in an intermediate position to obtain a certain flow rate Trip To manually activate a semi-automatic feature Vent To permit a gas or liquid confiaed under pressure to escape at a vent l

Verify To observe an expected condition or characteristic ado 386-0008c-93-89 i

t

e r-PrQC No 4.Q Attachment Revision 0 Page 1 of 3 AggEEVIATIONS. LETTER SYMBOLS AND ACRONYMS Alternating Current NC A-C Natural Circulation

=

=

Auaillary Feedwater Actuation NPSH

=

AFAS Net Positive Suction Head

=

System NSSS Nuclear Srsam Supply System

=

Ausiliary Feedwater ONP AFW Off Normal Procedure

=

=

Ausiliary PCP Primary Coolant Pump AUX

=

=

Breaker PCS Primary Coolant System BKR

=

=

Building PCV 8LDC Pressure Control Valve

=

=

Component Cooling Water PLCS

=

Pressurizer Level Control CCW

=

Core Exit Thermocouple System CET

=

Containment High Pressure PORY CHP Power Operated Relief Valve

=

=

Containment High Radiation PPCS CHR Pressurizer Pressure Control

=

=

Containment Isolation Actuation System CIAS =

Signal PRC Plant Review Committee

=

Containment Isolation System PSI CIS

=

Pounds Per Square Inch

=

Charging PSIA CHC Pounds Per Square Inch Absolute

=

=

Containment PSIC CONT =

Pounds Per Square Inch Cauge

=

Control Rod Drive PZR

=

Pressurizer CRb

=

Control Valve R

=

CV REM

=

Chemical Volume Control System RAS

=

Recirculation Actuation Signal CVCS

=

Direct Current RECIRC = Recirculation D-C

=

D/C Diesel Generator RIA Radiation Indicator Alare

=

=

D/P Differential Pressure RPS

=

Reactor Protection System

=

Resistance Temperature Detector EMERG = Emergency RID

=

Emergency Operating Procedure RV

=

Relief Valve E0P

=

ESDE Excess Steam Demand Event EK Reactor

=

=

Engineering Safeguards System SDC Shutdown Cooling ESS

=

=

• F Degrees Fahrenheit SDCHX Shutdown Cooling Heat Exchanger

=

=

'F/He = Degrees Fahrenheit Per Hour S/C

= Steam Cenerator Feed Only Coed Generator SGTR

=

FOCC Steam Generator Tube Rupture

=

General Operating Procedure SI Safety Injection C0P

=

=

Callons Per Minute SIAS Safety Injection Actuation CPM

=

=

Hydrogen Signal H2

=

Safety Injection Refueling HDR

=

Header SIRWT

=

High Pressure Safety Injection Water Tank HPSI

=

Safety Injection System Hour SIS HR

=

=

Hand Switch SOP System Operrting Procedure HS

=

=

Standard Post Trip Actions HTR

= Heater SPTA

=

Heathmg Ventilating Air SUR

=

RVAC Startup Rate

=

Conditioning SW

=

Service Water Haag amehanger AT Differential Temperature EX

=

=

Loss of Coolant Accident Te LOCA =

cold Les Temperature

=

Low Pressure Safety Injection TH Not Leg Temperature LPSI

=

=

LTOP =

Low Temperature Overpressure TAVg Average Temperature

=

Protection TSC Technical Support Center

=

Messanine Turb

=

Turbine MEZZ

=

Motor Operated Valve UV MOV

=

Undervoltage

=

Millires V

MR Volts

=

=

MR/HR = Millires Per Hour VCT Volume Control Tank

=

Main Steam Isolation Valve XFMR MSIV Transformer

=

=

Moisture Separator Reheater MSR

=

Percent

=

ado 386-0008d-93-89

s Pece No 4.06 C

Revision 0 Page 1 of 1 EMERGENCY OPERATING PROCEDURE BASIS DOCUMENT FOR Number DISTRIBUTION:

ORIGINAL (Master) Emergency Operating Procedure File CONTROLLED COPY

1) Control Room

2) Training Department REV AUTHOR DATE ITECHNICAL REVIEWER DATE OPS SUPT APPROVAL

_DATE cdO386-0008e-93-89

=

r Prec so 4.06 Revision 0 Page 1 of 3 OiERCDCY OPERAtiliC PROCEDURE QUALITY A2$UEANCE REVIEW CHgCXLIST NUM8Gt________,_ _ _ _ TITLI.t __

BEVISION Y-N-N/A 1.

Are title block inforfastion, section and. subiectiod bezdings; and fcrmat in eccordenes with Admins 10.41 and 4.66T 2.

It procedure numbering in accordsr.ca with Admin 10.41 and 1G 427 3.

Is component identifiestion in accordance vlth Main t. 057 4.

A'te lastruction steps num' ered carrectly'?

n 3.

Are instructigt.t steps constincted to comply with the followings (a) Steps deal, with only one ides.

(b) Sentences are short and simple.

{c) Operator accions are specifically stated.

(d) objects of operator action # are specifically st4ted.

(s) Oujects of operator actions are adequately stated.

(f) ff there are four or mora objects, they are listed (and spacs ia provided ' or operator chetk-off).

f (g) Punctuation and cap {talization are proper.

(h) Atbreviati0no are cotrset and undecetandable to the operecer.

6.

Do ins ~cruaties) stepe make proper use of logic structure?

7.

When sa W ee instr 9etion is based.on receipt 6f an annunciater altru, Et the setpcint 4.1 thf altra ideentified]

8.

Are cauticas ased appropria.taly?

9.

Are cactions placed pecperty?

ado 386-0008f-93.59

Proc No 4.06 Revision 0 Page 2 of 3 EMERCENCY OPERATINC PROCEDURE QUALITY ASSURANCE REVIEW CHECKLIST

10. Are cautions constructed to comply with the followings (a) They do not contain operator actions.

(b) They do not use extensive punctuation for clarity.

(c) They make proper use of emphasis.

11.

Are notes properly used?

12.

Are notes properly placed?

13. Are notes worded so that they do not contain operator actions?

14.

Are numerical values properly written?

15. Are values specified in such a way that mathematical operations are not required of the user?

16.

Is a chart or graph provided in the procedure for necessary operation calculations?

i 17.

Do the referenced and branched procedures identified in the E0Ps exist for operator use?

18. -Is the use of referencing reinimized?

19. Are referencing and branching instructions correctly worded?

(a)

"go to" (branching)

(b) " refer to" (referencing) 20.

Do the instructions avoid routing users past important information such as cautions proceeding steps?

21.

Are the east conditions compatible with the entry conditions of the radarenced or branched procedure?

ado 386-0008f-93-89

Proc No 4.06 Attachmint 3 Revision 0 Page 3 of 3 EMERCENCY OPERATING PROCEDURE QUALITY ASSURANCE REVIEW CHECKLIST l

l I

22.

Comments (use Form 3110's for additional space):

23. Quality Assurance Review Completed Byt

/

Date 24.

Comments Resolved By:

/

Date ado 386-0008f-93-89 l

l

e l

(

Pro, No 4.06 Attschment 6 Revision 0 Page 1 of

• i EMERCENCY OPERATING PROCEDURE TECHNICAL REVIEW CliECKLIST NUMBEtt TITLEI REVISION:

Y-N-N/A

• 1.

Are units of measurement in the EOP the :(De as those used on equipment?

2.

Are entry conditions or symptome correct end not excessive?

3.

Are differences between CEN-lS2 and E0P adequately documented? (ie, Basis Document Discriptiot or Technical Notebook) 4.

Is the technical strate 3y of CEE-i$2 mair.t.alned by the as written E0P7 s

5.

Are correct Plant-specific adaptations incorporated f rom CEN-152 in the E0P? (ie, sy, stems, instrumentatiot, limits, controls and indicacicas) 6.

Have any licensing coemitments applicable to the E0? been addressed?

I 7.

Are differences between licensing coesiteents and the E0P or CEN-152 documented? (ie, Basis Documert discripcion or e

Technical Notebook) 8.

Are quantitative vaines (iocludinx telerance bands) oyed in the E0P comply with the applicable EQP sour:e documents?

i 9.

Where CEN-152 values are noc used ir,che E0P, are the EDP values computed correctly?

10.

Whwre calculations are required in the ECP, are Aquatio6s presented with sufficient information for cperator use?

• 11.

Is the Plant Hardware specified in the E0P available for operator use (ie, equipment, controls, indicatoro and instrummatation)?

12.

Is the language and level of detail presented in the E0P compatible with the qualifications, training saa experience of the operating staff?

l i

I i

1 Part of Control Room Walkthrough ado 386-00083-93-89

Proc No 4.06

~

Revision 0 Page 2 of 2 DfEECENCY OPEnATING PROCEDURE TECHNICAL REVIEW CHECKLIST

13. Are operator optiorial sequence steps idgetified?

14. Source Documeltes usedt (a) CEM-152 Rev (b) Palisades function and Task Analysis Zaport Dated (c) FSAR Sections (d) Technical Specification Secticas

'(e) Pai.isadas Admin Procendures 4.06, 16.l.1 (f) Others

15. Comments (use Form 3110's for additional space):

l l

l

16. TechnicsL Bavierv Performed By

/

Date

17. Cosaments tesolved Byt

/

Date dfC386-0CC6 89 3

I i

j

,a Proc No 4.06 Revision 0 Page 1 of 3 EMERCENCY OPERATION PROCEDURE VALIDATION EVALUATION CRITERIA Applicable Tot I.

USABILITY (Y/N)

T-T W-T S

A.

LEVEL OF DETAIL Y

Y Y

1.

Is there sufficient information to perform the j

specified actions at each step?

Y Y

Y 2.

Are the alternatives adequately described at each decision point?

Y Y

Y 3.

Are the labeling, abbreviations and location information as provided in the E0P sufficient to enable the operator to find the needed equipment?

Y Y

Y 4.

Is the E0P missing information needed to manage the emergency condition?

Y Y

Y 5.

Are the contingency actions sufficient to address the symptoes?

Y Y

Y 6.

Are the titles and numbers sufficiently descriptive to enable the operator to find referenced and branched procedures?

d B.

UNDERSTANDABILITY Y

Y Y

1.

Is the E0P easy to read?

Y Y

Y 2.

Are the figures and tables easy to read with accuracy?

Y Y

Y 3.

Can the values on figures and charts be easily determined?

l Y

Y Y

4.

Are caution and note statements readily l

understandable?

t Y

Y Y

5.

Are the E0P steps readily understandable?

T-T = Table-Top Validation Method l

W-T - Walk-Through Validation Method S - Simulator Validation Method ado 386-0008h-93-89

Proc No 4*.06 --

Attechment 7 Revision 0 Page 2 of 3 EMERGENCY OPERATION PROCEDURE VALIDATION EVALUATION CRITERIA Applicable Tor (Y/N)

T-T W-T S

II. OPERATIONAL CORRECTNESS A.

PLANT COMPATIBILITY N

Y Y

1.

Can the actions specified in the procedure be performed in the designated sequence?

Y Y

Y 2.

Are there alternate success paths that are not included in the EOPs?

N Y

Y 3.

Can the information from the Plant instrumentatioc be obtained, as specified by the E0P?

N N

Y 4.

Are the Plant symptoms specified by the EOP adequate to enable the operator to select the applicable E0P7 N

N Y

5.

Are the EOP entry conditions appropriate for the Plant symptoms displayed to the operator?

N Y

Y 6.

IsinformationorequipmentnotspecifiedinthJ EOP required to accomplish the task?

N Y

Y 7.

Are the instrument readings and toleranc'es stated in the E0P consistent with the instrument values displayed on the instruments?

i N

Y Y

8.

Is the EOP physically compatible with the work situation (too bulky to hold, binding would not allow them to lay flat in work space, no place to lay the EOPs down to use)?

N Y

E 9.

Are the instrument readings and tolerances specified by the EOP for remotely located t

I instruments accurate?

T-T = Table-Top Validation Method W-T - Walk-Through Validation Method S - Simulator Validation Method ado 386-0008h-93-89 l

t

Proc No 4.06 Revision 0 Page 3 of 3 EMERCENCY OPERATION PROCEDURE VALIDATION EVALUATION CRITERIA Applicable Tot (Y/N)

T-T W-T S

8.

OPERATOR COMPATIBILITY N

Y Y

1.

If time intervals are specified, can the procedures action steps be performed on the Plant within or at the designated time intervals?

N Y

Y 2.

Can the procedure action steps be performed by the operating shift?

N Y

Y 3.

If specific actions are assigned to individual shif t personnel, does the EOP adequately aid in the coordination of actions among shift personnel where necessary?

N Y

Y 4.

Can the operating shift follow the designated action step sequences?

N Y

Y 5.

Can the particular steps or sets of steps be readily located when required?

N Y

Y 6.

Can procedure exit point be returned to without omitting steps when required?

Y Y

Y 7.

Can procedure branches be entered at the correct point?

Y Y

Y 8.

Are EOP exit points specified adequately?

T-T = Table-Top Validation Method W-T - Walk-Through Validation Method S - Simulator Validation Method ado 386-0008h-93-89 i

a-

Proc No I. 06 Attachmint 8 R3 vision 0 Page 1 of 4 EMERCENCY OPERATION PROCEDURE VALIDATION FORM A.

EOP IDENFIFICATION 1.

Number Revision 2.

Title 5.

VALIDATION METHOD (CIRCLE)

TABLE-TOP WALXTHROUCH SIMULATOR C.

EVENT INITIATOR 1.

Major Failure 2.

Additional Failures D.

INITIAL CONDITIONS 1.

Power Level, %

2.

Time At Power, Hrs.,

3.

Pressurizer Pressure, psia 4.

Pressurizer Level, %

5.

Steam Generator Level, %

6.

Steam Generator Pressure, psia 7.

Baron Concentration, ppe 8.

Case Life, MWD /MT 9.

Electric Lineup Normal Other ado 386-0008i-93-89

)

Proc No is.0 AttacFa:2nt Revision 0 Page 2 of 4 EMERCENCY OPERATION PROCEDURE VALIDATION FORM E.

CONTROL SYSTEM STATUS 1.

CVCS Makeup Mode Pressuriser Level Control Auto Manual Number of Charging Pumps Available 1

2 3

Charging Pump Control Status Letdown Auto Manual 2.

Pressurizer Pressure Control Auto Manual 3.

Steam Generator Level Control Number of Feedpumps Feedpump Speed Control Auto Manual Feed Regulating Valve Control Auto Manual 4.

Steam Bypass Control Auto Manual 5.

Atmospheric Dump Valves Auto Manual F.

SCENARIO DESCRIPTION ado 386-0008i-93-89 1

Proc No 4.06 Attacamtnt 8 Revision 0 Page 3 of 4 EMERGENCY OPERATION PROCEDURE VALIDATION FORM C.

REQUIRED OPERATION ACTIONS H.

ACCEPTANCE CRITERIA I.

DESIN^* OBSERVER / REVIEWER (S)

Preparation Completed By Date l

l ado 386-0008i-93-89

Proc No 4.06 Attachm2nt Revision 0 Page 4 of 4 EMERCENCY OPERATION PROCEDURE VALIDATION FORM J.

OPGMOR PARTICIPANTS:

QUALIFICATION:

(SRO. RO. OTHER)

K.

DISCREPANCIES / COMMENTS DURING EVALUATION:

1 l

l

{

Evaluator Date L.

RESOLUTION OF DESCREPANCIES/ COMMENTS:

I i

1 l

Resolved By Date Validation Approved / Acceptable YES NO (circle one)

~

Operations Superintendent Date ado 386-0008i-93-89

Proc No 4.06 Revision 0 Page 1 of 3 CHECKLIST FOR TABLE-TOP /

WALK-THROUCH METHODS OF VALIDATION 1.0 PURPOSE The purpose of this checklist is to provide guidance for the table-top

~

and walk-through methods of validating EOPs.

2.0 VALIDATION PROCESS E0P validation will be conducted in four parts:

preparation, assessment, resolution and documentation.

2.1 PREPARATION The designated observer / reviewer will be responsible for the followings a.

Using and completing the E0P Validation Form (Attachment 8) b.

Reviewing the scope of the validation designated by the Operations Superintendent or his representative Developing or modifying scenarios to support the scope of c.

validation and filling out this information on Attachment 8 d.

Modifying / selecting the developed evaluation criteria to support the scope of validation e.

Assist in selecting operators that are representative of the training level expected of all the operators f.

Scheduling the needed resources for table-top 1.

Observer / Reviewer 2.

Operator (s) Involved 3.

Conference Roon l

4.

Sets of EOPs and Support Procedures 3

gebeduling the needed resources for walk-through 1.

Observer / Reviewer (s) 2.

Operator (s) Involved 3.

Control Room or Control Room Mock-Up l

4.

Set of E0Ps and Support Procedures i

i ado 386-0008j-93-89

Proc No 4*.06

Revision 0 Page 2 of 3 CHECKLIST FOR TABLE-TOP /

WALK-THROUGH METHODS OF VALIDATION

2.2 ASSESSMENT

The designated observer / reviewer will perform the following duties:

a.

Brief the operator (s) on the scope of validation and how the assessment will be conducted.

b.

Foll V.no developed or modified scenario by first giving the Plan' nitial conditions and then give the changing Plant i

parameters as talking or walking through the procedures.

c.

Stop the talk-through or walk-through assessment for discussion of any identified discrepancies.

d.

Conduct a debriefing with the operators as soon as possible after each walk-through assessment, using the following sequence:

1.

Brief the participants on the purpose and objectives for debriefing.

2.

Have operators present problems and discrepancies which they had identified during assessment.

3 3.

Present other problems and discrepancies identified during i

assessment.

4.

Have operators provide possible reasons for problems.

5.

Summarize the findings of the debriefing for the operators.

i l

l e.

Record discrepancies and comments on Attachment 8.

l 2.3 RESOLUTION I

The designated observer / reviewer wiLL perform the following a.

dutiest 1.

Review consents and discrepancies 2.

Propose resolutions on Attachment 8 and submit the validation package to the Operations Superintendent.

b.

The Operations Superintendent will perform the following duties:

1.

Review proposed resolutions.

2.

Approve resolutions for incorporation in the E0Ps.

ado 386-0008j-93-89

f.

Proc No 4.06 Revision 0 Page 3 of 3 CHECKLIST FOR TABLE-TOP /

WALK-THROUGH METHODS OF VALIDATION 3.

Ensure EOPs are revised as necessary in a timely manner per approved resolutions.

2.4 DOCUMENTATION The following documentation will be included in the validation package which will become part of the procedure working file:

a.

Completed Attachment 8 b.

Evaluation Criteria used (Attachment 7)

Other supporting documentation (eg, Document revision requests, c.

etc) l l

l

(

ado 386-0008j-93-89

(

I

a Proc No 4.06 0 Revision 0 Page 1 of 2 CHECKLIST FOR SIMULATOR METHOD OF VALIDATION 1.0 PURPOSE The purpose of this checklist is to provide guidance for the simulator method of validating E0Ps.

2.0 VALIDATION PROCESS E0P validation will be conducted in four parts: preparation, assessment, resolution and documentation.

2.1 PREPARATION The designated observer / reviewer will be responsible for the following:

a.

Using and completing the E0P Validation Form (Attachment 8).

b.

Reviewing the scope of the validation as directed by the Operations Superintendent or his representative.

Completing Items A through F on Attachment 8 and forwarding a copy c.

to the Simulator Supervisor.

d.

Developing or modifying scenario runs to support the scope of validation.

e.

Developing Data Collection Techniques.

i f.

Evaluating Plant-to-Simulator characteristics.

g.

Assist in selecting and scheduling the operating crews.

h.

Modifying / selecting the evaluation criteria to support the scope of validation.

i. Ensuring the E0Ps and supporting procedures are available.

2.2 AS M The designated observer / reviewer will perform the following duties:

a.

Brief the operating crew on the scope of the validation and how the assessment will be conducted.

i b.

Ensure the observer / reviewer does not interfere or interact with the operating crew.

c.

Brief the operating crew on initial Plant conditions for each scenario run.

l ado 386-0008k-93-89 i

s,,_.

-.... -. - ~

s Proc No d.06 0 Revision 0 Page 2 of 2 CHECKLIST FOR SIMULATOR METHOD OF VALIDATION d.

Conduct a debriefing with the operators as soon as possible after each scenario run using the following sequence:

1.

Brief the participants on the purpose and objectives for debriefing.

2.

Have operators present problems and discrepancies which they had identified during assessment.

3.

Present other problems and discrepancies identified during assessment.

4.

Have operators provide possible reasons for problems.

5.

Summarize the findings of the debriefing for the operators.

e.

Record discrepancies and comments on Attachment 8.

2.3 RESOLUTION The designated observer / reviewer will perform the following s.

duties:

1.

Review comments and discrepancies.

2.

Propose resolutions on Attachment 8 and submit the validation package to the Operations Superintendent.

b.

The Operations Superintendent will perform the following duties:

1.

Review proposed resolutions.

2.

Approve resolutions for incorporation in the E0Ps.

3.

Ensure E0Ps are revised as necessary in a timely manner per j

approved resolutions.

I 2.4 DO M ATION l

The fellowing documentation will be included in the validation package l

which will become part of the procedure working files a.

Completed Attachment 8.

I I

b.

Evaluation criteria used (Attachment 7).

c.

Other supporting documentation (eg, Document review requests, l

etc).

ado 386-0008k-93-89

r

,a Proc No 4.06 1 Revision 0 Page 1 of 5 FUNCTION AND TASK ANALYSIS 1.0 CENERAL The safety functions contained in CEN-152' provide the basis for the function analysis. The resource trees found in CEN-152 will be independently developed in a plant specific fashion to identify:

a.

Success criteria for each safety function b.

Modes of control for each success path c.

Transient characteristics d.

Operator actions e.

Operator information and control needs f.

Equipment requirements 2.0 FUNCTION AND TASE ANALYSIS PARTICIPANTS An interdisciplinary team of individuals assigned by the Operations Superintendent shall perform the function and task analysis. This team shall include individuals experienced in the areas of:

a.

Transient analysis of emergency events b.

Human factors engineering (ie, detailed control room design review (DCRDR))

c.

Plant operations (ie, licensed SRO or RO) 3.0 FUNCTION ANALYSIS The function analysis consists of three parts:

Identification and definition of safety functions (SF). This is a.

completed in Sections 3.1 through 3.3 below.

b.

Identification of modes of control for each SF based on the transient status of key parameters, plant equipment availability and plant response characteristics. These modes of control will be referenced as " success paths" following the terminology of CEN-152. Flow charts (or logic diagrams) will be prepared for each success path of ea:h SF l

tesessisfy this requirement.

Iku$aificationofsuccesscriteriaofthesuccesspathsforeachSF.

c.

3.1 CLASSIFICATION OF SFs

~

Seven SFs must be fulfilled. All are directed at mitigating an event or containing and/or controlling radioactivity releases. These SFs can be grouped into three major classes as follows:

l a.

Anti-core melt SFs b.

Containment integrity SFs c.

Maintenance of vital auxiliaries needed to support other SFs l

ado 386-00081-93-89 1

7 Proc No 4.06 1 Revision 0 Page 2 of 5 f

FUNCTION AND TASK ANALYSIS The number of SFs in the anti-core melt class is four, down from the five contained in CEN-152. The two CEN-152 safety functions, namely core heat removal and reactor coolant system heat removal have been combined into a single SF named PCS temperature control.

The containment integrity class contains two SFar i

a.

Containment Isolation b.

Containment Atmosphere Control The number of SFs in the containment integrity class is two, down from the three contained in CEN-152. The containment temperature and pressure control safety function, and the containment combustible gas control safety function have been combined into the single SF named containment atmosphere control.

3.2 DEFINITIONS OF SFs a.

Definitions of the anti-core melt SFs ares 1.

Reactivity Control (RC)

The purpose of reactivity control is to achieve and maintain a shutdown condition in the reactor.

2.

PCS Inventory Control (IC)

The purpose of maintaining PCS inventory control is to provide a medium for the removal of decay heat.

3.

PCS Pressure Control (PC)

The purpose of PCS pressure control is to maintain' the PCS subcooled and prevent the loss of inventory through the pressuriser power operated relief valves (PORVs) and/or safety valves thereby preventing release of radioactive liquid to the containment and possibly the atmosphere. The control of the

===4=== PCW pressure within Technical Specification limits is important to minimize the potential for pressurized thermal shock.

4.

PCS Temperature Control (TC)

The purpose of the PCS temperature control function is to remove decay heat and cool the PCS to a stable heat removal condition.

ado 386-00081-93-89

Proc No 4.06 1 Revision 0 Page 3 of 5 FUNCTION AND TASK ANALYSIS b.

Definitions of the containment integrity class are:

1.

Containment Isolation (CI)

The purpose of the containment isolation function is to maintain closure / blockage of those flow paths required to isolate the containment following an event characterized by an increase in containment pressure and/or radioactivity levels or an increased risk of release of activity through a steam generator with leaking tubes.

2.

Containment Atmosphere Control (CA)

The purpose of the containment atmosphere control function is to maintain the containment temperature, pressure, and combustible gas concentration within their design limits. This will protect the final barrier to fission product release and prevent damage to vital equipment.

c.

Definitions of the remaining SF is:

1.

Maintenance of Vital Auxiliaries (MVA)

The purpose of maintaining vital auxiliaries is to assure that suppnet systems used to accomplish SFs described above are kept in service. Of greatest impact to the operator actions associated with successfully accomplishing the other SFs is vital AC and DC power. This initial function and task analysis will be directed explicitly at actions for maintaining vital.AC and DC power.

3.3 SF HIERARCHY The SF concept incorporates a principle of hierarchy (ie, some SFs have precedence over others as far as their sequence of implementation during an event). The following hierarchy will be utilized at Palisades:

SF HIERARCHY Reactivity Control l

Maintenance of Vital Auxiliaries PCS Inventory Control PCS Pressure Control PCS Temperature Control Containment Isolation Containment Atmosphere Control l

i l

ado 386-00081-93-89 L

e

• r, Proc No 4.06 1 Revision 0 Page 4 of 5 FUNCTION AND TASK ANALYSIS 4.0 TASK ANALYSIS Task analysis effort is a detailed extension of the function analysis effort which determines the actual tasks to be performed and the instrumentation and control needs of the operator to perform specific tasks must be determined.

It is assumed for the function and task analysis of the E0P upgrade effort that the operator is fully trained and experienced in the details of component operation. The tasks and step-by-step details will be stated using the terminology unique to the Palisades Plant with which operators are familiar. This terminology alignment is one of the major tasks in the function and task analysis.

4.1 The task analysis will be performed on the Functional Recovery Guidelines (FRCs) of CEN-152 only. The diagnosed events for which Optimal Recovery cuidelines (ORCS) of CEN-152 are presented contain identical steps to satisfy the safety functions, therefore, operator action, decisions, etc, are fully covered in the detailed analysis of the Functional Recovery Guidelines.

4.2 Tasks will be listed as steps to perform the functions or operator actions in the flow charts created in the function analysis. Tasks will be identified by analyzing the system and/or equipment involved in a particular operation. System drawings, including electrical drawings, will be used to determine steps required to perform actions of the flow charts. During this analysis, it must be continually emphasized to disregard existing instrumentation and concentrate on system components and their functions in listing tasks to be performed.

4.3 When the task listings are completed for the FRCs, each will be compared for consistency.

(Since the same systems are utilized to satisfy success criteria in several safety functions, this review will verify that tasks were consistent in operation of the same equipment.)

4.4 A form will be prepared to list information and control capability data.

Tasks and subtasks will be listed for the success path of a safety function. The desired action will be entered for each task or subtask and the characteristics of the information or control capability required entered on the form. These forms are then used to independently verify that the information and control capability requirements are met by control room instrumentation and exhibit the proper characteristics as well as meet appropriate human engineering guidelines.

4.5 The Function and Task Analysis Report is the output of the function and task enalysis to the Emergency Operating Procedures (EOPs) upgrade project for use as an additional source document in writing the E0Ps.

ado 386-00081-93-89

s Proc No 4.06 Attcchment 11 Revision 0 Page 5 of 5 FUNCTION AND TASK ANALYSIS 4.6 The bases sections of the Generic Emergency Procedure Guidelines in CEN 152 will be reviewed for Plant specific applicability and revised as necessary where Plant design differences make the general bases inappropriate. Justification shall be inserted based on available analysis, data, reports, or operating experience. These bases may be used by the E0P writer for guidance in developing EOPs.

In addition, the Training Department may consult these bases to clarify background of steps in the procedure when analyzing for skill and knowledge requirements.

Care must be exercised in revising these bases to preserve the overall approach and this ensures the accuracy and completeness of the task listings, information requirements, and control capability requirements in the analysis.

5.0 REVIEW REQUIREMENTS The Function and Task Analysis Report shall receive one level of technical review.

6.0 DOCUMENT CONTROL AND DISTRIBUTION The master copy of the approved function and task analysis report shall be sent to Document Control for filing with the master copies of the EOPs.

7.0 REVISION REQUIREMENTS The Function and Task Analysis Report shall be reviewed and revised if necessary whenever approved revisions to CEN-152 are issued, as required due to plant modifications, or if necessary following EOP verification / validation. Reviews and revisions shall be documented in the procedure working file for the appropriate EOP(s).

d I

ado 386-00081-93-89

$