ML20079L381

From kanterella
Jump to navigation Jump to search
Forwards Emergency Response Data Sys Implementation Plan,Per 10CFR50,App E & Rev 1 to NUREG-1394.Implementation Expected to Be Completed by 930213
ML20079L381
Person / Time
Site: Harris, Brunswick, Robinson  Duke Energy icon.png
Issue date: 10/28/1991
From: Vaughn G
CAROLINA POWER & LIGHT CO.
To:
NRC OFFICE OF INFORMATION RESOURCES MANAGEMENT (IRM)
References
RTR-NUREG-1394 NLS-91-285, NUDOCS 9111060245
Download: ML20079L381 (13)


Text

~ _ _ ,

~, ,

CA&L a

Carolina Power & Lloht Company P O Box 1651 e Raleigh, N C 27602 GCT Z 81991 SERIAL: NLS 91-285 G E. VAUGHN Vice President Nuclear U$fvices Department United States Nuclear Regulatory Commissir ATTENTION: Document Control 'e #

Washington, DC 20555

11. B. ROBINSON STEAM ELECTRIC PLANT, UNIT NO. 2 DOCKET NO. 50-2G/ LICENSE NO. DPR-23 BRUNSWICK STEAM ELECTRIC PLANT, UNIT NOS. 1 AND 2 DOCKET NOS. 50 325 AND 50-324/ LICENSE NCS. DPR 71 AND DPR 62 SiiEARON HARRIS NUCLEAR POWER FIANT DOCKET NO. 50=400/ LICENSE NO. NPF-63 EMERGENCY RESPONdE DATA SYSTEM IMPLEMENTATION PROCRAM PLAN Gentlemen:

The purpose of this letter is to submit an Emerge my Rempanse Data Systs.in (ERDS)

Implementation Program Plan for Carolina Power h L ght Companu (CP&L) as ri. quired by Appendix E to 10CFR Part 30. An implementation pl.n is enclosed for the M. B.

Robinson Steam Ele c. cric Plant, the Brunswick Steam Electric Plant, and the Shearon Harris Nuclear Power Plant. It should be noted that the enclosed schedulen are targets only; however, as required by 10CFR50, implementation of ERDS will be complete by February 13, 1993 at each of CP&L's nuclear projects.

If you have eny questions about this subject, please contact me at (919) 546-4590 t.r Ms. Tillie 11udson at (919) 546-4055.

Yours very truly, ,

Wh r G. E. Vaughn ONH/jbw (1358CLU)

Enclosures cc: Mr. S. D. Ebneter Mr. L. Garner (NRC-HBR)

Mr. J. R. Jolicoeur Mr. N. B. Le Mr. R. Lo ]

Ms. B. L. Mozafari Mr. n L, Prevatte (NRC-BSEP)

Mr. J. E. fedraw (NRC-SHNPP) hp 9111060245 911020 FDR ADOCK 05000261 h~ {1 F PDR

-t .-  ;

l l l

H. B. ROBINSON STEAM ELECTRIC ILANT EMERGENCY RESPONSE DATA SYSTEM (ERDS)

IMPLEMENTATION PROGRAM PLAN l

l (1363ctu)

. -- .- _ _ __ . - - - _ . _ . _ _.. m

.: i

' I'. Computer System Configuration / Interface The H, B. Robinson Steam Electric Plant, Unit No. 2 (HBR2) ERDS will be implemented in accordance with the requirements of the final rule published in the Federal Register on August 13, 1991 (FR40178) and consistent with the guidelines identified in NUREG 1394, Revision * .

HBR2 is a single-feeder site.

The ERDS communication hardware will consist of two synchronous communication channels on the HER2 Emergency Response Facility Information System / Safety Parat.eter Display System (ERFIS/SPDS) computer system: one on the primary and one on the hack-up computer which will feed through an A/B switch (automatically switched on system failover),

The HBR2 ERDS will include the following characteristics:

1. Data for the' parameters for pressurized water reactors listed in Appendix E to 10CFR50, to the extent that the points currently exist on ERFIS, will be transmitted via ERDS,
2. ERDS will transmit data for all parameters at time intervals of not less than 15 seconds or more than 60 seconds, as specified in Appendix E to 10CFR50,
3. Link control ar.d data transmission format will be compatible with the guidance provided in NUREG 1394, Revision 1, The ERDS communication subsystem will be manually activated and will operate unattended. Once activated, the communication subsystem will establish a communications link, retrieve and format data for transmission, provide. status information to the operator, and control communication with the NRC ERDS computer at the : Operations Center

-consistent with the guidelines identified in NUREG 1394, Revision 1.

Once activated, the ERDS communication subsystem will require no personnel action for the acquisition or transmission of data, l,

( II. Procedures The initial design and implementation of the ERDS software will be controlled by existing site Software Configuration Management L -Procedures. .tior to final system _ operability, plant procedures will be-revised, or new procedures will be developed, to support ERDS in the areas of operation, design / modifications, and maintenance.

-The operation and activation of the ERDS Iink will be incorporated in l: the plant emergency procedures and will include directions to activate the ERDS as soon as possible but no later than one hour alter declaring an emergency classification of alert or higher, 1 (1363cw)

'r l Configuration management and maintenance will be controlled by site procedures already in place to control changes to the ERFIS/SPDS software and database. Applicable procedures will be revised to accommodate the ERDS subsystem as follows: (1) include a review for any software changes that would affect the ERDS transmission' data format or communication protocol (but not data point modifications) as identified in the -plant attribute library (PAL) transmission, and notification of the NRC at least 30 days prior to tho' change, and'(2) include notification of the NRC within 30 days after completion of any hardware or database change that would affect the transmitted data ints identified in the ERDS data point library (DPi.). This is o accordance with Appendix E to 10CFR50. In addition, a procedure will be developed -

for the periodic ERDS availability and operability test. The frequency of ERDS testing is planned to be quarterly, unless otherwise set by the NRC-based on demonstrated system performance._

III, ' Implementation Schedule The ERDS implementation schedule for HBR2 is attached, It should be noted that the schedule provides targets only; however,;the ERDS will be

-implemented at ilBR2 by February 13, 1993, as required by regulation.

I l

l l

2 O r ctu)

=

H. B. ROBINSON STEAM ELECTRIC PLANT

~

ERDS IMPLEMENTATION SCHEDULE 1991 1992 1993 ACTIVITY RESPONS!BILfiY JUL AUG S~P OCT NOV DEC JAN FEB ' MAR ' WR MAY , JUN JUL AUG SEP OCT NOV DEC JAN.FEB UTILITY RECEfVES OUESTIONNAJRE NRC

  • UTIUTY CONTACTED NRC & NRC IKE '

CONTRACTOR CONDUCT SITE SURVEYNISTT NRC & NRC 4 CONTRACTOR INSTALL PHONE UNES AT SITE # NRC & CP&L '

DEVELOP AND RETURN DPUPAL CP&L El DEVELOPS SOFTWARE FOR DPL NRC NRC to deterrrane schedule CONTRACTOR UTILITY DEVELOPS eM ARE CP&L PREUMWARY TRANSMISSION TESTING CP&L & N9C M CONTRACTOR F ST WITH UTIUTY AT El CP&L & NRC E (FORMAL SYSTEM TEST) CONTRACTOR SAT WITH UTluTY AT NRC CP&L & NRC E (FORMALTEST WITH NRC OPS CENTER)

DEVELOP NEW AND MODIFY CP&L m EXISTING PROCEDURES SYSTEM INTEGRATlON CP&L Mm UTILfTY ON-UNED CP&L M NOTES: @ Schedule is based on that permded in Genenc Letter 91-14; CP&L k midih enorts wG be based on the NRC schedule. The schedt% agreed upon for GL 91-14 takes pre dence cwer the schedule provided here.

O ERDS wm be fully implornented and orWine some time aflor comp 6 ebon of the formalInst with tw NRC Optaanons Center, t:ut no later than February 13,1993.

l .

I r-3 [--

BRUNSWICK S'fEAM ELECTRIC PLANT EMERGENCY RESPONSE DATA SYSTEM (ERDS)

IMPLEMENTATION PROGRAM PLAN

-U [__

(1363GLU)

r- ..

' f. Computer System Configuration / Interface The Brunswick Steam Electric Plant (BSEP) ERDS will be implemented in

.accordance with the requirements of the final rule published in the Federal Register on August 13, 1991 (FR40170) and consistent with the guidelines identified in NUREG 1394, Revision 1. A separate ERDS shall be-installed for each of the two units at BSEP, Each unit is a single-feeder site.

The ERDS will be a direct near real-time electronic data link between the BSEP Emergency Response Facility Information System (ERFIS) and the NRC's computer system at the NRC Operations Center.

The BSEP ERDS will include the follouirg hardware and software characteristics:

1. Data-for the paraneters for boiling water reactors listed in Appendix-E to 10CFR50, to the extent that the points currently exist on ERFIS, will be transmitted via ERDS.
2. ERDS will transmit data for all parameters at time intervals of not less than 15 seconds or more than 60 seconds, as specified in Appendix E to 10CFR50.
3. Link control and data transmission format will.be compatible with the guidance provided in NUREG 1394, Revision 1.

The ERDS -will be manually activated and will operate unattended. Once activated, the-system will establish a communications link, retrieve and format data for transmission, provide status information to the operator, and control communication with the NRC ERDS computer at the NRC Operations: Center consistent with the guidelines identified in NUREG 1394, Revision 1. Once activated, the.ERDS will require no personnel action for the acquisition or transmission of. data.

II. Procedures The design, installation-, and acceptance testing of ERDS is planned to be performed under CP&L's design control process, the Nuclear Plant Modification Program, or a similar process. Prior to final system operability, plant procedures will be revised, or new procedures will be developed, to support ERDS in the areas of operation, design /

[ modifications, and maintenance.

Operation of the ERDS will be controlled by plant emergency procedures, or other appropriate plant procedures. The. procedure will include

-directions to activate the ERDS as soon as possible, but not later than one hour after declaring an emergency classification of alert or higher.

l l-1 (1363GLU)

. . - -~ _

l Hardware and software changes to ERDS will be controlled by a process

-siullar to-that for ERFIS. The design-control mechanism will includn.

(1) notification to the NRC at least 30 days prior to any hardware or Loftware change (with the exception of data point modifications) that could affect the ERDS transmission format or computer communication protocol in the plant attribute library, and (2) notification to the NRC within 30 days after completion of any hardware or software change-that could affect the transmitted data points identified in the ERDS data point library. This is in accordance with Appendix E to 10CFR50.

Maintenance of the ERDS will be administratively controlled similarly to ERFIS, Maintenance of ERFIS is controlled under approved plant procedures for complicated or sensitive activities, and computer maintenance guidelines for relatively simple activities. A procedure will be developed for the periodic ERDS availability and operability test,. The frequency of ERDS testing is planned to be quarterly, unless otherwise set by the NRC based on demonstrated system performance, III, Implementation Schedule The ERDS implementation schedule for BSEP is attached, It should be noted that the schedule provides targets only; however,_the ERDS will be implemented at BSEP_by February 13, 1993, as required by regulation.

Y W u 2 (1363ctu)

BRUNSWICK STEAM ELECTRIC PLANT ERDS IMPL.EMENTATION SCHEDULE 1991 1992 l1993 ACTIVffY RESPONSOUTY JUL AUG SEP OCT NOV DEC JAN FEB MAR APR MAY JUN R AUG SEP OCT NOV OEC .!AN FEB UTUTY RECEfvES QUESTIONNAJRE -NRC 8 UTUTY CONTACTED NRC & NRC m CONTRACTOR CONDUCT E E SURVEY / VISIT NRC & NRC

  • CONTRACTOR INSTALL PHONE UNES AT SfTE@ NRC & CP&L MLM DEVELOP AND RETURN DPUPAL CD&L El DEVELOPS SOFTWARE FOR DPL NHC NRC10 determne schedule CONTRACTOR UTUTY DEVELOPS SOFTWARE CP&L m PREUMtNARY TRANSMISSON TESiING CP&L & NRC M CONTRACTOR FST WITH UTUTY AT El CP&L & NRC E (FORMAL SYSTEM TEST) CONTRACTOR SAT VATH UTIUTY AT NRC CPAL & NRC E (FORMALTEST Y,TTH NRC OPS CENTER)

DEVELOP NEW AND MOOlFY CP&L

':X1 STING PROCEDORES SYSTEM INTEGPATION CP&L m UTUTY ON-UNED CP&L 6 i

i40TES: @ Schedule is based on that provided in Genene Letter 91-14; CP&L instaRabon efbrts ud be based m tw NRC achedule. % sdedune agread upon Scr j GL 91-14 takes precedena over the schedule proMed h<ve.

1 ERDS wis be fuey impernented and ordine sorne time after mmple00n of the formai test wrth the NRC Operadons Center, t A no later than February 1*,,1993.

__3 SHEARON HARRIS NUCLEAR POWER PLANT EMERGENCY RESPONSE DATA SYSTEM (ERDS)

IMPLF. MENTATION PROGRAM PLAN u

I L

, (1363GLU)

l I'. Computer System Configurat'on/ Interface The Shearon llarris Nuclear Power Plant (SilNPP) ERDS will be implemented in accordance with the requirements of the final rule published in the rederal Register on August 13, 1991 (FR40178) and consistent with the guidelines identified in NUREG 1394, Revision 1. SilNPP is a single-feeder site.

The new communication display and communication linking capabilities required by FRDS at SilNPP will be incorporated into the current Emergency Response Facility Information System (ERFIS) computer.

The SilNPP ERDS will include the following hardware and software characteristics:

1. Data for the parameters for pressurized water reactors listed in Appendix E to 10CFR50, to the extent that the points currently exist on ERFIS, will be transmitted via ERDS.
2. ERDS will transmit data for all parameters at time intervals of not less than 15 seconds or more than. 60 seconds, as specified in Appendix E to 10CFR50.
3. Link control and data transmission format will be compatible with the guidance provided in NUREC 1394, Revision 1.

The ERDS will be manually activated and will operate unattended. The FRDS funct.'ons will be capable of being a:tivated from any current ERFIS man machine interface terminal. Once activated, the system will establish a communications link, retrieve and format data for transmission, provide status information to the operator, and control communication with the NRC ERDS computer at the NRC Operations Center consistent with the guidelines identified in NUREG 1394, Revision 1, Once activated, the ERDS will require no personnel action for the acquisition or transmission of data.

II. Procedures The initial design and implementation of the ERDS will he controlled under existing plant database and modification procedures. Prior to final system operability, plant procedures will be revised, or new procedures will be developed, to support ERDS in the areas of operation, desi hn/ modifications, and maintenance.

Initiation and operation of ERDS will be incorporated in the plant emergency procedures and will include directions to activate the ERDS as soon as possible, but no later than one hour after declaring an emergency classification of alert or higher.

1 0363ctu)

'4- .

~

Design configuration control and changes to this design vill be administered in accordance with existing plant database and modification

_ procedures. Applicable procedures will be revised to accommodate ERDS as follows: (1) include a review for any software changes that would

- affect the ERDS transmission data format or communication protocol (but not data point modifications) as identified in the plant attribute library (PAL) transmission, and notifjcation of the NRC at least 30 days prior to the chango, and (2) include notification of the NRC within 30 days after completion of any hardware or database change that would affect the transmitted data points identified in the EkDS d ta point library (DPL). This is in accordance with Appendix E to 10CFR50.

Maintenance of the ERDS will be administrative 1y controlled similarly to-ERFIS. -In addition, a procedure will be developed for the periodic ERDS-availability and operability _ test. The frequency of ERDS testing is-planned to be quarterly, unless otherwise set by the NRC based on demonstrated system performance.

III. Implementation Schedule The ERDS implementation schedule for SHNPP is attached. It should be

.noted-that the schedule provides targets only; however, the ERDS will be implemented at SHNPP by February 13, 1993, as required by regulation.

l 2 (1343ctu)

l SHEARON HARRIS NUCLEAR POWER PLANT .

ERDS IMPLEMENTATION SCHEDULE 1992 1903 1991 RESPONSOUTY JUL AUG SEP OCT NOV DEC JAN FEB MAR . APR MAY JUN JUL AUG SEP OCT NCN DEC JAN F*tEs ACTIVITY )

NRC

  • UTIUTY RECENES CUESTIONNA!Il l

UTUTY CONTACTED NRC & NRC men CONTRACTOR NRC & NRC 8 CONDUCT SrTE SURVEYNISIT CONTRACTOR b NRC & CP&L INSTALL PHONE UNES AT SITE DEVELOP AND RETURN DPUPAL 7&L NRC NRC10 determne schedule El DEVELOPS SOFTWARE FOR DPL CONTRACTOR l UT1UTY DEVELOPE "M ARE CP&L MM'8 Sf!E INTEGRATION AND TESTING CP&L ElllE PREUM:NA;TY TRANSMISSION TESTING CP&L & NRC COMTRACTOR I'E FST WITH UTUTY AT El CP&L & NRC (FORMAL SYSTEM TEST) CONTRACTOR E5 SAT WITH UTILITY AT NRC CP&L & NRC (FORMALTEST WITH NRC OPS CENTER)

DEVELOP NEW AND MOOiFY CP&L ----

EXGTING PROCEDURES EME0MMWWl8 SYSTEM INTEGRATON CP&L IBMM$5hiaWERB UTUTY ON-UNE I CP&L NOTES: O Sdedule is based on that prended ira Genmc Letter 91-14; CP&Linsbitanon efforts vnll be based on the NRC schedute. The somdsde agreed upon tor GL 91-14 takes precedence over the schedule prcmded here.

  • EROS d be hay ;i, Aii.44 and cMne some time anor cornple+on of the formal test mh the NRC Oper1tions Cents, but no tasnr than February 13,19M

,