|
|
Application module:
Alternative solution |
ISO/TS 10303-1109:2019(E)
© ISO
|
This clause specifies the information requirements for the
Alternative solution
application module. The information requirements are specified as the
Application Reference Model (ARM) of this application module.
NOTE 1 A graphical representation of the information
requirements is given in
Annex C.
NOTE 2 The mapping specification is specified in
5.1. It shows how
the information requirements are met by using common resources and
constructs defined or imported in the MIM schema of this application
module.
This clause defines the information requirements to which implementations shall
conform using the EXPRESS language as defined in ISO 10303-11.
The following begins the
Alternative_solution_arm
schema and identifies the necessary external references.
EXPRESS specification:
*)
SCHEMA Alternative_solution_arm;
(*
The following EXPRESS interface statements specify the elements
imported from the ARMs of other application modules.
EXPRESS specification:
*)
USE FROM
Functional_breakdown_arm;
--
ISO/TS 10303-1216
USE FROM
Part_view_definition_arm;
--
ISO/TS 10303-1023
USE FROM
Person_organization_assignment_arm;
--
ISO/TS 10303-1013
USE FROM
Physical_breakdown_arm;
--
ISO/TS 10303-1215
USE FROM
Product_as_individual_arm;
--
ISO/TS 10303-1164
USE FROM
Product_occurrence_arm;
--
ISO/TS 10303-1063
USE FROM
Requirement_view_definition_arm;
--
ISO/TS 10303-1141
(*
NOTE 1
The schemas referenced above are specified in the following
part of ISO 10303:
| Functional_breakdown_arm |
ISO/TS 10303-1216 |
| Part_view_definition_arm |
ISO/TS 10303-1023 |
| Person_organization_assignment_arm |
ISO/TS 10303-1013 |
| Physical_breakdown_arm |
ISO/TS 10303-1215 |
| Product_as_individual_arm |
ISO/TS 10303-1164 |
| Product_occurrence_arm |
ISO/TS 10303-1063 |
| Requirement_view_definition_arm |
ISO/TS 10303-1141 |
NOTE 2
See Annex C,
Figures
C.1and C.2
for a graphical representation of this schema.
This subclause specifies the ARM types
for this application module. The ARM types and
definitions are specified below.
The complex_product_select type allows for the designation of the data
types
Alternative_solution, Breakdown_element, Functional_element_definition, Part_view_definition, and Physical_element_definition.
EXPRESS specification:
*)
TYPE
complex_product_select =
SELECT
(Alternative_solution,
Breakdown_element,
Functional_element_definition,
Part_view_definition,
Physical_element_definition);
END_TYPE;
(*
The final_definition_select type allows for the designation of the data
types
Product_as_individual_view, Part_view_definition, and Requirement_view_definition.
EXPRESS specification:
*)
TYPE
final_definition_select =
SELECT
(Product_as_individual_view,
Part_view_definition,
Requirement_view_definition);
END_TYPE;
(*
This subclause specifies the ARM entities for this
module. Each ARM application entity is an atomic element that
embodies a unique application concept and contains attributes
specifying the data elements of the entity. The ARM
entities and definitions are specified below.
An Alternative_solution is the identification of one of potentially many mutually exclusive implementations of a Functional_element_definition or of a Physical_element_definition.
An Alternative_solution may refer directly to the resolved concept or to another Alternative_solution. In the latter case, it specifies a refinement of the referenced Alternative_solution.
Each Alternative_solution may be specialized as a Technical_solution or a Supplier_solution.
EXPRESS specification:
*)
ENTITY Alternative_solution;
id : STRING;
version_id :
OPTIONAL
STRING;
base_element : complex_product_select;
END_ENTITY;
(*
Attribute definitions:
id:
the identifier of the Alternative_solution.
version_id:
the version of the Alternative_solution.
The value of this attribute need not be specified.
base_element:
the object for which the Alternative_solution provides a design alternative.
All Alternative_solution objects for the same base_element are mutually exclusive.
An Alternative_solution_relationship is a relationship between two
Alternative_solution
objects the meaning of which is defined by the attribute relation_type.
EXPRESS specification:
*)
ENTITY Alternative_solution_relationship;
description :
OPTIONAL
STRING;
id :
OPTIONAL
STRING;
related : Alternative_solution;
relating : Alternative_solution;
relation_type : STRING;
WHERE
WR1: relating :<>: related;
END_ENTITY;
(*
Attribute definitions:
description:
the text that provides further information about the Alternative_solution_relationship. The value of this attribute need not be specified.
id:
the identifier for the Alternative_solution_relationship.
related:
the second of the two
Alternative_solution
objects related by the Alternative_solution_relationship.
relating:
the first of the two
Alternative_solution
objects related by the Alternative_solution_relationship.
relation_type:
the meaning of the relationship. Where applicable, the following values shall be used:
Formal propositions:
WR1:
the related and the relating must be different.
A Final_solution is a type of
Alternative_solution
and is a set of additional sensual characteristics that can be applied to an Occurrence
that represents a neutral part to complete its definition.
EXPRESS specification:
*)
ENTITY Final_solution
SUBTYPE OF (Alternative_solution);
specifications : SET[1:?] OF final_definition_select;
status : STRING;
END_ENTITY;
(*
Attribute definitions:
specifications:
the set of means of finalization that are applied to the neutral part and which may be objects of type
Product_as_individual_view,
Part_view_definition
or
Requirement_view_definition.
status:
the text string that describes the level of completion between the neutral part and the final part.
A Solution_element is the association of a functional or organic requirement with an occurrence of a part that provides a way to resolve that
requirement.
The requirement is represented with a Functional_element_definition, a Physical_element_definition or with an Alternative_solution in case where several parts may resolve the requirement.
EXAMPLE 1
In a commercial aircraft, the function of main passenger exit is usually realized by the front left door.
NOTE
The requirement may be resolved by one part occurrence or by several part occurrences.
EXAMPLE 2
Closure of a door in a house is usually realized with a lock and a key.
EXPRESS specification:
*)
ENTITY Solution_element;
resolved_requirement : complex_product_select;
element : Product_occurrence;
description :
OPTIONAL
STRING;
END_ENTITY;
(*
Attribute definitions:
resolved_requirement:
the Functional_element_definition, the Physical_element_definition or the Alternative_solution.
element:
the part occurrence that provide a full or partial way to resolve the requirement.
description:
a text that provides further information about the rationale to consider the element as an element of the solution.
The value of this attribute need not be specified.
A Supplier_solution is a type of Alternative_solution provided by a supplier.
EXAMPLE
A Physical_element 'handle' has a Technical_solution 'H34215-VR17'. Three suppliers A, B, and C propose handle products that conform to that solution.
A Supplier_solution can be instantiated to represent the solution proposed by each of these suppliers.
EXPRESS specification:
*)
ENTITY Supplier_solution
SUBTYPE OF (Alternative_solution);
supplier : Organization;
probability_rate :
OPTIONAL
REAL;
DERIVE
actual_rate : REAL := NVL(probability_rate, 1.0);
WHERE
WR1: {0.0 <= actual_rate <= 1.0};
END_ENTITY;
(*
Attribute definitions:
supplier:
the Organization that acts as supplier of the solution.
probability_rate:
the share that is assigned to the supplier in the context of the base element.
The value of this attribute need not be specified.
In a case where the probability_rate is not specified, it shall be considered that the share granted to the Supplier_solution is either not yet known or not provided by intent.
actual_rate:
equal to the probability_rate or, by default, to 1.
NOTE
This derived attribute is specified to constraint the supplier share to be positive.
Formal propositions:
WR1:
The actual_rate shall be a value between 0 and 1.
A Technical_solution is a type of Alternative_solution where the functional or organic requirements are fulfilled in a technical way.
EXAMPLE
'gilded handle', 'unpolished handle' are examples of Technical_solution for the Physical_element 'handle'.
EXPRESS specification:
*)
ENTITY Technical_solution
SUBTYPE OF (Alternative_solution);
description : STRING;
END_ENTITY;
(*
Attribute definitions:
description:
Text that provides information about the Technical_solution.
*)
END_SCHEMA; -- Alternative_solution_arm
(*
© ISO 2019 — All rights reserved
