Telecommunication Service Order Task Flow Bottleneck Identification

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing customer service troubleshooting systems fail to accurately track and analyze the life cycle of task flows for telecommunication service orders, leading to inefficiencies and bottlenecks due to the inability to distinguish between tasks performed by multiple agents and interactions with centralized system components.

Innovation Solution

A method and system that gather and correlate usage data from agents' computers and centralized system components to determine the life cycle of task flows, identifying bottlenecks and issues by attributing active time spent on specific tasks, and determining if centralized system components or agent performance is the cause of processing delays.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Measurement precision

If traditional customer service troubleshooting systems are used, then system simplicity is maintained, but the ability to track and analyze task flow life cycle is insufficient

Engineering Contradiction:
Improvetask flow tracking precisionVSAvoidsystem complexity
Core Design Contradiction:
Measurement precisionVSDevice complexity

Solution Approach 1:

The system segments task flow tracking into distinct components: agent device usage data collection, centralized system component interaction logging, and correlated analysis modules. This segmentation enables precise task flow measurement while maintaining manageable system complexity through modular architecture.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces an intermediary correlation system that bridges agent device data and centralized system component data. This intermediary layer enables comprehensive task flow analysis without requiring direct complex integration between all system components, thus improving measurement precision while controlling overall system complexity.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If multiple agents and system components are involved in task flows, then service capability is enhanced, but the ability to identify bottlenecks deteriorates

Engineering Contradiction:
Improveservice capabilityVSAvoidbottleneck identification accuracy
Core Design Contradiction:
Adaptability or versatilityVSMeasurement precision

Solution Approach 1:

The system implements feedback mechanisms that continuously collect usage data from agent devices and centralized system components, correlate this data to identify bottlenecks in task flows, and provide actionable insights. This feedback loop enables accurate bottleneck identification while maintaining the versatility of multi-agent, multi-component service capabilities.

Inventive Principle:
Principle #23Feedback

3Measurement precision

If comprehensive usage data is collected from all sources, then analysis accuracy is improved, but data processing time increases

Engineering Contradiction:
Improveanalysis accuracyVSAvoiddata processing time
Core Design Contradiction:
Measurement precisionVSLoss of time

Solution Approach 1:

The system performs preliminary actions by collecting and organizing usage data from agent devices and centralized system components as tasks are executed, rather than attempting to retrieve and correlate all data afterward. This preliminary data preparation reduces processing time while maintaining comprehensive analysis accuracy.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS10346221B2Determining life-cycle of task flow performance for telecommunication service order
Publication Date: 2019.07.09 AT&T INTELLECTUAL PROPERTY I L P
  • US10346221B2 patent drawing
  • US10346221B2 patent drawing
  • US10346221B2 patent drawing

AI summary

A method includes a processor for determining a life cycle of a first performance of a task flow for a telecommunication service order, determining that a performance of a first task within the first performance of the task flow has exceeded a threshold processing time, and determining that there is a problem with a first centralized system component in response to determining that the performance of the first task within the first performance of the task flow has exceeded the threshold processing time. The method may further include identifying the centralized system component for servicing when it is determined that there is a problem with the centralized system component.