Issues against assigning_identification and representing_part

["Rob Bodington" <rob.bodington@eurostep.com>]

Hi

I have just raised these issues against:

template assigning_identification

template representing_part

 

They are basically concerned with the unique rule required to ensure that there is only one occurrence of a given part  in an exchange file.

 

<!-- ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ -->

<issue

   id="RBN-5"

   type="general"

   status="open"

   category="minor_technical"

   by="Rob Bodington"

   date="07-08-06">

<description>

The template contains the Unique constraint

 

Unique constraint: Unique identifier

There shall be at most one instance of the entity

(Identification_assignment) within the data set uniquely identified by a

combination of the following template parameters: id, id_class_name,

id_ecl_id, org_id, org_id_class_name, org_id_ecl_id. The instance is

referenced by the following template parameter: id_assgn.

 

This constraint is over restrictive. For example, if you have two PARTs A

and B, each which have a PART_VERSION at version 1.

The constraint means that there will be one instance of

IDENTIFICATION_ASSIGNMENT assigned to both PART_VERSIONs

E.g.

#42083=IDENTIFICATION_ASSIGNMENT('version 1','/IGNORE','$',(#128690,#130652))

 

Whilst correct according to the model, it means that you cannot assign any

dates or effectivity to the IDENTIFICATION_ASSIGNMENT.

 

It would be better if the IDENTIFICATION_ASSIGNMENT entity was split into

the Identifier and the assignment of the identifier. As it stands it does

both.

 

Rather than changing the model, the Unique constraint should be removed and

then applied when using the IDENTIFICATION_ASSIGNMENT.

 

For example, there should be a unique constraint in the Template

representing_part that states 

 

Unique constraint: Unique part version

There shall be at most one instance of the entity (Part_version) within the

data set uniquely identified by a combination of the following template

parameters: part_id, part_id_class_name, part_id_ecl_id, part_org_id,

part_org_id_class_name, part_vn_id, part_vn_id_class_name,

part_vn_id_ecl_id, part_vn_org_id, part_vn_org_id_class_name. The instance

is referenced by the following template parameter: version. 

 

This rule means that there can be only one version (Part_version) of a part

(Part) with any given identifier. 

</description>

 

<!-- ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ -->

<issue

   id="RBN-4"

   type="general"

   status="open"

   category="minor_technical"

   by="Rob Bodington"

   date="07-08-06">

<description>

There should be a uniqueness constraint that force a unique part and

version.

 

E.g.

Unique constraint: Unique part

There shall be at most one instance of the entity (Part) within the data

set uniquely identified by a combination of the following template

parameters: part_id, part_id_class_name, part_id_ecl_id, part_org_id,

part_org_id_class_name. The instance is referenced by the following

template parameter: part. 

 

Unique constraint: Unique part version

There shall be at most one instance of the entity (Part_version) within the

data set uniquely identified by a combination of the following template

parameters: part_id, part_id_class_name, part_id_ecl_id, part_org_id,

part_org_id_class_name, part_vn_id, part_vn_id_class_name,

part_vn_id_ecl_id, part_vn_org_id, part_vn_org_id_class_name. The instance

is referenced by the following template parameter: version. 

 

This rule means that there can be only one version (Part_version) of a part

(Part) with any given identifier. 

 

</description>

 

Regards
Rob

-------------------------------------------   
Rob Bodington
Eurostep Limited
Tel: +44 (0)1452 810 960
Mobile: +44 (0)7796 176 401
Email: Rob.Bodington@eurostep.com
Web: http://www.eurostep.com

Eurostep Limited. Registered in England and Wales No.03049099

Registered Office: Cwttir Lane, St. Asaph, Denbighshire LL17 0LQ.