Data Control is Essential

  In earlier days, data was collected by hand in an often hurried regimen of writing to a data pad as it was observed or calculated.  From this data the log was drawn by hand. This method was intentionally limited to a human's capacity to collect, calculate,  correlate and present information as a well is drilled.

 Once commited to paper, data was fixed to a given depth.  Depth errors could now only be addressed by overwriting previous data or leaving a blank and jumping ahead. (sometimes filling in the gap with "approximated" values)

 There are obvious problems with either solution.  In both cases the data curve integrity has been violated. Critical correlation and event analysis is now difficult at best. 

                Unique in the Industry               Virtually all logging programs today employ the same data method and  structure commonly used years ago, imposing  the human limitations of the data pad method on the modern computer.  

 Addressing the shortcomings inherent in the manual data method, we sought from the beginning of the design process to correct these issues by leveraging the functionality of recent developments in computing such as Object Oriented Programming, Hyper-Threading, Multi-Tiered Relational Data Base design and Solid State  Drives. Accuracy and Reliability is the result.

               Rule #One: Data is Inviolate

 There is no provision in the Data Center for adding or deleting footage or altering any data values.  Nothing is made up.  Data curves remain intact.  All of them.  All the time. Opinions cannot affect the data curves.

                Innovations in Data Control

 Modern drilling dictates that "flat file" data recording will no longer do.  Only an enterprise grade relational data base can accomplish what these techniques demand: a time based, multi-tiered data structure, to allow for active monitoring of drilling activities in real time, or by depth.

                          Time Based Edits 

 Human fallaibility will allow hole depth or bit depth errors to be entered into the rig's Electronic Data Recorder (EDR).  When this happens drill pipe motion can be recorded as drilled footage when in fact it was not. 

 We are uniquely able to select where this error occured and declare that bit movement during that interval was not an on-bottom event, but an off-bottom event.  The "feet" recorded are now simply pipe moving in the open hole, having no effect on recorded hole depth.  

                                 Depth Corrections

  It happens that errors are made and depths may be incorrect, but we know one thing: drilled feet are real.

 One cannot delete, change, insert or re-arrange them.

  But we can rename them.

 If, for example, we've been told our hole depth is now 20 feet less or greater than we previously believed, we will neither add nor delete 20 feet.

 We simply rename the bottom foot to the correct value and re-number the rest. Other methods can't do this. We keep the curves intact.  Any cumulative error due to even a slight mis-calibration of the drawworks encoder (often following a cut and slip procedure) is incrementally pushed towards the starting depth, rather than towards the bottom.

 As the hole is E-Logged from the bottom, so too is our log depth counted from bottom.  You get better correlation where it matters most. All the time.