Conv_Core_Acquisition

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

General Information

[Next]
Name Conv_Core_Acquisition
Entity Type Table
Description The wellsite activity of extracting a conventional core from the earth.
Submodel Rock_Sample_Acquisition
Entity Scope Project
Primary Key Id
Natural Key Borehole_Id , Start_Date , Existence_Kind , Version , Start_MD
Generalizations Core_Acquisition , Borehole_Activity , Wellsite_Activity , Activity , Entity , IT_Object , Tracked_Object
Specializations


Columns

[Previous] [Next] [Top]
NameValue DomainProperty /
Storage Unit		DescriptionRequired /
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)
Borehole_Id Borehole
The identifier of the borehole in which the activity occurred. Yes
 NUMBER(38)
Core_Barrel_Used_Id Core_Barrel
A value that uniquely identifies the core barrel used to perform the conventional core acquisition activity. No
 NUMBER(38)
Core_Bit_Used_Id Core_Bit
A value that uniquely identifies the core bit used during the conventional core acquisition activity. No
 NUMBER(38)
Drill_Fluid_Test_Id Drill_Fluid_Test
The unique identifier of the drill fluid test which is recorded during this conventional core acquisition activity. No
 NUMBER(38)
Drill_Fluid_Type R_Drill_Fluid
The type of fluid that was in the borehole at the time the conventional coring operation. Examples are Water Based, Oil Based, or Gel. No
 VARCHAR2(64)
Duration double Time
s		 The duration of the activity. For planned activities, this would be expected duration. No
 NUMBER
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
End_MD double Depth
m		 Measured depth at the end of the activity or proposed depth end of the activity. 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)
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)
Lost_Core_Length double Length
m		 A measurement that represents the length of the portion of core lost during the core acquisition activity. No
 NUMBER
Lost_Core_Position R_Core_Position
If the core recovery is less than 100%, this value represents an estimation of where the missing section of the core was lost. Examples include, TOP, MIDDLE, BASE, and SCATTERED. No
 VARCHAR2(64)
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)
Operator_Run_Num STRING32 NA
 The identifier, as assigned the well operator, that uniquely identifies the core acquisition run. No
 VARCHAR2(32)
Orientation_Flag boolean NA
 An indicator that specifies whether or not the core was acquired with equipment that preserves the original orientation of the sample. 1 = core was acquired with equipment that preserves the original orientation of the sample. 0 = core was not acquired with equipment that preserves the original orientation of the sample. No
 NUMBER(1)
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)
Pressure_Retained_Flag boolean NA
 An indicator that specifies whether or not the core was acquired with equipment that preserves the original reservoir pressure. 1 = core was acquired with equipment that preserved the original reservoir pressure. 0 = core was retrieved at ambient pressure. No
 NUMBER(1)
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)
Recovered_Length double Length
m		 A measurement that represents the length of the core that was recovered from the core acquisition activity. No
 NUMBER
Remarks STRING2000 NA
 Any type of remarks added to an entity instance. 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)
Service_Co_Run_Num STRING32 NA
 An identifier, as assigned by the company who performed the coring run, that uniquely identifies the core acquisition run. No
 VARCHAR2(32)
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)
Sponge_Core_Flag boolean NA
 An indicator that specifies whether or not the core was acquired with equipment that preserves lost reservoir fluids in a sponge liner. 1 = core was acquired with equipment that preserves lost reservoir fluids in a sponge liner. 0 = core was not acquired with equipment that preserves lost reservoir fluids in a sponge liner. No
 NUMBER(1)
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
Start_MD double Depth
m		 Measured depth at the start of the activity or proposed start depth of the activity. No
 NUMBER
Successful_Flag boolean NA
 A flag to indicate whether or not the activity was successful (Yes/No) No
 NUMBER(1)
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
Total_Cost double No_Unit
 The total cost of the activity expressed in the local currency. No
 NUMBER
Tracer_Type R_Tracer
The type of the drilling mud tracer additive used during conventional core acquisition. A tracer additive is used to mark the mud filtrate to help identify the depth of contamination of initial water saturations in the sample. Examples include RADIOACTIVE DEUTERIUM, RADIOACTIVE TRITIUM, RADIOACTIVE TRITIATED HEXADECANE, SODIUM POTASSIUM BROMIDE SALT, CHLORIDE SALT, IODIDE SALT, ISO-PROPANOL ALCOHOL, NITRATE and FLUORESCEIN DYE. No
 VARCHAR2(64)
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)
Work_String_Id Work_String
The work string used during a borehole activity. No
 NUMBER(38)


Referenced By

[Previous] [Next] [Top]
From EntityLinkDescriptionImplementation TechniqueRequired
Core Conv_Core_Acquisition The identifier of the wellsite activity that produced this core. Restrict No
Plug_DOV Core_Acquisition READ ONLY: Unique identifier for the Core Acquisition. Nullify No


Refers To

[Previous] [Next] [Top]
LinkTo EntityDescriptionImplementation TechniqueRequired
Lost_Core_Position R_Core_Position If the core recovery is less than 100%, this value represents an estimation of where the missing section of the core was lost. Examples include, TOP, MIDDLE, BASE, and SCATTERED. Restrict No
Activity_Program Activity_Program _ Restrict No
Core_Bit_Used Core_Bit A value that uniquely identifies the core bit used during the conventional core acquisition activity. Restrict No
Core_Barrel_Used Core_Barrel A value that uniquely identifies the core barrel used to perform the conventional core acquisition activity. Restrict No
Activity_Template Activity_Template _ Restrict No
Fulfilled_Activity Activity _ Assoc to Many No
Triggering_Event Event _ Nullify No
Transient_Period R_Transient_Period _ Restrict No
Super_Activity Activity _ Assoc to One No
Drill_Fluid_Test Drill_Fluid_Test _ Restrict No
Drill_Fluid_Type R_Drill_Fluid _ Restrict No
Work_String Work_String _ Restrict No
Borehole_Zone Borehole_Zone _ Assoc to Many No
Borehole Borehole _ Cascade Yes
Borehole_Section Borehole_Section _ Assoc to Many No
Tracer_Type R_Tracer The type of the drilling mud tracer additive used during conventional core acquisition. A tracer additive is used to mark the mud filtrate to help identify the depth of contamination of initial water saturations in the sample. Examples include RADIOACTIVE DEUTERIUM, RADIOACTIVE TRITIUM, RADIOACTIVE TRITIATED HEXADECANE, SODIUM POTASSIUM BROMIDE SALT, CHLORIDE SALT, IODIDE SALT, ISO-PROPANOL ALCOHOL, NITRATE and FLUORESCEIN DYE. Restrict No


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

Copyright © 2018 Schlumberger. All rights reserved.