0CAN099103, Revises ERDS Implementation Schedule Contained in .Software Development Expected to Be Completed by 920430, W/Hardware Installation Completed by 920515.Util Anticipates That ERDS Sys Will Be Operational by 920630

Revises ERDS Implementation Schedule Contained in .Software Development Expected to Be Completed by 920430, W/Hardware Installation Completed by 920515.Util Anticipates That ERDS Sys Will Be Operational by 920630

ML20079G464
Person / Time
Site:	Arkansas Nuclear
Issue date:	09/30/1991
From:	James Fisicaro ENTERGY OPERATIONS, INC.
To:	NRC OFFICE OF INFORMATION RESOURCES MANAGEMENT (IRM)
References
0CAN099103, CAN99103, NUDOCS 9110090124
Download: ML20079G464 (3)

Text

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

.-9 Enterg c"i ev, on asia" . iac.

Operations >

Sept ember 30, 1991 OCAN099103 U. S. Nuclear Regulatory Commission Document Control Desk Hall Station P1-137 Washington, DC 20',55

Subject:

Arkansas Nuclear One - Units 162 Document Nos. 50-313 6 50-368 License Nos. DPR-51 6 NPF-6 Revised ERDS Implementation Schedule Gentlemen:

Dy letter dated March 2, 1990 (OCAN039006), Entergy Operations volunteered to participate in the Emergency Response Data System (ERDS) implementation program at Arkansas Nuclear One (ANO). An implementatton schedule for ANO was provided to the Staff in letter dated March 28, 1991 (0CAN039107). As discussed in this letter, the previously proposed ERDS implementation schedule was developed based on ANO receiving the communication protocol code from the NRC hy August 31, 1991. Recent discussions with the ERDS interface contractor (NUS) have informed us that the NRC coa.munica t ton protocol code for the SCO XENIX operating system will not be available for _

use by the utilities until early 1992. Therefore, based on the attached sof tware development schedule, the ANO ERDS imp 1nmentation schedule has been revised'to June 30, 1992.

NRC letter dated May 15, 1990 (0CNA059026) transmitted a Survey and Data Point Library Reference File form to be completed for each unit. This in f o r ma t. ion will be submitted to the NRC as shown on the attached ERDS Irplementnt ion Schedule.

Also, the final ERDS Rule as published .i n the August 13, 1991 Federal Register requires licensees to submit an implementation plan to the NRC by October 28, 1991 which should address a proposed schedule to complete implementation within 18 months of the effective date of September 12, 1991. Since ANO voluntarily agreed to participate in the ERDS implement.atica program for Generic Letter 89-15, we are not required to resubmit the ERDS information. However, all licensees are required to complete installation by Fenruary 13, 1993. Based on our previous commitment to participate in the ERDS program and our at t ached - rev ised implementation schedule with an expected completion date of June 30, 1992, this fulfills the rule requirements for t he Octohnr 28, 1991 submittal.

"f g

(\mnn-~

9110090124 910930 ADOCKOSOOg3 g' g g

{DR # 0

, U. S. NP.C

. Page 2 Sepbembe* 30, 1991 If you have any further questions regarding this request, please contact me or my staff.

Sincerely, c1+m.}')iare,,,

James J. Fisicaro Director, Licensing JJF/NBM/sjf Attachment cc: Mr. Robert Martin U. S. Nuclear Regulatory Commission Region IV 611 Ryan Plaza Drive, Suite 1000 Arlington, TX 76011 NRC Resident inspector Arkansas Nuclear One - ANO-1 & 2 Number 1, Nuclear Plant Road Russellville, AR 72801 Mr. Thomas W. Alexion NRR Project Manager, Region IV/ANO-1 V. S. Nuclear Regulatory Commission NRR Mail Stop 11-0-23 One White Flint North 11555 Rockville Pike Rockville, Maryland 20852 Ms. Sheri Peterson NRR Project Manager, Region IV/ANO-2 U. S. Nuclear Regulatory Commission NRR Mail Stop 11-0-23 One White Flint North 11555 Rockville Pike Rockville, Maryland 20852 Mr. John R. Jolicoeur U. S. Nuclear Regulatory Commission Mail Statici MNBB-3206 Washington, DC 20555 l

,. 4-l ERDS IMPLEMENTATION SCHEDULE LIEM SIARL DALE COMELEl10N DATE Survey Completed --- 10-28-91 Data Point Library '12-1-91 2-28-92 Generation Receipt of NRC ---

3-31-92 Communication Protocol Code at AND Site Software Development 3-1-92 4-30-92*

Hardware Installation 3-1-92 5-15-92 Implementation / Testing 5-1-92 5-15-92 Site Acceptance Test 5-16-92 6-20-92 EROS Operational ---

6'-30-92

• Software development time may vary depending on the timely development of communication protocol code by NRC for the SCO XENIX operating system.

1 i

l

- _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ __ _. . _ _ _ _ _ _ _ _ _ ____________-_ _ __ _______________ _ _ _ _ _ _