KR20060070478A - Method and system for graphically navigating among stored objects - Google Patents

Abstract

The present invention relates to a product life cycle management (PLM) system comprising a database storing objects, preferably 3D objects and relationships between said objects. The PLM system provides the user with a graphical user interface suitable for displaying graphical representations of the hierarchy of objects stored. The graphical user interface is configured to display an object associated with the second selected object when the object displayed by the user is selected. At some level in the hierarchy, the displayed objects are distributed according to their respective weights. The weight of the displayed object depends on its lower number in the hierarchy, which is displayed in the graphical representation. The present invention makes it possible to navigate in a database of a PLM system, which stores highly complex modeled objects through correlated data. Due to the principle of weight dependency described, the solution also allows the user to understand its progress through organized data as well as the relationship between objects and data in an easy and intuitive way.

Navigating, data, layout

Description

METHOD AND SYSTEM FOR GRAPHICALLY NAVIGATING AMONG STORED OBJECTS}

1 to 3 are diagrams of embodiments of illustrative objects, displayed according to an “in-disk” layout.

4-6 are diagrams of embodiments of illustrative objects, displayed according to an “in-line” layout.

7 and 8 are diagrams of embodiments of illustrative objects, displayed in accordance with an “alternate in-line” layout.

9-11 illustrate embodiments of plane related objects, displayed in accordance with an “in-disk” layout, viewed from above.

12 is a diagram of embodiments of objects associated with a plane, displayed according to a layout as in FIGS. 1-3.

13-15 are diagrams of embodiments of objects associated with a plane, displayed according to a layout as in FIGS. 1-3.

FIG. 16 is a diagram of embodiments of objects associated with a plane, displayed according to a layout as in FIGS. 7 to 8;

17 is a schematic diagram of a software architecture that may be used to carry out the present invention.

18 is a flow diagram of a process for creating 3D representations to carry out the present invention.

19 is a schematic diagram of a client workstation architecture configured to carry out the invention.

20 is a schematic diagram of a network structure configured to carry out the present invention.

* Description of the symbols for the main parts of the drawings *

100: GUI 200: first object

202: Disk 204-210: Second object

110, 120: Menu Bar 150: Transparent Icon Board

213, 214, 216, 218, 220: child

500: navigation engine 520: contact engine

540: database client 560: database server

620: Vault Server 640: Visualization Engine

660 display driver

TECHNICAL FIELD The present invention relates to the field of computer programs and systems, and more particularly, to a product life cycle management solution comprising a database of data representing modeled objects.

A number of systems and programs, such as those provided by Dassault Systemes under the trademark CATIA, are provided on the market to design parts and assembly of parts and to form products. These CAD systems allow a user to construct and manipulate complex three-dimensional (3D) models of objects or assemblies of objects. Thus, the CAD system provides a representation of objects modeled using edges or lines, in particular cases faces. Lines or edges can be represented in various ways, such as, for example, non-uniform rational B-splines (NURBS). These CAD systems manage parts or assemblies of parts as modeled objects, which are essentially specifications of geometry. In particular, CAD files include the particulars from which geometry is generated, which in turn takes into account the representation to be generated. Specifications, geometry and representation may be stored in a single CAD file or multiple files. CAD systems include graphical tools that represent modeled objects to designers, which are dedicated to the display of complex objects, the typical size of a file representing an object in the CAD system ranges from 1 megabyte per part, The assembly may include about 1000 parts. The CAD system manages models of objects stored in electronic files.

 Under the CATIA, ENOVIA, and DELMIA trademarks, there is a Product Lifecycle Management Solution (PLM) provided by Dassault Systems, which is an Engineering Hub that organizes product engineering knowledge, Manufacturing Hub, and the Engineering Hub and Enterprise Hub, which enable enterprise integration and connectivity. The system as a whole provides an open product model that combines products, processes, and resources to support dynamic, knowledge-based product production and decision-making that drives optimized product definition, production readiness, production and service. To make it possible. These PLM solutions include a relational database of products. The database contains a set of data and relationships between the data. In general, data includes technical data related to products, which are indexed to be sortable and searchable in a hierarchy of data. The data represents modeled objects, which are primarily modeled products and processes.

One such PLM solution is that a user of a system may want to display a product and, if necessary, have a 3D graphical representation of the product. DASSAULT SYSTEMES offers a series of CAD tools under the so-called DMU review to allow users of PLM solutions to coordinate 3D graphical representations of products managed in their systems. These tools rely on the use of pre-computed digital mock-ups from the CAD representation of the product. These tools additionally provide a limited set of product's graphical clocks, and specifically, the DMU system generally provides a 3D representation of the product. In a system released under the so-called DMU navigator, the user can display a 3D representation of a complex product, the display further comprising a hierarchical tree representing various products or portions of the displayed product. The system provides the user with a 3D representation of the product stored in the database. However, navigation in this system can continue to be improved.

In CAD tools such as DMU Review or DMU Navigator, users can only navigate between products or parts that are loaded into the system. Therefore, the scope of the present invention is that if a user wants to navigate between all possible products or assemblies, he must load all those products or assemblies, which is impossible due to hardware constraints and transaction issues. Because it is very limited.

In fact, DMU products are limited in terms of the scope of navigation. Specifically, every user first opens a DMU session, and a list of restricted parts and assemblies is defined. This makes it possible for the system to calculate and store the representation to be used later in the DMU navigation. Navigation is limited to the list of parts and assemblies defined when the DMU session is opened.

The user may also want to know where and for example a product such as a brake pedal can be used, ie what other models it can be included in. Standard CAD tools allow the user to navigate primarily in accordance with an "is composed of" relationship between parts or products. Databases used in PDM systems allow for queries on various types of relationships between parts or products, and the scope of navigation of the databases is the widest possible. In fact, a user can have access to parts, products or assemblies.

However, in general, since the data does not have a graphical representation, the user cannot easily navigate the database. The data is identified by file name or type, which name may not be adequate enough to identify the exact item the user is looking for.

The problem of navigating in organized data has been widely mentioned in the literature.

For example, US-A-6,628,304 provides a method and apparatus for providing hierarchical data to a user through a graphical user interface. Preferred embodiments represent hierarchical data associated with a computer network and are provided to the user as part of a network management software application. In the interface, hierarchical data is represented by nodes, starting at one or more higher nodes and extending to lower hierarchical levels by display of child nodes, child nodes of children, and the like. The configuration of nodes on the graphical user interface is such that scaling depicts various hierarchical levels, and the nodes do not partially interfere with each other. Navigation through hierarchical data selects any clock node to the user, indicative of a zoom-in or zoom-out clock at the node selected as the centered node on the interface. By providing it. Lower hierarchical levels of child nodes that could not be seen before selection would be shown in a predetermined number of levels in the hierarchy.

WO-A-98 / 22866 relates to an interface for an interactive display device comprising at least two levels having at least two objects that can be displayed on the interactive display device, the interface displaying each object once Thereby further comprising means for continuously displaying the entire set of objects at the same level. An object of one level includes at least one set of icons to be displayed on an interactive display device, includes a plurality of icons having the ability to operate on accessing information, an image, preferably a legend, and more. It preferably includes a pictogram that represents an attribute of the information accessed when the icon is operated.

CHI'91, Computing System (1991), pages 189-202, by Robertson, G, Mackinlay, J., and Card, S. in Human Factors "Contree: Animated 3D Visualization of Hierarchical Information (cone trees: animated 3D visualizations of hierachical information "discusses the technique of visualizing hierarchical information structures.

US-A- 2002/0054166 calculates a focus position for each of the included and linked nodes to display the surrounding and surrounding source nodes connected with the node and the included nodes and source nodes connecting with the linked nodes. Providing a first included node at the inclusion starting angle and a first linked node at an adjacent starting angle.

US-A-2002 / 0145623 relates to a user interface constructed and animated to optimize, facilitate, and simplify displaying through a user input a layer of information displayed on a display device and accessible by an electronic device. will be. The basic method includes, for example, displaying a plurality of nodes in the viewing area; Receiving a user input for selecting one of a plurality of nodes displayed in the viewing area; And centering a selected one of the plurality of nodes in the viewing area, wherein the central node is a focusing node. The plurality of nodes preferably includes a plurality of hierarchically related nodes.

Although the interface allows navigation in organized data, the data is not similar with respect to the PLM request, and the data represents a complex modeling object that is presented graphically. In particular, the proposed centering or focus does not allow the user to clearly keep in mind the progress through the organized data. In addition, such an interface is not suitable for allowing a user to distinguish between different relationships of data le linking.

Accordingly, there is a need for an improved navigation solution that allows users to navigate in a database of a product life cycle management system that stores very complex modeled objects through correlated data, short of the limitations of the existing solution described above. The solution should preferably be user-friendly and allow the user to locate and display the object in an easy and intuitive manner. In addition, the solution should keep the user in mind through the data organized to distinguish different types of relationships that link the data if necessary.

Thus, in one embodiment, the present invention provides a product life cycle management system, comprising: a database storing modeled objects and relationships between objects; And a graphical user interface suitable for displaying a graphical representation of a hierarchy of stored objects to a user, wherein the graphical user interface is configured to display objects associated with the selected object when the object displayed by the user is selected, The displayed objects are distributed according to their respective weights at a predetermined level in the hierarchy, and the weight of the displayed objects depends on the number of descendants of the object in the hierarchy displayed in the graphical representation. To provide a system.

In another embodiment, the product life cycle management system according to the present invention may include one or more of the following features.

The graphical user interface is configured to display the hierarchy of displayed objects and the graphical cue representation of the subordinate of the object in the hierarchy displayed in the graphical representation;

The displayed objects have a rendering size that depends on their respective weights;

The weight of the displayed object depends on the size of the descendants of the object in the hierarchy, displayed in the graphical representation;

The graphical user interface is configured to display the objects using their own scale for all objects;

The graphical user interface is configured to display a 3D representation of the objects; And

The graphical user interface is configured to morph from a first representation of the displayed object to a representation of objects related to the displayed object when the selection of the object displayed by the user is made.

In addition, the present invention provides a product life cycle management system comprising a graphical user interface suitable for storing modeled objects and relationships between objects and for displaying a graphical representation of a hierarchy of stored objects to a user. A method of navigating in a database of PLMs, comprising: selecting a first object and a first relationship; Searching for descendants of the first object in the hierarchy, the descendants including second objects associated with the first object according to the first relationship; Displaying a representation of a first object comprising second objects; Selecting a second relationship and one of the displayed second objects; Searching for subordinates of the selected second object, the subordinates comprising, through the second relationship, third objects associated with the selected second object; And displaying a representation of the first object, the second object comprising the second and third objects, wherein the displayed objects are distributed according to respective weights, the weights of the objects being displayed in the graphical representation, A method is proposed, which depends on the number of children of the object in the hierarchy.

In other embodiments, the method according to the invention may comprise one or more of the following features.

Objects are displayed as 3D objects;

Selecting the first object and the first relationship includes selecting a first layout, wherein the representation of the second objects is a representation in the first layout;

Selecting one of the displayed objects and the second relationship comprises selecting a second layout, wherein the representation of third objects is a representation in the second layout;

The layout includes a linear layout having objects represented in perspective views exploded along the line; In-place layout; A circular layout having objects represented in an exploded perspective view distributed on the disk; And a 2D layout of 3D miniature representations;

Layouts are animated;

Relationships include, but are not limited to, "comprising" relationships; "Used" relationship; "Contacted" relationship; "Incompatible" relationship; And at least two of “conflicting” relationships; And

The method according to the invention further comprises calculating and storing 3D representations of the objects.

The invention also relates to a computer program for implementing the method of the invention.

Hereinafter, with reference to the accompanying drawings, a system for implementing the present invention will be described by way of non-limiting example.

The invention relates to a PLM system, comprising a database for storing objects, preferably 3D objects, and relationships between the objects. The PLM system provides the user with a graphical user interface suitable for displaying graphical representations of the hierarchy of objects stored. The graphical user interface is configured to display objects associated with the selected object when the object displayed by the user is selected. At some level in the hierarchy, the displayed objects are distributed according to their respective weights. The weight of the displayed object depends on its lower number in the hierarchy displayed in the graphical representation. The present invention makes it possible to navigate in a database of a PLM system, which stores highly complex modeled objects through correlated data. Due to the principle of weight dependence described above, the solution also allows users to understand the progress of the solution through organized data that is similar to objects and relationships between them in an easy and intuitive way.

With respect to the databases used in PLM solutions, as known to those skilled in the art, such databases include a set of data as well as relationships between the data in the set. Relationships are often indexed for the purpose of accelerating searches in the database. From a file standpoint, a relational database does not consist of a single file, but rather uses a complex file system that stores various data and relationships. By "a database storing objects", some data in the database is understood to represent modeled objects. Such objects may be one of modeled objects of a product or part, or objects such as a manufacturing process including various steps, resources such as a robot performing the manufacturing steps, and the like. In a PLM solution, a set of data, for example with respect to a modeled object,

Number of parts;

Manufacturing or obtaining information about the product or modeled object;

Reference to drawings or CAD files for products;

Versioning data (history of design iterations, history of release versions); And

Configuration data (which explores the various configurations of the object).

Relationships in a PLM solution significantly include an "is comprised of" relationship, which makes it possible to create a cluster or subassembly of a product.

Relationships also include "is used in" or so-called "where used" relationships that represent all subassemblies in which a given product is used. Relationships may also include "is in contact with" relationships that allow a user to manage contacts between various products in the database. Relationships may include “in clash with” relationships that direct various data to describe objects that overlap or conflict with each other. This can help find design problems. Relationships include partial dependencies, which represent a collision graph when some are made from others, also known as "relational design". Finally, relationships can represent attributes of various data, which are generally attributes in a PLM solution such as, for example, the material from which the object is formed, the origin of the objects (provider, manufacturer, etc.). Can include them.

With respect to the concept of hierarchy, strictly speaking, a hierarchy is like a rooted tree structure, such as each component but not one with one predecessor. However, the term should be understood more flexibly in this specification to include any partially aligned system or tangled hierarchy. A tangled hierarchy is an inheritance graph, for example an object belonging to one or more sets or supersets. Specifically, various user selectable relationships have multiple parents that allow an object to belong to a different set or closed relationship.

1-3 are diagrams of examples of objects, displayed in accordance with embodiments of the present invention.

Referring to FIG. 1, the GUI 100 is suitable for displaying a graphical representation of an object to a user, that is to say from data representing such objects stored in a database. GUI 100 may be more suitable for displaying a graphical representation of a hierarchy of stored objects.

The invention enables the user to navigate in the data representing the object via the GUI by displaying a representation of the data, more preferably a 3D representation. For example, the displayed data can be selected by the user according to various relationships stored in the database.

In this regard, the user can select the first data and the first relationship, for example. This can be accomplished due to the use of a tree that can be displayed in the GUI 100. It is possible for the user to select the first data due to another type of user interface, for example by entering identification information for the first data, selecting the first data in the list, and so on. The relationship can be selected by any kind of user interface, such as a combo-box, icon, special command or right click. Note that this applies to the other types of user selection mentioned below, which are specified if they do not apply.

In response to the selection of the first data and the first relationship, the system displays a representation of the objects via the GUI. In this case, the displayed objects are actual objects represented in the database by the second data associated with the first data according to the first relationship. For this purpose, the system uses the relational properties of the database to select all data from the database related to the first object in the first relationship. When the second data is identified, the modeled objects represented by this second data are displayed.

In the exemplary embodiment proposed in FIG. 1, the user can select, for example, a predetermined first object (not shown in FIG. 1) consisting of a set of cylinders and a “comprising” relationship. In this case, the PLM system will search the database for all data (some or products) that make up the selected first object. As a result, the PLM system displays, via the GUI, second objects 204-210 associated with the first object 200 through the relationship. The first object 200, for example the set of cylinders in the embodiment of FIG. 1 as well as FIGS. 2 and 3, is an illustrated object used for illustrative purposes only. This modeled object includes a second object 204-210 consisting of nested sets of concentric cylinders.

The selection of a relationship, eg, "comprising", may occur possibly from a toolbar provided in GUI 100 (eg from toolbar 140).

Several types of layouts can be shown and user selectable. Embodiments of the layout are now briefly described and will be described in detail with reference to FIGS. 4 to 16. The layout may be an assembled, often 3D representation of the object, which may be called an "in-play" layout. Alternatively, various second objects may be separated in an exploded perspective view, and the layout may be expanded (or exploded) along a predetermined line in a direction that may be selected by the user, which may be "in-line" or "linear". It can be called a layout. The layout may be decomposed along a direction from a given point, for example, the center trajectory of the represented combination or part or the center of the expressed combination or part. This layout facilitates the user to locate and select various second objects. Another possible layout is the miniature layout of the various objects. One uses, for example, the 2D layout of the 3D miniature representation of the object.

With respect to the embodiment of FIG. 1, the second objects 204-210 can be displayed to be distributed on the disk or circle 202 to obtain an "in-disk" or circular layout, which layout is understood by the model. It is useful to facilitate the user's understanding of the perspective view, and also facilitates the selection of additional data. The disc can be seen as a graphical representation of the relationship between the displayed objects. This disk 202 is further linked with objects belonging to the same first level (according to the previously selected object). It is called "level 1".

The layouts, in particular the disk 202, can be animated if necessary. Therefore, when the user changes the layout or selects a predetermined layout, various objects gradually move. For example, portions 204-210 can be rotated with disk 202 around the virtual disk axis. This helps to understand the location of the various objects and to view the objects.

The type of layout displayed to the user may be a preset or selected by the user. One advantageous solution allows the user to set the default type of field of view used in all displays. When a given layout is displayed, it then allows the user to change the default type of layout to another type.

The selection of the layout can be activated, for example, by right-clicking on an object first, a drop-down list appears, and the desired field can be selected from the list.

Preferably, when the relationship and layout are selected by the user, the same layout can be applied by default to this relationship. When selecting a different type of relationship, a different layout can be selected and applied to the selected new relationship.

In addition, the 3D representation of each object (part or product) can be pre-calculated if necessary. This reduces the computation time. At least for the part of the representation that is expected to be used repeatedly in the database, it is possible to pre-calculate the 3D representation. This may be a fact of the 3D representation of the subassembly, for example. This pre-computed representation can calculate the fly and can be stored for access by the system. If a given 3D representation is to be displayed, it will be searched first among the already stored representations, and if there is no representation to be displayed, it will be calculated.

With continued reference to FIG. 1, the illustrated GUI 100 may be a typical CAD-like interface, with standard or standard menu bars 110, 120, as well as bottom or side toolbars 140, 150. Such menu bars and toolbars include a set of user-selectable icons, each icon associated with one or more operations or functions, as known in the art.

Some of these icons 150 are associated with software tools, configured to edit and / or represent the displayed objects. The software tools in question can be grouped in workbenches. Or put, the workbench contains a subset of software tools.

The GUI can further represent various types of graphical tools, such as graphical tool 130, and can be manipulated by a user to facilitate the 3D orientation of object 200.

Components designated by reference numerals 100, 110, 120, 130, 140, 150, 200 are shown in Figs. 2 to 16 and will not be described further with reference to these figures.

2, a user may select one of the displayed second objects 204, 206, and 208 210 and a second relationship. The second relationship may be the same as the first relationship and may be, for example, a default choice. The second relationship may also be different from the first relationship. Thus, while the second user selection may be similar to the first user selection, in the second user selection, the selection may be performed directly on the representation displayed to the user.

In this regard, the user can select the object 210 by, for example, clicking the object with a mouse, passing the object with a mouse pointer, or selecting the appropriate command from a menu bar or pop-up icon. Other selection means can be embodied explicitly.

Thus, the third object associated with the selected second object through the selected second relationship is searched for and identified by the PLM system. Representation 210 of the third object is provided to the user, along the selected layout. Preferably, the layout is by default as before, but this can be changed at any moment by the user.

Reference numeral 210 in FIGS. 1 and 2 is associated with a concentric co-selected second object 210, ie a set of concentric cylinders. However, in FIG. 2, the graphical representation of the selected second object is changed to an exploded view of this object 210 as compared to FIG. 1. More specifically, object 210 may be shown as a superimposed set of concentric cylinders in FIG. 1, while in FIG. 2 it is represented as a set of concentric cylinders distributed on disk 210 or circle 212. Can be. In other words, the representation of the selected second object 210 in FIG. 2 includes its subordinates, that is, the third objects 213, 214, 216, 218, 220.

The disc 212 thus represents a second level (hereinafter referred to as "level 2") in which the selected second object 210 is exploded. Level 2 graphically links to third objects 213, 214, 216, 218, 220 associated with the parent object 210 according to the selected second relationship, ie, including in this embodiment.

More generally, to clarify the situation,

Level 1 at which the selected first object is decomposed from the second object;

Level 2 at which the selected second object is decomposed from the third object;

Etc. are observed.

The objects 204-210 are distributed on a large disk according to each weight and level, with respect to either FIG. 1 or FIG. 2. The weight of the displayed objects 204-210 depends on the number of subordinates of the objects 204-210 in the hierarchy and is displayed in the graphical representation. In particular, in FIG. 1, if no subordinates of objects 204-210 are displayed, the same weight is due to these objects 204-210.

Referring to FIG. 2, upon user selection, the object 210 is represented as a set of its subordinates, and the weight due to the object 210 is determined by the display of the displayed subordinates 213, 214, 216, 218, 220. Depending on the number, it is increased. Thus, more space is provided for the object 210 than the remaining objects 204, 206, 208. As a result, when no child of the remaining objects 204, 206, 208 is displayed in the graphical representation, the remaining objects 204, 206, 208 are less than the weight of the object 210, Redistributed on the large disk 202 according to the same weight.

While the size of the large circle 202 in FIG. 2 is preferably increased compared to FIG. 1, the scale of the cylinder remains the same. If this is perceived as a simple focus on the new representation of the object 210, the distribution of the cylinders 204, 206, 208 keeps changing.

In terms of the next step, the so-called "intermediate disk", the small disk 212, is linked to an object of level 2 and represents the selected second relationship. It is worth pointing out that searching and displaying a third object associated with the selected second object creates a hierarchy between the second object and the first object. In this respect, the intersection of the two disks 202, 212 represents a cue representing the hierarchy of the displayed object 210 and the displayed children 213, 214, 216, 218, 220 in the hierarchy. define. The field of view of FIG. 2 provides the user with an intermediate understanding of the various relationships between the objects displayed. The user benefits from the fact that the selected relationships are graphically represented on the layout displayed to the user.

Turning to FIG. 3, the user may be prompted to select additional objects 220 and relationships, ie, “comprising” in this embodiment. In fact, this relationship need not necessarily be selected when provided by default. Starting from FIG. 2, the selection of the object 220 switches the representation of this object shown in FIG. 3, ie, the “in-disk” clock of the children 224, 226, 228, 230 of the object 220. do. The subordinates, for example the fourth objects, consist of cylinders of different sizes and colors. Again, the sub-objects 224, 226, 228, 230 are aligned on the represented small disk 222 of level 3 and provide similar advantages as described above for level 2 and level 1.

According to the invention, the objects 204, 206, 208 and the objects 213, 214, 216, 218 of level 1 and level 2 are each redistributed according to respective weights which depend on the displayed children. More specifically, objects 213, 214, 216, 218 because object 220 has displayed children, in contrast to objects 213, 214, 216, 218. More space is provided to the object 220. On the other hand, the objects 213, 214, 216, 218 are preferably large disks 212 (compared to the representation of the disk 212 in FIG. 2) due to the large space provided to the object as a whole. Redistributed in the phase.

Similarly, there is more space apart from the object 210 than the objects 204, 206, 208 in the representation of FIG. 3. Preferably, disk 202 is made larger to allow redistribution of objects 204, 206, 208.

If necessary, the scale remains constant for all objects of all levels.

The present invention makes it possible to navigate between correlated data. Due to the dependence of the weight of the object on the displayed children, the solution also allows the user to understand the relationship between the objects easily and intuitively. In the meantime, the user's progress is visible during navigation, allowing the user to maintain an overview on all visited data.

Nevertheless, when the displayed object or level becomes critical, it may be possible to cause a zoom-out of the displayed objects, if necessary. This may be achieved, one of which is automatically triggered based on a user action or various possible parameters such as the displayed level or the number of objects.

For a better understanding of the various relationships, it is also possible to provide for the disk to rotate independently during user action.

In addition, it is also possible to provide that the graphical contents are close to or embedded within the displayed objects, as shown in FIG. 3, to facilitate understanding of the geometric context of the object as well as the geometric relationships between the objects. .

In addition, the user always has a chance to go back by collapsing the levels. The user can, for example, return to the state of FIG. 2 and select the disk 222 or select the "collapse" option (eg a right click displays several options).

4-6 are diagrams of embodiments of exemplary objects, displayed along a linear layout. Referring to this figure, the user generally selects an "in-line" layout so that the user creates an enlarged or exploded layout along a given line. 1 to 3, the same objects 204, 206, 208, 210 of level 1, sub-objects 213, 214, 216, 218, 220 of level 2 and sub-sub-objects of level 3 (224, 226, 228, 230) are displayed continuously, following a similar mechanism. However, in contrast to the "in-disk" layout, various objects are now displayed continuously on lines and strips 202, 212 and 222.

As provided in the embodiments of FIGS. 4, 5 and 6, lines or strips 202, 212 and 222 may be separated graphically, for example due to thin lines or other colors, to indicate level separation. .

7 and 8 are diagrams of embodiments of example objects, displayed according to an “alternative in-line” layout.

When enabling the strip to provide user-oriented, in operation, the user arrives at an alternate “in-line” layout, shown in FIGS. 7 and 8, now discussed. In this way, the first level 1 is represented graphically along a first direction (eg the direction of the strip 202 in FIG. 4) and the second level 2 is perpendicular to the first direction, for example 7. Along the second direction on the strip 212 in. Therefore, the compactness of the displayed objects increases while the user has a clear picture of the relationships between the objects. In third level 2 (FIG. 8), the lower objects can be represented along a third direction that is parallel to the first direction but shifted. Alternate in-line representation allows the user to better understand level separation.

Such alternative "in-line" layouts may be provided in a user selectable, basic layout type, and strips are automatically replaced at each level.

In addition, each object at the same level remains on its strip and its upper strip, as shown, to facilitate understanding of the hierarchy. For example, the object 228 of FIG. 8 is located on the strips 222, 212 and 202, which understand that the object 228 is a part of the object 220 itself, as part of the object 210. Makes things easier.

9-11 are diagrams of embodiments of plane related objects, shown along the “in-disk” layout, seen from above.

With reference to FIG. 9, a user may select, for example, first data associated with a plane (first object) and a “comprising” relationship therein. It uses this type of relationship only for understanding, and those skilled in the art can use other types of relationships as described above. Again, the PLM system provides second data related to the first data via the selected relationship. Graphical representations of the various components are shown. In the embodiment of FIG. 9, the second data represents second objects associated with the plane, which are decomposed on the disk 202, representing the first level (or level 1). These objects are the wall 201, the first room 203, the corridor 204, the passage 205, the bathroom 206, the warehouse 207, the living room 209, and the kitchen 210.

Such "objects" are preferably represented using some perspective to facilitate understanding of the object, even if the layout is viewed from above.

Referring to FIG. 10, a user may select a predetermined second object, eg, kitchen 210, when disassembled at level 2 on second disk 212. Subordinate third objects from the kitchen are, for example, a kitchen counter 220 with a refrigerator or sink equipment. According to FIGS. 1-3, the displayed objects are redistributed according to respective weights that depend on the number of subordinates of the object in the displayed hierarchy. So-called more space is provided to the disassembled kitchen 210 at the same predetermined scale, compared to other objects of level one. In the meantime, the first disk 202 is made large to allow redistribution of other objects, as highlighted above.

Next, referring to FIG. 11, the user selects a special third object, eg, kitchen counter 220, which is disassembled on the new disk 222. For example, the subordinates (fourth objects) comprising the counter top and two sinks 230 shown in FIG. 11 form level three. Object redistribution substantially occurs in the manner described above. Therefore, an advantage as described with reference to FIGS. 1 to 3 is provided here.

12 is a diagram of an embodiment of an object associated with a plane, displayed according to the same layout as in FIGS. 1-3.

In place of "view from above", the user can select the "in-disk" layout of the same perspective as in Figures 1-3. This is an example in FIG. 12 and represents the same components as in FIG. 12.

13-14 are diagrams of embodiments of objects associated with a plane, displayed according to the same layout as FIGS. 4-6.

The user also selects an "in-line" layout, as shown in Figures 13-15, with similar advantages as described with reference to Figures 4-6. 13-15 illustrate the selection of the living room 209, which is an exploded view of this object shown in FIG. 14, and in contrast to the previous selection of the kitchen in FIGS. 9-11, disassembled in FIG. 15, sofa 290. Indicates the selection.

FIG. 16 is a diagram of an embodiment of an object associated with a plane, displayed along the same layout as FIGS. 7 to 8.

Referring to this figure, the user may also choose to create or select an alternate "in-line" layout to benefit from each of the advantages described with reference to FIGS. 7 and 8.

With respect to embodiments of plane-related objects, it can be understood how powerfully the data can query the various relationships stored in the PLM database. The user may select, for example, "provided from" or "manufactured from" to clearly sense where the object can be obtained from.

In this regard, when various possible relationships between objects make it difficult for the user to understand the relationship, the present invention of the user is able to navigate in a method constructed between non-direct relationships.

For example, the present invention, in which the object is displayed by the GUI, renders the perspective effect more efficiently by giving a larger size to the last displayed object than the first displayed object, depending on the weight of each rendering size. It will also be possible to have

According to an embodiment of the present invention, the weight of the displayed object depends on the size of the lower of the object in the hierarchy, which is displayed in the graphical representation.

In another embodiment, the graphical user interface is configured to morph from a first representation of the displayed object to a representation of objects associated with the displayed object when the display object is selected by the user.

In another embodiment, the number of objects displayed in the level is user adjustable, that is to say, not all objects need to be displayed. For example, this happens if the object contains many children depending on the selected relationship.

Thus, in one embodiment of the present invention, means are provided for hiding some objects of the same level. For example, a graphic object with a tunnel structure can be displayed across a strip or disk representing a level and hidden objects can be displayed when the user moves the strip along a transformation or rotates the disk around its axis. , appear.

The presence of the graphical means allows the user to know whether there are more objects in the level than the low display.

In addition, the present invention can be performed by adding to an existing database system such as a PLM solution. Possible implementations of the invention are now disclosed with reference to FIGS. 17-20.

17 is a schematic diagram of a software architecture suitable for carrying out the present invention, showing a single client, database server 560 and vault server. The client includes a navigation engine 500, which manages the user interface and controls parts 520, 580, and 640. The navigation engine allows the user to select an object, a relationship, possibly a layout or a type of clock that displays the object. In addition, the navigation engine may provide a general type of query that is possible in a PLM system.

17 also shows query engine 520, database client 540, and database server 560. The query engine 520 is controlled by the navigation engine 500, relying on the user's instructions to create a database statement and pass the statement to the database client 540. The query engine 520 also manages the quality results received from the database client 540.

Database client 540 is configured to manage database server connections. The database client receives the query from the query engine 520 and passes the query to the database server 560. The database client receives the query results from the database server 560 and passes these results to the query engine 520.

Database server 560 receives inquiries from various database clients, such as client 540, and provides these inquiries. Database servers are typically relational databases and are implemented using solutions available from IBM or Oracle under reference DB2. The database may also be an object or XML database, or an application server that accesses the database. The application server may also provide processing to enhanced queries (proximity queries, spatial queries ...) for enhanced queries (on-fly or asynchronously).

Apart from the added graphical navigation functionality available to the user in the navigation engine 500, the components 520, 540 and 560 need not differ from the same conventional relational database used in the PLM solution. Therefore, these components are not described in more detail.

17 also shows a vault server 620 that stores and provides representations of objects included in the database, that is, the vault server is used as a representation store. Vault server 620 may be a file server, and representations may be stored in various files. For example, using a database server, using a "blob" (binary language object) store, can also be implemented. Proxy and / or cache techniques may be used. Representations of objects stored in the vault server can exist in a variety of formats, such as bounding-boxes, polygons, bitmaps, images, vector images, subdivision surfaces, or any of the more commonly known formats. As discussed below, it is advantageous to store various formats at the vault server to allow increased loading of representations.

The vault server is addressed by the vault client 600. The vault client allows the client to address the vault server to find a representation of the object. 17 also shows a representation loader 580. Representation loader 580 queries vault server 620 via vault client 600 to obtain a representation of the object to be displayed to the user. Representation loader 580 also manages the loading of representation increments when receiving representations from vault client 600.

A visualization engine 640 manages the representation display to the user. The visualization engine, in most cases, addresses display driver 660, which manages display hardware-graphics card. For the purpose of displaying representations on display hardware, you can use hardware accelerated via OpenGL drivers or using Microsoft Direct 3D or DirectX.

18 is a flow chart of a process for making a display in accordance with the present invention. The process uses the software structure represented in FIG. In steps 700-780, in response to the selection of the first data and the first relationship, the system displays a 3D representation of the object. In step 800, the user selects objects and relationships. Then, as shown, the process of FIG. 18 loops to step 720 to create a new clock that is displayed to the user.

More specifically, in step 700, a query is made and the layout type is selected. This can be done as described above. Selection of the query and layout is allowed by the user interface of the navigation engine 500 of FIG. The layout type is one of various types of watches illustrated with reference to FIGS.

In step 720, the database is queried to obtain the attributes of the objects that match the query made in step 700. In the structure of FIG. 17, this step will be performed by the navigation engine 500, the query engine 520, the database client 540, and the database server 560. As a result of step 720, attributes of a set of objects needed to be displayed are provided.

In step 740, the vault server needs to be queried and displayed to obtain various representations of the object. In the structure of FIG. 17, this step will be performed by the navigation engine 500, the representation loader 580, the vault client 600, and the vault server 620. As a result of step 740, in the selection layout, a set of representations are provided that correspond to the various objects to be displayed.

In step 760, the representation is published in 3D space, according to the information retrieved from the database server and the selected layout. In the structure of FIG. 17, this may be performed by the navigation engine 500 and the visualization engine 640. The published representations are displayed to the user at step 780 due to the display driver 660.

The process then loops through steps 740, 760, and 780, from a small and inferior format to a large and good format, to incrementally load the representations. For example, a process may first load the object's bounding-box representation before loading the object's polygon representations. The process also streams the representation. This makes it possible to give the user an almost intermediate representation of the object, and even though this representation may have a somewhat inferior quality first, the representation improves over time. The user can eventually be provided with a more complete representation of high quality without having to wait for a long period of time for this representation. The process can load the representation as a background task, using multi-threading or asynchronous inputs / outputs. This solution makes it possible to give high priority to database queries, so navigation in the database does not hide the user's work in the database.

The loop through steps 740, 760 and 780 can be stopped when the best and better representation is loaded and displayed to the user.

Alternatively, the loop through these steps may be stopped when the user selects one of the displayed objects and the relationship, which step is represented in FIG. 18 under 800. The process then loops back to step 720, and the database is queried again.

The process of FIG. 18 and the structure of FIG. 17 use a vault server and representations of various pre-computed data are stored.

11 and 12 are schematic diagrams of client and network hardware architecture, configured to carry out the present invention. 19 shows a client workstation. The workstation includes a central processing unit 900, a random access memory 920, and a workstation internal communication bus 940 that allows access to the random access memory. The workstation is further provided with a graphics processing unit 960, having a video random access memory 980 associated therewith. Disk controller 1000 manages access to mass memory devices, such as hard drive 1020. The network adapter 1040 manages access to the network 1060.

In operation, the various client components of FIG. 17 are processes performed in the CPU 900. The network adapter 1040 is used by the vault client 600 to access the vault server 620 on the network 1060, and by the database client 540 to access the database server 560 on the network 1060. Additionally used. Disk controller 1000 may be used by the vault client to form a cache that is represented on local mass memory device 1020, which improves the performance of frequently used representations. Display driver 660 feeds video RAM 980 with a layout of representations, which are displayed due to GPU 960.

The query engine 520 queries and stores the result in the RAM 920. Representation loader 580 processes and stores the operating format of the representation in RAM 920. The stored representation is used by the display driver 660 and transmitted to the display driver 660 as described with reference to step 960.

FIG. 20 is a schematic diagram of a network structure configured to carry out the present invention, wherein the structure of FIG. 20 is due to a common vault server that provides a database of accessible representations, and due to a common database server, for various users. Is configured to navigate. In the embodiment of FIG. 20, two local area networks 1100 and 1120 are connected to a wide area network 1140. 20 illustrates a database 1160 and a master vault 1180, which are represented in the WAN 1140 to be accessed from the LANs 1100 and 1120. The first LAN 1100 includes two clients 1200 and 1220 as well as a proxy vault 1240. Second LAN 1120 also includes two clients 1260 and 1280 and proxy vault 1300. Master vault 1180 is replicated in each proxy vault 1240, 1300 to optimize WAN widespread use.

In operation, clients in one of the LANs 1100 and 1120 access the database 1160 via the WAN 1140. In the first LAN 1100, the clients 1200 and 1220 access the proxy vault 1240 to have a representation, and the clients 1260 and 11280 in the second LAN 1120 have a representation. Access bolt 1300. This exemplary operation assumes that a query to the database 1160, which is most text queries as described above with reference to the PLM solution, can be provided to the WAN. Thus, the WAN has sufficient bandwidth to provide requests to the database 1160. Database 1160 can be updated by any client, and the solution of FIG. 20 is simpler than managing data updates at various database proxies. The operation of FIG. 20 optimizes WAN widespread use by replicating vault server 1180 to proxy vaults 1240 and 1300. This is advantageous because the representation of the data will generally have a larger size than the database information, and in addition, the representation does not need to be pre-computed and updated in contrast to the database information.

The invention is not limited to the preferred embodiments described with reference to the drawings. Remarkably, the words "first," "second," and "third" data or relationships are used for clarity of description and do not represent any actual capability of the data and relationships.

In Figures 1 to 16, a diagram of an embodiment is provided. One of them uses another embodiment of the layout. 17, 19 and 20 suggest a preferred structure, one of which also uses another software or hardware solution.

Improved navigation allows users to navigate in a database of product lifecycle management systems that store highly complex modeled objects through correlated data. The present invention allows a user to locate and display an object in a user-friendly, easy and intuitive manner.

Claims (16)

As a product lifecycle management system, A database for storing modeled objects and relationships between the objects; And A graphical user interface suitable for displaying a graphical representation of a hierarchy of stored objects to a user, The graphical user interface is configured to display objects related to the selected object, in accordance with the selection of the object displayed by the user, The displayed objects are distributed according to their weights at predetermined levels in the hierarchy, The weight of the displayed object is dependent on the number of descendants of the object of the hierarchy displayed in the graphical representation. The method of claim 1, And the graphical user interface is configured to display a hierarchy of displayed objects and a graphical cue representation of the subordinate of the objects of the hierarchy that are displayed in the graphical representation. The method according to claim 1 or 2, And the displayed objects have a rendering size depending on their respective weights. The method according to any one of claims 1 to 3, Wherein the weight of the displayed object depends on the size of the descendants of the object of the hierarchy displayed in the graphical representation. The method according to any one of claims 1 to 4, The graphical user interface is configured to display the objects using a unique scale for all objects. The method according to any one of claims 1 to 5, The graphical user interface is configured to display a 3D representation of objects. The method according to any one of claims 1 to 6, And the graphical user interface is configured to morph from a first representation of the displayed object to a representation of objects associated with the displayed object, in accordance with the selection of the displayed object by the user. In a database of a product life cycle management system (PLM), the database includes a graphical user interface suitable for storing modeled objects and relationships between the objects and for displaying a graphical representation of the hierarchy of stored objects to a user. As a way to navigate, Selecting a first object and a first relationship; Searching for descendants of the first object in the hierarchy, the descendants comprising second objects associated with the first object according to the first relationship; Displaying a representation of the first object including the second objects; Selecting a second relationship and one of the displayed second objects; Searching for subordinates of the selected second object, the subordinates comprising, through the second relationship, third objects associated with the selected second object; And Displaying a representation of the first object, including the second and third objects, The displayed objects are distributed according to their respective weights, and the weights of the objects depend on the number of subordinates of the object in the hierarchy displayed in the graphical representation. The method of claim 8, The objects are displayed as 3D objects. The method according to claim 8 or 9, Selecting the first object and the first relationship includes selecting a first layout, wherein the representation of second objects is a representation in the first layout. The method according to any one of claims 8 to 10, Selecting one of the displayed objects and a second relationship comprises selecting a second layout, wherein the representation of third objects is a representation in the second layout. . The method of claim 10 or 11, The layout is, A linear layout having objects represented in exploded perspective views along lines; In-place layout; A circular layout having objects represented in exploded perspective views distributed on the disk; And The 2D layout of 3D miniature representations. The method according to any one of claims 10 to 12, And the layouts are animated. The method according to any one of claims 9 to 13, The relationships are "Comprising" relationship; "Used" relationship; "Contacted" relationship; "Incompatible" relationship; And At least two of the “conflicting” relationships. The method according to any one of claims 9 to 14, Calculating and storing 3D representations of the objects. A computer program implementing the method of any one of claims 9-15.

Images