Grant / Refuse / Modification Request

Key Differences from EToN

Street Manager introduces Refusal reasons. We will map these onto Notice Types that have a DfT Reference "Refuse PAA/Permit/Variation" that contain the Reason for refusal code in the Notice Type name.

Modification Requests from Street Manager do not currently allow revised Permit Conditions to be proposed. When sending Modification Requests from Confirm we will combine all of the proposed Condition changes into a single text field.

EToN allows a Grant to be issued even after a Permit Application is Deemed, but Street Manager does not allow Grant to be issued for a Deemed application.

In EToN a Grant, Refuse or Modification Request (Permit decision) applies to all of the Applications, Modifications or Variations received up until that point, whereas in Street Manager a decision is recorded against the specific Permit or Change. When exporting a Permit decision to Street Manager, Confirm will only apply the decision to Permits or Changes that had already been downloaded into Confirm at the time the Permit decision was logged in Confirm (to avoid Granting something that the Confirm user hasn't seen yet).

Another complex scenario relates to how Street Manager deals with proposed changes to permits that haven't been granted yet... If a Promoter submits a Permit application to Street Manager but then requests a change before the original Permit has been Granted then the change details will be incorporated into the main Permit application and effectively granted when the permit is granted. The following scenario is therefore possible:

In this scenario the permit should not be granted because the user did not see the change entered at step 3. The proposed behaviour is that the Grant will not be logged in Street Manager and will be overwritten by the Permit change from street manager (so in Confirm it will look like the Grant never happened). The user can then Grant the permit with the change in Confirm and re-send this to Street Manager.

Refusal reasons and notice types

Refusal reason codes can be specified from Confirm in two ways:

The following Notice Types will be added to map to Street Manager Reasons for refusal. All with have their Dft Ref. set to "Refuse PAA/Permit/Variation".

The existing standard "Refuse Permit / PAA / Variation" Notice type will be used to represent "RC50 - Other (General)" unless the Notification Comment includes one or more valid "RC" codes.

Street Manager may also automatically cancel a proposed change if this is not granted before the works stop. In this scenario Confirm will generate an Refusal Notice for the cancellation using a new Notice Type Code of "RCCR" - "Street Manager Cancelled Change Request".

Duration Challenges

Under EToN the Duration Challenge notice is separate from the Grant notice, whereas Street Manager combines these into a single "Grant with duration challenge" permit change decision. During import of a Grant with duration challenge into Confirm, the Street Manager Agent will create two notices in Confirm, a Grant followed by a Duration Challenge.

A new "Grant with Duration Challenge" Notice Type has been added which can be selected from the Grant wizard. If this is selected then the Confirm Street Manager agent will indefinitely prevent the Grant from being set to Street Manager until a Duration Challenge has been entered into Confirm. Note that this must be used with caution as the Permit could deem if a "Grant with Duration Challenge" notice is entered without subsequently adding the Duration Challenge. This change introduces the following two new notice types:

On export, when the Street Manager agent encounters a normal Grant notice in Confirm it will "look ahead" to see if this has been followed by a Duration Challenge, and if so will record a Grant with duration challenge in Street Manager.

If a Duration Challenge is encountered after the Grant has already been sent to Street Manager then this will not be sent and a Transfer warning will be recorded.

Field Mapping