Well_Test_Trace_Data


[Columns] [Composed Of] [Referenced By] [Refers To]

General Information

[Next]
Name Well_Test_Trace_Data
Entity Type Table
Description Detail records regarding a well test trace.
Submodel Well_Testing
Entity Scope Project
Primary Key Id
Natural Key
Generalizations IT_Object , Tracked_Object
Specializations


Columns

[Previous] [Next] [Top]
NameValue DomainProperty /
Storage Unit
DescriptionRequired /
Default
Type
Absolute_Time DATE NA
Absolute date/time of data collection. Either this or a combination trace_hdr.start_time and time_offset should be used to find the date/time of any data point in the trace. No
DATE
Casing_Pressure double Pressure
kPa
The pressure observed in the casing. No
NUMBER
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)
Fluid_Flowrate double Flowrate
m3/h
The flow rate recorded at this trace point. No
NUMBER
Fluid_Level double Depth
m
The measured depth of the fluid level. No
NUMBER
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)
Hydrostatic_Pressure double Pressure
kPa
The hydrostatic pressure in the mud column at the particular point where values are being measured or calculated for a well test No
NUMBER
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)
MD double Depth
m
The measured depth of this trace point. No
NUMBER
Observaton_Number int No_Unit
The observation or sequence number of the trace data value. No
NUMBER(10)
Pressure double Pressure
kPa
The pressure recorded at this trace point. No
NUMBER
Pressure_Point_Gradient NUMBER Pressure_Per_Length
kPa/m
Pressure point gradient 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
A textual remark associated with this trace data entry. No
VARCHAR2(2000)
Resistivity double Resistivity
ohm.m
Resistivity of the fluid. No
NUMBER
SDAT_Label int No_Unit
Label used by the security system for entitlements. SDAT is Secure Data Access Technology. No
NUMBER(10)
Temperature double Temperature
degC
The temperature recorded at this trace point. No
NUMBER
Time_Offset double Time
s
Time offset of this data point with respect to the start time of the trace. The start time of the trace is stored in the trace_hdr table. No
NUMBER
Tubing_Pressure double Pressure
kPa
The pressure observed in the tubing. 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)
Volume double Volume
m3
The volume of fluid measured at this trace point. No
NUMBER
Well_Test_Trace_Id Well_Test_Trace
The trace header to which the detail records belong. Yes
NUMBER(38)


Refers To

[Previous] [Next] [Top]
LinkTo EntityDescriptionImplementation TechniqueRequired
Well_Test_Trace Well_Test_Trace The trace header to which the detail records belong. Cascade Yes


[Seabed Objects] [Entities in Schema Seabed] [Index]

Copyright © 2018 Schlumberger. All rights reserved.