|
|
Application module:
Activity |
ISO/TS 10303-1047:2014-02(E)
© ISO
|
This clause specifies the information requirements for the
Activity
application module. The information requirements are specified as the
Application Reference Model (ARM) of this application module.
NOTE 1 A graphical representation of the information
requirements is given in
Annex C.
NOTE 2 The mapping specification is specified in
5.1. It shows how
the information requirements are met by using common resources and
constructs defined or imported in the MIM schema of this application
module.
This clause defines the information requirements to which implementations shall
conform using the EXPRESS language as defined in ISO 10303-11.
The following begins the
Activity_arm
schema and identifies the necessary external references.
EXPRESS specification:
*)
SCHEMA Activity_arm;
(*
The following EXPRESS interface statement specifies the elements
imported from the ARM of another application module.
EXPRESS specification:
*)
USE FROM
Activity_method_arm;
--
ISO/TS 10303-1049
(*
NOTE 1
The schemas referenced above are specified in the following
part of ISO 10303:
| Activity_method_arm |
ISO/TS 10303-1049 |
NOTE 2
See Annex C,
Figures
C.1and C.2
for a graphical representation of this schema.
This subclause specifies the ARM type
for this application module. The ARM type and
definition is specified below.
The activity_item type is an
extensible list of alternate data types.
Additional alternate data types are specified in select data
types that extend the
activity_item type.
NOTE
This empty extensible select requires
extension in a further module to ensure that entities that refer to it have
at least one valid instantiation.
EXPRESS specification:
*)
TYPE
activity_item =
EXTENSIBLE
GENERIC_ENTITY
SELECT;
END_TYPE;
(*
This subclause specifies the ARM entities for this
module. Each ARM application entity is an atomic element that
embodies a unique application concept and contains attributes
specifying the data elements of the entity. The ARM
entities and definitions are specified below.
An Activity is the identification of the occurrence of an action that has taken place, is taking place, or is expected to take place
in the
future.
The procedure executed during that Activity is identified with the Activity_method that is referred to by the chosen_method attribute.
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.
EXPRESS specification:
*)
ENTITY Activity;
id : STRING;
name : STRING;
description :
OPTIONAL
STRING;
chosen_method : Activity_method;
END_ENTITY;
(*
Attribute definitions:
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 approach selected to carry out the
Activity.
An Activity_relationship is a relationship between two instances of
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.
EXPRESS specification:
*)
ENTITY Activity_relationship;
name : STRING;
description :
OPTIONAL
STRING;
relating_activity : Activity;
related_activity : Activity;
END_ENTITY;
(*
Attribute definitions:
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.
An Activity_status is the assignment of a status to an Activity
.
EXPRESS specification:
*)
ENTITY Activity_status;
assigned_activity : Activity;
status : STRING;
END_ENTITY;
(*
Attribute definitions:
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.
An Applied_activity_assignment is an association of an
Activity
with product or activity data. It characterizes the role of the concepts represented with these data with respect to 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
.
EXPRESS specification:
*)
ENTITY Applied_activity_assignment;
assigned_activity : Activity;
items : SET[1:?] OF activity_item;
role : STRING;
END_ENTITY;
(*
Attribute definitions:
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:
*)
END_SCHEMA; -- Activity_arm
(*
© ISO 2014 — All rights reserved
