| Name | Tubular_Utilization |
|---|---|
| Entity Type | View |
| Description | An extension class of Activity_Facility_Invl to hold the specific information required in the utilization of a "tubular". For the purpose of this class the term "Tubulars" includes casing string, drill string and drill pipe etc. |
| Submodel | WS_Activity |
| Entity Scope | Project |
| Primary Key | Id |
| Natural Key | Facility_Id , Activity_Id , Start_Date , Top_MD , Existence_Kind , Version |
| Generalizations | Activity_Facility_Invl , Entity , IT_Object , Tracked_Object |
| Specializations |
| Name | Value Domain | Property / Storage Unit | Description | Required / Default | Type |
|---|---|---|---|---|---|
| Activity_Id | Activity |
|
The activity associated with this particular involvement. It could be the activity that installed the facility, the activity that used the facility etc | No |
NUMBER(38) |
| Activity_Role | R_Activity_Role |
|
The role that the activity plays in this involvement. It could be the installation activity, the removal activity or utilization activity etc | No |
VARCHAR2(64) |
| Activity_Tbl | Meta_Entity |
|
Activity type | No |
VARCHAR2(30) |
| Base_MD | double | Depth m |
Measured depth to the base of the facility. | No |
NUMBER |
| Bend_Angle | double | Plane_Angle deg |
The offset angle to the axis of the body of the sub during this operation. | No |
NUMBER |
| Circulation_Duration | double | Time s |
Duration of circulation during deployment of the tubular in the hole. | No |
NUMBER |
| End_Date | DATE | NA |
End date and time of the validity of this entry. For example for an installation activity this would be the installation date and time and for a utilization activity this would be the end date and time of the period during which the facility is utilized | 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) |
| Facility_Id | Facility |
|
The facility that is the target of the involvement. For example in an installation involvement it is the facility that is installed | Yes |
NUMBER(38) |
| Facility_Role | R_Facility_Role |
|
The role that the facility plays in this involvement. It could be a gauge that performs the role of Primary Gauge. | No |
VARCHAR2(64) |
| Facility_Tbl | Meta_Entity |
|
Facility type | Yes |
VARCHAR2(30) |
| 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) |
| Installed_Weight | double | High_Force 1000 kgf |
Total weight of tubular deployed in borehole during this operation. | No |
NUMBER |
| Landing_Time | DATE | NA |
The date and time that the tubular was landed at the target depth | No |
DATE |
| Lost_Mud_Volume | double | Volume m3 |
Mud volume lost during operation on the tubular. | No |
NUMBER |
| Max_Hole_Angle | double | Plane_Angle deg |
Maximum angle of hole during the operation. | 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) |
| 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) |
| Parallel_Run_Flag | boolean | NA |
A flag to indicate whether or not the tubular was run parallel to another assembly | No |
NUMBER(1) |
| Position_Id | Position |
|
The position at which the facility is located. This should be normally used for facilities installed on the surface (though it can be used for tracking the position of a downhole facility in case of a deviated well). The position of a facility can change over time | No |
NUMBER(38) |
| Pressure | double | Pressure kPa |
The pressure at the facility during its utilization | 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) |
| SDAT_Label | int | No_Unit |
Label used by the security system for entitlements. SDAT is Secure Data Access Technology. | No |
NUMBER(10) |
| Site_Borehole_Id | Borehole |
|
The borehole in which the facility (e.g. A permanent Gauge) is installed or used. In general, this should be used only when a facility is installed or its depth is changed inside a borehole. For activities which utilize a downhole facility, this should be used when the activity involves multiple boreholes. | No |
NUMBER(38) |
| Site_Field_Id | Field |
|
The field in which the facility is installed. E.g. A separator can be associated to a field using this association | No |
NUMBER(38) |
| Site_Well_Id | Well |
|
The well at which the facility is installed. E.g. A Wellhead Facility can be associated to a well using this relationship. | No |
NUMBER(38) |
| Slips_Weight | double | High_Force 1000 kgf |
Weight in slips | No |
NUMBER |
| 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 |
Start date and time of the validity of this entry. For example for an installation activity this would be the installation date and time and for a utilization activity this would be the start date and time of the period during which the facility is utilized | No |
DATE |
| Sub_Type | Meta_Entity |
|
Sub type of Activity_Facility_Invl | No |
VARCHAR2(30) |
| Temperature | double | Temperature degC |
The temperature at the facility during its utilization | No |
NUMBER |
| Top_MD | double | Depth m |
Measured depth to the top of the facility. | No |
NUMBER |
| Tubular_Tension | double | Force N |
Tension during deployment of tubular | No |
NUMBER |
| 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 |
|---|---|---|---|---|
| Activity | Activity | _ | Cascade | No |
| Activity_Role | R_Activity_Role | _ | Restrict | No |
| Facility | Facility | _ | Cascade | Yes |
| Site_Well | Well | _ | Nullify | No |
| Position | Position | _ | Control | No |
| Site_Borehole | Borehole | _ | Nullify | No |
| Site_Field | Field | _ | Nullify | No |
| Facility_Role | R_Facility_Role | _ | Restrict | No |