Data integrationA case study on the creationof an integration frameworkfor the Oil & Gas industrywww.etlsolutions.com
Introduction Transformation Manager, our data integration toolkit for developers, is used to efficiently connect oil and gas data stores with the industry„s leading integration standard.• Our client is a global oilfield services company with a long track record in the Oil & Gas industry.• To maintain their position as the leader in the sector, the client‟s new product development plan included a Professional Petroleum Data Model (PPDM) based software product.
The challenge• The product required a data integration framework capable of tackling multiple and diverse Exploration & Production (E&P) data sources.• The challenge was to develop scalable export components from the underlying PPDM database to LAS, DLIS and WITSML.
The solution• After evaluating a range of potential data integration tools, the client chose our professional services and Transformation Manager software for a number of Transformation reasons: Manager data • We have a long and successful track record in E&P movement software technical data management. • We offer a comprehensive service to help in the design and development of all the required export components, in a highly competitive and risk sharing commercial arrangement. • We have a track record of delivering on budget and to client deadline. Consultancy • Transformation Manager offers a tried and tested toolset services for the efficient delivery of the project. • Transformation Manager has the ability to connect and transform all the data types and footprint required. • We were able to provide an integrated solution fitting directly into the client architecture.• The project was divided into three stages…
Phase 1: Design phase• The architecture design defined the deployment code framework, specifying the interaction between the client‟s product architecture and Transformation Manager‟s own deployment code.• Mapping rules were defined in conjunction with the client. A mapping rule spreadsheet was created for each export function, containing the PPDM table/element level mappings to file format specifications.• Output file formats were also specified, particularly any requirements not already defined by the standards. These included ordering, spacing, custom sections and data type representation.
Phase 2: deployment code framework development• The deployment code was developed to a range of specifications, including export parameters and reporting requirements.• The framework‟s interfaces were hooked up to the implementations required by the client‟s product using JNDI. This obtained a database connection and performed the other tasks required.• The export code included transforms generated with Transformation Manager. Using the software‟s TM Designer application, the client‟s developers are now able to specify the rules by which the PPDM source data is mapped to the target data.
Phase 3: Export function development• As mentioned, the project focused on three file formats: LAS, DLIS and WITSML. For each format, a set of tests were defined. These tests consisted of a sample set of PPDM data and the export file to be produced, which were then used for final acceptance testing.• Our consultants tested the deployment code and mapping implementation, and also conducted performance testing. Integration testing was a joint activity between our consultants and the client‟s developers. The client carried out acceptance and final performance testing, with support from our team.• The transforms created in this phase conformed to the mapping rules defined in Phase 1. The adapter for each file format was designed to be scalable to meet the requirements defined during the design phase.
The result• We used our expertise, tools and commercial flexibility to meet a challenging client requirement. Our team delivered a component which can efficiently deploy PPDM data to a range of the most popular file formats.• The client is able to benefit from reduced risk and cost, alongside increased control and transparency of their own clients‟ E&P data.
Why Transformation Manager?For the user: Everything under one roof Greater control and transparency Identify and test against errors iteratively Greater understanding of the transformation requirement Automatically document Re-use and change management Uses domain specific terminology in the mapping
Why Transformation Manager?For the business: Reduces cost and effort Reduces risk in the project Delivers higher quality and reduces error Increases control and transparency in the development Single product Reduces time to market
Contact us for more information: Karl Glenn, Business Development Director email@example.com +44 (0) 1912 894040 Read more on our website: www.etlsolutions.com Raising data management standardswww.etlsolutions.com www.etlsolutions.com Images from Free Digital Photos freedigitalphotos.net