|
Hi
Gordon,
are
saying that version relationships (aka product_version_relationships) are
not necessarily the only mechanism needed to distinguish between
versions?
I just
want to acertain whether you are raising an issue against adding version
relationships to this capability.
cheers,
Tim
Rob,
Your 1st para requires a slight amendment "All I am saying is
that we need to (and can) be able to represent/model the fact that a part
version can be related to another part version. In other words I want
to run a query on a database along the lines of I have Part XYZ at version 3,
What are the
other versions of
part XYZ?" This then caters for the fact that
common items for multiple customers are identified by a means of identifying
the correct version for each
customer.
e.g. 75A450123-2001 - FAIRING = AV-8B CUM 1 thru 125
;
75A450123-2003 -
FAIRING = GR5 CUM 1 thru
23;
75A450123-2005 -
FAIRING = SAV-8B CUM 1 THRU
14
75A450123-2007 -
FAIRING = AV-8B CUM 126 thru 167
My query to the 'database would be "Find all versions
of 75A450123................
The dash number in this case is the means of
versioning the fairing. I cannot ever remember seeing any Version 1 or 2
or 3 on drawing sets associated with the Aero world
It should be noted that the PLCS TD in which we are
supposed to be adhering to
states " product
identifier"
Definition
A name or alphanumeric identifier, used to designate a part or assembly, of the same configuration, and to
differentiate it from all other products.
Note
These identifiers may include a supplementary identifier used to
distinguish one of several sequentially created configurations of a product
from the previous configuration of the same product (i.e. revision or version)."
Gordon
Gordon
All I am saying is
that we need to (and can) be able to represent/model the fact that a part
version is related to a previous part version.
In other words I
want to run a query on a database along the lines of I have Part XYZ at
version 3, What was the previous version of part XYZ?
It is common
practice not to version parts, but to renumber them. Hence we need to (and
can) be able to represent/model the fact that a part is derived from a
previous part.
This information
does not necessa[Gordon
Robb] B rily require assembly
information.
That's
all.
Regards
Rob
-----Original
Message-----
From: Gordon
Robb [mailto:gor@lsc.co.uk]
Sent: 16 August 2005 07:36
To: 'Rob.Bodington@eurostep.com'; Tim
Turner; 'DEXS-PLCS-OASIS (E-mail)'
Subject: RE: [plcs-dex] Representing
parts - Issue: RBN-11
You
have to be careful in your statement 'fact that a version
of a part follows on the previous version' - there can be occasions were
there is concurrently several versions of the part in production dependent
on the customer base.
-----Original
Message-----
From: Rob
Bodington [mailto:rob.bodington@eurostep.com]
Sent: 15 August 2005
16:16
To: 'Tim Turner';
'DEXS-PLCS-OASIS (E-mail)'
Subject: RE: [plcs-dex] Representing
parts - Issue: RBN-11
I
don't believe that there is an issue in using an entity in more than one
capability.
-----Original
Message-----
From: Tim
Turner [mailto:tjt@lsc.co.uk]
Sent: 15 August 2005
15:54
To:
'Rob.Bodington@eurostep.com'; Tim Turner; 'DEXS-PLCS-OASIS
(E-mail)'
Subject: RE:
[plcs-dex] Representing parts - Issue: RBN-11
Fair
enough. But is there an issue with using product_version_relationship within
more than one capability like this?
If
this would be an issue, I'd propose to move the
subtype as well to rep_parts, else, I'd just move the super
type.
-----Original
Message-----
From: Rob
Bodington [mailto:rob.bodington@eurostep.com]
Sent: 15 August 2005
04:25
To: 'Tim Turner';
'DEXS-PLCS-OASIS (E-mail)'
Subject: RE: [plcs-dex]
Representing parts - Issue: RBN-11
My
motivation for writing the comment was that I want to represent the fact
that a version of a part follows on the previous
version.
Initially this
has nothing to do with an assembly of parts - it is just about the
part.
Similarly if a
Part is derived from another part, I want to relate the two. Again, this
has nothing to do with an assembly. Hence my suggestion that these
representations should be in the rep_part capability.
Regards
Rob
-----Original
Message-----
From: Tim
Turner [mailto:tjt@lsc.co.uk]
Sent: 12 August 2005
18:35
To:
DEXS-PLCS-OASIS (E-mail)
Subject: [plcs-dex] Representing
parts - Issue: RBN-11
In the interest of
visibility My response & comments to the issue are provided
below;
RBN-11 by
Rob Bodington (05-02-21) minor_technical issue
The relationship between
different version(s) should be described in this capability, not
"representing_assembly_structure" (C003). The
product_version_relationship should be treated in the same way as in
representing product as individual, and use the same classification. I
propose: Derived_version_relationship Sequential_version_relationship
Hierarchical_version_relationship as defined in the PDM Schema usage
guide.
TJT
Response: Relationships between
parts, part versions and view_definitions are not currently described
within Representing_parts. They are described within
representing_assembly_structures as these relationships are used to
define the assembly structures and how those structures might change if
different versions of a part are used. However, it is possible to
include product_version_relationship in this capability, but it would
then exist in both. This is because supplied_part_relationship (a
subtype) would & I believe should, stay within C003. Though I could
be persauded.
I agree with the use of the
classification and the ref data derived from the PDM
schema.
Comments?
regards,
Tim
*************************************************************************
*
* Mr. Timothy J. Turner BSC(Hons)
MSc, MBCS
*
Executive Consultant, Enterprise Integration
Technologies
* LSC Group, Lincoln House, Wellington Crescent,
Fradley Park, LICHFIELD, Staffordshire WS13 8RZ,
ENGLAND
* UK
Switchboard: +44-1543 446800 Fax: +44-1543 446900
* US Direct telephone: +1-803-327
2829 (Rock Hill)
* Mobile (US) telephone:
+1-843-4759179
* Mobile (UK) telephone:
+44-7885-393225
* e-mail: tjt@lsc.co.uk <mailto:tjt@lsc.co.uk>
Internet: <http://www.lsc.co.uk/>
*
*************************************************************************
DISCLAIMER:
***SECURITY LABEL: NOT PROTECTIVELY MARKED*** The
information in this message is confidential and may be legally
privileged. It is intended solely for the addressee. Access to
this message by anyone else is unauthorised. If you are not the
intended recipient, any disclosure, copying, or distribution of the
message, or any action or omission taken by you in reliance on it, is
prohibited and may be unlawful. Please immediately contact the
sender if you have received this message in error. This e-mail
originates from LSC Group. Registered in England & Wales No 2275471
Registered Office: Devonport Royal Dockyard, Devonport, Plymouth, PL1
4SG
DISCLAIMER:
***SECURITY LABEL: NOT PROTECTIVELY MARKED*** The information in this
message is confidential and may be legally privileged. It is intended
solely for the addressee. Access to this message by anyone else is
unauthorised. If you are not the intended recipient, any disclosure,
copying, or distribution of the message, or any action or omission taken
by you in reliance on it, is prohibited and may be unlawful. Please
immediately contact the sender if you have received this message in error.
This e-mail originates from LSC Group. Registered in England & Wales
No 2275471 Registered Office: Devonport Royal Dockyard, Devonport,
Plymouth, PL1 4SG
DISCLAIMER: ***SECURITY LABEL: NOT
PROTECTIVELY MARKED*** The information in this message is confidential and
may be legally privileged. It is intended solely for the addressee. Access
to this message by anyone else is unauthorised. If you are not the intended
recipient, any disclosure, copying, or distribution of the message, or any
action or omission taken by you in reliance on it, is prohibited and may be
unlawful. Please immediately contact the sender if you have received this
message in error. This e-mail originates from LSC Group. Registered in
England & Wales No 2275471 Registered Office: Devonport Royal Dockyard,
Devonport, Plymouth, PL1 4SG
DISCLAIMER: ***SECURITY LABEL: NOT PROTECTIVELY MARKED*** The information in this message is confidential and may be legally privileged. It is intended solely for the addressee. Access to this message by anyone else is unauthorised. If you are not the intended recipient, any disclosure, copying, or distribution of the message, or any action or omission taken by you in reliance on it, is prohibited and may be unlawful. Please immediately contact the sender if you have received this message in error. This e-mail originates from LSC Group. Registered in England & Wales No 2275471 Registered Office: Devonport Royal Dockyard, Devonport, Plymouth, PL1 4SG
|