Annotation of data in an operating plan data aggregation system

• US 10,229,176 B2
• Filed: 11/03/2014
• Issued: 03/12/2019
• 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): Burke, Jeffrey A
• Assistant Examiner(s): Vu, Thong
• Application Number:
  US14/531,592
• Publication Number:
  US 20150066838A1
• Time in Patent Office: 1,590 Days
• Field of Search: 707737, 707767, 705 2664, 705301, 705 28
• 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 method comprising:

executing non-transitory code, stored in a memory, by a computer system that transforms the computer system into a machine that performs;

connecting to data sources of a first group of users and a second group of users;

receiving future predictive forecast data in the computer system from the first group of users;

receiving essentially real-time updates to the forecast data including to the forecast numerical values and to the annotations;

integrating the forecast data into an information database and corresponding OLAP cube accessible by the computer system, wherein;

(i)the information database stores the forecast data including forecast numerical values and annotations associated with particular entities of the forecast numerical values including non-numeric textual comments;

(ii) the essentially real-time updates to the forecast and the annotations (a) include comments generated by the second group of users different from the first group of users, (b) indicate whether the future predictive forecast data values appear to be incorrect to some of the second group of users, (c) 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 (d) provide an objective basis for generating a new forecast having modified forecast values;

integrating in real-time the real-time updates and the annotations into the information database and the OLAP cube, wherein integrating the real-time updates and annotations includes (i) 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

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 real-time until a final forecast cut-off point is reached.

2. The method of claim 1 wherein the memory further includes code executable by the processor for:

identifying a user or user group, including to identify receipt of an annotation from the first user group and from the second user group.

3. The method of claim 1 wherein the memory further includes code executable by the processor for:

connecting to computer systems of the first group of users and the second group of users, wherein the computer systems are implemented across a network having networked access to the database and OLAP cube and multiple user interfaces throughout the network.

4. The method of claim 3 wherein the memory further includes code executable by the processor for:

communicating remotely with the computer systems of the first group of users and the second group of users.

5. The method of claim 1, wherein the first group of users are users in a sales group and the second group of users are users in an executive group.

6. The method of claim 1, wherein updates to the annotations made by users in the second group of users and relate to at least one of market conditions, overall relationships with customers, and forecast data available after the data received from the first group users.

7. The method of claim 1, wherein the annotations by the second group of users are executive group annotations that reflect customer relationships, overall business, and reflect executive expectations about actual performance as opposed to forecasted performance by the first group of users.

8. The method of claim 1, wherein the annotation comments and updates 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 data.

9. The method of claim 1, wherein integrating in real-time the real-time updates and annotations results in generation of an updated forecast in real-time with the receipt of the annotations.

10. The method of claim 1, wherein the updates to forecast data include actual changes to the forecast values and the comments include notes about the forecast values, and the updates and comments are received essentially simultaneously for a plurality of forecast values and are integrated into the database and the OLAP.

11. The method of claim 10, wherein the updates to the forecast data 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.

12. The method of claim 1, wherein 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, and executive group users, each being different from the first group of users.

13. The method of claim 1, 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 at least a proper subset of annotations from the earlier annotating users, allowing for further annotation and avoiding duplicative changes and comments.

14. The method of claim 1 wherein the memory further includes code executable by the processor for:

receiving a request by a user for forecast values; and

in response to the request, automatically retrieving the forecast values and any annotations 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.

15. The method of claim 1, wherein the memory further includes code executable by the processor for:

receiving revisions by the first user group includes at least one of contesting an earlier annotation, requesting further annotations, and indicating earlier annotations are agreeable.

16. The method of claim 1, wherein the integrating element includes alerting a second user group supervisory user to the annotations including to the comments and to the changes.

17. The method of 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.

18. The method of claim 1, wherein the annotation includes an indication that a forecast value is contingent on a future event occurring or not occurring.

19. The method of claim 1, wherein the annotation includes a contingency tag indicating how much a forecast value should be changed to handle an identified contingency.

20. The method of claim 1, wherein the annotation includes a contingency tag indicating how much a forecast value should be changed to handle an identified contingency, the contingency has an identified date or a known period of time by which the contingency will be resolved, and the annotation is implemented in a notification 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.

21. The method of 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 marketing group, a finance group, and a executive group, each different from the sales group;

the annotations include 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 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 updates to the 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 updates 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 annotations are repeated a plurality of times for the first and second groups of 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 data automatically retrieves the forecast data and any annotation associated with the requested forecast data 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.

22. The method of 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.

23. The method of claim 1, wherein the annotations include first annotations to original forecast value and second annotations respective of the first annotations.

24. The method of claim 21, wherein the notification comprises an email message sent at a specified or at predetermined times and is optionally displayed along with an indication of the impact of the contingency result to each recipient of the message.

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

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