[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [no subject]
Having read the current copy on STEPMOD (module.xml (Date: 2004/07/12 07:25:16 Revision: 1.24 ) arm.xm (Date: 2004/07/02 09:05:15 Revision: 1.7 ) mim.x (Date: 2004/07/04 14:17:03 Revision: 1.13 ) it needs some editing in the Introduction, it has duplicated paragraphs "This part of ISO 10303 specifies an application module for the representation of a central, common subset of the data being managed within a product data management (PDM) system. It represents the intersection of requirements and data structures from a range of application protocols, all generally within the domains of design and development of discrete electro/mechanical parts and assemblies. This part of ISO 10303 is not a specification for the functionality required for the complete scope of all PDM system functionality - i.e., it is not the union, but the intersection, of functionality present in the relevant set of application protocols. Some functionality important for complete PDM functionality is not represented in this application module, but is covered in other application protocols. By definition, a PDM system is something that manages data about products. At the central core of PDM information is product identification. A product in ISO 10303 represents the concept of a general managed item within a PDM system. In this part of ISO 10303, the general product concept may be interpreted as either a part or a document. Thus parts and documents are managed in a consistent fashion. This part of ISO 10303 is not a specification for the functionality required for the complete scope of all PDM system functionality; that is, it is not the union, but the intersection, of functionality present in the relevant set of application protocols. Some functionality important for complete PDM functionality is not represented in this application module, but is covered in other application protocols. By definition, a PDM system is something that manages data about products. At the central core of PDM information is product identification. A product in ISO 10303 represents the concept of a general managed item within a PDM system. In this part of ISO 10303, the general product concept may be interpreted as either a part or a document. Thus parts and documents are managed in a consistent fashion. Also central to the functionality of many PDM systems is identification of external files (both digital and physical), their relationship to managed documents, and the association of such files with core product identification. Classification of products is important in a PDM system for information classification and retrieval. This part of ISO 10303 supports the basic type distinction between products that are parts and those that are documents and employs product classification consistently for parts and documents. Product properties are integrally related to the definition of an identified product, and so are also included in the central core PDM information. Various general authorization and organizational data that are related to core product identification play an important role in PDM systems and this part of ISO 10303 supports a number of organizational and management constructs relating to product authorization. Product structures are the principle relationships that define assemblies and product configurations. This module details part and document structures and represents configuration identification and effectivity information related to those structures. This part of ISO 10303 supports the documentation of requests and corresponding orders for engineering action in support of change management and representations of contract and project identification." The words do tend to lean in having the time_interval_relationship and event occurrence relationship contained within regards Gordon -----Original Message----- From: Hendrix, Thomas E [mailto:thomas.e.hendrix@boeing.com] Sent: 13 October 2004 00:30 To: plcs-dex@lists.oasis-open.org Subject: [plcs-dex] Consensus on relationships Dear all: There has been a request to remove time_interval_relationship and event_occurrence_relationship from 1231, because they are not in AP214 and hence not in PDM Schema Would this be a problem for AP239? Regards, Tom Thomas E. Hendrix Phone: 206-544-5276 thomas.e.hendrix@boeing.com 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 ------_=_NextPart_001_01C4B0F0.02548670 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> <HTML> <HEAD> <META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; = charset=3Diso-8859-1"> <META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version = 5.5.2653.12"> <TITLE>RE: [plcs-dex] Consensus on relationships</TITLE> </HEAD> <BODY> <P><FONT SIZE=3D2 FACE=3D"Arial">Hi Tom,</FONT> <BR><FONT SIZE=3D2 FACE=3D"Arial">What is the relevance to this request = on 1231 Product data management from 214</FONT> <BR><FONT SIZE=3D2 FACE=3D"Arial">From a business sense I would have = thought having those attributes contained within 1231 was = necessary.</FONT> </P> <P><FONT SIZE=3D2 FACE=3D"Arial">Having read the current copy on = STEPMOD (module.xml (Date: 2004/07/12 07:25:16 Revision: 1.24 ) arm.xm = (Date: 2004/07/02 09:05:15 Revision: 1.7 ) mim.x (Date: 2004/07/04 = 14:17:03 Revision: 1.13 ) it needs some editing in the Introduction, it = has duplicated paragraphs</FONT></P> <P><FONT SIZE=3D2 FACE=3D"Arial"> "This part of ISO 10303 = specifies an application module for the representation of a central, = common subset of the data being managed within a product data = management (PDM) system. It represents the intersection of requirements = and data structures from a range of application protocols, all = generally within the domains of design and development of discrete = electro/mechanical parts and assemblies. </FONT></P> <P><B><I><FONT COLOR=3D"#FF0000" SIZE=3D2 FACE=3D"Arial">This part of = ISO 10303 is not a specification for the functionality required for the = complete scope of all PDM system functionality - i.e., it is not the = union, but the intersection, of functionality present in the relevant = set of application protocols. Some functionality important for complete = PDM functionality is not represented in this application module, but is = covered in other application protocols. </FONT></I></B></P> <P><FONT SIZE=3D2 FACE=3D"Arial">By definition, a PDM system is = something that manages data about products. At the central core of PDM = information is product identification. A product in ISO 10303 = represents the concept of a general managed item within a PDM system. = In this part of ISO 10303, the general product concept may be = interpreted as either a part or a document. Thus parts and documents = are managed in a consistent fashion. </FONT></P> <P><B><I><FONT COLOR=3D"#FF0000" SIZE=3D2 FACE=3D"Arial">This part of = ISO 10303 is not a specification for the functionality required for the = complete scope of all PDM system functionality; that is, it is not the = union, but the intersection, of functionality present in the relevant = set of application protocols. Some functionality important for complete = PDM functionality is not represented in this application module, but is = covered in other application protocols. </FONT></I></B></P> <P><FONT SIZE=3D2 FACE=3D"Arial">By definition, a PDM system is = something that manages data about products. At the central core of PDM = information is product identification. A product in ISO 10303 = represents the concept of a general managed item within a PDM system. = In this part of ISO 10303, the general product concept may be = interpreted as either a part or a document. Thus parts and documents = are managed in a consistent fashion. </FONT></P> <P><FONT SIZE=3D2 FACE=3D"Arial">Also central to the functionality of = many PDM systems is identification of external files (both digital and = physical), their relationship to managed documents, and the association = of such files with core product identification. </FONT></P> <P><FONT SIZE=3D2 FACE=3D"Arial">Classification of products is = important in a PDM system for information classification and retrieval. = This part of ISO 10303 supports the basic type distinction between = products that are parts and those that are documents and employs = product classification consistently for parts and documents. = </FONT></P> <P><FONT SIZE=3D2 FACE=3D"Arial">Product properties are integrally = related to the definition of an identified product, and so are also = included in the central core PDM information. </FONT></P> <P><FONT SIZE=3D2 FACE=3D"Arial">Various general authorization and = organizational data that are related to core product identification = play an important role in PDM systems and this part of ISO 10303 = supports a number of organizational and management constructs relating = to product authorization. </FONT></P> <P><FONT SIZE=3D2 FACE=3D"Arial">Product structures are the principle = relationships that define assemblies and product configurations. This = module details part and document structures and represents = configuration identification and effectivity information related to = those structures. </FONT></P> <P><FONT SIZE=3D2 FACE=3D"Arial">This part of ISO 10303 supports the = documentation of requests and corresponding orders for engineering = action in support of change management and representations of contract = and project identification.</FONT><FONT SIZE=3D2 = FACE=3D"Arial">"</FONT></P> <P><FONT SIZE=3D2 FACE=3D"Arial">The words do tend to lean in having = the time_interval_relationship and event occurrence relationship = contained within</FONT><FONT SIZE=3D2 FACE=3D"Arial"> </FONT> </P> <P><FONT SIZE=3D2 FACE=3D"Arial">regards</FONT> <BR><FONT SIZE=3D2 FACE=3D"Arial">Gordon</FONT> </P> <P><FONT SIZE=3D2 FACE=3D"Arial">-----Original Message-----</FONT> <BR><FONT SIZE=3D2 FACE=3D"Arial">From: Hendrix, Thomas E [<A = HREF=3D"mailto:thomas.e.hendrix@boeing.com";>mailto:thomas.e.hendrix@boei= ng.com</A>]</FONT> <BR><FONT SIZE=3D2 FACE=3D"Arial">Sent: 13 October 2004 00:30</FONT> <BR><FONT SIZE=3D2 FACE=3D"Arial">To: = plcs-dex@lists.oasis-open.org</FONT> <BR><FONT SIZE=3D2 FACE=3D"Arial">Subject: [plcs-dex] Consensus on = relationships</FONT> </P> <BR> <P><FONT SIZE=3D2 FACE=3D"Arial">Dear all:</FONT> </P> <P><FONT SIZE=3D2 FACE=3D"Arial">There has been a request to remove = time_interval_relationship and</FONT> <BR><FONT SIZE=3D2 FACE=3D"Arial">event_occurrence_relationship from = 1231, because they are not in AP214</FONT> <BR><FONT SIZE=3D2 FACE=3D"Arial">and hence not in PDM Schema</FONT> </P> <P><FONT SIZE=3D2 FACE=3D"Arial">Would this be a problem for = AP239?</FONT> </P> <BR> <BR> <P><FONT SIZE=3D2 FACE=3D"Arial">Regards,</FONT> </P> <P><FONT SIZE=3D2 FACE=3D"Arial">Tom</FONT> </P> <P><FONT SIZE=3D2 FACE=3D"Arial">Thomas E. Hendrix</FONT> <BR><FONT SIZE=3D2 FACE=3D"Arial">Phone: 206-544-5276</FONT> <BR><FONT SIZE=3D2 FACE=3D"Arial">thomas.e.hendrix@boeing.com</FONT> </P> <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> </BODY> </HTML> ------_=_NextPart_001_01C4B0F0.02548670--
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]