Capability (C053):— representing_periodicity Date: 2007/07/11 16:32:00
Revision: 1.16

Business DEX overview

This capability provides the ability to define information about periodicity with or without tolerances. Examples of periodicities that can be represented are:

Information model overview

Representing periodicity as a value with unit

Periodicities such as elapsed time and number of cycles are representated as Value_limit. The value of the periodicity is represented as Value_with_unit.

EXAMPLE    Examples of values of periodicity are 5 hours, 20 hours of operation, 500 rounds of amunition etc.

Representing periodicity as a value with unit including tolerances

Periodicity with tolerances is representated as Value_with_tolerances. The value of the periodicity is represented as Numerical_item_with_unit and the tolerances are represented as Value_range which represents the values of both the lower_limit and the upper_limit.

EXAMPLE    Examples of values of periodicity with tolerances are 50 hours of operation +/- 10 hours of operation.



Figure 1 —  Example of periodicity as value with unit with tolerances.

Figure 1 —  Example of periodicity as value with unit with tolerances.

 

Representing periodicity as text based description

Periodicity expressed as text based descriptions is representated as String_representation_item. The description of the periodicity is represented as the string_value attribute of String_representation_item



Figure 2 —  Example of periodicity as a text based description.

Figure 2 —  Example of periodicity as a text based description.

 

Assigning periodicity

The association between the entities representing the periodicity and the entity that's being assigned with the periodicity is established using the Activity_property.

NOTE    The entity assigning the periodicity should be classified as "Periodicity" (urn:plcs:rdl:std:Periodicity) using the C010: assigning_reference_data capability.



Figure 3 —  Example of assigning a periodicity to a task when performed on a specific part.

Figure 3 —  Example of assigning a periodicity to a task when performed on a specific part.

 

Multiple periodicity representations

In situations where there's a requirement for multiple representations of one and the same periodicity, this is resolved by associating the Representation  items attribute with multiple Representation_items, one for each representation.



Figure 4 —  Example of multiple representations of the same periodicity.

Figure 4 —  Example of multiple representations of the same periodicity.

 

Related capabilities

This capability "Representing periodicity with tolerances" is related to the following capabilities:

Dependent capabilities

This capability "Representing periodicity with tolerances" is dependent on the following capabilities:

Model reference data

The following classes of reference data are required for this capability:

Periodicity(urn:plcs:rdl:std:Periodicity)
independent property that defines the interval between activities. Note: This may be defined as time interval or as number of events, such as number of landings.

© OASIS 2010 — All rights reserved