Specifies the Facility within whose context the identifier is unique. There is no other semantic (e.g., composition or connection) implied by this relationship. Each separator may identified by one facility. Inherited from general_facility.
The existence kind for the facility e.g. actual, planned, required or predicted. Each separator must represent a lifecycle kind of one ref_existence_kind. Inherited from facility.
This is the date that this instance was created. This date is defined by the source if imported, or is the date the instance is created if a new instance. Inherited from e_and_p_data.
This is the person, company or application that created this instance. This identifies the party responsible for loading this instance. Inherited from e_and_p_data.
This is the date that this instance was last updated. This value should be updated when any part of this instance is altered (except for inverse relationships). Inherited from e_and_p_data.
The provider of this instance, which is usually a data provider for imported/purchased data. If this instance is provided by POSC, then this attribute must be "POSC". Inherited from e_and_p_data.
The activities which are identified within the context of this object. Each separator may identify one or more activity. Inherited from locatable_object.
Gives the facilities that are component parts of the general facility. Each separator may be the whole for one or more facility_composition. Inherited from general_facility.
Gives the connections for which the facility acts as the "from" facility. Each separator may be connected from one or more facility_connection. Inherited from general_facility.
Gives the connections for which the facility acts as the "to" facility. Each separator may be connected to one or more facility_connection. Inherited from general_facility.
These are the cargos that were stored or transported by this facility. Each separator may used to store or transport one or more fluid_cargo. Inherited from general_facility.
This defines the contract designations that are made for this business object. For example, this may be the contract designations that define the specific interest ownership fractions of the business object as it is bought and sold. Each separator may be subject to one or more contract_object_designation. Inherited from business_object.
These are the coordinate systems which have been defined in the context of this object. For example, a measured depth system defined for a wellbore. Each separator may be the context for one or more general_coordinate_system. Inherited from topological_object.
Indicates the data collections that include this instance of E and P data. Each separator may be a member of one or more data_collection_content. Inherited from e_and_p_data.
These are the ownership fractions for business associates of this object. Each separator may be referenced by one or more derived_interest_makeup. Inherited from object_of_interest.
These are the document specification parts that include this data value and define its meaning within a document specification. Each use may define a different meaning, and many uses are allowed. Each separator may be included in one or more document_information_content. Inherited from e_and_p_data.
Gives the classifications that have been made of the facility. Each separator may be classified by one or more facility_classification. Inherited from facility.
Shows the fulfillment of this facility (planned, required, or) expected) by another facility via the fulfillment association. Each separator may be fulfilled by one or more facility_fulfillment. Inherited from facility.
Indicates the various planned facilities from which this facility is derived. Each separator may be fulfillment of one or more facility_fulfillment. Inherited from facility.
Specifies one or more graphical elements which are depicting this data item. Each separator may be depicted by one or more graphical_element. Inherited from e_and_p_data.
These are the designations of compliance with guidelines, limitations, regulations and privileges that are made for this business object. Each compliance statement describes the state of compliance for a specified guideline, limitation, regulation or privilege for a period of time. Each separator may be the subject of one or more guideline_compliance. Inherited from business_object.
These are the guidelines, limitations, regulations or privileges that are specifically defined for this business object. Other general guidelines, etc., that apply to this business object are defined via the typical and class relationships (if any) defined for this business object. Each separator may be the subject of one or more object_subject_to_guideline. Inherited from business_object.
The facilities which are identified within the context of this facility. Each separator may identify one or more general_facility. Inherited from facility.
Indicates a space/time operation for which the object is involved as an intersecting agent. For projection, this is the screen on which an object is being projected. For proximity, this is the magnet object. Each separator may be the intersecting object for one or more space_time_operation. Inherited from topological_object.
This are the activity involvements which affect the object. Each separator may have involvements with one or more object_activity_involvement. Inherited from object_of_interest.
The class which asserts the fundamental nature of the facility. Each separator may be fundamentally defined by one facility_class. Inherited from facility.
The set of spatial objects which represent alternative spatial natures of this object. Each separator may be located by one or more spatial_object. Inherited from locatable_object.
Gives all the material utilizations that contribute to the service or business purpose of the facility. Each separator may defines the service resulting from one or more material_installation. Inherited from facility.
The naming system in which the identifier is specified and determined to be unique. Each separator may have name specified by one naming_system. Inherited from facility.
This is a sequenced set of datable remarks for this business object. Each separator may be described by one or more object_remark. Inherited from business_object.
Gives the original facilities for which this facility is a version. Each separator may be the version for one or more facility_version. Inherited from general_facility.
Gives the facilities for which this facility is a component part. For example: CDU1 is part of Refinery A. Each separator may be the part for one or more facility_specific_composition. Inherited from facility.
These are the cells that specify the location of this producing object within grids. A well completion, for example, may be connected to one cell within one grid and three cells within another. Each separator may be simulated using one or more pfnu_grid_cell_connection. Inherited from pfnu.
These are the descriptions of the product flow network groups and related allocation factors that this product flow network unit participates in. Each separator may participate in one or more pfnu_group_allocation. Inherited from pfnu.
These are the externally generated operational reports for this product flow network unit, describing the numbers of operational units in given states over time. Examples of information defined here include the number of active platform in a license, and the number of shut-in wells during a month. Each separator may be described by one or more pfnu_period_operation_report. Inherited from pfnu.
Indicates a space/time operation for which the object is involved as a primary agent. For degeneration, this object is being degenerated. For projection, this object is being projected onto another object. For proximity, this is the container object. Each separator may be the primary object for one or more space_time_operation. Inherited from topological_object.
Indicates a topological relationship in which the topologic object has the role of primary agent. For a spatial predicate type of "within" this is the containing role (e.g., if a city is inside a county then the county would be the primary agent). For all other spatial predicate types the roles are symmetrical and both relationships must be searched for a particular object. For example, if a wellbore and a formation overlap then either could be chosen as the primary agent with the other chosen as the secondary agent. Each separator may be primarily involved in one or more topological_relationship. Inherited from topological_object.
Indicates various records of property damage associated with this facility. Each separator may be afflicted with one or more property_damage. Inherited from facility.
These are the contractual obligations that this business object is designated as fulfilling, either completely or partially. Each separator may satisfy one or more contract_oblig_object_fulfil. Inherited from business_object.
Indicates a topological relationship in which the object is in the role of secondary agent. For a spatial predicate type of "within" this is the contained role (e.g., if a well is within a field then the well would be the secondary agent). For all other spatial predicate types the roles are symmetrical and both relationships must be searched for a particular object. For example, if a wellbore and a formation overlap then either could be chosen as the secondary agent with the other chosen as the primary agent. Each separator may be involved in one or more topological_relationship. Inherited from topological_object.
Indicates the space/time operation from which a topological object was the result. For addition, this is the union of two objects. For degeneration, this is the degenerate object. Each separator may be the result of one space_time_operation. Inherited from topological_object.
These are the contracts that specify information about the business object, and the business object is subject to the terms of these contracts. Each separator may be a subject of one or more subject_of_contract. Inherited from business_object.
These are the surface and standard temperatures that are defined for a fluid phase at a product flow network unit. Each separator may be characterized by one or more surface_fluid_phase_condition. Inherited from pfnu.
Gives the facility versions for which this facility acts as the original. Each separator may be the original for one or more facility_version. Inherited from general_facility.