HISTORIAN MODULE FOR USE IN AN INDUSTRIAL AUTOMATION CONTROLLER

• US 20070142941A1
• Filed: 11/10/2006
• Published: 06/21/2007
• Est. Priority Date: 11/14/2005
• Status: Active Grant

• Current Assignee: Rockwell Automation Technologies Incorporated (Rockwell Automation, Inc.)
• Original Assignee: Rockwell Automation Technologies Incorporated (Rockwell Automation, Inc.)
• Inventors: Herbst, Robert, Hartman, Justin, McGreevy, Robert, Sadowski, Deborah
• Granted Patent: US 7,627,385 B2
• Time in Patent Office: Days
• US Class Current: 700/83
• CPC Class Codes: G06Q 10/00 Administration; Management

Abstract

A distributed historian framework is provided where historical data is collected in accordance with an organizational model of a hierarchical system that is distributed across various elements of an enterprise. A directory service operates with the organizational model to enable configuration of historian components within the organization and to enable data to be located within the organization. In one aspect, an industrial automation system is provided. The system includes at least one historian component to archive data within an organization. A common data model then exposes functionality and data of the organization to the historian component.

Claims

1. An industrial automation historian module, comprising:

a module having at least one communications port coupled with a storage medium for collecting historical data from a controller; and

a backplane component within the module to automatically discover one or more tags within the controller.

2. The module of claim 1, further comprising a graphical user interface (GUI) to interact with the module.

3. The module of claim 2, the GUI is provided by a web page.

4. The module of claim 1, the backplane component communicates to one or more other modules across a programmable controller chassis.

5. The module of claim 1, the at least one communications port is associated with an Ethernet port, a universal serial bus port, a common information protocol port, and a computer console port.

6. The module of claim 1, further comprising one or more auto configuration components where one or more historian components are automatically discovered and configured.

7. The module of claim 1, further comprising a component to enable data collection load sharing between historian components.

8. The module of claim 1, further comprising a data structure that represents at least one of an enterprise, a plant, or a control layer within the plant.

9. The module of claim 1, further comprising a publish and subscribe component that enables data to be reported and generated based upon a change in the data.

10. An industrial automation controller, comprising:

a chassis having slots adapted to receive modules;

a processor;

a network in communication with the processor; and

a historian module removably connected in a slot of the chassis;

the historian module having a storage medium in communication with the network to collect historical data from the processor, the historian module adapted to automatically discover data structures associated with the controller.

11. The controller of claim 10, further comprising a backplane component adapted to the historian module to communicate across the chassis.

12. A communications method for a programmable controller backplane, comprising:

adapting a historian module to communicate over a controller chassis;

storing data on the historian module collected from the controller chassis; and

collecting tag data from an industrial controller via the chassis.

13. The method of claim 12, further comprising interfacing to the historian module via a web page.

14. The method of claim 12, further comprising collecting data on the historian module from at least one other chassis across a network.

15. The method of claim 12, further comprising collecting alarm or event data across the chassis.

16. The method of claim 12, further comprising collecting tag data from at least a second industrial controller across the chassis.

17. The method of claim 12, further comprising generating at least one graphical user interface to configure the historian module.

18. The method of claim 12, further comprising storing data on the historian module that has been published from at least one other module.

19. The method of claim 18, further comprising subscribing to data that is stored on the historian module.

20. A rack mounted historian module, comprising:

means for communicating across a controller backplane;

means for storing historian data on the controller backplane; and

means for generating tags on the controller backplane.