Lag Manual

Delta Lag Manual
5.3.x Server Series
© 2007 Datalog Technology Inc.
Version 1.1 July 2007

Written by: Mark Pickell
To be a Worldwide leader in providing drilling and geological monitoring solutions to the oil and
gas industry, by utilizing innovative technologies and delivering exceptional customer service.
I 5.3.0 Lag Reference Manual
Table of Contents
Foreword 0
Part I Introduction 1
Part II Theory 2
Part III Configuration 4

1 Basic Requirements
...................................................................................................................................
for lags 4
Time-Based Lags
.......................................................................................................................................................... 4
Stroke Based Lags
.......................................................................................................................................................... 4
Air-Based .......................................................................................................................................................... 5
Volume Based..........................................................................................................................................................
Lags 5
Override Lags .......................................................................................................................................................... 5
2 Lag Configuration
...................................................................................................................................
GUI 6
3 Lag Configuration
................................................................................................................................... 6
4 Lag delays ................................................................................................................................... 7
In .......................................................................................................................................................... 7
Out .......................................................................................................................................................... 8
Return .......................................................................................................................................................... 8
Surface .......................................................................................................................................................... 8
Delay Classifications
.......................................................................................................................................................... 8
Primary ......................................................................................................................................................... 8
Default ......................................................................................................................................................... 8
Other ......................................................................................................................................................... 8
Delay Methods.......................................................................................................................................................... 8
5 Lag Delay Gui................................................................................................................................... 9
6 Lag Records................................................................................................................................... 11
Lag Type .......................................................................................................................................................... 11
Delay ID .......................................................................................................................................................... 12
Trigger .......................................................................................................................................................... 12
Max Trigger .......................................................................................................................................................... 12
Check Mode .......................................................................................................................................................... 14
Parameters .......................................................................................................................................................... 14
Internal Calculations
.......................................................................................................................................................... 14
UserDefined Calculations
.......................................................................................................................................................... 15
Translation
......................................................................................................................................................... 15
Lag Record Gui.......................................................................................................................................................... 17
Part IV WWtestlag 21
© 2007 Enter your company name

Introduction 1
1 Introduction
With the release now of WellWizard Server 5.3.0 the Lagging software has been completely modified
to now fully support:
User Defined Calculation

In Lags
Delta Lags
The addition of these new features now provides the user of the WellWizard system with extremely
accurate lag information.
The addition of IN or Down lags to the system refers to the monitoring of data going into the hole rather
then the traditional Out monitoring where you only calculated the data coming out of the hole. With the
addition of knowing what is going into the hole you can now also properly calculate and log Delta
values (Out - In).
The User Defined Calculations is in addition to the lag system (though used by the lag system heavily)
and allows for calculations to be added to the system without intervention at the R&D level. This
allows one-off or job-specific calculations to be entered and utilized enhancing the value of data to the
client.

2 5.3.0 Lag Reference Manual
2 Theory
The theory of lags is difficult to explain generally but I will try my best to explain how the new system
works. Taking the picture below I wish to run you through an example of monitoring a Gas in and a
Gas Out parameter.
First you would have a Gas Detection unit located at the Suction pump. This would record the gas
readings in the mud system prior to entering the closed system. This gas reading will have a Surface
(IN) delay of x amount of time until it enters the drill pipe. This Surface delay is normally set as a fixed
time cycle. Once the mud enters the drill pipe we then switch to the In or Down lag counter. This
value uses either the time, stroke, volume or air setting as configured. For example if doing a Volume
lag, we would determine the pipe volume based on the current hole profile to be 100 m3 of mud, the
amount we need to move before reaching the bottom of the hole. Using the values from the pumps
and the flows we know how much volume of mud we are moving over a given time. We simply keep
extracting the value from the current total volume until it reaches zero. At the zero mark we have hit
the bottom of the hole and need to take the gas reading we read some time ago and apply this value to
the current hole depth. The system keeps track of each reading and the total delays per reading and
simply expires them and writes them out as they occur. So unlike out lags the current hole depth will
generally always have a gas reading for the in records recorded unless new delays are introduced that
cause a drilled interval to be skipped.
Second reading would be the Gas Out readings. These are taken generally from the flow line or the
shaker box header. The readings being read need to be lagged back up the database to an earlier
hole depth as they were liberated from the mud earlier on. For example if the current hole depth was
at 100m the gas being liberated would not be read until the proper volume of mud was moved and that
gas reading was brought to the surface. Of course during this movement drilling continues so we can't
take this reading and apply it at current hole depth. The lag system keeps track based on Time,
strokes, volume or air lag the amount of delay to apply to each gas reading read at the surface.
Normally your reading will be written out to the database at a much lower depth than hole depth unless
they stop drilling but keep on circulating the system, at which time it is possible to have a gas out
reading at the current hole depth. Along with the Out lag delay we can also apply a Return delay. The
return delay is the amount of time that is required for the gas that was liberated at surface to actually
be analyzed by the gas detection system or for any other delays you wish to take into account for. For
example a chromatograph would analyze the gas sample taken from the shaker box but not until is
was pulled across the lease by a pump which would take an extra 40seconds. So on top of the Out
delay we would need to add an additional 40 second delay.
The Delta readings which is the sum of Gas Out minus the Gas in is done as a recalc value. This
means that everytime you pull up this information the system actually recalculates the new data (not
stored). So at any given depth it will take the recorded values of both in and out gas readings and
come up with the delta value. This gives you a much truer reading of what was released from the
drilled formation as you remove the gas readings that were injected into the hole.
A round trip would look like -- Surface delays while mud is being circulated to the standpipe. In delays
while the mud is being moved down through the pipe to the bit. (In record recorded). Out delay while
the mud with the newly liberated gasses move back up the outside of the drillpipe to the gas extraction
point. Return delay while the gas is being moved to the gas detector. At which point the readings is
recorded into the database at the proper lagged depth. At this time the delta value is also calculated
and shown.
For those already familiar with gas out lag, think of it this way.
Gas IN - recording a reading that won't occur for some time with reference to depth
Gas Out - recording a reading that has already occurred in reference to depth.

Theory 3

3 Configuration
The lag configuration is stored on the WellWizard server in a file called lags.cfg (which replaces the
older trigger file). This file is an XML formatted file and includes all the different calculations for ratios
and the various lag delays. As this file is quite lengthy a GUI (graphical user interface) was developed
to make the entire configuration operation much easier.
As of this manual the GUI is release WellWizard client 401_4 and above.
3.1 Basic Requirements for lags

All the different lag methods (except AIR) use the basic set of rules to determine whether to process
the lag information or not.
You must be circulating for the lags to function. Circulation is determined by:
1. SPM channel with a value equal to or greater than 6 strokes per minute (with pump efficiencies set
or each pump output)
2. Mud Flow in with a value greater than 0
3. A physcial circulation switch connected to channel MC (mud circulating). See server side notes on
how to setup. (man WWtestlag)
And StandPipe pressure with a value equal to or greater than 500 kpa (-9999 no incoming data is also
acceptable)
3.1.1 Time-Based Lags

Time-based lags is the simpliest form of lag in the system. Time-based is at is says - based on time,
rather than pump rates or volumes. As long as a basic set of conditions are met (see conditions) the
lag will advance. This lag method is used primarily for stand-alone or IDS jobs.
Channels of interest to pull up on your WellWizard screen:
Lag Depth - current lag depth

Lag Time - current lag time
Time to Lag - counter to show how long at present conditions to next lag up
*** A very important channel to watch while doing Time-based lags is the Time to Lag channel under
Drilling Parameters. It is basically a countdown that when reaches zero will update the lag depth. If
this value is decreasing than things are at least working but doesn't rule out improper calibration.
3.1.2 Stroke Based Lags

Stroke based lags are based on actual Strokes. Once the basic conditions are met the system will
determine how many strokes are required to increment the lag depth. This method is more precise
than time based as it takes into effect the speed at which the pumps are moving.
Channels of Interest:
Lag Depth - set function and current lag depth

Lag Strokes- current value of strokes required for next lag up

Configuration 5
3.1.3 Air-Based
Air-based lags are different from the other types of lags in that no circulation condition is required.
Therefore you don't need SPM's, StandPipe, Flow in order to process Air lags. The only requirement
is setting the air-based lag parameters.
Channels of Interest
Lag Depth - shows current lag depth and set function to configure parameters
Lag Time - current lag time based on hole depth
Time to Lag - current time remaining until next lag depth up
*** A very important channel to watch while doing Time-based lags is the Time to Lag channel under
Drilling Parameters. It is basically a countdown that when reaches zero will update the lag depth. If
this value is decreasing than things are at least working but doesn't rule out improper calibration.
3.1.4 Volume Based Lags

Volume based lags are the most precise lags that can be used, but at the same time the most
complicated to configure. Unlike the previous methods where it was either time based or stroke
based, this method calculates the volume of fluid in the hole and how long it will take to circulate to the
surface. This method is quite involved
Basic conditions must be met and then the following conditions are also required:
1. Configuring a hole and pipe profile in the Add pipe section under the Edit menu. Pipe types can be
added through the edit pipe type section under Edit. All information on the hole and pipe should be
entered in here. Alternatively you can use the Jet Velocity channel and set the bit diameter on it. This
will create a hole profile for you.
3. Pump efficiences must be configured in the Pump Output channels
4. StandPipe pressure must be greater or equal to 500kpa.
ALTERNATIVELY
Bring in Mud Flow In and Standpipe to fit our basic circulating requirements and then bring in externally
Annular Volume (TVA) and Pipe Volume (TVP).
Channels of Interest:
Lag Depth - current lag depth and set function to set lag
Lag Time - current lag time
Time to Lag - counter to show how long at present conditions to next lag up
Lag Volume Left -- like the Time to lag channel shows the decreasing volume left to be circulated
before lags up.
Lag Volume Adjust - this shows the current value of Lag Volume Adjust as set by Lag Depth
3.1.5 Override Lags

Override lag method though it is an option isn't one that will be used. It's set automatically by the
server whenever a 3rd party brings their Lag Depth into the WellWizard system. This then removes all
calculation and processing down to calculate the lag depth. If the system is in override and it shouldn't
be check your incoming wits files for Lag Depth (DRTM)

3.2 Lag Configuration GUI

When firing up the GUI you are presented with this initial screen. The GUI interface automatically
loads up the lags.xml file from the current well. All changes are not commited back to the system until
you hit the Commit button. Hitting Quit first will cause all changes to be lost.
The initial screen "Lag Configuration" allows you to set the lag method type and then the
corresponding variables. Only those variables requiring attention will be highlighted. The meters or
feet unit box allow the user to modify the variables based on the units of region or familiarity. Please
note that the actual xml file is in based units of metric only. The GUI app will do all the unit translations
between meters to feet prior to writing out the file.
3.3 Lag Configuration

The Lag configuration screen is the main screen where most users will work in. The defaults lag
entries in the system are generally enough for most applications and only the initial variables need to
be entered.
Lag Method - this dropdown box allows the user to select the lag method desired. Air, Strokes, Time,
Volume and Override. Please see the respective sections for more details on each of these lag types.
Note that for both Volume and Override Lag methods there is no further need to set any values on this
screen.
Abs Lag Depth - this is the absolute lag depth used as a starting point for Air, Time and Strokes. This
is the reference depth that the absolute lag time will refer to. Usually this value is current hole depth or
a known depth and time combination
Abs Lag time - this is the time in seconds it would take a sample to be liberated from the drill bit and
arrive at the Abs Lag depth value.
Abs Lag Time Increment - this is the time increment in seconds that would occur over the next 100
meters (or feet if in Imperial units). As you drill deeper how much longer should the delay be. For

Configuration 7
example at 100m you have a delay of 100s. If you set the increment to be 100s as well, then when
you hit 200m of drilled depth your lag time will be 200s. At 101m, it will be 101s, ......
Abs Lag Depth Down - this is the IN lag value similiar to the Out lag values. This is the value you have
a known or calculated depth you can assign a time value to.
Abs lag Time Down - based on the value set in Abs Lag Depth Down this is the time in seconds that a
gas sample going into the system would take to hit the lag depth down depth.
Abs lag time Down Increment - as you drill deeper how much time in seconds should be added to the
lag time to compensate for the large depth value
Abs lag strokes - for stroke based lag systems how many total strokes would it take to reach the depth
value in Abs lag depth. (not based on volume, simply on stroke count). Take into account the
difference in volume between the pipe volume and the hole volume.
Abs lag strokes increment - like time how many extra strokes over a 100 meter or foot range would
need to be added to the strokes counter to adjust for the deeper depth.
Abs Lag strokes Down - for strokes going into the hole how many will be required to get to the value
inserted in Abs lag down depth. Remember the strokes should only take into account the pipe volume.
Abs lag strokes down increment - as the system goes deeper how many extra strokes are requried for
the In lag stroke readings per 100 meters or feet.
3.4 Lag delays

The Lag delays section defines the various delays that can be used in the system. The default delays
are designed to fit most needs and shouldn't require users to modify often. It is important for the user
to understand the order of operations when it comes to lags to better understand the actual values and
when the different lag records get written out. All four delay types all follow the same sequence -
expire Volume first, and then strokes and then time. For instance if you apply a value to STDGI (Gas
in Sample Time delay) to a volume based lag when the SURFACE lags expire and moves to the IN
lags you would first calculate your total volume to be moved for that record, expire that volume and
then tack on a time delay as per STDGI (note that in WWtestlag this will move to screen 4).
Order of operations is:
Surface delays which can be either volume, stroke or time. Once expired the IN delays are applied.
IN delays are calculated. If you mix two different types of delays then the order of operations is
Volume, stroke and then time.
Out delays work just the same as In delays. Volume, stroke and then time are applied to a record.
Once these are all expired the record moves to a RETURN delay
Return delays are applied and then the record is written out.
There are four major types of delays that can be used in the system.
3.4.1 In
The IN delay is to allow the user to apply a delay to the IN lag system to account for any anomolies or
changes in rig operation. While this variable is set the extra delay will be cycled through before the
main in lag is processed. This may be something like a temporary bypass of the flow system.

3.4.2 Out
The Out delay is a delay which can be used to compensate for any variances that the system isn't
taking into account already. This delay will be added to the lag queue prior to the Out lag variable. For
the Out delay this is accomplished by editing the value of Lag Volume Adjust. This in pure form is a
fudge factor.
3.4.3 Return
A Return delay is the delay experienced when a recording sensor takes x amount of time, strokes or
volume to analyze a sample. For instance a gas trap that liberates the gas from the mud needs time
to send that gas sample to a chromat. Or a GasWizard requires 40 seconds to analyze the gas
liberated from the probe (based on Mark I systems). There is by default a Return delay (unless you
remove it) that can be set in the WellWizard system that the return lag delays take into account --
channel "Gas Out Sample Time Delay". If you set a value to this channel this will delay all the Gas
variables upon transistion from Out delay to Return delay (taking into account polylines)
3.4.4 Surface
A Surface delay is a delay that takes place on the IN side. This delay takes into account any surface
delays that can be experienced from the recording sensor position to and including the standpipe.
This delay can be either a Time, Stroke or Volume delay. For time as long as the system is circulating
the timer will continue to function. Stroke is based on the pumps so they must be pumping to move
this delay forward. Volume is based on pumps and their efficiences to calculate volume of mud
moved. The system takes into account the channel "Gas In sample time delay" for any in Gas In lag
delays.
3.4.5 Delay Classifications

There are three different classifications types that can be assigned to a lag delay. Primary, default and
other. These classify whether the delay should be applied to all or just some of the record types.
3.4.5.1 Primary
A Primary delay whether it be in, out, surface or delay is applied to all lag entries that fit the record
type. If you have a primary IN delay with a value of 10 seconds then all In lags will be delayed by
10seconds.
There can be only one Primary lag defined per record type.
3.4.5.2 Default
A default lag delay can be either of type in, out, surface or return. These lags delays can be assigned
to some or all of the record type and are created to take into account delays which are common for
several different lag records.
3.4.5.3 Other
These will generally be any one-off delays you wish to include for any one of the types.
3.4.6 Delay Methods

After choosing the lag type, it's classification you then need to set the actual delay or delay source.
Options are:
Volume - this is simply a value that will be added to the delay that must expire before it moves on.
Stroke - a stroke based delay that must expire x amount of strokes
Time - a time based delay that must expire x amount of time
Channel - Channel delays refer to any channel in the system that can be used to apply a delay. LVA

Configuration 9
being lag volume adjust can be set in the WellWizard client and the value of this is applied to the delay
Volume and Time - this applies a two step delay. First a volume delay and then a time delay
Volume and Channel - First applies the volume delay and then a channel delay
((( note that there is no Volume and stroke combination and the volume calcs are taken from the
strokes so they essentially are the same)
Stroke and Time - first applies the stroke delay and then a time delay
Stroke and Channel - first applies the stroke delay and then the channel time delay
Time and channel - as these are both time delays it will delay the total combination of both channels
3.5 Lag Delay Gui

The lag delay Gui section appears as:
Users can Add new delays or modify/delete existing delays. Each delay shows the user given name
for the delay, it's type, primary or default and the type of delay it is.
Adding a new lag delay

When adding a new delay the user simply hits the Add button. The screen then changes to the Add
lag Delay screen.

From this screen you can enter your name being the descriptor of the lag, the lag type, it's
classification and then the methods. The appropriate method boxes will highlight at the bottom
allowing you to enter in the required variables.
Modfiying a lag delay

Modifying an existing lag delay is no different than adding a new lag delay, it simply allows you to
modify the same boxes but not create a new lag delay.

Configuration 11
Deleting a lag delay

Deleting a lag delay will prompt a "Are you sure?" screen and if you state yes then the lag is removed.
3.6 Lag Records

The Lag Records section is where the actual lags are defined. This section is all about what needs to
be lagged, based on what parameter and are there any calculations required to perform these duties.
In this section there are only three types of lags remembering that these are not the delays but the
actual lag records.
1. Out - these are the out lags. These are any records that are being based on the lag out
and the lag return delays
2. In -- these are the lag in records based on the lag in and lag surface delays.
3. Delta - the delta calcs for the various gas ratios.
3.6.1 Lag Type

When creating a new lag record it is important to pick the correct lag type:
IN - an in lag which any primary in lags will default to.

OUT - any out lag which the out primary delay will apply
Delta - a lag record or more likely a calculated record to determine the delta between an IN and a OUT
record.
Event - placeholder for future improvements.
Cuttings - future placeholder for cuttings wizard.
3.6.2 Delay ID
The Delay ID section allows you to pick any of the default lags based on your Lag Type. Remember
that primary delays are included automatically (non-optional).
3.6.3 Trigger
This is the mnemomic of the channel that the data in the parameters section is being triggered from.
Normal usage is to use DRTM (Lag Depth) for Out lags, and any third party mnemomic for Override
records.
For In and Delta records this option is not available.
3.6.4 Max Trigger

This value groups a number of parameters together to trigger them all at the same instance rather
than individually. This is normally triggered off of a calculated value and the result of the calculation is
used to determine the variables used for each of the parameters. For those whom are familiar with the
previous lag versions this is the trigger used by the GasLag system.
MaxTrigger should be used for all channels that are Gasses. There is extra logic applied to any
MaxTrigger value to account for trips, connections and gas sample delays.
An example of usage would be chromat gasses. The chromat gasses would all be grouped together
and a snapshot taken and databased whenever 'Total Hydrocarbons Out' reached a new maximum
over the gas interval. This is part of the recalculations to keep all the gasses properly adding up.
In the default MUDLOG template there is an example of this in action. Lag Record 6 shows that it has
a maxtrigger of HYDC1. In the user-defined calcs we can see that HYDC1 is a calculated value being:
METH+ETH+PRP+IBUT+NBUT+IPEN+NPEN+NHEX+NHEP+NOCT+BENZ+TOLU+MCH
When HYDC1 is the largest value over the interval we go ahead and take the values of each of the
individual components that created that maximum HYDC1 value and store those. Normally we would
store the maximum for each of the gasses but then if you were to add up those gasses individually you
would not have the correct HYDC1 value.

Configuration 13
A clearer example of why MaxTriggers are used. In the above example we mentioned Hydrocarbons
as being the trigger. Previous to this change your database would look like the following:
Depth Hydrocarb Methane Ethane Propane IsoButane IsoPentan N-Butane N-Pentane

ons e
1000 10 5 3 0.5 0.3 0.2 0.2 0.1
1000.2 9 6 2 0.3 0.2 0.1 0.1 0
1000.4 10 7 1 0.3 0.3 0.2 0.1 0.1
1000.6 12 7 2 1 0.5 0.4 0.2 0.2
Table Gaslag 1 -- old method of databasing Gas
Notice how the data presented doesn't add up to the Hydrocarbons total. Hydrocarbons is supposed
to be a total of all the gasses together -- yet often in your database you will see that this doesn't hold
true. The reason is that during the same depth interval you recorded the maximum value for each of
the different gasses and each gas may have reached a maximum interval at different points over the
recorded interval. For instance at 1000m above we have a hydrocarbons with a value of 10%. This
value is added from Methane, ethane ....but it is also the max Hydrocarbons over the 1000m interval.
The highest Hydrocarbons may not have been the value of Methane max + ethane max + propane
max..... it is simply the highest calculated Hydrocarbons over the run.

With MaxTrigger records when you record the Max Hydrocarbon take the gasses for Methane, Ethane,
propane and so on as well. So now in reality your database records the Hydrocarbon Max and the
associated gasses at the time, and not the max gas over the interval. By doing so all the gasses will
add up and appear proper. From the table "Gaslag 2" below you can see that the gasses all add up
now.
Depth Hydrocarb Methane Ethane Propane IsoButane IsoPentan N-Butane N-Pentane

ons e
1000 10 5 4 0.5 0.3 0.1 0.1 0.1
1000.2 9 6 2 0.4 0.3 0.2 0.1 0
1000.4 10 6 2 0.7 0.4 0.3 0.4 0.2
Table Gaslag 2 -- Gaslag method
3.6.5 Check Mode

Three mode options available:
1. None - standard mode type. This mode is used by most records and allows for lag
channels to be recorded when the bit is off bottom. Recorded data will not be overwritten but new data
can be written to the database. Example will be circulating gasses to surface while bit is off bottom.
2. Ream - this option allows the parameters to be re-lagged for a section. Enabling this option
causes a REAM-Lag button to be visible on the WellWizard client. This button is disabled by default
operating this mode as if it were a NONE mode option. If the button is enabled then pre-existing data
can be overwritten while this option is enabled.
3. Bottom - this option will only allow the parameters to be recorded while the bit is on bottom.
If the bit is off bottom and circulation continues you would not record any new data until you went back
on bottom. Example usage would be triggering gamma data off the bit depth.
3.6.6 Parameters
These are the parameters that are to be lagged into the database based on the Check Mode, trigger
and Max trigger fields.
SRC column - identifies where the source data is obtained from to be lagged
DST column - the destination column of where the data should be written to. Most often this is
the same mnemomic so if left blank this is assumed. Note that the SRC data refers to the time and
DST refers to the depth (thus same channel can be used for both).
Op column - the op column can be either Max, Min or AVG.
Max - Maximum value of parameter SRC will be written to parameter DST over the lag
interval.
Min - Minimum value of parameter SRC will be written to parameter DST over the lag interval.
Avg - Average value of parameter SRC will be written to parameter DST over the lag interval
3.6.7 Internal Calculations

The internal calcs fields are used to setup the defined parameters that you wish to use to monitor the
lag depth and time to update progress gauges.
By default the mud surface parameters setup and use the lag depth channel (DRTM). If all of these
parameters are absent than the calcs are not done so be sure to include at least one of them.
This section is best explained through an example.

Configuration 15
DRTM - lag depth, this value shows the lag depth for the mud-out parameters. It doens't though show
any delays being applied extra above the primary delays to the various other lag parameters. Example
would be a flare stack gas detection. The lag depth shown and time to lag shown do not take into
account this extra delays applied to a flare stack gas detector. To show the proper lag depth and time
to lag for the flare stack we can create our own internal calc to show the proper values for flarestack
lag depth and flarestack time to lag.
How to do this:
WWtext - create channels FDRTM by copying DRTM, FTDRTM by copying TDRTM and FDRTT by
copying DRTT.
In the lag GUI setup your internal calcs to be:
LagDepth - FDRTM
LagTime - FDRTT
TimeToLag - FTDRTM
Now when restarting your WellWizard client you can pull up these new channels and once they start
calculating (off-bottom to on-bottom) you will see that any extra delays you have assigned to this
channel will show up in the time to lag being different than that of the mud parameters.
For each Lag Record you can add:
Lag Depth - the depth of the current lag record

Lag Time - the time to for the current lag
Lag Strokes - number of strokes for current lag
Down Time - Lag time going into the Hole
Down Strokes - number of strokes into the hole
Time to Lag - time till next lag interval
LagVolumeLeft - volume left to next lag interval
Lagtime RB - lag time in reference to bit
Lagstrokes RB - lag strokes in reference to bit
3.6.8 UserDefined Calculations
Defines any calculations that require to be done on the parameters. Most often used in the delta and
the Lag parameters using a Max Trigger. These can also be used as userdefined calculations. When
adding or modifying the screen presented asks for:
Translation: This is the type of calculation you wish to perform. See subsection for more
details.
Name: name descriptor of calculation
Output Mnemonic: where should resultant calculation be stored
Mappings: Mappings follow pattern of ID SYM:Mnemonic and SRC being Mnemonic.
As of this manual the ability to define your own calculations is not included in this early version. Later
releases will include this option.
3.6.8.1 Translation
There are several different translation calculation types. These are all pre-defined calculations that
you can use and then map your channel selections into. If you need to modify the calculation you will
need to do so directly on the lags.cfg file. (always make a backup).

Types are: (note that SYM:channel is a mapping variable, see below on mappings)
Balance Ratio - calculation: (SYM:METH+SYM:ETH)/(SYM:PRP+SYM:IBUT+SYM:NBUT+SYM:IPEN

+SYM:NPEN)
Character Ratio - calculation: (SYM:IBUT+SYM:NBUT+SYM:IPEN+SYM:NPEN)/SYM:PRP
Delta - calculation: Out - In.
Basic delta calculation that simply does the Out value minus the in value. No checks done to
see if both are present.
Delta_Out - calculation: Out - In.
Same as Delta calc but does processing first to see if both values are present. If IN value is
not present than Delta simply equals the Out value.
Gas_Ratio_Analysis - calculation: Internal only
This calc uses the ratio between Balance, Character and Wetness to return a string variable.
Gas_Ratio1 - calculation: SYM:METH/(SYM:PRP+SYM:IBUT+SYM:NBUT+SYM:IPEN+SYM:NPEN)
Gas_Ratio2 - calculation: (SYM:PRP+SYM:IBUT+SYM:NBUT+SYM:IPEN+SYM:NPEN)/SYM:METH
Total_Gas_Chromat - calculation:
SYM:METH+SYM:ETH+SYM:PRP+SYM:IBUT+SYM:NBUT+SYM:IPEN+SYM:NPEN+SYM:NHEX
+SYM:NHEP+SYM:NOCT+SYM:BENZ+SYM:TOLU+SYM:N2+SYM:CO2+SYM:MCH
Total_Hydrocarbons - calculation:
SYM:METH+SYM:ETH+SYM:PRP+SYM:IBUT+SYM:NBUT+SYM:IPEN+SYM:NPEN+SYM:NHEX
+SYM:NHEP+SYM:NOCT+SYM:BENZ+SYM:TOLU+SYM:MCH
Wetness_Ratio - calculation:
(SYM:ETH+SYM:PRP+SYM:IBUT+SYM:NBUT+SYM:IPEN+SYM:NPEN)/(SYM:METH+SYM:ETH
+SYM:PRP+SYM:IBUT+SYM:NBUT+SYM:IPEN+SYM:NPEN)*100.0
MAPPINGS
With all the translation types shown above each requires a mapping for each of the variables in the
formula. The mappings are currently based on the following pre-defined options:
"SYM:BENZ" comment="Benzene"
"SYM:CO" comment="CO - Carbon Monoxide"
"SYM:CO2" comment="CO2 - Carbon Dioxide"
"SYM:ETH" comment="C2 - Ethane"
"SYM:H" comment="H - Hydrogen"
"SYM:H2S" comment="H2S - Hydrogen Sulfide"
"SYM:HE" comment="He - Helium"
"SYM:IBUT" comment="iC4 - Iso-Butane"
"SYM:IN" comment="Input"
"SYM:IPEN" comment="iC5 - Iso-Pentane"
"SYM:MCH" comment="Methylcyclohexane"
"SYM:METH" comment="C1 - Methane"

Configuration 17
"SYM:N2" comment="N2 - Nitrogen"

"SYM:NBUT" comment="nC4 - Nor-Butane"
"SYM:NHEP" comment="nC7 - Nor-Heptane"
"SYM:NHEX" comment="nC6 - Nor-Hexane"
"SYM:NOCT" comment="nC8 - Nor-Octtane"
"SYM:NPEN" comment="nC5 - Nor-Pentane"
"SYM:O2" comment="O2 - Oxygen"
"SYM:OUT" comment="Output"
"SYM:PRP" comment="C3 - Propane"
"SYM:SO2" comment="SO2 - Sulfur Dioxide"
"SYM:TOLU" comment="Toluene"
If you wish to change a variable in a formula when entering in the parameters for the formulate simply
change the mapping. For instance to use Iso-Pentane in place of ethane in a formula simply define
the mapping as being SYM:ETH -- IC5
3.6.9 Lag Record Gui

The Lag Record screen displays all the basic info about the lag record itself. It displays the Type, the
trigger channel, the lag delay assigned to it, the max trigger, mode and then displays a count for the
various fields included. Params (parameters) shows how many lag parameters are assigned to this
record. Int. Calcs shows the calculated channels that are assigned to the variable. User calcs shows
the number of user defined calcs in this record.
Adding a new Lag Record

Adding a new lag record brings up the dialog below. This dialog allows you to enter your lag type, and
then any delays that fit that type you can assign to this record. The user must know the mnemonic
used for trigger, max trigger, parameters and for any of the calc types. For the parameters, Internal
Calcs and User-defined calcs pages another window will open up allowing the user to enter the
variables.

Parameters
User needs to define their source, destination and

then using the drop
down box which operator they wish to apply. Leaving
the destination box empty
implies that you wish to lag to the same channel.

Configuration 19
Internal Calc
Internal calc dialog requires the user to enter in the
calculated name and then
the resultant Mnemonic. For Flare example given in
Internal Calc selection user would add here:
Name: LagDepth
Mnemonic: FDRTM
User defined calc
In this section you would choose the pre-

defined calculation type (see translations).
The name would be a descriptor
of this calculations usage. The Output
Mnemonic is the channel you wish the
resultant calculation
to be stored and viewed.
The Mappings section when you modify or

add will ask for ID and SRC. ID being the
calculation symbol such as SYM:METH or
SYM:ETH (see translation) and SRC being
the channel you wish to map to it. Normally
this would be the same channel SYM:METH
being METH but this is settable by the user if
the require it to be changed.
All required mappings must be included.


WWtestlag 21
4 WWtestlag
WWtestlag is the testing program which can be used to verify operation of the system. As it is hard to
tell what is happening with lags, are they being processed, are they actually counting down, are they
really working it was necessary to come up with a interface on the server side to indicate status of the
lag operations. Proper usage of this tool is best learned by testing and working with the system under
ideal conditions.
Assumption here is at least basic working knowledge of lags and BSD/WW operations.
WWtestlag -W# (# being lwid of well)
Mode - M -- pressing the M key on all screens (except 1 & 2) will change to In only, Out only, In and
Out, control lags or lags in memory
Screen 1 (default screen, use #1 key to jump to)

This screen contains all the basic information about the lag status.
a. Lag method - type of lag configured
b. Configuration variables (abs lag depth, time....)
c. Current sample depth
d. # of lags in the various queues.
Screen 2 (use #2 key)

Lag Record screen shows all the various lag records being processed. Important to
note if the Processing is Enabled.
Screen 3 & 4
These screens show the Time based delays that the lags are being processed
through. Screen 3 shows the in & out lags and should only contain data if using the Time based
method. Screen 4 is the irrespective of pumping screen and is also used for other lag methods when
time delays are included.
Screen 5 & 6
These screens show the volume related lags.
Screen 7
This screen displays the stroke related lags info.
Screen 8
Detailed info on the various lag records being processed (use M to scroll through)
Screen 9
Displays the current counter values for the various time, volume and stroke variables

Lag Manual

Încărcat de

Informații document

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

Lag Manual

Încărcat de

Drepturi de autor:

Formate disponibile

Delta Lag Manual

5.3.x Server Series

© 2007 Datalog Technology Inc.

Version 1.1 July 2007

Part III Configuration 4

© 2007 Enter your company name

User Defined Calculation

© 2007 Enter your company name

© 2007 Enter your company name

© 2007 Enter your company name

3.1 Basic Requirements for lags

3.1.1 Time-Based Lags

Channels of interest to pull up on your WellWizard screen:

Lag Depth - current lag depth

3.1.2 Stroke Based Lags

Lag Depth - set function and current lag depth

© 2007 Enter your company name

3.1.4 Volume Based Lags

3. Pump efficiences must be configured in the Pump Output channels

4. StandPipe pressure must be greater or equal to 500kpa.

3.1.5 Override Lags

© 2007 Enter your company name

3.2 Lag Configuration GUI

3.3 Lag Configuration

© 2007 Enter your company name

3.4 Lag delays

Order of operations is:

© 2007 Enter your company name

3.4.5 Delay Classifications

3.4.6 Delay Methods

© 2007 Enter your company name

3.5 Lag Delay Gui

Adding a new lag delay

© 2007 Enter your company name

Modfiying a lag delay

© 2007 Enter your company name

Deleting a lag delay

3.6 Lag Records

3. Delta - the delta calcs for the various gas ratios.

3.6.1 Lag Type

IN - an in lag which any primary in lags will default to.

© 2007 Enter your company name

For In and Delta records this option is not available.

3.6.4 Max Trigger

© 2007 Enter your company name

Depth Hydrocarb Methane Ethane Propane IsoButane IsoPentan N-Butane N-Pentane

© 2007 Enter your company name

Depth Hydrocarb Methane Ethane Propane IsoButane IsoPentan N-Butane N-Pentane

3.6.5 Check Mode

3.6.7 Internal Calculations

This section is best explained through an example.

© 2007 Enter your company name

In the lag GUI setup your internal calcs to be:

For each Lag Record you can add:

Lag Depth - the depth of the current lag record

3.6.8 UserDefined Calculations

© 2007 Enter your company name

Balance Ratio - calculation: (SYM:METH+SYM:ETH)/(SYM:PRP+SYM:IBUT+SYM:NBUT+SYM:IPEN

Character Ratio - calculation: (SYM:IBUT+SYM:NBUT+SYM:IPEN+SYM:NPEN)/SYM:PRP

Delta - calculation: Out - In.

Delta_Out - calculation: Out - In.

Gas_Ratio_Analysis - calculation: Internal only

Gas_Ratio1 - calculation: SYM:METH/(SYM:PRP+SYM:IBUT+SYM:NBUT+SYM:IPEN+SYM:NPEN)

Gas_Ratio2 - calculation: (SYM:PRP+SYM:IBUT+SYM:NBUT+SYM:IPEN+SYM:NPEN)/SYM:METH