ML20024F160
| ML20024F160 | |
| Person / Time | |
|---|---|
| Site: | Maine Yankee |
| Issue date: | 08/22/1983 |
| From: | Maine Yankee |
| To: | NRC |
| Shared Package | |
| ML20024F159 | List: |
| References | |
| 2.50.0, NUDOCS 8309080283 | |
| Download: ML20024F160 (3) | |
Text
_
Proc. No. 2.50.0 Rev. No. 5
{'
Page 2 of 3
^
l 5.0 PREREQUISITES 5.1 The Emergency Coordinator has recognized or been advised that a condition exists which may constitute an emergency condition, 0,,B 5.2 The Plant Manager or his designated alternate has ordered an emergency condition declared.
6.0 DEFINITIONS d
6.1 Unusual Event - A potential degradation of the level of safety of the plant constitutes an unusual event. Incidents which have no public safety significance but which would attract public attention (e.g., noise nuisance) may be treated as unusual events for notification of offsite authorities.
6.2 Alert - An actual or potential substantial degradation of the level of safety of the plant or failure of critical safety furctions that are not called upon to function constitutes an alert event.
6.3 Site Area Emercency - Actual or likely major failures of critical plant safety functions needed for protection of the public consitute a site area emergency.
(This classification would be assigned even though the affected plant function may not be required at the time).
6.4 General Emergency - Actual or imminent substantial core degradation or melting witn potential for loss of containment integrity constitutes a general emergency.
7.0 PROCEDURE-R 7.1 Refer to Figure 2.50.0-1. Rev. 4, " Emergency Condition Classification. Table".
7.2 Locate the appropriate " event in progress" in the left hand column of Figure l
2.50.0-1.
More than one " event in progress" may exist.
7.3 Working frcm left to right (in ascending severity of emergency condition) examine the emergency action levels associated with the " event (s) in progress" for each emergency ccndition. Determine which EAL's hve been reached, and note the severest emergercy condition for which an EAL has been reached.
7.4 Examine all EAL's associated with the severest emergency condition noted in Step 7.3.
Note any others wnich have been reached.
7.5 Scan all EAL's associated with emergency conditions more severe than the severest identified in Step 7.3.
Note any which have been reached, and note tne associated emergency condition.
8309080283 830831 PDR ADOCK 05000309 h
PDR X ool
~'
. s I
Proc. No, 2.50.0 Rev. No. 5
(
Page 3 of 3 -
7.6 Categorize the emergency condition as the most severe identified in Step 7.3.7.4 and 7.5, and declare this emergency condition.
7.7 Implement Procedure 2.50.17, " Emergency Notification" for the emergency condition declared in Step 7.6.
7.8 Repeat Steps 7.1 through 7.6 periodically and as plant conditions change, to provide a check that the declared emergency condition remains appropriate.
If it is determined that the declared emergency condition should be revised, repeat Step 7.7.
Step 7.7 snould also be performed when the emergency is declared to be terminated.
8.0 ADDITIONAL REQUIREMENTS 8.1 The Emergency Coordinator may classify an emergency condition based on the definition of the condition indicated in Figure 2.50.0-1 when time is of the essence, when there is uncertainty as to whether EAL's have been reached, or when the list of EAL's o.r measurables/observables appears not to deal '
directly with existing conditions.
8.1 When an emergency condition has been declared and classified, Procedure 2.50.1, 2.50.2, 2.50.3, or 2.50.4 should be initiated according to the classification assigned to the emergency condition.
9.0 FINAL CONDITIONS Plant conditions indicative of the possible existence of a plant emergency condition have been recognized and evaluated. An emergercy condition has been declared, classified, reclassified as necessary, and declared terminated.
1 1
4
-7 Form No. 0-05-1-1 Revised 3/11/83 4
MAIM YANKEE CONTRO. LED CCCDENT REVISICN TRANSMITTAL FCRM DCC1JENT: 2.50 Series - bE Dwyercy Plan & Implementirxy Procedures C7Y NUMEER: ch-Occ OtR1 V5 O R C., Oc4.
(a)
ISSUE CATE: Aucust 22, 1983 1.
Renove existing pages 2-4 of Proc. No. 2.50.0, Declaration & Categoriration of Energency Conditions, Rev. No. 5 and replace with attached pages 2 and 3.
Page 4 has been eliminated as it is a Classification Table Index.
Referenced pages have been replaced by Figure 2.50.0-1, "Bnergency condition Classification Table".
The above listed revisien(s)/ charge (s) has/have been placed in ycur assigned ccoy.
TM UNCERSIGNED ACXNOWLECCES COMPEICN CF TM FCLLCwLNG:
1.
The review of tre revised material.
2.
Assurance that these wno use tne cccunent are aware of tne charge.
SIGNATUFE CF HCLCER:
/
CAid RETURN THIS FCRM TO:.Acministraticn Office wit".in 10 workirs days of issue, h
I 1
s