DNV SOFTWARE PRODUCTS AND DEVELOPMENT

User Manual

ORBIT Offshore V2.2

Issue Log
Revisi
on No

Issue Date

Prepared by

Reviewed by

Approved
by

01
02
03

27-July-2000
29 July 2001
28 August 2002

P. Mathieson
G. Korneliussen
P Mathieson

J. Edwards
P. Topalis
P.
Topalis,
G.
Korneliussen & F.
Saint Victor

S. Angelsen
P. Topalis
P. Topalis

Comments
ORBIT Offshore 2.0, First Issue
ORBIT Offshore 2.1, Revision
ORBIT Offshore 2.2, Revision

Revision No: 03

DET NORSKE VERITAS

28 Aug. 02

User Manual
ORBIT Offshore V2.2

DET NORSKE VERITAS

Page 2 of 77
Revision 03

28 Aug. 02

User Manual
ORBIT Offshore V2.2

Page 3 of 77
Revision 03

Table of Contents
1.

INTRODUCTION ..............................................................................................................................................6
1.1
1.2

INTRODUCTION TO ORBIT OFFSHORE USERS GUIDE ......................................................................................6

INTRODUCTION TO ORBIT OFFSHORE ............................................................................................................6

2.

INSTALLATION AND LICENSING................................................................................................................8

3.

WORKING WITH ORBIT OFFSHORE ..........................................................................................................9

3.1
3.2
3.3
3.4
3.5
3.6
3.7

4.

INTRODUCTION ..............................................................................................................................................9
DATA INTEGRITY ...........................................................................................................................................9
DOCUMENTATION ..........................................................................................................................................9
WORKING PROCESS OVERVIEW .....................................................................................................................10
QRA: EXISTING DOCUMENT OR TO BE CALCULATED BY ORBIT ...................................................................10
POF MODELLING .........................................................................................................................................10
MENUS AND TOOLBARS ...............................................................................................................................11

LOGGING ON, CREATING AND MANAGING PROJECT FILES ............................................................12

4.1
LOGGING ON ...............................................................................................................................................12
4.2
PROJECT FILE MANAGEMENT .......................................................................................................................12
4.2.1
Opening an existing file.......................................................................................................................12
4.2.2
Selecting a new project file name.........................................................................................................13
4.3
MASTER DATABASE ....................................................................................................................................13

5.

EXECUTE THE PROJECT ............................................................................................................................14

5.1
WORKING PROCESS .....................................................................................................................................14
5.2
SCREENING .................................................................................................................................................15
5.2.1
Create a new Record Sheet..................................................................................................................15
5.2.2
Screening - Information.......................................................................................................................16
5.2.3
Screening Probability of failure evaluation .......................................................................................16
5.2.4
Screening Consequence of failure evaluation ....................................................................................16
5.2.5
Screening Risk Evaluation ................................................................................................................16
5.2.6
Screening Reporting .........................................................................................................................16
5.3
DETAILED ANALYSIS....................................................................................................................................17
5.3.1
The Parts table....................................................................................................................................17
5.3.2
Data requirement for models ...............................................................................................................19
5.3.3
Degradation mechanisms ....................................................................................................................21
5.3.4
Objects table .......................................................................................................................................23
5.3.5
Area table ...........................................................................................................................................24
5.3.6
Segments table ....................................................................................................................................25
5.4
RUNNING THE ANALYSIS ..............................................................................................................................27
5.4.1
Probability of failure for parts.............................................................................................................27
5.4.2
Consequence of failure for Parts .........................................................................................................27
5.4.3
Risk calculation for Parts ....................................................................................................................27
5.4.4
Time to Risk Limit ...............................................................................................................................27
5.4.5
Inspection Plans..................................................................................................................................27
5.4.6
Calculate All .......................................................................................................................................28
5.4.7
Consequence of failure analysis...........................................................................................................28
5.4.8
Consequence Analysis using External QRA..........................................................................................29
5.4.9
Individual Part analysis.......................................................................................................................30
5.4.10 Individual Object Analysis...................................................................................................................31

6.

REPORTING ...................................................................................................................................................32

7.

DATABASE MANAGEMENT, TOOLS & VIEWS .......................................................................................34

7.1
DATABASE MANAGEMENT ...........................................................................................................................34
7.1.1
ORBIT Project ....................................................................................................................................34
7.1.2
Multiple Users Entries.........................................................................................................................34

DET NORSKE VERITAS

28 Aug. 02

User Manual
ORBIT Offshore V2.2

Page 4 of 77
Revision 03

7.1.3
Backing Up The Data ..........................................................................................................................34
7.1.4
Saving Data During A Work Session....................................................................................................34
7.1.5
Buffered Mode ....................................................................................................................................34
7.1.6
A Warning: Do Not Tamper With The Database File. ..........................................................................35
7.1.7
Master database..................................................................................................................................35
7.2
DATA LOADING AND DATA ENTRY ..............................................................................................................35
7.2.1
Data available electronically...............................................................................................................35
7.2.2
Data available in paper form...............................................................................................................36
7.3
TOOLS.........................................................................................................................................................36
7.3.1
Info .....................................................................................................................................................36
7.3.2
Details ................................................................................................................................................37
7.3.3
Set manual rates and PoF....................................................................................................................37
7.3.4
Screening data exchange .....................................................................................................................37
7.3.5
Update from Group Data ....................................................................................................................37
7.3.6
Source Materials.................................................................................................................................38
7.3.7
Source Product Service .......................................................................................................................38
7.3.8
Risk analysis for Segments...................................................................................................................38
7.3.9
Allocate and Calculate All...................................................................................................................38
7.3.10 Repairing and Compacting the Database.............................................................................................39
7.3.11 Options ...............................................................................................................................................39
7.4
VIEWS AND FILTERS ....................................................................................................................................39
7.4.1
View Fields .........................................................................................................................................39
7.4.2
Filter ..................................................................................................................................................40
7.4.3
Search and Replace.............................................................................................................................40
7.4.4
Edit Copy, Paste...............................................................................................................................41
7.4.5
Sort.....................................................................................................................................................41
8.

CONFIGURATION .........................................................................................................................................42
8.1
INTRODUCTION ............................................................................................................................................42
8.2
WHY CONFIGURATION?................................................................................................................................42
8.3
DESCRIPTION OF BACKGROUND TABLES....................................................................................................42
8.3.1
Fixed values for tables.........................................................................................................................42
8.3.2
Installation..........................................................................................................................................43
8.4
PROBABILITY OF FAILURE TABLES................................................................................................................44
8.4.1
Insulation Types ..................................................................................................................................44
8.4.2
Coating Types .....................................................................................................................................45
8.4.3
Pipe classes (Optional)........................................................................................................................47
8.4.4
Functions (Optional) ...........................................................................................................................48
8.4.5
Product Service Codes ........................................................................................................................49
8.4.6
Materials ............................................................................................................................................51
8.4.7
Systems ...............................................................................................................................................52
8.4.8
Corrosion groups ................................................................................................................................53
8.5
CONSEQUENCE OF FAILURE TABLES ..............................................................................................................54
8.5.1
Repair categories ................................................................................................................................54
8.5.2
Repair category properties ..................................................................................................................55
8.5.3
Production loss profiles.......................................................................................................................56
8.5.4
Production loss profile properties........................................................................................................57
8.5.5
Leak sizes............................................................................................................................................59
8.5.6
Extents ................................................................................................................................................60
8.5.7
Segment extents...................................................................................................................................61
8.5.8
Segment Leak Sizes .............................................................................................................................62
8.5.9
Segment Leak Size Extents...................................................................................................................63
8.6
INSPECTION PLANNING ................................................................................................................................64
8.6.1
Inspection tasks...................................................................................................................................64
8.6.2
Inspection Effectiveness.......................................................................................................................65
8.6.3
PoD Curves ........................................................................................................................................66
8.7
MATRIX DEFINITION ....................................................................................................................................67
8.7.1
Risk Matrix Design..............................................................................................................................67
8.7.2
Probability categories .........................................................................................................................68
8.7.3
Consequence categories ......................................................................................................................69

DET NORSKE VERITAS

28 Aug. 02

User Manual
ORBIT Offshore V2.2

Page 5 of 77
Revision 03

8.7.4
Risk categories....................................................................................................................................70
8.7.5
Risk Matrix definition..........................................................................................................................71
8.8
OTHER DEFINITIONS ....................................................................................................................................72
8.8.1
Hole sizes............................................................................................................................................72
8.8.2
Status definitions (Optional) ................................................................................................................73
8.9
PROTECTED DATA .......................................................................................................................................74
8.9.1
DNV Materials....................................................................................................................................74
8.9.2
DNV Product Services.........................................................................................................................74
8.9.3
Object Types .......................................................................................................................................74
8.9.4
Degradation........................................................................................................................................74
8.9.5
Probability..........................................................................................................................................75
8.9.6
Configure Report ................................................................................................................................75
9.

TROUBLESHOOTING ...................................................................................................................................76
9.1
9.2

10.

PROBABILITY OF FAILURE = 1.00..................................................................................................................76

CURSOR REMAINS AS HOURGLASS ................................................................................................................76
REFERENCES .............................................................................................................................................77

DET NORSKE VERITAS

28 Aug. 02

User Manual
ORBIT Offshore V2.2

Page 6 of 77
Revision 03

1. INTRODUCTION
1.1 Introduction to ORBIT Offshore Users Guide
This document describes how to use the DNV software package ORBIT Offshore for creation and
modification of risk-based inspection plans for offshore topsides pressure systems. It is assumed
that the operator is familiar with MS Windows operation and terminology, and so this is not
covered in this document.
The Users Guide provides an introduction to the database tables, identifying the information
required to be inserted. It does not help with the sourcing of that information; for that, the Working
Procedures document should be consulted. In addition, there is a comprehensive Help available as
part of the software, and the training documentation can also be consulted for theory.
The philosophy used in developing ORBIT Offshore was that the software should automate the
calculation of risk and the inspection plan without replacing engineering judgement. It is therefore
essential that competent personnel evaluate the data required for the program, and consider the
results carefully in the light of the inputs and their experience. At all times, care should be taken to
avoid the automatic belief that the computer is always right, as the results are only as good as the
input data, and the assumptions made in generating that data.
Additionally, it is recognised that all the required data is not available in the necessary precision at
the time of carrying out RBI; it may be expensive to search for the data, or visit the platform to
measure it, especially if the result is a low risk when the RBI is complete. To try to avoid this,
ORBIT Offshore is designed with a multi-stage data fallback, such that where the required data is
missing, wherever possible a more conservative assumption is automatically made for example,
use the design pressure values if the operating values are not given.
The sequence of menu selections used to access tables and functions are described in this manual
thus: Data TechnicalInsulation Types. This shows the sequence of menu choices to be
selected.

1.2 Introduction to ORBIT Offshore

DNV have developed RBI methods and sophisticated software for carrying out RBI for the entire
offshore installation jackets, FPSOs, process and utility systems, pipelines and risers, leading to a
risk-based, cost-optimised inspection plan. The ORBIT Offshore package deals specifically with
inspection planning for offshore topsides pressure systems.
Software tool for Inspection Planning
DNVs ORBIT Offshore software helps you carry out risk calculations, and outputs a detailed
inspection plan. Inspection techniques are selected based on their cost-effectiveness, defined as the
greatest risk reduction per cost of inspection. Manual adjustment of the plan, to account for
scheduling of inspection to fit other platform activities can be made, and the effects on risk
recalculated. This allows the user to stay in control

DET NORSKE VERITAS

28 Aug. 02

User Manual
ORBIT Offshore V2.2

Page 7 of 77
Revision 03

Limit the Risk, Limit the Cost

ORBIT Offshore directly addresses the Client-specified acceptance limits for safety and Economic
Risk, and using the user-selected inspection methods calculates the cheapest inspection plan that
will keep the risk below these acceptance levels
Ease of implementation
ORBIT Offshore can read from most inspection management databases, and output the final
inspection plan back to the database, thereby minimising data handling.
ORBIT Offshore is easy to use, with form or spreadsheet views for data handling, graphical and
numerical outputs for results, and can carry out sensitivity and what-if studies. Reports can be
created with a management or a technical focus.
Installation-specific results
For installations where a service history is available, ORBIT Offshore can use the inspection
results already taken to adjust the risk levels according to actual findings, and revise the inspection
plan accordingly.
ORBIT Offshore can account for changes in the price of oil & gas, so that the inspection
schedule can be changed to reflect the change in economic risk as these prices fluctuate.
ORBIT Offshore will account for the installation process design and layout, as well as
maintenance and repair strategies when calculating the potential cost of lost production and
downtime
ORBIT Offshore allows detailed sensitivity and what-if calculations to be made to test the
effects of remedial actions before they are implemented
Results of inspection optimisation
ORBIT Offshore reports the following to allow focus where risk lies as well as detailed inspection
planning and scheduling.
Risk distribution by module, degradation mechanism, equipment type, corrosion group, process
or utility system, ESD segment
Effects of inspection on risk within the inspection planning period, shown as matrices
Contribution of safety and economic risk to the total risk
Detailed summary of results by system
Inspection frame program, giving what to inspect and when for each inspection group
Deterministic results can also be given, such as remaining life.

DET NORSKE VERITAS

28 Aug. 02

User Manual
ORBIT Offshore V2.2

Page 8 of 77
Revision 03

2. INSTALLATION AND LICENSING

An installation CD is supplied which contains the following:
The ORBIT Offshore installation files
RMS License utility 1.3.3 or later
ORBIT Offshore documentation
Word reader (for viewing the Release Note if the computer does not have Word installed)
Adobe Acrobat Reader (for viewing the Users Manual)
The first step is to install ORBIT by running Setup.exe in the ORBITOffshore directory. The
second step is to install the RMS license utility (if it has not already been installed). This may be
selected automatically at the end of the ORBIT installation or separately after ORBIT by running
Setup.exe in the DNV RMS License Utility directory. Finally you will need to run the License Utility
and enter a trigger code obtainable from DNV Software either in London (+44 20 77166545) or in
Houston (+1 281 721 6802) or in Kuala Lumpur (+603 2050 2973)
Follow these instructions to install ORBIT Offshore:
1. Load the CD into the drive.
2. Choose the directory you want ORBIT Offshore installed in. If this directory does not exist, the
install shield program will create it. After installation, ORBIT Offshore can be run from the
Start ProgramsORBIT Offshore menu or by creating a shortcut on your desktop to
ORBITOffshore.exe in the ORBIT Offshore installation folder.
Also installed with ORBIT Offshore is the DNV Licensing utility. This requires the owner of
the software to register with DNV, to prevent unauthorised copying and distribution of ORBIT
Offshore. Before attempting to run ORBIT Offshore for the first time, you will need to follow
the instructions below. The licence utility interrogates the PC to generate a unique encrypted
code based on the system time, date and BIOS and which will be different each time you run the
utility. This is then used by DNV to unlock the software, and so it is essential that the sequence
below is run without cancelling.
3. Follow the menu sequence StartProgramsRisk Management Licence Utility Licence
Utility (Local)
4. The utility will ask which software you want a licence for; select the radio button for ORBIT
Offshore.
5. With Software security selected, click on Add New Licence button. This will give you a
Code Entry Number and Computer ID number. These should be given to your nearest DNV
Risk Management Software office (London or Houston) by telephoning the appropriate number
above. They will respond with a number that should be entered in the space marked Enter
Code. Save and exit. Do not quit the telephone call.
6. Run ORBIT Offshore to test the licence utility before quitting the telephone call.
The licence is valid for the period given in the contract with DNV. Upon expiry, the sequence 3
through 6 above should be followed to obtain the new licence.
On successful completion of the licensing routine, ORBIT Offshore can be started from the Start
menu, from the ORBITOffshore.exe icon in the Explorer, or from a shortcut button placed on
the Desktop. Once started, the Status bar at the bottom of the screen will show the status of
licensing.

DET NORSKE VERITAS

28 Aug. 02

User Manual
ORBIT Offshore V2.2

Page 9 of 77
Revision 03

3. WORKING WITH ORBIT OFFSHORE

3.1 Introduction
This chapter gives an overview of the working process to generate a risk-based inspection plan
using ORBIT Offshore. Details of the process can be adjusted to follow specific project
circumstances, but the design of the database and its reference tables requires that these tables are
filled out in a certain sequence, otherwise a considerable time will be spent in switching from table
to table, resulting in ineffective working.
The working process for ORBIT comprises the accessing of data, configuring the database by
filling-out the reference tables, then the completion of the main data table, the Parts table. This is
followed by calculation of probability of failure, consequence of failure, risk and the inspection
plan, with reporting of the results to finish the project.
There is a data import utility to allow import of bulk data from inspection management databases
and other similar sources, to allow easy data exchanges and avoid the need to duplicate the work.
The use of this utility requires that the data in the other database is checked for quality; as poor data
quality will lead to an unnecessarily complex RBI evaluation.

3.2 Data Integrity

It is important to be aware that the calculation routines in ORBIT Offshore are complex, and to
work they require that data is entered in the correct format (numeric or text). Experience has shown
that databases used purely for recording data, as opposed for calculation, can have several means of
recording the same value, and these depend on the person interpreting the data for example,
atmospheric pressure has been recorded as 0 (zero), 1 (one), Atmos, Atmos., Amb., atm, all of
which can be interpreted by the operator as atmospheric, but the computer sees six different
values, two of which are numeric and four of which are text. If it expects a number, the four text
versions are then in error and the analysis stops.
It is therefore essential that the data used in RBI is correct and consistent, and uses the correct
format for the database. Although the checking of the source data can be time consuming, the
efforts add value to the data, as incorrect or incomprehensible results from inspection implies that
the inspection effort is wasted and might even be dangerous in that they give a false sense of
security.

3.3 Documentation
The following documents have been created by DNV to guide and instruct users in the execution of
RBI Offshore projects using ORBIT Offshore software:
1. Training Course manual Offshore Topsides Systems Risk Based Inspection. This document
contains training materials giving information on the purpose of RBI, an overview of topsides
process and utilities, theory of materials degradation and probability of failure calculation,
consequence of failure calculation, risk analysis and inspection planning, with the emphasis on
the use of ORBIT Offshore software.
2. RBI Upstream Working Procedures and Guidance. This gives detailed instruction and guidance
on the working process where data is extracted from source documents, evaluated and entered
into ORBIT Offshore. Assistance is given on the derivation of assumed values where no
precise information is available.
DET NORSKE VERITAS

28 Aug. 02

User Manual
ORBIT Offshore V2.2

Page 10 of 77
Revision 03

3.4 Working process overview

The working process using ORBIT Offshore is described in detail elsewhere/1/, but consists of the
following basic steps:
1.
2.
3.
4.

Agree risk acceptance criteria with the Client

Establish the ORBIT Offshore database and begin to configure it
Collect information and carry out screening
Collect information and carry out detailed probability of failure and consequence of failure
analysis
5. Calculate risk and review
6. Calculate the inspection plan, review and adjust manually
7. Report the analysis findings and the inspection plans and frame program
The description of the use of ORBIT Offshore will follow the above sequence.

3.5 QRA: Existing Document or to be calculated by ORBIT

ORBIT Offshore allows the use of an existing QRA to calculate the consequences of an ignited
release, or if this is not available, can calculate using its own built-in RBI-QRA. If the existing
QRA is available, its use is advantageous as it avoids duplication of work already carried out and
time taken in searching for information, as well as using the same basis for the consequence
analyses. Using the built-in RBI-QRA allows the inspection department to have its own QRA
model that allows updates to be made quickly based on, for example, changes in manning due to
modifications or work-over, or changes in the value of production. Such changes can affect the risk
levels and therefore the inspection timings, but would not normally be recalculated as an update to
the existing QRA.
Section 5.4.7 describes in detail how either option should be carried out.

3.6 PoF modelling

In modelling the probability of failure, the parts evaluated are assumed to be exposed to a marine
atmosphere moist, salty air, with potential for soaking by the operation of the sprinkler and deluge
systems. Therefore, external degradation is allocated based on a materials marine atmosphere
combination only. For this release of ORBIT Offshore, care must therefore be taken when
assessing parts not exposed to marine atmosphere, such as heat exchanger tubing.
Internal degradation mechanisms can be selected manually through the Product Service table, where
the DNV suggested degradation mechanisms per service code can be switched on or off by manual
selection.

DET NORSKE VERITAS

User Manual
ORBIT Offshore V2.2

28 Aug. 02

Page 11 of 77
Revision 03

3.7 Menus and Toolbars

ORBIT Offshore, in common with MS Windows applications, uses toolbars and menus situated at
the top of the screen. These are enabled and disabled depending on the windows that are opened.
Disabled toolbar buttons are not shown, disabled menu items are greyed out. The function of the
toolbar buttons is shown below.

Help

Explorer window

Working process window

Refresh

Sort

Remove Filter

Filter by Selection

View all fields

View Fields

Replace

Search

Delete record

Insert record

Paste

Copy

Print Preview

Print current window

Open existing project

New Project

The function of each button is shown by holding the cursor on the button for a few seconds.

The Working Process window gives guidance on the working process and the filling-out of
tables, and the Explorer window allows filtering according to the user selection from Materials,
Areas, Systems, Objects, Product Service codes, Corrosion groups, Segments, Objects, Function
codes, degradation mechanisms, safety risk categories, or economic risk categories.

DET NORSKE VERITAS

28 Aug. 02

User Manual
ORBIT Offshore V2.2

Page 12 of 77
Revision 03

4. LOGGING ON, CREATING AND MANAGING PROJECT FILES

4.1 Logging on
Start ORBIT Offshore from you desktop or the taskbar menu system.
When the ORBIT splash screen appears, enter name and password, and then hit the Open button.

4.2 Project File Management

After logging on, the project file dialog box appears and allows you to:
select a project from the list shown,
or create a new project.
If the project you want to open is not in the list shown, then double-click more files or cancel
and use the File-Open command from the menu, or the open file button on the toolbar.
When no file is open, many of the menu items in the top bar are deactivated, and all the frames are
empty.

4.2.1 Opening an existing file

Select a file from the list of existing files, double click or click Open.
Typically, ORBIT will be used for longer periods on the same project: When ORBIT is opened
it will offer the previously used file name as first choice in the list.
Note that you can also create, load and delete project files later by using the File menu on the
top left.

DET NORSKE VERITAS

28 Aug. 02

User Manual
ORBIT Offshore V2.2

Page 13 of 77
Revision 03

4.2.2 Selecting a new project file name

If you select to create a new file, a new dialog box appears, showing any other orbit files in the
ORBIT folder. You can move through the explorer to select both a drive and folder where you want
to place the project file. Enter the desired name and click Save.
It is recommended that a project file is created on a suitable path using a name such as the
installation /platform name.
It is strongly recommended that you avoid having more than one file for each installation, (e.g. do
not create one file for vessels and one for piping) as this will create extra work in entering and
maintaining configuration data, as well as the possibility of creating errors in this duplicated
activity.

Click here if you

want a new
project.

The file you used

previously is in the
top of the list ready
to go.
Use File menu
later to manage
project files.

4.3 Master Database

For operators who use common materials and coding systems, a master database can be established
on a server. This database is used as the template for all new projects, and will therefore contain
much common information, so reducing the need for repetitive data entry.
When you wish to establish the master database, select Tools->Options, thereafter specify the path
where the project template is to be found. Copy separately the database that is to be the master to
that location. This will then be available to all those logged on to your network and using ORBIT
Offshore, after they have adjusted their ORBITs to point to that location.

DET NORSKE VERITAS

User Manual
ORBIT Offshore V2.2

28 Aug. 02

Page 14 of 77
Revision 03

5. EXECUTE THE PROJECT

5.1 Working Process
An overview of the working process is shown below. The details of each stage are given in
reference /1/, and the use of the software is described in the following sections.
Create Project
(Chapter 4)

Line / equipment
data available?

No

Configure Database
(Chapter 8)

Yes

Carry out Screening

(Chapter 5.2)
Configure Database
(Chapter 8)
Get and Load Data
(Chapter 7.2)

No

Line / Equipment data

already loaded?

Load Data
(Chapter 7.2)

Yes

Detailed Analysis
(Chapter 5.3)

PoF
Working

CoF
Working

Inspection
Planning

Couple Objects, Materials

Product Service codes, Groups
to parts in Parts table

Complete Area and Segments table

Identify relevant inspection

tasks and costs (Chapter 5.3)

Calculate Risk Analysis for Segments

Add CO 2, sand, water,

flow conditions to parts
in Parts table

Complete Repairs and

Production Loss tables

Allocate and Calculate

PoF (Chapter 5.4)

Couple Areas, Segments, Repairs

Production loss profiles to parts
in Parts table

Check for errors /

inconsistencies & fix

Calculate CoF (Chapter 5.4)

Evaluate inspection task

effectiveness against
degradation mechanism

Select appropriate
PoD curves

Check for errors /

inconsistencies & fix
Calculate time to
Risk Limit (Chapter 5.4)

Calculate
Inspection Plan
(Chapter 5.4)

Review & adjust manually

(Chapter 5.4.5)

Re-calculate

Report
(Chapter 6)

DET NORSKE VERITAS

Check for errors /

inconsistencies & fix

28 Aug. 02

User Manual
ORBIT Offshore V2.2

Page 15 of 77
Revision 03

5.2 Screening
Analyse Screening
This screen logs the results of the screening process. See reference /1/ for the screening process.
The screening form can be opened without any other table being open.
It is preferable that a Screening is performed by assessing each system in turn. In some cases
systems may be poorly defined, or identical to Product Service groups. In these cases Screening
may be carried out by assessing each Product Service group in turn.
The form looks like the screen dump below, and is broken into 4 sections. The button
section title allows the section to be opened up or collapsed, to ease the view.

by the

5.2.1 Create a new Record Sheet

To create a new record sheet, use the EditInsert Record menu or the Insert button. This is
necessary before starting work on the first system. The screening group name must be given as the
first action.
To the right is a navigator bar, and a selection of buttons that are used to create, refresh or delete the
screening lines on the record sheet in view. Create a new line before adding data. This will create a
probability of failure as well as a consequence of failure and risk line; data common to both is
copied from one to the other automatically when the field is exited.

DET NORSKE VERITAS

28 Aug. 02

User Manual
ORBIT Offshore V2.2

Page 16 of 77
Revision 03

5.2.2 Screening - Information

The top section concerns information on the system, with description, function, and what other
systems depend on this one for their continued operation.
Select whether the record sheet relates to a system, product code or user-defined screening group.
5.2.3 Screening Probability of failure evaluation
The second section records the probability of failure evaluation.
Select the DNV Product Service Code by pull-down menu as the equivalent to the Clients
product service code, which is a text field with no links.
Choose the material category from the pull-down menu.
Input temperatures and pressures if known.
Evaluate internal, external, fatigue, other probability of failure as either High or Low in relation
to the acceptance level. This is selected by keystroke H or L, or can be toggled using the
space bar.
Mark the degradation models with X by toggling with the space bar as a reminder for the
detailed analysis what mechanisms have been identified.
Add comment as desired to the PoF Comment field, to record the reasoning behind the
evaluation.
5.2.4 Screening Consequence of failure evaluation
The third section records the consequence of failure evaluation.
Evaluate Safety, Economic, environment, other consequence of failure as either High or Low in relation to the
acceptance level. This is selected by keystroke H or L, or can be toggled using the space bar.
Add comment as desired to the CoF Comment field, to record the reasoning behind the evaluation.

5.2.5 Screening Risk Evaluation

The last section reports the risk, with recommended actions. Colour is used to highlight the
findings. The evaluations appear as the process continues.
5.2.6 Screening Reporting
Screening Evaluation Forms: With the screening evaluation form open, clicking on the Print
Preview icon will show the preview; at the top left of the preview screen there is a Print icon. Use
of this will print out all the forms using the default printer. Print settings can be adjusted as
required.
Screening Results Summary: From the menu bar, select Report->Screening Results Summary.
This shows a report sorted by system, product service code and material, of the PoF, CoF and risk
evaluations, together with recommended actions. This is printed using the Print icon on the preview
screen.
Screening Results Matrix:
From the menu bar, select Report->Screening Risk Matrix. This
shows a 2 x 2 risk matrix with a table showing how many screening lines fall within each category.
This is printed using the Print icon on the preview screen.
DET NORSKE VERITAS

28 Aug. 02

User Manual
ORBIT Offshore V2.2

Page 17 of 77
Revision 03

5.3 Detailed analysis

5.3.1 The Parts table
Data Parts
This table defines the dimensions, materials, conditions of operation, and consequence calculation
parameters for each part. It consists of some 68 fields, but all of these do not require data! Many of
the fields are used to link to the other tables, allowing assigning of consequences and degradation
mechanisms, and so have pull-down menus.
Due to the size of the table, and that most work in the analysis is carried out in this table, there are
facilities to select which fields you want to view from the total, and to filter according to the
contents of one or more fields. Details of this are given in sections 7.4.1, 7.4.2, 7.4.3, and 0.
Details of the working process are contained in reference /1/.
The Parts table view is divided into two. The upper part shows the Part data used in the calculations,
the lower part of the view shows the calculation results taken from the degradation mechanisms
table.
The data fields are:
Field
PartID
PartName
ObjectName
ActuDiameterMm
ActuWallThickMm
InitialDamageMeanMm

InitialDamageCoV%
InitialDamageSDmm
InitialDamageYear
PipeClass
SourceMaterialName

MaterialName
CoatingYear
CoatingType
InsulationYear
InsulationType
InstallationYear

Description
Automatically assigned identification for each line in the table. Not editable.
Name of the part. Often tag number for pipe, otherwise the description of the part, such
as Nozzle N3
Object name. From pull-down menu listing from Objects table
Part Outside Diameter in mm
Part wall thickness in mm. Use the nominal value according to the specification if the
real, measured value is not available.
Mean value of wall loss used in damage update calculations. NOTE: this is NOT the
remaining wall thickness. May be NULL, otherwise must be given with EITHER CoV
or Standard deviation (not both) see next 2 fields.
Coefficient of Variation for the distribution of wall loss. May equal NULL if mean
value is NULL, but cannot equal zero.
Standard deviation of the distribution of wall loss. May equal NULL if mean value is
NULL, but cannot equal zero..
Year when the wall loss was measured. Give as YYYY only.
Reference to Pipe Class table. Optional.
Material name used by the Client for the Part. Free text field, max 50 characters.
Useful for information where the Client uses a different name to the materials
standard.
DNV material name equivalent to the Clients material name. Pull-down menu referring
to the material table
Year in which the coating was applied. Give as YYYY only. If blank, uses build
year in Installation table
Type of coating as defined in Coating table. Pull-down menu to select.
Year in which insulation was applied. Give as YYYY. If blank, uses build year in
Installation table
Type of insulation as defined in Insulation table. Pull-down menu to select
Year when the part was installed. If blank, uses build year in Installation table.

DET NORSKE VERITAS

28 Aug. 02

User Manual
ORBIT Offshore V2.2

Page 18 of 77
Revision 03

Field
DesignLifeYears
Location
AreaName
SystemCode
SegmentName
QRAsegment
GroupName
FunctionCode
SourceProdServiceCode
ProdServiceCode

Description
Information field giving nominal design life of component. May be left blank.
Location of component (inside module, outside, etc).
Area in which the part is located. Pull-down list refers to table Area
System description. Pull-down menu to select from systems table.
Segment description. Pull-down menu to select from Segments table.
Segment as defined in QRA
Corrosion group name
Function description for the part. Optional field. Pull-down menu from Functions table
Client-defined product service code.
DNV product service code. Used to allocate degradation mechanisms. Pull-down menu
from product service table.

MaxActuTempC

Maximum observed temperature in C. If NULL, ORBIT refers to MaxOperTempC.

MinActuTempC

Minimum observed temperature in C.

MaxOperTempC

Maximum limit to operating temperature in C If NULL, ORBIT refers to

MaxDesignTempC in Pipe table.

MinOperTempC

Minimum limit to operating temperature in C

Maximum observed pressure in bar gauge. If NULL, ORBIT refers to
MaxOperPressureBar, cross-referred by pipe class..
Minimum observed pressure in bar gauge
Maximum limit to operating pressure in bar gauge. If NULL, ORBIT refers to
MaxDesignPressureBar in Pipe table, cross-referred by pipe class.
Minimum limit to operating pressure in bar gauge
Comment to part analysis aimed at inspection planning. Memo field
Comment to part analysis from PoF analysis. Memo field
Comment to part analysis from CoF analysis. Memo field
Text field intended as drawing number where the part can be found
Yes / No field.
Pull-down menu from status definitions table
Repair category used for small leaks. Pull-down menu from repair category table
Repair category used for medium leaks. Pull-down menu from repair category table
Repair category used for small large. Pull-down menu from repair category table
Repair category used for rupture. Pull-down menu from repair category table
Production affected. Pull-down menu from Installation table
Redundancy of the part. Field used for information only.
Production loss profile for small leaks. Pull-down menu from production loss profile
table
Production loss profile for medium leaks. Pull-down menu from production loss
profile table
Production loss profile for large leaks. Pull-down menu from production loss profile
table
Production loss profile for ruptures. Pull-down menu from production loss profile table
Text field generated by ORBIT Offshore, reporting the time of, and errors in, the
calculations.

MaxActuPressureBar
MinActuPressureBar
MaxOperPressureBar
MinOperPressureBar
Comment
PoFcomment
CoFcomment
Reference
Scope
Status
RepairCategorySmall
RepairCategoryMedium
RepairCategoryLarge
RepairCategoryRupture
ProdAffectedName
GradeOfRedundancy
ProdLossProfileSmall
ProdLossProfileMedium
ProdLossProfileLarge
ProdLossProfileRupture
CalcReport

CO2H2ScalcPressureBar

Pressure to be used in calculation of partial pressure for CO2 corrosion rates.

CO2inGasMole%

Mole % CO2 contained within the fluids & gases within the part.
Fugacity for C02 calculation. If NULL then calculated by ORBIT Offshore

CO2fugacity
CO2scaling
Phactual

Yes / No field. Switches on whether CO2 scaling is likely, affecting corrosion rates as
a result.
Measured value of pH. If NULL, ORBIT Offshore estimates pH.

DET NORSKE VERITAS

User Manual
ORBIT Offshore V2.2

28 Aug. 02

Page 19 of 77
Revision 03

Field
CO2condensationRateGm3s
GlycolWeight%

Description
Optional field.

CO2inhibitor%

% effectiveness of CO2 corrosion inhibitor in the system. Value given is mean of a

distribution of effectiveness, with fixed standard deviation.
Yes/No field. Does water liquid condense on the part surface?
Yes/No field. Is sand erosion present?
Total Mass flow within the part, in kg per second. Only required if sand erosion = Yes
Mass flow of sand, in grams per second. Only required if sand erosion = Yes
Volume fraction of gas in the product stream. Only required if sand erosion = Yes
Yes/no field. Is water vapour present in the part, whether or not it condenses?
Flow rate for water in utility water systems. Used in corrosion rate calculations.
Concentration of Chloride ions for utility waters only.

WaterWetting
SandErosion
TotalMassFlowKgPerS
MassFlowSandGramPerS
VolumeFractionGas
WaterPresent
FlowRateMs
ChlorideConcWt%

%age glycol flowing through system. Affects CO2 corrosion rate.

5.3.2 Data requirement for models

As far as is possible, the information needs have been reduced to a minimum, but the user should
note that many fields are required for a complete analysis; consider, for example, what information
is needed to calculate CO2 corrosion rates without consideration of RBI, and what is required to
estimate the consequences of a leak. The information needs also vary depending on the degradation
mechanisms to be assessed there is no need to quote CO2 data where there is no CO2 corrosion
mechanism operating, for example. Since data requirement is dependent on degradation mechanism
and whether there is safety or economic consequence to a leak, DNV have developed the screening
approach that can focus the need for data collection and entry so that the minimum effort is
required.

CuNi-In-Water

ESCC

Local-Corr-SS

MIC

Misc-Insignificant

Sand-Erosion

SS-Local-In-Water

A
R
P
R
R

A
R
P
R
R

A
R
P
R
R

A
R
P
R
R

A
R
P
R
R

A
R
P
R
R

A
R
P
R
R

A
R
P
R
R

A
R
P
R
R

O
O
R

O
O
R

O
O
R

O
O
R

O
O
R

O
O
R

O
O
R

O
O
R

O
O
R

O
O
R

O
O
R

DET NORSKE VERITAS

A
R
P
R

A
R
P
R

Inspection Planning
& Updating

CUI-CS

A
R
P
R
R

CoF Unignited

CS-In-Water

A
R
P
R
R

CoF Ignited

CO2

Field
PartID
PartName
ObjectName
ActuDiameterMm
ActuWallThickMm
InitialDamageMeanMm
InitialDamageCoV%
InitialDamageSDmm
InitialDamageYear
PipeClass
SourceMaterialName
MaterialName

Atmos-Corr

The following table outlines what data is required in the Parts table for each activity, covering PoF
modelling, CoF modelling and inspection planning and updating, as well as efficient working with
the database. The key at the foot of the table explains the symbols used.

A
R
P
R
R
R
R
R
R
O
O
R

P
O
O
O
P
P
R
P
P
P
R
R
O

O
O
O

O
O
O

P
O
O
O
P
P
R
P
P
P
R
R

P
O
O
R
P
P
R
P
P
P
R
R

P
O
O
O
P
P
R
P
P
P
R
R

P
O
O
O
P
P
R
P
P
P
R
R

P
O
O
R
P
P
R
R
P
P
R
R

P
O
O
R
P
P
R
P
P
P
R
R

P
O
O
R
P
P
R
P
P
P
R
R

P
O
O
R
P
P
R
P
P
P
R
R

P
O
O
R
P
P
R
P
P
P
R
R

P
O
O
R
P
P
R
P
P
P
R
R

P
P
P

P
P
P

P
P
P

P
P
P

P
P
P

P
P
P

P
P
P

P
P
P

P
P
P

P
P
P

P
P
P

A
R
R

DET NORSKE VERITAS

O
P
P
R

O
P
P
O

O
P
P
P
R
R
R
R
R
O
R
R
R
R
A

O
P
P
P
R
R
R
R
R
O
R
R
R
R
A

Inspection Planning
& Updating

O
O
O

CoF Unignited

O
O
O

O
O
O

Sand-Erosion

P
R
P
R
P
O
P
O
O

MIC

O
O
O

P
R
P
R
P
O
P
O
O

P
R
R
R
P
O
P
O
O

CoF Ignited

SS-Local-In-Water

Misc-Insignificant

CuNi-In-Water

Local-Corr-SS

O
O
O

Page 20 of 77
Revision 03

ESCC

P
R
P
R
P
O
P
O
O

CUI-CS

CO2

Atmos-Corr
Field
CoatingYear
CoatingType
InsulationYear
InsulationType
InstallationYear
DesignLifeYears
Location
AreaName
SystemCode
SegmentName
QRAsegment
GroupName
FunctionCode
SourceProdServiceCode
ProdServiceCode
MaxActuTempC
MinActuTempC
MaxOperTempC
MinOperTempC
MaxActuPressureBar
MinActuPressureBar
MaxOperPressureBar
MinOperPressureBar
Comment
PoFcomment
CoFcomment
Reference
Scope
Status
RepairCategorySmall
RepairCategoryMedium
RepairCategoryLarge
RepairCategoryRupture
ProdAffectedName
GradeOfRedundancy
ProdLossProfileSmall
ProdLossProfileMedium
ProdLossProfileLarge
ProdLossProfileRupture
CalcReport
CO2H2ScalcPressureBar
CO2inGasMole%

CS-In-Water

User Manual
ORBIT Offshore V2.2

28 Aug. 02

P
R
P
R
P
P
P
P
O

R
P
O
R
P
P
R
P
P
P
R
R
O
O
O
R
P
P
O
O
O
O
P
O
O
O
O
O
A

Key
A
P
R
O

Inspection Planning
& Updating

CoF Unignited

CoF Ignited

SS-Local-In-Water

Sand-Erosion

Misc-Insignificant

MIC

Page 21 of 77
Revision 03

Local-Corr-SS

ESCC

CuNi-In-Water

CUI-CS

CO2

Atmos-Corr
Field
CO2fugacity
CO2scaling
Phactual
CO2condensationRateGm3s
GlycolWeight%
CO2inhibitor%
WaterWetting
SandErosion
TotalMassFlowKgPerS
MassFlowSandGramPerS
VolumeFractionGas
WaterPresent
FlowRateMs
ChlorideConcWt%

CS-In-Water

User Manual
ORBIT Offshore V2.2

28 Aug. 02

P
P
P
P
P
P
R
R
R
R
R
R
R
R

R
R

Automatically assigned
Allows more precise calculation of degradation, but not essential
Required for the model to work; missing data gives PoF = 1.00
Optional; may be useful for information purposes

Empty cell:

No data entry required

5.3.3 Degradation mechanisms

Data Degradation Mechanisms
This table presents the results of analyses. It shows the same data as the Parts view, only the part
data is preceded by the degradation mechanisms, probability of failure and consequence of failure
data, and the results of inspection planning calculations.
This table is most useful when reviewing the results of the inspection planning calculations, and
entering manual data for inspection planning. If manual data is entered, you must close this table
and return to the Parts table (with the same filtering) to rerun the risk calculations.
The data fields are:
Field
XpartID
DegMechName
ManualRateMean
ManualRateSD
ManualRateCoV%

Description
Part identification the same as in the Parts table
Name of the degradation mechanism
Manually entered corrosion rate mean of the distribution
Manually entered corrosion rate standard deviation of the distribution
Manually entered corrosion rate Coefficient of Variation of the

DET NORSKE VERITAS

28 Aug. 02
Field
ManualPoF
ManualPoFinspection
PoF
PoFinspection
ConseqUnignited
ConseqFatalitiesIgnited
ConseqAssetsIgnited
ConseqProdLossIgnited
ConseqOther
PLLgivenLeak
CalcRateMean
CalcRateSD
CalcManual
XcalcReport
Conseq
ConseqCatNo
ConseqCat
PLLConseq
PLLConseqCatNo
PLLConseqCat
Prob
ProbCatNo
ProbCat
Risk
RiskCatNo
RiskCat
PLLRisk
PLLRiskCatNo
PLLRiskCat
CurrProb
CurrProbCatNo
CurrProbCat
CurrRisk
CurrRiskCatNo
CurrRiskCat
CurrPLLRisk
CurrPLLRiskCatNo
CurrPLLRiskCat
InspProb
InspProbCatNo
InspProbCat
InspRisk
InspRiskCatNo
InspRiskCat
InspPLLRisk
InspPLLRiskCatNo

User Manual
ORBIT Offshore V2.2

Page 22 of 77
Revision 03

Description
distribution
Manually entered probability of failure value
Manually entered probability of failure value following inspection
Probability of failure value at present time
Probability of failure value at present time following inspection
Unignited economic consequence
Safety consequences following ignition. In no. of deaths
Economic consequence as a result of damage to the installation &
equipment
Economic consequence as a result of production loss / downtime
Other consequences
PLL assuming a leak occurs
Calculated mean corrosion rate
Calculated standard deviation of corrosion rate
Calculation report. Advises of what calculations performed and error
messages.
Total economic consequence
Economic consequence category number. Refer to matrix definition
Economic consequence category name. Refer to matrix definition
Total safety consequence as PLL
Safety consequence category number. Refer to matrix definition
Safety consequence category number. Refer to matrix definition
Probability of failure in analysis year
Probability category number in analysis year. Refer to matrix definition.
Probability category name in analysis year. Refer to matrix definition.
Total economic risk in analysis year
Economic risk category number in analysis year. Refer to matrix
definition.
Economic risk category name in analysis year. Refer to matrix definition.
Total safety risk in analysis year
Safety risk category number in analysis year. Refer to matrix definition
Safety risk category name in analysis year. Refer to matrix definition
Probability of failure in current year
Probability category number for current year probability of failure. Refer
to matrix definition.
Probability category name for current year probability of failure. Refer to
matrix definition.
Total economic risk for current year.
Economic risk category number for current year. Refer to matrix
definition.
Economic risk category name for current year. Refer to matrix definition.
Safety risk for current year.
Safety risk category number for current year. Refer to matrix definition.
Safety risk category name for current year. Refer to matrix definition.
Probability of failure after inspection calculated for analysis year
Probability category number for probability of failure after inspection
calculated for analysis year. Refer to matrix definition.
Probability category name for probability of failure after inspection
calculated for analysis year. Refer to matrix definition.
Economic risk after inspection calculated for analysis year
Economic risk category number after inspection calculated for analysis
year
Economic risk category name after inspection calculated for analysis
year
Safety risk after inspection calculated for analysis year
Safety risk category number after inspection calculated for analysis year

DET NORSKE VERITAS

28 Aug. 02
Field
InspPLLRiskCat
TimeToRiskLimit
TimeToRiskLimitStatus
PLLTimeToRiskLimit
PLLTimeToRiskLimitStatus
ManualTimeToInspect
ManualInspTask
TimeToInspect
InspTask
InspTimeToRiskLimit
InspPLLTimeToRiskLimit
MinInspTimeToRiskLimit
ExpectedDamageMeanMm
ExpectedDamageSDmm
Pressure
Diameter
YieldStrength
RequiredWallThick
WallThick
RemainingLife

User Manual
ORBIT Offshore V2.2

Page 23 of 77
Revision 03

Description
Safety risk category name after inspection calculated for analysis year
Time from current year to economic risk limit
Status message regarding the time to risk limit
Time from current year to safety risk limit
Status message regarding the time to risk limit
Manual choice of time to inspection, measured from the current year.
Manual choice of inspection task, according to pull-down menu from
Inspection Effectiveness table
Shortest time in years from current year until the risk meets the first
acceptance criteria.
ORBIT Offshore calculated choice of inspection task
Time from current year until the second inspection for economic risk,
assuming that the first inspection found the expected damage.
Time from current year until the second inspection for safety risk,
assuming that the first inspection found the expected damage.
Smallest of the two times to second inspection
Calculated wall loss, mean value
Calculated wall loss standard deviation
Max actual or operating pressure, in barg
Outer diameter of part
Material yield strength in MPa
Wall thickness required, in mm, to withstand the above pressure given
the diameter and yield strength, calculated according to ASME B31.G
Actual wall thickness, in mm
Time remaining for the wall thickness to reduce from current thickness to
required wall thickness, in years

5.3.4 Objects table

Data Objects
This table defines the Objects in the database, and allows the results of the RBI to be summarised
into an Inspection Plan. This works on the assumption that the Parts are components of the Objects,
so typical objects are individual pressure vessels, Pipe, and similar. Parts related to a pressure vessel
would then be the shell, heads, and nozzles; parts related to Pipe would be the individual tag
numbers, but there is no reason why these should not also be defined in more detail as reducers,
elbows, tees, and similar. The table can also be completed by use of the Analyse->Object Data
form view (see 5.4.10).
The data given in this table are printed in the report Inspection Plan by Object. The data required
is:
Field
Object Name

Object Type
Description
Inspection_Internal_Comment
Inspection_External_Commen
t

Description
The name of the object. Typically used is the equipment tag number when equipment
is to be analysed in separate parts. Forms pull-down menu in Parts table
Max 20 characters.
Description of the object. This is a pull-down menu from pre-defined object types
Text description of the object. Max 50 characters
Memo field where internal inspection requirements based on the RBI can be entered
as text, also findings from inspections.
Memo field where external inspection requirements based on the RBI can be entered
as text, also findings from inspections

DET NORSKE VERITAS

28 Aug. 02
Field
PoF_Internal_Comment
PoF_External_Comment
CoF_Comment
MaxDesigntempC
MinDesigntempC
MaxDesignpressBar
MinDesignpressBar
InternalLiningCladding
LiningCladdingType

User Manual
ORBIT Offshore V2.2

Page 24 of 77
Revision 03

Description
Memo field where evaluations relating to internal PoF estimation can be summarised.
Memo field where evaluations relating to external PoF estimation can be
summarised.
Memo field where the CoF evaluation can be summarised.
Information field. Maximum design temperature for the Object.
Information field. Minimum design temperature for the Object.
Information field. Maximum design pressure for the Object.
Information field. Minimum design pressure for the Object.
Yes/No field (0 for No, 1 for Yes). For information only
Text field where the internal lining or cladding type can be specified. For information
only, not yet used in ORBIT evaluations.

5.3.5 Area table

Data Areas
This table defines the areas or modules forming the installation. An area is typically a module of the
installation bounded by fire and blast walls, or similar type of boundary. The data allows the
simplified QRA in ORBIT Offshore to calculate the branch probabilities for ignition, fire and
explosion, leading to installation damage and loss of life. The table contains data on what can cause
an ignited event, and the extent of the consequences of that ignition in terms of the scale of damage
to the installation and personnel on it. The data required is:
Field
AreaName
Description
Comment
VolumeM3
NumberOfPersons
AreaM2
PressWallDesignBar
PressEquipDesignBar
PressExplMaxBar
VentChange1Hr
HotWorkHrYear
FireWater
NumberOfPumps
NumberOfCompressors
NumberOfGenerators
NumberOfPersonsNbour
MaterialCost
WtElectTon
WtHvacTon
WtInstrTon
WtPipingTon
WtMechTon
WtStructTon
WtFireSafeTon

Description
Area name. Max 20 characters
Area description. Max 50 characters
Memo field allowing comment regarding the area data
Volume of space within the area floor area x height in cubic metres
Average number of persons located within the area
Area floor area in square metres
Design pressure for blast walls around the Area
Design blast pressure for major equipment within the area
Max. anticipated blast pressure usually taken from QRA
Number of air changes per hour
Number of hot work hours per year
Yes / No field is fire water present?
Number of pumps located within the area
N umber of compressors located within the area
Number of electrical generators located within the area
Average number of persons within neighbouring areas
Optional. Cost of materials of construction for the area
Optional. Tonnes weight of electrical equipment
Optional. Tonnes weight of HVAC equipment
Optional. Tonnes weight of instrumentation equipment
Optional. Tonnes weight of piping equipment
Optional. Tonnes weight of mechanical equipment
Optional. Tonnes weight of structural items
Optional. Tonnes weight of fire & safety equipment

DET NORSKE VERITAS

28 Aug. 02
Field
WtArchiTon
WtOther1Ton
WtOther2Ton
TotalWtTon
ProdDownTimeDays

User Manual
ORBIT Offshore V2.2

Page 25 of 77
Revision 03

Description
Optional. Tonnes weight of architectural items
Optional. Tonnes weight of user-defined other equipment
Optional. Tonnes weight of user-defined other equipment
Optional. Total tonnes weight of all the above
Optional. Production downtime expected during repairs and replacement of the above

All fields below the double = line are optional, and can be left blank. These are used if the option
CostRBIQRA is selected Yes in the Segments table, in conjunction with the cost per tonne of
these items that is given in the window that pops up following the sequence DataSegments;
select the relevant segment, then AnalyseRisk calculations and click on the Cost Parameters
button.
In the case where an external QRA is to be used to estimate consequence, then it is only necessary
to define the area name. No other data is required for ORBIT to assign CoF.
5.3.6 Segments table
Data Segments
This table defines the isolatable segments in hydrocarbon-containing pressure equipment, in terms
of their location, contents, and potential for blowdown, and is used in ignited consequence
calculations. The table contains data allowing the size and duration of any ignited event to be
estimated. The data required is:
Field
SegmentName
Description
Comment
TempC
PressureBar
VolumeM3
CalcRBIQRA

CostRBIQRA

AreaNameRBIQRA
FluidType
BlowDown
LowerExplLimit
SpreadEquip
SpreadRiser
SpreadArea
EquipFluid
EquipPFP
EquipBD
RiserFluid

Description
Segment name. Max 20 characters
Description of segment. Max 50 characters
Memo filed for consequence of failure analysts comments regarding definition of
the segments
Max operating temperature of segment contents
Max operating pressure of segment contents
Internal volume of the segment
Yes / No field: Set to Yes if the ORBIT internal QRA is to be used to calculate
the segment consequences of failure. Set to No if an external QRA will be used
to estimate consequence. Data must be edited manually into tables Segment Leak
Size, Segment Extent and Segment Leak Size Extents. See 5.4.7.
Yes / No field: Set to Yes if the ORBIT Internal QRA is to be used to calculate
the the repair costs. This requires that weights and costs per tonne of equipment
etc. to be supplied. See 5.4.7. Set to No otherwise, also if an external QRA is
to be used for CoF estimation.
Area name where the segment is located. Pull-down menu referring to table Area
Fluid type in segment. Pull-down menu to select.
Yes / No field
Lower explosive Limit for segment contents
Yes / No field. Is spread to equipment possible in the Area?
Yes / No field. Is spread to risers possible in the Area?
Yes / No field. Is spread throughout the Area possible?
What fluid is in the equipment? Pull-down menu.
Yes / No field. Is the equipment protected by passive fire protection??
Yes / No field. Is the equipment protected by blowdown?
What fluid is in the riser? Pull-down menu

DET NORSKE VERITAS

28 Aug. 02
Field
RiserPFP
RiserBD
KappaGas
MoleWeightGas
FlashFracOil
MassBurningRateOil
DensityOil
MaterialCost
WtElectTon
WtHvacTon
WtInstrTon
WtPipingTon
WtMechTon
WtStructTon
WtFireSafeTon
WtArchiTon
WtOther1Ton
WtOther2Ton
TotalWtTon
ProdDownTimeDays
NbourMaterialCost
NbourWtElectTon
NbourWtHvacTon
NbourWtInstrTon
NbourWtPipingTon
NbourWtMechTon
NbourWtStructTon
NbourWtFireSafeTon
NbourWtArchiTon
NbourWtOther1Ton
NbourWtOther2Ton
NbourTotalWtTon
NbourProdDownTimeDays

User Manual
ORBIT Offshore V2.2

Page 26 of 77
Revision 03

Description
Yes / No field. Is the riser protected by passive fire protection?
Yes / No field. Is the riser protected by blowdown?
The kappa value for the hydrocarbon gas
The molecular weight for the hydrocarbon gas
The flash fraction of the oil
The mass burning rate of the oil
The density of the oil
Optional. Cost of materials of construction for the area
Optional. Tonnes weight of electrical equipment
Optional. Tonnes weight of HVAC equipment
Optional. Tonnes weight of instrumentation equipment
Optional. Tonnes weight of piping equipment
Optional. Tonnes weight of mechanical equipment
Optional. Tonnes weight of structural items
Optional. Tonnes weight of fire & safety equipment
Optional. Tonnes weight of architectural items
Optional. Tonnes weight of user-defined other equipment
Optional. Tonnes weight of user-defined other equipment
Optional. Total tonnes weight of all the above
Optional. Production downtime expected during repairs and replacement of the
above
Optional. Cost of materials of construction for the neighbouring area
Optional. Tonnes weight of electrical equipment in the neighbouring area
Optional. Tonnes weight of HVAC equipment in the neighbouring area
Optional. Tonnes weight of instrumentation equipment in the neighbouring area
Optional. Tonnes weight of piping equipment in the neighbouring area
Optional. Tonnes weight of mechanical equipment in the neighbouring area
Optional. Tonnes weight of structural items in the neighbouring area
Optional. Tonnes weight of fire & safety equipment in the neighbouring area
Optional. Tonnes weight of architectural items in the neighbouring area
Optional. Tonnes weight of user-defined other equipment in the neighbouring
area
Optional. Tonnes weight of user-defined other equipment in the neighbouring
area
Optional. Total tonnes weight of all the above in the neighbouring area
Optional. Production downtime expected during repairs and replacement of the
above for the neighbouring area

All fields below the double = line are optional, and can be left blank. These are used if the option
CostRBIQRA is selected Yes in the Segments table, in conjunction with the cost per tonne of
these items that is given in the window that pops up following the sequence DataSegments;
select the relevant segment, then AnalyseRisk calculations and click on the Cost Parameters
button.
Where an external QRA is to be used, only the segment name and corresponding Area name should
be entered. The fields CalcRBIQRA and CostRBIQRA should be set to No.

DET NORSKE VERITAS

28 Aug. 02

User Manual
ORBIT Offshore V2.2

Page 27 of 77
Revision 03

5.4 Running the analysis

Once the data is entered in mandatory fields in the tables, the detailed analysis is executed as listed
below. The probability of failure and consequence of failure calculations can be done separately as
the work progresses, it is only when progressing to risk and further, that the order below must be
followed.
5.4.1 Probability of failure for parts
Allocate the degradation mechanisms to the Parts. Open the Parts table, set filters as desired,
and follow the sequence AllocateAll, or select the individual mechanism group you wish to
allocate instead.
After this is complete, follow the sequence Calculateprobability of failure
5.4.2 Consequence of failure for Parts
Open the Segments table, and follow the sequence ToolsRisk Analysis for Segments.
Segments where CalcRBIQRA is s set to No will not be calculated. Close the Segments
table.
Open the Parts table, set the filters, and follow CalculateConsequence of failure
5.4.3 Risk calculation for Parts
After calculating probability of failure and consequence of failure, the parts table should be
opened, filters set as desired, and CalculateRisk followed to calculate the risk values for the
Parts.
5.4.4 Time to Risk Limit
Open the Parts table and set the filters as desired. This allows the calculation of the time to the
safety and economic risk limits for all Parts in the filter. This is an iterative process, and may
take a little time. Follow CalculateTime to Risk Limit
5.4.5 Inspection Plans
Open the Parts table and set the filters as desired. Follow CalculateInspection Plan to
calculate the inspection plan for the parts. The software reviews all applicable inspection tasks
for each degradation mechanism for each part, and selects the one with the greatest risk
reduction per cost unit. It then calculates the second time to the risk limit. This is a lengthy
process, made longer if you have created a large list of potential inspection tasks for each
degradation mechanism.
After calculating the inspection plan, open the Degradation Mechanisms table, set the view
Fields to view those columns that are of interest, and review the inspection plan selection. This
table allows manual selection of inspection task (from those specified in the Inspection
Configuration) and timing. After selecting the manual inputs, re-run the inspection plan
calculations and the manual input is included in the plan, together with its effect on the risk
levels.
DET NORSKE VERITAS

28 Aug. 02

User Manual
ORBIT Offshore V2.2

Page 28 of 77
Revision 03

5.4.6 Calculate All

The use of CalculateCalculate All follows the above sequence in the above order, with the
exception of Allocating the degradation mechanisms.
To allocate and calculate all in one process, follow ToolsAllocate and Calculate All.
5.4.7 Consequence of failure analysis
When the areas and segments have been defined by name, a combined form view for these can be
used to complete the filling-out of the tables by opening the segments table and following the menu
sequence:
Analyse Risk Calculations
This data entry form (AnalyseRisk Calculations) can be available only when the Segment table is
active. A form view is given where tabs are used to show input data and results of calculations.
Segment data:

This allows input of data into the Segments table in a manner that is
easier to follow than direct input to the table.

Area and Installation data:

This allows input of data into the Area table in a manner that is easier
to follow than direct input to the table. It also contains one field not
given elsewhere, being the total personnel count for the installation.

Calculation results:

This shows an event tree for each segment and hole size combination.
To change the hole size: Click on a radio button,
To change segments: Close the form and select another segment.

Conseq costs input:

To be used where the CostRBIQRA is selected Yes. Allows input

of the cost data in relation to segment and area in several ways.
Either:

1. Material cost
Input the replacement / repair costs for equipment, area, neighbouring area
and entire installation. Exclude cost of deferred production whilst these repairs are ongoing.
Costs can be estimated from the sum of the cost of replacement of these items. Precise values
are not required.
2. Per weight
Input the weight of each discipline as listed. This requires that the cost per
tonne is entered into the Area and Segments tables.
3. Per total weight Input the total weight of equipment likely to be damaged. This requires that
the cost per tonne is entered into the Area and Segments tables.
The costs per tonne for options (2) and (3) can be given by clicking on the Cost parameters
button.
In addition, the downtime and deferred production are required. Two options exist:
a. Input the number of days downtime based on estimates by platform personnel and experience
b. ORBIT can calculate based on the Dow Fire and Explosion Index if (a) is left blank.

DET NORSKE VERITAS

28 Aug. 02

Conseq costs output:

User Manual
ORBIT Offshore V2.2

Page 29 of 77
Revision 03

This shows the results of the CostRBIQRA as the probability of

damage, the cost of damage, the extent of production downtime, the
production affected and the cost per day, the total cost and the total
risk cost, the last two after the Calculate button is pressed. The
option used in deriving the costs (1, 2 or 3; a or b) is shown next to
the cost figures.

5.4.8 Consequence Analysis using External QRA

There are many advantages to using an external QRA in RBI, not least the reduction in duplicated
effort in data collection and analysis, as well as consistency in approach with the other risk studies.
However, there are several points to note before following this approach:
A QRA is usually performed to assess all risks to personnel on an installation, not just risks
from leakage of fluids
A QRA usually is based on defined leak rates as opposed to degradation-based hole sizes, as is
ORBIT RBI.
These require correction prior to entering the data into ORBIT. The precise method of correction
should be checked for each case; guidance can be obtained from DNV if required.
The following guidelines are proposed for the use of existing QRAs in RBI analysis, and are
applicable for personnel risk only.
1.
2.
3.
4.

5.

Obtain the event trees for the relevant segments.

Determine the risk level arising from inspectable events
Remove the generic failure rate component from the event tree the output should be
GIVEN a leak, ORBIT will calculate the PoF.
Check whether the hole sizes used in the QRA are relevant to RBI by use of release rate
equations. If the QRA hole sizes are close to those required by RP-G 101 then the hole sizes
need not be adjusted and the event tree may be used directly, with correction for leak
frequency only. Otherwise, calculate the probability of ignition based upon corrected hole
size.
Tabulate corrected personnel CoF per segment with respect to the 4 hole sizes.

The following additional steps should be carried out to use existing QRA results in RBI covering
economic consequence assessments:
6.
7.
8.

9.

From the safety risk assessment, determine which end events contribute to fire and
explosion for each segment, materials and degradation combination
Determine from the QRA the end event probabilities for these events
Determine the likely extent of damage to equipment and structure, using, for example,
equipment count/value, rebuilding time & cost, referring to RP-G 101 Appendix B where a
graph is given from Dow that can assist in this.
Multiply the end event probabilities by the cost of that end event, and sum up for the
specific hole sizes for that segment, taking the values in the same distribution as the hole
size distribution to give the final economic consequence for that segment & degradation
mechanism.

The above method will give values of PLL per segment and hole size combination (step 5), and
material loss per segment and hole size (step 9), together with the probabilities for each end event.
The data is entered into ORBIT thus:
DET NORSKE VERITAS

28 Aug. 02

User Manual
ORBIT Offshore V2.2

Page 30 of 77
Revision 03

Safety Consequence
Open the Segment Leak Sizes table (Data->Ignited Events->Segment Leak Sizes). Select the first
segment by pull-down menu and the smallest leak size name, also by pull-down menu. The hole
size field is for information only. Enter the corrected PLL in the field PLLGivenLeak. Repeat for all
segment and leak size combinations.
Economic Consequence
Open the Segment Extents table (Data->Ignited Events->Segment Extents). Select the first
segment by pull-down menu and the damage extent name, also by pull-down menu. The material
cost of damage should be entered in the appropriate currency units for that segment and extent
combination, together with the number of days production downtime and the production affected.
Repeat for all segment and extent combinations. This table defines the size of the relevant end
events.
Open the Segment Leak Size Extents table (Data->Ignited Events->Segment Leak Size Extents).
Select the first segment by pull-down menu, the leak size by pull-down menu and the damage
extent name, also by pull-down menu. The probability of that combination of segment, leak size and
extent is then given i.e., the probability of that specific end event. Repeat for all segments, leak
size and extent combinations.
A short-cut to creating an empty set of tables so that the event tree data can be quickly entered is to
carry out the following:
1.
Define area names
2.
Define segment names, and input the area name for the segment
3.
Set CalcRBIQRA to Yes
4.
Complete for all segments and area combinations.
5.
Open Segments table. Run Risk Analysis (Tools->Risk Analysis for Segments)
6.
Return to Segments table, and set all CalcRBIQRA to No. Be sure to do this, otherwise
rerunning the risk analysis will erase any manually entered data!
7.
The tables listed above will have been filled out but with the numerical data missing.
5.4.9 Individual Part analysis
With the Parts table open, all data relating to the part selected can be viewed and adjusted for what-

DET NORSKE VERITAS

28 Aug. 02

User Manual
ORBIT Offshore V2.2

Page 31 of 77
Revision 03

if or sensitivity calculations, and the results viewed graphically as probability of failure and risk
plotted as functions of time for all degradation mechanisms, showing their relation to risk limits.
Probability of failure after inspection is also shown when this has been calculated. Graphs can be
copied and pasted into other documents.
This is achieved by selecting AnalysePart data and Calculations
5.4.10 Individual Object Analysis
This is intended to allow quick and easy data input, results analysis and inspection planning for
Objects. It is obtained through Analyse->Object Data. The following screen view is obtained:

This view is split into three areas. The top area shows the object name, description and type, and
has a navigation bar. Individual objects can be selected from a pull-down menu that refers to the
Objects table.
The middle area shows a sketch of the object type (a separator in this case), and has a few data entry
fields for mass data entry and editing. Entry of data into these fields allows all parts for the object to
be updated with the new data. Data entry is effected by clicking on the Edit button, at which point
a new screen is opened to allow the automatic creation of the vessel parts shell, head, nozzles,
materials. Press OK when the data is ready for entry and the parts created.
Changes that are required subsequent to the initial creation of the parts should be edited into the
table at the bottom of the screen; the insertion of additional parts (such as new nozzles) or deletion
of parts should be made by use of the Insert or Delete buttons to the left of the lower part of the
screen.
The lower part of the screen has three tabs. The first shows basic part mechanical data such as
materials, dimensions, pressures and temperatures and location; the degradation mechanisms tab
DET NORSKE VERITAS

User Manual
ORBIT Offshore V2.2

28 Aug. 02

Page 32 of 77
Revision 03

allows the RBI results and outline inspection plan to be reviewed and manually adjusted as
required; the Evaluation tab allows the PoF, CoF and Inspection evaluations to be made. The
buttons with three dots
can be used to open the field to a greater size for easier viewing and
editing.

6. REPORTING
Report (Choice as below)

The following reports are available, accessed as shown in the screen dump:
Report name
Executive Summary

System summary

Frame programme

Parts
Risk distribution

Description
Intended as a short summary for management, the report prints the contents of the
Comments field in the Installation table, followed by the contributions of safety and
economic risk to the whole picture, expressed as pie charts. Also, matrices for the current
year, analysis year before & after inspection are shown for safety & economic risk
This is a detailed summary of the risk results and the conditions that give rise to them,
printed on a system-by-system basis. The probabilities of failure, consequence of failure and
inspection comments from the System table are also printed as footnotes to each system
page.
The inspection frame program is given for the inspection planning period, and is intended as
a general forward planning tool. This shows, for each system and corrosion group
combination, when inspection should take place for each degradation mechanism, with a X
for the first inspection and a O for the second.
Simple table of parts including actual diameter and actual wall thickness for each part,
grouped by object
The risk distribution, showing risk in current year, analysis year with and without
inspection, can be printed for each of the following:
Degradation mechanisms
Areas
Systems
Segments
Objects
Groups

DET NORSKE VERITAS

28 Aug. 02
Report name
Inspection plan

Inspection Plan by
Object

Risk summary

Show Risk results

Show Risk matrices

Show Both
Screening Result
Summary
Screening Risk
Matrix
Access Report

User Manual
ORBIT Offshore V2.2

Page 33 of 77
Revision 03

Description
This is a part-based inspection plan, showing part name, degradation mechanism, risk
before and after inspection, inspection task and timing, expected damage extent. The Plan
can be focused by filtering on the desired conditions prior to running the report. The last
page shows any filter conditions.
This prints an inspection plan for all parts forming linked to Objects, based on the filtering
set in the Parts table. The descriptive data for the object is listed at the top of the report,
together with the risk limits and the inspection planning period, thereafter each part is listed
with the degradation mechanisms, rate(if applicable), PoF category, CoF category and
inspection requirement by task and timing.
This plots the safety and economic risk matrices according to the filters set for before and
after inspection, and also whether you want to filter selected degradation mechanisms see
the screen-dump below.
This allows the viewing of risk results, remaining life calculations and calculation reports
for each part and degradation mechanism according to the filters set on the Parts table.
This plots the safety and economic risk matrices according to the filters set, and also
whether you want to filter selected degradation mechanisms see the screen-dump below.
Only the current risk picture is given.
This plots the risk matrices and gives the risk summary together.
A summary of the results from the Screening Analysis (AnalyseScreening).
A summary 2 x 2 matrix showing the screening results, with a list of how many screening
lines lie in each cell of the matrix.
Accessible to Administrators only. Deprecated feature that will be removed in future
version. This allows the display and printing of MS Access report.

The reports above the double = line can be printed in their entirety without having the Parts table
open. Those beneath the double = line must have the parts table open, and also report according to
the filters you have set.
Reports may be printed as hard copy, or saved as .PDF or .RTF format by following FileExport

DET NORSKE VERITAS

User Manual
ORBIT Offshore V2.2

28 Aug. 02

Page 34 of 77
Revision 03

once the report preview screen is showing. The group name is also used in the Inspection Frame
programme report.

7. DATABASE MANAGEMENT, TOOLS & VIEWS

7.1 Database Management
7.1.1 ORBIT Project
An ORBIT Offshore project comprises a user interface file, ORBIT Offshore program file, and a
database built with MS ACCESS 97. You do not need to have MS ACCESS to run ORBIT.
The ORBIT Offshore uses three files. All three are required in the same location for ORBIT to
function properly:
Filename.sop
Filename.mdb
Filename.xls

gives information about the project "filename"

database containing the data entered into project "filename"
Excel spread sheet that may be used for exporting data from "filename"

7.1.2 Multiple Users Entries

Several users can simultaneously operate with ORBIT Offshore on their PC/workstation and
logged on to the project file on a network server. This allows for effective data entry, but implies
that users must co-operate so they avoid confusion.
At present it is not possible for users to work on separate database, e.g. on lap-tops/notepads,
and then "merge" the databases.
It is recommended that only one user initiate calculations using ORBIT Offshore, and that no
one else opens the database whilst calculations are ongoing.
7.1.3 Backing Up The Data
The database should be backed-up regularly, particularly during periods with intensive data
gathering. The frequency and number of backups should be decided on the basis of how much
data/time can be afforded to be lost if the system fails. This is less important at later stages where
most of changes can be re-calculated. It is the "filename.MDB", that contains data and hence
requires back-up.
7.1.4 Saving Data During A Work Session
ORBIT saves data almost immediately it is entered. This process is automatic, so the data does not
need to be saved manually. Although this philosophy has shown to work well and guards against
system failures, it means that there is no undo function.
7.1.5 Buffered Mode
ORBIT Offshore can be run in Direct or Buffered mode. When running in Direct mode the
underlying Access database will be updated instantaneously when data is changed by the user.
When running in Buffered mode, the user has to explicitly save (FileSave) to store changed data
in the database.

DET NORSKE VERITAS

28 Aug. 02

User Manual
ORBIT Offshore V2.2

Page 35 of 77
Revision 03

To work in Buffered mode select ToolsOptions and choose Buffered on the General tab. No
project can be open if you want to switch to or from Buffered mode.
Operation in Buffered mode may be quicker if accessing the database over a long network
connection, but be warned that a system crash is likely to result in data loss as it will not be saved.
Operation in Direct mode immediately saves each cell of data upon exiting that cell; experience
shows that there is no data loss upon a crash.
7.1.6 A Warning: Do Not Tamper With The Database File.
Users should not attempt to open the database directly, as it is very easy to corrupt the database.
Security is applied to prevent unauthorised direct entry to the database files. ORBIT 2.2 has been
upgraded to DAO 3.6, which effectively allows use of the MS Jet 4.0 engine. ORBIT 2.2 can
operate on databases of MS Access 97 format or databases that have been converted to the MS
Access 2000/2002 format. The ORBIT policy is that, for a period after the 2.2 release, databases
are kept in the Access 97 format (i.e. they are not converted to Access 2000 / 2002 format) so that
data can easily be exchanged between users who operate with different versions of ORBIT and MS
Access.
7.1.7 Master database
It is possible to specify a location for a master database. For operators who use common materials
and coding systems, a master database can be established on a server. This database is used as the
template for all new projects, and will therefore contain much common information, so reducing the
need for repetitive data entry.
When you wish to establish the master database, select Tools->Options, thereafter specify the path
where the project template is to be found. Copy separately the database that is to be the master to
that location. This will then be available to all those logged on to your network and using ORBIT
Offshore, after they have adjusted their ORBITs to point to that location.

7.2 Data Loading and Data Entry

This section considers the cases where the data required is available in electronic or paper form.
7.2.1 Data available electronically
Before loading the Parts data into ORBIT Offshore, the background data tables must be filled out,
otherwise the unmatched records will not be loaded. In addition, great care is required to match the
requirements for text or numeric fields, as the wrong format will not be loaded. DNV recommend
strongly that the data in the source file be checked carefully for consistency and correct format prior
to attempting to load it to prevent these problems. For example, typical errors that arise when
loading pressures, which can be given as 0 (Zero), 1, atm. Atmos, amb., all meaning ambient
pressure of zero bar.g, result in only those parts where the value zero or 1 is given being loaded, and
one of these is incorrect also !
Use of Exchange Inspection Data function
The Tools Exchange Inspection Data function can be used to import data from another database.
This function calls a file named Inspection.exe; this latter file is supplied blank. It is intended that
this .exe file is written by the Clients software specialist so that it selects the fields in the Clients
database, carries out unit conversions and checks the format before inserting the data into the

DET NORSKE VERITAS

28 Aug. 02

User Manual
ORBIT Offshore V2.2

Page 36 of 77
Revision 03

ORBIT tables. As there are a large number of inspection management databases in different levels
of development and customisation, it was seen to give better control for the .exe file to be written by
the Client rather than DNV trying to cover all possible combinations. DNV will, naturally, give
support in this activity.
Copy-Paste
Data can be copied to the clipboard from electronic sources and pasted directly into ORBIT
Offshore. Note that this function allows copying of whole lines of data as selected by the View
Fields function to or from the tables. Data copied from ORBIT is pasted into other programs with
the column headings present.
Data that is to be copied from other programs and pasted into ORBIT should be ordered as the
columns in ORBIT are ordered, and the data type checked so that you do not attempt to paste text
into a numeric field.
The function Edit->Copy Special or Edit->Paste Special carries out these operations
7.2.2 Data available in paper form
If the data required is available only in paper form, or partly in paper form, then this must be
entered manually. It is likely that, particularly for items of equipment, the detail of data desired has
not been recorded in an inspection management database, and so it is likely that some manual entry
is required even where the bulk of data is available electronically.
The most effective method of manual entry is to open the Parts table and use the View Fields
selector to view only the relevant fields related to the Parts; in addition, the order of these fields can
be changed to suit the order in which the information is presented, making the task just a little
easier.
You should take care that the background tables are fully completed before working with the
Parts table, as otherwise you will receive error messages that indicate that the background table
does not contain the same data.
A data entry form is provided to assist in data entry for Separators, and this will be extended in a
subsequent release of the software to include other common equipment types. This form ensures
that the data common to all parts of the vessel only needs entered once, thereby saving some time.
This form is accessed by clicking on the Insert Object Parts button at the bottom of the Objects
table when the highlight is on the required defined tag.

7.3 Tools
The following tools are available:
7.3.1 Info
Tools Info
This operates on the Parts table and the Degradation Mechanisms table, and shows the physical and
process information relating to the Part selected. This is useful in tracking down errors, such as
those that lead to a probability of failure = 1.00

DET NORSKE VERITAS

28 Aug. 02

User Manual
ORBIT Offshore V2.2

Page 37 of 77
Revision 03

7.3.2 Details
Tools Details
This shows the calculation report for the Part selected in the Parts table and the Degradation
Mechanisms table. This is useful in tracking down errors, such as those that lead to a probability of
failure = 1.00
7.3.3 Set manual rates and PoF
Tools Set manual rates and PoF
This opens a window that assists in creating user-defined degradation mechanisms with degradation
rates or set probability of failure values, or editing those already set for software-defined models.
Once created, these can be allocated to tags either using the Group Update function under the
Tools menu, or by manual allocation in the Parts view or the Degradation Mechanisms table.

7.3.4 Screening data exchange

Tools Screening Data exchange
[Currently not implemented]
7.3.5 Update from Group Data
Tools Update from Group data
This allows the updating of model rates and probability of failure values according to corrosion
groups. This might be desired, for example, following the receipt of corrosion coupon data, to
modify the CO2 corrosion rates applied to the tags in the subject group.

DET NORSKE VERITAS

28 Aug. 02

User Manual
ORBIT Offshore V2.2

Page 38 of 77
Revision 03

First, the data to be updated for the group must be defined, following ToolsUpdate from Group
data Specify data. After closing the table, follow ToolsUpdate from Group dataUpdate to
execute the updating of the data.
Note that there is no Undo function.
7.3.6 Source Materials
Tools Source materials
This table allows a quick translation between Client material descriptions in the Source Material
field of the Parts table to the DNV materials in the Parts table. This avoids having to manually
select the DNV materials, thereby saving a lot of time.
Firstly, the translation between the two materials is specified in the table accessed by
Tools Source MaterialsDefine. Thereafter, the translation is executed by ToolsSource
materials Convert Fields.
Note that this will only work where the DNV Materials field is NULL. If there is any data present,
including (Space), the function will skip to the next row. It therefore does not update. For that,
you should use the Replace function found under the Edit menu.
7.3.7 Source Product Service
Tools Source product service
This table allows a quick translation between Client product service codes in the Source Product
Service Code field of the Parts table to the DNV Product Service Code in the Parts table. This
avoids having to manually select the DNV product service codes, thereby saving a lot of time.
Firstly, the translation between the two is specified in the table accessed by ToolsSource
Product ServiceDefine. Thereafter, the translation is executed by ToolsSource Product
Service Convert Fields.
Note that this will only work where the DNV product service field is NULL. If there is any data
present, including (Space), the function will skip to the next row. It therefore does not update.
For that, you should use the Replace function found under the Edit menu.
7.3.8 Risk analysis for Segments
Tools Risk Analysis for Segments
This calculates the ORBIT Internal QRA for all segments where CalcRBIQRA is set to Yes in the
Segments table. Open the Segments table, and run the Risk Analysis for Segments.
7.3.9 Allocate and Calculate All
Tools Allocate and Calculate All
This allows the allocation of degradation mechanisms, calculation of probability of failure and
consequence of failure, risk, time to inspection and inspection plan in one click. It requires that the
Parts table is opened and filters set before starting.

DET NORSKE VERITAS

28 Aug. 02

User Manual
ORBIT Offshore V2.2

Page 39 of 77
Revision 03

7.3.10 Repairing and Compacting the Database

Tools Repair and Compact Database
Intensive use of the database results in the file becoming extremely large as partial calculation
results continue to be stored. When calculations become slow, the database file can be compacted.
Also try this function when you suspect that some data has become corrupted, e.g. due to an
incomplete update.
7.3.11 Options
This contains the security options. These can only be modified by operators with Administrator
rights.

7.4 Views and Filters

7.4.1 View Fields
Data ViewView Fields
This allows the user to select which fields are required for viewing, and to adjust the order in which
they are seen. Either pre-defined views can be selected from a pull-down menu from the View
Fields library, or user-defined fields selected and saved with a user-defined name.
Fields are selected by highlighting the fields and using the right or left arrows to choose which of
the available fields are to be shown. The order of viewing can be chosen by selecting one or more
fields and using the up/down arrows to reposition them. The choice of fields can be saved with a
name (before clicking OK), for later re-use.
Use of the Advanced feature allows the column width to be adjusted and new headings to be
given for the selected view. This does not affect the database field headings, only the screen view.

Select OK to view the fields as selected.

DET NORSKE VERITAS

28 Aug. 02

User Manual
ORBIT Offshore V2.2

Page 40 of 77
Revision 03

7.4.2 Filter
View Filter
This allows the user to select which rows are required for viewing, reporting or working with.
Fields are selected according to the form and can be saved with a name in a library, and viewed by
pressing OK. Fields can be combined by use of logical AND and OR statements according to
the pull-down menus.
Where only a part of the database is to be worked on or reported, filtering can be done on, for
example, segments, or temperatures in excess of a certain value. When reports are printed for
filtered data, the filter parameters are printed with the report.
Filtering can be done on one parameter only by highlighting that in the table and clicking on the
yellow lightning menu button to get filter by selection.

The above filtering operates with the Parts and Degradation Mechanisms tables only. Up to four
parameters can be selected in one go, and if more are required for a complex filtering operation,
then the first set should be saved and another set created with the AND or OR append function radio
button checked, and saved with a new name.
A different style of filter form is used on the other tables, where a function is built up by selection
of field name and operation, copying this into an expression that can be manually edited later. This
can also be saved with a name of choice.
Pre-existing filters are available through the pull-down list from the library.
7.4.3 Search and Replace
Edit Replace
This function searches for the string specified by the user in the field specified by the user, and
updates it according to the user-specification. The function works only on the fields in the filter, and

DET NORSKE VERITAS

28 Aug. 02

User Manual
ORBIT Offshore V2.2

Page 41 of 77
Revision 03

the filter can be applied using the Filter function or the explorer bar. Replace works only for the
Parts table and Degradation Mechanisms table.
Copy and paste by use of CTRL-C, CTRL-V can be used to insert the correct values into the replace
form, bearing in mind that the computer requires precise spellings, including spaces, to correctly
identify what is to be replaced, and that the relational database requires precise spellings to allow
replacements in many of the fields.

7.4.4 Edit Copy, Paste

Edit->Copy Special and Edit->Paste Special
Data can be copied to the clipboard from electronic sources and pasted directly into ORBIT
Offshore. Note that this function allows copying of whole lines of data as selected by the View
Fields function to or from the tables. Data copied from ORBIT is pasted into other programs with
the column headings present.
Data that is to be copied from other programs and pasted into ORBIT should be ordered as the
columns in ORBIT are ordered, and the data type checked so that you do not attempt to paste text
into a numeric field.
Edit->Copy Record and Edit->Paste Record
This allows the copying and pasting of a line of data in the table being worked on. It is particularly
useful in creating almost-duplicate parts, where the original part can be created with all parameters
for PoF and CoF calculation, copied and pasted, and the specific data changed quickly.
7.4.5 Sort
View Sort
This function sorts the column selected into firstly alphabetical order, then if applied again, into
reverse alphabetical order. Search can also be accessed by clicking on the column header.

DET NORSKE VERITAS

User Manual
ORBIT Offshore V2.2

28 Aug. 02

Page 42 of 77
Revision 03

8. CONFIGURATION
8.1 Introduction
ORBIT Offshore comprises a relational database. This allows one call from the main parts table to
a background table, where there may be a considerable amount of data, to use that data. This
avoids repetitive entry of all the data for each part, speeding the configuration process and reducing
the possibility of errors.
The configuration process requires that these background tables are completed before the parts
table, as otherwise these referential links will return error messages that the data referred to is not
present.

8.2 Why configuration?

Before entering all the equipment and part data it is necessary to fill out a number of background
tables containing common data that relates to the equipment and parts. These table effectively fill
out the dropdown lists in the Parts table. These background tables cover the following:

Insulation
Coatings
Materials
Product Services
System codes
Function codes

The last four groups will also appear in the ORBIT Explorer and used as quick filters in the parts
table.
Additional tables are:
Objects this describes the type of object the part is a part of;

8.3 Description of Background tables

8.3.1 Fixed values for tables
ORBIT Offshore uses three fixed descriptions that have a specific meaning. These are:
No

it is known positively that the item/condition is not present

Unknown

it is not known whether the item/condition is present or not (ORBIT applies rules to
determine worst case when this is specified)

Yes

it is known positively that the item/condition is present

If you use another code with a meaning as listed above, it is possible that you can get false results;
for example, to specify Insulation = 0 (zero), with the intention that insulation is not present,
ORBIT will take this as meaning that insulation IS present, and calculate accordingly.

DET NORSKE VERITAS

User Manual
ORBIT Offshore V2.2

28 Aug. 02

Page 43 of 77
Revision 03

8.3.2 Installation
Data Installation
This table gives basic information regarding the installation, its owners, operators, throughput, and
defines the safety and economic risk acceptance criteria. These last two figures are used in the
inspection planning, so that the risks for each part are maintained below these figures. In addition,
the various levels of production affected by a leak are defined.
The data required is:
Field
Installation name
Description
Position
Owner
Operator
Build year
Design life
Throughput oil
Oil price
Throughput gas
Gas price
Analysis year
Current year
Safety risk limit
Economic risk limit
Currency
Cost of Fatality
Production Affected
name
Description
Cost per day

Description
The name of the installation. Max 20 characters
Installation description. Max 50 characters
Location of the installations. Max 50 characters
Installation owners name. Max 50 characters
Operator name. Max 50 characters
Year when the installation was built. Default value used in corrosion calculations if
installation date not given.
Design life of the installation. Used as information only.
Throughput of oil in barrels per day. Used as information.
Oil price in currency units selected. Used as information.
Throughput of gas in million standard cubic metres per day. Used as information.
Gas price in currency units selected. Used as information.
The year at the end of the inspection planning period.
The year when the analysis should be carried out usually the start of the inspection
planning period.
Risk acceptance limits for safety risk per part.
Risk acceptance limit for economic risk per part, in the currency units selected.
Choice of currency unit.
If selected, this will include the cost per fatality into the economic consequence calculations.
The name given to the amount of production affected by a leak. This will depend on the
installation process design and the number of parallel trains. Max 20 characters. Used in
calculation of deferred production costs as part of ignited CoF calculation.
Further description of the production affected name. Max 50 characters
Cost of the production lost over 24 hours period. This is used in calculating the cost of
production lost during repairs. Manual input is required.

DET NORSKE VERITAS

User Manual
ORBIT Offshore V2.2

28 Aug. 02

Page 44 of 77
Revision 03

8.4 Probability of Failure tables

8.4.1 Insulation Types
Data TechnicalInsulation Types
This table defines the insulation types, and whether corrosion and stress corrosion under insulation
are likely. Any insulation that can affect these factors must be entered: included but not limited to
hot and cold thermal, and acoustic insulation, personnel protection and fire protection.
For assessment of possible corrosion and stress corrosion, the important factors are whether
insulation is present at all and, if present, whether it can retain water if it becomes wet. Mineral
wool, pearlite and similar can be expected to retain water hence supporting corrosion and stress
corrosion under insulation. New cellular-glass systems are impervious and adhere securely to the
metal surface and are not expected to retain water.
The data required is:
Field
Insulation Type
Description
Water Retaining

Description
Text field. Appears as pull-down menu in parts table.
Max 20 characters.
Text description of the insulation for information.
Max 50 characters
Yes/No field. Indicates whether insulation type can retain water. If there is any doubt then
use YES

ORBIT contains three default insulation types that must NOT be deleted. They are used as defaults
as follows:
No

it is known positively that insulation is not present

Unknown

is not known whether insulation is present or not ( ORBIT applies rules to determine
worst case when this is specified)

Yes

it is known positively that some kind of insulation is used

DET NORSKE VERITAS

User Manual
ORBIT Offshore V2.2

28 Aug. 02

Page 45 of 77
Revision 03

8.4.2 Coating Types

Data TechnicalCoating Types
This table defines the external coating type types. Internal coatings are not handled in the current
version. If there are coatings, data must be entered. These are used to assess the mitigation effect a
coating can have on external corrosion, and can be used to aid fabric maintenance planning.
Typically, the installation operator has specific coating systems for various types of equipment.
ORBIT assumes that coatings will deteriorate over time, thus providing an accumulative lower
protection in time following a profile based on a period of near-perfect protection, (specified in
FullProtectionYears) followed by a period where protection deteriorates to no significant
protection, specified in AgeNoProtectionYears ). See figure below for graphical description of
this.

%effective
100

Age no protection

Full
protection
0

Years

It is necessary to consider the performance of coatings on the installation, including consideration

of fabric maintenance. Regular re-painting, e.g. every 2 -3 years, may ensure that coating is always
in near perfect condition at all times. Poor surface preparation can infer that surface never
experiences near perfect protection, and deterioration starts from new. In this case the
FullProtectionYears is set to zero.
The data required is:
Field
Coating Type
Description
FullProtectionYears
AgeNoProtectionYears

Description
Text field that appears in parts table
Max 20 characters
Optional description field. May be used to describe coating specification, colour, etc.
Max 50 characters.
Period from coating application that the coating is effectively perfect.
Period after application after which coating is effectively useless.

DET NORSKE VERITAS

28 Aug. 02

User Manual
ORBIT Offshore V2.2

Page 46 of 77
Revision 03

ORBIT contains three coating types are used as defaults as follows:

No

it is known positively that no coating is present, no protection is used.

This must NOT be removed.

Unknown

it is not known whether coating is present or not (ORBIT assumes that no protection
is afforded. It applies rules to determine worst case when this is specified).
This must NOT be removed.

Yes

this is a default coating, with a 5 years period of near-perfect protection, followed by

10 years where coating deteriorates to having no significant protection. This coating
type must be reviewed for each installation and the deterioration profile changed as
considered appropriate to the specific case. It may be replaced with specific
coatings(s) or may be retained as a default for a non-specified but positively
identified coating.

Note that "Unknown" and "No" have same effect on the assessment of corrosion, however, an
"unknown" presence of coating implies that a check may be worthwhile based on the estimation of
risk, because a confirmation that a coating is used will lead to a reduction of the estimated risk.

DET NORSKE VERITAS

User Manual
ORBIT Offshore V2.2

28 Aug. 02

Page 47 of 77
Revision 03

8.4.3 Pipe classes (Optional)

Data TechnicalPipeClasses
This table defines piping sizes, materials and design limits, and is the equivalent of the piping data
sheet. Use of the Pipe Class table is optional.
If you decide to use pipe class, the pipe class table must be filled out before pipe classes appear in
the dropdown field in the Parts table. The Pipe class table contains design values for dimensions
and pressures, and is referred to by the Parts table where these values are missing from the Part
data. Pipe class data will be used only when it is referenced in the part AND equivalent data is not
entered in the parts fields.
Data entered into directly for the part in the Parts table takes precedence over the data referenced in
a pipe class.
The data required is:
Field
Pipe Class
Description
Nom Diameter
Design Diameter
Diameter Tol
Diameter Unit
Nom Wall Thick Mm
Design Wall Thick Mm
Wall Thick Tol Mm
Material Name
Max Design Temp C
Min Design Temp C
Max Design Pressure Bar
Min Design Pressure Bar

Description
Description of pipe class. Max 20 characters. Appears as pull-down menu in Parts table
Text description of pipe class Max 50 characters.
Nominal diameter of the pipe.
The specified tolerance in mm of the diameter
Tolerance in diameter allowed by the specification.
Units in which the diameter is measured. Text field
Nominal wall thickness in mm. This can often be greater than the design value due to
convenience in purchasing or site materials control.
Design specified wall thickness in mm
The specified tolerance in mm of the wall thickness
Pipe material. Appears as pull-down menu; name must be defined as Material Name in
Materials table
Maximum allowed design temperature for material
Minimum allowed design temperature for material
Max design pressure at design maximum temperature
Min design pressure at design minimum temperature

Note that Design Pressure and Design Temperatures given in Pipe Classes generally refer to
performance limits of materials and piping, and not to the expected operational limits in specific
application. If Pipe Classes are used then Design Pressure and Temperature will be used in the
absence of Actual and Operating values in the Parts table, an the result is expected to be
conservative.

DET NORSKE VERITAS

User Manual
ORBIT Offshore V2.2

28 Aug. 02

Page 48 of 77
Revision 03

8.4.4 Functions (Optional)

Data TechnicalFunctions
The Functions provide an optional table to fill out a dropdown field in the Parts table. Functions can
be usefully used to facilitate a grouping, or to add details to parts, e.g. . a weld location, or to
provide text descriptions of parts such as vessel, filter housing.
The data required is:
Field
Function Code
Description

Description
A text description of the function of a part.
Max 20 characters
Further explanation of the function code.
Max 50 characters

DET NORSKE VERITAS

User Manual
ORBIT Offshore V2.2

28 Aug. 02

Page 49 of 77
Revision 03

8.4.5 Product Service Codes

Data TechnicalProduct Service
ORBIT Offshore uses product service codes to control which internal degradation mechanisms are
expected. The table allows definition of the Client or User product service code in terms of the
codes recognised by the software, and selection of the appropriate water category (for utility water
systems only) and internal degradation mechanism.
Product service codes are expected to vary from installation to installation and client to client, and
so ORBIT Offshore provides for a "standard" set of codes that are recognised by the software
routines and a user- or client-defined set of codes (that is recognised by the user and is generally
found on drawings and other documentation). Similarly, the user codes can be presented in ORBIT
Offshore reports.
Initially, the user Code is identical to the DNVcode, but it is necessary to review and edit codes for
the installation. Note that the installation may use the same codes for different fluids; in particular
PW may be used for produced water or potable water. The Fluid type varies for several product
services, e.g. Fresh Raw water may actually be seawater, upstream the evaporator. The default
DNVFluidType is given for several systems, similarly the default expected degradation
mechanisms are set "Yes" for each fluid. The DNV settings cannot be changed, but users can add
and change fluids and the degradation mechanism settings in users area on the right side of the
screen. The users' allocation of fluids and internal degradation mechanisms will take precedence
over the default.
The data required is:
Field
Code
Description
DNV Code
DNV Fluid Type &
Next 10 rows
Fluid type
Next 10 columns
Comment

Description
User-defined product service code
Text description of the meaning of the product service code
DNV product service code equivalent to the contents of the user code.
These are fixed DNV expectations as to the type of utility water and the degradation
mechanisms for that product service code.
This is over-ridden by the selection of the next columns.
Type of water appropriate for utilities water systems. Select from pull-down menu.
Select whether the titled degradation mechanism is appropriate for that product service code,
having regard to the materials of construction
Comments field allowing notes to be made explaining the evaluation

The user Code must be checked edited and "mapped" to the appropriate DNVcode based on the
description shown in the table.
As the codes control allocation of degradation mechanisms it may be effective to define new
codes to split fluids more finely, such as wet and dry air, or wet and dry gas.
The user-defined degradation mechanism selection overrides the DNV proposed degradation
mechanism selection.

DET NORSKE VERITAS

28 Aug. 02

User Manual
ORBIT Offshore V2.2

Page 50 of 77
Revision 03

Review the settings for fluids and degradation mechanisms, edit as necessary
It is preferable that a Screening is performed by assessing each system is turn. In some cases
systems may be poorly defined, or identical to Product Service groups. In these cases Screening
may be carried out by assessing each Product Service group in turn.

DET NORSKE VERITAS

User Manual
ORBIT Offshore V2.2

28 Aug. 02

Page 51 of 77
Revision 03

8.4.6 Materials
Data TechnicalMaterials
This table defines the materials types and their corrosion and mechanical properties. ORBIT uses a
list of basic materials types to assess degradation mechanisms, e.g. it is assumed that all C and CMn steels corrode at same rates. However, ORBIT uses the strength of materials to calculates the
pressure retaining capacity, and a selection of materials types are given with default yield and
tensile strength that are conservative. ORBIT cannot estimate risk on a part without a material. In
the absence of better data, the default materials can be assigned to parts, at least for an initial
assessment. It is preferable that correct materials are included in the materials table together with
their strength, so that more accurate strength calculations are carried out.
The data required is:
Field
Material Name
Description
DNV Material Name
Next 3 columns
Last 3 columns

Description
User-defined material name. Stick as closely to the material specification name as
you can. Max 40 characters. Appears as pull-down menu in Parts table.
Text description of the user-defined material. Max 50 characters
The DNV material that is the closest equivalent to the user material. select from pulldown menu. This gives a link to the corrosion models.
DNV-defined mechanical and fracture properties
User-defined mechanical and fracture properties that over-ride the DNV values.

The table contains in excess of 130 frequently-found Offshore standard materials from ASTM,
API, ASME and BS. More can be added as desired.
Avoid using Other Material as far as possible as this contains no default data and will always
return a very high failure probability.

DET NORSKE VERITAS

User Manual
ORBIT Offshore V2.2

28 Aug. 02

Page 52 of 77
Revision 03

8.4.7 Systems
Data Systems
This table defines the systems on the installation, It is common, though not always the case, that
installations have equipment and piping grouped into systems with a specific purpose, e.g. a gas
recompression system, or a water injection system. These systems are generally given a code, and
are useful in the analyses because the consequences of failure is usually the same for the entire
system. It should be apparent that a system may comprise equipment that boundaries on other
systems, and/or has equipment with different product services. The gas compression system may
utilise instrument air, and seal oil, and if there is a failure in these two then an outage can be
expected in the gas compression system.
The data required is:
Field
System code
Description
Comment
PoF Comment
CoF comment
Installation year
Design Life Years
MIC diagnosed
MIC Cleaning
MIC deadlegs controlled

Description
System code or description as used in platform system designation. Max 20 characters
Description of the system. Max 50 characters
Memo field. This is intended as a commentary on the overall RBI results for the system aimed
at the inspection planning, and is printed in the System Summary report.
Memo field. This is intended as a commentary on the overall PoF analysis results for the
system, and is printed in the System Summary report.
Memo field. This is intended as a commentary on the overall CoF analysis results for the
system, and is printed in the System Summary report.
Year of installation. Only used if the Installation year is not filled out in the Parts table
Design life. For information only.
Optional text field relating to microbial corrosion assessment. Max 20 characters
Optional text field relating to microbial corrosion control. Max 20 characters
Optional text field relating to microbial corrosion control. Max 20 characters

Some data may be added with each system:

Installation year:
year when the systems was installed. This may be used if a platform has been revamped or new
processing has been added. This allows all the parts in the system to be assigned the same age as the
system to which they belong. (Parts can still be given an individual installation year to provide an
individual age if appropriate.) If no value is given the platform age will be used.
MIC Diagnosed and controlled:

Typically MIC is related to a system, and this information (good or bad!) can be added to the entire
system.

DET NORSKE VERITAS

User Manual
ORBIT Offshore V2.2

28 Aug. 02

Page 53 of 77
Revision 03

8.4.8 Corrosion groups

Data Groups
This table defines the corrosion groups. It is expected that corrosion conditions should be as close
as possible to being the same for all parts within the group, with the intention that a wall thickness
loss measured in one part is likely to be the same in all other parts. Normally, this is restricted to
internal corrosion, as the combination of NDT with visual inspection will allow corrosion wall loss
externally to be determined separately from that internally. The group name is also used in the
Inspection Frame programme report.
We recommend that, for Objects that are not Pipe, the Group name for the Object be made the same
as the Object name. This will ensure that the Frame programme report will identify individual
equipment items requiring inspection instead of highlighting parts of those equipment items. This
will make the report easier to understand.
The data required is:
Field
Group Name

Description

Description
User-defined group name. It is expected that corrosion conditions should be so close
as possible for all parts within the group, with the intention that a wall thickness loss
measured in one part is likely to be the same in all other parts. Max 20 characters.
Appears as pull-down menu in Parts table. DNV suggest that the stream number
from the process flow diagrams be used for identification to maintain labelling
consistency wherever possible.
Text description of the user-defined group. Max 250 characters

DET NORSKE VERITAS

User Manual
ORBIT Offshore V2.2

28 Aug. 02

Page 54 of 77
Revision 03

8.5 Consequence of failure tables

8.5.1 Repair categories
Data Unignited LeaksRepair categories
This table defines the methods used for repair of leaks on the installation, and is cross-referred to
the Repair Categories Properties table and the Parts table. The repair categories are used to define
the downtime and thence lost production if a leak of defined size occurs in each part of the pressure
system. The data required is:
Field
Repair Category

Description

Description
The name of the repair category. Links to the repair for each hole size for each part in the
Parts table.
Max 20 characters
Text description of the repair category. Used for information.
Max 50 characters.

DET NORSKE VERITAS

User Manual
ORBIT Offshore V2.2

28 Aug. 02

Page 55 of 77
Revision 03

8.5.2 Repair category properties

Data Unignited LeaksRepair categories Properties
This table defines, for each repair category, the downtime in hours that would be expected to result
whilst a leak is repaired in each component. This does not account for the contents of the system
needing repair for example, hydrocarbons systems requiring repair normally need making safe
prior to work beginning. This is taken care of in the production loss definitions.
The data required is:
Field
Repair Category

Diameter Mm
Description
Downtime Hours

Description
The name of the repair category. Defined in the Repair Category table, and is given as a
pull-down menu.
Max 20 characters
The diameter up to which the repair category and downtime combination are applicable.
Given in millimetres, with one decimal place.
Text description. Used for information.
Max 50 characters.
The number of hours downtime associated with the repair category and part diameter.
Given in hours.

DET NORSKE VERITAS

User Manual
ORBIT Offshore V2.2

28 Aug. 02

Page 56 of 77
Revision 03

8.5.3 Production loss profiles

Data Unignited LeaksProduction Loss Profiles
This table defines the production loss profiles relevant to the installation, by assigning names and
descriptions. The production loss profile is used to calculate the value of lost production that would
arise from shutdown and repairs when a leak has occurred. Different installations have different
profiles, depending on the plant design and numbers of parallel trains, the capacity of each train (3 x
50% capacity would have no production loss if one train is unserviceable, for example), and the
effect of utilities failures on production.
The data required is:
Field
Prod Loss Profile Name

Description

Description
Text field labelling the production loss profile. Appears as a pull-down menu in the Parts
table and production loss profile properties table.
Max 20 characters
This is a text field allowing a more detailed description of the production loss profile.
Max 50 characters

DET NORSKE VERITAS

User Manual
ORBIT Offshore V2.2

28 Aug. 02

Page 57 of 77
Revision 03

8.5.4 Production loss profile properties

Data Unignited LeaksProduction Loss Profile properties
This table defines the production loss profile in terms of time and production lost. This can
comprise up to 4 intervals.
Normally, in the case of a hydrocarbon leak, there would be a period following the leak when the
installation is made safe, the leak is investigated, repairs planned and permits-to-work are raised.
During this period it is likely that there is no production. Thereafter, if there is parallel production
trains, production can be raised to a certain level whilst repairs are carried out to the damaged parts,
thereafter production is brought up to 100%. This is shown schematically below.

Full production

100
d%
A

c%
b%

Time

A: Stop following leak. Zero % production

B: Ramp up to partial production
capacity over a specified time. Average
production = b%
C: Partial production continues whilst
repairs are carried out. Production =
c%
D: Ramp up to full production after
repair in a specified time. Average
production = d%
E: Continue production at 100%
capacity

For each production loss profile name, the last interval defined (the one with the greatest interval
number) is the one in which ORBIT Offshore assumes that the repair takes place, and then refers to
the Repair Category properties to find the actual time used in the repair. To prevent time restriction
here, it is normal that the number 99999 is entered.
The data required is:
Field
Production Loss Profile Name
Interval number
Time Interval Hours
Prod %

Description
The production loss profile name. A pull-down menu allowing selection from the
Production Loss profiles table only.
The interval over which an amount of production can be defined. Integer number,
can range from 1 through 4.
The duration of the interval, expressed in hours. Can be a decimal if required.
The average percentage production that can continue within the interval. The area
is calculated, therefore a triangular section has an area of base time x height.

Other than the last interval being the one where the repair is expected to take place, the order of the
intervals is immaterial, as ORBIT calculates the areas under the lines (shaded in the diagram
above), and clearly the area is unaffected by the order in which the components are summed.

DET NORSKE VERITAS

28 Aug. 02

User Manual
ORBIT Offshore V2.2

As an example, the above shows the following for the production loss profile 0%:
Interval number
1
2
3

Description
0% production in 12 hours whilst the cause of the failure is investigated
12 hours run-up time from 0% to 100% (50% average production)
0% production during a repair time that is given by the Repair Category
Properties for the part concerned

DET NORSKE VERITAS

Page 58 of 77
Revision 03

User Manual
ORBIT Offshore V2.2

28 Aug. 02

Page 59 of 77
Revision 03

8.5.5 Leak sizes

Data Ignited LeaksLeak sizes
This table defines the risk analysis cases to be considered. If the ORBIT Offshore simplified QRA
is to be used, four hole sizes are defined, and therefore four analysis cases must also be defined. If
an external QRA is to be used, then the number of cases should be the same as those applicable in
that QRA.
The data required is:
Field
Leak Size Name

Description

Description
Text field labelling the case name. This is used as pull-down menu in the Segment Leak size
table.
Max 20 characters
Text field. Further description of the case name.
Max 50 characters

DET NORSKE VERITAS

User Manual
ORBIT Offshore V2.2

28 Aug. 02

Page 60 of 77
Revision 03

8.5.6 Extents
Data Ignited LeaksExtents
This table defines the extent of damage resulting from an ignited leak. Four cases are used when
using the simplified QRA in ORBIT Offshore, but more can be defined if using an external QRA.
The data required is:
Field
Extent name
Description

Description
Label for the extent of damage. Used as pull-down menu in the Segment Extents table.
Max 20 characters
Further description of the extent name.
Max 50 characters.

DET NORSKE VERITAS

28 Aug. 02

User Manual
ORBIT Offshore V2.2

Page 61 of 77
Revision 03

8.5.7 Segment extents

Data Ignited LeaksSegment Extents
This table defines the economic end events resulting from an ignited leak from each segment
according to the Extent Names already defined in the Extent table and the segments defined in the
Segments table. This requires input of the cost of materials in the currency units defined in the
Installation table, and the production downtime in days for that extent name due to the damaged
equipment, area, neighbouring area and installation.
The data required is:
Field
Segment Name
Extent name
Material Cost
Prod Downtime Days
Prod Affected Name

Description
Segment name as defined in the segments table. Pull-down menu
Extent name as defined in the Extents table. Pull-down menu
Cost of materials and labour to repair the Extent damage
Days lost production whilst repairs are carried out
Optional field. Pull-down menu from the Production Affected table.

DET NORSKE VERITAS

User Manual
ORBIT Offshore V2.2

28 Aug. 02

Page 62 of 77
Revision 03

8.5.8 Segment Leak Sizes

Data Ignited LeaksSegment Leak Sizes
This table defines the safety consequences of a leak from each segment according to the Leak Size
Names already defined in the Leak Sizes table and the segments defined in the Segments table.
If the ORBIT Offshore simplified QRA is used, this table need not be filled out, but if an external
QRA is used, the combination of segment and leak size name and hole size requires the PLL to be
defined.
The data required is:
Field
Segment Name
Leak Size name
Hole Size mm
PLL Given Leak

Description
Segment name as defined in the segments table. Pull-down menu
Leak Size name as defined in the Leak Size table. Pull-down menu
Hole size in millimetres Type in as a number. Optional input.
The PLL figure assuming that the probability of failure = 1.00, i.e. the top event has
occurred.

DET NORSKE VERITAS

User Manual
ORBIT Offshore V2.2

28 Aug. 02

Page 63 of 77
Revision 03

8.5.9 Segment Leak Size Extents

Data Ignited LeaksSegment Leak Size Extents
This table defines the probabilities for the combinations of segment, leak size name and extent
name i.e., defining the branch probabilities of the economic end events from a leak from each
segment.
If the ORBIT Offshore simplified QRA is used, this table need not be filled out, but if an external
QRA is used, the combination of segment and leak size name and extent name requires the
probability of that combination to be defined.
The data required is:
Field
Segment Name
Leak Size name
Extent name
Prob Of Event

Description
Segment name as defined in the segments table. Pull-down menu
Leak Size name as defined in the Leak Size table. Pull-down menu
Extent name as defined in the Extents table. Pull-down menu.
The probability of the extent of damage occurring for each combination of segment
and leak size.

DET NORSKE VERITAS

User Manual
ORBIT Offshore V2.2

28 Aug. 02

Page 64 of 77
Revision 03

8.6 Inspection Planning

8.6.1 Inspection tasks
Configure Inspection PlanningInspection Task
This table defines the inspection tasks, and assigns costs to these. The task can be either a single
inspection method, or a number of these, although in the latter case, more judgement has to be
exercised as to how to assign a PoD curve in later tables.
ORBIT Offshore calculates the inspection plan by calculating the risk reduction following
inspection for each part and degradation mechanism by applying each inspection task listed as
applicable for that degradation mechanism, and selects the task that gives the greatest risk reduction
per cost unit. This does not necessarily result in the greatest risk reduction, but the cheapest
reduction in risk.
The data required is:
Field
Insp Task

Insp task description

Cost factor

Description
User-defined inspection task name. Can be related to technique, or use existing inspection
procedure name.
Max 40 characters.
Memo field allowing input of the task description.
Numeric field giving a cost rating in relative units, absolute financial or time units of your
choice. No units need be stated. This should be adjusted according to local circumstances
and manpower and maintenance costs, such as removal and reinstatement of insulation.

DET NORSKE VERITAS

User Manual
ORBIT Offshore V2.2

28 Aug. 02

Page 65 of 77
Revision 03

8.6.2 Inspection Effectiveness

Configure Inspection PlanningInspection Effectiveness
This table defines the effectiveness of each inspection task in detecting each degradation
mechanism, assigns a PoD curve and an effectiveness value. The effectiveness values are
judgement-based, and defined according to the list on the right-hand side of the screen. The data is
used in calculating risk after inspection.
The data required is:
Field

Description

Insp Task

Pull-down menu allows a choice of the inspection task as defined in the

Inspection task table

Deg Mech name

Pull-down menu allows a choice of degradation mechanism from all those

considered by ORBIT Offshore

PoD Curve

Pull-down menu allows a choice of the PoD curve names as defined in the
PoD table

Effectiveness

Pull-down menu allows a choice of one of five effectiveness descriptions

that are defined on the right of the screen

DET NORSKE VERITAS

28 Aug. 02

User Manual
ORBIT Offshore V2.2

Page 66 of 77
Revision 03

8.6.3 PoD Curves

Configure Inspection PlanningPoD Curves
This table defines the probabilities of detection for all inspection methods, and is used in calculation
of the risk reduction after inspection based on the expected extent of damage. A number of curves
are pre-defined based on data available to DNV, and additional curves can be user-defined
according to need, and available data.
The curve is defined in the form PoD = 1-1/(1+(X/Xo)b)
And is plotted at the bottom of the window for information
The data must be entered before the inspection effectiveness table can be completed.
The data required is:
Field
PoD Curve
PoD Curve Description
X0Constant
B Constant
Accuracy Mm

Description
Description of the curve.
Max 40 characters
Memo filed where the description of the PoD curve can be entered.
Xo constant in the PoD curve equation
B constant in the PoD equation
The inherent accuracy in the measurements using that technique

DET NORSKE VERITAS

28 Aug. 02

User Manual
ORBIT Offshore V2.2

Page 67 of 77
Revision 03

8.7 Matrix Definition

8.7.1 Risk Matrix Design
Configure Risk Matrix Design
Allows design of the risk matrix to suit each operators requirements. The number of rows and
columns can be selected by changing the Dimensions in the top left corner to a maximum of 5 x 5.
The PoF and CoF category limits entered in the cells on each axis. The qualitative definition of risk
(as low, medium, high etc) can be selected in the pull-down menu in each cell.
The matrix can also be defined by direct editing into the Configuration tables as shown in the
following sections.
For consistency with the technical basis outlined in DNV RP-G 101 on which the ORBIT method is
based, DNV recommend strongly that the PoF limits are increased in decades for each category
from 10-5 to 1, with the category 5 being two decades (10-2 through 1).

The risk category names are changed as defined in 8.7.4

DET NORSKE VERITAS

User Manual
ORBIT Offshore V2.2

28 Aug. 02

Page 68 of 77
Revision 03

8.7.2 Probability categories

Configure CategoriesProbability categories
This table defines the probability categories for the risk matrices. Probability of failure is common
for each risk category (Safety or economic), and so only one definition is needed.
The data required is:
Field
Prob category No
Name
Up To Limit

Description
Numbering of the matrix row. Smallest number is lowest probability. Cannot be edited.
The row label that is printed on the matrix.
Max 20 characters, but best kept as short as possible
Max. value of probability of failure for the row.
Numeric field, less than 1

DET NORSKE VERITAS

User Manual
ORBIT Offshore V2.2

28 Aug. 02

Page 69 of 77
Revision 03

8.7.3 Consequence categories

Configure CategoriesConsequence categories
This table defines the limits for each consequence column on the safety risk matrix and economic
risk matrix. This should be defined such that the lowest consequence category, numbered 1, has the
same value as the consequence of failure limit used in the screening analysis where the probability
of failure is assumed to equal 1.0 i.e., the same as the risk limit.
The data required is:
Field
Conseq category No
Name

Up To Limit
Up To Limit PLL

Description
Numbering of the matrix column. Smallest number is lowest consequence.. Cannot be edited.
The column label that is printed on the matrix. Note: this is the same label for safety and
economic consequence
Max 20 characters, but best kept as short as possible
Max. value of Economic consequence for the column
Numeric field
Max value of Safety consequence for the column
Numeric field

DET NORSKE VERITAS

User Manual
ORBIT Offshore V2.2

28 Aug. 02

Page 70 of 77
Revision 03

8.7.4 Risk categories

Configure CategoriesRisk Categories
This table defines the risk categories, gives them user-defined names, and allows changes in the
colour used on the matrices when displaying or printing. It is not normally necessary to edit this
table.
The data required is:
Field
Risk category No
Name
Red
Green
Blue
Color

Description
Numeric field. Cannot be edited or added to.
Text field giving risk level. Printed on matrices and in inspection reports.
Max 20 characters
Red proportion of the colour
Green proportion of the colour
Blue proportion of the colour
Description of the colour

DET NORSKE VERITAS

User Manual
ORBIT Offshore V2.2

28 Aug. 02

Page 71 of 77
Revision 03

8.7.5 Risk Matrix definition

Configure CategoriesRisk Matrix definition
This table allows redefinition of the risk levels for each cell in the risk matrix. It is not expected that
adjustment here is necessary.
The data required is:
Field
Prob Category No
Conseq Category No
Risk Category No

Description
Numeric. Relates to the category defined in the Probability categories table
Numeric. Relates to the category defined in the Consequence categories table
Numeric. Relates to the category defined in the Risk categories table

DET NORSKE VERITAS

User Manual
ORBIT Offshore V2.2

28 Aug. 02

Page 72 of 77
Revision 03

8.8 Other Definitions

8.8.1 Hole sizes
Configure Hole sizes
This table allows definition of the hole sizes to be used in the consequence calculations. It should
not be necessary to adjust these values unless it is necessary that they correspond to a previouslyexecuted QRA Note that these holes sizes are also those that result from the leak outcome from the
degradation models, and so changes here may make the materials degradation data unrealistic.
The holes size table is Read-only for users without administrator rights
The data required is:
Field
Hole size
Name

Diameter Mm

Description
Numeric field. Cannot be edited.
Description of the leak size. This is used in the consequence of failure calculations as
scenario labels.
Max 20 characters
Maximum diameter of the hole. If the part diameter is less than that of the hole, the part
diameter is used instead
Numeric field.

DET NORSKE VERITAS

User Manual
ORBIT Offshore V2.2

28 Aug. 02

Page 73 of 77
Revision 03

8.8.2 Status definitions (Optional)

Configure Status definitions
This table allows definitions of user-defined status to be used in the Parts table. This allows, for
example, the process of analysis to be tracked or quality check information to be given, on a partby-part basis. Filling-out of this table is not mandatory unless status definitions are to be used in the
Parts table.
The data required is:
Field
Status
Description

Description
Text field. Links to Parts table.
Max 20 characters
Text description of the part status.
Max 50 characters

DET NORSKE VERITAS

28 Aug. 02

User Manual
ORBIT Offshore V2.2

Page 74 of 77
Revision 03

8.9 Protected Data

Administrator rights (Security tab on ToolsOption ) are needed to alter any of the data
described in this section, users may view the data as read-only.
NB!

The data is central to ORBIT Offshore calculations. Changing the data may cause the
program to produce unexpected results or prevent calculation.

The data is accessed through the lower part of the Configure menu.

8.9.1 DNV Materials

Configure DNV Materials
Contains the DNV-defined mechanical and fracture properties for a number of materials and a link
to the corrosion model to be applied. See also section 8.4.6.
This menu option is visible only to users with admin rights.
8.9.2 DNV Product Services
Configure DNV Product Services
Product service codes control which degradation mechanisms are expected where. Product service
codes are expected to vary from installation to installation and client to client, and so ORBIT
Offshore provides for a "standard" set of codes that are recognised by the software routines. See
8.4.5 for how to set up a user- or client-defined set of product service codes.
This menu option is visible only to user with admin rights.
8.9.3 Object Types
Configure Object Types
This defines the list of object types that can be assigned to objects in DataObjects.
8.9.4 Degradation
Configure DegradationDegradation Mechanism Definitions
Defines the available degradation mechanisms and link them to the degradation mechanisms
recognised by the software routines.
Configure DegradationDegradation Mechanism Properties
Links the available degradation mechanisms to damage type, model function and limit state and
defines the distribution of damage size (small, medium, large and rupture).
Configure DegradationDamage Type
Defines the available damage types.

DET NORSKE VERITAS

28 Aug. 02

User Manual
ORBIT Offshore V2.2

Page 75 of 77
Revision 03

8.9.5 Probability
Configure ProbabilityModel Function
Defines all available model functions (e.g. rate functions and S-curves). New model function
generally requires modifications to the program.
Configure ProbabilityModel Function Parameters
Defines the parameters for each model function.
Configure ProbabilityLimit States
Defines all available limit state functions. A new limit state requires new program code.
Configure ProbabilityLimit State Variables
Defines the parameters and default values for each limit state function.
Configure Distributions
Defines all available types of probability distributions. New distribution requires new program
code.
8.9.6 Configure Report
Configure Report allows the user to include logos in his report either on the top left hand side or
the top right hand side of the page. The logos should be in *.bmp image form

DET NORSKE VERITAS

28 Aug. 02

User Manual
ORBIT Offshore V2.2

Page 76 of 77
Revision 03

9. TROUBLESHOOTING
The following difficulties may be experienced:

9.1 Probability of failure = 1.00

If you find you get a probability of failure = 1.00 precisely, then there is either essential data
missing, or an error in the data that the software cannot resolve. Review the calculation Report in
the bottom half of the Parts table, or in the Degradation Mechanisms table, and this will advise what
is wrong. Refer also to the Working Procedures for guidance /1/.
Probability of failure is set to 1.00 in these circumstances so that the need for further action can be
governed by the consequence of failure; a low consequence of failure suggests that it may be a
waste of time engaging in costly data searching when the risk is small.

9.2 Cursor remains as Hourglass

On occasions, the cursor does not revert from the hourglass (used to show calculations are in
progress) to the arrow setting. This does not prevent ORBIT from operating, but can make it
difficult to see exactly what is selected. The program should be closed and restarted to re-set the
cursor.

DET NORSKE VERITAS

28 Aug. 02

User Manual
ORBIT Offshore V2.2

Page 77 of 77
Revision 03

10. REFERENCES

/1/

DNV report 99-3436 rev. 02 RBI Upstream: Working Procedures and Guidance,
DNV Hvik, May 2000

/2/

DNV Recommended Practice RP-G 101 Risk Based Inspection of Offshore Topsides
Static Mechanical Equipment, DNV Hvik January 2002.

DET NORSKE VERITAS