Centralized Incident Communication Interface for Knowledge Management

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current knowledge management systems in businesses are decentralized, leading to inefficiencies in storing, accessing, and sharing production support information across departments and lines of business, resulting in time-consuming and costly processes for resolving incidents and auditing, with no centralized system for tracking and managing knowledge effectively.

Innovation Solution

A centralized knowledge management system with an incident communication interface that allows for the tracking, identification, and resolution of incidents across the organization, featuring a user interface, memory device, and processor configured to initiate incident tickets, communicate with associates, provide access to knowledge management tools, and store incident details in a database.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If knowledge management systems are decentralized and department-specific, then each department can store and access its own knowledge effectively, but knowledge cannot be shared across departments and lines of business, and incident resolution becomes time-consuming

Engineering Contradiction:
Improvedepartmental knowledge accessVSAvoidknowledge sharing across departments
Core Design Contradiction:
Ease of operationVSLoss of information

Solution Approach 1:

The patent merges previously decentralized departmental knowledge bases into a single centralized knowledge management system. The system consolidates knowledge from multiple departments and lines of business into unified repositories that are accessible organization-wide, eliminating knowledge silos while maintaining structured access controls. This allows associates to access both department-specific and cross-departmental knowledge through a single interface.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The centralized knowledge management system provides universal access to knowledge across all departments and functions. The system serves multiple purposes: storing departmental knowledge, enabling cross-departmental knowledge sharing, supporting incident resolution, and providing audit capabilities. A single system fulfills what previously required multiple separate departmental systems.

Inventive Principle:
Principle #6Universality (Multi-functionality)

2Reliability

If associates escalate incidents through calls or e-mails to call centers, then they can get support for incidents outside their department, but the process becomes time-consuming and removes key associates from their day-to-day responsibilities

Engineering Contradiction:
Improveincident resolution supportVSAvoidincident resolution time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The knowledge management system enables associates to self-service incident resolution by providing direct access to comprehensive knowledge bases, troubleshooting procedures, and resolution guidance. Associates can search and apply knowledge independently without escalating to call centers or subject matter experts, thereby resolving incidents faster and remaining productive on their day-to-day responsibilities.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system pre-organizes and makes immediately accessible all necessary knowledge, procedures, and troubleshooting information in a centralized location. When incidents occur, associates can instantly access pre-prepared knowledge articles and resolution steps without waiting for human intervention, enabling immediate self-service resolution.

Inventive Principle:
Principle #10Preliminary action

3Measurement precision

If audit reviews are conducted manually with data collection and face-to-face meetings on a LOB-by-LOB basis, then detailed review can occur, but the process becomes expensive and time-consuming that increases exponentially with business size

Engineering Contradiction:
Improveaudit review detailVSAvoidaudit review time
Core Design Contradiction:
Measurement precisionVSLoss of time

Solution Approach 1:

The patent replaces manual mechanical audit processes with an automated electronic system. The knowledge management system automatically collects, organizes, and presents audit-relevant data from all departments in a standardized format. Automated reporting and analysis tools eliminate the need for manual data collection and face-to-face meetings, providing precise audit capabilities that scale efficiently with business size.

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

4Adaptability or versatility

If each department stores data and documents in different manners, then departments can organize information according to their specific needs, but audit teams must review each department separately and the process becomes particularly expensive and time consuming

Engineering Contradiction:
Improvedepartmental data organizationVSAvoidaudit process complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The centralized knowledge management system maintains local quality by allowing each department to organize and store data according to its specific needs and preferences within the unified system. Departments can use their own classification schemes and organizational structures locally, while the system provides a standardized interface and aggregation mechanism for audit purposes, eliminating the need to review each department separately.

Inventive Principle:
Principle #3Local quality

Data Source

PatentUS8266072B2Incident communication interface for the knowledge management system
Publication Date: 2012.09.11 BANK OF AMERICA CORP
  • US8266072B2 patent drawing
  • US8266072B2 patent drawing
  • US8266072B2 patent drawing

AI summary

Embodiments of the present invention include a method, system, computer program product, or a combination of the foregoing for creating a knowledge management system with an incident communication interface for production support incidents that is standardized and centralized across the channels and sub-channels in an organization. The incident communication interface system is used to track, identify, and resolve the incidents that occur throughout the organization. The incident communication interface allows business associates to initiate an incident ticket associated with an incident. The incident communication interface also communicates information related to an incident to business associates. The incident communication interface provides the business associates knowledge management system access. The incident communication interface receives user input including details related to resolving the incident and the incident details are stored in the incident report database.