| Name | Rig_Utilization |
|---|---|
| Entity Type | Table |
| Description | The information regarding the usage of a rig to drill the whole or part of a borehole. |
| Submodel | WS_Job |
| Entity Scope | Project |
| Primary Key | Id |
| Natural Key | Activity_Program_Id , Rig_Id , Start_Date , Existence_Kind , Version |
| Generalizations | Entity , IT_Object , Tracked_Object |
| Specializations |
| Name | Value Domain | Property / Storage Unit | Description | Required / Default | Type |
|---|---|---|---|---|---|
| Activity_Program_Id | Activity_Program |
|
Reference to the wellsite program for which the rig has been utilized. | Yes |
NUMBER(38) |
| Arrival_Date | DATE | NA |
The date and time when the rig arrived at the wellsite | No |
DATE |
| Contract_Date | DATE | NA |
The date of the contract for the participation of this rig in the activity program | No |
DATE |
| Contract_Max_Value | int | No_Unit |
The maximum value allowed for this contract. It should be stored in the local currency | No |
NUMBER(10) |
| Contract_Number | CODE | NA |
The number given to a contract to uniquely identify it to the parties involved | No |
VARCHAR2(64) |
| Contract_Type | CODE | NA |
The type of contract | No |
VARCHAR2(64) |
| Currency | R_Currency |
|
The currency associated with the daily rate of the rig | No |
VARCHAR2(64) |
| Daily_Rate | double | No_Unit |
The cost per day of the rig | No |
NUMBER |
| Departure_Date | DATE | NA |
The date and time when the rig departed from the wellsite | No |
DATE |
| Drilling_Days | int | No_Unit |
The number of drilling days for this operation | No |
NUMBER(10) |
| 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) |
| KB_Elevation | double | Length m |
The elevation of the Kelly Bushing whilst drilling this borehole | No |
NUMBER |
| 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) |
| Operation_End_Date | DATE | NA |
The date that the operation that this rig was assigned to perform was completed | No |
DATE |
| 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) |
| Remarks | STRING2000 | NA |
Any type of remarks added to an entity instance. | No |
VARCHAR2(2000) |
| Rig_Charge_Date | DATE | NA |
The date and time at which the rig became chargeable | No |
DATE |
| Rig_Down_Date | DATE | NA |
The date and time when the rig down of the rig was completed. This is a denormalization of the start_date of the rig down generic activity | No |
DATE |
| Rig_Id | Rig |
|
Reference to the rig subject to utilization | Yes |
NUMBER(38) |
| Rig_Pick_Up_Date | DATE | NA |
The date and time when the rig up of the rig was picked up from the wellsite. This is a denormalization of the start_date of the rig pick up generic activity | No |
DATE |
| Rig_Release_Date | DATE | NA |
The date that the rig was released after drilling this borehole | No |
DATE |
| Rig_Up_Date | DATE | NA |
The date and time when the rig up of the rig was completed. This is a denormalization of the start_date of the rig up generic activity | No |
DATE |
| 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 start date of the drilling operation on this borehole by this rig | No |
DATE |
| 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) |
| Link | To Entity | Description | Implementation Technique | Required |
|---|---|---|---|---|
| Currency | R_Currency | The currency associated with the daily rate of the rig | Restrict | No |
| Rig | Rig | Reference to the rig subject to utilization | Cascade | Yes |
| Activity_Program | Activity_Program | Reference to the wellsite program for which the rig has been utilized. | Cascade | Yes |