| Capability (C086):— representing_slots | Date: 2006/06/14 12:07:10 Revision: 1.7 |
This section describes the EXPRESS information model for the capability.
EXAMPLE A fast jet aircraft has two engines. These engines are removable and interchangeable between individual aircraft. An attachment slot represents each installation position for an engine so as to ensure that an accurate record is maintained of which engines fly in which pairing on which aircraft for how many hours.
ENTITY Attachment_slot
SUBTYPE OF (Product);
END_ENTITY;
EXAMPLE FlyFasterWithUs Group will buy an aircraft with serial number 1234 next year. The company wishes to plan the schedule for removal of engines from the aircraft for maintenance purposes. Instances of the Attachment_slot_as_planned entity data type allow the company to associate individual engines with the aircraft at different times over the planned period.
ENTITY Attachment_slot_as_planned
SUBTYPE OF (Attachment_slot_version);
END_ENTITY;
EXAMPLE FlyFasterWithUs Group operates an aircraft with serial number 1234 next year. The company records which individual engines power the aircraft at different times during the lifetime of the aircraft.
ENTITY Attachment_slot_as_realized
SUBTYPE OF (Attachment_slot_version);
END_ENTITY;
EXAMPLE An airworthiness authority requires an airline company to report which individual engines power the aircraft at different times during the lifetime of the aircraft.
ENTITY Attachment_slot_definition
SUBTYPE OF (Product_view_definition);
SELF\Product_view_definition.defined_version : Attachment_slot_version;
END_ENTITY;
defined_version: the Attachment_slot_definition shall only be a view of an Attachment_slot.
EXAMPLE WeMakeBigPlanes Limited creates design version 1.34 of the attachment slot for the starboard engine of an aircraft.
ENTITY Attachment_slot_design
SUBTYPE OF (Attachment_slot_version);
END_ENTITY;
Attachment_slot_design_to_planned
An Attachment_slot_design_to_planned is a relationship between a design version of an Attachment_slot and a planned individual that conforms to the design.EXAMPLE WeMakeBigPlanes Limited plans production of aircraft serial number 1234 with a starboard engine attachment slot that is to conform to design version 1.34.
ENTITY Attachment_slot_design_to_planned;
id : STRING;
name : STRING;
description :
OPTIONAL
STRING;
design : Attachment_slot_design;
planned : Attachment_slot_as_planned;
WHERE
WR1: SELF.design.of_product :=: SELF.planned.of_product;
END_ENTITY;
id: the identifier for the relationship between the design and the planned individual.
name: the words by which the relationship between the design and the planned individual is known.
description: the text that provides further information about the relationship between the design and the planned individual. The value of this attribute need not be specified.
design: the version of the attachment slot concept to which the planned individual will conform.
planned: the attachment slot that is to conform to the design version.
Attachment_slot_design_to_realized
An Attachment_slot_design_to_realized is a relationship between a design version of an Attachment_slot and a realized individual that conforms to the design.EXAMPLE WeMakeBigPlanes Limited builds aircraft serial number 1234 with a starboard engine attachment slot that conforms to design version 1.34.
ENTITY Attachment_slot_design_to_realized;
id : STRING;
name : STRING;
description :
OPTIONAL
STRING;
design : Attachment_slot_design;
realized : Attachment_slot_as_realized;
WHERE
WR1: SELF.design.of_product :=: SELF.realized.of_product;
END_ENTITY;
id: the identifier for the relationship between the design and the realized individual.
name: the words by which the relationship between the design and the realized individual is known.
description: the text that provides further information about the relationship between the design and the realized individual. The value of this attribute need not be specified.
design: the version of the concept to which the realized individual conforms.
realized: the individual that conforms to the design.
EXAMPLE An aircraft has a pylon mounting on a wing as a location at which to install various equipment. An instance of the Attachment_slot_on_product entity data type identifies which attachment slot corresponds to the pylon.
ENTITY Attachment_slot_on_product;
id : STRING;
name : STRING;
description :
OPTIONAL
STRING;
product : Product_view_definition;
attachment_slot : Attachment_slot_definition;
END_ENTITY;
id: the identifier for the relationship between the attachment slot and the product.
name: the words by which the relationship between the attachment slot and the product is known.
description: the text that provides further information about the relationship between the attachment slot and the product. The value of this attribute need not be specified.
product: the thing that associates the attachment slot location at which to attach parts to the product view definition.
attachment_slot: a location on a product at which to attach parts via an aperture.
Attachment_slot_planned_to_realized
An Attachment_slot_planned_to_realized is a relationship between a realized individual of an Attachment_slot and a corresponding planned individual.EXAMPLE WeMakeBigPlanes Limited builds aircraft serial number 2468 with a starboard engine attachment slot that was previously planned.
ENTITY Attachment_slot_planned_to_realized;
id : STRING;
name : STRING;
description :
OPTIONAL
STRING;
planned : Attachment_slot_as_planned;
realized : Attachment_slot_as_realized;
WHERE
WR1: SELF.planned.of_product :=: SELF.realized.of_product;
END_ENTITY;
id: the identifier for the relationship between the planned individual and the realized individual.
name: the words by which the relationship between the planned individual and the realized individual is known.
description: the text that provides further information about the relationship between the planned individual and the realized individual. The value of this attribute need not be specified.
planned: the attachment slot that relates to the realized individual.
realized: the individual that relates to the planned individual.
NOTE This is a generic concept of version, in most situations it is possible and more specific to represent a version as Attachment_slot_design, Attachment_slot_as_planned or Attachment_slot_as_realized.
ENTITY Attachment_slot_version
SUPERTYPE OF
(ONEOF (Attachment_slot_as_planned,
Attachment_slot_as_realized,
Attachment_slot_design))
SUBTYPE OF (Product_version);
SELF\Product_version.of_product : Attachment_slot;
END_ENTITY;
of_product: the Attachment_slot_version shall only be a version of an Attachment_slot.
EXAMPLE A long-range fuel tank is designed to be attached to an aircraft in an attachment slot that corresponds to a pylon mounting on a wing.
ENTITY Product_in_attachment_slot
SUBTYPE OF (View_definition_usage);
name : STRING;
SELF\View_definition_relationship.related_view RENAMED attachment_slot : Attachment_slot_definition;
SELF\View_definition_relationship.relating_view RENAMED product : Product_view_definition;
END_ENTITY;
name: the words by which the relationship between the attachment slot and the product is known.
attachment_slot: the position where the product can be attached.
product: the Product_view_definition of a Product that has been designed to be attached to the attachment slot.