| Name | Activity |
|---|---|
| Entity Type | Abstract |
| Description | An activity can represent a process or procedure that takes place in the oilfield (for example, drilling a well, conducting a rock sample analysis, interpreting a well test, performing a log tool calibration, etc.); or it can represent a software program component (for example, a program that draws a map based on various inputs). |
| Submodel | Activity |
| Entity Scope | Project |
| Primary Key | Id |
| Natural Key | |
| Generalizations | Entity , IT_Object , Tracked_Object |
| Specializations | Activity_Program , Borehole_Formation_Eval , Cement_Slurry_Test , Fluid_Analysis , Fluid_Analysis_Stage , Fluid_Processing , Fluid_Sample_Acquisition , Gas_Lift_Utilization , Generic_Activity , Log_Channel_Processing , Log_Tool_Calibration , Measurement_Program , Outcrop_Sample_Acq , Reserve_Analysis , Reservoir_Analysis , Rig_Planning , Rock_Sample_Analysis , Rock_Sample_Preparation , Seismic_Acquisition_Act , Seismic_Processing_Act , Software_Component , Well_Test_Interpretation , Wellsite_Activity , Work_Order , Work_Order_Process |
| 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) |
| 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) |
| 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) |
| 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 |
| 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 |
|---|---|---|---|---|
| Activity | Fulfilled_Activity | The current Activity object is the fulfillment of the associated Activity object. For example, a planned activity (Activity.Existence_Kind="planned") could be fulfilled many times by actual activities (Activity.Existence_Kind="actual"), and a given activity could be the fulfillment of many planned activities. | Assoc to Many | No |
| Activity | Super_Activity | The Activity that is the immediate containing superactivity of the Activity. E.g., a given logging service run might be used as the superactivity for a given logging trip. | Assoc to One | No |
| Activity_BA_Invl | Activity | The associated Activity of this involvement. | Cascade | Yes |
| Activity_Dataflow_Arc | Owning_Activity | The identifier of the Activity for which this dataflow arc is defined. The arc could be between subworkflow data involvements, or between data involvement at the level of the superworkflow and one of the subworkflows. | Cascade | No |
| Activity_Entity_Invl | Involved_Activity | The identifier of the activity for which the data role is either an input or output. | Cascade | Yes |
| Activity_Facility_Invl | Activity | The activity associated with this particular involvement. It could be the activity that installed the facility, the activity that used the facility etc | Cascade | No |
| Activity_Parameter | Activity | The activity that uses this parameter. | Cascade | No |
| Activity_Remark | Activity | The identifier of the activity to which this remark applies. | Cascade | Yes |
| Activity_Status | Triggering_Activity | The activity that triggered the change in status of another activity | Assoc to One | No |
| Activity_Status | Activity | The identifier of the activity to which this status applies. | Cascade | Yes |
| Cost_Allocation | Allocated_Activity | Reference to the activity for which the cost has been allocated. | Assoc to One | No |
| Event | Activity | Reference to the activity during which the event took place or for which the risk has been identified. | Assoc to One | No |
| Facility_Status | Triggering_Activity | The activity that triggered the status of the facility. | Cascade | No |
| Material_Used | Activity | The activity that used the Material. | Cascade | Yes |
| Link | To Entity | Description | Implementation Technique | Required |
|---|---|---|---|---|
| Activity_Template | Activity_Template | The identifier of the activity template which activates or characterizes the Activity. | Restrict | No |
| Fulfilled_Activity | Activity | The current Activity object is the fulfillment of the associated Activity object. For example, a planned activity (Activity.Existence_Kind="planned") could be fulfilled many times by actual activities (Activity.Existence_Kind="actual"), and a given activity could be the fulfillment of many planned activities. | Assoc to Many | No |
| Super_Activity | Activity | The Activity that is the immediate containing superactivity of the Activity. E.g., a given logging service run might be used as the superactivity for a given logging trip. | Assoc to One | No |
| Transient_Period | R_Transient_Period | A code or name that indicates whether the activity is executed daily, monthly, on demand, etc. | Restrict | No |
| Triggering_Event | 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. | Nullify | No |