The workflow to solve
A subscription order may require OSS fulfilment and a provisioning layer to create or amend network subscriber information. The BSS workflow needs to know which action was requested and what the downstream system actually confirmed.
A practical software boundary
Map the commercial and network identifiers, define the operation contract and agree how execution status is returned. The Order Orchestration Platform can be evaluated as the coordination boundary around that work.
What the design should demonstrate
Test a lost response as well as an explicit rejection. The integration needs a way to discover the current state before repeating an action whose outcome is uncertain.
- Validate the identifiers and parameters required by the interface.
- Distinguish queued work from completed execution.
- Retain a correlation trail across the order and network action.
- Define reconciliation and controlled recovery.