ISO 10303-214:2010(E)

Figure — Arrowleft Figure — Clause 4 Figure — Arrowright

4.2.2 Activity

An Activity is the fact of achieving or accomplishing an action.

The data associated with an Activity are the following:

4.2.2.1 activity_type

The activity_type specifies the purpose of the Activity.

Where applicable the following values shall be used:

4.2.2.2 actual_end_date

The actual_end_date specifies the date when the Activity actually finished.

See activity to date_time for the application assertion.

The actual_end_date need not be specified for a particular Activity.

4.2.2.3 actual_start_date

The actual_start_date specifies the date when the Activity actually started.

See activity to date_time for the application assertion.

The actual_start_date need not be specified for a particular Activity.

4.2.2.4 chosen_method

The chosen_method specifies the Activity_method used to carry out the Activity.

See activity to activity_method for the application assertion.

The chosen_method need not be specified for a particular Activity.

4.2.2.5 concerned_organization

The concerned_organization specifies the set of Organization objects that are affected by the result of the Activity.

EXAMPLE The production site that has to change a manufacturing process due to a design change activity is an example for concerned_organization.

See activity to organization for the application assertion.

4.2.2.6 description

The description specifies additional information about the Activity.

See activity to multi_language_string for the application assertion.

The description need not be specified for a particular Activity.

If present, there shall be exactly one object that defines the description for an Activity.

4.2.2.7 id

The id specifies the identifier of the Activity.

4.2.2.8 internal

The internal specifies whether the activity is carried out within the organization that initiated the activity. A value of 'true' indicates that the activity is carried out within this particular organization.

The internal need not be specified for a particular Activity.

4.2.2.9 planned_end_date

The planned_end_date specifies the date when the Activity is or was supposed to be finished.

See activity to date_time, activity to duration, and activity to event_reference for the application assertions.

The planned_end_date need not be specified for a particular Activity.

If present, there shall be exactly one object that defines the planned_end_date for an Activity.

4.2.2.10 planned_start_date

The planned_start_date specifies the date when the Activity is or was supposed to be started.

See activity to date_time and activity to event_reference for the application assertions.

The planned_start_date need not be specified for a particular Activity.

If present, there shall be exactly one object that defines the planned_start_date for an Activity.

4.2.2.11 requestor

The requestor specifies the Person or Organization that requested the Activity and the date the request was submitted.

See activity to date_and_person_organization for the application assertion.

The requestor need not be specified for a particular Activity.

4.2.2.12 resolved_request

The resolved_request specifies the set of Work_request objects that are resolved by the Activity.

See activity to work_request for the application assertion.

4.2.2.13 status

The status specifies the level of completion of the Activity.

EXAMPLE The value 'open' is an example for status.

NOTE The values and sequence of status are company specific.

The status need not be specified for a particular Activity.

4.2.2.14 supplying_organization

The supplying_organization specifies the set of Organization objects that carry out the work.

See activity to organization for the application assertion.



© ISO 2010 — All rights reserved