MultiVendor Data and Application Integration - PowerPoint PPT Presentation

Loading...

PPT – MultiVendor Data and Application Integration PowerPoint presentation | free to download - id: a4889-MGM4N



Loading


The Adobe Flash plugin is needed to view this content

Get the plugin now

View by Category
About This Presentation
Title:

MultiVendor Data and Application Integration

Description:

Dev Kit. JNI. C OSI/OII. Java Server Skeleton (generated from IDL) ... Kit ... Can get a shape with all traces in a measure (covered next) Domain ... – PowerPoint PPT presentation

Number of Views:82
Avg rating:3.0/5.0
Slides: 68
Provided by: Gil151
Learn more at: http://www.posc.org
Category:

less

Write a Comment
User Comments (0)
Transcript and Presenter's Notes

Title: MultiVendor Data and Application Integration


1
Multi-Vendor Data and Application Integration
  • Technical Overview
  • Feb., 2000

2
OpenSpirit Introduction
3
(No Transcript)
4
Base Framework
5
Sub-Surface Data Module
6
CORBA and Distributed Object Framework Background
7
CORBA Background
  • IT Standard Managed by OMG
  • CORBA Architecture
  • ORB
  • CORBA Services
  • CORBA/COM Bridge
  • Convergent with Java Initiatives
  • J2EE interoperability
  • RMI over IIOP
  • Implemented by multiple vendors on many platforms
  • Solaris, IRIX, HP-UX, AIX, Linux, NT, MVS,
    AS-400, MacOS, .
  • Language independent, binding defined for
  • Java
  • C
  • -
  • Currently used in EP by
  • Landmark
  • GeoQuest
  • Paradigm
  • CGG

8
CORBA Data Server
Client Application
PC or UNIX Based
Java or C Client Stubs (generated from IDL)
IIOP

Java Server Skeleton (generated from IDL)
Business Objects
Java Implementation
JDBC
JNI
JNI
C OSI/OII
Dev Kit
Dev Kit
NFS SQLNet
Datastore
  • file based
  • Oracle

9
Object Frameworks
  • An Object framework is a set of objects and
    services designed to work together
  • Frameworks support the rapid construction of
    applications
  • Frameworks are extensible
  • Frameworks utilize consistent design patterns
  • Distributed object frameworks allow components to
    be distributed across a network

10
OpenSpirit Architecture Overview
11
OpenSpirit - A Process View
Client Application (s)

Per User
Shared Servers
  • User Server
  • UserProfile
  • ProjectSet
  • Session

OpenSpirit Launcher
osagent
oad
Notification
Event Gateway
Trading
Notification
Reference Value
Data Servers
Coordinate
Units
Well
Seismic
Interpretation
Data Store Descriptor(s)
Vendor Datastore
Auxiliary Datastore
12
Key Concepts
GUI component to manage ProjectSets, Sessions,
launch data servers, launch GUI utilities, user
apps, and access help/reference information
OSP Launcher
1
1
1..
1
1..
1..
1
1..
ProjectSet
Session
13
ProjectSet
  • Is an arbitrary set of vendor projects
  • Asserts default coordinate system
  • Asserts default units
  • Assign User roles
  • Owner (can delete projectset)
  • Administrator (can add users)
  • User (can read/write)
  • Supplies a federated QueryManager
  • Supplies a federated FactoryFinder
  • Starts data servers on preferred host(s) (set in
    UserProfile)

14
Session
  • Scope for user events
  • Manages life cycle for CORBA objects
  • Default coordinate system (takes precedence over
    ProjectSet)
  • Default units (takes precedence over ProjectSet)
  • Manages WorkingSet (a named collection of data
    objects)
  • Session objects state information stored in ADS
  • May be extended to manage session preferences fro
    client applications

15
UserProfile
  • Asserts user preferences on which hosts to launch
    data servers (per datastore)
  • Allows user to optionally store encrypted
    passwords for GeoFrame projects and UNIX userids
  • May be extended to manage user preferences for
    client applications

16
Trading Service
  • Conforms to OMG spec - no extensions
  • Supports all defined interfaces
  • Persistent
  • Java implementation daemon
  • Supports
  • Defining service types
  • Registering service offerings
  • Look-up of service offerings
  • Service loader utility
  • Java Bean based viewers

17
Notification Service
  • Java implementation
  • Supports event filtering based on extended trader
    constraint language
  • Supports persistent events
  • Supports different QOS
  • Event channels
  • supports fan-in, fan-out
  • can provide filtering
  • Defined event structure
  • origin, scope, name, simple data

18
Coordinate Service
  • CORBA object based service
  • 3 dimensional coordinates
  • Based on a directed graph of systems and
    transforms
  • Provides initial graph of common systems and
    transforms
  • Provides a Factory interface to extend the graph
  • Data servers are responsible for extending the
    graph
  • Data Objects use client assertion design pattern
  • Based on Shell's OOCLDM code

19
Coordinate System Types
  • Geocentric
  • earth centered
  • lacks ellipsoid
  • defined relative to WGS 84
  • Geographic
  • earth centered
  • reference ellipsoid with undulation function
  • derived from geocentric system
  • Map
  • projection of a geographic system
  • SeismicBinGrid
  • represent seismic survey line locations
  • relative to a Map system
  • IJK
  • relates 3d grid indices to SeismicBinGrid system

20
Sample Coordinate Graph
21
Client Assertion Pattern
  • void postWellsOnMap(System cs, Well wells)
  • for (int i 0 i lt wells.length i)
  • Coordinate loc wellsi.getLocation(cs)
  • drawWell(loc.point.x, loc.point.y)

22
Unit Of Measure Service
  • CORBA object based service
  • Conversions based on equation F(x) (A Bx) /
    (C Dx)
  • Units identified by formal acronym
  • Acronyms can be a simple name or an algebraic
    expression containing simple names (ex. ftUs,
    kg2/sec)
  • Over 850 predefined units
  • Provides Declaration interface for client
    specified units
  • Entities use client assertion design pattern
  • Based on Epicentre units

23
Reference Value Service
  • Manages constrained sets of values (Reference
    Value Sets) within an Authority
  • Examples of authorities are EPICENTRE 2.3,
    GeoFrame 3.7, OpenWorks 98, OpenSpirit V2.0, ...
  • Manages unidirectional mappings (Reference Value
    Maps) between sets
  • Used to convert values from one authority to
    another (e.g. an OpenWorks well bore status to a
    GeoFrame well bore status)
  • Sets, Maps, and Authorities are extensible.

24
OpenSpirit Sub-Surface Data ModuleData Models
25
Data Models
  • Wells
  • Wells, Bores, Picks, Log Traces and Time-Depth
    Tables
  • Support for diverse depth values and horizontal/
    upturned wells
  • Seismic
  • Post Stack 2D and 3D, Seismic Geometry 2D and 3D
  • Interpretation
  • Earth Models, Features and Representations
  • Horizons (Events) and Horizon Properties
  • Faults

26
Well Structure
WellBoreList
Well
0..n
0..1
0..n
0..n
WellBore
Project
0..1
0..1
0..1
0..1
0..n
0..n
0..n
WellLogTrace
WellPick
WellVelocity
27
EpiProjectProject
  • Provides descriptive information about a project
  • name, description
  • Project extent (min, max bounds of the project)
  • Preferred coordinate systems

28
EpiWellWell
  • Identifying information for a single well head.
  • Can have multiple bores.
  • Depends on the underlying data store.
  • Includes
  • identifier, aliases
  • location
  • country, county, currentOperator, field,
    platformIdentifier, spudDate, wellStatus
  • stateOrProvince, waterDepth

29
EpiWellWellBoreList
  • Just a named container for well bores
  • Limits loading in a convenient way
  • Equivalent to the Landmark well list concept
  • Equivalent to GeoFrames collections
  • Includes
  • name
  • dataSource Interpreter in Landmark.

30
EpiWelllWellBore
  • Identifier and summary information on a single
    bore.
  • identifier, boreAliases, boreStatus,
    completionDate, flowDirection, fluidType,
    showType
  • Path which represents the borehole geometry.
  • Regional coordinate systems (datum coordinates)
  • Access to logs, picks, well velocities (T/Z
    pairs).
  • Depth conversion methods (MD, TVD, Time)

31
EpiWellWellVelocity
  • Defines a set of time/depth values used to
    convert time to depth or depth to time.
  • Calculate interval and effective velocities.

32
EpiWellWellLogTrace
  • Contains the amplitudes (trace) and index data
    for a digital well log trace.
  • Sampling may be regular or irregular.
  • Can have one (scalar) measurement at each point,
    or a vector of measurements of simple data types.

33
EpiWellWellLogTrace II
  • The sampling point (called the index) can be
    obtained as
  • Measured depth
  • True Vertical Depth
  • Subsea Depth
  • One-way time
  • Two-way time

34
WellLogTrace Properties
  • Identifying, descriptive text
  • traceName, traceVersion, traceKind, comment,
    dataSource, softSource, user (creator)
  • Descriptions of the data
  • max/minTraceValue, nullValue, traceType
  • numElement, numSamples
  • traceUnit
  • traceProcess

35
EpiWellWellPick
  • A name/measured depth pair, with extra
    information
  • pickName
  • interpreter, pickDate, pickSource, pickColor,
  • pickValue, dipAngle, dipAzimuth
  • confFactor, pickType

36
Seismic Model
SeismicGeometrySet
0..1
Clients use this to create SampledData
representations.
0..n
SeismicDataSet
SeismicGeometry
0..n
1
SeismicGeometry2d
SeismicGeometry3d
PostStack2d
PostStack3d
1..n
Shape
37
Seismic Model II
  • SeismicDataset contains the sample data.
  • Amplitude, phase, etc.
  • PostStack3d is a 3d, gridded dataset.
  • SeismicGeometry describes grid orientation
    spacing.
  • Useful for a collection of SeismicDatasets with
    same geometry.
  • All associated SeismicDatasets share a single
    coordinate system.

38
Seismic Model III
  • Accessors
  • PostStack3d Point samples, traces, planes
    (slices), sub-volumes
  • PostStack2d Point samples, traces, sub-plane, or
  • Can get a shape with all traces in a measure
    (covered next)

39
Domain versus Representation
  • It is often useful to represent the same domain
    elements several ways, mathematically.
  • Seismic datasets
  • Earth model elements (faults, horizons, etc.)
  • Representations can include
  • point sets, poly-lines (irregularly-sampled)
  • n-dimensional grids
  • trimeshes

40
Sampled Data
  • Representation part of a Domain-Representation
    split.
  • Defines a lattice within which we define
    measures.
  • Lattice examples Grids (1,2,3d), PointSet,
    PolyLine, Trimesh (not implemented)
  • Measure examples Point locations (Geometry
    Measure), feature thickness, amplitude, phase
  • Used by Interpretation objects Seismic 2D.
  • Also Seismic 3D and Well in future.

41
Sampled Data Structure
0..n
0..n
Shape
1
1..n
Lattice
Measure
1
0..n
ltltcreatesgtgt
Grid
Mesh
ltltcreatesgtgt
Iterator
1
ltltcreatesgtgt
MeshEditor
1
ltltusesgtgt
IndicatorSet
Designator
GridVertexIterator
PolyVertexEditor
ltltusesgtgt
GridIndicatorSet
PolyEdgeEditor
MeasureValues
ltltcreatesgtgt means get factory from the head
class, then use create method to create tail class
42
Trimesh Example - Lattice
5
11
4
Not Implemented!
15
12
Vertices (cell-degree 0) 1,2,3,4,5 Edges
(cell-degree 1) 6 1-2 7 2-3 8 3-1 9
3-4 10 4-1 11 4-5 12 5-1 Faces (cell-degree
2) 13 6-7-8 14 8-9-10 15 10-11-12
10
9
14
1
Indicator
8
13
3
6
7
2
43
Example Measures
90.5
89.4
(132, 27, 210)
(73, 189, 126)
87.2
(203, 141, 47)
Whats missing?
88.9
88.9
44
Measure Attributes!
  • unitOrCoordinateSystem
  • cellDegree
  • elementSize
  • numericType
  • measureKindName
  • nullValue

45
The Geometry Measure
(19.038, 32.357, 7.782)
(20.392, 32.041, 7.622)
(20.142, 31.832, 7.233)
(20.445, 30.910, 7.461)
(19.939, 30.081, 7.535)
46
Sampled Data Capabilities
  • Defined Lattice types N-dimensional Grid,
    PolyLine PointSet (both Meshes).
  • Edit Lattice with an Editor
  • Can only create one a lock mechanism.
  • Can implement smart Designators that optimize
    access to the measures.

47
Interpretation Model
  • Interpretation Deriving a simple, plausible
    geologic model that is compatible with observed
    data. The model is never unique and discovering
    it involves a sequence of somewhat arbitrary
    choices.Encyclopedic Dictionary of Exploration
    Geophysics Robert E. Sheriff, 3rd ed.

48
Interpretation Model
  • For the model we need
  • Mathematical representation of form properties.
    (Sampled Data)
  • Geologic description
  • Display characteristics

49
Feature
Based on Epicenter V2.2
ArtificialFeature
RockFeature
FeatureBoundary
Horizon
Interval
Geobody
GeologicFault
50
Representing Features
  • A feature may have several representations due to
  • Discontiguous parts
  • Different origins (2/3d seismic, magnetic
    surveys, well logs, calculations)
  • Different dimensionalities (surface, pick)
  • A feature may be interpreted several ways (never
    unique)
  • Different interpreters
  • Different modeling scenarios
  • Different modeling times (4D)
  • Different computational elements/algorithms

51
EarthModelParts Representations
EarthModelPart
VersionName
EMPElementId
0..
1
1
0..
Representation
Feature
propOrigin repKind
Shape
52
Earth Model Parts
  • EarthModelParts gather consistent Representations
    of a single feature (not enforced.)
  • Can have a designated Representation that covers
    whole Feature.
  • Other Representations assumed to be partial.

53
Representations
  • Contains extra information about the Sampled Data
    representationrepKind Curve or
    SurfacepropOrigin NVP sequence
  • propOrigin contains very specific information
    about the data on which interpretation is based.

54
Finally, The Earth Model
  • Gathers consistent EMPs into a model of a region.

EarthModel
LastUpdate Name Version
0..
0..
EarthModelPart
55
A Simple Example Client Application
56
Well Example Application
orb.Factory
util.Session
session
projectSet
queryParams
qresult
enitities
well
WellModel
wellBore
wellPick
B
C
example Java source code
57
Extensions to OpenSpirit
58
Plans for Future Extensions
  • Sub-Surface Data Module
  • 2D interpretation
  • Trimesh representation
  • Well zone models
  • COM Option
  • Preliminary investigation of options
  • Prototyping of solutions in Q1
  • Drilling Data Module
  • Plan to begin forming cross company
    requirements/specification workgroup in Jan.
  • 2-3 month requirement/specification effort
  • 6 month implementation/testing
  • Shared Earth Model Services
  • Elf, Chevron, Tsurf, Prism, GeoQuest, Shell?,
  • Collaborative pre-commercial prototyping
  • Prism will look for opportunity to commercial
    appropriate results
  • Production Data Module
  • Timing based on customer demand and resource
    availability

59
Third Party Extensions to OpenSpirit
  • V2 architected to provide extensibility
  • New attributes/methods on existing objects
  • New Objects (in existing servers)
  • Linkage to new datastores
  • Source code and documentation will be provided
    for example extensions

60
Uses of OpenSpirit
61
Types of OpenSpirit Integration
Vendor D
OpenSpirit Enabled Application Vendor C
Applications can work with any OpenSpirit
supported datastore
OpenSpirit Enabled Applications

Base Framework
Sub-Surface Data Servers
Persistent Store
Event Gateway
Datastore Source-Sinks
Data and events available to any OpenSpirit
enabled application
Vendor A
Vendor A
Vendor B
Vendor B
62
Cross Platform Workflow
GENIE
Open Sesame
PC or UNIX Based
Petrophysical Analysis Modules

Base Framework
Sub-Surface Data Servers
Data Management
UNIX Based
OpenWorks
Finder
GeoFrame
63
Data Transfer using OpenSpirit
Data transfer application
Read data in desired units, coordinates, and
reference-value set
Create objects and then commit

Sub-Surface Data Server 1
Sub-Surface Data Server 2
Persistent Store 1
Persistent Store 2
DataStore 2
DataStore 1
64
Summary - Benefits
  • Developer Benefits
  • Uniform access to data independent of datastore
    -write once
  • Data supplied in desired coordinate system and
    units
  • Quicker time to market
  • Concentrate on value added
  • User Benefits
  • No need to reformat and duplicate data
  • Simultaneous access to data in-place
  • Sharing of user actions
  • cursor location
  • object selection
  • Use diverse applications to form virtual
    application

65
OpenSpirit v2 Whats new from v1
66
OpenSpirit v2 New Features
  • Base Framework
  • Project Set
  • A set of vendor projects used in a session and
    sharing events
  • Persistence
  • Non committed objects stored between sessions
  • Clients may reuse object references
  • Generalized Data Representation
  • Common means of representing 1D, 2D, 3D, arrays,
    trimesh, etc
  • Facilitates use of common visualization and
    processing components

67
OpenSpirit v2 New Features
  • Sub-Surface Module
  • All servers redesigned to provide greater
    extensibility
  • Enhance an existing object
  • Add a new object
  • Support an additional datastore
  • Interpretation Server
  • Basic Earth Model, Horizons, Horizon Properties,
    and Faults
  • Versions for SeisWorks, IESX, and Charisma
  • Seismic Server
  • 2D Post Stack
  • Versions for SeisWorks, IESX, and Charisma
  • Easily extensible to support additional
    datastores
  • Well Server
  • Time-date stamps added
  • Support for array logging tools
About PowerShow.com