ML18022A501
| ML18022A501 | |
| Person / Time | |
|---|---|
| Site: | Harris  |
| Issue date: | 04/14/1987 |
| From: | Zimmerman S CAROLINA POWER & LIGHT CO. |
| To: | NRC OFFICE OF ADMINISTRATION & RESOURCES MANAGEMENT (ARM) |
| References | |
| NLS-87-078, NLS-87-78, PROC-870414, NUDOCS 8704200284 | |
| Download: ML18022A501 (176) | |
Text
REQU ORY INFORj')ATION DISTR IBUT SYSTEN (R IDS) r ACCESSION NBR: 8704200284 DOC. DATl'=: 87/04/14 NOTARIZED: NO DOCKET FACIL: 50-400 Shearon Harris Nuclear Po~er Plant> Unit 1> Carolina 05000400 AUTH. NhNE AUTHOR AFFILIATION Z INMERHAN> S. R ~ Caro I lna Pohler 8< Ll g h+ Co.
RECIP. NAME RECIPIENT AFFILIATION t (44~ (go~)
SUBJECT:
Rev 1 to "Procedures Gener'a+ion Package. " Il/emergency operating procdures writing guide> verif ication 8< va lida+ion program 5 870414 1 ti .
DISTRIBUTION CDDE: IEBBD COPIEB RECEIVED: LTR J ENCL J TITLE: Emergency Preparedness-Apprai sal/Conf irmatoru Action Ltr/Ex ercise Rep BI ZE: i J (P NOTES: Application f or permit rene@.el filed. 05000400 RECIPIENT COPIES RECIPIENT COP IES ID CODE/NA51E LTTR ENCL ID CODE/NAME LTTR ENCL PD2-1 LA 0 PD2-1 PD 1 1 BUCKLEY, B 1 INTER NAL: ARN/A8(F /LFNB 0 NRR/ADT NRR/DREP/EPB 3 3 NRR/PNAS/ I LRB LE 02 1 1 RGN2 FILE
"/EPRPB 1 EXTERNAL: LPDR 1 - NRC PDR NSIC 1 TOTAL NUNBER OF COPIES REQUIRED: LTTR 15 ENCL 13
E
(
I
C F<f F'0'v'<" ' L,lg'~ CoMp86T APR I< pily SERIAL: NLS-87-078 United States Nuclear Regulatory Commission ATTENTION: Document Control Desk Washington, DC 20555 SHEARON HARRIS NUCLEAR POWER PLANT DOCKET NO. 50-000/LICENSE NO. NPF-63 EMERGENCY OPERATING PROCEDURES
REFERENCES:
- 1) Letter dated August 29, 1986 (NLS-86-318) from A. B. Cutter (CPRL) to Mr. Harold R. Denton (NRC)
- 2) Letter dated October 1, 1986 (NLS-86-379) from S. R. Zimmerman (CPRL) to Mr. Harold R. Denton (NRC)
- 3) NUREG-1038, Supplement 0, "Safety Evaluation Report Related to the Operation of Shearon Harris Nuclear Power Plant, Unit No. 1,"
October 1986 Gentlemen:
Carolina Power R Light Company submits a revised Procedures Generation Package (PGP) for the Shearon Harris Nuclear Power Plant. This satisfies our previous commitments, in the referenced documents, to provide this information to you by April 15, 1987. The PGP contains: 1) plant-specific technical guidelines, 2) writer' guide for emergency operating procedures (EOP), 3) EOP verification and validation program description, and 0) EOP training program description. Each element describes the approach taken as part of the overall EOP implementation plan for the Shearon Harris Nuclear Power Plant.
If you have any questions, please contact Mr. Gregg A. Sinders at (919) 836-8168.
Yours very truly, S. R. Zimmerman Manager Nuclear Licensing Section GAS/lah (5172GAS)
Attachment cc: Mr. B. C. Buckley (NRC)
Dr. 3. Nelson Grace (NRC-RII) gy5 Mr. G. F. Maxwell (NRC-SHNPP) ct', Fayp<tev>'I<('(~pe" ~ + 9 Bar '5~' Rplp>g~ 8 c 27602
v f
r,
PROCEDURES GENERATION PACKAGE SHEARON HARRIS NUCLEAR POWER PLANT UNIT NO. I REVISION I APPROVED: DATE: ~ 8 TITLE'IIIA8EWImrfII<S g704200~284~ 870414 PDR P
- DOC pspQQ4pQ pDR /I
TabLe of Contents Section ~Pa e I. INTRODUCTION A. PURPOSE F
B. SCOPE C. ORGANIZATION II. PLANT"SPECIFIC TECHNICAL GUIDELINES A. GENERAL B. SOURCE DOCUMENTS C. CONVERSION METHOD D. SHNPP EOP NETWORK E. CONVERSION METHOD DOCUMENTATION F~ ERG/EOP TRANSITION DOCUMENT<
III. SHNPP EOP WRITERS GUIDE A. GENERAL B. DOCUMENT DESCRIPTION IV. SHNPP EOP VERIFICATION AND VALIDATION PROGRAM A. GENERAL B. DOCUMENT DESCRIPTION V. SHNPP EOP TRAINING PROGRAM A. GENERAL B. PRE IMPLEMENTATION TRAINING PROGRAM 10 C. LICENSED OPERATOR REPLACEMENT TRAINING 10 D. TRAINING DUE TO EOP REVISIONS VI. ATTACHMENTS 12
- 1. EOP TITLE CROSS REFERENCE
- 2. SHNPP EOP WRITERS GUIDE 1-68
- 3. SHNPP EOP V&V PROGRAM MEM/PROC-PKG Page 2 of 12
OS1 INTRODUCTION
~Bur ose The Purpose of this Procedures Generation Package (PGP) is to describe the Emergency Operating P.ocedures (EOPs) development and revision process at the Shearon Harris Nuclear Power Plant. Shearon Harris Nuclear Po~er Plant is a three loop Westinghouse PWR.
B. ~Sco e This document was developed in response to Generic Letter 82-33 "Supplement 1 to NUREG-0737-Requirements for Emergency Response Capability," item 7.2.b., page 15.
Revision 1 to this document i.ncorp rates comments received during the Operational Readiness Inspection and comments documented in NRC Inspection Report No.
50-400/86-76.
C. Or anization The Shearon Harxis Nuclear Power Plant PGP is composed of the following four elements'.
- 1. Plant Specific Technical Guidelines
- 2. EOP Writers Guide
- 3. EOP Verification and Validation Program Descxiption
- 4. EOP Training Program Description Each element desc'ribes the approach being taken as part of the overall EOP implementation plan for the Shearon Harris Nuclear Power Plant.
II. PLANT SPECIFIC TECHNICAL GUIDELINES A. General Because of the similarity between SHNPP and the High Pressure (HP) reference plant used in the Westinghouse Owners Group (WOG) Emexgency Response Guideline (ERG) development, SHNPP has used the WOG ERGs (HP Revision 1) to develop plant specific EOPs. The High Pressure, Revision 1 ERGs were chosen for SHNPP EOP development for the following reasons'.
MEM/PROC-PKG Page 3 of 12
OSi A General (continued)
- 2. The content and organization of the Revision 1 ERG Background Document is an improvement over the Revision 0 ERG Background Document.
- 3. The Revision 1 ERGs have incorporated comments made by the NRC in the SER on the Revision 0 ERGs.
This section describes the method used to convert the WOG guidelines to plant specific EOPs.
Revisions to the SHNPP EOPs will utilize rhe most recent ERG revision.
B. Source Documents In the conversion process to plant specific EOPs, the following source documents were made available to EOP writers. The Latest revision of these same documents will be made available when the Plant Specific EOPs are revised:
Writers Guide for EOPs HOG generic guidelines and background documents (HP Revision 1)
SHNPP FSAR Plant System Descriptions Plant Operating Procedures SHNPP Technical Specifications SHNPP Piping and Instrument D'rawings Miscellaneous Technical Manuals, Plant Curves, etc., as necessary Setpoint Study C. Conversion Method The goals of the SHNPP conversion process are as follows.
The EOPs are to be technically correct The EOPs are to be easily understood HEM/PROC-PKG Page 4 of 12
OS1 C. Conversion Method (continued)
To accomplish, these goals, the following guidance'as given. to the EOP writers <<hen the EOP project was s=arted:
- l. All- values entered into 'the SHNPP EOPs vill be documented as to source of the number (if a setpoint) or the method of calculation.
- 2. The two column format of the WOG guidelines will be retained for the SHNPP EOPs. In addit,ion, the use of Path Procedures (explained in Section IID) will be used as a part of the EOP Network.
- 3. When a WOG guideline requests pl,ant specific information or actions to be added to the procedure, the information is to be added to the procedure. Ho~ever, iE the operator actions are routine and well within the knowledge of the operator, the specific details may not be included in the procedure.
- 4. If the WOG guideline fails to identify or address actions that are unique to SHNPP, then steps will be included to encompass the necessary actions.
- 5. If a WOG step specifies an action that cannot be performed or is not applicable to SHNPP, the step will be deleted or modified.
- 6. Minor modifications to WOG steps are acceptable without extensive justiEication provided that the change does not alter the intent of the guideline.
When revisions to the SHNPP EOPs are undertaken, the EOP writers will be given the guidance, as listed above. In addition, each procedure change will be evaluated Erom a human factors standpoint. Procedure changes to improve human factors will not require extensive justiEication, provided that the change does not alter the intent of the guidelines.
D. Shearon Harris Nuclear Power Plant EOP Network The SHNPP EOP network is based on the WOG Emergency Response Guidelines. The SHNPP EOP network contains Critical. Safety Function Status Trees, Function Restoration Procedures, End Path Procedures, and PATH Procedures. A cross-reference title listing is shown in Attachment l.
MEM/PROC-PKG Page 5 of 12
OS1 I
D. Shearon Harris Nuclear Power Plant EOP Network (continued)
The Path Procedures incorporate the actions of E"0, "Reactor Trip or Safety Injection", E-l, "Loss of Reactor or Secondary Coolant", and E-3," "Steam Generator Tube Rupture" guidel.ines into two logic tree Path Procedures.
The Path Procedure (flowpath) concept was chosen for the following reasons:
- 1. Path Procedures (flowpaths) make the actions of applicable procedures visible to the operator without having to turn pages.
- 2. Path Procedures (flowpaths) provide the operator with visible guidance which will assist the operator in stabil.izing the plant and bringing the plant to a safe stable condition quickly and consistently.
- 3. Path Procedures (flowpaths) relieve the operator of the burden of memorization of immedi.ate actions because they are incorporated into the Path Procedures. The Path Procedures will be maintained in an area readily accessible to the control room operator.
- 4. The flowpath concept has been adopted by Carolina Power & Light (CP&L) for use at its three (3) nuclear plant sites.
'dditional information on the Path Procedure format and content is contained in the SHNPP Writers Guide (Attachment 2).
E. Conversion Method Documentation To document and track the conversion process, an ERG/EOP Transition Document was created. The ERG/EOP Transition Document consists of the following parts'.
- 1. List of differences between the ERG High Pressure reference plant and Shearon Harris Nuclear Power Plant
- 2. Step deviation document
- 3. Derivations for the instrument values used in the SHNPP EOPs (Setpoint Study)
- 4. WOG/SHNPP "Plant Specific" STEP MATRIX MEM/PROC-PKG Page 6 of 12
OSl Conversion Method Documentation (continued)
.he step deviation Document in part two oi the ERG/EOP Transition Document is used to explain any variance between a SHNPP step and a WOG step.
F. ERG/EOP Transition Doc~ment The following provide's additional details on the contents of the ERG/EOP Transition Document. These documents will be revised, as necessary due to EOP Revisions.
- 1. SHNPP/HP Reference PLant A detailed comparison was made between the generic HP Reference Plant and SHNPP. The results of this comparison revealed the following two major differences:
SHNPP is a 3 loop plant versus a 4 Loop plant for the HP Reference Plant.
SHNPP does not have the High-Head SI Subsystem and the HP Reference Plant does have the High-Head SI Subsystem.
These two differences between SHNPP and the HP Reference Plant do not constitute safety significant changes'.
Step Deviation Document To document the conversion process from the WOG ERGs to the SHNPP EOPs, a step deviation document was developed. The step deviation document consists of the folLowing two (2) sections'.
ERG/EOP step comparison ERG/EOP step instrumentation and controL requirements comparison For each SHNPP EOP step, a step deviation form was prepared. This step deviation form explained any variance between the SHNPP EOP step and the WOG ERG step. In the same manner any variance between the SHNPP EOP step instrumentation and control requirements and the WOG ERG step instrumentation and control requirements was also explained MEM/PROC"PKG Page 7 of 12
OSl F. ERG/EOP Transition Document (continued)
.he step deviation forms document that the
.variances that do exist between SHNPP EOP steps and the WOG ERG steps do not constitute safety significant changes'.
Derivation of Instrument Values For each instrument value used in the SHNPP EOPs, a derivation (including instrument uncertainties) has been developed and documented (Setpoint Study).
- 4. WOG/SHNPP "Plant Specific" STEP MATRIX For each WOG step that recommends the addition of "Plant Specific" information, a Matrix showing the SHNPP step has been developed.
III. EMERGENCY OPERATING PROCEDURES WRITERS GUIDE A. General The Writers Guide (OMM-006) is a plant specific document that provides instructions, on writing EOPs using sound writing principles'n addition to establishing sound writing principles, the Guide helps to promote consistency among the EOPs and their. revisions, independent of the number of EOP writers.
The Writers Guide will be revised, as necessary, based on feedback from operator training and plant experience.
B. Document Descri tion The SHNPP Writer's Guide is provided as Attachment 2.
IV. SHNPP EOP VERIFICATION AND VALIDATION PROGRAM A. General The SHNPP EOP Verification & Validation Program is a plant-specific document that is used to perform V&V on any changes to the SHNPP EOP network.
B. Document Descri tion The purpose of the SHNPP EOP Verification & Validation Program is to ensure the SHNPP EOPs meet the following objectives,'
That the EOPs are technically correct (i.e.'hey accurately reflect the WOG Emergency Response Guidelines).
MEM/PROC"PKG Page 8 of 12
OSi A. General (continued)
That EOPs are written correctly (i.e. they accurately reflect the SHNPP EOP Mriters Gu'de).
~ That EOPs are usable (i.e. they can be understood and followed without confusion, delays, and errors}.
That there is a correspondence between the procedures and the control room/plant hardware (i.e controL equipment/indications that are
~
referenced are available both inside and outside of the control room, use the same designation, use the, same units of measurement, and operate as specified in the procedures).
That the language and level of information presented in the EOPs are compatible with the minimum number, qualifications, training, and experience of the operating staff.
That there is a high Level of assurance that the procedures will work (i.e. the procedures correctly guide the operator in mitigating transients and accidents).
The SHNPP EOP Verification & Val.idation Program is included as Attachment 3.
V. EOP TRAINING PROGRAM A. General The objectives of the Shearon Harris Nuclear Power Plant EOP training is as follows:
- 3. To enable the Operators and STAs to use-the EOPs under operational conditions This section will describe the training conducted prior to implementation of the SHNPP EOPs, the training to be accomplished for replacement operators and training due to revisions for licensed personnel. These programs are governed by approved plant Training Instructions.
MEM/PROC-PKG Page 9 of 12
Osl Pre-Im lementation Trai.nin Pro ram To accomplish, the above objectives and to maximize the effectiveness of the EOP procedures, the EOP procedure training was integrated with the SHNPP Cold License Training Program. The Col.d License Operator Training Program, TI-202A, consists of the following seven (7) major phases:
- 1. Phase I Theory Training
- 2. Phase II System Training
- 3. Phase III Systems O. J. T.
Phase IU SimQl.ator Preparatory Training
- 5. Phase V Simulator Training
- 6. Phase VI General Physics Review and Audit
- 7. Phase VII Preparatory License Review Training The EOP procedure training took place in Phase IU and V. Phase IV is classroom training and.Phase V is simulator training. The Phase IV (Simulator Preparatory Training) training is divided into two (2) parts Phase IVA and IVB. Phase IVA is pre-simulator and procedure training. Phase IVB is Mitigating Core-Damage and Transient and Accident Analysis training.
In Phase IVA, the Operators and STAs received training on all available plant procedures including the EOPs.
In Phase IVB, the Operators and STAs obtained additional training on the basi's for emergency action taken to recover the plant during transient and accident situations.
The Phase V training consisted of nine (9) weeks of training on the simulator, as a member of a shift. The simulator sessions used scenarios to provide the Operators and STAs with symptoms of events which allowed them to become familiar with the use of the EOP network. Each candidate was trained and evaluated in his assigned role. This training was completed prior to initial fuel load and implementation of the EOP network.
C. Licensed 0 erator Re lacement Trainin Reactor Operator Replacement Training is accomplished i.n accordance with TI-201, "Reactor Operators Replacement Training Program"., TI-202 describes training for Senior Reactor Operators.
MEM/PROC-PKG Page 10 of 12
OS1 C. Licensed 0 erator Re lacement Trainin (continued)
TI-201 curren(Ly provides approximately ten weeks of classroom Lectures to review major systems and cover plant procedures, including the EOPs. This is followed by approximately 9 weeks of Simulator and Transient &
Accident Analysis Training as a member of a shift.
During the Simulator Training phase, the EOPs are exercised by the RO candidate as RO. This includes major accidents ncluding multiple and sequential failure scenarios. Any portion of the EOP network that cannot be exercised on the SHNPP Simulator, is discussed as part of the simulator exercise or in the Simulator Differences" lesson.
TI-202, "Senior Reactor Operator Replacement Training Program" currently provides approximately three ~eeks of classroom Lectures to review procedures including the EOPs and their bases. This is followed by approximately four weeks of Simulator Training as a member of a shift. During the Simulator Training phase, the EOPs are exercised by the, SRO candidate as SRO. This includes major accidents including multiple and sequential failures. Any portion of the EOP network that cannot be exercised on the SHNPP Simulator is discussed as part of the simulator exercise or in the "Simulator Differences" lesson.
All license candidates (RO and SRO) are individuaLLy evaluated throughout the training sequence. This consists of periodic written, oral, and simulator evaluations. Prior to the NRC exam, each candidate receives an NRC-type exam, administered by CP&L. This exam is designed .to determine the candidates ability to operate the PLant under normal, abnormal, and emergency conditions, which inclu'des the proper use of the EOPs.
TI-201 and TI-202 may be revised as necessary to ensure that the training programs continue to provide competent replacement operators. This may result in a change in the amount of time devoted to the EOPs. However, these changes will be based on feedback from previous classes and industry "good practices" resulting in improved training on EOPs and other required subjects.
D. Trainin Due to EOP Revisions When a change or revision to the EOPs is initiated, the Operations Engineer wiLL notify the Harris Training Unit Manager, MEM/PROC-PKG Page ll of 12
OS1 D. Traini.n Due to EOP Revisions (continued)
The Harris Training Unit Manager will determine the type of training needed to smoothly implement the EOP change or revision. For minor changes, a pre-shift briefing may be adequate when the change is implemented.
Major revisions which would require extensive training wil.l be coordinated between the Operations Unit and the Training Unit Whenever possible, major revisions wil.l.
~
be implemented during plant outages so that the licensed operating staff can complete the training prior to implementation of the revision. If the revision must be implemented prior to a scheduled outage, the training will be accomplished, for each shift, during that shift's next training week.
Any change or revision to the EOPs that require formal training, will include an evaluation of each licensed individual., once the training is completed.
VI. ATTACHMENTS
- 1. EOP TITLE CROSS REFERENCE
- 2. SHNPP EOP WRITERS GUIDE
- 3. SHNPP EOP VGV PROGRAM MEM/PROC-PKG Page 12 of 12
Os 1 ATTACHMENT 1: EOP TITLE CROSS REFERENCE WOG GUIDELINES TITLE EPP-1 ECA-O.O Loss of AC Power to 1A-SA and 1B-SB Busses EPP-2 EGA-0. 1 Loss of All AC Power Recovery without SI Required EPP-3 ECA-0.2 Loss of All AC Power Recovery with SI Required EPP-4 ES-0.1 Reactor Trip Response EPP-5 ES-0.2 Natural Circulation Cooldown EPP-6 ES-0.3 Natural Circulation Cooldown with Steam Void in Vessel (With RVLIS)
EPP-7 ES-0.4 Natural Circulation Cooldown with Steam Vo'id in Vessel (Without RVLIS)
EPP-8 ES-1.1 SI Termination EPP-9 ES-1.2 Post-LOCA Cooldown and Depressurization EPP-10 ES-1.3 Transfer to Cold Leg Recirculation EPP-ll ES-1.4 Transfer to Hot Leg Recirculation EPP-12 ECA-1.1 Loss of Emergency Coolant Recirculation EPP-13 ECA-1. 2 LOCA Outside Containment EPP-14 E-2 Faulted Steam Generator Isolation EPP-15 ECA-2 ~ 1 Uncontrolled Depressurization of All Steam Generators EPP-16 N/A Deleted EPP-17 ES-3.1 Post-SGTR Cooldown Using Backfill EPP-18 ES-3.2 Post-SGTR Cooldown Using Blowdown EPP-19 ES-3.3 Post-SGTR Cooldown Using Steam Dump EPP-20 ECA-3.1 SGTR With Loss of Reactor Coolant: Subcooled Recovery EPP-21 ECA-3.2 SGTR With Loss of Reactor Coolant: Saturated Recovery EPP-22 ECA-3.3 SGTR Without Pressurizer Pressure Control FRP-S.1 FR-S.1 Response to Nuclear Power Generati.on/ATWS FRP-S.2 FR-S.2 Response to Loss of Core Shutdown FRP-C.1 FR-C. 1 Response to Inadequate Core Cooling FRP-C.2 FR-C.2 Response to Degraded Core Cooling FRP-C.3 FR-C.3 Response to Saturated Core Cooling FRP-H.1 FR-H.1 Response to Loss of Secondary Heat Sink FRP-H.2 FR-H.2 Response to Steam Generator Overpressure FRP-H.3 FR-H.3 Response to Steam Generator High Level FRP-H.4 FR"H.4 Response to Loss of Normal Steam Release Capability FRP-H.5 FR-H.5 Response to Steam Generator Low Level FRP-P.1 FR" P. 1 Response to Imminent Pressurized Thermal Shock Conditions FRP-P.2 FR-P.2 Response to Anticipated Pressurized Thermal Shock Conditions FRP-J.1 FR-Z.l Response to High Containment Pressure FRP-J.2 FR-Z.2 Response to Containment Flooding FRP-J.3 FR-Z.3 Response to High Containment Radiation Level FRP-I . 1 FR-I.1 Response to High Pressurizer Level FRP-I.2 FR-I.2 Response to Low Pressurizer Level FRP-I.3 FR-I.3 Response to Voids in Reactor Vessel PATH-1 E-0 & E-1 Reactor Trip or Safety Injection/Loss of Reactor or Secondary Coolant PATH-2 Steam Generator Tube Rupture NOTE: This cross reference list may change depending on future WOG ERG revisions and plant specific needs.
MEM/PROC-PKG Page 1 of 1
OS1 ATTACHMENT 2 OMM"006 EMERGENCY OPERATING PROCEDURES WRITERS GUIDE
i CARINA PCNER S 'LIGPZ CCMPANY
'SHEARDN HARRIS NUCLEAR PCWER PLAÃr PLPNZ OPERATING MANUAL PROCEZXJRE TZPE: 'PERATIONS MANAGEMENZ MANUAL" NUMEKR: Q9&406 TI'%LE: EMERG~ OPERATING EEDURE WaZTER'S GUIDE REVISION 3 VOW g~
APPROVED Date gc TITLE:
mgf[( 0[gg l0g
.:ri .. c '"OVI'ROLLED COPV No.
Page 1 of 68
OS2 IST OF EFFECTIVE PAGES P~ae 1-68 QR-006 Rev. 3 Page 2 of 68
4 OS2 Section Paae 1.0 PURPOSE 2.0 3.0 4.0 DEFINITIONS ABHKVZATIONS 4 1 CRITICAL'AFEIY FUNCZION 8ZA1US TREES 4.2 EMERGENCY'ESPONSE GUIDELINES
- 4. 3 EMERGENCY'ESPONSE GUIDELINES BAQKRQJM) DOCUMERZ 4~4 END PAIH PROCEDURES 4.5 HXDOVZS 4~6 FUNCTION RESIORATION PROCEDURES 4.7 PLCN PA'IHS 9 4~ 8 PA% GUIDES 5.0 PROCEDURE RGANIZATION AND FOUNT OF ECP 10 5.1 GEMumr, SZRUCnm OF EOP mrWORK 10 5.1.1 Basis of ECP Network 10 5.1.2 Use of Path Guides 11 5.1.3 Use of Foldouts ll 5.2 PROCURE ORGANIZATION AND FOIST OF PLCN PAWS 5.2 5.2.2 1 Designation and Numbering Revision and Authorization ll 12 5.2.3 Format 12 5.2.4 Decision Synbol 12 5.2.5 Action Symbol 12 5.2.6 Caution Symbol 12 5.2.7 Note Symbol 13 5.2. 8 Arrow Symbols 13 CMH-006 Rev. 3 Page 3 of 68
OS2
~~t'n PacCe 5.2 PRXEXSRE ORGANIZATION AND FOR/AT OF FLCN PAIHS (cont.)
5.2.9 Connecting Lines 13 5.2.10 Direction Arrows .13 5.2.11 Entry Conditions 14 5.2.12 Preparation, Mounting, and Location of Flow Paths 14 5.2.13 Revisions to Flow Paths 15 5.2.14 Character Type Size and Line Spacing 15 5.2.15 Use of Color 15 5.3 PROCEDURE ORGANIZATION AND FORtAT QF END PA% AND FUNCTION RESTORATION PRXEDURES 16 5.3.1 Cover Page 16
'.3.2 List of Effective Pages 16 5.3 ' Procedure Body 17 5 '.4 Procedure Identification 17 5.3.5 Page Identification and Numbering 18 5.3.6 Identification of Revised Material 19 5 4 PROCEDKK ORGANIZATION AND FOIST CP PA'IH GUIDES 20 5 4.1 20 5.4.2 20 5.4.3 Guide Identification 20 5~4~4 Page Identification and Numbering 21 5.4.5 Identification of Revised Material 22 5o5 PROCEDURE ORRNZZATION AND FORRT QF 'IHB CRITICAL SAFETZ FUNCTION STATUS TREE PRQGRURES 23 5.5.1 Designation 23 5.5.2 Revision and Authorization 23 5.5.3 Pormt 23 5 5.4 Connecting Lines 23 5.5.5 Preparing and Mounting of Procedures 23 5.5.6 Revision to Procedures 24 5.5.7 Use of Color 24 5+5.8 Use of Shapes 24 CM&406 Rev.~ 3 Page 4 of 68
OS2
~~t'an P~ae 5.7 GENERAL KGTING TEQiHIQUES 25 5.7.1 Page Foroat 25 5.7.2 Step Nunbering and Indenting 25 5.7.3 Step Sequencing 26 5.7.4 Caution Statanents 26 5.7.5 Notes 27 5.7.6 Calculations 27 5.7.7 Referencing and Branching 27 5.7.8 Style of Expression 29 5.7.9 Inst rurrentation Values 31 5.7.10 Identification of Equiprrent, Controls and Displays 32 5.7 ll 5.7.12 Abbreviations, Letter Symbols and Acronyms Level of Detail 32 33 5.7.13 Instruction Step Length and Content 34 5.7.14 Instruction Colurm 35 5.7 '5 Response Not Obtained Colunn 36 5.7.16 Use of Logic Terms 37 5.7.17 Use of Conjuntive AND 6 OR 39 5.7.18 Use of Underlining 39 5.7 '9 Carqonent Identification 40 5 8 PRINZED OPERATOR AIDS
- 5. 8.1 Units of Measure 41 5 8.2 Figure< Table and Attachrrr nt Numbering 41 5.9 MECHANICS OF SZYLE 42 5.9.1 Spelling 42 5.9.2 Hyphenation 42 5.9.3 Punctuation 43 5 9.4 Vocabulary 44 5.9.5 Numerical Values 45 CNH-006 Rev. 3 Page 5 of 68
Section P~cCe 5.10 TYPING FOMAT 45 5.10.1 Page Arrangement 45 5.10.2 Heading and Text Arrangement 46 5.10.3 Breaking of Words 46 5.10.4 Botation of Pages 46 5.10.5 Printed Operator Aids 46 5.10.6 Typing Rules for Tables 47 5.10.7 Cautions and Notes 48 5.11 USE OF OPERATOR AIDS 48 5.11.1 Checkof fs 48 5.11.2 Supporting Material/Background Material 48 5.12 49 5.12.1 A Change to the Emergency Operating Prccedures Is Identified 5.12.2 Generic Changes to the Emergency Response Guidelines 49 5.12 3 Processing an Emergency Operating Procedure C2 ange 50 5.13 VERIFICATION AND VALIDATIONPRCGRAM FOR CHANGES TO THE SHNPP EOP 6.0 ATVCfREMPS 52 6~1 COVER PMR 53 6.2 FLCN PA& EfANKE 6.3 PMH SYMBOLS 55
- 6. 4 PAGE FORMAT 6 5 CSFST EXAMPLE 57 6.6 AUHQRIZED VEBB LIST 58 CMM-006 Rev. 3 Page 6 of 68
OS2 1.0 The purpose 'of this docunent is to provide administrative and technical guidance for the pre~ration of EOPs for the Shearon Harris Nuclear Power Plant (SHNPP). This writer's guide applies to the writing of all Emergency Operating Procedures (EOPs) . The information contained in the EOPs should be canpatible with the information contained in other plant procedures that support the EOPs.
2.0 NUREG-0737 Noveaher 1980, "Clarification of the TMI Action Plan Require@ants."
NUREG-0737, Supplement 1, Deceaher 17, 1983/ "Requirenl.nts for Emergency Response Capability."
NUREG-0899, August 1982, "Guidelines for the Preparation of Emergency Operating Procedures."
INPO 82-017, July 1982, "Emergency Operating Procedures Writing Guidelines."
Westinghouse Owners Group Emergency Response Guidelines, High Pressure Version AP-005 Procedures Fornat and Preparation AP-600 Plant Change Request 3.0 RESPONSIBI ITIES The Manager - Operations is responsible for ensuring that Emergency Operating. Procedures are written in accordance with the instructions in this procedure.
4.0 DEFINITION AB TIONS 4.1 FUNCTION AKJ TREES The Critical Safety Function Status Trees (CSFSTS) are a set of six flow paths (one path for each critical safety function) mounted on a single board and kept in the control roan. The Critical Safety Function Status Trees allow a control roan operator or shift technical advisor (SIA) to systematically and explicitly determine the safety status of the plant during a casualty, and to dirmt the operator to the appropriate Function Restoration Procedure (FRP) if necessary.
CHM-006 Rev. 3 Page 7 of 68
EMERGENCY RESFONSE GUID INES The Emergency Response Guidelines (E~) are a generic guide for writing plantmpecific EOPs. They mre prepared by the Westirighoush Owner's Group (HOG) for use by individual plants to write enargency procedures that allow the operator to mitigate the consequences of an errergency without first having to diagnose the event causing the emergency.
4 ' EMERGENCY RESPONSE GUID INES BACKGRCUN) DOCUMENr The Emergency Response Guideline Background Document provides information on the analysis and reasoning used to create the E~.
The Nestinghouse Amer's Group prepared the Background Document for documenting KG developnent and for use as a learning tool by the individual plants.
4.4 END PARi PROCEDURES End Path Procedures (EPPs) are a set of event specific recovery
'he procedures developed from the Event Specific Guidelines and the Emergency Contingency Action Guidelines contained in the KGs. The EPPs are kept in the control room and used by the operator to provide the optimun recovery actions. They are entered based on plant conditions, either directly, fran the Flow Paths, Foldouts, or Function Restoration Procedures.
E~DOUI'S The Foldouts are a set of tim independent procedures for use by the control room operator while in an EOP. The EOP states which Foldouts apply to that EGP. Any applicable Foldouts are copied on the reverse side of all text pages of tbe appropriate EPP. Foldouts used by the Flow Paths are included on the Flow Path boards.
4.6 FUNCTION RESTORATION PRQCEDU1KS The Function Restoration Procedures are a set of recovery procedures kept in the control room and used by the operator to respond to challenges to the plant critical safety functions. The FRPs are written to restore the critical safety functions independent of the event scenario. The FRPs are entered via the Critical Safety Function Status Trees, Flow Paths, or End Path Procedures.
CNH-006 Rev. 3 Page 8 of 68
OS2 QQ/ PA'IHS The Flow Paths (PA'IH-l and PA'IH-2) are a set of board munted procedures kept in the control room which the op.rator uses following a rector trip oz safety injection. PA'IH-l deals with a Reactor Trip or Safety Injection (ERG E-0) and Loss of Reactor or Secondary Coolant (EBG E-l) . PA'IH-2 deals with a Steam Generator Tube Rupture (EBG E-3). The Flow Paths are designed to provide the operator with a smooth transition into the appropriate EPP or FRP using a systematic diagnosis of symptoms.
4.8 PA'IH GUIDES The Path Guides are the written basis for PA'IH-l and PA'IH-2 and are used by the control zoom operators to support the Flow Paths if necessary. The Path Guides are attaehrrents to the User's Guide, which is kept in the control roan.
CHN-006 Rev. 3 Page 9 of 68
OS2 5~ 0 PROCEDURE ORGANIZATION AND FORA,T OF ECP NE'IWORK 5~1 GENE STRUCIURE OF EQP NE'IWORK 5.1.1 Basis for the E Network The EOP network is based on the Westinghouse Owner's Group Emergency Response Guidelines (ERGs). The ERGs are a syaptan-based procedure network which was developed as an integrate procedure network. The following items explain the use of the EOP network as an integrated network.
I The EQPs are an integrated procedure network with a ccamun entry point based on either a Reactor Trip or Safety Injection. Chce the EOP network is entered, all further procedure transitions within the EOPs will be specifically directed. The EOP network prioritizes the operator actions and eliminates the situation where different EOPs est be iapleaanted concurrently.
20 The EQP network will direct the operator to different procedures depending on the event in progress (e.g. LOCA, SZR, Spurious SI). Since different events will cause different procedure transitions to be made, the delineation of immdiate and subsequent actions is not made.
- 3. Verification of autceatic actions for different events are covered by different methods depending on when in the overall transient the autanatic actions might occur. Since the KPs are an integrated procedure network which prioritizes the operator's actions< t;he operator will be directed to check the autanatic actions when appropriate.
- 4. The Westinghouse Owner's Group Eaargency Response Guidelines identify three (3) procedures as having immediate actions.
three '(3) generic procedures are:
- a. E-O, 'Reactor Trip or Safety Injection"
FR-S.1, Response to Nuclear Power Generation/MWS'06 Rev. 3 Page 10 of 68
GENE STRUCIURE OF EOP NEIWORK (cont.)
l All the actions identified generically as iaanediate actions are contained on PA'IH l. All these actions are rea3ily available to t%
operator on the Flow Paths and are not identified as immediate operator actions.
5.1.2 Use Of Path Guides The Path Guides are the two-column format type procedures that are equivalent to PATH-1 and FATH-2. They are provided both as a training tool, and as a supple@ant to the Flow Paths. Due to size limitation< sane detail is sacrificed on Mat indications are used to verify a given step ccmplete on the Paths. This additional detail is provided in the Path Guides.
Use Of Foldouts '.1.3 The EOP network uses Foldouts as unique procedures applicable to only the EOP network. Each Foldout contains operator actions that are tiaa independent (i.e. the operator action should be performed whenever the given conditions are satisfied). When a Foldout applies to an EGP, the applicable Foldout will be identified at the beginning of the EOP.
The applicable Foldouts will be copied on the reverse side of all text pages of the appropriate EPPs. Foldouts used on the Flow Paths will be located in the lower right hand corner.
5.2 HKCEDURE 0 ZATION AND FORtAT OF PA'IHS 5.2.1 son and Nunberin Each Flow Path shall be uniquely ident[fied (see Attmhnant 6.2).
This identification permits easy administration of the process of procedure preparation< review, revision, distribution and operator use. There shall be site identification but no unit identification for the Flow Path. Each Flow Path will be labeled with its associated Flow Path nunher blocked in the upper left area (see Attachnant 6.2).
~
CNH-006 Rev.~ 3 Page ll of 68
0 OS2 5.2 PRXXDURE ORGANIZATION AND FOWAT OF PA'IHS (cont.)
I 5.2.2 Revision and Authorization Each Flow Path shall include the current revision nurrber, approval date and authorized signature. This information shall be located at the upper right of each Flow Path (see Atta=hmnt 6.2).
5,2.3 Format The Flow Paths will utilize logic synhols arranged in a "decision tree" format as shown in Attachaant 6.2. The symbols should be arranged leftWo-right, top-to-bottan in order to correspond to natural reading covenant. Unnatural d'avenant should be minimized, but may be used if necessary to avoid crossing of lines or provide efficient utilization of space. Directional arrows will be used to aid the operator. All symbols will be entered fran the top. The average vertical separation between syabols will be approximately 3/8 inches. The average horizontal separation between symbols will be approximately Ij'2 inches, with an absolute minimum of 3/16 inches.
5.2.4 1 The decision syabol is a dianend shape of approximately 1 1/2 x 13/16 inches. The decision symbol will contain a question which the operator is to answer YES or K). Normally, a YES anger will exit the decision symbol from the bottom and a NO arear from the right side. There may be cases where the nornal YES and 83 exits cannot be used due to board space limitations or to avoid flow lines crossing.
The words "YES" and "M" will be displayed next to its corresparding exit from the decision syabol. Qoestions used in decision symbols shall pertain to a plant paranater, setpoint, switch position, or system condition. Attach~t 6.3 gives an example of the syabol.
The action syabol is an elongated oval shape of approximately 1 V'2 x 4'2 inches. The action symbol will contain a specific action or verification to be performed by the operator. Attmhnent 6.3 gives an example of the syabol.
5.2.6 Cau on The caution symbol is an enlongated hexagonal shape of approximately 1 i/2 x 13/16 inches. The caution symbol will contain critical infornation to assist the operator in diagnosing plant conditions.
It will be placed imnediately before the step to which it applies.
Attachment 6.3 gives an exanple of the symbol.
CNH-006 Rev.~ 3 Page 12 of 68
OS2 5.2 . FRXEDURE ORGANIZATION AND POPRT OF PA'IHS (cont.)
5.2.7 Note Svnbol .
The note symbol is a rectangular shape of approximately 1 4'2 x 1/2 inches. The note synbol will contain information less critical than cautions, but still needed to assist the op rator in performing Plow Fath steps. It will be placed immediately before the step to which it applies. Attach@ant 6.3 gives an example of the symbol.
5.2. 8 Arrows will be used to direct the operator between Flov Paths< EPPs, FRPs, and Foldouts. Large shaded arrows denote Flow Path entry points, while large unshaded arrows denote Plow Path to Flow Path exit. points. The small unshaded arrows denote Flow Path exit points to the EPPs and FRPs.
Exit arrows will contain the destination procedure nuaher (e.g. EPF 5, FRP-H.lt PATH-1). In addition,'he Flow Path to Flow Path exit arrows vill contain a letter identifier. Destination procedure titles are not given on the Flow Paths due to space limitations.
Entry arrows will contain only a letter identifier. Atta:hnLnt 6.3 gives examples and size limitations of the Plow Path arrows.
Entry point arrows will be located bawd on minimizing clutter on the Flov Paths.
5.2.9 Connect 'nes Line width used on the Flow Paths will be approximately 3/32 inches.
The operator should follov this line always entering the symbols at the top and exiting the symbols at the side or bottan.
No line shall cross or intersect on the Flow Paths; however, two or narc lines may enter the sana symbol.
Normal spacing between parallel lines vith different destinations will be a miniaaun of Q4 inches. Parallel lines that go to the sane destination vill be grouped closer together in order to prevent confusion with lines going to different destinations. These lines vill have a minimnn of 1/16 inches separation.
5.2.10 D'recti ows Directional arrows will be used on'connecting lines to prevent operator confusion when folloving long connecting lines which may be parallel to other connecting lines. Directional arrows on grouped lines will be ganged. Attachrant 6.3 gives examples of connecting lines, directional arrows and ganging of directional arrows.
CNN-006 Rev. 3, Page 13 of 68
5,2 PROCEDURE ORGANIZATION AND FOR4AT OF PARiS (cont.)
5.2.11 Ent Conditions The entry conditions for the entire EOP network will be one of the following:
- l. "ANY REACTOR TRIP OR SAFETY INJECTION ACIUATION" or
- 2. "ANY CONDITION REQUIRING REACTOR TRIP OR SAFETY INJECTION ACHRTION".
Once the entry condition is met, the operator will enter the PARi-1 entry point in the upper left hand corner.
5.2.12 Pre rat' Nountin and t'on o Flow Paths Flov Path boards vill be kept in an easily identified and a:cessed location in the control roan.
The Flov Paths will be vaunted front and back on a single board.
Symbols and connecting lines will be professionally drawn using standard drafting instruments.
The Flow Paths will be aaunted on styrofoam or other lightweight boards (approximately 2 x 3 feet). Each board vill be laminated or covered vith a lightweight, glaze-resistant plastic material.
Consideration vill be given to readability under normal and'eaargency lighting conditions.
OHH"006 Rev. 3 Page 14 of 68
5.2 PRXZDURE ORGANIZATION AND FORMAT OF PATHS (cont.)
5.2.13
~ ~ Revisions to. Flow Pat Flow Path revisions require the sane administrative controls as all other EOPs. Revision lines will not be drawn on the Flow paths to prevent confusion with connecting lines. When a Flow Path is revised,. its corresponding Path Guide will be revised and the revisions noted in the Guide.
5.2.14 Character S'ze and ine in The type size on the Flow Paths may vary depending on space available for printing a given item. However, the pitch should not be greater than 18 characters per inch. All capital letters will be used except for plurals of abbreviations (e.g. MSIVs< RCPs}.
Spacing between lines of type inside the Flow Path syabols will be no less than single spacing and no more than double spacing. Incre~s vill be limited by available space within the synbols. Text spacing will be consistant within all spools.
5.2.15 Black syabols and characters on a white background will be used for the Flow Paths. No other coloring will be used.
CNH-006 Rev. 3 Page 15 of 68
PRtXEDURE ORGANIZATION AND FOIST OF END PA& AND FUKTION RESIQRATION 5.3.1 Cover PacVe Every End Path Procedure (EPP) and Function Restoration Procedure (FRP) shall have a cover page (see Attaehaant 6.1). The primary purposes of this cover page are (1) to identify the procedure and (2) to identify the authorized revision. The cover page will contain the following miniraun information:
- 1. The full nane of the'lant.
- 2. The procedure type followed by the abbreviation in parenthesis.
- 3. The procedure number.
- 4. = The procedure title.
- 5. The latest revision nunber which applies to any part of the procedure.
- 6. The signature and title of the person approving the latest revision.
- 7. The date on which the latest revision of the procedure was approved.
5.3.2 of Eff t've Pa es Each End Path Procedure and Function Restoration Procedure will contain a List of Effective Pages as an aid to procedure validation.
The List of Effective Pages will list each page of the procedure versus the current revision number for'hat page. Consecutive pages bearing the sana revision number may be grouped together.
E~+e:
p s Qgv~jgn 1 through 9 10 through 16 The List of Effective Pages will inaediately follow the Cover Page.
CHH-006 Rev. 3 Page 16 of 68
PRXZDURE 0 ZATION AND FORRT OF END PA'IH AND FUKTION RESIORATION HCCEDURE (cont.)
Procedure Bod The body of each End Path Procedure and Function Restoration Procedure will be structured to include the following sections:
- 1. Purpose/Entry Conditions
- 2. Operator Actions 5.3.4 P ocedure Ident ficat'on Proper identification of procedures is necessary to avoid errors in selection and implemntation. Cceplete identif ication of a procedure includes its title< nerber and type.
- 1. Procedure Title
- a. Each procedure will be given a title which accurately reflects its intended purpose. Within this constraint, procedure titles should be kept as short and concise as possible.
- b. The procedure's title will be repeats at the top of ea:h successive page after page 2. No other car~ver information will be supplied.
- 2. Procedure Numbers Each procedure will be assigned a unique and peraanent neer within its associated book or volume of the Plant Operating Manual. Wtmnever a procedure is deleted, the asscciated procedure nunber will not normally be reassigned for the ensuing 2~ar period. If reassignment is made within this period, consideration should be given to user retraining to avoid confusion or error.
CNH-006 Rev. 3 Page 17 of 68
OS2
- 5. 3'VKCEDURE ORGANIZATION AND FOIST OF END PA'IH AND FUtZTION RESIORATION PMXEDURES (cont. )
- 3. Procedure Type The procedure type will be the title or abbreviations of the book or volume to which the procedure is assigned as chtermined by the Plant Operating Manual Master Index.
5.3.5 Pa e Ident'ficat'on and Numberin Each page of each procedure will bear the procedure designation and current revision number on the bottaa left hand side (except for the cover page) t and page nunher on the bottan right hard side. The top left hand side of each page will bear the disk reference number.
This will be done in accordance with AP-005.
- 1. Procedure Designation This will be a 2~rt designation in the formt:
EOP-XXX~
XXX: Procedure Type Abbreviation:
o End Path Procedure - EPP o Punction Restoration Procedure - FRP NNN. Procedure Number:
o 005 o H.3 Examples:
- a. E~PP-005 - The fifth in a series of EOP End Path Procedures.
- b. KP-K~I.3 - The third in a series of ECP Function Restoration Procedures for a Loss of Beat Sink (B).
CHH-006 Rev. 3 Page 18 of 68
5.3 PROCEDURE ORGANIZATION AND FOIST OP END PA~ AND FRZTION RE RATION PROCEDURE (cont.)
- 2. Revision Nunher
. This information will be supplied in the formt:
Rev. YY Where "YY" is the 1 or 2-digit nunher of the current revision for the associated page.
- 3. Page Nunber The page nuaber will appear in the foraat:
Page of ~Z Where "ZZ" is the total nuaber of pages. The last page of instzuctions will have the word "- EM) -'ollowing the last instzuctional step, and "FINAL PNZ'ust above the page nunber. If pages are added to a procedure, a cmplete renuabering of all pages will be acaoaplished.
5.3.6 I nt'ficat'on o 'eri Revised material will be identified with a heavy vertical bar in the right-hand margin opposite the revised text. Vertical bars fran any previous revision to the sane page will be deleted.
Marking of revisions will not normally apply to:
o Page identification data o Cover page data o List of Effective Pages o Deleted pages o Data shifted without modification of contents or sequence, as in data shifted to allow for insertion of a paragraph can result in revised pages with no vertical marking.
o Correction of typographical or semantical errors CNN-006 Rev. 3 Page 19 of 68
OS2 5.4 PROCEDURE ORGANIZATION AND FOR(AT OF PA'IH GUIDES 5.4.1 Covei ~acVe Each Path Guide shall have a cover page (see Attachment 6.1). The primary purpose of the cover page is to identify the procedure. The cover page will contain the following miniraan information:
I
- 1. The full nane of the plant.
- 2. The Guide type followed by the abbreviation in parenthesis.
- 3. The Guide number.
- 4. The Guide title.
5.4. 2 gu~de~y The body of each Path Guide vill be structured to include the folloving sections:
- 1. Purpose/Entry Conditions
- 2. Operator Actions 5.4.3 'f 'cat n Proper identification of procedures is necessary to avoid errors in selection and inplemntation. Gxrplete identification of a procedure includes its title, nuzber and type.
The Path Guides are attach~ts to the EOP User's Guide and their usage is discussed in the User's Guide. The User's Guide is identified using the normal administrative record.reagents for Plant Operating Manual procedures.
Q%-006 Rev. 3 Page 20 of 68
OS2 5.4 PROCEDURE ORGANIZATION AND FOMAT OF PA'IH GUIDES (cont.)
5.4.4 Pa e Identification and Nunberin Each page of each Path Guide will bear the procedure designation and current revision nunher on the bottan left hand side, and page number on the bottan right hand side. The top left hand side of each page vill bear the disk reference number. The top center of each page will have the Path Guide title. The attmhnant page nmrber will be in the top right hand corner. This will be cbne in accordance vith AP-005.
- 1. Procedure Designation This will be a 2-part designation in the format:
EOP- USER'S GUIDE
- 2. Revision Number This information vill be supglied in the format:
Rev. YY Where "YY" is the 1 or 2&igit number of the current revision for the associated page.
- 3. Page Qmber The page nuttier vill appear in the format:
Page of ~
Where "ZZ" is the total number of'ages of the procedure or attachment as appropriate. The last page of the Guide instructions will have the word '- EQ) -" following the last instructional step. If pages are added to a procedure< a conplete renmbering of all pages will be accoaplished.
- 4. Path Guide Title PMH-X GUIDE Where "X" is the Plow Path number to which the Guide applies.
CNH-006 Rev.~ 3 Page 21 of 68
OS2 5.4 PRQCEDKK ORGANIZATION AND PORtAT OF PA'%UIDES (cont.)
5.4.5 Identificat'on of Revised Material Revised material. will be identified with a heavy vertical bar in the right-hand margin opposite the revised text. Vertical bars from any previous revision to the sane page will be deleted.
Marking of revisions will not normally apply to:
o Page identification data o Cover page data o List of Effective Pages o Deleted pages o Data shifted without modification of contents or sequence, as in data shifted to allow for insertion of a paragraph can result in revised pages with no vertical marking.
o Correction of typographical or semantical errors CNN-006 Rev. 3 Page 22 of 68
OS2 5~5 PROCEDURE ORGANIZATION AND FORMAT OF 'HK CRITI SAFE'IY FUNCTION TUS TREE PROCEED The Critical Safety Function Status Tree (CSFST) procedure shall be uniquely identified. This identification permits easy administration of the process of procedure preparation, review, revision, distribution and operator use. There shall be site identification but no unit identification for the CSFST procedure.
5.5.2 Revision and Autho ization The CSFST Procedure shall include the current revision number<
approval date and authorized signature. This information shall be located at the upper right of the procedure.
5.5.3 Format The CSFST procedure will use a decision tree format designed to aid the operator in systematically determining the status of the plant's Critical Safety Functions and direct the operator to any Function Restoration Procedure needing to be inplenented.
5.5.4 ect' es There shall be one basic line width used to guide the operator through the CSFST procedure.
All lines are equally important. They represent the many different conditions which the plant could be in.
5.5.5 P e rin and Mount' Proced es The CSFSTs will be aeunted front and back on a single board.
CSFST procedures will be professionally drawn using standard drafting instamants.
The CSFST procedure will be naunted on styrofoam or other lightweight boards (approximately 2 x 1.5 feet) . Each board will be lancinated or covered with a lightweight< glare-resistant plastic material.
Consideration will be given to readability under normal and energency lighting conditions.
CNH-006 Rev. 3 Page 23 of 68
5.5 PROCEDURE ORGANIZATION AND FOFHAT OF THE CRITI SAFETY FUKTION GUS TREE (cont. )
5.5.6 Revisions to Procedure The revision process for the CSFST procedure requires the sana administrative controls as all other Emergency Operating Procedures.
5.5.7 Use of Color Color will be used on the CSFSI's to increase the operator's awareness of challenges to the plant critical safety functions. The four colors are used as follows:
Red - Highest challenge to critical safety functions. This condition requires immediate action.
Magenta - Next highest challenge. This condition requires imnediate action unless a higher challenge exists.
Yellow - Lowest challenge. This condition does not require imnediate action, but the operator will use his judgeaant whether or not to iapleaant the asscciated FRP.
Green No challenge. The critical safety function is satisfied.
The colors are contained in the CSFST terminus points and the Pressurized Ttmrmal Shock graph.
The CSFSPs will have a horizontal decision-tree format (see Attachment 6.5). Each possible condition will terminate in a colored circle that indicates CSF status and directs the operator to the appropriate FRP if required. The colored circle will also use a "shaded pie" aethod to further enhance the different levels of challenge:
Enpty green 4'3 shaded yellow - Lowest challenge 2/3s shaded magenta - Next highest challenge All shaded in red - Highest CSF challenge CNH-006 Rev. 3 Page 24 of 68
'ZNE WRITING TECHNI S The following section provides a set of standards which will he considered in the preparation of EOPs. In considering these guidelines, writers should keep in mind that sane are rxire irrportant than others. The writer should always consider the conditions under which the procedure will be irrplerrI nted, the tirre available for its, implenantation and the possible consequences of erroxs in implerrentation.
dual~luna format will be used for the EPPs, FRPs, and the Path A
Guides. The left~ colunn is designated for operator actions and the right-hand column is designated for contingency actions to be taken when the expected response is not obtained. A san@le page format is presented in Attachrrant 6.4. The Foldouts will use single colure format. The general appearance of procedural pages contribute significantly to comprehension and the elimination of confusion and error. Information on pages will be displayed with rrrinimum clutter<
sufficient spacing between lines and adequate margins. Hargins will be sufficient to ensure that binding will not interf'ere with reading the text and that subsequent reproduction will not cut off any of the pxocedure ccatent or page identif ication.
Instructional steps rmst be readily identif~le by the user. Step numbering and indenting are both used to assist procedure users in keeping track of step sequence and subordination. The following guidelines apply to numbering and indenting:
- 1. Roman nurM.rais will not be used in step nurrhering.
- 2. The same step numbering and indenting scheme will be applied consistently to all procedures.
- 3. The acceptable alpha-numeric numbering scherre is:
a0 (a)
- 4. Numbering and indenting beyond the sublevels of the example above should not be used. To do so leads to "vertical'eading and loss of continuity. If necessary, procedures should be reorganized to produce an acceptable nunher of sublevels.
OHN-OQ6 Rev. 3 Page 25 of 68
GENE WRITI TECHNI S (cont.)
- 5. If sequence of performance of substeps is inportant, then these substeps are designated by the appropriate alpha-nunaric scheme.
If sequence of performance is not inportant,- the substeps are designated by bullets (o) .
Instructional steps will be presented in the sequence most appropriate for the situation. The following guidance should apply in priority as listed:
- l. The steps should be presented in the order in which they must be performed (normally as listed in the WOG ERGs) .
- 2. Steps should be structured to minimize the physical interference between personnel moving around the Control Roan Wile carrying out procedure steps.
- 3. Steps should be organized and sequenced so operators are not overloaded or underutilized (e.g. alternate actions of RO and EGP operator) .
- 4. Steps should be structured to avoid unintentional duplication of tasks.
- 5. Steps should be written so that they can be performed with the f
miniman Control Room staf ing.
5.7.4 Caut'on Statements A caution statenant denotes a potential hazard to equipment or personnel associated with the subsequent action step. Cautions shall extend across the entire page and shall be highlighted as shown in .
the example below. Each, caution statemnt will be located irmediately before and on the sane page as the applicable step. This placeaant of cautions ensures that the operator observes the caution before performing the step. Caution statarants will not contain action steps.
Example CAVHON:
- A*****%*********************ixf'4V44444444%4k4A****A**********************
Damage to ARM level is low.
pcs may occur if no alternate mter source is located when CST
- +****************+*A***********A**%***A***4*****A***
CH4-006 Rev. 3 Page 26 of 68
OS2 5.7 WRITQG TECHNI S (cont.)
5.7.5 Notes A note provides descriptive or explanatory information not as critical as a caution state@ant, but still intended to aid ~rsonnel in performing a subsequent action step. Notes shall exterd across the entire page and shall be highlighted as shown in the exarrple below. Each note will be located imnadiately before and on the sare page as the applicable step. Notes will not contain'action steps.
Example t47ZE:
NOXE: RCPs should be run in order of priority to provide normal pressurizer spray.
5.7.6 c at'ons Mathematical calculations shoul'd be avoided in ECPs. If a value must be determined in order to perform a procedural step, a chart or graph should be provided.
5.7.7 Referencing is the use of additional procedures, attachments, or steps as a suppleaant to the procedure presently being used.
Referencing other steps within the procedure in use should be mirmnized. When only a few steps are involved in the referencing, the steps should be stated in the procedure whererer they are needed.
Referencing is generally used to a:coaplish required actions for which a standard procedure already exists. Referereing allows the operator at the control board to perform tasks in parallel with EOP mitigation actions.
Referencing examples:
Establish conditions for running RCPs using QP-100, 'RQ~R CDCLAMI'YSXEN" while continuing in this procedure.
~07> 'NDRSK, RAMP CDCUXNN" should be refereraed during this procedure.
CMN-006 Rev. 3 Page 27 of 68
I OS2 5.7 GENE will use WRITING TECHNI In the first*example above, S
OP-100 (a procedure he and the Balance of the second example, (cont.)
it is expected that the Reactor Operator is already familiar with) and accomplish the specified actions while the Senior Control Operator Plant Operator continue on with EOP actions. In the operator can use GP-007 if he needs it.
Referencing in this manner also has the advantage of reducing the physical content of the EOP network. Because the examples may appear in nunerous locations throughout the EOP network, repeating the guidance of OP-100 or GP-007 in all these locations would not be efficient. Referencing will be a:cceplished by the use of the following words:
Reference ...
Refer to ...
Use ~ ~ ~
Using o ~ ~
Branching is when the operator leaves one procedure and goes to another procedure, or goes to another step within a procedure.
Branching will be done with the words "8) TO " "RETURN TO " or "Continue with." The operator will know to leave the present step and not return unless directed by the words "RZ"IURN TO<" or to go back and perform skipped steps when conditions are aat fallowing a "Continue with. "
When branching within a procedure, no procedure nunher and title will be given because it is understood that the cattmand applies to the current procedure. When branching to other ECPs, the procedure nunber, procedure title, and the step nuaher should be given. The exception to this is in the Flow Paths where only the procedure nunber is required; the title is not given due to space limitations and the step nuaher is not given because the operator understands to go to Step l when branching from the Paths.
procedure nuaber and title are adequate references.
When referencing, the Quotation marks will be used to emphasize the title of the referenced or branched procedure.
Branchiag examples:
GO TO EPP-20t LOCA CVlSIDE COMrAQWENTg" Step 1 GO TO Step 9.
RETURN TO Step 16.
Continue with Step 19.
perform Steps lEb, c, and d.
~ pressure less than 2000 psig, 'Qgg CHH-006 Rev. 3 Page 28 of 68
5.7 WRITING THCHNI S (cont.)
5,7,8
~ ~ St le of ress'on Style of expression refers to the way in which instruction steps. are written. Instruction steps will be written in a style that presents information in a simple, familiar and clear manner. The following guidance should be followed:
.l. Use words that are conman in ordinary conversation.
- 2. Use terms personnel are trained to use and which are standard in the industry.
- 3. Use action verbs that describe exactly what the user is to do.
Ensure that these verbs are understood and used consistently throughout the procedures. San@les of action verbs are given in Attachment 6.6.
CNH-006 Rev. 3 Page 29 of 68
5.7 GENE WRITING TECHNI S (cont. )
- 4. Capitalization used in the End Path and Function Restoration Procedures for emphasis will be limited to the following cases in order to avoid overuse:
- a. Logic terms will be capitalized and underlined (e.g. IF
...THEN'NDg OR) ~
- b. The words "AND" and "OR" will be capitalized but not underlined when used as conjunctions.
- c. Expected responses are capitalized (e.g. Verify pressure SZAK E) ~
- d. Titles of procedures will be capitalized (e.g. NEURAL CIRCULATION COOLDCNN, etc.) .
- e. Abbreviations are carmunly capitalized. Plurals for abbreviated carponents will end in MSZVs) .
l~r case (e.g. RPa,
- f. The branching words "(D TO" and "RE'IURN KP will be capitalized.
- g. The first letter of every word in every high level instruction in the instruction coluaa will be capitalized.
- 5. When there are two or narc cbjects of an action verb< list them below the instruction step rather than. in the step. Alpha-nurraric substeps or bullets are not used in this case.
Example: Open the following valves:
lCS-240 1BD-10
- 6. Avoid adverbs that have imprecise rrsanings.
B~Q.e: Use "every 5 minutes until ..." rather than
'frequently until ...".
I CNH-006 Rev. 3 Page 30 of 68
OS2 GENE WRITE@ TEClBC S (cont.)
- 7. Use short direct sentences. Establish a style of sentence construction suitable for the prccedure type and use consistently.
it
- 8. Instructions steps will be limited to one required action wherever possible. Where two actions are included in one step, use the connective AND rather than two senterees.
- 9. Action steps should be written as directives.
Example: Use 'start one CSIP ..." rather than "one CSIP should be started ...".
- 10. Phrases such as "Check If" should not be used since the If is redundant.
- 11. When using phrases such as "as necessary'r 'as guidance to clearly define when or why the actions are required,'rovide necessary oz required.
- 12. Action steps should contain carplete instructions that clearly define what is to be done.
- 13. Action steps can vary in type (verification, continuous or periodic, alternate actions ~eptable, concurrent with other steps). When writing an action step, its type is determined by content, not format.
5.7.9 Inst ntat'on V ues When specifying instrunantation values, an appropriate range, tolerance, or limit will be used rath!r than a a single point value.
If the instrunantation value is the value used during normal plant operations, then the normal control setpoint will be used. Avoid the use of carats (g') in specifying these ranges. Instead, use phrases such as "greater than', 'less than'nd "bet~'HH-006 Rev. 3 Page 31 of.68
5.7 GENE WRIT TECHNI S (cont.)
5.7.10 Identificat'on of E i nt Controls and Dis la Norrenclature will be used which will assist personnel in quick location or identification of equipment, controls and displays. Use a consistent system of identification which corresponds with component identifications posted on equipnent and control panels.
Example:
- 8. Open Charging Valve:
1CS-240 5.7.11 Abb ev'a 's tter ls and Acron 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 aaaning is unquestionably clear to the intended refer.
Capitalization of abbreviations should be uniform. If the abbreviation is cceprised of lowercase letters, it should appear in lowercase in a title or heading. The period should be anitted in abbreviations except in cases where the omission would result in confusion.
Letter symbols rray be used to represent operations quantities, eleaants, relations and qualities.
An acronym is a type of symbol forrred by the initial letter or letters of each of the successive parts or major parts of a corrpound term. Acronyms may be used if they are contained in the Dictionary of Acronyms and Abbreviations for Shearon Harris.
Abbreviations, syabols and acronyms should not be overused. Their use should be'or the benefit of the reader. They can be beneficial by saving reading time, ensuring clarity when space is limited and camanicating mathematic ideas.
CNH-006 Rev. 3 Page 32 of 68
5.7 5.7.12 I@" WRITING 'HKfBC S (cont.)
detail in EQPs should be avoided in the interest of being
"'xcessive able to effectively execute the instructions in a timely manner.
This is especially iaportant for the Flow Paths which cannot present as much detail as can be efficiently presented in written procedures.
The level of detail in the Flow Paths shall not be so great that they are cluttered and unusable. The level of detail required in EOPs is the detail that a newly trained and licensed operator would desire during an eaargency condition. The Path Guides are written to provide an equivalent level of detail as other two coluan foraat procedures to suppleaant the Flow Paths.
To assist in determining the level of ECP detail, the following general rules apply:
- 1. Por control circuitry that executes an entire function upon actuation of the cxatrol switch, the action verb appropriate to the ccapanent suffices without further anplification of how to
'anipulate the control device< for ample, "Shut Peed Pung A Suction Ualve." Beccacmnded action verbs are as follows:
- a. Por power-driven rotating equipaent, use Start, Stop.
4
- b. Por valves> use Open, Shut> Throttle Open, Throttle Shut, Throttle.
- c. For power distribution breakers,. use Close, Open, Trip.
- 2. Standard practices of observing for abnormal results need not be prescribed within procedural steps. Por exaaple, observation of noise, vibration, erratic flow, or discharge pressure need not be specified by steps that start punps.
CHH-006 Rev. 3 Page 33 of 68
OS2 4
5.7 WRITI TECHNI S (cont. }
I 5.7.13
~ ~ Instruct'onal Ste t and Con tent Instruction steps will be short and exact. General rules to be used in rreeting these cbjectives are as follows:
- l. High level instruction steps should deal with only one idea.
- 2. A high level instruction step composed of complex evolutions should be broken down into a series of substeps, with each substep limited to one action.
- 3. Short< simple, sentences should be used. Do not use long<
compound, or coaplex sentences.
- 4. Cbjects of operator actions should be specifically 'stated. This includes identification of exactly what is to be done and to what.
- 5. Limits should be expressed quantitatively whenever possible (Refer to Subsection 5.9.5) .
- 6. Mandatory sequence of steps is assumed unless otherwise stated.
- 7. Identification of carpceents and parts should be ccaplete.
- 8. Instruction content should be written to camunicate to the user.
- 9. Expected results of non-routine tasks will be stated and capitalized.
/
- 10. After the reset or restoration of an alarm or trip, list the expected results in'.ately beneficial to the operator.
following the action if it would be ll. When system response dictates a tine fram within which the instruction est be accoaplished, define the tine frame.
Minimize using tine to initiate operator actions. Operator actions should be related to plant garanaters.
- 12. When additional confirmation of system response is considered necessary, prescribe the backup readings to be made.
.CNN-006 Rev. 3 Page 34 of 68
h OS2 5.7 KGTBG TECHNI S (cont.)
5.7.14 Instruction Column The left-hand colunn of the t~olurm format will contain the operator instruction steps and expected responses. The following rules are established for the instruction colurrn, in'ddition to the general rules above.
- 1. Expected results of non-routine tasks will be stated and capitalized.
- 2. If a step requires multiple substeps that have expected.
responses, then each substep will have its own expected response.
- 3. Left-hand coluaa tasks should be specified in sequence as if they could be performed in that manner. The user would normally move down the left~ colurm when the expected response to a particular step is obtained.
- 4. When the expected response is not cbtained, the user is expected to neve to the right-hand colurm for contingency instructions.
- 5. Routine single action steps or sdxsteps do not normally require-an expected response.
- 6. Use of logic terna in the Instructions coluna will be minimized by structuring. If logic terms aust be used, the guidelines of Section 5.7.16 will apply.
CNH-006 Rev. 3 Page 35 of 68
5.7 S (cont.)
I 5.7.15 Res Not Cbtained Colurm The right-hand column is used to present contingency actions which are to be taken in the event that a stated condition, event, or task in the left-hand colunn does not represent or achieve the expected result. Contingency actions will be specified for all steps or substeps for which the task requirarent might not be specified. The following rules apply to the right-hand column:
- 1. Contingency actions should identify directions to override automatic controls and to initiate manually automatically.
~t is normally'nitiated
- 2. Contingency actions should be nunbered consistently, vith the expected response/action for substeps only. A contingency for a single-task high-level step will not be separately nunbered but will appear on the sara line as its related step.
- 3. The user is expected to proceed to the next nunhered step or substep in the left-hand column after taking contingency action in the right-hand coluan.
- 4. All contingent transitions to other guidelines are to occur from the right-hand colurm.
- 5. If a contingency action cannot be ccapleted< the user is expected to proceed to the next step or substep in the left-hand coluna unless specif ically instructed otherwise. When writing the procedure, this rule of usage should be considered in wording subsequent left-hand coluan instructions.
- 6. If a contingency action must be coapleted prior to continuing, that instruction est appear explicitly in the right-hand colurm step or -substep.
- 7. Expected results of tasks will be stated and capitalized.
- 8. Do not repeat instruction colunn actions.
- 9. RM coluun actions will be structured to minimize use of logic terms, which may lead to operator confusion. If logic terms must be used, the guidelines of Section 5.7.16 will apply.
CHH-006 Rev. 3 Page 36 of 68
5.7 WRITBQ TECHNI S (cont.)
5.7.16
~ ~ Use of 'c Te The logic terms AND, OR, NOr, IF, IF Krr, m~Z and THEN may be necessary to describe a precise set of conditions or sequence of actions. All logic terms shall be capitalized, and also urxlerlined in order to clearly emphasize them from non-logical terms (e.g. the conjunctions "AND" E "OR" ).
Use 'logic terms as follows:
- 1. When action steps are contingent upon certain conditions or
+ or ~
combinations of conditions, the step will begin with the words followed by a description of the condition or conditions (the antecedent), a ccema, the word ~, followed by the action to be taken (the consequent). + is used for an unexpected but possible condition. Wggg is used for an expected condition.
Exaayles: + PRZ EOETs.
pressure less than 2335 psig, ~ shut PRZ Wggg ruptured SG pressure less than 1145 psig, Tgg5 shut SG EOPT.
- 2. Chly.logical AH) or Qg vill appear in the ante edent of an II'
~ o ggW or lgg4 ~ ~ ~ Qgà statBBRDt o
- 3. The use of ~ r OR within the in order to avoid confusion.
sana antecedent shall not be used
- 4. The use of Ag) a Qg within the sane antecedent will be limited to connecting two conditions. Three or narc connected conditions will be handled in a list format as in the following exarrples.
Example of gQ list:
Q? all the following conditions occur!
o PRZ level - LESS 'IKW 258 o PRZ pressure - LESS THAN 1500 PSIG o PRZ temperature - LESS %8M 596'F
~ secure PRZ heaters.
CHH-006 Rev. 3 Page 37 of 68
WRIT TEQBC S (cont.)
Example of OR list:
IF any of the following conditions occur:
o PRZ level - LESS THAN 25%
o PRZ pressure LESS THAN l500 PSIG o PRZ temperature - LESS THAN 596'F
- 4. Use of IF
~
Ã7P secure PRZ heaters.
should be minim~, and it will be limited to those cases in which the operator must resp'o the second of two possible conditions. + should be used to specify the condition. Q gg should be used to specify the negative of the condition and follows inaadiately after the consequent of the first stateaent.
Example: IF letdown in service,
~, Qgg use one
~
PRZ PORV.
use auxiliary spray.
- 5. ~ will not be used at the end of an action step to instruct the operator to perform the next step because together.
it runs actions CHN-006 Rev. 3 Page 38 of 68
~
~
OS2 5.7 WRITING TECHNI S (cont.)
5.7.17 Use of Con'unctive AND t OR Use of conjuntive "AND" E "OR" will be minimized by structuring of the steps.
The use of "AND" and "OR" within the consequent of an IF ... 'I%EN or WHEN ... 'ISEN statement will be minimized< and limited to connecting two items. Nore than two items will be listed as in the following examples.
Example of "AND" list:
IF PRZ level less than actions o 258< ~ perform the following
- a. Open 1CS-123
- b. Close 1CS-456
~ SG level less than following actions:
258, ggg perform one of the o
o o
Start' Start an Start the
~
feedwater puny KAFW puny pmy 5.7.18 Use of Under Unde~lining will be limited to enyhasis of logic terms, C~I'ION headings, and ggg headings in order to avoid overuse.
9 CNH-006 Rev. 3 Page 39 of 68
5.7 GENE OBIT TEQBG S (cont.)
5.7.19 C nent Identificat'on With respect to identification of components, the follow'ing rules are to be followed:
- l. Equipnent, controls and displays will be identified in operator language (conmon usage) terms. These terms should match engraved nanas an panels and equipaent.
- 2. When the engraved nants and nuabers on panel placards and alarm windows are specifically the item of concern in the proceduret the engraving should be quoted verbatim and emphasized by using all capitals.
- 3. The naaas of plant system titles are emphasized by initial capitalization. When the word "system" is deleted from the title because of brevity and is understood because of the context, the title is also e~ized by initial capitalization.
- 4. If the caaponent is seldan used or it is felt that the c emanent would be difficult to find, location information should be given in parentheses following the identification.
CNH-006 Rev. 3 Page 40 of 68
OS2 PRINZED OPERA%)R AIDS Hhen information is presented using graphs, charts, tables and figures, these aids est be self-explanatory, legible and the expected conditions of use and within the reading precision readable'nder of the operator. EOPs that refer the operator to a printed operator aid must have the aid attached in the back of ea."h procedure to which it applies, or else give the location of the aid (e.g. Reference Attachment 6 of OMH-004, "POST TRIP/SAFEGUARDS REVIEN," for a list of affected corrponents and required status) .
5.8.1 Un'ts of Measure Units of rreasure on figures, tables and attachments should be given for nunerical values that represent observed or calcu3ated results.
A virgule (slant line) should be used instead of 'per'; examples:
ft/sec, lbs/hr.
5.8.2 F'ab and A tac nt Sequential Arabic numbers should be assigned to figures, tables and attachments in separate series and placed at the top of its associated page. The sequence should correi pond with the order of their reference in the text. The symbol "0" and abbreviation "No."
are unnecessary and should not be used. %be number alone. suffices.
Examples: Table 1< Table 2> etc.
Figur'e 1, Figure 2, etc.
Attachment lg Attachment 2g etc.
Page identification for attachments, figures and tables skuld consist of the following information that identifies (1) procedure nunher, (2) attachment nuaher, (3) page number and (4) revision nunber. Page nuabering of attachments should neet the requireaents of Subsection 5.3.5. In addition, if an Attachaant consists of acre than one page, the page number of that Attachment should be at the top right hand side of each page in the Attachment.
CNN-006 Rev. 3 Page 41 of 68
OS2
" 5~9 MECHANICS OP Spelling should be consistent with modern usage. When a choice of spelling is offered by a dictionary, the first spelling should be used ~
Hyphens are used between elements of a ccapourd word when usage calls for it. The following rules should be followed for hyphenation.
- l. When doubt exists, the ccepound word should be restructured to avoid hyphenation.
- 2. In canpound nunarals from twenty-one to ninety-nine'e.g. one hundred thirty-four) .
- 3. In fractions (e.g. one-half, two-thirds).
- 4. In ccepounds with "self" (e.g. self-contained, self-lubricated) .
- 5. When misleading or awkward consonants would result by joining the words (e.g. bell-like) .
- 6. Vo avoid confusion with another word (e.g. re-cover to prevent confusion with recover, pre-position to avoid confusion with preposition).
- 7. When a letter is linked with a noun (e.g. X-ray, 0-ring> I-bolt, I~am) .
- 8. To separate chemical eleaants and their atanic weight (e.g.
Uranium-235, 0-235) .
Q%-006 Rev. 3 Page 42 of 68
5~9 MECHANICS OF 'cont.) I
- 5. 9. 3 Punctuation Punctuation should be used only as necessary to aid rea9ing and prevent misunderstanding. Word order should be selected to require a miniman 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:
- 1. Brackets Brackets shall be used to indicate values that should be used adverse containment conditions are present.
if Example: RCS Subcooling - GREATER THAN 25'F [45'F}
- 2. Colon Use a colon to indicate that a list of itans is to follow.
Ebmnple: Restore cooling flow as follows:
- 3. Carcna Use of many ccalnas is a sign the instruction is too ccaplex and needs to be rewritten. Therefore, evaluate the number of camas to ensure the instruction is not too canplex.
Use a comna after condition phrases for clarity and ease of reading.
Ehcaaple: Nggg level decreases to 60 inches, Tggg start poach.
- 4. Period Use a period at the end of carglete senteraes and for indicating the decimal place in numbers.
CNH-006 Rev. 3 Page 43 of 68
(cont. }
5.9.
~ ~ 4 v~ccabula Words used in procedures should convey precise understanding to the trained person. The following rules apply:
- l. Use sinple words. Simple words are usually short words of few syllables. Simple words are generally camron words.
- 2. Use ccaaan usage if it makes the procedure easier to understand.
- 3. Use words that are concrete rather than vague, specific rather than general, familiar rather than formal, precise rather than blanket.
- 4. Define key words that may be understood in vere than one sense.
- 5. Verbs with specific aaaning should be used. Examples are listed in Attachment.6.6.
- 6. Equipment status should be denoted as follows:
- a. Operable - Means that a system, subsystem, train, coaponent, or device is capable of performing its specified function(s) and all necessary attendant instrutl.ntation, controls, electrical power, cooling or seal mter>
lubrication or other auxiliary equipment required for the system, subsystem, train, caqxeent, or device to perform its function(s) are also capable of performing their related support function(s} .
- b. Operating - This word aaans that a system, subsystem, train, cadent, or device is in operation and is performing its specified function(s).
- c. Available - This words aaans that a system, subsystan, train, cceponent, or device is operable and can be used as desiredg however, it need not be operating.
Q%-006 Rev. 3 Page 44 of 68
- 5. 9 MECHANICS OF (cont. )
5.9.5 Nunerical Values The use of nunarical values should be consistent with the following rules:
- l. Arabic nererals should be used.
- 2. For nuabers less than unity, the decimal point should be preceded by a zero (e.g. 0.1).
- 3. The nuaber of significant digits should be equal to the nunher of significant 'digits available from the display and the reading precision of the operator.
- 4. Acceptance values will be specified in such a way that addition and subtraction by the user are avoided. This will be done by stating acceptance values as limits. Do not use I
Exaaples: 510'P maximan< 300 psig miniraun< between 580'P and 600'P
- 5. Engineering units should always be specified for ntmerical values of process variables. They should be the sana as those the control roan displays, for exanple: psig instead of psi.
- 1. Page margins are specified to be 1.5 inches on the side, 1.5 inches left~
on the right hand side, and 1 inch at the top and bottan.
- 2. Page identification information (refer to Subsection 5.3.5) vill, be in the bottom left corner.
- 3. The 8.5 inch edges shall constitute top and bottan of pages and text. Tables and figures shall be readable vith the page so arranged. Rotation of printed matter should be avoided for
. eaergency operating procedures.
rotation is necessary.
Refer to Subsection 5.10.4 if 0%-006 Rev. 3 Page 45 of 68
5.10.2 Head'nd Text Arr ement
- l. Section numbers shall be typed at the left-hand margin.
- 2. Two line spaces shall be allowed between headings and respective text.
- 3. Three line spaces shall be allowed between steps whenever possible.
- 4. Text will be typed using single line spacing.
- 5. Each action substep, caution, and note shall be wholly contained on a single page.
- 6. No part of the Ebs shall be handvritten with the exception of
.>>.3 ~f the preparer's initials, which are required for teaporary and advance changes.
Breaking of words (hyphenated and continued on the next line) shall be avoided to facilitate operator reading.
C If pages need to be rotated, the following rules vill be foLLowed:
L. The top of the page vith rotated print is the normaL left-hand edge a 2~ The page margins do not rotate.
- 3. Page identification and nunbering will not be rotated.
5.10.5 P 'ed rato Figures include graphs, drawings, diagrane and illustrations. The following rules are established:
- 1. The figure nerber and its title are placed three line spaces above the figure field (refer, to Subsection 5.8.2).
- 2. The figure field must not violate specified page margins.
- 3. The figure field should be of sufficient size to offer good readability.
CNH-006 Rev. 3 Page 46 of 68
.1
- 4. The essential message should be clear; single presentations are preferred.
S. Nmbered grid lines should be bolder than unnumbered grid lines.
- 6. Labeling of items within the figure should be accompanied by arrows pointing to the item.
- 7. The items within the figure should be oriented naturally insofar as possible. For example, height on a graph should be along the vertical axis.
- 8. In general> items within the figure should be labeled. Typed labels should be used.
- 9. All lines in figures should be reproducible.
5 10.6 es fo Tab es
- 1. Type style and size should be the saaa as that for the rest of the procedure.
- 2. The table nuaber and title should be located above the table field and three line spaces below preceding text.
- 3. A heading should be entered for each colunn and centered within the column; the first letter of words in the colunn headings should be capitalized.
- 4. Horizontal lines should be placed above and below the colum headings; vertical lines, while desirable, are not necessary or required.
- 5. Tabular headings should be aligned as follows:
- a. horizontally by related entries
- b. vertically by decimal point for nuaerical entries
- c. vertically by first letter for word entries; however, runner lines should be indented three spaces
- 6. Double spacing between horizontal entries suffices to segregate such entries; although horizontal lines may also be used if desire'd. If used, double horizontal lines should be used above and below the colurm headings.
CHN-006 Rev. 3 Page 47 of 68
5.10 1YPIhG FORRT (cont.)
- 7. There should not be a vacant cell in the table. If no entry is necessary, "QA" should be entered to indicate not applicable; 5.10.7 Cautions and Notes All notes and cautions should be distinguishable from the rest of the text by using the following format:
- 1. The heading Col'ION should be capitalized, centered and placed two lines spaces below the preceding text.
- 2. - The text of the caution should be block format with single line spacing. The caution text will extend from margin-to-margin and two line spaces below the heading.
- 3. The spacing. The note text is preceded by the word ~
text of the note should be block format with single line letters and underlined. Note margins are the sane as the page margin. The note text will begin two line spaces below the in capital preceding step.
- 4. Cautions shall be further highlighted by a line of asterisks one line space above the heading and one line space below the text.
- 5. Notes shall be further highlighted by a line one space above and below the text.
- 6. Examples are presented in Subsection 5.7.4 and 5.7.S.
S.ll U OP OPERATOR AID Operator aids will be used to assist the operator in carrying out the required EOP action.
5.11.1 C~:koffs In light of the fact that the operator must have a aathod of keeping track of the current step of the EQP while they are performing the designated action; a set of myla~ted Plow Paths will be mrailable in the Control Rxxn with a grease pencil or mter marker to checkoff the desi.gnated operation action.
5.11.2 Mater k Mater al Material needed to carry out actions in the EOPs, but which canot be included, should be appended to it.
CNH-006 Rev. 3 Page 48 of 68
5.12 5.12.1
~ ~ A e to the Emer enc rat Pr'ccedures Is Identified If the change is a result of generic changes to the Emergency Response Guidelines, then go to Subsection 5.12.2.
- 2. If the MCB has been modified and a change to the Emergency Operating Procedures is needed, go to Step 3. Otherwise go to Subsection 5.12.3, Step 8.
- 3. A plant specific change to the Emergency Operating Procedures is desired e
- a. Evaluate the proposed change against the generic guidelines (Emergency Response Guidelines Executive Volume and Background Docunants) to determine generic guidelines is altered. If if the intent of the the generic intent is not altered, go to Subsection 5.12.3.
- b. If the intent of the 'generic guidelines is altered, the proposed change nast be reevaluated to resolve the discrepancy between the generic guideline and the proposed change. The proposed change est be modified so that does not alter the intent of the mitigating strategies of it the generic guidelines.
- 4. Go to Subsection 5.12.3.
5.12.2 neric es to the Emer e Res ines
- 1. Evaluate the effect of the generic change on the SHNPP Emergency Operating Procedure. If the generic change has no effect on emergency operating procedures, then perform the following:
- a. Update the Emergency Response Guidelines.
- b. Update the EQP Transition Document.
- 2. If the generic change affects the $ 8% P Emergency Operating Procedures, then perform the following:
- a. Update the Emergency Response Guidelines.
- b. Go to Subsection 5.12.3.
CHN-006 Rev. 3 Page 49 of 68
OS2 5.12 MAINI'EN&,NCE OF EOP NFIWORK (cont.)
5.12.3
~ ~ Processin an Emer e ratin Procedure Chan e Prepare the change using the following for guidance:
AP-005, "Procedures Format and Preparation"
~06 / "Emergency Operating Procedures Writer '
Emergency Response Guidelines, High Pressure Guide" 2~ Determine if the proposed change affects the placenant or removal of EAL Flags in the Emergency Operating Procedure network.
for If the Emergency EAL flags are affected, Action Level Flags in SHNPP ate EOPs" the "Explanation docunant.
- 3. If the Critical Safety Function Status Trees will be changed, fill out a Plant Change Request, per AP-600 to have the updated. The procedure version should be irrpleaanted with the SPDS SPDS.
4, Canpare the proposed change to existing Emergency Operating Procedures for consistency in style and format.
- 5. Perform a human factors, evaluation of the proposed change to verify the change is acceptable.
- 6. Process the conge in accordance with ~06, 'Procedure Review and Approval".
- 7. Once approved, Verification and the change must be evaluated to see if any Validation is required. Refer to Section 5.13 and update the "Determination of Any Additional Verification and Validation" book as appropriate.
- 8. Update the applicable sections of the SH%'P ECP Transition Docunant.
- 9. Determine has if the change to the Emergency Operating Procedures affected any instrunantation or controls previously identified in the EOP Transition Document. If change adds, deletes or alters any instrunentation or cxetrols, then the SHNPP Task Analysis Doctxrantation est be updated.
CHN-006 Rev. 3 Page 50 of 68
OS2
- 5. 13 VERIFICATION AND IDATION PROGRAM FOR GRUDGES TO THE SHNPP ECPS
- 1. The Operations Engineer is responsible.
- 2. Verification and Validation (V6V) is required when a change to a SHNPP procedure alters the intent of the procedure.
- 3. The V&V program should denenstrate the following objectives are satisf ied:
a.. That the EOPs are technically correct (i.e. they accurately reflect the WOG Emergency Response Guidelines) .
- b. That EOPs are written correctly (i.e. they accurately reflect the SHNPP Emergency Operating Procedure Writer' Guide) .
- c. That EGPs are usable (i.e. they can be understtxd and followed without confusion, delays, and errors) .
- d. That there is a correspondence between the procedures and the control roan/plant bar&ere (i.e. control equipnent/indications that are referenced are available both inside and outside of the control roan, use the sane designation, use the sane units of measurenant, and operate as specified in the procedures).
- e. That the language and level of information presented in the EOPs are compatible with the mininaun number>
qualifications, training, and experience of the operating staff.
- f. That there is a high level of assurance that the procedures will work (i.e. the procedures correctly guide the operator in mitigating transients and accidents) .
- 4. The VLV program should make use of one or a ccahination of the following methods:
- a. Sinxxlator
- b. Tabletop c.. Control Roan Walk Through
- 5. The personnel involved in the VRV pxogram should be Licensed Operators, &iftTechnical Mvisors, and Operations Engineering Staff.
CNH-006 Rev.~ 3 Page 51 of 68
CQVER P~A 6.2 6.3 6.4 6.5 6.6 A RIZED VERB ISI'NM-006 Rev. 3 Page 52 of 68
OS2 Attachnant 6.1: COVER PAGE ChROLINh POWER & LIGEZ COMPhNY SHZhRON HhRRIS NUCLEhR POWER PLhÃZ PLhNT OPERhTING MhNUhL VOLUME 3 PhRT 4 PROCEDURE .TYPE: EMERGENCY OPERhTING PROCEDURE (EOP)
END PhTH PROCEDURE (EPP)
EOP"EPP 002 TITLE: LOSS OP as. hC POWER RECOVERY WmuXrr St REQUIRED REVISION 1 hP PROVED:
Signature Dace TITLE:
Page,l of 12 QK-006 Rev.~ 3 Page 53 of 68
Attnc?ment 6.2:
~
RtlSIQr
~>e mcsasr Oslo
~ I~lVEI
%7lC!~GAZA~
sa tas% ~ sa ANY
~ORCLQD LEAL aaaaa (NM-006 Rev. 3 Page 54 of 68
OS2 1 1/' 1 1/."
DECISION SYMBOL . 13/16" 4CTION evg~CL YES 1 1/2" 1/2" CAUTION SYMBOL 13/16'OTE ST<:-:: 1/2" P4T}{ ENTR Y P 4TH- TO-P4TH POINT 4RRON EXIT 4RRON P4TK- TO-EPP PATH-TO-FRP K X I T 4RRON EXIT ARROM G48QED CONNECTING LINKS NI YK DIRKCTION4L 4RROiiS
'HN-006 Bev. 3 Page 55 of 68
Attachment 6. 4: PAGE FORMAT PMH-1 GUIDE Page 6 of 31
- 5. b. AC energency busses b. Continue actions to restore lA-SA gQ 1B"SB- power to deenergized AC ENERGIZED energency bus while continuing with this procedure.
- 6. Check SI Actuaticni Check any cue of the Check whether SI is required following - LIT< by observing any cne of the followings ALB ll 2 o QRP pressure 3+0 PSIG
- GREGAL KRN ALB 11 1 o pressure - LESS ALB ll 3 PBZ
%RN 1850 PSIG ALB 12 - 1& o Stean line pressure - LESS
'ISBN 601 PSIG Q, SX is required, ggg actuate SX AM) GO %0 Step 7o Implant Puncticn Restoration Procedures as required hN) C) '10
~04'EEKS %RIP BESKSSE ~
Step l.
EOP - User's Guide Rev. 0 Poge 29 of 90 (NM-006 Rev. 3 Page 56 of 68
OS2 Attachment 6. 5: CSFST EXAMPI.E CONTAINMENT CSF-5
~AISIIIAONT PASS%PS I
THAN IS PS I 0 OO fO TNA J, I THIN I ~ POI ~ NAKNTA IXI IO TIP J, I OCHTAII4ONT LASS THAN AS PSIO CCNI A IIOONT THAN I ~ PS I ~
~ ~TON
~ NOCNT A IKI IO TIO J,S CTOIT POST LOCA CTSITAIIOONf OJOI JP%'A IOAOIATI ON IOSIITTSIO WKAIOTI THNI AAJIOI SOTTO INT ITSIJTO
'CN IOO TINES ~ O IO TIP J,S ISOIT POST LOCA APOA PAOIATIOI IASIITISIO I4$ $ THAN AANOI SOTTO INf (MM-006 Rev. 3 Page 57 of 68
Attachment 6.6:
l AUTHORIZED VERB I Page 1 of ll Neanm 1 ication Actuate 'Ib put a component or system into action Example: Actuate SI.
'Ib include or unite Example: Add boron 'to the RCS.
Adjust To regulate or bring to a desired state Exanple: Adjust charging line flow to 100 gpn.
To place a system in proper or desired configuration for an intended purpose Example: Align the charging system for normal charging.
To permit a stated condition to be achieved prior\ to proceeding Example: Allow discharge pressure to stabilize.
To inhibit an autQDatic action Example: Block SI actuation.
Borate To cause boron to be injected into a system Exanple: Borate the RCS.
Calculate To determine or carpute a value Example: Calculate total mass of boron injected into the reactor.
'Ib examine a plant paranater or system in order to obtain a def inite status Examgless Check PRZ pressure '- LESS THAN 2000 PSIG Check AEW Valve Alignaant Close To place a breaker or electrical switch in a position to allow current flow Example: Close the EDG breaker.
CN&006 Rev.~ 3 Page 58 of 68
OS2 ll
~ I Attachment 6.6: AVZHORI ED VERB I (cont.) Page 2 of Neanin 1 ication Coll~ To cause the failure of scaathing Exanple: Collapse the steam void in the rea=tor.
Commence To begin or all start'xample:
Caraance depressur izing SGs.
Complete To accomplish specific procedural requireaants, to finish Exanple: Canplete valve checkoff list "A".
To ask the advice or opiniion of Ex~~e: Consult with plant operations staff.
To maintain without interruption Example: Continue with RCS coaldown to cold shutdown.
Control To change or maintain plant paraneters to or at a desired condition Exanple: Control pressurizer level between 25% and 75%.
To remove heat from Exanqle: Cool down the RCS.
Coordinate To work with another in order to accanplish a task Example: Coordinate with Radwaste operators.
Cycle To cause to go through an operation Example: Cycle the PRE POP7.
CMH-006 Rev. 3 Page 59 of 68
Attachment 6.6: AUTHORIZED UEHB Ipr (cont.) Page 3 of ll Neanin 1 icat 'n J
Decrease To reduce in value Example: Decrease RCS pressure.
Deenergize To secure power to an electrical device or carponent Example: Deenergize PRZ heaters.
Defeat To override a protective interlock Example: Defeat the undervoltage trip on the breaker.
Depressurize To lower the pressure of Exa~e: Depressurize the RCS.
Determine To find out or ccats to a decision by investigation, reasoning, or calculation Example: Determine whether RCPs can be started.
Direct To instruct a person to do scaathing Example: Direct the M to shut the valve locally.
Dispatch To send a person to do sanething Example: Dispatch an operator to shut the valve locally.
To perform a task or action Example: Do Steps 15a, b, and c.
To discharge (usually used with stean)
Exanple: Dung stean from intact SGs. ~
CD+406 Rev. 3 Page 60 of 68
Attachment 6.6: ~RI'RED VERB ESI'cont.) Page 4 of ll I
Uerb Neanin licat'on Energize To line up power to an electrical device or canponent Example: Energize the AC energency busses.
Ensure To make certain Example: Ensure the system is lined up prior to operation.
To cause paranaters to have the sana value Example: Equalize pressure.
Establish To make arrangements for a stated condition Example: Establish ccaxmnication with control roan.
Evaluate To estimate of the status of scaathing Exa~e: Evaluate plant conditions.
To go above a given value (usually used in the negative sense)
Exaagle: Do not exceed 500'P.
Exit To leave Example: Exit this procedure.
To put into, to increase level Exaaple: Pill the SGs.
To aave to another place Bcaayle: Q) TO Step 16.
Seat To add heat to Exaagle: Seat up the BCS.
CNN-006 Rev. 3 Page 61 of 68
Attachment 6.6: AUTHORIZED VERB I (cont.) Page 5 of ll Mean in 1ication Identify To recognize a specific sea@thing Example: Identify any faulted SG.
Implement To carry out a set of actions or a procedure Example: Implement FRPs if necessary.
Increase To raise in value Example: Increase RCS temperature.
Initiate To begin a process Example: Initiate boron injection.
Insert To place inside of Exarple: Insert all control rods.
Isolate To shut one or more valves in a systan for the purpose of separating or setting apart a conplete system or a portion of the system from the rest Ehmaple: Isolate instrunent air header.
To place one or aare electrical devices on a power source Em~e: Load the EDGs.
To place in a condition where swathing cannot be operated easily or by accident Example: Shut and lock 1CS-123.
CNN-006 Rev. 3 Page 62 of 68
0 Attachment 6.6:
I AtKEORIZED VEM IST (cont.) page 6 of ll Verb Meanin 1 ication Maintain To keep in an existing state or set of conditions Example: Maintain SG level between 25% and 75%.
To operate in a manner that achieves the largest result Example: Maximize dumping steam.
Minimize To operate in a manner that achieves the smallest result Exangle: Minimize loss of coolant.
Monitor To keep track of Exarples Monitor PBT conditions.
Notify To inform Exanple: Notify the Shift Foreman.
To see through direct attention Bcaayle: Cbserve QI,~I'rior to Step L9.
To get by direct action Exanple: Cbtain SG samples.
To change the physical position of a valve such that it aLLows flow, or to change the physical condition of an electrical device such that it, prevents passage of electrical current Exanple: ~ i'-123.
To manipulate plant devices in order to control plant ca~ents Cerate or parameters Example: Operate the floe control valve to maintain tank level between 25% and 75%.
CNH-006 Rev. 3 Page 63 of 68
OS2 I
Attachment 6.6: AUZHORIZED VERB I (cont.) Page 7 of 11 Mean' lication Perform To carry out actions or a procedure Example: Perform the following:
Place M put in a particular position or condition Example: Place steam dump in pressure control mode.
Plot To put data points on a graph Example: Plot cooldown rate.
Pressurize To cause a system or cceganent to increase in pressure Exanple: Pressurize the system to RCS pressure.
Back out To place a breaker in an ino~rative condition Example: Rack out the pm@ breaker.
To increase a paraneter value Example: Raise flow to 100 ggn.
To line up a system in a certain configuration again Example: Realign the charging system for normal operation.
Record To docunent specified condition or charmteristic Exanple: Record discharge pressure.
To cause a paranl.ter to decrease in value Bcample: Reduce stean generator pressure using POErs.
Reestablish . To make arrangments for a stated condition again Exar~e: Reestablish nortnal charging flow.
Refer To look at for information Example: Refer to OP-100< 'RERCIOR QXLAMZ SYSZZM."
CSN-006 Rev.~ 3 Page 64 of 68
Attachnent 6.6: RIZED VERB I (cont.) Page 8 of 11 Reference To look at for information Example: Reference OP-100, "REACXOR COUNT SYSTPf."
Refill To fillagain Example: Refill SGs as necessary.
Repeat To perform an action or series of actions again Example: Repeat actions as necessary to start the EDGs.
Repressurize To pressurize again Exanqle: Repressurize the accuaQators. I To place back into a normal condition, to reaave a locked in signal Exaayle: Beset SI.
Restart To start again Exanple: Restart the pung.
Restore To return a system, carpanent, or paranater to normal EMmple Restore normal charging flow.
Return To go back to a step in a procedure, or to restore a system, cadent< or parameter to normal Exangles: RK,"IURN TO Step 16.
Return the charging lineup to normal.
To operate a system or ccapceent Exm~e: Run the pump as necessary to maintain level.
To cause a rapid decrease in the power output of the main turbine Example: Run back the turbine.
CNH-006 Bev. 3 Page 65 of 68
Attachment 6.6: AVZHORIZED VERB ESr (cont.) Page 9 0 f ]1 Verb Meanin 1 ication Sample To obtain a speciE Example: San@le SGs.
Secure To stop a device or process Example: Secure dumping steam.
To adjust a plant paraneter or device to a specified value or condition Example: Set turbine generator speed to 18QO rpn.
Shut To change the physical position of a valve such that it prevents flow Example: Shut 1FW-123.
Shut down To secure a device or process Exanple: Shut down the reactor.
Stablize To cause a paraneter or conditions to be steely and controlled Example: Stablize RCS pressure.
To energize an electro-mechanical device Exarple: Start one feedwater puap.
Stop To deenergize an electro-mechanical device Example: Stop the RCP.
CHH-006 Rev. 3 Page 66 of 68
OS2 Attachment 6.6: AUTHORIZED VERB I (cont.) Page 10 of 11 I
Verb Heanin 1 ication Terminate To stop a piocess or parameter Example: Terminate flow.
Throttle To operate a valve in an internadiate position to obtain a desired flow rate or condition Exanple: Throttle open 1CS-240 to maintain 100 gpn flow.
Transfer To shift a device to another input, output, or mode of operation Exanple: Transfer the nuclear recorder to the source range scale.
Trip To activate a semi-autanatic device that stops current flow or shuts down a caaponent Exanples: Trip the EDG breaker.
Trip the reactor.
Unblock To reneve the inhibit on an autanatic action Bangle: Unblock SI.
To place in a condition where scaething can be operated Example: Unlock and open 1CS-123 Use To eaploy Examples: Use OP-100t 'REACZOR QXLANP SYSZKN."
Use auxiliary spray.
Q%-006 Rev. 3 Page 67 of 68
Attachment 6.6: (cont.) Page 11 of ll V~e To permit a gas or liquid confined under pressure to escape Example: Vent the pressuri~r with the PRZ P0%'s.
Verify To observe a component or param ter in a given condition< and placing it in that given condition manual or local action as required if not already'there by Example: Verify ICS-123 - OPEN Nait To delay an action until a condition is satisfied EMnple: Nait for the system to be lined up prior to continuing this procedure.
Withdraw To reaave fran inside of Exar~e: RitMrav control rods.
To set a device to the zero value Exa~e: Zero the aeter.
CÃH-006 Bev. 3 Page 68 of 68
Osi ATTACHMENT 3 VERiFICATION AND VALIDATION PROGRAM FOR SHNPP
Table of Contents Section ~Pa e 1.0 PURPOSE
2.0 REFERENCES
3 3.0 RESPONSIBILITIES 4.0 VERIFICATION AND VALIDATION PROCEDURE 4.1 Identifying Changes To EOP Network 4.2 Verification & Validation Methodology 4.2.1 Verification Phase 4,,
4.2.2 Validation Phase 5.0 ATTACHMENTS 5.1 Initial V&V of EOP Network 5.2 Verification Checklist 5.3 Table Top Validation Checklist 15 5.4 Simulator Validation Checklist 23 MEM/PROC"PKG Page 1 of 30
OSL 1.0 PURPOSE This document outlj.nes the process for Verification and Validation (V&V) of advance changes and revisions to the SHNPP EOPs.
Verification and Val.idation are two separate processes providing complimentary information on the EOPs; thus, these two independent phases provide a comprehensive review of the EOPs for continued accuracy and usefulness throughout their lifetime.
Because this evat.uation is based on a set of impLemented EOPs which were evaluated prior to implementation, the process described here differs from a pre-implementation V&V program for 'EOPs. The intent of this program is to ensure that modifications to the EOPs maintain or improv'e the level of accuracy and usability established in the initial V&V.
The Verification and Validation process incorporates consideration for Human Factors concerns in each part of the process. This is accompLished primarily through the inclusion of Human Factors related items in the relevant criteria checklists and through consistent use of the EOP Writer's Guide.
The Verification phase provides feedback on the foLlowing issues:
Are -the changes to the EOPs technically accurate, e.g.
do they accurately reflect the technical guidelines EOP source documents?
and'ther Does the hardware called for in the EOP changes correspond to the hardware available for the operator's use?
Are the EOP changes written correctly, e.g. do the changes accurately reflect the EOP Writer's Guide?
The Validation phase provides feedback on these additional issues'.
Are the revised EOPs usable, e.g. can they be understood and followed without confusion or errors?
~ Are the revised EOPs compatible with the minimum number, qualifications, training and experience of the operating staff?
~ Is there a high Level. of assurance that the procedures will work with the plant, e.g. that the procedures correctly guide the operator in mitigating actual plant transients and accidents?
HEM/PROC-PKG Page 2 of 30
OS1
2.0 REFERENCES
NUREG-0737, Novembqr 1980, "Clarification of the T'A I Action Plan Requirements."
NUREG-0737, Supplement 1, December 17, 1983, "Requirements for Emergency Response Capability."
NUREG-0899, August 1982, "Guidelines for the Preparation of Emergency Operating Procedures."
INPO 82-017, July 1982, "Emergency Operating Procedures Writing Guidelines."
INPO 83-004, March 1983, "Emergency Operating Procedures Veri f ication Guidelines."
INPO 83-006, July 1983, "Emergency Operating Procedures Validation Guidelines."
INPO 83-007, February 1.983, "Emergency Operating Procedures Generation Package Guidelines."
Westinghouse Owners Group (WOG} Emergency Response Guidelines (ERGs},.High Pressure Version.
AP-005, Procedures Format and Preparation.
AP-,006, Procedure Review and Approval.
AP-007, Temporary and Advance Changes to Plant Procedures.
AP-600, Plant Change Request.
OMM-QQ6, Emergency Operating Procedures - Writer's Guide.
3.0 RESPONSIBILITIES The Manager - Operations has overall responsibility for the Verification and Validation process since he is the individual responsible for the entire EOP Network.
Both phases of the V&V process require operations-experienced personnel who have a good understanding of plant hardware, the EOP background documentation, and the EOP Writer' Guide. If possible, the reviewers should also include a person with some background in Human Factors. The specific goal of the Verification phase of the evaluation is to ensure accuracy of the EOPs from both a technical and written standpoint. The Validation phase ensures the usability of the EOPs and draws heavily on resources from the Operations Unit and the Training Unit. Implementation of the Verification and Validation program is assigned to the Operations Support Supervisor.
MEM/PROC-PKG Page 3 of 30
OSL 4,0 VERIFICATION AND VALIDATION PROCEDURE 4.1 Identif in Chan es to EOP Network There are three major factors that could potentiaLLy result in EOP changes'.
1.'lant equipment modifications
- 3. Other forces causing desired EOP changes (i.e., Operator input, corrections, audits, etc.)
\
Changes or modifications to plant equipment can to the EOPs. ALterations to the main control board require'hanges (sometimes as a result of plant equipment modifications) can also necessitate changes to the EOPs.
Since the WOG ERGs form the basis for the plant-specific EOPs, any revisions to the WOG ERGs will probably result in changes to the EOPs.
Other factors can cause changes to be made to components of the EOP Network. For exampLe, operator input can initiate changes to make the EOPs read or work better. Audits performed by various groups can result in directing changes to the EOPs.
4.2 Verification & Validation Hethodolo 4.2.1 Verification Phase Changes to the EOP Network are processed in accordance with AP-006, Procedure, Review and Approval, and AP-007, Temporary and Advance Changes to PLant Procedures. The verif'ication phase for each EOP revision or advance change will be completed as part of the procedure review and approval process.
AP-006 requires each procedure to receive two Technical Reviews as part of the approval process. A separate EOP Verification Checklist (Attachment 5.2) will be completed'y each of the Technical Reviewers as part of the Technical Review. The completed Verification Checklist is retained as an attachment to the Technical Review Comment Sheet. Any discrepancies identified will be resolved in accordance with AP-006. This process provides assurance that every change to the EOP network will receive proper verification. In addition, the verification documentation will become an integral part of the approved procedure package.
MEM/PROC-PKG Page 4 of 30
Osl 4.2.2 Validation Phase The EOP validation, phase consists of two components; and ongoing validation of the EOP's and pre impl.ementation validation for'ajor revisions to the EOP Network.
On oin Validation The ongoing, validation is coordinated wit,h the Training Unit with, a goal of providing a documented validation of each EOP every two years. As part of the Operator Training and Retraining Program, each EOP will be discussed in the classroom by a shift of Licensed Operators or License Training Class (RO and/or SRO). The evaluator(s) will complete the Table Top Validation Checklist (Attachment 5.3) and forward it to the Operations Support Supervisor.
The Operations Support Supervisor (or his designee) will complete the resolution section of the Validation Checklist resolving any identified discrepancies. If the resolution results in an advance change or revision to the procedure, the Validation Checklist will be added to the procedure approval package. If a procedure change is not required, the Operations Support Supervisor (or his designee) will retain the completed Validation Checklist until the two-year review due on the affected procedure or a change to the 'ecomes procedure is executed. When either of these events occurs, the completed Validation Checklist will be forwarded to documentation with the approved revision or procedure review form as applicable.
In addition to the "tabletop" type of review, each EOP will be evaluated on the SHNPP simulator at least once every two years. This validation will be accompLished using either a shift of Licensed Operators or a shift of License Candidates (RO and/or SRO). This validation will be accomplished as part of the Simulator Training Program.
When an EOP is exercised for the purpose of validation, the following process will take place. The Simulator Training Staff will select a scenerio that will require entry into the EOP to be validated. When the scenerio is run for validation purposes, it will be videotaped, if possible. In addition, the Simulator Validation Checklist will be completed by the evaluator(s).
Immediately following the validation exercise, the operators will critique the procedure with the evaluator(s) using the Simulator Validation Checklist. The evaluator(s) will forward the completed Simulator Validation Checklist and the videotape (if applicable) to the Operations Support Supervisor.
MEM/PROC"PKG Page 5 of 30
OS1 On oin Validation (continued)
The Operations Support Supervisor (or his designee) will .
review all'f the documentation and resolve any identified procedure discrepancies. If a videotape of the scenerio is avail. able, it may be reviewed along with the completed Simulator Validation Checklist. Additions or other pertinent comments wiLL be added to the Checklist Comment Sheet during the videotape review.
The completed SimuLator Validation Checkli,st and videotape will be transmitted to the Document Control system in the same way as the Validation Checklist described above.
Pre-Im lementation Validation Prior to implementation, an extensive validation program was conducted on the EOP Network (Described in Attachment 5.1),
The EOPs were also fully exercised during Cold License Simulator Training which resulted in many enhancements. In addition to the above, CP&L has agreed to conduct additional simulator validation of the EOP Network during 1987 (currently scheduled for the JuLy August time frame).
The above validation program coupled with the "ongoing" validation program provides assurance that the EOP Network has and wilL maintain the necessary accuracy and usefulness needed to mitigate an accident. Minor changes to the network will be validated thru the ongoing validation program.
Major revisions wiLL receive pre-implementation validation.
A major revision to the EOP Network is defined as changes that would add or delete procedures or change the mitigating strategies of a maj or portion of the EOP Network.
This type of revision would most likely be recommended by the Westinghouse Owners Group with NRC concurrence. If this event occurred, the extent of the validation program would be recommended by the Owner's Group, when the revision is issued. SHNPP would justify any deviation from the Owner's Group recommended validation program.
If CP&L determines that the addition or deletion of a procedure in the EOP Network is necessary, validation of the procedure change will be done. This validation would, as a minimum, consist of tabletop type of discussions using licensed operators, followed by simulator validation completely exercising the new procedure (or area affected by the deletion of a procedure).
MEM/PROC-PKG Page 6 of 30
Osl Pre-Im lementation Validation (continued)
The validation woujd be accomplished after the verification program was completed. The change (addition or deletion) would not be implemented until the validation program was complete. The documentation for this validation would be the same as is used for the ongoing- validation. The completed checklists would be transmitted to the Document Control system as part of the approved procedure package.
5.0 ATTACHMENTS S.l Initial V&V of EOP Network 5.2 Verification Checklist 5.3 Tableto Validation Checklist 5.4 Simulator Validation Checklist HEMIPROC-PKG Page 7 of 30
, ~
Osl Attachment 5.1: Initial V&V of EOP Network Because the SHNPP reactor plant was under construction, the initial V&V of the SHNPP EOPs was performed using all three methods:
- 1. Simulator Testing
- 2. Tabletop Reviews
- 3. Control Room Mal.k-Throughs The simulator testing of the EOP Network was performed using the original Harris simulator (83,84) and EAL Validation was performed at the Seabrook simulator (3/85).
MEM/PROC-PKG Page 8 of 30
OS ATTACHHENT S.2 VERIFICATION CHECKLIST This list summarizes the results of the Verification Process.
Using the Verification description as a guide, verify the proposed EOPs accuracy. Initial each item as it is completed. Circle the item number for any item that does not meet the requirements of the Verification description, Explain each deviation in the comment section and attach the completed checklist to the Technical Revie~ form.
Part A Technical Accuracy Item 1. Entry conditions/symptoms information Item 2. Instruction step, Caution, or Note information Item 3. Derived quantitative information Part B - Hardware Accuracy Item 1. Equipment availability Item 2. EOP/Control Room compatibility Part C - Written Accuracy Item 1. New page content, format, and readability Item 2. Instruction step content and format Item 3. Caution and Note content and format Item 4. Transition step content and format Comments.'EH/PROC-PKG Page 9 of 30
OS1 ATTACHMENT 5.2 VERIFICATION DESCRIPTION Page 1 of 5 PART A
,TECHNICAL ACCURACY Entry conditions/symptoms information Does the EOP revision/change result in the deletion of an ERG-based enter condition?
- 1) Evaluate the affected EOP to determine if the
'eletion of an ERG-based entry condition affects the basis for the EOP, e.g. does the deletion of the entry condition Limit operator entry into the procedure when use of the procedure is required.
Does the EOP revision/change result in the addition of an entry condition not based on the ERGs?
- 1) Evaluate the affected EOP to determine if the added entry condition is appropriate in the context of the procedure basis.
- 2) Evaluate the affected EOP to determine if the addition of an entry condition results in an excessive number of entry conditions for the procedure.
- 2. Instructional step, Caution, or Note information
- a. Does the EOP revision/change result in the addition to, deletion from, or reordering of information from the ERGs?
- 1) Evaluate the affected EOP to'determine if the change affects the basis of the EOP as defined by the ERGs.
- 2) Ensure that adequate justification has been provided for the change.
- 3) Ensure that the justification has been documented in the Step Deviation Document.
- 1) Evaluate the affected EOP to determine if the modification affects the basis of the EOP as defined by the ERGs.
- 2) Ensure that adequate justification has been provided for the change.
MEM/PROC"PKG Page 10 of 30
OS1 ATTACHMENT 5.2 VERIFICATION DESCRIPTION Page 2 of 5 PART A TECHNICAL ACCURACY (continued)
- 3) Ensure that the justification has been documented in the Step Deviation Document
- c. Does the EOP revision/change introduce additional information regarding plant-specific systems, instrumentation, controls, indications, or limits?
- 1) Evaluate the affected EOP to determine i.f the revision/change affects the basis of the EOP as defined by the ERGs.
- 2) Evaluate the affected EOP to determine if the revision/change is correct with respect to the source documents on which the revision/change is based.
- d. Does the revision/change affect a licensing commitment?
- 1) Ensure that a justification has been provided.
- 2) Ensure that the justification has been documented.
- 3. Derived quantitative information a ~ Evaluate the affected EOP to determine if the derived values and tolerance bands are correct with respect to the source documents.
- b. Evaluate the affected EOP to determine if plant-specific values used in the EOPs are computed accurately.
C ~ Does the revision/change include equations for required cal,culations?
- 1) Evaluate the affected EOP to determine if the equation could be replaced with a table or graph which could serve the same purpose.
- 2) Evaluate the affected EOP to determine if the equation includes all necessary information.
MEM/PROC-PKG Page 11 of 30
OS1 ATTACHMENT 5.2 VERIFICATION DESCRIPTION Page 3 of 5 PART B HARDWARE
- 1. Equipment availability
- a. Evaluate the affected EOP to determine if the additionaL equipment referenced in the EOP revision/change i.s available to the operator in the Control Room or plant.
- 2. EOP/Control Room compatibility a ~ Evaluate the affected EOP to determine if the designation used corresponds to the. designation used in the plant.
- b. Evaluate the affected EOP to determine if the units of measurement used are the same as those on the plant, instrumentation.
C ~ Evaluate the affected EOP to determine if the values used fall within the range of the pLant equipment.
d 0 Evaluate the affected EOP to determine if the values can be read to the necessary precision on the plant instrumentation.
- e. Evaluate the affected EOP to determine if the plant equipment referenced operates as indicated in the procedure.
MEM/PROC"PKG Page 12 of 30
0 OS1 ATTACHMENT 5.2 VERIFICATION DESCRIPTION Page 4 of 5 PART C WRITTEN ACCVRACY (continued)
- 1. "New page content, format, and readability a ~ Evaluate the affected EOP to determine if the format of the revision/change is consistent with the organization and page layout of the EOP Network as outlined in the Writer's Guide.
- b. Evaluate the affected EOP to determine if the necessary identification I
information is present as outlined in the Writer s Guide, e.g. a complete and accurate cover page for each procedure; procedure designation, revision number, and page of on each page except for the cover page and list of effective pages.
C ~ Evaluate the affected EOP to determine if, on a subjective basis, all pages of the revision/change are readable for text, tables, graphs, figures, and charts.
- 2. Instruction step content and format a ~ Evaluate the affected EOP to determine if instruction steps are numbered correctly.
- b. Evaluate the affected EOP to determine if the style of information presentation in the modified instruction step is consistent with the rest of the EOP Network, as outlined in the Writer's Guide.
C ~ Evaluate the affected EOP to determine if step construction is consistent with the EOP Network format, as outlined in the Writer's Guide.
- d. Evaluate the affected EOP to determine if the sequencing of instruction steps is clear.
- e. Evaluate the affected EOP to determine if, when the sequence of actions is optional, it is clear to the operator.
Evaluate the affected EOP to determine if the transitions for the unchanged parts of the EOP Network have been evaluated for impact.
MEM/PROC-PKG Page 13 of 30
OS1 ATTAGHi!ENT 5.2 VERIFICATION DESCRIPTION Page 5 of 5 PART C MRITTEN ACCURACY (continued)
- 3. Caution -and Note content and format
- a. Evaluate the affected EOP to determine if the Note and Caution formats are consistent with the EOP Network format, as outlined in the Mriter's Guide.
- b. Evaluate the affected EOP to determine if Notes and Cautions avoid inclusion of. operator actions.
- 4. Transition step content and format
- a. Evaluate the affected EOP to determine if references and branches are used correctly and consistently with the EOP Network format.
- b. Evaluate the affected EOP to determine if referenced/branched procedures are in place prior to implementation of the revision/change.
c~ Evaluate the affected EOP to determine if references and branches redirect the operator without jumping over important information, e.g. Notes or Cautions.
Evaluate the affected EOP to determine if conditions are consistent between the exit point and entry point of transitions.
HEM/PROC-PKG Page 14 of 30
OSl ATTACHMENT 5.3 TABLE TOP VALIDATION CHECKLIST PROCEDURE NUMBER REV.
TITLE NAME/TITLE NAME/TITLE PARTICIPANTS:
NAME/TITLE SIGNATURE EVALUATORS Attach a copy of the marked up procedure pages, if changes are identified, to the completed checklist.
Route the completed package to the Operations Support Supervisor Pages Attached MEM/PROC-PKG Page 1$ of 30
OSL ATTACHMENT 5.3 TABLE TOP VALIDATION CHECKLIST This form guides the evaluation of the performance deviations identified by the Tabletop Validation method. As each main category is considered, answer the question YES or NO. If the answer is YES, complete the sub-category questions on the 'attached pages. The completed sub-category questions for each item answered YES must be attached to the checklist. Identify the affected part(s) of the procedure for each YES answer, in the comment section.
ITEM CATEGORY YES/NO An operator considered an action not specified by the procedure.
If YES, compLete items la through le of this checklist.
2 ~ An operator should have pexformed appropriate actions in the wrong sequence.
IfI YES, complete items 2a through 2c of this checklist.
3 4 An operator made an incorrect transition.
If YES, complete items 3a through 3e of this checklist.
4, An operator did not operate equipment as directed by the procedure.
If YES, complete items 4a through 4c of this checklist.
- 5. An operator selected the wrong procedure.
If YES, complete items 5a through 5c of this checklist.
6 ~ An operator recorded an inappropriate value.
If YES, complete items 6a thxough 6d of this checklist.
- 7. An operator failed to perform an action specified by the procedure.
If YES, complete items 7a through 7e of this checklist.
MEM/PROC"PKG Page 16 of 30
Osi ATTACHMENT 5,3 TABLE TOP VALIDATION CHECKLIST (continued)
ITEM CATEGORY YES/NO
- 8. An operator did not make a transition when required.
If YES, complete items 8a through Bd of this checklist.
An operator failed to record a required. value.
If YES, complete items 9a through 9d of this checklist.
- 10. An operator was not abl.e to complete required actions in time If YES, complete items 10a through 10j of this checklist.
An operator could not locate required equipment.
If YES, complete items lla of this checklist.
- 12. An operator recorded a value after time limit.
If YES, complete items 12a through 12d of this checklist.
MEM/PROC-PKG Page 17 of 30
Os 1 ATTACHMENT 5.3 TABLE TOP VALIDATION CHECKLIST (continued)
/
ITEM CATEGORY YESiNO la. Information necessary to management of the emergency condition is missing.
lb. The wording is ambiguous or obscure.
lc. There are alternate success paths that are not included.
ld. There is information or equipment required to accomplish a task not specified sufficiently.
le. There is action information in a Caution or Note.
2a ~ The makeup of the operating shift prevents them from following the designated action step sequence.
2b. The design of the Control Room promotes deviations from the specified sequence 2c ~ There is insufficient information to perform the specified actions in the required sequence.
3a ~ There is insufficient information for a decision at the transition.
3b. The alternatives are not adequately described at the decision point.
3c ~ The wording of the transition is ambiguous or obscure.
3d. If transition made to wrong procedure, there is insufficient information for the operator to find the correct procedure.
3e ~ If transition made to wrong step, the destination is not specified .sufficiently and clearly enough to guide the operators to the correct step.
MEM/PROC-PKG Page 18 of 30
Osl ATTACHMENT 5 3 TABLE TOP VALIDATION CHECKLIST (continued)
ITEM CATEGORY YES/NO 4a. The labeling, abbreviations, symbols and l.ocation information in the procedure and on the equipment is insufficient for the operator to perform the required action.
4b. There is insufficient information to perform the specified actions.
4c. The Cautions and Notes are not clearly and correctly identified and understandable.
sa. The observable plant symptoms l.ead the operator to an inappropriate procedure.
5b. There is insufficient information for the operator to select the correct procedure.
5c. The Cautions and Notes are not clearly and correctly identified and understandable.
6a. Figures and tables are inadequately identified, or are not understandable, or readable.
6b. Values on figures and charts are difficult to determine.
6c. The operator cannot obtain the information spec'ified in the procedure from the plant instrumentation that is provided.
6d. The instrument readings and tolerances for plant instruments are inaccurate.
'a
~ There is insufficient information to perform the specified actions.
7't 7b. The makeup of the operating shift prevents them from performing the specified steps.
inadequately coordinates actions when the actions are assigned to specific shift personnel.
7d ~ The plant responses do not agree with the EOP basis.
7e ~ The Cautions and Notes are not clearly and correctly identified and understandable.
MEM/PROC-PKG Page 19 of 30'
051 ATTACHMENT 5.3 TABLE TOP VALiDATION CHECKLIST (continued)
ITEM CATEGORY YES/NO 8a. There is insufficient information for a decision at the transition.
Bb. The al.ternatives are inadequately described at the decision point.
8c. The wording of the transition is ambiguous or obscure.
8d. The Cautions and Notes are not clearly and correctly identified and understandable.
9a ~ Figures and tables are inadequately .identified, or are not understandabl.e, or readable.
9b. Values on figures and charts are difficult to determine.
9c ~ The operator cannot obtain the information specified from the plant instrumentation that is provided.
The Cautions and Notes are not clearly and correctly identified and understandable.
10a. There is insufficient information to perform the specified actions in time.
10b. The labeling, abbreviations, symbols and location information is insufficient for the operator to perform the required actions in time.
10c. There is information necessary to management of-the emergency condition missing.
10d. The makeup of the operating shift prevents them from performing the procedure action steps within or at the designated time intervals.
10e. The procedure inadequately coordinates actions when the actions are assigned to specific shift personnel.
The design of the control room prevents the operators from performing the designated sequence in time.
10g. The operator cannot obtain the information specified from the plant instrumentation that is provided.
10}I. There is information or equipment not specified which is required to accomplish a task.
10i. The plant responses do not agree with the EOP basis.
10j. The actual instrument readings and tolerances are not consistent with the values stated.
HEM/PROC-PKG Page 20 of 30
ATTACHMENT 5,3 TABLE TOP VALIDATION CHECKLIST (continued)
ITEM CATEGORY YES I NO 11a. The LabeLing, abbreviations, symbols and locatio'n information is not suEficient Eor the operator to find the needed equipment.
12a. The labeling, abbreviations, symbols and locatio'n information is not sufficient Eor the operator to find the needed equipment.
12b. Figures and tables are inadequately identified, or are not understandable, or readable.
Values on figures and charts are difficult'to determine.
12d. The operator cannot obtain the information specified from the plant instrumentation that is provided.
MEM/PROC-PKG Page 21 of 30
Osl ATTACHMENT 5.3 TABLE TOP VALIDATION CHECKLIST COMMENT SHEET (Attach Additional Pages if necessary)
OPERATOR DEBRIEFING EVALUATOR COMMENTS (Mandatory For Items Answered YES)
Signature/Date RESOLUTION (Mandatory For Deficiencies Noted Above)
Signature Date MEM/PROC-PKG Page 22 of 30
OS1 ATTACHMENT 5,3 SIMULATOR VALIDATION CHECKLIST PROCEDURE NUMBER REV ~
TITLE NAME SHIFT POSITION PARTICIPANTS: SHIFT FOREMAN SRO RO BOP STA NAME SIGNATURE EVALUATORS
)=This session is being videotaped This session is not being videotaped (EXPLAIN)
Attach the following'information to the completed checklist:
- 1. Simulator Scenario
- 2. Marked up procedure pages, if changes are identified
- 3. Videotape of session (If used)
Route the completed package to the Operations Support Supervisor Pages Attached MEM/PROC-PKG Page 23 of 30
OS1 ATTACHMENT 5,4 SIMULATOR VALIDATION CHECKLIST This Eorm guides the evaluation of the performance deviations identified by the Simulator validation method. As each main category is considered, answer the question YES or NO. If the answer is YES, complete the sub-category questions on the attached pages. The completed sub-category questions Eor each item answered YES must be attached to the checklist. Identify the affected part(s) of the procedure Eor each YES answer in the comment section.
ITEM CATEGORY YES/NO An operator performed an action not specified by the procedure.
If YES, complete items la through le 'of this checklist.
- 2. An operator performed appropriate actions in the wrong sequence.
If YES, complete'items 2a through 2c of this checklist.
3 ~ An operator made an incorrect transition.
If YES, complete items 3a through 3e of this checklist.
An operator did not operate equipment as directed by the procedure.
If YES, complete items 4a through 4c of this checklist.
5 ~ An operator selected the wrong pro'cedure.
If YES, complete items 5a through 5c of this checklist.
- 6. An operator recorded an inappropriate value.
If YES, complete .items 6a through 6d of this checklist.
7 ~ An operator failed to perform an action specified by the procedure.
If YES, complete items 7a through 7e of this checklist.
MEM/PROC-PKG Page 24 of 30
OS1 ATTACHMENT 5.4 SIMULATOR VALIDATION CHECKLIST (continued}
ITEM CATEGORY YES/NO
- 8. An operator did not make a transition when required.
If YES, complete items 8a through 8d of this checklist.
- 9. An operator failed to record a required value.
If YES, complete items 9a through 9d of this checklist.
- 10. An operator was not able to complete required actions in time.
If YES, complete items 10a through 10j of this checklist.
An operator could not locate required equipment.
If YES, complete items lla of this checklist.
- 12. An operator recorded a value after time limit.
If YES, complete items 12a through 12d of this checklist.
MEM/PROC-PKG Page 2S of 30
0 Os 1 ATTACHMENT $ .4 SIMULATOR VALIDATION CHECKLIST (continued)
ITEM CATEGORY YES/NO la. Information necessary to management of the emergency condition is missing.
lb. The wording is ambiguous or obscure.
lc. There are alternate success paths that are not included.
1d. There is information or equipment required to accomplish a task not specified sufficiently.
le. There is action information in a Caution or Note.
2a. The makeup of the operating shift prevents them from following the designated action step sequence.
2b. The design of the Control Room promotes deviation from the specified sequence.
Zc ~ There is insufficient information to perform the specified actions in the required sequence.
3a. There is insufficient information for a decision at the transition.
3b. The alternatives are not adequately described at the decision point.
3c ~ The wording of the transition is ambiguous or obscure.
If transition
'f, 3d. made to wrong procedure, there is insufficient information for the operator to find the correct procedure.
3e ~ transition made to wrong step, the destination is not specified sufficiently and clearly enough to guide the operators to the correct step.
MEM/PROC-PKG Page 26 of 30
OS1 ATTACHMENT 5,4 SIMULATOR VALIDATION CHECKLIST (continued)
ITEM CATEGORY YEE/NO 4a. The labeling, abbreviations, symbols and location information in the procedure and on the equipment is insufficient for the operator to perform the required action.
4b. There is insufficient information to perform the specified actions.
4c. The Cautions and Notes are not clearly and corrected identified and understandable.
sa. The observable plant symptoms lead the operator to an inappropriate procedure.
5b. There is insufficient information for the operator to select the correct procedure.
5c. The Cautions and Notes are not clearly and correctly identified and understandable.
6a. Figures and tables are inadequately identified, or are not understandable, or readable.
6b. Values on figures and charts are difficult to determine.
6c. The operator cannot obtain the information
'specified in the procedure from the plant instrumentation that is provided.=
6d. The instrument readings and tolerances for plant instruments are inaccurate.
7a. There is insufficient information to perform the specified actions.
7b. The makeup of the operating shift prevents them from performing the specified steps.
7c ~ It inadequately coordinates actions when the actions are assigned to specific shift personnel.
7d. The plant responses do not agree with the EOP basis.
7e. The Cautions and Notes are not clearly and correctly identified and understandable.
MEM/PROC-PKG Page 27 of 30
~,
OS1 ATTACHMENT 5.4 SIMULATOR VALIDATION CHECKLIST (continued)
ITEM CATEGORY YES I NO Sa. There is insufficient information for a decision at the transition.
Sb. The alternatives are inadequately described at the decision point.
Sc. The wording of the transition is ambiguous or'bscure.
Sd. The Cautions and Notes are not clearly and correctly identified and understandable.
9a. Figures and tables are inadequately identified, or are not understandable, or readable.
9b. Values on figures and charts are difficult to determine.
9c. The operator cannot obtain the information specified from the plant instrumentation that is provided.
The Cautions and Notes are not clearly and 9d.'0a'.
correctly identified and understandable.
There is insufficient information to perform the specified actions in time.
10b. The labeling, abbreviations, symbols and location information is insufficient for the operator to perform the required actions in time.
10c. There is information necessary to management of the emergency condition missing.
lod. The makeup of the operating shift prevents them from performing the procedure action steps within or at the designated time intervals.
10e. The procedure inadequately coordinates actions when the actions are assigned to specific shift personnel.
10E. The design of the Control Room prevents the operators from performing the designated sequence in time.
10g. The operator cannot obtain the information specified from the p}.ant instrumentation that is provided.
10h. There is information or equipment not specified which is required to accomplish a task.
10i. The plant responses do not agree with"the EOP basis'0j.
The actual instrument readings and tolerances ar' not consistent with the values stated.
MEM/PROC"PKG Page 28 of 30
Osl ATTACHMENT 5.4 SIMULATOR VALIDATION CHECKLIST (continued)
ITEM CATEGORY YES/NO lla. The label.ing, abbreviations, symbols and location information is not sufficient for the operator to find the needed equipment.
12a. The labeling, abbreviations, symbols and location information is not sufficient for the operator to find the needed equipment.
12b. Figures and tables are inadequately identified, or are not understandable, or readable.
12c. Values on figures and charts are difficult to determine.
12d. The operator cannot obtain the information specified from the plant instrumentation that is provided.
MEM/PROC-PKG Page 29 of 30
OSl ATTACHMENT 5.4 SIMULATOR VALIDATION CHECKLIST COMMENT SHEET (Attach Additional Pages if necessary)
OPERATOR DEBRIEFING EVALUATOR COMMENTS (Mandatory For Items Answered YES)
Signature/Date RESOLUTION (Mandatory For Deficiencies Noted Above)
Signature/Date MEM/PROC-PKG Page 30 of 30