[Oklahoma] - The Oklahoma Tax Commission (OTC) recently changed the structure and format of their digital data offerings. We have made changes to accommodate these changes, with the result that customers will see substantial improvements in the Oklahoma production dataset.
** The changes referenced above made significant improvements to Oklahoma production data, well header data, and cleanup of duplicate records. Please contact Support for additional detail including before/after production charts, oil and gas gatherer improvements, and detail behind duplicate cleanup.
First12 improvements - First12 precalculated logic improved to only reflect a volume for entities that have been online for greater than or equal to 12 months
[Oklahoma] - Oklahoma production has been historically supplemented back to 2015 (as well as the huge dip in August 2008) 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. The result from this change will be available in DI Desktop, Production Workspace, DI Analytics, and DI Activity Maps.
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.