Annotation of data in an operating plan data aggregation system

• US 8,086,607 B2
• Filed: 04/26/2005
• Issued: 12/27/2011
• 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): Timblin, Robert
• Assistant Examiner(s): Reyes, Mariela D
• Application Number:
  US11/116,125
• Publication Number:
  US 20060080160A1
• Time in Patent Office: 2,436 Days
• Field of Search: 707/737, 707/738, 707/757, 707/758, 707/751
• US Class Current: 707/737
• 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 an embodiment a method is provided. The method includes receiving forecast information in a computer from a first group of users. The method also includes integrating the forecast information into a database and corresponding OLAP cube accessible by the computer. The method further includes receiving comments on specific entries of the forecast information in the computer from a second group of users. The method also includes receiving changes of the forecast information in the computer from a second group of users The method further includes integrating comments and changes into the database and OLAP cube. Moreover, the method includes providing a display of the comments and the changes to the first group of users in an interface to the computer.

Claims

1. A computer implemented method, comprising:

gathering initial future predictive forecast values in a computer from a first group of users;

integrating the initial future predictive forecast values into a database and corresponding OLAP cube accessible by the computer, the OLAP cube providing a capability of presenting, manipulating and analyzing the predictive forecast values from multiple perspectives;

generating a baseline forecast using the initial future predictive forecast values into the database and corresponding OLAP cube;

gathering annotations during a period of time until a final forecast cut-off point is reached including gathering comments on specific entries of the forecast values and changes of the forecast values in the computer after the initial future predictive forecast values are gathered from a second group of users different from the first group of users;

the annotations including comments generated by the second group of users indicating whether the initial future predictive forecast values appear to be incorrect to some of the second group of users and to provide commentary information in association with the forecast values for more meaningful interaction between the first group of users and the second group of users than simple changes to the initial future predictive forecast values and to provide an objective basis for generating a new forecast having modified forecast values;

integrating the gathered annotations including the comments and changes of the forecast values into the database and corresponding OLAP cube in real-time with the gathering of the annotations, the integrating including (i) modifying the initial future predictive forecast values in the database and the OLAP cube based on any changes of the forecast values, and (ii) coupling the gathered annotations to the initial future predictive forecast values or to the modified future predictive forecast values for further review and annotation by the first group of users and the second group of users; and

iteratively generating a revised forecast including gathering revised forecast values and integrated annotations and making the revised forecast values and integrated annotations available for review and further annotation in the computer in real-time until the final forecast cut-off point is reached.

2. The method of claim 1, wherein:

the comments include textual information relating to the forecast values.

3. The method of claim 1, wherein:

the value changes include alterations of the forecast values and the method further includes updating a forecast value using the alterations of the forecast values.

4. The method of claim 1, wherein:

the computer is a network of computers hosting the database and OLAP cube which appears to users as a single computer.

5. The method of claim 3, further comprising:

receiving requests from users to watch specific entities of the forecast; and

providing updates to users having sent the watch requests when specific entity changes responsive to the requests to watch.

6. The method of claim 5, further comprising:

receiving judgments from the second group of users related to a set of forecast values or annotations coupled to the forecast values; and

changing the set of forecast values of the forecast responsive to the judgments.

7. The method of claim 5, further comprising:

receiving a first comment on a specific forecast value;

integrating the first comment into the database and OLAP cube;

receiving a second comment on the specific forecast value;

integrating the second comment into the database and OLAP cube; and

providing the first comment and the second comment to a user of the first group of users responsive to a request from the user of the first group of users.

8. The method of claim 3, wherein:

the comments and changes are received through devices other than the computer, the devices are coupled to the computer for communication.

9. The method of claim 3, wherein:

the forecast value is received and the comments are displayed through devices other than the computer that are coupled to the computer for communication.

10. The method of claim 1, wherein:

the method is executed by a processor in response to instructions, the instructions, embodied in a non-transitory, machine-readable medium.

11. A computer implemented method as in claim 1, wherein the first group of users are users in a sales group and the second group of users are users in at least one of a finance group, and an executive group.

12. A computer implemented method as in claim 11, wherein the finance group users provide annotation information related to financing constraints and financial market conditions which impact sales forecasts made by users in the sales group.

13. A computer implemented method as in claim 11, wherein the annotation changes are made by users in the marketing group and relate to at least one of market conditions, overall relationships with customers, and forecast data available after the data received from the sales group users.

14. A computer implemented method as in claim 11, wherein the second group users executive group annotations are annotations that reflect the executive group expectations for the economy, the executive group expectations for customer relationships, and the executive group expectations for overall business, and reflect executive expectations about actual performance as opposed to forecasted performance by the first group of users.

15. A computer implemented method as in claim 1, wherein the annotation comments and changes are received from the second group of users and pertain to production constraints, inventory considerations, supply chain issues, and allocations of production capacity respective of goods or services identified to the forecast.

16. A computer implemented method as in claim 11, wherein the integration results in generation of an updated forecast in real-time with the receipt of the annotations.

17. A computer implemented method as in claim 1, wherein the annotating is performed in real-time and includes presenting forecast values and any other annotations to at least the second group of users, receiving annotations that include adjustments or changes and comments respective of the forecast data from the second group of users, integrating the adjustments and the comments into the database and OLAP, and generating an updated forecast.

18. A computer implemented method as in claim 1, wherein the adjustments to forecast values include actual changes to the forecast values and the comments include notes about the forecast values, and the adjustments and comments are received essentially simultaneously for a plurality of forecast values and are integrated into the database and the OLAP.

19. A computer implemented method as in claim 1, wherein the adjustments to the forecast values are received at an adjustment module, and comments are received at a comment module, and an integration module receives the adjustments from the adjustments module and the comments from the comments module and integrates the received adjustments and comments into the database and OLAP.

20. A computer implemented method as in claim 1, wherein the first group of users comprises field operative sales users, and the second group of users making the annotations that include the changes and the comments are selected from marketing group users, production group users, operations group users, finance group users, and executive group users, each being different from the field operative sales users.

21. A computer implemented method as in claim 20, wherein the annotation is repeated a plurality of times for the marketing group users, the production group users, the operations group users, the finance group users, and the executive group users, even for the same forecast item value and later users accessing the forecast values are able to view some or all annotations from the earlier annotating users, allowing for further annotation and avoiding duplicative changes and comments.

22. A computer implemented method as in claim 1, wherein a request by a user for forecast values automatically retrieves the forecast values and any annotation associated with the requested forecast values that the requesting user is authorized to receive and view and does not require a separate request for the annotations.

23. A computer implemented method as in claim 1, wherein the first user group forecast value is annotated by the second group user and the annotations are integrated into the database and OLAP, and then the annotated and integrated forecast value is further reviewed and revised by the first group users who disagree with the second group user annotations to the forecast value either because specific information contradicts a more general change or because the first group user believes the value to be inaccurate, and the annotations by the first group users are integrated in the database and the OLAP.

24. A computer implemented method as in claim 23, wherein the further revision by the first user group includes at least one of contesting an earlier annotation, requesting further annotations, and indicating earlier annotations are agreeable.

25. A computer implemented method as in claim 1, wherein the integration process includes alerting a second user group supervisory user to the annotations including to the comments and to the changes.

26. A computer implemented method as in claim 1, wherein the annotations further include active annotation functions that provide an indication of a lack of confidence in part or all of a forecast values without changing that forecast value.

27. A computer implemented method as in claim 1, wherein the annotation includes an indication that a forecast value is contingent on a future event occurring or not occurring.

28. A computer implemented method as in claim 1, wherein the annotation includes a contingency tag indicating how much a forecast value should be changed to handle an identified contingency.

29. A computer implemented method as in claim 1, wherein the contingency has an identified date or a know period of time by which the contingency will be resolved, and the annotation is implemented to notify the second user making the annotation, and the first user whose forecast value was annotated, to check on the status of the contingency.

30. A computer implemented method as in claim 29, wherein the notification comprises an email messages sent at a specified or at predetermined times, and is optionally displayed along with an indication of the impact of the contingency result to the user.

31. A computer implemented method as in claim 1, wherein the annotation states a contingency concern about a forecast value and includes a tag indicating how much the forecast data number should be reduced to handle the contingency concern if the contingency on which the forecast data does not occur.

32. A computer implemented method as in claim 1, wherein the annotations include first annotations to original forecast value and second annotations respective of the first annotations.

33. The method as in claim 1, wherein the first group of users and the second group of users are each groups of users from different groups within the same company organization.

34. The method as in claim 33, wherein the first group of users are from a sales group in the company and the second group of users are from the non-sales financial group or non-sales CEO group of the same company organization.

35. A system comprising:

a processor;

a memory coupled to the processor, having code stored therein and executable by the processor;

to receive future predictive forecast data from a first group of users;

an analysis server including an OLAP cube; and

an information database coupled to the analysis server to support the OLAP cube, the information database to embody the forecast data including forecast numerical values and annotations associated with particular entities of the forecast numerical values including non-numeric textual comments and to receive essentially real-time updates to the forecast data including to the forecast numerical values and to the annotations through the user interface;

the annotations including comments generated by a second group of users different from the first group of users and indicating whether the future predictive forecast data values appear to be incorrect to some of the second group of users and to provide commentary information in association with the forecast values for more meaningful interaction between the first group of users and the second group of users than simple changes to the initial future predictive forecast values and to provide an objective basis for generating a new forecast having modified forecast values; and

wherein the memory further includes code executable by the processor;

(i) to receive the annotations to the forecast data over time from at least the second group of users after the forecast data was submitted by the first group of users, (ii) to integrate the received annotations including received comments and changes of the forecast information into the database and corresponding OLAP cube in real-time with the receipt of the annotations, the integrating including modifying the future predictive forecast values in the database and the OLAP cube based on any changes of the forecast values, and (ii) coupling the received annotations to the future predictive forecast values or to later modified future predictive forecast values for further review and annotation by the first group of users and the second group of users; and

(iii) to iteratively generate a revised forecast including gathering revised forecast values and integrated annotations and making the revised forecast values and integrated annotations available for review and further annotation in real-time until a final forecast cut-off point is reached.

36. The system of claim 35, further comprising:

an identification server coupled to the information database, wherein the identification server being operative to identify a user or user group, including to identify receipt of an annotation from the first user group and from the second user group.

37. The system of claim 36, further comprising:

a client coupled through the user interface to the analysis server and to the identification server.

38. The system of claim 35, wherein:

the system is implemented across a network of computers having networked access to the database and OLAP cube and multiple user interfaces throughout the network.

39. The system of claim 35, wherein:

the information database stores financial information.

40. The system of claim 36, further comprising:

a means for communicating remotely with the system.

41. A system as in claim 35, wherein:

the first group of users are users in a sales group and the second group of users are users in at least one of a marketing group, a finance group, and a executive group, each different from the sales group;

the integration results in generation of an updated forecast in real-time with the annotations;

the annotating of data is performed in real-time and includes presenting forecast values to at least the second group of users, receiving annotations that include adjustments or changes and comments respective of the forecast values from the second group of users, integrating the adjustments and the comments into the database and OLAP, and generating an updated forecast;

the adjustments to forecast data include actual changes to the forecast values and the comments include notes about the forecast values, and the adjustments and comments are received essentially simultaneously for a plurality of forecast values and are integrated into the database and the OLAP;

the adjustments to the forecast values are received at an adjustment module, and comments are received at a comment module, and an integration module receives the adjustments from the adjustments module and the comments from the comments module and integrates the received adjustments and comments the into the database and OLAP;

the annotation is repeated a plurality of times for the marketing group users, the production group users, the operations group users, the finance group users, and the executive group users, even for the same item of forecast value and later users access the forecast values are able to view some or all annotations from the earlier annotating users, allowing for further annotation and avoiding duplicative changes and comments;

a request by a user for forecast value automatically retrieves the forecast value and any annotation associated with the requested forecast value that the requesting user is authorized to receive and view and does not require a separate request for the annotation; and

the annotations further include active annotation functions that provide an indication of a lack of confidence in part or all of a forecast value without changing that forecast value.

42. The system as in claim 35, wherein the first group of users and the second group of users are each groups of uses from different groups within the same company organization.

43. The system as in claim 42, wherein the first group of users are from a sales group in the company and the second group of users are from the non-sales financial group or non-sales CEO group of the same company organization.