0
TECHNICAL PAPERS

A Grammar Driven Data Translation System for Computer Integrated Manufacturing

[+] Author and Article Information
Glen L. Niebur

Department of Aerospace and Mechanical Engineering, The University of Notre Dame, Notre Dame, IN 46556

Thomas R. Chase

Department of Mechanical Engineering, The University of Minnesota, Minneapolis, MN 55455

J. Mech. Des 124(1), 136-142 (Feb 01, 1999) (7 pages) doi:10.1115/1.1434268 History: Received February 01, 1999
Copyright © 2002 by ASME
Your Session has timed out. Please sign back in to continue.

References

Korenjak, A. J., and Teger, A. H., 1975, “An Integrated CAD Data Base System,” Proceedings of the 12th Design Automation Conference, IEEE, pp. 399–406.
Beeby,  W., 1982, “The Future of Integrated CAD/CAM Systems: the Boeing Perspective,” IEEE Comput. Graphics Appl., 2, No. 1, pp. 51–56.
Blackburn,  C. L., Storaasli,  O. O., and Fulton,  R. E., 1983, “The Role and Application of Data Base Management in Integrated Computer-Aided Design,” J. Aircr., 20, No. 8, pp. 717–725.
Taylor, D. L., 1988, “Integrated Mechanical Analysis Project,” Proceedings, 1988 ASME Computers in Engineering Conference, ASME, New York, N. Y., pp. 189–196.
Lapointe, J., 1985, “An Information Based Approach to Integrated Computer-Aided Engineering,” Masters Thesis, The University of Rhode Island.
Sidle, T. W., 1980, “Weaknesses of Commercial Data Base Management Systems in Engineering Applications,” Proceedings of the 17th Design Automation Conference, pp. 57–61.
Frank, U., and Klein. S., 1992, “Three Integrated Tools for Designing and Prototyping Object-oriented Enterprise Models,” NTIS Report GMD-689, US Department of Commerce.
Gilliam,  C., 1994, “An Approach for Using OMT in the Development of Large Systems,” Journal of Object-Oriented Programming, 6, No. 9, pp. 56–59.
Shah,  J. J., and Rogers,  M. T., 1988, “Functional Requirements and Conceptual Design of the Feature-Based Modeling System,” Computer-Aided Engineering Journal, 5, No. 1, pp. 9–15.
Whelan, P. T., and Fulton, R. E., 1988, “Experiences With Relational and Object Oriented DBMS s for CAD/CAM Data,” Managing Engineering Data: Emerging Issues, The 1988 ASME International Computers in Engineering Conference and Exhibition, ASME, New York, N.Y., pp. 13–18.
Yang, Y. K., 1988, “A Natural Data Organization for a CSG-Based CAD Database,” Proceedings, 1988 ASME Conference on Computers in Engineering, ASME, New York, New York, pp. 301–307.
Spooner,  D. L., and Hardwick,  M., 1997, “Using Views for Product Data Exchange,” IEEE Comput. Graphics Appl., 17, No. 5, pp. 58–65.
Ryan, S. A., 1992, “PDES/STEP: A Status Report,” Engineering Data Management: Key to Integrated Product Development, Proceedings of the 1992 ASME International Computers in Engineering Conference and Exposition, T. R. Chase et al. ed., ASME, New York, N. Y., pp. 43–47.
Aho, A. V., Sethi, R., and Ullmann, J. D., 1986, Compilers, Principles, Techniques, and Tools. Addison-Wesley, Reading MA.
AutoCAD, 1988, AutoCAD Release 10 Reference Manual, AutoDesk Incorporated.
ANSYS, 1994, ANSYS Version 5.0 Users Manual, Swanson Analysis Systems Incorporated.
Stonebraker, M., 1987, “The POSTGRES Storage System,” Proceedings of the 1987 VLDB Conference, Brighton England.
Huang, J., Wang, T., Wan, L., Zhang, X., and Zhou, J., 1994, “Step-based CAD/CAPP/CAM Integrated Systems: CADMIS,” Engineering Data Management: Integrating the Engineering Enterprise, ASME.

Figures

Grahic Jump Location
The data sharing architecture is built on a database management system. A translation program moves data from the central database to applications.
Grahic Jump Location
Database methods are used to map the data between differing representations or to perform complex schema transformations. Thus, the translator need only reformat the data, which can be done based on simple grammar rules. The methods become part of the database management system, and can be used for all applications that require the same data transformations.
Grahic Jump Location
Datatrans accesses the database and the application data files through interface programs. This isolates the translation process from the underlying data storage formats and schemas. The commands to the database interface and file interface are embedded in data description files, so that the interface commands to both the database manager and the data file are completely configurable for each application.
Grahic Jump Location
The format of a data description file. Lines beginning with # are comments. Bold face words are Datatrans keywords. The control section defines the processing actions, the tokens section specifies regular expressions to be recognized by a lexical analyzer, and the rules section specifies a context free grammar to be recognized by a parser.
Grahic Jump Location
(a) A two dimensional design of a retaining ring was created in the drafting program. (b) The geometry was imported into the FEA program and a finite element mesh was created.
Grahic Jump Location
(a) The DXF representation of a circular arc (column 1). The lexical analyzer converts each of these to tokens to be passed to the parser (column 2). The progression of grouping the tokens to represent a circular arc, and finally a geometric entity in through the productions figure 6b is shown in columns 3 to 6. (b) The productions from the data description file that recognize the circular arc in the DXF file. Note that arcs are stored as circles in the database. (c) The query generated by Datatrans to store the circular arc from figure 6a, and the resulting data retrieved from the database. The entity level, line style, and color are stored in the entities table in Postgres, of which the circles table is a subtype. Querying the circle table does not retrieve this data unless it is specified explicitly.
Grahic Jump Location
(a) The query from the data description file that is used to retrieve circles. Arc_start_point, and arc_angle are database methods that compute the location of a point on the arc, and the included angle of the arc, which are needed for the arc command in the FEA program. (b) The data retrieved by the query in a. (c) The productions from the data description file that recognize the data. (d) The FEA preprocessor commands that generate the arc. The preprocessor command language provides the capability to define the variables, kp1, kp2, and nextkp, which are used as identifiers for the keypoints used to create the circle. Alternatively, these could be generated within the database manager.

Tables

Errata

Discussions

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