ML20081K765

Emergency Response Data System (ERDS) Implementation

ML20081K765
Person / Time
Issue date:	06/30/1991
From:	John Jolicoeur NRC OFFICE FOR ANALYSIS & EVALUATION OF OPERATIONAL DATA (AEOD)
To:
References
FRN-56FR40178 AD32-2, AD32-2-58, NUREG-1394, NUREG-1394-R01, NUREG-1394-R1, NUDOCS 9107010108
Download: ML20081K765 (80)

Text

- - - - - - -

e NU REG-1394 Rev.I Emergency Response Da~:a Sys:em (ERDS) Imp:ementation U.S. Nuclear Regulatory Commission Office for Analysis and Evaluation of Operational Data J. Jolicoeur e "ca g

uq

+

.rs i

i

%,...../

sR7 En '2 6

1394 R PDR l

{

AVAILABILITY NOTICE Availability of Reference Matorials Cited in NRC Publications Most documents cited in NRC publications will be available from one of the fo!!owing sourCos:

1.

The NRC Public Document Room, 2120 L Street, NW, Lower f.evel, Washington, DC 20555 2.

The Superintendent of Documents, U.S. Government Printing Office, P O. Box 37082, Washington, DC 20013 7082 3.

The National Technical Information Service. Springfield, VA 22161 Although the listing that follows represents the majonly of documents cited in NRC publica-tions, it is not intended to be exhaustive.

Referenced documents available for inspection and copying for a fee from the NRC Public Document Room include NRC correspondence and internal NRC memorandal NRC Office of Inspection and Enforcement bulletins, circulars, information notices, inspection and investi-gation notices: Licensee Event Reports; vendor reports and correspondence; Commission papers; and applicant and licensee documents and correspondence.

The following documents in the NUREG series are available for purchase from the GPO Sales Program; formal hRC staff and contractor reports, NRC-sponsored conference proceed-ings, and NRC booklets and brochures. Also available are Regulatory Guides, NRC regula-I tions in the Code of Federal Regulations, and Nuclear Regulatory Commission issuances.

l>ocuments available from the National Technical Information Service include NUREG series -

reports and technical reports prepared by other federal agencies and reports prepared by the Atomic Energy Commission, forerunner agency to the Nuclear Regulatory Commission.

Documents available from public and special technical libraries include all open literature items, such as books, journal and periodical articles, and transactions. Federal Register -

notices, federal and state legislation, and congressional reports can usually be obtained from these libraries.

Documents such as theses, dissertations, foreign reports and translations, and non-NRC l

conference proceedings are available for purchase from the organization sponsoring the publication cited.

Single copies of NRC draft reports are available free, to the extent of supply, upon written request to the Office of Information Resources Management. Distribution Section U.S.

Nuclear Regulatory Commission, Washington, DC 20555.

Copies of industry codes and standards used in a substantive manner in the NRC regulatory process are maintained at the NRC Library,7920 Norfolk Avenue, Bethesda, Maryland, and are available there for reference use by the public. Codes and standards are usually copy-righted and may be purchased from the originating organization or, if they are American National Standards, from the American National-Standards Institute,1430 Broadway, New York NY 10018.

m...-_,__

)

e

)

NUREG-1394 Rev.1 -

.~.

Emergency Response Data System (ERDS) Implementation U.S. Nuclear Regulatory Commission Office for Analysis and Evaluation of Operational Data J. Jolicoeur on arooq

!),f 2) g.....,,

g 910630 70 1394 R PDR

w k

AVAILABILITY NOTICE Availability of Reference Materials Cited in NRC Publications Most documents cited in NRC publications will be available from one of the following sources:

1.

The NRC Public Document Room, 2120 L Street, NW, Lower Level, Washington, DC 20555 2.

The Superintendent of Documents, U.S. Govemment Printing Office, P.O. Box 37082, Washington, DC 20013-7082 3.

The National fochnical Information Service, Springfield, VA 22161 k

Although the listing that follows represents the majority of documents cited in NRC publica-tions, it is not intended to be exhaustive, Referenced documents available for inspection and copying for a fee from the NRC Public 1

Document Room include NRC correspondence and internal NRC memoranda; NRC Office of Inspection and Enforcement bulletins, circulars, information noticos, inspection and investi-

_{

gation notices; Licensee Event Reports; vendor reports and correspondence; Commission l

papers; and applicant and licensee documents and correspondence.

The following documents in the NUREG series are available for purchase from the GPO Sales Program: formal NRC staff and contractor reports, NRC-sponsored conference proceed-Ings, and NRC booklets and brochures. Also available are Regulatory Guldes, NRC regula-tions in the Code of Federal Regulations, and Nuclear Regulatory Commission Issuances, Documents available from the National Technical information Service include NUREG series reports and technical reports prepared by other federal agencies and reports propSred by the Atomic Energy Commission, forerunner agoney to the Nuclear Regulatory Commission, Documents available from public and special technical libraries include all open literature items, such as books, journal and periodical articles, and transactions. Federal Register notices, federal and state legislation, and congressional reports can usually be obtained from these libraries.

Documents such as theses, dissertations, foreign reports and translations, and non-NRC conference proceedings are available for purchase from the organization sponsoring the publication cited.

Single copies of NRC draft reports are available free, to the extent of supply, upon written request to the Office of information Resources Management, Distribution Section, U.S.

Nuclear Regulatory Commission, Washington, DC 20555.

Copies of industry codes and standards used in a substantive manner in the NRC regulatory process are maintained at the NRC Library, 7920 Norfolk Avenue, Bethesda, Maryland, and are available there for reference use by the public. Codes and standards are usually copy-righted and may be purchased from the originating organi7.ation or, if they are American National Standards, from the American National Standards institute, 1430 Broadway, 1

New York, NY 10018.

NUREG-1394 Rev.1 Emergency Response Data System (ERDS) Innementation Manuscript Completed: May 1991 Date Published: June 1991 J. Jolicoeur Olrice for Analysis and Evaluation of Operational Data U.S. Nuclear Regulatory Commission Washington, DC 20555 ra a%y p

s..... -

A11STRACT The U.S. Nuclear Regulatory Commission has begun implementation of the Emergency Response Data System (ERDS) to upgrade its ability to acquire data from nuclear power plants in the event of an emergency at the plant. ERDS provides a direct real-time transfer of data from licensee plant computers to the NRC Operations Center.The system has been designed to be activated by the licensee during an emergency which has been classified at an ALERT or higher level. The NRC portion of ERDS will receive the data stream, sort and file the data. The users will include the NRC Operations Center, the NRC Regional Office of the affected plant, and if requested the States u hich are within the ten mile EPZof the site.The currently installed Emer-gency Notification System will be used to supplement ERDS data.

This report provides the minimum guidance for implementation of ERDS at licensee sites. It is intended to be used for planning implementation under the current voluntary program as well as for providing the minimum standards for implementing the proposed ERDS rule.

NUREG-1394 (Rev.1)is being issued to provid. guidance that NRC staff believes should be followed to meet the requirements of the ERDS rule. NUREG-1394 (Rev.1)is not a substitute for the regulations, and compliance is not a requirement. Ilowever, an approach or method dif-ferent from the guidance contained here will be accepted only if the substitute approach or method provides a basis for determining that the above-cited regulatory requirements have been met.

in NUlWG-1394, INv. I

CONTENTS Page Iii Abstract...................................................... -

Vil Acknowledgments............................................................

1

1. I n t rod u ct io n.....................................................

2. E R D S I nfo rmat ion.............................................................

I 1

2.1 ERDS Design Concept...................................................

2 2.2 Con c e pt Test s..........................................................

2.3 Survey of Lice nsee Capabilities...............................................

2 6

3. Implementation.............................................................

6 3.1 ERDS Implementation Overview 3.2 ER DS Transmission / Reception Plan..........................................

6 3.3 ERDS Communications Description and Survey Questionnaire.....................

6 6

3.4 Data Point Library........

3.5 System Isolation Requirements....

7 i

3.6 Administrative Implementation Requirements................................

7 7

3.7 Periodic Testing......

3.8 ERDS Questions and Answers....

7 3.9 ERDS Implementation Plan......

7 3.10 Point of Contact..

7 8

4. References APPENDICES A.

ERDS Transmission / Reception Plan H.

ERDS Communications Description and Survey Questionnaire C.

Data Point I.ibrary D.

Data Point Library Reference File Definitions E.

Critical Safety Function Parameters F.

Engineering Units Coding Scheme G.

Zero Reference Coding Scheme II. Coding Scheme for Unit Name and Unit ID I.

Computer Point Selection J.

ERDS Questions and Answers v

NUREG-1394, Rev.1

i ACKNOWLEDGMENTS J

i The author wishes to acknowledge the efforts of Mr.T. Laitosa and Ms, L Saul of the II, sion of NUS Corporation, the NitC IlitDS implementation contractor. A number of the appen-dices enclosed in this report are the direct result of their efforts in managing the development of the FitDS system.

t 1

i i

s t

i i

i r

vii NUR!!G-1344. Rev.1

EMERGENCY RESPONSE DATA SYSTEM (ERDS) 1.

Introduction As a result of the Three Mile Island Unit 2 accident on March 28,1979, the NRC and others recognized a need to substantially improve the NRC's ability to acquire data on plant condi-tions during emergencies. Before designing a system to accomplish that task, the NRC first needed to resolve a number of bacisground issues. These issues were:(1) What is the appropri-ate role for the Commission during an accident? (2) What information is needed by the Com-mission to support this role? and (3) Are any changes necessary in Commission authority to enhance Commission response to nuclear emergencies?

The Commission has defined the NRC's role in the event of an emergency primarily as one of monitoring the licensee to assure that appropriate recommendations are made with respect to offsite protective actions. Other aspects of the NRC role include supporting the licensee witl technical analysis and logistic support, supporting offsite authorities (including confirming tb licensee's recommendations to offsite authorities), keeping other Federal agencies and entiti informed of the status of the incident, and keeping the media informed on the NRC's knowledge of the status of the incident including coordination with other public affairs groups. This role was studied by the Office of the Executive Legal Director (now Office of the General Counsel) who determined that the NRC's legal authority provides a sufficient basis for the Commission's emergency response role.

To fulfill the NRC's role, the NRC requires accurate timely data on four types of parameters:

(1) core and coolant system conditions must be known well enough to assess the extent or likeli-hood of core damage: (2) conditions inside the containment building must be known well i

enough to assess the likelihood and consequence of its failure:(3) radioactivity release rates must be available promptly to assess the immediacy and degree of public danger; and (4) the data from the plant's meteorological tower is necessary to assess the likely patterns of potential or actual impact on the public.

Experience with the voice only emergency communications link, currently utilized for data transmission, has demonstrated that excessive amounts of time are needed for the routine trans-mission of data and for verification or correction of data that appear questionable. Error rates have been excessive; and there have been problems in getting new data and frequent updates. In addition, the current system creates an excessive drain on the time of valuable experts. When errors occur, they can create false issues which, at best, divert experts from the real problems for long periods of time. At worst, incorrect data may cause the NRC to respond to offsite officials with inaccurate or outdated advice that results in inappropriate actions.

2.

ERDS Information 2.1 ERDS Design Concept The system selected to fulfill the data collection needs of the NRC is the Emergency Response Data System (ERDS). The Emergency Response Data System concept is a direct electronic transmission of selected parameters (Figures 1 and 2) from the electronic data systems that are currently installed at licensee facilities.

The ERDS design (Figure 3) utilizes DEC MicroVAX 3600 mini computers as system main-frames. These will be used to receive, sort, and file the incoming data stream. User stations will l

I NURl!G-139.t Rev. I

be PC based stations where the data may be accessed, processed, and displayed. System users willinclude the NRC Operations Center in Bethesda, M D, the NRC Regional Office, the NRC Technical Training Center, and if requested the States which are within the ten mile EPZ of the site.

The ERDS would be for use only during emergencies and would be activated by the licensees during declared emergencies classified at the ALERT or higher level to begin transmission to the NRC Operations Center. The ERDS would be supplemented with voice transmission of; essential data not available on licensee's systems rather than require a modification to the exist-ing system.

2.2 Concept Tests The concept of electronic data transmission was first tested on July 19,1984 from the Duke Power Company system at the McGuire facility. The data transfer was accomplished using an electronic mail type arrangement which, although not a real-time system, allowed for electronic data transfer.He data set was limited to a list of 69 specific data points to test the appropriate-ness of the NRC's parameter list.

A test of data transmission of 60 specific data points was successfully conducted on August 13,.

19S5 from the Commonwealth Edison system at the LaSalle facility.

A data transmission system was also established for the Zion Federal Field Exercise. The data transmission and rece'ipt methodologies were essentially the same as the test conducted with LaSalle, but several data display techniques for the NRC Operations Center were used. The data set consisted of 65 data points.

The tests of the ERDS concept have demonstrated that there is great value in using electronic data transmission for obtaining a limited set of reliable, time tagged data. The NRC response teams functioned more efficiently and their assessments were more timely. Major improve-ments in ability to focus on the significant factors and to predict the course of events were noted.-

The questions that were asked of the licensee were focused on overall status and course of action

{

rather than simple data requests, therefore reducing the volume of communication and increas-ing the quality of the communication.

2.3 Survey Of Licensee Capabilities An ERDS Requirements Analysis was conducted in 1986 that included survey visits at 59 plant sites representing 92 reactor units.The focus of the site surveys was to review the design of the data systems on site and availability of the data to be provided to the NRC.The following sum-matizes the availability of the ERDS parameters for the surveyed facilities:

i The average availability of points for applicable parameters at BWRs is 78.7 percent.

No BWRs had 100 percent of the applicab'c parameters available as transmittable computer points.

The average availability of points for applicable parameters at PWRs is 92.6 percent.

Eleven PWRs had 100 percent availability.

With regard to the capability of the current hardware environment at the sites to sup-port the generation of a data feed to ERDS, approximately 5 to 10 percent of the licen-see systems are running at close to 100 percent processing capability now in the post -

NURiiG-1394, Rev. I 2

)

trip or incident environment and approximately 10 to 15 percent of the licensee sys-tems are hardware limited (e.g., no available output port for an ERDS connection),in many cases however, the licensees with hardware limitations are planning equipment upgrades in the near future for reasons other than supporting ERDS.

Primary Coolant System Pressure Temperatures-llot Leg Temperatures-Cold Leg Temperatures-Core Exit Thermocouples Subcooling hlargin Pressurizer Level RCS Charging / Makeup Flow Reactor Vessel Level (When Available)

Reactor Coolant Flow Reactor Power Secondary Coolant System Steam Generator Levels Steam Generator Pressures Main Feedwater Flows Auxiliary / Emergency Feedwater Flows Safety injection liigh Pressure Safety injection Flows Low Pressure Safety injection Flows Safety injection Flows (Westinghouse)

Borated Water Storage Tank Level Containment Containment Pressure Containment Temperatures liydrogen Concentration Containment Sump Levels Radiation Monitoring System Reactor Coolant Radioactivity Containment Radiation Level Condenser Air Removal Radiation Level Effluent Radiation Monitors Process Radiation Monitor Levels Meteorological Wind Speed Wind Direction Atmospherie Stability Figure 1. PWR Parameter 1.ist 3

NURiiG-1394, Rev.1

Primary Coolant Splem Reactor Pressure Reactor Vessel lxvel Feedwater Flow Reactor Power Safety injection RCIC Flow HPCI/HPCS Flow Core Spray Flow LPCI Flow Condensate Storage Tank lxvel Containment Drywell Pressure Drywell Temperatures liydrogen and Oxygen Concentration Drywell Sump Levels Suppression Pool Temperature Suppression Pool Level Itadiation Monitoring System Reactor Coolant Radioactivity Level Primary Containment Radiation Level Condenser Off-Gas Radiation Level Effluent Radiation Monitor Process Radiation Levels Meteorological Wind Speed Wind Direction Atmospheric Stability 1 igure 2. IlWii Parameter 1.ist N UIlliG-1394, lies.1 4

SYSTEu CONSOLE SYSTEM CONSOLE m

LA7S LA75 [

VT323 PRNTER CRT l

PP!NTER]

[

CRT O

Rm Q ueAx 3soo

,'.55.y

/M Meu 3sao (22MB 16MB MEMORY I TK70 TAPE l 1EMB uEMORY DISK TK70 TAPE I N

l 8

CAR m O %

U U

24 R PORTS

4y 32 RTS 16 RS423 PORTS R">421 FAftovTR UNE 16 RS423 PORTS TS05 9-TRACK T5059 TRACK RS232 AND RSa23 UNES RS?32 AND RSA23 UNES CCOE X 6015 MUX l MODEM CC!TT v32 9&O Bs RS423 ONES MULTIPLE RS232 ONES T-BAR 36 CHANNEL RSTjfMT FEEDER <

CODE X SW"TCH!NG SYSTEM DIRECTORS SITES 6015 MU STAitON M

MODEM CCITT REACTOR v129 moas SAFETY TE AM t=,.

g I

Meaubsth HA 3905 ADK Cm 3E3 teu x24 19 Meretor MODEu CCITT Mrsutwa HA 390s AoK PROPRINTER v22 2ano es 1F" Morer

/

i PROTECTNT.

F EDER 4 y ;gn g

MEASURES DWW SITES NAM LB 815 UNE PRINTER I MODEu CCITT g r-T a

v222400 Bs j Compaq 3E3 IBM X24 Mttstusrv HA 3905 AOK PROPR.NTER TNTE.RMEDIATE DOSE ASSESSMENT SYSTEM UtiK s

l

/

17 Memor MODEM CCITT

, V22 2400 B/S N

EXPERT SYSTEM LINM l MODEu CCITT OPPICE R tw l v22 2g00 Bs rm 1

\\

Compaq 385/25 sBM X24 MOCEM CCITT I M m HA M ADK PROPRINTER OTHER 4 V?2 24ro B.s l 1F# Monster USERS MODEM CCrTTI V22 2O R,s]

l l

STATUS i

r--

MODEM CCITT 01 SPLAY g%

TEM, TRON!X

<e 3ncs

=

v22 zuc B.s N Ma z

CoMPAo sac 3 l

5 nErtnrNECE onawNc3 MITSLS$H13710 37" MOCR i

BF6-T303DO - EROS HOST COMPUTER CONTIGUPATION 4

BFS-7004DO - EROS CPERAT10NS CENTTR EQUIPMENT CONFIGURATION

-y Bf 6-TD10D0 - EFOS COMMUNICAT10NS INTERCONr.ECTIONS p

C FIGURE 3. NRC EMERGENCY RESPONSE DATA SYSTEM c$

i 3.

Implementation 3.1 ERDS Implementation Overview As an ERDS participant, the licensee is expected to provide a real time data stream of data point values from an existing computer system (s) to NRC provided equipment. Since ERDS treats each reactor unit as an individual plant, a separate data stream is required for each reac.

tor unit. The licensee is expected to provide the software to extract the data point engineering values frem their system, organize them into a standard sequence, and to translate values from internal cornputer format into ASCII or EBCDIC. The data points to be included in the trans-mission are those which to the greatest possible extent satisfy the NRC desired parameter list.

Any parameter which is not available to be electronically transmitted from a licensee system will not be backfit, but willinstead be provided in verbal transmissions as needed during an emer-gency. In additim to the data point identifiers and values, the transmission should include the quality (validated, questionable, bad, etc.) of the data point value. The data will be transmitted to the NRC over dial-up telephone lines. The NRC is planning an upgrade of its Emergency Telecommunications System that would include ERDS, but the details of this upgrade have not i

been decided. In addition to the computer related aspects of ERDS implementation, adminis-trative and quality assurance / configuration controls must be established. The steps necessary for a licensee to implement the ERDS program are outlined in the following sections.

4 I

3,2 ERDS Transmission / Reception Plan The ERDS Transmission / Reception Plan (Appendix A)was developed by NUS Corporation, El Division, the NRC ERDS implementation contractor, to provide a procedure for licensees to follow in completing the computer application portions of the ERDS implementation. It estab-lishes the sequence for correspondence, meetings, computer application development, and test-4 ing.

3,3 ERDS Communications Description And Survey Questionnaire The ERDS Communications Description and Survey Questionnaire (Appendix B) was de-signed to provide the hardware, communications, data point, and administrative information necessary to design the ERDS system interface and data base for each reactor unit. When in-structed to forward this questionnaire to the NRCin Appendix A,it should be forwarded to the NRC in accordance with the regulatory requirements set forth in 10 CFR Part 50.

Also included in Appendix B is the description of the data communication methodology to be used in the ERDS implementation. Individual computer system limitations which prohibit the use of the generic communication protocol should be addressed in the questionnaire.

3.4 Data Point Library The Data Point Library as described in Appendix C will be used to provide background infor-mation concerning each individual data point in the licensee data stream to better define the data point for the NRC technical teams. This provision was made to compensate for plant to plant differences in instrumentation.The data points outlined in the ERDS desired parameter list will be used to define generie displays for PWR and BWR units. Experience to date with early ERDS volunteers has shown a desire on the part of some Feensees to send parameters not included in tiie desired list. The individaal data bases for each unit will have a limited amount of additional space to allow for the addiuon of plant specific data points to the data stream. Plant j

specific data points which a licensee considers valuable to the assessment of critical safety NUREG-.1294. Rev. I 6

functions may be submitted for consideration as possible additions to the data point library.

Appendices D. !! F. O,11. rmd I provide amplifying information to be used to aid in computer point selection and Data Point 1.ibrary completion.

3.5 System isointion 1(equirements While it is recognized that EllDS is no: a safety system. it is conceivable that a licensee's lil(DS interface could connnunicate with a safety system. In this case appropriate isolation devhes would be required at these interfaces.

3.6 Administrative implementation itequirements lil(DS implementation will entail a change in the way the licensees provide data to the NitC during a plant emergency. As such, limergency Plan implementing procedures should be modi-fied to require EllDS to be activated as soon as possible within one hour of the declaration of an Alert or higher emergency classification level.

Configuration management is an integral part of assuring the quality of a data network of this slee. Part of the imp!cmentation plan must address procedures which will be followed to ensure the integrity of th;; lillDS hardware and software wnfiguration at each reactor unit.These pro-cedures should include provisions to allow NitC to icview proposed system modifications which could affect the data communication protocolin advance of those changes to ensure that the changes are compatible with the EllDS. Changes to the Data Point I ibraiy should be sub-mitted using the Data Point Libtary 1(cference File Form itom Appendis C within thirty days of the change.

3.7 Periodic Testing in order to verify syste:n connectivity, periodic tests of the lillDS data link will be conducted with each licensee. The tests will be coor dina!. d by the NI(C and consist of operational tests of the licensce's El(DS data communications. The initial testing periodicity will be quarterly.

3.8 EllDS Questions And Answers Appendix J provides answers to frequently asked questions conceining the lillDS implementat-son progsant 3.9 EllDS Implementation Plan I itensees implementing EllDS under the cuitently proposed rule would be seguired to submit an implementation plan within 3 days of the effective date of the final rule. In submitting implementation plans the licensee should address (including a propowd schedule) allitems noted in the lillDh Transmission!!(eception Plan (Appendix A). With regard to item 1 of the Transmission /lleception plan, alllicensees will be considered to have received the site survey s.aestionnaire as a tesult of ieceiving this doet ment (see Appendices 11 through 1).The adminis-trative requirements of section 3.6 should atoo be addressed in the implementation plan.

3.10 Point Of Contact Any questions concerning the liRDS implementation program should be referred to:

7 NUltthl394, llev. I

Jolm it. Jolicoeur EllDS l'roject Manager U.S. Nuclear llegulatory Commission Mail Stop MNiill 3206 Washington, DC 20555 Tel: (301) 492-4155 4.

References 1.

U.S. Nuclear llegulatory Commission,"Iteport to Congress on NRC Emergency Commu-nications" USNitC lleport NUllEG-0729 Septc.nber 1980 2.

U.S. Nuclear llegulatory Commission,"Iteport to Congress on the Acquisition of lleactor Data for the NitC Operations Center," USNitC lleport NUREG-0730, September,1980 3.

U.S. Nuclear llegulatory Commission," Emergency llesponse Data System Generic 1ettu No. 89-15," August 21,1989 4

til International, Inc., "Ilaulware Design Document," lleport Number, NitC-201, July 1, 1988 4

i l

i NLJRl:0-1394, Itev.1 g

7 APPENDIX A EMERGENCY RESPONEE DATA SYSTEM (ERDS)

TRANSMISSION /kECEPTION PLAN lit international, Inc.

~ -. -.-._.. _. - ~ - -. -... -.

1 t

d k

1 i

Contents i

i 1

l' age l

a j

i n t r od u ct ion.....................................

A-1 S c o pe o f Wo r k..............................................................

A-1 A-1 i

l iar dwar e itequirements.....................................................

l So f t wa r e Ta s k s............................................................... A-1 listablishing the Data l'oint Library and the I'lant Attribute 1.ibrary............... A-1

]

Incorporating the Utility into the !!!(DS........................................ A-2 l

Steps llequired to incorporate the Plant into the filtDS......................... A-2 S u r n i n a ry................................................................... A-3 i

Schedule..................................................................

A-4 0

1 At ta ch ment A - Sa rn ple Sched ule............................................. A-5

)

t

]

d a

r 1

i j

l J

i 3

t i

1 J

f 4

.nn-nc,,.,-

--.-n,r-a v

w,- - - - +, - - - - - - - - -- - ~

we,--n,

,~re

-~wr,

---~-,rw

,-e.

-,v.,

n---,-.

,-~~~n

i Introcluction

'the purpose of this document is to describe a plan which will allow the Nuclear llegulatory Commission (NitC) to survey and incorporate the utilities which have agreed to participate in the lirnergency llesponse Data System (lillDS) program into the limergency llesponse Data System.

1 Scolie of Work A significant por tion of the wor k scope for the tillDS includes developing a communications link with each of the participating nuclear utilities. This link will establish a means for the utility's plant computer ( ) to auto-matically transtnit predefined data points to the !!!(DS computer at the request of the Nuclear Isegulatory Conunission.

To perform this function, both the EltDS and plant cornputers must be software and hardware compatible.

'lhis compatibility exists at the data f ransmission interface level.

Ilarchyare llequirements Acwmplishing the hardware interface for the EllDS is straightforward and consist of standard off-the-shelf components.

'Ihe hardware interface requires:

Single feeder Sites:

an itS-232C asynchronous ruodem control port :md nvadem on each end of the communication line.

Multiple feeder Sites:

Multiple-feeder plants will require a multiplexer to be placed between the modems and computer (s)

IIS-232C ports.

Multiple-feeder sites may be converted to single feeder sites utilizing the approach described in step 70f this Appendix and item 150f Appt ndix J.This approach simplifies the implementation of EllDS for multiple feeder sites by reducing software development enforts.This option provides a pretested ERDS interface supplied by NitC.

Solhvare Tasks The software tasks associated with the data interface are plant specific with a data reception enmmunications program residing on the lillDS computer. In certain situations limited custom software will be written for the ERDS.

The plant specific softwaie ine!udes transmitting the actual data points to the Data Point Library (DPL)in the liRDS. These data points will essentially comprise a database (formally referred to as the DPL) which will reside on the ERDS and be made available to the users whenever a utility is transmitting data.

Establishing the Dl'L and the I'lant Attribute Library (l'AL)

Since the focal point of the ERDS is the DPL, a concentrated effort must be put forth to ensure that the DPL j

for each utility is acentate and that the software protocol for transferring these values is known to the ERDS software.

l A-1 NUREG-1394, Rev.1 i

i j

The lilli)S database, or I)PL, contains specific infor mation about each data point,i.e., point II), description, engineering units, etc. Storing this infm mation in the lilli)S climinates the necessity to transmit the infor ma-tion with each data set.

'lhe I'lant Attribute 1 ibrary(pal )contains the communications information necessary to communicate with each utility and remains on file within the system as a reference to establish the utility's software protocol requirements uhich the liltl)S can espect to accommodate during data transmission. Without the PAL infor-mation, it would not be possible to conununicate with the plant computer, incorporating the Utility into the ERDS The plan for incorporating ec h utility into the lillDS consists of the steps outlined below and are conunon among all the participating licensees.

In preparing this plan, the activities requir ed to incor potate the utility into the I!!(1)S were identified based on experience gained f rom the few site surveys that have been conducted to date. Understanding that not all utilities operate in the saine manner, the steps described herein represent the basic os minimum effort re-quired to inemporate the plant into the lilti)S.

Depending on the utility's and NitC's schedule, tasks can i e added or rearranged to acconunodate the situation.

Steps Required to incorporate the I'lant into the ERDS The iequired activities for participating in the liltl)S program are:

1) The NitC notifies the contractor, NUS Corporation, lil Division (NUS-lil), that a utility has received a site survey questionnaire.

This questionnait e consists of several enclosures which inquire about the plant computer capabilities and the available data points to be transtuitted to the lillDS.

Identification of these data points is the most tedious effort required of the utility because the response essentially forms the littl)S database (the DPlf) and, as described in previous sections, the DPL ir the local point of the liitDS. lif foits must be made to ensure the accuracy of the DPL and that the softwate protocol for transferring these values is known to the littl)S softwate.

1

2) Alter the utility has icecived the questionnaire, they will be contacted by NUS-lil.

1 NUS lit personnel will contact the utility to discuss the items within the site smvey questionnaire along with typical utility r esponses, to desciibe NUS-lil's imolvement in the lillDS program, to answer general and specifie questions legar ding what is expected of both the utility and N US-lil, and to convey NUS-lil's experiences and/or problems leained from other participating utilities. If the utility was not part of the pre-littl)S survey, an NUS-lil representative will assist the utility in selecting plant data points which f ulfill the NitC's requested parameter list.

3) A site visit will be airanged.

A visit is not mandatoiy but should be conducted prior to the licensee's return of the DPI and l'Al in an cifort to minimize criots in answeiing the questionnaire, If necessary, the visit can occur after the Di L and pal are submitted. In a very few eiicumstances, a visit may not be necessary; however, this is not r ecommended.

-1 ) 'lhe NiW will install phone lines at the site.

NUltI-n 1341. Itev.1 A _2

5) The utility then answers and returns the site suncy questioimaire containing the 1)Pl.and pal.

intornution to the NitC Veibal communicatiorn between the utilitis contact and NUS lil personnel are ongoing during this pluse in preparation for sof tware development on both ends of the data link and establishment of the littl)S database.

6) If the plant's computer system requires customi/cd liltl)S reception soltware, specific littl)S code will be developed and implemented by NUS-lil.

This may not be required if the licensee's system can conform to the " generic" software protocols of the littl)S.

7) In parallel with NUS-lil software development, the utility will design and write their data trans-mission sof tware. The NitC IIIII)S implementation contractor is developing a PC based littl)S interface which will perform all littl)S cornmunication protocol functions for single-feeder or multiple feeder plants (see Appendix.1, item 15).

1)uring this phase, NUS-lil will continue to provide consulting assistance to the utility's programmers in preparation for a preliminary software test. Any required tiansmission equipment including modem (s) and. il necessary, multiplexer (s) will be shipped to the utility during this phase.

8) Preliminary soltwaie testing is the next step and is the first attempt at transferring data between the plant and lilti)S computers.The preliminary sof tware test performs initial data transmis-sion testing of the utility's software and any custom code NUS lil has developed.This is in actu-ality the soltware debupping period and problems are to be expected.

This step is complete when data can be transmitted by the utility's plant or developmem computer and the Elli)S computer without error.

n) Following the preliminary sottwaic tests and the initial data transference between the plant and the lilli)5 computers a for mal test will be conducted at NUS-lit prior to adding the licensee to the Elli)S.

Upon suct efu! completion of this test, the 1)PI, pal, and any special software routines will be incorporated into the Elli)S pioduction computer. At this time, the utility will be transmitting data from their plant computer and not their development system.

10) A formal test is then conducted on the tiltl)S computer at the Operations Center.This is the final test to demonstrate system functionality. Again, data transmission will be from the desig-nated plant computer system.

I1) The final step in the schedule has the utility on-line with alldevelopment and testing completed.

Stimmary The eleven (l1) steps as outlined on the previous pages are to be used as a guideline for scheduling and accom-plishing the tasks requited to incorporate the utilities into the liltl)S. Again, understanding that not all utili-ties operate in the same manner. the steps as previously outlined represent only the basic approach to the efforts required. Tasks can be added or rearranged to acconunodate each utility.

The most significant portion of the woik scope of this plan is the development of the communications link with each of the participating utilities. While the hardware inter face for the lilli)S is straightfonvard, consisting of olf-the shelf har dware, the software tasks are plant-specific and require a dedicated ef fort in establishing the A3 N UllEG-1394, llev,1

1 I

I)ata Point Iibrary and the I'lant Attribute 1ibrary. 'lhe lil(DS Communications Description and Survey Questionnaire (site survey questionnaire) esplains in detail the purpose of collecting this data, provides de-scriptions and esarnples of the data streams the lillDS is especting to see transtnitted over the conununica-j tions lines, and provides sarnples of forans to be filled out and returned as part ofimplementing thisTransmis-sionliteception Plan.

it is of vitalirnportance that a dedicated ef fort be put forth to ensure the accuracy of the information in the

{

questionnaire (the Dl't.) for each utility. 'ihe contractor's (NUS lil's) personnel are available to assist the utility during all phases of this plan including the selection of hardware and sofhvare interfaces and, most importantly, <Juring the selection of the required data points.

Selledtlle The attached sample schedule (Attachment A) presents a visual display of the milestones associated with the implementation of this plan and is an actual schedule of a participating plant.'this schedule can be used as a guide for each utility to project schedules and testing dates.'lhe scheduled milestones represent the eleven (11) steps as outlined in this plan.

L NUltlM i-1341. Itev,1 A -.1

l l

9 9

3 8

J 0

C 3

E 9

)

k I

e 0

I t

1 a

9 D

9 0

I I

A A

1 P

P a

s I

V O

A ta P

D O

l l

N 7lA 1

4 4

8 I

A 9

I 6

P 8

A 0

P T

I C

A O

P SN O

9 5

I 3

0 S

I I

V P

A E

E P

R S

I 91 G

UA 3

e 0

l u

9 d

I S

A e

P h

L c

U 2

S J

0 c

S i

l p

T C

5 A

1 C

N 0

0 P

m I

4 9

a E

J 3

S S

I A

O 8

R A

N P

l P

N D

U l

A I

J O

D S

r I

E T

L

~N N

A L

9 E

N A

8 I

M R

R F

Y 1

l 3

E O

A l

O T

C M

A I

C N

I A

N T

I C

D O

T l

S P.

E I

A I

N RA v

P l

x s

OC E

R ET G

I A

N I

N S

T I

N T

D N

iF O

S N

E I

U E

E R

E I

IT N

A L

T C

G R

S R

P P

N R

E.

U I

E E

V L

j D

l O

E N

C I

U E

E P

R W

I I

I Q

T V

I S

f N

R N

D O

S S

(

6 S

U U

O S

I P

Y T

1 E

L S

1 E

I N

W O

3 I

1 I

V P

R S

L S

r.

N O

E I

I I

L U

E N

I L

E I

I E

V L

I S

I L

T P

V A

r I

N C

T i

T T

I T

S O

E C

A E

E R

t L

N CA R

A T

T R

O.

D T

I O

E C A T T S l

I T

T C

S I

i I

1 N

E N

Y E

Y I

T T

Y J T U A N E I

S I

I O

V T

I T O E L I

I C

N C

L L

L W

W F

R R C L V I

O D

T I

I E

I I

L I

D E

T T

P C A F E S I

I I

I I

T O

H T

l I

T R

S A

I U

E C

N U

U P

F S

II I

1 2

3 4

5 6

7 8

9 0

I 0

0 0

0 8

0 0

0 0

1 I

I I

I I

I I

I I

I I

I A

A A

A A

A A

A A

A A

P P

P P

P P

P P

P P

P I

I I

I I

I I

I I

I I

> m ZCA'mO hch 3r f

{ll 1

i

1 l

APPENDIX B i

ERDS COMMUNICATIONS DESCRIPTION AND SURVEY QUESTIONNAIRE 1

4 f

1 1

l l

APPENDIX 11 EltDS COMMUNICATIONS DESCillPTION AND SUltVEY QUESTIONNAlltE The following is a questionnaire pertaining to the Nuclear llegulatory Commission's (NRC) limergency itesponse Data System (EllDS). It consists of a scrics of questions concerning plant 1/0 points, software protocols, dath formats, transmission frequencies, and other plant com-puter specific information to be usef in the ERDS computer database files. Also, included here are descriptions and examples of data streams that the NRC is expecting to see transmitted over the communication line.

The purpose of collecting the data is to develop a plant specific database that will be retrieved into the liitDS once the system is activated by a utility. It will also be used to design and imple-ment ERDS software that can receive the utility's data transmission. In essence, this informa-tion will provide the basis for building a profile of the plant in the ERDS database.

In some cases, the 1/0 point data may be distributed over several computers. The ERDS consid-ers this situation a multi-feeder site and Section IV must be filled out for each feeder.

For plants that utilize the PC based interface described in Appendix J, item 15,Section IV must be filled out for the ERDS interface PC as well as each computer which feeds data to the inter-face PC.

This request is covered by Office of hianagement and lludget Clearance Number 3150-0150 w hich expires hlarch 31,1992.The estimated average burden hours is 32 person hours per licen-see response, meluding staff and management review and preparation of the requested re-sponse. These estimated average burden hours pertain only to those idemified response-related inatters and do not include the time for any follow on implementation. Send comments regard-ing this burden estimate or any other aspect of this colle,; tion ofinformation, including sugges-tions for reducing this burden, to the Records and Reports hianagement Ilranch, Division of j

information Support Services, Office of Information Resources hianagement, U.S. Nuclear Regulatory Commission. Washington, DC 20555; and to the Paperwork Reduction Project (3150-0150). Office of hianagement and lludget, Washington, DC 20503.

11-1 NURl!G-13N, Rev.1

j

l. Contacts j

Note: Please provide name, titic, mailing address, and plione number.

A.

Survey Coordinator (i.e., contact for later clarification of questionnaire answers):

11. Computer ilardware Specialist (s):

C.

Systems Sof tware Specialist (s):

1).

Application-level Software Specialist (s):

IL Telephone Systems Specialist (s):

NUliliG-1394.1(es. I 15-2

11. ERI)S Communications Description A.

~ anhvu n-

'I N following haidware wi'i be supplied; for a single feeder site:

Codes 2235 inodem or equivalent - V.22 24tH) bps, asynchtonous auto-dialing, auto-answer, error correcting, using the AT conunand set for a multiple-leeder site:

Codes Nil 5 multiplexer, CodcN 22M modern or equivalent - V.32 96(W) bps, asynchronous, auto-dialing, auto-answer, error-coriceting, using the AT Colnfiland set (for an alteinate approach see Appendix A, item 7)

'the moderns are intended to be operated in the auto-ieliable link mode (ref erred to as h1NP in the modem inanuals).There are several modem parameters that alteet hiNP operation.These are discussed in the sections of the modem inanuals pertaining to h1NP. The single feeder mo-dems at the NitC Operations Center are configured for auto reliable link mode, local terminal flow control, and def ault break handling.

11. Softw are 1.

1)ata Transmission All transinissions, from both the site and the lillDS, will be tenninated with a carriage icturn

( < Cl( > ).

Site willinitiate a link request in ASCil using:

a.

6 the thice-character site designator, the word I lNK, local site tiine and date in the format hihi/DD/YY/Illl:hth1:SS, and a < Cll >.

If the site does not Icecive a response from the Ei(DS within one minute,it should send another link icquest message and continue sending them at one-minute intervals. If more than live minutes elapses uthout a response, site personnel should notify the NllC before disconnecting the line.

b.

lillDS will respond in ASCil with:

the three-character site designator, the word ACCEPTED or DENIED, and a < CI( >,

if the EllDS responds with the denied message, the site should wait one minute and then send a link request message and continue sending them at one-rninute intervals. If 11-3 N Ultl!G-139-1, Ites.1

more than five minutes elapses without a response, site personnel should notify the NitC befere disconnecting the line.

When the liitDS is leady to acceive data, it will send an initiate inessage in ASCil c.

usmg:

l the three character site designator, the word INITIATli, and a < Cit >.

t if the I:llDS does not send an initiate message within one minute of the accept mes-sage, the site shouhl send the link reconnect message (described in Section ll.lli.f.).

d.

Upon receipt of the initiate inessage, the plant begins transmission of data at a 15 second sate. The data stiing consists of:

a header containing the three-character site designator and date and tirne in the format hiht/DD/YY/llil:h1Nt:SS, the data packet sequenced with point identifier, value, and quality tag, a trailer containing the checksum value of the data packet, and a < Cit >,

When the site or liltl)S wishes to terminate the connection. an ASCil message will be c.

sent containing:

the three-chalacter site designator, the word Tl!!1hilNATii, and a < Cit >.

f.

If a site is inadvertently terminated (due to loss of communications or receipt of teimi-nate message) and the incident is still underway, the site should reconnect with the lilt DS by tedialing and using the link icconnect message. The link reconnect message should be used any time the phone line is lost after the receipt of an Accept hiessage (desciibed in Section ll.lt 1.b). This message is in ASCll and will contain:

the three-character site designator.

the word IlliCONNIICT, local site time and date in the format Nihi/DD/YY/illi:hthi:SS, and a < Clt >.

Upon teceipt of this message, the liltDS will respond with the accept and initiate mes-sages as described in Sections ll.it1.b and li.II.l.c. If the lillDS responds with a link deny message (described in Section ll.Ill.b), the site should stop trying to ieconnect and send a link request message (described in Section ll.it t.a). If the liltDS does not tespond to the site's icconnect request within one minute. the site should send another reconnect request and continue sending reconnect requests once a minute. If more than five minutes elapses without a response, site personnel should notify the NitC befoie disconnecting the line. It is the responsibility of the site to monitor the outgoing line for loss of communications.

Once a physical connection has been established with the NiiC, the site should not disconnect the phone line until a TliitN11 NATL! message (described in section NURIEl3% Rn. I 164 l

ll.II,1.e) has been transmitted. If problems are encountered in the link request se-quence, do not hang up the line but proceed with the steps outlined above.

g.

If the site will transmit in lillCDIC rather than ASCil, the following applies:

(1) Thelink request message (defined in ll.II.l.a)and the reconnect message (defined in ll.II.1.f) must be in ASCil.

(2) All replies sent by the lillDS to the site will be in ASCll.

(3) The terminate message sent by the site may be in lillCDIC or ASCll.

(4) All update sets sent by the s!te inust be in EllCDIC.

2.

Data l'ormat The following three delimiters have been identified:

(1) field delimiter (*),

(2) data set delimiter (\\), and (3) carriage return ( < Cll> ).

Note:

The length of the messages sent by the lillDS (e.g., ACCl!PTED, DliNil!D, INITI ATE TiiRMINATE) are vatiable and it is reconunended that the site soft-ware use the data set delimiter as the message delimiter for messages received from the !!RDS.

Link requests will be in ASCil as described in ll.ll.1.a. with each field separated by a a.

field delimiter and the request terminated with a data set delimiter. For example, PA 1 *l.1 N K'01/12/89/11:4S:50\\ < CR >.

b.

The ERD $ vesponse will be in ASCll as described in ll.13.1.b. with each field sepa-rated by a field delimiter and the response terminated with a data set delimiter. For example, pal

• ACCEPTED \\ < CR >.

When the ERDS is ready to receive data it will respond in ASCll as described in c.

ll.ll.1.c with each field separated by a field delimiter and the response terminated with a data set delimiter. For example, pal *1NITIATE\\ < CR >.

d.

Data streams will be in ASCil and will consist of three parts (header, data, and trailer) as described in ll.13.1,d. with each field separated by a field delimiter and each of the three parts separated by a data set delimiter. For example, Ileader: pal *01/12/89/ll::,0:30\\

Data:

ll21CP004*-0.1234LI+ 00*3'..(for each parameter)\\

Trailer:

0000056000\\ < CR >

The point identifier may be up to 12 characters in length, c.

f.

The value may be up to 20 enaracters in length.

l 1

lb5 NUltliG-139.t. lley. I

g.

'the following quality tags will be accepted by the filtl)S:

Good

=0 Value is within iange tolerance for discreet points or in-f put points are within tolerance for composed points.

l Oll scan

=1 l'oint is currently out-of service, 1

Suspect

=2 Value is not bad yet should not be considered good. This j

quality will occur primarily on composed values when enough good inputs are present to allow the calculation to be made yet a bad quality on other inputs inay make i

the result questionable.

Ilad

=3 Value is not within tolerance for discreet points or calcu-(

lation of a composed point may not be made due to the qualities of its inputs.

Unknown 4

No quality indicator available.

u Upciator lintered 5

Value has been manually entered, overriding the dis-

=

cicet or composed value.

liigh Alarm 6

Value is in high alann.

n I ow Alarm 7

Value is in low alarm.

=

h. The checksum w hich accompanies each update set will be an integer value calculated by sununing each of the bytes of the transmission, un to and including the dataset de-limitet following the body of the update set (the body of the update set being the por-tion containing the pat ameter, value, and quality indications). This integer checksum value will then be encoded into the update set as a 10-digit value, left padded with zeros a:, required to fill the 10-digit field. The checksum is the sum of the transmitted bytes.

i.

The rec ( nnect link request message will be in ASCll as described in Section ll.il.l.f with eacl field separated by a field delimiter and the request terminated with a data set delin. iter. For example, pal *ltliCONNECT*01/12/Will:4S:50\\ < Cl( >.

3.

I'rotocol lilil)S will use XON/XOFF to stop, resume, or suspend data transmission for the site.

a.

b.

Communication parameters:

eight data bits 1 stop bit parity = none 4.

Faceptions Please note any exceptions which must be taken to Section 11 and esplain why.

NlmlE1394, licy. I 15-6 3

111. Selection Of Data Feeders A.

Ilow many data feeders are there (six maximum)?

11.

Identify tiie selected data feeders and piovide the following for each:

(1) a short description of the categories of data points it will provide (e.g., inet, lad, or plant data points, by unit) and (2) the rationale for selecting it if another system can also provide its categories of data points.

C. Which data feeder is the site tiine determining feeder? This should be the feeder which is providing the majority of the data points.

11 - 7 NUlll:.G-1394, lley.1

IV. Data Feeder Information Note: A new Section IV must be filled out for each feeder system selected.

General Questions I.

Identification of Data Feeder a.

What is the name in local parlance given to this data feeder (e.g., Emergency Response Information System)? Please give both the acronym and the words forming it, k

b.

Is this the site time determining feeder?

1 1

c.

Ilow often will this feeder transmit an update set to the !!RDS (in seconds)?

2.

llarthsare/Sof tware Emironment a.

Identity the manufacturer and model number of the data feeder hardware.

)

b.

Identify the operating system.

What method of timekeeping is implemented on this feeder sy. stem (Daylight Savings, c.

Standard, Greenwich)?

d.

In what time sone is this feeder heated?

N U lt l 'G - Du4, It ev.1 It -s

I

?

3.

1)ata Continunication Details Can this data feeder provide asyncluonous serial data conununication (RS-232-C) a.

with full modem control?

b.

Will this feeder transmit in ASCil or lillCDIC?

e.

Can this feeder transmit at a serial baud rate of 2400 bps? If not, at what baud rate can it transmit?

d.

Does the operating 3,ystem support XON/XOFF flow control?

1.

Are any probleins foreseen with the NRC using XON/XOl F to control the trans-mission of data?

If it is not feasible to :econfigure a serial port for the liRDS linkup (i.e., change the c.

baud rate, parity, etc.), please explain why.

f.

Do any ports currently exist for the liRDS linkup?

1.

If not,is it possible to add additional ports?

Il t NURI:G-1394, Rev.1

i I

l

)

l 4

1 1

l; 2.

If yes, will the port be used solely by the ERDS or shared with other non-emergency tiene users? Give details.

i j

4.

1)ata l' ceder Phpical Emironment and Managernent a.

Where is the data feeder kicated in terms of the TSC, liOF, and control room?

b.

Is the data feeder protected from loss of supply of electricity?

4 c.

Is there a human operator for this data feeder?

4 l

i i

i I

s L

If so, how many hours a day is the feeder attended?

1 1

i i

I ta l

l l

i I

l I

=

I i

f, NUlilIG-tN4. Itev.1 -

11 - 1 0 mo n e -

-ee n--, - -

_www,.,e_ m me a m-w m, wen e-

-.. wme. re-w wwm w-n-ww e w p a m-- cw es w e., e m -w ym wemm w '

APPENDIX C DATA POINT LillRARY

Al'PENDIX C DATA l'OINT 1.IllRARY

'the Data Point Library is a site-specific database residing on the EllDS computer which ex-pands upon the basic information in a typical data point dictionary,The data being displayed at the NitC's Operations Center for the EllDS parameter will be the same as the plant's Emer.

gency itesponse Team's data.That is,it will have the same value, timestamp, and be in the same engineering units. 'lhis requires that the Operations Center personnel adjust their thinking to accommodate the plant, functioning in terms of the plant's unique design and conununicating with the plant's flesponse Team in the latter's unique engineering and operational" language",

in order to do this, the Operations Center personnel need information which relates the data both to the plant's design and to the manner in w hich the plant's team utilizes and reacts to the data.

i

'the types of information contained in the Data Po:nt Library are the data point identifier, de-scription, engineering units, range, alarms and/or technical specification limits and engineering system data. There will be anc record in the plant's Data Point Library for each data point the plant will be sending to the EllDS.

Ilecause the points selected for transmission to the EllDS are indicative of plant " health" and are associated with Cr itical Safety Functions, they are the indicators the plant's itesponse Team uses to determine the proper actions to take to mitigate an incident. Where required and useful, the Data Point 1.ibraiy will present textual information to the Operations Center user to provide information supplementing the point's value which will be useful in understar.cHng how the plant team inter prets the data. For instance, associated with a transmitted data point represent-ing the reactor vessel kvel, the Data Point Library should contain the physical zero referente point, conversion factor for the height above the top of active fuel, type of detectors, effects of t unning s cactor coolant pumps, effects of cold calibration, effects of elevated containment tem-pelature, etc. Associated with a reactor water storage tank level transmitted a: a percentage should be the capacity of that tank in gallons, numbet of reactor water storage tanks at the plant site. veio reference point, conversion factor from percent to gallons, etc.

The Data Point I.ibrary will be particularly useful to the Operations Center user when evaluat-ing the plant's action in piedicting of f site radioactive releases. Associated with an effluent gaseous telease data point expressed in CPM, the Data Point Library lleference Sheet should indicate the assumptions regar dingisotopic mit the entrent calibration factors of detectors,the discharge point or points for monitored releases, expected stack flow rates under various fan combinations, and any default values used by the plant team in their calculations.

Two examples of typical Data Point Library entries are included. 'lhe first is an example for a llWit and the second is an example form PWit.

c-t NUllEG-1394, llev.1

llWit DATA l'OlNT 1,1liitAltY 11EltEllENCE lill.E Date:

06/05/S9

(

lleactor Urut:

XYZ Data 1 eeder:

N/A NitC liltDS l'arameter:

CSTlxvel l'oint ID.

C345ZO4 Plant Spt e l'oint Dese.:

CS TNK 1A INL Generic /Cond Dese.:

Condensate Storage Tank A Level Analog / Digital:

A lingr Units / Dig States:

?b i

lingr Units Conversion:

Each 19h = 1692 Gallons Minimum Instr llange:

0 Maximum lustr llange:

100 Zero l'oint

Reference:

SEALEV iteference l'oint Notes:

At O';b 245.lWK1 Gals itemain in Tank I'ItOC or Sl!NS:

l' i

Number of Sensors:

2 Ilow I'roecssed:

Average Sensor 1 ocations:

245,000 Gal Above Tank llottom I

Alarm / Trip Set l'oints:

Low Level At 120b NI Detector l'ower Supply Cut of f l'ower Ixvel:

N/A NI Detector l'ower Supply Turn-on l'ower Level:

N/A Instrument Failure Mode:

Low Temperature Compensation l'or DP Transmitters:

N/A I evel iteference 1 eg:

N/A Unique System Dese.:

This averaged sensor reading is for the normally used volume of the tank.The remaining 245AK)0 gallons are monitored by two discrete alarms at 150jKX) and 50j100 gallons total remaining tank contents. Total tank volume is 414.200 gallons.

NOTE:

A second identical tank normally dedicated to XYZ Unit I is available for cross connecting to this tank at the bottom (ECCS) suction line.

N UllEG-1391. Itev,1 C-2

l' Wit DATA l'OINT l.IllitAltY llElEllENCE lll.E Date:

06/05/89 lleactor Unit:

AllC I)ata 1 ecdct:

littlS NitC liRDS Parameter:

AX I;D 1;l.1/A l'oint ID:

A1105A j

l'lant Spee l'oint Dese.:

Al;W 1; low SG 11 hiTit l

Generic /Cond Dese.:

AliW 110w SG 11 l'irn lilee Al;W Pump Analog /l)igital:

A lingr Units / Dig States:

Gl'M lingr Units Conversmn:

N/A hiinimtun Instr llange:

0 Masimum Instr Range:

500 Zero l'oint iteletence:

N/A lieference Point Notes:

N/A PitOC or Sl!NS:

S Number of Sensors:

1 Ilow I'rocessed:

N/A Sensor locations:

On 1ine To SG 11 Outside Containment Alaim/I' rip Set l'oints:

liigh llow At 500 Gl'Al NI Detector l'ower Supply Cut-olf l'ower 1 evel:

N/A N1 I)etector Power Supply Turn-on Power 1.evel:

N/A instrument 1 ailure Mode:

low Temperatute Compensation 1;or DP Transmitters:

N/A I evel liefer ence i.eg:

N/A Unique System 1)esec There are one electiic and two turbine-diiven Al:W pumps. The electric pump has dedicated discharge lines to each SG. 'lhe 110w element for this point represents the last sensor prior to the line entering containment. The two turbine-diiven pumps use separate piping to the SGs.

Maximum rated flow for this pump is 450 GPM.

Shutoff head is 130 PSIG.

n3 NUlll!G-1394, key. I

DATA l'OINT I,IllitAltY llEFEllENCE Fil.E I) ate:

/

/

Itcactor Unit:

1 Data Feeder.

NitC lillDS Pararneter:

l'oint ID:

Plant Spec l'oint Dese.:

Generie/Cond Dese.:

i Analog / Digital:

lingr Units / Dig States:

linpr Units Conversion:

1 hiinimum lustr Itange:

hiasimum lustr Itange:

Zero l'oint iteference:

Iteference l'oint Notes:

l'ilOC or SliNS:

Number of Sensors:

llow Processed:

St nsor locations:

{

Alarmft rip Set l'oints:

NI Detector l'ower Supply Cut off l'<mer i evel:

NI Detector Power Supply Turn-on l'ower i evel:

Instrument Failure hiode:

Temperature Compensation For Di' Transmitters:

1 evel lieference i.eg:

Unique System Dese.:

NUltEG-13%1. Itev.1 C-4

t APPENDIX D DATA POINT LillitARY REFEllENCE FILE DEFINITIONS

Al'I'ENI)lX 1) 1)ATA l'OINT I,IllitAltY ltEl?ERENCE lilLE 1)EltlNITIONS Ilate:

The date that this form is filled out or modified. (liight characters) lleactor linit:

'the nuclear p(mer plant name and abb;eviation from the enclosed list of sites. ('ihree chaiacters) llata l'eeder:

If there is mote than one data feeder for your system,en-ter the acronym for the data feeder from which the point comes. If there is only one data feeder, enter "N/A" in this field. (Ten characters)

NitC l:ltl)S l'arameter:

One of the parameters from the enclo3cd ilWit or l'Wil parameter list. A single value should be tiansmitted for each parameter for each loop. If not on the list, insert "Not 1 isted" or "NI.". (Twelve charactets)

Point II):

Alphanumeric point desciiption used to label the point during transmission. (Tweh e characters)

Plant Specific l'oint liestription:

1.icensee computer point description for the transmitted point. (Forty characters).

Generic Or Condensed Parameter description Irom the enclosed list of points liestription:

for a ItWil or PWit. If not on the list, condense the plant specific peint descripiion.(Thirty-two characters)

Analog!!)igital:

"A"if the signal is analog or numerical or "l)"if the sig-nal is off/on. (One charactei) 1:ngineering I! nits or lingineering units used by the licensee for display on I)igital States:

licensee output devices Use the engineering units ab-breviations liom the enclosed list when possible. When specifying piessure, use " PSI A" or "PSIG" rather than "l'Sl" lit digital signals, give the "OFl " and "ON" state descriptors. (Twelve characteis) l'ngineering Units Comersion:

Notes about any special features of the A/D conversion and scaling. (Forty characters)

Minimum Imtrument Itange:

lingineering units value below which data cannot go (bottom-of-scale valut'). (Ten characteis)

Masimum lustrument llange:

lingineering units value above which data cannot go(top of-scale value). (Ten characters)

Zero iteference Point:

Zero point of engineering units scale, used primarily for levels or heights. Use the 7ero reference point abbrevia-tions from the enclosed list when possible.

(Six characters) 1)-1 NURIE1394, Rev. I

{

lieference Point Notes:

Notes about the reference point or other important and special features of the parameter,(Forty characters)

PitOC or SENS:

Is the point formed by processing more than one signal, or is the source a single sensor ("P" or "S")?

(One character)

Number of Sensors:

The number of signals ptocessed in a full calculation as.

suming no bypassed or inoperative sensors (Three chrracters) l llow Processed:

Th. oroccaing algorithm (sum, average, weighted av.

crage, highest, lowest, or a short de.seription).

(Forty characters)

Sensor locations:

Description of thelocation(s)of theinstrument(s)used.

(Forty characters)

Alarm or Trip Setpoints:

The most important setpoints for the parameter, State whether the limit is high or low. (Forty characters)

NI Detector Power Supply The power level at which the power supply for the Ni Cut off Power 1,escl:

detector switches off. (Fifteen characters)

Ni lietector Power Supply The power level at which the power supply for the NI Turn on Power f.evel:

detector switches on. (Fifteen characters)

Instrument Failure Mode:

The mode in which this instrument fails. Possible an-swers are 111011, MEDIUM,or LOW,if available, pro-vide the numerie value at which the instrument fails.

(Thirty characters)

Temperature Compen.,ation For This question pertains to differential pressure trans.

DP Transmitters:

mitters. Possible answers are "YES" or "NO"("Y" or "N"). If the answer is "NO", please attach a copy of the cor rection curve. (One character)

I,es el iteference I.cg:

The type of level measurement (dry or wet) used on the level reference leg. (Three characters)

Unique System

Description:

Additional important information which will assist the NRC Operations Center personnel in understanding how the plant team interprets the data. (600 characters)

NURl!G-1344, Rev.1 D-2

c

=

APPENDIX E CRITICAL SAFETY FUNCTION PARAMETERS

Critical Safety Function l'arameters For lloiling Water Reactors Iteactisity Control Parameter Description Typical Units Ni l'OWEll ItNG Nuclear lustruments Power Itange N1 INTlill ItNG Nuclear Instruments. Intermediate llange Ah1P NI SOUltC ltNG Nuclear Instruments, Source llange C/SEC CollE COOLING lli!AC VES I EV lleactor Vessel Water Level IN h1AIN FD FLOW Feedwater Flow into the Ileactor System ItCIC Fl.OW lteactor Core isolation Cooling Flow GPM llCS INTEGill'lY llCS PilliSSUllE lleactor Coolant System Pressure PSIG llPCI FI OW liigh Pressure Coolant injection Flow GPhi LPCI FI OW I ow Pressure Coolant. injection Flow GPhi Clt SPitAY FL Core Spray Cooling System Flow GPhi DW FD SMP 1.V Drywell Floor Drain Sump Level IN ItADIOACTIVITY CONTitol, EFF GAS IlAD lladioactivity of lleleased Gasses NIC1/Illt liFF 1.10 IIAD lladioactivity of lleleased Liquids h1Cl/Illt CND AlliitAD Condenser Air Ejector Itadioactivity C/ MIN DW llAD Itadiation I evel in the Drywell 11/1111 MN STliAh! IIAl)

Itadiation Level of the Main Steam Line Mit/illt CONTAINNIEN~I CONDITIONS DW PIlliSS Drywell Pressure PSIG DW TEMI' Drywell Temperature F

S P 'lliM l' Suppression Pool Temperature F

SP LEVEL Suppression Pool Water Level IN I12 CONC Drywell or Torus llydrogen Concentration O2 CONC Drywell or Torus Oxygen Concentration G

N11SCEl.LANEOUS PAllAMETEltS CST LEVEL Condensate Storage Tank Level WIND SPEED Wind Speed at the lleactor Site MPil WIND Dilt Wind Direction at the lleactor Site DEG stall CLASS Air Stability at the Ileactor Site F-1 NUllEG-D94. Itev. I

Critical Safety Function Paramete s For Pressurized Water Reactors Reactisity Control Parameter Description Typical Units 4

N1 POWER RNG Nuclear Instruments, Power Range NI INTER RNG Nuclear Instruments, Intermediate Range Ah1P NI SOURC RNG Nuclear Instruments, Source Range C/SEC CORE COOLING REAC VES LEV Reactor Vessel Water Level IN Tlih1P CORE I!X liighest Temperature at the Core Exit F

SUB h1 ARGIN Saturation Temperature-Ilighest CET F

CORl! FLOW Total Reactor Coolant Flow N1LB/IIR STEANI GENERATORS SG LliVEL 1/A Steam Generator 1 (or A) Water lxvel SG LEVEL 2/B Steam Generator 2 (or B) Water lxvel SG LEVliL 3/C Steam Generator 3 (or C) Water lxvel G

SG LEVEL 4/D Steam Generator 4 (or D) Water Level SG PRESS 1/A Steam Generator 1(or A) Pressure PSIG SG PRESS 2/B Steam Generator 2 (or B) Pressure PSIG SG PRESS 3/C Steam Generator 3 (or C) Pressure PSIG SG PRESS 4/D Steam Generator 4 (or D) Pressure PSIG h1N FD FL 1/A Stm Gen 1 (or A) hiain Feedwater Flow LBht/HR A1N FD FL 2/B Stm Gen 2 (or 11) hiain Feedwater Flow LUN1/llR h1N FD FL 3/C Stm Gen 3 (or C) hiain Fcedwater Flow LBht/IIR hlN FD FL 4/D Stm Gen 4 (or D) hiain Feedwater Flow LBht/flR AX FD FL 1/A Stm Gen 1(or A) Auxiliary FW Flow GPhi AX FD FL 2/B Stm Gen 2 (or 11) Auxiliary FW Flow GPhi AX FD FL 3/C Stm Gen 3 (or C) Auxiliary FW Flow GPhi AX FD FL 4/D Stm Gen 4 (or D) Auxiliary FW Flow GPM llL TEN 1P 1/A Sti. Den 1 (or A) Inlet Temperature F

llL TEh1P 2/B Stm Gen 2 (or B) Inlet Temperature F

llL TEh1P 3/C Stm Gen 3 (or C) Inlet Temperature F

llL TEh1P 4/D Stm Gen 4 (or D) Inlet Temperature F

CL Tiih1P 1/A Stm Gen 1 (or A) Outlet Temperature F

CL TEN 1P 2/B Stm Gen 2 (or B) Outlet Tempeiature F

CL TEN 1P 3/C Stm Gen 3 (or C) Outlet Temperature F

CL TEN 1P 4/D Stm Gen 4 (or D) Outlet Temperature F

NUREG-1394, Rev.1 E-2

/

Critical Safety Function Parameters For Pressurized Water Reactors (Cont'd)

Reactisity Control Parameter Description Typical Units

=

RCS INTEGRITY RCS PRESSURE Reactor Coolant System Pressure PSIG PRZR 1.EVEL Primary System Pressurizer Level 9b RCS CilG/h1U Primary System Charging or hiakeup Flow GPhi llP St FLOW liigh Pressure Safety injection Flow GPhi 1.P SI Fl.O W low Pressure Safety Injection Flow GPhi CTh1NT SN1P NR Containmer.t Sump Narrow Range Incl IN CThtNT Sh1P WR Containment Sump Wide Range Level IN RADIOACTIVITY CONTROL EFF GAS RAD Radioactivity of Released Gasses h1C1/HR EFF LIO RAD Radioactivity of Released Liquids htCl/HR COND A/E RAD Condenser Air Ejector Radioactivity C/h11N CNTN1NT RAD Radiation Levelin the Containment R/HR RCS LTDN RAD Rad Level of the RCS Letdown Line C/SEC N1 AIN SL 1/A Stm Gen 1 (or A) Steam Line Rad Level h1R/IIR h1 AIN SL 2/B Stm Gen 2 (or B) Steam Line Rad Level N1R/HR N1 AIN SL 3/C Stm Gen 3 (or C) Steam Line Rad Level h1R/llR h1 AIN SL 4/D Stm Gen 4 (or D) Steam Line Rad Level h1R/IIR SG llD RAD l A Stm Gen 1 (or A) Blowdown Rad I.evel h1R/llR SG BD RAD 2B Stm Gen 2 (or B) Blowdown Rad Level h1R/HR SG BD RAD 3C Stm Gen 3 (or C) Blowdown Rad Level h1R/HR SG BD RAD 4D Stm Gen 4 (or D) Blowdown Rad 1.evel h1R/IIR CONTAINhlENT CONDITIONS CThtNT PRESS Containment Pressure PSIG CTNINT TEh!P Containment Temperature F

112 CONC Containment flydrogen Concentration h11SCELLANEOUS l'ARAh1ETERS BWST LEVEL Borated Water Storage Tank Level WIND SPEED Wind Speed at the Reactor Site h1Pil WIND DIR Wind Direction at the Reactor Site DEG STAB CLASS Air Stability at the Reactor Site E-3 N U REG-1394. Rev.1

APPENDIX F ENGINEERING UNITS CODING SCHEME

I APPENDIX F ENGINEERING UNITS CODING SCllEME Pounds per square inch gauge PSIG

=

Pounds per square inch absolute PSIA

=

Inches of Water Pressure INil O

=

2 Percent

=

INCllES FEET Feet and inches 1%1N

=

Feet and decimal feet liTDEC

=

Gallons GAL

=

Pounds or pounds mass Lil

=

Gallons per minute GPhi

=

Thousands of gallons per minute KGPhi

=

Pounds per hour Lit /llR

=

Thousands of pounds per hour KLII/IIR

=

hiillions of pounds per hour N1LB/IIR

=

Counts per minute CPhi

=

Counts per second CPS

=

Ah1PS hiilliamps N1Ah1PS

=

hiicroamps gAh1PS

=

Degrees Fahrenheit DEGF

=

Degrees Centigrade DEGC

=

hiillirem per hour h1R/lIR

=

Rem per hour R/IIR

=

Curies per CC C1/CC

=

Curies per h1L Cl/h!L

=

hiicrocuries per CC gCl/CC

=

N1icrocuries per htL C1/htL

=

Curies per second CI/S

=

hiicrocuries per second Cl/S

=

Degrees true (for wind direction from)

DEGFR

=

Degrees true (for wind direction to)

DEGTO

=

Degrees Fahrenheit per foot DF/IT

=

Degrees Centigrade per meter DC/h1

=

Degrees Centigrade per 100 meters DC/Ilhi

=

Degrees Fahrenheit per 100 feet DF/IIFT

=

Stability class in form of A - G STAllA

=

Stability class in form of integer, where A =- 1,11 = 2 STABI

=

hiiles per hour N1PH

=

hieters per second A1/S

=

I l

l'1 N UIWG-1394, llev.1

APPENDIX G ZERO REFERENCE CODING SCHEME

1 API'ENDIX G ZEllO ltEFEllENCE CODING SCilEME

'this field applies to levels and heights only. Leave it blank for temperatures, pressure, and flows. Give the physical point represented by the number 7ero for the parameter from the choices below.

Top of active fuel Tali

=

Upper head UPilEAD

=

1.ower head 1.WilEAD

=

Moisture separator skirt MSSKitT

=

Top of pressurizer heater bank TOPilTR

=

Surge line penetration SUltGE

=

At the spray nozzle SPilAY

=

Top of S/GU tubes UTUllES

=

At S/G tube :,heet TU13SIIT

=

llottom of tank sump (e.g., CST)

TNKilOT

=

Refereace too complex for database entry COMPL i

=

Containment fhor CNTFl.K

=

Mean sea level SEAL.EV

=

G-1 NUllEG-1394, llev. I

APPENDIX H CODING SCIIEME FOR ~ UNIT NAME AND UNIT ID

-____-.m.______

m. _. -. ~ _ - _ _ _. _

I APPENDIX 11 CODING SCllEME FOR UNIT NAME AND UNIT ID ARKANSAS NUCLEAR ONE-1 ANI GRAND GUI.F-1 001 QUAD CITIES-1.

. OC1 ARKANSAS NUC1JIAR ONE-2. AN2 II ATCll-1.

IITI QUAD CITIES-2.

. OC2 ilEAVER VALIEY-1.

IIV1 IINTCli-2.

11 T2 RIVER BEND-1

. RBI IIEAVER VALLEY-2.

IIV2 IlOPE CREEK-1.

IICl ROBINSON-2.

. RO2 IlElj.EFONTE-1 IlEl INDIAN POINT-2..

IP2 SAIEht-1.

.. sal llEllEl ONI E-2

!!E2 INDIAN POINT-3.

IP3 S ALEht-2.

..SA2 IIRAIDWOOD-1 IIR 1 J Ah1ES A FIT 7J'ATRICK FZ1 SAN ONOFRE-1..

. sol IIRAIDWOOD-2 llR2 KEWAUNEE.

KW1 SAN ONOFRE-2..

.SO2 IIROWNS FERRY-1 BF1 1 ASAIJE COUNTY-1.

131 SAN ONOFRE-3.

.SO3 ilROWNS FERRY-2.

IlF2 1 ASAIJ E COUNTY-2.

IS2 SEABROOK-1.

. SBl 13ROWNS FERRY-3.

HF3 IJhiERICK-1 l.hl1 SEQUOYAll-1

.SE1 IIR UNSWICK-1 UKl Lih1ERICK-2.

Lht2 SEQUOYAll-2

.SE2 IIRUNSWICK-2 IIK2 h1AINE YANKEE.

htY1 S (EARON llARRIS-1

. IIR1 IlYRON - 1.

IlY i h1CGlJIRE-1 h1C1 SORTil TEXAS PROJECF-1

. STI ilY RON-2.

IlY2 htCG UIRE-2 htC2 SOtfril TEXAS PROJECT-2

.ST2 Call AWAY-1 CW1 hill.lSTONE-1 hts 1 ST. LUCIE-1.

. SL1 CAINERT Cl3FFS-1 CCI hillJ STONE-2 hts 2 ST. LUCIE-2.

. SL2 CAINERT ClJFFS-2 CC2 hill.lSTONE-3 hts 3 SURRY-1

.. SUI CATAWilA-1 CTI htONTICE!J.O h101 SURRY-2

' SU2 CATAWilA-2 Cr2 NINE hillE POINT-1

. Nht!

SUSQUEllANNA-1

'SQl C1.IN'l ON-1.

CL1 NINE hilLE POINT-2.

Nhi2 SO2 SUSQUEllANNA d' ND-1 '

COhtANC11E PEAK-1 CPI NORTil ANNA-1.

NAl TilREE hillE Isi

' Thil COh1ANCllE PEAK-2 CP2 NORTil ANN A-2.

NA2

.FROJAN

.I.R 1 CONNEC1ICUT YANKEE IINI OCONEE-1 OCl TURKEY POINT-3

. TP3 COOK-1 CK1 OCONEE-2 OC2 TURKEY POINT-4 FP4 COOK-2 CK2 OCONEE-3 OC3 V. C. SUhthtER.

. VS1 COOPER COI OYSTER CREEK.

OY1 CRYSTAL RIVEl(-3.

CR3 PALISADES.

pal VERhtONT YANKEE.

, VY1 DAVIS IlESSE-1.

Dill PALO VERDE-1.

PV1 VOGTIE-1.

., VOI DIAllLO CANYON-1 DCI pal O VERDE-2.

PV2 VOOTLU-2.

. VO2 DIABI O CANYON-2.

DC2 pal.O VERDE-3.

PV3 WNTERFORD-3.

. WF3 DRESDEN-2 DN2 PEACil 130TTOht-2 l'E2 WATTS IlAR-1

. Will DRESDEN-3 DN3 PEACII IlOTIOht-3 PE3 WNITS BAR-2

, WB2 DUANE ARNOLD DAl PERRY-1 PY1 WN P-2

. WP2 FARlEY-1.

FAI Pil.G Rlht-1 l'G 1 WOLF CREEK.

. WCl FARI.EY-2.

FA2 POINT BEACil-1.

Pill YANKEE-ROWE

. YR1 I ER hll-2 FE2 POINT llEACll-2.

Pil2 ZION-1

. 7141 FORT CA1 J10UN-1 FCI PRAIRIE ISl AND-1 PIl ZION-2

.ZN2 GINNA Gil PR AIRIE IST AND-2.

P12 11-1 NU R EG-1394. Rev.1 -

l APPENDIX 1 COMPUTER POINT SELECTION

APPENDIX I COMPUTER POINT SELECTION The main theme of the computer point selection process is to identify the minimum set of com-puter points, available on the fewest (preferably one) number of feeders from a site, which fully describe each of the parameters on the ERDS Parameter List.

When multiple computer points exist to describe a certain parameter, there is usually one point or a small subset of points which meet the following desirability criteria:

For fluids systems (e.g., IIPCI, Huilding Ventilation, Main Feedwater, etc.) the points rep-resenting the farthest location downstream in the system are most desirable. Examples:

If the ventilation system exhausts from all buildings in the power block converge and ascend up a single plant vent stack, then only the effluent process radiation monitors on the plant stack need be described under " gaseous effluent" versus describing the individual effluent monitors which may exist for each of the exhaust lines which converge.

If an injection or feedwater system has a set of points available which include flows measured at the pump discharges, at a combined header and at the point in the system just prior to injection into the loops or steam generators, then the points which should be selected as potential ERDS feeds are the furthest downstream points (flow meas-ured just prior to injection into loops or steam generators).

Computer points which have undergone the maximum amount of range checking and other data point validation schemes should be selected. We are aware that many utilities are in the process of upgrading computer system validation techniques and that what exists now may be replaced at some future date.

Computer points representing the widest expected range of the parameter should be se-lected. For example: If there is a choice of computer points for " Containment Pressure" with one representing the range -5 to + 5 PSIG and another representing the range -5 to

+ 100 PSIG, the wide-range -5 to + 100 PSIG computer point should be selected; even though its accuracy may not be as great r. ear the normally expected pressure of-1 to + 1 PSIO.

The point composed of the maximum number ofinputs should be used.The desirable point may be composed (processed)within the feeder computer or may be composed by a sepa-j rate microprocessor outside the feeder as in the case of PWR Reactor Vessel Level Indica-philosophy of selecting the most composed points should not be applied in the case of pa-tion (RVLIS). Subcooling Margin Monitors (SMM) and meteorological tower systems.The rac..eters associated with PWR coolant ioops(e.g., T-hot T-cold, S/G Pressure, SIG Level.

Main Feedwater Flow, etc.) to the extent of selecting points such as " Average T-hot", be-cause loop-specific parameters are preferable for use in coolant-loop-specific accidents such as Steam Generator Tube Breaks. Composed points such as " Average T-hot Loop 1",

" Average T-hot Loop 2, etc., should be selected.

t-1 NUREG-1394. Rev.1

APPENDIX J FsRDS QUESTIO'NS AND ANSWERS

APPENDIX J ERDS QUESTIONS AND ANSWERS 1.

Will the implementation of the ERDS affect the NRC response role or the way that role is fulfilled?

No. De NRC response role was defined and approved by the Commission and would not change due to the ERDS. Current response activities, including discussions with the licen-see, will be done more quickly and e ^iciently due to ERDS implementation but would not materially change.

2.

What is the current program schedule?

The NRC ERDS was d : livered to the Operations Center in April 1990. Following opera-tional testing, ERDS was placed in service in June 1990. There are currently thirteen reac-tor units capable of transmitting data to ERDS. To date 27 licensees comprising 67 reactor units have volunteered to implement ERDS. Implementation at all units is scheduled to be completed by the end of 1992.

3.

Will the implementation of the ERDS require significant equipment modification or addition by licensecs?

The only equipment requirements are for the hardware that is needed to provide a data stream for each unit from the current licensee equipment that processes the requested data on site. For those licensees where no new hardware is required, the costs per reactor unit are estimated in the range of $20K to $50K. This estimate includes labor costs associated with software development, design change notice documentation, testing, and procedure development. Approximately 5 to 10 percent of the licensee's systems are running at close to 100 percent processing capacity in the post trip or incident environment, and approxi-mately 10 to 15 percent of the licensee systems are hardware limited (e.g., no available out-put port for an ERDS connection). At the upper end of the cost spectrum, the ERDS feasi-bility study revealed that two plant sites would require additional computer equipment to provide the necessary ERDS feed. The hardware costs were estimated at $150K plus licen-see staff time required to set up a custom system development effort with the appropriate contractor.

4.

Will the ERDS be considered safety grade or require redundant equipment?

No. The ERDS feed will be as reliable as the current licensee equipment providing data to the licensee's own TSC and EOF. The addition of new plant instrumentation or computer data points to provide ERDS data will not be required.

5.

Will the current datn list be expanded?

No. The issue has been well studied since the Nuclear Data Link was originally proposed after TMI.The development of the data list followed our determination of our role in an emergency and provides the information we need to perform that role. The data list is in-tended to be generic in nature.There is a limited amount of space in each unit's data base to accommodate plant specific data points which are not on the data list, but would be useful I

J-l NURl!G-1394, Rev. I

l in assessing plant conditions. Experience from the implementation program to date has indicated that there are parameters that licensees would like to send as a part of the ERDS data stream. Licensee recommendations for additional data points will be considered for addition to individual unit data bases. Needed data not transmitted over ERDS will still be 3

passed over the ENS.

6.

Must the El(DS be used to transmit drill data?

That is not a design requirement. For those system configurations which only allow the transmission of real data, no modification will be expected. Ilowever,if the licensee system is used for drills and can provide the transmission of the drill data, we would like to use the capability for our drill participation.

7.

Will the ERDS be an 1,C0 of Tech Spee item?

No.

8.

Ilow soon does the NitC expect the system to be initiated after an Alert declaration?

The ERDS should be initiated as soon as possible following the declaration of an Alert or higher emergency classification, not to exceed one hour from the time of the declaration.

9 Will the transmission of data point values for times prior to the time of the ERDS activation be required?

No. Only the data values from the time of the link initiation will be required over the ERDS.

Information on initiating conditions and plant status will be provided over the verbal com-munication line as necessary,

10. Once the ERDS is implemented, will continuous manning of the ENS (Red Phone) still be required?

Yes. The ERDS will not eliminate the need for verbal transmission ofinformation such as licensee actions, recommended protective actions, and supplemental event specific data not provided by ERDS. Emphasis will be given to producing no new impact on Control Room personnel due to the transmission of data over the ERDS.

I1. Will the ERDS data be prmided to State authorities?

Although the NRC is not soliciting or recommending State participation in the ERDS pro-gram, one provision of the system design is user ports for States within the 10 mile plume exposure EPZ.This provision was made to reduce the likelihood of different data being provided to the NRC and a State because of differing data sets where the State has decided to collect data.This provision is not expected to affect States that already have a ciata col-lection system. If a State expresses a desire to participate in the ERDS program, the NRC will provide ERDS data to that State under a specific Memorandum of Understanding.

The purpose of this Memorandum of Understanding would be to specify communication protocols for clarification of ERDS data and data security requirements.The NRC would provide those States whh contractor developed softwaie and make one output port avail-able to the State from the NRC Operations Center.1he States would have to obtain com-patible PC hardware and licensed software used in the ERDS system to receive data. The NURIR1394, Rev. I J-2

Y l

specifications for a State ERDS workstation is attached at the er,d of the Questials and l

Answers for your information. These provisions will ensure that all parties involved are using the same data base for their analysis. Any request made by a state to set up the capa-3 bility to receive ERDS data will be discussed with the utility.

12. Will the NRC require a periodic test of the ERDS, and if so how frequently?

The NRC does expect that periodic testing will be required to ensure system operability.

Curiently we expect that testing will be donc quarterly. Should system reliability permit, the frequency of testing may be reduced. Testing of a State link portion of the system will be done with the NRC. Therefore, no licensee participation will be required for this test.

13. Will participation in the ERDS program remain voluntary?

d The NRC has initiated rulemaking to require the implementation of ERDS at all nuclear power plants. It is anticipated that the provisions of the proposed rule would be the same as those of the voluntary implementation program currently in effect.

14. What will be the boundary of system maintenance responsibility?

The NRC will be responsible for maintenance of all parts of the ERDS system installed starting at the input port of the first ERDS-specific piece of hardware (e.g., modem for single feeder plants and multiplexer for multi-feeder plants.)

15. Will the NRC develop a generie EROS interface for use by licensees?

The ERDS implementation contractor (NUS/El Division) will develop a UNIX based PC application which will provide an acceptable interface with ERDS. If a licensee desires to utilize this interface, they would be required to procure the PC and provide the data feed to the PC which would then handle all ERDS related communication functions. As is the case with ERDS modems,it would be expected that the PC would be powered from a power source that has the same reliability as that of the computer used to provide the data. Licen-sees desiring to explore the possibility of utilizing this generic interface program should contact the NRC ERDS project manager.The ERDS interface software,with source code, will be provided to licensees at no cost by the NRC.

i i

l t

l J-3 NURIG 13W. Rev.1

,_.~

s

.me,..

A

..A.T WORKSTATION DESCRIPTION FOR Tile STATE'S INTERFACE TO Tile NRC'S EMERGENCY RESPONSE DATA SYSTEM liardware 1.

Compaq 386/25 with:

40 Mllyte liard Disk (Minimum) 640K Memory (Minimum) 51/4 inch and/or 31/2 inch floppy drive EGA/VGA Card (640 x 480 llesolution)

Serial Communications Port Parallel Printer Port 2.

EGA Monitor (640 X 480 ltesolution) 3.

Mouse or Trackball with Card and Windows Driver 4.

Desk Top Printer 5.

Codex 2235 Modem or equivalent Software 6.

Microsoft Windows 286 7.

Winterm 8820 8.

DOS 33 NOTE: Items 2,3. 5,6. 7, and 8 are required components. A functional equivalent for item I is acceptable as long as the required items are supported. Item 4 is optional.

i d

i 4

i NUltliG-1394, llev. I J-4 r

, w

.e,-

'--r-t =- - -

'a" - ' - '*' -

' " " **"'"C

NRC FORM 335 U S. NUCLEAR REGJLATOHY COMMISSION L HLPORT NUMBER

( Assigned t'.y NRC Add Vol..

(2 -69 )

Supp., Rev, and Addendum Num-F4HCM 1102, 3m 22 BIBLIOGRAPHIC DATA SHEET

• * ' * - d M NUREG-1394 (se..nstruccons on 1% rev.rs.)

Rev.1 2 fill E At40 bubillLE

3. D A T E Ht PDH T PUuuSHL D Emergency Resp (mse Data System (liRDS) Implementation uay,g j

vg n June 1991

4. FIN OR GR ANT NUMBER 6 Av i Hva p )

6 T Y PE OF HLPOH T Regul tory L R. Jolicoeur

7. PtRiOO COVERED pnclusive Dates) 6 Pt HF OHM NG OHGANIZ AT ION - NAML AND ADOHLSS pt NHC, provide Divisson, Othce or Region, U, b. Nuclear Regulatory Commsssion, and maug audi,,ss, a contractor, provide nam..nd mening addr.ss. )

Office for Analysis and Evaluation of Operational Data U.S. Nuclear Regulatory Commission Washington, DC 20555 9 M'UNSOHW4G OHGANil A TION - NAML AND ADDRESS pt NHC, type 'Same as above'; it contractor, provios NRC Division, Ottice or Region.

US Nuctear Regulatory Comrmssion, and mailing address )

Same as alxn c.

10. SuhtLMt.NT AHY NOIL5

11. ADSTFT ACT (200 words or less)

The U.S. Nuclear Regula:ory Commission has begun implementation of the Emergency Response Data System (liRDS) to upgrade its ability to acquire data from nuclear power plants in the event of an emergency at the plant.

IIRDS provides a direct real-time transfer of data from licensee plant computers to the NRC Operations Center.

The system has been designed to be activated by the licensee during an emergency which has been classified at an AlJiRT or higher level. The NRC portion of ERDS will receive the data stream, sort and file the data. The users will include the NRC Operations Center, the NRC Regional Office of the affected plant, and if requested, the States which are within the ten mile EPZ of the site. The currently installed Emergency Notification System will be used to supplement ERDS data.

This report provides the minimum guidance for implementation of ERDS at licensee sites. It is intended to be used for planning implementation under the current voluntary program as well as for providing the minimum standards for implementing the proposed ERDS rule.

12. KEY WORDS/DESCRPTORS (List words or phrases that w40 assist researctwa m locatir'g the report )

13. AVAILABlWTY ST ATEMENT Unlimited

14. SECURITY CLASSIFICATION Emergency Response Data System (ERDS)

(7,,,,,,,,

NRC Operations Center Unclass.fied i

emergency Ghu kepero accident Unclassified

15. NUMBEH OF PAGES 16 F%Ct.

1 NRC FORM 335 (2-69)

l THIS DOCUMENT WAS PRINTED USING RECYCLED PAPER

7 I

UNITED STATES E

I NUCLEAR REGULATORY COMMISSION

,,,, c,e,,,is s emio resu.a m

WASHINGTON, D.C. 20555

• • • • C 9

einwt no o s7 O

OFFICIAL BUSINESS

[

PENALTY FOR PRIVATE USE tyJO 1.. C 5 5 5 1 1 j 5 3 )

m I

V. o t.) p 1ANICJ1c Icyj a,!

U^

T

. b d $ [j,3 1'.y P L I c t.I I r q 3 7

gygg o.

[ t gb f j yI9%

W Cc Sg$g7 l

a b

f.

m M,

0; m

Z,

=

Oz u)

M C>

>H Eax:

C'

?

G 9-Y) h)W H'

3 zl l

l 1

i l

l 4

i E*

e3 m

(

.-