|
Acquisition_Device
|
|
|
Activity_Facility_Invl
|
Business Rules
The activity is optional in this class because although you probably always have an activity whenever you identify the position and location of a facility, you may not know the activity at the time.
This class is used to identify the transient pieces of equipment that are installed in the well and borehole.
This class is used to identify the facility (and equipment) used during certain activities (like well test activities and fluid analysis activities).
|
|
Assembly
|
|
|
BHA
|
|
|
Casing_String
|
You should specify either a name or a set of depths (in the Current_Base_MD and Current_Top_MD columns) to uniquely identify a casing string within a borehole.
|
|
Communication_Interface
|
|
|
Compressor
|
|
|
Compressor_Oper_Pty_Set
|
|
|
Connector_Condition
|
|
|
Downhole_Assembly
|
Business Rules:
The same downhole assembly can't be placed into another borehole. If it is, a new downhole assembly facility would be created.
|
|
Drill_String
|
|
|
Expander
|
|
|
Expander_Oper_Pty_Set
|
|
|
Fac_BA_Involvement
|
|
|
Fac_Condition_Detail
|
|
|
Fac_Connection_Material
|
|
|
Fac_Network_Connection
|
Business Rules:
All networks should be made up of ONLY "facility-type" facilities. That means that they are the logical/abstract facilities, not the ones in which you want to keep track of the manufacturer serial number.
|
|
Facility
|
Business Rule
The commissioned and decomissioned dates for any facility will be determined using the Facility_Status structure. Recommend that there be a Facility_Status code of Commissioned and one for Decommissioned.
|
|
Facility_Alias
|
|
|
Facility_Composition
|
Business Rules
A 'part' facility should generally not have more than one parent (i.e., there should not be more than one record in which a particular facility is acting as a 'part' at a particular point in time.
Usage rule to define that, if used for anything other than a grouping of facilities, then it should match the number of records in the facility table.
Measurement points (logical points) can be connected to another facility by using the facility composition class (For example, a meter and the measurement point at the meter are associated via the facility composition class).
|
|
Facility_Condition
|
Business Rule
The natural key for this entity consists of: Facility Id; Measuring Activity Id; Start Date; Existence Kind; and Version. If the Measuring Activity doesn't exist or is deleted, the next time an attempt is made to insert a new Facility Condition record for this facility the natural key will be violated. Therefore, as a usage rule, the date discriminator, Start Date must be treated as mandatory and always provided on nsert. Start Date allows the Facility Condition to remain unique even if its Measuring Activity is deleted.
|
|
Facility_Connection
|
Business Rules
If a To_Connector is specified, it should reference a Facility_Connector record whose Facility_Id value is equal to the value of Facility_Connector.To_Facility_Id.
If a From_Connector is specified, it should reference a Facility_Connector record whose Facility_Id value is equal to the value of Facility_Connector.From_Facility_Id.
|
|
Facility_Connector
|
|
|
Facility_Maint_Activity
|
|
|
Facility_Network
|
Business Rule
The allocation process will run against a logical network that is at the “facility” level, not the “well” level. A well is NOT a facility in Seabed. Therefore, we need to specify facilities (like well completions, meters, or measurement points) as specific points on the facility network to which production will be allocated.
All networks should be made up of ONLY "facility-type" facilities. That means that they are the logical/abstract facilities not the ones in which you want to keep track of the manufacturer serial number.
|
|
Facility_Property
|
|
|
Facility_Status
|
|
|
Fiber
|
|
|
Gathering_System
|
|
|
Generic_Act_Fac_Invl
|
|
|
Generic_Assembly
|
|
|
Generic_Downhole_Assembly
|
|
|
Generic_Facility
|
|
|
Generic_Meter
|
|
|
Generic_Pump
|
Business Rule
The properties specified on the Pump class are nominal properties that rarely change. In addition, if they do change, we do not care about the history of these changes so they are not date effective. Properties for which is important to keep track of changes over time are going to be stored in the Pump_Oper_Pty_Set class.
|
|
Generic_Pump_Oper_Pty_Set
|
Business Rules
The operating properties stored in this class are properties that sporadically change over time or are properties that change at a fixed timeframe.
If an activity is defined (as measuring the properties in this property set), then only the properties measured by this activity will be populated. If another activity measures other properties (or the same properties) in this property set, then a new property set record will be created with those new properties.
|
|
Generic_Tracked_Facility
|
|
|
Maint_Obs_Pty_Set
|
|
|
Measurement_Tag
|
|
|
Measurement_Tag_Scal_Conf
|
|
|
Measurement_Tag_Threshold
|
Business Rule
The limit will either be stored as a value in the Threshold_Value attribute or as a curve via the Expected_Curve association to Bulk_Array.
|
|
Measurement_Tag_Vect_Conf
|
|
|
Meter
|
Business Rules
The meter type must be the same as this meter’s r_meter_cat.meter_type.
The properties specified on the Meter class are nominal properties that rarely change. In addition, if they do change we do not care about the history of these changes, so they are not date effective. Properties for which it is important to keep track of changes over time are going to be stored in the Meter_Oper_Pty_Set class.
|
|
Meter_Oper_Pty_Set
|
Business Rules
The operating properties stored in this class are properties that sporadically change over time or are properties that change at a fixed timeframe.
|
|
Nuclear_Source
|
|
|
Operating_Property_Set
|
|
|
Orifice_Meter
|
|
|
PD_Meter
|
|
|
Pipeline
|
|
|
Pipeline_Oper_Pty_Set
|
|
|
Process_Plant
|
|
|
Pump
|
|
|
Pump_Curve
|
|
|
Pump_Curve_Coef
|
|
|
Pump_Performance_Detail
|
|
|
Pump_Performance_Pty_Set
|
|
|
R_Acquisition_Device
|
|
|
R_Acquisition_Device_Cat
|
|
|
R_Casing_String_Role
|
|
|
R_Communication_Interface
|
|
|
R_Compressor
|
|
|
R_Expander
|
|
|
R_Fac_Cond_Category
|
|
|
R_Fac_Status_Category
|
|
|
R_Facility_Condition
|
|
|
R_Facility_Connection
|
|
|
R_Facility_Maint
|
|
|
R_Facility_Parameter
|
|
|
R_Facility_Status
|
|
|
R_Fiber_End
|
|
|
R_Fiber_Section_Number
|
|
|
R_Generic_Pump_Cat
|
|
|
R_Measurement_Mode
|
|
|
R_Measurement_Process
|
|
|
R_Measurement_Scal_Cat
|
|
|
R_Measurement_Signal
|
|
|
R_Measurement_Tag
|
|
|
R_Measurement_Tag_Cat
|
|
|
R_Measurement_Tag_Limit
|
|
|
R_Measurement_Vector_Cat
|
|
|
R_Observed_Facility
|
|
|
R_Orientation
|
Business Rules:
If the tank is a vertical tank, the First_End_Shape is the shape of the bottom end of the tank, and the Second_End_Shape is the shape of the top end of the tank.
|
|
R_Pipeline
|
|
|
R_Process_Plant
|
|
|
R_Pump_Cat
|
|
|
R_Pump_Curve_Cat
|
|
|
R_Pump_Curve_Coef
|
|
|
R_Recorder
|
|
|
R_Recorder_Cat
|
|
|
R_Sensor_Cat
|
|
|
R_Separator
|
|
|
R_Strapping_Table_Entry
|
|
|
R_String_Type
|
|
|
R_Tank
|
|
|
R_Tank_Cat
|
Business Rules
If there is only one end to the tank, then the First_Tank_End_Shape_Code will be populated, but the Second_Tank_End_Shape_Code will not.
|
|
R_Tank_End_Shape
|
|
|
R_Tank_Strapping_Table
|
Business Rules
If an entry in the strapping table changes, a new strapping table should be created with a new set of entries. The deletion_date should be populated in the old strapping table. This allows for the preservation of strapping tables used over time for a particular tank.
|
|
R_Thread
|
|
|
R_Tracked_Surf_Facility
|
|
|
R_Valid_Fac_Condition
|
|
