www.etlsolutions.com

An example of a successful proof of concept

• But how do you go about creating one? • A recent example from our data integration

work in the Oil & Gas industry illustrates the steps we take to create a successful proof of concept.

Introduction

In software development, a proof of concept can be a vital tool to demonstrate the software’s capabilities and its fit with the client’s requirements.

• Our clients’ needs can range from testing the suitability of the proposed software to sharing knowledge within the client’s organisation.

• In our recent Oil & Gas proof of concept, the main aim was to demonstrate the effectiveness of our Transformation Manager data migration tool in meeting the client’s petroleum data management requirements.

• Specifically, the proof of concept demonstrated that it is possible to use Transformation Manager to efficiently implement and deploy industry data standards to different types of petroleum data files.

Step 1: Defining the client’s requirements

• In our example, there were two types of files - LAS and DLIS – to migrate in the context of the PPDM and WITSML industry standards. The proof of concept accordingly aimed to deliver three scenarios:

• Embed transforms within near real-time message handling, particularly WITSML

• Data migration converting to LAS files to and from the client’s PPDM-based system

• Data migration converting to DLIS files to and from the client’s PPDM-based system.

Step 1 (continued)

• As with any project, defining the requirements from the client is an important step to take before starting work on the proof of concept. In this example, the items required before the proof of concept began included:

• Business rules to define the required mappings, such as details of field mappings, lookups and error handling

• Samples of the data to be extracted, such as well header and log curve data

• Any relevant information about the source and target models, such as local choices in the use of PPDM

• Sample files in the required format, including LAS 2.0 and 3.0.

Step 2: Defining the client’s input

• A review of the information received from the client:• Each source and target data model, including format, connection

options and sample data• Validation rules• Mapping rules

• Design of the workflow of the data through the integration process:

• Document flow of data• Document the decisions made

• Design the integration for implementation within our Transformation Manager software

• Implement the integration within Transformation Manager, including testing

• Demonstrate the results to the client• Describe the process and usage of Transformation Manager

to the user• Create a report describing the concepts, outcome and

potential usage within future projects.

Step 3: Action planning

The activities carried out by our consultants followed a similar path to previous proofs of concept and included:

• A final, tested, Transformation Manager deployment pack which delivered the data transformation to the client’s specification

• A licensed version of Transformation Manager for internal evaluation

• A proof of concept report as described above• Knowledge transfer to the client, including the use

of Transformation Manager, a review of its capabilities and an overview methodology

• A presentation and demo showing key processes, outcomes and future options.

Step 4: Delivery

In the petroleum data management example mentioned above, our team delivered:

The result was a component which can efficiently deploy the client’s data to a range of the most popular petroleum data management file formats.

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 user:

Why Transformation Manager?

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

For the business:

©2009 ETL Solutions

Why ETL Solutions?

• 10-year track record in data management, working with global blue chip clients

• Unparalleled knowledge from our team of data integration experts, many of whom have been with us since inception

• Our Transformation Manager and DataHub software have been proven in even the most complex data movements

• Expert support: first line of contact is with a developer or consultant

• Data integration focus – it’s all that we do

““We’ve cut a six-month project down to three months…a

sophisticated product that is easy to work with and maintain

AND gives us great performance. We’re very

confident with the solution."Arnaud Daeschner,

BNP Paribas

“Honda has been seeking to achieve Dealer Network

Integration for the last ten years. With the help of ETL Solutions, this has finally been achieved.

Considering the success, Honda is now planning to extend this

approach to the European dealers.”

Michael Doyle, Honda UK

Raising data management

standardswww.etlsolutions.com

Contact us for more information:

Karl Glenn, Business Development Directorkg@etlsolutions.com+44 (0) 1912 894040

Read more on our website:

www.etlsolutions.com

Images from Free Digital Photos freedigitalphotos.net