Achieving Automated Mapping of Seismic Acquisition Data Using FME Jerrod Stutzman Sr Spatial Analyst, Devon Energy

Devon Energy Corporation Devon Energy Corporation is a leading independent natural gas and oil exploration and production company. S&P 500, Fortune 500 NYSE: DVN ~5,000 employees Oklahoma City (HQ, new building under construction), Calgary, Houston, field offices in OK, TX, WY, NM, etc 40-year anniversary this month

Devon’s FME Environment FME Desktop 13 licenses on FLEX License Server FME Server 3 Production licenses, 3 Staging/Test licenses Windows Virtual Servers Windows 2003 SP2 2.66 GHz Intel Xeon, 1 GB RAM Apache Tomcat servlet engine/web server Scheduling handled by Tidal Enterprise Scheduler

Devon’s FME Usage ~20 desktop users FME Server jobs FME Administrator ~5 “power users” (workbench authors) FME Server jobs Scheduled 7 Nightly, 3 Weekly (and growing) “On Demand” Typically only used in special cases FME Administrator Handles Server uploads/scheduling for production (staging open for authors)

Devon’s FME Usage FME Desktop and Server are used directly or indirectly by a variety of groups at Devon. GIS, G&G, Land, Midstream, Field Operations, Seismic and Well Data Management, etc Lease dissections/rollups Scheduled data exports Pipeline Risk Management Creating spatial data for mapping Quality Control Automated comparisons & database updates

Problem Information Delivery System (webmap-based well and seismic data viewing/ordering tool) needed seismic mapping layers Seismic navigation data is stored in non-spatial Oracle database Mixed datums (NAD27, WGS84) Data stored as shot points, want to display as lines End result should perform very fast (cached ArcGIS service)

This looks like a job for… FME to the Rescue! HELP! This looks like a job for… GURU

FME Server + Custom Transformer Solution FME Server + Custom Transformer Multiple workbenches to handle inserts, updates and deletes are run and monitored via ServerJobSubmitter Each workbench uses 2DPointAdder and PointConnector to create seismic line geometry Reprojector transformers used to reproject to common coordinate system ArcGISCacheUpdater (custom-built transformer) updates cache when data changes

Run segments workbench Workflow Main Workbench Builds WHERE clause (published parameter for workbenches) based on last run time Run updates workbench Success = N Success = Y JobTerminator Run segments workbench Success = Y Update last run time. Run deletes workbench Success = Y END

Workbench

Custom Transformer ArcGISCacheUpdater transformer is used in all workbenches associated with this process Parameters are entered to define cache server details, SDE feature class, etc Cache tiles are refreshed for locations with new, updated, or deleted seismic lines

Custom Transformer Details Managed C++ .net, FME C++ API, SDE C API When a feature is passed into the transformer, a web service call returns cache details FME function receives feature, checks SDE for previous state, updates geometry. Previous and current state of feature extents are used to update cache tiles.

2 feature classes for seismic data in SDE End Result 2 feature classes for seismic data in SDE Automated sync (nightly) with seismic database Cached web mapping service real-time with SDE 2D seismic data represented by polylines 3D seismic data represented by polygons

Devon IDS Interface

Thank You! Questions? For more information: Jerrod Stutzman Devon Energy Corporation Jerrod.Stutzman@dvn.com (405) 228-8279