Graph-Based User Space Assignment for Project Efficiency

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

When an assigned user is unavailable, projects associated with that user may languish, leading to increased memory and network overhead due to persistent data structures and repeated status checks.

Innovation Solution

A system that applies graph representations of user spaces to determine a set of users for a project based on both expertise and availability, using keywords and properties from project data structures to select suitable users and transmit visual indicators of user availability for user interface displays.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If projects are automatically allocated to users based on expertise, then project assignment efficiency is improved, but memory overhead increases when assigned users are unavailable

Engineering Contradiction:
Improveproject assignment efficiencyVSAvoidmemory overhead
Core Design Contradiction:
ProductivityVSQuantity of substance

Solution Approach 1:

The system performs preliminary actions by pre-calculating and storing user availability status and expertise matching in advance. When a project needs assignment, the system queries pre-computed user availability data and expertise graphs to quickly identify suitable users without needing to track every project detail continuously, thus reducing memory overhead while maintaining assignment efficiency.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system extracts critical assignment information from the full project data structure, specifically separating user availability status and expertise matching criteria from the complete project tracking data. This extraction allows the system to maintain only essential project information in memory while using external data sources for availability and expertise queries, reducing overall memory consumption.

Inventive Principle:
Principle #2Taking out (Extraction)

2Reliability

If projects are tracked continuously to ensure completion, then project completion reliability is improved, but network overhead increases due to repeated status checks

Engineering Contradiction:
Improveproject completion reliabilityVSAvoidnetwork overhead
Core Design Contradiction:
ReliabilityVSLoss of energy

Solution Approach 1:

The system implements periodic status checks instead of continuous monitoring. Users can configure notification preferences and update frequencies, allowing the system to check project status at predetermined intervals rather than continuously. This periodic action maintains project completion reliability through regular updates while significantly reducing network overhead by eliminating constant status check traffic.

Inventive Principle:
Principle #19Periodic action

Solution Approach 2:

The system establishes feedback mechanisms where users proactively notify the system of their availability status and project completion state. This feedback approach allows the system to maintain accurate project tracking information without initiating frequent status check requests, thereby reducing network overhead while ensuring reliable project completion tracking through user-initiated updates.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS20250077994A1Applying graph representations of user spaces
Publication Date: 2025.03.06 CAPITAL ONE SERVICES LLC
  • US20250077994A1 patent drawing
  • US20250077994A1 patent drawing
  • US20250077994A1 patent drawing

AI summary

In some implementations, an expert system may receive, from a user device, a data structure representing a project associated with a technical request. The expert system may map the data structure to a graph representation of a user space to determine a set of users. The expert system may determine a set of statuses, corresponding to the set of users, associated with availability of the set of users. The expert system may transmit, to the user device, instructions for a user interface including visual indicators for the set of users and the set of statuses. The expert system may receive, from the user device, an indication of a selected user from the set of users and may transmit a message addressed to the selected user.