Code Checking Best Practice

<< Click to Display Table of Contents >>

Navigation:  PipeLay > Software Components & Operation > Analysis & Postprocessing > Analysis Component > Code Checking Tab >

Code Checking Best Practice

Previous page Next page

1.Defaults are provided for many of the code checking inputs and while they are deemed sufficient for general installation analysis you should always check their validity for your particular application. Please note that in the case of section diameter and wall thickness inputs if these are not specified by the user PipeLay will just use the corresponding element properties from the analysis by default.

2.In the case of DNV-OS-F101 there are both functional and environmental parts to the corresponding buckling checks. Functional loads are static in nature and while you can nominate a particular static installation stage to provide the functional loads by default PipeLay will automatically extract functional loads itself from the start of all the environmental stages (before environmental loads are introduced/ramped up), thus making it easier to assess multi-step operations where the pipeline static catenary is changing throughout (e.g. during start-up).

3.There is a transient period input for both types of code checking and this allows you to exclude a certain percentage of the dynamic analysis duration from the calculation of the buckling checks. This percentage input should typically be set to cover the ramp time as during this period there may be spurious effects or noise that could provide invalid checks.

4.If you wish to request code checking for all pipe sections in a model then select the ALL option in the corresponding Section Properties dialog. This quickly includes all sections without having to select them individually.