An activity is something that happens bringing about change to the perceived state of the universe.

ref_existence_kind (M: ref_existence_kind)

The lifecycle kind of the activity e.g. actual, planned, required or predicted.


cost (O: ndt_money)

The cost of the activity.


description (O: ndt_comment)

A description of the activity.


duration (O: ndt_time)

The duration of the activity.


end_time (O: ndt_date_tod)

The end time of the activity.


name (O: ndt_name)

The name or label given to the activity.


start_time (O: ndt_date_tod)

The start time of the activity.


activity_classification (V: SET[0:?] activity_classification(activity))

This activity can be classified as one or more activity classes via the activity classification association. Each activity may classified by one or more activity_classification.


business_associate_activity_role (V: SET[0:?] business_associate_activity_role(activity))

These are the roles of the business associates for the activity. For example, a service activity may have one business associate in the role of client and another in the role of vendor. Each activity may be characterized by one or more business_associate_activity_role.


caused (V: SET[0:?] activity_cause_and_effect(caused_by)) (0639)

This is the association that defines those activities that this activity caused to happen. Each activity may caused one or more activity_cause_and_effect.


cause_association (V: SET[0:?] transient_association(caused_by))

Indicates the various transient associations that are established as a result of this activity. For example, the movement of a material into a storage facility would cause a transient association to be established. Each activity may cause one or more transient_association.


constrained_by (V: SET[0:?] schedule_constraint(constraint_for))

Gives the schedule constraints where this activity is constrained by the other activity related to this schedule constraint. Each activity may be the activity constrained by one or more schedule_constraint.


constraint_for (V: SET[0:?] schedule_constraint(constrained_by))

This activity acts as a constraint, via the schedule constraint, upon the other activity related to this schedule constraint. Each activity may constrain one or more schedule_constraint.


contained_activity (V: SET[0:?] activity(containing_activity))

Specifies the contained activities. Containment means that the contained activities must occur during the time of the containing activity. Each activity may contain one or more activity.


containing_activity (O: activity(contained_activity))

Specifies the containing activity. The containing activity indicates the activity for which this activity is a component sub-activity. Constrains the time of the contained activity to be during the containing activity. Each activity may be contained by one activity.


contract (V: SET[0:?] contract(activity))

These are the contracts that provide specifications, requirements, or other information about this activity. For example, a contract may describe the manner in which this activity is performed. Each activity may be a subject of one or more contract.


contractual_obligation (V: SET[0:?] contractual_obligation(contractual_obligation_activity))

This instance of an activity satisfies the contractual obligation. Each activity may satisfy one or more contractual_obligation.


create_schedule (V: SET[0:?] schedule(create_activity))

Defines the schedules which were created by this activity. Each activity may create one or more schedule.


data_collection (I, V: SET[0:?] data_collection(collection_content))

Indicates the data collections that include this instance of E and P data. Each activity may be a member of one or more data_collection. Inherited from e_and_p_data.


describing_schedule (V: SET[0:?] schedule(described_activity))

The set of schedules that describe this activity. Each activity may be described by one or more schedule.


facility (O: SET[0:?] facility(activity))

Defines the facilities which were used by the activity. Each activity may utilize one or more facility.


fulfill (V: SET[0:?] activity_fulfillment(fulfillment))

This defines the associations with the activities that are fulfilled by this activity. Each activity may fulfills one or more activity_fulfillment.


fulfillment (V: SET[0:?] activity_fulfillment(fulfill))

This is the association that defines the activities that fulfill this activity. Each activity may is fulfilled by one or more activity_fulfillment.


graphical_element (I, V: SET[0:?] graphical_element(depicted_object))

Specifies one or more graphical elements which are depicting this data item. Each activity may be depicted by one or more graphical_element. Inherited from e_and_p_data.


guideline_or_privilege (V: SET[0:?] guideline_or_privilege(activity_subject_to_guideline)) (1223)

These are the guidelines, limitations, regulations or privileges that are specifically defined for this activity. Other general guidelines, etc., that apply to this activity are defined via the typical and class relationships (if any) defined for this activity. Each activity may be the subject of one or more guideline_or_privilege.


guideline_or_privilege_compliance (V: SET[0:?] guideline_or_privilege_compliance(activity))

This describes the guidelines, limitations, regulations or privileges for which compliance information is kept for this activity. Each compliance instance defines a specific guideline, limitation, regulation or privilege and states the status of this activity with respect to it over a period of time. Each activity may be the subject of one or more guideline_or_privilege_compliance.


populate (V: SET[0:?] data_collection(populated_by))

Defines the data collections whose contents were assembled from existing instances by this activity. Each activity may populate one or more data_collection.


process_data (V: SET[0:?] process_data(activity))

Defines the set of instances created by this activity. Each activity may result in values for one or more process_data.


process_data_item (V: SET[0:?] process_data_item(activity))

Defines the set of data used by this activity. Each activity may use one or more process_data_item.


ref_transient_period (O: ref_transient_period) (1222)

The type of period over which the property applies, such as day, month, quarter, cumulative, etc.


result_of (V: BAG[0:1] activity_cause_and_effect(result)) (0639)

This is the association that defines the activities that caused this activity to occur. Each activity may result of one activity_cause_and_effect.


schedule_activity (V: SET[0:?] schedule_activity(activity))

Shows how this activity is ordered within a schedule and, possibly with respect to other activities within the same schedule. Each activity may be scheduled as one or more schedule_activity.


terminate_association (V: SET[0:?] transient_association(terminated_by))

Indicates the transient associations terminated by the activity. For example, transferring materials from a storage facility terminates the storage association between the material and the storage facility. Each activity may terminate one or more transient_association.


typical_activity (O: typical_activity(activity))

Gives the typical activity which acts as the template or design for this activity. Each activity may be an occurrence of one typical_activity.


update_collection (V: SET[0:?] data_collection(updated_by))

The data pointed to by this data collection was updated or created by this activity. Each activity may updates or creates the instances contain one or more data_collection.


utilize_equipment (O: equipment_item(utilized_in_activity))

Defines a piece of equipment used by the activity without stating the functional usage of the equipment. This is useful for legacy data where there is knowledge about a piece of equipment but there is not enough knowledge to define a facility. Each activity may use one equipment_item.


utilize_material (O: SET[0:?] material(used_by_activity)) (1223)

Indicates various materials which are utilized by this activity, such as consumables, agents, catalysts, or in other roles. Each activity may utilize one or more material.

Local rules:

Abstract supertype:
Each ACTIVITY must be instantiated as one of its subtypes. These subtypes are: analytical_reservoir_analysis, choke_adjustment_event, compose_document_specification, contract_processing_operation, coordinate_transformation_activity, curve_fit_activity, digitize_document, directional_survey_analysis, document_circulation, equipment_calibration, equipment_repair_job, flow_system_analysis, geoscience_interpretation, incident_investigation, incident_of_noncompliance, lift_system_analysis, log_trace_analysis, materials_balance_analysis, materials_characterization, materials_processing, other_activity, positioning_measurement_activity, process_application_for_permit, production_activity, render_document, reserves_category_change, reserves_evaluation, reservoir_simulation, reservoir_simulation_case, reservoir_simulation_postprocessing, reservoir_simulation_preprocessing, reservoir_simulation_time_step, sample_acquisition, seismic_acquisition_activity, seismic_processing_activity, surface_geologic_survey, valve_close_event, valve_open_event, wellbore_activity, well_activity, well_completion_activity, well_pattern_analysis, well_test_analysis, well_test_measurement
Different Related Instance
An instance of ACTIVITY cannot contain itself.
Different Related Instance
An instance of ACTIVITY cannot be contained by itself.
Instance Value Constraint
If REF_TRANSIENT_PERIOD is EVENT, then both START_TIME and END_TIME must either be blank or be identical.
Instance Value Constraint
If REF_TRANSIENT_PERIOD is either YEAR TO DATE, MONTH TO DATE or CUMULATIVE, then END_TIME must be instantiated.
Instance Value Constraint
If REF_TRANSIENT_PERIOD is ANNUAL, SEMIANNUAL, QUARTER, MONTHLY, DAILY, or HOURLY, then either both START_TIME and END_TIME are blank or both must be instantiated.
Supertype path(s):
e_and_p_data > activity.

Entity replicated into subtype tables (@activity).

Referenced in Diagrams:

• AC1: Activity Schedule
• AC2: Activity Effects (0639)
• AC3: Activity Subtypes
• AC4: Activity Classes & Typicals
• DMG1: Specification and Rendering
• EPC1: Contracts and Agreements
• EPR1: Guidelines and Privileges (1223)
• EPR3: Incident Reporting
• EQF2: Equipment and Materials Use
• GPI2: Checkshot Analysis (1226)
• HL1: High Level Model (0644)
• MSA1: Materials Analysis (1223, 1226)
• POA: Production Activities
• POT1: Well Testing Activities
• RVA: Reservoir Activities
• WL2: Well Logging Activities
• WO1: Well Operations (0947, 1126, 1129)
• WO2: Wellbore Survey and Targets (1123, 1177)