E-procurement Hierarchy Splitting for Service Line Allocation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

E-procurement systems face complexity in managing service line hierarchies with multiple sub-tasks, as they are typically configured to handle goods rather than services, making it difficult to allocate and manage sub-service line items effectively across multiple entities.

Innovation Solution

An e-procurement system that generates an object hierarchy with a parent node and multiple child nodes, allowing for the allocation of sub-tasks to multiple entities by using a combination of stored hierarchies, artificial intelligence, and user input to split the hierarchy and generate electronic contracts for each entity.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If e-procurement systems use traditional goods-oriented configuration, then system simplicity is maintained, but ability to manage service line hierarchies with multiple sub-tasks deteriorates

Engineering Contradiction:
Improveability to manage service line hierarchiesVSAvoidsystem configuration complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The system segments service line hierarchies into parent nodes and child nodes, allowing each node to be independently configured and allocated. This segmentation enables the system to handle complex service structures by breaking them down into manageable units that can be assigned to different entities separately.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The e-procurement system is designed with universal capabilities to handle both goods and services through a unified hierarchy management approach. The same system infrastructure manages different object types (goods, services, sub-tasks) using consistent data structures and allocation mechanisms, eliminating the need for separate systems.

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

2Productivity

If service line hierarchies are allocated to multiple entities, then task distribution efficiency is improved, but allocation management complexity increases

Engineering Contradiction:
Improvetask distribution efficiencyVSAvoidallocation management complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The hierarchy is segmented into allocatable nodes that can be independently assigned to different entities. Each node contains identification information that enables automated matching with entity capabilities, simplifying the allocation process despite multiple entities involved.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system incorporates feedback mechanisms where entity responses and performance data are collected and used to refine future allocations. This feedback loop enables the system to learn from previous allocations and automatically optimize task distribution, reducing the perceived complexity for users.

Inventive Principle:
Principle #23Feedback

3Productivity

If AI and historical data are used to propose optimal splits, then allocation optimization is improved, but system complexity increases

Engineering Contradiction:
Improveallocation optimizationVSAvoidsystem architecture complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The system performs preliminary analysis of historical data and entity capabilities before making allocations. By pre-processing data and identifying optimal allocation patterns in advance, the system reduces real-time computational requirements and presents pre-evaluated allocation options to users.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The AI component acts as an intermediary between historical data and allocation decisions. It processes complex data relationships and translates them into simplified allocation recommendations, shielding users from the underlying complexity while delivering optimized results.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS11257035B2Splitting a task hierarchy
Publication Date: 2022.02.22 SAP SE
  • US11257035B2 patent drawing
  • US11257035B2 patent drawing
  • US11257035B2 patent drawing

AI summary

In one aspect, there is provided a method including presenting a first user interface including an object hierarchy comprising a parent node and a plurality of child nodes; receiving, at a second user interface, a first selection allocating at first portion of the object hierarchy to a first device; receiving, at the second user interface, a second selection allocating a second portion of the object hierarchy to a second device; and when a selection at a user interface element of a third user interface is received, sending an indication to a system to enable generation of a fourth user interface presenting a first electronic document for the first device and generation of a fifth user interface presenting a second electronic document for the second device. Related systems, methods, and articles of manufacture are also disclosed.