4 Information requirements

This clause specifies the information requirements for the Work request 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.

This clause defines the information requirements to which implementations shall conform using the EXPRESS language as defined in ISO 10303-11. The following begins the Work_request_arm schema and identifies the necessary external references.

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 Activity_method_arm;    --  ISO/TS 10303-1049
(*



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

Activity_method_arm

ISO/TS 10303-1049

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

4.2 ARM type definition

This subclause specifies the ARM type for this application module. The ARM type and definition is specified below.

4.2.1 affected_item_select   

The affected_item_select type is an extensible list of alternate data types. Additional alternate data types are specified in select data types that extend the affected_item_select type.

NOTE   This empty extensible select requires extension in a further module to ensure that entities that refer to it have at least one valid instantiation.

EXPRESS specification:

*)
TYPE affected_item_select = EXTENSIBLE SELECT;
END_TYPE;
(*

4.3 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.3.1 Activity_method_assignment   

EXPRESS specification:

*)
ENTITY Activity_method_assignment;
  relation_type : STRING;
  assigned_method : Activity_method;
  associated_request : Work_request;
END_ENTITY;
(*

Attribute definitions:

relation_type: the text that identifies the nature of the relationship between the Activity_method and the Work_request.

Where applicable, the following values shall be used:

• 'recommended method': the Activity_method is the recommended approach to accomplish the requested work;
• 'non recommended method': the Activity_method should not be used to accomplish the requested work.

assigned_method: the Activity_method that is associated.

associated_request: the Work_request that is considered.

4.3.2 Affected_items_assignment   

EXAMPLE    In case a tire on a car is flat, a Work_request may be created and associated with the instances that represent the tire that is flat, the car and the spare wheel.

EXPRESS specification:

*)
ENTITY Affected_items_assignment;
  assigned_work_request : Work_request;
  items : SET[1:?] OF affected_item_select;
END_ENTITY;
(*

Attribute definitions:

assigned_work_request: the Work_request for which a set of items is being identified.

items: the set of things that are affected by the Work_request.

4.3.3 Work_request   

NOTE    These requests may not be acted upon depending on the authorization granted to the request or its associated Work_order.

EXPRESS specification:

*)
ENTITY Work_request;
  request_id : STRING;
  version_id : OPTIONAL STRING;
  description : OPTIONAL STRING;
  purpose : STRING;
END_ENTITY;
(*

Attribute definitions:

request_id: the identification that distinguishes the Work_request.

version_id: the identification of the version of the Work_request. The value of this attribute need not be specified.

description: the text that provides further information about the Work_request. The value of this attribute need not be specified.

EXAMPLE 1   This attribute may contain a description of the issue that was the origin of the request.

purpose: the text that describes the reason for the activity request.

EXAMPLE 2   'technical improvement', 'government regulation', 'durability improvement', 'tool improvement', 'production relief', 'production requirement', 'quality improvement', 'security reason', 'standardization', 'cost reduction', 'customer rejection' in case the request results from a rejection by a customer, 'change of standard', 'production alignment', and 'procurement alignment' are examples of purpose.

4.3.4 Work_request_relationship   

EXPRESS specification:

*)
ENTITY Work_request_relationship;
  relation_type : STRING;
  description : OPTIONAL STRING;
  relating : Work_request;
  related : Work_request;
END_ENTITY;
(*

Attribute definitions:

relation_type: specifies the meaning of the relationship.

Where applicable the following values shall be used:

• 'dependency': The related Work_request is dependent of the relating Work_request.

description: specifies additional information.

relating: specifies the first of the two Work_request objects.

related: specifies the second of the two Work_request objects.

4.3.5 Work_request_status   

NOTE    A Work_request may have zero or more statuses, assigned at various dates by various organizations.

EXPRESS specification:

*)
ENTITY Work_request_status;
  status : STRING;
  work_request : Work_request;
END_ENTITY;
(*

Attribute definitions:

status: the text that provides a user interpretable designation for the level of completion of the study and resolution of the work request.

EXAMPLE    'drafted', 'issued', 'deferred', 'in-hand', 'completed', 'cancelled', 'rejected' are examples of request status.

work_request: the Work_request to which the status applies.

© ISO 2018 — All rights reserved