RE: [plcs-dex] RE: [plcs-Dex] Capability/Dex structuring

["Hendrix, Thomas E" <thomas.e.hendrix@boeing.com>]

Title: Message

In fact attachment_slot is also "slotted" for representing_product_as_realized_assembly

 

 

Regards,
Tom

Thomas E. Hendrix
Phone: 206-544-5276
thomas.e.hendrix@boeing.com

-----Original Message-----
From: Tim [mailto:timturner11@bellsouth.net]
Sent: Friday, June 04, 2004 12:54 AM
To: 'Les Debenham'
Cc: plcs-dex@lists.oasis-open.org
Subject: RE: [plcs-dex] RE: [plcs-Dex] Capability/Dex structuring

Les,

 

there is no mis-understanding about the module & what it contains. The question was about where the capability of slots gets described since there are two potential places (slots?)!  I believe that we are best served by the creation of a single capability for this purpose which is then brought in as dependant into both assemblies (C003) and breakdowns (C004) where it can be used. The module (attachment_slot) would be the main ingredient of the new capability.

 

Regards,

Tim

 

NB - do you have any insights (as below) for slot usage within breakdowns as well as assemblies?

-----Original Message-----
From: Les Debenham [mailto:lad@lsc.co.uk]
Sent: 04 June 2004 03:45
Cc: plcs-dex@lists.oasis-open.org
Subject: [plcs-dex] RE: [plcs-Dex] Capability/Dex structuring

There is already a module called attachment_slot. Are we allowed to use modules? Or must we create a new capability

For the record:
attachment_slot specifies an application module for the representation of data that tracks selected parts as an assembly and to note when some of those parts are not installed. A slot represents the position in which a part is or can be attached to an assembly, when it is necessary to record the history of usage of that slot.

A slot may be identified whenever there two parts that are physically interfaced. If the details of this interface are required then the slot may be associated with applicable instances of the Interface_connector and Interface_specification entity data types.

A slot has an identification and may have one or more versions (Slot_version), and each may have one or more applicable view definitions (Slot_definition). A slot version may exist in the form of a designed slot (Slot_design), a planned slot (Slot_as_planned) and realized slot (Slot_as_realized).

The relationships Product_in_slot and Slot_on_product identify which part or parts attach at a slot and on which part the slot is a location at which to attach one or more other parts.

Scope:
identification of positions within an assembly of parts to which component parts may be attached;
identification of parts that are attached to identified positions within an assembly.

Les Debenham
LSC Group Ltd.
PO Box 77 Devonport House
Durley Park, Bristol BS31 2YH

Tel: +44 117 916 1464
Fax: +44 117 916 1499
Mob: +44 7739 306799
www.lsc.co.uk

-----Original Message-----
From: Rob Bodington [mailto:rob.bodington@eurostep.com]
Sent: 03 June 2004 20:21
To: 'Barker, Sean (UK)'; 'Tim'
Cc: plcs-dex@lists.oasis-open.org
Subject: RE: [plcs-dex] Capability/Dex structuring

Sounds reasonable to me

Regards
Rob

-------------------------------------------  
Rob Bodington
Eurostep Limited
Web Page: http://www.eurostep.com http://www.share-a-space.com
Email: Rob.Bodington@eurostep.com
Phone: +44 (0)1454 270030
Mobile: +44 (0)7796 176 401

> -----Original Message-----
> From: Barker, Sean (UK) [mailto:sean.barker@baesystems.com]
> Sent: 03 June 2004 16:45
> To: Tim
> Cc: plcs-dex@lists.oasis-open.org
> Subject: RE: [plcs-dex] Capability/Dex structuring
>
>
> Tim
>       I would guess so, but Rob may have a view on this.
>
> Sean Barker
> ATC Filton
> 0117 302 8184
>
>
> -----Original Message-----
> From: Tim [mailto:timturner11@bellsouth.net]
> Sent: 03 June 2004 16:25
> To: Barker, Sean (UK)
> Cc: plcs-dex@lists.oasis-open.org
> Subject: RE: [plcs-dex] Capability/Dex structuring
>
>
> Saun,
>
> So, when more than one capability requires the same functionality, I presume
> that we should document that functionality independently (e.g. in another
> capability) and then reference that by those that require it, right?
>
> In that case - since both capabilities C003 (Assemblies) and C004 (breakdowns)
> both need to refer to Slots, I should create a separate capability, rather
> than doing it twice, correct?
>
> regards,
> Tim
>
> -----Original Message-----
> From: Barker, Sean (UK) [mailto:sean.barker@baesystems.com]
> Sent: 03 June 2004 11:09
> To: Tim
> Cc: plcs-dex@lists.oasis-open.org
> Subject: RE: [plcs-dex] Capability/Dex structuring
>
>
>
> Tim,
>       As I recall, no, though a capability can reference other capabilities.
>
> Sean Barker
> ATC Filton
> 0117 302 8184
>
> -----Original Message-----
> From: Tim [mailto:timturner11@bellsouth.net]
> Sent: 03 June 2004 16:00
> To: plcs-dex@lists.oasis-open.org
> Subject: [plcs-dex] Capability/Dex structuring
>
>
>
> A quick question to the wise.
>
> We have defined Dexs to be collections of capabilities. Is it also possible
> that a capability can be a collection of other capabilities?
>
> Regards,
> Tim
>
>
> ********************************************************************
> This email and any attachments are confidential to the intended
> recipient and may also be privileged. If you are not the intended
> recipient please delete it from your system and notify the sender.
> You should not copy it or use it for any purpose nor disclose or
> distribute its contents to any other person.
> ********************************************************************
>
> ********************************************************************
> This email and any attachments are confidential to the intended
> recipient and may also be privileged. If you are not the intended
> recipient please delete it from your system and notify the sender.
> You should not copy it or use it for any purpose nor disclose or
> distribute its contents to any other person.
> ********************************************************************

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