---
schema_version: "1"
id: 6b472a23cc53bb4cee9506e002e67b977540e7682c70da350fa5be7eaf1aa06c
title: Orchestrate Orders with Time-Awareness
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/ind/264-0-0/dro_time_aware_plan_sequence.md
canonical_url: https://help.salesforce.com/s/articleView?id=ind.dro_time_aware_plan_sequence.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 609100e626ea3aeb2ce2ef2d03e4e448b561e8ee62b026e53a7f603df3b69a01
description: Dynamic Revenue Orchestrator (DRO) sequences fulfillment steps across time period. Steps for a future period wait for the preceding period to finish, while configured dependencies continue to control the order of execution within each period.
products:
  - Revenue Cloud
release: "264"
---
# Orchestrate Orders with Time-Awareness

Dynamic Revenue Orchestrator (DRO) sequences fulfillment steps across time period. Steps for a future period wait for the preceding period to finish, while configured dependencies continue to control the order of execution within each period.

### Required Editions

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

When DRO creates an orchestration plan for a time-aware order, it groups instantiated fulfillment steps that apply to the same time period. DRO sequences these groups according to the start and end dates and times of the steps’ sources. It then adds dependencies from the applicable final steps in one group to the applicable first steps in the next group. As a result, fulfillment for a later period begins only after the required fulfillment for the preceding period finishes.

DRO preserves dependencies configured within each time period, including dependencies that use Plan, Bundle, Line Item, or Custom scope. Steps in the same period can run in parallel unless a configured dependency requires them to run sequentially. If a group has multiple first or final steps, DRO connects the applicable steps so that the required steps in the preceding period finish before the dependent steps in the next period begin.

![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-ind-revenue-264-0-0-production-enus/91ca99c6-d5c8-4986-b961-c6b7801e0d0d/images/icon_note.png)

Note

- To sequence fulfillment correctly across time periods, configure the required dependencies and scopes in the fulfillment step definitions and step dependencies. DRO preserves this configuration within each time period and uses it when connecting one time-period group to the next.
- A fulfillment step whose sources span multiple time periods can remain shared across the periods instead of belonging to a single time-period group.

## Example: Fulfillment Across Time Periods

Consider an order with a two-year ramp for Sales Cloud and Service Cloud. In year 1, the plan runs Provision Tenant, Activate License, and Notify Customer according to their configured dependencies and scopes. Steps without dependencies between them run in parallel. DRO sequences the groups of instantiated steps according to the start and end dates and times of their sources. The applicable year 2 steps start only after the required Year 1 steps finish.

![Two-year ramp showing fulfillment steps grouped by time period. The required year 1 steps finish before the applicable year 2 steps start.](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-ind-revenue-264-0-0-production-enus/91ca99c6-d5c8-4986-b961-c6b7801e0d0d/revenue/images/dro/dro_orchestration_plan_sequence.png)