ML20213H101

From kanterella
Jump to navigation Jump to search
Rev 2 to Emergency Plan Implementing Procedure FNP-0-AP-74, Emergency Response Procedures Verification
ML20213H101
Person / Time
Site: Farley  Southern Nuclear icon.png
Issue date: 05/12/1987
From:
ALABAMA POWER CO.
To:
Shared Package
ML20213H063 List:
References
FNP--AP-74, FNP-0-AP-74, NUDOCS 8705190137
Download: ML20213H101 (7)


Text

.

FNP-0-AP-74 ATTACHMENT 3 EMERGENCY RESPONSE PROCEDURES VALIDATION 1.0 Introduction 1.1 Purpose The purpose of this attachment is to guide the administrative process used in the validation of the Emergency Response Procedures (ERPs).

1.2 Applicability This procedure applies to ERP validation before and after initial implementation for Unit 1 and Unit 2 of the Farley Nuclear Plant.

2.0 References 2.1 Emergency Operating Procedures Validation Guideline INPO 83-006.

2.2 Farley Nuclear Plant Emergency Response Procedures Writers Guide, FNP-0-AP-74, Attachment 1.

. 3.0 Definitions Emergency Response Procedures (ERP's) - Plant procedures directing operator actions necess--v *e citicata the ;scrquences of transients and accidents that cause ptauc parameters to exceed reactor protection system setpoints, engineered safety features setpoints, or other appropriate technical limits.

Emergency Response Guidelines (ERG's) - Guidelines that provide round technical bases for the development of ERP's.

ERP Source Documents - Fundamental documents or records upon which ERP's are based.

ERP Technical Accuracy - Proper incorporation of generic and/or' plant-specific technical information from ERP source documents and plant hardware into the ERP's.

ERP Validation - The evaluation performed to determine that the actions specified in the ERP can be followed by trained operators to' manage the emergency conditions in the plant.

Scenario - A structural plan of parameter and plant symptom changes that provide operating cues for the conduct of assessment.

K oj4g Page 1 of 4 Gen. R m 2 PDR

FNP-0-AP-74 4.0 Responsibilities 4.1 Operations Superintendent The Operations Superintendent shall have overall responsibility for ERP validation.

4.2 Emergency Response Procedures Coordinator The Operations Superintendent shall designate an Emergency Response Procedures Coordinator who shall be responsible for coordination of the ERP validation process.

5.0 ERP Validation Process The process of ERP validation consists of three phases: ,

preparation, assessment and resolution.

5.1 Preparation The preparation phase consists of the following activities.

1

  • Scenario selection
  • Scenario preparation 5.1.1 Scenario selection

~

A set of scenarios to be used for validation shall be approved.by the Operations Superintendent. The scenarios selected shall be sufficient to provide reasonable assurance that operators s __ _. ..

emergency conditions using the ERP's and that ERP's are operationally correct. It is not intended or desireable that scenarios be selected to individually perform each procedure. Instead scenarios which integrate the performance and interaction of the ERP's as a whole should be utilized. As a minimum sufficient scenarios shall be selected to demonstrate satisfactory operator response and control over the following emergency conditions.

' Reactor Trip

' Loss of Coolant Accident

' Major Steam Break

, ' Loss of Offsite Power 4

'A severe (red path) challenge to any critical safety function.

Page 2 of 4 Gen. Rev. 2

,--w----_-._.---, , . , , -

.3.-._-. _ - - - -.-_-_w__-- - - . - . . . - -,.y.r.-%-.<---- ..---..~_,.,,-.-,-.m,------,-w, . ,,+-~-w----- --

FNP-0-AP-74 5.1.2 Scenario preparation For each scenario a scenario cover page shall be prepared (Figure 1). The cover page shall include the general scenario description, expected ERP's to be used, the initial plant conditions and the desig-nated evaluator. Following the cover page the 3

expected sequence portion of the scenario evaluation form will be completed (Figure 2) using as many sheets as necessary. The expected sequence shall specify the procedure and step number sequentially listed in the assumed order of performance for the associated

, scenario. The expected sequence will include cautions and note performance and 'shall detail expected transfers between procedures. For scenarios in which more than one sequence of performance is possible, an expected sequence shall be prepared for each alternative sequence.

During the scenario assessment phase the evaluator shall then utilize the associated sequence chosen.

5.2 The assessment phase consists of the following activities.

' Crew Briefing

  • Scenario Performance and Evaluation
  • Crew Debriefing 5.2.1 Crew Briefing

. The d. cd r, -? " slu tor shall brief the operating crew on the validation process and how the assessment

' will be conducted. During crew briefings general familiarization with the Emergency Response Procedures and presentation of initial plant conditions shall be conducted. Discussion of the specific scenario to be utilized however should be avoided to preclude "preprograming" the operator response .

5.2.2 Scenario Performance and Evaluation Each scenario shall be run on the plant simulator.

During the scenario performance the designated evaluator shall complete the evaluation portion of the scenario evaluation form. Each step, Note and Caution shall be evaluated in the categories of operational correctness, useability / understand 4bility, and plant response.

Additional guidance in assessing these categories is contained on the scenario evaluation form. If any additional actions not contained in the procedures are necessary the evaluator shall indicate this at j the appropriate location on the scenario evaluation fo rm .

i Page 3 of 4 Gen. Rev. 2 4

s.,. . - - ,a ., _ . - - . -< , - - _.--wey-._.w----_yre, . , ,m-_~ --e, ~,.- ,r.we,- ww,.,.m _-..._____.-_,__.-,,%,%..


- -.- m % r,-,.me eww w- -m-t--r-

FNP-0-AP-74 During performance of the simulator run, interaction between the operating crew and the evaluator should be minimized. It is permissible for the evaluator to resolve any obvious clerical errors or to provide information relating to parameters not observable from within the. control room. Any corrections required will be noted on the scenario evaluation form. If an alternative sequence other than one of the expected sequences is selected by the operating

  • crew it is permissible for the evaluator to redirect the scenario to one of the expected paths. In such circumstances however the initial selection by the operating crew shall be documented on the scenario evaluation form for subsequent review during the resolution phase.

5.2.3 Crew Debriefing 8

Immediately following completion of the simulator run a crew debriefing shall be conducted. The designated evaluator shall request any procedure problems noted by the operating personnel. Problems mentioned shall be documented in the comments section of the scenario evaluation form adjacent to the associated steps. Upon completion of comments by the operating crew, the evaluator may solicit comments regarding potential problems he identified during the simulator run. All valid discrepancies shall also be included on the scenario evaluation form.

1, ' ad an The designated evaluator will review all comments and discrepancies. All valid discrepancies shall be recorded on a discrepancy resolution form (Figure 3) along with a proposed resolution. All discrepancy resolution sheets along with the scenario cover page and scenario evaluation forms shall be forwarded to the Emergency Response Procedure Coordinator.

The Emergency Response Procedures Coordinator shall coordinate the selection of final resolution for all discrepancies and 4

the preparation of any procedure revisions required.

Upon completion of all scenarios the scenario packages shall be forwarded along with the updated Emergency Response -

Procedures to the Operations Superintendent for final review and approval.

i r

t i Page 4 of 4 Gen. Rev. 2

2 FNP-0-AP Attachment 3 FIGURE 1 ERP VALIDATION Page of

, (cover page) s .ERP TITLE:

ERP NUMBER: REVISION:

DATE:

SCENARIO DESCRIPTION:

1

)

1 i'

I J

1 4

i j

j . . .

i t

t ,

i 1

INITIAL PLANT CONDITIONS:

i' s

4 l

I EVALUATOR (S)

, t 4

i ,

Approved

,t i

i N

i

Gen. Rev. 2 i

1

. , - = . - - _ . _ . . . - - . , _ . - - - - - _ _- . _ , . . - - _ - . -

FNP-0-AP-74 Attachment 3 FIGURE 2 SCENARIO EVALUATION FORM Step Evaluation No Expected Step -Step - Plant Additional S:quence Operationally Useable / Response Actions Comments ERP/ Step correct Understandable as expected Required Y N Y N Y N Y N l

I i l l

l Operational Correctness: 1) Performed in expected sequence.

2) Performed in manner consistent with step presentation Usable / Understandable 1) Sufficient detail
2) Adequate feedback available
3) Compatible with plant layout, hardware and shift components
4) Figures, Tables, Notes and Cautions understandable Plant Response as 1) Sufficient contingencies to address plant systems expected 2) Plant response consistent with step intent
3) Plant response consistent with expected procedures branches

) additional actions 1) No missing information required to manage emergency cequired Gen. Rev. 2

FNP-0-AP-74 Attachment- 3 FIGURE 3 DISCREPANCY DISPOSITION STEP / NOTE / CAUTION NUMBER DISCREPANCY:

DISPOSITION: .

Gen. Rev. 2