Professional Documents
Culture Documents
Catenary requirements
Jesper Knudsen, Brian J.O. Justesen
Page 2
Contents
1
Basic requirements.............................................................................................................4
1.1
iSURVEY requirements.............................................................................................4
1.1.1
Interface .............................................................................................................4
1.1.2
Distribution to tug ..............................................................................................5
1.1.3
Correction of chain length .................................................................................6
1.1.4
Manual input ......................................................................................................6
1.1.5
Rig Display ........................................................................................................6
1.1.6
Calculations........................................................................................................6
1.1.7
Horizontal view..................................................................................................7
1.1.8
Vertical view......................................................................................................7
1.1.9
Cable lay view....................................................................................................7
1.1.10
Numeric data......................................................................................................7
1.1.11
Audio and visual alarms.....................................................................................8
1.2
Deep Ocean requirements ........................................................................................13
1.3
C&C requirements ...................................................................................................13
2
Accommodated requirements ..........................................................................................15
2.1
General setup ...........................................................................................................15
2.2
Catenary setup..........................................................................................................15
2.2.1
Physical line assembly .....................................................................................16
2.2.2
Physical cable properties..................................................................................16
2.2.3
Midline buoys properties .................................................................................16
2.3
Catenary calculations ...............................................................................................16
3
Design ..............................................................................................................................18
3.1
General setup ...........................................................................................................18
3.2
NaviPac ....................................................................................................................18
3.2.1
New Input Instruments.....................................................................................19
3.2.2
Navigation Data to Catenary............................................................................20
3.3
RigMon ....................................................................................................................20
3.4
Scene server .............................................................................................................21
3.5
Catenary Module......................................................................................................21
3.5.1
New Project......................................................................................................21
3.5.2
Calculate ..........................................................................................................22
3.6
3D display ................................................................................................................23
4
Workload..........................................................................................................................24
Page 2 of 24
Created on 30-05-2007
Page 3
Revision table
Date
30.05.2007
30.05.2007
31.05.2007
01.06.2007
Who
JUS
OKR
JEK
JUS
05.06.2007
07.06.2007
OKR
OKR
07.06.2007
08.06.2007
15.06.2007
15.06.2007
19.06.2007
OKR
OKR
JEK
JUS
OKR
Comment
First version (spawn of 3D Online Display.doc)
Added chapter Anchor Monitoring System by AS STEINCO
Added chapter Catenary setup
Added chapters Accommodated requirements and Design;
revised chapter Catenary setup
Version 1 reviewed internally
No comments received from clients (C&C, iSurvey, Deep Ocean)
so version 1 is defined OK
Version 1.1 Section 3 expanded with design elements
Added definition of NaviPac and RigMon
Filled chapter 3D Display
Filled chapter Catenary module
Reviewed internally OK
Page 3 of 24
Created on 30-05-2007
Page 4
1 Basic requirements
After having implemented and released the first version of EIVAs new 3D online/real time
monitoring application, were progressing to phase 2 implementing the basic catenary. This
document covers the requirements of setting up a catenary project, catenary computations, 2D
profiling and 3D monitoring. However, only TMS and anchor handling (Rig and Barge
move) is covered in this first version of catenary handling later on well include pipe- and
flexible cable lay as well.
It is important to note that the following parts will be based on the 3D platform implemented
in phase 1. Also notice that the listed client requirements are used as inspiration for the
suggested design, not a commitment to what will be implemented in the Catenary module.
1.1
iSURVEY requirements
1.1.1 Interface
A serial interface should be created for anchor monitoring system. The format should
be:
<anchor id>, <length[metre]>, <tension[metric ton], <speed[metre/min]>CRLF
- also a user defined format should be considered.
Where:
<anchor id> - anchor number
<length[metre]> - chain length
<tension[metric ton]> - total tension in winch
<speed[metre/min]> - winch speed while running anchor
<workwire[metre]> - work wire out on Tug as a manual input on rig
Also an angular meter input for cable lay operations could be considered.
Page 4 of 24
Created on 30-05-2007
Page 5
(byte 2) Length 1
(LSB) Length 1
then anchor 2 to 7
MSB Tension 8
(byte 2) Tension 8
(LSB) Tension 8
(MSB) Length 8
(byte 4) Length 8
(byte 3) Length 8
(byte 2) Length 8
(LSB) Length 8
ETB (17 hex)
Checksum
STX:
This is the character used to identify the start of the telegram.
Tension:
The anchor tension information is scaled in Tonne and sent with the most significant byte first.
Length:
The anchor length information is scaled in decimeters and sent with the most significant byte first
ETB:
This is the character used to identify the end of the telegram.
Checksum:
This is a left shifted XOR sum. The checksum is calculated for all the bytes in the telegram excluding
the checksum. The calculation is performed in accordance with the procedure below:
1. Checksum = byte 1
2. Checksum = Checksum XOR Byte 2
3. Shift left Checksum
4. Checksum = Checksum XOR Byte 3
5. Shift left Checksum
6. .. and so on ..
Page 5 of 24
Created on 30-05-2007
Page 6
The data should be received and visible in anchor handling display on Tug/Rig.
In addition the touchdown position calculated in part 2 should be distributed and
displayed on Tug
1.1.6 Calculations
Internationally accepted catenary algorithms should be used to compute the straight
line profiles of each mooring line.
The reference will be the rig fairlead or a dynamic offset point. The end point should
be a:
Anchor on seabed
At least 2 lift up boys with specified lift capacity and wire length should be
included
Page 6 of 24
Created on 30-05-2007
Page 7
Allowing lines with priority calculating a solution on a higher update rate if this
is an issue
Numeric data
The numeric data should be calculated for each anchor. It should be possible to
show/hide values/columns and change fonts. Conditional formatting of
colour/background at alarm limit should be available.
-
Chain add-on at drop (Difference between the two above values if Rig is out of
position)
Distance to touchdown
Grounded length
Winch offsets
Page 7 of 24
Created on 30-05-2007
Page 8
Total tension calculated at ref (Based on depth, weight In water and catenary
length)
Page 8 of 24
Created on 30-05-2007
Page 9
Page 9 of 24
Created on 30-05-2007
Page 10
Page 10 of 24
Created on 30-05-2007
Page 11
Page 11 of 24
Created on 30-05-2007
Page 12
Page 12 of 24
Created on 30-05-2007
Page 13
1.2
Except the requirement of displaying seabed data collected real time all requirements are
accommodated in phase 1.
1.3
C&C requirements
The following requirements from C&C must be covered by the solution. Points directly
supported in version 1 are highlighted.
1. Combination of the real time visualization & catenary module for the deployment and
recovery of anchors for a semi-submersible in water depths to 4,000 meters.
a. I would like to see in real time a plan & profile view of the catenary in 3-D
from the rig to the vessel or have the ability to zoom in and observe sea
floor assets i.e. wells, manifolds, plets etc in relationship with the chain, wire
rope and or combination of both. That is my client's main requirement for this
software i.e. this is a risk prevention tool for his end user the Oil Company.
b. I would envision the catenary analogue data to be available and configurable
on as need basis as an output on NaviPac Monitor
c. Sea floor asset drawings i.e. AutoCad from the client would be easily
imported into NaviPac and displayed and scalable as required in 3-D
d. If bathy data were available, it would be imported and used within the
visualization section of the software. In addition both swath data and single
point data and data formats would be defined by EIVA a/s.
2. Surface and sub-surface visualization option to support intervention work
utilizing an ROV
a. Support surface DGPS
b. Support sub surface USBL, LBL, INS systems
c. Represent sea floor assets i.e. wells, manifolds etc and be imported
drawings in the Auto Cad format and be scalable
d. Import bathy data in the visualization portion of the program in both
single point and swath formats
e. Represent object in the water column in 3-D
3. Perform the same functions as number #1 with a Pipe Lay Barge, not concerned
with the pipe at the moment, but just with barge anchor placement around the
sea floor assets in mind
4. Combination of the real time visualization & deployment of umbilical/cable &
flexible pipe, similar to the requirements but replacing the anchor legs with flexible
pipe or umbilical/cable.
5. Utilizing the visualization portion to observe pipe in the water column and above risk
associated with sea floor from an S-lay or J-lay barge DP or Anchor, assuming ROV
is acoustically positioned i.e. USBl or transponder is tied to the pipe i.e. USBL.
Page 13 of 24
Created on 30-05-2007
Page 14
6. Utilizing the visualization portion to observe pipe in the water column from an S-lay
or J-lay DP or Anchor Barge, and finally on bottom to observe the pipe in relationship
to the sea floor assets
7. The final request would be to utilize the visualization portion and analog to observe
deployment of jackets, sub-sea assemblies, SUBMAR MATS utilizing survey sensors
such as USBL, LBL input string into Navipac, Slew angle & Radius of vessels crane
with vessel 's gyro reference. The idea being in deep water when a semi-rig deploys
its sub-sea assembly, strong currents often effect the position of the assembly and
move it to critical positions throughout the water column causing concern. In this case
with the reference or the position of the semi-rig displayed and the riser string & subsea assembly displayed would provide a picture that a thousand words could not
describe. In addition I believe this would be a wonderful for setting jackets with a
RHO / THETA device such as a Fanbeam or THEODOLITE/EDM.
Page 14 of 24
Created on 30-05-2007
Page 15
2 Accommodated requirements
The accommodated client requirements are listed in the following sections - but first an
overall description of a general setup.
2.1
General setup
The following outlines an example of a setup. The local network on the vessel connects
NaviPac, a scene server and three 3D display clients.
2.2
Catenary setup
A new catenary module will handle catenary projects. A catenary project can be defined,
saved and reloaded. The project is basically a setup for one or more catenary lines (wires)
up to 16 (anchor) wires will be supported. Each catenary line is defined by a number of
different cable types (sections) and fix points, e.g. start, end and MLB points.
Page 15 of 24
Created on 30-05-2007
Page 16
The setup of the instrument(s) interfaced by the catenary module will be handled by NaviPac
(for the time being), but the binding to NaviPac will be as loosely as possible, making a total
independence of NaviPac obtainable, at least theoretically.
Length
Weight of cable per meter in water
Weight of cable per meter in air
Diameter
2.3
Catenary calculations
The calculations may be run either manually, determined by the operator, or automatically
triggered by exceeding some key settings or tolerances also defined by the operator, e.g. the
anchor or barge has been moved or the tension has changed.
To calculate the catenary curve the system needs:
File: I:\EIVA-PROJECTS\FILES FOR EIVA-TRAINING\NAVIMODEL3 MANUALS\3D ONLINE DISPLAY - CATENARY.DOC
Page 16 of 24
Created on 30-05-2007
Page 17
Page 17 of 24
Created on 30-05-2007
Page 18
3 Design
This section gives the system design as EIVA sees it based on the specification listed in the
previous section.
3.1
General setup
The goal is to keep the catenary stuff isolated in one component it works together with
NaviPac, TMS and 3D view but its not linked hard to this environment.
NaviPac
Kernel
Helmsmans
Display
2D Objects,
Anchor patterns
Anchor patterns,
MLBs
RigMon
3D Monitoring (.NET)
An
ch
or
pa
tte
W
rns
ire
lin
es
,M
LB
s
Winches, MLBs
genSetup.db
NaviModel
Repository
Instrument Setup
Winches, MLBs
Catenary
Anchor patterns
SceneServer
3D Objects
3D Display
The data flow and the anticipated implications of existing modules will be described in the
following chapters.
3.2
NaviPac
There will be a few modifications required in NaviPac. This is mainly because we will aim
for the most strict data flow when it comes to:
Anchor monitor inputs
Position data to Catenary
File: I:\EIVA-PROJECTS\FILES FOR EIVA-TRAINING\NAVIMODEL3 MANUALS\3D ONLINE DISPLAY - CATENARY.DOC
Page 18 of 24
Created on 30-05-2007
Page 19
Page 19 of 24
Created on 30-05-2007
Page 20
The definition of the interface will hereafter be found in the NaviPac setup database
(gensetup.db). NaviPac online will ignore the definition (DataIO skips opening the port, etc.)
and leave all interfacing to the Catenary module itself.
But this involves a lot of setup. Instead we suggest that we add a new output:
EIVA Catenary
The output will be defined as UDP/IP on the port to the scene server (see details in phase 1
documentation) so we re-use the output port. There is no user specification besides that. If
the output is defined NaviPac will simply output position of all fairleads in one string per
object. We suggest that the telegram is identical with the existing position output except that
it identifies fairlead rather than ordinary object:
$EIVA3D,C,3,POS,O=<obj> E=<easting> N=<northing> Z=<height><cr><lf>
The obj represents the NaviPac object numbering for fairleads i.e. fairlead 1 is 850, etc.
3.3
RigMon
RigMon must be expanded so it outputs the anchor patterns to the Catenary module (via
Scene Server) as illustrated in the general setup diagram.
RigMon will inherit the output defined in 3.2.2 and if it exists then it will send the anchor
pattern out on the same port as the output from NaviPac. This will be OK as we use UDP/IP
ports!
The anchor patterns must follow the same principles as existing outputs from RigMon (to
TUG Boats and CMS)
Each time an anchor changes status
Each time an anchor changes location
Each time MLB changes location
On user request (from RigMon menu)
With certain frequency (same as TMS output)
File: I:\EIVA-PROJECTS\FILES FOR EIVA-TRAINING\NAVIMODEL3 MANUALS\3D ONLINE DISPLAY - CATENARY.DOC
Page 20 of 24
Created on 30-05-2007
Page 21
3.4
Scene server
3.5
Catenary Module
The Catenary module will consist of 3 main views: a tree view listing hierarchical the whole
project; a property view where static, dynamic and calculated data will be displayed; and
lastly a tabbed graph view section where all 2D profiles are displayed in its own tab view.
Page 21 of 24
Created on 30-05-2007
Page 22
The property view will follow and show the properties for the catenary line part being
selected. In this prototype we only see some of the static data. A dynamic part will also be
added, e.g. length of section, known tension, etc.
As mentioned earlier all instrument setup will be handled in NaviPac. However, it might turn
out to be a good idea to list entered instrument setup data in the catenary module as well. An
adapting layer between the catenary module and NaviPac will be used to make the NaviPac
dependency as small as possible.
When a catenary project is defined the project may be persisted (saved). The format will be in
XML (hence the extension .xml).
3.5.2 Calculate
Calculation will be performed in the catenary module, and all calculations can be monitored
iteratively in the graph window. It will be possible to calculate each session and maybe even
each line. This is done manually in the start up phase but options to set up for automatically
calculation will also be added.
Each resulting 2D profile (see picture below) will be shown in its own tab view to the right
(not shown in the above listed prototype). There will be as many tab views as defined
catenary lines.
Page 22 of 24
Created on 30-05-2007
Page 23
Above we see an example of a 2D catenary profile. The full catenary line is shown with all its
sections. The current (last calculated) tension is also shown, and we expect to add some more
key data to the graph view as well.
After a calculation the results will be distributed to the 3D Display and the 3D Display will
then update and show the 3D profile accordingly. However, an option for doing calculations
without distribution (offline) is expected.
3.6
3D display
The 3D display should visualize everything the catenary module knows in terms of catenary
positions, curves and tensions. We intend to build a general protocol for showing pipes,
cables or chains that can be used by the catenary module to tell the 3D display what and
where to draw.
The catenary module will use the general text message protocol to control the display, and
update rates are determined by the catenary module. All catenaries stay at give position until
changed by the catenary module, although you will still be able to move around freely in the
most recent snapshot of the catenaries.
The catenary module will supply curves to the 3D display in parallel to other information
being sent to the display. In the (with faked 3D catenaries) screenshot below catenaries and
File: I:\EIVA-PROJECTS\FILES FOR EIVA-TRAINING\NAVIMODEL3 MANUALS\3D ONLINE DISPLAY - CATENARY.DOC
Page 23 of 24
Created on 30-05-2007
Page 24
other dynamic NaviPac objects are positioned along side each other in the scene. The scene
also holds an indexed terrain model.
4 Workload
Maintained in 3DPhase2.xls
Page 24 of 24
Created on 30-05-2007