ML18298A166

From kanterella
Jump to navigation Jump to search
Pfm Public Meeting - Tiered Approach - 10-23-18
ML18298A166
Person / Time
Issue date: 10/23/2018
From:
Office of Nuclear Regulatory Research
To:
Raynaud P
References
Download: ML18298A166 (8)


Text

PFM Regulatory Guide Tiered Approach Idea Generation October 23, 2018 Category 2 Public Meeting

Purpose, Driver and Process

Purpose:

To discuss thoughts on tiered approach to PFM Reg Guide

  • Driver: A tired approach to the PFM RG will help focus the guidance where it is needed, thus increasing its efficiency and effectiveness
  • Process: Sharing of ideas through roundtable/brainstorming open discussions 2

Open discussion

  • No ideas are discounted or criticized
  • Use ideas in the development of new ideas
  • NRC will document all thoughts/ideas 3

Questions

  • Assuming a tiered approach is needed, what factors differentiate between tiers? Are multiple factors weighted?
  • What changes between the tiers?

4

Thoughts to Spur Discussion

  • How to determine tiering? - Tier Driver

- Code complexity/type

  • Limited random variables versus xLPR/FAVOR
  • Modified previously approved code

- Component safety impact

  • Class 1,2,3: high versus moderate energy

- Code application type

  • Reduction (one cycle or forever) in inspection versus code case use

- Code use

  • PFM as sole basis versus supporting basis
  • Generic versus plant specific 5

Thoughts to Spur Discussion

  • What are we tiering? - Tier Topic

- QA

  • Not QA coverage, but what needs to be submitted: all QA documents versus QA summary. Third party reviews?

- V&V

  • Not V&V coverage, but what needs to be submitted: final V&V report with all supporting runs versus V&V description

- Code Technical basis

  • Technical basis document versus submit code to NRC

- Uncertainty

  • Mean values versus 95th percentile

- Additional analyses

  • No additional analyses versus sensitivity analyses, deterministic analyses, etc.

6

Thoughts to Spur Discussion

  • Other considerations?

- How many tiers (drivers and topics) are needed?

- Is weighting necessary?

- Are drivers tied to certain topics?

  • Code use tied only to QA and V&V?

Drivers Topics 1 1 2 2 3 3

- How much is too much before it becomes cumbersome?

7

Open Discussion 8