1 / 8

Standards in Seabed Data Modeling Overview for POSC

Standards in Seabed Data Modeling Overview for POSC. Jay Hollingsworth ( 郝灵傑 ) – Principal Data Architect November 2 nd , 2005. Seabed. New generation SIS E&P standard data model Common logical model for all scales Configurable databases generated from logical model

russ
Télécharger la présentation

Standards in Seabed Data Modeling Overview for POSC

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Standards in Seabed Data Modeling Overview for POSC Jay Hollingsworth (郝灵傑 ) – Principal Data Architect November 2nd, 2005

  2. Seabed • New generation SIS E&P standard data model • Common logical model for all scales • Configurable databases generated from logical model • Common data services in the database • Is already deployed with some products

  3. Seabed rationale • Technology update • Take advantage of new technologies - ORACLE 9/10, OOAD/OOM, etc… • Customer technology requirements – e.g., ESRI, LDAP, SQLServer • Replace aging infrastructure - AIX, ORACLE 7, 8 • Clients require an information management solution (e.g., for Petrel) • Managing cost of ownership • Resolving the legacy IM product issue • Resolving the acquisitions issue • SLB real-time/operational solutions • Open database without proprietary API

  4. Seabed - why a new data model? • Customers need the best characteristics of all models • breadth • descriptions • content • without the disadvantages • Epicentre • PPDM • OpenSpirit

  5. Data modeling approach • Derive from the best • Standards (POSC, PPDM, WITSML) • De facto standards (OpenSpirit, PIDD) • Common E&P applications • Modified object modeling style • Leverages experience with Epicentre • UML 1.5 with relational extensions • Consider mappability • Apply a single standard for names, etc.

  6. Object Object Object Object Object Object Class Class Class Class Class Table Table Table Table Object vs. Relational Object world Seabed logical model - UML Seabed physical schema

  7. Data model benefits • Modular by domains • Modular by levels of detail • Include specific functions • Activity history (Sarbanes/Oxley-style) tracking • Uncertainty • Integration of documents • Mappability

  8. Questions?

More Related