| Name | Instrument |
|---|---|
| Entity Type | Table |
| Description | A legal document registered on the Mineral Title indicating an interest in the lands. Examples include mortgage, assignment, caveat, lien, Certificate of Title, etc. (PPDM3.7) |
| Submodel | Interest_Set |
| Entity Scope | Project |
| Primary Key | Id |
| Natural Key | |
| Generalizations | Entity , IT_Object , Tracked_Object |
| Specializations |
| Name | Value Domain | Property / Storage Unit | Description | Required / Default | Type |
|---|---|---|---|---|---|
| Contact_Id | Person |
|
The person to contact in conjunction with the instrument. | No |
NUMBER(38) |
| Document_Number | STRING64 | NA |
The number on the document itself which has been registered as an instrument. (PPDM3.7) | No |
VARCHAR2(64) |
| End_Date | DATE | NA |
The date this instrument was no longer in effect. | No |
DATE |
| 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) |
| Instrument_Type | R_Instrument_Type |
|
The type of instrument. Examples are assignment, designation of operator, etc. | Yes |
VARCHAR2(64) |
| Jurisdiction_BA_Id | Business_Associate |
|
The business associate who has jurisdiction over this instrument. | No |
NUMBER(38) |
| Line_Number | STRING32 | NA |
The line number reference for the instrument registration. (PPDM3.7) | No |
VARCHAR2(32) |
| 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) |
| Obligation_Id | Obligation |
|
The actual document the obligation is defined in. | No |
NUMBER(38) |
| 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) |
| Page_Number | STRING32 | NA |
Page number in book number and book name in county. (PPDM3.7) | No |
VARCHAR2(32) |
| Produced_By | STRING64 | NA |
The name of application role that created the entity, for data created programmatically. | No |
VARCHAR2(64) |
| Received_Date | DATE | NA |
Date on which the instrument was received for recording. (PPDM3.7) | No |
DATE |
| Recorded_Date | DATE | NA |
Date on which instrument was recorded. | No |
DATE |
| Registration_Date | DATE | NA |
Date on which instrument was registered. (PPDM3.7) | No |
DATE |
| Registration_Number | STRING64 | NA |
The number assigned to the instrument. May be called a reception or file number. Assigned by the registration office. (PPDM3.7) | No |
VARCHAR2(64) |
| 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) |
| 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) |
| Start_Date | DATE | NA |
The date this instrument became effective. | No |
DATE |
| Submitter_Id | Business_Associate |
|
The business associate that sent the document. | No |
NUMBER(38) |
| 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) |
| From Entity | Link | Description | Implementation Technique | Required |
|---|---|---|---|---|
| Instr_Approval_Status | Instrument | The instrument to which the status applies. | Cascade | Yes |
| Instrument_Remark | Instrument | The instrument to which this remark applies. | Cascade | Yes |
| Operator_Designation | Instrument | The instrument on which the designation of operator was recorded. | Restrict | No |
| Transfer_of_Interest | Instrument | The instrument in which this transfer of interest is recorded. | Restrict | No |
| Link | To Entity | Description | Implementation Technique | Required |
|---|---|---|---|---|
| Submitter | Business_Associate | The business associate that sent the document. | Nullify | No |
| Jurisdiction_BA | Business_Associate | The business associate who has jurisdiction over this instrument. | Restrict | No |
| Obligation | Obligation | The actual document the obligation is defined in. | Nullify | No |
| Contact | Person | The person to contact in conjunction with the instrument. | Nullify | No |
| Instrument_Type | R_Instrument_Type | The type of instrument. Examples are assignment, designation of operator, etc. | Restrict | Yes |