Archer Well Company - Vivid field engineers guide course notes

yovaraj 55 views 77 slides Aug 21, 2020
Slide 1
Slide 1 of 77
Slide 1
1
Slide 2
2
Slide 3
3
Slide 4
4
Slide 5
5
Slide 6
6
Slide 7
7
Slide 8
8
Slide 9
9
Slide 10
10
Slide 11
11
Slide 12
12
Slide 13
13
Slide 14
14
Slide 15
15
Slide 16
16
Slide 17
17
Slide 18
18
Slide 19
19
Slide 20
20
Slide 21
21
Slide 22
22
Slide 23
23
Slide 24
24
Slide 25
25
Slide 26
26
Slide 27
27
Slide 28
28
Slide 29
29
Slide 30
30
Slide 31
31
Slide 32
32
Slide 33
33
Slide 34
34
Slide 35
35
Slide 36
36
Slide 37
37
Slide 38
38
Slide 39
39
Slide 40
40
Slide 41
41
Slide 42
42
Slide 43
43
Slide 44
44
Slide 45
45
Slide 46
46
Slide 47
47
Slide 48
48
Slide 49
49
Slide 50
50
Slide 51
51
Slide 52
52
Slide 53
53
Slide 54
54
Slide 55
55
Slide 56
56
Slide 57
57
Slide 58
58
Slide 59
59
Slide 60
60
Slide 61
61
Slide 62
62
Slide 63
63
Slide 64
64
Slide 65
65
Slide 66
66
Slide 67
67
Slide 68
68
Slide 69
69
Slide 70
70
Slide 71
71
Slide 72
72
Slide 73
73
Slide 74
74
Slide 75
75
Slide 76
76
Slide 77
77

About This Presentation

Archer Well Company - Vivid field engineers guide course notes


Slide Content

VIVID™acoustic listening platform field engineers guide 
–training notes
Name: Nicholas Ryan
Archer – Place Month Year

Private and Confidential 2
Field Engineers guide to the 
VIVID™
acoustic listening platform More info at: http://archerwell.com/news-announcements/archer-launches-new-acoustic-listening-platform-for-unrivalled-well- integrity-and-performance-evaluation/ Course notes

We know from life experience that different situations
generate different mixtures of sounds
3
If we press in the valve on a lorry tyre we
will get a predominantly high pitched hiss
This is at a relatively high ∆P compared to
the kettle.
An example may be an across barrier leak.
If a kettle is boiling there will be a
predominantly low frequency bubbling
This is at a relatively low ∆P compared to
the lorry tyre
An example may be gas bubbling through
a liquid filled cement channel
Note: We can only hear the sonic frequencies but bo th situations have 
both sonic and ultrasonic components.

4
Cap removal / pressure release 
Lab experiment - recording the sound of fizzing
carbonated water
We can of course hear the sonic frequencies of fizzing but n ote how the
frequencies go all the way up to high ultrasonic (600+K hz)!
Archer the well company – Private & Confidential

Audible sound
Ultrasound
Acoustic Spectrum
6
Infrasound
S100&S300 Noise
VIVID
Point (S100&S300)
• Exclusively ultrasound measurement
• Relative immunity to road noise (S100) 
• Leak detection possible logging dynamically
• High depth resolution
Noise (e.g. GE NTO)
• Audible only
• Station logging only
• Sensitive to low frequency
• Poor depth resolution
VIVID™sensor
• Full bandwidth from audible to ultrasound
• Multiple channels to fully describe acoustic events
• Dynamic and station logging possible
• Able to filter out specific frequencies e.g. XTU PSU noise
• Powerful post processing capability
Archer the well company – Private & Confidential

Re-cap - S300 & S100 tools
7
• Well proven legacy tools
• Exclusively detect ultrasound
• Wide bandwidths corresponding to multiple VIVID channels
• Unable to detect low frequency ultrasound and sonic fre quencies
• S100: 3 channel tools (A-C)
• High frequency ultrasound
• Good for detecting high ultrasonic leak frequencies – mai nly
primary barrier leaks with high ∆P (high velocity leaks)
• S300: 7 channel tools (A-G):
• Tuned to detect lower ultrasonic frequencies – mainly
secondary and outer barrier leaks and flows with low ∆P (low
velocity flows)
• The grouping of relatively wide frequency bands by th e S100 &
S300 tools may obscure results and reduce sensitivity compare d
to the VIVID tool which has more discrete channels
Archer the well company – Private & Confidential

New tool developed for the Archer VIVID™acoustic
listening platform
8
Tool Name: ALP1-0-02
Description: VIVID, ALP1-0-02, ACOUSTIC LISTENING PLATFORM
Two sensors (CH1&CH2)each optimised for a different part of the acoustic spectr um
Each sensor has a greater number of frequency channels (41) processed in 3
different ways. Gives a total of (2 x 41 x 3 =) 246 ou tput channels per tool
Full spectrum from sonic to ultrasonic (0.4 kHz to 656.6 kHz )
Channel bandwidths specially chosen (Archer I/P) for opti mum response
Higher sensitivity than competitors equivalent sensors due t o sensor design
Frequency vs amplitude colour mapping to easily convey complex information
The prototype was referred to as an FS500 sensor
Archer the well company – Private & Confidential

VIVID™– Unparalleled sensitivity
Confidential 9
• Dual sensors give optimum response across the entire freque ncy
spectrum
• The sensors are integrated with the tool housing by me ans of a patented
pressure-balanced insertion assembly.
• Removing the need for an oil filled pressure compensati on system means
the acoustic window is in direct contact with well fluid, giving proven
industry leading sensitivity

VIVID™(acoustic listening platform)
• Introduced as a new service / platform when VIVID tools are used.
• Range of services with new service names:
VIVID™
Casing and completion evaluation
VIVID™
Cement performance evaluation
• More services to follow: VIVID Turbulent flow analysis, VIVID sand control
mLtrotidplkbig-z
• Tested at The International Research Institute of Stava nger (IRIS) with good
results leading to the potential for cement performance evaluation
• No division into sub-services - /A50, /A70 etc. but there w ill be differing
services: VIVID CCE etc. More complex jobs will require lo nger durations.
• Point services will continue. We have ongoing contracts, th e brand is well
known and a VIVID tool is not always required (e.g. Le akPoint/A10)
• VIVID is the next step up from Point with all the be nefits of the new tool,
colour mapping and interpretation software
• Further
VIVID™
tools to follow.
Archer the well company – Private & Confidential

ICOTA 2018 12
VIVID™– Acoustic listening platform - sales positioning
• Patented ultra-high sensitivity acoustic technology
• Broadest frequency bandwidth and amplitude of acoustic energy with industry-
leading sensitivity
• Detects, investigates and describes leaks that negatively aff ect the
performance of oil and gas wells
• Accurately locates even the lowest energy leaks, verifying ce ment barrier seals
and characterizing downhole events with unparalleled pre cision
•VIVID™
acoustic logging platform detects leaks that were previously
undetectable and provides you with the clearest answers wh ere other
technologies fail If it’s there, we’ll detect it

Practical effect of changing from the prototype FS500
sensor to VIVID™
15
Originally the new sensor was to be promoted as a new se nsor within the Point
offering.
However in recognition of the features, performance and benefits of the new
sensor it was decided to promote the enhanced technology as a new service
using new VIVID tools.
This has meant several changes in terminology however the logging processes
are essentially the same except that what was an FS500 se nsor is now a
VIVID tool and the service is VIVID™
• Previous/current (Q2 2018) tools are described as an FS50 0 sensor
• The new tool description is VIVID, ALP1-0-02, ACOUSTIC LISTENING
PLATFORM
In the curve names ‘FS5’ is replaced with ‘V01’
When the new sensor is in the string the service name is VI VID (but this
depends on the current contract in place)
If running S100 & S300 tools only the service is LeakPoi nt or FlowPoint
Archer the well company – Private & Confidential

Colour mapping – how does it work?
ALP - FS500  16
The colour map is a variable density map of VIVID freque ncy channel number vs amplitude
Channel 1 is low (sonic) frequency, channel 41 is very hig h ultrasonic frequency.
The S100, S300 & VIVID tools are field tested with a URT
The URT generates a narrow band high ultrasonic frequency signal chosen primarily for the
S100 frequency range
In the VIVID data this corresponds to VIVID noise level curve 5 (banded medium to high
ultrasound). The other VIVID noise level curves are out side of URT frequencies.
It corresponds to VIVID channels 60-65% of the way across the 41 channel colour map
The rising amplitude can be seen in the noise level curve 5 as the URT amplitude cycles
This can also be seen in the colour map which changes co lour as the amplitude changes

The VIVID™tool allows investigation of different
frequencies – detected frequency increasing with ∆P
It has been observed that the higher the differenti al pressure (velocity) 
the higher the amplitude but also the higher the fr equency observed. 
High ∆P leak: Scaled x 1.0 (high amplitude, frequencies extend to high ultrasound)
Lower ∆P leak: Scaled x 10 (low amplitude, lower frequencies more evident)
Archer the well company – Private & Confidential
VIVID
VIVID
VIVID
V01_
VIVID
VIVID
VIVID
V01_

VIVID™data - frequency spectrum varying with ∆P.
The peak frequency has changed with increasing ∆P (≈ 25Khz changed to ≈ 40kHz)
The available ∆P to us is dictated by original pressures, c ollapse pressure, burst
pressure, customer policies, available facilities to pressure / bleed etc.
For low ∆P’s it is easier to spot raised energy/frequency in the colour map than in the
curves. The colour map will identify points of interest.
18
Tubing static pressure 620 psi, Annulus bled pressure 200 p si. ∆P 420 psi
Tubing injection pressure 2800 psi, Annulus bled pressure 400 psi. ∆P 2400 psi
Freq. Map
Archer the well company – Private & Confidential
S100
S300
VIVID
Freq. Map
S100
S300
VIVID

Example VIVID™CCE job – frequencies below the S100
sensor
• There are no indications of flow on the high frequen cy S100 data
• The S300 sensor & VIVID tool both detect flow but in different ways
• The VIVID colour map shows that the noise frequencies do not reach high
ultrasound (this explains the lack of S100 response)
• Looking closely there is a slight change in spectrum from below the noise
source (top of the log) to above the noise source (bottom of the log) indicating
fluid movement. This is easier to see in the frequency col our map.
Archer the well company – Private & Confidential
VIVID
VIVID colour map

Confidential
VIVID
TM– casing and completion evaluation
21
Gas movement characterisation (remember the carbonated water slide?)
VIVID detects characteristic ‘fizz’ of gas bubbles moving through liquid
The broadband response captures not only the gas entry point<
<but also the subsequent movement above
Special processing by WIS applying bandwidth equalization re veals the signature of gas
entry into liquid filled tubing
Gas entry 
through leaky 
unloading 
valve
Bubble flow 
up tubing
Equalized view
Gas entry signature
Characteristic signature 
of gas bubbles in a 
column of liquid

Required software for the field
22
Sondex Warrior 8.07 or above. May be run using a Warrior 8.02 key (the ones we have a lready)
Required supporting files:
• New Ultrawire, Ultralink, Services and Tools.ini files f or VIVID ULP
• New dll’s: btcalp32.dll & btcalpext32.dll (used to gen erate VIVID noise level
curves, XP curves and data for the colour map)
• New wproperties.ini containing colour maps for the VIV ID tool
• New log presentation files specific to VIVID services
• Bespoke AET files (ASCII Export Templates) to speed up data handling
• New wtd (Warrior Tool Diagram) files for better looki ng string diagrams
• Updates distributed by config restore or for field tria ls on a memory stick
Sondex Memlog 3.10 Enables turning off the beep (if not turned off the VIVID tool will detect this beep)
• Only applicable to the UMT007 and UMT008 memory recorders
• The UMT2 firmware (SON262-6) must first be installed via Memlog
• UMT003 no upgrade option to turn off beep - avoid usi ng a UMT003 with VIVID
FLOPS 3.9 Has been updated to process VIVID noise level and VIVID XP curves
Archer the well company – Private & Confidential

LNU noise level curves are used to represent bespoke
frequency bandwidths
• Colour map has all 41 channels. The colour map to use is
ArcherBasic
(as illustrated)
• It is not practical to show all 41 channels as noise level without cluttering the log therefore
certain frequency bands have been merged to give 6 bespoke noise level curves
• Curves 1 to 4 cover sonic and ultrasonic frequencies ( may be better for ‘Flow’ type jobs)
• Curves 5 & 6 are high ultrasonic (may be better for ‘L eak’ type jobs)
• Curves 7 and 8 include XTU power supply noise and are not generally used in the field
• Curves should never cross if plotted on the same scale
Band potentially 
influenced by XTU 
PSU noise
_1
_2
_3
_4
_5
_6
_7
_8
X
Archer the well company – Private & Confidential
XTU PSU noise not 
included in 
V01_LNU_5
V01
V01
V01
V01
V01
V01
V01_LNU_V

Naming format for VIVID™tool curves Legacy curve names had sensor ID FS5. This has been replaced with V01
Specific naming format for VIVID XP channels (as exporte d for WIS):
Curves start with ‘XP’. 41 frequency channels from dua l sensors with 3 different processing
methods applied (gives 2 x 3 x 41 = 246 curves per too l)
Example:
XP_V01_004 = Exported, FS500, Channel Number 004 Specific naming format for Noise Level (banded) curves:
V01 VIVID sensor 01
L / H Lower or Higher frequency V01 sub sensor (low range sensor in the field logs)
N Noise Level (Signal processing type ID)
U / F Unfiltered / Filtered (Note: Unfiltered curves should be used in field logs)
1-8 Curve (frequency range) number
#2 Used if a second V01 tool is in the string
Examples:
V01_LNU_1 = VIVID01, Low frequency sensor, Noise Level, Unfiltered, Curve 1
V01_LNU_1#2 = VIVID01, Low frequency sensor, Noise Level, Unfiltered, Curve 1, Tool # 2
Specific naming for colour map: V01_LNU_V = VIVID 01, Low frequency sensor, Unfiltered, VDL
Archer the well company – Private & Confidential

Field Log colour map for VIVID™VDL
• Colour mapping is an excellent way to convey complex data
• The standard VIVID colour map to use is ‘
ArcherBasic

• This has zero noise level as white (other colour maps do n ot)
• Other colour maps are for use by WIS and BTC.
• Contrast can be adjusted by changing the Colour Map ‘White’ Level
• If the map is not in wproperties.inithe track will be blank – request a new file
Archer the well company – Private & Confidential
V01_LNU_V
V01_LNU_V
V01_LNU_V
V01_LNU_V

The VIVID™Noise Level curves will change shape
according to frequency constituents
• The curves change shape with frequency (compare NL curves 1-4 with 5 & 6)
• High frequency curves 5 & 6 are similar to the S100 curve s but sharper
• What curves to focus on will depend on the type of job:
oFirst examine the colour map to locate zones of interest
oFor high velocity ‘Leaks’ start by looking at the higher  frequency curves
oFor low velocity ‘Flows’ start by looking at the lower f requency curves
oIf you are unsure leave it to the experts
Archer the well company – Private & Confidential
VIVID
VIVID
VIVID

XTU002 telemetry crossover - power supply crosstalk
VIVID™
SRO acquisition – XTU002
• XTU crosstalk is approximately 117-129kHz
(Channel #23) and may be apparent on the colour
map
• Engineers should be aware that this is normal, it is
from the XTU, not an anomaly, and not a symptom
of fluid flow
• The ability to filter out the XTU PSU frequency
band (#23) makes SRO data acquisition viable
VIVID™
Memory acquisition - UMT
Logged across the same depth range
The same low frequency response is seen on both
logs (Note: They are slightly different - this data is
from a different well intervention and pressure
conditions may have changed).
XTU crosstalk is not apparent on the colour map
XTU002 
crosstalk
Archer the well company – Private & Confidential

Private and Confidential 29
Field Engineers Guide to 
VIVID™
services Logging Operations

VIVID™ Operations
•The logging program is essentially the same as legacy FlowPoint 
programs using S100 and S300 tools.
• That is dynamic passes and extended station logging passes at different
well pressure states
• Current Archer VIVID™string sensors: 1 x S100, 1 x S300, 1 x VIVID tool
• May also run 2 x S100 and 1 x VIVID tool or 1 x S100 & 1 x VIVID tool
depending on the objectives.
• Depth correlation is by CCL or Gamma Ray (depending on the job)
• Includes a PIA (ACCE curve) as an alternative FLOPS filt ering option
• VIVID tools may be run in SRO mode due to the ability to selectively filter
out ultrasonic crosstalk from the XTU002. After powering up the string wait
for the ULP data to be registered before starting reco rding. If you do not
there will be a problem! Refer to BTC document ULP_Readme.pdf
(24.4.2017)
• VIVID tools have relatively high power consumption - eval uate battery
consumption when planning memory jobs
• Use the UMT battery power spreadsheet 1.8 or later
Archer the well company – Private & Confidential

Point & VIVID tool codes and telemetry
Archer the well company
Old Warrior
tool name Temperature
New
Warrior tool name
Std. telemetry
channel Remarks
LEAK1 150 WLD1 LEAK1-002 LEK1-0-03 S100-1 62
WLD2 S100-1
WLD001 S100-1
WLD002 S100-1
WFP001 S100-1
Run as S100 without rubber sleeve. Check channel
# for conflict. Only use in emergency.
LEAK2 150 WLD1001 LEAK2-002 LEK2-0-03 S100-2 58
WLD1002 S100-2
WLD2001 S100-2
WLD2002 S100-2
WLD001-001 S100-2
WLD001-002 S100-2
WLD002-001 S100-2
WLD002-002 S100-2
WFP00x S100-2 61
Run as S100 without rubber sleeve. Check channel
# for conflict. Only use in emergency.
LEAK 177 LEK1-0-33
FLOW1 150 WAF1 FLOW1-001 FLW1-0-03 S300-1 61
WAF2 S300-1
WAF001 S300-1
WAF002 S300-1
FLOW2 150 WAF1001 FLOW2-001 FLW2-0-03 S300-2 60
WAF1002 S300-2
WAF2001 S300-2
WAF2002 S300-2
WAF001-001 S300-2
WAF001-002 S300-2
WAF002-001 S300-2
WAF002-002 S300-2
FLOW 177 FLW1-0-33
VIVID 177VIVID-DEV 59 1st generation development too1
VIVID-EXP 59 2nd generation development too1
ALP1-0-02 VIVID-002 59 ALP1 - Production tool.
57 ALP2 - 2nd instance of tool
56 ALP3 - 3rd instance of tool
BTC Tool codes
ARCHER ULTRASONIC TOOL INFORMATION

Example VIVID™CCE string (the actual string make up
will depend on the job in hand)
QPC, PGR, PIA & TEMP +
1 x S100 + 1 x S300 + 1 x VIVID tool
or 2 x S100 + 1 x VIVID tool
or 1 x S100 + 1 x VIVID tools
May be run in SRO mode using an
XTU002. The ultrasonic crosstalk from the
XTU can be selectively filtered out.
May be run in memory mode using a UMT.
The high string current should be factored
into the job planning
• The VIVID tool current increases with
well temperature
• Use a 13Ah battery as standard
• A13Ah battery gives about 32 hrs
powered up time
• A6.2Ah battery gives about 16 hrs
powered up time
Archer the well company – Private & Confidential
VIVID
S100 or S300S100

Battery life must be checked for memory jobs • VIVID tools are power hungry
compared to S100 & S300 sensors
• The higher the temperature the
higher the VIVID tool current
• Use the UMT battery life calculation
spreadsheet:
oCalculate the total time for the job
oEnter tools in the string to get total current
oEnter the battery info for the battery type
oEnter the job time and any sleep period
oCheck remaining power
If there is insufficient power look at ways to
complete the job:
• Use sleep mode and only power up when
logging data is needed
• Remove non-vital tools
• Consider a longer spacing between stations
• Split the string into two with separate
memories and batteries
• Split the extended stations into lower and
upper and make an extra run (with overlap)
Archer the well company – Private & Confidential
Rig up time before RIH, hrs
1.0
Top depth
0
Bottom depth
5000
RIH / Logging speed
30
RIH / Log In Hole time, hrs
2.78
Bottom depth
5000
Top depth
0
Speed between stations.
10
Interval between stations.
1
Station time, secs
10
Station time, hrs
22.22
Bottom depth
0
Top depth
0
POOH / LOOH speed
40
POOH / LOOH time, hrs
0.00
Total run time, hrs
26.00
Time for logging stations
POOH / LOOH time
Point job run time calculator, Hrs.
Rig Up time
RIH / LIH time
JOB LENGTH Total Run Time, hrs
26
Time in Sleep Mode, hrs
3
 
Toolstring powered up time, hrs23 RESULTS Power Used by toolstring during logging, mAH
10902
Power Used by toolstring during sleeping, mAH
15
Power Used during motoring, mAH
0
mAh %
Total Power Available11700 100.0%
Total Power Used10917 93.3%
T OTAL LEFT783 6.7%

Characteristic shape of a battery running out of power
(for troubleshooting)
1. Voltage rises running in hole due to elevated tem perature
2. Voltage stays approximately steady until just bef ore power runs out
3. Voltage then drops quickly
4. Current goes up as PSU tries to maintain a steady output voltage
5. Tools start to quit once output voltage drops to about 13.5V
6. UMT007 recording on 5V carries on recording but with no tool data
Archer the well company

Example tandem memory string with VIVID™tools for
long jobs and for not enough available battery power
Reduced current for each
toolstring by splitting up the
sensors
Both strings include a VIVID
tool, a QPC for depth
correlation and a PIA for
FLOPS filtering
Both strings include
temperature.
If one string fails there will
still be sufficient data for an
interpretation.
For correct offsets of the
upper string make a dummy
tool representing the same
length as the lower string
(SRO) or add a depth shift
in output passes the same
length as the lower string
(Memory)
Archer the well company – Private & Confidential
VIVID

Don’t forget to turn off the beep from the UMT
• The UMT beep can be detected by the VIVID tool which may mask useful data
• Use Memlog 3.01 or later together with SON U262-6 UMT007/008 firmware
• Have the beep turned on when connecting the battery so you know the battery
has connected and the UMT is working
• Turn off the beep in the programming by using a setu p command
• Proceed as normal. The beep will remain off even if t he tool goes into sleep
mode.
• When the tools are retrieved from the well they will not be beeping and so you
will not know if the memory is still working until afte r downloading
• Use Memlog visual merge to check the recorded data ASAP
• Note: If the power is interrupted the UMT will powe r up with the beep enabled
– ensure battery connections are good.
Archer the well company – Private & Confidential

Testing the S100, S300 & VIVID™tools
S100 & S300 sensors: 
Perform the URT test as usual. The URT test shows if the
tools are working but it is not a good indicator of senso r sensitivity.
VIVID™
tools:
• Rub the sensor face lightly with a nylon pad to gener ate a broadband response
• The URT designed for testing S100 & S300 tools generates high frequency
ultrasound in a narrow bandwidth and thus will not te st the lower frequency
sensing of the VIVID tools.
• However the URT will show us the tool is working and al low examination of the
colour map for errors such as stripes.
• Clamp the URT on the VIVID tool and follow the S100&S300 testing procedure.
• Record the test for inclusion in the API log (proof th at a pre-job check was made)
Archer the well company – Private & Confidential
VIVID
VIVID
V01_

Pre-job and Post Job checking - SRO
Pre-Job • Open the Monitor, Devices, ULD (USBULD), Channels. Check that the samples/sec 
is not zero. There should be a changing hexadecimal number associated with the 
ALP (FS500)
• Open the Monitor, Devices, ULD (USBULD), Tools. It is OK to have a few tool errors
• Open the Monitor, Devices, ULD (USBULD), Telemetry. There should be no Tool 
Errors associated with the ALP (VIVID tools)
• Wait for VIVID tool ‘registration’ then record the p re-job check for the Point sensors.
During logging • Check the sensors are working properly by observing the VI VID curves and VDL. 
There should be no zero values, ‘flat lining’ or stripes
• Baselines should be stable with little sensor noise: +/- 3 0 cps is OK (excluding LNU 
curve 1 which may have more scatter) 
• Check that the sensors are not moving during logging stat ions by observing the 
baseline noise, CCL and ACCE data. If you think the to ols are moving wait longer
• Observe the curve responses and VDL for signs of raised noise  indicating leaks or 
flows.
• Follow the logging program as to whether to check and  verify suspicious leaks 
immediately or later
Archer the well company – Private & Confidential

Pre-job and Post Job checking - Memory Pre-Job • Open the Monitor, Devices, UWD (Ultrawire Memory), Channels. Check that
the samples/sec is not zero. There should be a changing hex adecimal
number associated with the VIVID ALP
• Open the Monitor, Devices, UWD (Ultrawire Memory), Tools. It is permissible
to have a few tool errors
• Open the Monitor, Devices, UWD (Ultrawire Memory), Telemetry. There
should be no Tool Errors associated with the VIVID ALP
• Check the tools are working properly by running the str ing in monitor mode,
opening the Warrior sensors and outputs windows and start logging in time
drive.
Post job • After the job the UMT will not be beeping (the bee p was turned off) so you do
not know if the tool is still working! Download the too ls and check recorded
data before fully rigging down.
• Check that the tools are not moving during logging stat ions by observing the
baseline noise, CCL and PIA data. If there are signs of movement during the
stations ask operations support for advice. A re-run may be required.
• Record the post-job check by logging in time drive.
Archer the well company – Private & Confidential

Standardised log presentations have been developed.
Use them – it is for standardisation and will save time .
43
• Example log presentation ‘Archer FlowPoint_S100_S300_V01_dynamic.prs’
for 1 x S100 + 1 x S300 + 1 x VIVID tool
• Plots S100 data, S300 data, V01_LNU_1to4, V01_LNU_5&6 + Colour map
• LNU_5&6 separated to relate to S100 responses (high ultrasound)
• Select dynamic (uses DEPTH) or stations (uses ADEPTH)
• Select other log presentations to match different strin gs
• As with all logs sensor scales should be interactively chosen to best present
the data
• The colour map should be observed. Adjust contrast if nee ds.
Archer the well company – Private & Confidential

Field log colour map contrast is adjustable
45
• With low signals (highly attenuated / little acoustic e nergy to start with) the
colour map contrast may need adjusting so that the change in frequency
spectrum is easier to see.
• This is done by adjusting the presentation VDL White L evel downwards
Archer the well company – Private & Confidential

LQC SRO – showing tool movement during stations
(colour map is available for memory after re-calculation)
• Tool movement evident for the first 3-4 seconds of some st ations.
• Line speed is zero and ACCE was very stable but the colour map clearly
shows tool movement
• When logging SRO observe the colour map and if necessary extend the
station duration
• When logging memory make a note that longer stations will be needed next
time. If there is too many instances of movement the run may need repeating.
‘Normal’ station
Station 
where the 
tools ‘crept’
Archer the well company – Private & Confidential

LQC Memory – Example extreme tool movement during
logging stations
• In this example the toolstring never stopped moving and the data was unusable
• Memlog – check the S100 and S300 sensors. After re-calculation the VIVID colour map
is the best indicator of tool movement as it shows road noise.
• You will not know the tools were moving until after the t ools are downloaded.
oCheck the data as soon as the tools are recovered f rom the well. 
oIf the tools did not stop moving during the station  the data is likely to be unusable – contact 
operations support ASAP for advice. 
• For deep jobs / CTU ops consider extending the logging station time when planning
Archer the well company – Private & Confidential

• Applicable to all memory jobs.
• If depth and tool data are not merged correctly it w ill invalidate the interpretation
• To make it easier to check alignment perform 1 or 2 lon ger duration stations
periodically during the job
• Then during merging check depth and data are correctly aligned by viewing the
stations of unequal duration
• This is also a good time to check Point tool baseline stab ility and for tool
movement during stations
LQC Memory - Check for correct alignment when
merging logging stations
Archer the well company – Private & Confidential

LQC Memory - Check for the effects of varying line
stretch / memory and depth clocks running differently
Tie in’s set at the bottom – merge OKTie in’s out of alignment at the top – not OK
SRO work: • Check for tool movement during stations. If there is a ny movement wait longer. Memory: Offset caused by changing line stretch or memory and de pth system clocks at different speeds
1. Set the tie ins at the bottom to get an initial alignment
2. Re-set the tie ins half way through the logging pass
3. Check at the bottom and top of the pass that ther e is still an overlap of zero line speed and
baseline Point / VIVID data of at least 8-10 seconds
4. If there is not, the pass may have to be split into lo wer and upper with new tie ins each
time. The two logs may be spliced after converting to de pth domain and depth correlating
Archer the well company – Private & Confidential

LQC - Some sensors perform better than others
(applicable to all jobs)
• The pre and post-job URT checks show that the tool is working but they are not a good indicator 
or sensitivity or stability.
• Examine the downhole data
• Sensor channels (excepting VIVID channel A ) should show a stationary count rate fluctuation of 
+/- 30 cps
• In this example of memory data sensor S300-2 (red) is noisier than sensor S300-1 (blue).
• A noisy sensor may be more evident if FLOPS is used to retain stationary data
• If one tool shows excessive baseline noise record in the logbook and inform WIS. 
Red tag 
the 
suspect tool for a full lab check.
Archer the well company – Private & Confidential

Managing relatively large VIVID™file sizes
• Because of the large number of channels (246+ per tool plus other sensors
in the string) VIVID tool data sets will be quite larg e.
• This may present problems transmitting data in remote areas and also adds
to the processing time when importing data for a quick l ook.
• Option 1: Memory operations –back up the original DB before re-
calculation. Re-calculation increases the file size by about 3.5 time s. If
communication is limited WIS may then recalculate the or iginal DB
• Option 2: Use VIVID QUICK LOOK AET files to minimise the exported LAS
file to the first 41 channels and send the full set of cu rves later
• If there has been a lot of re-calculation export the final passes to a new
Warrior database and back up the new database on the server
• Zip the output files to further reduce file size
• The default depth step from FLOPS is at 0.001m or ft. Before importing into
Warrior edit the LAS file header to have STEP size of 0.02m or 0.05ft. This
will reduce the time taken to read the LAS data in an d reduce the eventual
database size.
Archer the well company – Private & Confidential

Also CCL should also be exported from extended
logging stations at 0.1s intervals for depth correla tion
1. Export the CCL data at 0.1s intervals
2. Use the utility in FLOPS to convert CCL data into the d epth domain (data when the
depth is changing / tools are moving is retained)
3. The output LAS file is imported into Warrior and a proc essed CCL log is made (curve
xCCL) for depth correlation against the dynamic pass (w hich is already on depth).
4. The amount of depth shift required is recorded and t hen manually applied to the
FLOPS filtered tool data from the pass.
5. This method works OK for major completion items but not always for collars
Archer the well company – Private & Confidential

Private and Confidential 54
Field Engineers Guide to 
VIVID™
services API Field Log

VIVID™Field log contents stay the same
55
• The same field log contents as for existing Point surveys
• Archer log standardisation MUST be enforced including ‘ New’ branding
• New logging program and report branding for the VIVID™services
• New banner for log inserts (no blue ‘Point’ branding if VIVID tools used)
• Archer Document ‘API Field Log Format Guidelines’ has been updated and
should be used as a reference.
Archer the well company – Private & Confidential

Field logs should always be made for QC checking
• Whether the client requires a log or not an API fi eld log 
should always be made.
• Dynamic log depth correlation is by using the fiel d log
• It is the best way check raw data quality
• The original database and raw data may get lost
• If there is a problem or hard to understand result s it allows 
going right back to the original data
• Using template presentation files will speed up th e process
• As for any logging job scales should be chosen to  match the 
data. Important for stations with small changes to  baseline –
road noise between stations is irrelevant
• Extended station depth correlation is possible aft er 
converting to the depth domain using FLOPS.
56 Archer the well company – Private & Confidential

Suggested Log constituents (same as for FlowPoint)
ItemComment
1 Log HeaderArcherheading.hdg
2 Toolstring Diagram From logging pass or Excel string diagram
3 Archer Point or VIVID branding graphic Only for Point / VIVID services.
4 Well schematic If a well schematic is available in digital form
5 Log insert – Well condition 1 First well condition of VIVID logging job
6 Separate logs of dynamic data and extended 
station data for the well condition
•Alternatively a merged log of dynamic 
and FLOPS filtered stations for the well 
condition may be presented
Must contain a top log banner showing well pressure 
condition and log scale. 
e.g. Baseline. All annuli shut in. 1:500
7 Log insert – Well condition 2 Second well condition of VIVID logging job
8 Separate logs of dynamic data and extended 
station data for the well condition
•Alternatively a merged log of dynamic 
and FLOPS filtered stations for the well 
condition may be presented
Must contain a top log banner showing well pressure 
condition and log scale. 
e.g. B Annulus venting. All other annuli shut in. 1:500
9 Additional logs for further well conditions Repeat of items 5 to 8.
10 Sensor pre job checks Time drive logs of pre job checks for all Point / VIVID 
sensors in the string
11 Calibration report Print out of recorded calibrations.
12 Archer Point or VIVID branding graphic Only for Point / VIVID services
13 Log FooterArcherfooter.hdg
• The log constituents are essentially the same as for a FlowPoint job with S100 & S300
sensors but with the added VIVID colour map in the logs
• FLOPS filtering is not mandatory but is quite useful for im proving the log
• On-depth FLOPS processed lower and upper passes (if you had to split up the pass)
may be spliced into a single pass before including in the fie ld log
Archer the well company – Private & Confidential

Suggested template log presentation files
For 1 x S100, 1 x S300 and 1 x V01 sensors:
Archer flowpoint_S100_S300_V01_dynamic.prs
For dynamic passes
Archer flowpoint_S100_S300_V01_stations.prs
For logging station passes
For 1 x S100, 1 x S100 and 1 x V01 sensors:
Archer flowpoint_S100_S100_V01_dynamic.prs
For dynamic passes
Archer flowpoint_S100_S100_V01_stations.prs
For logging station passes
• These presentations have the Archer standard curve colours a nd interrupts
• Archer FlowPoint presentations separate high frequency LNU curves 5 & 6 to
compare with S100 curves
• If the presentations are customised to match the job in hand return to the defaults
for the next job
• FLOPS processed passes do not contain VIVID colour maps and so are not
mandatory. However FLOPS is very useful for finding smal l leaks at the wellsite
which may otherwise be missed.
• The presentation files are part of the installed Warr ior configuration or may be
downloaded from the training SharePoint site
Archer the well company – Private & Confidential

VIVID™/ Point data preparation
63
Data acquisition
Dynamic
Export to WIS
• Quick look for rapid report
• Full set for standard report
Extended Stations
Process with FLOPS
(optional)
Depth correlate
Depth correlate
(if FLOPS was used)
Produce Field Log
Without using FLOPS it
is not possible to
accurately depth correct
extended logging station
data.
Archer the well company – Private & Confidential

Private and Confidential 71
Field Engineers Guide to the  VIVID™
tool
Maintenance

Do not accidentally damage the tool
Archer the well company
• It is possible to accidentally put a spanner across the senso rs
• This will damage them
• Take care when rigging up / rigging down – keep an eye on operations
• Recommended torque for connections is 40-60Nm

VIVID™
Tool maintenance
• Changing the housing ‘O’ rings is a field operation
• Because of the sensor isolation changing the VIVID™sensor ‘O’ rings
is complex and should only be performed at a qualified Archer
maintenance centre. It is not a field operation.
• If the ‘O’ rings is seen extruding from either sensor r eturn for
servicing immediately
• Management should schedule for periodic servicing and checking. A
service schedule is in the VIVID field guide.
Tool Routine Maintenance
Roller Centralisers Change rollers as required. Inject grease through grease ports. Change ‘O’ rings. Check 
continuity and insulation. Check spring tension is sufficient to fully centralise  the logging string. 
Check the arms go in and out smoothly
Knuckle Joints Inject grease through grease ports. Check continuity and insulation.
QPC Change ‘O’ rings. Refill with silicon oil as required.
PIA & PRT Change ‘O’ rings. Check the calibrations.
Point sensors
Changing the VIVID™sensor ‘O’ rings is not a field operation.
Clean the tools thoroughly after a job (do not use a pressure hose). Inspect and change housing 
‘O’ rings as required. Change sensor seal for S100 & S300 tools only. 
Test the tools before the job using the correct method for the sensor.
Gamma Ray and CCL Change housing ‘O’ rings as required. Check for loose screws. Do not store the CCL next to the 
gamma ray. 
Archer the well company – Private & Confidential

Private and Confidential 74
Field Engineers Guide to 
VIVID™
FLOPS processing

FLOPS overview
Archer the well company
• Converts from time domain to the depth domain
• Removing road noise makes it easier to spot statio ns with raised
ultrasound which may otherwise be missed
• Useful for LQC – checks different tool responses at the same depth
• Resulting logs are easier for the customer to unde rstand:
oThe top of the log is the shallowest depth
oExplains our methodology (why we have extended stations in the
program i.e. for retention of baseline noise with no road noise)
oNo confusing spikes on the log due to to road noise betwe en stations
• Allows easy splicing by depth of multiple extended station passes
• If you had to run tandem strings due to limited ba ttery power it gives
a way to get the data from both strings on depth (a fter using FLOPS
the data is in the depth domain) before splicing.
• Allows merging with other depth domain data (dynamic pass data for
the same well condition, RBT cement bond log data, etc9)
Before using read the ‘FLOPS Data processing software User Manual’

FLOPS has been upgraded for
VIVID™
data
76
• FLOPS processing retains extended station stationary dat a and converts data
to the depth domain (with the log the right way up! )
• FLOPS filtering should be used in the field for QC p urposes – do similar tools
respond in the same way at the same depth?
• FLOPS filtered data should be included in the field logs
• There is no option for colour mapping of imported FL OPS processed data
Archer the well company

FLOPS disclaimer for the log header
Archer the well company
Because using FLOPS makes the data easier to understand (which is a
good thing) the customer may believe they can inter pret the data.
In some cases maybe they can but it should not be e ncouraged. Archer
interpretations are a bespoke, complex, quality con trolled product.
For this reason add this disclaimer to the log head er:
‘The averages of Point / VIVID tool stationary 
data presented in this log are for QC purposes only. 
Archer strongly advises against any inferences made 
from this data. An interpretation of the data conta ined 
in this log will be provided separately’.

FLOPS flowchart
Archer the well company

FLOPS processing – before starting
Examine the raw data
1. Check correct alignment of depth and
tool data
2. Note the allowable variation in LSPD
during a station (in this example the
stationary LSPD varied due to
vibration)
3. Note the allowable variation in ACCE
during a station (from the API log). It
may be a small value.
Record the sensor offsets
a) From the string diagram
b) View Edit / Sensors during re-
calculation
Archer the well company

FLOPS main screen
Archer the well company
• Press Plot data to see the data after loading
• Press the zoom icon (top left) and drag a box to zoo m. Double click to plot all data.
• Use ‘Change Displayed Curves’ to choose most useful curves
• Default V01 curves are XP_V01_010 and V01_LNU_3 (lower frequency curves include
sonic level and may be too noisy)

Using
Time Shift LSPD
to best align line speed and tool
data
Archer the well company
Before After
• Zoom in at the middle of the logging pass and check the alignment
• The line speed was out of synchronisation by 1 second
• After applying a -1 second shift the fit is better
• Check for the optimal fit at the bottom, middle and top of the data
• Due to differing line stretch it may not be perfect e verywhere.
• Aim to have a minimum 8 seconds overlap of zero line speed and baseline
signal
• Memory data - if there is insufficient overlap it may b e necessary to go back
to Memlog and split up the extended station pass into l ower and upper.

Filtering on
LSPD
Archer the well company
Enter a line speed value below which to retain data
• If the wireline unit has vibration or there is noise i t
may be higher than the default 0.1
• Click on apply to generate a filter vector
Filter vector after applying the Line Speed filter: • Most likely the vector will need further adjustment. In this case the filter
vector will save a little false data with the tools still moving
• Examine all the data - check the filter vector at the bo ttom, middle and top
of the data
• Filtering on ACCE may give a better result – try both filtering methods.

Filtering on
ACCE
Archer the well company
Enter an acceleration value below which to retain data
• Examine the API log first – this may be a small value
• Enter the minimum length below threshold before
retained data is assumed to be a logging station
Filter vector after applying the ACCE filter: • Examine the point tool data. In this case the filter vector may save a little
false data with the tools still moving
• Most likely it will need further adjustment.
• Filtering on LSPD may give a better result – try both filtering methods.

Expand the filter using
Change Filter Intervals
Archer the well company
Enter a time value to extend the data that will be r ejected
• This is to allow for the tools still moving a little af ter
stopping at a station (‘tool creep’)
• Examine the tool data and judge the amount to add
• Values are in seconds and are cumulative
• Do not use too large a value - try to retain as much use ful
data as possible for averaging later on
• Adjust to get the optimal result then check at the bott om,
middle and top of the logging pass
Filter vector after expand filter left and right has b een applied

Apply the current filter
(LSPD or ACCE)
• Click on ‘Apply Current Filter’ in the main menu
• Keeps the stationary data and rejects the non stat ionary data
• There may be some ‘outliers’ which can be filtered out later
Screen after applying the current filter • Tool movement has been rejected and baselines retained
• Data is still in the time domain
Archer the well company

Apply ‘
Recalculate depth

Archer the well company
• Attaches a depth from ADEPTH to each retained point
• To prevent overlap a small depth increment (step) is
applied to each retained point
• If there are no stations greater than 90 seconds long in
the pass use Depth step 0.01 (to make the file sizes
smaller). If not use a 0.001 depth step
• Depth spread for recalc is to merge stations which are
very close together.
Screen after recalculating depth • Data is now in the depth domain
• Tool offsets have not been applied

Apply ‘
Calculate average

Archer the well company
• Read the FLOPS manual for a description of how the
average filters work. They are to reject outliers.
• Use as low a filter as possible to retain peak height
• Start on the standard filter and view the results. If too
noisy apply a higher filter
• Adjust to get the optimal result and check the results at
the bottom, middle and top of the pass
Screen after applying the average function with filter ing • Outliers have been filtered out
• The average values are presented as an output curves ‘avSxxx’
• Tool offsets have not been applied

Double checking the FLOPS filter intervals
• If raised sound is apparent but it is suspect check at the same depth in the field log to
see if the filter interval needs optimising before sending t he FLOPPED file to WIS
• In this example 95% of the well was fine but there was a pparent noise over a short
interval at 1340m which was hard to explain
• This turned out to be tool movement for 3-4s during t he first part of a station. Line
speed was zero and ACCE was very stable so the data was retained by FLOPS but
the colour map shows toolstring movement as higher freq uency noise
• Adding 4s to the start of the station in ‘Change Filter Interval’ reduced the number of
false readings (but reduced the number of retained rea dings to average)
Archer the well company
‘Normal’ station

Apply ‘
Export to LAS

Archer the well company
1. Check the depth units are correct
2. Enter the sensor offsets from the zero point
(from the string diagram) for each sensor in
the same depth units. If the depth zero point is
the string bottom they will be negative
3. Adding an ‘st’ as a prefix will rename some of
the output curves. The resulting curves in the
both the dynamic and FLOPS filtered passes
will have unique names. This is to prevent a
merge error when merging dynamic and
FLOPS filtered data in Warrior
4. For WIS use in Emeraude do not add the ‘st’
prefix
5. After writing the LAS file a success message
will be displayed

Processing CCL files for depth correction of FLOPS
processed passes
Archer the well company
1. Use AET FLOPS_CCL_0.1 SEC.AET to output
the CCL data in 0.1 second intervals for each
extended station logging pass
2. In the main screen click on ‘Process CCL’ and
load the exported CCL data
3. At the prompt enter the CCL offset from zero
4. Add prefix ‘x’ to the CCL curve (xCCL) to denote
this is a processed curve
5. Save the processed CCL data with a suitable
name (xxxx_CCL_FL)
6. The CCL data is now in the depth domain
7. Import the FLOPS processed CCL file
8. Use the xCCLcurve to determine a depth shift
value for depth correction of the original
extended station pass it was extracted from

Determine the required depth shift for FLOPS
processed passes using xCCL
1. Depth correct the dynamic pass in the usual manner
2. Read the FLOPS processed xCCL file into Warrior and make a log
3. Correlate xCCL against the on-depth dynamic pass and make a note of the
required depth shift for the extended logging station passes (in this example
+2.2m)
4. After reading into Warrior manually apply the same depth shift to the FLOPS
processed Point data using interactive plot (with ‘shift e ncoder depth’ enabled)
Archer the well company

Reducing exported FLOPS LAS data importation time
1. FLOPS data is written at either 0.01 or 0.001 dep th steps to
prevent an overlap of false depth
2. To reduce the time taken to load the data without reducing data
quality the LAS file header ‘STEP’ may be directly edited using MS
Notepad.
3. The resulting Warrior database file size will be smaller
Archer the well company
• For Point / VIVID data edit the STEP in the header for 0.05m or 0.2ft
• For xCCL data edit the STEP in the header for 0.02m or 0.1ft

Importing FLOPS processed data into Warrior
Archer the well company
• Using ‘FLOPS’.wif (Warrior Import Filter)
will filter curves GR and TEMP on importing
to Warrior
• GR is filtered as standard during acquisition
• This will improve the appearance of the
data by reducing the ‘steppiness’.
• If you don’t use a WIF file it’s OK
Viewing the imported data is easier if pre-prepared . prs presentation files are
used:
oArcher FlowPoint_FLOPS.prsFor 1 x S100 and 2 x S300 
tools 
oArcher VIVID_V01_FLOPS.prsFor 1 x S100 and 2 x V01 
tools (LNU curves)
oArcher VIVID_S100_S300_V01_FLOPS.prs   For 1 x S100, 1 x S300 and 
1 x V01 (LNU curves)
oArcher VIVID_S100_S300_V01_XP_FLOPSFor 1 x S100, 1 x S300 and
1 x V01 (XP curves)
The scales for the imported data will need adjusting to match the job

Example FLOPS processed log of legacy tools –
FlowPoint_FLOPS.prs
Archer the well company
• FLOPS processed stGR, stTEMP and avS300 curves are displayed
• The log has been shifted to be on depth using FLOPS processed xCCL
• The depth accuracy of the log may be checked using curve stGR
• Check of log quality: Both S300 tools show the same resp onse at the
same depth
• The raised amplitude corresponds to the B annulus casing shoe

FLOPS supports
VIVID™
curves. Field log of FLOPS
processed data – VIVID_V01_FLOPS.prs
96
FLOPS processed logs of extended logging stations consisting of:
• Data in depth domain (not time domain)
• Sensor offsets applied for all processed sensors
• Used for QC purposes – compare different tool responses at the same depth
• Averaged gamma ray and temperature
• Averaged noise level curves for all Point / VIVID™sensors in the string
• Logs are primarily depth correlated by reference to F LOPS processed CCL
but GR may be used if there is a definitive match
• Scales to be interactively chosen as for any other field log
Archer the well company

Splicing FLOPS processed data
• For various reasons the extended station pass may 
have been split up into lower and upper.
• By splicing the logs one continuous log may be made
1. Process the lower and upper passes in FLOPS (FLOPS 
3.7 supports XP curves as well as Noise Level curves)
2. Import the lower and upper passes exported from 
FLOPS (now in the depth domain) into Warrior
3. Put the FLOPS logs exactlyon depth before splicing
4. Use Warrior merge to create a spliced pass. Splice in 
the middle of a joint where there is no raised sound 
5. Mark the splice point on the log with an annotation
6. If required export the final spliced log as LAS
Archer the well company

Merging dynamic and FLOPS processed extended
station data
• During a FlowPoint /
VIVID™
survey there is usually a dynamic pass
followed by an extended station pass for each pressure con dition.
• Dynamic data is the best for TEMP, CCL, GR, QP, DQP and other data
• Extended station FLOPS filtered baseline data is the best for acoustic data
• Merging dynamic and FLOPS processed extended station data will give one
log with the most representative data from the dynamic and stationary data
• It will also make a shorter complete API log
Archer the well company
1. Using ‘st’ as a prefix during FLOPS
processing makes the curves in both the
dynamic and processed passes have
unique names so there will be no conflict
2. Ensure both passes are on depth
3. Use Automerge Utility. Select: Both
passes, ‘No subscript’ and all the curves
4. Select a suitable log presentation to attach
5. Merge with a new pass name

Example of merged dynamic and FLOPS filtered
extended station data
Archer the well company
• GR, TEMP, CCL, QP, LSPD and LTEN are from the dynamic pass
• Average S300 curves are from the FLOPS filtered extended stations
• This gives a complete picture of the well response at thi s pressure state
• Optionally add the completion schematic as a well sketch f or clarity

100
Thank you
Questions?
Supporting documents:
VIVID field engineers guide.doc
Introduction to Archer acoustic logging.ppt
www.archerwell.com
Archer the well company