assigning_approval

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

-- Instantiate an Approval_assignment
Approval_assignment

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

-- Set the Approval_assignment attribute role
Approval_assignment.role = '/IGNORE'

-- Assign the Approval_assignment to the
-- instances passed into the template through the @items
-- input parameter (e.g. a Part_version)
Approval_assignment.items -> @items

-- Instantiate Approval and assign Approval_assignment to it
Approval
Approval_assignment.assigned_approval -> Approval

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

-- Set the Approval attributes
Approval.purpose = '/IGNORE'

-- Instantiate Approval_status and assign Approval to it
-- NB This mechanism is not used to represent an approval status
Approval_status
Approval.status -> Approval_status

-- Set the Approval_status attribute
Approval_status.status_name = '/IGNORE'

-- Set the approval status using assigning_asserted_state
/assigning_asserted_state(
    assigned_to=Approval,
    state_class_name=@status,
    state_ecl_id=@status_ecl_id)/

-- Instantiate an Approving_person_organization and
-- assign it to Approval
Approving_person_organization
Approving_person_organization.authorized_approval -> Approval

-- Bind the Approving_person_organization to the parameter ^app_pers_org.
-- This parameter is a reference parameter that allows the
-- Approving_person_organization entity to be referred to when this template is used.
%^app_pers_org = Approving_person_organization%

-- Assign the Approving_person_organization to the
-- to the instances passed into the template through the @person_org
-- input parameter (e.g. a Person_in_organization)
Approving_person_organization.person_organization -> @person_org

-- Bind the State_observed to the parameter ^state_obs.
-- This parameter is a reference parameter that allows the
-- State_observed entity to be referred to when this template is used.
%^state_obs = State_observed%

-- Bind the State_assertion to the parameter ^state_assert.
-- This parameter is a reference parameter that allows the
-- State_assertion entity to be referred to when this template is used.
%^state_assert = State_assertion%

-- Bind the State_definition to the parameter ^state_def.
-- This parameter is a reference parameter that allows the
-- State_definition entity to be referred to when this template is used.
%^state_def = State_definition%

Note that the templates representing_organization, assigning_time, assigning_reference_data, and assigning_asserted_state are used in the diagram. Note that one of the two templates representing_organization or representing_person_in_organization always must be present to make the approval complete. In this diagram, the assignment of an approving organization was done as follows:

@41 /representing_organization(org_id='Bike Rent Limited', org_id_class_name='Organization_name', org_id_ecl_id='urn:plcs:rdl:std')/

The approval status is assigned using the template assigning_asserted_state:

@5 /assigning_asserted_state(status='Approved', ecl_id='urn:plcs:rdl:std', assigned_to='#2')/

The following characterizations may apply:

Characterization Assigning purpose

NOTE this characterization is optional.

The purpose of an approval is represented using the template assigning_reference_data to assign a class to an Approval to identify the purpose of approval and to the Approval_status to assign a status to the approval.

Figure 5 — Approval purpose

Characterization Assigning dates

NOTE this characterization is optional.

Dates can be associated with the approval, in a given role, by using the template assigning_time.

Two dates are commonly assigned to the template assigning_approval, namely the date on which the item is planned to be approved, and the date of actual approval.

If the date is the planned date of approval, then the assigning_time template classifies the date and time as "Date_planned" (urn:plcs:rdl:std:Date_planned).

If the date and time is the actual date, then the assigning_time template classifies the date and time as "Date_actual" (urn:plcs:rdl:std:Date_actual).

Figure 6 — Approval dates

Characterization Approval relationships

NOTE this characterization is optional.

Approvals can be related to other approvals, such as for a successive approval as illustrated in Figure 7, by an instance of entity Approval_relationship. The relationship should be classified accordingly, as illustrated in Figure 7.

Figure 7 — Relating two approvals.

Entity in path	Value	Inherited from
Approval_assignment.role	'/IGNORE'	—
Approval.purpose	'/IGNORE'	—
Approval_status.status_name	'/IGNORE'	—