Process Engine for Automated Computer Event Monitoring

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing data processing systems lack automation in detecting and executing processes triggered by events on computers, requiring manual intervention and labor-intensive monitoring.

Innovation Solution

A data processing system comprising a processor, memory, and storage device with an interface for capturing events, a process engine for monitoring and identifying completed steps and processes, a trigger engine for executing software functions, and a reporting engine for generating reports, utilizing dependency relationships and real-time data management.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Extent of automation

If manual monitoring of computer events is used, then labor intensity is high, but automation level is low

Engineering Contradiction:

Improveautomation levelVSAvoidlabor intensity

Core Design Contradiction:

Extent of automationVSEase of operation

Solution Approach 1:

The system automatically monitors computer events, detects process steps, and executes actions without human intervention. The process engine autonomously captures events from the operating system, correlates them with defined process models, identifies completed steps, and triggers appropriate actions, making the monitoring system self-sufficient and eliminating manual labor.

Inventive Principle:

Principle #25Self-service

Solution Approach 2:

The patent replaces manual mechanical monitoring with an automated software-based process engine. Instead of human operators manually tracking events, the system uses electronic event capture, automated correlation algorithms, and software-driven process detection to substitute human labor with computational mechanisms.

Inventive Principle:

Principle #28Mechanics substitution (Replace mechanical system)

2Productivity

If automated process detection is implemented, then productivity increases, but system complexity increases

Engineering Contradiction:

Improvedetection efficiencyVSAvoidsystem complexity

Core Design Contradiction:

ProductivityVSDevice complexity

Solution Approach 1:

The system divides the complex task of process monitoring into distinct modular components: an event capture module that collects raw events, a process engine that correlates events with process models, a step detection module that identifies completed steps, and an action execution module that triggers responses. This segmentation allows each component to handle specific functions independently, managing complexity through modularity.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The process engine acts as an intermediary layer between raw computer events and high-level process detection. It translates low-level operating system events into meaningful process steps by correlating them with predefined process models, thereby simplifying the complexity of direct event-to-process mapping while maintaining high detection efficiency.

Inventive Principle:

Principle #24Intermediary (Mediator)

3Speed

If real-time event monitoring is performed, then response time improves, but computational resources increase

Engineering Contradiction:

Improveresponse timeVSAvoidcomputational resources

Core Design Contradiction:

SpeedVSUse of energy by moving object

Solution Approach 1:

The system performs preliminary actions by pre-defining process models, event correlations, and detection rules before runtime. The process engine is pre-configured with knowledge of what events signify process steps, eliminating the need for complex real-time analysis algorithms and reducing computational overhead during actual event monitoring while maintaining fast response times.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The system monitors only the specific events and processes that are relevant to defined business processes, rather than analyzing all possible computer events. This selective partial monitoring reduces computational resource consumption by focusing only on necessary event correlation and process detection, while still achieving real-time response for critical processes.

Inventive Principle:

Principle #16Partial or excessive action

Data Source

PatentUS9229769B2Monitoring of computer events and steps linked by dependency relationships to generate completed processes data and determining the completed processes data meet trigger criteria

Publication Date: 2016.01.05 VERINT AMERICAS INC

AI summary

A data processing system (1) is programmed with an interface (2) for capturing events which arise, and a process engine (3) for automatically monitoring captured events to identify completion of steps, each comprising a plurality of events linked by dependency relationships; and to identify completion of processes, each comprising a plurality of steps linked by dependency relationships. Software functions (5) execute in response to output of the process engine (3). The process engine (3) processes events to recognize a plurality of potential steps, but terminates other potential steps when completion of a step is determined. The process engine (3) processes steps to recognize a plurality of potential processes, but terminates other potential process when completion of a process is determined. The dependency relationships include Boolean AND operators and Boolean OR operators. There is a discrete start event for each step and a discrete start step for each process. The engine executes a plurality of processes simultaneously, applying captured events in real time to relevant steps, some events being applied to a plurality of steps.