An example of a customised DLIS, LAS and WITSML file export


Published on

Integrating E&P technical data often requires a tailored solution that simply is not available off-the-shelf. However, building a custom solution can be a costly and risky undertaking that can end in failure. This presentation, which includes links to the online demo version, shows an example of how we recently delivered a comprehensive LAS, WITSML and DLIS file export from our client’s new PPDM-based software product in around three months, on time and to budget.

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
  •  The export isn’t standalone, it’s an addition to an established system with many other applications. There are several companies involved and they have a way of working.The client UI code is developed by one team, required application server side services will be provided by another. The PPDM database contains the data to export.
  •  For us there are 2 aspects to the solution: mapping rules, which specify at a domain expert level how the fields etc in the source PPDM database are written to the export file formats.We did this in Excel mapping at the table and field level, using terms in the source familiar to PPDM relational model domain experts, and target terms familiar to the clients DLIS, LAS and WITSML domain experts.Somehow these definitions need to be imlpemented such that they can execute on the target system.Deployment is the provision of web services, JMS messaging and enterprise application to support the export functionality.Much of the system exists, there are 3 teams working together, they have their way of doing things. There are already Java, WebLogic application server developmehnt and admin expertise (admin ongoing), Oracle experts and client UI experts. We need to minimise the impact of the export module – minimise additional costs, installation and ongoing admin requirements.
  • An example of a customised DLIS, LAS and WITSML file export

    1. 1. www.etlsolutions.comAn example of acustomised DLIS, LASand WITSML file export
    2. 2. • Simple data loaders• Excel data into PPDM• LAS files into PPDMData movement scenarios• In-house or purchasedE&P application• Add import/exportcapability• Application vendor• Need to load customer’sexisting data• Continuous dataintegration• Make data availableacross the business• To all relevantapplications whereverstoredIn this presentation we will focuson data
    3. 3. Example: Global oilfield services companyThe client required a LAS, WITSML and DLIS file exportDLISLAS 2.0PPDMWell Log
    4. 4. • Well log data was fed continuously into the client’s PPDM Oracledatabase• The client wanted to add an export capability via a user menu:• Hand-coding was dismissed as an option because it is hard to maintain• Server tools (e.g. Oracle Data Integrator) had a lack of fit with theexisting architecture• Instead, we created a bespoke solution…The client’s existing systemWell logdataData feedPPDMJDBCApplicationsSecurityJava appletMessagesWebservicesExportLAS,DLIS orWITSMLfileJEE Application
    5. 5. Solution overview1. Design and implementation of mapping rules 2. DeploymentDesign• Domain experts• Documented in ExcelFit with existing architecture• JEE 5 – JMS, Web Services• Servlets/EJBs/MDBs• Oracle 11g Database• Custom services, eg SecurityImplementation• RuntimeFit in with current development choices and practicesOffsite testingWe split the solution into two
    6. 6. An example of the outputLAS 2.0 file
    7. 7. We defined the high level mapping, in this case from PPDM to LAS:An example of the high level mappingPPDM LAS
    8. 8. An example of the lower level mappingSection ~Well Information BlockStructured Mnemonic Unit Value DescriptionCOMP WELL.BUSINESS_ASSOCIATE.BA_NAME CompanyWELL WELL.WELL_NAME WellFLD WELL.FIELD.FIELD_NAME FieldExcel was used to define the lower level mappings. This is a LAS2.0 mapping
    9. 9. The implementation gapTends to be aone-waytranslation –mixes SQL withlow-levelconditional logicText output andexceptions• This example code(not the code actuallyused in this project)highlights the issues• It can be difficult forthe domain expertand the developer tocommunicate via
    10. 10. Closing the implementation gapSection ~Well Information BlockStructured Mnemonic Unit Value DescriptionCOMP WELL.BUSINESS_ASSOCIATE.BA_NAME CompanyWELL WELL.WELL_NAME WellFLD WELL.FIELD.FIELD_NAME FieldOur Transformation Manager software places all relevant terminologyinto the mapping system, improving communication and reducing risk:
    11. 11. Creating executable code010101Jar executableTransformationManager creates aJava jar file, whichthen fits into theclient’s
    12. 12. WebservicesApp serverIntegrationlayerPPDMClientQueryReadServices•Security•UoM•…Integration and deploymentCoreTestrigPPDM• A core mapping pieceof code was runautomatically via a testrig• An integration layerand test client werealso developed• All the client had to dowas to plug in a fewconfigurations e.g.units of
    13. 13. View the 30-minute on-demanddemo for more information and areal-time demonstration byRichard Cook, our E&P specialist: our free white paper onPPDM data integration: resources