Event Processing Modules for User Activity Tracking
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing computer systems face challenges in tracking and determining the appropriateness of user activities due to multiple ways of accomplishing tasks, which can lead to difficulty in detecting primary and secondary events effectively.
Innovation Solution
The system employs a primary event module that communicates with the operating system to detect application events generated by user input and a secondary event module that processes these events to identify primary and secondary events, using recursive substring analysis to determine event sequences and graphically display likely event combinations, while also receiving schedule information to determine workstation usage and occupied seats.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If multiple computer applications are used to accomplish tasks, then task completion flexibility is improved, but user activity tracking difficulty increases
Solution Approach 1:
The system segments event detection into multiple specialized modules: a primary event module that detects basic application events, a secondary event module that detects more complex events, and a process definition module that defines business processes. Each module focuses on specific aspects of user activity, making the overall tracking system more manageable and effective despite the diversity of applications and tasks.
2Measurement precision
If multiple event detection modules are implemented, then event detection accuracy is improved, but system complexity increases
Solution Approach 1:
The event detection system is divided into distinct modules with specialized functions. The primary event module handles basic detection, while the secondary event module handles more complex events. This segmentation allows each module to be optimized for its specific purpose, improving overall detection accuracy while keeping individual module complexity manageable.
Solution Approach 2:
The process definition module acts as an intermediary that translates detected events into meaningful business processes. It receives events from both primary and secondary event modules, applies process definitions, and generates high-level process information. This intermediary layer simplifies the integration of multiple detection modules by providing a standardized interface and interpretation layer.
3Measurement precision
If recursive substring analysis is used to identify event sequences, then process identification accuracy is improved, but processing time increases
Solution Approach 1:
The system performs preliminary actions by pre-defining business processes and their associated event sequences in the process definition module. These process definitions are prepared in advance and stored for quick reference. When events are detected, the system can quickly match them against pre-defined patterns rather than performing full recursive analysis from scratch, reducing processing time while maintaining accuracy.
Solution Approach 2:
The recursive substring analysis is applied selectively rather than uniformly to all event sequences. The system identifies likely event sequences using the analysis and then applies more rigorous verification only to promising candidates, rather than exhaustively analyzing every possible sequence. This partial application of the complex analysis reduces overall processing time while maintaining high identification accuracy for relevant processes.
Data Source
AI summary
Embodiments disclosed herein provide systems and methods for processing events using existing computer event capture modules. In a particular embodiment, a method provides a primary event module communicating with an operating system to detect application events generated by user input and processing the application events to determine if a primary event has occurred. The method further provides a secondary event module communicating with the primary event module to obtain an indication of the application events detected by the primary event module and processing the application events to determine if a secondary event has occurred.