Name | Mud_Pump_Oper_Pty_Set |
---|---|
Entity Type | Table |
Description | Activity of checking the mud pump and observing the liner size and the amount of fluid displacement at the given pressure. |
Submodel | WS_Surface_Facility |
Entity Scope | Project |
Primary Key | Id |
Natural Key | Mud_Pump_Id , Start_Date , Existence_Kind , Version |
Generalizations | Operating_Property_Set , Entity , IT_Object , Tracked_Object |
Specializations |
Name | Value Domain | Property / Storage Unit | Description | Required / Default | Type |
---|---|---|---|---|---|
Circulating_Rate | double | Mud_Flowrate L/min |
Rate of circulation at the given operating pressure and liner size. | No |
NUMBER |
End_Date | DATE | NA |
End date and time of the validity of these properties | 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) |
Kill_Line_Pressure | double | Pressure kPa |
The pressure observed in the kill line during this period | No |
NUMBER |
Liner_Size | double | Cylinder_Diameter mm |
Size of the Liner | No |
NUMBER |
Max_Pressure | double | Pressure kPa |
The maximum pressure observed during the reporting period | No |
NUMBER |
Measuring_Activity_Id | Generic_Wellsite_Activity |
|
The activity that measured the mud pump operating properties | No |
NUMBER(38) |
Mud_Density | double | Force N |
Density of the mud currently in the pump. | No |
NUMBER |
Mud_Pump_Id | Mud_Pump |
|
Reference to the mud pump subject to check. | Yes |
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) |
Operating_Pressure | double | Pressure kPa |
Operating pressure | 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) |
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) |
Slow_Speed_Flag | boolean | NA |
Flag indicating whether the pump was operating in slow speed or not | No |
NUMBER(1) |
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) |
Standpipe_Pressure | double | Pressure kPa |
The pressure observed in the standpipe during this period | No |
NUMBER |
Start_Date | DATE | NA |
Start date and time of the validity of these properties | Yes |
DATE |
Stroke_Rate | double | Stroke_Rate 1/min |
Pumping rates to be observed | No |
NUMBER |
Stroke_Volume | double | Volume m3 |
The volume pumped by a single stroke of the pump. This can also be calculated from the stroke length and liner size | 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) |
Volumetric_Efficiency | double | Dimensionless |
The ratio of the useful energy delivered by a dynamic system to the energy supplied to it. | No |
NUMBER |
Link | To Entity | Description | Implementation Technique | Required |
---|---|---|---|---|
Measuring_Activity | Generic_Wellsite_Activity | The activity that measured the mud pump operating properties | Nullify | No |
Mud_Pump | Mud_Pump | Reference to the mud pump subject to check. | Cascade | Yes |