Capability (C084):— representing_property_value

Capability (C084):— representing_property_value_ranges

Date: 2007/06/22 12:22:11
Revision: 1.13

Cover Contents Intro.Overview Info. model Templates Capabilities.Issues

Business overview

This section provides a business level overview of this capability.

Part specifications are composed of properties and their allowed values. Property values may be complex, such as vectors, tensors, or distributions, but for purposes of specification and measurement, they reduce to one or more simple numerical values, and an allowed value for each which is just a range of numbers. A part conforms to an aspect of a specification if the property value lies within the specified ranges.

PLCS provides the capability to specify a range of numbers in several ways:

a nominal value, a plus deviation, and minus deviation;

EXAMPLE Mass = 5.0 +/- 0.5 kg.
a range given by an ordered pair thus ( minimum, maximum);
a one sided limit, either minimum or maximum

Information model overview

This section provides an overview of the information model that supports this capability.

An EXPRESS-G diagram for the model used in representing property value ranges is shown in Figure 1 below.

Figure 1 — Entities Used for Representation of Property Value Ranges

To represent a property value that is a numeric range , the following entities (and their subtypes) are required:

Value_range - This entity represents a numerical range by specifying two instances of Numerical_item_with_unit that are the upper and lower limits of the range.
Value_limit - This entity represents a maximum or minimum value by specifying the Numerical_item_with_unit that represents the limit value, and a flag to indicate whether the limit to be interpreted as a minimum or a maximum value.
Value_with_tolerances - This entity represents a numerical range by specifying a Numerical_item_with_unit that represents a nominal value and two attributes defining the upper and lower tolerance limits. The numerical range is constructed from these by adding the nominal value to each limit. The Value_with_tolerances represents the a tolerance range about some number.
NOTE Either limit may be positive or negative, and they may be the same or different.
Numerical_representation_context (see C079: representing_properties_numerically)
Numerical_item_with_unit (see C079: representing_properties_numerically)
Property_value_representation (see C079: representing_properties_numerically)
Unit (see C096: representing_value_with_unit )

The Property_value_representation is assigned to a property through the following entities:

Property_representation for product properties (see C076: assigning_product_properties)
Activity_property_representation for activity properties (see C077: assigning_process_properties)
Resource_property_representation for resource properties (see C078: assigning_resource_properties)

Value limit

Figure 2 shows the use of value limit to establish a property value that is 5.05 kg. or less. Only Value_limit is included in the list of items

Figure 2 — Instances Used for Value_limit

Value range

Figure 3 shows the use of Value_range to establish a property value that is between 4.95 kg. and 5.05 kg. Only Value_limit is included in the list of items

Figure 3 — Instances Used for Value_range

Value with tolerances

Figure 4 shows the use of Value_with_tolerances to establish a property value that is between 4.97 kg. and 5.07 kg. This construct is semantically identical to a Value_range between these two values, it is just a different parameterization. Only Value_with_tolerances is included in the list of items

Figure 4 — Instances Used for Value_with_tolerances

Use of external reference data for units

The use of external reference data for Units is described in Capability C096: representing_value_with_unit.

Characterization of property value ranges

Characterization of Property_value_representation is discussed in C079: representing_properties_numerically. No additional characterization capability is introduced in C084: representing_property_value_ranges

Capability templates

The following sections define a set of templates for the capability, where a template is a specification of a set of entities that need to be instantiated to represent a given set of information.

Template: representing_value_limit (Short name: rep_limit)

This section specifies the template representing_value_limit.

NOTE An explanation of a template and the associated instantiation path is provided in the Template overview section.

Description

This template describes how to represent a value limit with associated unit for any property.

EXAMPLE The maximum weight (in kilograms) of an item.

NOTE The definition of the property itself (e.g. weight) and the item to which it may be assigned, are not in scope of this template. This template provides for the value limit and associated unit for the value.

Model diagrams

The EXPRESS-G diagram in Figure 1 shows the templates and EXPRESS entities that are required to represent the template "representing_value_limit". The text highlighted in blue shows the template parameters.

Figure 1 — An EXPRESS-G representation of the Information model for representing_value_limit

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 representing_value_limit template

Input parameters

The following input parameters are defined for this template:

limit (Type= 'TYPE (any_number_value)' )

The value of the property. The datatype is always 'any_number_value' and should not be registered together with the value i.e. enter the value as a number, without the datatype.

qualifier (Default=maximum,Type= 'ENUMERATION (limit_qualifier_list)' )

The qualifier of the limit value, either 'maximum' or 'minimum'.

si_unit (Type='BOOLEAN')

Value should be set to true if the unit is a SI base unit defined by ISO, i.e. kilogram (kg) for Mass, second (s) for Time, metre (m) for Displacement, ampere (A) for Electrical current, kelvin (K) for Temperature, mole (mol) for Amount of substance, and candela (cd) for Luminous intensity. If this is not the case it should be set to false.
Note that the representation of true and false depends on exchange format. In Part 11 and Part 21 (STEP file) true is represented by the string ".T.", and false by ".F.", while in Part 28 (XML) they are represented by text strings "true" and "false".

unit (Type='CLASS')

The class name of the unit in which the value is expressed.

The following classes and their sub-classes can be used:

classifications: "Context_dependent_unit" (urn:plcs:rdl:std:Context_dependent_unit)

unit_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 @unit.

context (Type='CLASS')

The name of the class being used to classify the representation context (Numerical_representation_context) of the property.

The following classes and their sub-classes can be used:

classifications: "Numerical_representation_context" (urn:plcs:rdl:std:Numerical_representation_context)

context_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 @context.

Reference parameters

The following reference parameters are defined for this template:

representation(Type='ENTITY (Property_value_representation)')

Allow the Property_value_representation entity instantiated in this path to be referenced when this template is used.

Note: The Property_value_representation entity can be referenced in a template path by:

%^target = $representing_value_limit.representation%

where target is the parameter to which the Property_value_representation is bound.

num_rep_cntxt(Type='ENTITY (Numerical_representation_context)')

Allow the Numerical_representation_context entity instantiated in this path to be referenced when this template is used.

Note: The Numerical_representation_context entity can be referenced in a template path by:

%^target = $representing_value_limit.num_rep_cntxt%

where target is the parameter to which the Numerical_representation_context is bound.

Uniqueness constraints

The following parameter combinations specify a uniqueness constraint:

Unique constraint: Unique numerical representation context

Each instance of the entity (Numerical_representation_context) within the data set shall be uniquely identified by a combination of the following parameters on this template (representing_value_limit) namely: context, context_ecl_id.
The instance is referenced by the following template parameter: num_rep_cntxt.

There will be one numerical context for the representation of a value.

Instantiation path

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 Reading Capability Templates help section.

-- Instantiate Property_value_representation entity
Property_value_representation

-- Set the Property_value_representation attributes id, name and description to be ignored
Property_value_representation.id = '/IGNORE'
Property_value_representation.name = '/IGNORE'
Property_value_representation.description = '/IGNORE'

-- Bind the Property_value_representation to the parameter ^representation.
-- The parameter is a reference parameter so the Property_value_representation
-- entity can be referred to when this template is used.
%^representation = Property_value_representation%

-- Instantiate Numerical_representation_context and assign
%^num_rep_cntxt = Numerical_representation_context%

-- Set the Numerical_representation_context attributes id and kind to be ignored
Numerical_representation_context.id = '/IGNORE'
Numerical_representation_context.kind = '/IGNORE'

-- Property_value_representation at it
^representation.context_of_items -> ^num_rep_cntxt

-- Assign reference data for kind of Numerical_representation_context
/assigning_reference_data(
    items=^num_rep_cntxt,
    class_name=@context,
    ecl_id=@context_ecl_id)/

-- Instantiate Value_limit and assign
-- Property_value_representation to it
^representation.items -> Value_limit

-- Set the Value_limit attributes
Value_limit.name = '/IGNORE'
Value_limit.limit_qualifier = @qualifier

-- Instantiate template representing_numerical_item
-- for value
/representing_numerical_item(
    value= @limit,
    unit= @unit,
    unit_ecl_id= @unit_ecl_id,
    si_unit= @si_unit)/

-- Bind ref param ^item in just instantiated template
-- representing_numerical_item to ref param ^item in this template,
-- and point attribute Value_with_tolerances.item_value to it
%^item = $representing_numerical_item.item%
Value_limit.limit -> ^item

The following entities are instantiated with attributes as specified:

Entity in path	Value	Inherited from
Property_value_representation.id	'/IGNORE'	Representation.id
Property_value_representation.name	'/IGNORE'	Representation.name
Property_value_representation.description	'/IGNORE'	Representation.description
Numerical_representation_context.id	'/IGNORE'	Representation_context.id
Numerical_representation_context.kind	'/IGNORE'	Representation_context.kind
Value_limit.name	'/IGNORE'	Representation_item.name
Value_limit.limit_qualifier	@qualifier	—

Instance diagrams

The instance diagram in Figure 3 shows an example of the EXPRESS entities and templates that are instantiated by the template:

/representing_value_limit(limit='any_number_value(5.2)', qualifier='maximum', unit='kilogram', unit_ecl_id='urn:plcs:rdl:std', si_unit='true', context='Calculated_in_design', context_ecl_id='urn:plcs:rdl:std')/

(an illustration of the consolidated representing_value_limit template is shown in Figure 4 below.)

Figure 3 — Entities instantiated by representing_value_limit 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:

Figure 4 — Instantiation of representing_value_limit template, related to an assigned product property

Characterizations

The following section details how the representing_value_limit 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_value_limit".

Figure 5 — Characterizations for representing_value_limit template

The following characterizations may apply:

Characterization Assigning time

NOTE this characterization is optional.

Time (and dates) can be associated with the assignment of property value representation as in Figure 5. This is described in C079: representing_properties_numerically, template representing_numeric_property. No additional characterization capability is introduced in this template.

Characterization Assigning organization

NOTE this characterization is optional.

An Organization (or a Person_in_organization) can be associated with the property value representation as in Figure 5. This is described in C079: representing_properties_numerically, template representing_numeric_property. No additional characterization capability is introduced in this template.

Template: representing_value_range (Short name: rep_range)

This section specifies the template representing_value_range.

NOTE An explanation of a template and the associated instantiation path is provided in the Template overview section.

Description

This template describes how to represent a property value range (with units) for any property.

EXAMPLE The weight of an item may range in weight from 5.05 down to 4.95 kilgrames.

The range (in terms of upper and lower values) of a property value defined in specific units (e.g. time, length etc..) that may be associated with an item.

NOTE The specification and definition of the property and the item to which it is associated, are outside the scope of this template. This template, however, defines the representation andvalues (range of) that may be associated with such a property.

Model diagrams

The EXPRESS-G diagram in Figure 1 shows the templates and EXPRESS entities that are required to represent the template "representing_value_range". The text highlighted in blue shows the template parameters.

Figure 1 — An EXPRESS-G representation of the Information model for representing_value_range

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 representing_value_range template, related to a resource property

Input parameters

The following input parameters are defined for this template:

upper_limit (Type= 'TYPE (any_number_value)' )

The upper limit value of the property. The datatype must also be indicated in this parameter, e.g. "ANY_NUMBER_VALUE(5)".

lower_limit (Type= 'TYPE (any_number_value)' )

The lower limit value of the property. The datatype must also be indicated in this parameter, e.g. "ANY_NUMBER_VALUE(5)".

unit (Type='CLASS')

The class name of the unit in which the value is expressed.

The following classes and their sub-classes can be used:

classifications: "Unit" (urn:plcs:rdl:std:Unit)

unit_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 @unit.

si_unit (Default=false,Type='BOOLEAN')

Value should be set to true if the unit is a SI base unit defined by ISO, i.e. kilogram (kg) for Mass, second (s) for Time, metre (m) for Displacement, ampere (A) for Electrical current, kelvin (K) for Temperature, mole (mol) for Amount of substance, and candela (cd) for Luminous intensity. If this is not the case it should be set to false.
Note that the representation of true and false depends on exchange format. In Part 11 and Part 21 (a STEP file) true is represented by the string ".T.", and false by ".F.", while in Part 28 (XML) they are represented by text strings "true" and "false".

context (Type='CLASS')

The name of the class being used to classify the representation context (Numerical_representation_context) of the property.

The following classes and their sub-classes can be used:

classifications: "Representation_context" (urn:plcs:rdl:std:Representation_context)

context_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 @context.

Reference parameters

The following reference parameters are defined for this template:

representation(Type='ENTITY (Property_value_representation)')

Allow the Property_value_representation entity instantiated in this path to be referenced when this template is used.

Note: The Property_value_representation entity can be referenced in a template path by:

%^target = $representing_value_range.representation%

where target is the parameter to which the Property_value_representation is bound.

num_rep_cntxt(Type='ENTITY (Numerical_representation_context)')

Allow the Numerical_representation_context entity instantiated in this path to be referenced when this template is used.

Note: The Numerical_representation_context entity can be referenced in a template path by:

%^target = $representing_value_range.num_rep_cntxt%

where target is the parameter to which the Numerical_representation_context is bound.

lower_item(Type='ENTITY (Numerical_item_with_unit)')

Allow the Numerical_item_with_unit entity instantiated in this path to be referenced when this template is used.

Note: The Numerical_item_with_unit entity can be referenced in a template path by:

%^target = $representing_value_range.lower_item%

where target is the parameter to which the Numerical_item_with_unit is bound.

upper_item(Type='ENTITY (Numerical_item_with_unit)')

Allow the Numerical_item_with_unit entity instantiated in this path to be referenced when this template is used.

Note: The Numerical_item_with_unit entity can be referenced in a template path by:

%^target = $representing_value_range.upper_item%

where target is the parameter to which the Numerical_item_with_unit is bound.

Uniqueness constraints

The following parameter combinations specify a uniqueness constraint:

Unique constraint: Unique numerical representation context

Each instance of the entity (Numerical_representation_context) within the data set shall be uniquely identified by a combination of the following parameters on this template (representing_value_range) namely: context, context_ecl_id.
The instance is referenced by the following template parameter: num_rep_cntxt.

There will be one numerical context for the representation of a value.

Instantiation path

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 Reading Capability Templates help section.

-- Instantiate Property_value_representation entity
Property_value_representation

-- Set the Property_value_representation attributes id, name and description to be ignored
Property_value_representation.id = '/IGNORE'
Property_value_representation.name = '/IGNORE'
Property_value_representation.description = '/IGNORE'

-- Bind the Property_value_representation to the parameter ^representation.
-- The parameter is a reference parameter so the Property_value_representation
-- entity can be referred to when this template is used.
%^representation = Property_value_representation%

-- Instantiate Numerical_representation_context and assign
%^num_rep_cntxt = Numerical_representation_context%

-- Set the Numerical_representation_context attributes id and kind to be ignored
Numerical_representation_context.id = '/IGNORE'
Numerical_representation_context.kind = '/IGNORE'

-- Property_value_representation at it
^representation.context_of_items -> ^num_rep_cntxt

-- Assign reference data for kind of Numerical_representation_context
/assigning_reference_data(
    items=^num_rep_cntxt,
    class_name=@context,
    ecl_id=@context_ecl_id)/

-- Instantiate Value_range and assign
-- Property_value_representation to it
^representation.items -> Value_range

-- Set the Value_range attribute name to be ignored
Value_range.name = '/IGNORE'

-- Instantiate template representing_numerical_item
-- for upper limit
/representing_numerical_item(
    value= @upper_limit,
    unit= @unit,
    unit_ecl_id= @unit_ecl_id,
    si_unit= @si_unit)/

-- Bind ref param ^item in just instantiated template
-- representing_numerical_item to ref param ^item in this template,
-- and point attribute Value_range.upper_limit to it
%^upper_item = $representing_numerical_item.item%
Value_range.upper_limit -> ^upper_item

-- Instantiate template representing_numerical_item
-- for lower limit
/representing_numerical_item(
    value= @lower_limit,
    unit= @unit,
    unit_ecl_id= @unit_ecl_id,
    si_unit= @si_unit)/

-- Bind ref param ^item in just instantiated template
-- representing_numerical_item to ref param ^item in this template,
-- and point attribute Value_range.lower_limit to it
%^lower_item = $representing_numerical_item.item%
Value_range.lower_limit -> ^lower_item

The following entities are instantiated with attributes as specified:

Entity in path	Value	Inherited from
Property_value_representation.id	'/IGNORE'	Representation.id
Property_value_representation.name	'/IGNORE'	Representation.name
Property_value_representation.description	'/IGNORE'	Representation.description
Numerical_representation_context.id	'/IGNORE'	Representation_context.id
Numerical_representation_context.kind	'/IGNORE'	Representation_context.kind
Value_range.name	'/IGNORE'	Representation_item.name

Instance diagrams

The instance diagram in Figure 3 shows an example of the EXPRESS entities and templates that are instantiated by the template:

/representing_value_range(upper_limit='ANY_NUMBER_VALUE(5.05)', lower_limit='ANY_NUMBER_VALUE(4.95)', unit='kilogram', unit_ecl_id='urn:plcs:rdl:std', si_unit='.T.', context='Representation_context', context_ecl_id='urn:plcs:rdl:std')/

(an illustration of the consolidated representing_value_range template is shown in Figure 4 below.)

Figure 3 — Entities instantiated by representing_value_range 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:

Figure 4 — Instantiation of representing_value_range template

Characterizations

The following section details how the representing_value_range 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_value_range".

Figure 5 — Characterizations for representing_value_range template

The following characterizations may apply:

Characterization Assigning time (and Dates)

NOTE this characterization is optional.

Time (and dates) can be associated with the assignment of a property value representation as shown in Figure 5, by using the templates assigning_time. An example of this is provided below.

Figure 6 — Characterization by date of representing_value_range template

The date of creation of the property value representation is represented by using the template assigning_time to assign a date and time to Property_value_representation (reference parameter ^representation in template representing_value_range). The date and time assignment is classified as: "Date actual creation" (urn:plcs:rdl:std:Date actual creation) to indicate that it is the date (and time) when the property value representation was actually created. This is illustrated in Figure 6.

Other dates may be assigned instead.

Characterization Assigning organization or person

NOTE this characterization is optional.

An Organization (or a Person_in_organization) can be associated with the property value representation (see the ^representation reference parameter), as in Figure 5. The creating organization is represented by using the template assigning_organization or assigning_person_in_organization assigned to Property_value_representation (reference parameter ^representation in template representing_value_range). The assignment of the organization (Organization_or_person_in_organization_assignment) is classified as: "Creator of" (urn:plcs:rdl:std:Creator of) to indicate that this organization created the property value representation. This is illustrated in Figure 7.

Figure 7 — Characterization by organization or person of representing_value_range template

Other roles of an organization with regard to a property value representation may be assigned instead.

Template: representing_value_w_tolerances (Short name: rep_val_tol)

This section specifies the template representing_value_w_tolerances.

NOTE An explanation of a template and the associated instantiation path is provided in the Template overview section.

Description

This template describes how to represent tolerances for any associated a property value.

This can be defined as the upper and lower tolerance limits associated with a particular value and unit.

EXAMPLE The design weight (property) of an item is declared as 35 kilograms and the tolerance associated with that value may allow the weight to increase (+) 0.5 kg, (e.g. to 35.5kg) or to decrease (-) 4.0kg, (e.g. to 31kg).

NOTE The upper and lower values are taken to equate to the traditional +/- (plus and minus) engineering tolerance definition that may be associated with a particular value (and unit). Hence the 'lower' limit should always be negative.

Model diagrams

The EXPRESS-G diagram in Figure 1 shows the templates and EXPRESS entities that are required to represent the template "representing_value_w_tolerances". The text highlighted in blue shows the template parameters.

Figure 1 — An EXPRESS-G representation of the Information model for representing_value_w_tolerances

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 representing_value_w_tolerances template

Input parameters

The following input parameters are defined for this template:

value (Type= 'TYPE (any_number_value)' )

The value of the property. The datatype is always 'any_number_value' and should not be registered together with the value, i.e. enter the value as a number, without datatype.

upper_limit (Default=0,Type='REAL')

The tolerance upper limit.

lower_limit (Default=0,Type='REAL')

The lower tolerance limit of the property value. This value should always be negative as upper_limit and lower_limit represent offsets from value, specifying a range of values defined as [value+lower_limit, value+upper_limit].

unit (Type='CLASS')

The class name of the unit in which the value is expressed.

The following classes and their sub-classes can be used:

classifications: "Unit" (urn:plcs:rdl:std:Unit)

unit_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 @unit.

si_unit (Type='BOOLEAN')

Value should be set to true if the unit is a SI base unit defined by ISO, i.e. kilogram (kg) for Mass, second (s) for Time, metre (m) for Displacement, ampere (A) for Electrical current, kelvin (K) for Temperature, mole (mol) for Amount of substance, and candela (cd) for Luminous intensity. If this is not the case it should be set to false.
Note that the representation of true and false depends on exchange format. In Part 21 (a STEP file) true is represented by the string ".T.", and false by ".F.", while in Part 28 (XML) they are represented by text strings "true" and "false".

context (Type='CLASS')

The name of the class being used to classify the representation context (Numerical_representation_context) of the property. The 'Representation context' defined below is a root classification. Other (subclasses) of this may be used instead.

The following classes and their sub-classes can be used:

classifications: "Representation_context" (urn:plcs:rdl:std:Representation_context)

context_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 @context.

Reference parameters

The following reference parameters are defined for this template:

representation(Type='ENTITY (Property_value_representation)')

Allow the Property_value_representation entity instantiated in this path to be referenced when this template is used.

Note: The Property_value_representation entity can be referenced in a template path by:

%^target = $representing_value_w_tolerances.representation%

where target is the parameter to which the Property_value_representation is bound.

num_rep_cntxt(Type='ENTITY (Numerical_representation_context)')

Allow the Numerical_representation_context entity instantiated in this path to be referenced when this template is used.

Note: The Numerical_representation_context entity can be referenced in a template path by:

%^target = $representing_value_w_tolerances.num_rep_cntxt%

where target is the parameter to which the Numerical_representation_context is bound.

Uniqueness constraints

The following parameter combinations specify a uniqueness constraint:

Unique constraint: Unique numerical representation context

Each instance of the entity (Numerical_representation_context) within the data set shall be uniquely identified by a combination of the following parameters on this template (representing_value_w_tolerances) namely: context, context_ecl_id.
The instance is referenced by the following template parameter: num_rep_cntxt.

There will be one numerical context for the representation of a value.

Instantiation path

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 Reading Capability Templates help section.

-- Instantiate Property_value_representation entity
Property_value_representation

-- Set the Property_value_representation attributes id, name and description to be ignored
Property_value_representation.id = '/IGNORE'
Property_value_representation.name = '/IGNORE'
Property_value_representation.description = '/IGNORE'

-- Bind the Property_value_representation to the parameter ^representation.
-- The parameter is a reference parameter so the Property_value_representation
-- entity can be referred to when this template is used.
%^representation = Property_value_representation%

-- Instantiate Numerical_representation_context and assign
-- Property_value_representation at it
%^num_rep_cntxt = Numerical_representation_context%

-- Set the Numerical_representation_context attributes id and kind to be ignored
Numerical_representation_context.id = '/IGNORE'
Numerical_representation_context.kind = '/IGNORE'
^representation.context_of_items -> ^num_rep_cntxt

-- Assign reference data for kind of Numerical_representation_context
/assigning_reference_data(
    items=^num_rep_cntxt,
    class_name=@context,
    ecl_id=@context_ecl_id)/

-- Instantiate Value_with_tolerances and assign
-- Property_value_representation to it
^representation.items -> Value_with_tolerances

-- Set the Value_with_tolerances attributes
Value_with_tolerances.name = '/IGNORE'
Value_with_tolerances.upper_limit = @upper_limit
Value_with_tolerances.lower_limit = @lower_limit

-- Instantiate template representing_numerical_item
-- for value
/representing_numerical_item(
    value= @value,
    unit= @unit,
    unit_ecl_id= @unit_ecl_id,
    si_unit= @si_unit)/

-- Bind ref param ^item in just instantiated template
-- representing_numerical_item to ref param ^item in this template,
-- and point attribute Value_with_tolerances.item_value to it
%^item = $representing_numerical_item.item%
Value_with_tolerances.item_value -> ^item

The following entities are instantiated with attributes as specified:

Entity in path	Value	Inherited from
Property_value_representation.id	'/IGNORE'	Representation.id
Property_value_representation.name	'/IGNORE'	Representation.name
Property_value_representation.description	'/IGNORE'	Representation.description
Numerical_representation_context.id	'/IGNORE'	Representation_context.id
Numerical_representation_context.kind	'/IGNORE'	Representation_context.kind
Value_with_tolerances.name	'/IGNORE'	Representation_item.name
Value_with_tolerances.upper_limit	@upper_limit	—
Value_with_tolerances.lower_limit	@lower_limit	—

Instance diagrams

The instance diagram in Figure 3 shows an example of the EXPRESS entities and templates that are instantiated by the template:

/representing_value_w_tolerances(value='ANY_NUMBER_VALUE(35)', lower_limit='-4.0', upper_limit='0.5', unit='kilogram', unit_ecl_id='urn:plcs:rdl:std', si_unit='.T.', context='Representation_context', context_ecl_id='urn:plcs:rdl:std')/

(an illustration of the consolidated representing_value_w_tolerances template is shown in Figure 4 below.)

Figure 3 — Entities instantiated by representing_value_w_tolerances 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:

Figure 4 — Instantiation of representing_value_w_tolerances template

Characterizations

The following section details how the representing_value_w_tolerances 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_value_w_tolerances".

Figure 5 — Characterizations for representing value with tolerances template

The following characterizations may apply:

Characterization Assigning time (and Dates)

NOTE this characterization is optional.

Time (and dates) can be associated with the assignment of a property value representation as shown in Figure 5, by using the templates assigning_time. An example of this is provided below.

Figure 6 — Characterization by date of representing_value_w_tolerances template

The date of creation of the property value representation is represented by using the template assigning_time to assign a date and time to Property_value_representation (reference parameter ^representation in template representing_value_w_tolerances). The date and time assignment is classified as: "Date actual creation" (urn:plcs:rdl:std:Date actual creation) to indicate that it is the date (and time) when the property value representation was actually created. This is illustrated in Figure 6.

Other dates may be assigned instead.

Characterization Assigning organization or person

NOTE this characterization is optional.

An Organization (or a Person_in_organization) can be associated with the property value representation (see the ^representation reference parameter), as in Figure 5. The creating organization is represented by using the template assigning_organization or assigning_person_in_organization assigned to Property_value_representation (reference parameter ^representation in template representing_value_w_tolerances). The assignment of the organization (Organization_or_person_in_organization_assignment) is classified as: "Creator of" (urn:plcs:rdl:std:Creator of) to indicate that this organization created the property value representation. This is illustrated in Figure 7.

Figure 7 — Characterization by organization or person of representing_value_range template

Other roles of an organization with regard to a property value representation may be assigned instead.

Related capabilities

This capability "Representing property value ranges" is related to the following capabilities:

Dependent capabilities

This capability "Representing property value ranges" is dependent on the following capabilities: