Process data management

• US 7,142,929 B2
• Filed: 06/09/2005
• Issued: 11/28/2006
• Est. Priority Date: 12/11/2002
• Status: Expired due to Fees

• Current Assignee: Frayson Systems Limited
• Original Assignee: Frayson Systems Limited
• Inventors: Gallagher, Finbar
• Primary Examiner(s): PHAM, THOMAS K
• Application Number:
  US11/148,349
• Publication Number:
  US 20050228506A1
• Time in Patent Office: 537 Days
• Field of Search: 700/19, 700/20, 709/203, 709/213, 709/216, 709/219, 709/229, 709/205, 707/100, 707/101
• US Class Current: 700/19
• CPC Class Codes: G05B 19/41845 characterised by system universality, reconfigurability, modularity
• CPC Class Codes: G05B 19/4185 characterised by the network communication
• CPC Class Codes: G05B 2219/31094 Data exchange between modules, cells, devices, processors
• CPC Class Codes: G05B 2219/31156 Network structure, internet
• CPC Class Codes: G05B 2219/32126 Hyperlink, access to program modules and to hardware modules in www, web server, browser
• CPC Class Codes: G05B 2219/32404 Scada supervisory control and data acquisition
• CPC Class Codes: G05B 2219/32406 Distributed scada
• CPC Class Codes: Y02P 90/02 Total factory control, e.g. smart factories, flexible manufacturing systems [FMS] or integrated manufacturing systems [IMS]

Abstract

A process data management system (1) has a number of modules (2 –6) each of which can operate independently to capture, process, and record process data from machines (P1–P6). The modules also communicate with each other via a messaging service (21, 40) so that data can be routed between components (22 –24, 42, 43, 45) of different modules using the Push mechanism. A Graphical data object (GDO) server (25, 45, 46) downloads applet instances to user browsers in response to the browser addressing a URL. The applet generates an output display in chart form of real time processed data.

Claims

1. A process data management system comprising a machine interface for receiving process data of a process operation, and a processor for processing the data, wherein,

the system comprises a plurality of modules, each module comprising a data collector component for capturing process source data, and a data logger component for saving data whereby each module is capable of operating independently to capture process source data, to process the source data to provide processed data, and to save the processed data;

the data logger component saves the processed data in a format for storage in a universal storage structure used by all of the modules of the system;

the universal storage structure comprises a hierarchy of process activities containing sub-activities, and leaf node activities containing event nodes for storing data;

the top level of the hierarchy is an overall production process, and activity nodes represent specific process activities forming part of the production process;

the data logger component saves both source data and processed data and links each item of processed data to the source data from which it is derived;

each module comprises a messaging service for communication of data between modules;

at least some modules comprise a data processor component for receiving source data from the data collector component and for generating processed data for output and for logging by the data logger component; and

at least some data processor components transmit via the messaging service processed data to the data logger component or the data processor component of a different module of the system or receive data via the messaging service data from the data collector of a different module of the system.

2. The system as claimed in claims 1, wherein at least some data collector components translate source data to provide data in the universal storage structure.

3. The system as claimed in claim 2, wherein the data collector component initially parses source data to provide the data in a mark-up language format, and translates the mark-up language to provide the universal storage structure format.

4. The system as claimed in claim 1, wherein the links between source data and processed data are activity source event records within the universal storage structure.

5. The system as claimed in claim 1, wherein at least some modules contain a graphical data object server for transmitting a display program to a user for display of processed data outputted by a data processor.

6. The system as claimed in claim 1, wherein at least some modules contain a graphical data object server for transmitting a display program to a user for display of processed data outputted by a data processor;

and wherein each graphical data object server transmits a program in response to a user browser accessing an internet or intranet address.

7. The system as claimed in claim 1, wherein at least some modules contain a graphical data object server for transmitting a display program to a user for display of processed data outputted by the data processor component;

and wherein each graphical data object server transmits a program in response to a user browser accessing an internet or intranet address; and

wherein the address is an Internet URL.

8. The system as claimed in claim 1, wherein at least some modules contain a graphical data object server for transmitting a display program to a user for display of processed data outputted by the data processor component;

and wherein the program is executable code which uses parameters hosted on the module of the graphical data object server.

9. The system as claimed in claim 1, wherein at least some modules contain a graphical data object server for transmitting a display program to a user for display of processed data outputted by the data processor component;

and wherein a plurality of different graphical data object servers download programs for data output with different output formats.

10. The system as claimed in claim 1, wherein at least some modules contain a graphical data object server for transmitting a display program to a user for display of processed data outputted by the data processor component;

and wherein the program is executable code which uses parameters hosted on the module of the graphical data object server; and

wherein each module downloads a plurality of URLs for user to select from.

11. The system as claimed in claim 1, wherein at least some modules contain a graphical data object server for transmitting a display program to a user for display of processed data outputted by the data processor component;

and wherein the server downloads multiple instances of a particular display program to a plurality of requesting users.

12. The system as claimed in claim 1, wherein at least some modules contain a graphical data object server for transmitting a display program to a user for display of processed data outputted by the data processor component;

and wherein the program is executable code which uses parameters hosted on the module of the graphical data object server; and

wherein there is only one parameter set per program per graphical data object server.

13. The system as claimed in claim 1, wherein each module comprises a management interface for configuring its module to comprise a desired configuration of components and the messaging service by adding, deleting, or modifying components and configuring the messaging service.

14. The system as claimed in claim 1, wherein each module comprises a management interface for configuring its module to comprise a desired configuration of components and the messaging service by adding, deleting, or modifying components and configuring the messaging service;

and wherein the management interface monitors the state and activities of the components and the messaging service.

15. The system as claimed in claim 1, wherein each module comprises a management interface for configuring its module to comprise a desired configuration of components and the messaging service by adding, deleting, or modifying components and configuring the messaging service;

and wherein the components and the messaging service are objects which are objects which are instantiated by the management interface.

16. The system as claimed in claim 1, wherein each module comprises a management interface for configuring its module to comprise a desired configuration of components and the messaging service by adding, deleting, or modifying components and configuring the messaging service;

and wherein the management interface operates to activate the module, to dynamically re-configure the module, and to shut down the module.

17. The system as claimed in claim 1, wherein the data logger, the data collector, and the data processor components communicate data to each other using a push mechanism in which a receiving component is a subscriber.

18. A process data management method carried out by a system comprising a plurality of modules, each module comprising a data collector component for capturing process source data from a machine implementing a production process, and a data logger component for saving data whereby each module is capable of operating independently to capture process source data, to process the source data to provide processed data, and to save the processed data, wherein each module comprises a messaging service for communication of data between modules, wherein at least some modules comprise a data processor component for receiving source data from the data collector component and for generating processed data for output and for logging by the data logger component, and wherein the method comprises the steps of:

the data logger component of each module saving the processed data in a format for storage in a universal storage structure used by all of the modules of the system, wherein the universal storage structure comprises a hierarchy of process activities containing sub-activities, and leaf node activities containing event nodes for storing data, and wherein the top level of the hierarchy is the overall production process, and activity nodes represent specific process activities forming part of the production process;

the data logger component saving both source data and processed data and linking each item of processed data to the source data from which it is derived; and

at least some data processors transmitting via the messaging service processed data to the data logger component or the data processor component of a different module of the system, or receive via the messaging service data from the data collector of a different module of the system.

19. A computer program product comprising software code for performing operations of a method of claim 18 when executing on a digital computer.