[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [no subject]
=20
However, some of the sections on this subject are indeed more generic & =
for
example, under the capability representing_assembly_structure the first
pre-processor statement reads...
=20
No cyclic part_view_definiton structures may be defined. The value of =
the
identification_assignment.identifier (for PDM Schema this is the local =
id
attribute) must be unique in combination with the same relating assembly =
and
related component definitions. For PLCS this implies that the identifier =
for
each part_view_definition, part_version and part must be unique within =
the
assembly. It is generally recommended that only subtypes of
assembly_component_relationship be instantiated. It is not necessary to
instantiate the optional relation_type, location_indicator or quantity
attributes for an instance of next_assembly_usage in the context of a =
basic
parts list. If information on the assembly type is to be represented, =
then this
additional information should be represented using the
view_definition_context.description attribute. This information is =
linked
through the part_view_definition.additional_contexts attribute inherited =
from
product_view_definition (leaving the application_domain and =
life_cycle_stage
attributes empty). Examples of such type information are 'functional =
assembly',
'manufacturing assembly', and 'design assembly'.....
.... I think most is still applicable, except for those examples which =
might be
different depending upon usage.
=20
Prop 1: This information, however, is now captured under the CVS =
versioning so
removing these sections for now, is not a problem and may aid =
consistency across
the capabilities. I could agree to putting this on the "back-burner" for =
now so
that the complexity issue can be ironed-out first; though I suspect we =
may need
to come back to it at some point.
=20
The other thing that seems to come out of this (for me at least) is a =
question
on whether the capabilities should document any of the items referenced =
from a
select type. In some capabilities I see examples that are specific to =
the Dex
within which it is primarily to be used, but when I look at Dex 1, I =
realize
that the example (entity used) in the capability is not actually present =
(e.g.
out of scope). Likewise, I could have done the same in generating =
capabilities
under Dex1 & for example, in assigning_identifiers I may have only used =
the
entity "Part" when showing how the identification_assignment works, =
though this
may not be present in al Dexs.=20
=20
Prop 2: We (modellers) need to decide if we are to document the contents =
of
these select types or not. I have actually documented ALL PLCS entities
available from the identification_item select type, though only chosen =
one for
the example. I have also added notes to state that this list may change
depending upon the usage of the capability (i.e. in which Dex) since the
contents of the list may be pruned according to the scope. However, =
someone
looking at the capability, from a *re-use point of view*, would be able =
to see
which entities are referable from the material and to make decisions =
accordingly
for the Dex they are planning. I would therefore, suggest this as a =
default
position when documenting the capabilties, (though I am still open to
discussion)!
=20
Kind regards,
Tim
-----Original Message-----
From: Leif.Tonning@dnv.com [mailto:Leif.Tonning@dnv.com]
Sent: 30 April 2004 07:53
To: timturner11@bellsouth.net
Cc: rob.bodington@eurostep.com; Trine.Hansen@dnv.com;
Jochen.Haenisch@epmtech.jotne.com
Subject: RE: Pre-post processor info
I get some of the picture.
As you are aware, we have had some uncertainty as to wether the current =
PLCS
capabilities and DEX'es can easily be reused in our pilots, and we have
communicated our needs and ideas back to Rob and others.
In this work we have not met the problem you refer to with documentation =
of
capabilities and the related DTD.
I appreciate that the PDM schema rightly calls on pre and =
postprocessors.
However, we have not met the need for these in our work. Why?
As in PLCS, we develop generic capabilities, and these are to a large =
extent of
the same type. Then we instantiate the capabilities to hold real data.
Currently, thes instantiated data are legacy type, not subject to
standardisation, but they should (using reference data) be identical to =
stable
logistics business data as found e.g. in DefStan 00-60. Then the =
instantiated
caps (possibly grouped inside a generic cap) should be standardised.
To be able to use caps (the instantiated ones), instantiation diagrams =
(also
candidates for standardisation when populated with reference data) are
developed. These represent business concepts where the caps are used and =
reused.
To populate a PLCS database, we have not met needs for postprocessing =
other than
as defined in the instantiations (the mapping diagrams). This, however, =
does not
mean that postprocessing is not an added value, but the need should be =
carefully
assessed before another level of complexity is added to PLCS.
To extract data from the PLCS database, query is used. Again no other =
need for
preprocessing, and again, carefully assess the need, complexity and cost
benefit..
We believe that the exchange specification for import and export =
technically is
the same, but there may be other reasons why this is not so.
Also, provided pre and post processing is introduced, care should be =
taken to
distinguish between the generic part and the instantiatied part. I see =
the
generic parts only as aids to develop the instantiated parts. When the =
logistics
domain is fully populated with instantiated reference data, these should =
be used
by all, and the need for the generic capabilities disappear. Mapping =
legacy data
to PLCS will then be done using the instantiation diagrams and the =
instantiated
capabilities. Databases and data exchanges will hold instantiated data =
(legacy
or the reference data substitution for the legacy data), not generic
capabilities.
=20
Knowing well I am operating in troubled water, I still hope this is to =
help and
not to confuse. If the latter, forget the mail.
=20
Best regards
Leif Tonning
=20
-----Original Message-----
From: Tim Turner [mailto:timturner11@bellsouth.net]=20
Sent: 29. april 2004 20:50
To: Tonning, Leif
Cc: rob.bodington@eurostep.com
Subject: RE: Pre-post processor info
Oh um, sorry!
=20
Well a lot of the early capabilities had sections on pre & post =
processor
guidence in the main body, underneath the descriptions of the entity =
attributes
being documented. For example, under representing assembly structures & =
BOM
there is a section on Postprocessor Recommendations. However, these =
sections
need to be moved to the usage area (I.e. in amongst the entity =
definitions), but
I cannot copy the section to that part as the dtd seems not to allow it. =
I need
to see some sort of example on how this should be done, or for the dtd =
to change
to enable a simpler format.
=20
I believe that I can just delete the attribute sections I have manually =
provided
since these are already available in the usage area.
=20
Regards,
Tim
=20
=20
-----Original Message-----
From: Leif.Tonning@dnv.com [mailto:Leif.Tonning@dnv.com]
Sent: 29 April 2004 02:46
To: timturner11@bellsouth.net
Cc: rob.bodington@eurostep.com
Subject: RE: Pre-post processor info
Hi, Tim=20
Sorry, I'm not on the net. Probably I have missed some communication and =
do not
understand what you are asking.=20
I will do my best to give you an answer, but need better to understand =
the issue
Leif t=20
-----Original Message-----=20
From: Tim Turner [ <mailto:timturner11@bellsouth.net>
mailto:timturner11@bellsouth.net]=20
Sent: 28. april 2004 20:32=20
To: Rob Bodington (E-mail); Tonning, Leif=20
Subject: Pre-post processor info=20
Guys,=20
I'm trying to address the issue of moving much of this information into =
the
usage section, but I need an example where this has been done that I can =
follow.
Do you have anything I could look at?=20
Cheers,=20
Tim=20
**************************************************************
Neither the confidentiality nor the integrity of this message can be =
guaranteed
following transmission on the Internet.=20
All messages sent to a DNV email addressee are swept by Sybari Antigen =
for the
presence of computer viruses.=20
DNV acknowledges that SPAM email represents a potential security risk, =
and DNVs
filters to block unwanted emails are therefore continuously adjusted. =
DNV has
disabled "out of office" replies to the Internet=20
**************************************************************=20
**************************************************************
Neither the confidentiality nor the integrity of this message can be =
guaranteed
following transmission on the Internet.=20
All messages sent to a DNV email addressee are swept by Sybari Antigen =
for the
presence of computer viruses.=20
DNV acknowledges that SPAM email represents a potential security risk, =
and DNVs
filters to block unwanted emails are therefore continuously adjusted. =
DNV has
disabled "out of office" replies to the Internet=20
**************************************************************=20
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=20
------=_NextPart_000_0059_01C431BA.3F31E890
Content-Type: text/html;
charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<html>
<head>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 10 (filtered)">
<title>Message</title>
<style>
<!--
/* Font Definitions */
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman";}
a:link, span.MsoHyperlink
{color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{color:blue;
text-decoration:underline;}
p
{margin-right:0cm;
margin-left:0cm;
font-size:12.0pt;
font-family:"Times New Roman";}
address
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman";
font-style:italic;}
span.EmailStyle20
{font-family:Arial;
color:blue;
font-weight:normal;
font-style:normal;
text-decoration:none none;}
@page Section1
{size:595.3pt 841.9pt;
margin:72.0pt 90.0pt 72.0pt 90.0pt;}
div.Section1
{page:Section1;}
/* List Definitions */
ol
{margin-bottom:0cm;}
ul
{margin-bottom:0cm;}
-->
</style>
</head>
<body lang=3DEN-GB link=3Dblue vlink=3Dblue>
<div class=3DSection1>
<p class=3DMsoNormal><font size=3D1 color=3Dblue face=3DArial><span =
style=3D'font-size:
9.0pt;font-family:Arial;color:blue'>I agree with =
Gordon.</span></font></p>
<p class=3DMsoNormal><font size=3D1 color=3Dblue face=3DArial><span =
style=3D'font-size:
9.0pt;font-family:Arial;color:blue'>Furthermore, please use the <a
href=3D"mailto:plcs-dex@lists.oasis-open.org";>plcs-dex@lists.oasis-open.o=
rg</a> exploder
rather than the ATI exploder.</span></font></p>
<div>
<p><font size=3D2 color=3Dblue face=3DArial><span =
style=3D'font-size:10.0pt;font-family:
Arial;color:blue'>Regards<br>
Rob</span></font></p>
<p><font size=3D2 color=3Dblue face=3DArial><span =
style=3D'font-size:10.0pt;font-family:
Arial;color:blue'>------------------------------------------- =
<br>
Rob Bodington<br>
Eurostep Limited<br>
Web Page: </span></font><font color=3Dblue><span style=3D'color:blue'><a
href=3D"http://www.eurostep.com";><font size=3D2 face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial'>http://www.eurostep.com</span></font></a></span=
></font><font
size=3D2 color=3Dblue face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;
color:blue'> </span></font><font color=3Dblue><span =
style=3D'color:blue'><a
href=3D"http://www.share-a-space.com";><font size=3D2 face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial'>http://www.share-a-space.com=
</span></font></a><br>
</span></font><font size=3D2 color=3Dblue face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial;color:blue'>Email: Rob.Bodington@eurostep.com<br>
Phone: +44 (0)1454 270030<br>
Mobile: +44 (0)7796 176 401</span></font></p>
</div>
<div style=3D'border:none;border-left:solid blue 1.5pt;padding:0cm 0cm =
0cm 4.0pt'>
<p class=3DMsoNormal><font size=3D2 face=3DTahoma><span lang=3DEN-US =
style=3D'font-size:
10.0pt;font-family:Tahoma'>-----Original Message-----<br>
<b><span style=3D'font-weight:bold'>From:</span></b> Gordon Robb
[mailto:gor@lsc.co.uk] <br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> 04 May 2004 =
09:21<br>
<b><span style=3D'font-weight:bold'>To:</span></b> Plcs-Modelers-L =
(E-mail);
Plcs-Dex teams (E-mail); </span></font><font size=3D2 =
face=3DTahoma><span
lang=3DEN-US style=3D'font-size:10.0pt;font-family:Tahoma'>Tim =
Turner</span></font><font
size=3D2 face=3DTahoma><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:Tahoma'>
(Offsite)<br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> [plcs-dex] FW: =
Pre-post
processor info</span></font></p>
<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'> </span></font></p>
<div>
<p class=3DMsoNormal><font size=3D2 color=3Dteal face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:teal'>It would be of beneficial to all =
involved
in the current programme if this type of query was broadcast via the
'exploders' instead of depending on the good faith of other 'team =
players'</span></font></p>
</div>
<div>
<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'> </span></font></p>
</div>
<div>
<p class=3DMsoNormal><font size=3D2 color=3Dteal face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:teal'>Gordon</span></font></p>
</div>
<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><font size=3D2 =
face=3DTahoma><span
style=3D'font-size:10.0pt;font-family:Tahoma'>-----Original =
Message-----<br>
<b><span style=3D'font-weight:bold'>From:</span></b> Nigel Newling <br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> 04 May 2004 =
09:01<br>
<b><span style=3D'font-weight:bold'>To:</span></b> Les Debenham; Gordon =
Robb<br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> FW: Pre-post =
processor
info</span></font></p>
<div>
<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'> </span></font></p>
</div>
<blockquote =
style=3D'margin-top:5.0pt;margin-right:0cm;margin-bottom:5.0pt'>
<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><font size=3D2 =
face=3DTahoma><span
style=3D'font-size:10.0pt;font-family:Tahoma'>-----Original =
Message-----<br>
<b><span style=3D'font-weight:bold'>From:</span></b> Tim Turner
[mailto:timturner11@bellsouth.net]<br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> 30 April 2004 =
17:02<br>
<b><span style=3D'font-weight:bold'>To:</span></b> =
Leif.Tonning@dnv.com<br>
<b><span style=3D'font-weight:bold'>Cc:</span></b> =
rob.bodington@eurostep.com;
Trine.Hansen@dnv.com; Jochen.Haenisch@epmtech.jotne.com; Nigel Newling =
(E-mail)<br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> RE: Pre-post =
processor
info</span></font></p>
<div>
<p class=3DMsoNormal><font size=3D2 color=3Dblue face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:blue'>Leif,</span></font></p>
</div>
<div>
<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'> </span></font></p>
</div>
<div>
<p class=3DMsoNormal><font size=3D2 color=3Dblue face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:blue'>Still waters run deep, so any =
troubled
ones are fairly shallow ones ; - )</span></font></p>
</div>
<div>
<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'> </span></font></p>
</div>
<div>
<p class=3DMsoNormal><font size=3D2 color=3Dblue face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:blue'>I think I understand what you =
are
saying and raise two proposals - though the implications need to be =
clearer..</span></font></p>
</div>
<div>
<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'> </span></font></p>
</div>
<div>
<p class=3DMsoNormal><font size=3D2 color=3Dblue face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:blue'>Your experiences seem not to =
involve full
exchange file scope as defined by the Dexs, since you are dealing with =
legacy
data and more ad-hoc query-related data extraction which does not =
require a
fully instantiated Step file acc. to one or other Dexs. However, for =
longterm
data archiving I suspect that this may be required.</span></font></p>
</div>
<div>
<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'> </span></font></p>
</div>
<div>
<p class=3DMsoNormal><font size=3D2 color=3Dblue face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:blue'>The suggestion is that there needs =
to be
(or is already) a generic set of capabilities that may then be extended =
with
standardized terms for common usage within a domain. These terms of =
common
usage I would suggest are those defined by the user community (such as =
MoD,
Nato, or other large organization) and are represented as reference =
data. </span></font></p>
</div>
<div>
<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'> </span></font></p>
</div>
<div>
<p class=3DMsoNormal><font size=3D2 color=3Dblue face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:blue'>This means that the capabilities
can/should only provide example reference data until the particular =
exchange
community has adopted a specific set/collection of reference data for =
that
industry/domain. Once adopted, the reference data can be used to =
complete the
schema in terms of the acceptable values for attributes such as =
identifiers and
relevant rules can be written to enforce these. This version of the
capability(s) is what you are saying needs/could be =
standardized.</span></font></p>
</div>
<div>
<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'> </span></font></p>
</div>
<div>
<p class=3DMsoNormal><font size=3D2 color=3Dblue face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:blue'>In other guises, this is close =
to the
subject of a set of implementor's agreements, but begins at a =
little
higher level.</span></font></p>
</div>
<div>
<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'> </span></font></p>
</div>
<div>
<p class=3DMsoNormal><font size=3D2 color=3Dblue face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:blue'>From this view I can see that pre =
&
post processor guidence may be a little premature and would need to be =
careful
not to include items that are effectively example reference data items. =
</span></font></p>
</div>
<div>
<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'> </span></font></p>
</div>
<div>
<p class=3DMsoNormal><font size=3D2 color=3Dblue face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:blue'>However, some of the sections =
on
this subject are indeed more generic & for example, under the =
capability
representing_assembly_structure the first pre-processor statement =
reads...</span></font></p>
</div>
<div>
<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'> </span></font></p>
</div>
<address style=3D'margin-left:36.0pt'><i><font size=3D2 color=3Dblue =
face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial;color:blue'>No cyclic
part_view_definiton structures may be defined. The value of the
identification_assignment.identifier (for PDM Schema this is the local =
id
attribute) must be unique in combination with the same relating assembly =
and
related component definitions. For PLCS this implies that the identifier =
for
each part_view_definition, part_version and part must be unique within =
the
assembly. It is generally recommended that only subtypes of
assembly_component_relationship be instantiated. It is not necessary to
instantiate the optional relation_type, location_indicator or quantity =
attributes
for an instance of next_assembly_usage in the context of a basic parts =
list. If
information on the assembly type is to be represented, then this =
additional
information should be represented using the =
view_definition_context.description
attribute. This information is linked through the
part_view_definition.additional_contexts attribute inherited from
product_view_definition (leaving the application_domain and =
life_cycle_stage
attributes empty). Examples of such type information are 'functional =
assembly',
'manufacturing assembly', and 'design =
assembly'.....</span></font></i></address>
<div>
<p class=3DMsoNormal><font size=3D2 color=3Dblue face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:blue'>.... I think most is still =
applicable,
except for those examples which might be different depending upon =
usage.</span></font></p>
</div>
<div>
<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'> </span></font></p>
</div>
<div>
<p class=3DMsoNormal><u><font size=3D2 color=3Dblue face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial;color:blue'>Prop =
1:</span></font></u><font
size=3D2 color=3Dblue face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;
color:blue'> This information, however, is now captured under the CVS
versioning so removing these sections for now, is not a problem and may =
aid
consistency across the capabilities. I could agree to putting this on =
the
"back-burner" for now so that the complexity issue can be =
ironed-out
first; though I suspect we may need to come back to it at some =
point.</span></font></p>
</div>
<div>
<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'> </span></font></p>
</div>
<div>
<p class=3DMsoNormal><font size=3D2 color=3Dblue face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:blue'>The other thing that seems to come =
out of
this (for me at least) is a question on whether the capabilities should
document any of the items referenced from a select type. In some =
capabilities I
see examples that are specific to the Dex within which it is primarily =
to be
used, but when I look at Dex 1, I realize that the example (entity used) =
in the
capability is not actually present (e.g. out of scope). Likewise, I =
could have
done the same in generating capabilities under Dex1 & for example, =
in
assigning_identifiers I may have only used the entity "Part" =
when
showing how the identification_assignment works, though this may not be =
present
in al Dexs. </span></font></p>
</div>
<div>
<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'> </span></font></p>
</div>
<div>
<p class=3DMsoNormal><u><font size=3D2 color=3Dblue face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial;color:blue'>Prop 2: =
</span></font></u><font
size=3D2 color=3Dblue face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;
color:blue'>We (modellers) need to decide if we are to document the =
contents of
these select types or not. I have actually documented ALL PLCS entities
available from the identification_item select type, though only chosen =
one for
the example. I have also added notes to state that this list may change
depending upon the usage of the capability (i.e. in which Dex) since the
contents of the list may be pruned according to the scope. However, =
someone
looking at the capability, from a *re-use point of view*, would be able =
to see
which entities are referable from the material and to make decisions =
accordingly
for the Dex they are planning. I would therefore, suggest this as a =
default
position when documenting the capabilties, (though I am still open to
discussion)!</span></font></p>
</div>
<div>
<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'> </span></font></p>
</div>
<div>
<p class=3DMsoNormal><font size=3D2 color=3Dblue face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:blue'>Kind regards,</span></font></p>
</div>
<div>
<p class=3DMsoNormal><font size=3D2 color=3Dblue face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:blue'>Tim</span></font></p>
</div>
<blockquote style=3D'margin-top:5.0pt;margin-bottom:5.0pt'>
<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><font size=3D2 =
face=3DTahoma><span
style=3D'font-size:10.0pt;font-family:Tahoma'>-----Original =
Message-----<br>
<b><span style=3D'font-weight:bold'>From:</span></b> =
Leif.Tonning@dnv.com [mailto:Leif.Tonning@dnv.com]<br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> 30 April 2004 =
07:53<br>
<b><span style=3D'font-weight:bold'>To:</span></b> =
timturner11@bellsouth.net<br>
<b><span style=3D'font-weight:bold'>Cc:</span></b> =
rob.bodington@eurostep.com;
Trine.Hansen@dnv.com; Jochen.Haenisch@epmtech.jotne.com<br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> RE: Pre-post =
processor
info</span></font></p>
<div>
<p class=3DMsoNormal><font size=3D2 color=3Dblue face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:blue'>I get some of the =
picture.</span></font></p>
</div>
<div>
<p class=3DMsoNormal><font size=3D2 color=3Dblue face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:blue'>As you are aware, we have had some
uncertainty as to wether the current PLCS capabilities and DEX'es can =
easily be
reused in our pilots, and we have communicated our needs and ideas back =
to Rob
and others.</span></font></p>
</div>
<div>
<p class=3DMsoNormal><font size=3D2 color=3Dblue face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:blue'>In this work we have not met the =
problem
you refer to with documentation of capabilities and the related =
DTD.</span></font></p>
</div>
<div>
<p class=3DMsoNormal><font size=3D2 color=3Dblue face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:blue'>I appreciate that the PDM schema =
rightly
calls on pre and postprocessors. However, we have not met the need for =
these in
our work. Why?</span></font></p>
</div>
<div>
<p class=3DMsoNormal><font size=3D2 color=3Dblue face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:blue'>As in PLCS, we develop generic
capabilities, and these are to a large extent of the same type. Then we
instantiate the capabilities to hold real data. Currently, thes =
instantiated
data are legacy type, not subject to standardisation, but they should =
(using
reference data) be identical to stable logistics business data as found =
e.g. in
DefStan 00-60. Then the instantiated caps (possibly grouped inside a =
generic
cap) should be standardised.</span></font></p>
</div>
<div>
<p class=3DMsoNormal><font size=3D2 color=3Dblue face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:blue'>To be able to use caps (the =
instantiated
ones), instantiation diagrams (also candidates for standardisation when
populated with reference data) are developed. These represent =
business
concepts where the caps are used and reused.</span></font></p>
</div>
<div>
<p class=3DMsoNormal><font size=3D2 color=3Dblue face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:blue'>To populate a PLCS database, we =
have not
met needs for postprocessing other than as defined in the instantiations =
(the
mapping diagrams). This, however, does not mean that postprocessing is =
not an
added value, but the need should be carefully assessed before another =
level of
complexity is added to PLCS.</span></font></p>
</div>
<div>
<p class=3DMsoNormal><font size=3D2 color=3Dblue face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:blue'>To extract data from the PLCS =
database,
query is used. Again no other need for preprocessing, and again, =
carefully
assess the need, complexity and cost benefit..</span></font></p>
</div>
<div>
<p class=3DMsoNormal><font size=3D2 color=3Dblue face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:blue'>We believe that the exchange =
specification
for import and export technically is the same, but there may be =
other
reasons why this is not so.</span></font></p>
</div>
<div>
<p class=3DMsoNormal><font size=3D2 color=3Dblue face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:blue'>Also, provided pre and post =
processing is
introduced, care should be taken to distinguish between the generic part =
and
the instantiatied part. I see the generic parts only as aids to develop =
the
instantiated parts. When the logistics domain is fully populated with
instantiated reference data, these should be used by all, and the need =
for the
generic capabilities disappear. Mapping legacy data to PLCS will then be =
done
using the instantiation diagrams and the instantiated
capabilities. Databases and data exchanges will hold instantiated =
data
(legacy or the reference data substitution for the legacy data), not =
generic
capabilities.</span></font></p>
</div>
<div>
<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'> </span></font></p>
</div>
<div>
<p class=3DMsoNormal><font size=3D2 color=3Dblue face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:blue'>Knowing well I am operating in =
troubled
water, I still hope this is to help and not to confuse. If the latter, =
forget
the mail.</span></font></p>
</div>
<div>
<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'> </span></font></p>
</div>
<div>
<p class=3DMsoNormal><font size=3D2 color=3Dblue face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:blue'>Best regards</span></font></p>
</div>
<div>
<p class=3DMsoNormal><font size=3D2 color=3Dblue face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:blue'>Leif Tonning</span></font></p>
</div>
<div>
<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'> </span></font></p>
</div>
<blockquote =
style=3D'margin-top:5.0pt;margin-right:0cm;margin-bottom:5.0pt'>
<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><font size=3D2 =
face=3DTahoma><span
lang=3DEN-US style=3D'font-size:10.0pt;font-family:Tahoma'>-----Original
Message-----<br>
<b><span style=3D'font-weight:bold'>From:</span></b> Tim Turner =
[mailto:timturner11@bellsouth.net]
<br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> 29. april 2004 =
20:50<br>
<b><span style=3D'font-weight:bold'>To:</span></b> Tonning, Leif<br>
<b><span style=3D'font-weight:bold'>Cc:</span></b> =
rob.bodington@eurostep.com<br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> RE: Pre-post =
processor
info</span></font></p>
<div>
<p class=3DMsoNormal><font size=3D2 color=3Dblue face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:blue'>Oh um, sorry!</span></font></p>
</div>
<div>
<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'> </span></font></p>
</div>
<div>
<p class=3DMsoNormal><font size=3D2 color=3Dblue face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:blue'>Well a lot of the early =
capabilities had
sections on pre & post processor guidence in the main body, =
underneath the
descriptions of the entity attributes being documented. For =
example, under
representing assembly structures & BOM there is a section on =
</span></font><a
name=3DPostprocessorRecommendations><strong><b><font color=3Dblack
face=3D"Times New Roman"><span style=3D'color:black'>Postprocessor =
Recommendations</span></font></b></strong></a><font
size=3D2 color=3Dblue face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;
color:blue'>. However, these sections need to be moved to the usage =
area
(I.e. in amongst the entity definitions), but I cannot copy the section =
to that
part as the dtd seems not to allow it. I need to see some sort of =
example on
how this should be done, or for the dtd to change to enable a simpler =
format.</span></font></p>
</div>
<div>
<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'> </span></font></p>
</div>
<div>
<p class=3DMsoNormal><font size=3D2 color=3Dblue face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:blue'>I believe that I can just delete =
the
attribute sections I have manually provided since these are already =
available
in the usage area.</span></font></p>
</div>
<div>
<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'> </span></font></p>
</div>
<div>
<p class=3DMsoNormal><font size=3D2 color=3Dblue face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:blue'>Regards,</span></font></p>
</div>
<div>
<p class=3DMsoNormal><font size=3D2 color=3Dblue face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:blue'>Tim</span></font></p>
</div>
<div>
<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'> </span></font></p>
</div>
<div>
<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'> </span></font></p>
</div>
<blockquote style=3D'margin-top:5.0pt;margin-bottom:5.0pt'>
<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><font size=3D2 =
face=3DTahoma><span
style=3D'font-size:10.0pt;font-family:Tahoma'>-----Original =
Message-----<br>
<b><span style=3D'font-weight:bold'>From:</span></b> =
Leif.Tonning@dnv.com
[mailto:Leif.Tonning@dnv.com]<br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> 29 April 2004 =
02:46<br>
<b><span style=3D'font-weight:bold'>To:</span></b> =
timturner11@bellsouth.net<br>
<b><span style=3D'font-weight:bold'>Cc:</span></b> =
rob.bodington@eurostep.com<br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> RE: Pre-post =
processor
info</span></font></p>
<p><font size=3D2 color=3Dblue face=3DArial><span =
style=3D'font-size:10.0pt;font-family:
Arial;color:blue'><!-- Converted from text/rtf format -->Hi, =
Tim</span></font> <br>
<font size=3D2 color=3Dblue face=3DArial><span =
style=3D'font-size:10.0pt;font-family:
Arial;color:blue'>Sorry, I'm not on the net. Probably I have missed some
communication and do not understand what you are asking. =
</span></font><br>
<font size=3D2 color=3Dblue face=3DArial><span =
style=3D'font-size:10.0pt;font-family:
Arial;color:blue'>I will do my best to give you an answer, but need =
better to
understand the issue</span></font> </p>
<p><font size=3D2 color=3Dblue face=3DArial><span =
style=3D'font-size:10.0pt;font-family:
Arial;color:blue'>Leif t</span></font> </p>
<p style=3D'margin-left:36.0pt'><font size=3D3 face=3D"Times New =
Roman"><span
style=3D'font-size:12.0pt'> </span></font><font size=3D1 =
face=3DTahoma><span
style=3D'font-size:7.5pt;font-family:Tahoma'>-----Original =
Message-----</span></font>
<br>
<b><font size=3D1 face=3DTahoma><span =
style=3D'font-size:7.5pt;font-family:Tahoma;
font-weight:bold'>From: </span></font></b> <font size=3D1 =
face=3DTahoma><span
style=3D'font-size:7.5pt;font-family:Tahoma'>Tim Turner =
[</span></font><a
href=3D"mailto:timturner11@bellsouth.net";><font size=3D1 =
face=3DTahoma><span
style=3D'font-size:7.5pt;font-family:Tahoma'>mailto:timturner11@bellsouth=
.net</span></font></a><font
size=3D1 face=3DTahoma><span =
style=3D'font-size:7.5pt;font-family:Tahoma'>] </span></font><br>
<b><font size=3D1 face=3DTahoma><span =
style=3D'font-size:7.5pt;font-family:Tahoma;
font-weight:bold'>Sent: </span></font></b> <font size=3D1 =
face=3DTahoma><span
style=3D'font-size:7.5pt;font-family:Tahoma'>28. april 2004 =
20:32</span></font> <br>
<b><font size=3D1 face=3DTahoma><span =
style=3D'font-size:7.5pt;font-family:Tahoma;
font-weight:bold'>To: </span></font></b> <font =
size=3D1
face=3DTahoma><span style=3D'font-size:7.5pt;font-family:Tahoma'>Rob =
Bodington
(E-mail); Tonning, Leif</span></font> <br>
<b><font size=3D1 face=3DTahoma><span =
style=3D'font-size:7.5pt;font-family:Tahoma;
font-weight:bold'>Subject: </spa=
n></font></b>
<font size=3D1 face=3DTahoma><span =
style=3D'font-size:7.5pt;font-family:Tahoma'>Pre-post
processor info</span></font> </p>
<p style=3D'margin-left:36.0pt'><font size=3D2 face=3DArial><span =
lang=3DEN-US
style=3D'font-size:10.0pt;font-family:Arial'>Guys,</span></font><span =
lang=3DEN-US>
</span></p>
<p style=3D'margin-left:36.0pt'><font size=3D2 face=3DArial><span =
lang=3DEN-US
style=3D'font-size:10.0pt;font-family:Arial'>I'm trying to address the =
issue of
moving much of this information into the usage section, but I need an =
example
where this has been done that I can follow.</span></font></p>
<p style=3D'margin-left:36.0pt'><font size=3D2 face=3DArial><span =
lang=3DEN-US
style=3D'font-size:10.0pt;font-family:Arial'>Do you have anything I =
could look
at?</span></font><span lang=3DEN-US> </span></p>
<p style=3D'margin-left:36.0pt'><font size=3D2 face=3DArial><span =
lang=3DEN-US
style=3D'font-size:10.0pt;font-family:Arial'>Cheers,</span></font> <br>
<font size=3D2 face=3DArial><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:
Arial'>Tim</span></font><span lang=3DEN-US> </span></p>
<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><br>
**************************************************************<br>
Neither the confidentiality nor the integrity of this message can be =
guaranteed
following transmission on the Internet. <br>
All messages sent to a DNV email addressee are swept by Sybari Antigen =
for the
presence of computer viruses. <br>
DNV acknowledges that SPAM email represents a potential security risk, =
and DNVs
filters to block unwanted emails are therefore continuously adjusted. =
DNV has
disabled "out of office" replies to the Internet <br>
************************************************************** =
</span></font></p>
</blockquote>
</blockquote>
<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><br>
**************************************************************<br>
Neither the confidentiality nor the integrity of this message can be =
guaranteed
following transmission on the Internet. <br>
All messages sent to a DNV email addressee are swept by Sybari Antigen =
for the
presence of computer viruses. <br>
DNV acknowledges that SPAM email represents a potential security risk, =
and DNVs
filters to block unwanted emails are therefore continuously adjusted. =
DNV has
disabled "out of office" replies to the Internet <br>
************************************************************** =
</span></font></p>
</blockquote>
</blockquote>
</div>
</div>
</body>
</html>
<BR>
<BR>
<P><B><FONT SIZE=3D1 FACE=3D"Arial">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 </FONT></B></P>
<BR>
<BR>
------=_NextPart_000_0059_01C431BA.3F31E890--
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]