4 Information requirements

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

4.1 Required AM ARMs

The following EXPRESS interface statements specify the elements imported from the ARMs of other application modules.

EXPRESS specification:

*)
USE FROM Date_time_assignment_arm;    --  ISO/TS 10303-1014



USE FROM Person_organization_arm;    --  ISO/TS 10303-1011
(*



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

Date_time_assignment_arm	ISO/TS 10303-1014
Person_organization_arm	ISO/TS 10303-1011

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 approval_item   

The approval_item type is an extensible list of alternate data types. Additional alternate data types are specified in select data types that extend the approval_item 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 approval_item = EXTENSIBLE GENERIC_ENTITY 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 Approval   

EXPRESS specification:

*)
ENTITY Approval;
  status : Approval_status;
  purpose : STRING;
  planned_date : OPTIONAL date_or_date_time_select;
  actual_date : OPTIONAL date_or_date_time_select;
END_ENTITY;
(*

Attribute definitions:

status: the Approval_status that provides a user interpretable designation of the level of approval.

purpose: the text that completes the information provided within the status attribute, specifying the reason or goal of the Approval.

EXAMPLE    'released for production' or 'preliminary design completed' are approval purposes.

planned_date: the point in time when the Approval is or was supposed to be performed. The value of this attribute need not be specified.

actual_date: the point in time when the Approval actually became valid. The value of this attribute need not be specified.

4.3.2 Approval_assignment   

EXPRESS specification:

*)
ENTITY Approval_assignment;
  assigned_approval : Approval;
  items : SET[1:?] OF approval_item;
  role : OPTIONAL STRING;
END_ENTITY;
(*

Attribute definitions:

assigned_approval: the Approval that is assigned with activity or product data.

items: the activity or product data to which the Approval is assigned.

role: the text that precises the role of the Approval with respect to the items it is assigned to. The value of this attribute need not be specified.

EXAMPLE    'legal requirement' is an example of role that may be used to represent the fact that a particular approval addresses a legal requirement for a product.

4.3.3 Approval_relationship   

EXPRESS specification:

*)
ENTITY Approval_relationship;
  relation_type : STRING;
  description : OPTIONAL STRING;
  relating_approval : Approval;
  related_approval : Approval;
END_ENTITY;
(*

Attribute definitions:

relation_type: the text that specifies the meaning of the relationship.

Where applicable, the following values shall be used:

• 'decomposition': The Approval_relationship defines a relationship where the related Approval is one of the components into which the relating Approval is broken down with no implication of 'sequence' or 'dependency';
• 'dependency': The Approval_relationship defines a relationship where the issuing of the related Approval is dependent on the issuing of the relating Approval;
• 'precedence': the Approval_relationship defines a relationship where the related Approval has higher priority than the relating Approval;
• 'sequence': The Approval_relationship defines a relationship where the relating Approval shall be completed before the related Approval is given.

NOTE    The value 'dependency' does not imply the semantics of the the values 'decomposition' or 'sequence'.

EXAMPLE 1   The Approval of an assembly may be dependent on the Approval of all of the constituents of the assembly.

EXAMPLE 2   In parallel approval processes of two assemblies, assignment of an Approval on one of the assemblies may depend on an Approval assigned to the second assembly.

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

relating_approval: one of the instances of Approval that is a part of the relationship.

related_approval: the other instance of Approval that is a part of the relationship. If one element of the relationship is dependent of the other, this attribute shall be the dependent one.

4.3.4 Approval_status   

EXPRESS specification:

*)
ENTITY Approval_status;
  status_name : STRING;
END_ENTITY;
(*

Attribute definitions:

status_name: the text by which the Approval_status is designated.

EXAMPLE    'approved' and 'disapproved' are examples of Approval_status.

4.3.5 Approving_person_organization   

EXPRESS specification:

*)
ENTITY Approving_person_organization;
  person_organization : organization_or_person_in_organization_select;
  approval_date : OPTIONAL date_or_date_time_select;
  authorized_approval : Approval;
  role : OPTIONAL STRING;
END_ENTITY;
(*

Attribute definitions:

person_organization: the Organization or the Person_in_organization that has granted the approval.

approval_date: the point in time when the Approval has been given. The value of this attribute need not be specified.

authorized_approval: the Approval that has been given by the considered person or the organization.

role: the text that specifies the role of the considered person or organization with respect to the approval. The value of this attribute need not be specified. By default, the person or organization shall only be considered as an approver without any specific role.

EXAMPLE    'quality insurance auditor', 'production cost examiner' are examples of values of role of persons or organizations with respect to approvals assigned to product data.

© ISO 2018 — All rights reserved