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

Standard Order Fulfillment – Successful Completion Sequence

  1. The order is submitted from Order Entry through the Orchestrator Submit Order interface. Note that this may use intermediate service layers. The order now has Start status
  2. Orchestrator sends a request to cache to store the order. The order now has Submitted status.
  3. Cache saves the order and returns a response to Orchestrator. The order now has Feasibility status.
  4. If feasibility is enabled, Orchestrator sends a request to the Feasibility Provider to perform feasibility checking on the order.
    1. Feasibility Provider may delegate the feasibility checking call to Validation as well as perform some internal checking.
    2. Validation returns the result of the order validation back to Feasibility Provider.
    3. Feasibility Provider aggregates all order feasibility checks and concludes that the order is feasible and sends a response back to Orchestrator.
  5. If feasibility is not enabled or the Feasibility Provider has returned the result then the order status is now Plan Development.
  6. Orchestrator sends a request to AOPD to analyze the order and design an execution plan.
  7. AOPD 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 and the plan now has Start status.
  8. Orchestrator sends a request to cache to store the plan. The plan now has Submitted status.
  9. Cache saves the plan and returns a response to Orchestrator. The plan now has Pending status.
  10. Orchestrator changes the plan status to Execution and begins invoking Process Components in the correct sequence. This is repeated for each plan item.
  11. Process Component returns a response to Orchestrator for each invocation.
  12. 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.