<?xml version="1.0"?>
<?xml-stylesheet type="text/css" href="http://www.wikistep.org/skins/common/feed.css?270"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
		<id>http://www.wikistep.org/index.php?title=Special:NewPages&amp;feed=atom&amp;hideliu=&amp;hidepatrolled=&amp;hidebots=&amp;hideredirs=1&amp;limit=50&amp;namespace=0</id>
		<title>WikiSTEP - New pages [en]</title>
		<link rel="self" type="application/atom+xml" href="http://www.wikistep.org/index.php?title=Special:NewPages&amp;feed=atom&amp;hideliu=&amp;hidepatrolled=&amp;hidebots=&amp;hideredirs=1&amp;limit=50&amp;namespace=0"/>
		<link rel="alternate" type="text/html" href="http://www.wikistep.org/index.php/Special:NewPages"/>
		<updated>2012-05-18T20:11:33Z</updated>
		<subtitle>From WikiSTEP</subtitle>
		<generator>MediaWiki 1.16.5</generator>

	<entry>
		<id>http://www.wikistep.org/index.php/PDTec_instance_explorer_link</id>
		<title>PDTec instance explorer link</title>
		<link rel="alternate" type="text/html" href="http://www.wikistep.org/index.php/PDTec_instance_explorer_link"/>
				<updated>2012-03-26T19:37:04Z</updated>
		
		<summary type="html">&lt;p&gt;Tom Thurman: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;http://www.pdtec.de/support/download_instance_explorer.aspx&lt;br /&gt;
The file is &amp;quot;PDTec Instance Explorer Setup&amp;quot; version 3.1.17.&lt;/div&gt;</summary>
		<author><name>Tom Thurman</name></author>	</entry>

	<entry>
		<id>http://www.wikistep.org/index.php/PDES-181</id>
		<title>PDES-181</title>
		<link rel="alternate" type="text/html" href="http://www.wikistep.org/index.php/PDES-181"/>
				<updated>2012-02-13T00:45:55Z</updated>
		
		<summary type="html">&lt;p&gt;Tom Thurman: Created page with &amp;quot;*  PDES-181.stp&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;*  [[Media:PDES-181.stp|PDES-181.stp]]&lt;/div&gt;</summary>
		<author><name>Tom Thurman</name></author>	</entry>

	<entry>
		<id>http://www.wikistep.org/index.php/PMI</id>
		<title>PMI</title>
		<link rel="alternate" type="text/html" href="http://www.wikistep.org/index.php/PMI"/>
				<updated>2010-04-20T16:09:31Z</updated>
		
		<summary type="html">&lt;p&gt;Lothar Klein: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;This page is under construction !&lt;br /&gt;
&lt;br /&gt;
Product manufacturing information, also abbreviated PMI, conveys non-geometric attributes in 3D computer-aided design (CAD) and Collaborative Product Development systems necessary for manufacturing product components or subsystems. PMI may include geometric dimensions and tolerances, 3D annotation (text) and dimensions, surface finish, and material specifications. CAD application literature may also refer to PMI synonymously with Geometric Dimensions and Tolerances (GD&amp;amp;T) or Functional Tolerancing and Annotation (FT&amp;amp;A).&lt;br /&gt;
See corresponding information on Wikipedia:&lt;br /&gt;
* http://en.wikipedia.org/wiki/Product_manufacturing_information &lt;br /&gt;
* http://en.wikipedia.org/wiki/GD%26T&lt;br /&gt;
&lt;br /&gt;
The information provided here is supported by AP203ed2 and to a big degree also by AP214.&lt;br /&gt;
&lt;br /&gt;
== Geometry ==&lt;br /&gt;
Nonetheless that PMI is focusing on non-geometric information, geometric representations are required to link to. &lt;br /&gt;
&lt;br /&gt;
=== Geometric product model ===&lt;br /&gt;
The geometric model of a product is represented by a shape_representation. STEP offers some 20 different specializations of shape_representation, but for the purposes of GD&amp;amp;T you should use '''advanced boundary representation''' only, see AM 1541 a wrapper for AIC 514. For the MIM/IR implementation we have to refer to these entities:&lt;br /&gt;
* advanced_brep_shape_representation, a subtype of shape_representation that requires a 3D coordinate system, established by a geometric_representation_context&lt;br /&gt;
* advanced_face, a topological bounded surface&lt;br /&gt;
* oriented_edge, a topological bounded curve&lt;br /&gt;
* vertex_point, the topological representation of a cartesian_point&lt;br /&gt;
* axis2_placement_3d that is used to define local coordinate systems within the 3D geometric_representation_context &lt;br /&gt;
&lt;br /&gt;
=== Supplemental geometry ===&lt;br /&gt;
Supplemental or constructive geometry are all the geometric elements that are needed to define the shape of a product, but that are not themselves part of the shape of a product. AM 1131 &amp;quot;Construction geometry&amp;quot; defines constructive_geometry_representation that is the collector of all these geometric elements. The valid entities are:&lt;br /&gt;
* placement, either axis2_placement_2d or axis2_placement_3d&lt;br /&gt;
* curve, bounded or unbounded&lt;br /&gt;
* edge&lt;br /&gt;
* face&lt;br /&gt;
* point, in most cases cartesian_point&lt;br /&gt;
* surface&lt;br /&gt;
* face_surface  &lt;br /&gt;
* vertex_point&lt;br /&gt;
A constructive_geometry_representation is linked to the corresponding advanced_brep_shape_representation by a constructive_geometry_representation_relationship. Both representations must share the same 3D geometric_representation_context. &lt;br /&gt;
&lt;br /&gt;
=== Draughting model ===&lt;br /&gt;
xxx&lt;br /&gt;
&lt;br /&gt;
A draughting_model includes the shape_representations and constructive_geometry_representation by a mapped_item with an identity transformation. These representations must share the same 3D geometric_representation_context&lt;br /&gt;
&lt;br /&gt;
=== Presentation and drawings ===&lt;br /&gt;
&lt;br /&gt;
== Non-geometrical information ==&lt;br /&gt;
=== Shape abstraction ===&lt;br /&gt;
Throughout STEP the term '''shape''' is used to refer to geometric information without having any detailed geometric information.&lt;br /&gt;
* product_definition_shape represents the shape of a product. A shape_definition_representation links it to the corresponding geometric model&lt;br /&gt;
* shape_aspect that identifies a portion of the shape of a product. The attributes product_definitional defines on whether the shape_aspect is part of the item_shape.&lt;br /&gt;
* composite_shape_aspect, a subtype of shape_aspect that represents a collection of other shape_aspects&lt;br /&gt;
* derived_shape_aspect, a subtype of shape_aspect that is derived from one or more other shape_aspects. There are further specializations for apex, centre_of_symmetry, geometric_alignment, geometric_intersection, parallel_offset, perpendicular_to, extension and tangent&lt;br /&gt;
&lt;br /&gt;
=== Dimensional tolerances ===&lt;br /&gt;
&lt;br /&gt;
=== Geometric tolerances ===&lt;br /&gt;
&lt;br /&gt;
=== Default tolerances ===&lt;br /&gt;
&lt;br /&gt;
=== Surface conditions ===&lt;br /&gt;
&lt;br /&gt;
=== Chemical substance ===&lt;br /&gt;
&lt;br /&gt;
=== Material properties ===&lt;br /&gt;
&lt;br /&gt;
=== Composites ===&lt;/div&gt;</summary>
		<author><name>Lothar Klein</name></author>	</entry>

	<entry>
		<id>http://www.wikistep.org/index.php/Integration_of_developer%E2%80%99s_API_(JavaDoc)_documentation_and_HTML_standards_documentation_for_AP210_query_library</id>
		<title>Integration of developer’s API (JavaDoc) documentation and HTML standards documentation for AP210 query library</title>
		<link rel="alternate" type="text/html" href="http://www.wikistep.org/index.php/Integration_of_developer%E2%80%99s_API_(JavaDoc)_documentation_and_HTML_standards_documentation_for_AP210_query_library"/>
				<updated>2010-04-02T21:48:14Z</updated>
		
		<summary type="html">&lt;p&gt;Tom Thurman: New page: Integration of developer’s API (JavaDoc) documentation and HTML standards documentation for AP210 query library  In order to facilitate development of AP210 applications, the Java progra...&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Integration of developer’s API (JavaDoc) documentation and HTML standards documentation for AP210 query library&lt;br /&gt;
&lt;br /&gt;
In order to facilitate development of AP210 applications, the Java programmer’s documentation of the&lt;br /&gt;
AP210 query library and JSDAI has been integrated with the HTML documentation of the AP210&lt;br /&gt;
standard. &lt;br /&gt;
Effective use of the AP210 query library requires repeated reference to the relevant AP210&lt;br /&gt;
ARM application objects and corresponding MIM entities. &lt;br /&gt;
A mechanism for enhancing the existing Java&lt;br /&gt;
API documentation through linking to the corresponding AP210 HTML referenced entities at the ARM&lt;br /&gt;
and MIM level has been developed. &lt;br /&gt;
Additionally, graphical entity instance diagrams have been extracted&lt;br /&gt;
and linked to the corresponding query methods to facilitate visual interpretation of the relationships&lt;br /&gt;
between the relevant entities. &lt;br /&gt;
Finally, the documentation was enhanced with additional detail and&lt;br /&gt;
numerous (linked) references to applicable ARM application objects and MIM entities.&lt;br /&gt;
The most recent updates to the query library (delivered 12/3/09) included significantly expanded queries&lt;br /&gt;
for extraction of PCA/PCB data, new queries for the purpose of extracting data from AP210 package&lt;br /&gt;
models, and queries to aid end-users in the extraction and interpretation of parametric data related to&lt;br /&gt;
products and packages. The Java source code resides in the package com.sfm.ap210.jsdai. &lt;br /&gt;
The current query library consists of approximately 100 methods contained in the MIMqueries,&lt;br /&gt;
MIMpackageQueries, and MIMparamQueries interfaces as well as the 100+ supporting lowerlevel&lt;br /&gt;
operation methods (MIMops). &lt;br /&gt;
The queries have been implemented in Java using a library known as&lt;br /&gt;
the JSDAI developed by LKSoftWare GmbH. LKSoft licenses the JSDAI under both commercial and&lt;br /&gt;
open-source terms1. &lt;br /&gt;
An algorithm for methodical traversal of the AP 210 model has also been provided in&lt;br /&gt;
order to demonstrate the successful integration of these queries and the ability to efficiently extract the&lt;br /&gt;
relevant data from an AP210 model. &lt;br /&gt;
Graphical and pseudo-code documentation of the queries has been&lt;br /&gt;
provided, as well as the Java source code for the implemented queries and supporting low-level&lt;br /&gt;
operations, as well as the traversal algorithm.&lt;br /&gt;
Javadoc is a tool from Sun Microsystems for generating API documentation in HTML format, and the&lt;br /&gt;
most common method for generating API documentation from Java source code2. &lt;br /&gt;
The Javadoc tool supports development of custom tags through Java classes that implement the Taglet3 interface. &lt;br /&gt;
To develop the integrated documentation, several custom tags were developed that enabled efficient&lt;br /&gt;
annotation of the Java source code to drive the generation of links with the HTML documentation of the&lt;br /&gt;
AP210 standard.&lt;br /&gt;
&lt;br /&gt;
NOTE: This is a placeholder to ensure the published reference in ISO 10303-210:20010 is valid.&lt;br /&gt;
The published HTML of ISO 10303-210:2010 is not publicly available.&lt;br /&gt;
The files that are not copyright ISO will be posted here shortly.&lt;br /&gt;
&lt;br /&gt;
Documentation and descriptions provided by SFM Technology and NIST&lt;/div&gt;</summary>
		<author><name>Tom Thurman</name></author>	</entry>

	<entry>
		<id>http://www.wikistep.org/index.php/AP210_Scope</id>
		<title>AP210 Scope</title>
		<link rel="alternate" type="text/html" href="http://www.wikistep.org/index.php/AP210_Scope"/>
				<updated>2009-11-18T22:29:31Z</updated>
		
		<summary type="html">&lt;p&gt;Tom Thurman: New page: ====configuration control data pertaining to the design phase of a product's development:==== ====characterization data:==== *the association of characteristics to classes, functional obje...&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;====configuration control data pertaining to the design phase of a product's development:====&lt;br /&gt;
====characterization data:====&lt;br /&gt;
*the association of characteristics to classes, functional objects, physical objects, and analytical models;&lt;br /&gt;
*the identification of planned parameters for functional objects, assemblies, interconnect, components, and analytical models;&lt;br /&gt;
*the identification of actual parameters for functional objects, assemblies, interconnect, components, and analytical models;&lt;br /&gt;
*the description of catalog data including explicit capability for binding externally defined data element type identifiers to product data types;&lt;br /&gt;
*the configuration management of characterization data;&lt;br /&gt;
*representation of standard si units, derived si units and units defined in other systems of units;&lt;br /&gt;
*representation of class hierarchies for product data;&lt;br /&gt;
====interface data:====&lt;br /&gt;
*the behavioural description of devices or physical objects, including the functional interface definition;&lt;br /&gt;
*the description of the physical interface of devices or physical objects, including material characteristics and composition of the interface;&lt;br /&gt;
*the behavioural description of features realized as part of the interconnect, including the functional interface definition;&lt;br /&gt;
*the description of the physical interface of features realized as part of the interconnect, including material characteristics and composition;&lt;br /&gt;
*the mapping between the functional and physical interface definitions;&lt;br /&gt;
====simulation model data:====&lt;br /&gt;
*the configuration management of analytical model templates that are being developed concurrently;&lt;br /&gt;
*the explicit interface to externally defined analytical models that define the behaviour of a functional object, a device, a physical object, an electronic assembly, or an interconnect;&lt;br /&gt;
*the classification and description of analytical model template ports;&lt;br /&gt;
*the identification of analytical model template libraries;&lt;br /&gt;
====material data:====&lt;br /&gt;
*materials and their composition of chemical substance;&lt;br /&gt;
*composite material product structure, shape and material properties;&lt;br /&gt;
*classification of materials according to domain specific conductivity performance measures;&lt;br /&gt;
*characterization of surface conditions including surface finish;&lt;br /&gt;
====generic part or device data:====&lt;br /&gt;
*the functional description of devices or physical objects, including mapping between functional and physical terminals;&lt;br /&gt;
*the physical description of devices or physical objects, including material characteristics and composition;&lt;br /&gt;
*the configuration management of constituent parts or devices that are being concurrently developed;&lt;br /&gt;
*the identification of libraries used for synthesis and design re-use;&lt;br /&gt;
*catalogue data characterized by property value pairs or by data tables;&lt;br /&gt;
*substitute and alternate product data;&lt;br /&gt;
*approved supplier data;&lt;br /&gt;
====mechanical part data:====&lt;br /&gt;
*the physical description of devices or physical objects, including material characteristics and composition;&lt;br /&gt;
*the configuration management of constituent parts or devices that are being concurrently developed;&lt;br /&gt;
*the identification of libraries used for synthesis and design re-use;&lt;br /&gt;
*products that are mechanical parts;&lt;br /&gt;
*catalogue data characterized by property value pairs or by data tables;&lt;br /&gt;
====generic electrical part or device data:====&lt;br /&gt;
*the functional description of devices or physical objects, including mapping between functional and physical terminals;&lt;br /&gt;
*the physical description of devices or physical objects, including material characteristics and composition;&lt;br /&gt;
*the configuration management of constituent parts or devices that are being concurrently developed;&lt;br /&gt;
*the configuration management of programmable devices and assemblies;&lt;br /&gt;
*the identification of libraries used for synthesis and design re-use;&lt;br /&gt;
*products that are electrical parts;&lt;br /&gt;
*catalogue data characterized by property value pairs or by data tables;&lt;br /&gt;
====electrical part or device data specific to designs that include layered interconnect:====&lt;br /&gt;
*the functional description of devices or physical objects, including mapping between functional and physical terminals;&lt;br /&gt;
*the physical description of devices or physical objects, including material characteristics and composition;&lt;br /&gt;
*the configuration management of constituent parts or devices that are being concurrently developed;&lt;br /&gt;
*the configuration management of programmable devices and assemblies;&lt;br /&gt;
*the identification of libraries used for synthesis and design re-use;&lt;br /&gt;
*products that are electrical parts;&lt;br /&gt;
*catalogue data characterized by property value pairs or by data tables;&lt;br /&gt;
*the description of conductive pattern templates associated with the part or device;&lt;br /&gt;
*the externally accessible connection areas in the physical description of the device;&lt;br /&gt;
*the externally accessible surfaces in the physical description of the device;&lt;br /&gt;
*the classification of terminals in the physical description of the device;&lt;br /&gt;
*representation of interface and seating planes in the physical description of the device;&lt;br /&gt;
*the classification of device terminals;&lt;br /&gt;
*the physical description of terminal templates including connection areas;&lt;br /&gt;
*representation of the geometric relationship between two-dimensional and three-dimensional models of the device;&lt;br /&gt;
*representation of the shape of a device under different application contexts and material conditions;&lt;br /&gt;
*representation of an instance of a device in an assembly;&lt;br /&gt;
====bare semiconductor device specific data:====&lt;br /&gt;
*the device connection areas;&lt;br /&gt;
*the device surfaces;&lt;br /&gt;
*the classification of device terminals;&lt;br /&gt;
*representation of an instance of a device in an assembly;&lt;br /&gt;
====cable specific data:====&lt;br /&gt;
*the description of basic geometric properties of the cable;&lt;br /&gt;
*the description of the interface definition of the cable;&lt;br /&gt;
*the description of the functional definition of the cable;&lt;br /&gt;
*representation of an instance of a cable in an assembly including connector placement;&lt;br /&gt;
====electrical connector specific data:====&lt;br /&gt;
*the description of the equivalent functional network for the connector;&lt;br /&gt;
*the description of physical mating characteristics;&lt;br /&gt;
*the classification of connector terminals;&lt;br /&gt;
*representation of an instance of a connector included in a physical layer protocol definition;&lt;br /&gt;
*representation of an instance of a connector included in an interface definition;&lt;br /&gt;
*representation of an instance of a connector included in an assembly as a socket for another component;&lt;br /&gt;
*representation of an instance of a connector included in an assembly as an interface of that assembly;&lt;br /&gt;
*representation of an instance of a connector included in a cable interface definition;&lt;br /&gt;
====requirement data:====&lt;br /&gt;
*the description of the functional and non-functional requirements for the product;&lt;br /&gt;
*the description of the functional and non-functional requirements for devices used in the assembly;&lt;br /&gt;
*the description of the functional and non-functional requirements for devices and features used in the physical interconnection;&lt;br /&gt;
*representation of electrical and thermal domain specific requirements;&lt;br /&gt;
*representation of geometric model based requirements;&lt;br /&gt;
*the configuration management of documents that contain requirements;&lt;br /&gt;
*the allocation of requirements to functional objects, physical objects, and the physical implementation;&lt;br /&gt;
*the allocation of requirements from functional objects to their physical implementation;&lt;br /&gt;
*the description of the constraints on the design of the interconnect that assure product performance, incorporate quality, and enhance manufacturing process capabilities;&lt;br /&gt;
*the description of production rules that represent requirements and constraints;&lt;br /&gt;
====functional network data:====&lt;br /&gt;
*the hierarchical description of the functionality of the parts or devices that are used in an electronic assembly or interconnect;&lt;br /&gt;
*the hierarchical description of the functional objects that are combinations of one or more functional objects;&lt;br /&gt;
*the configuration management of the functional objects and networks that are being developed concurrently;&lt;br /&gt;
*the description of the connection among the functional objects;&lt;br /&gt;
*the binding of functional objects to simulation model templates;&lt;br /&gt;
*the identification of functional object libraries;&lt;br /&gt;
*representation of a functional test bench;&lt;br /&gt;
*the description of electrical and thermal networks;&lt;br /&gt;
*representation of binding a thermal network node to physical domain product data;&lt;br /&gt;
====physical network data:====&lt;br /&gt;
*the description of the components that are in the role of function implementation for the functional network elements;&lt;br /&gt;
*the description of the connection among the components that are in the role of function implementation;&lt;br /&gt;
*the description of path based requirements for connections between physical terminals based on functional performance measures;&lt;br /&gt;
*the description of path based requirements for connections between classes of physical terminals based on functional performance measures;&lt;br /&gt;
*the configuration management of the physical network;&lt;br /&gt;
*the identification of the domain of the physical network;&lt;br /&gt;
====assembly data:====&lt;br /&gt;
*the physical layout of the assembly, including a description of the placement of the physical objects in the assembly;[[#CO_Basic_assembly]]&lt;br /&gt;
*the description of the constraints on the design of the assembly that assure product performance, incorporate quality, and enhance manufacturing process capabilities;&lt;br /&gt;
*the allocation of domain specific elements of the assembly design description to the interface description of a part or device;&lt;br /&gt;
*the description of assemblies to implement various functional domains including, but not limited to, analogue, digital, video, radio frequency, and microwave;&lt;br /&gt;
*the allocation of each specific connection among the devices used in the assembly to the component or group of components that realizes that connection;&lt;br /&gt;
*products that are electrical assemblies or that are mechanical assemblies;&lt;br /&gt;
*the description of assemblies that include more than one instance of a component in the role of interconnect;&lt;br /&gt;
*representation of an instance of a part in an assembly through its usage in a sub-assembly;&lt;br /&gt;
*the description of assembly panels used for manufacturing assemblies in lot quantities;&lt;br /&gt;
*representation of the joint between a feature of a component in the role of interconnect and a feature of a component that is in the role of function implementation;&lt;br /&gt;
&lt;br /&gt;
====discrete wiring based interconnect data:====&lt;br /&gt;
*the description of the wires that help realize the interconnect;&lt;br /&gt;
*representation of a wire in an assembly, including the wire shape and termination shape;&lt;br /&gt;
*the description of other components in the assembly that help realize the interconnect;&lt;br /&gt;
====cable based interconnect data:====&lt;br /&gt;
*the description of the cables that help realize the interconnect;&lt;br /&gt;
*representation of the shape of the cable in an assembly, including the cable centreline curve and connector locations;&lt;br /&gt;
====layered substrate based interconnect data:====&lt;br /&gt;
*the description of the material stackup, including stackups for sequential laminates and complex configurations of multiple sub-stacks;&lt;br /&gt;
*the description of conductive and non-conductive materials and patterns;&lt;br /&gt;
*the description of composite structures for non-conductive materials;&lt;br /&gt;
*representation of hierarchical footprint patterns, including breakout patterns;&lt;br /&gt;
*geometric patterns that include product data to explicitly represent detailed design intent;&lt;br /&gt;
*geometric patterns that do not include detailed design intent knowledge;&lt;br /&gt;
*representation of manufacturing requirements using geometric properties or electrical impedance properties;&lt;br /&gt;
*geometric patterns that are manufacturable descriptions of the design, including needed manufacturing geometric elements;&lt;br /&gt;
*the allocation of domain specific elements of the interconnect design description to the interface description of a part or device;&lt;br /&gt;
*the description of interconnect design where transmission line effects are ignored;&lt;br /&gt;
*the description of interconnect design where terminals are point on surface, point on edge, or an area in cross section of the interconnect;&lt;br /&gt;
*the description of interconnect design where transmission line effects are modeled using transmission line templates;&lt;br /&gt;
*the description of interconnect design where each element in the design is separately modeled using microwave design template library;&lt;br /&gt;
*the functional and physical description of features realized as part of the interconnect, including material characteristics and composition;&lt;br /&gt;
*representation of an instance of a part in an interconnect through its usage as an embedded component;&lt;br /&gt;
*representation of assembly manufacturing specific features;&lt;br /&gt;
*representation of test manufacturing specific features;&lt;br /&gt;
*representation of fabrication manufacturing specific features;&lt;br /&gt;
*the description of fabrication panels used for manufacturing substrates in lot quantities;&lt;br /&gt;
====multi-domain model data:====&lt;br /&gt;
*the description of electrical, thermal, mechanical sub-models;&lt;br /&gt;
*two-dimensional geometric representations of sub-models;&lt;br /&gt;
*three-dimensional geometric representations of sub-models;&lt;br /&gt;
*the description of the explicit relationships required to maintain consistency between the sub-models;&lt;br /&gt;
*two dimensional shape representations of a part or device, assembly, or interconnect:&lt;br /&gt;
*geometrically bounded surface models;&lt;br /&gt;
*non surface bounded solid models using constructive solid geometry;&lt;br /&gt;
====three dimensional shape representations of a part or device, assembly, or interconnect:====&lt;br /&gt;
*geometrically and topologically bounded wireframe models;&lt;br /&gt;
*geometrically bounded surface models;&lt;br /&gt;
*topologically bounded solid models with facetted, elementary and advanced faces;&lt;br /&gt;
*non surface bounded solid models including constructive solid geometry, curve swept and other swept solids, thickened face solid;&lt;br /&gt;
*solids with construction history;&lt;br /&gt;
*topologically bounded manifold surface and subsurface and non manifold surface models;&lt;br /&gt;
*topologically bounded compound models;&lt;br /&gt;
*geometric validation properties to allow the translation of geometric shape representations (advanced boundary representation and faceted boundary representation solids) to be checked for quality;&lt;br /&gt;
*geometric and dimensional tolerances applied to geometric shape representations;&lt;br /&gt;
*three dimensional presentation of product data:&lt;br /&gt;
*arranging geometric elements in layers and groups and assigning colours;&lt;br /&gt;
*presentation styles for points, curves, surfaces and sections, including hatching and tiling;&lt;br /&gt;
*saved views of particular camera positions and sections;&lt;br /&gt;
*textual annotation and notes applied to geometric elements;&lt;br /&gt;
*presentation of geometric and dimensional tolerances;&lt;br /&gt;
*technical drawings as two dimensional presentation of product data.&lt;/div&gt;</summary>
		<author><name>Tom Thurman</name></author>	</entry>

	</feed>
