Event Chain Mapping for Trigger Impact Management
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current event management systems fail to account for the intricacies of chained effects of triggers, such as changes to event times or locations, and are unable to systematically link past and future events relevant to an entity for effective management.
Innovation Solution
A method and apparatus that generate a timeline of events, identify event chains based on cause-and-effect relationships, detect triggers, and identify the effects of these triggers, including insights, actions, and opportunities, using a data storage system, event manager, and graphical user interface to present these effects visually.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of information
If current event management services are used to store and notify events, then basic event tracking is achieved, but the services are unable to determine how a change to the time or location of one event may affect multiple other events
Solution Approach 1:
The system segments event management into discrete event chains, where each chain represents a sequence of related events connected by cause-and-effect relationships. This segmentation allows the system to track and analyze the impact of changes to individual events on subsequent events in the chain, without requiring analysis of all possible event combinations simultaneously.
Solution Approach 2:
The system introduces event chains as an intermediary structure that mediates between individual events and their effects. By organizing events into chains with defined relationships, the system can systematically trace the impact of trigger events through multiple intermediate events to identify all affected downstream events, rather than directly analyzing all event-to-event relationships.
2Reliability
If the system tracks multiple events and their relationships, then comprehensive event management is achieved, but the ability to systematically show and link past and future events is insufficient
Solution Approach 1:
The system performs preliminary action by pre-establishing event chains and their relationships before changes occur. Event chains are constructed in advance based on historical data and defined policies, creating a structured framework that enables rapid identification of affected events when triggers occur, rather than analyzing relationships in real-time when changes happen.
Solution Approach 2:
The system implements feedback by continuously monitoring events against established event chains and policies. When events occur or change, the system automatically evaluates their impact on downstream events and provides feedback about affected events, enabling systematic linking of past and future events based on actual event occurrences and pre-defined relationships.
3Loss of information
If the system identifies all effects of a trigger including insights, actions, and opportunities, then comprehensive event analysis is achieved, but the processing time and computational resources increase
Solution Approach 1:
The system applies local quality by differentiating between types of effects (insights, actions, opportunities) and processing them according to their specific characteristics and priorities. Different effect types can be processed with different levels of detail and timing, allowing the system to identify and prioritize critical effects while optimizing processing resources based on the local requirements of each effect category.
Solution Approach 2:
The system implements partial action by identifying and processing the most critical effects of triggers first, rather than waiting to analyze all possible effects comprehensively. The system can provide immediate notification of high-priority effects (such as actions that require immediate response) while continuing to analyze less critical effects in the background, reducing perceived processing time for urgent matters.
Data Source
AI summary
A method and apparatus for managing events. A stream of event data for a plurality of events corresponding to an entity is received. A timeline for the plurality of events is generated based on the stream of the event data. A set of event chains is identified based on the timeline, the event data, and a set of policies. A trigger related to an event belonging to an event chain of the set of event chains is detected. A number of effects of the trigger is identified in which the number of effects includes at least one of a number of insights, a number of actions, or a number of opportunities.