WO2006119602A1 - Method for symultaneously displaying date information in two different calandar types - Google Patents
Method for symultaneously displaying date information in two different calandar types Download PDFInfo
- Publication number
- WO2006119602A1 WO2006119602A1 PCT/CA2005/000707 CA2005000707W WO2006119602A1 WO 2006119602 A1 WO2006119602 A1 WO 2006119602A1 CA 2005000707 W CA2005000707 W CA 2005000707W WO 2006119602 A1 WO2006119602 A1 WO 2006119602A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- calendar
- time
- date
- business
- user
- Prior art date
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/10—Office automation; Time management
- G06Q10/109—Time management, e.g. calendars, reminders, meetings or time accounting
Definitions
- the present invention relates to a system and method for time dimension management for a data analyzing system.
- business data such as financial data and operational data
- data store with time information.
- various data analyzing applications are proposed.
- business users can navigate through data in a time dimension relevant to their business. For example, a user may be interested in viewing data from the previous quarter, last January or last year.
- Time dimension having multiple levels of time.
- Organizations may use a conventional Gregorian calendar to define the time dimension that they use.
- time may be divided by Day, Week, Calendar Week, Business Week (less than 7 days), Calendar Month, Lunar or Manufacturing Month (4 or 5 week month), Lunar or Manufacturing Quarter (13 week), Semester and Year.
- time divisions into basic units and various summary levels on top of this basic unit set. Companies frequently start their fiscal year, quarter and month differently than those conventional calendar divisions. Companies may see time differently than the real world time. For example, a broadcast company may have a 28-hour day, beginning at midnight on the east coast and ending at midnight on the west coast. Further, time dimension hierarchies are often complicated by the overlap of different periods. In particular, the weekly boundaries do not coincide with the month, quarter and Year boundaries.
- User interfaces of existing data analyzing applications for time navigation support either Gregorian calendar date selection, or hierarchical navigation of the business calendar dimension.
- Hierarchical navigation of the business calendar is typically provided using cascading menus.
- Cascading structures however do not provide visual feedback of the business calendar. Also, they do not show how far along the business is in any given period regardless of granularity.
- These user interfaces do not have ability to translate between the Gregorian calendar and the business calendar. It is often difficult or unintuitive for users to select time that they are interested.
- a time dimension management system for managing time dimension of a data analyzing system for analyzing data stored in a data store based on a time data structure.
- the time dimension management system comprises a data selector controller and a calendar coordinator.
- the date selector controller is provided for controlling a date selector that presents to a user a standard calendar and a business calendar.
- the date selector controller has a standard calendar manager for managing presentation of the standard calendar for allowing the user to select a date on the standard calendar, and a business calendar manager for managing presentation of the business calendar to represent the time data structure that the data analyzing system uses, and allowing the user to select a date on the business calendar.
- the calendar coordinator is provided for coordinating the standard calendar manager and the business calendar manager to indicate a selected date on the standard calendar and the business calendar.
- a method of managing time dimension of a data analyzing system for analyzing data stored in a data store based on a time data structure comprises the steps of presenting a standard calendar for allowing the user to select a date on the standard calendar, presenting a business calendar that represents the time data structure that the data analyzing system uses for allowing the user to select a date on the business calendar; receiving a date selection by a user on the standard calendar or the business calendar; and coordinating presentation of the standard calendar and the business calendar to indicate a same date on the standard calendar and the business calendar in response to the date selection by the user.
- a memory containing computer executable instructions that can be read and executed by a computer for managing time dimension of a data analyzing system for analyzing data stored in a data store based on a time data structure.
- the memory comprising instructions to execute a method comprising the steps of presenting a standard calendar for allowing the user to select a date on the standard calendar, presenting a business calendar that represents the time data structure that the data analyzing system uses for allowing the user to select a date on the business calendar, receiving a date selection by a user on the standard calendar or the business calendar, and coordinating presentation of the standard calendar and the business calendar to indicate a same date on the standard calendar and the business calendar in response to the date selection by the user.
- a propagated signal or its carrier containing computer executable instructions that can be read and executed by a computer, the computer executable instructions being used to execute the method of managing time dimension of a data analyzing system for analyzing data stored in a data store based on a time data structure.
- Figure 1 is a block diagram showing a computer system that uses a time dimension management system in accordance with an embodiment of the invention
- FIG. 2 is a block diagram showing the time dimension management system in accordance with an embodiment of the invention.
- Figure 3 is a diagram showing an example of a toolbar drop down menu provided by the time dimension management system
- Figure 4 is a diagram showing an example of a time period selection image provided by the time dimension management system
- Figure 5 is a diagram showing an example of a most recent data view image provided by the time dimension management system
- Figure 6 is a diagram showing examples of a business calendar
- Figure 7 is a diagram showing an example of a time dimensional selector
- Figure 8 is a diagram showing an example of a time level selector
- Figure 9 is a diagram showing an example of a validity date indicator
- Figure 10 is a diagram showing an example of a metric history chart
- Figure 11 is a diagram showing an example of a metric history list
- Figure 12 is a diagram showing an example of an action tab
- Figure 13 is a diagram showing an example of a date selector image
- Figure 14 is a diagram showing another example of a date selector image.
- Figure 15 is a diagram showing another example of a date selector image.
- FIG. 1 shows a time dimension management system 10 in accordance with an embodiment of the present invention.
- the time dimension management system 10 is used in a computer system 20 having an input unit 22 and output unit 24.
- An organization uses a data analyzing system 30 to analyze business data stored in a data store 40.
- the time dimension management system 10 is suitably used to manage time dimensions for the data analyzing system 30.
- the data analyzing system 30 has a user interface 32 to allow users to analyze business data.
- the organizations uses its own financial calendar or business calendar having a predefined multi-level time hierarchy, or a time data structure 34.
- the time data structure 34 contains an ordered set of time levels. In each time level has an ordered set of time periods. The ordered set of time periods in each level may comprise a continuous time span with no overlapping periods. For example, the time data structure 34 may contain four levels of time: Days, Periods, Quarter and Year.
- the time data structure 34 has two types of members: leaf member and summary member.
- a leaf member represents values for that member alone.
- Time periods in summary levels represent the summarization of an adjacent set of one or more leaf time periods.
- the data analyzing system 30 may provide the value in the period, and various summary information of interest, such as a value of period-to-date one or more of the higher level periods, e.g., Quarter-to-Date and Year-to-Date, and rolling calculations, e.g., 12 month rolling total.
- Summarization of time periods in one level to time periods in higher levels is expressed as a set of child-parent relationships. For example, each successive level may represent a summarization of the next lower level. Higher levels represent coarser grain than lower levels. The number of time periods in each level therefore tend to be lower in higher levels.
- the data analyzing system 30 provides traces of the rollup relationships and relative ordering of periods to determine concepts such as "previous Period”, "Same child Period of a Sibling Period" for purposes of providing values of period-to-date periods and for trend calculations.
- the data analyzing system 30 may also define a set of special periods in the zero-th level which are aggregations of other time periods. These commonly are used for period-to-date or rolling-sum totals. There are no restrictions on the content of these periods and no requirements of a continuous time span or ordering of periods in the zero-th level.
- the data analyzing system 30 may also define a special level "Year", the period numbering is based on the virtual existence of an 'AH' parent. A user documentation item will need to be added to tell customers that when staging levels, Year has to get a level ID of 1 Y'.
- the data analyzing system 30 may provide a primary key to time periods, by which they are referenced.
- the key consists of two fields, a Level Identifier and a Start date.
- An end date is an attribute.
- the combination of these three fields represents a unique key for each time period, Time periods in the same level can be ordered based on the Start date.
- the business calendar is often different from a standard calendar, such as a Gregorian calendar, which is used in daily life.
- the time dimension management system 10 provides visualization of the hierarchy of the business calendar in the context of real time in a standard calendar. Also, Lunar/Manufacturing calendars, which are often used as a business calendar, do not maintain traditional week/month/year boundaries.
- the time dimension management system 10 provides a date selector.
- the date selector may be provided through the user interface 32 of the data analyzing system 30, allowing users to define the context of the data that they wish to view.
- the date selector provided by the time dimension management system 10 presents both a standard calendar and a business calendar.
- the standard calendar is typically a conventional Gregorian calendar, but it may be a different calendar.
- the business calendar represents the time data structure that the organization uses for its business, such as a fiscal year calendar. It presents the hierarchy of the time data structure in an intuitive manner.
- Figure 3 shows an example of a toolbar drop down menu 100 for a date selector.
- the a toolbar drop down menu 100 provides options: "select a period to view” 102 and "view most recent data” 104.
- a date selector 110 shows the selected period "September FY2004" on the business calendar 120 and September 24, 2004 on the standard calendar 130, as shown in Figure 4.
- the date selector 110 has a business calendar 120 and a Gregorian calendar 130.
- the business calendar 120 has multiple cells 122 that are arranged to represent the hierarchy 124 of the time data structure of the fiscal calendar or business calendar that the organization uses.
- the user has selected the business calendar level 126 as "Month", and thus there are the business calendar 120 shows three levels, including year, quarter and month.
- the Gregorian calendar 130 has a year selection field 132, month selection field 134 and a day or date selection field 136. This example shows that September FY2004 on the business calendar 120? and September 24, 2004 on the Gregorian calendar 130.
- the time dimension management system 10 allows users to easily visualize their business calendar hierarchy and where they are within any given period. It also allows users to easily navigate between relevant periods, for example to view the data for the same period in the previous year or quarter. The time dimension management system 10 enables users to navigate either calendar without knowing or calculating their corresponding periods in the other calendar.
- FIG. 2 shows details of the time dimension management system 10 in accordance with an embodiment of the invention.
- the time dimension management system 10 has a date selector controller 50 that provides a date selector having a standard calendar and a business calendar, and allows a user to select a date based on which the user wants to analyze data through the data analyzing system 30.
- the date selector controller 50 has a standard calendar manager 52 and a business calendar manager 54.
- the standard calendar manager 52 manages presentation of the standard calendar and allows the user to select a date on the standard calendar.
- the standard calendar manager 52 presents a conventional Gregorian calendar 130 in which months and days are arranged in a conventional manner.
- the standard calendar manager 52 may display the a standard calendar 130 in a different arrangement or manner, e.g., by arranging months to correspond to the fiscal year of the organization. For example, if the first day of the fiscal year is February 1 in the organization, the standard calendar manager 52 may present months in the month selection field 134 in sequence starting from February.
- the standard calendar manager 52 may show in the date selection field 136 those days that are available in the business or fiscal calendar 120 differently from unavailable days. Selection of year, month or date refreshes the display of the other fields to show the available dates of the month.
- the business calendar manager 54 manages presentation of the business calendar to represent the time data structure that the organization uses, and allows a user to select a desired date on the business calendar. To represent the time data structure, the business calendar manager 54 may use a time cell handler 56.
- the time cell handler 56 provides the business calendar using multiple cells, each representing a unit of the business calendar.
- the time cell handler 56 handles presentation of the cells based on the time levels of the business calendar in accordance with the time data structure 34 of the data analyzing system 30.
- the user can select a cell in each level on the business calendar to specify a desired date on the business calendar.
- the example shown in Figure 4 is an example of a business calendar that is presented by the time cell handler 56 using multiple cells arranged in hierarchy.
- the fiscal calendar 120 has multiple cells 122 arranged to represent the hierarchy of the fiscal calendar having four levels: year, quarter, month and day. Selection of a cell in a level refreshes the display of the cells in other levels. For a different fiscal calendar, there may be fewer or more levels and cells 122 may be arranged differently.
- Figure 6 shows different examples 140, 142 of business calendar with cells.
- cells 122 have no labels thereon in order to present a visual representation of the current placement within the fiscal calendar structure. This allows users to navigate to any representative period without having to reselect the child cells of the selected level. Cells 122 may be labeled appropriately in a different embodiment.
- the time dimension management system 10 also has a calendar coordinator 60 for coordinating or synchronizing the standard calendar manager 52 and the business calendar manager 54 so as to indicate a same date on both the standard calendar and the business calendar.
- the calendar coordinator 60 determines the correspondence between the standard calendar and the business calendar using the time data structure 34.
- the calendar coordinator 60 may provide links, linking each date on the standard calendar with corresponding cells on the business calendar 120.
- selecting a date on the standard calendar automatically highlights cells representing the same date on the business calendar, and vice versa. It is a 1 :1 relationship between the standard calendar and the business calendar.
- a calendar date selected on the standard calendar equals a period in the business calendar based upon the time dimension level or rollup level that the user has defined.
- hyperlinks 118 are provided to dates on the standard calendar 130, linking each date on the standard calendar with corresponding cells 122 on the fiscal calendar 120.
- the user has selected a date, September 24, 2004, in the Gregorian calendar 130.
- This date is shown in the business calendar 120 with the highlighted cells of each level, i.e., the third month of the third quarter of the fourth fiscal year.
- the user can now navigate by date or by period on the business calendar 120 or on the Gregorian calendar 130.
- the name of the year, quarter, month or day is displayed in a tool tip 112 when the user's cursor hovers over a cell in this display 110.
- the date selector controller 50 automatically updates the view of the Gregorian calendar 130 or the structure view of the business calendar 120.
- the date selector controller 50 provides side by side navigation of the business calendar 120 and the Gregorian calendar 130. Users can use the date selector to scroll through forward or backward, through fiscal years; select a reporting period as defined by the fiscal calendar; select a day of the reporting period for which to show data; and jump to the most recent data in the data store.
- the date selector controller 50 allows users to navigate the reporting periods of their respective companies regardless of the type of fiscal calendar 120 used, while also maintaining some sense of orientation of location in a typical real world calendar 130.
- a standard calendar and a business calendar may be arranged differently on a display.
- the business calendar manager 54 provides a business calendar with multiple cells to represent the time data structure of the business calendar.
- a different form of a date selector may be useful.
- the business calendar manager 50 may use a time dimensional selection handler 58 for presenting a time dimensional selector or rollup selector as a business calendar.
- the time dimensional selection handler 58 allows the user to select a time period defined by the time data structure 34 of the data analyzing system 30.
- the user can set the context of each level at which the user navigates the calendar. For example, if the user selects quarter, the user navigates the quarters of the business calendar and the data displayed in the main user interface is aggregated to the quarter. If the user changes the rollup to months, the aggregation displays the month level and the time line navigated at the month level.
- the time dimensional selection handler 58 may represent time levels of the data structure 34 in a tree structure or using a drill down mechanism that allows users to select the individual time level properties.
- FIG 7 shows an example of a time dimensional selector 160 presented by the time dimensional selection handler 58.
- This time dimensional selector 160 represents a custom calendar having multiple time levels 162, e.g., "Cookies", “Lorries”, “Jam”, and so on. Time levels are dictated and populated by the time data structure 34. Each time level has one or more time items 164. Time items in each time levels are provided using a pull down window 166.
- time dimensional selector 160 Using the time dimensional selector 160, the user can select a time item in each level that the user wishes to view. Selecting one level causes the next level becomes enabled, and allows the user to make a selection of a time item on the next level. This continues until all levels provided in the time dimensional selector 160 are selected.
- the combination of the selected time items in the levels correspond to a date or dates in the standard calendar.
- the calendar coordinator 60 provides links between the standard calendar manager 52 and dimensional selection handler 58 so that selecting a set of time items in the dimensional selector 160 automatically shows a corresponding date or dates in the standard calendar, and vice versa.
- the time dimensional selection handler 58 allows the user to set the time level selection to the lowest defined level in the time dimensional selector. In this example 160, if the user selects an item at the "Cookies Level", the user would only be able to select time level selections appropriate to that level.
- the time dimension management system 10 may have a time level selection controller 80 for presenting a time level selector.
- the time level selection controller 80 allows the user to select a time level at which the user wishes to view the data.
- the time level selection controller 80 may provide a time level selector in a form of a roll-up control.
- Figure 8 shows an example of a time level selector 170. The available selections are defined by the time data structure 34. In the example shown in Figure 8, time levels available for selections are shown in a normal tone and unavailable time levels are shown in a half tone. Not all time levels are available for selection in Figure 8 because the lowest time level of the date/time selection has not been selected.
- Availability of time levels are determined depending on the selections in the time dimensional selector. This example represents the view of a data store that is only defined down to the "period" level. To make the lower time level selections available, the user may open the dimensional selector and identify the details of the lower time levels. When the user uses a date selector, the lowest level “Day” is defined and all time levels are shown available.
- selecting a time level specifies a period for which the data is viewed. The period starts from the date selected on the standard calendar or on the business calendar or by the time dimensional selector.
- time level selector 170 shown in Figure 8 allows the user to see options of year, quarter, period, week, day and view most recent data.
- this type of time level selector may be amalgamated into the main calendar selector to set the navigation context and to make the calendar display simpler.
- Figure 13 shows a date selector 200 in accordance with another embodiment of the invention.
- the date selector 200 has a Gregorian calendar 210 and a fiscal calendar 220.
- the user has selected a date, March 14, 2004, on the Gregorian calendar 210.
- This date is shown in the fiscal calendar 220 with the highlighted cells of each level, i.e., the 10th day, of the 1st month of the 1st quarter of fiscal year 2004.
- the user can now navigate by date or by period on the Gregorian calendar 210 or on the fiscal calendar 220.
- the name of the year, quarter, month or day is displayed in a tool tip 230 when the user's cursor hovers over a cell in this display 200.
- Figure 14 shows that the user now selects on the Gregorian calendar 210 March 16, 2004. This selection of a different date automatically updates the structure view of the fiscal calendar 220.
- the user chooses to view the same relative day and month in the third quarter 222 on the business calendar 220.
- This selection automatically updates the Gregorian calendar 210 to show September 16, 2004. This navigation allows users to quickly move from one contextual time to another with little to no effort.
- the time dimension management system 10 may also have a validity date indication controller 90.
- the validity date indication controller 90 provides an indication of a validity date that identifies when the data was published.
- a validity date indication 180 may be provided with or adjacent to the data or data options 182 presented by the data analyzing system 30.
- a time dimension that defines the levels of time differs from other dimensions. Each time period is part of a continuum of periods. In analyzing business data, users are often interested in both the quantity in a period and the cumulative value for that period for either some fixed number of consecutive periods or relative to the start of any one of its parent periods. Data is added to a data analyzing application in time period based increments. The most recent time period may be in progress and have only partial data.
- the calendar control described above affects date selection throughout the user interface 32 of the data analyzing system 30.
- the affects of the data selection are described using a metric data analyzing system that provides metric views of data.
- the time data structure of the metric data analyzing system has the following features.
- Three concepts define a time dimension: time levels structure, time periods structure and time relationships structure. These structures have the following attributes that are used for time calculations. ⁇
- the time levels structure has attributes: Level Identifier (unique among levels), Language Text Id (to get Level Name), Level Number (numeric; indicating position in Level Hierarchy. 1 indicates the highest level ; 0 is reserved for internal use), and Reference Display Level ID (used as a default for the "latest view” feature in the Ul).
- the time periods structure has attributes: Time Period ID, Level Identifier (link to TIMEJ-EVELS), Start Time Code, End Time Code, Language Text Id (to get Level Name), Child Count (a count of children in the next lower level), Internal fiscal year value (fiscal year value used for internal purposes only), Period number (the order of period under a given parent level member), Previous period identifier (represents the identifier of the previous period in the same level), Period type (internal use), and Reference level identifier (internal use).
- the time relationships structure contains attributes: Parentldentifier (link to Time Periods Table), and Childldentifier (link to Time Periods Table).
- a time language text structure is used to provide multi-lingual representation of period and level display strings. Attributes include: Language_Text_ld, Language_Cd, Short_Name, and Long_Name.
- Certain periods may be used to calculate period-to-date comparison values. These values are calculated as of specified "Reference" periods. There is one Reference period in each time level. Reference periods are set at the time of data load. The Reference period for each time level can be explicitly set by the administrator or be defaulted from the current date (at the time that the loader is run).
- a Reference period for a time level is not explicitly set, it is assumed to be the most recent completed full time period of that level. For example, an application with Year, Quarter, Month, and Day time levels loaded on November 17, 2004 would have the following default Reference periods:
- a set of special cumulative time periods are provided based on the Reference periods. In the general case, there is one cumulative period for each for each higher-level period that exists for each Reference period.
- Month-to-date at daily grain for Nov 16 has 3 potential comparative time periods. They are:
- Month-to-date at daily grain for Oct 16 (Same period in previous month)
- Month-to-date at daily grain for August 16 (Same period in the same relative month in previous quarter)
- Values for comparison periods should not be staged since they will be generated by MMLOADER. The user might be required to stage localized names for those periods though in the case of a custom calendar.
- Trend calculations are based on a comparison of one time period with a corresponding earlier time period. By default, trend is based on the immediately previous similar time period. For example, the trend for Quarter 2, 2004 is based the comparisons of values from Quarter 1 , 2004. The trend for Quarter 1 , 2004 is based on a comparison of values from Quarter 4, 2003.
- the trend of interest to a customer may not be to the immediately preceding similar period but to a similar period in a previous higher level.
- a customer may be more interested in the trend from Quarter 4, 2003 to Quarter 4, 2004 than the trend from Quarter 3, 2004 to Quarter 4, 2004.
- Two methods for users to generate or modify their time dimensions are provided: generating standard time dimension based on predefined levels, and generating a time dimension from tables.
- a time dimension can be generated consisting of one or more of the standard date levels, such as: Fiscal/Calendar Year, Fiscal/Calendar Quarter, Lunar Quarter, Fiscal/Calendar Month, Lunar Month (4 Weeks), Week (5, 6 or 7 day), and Day.
- standard date levels such as: Fiscal/Calendar Year, Fiscal/Calendar Quarter, Lunar Quarter, Fiscal/Calendar Month, Lunar Month (4 Weeks), Week (5, 6 or 7 day), and Day.
- Various parameters specify the beginning and end period, the number of days in a week and fiscal period boundaries.
- the Time Dimension Staging table will be expended to provide a means to define each period and each relationship to the loader.
- Both Template Measure and Benchmark Period are attributes of a measure. Benchmark period also has a "Global" default value. All allocations and summarizations are performed during the loading process.
- a metric data analyzing system model with no data and no generated time periods can have unlimited changes to its structure. Once Time periods are entered, changes are limited to the following:
- New Time periods can be added to the end.
- Old time periods can be removed from the beginning. • Granularity levels for existing Measures can be modified. Levels can be added or removed. Parent Child relationships can be altered.
- the calendar control and associated . time level selector affect the data views, such as metric list values (on scorecard, metric type, owner, group or objective), history chart, history list and actions tab.
- the values displayed on a metric list are controlled by the calendar control.
- the values displayed are the most recent actual values available for each list, and at the lowest available time grain. For example, if revenue is provided monthly and bug count daily, both the most recent daily bug count and the revenue for the most recent month are displayed.
- the metric list view displays all metrics, but only the values available for that time and time level. Metrics available only at a higher time grain (e.g. months or quarters) are displayed as "under construction" when viewing at a lower time grain such as days.
- the time levels and range displayed by a history chart may be controlled by the calendar control of the time dimension management system 10 or by local controls as defined in a History Chart specification of the data analyzing system 30.
- the metric history chart may be displayed such that in recent data view, the history chart displays bars at the lowest time grain available for this metric. The number of bars displayed is defaulted per the History Chart specification. If a specific date and time level is selected in the global calendar control, it sets the default level and initial time period for the history chart. The user may navigate away from this view using the local history chart navigation controls. However, if a new global calendar date and level are selected, this overrides any local history chart navigation settings. A sample view is shown in Figure 10.
- a metric history list displays available periods and levels for the year selected in the global calendar control. Thus, the global time level drop down may be disabled when the user is viewing metric history list displays. In recent data mode, the most recent year in which data exists for this metric is displayed. A sample view is shown in Figure 11.
- the data analyzing system 20 may also provide an action display, as shown in Figure 12.
- the actions display displays actions associated with the currently selected period as well as those for which action is required and has not been completed. In recent data view, actions for the period in which the most recent actual value is available is displayed.
- the calendar control provided by the time dimension management system 10 is flexible enough to allow users to navigate a fiscal year, regardless of the type of business calendar that is employed by the organization.
- the time dimension management system 10 allows users to navigate periods of their business while maintaining a grounding in a real world calendar, e.g., a Gregorian calendar.
- a real world calendar e.g., a Gregorian calendar.
- the time dimension management system 10 can also provide a mechanism that supports arbitrary custom defined business calendars, e.g., non-time related calendars.
- the time dimension management system of the present invention may be implemented by any hardware, software or a combination of hardware and software having the above described functions.
- the software code either in its entirety or a part thereof, may be stored in a computer readable memory.
- a computer data signal representing the software code which may be embedded in a carrier wave may be transmitted via a communication network.
- Such a computer readable memory and a computer data signal or its carrier are also within the scope of the present invention, as well as the hardware, software and the combination thereof.
Abstract
Description
Claims
Priority Applications (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
EP05742644A EP1880353A4 (en) | 2005-05-09 | 2005-05-09 | Method for symultaneously displaying date information in two different calandar types |
PCT/CA2005/000707 WO2006119602A1 (en) | 2005-05-09 | 2005-05-09 | Method for symultaneously displaying date information in two different calandar types |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
PCT/CA2005/000707 WO2006119602A1 (en) | 2005-05-09 | 2005-05-09 | Method for symultaneously displaying date information in two different calandar types |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2006119602A1 true WO2006119602A1 (en) | 2006-11-16 |
Family
ID=37396124
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CA2005/000707 WO2006119602A1 (en) | 2005-05-09 | 2005-05-09 | Method for symultaneously displaying date information in two different calandar types |
Country Status (2)
Country | Link |
---|---|
EP (1) | EP1880353A4 (en) |
WO (1) | WO2006119602A1 (en) |
Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5764597A (en) * | 1997-04-10 | 1998-06-09 | Shih; Wu Yung | Electronic calendar |
CA2315389A1 (en) * | 1998-01-07 | 1999-07-15 | Microsoft Corporation | System and method of displaying times corresponding to events on a calendar |
US6108640A (en) * | 1997-01-14 | 2000-08-22 | Slotznick; Benjamin | System for calculating occasion dates and converting between different calendar systems, and intelligent agent for using same |
CA2418754A1 (en) * | 2002-01-12 | 2003-07-12 | Cognos Incorporated | System and method for automated database report definition |
-
2005
- 2005-05-09 EP EP05742644A patent/EP1880353A4/en not_active Withdrawn
- 2005-05-09 WO PCT/CA2005/000707 patent/WO2006119602A1/en not_active Application Discontinuation
Patent Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6108640A (en) * | 1997-01-14 | 2000-08-22 | Slotznick; Benjamin | System for calculating occasion dates and converting between different calendar systems, and intelligent agent for using same |
US5764597A (en) * | 1997-04-10 | 1998-06-09 | Shih; Wu Yung | Electronic calendar |
CA2315389A1 (en) * | 1998-01-07 | 1999-07-15 | Microsoft Corporation | System and method of displaying times corresponding to events on a calendar |
CA2418754A1 (en) * | 2002-01-12 | 2003-07-12 | Cognos Incorporated | System and method for automated database report definition |
Non-Patent Citations (2)
Title |
---|
DAWSON C.A.: "Graphical indicator for calendar days that have out-of-sync data", IBM TECHNICAL DISCLOSURE BULLETIN, vol. 35, no. 6, November 1992 (1992-11-01), pages 375 - 377, XP000314189 * |
See also references of EP1880353A4 * |
Also Published As
Publication number | Publication date |
---|---|
EP1880353A1 (en) | 2008-01-23 |
EP1880353A4 (en) | 2009-05-13 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US8434026B2 (en) | System and method for time dimension management for a data analyzing | |
US20190087400A1 (en) | Methods, systems and computer program products for facilitating visualization of interrelationships in a spreadsheet | |
US8190992B2 (en) | Grouping and display of logically defined reports | |
US7716592B2 (en) | Automated generation of dashboards for scorecard metrics and subordinate reporting | |
US5657437A (en) | Data processing apparatus and method including proportional updating of data | |
US7003737B2 (en) | Method for interactive browsing and visualization of documents in real space and time | |
US8839133B2 (en) | Data visualizations including interactive time line representations | |
US7318015B2 (en) | Method, system and program product for generating scenarios utilizing graphical objects representing hierarchically arranged elements of a modeled environment | |
US5873108A (en) | Personal information manager information entry allowing for intermingling of items belonging to different categories within a single unified view | |
US5787417A (en) | Method and system for selection of hierarchically related information using a content-variable list | |
US9058307B2 (en) | Presentation generation using scorecard elements | |
US8418070B2 (en) | Developing user interface element settings | |
US20080172287A1 (en) | Automated Domain Determination in Business Logic Applications | |
US20050091263A1 (en) | Systems and methods for representing and editing multi-dimensional data | |
US20060028917A1 (en) | Milestone bar calender | |
US20040252136A1 (en) | Designing and generating charts to graphically represent data in a data source | |
US8291334B1 (en) | Method and apparatus for creating a digital dashboard | |
US20090288030A1 (en) | System and method for task management | |
US20150269524A1 (en) | Device, method, and computer-readable medium for project management | |
US20080172348A1 (en) | Statistical Determination of Multi-Dimensional Targets | |
US20120304121A1 (en) | Method, processing device, and article of manufacture for providing instructions for displaying time-dependent information and for allowing user selection of time ranges | |
EP1894087A2 (en) | User interface for web analytics tools and methods for automatic generation of calendar notes, targets and alerts | |
MXPA05007073A (en) | User interface for providing task management and calendar information. | |
US20100131889A1 (en) | User interface to explore data objects and their related supplementary data objects | |
Emrouznejad et al. | Introduction to performance improvement management software (PIM-DEA) |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
WWW | Wipo information: withdrawn in national office |
Country of ref document: DE |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2005742644 Country of ref document: EP |
|
NENP | Non-entry into the national phase |
Ref country code: RU |
|
WWW | Wipo information: withdrawn in national office |
Country of ref document: RU |
|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 05742644 Country of ref document: EP Kind code of ref document: A1 |
|
WWP | Wipo information: published in national office |
Ref document number: 2005742644 Country of ref document: EP |