A GRAPHIC DATABASE FOR INTERACTIVE CAD tkwo Oyake, Hirotaka Mizune & Masayuki Yamagishi Computer System Division, OKI Electric Industry Co., Lté., Japan This paper concerns a graphic database which plays a central role in computer aided design for very complicated and structured objects like mechanical products. ‘A new approach is proposed here to answer how to construct a database for such geometric information and how to manipulate it interactively in the design process. This graphic database enables the CAD system* 10 be set up as well defined of- ganization, and also greatly helps improve the man-machine interface between the system and the designers, INTRODUCTION Design Process Practically speaking, a vast amount of geometric information is involved in designing a mechanical product, ‘The design process is devided into the following steps, conceptual design, basic design, detailed design, and drawing. At each step geometric information composing the product has particular characteristics as described below. Step 1) Determining specifications for functions, performance. etc. To satisfy the desired functions and performance, a mechanism is selected from the existing models, or is newly drafted. The shapes of the entire product and the individual parts are still vague and lack partic ular details, Step 2) _Basic design ‘The shapes of the entire products and the parts are outlined in order to accomplish the desired mechanism. However, they are still rough, and the three-dimensional models reside in the designer's brain, Step 3) Detailed design ‘To meet the specifications, the shapes and dimensions are determined by performing assembly simulation and design calculations through trial and error. Also, details of the shapes must be established with consid- eration on requests from production and assembly processes and on restrictions involved in such processes, At this step, significance is given to the dimensions and their accuracy. At this step, geometric information is given a predominant role in the design information. Step 4) Drawing Drawings are produced to pass the design information from design to manufacturing. The shapes are com- pletely specified in the drawings. The 3-dimensional geometric information is converted into 2-dimensional representation. In addition to the information specifying the shapes of the parts. the drawings also contain information about the physical characteristics of the parts and for manufacturing in 2-dimensional represen- tation, 133Requirements for a Graphic Database The following two points are emphasized, considering requirements for a graphic database. (1) A gmaphic database should provide a description facility which is Mexible enough to deal with the various types of information in the above design process. (2) All geometric information should be handled only through a graphic database in 3 consistent manner. Alo, the database should be manipulated by way of the pictute displayed on a graphic terminal so that records can be added. deleted, or modified easily, surely, and consistently: Current State of the Art Recently much research and development has been done on geometric modelling for 3D shapes(*%2MSX4NSKS) And Database Systems designed to handle 3D models include GLIDE and the World Model. GLIDE™ is a eraphie databace system oriented to. architectual design, and is operated through a specially designed language similar to conversational ALGOL. The World Model®) is a database system developed with the intention to apply to the field of mechanical assembly. In this system, shapes are represented as procedures through the use of a language resembling PL/I, and these procedures are executed by the geometric design processor. In this way, 3D models are generated in the World Model, Interactive graphics is one of the applications in the World Modsi. It & observed that the database itself is specially constructed to help assembly processes. The graphic database reported herein sims to handle various types of geometric infor- imation in design and helps 4 designer manipulate geometric data in a consistant manner while observing 4 picture displayed on the setven of a graphic terminal, GRAPHIC DATABASE FACILITY System Configuration AL present, an experimental CAD system for mechanical products assembled with a variety of parts is operating on 3 minicomputer, OKITAC System 0. ‘The system configuration of the CAD system is shown in Fig. 1. The portion bounded by dotted lines represents the graphic database (GDB), The software is written in SPL (System Programming Language developed by OKI). Data Description The Bachman diagram? shown in Fig. 2 illustrates records handled by the GDB for mechanical products and logical relationships between the records. The CODASYL terminology”) is mainly used in explaining ‘our database, The GDB handles three types of record as indicated: = Cataloged record type © Three-dimensional geometric record type + Two-dimensional geometric record type ‘The cataloged type refers to such records that occur whenever an assembly or a part is cataloged, Each record consists of more than one field for the defined assembly or part name, date of cataloging, comments, application data, etc. Assembly records and part records belong to this type. The contents of a cataloged record are dependent on the application of mechanical design. The 3D geometric type refers to such fecords that contains vertices, edges, faces, ete. An extended winged-edge representation by Baumgart'!) is used for shapes. Shape records belong to this type. The 2D geometric type refers to such records that contain lines, arcs, character strings, symbols, etc. Assembly drawing records, part drawing records, and figure records belong to this type. Some examples of record definitions in the GDB are presented below. The data description language used there is merely virtual one for the sake of explanation, The actually used data description language defenes 134also physical factors, including the size of each recon on a disk and the afea necessity fo conacel ane variable-length record to another. RECC PART (Part record definition) ITEM NAME 12 bytes (Part name) ITEM DATE 12 bytes (Catalog date ITEM CMNT 30 bytes (Cominents) ITEM MTRX 24 bytes (Transformation matrix for layout ina assemtaly) GROUP DMNS Seeaes (Dimension data between faces) REC3 SHAP (Shape reeord definition, A recon! format is provided by therefore u user need not specify in the record.) REC? PVEW (Part drawing record definition) RECC defines a cataloged-type record consisting of more than one item or group, group is structured items in 3 record. REC3 defines a 3D geometric type record. REC2 defines a 2D geometsic type recon ‘The following statements define set types between records shown in Fig. 2. The data deseription Language used there is again merely viztual SET PS (Definition of the owneramcmber relationship between the part recor and. the shape record) OWNER PART. MEMBER SHAP GDEPEND A SET PV (Definition of the owneranemt lationship between the part recon! snd the drawing recond) OWNER PART MEMBER PVEW GDEPEND B SET defines a parent and child relationship between two records. An owner recond is specified by GWNER, and a member recond is specified by MEMBER. In general, 3- and 2-D geometric reconts cannot become owner records. Owner-member sets facilitate to retrieve related reconds according to their relation, and also give graphic dependency to the relationship between the concerned records. Graphic Dependency ‘The concept of graphic dependency is explained below. As seen in the above definitions, layout matrix data and dimension data conceraing the geometry of products are contained in PART records. Also, shape data and part drawing data are contained in SHAP records und PVEW records, respectively. In this way, the GDB is not homogencously structurd in relation to the geometric entity of a given product, but is heterogeneous in theis respect -~ that is, data from the same source may be distributed to different records, each of which has different representation power for geometric information. Therefore, it is important that graphic dependency is specified in the description entry for owner-member relationship so that consis- tency within the database can be maintained when a series Of manipulations on the database are performed to modify record data (Refer to Fig, 3), GDEPEND specifies the degree to which the specified member tecord is dependent on the specified owner record. If “A™ is specified, whenever the owner record is fied, the related geometric information in the member records is also changed. This procedure is provided by the GDB system. When a member record is modified, the owner record is simply notified. In other words, the owner record receives a message from the member one. Asa result, when tef owner record later, the designer can know that the member record has been modified. If “B 5 an owner record modification only causes the member records to be notified. When a member record is modified, the owner record is not notified. Take SET PS as an example. When dimensions ina part record are modified, the geometric information in the member record SHAP is changed. IF the member record is modified, the owner part record is notified, Take SET PV as another example. When the part record is modified, the part drawing record is notified. Even when the part drawing record is modified or edited, asthe owner part record is not notified. As seen from the above discussion, graphic dependency is given according to the semantics of each geometric data in the design process. In this way, when a change occurs some range of data, it is notified only to those records defined in the database which are affected by it, ‘This function is essential to the database which handles a vast amount of geometric information and can be manipulated through trial and erros. Interactive Manipulations The design of a product is described as a process to convert the specifications for the functions and per- formance of 3 product into the detailed geometric information as drawings through trial and error. In computer aided design, this is represented by changes in the database 3s illustrated in Fig. 4. What is encircled in the figure (entity) is the actual value of the record. A design process shown in Fig. 4 cor responds to a scries of triakand-error based data manipulation steps to create, delete, and modify records and to put records of different types into logical relation. Manipulations. on the GDB have two levels, function level and command level. A function is considered 2 mapping between records in the database, and is intended to: implement a particular design function. Commands are available to realize each function, ‘A designer selects a function to declare the {ypes of records from and into which the mapping is to be performed, and inputs appropriate commands. An outline of functions and commands will be shown below, The functions are related to the records defined in the 2.2 section. Figure Generation Function (FGF); ‘The record type concerned is FIGR. Basic graphic commands are repeatedly used to define a number of line sepments on the screen until the segments determine a well-defined 2D area. The set of these segments can then be stored as a figure in the FIGR record (See Fig. 5). Shape Generation Function (SGFY: ‘The record types concerned are FIGR and SHAP. This function converts a 2D figure stored in the FIGR record into a 3D shape through the use of two commands SWEEP and REVOLVE (Sce Fig. 6). Shape Editing Function (SEF) The recond type concerned is SHAP. This function is to map a 3D geometric record into itself. Theee types of sct operation -- UNION, DIFFERENCE, and INTERSECTION —and 3D mirror operation, MIRROR, are available (See Fig. 7). Since shapes created by SEF can be subjected to modifications on dimension data in PEF (mentioned later) it is possible to create shapes with inaccurate dimensions first and correct them for exact dimensions later when necessary. In this respect, 3D shape generation and editing are con- sidered & step for.a 3D rough sketch, Generated shapes can be checked after the hidden lines are eliminated. fart Catalog Function (PCF) The record types concerned are SHAP and PART. When two faces of a shape are designated, the dimension value and fine associated with the specified faces are displayed automatically (See Fig. 8). The cataloged part record has the member record which contains the 3D shape of the part. Part Editing Function (PEF) ‘The record type concerned is PART and SHAP. This function controls the dimension data to determine the shape of a part. For example, it is possible to change the distance between two parallel planes (See Fig. 9) or alter the radius of a cylinder. Assembly Catalog Function (ACF): ‘The record types concerned are PART and ASSM. This function is to map part records into a cataloged assembly record, It is intended for assernbly simulation. A designer need not enter any coordinate value oF direction, Simply by designating related faces of the part shapes, it is possible to assemble these parts. Drawing Generating Function (DGF): ‘The record types concerned are ASSM and AVEW or PART and PVEW. This function is to map a cata- loged record into a 2D geometric record. A part drawing and an arbitrary view of the part are created automatically according to the shape and dimension data cataloged in PART. Similarly, an assembly drawing can also be created. 136Drawing Editing Function (DEF): ‘The record type concerned is AVEW or PVEW, This function acts on a drawing or an assembly drawing generated by DGF. It modifies details only on the drawings, adds dimension tines and center lines, and. Places various character strings and symbols. Final part and assembly drawings can thus be obtained. Graphic Format and Structure ‘A graphic format and a graphic structure of a screen are determined for each function mentioned above. ‘A graphic format determines how the contents of a record ate to be laid out on the sereen. For example, at the level of part drawing editing (DEF), views of the shape and dimensions of the part are displayed in a specific format, A graphic structure defines a structure of a picture displayed onthe screen. Fig. 11 shows a typical example. Three actions of identical picking cause three different things to be selected because the structures in the three cases are different: a part in case I, a face in case 2, and a line segment in case 3, When the Assembly Catalog Function is being performed, the graphic structure allows any part and face to be selected from the picture displayed on the screen. During the step of the Part Editing Function, the display structure allows any face and dimension to be sélected, The display structure fore the Drawing Editing Function makes it possible to select any line segment, character string, and symbol. Graphic formats and structures are essential points to be considered for building up the suitable graphic database, EXAMPLE OF USING THE GDB ‘This chapter presents an example of a design process using the GDB. A designer creates a 3D model on the GDB by performing the Shape Gencration Function while observing the picture on a graphic display screen. As a result of this step, the designer has, in effect, drafted a 3D rough sketch (Sce Fig, 12). Next, using the drafted model, the designer repeateuly simulates the desired assembly, computes the necessury physical quantities, and edits the parts in the 3D space, thereby determining the slimensions for the part shapes in every particular, The determined dimensions are then cataloged in the GDB (See Fig. 13). Once the shapes of the parts have been determined in details, the Drawing Generation Function can be performed to create a set of three views foreach part. A basis for the part drawing is now set up automatically. Next, the use of the Drawing Editing Function (in the 2D space) makes the picture perfect in the form of a drawing (See Fig. 14). Details of the assembly can also be projected on a drawing in which hidden lines have been properly treated. Once cataloged in the GIB, these drawings cam be cdited and checked. As mentioned above, the GDB system enables the designer to perform various operations, encompassing from rough model drafting to drawing creation, while communicating with the system, CONCLUSTION ‘The aforementioned graphic database (GDB) system arranges various types of design information into three record types: cataloged type, 2D geometric type, and 3D geometric type, thereby helping a designer manipulate desired records while communicating with the system through a graphic terminal. As a result of this function, the desien information is structured consistently so that data about 3D shapes and about drawings are linked to other associated data to facilitate manipulation of data, Also, interactive processing by way of the graphic display eases steps of generating, modifying, and editing data, Data about geometric entities can be checked by ditecting the system to display on the screen the necessary part and assembly shapes with hidden line eliminations. Another feature is the facility to include in the database definition the information conceming the need to synchronize the modification of a record with that of another related record in order to prevent inconsistency between related records, such as the record for a 3D shape and the record for the drawing of the shape. ‘The authors believe that, by further refinement of the GDB manipulation language to incorporate some 137additional but basic functions, the GDB can be advanced! to a general-purpose system to be useful for ‘computer aided design in various Fels. The principal features of the GDB are; 41) Database structure based on thie above-mentioned three record types (2) Interactive manipulation language to be used throug a graphic display (3) Proper relaliohsip between the manipalation language and the display Formats and structures, (4) Fmployment of the concept of graphical dependeney 10 prevent inconsistency between records and fo enhance the function of modifying the part information im order to respond to the demand for frequent modifications unavoidable in design. At present. the GDB system has been implemented on 4 minicamputer OKITAC System 50 and is operating ‘with two graphic terminals ACKNOWLEDGEMENTS *The system i being developed ay part of the mational R-& D projest entitled “Flexible Mamvfacturing ‘System Complex Provided with Layer. supported hy the Agency of Industrial Scicnee and ‘Technology, MINISTRY OF INTERNATIONAL TRADI AND INDUSTRY. REFERENCES, (UN. Okino, et al, “TIPS-1; Technical Information Provessing System for Compuler-Aillcd Design, Drawing and Manufacturing” Proc. of the sccon PROLAMAT (1973), Sesion I (2) 1.©. Braid, “The Synthesis of Solidy Bounvled by Many Faces", Comm, ACM, Vol. 18 (1975) (3) LB, Vowleker, ct at. Am Lotrodue University of Rochester fo PADL, Memo 22, Production Aulomation Project, (4) |. Oyake, “Part Representation in CAD/CAM™ Proceedings af ALIPS, NCC (1975) pp. 801-404 (5) 1. Oyuke and M. Shu, “Object Synthesis for Design and Manufacturing”, NCS Proceedings 13th Conference (1976) pp, 541-553 (6) M. Hosaka ond F, Kimura, “Ae interactive Geometrical Design System with Handwriting Input Information Processing 77. North-Iolland, Amsterdam (1977). 7) GLb) versity reference manual, Draft version 1.1, Institute of Physical Planning, Carnegie-Mellon Unie (8) M.A. Wesley, et all. “A Geometric Mexleling System for Automated Mechanical Assembly” J.RES. DEVELOP., Vol. 24, No. I. January (1960) pp. 64-74 1M (9) CW, Bachman, “Data Structure Diagram Interest Group on Business Data Processing Dota Base, 1, No. 2, 4-10 (1969) ACM Special (10) CODASYL, Data Description Language Committee, Journal of Development 1978, (11) BG, Baumgart, “A polyhedron Representation for Computer Vision”, Proceedings of AFIPS, NCC (1975) pp. 389-394Command Processing, Modules Process Basic Functions {—- al canine aU S e QO; O 2 ! | i ! 1 1256 kw (16 bits/word)| Fig. 1 System Configuration 20 Geometric Type PART AV 4 AVEW. AP j Asem shank Layout Dimension Record Matrix Data SHAP. PvEW S Part rowing Shape Data Record es Pvew Sy (eo {30 Geometric Type) Faure 4 Fig. 2. Records in the GDB Fig. 3. Graphic Dependency 139Spec. Fig. 4 Change of Data during a Design Process L-Bracket Lines Created by Batic Commands ‘3D Shape Created by SWEEP Bolt Figure Created by FGF ‘3D Shape Created by REVOLVE Fig. 5 Figure Generation Function Fig. 6 Shape Generation Functionlo] & nti Semmttieenioe Co [Eh ing a cylinder from the L-bracket using DIFFERENCE From the shape of an LH-bracket, the distance between two faces is calculated. It isthen possible to enter dimension data. Fig. 7 Shape Editing Function Fig. 8 Part Catalog Function ‘The small part specified in the right top Part editing by changing the denoted ‘comer of the screen is combined with the dimension from XXX to YYY. L-bracket. This assembling is dane simply [by designating the related faces. Fig.9 Part Editing Function Fig. 10 Assembly Catalog Function Ma(1) Part (2) Face (3) Line Fig. 11 Picking Action and Graphic Structure Fig. 12. GDB Application Fig. 13 GDB Application Fig, 14. GDB Application