Subscription methods and systems for component information of a system

• US 9,971,665 B2
• Filed: 03/31/2014
• Issued: 05/15/2018
• Est. Priority Date: 03/31/2014
• Status: Active Grant

• Current Assignee: Honeywell International Inc.
• Original Assignee: Honeywell International Inc.
• Inventors: De Mers, Robert E., Foslien, Wendy
• Primary Examiner(s): Ko, Chae M
• Application Number:
  US14/230,982
• Publication Number:
  US 20150278071A1
• Time in Patent Office: 1,506 Days
• Field of Search: 714 57
• CPC Class Codes: G06F 11/3006 where the computing system is distributed, e.g. networked systems, clusters, multiprocessor systems multiprogramming arrangements G06F9/46; allocation of resources G06F9/50
• CPC Class Codes: G06F 11/3079 the data filtering being achieved by reporting only the changes of the monitored data
• CPC Class Codes: G06F 11/3086 where the reporting involves the use of self describing data formats, i.e. metadata, markup languages, human readable formats
• CPC Class Codes: G06Q 10/20 Administration of product repair or maintenance

Abstract

A method of tracking and reporting data associated with a component of a system is provided. The method includes: creating a subscription that is associated with a component of a system based on subscription parameters; receiving component data associated with the component of the system; and generating reporting data based on the subscription and the component data.

Claims

1. A subscription method of tracking and reporting data associated with a component of a system, comprising:

generating a plurality of reporting data from a first, a second and a third type of interface data wherein the step of generating the first, the second and the third type of interface data from a subscription interface data, a data manager interface data, and a message interface data comprises;

receiving, for the subscription interface data, subscription parameters for defining a subscription and for storing the subscription in a subscription data store;

receiving, for the data manager interface data, user entered component data and component generated data for defining a component report and for storing the component report in a component data store; and

receiving, for the message interface data, message data for defining a message and for storing the message in a message data store; and

evaluating a plurality of subscriptions to determine and to report trigger events by, in a first instance, monitoring the component data store for trigger events and, in a second instance, monitoring the message data store for trigger events wherein in the first instance, generating the reporting data from the plurality of reporting data based on reports and subscription parameters and in the second instance, generating the reporting data from the plurality of reporting data based on messages and subscription parameters and.

2. The method of claim 1, wherein the subscription parameters indicate at least one of types of information associated with a component to subscribe to, a communication medium for receiving the reporting data, who to send the reporting data to, and where to send the reporting data to.

3. The method of claim 1, wherein the creating the subscription is further based on a subscription rule.

4. The method of claim 1, further comprising receiving the subscription parameters based on a user interacting with a user interface.

5. The method of claim 1, wherein the receiving the component data is based on a user interacting with a user interface.

6. The method of claim 1, further comprising communicating the reporting data based on at least a particular subscription.

7. The method of claim 1, further comprising communicating the message reporting data based on at least a particular subscription.

8. A subscription system for tracking and reporting data associated with a component of a system, comprising:

a non-transitory computer readable medium comprising;

a data manager configured for generating a plurality of reporting data from a first, a second and a third type of interface data wherein the first, the second and the third type of interface data are generated by the data manager by processing;

a subscription interface data of the first type of interface data generated by receiving subscription parameters for defining a subscription and for storing the subscription in the subscription data store;

a data manage interface data of the second type of interface data generated by receiving user entered component data and component generated data for defining a component report and for storing the component report in the component data store; and

a message interface data of the third type of interface data generated by receiving message data for defining a message and for storing the message in the message data store; and

a subscription manager configured for evaluating a plurality of subscriptions to determine and to report trigger events by, in a first instance, monitoring the component data store for trigger events and, in a second instance, monitoring the message data store for trigger events wherein in the first instance, generating the reporting data from the plurality of reporting data based on reports and subscription parameters and in the second instance, generating the reporting data from the plurality of reporting data based on messages and subscription parameters.

9. The system of claim 8, wherein the subscription parameters indicate at least one of types of information associated with a component to subscribe to, a communication medium for receiving the reporting data, who to send the reporting data to, and where to send the reporting data to.

10. The system of claim 8, wherein the subscription manager creates the subscription further based on a subscription rule.

11. The system of claim 8, wherein the subscription manager receives the subscription parameters based on a user interacting with a user interface.

12. The system of claim 8, wherein a data manager receives the component data based on a user interacting with a user interface.

13. The system of claim 8, wherein a data reporter communicates the reporting data based on the subscription.

14. The system of claim 8, wherein a message reporter communicates the reporting data based on the subscription.