Tag management within a decision, support, and reporting environment

• US 7,698,292 B2
• Filed: 11/19/2004
• Issued: 04/13/2010
• Est. Priority Date: 12/03/2003
• Status: Active Grant

• Current Assignee: Siemens AG
• Original Assignee: Siemens AG
• Inventors: DeMesa, Jesse G., Ougarov, Andrei V.
• Primary Examiner(s): Wong; Don
• Assistant Examiner(s): XUE, BIN
• Application Number:
  US10/993,712
• Publication Number:
  US 20050144154A1
• Time in Patent Office: 1,971 Days
• Field of Search: None
• US Class Current: 1/1
• CPC Class Codes: G06F 16/903 Querying for retrieval from the web G06F16/953
• CPC Class Codes: Y10S 707/99943 Generating database or data structure, e.g. via user interface

Abstract

A system and methods for retrieving and presenting data in a tag-based component environment. The disclosed system provides an efficient mechanism for associating point and non-point data using highly configurable data acquisition strategies. The data acquisition strategies incorporate customized retrieval routines to perform data acquisition at desired intervals so as to reduce unnecessary bandwidth consumption and computational overhead.

Claims

1. A system for developing computer models for collection and display of data, the system comprising:

a component builder, executed by a processing device, configured to create a first reusable component definition, the first reusable component definition including at least one component associated with point data and non-point data associated with at least one back-end data source, the point data including data collected from at least one addressable informational source and the non-point data including context-defining data associated with the point data;

a connection for defining a mechanism to utilize the non-point data and other information to uniquely identify the data to be collected from the at least one addressable information source;

a module, executed by a processing device, utilizing said first reusable component definition to build another component definition for at least another component associated with second point data to be collected and second non-point data to be collected, the connection additionally defining a mechanism to utilize the second non-point data and other information to uniquely identify the second point data to be collected;

a view builder operable to generate a first reusable view that corresponds to the first reusable component definition generated by the component builder, wherein the first reusable view defines how the point data and non-point data are to be displayed, the view builder displaying the collected second point data and second non-point data in a view corresponding to the another component definition using a format defined by the first reusable view;

wherein the point data comprises operational data representative of at least one of;

monitoring, control, and reporting functions, relating to operation of a selected back-end data source; and

wherein the view builder provides functionality for inserting a view corresponding to a first component within a view corresponding to a second component such that third point data and third non-point data can be aggregated and displayed in a user-defined manner.

2. The system of claim 1 wherein, the component builder further provides functionality for defining and associating differential collection strategies for the point data and non-point data.

3. The system of claim 2 wherein, the component builder further provides functionality for aggregating the point data and non-point data from a plurality of addressable informational sources while maintaining the differential collection strategies for the point data and non-point data.

4. The system of claim 2 wherein, the differential collection strategies for the point data and non-point data differ with respect to frequency of collection.

5. The system of claim 4 wherein, collection of the point data generally occurs at a greater rate than collection of the non-point data.

6. The system of claim 2 wherein, the differential collection strategies for the point data and non-point data differ with respect to manner in which the point data and non-point data are collected.

7. The system of claim 6 wherein, the point data is collected based upon a publish-and-subscribe data collection approach.

8. The system of claim 6 wherein, the point data is collected as streaming data from the at least one addressable informational source of the back-end data source.

9. The system of claim 6 wherein, the non-point data is collected based upon a structured query approach.

10. The system of claim 6 wherein, the non-point data is collected via application programming interface (API) calls.

11. The system of claim 1 wherein, the point data reflects real-time values associated with the at least one addressable informational source of the at least one back-end data source.

12. The system of claim 11 wherein, the point data collected from the at least one addressable informational source is obtained at a substantially constant time interval to maintain up-to-date information to be displayed by the at least one component associated with the point data and non point data.

13. The system of claim 1 wherein, the non-point data is collected relatively infrequently while still maintaining up-to-date information to be displayed by the at least one component associated with the point data and non point data.

14. The system of claim 1 wherein, the non-point data comprises at least one of:

relational, structural, attribute and documentational data.

15. The system of claim 1 wherein, the component builder provides functionality for generating a composite component that includes at least one previously generated component and wherein a solution builder provides an ability to selectively include at least a portion of the point data and non-point data from the previously generated at least one component within the composite component.

16. The system of claim 1 wherein, the module enables a user to specify a frequency with which the point data and non-point data are to be collected.

17. The system of claim 1 wherein, the module enables a user to separately specify, for each instance of a component, a frequency with which the point data and non-point data are to be collected.

42. The system of claim 1 wherein, the second point data comprises operational data representative of at least one of:

monitoring, control, and reporting functions, relating to operation of a selected back-end data source.

18. A method of generating a computer model for collection and display of aggregated point data and non-point data, the method comprising:

creating a first reusable component definition, the first reusable component definition including at least one component associated with point data and non-point data;

collecting point data associated with the at least one component including data collected from at least one addressable informational source based upon a specified point data acquisition strategy;

collecting non-point data associated with the at least one component including context-defining data associated with the point data based upon a specified non-point data acquisition strategy, the non-point data and other information being used to uniquely identify the point data to be collected in the point data collecting step;

identifying at least one relationship associating the point data and non-point data;

configuring a first reusable aggregate view, corresponding to the first reusable component definition, for displaying the point data and non-point data;

utilizing the first reusable component definition to build another component definition including at least another component associated with second point data and second non-point data, the at least one relationship associating the point data and non-point data identified in the identifying step also being used to associate the second point data and second non-point data; and

displaying the second point data and second non-point data in a second view corresponding to the another component, the second view being configured according to the configuration of the first reusable aggregate view;

wherein a second reusable view component further identifies relationships associating the collected point data and non-point data and displays the point data and non-point data in a second aggregate view by including the first view component such that when a user accesses the second view to view data collected by the second view component, the first aggregate view is displayed within the second aggregate view; and

wherein the point data comprises operational data representative of at least one of;

monitoring, control, and reporting functions, relating to operation of a selected back-end data source.

19. The method of claim 18 wherein, the second reusable component further collects additional point data and non-point data, said second reusable component including the at least one component as a member.

20. The method of claim 18 wherein, the specified point data acquisition strategy and the specified non-point data acquisition strategy differ with respect to the frequency with which the point data and non-point data are collected.

21. The method of claim 18 wherein, the specified point data acquisition strategy and the specified non-point data acquisition strategy differ with respect to the manner in which the point data and non-point data are collected.

22. The method of claim 21 wherein, the specified point data acquisition strategy is based upon a publish-and-subscribe data collection approach.

23. The method of claim 21 wherein, the specified point data acquisition strategy collects streaming data from the at least one addressable informational source.

24. The method of claim 21 wherein, the specified non-point data acquisition strategy is based upon a structured query approach.

25. The method of claim 21 wherein, the specified non-point data acquisition strategy collects data using application programming interface (API) calls.

26. The method of claim 18 wherein, the point data reflects real-time values associated with selected at least one addressable informational source of at least one back-end data source.

27. The method of claim 26 wherein, the point data collected from the at least one addressable informational source is obtained at a user-defined constant time interval to maintain up-to-date information.

28. The method of claim 18 wherein, the non-point data is collected relatively infrequently while still maintaining up-to-date information.

29. The method of claim 18 wherein, the non-point data comprises at least one of:

relational, structural, attribute and documentational data.

43. The method of claim 18 wherein, the second point data comprises operational data representative of at least one of:

monitoring, control, and reporting functions, relating to operation of a selected back-end data source.

30. An apparatus comprising a computer readable medium having instructions stored thereon to represent a collection of data from multiple sources and providing:

at least one instance of at least one base component, each instance of the at least one base component including point data comprising data collected from at least one addressable informational source and non-point data comprising context-defining data associated with the point data;

a connection for defining a mechanism to utilize the non-point data and other information to uniquely identify the data to be collected from the at least one addressable information source;

at least one instance of at least one extended component, each instance of the at least one extended component being generated using the at least one instance of the at least one base component, at least a portion of the point data and non-point data of the at least one base component being used to define the at least one extended component; and

a first reusable view specifying how data collected by the at least one instance of the at least one base component is to be displayed;

said first reusable view additionally specifying how data collected by the at least one extended component is to be displayed in a second view corresponding to the at least one extended component; and

a second reusable view including as a component at least a portion of the first view wherein the second view displays data collected by instances of the at least one base component and the at least one extended component in a display area corresponding to the first view;

wherein the point data and non-point data of the at least one base component are used to model a first business element;

wherein the extended component models a second business element of which the first business element is a logical subunit; and

wherein the base component represents a tag having component members defined thorough the at least one relationship associating the point data and non-point data.

31. The apparatus of claim 30 wherein, the first business element comprises an item selected from the group consisting of:

machinery, equipment, and production.

32. The apparatus of claim 31 wherein, the second business element is selected from the group consisting of:

a plant, facility, and factory.

33. The apparatus of claim 30 wherein, differential collection strategies are used in the collection of the point data and the non-point data.

34. The apparatus of claim 33 wherein, the differential collection strategies for the point data and non-point data differ with respect to frequency of collection.

35. The apparatus of claim 30 wherein, the tag represents a logical collection of point data and non-point data associated with at least one of a selected instrument, operation, function, view and business element.

36. A system for developing computer models for collection and display of data, the system comprising:

a component builder, executed by a processing device, configured to generate a first reusable component definition for collecting first tag-based point data and first non-point data associated with at least one back-end data source, wherein the first tag-based point data comprises data collected from at least one addressable informational source and the first non- point data comprises context-defining data associated with the first tag-based point data;

the component builder further operable to collect second non-point data associated with a non-tag-based informational source;

a connection for defining a mechanism to utilize the first non-point data and other information to uniquely identify the first tag-based point data to be collected from the at least one addressable information source;

a module, executed by a processing device, utilizing said first reusable component definition to build another component definition for collecting second tag-based point data and third non-point data associated with at least one back-end data source, the connection additionally defining a mechanism to utilize the third non-point data and other information to uniquely identify the second tag-based point data to be collected;

a view builder operable to generate a first reusable view corresponding to said first reusable component definition generated by the component builder, whereby a user can generate at least one view that specifies how the second tag-based point data and third non-point data collected by said another component definition are to be displayed;

wherein the first tag-based point data comprises operational data representative of at least one of;

monitoring, control, and reporting functions, relating to operation of a selected back-end data source; and

wherein the view builder provides functionality for inserting a view corresponding to a first component within a view corresponding to a second component such that point data and non-point data can be aggregated and displayed in a user-defined manner.

37. The system of claim 36 wherein, the component builder further provides functionality for defining and associating differential collection strategies for the first tag-based point data and the first non-point data.

38. The system of claim 37 wherein, the component builder further provides functionality for aggregating point data and non-point data from a plurality of addressable informational sources while maintaining the differential collection strategies for the first tag-based point data and the first non-point data.

39. The system of claim 38 wherein, the differential collection strategies for the first tag-based point data and the first non-point data differ with respect to frequency of collection.

40. The system of claim 39 wherein, collection of the first tag-based point data generally occurs at a greater rate than collection of the first non-point data.

41. The system of claim 40 wherein, the differential collection strategies for the first tag-based point data and the first non-point data differ with respect to manner in which the point data and non-point data are collected.

44. The system of claim 36 wherein, the second tag-based point data comprises operational data representative of at least one of:

monitoring, control, and reporting functions, relating to operation of a selected back-end data source.