Before Plan Creation

Order amendment is the process of modifying an order after submission. An amendment before plan development occurs prior to the creation of a plan within Orchestrator. The sequence is shown in the following diagram. Note that Validation has been removed for simplicity.

In this sequence the amendment is shown as occurring after the response from AOPD. Note that the amendment may occur at any point before this event. The key factor is that the plan has not yet been created in Orchestrator.

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 Transient Data Store to store the order. The order now has Submitted status.
3. Transient Data Store saves the order and returns a response to Orchestrator. The order now has Feasibility status.
4. Orchestrator sends a request to the Feasibility Provider to perform feasibility checking on the order.
5. Feasibility Provider aggregates all order feasibility checks and concludes that the order is feasible and sends a response back to Orchestrator. 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. The order amendment is submitted from Order Entry through the Orchestrator Submit Order interface.
9. Orchestrator sends a request to Transient Data Store to store the amended order. The order now has Submitted status.
10. Transient Data Store saves the amended order and returns a response to Orchestrator. The order now has Feasibility status.

Processing now continues as in the normal Standard Order Fulfillment case.

Copyright © Cloud Software Group, Inc. All rights reserved.