| Name | Activity_Template |
|---|---|
| Entity Type | Table |
| Description | An activity template is a model of an activity that is proposed for imitation. In other words, it does not represent an activity that has actually taken place; but rather a template of an activity that can be used as a pattern or model for an actual activity. Activity templates are especially useful for defining workflows. |
| Submodel | Activity |
| Entity Scope | Project |
| Primary Key | Id |
| Natural Key | Super_Workflow_Id , Name , Existence_Kind , Version |
| Generalizations | Entity , IT_Object , Tracked_Object |
| Specializations |
| Name | Value Domain | Property / Storage Unit | Description | Required / Default | Type |
|---|---|---|---|---|---|
| Activity_Subtype | Meta_Entity |
|
The subtype of Activity used to record the activations of this activity template. | Yes |
VARCHAR2(30) |
| Command_Arg_String | STRING255 | NA |
Any command line arguments that should be passed to the program on every execution. Or could be a method to compute the arguments tailored for each execution. | No |
VARCHAR2(255) |
| 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) |
| Expected_Duration | double | Time s |
The expected temporal duration of the workflow when it is executed. | No |
NUMBER |
| 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) |
| 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) |
| Order_In_Superworkflow | int | No_Unit |
The static execution order, starting from 1, of this workflow in its superworkflow (if any). This can be used to constrain execution order to honor data producer-consumer precedence, or any other criteria arising from the problem domain. There can be a set of subworkflows sharing a common order value. This indicates that there are no order constraints among the members of the set; they could be executed in any order, or even in parallel. | No |
NUMBER(10) |
| 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) |
| Primary_Goal | STRING255 | NA |
Primary goal of the Activity_Template e.g. "Plan_Well", or "Time_To_Depth_Conversion". There could be multiple Activity_Templates sharing a given primary Goal. | No |
VARCHAR2(255) |
| Produced_By | STRING64 | NA |
The name of application role that created the entity, for data created programmatically. | No |
VARCHAR2(64) |
| 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) |
| Super_Workflow_Id | Activity_Template |
|
The identifier of the immediate containing super activity template of the activity template. E.g., logging service run might be used as the superactivity for logging trip. | No |
NUMBER(38) |
| Supplier_Name | STRING255 | NA |
The name of the original supplier for this workflow program. Not the vendor who sells it. | No |
VARCHAR2(255) |
| Supplier_Product_Name | STRING255 | NA |
The name of the product name strongly associated with the execution of this workflow. Could be a software product, a name associated with a standard suite of wellsite services, etc. | No |
VARCHAR2(255) |
| Supplier_Product_Version | STRING64 | NA |
The supplier"s version number or nomenclature associated with Supplier_Product_Name. | 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) |
| 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) |
| Workstep_Flag | boolean | NA |
Indicate (value=Y) that a given Activity_Template is a leaf in the recursive Activity_Template-SubActivity_Template hierarchy. | No |
NUMBER(1) |
| From Entity | Link | Description | Implementation Technique | Required |
|---|---|---|---|---|
| Act_Tmpl_BA_Role | Activity_Template | The activity template for which this Business Associate role involvement is defined. | Cascade | Yes |
| Act_Tmpl_Data_Role | Activity_Template | The identifier of the activity template for which the role is an input or output. | Cascade | Yes |
| Act_Tmpl_Dataflow_Arc | Owning_Activity_Template | The identifier of the activity template 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 | Yes |
| Activity | Activity_Template | The identifier of the activity template which activates or characterizes the Activity. | Restrict | No |
| Activity_Parameter | Activity_Template | The activity template that uses this parameter. | Cascade | No |
| Activity_Template | Super_Workflow | The identifier of the immediate containing super activity template of the activity template. E.g., logging service run might be used as the superactivity for logging trip. | Cascade | No |
| Link | To Entity | Description | Implementation Technique | Required |
|---|---|---|---|---|
| Activity_Subtype | Meta_Entity | The subtype of Activity used to record the activations of this activity template. | Restrict | Yes |
| Transient_Period | R_Transient_Period | A code or name that indicates whether the activity is executed daily, monthly, on demand, etc. | Restrict | No |
| Super_Workflow | Activity_Template | The identifier of the immediate containing super activity template of the activity template. E.g., logging service run might be used as the superactivity for logging trip. | Cascade | No |