Document-Driven Design for Distributed CAD Services in Service-Oriented Architecture

[+] Author and Article Information
Yan Wang1

NSF Center for e-Design, University of Central Florida, 4000 Central Florida Blvd., Orlando, FL 32816-2993wangyan@mail.ucf.edu

Bart O. Nnaji

Center for e-Design, University of Pittsburgh, 1048 Benedum Hall, Pittsburgh, PA 15261-2210


Corresponding author.

J. Comput. Inf. Sci. Eng 6(2), 127-138 (Aug 11, 2005) (12 pages) doi:10.1115/1.2194911 History: Received January 23, 2005; Revised August 11, 2005

Current computer-aided design (CAD) systems only support interactive geometry generation, which is not ideal for distributed engineering services in enterprise-to-enterprise collaboration with a generic thin-client service-oriented architecture. This paper proposes a new feature-based modeling mechanism—document-driven design—to enable batch mode geometry construction for distributed CAD systems. A semantic feature model is developed to represent informative and communicative design intent. Feature semantics is explicitly captured as a trinary relation, which provides good extensibility and prevents semantics loss. Data interoperability between domains is enhanced by schema mapping and multiresolution semantics. This mechanism aims to enable asynchronous communication in distributed CAD environments with ease of design alternative evaluation and reuse, reduced human errors, and improved system throughput and utilization.

Copyright © 2006 by American Society of Mechanical Engineers
Your Session has timed out. Please sign back in to continue.



Grahic Jump Location
Figure 1

Comparison between binary relation in the traditional model and a trinary relation in the semantic model: (a) Binary relations capture semantics implicitly as aggregation and association in ER-type data models, and (b) trinary relations explicitly represent semantics of constraints and design intent with good extensibility

Grahic Jump Location
Figure 2

Semantic richness is associated with information loss during data transformation

Grahic Jump Location
Figure 3

Two levels of design intent, informative and communicative, need to be captured in semantic model: (a) solid model of anchor, (b) informative design intent is the abstract intention in the plan, (c) communicative design intent is the intention manisfested during the implementation, and (d) semantic model represents design intent explicitly with subject-predicate-object triples

Grahic Jump Location
Figure 4

Membership schema defines properties that are associated with semantic classes

Grahic Jump Location
Figure 5

Membership schema can be used in feature mapping between different domains: (a) definition of feature rib in SOLIDEDGE®, which supports finite thickness extension, and (b) definition of feature rib in PRO∕ENGINEER®, which does not support finite thickness extension. Extra feature cut may be needed to generated the geometry of (a)

Grahic Jump Location
Figure 6

Semantic interpretation helps to reduce ambiguity: (a) type I ambiguity of semantics – Different combinations of semantic features can generate the same geometry, and (b) type II ambiguity of semantics – Different geometry is created from the same semantic feature. Small variation of the parameter d causes topological differences in systems, such as SOLIDEDGE and PRO /ENGINEER .

Grahic Jump Location
Figure 7

Interoperable semantic feature model exchange based on common compound features: (a) search common semantics of substantive compound feature, (b) search common semantics of adjective compound feature, and (c) commonly agreed compound features are used to exchange data

Grahic Jump Location
Figure 8

Semantics simplification reduces the degrees of feature dependency: (a) feature semantics can be simplified by introducing datum features (b) examples of semantic equivalence

Grahic Jump Location
Figure 9

Membership schema expressed in RDFS syntax

Grahic Jump Location
Figure 10

The semantics is enriched gradually with multiresolution RDF documents

Grahic Jump Location
Figure 11

Feature representation and reasoning with RDF/XML documentation: (a) informational intent oriented high-level features and (b) communicative intent oriented low-level features

Grahic Jump Location
Figure 12

Document-centric interaction enables loosely coupled asynchronous CAD services

Grahic Jump Location
Figure 13

Service-oriented architecture for B2B engineering services

Grahic Jump Location
Figure 14

FIPER process model

Grahic Jump Location
Figure 15

An overview of the DDD system

Grahic Jump Location
Figure 16

DDD mechanism enables lightweight model construction based on documents: (a) document flow and processing in distributed environment, (b) sketch with global references submitted by client, and (c) models generated by PRO /ENGINEER with combinations of feature documents

Grahic Jump Location
Figure 17

A crankshaft model built with the DDD mechanism: (a) client requests DDD services from FIPER WEBTOP , (b)FIPER ACS and FIPER station direct DDD services to the service provider PRO /ENGINEER , (c) system-specific individual features for PRO /ENGINEER in XML documents, and (d)PRO /ENGINEER reads the 2D sketch file, and DDD driver processes feature documents in sequence automatically



Some tools below are only available to our subscribers or users with an online account.

Related Content

Customize your page view by dragging and repositioning the boxes below.

Related Journal Articles
Related eBook Content
Topic Collections

Sorry! You do not have access to this content. For assistance or to subscribe, please contact us:

  • TELEPHONE: 1-800-843-2763 (Toll-free in the USA)
  • EMAIL: asmedigitalcollection@asme.org
Sign In