MWD Log Quality & Standards

(1)

Baker Hughes INTEQ

MWD Log Quality and

Data Management Standards

Reference Manual

750-500-041 Rev. A January 1996

Baker Hughes INTEQ

Technical Publications Group 2001 Rankin Road

Houston, TX 77032 USA

(2)

This manual is provided without any warranty of any kind, either expressed or implied. The information in this document is believed to be accurate; however, Baker Hughes INTEQ will not be liable for any damages, whether direct or indirect, which results from the use of any information contained herein.

(3)

Data Management

Labeling Floppy Disks . . . 1-1 Data Back Up . . . 1-1 MWD Services. . . 1-2 M-SERIES Systems . . . 1-2 P-SERIES Systems . . . 1-2 RWD Services . . . 1-3 M-SERIES Systems . . . 1-3 M-SERIES Disks . . . 1-3 Raw Memory Dump Disks . . . 1-3 GetXfer Disks . . . 1-3 Getdata Disks. . . 1-4 P-SERIES Systems . . . 1-5

Additional Data Management . . . 1-5

Squeeze. . . 1-5 Quicken . . . 1-5 WTOB.EXE . . . 1-6 IMP2MPLT.EXE . . . 1-6 HTFX.EXE . . . 1-6 MEDIT . . . 1-6 Future Additions . . . 1-6 Chapter 2

Log Preparation

Original Holes and Sidetracks . . . 2-2 Traces/Scales . . . 2-2

Trace Coding . . . 2-2 Pen-up Intervals. . . 2-3

Recommendations for Scales . . . 2-3

Rate of Penetration . . . 2-3 Gamma Ray . . . 2-4

(4)

Table of Contents Log Quality and Data Management Standards Resistivity . . . 2-5 Conductivity . . . 2-6 Neutron Porosity . . . 2-6 Bulk Density . . . 2-6 Density Porosity. . . 2-7 Photoelectric Cross Section. . . 2-7 Delta Rho Correction. . . 2-7 Time Since Drilled . . . 2-7 Data Density . . . 2-8 True Vertical Depth . . . 2-8

Log Annotations . . . 2-9

See Remark . . . 2-9 Trace Labels . . . 2-9 Back Up Trace Labels . . . 2-10 Casing Markers . . . 2-10 Run Markers . . . 2-10 TD Markers . . . 2-11 Sliding Indicator . . . 2-11 Comment Files . . . 2-11 Remarks . . . 2-11 Annotations . . . 2-11 See Remark 1 . . . 2-12 Exclamation Mark . . . 2-12 Scale Changes . . . 2-12 Trace Labels . . . 2-12 Traces On/Off . . . 2-13

Guide to Comment.fil (Bryan Dugas) . . . 2-13

Comment.fil . . . 2-13 See Remarks X . . . 2-14 Comment Line . . . 2-14 Trace Labels . . . 2-14 Traces On and Off . . . 2-15 Scale Change . . . 2-15 Annotations Across . . . 2-15 Annotation Down From Depth . . . 2-16 Annotation Down To Depth . . . 2-16 Line Annotation . . . 2-16 Horizontal Lines . . . 2-17 Casing Markers . . . 2-17

(5)

Log Quality and Data Management Standards Table of Contents

Gulton Plotter Calibration . . . 2-18

Manual Calibration . . . 2-18 Software Calibration . . . 2-18 Chapter 3

Headers

Miniheader . . . 3-1 Full Header . . . 3-2

Main Header Page, Top Half . . . 3-2

Service Type . . . 3-2 Customer Information . . . 3-2 Well Numbers. . . 3-2 Field . . . 3-3 County . . . 3-3 Country . . . 3-3 Well Location . . . 3-3 North America . . . 3-3 International . . . 3-3 Sect./Twp./Range . . . 3-4 API Number . . . 3-4 Other Services . . . 3-4 Drilling Information . . . 3-4 Elevation Information . . . 3-5

Main Header Page, Bottom Half . . . 3-5

Borehole Record . . . 3-5 Casing Record . . . 3-5 Drilling Contractor/Rig . . . 3-6 Log Type/Scale. . . 3-6 Print Type . . . 3-6 Company Representative/Teleco Representative. . . 3-6 Job Number . . . 3-6

Main Header, Bit Run Summary . . . 3-6

Surface Gear . . . 3-6 Eastman Teleco OD/Type . . . 3-7 Run Data . . . 3-7 Mud Data . . . 3-7 Water Loss . . . 3-7 Rm @ Temp . . . 3-7 Company Representative/Eastman Teleco Field Engineer . . . 3-7

(6)

Table of Contents Log Quality and Data Management Standards Main Header, Equipment . . . 3-8

Equipment Serial Numbers . . . 3-8 Sensor Offsets to Bit/Memory Acquisition Rates . . . 3-8 Other Tool Information . . . 3-8

Main Header, Environmental Parameters . . . 3-8 Main Header, Calibration Verification . . . 3-9

DPR . . . 3-9 Gamma Ray . . . 3-9 Neutron Porosity . . . 3-9 Density . . . 3-10

Main Header, Remarks . . . 3-10

Mnemonics . . . 3-10 Remarks . . . 3-10

Chapter 4

Directional/Natural Gamma Ray

Introduction. . . 4-1 Mud Types . . . 4-1 Borehole Correction Inputs - Gamma Ray . . . 4-1 Data Editing. . . 4-2

Editing of Realtime Data . . . 4-2 Depth Shifts . . . 4-2

Data Management. . . 4-2

M-SERIES . . . 4-2 P-SERIES . . . 4-2 HPUTIL . . . 4-2

Rigsite Data Processing . . . 4-3

Smoothing and/or Averaging. . . 4-3

M-SERIES . . . 4-3 P-SERIES . . . 4-3 HPUTIL . . . 4-3 Filtering . . . 4-3 Other . . . 4-3 Borehole Corrections. . . 4-3 Squeeze. . . 4-3 Quicken . . . 4-4 ADDTSD . . . 4-4

(7)

Postwell Data Processing . . . 4-4

Before Final Logs . . . 4-4 After Final Logs - LIS ASCII File and Tape . . . 4-4

Rigsite Calibration Verification . . . 4-4 Quality Control . . . 4-5

Quality Control Curves . . . 4-5

Data Density . . . 4-5 Time Since Drilled . . . 4-5

Log Quality Control. . . 4-5

Typical Log Response . . . 4-5 Other Requirements for This Service . . . 4-5 Log Presentation . . . 4-6

North and South America Log Presentations . . . 4-6 International Log Presentations . . . 4-7 Chapter 5

Drilling Dynamics

Introduction. . . 5-1 Mud Types . . . 5-1 Borehole Correction Inputs . . . 5-2

Gamma Ray . . . 5-2 Drilling Dynamics . . . 5-2

Data Editing. . . 5-2

(8)

Table of Contents Log Quality and Data Management Standards Other . . . 5-4 Borehole Corrections. . . 5-4 Squeeze. . . 5-4 Quicken . . . 5-4 ADDTSD . . . 5-4 ADDTVD . . . 5-5 EWD. . . 5-5

Before Final Logs - EWD . . . 5-5 After Final Logs - LIS ASCII File and Tape . . . 5-5

Rigsite Calibration Verification . . . 5-5 Log Quality Control . . . 5-5 Typical Log Responses . . . 5-6

Gamma Ray . . . 5-6 Drilling Dynamics . . . 5-6

Other Requirements for This Service . . . 5-6 Log Presentation . . . 5-7

North and South America Log Presentations . . . 5-7

Plotting Recommendations . . . 5-8 Scales . . . 5-8 Traces. . . 5-8

International Log Presentations . . . 5-9

Plotting Recommendations . . . 5-10 Scales . . . 5-10 Traces. . . 5-10

Annotations . . . 5-10

Chapter 6

Short Normal Resistivity

Gamma Ray . . . 6-2 Short Normal Resistivity . . . 6-2

(9)

M-SERIES . . . 6-3 P-SERIES . . . 6-3 HPUTIL . . . 6-3 Filtering . . . 6-3 Other . . . 6-4 Borehole Corrections. . . 6-4 Squeeze. . . 6-4 Quicken . . . 6-4 ADDTSD . . . 6-4 ADDTVD . . . 6-4

Before Final Logs . . . 6-5 After Final Logs - LIS ASCII File and Tape . . . 6-5

Typical Log Response . . . 6-5

Gamma Ray . . . 6-5 Short Normal Resistivity . . . 6-6 Permeable Zones (No Hydrocarbons) . . . 6-6 Impermeable Zones . . . 6-6

North and South America Log Presentations . . . 6-7 International Log Presentations . . . 6-8

(10)

Table of Contents Log Quality and Data Management Standards Chapter 7

Dual Propagation Resistivity

Gamma Ray . . . 7-2 Dual Propagation Resistivity. . . 7-2

Editing of Realtime Data . . . 7-2 Editing of Memory Data . . . 7-2 Depth Shifts . . . 7-3 Data Management. . . 7-3 M-SERIES . . . 7-3 MDMS . . . 7-3 P-SERIES . . . 7-3 HPUTIL . . . 7-4

M-SERIES . . . 7-4 MDMS . . . 7-4 P-SERIES . . . 7-4 HPUTIL . . . 7-5 Filtering . . . 7-5 Other . . . 7-5 Borehole Corrections. . . 7-5 Dielectric Corrections . . . 7-5 Squeeze. . . 7-5 Quicken . . . 7-5 ADDTSD . . . 7-5 ADDTVD . . . 7-6

Before Final Logs . . . 7-6

Dielectric Corrections . . . 7-6 Inversion . . . 7-6

After Final Logs . . . 7-6

Postwell WDS Log Analysis. . . 7-6 LIS ASCII File and Tape . . . 7-6

(11)

Gamma Ray . . . 7-9 Dual Propagation Resistivity. . . 7-9 Permeable Zones . . . 7-9 Impermeable Zones (Shales) . . . 7-9 Dielectric Formations . . . 7-9 Thin Beds Intersecting Borehole at High Incident Angles

(Above 80°) . . . 7-10 Eccentricity . . . 7-10

North and South America Log Presentations . . . 7-11 International Log Presentations . . . 7-13 Chapter 8

Double Combo

Gamma Ray . . . 8-2 Dual Propagation Resistivity. . . 8-2 Modular Neutron Porosity. . . 8-2

(12)

Table of Contents Log Quality and Data Management Standards

M-SERIES . . . 8-4 MDMS . . . 8-5 P-SERIES . . . 8-5 HPUTIL . . . 8-5 Filtering . . . 8-5 Other . . . 8-5 Borehole Corrections. . . 8-5 Dielectric Corrections . . . 8-5 Squeeze. . . 8-5 Quicken . . . 8-6 ADDTSD . . . 8-6 ADDTVD . . . 8-6 WDS Quicklook Log Analysis . . . 8-6

(Above 60°) . . . 8-10 Eccentricity . . . 8-10

(13)

Modular Neutron Porosity. . . 8-10 Clean Reservoir Rocks Filled with Either Water or Oil . . . 8-10 Clean Reservoir Rocks Filled with Gas . . . 8-10 Shale Zones . . . 8-10

North and South America Log Presentations . . . 8-11 International Log Presentations . . . 8-13 Special Logging Applications . . . 8-15

Near/Far Count Overlays . . . 8-15 Pitfalls to This Technique . . . 8-15 Recommendations: "Methodology" . . . 8-16 Chapter 9

Triple Combo

Introduction. . . 9-1 Mud Types . . . 9-2 Borehole Corrections . . . 9-2 Gamma Ray . . . 9-2 Dual Propagation Resistivity. . . 9-2 Modular Neutron Porosity. . . 9-2 Modular Density Lithology . . . 9-2

M-SERIES . . . 9-4 MDMS . . . 9-5 P-SERIES . . . 9-5 HPUTIL . . . 9-5

(14)

Table of Contents Log Quality and Data Management Standards Filtering . . . 9-5

Despiking . . . 9-5 Hanning Window Filter . . . 9-5 Chi Square Smoothing . . . 9-5

Other . . . 9-6 Borehole Corrections. . . 9-6 Dielectric Corrections . . . 9-6 Squeeze. . . 9-6 Quicken . . . 9-6 ADDTSD . . . 9-6 ADDTVD . . . 9-6 Quicklook WDS Log Analysis . . . 9-6

Data Density . . . 9-8 Time Since Drilled . . . 9-8 Delta Rho (Dr) . . . 9-8

(Above 60°) . . . 9-11 Eccentricity . . . 9-11 Modular Neutron Porosity. . . 9-11 Clean Reservoir Rocks Filled with Either Water or Oil . . . 9-11 Clean Reservoir Rocks Filled with Gas . . . 9-11 Shale Zones . . . 9-11

(15)

Modular Density Lithology . . . 9-11 Permeable Zones . . . 9-11 Impermeable Zones . . . 9-12

North and South America Log Presentations . . . 9-13

Combined Log Formats (Triple Combo) . . . 9-13 Segregated Log Formats . . . 9-16

International Log Presentations . . . 9-19

Combined Log Formats) . . . 9-19 Segregated Log Formats . . . 9-22

Appendix A

Mnemonics Listing

Axis Magnetic Field. . . A-1 Attenuation. . . A-1 Axial. . . A-1 Azimuth . . . A-2 Bending Moment . . . A-2 Bulk Density . . . A-2 Conductivity. . . A-2 Dip Angle (Magnetic) . . . A-3 Density . . . A-3 Density (Photoelectric Cross Section) . . . A-5 Delta Rho . . . A-5 Drilling. . . A-5 Gamma Ray . . . A-5 Gravity (Accelerometer, Raw). . . A-6 Highside Toolface . . . A-6 Horizontal Magnetic Field (Magnetometer, Raw). . . A-7 Inclination . . . A-7 Lag Strokes . . . A-7 Magnetic Tool Face . . . A-7 Neutron Porosity . . . A-7 Phase Difference . . . A-9 Data Density/Elapsed Time calculated from MDMS/P-SERIES . . . A-9 DPR 2A Self Calibration Offset . . . A-10 Resistivity (Attenuation) . . . A-10 Resistivity (Mud) . . . A-11

(16)

Table of Contents Log Quality and Data Management Standards Rate of Penetration. . . A-11 Resistivity (Phase Difference) . . . A-11 RPM . . . A-12 Resistivity (Short Normal). . . A-12 Ratios . . . A-13 Resistance (Short Normal). . . A-13 Standpipe Pressure . . . A-13 Strokes (Pump) . . . A-13 Temperature . . . A-13 Total Gas . . . A-14 Total Magnetic Field . . . A-14 Torque (Rotary) . . . A-14 True Vertical Depth . . . A-14 Weight On Bit . . . A-14 Appendix B

Chart Calibration and Accuracy Test

Chart Accuracy (ST-250). . . .B-1 Invoking Chart Calibration and Accuracy Test . . . .B-2 Calibration Test . . . .B-2 Accuracy Test . . . .B-3

Film . . . .B-3 Chart Paper . . . .B-3

Gulton Wellogger . . . B-4

Multiscan Operating Instructions. . . .B-4

Multiscan Description . . . .B-4 Multiscan Operation . . . .B-4 Manual Method . . . .B-4 Software Method . . . .B-5 Software Version 3.00 Chart Calibration . . . .B-5 Manual Controls . . . .B-5 Software Command Data. . . .B-5 Step Accuracy Calibration Procedure . . . .B-5

Gultcal Software Calibration . . . .B-7 TABLE 1: Dip Switch Chart . . . .B-8 TABLE 2: Dip Switch Chart . . . .B-15

(17)

Chapter

1 Data Management

This chapter provides the proper procedures for labeling floppy disks and backing up data to ensure software compatibility and consistent management of data collected.

Labeling Floppy Disks

It is required that all data disks returning from a job be properly labeled as either Job Data, Raw/Edit Data, EP-1, D-Map, or Text. Every disk should have the job number, company, OCS-G/well number, location, and rig. In addition, every data disk should have beginning and ending depths as well as beginning and ending date and time. Avoid complicated

numbering schemes for your data disks in the event you do a lot of reaming or change from one service type to another (such as going from RGD to DPR).

When labeling your disks, use a pen with quick-drying ink. Allow the ink to dry before handling the disk or label (this will avoid smearing the ink and leaving the disk label illegible, which seems to be a common occurrence). Also avoid using a large broad tip marker (Marks-a-Lot) to label run numbers. Use a fine to medium tip marker instead.

Data Back Up

The number of MS-DOS utility packages available to the personal computer user are rapidly increasing. Many of these packages have redundant capabilities such as data back up and data compression. As a personal computer user, you may have your own special utility package that you prefer to use. However, it is extremely important that you leave your package at home and use the utility packages provided in the HPUTIL main menu. This ensures upward and downward software compatibility in

(18)

Data Management Log Quality and Data Management Standards every release of Teleco's surface software products. This also permits easy data manipulation for any data collected.

MWD Services

M-SERIES Systems

After all final logs are generated, back up all replay files to high density floppy disks. If the replay file (binary file) is relatively small (i.e., less than 1.1 megabytes), then copy the files directly to disk. If the file is larger, you need to back up the data using the Fastback Utilities program available from the HPUTIL main menu. The Fastback version used has been

upgraded to version 2.10. This version will read earlier versions of Fastback disks, but the disks created by 2.10 cannot be read by earlier versions of Fastback. If you are unfamiliar with using this utilities

program, contact your supervisor for guidance. It is important to note that during the job, you should always retain a copy of the original unedited raw data.

The files that are required for back up are as follows: • binary.* (this includes binary.fil, .idx, .uni, .apd)

• *.cfg (header information), use this with HPUTIL Rev. 2.1 or

greater

• setup.fil (Mplot/Wplot formats...formally newplot.fil)

• log.fil (Makelog/Head/Minihead formats) • tvddata.fil

• newplot.fil (use with HPUTIL versions earlier than Rev. 2.1)

• header.fil (use with HPUTIL versions earlier than Rev. 2.1) • comment.fil

• mserdb.133 (M-SERIES ASCII definition file)

P-SERIES Systems

All data is periodically backed up automatically to magnetic tape. Provide all job information and run numbers on each tape. If MPLOT in HPUTIL is used for plotting logs, a P-SERIES.Xfer file must be transferred into the HPUTIL directory so a binary file can be generated. In this case, back up the appropriate files as you would for an MWD M-SERIES system (see the preceding section). At the job's completion, you should have a set of disks with the binary.fil data and a set of P-SERIES magnetic cassette tapes.

(19)

Log Quality and Data Management Standards Data Management

RWD Services

M-SERIES Systems

In an effort to reduce the voluminous number of disks and different types of data disks returning from RWD jobs (i.e., xfer.fil, Getdata, raw memory, M-SERIES real-time data, etc.), please follow the recommended procedure for collection and storage of RWD data. The procedures also help conserve memory on the hard disk.

There are four types of data disks that need to be saved during the course of a downhole memory job when using an M-SERIES system. These are the M-SERIES “real-time” data disks, raw memory dump data disks, and Getdata and GetXfer data disks. All disks should be labeled with the job number, company, OCS-G number and well number, rig, and depth in and out and volume number, regardless of the type of disk label used. This becomes increasingly important when several sidetracks are drilled from the same job.

M-SERIES Disks

Using a standard floppy disk label, make sure every disk is fully labeled, including time/date and depth in and out. Also, be sure to label the M-SERIES software revision number in the upper left-hand side of the label and the disk number in the upper right-hand side.

Raw Memory Dump Disks

Standard (generic) disk labels can be used for these disks. You should back up memory dump data after each dump (run). Each memory dump needs to be stored on a separate set of disks. Label these as Mem Dump 1, Mem

Dump 2, etc. Besides the information recommended above (i.e., job

number, company, OCS-G number and well number, rig, and depth in and out), include any time offsets that were used for processing and the MDMS revision number in the upper left-hand corner of the disk label.

GetXfer Disks

Use a standard (generic) disk label for these disks. Label these disks as

GetXfer, volume (example: GetXfer, vol. 1 of 1). The directory for

GetXfer is automatically named “GetXfer.” The volume label is a reference to the disk number and total number of disks used when the GetXfer file is backed up to floppy disk using the Fastback Utilities program. Make sure to provide all other pertinent well information on the disk label that is required on the other disks.

The GetXfer executable is accessed in the HPUTIL main menu. This routine allows us to store the Xfer file selectively. When GetXfer is

(20)

Data Management Log Quality and Data Management Standards performed, a directory in the D:\ drive is created. The Xfer.fil is then compressed using PKARC and then copied into the Xfer directory. The engineer is required to perform a “GetXfer” at the completion of each run (i.e., memory dump) after all the memory data for that run has been processed.

Perform GetXfer on the D:\ drive. When performing the GetXfer program, name each run as Xfer1.ARC, Xfer2.ARC, Xfer3.ARC (Xfer file from run 1,2,3, etc.). Relog sections should be listed as Xrl1.ARC, Xrl2.ARC,

Xrl3.ARC (for Xfer file from relog 1,2,3, etc.). After a GetXfer is

performed, back up the GetXfer directory onto floppy disks using the Fastback Utilities program (see “Proper Sequence for Executing a GetXfer and Getdata” on page 1-7).

After the Xfer file has been backed up on the D:\ drive using the GetXfer utility program, delete the Xfer file from the C:\ drive. This is done to avoid duplication of data storage (i.e., storing the Xfer file on both the GetXfer and Getdata directories and data disks).

Getdata Disks

Use a standard (generic) disk label for these disks. Label these disks as

Getdata, directory (job number), volume, (example: Getdata \3250, Vol. 2 of 2). Always use the job number as the directory name. Make sure

to provide all other pertinent well information on the disk label, which is required on the other data disk types. Getdata backs up any file in the HPUTIL directory that has a “.fil” or “.cgf” extension. The Getdata routine is accessed through the HPUTIL main menu. A Getdata should be

performed at the end of each run. If you are on a job that uses both RGD and DPR tools, make sure the binary files for each tool type are merged or appended together prior to data back up. It is important to note that a Getdata should not be performed until a GetXfer has been executed and the Xfer file is subsequently deleted from the C:\ drive. After the Xfer file has been deleted from the C:\ drive, run Squeeze and Quicken, which will significantly reduce the size of your binary file. You are now ready to execute a Getdata (see “Proper Sequence for Executing a GetXfer and Getdata” on page 1-7).

Perform all of your Getdata on the D:\ drive. When Getdata is performed, store and label each run as Run1.ARC, Run2.ARC, Run3.ARC, etc. Run numbers should correspond to the correct bit run on the log header. After the Getdata has been executed, back up the Getdata to floppy disk using the

Fastback Utilities program. It is imperative that a Getdata be performed at

the completion of the last run, which includes the appended binary file for the entire job.

If changes are made to the database (e.g., comment.fil, *.cfg, etc.) after a Getdata was performed, another Getdata should be executed and backed up

(21)

Log Quality and Data Management Standards Data Management to disk to update the database. The idea is, in the event that logs have to be remade at a later date by either the engineer from the job or staff personnel, all of the information is readily available and will not have to be updated or recreated.

P-SERIES Systems

At the operator's option, all data is periodically backed up automatically to magnetic tape at a user selected time interval (every 30 minutes is

recommended). Provide all job information and run numbers on each tape. If MPLOT in HPUTIL is used for plotting logs, a P-SERIES Xfer file must be copied into the HPUTIL directory so a binary file can be generated. In this case, back up the appropriate files to disk using the Getdata routine in HPUTIL (see the preceding section). At the job's completion, you should have a set of Getdata disks and P-SERIES magnetic cassette tapes for the entire job.

Additional Data Management

Squeeze

Squeeze is a program that is accessed through the HPUTIL main menu and is designed to compress the binary.fil in HPUTIL. The compression is done by discarding all deleted records, removing all backplotted records, and averaging the data to a resolution of 0.25 feet (0.10 meters). In addition, the resistivity values are recomputed from conductivity to provide a more precise approximation than just averaging the resistivities. After Squeeze is finished processing, the data in the binary.fil is replaced in an ordered structure. The surface records are listed first, then directional, temperature, memory data, etc. This ordering however, poses some problems for the editor in MPLOT UTILITIES (DMD editor), such as time and depth searches. Therefore, use MEDIT to edit any squeezed files. There is also a Squeeze executable for XFER files in the HPUTIL main menu. Its

functionality is identical to the Squeeze used for binary files. Quicken

Quicken is also accessed from the HPUTIL main menu and is designed to speed up the searching routine for data when using MPLOT or MEDIT. It accomplishes this by creating a table of indices for each 100 feet of log. These indices allow MPLOT or MEDIT to jump to a point within 100 feet of the start depth of the log (or in the case of MEDIT, within 100 feet of the depth you are searching for), thus making it a lot quicker for searching. Quicken should be run after any program that modifies the binary.fil. This would include appending to a binary.fil, or executing ADDTVD,

(22)

Data Management Log Quality and Data Management Standards WTOB.EXE

This is a new program that copies a curve from a WDF file and either converts it to a binary.fil or writes it to a pre-existing binary file. IMP2MPLT.EXE

This program imports an ASCII file into MPLOT. It is similar to the MARC I ASCII file import.

HTFX.EXE

This program creates line commands for the sliding indicator (see “Comment Files” on page 2-11).

MEDIT

MEDIT is an editor for the binary.fil that has been compiled for use in the HPUTIL main menu. MEDIT is used to view/edit the binary.fil in the HPUTIL directory. Use the Up/Down arrow keys and the PgUp/PgDn keys to highlight the record type you wish to edit. Press [ENTER] to select a particular record type. Use the [F2] key for the Depth Search option. All changes to a file are permanent as soon as you change to another page or exit. If you do not leave the page, press [F1] to abort the edit and the original contents of the page will be restored. Always use MEDIT on a squeezed file. This will greatly reduce the search time when doing a depth search.

Future Additions

Future additions include the ability to convert binary files to TIF (Tape Image Files). This can be used to transmit data via fax or for rapid plotting of multiple log copies (MPLOT/WPLOT ver. 3.1).

(23)

Log Quality and Data Management Standards Data Management

Proper Sequence for Executing a GetXfer and Getdata

Process memory data using MDMS. An Xfer file is automatically created and copied over to the

DOS side on the C:\ drive.

Build a replay file using the Xfer file (this converts the Xfer file to a binary file) and append to the current binary file.

Execute Squeeze and Quicken.

Run a verification log to check data.

Execute GetXfer on the D:\ drive. Name runs as Xfer1.ARC,

Xfer2.ARC, Xrlg1.ARC, Xrlg2.ARC, etc.

Delete Xfer file on the C:\ drive.

Back up GetXfer file to floppy disk using Fastback Utilities program.

Execute Getdata on the D:\ drive. Name runs as Run1.ARC, Run2.ARC, etc.

Back up Getdata file on the D:\ drive to floppy disk using Fastback Utilities program.

(24)

(25)

Chapter

2 Log Preparation

This chapter provides specific instructions on generating various logs for original holes and sidetracks.

Recommendations for plotting traces and scales and generating log annotations and comments are explained in detail.

Note: Since depth scales for logs vary greatly between districts,

it would be difficult to include all of these each time the subject of depth scales is referred to within this

document. However, for any area, logs are generally presented with two depth scales that can be loosely defined as 1) correlation log scales and 2) quantitative log scales.

Correlation logs are typically plotted with smaller depth scales such as 1:600, 1:1200 English or 1:1000 metric. Quantitative logs are plotted with larger scales for quantitative analysis; typical scales are 1:240 English or 1:200 metric. All depth scales referred to beyond this point in this document are referenced as either “correlation” or “quantitative” log scales.

Regardless of customer requests on location, it is required that both 1- or 2- and 5-inch Measured Depth and True Vertical Depth Field and Final logs be generated at the end of a job. True Vertical Depth logs should be omitted if a vertical hole was logged. Two copies of field prints should be left on location.

When generating logs from the HPUTIL main menu, it is recommended to use the Make Log utility program. This utility permits the logging engineer to configure the header layout, log formats, and the configurations

(26)

Log Preparation Log Quality and Data Management Standards configurations can be stored for later use. The major advantage to this feature is headers can be individually matched to logs and comment files. Once your configuration is set up and plotting is invoked, both header and log are plotted sequentially.

Original Holes and Sidetracks

Engineers should treat original holes and sidetracks as separate wells. This means that the engineer should generate final logs and directional surveys for the original well, which should be completed and turned in before the start of the sidetrack. This data is finalized and sent to the customer. This is necessary because the client typically uses this data to plan the sidetrack wells.

If the engineers remain on location, they should make every attempt to generate final logs for the original hole and back up to floppy disk (or tape for P-SERIES) all appropriate data, including directional surveys, and send everything to the office. Only one End of Well Report, which summarizes the activities from both the original and sidetrack well, is necessary and should be turned in at the completion of the last sidetrack well.

Each sidetrack should have a separate header for that particular sidetrack. The first Eastman Teleco run number (in the Bit Run Summary) for each sidetrack header should succeed the last Eastman Teleco run number on the original hole or the sidetrack before that, unless the sidetrack well is considered as a “new well” by the operator. A “new well” status is usually applied if the bottom-hole location of the sidetrack well falls in another block.

When making final logs for the sidetrack well, the beginning of the log should correspond with the beginning of the sidetrack. Do not make a composite log that includes any portion of the original hole above the sidetrack unless specifically requested by the customer.

If you are requested to make composite logs, make sure to include a remark in the Remarks page indicating that the bit run information for the portion of log above the sidetrack can be found on the headers for the original log.

Traces/Scales

Trace Coding

The objective of using different line types is to distinguish between different types of measurements plotted together in the same track (i.e., phase difference/attenuation resistivities, neutron porosity/formation density, or conductivity/weight on bit, etc.). Therefore, unless you are

(27)

Log Quality and Data Management Standards Log Preparation plotting more than one parameter together in any one track, all primary trace curves should be represented by solid lines only. The only exception to this is the back up scale for conductivity (see conductivity scale in RGD/ DPR log formats) Both short normal curves in track 2 on the correlation

log format are plotted as solid lines. However, if you are plotting apparent

resistivities with corrected resistivities, the corrected resistivity should be coded with a medium dashed line.

Pen-up Intervals

Pen-up intervals should not exceed 10 feet (3 meters). The only exception to this is when plotting TVD for a horizontal well or tool temperature (TCDX, TCDM). There is no reason to use a pen-up interval greater than 10 feet (3 meters), regardless of data density. You are strongly discouraged from doing so. Any data gaps and the reasons for their occurrence should be documented in the Remarks page of the Log Header (see “Main Header, Remarks” on page 3-10). Pen-up intervals are referred to as “Interpolation Limits” in 1.3x M-SERIES software.

Recommendations for Scales

Use standard scales for traces where possible. However, when secondary traces continuously interfere with the primary trace or curve, scale

adjustments may be necessary. When it does become necessary to change scales, always contact the geologist and/or engineer in the office who is watching the well and request preferred scales and formats. Always perform a scale change on secondary curves before primary curves. If scale changes are made to both secondary and primary curves and interference still exists, it may be necessary to move the secondary curve to another track or remove it from the log. Once again, consult the client for the preferred location of traces.

Rate of Penetration

The rate of penetration is included on all logs unless otherwise requested by the client. This includes morning and afternoon field logs as well. Rate of penetration is plotted on a linear grid but variable scale. It is typically presented with “Gamma Ray” in track 1 or with “Conductivity” or “Weight on Bit” in track 3. The scale should always begin with 0 on the right side of the track with increasing rate of penetration towards the left. This provides correlation of the sands and shales with “Gamma Ray” in track 1. The scale should be set up to allow minimum interference with the primary curve (gamma ray, conductivity, or weight on bit). This may require a scale of 1000 to 0 ft/hr if the rate of penetration is high. Also explore the “Scale Change” option when the rate of penetration decreases or increases (see page 2-12 and page 2-15).

(28)

Log Preparation Log Quality and Data Management Standards It is important to note that when using MPLOT, select 5DSH (for

correlation logs) and 2DSH (for quantitative logs) under the selection line type. Trace coding and curve averaging are provided automatically. For example, for 2DSH, a histogram will be plotted as a medium dashed line with a 2-foot average. This means that no additional averaging or smoothing should be selected under MPLOT when preparing to plot the rate of penetration.

Gamma Ray

It is important to set the scale range so that individual divisions on the trace scale are whole numbers (for example, each division on a scale from 25 to 225 API is equal to 20 units, each division on a scale from 50 to 150 API is equal to 10 units, etc., as opposed to a scale of 50 to 275 API, where each division would be equal to 22.5 units). This is an API industry standard because it simplifies reading the curve.

Your scale should be set up to accommodate recommended divisions of either 10, 15, 20, or 25 units. Anything beyond 25 is generally too large because the separation between the sand and shale base line may be too small for adequate differentiation of lithologies.

The scale should also be arranged so the gamma trace is centered in track 1. If the curve becomes weighted to one side of the track (i.e., becomes increasingly sandy or shaly) as you increase in depth, it may be necessary to perform a scale change (see page 2-12 and page 2-15). If a scale change does not seem appropriate, pick the scale that works best through the zones of interest.

When plotting the gamma ray in track 1, you should set up your scaling to maximize the separation between the shale base line and the sand line. Ideally, you would shoot for a 4 to 6 division separation. However, when plotting a secondary trace in the same track as gamma ray, such as rate of penetration, the above recommendations often cannot be adhered to. The gamma ray trace must be compressed in order to accommodate the secondary trace. The following suggestions may be helpful.

1. Compress the secondary trace (i.e., rate of penetration) scale as much as possible before compressing the gamma ray.

Remember, MPLOT will do scale changes on the fly for any trace.

2. Since a 6 division separation between sand and shale may not be feasible, shoot for a 4 division separation (anything less than 4 divisions is not recommended). This may require using scales that we are not accustomed to, but still allow for divisions that are divisible by whole numbers. For example, with a scale from 30 to 180 or 80 to 230, each division equals 15.

(29)

Log Quality and Data Management Standards Log Preparation

Note: Note the different smoothing intervals for the gamma ray

MWD API trace on the 1-, 2-, and 5-inch logs. Always use a smaller smoothing interval for the higher rates of penetration.

Resistivity

The scale for both correlation and quantitative logs will vary for different locations. Consult the client for preferred scales and formats. As a standard, plot apparent resistivities on all logs for RGD services unless specifically requested by the customer. For the DPR service, plot corrected phase difference and amplitude ratio resistivities.

In the event that you need to change your resistivity scale due to anomalous readings that obscure the trace, use the following standards:

For correlation logs, your amplified measurement is always 1/5 the unamplified scale. For example:

Default scale: Change scale to:

unamplified = 0.0 to 10.0 unamplified = 0.0 to 20.0 amplified = 0.0 to 2.0 amplified = 0.0 to 4.0

Or:

unamplified = 0.0 to 50.0 amplified = 0.0 to 10.0

Note: An X10 scale is available (on MPLOT) as a back up

scale. This is typically used for linear resistivity scales (common in the Western Region) on all correlation logs for the 0 to 10 scale (see correlation log formats for the RGD and DPR Services). When the 0 to 10 scale wraps around (when resistivity exceeds 10 ohm-m) the back-up scale automatically switches to 0 to 100 scale. The back-up trace will begin at the first division beyond the left-hand track edge (this division equals 10 ohm-m). If the X-10 scale is used, a remark should be provided that explains that the back-up scale is a “X-10 scale.” Although this is a typical format for wireline 1- or 2-inch logs, it is new to our MWD/RWD logs. A remark will avoid any confusion for anyone reading the log.

For a quantitative log, the resistivity trace is ordinarily plotted on a two cycle semi-logarithmic scale. In order to increase the scale, increase from 2 cycles to 4 cycles. This is a standard procedure in the logging industry. For example:

(30)

Log Preparation Log Quality and Data Management Standards Increase from 2 to 4 cycles: 2-cycle = 0.2 - 20.0

4-cycle = 0.2 - 2000.0

A 4-cycle semi-logarithmic format should always occupy both tracks II and III (this will require you to sacrifice any other traces in track III). This prevents the scale from becoming too compressed in only one track. To do this, just set up track II with a 2-cycle semi-log scale from 0.2 to 20.0, and track III with a 2-cycle semi-log scale from 20.0 to 2000.0.

Note: Make note of the change from +/- wrap to the over option

for the resistivity trace in track 2 for quantitative logs. This option is now available on MPLOT and should be used wherever possible.

Conductivity

This trace is plotted commonly in areas characterized by low resistivity formations such as the Gulf Coast. This scale will also vary for different locations. It is always plotted on a linear grid, a default scale of which is typically 4000 to 0000 mmhos. Where space permits (i.e., extra traces are available for plotting), plot a back-up trace for conductivity (typically this would be 8000 to 4000 mmhos-meter). This trace is coded as a medium dashed line. If no space is available for extra traces, use the wrap or back-up feature for plotting. In either case, the back-back-up trace should be annotated as CSAX back up or CPCM back up on your logs (see “Back Up Trace Labels” on page 2-10).

Neutron Porosity

This scale is variable but always on a linear grid. In clastic formations (sand and shale), the scale is typically 60 to 0 porosity units. In carbonates (limestones), the scale is 45 to -15 porosity units. On correlation logs, this trace is plotted in track 3. On quantitative log scales, the trace is either plotted across tracks 2 and 3, or only in track 3. This trace is plotted as a solid line in double combo presentations (because it is a primary curve) and as a medium dashed line for triple combo presentations. Consult the client

for preferred scales and formats.

Bulk Density

This scale is variable, but always on a linear grid. The default scale is 2.0 to 3.0 g/cc (for a limestone matrix). Scales for clastic formations will vary for each region but a default scale that matches the neutron porosity 60 to 0 porosity units scale is 1.65 to 2.65 g/cc. Bulk density on correlation logs is typically plotted only in track 3. On quantitative logs, it is typically plotted across tracks 2 and 3 or only in track 3. This trace is plotted as a solid line.

(31)

Log Quality and Data Management Standards Log Preparation Density Porosity

This scale is variable (but always on a linear grid) to match the neutron porosity scale. In clastics (sands and shales), the scale is 60 to 0 porosity units. In carbonates (limestones), the scale is 45 to -15 porosity units. On correlation logs, this trace is plotted in track 3 with neutron porosity. On quantitative logs, the trace is plotted either across tracks 2 and 3 or only in track 3 with neutron porosity. This trace is plotted as a solid line. Consult

the client for preferred scales and formats.

Photoelectric Cross Section

The default scale is 0 to 10 barnes/electron, which is plotted on a linear grid. The scale may be manipulated to move the trace out of the way of the primary curves (keep track divisions as whole numbers). This trace is generally reserved for quantitative logs. It is plotted as a heavy dashed line in track 3 (when “Bulk Density” or “Density Porosity” is plotted across tracks 2 and 3), or in track 3 as a half track presentation (when “Bulk Density” or “Density Porosity” is plotted only in track 3). This currently is

not a commercial measurement!

Delta Rho Correction

The default scale is - 0.25 to 0.25 g/cc, which is plotted on a linear grid. Although the scale can be manipulated to move it out of the way of the primary curves, the same sensitivity should be maintained (i.e., - 0.5 to 0.20 g/cc). This curve is generally reserved for quantitative logs. It is plotted in track 3 as a medium spot line (when “Bulk Density” or “Density Porosity” is plotted across tracks 2 and 3), or in track 3 as a half track presentation (when “Bulk Density” or “Density Porosity” is plotted in only track 3). Consult the client for preferred scales and formats.

Time Since Drilled

“Time Since Drilled” is a trace that is automatically calculated in P-SERIES and MDMS software systems and is referred to as “Elapsed Time.” This trace is also calculated from the executable ADDTSD in the HPUTIL main menu (run ADDTSD after the binary file in HPUTIL has been constructed). It is important to note that there are differences between these traces. Most notably P-SERIES/MDMS calculates elapsed time on a run-by-run basis, which means the trace is interrupted at the end and beginning of runs. Use this trace only if HPUTIL and MPLOT are not available for generating logs. The ADDTSD executable calculates “Time Since Drilled” continuously from top to bottom so there are no

interruptions in the trace. The ADDTSD executable also gives you much more flexibility in selecting traces you can calculate TSD from, such as phase difference resistivity, gamma ray, etc. This is the trace of choice. Be careful when selecting mnemonics for plotting. Use mnemonics that are

(32)

Log Preparation Log Quality and Data Management Standards defined as “Time Since Drilled” (for example, RPTM - Time Since Drilled from Phase Difference Resistivity [RWD]).

This trace is plotted on linear grids only and reserved for quantitative logs. The default track for “Time Since Drilled” is track 3. However, it may be moved over to the first track for Triple Combo presentations to avoid competition with other traces or when a logarithmic grid is used in track 3. The default scale from 0 to 300 minutes (increasing from left to right should be used in conjunction with a medium spot line type. It is not recommended to use a scale smaller than 0 600 minutes. Since a medium spot line type is similar to a medium dashed line (the back up scale for conductivity), make sure to identify the back up conductivity trace as

CSAX back up or CPCM back up.

Note: Plot “Time Since Drilled” with the “X-10 Mode” (see

Note in “Resistivity” on page 2-5) to avoid multiple trace wraps where bit trips and long periods of circulation occur.

Data Density

Data density is another data type that is automatically calculated by the P-SERIES/MDMS software systems. This trace is also calculated with “Time Since Drilled” from the ADDTSD executable in the HPUTIL main menu (run ADDTSD after the binary file in HPUTIL has been

constructed). The “Data Density” calculated from ADDTSD is the trace of choice for plotting. Data density should be plotted as tick marks on the left side of the depth track on quantitative logs. Make sure to move any

annotated “Run Markers” to the right side of the depth track. True Vertical Depth

True vertical depth is another new trace added for horizontal wells. It is calculated from the ADDTVD executable in the HPUTIL main menu. It should be plotted on both correlation and quantitative logs in track 1 as a heavy spot line type with a variable scale (the scale will depend on the true vertical depths calculated in the lateral portion of the hole), which should increase from right to left. If scaled appropriately, the TVD trace can be used in conjunction with the gamma ray and/or resistivity traces to identify when the bit enters and exits the objective zone.

(33)

Log Quality and Data Management Standards Log Preparation

Log Annotations

Note: Annotations for logs are constructed using the control

file comment.fil (see page 2-13).

See Remark

Follow the recommendations in the “Remarks” section (see page 3-10). All remarks should be referenced on the log by the “See Remark” annotation. If the “See Remark” refers to a particular depth interval, position the reference in between the top and bottom of the interval instead of at the top or bottom of the interval. Do this unless the interval to be remarked is several hundred feet in depth on the log.

Trace Labels

Trace labels should be placed within the first 100 feet and last 100 feet of each log. If your log is only a few hundred feet in length, such as a relog or morning log, it may not be necessary to supply trace labels at both the top and the bottom of the log (i.e., avoid crowding the log with too much information). Examine TVD logs carefully for this! In addition, trace labels should be provided at intermediate points on quantitative logs and lengthy correlation logs. As a rule, these should be spaced approximately every five feet, or 1.5 meters, on both quantitative and correlation logs. It is important to remember that the trace labels may need to be adjusted so they are evenly spaced on the log. It is better to have fewer trace labels than too many trace labels. Also, avoid placing trace labels in pay zones or areas of interest.

Also, always make sure trace labels are provided where one service ends and another service begins on the log (i.e., where RGD converts to DPR). If large gaps are present on the log due to tool failures, or intervals that were drilled without Eastman Teleco, etc., provide trace labels where the traces end and begin again. Depending on the length of the gap, it may not be necessary to do this for the correlation log, but it should always be done for the quantitative log presentation.

When plotting correlation DPR logs with linear grids (such as the Gulf Coast), trace labels are required for both R_at and R_pd on the 0 to 10 scale as well as R_pd on the 0 to 2 scale. It is acceptable to position the trace labels for the 0 to 10 scale to the left of the traces, which will probably put the trace labels in the depth track (see log examples at the end of each chapter for service descriptions). Make sure that the trace labels are positioned such that they do not interfere with depth labels, run markers, casing markers, etc. Also take care to make sure the R_at trace label accurately points to the R_at trace (dashed curve) and the R_pd trace label points to the R_pd trace (solid line). As a rule, when the R_at and R_pd traces overlap one

(34)

Log Preparation Log Quality and Data Management Standards another, place R_at on the left side and R_pd on the right side of the

overlapping traces. Back Up Trace Labels

Make sure back up traces are labeled when plotted. They should be labeled as CSAX back up ->. These are entered as a freeform remark using the “Annotations Across” option (see page 2-15). This is done primarily for the conductivity trace.

Casing Markers

Always include casing markers in the depth track on all final logs

regardless of whether the casing marker overlaps with a depth label. Also identify the casing markers with the size of the casing (for example, 13-3/8” casing, see log examples at the end of each chapter for service descriptions). Attempt to place this inside of the casing unless space is a factor. This is done using the “Annotations Across” option (see page 2-15). Also make sure to reposition your casing markers appropriately for 5-inch logs. Casing markers can also be generated manually by using the “Line Annotation” option for comment.fil (see page 2-16).

If we log out of casing and this is recorded on the log, mark the casing according to the log, not at the depth recorded by the driller. If there is a discrepancy in depths, make note of it in the Remarks page. List separately the driller's casing depth and Teleco's casing depth (see log examples at the end of each chapter for service descriptions). It is also important to note those intervals of log that have been logged behind casing.

Run Markers

Identify run markers on the right side of the depth track where runs begin and end. If there are any runs that overlap one another, these runs need to be entered by hand using the “Annotations Down To” and “Annotations Down From Depth” options (see page 2-16). When runs do overlap, offset and alternate the run markers as shown in the log examples at the end of each chapter for service descriptions. Where resistivities plot below 0.2 ohm-m (i.e., plots into the depth track), offset run markers if necessary to avoid overlap between the run marker and resistivity trace.

Make note that run markers should now be plotted on the right side of the depth track. Data density has been moved to the left-hand side of the depth track so it will not interfere with resistivity traces that plot below 0.2 ohm-m.

(35)

Log Quality and Data Management Standards Log Preparation TD Markers

TD markers should also be provided at the end of the log (at “TD”) in the depth track unless they overlap with depth labels (see log examples at the end of each chapter for service descriptions). Commonly, this will happen on only one log, such as the TVD log. In this case, remove the marker from the log in question but include it on all other logs where it does not overlap. TD markers can also be generated manually using the “Line Annotation” option for comment.fil (see page 2-16).

Sliding Indicator

This is a new option that permits identification of sliding intervals on the log. As a default, plot the line between the specified depth interval on the outside edge of the right side of the log (i.e., track 3).

Comment Files

Note: In order to activate all or any of the annotation options in

comment.fil, go to the HPUTIL main menu and select MPLOT CONFIGURATION. Select “Yes” for desired options. It is important to note that comment files are generated using the SEE ASCII editor (selected from the HPUTIL main menu). Comment files are edited using either the SEE editor or the edit option in the MPLOT log plotting configuration menu (press [F1] to edit). To facilitate editing and log preparation, all features such as trace labels and annotations etc. can be viewed directly on the screen logs (press [F8] to view log).

Remarks

Type in your remarks as they should appear on the remarks page. If you do not want a remark printed, you must either delete it or insert an

exclamation mark in front of the remark. The exclamation mark, when placed in column 1, basically tells the computer not to print that line (see “Exclamation Mark” on page 2-12).

Annotations

You should make an attempt to learn all of the annotation options available under the comment.fil. Become familiar with freeforming the annotations and, in particular, the “Down from Depth” and “Down to Depth” options. These allow you to freeform run markers in the event that you have overlapping runs. You will also be required to annotate the casing size in the depth track of each log where applicable (see example logs at the end of each chapter for service descriptions). You may also find it necessary to

(36)

Log Preparation Log Quality and Data Management Standards freeform the “See Remark X” option when the preset positions get in the way of log traces.

Look for areas of conflict after plotting a log. For example, look for overlapping run markers, casing markers and TD markers that overlap depth markers, or trace labels and “See Remark X” that overlap traces, etc. If there are conflicts, reposition the label accordingly. Overlapping run markers should be put in the depth track using freeform annotations. Omit TD markers from logs where the TD marker conflicts with a depth label. See Remark 1

Make note of the track coding (1 through 4). If none of these positions works well for your log, use the freeform annotations (see the preceding section).

Exclamation Mark

Use the “!” symbol for any line you do not want to print on the remarks page. Also use this to fill line spaces between different sections in your comment.fil. This prevents blank remarks pages from printing below your last remarks.

Scale Changes

Become familiar with the “Scale Change” option (see example logs at the end of each chapter for service descriptions). This has a very important application for the first track on every log. In the past, we have encountered conflicts between the gamma ray and the rate of penetration trace. These conflicts can, in many cases, be eliminated with a scale change. In the event of high rates of penetration, you should apply a scale change to the rate of penetration trace through the interval characterized by the high drilling rates. In many cases, you may find it necessary to apply a scale change to the gamma ray trace when it drifts off to one side. Use good judgement for scale changes. Although you should feel comfortable about making scale changes, do not get in the habit of applying scale changes every 1,500 feet.

Trace Labels

When setting up trace labels, make sure to set up separate gamma ray trace labels for the correlation and quantitative logs. Due to the different

smoothing intervals between the two, labels set up for the correlation log typically will not work for the quantitative log.

Most engineers find it convenient to build a comment.fil for the main header and each log type (such as 1MD.fil, 1TVD.fil, 5MD.fil, 5TVD.fil, comment.fil). It is recommended to end each file with the three letter extension “.fil.” This ensures that all of these files will be stored when a

(37)

Log Quality and Data Management Standards Log Preparation Getdata is performed. Also make sure to use a name that makes it easy to understand which file is for which log. Remember, we need to have the capability to plot your log in the event you cannot. If any corrections are made to your comment files while you are plotting final logs, make sure to restore these to disk via a Getdata.

Traces On/Off

This is a new function in MPLOT that enables the engineer to turn traces on or off where desired. This is advantageous, for example, when you log behind casing. Your log response is rather erratic and may drift beyond the track it is plotted in. This data can be turned off without having to

manipulate the database. The same can be done in areas with poor data quality due to a tool failure. Its most common use is when combining real-time and memory data. Typically, the real-real-time data is disabled in the overlap region where the real-time data ends and the memory data begins or vice versa. (see “Traces On and Off” on page 2-15 for instructions on how to use this option.)

Guide to Comment.fil (Bryan Dugas)

Comment.fil

Comment.fil contains commands and text to be displayed on logs generated with MPLOT. It is important to note that the comment file is generated using the SEE editor (selected from the HPUTIL main menu). The comment file can be edited using either the SEE editor or the edit option in the MPLOT log plotting configuration menu (press [F1] to edit).

To facilitate editing, all features such trace labels, annotations, etc., can be viewed directly on the screen logs (press [F8] to view log).

Each line in the comment.fil is classified by the first character (which should always be left justified). Also note that there are no spaces in between characters. Below is a summary of the formats of the different types of annotations:

#LABEL,DEPTH,VALUE,LEFT OR RIGHT : Trace Labels

!COMMENT : Do Not Print

@X,DEPTH,TRACK # : See Remark X

^LABEL,DEPTH,CYCLES,LEDGE,REDGE : Scale Change

%ANNOTATION,DEPTH,LOCATION : ASCII Across

*ANNOTATION,DEPTH,LOCATION : ASCII Down To

(38)

Log Preparation Log Quality and Data Management Standards

+LABEL,DEPTH : Trace On

-LABEL,DEPTH : Trace Off

|START DEPTH,END DEPTH,LOCATION,WIDTH : Line Annotation Any Other Character : Remark On Header See Remarks X

@X,DEPTH,TRACK #

@1,12000,1 (example 1) @2,12500,4 (example 2)

Example 1: Place See Remark 1 at 12000 MD in the first track.

Example 2: Place See Remark 2 at 12500 MD in between tracks 2 & 3. TRACK # coding

1 = TRACK 1 2 = TRACK 2 3 = TRACK 3

4 = Between tracks 2 & 3

Comment Line

!This Line Will Not Print.

Trace Labels

#LABEL,DEPTH,VALUE,LEFT OR RIGHT

#GRCM,12000,160,R (example 1) #GRCM,12500,160,L (example 2)

Example 1: Place GRCM label at 12000 MD to the right of the trace at a value of 160.

Example 2: Place GRCM label at 12500 MD to the left of the trace at a value of 160.

An arrow automatically accompanies each trace label. For L the trace label looks like GRCM->.

For R the trace label looks like <-GRCM.

(39)

Log Quality and Data Management Standards Log Preparation Traces On and Off

+/-LABEL,DEPTH

-GRCM,12000 (example 1)

+GRCM,12100 (example 2)

Example 1: The GRCM trace is turned off at 12000 MD (the trace is no longer plotted on the log).

Example 2: The GRCM trace is turned on at 12100 MD (the trace begins plotting at the above depth).

Note: A valid range must exist for the <curve> when the log

begins plotting in order for the “+” and “-” commands to work. The screen log does not support this feature.

Scale Change

LABEL,DEPTH,CYCLES,LEDGE,REDGE

^GRCM,12000,0,25,250 (example 1)

^RSAX,12500,2,.2,20 (example 2)

Example 1: Change scale of GRCM at 12000 MD with 0 cycles (Linear Grid) and a scale from 25 to 250.

Example 2: Change scale of RSAX at 12500 MD with 2 cycles (Logarithmic Grid) and a scale from 0.2 to 20.

Annotations Across

%ANNOTATION,DEPTH,LOCATION

%10 3/4”,12500,540 (example 1)

%CASING,12000,540 (example 2)

Example 1: Place 10 3/4” at 12500 MD at location 540 (Depth Track). Example 2: Place CASING at 12000 MD at location 540 (Depth Track).

LOCATION CODING

28 280 540 690 940 1200 1450 1700

TRACK 1 Depth TRACK 2 TRACK 3

(40)

Log Preparation Log Quality and Data Management Standards Annotation Down From Depth

&ANNOTATION,DEPTH,LOCATION

&> Run 6,12000,660 (example 1) &> Run 5,11000,660 (example 2)

Example 1: Place > Run 6 starting at 12000 MD at location 660 (Depth Track).

Example 2: Place > Run 5 starting at 11000 MD at location 660 (Depth Track).

Annotation Down To Depth

*ANNOTATION,DEPTH,LOCATION

*Run 6 <,13000,660 (example 1) *Run 5 <,12000,660 (example 2)

Example 1: Place Run 6 < ending at 13000 MD at location 660 (Depth Track).

Example 2: Place Run 5 < ending at 12000 MD at location 660 (Depth Track).

Line Annotation

|<START DEPTH>,<END DEPTH>, <LOCATION>,<WIDTH>

This line command draws a line between the <Start Depth> and <End Depth> at the location of a given width. The width is represented in 1/200th of an inch (for example, “2” is 2/200th of an inch). This command is used to manually generate casing markers, TD markers, and sliding indicators.

|11000,11050,1701,8

Example: A vertical line is drawn on the outside edge of the track 3 from 11,000 to 11,050 feet with a line thickness of 8/200ths of an inch. “8” is a typical line thickness for a “sliding” bar indicator. “2” is typical for standard width lines.

(41)

Log Quality and Data Management Standards Log Preparation Horizontal Lines

|START DEPTH,END DEPTH,LOCATION,WIDTH

Horizontal lines can also be drawn by manipulating the start and end depth and width. In this case, start and end depth represent the line thickness and width is line length.

|9000,9000.2,540,153

Example: The TD marker is placed in the depth track at 9,000 feet. The length of the line begins at the location of 540 and extends for 153/200ths of an inch. Line thickness is 0.2 (log) feet.

Casing Markers

%?,DEPTH-0.5,537 %Þ,DEPTH-0.5,671

Casing markers can be created individually by using a combination of Annotation Across (%) and a line command (|). The depth listed should be the casing depth minus 0.5. Two special characters (?, Alt 22...for the left side) and (Þ, Alt-23...for the right side) are needed for plotting the casing markers. These ASCII characters are created in the text editor by holding down [ALT] and typing the number on the numeric keypad, then releasing

[ALT]. As can be seen, this annotation takes two comments, one for each

side of the depth track. Additionally, a line annotation is needed to draw a line across the depth track. Note the example below:

%?,9000.5,537 %Þ,9000.5,671

|9001,9001.2,537,153

Example: A casing marker is placed on each side of the depth track (location 537 and 671) at a depth of 9,000.5 feet. A horizontal line is also drawn across the depth track at 9,001 feet.

Note: Examples in “Line Annotation,” Horizontal Lines,” and

“Casing Markers” are based on a 5-inch log

presentation, the values for line width or thickness will vary depending on depth scales used for plotting.