AP scope  |  AP module  |  AP contents  |  AP index
Application module: Hybrid breakdown ISO/TS 10303-1218:2004(E)
© ISO

Cover page
Table of contents
Copyright
Foreword
Introduction
1 Scope
2 Normative references
3 Terms, definitions and abbreviations

4 Information requirements
   4.1 Required AM ARM
   4.2 ARM entity definitions
5 Module interpreted model
   5.1 Mapping specification
   5.2 MIM EXPRESS short listing
     5.2.1 MIM entity definitions

A MIM short names
B Information object registration
C ARM EXPRESS-G   EXPRESS-G
D MIM EXPRESS-G   EXPRESS-G
E Computer interpretable listings
Bibliography
Index

4 Information requirements

This clause specifies the information requirements for the Hybrid 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 Hybrid_breakdown_arm schema and identifies the necessary external references.

EXPRESS specification:

*)
SCHEMA Hybrid_breakdown_arm;
(*

4.1 Required AM ARM

The following EXPRESS interface statement specifies the elements imported from the ARM of another application module.

EXPRESS specification:

*)
USE FROM Product_breakdown_arm;    --  ISO/TS 10303-1248
(*

NOTE 1   The schemas referenced above are specified in the following part of ISO 10303:

Product_breakdown_arm ISO/TS 10303-1248

NOTE 2   See Annex C, Figures C.1and C.2 for a graphical representation of this schema.

4.2 ARM entity definitions

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.

4.2.1 Hybrid_breakdown   EXPRESS-GMapping table

A Hybrid_breakdown is a type of Breakdown that identifies a non-specific partitioning of a product into a set of related elements so as to form explicit, parent-child views that comprise the elements.

The parent-child view is represented by Hybrid_element_usage instances relating the elements in the hybrid breakdown which are represented by types of Breakdown_elements.

EXAMPLE    A product breakdown in which a 'climate control' function has a decomposition that comprises a 'heating function' and a 'cooling function' and in which the 'heating function' has a decomposition that comprises a 'heating element' and a 'heat distribution system' would be an example of a 'hybrid breakdown'.

EXPRESS specification:

*)
ENTITY Hybrid_breakdown
  SUBTYPE OF (Breakdown);
END_ENTITY;
(*

4.2.2 Hybrid_breakdown_context   EXPRESS-GMapping table

A Hybrid_breakdown_context is a type of Breakdown_context that is a relationship between a Breakdown_element and a Hybrid_breakdown of which the hybrid element is a member.

EXAMPLE    A 'pipe element' might be a member of a 'heating function' breakdown in a hybrid decomposition.

EXPRESS specification:

*)
ENTITY Hybrid_breakdown_context
  SUBTYPE OF (Breakdown_context);
  SELF\Breakdown_context.breakdown : Hybrid_breakdown_version;
END_ENTITY;
(*

Attribute definitions:

breakdown: the version of the Hybrid_breakdown of which the Breakdown_element is a member.

4.2.3 Hybrid_breakdown_version   EXPRESS-GMapping table

A Hybrid_breakdown_version is a type of Breakdown_version that identifies a version of a Hybrid_breakdown.

EXPRESS specification:

*)
ENTITY Hybrid_breakdown_version
  SUBTYPE OF (Breakdown_version);
  SELF\Breakdown_version.of_product : Hybrid_breakdown;
END_ENTITY;
(*

Attribute definitions:

of_product: the Hybrid_breakdown_version shall only be a version of a Hybrid_breakdown.

4.2.4 Hybrid_element_usage   EXPRESS-GMapping table

A Hybrid_element_usage is a type of Breakdown_element_usage that identifies a relationship between a parent and child Breakdown_element where the parent and child elements may be different subtypes of Breakdown_element.

EXAMPLE    In a hybrid breakdown, the 'fuel system' might include a 'tank element' and a 'fuel-injection element' as components.

EXPRESS specification:

*)
ENTITY Hybrid_element_usage
  SUBTYPE OF (Breakdown_element_usage);
END_ENTITY;
(*



*)
END_SCHEMA;  -- Hybrid_breakdown_arm
(*


© ISO 2004 — All rights reserved