representing_typical

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 typical activity that something or someone may undertake. A typical activity defines the approach to or method used for undertaking an activity.

For a typical activity that represents a structured set of processes, then the typical activity will be related to tasks which define the structured set of processes. For further details see: C015: representing_task (NB Capabilities are not documented in this release of the PLCS standard) . If the activities or tasks are to be scheduled, then the schedule is represented by a Scheme. For further details see: C062: representing_scheme (NB Capabilities are not documented in this release of the PLCS standard) .

The following templates are used to represent activities planned or undertaken in accordance with the typical activity. These activities are related back to the typical activity.

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.
Where the activity is a record of an activity that has taken place that is neither an authorized activity i.e. not authorized by a Work_order such as part of a directed change or technical bulletin, nor an activity performed by a product the more generic template representing_activity_actual should be used.

The following input parameters are defined for this template:

The following reference parameters are defined for this template:

The following parameter combinations specify a uniqueness constraint:

Unique constraint: Unique typical activity

Each instance of the entity (Activity_method) within the data set shall be uniquely identified by a combination of the following parameters on this template (representing_typical_activity) namely: id, id_class_name, id_ecl_id, id_owner, id_owner_class_name, id_owner_ecl_id.
The instance is referenced by the following template parameter: act_method.

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.

The following entities are instantiated with attributes as specified:

Entity in path	Value	Inherited from
Activity_method.name	'/IGNORE'	—
Activity_method.purpose	'/IGNORE'	—
Activity_method.description	'/IGNORE'	—
Activity_method.consequence	'/IGNORE'	—

The following section details how the representing_typical_activity 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 following characterizations may apply:

Characterization Specification of the typical activity

NOTE this characterization is mandatory.

A typical activity must be specified in some way. There are several alternative routes to do this,

by assigning a text definition of the typical activity,
by assigning a document describing the activity in more detail, or
by breaking the typical activity up into a structured set of processes (steps).

At least one of these alternatives must be used. See Figure 1 for an Express-G overview

A textual definition is represented by assigning a descriptor to the typical activity using the assigning_descriptor template.

A document describing the typical activity is assigned using template assigning_document with the Document_assignment classified as "Definition assignment" (urn:plcs:rdl:std:Definition assignment).

A structured set of processes or steps of a typical activity is represented using Activity_method_realization to relate e.g. a Task_method or Scheme to the Activity_method.

NOTE These alternatives are not mutually exclusive, they can be used at the same time.

Characterization Assigning products

NOTE this characterization is optional.

A product or a group of products can be assigned to the typical activity, classified as e.g. "activity input" and "product usage". See Figure 1 for an Express-G overview.

For a typical activity to be performed on a product or group of products, an Applied_activity_method_assignment, classified as "Activity input" (urn:plcs:rdl:std:Activity input), is used to relate the product to the activity as an "activity input".

This is done using template assigning_activity with the input parameter role_class_name given the value "Activity input" (urn:plcs:rdl:std:Activity input).

For a typical activity to be performed by a product, an Applied_activity_method_assignment, classified as "Product usage" (urn:plcs:rdl:std:Product usage), is used to relate the product to the activity as the product to be used ("product_usage").

This is done using template assigning_activity with the input parameter role_class_name given the value "Product usage" (urn:plcs:rdl:std:Product usage).

Characterization Assigning approval

NOTE this characterization is optional.

A typical activity may be approved, e.g. approved for use. See Figure 1 for an Express-G overview.

An approval of the typical activity is represented by assigning a Approval to the Activity_method using the assigning_approval template.

NOTE The assignment of approvals is described the capability C019: assigning_approvals (NB Capabilities are not documented in this release of the PLCS standard) .

Characterization Assigning person or organization

NOTE this characterization is optional.

A person or organization may be assigned to a typical activity, classified as e.g. "creator" or "owner" of the activity. See Figure 1 for an Express-G overview.

NOTE This characterization is not intended to assign persons or organizations as a resource to an activity. To assign types of persons or organizations as a resource to an activity, see characterization "assigning resources".

An organization is associated to a typical activity by using the template assigning_organization. The assignment of the organization (Organization_or_person_in_organization_assignment) must be classified, e.g. as "Owner_of".

A person in an organization is associated to a typical activity by using the template assigning_person_in_organization. The assignment of the person (Organization_or_person_in_organization_assignment) must be classified, e.g. as "Creator".

Characterization Assigning required resources

NOTE this characterization is optional.

Required resources, such as required type of person, required location, etc, may be assigned to a typical activity. See Figure 1 for an Express-G overview.

An required resource is associated to a typical activity by using Required_resource_assignment, classified appropriately.

Characterization Assigning properties

NOTE this characterization is optional.

Properties, e.g. estimated duration, can be assigned to a typical activity. See Figure 1 for an Express-G overview.

A property is represented by Activity_property assigned to the Activity_method, using template assigning_process_property.

NOTE The assignment of process properties are described further in capability C077: assigning_process_properties (NB Capabilities are not documented in this release of the PLCS standard) .

Figure 6 — A property assigned to a typical activity