ML20100F142

Rev 0 to Station Operating Procedure OS1300, Generation of Emergency Response Procedures

ML20100F142
Person / Time
Site:	Seabrook
Issue date:	02/23/1984
From:	Walsh L PUBLIC SERVICE CO. OF NEW HAMPSHIRE
To:
Shared Package
ML20100F115	List: ML20100F110 ML20100F142
References
OS1300, NUDOCS 8504040214
Download: ML20100F142 (39)

Text

,_ _

ATTACHMENT B STATION OPERATING PROCEDURE OS1300 REV00

" Generation of Emergency Procedures" 1

I f

8504040214 PDR 850329ADOCK 05000413 PDR p

P=gs I of I STATION CPERATING PROCEDURE COVER FORM i

i A. IDENTIFICATION NUMBER OS1300 REVISION 00 TITLE Ceneration of Emergency Response Procedures ORIGINATOR L. Walsh

3. INDEPENDENT REVIEW TITLE SIGNATURE DATE C. DEPARTMENT SUPVR./MGR APPROVAL i TITLE SIGNATURE DATE 4

D. QUALITY ASSURANCE REVIEW ("S" AND "X" PROCEDURES ONLY) f TITLE SIGNATURE . DATE f

1 E. SORC APPROVAL SORC MEETING MO.

i

! F. APPROVAL AND IMPLEMENTATION i

! STATION MANAGER APPROVED DATE EFFECTIVE DATE

' AQL.002A Rev. 00 i

02/23/84 I

TABLE OF CONTENTS, 1.0 OBJECTIVE

2.0 REFERENCES

3.0 SCOPE 4.0 DEFINITIONS AND ABBREVIATIONS 4.1 Terms and Definitiont 4.2 Abbreviations 5.0 RESPONSIBILITIES 5.1 Station Manager 5.2 Station Operation Review Committee 5.3 operations Manager 5.4 Operations Administrative Supervisor 6.0 INSTRUCTIONS 6.1 Emergency Response Procedure Designation & Numbering 6.1.1 Procedure Title 6.1.2 Procedure Numbering 6.1.3 Ravision Numbering 6.1.4 Page Numbering and Identification 6.2 Format 6.2.1 Procedure Organization 6.2.2 Page Formats 6.2.3 Instructional Step Numbering 6.3 Writing the Procedure 6.3.1 Cover Sheet 6.3.2 Operator Actions 6.3.3 Secpoint and Values 6.3.4 Operator Action Summary 6.4 Status Tree Format 6.5 Hechanics of Style 6.5.1 Spelling 6.5.2 Peuctuation-6.5.3 Capitalization 6.5.4 Vocabulary 6.5.5 Numerical Values i

6.5.6 Abbreviations and Acronyms 6.6 Ravisions and Canceliations 6.7 Printed Format 6.8 Reproduction

-t-

TABLE OF CONTENTS (cont.)

Table 1 - Emergency Response Procedure Index Table 2 - Action Verbs Figura 1 - Pre-Printed Page Format Figure 2 - Pre-Printed Page (2-Column) Format Figure 3 - Substep Numbering Example Figure 4 - Symptoms Example Figure 5 ' Entry Conditions Example Figure 6 - Use of Logic Terms Example Figuro 6a - Use of Multiple Logic Terms Example Figure 7 - Graph Example Figure 8 - Table Example Figure 9 - Attachment Example Figure 10 - Operator Action Summary Example Figure 11 - Status Tree Example Figure 12 - Status Tree Color Legend e-Emergency Response Procedure Change Form D

1.0 OBJECTIVE j

The objective or this document is to provide administrative and technical guidance on the preparation of Emergency Response Procedures (ERPs). This guide applies to Optimal Recovery Procedures, Function Restoration Procedures and Critical' Safety Function Status' Trees.

2.0 REFERENCES

2.1 Technical 2.2 Procedural i

3.0 SCOPE Emergency response procedures specify operator action to be taken during plant emergency situations to return the plant to a sate condition. Each procedure shall be uniquely identified to facilitate preparation, review, use and sub-i sequent revision.

4.0 DEFINITIONS AND ABBREVIATIONS 4.1 T_erms and Derinitions Approval Authorization - Unless otherwise specified an approval signature or authorizations designated to a staff position shall mean that individual or an authorized. designee.

Intent Change - Any change to a procedure which results.in alteration or

! the procedural method, scope, or acceptance criteria.

Non-Intent Change - Any change to a procedure which does not result in alteration of the procedural method scope, or acceptance criteria.

Special Proc *edure A procedure which may be used for an inf requently per-formed evolution and which shall not be included in the permanent list of station procedures.

Station Operating Procedure - Any procedures which are used to perform functions directly related to the operation, maintenance or surveillance or

. systems and equipment, and other technical functions performed by the operations and technical services groups. .

Unreviewed Safety Question - Any procedure, or change, which could (a) increase the probability of occurrence, or the consequences of an

[. accident or malfunction of equipment important to safety- as previously evaluated in the sarety-analysis report (b) create a possibility for an accident or malfunction of a different type than evaluated previously in the safety-analysis report, or (c) reduce the margin of safety as defined l

in the basis for any technical specifications.

l

, i i

p .-

'4.2 Abbreviations.

ac -

alternating current (electrical)

EFW =- emergency feedwater ASDV -

atmospheric steam dump valve ATWS - anticipated transient without scram BA - boric acid BAT - boric acid (storage) tank BIT -

boron injection tank BTRS :- boron thermal regeneration. system CCP- -

centrifugal charging pump CCW - component cooling water (preceded by an S or P)

CRDM - control rod drive mechanism CST -

condensate storage tank

'CVCS - chemical and volume control system CVCT - chemical volume control tank dc -

direct current (electrical power and signals)

DG -

diesel generator DWST - demineralized water storage tank EPS - emergency power sequencer ECCS. - emergency core cooling system HP -

high pressure HX -

heat exchanger LOCAL - loss of coolant accident LOP - loss of power LP -

low pressure MCC -

motor control center MD -

motor driven (in reference to pumps)

MSIV -

main steamline isolation valve NIS -

nuclear instrumentation system NRI -

narrow range (level indication)

PORY -

power operated relief valve (pressurizer only)

PDP -

positive displacement pump PRT - pressurizer relief tank PRZR -

pressurizer RAT. - reserve auxiliary transformer RCP. -

reactor coolant pump RCS - reactor coolant system RHR -

residual heat removal RMO -

remote manual operation (relay designation)

RPV -

reactor pressure vessel RWST - refueling water storage tank RVLIS - reactor vessel liquid inventory system SI -

safety injection SG -

steam generator SGTR - steam generator tube rupture SUR -

startup rate SW -

service water TA -

tower actuation TC -

thermocouple TD -

turbine driven (in reference to pumps)

TSC -

technical support center UAT -

unit auxiliary transformer WPB -

waste processing building WR -

wide range

r-5.0 RESPONSIBILITIES 5.1 Station Manager The station manager is responsible for. approving station operating proce-dures and special procedures to include changes and revisions.

5.2 Station Operation Review Committee (SORC,),

The'SORC is responsible for reviewing emergency response procedures and recommending approval / disapproval to the station manager.

5. 3. Operations Manager The operations manager is responsible for ensuring that the emergency response procedures, changes and revisions are prepared, reviewed and main-tained as outlined in this procedure.

5.4 Operations Administrative Supervisor The Operations Administrative Supervisor shall act in behait of the opera-tions manager in the preparation of the emergency response procedures prior to SORC approval and shall torward all procedures to the Document Control Center for proper distribution af ter SORC approval.

6.0 INSTRUCTION 6.1 Emergency Response Procedure Designation and Numbering The ERPs provide the basis for piant-specific emergency operating proce-dures (EOPs) which specify operator actions to be taken during plant emergency situations to return the plant to a safe stable condition. Each procedure shall be uniquely identified to f acilitate preparation, review, use and subsequent revisi 9n.

6.1.1 Procedure Title Every separate procedure shall have its own descriptive name which summarizes the scope of that procedure, or states the event (s) which it is intended to mitigate.

6.1.2 Procedure Numbering Each separate procedure shall have its own alpna-numeric designation to supplement the descriptive title. Letter designators are to be assigned according to the, definitions provided in Table L.

Emergency Response Procedures shall be designated by the letters E, ES or ECA plus a number designator. Number designators are assigned sequentially Bach E procedure number designator snail consist of a single integer. Each ES procedure shall consist or the number designator of the reference E procedure, plus a decimal integer, again assigned sequentially.

D 1

ECA procedures shall=each have a number designator consisting of an integer plus a decimal integer. Related procedures shall be assigned sequential decimal integers.

Letter and number designators shall be separated by a hyphen.

Examples: E-0 ES-0.1 ES-1.2 ES-1.3 ECA-0.0 ECA-1.1 ECA-2.1 Critical Safety Function Status Trees shall be designated by the letter F plus a number designator. Number designators shall consist l+ of the number zero plus a decimal integer which shall be assigned sequentially.

Letter and number designators shall be separated by a hyphen.

Example: F-0.1 F-0.2 Function Restoration Procedures shall be designated by the letters FR plus an additional letter which corresponds to the respective Critical Safety Function. All the separate procedures related to a particular Critical Safety Function are assigned decimal integers in increasing order.

' The procedure letter and decimal integers are separated from the FR designator by a hyphen.

Examples FR-S.1 F R-S . 2 6.1.3 Revision Numbering Every separate procedure shall have an assigned "Rev. Issue" designa-tor to identify its time of origin. The number following the "Rev."

abbreviation designates a republication of the entire ERP set following the BASIC publication. An additional " Issue" letter will designate an individual procedure modified after the "Rev." publica-tion. Absence of an " Issue" letter denotes that the procedure was part or the latest "Rev." publication and has not been changed.

Examples: Re v. 1 First republication ot the entire ERP set. Each procedure has the same designator.

Rev. lA First moditication to a Rev. 1 procedure.

Rev. 3C Third modification to a Rev. 3 procedure.

I

Any new procedure (s) added to the ERP set will be assigned tne latest "Rev." number and njl " Issue" letter. This will indicate that the vin-tage is consistent with the latest publication or the entire ERP set.

Each procedure "Rev. Issue" number will be accompanied by a date (Day, Month, Year) printed immediately below it.

6.1.4 Page Numbering and Identification Each page of a procedure will be identified by the procedure title, alpha-numeric designator, "Rev. Issue" designator, and date in a title block at the top of the page. Each page number will be specified as

"__ of __", centered on the bottom or the page. The last page or instructions will have the word "END" following the last instruction step.

6.2 Format The following format is to be applied consistently to all Emergency Response Procedures:

6.2.1 Procedure Organization All Optimal Recovery Procedures (ORPs) will have three (3) sections.

The Cover Sheet will summarize procedure intent and state either entry symptoms or means of entry. The Operator Actions will comprise tne

bulk of each procedure and present ene actual stepwise guidance. The Operator Action Summary appears on the back side of each page as applicable and provides information which could direct further opera-tor action at any point in the procedure.

6.2.2 Page Formats All pages of the Emergency Response Procedures (ERPs) will use the same page structure. This page structure employs a pre printed border to ensure all margins are correctly maintained, and pre printed designator boxes and page cues to assure completeness and consistency.

(See Figure 1).

The pages tor presentation of operator action steps will use a two-column format within the pre printed border. The left-hand column is designated tor operator action, and the right-hand column is designated for contingency actions when the expected response is not obtained. These pages will use pre-printed title blocks above the separate columns (including the " step" column) for uniformity (See Figure 2).

6.2.3 Instructional Step Numbering Procedura1 ' steps will be numbered as follows

1. High-level step

a. Substep

1) Detailed instructions (if necessary)

Substeps are lettered sequentially according to expected order of per-formance. If the order of substep performance is not important, the substeps are designated by bullets (e). If the logical Ojt is used, both choices may be designated by bullets. This same numbering senene is to be used in both the right and lef t columns or the guidelines.

(See Figure 3).

6.2.3.2 Immediate Action Steps For those procedures which can be entered directly based on symptoms, certain initial steps may be designated "immediate actions". This designation implies that those steps may be

- performed by the operator, based on his memory without reference to the written procedure. These steps should be limited to verifications, if possible. Immediate action steps are identified by a NOTE (see Section 4.2.4) prior to the first action step.

Examples NOTE: Steps 1 through 14 are IMMEDIATE ACTION steps.

6.2.3.3 Continuous Steps Many of the operator actions provided in a procedure imply con-tinuous performance throughout the remainder or the procedure.

This intent is best conveyed by the use of appropriate action verbs such as monitor, maintain or control.

6.3 Writing the Procedure The following toraat is to be applied consistently when writing Emergency Response Procedures (ERPs):

6.3.1 Cover Sheet Each cover sheet will contain two expianatory sections in addition to procedure and page designators. The first will be citied "PURPOSB" and will briefly describe what the procedure is intended to do for the o perator. The second section is a summary or those conditions wnien require entry into the procedure. This section will be titled

" SYMPTOMS OR ENTRY CONDITIONS". Certain procedures such as E-0 and ECA-0.0 can be entered purely based on symptoms, for these procedures, a symptom summary is sutficient (see Figure 4). For other procedures

. which can only be entered by transition from previous procedures, a summary of the entry conditions (and procedure / step) should be pro-vided. (See Figure 5).

6.3.2 ' Operator Actions

' Steps directing operator action should. be written in short and precise language. The statement snould present exactly the task which the operator is to perform. The equipment to be operated should ,tw speci-fically identified, and only those plant parameters should be spe-cified which are presented by instrumentation available in the control room. (If possible, use of qualified instruments is desired.) It is not necessary to state expected results or routine tasks or specity instrument usage if qualified instruments are already identified in the main control room.

All steps are assumed to be performed in sequence unless stated other-wise in a preceding NOTE (see Section 4.2.4). To keep the individual steps limited to a single action, or a small number of related actions, any complex evolution should be broken down into composite parts.

Actions required in a particular step should not be expected to be complete before the next step is begun. If assigned tasks are short, then the expected action will probably be completed prior to con-tinuing. Howgver, if an assigned task is very lengthy, additional steps may be pertormed prior to completion. If a particular task must be completed prior to continuation, this condition must be stated clearly in that step or substep.

Refer to Figure 6 as an example or the format for presenting operator actions in the following sections.-

6.3 2.1 Instruction Steps, Lett-Hand Column The lef t-hand column of the two-column format will be used for operator instruction steps and expected responses. The following rules or construction apply.

e Righ Level Action steps should begin with an appropriate verb, or verb with modifier.

e Expected' responses to operator actions are shown in ALL CAPITAL LETTERS.

• If a step requires multiple substeps, then each substep will have its own expected response if applicable.

e If only a single task is required by the step, the high level step contains its own EXPECTED RdSPONSE.

s e Left-hand column tasks should be specified in sequence as it they could be perrormed in that manner. The user would nor-mally move down that left-hand column when the expected response to a particular step is obtained.

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

expected to move to the right-hand column for' contingency instructions.

e All procedures should end with a transition to either another procedure or to some normal plant procedure.

6.3.2.2 Instruction Steps, Right-Hand Column The right-hand column is used to present contingency actions which are to be taken in the event that a stated condition, event, or task in the left-hand column does not represent or achieve the expected result. Contingency actions will be spe-cified for steps or substeps for wnich useful alternatives are available. The following rules apply to the right-hand column.

e Contingency actions should identify directions to override automatic controls and to initiate manually wnat is normally initiated automatically.

• Contingency actions should be numbered consistently with the expected response / action for substeps only. A contingency for a single-task high-level step will not be separately-numbered but wt11 appear on the same line as its related step.

• If the right-hand column contains multiple contingency actions for a single high-level action in the lett-hand column, the phrase " Perform the following " should be used as the introductory high-level statement.

e The user is expected to proceed to the next numbered step or substep in the left-hand column after taking contingency action in the right-hand column.

• As a general rule, all contingent transitions to other pro-cedures take place out at the right-hand column.

(Pre-planned transitions may be made f rom the lef t-hand column.)

e If a contingency action cannot be completed, the user is expected to proceed to the next step or substep in the left-hand column unless specifically instructed otherwise. When writing the procedure, this rule or usagu should be con-sidered in wording subsequent lert-hand column instructions.

e If a contingency action must be completed prior to con-tinuing, that instruction must appear explicitly in the right-hand column substep.

6.3.2.3 Use of Logic Terms The logic terms AND, Oil, NOT, IF NOT, WHEN, can NOT, and TdEN, are to be used to describe precisely a set or conditions or a sequence of actions. Logic terms will be highlighted for emphasis by capitalizing and underlining. (See Figure 6.)

The two-column format equates to the following logic: "IF NOT the expected response in the left-hand column, THEN perrorm the contingency action in the right-hand column." The logic terms should not be repeated in the right-hand column contingency.

However, the logic terms may be used to introduce a secondary contingency in the right-hand column.

When action steps are contingent upon certain conditions, the step shall begin with the words I][ or WHEN followed by a description of those conditions, a comma, the word THEN, and the action to be taken.

))[ is used for an unexpected, but possible condition.

WHEN is used for an expected condition.

AND calls attention to combinations of conditions and shall be placed between each condition. If more than two conditions are to be combined, a list format is preferred.

OR implies alternative combinations or conditions. ~~~OR means eTther one, or the other, or both (inclusive).

IF...NOT or IF,...can NOT should be used wnen an operator must respond to the second or two possible conditions. J][should always be used to specify the first condition. (The-right-hand column or the two-column tormat contains an implicit IF NOT.)~

- When the logic terms AND, Oj! are used two or more times in a substep, they shall De highlighted. Example Figure 6. If in addition to two ors there should be an AND, then the and state-

, ment should be highlighted separately. Example Figure 6a.

! 6.3.2.4 Notes and Cautions Because the present action-step wording is reduced to the mini-i aus essential, certain additional intormation is sometimes

, desired, or necessary, and cannot be merely included in a I

background document. This non-action information is presented as either a NOTE or a CAUTION. (See Figure 6.)

i

L

To distinguish this information trom action steps, it will extend across the entire page and will immediately precede the step to which it applies. Each category (NOTE or CAUTION)- will be preceded by its descriptor in larde, bold, letters.

Multiple statements included under a single heading shall be separately identified by noting them with bullets (e).

CAUTION denotes some potential hazard to personnel or equipment associated with the following instructional step. A CAUTION may also be used to provide contingent transition based on unfavorable changes in plant conditions. NOTE is used to pre-sent advisory or administrative information necessary to sup-port the following action instruction.

As a general rule, neither a CAUTION or NOTE will contain an instruction / operator action step; however, reference may be made to expected actions in progress.

6.3.2.5 Transitions to Other Procedures or Steps Certain conditions require the use of a ditterent procedures or step sequence. Transitions are specified by using the words "go to" followed by the procedure designator, title (in CAPITAL

~

LETTERS) and step number.

Transitions shall NOT contain a " return" feature (i.e. , pertorm steps X through Y in some'other procedure and then return).

Example: Go to ES-0.1, REACTOR TRIP RESPONSE, Step 1.

Transitions to a different step later in the same procedure are specified in a similar manner.

Example: Go to Step 20.

Transitions to an earlier step in a procedure are specified by using the words " return to".

Example: Return to Step 2.

Transitions to a step which is preceded by a CAUTION or NOTE shnll include special wording to assure that the CAUTION or NOTE is observed.

Example. If conditions are NOT satistied, THEN go to Step 22.

OBSERVE CAUTION PRIOR TO STEP 22.

~

6.3.2.6 Component Identification Equipment, controls and displays will be identified in

" operator language" terms. Standard abbreviations which may be used throughout the guidelines are listed alphabetically in Table 2. Since similar components are used in both primary and secondary systems, it is always necessary to clarify the loca-tion, even if the wording appears redundant.

Example: PCCW vs. SCCW identifies primary component cooling water as distinct from the secondary component cooling water.

6.3.2.7 Level of Detail To allow an operator to efficiently execute the action steps in a procedure, all unnecessary detail must be removed. Any information whien an operator is expected to know (based on his training and experience) should not be included. Many actuation devices (switches) in the control room are similar, even though the remotely performed functions are not, so cer-tain action verbs listed here are recommended.

o Use " start /stop" for power-driven rotating equipment e Use "open/close/ throttle" for valves, e Use " control" to describe a manually maintained process variable (flow level, temperature, pressure).

• Use " trip /close" for electrical breakers. (PULL-TO-LOCK for breaker switches with a pull-to-lock feature).

e Use " place in standby" to refer to equipment when actuation is to be controlled by automatic logic circuitry.

6.3.2.8 Figures If needed to clarity operator action instructions, figures shall be added to a procedure. Any figure used will be constructed to rit within the pre-printed page format (see Figure 1). Certain rules of construction will apply, e All wording on the figure shall be at least as legible (type size and spacing) as the instruction steps in the guide-lines.

e Each figure will occupy a complete page and will be uniquely identified by a figure number and title. The figure number will consist of the procedure designator, without punc-

, tuation, followed by a hyphen and an integer.

Example: Figure E-3-1

[

e Figure titles will explain the intent or content of the figure.

e The figure number and title will be placed at the top of the page just inside the printed border.

• If the figure is a graph, all the numbers and wording will be horizontal if possible. By convention, the independent variable is plotted on the horizontal (X) axis. Grid line density should be consistent with the resolution expected from the graph. Any labeling required on the graph will have a white (not graph) background. (Figure 7 is an example figure showing presentation of a graph.)

e All figures for a procedure are numbered sequentially and appear at the end of the procedure. Figure pages are num-bered as pages of that procedure. Any figures required for an ATTACHMENT are numbered in sequence with the procedure figures but have page numbers corresponding to placement in the attachment.

6.3.2.9 Taoles Tables may be used within the text or a procedure to clearly present a large number of separate options. A table will imme-diately follow the step or substep which makes use of it.

Therefore, it does not require a unique number and title. Any table will be completely enclosed by a distinct outline, if necessary it may extend into the adjacent column because of this delineation.

All information presented in a table shall be at least as legible (type size and spacing) as the instruction steps in the guideline.

All-columns and rows of information in a table will be defined by solid lines.

All column and row headings shall be presented in upper case type.

Absence of a table element will be indicated by a dash.

(Figure 8 presents a typical table).

6.3.2.10 Attachments Supplementary information or detailed instructions whien would unnecessarily complicate the flow of a procedure may be placed in an attachment to that procedure.

+. ,- m p - . - , - - -

Attachments are' identified by the title " ATTACHMENT" followed by a single letter designator *This title is centered at the top of a standard format page. The pre-printed title blocks will be the same as for the procedure.

Physically, ATTACHMENTS will be located after any Figures belonging to procedure. Attachments will use a single-column, full-page-width format. Figure 9 is an example ATTACHMENT page.

6.3.3 Setpoint and Value Studg The "SETPOINT AND VALUE STUDY" is a listing or the setpoints and values used in the ERPs and are plant specific to Seabrook Station.

This document provides all applicable setpoints, values, curves and other parameters needed for the ERPs.

The "SETPOINT AND VALUE STUDY" also includes references, assumptions and actual calculations used to derive setpoints and values and will be' maintained as a plant controlled safety related document for the life of the plant. This document is updated as necess'ary with appropriate changes made to ERPs.

6.3.4 Operator Action Summary The operator action summary appears. on the back of applicable proce-dure pages and is titled "0PERATOR ACTION

SUMMARY

FOR E-X SERIES PROCEDURES". It will use a plain page format for distinction.

Each set of operator informa' tion will be numbered sequentially and have an explanatory title. The title will be capitalized and underlined for emphasis. This page contains those important actions which can be performed at any step in the procedures. (Refer to Figure 10.)

6.4 Status Tree Format Critical' Safety Function Status Trees are presented.in the " block" version-and all trees in the set use the same format. Similarly the trees may be oriented either vertically or horizontally on a page, so long as the orien-tation is consistent over the set. (Refer to Figure 11.)

i Color-coding and/or line-pattern coding shall be used from each last branch point to its terminus.

All text on the Status Tr,ees shall be at least as legible (type size and spacing) as the instruction steps in the procedures. Refer to Figure 12 for the color usage legend.

Each status tree shall have at the top of the page, a designator block identical to that used in the standard procedure format and containing the same information.

s

Statements shall be worded so that the favorable response is downward.

Termini shall be ordered so that REDS are uniformly at the top and GREENS at the bottom. Termini order should be RED - ORANGE - YELLOW - GREEN ir possible.

CRT presentation of status trees should conform to this tormat for consistency..

6.5 Mechanics of Style 6.5.1 Spelling All spelling should be consistent with modern usage as specified in the Oxford Di ctionary of the English Language, unabridged version.

6.5.2 Punctuation Punctuation should be used only as necessary to aid reading and pre-vent misunderstanding. Word order should be selected to require a minimum of punctuation. The following rules apply:

e Use a colon to indicate that a list or items is to follow.

Example. Stop the following equipment e Use a comma after conditional phrases for ease of reading.

Example. Ij[ level exceeds 50%, THEN . ..

• Use parenthesis to indicate alternative items in a guideline.

• Use a period to indicate the end of complete sentences and for indicating the decimal place in numbers.

• Use a dash to separate a required action and its expected response and also to indicate a null table element.

Example: Verify SI Pump - RUNNING.

6.5.3 capitalization Capitalization shall be used in the procedures for emphasis in the following cases.

• Logic terms will be capitalized and underlined.

• Expected responses (left-hand column of instructions) are capita-lized.

• Titles of procedures will be completely capitalized whenever referenced within any guideline.

e Operator action steps may be capitalized FOR EMPdASIS.

• Abbreviations (TABLE 2) are commonly capitalized.

e Section headings on operator action summary pages are capitalized

, and underlined.

6.5.4 Vocabulary Words used in the procedures should convey precise meaning to the trained operator. Simple words having few syllables are prererred.

Thes'e are typical of words in common usage.

Verbs with specific meaning should be used. The verb.should exactly define the task expected to be performed by the operator. A list of frequently used verbs is included as Table 2.

Some words have unique meanings as listed below.

manual (manually) - an action perrormed by the operator ijl the control room. (The word is used in contrast to an automatic action, which takes place without operator intervention.)

local (locally) - an action performed by an operator outside the control room.

Example: " Locally close valve" means directly turning a handwheel to close a valve.

Inequalities are to be expressed in words rather than symbols. i.e.,

" greater than, less than". These words are always appropriate for comparing pressures, temperatures, levels and flowrates.

6.5.5 Numerical Values All numerical values presented in the procedures should be consistent with what can be read on instruments in the control room (i.e., con-sistent with instrument scale and range).

The number of significant digits presented should be equal to the reading precision of the operator.

Acceptance values should be stated in such a way that any addition and subtraction operations are avoided, if possible. This is done by stating acceptance values as limits. Examples. 2500 psig maximum, 350*F minimum, between 450*F,and 500*F. Tolerances can be expressed by stating the normal value followed by tne acceptable _ range in parenthesis.

Example: 550*F (540*F to 560*F)

Avoid: 550*F + 10*F if possible

Engineering units should aiways-be specified when presencing numerical values for process parameters. They should be the same as those used on the control room displays.

6.5.6 Abbreviations and Acronyms Abbreviations and acronyms should be limited to those commonly used by operators. Table 2'11sts the most common ones necessary for these procedures._ Abbreviations and acronyms should,be used whenever possible=to simplify the procedures.

. Abbreviations and acronyms from table 2 will be uniformly capitalized whenever they are used.

6.6 Revision and Cancellations 6.6.1 Non-intent changes, such as word changes for clarity or addi-

~

tion notes or cautions, may be made by any two senior licensed opera-tors. These changes will be reviewed by the operations manager and incorporated into the body of the procedure at its next full revision or if there are sufficient non-intent changes to warrant a revision rewrite, f

6.6.2 ;All non-intent changes will be forwarded to SORC for approval within 14 days of implementation.

6.6.3 -Cancellation and intent changes will be treated alike. All intent changes will be reviewed by the operations manager and SORC prior to approval. In addition, intent changes to these procedures will need a WOG review to ensure that the procedure set integrity has not been altered.. .(Presently there is a WOG feedback system started.

To date no revisions have been-issued; if and when this mechanism for procedure change has been finalized, an ammendment to this procedure will follow.)

6.7 Printed Format

[- The final printed format of the procedures will be clear and legible.

Final approved versions may be commercially printed at the option of sta-l tion management. 3 I

l 6.8 Reproduction i

(~ Procedure reproduction will be done on a standard copier, without signifi-cant loss of legibility. Uncontrolled copies shall be marked "FOR INFORMATION ONLY" or " UNTESTED" for those procedures which have not been validated and verified on the plant simulator or in actual practice.

l l

i 16 -

i i

, .. - - - . - . - , .-. - - - - - . . . ~ , - . - -

TABLE I DEFINITIONS OF LETTER DESIGNATORS FOR ERPs E - a procedure for diagnosis and recovery from design basis events ES - a procedure'which supplements the recovery actions of an E procedure ECA - a procedure which supplements both the E and ES procedures by providing recovery actions for low probability or unique event sequences which are not easily covered in the E or ES procedures or which may complicate or reduce the effectiveness of these procedures F - a procedure for diagnosis of challenges to a Critical Safety Function -

represented in tree format FR - a procedure for-restoration of a Critical Safety Function (CSF) to a

' satisfied condition S- - designator for SUBCRITICALITY CSF C - designator for CORE COOLING CSF H designator for HEAT SINK CSF P - designator for INTEGRITY CSF Z - designator for CONTAINMENT CSF I - designator for INVENTORY CSF 1

TABLE 2 .

- stAsseya STAftes -

ResRG8MCY assPONSE reoCroomt tuotx raccacets TITt,E matast.

Reactor Trip or safety 1 ejection 3-0

- 35-0.0, todtagnosto Someter Trip gespeese ES-0.1 Wateral Circulettee Coeldown ES-0.2 Watural Ctreelettee Cooldown With Steen Void in Vessel SS-0.3 (With tvLIS) ES-0.4 Hetural Circulation Cooldova with Steam void to Vessel (Without Ret 15) . . . -

Imes of Reactor or Secondary Coolant E-l St Termination ES-I.I Fest-Loca Coeldeve med Depresserisation ES-1 2 Tremeter to Cold 143 Recirculattoe ES-1 3 Transfer to Sot tag tactreulation ES-l.4 Faulted Steen Generator teoistion E-2 Steam Generator Tube Rupture E-3 Foot-SCTR Cooldown Usteg Beckf111 ES-3.1 Post-SCTE Cooldown Using 510wdown ES-3.2 Post-SCTE Cooldown Uetea scene Duen ES-3.3 loss of All AC Power ECA-0.0 laes of All AC Power Recovery Without $1 Required ECA-0.1 less of All AC Fower Recovery With S1 Required ECA-0.2 i

~

Imes of Emergency Coolant Recirculation FCA-l.1 LOCA Outside Contatament ECA-l.2 1

Uncontrolled Depressurisetton of All Steam Ceneratore ECA-2.1 SCTR with 1mse of Reactor Coolant - Subcooled Recovery ECA-3.1 Doetred SGTR With less of teactor Coolant - Saturated Recovery ECA-3.2 Desired ECA-3.3 i

SCTR Without Pressortsee Preceu o Control Suberiticality (Critical Safety Function Status Tree) F-0.1 Core Cooling (Critical Safety Function Status Tree) F-0.2 Heat Sink (Critical Safety Function Status Tree) ' F-0.3 Integrity (Critical Safety Function Status Tree) F-0.4 Contalement (Critical Safety Function Status Tree) F-0.5 Inventory (Critical Safety runetton Status Tree) F-0.6 Response to Buclear Power Generetton/ATVS FR-S.!

Response to Loes of Core Shutdown FR-S.2 seaponse to inadeqeate Core Cooltog FR-C.I geoponse to Degraded Core Cooling FR-C.2 j

Response to Saturated Core Cooling Condition FR-C.3 FR-M.1 Response to Ices of Secondary uset Sink FR-N.2 Response to Stees Generator Overpressure FR-il. 3 Seeponse to Stese Generator High Level FR-H.4 Response to imes of Stese Dump Capabilities FR-M.5 heeponse to Steen Generator tow tavel Response to temineet Presourised therest Shock FR-F.I

. Conditione FA-P.2

' Response to Anticipated Pressurised Thereal Shock Conditione iteoponse to High Containment Pressure FR-Z.t Response to Containeemt Flooding FR-Z.2 Response to Mlah Containment Radietton__tavel FR-Z.1_ _

posposee to High Presourtser Level FA-1.1 Response to Low Presourtser Level FR-1.2 Aoyonee to Volde in Reactor vessel FR- t .1_ ,

f

-ts-L

TABLE 3 ACTION VERBS Actuate To put into action or motion, commonly used to refer to automated, multi-faceted operations.

Examples: Actuate S.I., Actuate Phase A, Actuate Containment Spray Align To arrange components into a desired configuration.

Examples. Align tne system for normai charging. Align valves as appropriate.

Block To inhibit an automatic actuation.

Example. Block SI actuation.

Check To note a condition and compare with some guideline requirement.

Example: Check PRZR level - GREATER THAN 20%.

Close To change the physical position of a mechanical device. Closing a valve pre-vents fluid flow. Closing a breaker allows electrical current tiow.

Complete To accomplish specified procedure requirements.

l Continue To go on with a particular process.

(

Example

Continue with this procedure.

i l Control To manually operate equipment as necessary to satisry procedure require-l ments on process parameters pressure, temperature, level, flow.

l Example: Control pressurizer level.

t Determine To calculate or evaluate using formula or graphs.

I l- Example. Determine maximum venting

! time.

l ACTION-VERBS (CONTINUED) 4 Energize' To supply electrical energy to _

(something). Commonly used to describe an electrical bus or other dedicated.

electrical path.

Examples: Energize AC emergency buses.

Energize PRZR heaters.

Enter -To insert into or add to.

?

' Establish To make arrangements for a stated con-dition.

Example: Establish normal pressurizer pressure and level control.

Evaluate To examine and decide; commonly used in reference to plant conditions and opera-tions.

t Example: Evaluate plant conditions.

Initiate To begin a process.

Example: Initiate' flow to all SGs.

Load To connect an electrical component or unit to a source of electricai energy.

May involve a " start" in certain cases.

J Example: Load'the following equipment on AC equipment buses:

Maintain To control a given piant parameter to some procedure requirement continuously..

Example: Maintain SG level in the narrow range.

Monitor Similar to " check", except implies a con-tinuous function.

Open To change the physical-position of a mechanical device to the unobstructed position. Opening a valve permits fluid flow. Opening an electrical breaker pre-vents current flow.

Place-in-standby To return a piece or equipment to an inactive status but ready for start on demand; commonly.used to refer to a mid-position on a switch labeled "AUT0".

I-Example: Stop the pumps and place in standby.

ACTION VERBS (CONTINUED)

Reset To remove an active output sidnal from a retentive logical device even with the input signal still present, commonly used in reference to protection / safeguards logics in which.the actuating signal is

" locked-in". The RESET allows equipment i

energized by the initial signal to be de-energized.

Examples: Reset SI, Reset Phase A.

s Record To document specified characteristics.

Exampie. Record RCS average temperature.

Sample To take a representative portion ror the purpose of examination, commonly used to refer to chemical or radiological exami-nation.

Examples: Sample for RCS boron concen-

, tration. Samples for side activity.

Start To originate motion of an electrical or mechanical device, either directly or by remote control.

Example: start one RCP.

Stop To terminate motion of an electrical or mechanical device.

Example: Stop both diesels.

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

. Examples Throttle flow control valve to establish desired flow.

i Trip To manually activate a semi-automatic l feature. Commonly, " trip" is used to L reter to component de-activation.

i.

l Examples: Trip the reactor, trip the l' turbine. Trip a breaker.

l Verify To observe that expected characteristic l or condition exists. Typically the

[- expectation comes from some previous automatic or operator action.

l Examples: Verify Reactor Trip, Verify SI l Pumps - RUNNING.

l.

r i

I i

w ,--,-.

Coda. - Symptco/ Title '

Procsdura No.

Revision - No. / Data .

'q Y

w t

- . . . .e_ _.

e. _ - .e r

- . .-.--e-. . - .

Q r

L

+ -

.__e -

FIGURE 1 Pre-Printed Page Format b

e. e e- - ea f

l' l~

1 i

E II l

i v f

I f

a r

e

__ *ee w ee w *e eeeeeme -- m.e e e e + a.pm .= we wi a

p Efe

t. ...

Cods. :Symptos/ Title. Procedure No.

Revision No./Date.

l STEP l l ACTION / EXPECTED RESPONSE l l RESPONSE NOT OBTAINED l _ __

FIGURE 2 Pre-Printed Page (2-Column) Format Cods. .Symptcc/Titis. Procsdure No.

Revision No./ Data.

.E 3' STEAM GENERATOR TUBE RUPTURE E-3 Re v. 1 .(EXAMPLE ONLY) Rev. 1 / 01/12/84 l STEP l l ACTION / EXPECTED RESPONSE l RESPONSE NOT OBT_AINED A l ,,___

l FIGURE]

17 Depressurize RCS To Minimize Break'Fiow And Refill PRZR:

a. Normal PRZR spray - AVAILABLE a Go ro Step 18. OBSERVE CAUTION PRIOR'TO STEP.18.

b. Spray PRZR with maximum available spray until ANY of the following conditions satisfied e BOTH of the f2 1owing

1) RCS pressure - LESS THAN RUPTURED SG PRESSURE

2) PRZR level - GREATER THAN 5% [30% FOR ADVERSE

_ CONTAINME_NT]

- OR --

l

• PRZR level - GREATER THAN 80% l

- OR -

e RCS subcooling based on core

exit TCs - LESS THAN 30*F

c. Close spray valve (s) l 1) Normal spray valves 1) Stop RCP(s) supplying l failed spray valve.

o RC-PCV-455A RCP-1C i e RC-PCV-455B RCP-1A

d. .Go to Step 20. OBSERVE l CAUTION PRIOR TO STEP 20 l ._ . - - . .-- -.

l l

l

( . --

C:dm Sympto2/

Title:

Procedure No.

Revision No./Date E-0 REACTOR TRIP OR SAFETY INJECTION E-0 Re v. l' (EXAMPLE ONLY) Rev. 1 / 10/26/83-l FIGURE 4 l A. PURPOSE-This procedure provides actions to verify proper response of the automatic protection systems following manual or automatic actuation of a reactor trip or safety injection, to assess plant conditions, and to identify the appropriate recovery procedure, i

B. SYMPTOMS OR ENTRY CONDITIONS

1. Any symptom that requires a manuai reactor trip listed in ATTACHMENT A, if one has not occurred.

2. The following are symptoms of a reactor trip,

a. Any reactor trip annunciator lit.

b. Rapid decrease in neutron level indicated by nuciear instrumentation.

c. All shutdown and control rods are fully inserted. Rod bottom lights are lit.

3. Any symptom that requires a manual reactor trip and sarety injection listed in ATTACHMENT B, if one has not occurred.

4. The following are symptoms of a reactor trip and safety injection.

a. Any SI annunciator or status lamp lit.

b. ECCS pumps in service.

mM M - - - _

4

r-me> w -

Coda: Sympter/Titis: Proc 3 dura No.

Revision No./Dato:

FR-H.4 RESPONSE TO LOSS OF NORMAL STEAM DUMP FR-H.4

'Rev. 1 CAPABILITIES (EXAMPLE ONLY) Rev. 1 / 10/11/83 l FIGURE 5 l A. P_URPOSE This procedure provides actions to respond to a failure or the steam generator atmospheric steam dump valves (ASDVs) and con-denser steam dump valves.

B. S SYMPTOMS OR ENTRY CONDITION _S This procedure is entered from F-0.3, HEAT SINK Critical Safety Function Status Tree on a YELLOW condition.

NN N- e _-- ;e --e me e mn c.

~

C:da Syrptor/Titie. Procedure No.

Revis' ion " No. / Date .

E-0 REACTOR TRIP OR SAFETY INJECTION E-0 Rev. 1 (EXAMPLE ONLY) Rev. 1 / 10/26/83 l STEP l l ACTION / EXPECTED RESPONSE l l RESPONSE NOT OBTAINED) l FIGURE 6 l 25 Check If ECCS Flow Should Be Reduced

a. RCS subcooling based on a. DO NOT STOP ECCS PUMPS. Go '

core exit TCs - GREATER' to Step 27.

THAN 30*F

b. Secondary heat sink. b. F IF,neither condition satis-fled, T_ HEN DO NOT STOP CENTRIFUGAL CHARGING PUMPS e Total EFW flow to intact OR SI PUMPS. Go to Step 27.

SGs - GREATER THAN 470 GPM TOTAL CnMBINED FLOW CAPA-BILITY. ,

- OR -

e WR level in at least one intact SG - GREATER THAN 65%

c. RCS pressure - STABLE OR c. DO NOT STOP ECCS PUMPS. Go INCREASING to Step 27.

d. PRZR level - GREATER THAN d. DO NOT STOP ECCS PUMPS. Try 5% to stabilize RCS pressure with normal spray. Return to Step 25a.

26 Go To ES-1.1, SI TERMINATION, l~ Step 1 '

27 Initiate Monitoring of Critical Safety Function Status Trees l

CAUTION CST makeup should commence as early as possible to

avoid low inventory problems.

r I

' l L

Codt s Symptom /Titl@. Procedure No.

Revision No./D2ts:

E-3 STEAM GENR.RATOR TUBE RUPTURE E-3 Rev. 1 Rev.1 / 09/24/84 l STEP l l ACTION / EXPECTED RESPONSE l l RESPONSE NOT OBTAINED l _

l FIGURE 6a l

'17 Depresaurize.RCS To Minimize Break Flow And Refill PRZR.

a' . Normal PRZR spray AVAILABLE a. Go to Step 18. OBSERVd CAUTION PRIOR TO STEP 18.

b. Spray PRZR with maximum available spray until ANY of the following conditions satistied:

~

BOTH of the following

1) RCS pressure - LESS THAN RUPTURED SG PRESSURE

2) PRZR level - GREATER THAN 5% [50% FOR AD-VERSE CONTAINMENT]

- OR _

PRZR Level - GREATER THAN 80%

- OR -

RCS subcooling based on core exit TCs - LESS THAN 30*F

c. Close spray valve (s):

1) Normal spray valves 1) Stop RCP(s) suppiying ratied spray valve.

• RC-PCV-455A RCP-1C e RC-PCV-455B RCP-1A

2) Auxiliary spray valve 2) Isolate auxiliary spray line.

d. Go to Step 20. OBSERVE CAUTION PRIOR TO STEP 20

~

C:das Symptor/ Title. Procndure No.

devision No./D.te.

FR-H.1 RESPONSE TO LOSS OF SECONDARY HEAT SINK FR-H.1 (EXAMPLE ONLY) Rev. 1 / 01/12/84 l STEP l l ACTION / EXPECTED RESPONSE l l RESPONSE NOT OBTAINED l l FIGURE 7 l FIGURE FR-H.1-1 REQUIRED ECCS FLOW IOC CORE BLEED AND FEED COOLING l

l l

l l

p Cods. Sympter/Titis: Procedura No.

Revision No./Dato:

FR-H.1 RESPONSE TO LOSS OF SECONDARY HEAT SINK FR-H.1 Rev. 1 (EXAMPLE ONLY) Rev. 1 / 11/03/83 l STEP l l ACTION / EXPECTED RESPONSE l l RESPONSE NOT OBTAINED l l FIGURE 8 l NOTE e After stopping any ECCS pump, RCS pressure should be allowed to stabilize before stopping another ECCS pump.

e -The charging pumps and SI pumps should be stopped on alternate ECCS trains when possible.

20 Check If One CCP Should Be Stopped:

a. Two CCPs - RUNNING a. Go to Step 21.

b. Determine required RCS subcooiing from table:

RCS SUBC00 LING ("F)

SI PUMP STATUS NORMAL ADVERSE CONTAINMENT CONTAINMENT NONE RUNNING 91* 91*

ONE RUNNING 57" 57' TWO RUNNING 50* 50*

c. RCS subcooling based on c. DO NOT STOP CCP. Go to core exit TCs - GREATER Step 23.

THAN REQUIRED SUBC00 LING

d. PRZR level - GREATER THAN d. DO NOT STOP CCP. Go to 5% [30% FOR ADVERSE Step 23.

CONTAINMENT]

e. Stop one CCP

~

C:da; Sympto2/

Title:

Procedure No. '

Revision No./Date:

ES-1.2 POST LOCA C00LDOWN AND DEPRESSURIZATION ES-1.2 Rev. 1 (EXAMPLE ONLY) Rev. 1 / 10/26/83

~

l STEP l l ACTION / EXPECTED RESPONSE l l RESPONSE NOT OBTAINED [

l FIGURE 9 l ATTACHMENT A The following conditions support or indicate natural circulation flow.

e RCS subcooling based on core exit TCs - GREATER THAN 30*F e SG pressures - STABLE OR DECREASING e RCS hot leg temperatures - STABLE OR DECREASING e Core exit TCs - STABLE OR DECREASING e RCS cold leg temperatures - AT SATURATION TEMPERATURE FOR SG PRESSURE e Loop AT - INDICATED c-(EXAMPLE ONLY) l FIGURE 10 l OPERATOR ACTION

SUMMARY

FOR E-3 SERIES PROCEDURES

1. SI REINITIATION CRITERIA Manually operate SI pumps as necessary and go to ECA-3.1, SGTR WITH LOSS OF REACTOR COOLANT - SUBC00 LED RECOVERY DESIRED, Step 1, if EITHER condition listed below occurs.

• RCS subcooling based on core exit TCs - LESS THAN 30*F e PRZR level - CANNOT BE MAINTAINED GREATER THAN 5% [30% FOR ADVERSE CONTAINMENT]

l

2. SECONDARY INTEGRITY-CRITERIA Go to E-2, FAULTED STEAM GENERATOR ISOLATION, Step 1, if any SG pressure is decreasing in an uncontrolled manner or has completely depressurized, and has not been isolated, unless needed for RCS cooldown.

3. COLD LEG RECIRCULATION SWITCHOVER CRITERION Go to ES-1.3, TRANSFER TO COLD LEG RECIRCULATION, Step 1 if RWST level decreases to less than 23.5%.

4. EFW SUPPLY Commence CST makeup as soon as possible to avoid low inventory problems.

5. RED PATH

SUMMARY

- ATTACHMENT A

6. KEY CAUTIONS -

e Maintain _RCS pressure less than ruptured SG(s) ASDV setpoint, e If a MD EFW pump is running, shut down steam driven EFW pump.

32 -

~~

Cadme Symptom /

Title:

Procedura No.

Revision No./Date:

F-0.2 CORE COOLING STAIUS TREE F-0.2 (EXAMPLE ONLY) / 01/12/84

, l STEP l l ACTION / EXPECTED RESPONSE l RESPONSE NOT OBTAINED l l FIGURE 11 l LATER i

- MO H M& Q&T m L-

FIGURE 12 STATUS TREE COLOR LEGEND COLOR CODE Definition Green The critical safety function is satistled - no operator action is called for.

Yellow The critical safety function is not fully satisfied - operator action may eventually be needed. -

Orange The critical safety function is under severe challenge - prompt operator action is necessary.

Red The critical safety function is in jeopardy -

- immediate operator action is required.

i i

i i

i t

l l

r-l

7.

EMERGENCY RESPONSE PROCEDURE CHANGE FORM A. IDENTIFICATION Proc. No. Rev. Change No. _

Title .

Initiated By Date B. CHANGE:

C. TYPE OF CHANGE (NON-INTENT ONLY)

Change is valid.

D. REASON FOR CHANGE:

E. NON-INTENT CHANGE AUTHORIZATION (N/A FOR INTENT CHANGE)

TITLE SIGNATURE DATE

-SRO SRO F. REVIEW AND APPROVAL Operations Manager SORC Meeting No.

i Station Manager r

l-