---
title: "Configuring Planning Features for Irrigators"
canonical: "https://networkconnect.docs.rubiconwater.com/space/NC/3033333970/Configuring%20Planning%20Features%20for%20Irrigators"
format: markdown
---
> Macro (toc)

> Macro (details)
> 
> | **Source** | [Configuring Planning Features for Irrigators](https://rubiconwater.atlassian.net/wiki/spaces/NC/pages/3033333970) |
> | --- | --- |
> | **Space** | NC |
> | **Language** | English |

> Macro (hiddenfragment-macro)
> 
> > Macro (detailssummary)

# Configuring Notifications

Irrigators will receive the following notifications from the system. You can configure these notifications in the [https://rubiconwater.atlassian.net/wiki/spaces/CFGNC/pages/2018672641](https://rubiconwater.atlassian.net/wiki/spaces/CFGNC/pages/2018672641). In particular see [https://rubiconwater.atlassian.net/wiki/spaces/CFGNC/pages/2018672809](https://rubiconwater.atlassian.net/wiki/spaces/CFGNC/pages/2018672809). Users will automatically be signed up for any comm types that are configured to be *mandatory* or *opt-out*.

> ℹ️ **Note**
> ℹ️ 
> ℹ️ Notifications sent to the irrigator will include contact details for the Operations team. Use the **Operations Number** parameter on the System object to configure the contact number provided.

| **Notification** | **Description** | **Comm Type** |
| --- | --- | --- |
| Order Scheduled & Confirmation | Can be sent to the irrigator when a plan is published that includes their order. At this point the irrigator can log into CustomerConnect and confirm the order.<br>Note that you have the option NOT to send notifications when you publish the plan and you can auto-confirm orders (see [https://rubiconwater.atlassian.net/wiki/spaces/NC/pages/3033333948](https://rubiconwater.atlassian.net/wiki/spaces/NC/pages/3033333948)). | **Plan Finalisation Alert**<br>Optionally triggered by plan publication |
| Order Starting | Sent to the irrigator before the confirmation deadline to remind them to confirm their order and to let them know the order start time. If their order is linked to an upstream order the notice will include the contact details of the upstream irrigator. | **Order Confirmable Alert**<br>Uses a notice period measured from the order start time. The default notice period for this is 60 minutes (provided the plan has been finalised) |
| Confirmation Expired | Sent to the irrigator if they have not confirmed the order before the confirmation deadline to let them know that their order will not be delivered.<br>Note that a planner can still confirm the order if necessary. | **Order Not Confirmed Final Alert**<br>Uses a notice period measured from the order start time. The default notice period for this alert is 30 minutes but you can configure this as required, |
| Order Ending | Sent to the irrigator at a specified period before the end of the order. This notification will include the contact details of the downstream irrigator if there is a following linked order.<br>Note that, if the notice period for the alert is longer than the order duration, the notification will not be sent. | **Order Confirmed End Alert**<br>Uses a notice period measured from the order end time.The default notice period for this alert is 90 minutes but you can configure this as required, |

## Restricting Notifications to the Operator who Placed the Order

Order notifications can be configured to be sent to all the operators for an outlet or only to the operator who lodged the order. Use the **Lodged Party Only** attribute on the Customer Communication Type to configure this. See [https://rubiconwater.atlassian.net/wiki/spaces/CFGNC/pages/2869755915](https://rubiconwater.atlassian.net/wiki/spaces/CFGNC/pages/2869755915) 

- Do not set the **Lodged Party Only** attribute, or set it to *No* to include all operators for an outlet. This is the default.
- Set the **Lodged Party Only** attribute to *Yes* to restrict notifications to the operator who lodged the order.

> Macro (hiddenfragment-macro)
> 
> <span style="color: #ff5630">**Not yet implemented 20262**</span>
> 
> Remove section above - now that notifications are order specific the system will use whatever set of operators were selected for the previous order. The first order will ,,, by default (this initial default behaviour can be configured by Rubicon Support).
> 
> <span style="color: #ff5630">**end of hidden**</span>

## Configuring Notifications for Specific Orders

You can configure notifications at the order level when requesting a new order or from the Order Details screen. See [https://rubiconwater.atlassian.net/wiki/spaces/NC/pages/2868773103](https://rubiconwater.atlassian.net/wiki/spaces/NC/pages/2868773103) and [https://rubiconwater.atlassian.net/wiki/spaces/NC/pages/1914765735](https://rubiconwater.atlassian.net/wiki/spaces/NC/pages/1914765735) for more details.

# Configuring the Start Date/Time Range Notified to the Irrigator

Irrigators are given an expected time range for the order start time when the order is published. You can configure this time range by using the **Order Start Tolerance** and the **Order End Tolerance** attributes which can be set at the system level or on a lower-level object down to the outlet level.

> ℹ️ **Note**
> ℹ️ 
> ℹ️ The default value for both attributes is 3 hours

So when a notification is sent out the time range for the order start will be:

*(Scheduled time - Order Start Tolerance)* to *(Scheduled time + Order End Tolerance)*.

### What happens if the Operator has Linked Orders?

If the operator has lodged several linked orders in the same plan, they will only receive a start notification for the first order and a finish notification for the last order provided the orders share a source regulator. Source regulators are configured with the [PARENT-METERED relation](https://rubiconwater.atlassian.net/wiki/spaces/NC/pages/3032055810).

# Configuring Default Flow Rate and Remaining Allocations Display

When irrigators create or modify an order:

- The default flow rate for their outlet can be defaulted in for them.
- If the flow rate is set to a value above zero, they will also be able to see their remaining water allocation during the ordering process.

To enable these features, set the **Default Flow Rate** attribute for the outlet to a positive value.

# Displaying the Flow Rate of the Upstream Regulator on the CustomerConnect Home Page

When an order is operating at a metered outlet, the current flow rate at the outlet is displayed on the CustomerConnect Home page. If an outlet is unmetered you can configure CustomerConnect to use the flow at the upstream regulator instead.

To do this you must create a PARENT METERED relation between the outlet and the regulator. See [https://rubiconwater.atlassian.net/wiki/spaces/NC/pages/3032055810](https://rubiconwater.atlassian.net/wiki/spaces/NC/pages/3032055810)