ML20085L566

Forwards Emergency Response Data Sys Corporate Implementation Plan,Per 10CFR50,App E & Generic Ltr 91-14

ML20085L566
Person / Time
Site:	Oconee, Mcguire, Catawba, McGuire
Issue date:	10/24/1991
From:	Tuckman M DUKE POWER CO.
To:	NRC OFFICE OF INFORMATION RESOURCES MANAGEMENT (IRM)
References
GL-91-14, NUDOCS 9111040246
Download: ML20085L566 (5)

Text

. _ _ .

. Il I

, j< ,, o ,, e , r.., m i . , j '- ,,

\- l 1, , .

e /Si /

\.. i

\i /

{t ^

DUKE POWER October 24, 1991 U. S. Nuclear Regulatory Commission ___

Attention: Document Control Desk Washington, D. C. 20555

Subject:

McGuire Nuclear Station Docket Numbers 50-369 and -370 .

Catawba Nuclear Station Docket Numbers 50-413 and -414 Oconee Nuclear Station Docket Numbers 50-269, -270, and -287 Generic Letter 91-14; Emergency Response Data System; Implementation Plan The NRC has recently revised 10 CFR50, Appendix E, to require that licensees implement an Emergency Response Data System (ERDS) by February 13, 1993. Further, the rule requires that licensees submit, by October 28, 1991, a plan for the implementation of the ERDS. Attached is Duke Power Company's ERDS Implementation Plan.

If there are any questions on the administration of Duke's ERDS, please call W. Brad McCree at (704) 373-5149. Questions of 71 technical nature should be directed to Larry B. Bumgarner at (704) 373-5237 Very trul,y yours, M 3 aens._

M. S. Tuckman nregll4/ sag un )h),h n

,1 g g o 40M6 r

6c' u\

. . . - . _ . . .. _ _ _ . _.._.. ..___.___._.________...m____.__

l l

. l l

• a

- Nuclear Regulatory Commission-October e'4, 1991 Page 2 cca Mr. T. A. Reed, Project Manager Office of Nuclear Reactor Regulation U. S.. Nuclear Regulatory Commission Mail Stop 9113, OWFN Washington, D. C. 20555 Mr. R. E. Martin, Project Manager Office of Nuclear Reactor Regulation U. S. Nuclear Regulatory Commission l Mail Stop 9H3,-OWFN l l= Washington, D. C. 20555 l Mr. L. A. Wi er.s , Project Manager Office of Nuclear Reactor Regulation

U. S. Nuclear Regulatory Commission

Mail Stop 9113, OWFN l L

Mr. S. D. Ebneter, Regional Administrator U.S. Nuc]edr Regulatory Commission - Region II i 101 Marietta Street, NW - Suite 2900 l

. Atlanta, Georgia 30323 l

l 1

l l

l~

,v- + -

z , e

Emergency Response Data System Corporate Implementation Plan Duke Power Company O t erview Duke Power has installed an Operator Aid Computer (OAC) link to the corporate Wide Area Network (WAN) at Oconee. The mam component of this link is a software product DMACSW by Intellution,Inc. The link allows computer points to be transferred to a DMACS" database that can be accessed by anyone on the WAN using DMACSW A dedicated PC will be provided for each unit that will extract data from the DMACS data-base, format the data to meet the NRC requirements, and conununicate with the NRC using the protocol described in NUREG-1394, Rev.'l Appendix B.

liquivalent links have been purchased for McGuire and Catawba. They are currently being pro-totyped by the vendor and installation of the first link at McGuire Unit 2 is expected in May 1992. The last link should be installed at Catawba in the Fall of 1992. Using a common link to provide the data to the ERDS software, one program can be developed for use by all seven units.

This should reduce overall development time and maintenance costs, and possibly provide one system backing up the other system (s) on site.

i ImolementatimLfetaib ,

The following eleven steps have been taken from NUREG-1394, Rev. I appendix A.

1) The NRC notifies the contractor,Italliburton NUS Environmental Corporation, that a utility has received a site survey questionnaire.

As a participant in the voluntary program Duke Power has already received the site survey.

2) After the utility has received the questionnaire, they will be contacted by llalliburton NUS,

3) A site visit will be arranged.

A visit was held in Atlanta on October 1,1991, to discuss the Data Point Library, Plant At-tribute 1.ibrary and to answer licensee questions.

4) The NRC will install phone lines at the site.

This will be donc r,s part of Generic Letter 91 14. Due to recent organizational changes, spe-cific telephone system contacts cannot be named at this time. All tetivity should be coordi-l nated through the site ERDS contacts,(Al Sweney - Oconee, Randy llanner McGtdre,

1 Rainer Blessing - Cacawba) or through the corpolate contacts (litad McRee - Administrative, Larry Humgarner - Technical). Please copy Mr. McRee on all correspondence.

• 5) The utility then answers and returns the site survey questionnaire cor ining the DPL and pal.information to the NRC.

All the points that exist on plant computers have been identified for all seven units. Prelimi-nary infonnation h:u been gathered on instrument and process range ', engineering units, and description. Suppon has been tequested from site engineering staffs to provide the re-maining information. l

• M lithe plant's computer system requires customized ERDS n ception software, specif-ic ERDS ccxle will be developed and implemented by llallibunon NUS.

Duke does not anticipate this being necessary at this time.

7) in parallel with llallibunon NUS software development, the utility will design and write their data transmission software. The NRC ERDS implementation is develop-ing a PC based ERDS interface which will perfonn all ERDS communication proto- i cc' function, for single feeder or multiple-feeder plants. )

All software will be developed for a standard PC (IBM model 70 or equivalent). The exact operating system itas not been chosen, but no problems are anticipated. Duke requests h w view the muhiple feeder code written by liallibunon NUS for UNIX before committing to i specifics.  !

8) Preliminary software testing is the next step and is the first attempt at inmsfernng l data between the plant and GRDS computers. The preliminary software test perfonns '

initial data transmission testing of the utilities software and any custom code llalli-hunon NUS has developed. This is in actuality the software debugging pt riod and problems are to be expected. .

l Duke plans to write one generic program that can be used for all seven units. This may m-  ;

crease the debugging time on the first unit at Oconee, but should decrease the time irquired to implement the program at McGuire and Catawba.

9) Following the preliminary software tests and the initial dats transference between the plant and the ERDS computeis, a fonnal test will be conducted at llalliburton NLIS prior to adding the licensee to the ERDS.

A fomul test will be conducted as each unit's ERDS comes on line. His testing will be both site and unit specific. Duke desires consistency of ERDS software. If problems are found in testing any unit, all software will be updated according te Duke's configuration plan, and a formalietest will be performed with the llallibunon NUS facilities.

10) A fonnal test is then conducted on the ERDS computer at the Opene. ion Center.

This is the final test to demonstrate system functionality. Again data transmission

, vill be from the designated plant system.

This will be completed after the first preliminary test. D may also be required after signitb cant software changes. That significance will be detennined during the preliminary testing w

I l

.i i

I I

with llalliburton NUS. The required quarterly testing may be used for minor softwarr changes.

• The final step in the schedule has the utility on-line with all development and testing 11) completed.

This step will be obtained when all seven units are running their final software version and have completed all testing, heliminary Schedulei identify list of points for all units - Complete Submit implementation plan -- October 28,1991 Complete Oconee DPL and PAL-- April 1992 Complete McGuire DPL and PAL -- July,1992 Complete Catawba DPL and PAL -- October,1992 Complete initial software -- January,1992 Begin debugging software using Oconee data -- March,1992 Install PC hardware at Oconee - January,1992 Formal testing with llalliburton NUS for Oconee -- May 1992 Install PC hardware at McGuire -- June,1992 Fonnal testing with llalliburton NUS for McGuire -- August,1992 Install PC hardware at Catawba -- September,1992 Formal testing with italliburton NUS for Catawba -- November,1992 Fonnal Testing with NRC for Oconee --June,1992 Formal Testing with NRC for McGuire -- September,1992 i Fomial Testing with NRC for Catawba -- December,1992 Retests required by software changes,if necessary - January,1993 All seven units on-line - February,1993 i Dates are tentative and based on the current McGuire and Catawba DM ACS implementation xhedule.

I l

DMACS is a trademark of Inteilution, Inc., Norwux1, MA 02062 l

. --