| Capability (C024):— report_activity_progress | Date: 2004/01/08 11:28:41 Revision: 1.7 |
This section describes the EXPRESS information model for the capability.
TYPE activity_item =
EXTENSIBLE
GENERIC_ENTITY
SELECT;
END_TYPE;
EXAMPLE Change, distilling, design, a process to drill a hole, and a task such as training someone, are examples of activities.
NOTE 1 Status information identifying the level of completion of each activity may be provided within an instance of Activity_status.
NOTE 2 The items that are affected by an Activity, for example as input or output, may be identified within an instance of Applied_activity_assignment.
ENTITY Activity;
id : STRING;
name : STRING;
description :
OPTIONAL
STRING;
chosen_method : Activity_method;
END_ENTITY;
id: the identifier that distinguishes the Activity.
name: the words by which the Activity is known.
description: the text that provides further information about the Activity. The value of the attribute need not be specified.
chosen_method: the Activity_method that specifies the procedure selected to carry out the Activity.
EXAMPLE The activity required to complete a work order, may be decomposed into a series of activities. Their corresponding instances would be related using instances of the Activity_relationship entity.
ENTITY Activity_relationship;
name : STRING;
description :
OPTIONAL
STRING;
relating_activity : Activity;
related_activity : Activity;
END_ENTITY;
name: the words by which the Activity_relationship is known.
description: the text that provides further information about the Activity_relationship. The value of the attribute need not be specified.
relating_activity:
the first of the instances of Activity that is part of the relationship.
NOTE 1 The relating_activity usually identifies the activity the definition of the related_activity is based on, for example, derived from or dependent on.
NOTE 2 The meaning of this attribute is defined by the name attribute.
related_activity:
the second instance of Activity that is part of the relationship.
NOTE 3 The related_activity usually identifies the Activity, which is based on the definition of the relating_activity.
NOTE 4 The meaning of this attribute is defined by the name attribute.
ENTITY Activity_status;
assigned_activity : Activity;
status : STRING;
END_ENTITY;
assigned_activity: the Activity to which the Activity_status applies.
status: the label that provides a user interpretable designation for the level of completion of the Activity.
NOTE This entity should not be used to represent the association of an activity with the organizations that are responsible for its execution or its management. That kind of information can be represented with instances of Organization_or_person_in_organization_assignment .
ENTITY Applied_activity_assignment;
assigned_activity : Activity;
items : SET[1:?] OF activity_item;
role : STRING;
END_ENTITY;
assigned_activity: the Activity that is considered.
items: the set of activity_item that are associated with the assigned_activity.
role:
the text that specifies the purpose of the association of the Applied_activity_assignment with product or activity data.
Where applicable, the following values shall be used for role:
EXAMPLE Presence of a gas tube may constrain the execution of drilling of a hole.
NOTE 1 A Calendar_date or Date_time should be assigned to the Activity_actual with the role "start date" to record when the activity started.
NOTE 2 A Calendar_date or Date_time may be assigned to the activity with role "end date" to record when the activity finished. In general, the absence of this assignment cannot be used to infer that the activity is continuing, only that the end of the activity has not yet been recorded.
NOTE 3 A more detailed history of the progress of an activity may be recorded by applying states to the activity, but the meaning of these states must be defined through local business rules.
ENTITY Activity_actual
SUBTYPE OF (Activity);
END_ENTITY;
NOTE 1 The ordinary value for name may be "actual", though this is redundant.
NOTE 2 Many Activity_actuals may be the actual for a single Activity.
EXAMPLE 1 a single defined activity is recorded historically by several sub-activities.
NOTE 3 A single Activity_actual may fulfil several activities.
EXAMPLE 2 a single servicing activity takes the opportunity to make additional checks and repairs.
ENTITY Activity_happening
SUBTYPE OF (Activity_relationship);
SELF\Activity_relationship.relating_activity RENAMED actual : Activity_actual;
SELF\Activity_relationship.related_activity RENAMED predicted : Activity;
WHERE
WR1: NOT ('ACTIVITY_AS_REALIZED.ACTIVITY_ACTUAL' IN TYPEOF(predicted));
END_ENTITY;
actual: the Activity which is the record of the historical occurrence.
predicted: the Activity as defined in advance of its historical occurrence.