| Name | Pipe_Tally_Detail |
|---|---|
| Entity Type | Table |
| Description | Detail information on a pipe tally. |
| Submodel | WS_Resource_Mgmt |
| Entity Scope | Project |
| Primary Key | Id |
| Natural Key | |
| Generalizations | IT_Object , Tracked_Object |
| Specializations |
| Name | Value Domain | Property / Storage Unit | Description | Required / Default | Type |
|---|---|---|---|---|---|
| Centralizer_Flag | boolean | NA |
A flag indicating that this transform joint of drill pipe has a centralizer fitted to it. | No |
NUMBER(1) |
| 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) |
| Inside_Diameter | double | Cylinder_Diameter mm |
Inside diameter of an entity, such as an item of drill string equipment | No |
NUMBER |
| Joint_Number | int | No_Unit |
The number of the joint being run | No |
NUMBER(10) |
| Length | double | Length m |
The length of the joint being run | No |
NUMBER |
| Outside_Diameter | double | Cylinder_Diameter mm |
Outside diameter of the Equipment. For a tubular, it is the outside diameter of the body | No |
NUMBER |
| Pipe_Delivery_Number | int | No_Unit |
Delivery tally number (offload). | No |
NUMBER(10) |
| Pipe_Tally_Id | Pipe_Tally |
|
The pipe tally to which this detail record belongs. | Yes |
NUMBER(38) |
| Produced_By | STRING64 | NA |
The name of application role that created the entity, for data created programmatically. | No |
VARCHAR2(64) |
| Pull_Out_Flag | boolean | NA |
Indicates whether the pipe was ran out of hole or not | No |
NUMBER(1) |
| Remarks | STRING2000 | NA |
Remarks on this pipe tally detail record | 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) |
| Steel_Grade | STRING64 | NA |
Grade used to qualify the characteristics of the steel. For tubular, grade determines the minimum yield strength and thus the burst and collapse pressures. The grade can be either defined by the supplier or defined by the API. | No |
VARCHAR2(64) |
| Tubular_Type | CODE | NA |
The type of tubular reference by this pipe tally detail record. | No |
VARCHAR2(64) |
| 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 |
|---|---|---|---|---|
| Pipe_Tally | Pipe_Tally | The pipe tally to which this detail record belongs. | Cascade | Yes |