90 likes | 361 Views
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
E N D
Standards in Seabed Data Modeling Overview for POSC Jay Hollingsworth (郝灵傑 ) – Principal Data Architect November 2nd, 2005
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
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
Seabed - why a new data model? • Customers need the best characteristics of all models • breadth • descriptions • content • without the disadvantages • Epicentre • PPDM • OpenSpirit
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.
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
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