| Name | Well_Test |
|---|---|
| Entity Type | Table |
| Description | An activity, performed under specified conditions, to measure the factors affecting the capability of a well for production or injection of fluids. There are several different kinds of well tests which can be performed during the life history of a well, each with a specific purpose. Some Examples are production test, initial potential test, drill stem test, etc. |
| Submodel | Well_Testing |
| Entity Scope | Project |
| Primary Key | Id |
| Natural Key | Well_Completion_Id , Borehole_Id , Start_Date , Existence_Kind , Version |
| Generalizations | Wellsite_Activity , Activity , Entity , IT_Object , Tracked_Object |
| Specializations |
| Name | Value Domain | Property / Storage Unit | Description | Required / Default | Type |
|---|---|---|---|---|---|
| Activity_Program_Id | Activity_Program |
|
Reference to the program during which the activity was performed. | No |
NUMBER(38) |
| Activity_State | STRING64 | NA |
The current state, or status, of the activity. Activity state is a refinement of the lifecycle indicator Existence_Kind. For example, a drilling job whose Existence_Kind is "Actual" could have an activity state of "turning to the right", "suspended due to weather", or "tool makeup or breakdown". An activity whose Existence_Kind is "Required" could have State values like "under investigation", "proposed" and "AFE approved". Note: The valid list of activity states will vary from one kind of activity to another, so the values entered into this column are not validated via a lookup table. | No |
VARCHAR2(64) |
| Activity_Template_Id | Activity_Template |
|
The identifier of the activity template which activates or characterizes the Activity. | No |
NUMBER(38) |
| Base_Interval_MD | double | Depth m |
Base depth of the interval being tested. | No |
NUMBER |
| Borehole_Condition_Desc | STRING255 | NA |
Free form text to describe the condition of the hole during this test. | No |
VARCHAR2(255) |
| Borehole_Conditioned_Flag | boolean | NA |
A flag to indicate whether or not the borehole was conditioned during this well test. | No |
NUMBER(1) |
| Borehole_Id | Borehole |
|
The borehole from which the test was conducted. If the well test was conducted at multiple boreholes, specify the primary borehole in this column and specify the others in the Well_Test_Site table. | No |
NUMBER(38) |
| Duration | double | Time s |
The duration of the activity. For planned activities, this would be expected duration. | No |
NUMBER |
| Effective_Date | DATE | NA |
The production date on which the fluid properties from this well test start applying to production volume calculations. For example, if this well tests results are used to calculate volumes on fluid produced from this facility from 3/1/2004 onward, the value in this field should be 3/1/2004. Note that many companies production days go from 8 AM on the producing day to 8 AM the following day, so a well test performed between 12 AM and 8 AM on the following day is still considered to apply to production on the previous day, or the "Production Day". | No |
DATE |
| End_Date | DATE | NA |
The date and time at which the activity will end or did end. For planned activities, this would be expected end date. | 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) |
| External_Reference | STRING64 | NA |
A value that is used by an external organization to reference this activity. For example, if an external organization is hired to perform this activity, this column could be used to store the work order or purchase order number that organization uses to reference this activity. | No |
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) |
| Internal_Reference | STRING64 | NA |
A value that is used internally within the organization to reference this activity. | No |
VARCHAR2(64) |
| Max_Fluid_Level | double | Depth m |
The maximum recorded fluid level during the well test | No |
NUMBER |
| Min_Fluid_Level | double | Depth m |
The minimum recorded fluid level during the well test | 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) |
| Packer_Release_Date | DATE | NA |
The date/time the packer was released during this well test. | No |
DATE |
| Packer_Set_Date | DATE | NA |
The date/time the packer was set in the borehole during this well test. | No |
DATE |
| Problem_Description | STRING255 | NA |
Free form text that describes if any problems were encountered during this well test. | No |
VARCHAR2(255) |
| Produced_By | STRING64 | NA |
The name of application role that created the entity, for data created programmatically. | No |
VARCHAR2(64) |
| Purpose | STRING255 | NA |
A description of purpose of the activity or its stage | No |
VARCHAR2(255) |
| Remarks | STRING2000 | NA |
Any type of remarks added to an entity instance. | No |
VARCHAR2(2000) |
| Reverse_Circulation_Flag | boolean | NA |
Indicates whether or not the well was reverse circulated before the start of well test. Typically used for DST tests. | No |
NUMBER(1) |
| SDAT_Label | int | No_Unit |
Label used by the security system for entitlements. SDAT is Secure Data Access Technology. | No |
NUMBER(10) |
| 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 |
The date and time at which the activity will start or did start. For planned activities, this would be expected start date. | No |
DATE |
| Stimulated_Flag | boolean | NA |
A flag to indicate whether or not the borehole was stimulated/acidized before the well test was started. | No |
NUMBER(1) |
| Surface_Pressure | double | Barometric_Pressure kPa |
Atmospheric pressure on the surface when the well test took place | No |
NUMBER |
| Surface_Temperature | double | Temperature degC |
The ambient air temperature at the surface when the well test took place | No |
NUMBER |
| Time_Offset | double | Time s |
The time offset from the start of the program that this activity is scheduled to start at. This is normally used while planning a job. | No |
NUMBER |
| Top_Interval_MD | double | Depth m |
Top depth of the interval being tested. | No |
NUMBER |
| Total_Cost | double | No_Unit |
The total cost of the activity expressed in the local currency. | No |
NUMBER |
| Transient_Period | R_Transient_Period |
|
A code or name that indicates whether the activity is executed daily, monthly, on demand, etc. | No |
VARCHAR2(64) |
| Triggering_Event_Id | Event |
|
The identifier of the event that triggered the start of this activity. Events can trigger activities. For example, an explosion event could trigger a firefighting activity. Note that this value should not conflict with, or be confused with, the value in Activity_Status.Triggering_Event. | No |
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) |
| Well_Completion_Id | Well_Completion |
|
The completion at which this well test was conducted. If the well test was conducted at multiple completions, specify the primary completion in this column and specify the others in the Well_Test_Site table. | No |
NUMBER(38) |
| Well_Test_Reason_Code | R_Well_Test_Reason |
|
The reason the well test was performed. Example values are: to determine maximum production, to determine if the well is damaged. | No |
VARCHAR2(64) |
| Well_Test_Type | R_Well_Test |
|
A value that represents the type of well test performed. Examples of well test types are Production Test, Drill Stem Test, Potential Test, Pressure Transient Test, Formation Test, etc. | Yes |
VARCHAR2(64) |
| From Entity | Link | Description | Implementation Technique | Required |
|---|---|---|---|---|
| Well_Test_Interpretation | Well_Test | The identifier of the well test whose data is being interpreted via this interpretation. An interpretation can be performed either for a well test or a well test stage. | Cascade | Yes |
| Well_Test_Site | Well_Test | The identifier of the well test for which the site(s) is being defined. | Cascade | No |
| Well_Test_Stage | Well_Test | The identifier of the well test to which this stage belongs. | Cascade | Yes |
| Well_Test_Summary | Well_Test | Parent well test identifier | Cascade | Yes |
| Well_Test_Trace | Well_Test | The identifier of the well test during which the trace measurements were recorded. | Cascade | Yes |
| Link | To Entity | Description | Implementation Technique | Required |
|---|---|---|---|---|
| Activity_Template | Activity_Template | _ | Restrict | No |
| Fulfilled_Activity | Activity | _ | Assoc to Many | No |
| Borehole | Borehole | The borehole from which the test was conducted. If the well test was conducted at multiple boreholes, specify the primary borehole in this column and specify the others in the Well_Test_Site table. | Cascade | No |
| Well_Completion | Well_Completion | The completion at which this well test was conducted. If the well test was conducted at multiple completions, specify the primary completion in this column and specify the others in the Well_Test_Site table. | Cascade | No |
| Activity_Program | Activity_Program | _ | Restrict | No |
| Well_Test_Type | R_Well_Test | A value that represents the type of well test performed. Examples of well test types are Production Test, Drill Stem Test, Potential Test, Pressure Transient Test, Formation Test, etc. | Restrict | Yes |
| Triggering_Event | Event | _ | Nullify | No |
| Transient_Period | R_Transient_Period | _ | Restrict | No |
| Super_Activity | Activity | _ | Assoc to One | No |
| Well_Test_Reason_Code | R_Well_Test_Reason | The reason the well test was performed. Example values are: to determine maximum production, to determine if the well is damaged. | Restrict | No |