Forecasting system and method using change data based database storage for efficient ASP and web application

• US 10,074,137 B2
• Filed: 02/14/2017
• Issued: 09/11/2018
• Est. Priority Date: 04/26/2004
• Status: Active Grant

• Current Assignee: Ignite Enterprise Software Solutions, Inc. (Infonow Corporation)
• Original Assignee: Right90, Inc. (ESW Capital, LLC)
• Inventors: Orumchian, Kim, Stabenow, Art, Skelton, Dean, Petiot, David
• Primary Examiner(s): Vy, Hung T
• Application Number:
  US15/432,673
• Publication Number:
  US 20170154381A1
• Time in Patent Office: 574 Days
• Field of Search: 707600
• CPC Class Codes: G06F 16/2228 Indexing structures
• CPC Class Codes: G06F 16/254 Extract, transform and load [ETL] procedures, e.g. ETL data flows in data warehouses
• CPC Class Codes: G06F 16/283 Multi-dimensional databases or data warehouses, e.g. MOLAP or ROLAP
• CPC Class Codes: G06F 16/90335 Query processing
• CPC Class Codes: G06F 2216/03 Data mining
• CPC Class Codes: G06Q 10/04 Forecasting or optimisation specially adapted for administrative or management purposes, e.g. linear programming or "cutting stock problem" market predictions or forecasting for commercial activities G06Q30/0202
• CPC Class Codes: G06Q 10/063 Operations research, analysis or management
• CPC Class Codes: G06Q 10/0631 Resource planning, allocation, distributing or scheduling for enterprises or organisations
• CPC Class Codes: G06Q 30/02 Marketing; Price estimation or determination; Fundraising
• CPC Class Codes: G06Q 30/0202 Market predictions or forecasting for commercial activities
• CPC Class Codes: G06Q 30/06 Buying, selling or leasing transactions
• CPC Class Codes: G06Q 40/04 Trading; Exchange, e.g. stocks, commodities, derivatives or currency exchange
• CPC Class Codes: G06Q 40/06 Asset management; Financial planning or analysis
• CPC Class Codes: Y10S 707/99933 Query processing, i.e. searching
• CPC Class Codes: Y10S 707/99956 File allocation

Abstract

In one embodiment, a system is provided. The system includes a first client. The system also includes an analysis server coupled to the first client. The system further includes a first customer database of information coupled to the analysis server. The first customer database is to embody forecast data and to receive essentially real-time updates to the forecast data. The first customer database supports an OLAP cube associated with the analysis server.

Claims

1. A system comprising:

an analysis server adapted for coupling to at least an external first client and incorporating an analytics and aggregation unit to analyze and update the information in a first customer database; and

a first database of information coupled to the analysis server, the first database embodying forecast data and receiving updates to the forecast data, wherein during operation the analytics and aggregation unit analyze and update the information of at least a first partition of the first database;

wherein the first partition includes only changed data, the amount of data in the first partition is smaller than the amount of data in the second partition, so that there is a relatively low consumption of resources of the analytics and aggregation unit in analyzing and updating the information and in responding to a query, and so that access to the data is accomplished more quickly that if responding to the query required a higher consumption of resources of the analytics and aggregation unit in analyzing and updating the information in the second partition.

2. The system of claim 1, further comprising the at least an external first client.

3. The system of claim 1, wherein the customer database comprises forecast data for a first customer.

4. The system of claim 3, wherein the database comprises a customer database storing forecast data for a second customer.

5. The system of claim 1, wherein the database is a database shared by a plurality of customers, including for a first customer and a second customer.

6. The system of claim 1, wherein the change partition is aggregated by the analysis server.

7. The system of claim 1, wherein the database includes a first partition and a second partition, the first partition including change data and the second partition including general data.

8. The system of claim 1, wherein updating the database includes both adding or changing data and calculating the effects of that added or changed data.

9. The system of claim 1, wherein the first partition containing change data is calculated frequently without using too many analysis server resources due to the small amount of change data included in that second partition.

10. The system of claim 1, wherein analysis server and the database are configured to use the change data in the first partition so that the system only operates on the changed data and performs particularly well in response to a query.

11. The system of claim 10, wherein the query is communicated to both the first and second partitions and accessing data from both partitions, and having the data aggregated to appear as a single query response.

12. The system of claim 1, wherein the system includes provides a world wide web interface and a world wide web hosted forecasting application.

13. The system of claim 1, wherein the system provides for concurrent access by multiple organizations.

14. The system of claim 13, wherein for the multiple organizations, the data in the database is segregated for each different one of the multiple organizations to satisfy confidentiality concerns.

15. The system of claim 14, wherein the first database includes multiple data repositories that may be separate, either logically or physically, or both logically and physically.

16. The system of claim 13, wherein:

a first user uses a first client to access the system, and access a first data repository using the analysis server including the analytics and aggregation unit; and

a second user uses a second client to access the system, and access a second data repository.

17. The system of claim 13, wherein the first user and the second user use the same the analytics and aggregation unit.

18. The system of claim 13, wherein the first user and the second user use a different the analytics and aggregation unit.

19. The system of claim 13, wherein the first user and the second user use a different instantiation of the same analytics and aggregation unit.

20. The system of claim 1, wherein the an analytics and aggregation unit processing facilities are separated, logically, or physically, or both logically and physically.