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

Abstract: Systems and methods that facilitate discovery of history data via a locator component associated with a plant embedded historian(s) of an industrial programmer (e.g., a controller device.) Such locator component can further detect micro historians that are distributed on the back plane of an industrial network. The locator component can be part of applications running on a control unit, which can function as a management control center for the industrial network system. A common data model can be employed to expose functionality and data of the organization to the embedded historian component.

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

Abstract: An in situ system used for treating an oil and gas well drilling fluid and treating water after a well is completed. The system includes a fluid treatment unit used in a reserve pit and a water treatment unit disposed next to the pit. The fluid treatment unit includes a floating electrocoagulation unit in the reserve pit for destabilizing contaminates in the fluid and dropping out stable precipitates. The clear treated fluid is then pumped, using a submersible pump, to the water treatment unit. The water treatment includes a number of components including a pre-filter, an activated carbon filter and a heat exchanger for first treating the fluid. The filtered and heated fluid is then piped into a reverse osmosis unit for removing salt and any remaining minerals found therein. From the reverse osmosis unit, approximately 70 to 80% of the filtered water is cleaned and piped to a clean water storage tank for reuse.

Abstract: Systems and methods that provide for event driven downloading, via defining storage thresholds in an embedded historian (e.g. micro historian). Upon reaching predetermined thresholds (e.g., low/high water marks), stored data in the embedded historians can automatically down load to a central plant historian. An automatic download engine is provided that down loads historian data based on satisfaction of such conditions defined for the download. The download engine can further include a detector component, which detects whether a predetermined condition (e.g., associated with the storage capacity of the micro-historians have been met. Moreover, a notification component can notify the embedded historians that the data have been permanently persisted in the central historian.

Abstract: Systems and methods that enable query based formulation requests to an embedded historian and data acquired thereby, via employing a browser engine. Accordingly, users can browse data collected by the plurality of embedded historians based on numerous selection criteria such as for example, type of data collected, location/time of data collection, and the like. Query specific request can be inputted to the browser engine, and data that match such request can subsequently be presented to the user. Thus, history data can be viewed based on user preferences, and in a meaningful manner to such user.

Abstract: Systems and methods that provide for event driven downloading, via defining storage thresholds in an embedded historian (e.g. micro historian). Upon reaching predetermined thresholds (e.g., low/high water marks), stored data in the embedded historians can automatically down load to a central plant historian. An automatic download engine is provided that down loads historian data based on satisfaction of such conditions defined for the download. The download engine can further include a detector component, which detects whether a predetermined condition (e.g., associated with the storage capacity of the micro-historians have been met. Moreover, a notification component can notify the embedded historians that the data have been permanently persisted in the central historian.

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

Abstract: Systems and methods that configure an embedded historian(s) to a predetermined setting and an automatic propagation thereof to other embedded historians and units on the factory floor. Embedded historian can be automatically configured, and be set up as a default collection for a plant scan, such that when a plant comes on-line, embedded historians announce their presence to such plant, and are discovered thereby and configured thereby.

Abstract: Systems and methods that provide for historians communicating in a plurality of protocols/languages with various resources via employing an abstraction component that normalizes such communication. Accordingly, the historian can supply a common configuration for various data (e.g., events, command, event, alarm, scenarios, transactions, messages, and the like), and hence provide support for third party devices. The abstraction component can further facilitate: Filtering, Bridging, Routing, Propagation, Transformation and Monitoring of data exchange with third party devices.

Abstract: Systems and methods that enable historians (e.g., micro-historians) to function as proxies, to supply plant level data, (e.g., history data) back to the controllers. Accordingly, typically such micro historians can function as clients/servers, to provide higher level data to the controllers (e.g., from third part databases). The historians can create a proxy that image an object on a server associated with controllers (e.g., programmable logic controller.) Such objects can contain data; pieces of code; attributes; operations or combinations thereof, for example.

Abstract: Systems and methods that provide for adaptive processes in an industrial setting. Historian data, in conjunction with current collected data, can be converted into decision making information that is subsequently employed for modifying a process in real time. A process trend component, which is associated with a controller, can access historian data (e.g., trends collected via historians) to determine/predict an outcome of a current industrial process. Such enables a tight control and short reaction time to correcting process parameters.

Abstract: Systems and methods that supply direct access (e.g., bypassing the controller) to embedded historian via a subscription and notification component. By modeling the notification related information (e.g., subscription queries, subscriber information, event information . . . ) as data and leveraging the power of database systems to perform set-oriented manipulations on this data efficiently, the subject innovation enables for a highly scalable and efficient subscription and notification system for direct access to the historians.

Abstract: Systems and methods that discover relations and correlates among disparate pieces of data, to infer possible relationships between the industrial process and historian data/events to improve industrial operations. A correlation component can employ heuristic models to capture process data/event data, and can further include an implicit correlation component and an explicit correlation component. Accordingly, relations among various parameters can be discovered (e.g., dynamically) and proper corrective adjustments supplied to the industrial process.

Abstract: Systems and methods that provide a historian integrated as part of an industrial unit and/or product manufactured by the industrial process. A historian integrated as part of the industrial unit itself, can increase data resolution and supply immediate and real time data regarding the industrial unit's operation—while mitigating short comings of conventional PC historians. Moreover, a locator component can detect embedded historians that are distributed on the back plane of an industrial network, and integrated as part thereof.

Abstract: The electro-pneumatic latching valve system having an electrical switch unit that further includes an “apply” or “activate” switch, a “release” or “deactivate” switch, and a power supply. A first solenoid valve is in electrical communication with the activate switch and a second solenoid valve is in electrical communication with the deactivate switch. A pneumatic latching valve is in pneumatic communication with the first and second solenoid valves and a source of pressurized control and supply air is in pneumatic communication with the pneumatic latching valve and the solenoid valves. A terminal device, e.g., a spring brake, is in pneumatic communication with the latching valve, and the device is released or applied in response to pressurized supply air delivered to the device through the pneumatic latching valve in response to pneumatic control signals delivered to the pneumatic latching valve from the solenoid valves.

Abstract: A pneumatic brake system that includes at least one pneumatic latching valve; a single device, such as a solenoid, for providing momentary pilot signals to pneumatic latching valve; a source of pressurized supply air in communication with the pneumatic latching valve; a spring brake or other pneumatic device in communication with the pneumatic latching valve; and, optionally, an indicator device for monitoring and displaying the state of the pneumatic latching valve. Upon receiving a first momentary pilot signal the pneumatic latching valve changes from closed to open and delivers pressurized air to the spring brake. Upon receiving a second momentary pilot signal, the pneumatic latching valve changes from open to closed and exhausts pressurized air from the spring brake to the external environment. The valve remains “latched” in its current state until the signaling device is energized and the next momentary pilot signal is received.

Abstract: The electro-pneumatic latching valve system having an electrical switch unit that further includes an “apply” or “activate” switch, a “release” or “deactivate” switch, and a power supply. A first solenoid valve is in electrical communication with the activate switch and a second solenoid valve is in electrical communication with the deactivate switch. A pneumatic latching valve is in pneumatic communication with the first and second solenoid valves and a source of pressurized control and supply air is in pneumatic communication with the pneumatic latching valve and the solenoid valves. A terminal device, e.g., a spring brake, is in pneumatic communication with the latching valve, and the device is released or applied in response to pressurized supply air delivered to the device through the pneumatic latching valve in response to pneumatic control signals delivered to the pneumatic latching valve from the solenoid valves.

Abstract: Systems and methods that can vary a data collection rate via a rate adjustment component, to collect data with different level of granularity. The rate adjustment component can further include an estimation component that can automatically predict a required sampling rate for a stage of an operation, based on statistical models and collected for similar operations and/or history data. Such difference in the granularity level can initiate in part in response to fault detection, alert triggering, and the like. Accordingly, future trouble shooting efforts can be performed with respect to data that is typically collected at an adjustable rate.

Abstract: Systems and methods that automatically capture data/events related to industrial processes via a data capture unit. Such data capture unit includes an analysis component (which determines function blocks that define the control algorithm), and a triggering component (which initiates data capture for the function blocks based on such analysis.