| Name | Facility_Property |
|---|---|
| Entity Type | Table |
| Description | Additional properties of a facility not explicitly modeled |
| Submodel | Facility |
| Entity Scope | Project |
| Primary Key | Id |
| Natural Key | Facility_Id , Facility_Parameter , Existence_Kind , Version |
| Generalizations | Parameter , Entity , IT_Object , Tracked_Object |
| Specializations |
| Name | Value Domain | Property / Storage Unit | Description | Required / Default | Type |
|---|---|---|---|---|---|
| Boolean_Value | boolean | NA |
The Boolean value of this parameter. | No |
NUMBER(1) |
| Date_Value | DATE | NA |
The date value for this parameter. | 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) |
| Facility_Id | Facility |
|
The facility to which these properties belong | Yes |
NUMBER(38) |
| Facility_Parameter | R_Facility_Parameter |
|
The type of facility parameter | Yes |
VARCHAR2(64) |
| Facility_Tbl | Meta_Entity |
|
Facility type | Yes |
VARCHAR2(30) |
| 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) |
| Int_High_Limit_Clip_Flag | boolean | NA |
A flagged value to show if the integer parameter value is within the expected range for the parameter or if the value is equal to the high end limit and potentially represents a clipped, out of range, outlier. A 0 represents a NO response and states that the Integer_Value is less than the upper limit range specified by the reference data. This is the default case. A 1 represents a YES response and states that the Integer_Value is equal to the upper limit range specified in the reference data suggesting clipped data. | No 0 |
NUMBER(1) |
| Int_Low_Limit_Clip_Flag | boolean | NA |
A flagged value to show if the integer parameter value is within the expected range for the parameter or if the value is equal to the low end limit and potentially represents a clipped, out of range, outlier. A 0 represents a NO response and states that the Int_Value is greater than the lower limit range specified by the reference data. This is the default case. A 1 represents a YES response and states that the Num_Value is equal to the lower limit range specified in the reference data suggesting clipped data. | No 0 |
NUMBER(1) |
| Integer_Value | int | No_Unit |
The integer value of this parameter. | No |
NUMBER(10) |
| Integer_Value_UOM | UNIT_CODE | NA |
The unit of measure for an integer parameter. This must be consistent with the supplied reference data or the Valid_Parameter_Flag should be set to 0 (NO).. | No |
VARCHAR2(64) |
| Max_Num_Value | double | No_Unit |
The maximum numeric value of this parameter. The UOM for this maximum value must be the same as the UOM for the Num_Value. | No |
NUMBER |
| Min_Num_Value | double | No_Unit |
The minimum numeric value of this parameter. The UOM for this minimum value must be the same as the UOM for the Num_Value. | No |
NUMBER |
| 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) |
| Num_High_Limit_Clip_Flag | boolean | NA |
A flagged value to show if the numeric parameter value is within the expected range for the parameter or if the value is equal to the high end limit and potentially represents a clipped, out of range, outlier. A 0 represents a NO response and states that the Num_Value is less than the upper limit range specified by the reference data. This is the default case. A 1 represents a YES response and states that the Num_Value is equal to the upper limit range specified in the reference data suggesting clipped data. | No 0 |
NUMBER(1) |
| Num_Low_Limit_Clip_Flag | boolean | NA |
A flagged value to show if the numeric parameter value is within the expected range for the parameter or if the value is equal to the low end limit and potentially represents a clipped, out of range, outlier. A 0 represents a NO response and states that the Num_Value is greater than the lower limit range specified by the reference data. This is the default case. A 1 represents a YES response and states that the Num_Value is equal to the lower limit range specified in the reference data suggesting clipped data. | No 0 |
NUMBER(1) |
| Num_Value | double | No_Unit |
The numeric value of this parameter. | No |
NUMBER |
| Num_Value_UOM | UNIT_CODE | NA |
The unit of measure for a numeric parameter. This must be consistent with the supplied reference data or the Valid_Parameter_Flag should be set to 0 (NO).. | No |
VARCHAR2(64) |
| 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) |
| 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) |
| String_Value | STRING2000 | NA |
The string value for this parameter. | No |
VARCHAR2(2000) |
| 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) |
| Valid_Parameter_Flag | boolean | NA |
A flag value that states whether or not this instance of the parameter is valid. This allows questionable data to be preserved for cleanup or validation at a later time. An example of an invalid parameter occurs when incoming data attempts to load an expected number with a string value. Another example occurs when a number value has an invalid or missing unit of measure. The flag value is 1 (YES) if the parameter is valid and 0 (NO) if the parameter is invalid by some test. The default value is 1, stating that the parameter is valid. Error messages or comments addressing invalid parameter data should be made in the Remarks attribute. | Yes 1 |
NUMBER(1) |
| Version | STRING255 | NA |
The form or variant of the entity. | Yes 1 |
VARCHAR2(255) |
| Link | To Entity | Description | Implementation Technique | Required |
|---|---|---|---|---|
| Facility_Parameter | R_Facility_Parameter | The type of facility parameter | Restrict | Yes |
| Facility | Facility | The facility to which these properties belong | Cascade | Yes |