Confirm interface with Street Manager / Field Mappings |
Street Manager treats PAAs and Permits both as "Permits". The Street Manager Work Category indicates whether a "Permit" is a PAA or a Permit Application.
Changes are not permitted to PAAs, the previous PAA must be cancelled and a new PAA submitted to make any changes. Confirm will automatically cancel any outstanding PAA in Street Manager when submitting a revised PAA.
Under EToN, major works that were not Asset Activity (e.g. Remedial or Interim to Permanent) did not require a PAA, but in Street Manager a PAA is required. Conversely, at the moment Street Manager does not allow a PAA to be created if a previous permit exists on the works. The latter is acknowledged as a bug with Street Manager plan to address, but in the meantime Confirm will behave as follows:
Changes to Permit applications (Modified Applications, Works Data Variations and Duration Variation Applications) are referred to as Permit Changes or Change requests.
Street Manager uses the National Condition Types for Permit Conditions rather than the high-level condition "groupings" that were used by EToN. SQL is provided to add these extra Condition Types in Confirm. Each Condition Type will have a DfT Ref. set to the appropriate EToN value to allow you transition to the new Condition Types while still using EToN.
The old Condition Types in Confirm will be flagged as dead so that they don't clutter up the Permit Application process, with the exception of Condition Types 3 (Out of hours work) and 13 (Local) for which there are no Street Manager equivalent conditions. These latter condition types can be flagged as dead once EToN is no longer valid.
Note that the Permit Condition Type lookup management screen in Confirm does not currently cope with multiple conditions having the same DfT Ref, so until a Confirm desktop upgrade is available any additional changes to Condition Types will need to be made via SQL. Please contact the Confirm support team for assistance with this if required.
Once a Permit has been granted, Street Manager only allows one change (variation) to be processed at a time, however EToN allows multiple variations to be submitted with a Grant / Refuse covering all previous changes. This means that if you apply for a Variation from Confirm and then attempt to apply for another Variation before the first has been Granted, Refused or Deemed, then the second Variation will be rejected by Street Manager. The Street Manager Agent to "look ahead" whenever it is processing a Variation and if there are subsequent Variations to be processed submit them all to Street Manager as a single change.
For works in progress, EToN uses Works Data Variations for all changes other than duration and a Duration Variation Application to change the duration. In Street Manager a single permit change can change all aspects of the works. Therefore, when importing changes into Confirm that change both the duration of the works and other data (e.g. traffic management) we will create two notices in Confirm, a Works Data Variation and a Duration Variation Application.
Street Manager does not currently support Error Correction notices which are used to make corrections after the works has completed. (TBA) we could support exporting Error Corrections from Confirm by Reverting the Works Stop, issuing a Works Data Variation and re-issuing the Works Stop.
Street Manager Field | Confirm Field | Notes (When importing into Confirm from Street Manager) | Notes (When exporting from Confirm to Street Manager) |
---|---|---|---|
Works reference number | Street Works > Reference | ||
Permit reference | Not applicable | Ignored | |
Works area (View on Map) | Street Works > Map > Easting / Northing | Note these aren't mandatory in Confirm but Street Manager will reject the notification so this will have to be corrected and re-sent if not initially supplied | |
USRN | Site > Code | If only 7 digits then will attempt a match with and without a leading zero. |
Leading zeros will be stripped. If street is not found in Street Manager then notification won't be sent. |
Primary Notice Authority (Works apply to) | Street Works > Street Auth |
Will search for interests with type of "Highway Authority" or "Permit Authority" that has an Organisation with an External Ref 1 equal to the SWA code of the Primary Notice Authority. Priority will be given to Permit Authority interests. If no matches found will use the first live Organisation with a Highway/Permit Authority Interest, sorting by Organisation Name. See below for Private Streets. |
External Ref 1 from the Street Auth Organisation |
Road type | Street Works > Street Auth | If the Road type in Street Manager is "Private Street - No definition information held by Street Authority" then Confirm will prioritise Private Street Interests when determining the Street Authority from the Street Interests | Will be set to "Private Street - No definition information held by Street Authority" if the Street Authority is a Private Street Manager. Otherwise will default from the USRN. |
Interested Parties | Street Works > Contacts > Recipients | Will be coped from the USRN as these are not supplied by the Street Manager API | Not supplied - derived automatically by Street Manager |
Designations impacted by works | Street Works > Location > Designations | All the distinct designation types returned from Street Manager are pulled. The full details of the designation, e.g. location, are ignored | These are retrieved from Street Manager API for the USRN and compared with the street designation types from Confirm. Only the applicable designations are pushed. |
Location area | Street Works > Location | Appended to the Location text |
Extracted from the location text if supplied in brackets, e.g. a location text of "o/s 45 (Footway and verge)" would set the Footway and Verge checkboxes in Street Manager. If no suitable text is found in brackets then defaults to Carriageway. |
Location description | Street Works > Location | ||
Primary contact | Street Works > Contacts > Owner > Name | If truncated, no email will be sent. | Derived by Street Manager |
Primary contact number | Street Works > Contacts > Owner > Phone | Derived by Street Manager | |
Street Works > Contacts > Owner > Address | Populated from the Organisation Contact details stored in Confirm | Derived by Street Manager | |
Workstream | Street Works > From | Not used. Confirm Promoter Organisation is determined by matching the first 5 characters of the Works reference against DfT Ref 2 of live Organisations. | Last 3 digits of Dft Ref 2 from the Promoter Organisation |
Secondary contact | Street Works > Contacts > Agent > Name | If Agent Name not specified uses Owner name or otherwise the main contact name from the Promoter Organisation | |
Secondary contact number | Street Works > Contacts > Agent > Phone | As above if not specified | |
Secondary contact email | Street Works > Contacts > Agent > Address | Will be prepended to the Organisation's Contact contact address from Confirm | First line of the address. |
Project reference number | Street Works > Project Reference | ||
Works type | Street Works > Works Type | Not used. Work Type is derived from Works category | Set to "Immediate" if Street Work Type > Priority is Urgent, otherwise set to "Planned" |
Is a TTRO required | Street Works > Location> add text {ttro} | PAA created | Add text (ttro) in Location textbox for TTRO Application. |
Proposed start date and time | Street Works > Start Date | For immediate works, it is determined from the Actual Start Date. | |
Proposed end date and time | Street Works > Estimated End Date | ||
Reasonable period end date | Street Works > Reasonable Period | Derived. Note that Confirm displays the later of the Reasonable Period (based on the agreed duration of the works) and the Prescribed Period (2 days). Street Manager does not take the Prescribed Period into account when displaying this date so could be earlier than the date displayed in Confirm for works that take less than 2 working days. | Derived. See note on left. |
Works category | Street Works > Works Type | HS2 Highway works are imported as Major Permits | Derived by Street Manager |
Works duration | Street Works > Duration | Derived | Derived |
Early start preapproval | Street Works > Agreements | If true then Agreement with DfT Ref of 5 will be added | If Agreement present with DfT ref 5 or Agreement contact name or reference is set then True else False. |
Pre-approved by | Street Works > Agreements > Contact | ||
Pre-approval details |
Street Works > Agreements > Reference Street Works > Agreements > Date |
Invalid reference characters will be replaced with dashes "-" and may be truncated. Will also be added to Added to Street Works > Transfer > Notifice Comments Agreement Date is set to the date of the notice |
Agreement Reference and Date appended together |
Reason for requesting an early start | Does not exist | Added to Street Works > Transfer > Notifice Comments |
If the works require early start agreement but no Agreement has been specified then the Notice Comments will be used. If an early start is needed but no early start agreement or reason is supplied then this will be set to "None specified" |
Activity type | Street Works > Phase Type |
Phase Type will be set as appropriate for the following activity types: Permanent reinstatement Remedial works Core sampling And will be set to "Asset Activity" for all others. |
If the Phase Type in Confirm is "Asset Activity" then the Promoter Organisation's Interest will be examined. If the Interest Name contains the exact wording of one of the Activity Type options in Street Manager we will use this Activity Type. If not, then if the Promoter Organisation Interest DfT reference is "Highway Authority (Works Promoter)" then "Highways Improvement Works" will be used, otherwise “Utility Asset Works” will be used. If the Phase Type is not "Asset Activity" then the Activity type that matches the Phase Type will be used. |
Description of work | Street Works > Description | ||
Excavation required | Street Works > Excavation Type |
Excavation Type with Dft Ref of 18 if the received value is True. Otherwise Excavation Type with Dft Ref of 12. Note that Works Data Variations do not allow Excavation Type to be updated while works are in progress but if the change is agreed this will be picked up on Works Stop import. |
Set to True if Excavation Type Dft Ref is between 14-18 else set to False. |
Was an excavation carried out? | Street Works > Excavation Type | If this has been changed to "No" in Street Manager then the Excavation Type in Confirm will be updated using the above rules on receipt of the Works Stop |
Will be set to "No" on export of the Works Stop if the Excavation Type changes from a "with excavation" type to a "no excavation" type. Note this cannot be changed from "No" to "Yes" - to do this a change must be requested via Street Manager |
Required traffic management type | Street Works > Traffic Man. | ||
Footway closure |
Street Works > Footway Closure Street Works > Description |
Set if either of the "Yes" options are supplied. The specific option details will also be appended to the Works Description |
If the Confirm Footway Closure option is not selected then the Street Manager option will be set to "No". If the Confirm option is set as Yes,pedestrian walkway will be provided then the Street Manager option will be set to "Yes, pedestrian walkway will be provided". Otherwise it will be set to "Yes,alternative route will be provided" |
Is lane rental applicable | Does not exist | Ignored | Set to false |
Is traffic management plan required | Does not exist | Ignored | Set to false |
Attached traffic management plan | Street Works > Document Links | TBA Add as a document link. Description prefixed with Traffic Management Plan and Permit Id. Document Location is URL to Street Manager file | Not supplied. Documents are uploaded separately |
Notifying environmental health | Street Works > Outside Working Hours | ||
Is collaborative involved | Street Works > Collaboration | "Sharing traffic management only" is mapped to "Works involving other collaboration" | |
Collaboration details | Does not exist | Added to Street Works > Transfer > Notice comments | Set to name of collaboration type |
Works reference number of collaborative works | Does not exist | Added to Street Works > Transfer > Notice comments | Not set |
Conditions | Street Works > Conditions | Will be mapped to Confirm Condition Types based on matching the NCT condition code to the first 6 characters of the Permit Condition Type Name. Mandatory conditions NCT01a, NCT01b and NCT11a are ignored |
Will send all conditions where the first 6 characters of the condition name match one of the allowed values in Street Manager. SQL is provided to add these. Note that mandatory conditions are not needed. |
Condition Comments | Street Works > Conditions Text |
Concatenated together. May be truncated. The text from each condition will be on a new line prefixed by the corresponding NCT code. |
Added to the Comments of the first non-mandatory condition. If a fragment of Condition text in Confirm begins with a valid NCT code then everything after the code will be attached to the relevant Condition in Street Manager. |
Additional permit details |
Street Works > Transfer > Notice Comments Street Works > Agreements (Export) |
If Agreements other than early start are specified then details of these agreements will be appended to the Additional permit details. | |
Additional files | Street Works > Document links | Street Manager documents will be added as URLs to Confirm | |
Reason for changes (only on change requests) |
Street Works > Transfer > Notice Comments Street Works > Agreements (Export) |
Will be the first line of the Notification Comments where other fields are also added to Notification Comments |
If Agreements other than early start are specified then details of these agreements will be appended to the Reason for changes. Will default to "None specified" if blank. |