ML23069A241

From kanterella
Jump to navigation Jump to search

Attachment 12: HI-STORM 100 Amendment 19 CoC, Appendix D Reorganization Evaluation Form
ML23069A241
Person / Time
Site: Holtec
Issue date: 03/10/2023
From:
Holtec
To:
Office of Nuclear Material Safety and Safeguards
Shared Package
ML23069A227 List:
References
EPID L-2022-LLA-0028, CoC No. 1014, CAC 001028, 5014959
Download: ML23069A241 (1)


Text

CoC Condition/Technical Specification Evaluation Form - CoC original Appendix D

CoC Condition/TS Identifier: ___ D-Table 3-1_______

  • All LCOs also require an Applicability, Condition(s), Required Action(s), Completion Time(s),

Surveillance Requirement(s), and Frequency(ies). Refer to NUREG -1745 for additional guidance.

    • In performing the risk insight evaluation above, the evaluator should think about subsequent changes to a relocated CoC requirement. Specifically, ask the question what is the likelihood and worst possible consequences of a future change to this requirement in the less conservative direction?

Requirement Appendix D Table 3-1: List of ASME Code Alternatives for HI-STORM Multi-Purpose Canisters (MPCs)

CoC Body Section I. Technology No Certified Design Section II. Design Features No Appendix C - Inspections, Tests, and Yes Evaluations (see evaluation summary below)

Section 1 Definitions, Use No and Application Section 2 Approved A1 No Contents (Selection A2 No Criteria) A3 No Appendix D. Section 3 Limiting L1 No Technical Conditions for L2 No Specifications Operation (LCOs)* L3 No and Surveillance Requirements (SRs)

(Selection Criteria)

Section 4 Administrative No Controls A significant increase in No/A the probability or consequences of an accident previously Risk Insight**: evaluated in the cask Will removing FSAR?

this The possibility of a new or No/A requirement different kind of accident from the CoC/TS being created compared result in to those previously evaluated in the FSAR?

A Significant reduction in No/A the margin of safety for ISFSI or cask operation?

Evaluation Summary While this Table could potentially be removed without any risk impact, the removal could increase the need for cumbersome alternative code use

Page 43 of 84