TXX-4216, Rev 3 to Procedure ODA-204, Preparation of Emergency Response Guidelines
| ML20090C418 | |
| Person / Time | |
|---|---|
| Site: | Comanche Peak  |
| Issue date: | 07/06/1984 |
| From: | Schmidt H TEXAS UTILITIES ELECTRIC CO. (TU ELECTRIC) |
| To: | Youngblood B Office of Nuclear Reactor Regulation |
| References | |
| TASK-1.C.1, TASK-1.C.8, TASK-TM ODA-204, TXX-4216, NUDOCS 8407130292 | |
| Download: ML20090C418 (64) | |
Text
'
P c, ..
{ COMANCHE PEAK STEAM ELECTRIC STATION OPERATIONS DEPARTMENT ADMINISTRATION MANUAL ,
' Y TT ' ' -
.-~.,. .m" "
l . id .l .\ .1.11i '
. !.; i . I !s i
, ,7
'<g '4 : .l i . . . . :. , 1 . ' p ,
PREPARATION OF EMERGENCY RESPONSE GUIDELINES
(
PROCEDURE NO. ODA-204 REVISION NO. 3 SAFEIMBR SUEMITTED BY -
DATE $!29/P4 OPERATIONS SUPERINTENDENT e .
l APPROVED BY M~J "' DATE &?, M L xaNicER. - T oeE.u noNS
./
8407130292 040706 PDR ADOCK 05000445 F PDR l gl
r CPSES ISSUE DATE PROCEDURE NO.
OPERATIONS DEPARTMENT ADMINISTRATION MANUAL A-204 JUN 0 71984 PREPARATION OF EMERGENCY RESPONSE GUIDELINES REVISION No. 3 PAGE 2 0F 63 <
1.0 Purpose This procedure describes the method used to develop Emergency Response Guidelines from the Generic Guidelines provided by Westinghouse. This
. procedure also prescribes the format in which the CPSES Emergency' ,
Response Guidelines (ERG) shall be prepared and provides guidelines 4 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 tesponding to plant emergency conditions. This procedure becomes effective when issued.
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) e Function Restoration Guideline (FRS. FRP. FRC FRI. FRH. FRZ) 3.2 Emergency Operating Procedures. The E0Ps provide the operator with procedural guidance sutficient to effectively diagnose an event and directs the operacor 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 Enernoncy Contingency Action Procedures. The Emergency Contingency Action procedures provide contingency actions for equipment failures and transitions to Function Restoration Guidelines when required.
k.
(
CPSES ISSUE DATE PROCEDURE NO.
OPERATIONS DEPARTMENT ADMINISTRATION MANUAL g Q 7 jgg4 09A-204 PREPARATION OF EMERGENCY RESPONSE GUIDELINES REVISION NO. 3 PAGE 3 0F 63 3.5 Critical Safety Function Status Trees. Critical Safety function Status trees (CSFST) provide the operator 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 barriers to release of radioactivity, the fuel cladding, 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 Suberiticality (S-Series) e RCS Integrity (P-Series) e Core Cooling (C-Series)
( e e
e RCS Inventory (I-Series)
Core Heat Sink (H-Series)
Containment (Z-Series) 3.7 Issue Date - The issue date specifies when each CPSES Emergency Response Guideline becomes effective.
3.8 Validation - The demonstration that tasks specified in the technical guidelines are sufficient to accomplish the objective of the guideline.
3.9 Verification - The assurance that plant specific technical data is correctly transcribed into the WOG generic guidelines to provide accurate and usable CPSES Emergency Response Guidelines.
4.0 Instructions 4.1 Cuidance on the une of Emergency Responso Guidelines 4.1.1 Ceneral A set of procedures shall be prepared which provide the operator 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 proceduren is composed of the
( following
CPSES ISSUE DATE PROCEDURE NO. t OPERATIONS DEPARTMENT ADMINISTRATION MANUAL A-204 l JtJN 0 71984 PREPARATION OF EMERGENCY RESPONSE GUIDELINES REVISION NO. 3 PAGE 4 0F 63 e Emergency Operating Procedures (EOP) e Emergency Operating Sub-Procedures (EOS) [
e Emergency Contingency Actions (ECA) e Function Restoration (FRS, FRP, FRC, FRI, FRH, FRZ) j Figure 1 provides a pictorial representation of how tilese 5 procedures are collectively used to restore the plant to I safe conditions following an upset.
l noen optut!:= ;
i I
l l
auan !
, i 9 '
vt!
es go tarp : O!M90$t , erstent ,
[
o f
A,.
y lt
, l i IAIII '
vil l
, 't!
il i s i vit !
, t Actawat!(
ACIC41 I I
i vil f ; l ;
tvt .o
- 3!Maott3 l
i I l'
4 q
l j ,i ,i t
,e , l
,8188!!!
46;;,, :
J l l i
( , ,,
IIIsURt 1
~
PttCliCY Rt!7 CMC '.UICtL!Nt1172gCitat [
i
. , - , , _ . - , _ . . . , . , _ , , . _ , , , , . _ _ - = - . . _ _ _ _ _ - - - _ . _ . , _ . _ _ , . , , - - _ _ . . _ , - , . .
. ~, i
r a ,,
i CPSES ISSUE DATE PROCEDURE NO. I OPERATIONS DEPARTMENT ADMINISTRATION MANUAL ODA-204 1 JIJN071984 I PREPARATION OF EMERGENCY RESPONSE GUIDELINES REVISION NO. 3 PAGE 5 0F 63 4.1.2 Emergency Operatina 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. Thu E0Ps are initially entered to 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 l
diagnosed, the E0P will direct the operator to enter an EOS procedure for recovery. If the event is not immediately diagnosed, the operator returns to the diagnostic steps in the E0P and repeats specified actions. l As before, he concurrently monitors the critical safety I function status trees. The ECA procedures provide I instructions for contingency actions and will be entered I as directed by the E0Ps.
4.1.3 Critical Safety Function Status Trees w These status trees provide the operator with a systematic ,
and explicit means for determining the safety status of I his 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 l of safe plant conditions throughout the recovery. This l concurrent use of status trees and the appropriate l Emergency Response Guidelines also provides a method for 1 identifying the type of critical safety function challenge independent of specific event diagnosos 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 i coping with subsequent / multiple failure situations. l The status treen are intended to serve two purposes:
- 1) Cencral nurvalliance under all sets of unusual or abnormai conditions that can lead to or result from initiation of safety injection
- 2) Direct onorator cuidanen in those rare events that go f beyond the design basis of the Ongineered Safeguards
( Systems and the Emergency Response Guideline. and Emergency Contingency Actions.
e 1
CPSES ISSUE DATE PRCZEDURE NO.
OPERATIONS DEPARTMENT ADMINISTRATION MANUAL DA-204 JUN 0 71984 PREPARATION OF EMERGENCY RESPONSE CUIDELINES REVISION NO. 3 PAGE 6 0F 63 J l
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 Shift 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 l trees are displayed on the control room Safety Assessment System (SAS) and should be continuously available. In the unlikely event that SAS is inoperative during an accident a manual back-up system will be provided. This backup system consists of status tree cards mounted to a solid backboard structure to allow flipping through each critical safety function status tree in priority of use.
After the status of each individual safety function is determined, a tear-off tablet status sheet (see example below) attached to the bottom of the solid backboard is marked and given to the operator implementing the ERG's.
Time RED ORANGE YELLO'4 GREEN SUBCRITICALITY FRS-0.1 FRS-0.2 FRS-0.2 CSF !
SATISFIED l
CORE COOLING FRC-0.1 FRC-0.2 FRC-0.3 CSF SATISFIED FRH-0.2 IIEAT SINK FRH-0.1 FRil-0.3 CSF FRil-0.4 SATISFIED FRH-0.5 RCS INTEGRITY FRP-0.1 FRP-0.1 FRP-0.2 CSF SATIGFIED CONTAIUMENT FRZ-0.1 FRZ-0.1 FRZ-0.3 CSF FRZ-0.2 SATISFIED FRI-0.1 INVENTORY FRI-0.2 CSF FRI-0.3 SATSIFIED
I CPSES ISSUE DATE PROCEDURE NO. l OPERATIONS DEPARTMENT ADMINISTRATION MANUAL ODA-204 JUN 071984 PREPARATION OF EMERGENCY RESPONSE CUIDELINES REVISION No. 3 PACE 7 0F 63 In applications of this type, use of the Status Trees l would serve as a prudent safeguard against an unrecognized degradation of an already abnormal situation by random or common mode failures of safety equipment or by operator error. No recourse by the opeators to the Function , i Restoration Guidelines and Emergency Contingency Actions I would be necessary. Prioritization of operator actions would be directed by existing Emergency Responso Guidelines and Emergency Cont.ingency Actions. However, the non-operating user of the Critical Safety Function Status Trees might well use the Function Restoration Guidelines and the prioritization guides incorporated in the Status Trees to verify that the course of action being followed by the operator la consistent with the status of the plant. The " direct operator guidance" aspect of Critical 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 several plant systems, an ongoing transient has entered a domain in which the Emergency Response Guidelines and Emergency Contingenc/ Actions may not be reliable guides and available plant systems may have to be
{ used under direct operator control to maintain the l Critical Safety Functions 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 of prioritiration of operator reponse are invoked to direct the operators to the appropriate Function Restoration Guidelines in order to stabilize aid improve the plant status. Thereafter, the I
plant status would be reevaluated portodically and as the set of status indicators changes to reflect changing plant status, the operator would be directed to other Function l Restoration Guidelines or Emergency Peoponse Guidelines to
- treat less serious challenges to barrier integrity or to l respond to new challenges. Concurrently with those l Critical Safety Function oriented activities, it is l expected that the operators would attempt by other methods to diagnose the plant status in terms of failed equipment and to initiate remedial measures.
1 l
L 1
4 ..
1
~
i CPSES ISSUE DATE PROCEDURE NO. f OPERATIONS DEPARTMENT ADMINISTRATION MANUAL JUN 071984 #^-20' !
( i PREPARATION OF EMERGENCY RESPONSE CUIDELINES REVIS!0N NO. 3 PACE 8 0F 63 4.1.4 Funetton Restorstinn ProceAntan ,
) These procedures will provide oretator 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 certain cases it is possible to enter them t 4 '
directly from the Emergency Response Guidelines via l identified transitions that account for specific l l % :ingencies. These Function Restoration Guidelines i l provide guidance for maintainte.g the plant in a safe state !
4 without regard to initiating event or combinations of ;
i subsequent or consequentbd failures,af ter event '
diagnosis. In sont cases the operator can expect to recover the plant using only the tMP, EOS or Et'A precedures. However, the avaihtalles of the function !
Restoration Guidelines provides adettchnul guidance for f
4 situations whete disanosis cannot l's made, or where !
I' subsequent / multiple f ailures nake it impnezible to recover I the ,*1 ant by use of.the Emergency Operating Procedures. (
4 i t
( 4.2 Prepararinn af Plant 8pectfte Technteal Coldetineg 4.2.1 ceneral j
/
j Generic technical guidelinei are prepared for all of the i i Emergancy Neaponse Guidelines. These generic guide 11res i provide a complete and documented analytical bas w tot i each of the proceduren. The listed process is illustrated !
in figure 2 and is used to ensure the WG seneric l
, guidelines are applicable' to Cemanchv t'esk. !
j 4.2.2 .Davelnement of Plant Mpanffte hary 4.2.2.1 Each Cf8E8 plant specifto technical guideline is i based on the Westinghouse Owners Group dangric 1
Auldelines. The WO lMaric videltro shall be -
reviewed to determinn which data must be Sade !
plant specific. 1his reytev shall be rho bauts for the developport til a dComanche Pe.ek Data !
, fackage" for each guideline. Attachmout I indicates the immat for the Data Pac'vage. !
i f
I l
!l 1
}
4 I
f 3
._ - _ _ _ - _ . _ - . - _ _ _ _ _ _ _ _ . _ _ _ _ - _ _ _ . L
CPSES ISSUE DATE PROCEDURE NO.
OPERATIONS DEPARTMENT ADMINISTRATION MANUAL gal 071984 ODA-204 PREPARATION OF DIERGENCY RESPONSE C.U1DELINES REVISION NO. 3 PAGE 9 0F 63 4.2.2.2 To ensure the WOG Generic Guidelines are adequate for the CPSES plant specific guidelines A " Task Analysis Package" is compiled for each step and procedure to ensure all assumptions and requirements stated in the generic guideline have not been compromised.'
Attachment 2 indicates the format for the task
, , analyste package.
4.2.2.3 The Generic Plant design is compared to the Comanche Peak plant design and any differences between the two plants is analysed to ensure that the WOO generic technical guidelines are not compromised when making them plant specific.
Attachment 3 indicates the format for the generic comparison packags.
PICURE 2 C7lts Compaal104 W 4tNEA!C GU!OfLINil : 1 C'entil 43%P PACU48 o
CCMANCMt P(At
- TAlt ANALV$ll PActAGt o
~
9LANT $9ttiftC ftCNetCAL % CafA g CCMANCHE P(At Gul0tLINtl VtliflCAf!CN OAfA #AC O Gt 9
4
'" PLANf 1PtClFIC CCNf80L aCCM AND IflftM CCNFl%URAflCN o ,
ysLt0Aff0 (CNftet see PLANT 17tCIFIC & 'e4Lt.*dOVQM AND (CP's vttiflCAflCN CNtCELilf
r CPSES _
ISSUE DATE PROCEDURE NO.
OPERATIONS DEPARTMENT ADMINISTRATION MANUAL ^-204 M 07 m PREPARATION OF EMERGENCY RESPONSE GUIDELINES REVISION 110. 3 PAGE 10 0F 63 4.2.3 Validation of the technical cuidelines 4.2.3.1 The generic technical guidelines are valida'ted by the Westinghouse Owner's Group. This validation applies to the Comanche Peak Technical Guideline _s if only plant specific data is inserted and no substantial changes are made
. to the basic guideline.
4.2.3.2 To ensure the. validation process is not compromised, the person responsible for inserting plant specific data has determined the effect, if any on the validation by:
A) Performing an engineering evaluation of the generic plant design compared to CPSES plant specific design. The evaluation considers the CPSES FSAR, Technical Specifications, Systeza Technical Descriptions, Elementary Wiring Diagrams, Flow Diagrams, and Instrument and Control Diagrams. Any design differences identified during this process C are evaluated and te'ennical justification documented on Attachment 3. Each discrepancy is evaluated with respect to the generic guideline basis background document to ascertain if it compromises the safety of the plant anc./or function of the guideline.
The technical justification 9rovides the basis for the plant-specific approach which vill ensure the safety of the plant.
B)' Complet'ing a Data and Task Analysis package as shown'on Attachments 1 and 2. These packages ensure the following:
- 1) 'All plant specific data is within the e'ange specified in the generic technical guidhltnes.
- 2) All plant specific control /
instruuentation meet the analyzed ranges specified in the generic technical guidelines.
- 3) .All plant specific guidelines do not _
~
compromise the generic technical guideline objectives.
' , i CPSES ISSUE DATE PROCEDURE NO.
OPERATIONS DEPARTMENT ADMINISTRATION MANUAL ODA-204 JUN 0 71984
( PREPARATION OF EMERGENCY RESPONSE GUIDELINES REVISION NO. 3 PAGE 11 0F 63 5
4.2.4 Documentation The Plant Specific Technical Guidelines contain the following elements:
I e Generic Technical Guidelines e Comanche Peak Data Package e Comanche Peak Task Analysis Package e Comanche Peak Generic Comparison Package ,
e Verification the Plant Specific Data does not alter ,
the Generic Analysis i Together, these documents provide a complete and documented plant specific analytical basis for each ;
guideline. i 4.2.5 Instructions for Completing the Comanche Peak Data Package j
( 4.2.5.1 Cover Page !
A) Title - as indicated on Attachment 1 B) Guideline No. - Enter the Generic Guideline No.
C) Revision No. Date - Enter the Generic Guideline Revision Date.
I D) Enter the name of the Guideline e.g. Reactor trip or Safety Injection.
l E) Submitted By - Signature of submitter and submittal date.
F) Reviewed by - Signature of reviewer and date.
L G) Approval by - Signature of approver and date.
l b
CPSES ISSUE DATE PROCEDURE NO.
OPERATIONS DEPARTMENT ADMINISTRATION MANUAL A-204 07 M PREPARATION OF EMERGENCY RESPONSE GUIDELINES REVISION NO. 3 PAGE 12 0F 63 4.2.5.2 Second Page ;
A) Heading - as indicated on Attachment 1.
B) Guideline Name - Enter name.
C) Plant Specific Revision No. - Enter revisior.
number of the Comanche Peak ERG that is supported by th,is data package.
D) Generic Guideline Revision Date - Enter date listed on Generic Guideline.
E) Guideline No. - Enter Comanche Peak Guideline No.
F) Page No. - Enter data package page number as part of the entire data package.
G) 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 data. A space has been provided for the engineer's printed name.
H) 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 engineer verifying the data. A. space has been provided for the engineer's printed name.
- 4.2.5.3 Data Pages l
A) Header data - Same as section 4.2.5.2 B) Guideline Step No. - Enter the step number requiring Comanche Peak specific data.
t C) Plant Specific Data Required - Enter the l Plant Specific data, l
l D) Source / Justification / Calculation - Enter the source of the data (PSAR, ccmponent technical manual, Technical Specification,
(, etc.) along with necessary justification or calculations.
t
CPSES ISSUE DATE PROCEDURE NO.
OPERATIONS DEPARTMENT ADMINISTRATION MANUAL ODA-204 JUN 0 71984
( PREPARATION OF EMERGENCY RESPONSE GUIDELINES REVISION NO. 3 PAGE 13 0F 63
- 4.2.6 Instructions for completing the Comanche Peak Task Analysis package 4.2.6.1 Cover Page A) Title as indicated on Attachment 2.
B) Guideline No - Enter the Comanche Peak guideline No. ,
C) Revision Date - Enter the Comanche Peak revision date.
D) Enter the name of the Guideline e.g.
Reactor Trip or Safety Injection.
E) Submitted by - Signature of submitter and submittal date.
F) Reviewed by - Signature of reviewer and date.
. G) Approved by - Signature of approver and date.
4.2.6.2 Second Page A) Heading - as indicated on Attachment 2.
B) Guideline Name - Enter title name.
l C) Guideline No. - Enter Comanche Peak Guideline number.
D) Plant Specific Revision No. - Enter revision number of the Comanche Peak ERG that is supported by the Task analysis package.
l E) Generic Guideline Revision Date - Enter date l listed on Generic Guideline.
F) Step - Enter Specific step from the Comanche i Peak Guideline. If an analysis is done on the response not obtained column, then the step number followed by a letter designator
! will be inserted.
l C) Requirement - Enter what specifically is k_ required by the step e.g. pressurizer level increasing.
l
v .
CPSES ISSUE DATE PROCEDURE NO.
OPERATIONS DEPARTMENT ADMINISTRATION MANUAL DA-204 M 0 71984 PREPARATION OF EMERGENCY RESPONSE GUIDELINES REVISION No. 3 PAGE 14 0F 63 H) Control - List any controls that would be needed to accomplish the requirement above.
I) Indication - List any indications that would be needed to accomplish the requirement <
above.
J) Board Location - List location of Control /Indicat, ion on the main control board.
K) Feedback - List actions if the requirement above is not met.
L) Task Worksheet Completed - check when a worksheet has been completed.
M) Step Justified by - Check off whether the step was analyzed for plant specific data or if the Generic WOG background documentation provides justification.
( N) Comments - List any applicable comments which pertain to this step.
- 0) Completed by - Signature of person completing worksheet.
P) Reviewed by - Person reviewing worksheet shall sign and date.
Q) Page - Place page number.
4.2.6.3 Third Page A) Header Data - Same as section 4.2.6.1.
B) Instrument - List instrumentation required to meet the requirement listed on the Task analysis worksheet.
i C) Required Characteristics - List what response is needed by the indicator to meet the WOG generic guideline requirement.
D) Completed by - the person completing the l data should sign and date the form.
- km l
L
I CPSES ISSUE DATE PROCEDURE NO.
OPERATIONS DEPART!!ENT ADMINISTRATION MANUAL Jyg Q 7 ]Qg4 ODA-204
/
\
PREPARATION OF EMERGENCY RESPONSE GUIDELINES REVISION NO. 3 PAGE 15 0F 63 E) Instrument Number - List all indication numbers available to meet the required characteristics.
F) Units - List units specified on indication.
G) Scale Range - List minimum to maximum range on indication.
H) Increments - Give range between markings.
I) Tolerance - List total error that the indication can have.
J) Post Accident Monitoring - check whether the indication is qualified during accident conditions.
K) References Used - List any information that was used to compile this worksheet.
( L) If the instrumentation meets the requirements specified in the generic guideline, then an Engineer shall check yes and sign the form as complete.
M) Comments - List any applicable comments.
N) Procedures Reference - All procedures using this instrumentation will be listed here.
4.2.6.4 Forth Page A) Header Data - Same as section 4.2.6.1 B) Control - List all controls required to meet the requirement listed on the task analysis worksheet.
l C) Required. Characteristics - List what response is needed by the control to meet
~
l
'._ the WOG generic guideline requirement. '
l
, D) Completed by - the person ccepleting the data shall sign and date the form.
E) Control Number - List all control numbers e available to meet the required
[ (. characteristics.
l
CPSES ISSUE DATE PROCEDURE NO.
OPERATIONS DEPARTMENT ADMINISTRATION MANUAL DA-204 JUN 0 71984 PREPARATION OF EMERGENCY RESPONSE GUIDELINES REVISION NO. 3 PAGE 16 0F 63 F) Position - List what positions the control switch can be placed in.
G) Indication - List what indication are available for the particular control. ,
H) Comments - List any applicable comments. ;
, r
- I) References Used - List any information that was used to compile this worksheet. !
J) If the control meets the requirements specified in the generic guideline, then an Engineer shall check off yes and sign the form as complete.
K) Comments - List any applicable comments.
r L) Procedures Referenced - All procedures using this instrumentation will be listed here.
( 4.2.7 Instructions for completing the Generic Plant Comparison Package 4.2.7.1 Cover Page A) Revision Date - Enter the Comanche Peak Revision date.
B) Submitted by - Signature of submitter and submittal date.
C) Reviewed by - Engineer Reviewing Package should sign and date.
D) Approved by - Operations Engineer should sign and date.
4.2.7.2 Sec'ond Page A) System - List System that is being compared.
B) CPSES Differences - List the differences found between CPSES and the Generic Plant, j C) Justification completed - check off when a justification sheet has been completed.
k.
i l
L
h CPSES ISSUE DATE PROCEDURE NO.
OPERATIONS DEPARTMENT ADMINISTRATION MANUAL ODA-204 JUN 0 71984 PREPARATION OF EMERGENCY RESPONSE GUIDELINES REVISION NO. 3 PAGE 17 0F 63
.4.2.7.3 Third Page A) Difference Description - Describe specifically the difference between the Generic Plant and CPSES.
B) Justification - Explain the reasoning that this difference will not affect the ERG objective and how this difference is compensated.
C) Completed by - sign and date.
D) An Engineer shall sign the next two slots af ter reviewing the justification and i agreeing with the statements.
E) Generic Procedure Reference - List all procedures and step numbers that have the difference in design listed.
F) Comments - List any applicable comments. ,
4.2.8 Incorporation of changes When a revision is made to the plant specific ERG procedures due to either submittal of Guideline Improvement Recommendation sheets or through Temporary Changes, the documentation process for all changes to existing procedures are treated in accordance with steps 4.2.1 through 4.2.4 of this procedure. The same applies if new or revised WOG Generic Technical Guidelines are issued.
4.3 Preparation of Emergency Ooerating, Emergency Ooerating Sub-Procedures, Emergency Contingency Action and Function Restoration Procedures P
The Emergency Operating, Emergency Operating Sub-Procedures, Emergency Contingency Action and Function Restoration procedures are prepared using the plant specific technical guideline as the technical basis for the procedure. Attachment 4 provides instructions for translating this technical information into a procedure acceptable for use in the control room.
CPSES ISSUE DATE PROCEDURE NO.
OPERATIONS DEPARTMENT ADMINISTRATION MANUAL ODA-204 JUN 071984
( PREPARATION OF EMERGENCY RESPONSE GUIDELINES REVISION NO. 3 PAGE 18 0F 63 4.4 Verification of Emergency Response Guidelines Each procedure shall be verified to ensure the procedure is accurate and useable. The verification process will include, as r applicable, the following and will be documented on Attachment 5 when completed. An Attachment 5 check list for each procedure will be filed with the Comanche Peak Data Package.
4.4.1 Simula' tor Exercising - If simulator time is available prior to the initial operation of CPSES, the simulator exercising box on Attachment 5 should be checked to verify the procedure utilized accomplished the objective of the ERG. When the CPSES plant specific simulator becomes available, each revision of the ERG procedures will be verified on the simualtor to ensure it accomplishes the objective of the ERG and maintains the plant in a safe and stable condition.
4.4.2 Control Room Walkthrough - Each ERG will be walked through the control room and/or plant specific simulator. The walkthrough is to ensure nomenclature on handswitches, annunciators, monitor light boxes, and/or any verbage used C , in the main control room is identical to that of the ERG procedure. The Control Room Walkthrough box should be i
checked on Attachment 5 when completed.
4.4.3 Desk Top Review - The desk top review box should be checked to denote the data package for each procedure has been completed and filed with the procedure.
l 4.5 Verification Criteria 4.5.1 Attachment 5, No. 1 - The reviewer is to sign and date confirming the ERG has been written in accordance with the
, generic procedure and procedure data package. This verification is a step-by-step review of the generic WOG guideline background basis document versus the plant specific ERG procedure to ensure the intent of the step l was not compromised when made plant specific.
4.5.2 Attachment 5, No. 2 - The reviewer is to sign and date confirming the plant specific ERG has been written as l depicted in the ERG Writers Guide, Attachment 4 of this procedure. This review is to ensure all ERG's are written consistently, with good human factors principles.
l 1
CPSES ISSUE DATE PROCEDURE NO.
OPERATIONS DEPARTMENT ADMINISTRATION MANUAL "^- '
07 W
(
PREPARATION OF EMERGENCY RESPONSE GUIDELINES REVISION NO. 3 PAGE 19 0F 63 4.5.3 Attachment 5, No. 3 - The reviewer is to sign and date confirming the plant specific procedure has been walked through the control room verifying that the procedure can be followed by a newly licensed operator without confusion, delays or errors. This verification should be completed by a licensed Reactor Operator or a licensed Senior Reactor Operator.
4.5.4 Attachmest 5, No. 4 - The reviewer is to sign and date confirming the plant specific design has been verified that it is not different from that which was used in the generic plant design. The plant specific design will be ;
compared to the generic plant design delineated in the WOG comparison package. Any difference will be recorded in the comments section and evaluated to insure that the differences do not compromise the intent of the procedure.
4.5.5 Attachment 5, No. 5 - The reviewer is to sign and date confirming the ERG is sufficient to allow the least qualified (newly licensed) operator to use it effectively. l This verification should be completed by a licensed Reactor Operator or a licensed Senior Reactor Operator.and
( is based upon the reviewer's past experience.
4.5.6 Attachment 5, No. 6 - The reviewer is to sign and date confirming the plant specific pro'cedure has been verified by a control room walkthrough and/or simulator exercise and that the minimum shift crew complement, as delineated in ODA-102 Attachment 1, can successfully complete all steps within the plant specific ERG.
4.5.7 Attachment 5, No. 7 - The reviewer is to sign and date ,
confirming the plant specific procedure has been verified against the ERG transition flev chart provided by the WOG.
This process is to verify that transition from one procedure to another can be done accurately and in a timely manner.
CPSES ISSUE DATE PROCEDURE NO. .
OPERATIONS DEPARTMENT ADMINISTRATION MANUAL ODA-204 JUN 0 71984
( '
PREPARATION OF EMERGENCY RESPONSE GUIDELINES REVISION No. 3 PACE 20 0F 63 4.6 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 mecha'nism for feedback to. incorporate procedure improvements. The training will be a e mbination of classroom lectures, self study and control room walk-throughs of the actual procedures. Attachment 6 is the form used for incorporating procedural improvements identified through the training program.
4.7 Guideline Improvement Recommendations When a change is needed to an existing Plant Specific Guideline that does not change the intent of the procedure or does not need to be made immediately, Attachment 6 should be completed and sent to the Operations Department for review and evaluation. If approved the change will be incorporated in accordance with
{ section 4.2.8 of this procedure in the next revision.
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" i 5.3 STA-202, " Preparation, Review, Approval and Revision of Station I
Procedures" 5.4 ODA-201, " Preparation of Integrated Plant Operation Procedures" 5.5 ODA-202, " Preparation of System Operating Procedures"
! 5.6 NUREG - 0899, Guidelines for the preparation of Emergency
, Operating Procedures l
l
CPSES ISSUE DATE PROCEDURE NO.
OPERSTIONS DEPARTMENT ADMINISTRATION MANUAL ggg7jgg4 ODA-204 ,
( 5 PREPARATION OF EMERGENCY RESPONSE GUIDELINES REVISION NO. 3 PAGE 21 0F 63 ,
i 6.0 Attachments t 6.1 Attachment 1, Comanche Peak Data Package ,
6.2 Attachment 2, Task Analysis Package '.
6.3 Attachment 3, Comparison between Generic and CPSES
~
6.4 Attachment 4,' Writer's Guide -
6.5 Attachment 5, Procedure Verification Checklist 6.6 Attachment 6, Procedure Improvement Recommendations
(: -
e 1
CPSES ISSUE DATE PROCEDURE NO.
OPERATIONS DEPARTMENT ADMINISTRATION MANUAL ODA-204 i.
PREPARATION OF EMERGENCY RESPONSE GUIDELINES REVISION NO. 3 PAGE 22 0F 63 ATTACHMENT 1 PAGE 1 OF 3 a
COMANCHE PEAK STEAM ELECTRIC STATION DERGENCT RESPONSE GUIDELINE DATA PACKAGE DATA PACKAGE (4.2.5.1.A)
GUIDELINE NO. (4.2.5.13)
REVISION DATE (4.2.5.1C)
NAME (4.2.3.1D)
SczMITTED BY (4.2.5.tE) DATE REVIE*IED BY (4.2.5.1F) DATE r.:.6 R.f.la APPROVD !Y ff. 2.5.lci DAT!
OPERAILLN5 f.GR.11R ODA-204-3
. ___. .- _ = _ - . _ ~ _ ~ . . _ - - - - - _ . . _ - _ . . . - -
D e i
~CPSES ISSUE DATE PROCEDURE NO. !
OPERATIONS DEPARTMENT ADMINISTRATION MANUAL ODA-204 !
JUN 0 71984 !'
k.
PREPARATION OF EMERGENCY RESPONSE GUIDELINES REVISION NO. 3 PAGE 23 0F 63 [
ATTACHMENT 1
- PAGE 2 OF 3 k
i CPSES PIRIT SPECIFIC GUIDELINE NO. ;
DtERGENCY RESPONSE CUIDELINE DATA PACKACE REVISION NO. (4.2.5.2.E) (
.- REVISION DATE PAGE of CUIDELINE NAME: (4.2.5.2.28) (4.2.f.2.D) (4.2.5.2F) f
- Y l
- 1. Data on pages 3 through of this data package has been made specific to the Comanche Peas aestan and does not comproatse the f generic technical basis for this guideline.
Comments: .
I i
l (4.2.5.2c)
[
Signature cate Print name og Engineer entertog asca l
- 2. Data on pages 3 through of this data pedage has been !
verified as specific to tne Comanche Peak design and does not '
compromise the generic technical beats for this guideline. ,
'I Consents /brief description of verifiestion process 1
I (4.2.5.2.3)
$1gnature 4 ace Petat name oc engineer vertsying Jaca i ODA-204-3a 6
i.
, . - , .-.__- y_. _ _ , , , . . , .__--.,_,m .
._._.._,.._,c_., ,_.,,,_,wmm,r,,_, _ , _ . _
_ , . _ . _ - . _ _ _ _ _. - .-.,__ w
CPSES ISSUE DATE PROCEDURE NO.
OPERATIONS DEPARTMENT ADMINISTRATION MANUAL A-204 JUN 0 71984
(
PREPARATION OF EMERGENCY RESPONSE GUIDELINES REVISION NO. 3 PAGE 24 0F 63 ATTACHMENT 1 PAGE 3 0F 3 4
CPSES PI.A.VI SPECIFIC CUIDELINE NO.
EMERGENCY RESPONSE CUIDELINE DATA PACKAGE REVISION No.
CUIDELINE : REVI$IONDATE PAGE of Guideline Step No. Plant Specific Source / Justification /Calculatione Data Required (4.2.5.38) (5.2.5.3C) (4.2.5.30) n i
ODA-204-Jb
CPSES ISSUE DATE PROCEDURE NO.
OPERATIONS DEPARTMENT ADMINISTRATION MANUAL DA-204 M 071984 PREPARATION OF EMERGENCY RESPONSE GUIDELINES REVISION NO. 3 PAGE 25 0F 63 ATTACHMENT 2 PAGE 1 OF 4 CCMANCHE PEAK STEMt EI.ECTRIC STATION EME1GENCY RISPONSE CUIDELINE TASK ANALYSIS PACKAGE TASK ANALYSIS PACKAGE CUIDELINE NO. (4.2.6.15)
REVISION DATE (4.2.6.lC)
NAME (4.2.6.1D) 4 I
SUBMITTO ST (4.2.6.1E) DATE REVIE*4ED BT (4.2.6.tF) DATE a ngl.NEEA APPROVED BY _ (4.2.6.101 DATE OPi.aAILG:;5 f.sGI.NEEA CDA-204-4 L
CPSES ISSUE DATE PROCEDURE NO.
OPERATIONS DEPARTMENT ADMINISTRATION MANUAL ^-204 07 W k.
PREPARATION OF EMERGENCY RESPONSE GUIDELINES REVISION NO. 3 PAGE 26 0F 63 .
ATTACHMENT 2 PAGE 2 0F 4
. l .
E - ! 7 a
Q =
n- 1
?
. "?*y, $
5
> u
- C; 5 8 k"
.. 5h~
t-t s "
5~ C
-: M. r M
455 e t "at O 3 3C ~
lli
( 5 a
D
~
=
w L e
g u g 2,$
,z m
$^ " OE "
5 E* C 5 cQ -
$ "5 0
i . =
5 E i.
. a E
b T g "
s
=
ts T
a
- =
8 :
~.
. m 4 C 3 A" 3 b
5 e 5 :
E
_e b 3 t i e-h b
CPSES ISSUE DATE PROCEDURE NO.
OPERATIONS DEPARTMENT ADMINISTRATION MA'IUAL A-204 07 M
(
PREPARATION OF DIERGENCY RESPONSE GUIDELINES REVISION NO. 3 PAGE 27 0F 63 ATTACIDfENT 2 PAGE 3 0F 4 CPSES PLANT SPECIFIC CUIDELINE NO.
EM.ERGENCY RESPCNSE CUI0ELINE TASK ANALYSIS REVISION 50.
CUIDELINE NAME: RIVISICN DATE PAGE of INDICATOR '40RKSHEET INSTRL?ENTr (4.2.6.33)
REOUIRED CHARACTERISTICS: (4.2.6.3C)
COMPLETED BYr (4.2.6.3D) OATE:
CHAEACTERISIIC TUSTIFICATION INSIR WENT l SC.G.E FUSI ACC, [
Nt?BER UNITS I RANCE INCREVETTS TCLEPANCES MONITORINCIRF?ERENCES USFD (4.2.6.3E) (4.2.6.3F) (4.2.6.3G) (4.2.6.3H) (4.2.6.3.I) (4.2.6.3J) (4.2.6.3K)
Instrumentatien =eets the requirements soecified in the Rev. I Cenerte Backernund Documentation! YES NO Eneineers (4.2.6.3L)
Comments: (4.2.6.3M)
PROCESUDES #EFER!NCEDr (4.2.6.3N) 00A-204-45 L
CPSES ISSUE DATE PROCEDURE NO.
OPERATIONS DEPARTMENT ADMINISTRATION MANUAL A-204 07 W PREPARATION OF EMERGENCY RESPONSE GUIDELINES REVISION No. 3 PAGE 28 0F 63 ATTACHMENT 2 ,
PAGE 4 OF 4 CPSES PLA:iT SPECIFIC GUIDELINE NO.
E!iERCENCY RESPONSE GUIDELI:;E TASK ANALYSIS REVISICN NO.
CUIDELINE'NA E: P.EVISION DATE PAGE of CONTROL '.'ORKSHEET
'NSTRL?ENT: (4.2.6.4%)
PEOUTRED CHARACTERISTTCS: (4.2.6.4C)
CCMPLETED 3Y: (4.2.6.4D) DATE:
CliARACTERISTIC JUSTIFICATt0N CC IR6L l akt Ext;.CES NLPBER POSITIONS I!TDICATIONS CC??ENTS l USED
(*.. 0. E) (4.2.0.=F) 6.2.0.46) (. 4. o . ri) (..i.o. 1; Control meets the recuire-e9tn gemeified in the Rev. 1 Ce9eric Backeremd Documentation! Y!S NO Enriceer! (4.2.6.4J)
Ceraents: (4.2.6.4K)
'2ROCED"RES PETTRENCES (4.2.6.4t)
CDA-204-4c
= . ,.
. I CPSES ISSUE DATE PROCEDURE NO.
OPERATIONS DEPARTMENT ADMINISTRATION MANUAL DA-204 M 0 71984
( ,.
PREPARATION OF DIERGENCY RESPONSE GUIDELINES REVISION NO. 3 PAGE 29 0F 63 !
ATTACHMENT 3 PAGE 1 OF 3 CCMANCHE PEAK STEAM ELECTRIC STATION EMERCENCY RESPONSE GUIDELINE GENERIC PLANT COMPARISON e
i I
i i
l GENERIC PI. ANT CCMPARISCN i l
L REVISION DATE (4.2.7.1A) l l
l I
l SU3MITTED BY (4.2.7.13) TmE DATE REVIS'ED BY (4.2.7.1C) DATE UGLNEER APPROVED ST (4.2.7.1D) DATE GPEMUJN3 DJi!.EER l
l ODA-204-5 i
i
CPSES ISSUE DATE PROCEDURE NO.
OPERATIONS DEPARTMENT ADMINISTRATION MANUAL A-204 Jifri 0 71984
(.
PREPARATION OF EMERGENCY RESPONSE GUIDELINES REVISION NO. 3 PAGE 30 0F 63 ,
ATTACHMENT 3 PAGE 2 0F 3 j Generic Plant Comparison to CPSES System CPSES differences Juscification Completed !
(4.2.7.2.A) (4.2.7.2.B) (4.2.7.2.C) e i
3
( i l
P l
l l
l
( PAGE OF
( l:
ODA-204-Sa 1
l l
6 i
CPSES ISSUE DATE PROCEDURE NO. !
OPERATIONS DEPARTMENT ADMINISTRATION MANUAL g Q 71984 ODA-204
{
( i PREPARATION OF EMERGENCY RESPONSE GUIDELINES REVISION NO. 3 PAGE 31 0F 63 I ATTACHMENT 3 ;
PAGE 3 0F 3 f
- 1. Difference Description (4.2.7.3A) [
r i
l l
1 I
l i
- 2. Justification (4.2.7.3B)
( t t
- 3. Completed by (4.2.7.3C) DATE l
The difference mentioned above does not compromise the generic technical basis for the guidelines. ,
I (4.2.7.3D) /
ENGINEER DATE L
The difference mentioned above does not affect the overall objective ;
of the Plant Specific ERG's -
l (4.2.7.3D) /
i i
ENGINEER DATE i l Generic Procedure
Reference:
(4.2.7.3E) f l
l
\ +
i l
1 Comments: (4. 2. 7. 3 F) l (m. PACE OF l
i ODA-204-5b 1
CPSES ISSUE DATE PROCEDURE NO.
OPERATIONS DEPARTMENT ADMINISTRATION MANUE A-204 JUN 0 71984 PREPARATION OF EMERGENCY RESPONSE GUIDELINES REVISION No. 3 PAGE 32 0F 63 ATTACHMENT 4 PAGE 1 0F 28
( COMANCHE PEAK STEAM ELECTRIC. STATION EMERGENCY RESPONSE CUIDELINES WRITER'S GUIDE l
l l
L 1
I
CPSES ISSUE DATE PROCEDURE NO.
OPERATIONS DEPARTMENT ADMINISTRATION MANUAL JUN 0 71984 ODA-204 PREPARATION OF EMERGENCY RESPONSE GUIDELINES REVISION NO. 3 PAGE 33 0F 63 ATTACHMENT 4 PAGE 2 0F 28 TABLE OF CONTENTS SECTION TITLE PAGE
1.0 INTRODUCTION
1.2 Purpose 4 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.0 FORMAT 3.1 Title Page 5 C 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 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 16 4.4 Use of Logic Terms 16 4.5 Use of Cautions and Notes 17 4.6 Calculations 18 4.7 Underlining 18 4.8 Referencing among and between procedures 18 4.9 Component Identificttions 19 4.10 Level of Detail 19 4.11 Operator Aids 20 k.
CPSES ISSUE DATE PROCEDURE NO.
OPERATIONS DEPARTMENT ADMINISTRATION MANUAL DA-204 JUN 0 71984
(
PREPARATION OF EMERGENCY RESPONSE GUIDELINES REVISION NO. 3 PAGE 34 0F 63 ATTACHMENT 4 PAGE 3 0F 28 TABLE OF CONTENTS (continued)
SECTION TITLE PAGE 5.0 MECHANIC 3bF$TYLE .
5.1 Spelling 21 5.2 Hypenation 21 5.3 Punctuation 22 5.4 Vocabulary 23 5.5 Numerical Values 25 5.6 Abbreviations, Letter Symbols Acronyms 26 6.0 TYPING INSTRUCTIONS 6.1 General Typing Instructions 26 6.2 Page Arrangement 26 6.3 Breaking of Words 26
( 6.4 Printed Operator Aids 27 6.5 Use of Foldout Pages 28 6.5 Use of Oversized Pages 28 6.7 Use of Reduced Pages 28 7.0 REPRODUCTION 28 k.
r CPSES ISSUE DATE PROCEDURE NO.
OPERATIONS DEPARTMENT ADMINISTRATION MANUAL A-204 JUN 0 71984 ,
k '
PREPARATION OF EMERGENCY RESPONSE GUIDELINES REVISION No. 3 PAGE 35 OP 63 ATTACHMENT 4 PAGE 4 0F 28
1.0 INTRODUCTION
Emergency Response Guidelines (ERGS) are plant procedures that direct actions necessary to mitigate the conseguences of transients and accidents that.cause plant parameters to exceed reactor protection system set points or' engineered safety f eature set points. The ERGS will provide the operator guidance on how to verify the adequacy of critical safety functions and restore and maintain those functins 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. Generic Technical guidelines supp'.ied by the Westinghouse Owner's Group have been made plant ;
specific for Comanche Peak and will provide the technical basis for the development of the Comanche Peak ERGS. '
Technical guidelines represent the translation of engineering data derived from calculations, computer modeling, and plant-specific !
information (i.e. FSAR, Technical Specification, etc.) into
( information presented as guidance for development of detailed, plant-sepcific 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 Purpose This document provides administrative and technical guidance to be 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 l ERGS are procedures that govern plant operation during emergency I conditions and specify operator actions to be taken to return the plant to a known, stable condition.
I b
1
CPSES ISSUE DATE PROCEDURE NO.
OPERATIONS DEPARTNENT ADMINISTRATION MANUAL "^-204 k,
M 0 71984 PREPARATION OF EMERGENCY RESPONSE CUIDELINES REVIS10N No. 3 PAGE 36 0F 63 l
ATTACHMENT 4 PAGE 5.0F 28 2.1 Procedure Designation 1
Designation of the Emergency Response Guidelines sh'all be as follows:
2.1.1 Emergency Operating Proceduro.(EOP) 2.1.2 Emergency Operating Sub-procedura (EOS) 2.1.3 Emergency Contingency Actions (ECA) i 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 l unique identification number u
procedure designator EOS - 0.1 unique identification number.
procedure designator l
The unique number generally will correspond to the number assigned to the technical guidaline from which the procedure is prepared.
2.3 Revision Numbering and Identification l Revision to ERCS will be accomplished in accordance with STA-202, l " Preparation. Review. Approval and Revision of Station i Procedures."
3.0 FORMAT ,
(
l 3.1 Title Page
( Each ERG shall have a titio page (Figure 1). The primary l purposes of the title page are to identify the procedure and the l authorized revision.
k.
1 L
?
CPSES ISSUE DATE PROCEDURE NO.
OPERATIONS DEPARTMENT ADMINISTRATION MANUAL OD^-204 JUN 0 71984
(.
PREPARATION OF EMERGENCY RESPONSE CUIDELINES REVISION NO. 3 PAGE 37 0F 63 ATTACHMENT 4 l PAGE 6 0F 28 The title page shall contain the following information:
i .
3.1.1 A title descriptive of the emergency condition to which
- the procedure applies 3.1.2 The. procedure designation and number i 3.1.3 The'procidure revision number.
l 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 j 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
( drawn."
3.2.3 " Greater-than symbols for parameter 1 of symptom set I and III of Attachment 1 must be hand drawn."
3.2.4 " Figure 1 shall be printed on the reverse of page 2 i of 12." '
I l
4 w
E CPSES ISSUE DATE PROCEDURE NO.
OPERATIONS DEPARTMENT ADMINISTRATION MANUE A-204 JUN 0 71984 ,
PREPARATION OF EMERGENCY RESPONSE GUIDELINES REVISION No. 3 PAGE 38 0F 63 .
ATTACHMENT 4 PAGE 7 0F 28
- COMANCHE PEAK STEAM ELECTRIC STATION
. DERGENCY RESPCNSE GUIDELINES i
3.1.1
~
_ . l i
+
3.1.23
- 3.1.3 I
h h
SUBMITTED BY DATE
'3.t.
APPROVED ST DATE -
~3.4.3 FIZ*RE 1 1
'- . .- , , _ = - , _ . . - . . _ . , , . _ _ . r .., y, _, ,, , , . , . , , . , , , . _ . .. y.
CPSES ISSUE DATE PROCEDURE NO.
OPERATIONS DEPARTMENT ADMINISTRATION MANUAL A-204 JUN 0 71984
(
PREPARATION OF EMERGENCY RESPONSE GUIDELINES I . 3 ION NO. 3 PAGE 39 0F 63 ATTACHMENT 4 PAGE 8 0F 28 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 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 Issue 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, includine its attachments.
l i
+
l b
CPSES ISSUE DATE PROCEDURE NO.
OPERATIONS DEPARTMENT ADMINISTRATION MANUAL ^-204 M 0 71984 5, e PREPARATION OF EMERGENCY RESPONSE GUIDELINES REVISION NO. 3 PAGE 40 0F 63 ATTACHMENT 4 PAGE 9 0F 28 Procedure No.
Revision No.
NOTE:
- 1. The following administrative items must b'e 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*F and 700*F. ,
- 2. Upon completion of the above items, the procedure, less this sheet, is ready to be issued.
l I
k-
CPSES ISSUE DATE PROCEDURE NO.
OPERATIONS DEPARTMENT ADMINISTRATION MANUAL yy Q 7 ]Qg4 ODA-204 PREPARATION OF EMERGENCY RESPONSE GUIDELINES REVISION NO. 3 PAGE 41 0F 63 ATTACHMENT 4 PAGE 10 OF 28 CPSES ISSUE DATE PROCEDURE NO.
EMERGENCY RESPONSE CUIDELINE E0P- 0.0 REACTOR TRIP.OR, SAFETY INJECTION REVISION NO. O PAGE 2 of 14 M ACTION / EXPECTED RESPONSE l 1 RESPONSE NOT OBTAINED A. PURPOSE:
The purpose of this procedure is to verify proper response of automatic protection system following automatic actuation of a REACIOR TRIP or SAFETY INJECTION; and to assess plant conditions and identify the appropriate recovery procedure to be used.
- 8. STMPTOMS:
I. Reactor Trips '
- a. Any First-Out annunciator lit.
- b. Rapid decrease in neutron flux level
- c. All rod bottom lights lit and rods on the bottom
- d. Reactor trip breakers open
- e. Rapid decrease in unit load to 0 Power.
II. Safety Injection:
- a. Safety Injection annunciator lit.
- b. ECCS pumps running
- c. ESF status panel indications l
CPSES ISSUE DATE PROCEDURE NO.
OPERATIONS DEPARTMENT ADMINISTRATION MANUAL g.10 71984 ^-204
(
PREPARATION OF EMERGENCY RESPONSE GUIDELINES RFVISION NO. 3 PAGE 42 0F 63 ATTACHMENT 4 PAGE 11 OF 28 CPSES ISSUE DATE PROCEDURE NO.
EMERCENCY RESPONSE GUIDELINE E0P- 0.0 REACTOR TRIP OR SAFETT INJEC1!0N REVISION NO. O PAGE 3 of 14
_ sIEP b.4 ACTION / EXPECTED RESPONSE ',
' RESPONSE NOT 03IAIED !
NOTE: Circled numbers show IMMEDIATE ACT!CN steps NOTE: Poldout page should be open (Attachment 1)
Verify Reactor Trips
- a. All rod bottom lights - LIT a. Manually trip reactor.
IF reactor vill NOT E ip. THEN go to ECA -
L0 AN U CIPAIED C TRANSIENT WITHOUT TRIP.
- b. "All rod position indicators -
ZERO
- c. Neutron flux - DECREASING Verify Turbine Trip:
- a. All turbine stop vsives - CLCSED a. Manually trip turbine.
IF the turbine vill NOT E ip. THEN either stop ,
the EHC pumps OJ trip the turbine via the Local Trip Valve located at the hydraulic control rack.
hVerifyACEmergencyBuses IF NOT energized. THEN Ene rgized: go to ECA - I.0. Less e AC emergnecy bus voltage - OP ALL AC POWER. STEP NCRMAL 3.
Check If SI is Initiated: E E initiated. THEN
- a. Receipt of an "S" signal as go to BUS - 0.1 indicated on the RPS Status R7 ACTOR TRIP RECOVERY.
Panel A.D V acutuation of the follovIn~g" safeguards equipnent: ,
e CC Pumps - RUNNING e SI Pumps - RUNNING e RHR Pumps - RUNNING e CS Pumps - RCNNING e C74 Pumps - RUNNING e SSV Pumps - RUNNING e Motor-Driven AFW Pumps - RUNNING O e Emergency Diesel Generators - RUNNING
I
, o CPSES ISSUE DATE PROCEDURE NO.
OPERATIONS DEPARIMENT ADMINISTRATION MANUAL ^-204 M 0 71984 PREPARATION OF EMERGENCY RESPONSE GUIDELINES REVISION NO. 3 PAGE 43 0F 63 ATTACHMENT 4 PAGE 12 0F 28 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 Title.
3.5.1.2 Date Issued.
3.5.1.3 Procedure identifying number.
3.5.1.4 Procedure revision number.
3.5.1.5 Procedure page number as part of the entire procedure, including its attachments.
C- 3.5.1.6 Attachment Number.
3.5.1.7 Attachment Page Number as part of the entire attachment.
3.5.2 The " foldout" page shall always be the last attachment and shall have a color coded tab for rapid identification.
. o CPSES ISSUE DATE PROCEDURE NO.
OPERATIONS DEPARTMENT ADMINISTRATION MANUAL ODA-204 7
PREPARATION OF EMERGENCY RESPONSE GUIDELINES REVISION NO. 3 PAGE 44 0F 63 ATTACHMENT 4 PAGE 13 0F 28 CPSES ISSUE DATE PROCEDURE NO.
EMERGENCY RESPCUSE GUIDELINE E0P-0.0 REACTOR TRIP OR SAFETT INJECTION REVISION NO. O PACE 14 0F 14 ATTACHMENT I
- FAGE 1 0F 1 L
REACTCR TRIP OR SAFETY INJECTICN 4
- 1. RCP TRIP CRITERIA e Trip any RCP if component cooling water to that pump is lost and upper or lower bearing temperature is greater than 200*F.
e Trip all RCPs if BOTH conditions listed below are met:
- a. SI is ON
- a. Terminate SI unen & parameters listed below are met:
(1) Containment Conditions - NCRMAL (2) RCS Pressure - CREATER THAN 2000 PSIC (3) RCS Subcooling - (later) *F
( (4)
($)
Pressurizer Level - CREATER THAN 25:
Heat Sink:
(a) SG Level - CR3TER THAN 60
- OR -
(b) A W Flow - GREATER THAN 878 GFM
(1) RCS Pressure - LESS THAN 1785 PSIC (2) RCS Subcooling - LESS THAN (later) *F (3) Pressurizer Level - LESS THAN 10
- 4. SYwPTOMS FOR FRC - 0.1, RESPCNSE TO INA0ECUATE CC9? COCLINC Go to FRC - 0.L. R14PGNSE TO lbADEQUAIE CORE COULI5G vnen G systems in ANY ONE of the following sytytems sets occur:
s Yv? %M s1; PAWJ.IER:
. II .II
- 1. TCS > 1200*F -
> !00*F
- 2. Centainment Condition - AENCR2tAL A3NCPX\L
$. SNOMS FOR FRH - 0.1. DISPONSE TO LOSS OF SFCOND ARY HEAT SINK Go to FRH - 0.1 RESPCNSE IQ .455 0F SECCNCARY DEA: 4;>E, it Ar4 Flow is SOT AVAILABLE.
- 6. Reference procedure No. EPP-201 ACCESSWENT CF EMEROI: CT ACTION LP/ELS AND PLAN ACTIV!ATION, to determine if this event is covered by the emergency plan.
L FIGURE 5
CPSES ISSUE DATE PROCEDURE NO.
OPERATIONS DEPARTMENT ADMINISTRATION MANUAL ^-204 M 0 71984 PREPARATION OF EMERGENCY RESPONSE GUIDELINES REVISION NO. 3 PAGE 45 0F 63 ATTACHMENT 4 PAGE 14 0F 28 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. .
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 Instrtction Step Numbering
( 3.7.1 The PURPOSE and SYMPT 0MS 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 follows:
- 1. Verify . . . . . . . .
A. All . . . . . . .
- 1) Start . . . .
e CCP Running When steps are identified by a number or letter they must be followed in sequence. When bullets "o" are used, they may be performed in any order.
4.0 VRITING INSTRUCTION STEPS 4.1 Instruction Step Length and Content Instruction steps will be concise and precise. Conciseness denoted 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 eeeting objectives are as follows:
CPSES ISSUE DATE PROCEDURE NO.
OPERATIONS DEPARTMENT ADMINISTRATION MANUAL A-204 AN0719M PREPARATION OF EMERGENCY RESPONSE GUIDELINES REVISION NO. 3 PAGE 46 0F 63 ,
ATTACHMENT 4 PAGE 15 0F 28 4.1.1 Instruction steps should deal with only one idea.
4.1.2 Short, simple sentences should be used in preference t'o long, compound, or complex sentences.
4.1.3 Complex evolutions should be prescribed in a series of steps, with each step made as simple as practicable.
4.1.4 Objects 6f operator actions should be specifically stated.
This includes identification of exactly what is to be done and to what.
4.1.5 Limits should be expressed quantitatively whenever possible.
4.1.6 Mandatory sequence of steps is assumed unless the steps are identified by bullets "o".
4.1.7 Identification of components and parts should be complete.
4.1.8 Instruction content should be written to communicate to the 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 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 left-hand column of the dual-column format will contain operator action steps and expected response steps. The following
( rules are established for this column, in addition to the general b rules above.
. o CPSES ISSUE DATE PROCEDURE NO.
OPERATIONS DEPARTMENT ADMINISTRATION MANUAL DA-204 0 7 1984
(
PREPARATION OF EMERGENCY RESPONSE GUIDELINES REVISION NO. 3 PAGE 47 0F 63 ATTACHh2NT 4 PAGE 16 0F 28 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.
4.3 Response Not.0btained Column Conti'ngency 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.
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 override automatic controls and to initiate manually what is
{ normally automatically initiated.
4.4 Use of Logic Terms The logic terms AND, OR, NOT, IF, IF NOT, WHEN, and THEN are ofter 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 works will be underlined.
The use of AND and OR within the same action shall be avoided.
When AND or OR are Eed together, the logic can be very ambiguous.
The dual-column format used equates to the logic, IF NOT the action in the left-hand column, THEN follow the action specified in the right-hand column; for example: IF RCS press below 1536 psig, THEN verify SI pump flowmeters.
Use other logic terms as follows:
4.4.1 When attention should be called to combinations of conditions, the work AND shall be placed between the description of each condition. The work AND shall not be g used to join more than three conditions. If four or more b conditions need to be joined, a list format shall be used.
CPSES ISSUE DATE FROCEDURE NO.
OPERATIONS DEPARTMENT ADMINISTRATION MANUAL JUN 0 71984 ODA-204 PREPARATION OF EMERGENCY RESPONSE GUIDELINES REVISION NO. 3 PAGE 48 0F 63 ATTACHMENT 4 PAGE 17 0F 28 4.4.2 The work O_R_ 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 E B but bot both."
4.4.3 When action steps are contingent upon certain conditions or combinations of conditions, the step shall begin with the words _IF,or F WHEN followed by a description of the condition or conditions (the antecedent), a comma, the word THEN, followed by the action to be taken (the consequent). WHEN is used for an expected condition. IF is used for an unexpected but possible condition.
4.4.4 Use of E NOT should be limited to those cases in which the operator must respond to the second of two possible conditions. E should be used to specify the first condition.
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 are called " PRECAUTIONS" and are covered in operator training. Those that apply to 2 portion of a procedure are called " CAUTIONS" and are placed immediately before the procedural steps to which they apply.
l Cautions shall extend across the entire page and shall be
- highlighted as shown in the E
- < ample CAUTION. This placement of
) cautions helps vnsure that the procedure user observes the l 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 l consequent to the subsequent instructional step.
i 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 page.
l t
I i
CPSES ISSUE DATE PROCEDURE NO.
OPERATIONS DEPARTMENT ADMINISTRATION MANUAL A-204 JUN 0 71984 PREPARATION OF EMERGENCY RESPONSE GUIDELINES REVISION NO. 3 PAGE 49 0F 63 ,
ATTACHMENT 4 PAGE 18 0F 28 4.5.1 The following examples illustrate these instructions.
4.5.1.1 Example NOTE:
NOTE:, 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
- 4.6 Calculations 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.
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 whenever 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;,exampic: Go to EOS - 0.1, REACTOR TRIP RECOVERY." Go to Step 20.
When cross referencing is unavoidable, appropriate place keeping aids shall be incorporated. See section 4.11.
CPSES ISSUE DATE PROCEDURE NO.
OPERATIONS DEPARTMENT ADMINISTRATION MANUAL A-204 07 E PREPARATION OF EMERGENCY RESPONSE GUIDELINES REVISION NO. 3 PAGE 50 0F 63 ATTACHMENT 4 PAGE 19 0F 28 4.9 Component Identification With respect to identification of components, the following rules are to be followed:
4.9.1 Equipben't, 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 alarm windows are specifically the item of concern in the procedure, the engraving should be quoted verbatim and emphasized by using all capitals.
, 4.9.3 The names of plant system titles are emphasiz3d by capitalization of first letter in each word. khen the word is deleted from the title because of brevity and is understood because of the 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.'
4.10 Level of Detail Too much detail 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 each control that is provided for infrequent or abnormal operation, with a number engraved on the control panel placard, the number should be included in i parentheses within the instructional step. Indication for Controls provided for normal plant operation will not generally be listed in the ERGS.
4.10.2 For control circuitry that executes an entire function upon actuation of the control switch, the action verb
( appropriate to the component suffices without further b ar.111fication of how to manipulate the control devices for example, "SI PMPS SUCTION FROM RWST, (69/1-8806) - OPEN."
Recommended action verbs are as follows:
e CPSES ISSUE DATE PROCEDURE NO.
OPERATIONS DEPARTMENT ADMINISTRATION MANUAL A-204 07 M PREPARATION OF EMERGENCY RESPONSE GUIDELINES REVISION NO. 3 PAGE 51 0F 63 ,
ATTACHMENT 4 PAGE 20 OF 28 4.10.2.1 For power-driven rotating equipment, use Start, Stop.
4.10.2.2 For valves, use Open, Close. Throttle Open,
. Throttle Close, Trip 4.10.2'.3' For power distribut. ion breakers, use Sychronize and Close, Trip 4.10.3 For control switches with a potential placement that establishes a specified readiness condition, the verb
" Place" should be used along with the engraved name of the desired position;,For example, " Place the Steam Dump Interlock Selector Switch in the "BYP INTLK" position.
4.10.4 Standard practives for observing for abnormal results need not be prescribed within procedural steps. For example, observation of noise, vibration, erratic flow, or discharge pressure need not be specified by steps that start pumps.
{
4.11 Operntor 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.
4.11.1 Units of Measure Units of measure of 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, 1bs/hr.
4.11.2 Titles and Headings Capitalization should be used for references to tables and figures, titles of tables and figures within text material, and column headings within a table.
Examples: Refer to figure 2 for ....
... as shown in Table 2. Equipment Power l Supplies, the ....
k
CPSES ISSUE DATE PROCEDURE NO.
OPERATIONS DEPARTMENT ADMINISTRATION MidUAL DA-204 07 N PREPARATION OF EMERGENCY RESPONSE CUIDELINES REVISION NO. 3 PAGE 52 0F 53 ,
ATTACHMENT 4 PAGE 21 0F 28 4.11.3 Figures, Table, and Attachment Numbering Sequential arabic numbers should be assigned to figures, tables, and attachments in seperate series. The sequence sho.uld correspond with the order of their reference in the text. The symbol "//" and abbreviation "No." are unneccessary 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 completion 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 proedure to
, another.
5.0 MECHANICS OF STYLE 5.1 Spelling Spelling should be consistent with modern usuage. When a choice of spelling is offered by a dictionary, the first spelling should be used.
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.
k.
CPSES ISSUE DATE PROCEDURE NO.
OPERATIONS DEPARTMENT ADMINISTRATION MANUAL ^-204 M 0 71984 PREPARATION OF EMERGENCY RESPONSE GUIDELINES REVISION NO. 3 PAGE 53 0F 63 ATTACHMENT 4 PAGE 22 0F 28 ,
5.2.1 When doubt exists, the compound word should be '
restructured to avoid hyphenation.
5.2.2 Hyphens should be used in the following circumstances:
5.2.2.1 in compound numerals from twenty-one to ninety-nine; example:
one hundred thirty-four 5.2.2.2 in fractions; exampics: one-half, two-thirds 5.2.2.3 in compounds with "self"; examples:
self-contained, self-lubricated 5.2.2.4 when the last letter of the first work is the same vowel as the first letter of the second
( vork-as an alternative, two words may be used; example: fire-escape of 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 another work; exampics:
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 seperate 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 several sentences. Punctuation should be in accordance with the following rules.
5.3.1 Brackets
-k Do not use brackets.
CPSES ISSUE DATE PROCEDURE NO.
OPERATIONS DEPARTMENT ADMINISTRATION MANUAL DA-204 M 0 71984
( PREPARATION OF EMERGENCY RESPONSE GUIDELINES REVISION NO. 3 PAGE 54 0F 63 ATTACHMEN. 4 PAGE 23 0F 28 5.3.2 ccion Use a colon to indicate that a list of items is to follow, for example: Restore cooling flow as follows:
5.3.3 Comma 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 items in a procedure, instruction, or equipment numbers.
( 5.3.5 Period Use a period at the end of complete sentences and for indicating the decimal place in numbers.
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. Simpic words are generally common words.
i 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 i rather than general, familiar rather than formal, precise l rather than blanket.
l i 5.4.4 Define key works that may be understood in more than one j sense.
5.4.5 Verbs with specific meaning should be used. Exampics are listed in Table 1.
l l 5.4.6 Equipment status should be denoted as follows:
k.
l
. I
CPSES ISSUE DATE PROCEDURE NO. <
OPERATIONS DEPARTMENT ADMINISTRATION MANUAL ODA-204 jgg g 7 jgg4 PREPARATION OF EMERGENCY RESPONSE GUIDELINES REVISION NO. 3 PAGE 55 0F 63 l ATTACEMENT 4 PAGE 24 0F 28 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 performing related support function (s). -
Tab 1s 1. Action Verbs Verb Application
({ Allow To permit a stated condition to be achieved prior to proceeding, for example, " allow discharge perssure to stahtlize" -
Check To perform a comparison with a procedural requirement
" Check if SI can be terminated" .
l Close To change the physical position of a mechanical device so that 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.
r Inspect To measure, observe, or evalaate a feature or characteristic for comparison with specified limits;,
method of instpection should be included, for example,
" visually inspect for lesks"
( Open To change the physical position of a mechanical device,
%- such as valve or door to the unobstructed position that permits access or ficw, for example, "open valve ZL-2459A"
- - , - . -___- , , ~ ~ . , - - , , - ----- --------w --r--- --
CPSES ISSUE DATE PROCEDURE NO.
OPERATIONS DEPARTMENT ADMINISTRATION MANUAL ODA-204 PREPARATION OF EMERGENCY RESPONSE GUIDELINES REVISION NO. 3 PAGE 56 0F 63 ,
ATTACHMENT 4 PAGE 25 0F 28 Table 1. Action Verbs (continued)
Verb Aoplication Record To document specified contion 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" Stop To 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 . . ."
Trip To manually activate a semi-automatic feature, for example, " trip breaker . . ."
Vent To permit a gas liquid confined under pressure to escape at a vent . . . pump" Verify To observe an expected condition or characteristic, for example, " verify discharge pressure is stable" 5.4.6.2 Operating - This word means that a system subsystem, train, component, or device is in operation and is performing its specified function (s), and that " clearance" or other conditions do not prevent it from maintaining that service.
5.4.6.3 Available - This word means that a system, subsystem, train, component, or device is operable and can be used as desired;,however, it need not be operating.
5.5 Numerical Values The use of numerical values should be consistent with the followig rules:
5.5.1 Arabic numerals should be used.
- O CPSES -
ISSUE DATE PROCEDURE No.
OPERATIONS DEPARTMENT ADMINISTRATION MANUAL A- 04
,jjJl () 710Qd
( REVISION NO. 3 PAGE 57 0F 63 PREPARATION OF EMERGENCY RESPONSE GUIDELINES <
ATTACHMENT 4 PAGE 26 0F 28 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 shuld 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 addition and subtration 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 uppe- limits for each data cell would accomplish the same purpose; for example, 10 mil 11 amperes (9.5 to 10.5). Avoid using 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 Abreviations. Letter Symbols, and Acronyms 5.6.1 The use of abbreviations should be minimized because they may be confusing to those who are not thoroughly familiar with them. Abbreviations may be used where necessary to save time and space, and when their meaning is unquestionably clear to the intended reader. The full meaning of the abbreviation should be written in after the first use af the abbreviation and whenever in doubt.
Consistency should be maintained throughout the procedure.
5.6.2 Capitalization of abbreviations should be uniform. If the abbreviation is comprised of lowercase letters, it should e appear in lowercase in a title or heading. The period l
should be omitted in abbreviations except in cases where I the omission would result in confusion.
i j 5.6.3 Letter symbols may be used to represent operations, quantities, elements, relations, and qualities.
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 parts of a compound term.
l
CPSES ISSUE DATE PROCEDURE NO.
OPERATIONS DEPARTMENT ADMINISTRATION MANUAL ODA-204 PREPARATION OF EMERGENCY RESPONSE GUIDELINES REVISION NO. 3 PAGE 58 0F 63 ATTACHMENT 4 PAGE 26 OF 28 5.6.5 Abbreviations, 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 communicating mathemat,1c ideas.
5.6.6 Only those abbreviations, symbols and acronyms that are listed in the Comanche Peak standard list may be used in the ERCS.
6.0 TYPING FORMAT 6.1 General Typing Instructions For emergency operating procedures, the following general requirements are to be followed:
6.1.1 Paper size should be 8-1/2 x 11 inches.
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, typerwriter element is to be used.
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.
l 6.2.3 The 8-1/2 inch edges shall constitute top and bottom of the pages. Tables and figures shall be readable with the page so arranged. Rotation of print 2d matter should be avoided for emergency operating procedures.
f 6.3 Breaking of Words l
i Breaking of words shall be avoided to facilitate operator reading, k.
j 1
L i
CPSES ISSUE DATE PROCEDURE NO.
OPERATIONS DEPARTMENT ADMINISTRATION MANUAL DA-204 JUN 0 71984 I
PREPARATION OF EMERGENCY RESPONSE GUIDELINES REVISION NO. 3 PAGE 59 0F 63 ATTACHMENT 4 ,
PAGE 21 0F 28 (
i 6.4 Printed Operator Aids 6.4.1 Figures include graphs, drawings, diagrams, and I illustations. The following rules are established. ,
6.4'.111 s The figure number and its title are placed three [
line spaces below the figure field.
6.4.1.2 The figure number and titic should be of modern '
type, pitch 12.
6.4.1.3 The figure field must not violate specified l page margins. l 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. j 6.4.1.6 Grid lines of graphs should be at least 1/Q-inch apart; numbered grid lines should be bolder
, than unnumbered grid lines, j 6.4.1.7 Labeling of items within the figure should be (
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.
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 letters and numbers at ,
least 1/8-inch high. L 6.4.1.10 All lines in figures should be reproducible.
6.4.2 Tables should be typed using the following rules.
i 6.4.2.1 Type style and size should be the same as that i for the rest of the procedure.
P i
i e CPSES ISSUE DATE PROCEDURE NO.
OPERATIONS DEPARTMENT ADMINISTRATION MANUAL DA-204 M 071984 PREPARATION OF EMERGENCY RESPONSE GUIDELINES REVISION NO. 3 PAGE 60 0F 63 ,
ATTACHMENT 4 PAGE 28 0F 28 6.4.2.2 The table number and title should be located above the table field and three line spaces below preceding text.
6.4.2.3 A heading should be entered for each column and centered within the column; the first letter of words in the column headings should be capitalized.
6.4.2.4 Horizontal lines should be placed above and below the column headings; vertical itnes, while desirable, are not necessary or required.
6.5 Use of Foldout Pages When used, a foldout page is treated as a single page. It should follow the same format as a standard page except the width is
({ different. The page should be folded so that a small margin exists between the fold and the right-hand edge of standard pages. This will reduce wear of the fold.
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 pages should be avoided whenever possible. Final size of reduced pages should be standard page size. Reduced pages should be readable.
7.0 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 on the reverse of a precceding page.
k.
CPSES ISSUE DATE PROCEDURE NO.
OPERATIONS DEPARTMENT ADMINISTRATION MANUAL ODA-204 M 0 71984 PREPARATION OF EMERGENCY RESPONSE GUIDELINES REVISION NO. 3 PAGE 61 0F 63 ATTACHMENT 5 PAGE 1 0F 2 CP$E$ EMERCENCY RESPONSE DATE: PAGE 1 0F 2 CUIDELINE VERIFICATION CHECKLIST CUIDEL1"NE NAME: ERG.NO: ERC REV NO.
This checklist shall be used to establish the accuracy of information and instructional steps of the ERCS. to determine that the procedures can be accurately and ef ficiently carried out, and to demonstrate that the procedures are adequate to mitigate the consequences of transients and accidents. The verification may be accorp11shed by staulator exercises, control room walk-throughs or Desk top reviews. Any one, combinations or all methods say be used. Indicate the methoda(s) used below.
( ) Simulator Emereising
( ) Control Roon Walkthrough
( ) Desk top review criteria Revtever / snee
- 1. The ERG accurately reflects the information presented in the technical guidelines. /
- 2. The ERC is written in accordance with the writer's guide. /
- 3. The ERC has been walked through the control room and can be followed without confusion, delays or errors. /
4 Controls, equipeeet .id indications that are referenci+ in the ERC are available in the .Itar, use the same designation, see tre same units, and operate (or will operate) as specified in the procedure. /
- 3. The level of detail is sufficient to allow the least qualified operator en the shif t crew to use if effectively. /
CDA.204 1
, e o CPSES ISSUE DATE PROCEDURE NO.
OPERATIONS DEPARTMENT ADMINISTRATION MANUAL JW 0 71984 ODA-204
(.
PREPARATION OF EMERGENCY RESPONSE GUIDELINES REVISION NO. 3 PAGE 62 0F 63 ,
ATTACHMENT $
PAGE 2 0F 2 CPSES EMERGENCY RESPONSE DATE: PAGE 2 0F 2 eGUIDELINE VERITICATION CHECKLIST GUICELINE NAME: ERG NO: ERG REY NO.
- 6. The miniaua ehlft crew can complete the ERG without outside assistance. /
- 7. The ERG has been verified against the Emergency Response Guideline Transition Flow Chert. /
Comments
/
Comment Resolutions
/
CHECKLIST REVILTD 00A.204=la R-1/6-84
P CPSES ISSUE DATE PROCEDURE NO. l OPERATIONS DEPARTMENT ADMINISTRATION MANUAL DA-204 r JUtt 0 71984
(
PREPARATION OF DfERGENCY RESPONSE CUIDELINES REVISION NO. 3 PAGE 63 0F 63 J 4
ATTACHMENT 6 PAGE 1 UF 1
?
I CP$ts EMIRGENCY RESPONSE DATE: PAGE 10F L
, GU1JtLINE IMPROVEMENT REOCNMENDATION i
ERG NAMEt ERG NO: ERC RIV NO.I i
- 1. The fe11ewin6 change (s) are recommended to taprove the Casanche Feak ERCS '
i L
(
- 2. Justifiestion/Reeses for Changel '
i 4aae es person recesumenean6 enange
- 3. Evaluatten (taeorporate/de not interperate) and Justtitaations D
f I
I sporestene 6666neer
(
k CDAa204 1 l I
L i
?
I
TEXAS UTILITIES GENERATING COMPANY Log # TXX-4216
..vw4,v..w...... ..r ..sv ain =v,i..... ... ..in=4. ..a' Fi1e 1 10010 July 6, 1984 Mr. B.=J.'Youngblood, Chief Licensing Branch No.1 Division of Licensing U. S. Nuclear Regulatory Conmission .
Washington, D.C. 20555 l
l
SUBJECT:
COMANCilEPEAKSTEAMELECTRICSTATION(CPSES) l DOCKET NOS. 50-445 AND 50-446 I TM! ACTION PLANT ITEMS 1.C.1 AND-1.C.8; CPSES PROCEDURES GENERATION PACKAGE, REV. 3 i
REF: Mr. B. J. Youngblood letter to Mr. R. J. Gary i dated March 6,1984 '
Dear Mr. Youngblood; ,
Enclosed are ten copics of the CPSES Procedures Generation Package, I Rev. 3. This arocedure 00A-204. addresses all concerns and requirements expressed at t1e NRC meeting of March 29, 1984 with the WOG Procedures Subcommittee, cerely, fib /d4 H. C. Schmidt RWil:grr Enclosure cc - Mr. J. J. Stefano Mr. Dennis L. Serig Mr. James W. Clifiord
/
Y)s\ l i
A 0 8% tal.6% 0.V 09 5 Ah t't 00 0 00V N Vi FC't Mit'i t**il'I % V