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.
2. • Simple data loaders
• Excel data into PPDM
• LAS files into PPDM
Data movement scenarios
• In-house or purchased
E&P application
• Add import/export
capability
• Application vendor
• Need to load customer’s
existing data
• Continuous data
integration
• Make data available
across the business
• To all relevant
applications wherever
stored
In this presentation we will focus
on data export
www.etlsolutions.com
3. Example: Global oilfield services company
The client required a LAS, WITSML and DLIS file export
DLIS
LAS 2.0
PPDM
Well Log Data
www.etlsolutions.com
4. • Well log data was fed continuously into the client’s PPDM Oracle
database
• 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 the
existing architecture
• Instead, we created a bespoke solution…
The client’s existing system
Well log
data
Data feed
PPDM
JDBC
Applications
Security
Java applet
Messages
Web
services
Export
LAS,
DLIS or
WITSML
file
JEE Application ServerClient
www.etlsolutions.com
5. Solution overview
1. Design and implementation of mapping rules 2. Deployment
Design
• Domain experts
• Documented in Excel
Fit with existing architecture
• JEE 5 – JMS, Web Services
• Servlets/EJBs/MDBs
• Oracle 11g Database
• Custom services, eg Security
Implementation
• Runtime
Fit in with current development choices and practices
Offsite testing
We split the solution into two aspects:
www.etlsolutions.com
6. An example of the output
LAS 2.0 file extract:
www.etlsolutions.com
7. We defined the high level mapping, in this case from PPDM to LAS:
An example of the high level mapping
PPDM LAS 2.0
www.etlsolutions.com
8. An example of the lower level mapping
Section ~Well Information Block
Structured Mnemonic Unit Value Description
COMP WELL.BUSINESS_ASSOCIATE.BA_NAME Company
WELL WELL.WELL_NAME Well
FLD WELL.FIELD.FIELD_NAME Field
Excel was used to define the lower level mappings. This is a LAS
2.0 mapping extract:
www.etlsolutions.com
9. The implementation gap
Tends to be a
one-way
translation –
mixes SQL with
low-level
conditional logic
Text output and
exceptions
• This example code
(not the code actually
used in this project)
highlights the issues
• It can be difficult for
the domain expert
and the developer to
communicate via this
code
www.etlsolutions.com
10. Closing the implementation gap
Section ~Well Information Block
Structured Mnemonic Unit Value Description
COMP WELL.BUSINESS_ASSOCIATE.BA_NAME Company
WELL WELL.WELL_NAME Well
FLD WELL.FIELD.FIELD_NAME Field
Our Transformation Manager software places all relevant terminology
into the mapping system, improving communication and reducing risk:
11. Creating executable code
010101
Jar executable
Transformation
Manager creates a
Java jar file, which
then fits into the
client’s environment
www.etlsolutions.com
13. View the 30-minute on-demand
demo for more information and a
real-time demonstration by
Richard Cook, our E&P specialist:
http://www.etlsolutions.com/ep-data-management-demo/
Read our free white paper on
PPDM data integration:
http://www.etlsolutions.com/wp-
content/uploads/2012/07/Whitepaper-on-PPDM-Data-
Integration-Sept12.pdf
Free resources
Editor's Notes
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.