| Name | Act_Tmpl_Data_Role |
|---|---|
| Entity Type | Table |
| Description | An input to or output from an activity template that is playing a certain role. For example, an invoice amount can be an input to an activity template, playing the role of "cost". An activity template can have many inputs and outputs, each playing different roles. Additionally, a role can be an input to or output from many activity templates. |
| Submodel | Activity |
| Entity Scope | Project |
| Primary Key | Id |
| Natural Key | Activity_Template_Id , Role_Name , Involvement_Type , Existence_Kind , Version |
| Generalizations | Entity , IT_Object , Tracked_Object |
| Specializations |
| Name | Value Domain | Property / Storage Unit | Description | Required / Default | Type |
|---|---|---|---|---|---|
| Activity_Template_Id | Activity_Template |
|
The identifier of the activity template for which the role is an input or output. | Yes |
NUMBER(38) |
| Binding_HI_Component | STRING64 | NA |
The identity of the human interface component responsible for finalizing the binding of actual data items for this defined data role. See also Binding_Order, and Select_Query. | No |
VARCHAR2(64) |
| Binding_Order | int | No_Unit |
The order that this data role should be bound relative to other Act_Tmpl_Data_Role objects for the same Activity_Template. This accommodates dependencies among role bindings. For example, if a list of well markers displayed to a user for selection is based on an area of interest, then it is important to bind the area of interest before the well marker. | No |
NUMBER(10) |
| 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) |
| 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) |
| Involved_Entity_Type | Meta_Entity |
|
The entity that is designated to play this data role for this activity template. In other words, the entity that will be "bound" to this data role. | Yes |
VARCHAR2(30) |
| Involvement_Type | R_Activity_Entity_Invl |
|
The type of involvement the data role has with the activity template, with respect to the activity template. For example, "Input" means that the data role is involved as an input to the activity. "Output" means that the data role is involved as an output from the activity. "Incidental" means that the type of involvement is neither an input or output. | Yes |
VARCHAR2(64) |
| Local_To_Activity_Flag | boolean | NA |
Indicates whether or not the entity bound to this output is strictly local to the activity, or has visibility outside the activity. In other words, it specifies whether or not the entity should be deleted after the activity has completed. This should only be populated for data roles that are outputs. | No |
NUMBER(1) |
| Max_Cardinality | int | No_Unit |
Maximum number of data items that could be bound to this data involvement. In combination with Min_Cardinality, can encode both cardinality and optionality. | No |
NUMBER(10) |
| Min_Cardinality | int | No_Unit |
Minimum number of data items that could be bound to this data involvement. In combination with Max_Cardinality, can encode both cardinality and optionality. | No |
NUMBER(10) |
| 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) |
| Remarks | STRING2000 | NA |
Any type of remarks added to an entity instance. | No |
VARCHAR2(2000) |
| Role_Name | STRING64 | NA |
The name of the role that the input to/output from this activity template is playing. For example, an invoice amount can be an input to an activity template, playing the role of "cost". | Yes |
VARCHAR2(64) |
| SDAT_Label | int | No_Unit |
Label used by the security system for entitlements. SDAT is Secure Data Access Technology. | No |
NUMBER(10) |
| Select_Query | REMARKS_STR | NA |
The optional select query to restrict the set of candidate data bindings for this role. The default binding set is all qualifying data items in the repository, so e.g. for a binding for entities of type Well_Log, the default binding would be something like: select * from Well_Log; The qualifying set of objects can either be used without modification, or may be used as input to the HI component identified in Binding_HI_Component for further reductions. | 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) |
| 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 |
|---|---|---|---|---|
| Act_Tmpl_Data_Dependency | Input_Invl | The activity template data role that is the input role. E.g. the one that provides an identified level of influence, or provides identity for, the output. | Cascade | No |
| Act_Tmpl_Data_Dependency | Output_Invl | The activity template data role that is the output role. E.g. the one that is influenced by, or inherits identity from, the input. | Cascade | Yes |
| Act_Tmpl_Dataflow_Arc | Flow_Source | The identifier of the activity template data role that is on the source side of this connection. | Cascade | Yes |
| Act_Tmpl_Dataflow_Arc | Flow_Destination | The identifier of the activity template data role that is on the destination side of this connection. | Cascade | Yes |
| Link | To Entity | Description | Implementation Technique | Required |
|---|---|---|---|---|
| Activity_Template | Activity_Template | The identifier of the activity template for which the role is an input or output. | Cascade | Yes |
| Involved_Entity_Type | Meta_Entity | The entity that is designated to play this data role for this activity template. In other words, the entity that will be "bound" to this data role. | Restrict | Yes |
| Involvement_Type | R_Activity_Entity_Invl | The type of involvement the data role has with the activity template, with respect to the activity template. For example, "Input" means that the data role is involved as an input to the activity. "Output" means that the data role is involved as an output from the activity. "Incidental" means that the type of involvement is neither an input or output. | Restrict | Yes |