Large Line Item Event Routing for Faster Sourcing Processing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing sourcing systems struggle to process large line item (LLI) events efficiently, as they exceed the 30-second data processing limit and require separate handling via spreadsheets, limiting reporting and analysis capabilities, while changing the core sourcing application poses risks due to its stability for standard-size events.
Innovation Solution
A scalable solution that reroutes LLI event processing requests to a specialized content service, utilizing a document database for storage and retrieval, enabling faster operations through a microservice-based stack and concurrent processing.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If the core sourcing application is modified to handle large line item events, then processing capability for LLI events is improved, but system stability is worsened due to the risks of changing a stable core system
Solution Approach 1:
The system is divided into two independent pathways: the existing core sourcing application handles standard-size events, while a new specialized content service handles large line item events. This segmentation allows the core system to remain stable and unchanged, while the new service provides extended functionality for LLI events without risking the stability of the proven core system.
2Device complexity
If LLI events are processed using the existing core sourcing application, then system simplicity is improved, but processing speed is worsened as events exceed the 30-second data processing limit
Solution Approach 1:
A specialized content service acts as an intermediary between the graphical user interface and the database for LLI events. This intermediary service is specifically optimized to handle large volumes of line items efficiently, using concurrent processing and specialized data structures, thereby achieving fast processing speeds for LLI events while keeping the rest of the system architecture simple and unchanged.
3Reliability
If LLI events are handled separately via spreadsheets, then processing capability for standard events is preserved, but reporting and analysis capabilities are worsened due to integration limitations
Solution Approach 1:
The specialized content service provides multi-functionality by handling both the processing of LLI events and the generation of comprehensive reports and analysis. It can retrieve data from the database, process it, and provide reporting capabilities through the graphical user interface, thereby eliminating the need for separate spreadsheet handling and integrating full reporting functionality into the system.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
In an example embodiment, a scalable solution is provided that identifies sourcing events that are large line item events and reroutes requests for operations related to such events to a specialized content service. The specialized content service authenticates the requests and causes data pertaining to the large line item events to be stored in and/or retrieved from a document database for LLI event processing. The result is that operations for LLI events are able to be processed much faster than in prior art solutions.