PROFESSIONAL PETROLEUM
DATA MANAGEMENT ASSOCIATION
Introduction to PPDM 3.9
To be released late 2011
PPDM 3.9 IS ROBUST
Facilities Records
Land Rights & HSE And Media
Contracts
Partnerships
Financial
Data
Production &
Wells & Mgmt
Reserves
Geology
Geophysics
Samples & Support
Analysis Modules
Stratigraphy
WORKGROUP PROCESS
WORKGROUP
PROCESS
MODEL DESIGN OBJECTIVES
Main design focus is on business driven requirements
• How does the data represent the business?
- Based on business requirements collected by workgroups
- Not IT requirements!
• PPDM is not designed for a specific application
Key objectives
• Support best data management practices
• Keep the model as easy to understand as possible
- Some business knowledge is critical!
• Allow users to implement a subset of the data model
- Control the spaghetti effect
• Allow users to manage data as the business requires through the life cycle
(all the detail)
• Support a few important business variations (not everyone has the same
business requirements)
PPDM 3.9 IN DEVELOPMENT
RELEASE PLANNED FOR 2011
50000
Tables
45000 2000
1800
1600
40000 1400
1200
1000
35000 800
600
400
30000 200
0
Tables
25000 Columns
Constraints
20000
15000
10000
5000
0
PPDM 2.0 PPDM 3.2 PPDM 3.3 PPDM 3.4 PPDM 3.5 PPDM 3.6 PPDM 3.7 PPDM 3.8 PPDM 3.9 DEV
PPDM MODEL DELIVERABLES
Sample data
Data Model Definitions (DDL)
• Insert statements
• Oracle
• Oracle dmp
• SQL*Server
• “load of the rings”
• MySQL
• PostGRES Queries
Documentation
• Roadmaps
• Online documentation
• Printable documentation
• Data diagrams
• Architectural Principles
• Reference guides
• Sample data
• Wiki entries
MULTIPLE SCHEMA LAYERS
Add Spatial Extensions
Make PPDM_GUID “Not Null”, add unique index
Add UOM and OUOM / ROW QUALITY Constraints
Table Synonyms
Table Comments Column Comments
Primary Foreign Check
Tables Columns
Keys Keys Constraints
PPDM Compliance measure
PPDM 3.9 STATUS
Physical model is mostly complete
PPDM 3.9 alpha being prepared for release
Change management process is starting
Revisions to the Architectural Principles is underway
Release is planned for 2011
9 Copyright 2010, PPDM Association. All Rights Reserved
PROFESSIONAL PETROLEUM
DATA MANAGEMENT ASSOCIATION
Some Key Changes
GEOCHEMISTRY KEY REQUIREMENTS
Keep track of samples
Know what has been done to the sample(s)
Track the measurements from analysis
Validate the information
Integrate information from many sources!
Good data management
Better integration of Products & Substances
11
GEOCHEMISTRY LOGICAL MODEL
12 Copyright 2010, PPDM Association. All Rights Reserved
PRIMARY KEYS
What is the function of a Primary Key?
• Uniquely identify a row in a table
• Uniquely identify an object
• Synchronize master/child ..
What is the structure of a Primary Key?
• Natural vs surrogate
• Integer vs character
• GUID vs random vs concatenated vs license plate…
Should they cascade or not?
IMPLEMENT WIAW CONCEPTS
1. Avoid highly 4. Allow components to
destructive be fully described
changes
5. Distinguish
between
completions (n)
and completions
(v)
3. Keep the RI structure
as simple as possible
2. Don’t assume the user 6. Don’t require a
knows which mandatory hierarchy to
component type is be built. Create and
created relate only the
components you know
about for sure.
PRODUCTS AND SUBSTANCES
DEVIATION FROM SQL*92 RI
• PPDM GUID has been very well accepted.
• Use of the PPDM Data Management module is very strong.
• Can we carry these concepts into some of the heavy RI /
complicated tables, such as the COMPONENT tables?
DIRECTIONAL
SURVEYS
IMPLEMENTATION SUPPORT
Consistency
• Terminology
• Method of implementation
• Normalization vs denormalization
Implementation assists
• API?
• More documentation?
• More rigor in compliance?
PROFESSIONAL PETROLEUM
DATA MANAGEMENT ASSOCIATION
Thank you
Any questions?
