Application module: Zonal breakdown | ISO/TS 10303-1217:2004(E) © ISO |
This clause specifies the information requirements for the Zonal breakdown 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.
The following EXPRESS specification begins the Zonal_breakdown_arm schema and identifies the necessary external references.
EXPRESS specification:
*)
SCHEMA Zonal_breakdown_arm;
(*
The following EXPRESS interface statements specify the elements imported from the ARMs of other application modules.
EXPRESS specification:
*)
USE FROM
Product_breakdown_arm;
--
ISO/TS 10303-1248
USE FROM
Product_view_definition_arm;
--
ISO/TS 10303-1019
(*
NOTE 1 The schemas referenced above are specified in the following part of ISO 10303:
Product_breakdown_arm ISO/TS 10303-1248 Product_view_definition_arm ISO/TS 10303-1019
NOTE 2 See Annex C, Figures C.1and C.2 for a graphical representation of this schema.
This subclause specifies the ARM type for this application module. The ARM type and definition is specified below.
The in_zone_item type is an extensible list of alternate data types that allows for the designation of the data type Product_view_definition.
NOTE The list of entity data types may be extended in application modules that use the constructs of this module.
Items that may be identified as being in a zone.EXPRESS specification:
*)
TYPE
in_zone_item =
EXTENSIBLE
SELECT
(Product_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.
EXAMPLE A pump is in the starboard engine room of a ship.
EXPRESS specification:
*)
ENTITY In_zone;
id : STRING;
name : STRING;
description :
OPTIONAL
STRING;
located_item : in_zone_item;
zone : Zone_element_definition;
END_ENTITY;
(*
Attribute definitions:
id: an identifier for the relationship between the zone and the item in the zone.
name: the words by which the In_zone is known.
description: the text that provides further information about the relationship between the zone and the item in the zone. The value of this attribute need not be specified.
located_item: the item that exists in the zone.
zone: the region in which the item exists.
The parent-child view is represented by Zone_element_usage instances relating the zonal elements in the breakdown which are represented by Zone_elements.
EXAMPLE A zonal breakdown provides a means of identifying the decomposition of an aircraft in terms of spaces or high-level conceptual parts such as 'wing' - which might further decompose into lower-level zones such as 'inner-wing', and 'outer wing'.
EXPRESS specification:
*)
ENTITY Zone_breakdown
SUBTYPE OF (Breakdown);
END_ENTITY;
(*
EXAMPLE A 'fire-check zone' might be a member of the zonal breakdown of a building.
EXPRESS specification:
*)
ENTITY Zone_breakdown_context
SUBTYPE OF (Breakdown_context);
SELF\Breakdown_context.breakdown : Zone_breakdown_version;
SELF\Breakdown_context.breakdown_element : Zone_element_definition;
END_ENTITY;
(*
Attribute definitions:
breakdown: the version of the Zone_breakdown of which the Zone_element is a member.
breakdown_element: the view of the version of the Zone_element that is a member of the Zone_breakdown.
EXAMPLE An architect modifies the current fire-check zone breakdown for an building on the basis of reports from a buildings inspector.
EXPRESS specification:
*)
ENTITY Zone_breakdown_version
SUBTYPE OF (Breakdown_version);
SELF\Breakdown_version.of_product : Zone_breakdown;
END_ENTITY;
(*
Attribute definitions:
of_product: the Zone_breakdown_version shall only be a version of a Zone_breakdown .
EXAMPLE 'Empennage', 'Right vertical stabilizer and rudder' and 'Lower rudder' are all elements in a zonal breakdown of an aircraft.
EXPRESS specification:
*)
ENTITY Zone_element
SUBTYPE OF (Breakdown_element);
END_ENTITY;
(*
EXAMPLE For an aircraft, an element 'Right vertical stabilizer tip' is in a zonal breakdown that an engineer uses for reliability-centred maintenance analysis.
EXPRESS specification:
*)
ENTITY Zone_element_definition
SUBTYPE OF (Breakdown_element_definition);
SELF\Breakdown_element_definition.defined_version : Zone_element_version;
END_ENTITY;
(*
Attribute definitions:
defined_version: the Zone_element_definition shall only be a view of a Zone_element.
EXAMPLE In a zonal breakdown, the 'wing' (parent) might include (as children) an 'inner wing' and an 'outer wing'.
EXPRESS specification:
*)
ENTITY Zone_element_usage
SUBTYPE OF (Breakdown_element_usage);
SELF\Breakdown_element_usage.parent_element : Zone_element_definition;
SELF\Breakdown_element_usage.child_element : Zone_element_definition;
END_ENTITY;
(*
Attribute definitions:
parent_element: the parent zonal element of the relationship.
child_element: the child zonal element of the relationship.
EXAMPLE An engineer defines an inspection task on a breakdown element 'Upper rudder' that is part of a zonal breakdown of an aircraft. The engineer identifies the corresponding view of the breakdown element.
EXPRESS specification:
*)
ENTITY Zone_element_version
SUBTYPE OF (Breakdown_element_version);
SELF\Breakdown_element_version.of_product : Zone_element;
END_ENTITY;
(*
Attribute definitions:
of_product: the Zone_element_version shall only be a version of a Zone_element .
*)
END_SCHEMA; -- Zonal_breakdown_arm
(*
© ISO 2004 — All rights reserved