ML19331A726
| ML19331A726 | |
| Person / Time | |
|---|---|
| Site: | NuScale |
| Issue date: | 11/26/2019 |
| From: | - No Known Affiliation |
| To: | NRC/NRR/DNRL |
| References | |
| Download: ML19331A726 (4) | |
Text
From:
Joergensen, Nadja <njoergensen@nuscalepower.com>
Sent:
Tuesday, November 26, 2019 12:34 PM To:
Chowdhury, Prosanta
Subject:
[External_Sender] IBR Flow Chart Attachments:
IBR Flow Chart 11-26-2019.pdf
- Prosanta, Please see non-proprietary IBR flow chart attached.
Let me know if you have any questions.
Thank you, Nadja Nadja Joergensen Licensing Project Manager email: njoergensen@nuscalepower.com web: www.nuscalepower.com Office: 541.452.7338 Cell: 913.709.6300 The contents of this email are intended only for the person to whom it is addressed. If you received it by mistake, please inform me by reply email and then delete the message and any attachments. This email may contain proprietary, confidential and/or privileged material, which doesn't change if it is sent to an unintended recipient. Unless you have my consent, please do not copy, forward, or reveal the contents of this email to anyone.
Hearing Identifier:
NuScale_SMR_DC_Docs_Public Email Number:
34 Mail Envelope Properties (7ca2f588102b48cdae3a86597574e485)
Subject:
[External_Sender] IBR Flow Chart Sent Date:
11/26/2019 12:34:08 PM Received Date:
11/26/2019 12:34:32 PM From:
Joergensen, Nadja Created By:
njoergensen@nuscalepower.com Recipients:
"Chowdhury, Prosanta" <Prosanta.Chowdhury@nrc.gov>
Tracking Status: None Post Office:
nuscalepower.com Files Size Date & Time MESSAGE 818 11/26/2019 12:34:32 PM image001.png 11822 IBR Flow Chart 11-26-2019.pdf 618024 Options Priority:
Normal Return Notification:
No Reply Requested:
No Sensitivity:
Normal Expiration Date:
Is it a SUNSI report?
No Proprietary reports that do not have information needed to support a regulatory requirement or do not provide forward-looking requirements.
Do special circumstances apply?
Yes No Yes Is the information "intended as a requirement" sseverable from the remainder of report?
x
e.g., The report includes both a description of our methodology as well as forward-looking requirements, which can be reasonably distinguished.
Yes No Remove from IBR list. Report may be a reference only Further evaluate whether IBR allowable and preferred.
Yes No No Yes The report is IBR (DC rule will specify that only portions intended as a requirement are requirements and matters resolved)
Make necessary FSAR changes, if needed, and remove report from IBR list. Report may be reference only.
No Yes Remove from IBR list. Report may be a reference only Further evaluate
whether IBR allowable and preferred.
No Yes There are proprietary requirements-The report is IBR (DC rule will specify that only portions intended as a requirement are requirements and matters resolved)
There are proprietary requirements-The report is IBR (DC rule will specify that only portions intended as a requirement are requirements and matters resolved)
Non-proprietary reports that support FSAR information and should not be IBR, unless special circumstances apply (e.g.,
QAPD). Do special circumstances apply?
Are the portions that are intended as requirements nonproprietary, or can they be made nonproprietary Is it ppractical to capture the information "intended as a requirement" in FSAR directly (or is it already)
Is any information in the report "iintended as a requirement" for a COLA referencingD
design certification?
x
The report includes information that is necessary to support a required safety finding, AND x
Forward-looking: the report that is IBR provides prescriptive information (e.g.,
methodology, design description) that is necessary for a COL applicant to comply with.
x
Examples of reports used as references but are not IBR:
-,IDUHIHUHQFHGUHSRUWSURYLGHVDGGLWLRQDOLQIRUPDWLRQWRVXSSRUWWKH 6WDII VUHYLHZEXWWKH6WDII VVDIHW\\ILQGLQJLV RUFRXOGEH EDVHGRQWKH
)6$5LQIRUPDWLRQRQO\\WKHUHSRUWLVQRWQHFHVVDU\\WRVXSSRUWWKHVDIHW\\
ILQGLQJDQGLVQRWFRQVLGHUHG,%5
-If a report GHVFULEHVWKH methodology for developing a designparameter or feature, but the output (parameter or feature) is captured in the FSAR, it is not necessary for a COLA to comply with the report. Rather, the design described in the COLA simply needs to comply with the FSAR information.
Incorporated By Reference (IBR) Flow Chart November 26, 2019