Context-Aware Productivity Service Augmentation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Business applications often have outdated features and user interface components, limiting user productivity due to the need for complete upgrades and compatibility issues with third-party services, especially in heterogeneous environments where users require different features and configurations based on roles and preferences.

Innovation Solution

The system determines a user's context to integrate productivity features with existing applications, augmenting the user interface with graphical objects and allowing flexible deployment models, such as on-demand or on-premise services, to provide context-sensitive enhancements independent of the application's release lifecycle, enabling users to access specific features and services without modifying the underlying application.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If a complete upgrade of the business application is performed to update with new GUI or features, then user productivity and functionality are improved, but the complexity and cost of deployment increases, and compatibility issues may arise

Engineering Contradiction:
Improveuser productivityVSAvoiddeployment complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent segments the application upgrade process by separating the core business application from the user interface components. Instead of upgrading the entire application, only the UI layer is updated through web technologies, allowing incremental improvements without full deployment complexity

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces a web browser as an intermediary layer between the user and the business application. This mediator enables delivery of updated UI components without directly modifying the core application, reducing deployment complexity while maintaining productivity improvements

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If the application is upgraded to provide newer features, then functionality is enhanced, but compatibility with existing systems and third-party services may be compromised

Engineering Contradiction:
ImprovefunctionalityVSAvoidcompatibility
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The patent implements dynamic adaptability where the web-based UI layer can be independently updated to provide newer features while maintaining compatibility with the core application through standardized web protocols, allowing functionality enhancement without compromising reliability

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The patent uses universal web technologies (HTML, CSS, JavaScript) that can interact with multiple different business applications and third-party services through standard web APIs, providing enhanced functionality while maintaining broad compatibility across different systems

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

3Reliability

If on-premise deployment is used to maintain control over application updates, then security and control are improved, but the speed of deploying new features and updates is reduced

Engineering Contradiction:
ImprovecontrolVSAvoiddeployment speed
Core Design Contradiction:
ReliabilityVSSpeed

Solution Approach 1:

The patent segments the deployment process by allowing the web-based UI components to be updated and delivered independently through web servers, while the core application remains under on-premise control. This enables faster deployment of UI features without sacrificing control over the core system

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent allows UI components to be prepared and validated in web environments before being deployed to on-premise systems. This preliminary action in a more flexible web environment accelerates the development and testing process while maintaining on-premise control during actual deployment

Inventive Principle:
Principle #10Preliminary action

4Productivity

If different users are provided with different features and configurations, then user satisfaction and productivity are improved, but the complexity of managing multiple configurations increases

Engineering Contradiction:
Improveuser satisfactionVSAvoidconfiguration management complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent implements preliminary configuration where user preferences, roles, and features are defined through metadata and configuration files before the application runs. This allows different user configurations to be prepared in advance, improving user satisfaction while reducing the complexity of real-time configuration management

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent enables users to self-configure their own experience through the web interface by selecting features and customizing their workspace based on their roles and preferences. This self-service capability improves user satisfaction while reducing the administrative burden of managing complex configurations

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS9275365B2Integrated productivity services
Publication Date: 2016.03.01 SAP SE
  • US9275365B2 patent drawing
  • US9275365B2 patent drawing
  • US9275365B2 patent drawing

AI summary

The present disclosure involves systems, software, and computer implemented methods for providing integrated productivity services. One process includes operations for determining a context associated with a user of an application, identifying a user productivity feature for integration with an existing feature of the application based on the context, and augmenting a user interface of the application with a graphical object representing the user productivity feature. In some instances, the context can include an integration context defining a particular release version associated with the application. The context can also or alternatively include a role context defining a particular role of the user of the application within an organization, wherein the particular role is associated with a set of permissions or common tasks performed by the particular role. Still further, the context can include a user context defining a personal preference or habit of the user.