Name | Rock_Pty_Set |
---|---|
Entity Type | Table |
Description | A set of general rock properties. |
Submodel | Well_Marker |
Entity Scope | Project |
Primary Key | Id |
Natural Key | Rock_Pty_Zone_Id , Measurement_Date , Source , Existence_Kind , Version |
Generalizations | Entity , IT_Object , Tracked_Object |
Specializations |
Name | Value Domain | Property / Storage Unit | Description | Required / Default | Type |
---|---|---|---|---|---|
Avg_Deep_Resistivity | double | Resistivity ohm.m |
The average value for deep resistivity in this zone. | No |
NUMBER |
Existence_Kind | REF_EXISTENCE_KIND | NA |
A reference value that describes the state of existence in the lifecycle of the entity, for example, Planned, Predicted, Required, Simulated, and Actual. | Yes Actual |
VARCHAR2(64) |
GUID | STRING128 | NA |
Globally Unique IDentifier for an instance of a class. USAGE NOTES: There are two cases: 1) GUID is not populated or used; and 2) it is populated with a value that is globally unique. If the GUID is populated there are two means of doing so for a given project: 2a) Seabed automatically generates and populates the GUID when an instance is created (valid only on Oracle based systems); and 2b) the GUID is generated and populated by an application (other than Seabed) on instance creation. Whether Seabed automatically generates GUIDs for a project is determined by the Auto_GUID flag in SDS_Account. Note that techniques 2a and 2b can coexist in the same project. When GUIDs are automatically generated an application can override the automatically generated GUID with its own GUID by simply supplying the GUID value. Applications that generate their own GUIDs and populate the GUID column will function correctly on projects which have automatic GUID generation turned on. | No |
VARCHAR2(128) |
Gross_Sand | double | Length m |
The gross thickness of reservoir lithology not accounting for reservoir quality. | No |
NUMBER |
Id | ID | No_Unit |
Unique identifier for this entity. | Yes |
NUMBER(38) |
Insert_Date | DATE | NA |
Date the entity was created in the repository | No |
DATE |
Insert_User | STRING64 | NA |
The name of the user responsible for the creation of this entity in the repository. | No |
VARCHAR2(64) |
Litho_Zone_Desc | STRING64 | NA |
A borehole zone may encompass many different lithologies. Litho_Zone_Desc provides a description of the entire set of encountered rock types across the zone. It may be a list or a short narrative on how the lithologies relate. Typical entries include values like, Sand Shale Sand, Interlaminated sands and shales, Shaly sands and Sandy shales, etc. A more complete description of the breakdown of individual components is found in Litho_Zone_Fraction for this zone. | No |
VARCHAR2(64) |
Measurement_Date | DATE | NA |
The date and time when the measurement activity for this set of properties occurred. | No |
DATE |
Measuring_Activity_Id | Generic_Activity |
|
The activity that recorded the rock properties | No |
NUMBER(38) |
Name | ENTITY_NAME | NA |
The name given to any object or data item, e.g. name of Well, name of Field, etc. | No |
VARCHAR2(255) |
Net_Sand | double | Length m |
The net thickness of reservoir lithology including only intervals with reservoir quality. | No |
NUMBER |
Original_Source | STRING64 | NA |
The name of the person, Organization or project source that originally provided this entity, e.g. "IHS-EnergyData" or "FinderUpper Stratton Deeper Pool 15" | No |
VARCHAR2(64) |
Permeability | double | Permeability mD |
The permeability of the rock | No |
NUMBER |
Permeability_Height | double | Integrated_Permeability mD.m |
The product of the permeability and the length of the permeable section across the zone. This value is often called Kh. | No |
NUMBER |
Porosity | double | Porosity m3/m3 |
The porosity of the rock | No |
NUMBER |
Produced_By | STRING64 | NA |
The name of application role that created the entity, for data created programmatically. | No |
VARCHAR2(64) |
Remarks | STRING2000 | NA |
Any type of remarks added to an entity instance. | No |
VARCHAR2(2000) |
Rock_Pty_Zone_Id | Borehole_Zone |
|
The zone, from top to bottom, that defines the limits of the general properties in this borehole. | Yes |
NUMBER(38) |
SDAT_Label | int | No_Unit |
Label used by the security system for entitlements. SDAT is Secure Data Access Technology. | No |
NUMBER(10) |
Source | STRING64 | NA |
Name of the person or organization responsible for this entitys E and P content and quality. Not the data technologist or IT expert creating the entity, for which see IT_Object.Insert_User and Update_User. | No |
VARCHAR2(64) |
Update_Date | DATE | NA |
Date of the most-recent modification to the entity. | No |
DATE |
Update_User | STRING64 | NA |
The name of the user responsible for the last modification to this entity. | No |
VARCHAR2(64) |
Version | STRING255 | NA |
The form or variant of the entity. | Yes 1 |
VARCHAR2(255) |
Zone_Interval_Porosity | R_Porosity |
|
A value that represents the predominant porosity type of the borehole zone. Examples include Intergranular, Fenestral, Fracture. | No |
VARCHAR2(64) |
From Entity | Link | Description | Implementation Technique | Required |
---|---|---|---|---|
Litho_Zone_Fraction | Rock_Pty_Set | The rock property set for a zone that contains this lithologic fraction | Cascade | No |
Lithology | Rock_Pty_Set | The rock property set that the lithologic description references. | Cascade | No |
Zone_DOV | Rock_Pty_Set | READ ONLY: Unique identifier for the rock pty set. | Cascade | No |
Link | To Entity | Description | Implementation Technique | Required |
---|---|---|---|---|
Measuring_Activity | Generic_Activity | The activity that recorded the rock properties | Nullify | No |
Zone_Interval_Porosity | R_Porosity | A value that represents the predominant porosity type of the borehole zone. Examples include Intergranular, Fenestral, Fracture. | Restrict | No |
Rock_Pty_Zone | Borehole_Zone | The zone, from top to bottom, that defines the limits of the general properties in this borehole. | Cascade | Yes |