Skip to main content
Skip table of contents

GGU-DOLPHIN: Analyse fenders

The program includes a database containing commercially available fenders, for which the working capacity EA and the failure load RF are given. The fender analysis first demands that the required working capacity be determined. The failure load RF of the fender is then adopted as a horizontal load and the resulting working capacity Ed determined. The sum of EA and Ed must be greater than the required working capacity.

If you select "General load cases with fenders" in the start dialog box you will initially also see the dialog box for the steel design settings compliant with EC3 (see menu item“System/Analyse” Section “Analysing several load cases in a single computation”). Following this, the almost identical dialog box for specifying the load cases is displayed. In contrast here, though, you can select a fender analysis by activating the check box at the end of each load case line.

grafik-20241024-133729.png

For fender analysis, the Req. working capacity must first be entered or determined by pressing the "Calculate working capacity" button (also see menu item “Editor 1/General load cases”). In order to optimise the analysis procedure you will see the following dialog box, in which you can delineate the fenders to be analysed, when you exit the above box:

grafik-20241024-133943.png

In the default setting, the program analyses all fenders with a working capacity EA in the specified range. However, you can also analyse a specific fender if you activate the "Use only one fender" check box and then select the required fender from the fender database provided.

Analysis begins after you exit the dialog box. The results are then initially displayed in a message box and then in the graphics and the results legend.

You can find another example with fender analysis in the "Example General load cases_Fenders.ggu_dlb" file in the program's examples folder.

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.