ML20204F402
| ML20204F402 | |
| Person / Time | |
|---|---|
| Site: | Fermi  |
| Issue date: | 07/31/1986 |
| From: | DETROIT EDISON CO. |
| To: | |
| Shared Package | |
| ML20204F395 | List: |
| References | |
| RTR-NUREG-0737, RTR-NUREG-737 PROC-860731, NUDOCS 8608040176 | |
| Download: ML20204F402 (45) | |
Text
Enclosure 2 to VP-86-0093 PROCEDURES GENERATION PACKAGE 8608040176 860731 ADOCK0500g1 PDR P
PROCEDURES GENERATION FACKAGE (PGP)
Draft Revision 0 July, 1986 i
FERMI 2 4
I Prepared by:
General Electric Company Date: July, 1986 m
Approved by:
C-Date: 7/Zi/Ek Operations Engineer Recommended by:
/
Date:
8 OSRD Chairman Approved by:
-- ~
Date:
Plant Manager I
l page 1 of 14 l
LBP/100/R557/2.0 l
070286 1
I TABLE OF CONTENTS Section Page I
Introduction 3
II Plant Specific Technical Guidelines 4
III Writer's Guide for EOPs 7
IV EOF Verification Program 8
V E0P Validation Program 10 VI E0P Training Program 12 Enclosure 1
" Writer's Guide for Emergency Operating Procedures" 14 s
l page 2 of 14 rev. 0 draft
i I.
INTRODUCTION The purpose of this Procedures Generation Package (PCP) is to describe the Emergency Operating Procedures (EOPs) developmenc program for Fermi 2.
This document has been prepared and is sabmitted in response to Supplement 1 to NUREG-0737, Item 7.2.b.
This document has been reviewed for compilance with NUREG-0899 in accordance with Battelle document, " Review Criteria for the Evaluation of Procedure Generation Packages," Final Draf t dated November 1,1983.
The Fermi 2 E0Ps are developed directly from the Plant Specific Technical Guidelines (Section II) and are written in accordance with the Fermi 2 Writer's Guide for E0Ps (Section III). The E0Ps are verified and validated in accordance with the E0P Verification Program (Section IV) and E0P Validation Program (Section V) prior to use in the E0P Training Program (Section VI).
i page 3 of 14 rev. O draft
i II.
PLANT SPECIFIC TECHNICAL GUIDELINES GENERAL The following symptomatic Plant Specific Technical Guidelines (PSTGs) have been developed for the Detroit Edison Company Fermi 2. power plant:
o RPV Control Guideline o
Primary Containment Control Guideline o
Secondary Containment Control Guideline o
Radioactivity Release Control Guideline The RPV Control Guideline maintains adequate core cooling, shuts down the reactor, and cools down the RPV to cold shutdown conditions.
The Primary Containment Control Guideline maintains primary c ontainment integrity and protects equipment in the primary containment with respect to the consequences of all mechanistic events.
The Secondary Containment Control Guideline protects equipment in the secondary containment, limits radioactivity release to the secondary containment, and either maintains secondary containment integrity or limits radioactivity release from the secondary containment.
The Radioactivity Release Control Guideline limits radioactivity release into areas outside the primary and secondary containments.
These plant specific technical guidelines are based on draf t revision 4AC of the generic Emergency Procedures Guidelines (EPGs) developed by the BWR Owner's Group (BWROG). EPG draft revision 4AC was discussed with the NRC by representatives of the Emergency Procedures Committee i
of the BWROG in December, 1985.
REFERENCE DOCUMENTS The following documents have been used in developing the Fermi 2 PSTGs:
1 BWR Owners Group Emergency Procedure Guidelines, draf t revision 4AC dated November 22, 1985.
2.
Bases of Variables and Curves used in the EPGs, BWROG EPG Appendix A, draft revision 4AC dated December, 1985.
3.
EPG Bases, BWROG EPG Appendix B, draft revision 4AC dated December, 1985, page 4 of 14 rev. 0 draft
4 Calculational Procedures, BWROG EPG Appendix C, draf t revision 4AC dated January 1,1986.
5.
Fermi 2 documents including the FSAR, Technical Specifications, P& ids, and elementary diagrams.
6.
Fermi 2 POM Procedures series 29.000.00 based on s'previ'ous revision of the EPGs.
4 7.
Administrative Operations Procedure 21.000.13, "EOP Guidelines".
PSTG DEVELOPMENT The BWROG EPGs are generic to GE-BWR 1 through 6 designs in that they address all major systems which way be used to respond to an emergency.
Because the design and as-constructed status of Fermi 2 does not include all of the systems in the EPGs, the EPGs are applied to Fermi 2 by deleting statements which are not applicable or by substituting equivalent systems where appropriate. For example, l
Fermi 2 has no IC, HPCS, or SPMS and all statements referring to these systems have been deleted. Likewise, Fermi 2 has a Mark I primary containment and all EPG statements applicable to Mark II and III primary containment designs have been deleted.
Brackets within the EPGs enclose plant unique procedures, setpoints, design limits, pump shutoff pressures, etc. Parentheses within brackets indicate the source for the bracketed variable. Bracketed values are either obtained from Fermi 2 technical and source information such as Technical Specifications and the FSAR, or are calculated based on EPG Appendix C, " Calculational Procedures".
Additionally, the EPGs contain, in some cases, a general category of l
systems indicated by brackets, e.g. [other steam driven equipment], or a bracketed list of systems, dependent on plant design, that i
potentially could be used for a given action. EPG Appendices A and B provide the direction necessary to incorporate plant-specific data for the bracketed information to the PSTGs. Other source documents include as-built plant drawings, equipment manuals, design documents, plant operating procedures and vendor supplied documents.
To document the' development of the PSTGs from the EPGs, a copy of the generic EPGs has been marked-up to show plant-specific changes and retained in the EOP development program records file. Differences between the PSTGs and the EPGs and the bases for these differences have been documented. In addition, a list of the plant specific values, limits, curves, and information and the source of this data has been generated as part of the PSTG documentation.
I l
l page 5 of 14 rev. 0 draft
Further, changes have been evaluated as follows:
A step-specific evaluation to ensure the change conforms to the o
EPG intent.
An overall procedure evaluation to ensure that the,EPG strategy
~
o was not adversely af fected, An evaluation of supporting calculations.
o EOP DEVELOPMENT EOPs are developed from the PSTGs by reformatting the PSTGs in accordance with the Fermi 2 Writer's Guide for E0Ps and by incorporating Fermi-specific information such as:
Plant operating procedures, alarm response procedures,
o abnormal response procedures, and maintenance instructions Sampling procedures o
Calculational procedures o
E0P procedural cross-references and E0P step references o
Plant unique design features o
Where a list of systems appropriate for a given action is identified, In cases where there Fermi 2 systems are incorporated into the E0Ps.
is a choice of systems to be used, these systems are evaluated by Fermi 2 Operations and those most appropriate for Fermi 2 are used.
These decisions are documented by memo and retained as part of the EOP development program documentation package.
rev. O page 6 of 14 draft
.~ -
III. WRITER'S GUIDE FOR EOPs GENERAL The Fermi 2 " Writer's Guide for Emergency Operating Procedures" provides detailed instructions for the preparation and revision of E0Ps using effective writing principles and addresses aspects of writing procedures from a human factors standpoint. Compliance with the Fermi 2 Writer's Guide (Enclosure 1) ensures all EOPs are concise, complete, accurate and unambiguous. It also ensures that they are uniform in format, crganization, level of detail, and style.
DOCUMENT DESCRIPTION l
fo a on ht i ue to g n rate co ci and r cis strue ions with a uniform text arrangement.
Guidance for preparation of the E0Ps is addressed in the Writer's l
Guide as follows:
o Scope and General Guidelines o
Specific E0P Writing Guidelines o
E0P Format o
Mechanics of Style o
Typing Format o
Abbreviations and Acronyms o
Definitions and Usage of Key Words The writer's guide may be revised as necessary, based on training feedback, operating experience, and the results of the verification sud validation programs. Once the E0Ps are implemented, the writer's guide will become an administrative 1y controlled Fermi 2 document.
The " Fermi 2 Writer's Guide for Emergency Operating Procedures" is based on:
o Emergency Operating Procedures Writing Guideline (INPO 82-017) developed by the Emergency Operating Procedures Implementation Assistance (EOPIA) Review Group and published by INPO o
Guidelines for the Preparation of Emergency Operating Procedures (NUREG-0899)
Plant Specific Administrative Procedures o
page 7 of 14 rev. 0 draft
IV.
EOP VERIFICATION PROGRAM GENERAL The E0P Verification Program is the evaluation performed on the Fermi 2 E0Ps to confirm the written correctness of the procedures and to ensure that applicable generic and plant-specific technical information has been incorporated properly. This evaluation also confir=s that human factors considerations presented in the Writer's Guide have been applied.
The E0P Verification Program is based on the industry document
" Emergency Operating Procedures Verification Guideline" (INPO 83-004),
developed by the E0 PIA Review Group and published by INPO.
PROGRAM DESCRIPTION The E0P Verification Program encompasses the efforts necessary to support a comparative evaluation of the E0Ps to source documentation.
To fulfill this objective a desk-top review and a control room / simulator walk-through is performed.
The desk-top review is performed to confirm:
Plant-specific calculations of action values and design limits o
used in the EOPs are correct as verified by an independent engineering organization, The E0Ps and the Writer's Guide are reviewed for corrections and o
applicability by a Human Factors Engineer.
The PSTGs conform with the EPGs and the bases for any deviations o
are documented,
The E0Ps conform with the PSTGs and the bases for any deviations o
are documented, o
The list of plant specific values, limits, curves and plant specific information and the source of this data is checked for accuracy.
o The list of E0P procedure and step reference substitutions is checked for accuracy.
The control room / simulator walk-through of the E0Ps is performed by an independent team to confirm:
o E0P nomenclature agrees with equipment nomenclature on the control operating panels (COPS) page 8 of 14 rev. 0 draft
the decisions and Instrumentation is available to support o
implement the actions in the E0Ps. Items verified are:
Decision and action levels are within the range of the installed instrumentation Decision and action levels can be read on the installed instrumentation Decision and action level units are in agreement with the installed instrumentation Decision and action levels can be read within the required accuracy specified in the EOPs Satisfactory completion of the Fermi 2 Verification Program for Emergency Operating Procedures will ensure a thorough review for Any discrepancies between written correctness and technical accuracy.
the E0Ps and EOP source documer,tation identified will be evaluated and Documentation for this comparative evaluation will be resolved.
retained as part of the E0P development program documentation package.
At the completion of the E0P Verification Program, each EOP will be submitted for review and approval in accordance with established Fermi 2 procedures.
1 l
t t
- 0 page 9 of 14 draft l
l
--~
ss
V.
EOP VALIDATION PROGRAM GENERAL The EOP Validation Program is the evaluation performed on the Fermi 2 EOPs to determine that the decision process and actions specified in
~
the procedures can be performed by the operator to effectively manage i
emergency conditions.
In effect, the E0P Validation Program is performed to assure that the E0Ps are useable, that is, they can be understood and followed without confusion, delays or errors.
The program is based on the industry document " Emergency Operating Procedures Validation Guidelines" (INPO 83-006) developed by the E0 PIA Review Group and published by INFO.
PROGRAM DESCRIPTION In the E0P Validation Program, desk-top review, control room walk-throughs and sessions on a simulator are used to establish the accuracy of the E0Ps and demonstrate that the procedures can be used to effectively mitigate the consequences of transients and accidents.
o Desk-top review: A validation method whereby personnel explain and/or discuss procedure actions in response to a scenario, o
Control room walk-through: A validation method whereby control room or other personnel conduct a step-by-step enactment of their decision process and actions in response to a scenario without carrying out actual control room functions.
o Simulator: A validation method whereby control room or other' personnel perform actual control functions on simulated equipment in response to a scenario.
The program is implemented by an independent team comprised of Detroit Edison Company personnel, General Electric advisors, and a Human Factors consultant.
The team will select and develop scenarios which best exercise each E0P extensively. In selecting the scenarios, emphasis will be placed on human engineering factors as well as technical adequacy. The scenarios will be developed to guide the operator through anticipated procedure steps so that the evaluation criteria can be addressed. The team members will note expected versus actual responses to E0P actions in order to identify potential problems with the EOPs. They will evtluate operator feedback and provide recommended disposition of procedural discrepancies.
1 page 10 of 14 rev. 0 draft i
The evaluation criteria will include:
o Actions taken based on E0P decision and action statements conform with the intent of tl.e EOPs.
Effectiveness of the EOP actions to mitigate the consequences of o
transients and emergency conditions (taking into consideration simulator capabilities) o The usability of the E0Ps with respect to their ability to be understood and followed without confusion, delays or errors Operator feedback, considering the number of operators used and o
their previous experience and training It is recognized that some results may require revision to the E0Ps.
In such cases, the validating team will determine the extent to which the revised E0P must again be verified and validated. A report will be prepared upon completion of the Fermi 2 EOP Validation Program to document the above process.
The E0P Validation Program will be performed prior to the E0P Training Program discussed in Section VI.
Feedback from the E0P Training Program will be evaluated and incorporated into the EOPs as appropriate.
t page 11 of 14 rev. O draft
VI.
EOP TRAINING PROGRAM GENERAL The E0P Training Program portion of the Licensed Operator Training Program is designed to support implementation of the E0Ps. Training will be performed on the EOPs after the completion of the E0P Verification and Validation Programs. The E0P Training Program objectives are to enable the operator to:
o Understand the structure and technical bases of the E0Ps o
Develop a working knowledge of the E0Ps o
Use the E0rs under adverse operating conditions This training program may possibly point out additional deficiencies with the new E0Ps, enabling revision and refinement to the E0Ps before they are implemented in the plant.
The following description outlines the approach used to train licensed operators on E0Ps and,to ensure that the operators are informed and knowledgeable regarding future changes to the EOPs.
PROGRAM DESCRIPTION The initial training effort will consist of classroom instruction, control room walk-throughs and simulator exercises. In the classroom sessions, lectures will be presented that are based on both Appendix B to the BWRGG Emergency Procedure Guidelines, " Detailed Discussion of Cautions and Operator Actions" and on human factors considerations in the formating of the E0Ps as presented in the Fermi 2 Writer's Guide.
These lectures will be specifically tailored to the Fermi 2 plant and will include the following information:
o Logic behind EOP development o
The EOPs themselves o
Application of EOPs under multiple failure scenarios Control room walk-throughs will provide practical experience with the E0Ps. During training, the team approach to using E0Ps will be stressed.
This walk-through training will concentrate on:
o Operator responsibilities o
Information flow o
Interaction between operators in the control room Operators will be referred to control room panel indications and controls in specific emergency scenarios that simulate varying degrees of plant degradation.
4 page 12 of 14 rev. O draft
Training on the EOPs will be conducted using scenarios developed for the Fermi 2 control room simulator. Training will be conducted with operators performing their normal control room functions. To further promote the operator's understanding in the various aspects of the EOPs, team communications and procedural usage techniques will be reinforced during post scenario critique and discussion, sessions.
In addition, the plant training and operations staff will participate in the development and execution of annual operator requalification.
The Fermi 2 annual operator requalification program covers training on Fermi 2 operating procedures.
Whenever the EOPs undergo revision, training on minor procedure revisions will be conducted through a program of required reading (self-taught), preshift briefings, or lectures in the requalification program. Training on major revisions will be conducted by the use of classroom instruction during the annual operator requalification program.
page 13 of 14 rev. 0 draft
ENCLOSURE 1 Fermi 2 WRITER'S GUIDE FOR EMERGENCY OPERATING PROCEDURES l
page 14 o f 14 rev. 0 draft
WRITER' S GUIDE FOR EMERGENCY OPERATING PROCEDURES Draft Revision 0 July, 1986 FERMI 2 100/R530A/1,0 page 1 of 33 070286
TABL.E OF CONTENTS Page 1.0 Scope........................................
4 2.0 References...................................
4 3.0 G e ne ra l G u id e l i na s........................... 4 3.1 Revisions...............................
4 3.2 General Criteria a nd Level of Detail.... 5 4.0 Specific E0P Writing Guidelines.............. 6 4.1 E0P Overview............................
6 4.2 EOP P re s e nt a t io n........................ 7 4.3 Purpose and Entry Conditions Format..... 8 4.4 Operator Actions and Override Statements 8 4.5 Action and Conditional Statement Format. 9 4.6 Overrid e Statement s Forma t.............. 10 4.7 Log ic a'nd Co nd it io nal Terms............. 11 4.8 Ca u t i o n s a nd Not e s...................... 12 4.9 G ra ph s.................................
13 4.10 Ta b l e s.................................
14 4.11 Ca l c u la t i o n s............................ 15 5.0 E0P Format...................................
15 5.1 General Format Criteria.................
15 5.2 Approval Sheet and Table of Content s.... 16 5.3 Sect ion and Step Designation............ 16 5.4 Page Identificat ion a nd Numbering....... 17 5.5 Re fere ncing a nd Bra nching............... 18 6.0 Mcchanics of Style...........................
18 6.1 Vocabulary.............................
18 6.2 S pe l l i ng................................ 19 6.3 Abbreviat ions a nd Acronyms.............. 19 6.4 Capitalization..........................
19 6.5 Emph a s i s...............................
2 0 6.6 Punctuation............................
20 6.7 Component Id e nt i fi ca t io n...............
21 6.8 Numerical Values.......................
21 7.0 Typing Format................................
22 7.1 G e ne ra l Requ ireme nt s...................
2 2 7.2 Pag e Ar ra ng eme n t........................ 22 7.3 S pa c i ng................................ 2 2 page 2 of 33 rev. O draft
TABLE OF CONTENTS (Cont'd)
ENCLOSURES 4 - Definitions and Usage of
~
Key Words.........................
24 - Override Statement (Even Numbered /Lef t Hand Page).......... 28 - Operator Actions (Odd Numbered /Right Hand Page).........
30 - First Page of E0P (Odd Numbered /Right Hand Page).........
32 EOP Abbreviations and Acronyms....
33 -
i l
l-4 I
r I
t 1
l rev. O page 3 of 33 draft i
l
1.0 Scope This document provides detailed guidelines for writing and revising Fermi 2 Emergency Operating Procedures (EOPs).
~ 2.0 References 1.
Administrative Procedure 12.000.07, Plant Operations Manual Procedures 2.
Fermi 2 Nuclear Operations Interfacing Procedure (NOIP) 11.000,131 3.
Emergency Operating Procedures Writing Guidelines, INPO Document 82-017, July 1982 4.
Guidelines for the Preparation of Emergency Operating Procedures, NUREG-0899, August 1982 5.
Fermi 2 Final Safety Analysis Report 6.
Development of a Checklist for Evaluating Emergency Procedures used in Nuclear Power Plants, NUREG/CR-1970, SAND 81-7070 7.
Checklist for Evaluating Emergency Procedures used in Nuclear Power Plants, NUREG/CR-2005, SAND 81-7074 8.
Fermi 2 Plant Specific Technical Guidelines (PSTGs) 3.0 General Guidelines 3.1 Revisions 1.
Revisions to this E0P Writer's Guide shall not be made without approval of the Operations Engineer.
2.
Revisions to EOPs shall be made in accordance with this Writer's Guide and Fermi 2 Administrative Procedure 12.000.07, Plant Operations Manual Procedures.
3.
Neither individual E0Ps nor this Writer's Guide should employ individual page revisions. When a revision is made, l
all pages should take on the new revision number.
4.
Revisions to the Writer's Guide and E0Ps should be denoted in accordance with Administrative Procedure 12.000.07.
page 4 of 33 rev. O j
draft i
3.2 General Criteria and Level of Detail 1.
The following general criteria should be used in writing EOPs where practical:
o The organization of the EOPs should closely parallel, but not be constrained by, the organization of the PSTGs.
o Instruction steps should deal with only one idea.
o Short, simple sentences should be used in preference to long, compound, or complex sentences.
o Complex evolutions should be prescribed in a series of steps, with each step made as succinct as practicable.
o Objectives of operator actions should be clearly stated while allowing operational flexibility during degraded plant conditions.
o Objects will be listed for instructional steps that involve an action verb relating to three or more objects.
o Limits should be expressed quantitatively whenever possible.
o Numbered steps will be executed in sequence unless otherwise stated.
o Identification of components and parts should be complete enough to permit accurate identification by the operators.
o Location information for components or parts that might otherwise be difficult to find should be provided whenever practical.
2.
Human engineering and ALARA factors should be incorporated into the EOPs where practical.
3.
All EOPs should conform to the guidelines set forth in this Writer's Guide. Deviations from these guidelines should be based upon maintaining clarity, allowing for human factors considerations, or to retain the intent of the PSTGs.
4.
All copies of the original EOPs should be clearly legible and of high quality.
i page 5 of 33 rev. O draft
m 4.0 Specific EOP Writing Guidelines 4.1 E0P Overview The EOPs are developed from the Fermi 2 Plant Specific 1.
Technical Guidelines (PSTGs) which contain four symptomatic emergency procedure guidelines:
RPV Control (RC) o Primary Containment Control (PC) o Secondary Containment Control (SC) o Radioactivity Release Control (RR) o 2.
The Fermi EOPs should be organized as follows:
RPV Control (RC), 29.000.01, will consist of three a.
sections, two contingencies and an enclosure:
R'PV Water Level Control (RC/L) o RPV Pressure Control (RC/P) o Reactor Power Control (RC/Q) o RPV Flooding (C1) o Level / Power Control (C2) o o
RC Enclosure b.
Primary Containment Control (PC), 29.000.02, will consist of five sections and an enclosure:
Torus Water Temperature Control (TW/T) o Drywell Temperature Control (DW/T) o Primary Containment Pressure Control (PC/P) o Torus Water Level Control (TW/L) o Primary Containment Hydrogen and Oxygen o
Control (PC/H) o PC Enclosure Secondary Containment Control (SC) and Radioactivity c.
Release Control (RR), 29.000.03, will consist of four sections and an enclosure:
Secondary Containment Temperature Control (SC/T) o rev. O page 6 of 33 draft
l o
Secondary Containment Radiation Level Control (SC/R) o Secondary Containment Water Level Control (SC/L) o Radioactivity Release Control (RR) o SC/RR Enclosure 3.
Each E0P should consist of the following:
a.
Purpose a brief, succinct statement describing the objective of the operator actions performed in the control of specific parameters, b.
Entry Conditions:
symptoms of a plant condition or conditions which could degrade into an emergency.
Symptoms include specific values of plant operating parameters, instrument setpoints, and specific plant conditions which, when exceeded, require entry into the applicable EOP.
c.
Operator Actions:
procedural instructions to the operator to monitor and control specific plant.
parameters.
d.
Override Statements: detailed instructions to the operator to implement a new set of actions in accordance with an identified change in existing plant cond itions.
4.
E0P Enclosures The Enclosure to each E0P will consist of supplemental information such as plant-specific procedures, calculational procedures, graphs (full size), tables, and other pertinent information when such information cannot be ef fectively integrated into the body of the EOP. The order and contents of the Enclosure should be specified by a Table of Contents.
4.2 EOP Presentation 1.
Each of the E0Ps (see 4.1.2) should be contained in a separate E0P binder.
2.
E0P binders should be designed so that, when opened, the front and Sack of opposing pages will be completely visible.
3.
Each EOF binder should be clearly identified on the front cover and back binding to identify the E0P.
page 7 of 33 rev. O draft
m.
4.
The front cover and back binding should contain the EOP title, its acronym, and plant name.
5.
Each section and the enclosure of each EOP should be sepa-rated by a reinforced page with an offset tab, which should be identified by the unique acronym presented.in 4.1.2.
4.3 Purpose and Entry Condition Format 1.
The Purpose statement (see 4.1.3) shall be located at the top of page one of each E0P, immediately below the E0P title and number, 2.
The Purpose statement should be brief and concise.
3.
Entry Conditions (see 4.1.3) s: fall be listed on page one of each E0P, immediately below th& Purpose.
4.
When multiple Purpose statements or Entry Conditions are listed :
They should be presented in no particular order, o
They should be preceded by a bullet (o) rather than a o
number, so that no priority is implied by the order in which they are listed.
- 5. presents an example of the format used for page one of each EOP.
4.4 Operator Actions and Override Statements 1.
All instructions to the operator to monitor and control cpecific plant parameters shall be contained in Operator Actions and Override Statements.
2.
Operator Actions and Override Statements consist of Action Statements. They may also include Conditional Statements and supplemental information such as Cautions, Notes, Graphs j
and Tables as applicable.
l 3.
Action Statements provide instructions to the operator to I
perform a specific task or tasks for the purpose of monitoring and controlling the identified plant pa rame t er.
i 4.
Conditional Statements prescribe a specific plant condit ion i
or conditions that must exist prior to executing the 1
subordinate Action Statement. Use of anticipated or i
expected plant conditions should be avoided unless utilized by the PSTGs and should then be accompanied with additional j
evaluation criteria.
t 1
j page 8 of 33 rev. J draft i,
--h we~---M-*"-w-me m,w-ce
- = - - * -
wN-=-------e---+ m --Fwwmverv4e~e'-m"'
'w
+
- -'ews
.-e-*wm-i
,--,-,---,r-,-.w--,-_,wr-,,,,,,-.,-,.--ww%+-ewee em i
5.
All Conditional Statements shall be coupled with one or more Action Statements. However, Action Statements may or may not be coupled with a Conditional Statement.
6.
Override Statements specify actions which take precedence over the specific task or tasks being performed in the corresponding Operator Actions.
7.
Contingency actions, as detailed in the PSTGs, should be integrated with Operator Actions for the specific parameter being controlled. Contingencies which cannot be integrated shall be referenced as contingency procedures.
8.
All Operator Actions shall appear on right hand (odd numbered) pages.
9.
All Override Statements shall appear on left hand (even numbered) pages.
4.5 Action Statement and Conditional Statement Format 1.
All Action' Statements:
o Should begin with an action (command) verb or adverb as
~
prescribed by the PSTG.
Example 1:
Monitor and control RPV pressure.
Example 2:
Slowly increase'RPV pressure...
o Shall explicitly state when performance of concurrent actions is required, o
Should be presented in single column block format.
o Should be preceded by the conditional term (see 4.7.2) when subordinate to a Conditional Statement.
o Should not be presented in a negative format.
o Should be followed by a place-keeper "
2.
All Conditional Statements:
o Should be preceded by a conditional term (see 4.7.2).
o Should be presented in single column block format, indented from the conditional term.
Example:
IF the main turbine-generator is on-line, THEN confirm or initiate recirculation flow runback to minimum.
page 9 of 33 rev. 0 draft l
l 4
4.6 Override Statements Format l
1.
Override Statements are written using the same format described for Action and Conditional Statements.
All Override Statements shall _ start with the phrase "While 2.
executing step (s) XXX (through XXX):"
3.
The applicability of an Override Statement to Operator Actions is emphasized by a horizontal double border above the Override Statement at the same elevation as the first line of the text of the corresponding Operator Actions.
4.
Applicability of the Override Statement to the corresponding Operator Actions is also highlighted by a vertical double margin bar extending parallel to and for the length of the corresponding procedural text.
5.
If additional override Statements become applicable to the Operator Actions, a second Override Statement is placed within the structure of the first Override Statement. The applicability of this second Override Statement is specified through the use of the same format used for the initial Override Statement.
t 6.
When an Override Statement first appears, it shall be preceded by a bullet. Should an Override Statement require repeating on the following lef t hand page, it shall be preceded by an asterisk in place of a bullet.
j 7.
When an Override Statement no longer applies, the double margin bar is terminated with "X's" at the bottom of the margin bar.
8.
Override Statements which apply to more than one page of Operator Actions shall be repeated on each succeeding left hand page. The "X's" a t the bottom of the vertical double margin bar on the preceding page should then be replaced with a downward pointing arrow, but only when all the Over-ride Statements also apply to the following page.
9.
Pages containing Override Statements are headed by the EOP section title and the title "0VERRIDE STATEMENTS." Neither i
title will be in bold type.
I j
10.
If no Override Statements apply to a right hand page, the lef t hand page should contain the phrase "NONE APPLICABLE" i
centered on the page along with the E0P section title, and horizontal "0VERRIDE STATEMENTS" header.
l page 10 of 33 rev. O draft l
[
I
.n~
nn--.-.-------,--
-,,,,--a~-,
m,-w---__
.nnn-~-.-
+,,-,----.nc-----,
-,.,---m,.
---,-----,-r,
__-.r,~~~,-ww.,-----,
11.
Override Statement pages should not be used for supplemental procedures contained in the EOP Enclosures.
12.
See Enclosure 2 for examples of Override Statements.
4.7 Logic and Conditional Terms 1.
Logic terms:
AND identifies a conjunction of conditions or indepen-o dent actions (all associated conditions / actions must be satisfied or performed).
OR identifies a disjunction of conditions or indepen-o dent actions (only one of the associated conditions /
actions must be satisfied or performed).
1' 2.
Conditional terms:
BEFORE identifies an action that must be taken prior to l
o reaching a specified action level (e.g. if the param-l eter is approaching its action level rapidly, action should be taken sooner than if the parameter were chang-ing slowly).
l IF (including BUT ONLY IF) designates a condition that o
l may or may not exist when the associated step is reach-l ed.
IF is not meant to include future events and does not mean the operator must wait for the condition to be satisfied before proceeding to the next procedural step.
If the condition is not met, the operator proceeds to the next step and does not return, even if the condi-tion is subsequently met, unless specifically directed to do so.
THEN identifies an Action Statement which is subordi-o j
nate to a Conditional Statement.
WHEN identifies a condition which may or may not occur.
o The operator must monitor and wait for the condition before executing the action and proceeding to the next procedural step.
If the condition does not occur, subsequent steps are not per formed.
3.
Logic and conditional terms may be used in both Action and Conditional Statements.
i.
4.
Logic and conditional terms should be capitalized except when contained within a Caution, Note or Purpose Statement.
4
?
l 5.
Logic and conditional terms should be printed in bold type.
i I
i i
page 11 of 33 rev. 0 draft
[
I y
4
., _ _..,, -.... ~, _, -. _... -.--- -._-,.-... _.
6.-
Format:
o The use of AND and OR within the same phrases should be avoided. Phrases requiring the use of both AND and OR terms should be clarified through the use of bullets or text format.
o The term OR should be used when addressing alternate combinations of conditions, o
The terms AND and OR should not be used to join more than two conditional or actions. If three or more conditions or actions are to be joined, a list format should be used.
o The terms AND and OR should be separated through the use of spacing from the applicable conditions or actions in the text.
o Lists of conditions or actions should only be numbered or lettered if a specified order is required.
o The term THEN should be used prior to an Action State-ment when the Action Statement is subordinate to a Conditional Statement.
o The term THEN should not be used at the end of an action to instruct the operator to perform another action within the same step.
4.8 Cautions and Notes 1.
Cautionary information and plant operating limitations should be included within the procedural text when necessary to alert personnel of potentially degraded plant conditions or of possible danger to plant equipment or personnel.
2.
If additional information (other than a Caution) is necessary to support a procedural step, a Note should be used.
3.
When a Caution or Note is too lengthy (more than half of the page) to be included in the applicable text, it may be pre-sented in the E0P Enclosure and referenced by an abbreviated Caution / Note in'the applicable text.
4.
A Caution or Note should be located on the same page and prior to the step (s) to which it applies.
If a Caution or Note specifically applies to an action on a subsequent page, the Caution or Note should be repeated.
5.
Cautions and Notes shall not be used in lieu of Action Statements.
page 12 of 33 rev. 0 draft
j_
6.
Supplemental information other than Cautions and Notes i
should be contained in the EOP Enclosure whenever it cannot 4
be practically integrated into the procedural text.
7.
Caution and Note format:
Cautions should be highlighted by dashed double heading
~
a.
and bottom lines. The left edge of the lines should be i
aligned with the left margin of the applicable text.
i.
The right edge should be aligned with the right margin.
b.
Notes should not be highlighted by heading lines.
The heading CAUTION or NOTE should be capitalized and c.
centered above the text.
d.
The heading NOTE should be printed in bold type. The heading CAUTION and its text should be printed in bold type.
I e.
The text of Cautions or Notes should be block format and single spaced. Caution text should extend for the j
full length of the text to which it applies. Cautions i
applicable to an entire section should extend to the i
full margins of the page.
i j
f.
Note text should be centered between the margins, using half the intervening space.
3 When two or more Cautions are applicable to the same step (s), the Cautions should be separated by "*******"
)
centered between the Cautions. Only one Caution heading is necessary in this case.
t h.
Enclosures 2 and 3 present examples of the format used for Cautions and Notes, s
8.
Use of Cautions and Notes should be minimized to reduce clutter and maintain continuity of'the E0Ps.
l 4.9 Graphs j
l 1.
Graphs should be self-explanatory, legible, and within the j
instrument accuracy available to the operator.
j 2.
Graphs applicable to a page of text should be presented on
{
that page as part of the text, whenever practical, and shall be reduced size.
3.
If space is not available on the page of the applicable text, the previous page on which the graph appears should be explicitly referenced.
l l
page 13 of 33 rev. O draft
Full size graphs shall be located in the corresponding E0P 4.
Enclosure.
All written information on graphs should be capitalized for 5.
clarity.
6.
Graph Format:
Numerical Graphs should be referred to by title.
a.
designations should not be used. Consistantly applied acronyms may be used in lieu of full titles.
The graph title should be placed above the figure field.
b.
Capital letters are used for the title.
Grid lines and numbered divisions should be spaced for c.
accurate readability.
Break points along an axis should be clearly indicated.
d.
A restricted operation region should be clearly identi-e.
fied by slanted parallel lines and the area marked:
I I
l DO NOT OPERATE IN THIS AREA.
I I
I Significant points on a curve should be identified f.
along the corresponding axis.
4.10 Tables 1.
Tables should be Icgible and self-explanatory.
Tables should be presented within the body of applicable 2.
text.
If not, tables should appear in the E0P Enclosure.
3.
Table Format:
for the Type style and size should be the same as that a.
rest of the procedure, b.
A heading should be entered for each column and centered within the column. The first letter of words in the column headings may be capitalized.
Tables should be constructed with a double heading line c.
and double bottom line.
Tabular headings should be separated from the entries d.
by a line. Columns should be separated by vertical lines.
Tabular headings should be aligned as follows:
e.
1)
Horizontally by related entries.
rev. O page 14 of 33 draft
2)
Vertically by decimal point for numerical entries, t
3)
Vertically by first letter for word entries, with continuation lines indented two spaces.
f.
Vacant cells in any table should be labeled "N/A" to indicate "not applicable."
g.
The table title (if applicable) should be capitalized and centered above the table field below the preceding text.
h.
Example:
TABLE RC/P-3 l Minimum Alternate Number of l RPV Flooding Open SRVs l Pressure (psig) l l
4 or more l
120 3
l 160 2
l 245 1
l 505 I
l 4.11 Calculations 1.
Calculations should be located within the applicable text.
If not, they should appear on the opposing page (if they do not interfere with Override Statements) or in the E0P Enclosure.
2.
Conversion factors should be used to obtain calculated results in the sane engineering units used in the E0P text and on plant instrumentation.
3.
Only when specific instruments are required, calculation instructions shall identify the necessary instruments and, when necessary for clarity, the panel on which those instruments are located.
5.0 EOP Format 5.1 General Format Criteria i
1.
The E0Ps should be written on both sides of the page so that even numbered pages appear on the left and odd numbered pages appear on the right.
2.
Even numbered (left) pages should be used for the following:
a.
All Override Statements page 15 of 33 rev. O draft
b.
Graphs (when applicable to the Override Statement) c.
Cautions and Notes (when applicable to the Override Statement) 3.
Odd numbered (right) pages should be used for the following:
Purpose and Entry Conditions a.
b.
All Operator Actions Notes and Cautions (when part of the Operator Actions) c.
d.
Tables (when part of the procedural text and only when practical) e.
Graphs (reduced size when part of the procedural text, and only when practical) 4.
Page one of each EOP should include the EOP number and title, Purpose, and Entry Conditions (see Attachment 4).
Operator Act-ions may also be included if practical.
5.2 Approval Sieet and Table of Contents 1.
The initial page (page i) of every E0P shall be an Approval Sheet that identifies the procedure and includes plant management approval signoffs in accordance with Fermi review procedures (Reference 1).
2.
The second page (page li) of every E0P should contain a Table of Contents of that E0P.
5.3 Section and Step Designation 1.
The first two lettere indicate the area of control as follows:
RC = RPV Control PC = Primary Containment Control SC = Secondary Contalnment Control RR = Radioactivity Release Control DW = Drywell Control l
TW = Torus Water Control i
2.
The last letter indicates the parameters to be controlled:
L = Water Level R = Radiation Level P = Pressure H = Hydrogen and Oxygen 1
l Q = Power i
T = Temperature i
i page 16 of 33 rev. O draft l
l l
.m-.-
____,,...,,.m..__-,___,__-.-__
3.
Contingency sections and steps are designated by the letter "C".
4.
A virgule (slant line) separates the area of control and the parameter (e.g., RC/P).
~
5.
Arabic numerals should be used for numbering. steps and substeps in the following decimal format:
RC/L-1 (First-level step number)
RC/L-2 (First-level step number) 2.1 (Second-level step number - substep) 2.2 (Second-level step number'- substep)
RC/L-3 (First-level step number) 6.
Second-level substeps appearing as the first step on a page should be preceded by the section and step designation (e.g., RC/L-2.2) which should be contained in parentheses for emphasis.
7.
Supplemental procedures contained in E0P Enclosures may use a sequential arabic numbering system.
8.
Continuing a step onto a second page should be minimized. When necessary:
The word "(continued)" shall be placed at the end of a.
the text on the preceeding page.
b.
The abbreviation " cont'd" shall be placed directly below the step number on the subsequent page.
5.4 Page Identification and Numbering 1.
The top left hand corner of each E0P page should be identified by a Fermi 2 unique document number, revision number, and page number.
Example:
29.000.01 rev. 1 page 15 2.
The top of each page should identify the area of control and the parameter to be controlled; e.g.,
RPV WATER LEVEL CONTROL (RC/L).
3.
Subnumbering of pages should not be used; (e.g., page 7A of 20). EOPs will be repaginated when required.
4.
The last page of each E0P Section and Enclosure should contain the phrase "LAST PAGE SECTION XXX (ENCLOSURE XXX)"
centered at the bottom of the page.
page 17 of 33 rev. 0 draft
5.5 Referencing and Branching 1.
Referencing other steps within the procedure being used should be minimized. Steps should be repeated in the E0P text rather than referenced.
2.
When another procedure or other steps are to be performed in parallel, the referencing procedure shall specify that the operations are to be performed concurrently.
3.
To minimize confusion, branching is used when the operator is instructed to leave one procedure or step to use another procedure or step.
a.
The word " enter" shall be used when branching to another procedure.
b.
The word " continue" or " execute" shall be used when branching forward to another part of the sane procedure, c.
The word " return" shall be used when branching to a previous part of the same procedure.
4.
When referencing or branching, the referenced procedure title, step number and page number shall be explicitly stated; e.g., Enter RPV Control at step RC/L-1 (29.000.01, page 3).
5.
E0P sections should be tabbed as an aid for the operator.
The tabs should be marked to identify each section.
6.
Procedures should be referenced in parentheses in some Action Statements for use as an aid to the operator (See ).
6.0 Mechanics of Style 6.1 Vocabulary 1.
Words and meanings used in the E0Ps should be consistent with those used in the PSTGs.
2.
Words used in E0Ps should convey precise meaning to the trained person.
a.
Use short, common words of few syllables.
l b.
Use common usage if it makes the procedure easier to understand.
c.
Minimize the use of articles (a, an, and the) unless needed for clarity.
page 18 of 33 rev. O draft
d.
Use action verbs in instructional steps to denote a particular action that the operator must perform. Some common action verbs and their standardized applications are provided in Enclosure 1.
e.
Avoid words which are not clearly definable such as frequently, slowly, of ten, periodically or quickly.
3.
For control circuitry that executes an entire function upon actuation of a control switch, the action verb appropriate to the component suffices without further amplification of how to manipulate the control device (e.g., close F023A, A Recirc. PUMP SUCTION valve, on COP H11-P603).
6.2 Spelling Spelling should be consistent with modern usage as specified in a standard English dictionary.
6.3 Abbreviations and Acronyms 1.
Abbreviations and acronyms should be limited to those commonly used at Fermi.
3.
EOP section designations are listed in 4.1.2.
t 6.4 Capitalization 1.
Minimize the use of capitalization.
2.
Capitalize the first letter of each word of specific systems.
3.
Capitalize letters of engraved names and numbers on panel placards and annunciator windows.
4.
Capitalize page heading titles (see 4.1.2 and 5.4.3).
5.
Capitalize circuit breaker positions, valve positions and equipment running light indications when contained in an action statement that directs their operation.
6.
Capitalize logic and conditional terms (see 4.7).
7.
Capitalize acronyms (see 6.3).
8.
Capitalize the words PURPOSE, ENTRY CONDITIONS, OPERATOR ACTIONS, OVERRIDE STATEMENTS, CAUTION and NOTE when used as titles.
page 19 of 33 rev. O draft i
.. ~.
-.- _._..__ _._ _ _ __.._ _. __.__-.. _-._~..
9.
Capitalize key E0P terms such as EMERGENCY RPV DEPRESSURIZA-TION IS REQUIRED, STEAM COOLING IS REQUIRED or RPV FLOODING IS REQUIRED when used in Action Statements.
10.
Capitalize graph titles and all written information contained on graphs for clarity.
6.5 Emphasis 1.
Underlining should not be used for emphasis.
2.
Bold print should be used for emphasis, and should be restricted to the following:
a.
Logic and conditional terms (see 4.7),
b.
The word NOTE when used as a title (see 4.8).
c.
The word CAUTION when used as a title, the text withia a caution, and the heading and bottom lines around the caution.
d.
Numbered grid lines when practical.
e.
The following words when used to describe conditions, actions, or action values: cannot, not, no, until, except, unless, exceeds, both, all, only, any, above, below, more than, less than, irrespective, concurrently and at (when used with a setpoint).
f.
The words "and" and "or" in Action Statements and Conditional Statements when used to relate multiple or alternate conditions / actions.
6.6 Punctuction 1.
Punctuation should be used only as necessary to aid reading and prevent misunderstanding.
2.
Word order should be selected to minimize punctuation.
If extensive punctuation is necessary for larity, the sentence should be rewritten or broken down into several sentences.
3.
Punctuation should be in accordance with the following:
a.
Use a colon to introduce a list of items with no established priority.
b.
Limit the number of commas to ensure that the instruction is not too complex or awkward.
page 20 of 33 rev. O draft
c.
Use a period to indicate decimal places in numbers and to end sentences.
d Use parentheses to identify procedures when re fere nci ng.
e.
Use of hyphenation should be avoided in the EOP text.
6.7 Component Identification 1.
Equipment and controls that are identified within the E0Ps should be referenced by panel number and placard description (if provided on the panel).
2.
Annunciators should be identified by quoting the annunciator window number enclosed in parentheses e.g., RCIC TURBINE TRIPPOD (1D94).
3.
When referencing specific engraved names and numbers on panel placards and alarm windows, the engraving should be quoted verbatim.
6.8 Numerical Values 1.
Arabic numerals shall be used.
2.
For numbers between zero and one (or minus one), the decimal point shall be preceded by a zero (e.g., 0.1).
3.
For numbers less than zero, a minus sign shall precede the numbe r (e.g., -1. 2).
4.
The number of significant digits in procedural steps should be equal to the number of significant digits available on plant instrumentation. The operator should not be required to read an indicator to greater accuracy than that d isplayed.
5.
Engineering units specified for process variables should be the same as those on the panel displays.
6.
Units of measure should be given numerical values that represent observed or measured data and calculated results.
A virgule (/) should be used instead of "per" (e.g., f t/see a nd Ibs/hr).
7.
Limits should be expressed quantitatively whenever possible.
Tolerances should be expressed by indicating the entire range (e.g., use 10" t o 20" ra t he r tha n 15" + 5").
page 21 of 33 rev. O draft
7.0 Typing Format 7.1 General Requirements 1.
Paper should be white bond and sized 8)" x 11" with no foldouts or oversized pages.
For typing the following, see the specific seEtions:
2.
Action and Conditional Statements (4.5) a.
b.
Override Statements (4.6) c.
Cautions and Notes (4.8) d.
Graphs (4.9) e.
Tables (4.10) f.
Section and Step Designation (5.3) g.
Page Identification and Numbering (5.4) 7.2 Page Arrangement 1.
An example of an even-numbered (left hand) page is shown in.
2.
An example of an odd-numbered (right hand) page is shown in.
3.
Page margins are specified on Enclosures 2 and 3.
4.
A new page should be started to allow a Caution or Note to appear on the same page as the applicable step.
5.
An entire step should be placed on a single page wherever practical.
6.
Each E0P section should start on a new page.
7.3 Spacing 1.
Text should be typed using single spacing.
2.
Double spacing should be used:
l a.
between steps.
b.
In Conditional and Action Statements to enhance clarity.
page 22 of 33 rev. O draft
c.
between items in a list.
d.
to separate or emphasize text as necessary.
3.
Triple spacing should be used between page headings and the respective text.
4 4
i i
i 1
J i
i I
1 END OF TEXT page 23 of 33 rev. O J
draft i
ENCLOSURE 1 DEFINITIONS AND USAGE OF KEY WORDS l
Interpretations and definitions regarding the usage of key E0P words and phrases are provided below. This information promotes a uniform understanding of the actions intended by the steps and Cautions in the EOPs.
Adequate Core Cooling: heat removal from the reactor sufficient to restore and maintain peak fuel clad temperature (PCT) at or below 2200*F.
Two viable mechanisms of adequate core cooling exist.
In order of preference, they are Core Submergence and Steam Cooling.
Anticipate:
foresee or expect the certain occurence of a specified condition.
Approach: come very near to or make advances toward a setpoint or action level in such a manner that, in the operator's judgement, meeting or exceeding the setpoint or action level is imminent.
Assure: make certain that a specified state or condition is established and will be maintained. Both direct and indirect indications may be used to determine that the specified state or condition has been 1
achieved and will be maintained.
Available:
the state or condition of being ready and able to be used (placed into operation) to accomplish the stated (or implied) action or function.
Bypassing:
temporarily disabling the functioning of an automatic 4
protection feature or equipment interlocks.
Cannot be determined: using all available indications (direct and indirect, singly or in combination) the value, or as appropriate, the trend of the specified parameter is not ascertainable.
Cannot be maintained above (or below): using the systems which are specified, the value of the identified parameter will in the judgement of the operator, decrease below (or rise above) the specified limit or action level.
Cannot be restored and maintained above (or below):
using the systems j
~
which are specified, the value of the identified parameter will, in the judgement of the operator, not return to and remain above (or below) the specified limit or action level.
Concurrent:
See Enter.
page 24 of 33 rev. O draft
,,.. _.,, ~,
-,,,n,,--------,----.,-._---,,_.n,,
,,,n-_..--,
ENCLOSURE 1 (Continued)
DEFINITIONS AND USAGE OF KEY WORDS complete the step containing the continue instruction and then Continue:
go forward to the specified step of the same procedure.
Control: to regulate a parameter or process.
uncontrolled opening and closing of a safety / relief valve to Cycling SRV:
the extent that actions required in the RPV Control Guideline to monitor and control either RPV water level, pressure or power can not The actuation of Low-Low Set SRV control be satisfactorily performed.
logic which results in the lifting and resesting of a pre-determined set of SRVs over a wide RPV pressure band need not be interpreted as a
" cycling" condition as long as control of RP7 parameters is not adversely affected.
disabling the logic or function of a system or component so as Defeatina:
from operating; as used in the EOP, this term generally to prevent it indicates more than just the positioning of a " bypass" switch (e.g.
defeating RSCS interlocks).
unless concurrent execution is specified, leave the Enter (procedure..):
procedure (or section of the procedure if in one of several parallel If concurrent action paths) and proceed to the identified procedure.
action is specified, execute the steps of the entered procedure in parallel with the steps of the procedure containing the entry instruction.
Establish: to place a parameter or system into a specified condition.
the identified value of Exceeds: to go above or beyond, by any amount, limit.
leave the step containing the execute instruction and Execute [ step..}:
take the action specified in the identified step, continuing on through the subsequent steps of that section.
characterized by separateness of signal source (i.e.
Independent:
sensors), signal processors and indicators.
Initiate: operate readily available system controls as necessary to cause
" Initiate" is used only the identified action or function to occur.
when the action or function can be quickly accomplished by simple operation of controls located in the control room.
to remove from service by closing off the flowpath or breaking Isolate:
the circuit.
Maintain below (or above):
take the action necessary to prevent the value of the parameter from rising above (or decreasing below) the identified limit or action level.
rev. O page 25 of 33 draft
ENCLOSURE 1 (Continued)
DEFINITIONS AND USAGE OF KEY WORDS Maximize:
to increase to the upper allowable or attainable system limit.
Maximum Normal Operating [ parameter):
the highest value of the identified operating parameter which is expected during the full range of normal pla nt operations; values of the parameter exceeding this action level are symptomatic of off-normal conditions which could degrade into an emergency.
Maximum Safe Operating (parameter):
the highest value of the identified operating parameter beyond which required personnel access or continued operation of equipment important to safety cannot be assured; values of the parameter exceeding this action level may directly threaten adequate core cooling, primary containment integrity, equipment important to safety or personnel.
May:
implies permission, but is neither a requirement nor a recomme nd at ion.
Monitor:
observe and evaluate at a frequency suf ficient to remain apprised of the value, trend and rate of change of the identified plant operating parameter.
Multiple: as applied to plant inst ru me nt at ion, more than one but as many as may be conveniently included; independent of sensors, cabling, electronic signal processing, etc., is not required.
Prevent:
take whatever action is necessary to preclude the stated action of occurrence. Where not otherwise qualified or prohibited, this includes jumpering (or opening) contacts in the control logic of system components, deenergizing equipment, or overriding automatic signal s.
Primary containment:
the space enclosed by the drywell and the torus.
Refer: use as a supplement. Perform applicable actions of cited procedures and return to the controlling procedure.
Restore: action necessary to return the value of a plant parameter or the status of plant equipment to the specified state or condition; encompasses an implied instruction to operate whatever systems are available to accomplish this objective.
Return:
complete the step containing the return instruction and then go to the specified previous step of the same procedure.
Shall: denotes a requirement.
Should: denotes a recommendation of a desired or preferred method.
page 26 of 33 rev. 0 draft
ENCLOSURE 1 (Continued)
DEFINITIONS AND USAGE OF KEY WORDS Shutdown: as applied to the reactor. means suberitical; as applied to
~
plant equipment, means remove from service and take action to prevent return to service.
Suppression Chamber:
the enclosed volume of the torus, including the water volume and air space above the water.
Terminate: action to stop or prevent, until instructed otherwise, the stated action, or occurrence.
Trend:
the direction (increasing or decreasing) of the average rate of change of the value of a parameter. Momentary fluccuations in the value particularly over a small range are not considered a trend.
Verify:
use available indication (status lights, direct and indirect values of associated plant and system parameters, etc.) and/or physical observation' to establish that, as applicable, the specified action has occurred or conditions are as stated.
page 27 of 33 rev. O draft
ENCLOSURE 2 OVERRIDE STATEMENT (EVEN NUMBERED /LEFT HAND PAGE) e t
f 29 00001
}*
l1 u rev.O q
4 n
page 22 RPV PRESSURE CONTROL (RC/P)
= s s = = s e s s n e s s s = = = = = ssess OVE RRIDE STATEME NTS s e a s s s e s
RR While executing steps RC/P-2 through RC/P-5:
R a high drywell pressure ECCS initiation signal.18 psig exists.
IF R
THEN prevent injection from those CS and LPCI pumps not required to l
assure adequate core cooling prior to depressurizing below their R
R maximum injection pressures _
R
sse ss sss esse ma ssas s seses. CAUTION es======sseusa mm ass========
R Cooldown rates above 100'F/hr may be required to accomplish this step.
R sesssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssses R
R.
- IF Emergency RP,V Depressurization is anticipated.
l*
R AND l
all control rods are inserted to or beyond position 02.
THEN rapidly depressurize the RPV with the main turbine bypass valves _
R H
H H
IF less than 5 SRVs are open.
i R
AND Emergency RPV Depressurization is required.
3 R
o U
OR I
RPV water level cannot be determined.
H THEN execute step RC/P-7 (page 29)._
l#
l H
o h,
VR l
- IF at least 5 SRVs are open.
i R
R AND R
RPV water level cannot be determined.
R THEN execute step RC/L-4 (page 11).
R torus water temperature cannot be maintained below the Heat Capacity R o IF R
Temperature Limit (see 29 000 02. section TW/T).
oR H
torus water level cannot be maintained below the Torus Load Limit H
X (see ?Q 000 02. Section TW/T).
R THEN maintain RPV pressure below the Limit.
R R o IF Steam Cooling is required.
R THEN esecute step RC/P-6 (page 27).
R R o IF Boron injection is required.
H AND R
the main condenser is available.
AND H
there has been no indication of gross fuel failure OR steam line break.
R THEN open MSIVs by bypassing pneumatic system and few RPV water levet R
isolation interlocks if necessary. to re-establish the main condenser B
R as a heat sink.
R R
R R
R nllu xxx L
u32 rev. O page 28 of 33 draft
ENCLOSURE 2 (Continued)
OVERRIDE STATEMENT (EVEN NUMBERED /LEFT HAND PAGE) 29 000 02
~
rev. O page 20 PRIMARY CONTAINMENT HYDROGEN AND OXYGEN CONTROL (PC/H) asssssssssssssssssssssses OVERRIDE STATEMENTS ass==s======sesssses===ss G
H While executing steps PC/H-1 through PC/H-6.
O H o IF the hydrogen OR oxygen monitoring system is or becomes unavadable.
H THEN sample the drywell and torus for hydrogen and oxygen in H
sceordance with Post Accident Sampling 8. Analysis procedure H
(78 000.14). _
H H o IF drywe:I OR torus hydrogen concentration cannot be determined H
to be below 6%.
O AND G
drywell OR torus oxygen concentration cannot be determined to be below 5%.
H THEN:
X o EMERGENCY RPV DEPRESSURIZATION IS REQUIRED; enter RPV H
Control at step RC-1 (29 000 01, page 3) and execute it concurrently H
with this procedure,_
H H
o secure and prevent operation of drywell cooling fans and recombiners X
(23 415 and 23 409).~
O H
o vent and purge the primary containment, irrespective of H
the offsite radioactivity release rate 6n accordance il with steps PC/H-4.1 through PC/H-4 4 until either:
O a) drywell and torus hydrogen concentrations can be H
determined to be below 6%._
H OR H
b) drywell and torus osygen concentrations can be ll determined to be befow 5%_
H H
li sessassasssssssssssssa OVERRIDE STATEMENTS==sessnes===ssenessssa II H
H H While esecuting steps PC/H-1.1 through PC/H-1.3-H H
H H o IF the offsite radioactivity release rate reaches the H
H offsite release rate LCO.
U R
THEN isolate the primary containment vent and purge H
H (PC Enclosure page 38).
O H
11 H
H H
H H
H H
H H
H H
H H
H H
H H
ll u
H H
H ll xxHxx xxxxx xxx xxxxx x
page 29 cf 33 rev. O draft
ENCLOSURE 3 OPERATOR ACTIONS (ODD NUMBERED /RIGHT HAND PAGE)
C
[.
29 00001
- e rev.O q
ly a page 3 y
q RPV WATER LEVEL CONTROL (RC/L) u s a s s s a s s = = s s e n s s = = s a s s s = = = = = = = = C AUTION = = = = = = = = = = = = = Y= = = = = = = = e s = = = = =
RPV water level indication may be unreliable while executing section RC/L See RC Enclosure, page 3.
========sassess==========ss==============..assass=======sassamass====ss RC/L Monitor and control RPV water level.
RC/L-1 Initiate each of the following which should have initiated. but did not o isolation (23 427) o ECCS (23 201-206) o Emergency Diesel Generator (23 307)
- J A
lA*
4 7
RC/L-2 Restore and maintain RPV water levet between 172 in. and 219 in with one or more of the following systems:
o Condensate /feedwater (23.102/107) o Standby Feedwater (23107.01) o CRD (23106) a s s a s s s e s = = = = = = = = = = = = = s s = = = C AUTION = = = = = = = = = = s s s e n e s s e m a s s a s s s a Operating HPCI or RCIC turbines below 2100 RPM may result in unstable system operation and equipment damage Elevated torus pressure may trip the RCIC turbine on high exhaust pressure.
sessasses===ssessassessassassassassessssssssssssssssssssssssssues o RCIC with suction from the condensate storage tank. defeating low RPV pressure isolation interlocks and high torus water level suction transfer logic if necessary (23 206) o HPCI with suction from the condensate storage tank, defeating high torus water level suction transfer logic, if necessary (23 205)
' 4 t, 97 page 30 of 33 rev. O draft
1
}
ENCLOSURE 3 (Continued)
OPERATOR ACTIONS (ODD NUMBERED /RTCHT HAND PAGE) 29 000 01
~
rev. O page 29 RPV PRESSURE CONTROL (RC/P)
NOTE Step RC/P-7 is a contingency action to control RPV pressure. This step is performed only during degraded plant conditions RC/P-7 WHEN Emergency RPV Depressurization is required.
AND step RC/P-7 is directed to be executed by an Emergency Operating Procedure.
THEN execute steps RC/P-7.1 through RC/P-7.2._
sessanssasessmanessamasses. CAUTION ses=====ssassusasses......
Cooldown rates above 100'F/hr may be required to acommplish step RC/P-7.1.
sesssssssssssssssssssssssssssssssssssssssssemassessemassassanssa 7.1 WHEN either:
Any control rod is not inserted to or beyond position 02.
o AND allinjection into the RPV escept from boron injection systems and CRD has been terminated and prevented.
OR All control rods are inserted to or beyond position 02.
o THEN:
o IF a high drywell pressure ECCS initiation signal.1.8 psig exists.
THEN prevent injection from those CS and LPCI pumps not required to assure adequate core cooling _
o IF torus water level is above -105 in.,
THEN OPEN all ADS valves _
IF any ADS valve cannot be opened AND torus water levet is above -105 in..
THEN OPEN other SRVs until 5 valves are open _
(continued) page 31 of 33 rev. O draft
h ENCLOSURE 4 PAGE ONE OF EOP (ODD NUMBERED /RIGHT HAND PAGE) 29 000 01 rev.O page 1 29 000 01 RPV CONTROL (RC)
PURPOSE Tne purpose of this EOP is to:
o Maintain adequate core cooling.
4 Shut down the reactor, and 0
o Cool down the RPV to cold shutdown conditions (80 F < RPV water temperature 0
< 200 F).
ENTRY CONDITIONS The entry conditions for this EOP are any of the following-o RPV water level below 172 in.
o RPV pressure above 1088 psig o Drywell pressure above 1.8 psig o A condition which requires reactor scram AND reactor power above 3% OR cannot be determined OPERATOR ACTIONS RC-1 IF reactor scram has not been initiated.
THEN initiate reactor scram._
RC-2 Irrespective of the entry conditions. execute the following steps concurrently o RC/L page 3 o RC/P page 11 1
o RC/O page 17 page 32 of 33 rev. O draft
ENCLOSURE 5 EOP ABBREVIATIONS
- ND ACRONYMS
' Abbreviation / Acronym Name AD S Automatic Depressurization System APRM Average Power Range Monitor CRD Control Rod Drive CS Core Spray (System)
ECCS Emergency Core Cooling System E0P(s)
Emergency Operating Procedure (s)
- F Fahrenheit (degrees) ft feet gpm gallons per minute HVAC Heating, Ventilation and Air Conditioning HPCI High Pressure Coolant Injection (System) hr hour HX heat exchanger HCU Hydraulic Control Unit in, inches LCO Limiting Condition for Operation LPCI Low Pressure Coolant Injection MSIV Main Steam Isolation Valve maximum max.
mrem millirem milliroentgon mr min.
minimum NPSR Net Positive Suction Head NE Northeast NW Northwest Percent pci; Pounds per Square Inch RB Reactor Building Reactor Core Isolation Cooling (System)
RCIC Residual Heat Removal (System)
RHR revolutions per minute rpm RPV Reactor Pressure Vessel RPS Reactor Protection System RWCU Reactor Water Cleanup (System)
RSCS Rod Sequence Control System SRV Safety Relief Valve SE Southeast SW Southwest SGTS Standby Gas Treatment System SLC Standby Liquid Control (System) rev. O page 33 of 33 draft