assigning_identifiers

Capability (C001):— assigning_identifiers

Date: 2007/08/09 14:58:28
Revision: 1.52

Cover Contents Intro.Overview Info. model Templates Capabilities Ref. data Issues

Issue raised against: assigning_identifiers

GENERAL issues

Issue: TJT-4 by Tim Turner (Nov 13th 2005) minor_technical issue
Resolution: Accept. Status: open

It is not clear whether reference data which is hidden by templates should be included in the model reference data. E.g. organization_name is used by a template that is called by assigning_identification, however, it is not input to the original template call - but is har-coded (mandated) by the second template. Should this be listed anyhow?

Comment: (Peter Bergström 2007-05-24)
No, it should be listed in the underlying template/capability instead.

Issue: GYL-9 by Leif Gyllstrom (05-10-03) minor_technical issue
Resolution: Accept. Status: open

General issue against all figures. Use bike data.

Issue: GYL-13 by Leif Gyllstrom (05-10-03) minor_technical issue
Resolution: Accept. Status: open

Short form graphics are missing for the capability templates.

Issue: DNV-40 by Sylvia Schwab on behalf of DNV (07-03-07) major_technical issue
Resolution: Accept. Status: open

There is a need to represent a code with its description and explicit reference to its encoding system (C093 does not contain description and does not reference the encoding system explicitly).

Proposal: Add NEW template to C001 called representing_code (repr_code) with the associated name and reference to the encoding system used.

Identification_assignment.identifier (with reference data as per example 1 hereafter) holds the code_name, and is referenced by either an encoding system document or an instance of assigning_descriptor (C095). The Identification_assignment is classified by an internal class (with reference data as per example 1) where Class.name holds the "name". An organization shall optionally be assigned Identification_assignment the same way as in template assigning_identification.

Example 1:

For an instance of Representing_code, the Identification_assignment providing the "code" (e.g. Identification_assignment.identifier="3") shall be assigned Reference data that specifically identifies the type of code (e.g. "Safety_code"). The Class entity that holds the "name" associated with the "code" (e.g. Class.name="Critical") is assigned Reference data that specifically identifies the type of name (e.g. "Safety_code_name"), applying the postfix "_name" to reference data name assigned to the code.
Rule 1: For an instance of Identification_assignment there shall be one instance of Assigning_referenced_document classified as Encoding_system or one instance of Assigning_descriptor addressing the code origin.
Mapping rule 1: If neither Encoding document nor description exists in the population, populate Assigning_descriptor. Document.description with "/NULL".

Comment: (Peter Bergström 2007-05-24)
Codes should be handled as described in Capability assigning_codes. That means that using your example above, you use template assigning_code and give the code (e.g. "3") in parameter class_code and assign a reference data class (e.g. "Safety_code" in param code_class_name) representing the encoding system, to give it a meaning. What's missing here is of course the description of what the code means ("Critical"), but the reference data class (code_class_name) defintion should point you to the definition of all codes. You just have to use a code_class_name that is specific to your classification codes, "Safety_code" is not enough.
You could also define each code as a reference data class, and use assigning_reference_data. That would give you the exact definition for each code immediately, and that definition would probably say what encoding system you use as well.
I think it is wrong to provide the definition of the code in instance data, as suggested above. As soon as you enter the world of reference data, you should not provide further information about that data in the instance file, but through the class definition and description.
I see no need for a new template here.

Issue: RBN-13 by Rob Bodington (07-08-09) minor_technical issue
Resolution: Accept. Status: open

Move template representing_code to NDLO/templates

GENERAL issues

Issue: RBN-1 by Rob Bodington (04-01-16) minor_technical issue
Resolution: Accept. Status: closed

There should be minimal characterization of the identification_assignment. This should just be organization assignment, classification and date time. The diagrams and text should reflect this.

Comment: (Tim Turner 05th Feb 2004)
Characterization revised. Overview updated. Examples and model diagrams updated.

Issue: RBN-2 by Rob Bodington (04-01-16) minor_technical issue
Resolution: Accept. Status: closed

Comment: (Tim Turner 05th Feb 2004)
Empty issue

Issue: TJT-2 by Tim Turner (05-04-11) minor_technical issue
Resolution: Accept. Status: closed

Version 1.32 of this capability contains material developed for the example Dex and introduces tables of contraints, rules and sections which will be moved to the business DEXs area. This capability needs to be reset to version 1.28 to effect this.

Comment: (Tim Turner 19th Apr 2005)
Capability 1.32 was updated with the content from version 1.28

Issue: TJT-1 by Tim Turner (Feb 4th 04) minor_technical issue
Resolution: Accept. Status: closed

The EXPRESS example for date_time is missing the date entity instance

Comment: (Tim Turner 18th Oct 2004)
Fixed

Issue: TJT-1 by Tim Turner (Feb 4th 04) editorial issue
Resolution: Accept. Status: closed

I would like to provide a digram of ref data concepts, but it seems impossible in the ref data section itself (see Figure 9) in usage guidence section.

Comment: (Tim Turner 18th Oct 2004)
Not an issue against the capability. Closed.

Issue: TJT-1 by Tim Turner (Feb 4th 04) editorial issue
Resolution: Accept. Status: closed

Need to link in the ref data added in Bristol, Jan 04

Comment: (Tim Turner 18th Oct 2004)
Fixed

Issue: RBN-3 by Rob Bodington (04-09-21) minor_technical issue
Resolution: Accept. Status: closed

I think that you should make clear that if the same identifier is being assigned to multiple things, for example the same serial number applied to several versions of the product_as_realized

Comment: (Tim Turner 18th Oct 2004)
Not sure that i understand the question/issue. I think that each PAR is a separate version (that exists), therefore, it would have a different serial number to any other version. Assigning identifiers does not deal with versions. Actually, I shouldn't have used serial number as another type of identification for a Part - since this is at the design stage - NSN would have been better example. Raise another issue to clarify the question if required.

Issue: RBN-4 by Rob Bodington (05-02-07) minor_technical issue
Resolution: Accept. Status: closed

Figure 4.6 shows a serial number AND a part number being assigned to a part. A serial number should only be assigned to product-as_individual.

Comment: (Tim Turner 12th Nov 2005)
Example updated and problem fixed.

Issue: RBN-5 by Rob Bodington (05-09-02) minor_technical issue
Resolution: Accept. Status: closed

I think that there is room for confusion between codes used as a classification and codes used for identification. A part number may well be a code. When it is used to identify a part, identification assignment should be used. I think that this needs to be stated in this capability. I also think that an example showing the classification of the part number should also be provided.

Comment: (Tim Turner 12th Nov 2005)
Added clarification on difference between identifiers and codes to the business overview section. There are several examples of part type codes (aka part number) being assigned and classified as such.

Issue: RBN-7 by Rob Bodington (05-09-21) minor_technical issue
Resolution: Accept. Status: closed

There should be another template, assigning_classified_identification which assigns an identifier that is a sub class of a standard PLCS identifier. E.g. The FMV part number would be a sub class of Part_type_code, so the template should use the assigning_business_specific_reference_data.

Comment: (Tim Turner 12th Nov 2005)
I assume that this is to enable users to specify the reference data library, rather than have it hard coded. Will work on it.

Comment: (Tim Turner 13th Nov 2005)
I believe that by including assigning_identification_with_no_organization (as suggested by RBN-8 - that refers to the same template), that this issue is closed.

Issue: RBN-8 by Rob Bodington (05-09-21) minor_technical issue
Resolution: Accept. Status: closed

The assigning_classified_identification template should be moved from assigning_organization to assigning_identifiers capability. The template can then used to identify things where the organization that "owns" the identifier is not known, or is not important. The template should be renamed to: assigning_identification_with_no_organization

Comment: (Tim Turner 12th Nov 2005)
Working on it.

Comment: (Tim Turner 13th Nov 2005)
Now added to C001

Issue: RBN-9 by Rob Bodington (05-09-21) minor_technical issue
Resolution: Accept. Status: closed

The capability should make clear that the classification of the identifier should make the codification system used to create the identifier explicit. For example, if a part number has been encoded according to a particular coding standard, then there should be a class representing that standard, and that class should be a sub class of the part_identification_code. Hence it is clear that the id has been encoded according a particular standard and is a part_identification_code. The description of the class should make it clear which codification system and rules have been used.

Comment: (Tim Turner 12th Nov 2005)
Description emboying above added.

Issue: RBN-10 by Rob Bodington (05-09-21) minor_technical issue
Resolution: Accept. Status: closed

The capability refers to part_type_code - this class does not exist in the reference data - it should be part_identification_code

Comment: (Tim Turner 12th Nov 2005)
Fixed.

Issue: GYL-1 by Leif Gyllstrom (05-10-03) minor_technical issue
Resolution: Accept. Status: closed

Second section in Information Model Overview - Avoid descriptions on how not to use the model.

Comment: (Tim Turner 12th Nov 2005)
Removed.

Issue: GYL-2 by Leif Gyllstrom (05-10-03) minor_technical issue
Resolution: Accept. Status: closed

Figures 2 and 3. Color coding templates is not required (redundant information).

Comment: (Tim Turner 12th Nov 2005)
Re-formatted.

Issue: GYL-3 by Leif Gyllstrom (05-10-03) minor_technical issue
Resolution: Accept. Status: closed

First section under Figure 3 and first section in paragraph - Avoid descriptions on how not to use the model.

Comment: (Tim Turner 12th Nov 2005)
Done.

Issue: GYL-4 by Leif Gyllstrom (05-10-03) minor_technical issue
Resolution: Accept. Status: closed

First section under Figure 3 - The description attribute shall not be used (set to /IGNORE). The description of the identifier is provided through reference data and its description in the RDL.

Comment: (Tim Turner 12th Nov 2005)
Fixed.

Issue: GYL-5 by Leif Gyllstrom (05-10-03) minor_technical issue
Resolution: Accept. Status: closed

All references to reference data shoud be done using the tag rdl_ref. This ensures that reference data used actually exists in the RDL.

Comment: (Tim Turner 12th Nov 2005)
Done.

Issue: GYL-6 by Leif Gyllstrom (05-10-03) minor_technical issue
Resolution: Accept. Status: closed

Figures 4.2 and 4.3. Color coding and capability identification is redundant information to capability templates.

Issue: GYL-7 by Leif Gyllstrom (05-10-03) minor_technical issue
Resolution: Accept. Status: closed

Reference data given in examples shall correspond to reference data defined in the PLCS RDL. Figure 4.2, 4.3, 4.4 and 4.5 Identification_assignment skall be classified as Part_identification_code. Figure 4.3 and 4.4 Organization_assignment Org-id-classification shall be Organization_name. Figure 4.4 and 4.5 Date_time_assignment date_class_name shall be Date_actual.

Issue: GYL-10 by Leif Gyllstrom (05-10-03) minor_technical issue
Resolution: Accept. Status: closed

First section umder Figure 4.3 says : The instantiation diagram above shows the use of Organization_or_person_in_organization_assignment for both identifying and assigning an Organization to the identifier and establishing it's usage through it's classification_assignment. Comment - It does not !!

Comment: (Tim Turner 12th Nov 2005)
Removed.

Issue: GYL-11 by Leif Gyllstrom (05-10-03) minor_technical issue
Resolution: Accept. Status: closed

Figures 4.5, 4.7 and 4.9 are not complete, which must be a Requirement if templates are not used. The Organization is identified using the name attribute, which is not the recommended approach for assigning identifiers.

Comment: (Tim Turner 12th Nov 2005)
Fixed.

Issue: GYL-12 by Leif Gyllstrom (05-10-03) minor_technical issue
Resolution: Accept. Status: closed

The current content in section Additional Usage Guidence does not provide any new information. Is a summary of the previous section. Move section on Multiple identification into Additional Usage Guidence.

Comment: (Tim Turner 12th Nov 2005)
Done.

Issue: GYL-14 by Leif Gyllstrom (05-10-03) minor_technical issue
Resolution: Accept. Status: closed

Figure 5.3, 5.4 and 5.6. org_id_class_name shall be Organization_name.

Comment: (Tim Turner 12th Nov 2005)
Done.

Issue: GYL-15 by Leif Gyllstrom (05-10-03) minor_technical issue
Resolution: Accept. Status: closed

The ref_data_library.id attribute in all figures should be changed to urn:plcs:rdl:std.

Comment: (Tim Turner 12th Nov 2005)
Done.

Issue: GYL-16 by Leif Gyllstrom (05-10-03) minor_technical issue
Resolution: Accept. Status: closed

Usage section do not render properly !

Comment: (Tim Turner 12th Nov 2005)
Re-formatted.

Issue: RBN-11 by Rob Bodington (05-11-10) minor_technical issue
Resolution: Accept. Status: closed

Remove the attributes rd_library and rd_class_of_class They are redundant.

Comment: (Tim Turner 12th Nov 2005)
Done.

Issue: NN-1 by Nigel Newling (05-11-16) editorial issue
Resolution: Accept. Status: closed

The instance #7048 is referred to as serial_identification in tex but breakdown_identification in figure 4.9.

Comment: (Tim Turner 29th Nov 2005)
Fixed.

Issue: RBN-12 by Rob Bodington (05-11-23) minor_technical issue
Resolution: Accept. Status: closed

The EXPRESS-G in Figure 5.1 in template assigning_identification should have a reference parameter ^id_assign assigned to entity Identification_assignment

Comment: (Tim Turner 29th Nov 2005)
Fixed.