Supplemental Software Enhancement Shipment Infrastructure

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing software deployment systems struggle to efficiently provide and manage supplemental features for individual customers, as standard product releases often fail to meet unique customer needs, and providing custom upgrades is resource-intensive and impractical for software providers.

Innovation Solution

An infrastructure that supports the creation, assembly, and provisioning of supplemental software enhancements, including a Content Production Management System (CPMS) and Product and Production Management System (PPMS), allows for targeted shipment and installation of supplements without altering the main software product, enabling on-demand development and management of custom features.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If a software product provider provides additional features as a new product release, then all customers receive a common set of functionalities, but this does not adequately address the desired requirements of particular customers with unique needs

Engineering Contradiction:
Improveability to meet individual customer requirementsVSAvoidcomplexity of managing different product releases
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent segments the software product into a base product and separate supplemental features (add-ons). The base product remains unchanged and universally supported, while supplemental features are independently developed, tested, and deployed. This segmentation allows customers to receive only the specific features they need without requiring full product version upgrades, thereby meeting individual requirements while maintaining manageable complexity.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent extracts specific supplemental features from the main product codebase into separate, independent supplement packages. These extracted features can be individually managed, shipped, and installed without altering or retesting the entire product. This extraction enables targeted delivery of custom features while avoiding the complexity of managing multiple complete product releases.

Inventive Principle:
Principle #2Taking out (Extraction)

2Adaptability or versatility

If a software product provider provides a complete product upgrade at the request of an individual customer, then the customer receives desired features, but the modification is time and resource intensive

Engineering Contradiction:
Improvecustomization to customer requestVSAvoidefficiency of feature delivery
Core Design Contradiction:
Adaptability or versatilityVSProductivity

Solution Approach 1:

By segmenting features into independent supplements, the provider can deliver only the specific requested features rather than complete product upgrades. This segmentation enables efficient, targeted development and deployment that responds to customer requests without the time and resource overhead of full product version cycles.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent implements partial action by delivering only the specific supplemental features customers request, rather than providing complete product upgrades. This partial delivery approach maintains productivity by avoiding unnecessary development, testing, and deployment of unrelated features while still fully meeting customer customization needs.

Inventive Principle:
Principle #16Partial or excessive action

3Adaptability or versatility

If the customer requirements do not coincide with the software provider's product release schedule, then individual customer needs are not met, but providing custom upgrades is not practical or efficient

Engineering Contradiction:
Improvealignment of customer needs with product availabilityVSAvoidtime for development and deployment
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The patent enables preliminary action by allowing supplemental features to be developed, tested, and shipped independently of the main product release schedule. Customers can receive supplemental features as soon as they are ready, without waiting for the next scheduled product release. This preliminary delivery of specific features aligns product availability with customer needs while avoiding the time loss associated with synchronized release cycles.

Inventive Principle:
Principle #10Preliminary action

4Adaptability or versatility

If the main software product is altered to include supplemental features, then custom features can be integrated, but compatibility and supportability may be compromised

Engineering Contradiction:
Improveintegration of custom featuresVSAvoidcompatibility and supportability
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The patent segments supplemental features into separate packages that do not alter the main product. The base product remains unchanged, preserving its compatibility and supportability, while supplemental features are independently integrated at the customer's system. This segmentation maintains reliability while enabling adaptability.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces an intermediary mechanism (the supplement delivery and installation system) that bridges the main product and supplemental features. This intermediary allows custom features to be delivered and integrated without directly modifying or risking the integrity of the main product, thereby maintaining compatibility and supportability while enabling customization.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS8250561B2Shipment infrastructure for add-on content
Publication Date: 2012.08.21 SAP SE
  • US8250561B2 patent drawing
  • US8250561B2 patent drawing
  • US8250561B2 patent drawing

AI summary

A system including a software maintenance tool of a business process platform to manage software changes related to a main software product including a software enhancement supplement of the main software product; and a control unit interfaced with the software maintenance tool and provided by a software product provider to create, assemble, and provision the software enhancement supplement to the software maintenance tool based on a type of content comprising the software enhancement supplement.