Event Processor Platform for Dynamic Data Routing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In operational environments, manually configuring data objects for assets leads to inefficiencies, misallocated resources, and reduced asset performance due to inadequate reconfiguration of data objects during updates, especially when dealing with multiple instances of assets and diverse technology stacks, resulting in excessive maintenance and lack of interoperability.
Innovation Solution
An event data structure routing and processing system that uses a set of event processors to dynamically route and process event data structures generated by mobile devices, comparing event parameter identifiers to predefined rules to optimize data processing and reduce manual configuration efforts, thereby improving asset performance and data analytics efficiency.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Manufacturing precision
If manual configuration of data objects is performed for each asset, then data accuracy can be maintained, but time consumption and resource requirements increase significantly
Solution Approach 1:
The system segments data objects into templates and instances. Templates define the structure and configuration for asset types, while instances represent specific asset occurrences. This segmentation allows centralized template management that automatically propagates to multiple instances, reducing configuration time while maintaining data accuracy through template-driven consistency.
Solution Approach 2:
The system performs preliminary action by pre-defining data object templates with standard configurations before assets are created. When new assets are instantiated, they automatically inherit these pre-configured templates, eliminating the need for manual configuration of each individual asset and significantly reducing configuration time while maintaining accuracy.
2Stability of the object's composition
If individual data objects are reconfigured for each asset update, then data consistency is maintained, but maintenance effort and complexity increase
Solution Approach 1:
The system implements universality through reusable data object templates that can be applied across multiple asset instances. A single template update automatically propagates to all instances that use it, maintaining data consistency across the entire system without requiring individual reconfiguration of each asset, thereby reducing maintenance complexity.
Solution Approach 2:
The template acts as an intermediary between the central configuration system and individual asset instances. Updates are made to the template rather than directly to instances, and the template mediates the propagation of changes to all instances, ensuring consistency while simplifying the maintenance process through a single point of control.
3Adaptability or versatility
If manual configuration methods are used for diverse technology stacks, then system flexibility is maintained, but interoperability and resource allocation efficiency decrease
Solution Approach 1:
The system uses parameter changes to enhance flexibility while improving efficiency. Templates contain configurable parameters that can be adjusted to accommodate diverse technology stacks and asset types. This parameter-driven approach allows the system to adapt to different technologies without manual reconfiguration, enabling automatic resource allocation and improving productivity while maintaining versatility.
Data Source
AI summary
Various embodiments relate to event data structure routing and/or processing via an event processor platform. In an implementation, an event data structure is received. The event data structure can be generated by a mobile device based on an inspection event related to an asset located within an operational environment. Additionally, a first portion of the event data structure can include at least one event parameter identifier and a second portion of the event data structure comprises event data. In response to the event data structure, the at least one event parameter identifier is compared to a set of predefined event parameter rules for respective event processors of a set of event processors. Additionally, the event data structure is routed to a particular event processor in response to a determination that the at least one event parameter identifier satisfies the set of predefined event parameter rules.


