ML20058C933
| ML20058C933 | |
| Person / Time | |
|---|---|
| Issue date: | 10/02/1990 |
| From: | Chilk S NRC OFFICE OF THE SECRETARY (SECY) |
| To: | |
| References | |
| FRN-55FR41095, RULE-PR-50 AD32-1-002, AD32-1-2, PR-901002, NUDOCS 9011050230 | |
| Download: ML20058C933 (23) | |
Text
.-
<t DOCKET ID.'BER PROMSED RULEkdo.,
~
(65 F/2. 41095)mnitD UwkC
'90 BCT -3 NO 52
[7590-01)
- m cy ; n cd W '
bdChi i JG .'"'I ' VU inW NUCLEAR REGULATORY COMMISSION 10 CFR Part 50 RIN 3150 - AD32 Emergency Response Data System AGENCY:
Nuclear Regulatory Commission.
ACTION:
Proposed rule.
SUMMARY
The Nuclear Regulatory Commission (NRC) proposes to amend 10 CFR Part 50 of its regulations to require licensees to participate in the Emergency Response Data System (ERDS) program and to set a definite schedule for its implementation. The ERDS is a direct electronic data link between computer data systems used by licensees and the NRC Operations Center.
The ERDS would supplement the voice transmission over currently installed Emergency Notification System (ENS).
The ERDS would provide the NRC Operations Center with timely and accurate values of a limited set of parameters that describe selected plant conditions. The parameter values would be taken directly from data systems existing on a licensee's onsite computer.
The ERDS would be activated by a licensee during the declaration of an alert or higher emergency classification at a licensed nuclear power facility. The NRC's response role in the event of an emergency at a licensed nuclear-facility is primarily to monitor the licensee to ensure that appropriate recommendations are made by the
~
licensee regarding off-site protective actions.
The proposed rule is needed to q
qD g10g230901002
['
M*'
50 55FR41095 PDR {
l
%C'l
l'-
9 improve the NRC's capability to fulfill its response role during an emergency by better assuring that it will receive accurate and timely information on plant conditions.
This action will also allow the licensee to more effectively and efficiently utilize its time and resources in. collecting and transferring data to the NRC. The proposed requirement would apply to all operating nuclear power reactor facilities except Big Rock Point and those that are permanently or indefinitely shut down.
However, units shut down for maintenance, or authorized only for fuel loading and low power operations are required to report under ERDS.
Big Rock Point is exempt because the configuration of the facility is such that the number of parameters available are not sufficient for effective participation in the ERDS program.
DATES:
Comment period expires [75 days after date of publication in the FederalRegister].
Comments received after this date will be considered if it is practical to do so, but assurance of consideration cannot be given except as to comments received on or before this date.
ADDRESSES:
Mail written comments to:
the Secretary of the Commission, U.S. Nuclear Regulatory Commission, Washington, DC 20555, Attention:
l Docketing and Service Branch.
Deliver comments to:
11555 Rockville Pike, Rockville, MD, between l
7:45 a.m. and 4:15 p.m. on Federal workdays.
l Copies of regulatory analysis, the environmental assessment and finding of no significant impact, the supporting statement submitted to OMB, and comments received may be examined at:
The NRC Public Document Room, 2120 L Street,NW.(LowerLevel), Washington,DC.
l 2
~
W
y
?
l l
FOR FURTHER INFORMATION CONTACT:
M. L. Au, P.E., Office of Nuclear Regulatory Research, U.S. Nuclear Regulatory Commission, Washington, DC 20555, telephone (301)492-3749.
SUPPLEMENTARY INFORMATION:
1 Background
i As a result of the accident at Thret Mile Island, Unit 2, on March 28, 1979, the Nuclear Regulatory Commission (NRC) and others recognized a need to substantially improve the NRC's ability to acquire accurate and timely data on plant conditions during emergencies.
Before designing a system to accomplish this task, the NRC addressed several background issues dealing with its role during an accident, any changes necessary to enhance the response role to nuclear emergencies, and the information needed to support this role.
The NRC's role in the event of an emergency is primarily to monitor the licensee to ensure that appropriate recommendations are made with respect to offsite protective actions.
Other aspects of the'NRC's role include providing the licensee with technical analysis and logistic support, supporting offsite authorities (including confirming the licensee's recommendations to offsite authorities), keeping other Federal agencies and entities informed of the status of the incident, keeping the media informed of the NRC's knowledge of the status of the incident, and coordinating with other public affairs groups.
Detailed study has determined that the Commission's statutory authority provides a sufficient basis for carrying out this' defined emergency response role.-
l l
3 1
y.
To fulfill this emergency response role, the NRC requires reliable real-4 time (actual time in which a process takes place) data on four types of selected plant conditions.
These conditions are:
(1) Core and coolant system conditions -- needed to assess the extent or likelihood of core damage; (2) Conditions inside the containment building -- needed to assess the likelihood and consequence of its failure; (3) Radioactivity release rates -- needed to assess the immediacy and degree of public danger; and (4) Data from the plant's meteorological tower -- needed to assess the likely patterns of potential or actual impact on the public.
1 1
Site surveys, conducted by the NRC in 1986, have shown that data relevant to these conditions are maintained in the plant computer systems by a majority of the licensees. Currently during an emergency, data on these conditions is transmitted to the NRC Operations Center by the licensee through the Emergency Notification System (ENS) via voice communication by telephone.
In SECY-84-481, " Upgrading the NRC Operations Center's Emergency Data Acquisition Capability," dated December 26, 1984, it was noted that experience with the ENS voice-only emergency connunications link currently addressed in l
10 CFR 50.72(a) demonstrated that excessive amounts of time are needed for routine transmission of data and for verification or correction of. data that appears questionable.
Errors were also attributed to transcribing and interpreting voice-transmitted data.
Ti,;: resulted in the NRC exploring 4
y t
improved methods to receive accurate and timely information it requires to perform its role during an alert or higher emergency.
After evaluating several options, the NRC selected the Emergency Response Data System (ERDS) as the most appropriate option to supplement the ENS.
The staff conducted prototype ERDS testing with Duke Power and Commonwealth Edison reactor units.
For example, data was transmitted and beneficially used via aa ERDS prototype during the Zion Full Federal' Exercise in June 1987.
These tests demonstrated that there was great value in using electronic data transmission for obtaining a limited set of reliable, time tagged data.
With this better and more timely data, the NRC response team functioned more efficiently and their assessments were more timely. Major improvements in the ability to focus on significant factors and to predict the course of events were noted.
The questions directed from the NRC Operations Center to the licensee were focused on the overall event status and corrective actions being considered, rather than simple data requests, thereby reducing the volume of voice communications.
1 The NRC decided to implement the ERDS initially on a voluntary basis through the issuance of a generic letter while at the same time developing a rulema king. On August 21, 1989, the NRC issued Generic Letter 89-15 to request the voluntary cooperation of each nuclear power reactor licensee in implementing an ERDS program at each of its operational nuclear power units.
However, to date only about half of the operating nuclear power units have volunteered to participate in ERDS. The NRC recognizes the-importance of the ERDS in enhancing its ability to fulfill its role in the event of an emergency and has placed a high priority on the implementation of the ERDS program by all operational nuclear power units. The staff has, therefore, developed the i
l 5
v P
proposed rule that would amend Part 50 to require participation in the ERDS program and to set a definite schedule for its implementation.
Discussion 4
The ERDS would supplement the currently installed voice transmission ENS.
The system will provide the NRC Operations Center with a timely and accurate limited set of parameters from the installed onsite computer systems in the event of an emergency at a nuclear power plant.
Implementation of the ERDS would require each licensee to establish and maintain a computer information system which is designed to transmit a set of approximately 30 selected critical plant parameters.
The ERDS would be activated by the licensee upon declaration of an alert or higher emergency condition at a licensed nuclear power reactor facility. Tests with the ERDS indicate that a computer-based transmission system is far more accurate and timely than the current practice of relaying information on plant conditions via telephone voice communication.
Moreover, by automatically collecting and transmitting selected critical parameters to the NRC Operations Center, the ERDS would allow the licensee to redirect resources that now are required for voice communication of plant conditions to managing the emergency. Of course, the voice communication channel would remain available to permit needed dialogue between the licensee's
- facility and the NRC Operations Center during the emergency.
The proposed ERDS requirement would apply to all nuclear power reactor facilities except Big Rock Point and those that are permanently or indefinitely shut down. Big Rock Point is exempt because the facility has only five data points available for the ERDS program. Those units shut down for maintenance 6
y P
s or authorized only for fuel loading and low power operations are required to report under ERDS.
The ERDS would become operational during (1) emergencies at the licensee's facilities and (2) emergency training exercises if the licensee's computer system has the capability to transmit the exercise data.
The licensee would activate the ERDS to begin data transmission to the NRC Operations Center immediately after declaring an alert or a higher emergency classification.
The licensee would be required to provide the necessary software to assemble the data and an output communications port for each reactor unit in its in-plant computer system. The required emergency data would be transmitted to the NRC via NRC-furnished communication link hardware.
The acquisition and transmission of data would not require human intervention after.-the system is activated, thereby ensuring uninterrupted transmission of real-time data.
The data would be transmitted in a format compatible with the system at the NRC Operations Center.
Guidance for format compatibility with the NRC receiving system is provided in NUREG-1394.
The two main features of the ERDS are:
The software link, which will' extract and format the requisite data o
l to be transmitted to the NRC Operations Center; and The hardware link, which will connect the onsite data acquisition' o
system of the licensee with the data transmission unit supplied by the_.
4 7
l
e NRC.
In most cases, implementing ERDS can be accomplished with already installed equipment at the licensee's facility, i
The parameters to be included in the transmission are those that, to the greatest extent possible, describe the four selected plant conditions previously mentioned. The specific parameters desired by the NRC during an emergency are given in the proposed amendment to 10 CFR Part 50, Appendix E, Section VI, Paragraph 2.
The units of these parameters are pre-established for each site and will be transmitted to the NRC Operations Center without any change.
If the data for a selected plant condition parameter exists, but
(
cannot be transmitted electronically from a licensee's system, then the licensee will continue to provide that data via the existing ENS.
With regard to the capability of the current hardware at the sites to support the generation of data required as input to ERDS, approximately 5 to 10-percent of the licensee computer systems are currently running at close to 100 percent processing capability in the post-trip or post-incident environment.
Approximately 10 to 15 percent of the licensee systems are-hardware limited (i.e.,noavailableoutputportforanERDSconnectionexists).
However, in many of these cases, the licensees with hardware limitations were planning to upgrade their systems in the near future for reasons other than supporting ERDS.
Each licensee would establish and maintain an ERDS configuration control program which would ensure that the NRC is notified of any changes to the ERDS on-site hardware or sof tware. Any hardware and software changes that affect the transmitted data points identified in the ERDS Data Point Library (data 8
V base) must be reported to the NRC within 30 days after changes are completed.
Any changes that could affect the transmission format and communication protocol to the ERDS must be provided to the NRC, as soon as practicable, at least 30 days prior to the modification.
Other computer systems, such as the Nuclear Data Link (NDL) were considered; however, these would require new hardware and software as well as additional personnel for both licensees and the NRC.
Environmental Impact: Categorical Exclusion The NRC has determined that this proposed regulation is the type of action described in categorical exclusion 10 CFR 51.22(c)(3)(iii).
Therefore, neither an environmental impact statement nor an environmental assessment has been prepared for this proposed regulation.
Paperwork Reduction Act Statement This proposed rule amends information collection requirements that are subject to the Paperwork Reduction Act of 1980 (44 U.S.C. 3501 et seq.).
This rule has been submitted to the Office of Management and Budget for review and approval of the paperwork requirements.
The regulatory analysis estimates an annual per reactor level of effort of 5 days for licensee staff and 3 days for NRC staff for the maintenance of the on-site ERDS configuration control program. An integral part of this activity is the preparation of configuration control reports by the licensee and their 9
y review by the NRC.
This paperwork effort is estimated at less than one-third the overall configuration control level of effort.
Thus, the reporting burden per reactor is estimated at less than 2 days per year, and the NRC's review effort is estimated at less than 1 day per reactor year.
Send comments regarding this burden estimate or any aspect of this collection of information, including suggestions for reducing the burden, to the Information and Records Management Branch (MNBB-7714), U.S. Nuclear Regulatory Commission, Washington, DC 20555 and to the Paperwork Reduction Project (3150-0011), Office of Information and Regulatory Affairs (NE08-3019), Office of Management and Budget, Washington, DC 20503.
Regulatory Analysis The NRC has prepared a draft regulatory analysis on this proposed regulation. The analysis examines the costs and benefits of the alternatives considered by the NRC.
The draf t regulatory analysis is available for inspection in the NRC Public Document Room, 2120 L Street, NW. (Lower Level),
Washington, DC.
Single copies of the draft analysis may be obtained from M. L. Au, P.E., Office of Nuclear Regulatory Research, U.S. Nuclear Regulatory Commission, Washington, DC 20555, telephone (301) 492-3749.
The NRC requests public comment on the draft regulatory analysis.
Comments on the draft analysis may be submitted to the NRC as indicated under the ADDRESSES heading.
10
v Regulatory Flexibility Certification In accordance with the Regulatory Flexibility. Act of 1980 (5 U.S.C.
605(b)), the Commission certifies that this rule will not, if promulgated, have a significant economic impact on a substantial number of small entities. This proposed rule affects only the licensing and operation of nuclear power plants.
The companies that own these plants do not fall within the scope of the definition of "small entities" set forth in the Regulatory Flexibility Act or the Small Business Size Standards set out in regulations issued by the Small Business Administration at 13 CFR 121.
Backfit Analysis As required by 10 CFR 50.109, the Commission has completed a backfit analysis for this proposed rule.
The Commission concluded that the proposed rule will provide substantial increase in the overall protection of the public health and safety by ensuring far more accurate and timely flow of data for the NRC to fulfill its role during an alert or higher emergency. The direct and.
indirect costs estimated for the implementation of this rule are justified in view of this increased protection.
Further, the implementation and maintenance requirements of the proposed rule will have no effect on occupational radiological exposure. The backfit analysis on which this determination is based is as follows:
t Item 1:
Statement of the specific objective that the proposed backfit is designed to achieve.
1 Response: The objective of the proposed ERDS rulemaking effort is to achieve a 1
high degree of assurance that accurate real-time data is made available to the 11 t
i-NRC to evaluate critical parameters at any operating reactor facility during an alert or higher emergency.
This in turn would improve the NRC's understanding of an event and allow the NRC to perform its role more effectively and efficiently which includes: (i) monitoring the licensee to ensure that appropriate recommendations are being made with respect to offsite protective actions; (ii) providing the licensee with technical analysis and logistic support; (iii) supporting offsite authorities; (iv) keeping other Federal agencies and entities informed of the status of the incident; and (v) keeping the media informed of the NRC's knowledge of the status of the incident.
In addition, the implementation of the ERDS would enable the licensee to~
better use its time and resources to effectively and efficiently deal with the emergency. The combination of better and more timely assessments of licensee actions by the NRC and the focusing of the licensee's resources to better deal with the emergency at hand together will reduce the overall risk to the public health and safety from an emergency.
Item 2:
General description of the activity that would be required of the licensee or applicant in order to complete the backfit.
1 1
Response: All licensees or applicants would be required to install an NRC-supplied communication link, provide the sof tware necessary to format available selected critical plant condition data for NRC use, provide the necessary hardware from the in-plant computer to interface with the NRC-supplied communication link, provide support for periodic testing of the ERDS, and 1
report any configuration changes to the licensee's ERDS-related hardware and l
12 1
1
y software.
Initially, the ERDS will be tested quarterly, unless otherwise determined by NRC based on demonstrated system performance, i
Item 3:
Potential change in the risk to the public from the accidental offsite release of radioactive material.
Response: The implementation of the ERDS in all operating nuclear power reactors would provide the NRC with-more accurate and timely data to fulfill its major role during an alert or higher emergency.
The major role, as defined in the 1987 revision to NUREG-0728, is to monitor the licensee to ensure that approprieta recommendations are being made with respect to offsite protective actions. Cui rently, the NRC relies on data verbally transmitted through the Emergency Notification System (ENS) during an emergency. Although deemed adequate, this method of transmission has, on occasion, proven to be unreliable.
In addition, data collection is time consuming since various instruments are read and their indications logged on a periodic basis for verbal communication via ENS. The implementation of the ERDS would improve the reliability and timeliness of data transmission and help ensure that any i
reactor unit in distress can be suitably monitored.
Therefore, the NRC would be able to make better and more timely assessments of the licensee's actions regarding management of both emergency and protective actions. Although licensees will be required to maintain voice conmunication via the Emergency Notification System (ENS) with ERDS, the licensee resources that now are required to collect and relay data and information to the NRC will be available to deal with the emergency. The combination of better and more timely-assessments of licensee actions by the NRC, and the focusing of licensee 1
e i
13
i-resources to better deal with the emergency at hand together will reduce the j
overall risk to the public health and safety from an emergency.
Item 4:
Potential impact on radiolog'ical exposure of facility employees.
Response: The implementation of the proposed ERDS rule would have no effect on routine occupational radiological exposure and would not result in increased radiological exposure of facility employees.
Item 5:
Installation and continuing costs associated with the backfit, including the cost of facility downtime or the cost of construction delay.
Response: The cost impact of the rule was estimated to be approximately
$153,000 for one nuclear power reactor (one unit).
This figure, expressed in 1990 dollars, represents the incremental worth of installing and operating ERDS for 30 years using a 5 percent discount rate. The overall industry cost of implementing the rule for 118 nuclear power reactor units was estimated at i
approximately $18 million.
No downtime costs were considered in the cost impact estimates because the installation and operation of the ERDS should have i
no impact on the <,peration of a nuclear power plant.
Item 6:
ine potential safety impact of changes in plant or operational complexity, including the relationship to proposed and existing regulatory requirements.
1 l
Response: The proposed ERDS rule should have little or no impact on the operational complexity of the nuclear power reactor units since the required modifications to the hardware and software are minor.
The redirection in the e
y P
labor burden provided by the automatic collection and transmission of selected reactor data would increase the efficiency and effectiveness of nuclear power plant operating personnel during an emergency. The proposed rule is closely associated with Generic Letter 89-15 and complements the ENS that exists at every nuclear power reactor.
Item 7:
The estimated resource burden on the NRC associated with the proposed backfit and availability of such resources.
Response: The impact on the NRC resulting from the implementation of the proposed ERDS rule is anticipated to be a one-time cost of about $200,000 for the current population of operational / licensed nuclear reactor units.
This figure provides for initial reviews of licensees' implementation plan submittals. After implementation, the NRC cost is estimated to be approximately $4.3 million for 118 nuclear power reactor units.
This figure represents the costs for periodic testing and configuration control expressed as the present worth in 1990 dollars and uses a 5 percent discount rate over 30 years.
Item 8:
The potential impact of the differences in facility type, design, or age on the relevancy and practicality of the proposed backfit.
Response: The proposed rule is independent of the facility's type, design, or age. There are considerable variations in the instrumentation systems of the nuclear power plants, and the estimated cost impacts were based on an average value for current nuclear power plants to implement the ERDS.
There will be no differences, however, in potential impacts between the various facilities on a 15
y e
1 yearly basis.
The proposed rule does not require that licensees monitor more parameters than are presently monitored at each facility.
Item 9:
Whether the proposed backfit is interim or final and, if interim, the t
justification for imposing the proposed backfit on an interim basis.
Response: Implementation of the ERDS in accordance with the proposed rule will require that all licensees develop and submit an ERDS implementation plan to the NRC within 60 days of the publication of the final rule in the Federal Register. The implementation plan should provide a schedule which identifies the earliest possible time frame for ERDS implementation by the licensee as well as proposed alternate implementation dates.
The NRC will establish an industry wide ERDS implementation schedule which will take into account such factors as planned computer modifications and scheduled outages.
The ERDS must be implemented within 18 months of the publication of the final rule in the Federal Register.
List of Subjects in 10 CFD Part 50 Antitrust, Classified information, Criminal penalty, Fire protection, Incorporation by reference, Intergovernmental relations, Nuclear power plants and reactors, Radiation protection, Reactor siting criteria, Reporting and recordkeeping requirements.
For the reasons set out in the preamble and under the authority of the Atomic Energy Act of 1954, as amended, the Energy Reorganization Act of 1974, 16
's V
v as amended, and 5 U.S.C. 553, the NRC is proposin9 to adopt the following amendment to 10 CFR Part 50.
FART 50 - DOMESTIC LICENSING OF PRODUCTION AND UTILIZATION FACILITIES
- 1. The authority citation for Part 50 continues to read as follows:
3 AUTHORITY:
Secs. 102, 103, 104, 105, 161, 182, 183, 186, 189, 68 Stat.
536, 937, 938, 948, 953, 954, 955, 956, as amended, sec. 234, 83 Stat.1244, as amended (42U.S.C.2132,2133,2134,2135,2201,2232,2233,2236,2239,2282);
cecs. 201, as amended. 202, 206, 88 Stat. 128, as amended, 1244,1246,(42 L;.S.C. 5841, 5842, $846).
Section 50.7 also issued under Pub. L.95-601, sec. 10, 92 Stat. 2951 (42 U.S.C. 5851).
Section 50.10 also issued under secs. 101, 185, 68 Stt., 936, 955, as amended (42 U.S.C. 2131, 2235), sec. 102, Pub. L.91-190, 83 Stat. 853 (42 U.S.C. 4332).
Sections 50.13,and50.54(dd),alsoissuedundersec.108, 68 Stat. 939, as amended (42 U.S.C. 2138).
Sections 50.23, 50.35, 50.55, and 50.56alsoissuedundersec.185,68 Stat.955(42U.S.C.2235).
Sections l
50.33a, 50.55a, and Appendix Q also issued under sec. 102, Pub. L.91-190, 83 Stat. 853 (42 U.S.C. 4332).
Sections 50.34 and 50.54 also issued under sec. 204,88 Stat.1245(42U.S.C.5844) Sections 50.58, 50.91, and 50.92 also issued under Pub. L.97-415, 96 Stat. 2073 (42 U.,S.C. 2239). Section 50.78 also issued under sec.112, 68 Stat. 939 (42 U.S.C. 2152).
Sections 50.80 through 50.81 also issued under sec.184, 68 Stat. 954, as amended (42 U.S.C.
2234).
Section 50.103 also issued under sec.108, 68 Stat. 939, as amended (42 U.S.C.2138). Appendix F also issued under sec. 187, l
68 Stat.955(42U.S.C.2237).
17.
j for the purposes of sec. 223, 68 Stat. 958, as amended (42 U.S.C. 2273),
l il 50.46(a) and (b), and 50.54(c) are issued under sec.161b, 68 Stat. 948, as amended (42 U.S.C. 2201(b)); il 50.7(a), 50.10(a)-(c), 50.34(a) and (e),
50.44(a)-(c) 50.46(a) and (b), 50.47(b), 50.48(a), (c), (d), and (e),
50.49(a), 50.54(a), (1), (i)(1), (1)-(n), (p), (q), (t), (v), and (y),
50.55(f), 50.55a(a), (c)-(e), (g), and (h), 50.59(c) 50.60(a), 50.62(c),
50.64(b),and50.80(a)and(b)areissuedundersec. 1611, 68 Stat. 949, as amended (42U.S.C.2201(1));andil50.49(d),(h),and(j),50.54(w),(2),
(bb),(cc),and(dd),50.55(e),50.59(b),50.61(b),50.62(b),50.70(a),
50.71(a)-(c) and (e), 50.72(a), 50.73(a) and (b), 50.74, 50.78, and 50.90 are issuea under sec. 1610, 68 Stat. 950, as amended (42 U.S.C. 2201(o)).
PART 50 - DOMESTIC LICENSING OF PRODUCTION AND UTILIZATION FACILITIES
- 2. In i 50.72, paragraph (a)(4) is redesignated as paragraph (a)(5) and a
{
new paragraph (a)(4) is added to read as follows:
1 5 50.72 Immediate notification requirements for operating nuclear power reactors.
(a)
L (4) The licensee shall activate the Emergency Response Data System (ERDS) for any condition that requires the declaration of an emergency class of alert, site area emergency, or general emergency at the time that the NRC Operations Center is notified of the emergency class declaration.
5 Requirements for ERDS are addressed in Appendix E.
18 i
i
- 8
\\
t i
1
- 3. Appendix E is amended by adding a new Section Yl., Emergency Response Data System, to read as follows:
Appendix E - Emergency Planning and Preparedness for Production and Utilization facilities 1
VI. Emergency Response Data System
- 1. The Emergency Response Data System (ERDS) is a direct real-time electronic data link between the licensee's onsite computer system and the NRC Operations Center which provides for the automated transmission of a limited data set of selected parameters.
The ERDS supplements the existing voice transmission over the Emergency Notification System (ENS) by providing the NRC Operations Center with timely and accurate updates of a limited set of 2
parameters from the licensee's installed onsite computer system in the event of an emergency. When selected plant data are not available on the licensee's onsite computer system, retrofitting of data points is not required. The licensee shall test the ERDS periodically to verify system availability and operability. The frequency of ERDS testing will be quarterly unless otherwise set by NRC based on demonstrated system performance.
4 19
(
(
i i
i
- 2. Except for Big Rock Point and all nuclear power facilities that are shut down permanently or indefinitely, onsite hardware and sof tware shall be provided at each unit by the licensee to interface with the NRC receiving system. The hardware and software must have the following characteristics:
- a. Data points, if resident in the in-plant computer systems, must be transmitted for four selected types of plant conditions:
reactor core and coolant system conditions; reactor containment conditions; radioactivity release rates; and plant meteorological tower data. A separate data feed is required for each reactor unit.
While it is recognized that ERDS is not a safety system, it is conceivable that a licensee's ERDS interface could communicate with a safety system.
In this case, appropriate isolation devices I
would be required at these interfaces.6 The data points, identified in the following parameters will be transmitted:
(i) For pressurized water reactors (PWRs), the selected plant parameters are:
(1) Primary coolant system:
pressure, temperatures ' hot leg, cold leg, andcoreexitthermocouples),subcoolingmargin,pressurizerlevel, reactor coolantcharging/makeupflow,reactorvessellevel(whenavailable), reactor coolant flow, and reactor power; (2) Secondary coolant system:
steam generator levels and pressures, main feedwater flows, and auxiliary and emergency feedwater flows; (3) Safety injection:
high-and low-pressure safety injection flows, safety injection flows (Westinghouse), and borated water storage tank level;(4) Containment:
pressure, temperatures, hydrogen concentration, and sump levels; (5) Radiation monitoring system:
reactor coolant radioactivity, 6
See10CFR50.55a(h)ProtectionSystems.
20
7 r
containment radiation level, condenser air removal radiation level, effluent 9
radiation monitors, and process radiation monitor levels; and (6) fieteorological data:
wind speed, wind direction, and atmospheric stability.
(ii) For boiling water reactors (BWRs), the selected parameters are: (1)
Reactor coolant system:
reactor pressure, reactor vessel level, feedwater flow, and reactor power; (2) Safety injection:
reactor core isolation cooling flow, high-pressure coolant injection /high-pressure core spray flow, core spray ficw, low-pressure coolant injection flow, and condensate storage tank level; (3) Containment: drywell pressure, drywell temperatures, drywell sump levels, hydrogen and oxygen concentrations, suppression pool temperature, and suppression pool level; (4) Radiation monitoring system:
reactor coolant radioactivity level, primary containment radiation level, condenser off-gas radiation level, effluent radiation monitor, and process radiation levels; and (5)Heteorologicaldata: wind speed, wind direction, and atmospheric stability.
- b. The above selected parameter sets must be transmitted at time intervals not less than 15 seconds or more than 60 seconds,
- c. All link control and data transmission must be established in a format compatible with the NRC receiving system.7
- 3. Maintaining Emeri ency Response Data System 7
Guidance is provided in NUREG-1394 21
x t
4 containment radiation level, condenser air removal radiation level, effluent t
radiation monitors, and process radiation monitor levels; and (6) tieteorological data: wind speed, wind direction, and atmospheric stability.
(ii) For boiling water reactors (BWRs), the selected parameters are: (1)
Reactor coolant system:
reactor pressure, reactor vessel level, feedwater flow, and reactor power; (2) Safety injection:
reactor core isolation cooling flow, high-pressure coolant injection /high-pressure core spray flow, core spray ficw, low-pressure coolant injection flow, and condensate storage tank level; (3) Containment:
drywell pressure, drywell temperatures, drywell sump levels, hydrogen and oxygen concentrations, suppression pool temperature, and suppression pool level; (4) Radiation monitoring system:
reactor coolant radioactivity level, primary containment radiation level, condenser off-gas radiation level, effluent radiation monitor, and process radiation levels; and (5) Meteorological data: wind speed, wind direction, and atmospheric stability,
- b. The above selected parameter sets must be transmitted at time intervals not less than 15 seconds or more than 60 seconds,
- c. All link control and data transmission must be established in a format compatible with the NRC receiving system.
- 3. Maintaining Emergency Response Data System 7
Guidance is provided in NUREG-1394 21
- a. Any hardware or sof tware changes that affect the transmitted data points identified in the Emergency Response Data System Data Point Library (data base) must be submitted to the NRC within 30 days after changes are completed,
- b. Hardware and software changes, with the exception of data point modifications, that could affect the transmission format and computer 1
connunication protocol to the ERDS must be provided to the NRC, as soon as practicable, at least 30 days prior to the modification.
- 4. Implementing Procedures for Emergency Response Data System
- a. Each licensee shall develop and submit an ERDS implementation program plan to the NRC by [ insert a date 75 days af ter publication of the final,*ule).
To ensure compatibility with the guidance provided for the Emergency Response Data System (ERDS), the ERDS implementation prograe, plan must include, but not be limited to, information on the licensee's computer system co.' figuration (i.e., hardware and software), interface, and procedures. Applicants for an operating license must comply with Appendix E,Section V of this part.
- b. Each licensee shall complete implementation of the Emergency Response DataSystemby[insertadateeighteenmonthsaftertheeffectivedateofthe final rule) or before initial escalation to full power, whichever comes later.
l Licensees with currently operational ERDS interfaces approved under the 22
\\
'. s ' ',
0 voluntary ERDS implementation program will be considered to have met the requirements for ERDS under Appendix E, Sections VI.1, and 2 of this part.
Dated at Rockville, Maryland, this Mday of b
, 1990.
For the Nuclear Regulatory Commission.
r
(
\\
-C hamuelJ.Chil, Secretary.
8 See, NUREG-1394.
23