Event Historian Data Dictionary for Industrial Process Control
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Complex industrial processes generate vast amounts of data that are difficult to store and retrieve efficiently, requiring an event historian system to quickly and accurately record event data and provide responsive query results in a process control system environment.
Innovation Solution
An event historian system utilizing block data storage and snapshots to efficiently record and retrieve event data, with features like dynamic snapshot creation, data compression, and a merge process to eliminate duplicates, enabling fast query responses and flexible data handling across various formats and sources.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of information
If all industrial process data is stored to enable comprehensive analysis, then data completeness and analysis capability are improved, but storage complexity and retrieval difficulty increase
Solution Approach 1:
The patent segments industrial process data into discrete events with specific attributes (timestamp, source, value, etc.). Each event is stored as an independent record in a standardized format, allowing the system to manage vast amounts of data through modular, manageable units rather than as a monolithic dataset.
Solution Approach 2:
The patent creates a simplified representation or copy of the complex industrial data through standardized event records. Instead of storing raw, unstructured process data, the system creates structured event copies that retain essential information while enabling efficient storage and retrieval through consistent formatting and indexing.
2Measurement precision
If event data is recorded at high speed to capture all process occurrences, then data accuracy and completeness are improved, but system performance and query responsiveness may deteriorate
Solution Approach 1:
The patent applies preliminary action by pre-structuring and indexing event data as it is recorded. Events are stored in a standardized format with consistent attributes and timestamps from the moment of ingestion, and indexing structures are built during the recording phase. This preliminary organization enables rapid query response later without compromising the high-speed capture of events.
3Ease of operation
If a comprehensive data dictionary is maintained to define all data values, then data accessibility and query capability are improved, but initial system setup and data dictionary population time increase
Solution Approach 1:
The patent implements self-service by enabling the event historian system to automatically generate and maintain its own data dictionary. As events are recorded with their attributes and data types, the system autonomously populates the data dictionary with this information, eliminating the need for manual configuration and reducing initial setup time while maintaining comprehensive data definition for accessibility.
Data Source
AI summary
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.