Order Orchestration

After the decomposition function is complete, the process of communicating with external systems to fulfill an order can begin. Industries Order Management controls the interactions with these external systems through order orchestration.

Order Management uses the catalog to dynamically generate, sequence, and monitor orchestration processes according to the specific context of each order and to ensure that the information contained on the order is communicated to the systems that realize or fulfill the order. This may include fulfillment systems, such as billing, workforce management, inventory, activation, and others.

The orchestration plan that is generated also ensures orchestration items or tasks in the workflow execute in the correct sequence and provide the correct information to each fulfillment system according to the fulfillment action performed.

An orchestration plan may include both automated interactions with fulfillment systems as well as manual tasks that must be completed by users with specific skill sets. Orchestration items in the workflow can execute in sequence or in parallel according to any dependencies that are detected between orchestration items in the flow.

During orchestration, the order management application is responsible for communicating fulfillment status back to order capture channels.

When a new version of an orchestration flow is deployed, new orders flowing into the system run on the new version. The previous version of the orchestration flow is frozen and orders currently executing on the frozen version are allowed to complete. No new orders run against the old version.

For information about the Industries data model, see: Industries Communications Data Model.

• Dynamically Generated Workflows
  Industries Order Management workflows are entirely dynamically assembled to provide optimal support for the many types and combinations of products that can be present on communications orders.
• 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.
• The Fulfillment Designer
  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 View
  After an order has been submitted and decomposed, the Orchestration Plan is generated. The Orchestration Plan View shows orchestration items and their dependencies on each other.
• Assetization and Activation in Industries Order Management
  Assetization and activation are related concepts with different implications and triggers in Industries Order Management. The "In this section" topics explain these concepts.
• Orchestration Scenarios
  Industries Order Management uses orchestration scenarios to determine when an orchestration plan definition should execute. Define an orchestration scenario by specifying a product entity and an order action such as Add, Modify, Disconnect, or NoChange.
• Orchestration Items
  Orchestration items represent the tasks and activities in an orchestration plan that are performed during the order process, and they are grouped by an orchestration plan definition.
• Manual Queues and Manual Tasks
  Manual queues are created by administrators and contain manual tasks. When an order is processed, ​Industries Order Management​​ automatically creates instances of manual tasks and places them in a manual queue as defined by the orchestration item definition.
• Partial Assetization of Product Attributes
  You can set a technical product attribute as "not assetizable" so that Order Management doesn't store Personally Identifiable Information (PII) in OM internal technical inventory. In fact, OM doesn't store that information permanently at all.
• Use Assetization and Encryption Options for Product Attributes
  You can set a technical product attribute as "not assetizable" so that Order Management does not store Personally Identifiable Information (PII) in OM internal technical inventory (or anywhere else on a permanent basis).
• Updating Salesforce Records During Order Fulfillment
  As a CSR, you may need to update existing Salesforce records during the order fulfillment process.
• Order Delay Predictions with Einstein Discovery
  Fulfillment managers can prevent delays in order fulfillment by using predictions from an Einstein Discovery model to identify in-progress orders that are at risk of delay. They can then determine and fix any issues delaying the upcoming tasks and expedite the order delivery. The probability of delay is updated as the order progresses through the orchestration plan.
• Order Management Plus: Accessing Pricing Information
  You can write Apex code or JAVA to access pricing information so that price adjustments can be decomposed in Amazon Web Services.