Application module: Interface lifecycle ISO/TS 10303-1294: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
F Application module implementation and usage guide
Bibliography
Index

4 Information requirements

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

EXPRESS specification:

*)
SCHEMA Interface_lifecycle_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 Interface_arm;    --  ISO/TS 10303-1251
(*

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

Interface_arm ISO/TS 10303-1251

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 Interface_connector_as_planned   EXPRESS-GMapping table

An Interface_connector_as_planned is a type of Interface_connector_version that identifies an individual that is the subject of a plan to realize an Interface_connector.

EXAMPLE    Company Acme Limited is planning to produce an aircraft with serial number 1234 next month. This aircraft has connectors on each engine for fuel pipes. The company wishes to plan when each connector will be realized and then identify a date on which an inspector can test all the realized connectors.

EXPRESS specification:

*)
ENTITY Interface_connector_as_planned
  SUBTYPE OF (Interface_connector_version);
END_ENTITY;
(*

4.2.2 Interface_connector_as_realized   EXPRESS-GMapping table

An Interface_connector_as_realized is a type of Interface_connector_version that identifies an individual that is a realized Interface_connector.

EXAMPLE    Company WeFlySafest Corporation owns and operates an aircraft with serial number 1234. When landing at Heathrow airport, the pilot reports a loss of fuel pressure on engine number 4 with serial number A9876 and recommends that an inspector tests the realized connector on the engine.

EXPRESS specification:

*)
ENTITY Interface_connector_as_realized
  SUBTYPE OF (Interface_connector_version);
END_ENTITY;
(*

4.2.3 Interface_connector_design   EXPRESS-GMapping table

An Interface_connector_design is a type of Interface_connector_version that identifies a design version of an Interface_connector.

EXAMPLE    BuildAWidget Incorporated creates design version 2.10 for an electrical supply connector.

EXPRESS specification:

*)
ENTITY Interface_connector_design
  SUBTYPE OF (Interface_connector_version);
END_ENTITY;
(*

4.2.4 Interface_connector_design_to_planned   EXPRESS-GMapping table

An Interface_connector_design_to_planned is a relationship between a design version of an Interface_connector and a planned individual that is to conform to the design.

EXAMPLE    BuildAWidget Incorporated plans production of pump serial number 30301 with an electrical supply connector that is to conform to design version 2.10.

EXPRESS specification:

*)
ENTITY Interface_connector_design_to_planned;
  id : STRING;
  name : STRING;
  description : OPTIONAL STRING;
  design : Interface_connector_design;
  planned : Interface_connector_as_planned;
END_ENTITY;
(*

Attribute definitions:

id: an 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 the attribute need not be specified.

design: the version to which the planned individual will conform.

planned: the individual that is to conform to the design version.

4.2.5 Interface_connector_design_to_realized   EXPRESS-GMapping table

An Interface_connector_design_to_realized is a relationship between a design version of an Interface_connector and a realized individual that conforms to the design.

EXAMPLE    BuildAWidget Incorporated builds pump serial number 30301 with an electrical supply connector that conforms to design version 2.11.

EXPRESS specification:

*)
ENTITY Interface_connector_design_to_realized;
  id : STRING;
  name : STRING;
  description : OPTIONAL STRING;
  design : Interface_connector_design;
  realized : Interface_connector_as_realized;
END_ENTITY;
(*

Attribute definitions:

id: an 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 the attribute need not be specified.

design: the version to which the realized individual conforms.

realized: the individual that conforms to the design.

4.2.6 Interface_connector_planned_to_realized   EXPRESS-GMapping table

An Interface_connector_planned_to_realized is a relationship between a realized individual of an Interface_connector and a corresponding planned individual.

EXAMPLE    BuildAWidget Incorporated builds pump serial number 30302 with an electrical supply connector that was previously planned.

EXPRESS specification:

*)
ENTITY Interface_connector_planned_to_realized;
  id : STRING;
  name : STRING;
  description : OPTIONAL STRING;
  planned : Interface_connector_as_planned;
  realized : Interface_connector_as_realized;
END_ENTITY;
(*

Attribute definitions:

id: an 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 the attribute need not be specified.

planned: the individual that relates to the realized individual.

realized: the individual that relates to the planned individual.



*)
END_SCHEMA;  -- Interface_lifecycle_arm
(*


© ISO 2004 — All rights reserved