| POSC Specifications Version 2.2 | Epicentre Logical Data Model |
Often, the only information from a suite of rft's (run on the same day) is values of pressure and depth.The only way to store this information at present is to define awireline_formation_test at each depth, and relate it to a temporary_completion (so that the pressure information can be stored).Having one wireline_formation_test activity for each point tested is overkill for this simple set of data. I would like to have a single activity (which allows storage of date and contractor) for a suite of rft values.There is no semantic relationship between temporary_completion and activity (or its subtypes) that will allow this 1-many relationship. I recommend there be one..
The relationship from wireline_formation_test to temporary_completion is has been moved to wellbore_measurement_point. The cardinality of the relationship was changed to from one to many. Modify the uniqueness rule for the properties added to wellbore_measurement_point.
Modified objects:
POT3:_Well_Test_Recovery (Diagram)
wireline_formation_test.wellbore_measurement_point (Attribute)
pty_productivity_index.si (Unique rule)
pty_skin_effect.si (Unique rule)
pty_transient_pressure.si (Unique rule)
pty_transient_temperature.si (Unique rule)
wireline_formation_test.temporary_completion (Attribute)
Properties similar to those for temporary_completion were added to wellbore_measurement_point to hold data for wireline_formation_tests.
Added objects:
wellbore_measurement_point (Entity)
pty_transient_pressure.wellbore_measurement_point (Attribute)
pty_productivity_index.wellbore_measurement_point (Attribute)
pty_skin_effect.wellbore_measurement_point (Attribute)
pty_transient_temperature.wellbore_measurement_point (Attribute)
Delete the attribute in temporary_completion that represented the moved relationship.
Deleted objects:
temporary_completion.wireline_formation_test (Attribute)