ML17214A527
| ML17214A527 | |
| Person / Time | |
|---|---|
| Site: | Saint Lucie  |
| Issue date: | 10/26/1983 |
| From: | FLORIDA POWER & LIGHT CO. |
| To: | |
| Shared Package | |
| ML17214A526 | List: |
| References | |
| RTR-NUREG-0737, RTR-NUREG-737 PROC-831026, NUDOCS 8310310102 | |
| Download: ML17214A527 (65) | |
Text
PROCEDURES GENERATION PACKAGE ST. LUCIE PLANT UNIT 1 AND 2 831031 0102 83i026 PDR ADOCK 05000385 F' PDR "-
C 0
~z".~C,)"5 ."cg"~@~4'~>'V ~i 4~"'c>'@%
TABLE OF CONTENTS
~Pa e INTRODUCT ION o ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ o ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ 1 I .1 PURPOSE o ~ ~ ~ ~ ~ ~ ~ ~ r ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ o ~ ~ ~ ~ ~ 1 1 ~ 2 SCOPE. ~ .. ~ ~ ~ ~ ~ .......... ~ .. ~ ~ ~ ~ ... ... ... ........ .......1
~ ~ ~ ~
1.3 ORGANI2ATXONo ~ oo ~ ~ ~ ceo. ~ ~ oo ~ oo ~ . ~ ~ ~ o ~ o ~ ~ ~ ~ ~ ~ ~ oo ~ ~ ooeo.o.oool 2~ PLANT-SPECIFXC TECHNICAL GUID INES ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ o ~ ~ ~ ~ 2 2~ 1 GENERALo ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ o ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ 2 2 2 PROGRAM DESCRXPTION....... ~ ........ ~ . ~ .....................2 2e2el MECHANICS OF CONVERSIONe ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ 2 2 ' ' DOCUMENTATION.... ~ . ~ ~ ~ ~ ~ ~ ~ ~ ........ ~ .. ~ . ~ ~ . ~ .. ..
~ ~ ~ .3 3o WRITERS GUIDE FOR EOPS ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ 6 3~ 1 GKNERALe ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ 6 3 ' DOCUMENT DESCRXPTXONe ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ 6 EOP VERIFICATION PROGRAMo ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ o, ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ o ~ 7 4~ 1 GENERAL o ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ o ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ 7 4 ' PROGRAM DESCRIPTXONo.ooo.o ~ ooooo.o ~ o ~ oo ~ ooo. oooo.e.oo. o.oo7 EOP VALIDATION PROGRAM ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ 'i ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ 8 5~1 GKNERALeo ~ ~ ~ ~ ~ ~ ~ ~ o ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ o ~ ~ 8 5e2 PROGRAM DESCRIPTIONe ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ e ~ ~ 8 EOP TRA XNXNG PROGRAM o ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ 9 6 1 GOALS ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ 9 6 ' TRAINING METHODS ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ o ~ ~ ~ 9 6 'e'1 CLASSY INSTRUCTIONe ~ ~ ~ ~ ~ ~ ~ ~ ~ e ~ ~ e ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ 9 6o2o2 PROCEDURE WALK THROUQHS ~ oo ~ ~ ~ ~ o ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ o ~ oooo9 6o2o3 SIMULATOR EXERCISES ~ ee. ~ . ~ ~ ~ o ~ ~ oo ~ ~ ~ ~ ~ oo ~ o.. ~ ~ ~ ooooo9 6 ' REFRESHER TRAXNXNGe ~ o ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ e ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ o ~ ~ ~ ~ ~ 10 6e4 TRAINING ON REVISIONSo ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ol0 6 5 INPUTS INTO TRAINXNG PROGRAM CHANGES ~ ~ ~ ~ ~ ~ . ~ ~ . ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ 10 6 '.1 SUPPORTING TRAINING MATERIAL CHANGES ~ ~ ~ ~ . ~ ~ ~ ~ ~ ~ ~ ~ ~ 10 6 ' ' OPERATOR FEEDBACKo ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ o ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ 10 6.6 EVALUATXONo ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ 10 ATTACHMENT 1 ST. LUCIE PLANT WRITERS GUIDE FOR EMERGENCY OPERATING PROCEDURES ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ . ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ 11
e s 1 ~ IHTRODUCTIOH 1 ~
1" PURPOK The purpose of this Procedures Generation Package (PGP) is to describe the emergency operating procedures (EOPs) development at the St. Lucie Plant, Unit 1 and Unit 2. CE-type pressurized water reactor.
1.2 SCOPE This docuaant was developed in response to Supplement 1 to NUREG-0737, Item 7.2b), page 19.
- 1. 3 ORGANIZATION This document consists of the following six parts:
o Intro duction o Plant-Specific Technical Guidelines o Writers Guide for EOPs o EOP Verification Program o EOP Validation Program o EOP Training Program Each part describes the approach taken as part of the overall EOP Implementation Plan for St. Lucie Plant, Unit 1 and Unit 2.
PAGE
, 2 PLAHT-SP C C TECHNICAL GUZDELZgPS 2~ 1 GENERAl'he followiag program for converting the Combust1on Engineeriag Emergency Procedure Guidelines (EPGs} into EOPs has been developed and will be used by St.
Luci.e Plant Unit l,and Unit 2.
The EPGs, CEN 152, Revis1oa 1, Dated November, 1982, will be used for the initially implemented EOPs. When Revision 2 is completed aad approved, the revised information will be incorporated using the established revision, review, aad approval process.
The followiag ma)or items were considered in the methodology to be used.
o nwchanics of conversion o location of the plant~ecific techxd.cal information o how the plaatmpecific technical information will be used o the use of old EOPs o documeatat1on requirements o use of the backgrouad information supplied with techaical guidelines 2 2 PROGRAM DESCRTPTXON 2 2 ' Macha'.cs of Coaversion 2~2~ 1~1 Preparation The designated EOP writing team will obtain and review the following plant-spec1fic techaical information (EOP source docuamnts)x o Combustion Eagiaeeriag EPGs, Revision 1, with background information o PSAR Unit 1 and Uait 2 o St. tucie Plant Writers Guide for Emergency Operating Procedures (Rev. 0) o Techaical Specifications for Unit 1 and Unit 2 o the Iost current revision of existing EOPs o as-built plant drawings The EOP source documents are located in the Document Control Center PAGE
'2.2.1 ~ 2 -- Vriting EOPs The EOP writing team will follow the EPGs step-by~tep, adding footnoted information where designated. Concurrently, the writers will review appropriate EOP source documents The information on Pigure 1 will be completed during the writing of the EOP. The justification section will be used to provide the plant-specific technical information or analysis to assist in the verification process.
2.2. 2 Documentation The completed Figure 1 (Documentation Sheet) will be provided as a source document to assist in the EOP verification process and in the revision, review, and approval process.
An example of a completed "Step Documentation" sheet is presented as Figure 2, LOCA Procedure Page 2 of 4, comparing it to the equivalent EPG Step of Page 5-72 Step 2a)
PAGE FIGURE 1 EOP Title DOCUHENTATION SHEET EOP Number Rev ~
Page of STEP JUSTIFICATION OF NlNBER EOP CEN '152 DIFFERENCES SIGNATURE/DATE PAGE .
RIGURE 2 EOP Title LOCh DOCUMENTATION SHEET EOP Number Rev. 2 Paga 2 af 4 STEP JUSTIRICATION OR NUMBER EOP CEN 152 DIFRERENCES SIGNATUREIDATE EPG If pressurizer level If pressuricer level Recorded to remove reference Pg. 5-72 is outside normal is between (35") and to level in inches. Joe Doe Step 2a) operating band ".. (245") . St. Lucie Plant level. OCT 10 83 instruments are in ercenta e PAGE .
- 3. WRITERS GUIDE POR EOPs I
3~ I GENERAL A writers guide for EOPs is a plant-specific document that provides instructions on writing EOPs, using good writing priaciples. Tn addition to establishing sound writing principles, the guide helps to promote consistency among all EOPs and their revisions, independent of the number of EOP writers.
The writers guide will be revised, as necessary, based. on feedback from operator trainingp experience, and validatioa.
t
- 3. 2 DOCUMENT DESCRIPTION Information on the following ma)or items is included in the plantmpecific writers guide for EOPs:
o EOP format o EOP organization o EOP level of detail o role of the EOP within the procedure system aad network o EOP conteat o mechanics of style The St. Lucie Plant Writers Guide for Emergency Operating Procedures, Revision 0 is based on the iadustry document Emer ency eritin Procedures Vritin daliue (INPO 82-017), developed by the Emergency Operating Procedures Iupletmntation Assistance (EOPIK) Eevieu Group aad published by.INPO. The gt.'.
Lucie Plant guide is provided as Attachmeat, I.
PAGE 4e EOP VERIPICATION PROGRAM 4e 1 GENERAL EOP verif1cation is the evaluation performed to confirm the written correctness of the procedure and to ensure that applicable generic and plantmpecific technical information has been incorporated properly. This evaluation also checks that the human factors aspects presented 1n the writers guide for EOPs have been applied 4.2 PROGRAM DESCRIPTION When developing this EOP verification program, the following ma)or items were considered:
o how EOP verification vill be performed o how completion of the EOP verification process wi.Q. be documented o what process will be used in resolving discrepancies The verification program is based on the industry document Emer ency Operatin Procedures Verification Guideline (INPO 83>>004), developed by the EOPIA Review Group and published by INPO The.St. Lucie Plant ver1fication procedure for emergency operating procedures should address the following obgectives:
o EOPs are technically correct, i.e., they accurately reflect the technical gu1delines and other EOP source documents.
o EOPs are written correctly, 1 e., they'ccurately reflect the plant-specific writers guide.
o A correspondence exists between the procedures and the control room/plant hardware o The language and level of information presented in the EOPs are compatible with the qualifications, training, end experience of the operating staff.
PAGE
- 5. EOP VALIDATION PROCRAH 5, 1 GENERAL EOP validation is the evaluation performed to determine that the actions specified in the procedure can be performed by the operator to manage the eaargency conditions effectively. The methodology for EOP validation utiU.zes present, available methods at the St. Lucie Plant while recognizing and allowing for future= improvements. The EOP validation will evaluate the opexators'bility to manage, emergency conditions using the EOPs. It will validate that part of the EOP not covered by any technical validation of generic technical guidelines.
5o2 PROGRAN DESCRIPTION When developing this EOP validation program, the following major items were considered:
o how EOP validation will be performed o how to'ppropriately use simulators, walk-throughs, or table-top methods of validation o how operating and training experience will be integrated into the program evaluation o the evaluation criteria to be applied and the methods to be followed in resolving discrepancies o how completion of the EOP validation process will be documented The px'ogram is based on the industry document Emex'ncy Operatin Procedures Validation Guideline (INPO 83-006); developed by the EOPIA Review Group and published by INPO. The St. Lucie Plant validation procedure for emergency operating procedures should address the following objectives:
o EOPs are usable, i.e., they can be understood and followed without confusion, delays, and errors.
o A correspondence eMsts between the procedures and the contxol room/plant har dware.
The instructions presented in the EOPs are compatible with the shift manpower, qualifications, training, and exper5.ence of the operating staff.
o A high level of assurance exists that the procedures will work, i.e., the procedures guide the operator in mitigating transients and accidents.
PAGE 6~ EMERGENCY OPERATING PROCEDURES TRAINING PROGRAM (EOPT) 6.1 GOALS The EOPT will have as its basis the following goals:
o To enable the operators to understand the structure of the EOPs.
o To enable the operators to understand the technical basis of the EOPs.
o To enable the operators to have a working knowledge of the technical content of the EOPs.
o To enable the operator to be able to use the EOPs under operational conditions.
Lesrning objectives will be developed to support each of these goals 6 2 TRAINING METHODS The EOPT wiLL utilize various combinations of classroom instruction, practice walk throughs, and simulator exercises as appropriate for the learning ob)ectives.
6 2.1 Classroom Instruct1on Classroom instruction session will include information on the following:
o Technical bases of the EOPs o Technical content of the EOPs o Structure of the EOPs 6.2.2 Procedure Walk Throughs Familiarity with procedural content, structure, and implementation will be gained by perforadng practice walk throughs in the control room.
6.2.3 Simulator Exercises Simulator practice on performing EOPs will occur as a part of regularly scheduled simulator requalification or hot license training. Scenarios wiLl be developed to be as specifically appl1cable as possible to the generic simulator now being used. Procedural practice wilL be structured such that operators are performing their normal control room functions. Unt11 a plant specific simulator is available, complicated scenarios will be discussed during classroom instruction or control room walk throughs.
PAGE I
6~3 REFRESHER TRAINING All licensed operators will conduct procedural walk throughs for refresher training. The walk throughs may be conducted either in the plant control room or the simulator. Simulator scenarios will be as described"in 6-2.3 above.
Simulator exercises will be evaluated by the Training staff or operations supervision. Evaluation results will be critiqued for feedback to the operators and to determine additional training needs.
6~4 TRAINING ON REVISIONS TO EOPs Training on revisions to EOPs will be accomplished through a program of required readings (self taught), preshift briefings, or lectures in the requalification program. Determination of appropriate methods will be made by'he training staff.
6 ' INPUTS INTO TRAINING PROGRAM CHANGES 6.5.1 Supporting Training Material Changes Changes to supporting training material will be factored into updated lesson plane and operator memos.
6.5.2 Operator Peedback Operator feedback resulting from EOP verification, EOP validation, and training critique forms will be used to keep the training program and EOPs current and relevant.
6 ' EVALUATION An evaluation will be used to ensure that the training program goals have been accomplished.
PAGE'10-
I
~ ~ ~
ST LUCIE PLhtiT WRITERS GUIDE FOR EMERGENCY OPERATING PROCEDURES
FIGURE 5 FLORIDA POWER & LIGHT COMPANY ST. LUCIE PLANT QUALITY INSTRUCTION NUMBER QI 5-PR/PSL-2 REVISION 0 1 ~ TITLE: WRITERS GUIDE FOR EMERGENCY OPERATING PROCEDURES 2~ PREPARED BY: F. M. Ro er October 1, 1983
- 3. SUBCOMMITTEE REVIEW BY: (including content list)
W. S. Windecker for FP&L PNE October 1, 1983
- 4. REVIEWED BY FRG ON: / 2. 19~@
5o APPROVED BY: ant Mana er /4'<719/7 6~ REVISION REVIEWED BY FRG ON: 19
- 7. 'PPROVED BY: Plant Mana er 19 Type of procedure (such as Operating, I & C, Chemistry, etc.)
- Procedure number with prefix of 1 for Unit 1 only, 2 for Unit 2 only, and no prefix if for both units.
QI 5-PR/PSL-2 Revision 0 October 1983 Page 1 of 32 FLORIDA POWER 6 LIGHT COMPANY NUCLEAR ENERGY DEPARTMENT ST. LUCIE PLANT WRITERS GUIDE FOR EMERGENCY OPERATING PROCEDURES 1 ' APPROVAL:
Reviewed by Fac lit Review G~rup 19 g3 Approved by: ~444% ~lant Manager /4 19gZ Revision Reviewed by F R G 19 Approved by Plant Manager 19
2.0 PURPOSE
2.1 This document is intended to provide administrative guidance in the preparation of emergency operating procedures (EOPs).
3.0 SCOPE
3.1 This guide applies to the preparation of all EOPs.
4oO RESPONSIBILITIES:
4.1 Each person drafting or revising an EOP is responsible for using the format described in Appendix A to this procedure.
4.2 The Plant Manager is responsible for approving each EOP.
4.3 Each EOP shall be verified for technical accuracy and written correctness using QI 5-PR/PSL-3, "EOP Verification Procedure", prior to implementation.
4.4 Each EOP shall be validated for usability and operational correctness using OI 5-PR/PSL-4, "EOP Validation Procedure", prior to implementation.
QI 5-PR/PSL-2 0 Revision October - 0 1983 I
I Page 2 of 32
5.0 INSTRUCTIONS
5.1 The format and instructions for preparing EOPs is contained in Appendix A to this procedure.
I OI 5-PR/PSL-2 Revision 0 October 1983 Page 3 of 32 APPENDIX A FLORIDA POWER & LIGHT COMPANY ST. LUCIE PLANT WRITERS GUIDE FOR EMERGENCY OPERATING PROCEDURES
QI 5-PR PSL-2 Writers Guide Rev. 0 Page 4 o f 32 I
I TABLE OP CONTENTS I
Section ~Pa e INTRODUCTIONooooooooooooooeooooo.oo.o..oo.oo.oooooooo.oooooooo 4 1 ~ I PURPOSEe ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ 4 I 1.2 SCOPEo ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ 4 t 2 EOP DESIGNATION AND NUMBERING................................. 4 t 2.1 COVER SHEETo ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ o ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ 4 I 2' PROCEDURE DESIGNATION. ~ . ~ ~ . ~ ~ ~ . ~ ~ ~ ~ ~ . ~ ~ ~ . ~ ~ . ~ .. ~ ~ . ~ ~ . ~ ~ ~ 4 I 2 ' PROCEDURE NUMBERING, ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ . ~ . ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ .~. 6 I 2' REVISION NUMBERING AND DESIGNATIONS'.5
~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ 6 I PAGE IDENTIFICATION AND NUMBERING.... ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ 6 I 3 PORMAT..................................... ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~
'8 I 3ol PAGE FORMATo ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ o' ~ ~ ~ ~ ~ ~ ~ ~ ~ 8 t 3.2 PROCEDURE ORGANIZATION................................. 8 I 3 ' SECTION NUMBERING. ~ ~ ~ . ~ . ~ ~ o ~ ~ ~ ~ ~ ~ o ~ o ~ e ~ ~ ~ ~ ~ o ~ ~ ~ . ~ ~ . ~ ~ ~ o 8 I 3 ' INSTRUCTION STEP NUMBERINGo ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ 9 I WRITING INSTRUCTIONAL STEPS.................................. 9 I 4 ' INSTRUCTION STEP LENGTH AND CONTENT.o . ~ ~ ~ ~ ~ ~ .. .o.....
~ ~ 9 I
~
4~ 1 ~ 1 INSTRUCTION COLUMNooo ~ ~ ~ . ~ ~ ~ ~ o ~ o.' ..... ~ ~ ~ o ~ o ~ o ~ 11 I 4. 1.2 CONTINGENCY ACTIONS COLUMN...................... F 11 I 4.2 USE OP LOGIC TERMS oooo..oooooo.oooooooo.ooooooooooooooo ~ ll I 4 ' USE OP CAUTIONARY INFORMATION AND NOTES........... ~ ... ~ ~ 12 t 4 ' CALCULATIONS ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ol3 I 4.5 USE OP UNDERLINING. ~ . ~ ~ ~ . ~ ~ ~ ~ . ~ ~ ~ ~ . ~ ~ ~ .. ~ . ~ ~ ~ ~ ... ~ ~ . ~ . ~ .14 I 4.6 REFERENCING AND BRANCHING TO OTHER PROCEDURES OR STEPSON 14 I 4 ' COMPONENT IDENTIPICATIONoooooooooooooooooo.ooooooo..ooo.l4 HEADINGS' I 4.8 LEVEL OF DETAIL ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ 15 I 4.9 PRINTED OPERATOR AIDS...................................16 I 4.9ol UNITS OF MEASUREo.o,ooo..o..o.ooooo...oo..o......16 I 4' ' TITLES AND .. ~ .~.~. ~ . ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ 16 t 4 ' ' PIGURE, TABLE, AND ATTACHMENT NUMBERING. ~ . ~ ~ ~ ~ ~ ~ ~ 17 I
I
QI -PR PSL-Writers Guide Rev ~ 0 Page 5 of 32 I
l TABLE OF CONTENTS (Continued) l Sec'tion ~Pa e
) 5 MECHANICS OF'TYLE ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ 17 I 5.1 SPELLINGoo ~ ~ ~ oo ~ ooo.o.....o.oooooo.ooo.oo.o..o ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ 17 I 5.2 HYPHENATION.......... ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ o ~ ~ ~ ~ o ~ ~ ~ ~ ~ 17 1
5 ' PUNCTUATIONoo ~ oo..oo.o.o.......ooooooooo oooo.o ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ 18 I 5 ~ 3ol BRACKETS ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ 18 t 5 'o2 COLON..o.oo..ooooooooooooo ~ oooooo.oo.oo ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ 19 5 ' ' COMMAo ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ o ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ 19 5' ' PARENTHESES ~ ~ ~ ~ ~ ~ o ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ 19 l 5' ' PERIODo ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ "
~ ~ ~ ~ ~ ~ ~ 19 l 5 ' VOCABULARY.~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ . ~ ~ ~ ~ . ~ ~ ~ ~ ~ . ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ 19 l 5' NUMERICAL VALUES ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ o ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ 23 l 5.6 ABBREVIATIONS, LETTER SYMBOLS, AND ACRONYMS... ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ 24 6 TYPING FORMATo ~ o ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ 24 I 6 ' GENERAL TYPING PAGES' AIDS'~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~
INSTRUCTIONS ~ ~ ~ . ~ ~ ~ ~ ~ ~ ~ ~ 24 I 6' PAGE ARRANGEMENT. ~ ~ ~ ~ ~ o ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ 25 t 6.3 HEADING AND TEXT A18ANGEMENToooooooooooooo ~ o ~ oooo ~ ~ ~ ~ ~ ~ ~ 25 t 6o4 BREAKING OP WORDSo.'ooooooooo.oooooo.ooooooooooooo ~ ~ ~ ~ ~ ~ ~ 26 I 6.5 ROTATION OP ............ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ o ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ 26 I 6 ' PRINTED OPERATOR .. ~ ~ ~ . ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ 26 6.7 CAUTIONS AND NOTESooo.ooo..'ooo.o.ooo.ooooo.ooo.o ~ ~ ~ ~ ~ ~ ~ 28 l 6 ' USE OP FOLDOUT PAGES ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ 29 I 6' USE OP OVERSIZED PAGES ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ 29 1
6 '0 USE OP REDUCED PAGES ~ ~ ~ o ~ ~ ~ ~ ~ ~ ~ ~ ~ .~, ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ . ~ ~ ~ ~ ~ ~ ~ 29 t 7 REPRODUCTION, ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ o ~ ~ ~ ~ ~ o ~ ~ ~ ~ ~ ~ ~ ~ ~ os ~ ~ ~ ~ ~ o ~ ~ 29 I
I t
l t
I
QI 5-PR PSL-Writers Guide Rev. 0 Page 6 of 32 1 INTRODUCTION 1.1 PURPOSE This document is intended to provide administrative guidance in the preparation of Emergency Operating Procedures, (EOPs).
The CE Emergency Procedures Guidelines shall be used as a format and technical guide during this preparation.
l 1. 2 SCOPE This guide applies to the preparation of all EOPs.
I l
2 EOP DESIGNATION AND NUMBERING I
) 2. 1 COVER SHEET Each EOP shall have a cover sheet (see Figure 1) which will identify the procedure and the authorized revision. To .identify the procedure, a title should be used that is sufficiently short and descriptive of the emergency condition or purpose for which the procedure is applicable.
l 2.2 PROCEDURE DESIGNATION The emergency operating procedure designator shall be EOP. The applicable unit is to be signified by the number 1 or 2 preceding EOP. Each unit shall have its own EOPs.
I I
f
. I I
l I
l I
QZ -PR PSL-2 Writers Guide Rev. 0 Page 7 of 32 Pigure 1. Cover Sheet
0 QI -PR PSL-2 Writers Guide Rev. 0 Page 8 of 32 I 2~3 PROCEDURE NUMBERING I A sequential number shall follow the procedure designator and should consist I of one or two digits.
I, Example 1 EOP 5 I I I I Sequence Number I I I Procedure Designator I I Applicable Unit I
I 2.4 REVISION NUMBERING AND DESIGNATION I Revisions to EOPs shall follow the same flow path as Off-Normal and Operating I procedures during the revision process.
I I One or two digits following the abbreviation "Rev" shall be used to designate the revision level of the EOP.
Example Rev 1 I I Revision Level I Abbreviation To identify revisions to the text of an EOP, a change bar shall be located in the right margin, alongside the text change.
I A 5 in the left margin shall indicate the text contains a licensing commitment and should not be revised without licensing approval.
2.5 PAGE IDENTIFICATION AND NUMBERING Each page of the procedure will be identified by:
a) The procedure designator and numbers.
b) The revision number c) An abbreviated title.
d) The page number, specified as "Page of ". This information will be together and located in the upper'right hand corner of each page. (See Figure 2).
QI -PR PSL-Writers Guide Rev ~ 0 Page 9 of 32 Figure 2. Page Format
0 f
0 U
QI 5-PR PSL-2 Writers Guide Rev. 0 3 FORMAT I The following format is to be applied consistently for al 1 EOPs.
I I
- 3. 1 PAGE FORMAT .I A dualmolumn format shall be used. The left-hand column is designated for I operator actions, and the right-hand column is .designated for contingency I I actions to be taken when the expected response is not observed. A sample I page format is presented in Figure 2. I I I 3 ' PROCEDURE ORGANIZATION I The following section headings will be used for all EOPs. I I I I I title will be TITLE The stated for operator association with the I I ENTRY CONOYTYONS ~
1 t I I 2 ENTRY CONDITIONS The entry conditions will include \ only those I alarms, indications, operating conditions, automatic system actions, t or other unique symptoms that the operator is to use in deciding to I use the procedure. I I I
.I 3 OPERATOR ACTIONS The operator actions will be short, concise, I' identifiable instructions that give appropriate directions to the user.
I I 3 ' SECTION NUMBERING t Arabic numerals will be used for numbering sections and subsections in the I decimal'ormat. (See Figure 2, Page Format) t I
I I
I I
I I"
l 4
V
'I 1
QI -PR PSL-Writers Guide 0
'ev.
Page 11 of 32 3.4 INSTRUCTION STEP NUMBERING Instruction steps in a section or subsection shall be numbered and indented as follows:
- 1. Verify .
ao Check ~ ~ ~
P J
I The same step number scheme shall be used in both the right and left columns t of the procedure.
I l 4 WRITING INSTRUCTIONAL STEPS l
I 4.1 INSTRUCTION STEP LENGTH AND CONTENT I Instruction steps shall be concise and precise. General guides to be used in
.j meeting these objectives are as follows:
I I o Each instruction step should deal with only one idea.
l I o Short, simple sentences should be used in preference to long, compound, or complex sentences.
I I o Complex evolutions should be prescribed in a series of steps, with each I step made as simple as practicable.
l I o 'bjects of operator actions should be specifically stated. This includes I identification of exactly what is to be done and to what.
I o Por instructional steps that involve an action relating to three or more objects, the objects should be listed with space provided for operator checkof f.
I o Limits should be expressed quantitatively whenever possible (refer to I Subsection ST 5).
I j'
Ql 5-PR PSL-2 Writers Guide Rev ~ 0 Page 12 of 32 o Each step should have a check off to indicate that the following were I either observed or performed:
I a. Symptoms
- b. Automatic Actions I c. Operator Actions o Mandatory sequence of steps is assumed unless otherwise stated.
o Identification of components and parts should be complete.
o Instruction content should be written to communicate to the operator.
o Expected results of routine tasks need not be stated.
I o When actions are required based upon receipt of an annunciated alarm, the I setpoint of the alarm should be given for ease of verification. '
I I When resetting or restoration of an alarm or trip is required, the I I expected resul'ts immediately following the resetting or restoration I I should be given if it would be beneficial to the operator. I I I s
o 'hen considered beneficial to the operator for proper understanding and I performance, describe the system response time associated with performance J
of the instruction. I I 'I ~
I I o When system response dictates a t1me frame within which the instruction ih I should be accomplished, prescribe such time frame. If" possible,'owever, avoid using time to initiate operator actions ~ Operator act1ons should be )
I related to plant parameters. I I t l o When anticipated system response may abrersely affect instrument I I indications, describe the conditions that will likely introduce 1nstrument I error and means of determining if instrument error has occurred by using a NOTE.
l
Q -P P Writers Guide RBV ~ 0 Page 13 of 32 o When additional confirmation of system response is considered necessary, prescribe the backup readings needed.
- 4. 1. 1, Instruction Column The left-hand column of the dual-column format shall contain the operator e
instructional steps. The following guides are established for this column, in addition to the general guides above.
t o Expected indications should be presented in this column.
l 4.1.2 Contingency Actions Column Contingency actions shall be presented in the right-hand column of the dual-column format. Contingency actions are operator actions that should be taken in the event a stated condition, event, or task does not represent or achieve the expected result. The need for contingency action occurs in con)unction with tasks involving verification, observation, confirmation, and monitoring.
Contingencies should be written so that the conditional statement precedes the action statement. "If......Then......."
Contingency actions should be specified for each circumstance in which the expected results or actions might not be achieved. The contingency actions should identify, as appropriate, directions to override automatic controls and to initiate manually what is normally automatically initiated.
4 ' USE OP LOGIC TERMS The logic terms ENO, OR, NOT, TP, TP NOT, WHEN, and THEN are often necessary to describe precisely a set of conditions or sequence of actions. When logic statements are used, logic terms will be highlighted so that all the conditions are clear to the'. operator. Emphasis will be achieved by using capitalization and underlining. All letters of the logic terms shall be capitalized and the words will be underlined.
The use of AND and OR within the same action shall be avoided. When AND and OR are used together, the logic can be very ambiguous.
QI 5-PR PSL-2 Writers Guide Rev ~ 0 Page 14 of 32 The dualmolumn format used equates to the logic; ZF NOT the action in the left-hand column, THEN folios the action specified in the right hand column.
I Use other logic terms as follows:
I o When attention should be called to combinations of conditions, the word I AND shall be placed between the description of each condition. The word I AND shall not be used to goin more than three conditions. If four or more I conditions need to be )oined, a list format shall be used.
~
I o The word OR shall be used when calling attention to alternative I combinations of conditions. The use of the word OR shall always be in the I inclusive sense. To specify the exclusive "OR," the following may be I used: "either A OR B but not both."
I o When action steps are contingent upon certain conditions or combinations I of conditions, the step shall begin with the words IP or WHEN followed by I a description of the condition or conditions, a comma, the word THEN, I followed by the action to be taken. WHEN is'sed for an expected I condition. IP is used for an unexpected but possible condition.
I o Use of,IP NOT should be limited to those cases in whi'ch the operator must I respond to the second of two possible conditions. IP should be used to I specify the first condition.
I v
o THEN shall not be used at the end of an action step to instruct the I operator to perform the next step because it runs actions together.
I I
I I
I I
1 I
I"
P QI 5-PR PSL-2 Writers Guide Rev. 0 Page 15 of 32 4~3 USE OP CAUTIONARY INFORMATION AND NOTES Cautionary information can be considered in two fundamental categories: those that apply to the entire procedure and those that apply to a portion or a specific step of the procedure. Those that apply to the entire procedure are
)* called "PRECAUTIONS" and are covered in operator training. Those that apply
} to a portion of a procedure are called "CAUTIONS" and are placed immediately before the action statements to which they apply.
l Cautions shall extend across the entire page and shall be highlighted as shown in the Example CAUTION. This placement of cautions helps ensure that the procedure user observes the caution before performing the step. A caution cannot be used instead of an action statement. It should be used to denote a potential hazard to equipment or personnel associated with or consequent to the subsequent action statement I
I Cautions should be used to alert personnel to displays based on secondary I sensing modes. For example, when a light indicates a circuit is energized I and not the position of a valve.
I I If additional information other than cautions is necessary to support an action statement, a NOTE should be used. A NOTE should present information I only, not instructions, and should be located in the right-hand column as I as close to the applicable action statement as possible.
l l o The following examples illustrate these instructions.
I a. Example NOTE:
I NOTE I Break identification chart I (Pigure 1) may be helpful t in evaluating the situation I
I l
I
I
'QI -PR PSL-Writers Guide Rev ~ 0 Page 16 of 32
- b. Example CAUTION:
- 'A***A *********************** I CAUTION I Orerfeeding the Steam Generators may cause excessive cooldown. I Do not exceed 75 F/Hr cooldown rate. I I
t, I 4 ' CALCULATIONS I
( Mathematical calculations should be avoided in EOPs. If a value has to be I determined in order to perform a procedural step, a chart or graph should be I used whenever possible. I I
1 4.5 USE OF UNDERLINING I I Underlining should be used for certain headings, emphasis of logic terms and l l CAUTION. I I I I 4' REFERENCING AND BRANCHING TO OTHER PROCEDURES OR STEPS I I Referencing implies that an additional procedure or additional steps will be I used as a" supplement to the procedure presently being used. 'Referencing l other steps within the procedure being used, either future steps or completed I steps, should be minimized. When only a few steps are involved in the I referencing, the steps should be restated in the procedure wherever they are J
needed.
j t To minimize potential operator confusion, branching should be used when the I operator is to leave one procedure or step and use another procedure or step.
l Use the key words "go to " This will alert the operator to leave the I present, step and not return until directed.
. 1 Use quotation marks to emphasize the title of the referenced or branched procedure; examples: Go to E-l, "Loss of Reactor Coolant", Step 5.2.
gl 5-PR PSL-2 Writers Guide Rev ~ 0 Page 17 of 32
- 4. 7 COMPONENT IDENTIFICATION With respect to identification of components, the following rules are to be followed:
Equipment, controls, and displays will be identified in operator language (common usage). This language may not always match engraved names on panels but will be recognizable.
o When the engraved names and numbers on panel placards and alarm windows are specifically the item of concern in the procedure, the engraving should be quoted verbatim and emphasized by using all capitals.
o The names of plant system titles are emphasized by initial capitalization.
t When the word "system" is deleted from the title because of brevity and is I understood because of the context, the title is still emphasized by 1
initial capitalization.
I o If the component is seldom used or it is felt that the component would be l difficult to find, location information should be given in parentheses I following the identification.
I LEVEL OP DETAIL Too much detail in EOPs should be avoided in the interest of 'being able to effectively execute the instructions in a timely manner. The level of detail required is the detail that a newly trained and licensed operator would desire during an emergency condition.
To assist in determining the level of EOP detail, the following general .rules apply ~
QI 5-PR PSL-2 Writers Guide Rev. 0 Page 18 of 32 Por control circuitry that executes an entire function upon actuation of the control switch, the action verb appropriate to the component suffices I without further amplification of how to manipulate the control device; for I example, "Close PCV-07-1A, PCV-07-1B." Recommended action verbs are as I follows: I I
- a. Por power-driven rotating equipment, use Start, Stop. I I
- b. Por valves, use Open, Close, Throttle Open, Throttle Close, Throttle. [
I
- c. Por power distribution breakers, use Synchronize and Close, Open.
l For control switches with a positional placement that establishes a I standby readiness condition, the verb "Set" should be used, along with the engraved name of the desired position. Positional placements are l typically associated with establishing readiness of automatic functions I and are typically named AUTO or NORMAL; for example, "Set the GLAND STEAM I EXHAUSTER Control Switch in AUTO." I o For multiposition control switches that have more than one position for a similar function, placement to the 'desired position should be specified; for example, "Place PIRE pump SELECTOR Switch to TEST NO. 2."
I Standard practices for observing for abnormal results need not be I prescribed within procedural steps. For example, observation of noise, I vibration, erratic flow, or discharge pressure need not be specified by I steps that start pumps. I I
o Alignment instructions should contain all the following: I I
- a. Each item requiring alignment is individually specified. (Do not I refer personnel to previous steps I I
- b. Each item is identified with a unique number or name. I I
QI 5-PR PSL-2 Writers Guide Rev. 0 Page 19 of 32'.
The position in which the item is to be placed is specified.
- d. The position in which the item is placed is verified.
4.9 PRINTED OPERATOR AIDS l When information is presented using graphs, charts, data sheets, tables, and j figures, these aids must be self~xplanatory, legible,,and readable under the expected conditions of use and within the reading precision of the operator.
I Data sheets should designate the frequency of use. If the action step must l be repeated every 15 minutes, the data sheet should contain enough spaces to I comply with the action.
l 4~9 1 Units of Measure I Units of measure on figures, tables, and attachments should be given for l numerical values that represent observed, measurement data, or calculated I results. A slant line should be used instead of "per"; examples: ft/sec, lbs/hr.
4.9.2 Titles and Headings Capitalization should be used for references to-tables and figures, titles of tables and figures within test material, and column headings within a table.
Examples: Refer to Pigure 201 for ~
. as shown in Table 201, Equipment Power Supplies the ~ ~ ~ ~
4.9.3 Pigure, Table, and Attachment Numbering Sequential arabic numbers should be assigned to figures, tables, and attachments in separate series. The sequence should correspond with the order of their reference in the text. The symbol "0" and abbreviation "No." are unnecessary and should not be used. The number alone suffices.
Examples: Pigure 1, Figure 2, etc.
Table 1, Table 2, etc.
Attachment 1, Attachment 2, etc.
Ql 5-PR PSL-2 Writers Guide Rev. 0.
Page 20 of 32 Page identification for attachments should consist of a block of information that identifies (I) procedure number, (2) abbreviated title, (3) attachment number, (4) page number, and (5) revision number. Page numbering of attachments should meet the requirements of Subsection 2.5.
Section numbering for attachments should be in accordance with Subsection 3.3.
- 5. MECHANICS OP STYLE 5.1 SPELLING Spelling should be consistent with modern usage. When a choice of spelling is offered by a dictionary, the fir'st spelling should be used.
I 5.2 HYPHENATION Hyphens are used between elements of a compound word when usage calls for it.
The following rules should be followed for hyphenation.
V When doubt exists, the compound aord should be restructured to avoid hyphenation.
o Hyphens should be used in the following circumstances:
- a. in compound numerals from twenty-one to ninety-nine; example: one hundred thirty-four
- b. in fractions; examples: one-half, two-thirds "Co in compounds with "self"; examples: self-contained, self-lubricated
- d. when the last letter of the first~ word is the same vowel as the first letter of the second word .as an alternative, two words may be used; example: firemscape or fire escape I
QI -PR PSL-Writers Guide Rev. 0 Page 21 of 32
- e. when misleading or awkward consonants would result by Joining the wor ds; example: bell-like l* to avoid confusion with another word; examples: remover to prevent I confusion with recover, pre~osition to avoid confusion with preposition
- g. when a letter is linked with a noun; examples: X-ray, O-ring, U-bolt, I-beam
- h. to separate chemical elements and their atomic weight; examples:
Uranium-235, U-235 5~3 PUNCTUATION Punctuation should be used only as necessary to aid reading and prevent misunderstanding. Word order should be selected to require a minimum of punctuation. When extensive punctuation is necessary for clarity, the sentence should be rewritten and possibly made into several sentences.
Punctuation should be in accordance with the following rules.
I 5.3.1 Brackets I Do not use brackets.
I 5 '.2 Colon t Use a colon to indicate that a list of items is to follow. For example, l Restore cooling flow as follows:
I l 5.3. 3 Comma
. t Use of many commas is a sign the instruction is too complex and needs to be I rewritten. Therefore, evaluate the number of commas to ensure the instruction I is not too complex.
I Use a comma after conditional phrases for clarity and ease of reading.
Example: WHEN level decreases to 60 inches, THEN start pump .
I"
1I QI 5-PR PSL-2 Writers Guide Rev. O Page 22 of 32 5.3 ' Parentheses Parentheses shall be used to indicate alternative items in a procedure, instruction, or equipment numbers. I l t 5.3.5 Period I a period at the end of complete sentences and for indicating the decimal l place in numbers.
l l 5~4 VOCABULARY I Words used in procedures should convey precise understanding to the trained person. The following rules apply.
I o Use simple words. Simple words are usually short words of few syllables. I l Simple words are generally common words. 'I l
o Use common usage if it makes the procedure easier to understand.
l, I I I I o Use words that are concrete rather than vague, specific rather than I l general, familiar rather than formal, precise rather than blanket. I I'se l
o Verbs with specific meaning should be used. Examples are listed in I
l I Table l. I I I l o Equipment status should be denoted as follows: I I I I a. Operable/operability These words mean that a system, subsystem, I train, component, or device is capable of performing its specified I function(s) and when all necessary attendant instrumentation, l controls, electrical power, cooling or'eal water, lubrication or I.
other auxiliary equipment that are required for the system, I subsystem, train, component or. device to perform its function(s) are I also capable of performing their related support function(s). I I I t I I
~'
QI -PR PSL-Writers Guide Rev. 0 Page '23 of 32 Operating This word means that a system, subsystem, train, component, or device is in operation and is performing its specified function(s). I I
Available This word means that a system, subsystem, train, I component, or device is operable and can be used as desired; I however,.it need not be operating. I II I
I I
I
'I I
I I
I I
I I
I I
I I
I I
I I
I I
I I
I
QI 5-PR PSL-2 Writers Guide Rev. 0 Page "24 of 32 Table I. Action Verbs Verb Appiication Allow To permit a stated condition to be achieved prior to proceeding, for example, "allow discharge pressure to stabilize" Check To perform a comparison with a procedural requirement "Check if SI can be terminated".
0 Close To change the physical position of a mechanical device so that it prevents physical access or flow or permits passage of electrical current, for example, "close valve V2530" Complete To accomplish specified procedural requirements, for example, "complete valve checkoff list 'A,'" "complete data report QA-l,"
"complete steps 7 through 9 of Section III" Decrease Do not use because of oral communication problems.
Establish To.make arrangements for a stated condition, for example, "establish communication with control room" Increase Do not use because of oral communication problems.
Inspect To measure, observe, or evaluate a feature or characteristic for comparison with specified limits;'method of. inspection should be included, for example, "visually inspect for leaks" Lower To decrease, as in setpoint, flow, pressure, etc.
Open To change the physical position of a mechanical device, such as valve or "door to the unobstructed position that permits access or flow, for example, "open valve Vlll4" s
QI 5-PR PSL-2 Writers Guide Rev. 0 Page 25 of 32 Table 1. Action Verbs (Continued)
Verb Application Raise To increase, as in setpoint, flow, pressure, etc.
Recor d To document specified condition or characteristic, for example, "record discharge pressure"
, Set To physically adjust to a specified value an adjustable feature, for example, "set diesel speed to . . .'rpm'"
I Start To originate motion of an electric or mechanical device directly or by remote control, for example, "start . . . pump" Stop To, terminate operation, for example, "stop ~ .. pump" Throttle To operate a valve in an intermediate position to obtain a certain flow rate, for example, "throttle valve V6550 to .
Trip To manually activate a semi-automatic feature,, for example, "trip breaker ~
I Vent To permit a gas or liquid confined under pressure to escape at a I vent, for example, "vent ~ . . pump" I Veri fy To observe an expected condition or characteristic, -for example, I "verify discharge pressure is stable" I
I
I ~ ~
~
Ql 5-PR PSL-2 Writers Guide Rev. 0 Page 26 of 32 5~5 NUMERICAL VALUES The use of numerical values should be consistent with the following rules:
I o Arabic numerals should be used.
) o For numbers less than unity, the decimal point should be preceded by a l zero; for example: 0.1.
I o The number of significant digits should be equal to the number of l significant digits available from the display and the reading precision l of the operator.
I o Acceptance values should be specified in such a way that addition and I subtraction by the user is avoided if .possible. This can generally be l done by stating acceptance values as limits. Examples: 510 F maximum; l 300 psig minimum; 580 to 600 F. For calibration points, statement of l the midpoint and its lower and upper limits for each data cell would accomplish the same purpose; for example, 10 milliamperes (9.5 to 10.5).
I Avoid using +.
j I o Engineering units should always*be specified for numerical values of variables. They should be the same as those used on the control 'rocess room displays, for example: psig instead of psi.
I I 5.6 ABBREVIATIONS, LETTER SYMBOLS, AND ACRONYMS l The use of abbreviations should be minimized because they may be confusing to I those who are not thoroughly familiar with them. Abbreviations may be used where necessary to save time and space, and when their meaning is
, I unquestionably clear to the intended reader. The full meaning of the I abbreviation, other than the abbreviations listed in AP0010137, should be J fully written before the first use of the abbreviation and whenever in doubt.
I Consistency should be maintained throughout the procedure.
l I
QI 5-PR PSL-2 Writers Guide Rev ~ 0 Page 27 of 32 Capitalization of abbreviations should be uniform. If the abbreviation is I comprised of lowercase letters, it should appear in lowercase in a title or l heading. The period should be omitted in abbreviations except in cases where l the omission would result in confusion.
I Letter symbols may be used to represent operations, quantities, elements, I relations, and qualities.
I I An acronym is a type of symbol formed by the initial letter or letters of t each of the successive parts of ma)or parts of a compound term. Acronyms may I be used if they are defined or commonly used.
l I
l l
l I
I I 6~ TYPING FORMAT I
l 6 1 GENERAL TYPING INSTRUCTIONS I For emergency operating procedures, the following general requirements are to J
be followed.
l 1
o Paper size should be 8-1/2 X 11 inches.
I t o Procedures should be typed on a word processor.
t l
'o 'restige Elite 12, 82052 WP printwheel should'be used.
6 2 PAGE ARRANGEMENT l
o Page margins are specified by the printed borders. Two type spaces are to be maintained between the text and borders.
1 I
e QI 5-PR PSL-2 Writers Guide Rev. 0 Page 28 of 32 o Page identification information (refer to Subsection 2.4) will be one line space below the top page printed border and one line space to the left of the right printed border.
The 8-1/2 inch edges shall constitute top and bottom of pages and text.
Tables and figures shall be readable with the page so arranged. Rotation of printed matter should be avoided for emergency operating procedures.
Refer to Subsection 6.5 if rotation is absolutely necessary.
6.3 HEADING AND TEXT ARRANGEMENT Block style, as illustrated in Figure 2, shall be used. First-level section headings shall'be in full capitals, with an underscore; second-level section headings shall be in'ull capitals without an underscore; and third-level section headings shall be placed in initial capitals without an underscore (refer to Subsection 3.3 for its numbering).
Section numbers shall begin two spaces from the left>>hand printed border.
o Three line spaces shall be allowed between headings and respective text ~
o Three line spaces shall be allowed between paragraphs.
o Text shall be typed using one-and-a-half line spacing.
6 ' BREAKING OF WORDS Breaking of words shall be avoided to facilitate operator reading.
6 ' ROTATION OF PAGES If pages need to be rotated; these rulesshall be followed:
o The top of the page with rotated print is the normal left-hand edge.
o The page margins do not rotate.
QI 5-PR PSL-2 Writers Guide Rev. 0 Page 29 of 32 o Page identification and numbering will not be rotated.
I 6.6 PRINTED OPERATOR AIDS Figures include graphs, drawings, diagrams, and illustrations. The following rules are established..
I o The figure number and its title are placed three line spaces above the I figure field (refer to Subsection 4.9).
I o The figure number and title should be of Prestige Elite 12, 82052 WP type.
I o The figure field must not violate specified page margins.
I o The figure field should be of sufficient size to offer good readability I
o The essential message should be clear; simple presentations are preferred.
I o Grid lines of graphs should be at least 1/8-inch apart; numbered grid I lines should be bolder than unnumbered grid lines.
I o Labeling of items within the figure should be accompanied by arrows I pointing to the item.
I o The items within the figure should be oriented naturally insofar as I possible. For example, height on a graph should be along the vertical I axis I
I o In general, items within the figure should be labeled. Typed labels I' should use Prestige Elite 12, 82052 WP printwheel. Handwritten labels should be printed, using all capitals, with letters and numbers at least I I/8-inch high.
II I
o All lines in figures should be reproducible.
QI 5-PR PSL-2 Writers Guide Rev. 0 Page 30 of 32 Tables should be typed using the following rules.
o Type style and size should be the same as that for the rest of the procedure.
o The table number and title should be located above the table field and three line spaces below preceding text.
o A heading should be entered for each column and centered within the column; the first letter of words in the column headings should be capitalize d.
o Horizontal lines should be placed above and below the column headings; vertical lines, while desirable, are not necessary or required.
o Tabular headings should be aligned as follows:
- a. horizontally by related entries
- b. vertically by decimal point for numerical entries
- c. vertically by first letter for word entries; however, run-over
. lines should be indented three spaces 0 Double spacing between horizontal entries suffices to segregate such entries, although horizontal lines may also be used if desired. If used, double horizontal lines should be used above and below the column headings.
There should not be a vacant cell in the table. If no entry is necessary, "N.A." should be entered to indicate not applicable.
QI 5-PR PSL-2 Writers Guide Rev ~ 0 Page 31 of 32 6~7 CAUTIONS AND NOTES All notes and cautions should be distinguishable from the rest of the text by using the following format. l I
k o The applicable heading "NOTE" and "CAUTION" should be capitalized, I centered, and placed three line spaces below the preceding text.
I o The text of the note or caution should be block format, line-and-a-half spaced. The caution text should be indented five spaces from the left- I hand printed margin and begun onemndm-half line spaces below the l heading. The text for notes should begin 10 spaces from the column I dividing line. I l
o A caution statement should not continue to a second page, unless unusually )
lengthy. I I
The right-hand margin of the text of the note or caution should be five I spaces to the left of the right-hand printed margin. I I
CAUTIONS shall be further highlighted by a line of asterisks l one-and-a-half spaces above the-heading and one-and-a-.half spaces below the last line of the text. I I
o Examples are presented in Subsection 4.3. I I
6.8 USE OP FOLDOUT PAGES I When used, a foldout page is treated as a single page. It should follow the 1 same format as a standard page except the width is different. The page I should be folded so that a small margin exists between the fold and the I right-hand edge of standard pages. This will reduce wear of the fold. l I
6.9 USE OP OVERSIZED PAGES I Oversize pages should not be used. They should be reorganized or reduced to t a standard page. If this cannot be done, a foldout page should be used. I I
f QZ 5-PR PSL-2 Writers Guide Rev. 0 1
Page 32 of 32 6 '0 USE OF REDUCED PAGES Reduced pages should be avoided whenever possible. Final size of reduced pages should be standard page size. Reduced pages should be readable.
l I 7~ REPRODUCTION Reproduction will be done on a standard copier, single-sided copy only.
I I
l I
t l
I I
j I
I I . I I I l l I I I
I I
I I l I I l I I
I t
I" I
4' l
EOP Abbreviated Title Rev ~
Page of FLORIDA POWER 6 LIGHT COMPANY ST. LUCIE PLANT UNIT NO.
EMERGENCY OPERATING PROCEDURE (TITLE)
Reviewed By Approved By Date
I 1/ 2ss It 1 I 1 )
TITLE - Reactivity Control 1-EOP-Ol I I 2.5 I I.I Rev e 1 I I 4 t 12 IENTRY CONDITIONS TLOP I I 5~5 I 11. Reactor Power 100K Page 1 of 20 I I 7 I 12. Reactor Power cannot be determined t I 8.5 I I I I 10 I 13 I OPERATOR ACTIONS I I 11.5 I I I I I 13 t I I t I 14.5 I I I I I 16 I I Instructions Contingency Actions I I 17.5 I 11. ITrip Reactor I 11. IDrive Rods t I 19 I Ia. Depress switch I Ia. Select rod I I 20.5 I I I I' I I I 22 t (2 spaces) I (2 spaces) I I 23 ~ 5 I (5 spaces) (5 spaces)
I 25 I (9 spaces) I I I I I 26 ' I I I I t I I 28 I I I I I I I I I 29.5 I I I I I I 11/2" I 31 I I I I I I I 32.5 I I I I I I I I 34 I' 35 spaces)~ I I I 35.5 I I I I I I I 37 I I I I I I I I 38.5 I I I I t I I t 40 I I I I I I I 41. 5 t I I I I I I I 43 t I I I I I I t 44.5 I I I I I I I I 46 I I t I I I I I 47.5 t I I I I I t t 49 I I I I I I I I 50. 5 t I I I I I I I 52 t I I I I I I I 53.5 I' I
I I
k c ga 7"
,r