CA2344638A1 - Multi-dimensional data management system - Google Patents
Multi-dimensional data management system Download PDFInfo
- Publication number
- CA2344638A1 CA2344638A1 CA002344638A CA2344638A CA2344638A1 CA 2344638 A1 CA2344638 A1 CA 2344638A1 CA 002344638 A CA002344638 A CA 002344638A CA 2344638 A CA2344638 A CA 2344638A CA 2344638 A1 CA2344638 A1 CA 2344638A1
- Authority
- CA
- Canada
- Prior art keywords
- user
- data
- classes
- properties
- database system
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Abandoned
Links
- 238000013523 data management Methods 0.000 title description 2
- 238000007726 management method Methods 0.000 description 20
- 238000004519 manufacturing process Methods 0.000 description 7
- 230000008520 organization Effects 0.000 description 7
- 238000000034 method Methods 0.000 description 5
- 230000008569 process Effects 0.000 description 5
- 238000010586 diagram Methods 0.000 description 4
- 238000007596 consolidation process Methods 0.000 description 3
- 230000004044 response Effects 0.000 description 3
- 230000008901 benefit Effects 0.000 description 2
- 230000001149 cognitive effect Effects 0.000 description 2
- 238000004458 analytical method Methods 0.000 description 1
- 230000007246 mechanism Effects 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/28—Databases characterised by their database models, e.g. relational or object models
- G06F16/283—Multi-dimensional databases or data warehouses, e.g. MOLAP or ROLAP
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y10—TECHNICAL SUBJECTS COVERED BY FORMER USPC
- Y10S—TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y10S707/00—Data processing: database and file management or data structures
- Y10S707/953—Organization of data
- Y10S707/954—Relational
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y10—TECHNICAL SUBJECTS COVERED BY FORMER USPC
- Y10S—TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y10S707/00—Data processing: database and file management or data structures
- Y10S707/953—Organization of data
- Y10S707/955—Object-oriented
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y10—TECHNICAL SUBJECTS COVERED BY FORMER USPC
- Y10S—TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y10S707/00—Data processing: database and file management or data structures
- Y10S707/953—Organization of data
- Y10S707/956—Hierarchical
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y10—TECHNICAL SUBJECTS COVERED BY FORMER USPC
- Y10S—TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y10S707/00—Data processing: database and file management or data structures
- Y10S707/99931—Database or file accessing
- Y10S707/99932—Access augmentation or optimizing
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y10—TECHNICAL SUBJECTS COVERED BY FORMER USPC
- Y10S—TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y10S707/00—Data processing: database and file management or data structures
- Y10S707/99931—Database or file accessing
- Y10S707/99933—Query processing, i.e. searching
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y10—TECHNICAL SUBJECTS COVERED BY FORMER USPC
- Y10S—TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y10S707/00—Data processing: database and file management or data structures
- Y10S707/99931—Database or file accessing
- Y10S707/99933—Query processing, i.e. searching
- Y10S707/99934—Query formulation, input preparation, or translation
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y10—TECHNICAL SUBJECTS COVERED BY FORMER USPC
- Y10S—TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y10S707/00—Data processing: database and file management or data structures
- Y10S707/99941—Database schema or data structure
- Y10S707/99944—Object-oriented database structure
Abstract
Multi-dimensional data is organized into classes which correspond to each of the dimensions that characterize the data. All relevant data is consolidated into a fact table (30), which is based upon information of interest. The dat a within this table is linked to the top level of each class that corresponds to a different dimension of data, and subclasses which exist within a given dimension of class automatically inherit the linked reference to the consolidated data. A user can thereby select search criteria (32) within particular classes that correspond to the dimensions of interest. This searc h criteria is then used to form a query which is applied to a relational database, to obtain the desired results.
Description
M(TLTI-DllVIENSIONAL DATA MANAGEMENT SYSTEM
This disclosure is based upon, and claims priority from, provisional U. S.
patent application No. 60!102,463, the contents of which are incorporated herein by reference.
Field of the Invention The present invention is directed to the; management of large amounts of data, sometimes referred to as "data warehou:cing", and more particularly to the management of data in a manner which permits a user to examine the data across multiple dimensions, and thereby gain more insight into information represented by the data.
Background of the Invention In many different business environments, database systems are used to manage various types of information which relate to the businesses. For relatively modest amounts of information, a number of suitable database systems are available. However, as the volume of information increases, the ability of the user to construct a request for certain types of information, and to obtain meaningful results from such a request, becomes more difficult. This difficulty is due, at least in part, to the fact that the data itself becomes more complex, and therefore presents a variety of different perspectives from which a search for specific information can be formulated. As a result, specialized types of database systems have been developed for situations in which large volumes of highly varied data are encountered, to facilitate the user's ability to manage and access that data. For instance, a relational database management system stores different aspects of data in different respective tables, which are linked to one another by common attributes. When a user enters a query, pertinent data is extracted from the various tables to provide a response.
WO 00!19340 PCT/US99/226?4 One example of a situation that presents highly complex data access requirements is the field of manufacturing connponent and supplier management.
For a large manufacturing organization that may have several sites that produce a variety of products, the number of individual components that are used in those products may number in the thousands or even millions. Depending upon the nature of the component, many different parameters may be used to identify it and describe its source and characteristics. Becau se of the large amount of data, and the various manners in which it can be interlin~ked, a relational database may prove to be too cumbersome to use in this situation, since the layout of the data in the tables may no longer be intuitive to the user, and therefore makes it difficult to construct meaningful queries. To provide the user with the ability to regularly manage the large volumes of information presented in this type of situation, a database management system which integrates the advantages of relational databases and object-oriented databases has been found to be quite effective.
An example of such a database system, which is referred to as an object/relational database system, is described in application Serial No. 08/951,714, bled October 16, 1997.
An object/relational database management system of the type described in this application provides the user with the abiliity to organize the data in a cognitive manner, by creating a hierarchical object model. This object model is linked to a relational database in a manner which enables the user to present queries to the database in the context of an organizational structure that is understood by the user. Thus, in the example of a component and supplier management system of the type described above, a product engineer can readily obtain information about a component that is provided by a variety of different suppliers, and compare and contrast various pieces of this information to identify the particular item which best suits the needs o~f a given product.
This disclosure is based upon, and claims priority from, provisional U. S.
patent application No. 60!102,463, the contents of which are incorporated herein by reference.
Field of the Invention The present invention is directed to the; management of large amounts of data, sometimes referred to as "data warehou:cing", and more particularly to the management of data in a manner which permits a user to examine the data across multiple dimensions, and thereby gain more insight into information represented by the data.
Background of the Invention In many different business environments, database systems are used to manage various types of information which relate to the businesses. For relatively modest amounts of information, a number of suitable database systems are available. However, as the volume of information increases, the ability of the user to construct a request for certain types of information, and to obtain meaningful results from such a request, becomes more difficult. This difficulty is due, at least in part, to the fact that the data itself becomes more complex, and therefore presents a variety of different perspectives from which a search for specific information can be formulated. As a result, specialized types of database systems have been developed for situations in which large volumes of highly varied data are encountered, to facilitate the user's ability to manage and access that data. For instance, a relational database management system stores different aspects of data in different respective tables, which are linked to one another by common attributes. When a user enters a query, pertinent data is extracted from the various tables to provide a response.
WO 00!19340 PCT/US99/226?4 One example of a situation that presents highly complex data access requirements is the field of manufacturing connponent and supplier management.
For a large manufacturing organization that may have several sites that produce a variety of products, the number of individual components that are used in those products may number in the thousands or even millions. Depending upon the nature of the component, many different parameters may be used to identify it and describe its source and characteristics. Becau se of the large amount of data, and the various manners in which it can be interlin~ked, a relational database may prove to be too cumbersome to use in this situation, since the layout of the data in the tables may no longer be intuitive to the user, and therefore makes it difficult to construct meaningful queries. To provide the user with the ability to regularly manage the large volumes of information presented in this type of situation, a database management system which integrates the advantages of relational databases and object-oriented databases has been found to be quite effective.
An example of such a database system, which is referred to as an object/relational database system, is described in application Serial No. 08/951,714, bled October 16, 1997.
An object/relational database management system of the type described in this application provides the user with the abiliity to organize the data in a cognitive manner, by creating a hierarchical object model. This object model is linked to a relational database in a manner which enables the user to present queries to the database in the context of an organizational structure that is understood by the user. Thus, in the example of a component and supplier management system of the type described above, a product engineer can readily obtain information about a component that is provided by a variety of different suppliers, and compare and contrast various pieces of this information to identify the particular item which best suits the needs o~f a given product.
It is desirable to improve upon the capabilities provided by an object/relational database management system, in a manner which enables the user to access the data in a mufti-dimensional manner. For instance, a financial manager may want to know which commodities were most used in a particular S financial quarter across all manufacturing sites, and compare that information to a previous quarter or a particular site. A purchasing officer may desire to know the price that was paid for a particular component: at the respective sites, to identify discrepancies. These types of information require the data to be searched in multiple dimensions, i.e. by time, manufacturing site and commodity. In the past, a star-schema approach has been employed to provide this type of multi-dimensional search capability in a relational database system. In general, the star schema comprises a single fact table and a number of dimension tables that respectively correspond to each of the dimensions of the data, e.g. time, site, product. The dimension tables describe the attributes of that dimension, e.g.
the attributes of the time dimension might comprise date, month, quarter and year.
The fact table contains a reference, or key, to each dimension table, as well as the detailed data that can be aggregated in a query, e.g. dollar cost for a given component at a given site on a particular date.
The star schema organizes the data in a flat, or non-hierarchical, manner, which makes it difficult to construct queries. More particularly, a query has to address the fact table and the dimension tables. This approach requires a significant programming effort, both to initially create the star schema as well as to subsequently maintain it. Furthermore, because of the programming effort required to link the various tables of the database in a manner that is necessary to obtain the desired results, it is not readily extensible to accommodate new types of data. Consequently, the ability to conduct mufti-dimensional searches is quite limited, because of the special knowledge it requires.
the attributes of the time dimension might comprise date, month, quarter and year.
The fact table contains a reference, or key, to each dimension table, as well as the detailed data that can be aggregated in a query, e.g. dollar cost for a given component at a given site on a particular date.
The star schema organizes the data in a flat, or non-hierarchical, manner, which makes it difficult to construct queries. More particularly, a query has to address the fact table and the dimension tables. This approach requires a significant programming effort, both to initially create the star schema as well as to subsequently maintain it. Furthermore, because of the programming effort required to link the various tables of the database in a manner that is necessary to obtain the desired results, it is not readily extensible to accommodate new types of data. Consequently, the ability to conduct mufti-dimensional searches is quite limited, because of the special knowledge it requires.
It is further desirable, therefore, to provide a objectlrelational database management system in which mufti-dimensional searches can be easily constructed by the user in a dynamic manner, and which is readily extensible, without requiring any significant programming, or the like.
Summary of the Invention In accordance with the present invention, the foregoing objectives are achieved in an object/relational database management system by organizing the data into hierarchical classes which correspond to each of the dimensions that might be used to characterize the data. All relevant data is consolidated into a fact table, which is based upon transactional information of interest. The data within this table is linked to the top level of each class that corresponds to a different dimension of data. All subclasses which exist within a given dimensional class automatically inherit the linked reference to the consolidated data. As a result, the user is only required to select search criteria within particular classes that correspond to the dimensions of interest. This search criteria is then used to form a query which is applied to a relational database, to obtain the desired results.
A further feature of the invention resides in the user interface by which information about the data is accessed. The user interface displays the hierarchical organization of the dimensional classes and their respective subclasses, to thereby provide the user with an indication of possible areas of inquiry. For any given subclass, the user interface displays properties associated with that subclass, that can be used to specify search criteria. These I>roperties can be limited to only those which are specific to a particular subclass, or include those which are inherited from parent classes and subclasses as. well.
By virtue of these features, the present invention provides an object/relational database management system that enables a user to present inquiries and analyze data in a truly mufti-dimensional manner that is inherently intuitive to the user, based upon the hierarchical organization of the classes.
Further features of the invention, and the adv~untages attained thereby, are described hereinafter with reference to specific embodiments illustrated in the accompanying drawings.
Brief D,~scription of the Drawings Figure 1 is a general overview of the architecture of an object/reiational database management system;
Figure 2 is a perspective illustration of mufti-dimensional arrangement of data;
Figure 3 is a block diagram illustrating the process for the consolidation of data;
Figure 4 is a block diagram illustration of the objects and levels for a four-dimensional data representation;
Figure 5 is a block diagram illustrating the relationship of the consolidated fact table to the dimensional objects; and Figures 6-8 illustrate examples of a user interface for constructing searches in accordance with the present invention.
Detailed De~~ri t~n_ To facilitate an understanding of the principles which underlie the present invention, it is described hereinafter with reference to a specific embodiment that relates to component and supplier process management. It will be appreciated that the practical applications of the invention are not limited to this particular example. Rather, the fundamental principles of the invention can be used in all types of database applications in which it is desirable to organize and present business information in a manner that can be used to support the interests of the business.
_5_ The present invention operates within the context of an objectlrelational database management system. As a background to a discussion of the features of the invention, a brief overview of an objectlrelational database management system is first provided. For more detailed information about such a system, reference is made to Application Serial No. 08/951,714, filed October 16, 1997, the disclosure of which is incorporated herein by reference.
Referring to Figure l, the general architecture of an object/relational database management system is illustrated. In such a system, an object database is created by the user, and provides a conceptual overview of the data. The 10 database 10 comprises a set of classes, each of which includes searchable properties. The classes form a hierarchy, in which each class that is derived from a base class inherits all of the searchable properties of that base class. The derived class may have additional searchable properties :as well as those which are inherited.
The classes, objects and relationships between classes in the user's object database 10 are modeled in a meta-model 12. T'he mesa-model is an object/relational representation, comprising a set of classes, objects and relationships which model the application object-relational model of the user object database. The user can create, edit and manipullate both the application objects in the database and the application object-relational model by means of a suitable user interface 14.
The meta-model 12 has a corresponding set of relational database structures 16, which are capable of being manipulated by a conventional relational database engine I8. Preferably, each class in the user's object database 10 is modeled by a table in the relational database 16. Each searchable property of a class is modeled by a column in the associated table, and each object of a class is modeled by a row in the table. A relationship between two objects is modeled by a pointer from one row to another row within the table.
Once the object database and corresponding meta-model and relational database have been created, the user can conduct searches on the data by means of the interface 14. Within the interface, the user selects one or more classes to be searched, restrictions on searchable properties of objects in those classes, and information to be presented for the objects. In response to this input, a relational database query 20 is generated. This query is presented to the search engine i8, which retrieves information from the relational database 16 and presents it to the user according to the properties of the classes which were searched.
Within the context of such an object/relational database management system, the present invention provides the user with the ability to easily manipulate and access data across multiple dinnensions. The concept of multi-dimensional data is depicted in Figure 2 in connection with an example that relates to component management in a manufacturing organization. In this particular example, the data relating to components is organized along three dimensions, namely by time, manufacturing site, and individual component, or item. In this particular example, the time dimension has three levels of granularity, i.e.
months, fiscal quarters and years. A cost value, represented by the dollar sign, is associated with each combination of values for the three dimensions.
The organization of the data in a multi-dimensional fashion, as depicted in Figure 2, provides the user with the ability to perform various types of analysis.
For example, a financial officer can compare the cost for a given component over a particular quarter between various sites, or locate the components which had the highest costs across all sites during a particular time period.
To provide the user with the ability to ;analyze data in a multi-dimensional format, the data first undergoes a consolidation process. This process is depicted in the block diagram of Figure 3. Referring thereto, transaction files 22 containing data that is of interest to the user are first provided to a staging area 24, where the files are parsed to extract the relevant data. The transaction files 22 can represent any type of information that is relevant to the data to be managed.
For example, in a component and supplier management system, purchase orders constitute one type of transaction file that contains data relating to the individual components of interest. Within the staging area 24, the information extracted from the individual files is placed into tables, preferably tables of the type which are associated with a relational database system. From these tables, the information is first grouped into sub-granular .data 26. One example of the grouping of information into sub-granular data is to consolidate the data by individual days. Thus, fox the example depicted in Figure 2, the data for all purchase orders of a given date is grouped in accordance with manufacturing site and purchased item.
At the next stage of the process, the sub-granular data is further consolidated into granular data 28. Again referring to the example of Figure 2, the lowest level of granularity along the time dimension is by month.
Therefore, in this step of the process, the data for each of the days of a given month is consolidated into a single cost figure for each site and item. The final step in the consolidation process comprises the generation of a fact table 30; which stores the data in a form that can be searched by a relational database search engine.
In addition to being consolidated into granular data, the sub-granular data 26 can also be employed for various purposes that the user may desire. For instance, a file 32 containing some or all of the sub-granular data can be supplied to the user's accounting system to generate daily cost reports, or the like.
In the user object model for the objectlrelational database system, each dimension of the data is associated with a different class. Figure 4 illustrates an example of a four-dimensional classlsubclass hierarchy. In this example, the four dimensions are associated with the base classes for commodity, organization, supplier and time. Each of these base classes may have one or more searchable properties. Each base class also has one or more subclasses, which inherit the _g_ searchable properties of their parent classes, and may have additional searchable properties which are specific to them.
The data in the fact table 30 is linked to the classes of the hierarchy.
Figure 5 illustrates an example of a relatively simple fact table 30 containing multiple columns of information. Various ones of these columns are linked to the top level, or base class 34, for each dimension. Due to the inheritance property of the classes, each of the subclasses 36-40 below a base class automatically inherits this linking as well. As a result, users can construct searches on the basis of properties associated with any of the various classes and subclasses within the hierarchy.
With reference back to the objectlrelational database system of Figure 1, each class 34 and subclass 36-40 of the dimensional hierarchy maps into a respective table in the relational database 16. The properties of a class map into the fields of its respective table. More specifically, each instance of the class comprises one row of the table. In the case of a subclass, only its unique, i.e.
non-inherited properties, appear in the row of its table, since the higher-level, inherited properties already appear in another row. The search engine contains information about the structure of the classes and tables, and is thereby able to locate the rows in the tables which return the desired results. By means of this arrangement, therefore, the user is able to relate to the data in terms of classes and instances of classes, rather than as rows in tabaes.
As an enhancement, all of the possible mufti-dimensional queries that can be envisaged are precomputed from the data, <~nd the results of each are loaded into the fact table 30 as individual rows. Thereafter, whenever a query is entered, the data from the appropriate row is retrieved, to provide the results more quickly.
Figures 6-8 illustrate examples of a user interface that can be employed in.
the context of the present invention to construct searches. This particular user interface comprises a search navigator that consists of two primary window panes.
-g_ WO 00/1.9340 PCTNS99/22674 The left pane 34 illustrates the classes and subclasses of the hierarchy, along with their relationships. In the example of Figure 6, the user has selected the base class entitled "Available Inventory" . This base class has two dimensions associated with it, which are represented by the subclasses labeled "Commodity" and "Organization" . The various levels associated. with each of these dimensions are depicted under their respective subclasses.
Figures 7 and 8 illustrate an example in which the user has selected a different base class, in this case "Cost History". As can be seen in the left window pane 34, this class has four dimensions associated with it, which correspond to the example of Figure 5. The first two dimensions are the same as those appearing in the "Available Inventory" class depicted in Figure 6. Two additional dimensions, labeled "Supplier" and "Time", are also present for this class of information.
The right window pane 36 of the user interface identifies the searchable parameters that are associated with a particular class or dimension level.
These parameters can be limited to only those which are specific to a chosen subclass, or include those which are inherited from parent classes and subclasses as well.
A
number of tabs 38 are displayed at the top of the window pane. The left tab corresponds to the base class, and the remaining tabs relate to levels in each of the four dimensions which have been chosen by the user. In the example of Figure 6, the tab associated with the base class "Available Inventory" has been selected.
This base class has one searchable parameter, labeled "Value", associated with it.
A search window 40 is provided for the user to enter a parameter value for the search. In addition, the window pane includes a button 42 associated with the parameter. By selecting this button, the user is presented with a list of all of the available values that could be entered in the search window 40 as one of the search criteria.
WO 00/19340 PCTIUS99I22b74 In the example of Figure 7, the user has selected the tab for the level "Ordered Part Number" . In this case, a number of search windows 40 are displayed, for each of the searchable properties associated with that dimension level. The user can enter values into any one or more of the search windows, to refine the search criteria. In the example of Figure 8, the user has switched to the "Month" tab within the same base class. Consequently, the search windows 40 appearing in the right pane correspond to the two searchable parameters for that level, i. e. "Month" and "Year" .
Once the user has entered criteria into any one or more of the search windows 40, a "Search" button 44 is selected. In response, the parameter values entered by the user are presented to the search engine for the relational database.
This engine reads the structure of the user object model, and constructs a query to identify all of the data which matches the search criteria. This query is based upon the cascaded search mechanism described in detail in the previously cited Application Serial No. 08/951,714, which enables a search to be conducted across all classes in a relational manner. For further information regarding this aspect of the system, the reader is referred to that disclosure.
From the foregoing, it can be seen that the present invention provides a database management system which permits the user to access data across multiple dimensions. The dimensions are respectively associated with different classes, and the various levels within a dimension have corresponding subclasses. The classes and subclasses are displayed to the user in a hierarchical manner. This representation is more cognitive to the user, since it corresponds to the manner in which the data is intuitively organized, so that the user's ability to construct a search is facilitated. By selecting the various tabs in the user interface window, it is possible for the user to identify all of the various properties of a subclass, including those which are inherited from parent classes, that are available fox searching. As a result, searches can be automatically configured, and reports generated, in a dynamic manner, without requiring extensive programming efforts.
As a further advantage, the system is easily created and maintained, and is completely extensible so that additional dimensions can be used to access data, by creating further classes to define the dimensions.
It will be appreciated by those of ordinary skill in the art that the present invention can be embodied in other specific forms without departing from the spirit or essential characteristics thereof. The presently disclosed embodiments are therefore considered in all respects to be illustrative, and not restrictive.
The scope of the invention is indicated by the appended claims, rather than the IO foregoing description, and all changes that come within the meaning and range of equivalents thereof are intended to be embraced therein.
Summary of the Invention In accordance with the present invention, the foregoing objectives are achieved in an object/relational database management system by organizing the data into hierarchical classes which correspond to each of the dimensions that might be used to characterize the data. All relevant data is consolidated into a fact table, which is based upon transactional information of interest. The data within this table is linked to the top level of each class that corresponds to a different dimension of data. All subclasses which exist within a given dimensional class automatically inherit the linked reference to the consolidated data. As a result, the user is only required to select search criteria within particular classes that correspond to the dimensions of interest. This search criteria is then used to form a query which is applied to a relational database, to obtain the desired results.
A further feature of the invention resides in the user interface by which information about the data is accessed. The user interface displays the hierarchical organization of the dimensional classes and their respective subclasses, to thereby provide the user with an indication of possible areas of inquiry. For any given subclass, the user interface displays properties associated with that subclass, that can be used to specify search criteria. These I>roperties can be limited to only those which are specific to a particular subclass, or include those which are inherited from parent classes and subclasses as. well.
By virtue of these features, the present invention provides an object/relational database management system that enables a user to present inquiries and analyze data in a truly mufti-dimensional manner that is inherently intuitive to the user, based upon the hierarchical organization of the classes.
Further features of the invention, and the adv~untages attained thereby, are described hereinafter with reference to specific embodiments illustrated in the accompanying drawings.
Brief D,~scription of the Drawings Figure 1 is a general overview of the architecture of an object/reiational database management system;
Figure 2 is a perspective illustration of mufti-dimensional arrangement of data;
Figure 3 is a block diagram illustrating the process for the consolidation of data;
Figure 4 is a block diagram illustration of the objects and levels for a four-dimensional data representation;
Figure 5 is a block diagram illustrating the relationship of the consolidated fact table to the dimensional objects; and Figures 6-8 illustrate examples of a user interface for constructing searches in accordance with the present invention.
Detailed De~~ri t~n_ To facilitate an understanding of the principles which underlie the present invention, it is described hereinafter with reference to a specific embodiment that relates to component and supplier process management. It will be appreciated that the practical applications of the invention are not limited to this particular example. Rather, the fundamental principles of the invention can be used in all types of database applications in which it is desirable to organize and present business information in a manner that can be used to support the interests of the business.
_5_ The present invention operates within the context of an objectlrelational database management system. As a background to a discussion of the features of the invention, a brief overview of an objectlrelational database management system is first provided. For more detailed information about such a system, reference is made to Application Serial No. 08/951,714, filed October 16, 1997, the disclosure of which is incorporated herein by reference.
Referring to Figure l, the general architecture of an object/relational database management system is illustrated. In such a system, an object database is created by the user, and provides a conceptual overview of the data. The 10 database 10 comprises a set of classes, each of which includes searchable properties. The classes form a hierarchy, in which each class that is derived from a base class inherits all of the searchable properties of that base class. The derived class may have additional searchable properties :as well as those which are inherited.
The classes, objects and relationships between classes in the user's object database 10 are modeled in a meta-model 12. T'he mesa-model is an object/relational representation, comprising a set of classes, objects and relationships which model the application object-relational model of the user object database. The user can create, edit and manipullate both the application objects in the database and the application object-relational model by means of a suitable user interface 14.
The meta-model 12 has a corresponding set of relational database structures 16, which are capable of being manipulated by a conventional relational database engine I8. Preferably, each class in the user's object database 10 is modeled by a table in the relational database 16. Each searchable property of a class is modeled by a column in the associated table, and each object of a class is modeled by a row in the table. A relationship between two objects is modeled by a pointer from one row to another row within the table.
Once the object database and corresponding meta-model and relational database have been created, the user can conduct searches on the data by means of the interface 14. Within the interface, the user selects one or more classes to be searched, restrictions on searchable properties of objects in those classes, and information to be presented for the objects. In response to this input, a relational database query 20 is generated. This query is presented to the search engine i8, which retrieves information from the relational database 16 and presents it to the user according to the properties of the classes which were searched.
Within the context of such an object/relational database management system, the present invention provides the user with the ability to easily manipulate and access data across multiple dinnensions. The concept of multi-dimensional data is depicted in Figure 2 in connection with an example that relates to component management in a manufacturing organization. In this particular example, the data relating to components is organized along three dimensions, namely by time, manufacturing site, and individual component, or item. In this particular example, the time dimension has three levels of granularity, i.e.
months, fiscal quarters and years. A cost value, represented by the dollar sign, is associated with each combination of values for the three dimensions.
The organization of the data in a multi-dimensional fashion, as depicted in Figure 2, provides the user with the ability to perform various types of analysis.
For example, a financial officer can compare the cost for a given component over a particular quarter between various sites, or locate the components which had the highest costs across all sites during a particular time period.
To provide the user with the ability to ;analyze data in a multi-dimensional format, the data first undergoes a consolidation process. This process is depicted in the block diagram of Figure 3. Referring thereto, transaction files 22 containing data that is of interest to the user are first provided to a staging area 24, where the files are parsed to extract the relevant data. The transaction files 22 can represent any type of information that is relevant to the data to be managed.
For example, in a component and supplier management system, purchase orders constitute one type of transaction file that contains data relating to the individual components of interest. Within the staging area 24, the information extracted from the individual files is placed into tables, preferably tables of the type which are associated with a relational database system. From these tables, the information is first grouped into sub-granular .data 26. One example of the grouping of information into sub-granular data is to consolidate the data by individual days. Thus, fox the example depicted in Figure 2, the data for all purchase orders of a given date is grouped in accordance with manufacturing site and purchased item.
At the next stage of the process, the sub-granular data is further consolidated into granular data 28. Again referring to the example of Figure 2, the lowest level of granularity along the time dimension is by month.
Therefore, in this step of the process, the data for each of the days of a given month is consolidated into a single cost figure for each site and item. The final step in the consolidation process comprises the generation of a fact table 30; which stores the data in a form that can be searched by a relational database search engine.
In addition to being consolidated into granular data, the sub-granular data 26 can also be employed for various purposes that the user may desire. For instance, a file 32 containing some or all of the sub-granular data can be supplied to the user's accounting system to generate daily cost reports, or the like.
In the user object model for the objectlrelational database system, each dimension of the data is associated with a different class. Figure 4 illustrates an example of a four-dimensional classlsubclass hierarchy. In this example, the four dimensions are associated with the base classes for commodity, organization, supplier and time. Each of these base classes may have one or more searchable properties. Each base class also has one or more subclasses, which inherit the _g_ searchable properties of their parent classes, and may have additional searchable properties which are specific to them.
The data in the fact table 30 is linked to the classes of the hierarchy.
Figure 5 illustrates an example of a relatively simple fact table 30 containing multiple columns of information. Various ones of these columns are linked to the top level, or base class 34, for each dimension. Due to the inheritance property of the classes, each of the subclasses 36-40 below a base class automatically inherits this linking as well. As a result, users can construct searches on the basis of properties associated with any of the various classes and subclasses within the hierarchy.
With reference back to the objectlrelational database system of Figure 1, each class 34 and subclass 36-40 of the dimensional hierarchy maps into a respective table in the relational database 16. The properties of a class map into the fields of its respective table. More specifically, each instance of the class comprises one row of the table. In the case of a subclass, only its unique, i.e.
non-inherited properties, appear in the row of its table, since the higher-level, inherited properties already appear in another row. The search engine contains information about the structure of the classes and tables, and is thereby able to locate the rows in the tables which return the desired results. By means of this arrangement, therefore, the user is able to relate to the data in terms of classes and instances of classes, rather than as rows in tabaes.
As an enhancement, all of the possible mufti-dimensional queries that can be envisaged are precomputed from the data, <~nd the results of each are loaded into the fact table 30 as individual rows. Thereafter, whenever a query is entered, the data from the appropriate row is retrieved, to provide the results more quickly.
Figures 6-8 illustrate examples of a user interface that can be employed in.
the context of the present invention to construct searches. This particular user interface comprises a search navigator that consists of two primary window panes.
-g_ WO 00/1.9340 PCTNS99/22674 The left pane 34 illustrates the classes and subclasses of the hierarchy, along with their relationships. In the example of Figure 6, the user has selected the base class entitled "Available Inventory" . This base class has two dimensions associated with it, which are represented by the subclasses labeled "Commodity" and "Organization" . The various levels associated. with each of these dimensions are depicted under their respective subclasses.
Figures 7 and 8 illustrate an example in which the user has selected a different base class, in this case "Cost History". As can be seen in the left window pane 34, this class has four dimensions associated with it, which correspond to the example of Figure 5. The first two dimensions are the same as those appearing in the "Available Inventory" class depicted in Figure 6. Two additional dimensions, labeled "Supplier" and "Time", are also present for this class of information.
The right window pane 36 of the user interface identifies the searchable parameters that are associated with a particular class or dimension level.
These parameters can be limited to only those which are specific to a chosen subclass, or include those which are inherited from parent classes and subclasses as well.
A
number of tabs 38 are displayed at the top of the window pane. The left tab corresponds to the base class, and the remaining tabs relate to levels in each of the four dimensions which have been chosen by the user. In the example of Figure 6, the tab associated with the base class "Available Inventory" has been selected.
This base class has one searchable parameter, labeled "Value", associated with it.
A search window 40 is provided for the user to enter a parameter value for the search. In addition, the window pane includes a button 42 associated with the parameter. By selecting this button, the user is presented with a list of all of the available values that could be entered in the search window 40 as one of the search criteria.
WO 00/19340 PCTIUS99I22b74 In the example of Figure 7, the user has selected the tab for the level "Ordered Part Number" . In this case, a number of search windows 40 are displayed, for each of the searchable properties associated with that dimension level. The user can enter values into any one or more of the search windows, to refine the search criteria. In the example of Figure 8, the user has switched to the "Month" tab within the same base class. Consequently, the search windows 40 appearing in the right pane correspond to the two searchable parameters for that level, i. e. "Month" and "Year" .
Once the user has entered criteria into any one or more of the search windows 40, a "Search" button 44 is selected. In response, the parameter values entered by the user are presented to the search engine for the relational database.
This engine reads the structure of the user object model, and constructs a query to identify all of the data which matches the search criteria. This query is based upon the cascaded search mechanism described in detail in the previously cited Application Serial No. 08/951,714, which enables a search to be conducted across all classes in a relational manner. For further information regarding this aspect of the system, the reader is referred to that disclosure.
From the foregoing, it can be seen that the present invention provides a database management system which permits the user to access data across multiple dimensions. The dimensions are respectively associated with different classes, and the various levels within a dimension have corresponding subclasses. The classes and subclasses are displayed to the user in a hierarchical manner. This representation is more cognitive to the user, since it corresponds to the manner in which the data is intuitively organized, so that the user's ability to construct a search is facilitated. By selecting the various tabs in the user interface window, it is possible for the user to identify all of the various properties of a subclass, including those which are inherited from parent classes, that are available fox searching. As a result, searches can be automatically configured, and reports generated, in a dynamic manner, without requiring extensive programming efforts.
As a further advantage, the system is easily created and maintained, and is completely extensible so that additional dimensions can be used to access data, by creating further classes to define the dimensions.
It will be appreciated by those of ordinary skill in the art that the present invention can be embodied in other specific forms without departing from the spirit or essential characteristics thereof. The presently disclosed embodiments are therefore considered in all respects to be illustrative, and not restrictive.
The scope of the invention is indicated by the appended claims, rather than the IO foregoing description, and all changes that come within the meaning and range of equivalents thereof are intended to be embraced therein.
Claims (11)
1. A multi-dimensional object/relational database system, comprising:
at least one table containing data which can be represented along a plurality of dimensions;
a plurality of object-oriented classes which are respectively associated with said plurality of dimensions and which map to corresponding data in said tables; and a search engine which retrieves data from said table in accordance with user-designated properties of said classes.
at least one table containing data which can be represented along a plurality of dimensions;
a plurality of object-oriented classes which are respectively associated with said plurality of dimensions and which map to corresponding data in said tables; and a search engine which retrieves data from said table in accordance with user-designated properties of said classes.
2. The database system of claim 1, wherein at least some of said classes contain subclasses which inherit properties from their parent classes, and wherein said search engine retrieves data corresponding to both the unique and inherited properties of a subclass designated by a user.
3. The database system of claim 2 wherein each of said classes and subclasses maps to a respective table containing data which corresponds to the properties of its associated class or subclass.
4. The database system of claim 3 wherein each table contains data which corresponds only to the unique properties of its associated class or subclass.
5. The database system of claim 1 further including a user interface comprising a first panel which illustrates the hierarchical relationship of said classes, and a second panel which displays the properties of a selected class.
6. The database system of claim 5 wherein said second panel includes a means for the user to specify values for the displayed properties of a selected class.
7. The database system of claim 6 wherein said user-specifying means includes a window in which the user can enter a value.
8. The database system of claim 6 wherein said user-specifying means includes a list in which the user can select from all of the available values for a property.
9. A user interface for a multi-dimensional object/relational database system having a plurality of object-oriented classes which are respectively associated with different dimensions of data, comprising:
a first panel which illustrates a hierarchical relationship of said classes; and a second panel which displays the properties of a selected class and includes means for a user to specify values for the displayed properties.
a first panel which illustrates a hierarchical relationship of said classes; and a second panel which displays the properties of a selected class and includes means for a user to specify values for the displayed properties.
10. The user interface of claim 9 wherein said user-specifying means includes a window in which the user can enter a value.
11. The user interface of claim 9 wherein said user-specifying means includes a list in which the user can select from all of the available values for a property.
Applications Claiming Priority (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US10246398P | 1998-09-30 | 1998-09-30 | |
US60/102,463 | 1998-09-30 | ||
PCT/US1999/022674 WO2000019340A1 (en) | 1998-09-30 | 1999-09-30 | Multi-dimensional data management system |
Publications (1)
Publication Number | Publication Date |
---|---|
CA2344638A1 true CA2344638A1 (en) | 2000-04-06 |
Family
ID=22289984
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CA002344638A Abandoned CA2344638A1 (en) | 1998-09-30 | 1999-09-30 | Multi-dimensional data management system |
Country Status (8)
Country | Link |
---|---|
US (1) | US6366922B1 (en) |
EP (1) | EP1125226A4 (en) |
JP (1) | JP2002526833A (en) |
KR (1) | KR20010093775A (en) |
AU (1) | AU1097800A (en) |
CA (1) | CA2344638A1 (en) |
IL (1) | IL142136A0 (en) |
WO (1) | WO2000019340A1 (en) |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN107766445A (en) * | 2017-09-23 | 2018-03-06 | 湖南胜云光电科技有限公司 | A kind of efficient rapid data search method for supporting various dimensions to retrieve |
Families Citing this family (95)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6408292B1 (en) | 1999-08-04 | 2002-06-18 | Hyperroll, Israel, Ltd. | Method of and system for managing multi-dimensional databases using modular-arithmetic based address data mapping processes on integer-encoded business dimensions |
US6385604B1 (en) | 1999-08-04 | 2002-05-07 | Hyperroll, Israel Limited | Relational database management system having integrated non-relational multi-dimensional data store of aggregated data elements |
US20020133368A1 (en) * | 1999-10-28 | 2002-09-19 | David Strutt | Data warehouse model and methodology |
US6700590B1 (en) * | 1999-11-01 | 2004-03-02 | Indx Software Corporation | System and method for retrieving and presenting data using class-based component and view model |
US20020029207A1 (en) * | 2000-02-28 | 2002-03-07 | Hyperroll, Inc. | Data aggregation server for managing a multi-dimensional database and database management system having data aggregation server integrated therein |
JP2001243244A (en) * | 2000-02-28 | 2001-09-07 | Hitachi Ltd | Retrieving method of multi-dimensional database, retrieving device and computer readable recording medium storing multi-dimensional database retrieval program |
US7222130B1 (en) * | 2000-04-03 | 2007-05-22 | Business Objects, S.A. | Report then query capability for a multidimensional database model |
US6768986B2 (en) * | 2000-04-03 | 2004-07-27 | Business Objects, S.A. | Mapping of an RDBMS schema onto a multidimensional data model |
AU2001257077A1 (en) * | 2000-04-17 | 2001-10-30 | Brio Technology, Inc. | Analytical server including metrics engine |
JP2001306377A (en) * | 2000-04-20 | 2001-11-02 | Natl Inst Of Advanced Industrial Science & Technology Meti | Property data base system |
US7072897B2 (en) * | 2000-04-27 | 2006-07-04 | Hyperion Solutions Corporation | Non-additive measures and metric calculation |
US6941311B2 (en) * | 2000-04-27 | 2005-09-06 | Hyperion Solutions Corporation | Aggregate navigation system |
US6748394B2 (en) * | 2000-04-27 | 2004-06-08 | Hyperion Solutions Corporation | Graphical user interface for relational database |
US7080090B2 (en) | 2000-04-27 | 2006-07-18 | Hyperion Solutions Corporation | Allocation measures and metric calculations in star schema multi-dimensional data warehouse |
US7167859B2 (en) * | 2000-04-27 | 2007-01-23 | Hyperion Solutions Corporation | Database security |
US6732115B2 (en) | 2000-04-27 | 2004-05-04 | Hyperion Solutions Corporation | Chameleon measure and metric calculation |
US20050050343A1 (en) * | 2000-06-30 | 2005-03-03 | Selinfreund Richard H. | Storage media access control method and system |
US6647391B1 (en) * | 2000-07-11 | 2003-11-11 | Ian E. Smith | System, method and article of manufacture for fast mapping from a propertied document management system to a relational database |
AU2002211197A1 (en) * | 2000-10-25 | 2002-05-06 | Philip Tan Meng Ngee | A multi-dimensional method and system for simulating strategic alliance of enterprises |
DE20020170U1 (en) * | 2000-11-28 | 2001-03-01 | Guru Netservices Gmbh | Storage and access structure |
US20020099563A1 (en) * | 2001-01-19 | 2002-07-25 | Michael Adendorff | Data warehouse system |
GB2376316B (en) * | 2001-06-04 | 2004-09-22 | Gordon Frederick Ross | Multi-dimensional human-computer-content processing using iterative, structured,shared categorisation cycles. |
US20030154271A1 (en) | 2001-10-05 | 2003-08-14 | Baldwin Duane Mark | Storage area network methods and apparatus with centralized management |
AU2002221573A1 (en) * | 2001-12-16 | 2003-06-30 | Acinta Aps | Computer-implemented method of merging at least two dimensionally modeled databases |
US6839719B2 (en) | 2002-05-14 | 2005-01-04 | Time Industrial, Inc. | Systems and methods for representing and editing multi-dimensional data |
US7191182B2 (en) * | 2002-07-20 | 2007-03-13 | Microsoft Corporation | Containment hierarchy in a database system |
RU2005105582A (en) * | 2002-07-26 | 2005-10-10 | Рон ЭВЕРЕТТ (CA) | DATABASE AND KNOWLEDGE MANAGEMENT SYSTEM |
KR100488916B1 (en) * | 2002-12-04 | 2005-05-17 | 유징테크주식회사 | Apparatus and method for selecting task class |
KR20030009556A (en) * | 2003-01-02 | 2003-01-29 | 에이티이시스템즈(주) | Classification and Basic Information Management Method of Object-Oriented Programming |
US20040181518A1 (en) * | 2003-03-14 | 2004-09-16 | Mayo Bryan Edward | System and method for an OLAP engine having dynamic disaggregation |
EP1482419A1 (en) * | 2003-05-28 | 2004-12-01 | Sap Ag | Data processing system and method for application programs in a data warehouse |
US7853507B2 (en) * | 2003-06-23 | 2010-12-14 | Omx Technology Ab | Method for organizing financial instruments in a CSD-system |
US7302445B2 (en) | 2003-08-29 | 2007-11-27 | International Business Machines Corporation | Method, system, and storage medium for providing a dynamic, multi-dimensional commodity modeling process |
US20050080778A1 (en) * | 2003-10-14 | 2005-04-14 | Yvan Pochon | System and method using universal substitute values in database tables |
US9268831B2 (en) * | 2004-01-12 | 2016-02-23 | Lightfoot Solutions Group Limited | System and method for extracting user selected data from a database |
US7076493B2 (en) * | 2004-05-28 | 2006-07-11 | Metadata, Llc | Defining a data dependency path through a body of related data |
US20060149739A1 (en) * | 2004-05-28 | 2006-07-06 | Metadata, Llc | Data security in a semantic data model |
EP1610236A1 (en) * | 2004-06-23 | 2005-12-28 | Sap Ag | A data processing system and method |
EP1617326A1 (en) * | 2004-07-14 | 2006-01-18 | Sap Ag | Technique for handling hierarchical application data |
US7610300B2 (en) * | 2004-11-30 | 2009-10-27 | International Business Machines Corporation | Automated relational schema generation within a multidimensional enterprise software system |
US7505888B2 (en) * | 2004-11-30 | 2009-03-17 | International Business Machines Corporation | Reporting model generation within a multidimensional enterprise software system |
US7418438B2 (en) * | 2004-11-30 | 2008-08-26 | International Business Machines Corporation | Automated default dimension selection within a multidimensional enterprise software system |
US7593955B2 (en) * | 2004-11-30 | 2009-09-22 | International Business Machines Corporation | Generation of aggregatable dimension information within a multidimensional enterprise software system |
US7797320B2 (en) * | 2005-03-15 | 2010-09-14 | Hyperion Solutions Corporation | Dimensionality reduction |
US7634766B2 (en) * | 2005-05-20 | 2009-12-15 | Sun Microsystems, Inc. | Method and apparatus for pattern-based system design analysis using a meta model |
JP4808736B2 (en) * | 2006-02-01 | 2011-11-02 | パナソニック株式会社 | Information classification device and information retrieval device |
US7770146B2 (en) * | 2006-05-19 | 2010-08-03 | Sap Ag | Computer software development incorporating core and compound services |
KR100892842B1 (en) * | 2007-08-08 | 2009-04-10 | 엔에이치엔(주) | Method and system for user centered information searching |
KR100903506B1 (en) | 2007-10-24 | 2009-06-17 | 엔에이치엔(주) | System and method for managing informaiton map |
WO2010014852A1 (en) * | 2008-07-30 | 2010-02-04 | Kevin Francis Eustice | Social network model for semantic processing |
US20100031198A1 (en) * | 2008-07-30 | 2010-02-04 | Michael Zimmerman | Data-Oriented User Interface for Mobile Device |
US8463739B2 (en) * | 2008-08-28 | 2013-06-11 | Red Hat, Inc. | Systems and methods for generating multi-population statistical measures using middleware |
US8495007B2 (en) * | 2008-08-28 | 2013-07-23 | Red Hat, Inc. | Systems and methods for hierarchical aggregation of multi-dimensional data sources |
US9020882B2 (en) | 2008-11-26 | 2015-04-28 | Red Hat, Inc. | Database hosting middleware dimensional transforms |
US20100174998A1 (en) * | 2009-01-06 | 2010-07-08 | Kiha Software Inc. | Calendaring Location-Based Events and Associated Travel |
US8417739B2 (en) * | 2009-05-29 | 2013-04-09 | Red Hat, Inc. | Systems and methods for object-based modeling using hierarchical model objects |
US9105006B2 (en) | 2009-05-29 | 2015-08-11 | Red Hat, Inc. | Generating floating desktop representation of extracted model object |
US9292592B2 (en) * | 2009-05-29 | 2016-03-22 | Red Hat, Inc. | Object-based modeling using composite model object having independently updatable component objects |
US8930487B2 (en) * | 2009-05-29 | 2015-01-06 | Red Hat, Inc. | Object-based modeling using model objects exportable to external modeling tools |
US9292485B2 (en) | 2009-05-29 | 2016-03-22 | Red Hat, Inc. | Extracting data cell transformable to model object |
US9009006B2 (en) | 2009-05-29 | 2015-04-14 | Red Hat, Inc. | Generating active links between model objects |
US8606827B2 (en) * | 2009-05-29 | 2013-12-10 | Red Hat, Inc. | Systems and methods for extracting database dimensions as data modeling object |
US9069862B1 (en) | 2010-10-14 | 2015-06-30 | Aro, Inc. | Object-based relationship search using a plurality of sub-queries |
US8560548B2 (en) * | 2009-08-19 | 2013-10-15 | International Business Machines Corporation | System, method, and apparatus for multidimensional exploration of content items in a content store |
US9152435B2 (en) * | 2009-08-31 | 2015-10-06 | Red Hat, Inc. | Generating a set of linked rotational views of model objects |
US8417734B2 (en) * | 2009-08-31 | 2013-04-09 | Red Hat, Inc. | Systems and methods for managing sets of model objects via unified management interface |
US20110054854A1 (en) * | 2009-08-31 | 2011-03-03 | Eric Williamson | Systems and methods for generating dimensionally altered model objects |
US8365195B2 (en) * | 2009-08-31 | 2013-01-29 | Red Hat, Inc. | Systems and methods for generating sets of model objects having data messaging pipes |
US9152944B2 (en) | 2009-08-31 | 2015-10-06 | Red Hat, Inc. | Generating rapidly rotatable dimensional view of data objects |
US8909678B2 (en) * | 2009-09-30 | 2014-12-09 | Red Hat, Inc. | Conditioned distribution of data in a lattice-based database using spreading rules |
US9031987B2 (en) * | 2009-09-30 | 2015-05-12 | Red Hat, Inc. | Propagation of data changes in distribution operations in hierarchical database |
US20110078199A1 (en) * | 2009-09-30 | 2011-03-31 | Eric Williamson | Systems and methods for the distribution of data in a hierarchical database via placeholder nodes |
US8996453B2 (en) * | 2009-09-30 | 2015-03-31 | Red Hat, Inc. | Distribution of data in a lattice-based database via placeholder nodes |
US8984013B2 (en) * | 2009-09-30 | 2015-03-17 | Red Hat, Inc. | Conditioning the distribution of data in a hierarchical database |
US8396880B2 (en) * | 2009-11-30 | 2013-03-12 | Red Hat, Inc. | Systems and methods for generating an optimized output range for a data distribution in a hierarchical database |
US8589344B2 (en) * | 2009-11-30 | 2013-11-19 | Red Hat, Inc. | Systems and methods for generating iterated distributions of data in a hierarchical database |
US8315174B2 (en) * | 2009-12-31 | 2012-11-20 | Red Hat, Inc. | Systems and methods for generating a push-up alert of fault conditions in the distribution of data in a hierarchical database |
US9342793B2 (en) | 2010-08-31 | 2016-05-17 | Red Hat, Inc. | Training a self-learning network using interpolated input sets based on a target output |
US10353891B2 (en) | 2010-08-31 | 2019-07-16 | Red Hat, Inc. | Interpolating conformal input sets based on a target output |
US8429099B1 (en) | 2010-10-14 | 2013-04-23 | Aro, Inc. | Dynamic gazetteers for entity recognition and fact association |
US20120102453A1 (en) * | 2010-10-21 | 2012-04-26 | Microsoft Corporation | Multi-dimensional objects |
US9292575B2 (en) * | 2010-11-19 | 2016-03-22 | International Business Machines Corporation | Dynamic data aggregation from a plurality of data sources |
US9355383B2 (en) | 2010-11-22 | 2016-05-31 | Red Hat, Inc. | Tracking differential changes in conformal data input sets |
US8346817B2 (en) | 2010-11-29 | 2013-01-01 | Red Hat, Inc. | Systems and methods for embedding interpolated data object in application data file |
US8364687B2 (en) | 2010-11-29 | 2013-01-29 | Red Hat, Inc. | Systems and methods for binding multiple interpolated data objects |
US10366464B2 (en) | 2010-11-29 | 2019-07-30 | Red Hat, Inc. | Generating interpolated input data sets using reduced input source objects |
US8290969B2 (en) | 2011-02-28 | 2012-10-16 | Red Hat, Inc. | Systems and methods for validating interpolation results using monte carlo simulations on interpolated data inputs |
US9489439B2 (en) | 2011-02-28 | 2016-11-08 | Red Hat, Inc. | Generating portable interpolated data using object-based encoding of interpolation results |
US8862638B2 (en) | 2011-02-28 | 2014-10-14 | Red Hat, Inc. | Interpolation data template to normalize analytic runs |
US8768942B2 (en) | 2011-02-28 | 2014-07-01 | Red Hat, Inc. | Systems and methods for generating interpolated data sets converging to optimized results using iterative overlapping inputs |
US8650185B1 (en) * | 2012-09-28 | 2014-02-11 | Ampersand Ventures, Inc. | Systems and methods for database interaction using a multi-dimensional graphical user input interface |
US9223832B2 (en) | 2013-03-07 | 2015-12-29 | International Business Machines Corporation | Insight determination and explanation in multi-dimensional data sets |
CN104021156B (en) * | 2014-05-22 | 2017-03-15 | 武汉天量数据技术有限公司 | A kind of method that multilamellar factual data is quickly collected based on SQL statement |
US10318703B2 (en) | 2016-01-19 | 2019-06-11 | Ford Motor Company | Maximally standard automatic completion using a multi-valued decision diagram |
US20190108256A1 (en) * | 2017-10-09 | 2019-04-11 | Switch Commerce, Llc | System for scalable database security |
Family Cites Families (10)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5548749A (en) * | 1993-10-29 | 1996-08-20 | Wall Data Incorporated | Semantic orbject modeling system for creating relational database schemas |
US6061515A (en) * | 1994-07-18 | 2000-05-09 | International Business Machines Corporation | System and method for providing a high level language for mapping and accessing objects in data stores |
US5627979A (en) * | 1994-07-18 | 1997-05-06 | International Business Machines Corporation | System and method for providing a graphical user interface for mapping and accessing objects in data stores |
US5694598A (en) * | 1994-10-12 | 1997-12-02 | U S West Technologies, Inc. | Method for mapping data between a relational format and an object-oriented format |
US5680619A (en) * | 1995-04-03 | 1997-10-21 | Mfactory, Inc. | Hierarchical encapsulation of instantiated objects in a multimedia authoring system |
US5845270A (en) * | 1996-01-02 | 1998-12-01 | Datafusion, Inc. | Multidimensional input-output modeling for organizing information |
US5907846A (en) * | 1996-06-07 | 1999-05-25 | Electronic Data Systems Corporation | Method and system for accessing relational databases using objects |
US5937402A (en) * | 1997-06-19 | 1999-08-10 | Ontos, Inc. | System for enabling access to a relational database from an object oriented program |
US5905985A (en) * | 1997-06-30 | 1999-05-18 | International Business Machines Corporation | Relational database modifications based on multi-dimensional database modifications |
US5937409A (en) * | 1997-07-25 | 1999-08-10 | Oracle Corporation | Integrating relational databases in an object oriented environment |
-
1999
- 1999-09-30 IL IL14213699A patent/IL142136A0/en unknown
- 1999-09-30 KR KR1020017004144A patent/KR20010093775A/en not_active Application Discontinuation
- 1999-09-30 CA CA002344638A patent/CA2344638A1/en not_active Abandoned
- 1999-09-30 WO PCT/US1999/022674 patent/WO2000019340A1/en not_active Application Discontinuation
- 1999-09-30 JP JP2000572777A patent/JP2002526833A/en not_active Abandoned
- 1999-09-30 EP EP99954690A patent/EP1125226A4/en not_active Withdrawn
- 1999-09-30 AU AU10978/00A patent/AU1097800A/en not_active Abandoned
- 1999-09-30 US US09/409,069 patent/US6366922B1/en not_active Expired - Lifetime
Cited By (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN107766445A (en) * | 2017-09-23 | 2018-03-06 | 湖南胜云光电科技有限公司 | A kind of efficient rapid data search method for supporting various dimensions to retrieve |
CN107766445B (en) * | 2017-09-23 | 2021-06-01 | 湖南胜云光电科技有限公司 | Efficient and rapid data retrieval method supporting multi-dimensional retrieval |
Also Published As
Publication number | Publication date |
---|---|
KR20010093775A (en) | 2001-10-29 |
US6366922B1 (en) | 2002-04-02 |
WO2000019340A1 (en) | 2000-04-06 |
AU1097800A (en) | 2000-04-17 |
IL142136A0 (en) | 2002-03-10 |
EP1125226A4 (en) | 2006-05-10 |
JP2002526833A (en) | 2002-08-20 |
EP1125226A1 (en) | 2001-08-22 |
WO2000019340A9 (en) | 2000-10-12 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US6366922B1 (en) | Multi-dimensional data management system | |
US7925658B2 (en) | Methods and apparatus for mapping a hierarchical data structure to a flat data structure for use in generating a report | |
US5978811A (en) | Information repository system and method for modeling data | |
US6199059B1 (en) | System and method for classifying and retrieving information with virtual object hierarchy | |
US8027971B2 (en) | Relationship management in a data abstraction model | |
US5701453A (en) | Logical schema to allow access to a relational database without using knowledge of the database structure | |
US6839719B2 (en) | Systems and methods for representing and editing multi-dimensional data | |
US7634478B2 (en) | Metadata driven intelligent data navigation | |
US6212524B1 (en) | Method and apparatus for creating and populating a datamart | |
US8571945B2 (en) | Pre-qualifying sellers during the matching phase of an electronic commerce transaction | |
US20180285883A1 (en) | Providing Market Feedback Associated with Electronic Commerce Transactions to Sellers | |
US6944613B2 (en) | Method and system for creating a database and searching the database for allowing multiple customized views | |
JP2006505059A (en) | System and method for generating reports on versioned databases | |
Lewerenz et al. | Modelling data warehouses and OLAP applications by means of dialogue objects | |
US7440969B2 (en) | Data processing systems and methods for processing a plurality of application programs requiring an input database table having a predefined set of attributes | |
EP1634192B1 (en) | Data processing system and method for application programs in a data warehouse | |
WO2002001415A2 (en) | Computer method and device for transporting data | |
Seyed-Abbassi | Teaching Effective Methodologies to Design a Data Warehouse | |
Anderson et al. | Toward a national model of an electronic decision support system for domestic sourcing of textiles and apparel | |
McDermid | Oracle OLAP Java API Developer’s Guide, 11g Release 1 (11.1) B28127-02 | |
Wolfe | Ad Hoc Query: a reusable database access capability |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
FZDE | Discontinued |