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 Lighting 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
The Proposer Organisations should ensure information as described in the departure overview section below is provided in support of all departure applications for Road Lighting departures.
The remaining items are generic and the Proposer Organisation should consider which are appropriate to each specific proposed Road Lighting departure and supply the appropriate information.
Departure Overview
Provide a concise summary of the departure including the nature of the departure, 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.
A statement describing specifically “what” the departure application is applying for and “why”.
For example: “This departure application is applying for a relaxation to the UL requirements of BS EN 13201 [SPECIFY PART] [Ref 6.I] along the hard shoulder for an M2 class motorway link in order to avoid having to use a 400W luminaire or a non-G6 rated 250W luminaire with a standard setback behind the barrier”.
Descriptive impact statements of proposed departure such as:
If reduced uniformity: statement describing how this will present itself and how this will affect road users and road workers.
If reduced Lave: statement describing how this will present itself and how this will affect road users and road workers.
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 Information / Justification
Provide the technical detail and justification for the departure.
This should include consideration of the interaction of the departure with other departures at the same location and the context within the wider scheme.
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 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 alternatives design 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 documentation
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 required
An options/recommendations discussion explaining why other options were rejected in favour of the proposed departure option. Where non-standard designs are proposed simply because it is cheaper, then a suitable justification should be made.
Evidence that the scheme is adopting a “minimum carbon footprint” approach, e.g. 20/20 (or 55/28) group controlled PECU, electronic control gear, midnight switch-off, central management system etc. including:
This should include evidence that the design hasn’t been over-engineered, e.g. 400W lamps used because a trivial part of an exit lane on a gyratory system couldn’t achieve Lave using 250W lamps.
Confirmation that the Lighting Class used is appropriate for the traffic volumes, e.g. if a local authority road has been over-lit to a higher class than necessary then avoid the conflict zone at the gyratory system now using the next higher C class than the local authority road. In this case a lesser C class could be used that is perhaps the same lighting level as the Local Authority road.
Comparison of the variables required to achieve compliance with requirements compared with values achieved with the departure that shows the extent to which the departure is deviating from compliant design solution, e.g. TI needs to be 10% under standard conditions but departure proposal would achieve TI = 11% which is a 10% deviation from compliant design solution.
This should include a statement explaining what the anticipated impact on the design might be once infrastructure is physically installed – e.g. where lighting columns might be placed in slightly different locations to the drawings – columns can often be two or more feet away from their designated location.
Clarity of the extents of the road and surrounding area that will be affected by this proposal – such as:
- Reduced uniformity: diagram highlighting where the uniformity will be substandard.
- Reduced Lave: diagram highlighting where the average luminance will be substandard, e.g. which lanes affected, where and over what distance etc.
A statement describing which lighting design software was used. Where available this should include the manufacturer’s statement declaring the design accuracy of software, e.g. tolerance of designed output is within ±10% of actual installed.
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.
NOTE: Benefits, impacts or risks to the wider community should be considered for Nationally Significant Infrastructure Projects.
Departures typically involve a change that affects the safety levels that would otherwise be achieved when fully compliant with requirements. Detailed risk assessments identifying the hazards to road user and road worker should include:
Probability/impact analysis with scoring and definitions for each hazard.
Justification for using qualitative analysis instead of quantitative analysis (if qualitative assessments used).
Identification of evidence sources referred to in quantitative assessments.
Numerical cost statements for each option. Subjective statements about reduced maintenance/whole life cost are usually insufficient.
Safety (road users)
With reference to an attached 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 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.