R_Well_Test

R_Well_Test_Stage

Swab

Swab_Run_Fluid_Recovery

Well_Test

Business Rules
When a well test is created, at least one well test stage must always be created.
If you specify the well completion on which the well test was performed, the production string referenced by the well completion should reference the same Borehole_Id as the Borehole_Id referenced by the well test.
The equipment or pieces of equipment that are used during a well test or to perform a well test are stored in the Activity_Facility_Invl class.
Certain well tests (like MDT tests) consist of multiple different tests all run at the same time. The way to implement this will be to create a super-activity for the MDT well test, and then create separate well tests for each of the individual tests that are conducted during the MDT test. These will all be related via the super-activity relationship in the Activity parent class.
The MDs will be used to determine the Perforation_Interval and Reservoir that the well test is for.
The measured depths on the well test and well test stage are different than the measured depths at the completion and equipment level. The measured depths at the completion level are the top and bottom depths of the actual completion or temporary completion. The depths at the equipment level (Activity_Facility_Invl) specify the depth at which a particular piece of equipment is being used. The depths at the well test and well test stage level are the depths at the start/end of the activity. Therefore the well test and well test stage measured depths can span a larger or smaller area than the actual measured depths specified at the completion level.
The blow description can be stored in the generic remarks column.
The fluids that are used/consumed during a well test (such as cushions, catalysts, consumable agents) are stored at the well test stage level via the association to the Fluid_Pumping_Schedule, in the Fluid_Pumping_Detail class. This will identify the fluids that are pumped into a borehole during a well test. Note: This is only valid for well tests that are done on one borehole.
There are two methods to determine whether a particular well test will be included or excluded from production calculations. One method is to fill in the effective date, which will indicate on which date the well test starts applying to production. The second method is to use the quality and context data structures to specify codes which will indicate if the well test will apply to production.
In cases where a single well test measurement involves multiple completions, specify the primary completion in the Well_Test.Well_Completion_Id column; and specify the rest via the Well_Test_Site table.
If the well test is conducted from the borehole before a completion exists, leave Well_Completion_Id blank and populate Borehole_Id. If the test is conducted at a completion, populate Well_Completion_Id and, and optionally, Borehole_Id. If you choose to populate Borehole_Id, make sure the Well_Test.Borehole_Id value matches the associated Well_Completion.Borehole_Id value.

Notes
The Test_Quality attribute was removed because quality will be determined using the quality and context subject area.
Note the fluid/Gas_To_Surface attributes are removed because they can be determined by the Time_To_Surface at the well test stage level.

Well_Test_Interpretation

Business Rules
If the well test interpretation is at the well test stage level, the Well_Test attribute should be NOT_NULL; and the Well_Test_Stage attribute should be NOT_NULL. If the well test interpretation is at the well test level, the Well_Test attribute should be NOT NULL; and the Well_Test_Stage attribute should be NULL. This is done for ease of querying.
Well Test Interpretation is usually done on the data (e.g. the raw pressure data) collected (e.g. by a Recorder) during the Well_Test/Well_Test_Stage. This is specified by the Utilized_Facility association which references an instance in Activity_Facility_Invl. This row in Activity_Facility_Invl should reference a Well_Test/Well_Test_Stage activity using the Activity_ID association.
The business associate (person) who is interpreting the results of the well test in the Well_Test_Interpretation class can be stored in the Activity_BA_Invl class. This is a generic class that will associate any Activity with any Business Associate.
The name of the INDIVIDUAL who performed the interpretation should go in the Source column.

Well_Test_Stage

Business Rules
At least one well test stage record must always be created for every well test.
The equipment or pieces of equipment that are used during a well test stage or to perform a well test stage are stored in the Activity_Facility_Invl class.
Certain well tests (like buildup tests and drawdown tests) cause changes to other boreholes and completions, in addition to the current borehole and completion that is being changed. The affected boreholes and completions can be determined by creating a separate well test stage for each of the affected boreholes or completions.
Certain well tests (like MDT tests) consist of multiple different tests all run at the same time. The way to implement this will be to create a super-activity for the MDT well test, and then create separate well tests for each of the individual tests that are conducted during the MDT test. These will all be related via the super-activity relationship in the Activity parent class.
The MDs will be used to determine the Perforation_Interval and Reservoir that the well test is for.
The measured depths on the well test and well test stage are different than the measured depths at the completion and equipment level. The measured depths at the completion level are the top and bottom depths of the actual completion or temporary completion. The depths at the equipment level (Activity_Facility_Invl) specify the depth at which a particular piece of equipment is being used. The depths at the well test and well test stage level are the depths at the start/end of the activity. Therefore the well test and well test stage measured depths can span a larger or smaller area than the actual measured depths specified at the completion level.
The fluids that are used/consumed during a well test (such as cushions, catalysts, consumable agents) are stored at the well test stage level via the association to the Fluid_Pumping_Schedule, in the Fluid_Pumping_Detail class. This will identify the fluids that are pumped into a borehole during a well test. Note: This is only valid for well tests that are done on one borehole.
Even though there are not explicit unit of measure columns for numeric columns in Seabed, the choke size columns need an explicit unit of measure column because the choke size can be measured in length or number of turns, and since we don't have a single unit of measure we need a separate attribute.

Well_Test_Trace

Business Rules
If the well test trace is at the well test stage level, the well_test attribute should NOT_NULL; and the well_test_stage attribute should be NOT_NULL. If the well test trace is at the well test level, the well_test attribute should be NOT NULL; and the well_test_stage attribute should be NULL. This is done for ease of querying.
The bulk array will be used to store well test trace point values. The different values that can be captured for a well test trace are (time_offset_Number, pressure, temperature, flow_rate).
The equipment that is used to collect the data for a well test trace must be one of the pieces of equipment that are already specified as being a piece of equipment (in the Borehole_Act_Fac_Used class) that is used by the well test or well test stage activity that is also collecting the trace data.
The bulk array record will only be for one specific depth (Measured_Depth), which is specified in the Well_Test_Trace class, if more pressure and temperature values are captured at a different depth, then another Well_Test_Trace record will be created with a new Bulk_Array.
Trace data (5 minute increment data) should be on both the Well_Test_Stage level and at the Well_Test_Flow_Material level.