G-90-041-VAG-10_ENGINEERING _vers.01.00

VERSION SAERT3 ENGINEERING

PAG 1 OF 47 1

Document Ref: G-90-041-VAG-10 Version: 01.00 Date: 26-02-10 Technical Management

SAERT3

ENGINEERING

TECHNICAL MANUAL


PAG 2 OF 47 1


Geolog S.p.a.

Via Carlo Porta 21 20098 S. Giuliano Milanese (Mi) Italy

Tel: +39 02 982 521 Fax: +39 02 982 52324 e-mail [email protected] web www.geolog.it

Copyright 2000 by Geolog S.p.A. All rights reserved.

No part of the content of this book may be reproduced or transmitted in any form or by any means without the written permission of Geolog S.p.A.

Revision Date Description Issued by Controlled by Approved by 01.00 26/02/2010 FIRST ISSUE P.Baldini/JP.Vagnoux G.Di Turi G. Ferroni


PAG 3 OF 47 1


TABLE OF CONTENTS

1 HYDRAULICS .......................................................................................................................................... 4

1.1 Hydraulics - On Line & Real Time Analysis - While Drilling ............................................................................... 6 1.1.1 Algorithms used (SI Units): ........................................................................................................................... 12 1.1.2 Report ........................................................................................................................................................... 13

1.2 Hydraulics - On Line & Real Time Analysis - While Tripping ............................................................................15 1.2.1 Hydraulics - On Line & Real Time Analysis - While Tripping (POOH) ............................................................ 16 1.2.2 Hydraulics - On Line & Real Time Analysis - While Tripping (RIH) ................................................................ 18

1.3 Hydraulics Simulations - Drilling ..................................................................................................................20

1.4 Hydraulics Simulations POOH - SWABBING...............................................................................................23 1.4.1 Generate the Report ..................................................................................................................................... 24

1.5 Hydraulics Simulations RIH - SURGING .....................................................................................................27 1.5.1 Generate the Report: .................................................................................................................................... 28

2 LEAK OFF TEST .................................................................................................................................. 31

3 TVD ........................................................................................................................................................ 33

4 D EXPONENT ON LINE ..................................................................................................................... 35

5 FLOW-GUARDIAN ............................................................................................................................. 36

5.1 Pipe Connection Modelling ............................................................................................................................36 5.1.1 Titles and version number ............................................................................................................................ 37 5.1.2 Commands and settings ................................................................................................................................ 38 5.1.3 Events-related X/Y plots for active mud volume .......................................................................................... 40 5.1.4 Alarms ........................................................................................................................................................... 43

5.1.5 Events storage program rtdb_event_storage .............................................................................................. 45


PAG 4 OF 47 1


1 HYDRAULICS

By Hydraulics is intended the analysis of all pressure losses created by the friction between the drilling fluid and the hole, casing, external surface of drill-string, internal surface of drill-string, bit and surface system when the drilling fluid is moving (drilling conditions) or when the drill-string is moving (tripping conditions).

This analysis has a fundamental importance for the safety of the well and for the efficiency of the drilling conditions :

Safety of the well: Calculations of ECD (Equivalent Circulating Density) to be sure that it is not

higher that the fracture gradient at the shoe Calculation of ECD to evaluate possible connection gas (under-balance

conditions) Calculate the maximum velocity of the drill-string while tripping to avoid

the swab or surge effect

Drilling Efficiency : Verify that the computed value is close enough to the real value, to control

abnormal situations (pumps efficiency, wash-out, nozzles efficiency, wrong rheology, wrong pipes diameters.)

Choose proper liners of the pumps Apply a proper mud flow rate to ensure the good cleaning of the annulus Determine the flow regime to avoid turbulence in loose formations Optimize the Bit Hydraulics

While Drilling the following systems will be analyzed : Surface System (from the pump to the top-drive or Kelly) Inside the pipes (Circular flow) Through the bit nozzles Inside the annulus (Annular flow)

The sum of those four partial pressure losses should be close to the real value of SPP

While tripping the following systems will be analyzed : Inside the annulus considering the nozzle closed Inside the annulus considering the nozzles open

For no reason the swab effect can reduced the mud weight less than the pore pressure kick & eruption For no reason the surge effect can increase the mud weight more than the fracture gradient at the shoe losses and consequential kick & eruption


PAG 5 OF 47 1


The factors determining the various pressure losses are the following: Length of the circuit (bit position where is circulating the mud): ^1 Various diameters: nozzles, internal and external of pipes, open hole

and casing internal: ^5 Mud flow rate In: ^2 Mud density: ^1 Mud rheological properties: ^4

The four first factors are direct measurements : Be always very careful on the pipes inside diameters, taking also into account the tool-joints diameters.

The mud rheology is computed from the viscosimeter readings given by the Mud Engineer and the consequential parameters to use in the algorithms are :

Plastic Viscosity (PV): viscosity Yield Point (YP): stress (pressure)

n : flow index: no dimension K : consistency index: viscosity at power n

Tau 0: stress (pressure)

Those parameters are computed according 3 mathematical models : Bingham Plastic Power Law Herschel & Bulkley

As default model use preferentially Power Law.

Recommended values for Flow Rate and HIS: Hole Diam (in) Flow Rate (lpm) HSI

26 3500 5000 2 17 1/2 3500 3800 4 to 5 12 1/4 2200 2800 6 to 7 8 1/2 1600 2000 9 6 500 - 1000


PAG 6 OF 47 1


1.1 Hydraulics - On Line & Real Time Analysis - While Drilling

Control that the well profile is correct: the last section MUST BE H (open hole):


PAG 7 OF 47 1


Control that the drill-string is correct:

Use the dictionary to identify the pipes, pay a great attention to the diameters and DONOT forget to enable the tool-joints (1m each 10m for the HWDP and 0.5m for the DP).

DO NOT INSERT ADDITIONAL ELEMENTS LIKE BIT, STAB, ETC..... IDENTIFY THE BHA AS DC. ONLY DC, HWDP AND DP.


PAG 8 OF 47 1


Input the mud properties :

Viscosimeter readings: possibly 5 readings to use the most precise model: Herschel & Bulkley:

If the viscosimeter readings are not available, insert the PV, YP and Gels @ 10seconds:

Mud density to apply (should be the same than the mud density In) measured by the sensor. The rheological parameters will be calculated automatically.

Input the bit properties:

If the nozzles are known, input them and compute the TFA (Total Flow Area). Nozzle coefficient MUST be 1.


PAG 9 OF 47 1


Input the bit TFA (in case of Diamond bit having no nozzle):

Input constants :

Surface equipment type (normally 3 or 4). Eventually additional pressure losses due to MWD/LWD or /and down hole motor (DHM).

Input pore gradient and fracture gradient at bottom and at the last casing shoe:

Those values should be computed by you, or given by the WSG Company Man.

Pressure Gradients do not influence Hydraulics Calculations but is MANDATORY for SWAB/SURGE.


PAG 10 OF 47 1


Input last Deviation Survey:

TVD : be extremely careful about TVD because Hydrostatic Pressures and ECD are a direct function of the TVD

Hydrostatic Pressure (static conditions) = Mud Weight * TVD / 10 Hydrostatic Pressure (dynamic conditions) = (Mud Weight * 10 / TVD) + Annular Pressure losses ECD = Hydrostatic Pressure (dynamic) * 10 / TVD

In this panel ECD will blink in red if : ECD >= Fracture Gradient at casing or at bottom (losses) ECD


PAG 11 OF 47 1


Pressure Losses :

Is a synthesis of all partial pressure losses compared also with the real SPP.

Bit Hydraulics :


PAG 12 OF 47 1


1.1.1 Algorithms used (SI Units): Q : Flow rate (m3/s) Diam : Bit Diameter (m) TFA : Total Flow Area (m2) Mw : Mud Density (kg/m3) JVel : Jet velocity (m/s) JIm : Jet impact (N) JPr : Jet pressure (Pa) JHP : Jet Power (W) HSI : Jet Power /in2 (HP/in2)

JVel = Q / TFA JIm = 0.996 * Q * Mw * JVel JPr = 0.556 * Q^2 * Mw / TFA^2 JHP = Q * JPr HSI = 1.1 * JHP / Diam^2 / 10^6

Bit Optimization : Consists in adjusting the flow rate and the bit nozzles in order to minimize the pressure losses inside the pipes and maximize the bit hydraulics:

Power spent at bit should not be less than 50% of total (not possible at high depth) Jet velocity should be at least 60m/s. HSI should be according to the bit diameter:

26 2 17 1/2 4 to 5 12 1/4 6 to 7 8 1/2 9


PAG 13 OF 47 1


1.1.2 Report


PAG 14 OF 47 1



PAG 15 OF 47 1


1.2 Hydraulics - On Line & Real Time Analysis - While Tripping

ECD CALCULATIONS WHILE TRIPPING


PAG 16 OF 47 1


1.2.1 Hydraulics - On Line & Real Time Analysis - While Tripping (POOH)

POOH: Swab effect : The upward movement of the drill-string will create a negative pressure at bit location that will translated by a suction effect on the formation. The negative annular pressure losses will decrease virtually the mud density and a critical situation of under-balance can be created (Pore Gradient higher than the ECD). If this under-balance takes place in front of a porous and permeable formation containing a fluid, a kick and further an eruption can be created.

It is fundamental for safety to monitor closely the hook velocity while POOH and to control the value of the ECD. If ECD at this speed becomes lower than Pore Gradient give immediately the necessary alarm !!!


PAG 17 OF 47 1


SWABBING EFFECT: NEGATIVE PRESSURE DECREASING ECD


PAG 18 OF 47 1


1.2.2 Hydraulics - On Line & Real Time Analysis - While Tripping (RIH)

RIH : Surge effect: The down movement of the drill-string will create a positive pressure at bit location that will translated by an overpressure effect of the mud on the formation. The positive annular pressure losses will increase virtually the mud density and a critical situation of over-balance can be created (ECD higher than Fracture Gradient) and the hydrostatic pressure of the mud can break the formation causing mud losses and eventual consequential kick.

It is fundamental for safety to monitor closely the hook velocity while RIH and to control the value of the ECD. If ECD at this speed becomes higher than Fracture Gradient at casing shoe, give immediately the necessary alarm !!!


PAG 19 OF 47 1


SURGING EFFECT: NEGATIVE PRESSURE INCREASING ECD


PAG 20 OF 47 1


1.3 Hydraulics Simulations - Drilling

It is possible to simulate any drilling condition, print the report and be back on the on line real time analysis.

Update the well profile used for simulations and save it for simulations :

!!! Take extreme care when you save the new profile. DO NOT SAVE IT for the real time because in this case all volumes calculations and depth synchronization will

be destroyed !!!

Update the drill-string used for simulations and save it for simulations :

!!! Take extreme care when you save the new drill-string. DO NOT SAVE IT for the real time because in this case all volumes calculations and depth synchronization

will be destroyed !!!


PAG 21 OF 47 1


By pressing the Simulation button, the program allows the data entry of all parameters : Example : What will be the pressure losses at 4000m, using a mud density of 1.8kg/l, and using 3 nozzles of 12 in/32 ?


PAG 22 OF 47 1


Input hypothetical Flow Rate and Click on Re-compute and display:

Complete analysis is computed.

Change any parameter to simulate a new situation. Simulation Report is built like Real Time Report.


PAG 23 OF 47 1


1.4 Hydraulics Simulations POOH - SWABBING

Insert CORRECT Gradients, input all data and click Re-compute and display. Each 100m the program calculates the time per stand necessary to keep the ECD equal, not lower than the Pore Gradient at TD.


PAG 24 OF 47 1


1.4.1 Generate the Report


PAG 25 OF 47 1


Each 100m , the graph shows what is the MAXIMUM ALLOWED trip velocity to keep ECD not lower than 1.57kg/l (value of the Pore Gradient at TD).


PAG 26 OF 47 1


Verification can be done on the single point:

At 23s per stand, ECD will be equal to Pore Gradient @ TD (WARNING).


PAG 27 OF 47 1


1.5 Hydraulics Simulations RIH - SURGING

Insert correct Gradients:

Input all data and click Re-compute and display. Each 10m the program calculates the time per stand necessary to keep the ECD equal, not higher than the Fracture Gradient at Casing Shoe.


PAG 28 OF 47 1


1.5.1 Generate the Report:


PAG 29 OF 47 1


Each 10m , the graph shows what is the MAXIMUM ALLOWED trip velocity to keep ECD not higher than 2.1kg/l (value of the Fracture Gradient at Casing Shoe).


PAG 30 OF 47 1


Verification can be done on the single point:

At 10s per stand ECD will be higher than Fracture Gradient @ Shoe.


PAG 31 OF 47 1


2 LEAK OFF TEST

LEAK OFF TEST OR FORMATION INTEGRITY TEST are run straight after the casing set when cement is dry. It consists to pump mud with BOP closed until the pressure breaks the Formation (refer to 07_GEOPRESSURES for theoretical explanations.

Click OK to save data set as proponed. Click on Settings to input variables:

Normally DBR are the one displayed.


PAG 32 OF 47 1


When they start pumping, click on Start new session:

Display Time in abscises and Show volumes:


PAG 33 OF 47 1


3 TVD

According to the Deviations Surveys input, TVD calculates TVD by extrapolation or interpolation. TVD is stored each 5sec and 0.25m or 1 ft.


PAG 34 OF 47 1



PAG 35 OF 47 1


4 D EXPONENT ON LINE

It calculates D exponent Time or depth based, and the relative pressure Gradients:

Refer to ENGINEERING GEOPRESSURES for theoretical explanations.

Take care of the input of yellow fields. Increasing the Trend b coefficient will increase your Gradients.


PAG 36 OF 47 1


5 FLOW-GUARDIAN

FlowGuardian is a set of 5 programs providing assistance to flow control and interpretation. Pipe connection modelling : allows to interpretate the mud volumes in critical moments : when the

pumps stops and the mud volume increases in the tanks, and when the pumps restart and the total mud volume decreases.

Transient flow analysis : allows to visualize and to interpretate small flow rate variations. Tripping monitor : redesigned trip analysis program. Total mud loss monitor : calculate the water table level from then injection pressure. Pumps efficiency monitor : calculate the real pumps efficiency from the flow-in sensor.

5.1 Pipe Connection Modelling Single-page monitor containing real-time data and memorized events. The PCM is the front-end of a background program called rtdb_event_storage. It uses a dedicated database.

Layout :

1: Titles and version number 2: Commands and settings 3: Continuous real-time plot zone 4: Events-related X/Y plots for active mud volume 5: Alarms

2

1

5

4 3


PAG 37 OF 47 1


5.1.1 Titles and version number

B is the build number : 85 for the first release C is the executable size, 259308 for the first release

The monitor is active as soon as launched.

The following keyboard shortcuts are implemented : Control + H : activates the context HELP. The main objects of the screen are commented. Control + F1 : closes the screen (same as the stop button).

Context menus: on the plots you can display/hide the following elements: X-scale : is visible by default on Pumps Stop and Pumps start. It should remain hidden on Flow rates

because it is a virtual 0..1 scale. Y-scale : is visible by default on all plots Plot legend : is visible by default on all plots. It gives access to many settings, like: o Color (but color is forced by the program). After a color change, you can restore the default colors by

clicking the command Set colors to default. o Line style o Line width o Plot type and interpolation o Filling (not recommended) o Points style

These settings are not saved when the screen is closed. Scale legends settings are hidden by default. Graph palette is hidden by default on all plots. It is useless since the plots are continuously refreshed

and scales are recomputed. Cursor legend is visible by default only on Flow rates. It allows to configure the cursors shapes and

behaviour. It is recommended to keep the default settings since cursors are integrated to the monitor functions.

We call cursors the highligted crosses on the plot surface which allow to scan through displayed data: When you move the mouse over them, the mouse cursor changes into a handle which allows to grap and move the plot cursor. By default the cursors will link to the plot which is closest to them. You can also move the cursors with the dedicated keypad:

Right arrow : moves the active cursor(s) from the oldest to the more recent points. Left arrow : moves the active cursor(s) from the recent to the older points. Top/down arrows : switch the cursor from one to the next plot.

Other plots settings : Autoscale X : is ACTIVE on pumps stop and pumps start, but INACTIVE on flow rates. Autoscale Y : is ACTIVE on all plots.

Do not change these settings


PAG 38 OF 47 1


5.1.2 Commands and settings

Most of these commands will be explained together with the plots they are related to. Stop closes the monitor. Obviously, the events storage process keeps active.

Continuous real-time plot zone

Vertical real-time plot for flow rates, pressure, active volume and hook position. The internal buffer holds 2 hours of data which are loaded from the time based storage at startup. A new set of points is added every 3 seconds. Horizontal scales: the minimum is supposed to be always 0. Maxima are common to several variables:

One maximum for all flow rates One maximum for hook position One maximum for pressure One maximum for volume

Zoom and scroll : the vertical span can be increased (zoom scrollbar) so as to show only 15 minutes of data. The scroll bar allows to navigate this 15 minutes window through the last 2 hours of registered data.

Real time and memorized values : combined with the plot legend, the program displays the curent value for each of the 7 curves. Just on the right, it gives the values at main cursor position. These values are obviously read-only. The main cursor is the yellow one.


PAG 39 OF 47 1


The plot is a fixed configuration: you can not display any other variable. Related DBRs are : Flow rate pumps: 7 01 05 Flow meter IN : 7 01 07 Flow meter OUT : 7 01 09 Normalized flow rate OUT : 7 01 10 Hook position : 2 01 01 Pressure IN : 7 01 01 Active mud volume : 9 01 02

Displays are refreshed every 2 seconds.

Cursors : The flow rates plot has 2 cursors. Main cursor: yellow square point and yellow dotted

line Secondary cursor: light grey cross and light grey solid

line

When you move the main cursor, the program indicates on which plot it is locked: just above the black display zone. The message also contains its current temporal position. The secondary cursor allows to measure variations between different zones of the plot area. In this example, both cursors are locked to the pressure line. The program displays the difference between the 2 positions, as well in time as in pressure units:

You can also read values from different curves, but some (like : hook position pressure) makes no sense. The program will display *?! if the units are not exactly the same.

Command read flow rate data allows to read the last 2 hours of data from the time based database. This operation is made automatically at startup. If data do not load, check if the local clock is synchronized with the time of Saert-2. If it is, check if the time based storage has been running for at least 2 hours.


PAG 40 OF 47 1


5.1.3 Events-related X/Y plots for active mud volume

These two displays works alternately, one at pumps stop, the other on pumps start. The scope is to check if the active mud volume turns to its initial value after a Stop-Start sequence, or if the mud volume changed during the blackout time. The events storage detects changes of the Flow status 31 02 62 and creates a new event.

Event type 6 for pump stops Event type 7 for pumps starts

Each event record contains start and stop date and time, a sequential number for identification, and some additional values. It is associated to a collection of active volume records. The size of this collection depends on the variable 99 63 17. Its default value is 5 minutes, which are 150 records sampled every 2 seconds. The event is considered complete only when the recording time has run out, or when the flow status changes again.

The PCM monitor displays the data of several events: their actual number depends on the setting last X events which default to 20. Hereafter we will relate events of the same type as 0 for the current event, -1 for the last complete event, -2 the event before, and so on.

The legend has space for 14 curves maximum. You can configure the plot so as to show more than 14 events but the curves above #14 will not be accessible for configuration.

The colors are redefined every time a new plot is created: Bright orange and thick line for the most recent complete

event (event 1) Orange thin line for event 2 Blue thin lines for events 3 to N, with decreasing

brightness. If the registration is still running for an event (event 0), it

is displayed as a thin yellow line with red points. This plot is redesigned as bright orange when the event closes.

To identify an event, just move the cursor to a curve. The program will react as following : The curve becomes bright yellow which makes it easier to distinguish in between all the other plots The rectangle below the plot displays : o The event identification number o The time at which this point was saved

-1

0

-2 -3


PAG 41 OF 47 1


o The volume variation since event start. Dragging the cursor right or left you can inspect all the values of the plot, point by point. On curves intersections it may happen that the cursor jumps to the other plot. You can display the cursor legend and use the cursors keypad to follow eactly one curve.

o The id of the complementary event (for a pumps stop it is the previous pumps start and vice-versa)

o The volume difference at the events termination. Lets suppose that event #231 is a pumps start, which terminated after 4 minutes with a volume variation of -2.51 m3. Its complementary event is #230 (pump stop) with a volume variation of +2.30 m3. The final volume variation (stop--> start) is a loss of 0.21 m3.

When moving the cursor of the pumps start plot, the complementary event of the pumps stop plot (above) will position automatically.

If you need more details about an event, you can click the checkbox Show event details . The yellow bordered rectangle below the plots will be covered with additional informations about the selected event:

Start date and time Stop date and time Total measured depth at start time Annular volume at start time

To see the associated pumps data collection click the checkbox Show numeric values . The alarms zone and the legend of Flow rates will be covered with two numeric tables. Note that the program finds automatically the records associated to the current cursor positions. If an alarm rises while the tables are open, the alarm messages will partially recover the tables.

Each pumps plot displays two additional informations: The final volume difference with the previous event of the

same type. These values do not change when you select different curve, since they relate to the results of the two most recent events.

The final volume difference with the previous complementary event.

Hiding some events: It may be necessary to eliminate some non-significative events. To do so, just select the event to hide and click on the red button labelled Hide selected curve. The wrong curve will be eliminated from the display and another event will be loaded, so as to have always the last X events on the screen, according to setting. The event will not be actually cancelled but flagged so as to not compare on the screen any more. The advantage is work on a selected set of curves. The drawback is that not all events will be able to find their complementary event.

The hidden events can always be restored with the command button Restore all hidden curves.

Envelops : to allow some anomaly detection, the program defines two virtual curves: one curve called max contains all highest values of the displayed curves + margin. The other, called min contains all the lowest values of the displayed curves margin. The margin is defined as a % of the value. Envelope curves are like normal event curves, one can select them and visualize the data, but they are not related to any particular event.


PAG 42 OF 47 1


Here below an example of an envelop designed with a 12% margin:

The envelope should be representative of the real volume evolution. You should eliminate incomplete or abnormal events so as to allow an accurate detection of well flowing or mud loss. On every new event , the program will automatically calculate and draw the envelope.

For instance, lets consider this example of pump stop data :

After selecting and hiding the wrong curves, we obtain the following graphics. It is now much better adapted to the detection of anomalies.

Envelop was defined as 5% in this example.

Envelop with filling (to set filling, click on legend of min , select fill base line , mx . Then command draw envelop ).

No envelop at all (command Cancel envelop )

Envelop is set.

This event is just a straight line : it is meaningless

Abnormal curve due to sensor adjustment: to be eliminated

Pump stop during a mud transfer: not significative event


PAG 43 OF 47 1


5.1.4 Alarms

The program rises alarm messages on 3 types of situations, all of which are related to the pumps events. The new volumes curve lies outside of the envelope: it means that the volume increase or decrease is

N% more than in all the previous similar situations. This alarm would trigger immediately, giving an early warning. It resets when the event terminates.

The difference between the new curve and the previous one is more than the percentage defined for the envelope. This is computed point by point as the curve progresses. This alarm would trigger immediately, giving an early warning. It remains active even after the event terminates.

When a pump start event completes: if the final volume decrease does not correspond to the volume increase at previous pump stop. The difference threshold lies again at the percentage defined for the envelope. This alarm can trigger only after 2 minutes. It remains active after the event completes.

LED : in case of alarm, the alarm LED starts blinking Red/Orange. The blinking frequency increases with the intensity of the detected anomaly.

Hereafter some examples :

In this cas the new curve is far away as well from the previous one as from the envelope.


PAG 44 OF 47 1


The pumps start curve looks normal, but the final volume diminution is 4.3 m3 too much, it should be -14.2 with a tolerance of +/- 0.71 m3 . This mud gain of 4.3 m3 must be explained.


PAG 45 OF 47 1


5.1.5 Events storage program rtdb_event_storage

Documentation update : 10/08/2006

Description and versions This program detects events of different types, creates event records and stores them into a dedicated table of the EVENTS_BASED Database. It launchs limited monitorage sub-programs so as to register dedicated context information and limited event logs.

In its current state, the program manages only 2 types of events : pumps stop and pumps start. Several other event types should be added in the future.

Versions and associated GeoDesk programs

Program name Last Version LGIMAS Background program(s) rtdb_event_storage 001.003 released 2006/08/07 GeoDesk Program(s) FLOW_GUARDIAN_PCM Build 89 Size 259232

Technical characteristics : Additional files none RTDB extension file catext_drill_pits_fr.txt Programming langage C Default cycle time 100 / 100 sec Process parameters None Process control variables Chapter 99 63 00 of the catalog Database Depth-based for descriptions + Events-based for data Tables RT_EVENTS and RT_PUMPS

Related database variables

W this variable is an output of the program R this variable is an input Colour codes: Overwriting program output: no user-input allowed Non-overwriting program output: user input is allowed Counter User-set parameter Value provided by another LGIMAS program User command trigger Table

N DB-Ref W R Description Unit 31 02 62 R Flow status (=1 if flow rate IN is significative)

31 10 01 R Number of managed events

31 10 02 R Shift in events table

31 10 11 W Event #0 Alarm



W



PAG 46 OF 47 1


1 99 31 12 R Current date and time

2 99 31 15 R Seconds counter s 3 99 63 04 W Programs activity description message

99 63 05 W Programs status: 0 : idle, ok 101: Inserted data into RT_EVENTS, all right 103: Data initialization 105: got system error after data insertion into RT_EVENTS 108: cannot connect to Data Base 109: cannot create table RT_EVENTS 161: ok, inserted data into RT_PUMPS 165: got system error after data insertion into RT_PUMPS

99 63 09 W Current primary key of RT_EVENTS table

99 63 11 W R Command : future implementation

99 63 12 W R Errors counter

99 63 16 W Data alarm flag

99 63 17 R Maximum time to monitor PUMPS events s

Events database and Tables structure

The EVENTS database is created automatically by the program at startup, if it does not exist yet. Its name is built from the Depth-Based DB name, by appending _Events to the name body. For instance, a DB named MyDb.gdb becomes MyDb_Events.gdb.

By the time, the events database contains only 2 tables, described here below :


PAG 47 OF 47 1


The corresponding descriptions are created in the D_ALIAS and D_TAB_ALIAS tables of the depth-based DB.

Pumps related events

The trigger variable for pumps events is the FLOW STATUS (31 02 62). Every change of its value creates a new pumps event. The program starts to memorize the total active volume and the different flowrates. Timing is provided though the column RPTU_DT which holds the system time. Recording frequency is 0.5 Hz (1 record every 2 seconds). Event types are : 6 : pumps stop, associated to the DBR 31 10 17 7 : pumps start, associated to the DBR 31 10 18

The recording stops after a fix time, defined in the DBR 99 63 17. By default it is 5 minutes, but depending on the rig settings, it must be increased so as to record pump events as completely as possible. 15 minutes could be the maximum time.

Records of the RT_EVENTS table or of the RT_PUMPS table are never

G-90-041-VAG-10_ENGINEERING _vers.01.00

Documents

Transcript of G-90-041-VAG-10_ENGINEERING _vers.01.00