Template:— concession_impact (con_impt)
Context:— UK_Defence

Date: 2009/04/17 10:34:29
Revision: 1.2

Cover Contents Description Bus. perspective Bus. obj.Model diags.Input params.Ref. params.Instantiation path Instance diags.Characterizations Issues in situ

This section specifies the template concession_impact.

NOTE The template has been defined in the context of UK_Defence. Refer to the business context for details of related templates.

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 UK_Defence concession impact, using Approval_assignment.

This information object represents the relationship between a (set of) concession(s) and the impact that it(they) has.

EXAMPLE: A concession may impact on specific operational roles, environments or activities of the product.

For further information about the representation of a concession impact, see below.

Business perspective

This information object represents the relationship between a (set of) concession(s) and the impact that it(they) has.

Business object definition

Figure 1 — Graphical Representation for Business Object concession impact

Record:

This information object represents the information about a physical instance of a Concession Impact.

Attribute name	Attribute description	Attribute type	Optionality
Description	This is the description of the concession restriction.	Intrinsic	Mandatory
ID	This is the identifier of the concession restriction. This is removed until issue is addressed	Identifier	Mandatory
Impact	This is the reference to the item usage data which details the concession impact / restriction / applicability. This could be a Location, Operating Environment, Product Role or Activity.	Location, Operating Environment, Product Role or Activity.	Mandatory
Related Concession	This is the reference to the concession to which the restriction applies.	Concession	Mandatory

Table 1 — Product attribute details

Model diagrams

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

Figure 2 — An EXPRESS-G representation of the Information model for concession_impact

The graphic for the template to be used in other EXPRESS-G diagrams is shown in Figure 3 below.

Figure 3 — The graphical representation of the concession_impact template

Input parameters

The following input parameters are defined for this template:

description (Type='STRING')

This is the description of the concession restriction.

impact (Type= 'SELECT (activity_item)' )

Identifies that the concession impacts on either an Operating Environment, Product Role or Activity.

related_concession (Type= 'ENTITY (Approval)' )

This is the reference to the concession to which the restriction applies.

Reference parameters

The following reference parameters are defined for this template:

approval_assgn(Type='ENTITY (Approval_assignment)')

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

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

%^target = $concession_impact.approval_assgn%

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

Uniqueness constraints

The following parameter combinations specify a uniqueness constraint:

Unique constraint: Unique impact

Each instance of the entity (Approval_assignment) within the data set shall be uniquely identified by a combination of the following parameters on this template (concession_impact) namely: description, impact, related_concession.
The instance is referenced by the following template parameter: approval_assgn.

There should be one assignment between each concession, impact and description in a data set.

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 Templates Help/Information 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 @impact
Approval_assignment.items -> @impact

-- Instantiate Approval and assign Approval_assignment to it
Approval_assignment.assigned_approval -> @related_concession
/assigning_descriptor(
    descr=@description,
    class_name='Description',
    ecl_id='urn:plcs:rdl:std',
    is_assigned_to=^approval_assgn)/

The following entities are instantiated with attributes as specified:

Entity in path	Value	Inherited from
Approval_assignment.role	'/IGNORE'	—

Instance diagrams

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

/concession_impact(description='This impacts the ability to perform high altitude exercises', impact='@176', related_concession='@36')/

(an illustration of the consolidated concession_impact template is shown in Figure 5 below.)

Figure 4 — Entities instantiated by concession_impact template

The instance diagram in Figure 5 shows the graphic symbol for the template that is to be used in other instance diagrams. The example template is:

/concession_impact(description='This impacts the ability to perform high altitude exercises', impact='@176', related_concession='@36')/

Figure 5 — Instantiation of concession_impact template

Characterizations

No common characterizations of the template concession_impact have been identified. However, the ISO 10303-239 EXPRESS model may enable other assignments to the entities instantiated by the template.