"Out of the Box" Workflow Simplicity Data Access Using PPDM in a Multi-Vendor Environment

Transcription

1 "Out of the Box" Workflow Simplicity Data Access Using PPDM in a Multi-Vendor Environment W. Brian Boulmay Director, Business Partners Fall 2010

2 Abstract Proper conversion of unit and coordinate reference values is critical to placement of the drill bit. The OpenSpirit Catalog of Reference Values allows PPDM to have virtual "out of the box" capabilities and immediate interactivity across an end user's multi-vendor environment. This talk will introduce the new PPDM Data Connector from OpenSpirit, which enables read/write data transfer capability from/to PPDM data bases in a multi-vendor application and data store environment. End users will experience improved support for coordinate reference systems, as well as the ability to leverage reference data from existing sources or via the PPDM Data Connector. The talk will also illustrate use cases of the next generation of OpenSpirit data management tools to access the entire PPDM data model.

3 Outline Master data management Attraction of open standards like PPDM Challenges in implementing PPDM Solution approaches Example workflows Conclusions

4 What is Master Data Management? management of the non-transactional data entities within an organization

5 Need for Well Master Data Management Project Data Transactional Data G&G Interpretation System Final Results Reports, Analyses, Processes and Interpretations Field Collection Proprietary Data Master Data Corporate Repositories Data Vendors Public Data Legacy/ Archive Data Paper\Film\Tapes

6 Vendor Neutrality A good MDM strategy should rely on open data standards Over time, most organizations have hybrid interpretation and data management solutions. Vendor neutrality ensures that the data being managed today will be accessible tomorrow

7 Public Petroleum Data Model Developed by 100+ member companies to establish global E&P standards and increase efficiency Overriding set of principals that apply to the design of the PPDM database. Ensures disparate subject areas developed by many people over many years have similar look and feel and usage patterns. Designed to minimize impact of different database platforms (Oracle, SQL Server, PostgreSQL, ) Based on SQL 92 ANSII Standard (Oracle 9i and higher) Includes naming conventions for tables, columns and constraints PPDM supplied materials include the Data Definition Language for several popular database platforms

8 PPDM provides WELL UWI ABANDONMENT_DATE ACTIVE_IND ASSIGNED_FIELD BASE_NODE_ID BOTTOM_HOLE_LATITUDE BOTTOM_HOLE_LONGITUDE CASING_FLANGE_ELEV... > R_WELL_STATUS Tables and columns with comments Primary and Foreign Keys Check constraints Indexes Units of Measure constraints

9 But you will need to add. Integration with GIS Integration with vendor project data stores Data browsing/viewing ASCII LAS File import/export WELL R_WELL_STATUS Reference values Audit triggers, cascade deletes, views and queries, security users, roles Integration with G&G applications

10 Options to provide this integration

11 Services For Application & Data Integration Applications Web Client Web Services APIs in Java,.NET, and C++ Windows, Linux, and Solaris Event Service Unit Service Coordinate Service Data Access Service Copy Service Meta Model Service Integration Framework Data Connectors Metadata Repository Master Data Store PPDM Projects

12 New PPDM Data Connector Read/Write to PPDM 3.7 (3.8 under development) Over 45+ Geotechnical apps have automatic access to PPDM for Read/Write. Full access to entire PPDM data model Transfer Data between PPDM and other 12+ G&G data stores using customized Business Rules GIS integration via ArcGIS Desktop, Server, Explorer Reference values Units, coordinates, logs, etc

13 Anatomy of a Data Connector Application Data Service API Query data (SELECT, INSERT, UPDATE, or DELETE) in desired CRS, units, data model (native or common) Data Connector Query Engine Native Model Queries Coordinate and unit transformation (optional) Model Map Mapped Model Queries Use ETL design tool and ETL runtime engine. Map may be updated to account for changing data model and business rules. DataProvider Data store Metadata Repository

14 Examples Workflows enabled by PPDM Data Connector

15 Conclusions A vendor independent data model like PPDM offers advantages is a good basis for a master data management solution PPDM needs to be supplemented with a number of data management tools and integrated with other vendor applications and data stores An SOA approach offers a great deal of flexibility and minimizes effort to integrate with a diverse set of changing data stores and applications Leveraging ETL model mapping and transformation tools allows change to be more easily managed

16 OpenSpirit Partners November 9, 2010

17 W Brian Boulmay