An example of a successful proof of concept


Published on

In this presentation we explain how to create a successful proof of concept for software, using a real example from our work in the Oil & Gas industry.

Published in: Technology
  • Be the first to comment

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

An example of a successful proof of concept

  1. 1. An example of asuccessful proof of
  2. 2. 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.• 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.
  3. 3. Step 1: Defining 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.
  4. 4. Step 1 (continued)• 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.
  5. 5. Step 2: Defining the client’s input• 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.
  6. 6. Step 3: Action planningThe activities carried out by our consultants followed a similar path to previous proofs ofconcept and included:• 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.
  7. 7. Step 4: DeliveryIn the petroleum data management example mentioned above, our team delivered:• 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.The result was a component which can efficiently deploy theclient’s data to a range of the most popular petroleum datamanagement file formats.
  8. 8. 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
  9. 9. 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
  10. 10. Why ETL Solutions? ““We’ve cut a six-month project• 10-year track record in data down to three months…a management, working with global blue sophisticated product that is easy to work with and maintain AND chip clients gives us great performance.• Unparalleled knowledge from our team of We’re very confident with the solution." data integration experts, many of whom Arnaud Daeschner, have been with us since inception BNP Paribas• Our Transformation Manager and DataHub software have been proven in even the most complex data movements “Honda has been seeking to achieve Dealer Network• Expert support: first line of contact is with Integration for the last ten years. With the help of ETL Solutions, a developer or consultant this has finally been achieved.• Data integration focus – it’s all that we do Considering the success, Honda is now planning to extend this approach to the European dealers.” Michael Doyle, Honda UK ©2009 ETL Solutions
  11. 11. Contact us for more information: Karl Glenn, Business Development Director +44 (0) 1912 894040 Read more on our website: Raising data management Images from Free Digital Photos