---
title: "Configuring Notice Periods for Ordering"
canonical: "https://docs.rubiconwater.com/space/PNC/2051866897/Configuring%20Notice%20Periods%20for%20Ordering"
format: markdown
---
> Macro (toc)

Notice period attributes control when orders can be placed and changed by customers. If you manually place an order in the Orders module, you have the option of overriding the configured notice periods.

The parameters used for notice periods depend on the way that the scheduling mode has been configured for an outlet. See <u>[Configuring the Scheduling Mode ](https://rubiconwater.atlassian.net/wiki/spaces/PNC/pages/2051899589)</u>for more details.

Alternatively, you can specify a daily *cut off time* after which customers cannot place or apply changes to orders for the duration of a *blackout period*. See <u>[Configuring Cut off Times for Ordering](https://rubiconwater.atlassian.net/wiki/spaces/PNC/pages/2051899634)</u> for more details.

> ℹ️ **Caution**
> ℹ️ 
> ℹ️ To avoid confusion we recommend that you implement EITHER notice periods OR cut off times and blackout periods, but not both at the same time.

# Attribute Scope

Note that some attributes can be set at the system, area, or group. Attributes set at a lower level in the hierarchy take precedence.

> ℹ️ **Example**
> ℹ️ 
> ℹ️ An attribute set on an area takes precedence over the same attribute set on the system.

# Standard Notice Period Attributes

> ℹ️ **Note**
> ℹ️ 
> ℹ️ Notice period attributes may be affected by what other attributes are set. See [How do Notice Period Attributes Work?](https://rubiconwater.atlassian.net/wiki/spaces/PNC/pages/edit-v2/2051866897#How-Do-Notice-Period-Attributes-Work%3F) for more details.

| **Attribute** | **Description** | **TCC Mode at Outlet** | **Available Scope** |
| --- | --- | --- | --- |
| Required Notice to Enter Order | Minimum notice required for placing an order on a manually planned or manually scheduled outlet. | No | system, planning group, area, group |
| Required Notice to Vary Order | Minimum notice required to change the start or finish time, the flows, or the plantings of an order on a manually planned or manually scheduled outlet. | No | system, planning group, area, group |
| Lodge Notice Minimum | Minimum notice required for placing an order on an outlet that is configured for automatic order scheduling. | Yes, Partial | area, planning area, system |
| Lodge Notice Maximum | Maximum time in advance that an order can be placed on an outlet that is configured for automatic order scheduling. | Yes, Partial | area, planning area, system |
| Change Notice | Notice required to change the finish time for an order on an outlet that is configured for automatic order scheduling. | Yes, Partial | area, planning area, system |
| Maximum finish time offset | Maximum order finish time allowed for an outlet. | Any | system |
| Notice Period | Time in seconds before an order starts and stops when a message will be sent to the customer advising them of the event.<br>See <u>[Configuring the Notice Period for Order Start and Stop Alerts](https://support.rubiconwater.com/help/dms/content/topics/modules/commtypes/pcd_configorderstartstop.htm)</u> for more details. | Any | comm type |

# How Do Notice Period Attributes Work?

Attributes are NOT independent of each other. In particular:

- If the **Lodge Notice Minimum** is NOT set, then the **Lodge Notice Maximum** is measured from the current time. However, if the **Lodge Notice Minimum** IS set, then the **Lodge Notice Maximum** is measured from the *END *of the **Lodge Notice Minimum**.
- If the **Lodge Notice Maximum** is NOT set, then the **Max Finish Offset** is measured from the current time. However, if the **Lodge Notice Maximum** IS set, then the **Max Finish Offset** is measured from the *END *of the **Lodge Notice Maximum**.
- The **Change Notice** is independent of the other attributes. (It may be shorter than, equal to, or more than the **Lodge Notice Minimum**.)

## Notice Period Calculator

Download this calculator to calculate the possible start, finish, and change times for orders given the attribute settings:

## Lodging an Order

These diagrams illustrate what order start and finish times are permitted when lodging an order depending on the notice period attributes that are set.

If DMS needs to re-schedule a requested order it searches for a suitable start time between the earliest and latest possible start times. The time closest to the requested start time will be returned as the suggested start time. If there are equally close start times before and after the requested time then DMS will choose the later time.

## Cancelling a Pending Order

Starting from the time of the cancellation request, the start time of the earliest cancellable order is at *Current Time + Change Notice*. Orders that start  before this time cannot be cancelled (but you can use the Emergency Stop function to stop an operating order.

## Changing the Start Time of a Pending Order

These diagrams illustrate what order start times are permitted when changing an order.

## Changing the Finish Time of an Operating Order

These diagrams illustrate what order finish times are permitted when changing an order.

> ℹ️ **Note**
> ℹ️ 
> ℹ️ - The relationships between the **Lodge Notice Minimum**, **Lodge Notice Maximum**, and **Max Finish Offset** are as described above under [Lodging an Order](https://rubiconwater.atlassian.net/wiki/spaces/PNC/pages/edit-v2/2324070432#Lodging-an-Order).
> ℹ️ - The **Change Notice** is independent of the other attributes. (It may be shorter than, equal to, or more than the **Lodge Notice Minimum**.)

## Changing the Flow Rate of an Operating Order

For changing the flow rate of an operating order the rules are:

- The earliest time that the flow can change is after the duration of the **Change Notice**.

## Stopping an Operating Order (Emergency Stop)

There are no *notice* restrictions on stopping an operating order, but whether this option is enabled depends on how the **Emergency Stop** function is configured. See [https://rubiconwater.atlassian.net/wiki/spaces/PNC/pages/2051866852](https://rubiconwater.atlassian.net/wiki/spaces/PNC/pages/2051866852) for details.

---