Text

Forwards Update to ERDS Plant Attribute Library,Per 10CFR50, App E,VI,3.b.Update Associated W/Equipment & Software Changes Being Incorporated During Plant Monitoring Computer Upgrade
	ML20098C057
Person / Time
Site:	Waterford
Issue date:	10/05/1995
From:	Burski R; ENTERGY OPERATIONS, INC.
To:	; NRC OFFICE OF INFORMATION RESOURCES MANAGEMENT (IRM)
References
	W3F1-95-0164, W3F1-95-164, NUDOCS 9510060229
	Download: ML20098C057 (13)
	v • d • e

c

= .ENTERGY EilN"""'"

K&sa LA 70066

/ ,.g .

Tel 504 739 6774 R. F. Burski CwcKv.

t Adar Safety ,

V.Wer!ce) 3 !

W3F1-95-0164 )

A4.05 !

PR October 5,1995 U.S. Nuclear Regulatory Commission ATTN: Document Control Desk Washington, D.C. 20555

Subject:

Waterford 3 SES Docket No. 50-382 License No. NPF-38 Emergency Response Data System (ERDS)

Plant Attribute Library Update Gentlemen:

Waterford 3 is hereby submitting (attached) an update to the ERDS Plant Attribute Library (PAL) in accordance with 10CFR50, Appendix E, VI, 3.b.

The update is associated with equipment and software changes being incorporated during the Waterford 3 Plant Monitoring Computer upgrade. The changes are being incorporated during Refuel 7, currently in progress. The attached updated library will be effective at the completion of the refueling outage, which is currently scheduled to occur on November 6, 1995. Waterford 3 personnel will notify the NRC Operations Center by phone when the ERDS is back in service (at the completion of the outage) with the new PAL in effect.

0G00G1

&l 9510060229 951005 l

PDR ADOCK 050003B2 p PDR

.j i

re 'l

- - - $DS Plant Attribute Library Update ]'

W3F1-95-0164~

Page-2 ,

'3 October 5', 1995 ;

If you have,any questions ~ concerning the above, please contact 0.P. Pipkins :

at (504) 739-6707.. I Very truly yours, 4 t

R.F. Burski Director- !

Nuclear Safety

- RFB/0PP/ssf.

Attachment 3 l

cc: L.J. Callan, NRC Region IV C.P. Patel, NRC-NRR

'R.B.~ McGehee J.R. Jolicoeur, NRC-AE0D N.S. Reynolds NRC Resident Inspectors Office .

t i

I c

I

=

t s

i .

]

i i

4 APPENDIX B l

l --

ERDS COMMUNICATIONS DESCRIPTION

! AND SURVEY QUESTIONNAIRE 4

4 i

i I

k

APPENDIX B ERDS COMMUNICATIONS DESCRIPTION AND SURVEY QUESTIONNAIRE ne to!!owing is a questionnaire pertaining to the Nuclear Regulatory Commission's (NRC)

Emergency Response Data System (ERDS). It consists of a senes of quesuons concerning plant I/O points. software protocols, data formats. transmission frequencies. and other plant com-puter specific information to be used 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 communicauon line.

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

In some cases the I/O 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 AppendizJ. 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.

His request is covered by Off!ce of Management and Budget Clearance Number 3150 0150 which expires March 31,1992.ne estimated average butden hourn is 32 person hours per lican-ses response, including staff and management review and preparation of the requested re-sponse. Dese estimated average butden hours pertain only to those identified response related matters and do not include the time for any follow on implaamatariaa Sand comments regard-ing this burden estimate or any other aspect of this collection ofinformation. including sugges-tions tor reducing this burden. to the Records and Reports Management Branch. Division of informsuon Support Services. Office of Information Resources Management. (*.S. Nuclear lleguistorv Commission. Washington. DC 20555: and to the Paperwork Reducuen Project j 0150-0150). Office of Management and Budget. Washington. DC 20503.

4 f

4 i

f i

i l

l l

B-1 NUREG-1394. Rev. I

1. Contacts Note: Please provide name. title. malling address. and phone number.

A. Survey Coordinator (i.e contact for later clarifiestion of questionnaire answers):

Clarence Kimble Engineer Senior P.O. Box B Killona LA 70066 (504) 739-6405 B. Computer Hardware Specialist (s):

Clifton George

- Senior Maintenance Specialist P.O. Box B K111ona, LA 70066 (504) 739-6729 C. Systems Software Specialist (s)-

1 Clarence Kimble , l l

l l

D. Application level Software SWaHMs): .

Clarence Kimble Robert Verderame Engineer II P.O. Box B 4 Killona, LA 70066 (504) 739-6727 J

E. Telephone Systems SWeliet(s);

i Donald St. Germain

'- IT Specialist P.O. Box B Killona, LA 70066 4

(504)739-6241 4

4 i g

NUREG-1394. Rev.1 B-2

< 1 l

1 :

II. ERDS Communications Description l-l A. Hardware i The followmg hardware will be supplied:

- for a single. feeder site:

l Codex 2235 modem or equivalent V.222400 bps. asynchronous. auto. dialing. auto-

! answer. error correcting. using the AT command 4

a

set I' '

- for a multiple feeder site:

I Codex 6015 multiplexer.

! Codex 2264 modem or equivalent V.329600 bps, asynchronous, auto dialing auto-answer. error correctmg, using the AT command set I (for an alternate approach see Appendix A. Item 7) l De modems are intended to be operated in the auto reliable link mode (referred to as MNP ih the modem manuals). Ders are several modem parameters that affect MNP operation. Thess are discussed in the sections of the modem manuals pertaining to MNP. The single feeder mo-dams at the NRC Operations Center are configured for auto reliable link mode, local terminal l- flow control and default break handling.

! B. Software t

i 1. Data Transmission All transmissions. from both the site and the ERDS.will be terminated with a carriage return

( < CR > ). .

l

! a. Site will initiate a link request in ASCH using:

- the three. character site designator.

[

- the word LINK.

4

- local site time and date in the format MM/DD/YY/HitMM:SS and l j

- a < CR > .

o

' If the site does not receive a response from the ERDS within one minute. it should send i

another link request message and continue sending them at one minute intervals. If more than five minutes elapses without a response, site personnel should notify the NRC before disconnecting the line.

l- b. ERDS will respond in ASCII with: ,

l - the three<:baracter site designator.

- the word ACCEPTED or DENIED. and ,

- a<CR>.

if the ERDS responds with the denied message. the site should wait one minute and then send a link request message and continue sending them at one.mmute intervals. If g.) Mf fB e#* ****

h

...c, . _ _ _ _ . .

1

.more than rive m nutes elapses without s response site personnel shout nottrv the

! NRC betore disconnecting the line.

c. When the ERDS is ready to receive data, it will send an initiate message in ASCH

~

using:

I - the three character site designator.

! - the word INTIIATE. and

- a < CR> .

If the ERDS does not send an initiate message within one minute of the accept mes-sage. the site should send the link reconnect message (desenbed in Section II.B.1.f.).

f d. Upon receipt of the initiate message, the plant begins transminion of data at a 15 second rate. The data string consisu of:

! - a header containing the three character site designator and date and time in the

format MM/DD/YY/HItMM: SS.

- the data packet sequenced with point identiSer value, and quality tag.

- a trailer containing the checksum value of the data packet. and a < CR>. -

4 h e. When the site or ERDS wishes to terminate the connection. an ASCH message will be sent containing: #

t

! - the three character site designator.

I -

the word 'IT.RMINATE and

- s<CR>.

1

t. If a site is inadvertently terminated (due to loss of communications or receipt of termi-

nate message) and the incident is still underway, the site should reconnect with the l ERDS by redialing and using the link reconnect message. The link reconnect message

! Should be used any time the phone line is lost atter the receipt of an Accept Message

! (described in Section II.B.1.b). This message is in ASCII and will contain:

(

i

- the three character site designator.

} - the word RECONNECT.

j - local site time and date in the format MM/DD/YY/HH:MM:SS. and i

- s<CR>.

Upon receipt of this message. the ERDS will respond with the accept and initiate mes-l sages as described in Sections !!.B.1.b and ILB.1.c. lf the ERDS responds with a link

deny message (described in Section II.B.1.b). the site should stop trying to reconnect j snd send a link request message (described in Section II.B.1.a). lf the ERDS does not j respond to the site's reconnect request within one minute. the site should send another reconnect request and conunus sending reconnect requests once a minute. If more l j than tive minutes elapses without a response. site personnel should notify the NRC before disconnecting the line. It is the responsibility of the site to monitor the outgoing i

line tor loss of communications. '

i J

Once a physical connection has been established with the NRC. the site should not disconnect the phone line until a TERMINATE message tdescribed in section i

l NUREG-1394. Rev.1 8-4 l 1

!!.B.1.'e) has been transmitted. If problems are encountered in the link recuest se.

quence. do not hang up the line but proceed with the steps outlined above.

g.

If the site will transmit in EBCDIC rather than ASCII. the following applies:

(1) The link request message (defined in II.B.I.a) and the reconnect message (defined in II.B.1.f) must be in ASCII.

(2) All replies sent by the ERDS to the site will be in ASCII.

(3) The terminate message sent by the site may be in EBCDIC or ASCII.

(4) All update sets sent by the site must be in EBCDIC.

2. Data Format The following three delimiters have been identified:

(1) field delimiter (*).

(2) data set delimiter (\). and j (3) carriage return ( < CR > ).

Note

The length of the messages sent by the ERDS (e.g ACCEPTED. DENIED.-

! INITIATE. TERMINATE) are variable and it is recommended that the site so

ware use the data set delimitar as the message delimiter for messages received from the ERDS.

t

a.

! I. ink requests will be in ASCII as described in II.B.1.a. with each field separated by a i field delimiter and the request terminated with a data ses delimiter. For example.

pal' LINK'01/12/89/11:48.50\ < CR > .

i b.

+ The ERDS response will be in ASCU as dercribed in II.B.Lb. with each field sepa-i rated by a field delimiter and the response terminated with a data set delimiter. For example. pal

ACCEPTED \ < CR >.

c.

When the ERDS is ready to receive data it will respond in ASCII as described in II.B.1.c with each field separated by a field delimiter and the res j a data set delimiter. For example. pal

INITIATE \ < CR>. ponse terminated with l d.

Data streams will be in ASCII and will consist of three parts (header. data. and trailer) as described in II.B.1.d. with each field separated by a field delimiter and each of the j three parts separated by a data set delimiter. For example.

, Header: pal *01/12/89/11:50:30\

Data:

B21CP004*-0.1234E+00'3'... (for each parameter)\

Trailer: 0000056000\ < CR>

e.

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

f.

The value may be up to 20 chr.racters in length.

B-5 NUREG-1394. Rev.1 I

, l I

I ., .-

! e. The tollowinc quality tags will be accepted by the ERDS:

1

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

l Off scan =1 Point is currently out of. service.

I e Suspect =2 Value is not bad yet should not be considered good.nis

! quality will occur primarily on composed values when j enough good inputs are present to allow the calculation to be made yet a bad quality on other inputs may make i the result questionable.

Bad =3 Value is not within tolerance for discrest 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.

Operator Entered =5 Value has been manually entered. overriding the dise creet or composed value.

High Alarm =6 Value is in high alana.

1 j Low Alarm =7 Value is in low alarm. l

h. The checksum which accompanies each update set wiu be an integer value calculated 1

, by summing each of the bytes of the transmission, up '.s and including the dataset de- 1 i limiter following the body of the update set (the body of the update set being the por-tion containing the parameter. 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 as required to fill the 10 digit field.The checksum is the sum of the transmitted bytes.

. i. De reconnect link request message will be in ASCII as described in Section II.B.1.f j with each field separated by a field delimiter and the request terminated with a data 4 set delimiter. For example. pal' RECONNECT *01/12/89/11:48:50\ < CR > .

4

3. Protocol 4

a. ERDS will use XON/XOFF to stop. resume, or suspend data transminion for the site.

b. Communication parameters:

- eight data bits 1 stop bit

- parity = none d

4. Ezeeptions 1

Please note any exceptions which must be taken to Section II and explain why.

No exceptions to Section II.

. NUREG-1394. Rev. I 84 i

)

~

III. Selection Of Data Feeders 1

A. How many data feeders are there (six maximum)?

f l There is one data feeder supporting the Waterford 3 ERDS interface.

The Plant Monitoring Computer (PMC) is the ERDS data feeder.

1 i

1 1

I B. Identify the selected data feeders and provide the following for each:

- (1) a short description of the categories of data points it will provide *(e.g., met. rad. or plant data points, by unit) and (2) the rationale for selecting it if another system can r.lso provide its categories of data' points.

- (1) The PMC will supply all point data in the Waterford 3 DPL. No 1

changes to the DPL are required or anticipated during the Waterford 3 Plant Monitoring Computer replacement.

(2) All data required for the Waterford 3 DPL is available from the PMC

. through existing system interconnections.

a 3

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

l The Plant Monitoring Computer is the site time deterinining feeder.

1 I

)

d 8-7 NUREG-1394. Rev.1

I

)

. IV. Data Feeder Information ,

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

General Questions

1. Identification of Data feeder

s. 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 formmg it. ,

PNC - Plant Nonitoring Computer

b. Is this the site time determining feeder?

Yes, the PMC is the site time determining feeder.

c. How often will this feeder transmit an updata set to the ERDS (in seconds)?

An update set will be transferred to the ERDS every 30 seconds. -

i

2. Hardware / Software Environmens i

s. Identify the manufacturer and model number of the data feeder hardware. ,

I Digital Equipment Corporation Alpha 4000-610

b. Identity the operating system. I DEC Open VMS AXP Rev. 6.1

c. What method of timekeeping is implemented on this feeder system (Daylight Savings.

Standard. Grasmnch)?

Standard / Daylight Savings Time l

J. In wnst time zone is this feeder located?

5 Central Time Zone '

i l !

i l

i

! , NUREG-1394. Rev. I B-3

/

e

' .2 '. Dats Communication Details

, .t . Can this dats teeder provide asynchronous serisi dsts communication IRS 32 C) witn tull mocem control?

Yes, the PMC can support this mode of operation and a RS-232-C serial port is available.

b. Will this feeder transmit in ASCII or EBCDIC' i

The PMC will transmit in ASCII.

c. Can this feeder transmit at s serial baud rate of 2400 bps? If not. at what baud rate can it transmit?

The PMC will transmit at 2400 bps.

d. Does the operating system support XON/XOFF flow control?

l XON/X0FF flow control is supported by the PMC.

1. Are any problems foreseen with the NRC using XON/XOFF to control the trans. l mission of data?

. No problems are anticipated using XON/XOFF flow control.

1 i

e. If it is not feasible to reconfigure a serial port for the ERDU linkup ti.e change the baud rate. parity. etc.). please explain why.

N/A 1

(

f. Do any ports currentiv exist for the ERDS linkup?

Yes, a port is available for ERDS linkup.

1. If not. is it possible to add additional ports?

3 N/A B-9 NUREG-1394. Rev. I L

2. li yes. Eiil the port be used solely by the ERDS or shared with otner non.

emergency time users! Give details.

The port will be dedicated to the ERDS interface.

4. Data Feeder Physical Environment and Management

a. Where is the data feeder located in terms of the TSC. EOF. and control room?

The Plant Monitoring Computer room is imediately adjacent to the control room, within 200 feet of the TSC, and within 2 miles of the EOF.

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

Yes, the PHC is supported by the Waterford 3 Computer SUPS (approximately 1 hour1.157407e-5 days 2.777778e-4 hours 1.653439e-6 weeks 3.805e-7 months ).

c. Is there a human operator for this data feodar?

Yes, there is an on-duty PMC operator / technician.

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

. The PMC operator position is staffed 24 hours2.777778e-4 days 0.00667 hours 3.968254e-5 weeks 9.132e-6 months a day.

J 4

4 1

1 J

NUREG-13M. Rev. I D-10

.

ML20098C057

Text

Subject:

Navigation menu

Search