Computer-implemented system and method for visualizing OLAP and multidimensional data in a calendar format

[0001] This document relates generally to computer-implemented data processing systems and methods and more particularly to data presentation.

[0002] Database technology has evolved to where multidimensional data can be stored and retrieved. In a multidimensional database, data is categorized into measures which are numerical in nature and into time dimensions which characterize the measures. The time dimensions have hierarchies and have found utility in many fields, including the data warehousing field and the Online Analytical Processing (OLAP) field. Despite the evolution of database technology, data visualization of multidimensional data has remained limited.

[0003] In accordance with the teachings provided herein, systems and methods for operation upon data processing devices are provided in order to overcome one or more of the aforementioned disadvantages or other disadvantages concerning the presentation of multidimensional data.

[0004] For example, a system and method can be configured to associate actual calendar dates with time dimension members. This association can be based on the time periods and the corresponding time-level information in a cube's time dimension hierarchies. Query results involving time periods and time period analysis are displayed as graph chart objects within the time period's visual presentation.

[0005] As another example, a system and method can be configured to generate a time dimension calendar to visualize time dimension hierarchy and/or time series analysis of multidimensional data. The time dimension hierarchy levels are mapped to actual time periods in the common date and time calendar. The tuple cell values of dimension members are represented graphically on calendars by chart objects. The user can interactively drill down on time periods by drilling on a date object, or can drill down by dimension members by using the chart objects. Additional comparative and summary statistics relating to time dimension and time functions can be presented in the calendar. The time dimension calendar can be customizable based on user preferences and locales.

[0006] As will be appreciated, the systems and methods disclosed herein are capable of other and different embodiments, and capable of modifications in various respects. Accordingly, the drawings and description set forth herein are to be regarded as illustrative in nature and not restrictive.

[0030] FIG. 1 depicts at 30 a system for use with a multidimensional database 32. An end user 34 or a host application 36 (such as a data warehousing application, or an Online Analytical Processing (OLAP) or a data mining application) initiates a query to the multidimensional database 32 via a database engine (38). The database engine 38 processes the query, such as by parsing and translating, optimizing, and evaluating in order to formulate a logical expression from the query.

[0031] The logical expression can be in the form of a plurality of terms connected via a plurality of operators such as logical operators, relational operators, arithmetic operators, etc. The engine 38 then scans the multidimensional database 32 to locate and relate data records 40 that fulfill the logical expression and return results to the end user 34 or host application 36.

[0032] The results could be the data records themselves, such as a single data record for a singleton answer or a group of data records for an answer grid. However, within the system 30 of this example, results can be provided as a calendar-formatted display that is tied to or otherwise connected to one or more portions of the multidimensional database's hierarchy.

[0033] Calendar processing functionality 42 can be added to provide a connection or link between the multidimensional hierarchy and calendar-formatted graphical objects located on the display of the computer 34. When a user manipulates a graphical object on the displayed calendar, calendar processing functionality 42 receives information related to the user interaction and based upon the multidimensional hierarchy can assist in generating a new calendar-based display that addresses what the user had manipulated.

[0034] FIG. 2 illustrates a few characteristics of a multidimensional database 32 within a system 44. In the multidimensional database 32 of system 44, data records 40 contain numerical measures 58 and time dimensions 54 that characterize the numerical measures 58.

[0035] The multidimensional database 32 can contain other types of dimensions. For example, a textual dimension could contain geography information. The textual dimension could be arranged hierarchically starting from a general geographical designation to a more specific one—e.g., the geography hierarchy could be arranged at a state level which could decompose to a county geographical level which could decompose even further, such as to a city or township geographical level.

[0036] The multidimensional database 32 views data records 40 as cubes 50 that contain hierarchies of the dimensions 52. Stated another way, a cube 50 represents a particular set of dimensions that the user can use to view the data records 40.

[0037] The dimensions 52 of the database's cubes are used for selecting and aggregating data at the desired level of detail. A time dimension 54 can be organized into a hierarchy composed of multiple levels 56, each representing a level of detail for use within a desired type of analysis. For example, multidimensional data can contain time-related data aggregation along time period intervals. An aggregation can result in time period summaries for members of the cube. The time dimension levels may be ordered by level number ordinals in a logical time order. The level ordinal number represents the distance of the level from the root of the hierarchy with level zero being the root level number. Members belonging to the time dimension levels are related in parent-child relationships, where members belonging to a level with a low ordinal value will have children in a level with a higher ordinal value.

[0038] In the example of system 44 depicted in FIG. 2, calendar processing functionality 42 can be used to visualize time dimension hierarchy and time series analysis of multidimensional data by mapping 60 (e.g., associating) actual calendar dates 62 with time dimension members 56. The tuple cell values of dimension members are represented graphically on calendars by chart objects. Because of the mapping 60, a user can interactively drill down on time periods by drilling on a date object, or can drill down by dimension members by using the chart objects.

[0039] It should be understood that other or different calendar processing may be utilized, such as using the mapping 60 to drill up (e.g., from a lower time dimensional level to a higher time dimensional level). As another example, additional comparative and summary statistics relating to time dimension and time functions can be presented in a displayed calendar. The time dimension calendar could also be customizable based on user preferences and locales.

[0040] While FIG. 2 displays a single computer 34 having access to one or more calendar processing functions, computer 34 may be configured to locally have one or more calendar processing functions, or a system may be configured to have one or more of calendar processing functions accessible on a remote server over a network (e.g., local area network, wide area network, internet, etc.).

[0041] Moreover, a system can contain multiple computers that locally contain one or more calendar processing functions or have the functions accessible over a network. Data signal(s) can carry any or all of the data disclosed herein that is provided to or from a computer or device. Data signals may be conveyed via networks, fiber optic medium, carrier waves, wireless networks, etc. for communication among multiple computers or computing devices.

[0042] FIG. 3 shows at 100 examples of different hierarchical structures that can be used in a multidimensional database. A “product line” dimensional hierarchy decomposes in this example into an “all productline” dimensional level which decomposes into a furniture and office dimensional level. A time-based dimensional hierarchy decomposes into an “all time” dimensional hierarchy which further decomposes into a year dimensional level (which, e.g., includes a 1993 dimensional level member, a 1994 dimensional level member, etc.). The year dimensional level itself decomposes into a quarterly dimensional level. The quarterly dimensional level decomposes into a monthly dimensional level. The time-based dimensional hierarchy could be further decomposed at more granular levels (e.g., a weekly level, a daily level, etc.). Numerical measures (e.g., sales values) can be stored as data records for the product lines at the different levels in the time dimensional hierarchy.

[0043] FIG. 4 shows an example of a multidimensional query 150 that takes into consideration the dimensional hierarchical structure 100 of FIG. 3. The multidimensional query 150 is formulated to compare quarterly sales for the years 1993 and 1994 for the furniture and office product lines. The query is processed and at least a portion of the results are formatted as graphical objects as shown at 160 in FIG. 4.

[0044] The graphical calendar-formatted display 160 shows the years 1993 and 1994 along the horizontal axis. The horizontal axis further shows the quarters for these years. The vertical axis shows sales data for the furniture and office product lines for each of the years' quarters. A user can see additional detail by manipulating (e.g., clicking upon or selecting) one or more of the graphical objects (e.g., bargraph object 162). The manipulation can result in the user seeing a more detailed time breakdown for bargraph 162, such as seeing the sales data on a weekly or daily basis.

[0045] The calendar data can be formatted in many different ways, such as web pages accessible over a network such as over the world-wide web (web). The web is a method of accessing information on the internet which allows a user to navigate the internet resources intuitively, without IP addresses or other technical knowledge. A user's computer can contain client software, known as a web “browser,” which is used to display web pages as well as traditional non-web files on the client system.

[0046] FIGS. 5A and 5B are flowcharts depicting an example of an operational scenario using calendar processing functions. With reference to FIG. 5A, start block 200 indicates that a query is received at process block 202 for retrieving data from a multidimensional database. Process block 204 processes the query, such as by using the mapping at process block 206 to generate a time-based graphical display of the data that satisfies the query received at process block 202.

[0047] More specifically in this operational scenario, an OLE database for OLAP can be used, and in a multidimensional result set, an ordered collection of members from different dimensions can be represented as a compound coordinate on a dataset axis. Processing continues at FIG. 5B as indicated at continuation marker 208.

[0048] With reference to FIG. 5B, decision block 210 examines whether the data requested in the query requires any statistical analysis associated with the retrieved data. Comparative and/or summary statistics can be performed respectively at process blocks 212 and 214 for use in generating a calendar-formatted display that meets the needs of the user. The computations involved in comparative statistical analysis and summary statistical analysis may be performed on the client-side and/or server-side. In this operational scenario, the comparative statistical analysis is performed on the client-side, and because of the computationally intensive nature of the summary statistical analysis, the summary statistical analysis is performed on the server-side.

[0049] In this operational scenario, many different types of comparative statistics can be used, such as the following calculations:

• • [0050] Parallel period comparison: a calculation that compares the value of measure/member tuple in the current period with the values of the same tuple in a parallel period. Parallel periods are periods that have the same parallel position in the time dimension hierarchy. For example, the year 2001 period has the years 2002, 2003, and 2004 as parallel periods. May of 2001 has parallel periods of May 2002, May 2003, and May 2004. The calculation results are shown as a percentage of the difference.
  • [0051] Consecutive period comparison: a calculation that compares the value of measure/member tuple in the current period with the values of the same tuple in a consecutive period. Consecutive periods are periods that have adjacent positions in the time dimension hierarchy. For example, year 2001 period has years 2000 and 2002, as adjacent periods. May of 2001 has April 2001 and June 2001 as adjacent periods. The calculation results are shown as a percentage of the difference.
  • [0052] Relative contribution analysis: a calculation can be made in four different ways:

[0053] 1. The percentage of contribution of a current child member tuple relative to its parent total.

[0054] 2. The percentage of contribution of the current child member relative to an overall total.

[0055] 3. The percentage of contribution of the current time period relative to its parent time period total.

[0056] 4. The percentage of contribution of the current time period relative to an all time total.

[0057] Comparative statistics may be placed on a chart, such as shown in FIG. 6 at 302. A user can change which comparative statistics are shown by manipulating (e.g., clicking upon) the change measure hyperlink shown at 304. After the hyperlink 304 is activated, a user interface appears wherein the user can specify which (if any) comparative statistics should be shown with the chart.

[0058] Time series summary statistics can also be presented within the calendar and placed in the calendar side bar, and could include the following calculations:

• • [0059] Year-to-Date YTD: The YTD total and YTD Average can be calculated for the current members displayed in the chart.
  • [0060] Quarter-to-Date QTD: The QTD total and QTD average can be calculated for the current members displayed in the chart.
  • [0061] Month-to-Date MTD: The MTD total and MTD average can be calculated for the current members displayed in the chart.
  • [0062] Week-to-Date WTD: The WTD total and WTD average can be calculated for the current members displayed in the chart.
  • [0063] Period-to-Date: for other time periods, such as Half years, Days and Hours, the Period to date total and the Period to date average can be calculated for the current members displayed in the chart.
  • [0064] Opening Period: Represents the value of the current members at the beginning of the time period, such as opening balances.
  • [0065] Closing Period: Represents the values of the current members at the end of the time period, such as closing balances.

[0066] Summary statistics may be placed on a chart, such as shown in FIG. 6 at 310. A user can change which summary statistics are shown by manipulating (e.g., clicking upon) the hyperlink shown at 312. After the hyperlink 312 is activated, a user interface appears wherein the user can specify which (if any) summary statistics should be shown with the chart.

[0067] Any other user defined calculations can be specified by the user to display in the calendar. Such calculation might be a 5 Year Average, 2 Years Total, etc.

[0068] If statistics are not needed as determined at decision block 210, then processing continues at process block 216 wherein the calendar-formatted display is provided to the requester or to an entity that requires the display. Process block 218 processes interactions from the user, such as a user interacting with the graph in order to drill down to view more detail associated with a particular time dimension. As an example of interaction handling, graphical objects (e.g., a date barchart object) that are generated and that comprise the graphical display can be used such that a user can activate (e.g., click upon) a graphical object in order to do a drill down (or drill up) operation. Based upon the user's interaction, an event notification is sent from the client's web browser to a computer program/routine for use in formulating a multidimensional database query to retrieve data in response to the drill down (or drill up) operation. For example, the event notification, among other things, can contain what date barchart object had been activated by the user. Using the hierarchy association between actual calendar dates/time units with levels of the time dimension hierarchy, the program/routine formulates the multidimensional database query to retrieve data at a lower level (or higher level) associated with the time dimension hierarchy in order to respond to the drill down (or drill up) operation. The multidimensional database query can then be handled by a process, such as by process block 202. Processing for this operational scenario ends at end block 220.

[0069] It should be understood that similar to the other processing flows described herein, the steps and the order of the steps in the flowchart may be altered, modified, deleted and/or augmented and still meet the situation at hand. Moreover, the steps may be performed on the same computer or distributed across multiple computers (e.g., client computers and server computers) to meet the situation at hand.

[0070] FIG. 6 illustrates another calendar-formatted display that contains four dimensions: Time, Measure, Products, and Geography. Sales is a measure in the Measures dimension and represents gross sales calculation for products in regions over time periods. Appliances and Hardware are members in the Product Dimension. The time dimension contains two hierarchies:

• • [0071] the first time hierarchy is organized by years, quarters, months, and days.
  • [0072] the second time hierarchy can be drilled by years, months, days and hours.

[0073] In the calendar pages interface of FIG. 6 and other figures shown herein, time levels in the dimensional hierarchy are mapped to correspond to an actual date, a date range, or a time stamp (e.g., actual displayed calendar date 2003 and actual date 2004 shown in FIG. 6 respectively at 320 and 322). Time periods represented by a calendar are: Years, Half Years, Quarters, Months, Weeks, Days, and Hours. These periods correspond to the OLE DB for OLAP enumerated time dimension level types of:

• • [0074] MDLEVEL_TYPE_TIME_YEARS represented by the Year period GUI (graphical user interface) (as shown in FIG. 6).
  • [0075] MDLEVEL_TYPE_TIME_HALF_YEAR represented by the Half-Year period GUI (as shown in FIG. 7).
  • [0076] MDLEVEL_TYPE_TIME_QUARTERS represented by the Quarters period GUI (as shown in FIGS. 8 and 9).
  • [0077] MDLEVEL_TYPE_TIME_MONTHS represented by the Months period GUI (as shown in FIGS. 10 and 11).
  • [0078] MDLEVEL_TYPE_TIME_DAYS represented by the Days period GUI (as shown in FIG. 12).
  • [0079] MDLEVEL_TYPE_TIME_HOURS represented by the Hour period GUI (as shown in FIG. 13).

[0080] As shown at 300, FIG. 6 is a single level representation. Years 2003 and 2004 belong to the same level in the Time dimension hierarchy. The bar reflects values at the Year level. The chart bars represent the value of Appliances and Hardware for the year 2004. The +55% is the calculated percentage of difference between the appliances values in the year 2004 and 2003.

[0081] As shown at 350, FIG. 7 is a representation of two different time dimension levels. Years 2003 and 2004 are members of the Year level. The “First Half Year” member and “Second Half Year” member are the children of 2004 at the Half-Year level. Comparison is for the Half Year Level data.

[0082] As shown at 400, FIG. 8 is a chart which represents the Appliance and Hardware sales value for the 2003 and 2002 quarter periods. The quarter period children are stacked so that each month period is visible and can be selected to drill down to the day of month level values.

[0083] As shown at 450, FIG. 9 is an alternate style representation of the Quarter time level data. This style allows for the representation of three time levels periods—year, quarter, and months levels. The bar represents the values at the Quarter level. The user can select any of the months to drill down to the months values.

[0084] As shown at 500, FIG. 10 is a single Quarter Level member representation. The Comparison in this figure is between Q1 of 2003 and Q1 of 2002.

[0085] As shown at 550, FIG. 11 shows the months summary values of year 2004, compared to the month's summary values of 2003. The user can click on the month to get the daily summaries.

[0086] As shown at 600, FIG. 12 shows the values of the children of the Month level Member at the day level. The calendar displays the holidays in the month of May. The user interface also displays a custom user defined period starting on May 1st and ending on May 7th.

[0087] As shown at 650, FIG. 13 displays the day summary for Appliances and Hardware Sales as compared with the same day in a previous year. The three shift layout is a display option. The user can click a date tab to drill down to hourly statistics.

[0088] As shown at 700, FIG. 14 shows a different cube example that displays hourly summaries for a call center data. The “Lunch Break” text is a type of user defined event that can be incorporated into the calendar. The “Christmas Eve” information is a calendar option that allows the user to view holidays and events specific to a locale.

[0089] The graph chart objects shown in these figures represent the tuple values of cube members. A tuple is the cell at the intersection of one or more dimension members and a measure. The graph chart can also be in any type of time-based graph. The following are a few examples: a vertical bar, a horizontal bar (e.g., as shown at 750 in FIG. 15), a line chart (e.g., as shown at 800 in FIG. 16), an area plot (e.g., as shown at 850 in FIG. 17), or a pie chart (e.g., as shown at 900 in FIG. 18).

[0090] The calendar may also be customized in appearance and style to display different styles and layout. Users may customize the calendar to enter their own dates and date ranges to be displayed in the calendar object. For example, a calendar display can be customized such that the 1st of May to 12th of May (Mother's day) ad campaign dates are reflected in the calendar. The time calendar can also be based on a fiscal year. Quarters can be customized to reflect seasons of the year. The calendar can also optionally show holiday dates and special events.

[0091] The time calendar can use the current locale to display dates in the format appropriate to the current locale. Holidays and culture specific date information can be reflected in the calendar. For example, a calendar operating in a French locale is shown at 950 in FIG. 19.

[0092] While examples have been used to disclose the invention, including the best mode, and also to enable any person skilled in the art to make and use the invention, the patentable scope of the invention is defined by claims, and may include other examples that occur to those skilled in the art. For example, many different types of time-based graphical displays can be generated. As an illustration, FIG. 20 shows at 1000 an alternative style for quarters of the year calendar display. FIG. 21 shows at 1050 an alternative style of the month of the year calendar. FIG. 22 shows at 1100 a weekly comparison calendar. FIG. 23 shows at 1150 an alternate calendar style for a day of the month display. Calendar-based formatted displays can include traditional types of calendar displays as well as many other different types that illustrate time-based data.

[0093] As another example of the broad ranges of the systems and methods disclosed herein, many different types of time objects may be used, such as centuries, decades, work weeks, work days, days before and after a holiday, hours, minutes, seconds, milliseconds, microseconds, hours in a day, hours in a work day, minutes in an hour, etc.

[0094] It is further noted that the systems and methods may be implemented on various types of computer architectures, such as for example on a single general purpose computer or workstation, or on a networked system, or in a client-server configuration, or in an application service provider configuration.

[0095] Additionally, the methods and systems described herein may be implemented on many different types of processing devices by program code comprising program instructions that are executable by the device processing subsystem. The software program instructions may include source code, object code, machine code, or any other stored data that is operable to cause a processing system to perform methods described herein. Other implementations may also be used, however, such as firmware or even appropriately designed hardware configured to carry out the methods and systems described herein.

[0096] The systems' and methods' data (e.g., associations, mappings, etc.) may be stored and implemented in one or more different types of computer-implemented ways, such as different types of storage devices and programming constructs (e.g., data stores, RAM, ROM, Flash memory, flat files, databases, programming data structures, programming variables, IF-THEN (or similar type) statement constructs, etc.). It is noted that data structures describe formats for use in organizing and storing data in databases, programs, memory, or other computer-readable media for use by a computer program.

[0097] The systems and methods may be provided on many different types of computer-readable media including computer storage mechanisms (e.g., CD-ROM, diskette, RAM, flash memory, computer's hard drive, etc.) that contain instructions for use in execution by a processor to perform the methods' operations and implement the systems described herein.

[0098] The computer components, software modules, functions, data stores and data structures described herein may be connected directly or indirectly to each other in order to allow the flow of data needed for their operations. It is also noted that a module or processor includes but is not limited to a unit of code that performs a software operation, and can be implemented for example as a subroutine unit of code, or as a software function unit of code, or as an object (as in an object-oriented paradigm), or as an applet, or in a computer script language, or as another type of computer code. The software components and/or functionality (e.g., calendar processing functionality) may be located on a single computer or distributed across multiple computers depending upon the situation at hand (e.g., located on client and/or server computers).

[0099] It should be understood that as used in the description herein and throughout the claims that follow, the meaning of “a,” “an,” and “the” includes plural reference unless the context clearly dictates otherwise. Also, as used in the description herein and throughout the claims that follow, the meaning of “in” includes “in” and “on” unless the context clearly dictates otherwise. Finally, as used in the description herein and throughout the claims that follow, the meanings of “and” and “or” include both the conjunctive and disjunctive and may be used interchangeably unless the context clearly dictates otherwise; the phrase “exclusive or” may be used to indicate situation where only the disjunctive meaning may apply.