Chat-Based Software Provisioning Interface

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional software provisioning processes are cumbersome and time-consuming due to the complexity of managing customer-specific features, lack of user-friendly interfaces, inconsistent feature naming, and scattered dependent feature configurations, leading to difficulties in enabling features and potential loss of functionality.

Innovation Solution

An interactive chat-based user interface system that uses natural language processing to interpret user inputs, determine requested features and dependent features, and enable them through a provisioning database, with confirmation from the user and automatic provisioning of unenabled dependent features.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If conventional provisioning tools are used, then feature provisioning can be performed, but the process is cumbersome and time-consuming due to complex back-and-forth communication between customer and CS/PS team

Engineering Contradiction:
Improveprovisioning speedVSAvoidturnaround time for feature addition
Core Design Contradiction:
ProductivityVSLoss of time

Solution Approach 1:

The patent implements a self-service provisioning system where customers can directly add features through a chat interface without requiring CS/PS team intervention. The system automatically verifies feature availability, checks dependencies, and provisions features, eliminating the need for manual back-and-forth communication and significantly reducing turnaround time.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The patent introduces a chatbot as an intermediary between the customer and the provisioning system. This intermediary handles natural language queries, translates them into provisioning actions, and manages the entire workflow automatically, bridging the gap between user-friendly interaction and complex backend processing.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Ease of operation

If conventional provisioning interfaces are used, then features can be configured, but the interface is not user-friendly and difficult for customers to use directly

Engineering Contradiction:
Improveuser-friendliness of provisioning interfaceVSAvoidcomplexity of provisioning system
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The patent replaces the traditional mechanical provisioning interface (complex forms, menus, and configuration screens) with a conversational chat interface. This substitution allows users to interact using natural language, dramatically simplifying the user experience while the backend handles the complexity of feature configuration and dependency management.

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

Solution Approach 2:

The chatbot acts as an intermediary that translates simple user queries into complex provisioning operations. Users only need to specify what feature they want, and the chatbot handles the complexity of interpreting requirements, checking dependencies, and executing the provisioning process.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Adaptability or versatility

If feature names are not standardized, then different feature names can be used, but inconsistency in enabling essential components results in functionality loss

Engineering Contradiction:
Improveflexibility in feature namingVSAvoidconsistency of feature enabling
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The patent implements a universal feature identification system that accepts multiple names and aliases for the same feature (e.g., 'metadata framework (MDF)' and 'Generic Object' both refer to the same feature). The system maintains a mapping between different names and their corresponding feature identifiers, ensuring consistent handling regardless of the name used by the customer.

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

4Ease of operation

If dependent features are not automatically identified, then manual lookup is required, but this makes finding scattered dependent features difficult and time-consuming

Engineering Contradiction:
Improveease of finding dependent featuresVSAvoidtime to locate and enable dependent features
Core Design Contradiction:
Ease of operationVSLoss of time

Solution Approach 1:

The patent performs preliminary identification of all dependent features before the actual provisioning action. When a customer requests a feature, the system proactively queries the dependency database, identifies all required dependent features, and presents them to the user for confirmation before execution, eliminating the need for manual searching.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system provides feedback to the user about identified dependent features, allowing them to review and confirm the complete set of features to be provisioned. This feedback mechanism ensures transparency and gives users control over the provisioning process while automating the complex dependency analysis.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS10558753B2Software provisioning using an interactive chat-based user interface
Publication Date: 2020.02.11 SAP SE
  • US10558753B2 patent drawing
  • US10558753B2 patent drawing
  • US10558753B2 patent drawing

AI summary

Systems and methods for performing software provisioning using an interactive chat-based user interface. The method includes receiving a chat input from a user by a chat controller. The method further includes interpreting the user input using natural language processing to determine a requested feature to be provisioned to the user. The method further includes determining, by accessing a provisioning database, an identifier of the requested feature and identifiers of dependent features which are to be provisioned with the requested feature. The method further includes enabling the requested feature and the determined dependent features by accessing the provisioning database based on at least one parameter, the at least one parameter comprising an identifier of the requested feature and the identifiers of the determined dependent features obtained in the determining step.