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

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

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

# Configuring Planner Access

There are different ways to configure Planner access depending on whether you want to ensure that only one user can operate as a planner for an area or group at a time. For details see [https://rubiconwater.atlassian.net/wiki/spaces/UMNC/pages/2659287156](https://rubiconwater.atlassian.net/wiki/spaces/UMNC/pages/2659287156) 

In summary:

- Planners who have the planner role on a specific area or group will **always** have full planner access for that area or group in both DMS and NetworkConnect. They will be able to view, create, and manage plans for that area or group and they do not need to log into the area or group in DMS before logging into NetworkConnect.
- If the Planner role has ALL PARTIES access to the system then any planner can log into any area or group in DMS or NetworkConnect. They will then be granted planner access to that area or group. No other planners will have planner access to that area or group in either DMS or NetworkConnect **unless** they have been configured to have individual access to the area or group.

> ℹ️ **What happens if you are already logged into a different planning area?**
> ℹ️ 
> ℹ️ If you are already logged in to a different planning area you will be prompted to log out of that area and assign an after-hours contact for the area. You will not be able to log in to a new area until you have done this.

# Auto Confirming Orders

You can configure orders to be automatically confirmed when the plan is published. To do this, set the **Auto Confirmation** attribute to *Yes*. You can set this for individual outlets on the Site Summary screen in NetworkConnect. See [Modify tag and attribute values](https://rubiconwater.atlassian.net/wiki/spaces/NC/pages/1914765569/Site+Tags+and+Attributes#Modify-tag-and-attribute-values) or you can set it for groups, areas, or the whole system in DMS or SCADAConnect Forms. See [https://rubiconwater.atlassian.net/wiki/spaces/SMNC/pages/2000979142](https://rubiconwater.atlassian.net/wiki/spaces/SMNC/pages/2000979142).

# Setting up Regulator-Outlet Relationships for Auto-Scheduling and Grouping

You can also group the Unscheduled Orders list by their shared upstream regulator. When NetworkConnect is auto-scheduling it also uses this grouping to select segments for the orders. To identify the upstream regulator you must configure PARENT_METERED relations between the objects. See [https://rubiconwater.atlassian.net/wiki/spaces/NC/pages/3032055810](https://rubiconwater.atlassian.net/wiki/spaces/NC/pages/3032055810) for more details.

# Configuring Segment Properties for Auto-Scheduling

Use the Configuration option on the Planning screen to set up the flow ranges and the linking behaviour of segments that are created by the Auto-Scheduler. 

Click the **Edit **button to edit the existing ranges or add new ranges. 

> ℹ️ **Note**
> ℹ️ 
> ℹ️ Flow ranges must not overlap. You will not be able to save an overlapping range.

# Restricting Orders outside the Plan Range

By default a new plan will include all unscheduled orders for the area/group except those that start after the end of the plan range.

You can exclude orders from a plan that do not overlap with the plan range by setting the **Exclude Orders before Plan Range** parameter to *Yes*. 

# Configuring Publishing with Over-Capacity Regulators

By default you can’t publish a plan that includes over-capacity regulators. You can change this behaviour by setting the **Plan Finalise if Over Capacity** parameter to *Yes*. In this case you’ll still receive a warning listing the over-capacity regulators but you’ll be able to go ahead and publish the plan anyway.