Pre-calculated EURs - Effective today, Drillinginfo is now providing pre-calculated EURs using its own internally developed Decline Curve Analysis engine. We are very happy with the overall quality of the EURs calculated by our new engine and having internal control of the entire process is a major benefit moving forward. Be on the lookout for a more detailed white paper comparing these internally generated EURs to those previously calculated through a third party provider.
[Oklahoma] - Oklahoma production is now supplemented with purchaser/transporter tax reports containing gross monthly oil volumes gathered from oil PUNs. This resolves issues regarding OTC oil production volumes where entire months of production were missing and reduces the reporting lag of oil production from 9-12 months to about three months. The result from this change will be available in DI Desktop, Production Workspace, DI Analytics, and DI Activity Maps.
[Oklahoma] - Oklahoma production is now supplemented with purchaser/transporter tax reports containing gross monthly oil volumes gathered from oil PUNs. This resolves issues regarding OTC oil production volumes where entire months of production were missing and reduces the reporting lag of oil production from 9-12 months to about three months. The result from this change will be available in DI Desktop, Production Workspace, DI Analytics, and DI Activity Maps.
[Louisiana] - Improvements to cross-unit well allocations - Changes were made to the Louisiana allocation algorithm to better handle cross-unit wells. Cross-unit wells are wells with laterals that span multiple units, therefore reporting production to multiple LUWs simultaneously. The Louisiana allocation process was originally designed to handle a well reporting production to multiple LUWs consecutively, but not concurrently. This resulted in cross-unit wells being mishandled as the process would only allocate production to cross-unit wells from one LUW rather than all of the relevant LUWs. Consequently, production for cross-unit wells was often understated and production for other wells on the same LUW’s was often artificially inflated. The allocation process was updated to allocate production to cross-unit wells from all associated LUWs. The associated LUW’s contribution to the well’s production is prorated based off of the percentage of lateral in each unit.
[North Dakota] - Several improvements were made including: (1) Increased reservoir coverage - Nearly 57% increase in Entity IDs with a valid reservoir, or approximately 96% of all ND Entity IDs now have a valid reservoir. (2) Increased status granularity - The state now provides status data that identifies confidential wells and drilled/uncompleted wells. New statuses of "CONFIDENTIAL" and "DRILLED/UNCOMPLETED" are now present. (3) Streamlined production ingestion logic - The state provides a full, historic data set. Previously, our ingestion process used business logic that treated the data as incremental rather than as a full data set. This resulted in missing certain types of adjustments to monthly production volumes. The logic has been adjusted and changed to correct this.
[Texas] - Allocated Input Improvements: We've made several improvements to our Texas allocated data set related to the inputs. (1) Injection Wells - we've introduced several measures to identify some of these wells and handle them properly. We're using various new sources of data including the RRC's UIC data and DI's internal completion data to more accurately identify injection wells that should not receive allocated production volumes. (2) Changing API Numbers - The RRC reassigns API numbers over time which can cause issues if the history isn't tracked properly. We've addressed this using the Texas Wellbore file and we will be using that data to clean up changing API numbers in the Allocated data set. (3) Correct Allocation Start Dates - Using completion data from DI Ingestion teams, we were able to identify Entity IDs that had an Allocation Start Date derived from an incorrect completion date. The start dates have been adjusted to the actual completion dates. (4) Monitor Wells - Business rules were developed to help identify monitor wells in unconventional plays. These wells were previously being allocated oil and gas volumes, but are now excluded from the allocation algorithm.
[Colorado] - Duplicated Production Improvement: Producing Entities that are pending review and approval by the COGCC are currently identified by the state with a reservoir name of “Not Completed”. There are some cases where the COGCC does not properly manage the transition of a well’s production from this pending status (i.e., “Not Completed”) to an approved and final reservoir name. This can result in duplicated production on the COGCC website as well as in the data they provide. We made changes to DI Desktop’s Colorado processes to help address these situations where duplication exists as a result of this error in transition to "approved" status. If the following two conditions are met, we will cull the monthly production record tied to the “Not Completed” Entity ID so that it doesn’t make its way into DI Desktop or any raw data feeds: (1) The well is horizontal, and (2) Production exists for the “Not Completed” stream and an approved stream for the same month
[Colorado] - Changes from the Customer's Perspective: The changes addressed in the bullet above only affect about 150 Entity IDs. However, the oil production associated with these is significant in the first half of 2015. When looking at production state-wide, customers will see drops in oil production as high as 700,000 bbls (or approximately 6.5%) in the early months of 2015. Drops in gas production are much smaller, averaging about 1.5% in early 2015. It is also important to note that since these changes involve correcting errors in the state’s data, DI Desktop’s data will now differ from state reports. For instance, DI Desktop will now report lower state-wide production during some months than reports available via the COGCC website.
[Colorado] - Reservoir Improvements: Producing entities that are pending review and approval by the COGCC are currently identified by a reservoir name of “Not Completed”. This is the reservoir name used by the state for these records. In DI Desktop, the permitted reservoir (when available) will now be included in parentheses following the “Not Completed” designation. Following are some examples of how the reservoir name will now show up in DI Desktop: NOT COMPLETED (NIOBRARA), NOT COMPLETED (CODELL), NOT COMPLETED (WILLIAMS FORK), NOT COMPLETED (NIOBRARA-CODELL)
** Customers who want to query all Colorado “Not Completed” records will now have to use wildcards in their search to pull all records.
[Virginia] - API Number Assignments: For many years the state of Virginia did not use or assign API numbers. Recently the API number was reintroduced, but the API numbers assigned to historical wells were overwritten resulting in changes in API numbers for about 3,000 wells. DI Desktop will be using the newly assigned API numbers to identify Virginia wells. However, the old API numbers will still be available to customers in PDEN_DESC.COMMINGLE_NO. This is a column that is searchable in DI Desktop as “Other No.”
[Virginia] - General Well Header Data Improvements: Added new data sources which increased the coverage of certain header data elements. Depth coverage increased by 11%, completion date coverage increased by 43%, and lease/well name coverage increased by 15%.
[Texas] - Salt Water Disposal (SWD) Improvements: Improvements were made to the HPDI Texas UIC loader to identify SWD wells. Previously, SWD wells in Texas were labeled with the more generic types of "SW INJ" or "OTHER INJ"; With these improvements, there will be about 32,000 total SWD wells in Texas in DI Desktop, approximately 8,000 of which are active.
[Colorado] - Header Data Improvements: Several changes were made to the Colorado loaders to improve header data coverage and quality in Colorado; These changes resulted in the addition of over 40,000 new completion dates and about 4,500 new spud dates