Code checks

Standards organisations such as API, DNV, and BSI lay down design standards, or codes, some of which are relevant to analysis work which may be carried out in OrcaFlex. To facilitate your checking for compliance with these codes, OrcaFlex implements a number of code checks, each of which addresses a particular standard.

A code check consists of a set of input data and a number of named results. You would usually define the input values by consulting the corresponding code for guidance; having done so, and run your OrcaFlex simulation, the relevant output variables will be available for selection and reporting, at which point it should be clear whether or not that particular analysis meets the code requirements.

Note that the code check input data do not influence the course of a simulation. You can, therefore, edit these data after a simulation has completed without having to re-run the simulation.

The code checks data form gathers together all input data related to code checks. The following code checks are implemented:

• API RP 2RD.
• API STD 2RD.
• API RP 1111.
• DNV ST F101.
• DNV OS F201.
• PD 8010.

The data form has a number of different pages – broadly speaking, one for each code check. The exception to this is the DNV functional load page, which contains data shared between the DNV ST F101 and F201 code checks. Some of the code checks require a large amount of input data; data for these may in turn span multiple pages.

The data fall into two main categories: model-wide and per line type. Model-wide values each have only a single value which applies thoughout, whereas per line type data are each associated with a specific line type and may take a different value for each line type in the model.

To automate modifications to code check data, please refer to

• Batch processing: Examples of setting data.
• Text data files: Examples of setting data.