Central Hosted Component Workflow Management

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Modifying installed applications to extend functionality or integrate new features at customer sites is resource-intensive and time-consuming, often requiring custom modifications and extensive testing, leading to system downtime and burdensome processes, especially when applied across multiple customer sites.

Innovation Solution

An extensible infrastructure that connects installed application components with a central hosted component, allowing the central component to manage workflows, augment information, and alter application behavior without modifying the installed application code, using an extensible infrastructure that includes a central hosted component interacting with installed application components via a network, enabling the central component to manage insurance-related workflows and provide alerts or holds based on external data like weather information.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If installed applications are modified to extend functionality or integrate new features, then application functionality is improved, but resource consumption and time requirements increase significantly

Engineering Contradiction:
Improveapplication functionalityVSAvoidmodification time
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The patent introduces a service provider system as an intermediary between the central hosted component and installed applications. This intermediary manages the complexity of modifications by handling configuration, deployment, and coordination across multiple customer sites, thereby reducing the time and resources required for functionality extension while maintaining adaptability

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If custom modifications are made to installed applications, then application functionality is extended, but system downtime increases

Engineering Contradiction:
Improveapplication functionalityVSAvoidsystem downtime
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The service provider system performs preliminary actions by pre-configuring and pre-testing modifications before deploying them to production environments. This allows functionality extensions to be prepared in advance, reducing the actual downtime required during deployment and minimizing disruption to customers

Inventive Principle:
Principle #10Preliminary action

3Adaptability or versatility

If installed applications are modified across multiple customer sites, then application functionality is extended, but complexity and resource requirements increase

Engineering Contradiction:
Improveapplication functionalityVSAvoidmodification complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The service provider system implements a universal platform that can manage modifications across multiple customer sites through a single interface. This multi-functional system handles configuration, deployment, and monitoring for numerous installations simultaneously, reducing the complexity and resource requirements compared to managing each site separately

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

4Reliability

If extensive testing is performed on modified applications, then reliability is improved, but time and resource consumption increase

Engineering Contradiction:
Improveapplication reliabilityVSAvoidtesting time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The service provider system performs extensive testing in advance during the configuration and preparation phase, before deploying modifications to production. This preliminary testing ensures reliability is established beforehand, reducing the time required for post-deployment validation and minimizing the impact on customers

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS10373263B1Extensible infrastructure for managing workflow on a plurality of installed application components that interact with a central hosted component
Publication Date: 2019.08.06 GUIDEWIRE SOFTWARE INC
  • US10373263B1 patent drawing
  • US10373263B1 patent drawing
  • US10373263B1 patent drawing

AI summary

Managing workflow on a plurality of installed application components that interact with a central hosted component is disclosed. A rule defined on the central hosted component is obtained. A new action item to be executed on an installed application component in the plurality of installed application components is generated at least in part by applying the obtained rule based at least in part on data provided by the installed application component and information that is managed by the central hosted component. The new action item to be executed by the installed application component is communicated. The new action item modifies a workflow on the installed application component without modifying application code on the installed application component.