ML20064J983

From kanterella
Revision as of 14:21, 6 January 2021 by StriderTol (talk | contribs) (StriderTol Bot change)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search
Rev 2 to Preparation of Emergency Response Guidelines
ML20064J983
Person / Time
Site: Comanche Peak  Luminant icon.png
Issue date: 12/28/1982
From: Jane R
TEXAS UTILITIES SERVICES, INC.
To:
Shared Package
ML20064J976 List:
References
ODA-204, NUDOCS 8301180269
Download: ML20064J983 (44)
v • d • e


Text

. - . - - - . _ _ _ _ .- ._ _ . . . --= . _ _

(

u .

COMANCHE PEAK STEAM ELECTRIC STATION OPERATIONS DEPARTMENT ADMINISTRATION MANUAL '

T30 '"

pg gegd5 w4 .,

PREPARATION OF

~

EMERGENCY RESPONSE GUIDELINES PROCIDURE NO. ODA - 204 REVISION NO. 2 l

'j

,: ~'

~

,9 ~7 m ,

', l/ .' u .

  • m .' u e. .

. , .: 3

u ; e y l

SUBMITTED BY '- "

,u -

DATE / '

OPERATIONS SUPERINTENDENT APPROVED BY

/7 ,/ -d DATE / 7-[2 9 /fff_

MANAGER y OPERATIONS '

8301100269 830112 PDR ADOCK 05000445 F PDR

r .

, CPSES

  • ISSUE DATE PROCEDURE NO.

OPERATIONS DEPARTMENT ADMINISTRATION MANUAL DEC 2 8 B82 ODA - 204 PREPARATION OF EHERGENCY RESPONSE REVISION NO. 2 Page 2 of 44 GUIDELINES 1.0 Purpose This procedure describes the method used to develop Emergency Response Guidelines from the Generic Guidelines provided by Westinghouse. This l procedure also prescribes the format in which the CPSES Emergency Response Guidelines (ERG) shall be prepared and provides guidelines regarding the scope and content of and the level of detail to be incorporated into each procedure.

2.0 Applicability This procedure applies to the procedural set which provides guidance for responding to plant emergency conditions. This procedure becomes effective when issued. 4 3.0 Definitions 3.1 Emergency Response Guidelines (ERGS). The over all procedural set which provides guidance for response to plant emergency conditions.

The procedural set is comprised of the following subsets:

e Emergency Operating Procedures (EOP) e Emergency Operating Sub-Procedures (EOS) e Emergency Contingency Actions (ECA) o Function Restoration Guideline (FRS, FRP, FRC, FRI, FRH, FRZ) 3.2 Emergency Operating Procedures. The E0Ps provide the operator with procedural guidance sufficient to effectively diagnose an event and directs the operator to a subprocedure or contingency procedure to recover the plant from nominal emergency conditions and return it to a known safe state from which repair or return to power can be accomplished.

3.3 Emergency Operating Sub-Procedures. The Emergency Operating Sub-Procedures provide guidance for the operator to recover the plant from a known event, condition or state.

3.4 Emergency Contingency Action Procedures. The Emergency Contingency Action procedures provide contingency actions for equipment failures and transitions to Function Restoration Guidelines when required.

3.5 Critical Safety Function Status Trees. Critical Safety function Status trees (CSFST) provide the onerator with a systemmatic and explicit means for determining the status of a limited number of plant parameters which are directly related to maintaining the integrity of the classical

CPSES ISSUE DATE PROCEDURE NO.

OPERATIONS DEPARTMENT ADMINISTRATION MANUAL Mt2E18 ODA - 204 PREPARATION OF EMERGENCY RESPONSE REVISION NO. 2 Page 3 of 44 GUIDELINES barriers to release of radioactivity, the fuel / fuel matrix, the reactor coolant system and the containment. Additionally, the CSFSTS prioritize and direct the operator to the appropriate Function Restoration Guideline.

3.6 Function Restoration Guidelines. Procedures designed to maintain the plant in a safe condition without regard to initiating events or failures subsequent to an event diagnosis. The function restoration procedures will restore critical safety functions to acceptable values and provide transitions to the appropriate E0P, EOS or ECA after the challenge to the safety function has been removed. The following six categories of Function Restoration Procedures are provided:

e Subcriticality (S-Series) e RCS Integrity (P-Series) e Core Cooling (C-Series) e RCS Inventory (I-Series) e Core Heat Sink (H-Series) e Containment (Z-Series) 3.7 Issue Date - The issue date specifies when each CPSES Emergency Response Guideline becomes effective.

4.0 Instructions 4.1 Guidance on the use of Emergency Response Guidelines 4.1.1 General A set of procedures shall be prepared which provide the operatpr with specific instructions to follow in the event of an alarm or upset condition. Collectively, this set of procedures will be sufficient to permit recovery for all upset conditions, whether or not the initiating event has been diagnosed. The set of procedures is composed of the following:

e Emergency Operating Procedures (EOP) e Emergency Operating Sub-Precedures (EOS) e Emergency Contingency Actions (ECA) e Function Restoration (FRS, FRP, FRC, FRI, FRH, FR2)

Figure 1 provides a pictorial representation of how these procedures are collectively used to restore the plant to safe conditions following an upset.

.- _~_ - - - - - - -- -

CPSES " ISSUE DATE PROCEDURE NO.

OPERATIONS DEPARTMENT ADMINISTRATION MANUAL DEC 2 E 1992 ODA - 2 04 PREPARATION OF EMERGENCY RESPONSE REVISION NO. 2 Page 4 of 44 GUIDELINES NO MAL OPERAT!DN b

e ALAR'*

l l VI5 i

RX NO TRIP  : DIEGI  : ESTORE  :

( VE5

\

n l l' E P 1r

!FIED 1 CSF No gg3 5AT!5FIED ,

Yt3

(

its ir

, AUTOMATIC l ACTIONS Yt5 TVE .#0 _

D1MN05l u p 1r 1r p ti ir FR-5ER!!5 1r 1r 1r p 1r y

if If ir if y 1r

's ir U FIGURE 1 EMERGENCY RESPONSE GUIDELINES STRUCTURE l

i I

CPSES . ISSUE DATE PROCEDURE NO.

OPERATIONS DEPARTMENT ADMINISTRATION MANUAL DEC 2 81982 ODA - 204 PREPARATION OF EMERGENCY RESPONSE REVISION NO. 2 Page 5 of 44 GUIDPLINES -

4.1.2 Emergency Ope:. sting Procedures The Emergency Operating Procedures provide the operator with sufficient procedural guidance to diagnose nominal emergency conditions and direct the operator to the appropriate Emergency Operations Sub-Procedure or Emergency Contingency Action Procedure. The E0Ps are initially entered to i

diagnose the initiating event. Concurrently, the critical safety function status trees should be monitored to ensure

( that specified parameters are in acceptable ranges. If the initiating event can be diagneced, the E0P will direct the operator to enter an EOS procedure for recovery. If the event is not immediately diagnosed, the operator returns to l the diagnostic steps in the E0P and repeats specified actions. As before, he concurrently monitors the critical safety function status trees. The ECA procedures provide instructions for contingency actions and will be entered as

, directed by the E0Ps.

4.1.3 Critical Safety Function Status Trees These status trees provide the operator with a systematic and explicit means for determining the safety status of his i

plant for any emergency situation, irrespective of the specific guidance intended for this purpose which is also contained in the Other Emergency Response Guidelines. The status trees can be referenced by the operator at any time, and continuous use of these status trees provides independent verification of the attainment and maintenance of safe plant conditions throughout the recovery. This concurrent use of status trees and the appropriate Emergency Response Guidelines also provides a method for identifying the mode of critical safety function challenge independent of specific event diagnoses and nominal prescribed recovery actions. Therefore, use of the status trees in conjunction with the Emergency Response Guidelines provides a systematic way of identifying and coping with subsequent / multiple failure situations.

The status trees are intended to serve two purposes:

1) general surveillance under all sets of unusual or abnormal conditions that can lead to or result from initiation of safety injection
2) direct operator guidance in those rare events that go beyond the design basis of the Engineered Safeguards Systems and the Emergency Response Guidelines and Emergency Contingency Actions.

1

CPSES 1SSUE DATE PROCEDURE N0 0 OPERATIONS DEPARTMENT ADMINISTRATION MANUAL DEC 2 6 BC ODA - 2(M PREPARATION OF EMERGENCY RESPONSE REVISION NO. 2 Page 6 of 44 CUIDELINES

, It is anticipated that the " general surveillance" aspect of Critical Safety Function monitoring with the Status Trees would be carried out routinely by control room personnel not intimately involved in plant operations (typically, a Senior Reactor Operator in a supervisory role or a Shif t Technical Advisor) during the period following activation of the Engineered Safeguards System and continuing until the plant status is fully diagnosed and understood by the operating personnel. The status trees are displayed on the control room Safety Assessment System (SAS) and should be continuously available. In the unlikely event that the SAS is inopera-tive during an accident, a manual back-up system shall be In applications of this type, use of the Status provided.

Trees would serve as a prudent safeguard against an unrecog-nized degradation of an already abnormal situation by random or common mode failures of safety equipment or by operator error. No recourse by the operators to the Function Restoration Guidelines would be necessary. Prioritizati on of operator actions would be directed by existing Emergency Response Guidelines and Emergency Contingency Actions. How-ever, the non-operating user of the Critical Safety Function Status Trees might well use the Function Restoration Guide-lines and the prioritization guides incorporated in the Sta-tus Trees to verify that the course of action being followed by the operator is consistent with the status of the plant, in terms of Critical Safety Functions, as indicated 'oy the Status Trees. The " direct operator guidance" aspect of Cri-tical Safety Function monitoring with the Status Tree is expected to be applicable only in those very rare situations in which, as a result of multiple or sequential failures of I

' several plant systems, an ongoing transient has entered a domain in which the Emergency Response Guidelines and Emergency Contingency Actions may not be reliable guides and available plant systems may have to be used under direct operator control to maintain the Critical Safety Functions I

and to protect the surviving barriers. Under these

! conditions an initial evaluation of the plant status in terms of the Critical Safety Functions is made and the rules l of prioritization of operator response are invoked to direct the operators to the appropriate Function Restoration Guidelines in order to, at the udnimum, stabilize and, if possible, improve the plant status. Thereafter, the plant status would be reevaluated periodically and as the set of status indicators changes to reflect changing plant status, the operator would be directed to other Function Restoration Guidelines or Emergency Response Guidelines to treat less serious challenges to barrier integrity or to respond to new challenges. Concurrently with these Critical Safety 9 ,-m _-_y- ,,,_ -  %,

_ . - - . . . 3,- , .,- _ - . - . .

we.e CPSES

  • ISSUE DATE PROCEDURE NO.

OPERATIONS DEPARTMENT ADMINISTRATION MANUAL DEC 2 b 1532 ODA - 204 PREPARATION OF EMERGENCY RESPONSE REVISION NO. 2 Page 7 of 44 GUIDELINES Function oriented activities, it is expected that the operators would attempt by other methods to diagnose the plant status in terms of failed equipment and to initiate remedial measures.

4.1.4 Function Restoration Procedures These procedures will provide operator actions which could be effective in responding to challenges to the plant critical safety functions. These guidelines are normally entered via the Critical Safety Function Status Trees, although in cer-tain cases it is possible to enter them directly from the Emergency Response Guidelines via identified transitions that account for specific contingencies. These Function Restoration Guidelines provide guidance for maintaining the plant in a safe state without regard to initiating event or combinations of subsequent or consequential failures after event diagnosis. In most cases, the operator can expect to recover the plant using only the E0P's, EOS's or ECA procedures. However, the availability of the Function Restoration Guidelines provides additional guidance for situations where diagnosis cannot be made, or where subsequent / multiple failures make it impossible to recover the plant by use of the Energency Operating Procedures.

4.2 Preparation of Plant Specific Technical Guidelines 4.2.1 General Generic technical guidelines have been prepared for all of the Emergency Response Guidelines. These generic guidelines provide a complete and documented analytical basis for each of the procedures. The below listed process is illustrated in figure 2 and will be used to make these guidelines applicable to Comanche Peak.

4.2.2 Development of Plant Specific Data Each generic guideline shall be reviewed to determine which data must be made plant specific. This review shall be the basis for the development of a " Comanche Peak Data Package" for each guideline. Attachment 1 indicates the format for the Data Package.

' ~

CPSES , ISSUE DATE PROCEDURE NO.

OPERATIONS DEPARTMENT ADMINISTRATION MANUAL DC0EUn ODA - 2 04 FR'M3ATION OF EMERGENCY RESPONSE REVISION NO. 2 Page 8 of 44 GUIDELINES --

I FIGURE 2 GENERIC GUIDELINES -<

@DWNERSGROUP V

PLANT SPECIFIC TECm! CAL DATA COMANCHE PEAK GUIDELINES VERIFICATION DATA PACKAGE -

l 7

, PLANT SPECIFIC

< EW WIWs GUIDE E 0 P *s PLANT SPECIFIC

< CONTROL ROOM AND SYSTEM CONFIGURATION V

VALIDATED CONTROL ROOM PLANT SPECIFIC

< WALK-TE DUGH AND

  1. 0 P 's VE?.!FICATION CHECKLIST I

l -

t

(

CPSES ISSUE DATE PROCEDURE NO.

OPERATIONS DEPARIMENT ADMINUiRATION MANUAL DEC 2 61982 ODA - 2 %

4 PREPARATION OF EMERGENCY RESPONSE REVISION NO. 2 Page 9 of 44 GUIDELINES 4.2.3 Validation of the technical suidelines The generic technical guidelines have been validated by the Westinghouse Owner's Group. This validation applies also to the Comanche Peak Technical Guidelines since only plant specific data has been inserted and no substantial changes have been made ;o the basic guideline. In order to ensure that the validation process is not compromised, the person responsible for inserting plant specific data shall determine the eff ect, if any, on the validation. This determination shall be documented on Attachment 1.

4.2.4 Documentation The Plant Specific Technical Guidelines contain the following elements:

o Generic Technical Guidelines o Comanche Peak Data Package o Verification that Plant Specific Data does not alter the Generic Analysis Together, these documents provide a complete and documented plant specific analytical basis for each guidelirm 4.2.5 Instructions for Completing the Comanche Peak Data Package 4.2.5.1 Cover Page 4.2.5.1.1 Title - as indicated in Attachment 1 4.2.5.1.2 Guideline No. - Enter the Generic Guideline No.

4.2.5.1.3 Revision No. - Enter the Generic Guideline Revision Date 4.2.5.1.4 Enter the noun name of the Guideline e.g. Reactor trip or Safety Injection 4.2.5.1.5 Submitted By - Signature of submitt er and submittal date 4.2.5.1.6 Approval by - Signature of approver and approval date 4.2.5.2 Second Page -

4.2.5.2.1 Heading - as indicated on Attachment 1 4.2.5.2.2 Guideline Name - Enter noun name 4.2.5.2.3 Plant Specific Revision No. - Enter revision number of the Comanche Peak ERG that is supported by this data package 4.2.5.2.4 Generic Guideline Revision Date - Enter date listed on Generic Guideline 1__. .

~

T~ L ~C::::: : ^ ~ ~ ~ ^: ::"

~~

CPSES ISSUE DATE PROCEDURE NO.

OPERATIONS DEPARTMENT ADMINISTRATION MANUAL pq c c 11- ODA - 2 04 PREPARATION OF EMERGENCY RESPONSE REVISION NO. 2 Page 10 of 44 GUIDELINES 4.2.5.2.5 Guideline No. - Enter Comanche Pea k Guideline No.

4.2.5.2.6 Page No. - Enter data package page number as part of the entire data packag e 4.2.5.2.7 Step 1 - Enter the total number of pages of data entered and provide any comments necessary to support the entry of data.

The signature block shall contain the signature of the responsible engineer entering the da ta. A space has be en provided for the engineer's printed name.

4.2.5.2.8 Step 2 - Enter the total number of pages of data verified and provide a brief description of the verification process.

The signature block shall contain the signature of the responsible enginee r verifying the da ta. A space has be en provided for the enginear's printed name.

4.2.5.3 Data Pages 4.2.5.3.1 Header data - Same as section 4.2.5.2 l 4.2.5.3.2 Guideline Step No. - Enter the step number requiring Comanche Peak specific data.

4.2.5.3.3 Plant Specific Data Required - Enter the Plant Specific data.

4.2.5.3.4 Source / Justification / Calculation - Enter the source of the data (PSAR, component technical manual. Technical Specifications, etc.) along with necessary justification or calculations.

4.2.6 Incorporation of changes Periodically, the generic guidelines may be changed or new guidelines added. When this occurs, revised generic guidelines will be reviewed and plant specific data entered, l as appropriate. The same documentation process will be I

used. New guidelines i til be treated in accordance with I steps 4.2.1 through 4.2., of this procedure and reference 5.3.

l l

w v. e- --, <,

y, ,n

CPSES ISSUE DATE PROCEDURE NO.

O'PERATIONS DEPARTMENT ADMINISTRATION MANUAL DEC 2 619B? ODA - 204 PREPARATION OF EMERGENCY RESPONSE REVISION NO. 2 Page 11 of 44 GUIDELINES '-

4.3 Preparation of Emergency Operating, Eaergency Operating Sub-Procedures, Emergency Contingency Action and Function Restoration Procedures The Emergency Operating, Emergency Operating Sub-Procedures.

Emergency Contingency Action and Function Restoration procedures will be prepared using the plant specific technical guideline as the technical basis for the procedure. Attachment 2 provides instructions for translating this technical information into a procedure acceptable for use in the control room.

4.4 Verification of Emergency Response Guidelines Each procedure shall be verified to ensure the procedure is accurate and useable. The verification process.will normally be a control- room walk-through to ensure technical adequacy as well as usability (hunan factors). The check list shown in Attachment 3 will be used to document this verification. The check list will be filed with the Comanche Peak Data Package for each procedure.

4.5 Operator Training Criteria The plant operators (R0 and SRO) will receive training on the Emergency Response Program and on each procedure. The training will provide a mechanism to ensure that each operator understands the fundamental concepts with symptom based procedures.

Additionally, the training will be structural to ensure that the operators become familiar with each of the procedures and will provide a mechanism for feedback to incorporate procedure improvements. The training will be a combination of classroom lectures, self study and control room walk-throughs of the actual procedures. Attachment #4 is the form used for incorporating procedural improvements identified through the training program.

5.0 References 5.1 CPSES Operations Administrative Control and Quality Assurance Plan.

5.2 ANSI N18.7-1976, " Administrative Controls and Quality Assurance for the Operational Phase of Nuclear Power Plants."

5.3 STA - 202, " Preparation, Review, Approval and Revision of Station Procedures."

5.4 ODA - 201, " Preparation of Integrated Plant Operating Procedures."

5.5 ODA - 202, " Preparation of System Operating Procedures."

5.6 NUREG - 0899, Guidelines for the preparation of Emergency Operating s Procedures.

6.0 Attachments 6.1 Attachment 1, Comanche Peak Data Package 6.2 Attachment 2. Writer's Guide 6.3 Attachment 3. Procedure Verification Checklist 6.4 Attachment 4, Procedure Improvement Recommendations 7 - --

. _ .. _ 7 _ - -.- -

1 .. .

CPSES ,

ISSUE DATE PROCEDURE NO.

OPERATIONS DEPARTMENT ADMINISTRATION MANUAL CEC (,19p ODA - 2 04 i

PREPARATION OF EMERGENCY RESPONSE REVISION NO. 2 Page 12 of 44 GUIDELINES ATTACHMENT 1 PAGE 1 0F 3 C(MANCHE FEAK STEAM II.ECTRIC STATION EMERGENCY 3.r$PONSE WIDELINE DATA FACKAGE I

DATi. PACKAGE (4.2.5.1.1)

CUIDELINE NO. (4.2.5.1.2)

REVISION DATE (4.2.5.1.3)

NAMI (4. 2. 5.1.4 )

l SUBMITTED BT (4.2.5.1.5) DATE OPERAT100iS SUPERINTDiDENI APPROVED BT (4.2.5.1.6) DATE MANAGER. FLANI OPERATIONS

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

__ - --,_.-e---

, . . . . ~ - -

. = _ . . .- _ - - ._ _

CPSES . ISSUE DATE PROCEDURE NO.

OPERATIONS DEPARTMENT ADMINISTRATION MANUAL DEC 2 81332 ODA - 2 04 PREPARATION OF EMERGENCY RESPONSE REVISION NO. 2 Page 13 of 44 ,

GUIDELINES ATTACHMENT 1 PAGE 2 OF 3 g CPSES FLANT aru.1FIC wwELINE NG.

DIERGENCY RESPONSE CUIDELINE DATA PAGAGE REVISION NO. ODA - 2 04 (4.2.5.2.3) (4.2.5.2.5)

GUIDELINE NAME: (4.2.$.2.2) REVISION DATE Page of (4.2.5.2.4) (4.2.5.2.6)

1. Data on pages 3 through of this data package has been made specific to the Comanche Peak design and does not compromise the generic technical basis for this guideline.

Commente:

l (4.2.5.2.7) l l

Signature da te Print name of Engineer entering da ta

2. Data on pages 3 through of this data package has been verified as specific to the Comanche Peak design and does not compromise the generic technical basis for this guideline.

Comments /brief description of verification process: ,

I i

(4.2.5.2.8)

Signature da te Print name of Engineer verifying da ta i

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

CPSES . ISSUE DATE PROCEDURE NO.

OPERATIONS DEPARTMENT ADMINISTRATION MANUAL DEC 2 81982 ODA - 2 04 PREPARATION OF EMERGENCY RESPONSE REVISION NO. 2 Page 14 of 44 CUIDELINES ___

ATTACHMENT 1 PAGE 3 0F 3 LFbLb TLAN4 brg4,4746 E wL 4DL h.

IMERGENCY RESPONSE GUIDELINE B4TA FACKAGE 2EVIS10N NO. ODA - 2 04 GUIDELINE NAME: REVISION DATE Page of Guideline Step No. Plant Specific Sour ce / Jus tifi ca ti on /Calcula t i o ns Data Required (4.2.3.3.2) (5.2.S.3.3) (4.2.5.3.4) i

=%, - - = -+ % m.,w w.- g -w- - vo - ww e .. w - e w - - . + " - "--

CPSES ' ISSUE DATE PROCEDURE NO.

OPERATIONS DEPARTMENT ADMINISTRATION MANUAL DEC 2 lie 2 ODA - 2 04 PREPARATION OF EMERGENCY RESPONSE REVISION NO. 2 Page 15 of 44 GUIDELINES ATTACHMENT 2 PAGE 1 0F 27 COMANCHE PEAK STEAM ELECTRIC STATION i

EMERGENCY RESPONSE GUIDELINES WRITER'S GUIDE I

l l

.- ....-..-..,,~.m.-_. . . . . . . - - - . . - - - - - - - . - - . - - -

,, , r--

, @ESS ' ISSUE DATE PROCEDURE NO.

OPERATIONS DEPARTMENT ADMINISTRATION MANUAL DEC 2 6 1532 ODA - 2 04 PREPARATION OF EMERGENCY RESPONSE REVISION NO. 2 Page 16 of 44 GUIDELINES ATTACHMENT 2 PAGE 2 0F 27 TABLE OF CONTENTS SECTION TITLE PAGE

1.0 INTRODUCTION

1.2 Purpose 4 .

l 1.2 Scope 4 2.0 ERG DESIGNATION AND NUMBERING 2.1 Procedure Designation 5 2.2 Procedure Numbering 5 2.3 Revision Numbering and Designation 5 3.O FORMAT 3.1 Title Page 5 3.2 Administrative Note Page 6 3.3 First Procedure Page 8 3.4 Remaining Procedure Pages 8 3.5 Attachments 12 3.6 Procedure Organization 14 3.7 Section Numbering 14 l

1 4.0 WRITING INSTRUCTIONAL STEPS 4.1 Instruction Step Length and Content 14 4.2 Action / Expected Response Column 15 4.3 Response Not obtained Column 15 4.4 Use of Logic Terms 16 4.5 Use of Cautions and Notes 17 4.6 Calculations 17 4.7 Underlining 17 4.8 Referencing among and between procedures 18 4.9 Component Identifications 18 4.10 Level of Detail 19 4.11 Operator Aids 19 l

__ .- 3 7 -. . .

.,7_ _---

CPSES ISSUE DATE PROCEDURE NO.

OPERATIONS DEPARTMENT ADMINISTRATION MANUAL DEC 2 81982 ODA - 2 04 PREPARATION OF EMERGENCY RESPONSE REVISION NO. 2 Page 17 of 44 GUIDELINES ATTACHMENT 2 PAGE 3 0F 27 TABLE OF CONTENTS (continued)

SECTION TITLE PAGE 5.0 MECHANICS OF STYLE 5.1 Spelling 20 5.2 Hyphenation 21 5.3 Punctuation 21 5.4 Vocabulary 22 5.5 Numerical Values 24 5.6 Abbreviations Letter Symbols, Acronyms 25 6.0 TYPING INSTRUCTIONS 6.1 General Typing Instructions 25 6.2 Page Arrangement 26 6.3 Breaking of Words 26 6.4 Printed Operator Aids 26 6.5 Use of Foldout Pages 27 6.6 Use of Oversized Pages 27 6.7 Use of Reduced Pages 27 7.0 REPRODUCTION 27

-- , , _ 4__. =J+

CPSES ' ISSUE DATE PROCEDURE NO.

OPERATIONS DEPARTMENT ADMINISTRATION MANUAL DEC 2 E D" ODA - 2 04 PREPARATION OF EMERGENCY RESPONSE REVISION NO. 2 Page 18 of 44 l GUIDELINES l -

ATTACHMENT 2 PAGE 4 0F 27

1.0 INTRODUCTION

Emergency Response Guidelines (ERGS) are plant procedures that direct actions necessary to mitigate the consequences of transients and accidents that cause plant parameters to exceed reactor protection system set point s or engineered safety feature set points. The ERGS will provide the operator guidance on how to verify the adequacy of critical safety  ;

functions and restore and maintain those functions when degraded. The ERGS will be written so that the operator need not diagnose an event, such as a )

small break LOCA, in order to maintain the plant in a safe configuration. I Generic Technical guidelines supplied by the Westinghouse Owners' Group have been made plant specific for Comanche Peak and will provide the technical basis for the development of the Comanche Peak ERGS. j l

Technical guidelines represent the translation of engineering data derived '

from calculations, computer modsling, and plant-specific information (i.e.

TSAR, Technical Specification, etc.) into information presented as guidance for development of detailed, plant-specific ERGS. These technical guidelines will provide plant specific information such as inventory control and containment integrity, delineating the entry conditions to be used in the ERGS. The technical guidelines will provide step-by-step information for transition from emergency conditions to a safe, stable condition, such as cold shutdown. ERGS must be written to provide detailed, plant specific instructions to implement each step in the technical guidelines.

1.1 Purpos e This document provides administrative and technical guidance to 'ue followed when writing ERGS.

1.2 Scope This writers guide applies to the writing of all emergency response guidelines (ERGS).

2.0 ERG DESIGNATION AND NUMBERING ERGS are procedures that govern plant operation during emergency conditions and specify operator actions to be taken to return the plant to a known, stable condition.

Each procedure shall be uniquely identified. This identification permits easy administration of the process of procedure preparation, review, revision and distribution. Unique identification also facilitates ease of use by operations personnel.

=

  • _-=7-, y-.+. . . . . _ . . .

, CPSES ISSUE DATE PROCEDURE NO.

OPERATIONS DEPARTMENT ADMINISTRATION MANUAL nm , y , , ODA - 2 04 PREPARATION OF EMERGENCY RESPONSE REVISION NO. 2 Page 19 of 44 GUIDELINES ATTACHMENT 2 PAGE 5 0F 27 2.1 Procedure Designation Designation of the Emergency Response Guidelines shall be as follows:

2.1.1 Emergency Operating Procedure (EOP) 2.1.2 Energency Operating Sub-procedure (EOS) 2.1.3 Emergency Contingency Actions (ECA) 2.1.4 Function Restoration Guidelines (FR) 2.2 Procedure Numbering A unique number will follow the procedures designation and will consist of two digits spaced by a period.

Examples: E0P - 0. 0 unique identification number procedure designator EOS - 0.1 l

unique identification numbe r procedure designator The unique number generally will correspond to the number assigned to the technical guideline from which the procedure is prepared.

2.3 Revision Numbering and Identification Revisions to ERGS will be accomplished in accordance with STA - 202

" Preparation, Review, Approval and Revision of Station Procedures."

3.0 FORMAT 3.1 Title Page Each ERG shall have a title page (Figure 1). The primary purposes of the title page are to identify the procedure and the authorized revision.

i l CPSES ISSUE DATE PROCEDURE NO.

OPERATIONS DEPARTMENT ADMINISTRATION MANUAL DEC 2 c edi ODA - 2 04 PREPARATION OF EMERGENCY RESPONSE REVISION NO. 2 Page 20 of 44 GUIDELINES -

ATTACEMENT 2 PAGE 6 0F 27 The title page shall contain the following information:

3.1.1 A title descriptive of the emergency condition to which the procedure applies 3.1.2 The procedure designation and number 3.1.3 The procedure revision number 3.1.4 The submitter's signature and the date of submittal 3.1.5 The approver's signature and the date of approval.

3.2 Administrative Note Page This page is used to identify those administrative tasks that must be performed prior to issuing the procedure (Figure 2). Examples of Administrative Notes are as follows:

3.2.1 " Identification numbers for steps 1, 2 and 3 shall be circled with black ink."

3.2.2 " Vertical lines for the table on Attachment 1 must be hand d rawn. "

3.2.3 " Greater-than symbols for parameter 1 of symptom set I and III of Attachment I must be hand drawn."

3.2.4 " Figure 1 shall Se printed on the reverse of page 2 of 12."

= h w...- e.#.. s . .. --..f .-.-m.. e -w -m,-- == m

@SES . ISSUE DATE PROCEDURE NO.

OPERATIONS DEPARTMENT ADMINISTRATION MANUAL DEC 2 81982 ODA - 2 04 PREPARATION OF EMERGENCY RESPONSE REVISION NO. 2 Page 21 of 44 GUIDELINES ATTACHMENT 2 PAGE 7 0F 27

. C(MANCHE PEAK STEAM ELECTRIC STATION

  • EMERGENCY RESP 0pSE GUDELINES 6

3.1.1 3.1.2 3.1.3 SUBMITTED BY DATE 3.1.4 AFFR072 SY DATE _ ,

3.1.5 FIGURE 1

i CPSES ISSUE DATE PROCEDURE NO. i PERATIONS DEPARTMENT ADMINISTRATION MANUAL DEC 2 81962 ODA - 204 PREPARATION OF EHERGENCY RESPONSE REVISION NO. 2 Pa'ge 22 of 44 GUIDELINES ATTACHMENT 2 PAGE 8 0F 27 The Administrative note page shall contain a statement that indicates it is not to be issued with the procedure.

3.3 First Page of Each Procedure The first page of each procedure shall contain the purpose statement and symptoms for entry into the procedure, as applicable per the latest revision of the Westinghouse Owners Group generic guideline.

Figure 3 is an example of a typical procedure first page.

3.4 Remaining Procedure Pages A two column format for the remaining pages of the procedure shall be used (Figure 4). The left hand column is designated for operator action or expected response to automatic actions. The right hand column is designated " response not obtained" and lists contingency actions for the operator to take when the expected response is not obtained.

3.4.1 With the exception of the title page and the attachments, each page of an Emergency Response Guideline shall contain the following information in the title block at the top of that page (Figure 4).

3.4.1.1 Title 3.4.1.2 1ssue date 3.4.1.3 Procedure identifying number 3.4.1.4 Procedure Revision number 3.4.1.5 Page number as part of the entire procedure, including its attachments.

'* em wapW qe., ye-w Ay *3 g-*e 4e me m

  • n - w .9 *
  • e4 m geg-u.as w m e e e & mgO$ ey pgap-% m w'

C*SES ISSUE DATE PROCEDURE NO.

OPERATIONS DEPARTHENT ADMINISTRATION MANUAL g.- 3 3 j;g ODA - 2 04 PREPARATION OF EMERGENCY RESPONSE REVISION NO. 2 Page 23 of 44 GUIDELINES ATTACHMENT 2 PAGE 9 0F 27 Procedure No.

Revision No.

NOTES:

1. The following administrative items must be complete prior to issuing this procedure.
a. Identification, numbers for Steps 1 through 17 shall be circled with black ink.
b. Place keeping aids (boxes, approximately 3/8" square) shall be hand drawn at the conclusion of each " circled" step.
c. Bullets "o" shall be " colored" in with black ink,
d. Foldout step 4 - Table must be hand drawn, also greater thans for 1200*7 and 700*F.
2. Upon completion of the above items, the procedure, less this sheet, is ready to be issued.

l l

l FIGURE 2

""""7 - == -e r g

CPSES ISSUE DATE PROCEDURE NO.

OPERATIONS DEPARIMENT ADMINISTRATION MANUAL DEC 2 8 G32 ODA - 2 04 PREPARATION OF EMERGENCY RESPONSE REVISION NO. 2 Page 24 of 44 GUIDELINES ATTAC1DiENT 2 PAGE 10 0F 27 CPSES ISSUE DATE PROCEDURE NO.

EMERCENCY RESPONSE CUIDELINT IDP - 0.0 REACTOR TRIP OR SATETY INJECTION REVISION NO. O Page 2 of 14 d STEP ) l ACisON et APECitD RE5POrME l ,I RESPONSE NOT OSTAINED l A. PURPOSE:

The purpose of this procedure is to verify froper response of aut t .atic protection systems following auto =atic actuation of a PEACTOR TRIP or SATETY 1 EJECTION; and to assess plant conditions and identify the appropriate recovery procedure to be used.

B. SYMP70F.S:

1. Feactor Trip:
a. Any Tirst-Out arnunciator lit.
b. Rapid decrease in neutron flux level
c. All rod bot tom lights lit and rods on the bottom
d. Eeactor t rip breakers open
e. Empf d decrease in unit load to O Power.
11. Safety injection:
a. Safety injection ar.nunciator lit.
b. ECCS pu=ps running
c. EST status parel indications t

i l

i l

l

! PIGURE 3

CPSES ISSUE DATE PROCEDURE NO.

OPERATIONS DEPARTMENT ADMINISTRATION MANUAL DEC 2 E 1982 ODA - 2 04 PREPARATION OF EMERGENCY RESPONSE REVISION NO. 2 Page 25 Of 44 GUIDELINES ATTACHMENT 2 PAGE 11 0F 27 CPSES ISSUE DATE PROCEDURE N0, EPERCENCY RESPONSE CUIDELINE EOF - 0.0 R DCTOR TRIP OR SATETT INJECTION REVISION NO. O Page 3 of 14 d51EPl l ACilON/f XPECif D RE5PONSE l l RESPON5f NOT O81AINED l NOTE: Circled nu:sbers show I!?.I.DIATE ACTIO'1 steps h0T E: Foldout page should be cpen (Att.achrtnt 1).

Verif y Reactor Trip:

a. All rod bot tom lights - LIT a. P.anually trir reactor.

IT reactor vill NOT trip.

THEN go to ECA - 1.0 INTICIPATEP TUI.SIEhT

'.!!HOUT TRIP.

b. All rod pesition indicaters -

ZERO

c. heut ron flux - DECREASING Terif y Twiline Trip:
a. All turLine stcp valves - CLOS 2 a. Panually trip tuttine. IF the turtir.e vill NOT trip.

THEN either stop the EHC p u=ps OR trip the t urbine via the Lctal Trip Valve located at the bydraulic centrol rack.

W rify AC Emergency Euses IF ?;0T energized. THE*: go to Energized: LCA - 2.0, LOSS OF Al.L AC e AC ercrgency bus voltage - FC'.'ER, STEP 3.

h3/?.AL I F ?.07 f r.itiat ed. THEN go t o C1.rck If 51 in lettiated:

i c!. - 0.1 F. LAC %E c.1P

a. F.rstpt o f .in "5" r irr.a1 a s F KC/.' LRY.

1.dscated on t hi, IST Sutus

, P..r.v1 g aru. t s on of t bc f oll e.. : rg s a f ers... r d 6 e q .i p: .t nt :

. CC h.:p> - >J.' ?;1NC e 51 ! u p s - HT:. !!.C e til re ps . F:.!.!NG e C5 P: r.ps. - F 1 ? '.1 ?.r.

. ( h T-  ; s - v  !.C e *4:  ;.. . i t *, *c e y - *r..sr.  :.Y.' Pa p s

&L '. l '. L D) ,

\ __.

e t.s ,

es s e:.q T:s*c1

..t a r s . >~. *. t a.C FIGURE 4

  • e.
  • ' Nd ' * %>'e. +4.g..e w.e. , ,

@SES j ISSUE DATE PROCEDURE NO. t OPERATIONS DEPARTMENT ADMINISTRATION MANUAL DEC 2 61982 ODA - 2 04 PREPARATION OF EMERGENCY RESPONSE REVISION NO. 2 Page 26 of 44 CUIDELINES -

ATTACHMENT 2 PAGE 12 0F 27 3.5 Attachments Attachments to Emergency Response Guidelines shall be minimized; however, there are cases where attachments may be necessary. The attachments should contain information pertinent to accomplish certain functions in the procedure. Fold-out pages will be attachments.

Other Attachments might be steps necessary to start a reactor coolant pump.

3.5.1 Attachments to Emergency Response Guidelines shall contain identifying information at the top of each page as follows (see Figure 5):

3.5.1.1 Attachment Number 3.5.1.2 Attachment Page Number as part of the entire attachment 3.5.1.3 Procedure identifying number 3.5.1.4 Procedure revision namber 3.5.1.5 Procedure page number as part of the entire procedure, including its attachments 3.5.2 The " foldout" page shall always be the last attachment and

! shall have a color coded tab for rapid identification.

I O

l

CPSES ISSUt DATE PROCEDURE NO.

OPERATIONS DEPARTMENT ADMINISTRATION MANUAL DEC 2 b bac ODA - 2 04 PREPARATION OF EMERGENCY RESPONSE REVISION NO. 2 Page 27 of 44

. GUIDELINES ATTACHMENT 2 PAGE 13 0F 27 Attachment 1 Page I of 1 Procedure No. E0P - 0.0

' Revision No. 0 Page 14 of 14 REACTOR TRIP OR SAFETY INJECTION

1. RCP TRIP CRITERIA o Trip any RCP if component :ooling water to that pump is lost and uPFer et lower bearing temperature is greater than 200*F, o Trip all RCPs if BOTH conditions listed below are met:
a. SI is OK,
b. FCS pressure - EQ' AL J TO OR LESS THAN (.later) PSIG.
2. SI 7ERMINATION CRITERIA FOR SPURIOUS SI
a. Terminate 51 when M parameters listed below are set z

( 1) Containment Conditions - NOPJtAL (2) RCS Pressure - CREATER THAN 2000 PSIC (3) RCS Subceoling - (lat er) *T (4) Pressurizer Level - GREATER THAN 25%

(5) Ecat Sink:

(a) SG Level - CREATER THAN 601

-OR-(b) AIV T1ow - GREATER THAN 878 GPM

3. 51 REINITI ATION CRITERI A FOLLO*.'INC SPURIOUS SI
a. Reinitiate SI if ANY ONE of the parameters listed below occurs:

(I) RCS Pressure - LESS THAN 1785 PSIG (2) RCS Stt cooling - LESS THAN (later)*T (3) Pressurizer Level - LESS THAN 102 4 S gPTOMS FOR FRC - 0.1. RESPONSE TO INADEQl' ATE CORE C00l!NC Co to t kC - 0.1. RESIONSE 10 JNA LEQUATE CORE COOLING when ALL symptoms in ANY ON E of the following syrptom sets occur:

PARAMETER: SYMPTOM SET I II I II

1. TCs > 1200 'T -

> 700'T

2. Containment Condition -

AENOPJML #ENOPMAL

3. RCP Status -

ANY ON ALL OFF

5. SYKPTOMS FOR ITJi - O.1. PESPONSE TO LOSS OF SECONDARY HEAT SINK Co to IEH - 0.1 PESPONSE TO LOSS OF SECONL/aY !iuf SihK, if AFW T10w is h0T AVAILABLE.
6. Reference procedure No. EPP-201, ACCESSENT OF E.P.RCE' ICY ACTION EE".'ELS AND FLAN ACTIVIATION, to deter ine if t his event is covered by the e erpncy plan.

FIGURE 5

CPSES ISSUE DATE PROCEDURE NO.

OPERATIONS DEPARTMENT ADMINISTRATION MANUAL DEC 2 81982 ODA - 2 04 PREPARATION OF EMERGENCY RESPONSE REVISION NO. 2 Page 28 of 44 GUIDELINES .

ATTACHMENT _2 PAGE 14 0F 27 3.6 Procedure Organization The following section headings will be used for all ERGS:

3.6.1 PURPOSE -- Brief statement of the purpose of the specific procedure.

l 3.6.2 SYMPTOMS -- The entry conditions or symptoms requiring the use of the procedure. The list will contain only those alarms, indications operating conditions, automatic system actions or other unique symptoms that the operator is to use in deciding to use the procedure. .

3.6.3 ACTION / EXPECTED RESPONSE and RESPONSE NOT OBTAINED -- The  !

operator actions will be short, concise, identifiable instructions that give appropriate directions to the user.

3.7 Section and Instruction Step Numbering 3.7.1 The PURPOSE and SYMPTOMS sections shall be identified as sections A and B respectively (see Figure 3) 3.7.2 An alpha-numeric system will be used for numbering steps in the ACTION / EXPECTED RESPONSE and RESPONSE NOT OBTAINED sections as f ollows:

1. Verify ........
a. All .......
1) S tar,t ........

o CCP Running When steps are identified by a number or letter they must be f ollowed in sequence. When bullets "o" are used, they may be performed in any order.

4.0 WRITING INSTRUCTION STEPS 4.1 Instruction Step Length and Conten t

(

Instruction steps will be concise and precise. Conciseness denotes brevity; preciseness means exactly defined. Thus, instructions should be short and exact. This is easily stated, but not so easily achieved. General rules to be used in meeting objectives are as follows:

4.1.1 Instruction steps should deal with only one idea.

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

CPSES ISSUE DATE PROCEDURE NO.

OPERATIONS DEPARTMENT ADMINISTRATION MANUAL DEC 2 L I; ODA - 2 04 PREPARATION OF EMERGENCY RESPONSE REVISION No. 2 Page 29 of 44 GUIDELINES AKLAGhnLhk 4 PAGE 15 0F 27 4.1.3 Complex evolutions should be prescribed in a series of steps, with each step made as simple as practicable.

4.1.4 Obj ects of operator actions should be specifically stated.

This includes identification of exactly what is to be done and to what.

l 4.1.5 Limits should be expressed quantitatively whenever possible.

4.1. 6 Mandatory sequence of steps is assumed unless the steps a re identified by bullets "o".

4.1.7 Identification of components c.nd parts should be complete.

4.1.8 Instruction content should be written to communicate to the i

user.

4.1.9 Expected results of routine tasks need not be stated.

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

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

4.1.12 When considered beneficial to the user for proper understanding I and performance, describe the system response time associated with

performance of the instruction.

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

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

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

4.2 Action / Expected Response Column The lef t-hand column of the dual-column format will contain operator action steps and expected response steps. The following rules a re established for this column, in addition to the general rules above.

4.2.1 Expected indications should be presented in this column.

4.2.2 Operator actions in this column should be appropriate for the expected indications.

l 4.3 Response Not Obtained Column Contingency actions (expected response not obtained) will be presented in the right-hand column of the dual-column format. Contingency actions are operator actions that should be taken in the event a stated condition, event, or task does not represent or achieve the expected result. The need for contingency action occurs in conjunction with tasks involving verification, observation, confirmation, and monitoring.

.. v , , .- ,

CPSES ISSUE DATE PROCEDURE NO.

OPERATIONS DEPARTMENT ADMINISTRATION MANUAL KC g 81982 ODA - 2 04 PREPARATION OF EMERGENCY RESPONSE REVISION NO. 2 Page 30 of 44 GUIDELINES ATTACKHENT 2 PAGE 16 0F 27 Contingency actions will be specified for each circumstance in which the expected results or actions might not be achieved. The contingency actions should identify, as appropriate, directions to i override automatic controls and to initiate manually what is normally automatically initiated.

4.4 Use of Logic Terms The logic terms AND, 0R, NOT, IF, IF NOT, WHEN, and THEN are of ten necessary to describe precisely a set of conditions or sequence of actions. When logic statements are used, logic terms will be highlighted so that all the conditions are clear to the operator.

Emphasis will be achieved by using capitalization and underlining.

All letters of the logic terms shall be capitalized and the words will be underlined.

The use of AND and OR within the same action shall be avoided. When AND and OR are usedTogether, the logic can be very ambiguous.

t The dual-column format used equates to the logic, IF NOT the action in the lef t-hand column. THEN follow the action specified in the right-hand column; for example: ))[ RCS press, below 1536 psig, THEN l verify SI pump flowmeters.

i Use other logic terms as follows:

4.4.1 When attention should be called to combinations of conditions, the word AND shall be placed between the description of ea ch condition. The word AND shall not be used to join more than three conditions. Il four or more conditions need to be joined, a list format shall be used.

4.4.2 The word OR shall be used when calling attention to alternative combinations of conditions. The use of the word OR shall

~

always be in the inclusive sense. To specify the exclusive "0R," the following may be used: "either A OR B but not both."

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

4.4.4 Use of IF NOT should be limited to those cases in which the operator must respond to the second of two possible conditions.

JU[ should be used to specify the first condition.

_ _ n:r:_. _ r - T' - _-

CPSES ISSUE DATE PROCEDURE NO.

OPERATIONS DEPARTMENT ADMINISTRATION MANUAL DEC 2 e 1982 ODA - 2 04 PREPARATION OF EMERGENCY RESPONSE REVISION NO. 2 Page 31 of 44 GUIDELINES ATTACHMENT 2 PAGE 17 0F 27 4.4.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.

4.5 Use of Cautions and Notes 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 gre called "PRECAUTIObE" 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.

Cautions shall extend across the antire page and shall be highlighted as shown in the Example CAUTION. This placement of cautions helps ensure that the procedure user observes the caution before performing the step. A caution cannot be used instead of an instructional step.

It should be used to denote a potential hazard to equipment or ,

personnel associated with or consequent to the subsequent instructional step.

If additional information other than cautions is necessary to support an action instruction, a NOTE should be used. A NOTE should present information only, not instructions. Notes will extend across the j Page.

4.1.1 The following examples illustrate these instructions.

4.5.1.1 Example NOTE:

NOT E: Circled numbers show IMMEDIATE ACTION steps.

4.5.1.2 Example CAUTION:

  • CAUTION: Do not throttle AFW flow until level is above the
  • top of the U-tubes.

t 4.6 Calculation s Mathematical calculations should be avoided in ERGS. If a value has to be determined in order to perform a procedural step, a chart or graph should be used whenever possible.

4.7 Use of Underlining Underlining will be used for emphasis of logic terms NOTE and CAUTION.

I --

1 . . - .-.. . . -.... . _ - .. - . . .

CPSES ISSUE DATE -

PROCEDURE NO.

OPERATIONS DEPARTMENT ADMINISTRATION MANUAL DEC 2 81982 ODA - 2 04 PREPARATION OF EMERGENCY R2SPONSE REVISION NO. 2 Page 32 of 44 GUIDELINES ATTACHMENT 2 PAGE 18 0F 27 4.8 Referencing Among and Between Procedures Referencing implies that an additional procedure or additional step will be used as a supplement to the procedure presently being used.

Referencing other steps within the procedure being used, either future steps or completed steps, should be minimized. When only a few steps are involved in referencing, the steps should be stated in the procedure wherever they are needed.

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

Use quotation marks to emphasize the title of the referenced or branched procedure; examples: Go to EOS - 0.1, REACTOR TRIP RECOVERY. " Go to Step 20.

t When cross referencing is unavoidable, appropriate place keeping aids shall be incorporated. See section 4.11, 4.9 Ccuponent Identification With respect to identification of components, the following rules are to be followed: ,

i 4.9.1 Equipment , controls, and displays will be identified in operator language (common usage) terms. These terms will generally match engraved names on panels.

4.9.2 When the engraved names and numbers on panel placards and ala rm windows are specifically the item of concern in the procedure, the engraving should be quoted verbatim and emphasized by using all capitals.

1 4.9.3 The names of plant system titles are emphasized by initial capitalization. When the word " system" is deleted from the title because of brevity and is understood because of the con text , the title is also emphasized by initial capitalization.

4.9.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 parentheses following the identification.

l .- . . . - . - . - - . - - . . - . . , - . ..

CPSES ISSUE DATE PROCEDURE NO.

OPERATIONS DEPARTMENT ADMINISTRATION MANUAL nre , n e, ODA - 2 04 PREPARATION OF EMERGENCY RESPONSE REVISION NO. 2 Page 33 of 44 GUIDELINES ATTACHMENT 2 PAGE 19 0F 27 4.10 Level of Detail Too much detcil in ERGS should be avoided in the interest of being able to effectively execute the instructions in a timely manner. The level of detail required is the detail that a newly trained and licensed operator would desire during an emergency condition.

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

4.10.1 For asch control that is provided for infrequent or abnormal operation, with a number engraved on the control panel placard, the nvmber should be included in parentheses within the instructional step. Indication for Controls provided for normal plant operaticn will not generally be listed in the ERGS.

4.10.2 For control circuitry that executes an entire function upon actuaticn of the control switch, the action verb appropriate to -

the component suffices without further amplification of how to manipulate the control device; for example, "SI PNTS SUCTION ,

FROM RWST, (69/1-8806) - OPEN." Recommended action verbs are as follows:

4.10.2.1 For power-driven rotating equipment, use Start, S top.

4. 10.2. 2 For valves, use Open, Close, Throttle Open, Throttle Close Throttle.

4.10.2.3 For power distribution breakers, use Synchronize and Close, Trip 4.10.3 For control switches with a positional placement that l establishes a specified readiness condition, the verb " Place" l should be used along with the engraved name of the desired l

position; For example, " Place the Steam Dump Interlock Selector i Switch in the "BYP INTLK" position.

4.10.4 Standard practices for observing for abnormal results need not be prescribed within procedural steps. For example, observation of noise, vibration, erratic flow, or discharge l

pressure need not be specified by steps that start pumps.

l .

, 4.11 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.

  • - - - - -- -- , - - - m

CPSES ISSUE DATE PROCEDURE NO.

OPERATIONS DEPARTMENT ADMINISTRATION MANUAL DEC 2 81982 ODA - 204 PREPARATION OF EMERGENCY RESPONSE REVISION NO. 2 Page 34 of 44 GUIDELINES ATTACHMENT 2 PAGE 20 0F 27 4.11.1 Units of Measure Units of measure on figures, tables, and attachments should be given for numerical values that represent observed, measurement data, or calculated results. A slant line should be used instead of "per";

examples: ft/sec, lbs/hr.

4.11.2 Titles and Headings Capitalization should be used for references to tables and figurcu, titles of tables and figures within text material, column headiags within a table.

Examples: Refer to figure 1 for . ..

... as shewn in Table 2, Equipment Power i

Supplies, the ....

4.11.3 Figure, [sble, and Attachment Numbering i

! Sequential .1 rabic numbers should be assigned to figures, I

tables, and attachments in separate series. The sequence should correspond with the order of their reference in the

, text. The symbol "#" and abbreviation "No." are unnecessary l and should not be used. The number alone suffices.

Examples: Figure 1, Figure 2, etc.

Table 1, Table 2, etc.

  • Attachment 1, Attachment 2, etc.

4.11.4 Place Keeping Aids Place keeping aids should be used when it is determined to be helpful to ensure that procedural steps are completed or when cross referencing is required.

4.11.4.1 Place keeping aids shall be provided for immediate action steps. This aid will consist of a check-off block (about 3/8" square) at the completien of the immediate action step.

4.11.4.2 Place keeping aids for use during cross referencing will be provided for the control room copy of the ERG manual. This aid will be attached to the binder, and will be used as a marker during transitions from one procedure to another.

5.0 MECHANICS OF STYLE 5.1 Spelling l Spelling should be consistent with modern usage. When a choice of spelling l is offered by a dictionary, the first spelling should be used.

CPSES ISSUE DATE PROCEDURE NO.

OPERATIONS DEPARTMENT ADMINISTRATION MANUAL DEC 2 8198Z ODA - 204 PREPARATION OF EHERGENCY RESPONSE REVISION NO. 2 Page 35 of 44 GUIDELINES ATTACHMENT 2 PAGE 21 0F 27 5.2 Hyphenation Hyphens are used between elements of a compound word when usage calls for it. The following rules should be followed,for hyphenation.

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

5.2.2 Hyphens should te used in the following circumstances:

5.2.2.1 in compound nunerals from twenty-one to ninety-nine; example:

one hundred thirty-four 5.2.2.2 in fractions; examples: one-half, two-thirds 5.2.2.3 in compounds with "self"; examples: self-contained, self-lubricated u

5.2.2.4 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 5.2.2.5 when misleading or awkward consonants would result by joining the words; example: bell-like 5.2.2.6 to avoid confusion with anothe'r word; examples: re-cover to prevent confusion with recover, pre-position to avoid confusion with preposition 5.2.2.7 when a letter is linked with a noun; examples: X-ray, 0-ring, U-bolt, I-beam 5.2.2.8 to separate chemical elements and their atomic weight; examples: Uranium-235, U-235 5.3 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 1 several sentences. Punctuation should be in accordance with the following rules.

5.3.1 Brackets Do not use brackets.

5.3.2 Colon Use a colon to indicate that a list of items is to follow, for example: Restore cooling flow as follows:

v-eeemew w-@* q-em 4N *Ne' &'" "" *'W"*' -

l .

CPSES ISSUE DATE PROCEDURE NO.

OPERATIONS DEPARTMENT ADMINISTRATION MANUAL DEC 2 6 682 ODA - 2 04

PREPARATION M EMERGENCY RESPONSE REVISION NO. 2 Page 36 of 44 l GUIDELINE 5 ~ ~ - -

ATTACHMENT 2 PAGE 22 0F 27 5.3.3 Coman 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 . . . .

5.3.4 Parentheses Parentheses shall be used to indicate alternative itens in a procedure, instruction, or equipment numbers, 5.3.5 Periou Use a period at the (ad of complete sentences and fer '

indicating the decimal placa in numbera.

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

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

5.4.2 Use common usage if it make the procedure easier to understand.

5.4.3 Use words that are concrete rather than vague, specific rather than general, familiar rather than formal, precise rather than blanket.

5.4.4 Define key words that may be understood in more than one sense.

5.4.5 Verbs with specific meaning should be used. Examples are l listed in Table 1.

5.4.6 Equipment status should be denoted as follows:

5.4.6.1 Operable / operability -- These words mean that a system, subsystem, train, component, or device is capable of performing its specified function (s) in the intended manner. Implicit in this definition is the assumption that all necessary attendant instrumentation, controls, normal and emergency electrical power sources, cooling or seal water, lubrication or other auxiliary equipment required for the system, subsystem, train, component, or device to perform its function (s) are also capable of 1 performing related support function (s).

J . _ LL _ ? ~ ~~~~:L LJ:_ _ ~_ _: __

CPSES ISSUE DATE PROCEDURE NO.

OPERATIONS DEPARIMENT ADMINISTRATION MANUAL DEC 2 81982 ODA - 2 04

! PREPARATION OF EMERGENCY RESPONSE REVISION NO. 2 Page 37 of 44 GUIDELINES ATTACHMENT 2 PAGE 23 0F 27 Table 1. Action Verbs Verb Application Allow To permit a stated condition to be achieved prior to proceeding, for example, " allow discharge pressure to stabilice" Check To perform a comparicon with a procedural requirement " Check if S1 can be terlinated" Close To changa the physical position of a mechanical device so tha t

, it prevents physical access or flow or permits passage of electrical current, for example, "close valves ZL-2462A" Complete To accomplish specified procedural requirements.

Decrease Do not use because of oral communication problems. .

Establish To make arrangements for a stated condition, for example,

" establish communication with control room" Increase Do not use because of oral communication problems.

Inspect To measure, observe, or evaluate a feature or characteristic for comparison with specified limits; method of inspection should be included, for example, " visually inspect for leaks" Open To change the physical position of a mechanical device, such as valve or door to the unobstructed position that permits access or flow, for example, "open valve ZL-2459A" Record To document specified condition or characteristic, for example,

" record discharge pressure" Set To physically adjust to a specified value an adjustable feature, for example, " set diesel speed to . . . ' rpm'"

Start To originate motion of an electric or mechanical device directly or by remote control, for example, " start ... pump" i

Stop Tc terminate operation, for example, "stop ... pump" Throttle To operate a valve in an intermediate position to obtain a certain flow rate, for example, " throttle valve ZL-2461A to ..."

CPSES ISSUE DATE PROCEDURE NO.

OPERATIONS DEPARTMENT ADMINISTRATION MANUAL DEC 2 81982 ODA - 2 04 PREPARATION OF EMERGENCY RESPONSE REVISION NO. 2 Page 38 of 44 GUIDELINES ATTACHMENT 2 PAGE 24 0F 27 Table 1. Action Verbs (continued)

Verb Application Trip To manually activate a semi-automatic feature, for example.

" trip breaker ..."

l Vent To permit a gas or liquid confined under pressure to escape at i a vent ... pump" l

! Verify To observe an expected condition or characteristic, for  ;

l example, " verify discharge pressure is stable"  :

i l

l 5.4.6.2 Operating -- This word means that a system, s ubsyst em, train, component, or device is in operation and is performing its specified fur.ction(s), and that " clearances" or other e

l conditions do not prevent it from maintaining tha t service.

5.4.6.3 Available -- This word means that a system, s ubsyst em, train, component, or device is operable

[ and can be used as desired; however, it need not be j operating.

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

5.5.1 Arabic numberals should be used.

5.5.2 For numbers less than unity, the decimal point should be preceded by a zero; for example: 0.1.

5.5.3 The number of significant digits should be equal to the number of significant digits available from the display and the reading precision of the operator.

5.5.4 Acceptance values should be specified in such a way that I addition and subtraction by the user is avoided if possible.

This can generally be done by stating acceptance values as limits. Examples: 510*F maximum, 300 psig minimum, 580* to 600*F. For calibration points, statement of 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 +.

- - - 7 .-_-_ --

CPSES ISSUE DATE PROCEDURE NO.

OPER'ATIONS DEPARTMENT ADMINISTRATION MANUAL DEC 2 81982 ODA - 2 04 PREPARATION OF EMERGENCY RESPONSE REVISION NO. 2 Page 39 of 44 GUIDELINES ~~

ATTACHMENT 2 PAGE 25 0F 2) 5.5.5 Engineering units should always be specified for numerical values of process variables. They should be the same as those used on the control room displays, for example: psig instead of psi.

5.6 Abbreviations, Letter Symbols, and Acronyms 5.6.1 The use of abbreviaticus should be micimized becauce they may be confusing to those who are not thorougnly familiar with them. Abbreviations may be used where necessary to save time and stace, and wh3n their e+cniwg Ls unquestionably clear to

, the iatended reader. Tha full meaning of the abbreviation should be written in af ter the first us of the abbrevictien and whenever in dcubt. Consistency should be maintained thrctghout the procedure.

5.6.2 Capitalization of abbreviations should be unifort. If the l abbreviation is comprised of lowercase letters, it should appaar in lowercase in a title or heading. The period should be omitted in abbreviations except in cases where the omissi on would result in confusion.

5.6.3 Letter symbols may be used to represent operations, quantities, elements, relations, and qualities.

l 5.6.4 An acronym is a type of symbol formed by the initial letter or letters of each of the successive parts or major par;s of a I compound term.

I 5.6.5 Abbrevf y.tions, symbols, and acronyms 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 communications mathematic ideas.

5.6.6 Only those abbreviations, symbols and acronyms that are listed in the Comanche Peak standard list may be used in the ERGS.

6 TYPING FORMAT 6.1 General Typing Instructions For emergency operating procedures, the following general requirement s are to be followed:

6.1.1 Paper size should be 8-1/2 x 11 inches.

l 6.1.2 White, bond paper with printed border should be used.

6.1.3 Procedures are to be typed on an electric typewriter.

6.1.4 Modern, pitch 12 typewriter element is to be used.

l l

. CPSES ISSUE DATE PROCEDURE NC.

OPERATIONS DEPARTMENT ADMINISTRATION MANUAL DEC 2 81982 ODA - 2 04 PREPARATIi ei 0F EMERGENCY RESPONSE REVISION NO. 2 Page 40 cf 44 GUIDELINES ATTACHMENT 7 PAGE 26 0F 27 6.2 Page Arrangement 6.2.1 Page margins are specified by the printed borders. Two type spaces are to be maintained between the text and borders.

6.2.2 Page identification information will be in accordance with Section 3.0.

6.2.3 The S-1/2 inch edges shall constitute top and bottom of pages and text. Tables and figures shall be readable with the page so atranged. Rotation of printed matter should be aveided fer >

emergency operating precedures.

6.3 Breakinc of Vcrds Breaking of words shall be avoided to facilitate operater reading.

6.4 Printed Operator Aids 6.4.1 Figures include graphs, drawings, diagrams, and illustrations.

The following rules are established.

6.4.1.1 The figure number and its title are placed three line spaces below the figure field.

6.4.1.2 The figure number and title should be of modern type, pitch 12.

6.4.1.3 The figure field must not violate specified page margins.

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

6.4.1.5 The essential message should be clear; simple presentations are preferred.

6.4.1.6 Grid lines of graphs should be at least 1/8-ir.ch apart; numbered grid lines should be bolder than unnumbered grid lines.

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

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

  • -e-- - - - + +- , , we 1 e ,y e toe r ~ + w - e a- r, =se .ge . g,-se r=g e te e , -

4 CPSES ISSUE DATE PROCEDURE NO.

OPERATIONS DEPARTMENT ADMINISTRATION MANUAL DEC 2 81982 ODA - 2 04 PREPARATION OF EMERGENCY RESPONSE REVISION NO. 2 Page 41 of 44 GUIDELINES ATTACHMENT 2 PAGE 27 0F 27 6.4.1.9 In general, items within the figure should be labeled. Typed labels should use modern type, pitch

12. Handwritten labels should be printed, using all capitals, with letrers and numbers at least 1/8-in ch high.

, 6.4.1.10 AJ1 lines in figures should be reproducible.

6.5.2 Tables should tv typad using the following rules.

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

6.5.2.2 The table number and title should be located above the table field cod three line spaces below preceding text.

6.5.2.3 A heading should be entered for each column and centered within the column; the first letter of wordLs in the column headinEs should be capitalized. "

6.5.2.4 Horizontal lines should be pl ced above and below the column headings; vertical lines, while desirable, are not necessary or required.

l l 6.5 Use of Foldout Pages When used, a foldout page is treated as a single page. It should l

f ollow 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 sear of the fold.

6.6 Use of Oversized Pages Oversize pages should not be used. They should be reorganized or reduced to a standard page. If this cannot be done, a foldout page should be used.

6.7 Use of Reduced Pages Reduced paget should be avoided whenever possible. Final size of ,

reduced pages should be st:ndard page size. Reduced pages should be readable.

7 REPRODUCTION Reproduction will be done on a standard copier, single-sided copy only.

The exception is when a figure or graph is to be printed in the reverse of a preceeding page.

.~ - - . - . .

~ ~

CPSES ISSUE DATE PROCEDURE NO.

OPERATIONS DEPARTMENT ADMINISTRATION MANUAL ODA - 2 M deb 2 81582 PREPARATION OF EMERGENCY RESPONSE REVISION NO. 2 Page 42 of 44 GUIDELINES ATTACHMENT 3 PAGE 1 0F 2 CPSES EMERGENC1 RESPONSE DATE: Page 1 of 2 GUIDELINE VERITICATION CHECILIST GUIDELINE NAME: ERG NO.: ERG REV NO.?

This checklist shall be used to establish the accuracy of information and inetructional stace of the ERGS. to determine that the procedures can be accurately and efficiently carried out, and to deas,nstrate that the procedares

! are adequate to mitigate the consequences of transients and accidents. The verificatior may be acccaplished by ainulator exercises, control room j valk-throughs or ')esk top reviews. Any rina, combinatioca or all methcds as y be - i

used. Indicate the method (s) used below.

l I i

[] Kimulator Exercising f t

[] Control Room Walkthrough

[] Desk top review 1

Criteria _

Reviewer /dt te

l. The ERG accurately reflects the information presented in the technical gut (elines. /
2. The ERG is written in accordance with the writer's guide. /
3. The ERG has been walked through the control roca ted can be followed without confusion.
delays or errors. /

l l 4 Controls, equipment and indications that are referenced in the ERC are available in the plant, use the same designation, use the same units, and operate (or will operate) as specified in the procedure. /

5. The level of detail is sufficient to .silow the least qualified operator on the shif t crew to use it effectively. /

ODA-204-1 i

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

~

. CPSES ISSUE DATE PROCEDURE NO.

OPERATIONS DEPARTMENT ADMINISTRATION MANUAL DEC 2 81982 ODA - 2 04 PREPARATION OF EMERGENCY RESPONSE REVISION NO. 2 Page 43 of 44 GUIDELINES ATTACHMENT 3 PAGE 2 0F 2

@SES DIERGENCY REFPONSE DATE: Page 2 of 2 CUIDELINE YERITICATION CHECKLIST GUIDELINE NAME: ERG No.: ERG RIV No.:

6. The minimum shif t crew can complete the ERG without outside assistance. /
7. The ERG has been verified agstr.dt the Leergency Response Guideline Transition Flow Char . / -

Comments :

/

Comment Resolution:

4

/

l CBECKLIST REVIEWED (OPERATIONS SUPERINTENDENT)

/

ODA-204-la

~

_:- _ ~ ~

_ - -- T_':' -~~~'.L_ . ~ -.

CPSES ISSUE DATE PROCEDURE NO.

OPERATIONS DEPARTMENT ADMINISTRATION MANUAL ODA - 2 %

DEC 2 81982

~

PREPARATION OF EMERGENCY RESPONSE REVISION NO. 2 Page 44 of 44 GUIDELINES ATTACHMENT 4 PAGE 1 0F 1 WSES EMERGENCY RESP 0PSE DATE: Page 1 of I CUIDELINE IMPROVEMENT RECOPMENDATION ERG MA O ERG NO.: ERG REV No.:

1. The following change (s) are recoreended to improve the Comanche Peak ERGS:

1 I

i

2. Justification /Raason for Change:

I Name of person reconnending change

3. Evaluation (incorporate /do not incorporate) and Justification:

Operations Engineer ODA-204-2

. . , , . . . . . . . . . - - . , , .

Retrieved from "https://kanterella.com/w/index.php?title=ML20064J983&oldid=3077659"