| Name | SCAL_Analysis |
|---|---|
| Entity Type | Table |
| Description | SCAL is any sample analysis that is not part of basic core analysis. Most SCAL concerns reservoir properties, electrical properties, and petrographic studies. The reservoir properties measured include relative permeability, wettability, and capillary pressure. Electrical properties include formation factor, resistivity index, and cation-exchange capacity. |
| Submodel | Rock_Sample_Analysis |
| Entity Scope | Project |
| Primary Key | Id |
| Natural Key | Rock_Sample_Id , Analysis_Kind , Analysis_Method , Analysis_Order_Number , Lab_Name , Analyst_List_Txt , Start_Date , Existence_Kind , Version |
| Generalizations | Rock_Sample_Analysis , Activity , Entity , IT_Object , Tracked_Object |
| Specializations |
| Name | Value Domain | Property / Storage Unit | Description | Required / Default | Type |
|---|---|---|---|---|---|
| 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) |
| Analysis_Kind | R_SCAL_Analysis |
|
A value that represents the type of SCAL analysis. It specifies the category of properties being measured by a SCAL analysis. Examples are Relative Permeability Analysis, Formation Resistivity Factor Analysis, etc. For SCAL analyses with associated curve data sets, the activity type specifies the trace type. | Yes |
VARCHAR2(64) |
| Analysis_Method | R_SCAL_Analysis_Method |
|
The analysis method utilized to conduct the SCAL analysis. Examples are POROUS_PLATE, SIEVE_ANALYSIS, CENTRIFUGE. | Yes |
VARCHAR2(64) |
| Analysis_Order_Number | int | No_Unit |
A number that identifies the order of the sample analysis for a particular sample. I.e., if this is the 1st analysis performed on the sample, the value should be 1. If it is the 2nd analysis, the value should be 2, etc. | Yes |
NUMBER(10) |
| Analysis_Subtype | R_Analysis_Subtype |
|
Analysis subtype | No |
VARCHAR2(64) |
| Analyst_List_Txt | STRING255 | NA |
Free-form text used to specify the analyst or list of analysts who performed the analysis. | No |
VARCHAR2(255) |
| Basic_Core_Analysis_Id | Basic_Core_Analysis |
|
The basic core analysis that was performed on this sample while it was in the same state as during this SCAL analysis. | No |
NUMBER(38) |
| Digital_Format_Avail_Flag | boolean | NA |
Specifies whether or not the sample analysis is available in digital format. "1" = sample analysis is available in digital format. "0" = sample analysis is not available in digital format. | No |
NUMBER(1) |
| 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 |
| 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) |
| Lab_Business_Associate_Id | Business_Associate |
|
The business associate ID of the lab who performed the sample analysis. | No |
NUMBER(38) |
| Lab_File_Number | CODE | NA |
The file number assigned to the analysis by the lab. | No |
VARCHAR2(64) |
| Lab_Name | CODE | NA |
The name of the lab who performed the sample analysis. | 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) |
| 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) |
| 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) |
| Report_Date | DATE | NA |
Report date | No |
DATE |
| Restored_State_Reserv_Anal_Id | Reservoir_Analysis |
|
A sequence-generated identifier that uniquely identifies the reservoir analysis containing the properties representing the in situ reservoir conditions. The fundamental objective of core analysis is to obtain data representative of in situ reservoir rock properties. A reservoir analysis provides the in situ stress state as a target for approximating reservoir stresses in laboratory. Then Basic and SCAL measurements can be made to obtain values closer to expected in situ reservoir permeabilities and porosities via a restored state analysis. | No |
NUMBER(38) |
| Rock_Sample_Id | Rock_Sample |
|
The rock sample on which this analysis was performed. | Yes |
NUMBER(38) |
| SCAL_Curve_Data_Bulk_Array_Id | Bulk_Array |
|
The bulk array containing the SCAL Curve data when there are more than 4 properties. | No |
NUMBER(38) |
| SDAT_Label | int | No_Unit |
Label used by the security system for entitlements. SDAT is Secure Data Access Technology. | No |
NUMBER(10) |
| Sample_State_Desc | REMARKS_STR | NA |
Text used to describe a lab analysts interpretation of the state of a sample at the time of analysis. For example, whether the oil/salt has been extracted, etc.. | No |
VARCHAR2(999) |
| 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 |
| 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) |
| From Entity | Link | Description | Implementation Technique | Required |
|---|---|---|---|---|
| SCAL_Analysis_Condition | SCAL_Analysis | The SCAL analysis that was performed under this condition. | Cascade | Yes |
| SCAL_Analysis_Result | SCAL_Analysis | The SCAL analysis that generated this SCAL property value. | Cascade | Yes |
| SCAL_Curve_Data_Set | SCAL_Analysis | The SCAL Analysis that generated this SCAL curve data set. | Cascade | Yes |
| Link | To Entity | Description | Implementation Technique | Required |
|---|---|---|---|---|
| Analysis_Kind | R_SCAL_Analysis | A value that represents the type of SCAL analysis. It specifies the category of properties being measured by a SCAL analysis. Examples are Relative Permeability Analysis, Formation Resistivity Factor Analysis, etc. For SCAL analyses with associated curve data sets, the activity type specifies the trace type. | Restrict | Yes |
| Analysis_Method | R_SCAL_Analysis_Method | The analysis method utilized to conduct the SCAL analysis. Examples are POROUS_PLATE, SIEVE_ANALYSIS, CENTRIFUGE. | Restrict | Yes |
| Basic_Core_Analysis | Basic_Core_Analysis | The basic core analysis that was performed on this sample while it was in the same state as during this SCAL analysis. | Restrict | No |
| SCAL_Curve_Data_Bulk_Array | Bulk_Array | The bulk array containing the SCAL Curve data when there are more than 4 properties. | Control | No |
| Analysis_Subtype | R_Analysis_Subtype | Analysis subtype | Restrict | No |
| Activity_Template | Activity_Template | _ | Restrict | No |
| Lab_Business_Associate | Business_Associate | _ | Restrict | No |
| Triggering_Event | Event | _ | Nullify | No |
| Transient_Period | R_Transient_Period | _ | Restrict | No |
| Super_Activity | Activity | _ | Assoc to One | No |
| Rock_Sample | Rock_Sample | _ | Cascade | Yes |
| Restored_State_Reserv_Anal | Reservoir_Analysis | _ | Restrict | No |
| Fulfilled_Activity | Activity | _ | Assoc to Many | No |