Block data storage system in an event historian
AssigneeAveva Software, LLC
InventorsBrian Kenneth Erickson, Bala Kamesh Sista, Abhijit Manushree, Vinay T. Kamath
Life of this patent
Estimating the term…
Abstract
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.
Claims18
A system for storing event data from an industrial process comprising:
- an event historian comprising one or more processors and one or more non-transitory computer readable media, the one or more non-transitory computer readable media comprising instructions stored thereon that when executed by the one or more processors implement:
- a storage block,
- wherein the system is configured to:
- receive event data
- comprising properties including one of an event type and an occurrence time of the individual event;
- write the received event data to a snapshot,
- the snapshot including a time period associated with the occurrence of the individual event;
- analyze the individual event for common patterns by comparing the event with one or more similar events;
- create a separated event by removing the common patterns from the individual event, a size of the separated event being smaller than a size of the individual event;
- create an encoded file for the separated event and a different encoded file for the common patterns;
- and
- store the encoded file for the common patterns separately from the encoded file for the separated event, wherein all the common patterns identified within the individual event being stored within the encoded file for the common patterns.
A system for storing event data from an industrial process comprising:
- an event historian comprising one or more processors and one or more non-transitory computer readable media, the one or more non-transitory computer readable media comprising instructions stored thereon that when executed by the one or more processors implement:
- a storage block,
- a snapshot,
- a lookup process, and
- a common bytes encoder (CBE) module;
- wherein the system is configured to;
- receive event data from an industrial process,
- the event data comprising an individual event and property data associated with the individual event;
- send the property data to the lookup process
- the lookup process sorting the property data into one or more files in the storage block,
- the one or more files are configured to enable a lookup of the event data upon receiving a query;
- send the individual event to the CBE module upon completion of the lookup process,
- the CBE module being configured to analyze the individual event and determine shared patterns between the individual event and one or more other events;
- create an individual event by removing the shared patterns from the event data, the size of the individual event being smaller than the size of the event data;
- create an encoded file for the individual event and a different encoded file for the shared patterns;
- and
- create the snapshot that comprises the encoded file for the individual event,
- wherein the snapshot is stored in the storage block, and wherein all the shared patterns identified within the event data is stored in the encoded file for the shared patterns.
Dependencies are inferred from the claim text.