Standard Order

This is the normal flow of events through standard order fulfillment with no exceptions. The sequence is shown in the following diagram:

Standard Order Fulfillment – Successful Completion Sequence

1. The order is submitted from Order Entry through the Orchestrator Submit Order HTTP protocol. Note that this might use intermediate service layers.
2. Orchestrator sends a request to cache to store the order. The order now has Pending status.
3. Cache saves the order and returns a response to Orchestrator.
4. Orchestrator sends a request to Automated Order Plan Development to analyze the order and design an execution plan.
5. Automated Order Plan Development sends a response back to Orchestrator with the execution plan definition. Orchestrator then generates a plan based on this definition. The order now has Execution status.
6. Orchestrator sends a request to cache to store the plan.
7. Cache saves the plan and returns a response to Orchestrator. The plan now has Pending status.
8. Orchestrator changes the plan status to Execution and begins invoking Process Components in the correct sequence. This is repeated for each plan item.
9. Process Component returns a response to Orchestrator for each invocation.
10. Once all plan items have completed, the plan is set to Complete status. Orchestrator sends a request to cache to change the order status to complete for archiving. The order status then goes to Complete in Orchestrator.