Orchestration System Update Handling via Queuing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Business agreement updates are blocked when the orchestration system is unavailable, leading to incomplete fulfillment and subsequent updates being blocked as well.
Innovation Solution
A system and method that handle business agreement updates by determining the unavailability of the orchestration system and performing actions such as providing notifications or resending updates when the system becomes available, allowing for merged changes to be resent once the system is operational.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If the orchestration system is unavailable, then system reliability is maintained by blocking updates, but productivity deteriorates as subsequent updates are blocked indefinitely
Solution Approach 1:
The system performs preliminary actions by queuing signed updates in a database when the orchestration system is unavailable. Instead of immediately blocking updates, the system prepares them for later processing by storing them in a persistent storage medium, allowing resubmission when the orchestration system becomes available again.
Solution Approach 2:
A message queue or intermediary storage mechanism is introduced between the CPQ system and the orchestration system. This intermediary allows updates to be buffered and forwarded when the orchestration system is available, resolving the contradiction by decoupling the immediate update signing from the orchestration execution.
2Stability of the object's composition
If updates are blocked when the orchestration system is unavailable, then data consistency is maintained, but loss of time increases as updates cannot be processed
Solution Approach 1:
The system performs preliminary actions by immediately storing signed updates in a database with timestamps and status markers when the orchestration system is unavailable. This preserves data consistency by ensuring no updates are lost, while minimizing time loss through immediate queuing rather than blocking.
Solution Approach 2:
The system maintains continuity of useful action by continuously accepting and queuing signed updates even when the orchestration system is unavailable. The queuing mechanism ensures that the update acceptance function continues uninterrupted, and processing resumes automatically when the orchestration system becomes available again.
3Stability of the object's composition
If the system blocks updates during orchestration unavailability, then system stability is preserved, but adaptability deteriorates as the system cannot handle external system failures
Solution Approach 1:
The system introduces dynamic behavior by implementing a state-aware update handling mechanism that adapts its response based on orchestration system availability. When unavailable, the system dynamically switches to queuing mode; when available, it switches to processing mode. This dynamic adaptation resolves the contradiction between stability and adaptability.
Solution Approach 2:
The system changes operational parameters based on orchestration system status. The update handling parameter transitions between 'block' and 'queue' states depending on availability. This parameter change allows the system to maintain stability through controlled responses while adapting to external conditions through flexible state transitions.
Data Source
AI summary
As described herein, a system, method, and computer program are provided for handling business agreement updates requiring orchestration when an orchestration system is unavailable. A signed update to a business agreement requiring orchestration by an orchestration system is received. It is determined that the orchestration system is unavailable to orchestrate requirements of the signed update to the business agreement. One or more actions are performed to handle the signed update in response to determining that the orchestration system is unavailable.