ML20087Q028

Procedures Generation Package

ML20087Q028
Person / Time
Site:	San Onofre
Issue date:	04/06/1984
From:	SOUTHERN CALIFORNIA EDISON CO.
To:
Shared Package
ML13309B395	List: ML20087Q028
References
RTR-NUREG-0737, RTR-NUREG-737 PROC-840406, NUDOCS 8404100225
Download: ML20087Q028 (66)

Text

i ,

L

.a

's PROCEDURES GEhERA110h PACKAGE SAN Oh0FRE huCLEAR GEhERAllht: STA110N

, UNITS 2 AND 3

\s  %

i t.'

t.,

1  !

/- g ( [., - l

/ ( , , t, i ii e.'-

• l i . ,' h .

,' L

, \ ,

5, y

'd ' ) \

', / *% >

i i '

N 'N.

,1 i

/ss

\

f

\

,(

, s

(,

l' ,

, s ,

,  ? ,

't

- i

[, N ,

,- 4 m

,s,

• i i .

)

+

,\, ' th i

,\ -( t-

i ,

840410C225 840406 PDR ADOCK-Q3000361 PDR i p i i

.? ' 's. -

\

o 8 17P. e _ ,

. -)

k' PROCEDURE 5 GENERATION PACKAGE CONTENTS Total Pages Part A OVERVIEW AND TECHNICAL GUIDELINES. . . . . . . . . . . . . 10 Part B EMERGENCY OPERATING INSTRUCTION WRITER'S GUIDE . . . . . . 31 Part C VAllDATION PROGRAM DESCkiPTION . . ............12 Part D TRAINING PROGRAM DESCRIPTION . ............... 2 l

L

6 sO

/

PROCEDURES GENERATION PACKAGE PART A OVERVIEW AND TECHhlCAL GulDELIhE5 i

!~

h-r k

t i

t t

k 3.

1 i .

). -

{.

r

~,

s a- + - . -- -. . - . .- . . . . . ,, _ , _ _ _ _ _ _ _ _ ,__

1:

e ob o OVERVIEW AND TECHNICAL'GUIDEllhES lABLE OF C0h1EhTS Section Page 1.0 lhlkODUC110h. . . ... . . . . . . . . . . . . . . . . . . . . . . .A-1 1.1 Purpose. . . . . . . . . . . . .-. . . . . . . . . . . . . .A-1 1.2 Scope. . . . . . . . . . . . . . . . . . . . . . . . . . . .A-!

1.3 Background . . . . . . . . . . . . . . . . . . . . . . . . .A-2 2.0 UPGRADE FROCESS . . .,. . . . . . . . . . . . . . . . . . . . . .A-3 L 2.1  ; Resources and Organization _. . . . .,. . . . . . . . . . . .A-3 2.2 Operating Instruction System . . . . . . . . . . . . . .

. . .A-3 2.3 ~ Process Description. . . . . . . . . . . . . . . . . . . . .A-4 2.4 Implementation anc Revision. . . . . . . . . . . . . . . . .A-8 3.0 T ECHNICAL GUIDELINES. . . . . . . . . . . . . . . . . . . . . . . . A-9 3.1 Introduction . . . . . . . . . . ..... . . . . . . . . . . .A-9 3.2 Description. . . . . . . . . . . . . . . . . . . . . . . . .A-9 LIST OF FIGURES

- Figure tu). Page

^

1 -Sequence Of Decisions For Off-Normal Operations. . . . . . .A c Overview Of The Emergency' Operation Instruction System . . .A '

-2

'3 E01 Upgrade Process. . . . . . . . . . . . . . . . . . . . .A-7 ,

+.

r 4

1 b

B k-e I  %

I

1. s - me.

E

, .o OVERVIEW AND TECHNICAL GU10ELINES 1.0 lhikODUCT10N 1.1 . Purpose The purpose of the Procedures Generation Package (PGP) is to provide a description of the process used to upgrade the San Onofre Nuclear Generating Station, Units 2 and 3 (SONGS 2 and 3) Emergency Operating Instructions (E01's). The process utilizes upgraded writin technical,E01's.

implement g, validation, and training bases to develop and 1.2 Scope 1.2.1 The E01 upgrade process is documented in response to item 7.2.b, Supplement 1 of huREG-0737, "kequirements for Emergency Response Capability," as committed to in SCE letter to Mr. D. G. Eisenhut from Mr. K. P. Baskin dated May 13. - 1983. The guidance presented in NUREG-0899,

" Guidelines for the. Preparation of Emergency Operating Procedures " was used in developing the upgrade process.

huREG-0899 provides guidance for determining that the requirements of Title 10 Code of Federal Regulations, Part 50.34(b)(6)(ii), have been met. NURE6-Ub99 also provides guidance on the recommendations of NUREG-0737, item 1.C.1

" Emergency Operating Procedures."

1.2.2 The E01's are based on CEN-152 Rev. 01, Combustion Engineering-Emergency Procedure Guidelines. The guidelines were determined to be acceptable tor implementation as stated in hkC letter D. G. Eisenhut to R. W. Wells, dated.

July 29, 1983. The letter transmitted the Safety-Evaluation (Report) by the Office of Nuclear Reactor Regulation in the Matter of Combustion Engineering Owners broup tmergency Procedures buidelines. lhe E01 upgrade does not attempt to resolve any open Safety Evaluation Report issues associated with'CEh-152 Rev. 01. As these issues are resolved, the LJ1's will be reviewed and revised

- as necessary to incorporate the resolutions.

1.2.3 Ongoing work by the hRC and its contractors'is continuously being reviewed by the Southern California Edison Company

! ($CE) and industry groups such as the Institute of. Nuclear Peter Operations (IhPO) for appropriate E01 incorporation.

1.2.4 Previous results of tasks relating to the Safety Parameter Display System; Regulatory Guide 1.97 Rev. 2,

" Instrumentation for Light-Water-Cooled Nuclear Power Plants to Assess Plant and Environs Conditions During and.-

Following an Accident"; and Detailed Control Room Design Review are not required to be addressed by this package.

However, these results are integrated into the design,

!- configuration, and operation of SONGS 2 and 3, and the E01's.

l A-1 t _ _

. e OVERVIEW AND TECHNICAL GU10EllhES 1.2.6 The parts of this package dealing with the Technical Guiaelines, Writer's Guide, Validation Program, ano Training Program were written as autonomous sections. This was done to facilitate subsequent incorporation, as applicable, into the station documentation system for aaministrative control purposes. The various PGP parts may be revised prior to incorporation into the station ao'cumentation system. This revision process is not intended to alter nor diminish the integrity of the oevelopment process. This would be done to improve directional clarity for the forthcoming revision process vice the completed upgrade process, to incorporate lessons learned in the execution of the upgrade program steps, etc.

1.2.6 The plant configuration for purposes of E01 development is considered to be that corresponding to the 50hG5 2 and 3 configuration.tollowing completion of the first refueling outage for Unit 2.

1.2.7 Input was obtained from Combustion Engineering (C-E) in the areas of technical guidelines, conversion to plant specific information, determination of safety significant deviations or additions to the guicelines and Justification for them, and review and verification of the E01's.

1.2.8 References stated in the Procedures Generation Package are current for the time of this submittal.

1.3 backgrouno San Onofre Units 2 and 3 E01's were initially developed consistent with the gui"aace of NUREG-0578, "TMl-2 Lessons Learnea Task Force Status Report and Short Term Recommendations." These E01's incorporated improvea analysis ana operator guidance for non-normal events. The basis information was supplied by the Combustion Engineering Owners Group (CE0G) in CEN-128, " Response of Combustion Engineering Nuclear Steam Supply System to Transients and Acciaents." best estimate analysis techniques were used.

l The guidance of NUREG-0578 was integrated into and expanded by hukEG-0660, "hRC Action Plan Developed as a Result of the TMI-2 Accident." NUREG-0660 task 1.C.1 was to conduct a short-term program of best estimate accident analyses and procedure revisions. Task 1.C.8 was to conduct " Pilot Monitoring of Selected Emergency Procedures for hear Term Operating License Applicants."

Task 1.C.9 was to conduct a long-term program of EDI revision to include improvea writing, engineering, and operational practicalities.

A-2

OVERVIEW AND TECHhlCAL GU10EllhES San Onofre Units 2 and 3 E01's were selected as part of the pilot review program. The E01's were revised to include improved emergency classification, prioritization of actions, place-keeping aids, and technical ano administrative features. The revisions were validated by walk-through on a simulator and in the control room.

NUREG-0737 " Clarification of TMl Action Plan Requirements," was issued to improve the recommendations of hUREG-0660. Item I.C.1 of huREG-0737 recommends that the events analyzed for E01 bases include multiple f ailures, that guidelines be prepared to communicate designer information to the procedure writers, and that the E01's include function oriented proceaures as well as the event oriented ones.

In response to item 1.C.1 of NUREG-0737 as clarified in Supplement 1, ano as required in item 7.2.b, this Procedure Generation Package is submitted. It integrates the efforts of the CEOG Emergency Procedure Guiaelines, CEN-152, key. 01; the Writer's Guide; and previous E01 efforts. Implementation of the first set of E01's generated as described in this package for Units 2 and 3 is scheduled to be complete prior to the return to power following the first refueling outage for Unit 2.

?.0 UPGRAVE PROCE55 2.1 Resources and Organization

$an Onofre Units 2 and 3 E01's will be initially upgraded by a multidiscipline team tamiliar with the development process and the plant, and consisting of licensed operators, design engineers, and contracted human f actors support. A multidisciplined group is necessary to maintain compliance with the requirements set forth in the Technical Guidelines, Writer's Guide, and Validation Program.

2.2 Operating Instruction System Operating instructions are divided into six groups. These are administrative, normal, surveillance, alarm response, abnormal, and emergency. E01's are entered whenever the reactor trips or needs to be tripped or a Safety injection Actuation Signal is initiated.

Emergency events chn be diviced into two kinds. For the first kino, the operator can ascertain the general type of the event by diagnosing its symotom set from control room indications and knowleage of the plant and recent operating history. For the events where an accurate diagnosis can be made, mitigating instructions are selected ano sequenced to strategically address that symptom set (e.g., LOCA, steam generator tube rs:pture). Since these types of events have been well analyzed and ur.derstood, it is possible to write the emergency instructions to optimize the A-3

T

'O. C-OVERVIEW AND TECHNICAL GUIDELihES recovery (i.e., minimize release of radiation, minimize system leakage, reduce risk of core damage, reduce post accident recovery time to full power, etc.).

In the second kind of emergency, the operator is unable to diagnose a recognizable symptom set f or the disturbance. This may be due to errors in symptom assessment by the operator, multiple failures in the plant, the occurrence of an event that has not been previously analyzed, or instrumentation failures which distort the symptom picture.

Emergency instructions provide guidance for both kinds of emergencies. Thus, when a reactor trip occurs or should occur, the operator can refer to an instruction which will provide a safe response whether or not a symptom set is identified. In this system, E01's written to treat specific symptoms are called Optimal Recovery Instructions. The E01 which provides guidance for undiagnosed events for which a reactor trip is required is called the Functional Recovery Instruction. Figure 1 illustrates the sequence of occurrences and decisions which lead to the relation of either an Optimal Recovery Instruction or the Functional Recovery Instruction.

The E01 system is illustrated in Figure 2. The Standard Post Trip Actions are performed following all required or activated trips to evaluate the status of each safety function (e.g., RCS inventory control, RCS pressure control) ano to provide immediate actions which can be quickly and easily performed to improve the status of functions in Jeopardy. Following the Standard Post Trip Actions, oiagnostic actions occur-in which the operator attempts to oetermine the symptom set corresponding to the type of event which is transpiring. Depending on the diagnosis reade from the symptom set evolving, the operator will select either an Optimal Recovery Instruction or the Functional Recovery Instruction.

- 2.3 Process Description The upgrading and revision of E01's is a process consisting of several steps. The process steps are: 1) establish a technical basis, 2) develop a writing method, 3) write the E01's, 4) validate

'the E01's, 5) train the operators to use the E01's, 6) implement the revised E01's. .The process is illustrated in Figure 3. .The process elements taken collectively are a description of the methods used to convert the generic guidelines to E01's, and L continuing through actual implementat.on of the E01's. The elements.are the CEOG Guidelines, the Writer's Guide, a description of the Validation Program, and a description of the Training

= Program. _The four elements are more fully described elsewhere in this Procedures Generation Package.

A-4

.. .o OVERVIEW AND TECHNICAL GUIDELIhES FIGURE 1 SEQUENCE OF DECISIONS FOR OFF-h0RMAL OPERATIONS NORMAL POWER OPERATION - SURVEILLANCE o

PLANT ABNORMAL NO .

~

CONDITIONS OR ALARM?

YES MULTIPLE PLANT N0 ALARM Bh0RMAL CONDITIONS RESPONSE OR ALARMS? INSTRUCTION YES IS ESF ACTUATION NO -

~

ABNORMAL  %

OR REACTOR TRIP INSTRUCTION REQUIRED?

YES CARRY OUT STANDARD POST TRIP ACTIONS SYMPTOMS P0lf:T TO NO  ; FUNCTIONAL  %

EVEhT SPECIFIC RECOVERY INSTRUCTION INSTRUCTION YES OPTIFAL REC 0VERY INSTRUCTION ADMINISTRATIVE OPERATING INSTRUCTIONS A-5

OVERVIEW AND TECHNICAL GUIDELINES FIGURE 2 OVERVIEW 0F THE EMERGENCY OPERATION INSTRUCTION SYSTEM h0RMAL POWER OPERATION v

REACTOR TRIP OR ESF ACTUATED OR REQUIRED lt STANDARD POST TRIP ACTIONS TAKEN TO MAINTAIN CRITICAL SAFETY FUNCTIONS u

DIAGNOSTIC OPTIMAL RECOVERY INSTRUCTIONS REACTOR TRIP RECOVERY

LOS5 OF COOLANT ACCIDENT RECOVERY j

STEAM GENERATOR TUBE RUPTURE REC 0.VERY STEAM LINE BREAK RECOVERY

LOSS OF FEEDWATER REC 0VERY

LOSS OF FORCED CIRCULATION REC 0VERY FUhCTIONAL RECOVERY INSTRUCTION A-6

'O :

OVERVIEW AND TECHNICAL GUIDELINES

. FIGURE 3 E01 UPGRADE PROCESS PROCES$ STEPS ELEMENTS SUPPORTING INFORMATION 1 1ECHNICAL BA515 CEOG Gul0ELINE5 ---C-E PLANT SPECIFIC Gul0ANCE

-- PREVIOUS lNSTRUCTIONS

-- OPERATING H15 TORY

-- STATION DOCUMENTATION CONFIGURATION

-- STATION FACILITIES CONFIGURATION

-- CEOG AND LICEN51NG ISSUES 2 WRITING METHUD kkITER'S Gul0E -- INPO WRITER'S Gul0E

-- WESTINGHOUSE WRITER'S GUIDE

-- HUMAN FACTORS CONSULTANT

-- ADMINISTRATIVE PROCEDURES

. 3 E01 WRITING -- CEOG Gul0ELINES' OPERATING-EXPERIENCE

-- WRITER'S GUIDE 4 VAL 10AT10N VALIDATION PROGRAM -- INPO VAL 10AT10N Gul0E

-- INP0 VERIFICATION Gul0E 5 TRAINING TRAINING PROGRAM -- CEOG LE550N PLANS

-- TRAINING MEMORANDA 6 IMPLEMENTATION ADMINISTRATIVE PROCEDURES A-7

m - ._

OVERVIEh AND TECHNICAL GUIDEllhES The writing of E01's is performed in the third process step. The writer is tasked with implementing the CE0G guidelines, the kriter's Guice, and operating experience thereby generating E01's.

The CEOG guidelines and supporting information identify the plant objectives to be met, the systems required, the required level of performance, the required operator' actions, and the strategy with which the actions are to be carried out.

The writer also identifies additional strategies, functions, tasks, ano analysis neeaed to prepare the E01's. The writer or writing team integrates the E01 process elements based on operating experience, writing methods, engineering, plant design features and operating characteristics. While integrating the process elements, the writer aads subsystem and component detail to the E01.

Finally, aaministrative requirements for emergency plant operation are incorporatea into the E01's.

2.4 Implementation and Revision E01 implementation as well as subsequent revisions will be accomplished in accordance with Aaministrative Procedure t

$0123-VI-1.0, " Station Orders, Procedures and Instructions -

Preparation, Revision, keview, Approval'and Publication," and S0123-VI-1.C.5, " Units 2 and 3 E01's - Preparation, Revision And Valioation." The first procedure celineates the method for indexing, preparation, review, approval and revision of station-accuments. The latter procedure, aeveloped from applicable PGP parts, provides amplifying direction specific to that portion of the-station document system consisting of the Units 2 and 3 E'Ol's.

Following E01 implementation, the Operations Procedure Group (OPG) will assume responsibility for the.E01's. Administrative controls used by the OPG to prepare, review and issue E01's as well as other operating instructions is containea in Operating Instruction

$023-0-37, " Operations Procedure Coordination." Items that may affect procedure revision are-forwarded to the OPG from a variety of sources. These sources include but are not limited to the following:

o -Amendments to the Technical Specifications o Amenaments to the Final Safety Analysis Report

o. Proposea Facility Changes

~

o Design Change Packages o ' Temporary Change Notices o- Revision requests submitted to OPG per 5023-0-35, "Use of Procedures" A-8 -

OVERVIEW AND TECHhlCAL Gul0EllhES o Venoor-supplied information o Procedure validation review comments in accordance with S0123-VI-12.0, " Procedure Validation" o Feeaback of operating experience o Review comments from Project Support, Engineering, Management, and Bechtel Power Corporation o Combustion Engineering Owners Group Configuration Control Procedure 50123-XIV-3.1, " Configuration Document Change Control" provides an additional source of input for OPG consideration. This procedure provides a system for identifying, recording, and monitoring completion of changes to identified documents resulting from physical changes to SONGS 2 and 3 and/or other Contiguration Documents.

Should the information received by the OPG indicate that an E01 revision is warranted, previously aiscussed Administrative Procedures 50123-VI-1.0 and 50123-VI-1.0.5 will be utilized in effecting the revision development and impicmentation.

3.0 TECHhlCAL GU10EllhES 3.1 Introduction Technical guidelines are documents that identify equipment or systems to be operated, and list the necessary steps to (1) mitigate the consequences of transients and accidents, and (2) restore safety functions. 'They represent the translation of engineering data derived from best estimate transient ano accident l

analyses into information presented in such a way that it can be used to write E01's.

3.2 Description San Onofre Units 2 and 3 will use the CEOG Gui' alines to upgrade the current E01's. The process usea to convert the generic guidelines to plant specific E01's is described in Section 2. The guideline information was implemented using the approach described in Section 12 of the CEOG Guidelines. Combustion Engineering performea'the following tasks for the initial upgrade of the E01's.

1. Determination of which guideline steps are compatible with SONGS 2 and 3.

2. Determination of plant specific values to be put into the guideline steps.

A-9

O' O OVERVIEW AND TECHhlCAL GUIDELINES

3. The ad11 tion of plant specific details to the guideline steps.

4. The adaition of plant specific steps to encompass ano address the systems and actions that are unique to SONGS 2 and 3.

5. The deletion or modificaton of generic steps that cannot be performed at SONGS 2 and 3.

6. The reworaing of generic steps to conform to SONGS 2 and 3 standard terminology.

7. The rearrangement of gencric steps to improve operator task efficiency provided the technical intent remains unchanged.

8. Determination of safety significant deviations or additions, and justification for them.

The results of these C-E tasks and writer review of these tasks is termeo C-E plant specific guidance on Figure 3. The plant specific guidance will be accumented by letter f rom C-E to SCE. Resolution of any comments pursuant to the C-E letter should be accomplished by the E01 upgrade team and a C-E representative. A memorandum to file should be prepared indicating the resolution of SCE writer comments on the C-E plant specific guidance.

The E01 initial upgrade team will augment the C-E plant specific guidance with balance of plant details, and will forward the supportive information for subsequent E01 revisions to the Corporate Document Control System and/or OPG file system.

1 t

A-10

e T

PROCEDURES GENERATION PACKAGE PART b EMERGENCY OPERAilhG lh51RUC110N WRITER'$ GUIDE

- - --- - - _ - _m. _ _ _ _ . _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ . _ _ _ _ _ _ _ _ _

6- - .

EMERGENCY OPERAllhG INSTRUCTION WRITER'S GUIDE TABLE OF CONTENTS-Section' Page 1.0' lhTR000CT10N. . . . . . . . . . . . . . . . . . . . . . . . . . . .B-1 1.1 Purpose. . . . . . . . . . . . . . . . . . . . . . . . . . .B-1 1.2 General. . . . . . . . . . . . . . . . . . . . . . . . . . .B-1 2.0 COVEk PAGE FORMAT . . . . . . . . . . . . . . . . . . . . . . . . .B-1 3.0 lh5TRUCT 10N PAGE FORMAT . . . . . . . . . . . . . . . . . . . . . .B-5 4.0 WRITihG INSTRUCTIONAL STEPS . . . . . . . . . . . . . . . . . . . .B-8

' 4.1 General. . . . . . . . . . . . . . . . . . . . . . . . . . .B-8 4.2 Level of Detail. . . . . . . . . . . . ... . . . . . . . . .B-9 4.3 Action Step Classifications and Sequencing . . . . . . . . .B-10 4.4 Cross-Referencing Within ana Among Procedures. . . . . . . .B-12

.4.5 Logic Statements . . . . . . . . . . . . . . . . . . . . . .B-13 4.6 Caution and hote Statements. . . . . . . . . . . . . . . ...B-15 5.0 MECHANIC 5 0F ST YLE . . . . . . . . . . . . . . . . . . . . . . . . . B- 19 5.1 ' Vocabulary . . ... . . . . ... . . . . . . . . . . . . . . 8-19 5.2 Abbreviations and Acronyms . . . . . . . . . . . . . . . . .B-19 5.3 $pelling and Hyphenation . . . . . . . . . . . . . . . . . .B-20 5.4 Punctuation. . . . . . . . . . . . . . . . . . . . . . . . .B-21 5.5 h ume r i c a l V a l u e s . . . . . . . . . . . . . . . . . . . . . . B 5.6 Calcu lati ons . . . . . . . . . . . . . . . . . . . . . . . . B-22 6.0 OPERATOR AIDS . ... . . . . . . . .:. . . . . . . . . . . . . . . .B-27

6.1 Figure Development . . . . . . . . . . . . . . . . . . . . .B-27 6.2 . Table Development. . . . . . . . . . . . . . . . . . . . . .B-27 6.3 ' , Fold-Out Pages . . . . . . . . . . . . . . . . . . . . . . .B-28 6.4 Place-Keeping Aids . . . . . . . . . . . . . . . . . . . . .B-29 6.5 Rotation of Pages. . . . . . . . . . . . . . . . . . . . . 8-29 6.6 Reducea P age s'. . . . . . . . . . . . . . . . . . . . . . . . B-29 6.7 Att ac hments . . . . . . . . . . . . . . . . . . . . . . . . . B-29 7.0. -T YP l h6 FORMAT . . . . . . . . . . . . . . . . . . . . . . . . . . . B-29 7.1 Page Arrangement . . . . . . . . . . . . . . . . . . . . . .B-30 8.0 REPRODUCTION AND DOCUMENT CONTROL . . . . . . . . . . . . . . . . .b-31 8.1 . Reproduction and Document Control. . . . . . . . . . . . . .B-31 I

l i

e

• EMERGEhCY OPERATING lh51RUCT10N WRITER'S GUIDE L151 0F FIGURE 5 Figure ho. Page 1 EXAMPLE COVER PAGE. . . . . . . . . . . . . . . . . . . . 8-4 2 EXAMPLE INSTRUCTION PAGE. . . . . . . . . . . . . . . . . .B-7 LIST OF TABLES Table No. Page 4-1 PREFERRED CONDITIONAL STATEMENT WORD (5) . . . . . . . . . .B-17 5-1 PREFERRED VERBS . . . . . . . . . . . . . . . . . . . . . 8-23 5-2 PREFERRED ABBREVIATIONS AND ACRONYMS. . . . . . . . . . . .8-25 i

l

EMERGEhCY OPERATlhG lhSTRUCTION WRITER'S Gul0E 1.0 1hTko00CT10N 1.1 Purpose The purpose of this document is to provide administrative and technical guioance for the preparation and revision of Emergency Operating Instructions (E01's) for San Onofre Units 2 and 3.

1.2 General As discussed in Part A, Section 1.2.5 of this package, the contents of this part of the PGP will be incorporated into the station document system. The current identification of this forthcoming document is Administrative Procedure S0123-VI-1.0.5,

" Units 2 and 3 E01's - Preparation, Revision and Validation."

2.0 COVER PAGE FORMAT Each E01 has a cover page (See Figure 1) originating from SCE form number, SCE 50-20-1. Information that is generally consistent with the guidance provided in Administrative Procedure 50123-VI-1.0, " Station Orders, Procedures and Instructions - Preparation, Revision, Review, Approval and Publication," is entered on the cover page form for the indicated purpose as follows:

2.1 SAN ONOFRE NUCLEAR GEhERATlhG STATION identifies the generating station within the Southern California Edison Company to which this document applies.

2.2 EMERGEhCY OPERATlhG lhSTRUCTION identifies the type of document within the system of station documents.

2.3 SO#-#

uniquely identifies the document by station, unit and type / sequence number for use and retrival purposes.

'l' EXAMPLE:

S_0[2-#

S an Onof re------------

U n i t 2 -----------------

Type / Sequence------------

2.4 UNIT #

identifies the unit to which the document is applicable.

B-1

a r

EMERGENCY OPERATING INSTRUCTION kkITER'S GUIDE

(:

\-:

~ 2.5 REVISION #

identifies the revision number.

I ~2.6 PAGE # OF #

identifies the page. number and the total number of document pages.

4 2.7 TITLE descriptive heading of the procedure scope.

2.8 EFFECTIVE DATE a date is entered..in the. space provided designating the effectivity of the document.

~

- 2.9 PURPOSE text area contains a narrative description of the procedure objectives followed by a line across the page.

2.10 < SYMPTOMS text area may include alarms, indications, operating conditions, automatic system actions, etc.', indicative of the conditions for which the E01 is intended.

2.11 PAGES CHANGED WITH THIS REVISION: (NEW,ALL,#) -

indicates.the document pages affected by this revision as follows:

- o' NEW - first publication of this document, o ALL -'every page of the document is affected by this

- . revision,.

o (#) - only the indicated page(s) are affected by this revision.- -

4

' 2.12 PREPARED'BY:

, .AUIHOK DAlt author signs and dates the document in the space provided prior-to final routing.

- 2.13 APPROVED BY:

. -(NAhl) DATE 1 MANAGER, OPERATIONS

• indicateo manager signs- and dates the document in the space

, provideo during the final approval routing.

A e

a

i

\

c 9-EMERGEhCY OPERAT1hG INSTRUCTION WRITER'S GUIDE 2.14 (Initials):(initials):(r) information entered by the word processor operator as follows:

(Initials): - author's initials in capital letters (initials): - word processor operator's initials in lower case letters

(#) - word processor document identification number B-3

e .*

. EMERGENCY OPERATING INSTRUCTION WRITER'S GUIDE FIGURE 1 EXAMPLE COVER PAGE SAN ONOFRE NUCLEAR GENERATING STATION EMERGENCY OPERATING INSTRUCTION SO#-#

' UNIT # REVISION # PAGE # OF #

E33333333333333333=3==E32===33333333333=33333=33333333=333333=333333333=333333:

TilLE k3333333333333333=333333=E=33333=33E===33333333=333=3E=E==3333333==333332323=3:

EFFECTIVE DATE PURPOSE

[. . . . . . . . TEXT AREA. . . . . . . .]

$YMPTOM$

[. . . . . . . . TEXT AREA. . . . . . . .]

PAGES CHANGED WITH THl$ REV1510N: (NEW, ALL, #)

4 PREPARED BY:

AUTH0k OATE c

APPROVED BY:

(NAME) DATE MANAGER, OPERATIONS (Initials):(initials):#

B-4

E O e EMERGENCY OPERATING INSTRUCTION WRITER'S GUIDE 3.0 INSTRUCTION PAGE FORMAT

-Each E01 instruction page (See Figure 2) originates f rom SCE form number SCE 50-20-2. .Information from the cover page (2.1.1 through 2.1.7) as well as instructional direction in a two-column format is entered on the instruction page as follows:

3.1 The left-hand column-is entitled ACTION / EXPECTED RESPONSE (A/ER).

o The A/ER text contains the action steps to be taken and/or the. response which should be obtained af ter completion of the steps.. The action steps consist of top-level and sub-level statements.

o The top-level portion of the action step directs broad actions. The statement begins with a capitalized action verb followed by text in which the first letter of each word is capitalized. .The text is underlined and ends with a colon.

o The sub-level portion of the action step directs specific

. tasks. The statement begins with the first letter of the first word capitalized followed by text.

o When a desired action or response is not obtained, the operator looks to the right-hand column for further direction.

3.2 The right hand column is entitled RESPON5E NOT OBTAINED (RNO).

o The RNO text contains the contingency action steps to be taken if an ACTION / EXPECTED RESPONSE is not obtained. The need for contingency action occurs in con. junction with tasks involving verification, observation and confirmation.

o RN0's should be specified for each circumstance in which the A/ER might not be achieved. RN0's should provide appropriate-

. directions to override automatic controls and to initiate

-manually what is normally initiateo automatically.

O At the completion ~of the RNO step or substep, the operator

> yreturns to the A/ER column and proceeds with the next step or substep, as appropriate, unless specifically directed to

'another point.

9

'B-5.

.c .

EMERGENCY OPERATlhG lh5TRUCT10h WRITER'S Gul0E 3.3 Action steps are identified by Arabic numerals aligned under the STEP heading.

O Sub-level statements are identified by lower case letters, aligned under the top-level statement. The same lower case letters identify corresponding sub-steps in both columns.

For example, sub-step "c." in the right hand column is the contingency action for sub-step "c." in the left hand column.

o When multiple left hand column, A/ER sub-steps exist, and the right hand column, Rh0 sub-step (s) are applicable to all the A/ER sub-steps, the RhD sub-step is not rewritten for each A/ER sub-step, but is written only once, and identified with a bullet (o).

B-6

(O e-EMERGEhCY OPERATING INSTRUCTION WRITER'S GUIDE FIGURE 2 EXAMPLE IN51RUCT10N PAGE SAN ONOFRE NUCLEAR GENERATING STATION EMERGENCY OPERATING INSTRUCTION 50#-#

. UNIT # REVISION # PAGE # OF #

E33333333333333333333333333333333333333333333333333333333333333333333333333333="

TITLE E333333333333333333333333333333333333333333=33333333333333333333333333333333333

-d $1tP F--d AC110N/EXPECIED RESPONSE F------4 RESPONSE NOT 081AINED F---

---

A/ER Text --------,

r------- RNO Text --------

h/ \/ h/ h/

[ Example Action Step with-RNO f or A/ER sub-step c.]

1. ' (. . Broad Action Text. .)i <(-----Top-levelstatement

a. (. . Specific task text. .). ({-----5ub-levelstatement

b. (. . Specific task text. .).

c. (. . Specific task text. .).- c. (. . Contingency action

text . .)

[ Example Action 5t'ep with RNO for all A/ER sub-steps.]

~

1. (. . broad Action Text. .):

a. (. . Specific task text. .). o (. . Text . .)

b.

C.

B-7 L . 3

'6 -.

EMERGENCY OPERATlhG lh5TRUCT10N WRITER'S GUIDE

. 4.0 WRITlhG lh5TRUCT10hAL STEP 5 4.1 General Instruction steps should be short and exact.- The following general rules should be used to meet these objectives:

o Instruction steps should deal with only one idea.

4 o Short, simple sentences should be used in preference to long, compound, or complex sentences.

o Complex evolutions should be prescribed in a series of steps, with each step made as. simple as practicable.

o Objectives of operator actions should be specifically stated, that is, identify exactly that which needs to be done, and to what..

o The objects should be listed for instructional steps that involve an action verb relating to three or more objects.

o Limits should be expressed quantitatively whenever possible.

o Expected results of routine tasks need not be stated.

O When actions are required based upon receipt of an annunciated alarm, the alarm setpoint should be listed for ease of verification.

O When directing an operator to any type of signal, the expected results from reset of the signal should be listed if it would be beneficial to the operator.

o When system-response dictates a time frame within which the instruction must be accomplished, prescribe that time frame.

However, when possible, avoid using time to initiate operator.

actions. ,0perator actions should be related to plant parameters, o When additional confirmation of system response is considered necessary, required backup readings should be prescribed.

1

, B-8

. o l l

EMERGENCY OPERATlhG lh5TRUCT10h WklTER'S GUIDE 4.2 Level of Detail Too much detail in the E01's should be avoided in the interest of being able to effectively execute the instructions in a timely manner. The level of detail desired is that amount a newly trainea and licensed operator would need during an emergency condition. The following general rules should be used to meet this objective; o for control circuitry that executes an entire function upon initiation by the control switch, use the action verb appropriate to the component without further amplification of how to manipulate the control device. Recommended action verbs are as follows:

For power-driven rotating equipment, use Start, Stop For valves, use Open, Close, Throttle Open, Throttle Close, Throttle.

-- For power distribution breakers, use Close and Trip.

o Jor control switches, use the verb " Select" along with the engravea name of the desired pusition fully capitalized.

EXAMPLE: Select LOCAL on the diesel generator )

Mode $ elector Switch.

o 5tandard practices used to observe abnormal results need not be prescribed within procedural steps. For example, observation of noise, vibration, erratic flow, or discharge pressure need not be specified in steps that start pumps.

o Equipment, controls, and displays should be identified in operator language (common usage) terms. These terms should be the same as the panel engraved names.

-- If the component is seldom used, or if the component woula be difficult to find, location information should be given in parentheses following the identification or represented in a plant arrangement drawing.

B-9

e .

EMERGENCY OPERATlhG lh51RUCT10N WRITER'$ GUIDE 4.3 Action Step Classifications and Sequencing 4.3.1 Action steps are classified as either immediate or subsequent as follows:

o Immeaiate action steps are those taken without delay when there are indications of an emergency. These actions are taken to: 1) ensure automatic systems are stabilizing the plant and mitigating degraded events, and 2) as a means to evaluate the situation. Operators normally memorize these actions and refer to an E01 to confirm that they were performed. These steps should neither direct the operator to, nor reference another procedure. Immediate actions are found only in the

" Standard Post Irip Actions" E01.

o Subsequent action steps form the major body of instructional steps within the E01 set. These actions are taken to return the plant to a stable or safe steady-state condition.

4.3.2 Action steps should be sequenced according to CEOG Guidelines. The physical layout and staffing organization of the control rcom is an important consideration in sequencing tasks for optimal staff movemen.t and monitoring when performing action steps. The administrative controls associated with operator staffing and movement as contained in Station Order 5023-0-4, " Station Operation," and Administrative Operating Instruction 5023-0-14, " Shift Manning," should be considered in the action step development process. In developing instructional direction, the writer should utilize the following types of steps and associateJ rules to meet the objectives:

o Action steps may contain conditional statements that consist of conditicu word (s) with a specific parameter or object. These steps specify appropriate plant conditions that permit the operator to assess the effectiveness of action steps and their tasks as well as to determine the progress in mitigating the emergency.

The condition word (s) are highlighted for operator recognition with emphasis achieved by hyphenation, spacing and capitalization.

EXAMPLE: Check CET's - LES$ THAN 7000 F.

The volume of conditional statement words should be limited so as to obtain uniformity in their usage and meaning as well as action step execution. See Table 4-1 at the end of this section for a list of preferred conditional statement word (s) that should be used.

B-10

a s EMERGENCY OPERATihG INSTRUCTION WRITER'S Gul0E o honsequential steps are those performed strategically anytime the specified condition (s) exist. Within the CEOG guideline system, these steps are termed floating steps. For ease of access and use, these steps are positioned together with a unique step identification, e.g., F5-1, FS-2, etc. These steps should conform to the formatting of other action steps. Direction for the use of floating steps should be contained within the body of the E01.

EXAMPLE: Implement floating steps as applicable, o Recurrent steps are those that require the operator to repeatealy perform a given action, typically, monitoring or controlling some plant parameters. For these steps, the operator should be told when or how often the steps are to be performed, be reminded to perform the steps, and be told what conditions for which the steps should no longer be carried out.

To implement this activity, consideration should be given to existing forms of recordation for the parameter of interest, e.g., plant computer, control room recoraers, etc. To ensure timely monitoring, computer entry information should be provided, e.g., page number, point identification number, etc. Trending activity results should be provided in an attachment.

To obtain uniformity in usage and meaning as well as action step execution, the word " monitor" should be used in the step.

EXAMPLE: Monitor Safety function status per Attachment 1.

o Time-dependent steps are those that are required of the operator at some specified time interval, or some time after another action has taken place. Development of these steps should consider the control room staff capabilities to execute them and should only be used as required.

Upon entering the E01 set, selected timing information should be recorded in the Standard Post Trip Actions E01 for future use throughout the event. Space for recordation of timing information should be provided with the action step.

23===333333 EXAMPLE: Record The Time:

323==33333:

The use of operator aids such as checklists or graphs should also be considered when developing these steps.

B-ll

s: ; - -- - ._. ..

5

~~

y v.

, 1,

,l , . < A L ,

,' 4

. .- (, (= ,

- 4 EMERGENCY OPERAT)hG lh5TRUCT10N WRITER'S GUIDE i

4 .c 3

1 ~

i #

o' Concur'reth stepsjre those which should be performed in

%, parallel witt other actions. The text should explicitly

' 'j/\' indicate thich ste9s are concurrent so that operators <

can easily refertt'o both (or all) sets of steps.

O Development of thes'. steps should consider the control y y*oom staff capabilit3es to execute them.

y ,

Toobtain;uniformitknusageandmeaningaswellas ij/

action step execution, the wora " implement" should be j ,, used in the step.4

' " J EXAMPLE: Implemc.)tFS-5. .

') o Olagnostic steps are tho'se which should assist the

~

operator in diagnosis, and proside clear and unambiguous

, guicance leading to the diagtmstic decision, as well as clear and unambiguous referencing to the appropriate .

section of the E01 or to another E01. These steps may include the use of flow diagrams, graphs or other operator aids.

f Consideration shou b be given to the development of

diagnostic steps similar in' style and content te the format examples illustrated in the CEOG Guidelin0s and in the current E01 Yet. The step cid(s) should be sized such that it confoiFras to the space limitations of an

instruction pa M However, the fola-out page may also be.usedasnecessa]ryforthedisplayofthistypeofaid.

o The developinent of. action steps should not be directive by job title. ' ffenvfri wren the need arises to provide this type of direction',j the job title should be incorporatedintd)heactionstep.

EXAMPLE: Direct the Cominon Control Operator to l start the diesel generators.

L' 4.4 Cross-Referencing Within and Among Procedures Information necessary.to perform a task should be consolidated in one place, if possible.NThe r. ecd to go f rom one procedure (or part) to another during a sequence of. actions is disruptive and can cause errors or unnecessary delays. Consequently, once the

. sequence of actions has begun they should continue.without.

interruption. When the expected sequence of actions in the A/ER column 1s disrupted, the cperator enters the Rh0 column for ladditional direction. Th'erefore, the bulk of cross-referencing

' occurs here in'an effort to fully apprise the operator of alternative actions. Jhe cross-referencing actions may require

, thy operator to skip Att.ps, return, to an earlier step, go to

^

- Spother instruction, oV perform a step or instruction in parallel tith the step being per'fcrmea. The following rules should be utilized when the neeA for cross-referencing occurs:

> i

, 'w j L' 4 0h.12

^ '

1 , l

EMERGENCY OPERATihG lhSTRUCT10h WRITER'S GUIDE o Cross-referencing to other steps or instructions from the A/ER column should be avoided unless the direction to do so appears as the last A/ER step.

o The Rho cross-referencing direction should be positioned in the'last line of text.

o When cross-referencing to another step within the E01, it is not necessary to utilize the term "of this instruction."

o Direction to a step should be' positioned such that the word step and corresponding identification information are on the same line of text.

o Direction to another instruction should contain the document identification information as well as the title fully capitalized.

o Inunediate action steps should neither direct the operator to, nor reference another procedure.

4.5 Logic Statements 4.5.1 The logic terms AND, OR_, NOT, E WHEh, and THEN are often necessary to describe precisely a set of conditions or sequence of actions. When logic statements are used, the logic terms should be highlighted so that the conditions are clear to the operator. Emphasis is achieved by capitalization, underlining, and positioning.

EXAMPLE: E (. . text . . NOT . . text . .),

THEN (. . text . .).

4.5.2 When action steps are contingent upon certain conditions or combinations of conditions, the step should begin with the woras E or WHEN followed by a description of the condition followed by the action to be taken.

o E is used for an unexpected but possible condition.

o WHEN is used for an expected condition.

o The logic word THEN should not be used at the end of an action to instruct the operator to perform another-action within the same step, because it runs actions together. Actions which are embedded in this way (1) {

may be overlooked and not be performed, (2) make it  !

difficult to verify the performance of each action step i and, (3) can be confused with a logic statement. l n' EXAMPLE: Verify all 51 accumulators are  ;

(Bad Practice) isolated, THEN cooldown pressurizer. l with auxiliary spray.

. I 6-13 I

i

/

EMERGENCY OPERATING INSTRUCTION WRITER'S GUIDE r

4 14.5.3 When attention should be called to' combinations of

~

-conditions, the word AND should be centered;between the description of'each conoition.

EXAMPLE: (. . . Description Text . . .)

AND

(...bescriptionText. . .)

1 o in order to simplify a-long sequence of conditions, the woro AND should not be used to join more than f our

, conditions. If more than-four cond[tions need to.be joined, a list format should be'used. .

EXAMDLE: IF all of the following conditions are met,

(. . Condition 1 Text . .)

(. . Condition 2 Text . .)

, (. . Condition 3 Text . .)

(. . Condition 4 Text . .)

(.4 Condition 5 Text . .)

, THEN (. . ., Action Text . . .)

0 When used as a simple _or compound conjunction, the word-

"and" need not be emphasized (e.g., to connect actions

.in a step, as in: "stop low-head 51-pumps and place them 1 19 standby").

4.5.4 hhen' attention should be called to alternative combinations (of conditions, the word OR should be centered between the-

~

description.of'each condition.

s ,

)

o The use of'the word OR','for' conditions, should be in the-inclusive sense, 1.i77 any one or all conditions may be

-present. .

gg a .

/, o- Fce alternative actions, the'use of"0R should be

' 3 3 minimized and priorities'should be established where i r' ' possible. If priorities.cannot be established, and

• alternative actions are equally acceptable, then it is! '

/ .necessary to specify the exclusive "or"'.

EXAMPLE: 5t'ArteitherApump0][Bpump,butnot both.

e b

. < }

r > .

, ;f . a B-14

_,-_ 1 ,

'k .. 1

2 p: ,W EMERGENCY OPERATING INSTRUCTION WRITER'S Gul0E 4.6 Caution and Note Statements 4.6.1 Cautions o Caution statements should contain information used to prevent actions which could injure plant personnel, damage equipment, or endanger public health and safety.

The following. general rules should be considered in developing cautions:

The text should be accurate and concise.

-- The text should_contain only information relevant to the caution.

-- The text should not contain operator actions.

o Highlighting the caution statements ensures the. operator will. observe the caution before performing the step (s).

The following general rules for formatting should be used to meet this objective:

-: Cautions which apply to the entire instruction should be positioned on the first instruction page before the first action step.

-- Cautions that refer to action step (s) should be positioned immediately before the step (s) and on the same page.-

-- The caution text is positioned within a double

-lined box, centered on the page. The left and-right box borders should be approximately one inch from the page borders. The top and bottom box border dimension is determined by the text volume.

-- -The word " CAUTION" is positioned within the box, centered, capitalized and unde'rlined with two broken lines.

EXAMPLE:

s CAUTION

=

(. .-. . . . . Text. . . . . . .)

I' B-15 o

.iMER6ENCYOPERATlh6lhSTRUCTIONWRITER'SGUIDE 4.6.2 -hote Statements o Note statements _ remind operator (s) of supplemental information such as correct sequence. The following general rules should be considered in developing notes:

The text should be accurate and concise.

The text should contain only information relevant to the note.

-- The text should not contain operator actions.

O Highlighting the note statements ensures the operator will observe the note before performing the step (s).

The following general rules for formatting should be

-used'to~ meet this objective:

-Notes which apply to the entire instruction should-be positioned on the first instruction page before the first action step.

-hotes that refer to action step (s) should be positioned immediately before.the step (s) and on the same page.

The note text is positioned within a single-lined box, centered on the page. The' box border

. dimensions are~ determined by the-text volume.

-- The word " NOTE"'i_ positioned within the box to the left of the first line of text, capitalized and followed with a colon.

EXAMPLE:

NOTE: (. . . Text . . .)

g.

$?

~

B-16 L'---

d{'_ -

l 1

s o EMERGENCY OPERATlhG INSTRUCTION WRITER'S GUIDE TABLE 4-1 PREFERRED CONDITIONAL STATEMENT WORD (S)

PREFERRED WORD ($) DEFINITION AT PRESET POSITION - pre-established position, e.g., AFW control valves positioned for automatic operation. .

AL'TO . - system functions without manual action.

AVAILABLE -

a system, subsystem, train, component, or device will operate and can be used as desired; however, it need not be operating.

bYPAS$ - a switch position to defeat a signal from initiating some further action, or the condition which results from manipulation of the switch.

CLEAR - annunciator is not alarming, or is able to be reset.

CLO5ED - fully shut; for a breaker, means power is going to' the component.

GREATER THAN -

of larger magnitude.

IhlTIATED - system or component is functioning as a result of meeting some start criteria.

lh5ERTED - fully in piace, e.g., control. rods fully inserted.

LESS THAN~ - of less magnitude.

LOWERlhG - becoming less in magnitude.

OFF/0N - switch positions to supply or remove power.

OPEhED - fully open; for a breaker, means no power going to the component.

B-17

EMER6ENCY OPERATlhG lhSTRUCTION WRITER'S GUIDE TABLE 4-1 (Continued)

PREFERRED CONDITIONAL STATEMENT WOR 0(S)

PREFERRED WOR 0(5) DEFINITION OPERABLE - a system, subsystem, train, component, or. device is capable of' performing its specified function (s) in the intended manner. Implicit in this definition is the assumption that all necessary attendant

. instrumentation, controls, norn.al and emergency electrical power sources, cooling or seal water, lubrication or other auxiliary equipment required for the system, subsystem, train, component, or device to perform its function (s) are also capable of performing related support function (s).

OPERATlhG - a system, subsystem, train, component, or device is in operation and is performing its specified function (s).

- 0VERRIDE - a switch. position which results in signal interruption to a component, thereby permitting manual operation of that component, or the condition which results from manipulation of that switch.

POWERED - energized electrically.

RESET - breaker or control' circuit repositioned to prepare for future operation.

. RISlhG - raising or becoming greater in magnituda..

STABLE - condition that is not deviating significantly.

f TREh01hG TO - parameter rising or lowering in a controlled manner to a stated value.

B-18 .

- W -

4

.) .

EMERGENCY OPERATING' INSTRUCTION WRITER'S GUIDE

-5.0- MECHANICS OF STYLE 5.1- Vocabulary The simplest, most familiar, and most specific words that accurately convey the intended meaning-should be useo. Operators should understand all words used in the procedures.- To achieve e this overall objective, the following guidance should be followed:

o Use short words that are common in ordinary conversation.

o Use simple well-defined words.

'o Use words and meanings consistently throughout the instructions.

~

o Use words with unambiguous meanings.

o Use concrete and specific words that describe precisely what the operator is to do or-observe.

o: Use_ nomenclature and idioms that the operator is trained to use and which are standard in the nuclear. power industry.

o Use words which are familiar to control room operators.

O Use units of measure that are familiar to the operator. The operator should be able to relate the units to those referenced on plant instrumentation without conversion, translation or mental manipulation.

O Avoid using adverbs that are difficult to define in a precise manner (e.g., frequently, slowly).

o- See Table 5-1 at the end of this section for a list of preferred verbs that should be1used.

5.2 Abbreviations And Acronyms The use of abbreviations and acronyms should be' minimized as they

~

, ~

-may be confusing to'those who are not thoroughly familiar with them.- They may be used where necesary foritime and space considerations provided their meaning is clear to the operator without the use of a glossary. The.following general rules should be used'to meet this objective:

o Where' applicable, use the same abbreviations and acronyms as-

marked on1 equipment.'

B-19 i

r - , , - - - , y * - - - , - -

w

' EMERGENCY OPERATING INSTRUCTION WRITER'S GUIDE

.t 5.2' Abbreviations,And Acronyms (continued) o- Uniformly capitalize abbreviations and acronyms. Omit the periods except in cases where the omission might result in confusion.

o' . Pluralization of abbreviations / acronyms should be accomplished by following the last letter with an apostrophe and then a lower case letter "s".

o See Table 5-2-at the end of this section for a list of preferred abbreviations and acronyms.

^ '

5.3 Spelling And Hyphenation 5.3.1 Spelling should be consistent with modern usage. When a choice of spelling is offered by a. dictionary, the first-spelling should be used.

5.3.2 The following. rules should be used for hyphenation:  !

o Hyphens.should.be used between elements of,a compound word when usage calls for it. WhenLdoubt exists, restructure'the compound word to avoid hyphenation.

o+ In compound numerals from twenty-one to ninety-nine o In fractions; e.g., one-half, two-thirds o in compounds with "self";.e.g., self-contained,

.self-lubricated o When the last letter of the first word is the same vowel as the first letter of the second word. .As an alternative,-use two words; e.g., fire-escape or fire escape o LWhen misleading or awkward consonants result-by joining the words; e.g., bell-like o To avoid confusion with another word; e.g., re-cover to avoid confusion with recover, pre-position to avoid confusion'with preposition ~

o--When a letter is linked with a noun;.e.g., X-ray, i

. 0-ring. U-bolt, beam -

~

- o4 To separate chemical elements an'.their d atomic weight; e.g., Uranium-235, U-235 B .

_,m., ._ - - _ _ _ - - _ - - - - - - _ _

.. =

EMERGENCY OPERATING INSTRUCTION WRITER'S Gul0E

~ 5.3.2 (continued) o A hyphen with a space on both sides is utilized for

' ~

emphasis in conditional statements (See 4.3.2).

J o A hyphen should not be used in front of a number where it could be confused as a minus sign, e.g., -5" 5.'4 Punctuation The rules of punctuation for standara American English should be I used as necessary-to aid reading and to prevent misunderstanding.

Punctuation helps'to reveal the precise relationship among thoughts'ano communicate the writer's intention. Accordingly, consistent and proper use of punctuation will lessen the chances that operators might misinterpret what the writer intended to say. .The following general rules should be used to meet this objective:

o Text should be selected to require a minimum of punctuation.

When extensive punctuation is necessary for clarity, the text should be rewritten.

o A colon shoula be-used to end all top-level statements, and to indicate that a list of-items follows.

O Commas should be used to separate instruction designators from the instruction title.

EXAMPLE: S02-#, LOSS OF COOLANT ACCIDENT.

O A hyphen with a space on both sides is utilized for.-emphasis in conditional statements (See 4~.3.2).

O A hyphen should not be used in front of.a number where it' could be confused as a minus sign, e.g., -5%.

~ ~

-5.5- Numerical Values

.The use of numerical values should be consistent with the following rules: .{

I o Arabic numerals should be used. j o For numbers less than one, the decimal point should be preceded by a zero. l 1

-o -The number of significant digits should be equal to the number of significant digits available-from the display and the reading precision of the operator.

i

~

b -

^

. , , , e EMERGENCY OPERATlhG Ih5TRUCTION WRITER'S GUIDE 5.5- humerical Values (continued)-

o Units of measure should-be specified for numerical values of process variables. They should be the'same units used on the control room displays, e.g., use-PSIA instead of PSI.

o References to partial-hour time limits in time dependent steps shoula be expressed in fractional from. Write out fractions as hyphenated numbers.

EXAMPLE: 1-1/2 Hours, NOT 1.5 Hours 0 Acceptance values should be.specified in such a way that addition and subtraction by the user'is avoided if possible.

This can ge'nerally be done by stating acceptance values as limits, thereby avoiding'use'of. the symbol +.

EXAMPLE: Between 31% AND 35%

o humerical values from twenty-one to ninety-nine as well as L

fractions should be hyphenated when written out.

o. The numerical value and associated unit of measure should be positioned on the same line of text.

~

o A. hyphen should not'be use'd in front of a number where it.

could be confused as a minus sign, e.g., -5%.

5.6 Calculations The operator's use of formulas and need for calculations within a the.E01's should be minimized because of the time they require and D- because they increase the possibility of operator error. .T he .

following general rules should be used to meet'this objective:

.o -When calculations are1 required they should be as simple as possible, and space should be provided for the calculations.

o' Consideration should be given to utilizing a chart or graph in lieu of a calculation.

I e

2 B-22

EMERGENCY 3PERATlhG lhSTRUCTION WRITER'S Gul0E TABLE 5-1 PREFERRED VERBS PREFERRED VERB DEFINITION ALIGN - To arrange a system for operation, or to adjust an electronic system to a set of standards.

ATTEMPT TO - To make an effort to do.

CHECK -

To determine what condition exists. Implies any of the conditions described could be expected.

CLOSE - For. valves, to position fully shut; for electrical devices, to make a connection to a power supply.

DEPRE55 -

To press down.

ENSURE - To verify a specified condition exists, and if it does not, to manually take the necessary steps to establish the condition.

ESTABL15H -

To take the necessary steps to obtain the desired condition.

' EVALUATE - To assess conditions based upon observations, outside inputs, and experience.

GO TO - To leave this instruction step and follow referenced instruction until directed back to this or another instruction.

IMPLEMENT - To place an instruction into effect in parallel with this instruction.

150 LATE - To set apart or separate from a system in use.

1 LOCALLY - To take an action outside the control room.

LOWER -

To reduce in magnitude.

MAlhTAlh - To keep in a certain condition or position.

B-23 L:-_ _

EMERGENCY OPERATING INSTRUCTION WRITER'$ Gul0E TABLE 5-1 (continuea)

PREFERRED VERBS

' PREFERRED VERB DEFINITION MONITOR - To observe for conditions or trends.

OPEN - For valves, to position for full flow.

RAISE -

To increase in magnitude.

RECORD - To write down manually or via an automatic device.

RE-EVALUATE - To evaluate again.

RE$ET - To reposition a breaker or control circuit for future operations.

SELECT - To manipulate controls or switches to a desired condition.

START - To perform actions necessary to set into operation.

$ TOP - To cause to cease operating.

' TERMINATE - To bring to an end; to stop.

THROTTLE - To position so as to limit flow to less than full.

TRAN5FER - To shift electrical or fluid supply from one source to another.

TRIP - To bring to an abrupt and complete ceasation; to manually activate a semi-automatic feature, or to open an electrical breaker.

VERIFY - To confirm that an expected condition exists.

B-24

.; = m;

. EMERGENCY OPERATING INSTRUCTION WRITER'S GUIDE TABLE 5-2 PREFERRED ABBREVIATIONS AND ACRONYMS A6BREVIATION/ ACRONYM DEFINITION.

ADV - Atmospheric Dump Valve AFW - Auxiliary Feedwater CET - Core Exit Thermocouple CIAS - Containment Isolation Actuation Signal CSAS - Containment Spray Actuation Signal EFAS - Emergency Feedwater Actuation Signal 0F - Degrees Fahrenheit FR - Functional Recovery FS. - Floating Step GPM - Gallons Per Minute HPSI High Pressure Safety injection LOCA - Loss of Coolant Accident LOF -

Loss of Feedwater LOFC - Loss of Forced Circulation

.LVL - Level

.MFIV - -

Main Feedwater Isolation Valve MSIS - Main Steam Isolation System MSIV- - Main Steam Isolation Valve PSIA - ' Pounds Per Square Inch Absolute PSIG -

Pounds Per Square Inch Gauge PZR - Pressurizer' e

g.

.: B-25

6' s *-#

EMERGENCY OPERATlhG lh5TRUCT10N WRITER'S GUIDE TABLE 5-2 (continued)

' PREFERRED ABBREVIATIONS AND ACRONYMS ABBREVIATION /ACR0hYM - DEFINITION RAS - Recirculation Actuation Signal RCP - Reactor Coolant Pump RCS' - Reactor Coolant System RTR - Reactor Trip Recovery RW5T - Refueling Water Storage Tank 5BCS - Steam Bypass Control System

$DC. - Shutdown Cooling S/G - Steam Generator SGTR - Steam Generator Tube Rupture

$1 -

Safety injection

.SlAS. - Safety injection Actuation Signal SIT - Safety injection Tank .,

$LB - Steam Line break 50 -

San Onofre SPTA - Standard Post Trip Actions T .

Temperature - as used in Delta T Tave - Average Temperature

, TSC - Technical Support Center o

B-26

- _ - - - - ---------,----,-_-----__--_--_-____--_--_----_a- - _ _ _ - - - - - - - - - - - - - - - --

. - =

-EMERGENCY OPERATING INSTRUCTION WRITER'S GUIDE'

- '6.0 OPERATOR AIDS 6.1 Figure Development Figures may include graphs, drawings, diagrams, illustrations, flowcharts and decision aids. These aids should be self- "

explanatory, legible, and readable under..the expected conditions of use and within the reading precision of the operator. The following rules should be considered in figure development.

o- Capitalization should be used for references to figures 'and f their titles within text material.

o' Sequential arabic numbers should be assigned to figures. The sequence should correspond with_the order of their reference in the text. The symbol "#" and abbreviation "No." are

. unnecessary and should not be used. .The number alone suffices.

EXAMPLE: Figure 1, Figure 2, etc.

o Figures should_be located on the page following their reference where practicable. Commonly used~ figures should be located following the end of the action steps.

- 0 The figure number.and title should be centered above the figure using standard station word processing equipment.

O The figure shoula be positioned within the page margins.

o The figure should be of sufficient size to offer good readability..

o The figure presentation should be clear and simple.

o Typed labels with arrows;should be used.to identify items within the figure. Handwritten labels should be printed,

-using all capitals,.with letters and numbers at least 1/8-inch high.

o Figure elements should'be oriented naturally. For example, height on a graph should be along the vertical axis.

6. 2' Table Development The following rules should be considered in table development.

o Capitalization should be used for references to tables and their titles within text material.

B-27

.c

. . . ~ , ,.~,,m,, . , . , _ ,

EMERGENCY OPERATlhG INSTRUCTION WRITER'S GUIDE o Sequential arabic numbers should be assigned to tables. The sequence shoula correspond with the order of their reference in the text. The symbol "#" and abbreviation "ho. are unnecessary and should not be used. The number alone

. suffices.

EXAMPLE: Table 1, Table 2, etc.

o Tables should be located on the page following their reference where practicable. Commonly used tables should be located tollowing the end of the action steps.

o The table number and title should be centered above the figure using standard station word processing equipment.

o Standard station word processing equipment should be used for entering table text.

o Each column should contain a centered heading. The first letter of each word in the column headings should be capitalized.

o Horizontal lines should be placed above and below the column headings; vertical lines, while desirable, are not required.

o Tabular headings should be aligned as follows:

--horizontally by related entries.

--vertically by decimal point for numerical entries.

--vertically by first letter f or word entries.

o Double spacing should be used between horizontal entries to separate them. Use horizontal lines also, if desired, but if used, draw double horizontal lines above and below the column headings.

o Table cells should not be vacant. If no entry is necessary, "N.A." should be entered to indicate not applicable.

6.3 Fold-Out Pages The fold-out page should' follow the last instruction page. The fold-out page is intended for the display of information that would be appropriate to have available throughout the E01 usage period. The format and spacing of the contents on the fold-out page vary according to the quantity of information required on the page.

B-28 i _.

S. >- .

ic.

a

! V EMERGENCY OPERATING INSTRUCTION' WRITER'S GUIDE 6.4 Place-Keeping Aids It is important that' operators have a means of keeping track _of

the current step while they are performing the designated actions.

Various recordation needs associated with monitoring ^and timing activity steps also demonstrate the need to write on the E01's.

To satisfy these needs, E01 pages should be placed in sheet protectors that can be marked on with a grease pencil.

6.5 Rotation of Pages

_ If pages need to be rotated (turned sideways), follow these rules:

o Place the: top,of the rotated page at the normal lefthand edge.

O Do not rotate.the page margins.

o Do not rotate page identification and numbering.

'6.6 Reduced Pages

. Avoid using reduced pages as they are more difficult to read. If

~

used, the final size of reduced pages should be standard page size-to improve readability.

6.7 Attachments Attachments-may be in the form of figures, tables, fold-out pages,;

amplifying task discrete action steps'or other information

~

i

~

determined to be necessary for pr_oper E01 execution. The following' rules should be considered in attachment' preparation:

o Sequencing of the attachments should. consider their order of

-use within the E01,-their fre'quency of use as well as their-

' useability.

0 Sequenti'al. arabic numbers should be assigned to the attachments.- The symbol'"#"'a'nd~ abbreviation ~"No." are

. unnecessary and should'not be used. The number alone suffices.

-EXAMPLEi Attachment 1, Attachment 2, etc.

o -Attachment-formatting shoulo be consistent with the applicable writer's guide section(s) e.g., figures shculd be formatted'in accordance with Section 6.1, etc.

~

7.0: TYPING FORMAL i

The following general rules should be used to.obtain uniformity in the, presentation,-_ clarity, and' readability of E01 typed contents:

o. . Text should be entered onto preprinted form SCE 50-20-1 and-SCE 50-20-2 as applicable..

B-29 u, J

f(5**=

EMERGENCY OPERATING INSTRUCTION WRITER'S GUIDE s ,

'o Typing should be accomplished utilizing standard station word processing equipment.

o '. -breaking of words should be avoided.

o ' Steps should be completed on the same page they begin.

o. Capitalization, underlining, positioning and punctuation are methoos ofLhighlighting instructional text and should therefore be

, typed as' indicated by the author.

7.1 Page Arrangement 7.1.1 The contents of the cover page and instruction page should be positioned in accordance with the following:

o Cover Page Contents:

Line 1 SAN ONOFRE NUCLEAR GENERATING STATION EMERGENCY OPERATING INSTRUCTION S0#-#

Line 2 UNIT #

REVISION #

PAGE # OF #

Line 5 - TITLE '

Line 9 EFFECTIVE DATE (Cover page only);

Line-12 PURPOSE . ,

Line 14 Text Area Line 21 SYMPTOMS Line 23 Text area Line 42 PAGES CHANGED WITH THIS REVISION: _

(NEW, ALL, #)

Line 46 PREPARED BY:

AUTHOR- .DATE- ,

f-Line 51 APPROVE 0'BY:

(NAME) . DATE MANAGER, OPERATIONS Line 56 (Initials):(initials):(#)

B-30

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

gb [ */* .

EMERGENCY OPERATING INSTRUCTION WRITER'S GUIDE t

1, .

7.1.1 =(continued).

> u Instruction Page' Contents:

Line 1 -SAN ONOFRE NUCLEAR GENERATING STATION

~

EMERGENCY'0PERATING INSTRUCTION

-S0#-#

I. -

Line 2 UNIT #

REVISION #-

PAGE'# 0F # *

'Line'5 TITLE Lines 12 Action Step: Text thru 62 7.1.2 Horizonall text positioning should be'ac'complished in p

-accordance with the following rules:

c' Page margins.are specified by the printed borders.

Allow at least two typed spaces between the text and e ' borders.

o 'The step number should be aligned under the STEP column.

a :' ,

o The A/ER and RNO text should be aligned under their respective column titles.

n

. 4>

"T" -8.0! REPRODUCTION AND DOCUMENT CONTROL

~

~

'8.1 Reproduction and document control should be in accordance with

""l existing Station Administrative controls.

n I .

~

, kfE 4 ,

y m-;

, 'c >,

.v-I '

?<

gx -

, . j. 6 i ',

;b .(- -

.-

.p #: b-31 gl~ TX -- ; .2 - .

. -r: r -  ;

.t

s

() . _ 4 i

PROCEDURES GENERATION PACKAGE PART C VAL 10AT10h PROGRAM DESCRIPTION hu um e

L. . 3 -

j E

VALIDATION PROGRAM DESCRIPTION

-TABLE ~OF CONTENTS 4

- Section Page

' 1.0; . INTRODUCTION. . . . . . . . . . . . . . .-. . . . . . . . . . . . .C-1 1.1 Purpose. . . . . . . . . . . . . . . . . . . . . . . . . . .C-1 1.2- General. . . . . .~. . . . . . . ... .'. . . . . . . . . . .C-1 1.3 Scope. . . . . . . . . . . . . ... . . . . . . . . . . . . .C-1 2.0 VALIDATION PROCESS. . . . . . . . . . . . . . . . . . . . . . . . .C-1 2.1 Desk Top Reviews . . . . . . . . . . . . . . . . . . . . . .C-2 2.2 Simulator Exercises. . . . . . . . . . . . . . . . . . . . .C-7 LIST OF FIGURES Figure No. 1 Page 1 EXAMPLE DESK TOP REVIEW CRITERIA . . . . . . . . . . . . . .C-3

-2 -EXAMPLE DESK TOP. REVIEW DOCUMENlATION. . . . . . . . . . . .C-6.

.3 ' EXAMPLE SIMULATOR EXERCISE SCENARIO DOCUMENTATION. . . . . .C-8 4 EXAMPLE SIMULATOR EXERCISE CRITERIA. . . . . . ... . . . . .C-10 t- ,

5 EXAMPLE DISCREPANCY-DOCUMENTATION. . . . . . . . . . .-... .C-12 j

P t

. N' , .

.v ,

A

'^

J -

, e s VALIDATION PROGRAM DESCRIPTION

1.0 INTRODUCTION

1.1 Purpose The purpose of the Validation Program is to verify that the E01's can be accurately and efficiently carried out and are adequate to mitigate transients and accidents.

1.2 General-As discussed in Part A,_Section 1.2.5 of this package, the centents

'of-this part of the PGP will be incorporated into the station document system. The current identification of this forthcoming document is Administrative Procedure 50123-VI-1.0.5, " Units 2 and 3 E01's - Preparation, Revision and Validation."

1.3 Scope The validation should verify that the following objectives are met:

a) The E01's accurately reflect the CEOG Guidelines.

b). .The E01's accurately reflect the Writer's Guide. <

c) The E01's use language and level of information presentation that is compati.ble with the minimum number, qu'alifications,

. training, Land experience of the licensed operators.

d) The E01's reference controls, equipment, and hardware that are available. -This equipment uses the same designation, units of measure, and operation that.is specified in the E01's.

e) The E01's can be understood and followed without confusion, delays, or errors.

- .f) The E01's are-assured'to guide the licensed operator in mitigating-transients and accidents.

The validation will not verify the' accuracy, efficiency, or aaequacy of the CEOG Emergency Procedure Guidelines, as this was-previously accomplished in CEN-152 Rev. 01 and~ submitted to the NRC in CEOG letter RWW-83-15 to D. G. Eisenhut, NRC, from R. W. Wells,

~

Chairman C-E Owners Group, dated March 19, 1983.

l l

1 l

l l

=

C-1  ;

1

3 VALIDATION PROGRAM DESCRIPTION 2.0 VALIDATION PROCESS The validation of E01's should consist of two methods, desk top reviews and simulator exercises.

2.1 Desk Top Reviews o The desk top reviews should be performed prior to simulator exercises and should meet the following criteria:

a) The E01's accurately reflect the CEOG Guidelines.

b) The E01's accurately reflect the Writer's Guide.

c) The E01's use language and level of information presentation that is compatible with the minimum number, qualifications, training, and experience of the licensed operators.

d) The E01's reference controls, equipment, and hardware that are available.

o The desk top reviewers should consist of licensed operators, aesign engineers, ana other personnel familiar with the E01 subject matter and Writer's Guide. The authur of an E01 should not perform the only desk top review of that E01.

o The reviewer should compare the E01's against the criteria provided in Figure 1. _ Role playing is not required for this effort. Identified discrepancies from this review should oe documented as illustrated in Figure 2. Discrepancies should be resolved prior to the simulator exercises and must be resolved I prior to the E01's being issued.

O In addition to the aesk top review, another cocumented E01 review and discrepancy resolution cycle will be performed in accordance with Station Administrative Procedure 50123-VI-1.0,

" Station Oraers, Procedures, and Instructions - Preparation, Revision, Review, Approval, and Publication."

o Also, Combustion Engineering will conduct a review of the upgraded E01's. This review will be documented by letter from C-E to SCE. Resolution of any comments pursuant to the C-E letter should be accomplished by the E01 upgrade team and a C-E representative. A memorandum to file should be prepared indicating the resolution of the comments detailed in the C-E letter.

C-2

.= -

s.

• 1

~

VALIDATION PROGRAM DE5CRIPT10N FIGURE 1 EXAMPLE DESK TOP REVIEW CRITERIA

'I. PROCEDURE - GENERAL A. Written Correctness

1. . Legibility

a. 1s.the information visible and reproducible on all instruction pages?

b. Are'the test, tables, graphs, figures, and charts legible to

- the reader?-

4

2. E01-Format Consistency

a. Do the following sections exist in each E0l?

1) -PURPOSE?

2) SYMPT 0MS?

3) OPERATOR ACTIONS?

4) FIGURES?

.b. .ls,the operator. actions section-presented in a dual column?-

c. 1s the page layout consistent with the Writer's Guide / examples?

I: ~3. Identification Information

-a. Is the: instruction title accurate and descriptive?

~

b. Isla cover sheet provided?

c. Does each page contain the correct:

1): instruction designator?

L 2) revision number?

3) ~page number?.

d. Does'the instruction have all its pages in the correct order?

~.

11. STEPS, CAUTIONS,NOT85 A. Written Correctness

1. Information Presentation

-a. Are instruction steps numbered correctly?

C-3

3 a .. .

VALIDATION PROGRAM DESCRIPTION FIGURE 1 EXAMPLE DESK TOP REVIEW CRITERIA ,

(continued)

b. Are, instruction steps constructed so that:

1) Each step deals with only one idea?

-2) Sentences are short and simple?

3) Operator actions are explicit?

4) Objectives of operator action are specifically or adequately stated?

5) If there are three or more objects, they are listed?

6) Punctuation and' capitalization is proper?

~7)- Abbreviations are correct and understandable to the operator?

c. Do instruction steps make proper use of logic structure?

d.- When an action instruction is based on receipt of an alarm, is the setpoint of the alarm identified?

Are cautions used appropriately?

e.

f. Are cautions properly placed?

9 Are cautions constructed so that:

1) they do not contain operator actions?- '

2) they'do-not use extensive punctuation?-

~

3) they make proper use of highlighting?

h. Are notes properly used?

i. Are notes properly placed?

j. Are notes worded so-that they do not contain operator

^

actions?

k. Are numerical values properly written?

[ 1. _Are values in the instruction specified in such a way that

-mathematical operations are appropriate for the user?. (Is a chart or graph provided in the-instruction for necessary

, , operator calculations?)

.m. Are units of measurement in the E01 the same as those on

' instruments?'

C-4

., a.

VALIDATION PROGRAM DESCRIPTION FIGURE 1 EXAMPLE DESK TOP REVIEW CRITERIA (continued)

2. Procedure Referencing and branching

a. Do the referenced and branched procedures identified in the E01's exist for operator use?

b. Is the use of referencing minimized?

c. Are referencing and branching instructions correctly worded?

1) "go to"

2) " implement"

o. Do the instructions avoid routing users past important information such as cautions?

e. Are the exit conditions compatible with the entry conditions of the referenced or branched procedure?

B. Technical Accuracy

1. Entry Conditions

a. Are the entry conditions of the E01 correct?

b. If additional entry conditions have been added, are they:

1) unique entry conditions?

2) not excessive in number?

2. Quantitative Information

a. Do the quantitative values include tolerance bands?

3. Plant Hardware Information

a. Is.the plant hardware specified in the E01 available for operator use?

1) equipment?

2) controls?

3) indicators?

4) instrumentation?

C-5

i

-5/

.;  : s i.

VALIDATION PROGRAM DESCRIPTION i

FIGURE 2' EXAMPLE DESK TOP REVIEW DOCUMENTATION DISCREPANCY' NUMBER:

TITLE (E01.#/REV. #)

DISCREPANCY' DESCRIPTION:

I

' REVIEWER: DATE:

(Printed Name)

, REVISION! REQUIRED: NO YES: Prior to implementation Future

[ . RESOLUTION:

i l

~

L - E01' REVISED bY:- DATE:

-(Printed Name)

.c t.;

cc: REVIEWER.

r. ~

, j

^

C-6

, . . .~

3

/

s i a' '

, s. '

s

• V4LIDAT10h PROGRAM DESCRIPTION i s v s

- 1

'\'

N

• O, o2 7'$1mulater Exerca es ,

4 4.- N ,.

s g /. 5/ (_ s

. ou'The simulator exercises' should mJet the following criteria:

4 t

" ~

a) The' equipment refererced in ,the E01's use the same

-c designation,unitpcfimcasu , and operation that1 1s used in the E01'.s.

4

~

b) The E01's can be unaerstood and followed without confusion, delays,pcerrors. f, -} y c) The E l's are assured qh guide ithe I.icensed operator in mitigating transients'ano accidents.

'  %,x -

o Simultaneous, sequential multiple f ailurei as well as

,[ "

uncomplicated events should Ve seier.t'ed to exercise the maximum

& number of E01's. The followieg sc.enacio selection criteria should be used to meet this objective:

.s .- -

y. . . s a) exercise all E01 entrances, exits,.and branches.

b) exercise the E01 standara p6st trip actions for all optimal recovery instructions. ,

, c c) 3xercise the E01 diagnostic for"t.ll optimal recovery instructions.

,_ 7f ~.. ,

.d) exercip th safety function checks and functional recovery instruction usage.

7

% %, i ,.

- e) exercht the use of fche fu'ndtional recovery instruction for sequediihlorsimu)}anEeeusfailures. .

'; . \ b; .

f) . exercise the E01's duding ti,me dependent operations.

g) exercise the EOl's.t,o assess the criteria-in Figure 4..

. v .

The simulator exercise scenarios should be documented as V illustratea in Figure 3. The simulator event sequence should

-consist of(applicable intornstion tracking the event development

,' from initiafNon to termination. The source of this information should be available autenatic simulator recordation documen-tation. This documentation should be attached to the exercise form.

o The simulator exercise observation team shbuld consist of

. licensed' operators, design engineers, trainers, and simulator L erparts f amiliar, with >the E0I s'ubject matter. The observation

[l -t'eam should' be fjmiliar with the simulator, the exercise scenarios, end ,the observation criterja prior to running the

' exercises. ,

~

_ L'Y -C-7~

s'

• \

g. (

, ..w * , - y . - . - ..m, , - - . . , - - . -

4 - . .

',;. 1 .

VALIDATION PROGRAM DESCRIPTION 1, . FIGURE-3 EXAMPLE SIMULATOR EXERCISE, SCENARIO DOCUMENTATION

-TITLE E01 #/REV. #

DATE:

E . E01. FEATURE 5 TO BE' EXERCISED

-5CENAR10 DESCRIPTION:

' INITIAL PLANT CONDIT10N5': .

s Ob5ERVAT10N' TEAM MEMBER $2 POSITION NAME I ~.',

\ '

. m .

l- ,

' CONTROL ROOM' TEAM MEMBERS'

. fP051 TION, NAME

A- ' n , ,

s l

'3 , '

& -W i ~

9 4 SIMULATOR EVENTSEQUENCEl(AFTER EXERCISE):

C-8

.ca r

i '

. m. o l

VAllDATION PROGRAM DESCRIPTION i o A minimum complement of control room staff should be used for the exercises. The control room team should be briefed on the E01's and their use prior to the start of the simulator exercises. They should not be briefed on the scenarios to be run or the expected operator performance.

o Ine San Onofre plant specific simulator will be used. Any configuration differences should be reviewed by the observation team and control room team during exercise briefing and debriefing sessions.

o The obse"vation and control room teams should be debriefed after the simulator exercise for the purpose of identifying and defining discrepancies. The observation team leader will (

moderate the discussion utilizing the following techniques to identify and define discrepancies:

a) present problems and discrepancies -- verbal explanations may be augmented by videotape displays of problems b) present possible causes for problems c) present potential solutions to problems d) present explanations of possible causes and potential solutions identified discrepancies from this debriefing should be documented as illustrated in Figure 5. Discrepancies must be resolved prior to the E01's being issued.

t C-9 a -

o a

r

. A:e VALIDATION PROGRAM DESCRIPTION FIGURE 4 EXAMPLE SIMULATOR EXERCISE CRITERIA

1. USAblLITY A. LEVEL OF DETAll

1. Was there sufficient information to perform the specified-actions at each step?

2. Were the alternatives adequately described at each decision point?

3. Could the operator use labeling, abbreviations, and location information as provided in the E01's to find the needed equipment?

4. Were the E01's missing information needed to manage the emergency condition?

5. Were the contingency actions sufficient to address the symptoms?

6. Could the operator use the titles and numbers to find referenced and branched procedures?

8 .- UNDERSTANDABILITY

. 1. Was the E01 read easily?

2. Were the figures and tables easily and accurately read?

Were the values on. figures and charts easily determined?.

~

3.

4. _W ere caution and note statements complied with?

5. -Were the E01 steps complied with? ,

- 11. WORKAblLITY A. PLANT COMPATIBILITY

1. Were the actions specified in the procedure able to be performed in the designated sequence?

2. . Did the operator find alternate success paths not included in the:E01's?'

3. .As specified in the E01's, could the operator obtain the

> necessary information from the plant instrumentation that is provided?

^

C-10 -

, 6..

VAL 10A110N PROGRAM DESCRIPTION FIGURE 4 EXAMPLE $1MULA10R EXERCISE CRllERIA (continued)

4. Did the diagnostic and symptoms provide adequate information for the operator to select the applicable E0l?

5. Were the E01 entry conditions appropriate for the plant symptoms seen by the operator?

6. Dio the operator have to use information or equipment not specified in the E01's to accomplish the task?

7. Did the plant responses agree with the E01 basis?

8. Were the instrument readings ano tolerances consistent with the instrument values stated in the E0l?

9. Were the E01's physically compatible with the work situation (too bulky to hold, binaing wouldn't allow them to lie flat in work space, no place to lay the E01's down to use)?

b. OPERATOR COMPATiblLITY

1. If time intervals are specified, were the procedure action steps able to be performed on the plant within or at the designated time intervals?

2. Were the procedure action steps able to be performed by the operators?

3. If specific actions were assigned to individual personnel, did the E01's help coordinate the actions where necessary?

4. Were the operators able to follow the designated action step sequences?

5. Could the operator find the particular step or set of steps when required?

6. Could the operator return to the procedure exit point without omitting steps when requirea?

7. Could the operator enter the branched procedure at the correct point?

8. Could the operator exit from a given E01 at the correct point?

t-

9. Were physical conflictt between operators minimized?

10. Were action steps sequenced to avoid unintentional duplication?

C-ll

. 6 VALIDATION PROGRAM DESCRIPTION FIGURE 5 EXAMPLE DISCREPANCY DOCUMENTATION OlSCREPANCY NUMBER:

TITLE (E01 #/REV. #)

DISCREPANCY DESCRIPTION:

OBSERVER /0PERATOR: DATE:

(Printed Name)

KEV 1510N REQUIRED: NO YES: Prior to implementation Future RESOLUTION:

E01 REV15ED BY: ,

DATE:

(Printed Name) cc: OBSERVER /0PERATOR C-12

p

, o.u PROCEDURES GENERATION PACKAGE PART 0 TRAIN 1hG PROGRAM DESCRIP110N i

l

-..-...,...----......~.-....',--, -. , - - - - .

.. ab 1RAINihG PROGRAM DESCRIPTION TABLE OF C0h1ENTS

. Section' Page

- 1.0 1hTRODUCT10N. . . . . . . . . . .'. . . . . . . . . . . . . . . . .D-1 1.1 Purpose. . . . . ... . . . . . . . . . . . . . . . . . . . 0-1

.l.2 General. . . . . . . . . . . . . . . . . . . . . . . . . . .D-1 l.3 Scope. . . . . . . . . . . . . . . . . . . . . . . . . ... .D-1 2.0 PROGRA>l DESCRIPTION - INITIAL TRAINihG. . . . . . . . . . . . . . 0-1 2.1 Classroom Training . . . . . . . . . . . . . . . . . . . . 0-1 2.2 Simulator Training . . . . . . . . . . . . . . . . . . . . .D-1 2.3 Operational Feedback . ... . . . . . . . . . . . . . . . . 0-2 a

3.0 - RETRAlhlhG. . . . . . . . . . . . . . . . . . . . . . . . . . . . .D-2 4.0 - INITIAL TRAlhlhG EVALUATION-. . . . . ... . . . . . . . . . . . . .D-2

~ 5.0 DOCUMENTATION ... . . . . . . . . . . . . . . . . . . . . . . . . .D-2 Y

9

1. .2

---_---__-m___.-_____-m__ , _ __m._ , __, _ __

c-c (.

TRAINING PROGRAM DESCRIPTION

1.0 INTRODUCTION

1.1 Purpose The purposes of this program are to:

o Enable the operators to understand the structure and format of the upgraded Emergency Operating Instructions (E01's).

-0 Enable the operators to understand the technical bases of the upgraded E01's. ,

o Provide the operator with a working knowledge of the technical content of the upgraded E01's.

.o Enable the operators to use the upgraded E01's under operational conditions.

1.2 General As discussed in Part'A, Section 1.2.5 of this package, the contents of this part of the PGP.will be incorporated into the Nuclear '

Training Division document system. The current identification of

> this forthcoming document is Training Program Description OPT 2/3,

" Upgraded Emergency Operating Instructions (E01's) Program - Units 2/3."

1.3 ' Scope e Personnel licensed on San Onofre Units 2 and 3 shall. receive training on the upgraded E01's in accordance with Section 2.0 and prior to E01. implen=entation.

2.0 PROGRAM' DESCRIPTION ' INITIAL TRAINING c, 2.1 fClassroom Training Classroom training shall consist of'a series of lectures and

' discussions. These should cover the logic behind development of-2 the E01's, the process used to' develop E01's, and the E01's-themselves, including supporting technical and human factors

- information.

-2.2 Simulator Training cF Training conducted on the plant-specific simulator shall .

consistlof a combination of ~ simulated events and walk-throughs-to exercise the E01's.-

.1-

, o. A wiae variety of scenarios including-multiple and. sequential:

' failures should be used to exercise the E01's.

~ 0-1 r + n.

.a -

" 1.

, 00 TRAlhlhG PROGRAM DESCRIPTION 2.2 Simulator Training (continued) o Training shoulo be conducted with a full shif t ccmplement exercising each E01 to stress operator roles, interaction, and team training. Crew members should train by performing their normal, as well as alternate control room functions.

o Differences between Unit 2. Unit 3, and the plant-specific simulator should be addressed during training.

2.3 Operational Feeaback Operational feedback to improve E01 usage and content will be encouraged during the training described in Sections 2.1 and 2.2.

Operation Instruction 5023-0-35, "Use of Procedures," provides the necessary guidance for formalizing and processing these cona ats.

3.0 RETRAlhlhb Following the initial training described in Section 2.0, retraining on the upgraded E01's will be conducted as part of the Operator kequalification Program in accordance with the Operator Requalification Program (Training Memorandum 19-81).

4.0 INITIAL TRAINihG EVALUATION The operators' knowledge and understanding of the E01's shall be evaluatea. Inis evaluation should be done in accordance with the following:

o A w itten examination should be conducted at the completion of the classroom training described in Section 2.1.

o The simulator instructors should evaluate both individual and team performance during each of the training scenarios performed on the simulator.

5.0 DOCUMENTATION Documentation of operator training shall be maintained in accordance with the Training Division Records Control Center Procedures Manual.

0-2

\