ML090650275
| ML090650275 | |
| Person / Time | |
|---|---|
| Site: | Nuclear Energy Institute, Boiling Water Reactor Owners Group, PROJ0669, PROJ0700, PROJ0694 |
| Issue date: | 03/12/2009 |
| From: | Schoppman M Nuclear Energy Institute |
| To: | NRC/NRR/DPR/PSPB |
| Mensah, T M, NRR/DPR, 415-3610 | |
| Shared Package | |
| ML090680284 | List: |
| References | |
| TAC MD4832 | |
| Download: ML090650275 (5) | |
Text
NRC/NEI Topical Report Meeting February 19, 2009 NEI Handout CONTENTS NEAR-TERM PRIORITIES
- 1.
LIC-500 -----------------------------------------------------------------------------
Pg 2 A.
Limitations & Conditions B.
Additional NEI Comments C.
Additional NEI Markup
- 2.
PRIORITIZATION------------------------------------------------------------------
Pg 4 A.
Pipeline Estimates B.
Prioritization Factors
- 3.
METRICS----------------------------------------------------------------------------
Pg 4 A.
Pilot Plant Applications
- 4.
CHAMPION--------------------------------------------------------------------------
Pg 4 A.
Comment on NRC Flow Chart FUTURE TOPICS
- 1.
COMMUNICATIONS PLAN--------------------------------------------------------- Pg 5 A.
Integrating Topical Reports and Licensing Actions B.
Pipeline Estimates
- 2.
PILOT PLANT APPLICATIONS----------------------------------------------------- Pg 5 A.
Identify Initial Pilots
- 3.
FORMAT & CONTENT ISSUES---------------------------------------------------- Pg 5 A.
Standard Template B.
NEI 06-02, License Amendment Request Guideline
- 4.
FUTURE REVISIONS OF LIC-500------------------------------------------------- Pg 5
NRC/NEI Topical Report Meeting February 19, 2009 NEI Handout NEAR-TERM PRIORITIES
- 1.
LIC-500 A.
Limitations & Conditions Discussion item at todays meeting.
B.
Additional NEI Comments Build periodic updates of pipeline estimates into LIC-500.
Move the notification associated with 4.2.7 (TB Transmits SE to PSPB) sooner in the process (for example, as part of 4.2.6 on RAIs) so that the applicant is aware of pending limitations and conditions.
4.1.3 (TRs and Related Plant-specific Licensing Actions) - Update per current NRC position on pilot LARs.
4.2 (TR Review Process Steps), Table, after item 2 and before item 6 - Offer an option, or consider drafting a new section, for an initial (early) post-submittal meeting. This would underscore the following benefits:
3/4 Benefits both the NRC staff and applicants.
3/4 The TR is available for discussion at that point.
3/4 Different from pre-submittal meetings because there is a greater likelihood of participation by the technical reviewers that will conduct the review.
3/4 Opportunity for NRC staff to meet with the TR applicant and preparers.
3/4 Opportunity for applicant to introduce the TR and explain the strategy and the methods used.
3/4 Opportunity to exchange information that could preclude the need for RAIs 3/4 The dialogue would support the NRC acceptance review process.
4.2, Table, Item 4 - Share Green Sheets with NEI Topical Report Team.
4.2, Table, Item 6 - 45 days or 60 days?
4.2, Table, item 13 - Ten days is not sufficient to resolve proprietary concerns.
4.2.1 (Pre-submittal Meeting) - Add text to describe the objectives and attributes of the pre-submittal meeting.
4.2.3 (Work Plan) - Is there an internal NRC procedure or process for selecting topics for ACRS briefings?
4.2.5 (Proprietary Determination) - Has the NRC staff identified a time frame for resolving proprietary disagreements?
4.2.10 (Applicant Submits Approved Version of TR), 1st paragraph, 1st sentence -
Suggest ending the sentence after the word date.
4.2.10 - Status of last paragraph?
5.1 (TB Branch Chiefs) - Administrative procedural changes to encourage the transfer of working files from a departing reviewer to an incoming reviewer are logical steps and should not be deferred pending broader agency action on knowledge management.
NRC/NEI Topical Report Meeting February 19, 2009 NEI Handout C.
Additional NEI Markup Add paragraphs to Section 2 (OBJECTIVE)
To achieve the value that topical reports offer, it should be the objective of the review to approve the maximum level of requested features and scope of application requested to the extent that the topical report content justifies the features to be in conformance with the NRCs rules, regulations and Commission policy statements and meets applicable Regulatory Guides or justifies an alternate approach.
While adding conditions and limitations to the Safety Evaluation may in some cases be necessary, NRC staff should realize that it is preferable to allow the TR applicant the timely opportunity to provide the justification that can avoid those restraints. Conditions and limitations amplify the effort that is needed by both licensee and NRC on subsequent individual plant applications that reference the TR and also will likely diminish the advantages of the standardization that could have been achieved from a TR that is not conditioned.
Edit the NOTE in Section 4.1.1 (Accepting a TR for Review)
NOTE: Technical reports submitted for resolution of industry issues or in support of plant-specific license amendment applicationsto support an application for design certification or plant-specific licensing action are not defined as TRs under this program. A technical report is typically submitted by a vendor. or OG to support an application for a design certification. The information in the technical report is subsequently captured in an amended application (perhaps by reference); however the NRC's evaluation of that technical report is included in the safety evaluation report for the design certification application (a separate SE is not provided for each technical report). Owners Groups may submit technical reports for NRC staff information that address industry issues.
4.2.11 Applicant Submits Revision(s) or Supplement(s) To the Approved Version of TR Add the paragraph:
Some revisions to topical reports are not submitted to NRC for review and approval when the applicant concludes that the implementation of the revision will not require a request for licensing action in accordance with 10 CFR 50.59, 10 CFR 50.54, or 10 CFR 52. The applicant may submit the revision for NRC information. In those cases, licensees and implementers of the topical report revision are responsible for assuring the changes of the revised topical report do not require NRC review and approval.
NRC/NEI Topical Report Meeting February 19, 2009 NEI Handout
- 2.
PRIORITIZATION A.
Pipeline Estimates (Replies to 12/23/08 NRC letters)
Discussion item.
B.
Prioritization Factors IMPORTANCE 3/4 Safety 3/4 Risk 3/4 Reliability 3/4 Availability 3/4 Dose reduction 3/4 Issue resolution 3/4 Event prevention 3/4 Shutdown prevention IMPLEMENTATION 3/4 Standardization 3/4 Broad applicability 3/4 High adoption RESOURCES 3/4 Availability 3/4 Burden reduction 3/4 Cost factors (sunk/future)
- 3.
METRICS A.
Pilot Plant Applications Discussion item.
- 4.
CHAMPION A.
Comment on NRC Flow Chart Add language to clarify that these instructions apply to external coordination with industry groups as well as internal coordination of NRR branches.
NRC/NEI Topical Report Meeting February 19, 2009 NEI Handout FUTURE TOPICS
- 1.
COMMUNICATIONS PLAN A.
Integrating Topical Reports and Licensing Actions Learn from Pilots Refine Pipeline estimates Capture LIC-500 lessons learned & good practices Metric adjustments B.
Pipeline Estimates Protocol for continuing estimates
- 2.
PILOT PLANT APPLICATIONS A.
Identify Initial Pilot(s)
- 3.
FORMAT & CONTENT ISSUES A.
Standard Template B.
NEI 06-02, License Amendment Request Guidelines
- 4.
FUTURE REVISIONS OF LIC-500