Aveva Software, LLC

Schneider Electric Software, LLC

Bala Kamesh Sista

Vinay T Kamath

Abhijit Manushree

Brian Kenneth Erickson

Elliott Middleton

Yevgeny V Naryzhny

Alexander Vasilyevich Bolotskikh

Steven Michael Weinrich

Dave Tran

Shiewun Lie

An event historian system receives event data from a client system via a network connection and stores the event data in a block data storage system. An event data block in which to store the received event data is selected based on the time range of the occurrence of the received event data. The received event data is stored in a snapshot within the event data block. Event property data is extracted from the received event data and used to build a plurality of event property index files.

Block data storage system in an event historian

Annotating content, comprising data values of one or more tags corresponding to a process device within a continuous process, with content descriptors in a historian system. Content descriptors enable indexing and saving content within a search service database for later retrieval by search strings that match the content descriptors. Content having one or more common content descriptors are retrieved and transmitted to a client computing device via a communications network for displaying in a dashboard on the client computing device.

Storing and identifying content through content descriptors in a historian system

Processing raw data stored in an historian device for determining an amount of products passed through a process element in a process control environment is described. A count value is incremented by a counter at a rate at which products pass through the process element. The count value rolls over to zero when the count value reaches a rollover value R. An historian device periodically receives count value data points from the counter. A deadband value D is set in the historian device for distinguishing between rollovers, resets, and reversals. A client device queries the historian device for an amount of products passed through the process element for a timeframe. The historian device selects a set of count value data points from within the queried timeframe. The historian device determines, based on the selected data points and their quality, an amount of products passed through the process element.

Optimistic data retrieval in a process control environment

An event historian system stores an event data dictionary. The system receives an initial query from a client device on a network connection and responds by providing the event data dictionary information to the client device. The client device sends another query requesting data values which are defined in the event data dictionary. The system responds to the second query by sending results comprising the requested data values to the client system over the network connection.

Data dictionary system in an event historian

A system for displaying statistical data in a process control environment. A client device connects, via a network, to a historian connection module, and subscribes, via the connection to the historian connection module, to statistical data stored in a historian server module. A historian device receives a connection, by the historian connection module via the network, from the client device, forms a connection between the historian connection module and the historian server module, receives a subscription, by the historian connection module via the network, to statistical data stored in the historian server module from the client device, and stores, by the historian connection module, the received subscription.

Historical summarization in a process control environment

A system for communicating data packets in a process control environment is described. A client device connects, via the network, to an historian device, creates, via a first dictionary manager module, a first tag dictionary, synchronizes, via the network, the first tag dictionary with a second tag dictionary created by the historian device, optimizes a packet via a packet optimization layer comprising scanning a tag ID present in the packet, determines a matching tag handle for the tag ID from the first tag dictionary, replaces each instance of the tag ID in the packet with the matching tag handle, and sends the optimized packet to the historian device via the network. The historian device connects, via the network, to the client device, creates, via a second dictionary manager module, the second tag dictionary, synchronizes, via the network, the second tag dictionary with the first tag dictionary created by the client device, receives the optimized packet from the client device via the network, converts the optimized packet back to its original form comprising scanning a tag handle present in the packet, determines a matching tag ID for the tag handle from the second tag dictionary, and replaces each instance of the tag handle in the packet with the matching tag ID.

Connection based bandwidth optimization of data packets

An event historian system receives and responds to queries for event data from a client device over a network connection. The queries comprise parameters indicating a date range and filter limitations defining the desired event data. The system selects storage blocks based on the date range and filters event data in the storage blocks based on the filter limitations. The filtered event data is grouped into a results message and sent to the client system via the network connection.

Data query interface system in an event historian

An event historian system merges stored event data snapshots into sorted event storage blocks. The system determines that a storage block contains a plurality of snapshots to be merged. A new snapshot is created into which the plurality of snapshots will be merged. The event data within the snapshots is combined and recorded into the new snapshot in a sorted order. The index files within the snapshots are combined and recorded into the new snapshot.

Growing community of inventors

Irvine, CA, United States of America

Bala Kamesh Sista