ML18064A617

Discusses Changes to Erds,Including Replacement of Criticality Functions Monitoring Sys (CFMS) Which Provides SPDS Functionality.Replacement of CFMS Computer Scheduled for Mar or Apr of 1995

ML18064A617
Person / Time
Site:	Palisades
Issue date:	02/13/1995
From:	Haas K CONSUMERS ENERGY CO. (FORMERLY CONSUMERS POWER CO.)
To:	NRC OFFICE OF INFORMATION RESOURCES MANAGEMENT (IRM)
References
NUDOCS 9502210171
Download: ML18064A617 (14)

Text

consumers Power KurtM. Haas Plant Safety and Licensing Director POWERIN&

MICHl&AN"S PIUl&llESS Palisades Nuclear Plant: 27780 Blue Star Memorial Highway, Covert, Ml 49043 February 13, 1995 Nuclear Regulatory Commission ATTN: Document Control Desk Washington, DC 20555 DOCKET 50-255 - LICENSE DPR PALISADES PLANT CHANGES TO THE EMERGENCY RESPONSE DATA SYSTEM The Palisades Nuclear Plant will replace the Critical Functions Monitoring

~ystem (CFMS) in 1995. This system provides. the Safety Parameter Display System (SPDS) functionality and is linked to the Emergency Response Datalink System (EROS). Replacement of the CFMS computer will result in the SPDS and EROS being out of service for a period of time. We will notify the NRC

• approximately one week prior to the replacement of the CFMS computer, which is currently scheduled for March or April of this year. We estimate that the SPDS will be out of service for no longer than one week and the EROS out of service for no longer than three weeks ..

10 CFR 50 Appendix E, Section VI, describes the EROS requirements. One of the requirements is to notify the NRC as soon as practicable, but at least thirty days prior to hardware or software modifications that could affect the transmission format and computer communication protocol to the EROS. The new CFMS computer system uses a different type of computer and operating system but, as demonstrated during factory acceptance testing, the new system is able to link to the NRC's EROS system with no changes to the EROS attributes or EROS communications protocol.

Appendix E to 10 CFR 50, paragraph Vl.2.b requires that the EROS system be capable of transmitting all available EROS parameters at time intervals of not less than 15 seconds or more than 60 seconds. The new computing system will transmit data every 15 seconds. In our June 27, 1989 EROS survey response, we noted an exception to the NRC's request to provide a system capable of transmitting all available .EROS parameters at a fifteen~second rate. In the survey response, we indicated that we were not sure that a 15-second rate 9502210171 950213 PDR ADOCK 05000255 F PDR Ac.MS ENERGY COMPANY

2

~.-*--.

could be maintained during a plant transient without affecting performance of the CFMS tasks. At that time, we stated that we would use 60 seconds as a transmission rate.* Both our current and proposed systems data transfer rates meet the data transfer requirements.

In our June 27, 1989 letter we responded to the NRC EROS survey from NUREG 1394 which was designed to provide the NRC with the hardware, communications, data point and administrative information necessary for the NRC to design the EROS interface *and data base for Palisade~. Because the information on the data transfer rates mentioned above was contained in that survey, and because we have made some other minor changes to information provided by the survey, We have revised the survey information and it is provided in Attachment 1.

. Note that the attachment is provided in the format of the survey found in Revision. 1 to NUREG 1394 ..

If you have any questions on these design changes do not hesitate to call the plant specialist for the EROS system, Andrew Zillins at (616) 764-8913 extension 0377.

SUMMARY

OF COMMITMENTS This letter contains one new commitment, as follows:

We will notify the NRC approximately one week prior to the change-out of the CFMS computer.

I Kurt M Haas Plant Safety and Licensing Director CC Administrator, Region III, USNRC NRC Resident Inspector - Palisades Attachment

e.

• ATTACHMENT Consumers Power Company Palisades Plant Docket 50-255

• I CHANGES TO THE EMERGENCY RESPONSE DATA SYSTEM 11 Pages

.e APPENDIX B ERDS COMMUNICATIONS DESCRIPTION AND SURVEY QUESTIONNAIRE

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

Emergency Response Data System (ERDS). It consists of a series of questions concerning plant 110 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 communication line.

• The purpose of collecting the data is to develop a plant-specific database that will be retrieved

• into the EROS once the system is activated by a utility. It will also be used to design and imple-ment EROS 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 EROS 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 EROS interface PC as well as each computer which feeds data to the inter-face PC.

This request Is covered by Office of Management and Budget Clearance Number 3150-0150

• which expires March 31, 1992. The estimated average burden hours is 32 person hours per licen-see response, including staff and management review and preparation of the requested re-sponse. These estimated average burden hours pertain only to those identified response-related matters and do not include the time for any follow on implementation. Send comments regard-ing this burden estim*ate or any other aspect of this collection of information, including sugges-tions for reducing this burden, to the Records and Reports Management Branch, Division of Information Support Services, Office of. Information Resources Management. U.S. Nuclear Regulatory Commission, Washington, DC 20555; and to the Paperwork Reduction Project (3150-0150). Office of Management and Budget, Washington, DC 20503.

Note: Consw;iers Power Company originally responded to the NRC's April 5, 1989 request to respond to the survey.

Attached is Revision 1 to the survey.

B-1 NUREG-1394. Rev. I

I. Contacts Note: Please provide name. title. mailing address. and phone number.

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

Andrew Zillins Consumers Power Company 27780 Blue Star Hwy Covert, MI 49043 (616) 764-8913 B. Computer Hardware Specialist(s):

Andrew Zillins C. Systems Software Specialist(s):

Andrew Zillins D.

• Application-level Software Specialist(s):

• Andrew Zillins E. T de phone Systems Specialist(s):

. Sandy Wymer, Emergency Planning, or Butch Geisler, Facilities Consumers Power Company 27780 Blue Star Hwy Covert, MI 49043 (616) 764-8913 .

NURCG-1394. Rev. 1 B-2

II. EROS Communications Description A. Hardware The following hardware will be supplied:

for a single-feeder site:

Codex 2235 modem or equivalent - V.22 2400 bps. asynchronous. auto~dialing. auto-*

answer. error-correcting. using the AT command set for a multiple-feeder site:

Codex 6015 multiplexer, Codex 2264 modem or equivalent - V.32 9600 bps. asynchronous. auto-dialing. auto-answer. error-correcting, using the AT command set (for an alternate approach see Appendix A. Item 7)

The modems are intended to be operated in the auto-reliable link mode (referred to as MNP in.

the modem manuals). There are several modem parameters that affect MNP operation. These are discussed in the sections of the modem manuals pertaining to MNP. The single feeder mo-dems at the NRC Operations Center are configured for auto-reliable link mode. local terminal tlow control. and default break handling. '

B. Software

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

(<CR>).

a. Site will initiate a link request in ASCII using:

the three-character site designator.

the word LINK, local site time and date in the format MM/DD/YY/HH:MM:SS. and a <CR>.

If the site does not receive a response from the ERDS within one minute. it should send 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. -

b. ERDS will respond in .ASCII with:

the-three-character 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-minute intervals. If B-3 NUREG-1394. Rev. 1

. more than five minutes elapses without a response. site personnel should notify the NRC before disconnecting the line. *

c. When the EROS is ready to receive data, it will send an initiate message in ASCII using:

• the three-character site designator, the word INITIATE. 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 (described in Section II.B.1.f.).

d. Upon receipt of the initiate message,. the plant begins transmission of data at a 15-second rate. The data string consists of:

• a header containing the three-character site designator and date and time in the format MM/DO/YY /HH:MM:SS, the data packet sequenced with point identifier, value, a.nd quality tag, a trailer containing the checksum value of the data packet, and a <CR> .

e. When the site or ERDS wishes to terminate the connection, an ASCII message will be

. sent containing:

the three-character site designator, the word TERMINATE, and a <CR>.

f. 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 EROS by redialing and using the link reconnect message. The link reconnect message should be used any time .the phone line is lost after the receipt of an Accept Message (described in Section II.B.1.b). This message is in ASCII and will contain:

the three-character site designator, the word RECONNECT, .

local site time and date in the format MM/OD/YY/HH:MM:SS. and a <CR>.

• Upon receipt of this message. the ERDS will respond with the accept and initiate mes-sages as described in Sections II.B.l.b and II.B.1.c. If the EROS responds with a link deny message (described in Section II.B.1.b), the site should stop trying to reconnect and send a link request message (described in Section II.B.1.a). If the EROS does not respond to the site's reconnect 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 NRC before 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 NRC. the site should not disconnect the phone line until a TERMINATE message (described in section NUREG-l394. Rev. 1 B-4

l ,_

II.B. Le) has been transmitted. If problems are encountered in the link request se-

- quence. -do not hang up the line but proceed with the stei:>s 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.1.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 (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 soft-ware use the data set delimiter as the message delimiter for messages received from the ERDS.

a. Link requests will be in ASCII as described in II.B.1.a. with each field separated by a field delimiter and the request terminated with a data set delimiter. For example, PAl *LINK*Ol/12/89/11:48:50\ <CR>.

_b. The ERDS response will be in ASCII as described in II.B.1.b. with each field sepa..:

rated by a freld 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 response terminated with a data set delimiter. For example, PAI *INITIATE\< CR>.

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 three parts separated by a data set delimiter. For example, Header: PA POl/12189/l Li0:30\

Data: B21CP004*-0.1234E+003* ..... (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 characters in length.

B-5 NUREG-1394, Rev. 1

g. the following quality tags will be accepted by the EROS:

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

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

Suspect =2 Value is not bad yet should not be considered good. This 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 may make the result questionable.

Bad =3 Value is not within tolerance for discreet points or calcu-latiQn 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 dis-creet or composed value. *

• High Alarm .= 6 Value is in high alarm .

Low Alarm = 7 Value is in low alarm.

h. The checksum which accompanies each update set will be an integer value calculated by summing each of the bytes of the transmission, up to and including the dataset de-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 th!! transmitted bytes.

• 1. The reconnect link request message will be in ASCII as described in Sect\on II.B. l.f with each field separated by a field delimiter and the request terminated with a data set delimiter. For example, PAl *RECONNECT*Ol/12/89/11:48:50\ <CR>.

3. Protocol

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

b. Communication parameters:

eight data bits -- . ---*--

1 stop bit parity = none

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

NUREG-L394, Rev. l B-<l

III. Selection Of Data Feeders A. How many data feeders are there (six maximum)?

One data feeder.

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 also provide its categorie*s of data points.

Palisades.Plant Computer (PPG)

( 1) All data points requested are availa.ble o~ the PPC and*

(2) is only system containing all categories of data points.

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

• Palisades Plant Computer (PPG)

B-7 NUREG-1394. Rev. l

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

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.

Palisades Plant Computer (PPC)

b. Is this the site time determining feeder?

Yes

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

Every 15 seconds.

2. Hardware/Software Environment

a. Identify the manufacturer and model number of the data feeder hardware.*

Digital Equipment Company (DEC), Hodel 4705A

b. Identify the operating system.

VMS

c. What method of timekeeping is implem~nted on this feeder system (Daylight Savings.

Standard. Greenwich)?

Daylight Savings

d. In what time zone .is this feeder located?

Eastern NUREG-1394. Rev. 1 B-8

3. Data Communication Details

a. Can this data feeder provide asynchronous serial data communication (RS-i32-C) with full-modem control?

Yes.

b. Will this feeder transmit in ASCII or EBCDIC?

ASCII

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

Yes, i t .can transmit at 2400 bps.

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

Yes.

1. Are any problems foreseen with the NRC using XON/XOFF to control the trans-

. mission of data?

No.

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

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

Yes.

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

B-9 NUREG-1394, Rev. 1

2. If yes. will the port be used solely by the EROS or shared with other no~

emergency-time users? Give details.

Yes, used for ERDS only.

4. Data Feeder Physical Environment and Management

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

In a trailer on turbine deck within 100 feet of Control Room/TSC.

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

UPS will supply PPC for greater than two hours following a loss of offsite power. The PPC is capable of automatic restart after return of power.

c. Is there a human opexator for this data feeder?

No.

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

NUREG-1394. Rev. l B-10