20
Paradigm and WITSML 29 th April 2004 John Turvill

Paradigm and WITSML 29 th April 2004 John Turvill

Embed Size (px)

Citation preview

Page 1: Paradigm and WITSML 29 th April 2004 John Turvill

Paradigm and WITSML29th April 2004

John Turvill

Page 2: Paradigm and WITSML 29 th April 2004 John Turvill

About ParadigmOur Solution Offering

Technical Software Solutions and

Product-Driven Services

for exploration & production companies

and for oilfield service companies

Page 3: Paradigm and WITSML 29 th April 2004 John Turvill

What does Paradigm offer?

Page 4: Paradigm and WITSML 29 th April 2004 John Turvill

Scalable Solutions

Page 5: Paradigm and WITSML 29 th April 2004 John Turvill

Wellbore Placement Technology

WellPlanning

Geosteering& Drilling

Visualisation

Petrophysics & Rock Physics

Advanced Seismic ProcessingVelocity Modelling & Depth Imaging

AVO / AI / EI Inversion

Attribute Calculation & AnalysisPetro-Acoustic Modelling

Volume Classification

Interpretation

Time to Depth

Trac

e-to

-Tar

get

Trace-to-Target™ Well Planning,

Geosteering & Drilling Workflow

Page 6: Paradigm and WITSML 29 th April 2004 John Turvill

DrillingOptimization

GeosteeringReservoir Placement

Wellbore Placement Workflows

Co-visualization

Reservoir Characterization

3DPore

pressure

Real-TimeUpdate

WellProgram

& Drilling Design

InteractiveWell

Planning

Page 7: Paradigm and WITSML 29 th April 2004 John Turvill

WITSML Implementation

Page 8: Paradigm and WITSML 29 th April 2004 John Turvill

Paradigm Key Product Brands

Data Management

and Interoperability

Page 9: Paradigm and WITSML 29 th April 2004 John Turvill

The εpos 5-layer model

Page 10: Paradigm and WITSML 29 th April 2004 John Turvill

What is εpos?

• Data Repositories optimized for E&P– Designed for complex structures and large data volumes– Can host data for a large spectrum of applications and disciplines

• A Middleware Framework– Supporting distributed data management– Multi-vendor, multi-data model, multi-platform– Independent of repository architecture (relational, hierarchical, flat)– Simple access using a powerful Application Programming Interface

• Data Management Applications– Administration of projects, repositories, users and groups– Browsing tools for broad, multi-vendor networked repositories

Page 11: Paradigm and WITSML 29 th April 2004 John Turvill

Tight & Loose, or Loose & Tight?

ApplicationApplication

Application

Application

Single Database

Application

Visualization Application

Modeling Application

Inter-Process Communication

Traditional: Tight Data, Loose Applications DistributedData Management

Visualization Canvas

Solid EarthModeler

ApplicationApplication

Application

εpos: Loose Data, Tight Applications

Page 12: Paradigm and WITSML 29 th April 2004 John Turvill

Keep the data where it belongs

• Locate data where it makes sense, under its own rules– Seismic in multi-terabyte disk farms– Engineering on Windows servers– Databases from other vendors for certain asset teams, etc..

• Catalog the existing data repositories– Register over the entire network all data sources

• E&P projects will point to a list of selected repositories– Build a project by associating data from different sources.

• Distribute the management of data– Synchronized services available on all systems storing data– No single point of failure

Page 13: Paradigm and WITSML 29 th April 2004 John Turvill

Benefit: Scalable to any company size

• εpos can run on a single laptop, with a single user– No onerous administrative overheads

• εpos can run in a complex environment– Heterogeneous hardware platforms– Great diversity of data in different data stores– Connected to third-party repositories– Complex user authorization patters including specialists, etc…– Administrators can have overview the available services

• Mobile systems included– Disconnection and re-connection of mobile systems– Automatic synchronization with the other εpos servers

Page 14: Paradigm and WITSML 29 th April 2004 John Turvill

Where does WITSML fit?

Paradigm Architecture

IDEASRDBMS

Sysdrill

OpenWorks

ORACLE

GeoFrame

ORACLE

IDEAS Well Data Server

GF Well Data Server

OW Well Data Server

3rd partyDB

3rd party Well Data Server

GeologRDBMS

Geolog

Geolog Well Data Server

Paradigm posApplications

3rd party applications

posWITSML

Link

3rd PartyWITSML

3rd PartyWITSML

Page 15: Paradigm and WITSML 29 th April 2004 John Turvill

Geosteering SolutionGeneral Workflow

Well DataWell DataServerServer

DirectorGeo

Planned wellpathProjected wellpath

VoxelGeo

Horizons curtainFaults MD

WITSML

Service Company MWD dataReal-time survey data

Geolog Geosteer

Control Points @ Control Points @ HorizonsHorizons

Inter-horizonsInter-horizons FaultsFaults

Borehole uncertainties

Real-time log displayInteractive editing ofHorizons & Faults TST & Forward modeling

Service Company LWD dataReal-time log data

LWD GR

Modeled GR

Horizon crossHorizon cross--sectionsectionOffset Well

Page 16: Paradigm and WITSML 29 th April 2004 John Turvill

Wellbore Placement Workflows

Real-TimeUpdate

DrillingOptimization

GeosteeringReservoir Placement

Co-visualization

Reservoir Characterization

3DPore

pressure

WellProgram

& Drilling Design

InteractiveWell

Planning

Page 17: Paradigm and WITSML 29 th April 2004 John Turvill

3D Visualization

Page 18: Paradigm and WITSML 29 th April 2004 John Turvill

Synthetics to seismic tie. Variable Density display.

Synthetics Generation and Tie

Page 19: Paradigm and WITSML 29 th April 2004 John Turvill

Paradigm WITSML status

• Current Product – pos WITSML link– WITSML Receiver

– WITSML 1.1 and 1.2– Supports multiple simultaneous subscriptions & datastores– Cross-platform implementation– Tested against multiple vendor servers with

WITSML versions 1.1 and 1.2

Wells/wellbores, Trajectories, Logs and Realtime Objects

Mudlog under construction…

• Committed to full support of WITSML

• Comments– Standards, dialects and communication…..

Page 20: Paradigm and WITSML 29 th April 2004 John Turvill