Data Model - Overview

This documentation captures the data model that is implemented in the DecisionSpace 365 Production Data Management. This documentation is live - we are actively adding and extending the data model, and the additions will be documented here.

PDM365 data model is relational data model. PDM application supports Postgres and SQL Server 2 kinds of data base.

We prioritize performance and extensibility when designing the data model.

Performance means being fast. The data model should NOT be too excessive and complicated to the point that it slows down processes and queries, but still structured enough for fast indexing.

Extensibility means that the PDM365 data model provides a core definition that can be extended in a maintainable and sustainable way, over the life of the field. We are aware that trying to define all possible entities and attributes throughout many kinds of assets and operations is a never-ending quest. With the PDM365 data model and application, new entities and attributes can be added and maintained out-of-the-box.

The standards that we consider and examine when defining the data model structure are:

For entity definition, table names, and attribute definitions and constraints, we adhere to PPDM definition with minor modifications.

For example, we follow PPDM definition to use Pool and its definition (POOL: Represents a reservoir or a group of small tracts of land brought together for the granting of a well permit under applicable spacing rules). However, we also modify it into ``Pool/Reservoir'' as display name in PDM application because the”Pool” terminology is not widely used outside North America.

PPDM has developed the industry standard and an extensive guideline on petroleum data model definition since 1988. OSDU is the new industry initiative led by supermajors (BP, Chevron, Total, among others) to develop a standard data platform for the oil and gas industry, which will reduce silos and put data at the center of the subsurface community. PRODML is a set of standards for optimizing producing oil and gas wells, with a focus on data from the reservoir-wellbore boundary to the custody transfer point.

When developing PDM core data model, we examine PPDM 3.9 standard closely. We adhere to their entity definitions, table names, attribute definitions, and attribute constraints. However, we rethink the approach of the highly normalized table structure that comes with the standard, to ensure performance and extensibility taking priority over completeness/complexity. We seek to simplify the data structure and tables, reduce data redundancy and ensure consistency.

The PPDM3.9 is on PPDM website (membership required). The PDF version is available for v3.8.

On OSDU, we are closely monitoring the progress of the data modeling. It’s important to note that OSDU data definition is still under iteration. In the year 2021, OSDU defined the volume, well test and downtime event, and PDM refers to the standard and extend the data model.

On PRODML, we also examine the data transfer standard they defines. Especially in reporting volume and flow model module, PDM aligns the PRODML standards very closely.

PDM data model has covered the data definition of the use cases those the production optimization analysis features needed and as following:

Meanwhile, the data model provides the following advantages,