Name | Study |
---|---|
Entity Type | Table |
Description | An analysis of geological and geophysical data with the express objective and a finite timeframe related to a specific milestone in an exploration or production context. |
Submodel | Interpretation_Results |
Entity Scope | Project |
Primary Key | Id |
Natural Key | Study_Identifier , Existence_Kind , Version |
Generalizations | Entity , IT_Object , Tracked_Object |
Specializations |
Name | Value Domain | Property / Storage Unit | Description | Required / Default | Type |
---|---|---|---|---|---|
Cartographic_System_Code | R_Coordinate_Ref_System |
|
The cartographic system in which the X and Y measurements for the Study bounding box are described. | No |
VARCHAR2(64) |
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) |
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) |
Loading_Status | R_Loading_Status |
|
This defines the loading status of the study. It can be initiated, completed, or other site defined values. | Yes |
VARCHAR2(64) |
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) |
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) |
Produced_By | STRING64 | NA |
The name of application role that created the entity, for data created programmatically. | No |
VARCHAR2(64) |
Project_Data_Manager | STRING255 | NA |
The name of the project data manager populating the data in the study. | Yes |
VARCHAR2(255) |
Quality_Control_Auditor | STRING255 | NA |
The name(s) of the person(s) responsible for quality assurance of the study. | No |
VARCHAR2(255) |
Quality_Description | REMARKS_STR | NA |
Comments on the quality of the data contained in the study. | No |
VARCHAR2(999) |
Register_Date | DATE | NA |
The date the study was first registered in the database. | Yes |
DATE |
Remarks | STRING2000 | NA |
Any type of remarks added to an entity instance. | No |
VARCHAR2(2000) |
SDAT_Label | int | No_Unit |
Label used by the security system for entitlements. SDAT is Secure Data Access Technology. | No |
NUMBER(10) |
Shape_Id | Area |
|
The identifier of a polygon outlining the shape of the study. | No |
NUMBER(38) |
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) |
Study_Date | DATE | NA |
The year in which the study was completed. | Yes |
DATE |
Study_Identifier | STRING255 | NA |
A unique identifier for the study. It is a concatenation of name, phase, type and year, comma separated. | No |
VARCHAR2(255) |
Study_Owner | STRING255 | NA |
The name(s) of the person or persons responsible for the interpretation. | Yes |
VARCHAR2(255) |
Study_Phase | STRING255 | NA |
The phase for which the study was performed, e.g. exploration, production. Established by local business rule. | Yes |
VARCHAR2(255) |
Study_Type | R_Study |
|
Defines the type of Study. | Yes |
VARCHAR2(64) |
URL | STRING255 | NA |
One or many URLs addresses for report(s) describing the study. | No |
VARCHAR2(255) |
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) |
X_Maximum | double | No_Unit |
The maximum X value for the study. | Yes |
NUMBER |
X_Minimum | double | No_Unit |
The minimum X value for the study. | Yes |
NUMBER |
Y_Maximum | double | No_Unit |
The maximum Y value for the study. | Yes |
NUMBER |
Y_Minimum | double | No_Unit |
The minimum Y value for the study. | Yes |
NUMBER |
From Entity | Link | Description | Implementation Technique | Required |
---|---|---|---|---|
Study_Element | Study | The identifier of the study in which this study element is contained. | Restrict | No |
Link | To Entity | Description | Implementation Technique | Required |
---|---|---|---|---|
Study_Type | R_Study | Defines the type of Study. | Restrict | Yes |
Cartographic_System_Code | R_Coordinate_Ref_System | The cartographic system in which the X and Y measurements for the Study bounding box are described. | Restrict | No |
Loading_Status | R_Loading_Status | This defines the loading status of the study. It can be initiated, completed, or other site defined values. | Restrict | Yes |
Shape | Area | The identifier of a polygon outlining the shape of the study. | Control | No |