---
schema_version: "1"
id: e0cfa891d0dc6bc39d3f6549f1476aaa25a2f54794749cd345ca43345c4ab03b
title: Use Case Scenarios for CME - DRO
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/ind/264-0-0/comms_use_case_scenarios_for_cme_dro.md
canonical_url: https://help.salesforce.com/s/articleView?id=ind.comms_use_case_scenarios_for_cme_dro.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: e21e20db069fe22ec528a34fe188e298b285d2de7df03cfb5e6aa1011ad0153b
description: Here are advanced logic examples, which automate complex order lifecycles from initial product decomposition to mid-fulfillment amendments and asset relocation. The process ensures proper technical execution across move orders and legacy systems while synchronizing staged assetization with commercial intent. By using attribute-based rules and point-of-no-return (PONR) logic, the system makes sure that technical fulfillment remains perfectly synchronized with commercial intent.
products:
  - Communications
  - Media
  - Energy and Utilities
release: "264"
---
# Use Case Scenarios for CME - DRO

Here are advanced logic examples, which automate complex order lifecycles from initial product decomposition to mid-fulfillment amendments and asset relocation. The process ensures proper technical execution across move orders and legacy systems while synchronizing staged assetization with commercial intent. By using attribute-based rules and point-of-no-return (PONR) logic, the system makes sure that technical fulfillment remains perfectly synchronized with commercial intent.

### Required Editions

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small edition"><colgroup><col style="width:100%"></colgroup><tbody><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;">Available in: Lightning Experience</td></tr><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;">Available in: <strong>Enterprise</strong>, <strong>Unlimited</strong>, and <strong>Developer</strong> Edition.</td></tr></tbody></table>

- **[Configuring Decomposition Rules & Mappings](https://help.salesforce.com/s/articleView?id=ind.comms_configuring_decomposition_rules_mappings.htm&release=264.0.0&type=5)**  
    Product decomposition automates technical fulfillment by breaking down commercial bundles into specific, actionable tasks based on attributes, classes, and custom fields. This logic-driven approach reduces manual errors and makes sure that every product variation triggers the precise technical sequence required for delivery.
- **[Configuring Orchestration Rules](https://help.salesforce.com/s/articleView?id=ind.comms_configuring_orchestration_rules.htm&release=264.0.0&type=5)**  
    Orchestration rules synchronize the entire product lifecycle by triggering dynamic fulfillment plans based on specific attributes, order actions, and dependencies. These rules turn on staged assetization to align billing with actual delivery timelines while automating data feedback, such as serial numbers, through reverse propagation.
- **[Managing In-Flight Order Amendments](https://help.salesforce.com/s/articleView?id=ind.comms_managing_in_flight_order_amendments.htm&release=264.0.0&type=5)**  
    These use cases demonstrate how the order management system dynamically orchestrates changes to "in-flight" orders to maintain fulfillment accuracy.
- **[DRO & Legacy OM Co-Existence](https://help.salesforce.com/s/articleView?id=ind.comms_dro_legacy_om_co_existence.htm&release=264.0.0&type=5)**  
    Show that orders fulfilled by DRO and a legacy OM+ system create a unified but distinguishable asset view for a single customer.
- **[CME - DRO Move Order](https://help.salesforce.com/s/articleView?id=ind.comms_dro_move_order.htm&release=264.0.0&type=5)**  
    Move orders synchronize the de-provisioning of equipment at an old location with its re-installation to a new one, ensuring the transfer of the location-dependent services. The system distinguishes the "Move" actions from standard adds or cancels, helps operators to trigger specialized fulfillment logic for relocated assets.
- **[CME - DRO Change of Plan](https://help.salesforce.com/s/articleView?id=ind.comms_dro_change_of_plan.htm&release=264.0.0&type=5)**  
    In a Change of Plan (COP) order, the system manages both the replaced asset and the new replacement product within a single order. This unified process ensures an easy transition between old and new offers.