Service-Oriented Architecture for Scalable Supply Chain Control

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Enterprise software systems, particularly those with supply chain control functionality, face challenges in scalability and cost-effectiveness due to their complexity and distributed nature, requiring a robust architecture that allows for independent deployment of components across multiple hardware platforms.

Innovation Solution

A services architecture design that includes service operations, process components, and deployment units, enabling scalable and cost-effective implementation by defining pair-wise interactions between process components across different deployment units, with business objects and process agents facilitating efficient communication and transaction management.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If enterprise software systems are implemented with distributed components across multiple hardware platforms, then adaptability and versatility are improved, but device complexity increases

Engineering Contradiction:
Improvedeployability across platformsVSAvoidsystem architecture complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent segments the enterprise software system into independent deployment units, each containing specific process components that can be deployed separately on different hardware platforms. This segmentation enables the system to adapt to multiple platforms while managing complexity through modular organization.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent creates universal service interfaces that allow process components to interact across different deployment units and hardware platforms through standardized protocols. This universality enables the same software components to function across diverse platforms without increasing architectural complexity.

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

2Productivity

If process components are distributed across separate deployment units, then scalability is improved, but ease of operation deteriorates

Engineering Contradiction:
ImprovescalabilityVSAvoidcomponent interaction management
Core Design Contradiction:
ProductivityVSEase of operation

Solution Approach 1:

The patent introduces service interfaces as intermediaries between process components in different deployment units. These standardized interfaces simplify component interaction by providing uniform communication protocols, making it easier to manage distributed components while maintaining scalability.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Reliability

If service interfaces are defined for pair-wise interaction between process components, then reliability is improved, but device complexity increases

Engineering Contradiction:
Improveinteraction reliabilityVSAvoidinterface definition complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent defines universal service interfaces that can handle multiple types of interactions between process components through standardized methods. This approach improves reliability by ensuring consistent interaction patterns while reducing interface definition complexity through reusability.

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

Data Source

PatentUS8359218B2Computer readable medium for implementing supply chain control using service-oriented methodology
Publication Date: 2013.01.22 SAP SE
  • US8359218B2 patent drawing
  • US8359218B2 patent drawing
  • US8359218B2 patent drawing

AI summary

Methods and apparatus, including systems and computer program products, for a services architecture design that provides enterprise services having supply chain control functionality at the level of an enterprise application. The design includes a set of service operations, process components, and optionally deployment units. Suitable business objects are also described.