ML20343A192
| ML20343A192 | |
| Person / Time | |
|---|---|
| Issue date: | 08/31/2020 |
| From: | Borowski J, Michel Call, Darrell Dunn, Antonio Rigato, James Smith, Jorge Solis, Jeremy Tapp, Bernie White Division of Fuel Management |
| To: | |
| SKumar - NMSS/DFM/NARAB | |
| Shared Package | |
| ML20343A188 | List: |
| References | |
| NUREG-2216 | |
| Download: ML20343A192 (4) | |
Text
ATTACHMENT 2A COMPUTATIONAL MODELING SOFTWARE TECHNICAL REVIEW GUIDANCE Technical Review Guidance 2A.1 Computational Modeling Software Application The U.S. Nuclear Regulatory Commission (NRC) staff does not endorse the use of any specific type or code vendor of computational modeling software (CMS). Any appropriate CMS application could be used for analyses of cask or package components; however, for any CMS to demonstrate that a particular cask or package design satisfies regulatory requirements, the applicant must demonstrate adequate validation of that CMS. Descriptions of CMS validations can be contained within a given application or incorporated by reference.
Verify that the application or related documentation (such as proprietary calculation packages or benchmark reports) provides the following information:
- details of the methodology used to assemble the computational models and the theoretical basis of the program used
- a description of benchmarking against other codes or validation of the CMS against applicable published data or other technically qualified and relevant data that are appropriately documented
- standardized verification problems analyzed using the CMS, including comparison of theoretically predicted results with the results of the CMS
- release version and applicable platforms Once the information described above has been docketed, it need not be submitted with each subsequent application but can be referred to in subsequent safety analysis reports (SARs) or related documents. If an applicant changes its analysis methodology or changes the type or vendor of the CMS used, the applicant should submit either a revision of previously submitted information or include a clear explanation of the methodology changes, and their effects on the analysis in question, in subsequent application submittals.
2A.2 Modeling Techniques and Practices The staff may need to verify the modeling techniques and practices the applicants used to demonstrate adequacy of the model.
Verify that the CMS and the options the applicant used are appropriate for adequately capturing the behavior of a cask, package, or any components.
The original application should include relevant input and results files or an equivalent detailed model description and output.
2-25
2A.3 Computer Model Development Verify that the computer model used for the analysis is adequately described, either in the application or in other documentation, is geometrically representative of the cask or package design being analyzed, has addressed how material and manufacturing uncertainties might affect the analysis, has appropriate boundary conditions, and has no significant analysis errors.
Verify that the model description includes an adequate basis for the selection of parameters and components used in the analysis model (e.g., the reason a particular element type was applied in the analysis model).
Verify that models sufficiently represent cask or package geometry and that adequate justification is provided for simplifications used. Models created with CMS are often simplified to reduce computer processing time. Models can often omit geometric details or use homogenized or smeared material properties to represent complex geometry or material combinations and still retain analytic accuracy. If smeared or homogenized properties are used, verify that the applicant has provided adequate justification for this approach, as the response of the problem can be dramatically altered Verify that the applicant has discussed how manufacturing and assembly tolerances and contact resistances will affect the analyses that have been conducted, if at all, in both the structural and thermal disciplines. Verify that the applicant has described how tolerances and contact resistances are accounted for, if applicable, in the cask or package analysis models that are submitted for review.
Verify that the applicant provided a general discussion of how error, warning, or advisory messages generated by the software affect the analysis result (if applicable). When processing a computer model developed using CMS, the software will frequently provide error, warning, or advisory messages indicating a possible problem with the model that may or may not be sufficient to terminate processing. If the error or warning function has been disabled during processing, ensure that an explanation of why this is appropriate is provided.
Verify that, within the specific disciplines, the dimensions and physical units used in the models developed are clearly labeled and mutually consistent. Ensure that the fundamental units of time, mass, and length are clearly identified. All other physical units derived must be consistent with the basic units adopted. For example, if the unit of length is the millimeter (mm), time in milliseconds (ms), and mass in gram (gm), then the mechanical force should have units of Newton (N), energy in millijoule (mJ), and stress in megapascal (MPa). Verify that the input parameters are expressed in the units as assigned. If an applicant chooses to not adopt this uniformity of units, ensure that the applicant applied the appropriate conversion before processing the input into CMS. Similar assurances must be provided for the output for the analysis solution.
2A.4 Computer Model Validation Verify that the application properly documents model validation done with applicable experiments or testing and that appropriate references are provided.
For example, an analytical models ability to capture relevant model output such as g-loads and plastic deformations can be demonstrated by comparing the physical test data of a similar package that was drop tested. The test data used to validate or benchmark the analytical model 2-26
should be similar with regard to the expected package behavior of interest. For instance, a package with impact limiters should be used to benchmark a package that also has impact limiters. Plastic strain data used for validation, for instance, should come from areas of the package where such data are crucial or relevant to the performance of the package, such as the containment boundary. Other details to consider when benchmarking and validating physical data include whether the package is bolted or welded, and whether the response will be dominated primarily by a quasi-static, wave, or impulse-type response. The data source should be readily available or included in the application and describe all the assumptions and simplifications made during physical testing so that the staff can weigh its relevance to the design of interest.
2A.5 Justification of Bounding Conditions/Scenario for Model Analysis The applicant must determine the most damaging orientation and worst-case conditions for a given design and document how the analytic model was configured for the scenario. Verify that the applicant provided sufficient justification for selecting the most damaging orientation and worst-case conditions.
2A.6 Description of Boundary Conditions and Assumptions Verify, as necessary, that the textual description included in the application or other documents addresses boundary conditions such as an unyielding surface in a drop scenario. The textual description should also include justifications and bases for such items. Ensure appropriate material (temperature dependent) properties are used.
2A.7 Description of Model Assembly Verify that the application lists the types of elements used in the model along with the corresponding materials or components in which they are used in the analysis model. The application should present the elements and materials associated with specific components of the analysis model to enable a quick assessment.
Verify that the applicant provided a sufficient explanation of the logic behind the creation of each specific computer model (such as the mesh) so that effective confirmatory calculations can be performed.
Input files should be provided for the models used in the analysis. If input files are not provided or do not adequately describe model assembly, ensure that the applicant has provided in the appropriate application sections or related documents an adequate explanation of how computer models were assembled using the CMS.
2A.8 Loads, Time Steps, and Impact Analyses Verify that the applicant has clearly explained the loads, load combinations, and, if used by the analytical code, the load steps used in the computer model. Evaluate all loads, how they are placed on the computer models, load combinations, and, if used, the time steps applied in the analysis.
Verify that the time steps specified for the solution of the analysis are sufficiently small to accurately capture the behavior of the structures, systems, or components being modeled.
2-27
For impact analyses using software such as LS-DYNA, examine the output files for hour-glassing energy in each part of the system, in addition to the package as a whole. Verify that impact analyses output is realistic. If the parts in a model contact each other, they should exhibit deformation and penetration as appropriate. Disassemble the model by component and examine them for breaches or other unseen damage. For instance, components can be perforated, but this damage may be hidden from view by other components in the model.
2A.9 Sensitivity Studies Verify that the discussion of the general development of the computer model covers sensitivity studies, with relevant references to examples included in the application or related documents.
Verify that the applicant has completed sensitivity studies for relevant CMS modeling parameters. This includes element type and mesh density, load-step size, interfacing gaps or contact friction, material models and model parameters selection, and property interpolation, if applicable. For example, a mesh sensitivity study should be conducted not only for mesh density but also for mesh density and refinement in areas of thermal or structural concern or where performance of the material is crucial, such as seal areas and lid bolts. A mesh sensitivity is also needed to make sure the analysis results are mesh independent.
Verify that the application or related documentation clearly describes the results of applicable sensitivity studies and that the sensitivity studies can be independently verified, if necessary.
Verify that the applicants documentation includes at least a brief discussion of the different models used in its mesh sensitivity studies.
2A.10 Results of the Analysis Verify that the application or related documents includes all relevant results (tabular and computer plots) for applicable load cases and load combinations evaluated for design code compliance, and that the tables and plots clearly identify all governing results (stresses, deformation).
Verify that results are consistent throughout the application, and that the correct results are used in calculations of other cask or package performance.
2-28