RNP-RA/03-0060, Transmittal of Emergency Procedure Revisions

From kanterella
Jump to navigation Jump to search
Transmittal of Emergency Procedure Revisions
ML031210298
Person / Time
Site: Robinson Duke Energy icon.png
Issue date: 04/29/2003
From: Baucom C
Progress Energy Co
To:
Document Control Desk, Office of Nuclear Reactor Regulation
References
RNP-RA/03-0060
Download: ML031210298 (17)


Text

ill -

II P 10 CFR 50, Appendix E Progress Energy Serial: RNP-RA/03-0060 APR 2 9 2003 United States Nuclear Regulatory Commission Attn: Document Control Desk Washington, DC 20555 H. B. ROBINSON STEAM ELECTRIC PLANT, UNIT NO. 2 DOCKET NO. 50-261/LICENSE NO. DPR-23 TRANSMITTAL OF EMERGENCY PROCEDURE REVISIONS Ladies and Gentlemen:

In accordance with 10 CFR 50.4(b)(5) and Appendix E to 10 CFR 50, Progress Energy Carolinas, Inc., also known as Carolina Power and Light Company, is transmitting revisions to H. B. Robinson Steam Electric Plant (HBRSEP), Unit No. 2, Emergency Implementing Procedures. The procedure revisions and effective dates are listed in the attachment to this letter.

A description of the procedure changes is provided on the "Summary of Changes" page for the emergency procedures. Please replace the superseded procedures with the enclosed revisions.

If you have any questions concerning this matter, please contact me.

Sincerely, C. T. Baucom Supervisor - Licensing/Regulatory Programs CAC/cac Attachment Enclosures c: L. A. Reyes, NRC, Region II (2 copies)

NRC Resident Inspector, HBRSEP C. P. Patel, NRC, NRR (w/o Attachment and Enclosures)

Progress Energy Carolinas, Inc.

3581 West Entrance Road

,#Jir(bf-Hartsville, SC 29550

United States Nuclear Regulatory Commission Attachment to Serial: RNP-RA/03-0060 Page 1 of 1 Procedure Revisions and Effective Dates I

Procedure Revision Effective No. Date EPCLA-03, "Generic Instructions" 3 04/08/03 EPNOT-04, "TSC NRC Emergency Communicator" 6 04/08/03

Pr.

arogress Enipy H. B. ROBINSON STEAM ELECTRIC PLANT, UNIT NO. 2 PLANT OPERATING MANUAL VOLUME 2 PART 5 EPCLA-03 GENERIC INSTRUCTIONS REVISION 3 I EPCLA-03 I Rev. 3 l Page 1 of 7 l

SUMMARY

OF CHANGES PRR 86956 STEP # REVISION COMMENTS Entire Procedure Converted to WORD 2000. Formatting changes as required to accommodate WORD.

8.3.3.2 Changed reference to AP-022 to PRO-NGGC-0204.

8.3.3.2.2 Changed procedure control to Plant Support Group.

8.3.4 Added generic statement to replace N/A that there are no records generated by this procedure.

I EPCLA-03 I Rev.3 Page2of7

TABLE OF CONTENTS SECTION PAGE 8.3.1 PURPOSE.............................................................................................................4 8.3.2 RESPONSIBILITIES ................................ 4 8.3.3 INSTRUCTIONS ................................ 4 8.3.3.1 Generic Guidance ................................ 4 8.3.3.2 EAL Development and Maintenance ................................ 5 8.3.4 RECORDS ................................ 7 8.3.5 ATTACHMENTS..................................................................................................7 I EPCLA-03 I Rev. 3 l Page 3 of 7

8.3.1 PURPOSE

1. This procedure provides generic guidance applicable to all sections of EPCLA-00.
2. This procedure provides the requirements for the conduct of the Emergency Action Levels (EALs) Procedure Program. The specific areas controlled by this procedure are EAL Development and Maintenance. (ACR-00429) (CR 99-00828) (CR 99-00766) 8.3.2 RESPONSIBILITIES
1. Supervisor-Emergency Preparedness The Supervisor-Emergency Preparedness is responsible for the implementation of the EAL Maintenance Program. This includes the recommendation of revisions to the EALs and approval of the transition document.
2. Manager-Regulatory Affairs The Manager-Regulatory Affairs is responsible for approval of all revisions to the EALs.

8.3.3 INSTRUCTIONS 8.3.3.1. Generic Guidance

1. Procedure steps which have been previously implemented as the result of earlier classifications need not be repeated unless warranted by changing conditions.

EXAMPLE: Sounding of the site evacuation alarm for both Site Area Emergency and General Emergency.

2. To the extent practical, emergency response activities should be accomplished in parallel to expedite notification of off-site agencies.

- Notifications should be made per EPNOT-00, Notification and Emergency Communications.

I EPCLA-03 I Rev. 3 l Page4of7

8.3.3.1 (Continued)

3. Portions of this procedure may be implemented from the Control Room, Technical Support Center or Emergency Operations Facility.
4. Dynamic situations which arise in an emergency condition may require that steps be performed out of sequence or alternate methods devised to accomplish the intent of the step.
a. Deviations which do not violate license requirements may be approved by the SEC or ERM.
b. Deviations which violate license requirements shall be implemented per 10 CFR 50.54 (x, y, and z). Time permitting SEC or ERM approval shall also be obtained.

8.3.3.2 EAL Development and Maintenance

1. EAL Development includes the creation of new procedures and the revision of existing procedures. The process involves the following documents that supplement the procedure revision process as defined in PRO-NGGC-0204, Procedure Review and Approval.

- EPCLA-02, Emergency Action Level Procedure User's Guide I EPCLA-03 I Rev. 3 l Page5of7

8.3.3.2 (Continued)

2. Upon successful development / corrections of the EALs, copies of the procedure will be mounted or laminated for distribution by the Plant Support Group or Emergency Preparedness. The number and type of EALs to be distributed can be found using NRCS (or its equivalent) or PLP-007. PLP-007 contains single page size reproductions of the EALs. Items to consider when revising the EALs is as follows: (CR 99-00766)

- The signed copy of the EALs when revised, is printed on Mylar (or equivalent) and sent to Document Control.

- The EALs are part of the Emergency Plan. When revising the EALs, PLP-007 should also be updated. This will require independent (TWO) safety reviews. The changes will be reviewed by the PNSC per PLP-007.

3. The EAL Transition Document contains the step by step comparison of the EAL to NUREG-0654. It may also include the basis for steps and any associated commitments. The EAL Transition Document contains the justification for the step differences between the EALs and NUREG when differences exist. Inaddition, the EAL Transition Document may contain any item that increases the understanding of why the EAL appears in it present form. Typical examples of such items include licensing commitments and Plant Management polices.

Consider the following material for inclusion into the Transition Document.

- Licensing commitments.

- Plant Management directives and policies.

- NRC and INPO recommendations.

- Audit commitments, recommendations and observations.

- Plant operating experience.

- Industry events.

EPCLA-03 I Rev. 3 l Page6of7

8.3.3.2 (Continued)

4. The Transition Document should be revised concurrently with the EALs to allow the document to be reviewed with the EAL procedure change package. If the Transition Document cannot be reviewed and approved concurrently with the EAL, it should be processed as soon as reasonably achievable to maintain the EAL supporting documentation current.

The EAL Transition Document shall be approved by the Supervisor-Emergency Preparedness.

5. The EAL Maintenance Program ensures the EALs remain current and controls the documentation that supports the plant specific EALs. The program is administered by the Emergency Preparedness (EP)

Staff as follows:

- Comments are provided to the EP Staff via EP Improvement Forms or similar document.

- Comments are reviewed by a member of the EP Staff for incorporation into the EALs or supporting documents.

- The reviewer determines if the comment warrants the initiation of a procedure revision or if the comment can be held in the applicable work control data base until it is incorporated in the next procedure revision.

- The EALs and supporting documents are revised in compliance with the requirements listed in Section 8.3.3.6 of this procedure.

8.3.4 RECORDS There are no records generated by this procedure.

8.3.5 ATTACHMENTS N/A l EPCLA-03 I Rev. 3 l Page 7 of 7

CProgress Energy H. B. ROBINSON STEAM ELECTRIC PLANT, UNIT NO. 2 PLANT OPERATING MANUAL VOLUME 2 PART 5 EPNOT-04 TSC NRC EMERGENCY COMMUNICATOR REVISION 6 I EPNOT-04 I Rev. 6 l Page 1 of 8 l

SUMMARY

OF CHANGES PRR 83007 Step # Revision Comments Entire Procedure Converted to WORD 2000 including necessary formatting changes.

8.4.4 Replaced N/A with the generic statement the procedure does not generate records.

IEPNOT-04 IRev. 6 I Page 2of 81

TABLE OF CONTENTS SECTION PAGE QUICK START GUIDE ................. 4 8.4.1 PURPOSE .5 8.4.2 RESPONSIBILITIES .5 8.4.3 INSTRUCTIONS .5 8.4.4 RECORDS .6 8.4.5 ATTACHMENTS . . . 6 8.4.5.1 Event Notification Worksheet .7 EPNOT-04 I Rev. 6 l Page 3 of 8

NRC EMERGENCY COMMUNICATOR QUICK START GUIDE NOTE: Blanks are provided for place keeping, only, heslogs are the official record.

This isa summary level guide and does not replace the procedure steps.

1. Sign in.
2. Check equipment status.
3. Log on to Electronic Display System (EDS).
4. Review previous emergency notifications and NRC notifications.
5. Notify Site Emergency Coordinator (SEC) and EOF Emergency Communicator when ready to assume duties.
6. Refer to procedure.

I EPNOT-04 I Rev.6 l Page4of8 l

8.4.1 PURPOSE

1. To provide instructions for notifications by the NRC Emergency Communicator to the Nuclear Regulatory Commission (NRC).

8.4.2 RESPONSIBILITIES

1. Accurately transmit information to the NRC.

8.4.3 INSTRUCTIONS

1. Determine the status of NRC notifications with the Control Room.
a. If initial contact is required, use Attachment 8.4.5.1, Event Notification Worksheet.
b. Information subsequent to initial notifications is typically responding to questions and providing verbal feedback, as such, no specific form is required.

- Records shall be maintained of responses which require approval by the SEC.

2. Notify the EOF Emergency Communicator and the SEC when you are ready to assume position duties.
3. Obtain SEC approval for information provided on the Event Notification Worksheet and responses to questions which do not contain information already approved for release.
a. Information posted on status boards and valid plant data from the Emergency Response Facility Information System (ERFIS) or Electronic Display System (EDS) are approved for release.
b. Any question which involves speculation about the future condition of the plant should be directed to appropriate personnel for an "official" response. This shall be approved by the SEC.

EPNOT-04 Rev. 6 Page5of8

8.4.3 (Continued)

4. Establish contact with the NRC.
a. Use an Emergency Telecommunication System (ETS) phone and dial the number listed on the sticker on the phone, or
b. Meridian phone and number listed in the ERO phone book.
5. Respond to NRC questions and requests with latest available information.
a. Keep the EOF Emergency Communicator informed of issues which emerge.
6. Man the phone continuously when requested by the NRC.
7. Verify transmission of Emergency Response Data System (ERDS) data after activation of the system.
a. ERDS must be activated within 1 hour1.157407e-5 days <br />2.777778e-4 hours <br />1.653439e-6 weeks <br />3.805e-7 months <br /> of the declaration of an Alert or higher.
8. Notify NRC personnel of drill or event termination as appropriate.

8.4.4 RECORDS There are no records generated by this procedure.

8.4.5 ATTACHMENTS 8.4.5.1 Event Notification Worksheet l EPNOT-04 I Rev. 6 l Page 6 of 8 l

ATTACHMENT 8.4.5.1 Page 1 of 2 PAGE 1 OF NRC FORM 361 U S. NUCLEAR REGULATORY COMMISSION (12-2000) OPERATIONS CENTER REACTOR PLANT EVENT NOTIFICATION WORKSHEET EN #

NRC OPERATION TELEPHONE NUMBER: PRIMARY -301-816-5100 or 800-532-3469', BACKUPS - [1st] 301-951-0550 or 800-449-3694,

[2nd] 301-415-0550 and [3rd] 301-415-0553 Licensees who maintain theirown ETS are provided these telephone numbers NOTIFICATION TIME FACILITY OR ORGANIZATION UNIT NAME OF CALLER CALL BACK #

H. B. ROBINSON 2 843-857-EVENT TIME&ZONE EVENT DATE POWERIMODE EFORE POWERMODE AFTER EVENT CLASSIFICATIONS 1-Hr. Non-Emergency 10 CFR50.72(b)(1) (v)(A) SafeS/DCapability AINA GENERAL EMERGENCY GEN/AAEC TS Devation ADEV (v)(B) RMR Capability AINB SITEAREAEMERGENCY SITIAAEC 4-Hr. Non-Emergency 10 CFR 50.72(b)(2) (vXC) Conrol of Rad Release AINC ALERT ALE/AAEC (i) TS Requred S/D ASHU (v)(D) Accident Miltgation AIND UNUSUAL EVENT UNUIAAEC (rv)(A) ECCS Discharge to RCS ACCS (xi) Offsie Medical AMED 50 72 NON-EMERGENCY (see next colurmns) = rv)(B) RPS Actuabon (scram) ARPS (xix) Loss Comnm/AsmitResp ACOM PHYSICALSECURITY(73 71) DDDD (x) OffsdieNotbicabon APRE 60-Day Optional 10 CFR 50.73(a)(1)

MATIER POSURE B??? 8-Hr. Non-Emergency 10CFR 50.72(b)(3) InvalidSpecifedSystem Actuabton AINV FITNESS FOR DUTY HFIT (dj(A) DegradedCondbon ADEG Other Unspecified Requirement (IdentIfy)

OTHER UNSPECIFIED REOMT. (see last colulmn) (-i)(B) Unanalyzed Condition AUNA NONR INFORMATION ONLY NINF _ rv)(A) Speafied System Actuation AESF =NONR DESCRIPTION fndude Systems affected, actuations andtiernrtiating signals. caGses, effect of event on planl actions taken or paraied, etc. (Continue on bac)

NOTIFICATIONS YES NO WILL BE ANYTHING UNUSUAL OR El YES (EXPLAIN ABOVE) E1NO NRC RESIDENT NOT UNDERSTOOD?

STATE(s) DID ALL SYSTEMS 1] YES E1 NO LOCAL FUNCTION AS REQUIRED?

OTHER GOV AGENCIES IOADDITIONAL INFO ON BACK MEDIAJPRESS RELEASE _ _UNTIL MODE OF OPERATION CORRECTED ESTITDATE RESTART DATE FOR IElmcYES n s~El NOr NRC FORM 361 (12-2000) rrP4 I tU UN KTUY~ rMt-l EPNOT-04 I Rev. 6 l Page7of8 l

ATTACHMENT 8.4.5.1 Page 2 of 2 ADDITIONAL INFORMATION PAGE 9OF 92 RADIOLOGICAL RELEASES: CHECK OR FILL IN APPLICABLE ITEMS specific detallslexplanations should be covered In event description)

LIQUID RELEASE GASEOUS RELEASE UNPLANNED RELEASE PLANNED RELEASE ONGOING TERMINATED MONITORED UNMONITORED OFFSITE RELEASE T. S EXCEEDED RM ALARMS AREAS EVACUATED PERSONNEL EXPOSED OR CONTAMINATED OFFSITE PROTECTIVE ACTIONS RECOMMENDED *State relase path in desaimpton Release Rate (ClIsec)  % T. S HOO GUIDE Total Activity (CI)  % T. S. LIMIT HOO GUIDE

__ _ _ __ _ __ _ _ __ ___ __ __ _ _ ~~L IM IT _ _ _ _ _ _ _ _ _ _ _ _ __ _ _ _ _ _ _ _ _ _ _ _ _

Noble Gas (i /lW I C1 Iodine l 0Ox__________ amCl Particulate I d /11 1 it Liquid (excluding tritium and a10.off111k 01 L dissolved noble gases) l Liquid (tritium) _ _ _ 2 0/ _ 51L Total Activity

_ PLANT STACK CONDENSERIAIR EJECTOR MAIN STEAM LINE SG BLOWDOWN OTHER RAD MONITOR READINGS l l l_ _

ALARM SETPOINTS l l lll

% T. S. LIMIT (if applicable)

RCS OR SG TUBE LEAKS: CHECK OR FILL IN APPLICABLE ITEMS: (specific detallslexplanations should be covered In event description)

LOCATION OF THE LEAK (e g, SG #, vawe, pipe, etc)

LEAK RATE I UNITS gpm/gpd T.S LIMITS SUDDEN OR LONG-TERM DEVELOPMENT LEAK START DATE TIME COOLANTACTMTY PRIMARY SECONDARY AND UNITS LIST OF SAFETY RELATED EQUIPMENT NOT OPERATIONAL:

EVENT DESCRIPMON (cortnrued from han)

NRC HEADQUARTERS DUTY OFFICER CONTACTED _ I

  • AMIPM NAME DATE TIME I EPNOT-04 I Rev. 6 l Page8of8 l