EasyWay and Key Performance Indicators

Transcription

1 EasyWay and Key Performance Indicators J.W. Tierolf Geneva 11 December

2 Overview Types of KPI EasyWay Introduction Status Core Services LoS Use of KPI s Today Future 2

3 KPI for what/whom? KPI s can be chosen regarding: Goals Project performance Service performance Policy goals Target Groups Professionals End-Users Decision makers Level High/Low level Define for whom and for what goals you ll have KPI s 3

4 EasyWay Road Authorities deploying ITS Harmonised ITS DEPLOYMENT (TEN-T, other networks) 150 public & private RAs 1000 Mln. ITS deployed % EC support 8 Euro-Regions (deployment) Horizontal support activities EasyWay 1 & 2: EasyWay 3, EIP: Nov 13 Feb 15 EasyWay 4 proposals: Jan 13 Dec 15 EasyWay N: 14 X Policy Goals till 2020: 25% better safety 25% less congestion 10% reduction of environmental impact. 4

5 KPI Considerations: EasyWay and EC EC wanted reporting of nr. of systems and milestones Already in 94 # of monitoring loops /km etc. Telten stressed to use operating environments and service performance instead EasyWay defined: Core services (CS) Operating environments (OE) Quality/Level-of-Service per CS and OE EasyWay reported: Deployment of CS (# kms with Q-level per OE) Performance re policy goals Safety (%reduction # acciddents, # casualties) Mobility (% reduction congestion) Environment (% reduction CO2) 5

6 Measuring EasyWay Performance (1) KPI s for Deployment Deployment of services rather than equipment Chain: Core Service, with LoS/Quality Level, defined per OE Mapped on EasyMap (open and interactive) KPI - e.g. kms of road serviced, LoS - e.g. low, medium, high level Typical KPI: # kms of road serviced by CS x of LoS medium as defined for OE y 6

7 Measuring EasyWay Performance (2) KPI s for Policy goals Policy Goals EW % better safety 25% less congestion 10% reduction of environmental impact. Evaluation results of ITS deployments related to the policy goals were used and extrapolated to the # of kms where they had been deployed So derived, EW 1 and 2 were on target for : Safety 10%, Congestion 10%, Environment 4 % 7

8 Core and Sub-services Overview (1) EW 1 - Traveller Information Services Traveller information services (TIS-DG01) Forecast and real time event information (TIS-DG02) Traffic condition information services (TIS-DG03) Speed limit information services (TIS-DG04) Travel time information services (TIS-DG05) Weather information services (TIS-DG06) Co-modal traveller information (TIS-DG07) EW 2 - Traffic Management Services Dynamic lane management (TMS-DG01) Speed control (TMS-DG02) Ramp metering (TMS-DG03) Incident warning (TMS-DG05) HGV overtaking ban (TMS-DG06) Traffic management on corridors (TMS-DG07) Incident management (TMS-DG08)

9 Core- and Sub-Services Overview (2) EW 3 - Freight & Logistics Services - Intelligent Truck Parking (FLS-DG01) - Access to abnormal and dangerous good transport regulations (FLS-DG02) EW 4 VMS - Variable Message Signs (VMS LS-DG01) EW 5 DATEX - DATEX (DAT-DG01) EW 6 Connected ICT Infrastructure - Operating Environments (Supporting action, not a deployment guideline) - Cooperative systems (TaskForce, not a deployment guideline) For each Core Service a Deployment Guideline (DG) was developed and agreed. The 2012 version is the latest consolidated set (DG12 set) More information on the EW deployment guidelines:

10 Deployment Guidelines the DG2012 Set of Documents 10

11 EasyWay Operating Environments The Need for and Impact of a ITS service depends on the Operating Environment Criteria Flow Weather Safety Road Type OE Types # C- Blackspot 1 T- Motorways 4 R- Multilane Roads 8 S- Motorway Network 2 N- Road Network 2 P- Ringroads/Urban access Rds 1 11

12 EasyWay Operating Environments C1 critical or black spots, local flow-related traffic impact and/or safety concerns T1 motorway ( link), no flow-related traffic impact and no major safety concerns T2 motorway (link), no flow-related traffic impact, safety concerns T3 motorway (link), daily flow-related traffic impact, no major safety concerns T4 motorway (link), daily flow-related traffic impact, safety concerns R1 two-lane road (link), no flow-related impact, no major safety concerns R2 two-lane road (link), no flow-related traffic impact, safety concerns R3 two-lane road (link), seasonal or daily flow-related traffic impact, no major safety concerns R4 two-lane road (link), seasonal or daily flow-related traffic impact, safety concerns R5 three-/four-lane road (link), no flow related traffic impact, no major safety concerns R6 three-/four-lane road (link), no flow related traffic impact, safety concerns R7 three-/four-lane road (link), seasonal or daily flow related traffic impact, no major safety concerns R8 three-/four-lane road (link), seasonal or daily flow related traffic impact, safety concerns S1 motorway corridor or network, seasonal flow-related impact, possibly safety concerns S2 motorway corridor or network, daily flow-related traffic impact, possibly safety concerns N1 road corridor or network, seasonal flow-related traffic impact, possibly safety concerns N2 road corridor or network, daily flow-related traffic impact. possibly safety concerns P1 peri-urban motorway or road interfacing urban environment, possibly safety concerns 12

13 Operating Environments, Roads Classification - Example 13

14 LoS Requirements TCM - Example Example of LoS for Traffic Management along a Corridor or Network, TCM Low Level Coverage: Critical spots coverage Availability (time): Service periodically operated during critical periods Availability (system): One single(pre-defined) system available Consistency: Consistent local road user advice along routes Level of Coordination: Knowledge and scenario sharing between included operators Medium Level Coverage: Spatial expansion of the service, linkages Availability (time): Extended availability Availability (system): Diverse systems Consistency: Consistent local road user advices along routes Level of Coordination: Cross-border scenario consistency, DATEX connected 14

15 LoS Corridor TM - Example 15

16 EasyWay Today - EIP EIP, the European ITS (deployment) Platform November 2013 Febr 2015 Horizontal Project providing frameworks for ITS deployment Activities Deployment Guidelines use and maintenance ITS Specifications input European single Point of Access guidelines Quality Requirements for RTTI (ITS specs b, c) DATEX and Mare Nostrum (VMS) Urban Interface, 1st framework 16

17 EasyWay Future 11 December 2013 TEN-T call proposals January 2013 December 2015 Deployment of ITS services along corridors Additional horizontal activities and frameworks A.o. evolve ITS KPI s with other stakeholders CEF, Horizon2020, other Further deployment of ITS services Feasibility studies for new ITS Horizontal support actions 17

18 EasyWay 3 and KPI s Corridors report KPI s and evaluations to EIP KPI definition task Define better KPI s For project performance For policy performance With IRF Share/Agree with other stakeholders Other inputs Stockholm Group (e-tolling) KPI concept Other 18