| Name | Shale_Shaker_Screen |
|---|---|
| Entity Type | Table |
| Description | Entity defining the properties of the screen used in a shale shaker. |
| Submodel | WS_Surface_Facility |
| Entity Scope | Project |
| Primary Key | Id |
| Natural Key | |
| Generalizations | IT_Object , Tracked_Object |
| Specializations |
| Name | Value Domain | Property / Storage Unit | Description | Required / Default | Type |
|---|---|---|---|---|---|
| Cut_Point | double | No_Unit |
The cut point for this screen | No |
NUMBER |
| Deck_Number | int | No_Unit |
Deck on which the screen is installed. | 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) |
| Install_Date | DATE | NA |
Date of installing the screen on the shaker | No |
DATE |
| Produced_By | STRING64 | NA |
The name of application role that created the entity, for data created programmatically. | No |
VARCHAR2(64) |
| Removal_Date | DATE | NA |
Date of removing the screen from the shaker | No |
DATE |
| SDAT_Label | int | No_Unit |
Label used by the security system for entitlements. SDAT is Secure Data Access Technology. | No |
NUMBER(10) |
| Screen_Count | int | No_Unit |
Number of screens installed on shaker with the same property. | No |
NUMBER(10) |
| Screen_Cut_Point | STRING8 | NA |
Screen cut point such as d50, d16 | No |
VARCHAR2(8) |
| Screen_Mesh_X_Size | double | Length m |
Mesh size of shaker's screen in the x direction. | No |
NUMBER |
| Screen_Mesh_Y_Size | double | Length m |
Mesh size of shaker's screen in the y direction. | No |
NUMBER |
| Shale_Shaker_Id | Shale_Shaker |
|
Reference to the shale shaker whose screen is defined. | Yes |
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) |
| Link | To Entity | Description | Implementation Technique | Required |
|---|---|---|---|---|
| Shale_Shaker | Shale_Shaker | Reference to the shale shaker whose screen is defined. | Cascade | Yes |