Technical Specification Ken Hickson Chairman Symology Ltd. On - - PowerPoint PPT Presentation

Synopsis of EToN 6 Technical Specification

Ken Hickson Chairman – Symology Ltd. On behalf of the EToN Developers Group

EToN 6 Topics

 Inspections  Section 81 – Defective Apparatus  Temporary Traffic Signals Applications  Permit Applications Modification Request  Section 85 – Diversionary Works  Rationalising Charge Category Codes  Forward Planning Information  Extended use of Attachments  Other Enhancements  Introduction Timetable

Web Service Inspections

 Existing Inspections kept same  Incorporated original clarifications  Attachments  Consistent mechanism agreed for

calculating sample size

S74 / S74A / Permit Inspections

 Only send inspections in support of…

 FPN / Prosecution  S74 / S74A charges

 So no “Complies with conditions” outcome

 Works Stopped  Works in progress  Works in progress – No carriageway incursion  Works Stopped – Apparatus remaining  Non-Compliant (with Conditions)

 “Works Stopped” would only be sent if Stop notice was late  Always classed as “Routine”  Optional Location (point) + Attachments

Section 81 – Defective Apparatus

 Additional Notification Type for reporting

Defective Apparatus

 Same format as “Unattributable Works”  Must be followed by a Defect Report with

a Category of “Apparatus”

 May only be sent to one promoter at a

time; may be sent to alternative promoter following a “Non-Acceptance” response

Section 81 – Defective Apparatus

 Acceptance/Non-Acceptance response is

retained as for Unattributable Works

 Acceptance response includes a promoter

works reference

 Defect resolution indicated by “Works Stop”

• n promoter works reference

 Further new notification Type for

“Completion of Non-Notifiable Phase”

Completion of Non-Notifiable Phase

 Completion Date plus standard fields only  Equivalent of Works Stop, where full life-

cycle not required (e.g. “No excavation in non-TS street”)

 Used for response to Defective Apparatus  May be used for other works phases to

rectify reported defects that do not require full cycle of notices

Temporary Traffic Signals

 Considerations / Limitations

 Inconsistent practices adopted throughout the

community

 No legal requirement on timing

 Two new transactions:

 Temporary Traffic Signal Application  Temporary Traffic Signal Application Response

 Transactions are exchanged solely between works

promoter and authority, i.e. no copy recipients

 Application responses directly cross-reference

applications (allows for the possibility of modified applications).

Design Goals

 Notice may be given at any point after the first notice

for a phase, up until Works Stopped, i.e. after:

 Forward Planning notice  Section 54 notice / PAA Application  Section 55 notice / Permit Application  Section 57 notice  Actual Start  Permit variation

 Independent of existing noticing rules  Should contain enough information for majority of

simple signal configurations without need for attachments

Temporary Traffic Signal Application

 Inherits basic data elements, e.g. works description, from

existing notifications thereby reducing re-entry of information

 Contact information

 Signal supplier  Emergency contact

 Signal Configuration

 2-way no junction  2-way with junction  Multi-way  See attached plan

 Type of signal approval sought

 For information, approval assumed  Request Approval  Request Design and Approval

Temporary Traffic Signal Application

 Signal Operating pattern

 Working Day  24 Hour  Overnight  Off peak  Multiple configurations

 500 characters free text  Attachments for plans, maps and diagrams.

Temporary Traffic Signal Response

 Response type

 Approved  Not approved

 500 characters of free text  Attachments – allows for authority to

provide traffic management plans, diagrams, maps etc.

Permit Modification Request

 Following a Modification Request, the response period for the

subsequent modified permit application will be the later of:

 the original application response period  2 days, starting from when the Modification Request is

received

 An early start agreement on the subsequent application will

not be required

 The above rules only apply if the modified application is for

the same Start/End dates as the original; otherwise it is treated as a new application, in the same way as following a refusal

 The original application will not “deem” under any

circumstances, once a Modification Request is sent

Permit Modification Request Regulatory Considerations

 Regulation 16(3)

 “If a Permit Authority does not grant or refuse a

duly completed application within the applicable time limit the application shall be deemed”

 Approach

 Where the Primary Notice Authority gives a

Modification Request in response to an application or variation then this shall be considered a refusal in accordance with Regulation 16 (3) if a modified application is not subsequently submitted by the promoter within the required timeframe

Permit Modification Request Overview of changes to EToN

 New notice

 “Modification Request”. Notice can be used to

respond to Permit and Variation applications. Notices are sent to the works promoter and all copy recipients.

 Changes to existing notices

 “Refuse Permit / PAA / Variation”

 Data Elements

 Conditions (complete replacement if supplied)  Attachments

Section 85 – Diversionary Works

 One new Notification Type  Same format as “Restriction in Force”  Can be raised by Highway, Transport or

Bridge Authority

 Specifies the Expected Start date of the

planned major works

 Sent up to 5/10 years in advance of works

Section 85 – Diversionary Works

 May be cancelled if works not proceeding  Updated notice may be sent if details change  Section 85 Condition expires on the date

specified on the latest notice

 “GetRestrictions” transaction response now

includes both S58 Restrictions and S85 Diversionary Works

 Street Authority for USRN lists all authority

restrictions in response to “GetRestrictions”

Existing Charge Categories

Works involving excavation (single promoter) Works involving excavation (collaborative working, primary promoter) Works in footpath or bridleway Works in a highway in relation to which a pedestrian planning order is in place Works in a highway whose use by vehicular traffic is prohibited by a traffic order (that applies at all times) Laying apparatus only (collaborative works, secondary promoter) Works for road purposes carried out on behalf of a highway authority Replacing poles, lamps, columns or signs in the same location Pole testing Repairing, resetting or replacing manhole or chamber covers or frames Works in non-traffic-sensitive streets that require opening of the highway, but not breaking it up Other works not involving excavation

New Collaboration Type Code

Works involving no collaboration Works involving excavation (collaborative working, primary promoter) Laying apparatus only (collaborative works, secondary promoter) Works involving other collaboration The last item is a new code to identify works other than trench sharing, which involve collaboration

New Excavation Type Code

Replacing poles, lamps, columns or signs in the same location Pole testing Repairing, resetting or replacing manhole or chamber covers or frames Other works not involving excavation Culvert/Ditch/Tunnel work – no excavation Open Cut/Machine Cut Road Breaker Minimum Dig/Thrust Boring Slab Working Other works involving excavation The codes in red are new codes to assist in providing the data required for permit applications

New Street Category Code

Works in footpath or bridleway Works in a highway in relation to which a pedestrian planning

• rder is in place

Works in a highway whose use by vehicular traffic is prohibited by a traffic order (that applies at all times) Ideally, this data would be on the gazetteer/ASD, but the code was retained, because it was thought unlikely that the data would be provided

• n the gazetteer in time.

Clarification of Rules

 Works for Road Purposes must always be

notified against a Highway Authority OD

 Collaboration Type and Excavation Type

codes are related to individual phases

 A “No Excavation” phase can be followed

by an “Excavation” phase

 An “Excavation” phase can be followed by

a “No Excavation” phase

Clarification of Rules

 A works closed with “No Excavation” can be

resurrected on the same reference

 A cancelled works (first or a subsequent

phase) may be resurrected on the same reference

Forward Planning

 Allowed on all Works Categories  Can only be sent 10 or more days before

statutory period

 Only valid before first ever statutory notice

for works, i.e. not on second or subsequent phase

 Dates reflects estimated duration  Must lead into works or be cancelled

Attachments

 Attachments added to:

 Works Stop  Works / FPN Comments  Directions and Permit Responses (except Grant)  Intention to Issue S50 Licence  Unattributable Works

 Added Compulsory Attachment Description  Support for .docx (Word) & .odt (OpenOffice)  Retain one year after most recent notification or

guarantee period, whichever is the later

Other Enhancements (of note)

 Flag indicating works are within a Restriction  Conditions added to Works Data Variation

 Complete replacement or no change

 Added “No carriageway incursion” Carriageway

Restriction Type

 Existing “None / signing only” becomes “Some

carriageway incursion”

 Still supply most severe for the duration of the phase

 Barhole Registration extended to cover Pole Testing

and Coring

 Removed Legacy NSG Format Specification

Introduction Timetable

 Today: Agreement on substantive issues  17 April: Draft ETS circulated to wider

audience for Impact Analysis

 20 April: Agreement on code lists, etc.  w/c 30 April: EDG “All members” meeting  4 May: EDG Release Final ETS  1 June: Release XML Schema  April 2013: Go live