ML20094F319

From kanterella
Jump to navigation Jump to search
Rev 0 to Station Administrative Procedure SAP-207, Development of Emergency Operating Procedure
ML20094F319
Person / Time
Site: Summer South Carolina Electric & Gas Company icon.png
Issue date: 04/02/1984
From:
SOUTH CAROLINA ELECTRIC & GAS CO.
To:
Shared Package
ML20094F305 List:
References
RTR-NUREG-0737, RTR-NUREG-737 GL-82-33, SAP-207, NUDOCS 8408100012
Download: ML20094F319 (77)


Text

l ENCLOSURE IIL SOUTH CAROLINA ELECTRIC AND GAS COMPANY

- - 004-h0 VIRGIL C. SUMMER NUCLEAR STATION NUCLEAR OPERATIONS STATION ADMINISTRATIVE PROCEDURE SAP-207 DEVELOPMENT OF EMERGENCY OPERATING PROCEDURE REVISION 0 APRIL 2, 1984 20R INIORMATION 01Yj SAPETY REtATED (2 W '

DISCIPLINE SUPERVISOR ffl'f)V-

' Date l APPROVAL AUTHORITY Date l

DATE ISSUED RECORD OF CHANGES l CHANGE TYPE DATE DATE CHANGE TYPE DATE lDATE NO. CHANGE APPROVED CANCELLED NO. CHANGE APPROVED CANCELLED 1

I h0khkO F

t

, SAP-207 PAGE i REVISION 0 4/2/84 LIST OF EFFECTIVE PAGES PAGE REVISION 1

0 11 0 111 0 1 0 2 0 3 0 4 0 5 0 6 0 7 0 8 0 9 0 10 0 11 0

12. O
13 0 14 0 15 0 l ATTACHMENTS Attachment 1 0 I

Attachment 2 0 Attachment 3 0 Attachment 4 0 Attachment I O i Attachment II O Attachment III O Attachment IV 0 Attachment V 0 Attachment VI O

! Attachment-VII 0 Attachment VIII O r - , ,__.m._,_,

Y- w - -r+- - --m+- _w-. - - .,.-y-_.-

SAP-207 PAGE 11 REVISION 0 4/2/84 TABLE OF CONTENTS S ECTION ~ PAGE 1.0 PURPOSE 1 2.0 SCOPE 1 30 REFERENCES 1 4.0 DEFINITIONS 2 50 RESPONSIBILITIES 2 6.0 TECHNICAL GUIDELINES 3 7.0 EMERGENCY OPERATING PROCEDURE WRITER'S GUIDE 5 8.0 E0P PREPARATION 5 90 E0P VERIFICATION 6 10.0 E0P VALIDATION 8 11.0 E0P TRAINING 14 12.0 E0P IMPLEMENTATION 14 13 0 E0P REVISIONS 14 14.0 RECORDS 15 l

l ATTACHMENTS j Attachment 1 - Cover Sheet Format l

l Attachment 2 - Table of Contents Format i

Attachment 3 - Page Format i

Attachment 4 - Constrained Language List i

1

r i- ~

, +

, SAP-207 PAGE iii REVISION 0 4/2/84 TABLE OF CONTENTS ATTACHMENTS

-Attachment I~ -

Intr'oduction Attachment II - E0P Step Documentation Attachment III - E0P Development Checklist Attachment IV -

E0P Technical Review Checklist Attachment V - Technical Review Discrepancy Attachment VI -

E0P Validation Form

. Attachment VII - Validation Discrepancy Form Attachment VIII- Simulator Scenario Form

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

-,y_ -

e- . , ,w, , , - p -,- ,--- _ . _ _ _ _ _ .

, SAPi207 REVISION O

  • ~ 4/2/84 1.0 PUR POSE 1.1 This procedure provides guidance for the development, verifica tion , ' validation , training and implementation of Emergency Operating Procedures (EOP). This procedure has been developed in response to NRC Generic letter 82-33
2. 0 SCOPE This procedure describes:

2.1 Use of source documents for the development of plant specific Technical Guidelines which are used as.a bases for the E0P's.

2. 2 Use of an E0P Writer's Guide to ensure E0P's are formated and worded in a consistant manner, applying proper hunan fac tor guidelines.
2. 3 Method of performing an E0P verification to confirm written correctness and that the Technical Guideline information has been properly incorporated into the procedures.
2. 4 Method of performing an E0P validation to confirm that the actions specified in the procedure can be performed by the operator to manage the emergency conditions effectively.

25 Requirements for the Operator training program in regards to Bnergency Operating Procedures .

2. 6 Me thod of implementing E0P and subsequent revisions.

30 R EF ERENC ES 31 Westinghouse Owners Group Bnergency Response Guidelines, Revision 1, with Bac kground L1fo rma tion.

32 NRC Generic Le tter 82-33 33 INPO 82-016, Emergency Operating Procedures Implementation Guideline (Preliminary) .

34 INPO 82-017, Emergency Operating Procedures Writing Guideline (Preliminary) .

PAGE 1 0F 15

, SA P-2 07 .

, REVISION 0 s~ 4/2/84 35 INPO 83-004, Dnergency Operating Procedures Verification Guidelices (Preliminary) .

36 INPO 83-00 6, anergency operating Procedures Validation Guidelines (Preliminary) .

37 INPO 83-00 7, Bnergency Operating Procedures Generation Package Guideline (Preliminary) .

4.0 DEPINITIONS 4.1 Verification - E0P verification is the evaluation performed to confirm the written correctness of the procedur'e and to ensure that applicable generic and plant specific technical information has been incorporated properly. This evaluation also checks that the human factors aspects presented in the writers guide have been applied.

4. 2 Validation - E0P validation is the evalua tion performed to determine that the actions specified in the procedure can be performed by the operator to manage the emergency condition effec tively. The methodology for E0P validation utilizes present, available methods at the V. C. Summer Nuclear Station while recognizing and allowing for future improvements. It will validate that part of the E0P not covered by any technical validation of generic technic al guid elines .
5. 0 R ES PONSIBILITIES 51 The Manager, Operations is responsible fo r the development of E0P's in conformance with this procedure.

52 The Manager, Technical Services, is responsible for development of plant specific setpoints as required for E0P preparation and which are beyond the scope of source doc uments such as Technical Specifications and the Westinghouse PLS document.

53 The Manager, Nuclear Operations Education and Training Group is responsible for:

531 Developnent and implementation of the Operator E0P Training Program.

PAGE 2 0F 15

SAP-207

'.* REVISION 0

.- 4/2/84

5. 3. 2 Providing operator feedback to Nuclear Operations Group .in regards to procedure inadequacies revealed during the operator E0P training.

5 3.3 Assisting in the E0P Validation Program whenever the plant simulator is used by:

a. Developing test scenarios which adequately challenge the E0P's.
b. Providing simulator instructors.

6.0 TECHNICAL GUIDELINES 6.1 The following docunents constitute the V. C. Summer Nuclear Station Baergency Operating Procedure Technical Guidelines:

6.1.1 Westinghouse Owners Group Emergency Response Guideline s (ERG ) Revision 1, with Backg round In fo rmation.

6.1. 2 V. C. Summer Nuclear Station Final Safety knalysis Report (FSAR).

6.1. 3 V. C. Summer Nuclear Station Technical Specifications.

6.1. 4 V. C. Summer Nuclear Station Evaluation Report (SER) , N UREG 0 717.

6.1. 5 V. C. Summer Nuclear Station Precautions, Ltmitations and Setpoint (PLS) as supplied by Westinghouse Elec tric Co rporation.

6.1. 6 V. C. Sumner Nuclear Station System Descriptions as supplied by Gilbert Associates Inc.

6.1.7 We stinghouse Letter CGE-83-822. - This provides plant specific values for adverse instrument conditions to be used in the-EOP's.

6.1. 8 V. C. Summer Nuclear Station plant drawings and equipment manuals.

PAGE 3 0F 15

, SAP-207 -

- REVISION 0
  • 4/2/84
6. 2 The ERGS constitute .the primary Technical Guidelines for development of the plant specific E0P's. Taey provide:

6.2.1 Generic Bnergency Operating Procedures , indicating:

A. Procedure breakdowns by type of events or

. conditions to be mitigated.

B. Se quence of procedural steps .

6.2.2 Bac kground doc umentation to explain the procedure s te ps .

6. 3 The Tbchnical Guideline Supplements, Item 6.1. 2 through 6.1. 7, provide plant specific details required .to adapt the ERGS to plant specific E0P's.
6. 4 Use of the Technical Guidelines .

6.4.1 The ERG 3 shall provide the nucleus of the plant specific Technical Guidelines for E0P development.

Generally the E0P writer will follow the ERGS s te p-by- s te p .

6.4.2 Deviations from the ERGS due to plan t specific restraints will be justified on Attachment II, EO P Step Documentation.

6.4 3 Us e o f no n-ERG Te c hnic al Gu id elines , It ems 6.1. 2 through 6.1. 7, will be doc umented on Attachment II, E0P Step Docunentation.

6.4.4 Format and word changes to comply with the E0P Writers Guide does not constitute a deviation from the Technical Guidelines .

I 6.4.5 Recognizing that the ERGS are a generic procedure set, the Manager, Operations Group, has the authority to modify the procedures by simplifing or consolidating to satisf y plant specific needs or human fac tor considerations provided the basic intent of the ERGS are no t jeopardized. Such modifications will be docunented.

PAGE 4 0F 15

. S A P-2 07 -

, REVISION 0 4/2/84 70 EMERGENCY OPERATING PROCEDURE WHITER 'S GUIDE f.1 Emergency Operating procedures shall be written ~1n compliance with the Bnergency Operating Procedures Writers Guid e, At tachment I.

8. 0 E0P PREPARATION 8.1 E0P writers will familiarize themselves with the EOP Writers Guide and the Technical Guidelines for the procedures they have been assigned to develop.
8. 2 Using the format contained in the Writers Guide., the writer prepares a 1st draft plant specific E0P based on the Tec hnic al Guidelines .

83 Fo r each step in the.EOP and E0P Step Docunentation Fo rm, Attac hment II, will be comple ted. This form indicates :

8.3 1 EOP Number and Title.

8.3 2 E0 P Ste p n umb er and ac t ual wo rd ing.

8.3 3 The related ERG Number, Step Number and wording.

8.3.4 Justification for any differences between the E0P and ERG step, if any.

8.3 5 The source of any numerical values used in the E0P s tep .

8. 4 The d raft E0P will be submitted for typing and review per SA P-13 9, Procedure Develo pment, Review, Approval and Co ntrol .
8. 5 Docwnents generated during the writing process include:

8.5.1 Pro po sed E0 P in draf t form.

8 5.2 Procedure Develognent form.

8.5 3 E0P Step Doc umentation.

PAGE 5 0F 15

~*

  • SAP' 207 REVISION 0 e- 4/2/84 90 E0P VERIFICATION 91 The originator will proofread the typed draft of the E0P )

for:

91.1 Correctness - Does the procedure agree with the

- submitted handwritten version?

91.2 Fo rmat - Does the procedure comply with the format specified in the Writer's Guid e?

913 Spelling Errors .

91.4 Numbering - Are the procedure steps pr.operly numbered in sequence?

91.5 Spac ing - Are the procedure steps properly s pac ed? Are the lef t and right hand columns properly aligned?

92 Corrections will be noted in red on the typed version of the procedure as they are identified. Unless the corrections are extensive, tha procedure does not require retyping prior to Technical Review.

9. 3 The originator will complete E0P Development Checklist, Attachment III, and submit it and the marked up typed version of the procedure to the Supervisor of Operations .

94 The Supervisor of Operations will select a qualified individual to perform a technical review of the procedure.

No rmally this will be an STA or other qualified engineer.

95 To perform a Technical Review the following documents must be available:

951 The proposed EOP, a s m ar ked up b y t he o rigin ato r.

95.2 The applicable ERG.

953 The applicable ERG Backg round In fo nnatio n.

9 5.4 The E0P Step Doc umentation forms .

9. 6 The Tbchnical Reviewer will review the procedure for those items specified on Attachment IV, EOP Technical Review Chec klist .

PAGE 6 0F 15

. S A P-2 07 -

REVISION 0 4/2/84 97 Comments can be noted in one of two ways:

971 Making minor corrections on the procedure being r evie wed.

9 7.2 Completing At tachment V, Te c hnic al Review Discrepancy Form, when the discrepancy requires re-writing significant portions of the procedure.

9. 8 The Technical Reviewer will review the E0P Step Docunentation forms for the following:

9.8.1 E0P/ ERG step differences are adequately justified and does not have an adverse safety significance.

9.8.2 The differences does not alter the intent of the procedure as described in the ERG background in fo rma tion.

983 The proper source of numerical values was identified.

9 8.4 The value used in the procedure step agrees with the sourc e value.

9 8.5 Disc repancies will be docunented on Attachment V.

99 The Technical Reviewer will return the procedure package to the Supervisor of Operations.

910 The Supervisor of Operations shall ensure:

9.10.1 Comments generated during the verification process are resolved.

9 10.2 Procedures are re-typed with comments incorporated prics to the validation phase.

9 11 Documents generated during the verification process include :

9 11.1 E0P Development Checklists.

9.11.2 E0 P Technical Review Checklists .

9113 Technical Review Disc repancy.

PAGE 7 0F 15

, S A P-2 07

, REVISION 0 4/2/84 10.0 E0P VALIDATION 10.1 The ERG Validation Program, included as a part of the Technical Guidelines , constitute the basic validation that the ERG based E0Ps will manage the emergency conditions e ff ec tively .

10.2 The E0Ps to be validated use instrunents and controls currently installed in the plant ; therefore , thi s validation is independent of the Control Room Design Review validation to ensure the availability and adequacy of instrumentation and controls to meet the task analysis identified 7eeds .

10 3 Plant specific E0Ps may be validated by one or. more of the following methods :

10 3 1 Table-Top Me thod - A validation method where by a qualified person (s) reviews the procedure and based on their knowledge of plant systems determines the adequacy of the procedure to manage the emergency conditions effec tively. Tais method is effective only for minor revisions to previously validated procedures.

1032 Walk-Through Method - A validation method whereby plant operators conduct a step-by-step enactment of their actions without actual control manipulation. This method is effec tive in identifing confusing proc edure steps ,

compatability of instruments and controls to the procedure requirements , traffic flow required by the operators to complete the procedures in the required sequence.

10.3 3 Simulator Me thod - A validation method whereby Control Room operators perform the actual control f unctions on a simulator during a simulated emergency condition. This method is the most effective method of challenging and validating the Control Room portion of EOPs provided the operators have received adequate familiarization of the procedures to be validated.

PAGE S OF 15

S AP-2 07

'. REVISION 0

', 4/2/84 10.4 The Supervisor of Operations will determine the method (s) of validation to be used. This determination will be based on the magnitude of the change or revision being made to the procedures. Selec tion of the validation method will be documented on Attachment VI, E0P Validation Re quir ements .

10.5 Table Tbp Validations .

10.5 1 The Supervisor of Operations will assign an SRO licensed individual to perform the validation.

10.5 2 This validation shall consist of an . independant verification of the correctness and adequacy of the procedure as desc ribed in Section 9 0.

1053 The validation will be documented on Attachment IV, E0P Technical Review Checklist.

10.6 Walk Through Validations .

10.6.1 The Supervisor of Operations will assign a qualified reviewer. This may be a Shif t Su pe rv iso r , Sh if t Te c hn ic al Ad v iso r , o r him sel f .

10.6.2 The designated reviewer will:

A. Review and familiarize himself with Section 3 of IN PO 83-00 6, Dnergency Operating Procedures Validation Guideline.

B. Review-the scope of the validation designated by the Supervisor of Operations.

C. Review the procedure and develop scenarios to support the scope of validation.

NOTE: This scenario may be as sDnple as making marginal notes on a working copy of the draft procedure to verify alternative actions and branching.

D. Selec t operators to perform the walk-through.

This should be coordinated with the Supervisor of Operations to ensure operator .

av ail ability.

PAGE 9 OF 15

S AP-2 07 -

! REVISION 0 4/2/84 l

E. Select the location for the walk-through, l either the Main . control Room or simulator for i Control Room ac tivities .

10.6.3 Validation process:

A. Th e r ev ie we r will tal k t he . o pe r ato rs t hr o ug h the procedure, step by step.

B. The operator will:

1) Go to the referenced instrument or control.
2) Verify the nomenclature is correct.
3) Verif y referenced values can be monito red .
4) Verify the control ac tion can be perfo rmed as stated in the procedure.
5) No tify the reviewer of any disc repancies or step omissions which would preclude taking the required step.

C. The reviewer will:

1) Observe the operators performing the step.
2) Observe movements of the operators around the Control Room to ensure smooth traffic patterns and lack of c rowding.
3) Note parts of the procedure that can be accomplished concurrently and parts that must be accomplished in sequence. Ens ure sequencial steps are listed in the proper o rd er .
4) Record observations and operator comments.

PAGE 10 OF 15

. S A P-2 07

', REVISION 0 4/2/84 D. Perform a second walk-through of the p rocedure. During this walk-through the reviewer provides copies of the procedures to the operators and only establishes various conditions to be reacted to. During this walk-through the reviewer will observe:

1) Can the operators easily select the proper procedure to implement for the co nditions .
2) Can the operators progress through the procedures and comple te the . alternatives and branching without confusion..

E. The reviewed will record discrepancies by:

1) Preparing Attachment VII, Validation Discrepancy Form 9E
2) Making corrections on the review copy of the procedure for typographical ereces.

10 7 Simulator Validations .

1071 The Supervisor of Operations will coordinate with the Nuclear Operations Education & Training Group

.to perform simulator validations. This coordination should include:

A. Simulator availability.

B. Selection of operators to perform the

-v alid atio n.

C. Training or familiarization the o perators will require to perform the validation.

D. The scope of validation required or recommended scenarios to use.

10. 7. 2 - The Supervisor of Operations will assign an evaluator to control and supervise the simulator valid atio n.

PAGE 11 OF 15

i S A P-2 07 .

REVISION 0

', 4/2/84 1073 Nuclear Operations Education & Training will:

A. Provide instructor personnel to assist in the validation process. They will:

B. Familiarize themselves with the procedures to be validated and the scope of validation required by the Supervisor of Operations.

C. Provide adequate classroom instruction to prepare the designated operators for the validation of the procedures. This should includ e:

1) Background on the purpose and . intent of the proc edures .
2) Familiarization with the general content of the procedures.
3) Instruc tion' on the validation process i .e .

to perform the procedures exactly as written. The only deviations allowed will be because of procedure inadequacies that preclude doing the procedure step.

D. Prepare Attachment VIII, Simulator Scenario Fo rm, for all Simulator scenarios to be used during the validation process.

1074 The validation process.

A. The designated operators will be briefed as de scribed in 10 7 3. C.

B. Sufficient observers will be assigned to verif y the movements and actions of the ope ra to rs . Uney will have copies of the procedures and scenarios to be used.

C. If available TV monitors should be used to record the actions of the operators for later use during the debriefing.

D. Using the developed simulator scenarios the operators will be subj ec ted to plant conditions which require implementing the EO Ps .

PAGE 12 0F 15

SA P-2 07

  • REVISION 0 4/2/84 E. The observers will note the operators responses as desc ribed in step 10. 6. 4.

F. All deviations , either omissions or additional ac tions will be recorded on Attachment VII, Validation Discrepancy Form.

G. At the completion of the simulator exercise the operators will be debriefed:

1) All discrepancies noted by the observers will b e discussed.
2) All comments by the operators .as to problem areas or confusing steps will be d isc us sed.
3) If TV monitors were used, they will be replayed to determine if any other problem areas were overlooked.

H. The scenarios should be completed a sufficient number of tbnes to determine if discrepancies and problem areas are caused by procedure inadequacies or non-compliance with the procedures.

G. The Evaluator will determine if the procedures were successful in managing the emergency conditions effectively.

10.8 The validation reviewers will submit all comments and documentation to the Supervisor of Operations for resolution.

10 9 The Supervisor of Operations will submit the draft procedures with all comments resolved for final typing.

10.10 Docunents generated during the validation process

- include :

10.10.1 EOP Validation Fo rms.

10.10.2 Valida tion ' Discrepancy Forms .

10.10.3 simulator sc enario Fo rms.

PAGE 13 0F 15

  • a n

+ , SA P-2 07 .

'. REVISION 0 4/2/84 11.0 E0P TRAINING 11.l' The Nuclear Operations Education & Training Group is responsible for Operator Training in accordance~ with the Nuclear Education & Training Group Manual and approved Nuclear Training Center Instructions (NTOIs) .

11.2 Operator E0P training will contain the following elements :

11.2.1 Classroom training:

A. Background and purpose oE the E0Ps .

B. Ste p-b y-s te p r evie w o f the E0 Eb .

11.2.2 Simulator Training.

12.0 'EO P IMPLB4ENTATION 12.1 E0Ps will be issued and implemented as follows :

12.1.1 Major revisions will be issued upon completion of the E0P Training Program. Whenever possible this should coincide with major outages so the training and transition can be completed while. the plant is in cold shutdown.

12.1.2 Minor individual E0P revisions will be issued upon completion of the review and approval process.

Operating shifts will be briefed on the nature and scope of the revision prior to ass uming operator d ut ie s .

12.1 3 The Supervisor of Operations will maintain a copy of the Technical Guidelines for the E0Ps in the vacinity of the Oontrol Room for operato rs reference.

13 0 EOP REVISIONS 13 1 EO Ps will be revised for the following reasons :

13 1.1 Changes to the Technical Guidelines identified by-the WOG-ERG maintenance program.

PAGE 14 OF 15

. S A P-2 07

'. REVISION 0 4/2/84 13 1.2 Inadequacies observed during procedure implementation during actual plant emergencies.

~

13.13 Modifications to the plant such as new instrumentation and controls installed as a result of the Detailed Control Room Design Review.

13 2 E0P revisions will undergo the same review process as the basic procedures received.

14.0 R ECOR DS 14.1 The E0P Generation Package will be maintained in accordance with the Q. A. Records Accumulation and Retention Chart for plant procedures .

14.2 Each E0P Generation Package will contain as a minimum:

14.2.1 Procedure Develo pment Fo rms , PDF-A & B.

14.2.2 Final Approved Master 03py of the procedure.

14.2 3 EO P Step Doc umentation.

14.2.4 E0P Development Checklists.

14.2 5 E0P Technical Revie.< Chec klist .

14.2.6- Te c hn ic al Re v ie w Di sc re panc y Shee ts .

14.2.7 E0P Validation Form.

14.2.8 Validation Disc repancy Fo rms.

14.2 9 Simulator Scenario Forms .

PAGE 15 0F 15

- SA P-2'07 ATTACHME?fl' I

  • REVISION 0 l

V. C. SUMMER NUCLEAR STATION WRITER 'S GUIDE FOR EMERGENCY OPERATING PROCEDURES 1

n l SA P-2 07 l PAGE 1 l REVISION 0 4/2/84 TABLE OF CONTENTS SECTIO N PAGE

l. 0 INTRODUCTION. . . . . . . . . . . . . . . .. 1 1.1 PUR POSE. . . . . . . . . . . . . . . .. 1
1. 2 SCOPE. . . . . . . . . . . . . . . . .. 1
2. 0 E0P ORGANIZ ATION AND IDENTIFIC ATION. . . . . .. 1 2.1 GENERAL ORGANIZ ATION OF EOPS. . . . . . 1 2.1.1 C ONDITIONS. . . . . . . . . . .. 2
2. 2 COVER SEEET. . . . . . . . . . . . . .. 2 23 PROCEDURE TITLE. . . . . . . . . . . .. 2
2. 4 PROCEDURE DESIGNATION AND NUMBERING. .. 2 25 REVISION DESIGNATION AND NUMBERING. . .. 2 30 FORMAT. . . . . . . . . . . . . . . . . . .. 3 31 TABLE OF CONTENTS. . . . . . . . . . .. 3
3. 2 PAGE IDENTIFICATION AND NUMBERING. . .. 3 33 PAGE FORMAT. . . . . . . . . . . . . .. 3 34 PROCEDURE ORGANIZ ATION. . . . . . . ... 4 35 C ON DITIONS . . . . . . . . . . . . . ... 4
3. 6 NUMBERING WITHIN PROCEDURES. . . . . .. 5 37 IN-TEXT REVISION IDENTIFICATION. . . .. 5 38 ATTACHMENT ORGANIZ ATION. . . . . . . .. 6 1

t 1

4 O

n

.' j SA P-2 07 PAGE 11 l REVISION 0 4/2/84 TABLE OF CONTENTS (continued)

SECTION PAGE

4. 0 WRITING ACTION AND A LTERNATIVE ACTION STEPS. . 7 4.1 STEP LENGTH AND CONTENT. . . . . . . .. 7 4.1.1 ACTION COLUMN. . . . . . . . .. 9 4.1. 2 ALTERNATIVE ACTION COLUMN . .... 9
4. 2 USE OF LOGIC TERMS. . . . . . . . . .. 10 43 USE OF CAUTIONARY INFORMATION AND NOTES. 11
4. 4 C ALCULATIONS . . . . . . . . . . . . .. 13 45 USE OF UNDERLINING . . . . . . . . ... 13
4. 6 REFERENCING AND BRANCHING TO OTHER PROCEDURES OR STEPS. . . . . . . . ... 13 47 COMPONENT IDENTIFIC ATION. . . . . .. .. 14
4. 8 LEVEL OF DETAIL. . . . . . . . . . ... 15 49 PRINTED OPERATOR AIDS. . . . . . . . . . 17 491 UNITS OF MEASURE. . . . . . . . . 17 492 TITLES AND HEADINGS . . . . . .. 17 493 FIGURE, TAB LE , AND ATTACHMENT NUMBERING. . . . . . . . . . . .. 17 50 MECHANICS OF STYLE. . . . . . . . . . . . ... 18 51 S PELLING. . . . . . . . . . . . . . . .. 18 52 PUNCTUATION. . . . . . . . . . . . . . .. 18 52.1 B RAC KETS. . . . . . . . . . . ... 18 1

i

I SA P-2 07 l i PAGE 111 REVISION 0 4/2/84 TABLE OF CONTENTS (continued)

SECTION PAGE 5 2.2 C OLON. . . . . . . . . . . . . . . 18 5 2.3 C OMM A. . . . . . . . . . . . . . . 18

5. 2. 4 P A RENTHESES. . . . . . . . . . . 18

! 5.2.5 PER IO D. . . . . . . . . . . . . . 19 53 C APITA LIZ ATION. . . . . . . . . . . . . 19 54 HYPHENATION. . . . . . . . . . . . . . . 19 55 VOCABULARY. . . . . . . . . . . . . . . 20

5. 6 SENTENCE STRUCTURE . . . . . . . . . . . 21 57 N UM ERIC A L VA LUES. . . . . . . . . . . . 21 58 ABB REVI ATIONS, LETTER SUMBOLS, AND ACRON YM S. . . . . . . . . . . . . . . . 22
6. 0 TYPING FORM AT. . . . - . . . . . . . . . . . . 23 6.1 GENERAL REQUIREMENTS. . . . . . . . . . 23 6.1.1 FONT. . . . . . . . . . . . . . . 23 6.1. 2 M ARGINS. . . . . . . . . . . . . 23
6. 2 COVER SHEET. . . . . . . . . . . . . . . . 23 63 TABLE OF CONTENTS . . . . . . . . . . . . 24
6. 4 PROCEDURE BODY . . . . . . . . . . . . . . 25 6.4.1 PAGE IDENTIFIC ATION . . . . . . . . 25 6.4.2 HEA DINGS. . . . . . . . . . . . . . 26 6.4 3 S PAC ING. . . . . . . . . . . . . . 26 i l

. i

'. l SA P-2 07 '

)

PAGE iv I REVISION 0 l

4/2/84 TABLE OF CONTENTS (continued) 1 SECTION PAGE 6.4.4 NUMBERING PROCEDURE STEPS. . . . . 27 6.4 5 BREAKING PROCEDURE STEPS AND BREAKING WORDS. . . . . . . . .. 27 6.4.6 TAB SETS. . . . . . . . . . . .. 27 6.4.7 C AUTIONS . . . . . . . . . . .. 28 6.4.8 NOTES. . . . . . . . . . . . .. 29 6.4 9 FINIS HING. . . . . . . . . .. . 30

6. 4.10 C APITA LIZ ATION. . . . . . . . .. 30
6. 4.11 PLACEKEEPING AIDS. . . . . . .. 31
6. 5 ROTATION OF PAGES. . . . . . . . . . .. 31
6. 6 PRINTED OPERATOR AIDS. . . . . . . . .. 32 6.6.1 FIGURES. . . . . . . . . . . .. 32 6.6.2 TAB LES. . . . . . . . . . . . .. 33
6. 7 ATTACHMENTS. . . . . . . . . . . . . .. 33
6. 8 USE OF FOLDOUT PAGES . . . . . . . . .. . 34
6. 9 USE OF OVERSIZED PAGES. . . . . . . . .. 34 6.10 USE OF REDUCED PAGES . . . . . . . . .. . 34 70 R EPRODUCTION. . . . . . . . . . . . . . . .. . 34 ATTACHMENT 1 - COVER SHEET FORMAT ATTACHMENT 2 - TABLE OF CONTENTS FORMAT ATTAC HMENT 3 - P A GE F ORM AT ATTACHMENT 4 - CONSTRAINED LANGUAGE LIST I

. SAP-207 ATTACHMENT I REVISION 0

1. 0 INTRODUCTION 1.1 PUR POSE This docunent provides administrative and technical guidance on the preparation of Bnergency Operating Procedures (EOPs) .
1. 2 SCO PE This writer's guide applies to the writing of all E0 Ps. The guidelines should be applied uniformly, with the exception of those circumstances where deviation is thought to result in a more readable docunent, or where deviation better conforms to accepted htman fac tors principles .
2. 0 EOP ORGANIZ ATION AND IDENTIFIC ATION E0Ps govern plant operation during emergency conditions and specif y operator actions for returning the plant to a stable condition.

Each plant procedure is uniquely identified. This identification permits easy administration of the process of procedure preparation, review, revision, distribution, and operator use. In addition, all E0 Ps follow a similar pattern of organization to enhance operator. use of the EO Ps .

2.1 GENERAL ORGANIZ ATION OF E0Ps Organize E0 Ps into the following general elements :

a. Cover Shee t.
b. Table of Contents .
c. I. PUR POSE
d. II. S YMPTOMS
e. III. IMMEDIATE OPERATOR ACTIONS
f. I V. FOLLOWUP OPERATOR ACTIONS PAGE 1 0F 34 L -

e, SA P-2 07 -

- ATTACHMENT I

', REVISION 0

g. V. ATTAC HMENTS ATTACHMENT 1 - TITLE ATTACHMENT 2 - TITLE 2.1.1 Co nditions .-

If necessary to divide a procedure to reflect different situations , use conditions .

2. 2 COVER SHEET Every E0P has a cover sheet (see Attachment l').. The prtnary purposes of the cover sheet is to:

(1) identify the procedure and (2 ) to identify the authorized revision.

23 PROCEDURE TITLE Use a concise and descriptive title to identify the procedure and designate the scope of the procedure.

2. 4 PROCEDURE DESIGNATION AND NUMBtRING Designate the energency operating procedure as an E0P. A sequential nunber follows the procedure designator.

Ex ample: E0P-1.0 J l Sequence Number I Procedure De signator 25 REVISION DESIONATION AND NUMBERING Use sequential nunber after the word " revision" to ,

designate the revision level of the emergency operating procedure.

Ex ample: REVISION 1 l Revision Level PAGE 2 0F 34

1

- S AP-2 07 ATTACHMENT I

  • REVISION 0 30 PROCEDURE FORMAT Apply the following format consistently for all E0Ps .

31 TABLE OF CONTENTS Prepare a Table of Contents identifying the title and page number of major sections within the procedure.

Number of pages of the Table of Contents with lower case roman numerals (1,11) . Locate the page identification information (See 3 2) and page number in the top right corner of the page, as 'shown in Attachment 2.

Identify the procedure by centering the ,rocedure title on the Table of Contents page, and iden tif y column headings as SECTION and PAGE. Section headings and page numbers are connected by a series of periods ,

as shown in Attachment 2.

32 PAGE IDENTIFICATION AND NUMBERING Identify page of the procedure with (1) the procedure designator and number, (2) the revision number , and (3) the revision date. Place this information at the top right corner of each page, as shown in Attachment 3.

Identify each page of the procedure with the page number, specified as "PAGE of . Center this information at the bottom of each page, as shown in At tac hment 3 33 PAGE FORMAT Use dual-column format. Use the left-hand column for operator actions and label this ACTION. Use the right-hand column for contingency or alternative actions to be taken when the expected response is not obtained. Label this column ALTERNATIVE ACTION. A sample page format is presented in Attachment 3 PAGE 3 0F 34

SA P-2 07 ATTACHMENT I

', REVISION 0 3.4 PROCEDURE ORGANIZATION Use the following sec tion headings for all E0Ps .

a. PURPOSE -- The purpose provide s a brief descripti-on of what the procedure is intended to accomplish. State the purpose for operator association with the synptoms.
b. SYMPTOMS -- Include as a ymptoms only those alarms ,

indications, o perating conditions, automatic system actions , or other unique s ymp_ toms that the operator is to use in deciding to use the procedure.

c. IMMEDI ATE OPERATOR ACTIONS -- The Dnmediate operator actions are snort , concise, identifiable instructions that the user should be able to perform without recourse to the procedure.
d. FOLLOWUP OPERATOR ACTIONS -- The followup operator actions are short , concise, identifiable instruc tions that give appropriate direc tions to the user.

35 CONDITIONS Each E0P may c'ontain several conditions, as deemed necessary.

a. Designate conditions with capital letters, e.g.,

Condition A, Condition B, e tc.

b. Locate each condition on a new page.
c. Indicate the continuation of the condition by placing a continuation at the top of the page.

Ex ample: (CONDITION A : continued)

If a procedure contains numerous conditions, include the condition title in the continuation to minimize confusion. Abb rev iate only as necessary.

Ex ample : CONDITION A: HIGH RADIATION GENERAL AREA GAMM A (continued)

PAGE 4 0F 34

C S A P-2 07

. ATTACHMENT I REVISION 0

d. If appropriate, a single purpose statement reflecting the general purpose of the procedure may be used. More precision may be gained by using separate purpose statements for each condition.
e. Each condition should contain its own Symptoms, Immediate Operator Actions , and followup Operator Ac tions .
f. kny attachments are placed after the final condition.
3. 6 NUMBERING WITHIN PROCEDURES Use Roman numerals for numbering sections.

Number End indent ACTION and AUPERNATIVE ACTION steps as follows:

1. Ve r ify . . .
a. Check...
1) Position. . . (No t d esirable)

Use every effort to avoid using the 1) level of indenting. (See Figure 3, Page format) .

Use conttnuous step numbering from SECTION III to SECTION IV.

37 IN-TEXT REVISION IDENTIFIC ATION Tb identif y revisions to the text of an E0 P, locate a change bar in the margin' alongside the tex t change.

Changes in the lef t column are marked by a change bar in the left margin. Changen in the right colwnn are located by change bars in the right margin.

PAGE 5 0F 34

SAP-207 -

ATTACHMENT I REVISION 0

3. 8 ATTACHMENT ORGANIZATION Attachments include any materials which are neither included in the body of the procedure nor immediately available in the Control Room, but which are essential to carrying out the procedure. Attachments are to appear at the end of the procedure, arranged in numerical order. Use arabic numbers for numbering attachments.
a. Page identification for attachments is placed at the upper right corner of the page and is to follow one of two fo rmats:
1) When the attachment consists of a figure, table, graph, flow chart, log, list , or questionnaire, the identification includes the following information:

a) Procedure n6nber b) Attachment number c) Pag e number d) Revision number

2) When the attachment consists of entry conditions and operato r ac tions, the identification information and page numbering is the same as that for the body of the procedure (See Section 3 2) .
b. Provide a concise and descriptive title for each a ttac hment. Place the title at the top of each page of the attachment, centered, in all capital letters.
c. When attachments involve entry conditions and operator ac tions , use the following section headings .and guidelines:
1) TITLE -- State the title for operator association with the entry conditions.

PAGE 6 0F 34

a

  • S A P-2 07 .

ATTACHMENT I REVISION 0

2) ENTRY CONDITIONS -- Include only those alarms ,

indications, operating conditions, automatic system actions , or other unique s ymptoms that the operator is to use in deciding to use the procedure.

3) OPERATOR AC* IONS -- State the o perator ac tions as short, co nci se , identifiable instructions that give appropriate directions to the user.
4) Number and indent instruction steps as in the procedure b ody (See Sec tion 3. 6) . .
5) Use the two column format unless there are no alternative actions and a single column fonnat provides a more readable , more concise a ttac hmen t.
d. When attachments involve something other than entry conditions and operator actions (e .g. ,

figures , logs, g raphs , e tc. ) , follow the appropriate guidelines presented elsewhere in this Writer's Guid e.

4.0 WRITING ACTION AND ALTERNATIVE ACTION STEPS 4.1 STEP LENGTH AND CONTENT.

Instruction steps are to be concise and precise.

Conciseness denotes brevity; preciseness means exac tly defined. Th us , instruc tions should be b rief and exact. This is easily stated, but not so easily achieved. General rules to follow to meet these obj ectives are as follows :

a. Write instructions to communicate clearly to the procedure user.
b. Use short, simple sentences rather than long, compound, or complex sentences .
c. Deal with only one idea per step.
d. Write steps using an action verb-object fo rmat .
e. Specifically state the objec ts of operator actions. Identify exactly what is to be done to wha t.

PAGE 7 0F 34

. SA P-2 07 ATTACHMENT I REVISION 0

f. Use positive rather than negative sentences whenever possible.
g. Avoid long, obscure or abstract words.
h. Present complex evolutions in a series of steps, with each step made as simple as practicable.
1. If a step relates to three or more objects, give the objects in a list. If appropriate , provide space for operator c hec k-off.

~

J. Completely identif y component s and parts. If l appropriate , use exac t nomenclature. Include component numbers whenever possible. i

k. Express limits"4uantitatively whenever possible  :

(see 5 7). .Specif y values such that computations are unnecessary. ,

l

1. Generally, expected results of routine tasks need no t be s ta ted .
m. If stating expected results would benefit the user, as in restoring or resetting an alarm or trip, list the expected results immediately after the required action.
n. When actions are required based upon receipt of an annunciated alarm, list the setpoint of the alann for ease of verification.
o. When considered beneficial to the user for proper understanding and performance, describe the system response time associated with performance of the instruction.
p. When system response dictates a time frame within which the instruction must be accanplished, prescribe such time frame. If possible, however, avoid using time to initiate operator actions .

Operator actions should be related to plant par ame ters .

q. When anticipated system response may adversely a f fec t in s tr umen t indications , de scribe the conditions that will likely introduce instrument error and means of determining if instrument error has occurred by using a NOTE.

PAGE 8 0F 34

S A P-207

, ATTACHMENT I REVISION 0

r. When additional confirmation of system response is considered necessary, prescribe the backup '

readings to be made.

s. When steps are to be performed in other than numberical order, provide clear instructions to the user regarding proper sequence (for example, use "go to. . ." or " refer to. . .") .

4.1.1 Ac tion Dalunn The left-hand colunn of the dual .colunn format contains the operator action steps. . In addition to the general rules stated above, the following rules apply :

a. Locate expected sequences in this column.

The user normally will continue down the left hand column when the expected res ponse s ars ob tained.

b. Provide appropriate operator actions for the expec ted sequences .

4.1.2 Alternative Ac tion Colunn.

Present alternate actions in the right-hand column of the dual-colunn format. Al te rnative actions are operator actions that should be taken in the event a stated condition, event, or task does not represent or achieve the expec ted result. The need for alternative action occurs in. conjunction with tasks involving verification, observation, confirmation, and monitoring.

I Specify alternate actions for each circumstance in which the expected results or actions might not be achieved. The alternative actions should identify , a s appropriate , directions to override automatic controls and to initiate manually what is normally automatically initiated .

PAGE 9 0F 34

e *

ATTACHMENT I

  • REVISION O 4.2 USE OF LOGIC TERMS The logic terms and, or, not, if, if not, when and unless are of ten necessary to describe precisely a set of conditions or sequence of ac tions. When logic statements are used, emphasize logic terms so all conditions are clear to the operator. Ac hieve emphasis by underlining all letters of the logic terms.

Avoid using and and fy; within the same action. When and and cg; are used together, the logic can be very ambiguous.

The dual-column format used equates to the logic,11 not the action in the lef t-hand column, then follow the action specified in the right-hand column; for example: If Condensate Storage Tank level low, then switch to alternate Emergency Feedwater Supply.

Use other logic terms as follows:

a. When attention should be called to combinations of conditions , place the word and between the desc ription of each condition. Do not use the word and to join more than three conditions. If four or more conditions need to be joined, use a list fo rmat .
b. Us e the wo rd fy; when calling attention to alternative combinations of conditions. The use of the word cg; shall always be in the inclusive sense. To specif y the exclusive "or," the following may be used: "either A cy; B, but not both."
c. When action steps are contingent upon certain conditions or combinations of conditions , begin the step with the words if; or when followed by a description of the condition or conditions (The antecedent) , a comma, the word then, followed by the action to be taken (the consequent). Use when for an expected condition. Us e il fo r an unexpec ted but possible condition.
d. Limit use of if not to those cases in which the operator must respond to the second of two possible conditions. Use if to specify the first condition.

PAGE 10 0F 34

. m S A P-2 07 .

ATTACHMENT I h1- REVISION 0 Do not use then at the end of an action step to instruct the operator to perform the next step

^

because it runs actions together.

'" ~ . c nn, 43 USE OF CAUTIONARY INFORMATION AND NCTES Cautionary information can be considered in two f undamental categories: that which applies to the entire procedure and that which applies to a portion or a specific step of the procedure. That which applies to the entire procedure is called a "PREC AUTION" and is covered in operator . training.

That which applies to a portion of a procedure is called " CAUTION" and is placed immediately before the procedural step to which it applies.

Cautions attrac t attention to essential or c ritical baformation in procedures. Use a caution to denote a potential hazard to equipment or personnel associated with or consequent to the subsequent instructional step. Cautions are not meant to replace instructional steps , and should no t generally contain operator ac tio ns . To ensure that the procedure user observes the caution before performing the step, adhere to the following:

a. Place the caution to extend across the entire page, immediately prior to the applicable step.
b. Follow the word " caution" with the number (s) of the ste p( s) to which it applies (i.e. CA UTION 6 ) .
c. Center , capitalize , and underline the caution heading.
d. Highlight the caution in a box of asterisks .
e. Never break a caution statement between pages or place a caution at the bottom of a page separated from its associated step.

PAGE 110F 34 l

l

9 SA P-2 07

.' ATTACHMENT I

', REVISION 0

f. Example:

e e e a** * * * * * *a a ea ea e n * * ****

  1. CAUTION 11
  • n .. *
  • Automatic reinitiation of Safety Lajection *
  • o pen. If, Sa fe ty La j ec tion is need ed , then it #
  1. must be reinitiated manually.
  • W W W # # # # # # # # N f 5 W N W M N W W # M N M 4 5 5 Notes are used to present other Lnportant supplemental information in procedures, such as information necessary to support an instructional step. No tes present info rmation only, not ins truc tions . Adhere to the following guidelines when using a note:
a. In general, locate the note in the right hand margin column immediately before the procedural step to which it applies. If a note applies to an entire section, place the note at the beginning of the section, centered on the page.
b. Follow the title NOTE by the appropriate step n umb er .
c. Place the title information immediately over the note , centering, capitalizing and underlining as follows :

NOTE b Inj ec tion from. . .

d. Locate the note on the saae page as the step to which it applies.

PAGE 12 0F 34

S A P-2 07 ATTACHMENT I

- REVISION O

4. 4 CA LCULATIONS Avoid mathematical calculations in E0Ps . If a calculation is required to perform a procedural step, keep the calculation as simple as possible, provide work space for the calculation, and use a chart or graph whenever possible.

45 USE OF UNDERLINING Underlining is an effec tive means of emphasizing key terms. Use underlining for emphasis of the following:

a. Log ic te rms ( and , o r , no t , i f , i f no t , when ,

unle s s) .

b. Negative terms (not) .
c. Wo rds deno ting nunber (all, any, both, either ,

neither , nor , eac h) .

d. Headlines or titles (PURPOSE, CAUfION, NOTE).
e. Other instances where the writer deems underlining to be essential for gaining needed emphasis.
4. 6 REFERENCING AND BRANCHING TO OTHER PROCEDURES OR STEPS Referencing and branching indicate that additional steps or an additional procedure are' used to supplement the procedure presently in use. Av oid referencing either past or future steps within the procedure being used. When only a few steps are involved in the referencing, include the steps in the procedure at the point they are needed.

To minimize potential operator conf usion, use branching when the operator is to leave one procedure or step and use another procedure or step. When b ranching is used, the following rules apply:

a. When the operator is to reference a future step within the procedure currently in use, the key wo rd s "go to" .

PAGE 13 0F 34

s

- SA P-2 07 -

.' ATTACHMENT I REVISION 0

b. When the user is to return to a completed step with that procedure, use the key words, " return to".
c. When the user is to leave the procedure in use and refer to -another procedure , use the key wo rds , "go to".
d. . To emphasize the title of the branched procedure, capitalize all letters of the title', and place it in quo ta tion marks , for example, go to E0P-1. 0,

" SAFETY INJECTION ACTUATION".

e. As indicated, the terms "go to" and " return to" direct the user to leave the current step and refer to the b ranched step or procedure. When referencing is an optional rather than a required operator ac tion, use the key words " refer to" .

47 COMPONENT IDENTIFICATION With respect to identification of components, adhere to the following rules :

a. Identify equipment, controls, and displays in operator language (common usage tenns). Do no t abbreviate unless using exact nomenclature from panel placards and alarm windows .
b. When the engraved names and numbers on panel placards and alarm windows are specifically the item of concern in the procedure, quote the engraving verbatim (use exac t nomenclature) , and emphasize by using all capital letters.
c. When identif ying components , list the component name first , and follow the name with the component n umb er , plac ed in parentheses.

Ex ample: RHR DISCHARUE FIDW ( F1-605A )

d. When a c omponen t n ame inv olve s a s umm ar y lab el ,

state the summary label first , followed by a parentheses , and the name of the specific c ompo nen t .

Ex ample: PZ R HEA TER , BU GRP 1 PAGE 14 0F 34

e

- S A P-2 07 -

l ATTACHMENT I

  • REVISION O
e. Do not combine component names and/or numbers unless such a combination represents exact nomenclat ure .

Ex ample: Do no t use :

a. Reset SI RESET TRAIN A and TRAIN B.

Do use :

a. Re se t b oth SI RESET TRAIN and SI RESET TRAIN 8.

Do not use :

(MVB-310 6A and B)

Do use:

(MVB-3106A and MVB-31068)

f. If the component is seldom used or it is felt that the component would be difficult to find, give location information following the identification.

In general, location infonnation should be placed in parentheses.

g. Capitalize all letters of exact labeling of switch or component positions (FAST, START) .
4. 8 LEVEL OF DETAIL Av oid too much detail in E0Ps so that operators can effectively execute the instructions in a timely m anner . Use the level of detail that a newly trained and licensed operator would desire during an ' emergency

~

c ond ition.

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

a. For each control with a number engraved on the control panel placard, include the number in parentheses within the instructional step; for example , " Ensure SEAL WTR RTN ISOL (MVT-6100) o pen." '

PAGE l$ OF 34

S A P-2 07

. ATTACHMENT I REVISION 0

b. For control circuitry that executes an entire function upon actuation of the control switch, use the action verb appropriate to the component without further amplifying how to manipulate the control device ; for example , "Close PZR PWR RELIEF

( P CV-4 4 5A ) ." The following action verbs are rec ommend ed :

1) For power-driven rotating equipment, use Start, Stop.
2) Fo r valves , use Open, Close , Thr.o ttle Open, Thro ttle Close, Thro t tle .
3) Fo r po we r d ist r ib ut io n b reake r s , u s e Synchronize and Close, Trip.
c. For control . switches with a positional placement that establishes a standby readiness condition, use the verb "Se t," 'along with the engraved namo o f the desired position.

Po sitional placements are generally associated with establishing readiness of automatic functions and are typically named AUTO or NORMAL; for example , " Set the GLAN D SEA L AIR COMPRESSOR Control Switch (S15) in AUTO. "

d. For multiposition control sw! tches that have more than one position for a similar func tion specify the desired position placement; for ex mnple ,

" Place DIESEL FIRE pump SELECTOR switch to TEST No. 2."

e. Standard practices for observing for abnormal res ults need no t be prescribed within procedural st e ps . For example, observation of noise, vibration, erratic flow , or discharge pressure need not be specified by steps that start pumps.
f. Attachment 1 contains a complete constrained language list .

PAGE 16 0F 34

SA P-2 07

, ATTACHMENT I

", REVISION 0

4. 9 PRINTED OPERATOR AIDS When presenting information with graphs, charts, tables , and figures , verif y tha t aids are self-explanatory, legible, and readable under the expected conditions of use and are within the reading precision of the operator.

4.9 1 Units of Measure Give units of measure on figures, tables, and attachments in numerical values that represent observed measurement data or calculated res ults . Use a virgule (slant line) ins tead o f "per";

ex amples : f t/sec , lbs/hr.

492 Titles and Headings Capitalize all letters of table titles and all letters of column headings within the table.

When referencing tables and figures within the text, initially capitalize the generic reference and capitalize all letters of the actual figure or table title.

Ex ample: Complete Attachment 1, SHORT TERM PLANT STATUS LOG, or Refer to Table 2.

4.9 3 Figure, Thble, and Attachment Numbering Assign sequential arabic numbers to figures ,

tables, and attachments in separate series.

The sequence should correspond with the order of their reference in the text. The synbol "# "

and. abbreviation "No." are unnecessary and should not be used. The number alone-s uffices .

Ex amples : Figure 1, Figure 2, e tc .

Table 1, Table 2, e tc.

Attachment 1, Attac hment 2, e tc .

PAGE 17 0F 34

o 4 SA P-207 ATTACHMENT I

", REVISION 0 50 MECHANICS OF STYLE 51 S PELLING' Keep spelling consistent with modern usage. When a choice of spelling is offerred by a dictionary, use the first spelling.

52 PUNCTUATION Punctuation should be used as necessary to aid reading and prevent misunderstanding. Select word order to require a minimum of punctuation. When extensive punctuation la necessary for clarity, the sentence should be rewritten and possibly made into several sentences. Apply the folloving rules for punc tua tion:

5 2.1 Brac kets Use brackets only to enclose values for reference under adverse conditions .

5 2.2 Colon ,

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

5 2.3 Comma Use of many commas is a sign the instruction is too complex and needs to be rewritten.

Therefore, evaluate the number of commas to ensure the instruction is not too complex.

Use a comma after conditional phrases for clarity. Ex ample: WHEN level decreases to 60 inc he s , THEN star t pump. . . .

5 2.4 Parentheses Use parentheses to indicate alternative items in a procedure , for instruction, for equipment numbers, and for indicating location.

PAGE 18 0F 34

4

, . SA P-2 07 ATTACHMENT I

, REVISION 0 525 Period Use a period at the end of complete sentences and for indicating the decimal place in num ber s .

53 CA PITALIZATION Use capitalization to conform to standard knerican English usage , and also to emphasize wceds cad phrase s as follows:

a. Center and capitalize all letters in the procedure ti tle .
b. Capitalize and underline all letters in sec tio.n headings , column headings , caution headings , and no te headings.
c. Capitalize all letters contained in the page identification information.
d. Capitalize all letters of exact nomenclature.
e. Center and capitalize all letters of attachment, figure, and table titles.
f. Capitalize all letters of column headings in attachments, figures, and tables.
g. Enphasize the names of plant system titles 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 still emphasized by initial capitalization.

54 HYPHENATION Use hyphens between elements of a compound word when usage calls for it. Apply the following rules for hyphenation:

a. When doubt exists, restruc ture the compound word to avoid hyphenation.

PAGE 19 0F 34

~ -- - --- - -

,- . . - - - , , , - - , - - . . , - , - - , e- , , , ,, --

. SA P-207 -

', ATTACHMENT I

', REVISION 0

b. Use hyphens in the following circumstances:
1) in compound nunerals from twenty-on~e to ninety-nine ; example: one hundred thirty-four.
2) in fractions; examples: o ne-hal f, t wo-thirds .
3) in compounds with "self"; examples:

s el f-con tained , s el f-lub rica ted.

4) when the last letter of the first ; word is the asne vowel as the first letter of the second word--as an alternative, use two words; example: fire-escape or fire escape.
5) when misleading or awkward consonants would result by joining the words; example:

b ell-like .

6) to avoid confusion with another word; examples: re-cover to prevent confusion with recover, pre-position to avoid confusion with pre position.
7) when a letter is linked with a noun; examples: X-ray , 0-ring, U-b olt , I-beam.
8) to separate chemical elements and their atomic weight ; examples: Uranium-23 5, U-23 5 55 VOC ABULAR Y Une words to convey precise understanding to the trained peroon. The following cules apply :
a. Us e simple wo rd s . Simple words are usually short words of few syllables , and are generally common wo rd s .
b. Use common usage if it makes the procedure easier to understand.
c. Us e wo rd s t ha t a r e c onc re te r athe r t han v ague ,

specific rather than general, familiar rather than formal, precise rather than blanke t.

PAGE 20 0F 34

SAP-207 -

ATTACHMENT I REVISION 0

d. Define key words that may be understood in more than one sense.
e. Use verbs with specific meaning. Examples are listed in Attachment 4.
f. Denote equipment status as follows :
1) Operable / operability--These words mean that a s ys tem, s ub sys tem, t rain , c omponent , o r d ev ic e is capable of perfonning its specified f unc tion ( s) in the intended manner. Implicit in this definition is the assumption. that all necessary attendant instrunentation, controls, normal and emergency electrical power sources ,

cooling or seal water, lubrication or other auxiliary equipment required for the system, subsystem, train, component, or device to perform its function (s) are also capable of perfo rming related support func tion ( s) .

2) Operating--This word means that a system, s ubsystem, t rain, c omponent, or device is in operation and is performing its specified f unc tio n( s) , and tha t " Ou t o f Se rv ic e Card s" or other conditions do not prevent it from maintaining that service.
3) Available--This word means that a system, subsystem, train, component, or device is operable and can be used as desired; however ,

it need not be operating.

5. 6_ SENTENCE STRUCTURE Write sentences, clauses, and phrases in a manner which is short and directive. .Use action verb s followed by the object of the verb. Us e 13, are, have, has, etc. when necessary. In general, the se terms are unncessary.
5. 7 NUMERICAL VALUES Use numerical values in accordance with the following rules:
a. Use arabic numberals. Fo r b revity, use nwnerals t rather than words when referring to quantities.

PAGE 210F 34

. SAP-207 .

ATTACHMENT I REVISION 0

b. For numbers less than unity , precede decimal point by a zero; for example: 0. 1.
c. The number of significant digits should be equal to the number of significant digits available from the display and the reading precision of the o perato r.
d. Specify acceptance values in such a way that addition and subtraction by the user is avoided if possible. Tais can generally be done by stating acceptance values as limits. Examples: 510 F maximum, 300 psig minimum, 580 to 600 F. Fo r calibration points , stating the midpoint' and its lower and upper limits for each data cell will accomplish the same purpose ; for example,10 milliamperes (9 5 to 10 5). Avoid using + .
e. Always specif y engineering units for numerical values of process variables. They should be the same as those used on the Control Room displays ,

for example: psig instead of psi.

f. When values for adverse Containment conditions must be given, place them in bracke ts following the value for normal Containment conditions.

Ex ample: a. Pressurizer pressure is greater than 20% [25%].

58 ABBREVI ATIONS, LETTER SYMBOLS, AND ACRONYMS Minimize the use of abbreviations and acronyms because they may be confusing to those who are not thoroughly f amiliar with them. Use abbreviations and acronyms only when their meaning is unquestionably clear to the in tended reader, when using exac t nomenclature , and when referring to quantiti.es. Maintain consistent use of abbreviations and acronyms throughout the procedure.

Capitalize abbreviations unifo rmly. If t he abbreviation is comprised of lowercase letters , use lower case letters when the abbreviation appears in title s or headings. Omit the period in abbreviations except in cases where the omission would result in conf usion .

PAGE 22 0F 34

. S AP-2 07 ATTACHMENT I REVISION 0 Use letter a ymbols , abbreviations , and acronyms to represent quantities, as appropriate. Ex amples o f s uch use ' include: F, 5 %, T, gpm, psig, Tavg. do not use synbols for greater than, less than, or equal to, unless presenting a computational formula.

6.0 TYPING FORMAT 6.1 GENERAL REQUIREMENTS Use 8 1/2 x 11 inch white , bond paper.

6.1.1 font

a. 10 pitch (10 characters per inch) .

4 b. PIC,A 10 print wheel (unadorned font , with no serifs).

6.1. 2 Margins

a. Se t to p o f pag e a t 1 1/2 inc he s , o r line 8.
b. Se t lef t margin at 1 1/4 inches , or space 12..
c. Se t r ight marg in at 1 1/8 inche s , o r s pac e 7 4.
d. Se t boctom of page at 1 inch, or line 60.

6.2 COVER SHEET Type the c ov er she e t a s sho wn in At tac hm en t 1.

a. Beginning on line 8, center, capitalize , and double space the plant identification Lafo rma tion.

i l

b. Type in capital letters, center, and double space the following procedure specific information, l

> beginning on line 20:

l

l. EMERGENC Y 0 PERATING PROCEDURE
2. Procedure Number.

3 Procedure title.

4. Revision number.

5 Revision date.

PAGE 23 0F 194

, S A P-2 07 .

ATTACHMENT I e REVISION 0

c. 3t line 3 6, spac e 60, capitalize & type SAFETY HELATED.
d. Beginning on line 42, type the review and approval information at the lei t hand margin. Triple s pac e this information.
e. On line 60, s pace 50, type the date identification line.
6. 3 TABLE OF CONTENTS
a. Type the table of contents as shown in. .

Attachment 2. Type all alphabet characters in capital letters.

b. Place the following page identification information in the upper right corner on line 3, beginning at space 64.
1. Procedure number.
2. Page number in lower case Roman numerals.

3 Revision number.

4. Num eric al date .
c. Center and capitalize the procedure title on line 9 ra
d. Underline SECTION and PAGE headings and place on

. line 12 as follows :

1. Type SECTION at left margin.
2. Type PAGE at spac e 6 8.
e. Spacing for listing contents is as follows :

I'. Triple space af ter the following:

a) Page identification.

b) Procedure title .

c) Section, page headers.

2. Double space af ter the following:

a) Se c tio n heading s .

b) Attac hment titles .

3 Single space after any continued lines.

PAGE 24 0F 34

SA P-2 07 -

. ATTACHMENT I REVISION 0

f. Begin listing contents on line 16 as follows:
1. Section headings:

j a) Use Roman numerals, left hand justified at nrargin .

b) Capitalize all letters in Section headings and begin at space 18. Do NOT underline.

2. Attachment titles:

a) Place the word " ATTACHMENT" at space 18.

b) Use Arabic numerals one space af ter

" ATTACHMENT", and follow the number by a dash with one blank space before and af ter the . dash.

c) Begin attachment titles after the space, and do no t extend past spac e 7,4.

g. Connect section headings to page numbers by a serie s .of periods , each separated by a space .
h. Type page numbers at space 70.
6. 4 PROCEDURE BODY Attachment 3 provides some examples for typing the procedure body. Type the procedure as follows :

6.4.1 Page Id entification Place the following page identification b1 formation in the upper right corner on line 3, beginning at space 64, single spaced, in capital letters :

a. Procedure nunber.
b. Revision number.
c. Numerical date.

4 PAGE 25 0F 34

~

S A P-207 .

ATTACHMENT I REVISION 0 6.4.2 Headings Type headings throughout the text as- follows :

a. Section headings are centered, underlined, and placed within the text page; for ex ample , I. PUR POS E.
b. Attachment titles are centered', and each a ttac hmen t b egin s on a ne w page .
c. Use two colunn headings under Sections lII. IMMEDIATE OPERATOR ACTIONS and I V. FOLLOWU P OPERATOR ACTIONS. . The lef t column under each section is entitled ACTION: the right column is AUTERNATIVE ACTION.
1. Place the column header ACTION at s pace 16.'
2. Place the column header AUTERNATIVE ACTION at space 4 6.

6.4.3 Spacing Space the tex t as follows :

a. Triple-space af ter the following:
1) Page headers.
2) Section headings .
3) Text, when preceding Sec tion headings.
4) Two column headings .
5) Upper and lower caution box lines.
b. Double space af ter the following:
1) Caution and No te he ad ing s .
2) Caution and Note text .
3) Each Step.
4) Each Sub s tep .
c. Single space the following:
1) Purpose statement.
2) Subsequent lines of text.
3) Sub sequen t line s o f s ub s te ps .
4) Text of Cautions and No tes.

PAGE 26 0F 34

D SA P-207 ATTACifMENT I EdVISION 0 6.4.4 Numbering Procedure Steps Number procedure steps as follows:

1. Number steps consecutively (1,2,3. . . ).
2. Designate substeps with lower case letters ,

(a, b, c...).

3 Designate further substaps with a number followed by a parenthesis (1), 2), 3) ...).

6.4.5 Breaking procedure steps and breaking. words.

a. To . facilitate operator reading avoid b reaking procedure steps. When b reaking of steps is unavoidable , apply the following rules"
1. Do not separate a caution from its appropriate text.

- 2. Do no t break substeps at the third level.

3 When a step begins on one page and ends on another, place a continuation in parentheses at the top of the next page , for example , (2 0. continued) or (2 0.a continued) .

4. Where a step is continued on the next page in both the ACTION and ALTERNATIVE ACTION columns , place a continuation (as above) at the top of both columns.
b. Do no t break words .

6.4.6 Tab se ts Se t tabs for steps and substeps at the follo wir.g :

a. Fo r lef t hand side, ACTION column:
1) Start Step number at margin and set tex t a t space 16.

PAGE 27 0F 34

~

. SAP-207 ATTACHMENT I

.. REVISION 0 NOTE: Placekeeping line extends into

. left hand margin, in, front of step number.

2)

~

Start Substep number at 16 and set test at 20.

3) Do not extend text past space 43
b. For right hand side, ALTERNATIVE ACTION column:
1) Begin Step number at 46 and set text at 50.
2) Begin Substep number at 50 and set text at 54.
3) Do not extend text past space 74.

6.4 7 cautions Type cautions as follows:

              • n e a e n a ae eae* *a e a eae n a e a CAUTION 2
  • e n
  • Emergency feedwater flow should not be throttled *
  1. until water level is above the top of the #

U-tubes.

          • n a e aea e a a e en a ee n**** *a
a. Margins and spacing are as follows:
1) Left box margin at 16.
2) Right box margin at 70.
3) center title.
4) Begin text at 20; do not go past 70.
5) Double space between upper row of asterisks and title.
6) Double space after title.
7) Double space after text.
b. Type the caution above its associated i step.
c. The caution and step should be typed on the same page.

PAGE 28 0F 34

. S A P-2 07 ATTACHMENT I

', REVISION 0 6.4.8 No tes Type notes as follows :

a. Keep margins consistent with previous right c ol umn ma rgins .
1) A note referring to a step begins at s pac e 5 0.
2) A no te r efe rr ing to a s ub st e p b eg in s a t s pac e 54.
3) Do not type past space 74.
4) Center the title over the text.
5) Double space after the title.
b. The exception: Notes at III or IV level are centered on the page.
c. Type the note and the step or substep on the same page.
d. When the note applies to a step (e .g . ,

NOTE 10), the note is placed as follows :

1) If there is an alternative action in righ t col umn , plac e the no te and tex t entirely prior to the step.
2) If Jgt alternative action, place the note so that the text of the note begins on the sane line as the text of the scep.
e. Fo r s ub s te p (e .g. , Note a):
1) If there is an alternative action in right column, place entirety of NOTE a before substep, but after step.

PAGE 29 0F 34

. SAP-2 07 ATTACHMENT I REVISION 0 Example:

^ 25. Check for switchover to Cold Leg recirculation:

No te a

a. a.
2) If nJt alternative action, place first line of text on same line as first line of substep.

Ex:

No te a a.

6.4.9 Finishing Do not ex tend the east line of text past line 55.

Type footers as follows :

a. Capitalize PAGE, use lower case letters for o f, a s sho wn : PAGE of
b. Place footers on line 60.
c. Start a t s pace 3 4.
6. 4.10 Capitalization
a. Type in all capital letters:
1) Title and procedure specific*

information on titl e page.

2) Wording on Table of Con tents page .
3) He ad ing s .

PAGE 30 0F 34

S A P-2 07 I ATTACHMENT I

', REVISION 0

4) Annunciator legends.
5) Engineering / equi pment prefixes.

6} Exac t control board and plant

-' nomenclatur e.

b. Initially capitalize the following:
1) First word in the sentence.
2) Proper names .
3) Major system names.
4) Plant conditions .
6. 4.11 Placekeeping aids.

Placekeeping aids are checkoff spaces used to remind the operator of his/her place in the procedure. The complexity of the step will influence placement of the placekeeping aids.

a. Use placekeeping aids for each step in the followup Operator Actions.
b. Place the aid in the ACTION column so that i t ex tend s in to the le f t hand ma rgin , in front of the step number.
c. Use placekeeping aids in front of substep numbers as deemed necessary.
6. 5 ROTATION OF PAGES If pages need to be rotated, follow these rules:
a. The top of the page with rotated print is the normal left-hand edge.
b. The page margin s doi no t ro ta te .

PAGE 31 0F 34

SA P-2 07 ATTACHMENT I REVISION 0

6. 6 PRINTED OPERATOP. AIDS 6.6.1 Figures -

Figures include graphs, drawings, diagrams, and illustrations. The following rules are established:

a. Place the figure number and title three live spaces below the figure field.
b. The figure number and title should be in

~

the same type style as the rest of the procedure.

c. Do not violate specified page margins to accommodate the figure field.
d. Use a figure field of sufficient size to offer good readability.
e. Use simple presentauions such that the essential message is clear.
f. Place grid lines at least 1/8 inch apart.

Make numbered grid lines bolder than unnumbered B rid lin es .

g. Accompany labels of items within the figure with arrows pointing to the item.
h. Orient items within the figures as naturally as possible. Fo r example, place height on a graph along the vertical axis.
1. In general, items within the figures should be labeled. using pica 10 pitch type.

Exceptions may be in pitch 15, bold faced.

Print handwritten labels using all capitals, with letters and numbers at least 1/8 inc h high .

J. Be certain all lines in figures are re prod uc ible .

4 PAGE 32 0F 34

S A P-2 07

- ATTACHMENT I

', REVISION 0 6.6.2 Tables Type tables according to the following rules:

a, Use type style and size consistent with that used for the rest of the procedure.

b. Locate table number and title three line spaces above the table field and three line spaces below preceding text. Capitalize all letters of the title.
c. Enter a heading for each column, and center that heading within the colunn.. Capitalize all letters of column headings.
d. Place horizontal lines above and below the column headings; vertical lines , while desirable, are not necessary or required.
e. Align tabular headings as follows :
1) horizontally by related entries.
2) vertically by decimal point for numerical entries.
3) vertically by first letter for word entries; however, run-over lines should be indented three spaces.
f. Double space between horizontal entries to segregate such entries. Horizontal lines may also be used if desired. If used, place double horizontal lines above and below the column headings.
g. There should be no vacant cells in the table. If no entry is necessary, enter "N. A." to indicate no t applicable.
6. 7 Attac hnent s When typing attachments, follow the margin guidelines a s se t in 6.1. 2.
a. Place the page identification information in the upper right corner, beginning on line 3 at space 64.

PAGE 33 0F 34

. S A P-207 .

ATTACHMENT I

  • REVISION O
b. Three line spaces below the page identification information, center and capitalize the attachment title, beginning each title on a new page.
c. When typing entry conditions and operator actions, the following guidelines apply :
1) Type the headings, ENTRY CONDITIONS and OPERATOR ACTIONS at the lef t margin, underlined, in all capital letters.
2) . Type the twc column headings as specified in s ec tion 6. 4. 2. c .
3) Follow o ther guidelines as established in Sections 6. 4 3 through 6. 4.11.
d. When typing operator aids, see Sections 4 9 and
6. 6.
6. 8 USE OF FOLDOUT PAGES Use of foldout pages are optional. Foldout pages contain information or conditions that may apply throughout the procedure implementation.
6. 9 USE OF OVERSIZED PAGES Lo not use oversized pages. Reorganize or reduce the page to standard size.

6.10 USE OF REDUCED PAGES Avoid using reduced pages whenever possible. Be certain reductions are readable.

7.0 RE PRODUCTION Re produc tion will be done on a standard copier.

9 PAGE 34 0F 34

. ATTACHMENT 1, COVER SHEET FORMAT

. .' C ENTERED I

LIN'E 5 SOUTH CAROLINA ELECTRIC AND GAS COMPANY VIRGIL C. SUMMER NUCLEAR STATION DOUB LE S PACE NUCLEAR OPERATIONS 4 8 LINES LINE 16 EMERGENCY OPERATING PROCEDURE E0P-1.0 SAFETY INJECTION ACTUATION DOUBLE SPACE 4

REVISION 1 JUNE 19, 1983 LINE 30 SAFETY RELATED SPACE 60 LINE 36 DISCIPLINE SUPERVISOK Da te TRIFLE SPACE A PPHO VA L A UTHORIT Y Da te LINE 47 l DATE ISSUED SPACE 63 RECORD OF CHANGES l CHANGE TYPE DATE DATE CHANGE TYPE DATE DATE l NO. CHANGE APPROVE E CA NC ELLE L NO. CHA NGE APPROVEL C ANC ELLEL i

i

SPACE l64

, LINE 3 E0P-9 0 PAGE i SINGLE SPACE REVISION O 7/29/83 ATTACIMENT 2, TABLE OF CONTENTS FORMAT CENTER l LINE 9 HIGH RADIATION OUTSIDE CONTAINMENT S PACE 12 SPACE 68 LINE 12 S ECTION PA GE LINE 15 I. PUR POSE. .. . . . .. . . . . . ......... 1 II. S YMPTOMS. . . . . . .. . . . . . ......... 1 DOUB LE S PAC E III. IMMEDIATE OPERATOR ACTIONS. . . . ......... 2 IV. FOLIDWUP OPERATOR ACTIONS . . . . ......... 4 I V. ATTACHMENTS ,

A TTACHMENT 1 - TITLE t

O I

I

. SA P-207 l

< ,' ATTACIMENT III PAGE 1 OP 4 REVISION 0 1

E0P DEVEIDINENT CHECKLIST E0P NUMBER:

TITLE:

  • This checklist is to be used for non-technical review by writers , editors , and proofreaders. Review the procedure for each of the following criteria. If the procedure meets a
criterion, place a check on the line provided. If a criterion is not met, write "no" on the line. If the critorion does not apply , write "NA" .

YES O N_O A. Cover Page i i 1. The cover page layout is consistent with Figure 1 of the Writera Guide.

l 2. Upper and lower caso lettering is used as shown in Figure 1 of the Writer' a Guide.

3 The title la brief and describes I the purpose of the procedure.

B. Table of Contents contains the following!  ;

1. Header (4 lines - upper right) . _
2. Procedure Title (centered) .

3 Column lloaders.

4. Ol tr ica .

I. PUR POSE II. S YMPIONS III. IMMEDI ATE OPERATOR ACTIONS I V.

V.

FOLLOWU P OPERATOR ACTIONS ATTACINEt(fS

[

ATTACINEffP 1 - TITLE 5 Corresponding page numbern for above. __

C. Proceduro Body ,

1. Ileader (each pago - 311nos uppor r igh t) . ,
2. PAGE of (each page - bottom) _

. SPACE l64

,' LINE 3 E0P-9 0

    • PAGE 1 SINGLE SPACE REVISION 0 7/29/83 ATTACHMENT 3, PAGE FORMAT C ENTERED TRIPLE SPACE I. PUR POSE TRIPLE SPACE This proc edure provides. . .

TRIPLE SPACE II. 0 YM PTOMS III. IMMEDIATE OPERATOR ACTIONS SPACE 16 SPACE 46 'IRIPLE SPACE l ACTION ALTERNATIVE ACTION S PACE 12 S PACE 16 SPACE 50 TRIPLE I

l l SPACE

' 1. 1.

SPACE 20 S PACE 54 l l

a. a.

SPACE 24 SPACE 58 I i

1) 1)

I V. POLTOWUP O PER ATOR ACTIONS ACT!aN A LTERNATIVE ACTION i

2.

3 3 a.

a. -

1) 1)

PAGE of

4 ATTACHMENT 4, CONSTRAINED LANGUAGE LIST Align Place valves or electrical devices in proper position for accomplishing specified f unction.

Check Detenmine present s tat us .

Cl ose Re fers to valves. Generally

- involves completely stopping flow from entering or exiting an area, e.g., Close PCV-445 8, PZR 'PWR RELIEF.

De-ene rgize Remove power supply by manual b reaker operation.

Depress Refers to pushbutton operation.

De termino Infers technical knowledge. Make a decision based on operational kno wledg e.

Drive Stepping in rods to specified po in t. Movement of reactor control rods , either in or out.

Energize Supply power by manual breaker operation.

En sure Take necessary/ appropriate actions to guarantee component , system, reading, e tc. is as specified.

Establish Perform actions necessary to meet stated condition.

Evalua te Appraise the aituation. Infers technical knowledge.

Paulted The piece of equipment which has currently become inoperable.

Go To Leave the present step or procedure and not return until directed.

Implement Commence a required program or series of procedures, for example,

" Implement the Dnergency Plan".

Ins pec t Examine or review present c onditio n. ,

Load Increase electrical output of a g enerato r.

l PAGE 1 of 4

CONSTRAINED LANGUAGE LIST s

.~

Maintain Take appropriate actions to prevent fluc tua tion / changing.

Manually Initiate Operator action which activates a safety f unc tion which is~ normally initiated automatically due to plant conditions.

Manually Trip Operator action to activate a Reactor Trip or stop an operating piece of equipment such as a pump.

Modulate Position a valve to a required position by use of controller to establish a required parameter.

Monitor Periodically check status. Ob se rve current trend.

No n-faulted An operational component which is redundant to one which has malf unctioned.

Open Refers to valve. Generally involves removing barrier to allow flow to enter an area , e .g., Open

]'

POV-4458, PZR PWR RELIEF. Where instruction to partially open a valve is given, involves

controlling or restricting the volume of flow across a barrier.

Per As specified in or by name procedure. Infers referencing the doc ument is optional.

Plac e Physically position a switch to the specified location.

Rack in Place an electrical breaker in place by physically connecting it to its associated power source.

Rack out Remove an electrical breaker from service by physically disconnec ting it from its associated power source.

Reco rd Doc ument requested information on form provided.

PAGE 2 of 4

. CONSTRAINED LANGUAGE LIST

.. i

( Re fer Use as a supplement. Perfo rm '

applicable actions of cited procedure and return to the controlling procedure, for example,

- " Refer to Foldout page".

Regulate.

Con trol or re s tric t ra te .

Rostore Repair and/or return to service.

Ro ta te Turn a rotary multi-position switch to the required position. In reference to pump, hand rotate before energizing.

i Sample Generally involves directing other

! personnel to obtain a representative part to be analyzed  ;

for content.

i Secure Remove from service. Take appropriate action to prevent l return.

Se t Manually position a control switch to s pecified setting.

Shift Specifies changing mode of

- operation, for example, " Shift SW Pump to FAST Speed".

l Shutdo wn Comple tely close down. l Stabilize Maintain in a manner to reduce fluc tuat ion.

Start To originate motion of an elec trical device, for example, .

" Start . . . . Puu p" .

Startup Tb set into motion the process of

  • aligning valves , starting pumps , or any other auxiliary equiment necessary to place a system or systems into operation.

i Stop Tb terminate operation, for  ;

ex am pl e , " St o p . . . . . pum p" .

Survey Ins pect , examine. Complete survey fo rm.

l PAGE 3 of 4 l

CCIISTItAINED LAIIGUAM LIST  !

Transfer Specifies changing location or mode of control, for example, " Transfer S G Lev el to MAN UA L" .

Trip Effec t a comple te and total immediate shutdown.

Thro ttle . Place a valve in an intemediate position to restrict flow to the required amount. Infers that an automatic controller las been i placed in a manual mode of o pe ratio n.

Verify Detemine if in proper cond itio n/sta tus .

1 PAGE 4 of 4 i

il

6. ..'

l , .

SA P-2 07 .

j ,' ATTACHMENT II

+

PAGE 1 OF 1  !

REVISION 0 i EOP STEP DOCUMENTATION E0P NO REV. TITLE i

STEP NO. __

l STEP:  !

i \

4 I

i l

i i

ERO NO. TITLE l 4 i

] STE P:

i l

JUSTIFICATION OF DIFFERENCES:

SOURCE OF NUMERICAL VALUE USED: ,

i REVIEWED BY:

SA P-2 07 .

ATTACIMEPR III PA GE 1 OP 4 i REVISION 0 i EOP DEVEIDPMENT CHECKLIST E0P NUMBER:

TITLE: -

This checklist is to be used for non-technical review by writers , editors , and proofreaders. Review the procedure for each of the following criteria. If the procedure meets a criterion, place a check on the line provided. If a criterion is not met, write "no" on the line. If the criterion does not apply , write "NA" .

YES NJ A. Cover Page

1. The cover page layout is consistent with Figure 1 of the Writers Guide.
2. Upper and lower caso lettering is  !

used as shown in Figure 1 of the Writer's Ouide.

3 The title is brief and describes the purpono of the procedure.

B. Table of Contents contains the following:  !

l

1. Hender (4 linen - upper right) .
2. Proceduro Title (centered) . '

3 Colum n He ad er s.

t

4. Eh tr ies .

I. PUR POSE II. 8 YMPTONS i III. IMMEDIATE OPERATOR ACTIONS 1 V.

V.

FOLLOWU P OPERATOR ACTIONS ATTACHMEtCS

(( _

A TTACHM ENT 1 - TITLE 5 Corresponding pago ntsnbers for above.  ;

C. Procedure Body

1. Heador (each paso - 3 lines uppor righ t) . t
2. PAGE _ of (each pago - bottom) _

i l

SA P-207 ATTACHMENT III PAGE 2 0F 4 REVISION 0 YES g

^

,. I. PUR POSE

a. Section Title in correct centored. -
b. Statomont la brior, but clearly describoa the function of the proceduro.
4. II. 3 YMPTOMS
a. Section Title la correct (cen tored) .
b. All noceanary alarma, indications, operating conditions , and automatic system ac tions are included.
5. III. IMMEDIATE OPERATOR ACTIONS and IV. POLLOWU P OPERATOR ACTIONS
a. Soc tion Tition are correc t.
b. Stops are brier, and undor-standable.
c. Grammer and punctuation la correct (porloda at the end of all contoncoa).
d. Spacing betwoon linoa la correct.
o. Stop numbering in correct.
f. Stops are written no follows:

Ac t io n v orb - o bj ec t . _

g. Long, obscuro, or abstrac t words are avoided. _
h. Positivo auntonceu are used rather than negativos , whenover possible. _
i. If thoro are throo or more objecto ,

they are given in a list. _

j. Exac t nomenclaturo is in all capa. _

i

  • SA P-2 07 ATTAC}9 TENT III ;

. PAGE 3 OP 4  !

REVISION O llel E9.

k. Component ntanbers are included whenever possible. _ _, ,
1. Abbreviations are avoided, exonpt '

in exac t nomenclature. _

j m. System names aro in initial caps. _ _

i

n. Limits and tolerar.ces are ~

expressed quantitatively, CO. 935 psig (930-940).

o. Only approved abbreviations and I acronpis are used (see Writer's j i Guid e) .  ;
p. Greater than,'less than, and -

equal to are spelled out (not i sym bols) . _ _ j

q. The meaning of verbs is l consistent. _ _

l

r. Check-off lines are used in Pollowup Operator Ac tions. _ _
s. Conditional statements are correctly written (1[,. . . ggg). __  !
t. Appropriate words are underlined j (logic terms, ne denoting ntsnber)gatives, worda l

i u. Cautions and notes precodo the j applicable step and have namo 1

+

ntsnber as step. _

i

v. Cautions and noton are structured, and located as per the Writor's  :

Guid e . __ _

w. Cautions and notou do g contain t opera tor actions. _
x. Values are opooiriod whorevor 4

needed, coinputations are not i required. _ _

l

y. fleferenco doctanenta are identiriod by both titlen (all onpa - quotoa)

. and nunber. )

l 1 -

. SA P-2 07

,' ATTACHMENT III PAGE 4 0F 4 REVISION 0 YES NO

z. Referencing is appropriately used:
1) Does not route users past important information.
2) Us e s "go to" for b ranching.
3) Use s " refer to" for refe r enc ing.

D. Attac hments .

1. Header is correct (4 lines - upper r igh t) .
2. Title is in caps and centered.

~

3 All action steps meet requirements b-z in previous checklist sec tion.

All graphs , charts , and tab'les are

~

4.

easily read and interpreted.

5. Units of measurement are correctly giv en , Eg . f t/ se c .
6. At tac hments , tables , and figures are correctly numbered, 1, 2, 3, e tc.

INITIA LS : __

I 7 "" c =

SA P-2 07

.

  • ATTACHMENT IV PAGE 1 0F 2 REVISION 0 E0P TECHNICAL REVIEW CHECKLIST .

E0P NUMBER:

TITLE: -

Review the procedure for each of the following criteria. If the procedure meets a criterion, place a check on the line provided.

If the c riterion is not met, write "no" on the line. Write "NA" (not applicable), if the criterion does not apply.

1. The purpose statement b riefly and clearly s pecifies the f unction of the procedure.
2. If appropriate, s ymptoms are listed by importance or order of probable appearance.

3 sequence of steps is logical and accurate.

4. Text is compatible with operato r's viewpoint.

5 Steps are b rief, and easily understood.

6. All necessary steps are included.

7 There are no unnecessary steps or substeps.

8. Level of detail within steps is appropriate.

9 Within any given step, there is no uncertainty or conf usion as to which step to go to next.

10. Specific instrument references match control room or local labeling (numbers are correc t) .
11. Control, displays , and other equipment mentioned are available and located as specified.
12. Descriptions given match actual units of measure-ment , engineering parame ters , and f unction of control and displays .
13. Note s/Cauti'ons do no t contain opera tor ac tions (not ac tive command ste ps) .
14. Note s/ Cautions are appropriately located and easily understood.
15. All necessary Notes / Cautions are included. .

SA P-P 07 ATTACHMENT IV

  • PAGE 2 0F 2 REVISION 0
16. There are no unnecessary Note s/ Cautions .
17. Branching ( go to) and referencing ( refer to) instructions are correct.
18. References to othen . procedures give correct numbers and titles .
19. Exit conditions are compatible with the entry conditions of the referenced procedure.
20. The use of referencing is minimized.
21. Quantitative values , including tolerance bands ,

comply with E0P source documents.

22. Appropriate and correct quantitative values ,

charts, or tables are .provided, so that computations are no t required.

23. Check-off blanks are appropriately located.
24. Licensing commitments applicable to EO Ps have been addressed.

2$. E0P/ ERG differences have been documented and are justified.

26. Corrections marked on the procedure.

2 7. Disc repancies d ocunented on Attac hment V.

REVIEWER:

DATE:

. o SA P-2 07 l ATTACHMENT V

  • PAGE 1 0F 1 '

REVISION 0 l TECHNICAL REVIEW DISCREPANCY EOP NUMBER STEP NUMBER DESCRIPTION OF DISCREPANCY:

RECOMMENDED RESOLUTION:

l l

l TECHNICAL REVIEWER: _ DATE RESOLUTION:

ORIGINATOR: DATE i

i

s j SA P-2 07

  • ATTACHMENT VI PAGE 10F 1 REVISION 0 E0P VALIDATION FORM Page of E0P

Title:

E0P Number: Revision:

Scope of Validation:

Validation Method or Methods to be Used: ,

De signated Ob server /Re viewer ( s) :

Preparation Completed on By:

Assessment Completed on By:

Operator ( s) Involved : Qualific ation: (SRO, RO, Other)

Re solution Completed on By:

Docunentation Package Borwarded on

By

l I

i e

g\ .. {

l SA P-2 07

.- ATTACHMENT VII

  • PAGE 1 0F 1 REVISION 0 VALIDATION DISCREPANCY FORM I 1

E0P: REV.: STEP NUMBER:

DISCREPANCY:

EVA LUATOR : DATE:

RESOLUTION:

APPROVED: YES NO (circle one)

SUPERVISOR OF OPERATIONS: DATE:

RESOLUTION INCORPORATED BY: DATE:

1

I h4 6

~

, l SA P-2 0 7 ATTACHMENT VIII PAGE 1 0F 1 REVISION 0 SIMULATOR SCENARIO FORM PROCEDURE NO. : REVISION:

TITLE:

DATE:

PURPOSE: _ ,

SCENARIO DESCRIPTION:

INITIAL PLANT CONDITIONS:

SIMULATOR SEQUENCE (to be completed by the simulator instruc to r) :

EVENT TIM E MALFUNCTION NO. HR : MIN: SEC I/O OVERRIDE DESCRIPTION INTENT l

l l

l l

l