Template:— representing_activity_actual (rep_act_act) |
Date: 2008/01/18 08:58:19 Revision: 1.29
|
This section specifies the template representing_activity_actual.
NOTE
An explanation of a template and the associated instantiation path is
provided in the
Template overview
section.
This template describes how to represent a record of an activity that has at
least started and may have finished - an actual activity.
It can be used to record any information about an actual activity, such as who has performed and/or
reported the activity, what typical activity was followed, and when the activity was performed. It is
mandatory to assign an identifier or name to the activity, and a start or end time, and to relate
it to a typical activity (method).
This template should only be used for activities that
are neither performed by a product, or activities, such as configuration
change activities, that have been undertaken in response to
an activity (a Directed_activity) that has been authorized
by a Work_order.
Where the activity is work planned to be done on a product and authorised
by a Work_order, the template
representing_work_order
should be used.
Where the activity is planned to take place
some time in the future but is not authorized by a work order i.e. directed, the template
representing_planned_activity
should be used.
Where the activity is work that has been done to a product in response to
a planned activity (a Directed_activity) that has been authorized
by a Work_order, the template
representing_work_done
should be used.
Where the activity is a record of a usage of a product that has taken place, e.g.
a sortie flown by an aircraft , the template
representing_product_usage
should be used.
The EXPRESS-G diagram in
Figure
1
shows the templates and EXPRESS entities that are required
to represent the template
"representing_activity_actual".
The text highlighted in blue shows the template parameters.
Entities in the grey areas are not included in the template, but may be used to further
characterize the template.
Relations between the actual activity (product_usage) and a planned activity is instantiated through
Activity_happening.
Figure 1 — An EXPRESS-G representation of the Information model for representing_activity_actual
The graphic for the template to be used in other EXPRESS-G diagrams
is shown in Figure
2
below.
Figure 2 — The graphical representation of the representing_activity_actual template
The following input parameters are defined for this template:
The identifier of the Activity_actual.
id_class_name (Default=Activity_identification_code,Type='CLASS')
The name of the class being used to classify the identification
(
Identification_assignment)
of the actual activity. This provides the role or reason for the identification.
The following classes and their sub-classes can be used:
id_ecl_id (Default=urn:plcs:rdl:std,Type='URN')
The identifier of the
External_class_library
storing the definition of the class referenced by the parameter @id_class_name class.
The name or identifier of the organization owning the identifier or name.
The name of the class being used to classify the
identification of the organization. For example CAGE code, or organization name.
The following classes and their sub-classes can be used:
The typical activity of which this activity_actual is an instance,
or other regulating method.
The name of the class being used to classify the date or time. Must be either a start or an end date or time.
The following classes and their sub-classes can be used:
The year component of the date and time the activity was started or completed.
The month component of the date and time the activity was started or completed.
The day component of the date and time the activity was started or completed.
The hour component of the date and time the activity was started or completed.
The minute component of the date and time the activity was started or completed.
This parameter is optional. If not given, it will remain unset.
The second component of the date and time the activity was started or completed.
This parameter is optional. If not given, it will remain unset.
The direction that the time the activity was started or completed is offset from Coordinated Universal
Time.
Enumeration values are: 'ahead', 'exact' or 'behind'.
The number of hours by which the time the activity was started or completed is offset from Coordinated Universal
Time.
The number of minutes by which the time the activity was started or completed is offset from Coordinated Universal
Time.
The value of this attribute need not be specified.
This parameter is optional. If not given, it will remain unset.
The following reference parameters are defined for this template:
Allow the
Activity_actual
entity instantiated in this path to be referenced when this template is used.
%^target = $representing_activity_actual.act_act%
Allows referencing of entity Activity_actual from outside the template, e.g.
in order to characterize the Activity_actual further.
The following parameter combinations specify a uniqueness constraint:
Unique constraint: Unique activity actual
The instantiation path shown below specifies the entities that are to be
instantiated by the template.
A description of templates and the syntax for the instantiation path is
provided in the
Templates Help/Information section.
-- instantiate Activity_actual Activity_actual%^act_act =
Activity_actual%
^act_act.id = '/IGNORE'
^act_act.name = '/IGNORE'
^act_act.description = '/IGNORE'
^act_act.chosen_method ->
@method-- assign ID to activity_actual /
assigning_identification(
id=@id,
id_class_name=@id_class_name,
id_ecl_id=@id_ecl_id,
org_id=@id_owner,
org_id_class_name=@id_owner_class_name,
org_id_ecl_id=@id_owner_ecl_id,
items=^act_act)/
-- assigning an actual date of the activity_actual /
assigning_time(
date_class_name=@date_class_name,
date_ecl_id=@date_ecl_id,
year=@year,
month=@month,
day=@day,
hour=@hour,
minute=@minute,
second=@second,
sense=@sense,
hour_offset=@hour_offset,
minute_offset=@minute_offset,
items= ^act_act)/
The following entities are instantiated with attributes as specified:
The instance diagram in Figure
3
shows an example of the EXPRESS entities and templates that are instantiated by the template:
/representing_activity_actual(id='Quotation_121', id_class_name='Activity_identification_code', id_ecl_id='urn:plcs:rdl:std', id_owner='Express Delivery Inc', id_owner_class_name='Organization_name', id_owner_ecl_id='urn:plcs:rdl:std', method='#34', date_class_name='Date_actual_start', date_ecl_id='urn:plcs:rdl:std', year='2007', month='01', day='23', hour='23', minute='11', second='07', sense='.EXACT.', hour_offset='', minute_offset='')/
(an illustration of the consolidated representing_activity_actual template is shown in
Figure
4 below.)
Figure 3 — Entities instantiated by representing_activity_actual template
The instance diagram in
Figure
4
shows the graphic symbol for the template that is to be
used in other instance diagrams. The example template is:
/representing_activity_actual(id='Quotation_121', id_class_name='Activity_identification_code', id_ecl_id='urn:plcs:rdl:std', id_owner='Express Delivery Inc', id_owner_class_name='Organization_name', id_owner_ecl_id='urn:plcs:rdl:std', method='#34', date_class_name='Date_actual_start', date_ecl_id='urn:plcs:rdl:std', year='2007', month='01', day='23', hour='23', minute='11', second='07', sense='.EXACT.', hour_offset='', minute_offset='')/
Figure 4 — Instantiation of representing_activity_actual template
The following section details how the
representing_activity_actual
template can be optionally characterized by assigning
other constructs to it. These are characterizations commonly
applied to the template. The ISO 10303-239 EXPRESS model may enable
other assignments to the entities instantiated by the template.
The EXPRESS-G diagram in Figure
5
shows the possible characterizations of the template
"representing_activity_actual".
Figure 5 — Characterizations for representing_activity_actual template
The following characterizations may apply:
Characterization Assigning classification or code
NOTE this characterization is optional.
Characterization Assigning organization or person in organization
NOTE this characterization is optional.
Characterization Assigning state
NOTE this characterization is optional.
Characterization Assigning location
NOTE this characterization is optional.
A location can be associated to the actual activity
by using the template
assigning_location. See
Figure 1
for an Express-G overview.
The location may be expressed as a global location, an address-based location, an organization-based location,
or as a location in a regional grid. See further Capability C049: assigning_location (NB Capabilities are not documented in this release of the PLCS standard)
.
The assignment of the location
(assigning_location)
may be classified e.g. as 'Actual_start_location' or 'Actual_maintenance_location'.