assigning_asserted

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

This template describes how to represent the fact that something has been observed to be in a given state and that this assertion has been confirmed by evidence such as a measurement.

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 state definition

There shall be at most one instance of the entity (State_definition) within the data set uniquely identified by a combination of the following parameters on this template (assigning_asserted_state) namely: state_class_name, state_ecl_id.
The instance is referenced by the following template parameter: state_def.

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 an Applied_state_assignment
Applied_state_assignment

-- Assign the Asserted State to the
-- to the instances passed into the template through the @assigned_to
-- input parameter (e.g. a Product_as_individual_view)
Applied_state_assignment.assigned_to -> @assigned_to

-- Instantiate and point at a State_role
Applied_state_assignment.role -> State_role

-- Set the State_role attributes name and description to be ignored
State_role.name = '/IGNORE'
State_role.description = '/IGNORE'

-- Instantiate and point at State_observed
Applied_state_assignment.described_state -> State_observed

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

-- Set the State_observed attributes name and description to be ignored
State_observed.name = '/IGNORE'
State_observed.description = '/IGNORE'

-- Instantiate state_assertion and point it at
-- State_observed just instantiated
State_assertion.asserted_state -> ^state_obs

-- Set the state_assertion attributes name and description to be ignored
State_assertion.name = '/IGNORE'
State_assertion.description = '/IGNORE'

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

-- Instantiate and point at a State_definition
^state_assert.conformance_state -> State_definition

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

-- Set the State_definition attributes name and description to be ignored
State_definition.name = '/IGNORE'
State_definition.description = '/IGNORE'

-- Assign reference data for name of State_definition
/assigning_reference_data(
    items=^state_def,
    class_name=@state_class_name,
    ecl_id=@state_ecl_id)/

The following entities are instantiated with attributes as specified:

Entity in path	Value	Inherited from
State_role.name	'/IGNORE'	—
State_role.description	'/IGNORE'	—
State_observed.name	'/IGNORE'	State.name
State_observed.description	'/IGNORE'	State.description
State_assertion.name	'/IGNORE'	—
State_assertion.description	'/IGNORE'	—
State_definition.name	'/IGNORE'	—
State_definition.description	'/IGNORE'	—

Note that the templates assigning_time, assigning_identification and assigning_person_in_organization are used in the diagram. Namely:

@2 /assigning_time(date_class_name='Date_actual_assertion', date_ecl_id='urn:plcs:rdl:std', year='2005', month='10', day='3', hour='10', minute='34', second='21', sense='OFFSET_ORIENTATION.exact', hour_offset='0', minute_offset='0', items='#105')/

and:

@3 /assigning_person_in_organization(person_id='LA3412', person_id_class_name='Person_identification_code', person_id_ecl_id='urn:plcs:rdl:std', last_name='Smith', first_name='Jack', middle_names='', prefix_titles='', suffix_titles='', person_role_class_name='Assertor_of', person_role_ecl_id='urn:plcs:rdl:std', org_id='BikeHire Limited', org_id_class_name='Organization_name', org_id_ecl_id='urn:plcs:rdl:std', items='#105')/

and:

@4 /assigning_time(date_class_name='Date_actual_observation', date_ecl_id='urn:plcs:rdl:std', year='2005', month='10', day='3', hour='10', minute='12', second='55', sense='OFFSET_ORIENTATION.exact', hour_offset='0', minute_offset='0', items='#1')/

and:

@5 /assigning_person_in_organization(person_id='LA3411', person_id_class_name='Person_identification_code', person_id_ecl_id='urn:plcs:rdl:std', last_name='Olsen', first_name='Bob', middle_names='', prefix_titles='', suffix_titles='', person_role_class_name='Observer_of', person_role_ecl_id='urn:plcs:rdl:std', org_id='BikeRent Limited', org_id_class_name='Organization_name', org_id_ecl_id='urn:plcs:rdl:std', items='#1')/

and:

@6 /assigning_identification(id='abc123', class_name='Identifier_type', id_ecl_id='urn:plcs:rdl:std', org_id='BikeRent Limited', org_id_class_name='Organization_name', org_id_ecl_id='urn:plcs:rdl:std', items='#1')/

The following section details how the assigning_asserted_state 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 Assigning times

NOTE this characterization is optional.

Dates and times can be associated with the assignment of an asserted state in a given role by using the template assigning_time.

Figure 6 — Characterization by date of assigning_asserted_state template

Several dates can be assigned to the template assigning_asserted_state, however two dates and times are commonly assigned these being the date and time on which the state was asserted and the date and time when the state was observed.

The date and time on which the state was asserted is represented by using the template assigning_time to assign a date and time to State_assertion. The date assignment is classified as: "Date_actual_assertion" (urn:plcs:rdl:std:Date_actual_assertion) to indicate that it is the date when the state was asserted. This is illustrated in Figure 6.

The date and time on which the state was observed is represented by using the template assigning_time to assign a date and time to State_observed. The date assignment is classified as: "Date_actual_observation" (urn:plcs:rdl:std:Date_actual_observation) to indicate that it is the date when the state was observed. This is illustrated in Figure 6.

Characterization Assigning person

NOTE this characterization is optional.

People can be associated with the assignment of an asserted state in a given role by using the template assigning_person_in_organization to assign a person to either a State_observed or a State_assertion .

Figure 7 — Characterization by person of assigning_asserted_state template

Several roles can be assigned to an asserted state. Two common roles in which people are assigned to the assignment of an asserted state are as an "Assessor of" the state and as an "Observer of" the state.

The person who asserted the state is represented by using the template assigning_person_in_organization to assign a person to State_assertion. The assignment of the person (Organization_or_person_in_organization_assignment) is classified as: "Assertor_of" (urn:plcs:rdl:std:Assertor_of) to indicate that it is this person who has asserted the state. This is illustrated in Figure 7.

The person who observed the state is represented by using the template assigning_person_in_organization to assign a person to State_observed. The assignment of the person (Organization_or_person_in_organization_assignment) is classified as: "Observer_of" (urn:plcs:rdl:std:Observer_of) to indicate that it is this person who has observed the state. This is illustrated in Figure 7.

Characterization Assigning Identification

NOTE this characterization is optional.

Identifiers can be associated with the assignment of an asserted state by using the template assigning_identification to assign an identifier to a State_observed.

Figure 8 — Characterization by identifier of assigning_asserted_state template

An example of the use of an identifier could be to identify the fault that is the reason for a repair activity.