Constructing National Well Catalog with ArcGIS 10 and IHS Enerdeq 2013 John Farrell, GIS Manager, Fidelity E&P Co.
Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
Constructing National Well Catalog with ArcGIS 10 and IHS Enerdeq
2013
John Farrell, GIS Manager, Fidelity E&P Co.
Purpose of NWC
2
} National Well Catalog (NWC) } Asset teams are interested in oil and gas well information
around the country } Wells with Fidelity E&P Co. interest } Wells owned by other companies } Historical data about wells
} A fast and simple way to get data } Avoid bewildering array of applications } Let’s use a map } Blend with Fidelity E&P’s proprietary well data
Fidelity Enterprise GIS
Fidelity E&P Co. enterprise
3
} Corporate parent
Fidelity Enterprise GIS
§ Bismarck, ND
§ Energy
§ Construction
§ Utilities
§ Fortune 500
§ Denver, CO
§11.1 MBOE production (2011)
§ $456.3 M revenue (2011)
What is a well catalog?
4
} A list of wells } Not an oil & gas data model
} Enterprise data asset } Not “cloud computing”
} Indexed and searchable } Geo-referenced data } A data backplane to access other data and applications
that rely on a unique well ID for reference
Fidelity Enterprise GIS
Challenges
5
} Choice of a unique well ID } “What is a well?”
} Comprehensive coverage } Cost } Currency of data } Automation } Priority of source
Fidelity Enterprise GIS
Unique well ID
6
} Establish one surface location } 10-digit API number
} Establish one or more bottom hole locations } 14-digit API number
} Assume each surface location gets at least one bottom hole location
} Differentiate by proximity of surface and bottom hole } Nearby bottom holes treated as vertical wellbores } Outliers treated as directional wellbores } Caution: this is not a subsurface modeling database
Fidelity Enterprise GIS
Coverage
7
} Domestic historical header and production data } 8600 Fidelity E&P wells } Corporate “database of record”
} 3.9 M non-Fidelity top hole locations } 4.4 M non-Fidelity bottom hole locations } Several commercial data sources available } Fidelity E&P Co. uses data from IHS, Inc.
Fidelity Enterprise GIS
Cost
8
} “Big data” cliché } Cost is a function of completeness and quality of data } Value-add for collecting and organizing data for oil & gas
industry
Fidelity Enterprise GIS
Currency of data
9
} There is no point-in-time baseline } Data must be updated daily
Fidelity Enterprise GIS
Automation
10
} Coverage and currency demand automation } No humans in the loop } Server power
} Intel® Xeon® CPU X5660 4x2.0 GHz } 16 GB RAM
} Elapsed processing time 7 hours/night } Event notification via Email
Fidelity Enterprise GIS
Priority of sources
11
} Proprietary data first } Commercial data second } Any null fields in proprietary rows are backfilled with
commercial data } Sources of attributes are tracked
Fidelity Enterprise GIS
Design considerations
12
} Inception of project: populate an initial well header table } Validate software requirements and preliminary design } Seek review by data supplier IHS, and Enterprise GIS supplier
petroWEB, Inc. } Bulk well load from IHS } Tune database performance
} Technologies } SQL Server } Python } C# for update task } C# ArcObjects for wellbore polylines } ArcGIS Geoprocessing Tools } Microsoft Task Scheduler
Fidelity Enterprise GIS
Data sources
13 Fidelity Enterprise GIS
Data sources
14
} SQL database populated with initial load from IHS } Over 70 well header fields are included } SQL views used to replace well data with corresponding
proprietary data } Fidelity E&P data given priority } Null fields from Fidelity E&P are backfilled with IHS data } Resulting feature classes are a blend of IHS and Fidelity
E&P data
Fidelity Enterprise GIS
Tables, views, feature classes
15
} SQL tables used wherever possible } High performance } Warehouse IHS data } Fidelity E&P data in proprietary SQL database
} SQL views help shape data } “Rules engine”
} Final table is produced } Serves as Input Table Parameter value in geoprocessing } Geoprocessing yields feature classes } Top hole 10 } Bottom hole 14 } Wellbore path representations
Fidelity Enterprise GIS
Order of processing
16
} Three distinct processing episodes } Top and bottom hole locations processed nightly } Requires exclusive database locks
} Update task processed continuously } No interference with other processes
} Wellbore path processed over period of days } No interference with other processes
Fidelity Enterprise GIS
Update task characteristics
17
} Unattended process } All well and production data continuously updated } Adds/updates/deletes accomplished } Fields backfilled } Work queued by county } Deployed on multiple computers for max throughput } Functional and performance monitoring via Email
Fidelity Enterprise GIS
Update task benefits
18
} No interference with GIS users or other systems } No interference with nightly catalog update } High performance and throughput } 1000 transactions per hour or more } Fault tolerant } Network outages } Server downtime } Vacations
} Low disk space utilization
Fidelity Enterprise GIS
Update task technology
19
} Windows Task Scheduler } Windows 7 and Windows Server 2008
} IHS Enerdeq Web Service API } Windows console application C# .NET } Multiple worker “bots” } One unit of work at a time (county) } Any failed bot is quickly replaced } Extended data gaps due to service down are quickly filled
} Run continuously for 28 months to date } Practically no faults due to IHS data discrepancy or other } Enerdeq Web Service API is sensible, stable, and fast
Fidelity Enterprise GIS
Geoprocessing
20
} Windows MS-DOS batch scripts } Python scripts } Transact-SQL scripts } Windows Task Scheduler invokes batch scripts } ArcGIS Geoprocessing Tools } Table manipulation tools } Make XY Event Layer
Fidelity Enterprise GIS
Map symbols
21
} Large number of well statuses summarized } Rules engine } Cross reference tables support classification
} 15 distinct symbols result
Fidelity Enterprise GIS
Wellbore paths
22
} Representations of relationships } Not wellbore survey data } Relate top-to-bottom hole locations
Fidelity Enterprise GIS
Wellbore paths
23 Fidelity Enterprise GIS
Enterprise GIS
24
} Fidelity E&P Co. functional disciplines use Enterprise GIS } NWC attributes provide good flexibility for GIS maps } Access to dozens of reports } Well header } Production } Facility
} Exports for PETRA } High performance and data availability through petroWEB
Fidelity Enterprise GIS
Conclusion
25
} A few key components can be used to customize and enhance the national well data set maintained by IHS
} Seamless combination with Fidelity E&P data is achieved } NWC meets our goals of Currency, Completeness, and
Performance
Fidelity Enterprise GIS
Related Documents
