ML15364A019

From kanterella
Revision as of 02:39, 31 October 2019 by StriderTol (talk | contribs) (Created page by program invented by StriderTol)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search
Revision 13 to RA-EP-02110, Emergency Notification and Revision 13 to RA-EP-02220, Emergency Operations Facility Activation and Response
ML15364A019
Person / Time
Site: Davis Besse Cleveland Electric icon.png
Issue date: 12/22/2015
From:
FirstEnergy Nuclear Operating Co
To:
Document Control Desk, Office of Nuclear Reactor Regulation
References
Download: ML15364A019 (38)


Text

LIZ

-F Davis-BesseENOC Power Station Transmittal Report Page 1 of 1 Data Date Time: 12/22/2015 07:05:32 AM Trnsita DB-P-2112POC0010SMPL-CANE5APRVE Trnmta D0e 10 22205PI0B4A DB1 RA-EP-02220 PROC 0012 SIPROEUE CORECING REVISED 1 0 0 EPIB DB1 PA-EP-02220 PROC 0013 SIMPLE CHANGE APPROVED 1 0 0 EPIB Use this document transmittal to update the identified documents and remove the superseded documents from use.

Page 1 of 14 Davis-Besse Nuclear Power Station EMERGENCY PLAN IMPLEMENTING PROCEDURE RA-EP-021 10 EMERGENCY NOTIFICATION REVISION 13 Prepared by: Patti J. Smith Procedure Owner: Emergency Response Manager Effective Date: 1 2/22/1 5 LEVEL OF USE:

IN-FIELD REFERENCE

2 RA-EP-021 10 Revision 13 TABLE OF CONTENTS 1.0 PtURPOSE...................................................... ...................................... 3

2.0 REFERENCES

....................................................................................... 3 3.0 DEFINITIONS ........................................................................................ 3 4.0 RE SPONSIBILITIES ........ *.................................................4 5.0 INITIATING CONDITIONS........................................................................ 4 6.0 PROCEDURE ........................................................................................ 5 6.1 Notification during a Security Event....................................................... 5 6.2 Notification of the Emergency Response Organization ................................. 5 6.3 Notification of the State and Counties.....................................................

6.4 Individual Contact of Emergency Responders............................................ 10 6.5 Notification of the NRC.................................................................... 11 7.0 FINAL CONDITIONS ............................................................................... 11 8.0 RECORDS............................................................................................ 12 ATTACHMENT 1. Emergency Position Checklist ....................................................... 13 COMMITMENTS........................................................................................... 14

3 ~RA-EP-021 10 Revision 13 1.0 PURPOSE To provide guidelines for notifying the Emergency Response Organization, offsite agencies, and the Nuclear Regulatory Commission (NRC) in accordance with the Davis-Besse Nuclear Power Station Emergency Plan.

2.0 REFERENCES

2.1 Developmental 2.1.1 Davis-B esse Nuclear Power Station Emergency Plan 2.2 Implementation 2.2.1 NOP-OP-1 015, Event Notification 2.2.2 DBNPS Emergency Plan Telephone Directory 2.2.3 DB-OP-02544, Security Events or Threats 2.2.4 RA-EP-00200, Emergency Plan Drill and Exercise Program 3.0 DEFINITIONS 3.1 COMPUTERIZED AUTOMATED NOTIFICATION SYSTEM (CANS) - A computer system used to notify designated personnel in the event of an emergency. This computer system has the following capabilities:

3.1.1 Contacting emergency response personnel through the use of pagers and the telephone system.

3.1.2 Accepting calls from authorized emergency responders.

3.1.3 Maintaining an updated list of Emergency Responders that have responded.

3.2 EMERGENCY RESPONSE ORGANIZATION (ERO) - The ERO is a trained team of employees who provide emergency response in the event of an emergency at the Davis-Besse Nuclear Power Station.

3.3 EMERGENCY RESPONSE ORGANIZATION ON CALL REPORT - This report lists the ERO On-call Positions indicating the On-call Duty assignment for the qualified individuals.

3.4 INTEGRATED ON CALL REPORT - This report lists ERO On-call Positions and the applicable corresponding Plant Duty Team positions. The report lists the ERO/Plant Duty Team responder with their applicable contact phone numbers.

3.5 ON-CALL DUTY RESPONDER - Responders that are filling the duty week assignment for their assigned ERO On-call position. On-call Duty responders shall be available to respond within 30 or 60 minutes during dayshift, and 60 or 120 minutes during off hours.

4 ~RA-EP-021 10 Revision 13 3.6 ON-COMING DUTY RESPONDER - On-coming responders are the secondary responders for their assigned ERO On-call position. On-coming responders shall be available to respond0 within twelve hours. These responders will rotate to On-call Duty responder at the start of the next week.

3.7 STANDBY RESPONDER - Standby responders are those responders not filling On-call Duty or On~coming duty for their assigned ERO On-call position. Standby responders have no response time responsibility. These responders will rotate to On-coming responder per their On-call Position schedule.

3.8 USER ID - Numbers assigned to designated individuals used to activate CANS.

3.9 SECURITY PIN CODE - A number assigned to designated individuals to provide for an additional level of security used to activate CANS.

3.10 INITIAL NOTIFICATION FORM - The form used when notifying the State and Counties of an emergency at the Davis-Besse Nuclear Power Station. The Initial Notification Form is also used when changing either the level of classification or the protective action recommendations.

3.11 PERIODIC UPDATE FORM - The form used when updating the State and Counties of the status of an emergency at the Davis-B esse Nuclear Power Station.

4.0 RESPONSIBILITIES 4.1 The Emergency Director shall be responsible for ensuring that Emergency Response Organization notification, offsite notifications, and NRC notifications are performed in accordance with this procedure.

4.2 The Emergency Director or designated alternate shall be responsible for the activation of the CANS upon declaration of an emergency classification.

4.3 The Emergency Response Manager shall be responsible for:

4.3.1 Review of documentation created from this procedure.

4.3.2 The corrective actions of any deficiencies found with the equipment.

5.0 INITIATING CONDITIONS 5.1 This procedure shall be implemented when any of the following have been declared:

5.1.1 Unusual Event 5.1.2 Alert 5.1.3 Site Area Emergency 5.1.4 General Emergency

5 RA-EP-021 10 Revision 13 6.0 PROCEDURE 6.1 Notification during a Security Event 6.1.1 If a security event is in progress then immediately implement DB-OP-02 544, Security Events or Threats to make initial notifications to the Emergency Response Organization (ERO), the NRC, and the State and Counties.

NOTE 6.2 During a non-security event, the priority for performing notification is as follows, however, steps may be performed concurrently:

1. Notification of ERO - Section 6.2.
2. Notification of State and Counties - Section 6.3.
3. Individual Contact of ERO - Sections 6.4.
4. Notification of NRC - Section 6.5.

Initial notification of the State and Counties or a change in Protective Actions is required within 15 minutes of declaration of an emergency or change in classification.

6.2 Notification of the Emergencv Response Organization NOTE 6.2.1

1. The following ERO positions have access for activating CANS:

Central Alarm Station (CAS) Operator (Security)

Security Shift Supervisor (Security)

Shift Manager (Control Room)

Emergency Assistant Plant Manager (Control Room)

Unit Supervisor (Control Room)

Shift Engineer (Control Room)

Emergency Planning Advisor (Emergency Operations Facility)

Emergency Offsite Manager (Emergency Operations Facility)

EOF Communications Equipment Operator (Emergency Operations Facility)

2. Control Room staff should notify the ERO if Security personnel are not available during a Security event.

6.2.1 To initiate callout of the ERO:

a. The Emergency Director shall direct the Central Alarm Station (CAS) operator or other designee listed in Note 6.2.1 to initiate callout of the ERO and provide them with the Emergency Classification.

6 ~RA-EP-021 10 Revision 13

b. The individual activating CANS shall perform the following:

NOTE 6.2.1 .b. 1 The ERO numeric group page is used to notify the ERO of a change in emergency classification from an Alert, Site Area Emergency, or a General Emergency.

1. REFER TO the ERO Notification Flow Chart in the Immediate Notification Numbers section of the Emergency Plan Telephone Directory to initiate callout of the ERO.

NOTE 6.2.1.b.2 Within 10 minutes an ERO pager should activate with displays of the selected classification. ERO pagers are located in CAS and in the Control Room.

2. Verify an ERO pager activates with the proper display:
a. IF the ERO pagers fail to respond, THEN contact the On Call Duty Emergency Response individual.

(Refer to the Integrated On Call Report)

b. Upon contact inquire if their pager has received the proper Emergency Classification Code.0
c. IF it is determined that the primary CANS is not working, THEN ensure Section 6.3, Notification of the State and Counties is being performed (Control Room personnel only),

AND REFER TO the ERO Notification Flow Chart in the Immediate Notification Numbers section of the Emergency Plan Telephone Directory to initiate callout of the ERO using the CANS backup number.

1. Verify an ERO pager activates with the proper display:
a. IF the ERO pagers fail to respond, THEN contact the On Call Duty Emergency Response individual. (Refer to the Integrated On Call Report)
b. Upon contact inquire if their pager received the proper Emergency Classification Code.

0

7 ~RA-EP-021 10 Revision 13

c. IF it is determined the backup CANS is not working, REFER TO the ERO Notification Flow Chart in the Immediate Notification Numbers section of the Emergency Plan Telephone Directory to initiate callout of the ERO using ERO numeric group page.
1. Verify an ERO pager activates with the proper display:
a. IF the ERO pagers fail to respond, THEN contact the On Call Duty Emergency Response individual. (Refer to the Integrated On Call Report)
b. Upon contact inquire if their pager received the proper Emergency Classification Code.
c. IF the primary CANS, the backup CANS, and the ERG numeric group page fail to respond, THEN proceed to Step 6.4, Individual Contact of Emergency Responders.
d. Inform the Emergency Director when CANS has been properly activated or if any system problems were encountered.

NOTE 6.2.1.b.3 The CANS printout is faxed to the Control Room fax, the Central Alarm Station (CAS) fax, and the EOF fax.

The CANS printout is emailed to Emergency Offsite Managers, Emergency Planning Advisors, and the EOF Conmmunications Equipment Operators.

3. IF the primary or backup CANS was activated, THEN. review the CANS Fax to ensure the ERO positions are being filled.
a. IF the positions are not being filled, THEN contact the On Call Duty Emergency Response individual.

(Refer to the Integrated On Call Report)

8 ~RA-EP-021 10 Revision 13 6.3 Notification of the State and Counties NOTE 6.3.1 Initial notification of the State and Counties is required within 15 minutes of the declaration of an emergency or a change in classification or a change in Protective Actions.

6.3.1 if making an initial notification, THEN the Emergency Director or designee shall fill out an FENOC Nuclear Power Plant Initial Notification Form (DBEP-0 10).

NOTE 6.3.2 Periodic updates are required as conditions change or hourly, at a minimum, unless the offsite agencies agree to forgo them.

6.3.2 IF making a periodic update, THEN the Emergency Director or designee shall fill out a FENOC Follow-Up/Periodic Update Notification Form (DBEP-009).

6.3.3 The Emergency Director or designee shall fill out a Davis-Besse Emergency Notification Coversheet (DBEP-0 12).

6.3.4 Perform the following on the Davis-Besse Emergency Notification Coversheet (DBEP-0 12):

  • Check box for FENOC Nuclear Power Plant Initial Notification Form or FENOC Follow-Up/Periodic Update Notification Form.
  • Check box for Actual Emergency or Drill.
  • Ensure signatures are obtained for the "Form completed by" and "accuracy verified by" sections.
  • Obtain Emergency Director review and approval of the FENOC Nuclear Power Plant Initial Notification Form or FENOC Follow-Up/Periodic Update Notification Form to release the information.
  • Provide the information to the communicator.

6.3.5 Activate the Davis-Besse 4-Way Phone. (Detailed instructions are contained in the Emergency Plan Telephone Directory).

a. IF the 4-Way is not operable, THEN obtain telephone numbers for the offsite agencies in the Immediate Notification section of the Emergency Plan Telephone Directory. Contact should be established in the following order:
1. Ottawa County
2. Lucas County
3. State of Ohio

9 ~RA-EP-021 10 Revision 13 6.3.6 As agencies answer, identify yourself by name and facility (Control Room, EOF) and record the following on the Davis-Besse Emergency Notification Coversheet (DBEP-012):

a. The agency notified.
b. Time of initial contact.
c. Completion time of call.
d. If the 4-Way Phone was used when making the notification.

6.3.7 Transmit the information from the approved FENOC Nuclear Power Plant Initial Notification Form or FENOC Follow-Up/Periodic Update Notification Form.

6.3.8 Sign the Davis-Besse Emergency Notification Coversheet (DBEP-0 12) and check the location on the form.

6.3.9 IF any of the required three agencies did not answer the 4-Way Phone, THEN contact them using the Immediate Notification section of the Emergency Plan Telephone Directory.

a. If any of the three offsite agencies were contacted using a means other than the 4-way Phone, request that the agency call back to verify the notification, and record the name of the individual(s) on the Davis-Besse Emergency Notification Cover Sheet (DBEP-012).

6.3.10 Telefax all completed forms to the Emergency Operations Facility.

10 RA-EP-021 10 Revision 13 6.4 Individual Contact of Emergency Responders 6.4.1 IF CANS and the pager system fail, 0

THEN the Emergency Director or designee shall obtain the following:

a. Attachment 1, Emergency Position Checklist
b. The ERO On-Call Report
c. The Emergency Plan Telephone Directory 6.4.2 Contact the positions listed on Attachment 1, Emergency Position Checklist, using the On Call Report to determine who is on-call. The Emergency Plan Telephone Directory lists all phone numbers available for these individuals.

NOTE 6.4.3 It is important that calls be as short and concise as possible in order to expedite the notification process.

6.4.3 Upon making contact inform the individual of the following:

a. Your name and title.
b. Basis for your call (CANS and pagers failed to initiate emergency notifications).
c. The classification.

6.4.4 Record time of contact, fitness for duty status, and estimated time of arrival on Attachment 1, Emergency Position Checklist.

11 RA-EP-021 10 Revision 13 6.5 Notification of the NRC NOTE 6.5.1 During a security event, accelerated notification to the NRC is accomplished in accordance with DB-OP-02544, Security Events or Threats.

6.5.1 Initial notification to the NRC should be made by the Control Room staff, unless directed otherwise by the Emergency Director.

6.5.2 Make initial notification to the NRC immediately after notification of the local and state agencies, but no later than one hour after any emergency declaration.

6.5.3 For all NRC notifications, fill out the Reactor Plant Event Notification Worksheet (NOP-OP-l1015-01), in accordance with NOP-OP- 1015, Event Notifications.

6.5.4 Notification to the NRC Operations Center should normally be made using the NRC Emergency Notification System (ENS) (red) phone.

a. IF using a phone other than the NRC ENS phone, THEN NRC notification may be made by obtaining the phone numbers listed in the Emergency Plan Telephone Directory, Immediate Notification Tab.

6.5.5 Transmit the information on the form.

6.5.6 Telefax all forms to the Emergency Operations Facility.

7.0 FINAL COND)ITIONS 7.1 The required personnel have been notified in accordance with the appropriate Emergency Classification.

7.2 Any communication system malfunctions have been reported to the Emergency Response Manager.

12 RA-EP-021 10 Revision 13 NOTE 8.0 All logs, documents and forms generated during the implementation of this procedure are to be retained and processed in accordance with RA-EP-02720, Recovery Organization.

8.0 RECORDS 8,1 The following records that are completed by this procedure shall be processed and retained as part of the Event Package in accordance with RA-EP-02720, Recovery Organization:

8.1.1 Davis-Besse Emergency Notification Coversheet (DBEP-0 12) 8.1.2 FENOC Nuclear Power Plant Initial Notification Form (DBEP-0 10) 8.1.3 FENOC Follow-Up/Periodic Update Notification Form (DBEP-009) 8.1.4 Reactor Plant Event Notification Worksheet (NOP-OP- 1015-01) 8.1.5 Emergency Position Checklist

13 RA-EP-021 10 Revision 13 ATTACHMENT 1: EMERGENCY POSITION CHECKLIST Page 1 of 1 Complete this attachment only if individual contact of the emergency responders is required. Log the appropriate information. Request the individual initiate their call-tree card for those positions indicated with an asterisk (*):

Emergency Title IEmergency I Per~son Notified Time IAbstained from Estim.rated Facility Notified alcohol for 5 hours5.787037e-5 days <br />0.00139 hours <br />8.267196e-6 weeks <br />1.9025e-6 months <br /> Time of and are Fit-for-Duty? Arrival 1 Emergency Assistant Plant Mgr CTRM LI Yes LI No 2 Dose Assessment Coordinator

  • EOF LI Yes I] No 3 Emergency Offsite Manager EOF Lj Yes LI No 4 Emergency Planning Advisor EOF Li Yes LI No 5 OSC Manager

8 I&C On-call Responder OSC LI Yes LI No ____

9 Mechanical On-call Responder OSC [] Yes LI No ___

10 TSC Engineering Manager TSC D]Yes LI No ____

11 Core/Thermal Hydraulic Eng TSC [] Yes I] No _____

12 Emergency Director EOF/TSC Li Yes LI No ____

13 NRC Liaison

  • EOF LI Yes LI No 14 State / County Communicator
  • EOF ___________L Yes LI No ____

15 TSC Electrical Engineer TSC [] Yes LI No 16 TSC I&C Engineer TSC LI Yes LI No 17 TSC Mechanical Engineer TSC _____L Yes LI No 18 Emergency RP Manager

  • TSC LI Yes LI No 19 Emergency Plant Manager TSC L] Yes LI No 20 RMT Coordinator

21 RTL Coordinator EOF EI Yes LI No 22 RecoVery Advisor

  • TSC LI Yes LI No 23 Emergency Director Advisor
  • EOF _______________L Yes LI No ____

24 Company Spokesperson

  • JIC _________ ___L Yes LI No ____

Performed by:

Date:

14 RA-EP-021 10 Revision 13 COMMITMENTS Section Reference Comments Notes 6.3.1 O 13969 Capability to notify State and Local agencies within 15 minutes after declaring an emergency.

Section 6.3 O 13462 Initial notifications should address all items in NUREG-0654, Rev. 1, Standard E Criterion 3.

Section 6.3 O 13532 Notification of the State of Ohio as well as the Counties.

O 13566 O 15211 Section 6.3 0 13532 Message content 0 15211 Section 6.5 O 13532 NRC Notification.

0 15211 Section 6.3 O 13534 Initial and follow up message content O 14152 0 15211 Note 6.2.1 CA 04-03371-01 CANS activation during a security event Section 6.2 CA 04-02854-01 CANS activation is performed at the direction of the Shift Manager

Page 1 of 23 Davis-Besse Nuclear Power Station EMERGENCY PLAN IMPLEMENTING PROCEDURE RA-EP-02220 EMERGENCY OPERATIONS FACILITY ACTIVATION AND RESPONSE REVISION 13 Prepared by: P. J. Smith Procedure Owner: Emergency Response Manager Effective Date: 12/22/1 5 LEVEL OF USE:

IN-FIELD REFERENCE

2 RA-EP-02220 Revision 13 TABLE OF CONTENTS Page 1.0 PURPOSE...................................................................... 3

2.0 REFERENCES

................................................................ 3 3.0 DEFINITIONS ................................................................ 3 4.0 RESPONSIBILITIES ......................................................... 4 5.0 INITIATING CONDITIONS................................................. 5 6.0 PROCEDUJRE.................................................................. 6 6.1 Emergency Director Advisor......................................... 6 6.2 Emergency Planning Advisor ........................................ 6 6.3 State and County Communicator.................................... 10 6.4 NRC Liaison........................................................... 10 7.0 FINAL CONDITIONS........................................................ 13 8.0 RECORDS..................................................................... 13.

ATTACHMENT 1: SIREN SYSTEM ............................................... 14 ATTACHMENT 2: PREPARING FOR NRC INCIDENT RESPONSE TEAM 21 ATTACHMENT 3: CANS RESPONSE VERIFICATION......................... 22 COMMITMENTS ..................................................................... 23

3 RA-EP-02220 Revision 13 1.0 PURPOSE This procedure outlines the steps required for activation, operation, and deactivation of the Emergency Operations Facility (EOF) as performed by the Emergency Director Advisor, Emergency Planning Advisor, State and County Communicator and the NRC Liaison.

2.0 REFERENCES

2.1 Developmental 2.1.1 Davis-Besse Nuclear Power Station Emergency Plan 2.2 Implementation 2.2.1 RA-EP-0 1500, Emergency Classification 2.2.2 RA-EP-020 10, Emergency Management 2.2.3 RA-EP-02 110, Emergency Notification 2.2.4 RA-EP-02720, Recovery Organization 2.2.5 NOP-LP-5005, FENOC Siren Testing and Maintenance Procedure 2.2.6 DBNPS Emergency Plan Telephone Directory 2.2.7 RA-EP-02270, Facilities Support 2.2.8 RA-EP-023 10, Technical Support Center Activation and Response 2.2.9 NOP-LP- 1002, Fitness for Duty Program 2.2.10 DBBP-EMER-0050, Owner Controlled Area Public Address System (OCA PA) 2.2.11 NORM-LP-5 005, Emergency Operations Facility Reference Manual 3.0 DEFINITIONS 3.1 CENTRAL COMPUTER UNIT (CCU) - The personal computer that the Federal Signal Corporation's SFCDWARE Software resides on and provides for the interface to the Remote Terminal Units (RTU) at each siren. This terminal provides for activation, polling and monitoring of the siren system. The CCUs are at the following locations:

Ottawa County Sheriffs' Office, Davis-Besse Emergency Operations Facility, Davis-Besse Administration Building, and at the Oak Harbor 500-Foot Tower Site.

3.2 COMPUTERIZED AUTOMATED NOTIFICATION SYSTEM (CANS) - A computer developed and used to control notification of designated personnel in the event of an emergency.

4 RA-EP-02220 Revision 13 3.3 EMERGENCY OPERATIONS FACILITY (EOF) - An area located at the Lindsey Emergency Response Facility (LERF) which is equipped to facilitate the control and coordination of emergency activities and assessment.

3.4 LINDSEY EMERGENCY RESPONSE FACILITY - An area located at 1240 South Main Street, Lindsey, Ohio 43442, which is equipped to facilitate the control and coordination of emergency activities and assessments. The LERF houses the EOF, Alternate TSC, and provides a muster area for additional ERO personnel.

3.5 MASTER RESET - A command that resets the Remote Terminal Units (RTU) registers in each siren.

4.0 RESPONSIBILITIES 4.1 The Emergency Director Advisor is responsible for:

4.1.1 Assisting the Emergency Director in performing his emergency responsibilities.

4.1.2 Providing periodic approved information to the Company Spokesperson for release to the general public.

4.1.3 On failure of the Computerized Automated Notification System (CANS) call out emergency staffing as specified in the call tree section of the Emergency Plan Telephone Directory.

4.2 The Emergency Planning Advisor is responsible for:

4.2.1 Verifying proper operation of CANS and appropriate EOF staff notifications of

  • the emergency classification.

4.2.2 Verifyiing proper operation of the offsite sirens.

4.2.3 Providing Initial Notifications and Periodic Updates to offsite agencies.

4.2.4 Interacting with the liaisons that arrive at the EOF from the State of Ohio, and Ottawa and Lucas Counties.

4.3 The State and County Communicator is responsible for:

4.3.1 Maintaining communication with Ottawa County, Lucas County and the State of Ohio.

4.3.2 On failure of the Computerized Automated Notification System (CANS) call out emergency staffing as specified in the call tree section of the Emergency Plan Telephone Directory.

0

5 RA-EP-02220 Revision 13 4.4 The NRC Liaison is responsible for:

4.4.1 Interfacing with the NRC.

4.4.2 Interfacing with the NRC Incident Response Team when it arrives at Davis-Besse.

4.4.3 On failure of the Computerized Automated Notification System (CANS) call out emergency staffing as specified in the call tree section of the Emergency Plan Telephone Directory.

5.0 INITIATING CONDITIONS This procedure shall be used when:

5.1 An emergency has been declared and classified as an Alert, a Site Area Emergency, or a General Emergency.

5.2 Determined by the Emergency Director.

6 RA-EP-02220 Revision 13 6.0 PROCEDURE Steps in this procedure may be performed simultaneously.

6.1 Emergency Director Advisor 6.1.1 On failure of the Computerized Automated Notification System (CANS) call out emergency staffing as specified in the call tree section of the Emergency Plan Telephone Directory.

6.1.2 Assist the Emergency Director in turnover of responsibilities from the Control Room.

6.1.3 Follow events closely, be prepared to brief and assist the Emergency Director concerning procedural requirements relating to the emergency (see RA-EP-020 10, Emergency Management).

6.1.4 Act as a liaison between the Emergency Director and Company Spokesperson.

6.1.5 Review checklists and notifications for completeness, as appropriate.

6.1.6 Assess the need to upgrade or downgrade the emergency in accordance with RA-EP-0 1500, Emergency Classification.

6.2 Emergency Planning Advisor 6.2.1 Activation

a. Verify with the Emergency Offsite Manager that the minimum required EOF staffing as identified in RA-EP-020 10, Emergency Management, Attachment 3 has been met.
b. Ensure each EOF position required for minimum staffing and assigned to the EOF has telephone communications available. The 4-Way Phone is not activated until after the facility is activated and has responsibility for communications. Contact the FE Help Desk for assistance with any equipment issues.

6.2.2 Operation

a. WHEN the EOF is activated, AND the Emergency Director responsibilities have been transferred to the EOF, THEN perform the following:
1. Obtain concurrence fr~om the Emergency Offsite Manager to activate the 4-Way Phone.

7 RA-EP-02220 Revision 13

a. Advise the State and County Communicator to establish and maintain communications with Ottawa and Lucas Counties, and the State of Ohio. Refer to Step 6.3.2.
2. Assume responsibility for preparing required notifications to the State of Ohio, Ottawa County, and Lucas County. Ensure all FENOC Nuclear Power Plant Initial Notification Forms and FENOC Follow-up/Periodic Update Notification Forms are approved by the Emergency Offsite Manager and approved by the Emergency Director prior to transmittal to offsite agencies. Perform offsite notifications per RA-EP-02 110.
a. FENOC Nuclear Power Plant Initial Notification Forms are transmitted to State and County agencies WITHIN 15 MINUTES of:
  • Change in Emergency Classification
  • Change in Protective Action Recommendation
  • If plant condition degrade and a higher classification is declared before the notifications are made for the lesser declaration, the licensee should update the notification to reflect the higher emergency declaration and complete the updated notification within 15 minutes of the lesser emergency declaration.
  • If the notification cannot be updated and completed within 15 minutes of the lesser emergency declaration, the ERO should make the notification for the lesser emergency within 15 minutes of its declaration. The notification could contain the caveat that a change in classification was forthcoming. In parallel, the licensee should prepare the notification for the higher emergency classification and make an additional notification within 15 minutes of its declaration.
b. FENOC Follow-up/Periodic Update Notification Forms are provided to State and County agencies:
  • Immediately following the transmittal of an FENOC Nuclear Power Plant Initial Notification Form for a General Emergency
  • Immediately following the transmittal of an FENOC Nuclear Power Plant Initial Notification Form for a change in Protective Action Recommendations
  • Approximately hourly
  • As conditions change
3. Notify the Institute of Nuclear Power Operations (INPO) as soon as reasonably practical, but within a goal of 1 hour1.157407e-5 days <br />2.777778e-4 hours <br />1.653439e-6 weeks <br />3.805e-7 months <br /> of the emergency declaration using utilizing form DBEP-03 10, INPO Event Notification Form.

8 RA-EP-02220 Revision 13

4. Ensure that the GaiTronics volume is audible in the EOF.O
5. Ensure status boards are being maintained current.
6. Ensure emergency responders sign in on the Emergency Organization sign in board.
7. Contact the Technical Support Center or utilize the time on a cellular phone to determine the need to synchronize the EOF Digital Clock. If required, synchronize the time on the EOF digital clock with the digital clock in the Technical Support Center or with a cellular phone using the posted instructions.
8. Establish initial siren system status. Refer to ATTACHMENT 1, SIREN SYSTEM, A. INITIAL SYSTEM ASSESSMENT
9. If Emergency Response Organization (ERO) positions in the Emergency Response Facilities are not filled, then verify individuals have responded to the CANS. Refer to Attachment 3, CANS Response Verification.
10. Discuss with the Dose Assessment Coordinator the need to establish personnel monitoring at the Lindsey Emergency Response Facility.
b. IF there is a change in Classification or a change in Protective Action Recommendation (PARs)

THEN perform the following:

1. Transmit an approved FENOC Nuclear Power Plant Initial Notification Form to State and County agencies WITHIN 15 MINUTES.
2. Provide an approved FENOC Follow-up/Periodic Update Notification Form and, as appropriate, a release pathway drawing and a plume footprint to the State and County agencies immediately following the transmittal of an FENOC Nuclear Power Plant Initial Notification form for a General Emergency or a change in Protective Action Recommendation.
3. Provide a FENOC Follow-up/Periodic Update Notification Form to the State and County agencies approximately hourly or as conditions change.
4. Notify the ERO of the change in classification in accordance with RA-EP-021 10, Emergency Notification.
5. Notify the Institute of Nuclear Power Operations (INPO) of the change in classification utilizing form DBEP-03 10, INPO Event Notification Form.
6. When directed by the Emergency Offsite Manger, make an announcement over the Owner Controlled Area Public Address System. I

9 RA-EP-02220 Revision 13 Refer to DBBP-EMER-0050, Owner-Controlled Area (OCA) Public Address System for additional information.

a. IF the Owner Controlled Area Public Address System cannot be activated from the EOF, contact the Emergency Facilities Services Manager in the TSC or contact the Secondary Alarm Station (SAS) to make the announcement.
7. When directed, communicate meteorological condition changes to the State of Ohio, Ottawa County, and Lucas County.
8. When siren system status is requested by Ottawa or Lucas County and with the EOM's concurrence, refer to ATTACHMENT 1: SIREN SYSTEM, B. DETERMINING STATUS FOLLOWING SIREN SYSTEM ACTIVATION.
9. Ensure protective actions implemented by the Counties are posted on the Protective Actions Taken Status Board
a. Provide periodic briefings to and answer questions from the EMA Liaisons in the EOF.
b. Provide assistance to the Emergency Offsite Manager, as needed.
c. IF any personnel contaminations are detected at the Lindsey Emergency Response Facility, THEN request the TSC Emergency Radiation Protection Manager dispatch RP Technicians to respond to provide personnel monitoring and decontamination support.
d. If a high-level alarm is received on the Decontamination Tank at the Lindsey Emergency Response Facility, then perform the following:
1. If the Decontamination Room has never been used for personnel decontamination, then the contents of the tank may be pumped via normal methods.
2. if decontamination efforts are being performed, stop the activities adding water to the Decontamination Tank.
3. if personnel decontamination efforts are still necessary, consider relocating these activities to the Lindsey Service Center, in accordance with RA-EP-02550, Offsite Personnel And Vehicle Monitoring And Decontamination.
4. If the Decontamination Room has been used for personnel decontamination, then contact the Emergency Radiation Protection Manager in the TSC for guidance and protocol for pumping the contents of the Decontamination Tank.

10 RA-EP-02220 Revision 13 6.2.3 Deactivation

a. Upon deactivation of the EOF, inform the State of Ohio, Ottawa and Lucas Counties using an Initial Notification Form in accordance with RA-EP-02 110, Emergency Notification.
b. Notify the ERO of the "All Clear" in accordance with RA-EP-021 10, Emergency Notification.

6.3 State and County Communicator 6.3.1 Activation

a. On failure of the Computerized Automated Notification System (CANS) call out emergency staffing as specified in the call tree section of the DBNPS Emergency Plan Telephone Directory.

6.3.2 Operation

a. When notified by the Emergency Planning Advisor, establish and maintain communications with Ottawa and Lucas Counties, and the State of Ohio.
1. Activate the 4-Way Phone in accordance with the Emergency Plan Telephone Directory, section 2.1.11.

6.4 NRC Liaison 6.4.1 Activation

a. Respond to Computerized Automated Notification System (CANS) b.* On failure of the CANS call out emergency staffing as specified in the call tree section of the DBNPS Emergency Plan Telephone Directory.

NOTE 6.4.1.c Extensions of the Emergency Notification System (ENS) are located in the Control Room, Shift Engineer's Office, TSC, EOF and the NRC Conference Room (DBAB Room 110).

If the Control Room is communicating with the NRC you will be able to monitor the communications.

c. Verify that the primary and backup Emergency Notification System (ENS) telephones at the NRC Liaison Desk have dial tone by picking up the receiver. If no dial tone is present notify the Emergency Offsite Manager.

0

11 RA-EP-02220 Revision 13

d. Begin a personal log for the NRC Liaison position. Ensure key interactions with the NRC are documented in your log. All documents should have time, date and author/sources.
e. Verify that the Emergency Response Data System (ERDS) is transmitting data to the NRC by contacting the TSC Computer Technician, or by using RA-EP-023 10, TSC Activation and Response, Attachment 1. If the ERDS is not transmitting data to the N-RC, refer to Attachment 1 of RA-EP-023 10.

6.4.2 Operation

a. Determine the Emergency Action Level (EAL) that the event was classified under.
b. Verify initial notification to the NRC was made and obtain a copy of Reactor Plant Event Notification Worksheet(s), (Form NOP-OP- 1015-01) that have been transmitted to the NRC during this event. If the Control Room has not faxed a copy of the Event Notification Worksheet, request that the EOF Operations Advisor obtain a copy from the Control Room.
c. If the initial NRC notification has not been made notify the Emergency Offsite Manager.
d. Periodically (at least once every hour) complete a Reactor Plant Event Notification Worksheet (NOP-OP- 1015-01) and have it peer checked, then update the NRC via the ENS. Update the EOF Task Board following each periodic briefing. Ensure that items that require follow-up/feedback are posted on the EOF Task Board. Suggested issues for discussion:
1. Emergency Classification
2. Status/condition of the three fission product barriers
3. Status of reactor (operating/shutdown/cooldown/shutdown margin)
4. Status of station emergency response facility activation
5. Status of a radiological releases to the environment

[] Wind direction

[] Stability Class

[] Expected release duration of the (2 hours2.314815e-5 days <br />5.555556e-4 hours <br />3.306878e-6 weeks <br />7.61e-7 months <br /> default)

6. Source of the release
7. Station onsite protective actions
8. Station offsite protective action recommendations
9. Protective actions taken by offsite agencies
10. Requests for offsite medical, fire or law enforcement assistance
11. Issues that have received media attention

12 RA-EP-02220 Revision 13

e. Request information from the NRC on:
1. Potential or expected NRC response to the station
2. Potential or expected NRC response to the State of Ohio Emergency Operations Facility
3. Requests for additional information
f. Participate in periodic EOF briefings. Highlight key interactions with the NRC, questions and NRC dispatch of personnel to the stations.
g. When advised that the NRC is dispatching an Incident Response Team refer to ATTACHMENT 2: PREPARING FOR NRC INCIDENT RESPONSE TEAM (IIRT) and notify the following of the pending NRC Team arrival:
1. Emergency Director
2. Emergency Offsite Manager
3. Emergency Plant Manager
4. Emergency Security Manager
5. Company Spokesperson 6.4.3 Deactivation
a. Prepare a list of NRC issues and provide turnover to the Manager, 0 Regulatory Compliance or his designee.
b. Review RA-EP-02720, Recovery Organization procedure.
c. For significant events consider the following activities:
1. Sequester of failed equipment not necessary for safe shutdown for NRC inspection before repair.
2. Prepare a location and list of appropriate personnel for interview.
3. Prepare a list of names, titles and telephone numbers of key personnel in the recovery organization.

13 RA-EP-02220 Revision 13

. 7.0 FINAL CONDITIONS This procedure shall be terminated when:

7.1 Plant conditions are such that the emergency has been downgraded to Unusual Event, or terminated; and the EOF has been deactivated.

7.2 All equipment and useable supplies have been returned to their storage location.

7.3 The EOF staff has been relieved of all duties associated with the operation of the EOF.

7.4 The Company Spokesperson has been fully briefed on plant status and planned recovery actions.

NOTE: 8.0 All logs, documents and forms generated during the implementation of this procedure are to be retained and processed in accordance with RA-EP-02720, Recovery Organization.

8.0 RECORDS 8.1 The following records that are completed by this procedure shall be processed and retained as part of the Event Package in accordance with RA-EP-02720, Recovery Organization.

8.1.1 PNS Siren Computer Map Report Form (DBEP-05 1).

8.1.2 NRC Incident Response Team (IIRT) Form (DBEP-306) 8.1.3 CANS Validation Checklist (DBEP-3 05) 8.1.4 Reactor Plant Event Notification Worksheet (NOP-OP-1015-01) 8.1.5 INPO Event Notification Form (DBEP-03 10)

14 RA-EP-02220 Revision 13 ATTACHMENT 1: SIREN SYSTEM (Page 1 of 7)

A. INITIAL SYSTEM ASSESSMENT The Davis-Besse Prompt Notification System is comprised of 54 sirens. Sirens 1-5 are located in Jerusalem Township in eastern Lucas County; the remaining 49 sirens are in Ottawa County. Ottawa County has 32 non-EPZ sirens in addition to the 49 EPZ sirens. The EPZ sirens are those found in the red box on the siren map displayed on the Central Computer Unit (CCU).

Each morning at approximately 0500 the CCU automatically polls the sirens. The CCU will automatically poll the siren a second time if the siren does not respond to the initial polling. The siren will not respond to the poll if there is radio traffic on or near the siren frequency in the vicinity of the individual siren site.

For additional information refer to RA-EP-00420, Response to Prompt Notification System Malfunction.

NOTE: A. 1 When the siren monitoring program is accessed remotely through the use of the modem, the Map Display may turn grey or partial grey and may need to be minimized, if necessary.

1. Reset the siren monitoring program display by:
a. Verifying the Federal Signal SFCDWARE software is open and maximized.
b. Verifying the Map Display is open and sized so the Federal Signal SFCDWARE software toolbar is visible.

NOTE: A.2 When the siren monitoring program is on the "Map Display" screen, additional information about the colored dots can be obtained by opening the "Legend" Window. Detailed information about each siren can be obtained by positioning the pointer on the numbered siren dot and left clicking the mouse.

2. From the EOF Central Computer Unit (CCU), review the siren status by:
a. Obtaining a copy of the PNS Siren Computer Map Report Form (DBEP-05 1).

15 RA-EP-02220 Revision 13 ATTACHMENT 1: SIREN SYSTEM (Page 2 of 7)

b. From the siren computer if not already selected, select the Map screen from the upper tool bar.

NOTE: A.2.c The third line of the individual siren "Status Detail FCT" window labeled "Last Conun" will indicate the last date and time that the siren communicated with the CCU.

c. For any siren that indicates a communication failure (Purple) poll the siren again by selecting the individual siren from the map. When the individual siren "Status Detail FCT" window opens, select Poll to poll this siren. If the siren does not respond poll the individual siren a second time. After three attempts indicate that the siren has a communications failure.
d. Observe the color of the "Map Display" dots and record the numbers of those sirens (dots) that are not solid green or solid blue on the PNS Siren Computer Map Report Form (DBEP-05 1).
e. Advise the Emergency Offsite Manager (EOM) of any abnormal indications.
1. Ensure that the abnormal indication is entered into the facility log.
2. Advise the affected county of the siren(s) with abnormal indication to allow them to focus resources in the area if route alerting is required.

NOTE A.2.e.3 If corporate dispatches a siren vendor into the 10 mile EPZ then ensure that if conditions become hazardous that he/she is advised to evacuate the EPZ.

3. If the desire is to repair the siren requeste that the Policy Loop Communicator contact the corporate Emergency Preparedness representative and request support.
f. With concurrence of the EOM, reset the "Map Display" by selecting Reset Map on the upper tool bar.
1. Periodically check the "Map Display" and report any changes to the EOM.

16 RA-EP-02220 Revision 13 ATTACHMENT 1: SIREN SYSTEM (Page 3 of 7)

B. DETERMINING STATUS FOLLOWING SIREN SYSTEM ACTIVATION

1. When requested by Ottawa or Lucas County and with the EOM's concurrence, use the CCU to determine the preliminary results of the siren activation:
a. Obtain a copy of the PNS Siren Computer Map Report Form (DBEP-05 1).
b. Select Poll All from the upper tool bar. Left clicking on Poll All will initiate the polling sequence.
c. After the polling is complete (approximately 12 minutes), observe the color of the "Map Display" dots and record the numbers of those sirens (dots) that are not solid green on the PNS Siren Computer Map Report Form (DBEP-05 1).
d. For any siren that indicates a communication failure (Purple), poll the siren again by selecting the individual siren from the map. When the individual siren "Status Detail FCT" window opens select Poll to poll this siren. If the siren does not respond, poll the individual siren a second time.

After a total of three attempts indicate that the siren has a communications failure.

e. Advise the Emergency Offsite Manager (EOM) of any abnormal indications. Then communicate this information to the requesting offsite agency.
1. Ensure that the abnormal indication is entered into the facility log.
2. Advise the affected county of the siren(s) with abnormal indication to allow them to focus resources in the area if route alerting is required.

NOTE B. 1.e.3 If corporate dispatches a siren vendor into the 10 mile EPZ then ensure that if conditions become hazardous that he/she is advised to evacuate the EPZ.

3. If the desire is to repair the siren requeste that the Policy Loop Communicator contact the corporate Emergency Preparedness representative and request support.

17 RA-EP-02220 Revision 13 ATTACHMENT 1: SIREN SYSTEM (Page 4 of 7)

2. To verify the preliminary results of the siren activation:
a. Print out the RTU report as follows:
1. Select "Reports" from the upper toolbar of the Federal Signal Corporation SFCD WARE window. The Map Display may need to be temporarily minimized.
2. Select "Current RTU Status"
3. Select "Print Report"
4. Close "Current RTU Status Report" dialog box NOTE: B.2.b The report will print out data for all EPZ and non-EPZ sirens.
b. Review the report verifying that the EPZ sirens indicate:

3-Minute Sounding Last Function 3 MIN STEADY Current Pass Rotation Pass

c. Immediately notify the Emergency Offsite Manager or his designee of any siren that does not list the indications described in step B.2.b above.
d. Reset the RTUs as follows:
1. Select "Activate" from the Map Display toolbar.
2. When the prompt for password appears, enter "TEST". The password is case sensitive.
3. Select "Exit"
4. Select "SIREN MASTER RESET"
5. The computer will indicate that you are about to sound the sirens. Select "OK"

18 RA-EP-02220 Revision 13 ATTACHMENT 1: SIREN SYSTEM (Page 5 of 7)

6. Close the siren activation window.
7. The computer will send the "SIREN MASTER RESET"'

command three consecutive times.

NOTE: B.2.e A Master Reset followed by a poil should reset all online CPU maps to GREEN with the exception of any siren that is not communicating.

e. Wait approximately one minute and verify the master reset by polling the sirens:
1. Reset the map by selecting "Reset Map" from the Map Display toolbar.
2. Select Poll All from the upper tool bar. Left clicking on Poll All will initiate the polling sequence.
3. For any siren that indicates a communication failure (Purple),

poll the siren again by selecting the individual siren from the map. When the individual siren "Status Detail FCT" window opens, select Poll to poll this siren. If the siren does not respond, poll the individual siren a second time. After a total of three attempts indicate that the siren has a communications failure.

4. Advise the Emergency Offsite Manager (EOM) of any abnormal indications.
f. After the system has completed the poll, then print out the RTU report as follows:
1. Select "Reports" from the upper toolbar of the Federal Signal Corporation SFCD WARE window.
2. Select "Current RTU Status"
3. Select "Print Report"
4. Close "Current RTU Status" dialog box

19 RA-EP-02220 Revision 13 ATTACHMENT 1: SIREN SYSTEM (Page 6 of 7)

g. Review the report verifying that the EPZ sirens indicate:

SIRENS MASTER RESET Last Function Standby Current Reset Rotation Reset

h. Advise the Emergency Offsite Manager (EOM) of any abnormal indications.
3. Cancel Poll All
a. If the need occurs during the automatic polling sequence to cancel the "Poll All" perform the following:
1. Select "Activate" from the upper toolbar.
2. When prompted for a password press "Enter", no password is required.
3. Select "Cancel Poll" from the upper toolbar.
4. Close the "Activation" window.
4. With concurrence of the EOM reset the "Map Display" by selecting Reset Map on the upper tool bar. All siren dots should change to blue.
5. Periodically check the "Map Display" and report any changes to the EOM.

C. ACTIVATING THE SIREN SYSTEM

1. If directed by Ottawa County to sound the sirens, perform the following:
a. Obtain from Ottawa County what sirens should be activated.
b. Obtain the password from the Emergency Plan Telephone Directory, Section 2.1, Immediate Notification
c. Select Activate from the upper toolbar
d. When prompted, enter the Prompt Notification System Status Logger password (Passwordis case sensitive), and select Exit

20 RA-EP-02220 Revision 13 ATTACHMENT 1: SIREN SYSTEM (Page 7 of 7)

NOTE C. 1.e Ottawa County activates all 82 sirens in Ottawa County.

Davis-Besse activates the 54 EPZ sirens (49 Ottawa County and 5 Lucas County sirens).

e. Select the desired siren activation group, and select, OK.
f. Close window.

0

21 RA-EP-02220 Revision 13 ATTACHMENT 2:

PREPARING FOR NRC INCIDENT RESPONSE TEAM (IRT)

Page 1 of 1

1. Using the NRC Incident Response Team (LRT) Form (DBEP-3 06) obtain as much information as possible.
2. Obtain from the Emergency Offsite Manager recommended route/requirements to the Emergency Operations Facility at the Lindsey Emergency Response Facility and for entering the 10-mile emergency planning zone.
3. Obtain information on NRC IRT itinerary, including place (airport) and estimated time of arrival (ETA). Advise the NRC of any special routing considerations and provide directions to the Emergency Operations Facility at the Lindsey Emergency Response Facility. Request that the NRC IRT team report to the EOF for an initial briefing.
4. Notify the Emergency Offsite Manager that a NRC JIRT is being dispatched and request that the local law enforcement be advised.
5. Coordinate with the Emergency Security Manager to make arrangements for protected area and TSC access for the NRC IRT team members.
6. Ensure that arrangements are made for an initial briefing for the NRC IRT upon their arrival.
7. Obtain Emergency Offsite Manager permission to call in additional personnel, as necessary, for technical briefings and to serve as liaisons and as escorts for unbadged NRC personnel. (Note:

Personnel who are being called in shall comply with NOP-LP-1002, Fitness for Duty Program guidelines).

8. Request that the Emergency Security Manager ensures that individuals called-in will be granted access to the TSC. Confi-n that their site access requirements are current.

22 RA-EP-02220 Revision 13 ATTACHMENT 3:

CANS RESPONSE VERIFICATION Page 1 of 1 NOTE A.

The CANS Report is faxed / emailed 30 minutes after the system is activated and every 30 minutes for up to 2 hours2.314815e-5 days <br />5.555556e-4 hours <br />3.306878e-6 weeks <br />7.61e-7 months <br />.

A. Obtain the CANS Report from the BOF fax machine located by the PR Communicator.

NOTE A. 1 The CANS Report is emailed to the Emergency Offsite Managers, the Emergency Planning Advisors, and the BOF Communications Equipment Operators.

1. If the CANS Report was not received on the fax machine, then obtain the report by:
  • Logging into your windows network account using a company business network computer.
  • Open your email application.
  • Look for an email from "davisbesse" with a subject line similar to "ALERT Communicator NXT Completion Report."
  • If the CANS Report is not received in your email, then refer to Section 2.1 Immediate Notification Section in the Emergency Plan Telephone Directory to contact Cassidian Customer Support for assistance in obtaining the report.

B. Use the CANS Report to determine if all positions have responded. Compare the CANS Report to the CANS Validation Checklist, DBEP-305, if needed.

C. Notify the Emergency Offsite Manager of CANS status and status of the emergency response organization callout.

23 RA-EP-02220 Revision 13 COMMITMENTS Section Reference Comments None None None END

LIZ

-F Davis-BesseENOC Power Station Transmittal Report Page 1 of 1 Data Date Time: 12/22/2015 07:05:32 AM Trnsita DB-P-2112POC0010SMPL-CANE5APRVE Trnmta D0e 10 22205PI0B4A DB1 RA-EP-02220 PROC 0012 SIPROEUE CORECING REVISED 1 0 0 EPIB DB1 PA-EP-02220 PROC 0013 SIMPLE CHANGE APPROVED 1 0 0 EPIB Use this document transmittal to update the identified documents and remove the superseded documents from use.

Page 1 of 14 Davis-Besse Nuclear Power Station EMERGENCY PLAN IMPLEMENTING PROCEDURE RA-EP-021 10 EMERGENCY NOTIFICATION REVISION 13 Prepared by: Patti J. Smith Procedure Owner: Emergency Response Manager Effective Date: 1 2/22/1 5 LEVEL OF USE:

IN-FIELD REFERENCE

2 RA-EP-021 10 Revision 13 TABLE OF CONTENTS 1.0 PtURPOSE...................................................... ...................................... 3

2.0 REFERENCES

....................................................................................... 3 3.0 DEFINITIONS ........................................................................................ 3 4.0 RE SPONSIBILITIES ........ *.................................................4 5.0 INITIATING CONDITIONS........................................................................ 4 6.0 PROCEDURE ........................................................................................ 5 6.1 Notification during a Security Event....................................................... 5 6.2 Notification of the Emergency Response Organization ................................. 5 6.3 Notification of the State and Counties.....................................................

6.4 Individual Contact of Emergency Responders............................................ 10 6.5 Notification of the NRC.................................................................... 11 7.0 FINAL CONDITIONS ............................................................................... 11 8.0 RECORDS............................................................................................ 12 ATTACHMENT 1. Emergency Position Checklist ....................................................... 13 COMMITMENTS........................................................................................... 14

3 ~RA-EP-021 10 Revision 13 1.0 PURPOSE To provide guidelines for notifying the Emergency Response Organization, offsite agencies, and the Nuclear Regulatory Commission (NRC) in accordance with the Davis-Besse Nuclear Power Station Emergency Plan.

2.0 REFERENCES

2.1 Developmental 2.1.1 Davis-B esse Nuclear Power Station Emergency Plan 2.2 Implementation 2.2.1 NOP-OP-1 015, Event Notification 2.2.2 DBNPS Emergency Plan Telephone Directory 2.2.3 DB-OP-02544, Security Events or Threats 2.2.4 RA-EP-00200, Emergency Plan Drill and Exercise Program 3.0 DEFINITIONS 3.1 COMPUTERIZED AUTOMATED NOTIFICATION SYSTEM (CANS) - A computer system used to notify designated personnel in the event of an emergency. This computer system has the following capabilities:

3.1.1 Contacting emergency response personnel through the use of pagers and the telephone system.

3.1.2 Accepting calls from authorized emergency responders.

3.1.3 Maintaining an updated list of Emergency Responders that have responded.

3.2 EMERGENCY RESPONSE ORGANIZATION (ERO) - The ERO is a trained team of employees who provide emergency response in the event of an emergency at the Davis-Besse Nuclear Power Station.

3.3 EMERGENCY RESPONSE ORGANIZATION ON CALL REPORT - This report lists the ERO On-call Positions indicating the On-call Duty assignment for the qualified individuals.

3.4 INTEGRATED ON CALL REPORT - This report lists ERO On-call Positions and the applicable corresponding Plant Duty Team positions. The report lists the ERO/Plant Duty Team responder with their applicable contact phone numbers.

3.5 ON-CALL DUTY RESPONDER - Responders that are filling the duty week assignment for their assigned ERO On-call position. On-call Duty responders shall be available to respond within 30 or 60 minutes during dayshift, and 60 or 120 minutes during off hours.

4 ~RA-EP-021 10 Revision 13 3.6 ON-COMING DUTY RESPONDER - On-coming responders are the secondary responders for their assigned ERO On-call position. On-coming responders shall be available to respond0 within twelve hours. These responders will rotate to On-call Duty responder at the start of the next week.

3.7 STANDBY RESPONDER - Standby responders are those responders not filling On-call Duty or On~coming duty for their assigned ERO On-call position. Standby responders have no response time responsibility. These responders will rotate to On-coming responder per their On-call Position schedule.

3.8 USER ID - Numbers assigned to designated individuals used to activate CANS.

3.9 SECURITY PIN CODE - A number assigned to designated individuals to provide for an additional level of security used to activate CANS.

3.10 INITIAL NOTIFICATION FORM - The form used when notifying the State and Counties of an emergency at the Davis-Besse Nuclear Power Station. The Initial Notification Form is also used when changing either the level of classification or the protective action recommendations.

3.11 PERIODIC UPDATE FORM - The form used when updating the State and Counties of the status of an emergency at the Davis-B esse Nuclear Power Station.

4.0 RESPONSIBILITIES 4.1 The Emergency Director shall be responsible for ensuring that Emergency Response Organization notification, offsite notifications, and NRC notifications are performed in accordance with this procedure.

4.2 The Emergency Director or designated alternate shall be responsible for the activation of the CANS upon declaration of an emergency classification.

4.3 The Emergency Response Manager shall be responsible for:

4.3.1 Review of documentation created from this procedure.

4.3.2 The corrective actions of any deficiencies found with the equipment.

5.0 INITIATING CONDITIONS 5.1 This procedure shall be implemented when any of the following have been declared:

5.1.1 Unusual Event 5.1.2 Alert 5.1.3 Site Area Emergency 5.1.4 General Emergency

5 RA-EP-021 10 Revision 13 6.0 PROCEDURE 6.1 Notification during a Security Event 6.1.1 If a security event is in progress then immediately implement DB-OP-02 544, Security Events or Threats to make initial notifications to the Emergency Response Organization (ERO), the NRC, and the State and Counties.

NOTE 6.2 During a non-security event, the priority for performing notification is as follows, however, steps may be performed concurrently:

1. Notification of ERO - Section 6.2.
2. Notification of State and Counties - Section 6.3.
3. Individual Contact of ERO - Sections 6.4.
4. Notification of NRC - Section 6.5.

Initial notification of the State and Counties or a change in Protective Actions is required within 15 minutes of declaration of an emergency or change in classification.

6.2 Notification of the Emergencv Response Organization NOTE 6.2.1

1. The following ERO positions have access for activating CANS:

Central Alarm Station (CAS) Operator (Security)

Security Shift Supervisor (Security)

Shift Manager (Control Room)

Emergency Assistant Plant Manager (Control Room)

Unit Supervisor (Control Room)

Shift Engineer (Control Room)

Emergency Planning Advisor (Emergency Operations Facility)

Emergency Offsite Manager (Emergency Operations Facility)

EOF Communications Equipment Operator (Emergency Operations Facility)

2. Control Room staff should notify the ERO if Security personnel are not available during a Security event.

6.2.1 To initiate callout of the ERO:

a. The Emergency Director shall direct the Central Alarm Station (CAS) operator or other designee listed in Note 6.2.1 to initiate callout of the ERO and provide them with the Emergency Classification.

6 ~RA-EP-021 10 Revision 13

b. The individual activating CANS shall perform the following:

NOTE 6.2.1 .b. 1 The ERO numeric group page is used to notify the ERO of a change in emergency classification from an Alert, Site Area Emergency, or a General Emergency.

1. REFER TO the ERO Notification Flow Chart in the Immediate Notification Numbers section of the Emergency Plan Telephone Directory to initiate callout of the ERO.

NOTE 6.2.1.b.2 Within 10 minutes an ERO pager should activate with displays of the selected classification. ERO pagers are located in CAS and in the Control Room.

2. Verify an ERO pager activates with the proper display:
a. IF the ERO pagers fail to respond, THEN contact the On Call Duty Emergency Response individual.

(Refer to the Integrated On Call Report)

b. Upon contact inquire if their pager has received the proper Emergency Classification Code.0
c. IF it is determined that the primary CANS is not working, THEN ensure Section 6.3, Notification of the State and Counties is being performed (Control Room personnel only),

AND REFER TO the ERO Notification Flow Chart in the Immediate Notification Numbers section of the Emergency Plan Telephone Directory to initiate callout of the ERO using the CANS backup number.

1. Verify an ERO pager activates with the proper display:
a. IF the ERO pagers fail to respond, THEN contact the On Call Duty Emergency Response individual. (Refer to the Integrated On Call Report)
b. Upon contact inquire if their pager received the proper Emergency Classification Code.

0

7 ~RA-EP-021 10 Revision 13

c. IF it is determined the backup CANS is not working, REFER TO the ERO Notification Flow Chart in the Immediate Notification Numbers section of the Emergency Plan Telephone Directory to initiate callout of the ERO using ERO numeric group page.
1. Verify an ERO pager activates with the proper display:
a. IF the ERO pagers fail to respond, THEN contact the On Call Duty Emergency Response individual. (Refer to the Integrated On Call Report)
b. Upon contact inquire if their pager received the proper Emergency Classification Code.
c. IF the primary CANS, the backup CANS, and the ERG numeric group page fail to respond, THEN proceed to Step 6.4, Individual Contact of Emergency Responders.
d. Inform the Emergency Director when CANS has been properly activated or if any system problems were encountered.

NOTE 6.2.1.b.3 The CANS printout is faxed to the Control Room fax, the Central Alarm Station (CAS) fax, and the EOF fax.

The CANS printout is emailed to Emergency Offsite Managers, Emergency Planning Advisors, and the EOF Conmmunications Equipment Operators.

3. IF the primary or backup CANS was activated, THEN. review the CANS Fax to ensure the ERO positions are being filled.
a. IF the positions are not being filled, THEN contact the On Call Duty Emergency Response individual.

(Refer to the Integrated On Call Report)

8 ~RA-EP-021 10 Revision 13 6.3 Notification of the State and Counties NOTE 6.3.1 Initial notification of the State and Counties is required within 15 minutes of the declaration of an emergency or a change in classification or a change in Protective Actions.

6.3.1 if making an initial notification, THEN the Emergency Director or designee shall fill out an FENOC Nuclear Power Plant Initial Notification Form (DBEP-0 10).

NOTE 6.3.2 Periodic updates are required as conditions change or hourly, at a minimum, unless the offsite agencies agree to forgo them.

6.3.2 IF making a periodic update, THEN the Emergency Director or designee shall fill out a FENOC Follow-Up/Periodic Update Notification Form (DBEP-009).

6.3.3 The Emergency Director or designee shall fill out a Davis-Besse Emergency Notification Coversheet (DBEP-0 12).

6.3.4 Perform the following on the Davis-Besse Emergency Notification Coversheet (DBEP-0 12):

  • Check box for FENOC Nuclear Power Plant Initial Notification Form or FENOC Follow-Up/Periodic Update Notification Form.
  • Check box for Actual Emergency or Drill.
  • Ensure signatures are obtained for the "Form completed by" and "accuracy verified by" sections.
  • Obtain Emergency Director review and approval of the FENOC Nuclear Power Plant Initial Notification Form or FENOC Follow-Up/Periodic Update Notification Form to release the information.
  • Provide the information to the communicator.

6.3.5 Activate the Davis-Besse 4-Way Phone. (Detailed instructions are contained in the Emergency Plan Telephone Directory).

a. IF the 4-Way is not operable, THEN obtain telephone numbers for the offsite agencies in the Immediate Notification section of the Emergency Plan Telephone Directory. Contact should be established in the following order:
1. Ottawa County
2. Lucas County
3. State of Ohio

9 ~RA-EP-021 10 Revision 13 6.3.6 As agencies answer, identify yourself by name and facility (Control Room, EOF) and record the following on the Davis-Besse Emergency Notification Coversheet (DBEP-012):

a. The agency notified.
b. Time of initial contact.
c. Completion time of call.
d. If the 4-Way Phone was used when making the notification.

6.3.7 Transmit the information from the approved FENOC Nuclear Power Plant Initial Notification Form or FENOC Follow-Up/Periodic Update Notification Form.

6.3.8 Sign the Davis-Besse Emergency Notification Coversheet (DBEP-0 12) and check the location on the form.

6.3.9 IF any of the required three agencies did not answer the 4-Way Phone, THEN contact them using the Immediate Notification section of the Emergency Plan Telephone Directory.

a. If any of the three offsite agencies were contacted using a means other than the 4-way Phone, request that the agency call back to verify the notification, and record the name of the individual(s) on the Davis-Besse Emergency Notification Cover Sheet (DBEP-012).

6.3.10 Telefax all completed forms to the Emergency Operations Facility.

10 RA-EP-021 10 Revision 13 6.4 Individual Contact of Emergency Responders 6.4.1 IF CANS and the pager system fail, 0

THEN the Emergency Director or designee shall obtain the following:

a. Attachment 1, Emergency Position Checklist
b. The ERO On-Call Report
c. The Emergency Plan Telephone Directory 6.4.2 Contact the positions listed on Attachment 1, Emergency Position Checklist, using the On Call Report to determine who is on-call. The Emergency Plan Telephone Directory lists all phone numbers available for these individuals.

NOTE 6.4.3 It is important that calls be as short and concise as possible in order to expedite the notification process.

6.4.3 Upon making contact inform the individual of the following:

a. Your name and title.
b. Basis for your call (CANS and pagers failed to initiate emergency notifications).
c. The classification.

6.4.4 Record time of contact, fitness for duty status, and estimated time of arrival on Attachment 1, Emergency Position Checklist.

11 RA-EP-021 10 Revision 13 6.5 Notification of the NRC NOTE 6.5.1 During a security event, accelerated notification to the NRC is accomplished in accordance with DB-OP-02544, Security Events or Threats.

6.5.1 Initial notification to the NRC should be made by the Control Room staff, unless directed otherwise by the Emergency Director.

6.5.2 Make initial notification to the NRC immediately after notification of the local and state agencies, but no later than one hour after any emergency declaration.

6.5.3 For all NRC notifications, fill out the Reactor Plant Event Notification Worksheet (NOP-OP-l1015-01), in accordance with NOP-OP- 1015, Event Notifications.

6.5.4 Notification to the NRC Operations Center should normally be made using the NRC Emergency Notification System (ENS) (red) phone.

a. IF using a phone other than the NRC ENS phone, THEN NRC notification may be made by obtaining the phone numbers listed in the Emergency Plan Telephone Directory, Immediate Notification Tab.

6.5.5 Transmit the information on the form.

6.5.6 Telefax all forms to the Emergency Operations Facility.

7.0 FINAL COND)ITIONS 7.1 The required personnel have been notified in accordance with the appropriate Emergency Classification.

7.2 Any communication system malfunctions have been reported to the Emergency Response Manager.

12 RA-EP-021 10 Revision 13 NOTE 8.0 All logs, documents and forms generated during the implementation of this procedure are to be retained and processed in accordance with RA-EP-02720, Recovery Organization.

8.0 RECORDS 8,1 The following records that are completed by this procedure shall be processed and retained as part of the Event Package in accordance with RA-EP-02720, Recovery Organization:

8.1.1 Davis-Besse Emergency Notification Coversheet (DBEP-0 12) 8.1.2 FENOC Nuclear Power Plant Initial Notification Form (DBEP-0 10) 8.1.3 FENOC Follow-Up/Periodic Update Notification Form (DBEP-009) 8.1.4 Reactor Plant Event Notification Worksheet (NOP-OP- 1015-01) 8.1.5 Emergency Position Checklist

13 RA-EP-021 10 Revision 13 ATTACHMENT 1: EMERGENCY POSITION CHECKLIST Page 1 of 1 Complete this attachment only if individual contact of the emergency responders is required. Log the appropriate information. Request the individual initiate their call-tree card for those positions indicated with an asterisk (*):

Emergency Title IEmergency I Per~son Notified Time IAbstained from Estim.rated Facility Notified alcohol for 5 hours5.787037e-5 days <br />0.00139 hours <br />8.267196e-6 weeks <br />1.9025e-6 months <br /> Time of and are Fit-for-Duty? Arrival 1 Emergency Assistant Plant Mgr CTRM LI Yes LI No 2 Dose Assessment Coordinator

  • EOF LI Yes I] No 3 Emergency Offsite Manager EOF Lj Yes LI No 4 Emergency Planning Advisor EOF Li Yes LI No 5 OSC Manager

8 I&C On-call Responder OSC LI Yes LI No ____

9 Mechanical On-call Responder OSC [] Yes LI No ___

10 TSC Engineering Manager TSC D]Yes LI No ____

11 Core/Thermal Hydraulic Eng TSC [] Yes I] No _____

12 Emergency Director EOF/TSC Li Yes LI No ____

13 NRC Liaison

  • EOF LI Yes LI No 14 State / County Communicator
  • EOF ___________L Yes LI No ____

15 TSC Electrical Engineer TSC [] Yes LI No 16 TSC I&C Engineer TSC LI Yes LI No 17 TSC Mechanical Engineer TSC _____L Yes LI No 18 Emergency RP Manager

  • TSC LI Yes LI No 19 Emergency Plant Manager TSC L] Yes LI No 20 RMT Coordinator

21 RTL Coordinator EOF EI Yes LI No 22 RecoVery Advisor

  • TSC LI Yes LI No 23 Emergency Director Advisor
  • EOF _______________L Yes LI No ____

24 Company Spokesperson

  • JIC _________ ___L Yes LI No ____

Performed by:

Date:

14 RA-EP-021 10 Revision 13 COMMITMENTS Section Reference Comments Notes 6.3.1 O 13969 Capability to notify State and Local agencies within 15 minutes after declaring an emergency.

Section 6.3 O 13462 Initial notifications should address all items in NUREG-0654, Rev. 1, Standard E Criterion 3.

Section 6.3 O 13532 Notification of the State of Ohio as well as the Counties.

O 13566 O 15211 Section 6.3 0 13532 Message content 0 15211 Section 6.5 O 13532 NRC Notification.

0 15211 Section 6.3 O 13534 Initial and follow up message content O 14152 0 15211 Note 6.2.1 CA 04-03371-01 CANS activation during a security event Section 6.2 CA 04-02854-01 CANS activation is performed at the direction of the Shift Manager

Page 1 of 23 Davis-Besse Nuclear Power Station EMERGENCY PLAN IMPLEMENTING PROCEDURE RA-EP-02220 EMERGENCY OPERATIONS FACILITY ACTIVATION AND RESPONSE REVISION 13 Prepared by: P. J. Smith Procedure Owner: Emergency Response Manager Effective Date: 12/22/1 5 LEVEL OF USE:

IN-FIELD REFERENCE

2 RA-EP-02220 Revision 13 TABLE OF CONTENTS Page 1.0 PURPOSE...................................................................... 3

2.0 REFERENCES

................................................................ 3 3.0 DEFINITIONS ................................................................ 3 4.0 RESPONSIBILITIES ......................................................... 4 5.0 INITIATING CONDITIONS................................................. 5 6.0 PROCEDUJRE.................................................................. 6 6.1 Emergency Director Advisor......................................... 6 6.2 Emergency Planning Advisor ........................................ 6 6.3 State and County Communicator.................................... 10 6.4 NRC Liaison........................................................... 10 7.0 FINAL CONDITIONS........................................................ 13 8.0 RECORDS..................................................................... 13.

ATTACHMENT 1: SIREN SYSTEM ............................................... 14 ATTACHMENT 2: PREPARING FOR NRC INCIDENT RESPONSE TEAM 21 ATTACHMENT 3: CANS RESPONSE VERIFICATION......................... 22 COMMITMENTS ..................................................................... 23

3 RA-EP-02220 Revision 13 1.0 PURPOSE This procedure outlines the steps required for activation, operation, and deactivation of the Emergency Operations Facility (EOF) as performed by the Emergency Director Advisor, Emergency Planning Advisor, State and County Communicator and the NRC Liaison.

2.0 REFERENCES

2.1 Developmental 2.1.1 Davis-Besse Nuclear Power Station Emergency Plan 2.2 Implementation 2.2.1 RA-EP-0 1500, Emergency Classification 2.2.2 RA-EP-020 10, Emergency Management 2.2.3 RA-EP-02 110, Emergency Notification 2.2.4 RA-EP-02720, Recovery Organization 2.2.5 NOP-LP-5005, FENOC Siren Testing and Maintenance Procedure 2.2.6 DBNPS Emergency Plan Telephone Directory 2.2.7 RA-EP-02270, Facilities Support 2.2.8 RA-EP-023 10, Technical Support Center Activation and Response 2.2.9 NOP-LP- 1002, Fitness for Duty Program 2.2.10 DBBP-EMER-0050, Owner Controlled Area Public Address System (OCA PA) 2.2.11 NORM-LP-5 005, Emergency Operations Facility Reference Manual 3.0 DEFINITIONS 3.1 CENTRAL COMPUTER UNIT (CCU) - The personal computer that the Federal Signal Corporation's SFCDWARE Software resides on and provides for the interface to the Remote Terminal Units (RTU) at each siren. This terminal provides for activation, polling and monitoring of the siren system. The CCUs are at the following locations:

Ottawa County Sheriffs' Office, Davis-Besse Emergency Operations Facility, Davis-Besse Administration Building, and at the Oak Harbor 500-Foot Tower Site.

3.2 COMPUTERIZED AUTOMATED NOTIFICATION SYSTEM (CANS) - A computer developed and used to control notification of designated personnel in the event of an emergency.

4 RA-EP-02220 Revision 13 3.3 EMERGENCY OPERATIONS FACILITY (EOF) - An area located at the Lindsey Emergency Response Facility (LERF) which is equipped to facilitate the control and coordination of emergency activities and assessment.

3.4 LINDSEY EMERGENCY RESPONSE FACILITY - An area located at 1240 South Main Street, Lindsey, Ohio 43442, which is equipped to facilitate the control and coordination of emergency activities and assessments. The LERF houses the EOF, Alternate TSC, and provides a muster area for additional ERO personnel.

3.5 MASTER RESET - A command that resets the Remote Terminal Units (RTU) registers in each siren.

4.0 RESPONSIBILITIES 4.1 The Emergency Director Advisor is responsible for:

4.1.1 Assisting the Emergency Director in performing his emergency responsibilities.

4.1.2 Providing periodic approved information to the Company Spokesperson for release to the general public.

4.1.3 On failure of the Computerized Automated Notification System (CANS) call out emergency staffing as specified in the call tree section of the Emergency Plan Telephone Directory.

4.2 The Emergency Planning Advisor is responsible for:

4.2.1 Verifying proper operation of CANS and appropriate EOF staff notifications of

  • the emergency classification.

4.2.2 Verifyiing proper operation of the offsite sirens.

4.2.3 Providing Initial Notifications and Periodic Updates to offsite agencies.

4.2.4 Interacting with the liaisons that arrive at the EOF from the State of Ohio, and Ottawa and Lucas Counties.

4.3 The State and County Communicator is responsible for:

4.3.1 Maintaining communication with Ottawa County, Lucas County and the State of Ohio.

4.3.2 On failure of the Computerized Automated Notification System (CANS) call out emergency staffing as specified in the call tree section of the Emergency Plan Telephone Directory.

0

5 RA-EP-02220 Revision 13 4.4 The NRC Liaison is responsible for:

4.4.1 Interfacing with the NRC.

4.4.2 Interfacing with the NRC Incident Response Team when it arrives at Davis-Besse.

4.4.3 On failure of the Computerized Automated Notification System (CANS) call out emergency staffing as specified in the call tree section of the Emergency Plan Telephone Directory.

5.0 INITIATING CONDITIONS This procedure shall be used when:

5.1 An emergency has been declared and classified as an Alert, a Site Area Emergency, or a General Emergency.

5.2 Determined by the Emergency Director.

6 RA-EP-02220 Revision 13 6.0 PROCEDURE Steps in this procedure may be performed simultaneously.

6.1 Emergency Director Advisor 6.1.1 On failure of the Computerized Automated Notification System (CANS) call out emergency staffing as specified in the call tree section of the Emergency Plan Telephone Directory.

6.1.2 Assist the Emergency Director in turnover of responsibilities from the Control Room.

6.1.3 Follow events closely, be prepared to brief and assist the Emergency Director concerning procedural requirements relating to the emergency (see RA-EP-020 10, Emergency Management).

6.1.4 Act as a liaison between the Emergency Director and Company Spokesperson.

6.1.5 Review checklists and notifications for completeness, as appropriate.

6.1.6 Assess the need to upgrade or downgrade the emergency in accordance with RA-EP-0 1500, Emergency Classification.

6.2 Emergency Planning Advisor 6.2.1 Activation

a. Verify with the Emergency Offsite Manager that the minimum required EOF staffing as identified in RA-EP-020 10, Emergency Management, Attachment 3 has been met.
b. Ensure each EOF position required for minimum staffing and assigned to the EOF has telephone communications available. The 4-Way Phone is not activated until after the facility is activated and has responsibility for communications. Contact the FE Help Desk for assistance with any equipment issues.

6.2.2 Operation

a. WHEN the EOF is activated, AND the Emergency Director responsibilities have been transferred to the EOF, THEN perform the following:
1. Obtain concurrence fr~om the Emergency Offsite Manager to activate the 4-Way Phone.

7 RA-EP-02220 Revision 13

a. Advise the State and County Communicator to establish and maintain communications with Ottawa and Lucas Counties, and the State of Ohio. Refer to Step 6.3.2.
2. Assume responsibility for preparing required notifications to the State of Ohio, Ottawa County, and Lucas County. Ensure all FENOC Nuclear Power Plant Initial Notification Forms and FENOC Follow-up/Periodic Update Notification Forms are approved by the Emergency Offsite Manager and approved by the Emergency Director prior to transmittal to offsite agencies. Perform offsite notifications per RA-EP-02 110.
a. FENOC Nuclear Power Plant Initial Notification Forms are transmitted to State and County agencies WITHIN 15 MINUTES of:
  • Change in Emergency Classification
  • Change in Protective Action Recommendation
  • If plant condition degrade and a higher classification is declared before the notifications are made for the lesser declaration, the licensee should update the notification to reflect the higher emergency declaration and complete the updated notification within 15 minutes of the lesser emergency declaration.
  • If the notification cannot be updated and completed within 15 minutes of the lesser emergency declaration, the ERO should make the notification for the lesser emergency within 15 minutes of its declaration. The notification could contain the caveat that a change in classification was forthcoming. In parallel, the licensee should prepare the notification for the higher emergency classification and make an additional notification within 15 minutes of its declaration.
b. FENOC Follow-up/Periodic Update Notification Forms are provided to State and County agencies:
  • Immediately following the transmittal of an FENOC Nuclear Power Plant Initial Notification Form for a General Emergency
  • Immediately following the transmittal of an FENOC Nuclear Power Plant Initial Notification Form for a change in Protective Action Recommendations
  • Approximately hourly
  • As conditions change
3. Notify the Institute of Nuclear Power Operations (INPO) as soon as reasonably practical, but within a goal of 1 hour1.157407e-5 days <br />2.777778e-4 hours <br />1.653439e-6 weeks <br />3.805e-7 months <br /> of the emergency declaration using utilizing form DBEP-03 10, INPO Event Notification Form.

8 RA-EP-02220 Revision 13

4. Ensure that the GaiTronics volume is audible in the EOF.O
5. Ensure status boards are being maintained current.
6. Ensure emergency responders sign in on the Emergency Organization sign in board.
7. Contact the Technical Support Center or utilize the time on a cellular phone to determine the need to synchronize the EOF Digital Clock. If required, synchronize the time on the EOF digital clock with the digital clock in the Technical Support Center or with a cellular phone using the posted instructions.
8. Establish initial siren system status. Refer to ATTACHMENT 1, SIREN SYSTEM, A. INITIAL SYSTEM ASSESSMENT
9. If Emergency Response Organization (ERO) positions in the Emergency Response Facilities are not filled, then verify individuals have responded to the CANS. Refer to Attachment 3, CANS Response Verification.
10. Discuss with the Dose Assessment Coordinator the need to establish personnel monitoring at the Lindsey Emergency Response Facility.
b. IF there is a change in Classification or a change in Protective Action Recommendation (PARs)

THEN perform the following:

1. Transmit an approved FENOC Nuclear Power Plant Initial Notification Form to State and County agencies WITHIN 15 MINUTES.
2. Provide an approved FENOC Follow-up/Periodic Update Notification Form and, as appropriate, a release pathway drawing and a plume footprint to the State and County agencies immediately following the transmittal of an FENOC Nuclear Power Plant Initial Notification form for a General Emergency or a change in Protective Action Recommendation.
3. Provide a FENOC Follow-up/Periodic Update Notification Form to the State and County agencies approximately hourly or as conditions change.
4. Notify the ERO of the change in classification in accordance with RA-EP-021 10, Emergency Notification.
5. Notify the Institute of Nuclear Power Operations (INPO) of the change in classification utilizing form DBEP-03 10, INPO Event Notification Form.
6. When directed by the Emergency Offsite Manger, make an announcement over the Owner Controlled Area Public Address System. I

9 RA-EP-02220 Revision 13 Refer to DBBP-EMER-0050, Owner-Controlled Area (OCA) Public Address System for additional information.

a. IF the Owner Controlled Area Public Address System cannot be activated from the EOF, contact the Emergency Facilities Services Manager in the TSC or contact the Secondary Alarm Station (SAS) to make the announcement.
7. When directed, communicate meteorological condition changes to the State of Ohio, Ottawa County, and Lucas County.
8. When siren system status is requested by Ottawa or Lucas County and with the EOM's concurrence, refer to ATTACHMENT 1: SIREN SYSTEM, B. DETERMINING STATUS FOLLOWING SIREN SYSTEM ACTIVATION.
9. Ensure protective actions implemented by the Counties are posted on the Protective Actions Taken Status Board
a. Provide periodic briefings to and answer questions from the EMA Liaisons in the EOF.
b. Provide assistance to the Emergency Offsite Manager, as needed.
c. IF any personnel contaminations are detected at the Lindsey Emergency Response Facility, THEN request the TSC Emergency Radiation Protection Manager dispatch RP Technicians to respond to provide personnel monitoring and decontamination support.
d. If a high-level alarm is received on the Decontamination Tank at the Lindsey Emergency Response Facility, then perform the following:
1. If the Decontamination Room has never been used for personnel decontamination, then the contents of the tank may be pumped via normal methods.
2. if decontamination efforts are being performed, stop the activities adding water to the Decontamination Tank.
3. if personnel decontamination efforts are still necessary, consider relocating these activities to the Lindsey Service Center, in accordance with RA-EP-02550, Offsite Personnel And Vehicle Monitoring And Decontamination.
4. If the Decontamination Room has been used for personnel decontamination, then contact the Emergency Radiation Protection Manager in the TSC for guidance and protocol for pumping the contents of the Decontamination Tank.

10 RA-EP-02220 Revision 13 6.2.3 Deactivation

a. Upon deactivation of the EOF, inform the State of Ohio, Ottawa and Lucas Counties using an Initial Notification Form in accordance with RA-EP-02 110, Emergency Notification.
b. Notify the ERO of the "All Clear" in accordance with RA-EP-021 10, Emergency Notification.

6.3 State and County Communicator 6.3.1 Activation

a. On failure of the Computerized Automated Notification System (CANS) call out emergency staffing as specified in the call tree section of the DBNPS Emergency Plan Telephone Directory.

6.3.2 Operation

a. When notified by the Emergency Planning Advisor, establish and maintain communications with Ottawa and Lucas Counties, and the State of Ohio.
1. Activate the 4-Way Phone in accordance with the Emergency Plan Telephone Directory, section 2.1.11.

6.4 NRC Liaison 6.4.1 Activation

a. Respond to Computerized Automated Notification System (CANS) b.* On failure of the CANS call out emergency staffing as specified in the call tree section of the DBNPS Emergency Plan Telephone Directory.

NOTE 6.4.1.c Extensions of the Emergency Notification System (ENS) are located in the Control Room, Shift Engineer's Office, TSC, EOF and the NRC Conference Room (DBAB Room 110).

If the Control Room is communicating with the NRC you will be able to monitor the communications.

c. Verify that the primary and backup Emergency Notification System (ENS) telephones at the NRC Liaison Desk have dial tone by picking up the receiver. If no dial tone is present notify the Emergency Offsite Manager.

0

11 RA-EP-02220 Revision 13

d. Begin a personal log for the NRC Liaison position. Ensure key interactions with the NRC are documented in your log. All documents should have time, date and author/sources.
e. Verify that the Emergency Response Data System (ERDS) is transmitting data to the NRC by contacting the TSC Computer Technician, or by using RA-EP-023 10, TSC Activation and Response, Attachment 1. If the ERDS is not transmitting data to the N-RC, refer to Attachment 1 of RA-EP-023 10.

6.4.2 Operation

a. Determine the Emergency Action Level (EAL) that the event was classified under.
b. Verify initial notification to the NRC was made and obtain a copy of Reactor Plant Event Notification Worksheet(s), (Form NOP-OP- 1015-01) that have been transmitted to the NRC during this event. If the Control Room has not faxed a copy of the Event Notification Worksheet, request that the EOF Operations Advisor obtain a copy from the Control Room.
c. If the initial NRC notification has not been made notify the Emergency Offsite Manager.
d. Periodically (at least once every hour) complete a Reactor Plant Event Notification Worksheet (NOP-OP- 1015-01) and have it peer checked, then update the NRC via the ENS. Update the EOF Task Board following each periodic briefing. Ensure that items that require follow-up/feedback are posted on the EOF Task Board. Suggested issues for discussion:
1. Emergency Classification
2. Status/condition of the three fission product barriers
3. Status of reactor (operating/shutdown/cooldown/shutdown margin)
4. Status of station emergency response facility activation
5. Status of a radiological releases to the environment

[] Wind direction

[] Stability Class

[] Expected release duration of the (2 hours2.314815e-5 days <br />5.555556e-4 hours <br />3.306878e-6 weeks <br />7.61e-7 months <br /> default)

6. Source of the release
7. Station onsite protective actions
8. Station offsite protective action recommendations
9. Protective actions taken by offsite agencies
10. Requests for offsite medical, fire or law enforcement assistance
11. Issues that have received media attention

12 RA-EP-02220 Revision 13

e. Request information from the NRC on:
1. Potential or expected NRC response to the station
2. Potential or expected NRC response to the State of Ohio Emergency Operations Facility
3. Requests for additional information
f. Participate in periodic EOF briefings. Highlight key interactions with the NRC, questions and NRC dispatch of personnel to the stations.
g. When advised that the NRC is dispatching an Incident Response Team refer to ATTACHMENT 2: PREPARING FOR NRC INCIDENT RESPONSE TEAM (IIRT) and notify the following of the pending NRC Team arrival:
1. Emergency Director
2. Emergency Offsite Manager
3. Emergency Plant Manager
4. Emergency Security Manager
5. Company Spokesperson 6.4.3 Deactivation
a. Prepare a list of NRC issues and provide turnover to the Manager, 0 Regulatory Compliance or his designee.
b. Review RA-EP-02720, Recovery Organization procedure.
c. For significant events consider the following activities:
1. Sequester of failed equipment not necessary for safe shutdown for NRC inspection before repair.
2. Prepare a location and list of appropriate personnel for interview.
3. Prepare a list of names, titles and telephone numbers of key personnel in the recovery organization.

13 RA-EP-02220 Revision 13

. 7.0 FINAL CONDITIONS This procedure shall be terminated when:

7.1 Plant conditions are such that the emergency has been downgraded to Unusual Event, or terminated; and the EOF has been deactivated.

7.2 All equipment and useable supplies have been returned to their storage location.

7.3 The EOF staff has been relieved of all duties associated with the operation of the EOF.

7.4 The Company Spokesperson has been fully briefed on plant status and planned recovery actions.

NOTE: 8.0 All logs, documents and forms generated during the implementation of this procedure are to be retained and processed in accordance with RA-EP-02720, Recovery Organization.

8.0 RECORDS 8.1 The following records that are completed by this procedure shall be processed and retained as part of the Event Package in accordance with RA-EP-02720, Recovery Organization.

8.1.1 PNS Siren Computer Map Report Form (DBEP-05 1).

8.1.2 NRC Incident Response Team (IIRT) Form (DBEP-306) 8.1.3 CANS Validation Checklist (DBEP-3 05) 8.1.4 Reactor Plant Event Notification Worksheet (NOP-OP-1015-01) 8.1.5 INPO Event Notification Form (DBEP-03 10)

14 RA-EP-02220 Revision 13 ATTACHMENT 1: SIREN SYSTEM (Page 1 of 7)

A. INITIAL SYSTEM ASSESSMENT The Davis-Besse Prompt Notification System is comprised of 54 sirens. Sirens 1-5 are located in Jerusalem Township in eastern Lucas County; the remaining 49 sirens are in Ottawa County. Ottawa County has 32 non-EPZ sirens in addition to the 49 EPZ sirens. The EPZ sirens are those found in the red box on the siren map displayed on the Central Computer Unit (CCU).

Each morning at approximately 0500 the CCU automatically polls the sirens. The CCU will automatically poll the siren a second time if the siren does not respond to the initial polling. The siren will not respond to the poll if there is radio traffic on or near the siren frequency in the vicinity of the individual siren site.

For additional information refer to RA-EP-00420, Response to Prompt Notification System Malfunction.

NOTE: A. 1 When the siren monitoring program is accessed remotely through the use of the modem, the Map Display may turn grey or partial grey and may need to be minimized, if necessary.

1. Reset the siren monitoring program display by:
a. Verifying the Federal Signal SFCDWARE software is open and maximized.
b. Verifying the Map Display is open and sized so the Federal Signal SFCDWARE software toolbar is visible.

NOTE: A.2 When the siren monitoring program is on the "Map Display" screen, additional information about the colored dots can be obtained by opening the "Legend" Window. Detailed information about each siren can be obtained by positioning the pointer on the numbered siren dot and left clicking the mouse.

2. From the EOF Central Computer Unit (CCU), review the siren status by:
a. Obtaining a copy of the PNS Siren Computer Map Report Form (DBEP-05 1).

15 RA-EP-02220 Revision 13 ATTACHMENT 1: SIREN SYSTEM (Page 2 of 7)

b. From the siren computer if not already selected, select the Map screen from the upper tool bar.

NOTE: A.2.c The third line of the individual siren "Status Detail FCT" window labeled "Last Conun" will indicate the last date and time that the siren communicated with the CCU.

c. For any siren that indicates a communication failure (Purple) poll the siren again by selecting the individual siren from the map. When the individual siren "Status Detail FCT" window opens, select Poll to poll this siren. If the siren does not respond poll the individual siren a second time. After three attempts indicate that the siren has a communications failure.
d. Observe the color of the "Map Display" dots and record the numbers of those sirens (dots) that are not solid green or solid blue on the PNS Siren Computer Map Report Form (DBEP-05 1).
e. Advise the Emergency Offsite Manager (EOM) of any abnormal indications.
1. Ensure that the abnormal indication is entered into the facility log.
2. Advise the affected county of the siren(s) with abnormal indication to allow them to focus resources in the area if route alerting is required.

NOTE A.2.e.3 If corporate dispatches a siren vendor into the 10 mile EPZ then ensure that if conditions become hazardous that he/she is advised to evacuate the EPZ.

3. If the desire is to repair the siren requeste that the Policy Loop Communicator contact the corporate Emergency Preparedness representative and request support.
f. With concurrence of the EOM, reset the "Map Display" by selecting Reset Map on the upper tool bar.
1. Periodically check the "Map Display" and report any changes to the EOM.

16 RA-EP-02220 Revision 13 ATTACHMENT 1: SIREN SYSTEM (Page 3 of 7)

B. DETERMINING STATUS FOLLOWING SIREN SYSTEM ACTIVATION

1. When requested by Ottawa or Lucas County and with the EOM's concurrence, use the CCU to determine the preliminary results of the siren activation:
a. Obtain a copy of the PNS Siren Computer Map Report Form (DBEP-05 1).
b. Select Poll All from the upper tool bar. Left clicking on Poll All will initiate the polling sequence.
c. After the polling is complete (approximately 12 minutes), observe the color of the "Map Display" dots and record the numbers of those sirens (dots) that are not solid green on the PNS Siren Computer Map Report Form (DBEP-05 1).
d. For any siren that indicates a communication failure (Purple), poll the siren again by selecting the individual siren from the map. When the individual siren "Status Detail FCT" window opens select Poll to poll this siren. If the siren does not respond, poll the individual siren a second time.

After a total of three attempts indicate that the siren has a communications failure.

e. Advise the Emergency Offsite Manager (EOM) of any abnormal indications. Then communicate this information to the requesting offsite agency.
1. Ensure that the abnormal indication is entered into the facility log.
2. Advise the affected county of the siren(s) with abnormal indication to allow them to focus resources in the area if route alerting is required.

NOTE B. 1.e.3 If corporate dispatches a siren vendor into the 10 mile EPZ then ensure that if conditions become hazardous that he/she is advised to evacuate the EPZ.

3. If the desire is to repair the siren requeste that the Policy Loop Communicator contact the corporate Emergency Preparedness representative and request support.

17 RA-EP-02220 Revision 13 ATTACHMENT 1: SIREN SYSTEM (Page 4 of 7)

2. To verify the preliminary results of the siren activation:
a. Print out the RTU report as follows:
1. Select "Reports" from the upper toolbar of the Federal Signal Corporation SFCD WARE window. The Map Display may need to be temporarily minimized.
2. Select "Current RTU Status"
3. Select "Print Report"
4. Close "Current RTU Status Report" dialog box NOTE: B.2.b The report will print out data for all EPZ and non-EPZ sirens.
b. Review the report verifying that the EPZ sirens indicate:

3-Minute Sounding Last Function 3 MIN STEADY Current Pass Rotation Pass

c. Immediately notify the Emergency Offsite Manager or his designee of any siren that does not list the indications described in step B.2.b above.
d. Reset the RTUs as follows:
1. Select "Activate" from the Map Display toolbar.
2. When the prompt for password appears, enter "TEST". The password is case sensitive.
3. Select "Exit"
4. Select "SIREN MASTER RESET"
5. The computer will indicate that you are about to sound the sirens. Select "OK"

18 RA-EP-02220 Revision 13 ATTACHMENT 1: SIREN SYSTEM (Page 5 of 7)

6. Close the siren activation window.
7. The computer will send the "SIREN MASTER RESET"'

command three consecutive times.

NOTE: B.2.e A Master Reset followed by a poil should reset all online CPU maps to GREEN with the exception of any siren that is not communicating.

e. Wait approximately one minute and verify the master reset by polling the sirens:
1. Reset the map by selecting "Reset Map" from the Map Display toolbar.
2. Select Poll All from the upper tool bar. Left clicking on Poll All will initiate the polling sequence.
3. For any siren that indicates a communication failure (Purple),

poll the siren again by selecting the individual siren from the map. When the individual siren "Status Detail FCT" window opens, select Poll to poll this siren. If the siren does not respond, poll the individual siren a second time. After a total of three attempts indicate that the siren has a communications failure.

4. Advise the Emergency Offsite Manager (EOM) of any abnormal indications.
f. After the system has completed the poll, then print out the RTU report as follows:
1. Select "Reports" from the upper toolbar of the Federal Signal Corporation SFCD WARE window.
2. Select "Current RTU Status"
3. Select "Print Report"
4. Close "Current RTU Status" dialog box

19 RA-EP-02220 Revision 13 ATTACHMENT 1: SIREN SYSTEM (Page 6 of 7)

g. Review the report verifying that the EPZ sirens indicate:

SIRENS MASTER RESET Last Function Standby Current Reset Rotation Reset

h. Advise the Emergency Offsite Manager (EOM) of any abnormal indications.
3. Cancel Poll All
a. If the need occurs during the automatic polling sequence to cancel the "Poll All" perform the following:
1. Select "Activate" from the upper toolbar.
2. When prompted for a password press "Enter", no password is required.
3. Select "Cancel Poll" from the upper toolbar.
4. Close the "Activation" window.
4. With concurrence of the EOM reset the "Map Display" by selecting Reset Map on the upper tool bar. All siren dots should change to blue.
5. Periodically check the "Map Display" and report any changes to the EOM.

C. ACTIVATING THE SIREN SYSTEM

1. If directed by Ottawa County to sound the sirens, perform the following:
a. Obtain from Ottawa County what sirens should be activated.
b. Obtain the password from the Emergency Plan Telephone Directory, Section 2.1, Immediate Notification
c. Select Activate from the upper toolbar
d. When prompted, enter the Prompt Notification System Status Logger password (Passwordis case sensitive), and select Exit

20 RA-EP-02220 Revision 13 ATTACHMENT 1: SIREN SYSTEM (Page 7 of 7)

NOTE C. 1.e Ottawa County activates all 82 sirens in Ottawa County.

Davis-Besse activates the 54 EPZ sirens (49 Ottawa County and 5 Lucas County sirens).

e. Select the desired siren activation group, and select, OK.
f. Close window.

0

21 RA-EP-02220 Revision 13 ATTACHMENT 2:

PREPARING FOR NRC INCIDENT RESPONSE TEAM (IRT)

Page 1 of 1

1. Using the NRC Incident Response Team (LRT) Form (DBEP-3 06) obtain as much information as possible.
2. Obtain from the Emergency Offsite Manager recommended route/requirements to the Emergency Operations Facility at the Lindsey Emergency Response Facility and for entering the 10-mile emergency planning zone.
3. Obtain information on NRC IRT itinerary, including place (airport) and estimated time of arrival (ETA). Advise the NRC of any special routing considerations and provide directions to the Emergency Operations Facility at the Lindsey Emergency Response Facility. Request that the NRC IRT team report to the EOF for an initial briefing.
4. Notify the Emergency Offsite Manager that a NRC JIRT is being dispatched and request that the local law enforcement be advised.
5. Coordinate with the Emergency Security Manager to make arrangements for protected area and TSC access for the NRC IRT team members.
6. Ensure that arrangements are made for an initial briefing for the NRC IRT upon their arrival.
7. Obtain Emergency Offsite Manager permission to call in additional personnel, as necessary, for technical briefings and to serve as liaisons and as escorts for unbadged NRC personnel. (Note:

Personnel who are being called in shall comply with NOP-LP-1002, Fitness for Duty Program guidelines).

8. Request that the Emergency Security Manager ensures that individuals called-in will be granted access to the TSC. Confi-n that their site access requirements are current.

22 RA-EP-02220 Revision 13 ATTACHMENT 3:

CANS RESPONSE VERIFICATION Page 1 of 1 NOTE A.

The CANS Report is faxed / emailed 30 minutes after the system is activated and every 30 minutes for up to 2 hours2.314815e-5 days <br />5.555556e-4 hours <br />3.306878e-6 weeks <br />7.61e-7 months <br />.

A. Obtain the CANS Report from the BOF fax machine located by the PR Communicator.

NOTE A. 1 The CANS Report is emailed to the Emergency Offsite Managers, the Emergency Planning Advisors, and the BOF Communications Equipment Operators.

1. If the CANS Report was not received on the fax machine, then obtain the report by:
  • Logging into your windows network account using a company business network computer.
  • Open your email application.
  • Look for an email from "davisbesse" with a subject line similar to "ALERT Communicator NXT Completion Report."
  • If the CANS Report is not received in your email, then refer to Section 2.1 Immediate Notification Section in the Emergency Plan Telephone Directory to contact Cassidian Customer Support for assistance in obtaining the report.

B. Use the CANS Report to determine if all positions have responded. Compare the CANS Report to the CANS Validation Checklist, DBEP-305, if needed.

C. Notify the Emergency Offsite Manager of CANS status and status of the emergency response organization callout.

23 RA-EP-02220 Revision 13 COMMITMENTS Section Reference Comments None None None END