ML20099B429

From kanterella
Jump to navigation Jump to search
Forwards Completed ERDS Survey Questionnaire,Per Rev 1 to NUREG-1394 Re ERDS Implementation,Consisting of Quality Codes & Descriptions for Plant Process Computer Sys at Facility
ML20099B429
Person / Time
Site: Ginna Constellation icon.png
Issue date: 07/20/1992
From: Mecredy R
ROCHESTER GAS & ELECTRIC CORP.
To: Andrea Johnson
NRC OFFICE OF INFORMATION RESOURCES MANAGEMENT (IRM), Office of Nuclear Reactor Regulation
References
RTR-NUREG-1394 NUDOCS 9207310156
Download: ML20099B429 (7)


Text

. . . _ - __

ROCHESTER GAS AND ELECTRIC CORPORATION

  • 89 EAST AVENUE, ROCHESTER H Y. 14649 b001 ,

sostu c m uto m m* >st

  • *n Pm"W"' MK r ctXf m $4(r2100 u w~ e, s.
  • July ~20, 1992 U.S. Nuclear Regulatory Commission 1 Document Control Desk Attn: Allen R. Johnson I

Project Directorate I-3 Washington, D.C. 20555  ;

Subject:

Emergency Response Data System (ERDS)

Submittal of ERDS Survey Questionnaire R. E. Ginna Nuclear Power Plant

- Docket No. 50-244 Rcf.(a): NUREG-1394, Revision 1, Emergency Response Data System Tmplementation, June 1991 (b): Letter f rom R. C . Mecrady, RG&E, to A.R. Johnson, NRC, subject: Submittal of. Data Point Library Sheets, dated-February 28, 1992

Dear Mr. Johnson:

Enclosed is the information required in reference (a), Appendix B.

Also enclosed are the quality codes - and descriptj ons for- our Plant-Process Computer System (PPCS) at Ginna Station.- Based on our october 18, 1991 meeting with the NRC and-Halliburton NUS at King of Prussia, PA, the NRC will use the quality codes as they appear on the PPOS. Please inform us if there are limitations-on the number of etuality codes that the NRC can accept.

Ve truly yours,.

.+

Robert C. Mec edy [

GAL \236

.ttachments xc: Mr. Allen R. Johnson (Mail ~Stop 14D1)-

Project Directorate I-3 Washington, D.C. 20555 U.S. fluclear. Regulatory Commission Region I 475-Allendale Roid King of Prussia, PA 19406 0 I L

h US NRC Ginna Senior Resident Inspector h[1 .

g74tg Eg4 F

[#[t

I; .

ATTACHMENT A 13

{From NUREG-1394 Rev. ? Apper. dix B]

I. Contacts Note: Pleast provide name,-title, mailing add)ess, and phone ^

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

Peter Polficit On-Site Emergency Planner R.E. Ginna. Nuclear Power Plant 1503 Lake Road Ontario, NY 14519 315-524-4446 X108 B. Computer Hardware Specialist (s):

Thomas Kaza Computer Systems Loordinator same address "

315-524-4446 X899 C. Systems Software Specialist (s)

Thomas Kaza D. Application-level Software Specialist (s):

, Thomas Kaza E. Telepnone Systems Specialist (s):

David Le'eper

> Foreman, I&C Special Projects same address 315-524-4446 X100 I I .- ERDS Communications Description

'This section provides information ..to licensees. - No response required.

_ _ _ _ _ _ _u _ _ - - _ _ _ _ _ _ - - - - - - - - - - - - - - - - - - - - -

i a ,

i '

!i j III. Selection of Data Feeders A. How many data feeders are there (six maximum)?

5 One data feeder i

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, b:;

unit)

{ Meteorological, Radiation monitoring, and Plant data points will be provided.as' described on the-DPL sheets

submitted in Reference (b).

(2) the rationale for selecting it if another system can also provide its categories of dats points.

N/A

! C. Which data' feeder is the site time determinin'J feeder? This

abould be the feeder wnich is providing the majority of the data points.

Site time is j)pi determined by data feeder time.

l-i IV. I'ata Feeder Information Note: A new Section IV must be- filled out~for-cach feeder system selected.

I I

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 givelboth the acronym and the words forming it.

PPCS - Plant Process Computer System L .
b. Is-this the site time det'rmining e feeder?

No l

i l t-

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

i-One transmission /60 seconds

2. Hardware / Software Environment l a. Identify the' manuf acturer and model number of the data j feeder hardware.

i Gould SEL 6780 i

b. T.dentify the operating system.

MPX 3.2 B

c. What method of timekeeping is implemented on this feeder system (Daylight Savings, Standard, Greenwich)?

Eastera; Standard / Daylight Savings Time

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

l Eastern

j. 3. Data Communication Details
a. Can this data feeder provide a synchronous serial data I communication (RS-232-C) will full-modem control?

Yes

b. Will this feeder transmit in ASCII or EBCDIC 7~ ,

ASCII

! c. Can this feeder transmit at a serial baud - rate of ' 240 )

bps? If not, at what baud rate can it transmit?.

2400 bps

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

l

-Yes

-1.- Are any problems foreseen.with the NRC'using XON/.

XOFF-to control-the transmission of. data?

No-L , . _ _ _ _

. .u . _ ,_ _-___..,_;-._.,._.-.._._.-. . . _ . . . - . . _ - . . . . -._....-.w..

c. 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.

N/A; The port will be configured for the ERDS linkup

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

d No '

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

Yes

2. If yes, will the port be used solely by the ERDS or shared with other non-eu.ergency-time users? _Give details.

Used solely for ERDS

4. Data Feeder Physical Environment and Management
a. Where is the data feeder located in terms of the TSC, EOF, and control room?

TSC Computer Room

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

Yes. The PPCS is powered f rom the Technical - Support Center Uninterruptible Power Supply

c. Is there a human operator for this data feeder? i Yes
1. If so, how many hours a day-is the, feeder attended?

Typically 8-hours / workday

_ _ _ - _ - - _ - _ - - _ _ _ _ _ _ _ _ - . - - - = . - -

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

_~. .

- . _ . _ - ~ _ _ _

1 l

l

_ c, _

) ATTACHMENT B 4 I l Plant Process Computer System (PPC3) l l Data Quality Code Definitions I l l- . Code Name Color Description j i .

j 00 UNK White Unknown.- Point has not yet been processed.

i White Point is deleted from processing by 01 DEL i the operator. Point will not be processed until re-enabled.

! 03 NCAL White Value is "non-calculatc.ble" due to j one or ' more' required input- values having a " white" quality code.

i j 04 INVL M' i te Invalid., Data-acquisition hardware arror.

05 RDER White Sensor read error.

06 OTD White Open thermocouple error.

07 BAD White Analog input " counts" exceed sensor i limits.

08 HENG Red Engineering unit (EU) value is.above .

j high_EU.

09 LENG Red EU value is below low-EU.

i

!- 10 REDU_ Red Point f ails redundant point compari--

son.

j 11 HALM Red EU value'is above high. alarm limit.

12 LALM Red EUJvalue'is below low alarm limit.

l 13 ALRM Red Logical-value Point's. state matches

-defined alarm state.

14 COS Red Logical-value Point meets change-of-state alarm criteria i 17 HWRN Yellow EU value is above high warning lim-i t .-

1 -

, 18 lLWRN Yellow EU value is below low warning limit.

_ . . = - m. _ , , . . _. _ , , _ . . _ . . - _ . . .

22 SUB Green A substirute value has been entered for Point.

24 DALM Green Point is deleted from all alarm processing.

25 INHB Green Point is in an abnormal condition, but alarm generation is inhibited via cut-out point.

26 OTT Green Open thermocouple hardware test-was in progress when point was scanned.

29 GOOD Green Point is normal, J.c., passes all above tests.

Suspect Data Bias In the RG&E PPCS system, additional provision is made to identify certain data points whose values are considered to be " suspect"'or-questionable. Examples of suspect data. points are:

1. a calculated point where one or more of-the-argument points used in the calculation has a " white" data quality code and, hence, the " white" point.was excluded-from the calculation'.
2. cn average-value calculation where one er more of the point values used in the calculation -differed by more than _a specified tolerance from the average value and war excluded-from the calculation.

" Suspect" data points are considc; ed as valid -points for use. in

, _other - point calcu?ations._ " Suspect quality - codes . of argument points in calculations are p mogated to the calculated point.

The quality code of a suspect point will be biased by 128. For example:

GOOD code = 29 SUSPECT bias = + 128 quality code = 157 Alarm Posted Bias

' An " alarm'- posted bias" of 32 - may also be included in the data quality code. The alarm bias is-for internal alarm processing and should be ignored by the NRC. For example:

GOOD code = 129 posted bias = + 32 quality code = 61

- - _ _ _ _ - _ _ . _ _ _ _ _ _ -