Template:— transportation_specification (trans_spec)
Context:— UK_Defence

Date: 2010/03/15 15:09:16
Revision: 1.3

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 transportation_specification.

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 the transportation specification of the item of supply.

Business perspective

The Transportation Specification business object is used by those UK_Defence Data Exchange Specifications that require information about the transportation specification of the item of supply, in terms of requirements, constraints and instructions.

Business object definition

Figure 1 — Graphical Representation for Business Object Transportation Specification

Attribute name	Attribute description	Attribute type	Optionality
Content	This attribute provides a reference to the document that contains the transportation specification for the related item of supply. This will specify all constraints for vibration, tie down, temperature, humidity etc that must be complied with during transportation.	Relationship to Document	Mandatory
Derived From	This attribute provides a reference to the analysis from which the specification was derived.	Relationship to PHS and T Analysis	Mandatory
ID	This is the identifier of the specification.	Relationship to Identifier	Mandatory

Table 1 — Transportation Specification attribute details

Model diagrams

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

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

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

Input parameters

The following input parameters are defined for this template:

Content (Type= 'ENTITY (Document)' )

The reference to the document that contains the transportation specification for the related item of supply.

Derived_from (Type= 'ENTITY (Document)' )

The reference to the analysis from which the specification was derived.

ID (Type='STRING')

The identifier of the transportation specification.

ID_source_organization (Type='STRING')

The identifier of the organization responsible for identifying the handling specification.

Reference parameters

The following reference parameters are defined for this template:

transportation_specification(Type='ENTITY (Task_method_version)')

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

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

%^target = $transportation_specification.transportation_specification%

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

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.

-- task
/task(
    Acceptance_criteria='/NULL',
    Category='Task_category',
    ID=@ID,
    ID_source_organization=@ID_source_organization,
    Name='/NULL',
    Name_source_organization='NULL',
    Version='/NULL',
    Version_source_organization='NULL',
    Description='/NULL',
    Required_outcome='/NULL',
    Duration_value='0',
    Duration_unit='Unit',
    Periodicity_type='Periodicity',
    Periodicity_value='0',
    Periodicity_unit='Unit',
    Subject=@Content)/
%^transportation_specification = $task.task%
Applied_activity_method_assignment
Applied_activity_method_assignment.assigned_activity_method -> ^transportation_specification
Applied_activity_method_assignment.role = '/IGNORE'
Applied_activity_method_assignment.items -> @Derived_from

The following entities are instantiated with attributes as specified:

Entity in path	Value	Inherited from
Applied_activity_method_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:

/transportation_specification(ID='TS001', ID_source_organization='UK_Defence', Content='@299', Derived_from='@409')/

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

Figure 4 — Entities instantiated by transportation_specification 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:

/transportation_specification(ID='TS001', ID_source_organization='UK_Defence', Content='@299', Derived_from='@409')/

Figure 5 — Instantiation of transportation_specification template

Characterizations

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