SRWR Guidance Note. Traffic Signals Application and Approval

Transcription

1 INTEGRATION INNOVATION INTEGRITY Introduction SRWR Guidance te Traffic Signals Application and Approval RAUC(S) Advice te 8 details the procedures that must be followed when requesting approval to use portable traffic signals. The request and approval procedures are incorporated into the SRWR. This provides seamless management of the process within the existing framework that undertakers and roads authorities currently use. Using the SRWR for this purpose has many benefits for both promoter and roads authority: Automated transfer of application and response data between promoter and authority. Prompting lists to follow through the application. Standardised approach for all applications. Linking the traffic signals application information to the related works Providing a guaranteed audit trail, which is instantly accessible and retrievable. Even if Traffic Signals Applications are dealt with by a different section of the Roads Authority, this should not be considered a reason for not having them submitted within the SRWR. The user that reviews the incoming tices Awaiting Assessment can simply use the function Produce Report to produce a printed application in Advice te 8 format and forward it to the relevant person to review. In this way, the benefits of using the SRWR can still be retained. Requirement for Requesting Permission The flow diagram on page 3 of Advice te 8 (also included at the end of this document) details the first decision required from the undertaker: [Do] works require portable traffic signals?. This is not a decision that can be automated in the SRWR, although some assistance is provided where possible. The promoter needs to review the necessary rules and determine if a request is required. Likewise, the receiving roads authority needs to review whether or not they believe a request is required. To assist the promoter and the roads authority in this decision process, when the promoter has selected Traffic Signals as the Traffic Management Type, the system triggers one of two messages. The message triggered depends on whether a request has been supplied in the update: Approval may be required for traffic signals. Request has not been supplied Approval may be required for traffic signals. Request has been supplied For the first of these messages, the user is prompted to either (i) ignore the warning; or (ii) update the works before re-submitting the update. If they elect to ignore the warning, this is logged against the update. If the second message is triggered then this is simply logged against the update. The logged messages can be viewed in the usual places (tices Awaiting Assessment screen, Works Reference Event History, Message Audit Trail etc.). Furthermore, a warning is produced if the street on which traffic signals are planned also has a Special Designation indicating a railway level crossing. This message is to prompt particular care in the planning of the traffic controls. Insight 3.6 Page - 1 vember 2014

2 Submission of Application Once it has been determined that approval or notification may be required for traffic signals, an application may be generated in the SRWR. This should be done within the agreed timeframes. To provide a fully integrated process that most benefits both parties in their coordination and planning duties, the request is associated with the relevant works reference. The request forms an additional group item that is supplied when submitting the initial notice (section 113, section 114 or section 116). This process is similar to the current method for supplying agreements or works contacts. The Works Create Screen, with the Traffic Signals button The Traffic Signals button is available (shown beneath the Agreements button on the right). This option is also available when updating a works or creating a new works phase. Selecting the button displays a pop-up window: Insight 3.6 Page - 2 vember 2014

3 The overlay window for recording Traffic Signals applications The Traffic Signal Design combo-box has the values: t Required A traffic signal design is not required Supplied Approval is requested for traffic signal and a design has been supplied as an Additional Object. Requested Approval is requested for traffic signals and also a traffic signal design is required from the roads authority. The Proposed Signal Operation combo-box has the values: Working day 24 Hours Night Off-peak Both these fields appear blank initially both Traffic Signal Design and Proposed Signal Operation must be supplied for a Traffic Signal request. If Road Junction Between Signal Heads is ticked, Traffic Signal Design must be set to either Supplied or Requested. The text box provides for 500 characters of free-text and is optional. The Remove Request button blanks out any information that may have previously been provided for the works. If the Cancel button is pressed then any changes made to the screen will be lost. tice Period Checks New validation messages check that sufficient notice period has been given for Traffic Signal requests. These checks do not replace the regular notice period checks for the statutory NRSWA notices, nor do they replace the Mandatory/Plans Required period checks. The messages do not cause the notice to appear on the Late tices Enquiry. For planned works, the required notice period is 7 days, unless Traffic Signal Design is set to Requested, in which case 2 weeks notice is needed. For Emergency, Urgent, Special Urgent or Remedial Dangerous works. the request must be within 2 hours of the works start date Insight 3.6 Page - 3 vember 2014

4 Contacts and Correspondents The standard Correspondent entry screen allows insertion of up to four telephone numbers per correspondent. For each telephone number it is possible to specify the type of number. For example, that it is an Out of Hours number (as is required for emergency contact, according to the Advice te). In order to apply for Traffic Signals, ORIGINATOR, CONTRACTOR and TRAFFIC SIGNAL SUPPLIER contacts must all be supplied. As with other contact types, the latter can be specified against operational districts and then assigned to works as they are created/updated. The presence of contact information is further validated when the main update is confirmed from main screen. Assessment and Reporting The assessment and reporting features of Insight identify works with Traffic Signal requests. tices Awaiting Assessment The tices Awaiting Assessment may be used to show the existence of associated Traffic Signals applications. Using Highlighting Expert it is possible to display these rows in a userdefined colour. For example: Using colour to highlight notices for assessment that include Traffic Signal applications Insight 3.6 Page - 4 vember 2014

5 Reference Summary Screen Works A Traffic Signals button exists on the Works Summary screen to allow access to the Traffic Signals application details. User-Defined Grid Layouts The overlay window to display Traffic Signal application details The following fields exist as options for the user-defined grid layouts: Traffic Signals Checkbox (set if Traffic Signal Request exists for the current phase). Traffic Signal Design Text field (e.g. Requested, Supplied ) Junction Between Signal Heads Checkbox Proposed Signal Operation Text field (e.g. Working Day, 24 Hours ) Information is displayed from the current works phase only. Updating a Request A Traffic Signal request that is included at Works Create time will be sent with the initial notice. Adding, removing or updating a Traffic Signal Request on an existing works causes an Error Correction notice to be produced, unless other changes are also made at the same time, which necessitate another type of notice to be produced (e.g. a subsequent 7 day tice). A message is logged against the notice and on the Messages Audit trail: Insight 3.6 Page - 5 vember 2014

6 Responding to a Request The Roads Authority responds to a request by selecting Traffic Signal Response from the Functions menu. This sends a response notice. The function is available for the Roads Authority when viewing a works that has a Traffic Signal request for the current works phase, and displays: The mandatory Response Type field will display the following new notice type values: TRAFFIC SIGNAL APPROVAL If a design was supplied then this means the design is also approved. TRAFFIC SIGNAL APPROVAL WITH DESIGN Approval for portable traffic signals with roads authority produced design. TRAFFIC SIGNAL DESIGN/INFO REQUIRED Further information required (such as a portable traffic signal design). TRAFFIC SIGNAL REFUSED Refusal of requested design, with text to define the actions required. TRAFFIC SIGNAL APPROVAL NOT REQUIRED Approval is not required for portable traffic signal for this works (as is generally the case for a simple two-way configuration with no road junction). The tice Text field is mandatory for Traffic Signal Refused and optional for the other notice types. This free-text field can also make use of standard user-defined tice Text. When the update is successful, a notice record is generated. This is prominently displayed on the Works Summary screen as the Latest Authority tice. The promoter can review received Traffic Signal Responses from the tices Awaiting Assessment screen (with optional highlighting using the Highlighting Expert). Traffic Signal Plans Plans can be added by the promoter or a roads authority. These plans are uploaded using the existing Additional Objects feature from within the SRWR portal. These can then be assigned to a works from the Objects tab when viewing the works reference details. Both the promoter and the applicable roads authority can add their own entries or amend those that are already present. An event history line is created for all added, deleted or updated fields or objects. Insight 3.6 Page - 6 vember 2014

7 SRWR Process Flow Undertaker Roads Authority Start Assess application - Including any supplied plans. Create works as normal Works may require portable traffic signals? Create/update^ works with application for portable traffic signals design/info required response Is sufficient information supplied? Assess Response Is application required? Permission not required response * Approves application or states one is not required? Should application be approved? Execute Works refused response *The undertaker may elect to abandon the works (presumably to reschedule later). ^The update may be to the works details (e.g. rescheduling) or to the application itself. approval response (with design if requested) Insight 3.6 Page - 7 vember 2014