Please note that the indexing used within the DAS application form does not match the indexing within this help page.
The below provides guidance on how to complete the submission section of the departure application when the VRS template has been selected.
Submission
Guidance on the information to be provided within each section is highlighted in amber. Please review the guidance and then replace it with submission specific details – simply select all the guidance text under a heading and start typing to replace it.
Details of submission
General
CD 127 Vehicle Restraint Systems (VRS) setback departures for permanent installations require a departure against CD 127.
Key parameters
Additional information required:
- Location of departure, in terms of chainage, which carriageway, and whether the departure is on the verge, central reserve or in another position.
- A concise narrative providing the context of the scheme and the scope and extent of the work.
- A statement highlighting the current status of the VRS works (in design, on site, completed, etc.).
Departure Overview
Provide a concise summary of the departure including the nature of the departure,Clause that the applicant is departing, the reason for the departure, the key considerations and constraints, including any assumptions made.
The departure overview should also include a brief summary of the anticipated negative impacts and risks and the proposals for mitigation.
The departure overview should be approximately 200 words in length and along with the information above should provide enough information to allow the Technical Specialist to consider a provisional agreement.
A plan showing the location and full extent of the proposed departure should be attached.
Additional information required:
Photos of site showing 50 metres either side of the hazard. When third party information is used (e.g. mapping information, video surveys), a statement is required confirming that the information is representative of the current status.
Reason for the VRS installation, identifying the hazard(s) and justification for the hazard’s exact location.
Design drawing including potential discreet hazards within 50 metres of the proposed scheme limits, including appropriate cross sections relevant to the design/departure. Repeated hazards such as lamp columns or embankments currently unprotected do not need to be shown.
Full and detailed drawings of products / solutions proposed including manufacturer’s declarations relating to CE and/or UKCA marking, unless the subject of the departure application is to use a non-compliant system when full background information is required, including manufacturer’s written support.
Secondary Standard
As applicable, information should be provided where the departure results in a design that does not satisfy other interdependent requirements.
Linking Departures
Associated, Repeat / Similar Departures and Relaxations
Associated, similar or repeated departures should be provided in the above section which has relevance to the departure application. The knowledge or lessons learned taken from the previous departure should be included as well as previous comments and conditions provided by SES specialists. It should be noted that the existence of a previously approved application should not be used as the justification for the current application and does not guarantee acceptance.
This has been an enhanced addition to the tool and will only be linking to departures available to the supply chain based on specific permissions. That way users can identify and recognise best practice and engage with previous records to guide and support the overall process.
Currently the drop-down menu for this field has been designed for the following three categories:
- Associated i.e., determined departures or otherwise, with the same PIN, as in the departure being applied for, where the departure is in the same or adjacent locations that have a cumulative effect.
- Similar i.e., these are only determined departures (not confidential) on any PINS (schemes) on DAS.
- Repeated i.e., these are only determined departures with the same PIN as in the departure being applied for.
Technical description
Provide comprehensive technical and contextual information to justify the departure and aid the technical appraisal of the proposal.
Stakeholder consultations
List the stakeholders, including VRS manufacturers, who have been consulted in the preparation of the departure and provide any observations, comments or concerns raised. National Highways’ objective is to work with “neighbours”; please ensure that owners of neighbouring highways assets are involved where appropriate.
Alternative options rejected
List any alternative design and product options that were considered in the preparation of the departure application and the reasons for rejection.
The number of alternatives normally to be considered should be agreed with the Project Manager.
Supporting information
Supporting information should only be included where it is relevant and specifically referenced using the indexed number in line with the automated attachments side pane.
Extracts should be included within the relevant section within the departure submission.
Additional information
Additional information required:
Clear statement outlining what the departure is for, and why it cannot be avoided.
Reason for the VRS installation, identifying the hazard(s) and justification for the hazard’s exact location.
Road Restraints Risk Assessment Process (RRRAP) summary (or detailed output, where applicable) including commentary on results.
GG104 risk assessment.
Correspondence with any other parties which could influence a decision to approve/reject the departure application (e.g. Local Road Authorities and/or Rail Authorities). For Departures related to Major Project schemes, this is likely to include the Operations Directorate within National Highways.
The following details should be provided when applicable:
- Speed limit (mph) and anticipated speed if less than the speed limit. This could include the result of speed surveys.
- Traffic Flow. This could include the results of traffic flow surveys.
- Category of Vehicle Restraint Systems proposed (e.g. safety barrier, terminal, transition, parapet, crash cushion, other)
- Proposed Containment Level Class, Normalised Vehicle Intrusion Class, Impact severity Level, Normalised Working Width Class and/or normalised Working Width Value, length (where relevant to the submission) and any other performance criteria pertaining to the specific VRS.
- Minimum installation length of safety barrier, as defined by the manufacturer (where relevant to the application).
- Minimum length of safety barrier required to achieve full containment, as defined by the manufacturer (where relevant to the application).
- Setback and clearance (proposed and standard).
- A statement that Stopping Sight Distance is/is not to requirements
- Cross-section with full dimensional information
- Layout plans and detailed plans with full dimensional information.
- Specific clauses/paragraphs from the requirements and advice document(s) which are being departed from i.e. not just the document reference number
- Incident statistics for the location of the departure for the past 5 years, as a minimum
- Assumptions made and implications if the assumption(s) do not materialise (risk)
- Correspondence with/agreement from VRS manufacturers, where appropriate
Any additional information that the designer considers is necessary to support the case for the departure.
Remember that if the VRS is on a two-way road, VRS should be provided to both sides of the hazard. This applies also at parapet ends. It also applies on major roads where contraflow may occur.
Benefits
Benefits, Impacts & Risks
Provide a summary of all of the benefits, impacts and risks, when compared to a design fully in accordance with requirements; identified and assessed as part of the departure assessment process, including any mitigation proposed as part of the design. This summary should be broken down into the areas of consideration listed below.
Each section should include justification of why:
The benefits outweigh the negative impacts
The risks, after mitigation, are as low as reasonably practicable.
Where relevant, supporting documentation such as drawings, plans and technical notes should be attached. The parts of the documents that relate to each of the areas below should be clearly referenced.
Any benefits, impacts or risks that relate to the proposer or an associated party (e.g. cost savings to the developer in the case of a Section 278 scheme) but do not impact National Highways, its road users or the wider community should be ignored.
Benefits, impacts or risks to the wider community should be considered for Nationally Significant Infrastructure Projects.
Safety (road users)
With reference to an attached mandatory GG 104 risk assessment, summarise the safety impact of the departure on road users and other parties. Give details of how the safety risk on customers compares to the baseline of a fully compliant design.
Safety (construction, maintenance, operation and disposal)
With reference to an attached mandatory GG 104 risk assessment, summarise the safety impact of the departure on workers during construction, maintenance (including inspections), operation and disposal of the proposed design. Give details of how the safety risk on workers compares to the baseline of a fully compliant design. Consideration should be given to all legal requirements, including CDM regulations.
Technical
Summarise the technical impact associated with the departure following the incorporation of any mitigating measures. Give details of how the residual risks and impacts compare to a design fully complaint with the requirements.
Programme
Summarise the effect of the departure on the project’s critical path and the future risks to the programme arising from the incorporation of the departure into the design. This should include both design and construction programme considerations.
Budget
Summarise the effect of the departure on the project’s budget and the future risks to the budget arising from the incorporation of the departure into the design. This should consider design, construction, maintenance and operation.
Carbon net zero
Summarise how the departure will support, if not improve, the decarbonisation obligations of the requirement being departed from.
Environmental
Summarise the effect of the departure on all relevant environmental issues following the incorporation of any mitigating measures.
Innovation
Where the departure relates to the use of a novel technology or method the risks associated with the innovative aspects of the departure.
Durability / Maintenance
Consider the implications of the departure for future maintenance and inspection of the element under consideration and for other elements of the scheme affected by the departure. Also consider the impact of the departure on the maintenance and inspection of other aspects of the scheme.
Network Availability
Consider the impacts of the departure on network availability during construction, maintenance, inspection and normal use.
Mitigation
Provide information about any specific mitigation that is proposed as part of the design solution to reduce any associated risk with the departure.
An explanation of why the mitigation is being proposed and how it reduces any associated risk with the departure should be included.
Risks after Mitigation are As Low As Reasonably Practicable
An explanation why the level of residual risk is as low as reasonably practicable should be provided.
Overall Justification
Provide a final summary outlining the overarching benefit of the proposed departure when compared to a compliant scheme.