---
title: "Customer Connect Order Rules"
canonical: "https://docs.rubiconwater.com/space/PNC/2086895800/Customer%20Connect%20Order%20Rules"
format: markdown
---
> Macro (toc)

> ℹ️ **Note**
> ℹ️ 
> ℹ️ If the outlet is stopped, you cannot modify/ stop the order other than to modify plantings in CustomerConnect.

# Terminology

- TCC YES/PARTIAL → YES* - means when unplanned/not finalised
- TCC NO → YES* - means when unplanned/not finalised/not in latest plan
- YES (future) - YES for future flow items

### Assumptions:

- Order cut off and notice period are honoured with modification

> ℹ️ **Note**
> ℹ️ 
> ℹ️ CustomerConnect uses the parameter **Allow irrigators to modify any of their pending orders**. The modify options presented to the user are based on that parameter as per the tables below (Note that setting the option to *NO* gives the user the same abilities as Irrigator Portal (with some exceptions).

# General Order Modification Rules

<details>
<summary>Allow irrigators to modify any of their pending orders is NO and order is not rationed</summary>

| **Order Status** | **Feature** | **Standard Order**<br>**TCC = YES**<br>Plan is not relevant | **Standard Order**<br>**TCC = PARTIAL**<br>Plan is not relevant | **Standard Order**<br>**TCC = NO**<br>Not in plan | **Standard Order**<br>**TCC = NO**<br>In plan or finalised | **Low Volume** | **Unsatisfied**<br>**TCC = YES** | **Unsatisfied**<br>**TCC = PARTIAL** | **Unmetered SP**<br>(IGNORE THIS - Unmetered SPs should behave in the same way as metered) |
| --- | --- | --- | --- | --- | --- | --- | --- | --- | --- |
| OPERATING | Modify Start | NO | NO | NO | NO | Confirmed with MIA (Andrew P) that low volume orders are no longer required.<br>Therefore this will not be implemented in CC | NO | NO | NO |
| Modify End | YES | YES | NO | NO | NO | NO | NO |
| Modify Flow | YES if multiple flows are allowed.<br>NO if only single flow | YES | NO | NO | NO | NO | N/A |
| Modify Stored Water<br>*(Customer Specific)* | YES | YES | NO | NO | NO | NO | N/A |
| Modify Planting<br>*(Customer Specific)* | YES | YES | YES | YES | NO | NO | N/A |
| Cancel | NO | NO | NO | NO | YES | YES | NO |
| Stop<br>(Only TCC YES/PARTIAL with PS_STOP tag) | YES | YES ( when `Disable Emergency Stop for TCC partial orders` is disabled) | NO | NO | NO | NO | NO |
| PENDING | Modify Start | YES | NO | NO | NO | NO | NO | NO |
| Modify End | NO | NO | NO | NO | NO | NO | NO |
| Modify Flow | NO | NO | NO | NO | NO | NO | N/A |
| Modify Stored Water<br>*(Customer Specific)* | YES | YES | NO | NO | NO | NO | N/A |
| Modify Planting<br>*(Customer Specific)* | YES | YES | YES | YES | NO | NO | N/A |
| Cancel<br>(Can’t cancel if outlet is stopped) | YES | NO | NO | NO | YES | YES | NO |
| Stop | NO | NO | NO | NO | NO | NO | NO |
| DELIVERED / CANCELLED | Modify Start | NO | NO | NO | NO | N/A | N/A | N/A |
| Modify End | NO | NO | NO | NO | N/A | N/A | N/A |
| Modify Flow | NO | NO | NO | NO | N/A | N/A | N/A |
| Modify Stored Water | NO | NO | NO | NO | N/A | N/A | N/A |
| Modify Planting | NO | NO | NO | NO | N/A | N/A | N/A |
| Cancel | NO | NO | NO | NO | N/A | N/A | N/A |
| Stop | NO | NO | NO | NO | N/A | N/A | N/A |
</details>

<details>
<summary>Allow irrigators to modify any of their pending orders is YES and order is not rationed</summary>

| **Status** | **Feature** | **Standard Order**<br>**TCC = YES**<br>Plan is not relevant | **Standard Order**<br>**TCC = PARTIAL**<br>Plan is not relevant | **Standard Order**<br>**TCC = NO**<br>Not in plan | **Standard Order**<br>**TCC = NO**<br>In plan or finalised | **Low Volume** | **Unsatisfied**<br>**TCC = YES** | **Unsatisfied**<br>**TCC = PARTIAL** | **Unmetered SP**<br>(IGNORE THIS - Unmetered SPs should behave in the same way as metered) |
| --- | --- | --- | --- | --- | --- | --- | --- | --- | --- |
| OPERATING | Modify start | NO | NO | NO | NO | Confirmed with MIA (Andrew P) that low volume orders are no longer required.<br>Therefore this will not be implemented in CC | NO | NO | NO |
| Modify end | YES | YES | NO | NO | NO | NO | if in a rationing plan then NO<br>If not in a rationing plan then YES |
| Modify flow | YES if multiple flows are allowed.<br>NO if only single flow | YES | NO | NO | NO | NO | N/A |
| Modify Stored Water<br>*(Customer Specific)* | YES | YES | NO | NO | NO | NO | N/A |
| Modify planting<br>*(Customer Specific)* | YES | YES | YES | YES | NO | NO | N/A |
| Cancel | NO | NO | NO | NO | YES | YES | NO |
| Stop<br>(Only TCC YES/PARTIAL with PS_STOP tag) | YES | YES ( when `Disable Emergency Stop for TCC partial orders` is disabled) | NO | NO | NO | NO | YES (TCC YES/PARTIAL)<br>NO (TCC NO) |
| PENDING | Modify start | YES | YES* | YES* | NO | NO | NO | YES for all TCC modes |
| Modify end | YES | YES* | YES* | NO | NO | NO | if in a rationing plan then NO<br>If not in a rationing plan then YES |
| Modify flow | YES | YES* | YES* | NO | NO | NO | N/A |
| Modify Stored Water<br>*(Customer Specific)* | YES* | YES* | YES* |  | NO | NO | N/A |
| Modify planting<br>*(Customer Specific)* | YES | YES* | YES* | YES | NO | NO | N/A |
| Cancel (Can’t cancel if outlet is stopped) | YES | YES* | YES* | NO | YES | YES | YES (Follow TCC rules) |
| Stop | NO | NO | NO | NO | NO | NO | NO |
| DELIVERED / CANCELLED | Modify start | NO | NO | NO | NO | N/A | N/A | NO |
| Modify end | NO | NO | NO | NO | N/A | N/A | NO |
| Modify flow | NO | NO | NO | NO | N/A | N/A | NO |
| Modify Stored Water | NO | NO | NO | NO | N/A | N/A | N/A |
| Modify planting | NO | NO | NO | NO | N/A | N/A | N/A |
| Cancel | NO | NO | NO | NO | N/A | N/A | NO |
| Stop | NO | NO | NO | NO | N/A | N/A | NO |
</details>

# Default Start Time and Order Duration Interval

> ℹ️ **Note**
> ℹ️ 
> ℹ️ *Order Duration Interval* was previously called *Order Privileges*.
> ℹ️ 
> ℹ️ See [https://rubiconwater.atlassian.net/wiki/spaces/PNC/pages/2294972417](https://rubiconwater.atlassian.net/wiki/spaces/PNC/pages/2294972417)for more details.

> ℹ️ <u>**IMPORTANT**</u>
> ℹ️ 
> ℹ️ The below rules are defined for CustomerConnect. For NetworkConnect and Site Connect, and for similar scenarios, if an order does not meet the Default Start Time and Order Duration Interval configured, a confirmation dialog is displayed (instead of an error message which is displayed for CustomerConnect).

Default Order Start Time and Order Duration Interval can be configured for outlet, area, group or system

- Default Order Start Time (when configured) can have 1 time (HHMM) or a list of times (HHMM, HHMM, HHMM)
- Order Duration Interval (when configured) can be set to YES, NO, or a block of minutes

> ℹ️ **Note**
> ℹ️ 
> ℹ️ - Modifying Flow for TCC NO allows the modification of Order Start as well. Regardless, the same rules described below are applicable
> ℹ️ - For TCC NO we can modify both Start and Finish all together. Regardless, the same rules described below are applicable

## Lodge an Order

<details>
<summary>Lodge Order Rules</summary>

|  |  |  |
| --- | --- | --- |
| **DEFAULT START TIME FOR ORDER** | **ORDER DURATION INTERVAL** | **Lodge** |
| none | none | Order Start defaults to next day at 07:00.  
User can modify the start and there is no default start or duration force on the user. |
| 1 time value | YES | Default Start Time is loaded and displayed when the service point is selected.  
User can modify the start and there is no default start or duration force on the user. |
| 1 time value | NO | Default Start Time is loaded and displayed when the service point is selected.  
Error message and order cannot be saved if the user tries to put a start time which is different from the Default Start Time.  
Each flow duration and the full order duration can only be in days. |
| 1 time value | Minutes Value | Default Start Time is loaded and displayed when the service point is selected.  
Error message and order cannot be saved if the user tries to put a start time which is different from the Default Start Time.  
Each flow duration and the full order duration can only be a multiple of minute(s) blocks specified in ORDER DURATION INTERVAL. |
| 1 time value | none / Invalid | Same as ORDER DURATION INTERVAL = YES. |
| n time value | YES | The first Default Start Time configured is loaded and displayed when the service point is selected.  
User can modify the start and there is no default start or duration force on the user. |
| n time value | NO | The first Default Start Time configured is loaded and displayed when the service point is selected.  
Error message and order cannot be saved if the user tries to put a start time which is different from the Default Start Time.  
Each flow duration and the full order duration can only be in days. |
| n time value | Minutes Value | The first Default Start Time configured is loaded and displayed when the service point is selected.  
Error message and order cannot be saved if the user tries to put a start time which is not specified for the Default Start Time.  
Each flow duration and the full order duration can only be a multiple of minute(s) blocks specified in ORDER DURATION INTERVAL. |
| n time value | none / Invalid | Same as ORDER DURATION INTERVAL = YES. |
| none | YES | Default Start Time of 07:00 is displayed when the service point is selected.  
User can modify the start and there is no default start or duration force on the user. |
| none | NO | Default Start Time of 07:00 is displayed when the service point is selected.  
Error message and order cannot be saved if the user tries to put a start time which is other than 07:00.  
Each flow duration and the full order duration can only be in days. |
| none | Minutes Value | Default Start Time of 07:00 is displayed when the service point is selected  
Error message and order cannot be saved if the user tries to put a start time other than 07:00.  
Each flow duration and the full order duration can only be a multiple of minute(s) blocks specified in ORDER DURATION INTERVAL. |
</details>

## Modify an Order

<details>
<summary>Modify Order Rules</summary>

|  |  |  |
| --- | --- | --- |
| **DEFAULT START TIME FOR ORDER** | **ORDER DURATION INTERVAL** | **Modify** |
| none | none | There is no default start or duration force on the user |
| 1 time value | YES | There is no default start or duration force on the user |
| 1 time value | NO | - Modify Start: Order Start time can only be the one specified in Default Start Time, else error message. No restriction on the Date per se.
- Modify Finish : Each flow duration and the full order duration can only be in days
- Modify Flow : Each flow duration and the full order duration can only be in days |
| 1 time value | Minutes Value | - Modify Start: Order Start time can only be the one specified in Default Start Time, else error message. No restriction on the Date per se.
- Modify Finish: Each flow duration and the full order duration can only be a multiple of minute(s) blocks specified in ORDER DURATION INTERVAL. Flow duration is counted from the order finish, backwards.
- Modify Flow: Based on the Effective Time specified, each flow duration and the full order duration can only be a multiple of minute(s) blocks specified in ORDER PRIVILEGES. Flow duration is counted from the order finish, backwards. |
| 1 time value | none / Invalid | Same as ORDER DURATION INTERVAL = YES |
| n time value | YES | There is no default start or duration force on the user |
| n time value | NO | - Modify Start: Order Start time can only be among the times specified in Default Start Time, else error message. No restriction on the Date per se.
- Modify Finish: Each flow duration and the full order duration can only be in days
- Modify Flow: Each flow duration and the full order duration can only be in days |
| n time value | Minutes Value | - Modify Start: Order Start time can only be among the times specified in Default Start Time, else error message. No restriction on the Date per se.
- Modify Finish: Each flow duration and the full order duration can only be a multiple of minute(s) blocks specified in ORDER DURATION INTERVAL. Flow duration is counted from the order finish, backwards.
- Modify Flow: Based on the Effective Time specified, each flow duration and the full order duration can only be a multiple of minute(s) blocks specified in ORDER PRIVILEGES. Flow duration is counted from the order finish, backwards. |
| n time value | none / Invalid | Same as ORDER DURATION INTERVAL = YES |
| none | YES | There is no default start or duration force on the user |
| none | NO | - Modify Start: Order Start time can only be 07:00, else error message. No restriction on the Date per se.
- Modify Finish: Each flow duration and the full order duration can only be in days.
- Modify Flow: Each flow duration and the full order duration can only be in days |
| none | Minutes Value | - Modify Start: Order Start time can only be 07:00, else error message. No restriction on the Date per se.
- Modify Finish: Each flow duration and the full order duration can only be a multiple of minute(s) blocks specified in ORDER DURATION INTERVAL. Flow duration is counted from the order finish, backwards.
- Modify Flow : Based on the Effective Time specified, each flow duration and the full order duration can only be a multiple of minute(s) blocks specified in ORDER DURATION INTERVAL. Flow duration is counted from the order finish, backwards. |
</details>

# Service Point is STOPPED

> ℹ️ **Note**
> ℹ️ 
> ℹ️ You cannot lodge orders for an outlet that is stopped

## Modify Order

<details>
<summary>Allow irrigators to modify any of their pending orders is NO</summary>

| **Status** | **Feature** | **TCC = YES** | **TCC = PARTIAL** | **TCC = NO** |
| --- | --- | --- | --- | --- |
| OPERATING | Modify start | NO | NO | NO |
| Modify end | NO | NO | NO |
| Modify flow | NO | NO | NO |
| Modify planting | NO | NO | NO |
| Cancel | NO | NO | NO |
| Stop | NO | NO | <span style="color: #97a0af">N/A</span> |
| PENDING | Modify start | NO | NO | NO |
| Modify end | NO | NO | NO |
| Modify flow | NO | NO | NO |
| Modify planting | NO | NO | NO |
| Cancel | <span style="color: #36b37e">**YES**</span> | NO | NO |
| Stop | NO | NO | <span style="color: #97a0af">N/A</span> |
</details>

<details>
<summary>Allow irrigators to modify any of their pending orders is YES</summary>


</details>

---