| POSC Specifications Version 2.2 | Epicentre Logical Data Model |
There are many times in our business when we need to describe the use of a number of items of a given type. The only information we know is the type and the quantity of the items. This is very common in making up casing, tubing, drillstring etc.
Added entities catalog_item_assembly and catalog_item_collection as new subtypes of (renamed) entity equipment_composition. Catalog_item_assembly and catalog_item_collection have new relationships from catalog_equipment, and the "part" relationship from equipment_item to equipment_item_composition has been replaced with the two relationships from equipment_item
Added objects:
catalog_item_assembly (Entity)
catalog_item_collection (Entity)
catalog_equipment.catalog_item_assembly (Attribute)
catalog_equipment.catalog_item_collection (Attribute)
equipment_item.equipment_item_assembly (Attribute)
equipment_item.equipment_item_collection (Attribute)
equipment_item_assembly.val1 (Where rule)
equipment_item_collection.val1 (Where rule)
equipment_item_assembly.part (Attribute)
equipment_item_collection.part (Attribute)
Modify diagrams to reflect the changes. The uniqueness rules on the subtypes will be different in the EXPRESS file. The supertype of equipment_item_assembly and equipment_itemcollection have changed from equipment_item_composition to equipment_composition
Modified objects:
EQW1:_Equipment_Item (Diagram)
EQF2:_Equipment_and_Materials_Us (Diagram)
WO2:_Wellbore_Survey_and_Targets (Diagram)
equipment_item_assembly.si (Unique rule)
equipment_item_collection.si (Unique rule)
equipment_item.composed_of (Attribute)
equipment_item_assembly (Entity)
equipment_item_collection (Entity)
Rename equipment_item_composition to equipment_composition to better reflect its new subtype behavior.
Renamed objects:
equipment_composition (Entity), previous name was equipment_item_composition
Add the following subtypes to equipment_installation: catalog_item_installation and catalog_equipment_installation. Add the attributes that point from these to equipment_item and catalog_equipment respectively and also add the corresponding inverse attributes. The relationship from equipment_item to equipment_installation is replaced by the relationship from equipment_item to equipment_item_installation.
Added objects:
catalog_equipment_installation (Entity)
equipment_item_installation (Entity)
catalog_equipment.catalog_equipment_installation (Attribute)
The relationship from equipment_item to equipment_installation has been moved to equipment_item_installation. Changed equipment_installation from non-abstract to abstract as a result of adding subtypes.
Modified objects:
equipment_item.equipment_installation (Attribute)
equipment_installation (Entity)
Delete the "part" attributes that represented the replaced relationship. Delete the attribute (equipment_item) in equipment_installation that represented the "moved" relationship. Delete the uniqueness rule on Equipment_installation as a result making it abstract and adding subtypes. Delete the local rule on Equipment_composition (it is being moved to each subtype).
Deleted objects:
equipment_installation.equipment_item (Attribute)
equipment_composition.part (Attribute)
equipment_item.part_of (Attribute)
equipment_installation.si (Unique rule)
equipment_composition.val1 (Where rule)