PPDM Lite 1.1 Modules
Application and License
This table captures requests for authorization for an activity.æ Applications may be made for AFE‰s, to regulatory agencies or to partners to conduct operations according to the terms of a contract.æ Includes the type of application made, major dates (submitted and received), the decision and any remarks about the application.
A license is a formal authorization to conduct operations, and is usually granted by a regulatory authority.æ This is a rolled up table that contains a summary of detailed license information from the following tables in PPDM 3.7: BA_LICENSE, FACILITY_LICENSE, SEIS_LICENSE and WELL_LICENSE.æ
The primary key is two part:æ the first part is a unique License ID, which is typically derived from the source table.æ The second is the name of the table in PPDM 3.7 that is the master for the row of data. Allowed values are BA_LICENSE, FACILITY_LICENSE, SEIS_LICENSE and WELL_LICENSE.
Area
An area can be any geographic place, including project areas, organizational areas or environmentally restricted areas.æ High level information about the area type, the preferred name as well as remarks.
L_AREA_ALIAS
Alias table that contains what the area is called and what it could be or is called in other contexts.æ All names, codes and identifiers (including the preferred name) for an area should be stored in this table.æ
Business Associate
A business associate may be any company, agency or person with whom you do business.æ This may be considered to be a contact data base, and would normally be managed from a central corporate database.
L_BA_ADDRESS
The address table contains physical, postal or billing addresses. Companies that have more than one branch may have more than one valid address.
L_BA_ALIAS
Alias tables track all names, codes and identifiers for each business associate. This table allows useful functionality for linking company information between multiple applications, including your financial and billing systems and your geotechnical applications.æ All names, codes and identifiers should be stored in this table, including current and out dated versions.
Contracts
The contract table may be used to reference contracts of any type.æ This is a high level table that contains contract name, status, date and penalty percentages.
L_CONTRACT_COMPONENT
Cross reference table that associates contracts with all the business objects (wells, land rights, seismic data) that the contract relates to.æ
L_CONT_ALIAS
Alias table that is used to track what a contract is called or is to be referenced as by various partners, systems or applications.æ Out dated aliases may also be tracked in this table. All names, codes and identifiers should be stored in this table, including current and out dated versions.
L_CONT_EXTENSION
Most often used for the extension of land right related contracts.æ If the contract was extended, use this table to capture the type of extension, and associated terms of the extension.
Entitlements
Entitlements describe the rights you have to data or information, such as a well, facility, report or area.æ These entitlements may be captured for any business object or table in PPDM Lite 1.0.
L_ENT_GROUP
Use this table to define groups of users or business associates who have a common set of entitlements.æ Often, a group may be departmental, functional or organizational.æ
L_ENT_COMPONENT
Cross reference table that allows specific business objects such as wells or facilities to be associated with a specific set of rights or entitlements.æ
Facility
A facility is a physical construct that is directly associated with the production, management or processing of hydrocarbons.æ A facility may be a pipeline, storage tank, AV unit, separator, valve etc.æ This table contains very general facility data such as operator, type, production date, status and status type.æ
L_FACILITY_SUBSTANCE
This table captures information, varied over time, about what substances a facility is capable of handling and what its average, minimum and maximum capacities are.
L_FACILITY_ALIAS
Alias table that is used to track what a facility is called or is to be referenced as by any business associate or application. All names, codes and identifiers should be stored in this table, including current and out dated versions.
L_FACILITY_XREF
Shows how two facilities are related to each other.æ This table may be used to capture physical connections between facilities, such as connections between pipelines and other pipelines or facilities.
Financial
This table will allow you to associate your PPDM Lite 1.0 implementation with your accounting systems; in this way information about finances may be drawn directly from your accounting system. Defines the type of financial transaction, the budgeted and actual costs, the issue date and if there is a tax credit available for it.
L_FIN_COST_SUMMARY
Allows the capture of multiple costs to a single financial cost centre(AFE).æ Each cost breakdown may be associated with a specific business object or process using the L_FIN_COMPONENT table.
L_FIN_COMPONENT
Use this table to associate the overall finance record or a specific component with a specific business object.
L_FIN_XREF
Use this table to track the relationships between financial systems, cost center numbers, AFE‰s or other financial information.
Field/Pool
High level table of the field name, type, the geographic boundaries it is confined in and the discovery date.
L_FIELD_ALIAS
Alias table that is used to track what a field was called or is to be referenced by.æ All names, codes and identifiers for the field should be stored in this table, including current and out dated versions.
L_POOL
Pool descriptions are usually set by regulatory agencies; this table may be used to define the owning field, related stratigraphic formations and the geographic boundaries.
L_POOL_ALIAS
Alias table that is used to track what a pool was called or is to be referenced by. All names, codes and identifiers should be stored in this table, including current and out dated versions.
Interest Sets
Interest sets, also called partnerships or division of interests, are captured in this table.æ Any kind of interest set may be stored in this table, including working interests, royalty interests, production interests and construction interests.æ Interest sets version over time using the INT SET SEQ NO in the full version of PPDM.æ In PPDM Lite, only the most up to date version of the interest set is stored.
L_INT_SET_PARTNER
Tracks who your partner(s) are, what role each has and what the gross & net interests are.æ As with the interest set, only the most up to date version of partner shares are managed in PPDM Lite 1.0.æ Full information is captured in PPDM 3.7.
L_INT_SET_COMPONENT
This table is used to tie the interest set back to the business objects, such as well, seismic, land (onshore or offshore) and facilities that they govern.
Land
A land right represents the rights you have to a geographic area, whether it is onshore or offshore and whether the rights are owned outright or obtained through contractual or lease arrangements with the owner.æ Land rights may include rights only to the surface or to the subsurface (mineral zones). Header information captured about the land right such as type, status, primary term, cost center are included in this table.
The column LAND RIGHT TYPE is controlled by a check constraint.æ Allowed values correspond to allowed values in PPDM 3.7; the PPDM Association recommends that these values be left as published, so that replication processes are not compromised.æ Allowed values are LAND_TITLE, LAND_AGREEMENT, LAND_AGREE_PART, LAND_UNIT, and LAND_UNIT_TRACT.
L_LAND_ALIAS
Alias table that is used to track what a land right was called or is to be referenced as. All names, codes and identifiers should be stored in this table, including current and out dated versions.
L_LAND_XREF
The relationships between land rights are captured here.æ Typically, these relationships may include associations between a land title and the leases that have been granted on that land, leases and subleases, tracts or splits.
L_LAND_SALE
Land sales capture information about geographic areas (sometimes including stratigraphic or substance definitions) that are made available by offering to the E&P industry.æ Land sale bids may be based on financial offerings, work promises or both. This table captures information such as the opening, closing and sale dates, the jurisdiction offering it and remarks about it.
In a land sale, one or more offerings may be presented for bidding. Each offering may consist of one or more parcels, which may or may not be geographically contiguous.æ Each offering is bid on as a whole, and granted as a whole.ææ
PPDM Meta Data
Captures the database(source) that is the master data store for a table in PPDM Lite 1.0.
L_PPDM_EXCEPTION
This table is used by the data management routines to capture load errors at run time.æ After any data replication is done, this table should be reviewed to ensure that the load was successfully completed.æ
L_PPDM_ORIGIN
Table that tracks the exact row in the master data store that the PPDM Lite data came from.æ As a result of this detail, the table may be quite large.æ It is powerful in that you can drill back very precisely to the place in the master data store where the data came from.
L_PPDM_TABLE
A meta-data table which contains information regarding the tables contained within the PPDM Lite schema.
L_PPDM_COLUMN
Contains meta-data regarding the columns in the PPDM Lite schema.æ This includes data type and primary key information.
Projects
A project is any set of tasks or activities that are managed.æ The project name, type, status and start/completion date are capture here. PPDM 3.7 contains a great deal of information about projects.
L_PROJECT_ALIAS
Alias table that is used to track what a project was called or is to be referenced by. All names, codes and identifiers should be stored in this table, including current and out dated versions.
L_PROJECT_COMPONENT
This table is used to associate the project with the business objects in PPDM Lite 1.0 that are associated with the project.
Production Volumes
A PDEN (Producing entity) can be used to capture production information for a variety of producing objects.æ A PDEN can be categorized as a well, production string, production string completion, pool, field, land right, business associate (such as a partner) or geographic area (such as a county).æ It represents any entity for which production can be reported against.
The column PDEN TYPE is controlled by a check constraint.æ Allowed values correspond to allowed values in PPDM 3.7; the PPDM Association recommends that these values be left as published, so that replication processes are not compromised.æ Allowed values are PDEN_OTHER, PDEN_WELL, PDEN_RESENT_CLASS, PDEN_RESENT, PDEN_PROD_STRING, PDEN_PR_STR_FORM, PDEN_POOL, PDEN_LEASE_UNIT, PDEN_FACILITY, PDEN_FIELD, PDEN_BUSINESS_ASSOC, PDEN_AREA.
L_PDEN_STRAT_UNIT
This table allows a PDEN entity to have multiple stratigraphic units from which it can produce.æ
L_PDEN_XREF
This table tracks PDENs when they are cross-referenced to each other.æ This allows you to capture information about which PDENs are physically connected at the time of reporting, or new PDENs that replace old PDENs.æ
L_PDEN_VOL_SUMMARY
This table allows you to capture volumes that are associated with any activity (sales, flaring, production, injection, loss, fuel use etc) for any time period (monthly, yearly) and for any method (estimated, actual, forecast).
Note that while PPDM 3.7 supports the management of amended volumes, PPDM Lite 1.0 will capture only the most current reported production volumes.æ Amendment histories should be stored in your full version of PPDM 3.7.æ Volumes for the most commonly reported substances are captured in this table, including oil, gas, sulphur, water, BOE, CO2 and Nitrogen.æ
Records Management
The records management module is used to capture information about products and how they are managed.æ Although unstructured documents such as reports and images are the most commonly managed in this module, other products such as equipment and fossils may also be managed.æ The L_RM_INFORMATION_ITEM table captures details about the information contained in a product š specifically, what the product is in business terms.æ
This table captures information such as the name of the item, the kind of item it is, the media that it is stored on (tape, film, paper etc) and who the authors are.æ
The column INFO ITEM TYPE is controlled by a check constraint.æ Allowed values correspond to allowed values in PPDM 3.7; the PPDM Association recommends that these values be left as published, so that replication processes are not compromised.æ Allowed values are .
L_RM_INFO_ITEM_CONTENT
This table will capture information about the business objects that are related to a product, such as the wells, seismic sets, facilities, production reports and so on.
L_RM_INFO_ITEM_DESC
This table is very vertical in nature, and will allow any descriptive information to be captured for a product.æ Captures any detailed description data about the record.
Reserves
A reserve entity represents any single producing well (or well completion or string) or group of wells that are used to determine reserves.æ Stores the product type, created by and update schedule for the reserves analysis.æ Each reserve entity is qualified by the primary product being produced.
L_RESENT_CLASS
For each reserve entity, reserve estimates may be defined as categorized by the reserve classes (proven, unproved, developed, undeveloped etc).æ For each reserve entity, captures the confidence factor (90 % probable reserves) and effective date of a reserve estimate.
L_RESENT_COMPONENT
This table associates the reserve entity with all the wells, production strings and production string formations that are part of the reserve entity.
L_RESENT_XREF
This table may be used to define the relationships between reserve entities, usually when one replaces another.
Seismic
A seismic set represents a set of seismic data, either an entire survey (sometimes called a project or prospect) or a seismic line.æ PPDM 3.7 defines several additional types of seismic sets that are not supported in PPDM Lite 1.0.æ
This table tracks the first & last point in a seismic set, the type of seismic set) controlled by a check constraint), the political jurisdiction that it was shot in and a tie to the Finance module.
The column SEIS SET TYPE is controlled by a check constraint.æ Allowed values correspond to allowed values in PPDM 3.7; the PPDM Association recommends that these values be left as published, so that replication processes are not compromised.æ Allowed values are SEIS_INTERP_SET, SEIS_3D, SEIS_SET_PLAN, SEIS_PROC_SET, SEIS_LINE, SEIS_ACQTN_SURVEY, SEIS_WELL, SEIS_SEGMENT.
L_SEIS_ALIAS
Alias table that is used to track what a seismic set was called or is to be referenced by. All versions of names, codes and identifiers should be loaded in this table.
L_SEIS_POINT
This table captures the name and location of individual points on a seismic set.æ These points may exist on the surface (field data, as shots, receivers or both) or in the subsurface (CDP data).
L_SEIS_RECORD
This table contains information about every record created for every shot on a seismic line.æ The quality of each resulting record may be tracked.æ The potential size of this table could be very large; considerable care should be exercised for implementation.
Spatial
This is the main driving table for the spatial component in PPDM Lite 1.0.æ This table contains summary information about the type of geometry that has been captured, the coordinate systems used and other important spatial reference information.æ
L_SP_BOUNDARY
This table contains the points which outline the perimeter of a polygon.æ The points must be sequenced spatially in either a clockwise or counter clockwise direction, using the value specified in L_SP_POLYGON.
L_CS_COORDINATE_SYSTEM
This table contains basic reference information about the coordinate systems referenced by spatial data.æ It contains a summary of much more detailed data in PPDM 3.7:æ
L_SP_COMPONENT
This table is used to identify the business objects that are defined by this spatial description.æ The relationship supports the business rules that an object may have one or more spatial descriptions and that a spatial description may describe one or more business objects.æ It would be common for example, for a land right and a contract to be described using the same spatial description.
L_SP_GEOMETRY
This table provides a method for spatially enabling descriptions through association with appropriate geometries in a spatial engine such as SDE.
L_SP_LINE
This table stores line data.æ A line can be described as the linear extent of a spatial object such as a road, pipeline or transmission line.
L_SP_LINE_POINT
This table contains the points along a line.
L_SP_MINERAL_ZONE
Definition of the subsurface stratigraphic zone(s) included in the spatial description. This is important for many types of land rights, in which rights are granted to specific (and well defined) stratigraphic zones and often to specific substances in each zone.æ
L_SP_POINT
The location of a point geometry.
L_SP_POLYGON
A polygon is defined as the outline of an area and this table stores this information.æ Polygons may describe outlines of fields, pools, AOI agreements, land titles, land parcel lots, surface restrictions and others within PPDM Lite 1.0.
L_SP_ZONE_SUBSTANCE
Describes substances (and their related zone) which are specifically included or excluded from the spatial description.æ For example, land rights may be granted from surface to basement, except for gas inæ Zone A.
Support Facility
A support facility provides operational support for activities.æ These facilities may include roads, transmission towers, airstrips, vessels, docks and so on.æ Sub types are used to fully describe each type of support facility.
L_SF_COMPONENT
This table is used to track relationships between support facilities of all types and other business objects.
L_SF_XREF
This table is used to capture physical or business relationships between support facilities.
L_SF_DESCRIPTION
This generic table may be used to track descriptive information about support facilities.æ
L_SF_ALIAS
Support facilities may have more than one name, code or identifier.æ All versions, including the preferred version, should be stored here.
Stratigraphy
A stratigraphic name set is an unordered collection ofæ stratigraphic units, that may be in use for a geographic area, a project, a company etc.
L_STRAT_UNIT
A stratigraphic unit may be lithologic (a body of rock), chronostratigraphic (defined based on time), an event (unconformity, fault, thrust sheet) or other type of stratigraphy.æ It is most commonly used for lithostratigraphic units.æ
Well
A table for general and header information about a well.æ A well is an actual or proposed hole in the ground, designed to exchange fluids between a subsurface reservoir and the surface (or another reservoir) or to enable the detection and measurement of rock properties.æ A wellbore is a cylindrical hole created by a drill.æ A well may consist of zero, one, or more wellbores; their relationships are described by PARENT_UWI and WELL_RELATIONSHIP.æ Information from other well tables (e.g. key dates and depths) may be included (or de-normalized) for convenience.æ The term "well" is used in the column name and comments to mean "well", "wellbore", either, or both (depending on context)..
L_WELL_ALIAS
The Well Alias table contains names and identifiers that a well may otherwise be known as.æ This would include previous or alternate well identifiers assigned to the well by a regulatory agency and the reason for the alias.
L_WELL_SERVICE
This is a rollup table that stores the type of service (core, DST, perf, etc), the date run, the top and base depth and the top and base stratigraphic unit.æ This table is populated from almost all of the well tables in PPDM 3.7 that have a foreign key from the WELL table.æ
L_STRAT_WELL_SECTION
This table contains information on well tops. This includes pick (positional) data on formations, markers, contacts and horizons thatæ can be correlated from well to well within a geographic area.