| Name | Facility_Composition |
|---|---|
| Entity Type | Table |
| Description | An association denoting that one facility is a part of another facility. One facility can be composed of many other facilities, sequentially and simultaneously. An example of a facility composition is a well completion facility that is composed of a physical assembly of downhole tubulars and equipment. |
| Submodel | Facility |
| Entity Scope | Project |
| Primary Key | Id |
| Natural Key | Whole_Facility_Id , Part_Facility_Id , Part_Well_Id , Start_Date , Existence_Kind , Version |
| Generalizations | Transient_Association , IT_Object , Tracked_Object |
| Specializations |
| Name | Value Domain | Property / Storage Unit | Description | Required / Default | Type |
|---|---|---|---|---|---|
| End_Date | DATE | NA |
End time of the association | 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) |
| 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) |
| Linear_Sequence_Number | int | No_Unit |
An integer that specifies the sequential order of the parts. The ordering is bottom-up, the first piece of equipment entering the borehole is sequence number 1, the second piece entering the hole is sequence number 2, etc . | No 1 |
NUMBER(10) |
| Measure_Point_Offset | double | Length m |
The position of the measurement point of a sensor within an assembly (as part of a tool or part of a tool string): distance from the measure reference plane of the part, i.e., sensor or tool, to the measure reference plane of the whole, i.e., tool or tool string | No |
NUMBER |
| Part_Facility_Base_Offset | double | Depth m |
The offset of the base of the part facility as measured from the top of the whole facility. To calculate the Base MD you should add the Base Offset to the top MD of the whole facility. | No |
NUMBER |
| Part_Facility_Count | int | No_Unit |
The count of part facilities in this composition | No |
NUMBER(10) |
| Part_Facility_Id | Facility |
|
Reference to the facility defining the part | No |
NUMBER(38) |
| Part_Facility_Role | R_Facility_Role |
|
Defines the role that the Part_facility plays with respect to the Whole_Facility in this composition relationship. | No |
VARCHAR2(64) |
| Part_Facility_Spacing | double | Length m |
In a situation where the part_facility_count is greater than 1 this would be the distance between the part facilities. | No |
NUMBER |
| Part_Facility_Tbl | Meta_Entity |
|
Facility type | No |
VARCHAR2(30) |
| Part_Facility_Top_Offset | double | Depth m |
The offset of the top of the part facility as measured from the top of the whole facility. To calculate the Top MD you should add the Top Offset to the top MD of the whole facility. | No |
NUMBER |
| Part_Well_Id | Well |
|
An association to denote wells that are part of another larger facility. For example a Generic_Facility of type wellsite could be composed of 1 well and 1 tank battery. | No |
NUMBER(38) |
| Produced_By | STRING64 | NA |
The name of application role that created the entity, for data created programmatically. | No |
VARCHAR2(64) |
| Remarks | REMARKS_STR | NA |
Comments made during the creation of the composite facility. | No |
VARCHAR2(999) |
| SDAT_Label | int | No_Unit |
Label used by the security system for entitlements. SDAT is Secure Data Access Technology. | No |
NUMBER(10) |
| Start_Date | DATE | NA |
Start time of the association. | No |
DATE |
| 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) |
| Whole_Facility_Id | Facility |
|
Reference to the facility defining the whole | Yes |
NUMBER(38) |
| Whole_Facility_Tbl | Meta_Entity |
|
Facility type | Yes |
VARCHAR2(30) |
| Link | To Entity | Description | Implementation Technique | Required |
|---|---|---|---|---|
| Part_Facility | Facility | Reference to the facility defining the part | Cascade | No |
| Part_Facility_Role | R_Facility_Role | Defines the role that the Part_facility plays with respect to the Whole_Facility in this composition relationship. | Restrict | No |
| Part_Well | Well | An association to denote wells that are part of another larger facility. For example a Generic_Facility of type wellsite could be composed of 1 well and 1 tank battery. | Cascade | No |
| Whole_Facility | Facility | Reference to the facility defining the whole | Cascade | Yes |