Austroads Webinar Techniques for Incident Management to ... · Techniques for Incident Management...

Techniques for Incident Management to Support Network Operations Planning29 August 2017

Today’s moderator

Eliz EstebanCommunications OfficerAustroads

P: +61 2 8265 3302E: eesteban@austroads.com.au

About Austroads

The peak organisation of Australasian road transport and traffic agencies

• Roads and Maritime Services New South Wales

• Roads Corporation Victoria

• Department of Transport and Main Roads Queensland

• Main Roads Western Australia

• Department of Planning, Transport and Infrastructure South Australia

• Department of State Growth Tasmania

• Department of Transport Northern Territory

• Transport Canberra and City Services Directorate, Australian Capital Territory

• Commonwealth Department of Infrastructure and Regional Development

• Australian Local Government Association

• New Zealand Transport Agency

Housekeeping

Webinar = 35 mins

Question time = 15 mins

GoToWebinar

Please type your questions here

Austroads reports

Download from Austroads Website:

https://www.onlinepublications.austroads.com.au/items/AP-R547-17

https://www.onlinepublications.austroads.com.au/items/AP-R304-07

Today’s presenters

Dr Aut KarndacharukSenior Research EngineerAustralian Road Research Board (ARRB)P: +64 2 9282 4405E: auttapone.karndacharuk@arrb.com.au

Asif HassanProfessional EngineerAustralian Road Research Board (ARRB)P: +64 2 9282 4413E: asif.hassan@arrb.com.au

Agenda

Topic PresenterProject Background and Introduction

Dr Aut KarndacharukTIM Techniques from Literature Review Contemporary TIM Practices in Australasia

Asif HassanTIM Principles & FrameworkQuestions and Answers Both Presenters

Project Background & IntroductionDr Aut Karndacharuk

Background and motivation See Section 1

• Background: traffic incident management (TIM) is an evolving area of road transport management because of its complexity in managing multi-agency, multi-jurisdictional response to road traffic disruptions.

• Motivation: with the emergence of ITS and other transport technologies, Austroads has identified the lack of a nationally agreed framework across the member organisations as a gap in the TIM knowledge.

Key Stakeholders

for TIM

Road Transport Agencies

Road Users

Police & Emergency

Services

Project objectives

Review of Current ANZ

Practices

Stakeholder Consultation

Identification of Leading Practices

Development of Framework and Principles

Literature Review

See Section 1

Austroads Project NS1017 See Appendix A

• TIM is a process of managing multi-agency, multi-jurisdictional response to road traffic incidents

• TIM encompasses the planning, management, operations and review of incident management activities

• The Austroads best practices report (AP-R304-07) identified a number of TIM techniques for incident detection, verification and response, traffic management and traveller information.

Traffic incident management timeline See Appendix A

TIM Techniques from Literature ReviewDr Aut Karndacharuk

Baseline TIM Techniques See Section 2.1

• Emergency phones

• In-road sensors− inductive loops− magnetometers− piezoelectric sensors

• Over-road sensors− Acoustic− Infrared − Laser-pulsed (LIDAR)− Pneumatic tubes− Radar− Ultrasonic

• Video camera system

• In-vehicle sensors

• Automatic Incident Detection (algorithm)

• Traffic incident watch (professional drivers)

• Static traffic and road space management devices (e.g. signage)

• Adaptive traffic control and communications devices (e.g. VMS and VSLS)

• Service patrol and incident response unit

Smartphones & GNSS See Section 2.2

• Location-aware mobile devices − accelerometers− gyroscopic sensors− a compass

• Versatile sensing applications− Position of the phone / user− Mode of travel− Origin-destination patterns− Road network management

• Opportunity for use of mobile phone data for TIM

C-ITS and DSRC See Section 2.2

• Cooperative-ITS (C-ITS)− vehicle-to-vehicle (V2V) & vehicle-to-infrastructure (V2I, V2X) communications

− Two key components: on-board and road-side units

• Dedicated Short Range Communications (DSRC) is a primary component of C-ITS

• Applications (esp. by locating DSRC systems at intersections)− Improved traffic operation and management

− Road & traffic conditions

− Traveller information

• Opportunity to use ITS & DSRC technology for TIM

Social media & crowdsourcing See Section 2.2

• Opportunity: utilise real-time social media to expedite the detection of a traffic incident

• Examples− Google through Waze app collect

driving data to optimise traffic routes

− Analysis of Tweeter feeds detect congestion and incident events

Drones for traffic data See Section 2.2

• Configurations:− Navigation systems

− High-resolution cameras

− High-capacity data collection links

• Application: to collect data and information on traffic movements

• Opportunity: 3D laser scanning drones to expedite incident data collection

Summary of baseline TIM techniques See Section 2.3

Practice

Traffic Incident Management Step

Detection Verification Response Traffic Management

Traveller Information

Baseline technique

Emergency phone call and hotline by general public Enable Support – – –

In-road sensors (e.g. inductive loop) Enable Support – – –

Over-road sensors (e.g. radar and infrared) Enable Support – – –

Automatic Incident Detection (algorithm) Enable Support Support – –

Traffic incident watch (by professional drivers) Enable Enable Support – –

In-vehicle emergency (e.g. Mayday and e-Call) Enable Enable Enable – –

CCTV Enable Enable Enable Support –

Static traffic and road space management devices – – Enable Enable Support

Adaptive traffic control and communication devices (e.g. VMS and VSLS) – – Enable Enable Enable

Service patrol and incident response unit Enable Enable Enable Enable Support

Summary of emerging TIM techniques See Section 2.3

Practice

Traffic Incident Management Step

Detection Verification Response Traffic Management

New and emerging technique

Smartphones and GNSS Enable (Link) Enable Enable Support Enable

C-ITS and DSRC Enable (Lane) Support Support Enable Enable

Social media and crowdsourcing Enable (Link) Support Support Support Enable

Drones for traffic data and incident management Enable (Lane) Enable Support Support Support

Contemporary TIM Practices in AustralasiaAsif Hassan

Contemporary leading practices

Capability Development

Performance Evaluation

Traffic Incident

ManagementPlanning for

TIMMulti-agency Collaboration

See Section 4

5 phases of Integrated Process for Traffic Incident Management (IPTIM)

Multi-agency collaboration

• Effective TIM require good inter-agency coordination.

• Setting up a formal agreement or MoU can help to achieve efficient TIM.

• In Victoria, a MoU on Road Clearance has been signed between Victoria Police and VicRoads.

See Section 4.1

Planning for TIM

• Operational planning for potential traffic incident scenarios is an important step.

• Most jurisdictions follow the current best practice recommended by Austroads.

• In New Zealand, the Coordinated Incident Management System (CIMS) is used to establish the structure, roles and processes in managing traffic related incident response.

See Section 4.2

Traffic Incident Management (TIM)

Incident Detection and

Verification

Response to Traffic

Incidents

Traffic Management

See Section 4.3

Incident Detection

and Verification

Response to Traffic

Incidents

Traffic Management

• Incident detection is the very first action in incident management.

• Different technologies are currently in place across Australasia.

• Verification of incidents is heavily relied upon field units.

• In South Australia, based Bluetooth technology DPTI has developed an app, Addinsight, that can identify incidents and notify drivers.

See Section 4.3.1

Incident Detection

and Verification

Response to Traffic Incidents

Traffic Management

• Response to traffic incidents is categorised according to the nature and severity of the incident.

• Austroads NS1017 had proposed a ‘five-level’ incident classification based on the expected duration and the nature of the incident.

• In Queensland, TMR is actively rolling out an emergency vehicle priority system.

See Section 4.3.2

Level 1 Level 2 Level 3 Level 4 Level 5

Type of incident

Vehicle on shoulder

Vehicle in lane

Minor crash (no injuries)Minor debris

Injury crashDebrisFire

Minor injury crashHazmatFires

Estimated duration

Nil 0-30 minutes 30-60 minutes 1-2 hours >2 hours

Response TRU / tow TRU / towTrafficcontrol

PoliceTraffic controlTowClean up

PoliceFireMedicalTraffic controlTowClean up

PoliceFireMedicalHazmatTraffic controlTowClean up

Incident Detection

and Verification

Response to Traffic

Incidents

Traffic Management

• Traffic management is the application of traffic control measures in incident affected areas.

• Traffic management procedures vary based on the type of road, diversion route, and the weight and size of vehicles.

• In Western Australia, key stakeholders use laser scanning survey equipment to quickly capture a permanent 3D, 360 degree visual record of the accident scene in great detail.

See Section 4.3.3

Incident Detection

and Verification

Response to Traffic

Incidents

Traffic Management

• Responsible agencies across Australasia use different sources/technologies to disseminate incident-related information.

• Dissemination can be improved by extracting real-time incident-related data from social media.

• South Australian Addinsight system includes a smartphone app that provides drivers with real-time congestion information and the TMC with raw traffic data from about 15% of the traffic using the network.

See Section 4.3.4

Performance evaluation See Section 4.4

Item Input Process Output

Incident Management

Detection and verification Response, performance evaluation and review

Minimise traffic delays; maintain safety

Potential measures • number of incidents (by category: major, intermediate, minor)

• time to detect, verify

• response time of responders• response time (detection to

activation)• number of traffic diversions• time to clear incidents• duration of incidents• number of responses to

enquiries• lane-loss time• relationships with responders• major incident debrief/audit

• delays due to incidents• secondary incidents• customer satisfaction

(complaints, media reports)

Capability development

• Capabilities can be improved firstly within individual agencies and secondly across multiple agencies, at both the strategic and operational levels.

• Transport agencies provide in-house courses plus some inter-agency desktop and field training on the usage of software tools and equipment.

• Microscopic simulation modelling is an effective tool.

• Capability development towards technological advancements should be given greater priority.

See Section 4.5

Integrated Traffic Incident Management Principles and Framework Asif Hassan

TIM Principles

TIM principles

Modular structure with a common

language

Multi-stage incident response

planning

Prioritisation of TIM initiatives for value for money

Quick clearance policy

Technological adaptation at various TIM

stages

Feedback, evaluation and

continuous improvement

Inter-jurisdictional and multi-agency

collaboration

See Section 5.2

TIM Principles

TIM principles

language

planning

stages

collaboration

See Section 5.2

TIM Principles

TIM principles

language

planning

stages

collaboration

See Section 5.2

TIM Principles

TIM principles

language

planning

stages

collaboration

See Section 5.2

TIM Principles

TIM principles

language

planning

stages

collaboration

See Section 5.2

TIM Principles

TIM principles

language

planning

stages

collaboration

See Section 5.2

TIM Principles

TIM principles

language

planning

stages

collaboration

See Section 5.2

TIM Principles

TIM principles

language

planning

stages

collaboration

See Section 5.2

TIM Framework

Questions?

Dr Aut KarndacharukSenior Research EngineerAustralian Road Research Board (ARRB)P: +64 2 9282 4405E: auttapone.karndacharuk@arrb.com.au

Asif HassanProfessional EngineerAustralian Road Research Board (ARRB)P: +64 2 9282 4413E: asif.hassan@arrb.com.au

Austroads Webinar Techniques for Incident Management to ... · Techniques for Incident Management...

Documents

Proyecto ppt eliz

could have danced2.pdf · 60 ELIZ danced ELIZ still 22 ELIZ 'pread ELIZ nev 30 ELIZ all night! I could have danced etc. all night And have begged for more. I could have

Incident response, Hacker Techniques and Countermeasures

008bonecos02 - kfw.com.br · PARF F ELIZ NATAL F ELIZ NATAL . Title: 008bonecos02 Created Date: 5/31/2011 8:00:37 AM

Busqueda de herramienta eliz

Security Essentials Bootcamp Style Hacker Techniques, Exploits, and Incident Handling€¦ · · 2013-01-18Hacker Techniques, Exploits, and Incident Handling ... SEC504 Hacker Techniques,

Triangulosdelcuello Eliz 130103191212 Phpapp01

Anatomy of the Eliz. Aristocracy, Stone L

eliz Anivers - sibbp.com.brsibbp.com.br/boletim/edicao114.pdf · eliz Anivers (hamado cflnivørsariantøs . Title: Untitled-1 Author: Eduardo Nunes Created Date: 9/16/2011 11:21:15

Incident Management Process: Strategies, tools and …ebaltics.com/forum2008/Presentations/Schuurman.pdf · IMP: strategies, tools, techniques Agenda - Introduction into Incident

eliz avidad !! Jorge Núñez de Arco

Incident Management Process: Strategies, tools and techniques

Accident Incident Prevention Techniques

PowerShell Command Line Argument Obfuscation Techniques · in powershell.exe’s command line arguments • I began looking for these techniques in my incident response investigations,

Triangulos del cuello..eliz!!

Hacker Tools, Techniques, Exploits, and Incident Handling

ΕΘΝΙΚΗ ΛΥΡΙΚΗ ΣΚΗΝΗ · all Chappell he I could have danced, danced . 84 Poco meno ELIZ night ! Tempo I 92 ELIZ danced ELIZ still 44169 65 Eliza PP I could have all

Eliz Lit Nonfiction

I Could Have Danced All Night - Exmouth Musical Theatre … · 60 14 danced ELIZ still 22 El.!Z pread Fl. Cl ELIZ nev 30 ELIZ know V In 44169 begged wings dot:e could d'aced right

Incident Investigation Techniques - wvinsurance.gov to incident prevention measures. ... Inadequate design 3. ... What’s the cost of the control