Step-by-step Tutorial - EIVA Download Sitedownload.eiva.com/online-training/Step_By_Step_Pipeinspection.pdf · At this point in the process the KP-window will include all the online

April, 2010

Step-by-step Tutorial

Pipeline Inspection within NaviModel3

NaviModel3

Step-by-step Tutorial, Pipeline Inspection with NaviModel3

EIVA Software Page 2 of 36 Rev. no. 0, 2010-04-23

INTRODUCTION

The purpose of the present Step-by-step Pipeline Inspection Processing Tutorial is to introduce the

various tools involved when carrying out a typical Pipeline Inspection Processing session with the

EIVA Hydrographic Software Suite, in a logical sequence.

Furthermore the step-by-step tutorial will also include aspects associated with eventing and it will

involve video integration. Though considered indispensable parts of a Pipeline Inspection

Processing task, both features will only be dealt with when considered essential for the

enhancement of the understanding of how the making of the pipe object is conducted i.e. how they

can be supporting the applicable decision making. Further details on the subject of eventing and

video integration can be found in the dedicated manuals in the EIVA Training & Documentation

Site http://download.eiva.dk/online-training. Relevant details regarding how to generate a DTM on

the basis on bathymetric data as well as aspects associated with the cleaning of such a model can

also be found on this site.

1. PREPARING NAVIMODEL3 FOR THE PIPE JOB

When preparing for a pipeline inspection session, the first thing to do is to start NaviModel3. At

start-up, NM3 will appear as shown below in Figure 1.

http://download.eiva.dk/online-training



Figure 1 NaviModel3 at start up

1.1 Loading and configuring the DTM

All data required for the pipeline inspection session must now be entered into NM3. First drag-and-

drop a cleaned digital terrain model into the DTM-window (see Figure 2). Now highlight the DTM

in the project tree and ensure that the colour mode ‘depth’ has been chosen in the properties panel

and that the ‘geometry mode’ (model type) has been set to minimum (see red arrows).



Figure 2 Step 1 DTM loaded

At this stage, the user should also choose the correct colour mode and light-settings. Colour mode

is defined by highlighting ‘Color modes – Depth’ in the project tree. The properties panel will now

show the default settings as shown below in Figure 3. In the middle, the custom settings are shown.

Palettes can be chosen from a drop-down list, and from-step-to can be entered manually from the

keyboard. Fade is a boolean (true/false). When true, NM3 will fade seamlessly between the colour-

ranges as shown below in Figure 4. Alternatively the user could click on the dedicated icon in the

toolbar . A selection window (Figure 3, right) will appear that will enable the user to select the

palette directly.

Figure 3 Defining colour mode – default (left) and custom (middle) and the ‘Pick Palette’ window (right)



Figure 4 Colour mode defined

The light setup is defined from menu-item ‘View – Light setup’ (or from the dedicated icon in the

toolbar ). When activated, the window below in Figure 5 will appear, enabling the user to choose

between a number of predefined settings or to define his own settings. Note that the settings in the

figure are associated with the default values.

Figure 5 Light setup

1.2 Loading and configuring the Toppings

Next drag-and drop the various toppings onto the DTM-Window. In the present context toppings

are: runline, pipe tracker data, track for the ROV and video data. The runline will appear as a green

line, whereas the ROV-track associated with the video-information will be visualised as a yellow



line, as can be seen in Figure 6 below. When entering 3D-models, the user is prompted whether or

not the model should be placed at a fixed position in the mode (see Figure 7). Answer ‘No’ to this.

Figure 6 Toppings loaded

Figure 7 3D-model prompt

Now the video-windows must be opened. This is done by choosing the menu item ‘View – Video –

Open all video windows’. Then move the camera position to an appropriate position on the DTM

and press the ‘Bring Video Here’ icon . This will open the video in the actual position – this is

visualised below in Figure 9. Note that at this stage, an empty event window will open at the

bottom far right of NM3. Also note that if the video windows are not opened prior to pressing the

‘Bring Video Here’ icon, the prompt shown below will appear, urging the user to open the video

windows.



Figure 8 Video window prompt

Figure 9 Video windows opened

The actual video position will be visualised, in the DTM-window, as a sphere with beams

underneath (see the red arrow). Note also that the videos are fixed in time at this stage, as indicated

by the video toolbar ( ). Pressing the -button, will cause the video to start advancing,

whereas the - and the - buttons will make the video step back and forth, respectively.

To attach a 3DS model to the video position, highlight the ‘Cursor’ item in the Project Tree

Window and choose ‘Attach…’ the appropriate 3DS-model here, as shown below in Figure 10.



Figure 10 Attach 3DS-model

Figure 11 NM3 with 3DS-model



The next thing to do is to load the events that were generated online. These might have been re-

calculated with respect to the modifications performed in NaviEdit. To import the events, choose

menu item ‘File – Import…’. This will open the window and the window to the left in Figure 12

will appear. Choose ‘Event Collection’ in the panel to the left, choose appropriate format in the

middle column (NaviEvent in the present context) and do one of the following: a) browse to select

the file to import or b) drag-and-drop a file (or a folder that contains a file) to import. The path will

appear in the field at the top of the form. Finally press the ‘Import’ button to activate the import in

accordance with the settings.

Note that if an appropriate template does not already exist, the user will have to generate one

himself. Details on how to do this can be found in the ‘Bathymetric Post-processing Tutorial with

NM3’ found on the EIVA Training and Documentation site.

Figure 12 ASCII import from - default (left) and with event collection selected (right)

Now the KP-axis window should be opened. This is done from the menu-item ‘View – KP-axis’.

At this point in the process the KP-window will include all the online events as well as the runline

(including range) and the video-track. Choose menu-item ‘Show’ from the KP-window and choose

which events and other items to visualise, as shown below in Figure 13. Figure 14 Shows

NaviModel after the KP-axis window is activated.



Figure 13 Show selection from KP-axis

Figure 14 NM3 including KP-axis & Events

The final thing to do before actually starting to generate the pipe object is to load the pipetracker

topping. Prior to that, however, the pipe tracker settings must be specified (see Figure 15,

below). Details on how to do this can be found in the ‘Bathymetric Post-processing Tutorial with

NM3’ found on the EIVA Training and Documentation site.



Figure 15 Pipetracker Settings in the ‘Project Settings’

To load pipe tracker data, drag-and-drop the appropriate, edited pipetracker information (in the

*.pip format) onto the DTM window of NM3. Observe that, as a consequence, there will appear

a pipetracker entry under the toppings item in the ‘Project Tree’ window and that there will

appear a new line in the KP-axis window as shown below in Figure 16.

Figure 16 Pipetracker and Kalman data in the KP-axis window

In the DTM window, the pipetracker information is visualised with a green line with points. That

is the pipetracker line with observations (points). The blue line, shown below in Figure 17, right,

represents the Kalman Line. If selected by the user, the Kalman line can be used to place the pipe

at a later stage of the process.



Figure 17 Pipe Tracker data loaded into NM3, 'Project Tree' window, left and DTM window together with the

Kalman Filtered line (right)

2. THE PIPE OBJECT

In general terms, determination of the pipe object involves modification of the pipe and of the

flags. This determination should involve the following, as a minimum:

Undesirable pipe bends/bending violations

Burial status (buried/exposed)

Freespans

Events versus pipe status

Video versus pipe status

Events versus Video

The three last items are only relevant in cases where events and video is available in support of

the pipe determination. However, if this is the case, it is highly recommended to use all

information available, in order to arrive at the best possible solution for the pipe as well as for the

events. The optimum pipe determination process is consequently one that, in an iterative process

and using all available information, also modifies the events achieved online and supplies these

with offline events. NM3 has comprehensive facilities for conducting offline eventing as well as

for editing of events. These are described in detail in the two dedicated manuals, ‘Online

Eventing Manual’ and ‘Offline Eventing Manual’ that can be found in the EIVA Training and

Documentation Site, http://download.eiva.dk/online-training/NaviPac%20-%20Tools.htm.

The pipe object will be generated, within NaviModel3, on the basis of a priority list that looks as

follows: 1) digitized pipeline 2) pipetracker data (or Kalman line) 3) runline. Consequently: only

http://download.eiva.dk/online-training/NaviPac%20-%20Tools.htm



when no digitized pipeline and no pipe tracker data is available, will the runline be used to place

the pipe and only when no digitized pipeline is available, will the pipetracker data be used for the

pipe.

At this stage, it must therefore be decided whether or not the pipetracker information is adequate

as basis of the pipe object. Alternatively the following can be conducted:

modification of the pipetracker data

digitization of the pipe object

2.1 Modification of the pipetracker data

To evaluate whether or not modification of the pipetracker data is required, start by making a fly-

through relative to the data. Click on the ‘Fly Mode’ icon in the ‘NM3 Standard Toolbar’ and

choose the pipetracker item in the drop-down menu that will appear. The speed of the movement

can be changed by pressing the + and –buttons next to the icon . Press the ‘Esc’ button

(when the DTM window is active) to exit the mode.

On the basis of the fly-through, pipe-tracker data must now be edited. NM3 contains a series of

tools for that:

definition of ‘Pipe Filter Flexibility’

choice of using pipe filter (yes/no)

validation/invalidation of pipetracker data

use of pipefixes

NaviModel3 will generate a Kalman line along the pipetracker path when pipetracker data is added

to a project. The smoothed line can be used to generate a new pipe added in situations where there

is no digitized line, provided the ‘Use Pipefilter’ has been set to ‘True’ (see above in Figure 18). If

this is not the case, the pipetracker data will be used directly to generate the pipe.

Figure 18 Project Settings – ‘Use pipefilter’



Apart from the pipetracker data, the Kalman filtered line is based on the pipetracker settings that

are defined in the ‘Pipe Tracker’ tab of the Project settings window, as shown above in Figure 15.

The default setting for the ‘Pipe Filter Flexibility’ is 0.2 cm/m, which means that the Kalman pipe

is allowed to bend 2 mm per meter.

The ‘Pipe Fix Point’ quality parameter is used to define the quality of pipe fixes. Pipe fixes are

points that can be made manually to assist and thereby to improve the pipe tracker data. Right-click

on the ‘Pipetracker’ entry under ‘Toppings’ in the ‘Project Tree’ window and choose the menu-

item ‘New pipe fixes’ as shown below in Figure 19.

Figure 19 'New Pipe Fixes' functionality

Pipe fixes can now be placed, with the mouse, in areas where the pipe tracker data must be

overruled. This is visualised below in Figure 20, where the pipe fixes are shown as white crosses.

Note that the Kalman line is close to the pipe fixes points and far from the pipetracker data.

Figure 20 Pipe fixes to assist the pipetracker data

Pipetracker data can furthermore be validated and invalidated by performing a manual selection.

Right-click on the ‘Pipetracker’ entry under ‘Toppings’ in the ‘Project Tree’ window and choose

the appropriate menu-item, either ‘Invalidate Pipetracker Data’ or ‘Invalidate Pipetracker Data’ as

shown below in Figure 21.



Figure 21 'Invalidate Pipetracker Data' and 'Validate Pipetracker Data'

The tool will now appear on the DTM window as a circle (see Figure 22, below, right). The radius

of the circle will determine the number of pipetracker points to be made invalid. Click with the left

mouse button whenever an appropriate selection has been made.

Figure 22 Invalidate tool. Selection (left) and after invalidation (right)

The validation tool works in exactly the same ways as the invalidation tool. As can be seen below

in Figure 23, the validated points are given the quality parameter 17, irrespective of their former

quality parameter, to indicate that they are to be regarded ‘Auto Placed Points’.



Figure 23 Validated points

2.2 Digitizing the pipe object

The pipe object must now be digitized in areas where the pipetracker data is missing or where it

has been deemed not adequate, even after the modification has taken place. The digitization tool

is used for defining the pipe location, and it will override all measured pipe tracker data. The

pipe will follow exactly along the digitized line. Consequently more points must be digitized in

curves than on straight sections.

NM3 has two functionalities designed for the digitization of the pipe object:

The ‘New Digitized Pipeline’ functionality

The ‘New Digitized Cover (NA)’ functionality

Prior to digitizing, the pipe diameter must however be specified, either in the ‘Project Settings’ as

shown below in Figure 24, left or in the ‘Properties’ window, as shown to the right in the same

figure.

Figure 24 Pipe Settings in the Project settings dialogue (left) and in the ‘Properties’ window (right)



The ‘New Digitized Pipeline’ functionality is invoked from the ‘Pipe Inspection’ toolbar or by

right-clicking in the ‘Toppings – Digitized Lines’ entry of the ‘Project Tree’ window and choosing

the menu item 'New digitized Pipeline' as shown below in Figure 25.

Figure 25 'New digitized Pipeline' menu option

Once the ‘New digitized pipeline’ functionality has been selected, the cursor in the DTM window

will have changed its appearance. Click in an appropriate position with the left mouse-button to

start the digitizing process. For each new additional pipeline segment, perform a left-click. To end

the process, either double-click with the left button or press the ‘Esc’ key on the keyboard. The

first action will add a new pipeline segment that ends in the position of the ‘double-click’, whereas

the latter will end the digitized pipeline at the position of the latest point.

To assist in the digitization, the relative range and bearing from the previous point in the line to the

present position of the cursor is visualised (see below). The bearing is of particular interest in

connection with digitizing pipe objects, since the angle between segments is used to flag for

bending violations. The default maximum allowable value is 3 degrees. This can be specified in the

‘Pipe Settings’ dialogue (see above in Figure 24), where the properties for the item ‘Acceptable

flexion of the pipe’ can be specified.

To further assist in the digitization, the snap functionality can be switched to ‘True’. Also the

‘Video Lock’ option can be set to ‘True’. When the snap is turned to on, a set of blue spheres will

appear to the left and to the right of the cursor during the digitizing. The cross-track distance

between the spheres is defined by the user in the ‘Snap window width’ option in the properties



window and the diameter of the spheres is identical to the diameter of the pipe. The digitization

will appear at the highest point (Top Of Pipe) as long as the cursor is within the ‘Snap window

width’. The snap functionality is particularly useful in connection with well-defined, relatively

large exposed pipes (or cables), whereas it is advised to turn the function off if the pipe is difficult

to detect, based on the bathymetric data/the DTM.

The video-lock functionality is used to force the video forward and/or backward to the present

position of the cursor and thereby of the digitized line, in order to supply additional information for

the determination of the whereabouts of the pipe. When activated, the video lock functionality also

works when the digitized line is being modified.

Figure 26 Using snap (see blue spheres) and video-lock

The ‘New Digitized Coverline’ is the recommended line type to use if the pipe is buried but the

pipetracker is exposed or missing. The functionality is invoked from the ‘Pipe Inspection’ toolbar

or by right-clicking in the ‘Toppings – Digitized Lines’ entry of the ‘Project Tree’ window and

choosing the menu item 'New digitized cover line' as shown below in Figure 27.



Figure 27 'New digitized Coverline' menu option (left) and ‘Properties’ window, right

In the ‘Properties’ window to the right, it is possible to define the ‘Distance below cover line’

option. When using cover lines to generate a pipe, the Quality is set to NA as seen below in Figure

28.

Figure 28 Covered Pipeline with annotations

Digitization of a pipeline can be particularly useful in connection with exposed pipes. In rock

dump and burial areas, it can sometimes be expedient to stop digitizing when the pipe goes into the

area and proceed with a new digitized line where the pipe comes out the other side. If the quality

of the pipetracker-data is poor, a cover-line should be digitized, otherwise the pipetracker

information can be used directly.

Also be aware that, in order to use the pipetracker in freespan area, the digitized line must be ended

prior to the freespan and the digitization process must be resumed again after the freespan.

2.2.1 Modifying the digitized pipe

A series of tools can be used to assist in the editing of the digitized pipe line as it appears from

Figure 29, where the digitizing help text visualised in the Log window is shown.



Figure 29 Digitizing Help in the Log window

Clicking on a digitized point will make the point appear as a vertical line with two spheres (or

balls), one at the top and one at the bottom, as can be seen below in Figure 30.

Figure 30 Digitized point with spheres

Moving an already digitized point is accomplished by clicking on one of the points and

subsequently moving it in the horizontal plane, by moving the lower ball and in the vertical plane,

by moving the top ball up and down.

To remove a misplaced point, click on the point in question. It will be marked yellow and can now

be deleted by pressing the ‘Delete’ key on the keyboard.

To place a new point in between two points, double-click on the ball either before or after the new

point. It is now possible to place an unlimited number of points between this point and one of its

two neighbouring points (see Figure 31 below).



Figure 31 Adding Points to a Digitized Line

A digitized pipeline can also be extended at both ends. This is accomplished by double-clicking on

the ball from where the extension should be made. The action to take is now identical to what is

done in connection with a normal digitization.

Marking a digitized point and clicking the ‘Shift’ and ‘Delete’ buttons simultaneously on the

keyboard will finally split the digitized line into two lines.

2.3 Generating the Pipe object

Once it has been established, that the digitization of the pipe object supports the edited and revised

pipetracker information adequately, the pipe object must be generated.

Generation of the pipe is done either from the ‘Pipe Inspection’ toolbar or by right-clicking in the

‘Pipe’ entry under ‘Toppings’ in the ‘Project Tree’ window as shown below in Figure 32, left.

Figure 32 'New Pipe' functionality, left and ‘Range Selection’, right

When this is done, the ‘Range Selection’ window in Figure 32, right will appear. The range can

either be entered manually or it can be determine through the use of the mouse. The latter is

activated by pressing the ‘Use mouse…’ button. As a consequence the cursor will appear as a

bull’s eye. The user can now choose the starting point and the ending point of the pipe. When this



is accomplished, the pipe will appear in the DTM window, in the ‘Project Tree’ window as well as

in the ‘KP-axis’ window. In the DTM window, the pipe will appear as shown below in Figure 33.

Figure 33 Pipe generated, with points spaced 1 m

2.4 Modifying the Pipe

NaviModel3 has a series of tools for modification and editing of the pipe object, such as:

Changing the properties of the Pipe

Visual control of the Pipe

Pipe Flexion flagging

Recalculation of the Pipe

Use of Pipe Ranges

Setting of KP Ranges



Figure 34 Pipe Properties window

When the pipe has been generated, the properties must first be checked and modified. Highlight the

pipe object under ‘Toppings’ in the ‘Project Tree’ and focus on the properties window as shown

above in Figure 34. Many of the initial properties are inherited from the ‘Project Settings’ whereas

other are default settings.

Cover Calculation:

o Fuzz factor: here the pipe coverage in cm before the pipe is tagged as covered can

be specified. Default value is 5 cm

Cross profile export Options: These options are used when the pipe is used to export cross-

profile data

o Interval: specifies the horizontal distance between points in the cross profile

o Width: specifies the width of the cross profile

o Thickness: width along the runline for export of raw data in a cross profile

o Points: number of points in the cross profile

General:

o Visible: visibility of the pipe object can be toggled here

o Diameter: this specifies the diameter of the pipe

o Min KP, Max KP: potential change will not take effect until the pipe is recalculated

Pipe Tracker alignment:

o Filtered Line: specifies whether or not the pipe should follow the pipetracker

Runline Alignment:

o Below Seabed: if pipe is aligned to the runline, distance below seabed is given here



Next, the ‘Fly Mode’ functionality can once again be used to perform a visual inspection of the

pipe, now that it is generated. When flying along the pipe, a variety of tools are available to check

whether the pipe is placed correctly or not.

Undesirable pipe bends can be located by altering the general pipe colour mode, to ‘Pipe_Flexion’

(see Figure 35, left). This quality flagging uses the ‘Acceptable flexion of the pipe’ value stated in

the ‘Pipe Settings’ tab of the ‘Project Settings’ (see Figure 35, left), and can be used to identify

bending violations on the pipe. The default value is 3 degrees.

Figure 35 Pipe Flexion Settings (left) and Pipe Color Mode set to ‘Pipe Flexion’ (right)

Alternatively these bending violations can be visualised on the KP-axis window as shown below in

Figure 36. The violations are depicted on the DTM window at the bottom as red quality indicators

on the points of the pipe, whereas they are shown as red lines in the ‘Bending violation’ line of the

‘KP-axis’ window at the top.

Figure 36 Pipe Flexion visualisation



Similarly the general pipe colour mode can be altered to ‘Burial_Status’ as shown below in Figure

37. This can be used to check the ‘in’ and ‘out’ of burial of the pipe. The figure also shows the

‘Exposed’ and ‘Covered’ status on the KP-axis window at the top. Note that the burial status can

only be visualised when the sideflags have been generated (see chapter 3 for details on this

subject).

Figure 37 Pipe Burial Visualization

Often the transition between a pipetracker based pipe object and one that is based on digitized lines

will result in a bending violation. A seamless transition must be ensured at this stage. This can be

accomplished in different ways: by modifying the digitized line or by inserting pipe fixes on the

pipetracker data.

When changes have been applied to the sources of a pipe, primarily the pipetracker data, the pipe

must be recalculated. This is accomplished by right-clicking on the Pipe Object in the ‘Project

Tree’ window and selecting the menu-item ‘Recalculate’ as shown below in Figure 38, left. A

window will appear, prompting the user to specify what to recalculate: Position and Flags, User

moved flags, Quality Status and Burial Status as visualised below in Figure 38, right.



Figure 38 Recalculate Pipe (left) and item for recalculation (right)

Figure 39 Select Pipe Range



Selected parts of the pipe object can be modified, by selecting a range of the pipe. This is

accomplished by right-clicking on the pipe object in question and selecting the menu-item ‘Select

Range’ as shown above in Figure 39. When doing so, the cursor will change its appearance to a

bull’s eye to indicate that a manual selection of the range is now facilitated. When the selection has

been accomplished, the pipe changes its appearance as shown below in Figure 40.

Figure 40 Selected range visualised

At the same time, the menu list associated with the pipe object has changes its appearance with a

series of additional items added as shown below in Figure 41.

Figure 41 Pipe Range menu items



It is in other words possible to modify the pipe within the selected range, for example ‘Apply

status’ and ‘Recalculate’. Note that once the status has been changed, the pipe range resets itself

and recalculate, as well as other menu items, will then be associated with the entire pipe. To avoid

this, the user will have to re-select the pipe range prior to recalculating.

The ‘Set KP range’ menu item, that also appears when right-clicking on a pipe object, will

facilitate a manual definition of the range of the pipe. When doing so, the cursor will change its

appearance to a bull’s eye to indicate that a manual selection of the KP range is now facilitated.

When the selection has been accomplished, the pipe will be defined from the defined KP starting

and ending points as shown below in Figure 42.

Figure 42 Selection of KP range, prior (top) and after (bottom)

Note the KP-values given at the bottom of Figure 42 that indicates the starting and ending points

of the pipe.

3. THE SIDEFLAGS

When the pipe object is acceptable, the sideflags must be generated. This is done by right-clicking

on the pipe object in the ‘Project Tree’ window and selecting the menu-item ‘Add sideflags’.

Based on the settings defined in the ‘Flag Settings’ tab of the ‘Project Settings’ dialogue, as shown

in Figure 43 below, the 5 flags will now be placed automatically by NM3.



Figure 43 Flag settings



Figure 44 Pipe project after the side flags have been generated

3.1 Using the Flags

Once the flags have been generated, they will be visualised on the DTM window as shown in

Figure 44 above. The contents of the KP-axis window will also have changed, based on the flags.

The burial/exposed status will be shown in two different lines – one for burial and one for exposed.

This status is based on the cover on top of the pipe (one of the flags), compared to the fuzz factor.

Also the ‘Possible Burial Error’ is flagged in the KP-axis window. As shown below in Figure 45,

‘Possible Burial Error’ will be flagged when the pipe is buried less than what is specified for the

fuzz factor. In the example the factor has been set to 5 cm and the burial was only 1 cm. The pipe

will therefore be flagged as exposed -0.01 m.



Figure 45 Possible Burial Error parameters (see red arrow)

Freespans will also be visualised in the KP-axis as well as on the DTM window. The latter appears

when hovering the cursor on one of the points of the pipe.

In Figure 46 below, a freespan is visualised. On the DTM window it appears that there is a

freespan of 0.31 m. This is the difference between the TOP and the Terrain z-value, corrected for

pipe diameter, which is 1.2 m in the present context, with terrain z being the average z-value of the

two adjacent flags (seabed left and seabed right of pipe).



Figure 46 Freespan visualised in the DTM window

3.2 Modifying the Flags

Once the flags have been generated, they must be checked. The most efficient way of doing this, is

to make a fly-through in order to check for misplaced flags, obstructions and holes in the DTM,

resulting in missing flags.

Modification of the flags can be performed in two different ways:

manual digitization of the flags

moving the flags

Manual digitization of side-flags is facilitated in NaviModel3. Apart from the fact that digitizing

the pipe is really digitizing the TOP flag, all side flags can be digitized, which in effect means that

the automatically placed flags will be overruled in the area in question.

To accomplish this, right-click on the ‘Digitized Lines’ entry under ‘Toppings’ in the ‘Project

Tree’ window, and choose the menu-item ‘New digitized line’. Now change the ‘Type’ of the line

to be digitized in the ‘Properties’ window, as shown below in Figure 47. Note that all 5 flags as

well as the cover flag can be chosen.



Figure 47 Defining the Digitizing Line Type

Figure 48 below shows digitization of the left seabed outer flag. The digitisation is conducted in

order to move the automatically placed flags inside the DTM in an area where they were close to

the edge.

Figure 48 Digitizing the left seabed outer side flag line

The side flags can also be modified and moved manually. This is done in the DTM window by use

of the mouse. Left-click on the flag without releasing the left mouse button. The flag will now have

a round sphere at the bottom as can be seen in Figure 49 below. The flag can now be moved in the

across-track direction and released whenever an acceptable placement has been accomplished.

Note in the figure, that, whereas the KP-value is constant, the z-value varies as the flag is moved.



Figure 49 Manual movement of sideflags: before movement (left) and during movement (right)

3.3 Export of Freespan and Burial status

Figure 50 Export Freespans/Burials

NM3 facilitates exporting of freespan and burial status for each pipe object in a project. Right-click

on a pipe object and choose menu-item ‘Export freespans/burials’. The freespan burial status along

the pipe will be sent to Notepad as shown above in Figure 50.

The items shown are: KP range in absolute terms (minimum, maximum), Status (Covered,

Exposed or Freespan) and maximum value (in meters) within the range.

3.4 Pipe Listings

When choosing the menu item ‘Pipe Listings’ from the pipe object in the ‘Project Tree’ window,

the window visualised in Figure 51 below, will appear. The window supplies another way of

giving a fast overview of the pipe status along the pipe than the KP-axis window. As is the case



with the KP-axis window, however, the Pipe Listing window will scroll up and down in

accordance with the DTM view. It is also possible to double-click on a line in the Pipe Listing

window and thereby moving the DTM view (and the KP-axis window) in accordance.

Figure 51 Pipe Listings Window (bottom) and KP-axis window (top)

The items listed in the Pipe Listing window are associated with the points of the pipe (one line per

point). The items are (from left to right):

#: the point number

KP: the KP-value

Burial: the burial status (with colourcoded background, green for Covered, yellow for

Exposed and purple for Freespan)

Quality: the quality status (with colourcoded background, green for OK and red for NA)

TOP (m): the depth value of the TOP

MTR (m): mean trench (average of Left and Right Seabed Inner)

Source: displays the source of the pipe (pipetracker, digitized pipe, runline) (with

colourcoded background, green for digitized pipe, purple for pipetracker and red for runline)



Bend: the bend of the pipe in degrees (with colourcoded background, green for values less

than limit and red when limit is exceeded)

E (m): Easting coordinate

N (M): Northing coordinate

MSBL (m): Mean Seabed Left depth value (Left Seabed Outer)

MSBR (m): Mean Seabed Right depth value(Right Seabed Outer)

BOTL (m): Bottom Of Trench Left depth value (Left Seabed Inner)

BOTR (m): Bottom Of Trench Right depth value (Right Seabed Inner)

Burial defined: the source of the burial definition (Flags or User)

4. EXPORTING FROM A PIPE OBJECT FOR FURTHER PROCESSING

The various results that are to be used for further processing in NaviPlot and in connection with

other, project specific documentation, is now to be exported from NaviModel3. This is done by

right-clicking on the pipe object under ‘Toppings’ in the ‘Project Tree’ window and choosing the

menu-item ‘Export…’. The export dialogue, shown below in Figure 52, left, will appear.

Figure 52 Export dialogue for a pipe object (left) and formats available - based on a pipe object (right)

The drop-down-list for a pipe object based export, that will appear when clicking on the arrow-

down in the ‘Save as type’ field, is depicted above in Figure 52, right. From here the format to be

exported can be selected.

A typical pipe-based plot in NaviPlot would typically involve a longitudinal profile and a cross

profile. For these, the ‘Long Profile Ascii (*.lpa)’ for the longitudinal profile and ‘Cross Profile

Ascii (*.xpa)’ or ‘Cross profile (*.gcp)’ for the cross profile would apply. However also the

‘VisualWorks Cross-profile (*.csv)’ format, associated with events, is supported in NaviPlot.

Documents

Step-by-step Tutorial - EIVA Download Sitedownload.eiva.com/online-training/Step_By_Step_Pipeinspection.pdf · At this point in the process the KP-window will include all the online