ISO 10303-239 Representation

Model overview

Use of this DEX involves a three-step process:

1. Observing an actual product to note its usage, state, properties, location or environment;

   NOTE    An actual product is represented by the EXPRESS entity Product_as_realized.

2. Entering the information into a computer application capable of holding the information specified by this DEX;
3. Creating an export file, which is a populated instance of this DEX, to transfer some or all the information collected from that application to another.

The capabilities that provide this functionality are summarised in Figure 1

Figure 1 —  Capabilities used by DEX

Transmitting feedback information

Information describing an exchange of information by the usage of this DEX is provided by the capability C014: messaging. This is used to communicate meta-data associated with a specific message, such as the intent of the sender, identification of the business process (if any) of which the message forms part, or status information relating to the message itself.

Although this DEX will often be used to communicate information which requires no immediate action, it can also be used to raise issues, in the form of a work request. The work request is described by the capability C066: representing_work_request.

The issue, work request, or message meta data may be amplified by associated documents. These are described by the capability C005: representing_documents and referencing_documents
Error C1: Capability referencing_documents not in dex_index.xml
.

These document capabilities are also available for use when reporting usage or product state.

Reporting the usage of an actual product

Reporting involves identifying:

• the Product_as_realized that is the subject of the feedback,
• the activity (usage) that the Product_as_realized was undertaking,
• the properties that define the use, or result from use,
• and the environment in which the usage occurred.

Referencing an actual product

The identification of the Product_as_realized to which operational feedback applies can be achieved in several ways. One option is to record the serial number, but this may not always be available and, sometimes, is not sufficient. The various approaches to product identification supported by this DEX are described in the following sections.

Any additional constraints on which of these options shall be used in a specific business context should be specified in data exchange agreements between business partners.

Identifying a product_as_realized by serial number

The Product_as_realized can be identified by using the serial number assigned to it. This is described in capability referencing_product_as_individual
Error C1: Capability referencing_product_as_individual not in dex_index.xml
.

Referencing a product_as_realized and its association to the design

The Product_as_realized can be identified by reference to the design of the part from which it was made (often through a part number). This may used alone, or with a serial number. Both options are provided in capability referencing_product_as_individual
Error C1: Capability referencing_product_as_individual not in dex_index.xml

Referencing a Product_as_realized in an assembly

Where the Product_as_realized is part of assembly, it is necessary to be able record the serial number of its parent in the assembly structure. This can be achieved through the entity Next_assembly_usage.

If attachment slots are used (entity Attachment_slot_as_realized), it may also be useful to record the attachment slot to which the Product_as_realized was fitted.

This functionality is supported by the capability referencing_product_as_individual
Error C1: Capability referencing_product_as_individual not in dex_index.xml
.

Referencing a Product_as_realized in a configuration

Where the Product_as_realized is part of an assembly, which has different configuration options it will be necessary for the feedback report to identify the configuration of the assembly to which the feedback applies. This is achieved by identifying the relevant Item_design_association entity and Product_configuration entity.

This capability is provided by referencing_product_as_individual_configuration
Error C1: Capability referencing_product_as_individual_configuration not in dex_index.xml
.

Referencing a Product_as_realized in the context of a breakdown

If a Product_as_realized is linked to an element in a product breakdown structure (see C004: representing_breakdown_structure) by a Breakdown_element and a Breakdown_element_realization relationship, then it will be necessary to refer to these constructs in the operational feedback.

Reporting the status of an actual product

The concept of the state, or status, of a Product_as_realized may be used to record several different aspects of feedback as follows:

• the observed state of the Product_as_realized as it progresses through recognised points in any process, such as a repair loop, or manufacturing process;
• the existence of a fault state affecting the Product_as_realized. Observed faults may be related to those defined by an analysis process, such as a FME(C)A.
• the version or modification state of the Product_as_realized, perhaps after completing an activity to implement a configuration change;
• the role configuration of the Product_as_realized;

Identifying the location of an actual product

The geographic location of a Product_as_realized may be recorded at any time, as the location provides a context for a period of usage or a report on other aspects of product state or status.

This is described in capability representing_product_location
Error C1: Capability representing_product_location not in dex_index.xml
.

NOTE    Location within a product structure is addressed by the capability referencing_part_or_slot
Error C1: Capability referencing_part_or_slot not in dex_index.xml
which describes how to reference a product in an assembly, and referencing_product_breakdown_element
Error C1: Capability referencing_product_breakdown_element not in dex_index.xml
which describes how to reference a product in a breakdown.

© OASIS 2010 — All rights reserved