--- schema_version: "1" id: 1ab59be14ed1d2e971adc0f5b6e47840ffadd5b7bb9b564720afc580ed4e090e title: Orchestration Plan Definition collection: admin version: current locale: en-us portal_url: https://docs.salesforce.com/admin/current/en-us/ind/264-0-0/comms_t_orchestration_plan_definition_231046.md canonical_url: https://help.salesforce.com/s/articleView?id=ind.comms_t_orchestration_plan_definition_231046.htm&release=264.0.0&type=5 source_site: help.salesforce.com content_type: documentation content_hash: 55641788c219245fb67e127f6b2746ebb0fb92a94815cf7a04ad14a6423cfef4 description: Industries Order Management uses orchestration plan definitions to specify how to fulfill orders across a set of fulfillment systems. Orchestration plan definitions group order processing tasks for the fulfillment requests that were created by the decomposition process. products: - Industry Solutions - Cross Cloud release: "264" --- # Orchestration Plan Definition Industries Order Management uses orchestration plan definitions to specify how to fulfill orders across a set of fulfillment systems. Orchestration plan definitions group order processing tasks for the fulfillment requests that were created by the decomposition process. Each orchestration plan is a collection of orchestration items that run in the correct sequence to fulfill the requests. Each plan forms a single swimlane in an orchestration process. An orchestration process is dynamically generated for each order based on orchestration scenarios that associate orchestration plans with commercial or technical products. Orchestration plan definitions are made up of of orchestration item definitions and orchestration scenarios. An orchestration plan definition may include both automated interactions with fulfillment systems as well as manual tasks that must be completed by users with specific skillsets. Tasks in the workflow are called orchestration items, and can execute in sequence or in parallel according to any dependencies that are detected between orchestration items in the flow. Plans are reusable components that can be associated with multiple products. ![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-ind-order_management-264-0-0-production-enus/c2040b01-aade-4ba7-8a7d-d7cd745d5c8c/images/icon_note.png) Note From release Spring '23, you can use the new fulfillment designer to manage your orchestration plan definitions and design-time fulfillment. See [The Fulfillment Designer](https://help.salesforce.com/s/articleView?id=ind.order_mgmt_the_fulfilment_designer.htm&release=264.0.0&type=5 "Use the Fulfillment Designer to save time and manage your design-time fulfillment in just the one page. The Fulfillment Designer allows you to create diagrams, which are visual, one-stop, canvases where you create (or import) orchestration plan definitions, orchestration item definitions, and their dependencies."). The Orchestration Plan Definition tab lets you: - View or create orchestration plans. - View or create orchestration items, conditions, and dependencies. - View or create orchestration scenarios. **Example of a swimlane in a fulfillment process** ![Example swimlane](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-ind-order_management-264-0-0-production-enus/c2040b01-aade-4ba7-8a7d-d7cd745d5c8c/order_management/images/om_orch_plan_swimlane.jpg) In this example: - An orchestration plan is for an order. - Orchestration items are color-coded to indicate the item's current status. At design-time, you can visualize what the orchestration plan might look like at runtime. You can see the Orchestration Plan Definitions and associated Orchestration Items Definitions from the Scenario page to get an idea of what the eventual project structure will look like for this orchestration scenario. ![Orchestration Plan details](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-ind-order_management-264-0-0-production-enus/c2040b01-aade-4ba7-8a7d-d7cd745d5c8c/order_management/images/om_print_button.png) The preview shows all the possibilities. You can update the Orchestration Plan Definition by doing any of the following: - Add or delete an Orchestration Item with or without dependencies. - Delete an Orchestration Item Dependency. - Update an Orchestration Item Name. - Update an Orchestration Plan Name. - Update an Orchestration Item Scope. - Update an Orchestration Plan Scope. As an Order Management implementation user, you can use the Print button on the Orchestration Plan to print or download a view. To print the orchestration plan, click **Print** and follow the prompts. ## Guidelines for Designing Orchestration Plan Definitions Orchestration plan definitions are very flexible, and can group processing tasks using a variety of different organizing principles. Salesforce recommends the following guidelines when designing orchestration plan definitions: - Create a master end-to-end plan to sequence the major milestones of all orders, such as the start of the order and the completion of the order. - Create separate orchestration plan definitions for each macro logical function, for example, provisioning, logistics, inventory, or billing. - Simplicity should be the goal, avoiding loops unless absolutely required. - Creating assets should occur as an Auto Task as the final orchestration item prior to the Complete Order milestone. When the assetize auto-task runs, it creates or updates assets and inventory items at the same time. Typically, assets are only created after fulfillment flow is completed.