US20130290374A1 - Data federation with industrial control systems - Google Patents
Data federation with industrial control systems Download PDFInfo
- Publication number
- US20130290374A1 US20130290374A1 US13/933,008 US201313933008A US2013290374A1 US 20130290374 A1 US20130290374 A1 US 20130290374A1 US 201313933008 A US201313933008 A US 201313933008A US 2013290374 A1 US2013290374 A1 US 2013290374A1
- Authority
- US
- United States
- Prior art keywords
- industrial
- hierarchical
- data structure
- hierarchical data
- defining
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Images
Classifications
-
- G06F17/30589—
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/28—Databases characterised by their database models, e.g. relational or object models
- G06F16/282—Hierarchical databases, e.g. IMS, LDAP data stores or Lotus Notes
-
- G—PHYSICS
- G05—CONTROLLING; REGULATING
- G05B—CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
- G05B19/00—Programme-control systems
- G05B19/02—Programme-control systems electric
- G05B19/418—Total factory control, i.e. centrally controlling a plurality of machines, e.g. direct or distributed numerical control [DNC], flexible manufacturing systems [FMS], integrated manufacturing systems [IMS], computer integrated manufacturing [CIM]
- G05B19/4188—Total factory control, i.e. centrally controlling a plurality of machines, e.g. direct or distributed numerical control [DNC], flexible manufacturing systems [FMS], integrated manufacturing systems [IMS], computer integrated manufacturing [CIM] characterised by CIM planning or realisation
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
-
- G—PHYSICS
- G05—CONTROLLING; REGULATING
- G05B—CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
- G05B2219/00—Program-control systems
- G05B2219/30—Nc systems
- G05B2219/31—From computer integrated manufacturing till monitoring
- G05B2219/31393—Object oriented engineering data management
-
- G—PHYSICS
- G05—CONTROLLING; REGULATING
- G05B—CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
- G05B2219/00—Program-control systems
- G05B2219/30—Nc systems
- G05B2219/31—From computer integrated manufacturing till monitoring
- G05B2219/31395—Process management, specification, process and production data, middle level
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02P—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN THE PRODUCTION OR PROCESSING OF GOODS
- Y02P90/00—Enabling technologies with a potential contribution to greenhouse gas [GHG] emissions mitigation
- Y02P90/02—Total factory control, e.g. smart factories, flexible manufacturing systems [FMS] or integrated manufacturing systems [IMS]
Definitions
- the subject invention relates generally to industrial control systems and more particularly to distributing and manipulating data across data hierarchies that can be shared between organizational models and industrial control systems.
- Industrial controllers are special-purpose computers utilized for controlling industrial processes, manufacturing equipment, and other factory automation, such as data collection or networked systems.
- a logic processor such as a Programmable Logic Controller (PLC) or PC-based controller.
- PLC Programmable Logic Controller
- Programmable Logic Controllers for instance, are programmed by systems designers to operate manufacturing processes via user-designed logic programs or user programs.
- the user programs are stored in memory and generally executed by the PLC in a sequential manner although instruction jumping, looping and interrupt routines, for example, are also common.
- Associated with the user program are a plurality of memory elements or variables that provide dynamics to PLC operations and programs. Differences in PLCs are typically dependent on the number of Input/Output (I/O) they can process, amount of memory, number and type of instructions, and speed of the PLC central processing unit (CPU).
- I/O Input/Output
- An organizational model and addressing mode is provided that enables data to be automatically and efficiently exchanged from various layers of an organization, across organizational boundaries, and/or exchanged between lower-level control entities to upper-tiers of the organization.
- a hierarchical model of an organization is distributed across control systems and other components of the organization such as business computers.
- Such hierarchy can be stored in an instantiation of a controller which is also accessible by the controller.
- This enables external applications to address data in the controller via a controller namespace and/or via an organization hierarchy such as provided by a hierarchical plant model, for example. Portions of the hierarchy can be implemented in the controller without being connected to the central system. This enables distributed development by multiple users such as outside equipment manufacturers (OEMs).
- OEMs outside equipment manufacturers
- the organizational hierarchy can also include other organizational units, controller scoped tags, programs with associated program scoped tags, add-on instructions, routines, operator interface screens, and/or user defined information such has procedures and help files, for example.
- a local hierarchy stored in a controller can be connected to the system hierarchy via a “mount point.”
- the “mount point” can be connected with a particular location in the system hierarchy during a configuration operation which associates the respective controller with a specific organizational project.
- FIG. 1 is a schematic block diagram illustrating data federation in an organizational data model.
- FIG. 2 is a diagram illustrating an example organizational hierarchy.
- FIG. 3 is a diagram illustrating an example business model and hierarchical data representation that has been federated across an enterprise and control systems.
- FIG. 4 is a diagram illustrating a flat and hierarchal data representation for a controller.
- FIG. 5 is a diagram illustrating a mount point for a control system hierarchy.
- FIG. 6 is a diagram illustrating multiple mount points for a control system hierarchy.
- FIG. 7 is a diagram illustrating multiple mount point for a control system hierarchy and combined naming conventions.
- FIG. 8 is a diagram illustrating an example system for processing model data structures.
- FIG. 9 is a flow diagram illustrating a control data and enterprise federation process.
- FIG. 10 illustrates exemplary hierarchies that can be utilized in connection with the hierarchically structured data model.
- FIG. 11 illustrates exemplary hierarchies that can be utilized in connection with the hierarchically structured data model.
- FIG. 12 illustrates an exemplary combination of hierarchies.
- FIG. 13 illustrates an exemplary combination of hierarchies.
- An organizational model of a hierarchical system can be distributed across various elements of an enterprise. Such elements include representations of the system that are maintained on higher-level business servers and other representations that serve control elements of the system such as programmable logic controllers and/or other industrial control components.
- an industrial automation system is provided. The system includes at least one controller to instantiate a portion of an organizational hierarchy. A communications component in the controller interacts with at least one other portion of the organizational hierarchy to facilitate data exchange and control between various components of an enterprise.
- a component may be, but is not limited to being, a process running on a processor, a processor, an object, an executable, a thread of execution, a program and a computer.
- an application running on a server and the server can be components.
- One or more components may reside within a process and/or thread of execution and a component may be localized on one computer and/or distributed between two or more computers, industrial controllers, and/or modules communicating therewith.
- a system 100 illustrates data federation concepts in an organizational data model.
- a hierarchical data model 110 is illustrated having various nodes and branches that store data at multiple locations throughout the system 100 .
- Such model 110 can be distributed across a network 114 to provide a collective or federated database.
- an enterprise 120 may have one or more computers or network components that communicate across the network 114 to one or more industrial control components 130 such as programmable logic controllers (PLCs) 130 .
- PLCs programmable logic controllers
- the data hierarchy 110 having data nodes and branches can be managed as a singular or collective entity while being viewed, managed and distributed across substantially all or portions of the enterprise 120 and/or PLC 130 .
- the system 100 enables combining organizational information called an organizational or hierarchical data model 110 which represents a common model of a plant that can be based in the S88 or S95 model, for example, and is distributed among computers of the enterprise 120 and industrial controllers 130 , for example.
- the model 110 can be viewed as an Organizational Model—a tree-like hierarchical and heterogeneous structure of organizational Units.
- respective Organizational Units may include other Organizational Units.
- Organizational Units can be either physical locations (e.g., Site, Area) or logical grouping node or collection (e.g., Enterprise as a collection of Sites).
- the nodes in the organizational hierarchy or model 110 can have associated items representing the plant's production and control equipment, tags, backing tags (e.g., Alarm & Event and AOI objects), programs, equipment phases, I/O devices, and other application related entities. These organizational units thus can form an application view of the user's system.
- a typical system 100 can assign the upper levels of the hierarchy such as an Enterprise node and site to a computer system and the lower levels such as area, line, cell and machine could be contained in multiple industrial controllers each of which can include components which are members of one or more organization units such as area or area model.
- An organization unit such as area can contain components from one or more controllers.
- IT information technology
- the enterprise 120 can include various computer or network components such as servers, clients, communications modules, mobile computers, wireless components, and so forth which are capable of interacting across the network 114 .
- the term PLC as used herein can include functionality that can be shared across multiple components, systems, and or networks 114 .
- one or more PLCs 130 can communicate and cooperate with various network devices across the network 114 . This can include substantially any type of control, communications module, computer, I/O device, Human Machine Interface (HMI)) that communicate via the network 114 which includes control, automation, and/or public networks.
- the PLC 130 can also communicate to and control various other devices such as Input/Output modules including Analog, Digital, Programmed/Intelligent I/O modules, other programmable controllers, communications modules, and the like.
- the network 114 can include public networks such as the Internet, Intranets, and automation networks such as Control and Information Protocol (CIP) networks including DeviceNet and ControlNet. Other networks include Ethernet, DH/DH+, Remote I/O, Fieldbus, Modbus, Profibus, wireless networks, serial protocols, and so forth.
- the network devices can include various possibilities (hardware and/or software components). These include components such as switches with virtual local area network (VLAN) capability, LANs, WANs, proxies, gateways, routers, firewalls, virtual private network (VPN) devices, servers, clients, computers, configuration tools, monitoring tools, and/or other devices.
- VLAN virtual local area network
- WANs wide area network
- proxies gateways
- routers virtual private network
- VPN virtual private network
- GUI Graphical User Interface
- interfaces can be provided to manipulate the hierarchical or organizational data model 110 where various examples are illustrated in more detail below.
- This can include a Graphical User Interface (GUI) to interact with the model 110 or other components of the hierarchy such as any type of application that sends, retrieves, processes, and/or manipulates factory or enterprise data, receives, displays, formats, and/or communicates data, and/or facilitates operation of the enterprise 120 and/or PLCs 130 .
- GUI Graphical User Interface
- such interfaces can also be associated with an engine, server, client, editor tool or web browser although other type applications can be utilized.
- the GUI can include a display having one or more display objects (not shown) for manipulating the model 110 including such aspects as configurable icons, buttons, sliders, input boxes, selection options, menus, tabs and so forth having multiple configurable dimensions, shapes, colors, text, data and sounds to facilitate operations with the model 110 .
- the GUI can also include a plurality of other inputs or controls for adjusting and configuring one or more aspects. This can include receiving user commands from a mouse, keyboard, speech input, web site, remote web service and/or other device such as a camera or video input to affect or modify operations of the GUI.
- FIGS. 3-8 are directed to exemplary hierarchies and data arrangements. It is to be appreciated however than substantially any data hierarchy that is distributed across an enterprise or business and/or shared across an industrial control system is within the scope contemplated herein.
- the example structure 200 includes an enterprise level 202 , where a particular enterprise can be represented within data structured in accordance with a hierarchical data model. Beneath the enterprise level 202 can be a site level 204 , so that a particular factory (site) within an enterprise can be represented within a data packet. Beneath the site level 204 an area level 206 can exist, which specifies an area within the factory that relates to the data.
- a line level 208 can lie beneath the area level 206 , wherein the line level 208 is indicative of a line associated with particular data. Beneath the line level 208 a work-cell level 210 can exist, thereby indicating a work-cell associated with the data.
- PLCs can become more aware of data associated therewith.
- the hierarchy 200 can be customized by an owner of such hierarchy. For instance, more granular objects/levels can be defined within the hierarchy 200 .
- FIG. 3 an example business model 300 and hierarchical data representation is illustrated that has been federated across an enterprise and control systems.
- an enterprise 310 is represented in the model 300 which is at the highest levels of an organization.
- a commodity such as potato chips are produced by the enterprise.
- higher or lower levels than the enterprise 310 can be represented in the model 300 .
- Beneath the enterprise level two plants are represented at a site level 314 (e.g., one plant in Dallas and another in Detroit) although more or less than two shown can be employed.
- a site level 314 e.g., one plant in Dallas and another in Detroit
- an area of a site includes some of the automated manufacturing processes for the site 314 such as slicing, washing, frying and packaging in this example.
- a line level 330 can be represented which includes equipment (further divided into work-cell), controllers, production components, segment components, and miscellaneous components such as training elements, quality control data, and maintenance data.
- a control level 340 logic processors that execute sequential function charts or ladder logic are represented.
- data from the control view 340 is aggregated and federated from the top down where the data model shows a unified view of data that is distributed across remote or local geographic locations via network communications yet represented as a singular data model 300 .
- components for processing data include work order elements, material managers, equipment sequencers, and production sequencers that may execute on machines such as batch processors or servers, for example.
- FIG. 4 illustrates flat and hierarchal data representations 400 for a controller.
- controller data representations can be integrated with hierarchical enterprise elements described above.
- a flat representation at 410 shows a program engine that can start and stop two motors.
- a hierarchical view 420 of the same data structure 410 can be represented in the controller as well.
- portions of an organizational hierarchy are stored in a runtime instantiation of a controller's operating environment which is accessible by a communications layer of the controller (e.g., controller foreground loop interfacing to a TCP/IP or Control Net stack). This will enable an external application executing at other levels of the hierarchy to address data in the controller via the flat controller name space at 410 and/or via the organizational hierarchy at 420 .
- portions of the hierarchy can be implemented in the controller without being connected to a central system. This enables distributed development by multiple users such as OEMs and systems designers, for example.
- the organizational hierarchy can also include other organizational units, controller scoped tags, programs with associated program scoped tags, add-on instructions, routines, operator interfaces, and/or user defined information such has procedures and help files, for example.
- FIGS. 5-7 illustrate a mount point examples for control system hierarchies.
- Mount points represent where in a distributed data hierarchy the controller is responsible for maintaining data at or below such level of mount point. Data above such level can be stored on enterprise components such as client or server computers in the enterprise.
- the local hierarchy in a controller is connected to the system hierarchy 500 via a “mount point” at 510 .
- This “mount point” 510 can be connected with a particular location in the system hierarchy during a configuration operation which associates this controller with a specific hierarchical project.
- the mount point 510 can be positioned at different portions of the hierarchy 500 .
- an organization unit such as area 700 can be composed of components from multiple industrial controllers at 710 and 720 . It is noted that organization units from multiple controllers with the same name can be combined.
- FIG. 8 illustrates an example system 800 for processing model data structures.
- the system 800 includes an enterprise computer 810 , an application 820 for modifying data structures, configuration components 830 , and one or more control racks 840 .
- an IT developer via an application can define a data structure 820 which can be deployed in the controller 840 .
- the definition can be in the form of an XML file that describes the data structure, and the meaning for each of the respective members. This XML description could also be combined with other descriptions which would form a set of system structures.
- These definitions could be stored in a file which can be distributed to remote users with separate copies of the configuration software 830 , if desired.
- a control engineer could then create instances of these system structures and fill in the data to enable sending the data to the IT applications 820 .
- These system structures may be based on plant data standards such as S88 and S95, for example although other standards can be applied.
- the control system can also have a mechanism to enable a controller to originate a transactions based on an instruction in the controller that uses a system data structure as defined herein.
- the organizational structure or model can provide a way to indicate where a controller variable should be public or private and if public whether it can be written. Generally, only the subset of controller tags specified as public should appear in the organizational hierarchy.
- FIG. 9 illustrates an organizational model and communications process 900 . While, for purposes of simplicity of explanation, the methodology is shown and described as a series of acts, it is to be understood and appreciated that the methodology is not limited by the order of acts, as some acts may occur in different orders and/or concurrently with other acts from that shown and described herein. For example, those skilled in the art will understand and appreciate that a methodology could alternatively be represented as a series of interrelated states or events, such as in a state diagram. Moreover, not all illustrated acts may be required to implement a methodology as described herein.
- FIG. 9 illustrates a control model and communications process 900 .
- a one or more data structures are defined within the domain of a controller. This includes storing portions of a hierarchical model in a runtime instantiation of a controller or component associated with a controller. Such structures can be configured with controller configuration software for defining address locations for various components and network data.
- respective data structures defined at 910 are associated with a communications layer of the controller or control components. The layer can communicate with substantially any type of network including factory networks, global networks such as the internet, wireless networks, and so forth.
- portions of the organizational hierarchy that are stored on the controller can be communicated and interacted with other enterprise components across respective networks.
- data for the enterprise and control systems are aggregated at a particular node or at a given network location. This could include aggregating or collecting, viewing, or collecting data at a network computer that communicates with the various data nodes of the enterprise and control hierarchy and then presenting such data at a display interface in a hierarchical form.
- data is managed across the enterprise or organization via the hierarchical organization model. This can include viewing upper layers of the organization in higher level nodes of the hierarchy, where such layers may conform to such standards as S88 or S95 as previously noted.
- Data structures can be defined which exchange data between substantially all layers of an organization from lower-level control and configuration layers on a network to higher level data nodes of the enterprise.
- Respective nodes can be adapted with varying levels of security to control the type of human or machine access to a data node that may be available from different portions of the hierarchy.
- a first hierarchy 1000 illustrates a representation of equipment within a plant given disparate processes.
- a hierarchy in accordance with a batch process can include a representation of an enterprise, site, area, process cell, unit, equipment module, and control module.
- a hierarchical representation of equipment within a continuous process can include representations of an enterprise, site, area, production unit, continuous unit, equipment module, and control module.
- an enterprise can represent an entirety of a company
- a site can represent a particular plant
- an area can represent a portion of the plant
- a process cell can include equipment utilized to complete a process
- a unit can relate to a unit of machinery within the process cell
- an equipment module can include a logical representation of portions of the process cell
- the control module can include basic elements, such as motors, valves, and the like.
- equipment modules can include equipment modules and control modules can include control modules.
- a second hierarchy 1002 can be utilized that represents each of the aforementioned hierarchical representations.
- the hierarchy 1002 can include representations of an enterprise, a site, an area, a work center, a work unit, an equipment module, and a control module.
- a common representation can be generated that adequately represents the hierarchy 1000 .
- data objects can be associated with metadata indicating which type of process they are associated with. Therefore, data objects can be provided to an operator in a form that is consistent with normal usage within such process.
- batch operators can utilize different terminology than a continuous process operator (as shown by the hierarchy 1000 ). Metadata can be employed to enable display of such data in accordance with known, conventional usage of such data.
- a schema in accordance with the hierarchy 1002 will be seamless to operators.
- only a portion of such representation can be utilized in a schema that is utilized by a controller. For instance, it may be desirable to house equipment modules and control modules within a controller. In another example, it may be desirable to include data objects representative of work centers and work units within a controller (but not equipment modules or control modules). The claimed subject matter is intended to encompass all such deviations of utilizing the hierarchy 1002 (or similar hierarchy) within a controller.
- a hierarchy 1100 represents procedures that can exist within a batch process.
- a procedure can relate to a high-level procedure, such as creation of a pharmaceutical drug.
- a unit procedure can be more specific, such as adding particular chemicals to a mix by way of a particular unit.
- a unit operation can be still more specific, and a phase can be yet more specific (relating to operation of low-level machines).
- a phase can relate to various states which can exist with respect to low-level equipment, such as stopping, starting, and pausing a motor, opening and closing a valve, and the like.
- a hierarchy 1102 relating to a representation of equipment in, for example, a batch process is displayed adjacent to the hierarchy 1100 . The representations within the hierarchy 1102 were described in greater detail with respect to FIG. 10 .
- FIG. 12 a hierarchy 1200 that represents one possible integration of the hierarchies 1100 and 1102 ( FIG. 11 ) is illustrated.
- a unit (such as a work unit described in FIG. 10 ) can be associated with an equipment procedure, an equipment unit procedure, an equipment operation, and an equipment phase).
- the procedures, operation, and phase can be associated with a particular work unit.
- An equipment module can be associated with one or more equipment phases, and can be above a control module in the hierarchy.
- FIG. 13 a hierarchy 1300 that can be utilized in connection with equipment control is illustrated. The hierarchy is substantially similar to that described within the unit portion of the equipment unit. As stated above, the hierarchies illustrated in FIGS.
- 11-13 can be based upon a standard, such as ISA 88, ISA 95, or other standard. Any suitable representation that can be utilized to model an entirety of a plant, however, is contemplated. Further, the representations shown in these figures can be directly implemented into a controller. For instance, data objects in accordance with any portion of the hierarchies described in FIGS. 11-13 can be existent within a controller, together with state machines that enable creation of such objects.
Abstract
An organizational model of a hierarchical system can be distributed across various elements of an enterprise. Such elements include representations of the system that are maintained on higher-level business servers and other representations that serve control elements of the system such as programmable logic controllers and/or other industrial control components. In one aspect, an industrial automation system is provided. The system includes at least one controller to instantiate a portion of an organizational hierarchy. A communications component in the controller interacts with at least one other portion of the organizational hierarchy to facilitate data exchange and control between various components of an enterprise.
Description
- This application is a continuation of U.S. patent application Ser. No. 11/239,937, filed on Sep. 30, 2005, and entitled “DATA FEDERATION WITH INDUSTRIAL CONTROL SYSTEMS,” the entirety of which is incorporated herein by reference.
- The subject invention relates generally to industrial control systems and more particularly to distributing and manipulating data across data hierarchies that can be shared between organizational models and industrial control systems.
- Industrial controllers are special-purpose computers utilized for controlling industrial processes, manufacturing equipment, and other factory automation, such as data collection or networked systems. At the core of the industrial control system, is a logic processor such as a Programmable Logic Controller (PLC) or PC-based controller. Programmable Logic Controllers for instance, are programmed by systems designers to operate manufacturing processes via user-designed logic programs or user programs. The user programs are stored in memory and generally executed by the PLC in a sequential manner although instruction jumping, looping and interrupt routines, for example, are also common. Associated with the user program are a plurality of memory elements or variables that provide dynamics to PLC operations and programs. Differences in PLCs are typically dependent on the number of Input/Output (I/O) they can process, amount of memory, number and type of instructions, and speed of the PLC central processing unit (CPU).
- In a more macro sense than the controller, businesses have become more complex in that higher order business systems or computers often need to exchange data with such controllers. For instance, an industrial automation enterprise may include several plants in different locations. Modern drivers such as efficiency and productivity improvement, and cost-reduction, are requiring manufacturers to collect, analyze, and optimize data and metrics from global manufacturing sites. For example, a food company may have several plants located across the globe for producing a certain brand of food. These factories in the past were standalone, with minimum data collection and comparison of metrics with other similar factories. In the networked world of today, manufacturers are demanding real-time data from their factories to drive optimization and productivity. Unfortunately, conventional control systems architectures are not equipped to allow a seamless exchange of data between these various components of the enterprise.
- The following presents a simplified summary in order to provide a basic understanding of some aspects described herein. This summary is not an extensive overview nor is intended to identify key/critical elements or to delineate the scope of the various aspects described herein. Its sole purpose is to present some concepts in a simplified form as a prelude to the more detailed description that is presented later.
- An organizational model and addressing mode is provided that enables data to be automatically and efficiently exchanged from various layers of an organization, across organizational boundaries, and/or exchanged between lower-level control entities to upper-tiers of the organization. In one aspect, a hierarchical model of an organization is distributed across control systems and other components of the organization such as business computers. Such hierarchy can be stored in an instantiation of a controller which is also accessible by the controller. This enables external applications to address data in the controller via a controller namespace and/or via an organization hierarchy such as provided by a hierarchical plant model, for example. Portions of the hierarchy can be implemented in the controller without being connected to the central system. This enables distributed development by multiple users such as outside equipment manufacturers (OEMs).
- The organizational hierarchy can also include other organizational units, controller scoped tags, programs with associated program scoped tags, add-on instructions, routines, operator interface screens, and/or user defined information such has procedures and help files, for example. A local hierarchy stored in a controller can be connected to the system hierarchy via a “mount point.” The “mount point” can be connected with a particular location in the system hierarchy during a configuration operation which associates the respective controller with a specific organizational project.
- To the accomplishment of the foregoing and related ends, certain illustrative aspects are described herein in connection with the following description and the annexed drawings. These aspects are indicative of various ways which can be practiced, all of which are intended to be covered herein. Other advantages and novel features may become apparent from the following detailed description when considered in conjunction with the drawings.
-
FIG. 1 is a schematic block diagram illustrating data federation in an organizational data model. -
FIG. 2 is a diagram illustrating an example organizational hierarchy. -
FIG. 3 is a diagram illustrating an example business model and hierarchical data representation that has been federated across an enterprise and control systems. -
FIG. 4 is a diagram illustrating a flat and hierarchal data representation for a controller. -
FIG. 5 is a diagram illustrating a mount point for a control system hierarchy. -
FIG. 6 is a diagram illustrating multiple mount points for a control system hierarchy. -
FIG. 7 is a diagram illustrating multiple mount point for a control system hierarchy and combined naming conventions. -
FIG. 8 is a diagram illustrating an example system for processing model data structures. -
FIG. 9 is a flow diagram illustrating a control data and enterprise federation process. -
FIG. 10 illustrates exemplary hierarchies that can be utilized in connection with the hierarchically structured data model. -
FIG. 11 illustrates exemplary hierarchies that can be utilized in connection with the hierarchically structured data model. -
FIG. 12 illustrates an exemplary combination of hierarchies. -
FIG. 13 illustrates an exemplary combination of hierarchies. - An organizational model of a hierarchical system can be distributed across various elements of an enterprise. Such elements include representations of the system that are maintained on higher-level business servers and other representations that serve control elements of the system such as programmable logic controllers and/or other industrial control components. In one aspect, an industrial automation system is provided. The system includes at least one controller to instantiate a portion of an organizational hierarchy. A communications component in the controller interacts with at least one other portion of the organizational hierarchy to facilitate data exchange and control between various components of an enterprise.
- It is noted that as used in this application, terms such as “component,” “hierarchy,” “model, ” and the like are intended to refer to a computer-related entity, either hardware, a combination of hardware and software, software, or software in execution as applied to an automation system for industrial control. For example, a component may be, but is not limited to being, a process running on a processor, a processor, an object, an executable, a thread of execution, a program and a computer. By way of illustration, both an application running on a server and the server can be components. One or more components may reside within a process and/or thread of execution and a component may be localized on one computer and/or distributed between two or more computers, industrial controllers, and/or modules communicating therewith.
- Referring initially to
FIG. 1 , asystem 100 illustrates data federation concepts in an organizational data model. Ahierarchical data model 110 is illustrated having various nodes and branches that store data at multiple locations throughout thesystem 100.Such model 110 can be distributed across anetwork 114 to provide a collective or federated database. As illustrated, anenterprise 120 may have one or more computers or network components that communicate across thenetwork 114 to one or moreindustrial control components 130 such as programmable logic controllers (PLCs) 130. Thus, thedata hierarchy 110 having data nodes and branches can be managed as a singular or collective entity while being viewed, managed and distributed across substantially all or portions of theenterprise 120 and/orPLC 130. - The
system 100 enables combining organizational information called an organizational orhierarchical data model 110 which represents a common model of a plant that can be based in the S88 or S95 model, for example, and is distributed among computers of theenterprise 120 andindustrial controllers 130, for example. Themodel 110 can be viewed as an Organizational Model—a tree-like hierarchical and heterogeneous structure of organizational Units. For instance, respective Organizational Units may include other Organizational Units. Organizational Units can be either physical locations (e.g., Site, Area) or logical grouping node or collection (e.g., Enterprise as a collection of Sites). The nodes in the organizational hierarchy ormodel 110 can have associated items representing the plant's production and control equipment, tags, backing tags (e.g., Alarm & Event and AOI objects), programs, equipment phases, I/O devices, and other application related entities. These organizational units thus can form an application view of the user's system. - A
typical system 100 can assign the upper levels of the hierarchy such as an Enterprise node and site to a computer system and the lower levels such as area, line, cell and machine could be contained in multiple industrial controllers each of which can include components which are members of one or more organization units such as area or area model. An organization unit such as area can contain components from one or more controllers. To ease the integration of data with information technology (IT) applications, methods are provided for defining various data structures in the IT space and translating those to the controller and a method using transactions to connect the controller and IT versions of the structure. - Before proceeding, it is noted that the
enterprise 120 can include various computer or network components such as servers, clients, communications modules, mobile computers, wireless components, and so forth which are capable of interacting across thenetwork 114. Similarly, the term PLC as used herein can include functionality that can be shared across multiple components, systems, and ornetworks 114. For example, one ormore PLCs 130 can communicate and cooperate with various network devices across thenetwork 114. This can include substantially any type of control, communications module, computer, I/O device, Human Machine Interface (HMI)) that communicate via thenetwork 114 which includes control, automation, and/or public networks. ThePLC 130 can also communicate to and control various other devices such as Input/Output modules including Analog, Digital, Programmed/Intelligent I/O modules, other programmable controllers, communications modules, and the like. - The
network 114 can include public networks such as the Internet, Intranets, and automation networks such as Control and Information Protocol (CIP) networks including DeviceNet and ControlNet. Other networks include Ethernet, DH/DH+, Remote I/O, Fieldbus, Modbus, Profibus, wireless networks, serial protocols, and so forth. In addition, the network devices can include various possibilities (hardware and/or software components). These include components such as switches with virtual local area network (VLAN) capability, LANs, WANs, proxies, gateways, routers, firewalls, virtual private network (VPN) devices, servers, clients, computers, configuration tools, monitoring tools, and/or other devices. - In addition to various hardware and/or software components, various interfaces can be provided to manipulate the hierarchical or
organizational data model 110 where various examples are illustrated in more detail below. This can include a Graphical User Interface (GUI) to interact with themodel 110 or other components of the hierarchy such as any type of application that sends, retrieves, processes, and/or manipulates factory or enterprise data, receives, displays, formats, and/or communicates data, and/or facilitates operation of theenterprise 120 and/orPLCs 130. For example, such interfaces can also be associated with an engine, server, client, editor tool or web browser although other type applications can be utilized. - The GUI can include a display having one or more display objects (not shown) for manipulating the
model 110 including such aspects as configurable icons, buttons, sliders, input boxes, selection options, menus, tabs and so forth having multiple configurable dimensions, shapes, colors, text, data and sounds to facilitate operations with themodel 110. In addition, the GUI can also include a plurality of other inputs or controls for adjusting and configuring one or more aspects. This can include receiving user commands from a mouse, keyboard, speech input, web site, remote web service and/or other device such as a camera or video input to affect or modify operations of the GUI. - Before proceeding, it is noted that
FIGS. 3-8 are directed to exemplary hierarchies and data arrangements. It is to be appreciated however than substantially any data hierarchy that is distributed across an enterprise or business and/or shared across an industrial control system is within the scope contemplated herein. - Referring now to
FIG. 2 , an exemplaryhierarchical structure 200 which can be utilized in connection with the hierarchically structured data model described herein is illustrated. For example, the data model can facilitate nested structures, thereby mitigating deficiencies associated with data models that employ flat namespaces although flat namespaces can be employed as well. Theexample structure 200 includes anenterprise level 202, where a particular enterprise can be represented within data structured in accordance with a hierarchical data model. Beneath theenterprise level 202 can be asite level 204, so that a particular factory (site) within an enterprise can be represented within a data packet. Beneath thesite level 204 anarea level 206 can exist, which specifies an area within the factory that relates to the data. Aline level 208 can lie beneath thearea level 206, wherein theline level 208 is indicative of a line associated with particular data. Beneath the line level 208 a work-cell level 210 can exist, thereby indicating a work-cell associated with the data. Utilizing a nested, hierarchical data model, PLCs can become more aware of data associated therewith. Furthermore, thehierarchy 200 can be customized by an owner of such hierarchy. For instance, more granular objects/levels can be defined within thehierarchy 200. - Turning to
FIG. 3 , anexample business model 300 and hierarchical data representation is illustrated that has been federated across an enterprise and control systems. In this example, anenterprise 310 is represented in themodel 300 which is at the highest levels of an organization. In this specific example, a commodity such as potato chips are produced by the enterprise. As can be appreciated, higher or lower levels than theenterprise 310 can be represented in themodel 300. Beneath the enterprise level, two plants are represented at a site level 314 (e.g., one plant in Dallas and another in Detroit) although more or less than two shown can be employed. At 320, an area of a site includes some of the automated manufacturing processes for thesite 314 such as slicing, washing, frying and packaging in this example. - From the
respective area level 320, aline level 330 can be represented which includes equipment (further divided into work-cell), controllers, production components, segment components, and miscellaneous components such as training elements, quality control data, and maintenance data. At acontrol level 340, logic processors that execute sequential function charts or ladder logic are represented. Thus, from the highlevel enterprise view 310, data from thecontrol view 340 is aggregated and federated from the top down where the data model shows a unified view of data that is distributed across remote or local geographic locations via network communications yet represented as asingular data model 300. At production andsegment levels 350, components for processing data include work order elements, material managers, equipment sequencers, and production sequencers that may execute on machines such as batch processors or servers, for example. -
FIG. 4 illustrates flat andhierarchal data representations 400 for a controller. In this aspect, controller data representations can be integrated with hierarchical enterprise elements described above. Here, two views are shown. A flat representation at 410 shows a program engine that can start and stop two motors. Ahierarchical view 420 of thesame data structure 410 can be represented in the controller as well. In general, portions of an organizational hierarchy are stored in a runtime instantiation of a controller's operating environment which is accessible by a communications layer of the controller (e.g., controller foreground loop interfacing to a TCP/IP or Control Net stack). This will enable an external application executing at other levels of the hierarchy to address data in the controller via the flat controller name space at 410 and/or via the organizational hierarchy at 420. As can be appreciated, portions of the hierarchy can be implemented in the controller without being connected to a central system. This enables distributed development by multiple users such as OEMs and systems designers, for example. The organizational hierarchy can also include other organizational units, controller scoped tags, programs with associated program scoped tags, add-on instructions, routines, operator interfaces, and/or user defined information such has procedures and help files, for example. -
FIGS. 5-7 illustrate a mount point examples for control system hierarchies. Mount points represent where in a distributed data hierarchy the controller is responsible for maintaining data at or below such level of mount point. Data above such level can be stored on enterprise components such as client or server computers in the enterprise. As illustrated inFIG. 5 , the local hierarchy in a controller is connected to thesystem hierarchy 500 via a “mount point” at 510. This “mount point” 510 can be connected with a particular location in the system hierarchy during a configuration operation which associates this controller with a specific hierarchical project. Also, it is noted that themount point 510 can be positioned at different portions of thehierarchy 500.FIG. 6 shows asingle controller 600 that supports multiple “mount points” at 610 and 620 which can be mounted at different levels of the system hierarchy. AtFIG. 7 , an organization unit such asarea 700 can be composed of components from multiple industrial controllers at 710 and 720. It is noted that organization units from multiple controllers with the same name can be combined. -
FIG. 8 illustrates anexample system 800 for processing model data structures. Thesystem 800 includes anenterprise computer 810, anapplication 820 for modifying data structures,configuration components 830, and one or more control racks 840. In general, an IT developer via an application can define adata structure 820 which can be deployed in thecontroller 840. The definition can be in the form of an XML file that describes the data structure, and the meaning for each of the respective members. This XML description could also be combined with other descriptions which would form a set of system structures. These definitions could be stored in a file which can be distributed to remote users with separate copies of theconfiguration software 830, if desired. A control engineer could then create instances of these system structures and fill in the data to enable sending the data to theIT applications 820. These system structures may be based on plant data standards such as S88 and S95, for example although other standards can be applied. The control system can also have a mechanism to enable a controller to originate a transactions based on an instruction in the controller that uses a system data structure as defined herein. The organizational structure or model can provide a way to indicate where a controller variable should be public or private and if public whether it can be written. Generally, only the subset of controller tags specified as public should appear in the organizational hierarchy. -
FIG. 9 illustrates an organizational model andcommunications process 900. While, for purposes of simplicity of explanation, the methodology is shown and described as a series of acts, it is to be understood and appreciated that the methodology is not limited by the order of acts, as some acts may occur in different orders and/or concurrently with other acts from that shown and described herein. For example, those skilled in the art will understand and appreciate that a methodology could alternatively be represented as a series of interrelated states or events, such as in a state diagram. Moreover, not all illustrated acts may be required to implement a methodology as described herein. -
FIG. 9 illustrates a control model andcommunications process 900. Proceeding to 910, a one or more data structures are defined within the domain of a controller. This includes storing portions of a hierarchical model in a runtime instantiation of a controller or component associated with a controller. Such structures can be configured with controller configuration software for defining address locations for various components and network data. At 920, respective data structures defined at 910 are associated with a communications layer of the controller or control components. The layer can communicate with substantially any type of network including factory networks, global networks such as the internet, wireless networks, and so forth. At 930, portions of the organizational hierarchy that are stored on the controller can be communicated and interacted with other enterprise components across respective networks. This can include exchanging data from various portions of the enterprise over the network at different nodes and paths of the hierarchy or model. At 940, data for the enterprise and control systems are aggregated at a particular node or at a given network location. This could include aggregating or collecting, viewing, or collecting data at a network computer that communicates with the various data nodes of the enterprise and control hierarchy and then presenting such data at a display interface in a hierarchical form. - At 950, data is managed across the enterprise or organization via the hierarchical organization model. This can include viewing upper layers of the organization in higher level nodes of the hierarchy, where such layers may conform to such standards as S88 or S95 as previously noted. Data structures can be defined which exchange data between substantially all layers of an organization from lower-level control and configuration layers on a network to higher level data nodes of the enterprise. Respective nodes can be adapted with varying levels of security to control the type of human or machine access to a data node that may be available from different portions of the hierarchy.
- Now turning to
FIG. 10 , hierarchical representations that can be employed in connection with a schema employed by programmable logic controllers to facilitate use of a hierarchically structured data model are illustrated. The hierarchies illustrated in this figure relate to equipment hierarchies, which can be integrated with procedure hierarchies to generate a robust representation of a plant (which is incorporated within a schema for use in connection with industrial controllers). Afirst hierarchy 1000 illustrates a representation of equipment within a plant given disparate processes. For instance, a hierarchy in accordance with a batch process can include a representation of an enterprise, site, area, process cell, unit, equipment module, and control module. In contrast, a hierarchical representation of equipment within a continuous process can include representations of an enterprise, site, area, production unit, continuous unit, equipment module, and control module. In still more detail, an enterprise can represent an entirety of a company, a site can represent a particular plant, an area can represent a portion of the plant, a process cell can include equipment utilized to complete a process, a unit can relate to a unit of machinery within the process cell, an equipment module can include a logical representation of portions of the process cell, and the control module can include basic elements, such as motors, valves, and the like. Furthermore, equipment modules can include equipment modules and control modules can include control modules. Thus, as can be discerned from the figure, four disparate hierarchical representations can be employed to represent equipment within batch processes, continuous processes, discrete processes, and inventory. - A
second hierarchy 1002 can be utilized that represents each of the aforementioned hierarchical representations. Thehierarchy 1002 can include representations of an enterprise, a site, an area, a work center, a work unit, an equipment module, and a control module. Thus, a common representation can be generated that adequately represents thehierarchy 1000. For purposes of consistent terminology, data objects can be associated with metadata indicating which type of process they are associated with. Therefore, data objects can be provided to an operator in a form that is consistent with normal usage within such process. For example, batch operators can utilize different terminology than a continuous process operator (as shown by the hierarchy 1000). Metadata can be employed to enable display of such data in accordance with known, conventional usage of such data. Thus, implementation of a schema in accordance with thehierarchy 1002 will be seamless to operators. Furthermore, in another example, only a portion of such representation can be utilized in a schema that is utilized by a controller. For instance, it may be desirable to house equipment modules and control modules within a controller. In another example, it may be desirable to include data objects representative of work centers and work units within a controller (but not equipment modules or control modules). The claimed subject matter is intended to encompass all such deviations of utilizing the hierarchy 1002 (or similar hierarchy) within a controller. - Now referring to
FIG. 11 , standard hierarchies that can be utilized to represent procedures and equipment are illustrated. In particular, ahierarchy 1100 represents procedures that can exist within a batch process. For instance, a procedure can relate to a high-level procedure, such as creation of a pharmaceutical drug. A unit procedure can be more specific, such as adding particular chemicals to a mix by way of a particular unit. A unit operation can be still more specific, and a phase can be yet more specific (relating to operation of low-level machines). For instance, a phase can relate to various states which can exist with respect to low-level equipment, such as stopping, starting, and pausing a motor, opening and closing a valve, and the like. Ahierarchy 1102 relating to a representation of equipment in, for example, a batch process is displayed adjacent to thehierarchy 1100. The representations within thehierarchy 1102 were described in greater detail with respect toFIG. 10 . - Now turning to
FIG. 12 , ahierarchy 1200 that represents one possible integration of thehierarchies 1100 and 1102 (FIG. 11 ) is illustrated. A unit (such as a work unit described inFIG. 10 ) can be associated with an equipment procedure, an equipment unit procedure, an equipment operation, and an equipment phase). Thus, the procedures, operation, and phase can be associated with a particular work unit. An equipment module can be associated with one or more equipment phases, and can be above a control module in the hierarchy. Referring Briefly toFIG. 13 , ahierarchy 1300 that can be utilized in connection with equipment control is illustrated. The hierarchy is substantially similar to that described within the unit portion of the equipment unit. As stated above, the hierarchies illustrated inFIGS. 11-13 can be based upon a standard, such as ISA 88, ISA 95, or other standard. Any suitable representation that can be utilized to model an entirety of a plant, however, is contemplated. Further, the representations shown in these figures can be directly implemented into a controller. For instance, data objects in accordance with any portion of the hierarchies described inFIGS. 11-13 can be existent within a controller, together with state machines that enable creation of such objects. - What has been described above includes various exemplary aspects. It is, of course, not possible to describe every conceivable combination of components or methodologies for purposes of describing these aspects, but one of ordinary skill in the art may recognize that many further combinations and permutations are possible. Accordingly, the aspects described herein are intended to embrace all such alterations, modifications and variations that fall within the spirit and scope of the appended claims. Furthermore, to the extent that the term “includes” is used in either the detailed description or the claims, such term is intended to be inclusive in a manner similar to the term “comprising” as “comprising” is interpreted when employed as a transitional word in a claim.
Claims (20)
1. A system that facilitates data federation, comprising:
a processor, coupled to a memory, that executes computer-executable components, the computer-executable components comprising:
a configuration component configured to receive first configuration information that defines a mount point of an industrial controller, wherein the mount point defines a location in a hierarchical data structure where a first subset of the hierarchical data structure stored on the industrial controller connects to a second subset of the hierarchical data structure; and
an aggregation component configured to aggregate the first portion of the hierarchical data structure and the second portion of the hierarchical data structure at the location based on the mount point.
2. The system of claim 1 , wherein the hierarchical data structure comprises a hierarchical model of an industrial organization.
3. The system of claim 2 , wherein the hierarchical model defines at least one of a plant level of the industrial organization or an enterprise level of the industrial organization.
4. The system of claim 1 , wherein the configuration component is further configured to receive second configuration input that facilitates creation of the first subset of the hierarchical data structure in the industrial controller.
5. The system of claim 4 , wherein the first subset of the hierarchical data structure comprises a first set of nodes that define first hierarchical relationships between first entities relating to control of an industrial asset of an industrial organization.
6. The system of claim 5 , wherein the second subset of the hierarchical data structure comprises a second set of nodes that define second hierarchical relationships between second entities of the industrial organization.
7. The system of claim 6 , wherein the second entities relate to a business operation of the industrial organization.
8. The system of claim 5 , wherein the first set of nodes are associated with a set of data items stored on the industrial controller.
9. The system of claim 2 , wherein the hierarchical data structure defines at least a line level of the industrial organization, wherein the line level comprises at least one of an equipment component, a control component, a production component, a segment component, or a miscellaneous component.
10. The system of claim 1 , wherein the computer-executable components further comprise a controller component configured to convert a flat data structure to a hierarchical format based on the hierarchical data structure.
11. The system of claim 1 , wherein the configuration component is further configured to receive second configuration information that sets a tag associated with the hierarchical data structure as one of public or private, and wherein setting the tag as public renders the tag viewable from an application that reads data from the industrial controller.
12. A method for federation of data, comprising:
defining a mount point for an industrial controller, wherein the mount point defines a location within a hierarchical data structure at which a first portion of the hierarchical data structure that is stored on the industrial controller connects to a second portion of the hierarchical data structure that is stored on a device that communicates with the industrial controller; and
aggregating the first portion of the hierarchical data structure and the second portion of the hierarchical data structure based on the mount point.
13. The method of claim 12 , further comprising defining the first portion of the hierarchical data structure in the controller, wherein the defining the first portion comprises defining one or more first nodes that define first hierarchical relationships between first entities relating to control of an industrial asset of an industrial enterprise.
14. The method of claim 13 , further comprising defining the second portion of the hierarchical data structure in the device, wherein the defining the second portion comprises defining one or more second nodes that define second hierarchical relationships between second entities of the industrial enterprise.
15. The method of claim 14 , wherein the defining the second portion comprises defining the second hierarchical relationships between the second entities relating to one or more business operations of the industrial enterprise.
16. The method of claim 14 , wherein the defining the first portion or the defining the second portion comprises defining at least one of a line level of the industrial enterprise, wherein the line level comprises at least one of an equipment component, a control component, a production component, a segment component, or a miscellaneous component.
17. The method of claim 12 , further comprising at least one of converting a flat data structure to a hierarchical format based on the hierarchical data structure.
18. A computer-readable storage device having stored thereon computer-executable instructions that, in response to execution, cause a computing system including a processor to perform operations, the operations comprising:
defining a mount point of an industrial controller, wherein the mount point defines a node of a hierarchical data model at which a first subset of the hierarchical data model that is stored in the industrial controller connects to a second portion of the hierarchical data model that is stored in a device that is networked to the industrial controller; and
aggregating the first subset of the hierarchical data model and the second subset of the hierarchical data model based on the mount point.
19. The computer-readable storage device of claim 18 , wherein the operations further comprise defining the first subset of the hierarchical data model in the industrial controller, wherein the defining the first subset comprises defining one or more first hierarchical relationships between first entities relating to control of an industrial asset of an industrial enterprise.
20. The computer-readable storage device of claim 18 , wherein the operations further comprise defining the second subset of the hierarchical data model in the device, wherein the defining the second subset comprises defining one or more second hierarchical relationships between second entities relating to a business operation of the industrial enterprise.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US13/933,008 US20130290374A1 (en) | 2005-09-30 | 2013-07-01 | Data federation with industrial control systems |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US11/239,937 US8484250B2 (en) | 2005-09-30 | 2005-09-30 | Data federation with industrial control systems |
US13/933,008 US20130290374A1 (en) | 2005-09-30 | 2013-07-01 | Data federation with industrial control systems |
Related Parent Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US11/239,937 Continuation US8484250B2 (en) | 2005-09-30 | 2005-09-30 | Data federation with industrial control systems |
Publications (1)
Publication Number | Publication Date |
---|---|
US20130290374A1 true US20130290374A1 (en) | 2013-10-31 |
Family
ID=37517866
Family Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US11/239,937 Active 2028-12-11 US8484250B2 (en) | 2005-09-30 | 2005-09-30 | Data federation with industrial control systems |
US13/933,008 Pending US20130290374A1 (en) | 2005-09-30 | 2013-07-01 | Data federation with industrial control systems |
Family Applications Before (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US11/239,937 Active 2028-12-11 US8484250B2 (en) | 2005-09-30 | 2005-09-30 | Data federation with industrial control systems |
Country Status (3)
Country | Link |
---|---|
US (2) | US8484250B2 (en) |
EP (1) | EP1770464A3 (en) |
CN (1) | CN1952815A (en) |
Cited By (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20170337283A1 (en) * | 2014-11-07 | 2017-11-23 | Rockwell Automation Technologies, Inc. | Dynamic search engine for an industrial environment |
US9864786B2 (en) | 2014-11-10 | 2018-01-09 | Red Hat, Inc. | Native federation view suggestion |
US10156842B2 (en) | 2015-12-31 | 2018-12-18 | General Electric Company | Device enrollment in a cloud service using an authenticated application |
US10210208B2 (en) | 2014-11-10 | 2019-02-19 | Red Hat, Inc. | Viewable suggestions for federation engine |
US10796156B2 (en) | 2016-04-19 | 2020-10-06 | Rockwell Automation Technologies, Inc. | Analyzing video streams in an industrial environment to identify potential problems and select recipients for a display of video streams related to the potential problems |
US11221661B2 (en) | 2019-01-14 | 2022-01-11 | Rockwell Automation Technologies, Inc. | Method for auto-discovery and categorization of a plants power and energy smart devices for analytics |
Families Citing this family (38)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US9565275B2 (en) | 2012-02-09 | 2017-02-07 | Rockwell Automation Technologies, Inc. | Transformation of industrial data into useful cloud information |
WO2008036058A2 (en) | 2005-03-16 | 2008-03-27 | Cluster Resources, Inc. | On-demand computing environment |
CN101529345B (en) * | 2005-05-13 | 2011-10-19 | 洛克威尔自动控制技术股份有限公司 | Distributed database in an industrial automation environment |
US8392008B2 (en) | 2006-10-20 | 2013-03-05 | Rockwell Automation Technologies, Inc. | Module arbitration and ownership enhancements |
US7844349B2 (en) | 2006-10-20 | 2010-11-30 | Rockwell Automation Technologies, Inc. | Standard MES interface for discrete manufacturing |
US8601435B2 (en) | 2006-10-20 | 2013-12-03 | Rockwell Automation Technologies, Inc. | Module class subsets for industrial control |
US7684877B2 (en) | 2006-10-20 | 2010-03-23 | Rockwell Automation Technologies, Inc. | State propagation for modules |
US7680550B2 (en) | 2006-10-20 | 2010-03-16 | Rockwell Automation Technologies, Inc. | Unit module state processing enhancements |
US7725200B2 (en) | 2006-10-20 | 2010-05-25 | Rockwell Automation Technologies, Inc. | Validation of configuration settings in an industrial process |
US7894917B2 (en) | 2006-10-20 | 2011-02-22 | Rockwell Automation Technologies, Inc. | Automatic fault tuning |
US7676292B2 (en) | 2006-10-20 | 2010-03-09 | Rockwell Automation Technologies, Inc. | Patterns employed for module design |
US9317494B2 (en) * | 2007-04-03 | 2016-04-19 | Sap Se | Graphical hierarchy conversion |
US20090089359A1 (en) * | 2007-09-27 | 2009-04-02 | Rockwell Automation Technologies, Inc. | Subscription and notification in industrial systems |
US20090171897A1 (en) * | 2007-12-28 | 2009-07-02 | Ulrich Spinola | Method and system for case management |
US20090271721A1 (en) * | 2008-04-29 | 2009-10-29 | Rockwell Automation Technologies, Inc. | Organizational roll-up/down |
DE102008048552B4 (en) * | 2008-09-17 | 2014-02-27 | Khs Gmbh | Method for operating an industrial system |
DE102008062934A1 (en) * | 2008-12-23 | 2010-06-24 | Kuka Roboter Gmbh | Networked industrial controller and method for changing the operating mode of such an industrial controller |
US9477936B2 (en) | 2012-02-09 | 2016-10-25 | Rockwell Automation Technologies, Inc. | Cloud-based operator interface for industrial automation |
US9047463B2 (en) * | 2012-06-29 | 2015-06-02 | Sri International | Method and system for protecting data flow at a mobile device |
US20140214801A1 (en) * | 2013-01-29 | 2014-07-31 | Vito Anthony Ciliberti, III | System and Method for Enterprise Asset Management and Failure Reporting |
US9911163B2 (en) * | 2013-03-15 | 2018-03-06 | Rockwell Automation Technologies, Inc. | Systems and methods for determining energy information using an organizational model of an industrial automation system |
US9709978B2 (en) | 2013-05-09 | 2017-07-18 | Rockwell Automation Technologies, Inc. | Using cloud-based data for virtualization of an industrial automation environment with information overlays |
US10026049B2 (en) | 2013-05-09 | 2018-07-17 | Rockwell Automation Technologies, Inc. | Risk assessment for industrial systems using big data |
US9786197B2 (en) | 2013-05-09 | 2017-10-10 | Rockwell Automation Technologies, Inc. | Using cloud-based data to facilitate enhancing performance in connection with an industrial automation system |
US9989958B2 (en) | 2013-05-09 | 2018-06-05 | Rockwell Automation Technologies, Inc. | Using cloud-based data for virtualization of an industrial automation environment |
US9438648B2 (en) | 2013-05-09 | 2016-09-06 | Rockwell Automation Technologies, Inc. | Industrial data analytics in a cloud platform |
US9703902B2 (en) | 2013-05-09 | 2017-07-11 | Rockwell Automation Technologies, Inc. | Using cloud-based data for industrial simulation |
US10078314B2 (en) | 2014-01-29 | 2018-09-18 | Siemens Aktiengesellschaft | Method for providing functions within an industrial automation system, and industrial automation system |
EP2902857B1 (en) * | 2014-01-29 | 2018-12-19 | Siemens Aktiengesellschaft | Method for providing functions within an industrial automation system and industrial automation system |
DE102014013943A1 (en) * | 2014-09-19 | 2016-03-24 | Abb Technology Ag | Device for managing and configuring field devices of an automation system |
US10496061B2 (en) * | 2015-03-16 | 2019-12-03 | Rockwell Automation Technologies, Inc. | Modeling of an industrial automation environment in the cloud |
US11513477B2 (en) | 2015-03-16 | 2022-11-29 | Rockwell Automation Technologies, Inc. | Cloud-based industrial controller |
US11042131B2 (en) | 2015-03-16 | 2021-06-22 | Rockwell Automation Technologies, Inc. | Backup of an industrial automation plant in the cloud |
US11243505B2 (en) | 2015-03-16 | 2022-02-08 | Rockwell Automation Technologies, Inc. | Cloud-based analytics for industrial automation |
US10416661B2 (en) | 2017-11-30 | 2019-09-17 | Abb Schweiz Ag | Apparatuses, systems and methods of secure cloud-based monitoring of industrial plants |
JP6996002B2 (en) * | 2018-01-22 | 2022-01-17 | 株式会社日立ハイテクソリューションズ | Protecting your system from harmful communications |
JP2020057090A (en) * | 2018-09-28 | 2020-04-09 | 日本電気株式会社 | data structure |
JP7052755B2 (en) * | 2019-02-27 | 2022-04-12 | オムロン株式会社 | Controls, management programs and control systems |
Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6535227B1 (en) * | 2000-02-08 | 2003-03-18 | Harris Corporation | System and method for assessing the security posture of a network and having a graphical user interface |
US6732095B1 (en) * | 2001-04-13 | 2004-05-04 | Siebel Systems, Inc. | Method and apparatus for mapping between XML and relational representations |
US20050015397A1 (en) * | 2001-11-09 | 2005-01-20 | Abineri Robert F. | Data integration |
US20050198034A1 (en) * | 2004-03-02 | 2005-09-08 | Paragon Technical Services, Inc. | Industrial controller event logging |
US20070028215A1 (en) * | 2005-07-26 | 2007-02-01 | Invensys Systems, Inc. | Method and system for hierarchical namespace synchronization |
Family Cites Families (192)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
IT1020819B (en) | 1974-09-18 | 1977-12-30 | Olivetti & Co Spa | ACCOUNTING MACHINE WITH VARIABLE CONFIGURATION |
JPS55146552A (en) | 1979-05-02 | 1980-11-14 | Hitachi Ltd | N 1 backkup method of dispersion type hierarchy system |
EP0082225B1 (en) | 1981-12-23 | 1987-05-06 | International Business Machines Corporation | Business system |
JP2676397B2 (en) | 1989-01-05 | 1997-11-12 | 株式会社エイ・ティ・アール視聴覚機構研究所 | Dynamic trajectory generation method for dynamic system |
US5634048A (en) | 1989-09-14 | 1997-05-27 | Fujitsu Limited | Distributed database system having a center system with a link file and a method for retrieving data from same |
US5072374A (en) | 1989-11-07 | 1991-12-10 | Ge Fanuc Automation North America, Inc. | Method for communicating among a plurality of programmable logic controllers each having a dma controller |
US5185708A (en) | 1990-06-18 | 1993-02-09 | Ge Fanuc Automation North America, Inc. | Method for collecting data by a manufacturing process manager from a plurality of programmable logic controllers |
US5253184A (en) | 1991-06-19 | 1993-10-12 | Storage Technology Corporation | Failure and performance tracking system |
US5301320A (en) | 1991-06-28 | 1994-04-05 | Digital Equipment Corporation | Workflow management and control system |
US5504891A (en) | 1991-10-17 | 1996-04-02 | Ricoh Company, Ltd. | Method and apparatus for format conversion of a hierarchically structured page description language document |
US5446868A (en) | 1992-09-11 | 1995-08-29 | R. J. Reynolds Tobacco Company | Network bridge method and apparatus |
JPH06176081A (en) | 1992-12-02 | 1994-06-24 | Hitachi Ltd | Hierarchical structure browsing method and device |
US5572731A (en) | 1992-12-30 | 1996-11-05 | Hewlett-Packard Company | Sequentially navigated object oriented computer system |
US5455775A (en) | 1993-01-25 | 1995-10-03 | International Business Machines Corporation | Computer design system for mapping a logical hierarchy into a physical hierarchy |
US5367624A (en) | 1993-06-11 | 1994-11-22 | Consilium, Inc. | Interface for controlling transactions in a manufacturing execution system |
AU6814594A (en) | 1993-12-21 | 1995-07-10 | Taligent, Inc. | Automatic hardware configuration |
DE4403614A1 (en) | 1994-02-05 | 1995-08-10 | Philips Patentverwaltung | Communication system with a distributed database system |
US5485620A (en) | 1994-02-25 | 1996-01-16 | Automation System And Products, Inc. | Integrated control system for industrial automation applications |
US5537585A (en) | 1994-02-25 | 1996-07-16 | Avail Systems Corporation | Data storage management for network interconnected processors |
JP3085085B2 (en) | 1994-05-09 | 2000-09-04 | 三菱電機株式会社 | Data access device and distributed database system |
US5655148A (en) | 1994-05-27 | 1997-08-05 | Microsoft Corporation | Method for automatically configuring devices including a network adapter without manual intervention and without prior configuration information |
US5619724A (en) | 1994-08-10 | 1997-04-08 | Databook Incorporated | System for assigning a unique identifier to components by storing a bit sequence from a selected bit line after detecting a predetermined sequence of data |
DE69530595T2 (en) | 1994-09-01 | 2004-03-18 | Computer Associates Think, Inc. | SYSTEM AND METHOD FOR THE X.500 DATABASE STANDARD |
US5611059A (en) | 1994-09-02 | 1997-03-11 | Square D Company | Prelinked parameter configuration, automatic graphical linking, and distributed database configuration for devices within an automated monitoring/control system |
US5978577A (en) | 1995-03-17 | 1999-11-02 | Csg Systems, Inc. | Method and apparatus for transaction processing in a distributed database system |
US6307574B1 (en) | 1995-05-08 | 2001-10-23 | Apple Computer, Inc. | Graphical user interface with hierarchical structure for customizable menus and control objects |
US5802320A (en) | 1995-05-18 | 1998-09-01 | Sun Microsystems, Inc. | System for packet filtering of data packets at a computer network interface |
US5761499A (en) | 1995-12-21 | 1998-06-02 | Novell, Inc. | Method for managing globally distributed software components |
US6393566B1 (en) | 1995-07-28 | 2002-05-21 | National Institute Of Standards And Technology | Time-stamp service for the national information network |
US5848273A (en) | 1995-10-27 | 1998-12-08 | Unisys Corp. | Method for generating OLE automation and IDL interfaces from metadata information |
TW319942B (en) | 1995-11-14 | 1997-11-11 | Nippon Bickter Kk | |
US5784620A (en) * | 1995-11-15 | 1998-07-21 | Philips Electronics North America Corp. | Object-oriented system having shared-persistent class pattern |
US6101531A (en) | 1995-12-19 | 2000-08-08 | Motorola, Inc. | System for communicating user-selected criteria filter prepared at wireless client to communication server for filtering data transferred from host to said wireless client |
US5940854A (en) | 1996-01-16 | 1999-08-17 | International Business Machines Corporation | Unique identifier for optical media |
US5936539A (en) | 1996-03-19 | 1999-08-10 | Siemens Medical Systems, Inc. | Method and apparatus for automatic configuration of a network node |
US5797137A (en) | 1996-03-26 | 1998-08-18 | Golshani; Forouzan | Method for converting a database schema in relational form to a schema in object-oriented form |
DE19705955A1 (en) | 1996-03-29 | 1997-10-02 | Ibm | Workflow processing model implementation method |
US5828851A (en) | 1996-04-12 | 1998-10-27 | Fisher-Rosemount Systems, Inc. | Process control system using standard protocol control of standard devices and nonstandard devices |
US5940294A (en) | 1996-04-12 | 1999-08-17 | Fisher-Rosemont Systems, Inc. | System for assisting configuring a process control environment |
US6032208A (en) | 1996-04-12 | 2000-02-29 | Fisher-Rosemount Systems, Inc. | Process control system for versatile control of multiple process devices of various device types |
US5838563A (en) | 1996-04-12 | 1998-11-17 | Fisher-Rosemont Systems, Inc. | System for configuring a process control environment |
US5909368A (en) | 1996-04-12 | 1999-06-01 | Fisher-Rosemount Systems, Inc. | Process control system using a process control strategy distributed among multiple control elements |
US6098116A (en) | 1996-04-12 | 2000-08-01 | Fisher-Rosemont Systems, Inc. | Process control system including a method and apparatus for automatically sensing the connection of devices to a network |
US5862052A (en) | 1996-04-12 | 1999-01-19 | Fisher-Rosemount Systems, Inc. | Process control system using a control strategy implemented in a layered hierarchy of control modules |
US6110214A (en) * | 1996-05-03 | 2000-08-29 | Aspen Technology, Inc. | Analyzer for modeling and optimizing maintenance operations |
US5884033A (en) | 1996-05-15 | 1999-03-16 | Spyglass, Inc. | Internet filtering system for filtering data transferred over the internet utilizing immediate and deferred filtering actions |
DE19624929C2 (en) | 1996-06-21 | 2001-08-02 | Siemens Ag | Process automation system |
US5715413A (en) | 1996-06-25 | 1998-02-03 | International Business Machines Corporation | Dragging and dropping with an instantiation object |
DE19627464A1 (en) | 1996-07-08 | 1998-01-15 | Siemens Ag | Process automation system |
US5812773A (en) | 1996-07-12 | 1998-09-22 | Microsoft Corporation | System and method for the distribution of hierarchically structured data |
US6246972B1 (en) * | 1996-08-23 | 2001-06-12 | Aspen Technology, Inc. | Analyzer for modeling and optimizing maintenance operations |
US5960420A (en) | 1996-09-11 | 1999-09-28 | International Business Machines Corporation | Systems, methods and computer program products for implementing a workflow engine in database management system |
US5924094A (en) | 1996-11-01 | 1999-07-13 | Current Network Technologies Corporation | Independent distributed database system |
US5983016A (en) | 1996-11-12 | 1999-11-09 | International Business Machines Corporation | Execution engine in an object modeling tool |
GB2321720A (en) | 1997-02-04 | 1998-08-05 | Secr Defence | Modelling a system with more parameters than sensors |
US5913029A (en) | 1997-02-07 | 1999-06-15 | Portera Systems | Distributed database system and method |
US5980078A (en) | 1997-02-14 | 1999-11-09 | Fisher-Rosemount Systems, Inc. | Process control system including automatic sensing and automatic configuration of devices |
US6952705B2 (en) * | 1997-03-25 | 2005-10-04 | Mci, Inc. | Method, system and program product that utilize a hierarchical conceptual framework to model an environment containing a collection of items |
US6539430B1 (en) | 1997-03-25 | 2003-03-25 | Symantec Corporation | System and method for filtering data received by a computer system |
CA2201278C (en) | 1997-03-27 | 2001-02-20 | Ibm Canada Limited-Ibm Canada Limitee | Hierarchical metadata store for an integrated development environment |
US5966705A (en) | 1997-06-30 | 1999-10-12 | Microsoft Corporation | Tracking a user across both secure and non-secure areas on the Internet, wherein the users is initially tracked using a globally unique identifier |
JP3087694B2 (en) | 1997-07-15 | 2000-09-11 | 日本電気株式会社 | Information retrieval device and machine-readable recording medium recording program |
US6409082B1 (en) | 1997-07-25 | 2002-06-25 | Perseu Administration (Proprietary) Limited | Tracking of products |
US6484061B2 (en) | 1997-09-10 | 2002-11-19 | Schneider Automation Inc. | Web interface to a programmable controller |
US6763395B1 (en) | 1997-11-14 | 2004-07-13 | National Instruments Corporation | System and method for connecting to and viewing live data using a standard user agent |
US6681227B1 (en) | 1997-11-19 | 2004-01-20 | Ns Solutions Corporation | Database system and a method of data retrieval from the system |
JPH11175329A (en) | 1997-12-08 | 1999-07-02 | Hitachi Ltd | Application linking method and device therefor |
US6081899A (en) | 1998-01-09 | 2000-06-27 | Netscape Communications Corporation | Time stamp authority hierarchy protocol and associated validating system |
US6807632B1 (en) | 1999-01-21 | 2004-10-19 | Emc Corporation | Content addressable information encapsulation, representation, and transfer |
US6356920B1 (en) | 1998-03-09 | 2002-03-12 | X-Aware, Inc | Dynamic, hierarchical data exchange system |
JPH11312151A (en) | 1998-04-28 | 1999-11-09 | Hitachi Ltd | High-speed distribution object request broker |
US6157864A (en) * | 1998-05-08 | 2000-12-05 | Rockwell Technologies, Llc | System, method and article of manufacture for displaying an animated, realtime updated control sequence chart |
US6161051A (en) * | 1998-05-08 | 2000-12-12 | Rockwell Technologies, Llc | System, method and article of manufacture for utilizing external models for enterprise wide control |
US5951440A (en) | 1998-06-12 | 1999-09-14 | Reichlinger; Gary | Engine controller with operator interface |
US6438744B2 (en) | 1998-07-15 | 2002-08-20 | Microsoft Corporation | Dynamic mapping of component interfaces |
US6411987B1 (en) | 1998-08-21 | 2002-06-25 | National Instruments Corporation | Industrial automation system and method having efficient network communication |
US6505247B1 (en) | 1998-08-21 | 2003-01-07 | National Instruments Corporation | Industrial automation system and method for efficiently transferring time-sensitive and quality-sensitive data |
US6457053B1 (en) | 1998-09-21 | 2002-09-24 | Microsoft Corporation | Multi-master unique identifier allocation |
US6559860B1 (en) * | 1998-09-29 | 2003-05-06 | Rockwell Software Inc. | Method and apparatus for joining and manipulating graphical objects in a graphical user interface |
DE19848340A1 (en) | 1998-10-21 | 2000-04-27 | Philips Corp Intellectual Pty | Local network with bridge terminal for the transfer of data between several sub-networks |
US6469986B1 (en) | 1998-10-22 | 2002-10-22 | Electronic Data Systems Corporation | Method and system for configuring a network management network |
US6311187B1 (en) | 1998-12-29 | 2001-10-30 | Sun Microsystems, Inc. | Propogating updates efficiently in hierarchically structured data under a push model |
US6377957B1 (en) | 1998-12-29 | 2002-04-23 | Sun Microsystems, Inc. | Propogating updates efficiently in hierarchically structured date |
US6327511B1 (en) | 1998-12-30 | 2001-12-04 | Schneider Automation, Inc. | Input/output (I/O) scanner for a control system with peer determination |
US6853867B1 (en) | 1998-12-30 | 2005-02-08 | Schneider Automation Inc. | Interface to a programmable logic controller |
US6738821B1 (en) | 1999-01-26 | 2004-05-18 | Adaptec, Inc. | Ethernet storage protocol networks |
US6308168B1 (en) | 1999-02-09 | 2001-10-23 | Knowledge Discovery One, Inc. | Metadata-driven data presentation module for database system |
US6415983B1 (en) | 1999-02-26 | 2002-07-09 | Canada Post Corporation | Unique identifier bar code on stamps and apparatus and method for monitoring stamp usage with identifier bar codes |
US6874146B1 (en) | 1999-06-30 | 2005-03-29 | Unisys Corporation | Metadata driven system for effecting extensible data interchange based on universal modeling language (UML), meta object facility (MOF) and extensible markup language (XML) standards |
US6874145B1 (en) | 1999-07-13 | 2005-03-29 | Sun Microsystems, Inc. | Methods and apparatus for implementing an application lifecycle design for applications |
JP2001036549A (en) | 1999-07-15 | 2001-02-09 | Toshiba Corp | Data processing system and time stamp generating method |
US6234899B1 (en) | 1999-07-20 | 2001-05-22 | Scientific Games, Inc. | System for linking a unique identifier to an instant game ticket |
US6769095B1 (en) | 1999-07-23 | 2004-07-27 | Codagen Technologies Corp. | Hierarchically structured control information editor |
US6510352B1 (en) | 1999-07-29 | 2003-01-21 | The Foxboro Company | Methods and apparatus for object-based process control |
DE19939568C1 (en) | 1999-08-20 | 2001-02-08 | Pilz Gmbh & Co | Data transmission rate setting method for field bus system for safety critical process control has transmission rate set to higher data rate by central control after intial signalling of substations connected to field bus |
US6751634B1 (en) | 1999-08-26 | 2004-06-15 | Microsoft Corporation | Method and system for detecting object inconsistency in a loosely consistent replicated directory service |
JP2002117107A (en) | 1999-09-02 | 2002-04-19 | Ricoh Co Ltd | Production managing system, client for the same, production managing method for the same, data retrieving method for the same and computer readable recording medium stored with program for executing the same method |
KR100304482B1 (en) | 1999-09-22 | 2001-11-02 | 구자홍 | Method and apparatus for user adaptive information presentation using multiple hierarchical preference information structure and the data structure of multiple hierarchical preference information |
WO2001024518A1 (en) | 1999-09-25 | 2001-04-05 | Koninklijke Philips Electronics N.V. | User interface generation |
US6556950B1 (en) * | 1999-09-30 | 2003-04-29 | Rockwell Automation Technologies, Inc. | Diagnostic method and apparatus for use with enterprise control |
US6268853B1 (en) * | 1999-09-30 | 2001-07-31 | Rockwell Technologies, L.L.C. | Data structure for use in enterprise controls |
US6446202B1 (en) | 1999-10-04 | 2002-09-03 | Fisher-Rosemount Systems, Inc. | Process control configuration system for use with an AS-Interface device network |
US6445963B1 (en) | 1999-10-04 | 2002-09-03 | Fisher Rosemount Systems, Inc. | Integrated advanced control blocks in process control systems |
US6901578B1 (en) | 1999-12-06 | 2005-05-31 | International Business Machines Corporation | Data processing activity lifecycle control |
US6643652B2 (en) | 2000-01-14 | 2003-11-04 | Saba Software, Inc. | Method and apparatus for managing data exchange among systems in a network |
US6745089B2 (en) | 2000-02-01 | 2004-06-01 | California Institute Of Technology | Adaptable state based control system |
US6714981B1 (en) | 2000-02-07 | 2004-03-30 | Hewlett-Packard Development Company, L.P. | Addressing system and method for communicating data |
US6865509B1 (en) | 2000-03-10 | 2005-03-08 | Smiths Detection - Pasadena, Inc. | System for providing control to an industrial process using one or more multidimensional variables |
US6631519B1 (en) | 2000-03-30 | 2003-10-07 | Microsoft Corporation | Automated schema and interface generation |
US6760721B1 (en) | 2000-04-14 | 2004-07-06 | Realnetworks, Inc. | System and method of managing metadata data |
US6714949B1 (en) | 2000-04-25 | 2004-03-30 | Adaptec, Inc. | Dynamic file system configurations |
EP1150213B1 (en) | 2000-04-28 | 2012-01-25 | TELEFONAKTIEBOLAGET LM ERICSSON (publ) | Data processing system and method |
US6697797B1 (en) | 2000-04-28 | 2004-02-24 | Micro Data Base Systems, Inc. | Method and apparatus for tracking data in a database, employing last-known location registers |
US6842769B1 (en) | 2000-05-05 | 2005-01-11 | Interland, Inc. | Automatically configured network server |
US6934749B1 (en) | 2000-05-20 | 2005-08-23 | Ciena Corporation | Tracking distributed data retrieval in a network device |
US20020012401A1 (en) | 2000-05-23 | 2002-01-31 | Endevco Corporation | Transducer network bus |
CA2310150A1 (en) | 2000-05-30 | 2001-11-30 | Crosskeys Systems Corporation | Metadata-driven statistics processing |
US6973556B2 (en) | 2000-06-19 | 2005-12-06 | Storage Technology Corporation | Data element including metadata that includes data management information for managing the data element |
DE10030845B4 (en) | 2000-06-23 | 2008-11-20 | Abb Ag | Fieldbus connection system for actuators or sensors |
US6928521B1 (en) | 2000-08-01 | 2005-08-09 | International Business Machines Corporation | Method, system, and data structures for using metadata in updating data in a storage device |
US6938079B1 (en) | 2000-09-19 | 2005-08-30 | 3Com Corporation | System and method for automatically configuring a client device |
US6425051B1 (en) | 2000-09-25 | 2002-07-23 | International Business Machines Corporation | Method, system, program, and data structures for enabling a controller accessing a storage device to handle requests to data in a first data format when the storage device includes data in a second data format |
US6950900B1 (en) | 2000-09-27 | 2005-09-27 | International Business Machines Corporation | Method and apparatus for migrating data having a format of a first type to a format of a second type |
DE60036031T2 (en) | 2000-10-03 | 2008-05-15 | U4Ea Technologies Ltd. | ALLOCATION OF PRIORITY LEVELS IN A DATA FLOW |
AU2000275420A1 (en) | 2000-10-03 | 2002-04-15 | U4Ea Technologies Limited | Prioritising data with flow control |
US6643555B1 (en) | 2000-10-10 | 2003-11-04 | Schneider Automation Inc. | Method and apparatus for generating an application for an automation control system |
EP1199847A1 (en) | 2000-10-20 | 2002-04-24 | Deutsche Thomson-Brandt Gmbh | Method for the data exchange between network devices |
US6930985B1 (en) | 2000-10-26 | 2005-08-16 | Extreme Networks, Inc. | Method and apparatus for management of configuration in a network |
EP1364313A2 (en) | 2000-10-31 | 2003-11-26 | Michael Philip Kaufman | System and method for automatically generating user interfaces for arbitrarily complex or large databases |
US6687817B1 (en) | 2000-11-14 | 2004-02-03 | Sun Microsystems, Inc. | Configuration of a network device via the network |
US6961728B2 (en) | 2000-11-28 | 2005-11-01 | Centerboard, Inc. | System and methods for highly distributed wide-area data management of a network of data sources through a database interface |
WO2002044863A2 (en) | 2000-12-01 | 2002-06-06 | James Conlow | Efficient presentment and payment of bills |
US6704746B2 (en) | 2000-12-12 | 2004-03-09 | Sun Microsystems, Inc. | Method and apparatus for lazy instantiation of objects in a virtual machine |
US6539271B2 (en) | 2000-12-27 | 2003-03-25 | General Electric Company | Quality management system with human-machine interface for industrial automation |
US6748486B2 (en) | 2001-01-04 | 2004-06-08 | International Business Machines Corporation | Method, system, and data structures for superimposing data records in a first data format to memory in a second data format |
US6766312B2 (en) | 2001-01-31 | 2004-07-20 | International Business Machines Corporation | Method and system for a random number generator |
US6868413B1 (en) | 2001-05-10 | 2005-03-15 | Networks Associates Technology, Inc. | System and method for customizing and processing business logic rules in a business process system |
US6859921B2 (en) | 2001-05-31 | 2005-02-22 | International Business Machines Corporation | System, method, and computer program product for creating a hierarchy of software components based on the programming constructs therein |
US7162534B2 (en) * | 2001-07-10 | 2007-01-09 | Fisher-Rosemount Systems, Inc. | Transactional data communications for process control systems |
US6975913B2 (en) | 2001-07-13 | 2005-12-13 | Siemens Aktiengesellschaft | Database system and method for industrial automation services |
US6947947B2 (en) | 2001-08-17 | 2005-09-20 | Universal Business Matrix Llc | Method for adding metadata to data |
US6954770B1 (en) | 2001-08-23 | 2005-10-11 | Cavium Networks | Random number generator |
US6760732B2 (en) | 2001-09-06 | 2004-07-06 | International Business Machines Corporation | Method and system for viewing a record of an organization having a hierarchy of departments |
US6758403B1 (en) | 2001-09-11 | 2004-07-06 | Psc Scanning, Inc. | System for editing data collection device message data |
EP1298539A1 (en) | 2001-10-01 | 2003-04-02 | Sun Microsystems, Inc. | Method and device for marking and filtering data elements in a database |
US20030090514A1 (en) | 2001-10-23 | 2003-05-15 | Cole Douglas J. | Business process user interface generation system and method |
US6944626B2 (en) | 2001-11-26 | 2005-09-13 | Microsoft Corp. | Dynamically generated schema representing multiple hierarchies of inter-object relationships |
US7093259B2 (en) | 2001-12-20 | 2006-08-15 | Cadence Design Systems, Inc. | Hierarchically structured logging for computer work processing |
KR100429551B1 (en) | 2002-01-03 | 2004-04-29 | 삼성전자주식회사 | Method for processing events of hierarchy structure in communication equipment |
US7139750B2 (en) | 2002-03-13 | 2006-11-21 | Agile Software Corporation | System and method for where-used searches for data stored in a multi-level hierarchical structure |
IL164143A0 (en) | 2002-03-25 | 2005-12-18 | Data Quality Solutions Inc | Method and system for enterprise business process management |
US6880060B2 (en) | 2002-04-24 | 2005-04-12 | Sun Microsystems, Inc. | Method for storing metadata in a physical sector |
JP2003323357A (en) | 2002-05-08 | 2003-11-14 | Hitachi Ltd | Time stamp generation system |
US20030218641A1 (en) | 2002-05-23 | 2003-11-27 | International Business Machines Corporation | Method and system for navigating a hierarchical structure in a data processing system |
US6904473B1 (en) | 2002-05-24 | 2005-06-07 | Xyratex Technology Limited | Direct memory access controller and method of filtering data during data transfer from a source memory to a destination memory |
GB2389432B (en) | 2002-06-07 | 2005-09-07 | Advanced Risc Mach Ltd | Instruction tracing in data processing systems |
US6839790B2 (en) | 2002-06-21 | 2005-01-04 | Smar Research Corporation | Plug and play reconfigurable USB interface for industrial fieldbus network access |
JP2004038876A (en) | 2002-07-08 | 2004-02-05 | Hitachi Ltd | Data format conversion method and device for program and the like, and controller management system using the data format conversion device |
US6809732B2 (en) | 2002-07-18 | 2004-10-26 | Nvidia Corporation | Method and apparatus for generation of programmable shader configuration information from state-based control information and program instructions |
DE10245931A1 (en) | 2002-09-30 | 2004-04-08 | Siemens Ag | Workflow management system has a device for detecting fuzzy process definitions to enable continuous status management |
US20040203620A1 (en) | 2002-10-15 | 2004-10-14 | Timothy Thome | Method and apparatus for time stamp of electronic message |
WO2004036325A1 (en) | 2002-10-16 | 2004-04-29 | Honda Giken Kogyo Kabushiki Kaisha | Step processing configuration/management method in factory production step management system |
DE10254010B4 (en) | 2002-11-19 | 2009-01-02 | Siemens Ag | Method for automatic configuration of a parameterization surface of machine tools or production machines |
US20040215478A1 (en) | 2002-12-24 | 2004-10-28 | Baker Christopher A. | Method of providing a unique identifier for a mailpiece |
US8935298B2 (en) | 2002-12-30 | 2015-01-13 | Fisher-Rosemount Systems, Inc. | Integrated navigational tree importation and generation in a process plant |
US20040167790A1 (en) | 2003-02-24 | 2004-08-26 | Grasse Robert De | Method of conducting business in a system requiring frequency up-dates and corrections |
US7634478B2 (en) | 2003-12-02 | 2009-12-15 | Microsoft Corporation | Metadata driven intelligent data navigation |
JP4035822B2 (en) | 2003-04-14 | 2008-01-23 | ソニー株式会社 | Audio data editing apparatus, audio data editing method, and audio data editing program |
US20040260591A1 (en) | 2003-06-17 | 2004-12-23 | Oracle International Corporation | Business process change administration |
EP1494241A1 (en) | 2003-07-01 | 2005-01-05 | Deutsche Thomson-Brandt GmbH | Method of linking metadata to a data stream |
WO2005008524A1 (en) | 2003-07-16 | 2005-01-27 | Joltid Ltd. | Distributed database system |
US7318148B2 (en) | 2003-07-31 | 2008-01-08 | Sap Ag | Automatically configuring a computer |
JP4241261B2 (en) | 2003-08-19 | 2009-03-18 | キヤノン株式会社 | Metadata grant method and metadata grant apparatus |
JP3909848B2 (en) | 2003-09-19 | 2007-04-25 | 本田技研工業株式会社 | Product lifecycle information management system |
US20050069853A1 (en) | 2003-09-26 | 2005-03-31 | Tyson William Randal | Performance tracking systems and methods |
CA2443447A1 (en) * | 2003-09-30 | 2005-03-30 | Ibm Canada Limited-Ibm Canada Limitee | System and method for conversion between graph-based representations and structural text-based representations of business processes |
US7103874B2 (en) * | 2003-10-23 | 2006-09-05 | Microsoft Corporation | Model-based management of computer systems and distributed applications |
EP1530139A1 (en) | 2003-11-05 | 2005-05-11 | Sap Ag | Method and computer system for workflow management |
US7552433B2 (en) | 2003-11-12 | 2009-06-23 | Hewlett-Packard Development Company, L.P. | Non-platform-specific unique indentifier generation |
US7480709B2 (en) | 2003-11-14 | 2009-01-20 | Rockwell Automation Technologies, Inc. | Dynamic browser-based industrial automation interface system and method |
DE10357782B3 (en) | 2003-12-10 | 2005-05-04 | Infineon Technologies Ag | Random number generator for cryptographic applications e.g. for chip card, has intermediate condition of pseudo-random number generator stored in memory as initializing information |
US20050166215A1 (en) | 2004-01-27 | 2005-07-28 | International Business Machines Corporation | Common user interface for interacting with various interfaces |
US7130956B2 (en) | 2004-02-10 | 2006-10-31 | Sun Microsystems, Inc. | Storage system including hierarchical cache metadata |
JP2005234705A (en) | 2004-02-17 | 2005-09-02 | Fujitsu Ltd | System layout designing program for realizing automatic configuration of system, system layout designing device and system layout designing method |
US20050187925A1 (en) | 2004-02-25 | 2005-08-25 | Diane Schechinger | Schechinger/Fennell System and method for filtering data search results by utilizing user selected checkboxes" |
GB2412755A (en) | 2004-03-30 | 2005-10-05 | Hewlett Packard Development Co | Coordination of lifecycle state changes in software components |
US20050251527A1 (en) | 2004-05-07 | 2005-11-10 | Mark Phillips | System and method for integrating disparate data and application sources using a web services orchestration platform with business process execution language (BPEL) |
JP4020396B2 (en) | 2004-05-11 | 2007-12-12 | インターナショナル・ビジネス・マシーンズ・コーポレーション | Apparatus and method for tracking products |
WO2005109160A1 (en) | 2004-05-12 | 2005-11-17 | Redsky Mobile Inc. | Navigation of an n-dimensional hierarchical structure using a 2-dimensional controller |
GB2415063A (en) | 2004-06-09 | 2005-12-14 | Oracle Int Corp | Data retrieval method |
US9268780B2 (en) | 2004-07-01 | 2016-02-23 | Emc Corporation | Content-driven information lifecycle management |
US20060004475A1 (en) | 2004-07-01 | 2006-01-05 | Abb Inc. | Incrementally accruing product and component quality and tracking data in the manufacturing of devices |
-
2005
- 2005-09-30 US US11/239,937 patent/US8484250B2/en active Active
-
2006
- 2006-09-28 EP EP06020456A patent/EP1770464A3/en not_active Ceased
- 2006-09-30 CN CNA200610131757XA patent/CN1952815A/en active Pending
-
2013
- 2013-07-01 US US13/933,008 patent/US20130290374A1/en active Pending
Patent Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6535227B1 (en) * | 2000-02-08 | 2003-03-18 | Harris Corporation | System and method for assessing the security posture of a network and having a graphical user interface |
US6732095B1 (en) * | 2001-04-13 | 2004-05-04 | Siebel Systems, Inc. | Method and apparatus for mapping between XML and relational representations |
US20050015397A1 (en) * | 2001-11-09 | 2005-01-20 | Abineri Robert F. | Data integration |
US20050198034A1 (en) * | 2004-03-02 | 2005-09-08 | Paragon Technical Services, Inc. | Industrial controller event logging |
US20070028215A1 (en) * | 2005-07-26 | 2007-02-01 | Invensys Systems, Inc. | Method and system for hierarchical namespace synchronization |
Cited By (10)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20170337283A1 (en) * | 2014-11-07 | 2017-11-23 | Rockwell Automation Technologies, Inc. | Dynamic search engine for an industrial environment |
US10713307B2 (en) * | 2014-11-07 | 2020-07-14 | Rockwell Automation Technologies, Inc. | Dynamic search engine for an industrial environment |
US9864786B2 (en) | 2014-11-10 | 2018-01-09 | Red Hat, Inc. | Native federation view suggestion |
US10210208B2 (en) | 2014-11-10 | 2019-02-19 | Red Hat, Inc. | Viewable suggestions for federation engine |
US10156842B2 (en) | 2015-12-31 | 2018-12-18 | General Electric Company | Device enrollment in a cloud service using an authenticated application |
US10156841B2 (en) | 2015-12-31 | 2018-12-18 | General Electric Company | Identity management and device enrollment in a cloud service |
US10444743B2 (en) | 2015-12-31 | 2019-10-15 | General Electric Company | Identity management and device enrollment in a cloud service |
US10719071B2 (en) | 2015-12-31 | 2020-07-21 | General Electric Company | Device enrollment in a cloud service using an authenticated application |
US10796156B2 (en) | 2016-04-19 | 2020-10-06 | Rockwell Automation Technologies, Inc. | Analyzing video streams in an industrial environment to identify potential problems and select recipients for a display of video streams related to the potential problems |
US11221661B2 (en) | 2019-01-14 | 2022-01-11 | Rockwell Automation Technologies, Inc. | Method for auto-discovery and categorization of a plants power and energy smart devices for analytics |
Also Published As
Publication number | Publication date |
---|---|
EP1770464A3 (en) | 2011-09-28 |
EP1770464A2 (en) | 2007-04-04 |
US20070078862A1 (en) | 2007-04-05 |
US8484250B2 (en) | 2013-07-09 |
CN1952815A (en) | 2007-04-25 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US8484250B2 (en) | Data federation with industrial control systems | |
US8229577B2 (en) | Distributed historian architecture and interfaces | |
US8965931B2 (en) | Distributed historian architecture | |
CN111562769B (en) | AI extension and intelligent model validation for industrial digital twinning | |
US7627385B2 (en) | Historian module for use in an industrial automation controller | |
US20210397174A1 (en) | Industrial automation information contextualization method and system | |
EP3285127B1 (en) | Remote industrial automation site operation in a cloud platform | |
EP1624351B1 (en) | Dynamic schema for unified plant model | |
EP2045684B1 (en) | Contextualization for historians in industrial systems | |
EP1531373B1 (en) | Dynamic browser-based industrial automation interface system and method | |
US8855791B2 (en) | Industrial operator interfaces interacting with higher-level business workflow | |
US8190284B1 (en) | Auto discovery of embedded historians in network | |
US8624921B2 (en) | Industrial automation visualization schemes employing overlays | |
EP1936496A1 (en) | Module classification and searching for industrial control systems | |
US20040204772A1 (en) | Agent-equipped controller having data table interface between agent-type programming and non-agent-type programming | |
US7809656B2 (en) | Microhistorians as proxies for data transfer | |
US7774167B2 (en) | System and method for providing diagnosis information | |
WO2006124487A2 (en) | Automatic user interface generation | |
US8806343B2 (en) | System and method for handling a data refresh procedure in a production execution system | |
Grothoff et al. | Asset administration shell as integration layer for the orchestration of mixed process and manufacturing plants | |
Grüner et al. | An approach for interconnection and unification of state models in discrete manufacturing | |
Siverskiy | Implementing an AAS for a Siemens motor control system | |
Gomez Gomez | Survey of SCADA SYSTEMS and visualization of a real life process |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: ROCKWELL AUTOMATION TECHNOLOGIES, INC., OHIO Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:CHAND, SUJEET;BRIANT, STEPHEN C.;HALL, KENWOOD H.;AND OTHERS;SIGNING DATES FROM 20051110 TO 20051216;REEL/FRAME:030723/0753 |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: NON FINAL ACTION MAILED |