ML20237C850

From kanterella
Revision as of 14:44, 4 August 2021 by StriderTol (talk | contribs) (StriderTol Bot insert)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search
Informs That NRC Considering Establishing Emergency Communication Sys Called Emergency Response Data Sys (Erds). ERDS Concept Determined to Be Design Which Best Addresses Requirements of NRC W/Minimal Impact on Licensee
ML20237C850
Person / Time
Site: Nine Mile Point, 05000000
Issue date: 04/25/1986
From: Starostecki R
NRC OFFICE OF INSPECTION & ENFORCEMENT (IE REGION I)
To: Hooten B
NIAGARA MOHAWK POWER CORP.
Shared Package
ML20235G519 List: ... further results
References
FOIA-87-737 NUDOCS 8712220225
Download: ML20237C850 (16)
v • d • e


Text

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ .

~

8 'o, UNITED STATES

[' 1,4 'j E NUCLEAR REGULATORY COMMISSION ,

REGION I o,, [ 631 PARK AVENUE KING OF PRUSSIA, PENNSYLVANIA 19406

%.....,o#

APR 2 51986 1Cocket No. 50-410 Niagara Mohawk Power Corporation ATTN: Mr. B. G. Hooten Executive Director Nuclear Operations 300 Erie Boulevard, West Syracuse, New York 13202 l

Gentlemen:

Subject:

Emergency Communication System, Point-of-Contact This letter is to inform you of an emergency communications capability that i the NRC is considering establishing with licensed nuclear power facilities and an upcoming site visit by an NRC contractor to obtain information on how such a system would interface ith .your facility.

The emergency communication capability being considered is called the Emergency Response Data System (ERDS), The EROS concept has been determined by the NRC to be a design which best addresses the requirements of the NRC with minimal impact on the licensee. The development of the ERDS concept began with an assessment of what is the' NRC's role in an emergency at a licensed nuclear facility. Tre Commission determined that the NRC's primary role is one of n.onitoring the licensee to assure that appropriate recommendations are made with respect to offsite protective actions. To fulfill this 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 likelihood of core damage; (2) conditions inside the containment must be known well enough to assess the likelihood of its failure; (3) radioactivity' release rates must be available promptly to assess the immediacy and degree of public danger; and (4) the data f rom the plant's meteorological tower is necessary to -

assess the distribution of potential or actual impact on the public. A list of the particular parameters considered necessary to these assessments is included as Enclosure 1.

Experience with the voice-only emergency communications link, currently utilized for data transmission, has demonstrated that excessive amount of time are needed for the routine transmission of data and for verification or correction of data that appear questionable. Error rates have been excessive; initiations have been slow; frequency of updates have been unreliable. In addition, the current system creates an excessive drain on the time of valu-able experts at the NRC and at the facility. When errors occur, they- f re-quently create false issues which, at best, divert experts. from the real problems for seriously long periods of time. At worst, incorrect data may cause the NRC to respond to of fsite officials with inaccurate or outdated advice that results in the implementation of inappropriate protective actions.

8712220225 871210 PDR FOIA SHOLLYB7-737 PDR

f.

2 i

Several at options were the Operations considered for upgrading the data acquisition capabilities Center.

data: The options included various means of acquiring the electronically formatted specially qualified communicators. data, image facsimile, or by voice through The criteria used to compare these options involved accuracy, reliability, timeliness, completeness, cost (in dollars and expert personnel), and backfit-ting requirements.

The NRC determined that automatic transmission of selected parameters from licensees' existing electronic data systems is not capable of providing acceptably complete and reliable data on a timely basis at reason-able cost with the minimum potential for burdening licensees in an emergency.

Most licensees either already have developed or are developing electronic data systems for their emergency response f acilities (ERFs). Because the role of the licensees' ERFs is similar to the role of the NRC during emergencies, the licensee's data systems already include most of the parameters desired by NRC.

Those few parameters which are not included in any particular licensee's system can be communicated by voice over the Emergency Notification System (ENS), thus avoiding backfitting requirements on the licensee to include additional parameters on their electronic data systems. Data would be accepted in whatever as necessary.format the licensee uses and reformatted at the Operations Center, Because of the diversity of data systems utilized by the licensees, the best means for extracting the NRC's parameters from each system would be determined on a case-by-case basis.

The licensees would have control over transmission and would use the system only during emergencies. This option is the Emergency Response Data System (ERDS). The design concept for the ERDS is outlined in Enclosure 2.

1 Previous discussions with several licensees and two tests of the ERDS concept which were conducted with Duke Power and Commonwealth Edison have indicated that the ERDS concept has the potential to significantly improve the NRC inci-dent response function and our response relationship with licensees. Therefore, to determine more specifically the factors that would effect implementation of an ERDS we have initiated an effort to survey the equipment and facilities at licensees' sites and determine the hardware and software requirements of such a system.

You should designate an individual to act as a contact point for'this effort and have that individual contact the Project Section Chief responsible l j

for your facility in Region I within the next two weeks. A site visit by a NRC  !

Headquarters staff member accompanied by a NRC contractor will be arranged.

The visit is an information gathering process. It is oriented toward deter- I mination of: i The form.

availability of a particular set of PWR or BWR parameters in digital The verification and validation method, if any.

Characterization of the available data feed point (s).

F.

3 Access will be needed to documentation and knowledgeable individuals typically from instrumentation and control, technical, telecommunications, and computer system cadres within the plant staff. Further information on the personnel and information desired is provided in Enclosures 3, 4, and 5. Should you have any questions on this site visit please contact the responsible Project Section Chief in Region I.

Should you have any question on the ERDS concept in general please contact Ken Perkins of the Incident Response Branch at NRC Headquarters. He can be reached at 301-492-7361.

Sincerely, D f

' i s (i.. w 'u

-eq Richard W. rostecki, Director Division of Reactor Projects

Enclosures:

As Stated 1

\

l 1

l i

4 cc w/2ncis:

Connor & Wetterbahn John W. Keib, Esquire J. A. Perry, Vice President, Quality Assurance W. Hansen, Manager of Quality Assurance D. Quamme, NMP-2 Project Director C. Beckham, NMPC QA Manager T. J. Perkin's, General Superintendent R. B. Abbott, Station Superintendent  :

Department of Public Service, State of New York Public Document Room (POR)

Local Public Document Room (LPDR)

Nuclear Safety Information Center (NSIC)

NRC Resident Inspector State of New York bec w/encis:

Region I Docket Room (with concurrences)

DRP Section Chief Region I SLO I

l I

l O

Enclosure 1 PWR PARAMETER LISTS Primary Coolant Pressure.

System Temperatures - hot leg Temperatures - cold leg Temperatures - core exit thermocouple  ;

Subcooling margin Pressurizer level RCS charging / makeup flow Reactor vessel level,(when available)

Reactor coolant flow Neutron flux startup range Secondary Coolant Steam generator levels System .

Main feedwater flows Auxiliary / Emergency feedwater flows Safety Injection High pressure safety injection flows low pressure safety injection flows Safety injection flows (Westinghouse)

Borated water storage tank level-Containment Containment pressure Containment temperatures Hydrogen concentration Containment sump levels Radiation Monitoring Reactor coolant radioactivity System Containment radiation level Condenser air removal radiation level Ef fluent radiation monitors Process radiation monitor. levels Meteorological Wind speed Wind direction 3

-Atmospheric stability l

l 4

1 l

. BUR PARAMETER LISTS

-Reactor Coolant Reactor pressure System o Reactor vessel-level l Feedwater flow Neutron flux-Startup range Safety Injection RCIC flow HPCI/HPCS flow Core spray flow LPCI flow i

Condensate storage tank level l

Containment Drywell pressure Drywell temperature Hydrogen & 0xygen Concentration Drywell sump level Suppression pool temperature Suppression pool level Radiation Monitoring Reactor coolant radioactivity level-Systems Primary containment radiation level Condenser off gas radiation levels Effluent radiation monitor Process radiation levels Meteorological Wind speed Wind direction Atmospheric stability-4 I

s 1

l u_____- -

Enclosure 2 EMERGENCY RESPONSE DATA SYSTEM (EROS)

DESIGN CONCEPT Data Acquisition Parameter inputs to ERDS would be obtained from an existing computer system (e.g SPDS, plant computer, EOF data systems, etc.) at the plant.

Data Transmission Data will be transmitted to the NRC Operations Center by modem to commer-cial telephone line or a dedicated line maintained by NRC (e.g. ENS).

Data Collection A processing system maintained by the NRC will receive the data stream by modem.

The system will be designed to receive all varied data streams and to reformat the data into a consistent format. The reformatted data will be output to CRTs and printer.

Parameter List The parameter list would include those parameters necessary to ensure that I appropriate protective action is being taken with respect to offsite recommendations.

plant status, radiological and meteorological conditions.The list would be Licensees will not be required to backfit their systems to include addi-tional parameters to provide data on NRC's parameter list. Data that is not available over from the existing phone electronic data stream can be provided by voice lines.

Transmission Frequency i

The updating frequency of the licensees' systems will determine transmis-sion frequency to NRC.

If more frequent updates are required than those provided electronically by a particular licensee, the increased frequency overbe will accomplished existing telephone (forlines.

a very limited subset of parameters) by voice Centrol The licensee will have complete control over data transmission. EROS would be " switched on" by the licensee in the early stage of a declared emergency.

1 i

l l

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ a

PERSONNEL AND REFERENCE MATERI AL l

It is recogni zed that the key disciplines necessary to support the ERDS survey will represent different departments and organizational (e.g., Corporate relationships unique to each utility surveyed vs. Plant Site Engineering staff). It is believed that most of the appropriate personnel will be the  !

same as those on the project teams for SPDS and Energency Response Facility Data Acquisition System development.

The appropriate utility manager to coordinate the ERDS site survey is likely to be the same individual who is responsible for SPDS, RG1.97 or ERF upgrade programs. The approximate man-hours for each site survey are based on a 2 to 2 day survey for a single unit site or a 2 unit site where both units are identical and a common Data Acquisition System has j been installed at a common TSC or EOF. '

Personnel Approxima t e Person or Discipline Man-Hours Required ERDS Survey Coordinator 1 8 - 12

)

NSSS System Expert 4-6 l

l Plant I&C Expert 2- 4 Computer Hardware Expert (for ERDS signal source (s)) 4 -6 Computer Applications Expert 4 -6 Emergency Planning Coordinator 1/2 - 1 Telecommunications Expert 2- 4 l Meteorologist or Environmental Engineer 1/2 - 1 l

Radiological Monitoring System Expert 1 RGl.97, RVLIS, SMM Instrument Expert . 1 k

l

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ - - - - - - _ - - - - - - - - - - - - J

i It is understood that many of the areas of expertise listed above may be represented by a single individual (e.g., one I&C engineer may be able to address instrument characteristics and display conventions for RVLIS, SMM, Radiological, and i Meteorological ins t ruments ) .

Reference Material ,

FSAR Any locally generated Plant Data Book (Compilation of System Design Data)

Systems Training Manuals Tables or graphs for engineering unit conversion (e.g.,

feet to gallons for containment sumps)

Data System Design documents and block diagrams Hardcopy printouts of Data Acquisition System displays l

i 2

1 Enclosure 4 specific section of the ERDS survey instrument.This samples are as follows:

r- attach The three Generic Checklist:

This four page checklist is repeated for each of the 29 PWR parameters and 25 BWR parameters Some questions (e.g., in the checklist do not apply to every parameter factors would not be applicable to parameters such as Hotques Leg Temperature which is always expressed in degrees Parenheit).  ;

j

- j Parameter-Specific Checklist \

(applicable to both PWRs and BWRs) .for Atmospheric Stabili ty (

Parameter-Specific Checklist {

In]ection Flow for BWR Low Pressure Coolant l

I l

l I

C. Number of separate locations monitored (i.e. loop 1, '

2, loop 3, etc)?

loop D. How many ranges of instrumentation ere provided for each location monitored?

E. For each of these ranges, describe instrument range:

F. Reference point of each instrument range (e.g. BWR level; ref. to bottom head or feedwater sparger or steam separator shroud; PWR RVLIS; etc.)?

G. Number of instruments within each range for each location.

monitored (e.g. PWR loop 2; Th; 2 NR & 1 WR etc.')?

H.

For those cases where data does not read out at the host location in final required units, what is the engineering conversion factor for each range (i.e. tank level measured in feet, factor to convert to gallons)?

3

NOTE:

If conversion factor is not e simple constant, you

, may require a copy of the curve. (For example, of on irregularly shaped RWST tank where level data isin the cose provided in feet, capacity curve toyou must obtain a copy of the tank allow to gallons). the ERDS system to convert levels  !

Not applicable.

Conversion is a constant, value is:

Conversion is not a constant, curve attached.

t Conversion is not a constant, curve not required or not obtained.

1. Engineering units for each range?

3 1

4.

If parameter is a processed value, describe the following attributes arrive at aofsingle how the above instrument inputs are processed to value:

A. Does the processed variable instrument range? take inputs from more than one

\

1. If yes, ranges. then describe method used to switch between '4 I

B.

For each range of the parameter available, identify the instruments processed whose signals are combined to provide the parameter?  ;

~

4

C.

Describe the validation scheme used for range checking.

.orror checking and overoging the input parameters?

l l

l 1

l 5

PARAMETER: ATMOSPHERIC STABIL2TY SPECIFIC CHECKLIST:

1.

IF THE SITE EMPLOYS MORE THAN ONE METEOROLOGICAL TOWER FOR REASONS OF TERRAIN (AS OPPOSED TO REDUNDANCY), THEN COLLECT THE DATA BELOW FOR BOTH TOWERS.

2.

WHAT IS THE LOCATION OF EACH OF THE TOWERS WITH RESPECT TO THE PLANT POWER BLOCK?

3. WHAT IS THE HEIGHT OF THE LOWER TEMPERATURE DETECTOR?

4.

WHAT IS THE HEIGHT OF THE UPPER TEMPERATURE DETECTOR?

i 5.

WHAT IS THE DISTANCE IN METERS BETWEEN THE LOWER AND UPPER l TEMPERATURE DETECTORS? '

6.

DOES THE HOST COMPUTER CONVERT THE DELTA T INTO A DEGREES CENTIGRADE PER 100 METERS VALUE?  !

1 l

6

SPECIF3C CHECKLIST:

]

1. HOW MANY TRA8NS OF RHR ARE AVAILABLE?
2. HOW MANY RHR PUMPS PER TRAIN?
3. WHAT IS THE DESIGN CAPACITY OF EACH RHR PUMP?
4. WHAT IS THE SHUTOFF HEAD OF THE RHR PUMPS?
5. WHAT IS THE TOTAL DESIGN RHR FLOWRATE IN THE LPCI MODE?' l 6.

IS THE RHR SYSTEM SHARED WITH ANOTHER UNIT? i A. IF So, DESCRIBE LINEUP?

l 7

~

inB osure 5 OVERVI EW OF COMPUTER AND TELECOMMUNICATIONS SYSTEM INFORMATION NEEDS Computer _Systens Related The computer systems related portions of the survey instrument focus on the following general areas of investigation. ,

i Characterization of each utility computer system that is  ;

a potential data feeder to ERDS: i its hardware and system sof tware environment its data communication technical details Characterization of the potential siting locations for NRC-provided hardware.

Characterization of the documentation available that describes the plant-specific details of the engineering evolution of a parameter value (as it travels from a sensor through analog and digital logic and computer systems to a reactor operator's eyes) .

Telephony Related The telephony-related portions of the survey instrument focus on the following general areas of investigation:

Characterization of potential site-related engineering dif ficulties associated with the utility providing a dial-up phone line accessible to, and suitably configured for, the NRC-provided ERDS computer hardware.

Characterization of potential operating procedures for utility personnel creating and maintaining the dial-up phone connection between the site and NRC headquarters.

1 i

_ _________-_-_w

Retrieved from "https://kanterella.com/w/index.php?title=ML20237C850&oldid=3273601"