Manual Order Plan Development

Manual Order Plan Development (MOPD) gives users the control to modify the Automated Order Plan Development developed plan. In Manual Order Plan Development, plan development happens through TIBCO Order Management - Long Running User Interface under predefined logical boundaries.

  1. Order is submitted by using JMS or HTTP.
  2. Order Management Server picks up the order request and saves the record into the database.
  3. Router Component of Order Management Server routes the order request to Orchestrator by using JMS or can invoke the orchestrator service directly (in Process).
  4. Orchestrator sends the order Request to Automated Order Plan Development/JMS/third party for draft plan generation.
  5. Orchestrator receives the draft plan and halts the further execution until final plan is not received.
  6. User searches for the manual order which is supposed to be edited manually.
  7. User retrieves the order details for manual order and gets order details in Order Management Server UI.
  8. User traverse to the draft plan (showing Manual Order Plan Development plan similar to execution Plan) which is saved earlier.
  9. User can see the draft plan in user interface.
  10. User instructs to get draft plan in UI. This indicates that user wants to edit the plan now.
  11. User can edit the plan now by adding/modifying/deleting Plan-Item, Milestones and Dependencies in the plan developed by Automated Order Plan Development.
  12. User edits the draft plan through the TIBCO Order Management - Long Running UI and instructs to save the plan in database.
  13. Plan is saved in database.
  14. User instructs to execute this plan.
  15. Plan is validated by using the validation framework provided by server.
  16. If plan is valid then Orchestrator is notified with the final plan and it starts execution of the plan.
  17. If plan is not valid then application returns back specifying that plan is not valid and plan can be corrected.

Server and Client Side Validations

A plan manually modified after being instructed to go into execution by the user does not go for Automated Order Plan Development rule validation. Hence, it is user's responsibility to modify the plan correctly. Some of the plan level validation by default happen at the client side which is covered in the TIBCO Order Management - Long Running Administration guide.