Bridge Owners Forum

May 2008

ESDAL Stakeholder Management Team

bringing service to life

ESDAL Project - Outline

• ESDAL Project Update

• Data Elements

• Phases 2, 3 & 4

• ICA’s

• Data Updates

Project Update

Phase 1 Operational 03/03/06Phase 2 Operational 14/01/08Phase 3 Autumn 08Phase 4 Summer 09

• Data Collection168 LA’s providing data192 Total data providersTotal number of structures collected - 209597 Expected number of ESDAL structures - 116131 Total structures transformed 110592Total structures cleansed 74727

Data Elements• Essential Data

• Structure Key - Your unique identifier for the structure

• Location - A grid reference which may be OSGR format or another co-ordinate pair

• Notification Contact – details of the person to be notified with regards to abnormal loads for a given structure

• Category The type of structure - for example Road Bridge, Elevated Road, Culvert, Level Crossing, from a pre-defined list of values.

Data ElementsAdditional structure information would also be

most useful:• Structure Name - The name or identifier you use for the

structure• Alternative Names - Any other names that are used• Managing Authority - Contact details for the delegated

authority responsible for receiving abnormal load notifications

• Object Under - The road, railway or other path passing under the bridge

• Object Over - The road, railway or other path passing over the bridge

• Structure Length - The overall span of the structure – may be between bearing centrelines, deck joints or abutment faces

• Width Over - The minimum clear width between parapets

Data Elements

• Width Under - The minimum clear width between kerbs and abutments where a route passes under the structure

• Safe Vehicle Height - The maximum permissible height of a vehicle and load able to pass under the lowest part of the structure

• Gross Weight Limit - The maximum permissible gross weight of vehicle and load able to pass over the structure

• Axle Weight Limit - Maximum permissible single axle weight of vehicle and load able to pass over the structure

• Structure Description - Any additional information which might help to clarify the structure’s type or location

• HB/SV rating• Number of spans• Details of publically available heights & weights

Data Elements

• Height Envelope - The maximum permissible envelope through which a load may pass under the structure – for example, where a particular route path under the structure will allow a higher load than the specified height limit.

• Intellectual property rights for the data remain with the structure owner at all times. Any data collected by the ESDAL team will not be used for anything other than the ESDAL system without prior written permission.

Phases 2, 3 & 4

• Phases 2 & 3

– Allows Hauliers to submit applications and to notify all abnormal loads through a website.

– Detailed route identification gives clear picture of proposed route to notifiable authorities.

• Map based review of route and structures• List of affected structures• Facility to comment on proposed special order route

– Standard format for ESDAL notifications and applications– Routine alert of unread notifications by fax or email– You can filter notifications to see only notifications that affect a

given structure

Phases 2, 3 & 4

• Phase 4

– Online editing of own structure data– Constraints & restrictions– “Indicative Capacity Appraisals”– Ability to produce statistical information allowing

better management of abnormal loads and structures

• Bridge Heights

Using signed height and weight data for use of third parties to assist in reducing bridge strikes.

ICA’s

• Indicative Capacity Appraisal

– Structure owners notification will indicate whether the proposed load is suitable for individual structures

– Hauliers see an indication of whether there is a potential problem with the proposed route

– Reduction in unsuitable notifications– Appraisal methods, such as weight screening,

influence line, BD86

Data Updates

The key to ESDAL is maintaining accurate data

• Structure Data– We will send an email to the data holder asking for

data updates every six months from the date of the original provision of data.

• Contact data– We confirm contact data every three months by

sending an email to the notification contact asking them to confirm their details

Thank you for your attention

For more information, visit

www.highways.gov.uk/esdalwww.highways.gov.uk/esdal