Dynamic Service Procedure System for Centralized Configuration Management

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Service organizations face challenges in ensuring that service representatives have access to complete and up-to-date documentation for procedures, as existing documentation is often static and not readily shared across different parts of the organization, leading to inconsistencies and outdated information.

Innovation Solution

A system and method that utilize a central database containing software modules for tasks and services, where information specifying a procedure is received, and software modules are invoked to access both default and custom configurations, consolidating operational tasks into a procedure provided to operatives, ensuring they have the latest information.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If static documentation is used, then documentation is easy to store and access, but the information becomes outdated and inconsistent across different parts of the organization

Engineering Contradiction:
Improveaccuracy of procedural informationVSAvoidcomplexity of documentation system
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent transforms static documentation into a dynamic system where procedures are automatically updated and redistributed. The documentation system now responds to changes in real-time, ensuring that all users access the latest version of procedures without manual intervention, thus resolving the contradiction between reliability and complexity.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The system implements feedback mechanisms where changes to procedures are automatically detected, processed, and communicated to all relevant users. This feedback loop ensures that documentation remains accurate and up-to-date while maintaining system manageability through automated processes.

Inventive Principle:
Principle #23Feedback

2Adaptability or versatility

If documentation is customized for specific customers or geographic areas, then the procedures become more relevant and accurate, but the documentation becomes harder to share and access across the organization

Engineering Contradiction:
Improvecustomization of proceduresVSAvoidaccessibility of documentation
Core Design Contradiction:
Adaptability or versatilityVSEase of operation

Solution Approach 1:

The patent creates a universal documentation system that can handle both generic and customized procedures. The system maintains a centralized repository that serves all users while automatically incorporating customizations for specific customers or geographic areas, making the system both universally accessible and specifically adaptable without sacrificing either aspect.

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

3Loss of information

If documentation is maintained manually, then the system is simpler to implement, but the information becomes outdated and incomplete

Engineering Contradiction:
Improvecompleteness of procedural informationVSAvoidautomation of documentation updates
Core Design Contradiction:
Loss of informationVSExtent of automation

Solution Approach 1:

The system performs preliminary actions by automatically detecting and processing changes to procedures before they need to be distributed. This proactive approach ensures that all users receive complete and up-to-date information without requiring manual verification or distribution processes.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS8689056B2Method and system for providing customer service information
Publication Date: 2014.04.01 ENT SERVICES DEV CORP LP
  • US8689056B2 patent drawing
  • US8689056B2 patent drawing
  • US8689056B2 patent drawing

AI summary

A method and system for providing customer service information provide a central database containing software modules for tasks and services and configurations for the modules. Information is received specifying a procedure to be carried out. Software modules relating to tasks forming part of the procedure are invoked, and the information indicative of appropriate configurations for the specified procedure is passed to the software modules. The software modules access the configurations, and instantiate operational tasks applying the configurations. The operational tasks are consolidated into an operational procedure, and the operational procedure is provided to an operative.