RE: Dex 8

["Tim turner" <timturner11@bellsouth.net>]

Apologies for the poor format of the last two messages - please delete them
as I think they are un-readable.
Here is a another copy which originally bounced from the exploder.
Tim

-----Original Message-----
From: tim turner [mailto:tim_the_intrepid@yahoo.co.uk]
Sent: 24 August 2004 20:46
To: 'tim turner'; 'Hendrix, Thomas E'; Plcs (E-mail)
Cc: Robert M Mcbride (E-mail)
Subject: RE: DEX 8
Tom & other Dex8 gurus!
without wishing to stir up the hornet's nest -
Dex8 has both within it's scope statement at present, but the capabilities
for this are all but none existant except for that explained within C045
(product_as_realized). Either Dex8 is seriously under-developed on the
representation of product_as_planned or a new Dex is required.
The business need for this is two-fold (probably others too?);
a) for OEMs to track designs thru to realized products & vice-versa
b) for in-service planning of refits & outfitting (however, we need to be
wary of the difference between this & re-supply of consumables).
My question to all is this; are we expecting to use Dex8 for exchanging BOTH
types of information? That is both products as planned and/or products as
realized? Is it expected that both product_as_planned & product_as_realized
views will always only be used in the same exchange scenarios, or can/should
they be able to be used separately?
I think the decision on this will dictate whether we need to generate a
bunch more capabilities, or to amalgamate this functionality into other
existing ones.
Merging them is of course, means that dexlib will suck in all the express
entities for that additional functionality which is something previously
hotly contested by those who only want to implement the required entities
for a specific exchange capability.
Given the current capabilities in Dex8 (specifically C045), Dex8 has both
relationships product_design_to_individual and product_planned_to_realized,
it would also not be inconceivable to think that Dex8 would also cover
design data from Dex1 (albeit in the form of a different set of capabilities
which largely pull in the same information)!
Kind regards,
Tim