Plan Development Failed

This is the flow of events through standard order fulfillment with Automated Order Plan Development indicating that the order is not valid for plan development. The sequence is shown in the following diagram:

Standard Order Fulfillment–Plan Development Failed Sequence

  1. The order is submitted from Order Entry through the Orchestrator Submit Order interface. Note that this might use intermediate service layers. The order now has Start status.
  2. The orchestrator sends a request to Data Service to store the order. The order now has submitted status.
  3. The data service saves the order and returns a response to the orchestrator. The order now has feasibility status.
  4. If feasibility is enabled, the orchestrator sends a request to the feasibility provider to perform feasibility checking on the order.
    1. The feasibility provider might 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 the Feasibility Provider.
    3. The feasibility Provider aggregates all order feasibility checks and concludes that the order is feasible and sends a response back to the Orchestrator.
  5. If feasibility is not enabled or the Feasibility Provider has returned the result then the order status is now Plan Development.
  6. The orchestrator sends a request to Automated Order Plan Development to analyze the order and design an execution plan.
  7. Automated Order Plan Development sends a response back to the orchestrator indicating the order is not valid for plan design. The order status is now pre-qualification failed.
  8. The orchestrator sends the order and the validation messages from Automated Order Plan Development to the pre-qualification failed handler for manual intervention.
  9. The pre-qualification failed handler sends a response back to the orchestrator with one of two possible actions:
    1. Withdraw the order, which terminates execution and the order status is now withdrawn.
    2. Resubmit the order with an updated version. This flow continues as a normal order amendment flow.