Whereoil/OpenSpirit Integration in a Major Information Access Project

1,412 views

Published on

KADME deployed Whereoil software in a major international oil company to help them access their data via OpenSpirit. The result is a single point of access to multiple sources of information from internal information sources, external data storage facilities, and national data repositories.

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
1,412
On SlideShare
0
From Embeds
0
Number of Embeds
6
Actions
Shares
0
Downloads
18
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Whereoil/OpenSpirit Integration in a Major Information Access Project

  1. 1. Whereoil/OpenSpirit Integration in a Major Information Access Project EAGE Vienna, 26th May 2011Thursday, June 9, 2011
  2. 2. The ChallengeThursday, June 9, 2011
  3. 3. The Challenge • The customer is a major international oil company with multiple office locations worldwide. • Access to the information distributed across locations and data silos is a major challenge for the Head Office. • Information is also available in the form of data subscriptions and external data storage facilities such as National Data Repositories. • The organization wanted a simple, fast, single point of access to those multiple sources of information. • The system should reduce the time spent to collect and assemble information from different applications, databases and websites. • The system should be accessed via a web based GIS front-end.Thursday, June 9, 2011
  4. 4. The Challenge • The customer is a major international oil company with multiple office locations worldwide. • Access to the information distributed across locations and data silos is a major challenge for the Head Office. • Information is also available in the form of data subscriptions and external data storage facilities such as National Data Repositories. • The organization wanted a simple, fast, single point of access to those multiple sources of information. • The system should reduce the time spent to collect and assemble information from different applications, databases and websites. • The system should be accessed via a web based GIS front-end. SimpleThursday, June 9, 2011
  5. 5. The Challenge • The customer is a major international oil company with multiple office locations worldwide. • Access to the information distributed across locations and data silos is a major challenge for the Head Office. • Information is also available in the form of data subscriptions and external data storage facilities such as National Data Repositories. • The organization wanted a simple, fast, single point of access to those multiple sources of information. • The system should reduce the time spent to collect and assemble information from different applications, databases and websites. • The system should be accessed via a web based GIS front-end. Simple FastThursday, June 9, 2011
  6. 6. The Challenge • The customer is a major international oil company with multiple office locations worldwide. • Access to the information distributed across locations and data silos is a major challenge for the Head Office. • Information is also available in the form of data subscriptions and external data storage facilities such as National Data Repositories. • The organization wanted a simple, fast, single point of access to those multiple sources of information. • The system should reduce the time spent to collect and assemble information from different applications, databases and websites. • The system should be accessed via a web based GIS front-end. Simple Fast AffordableThursday, June 9, 2011
  7. 7. The Challenge • The customer is a major international oil company with multiple office locations worldwide. • Access to the information distributed across locations and data silos is a major challenge for the Head Office. • Information is also available in the form of data subscriptions and external data storage facilities such as National Data Repositories. • The organization wanted a simple, fast, single point of access to those multiple sources of information. • The system should reduce the time spent to collect and assemble information from different applications, databases and websites. • The system should be accessed via a web based GIS front-end. Simple Fast Affordable ComprehensiveThursday, June 9, 2011
  8. 8. Thursday, June 9, 2011
  9. 9. Thursday, June 9, 2011
  10. 10. Information access scenario send data to map send data to search Whereoil GIS portal Search Corporate Geodatabase Whereoil server (ArcSDE) Corporate OpenSpirit OpenWells DB NPD DEAL Task Management IHS GEUS OpenWorks OpenWorks Petrel application R2300 R5000 Petrobank News internal data external dataThursday, June 9, 2011
  11. 11. OpenWorks/SeisWorks Crawler • Metadata contained within an Openworks / Seisworks data repository is scanned and then crawled for inclusion into Whereoil. The metadata extraction process is performed using the Openspirit API • The following Openspirit Data Model types are supported: Project, Well, WellBore, WellPick, WellVelocity, WellLogTrace, LineGeometry2d, SeismicGeometry3d, PostStack3d, PostStack2d • Scanning can be a processor and time-consuming exercise, hence the need for an “updated only” scan. Scan commands must be executed as a user with suitable access permissions to the Openworks / Seisworks data repository. • Therefore we created two Whereoil tools for metadata extraction: • A Scan tool that undertakes full metadata extraction from a specified Openspirit DataSource • An Update tool that only extracts metadata modified within a specified time intervalThursday, June 9, 2011
  12. 12. OpenSpirit data sources and the restThursday, June 9, 2011
  13. 13. Entitlement management in OpenWorks/ SeisWorks • OpenSpirit is normally used at runtime with a named user, so this particular use in this project (check with Igor) • As Openworks metadata is not available for public access, users must be granted a minimum of "browse" level access to view data. User access is configured on a User/Project basis in Openworks. • The Whereoil Crawler is setting the corresponding access rights for each extracted record during the crawling phase. • Individual entitlement properties determine record filtering during querying in Whereoil Search. • To preserve in Whereoil the user access level defined in Seisworks, data entitlements are extracted from the plist.* text files in the user profile directory.Thursday, June 9, 2011
  14. 14. Using the OpenSpirit API • To maintain OpenWorks spatial data in the GIS portal, the OpenSpirit Scan Utility was used to convert datatypes to features that can be stored in ArcSDE. • This data spatialization process is both time and process intensive. As the Scan Utility does not handle selective updating, the need for a batch updating process that only processes changes is of the highest importance. • This was achieved using a utility developed by Kadme, called SCANXML. The utility determines updated datasource files and generates Scan Utility xml configuration files. • The Scan Utility is then run in batch mode, invoked selectively with the xml configuration files created by SCANXML to update the ArcSDE datastore and ensuring updated features can be displayed on the GIS portal. • We understand that this type of functionality will be included in the next release of the Scan Utility.Thursday, June 9, 2011
  15. 15. Integration with the GIS portal Send to mapThursday, June 9, 2011
  16. 16. Global Rollout send data to map send data to search Whereoil GIS portal Search Corporate Geodatabase Whereoil server (ArcSDE) ync Da ta s Whereoil server Corporate SDE OpenSpirit OpenWells DB NPD DEAL Task Data Management Petrel IHS GEUS sync OpenWorks OpenWorks application OpenSpirit R2300 R5000 Petrobank News internal data external data SDE Whereoil server Data sync OpenSpirit SDE Whereoil server OpenSpiritThursday, June 9, 2011
  17. 17. Future Developments • Possible new connectors for other OpenSpirit enabled data sources • Use of OpenSpirit’s Enterprise Service Bus • To support exchange of events between Whereoil and OpenSpirit-enabled applications, applied for OpenSpirit-enabled data sources. • Run Time access to applications • Data transfer workflowsThursday, June 9, 2011
  18. 18. Thanks! For more info about Whereoil, please visit: http://www.kadme.com/solutions/whereoil/ You can see a short video demonstration of Whereoil at: http://www.kadme.com/solutions/whereoil/whereoil-demo-video/ KADME is booth number 1591 12Thursday, June 9, 2011

×