OpenSpirit Overview

1
OpenSpirit Overview

• Steve Jennis
• PrismTech Corporation
• Houston, TX

2
OpenSpirit OverviewPOSC Workshop 4/23/98

• 08.40 Introduction and Overview PrismTech
• 09.20 An Oilco sponsors view Chevron
• 09.40 A vendors sponsors view CGG
  Petrosystems
• 10.00 OpenSpirit Technical Overview PrismTech
  
• 10.30 QA Panel All
• 10.40 Close

3
OpenSpirit Overview1995 Quotations

• The single most effective countermeasure that can
  be taken to reduce the pains of constant change
  is to let applications and their enabling
  technology change independently from one another
• Gartner Group
• Rapid application development sounds good. But
  it doesnt quite hack it. You need rapid,
  adaptable applications, because life changes
  after an application has been delivered
• OVUM
• Organizations need to adopt a layering
  approach to software, and try to separate out
  what is of value to the business from what is
  essentially supporting technology
• Butler Group

4
The OpenSpiritInitiative

• Alliance Sponsors
• Shell, Elf, Chevron, STATOIL, BG, CGG
  Petrosystems, IBM, Shared Earth, Jason,
  deGroot-Bril, Foster Findlay
• Developers and Marketers
• PrismTech Corporation

5
The OpenSpiritInitiative

• Alliance Sponsor Role
• Cash and/or personnel and/or IP contribution to
  design and development effort
• Use-case scenarios
• Technical expertise and advice
• Early adopter market
• Promote take-up
• Support POSC standardization effort

6
The OpenSpiritInitiative

• PrismTech Role
• Software development and ownership
• Project management
• Marketing
• Support and maintenance
• Application-vendor neutrality
• Sponsor credits
• Support POSC standardization effort

7
The OpenSpiritInitiative

• Project Organization
• Project Steering Group
• Execution Team
• Design Authority Team
• Marketing Committee
• Quarterly meetings and deliverables

8
The OpenSpiritInitiative

• Project Metrics
• 11 sponsors (currently)
• Approximately 45 man-years of development
• 6 organizations contributing resources
• Potential market of 1500 developers
• Potential market of 15000 users
• Special interest group 50 members (goal)

9
The OpenSpiritInitiative

• Project Deliverables
• OpenSpirit Development Environment(s)
• OpenSpirit Run-time Environment(s)
• Commercial OpenSpirit-based applications
• (from sponsors, not PrismTech)
• POSC RFT response
• Marketing activities
• OpenSpirit Special Interest Group

10
The OpenSpiritInitiative

• Project Timing
• Development commenced July 1997
• First deliverables (internal) Nov 1997
• SEG announcement Nov 1997
• Application development commences May 1998
• AAPG May 1998
• EAGE Jun 1998
• SEG demonstrations Sept 1998
• V1 beta Nov 1998

11
The OpenSpirit EP Component Framework

• PrismTechs Motivation
• and Plans

12
The OpenSpirit EP Component FrameworkPrismTech
Corporation

• Alliance development and marketing partner
• Leaders in technical data management (including
  data warehousing) and application
  interoperability
• Strongly committed to standards (OMG, POSC,
  ISO/STEP)
• Vendors of business object frameworks, OO and
  data access middleware, technical data management
  and warehousing tools, and related project
  services
• USA and UK offices
• Significant EP and Manufacturing customer base

13
OpenSpirit EP Component FrameworkPrismTechs
Motivation

• To provide the EP industry-standard business
  object framework, that facilitates the
  plug-and-play integration of application
  components and datastores
• To deliver productivity and other benefits to
  ISVs, VARs, SIs, and in-house development teams
• To remain a complementary supplier to application
  developers and datastore providers
• To maximize market size and share
• To make profits and re-invest in extending the
  framework domain coverage

14
OpenSpirit EP Component Framework
15
OpenSpirit EP Component FrameworkWhy
OpenSpirit as the EP industry standard business
object framework?

• It delivers business benefits to end-users,
  application developers and systems integrators
• It is application independent
• It is application vendor neutral
• It is designed to be EP domain independent
• It has an immediate and strong user base
• It utilizes advanced technology and supports
  web-based applications
• It leverages industry standards POSC, OMG, DCOM

16
OpenSpirit EP Component FrameworkTypical Users
and User Benefits

• Application developers (I.S.V.s, EP Technology
  Companies, Consultants)
• Single development environment for cross-platform
  deployment
• Focus on value-added functionality instead of
  infrastructure
• Transparent access to widely-used data-stores
• Higher productivity and faster time to market

• Application end-users (Earth Scientists and
  support personnel)
• Cross-platform and multi-vendor data access
  eliminates re-formatting
• Accessible from Web browsers
• Integration with MS Office applications
  leverages desk-top tools
• Lowers purchase and integration costs of new
  applications

17
OpenSpirit EP Component FrameworkRequirements
from Use-Cases

• Product requirements derived from Use-Cases
• Initial Use-cases provided by Alliance
  participants Shell, Chevron, Elf, STATOIL,
  BGplc, CGG Petrosystems, IBM, Jason, de
  Groot-Brill, etc.
• Use-cases reflect oil company and ISV usage
  scenarios
• Use-cases will be solicited from a wide range of
  ISVs and other developers
• Prime objective of OpenSpirit is to create a
  vendor-neutral industry-standard EP framework.
  Thus Use-cases will span the EP lifecycle.

18
OpenSpirit EP Component Framework
Domain Components
Domain Components
Domain Components
OpenSpirit
Generic EP Components
BOF (CORBA and/or DCOM)
Object Services
Object Request Broker
Operating System and Network Services
19
OpenSpirit EP Component FrameworkIndustry
Standardization

• OpenSpirit will respond to the POSC
  Inter-operability RFT
• OpenSpirit Alliance seeks industry consensus
• RFT workshops are taking place
• Workshop 1 - Chevron Corp., Houston, 23 February
• The OpenSpirit Framework will adopt the POSC
  Standard as soon as possible
• The OpenSpirit Framework intends to be the first
  implementation of POSC business objects

20
OpenSpirit EP Component FrameworkDevelopment
Roadmap

• Framework development underway since July 1997
• First deliverables to Alliance sponsors November
  1997
• Quarterly deliverables throughout project
• Alliance application development starts April
  1998
• OpenSpirit response to POSC Business Objects RFT
  May 1998
• Alliance Application and Framework demonstrations
  SEG September 1998
• OpenSpirit V1 beta November 1998

21
OpenSpirit EP Component FrameworkPromotional
Plans

• SEG97 - Awareness
• Conceptual demonstrations (courtesy of Chevron
  Corporation)
• Poster sites
• Literature data sheet, white-paper, poster
  reprints
• Press release
• Visits to exhibiting ISVs
• OpenSpirit Special Interest Group (OSIG) - 1/98
• AAPG, Utah, May 98 - Awareness
• EAGE, Germany, June 98 - Awareness
• SEG, New Orleans, Sept 98 - Demonstrations
• November 1998 - Version 1 beta release

22
OpenSpirit EP Component FrameworkConceptual
Demonstrations

• Demonstrations kindly provided by Chevron
  Corporation
• Demonstration of key concepts addressed by
  OpenSpirit
• Cross-platform interoperability
• Browser-based Virtual applications
• Heterogeneous data access
• Multi-vendor integration
• Integration with Microsoft Office applications

23
OpenSpirit EP Component FrameworkOpenSpirit SIG

• January 1998 launch - goal 50 ISVs, SIs, VARs
• Precursor of an OpenSpirit User Group
• Deliverables
• Early access to technical documentation IDL,
  architecture, user manuals, etc..
• Technical forums
• Early access to code - Beta program
• Free evaluation license
• Marketing benefits via OpenSpirit Alliance
• Cost
• 1000 per annum