Incident Notification System with Personalized Subscriptions

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Traditional notification systems are unidirectional and lack personalized communication, failing to provide timely and relevant updates to recipients about incidents, as they often rely on generic messages and do not account for user preferences or status monitoring.

Innovation Solution

A method and system for managing incident notifications that classify incidents by priority and severity, provide personalized updates through a user interface accessible via multiple devices, and allow users to subscribe to specific notifications, enabling feedback and status monitoring.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If traditional notification systems use email and text messages to broadcast status to mass groups, then information can be distributed widely, but the system lacks personalization and users cannot monitor status or provide feedback

Engineering Contradiction:
Improvepersonalization capabilityVSAvoidsystem complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The system segments the mass audience into individual user profiles with personalized subscription preferences. Each user can selectively subscribe to specific incident types, sources, and severity levels, transforming the generic broadcast system into targeted personalized notifications while maintaining the underlying broadcast infrastructure.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system implements feedback mechanisms by allowing users to acknowledge receipt of notifications and providing status monitoring capabilities. Users can view current incident status and confirm they have received and processed the information, creating a closed-loop communication system that tracks delivery and engagement.

Inventive Principle:
Principle #23Feedback

2Loss of information

If the system provides generic messages to all recipients, then implementation is simple, but recipients cannot determine relevance to their specific needs

Engineering Contradiction:
Improveinformation relevanceVSAvoidnotification management complexity
Core Design Contradiction:
Loss of informationVSDevice complexity

Solution Approach 1:

The system applies local quality by allowing different users to receive different subsets of incident information based on their roles, responsibilities, and preferences. Each user's notification stream is customized to contain only the incidents relevant to their specific needs, rather than uniform generic messages to all recipients.

Inventive Principle:
Principle #3Local quality

Solution Approach 2:

The notification system is made dynamic by allowing users to modify their subscription preferences at any time. Users can add or remove incident types, sources, and severity levels from their subscriptions, enabling the system to adapt to changing user needs and roles without reimplementation.

Inventive Principle:
Principle #15Dynamics

3Reliability

If the system sends updates through new messages, then information is delivered, but recipients have limited ability to monitor status and understand current situation

Engineering Contradiction:
Improvestatus monitoring capabilityVSAvoidtime to understand incident status
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system prepares users for incident monitoring by pre-configuring subscription preferences and organizing incident information into structured categories before incidents occur. When incidents are reported, users already have their notification preferences set, enabling immediate personalized delivery without requiring users to configure anything during the incident response.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system introduces an intermediary layer between incident reporting and user notification that consolidates and structures incident information. This intermediary processes raw incident data, matches it against user subscriptions, and delivers only relevant information, saving users time by filtering out irrelevant details and presenting only what they need to know.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS11030579B1Method and system for incident communication
Publication Date: 2021.06.08 JPMORGAN CHASE BANK NA
  • US11030579B1 patent drawing
  • US11030579B1 patent drawing
  • US11030579B1 patent drawing

AI summary

An embodiment of the present invention is directed to a computer implemented method and system for managing incident notification. The system uses bi-directional (two way) communication of incidents to multiple users where the system gives them substantial control over the information they need and want. An embodiment of the present invention may be aware of whether they have received and consumed that information thereby enabling those users to rapidly engage in additional communication paths (e.g., chat sessions, phone/video sessions, etc.) as needed to inform them and solicit their input into problem solving.