RNO/ITS - PIARC (World Road Association)
Published on RNO/ITS - PIARC (World Road Association) (https://rno-its.piarc.org)

Home > Printer-friendly > Network Operations

Network Operations

Porto, Portugal – Traffic operations centre

Porto, Portugal – Traffic operations centre

Ground transport is essential to every country’s economic and social well-being. Many existing road networks have reached the limits of their capacity; so to ensure continued or improved efficiency, effectiveness and safety, better use of the existing infrastructure is essential.

Traditionally, road authorities and other organisations responsible for roads and highways, such as toll road operators, have focused primarily on building and maintaining the infrastructure: roads, highways, bridges and related facilities. Over the years, as traffic volumes have increased, this focus has shifted to place greater emphasis on effectively operating and managing the road networks to minimise disturbances and gain maximum usage. This transition is not easy because it involves re-thinking how the organisations carry out their mission and how the agencies themselves are structured.

Operating the network covers all field operations designed to maintain a satisfactory level of service for road users or, in the event of a disturbance, restore conditions as close as possible to the normal situation.

Operational Activities

Authors  Charles Wallace and Greg Speier (Courage & Wallace, USA)  John Miles (Editor)  Barry Moore (MoCh Tech Consulting Ltd, UK) 

In the past, road authorities and other organisations responsible for roads and highways, such as toll road operators, focused primarily on building and maintaining the infrastructure: the roads, highways, bridges and related facilities. Over the years, as traffic volumes have increased, this focus has shifted to place greater emphasis on operating and managing the road networks to minimise disturbances and maximise usage. This transition has not been easy because it involves re-thinking how organisations carry out their mission and how agencies are structured.

Road Network Operations (RNO) include all services focused on maintaining the safe and efficient use of highway infrastructure, and associated Intelligent Transport Systems (ITS). Dedicated road network management services have evolved that are designed to keep the road network available for safe use by road-users. Five groups of services can be identified:

1. Traffic management services that are designed to make best use of the available roadway and highway capacity day-by-day in real time – for very heavily trafficked routes and road networks this can be a 24 hours a day, 7 days a week activity.

Traffic management services principally involve responding to “events” as they occur, contingency planning in anticipation of those events, and planning the operational capability to respond appropriately. The events themselves may be:

  • planned and expected events, such as regularly occurring rush hour congestion, major road works or bridge maintenance and scheduled sports or entertainment events (See Planned Events)
  • unplanned and unexpected events such as road accidents, emergency situations and other traffic incidents (See Traffic Incidents)

2. Network control services that seek to control and influence road users over a wide area in order to spread the traffic load and optimise demand on the road network. Examples are balancing demand between alternative routes and integrating network management between different authorities. (See Urban Networks and Regional Networks)

3. Information services that have the capability to:

  • collect, filter, process, and disseminate data for operational traffic management (control centre operators, supervisors, management and maintenance) (See Network Monitoring)
  • provide traffic and travel information within the organisation, to stakeholder organisations (operating partners) and other external parties and the travelling public (See  Travel Information Systems)

4. Planning and reporting services that enable response planning for both planned and unplanned events, reports on operational and business services and performance monitoring of the highway network (See Planning and Reporting).

5. Support services that indirectly enable and allow other operational functions to be delivered: for example human resource and shift planning for mobile patrols and traffic control centre operatives, business plans, service development and telecommunications networks across the various functions (See TCC Administration).

Regional Operations

Adopting a customer focus for Road Network Operations has many implications. First is the need to keep roads and highways open and available for safe passage wherever and whenever possible: 24 hours a day, 7 days a week. Network Operations are designed to achieve just that.

For road authorities and other organisations closely involved a customer focus means working across administrative boundaries to achieve transport operations that are coordinated and integrated. The operational reach of any single road authority or operating organisation is no longer self-contained. Operational objectives have to be defined according to the road users’ needs. This means that to a great extent Road Network Operations must be integrated:

  • across geographical and jurisdictional boundaries between different road operators and road administrations
  • to provide smooth access to ferry-terminals, ports, airports, road-rail transfer points for inter-modal transfer

The Institutional issues in network operations are significant because of the number of stakeholders involved. Network operations can:

  • be multi-modal, multi-jurisdictional, multi-national (local, regional, national authorities and concession-holders)
  • use different levels of infrastructure (rural, local or national roads hierarchy)
  • involve interaction and cooperation between different organisations and entities on traffic management and traffic information

How Road Network Operations (RNO) are organised varies significantly from place to place. The missions, responsibilities and needs of the organisations involved can be quite different. In many countries, the national ministries/departments of transportation have primary responsibility for strategic roads; whereas provincial and even local agencies are responsible for other types of roadways. In many countries there is a significant role for the private sector.

Close coordination is critical between all the relevant agencies, operating partners, task forces dedicated to incident management or security, external news media and information service providers. This sometimes takes the form of a regional transport operations coalition with parties that include the road network operators, law enforcement, emergency vehicle operators, public transport operators, port operators and public and private providers of information – such as weather and various commercial activities. The degree of coordination involved differs depending on local priorities the need for coordination and the characteristics of the road network. (See Inter-Agency Working)

In order to ensure smooth implementation, roles and responsibilities must be clearly defined, including identification of technological requirements and who takes responsibility in emergencies and other critical situations.

The division of roles between different organisations can be set out within a legal framework where public institutions are involved, or in a more contractual arrangement such as PPP (Public Private Partnerships) when the private sector is involved. Close coordination between all stakeholders will ensure seamless operations that will benefit the road user. (See Public Private Partnerships)

Sharing of information and responsibilities between and across organisational boundaries can be a challenge. Nevertheless, significant progress has been made in gaining acceptance and support for ITS applications that enable effective information sharing and collaboration - while addressing concerns associated with differing priorities and requirements among the stakeholders.

What is a Region?

A “region” may be anything from a greater metropolitan area, such as Greater London, to a geographic sector of a nation or state, and can be extended to a cross-border international operating organisation, such as the Niagara International Transportation Technology Coalition (NITTEC) covering parts of western New York State in the USA and portions of Ontario, Canada.

At the local (city, county or toll road) levels, operations have a prominent role, because of the need to manage conflicting flows of traffic and share capacity evenly – or equitably – at junctions and for junction to junction coordination.

A regional operating partnership is a means of fostering relationships and building cooperation among entities that may otherwise have few, if any, opportunities to interact. These collaborations are a means of sharing information, experience, successes, problems and mutual needs with stakeholders in the broader region. A key output of such collaboration is often the development of a regional ITS architecture. (See ITS Architecture)

Regional Operations in UK

In the UK legislation requires local road and highway authorities to nominate “traffic managers” and coordinate traffic management with neighbouring authorities. The national operator of the strategic road network has also entered into local operating agreements with operators of local roads.

Regional ITS Infrastructure

The ITS infrastructure for regional operations is made up of a number of different features. For the systems to work properly, ITS services need all the basic components in place and these must be fully and reliably operational. For example a lack of basic infrastructure affecting any part of the information supply chain will lead to poor-quality information services and ineffective and inefficient network management. (See Data and Information)

Designers and installers of ITS for road network operations should consider the probability of roadside equipment being struck by passing vehicles and locate the equipment accordingly. Structures and poles holding ITS devices on high-speed highways should be shielded by collision-tested barriers, both to protect the equipment and to make any crash less severe. Similarly, potential threats of weather should be taken into account.

The technical requirements for regional ITS operations include:

  • reliable broadcast and mobile communications links, including the Internet, for transmitting data and information to and from the users and their vehicles (See En-route Information)
  • intelligent infrastructure and the means for vehicle location (fixed beacons or satellite navigation, with corresponding on-vehicle equipment) (See Location Based Services)
  • a well-developed info-structure consisting of location referencing systems, data dictionaries, digital maps and data exchange protocols (See ITS Infrastructure)
  • dedicated wireless and fibre optic links for high bandwidth applications such as transmission of Closed Circuit Television (CCTV) images (See Communications)
  • real-time data capture for traffic monitoring, pollution monitoring, weather monitoring (See ITS and Network monitoring)
  • the people and buildings to provide ITS services, such as traffic control centres, vehicle fleet controllers and dispatchers, travel information centres (See Traffic Control Centres,  Travel Information Systems and Operations & Fleet Management )
  • common support services, such as electronic payment systems, vehicle tracking, load and driver identification, enforcement and security systems (See Technologies and Processes, Enforcement and  Credential Checking)
  • enabling legislation (See Legal and Regulatory Issues)

Advice to Practitioners

Working across jurisdictions is essential: the technologies, procedures, planning and preparations to support management of recurring and non-recurring congestion have to be integrated. Experience clearly illustrates that providing the means for representatives of partner entities and task forces to meet and discuss common concerns and needs helps improve effective coordination and the building of relationships that significantly enhance common policies and practices, when, for example, incidents or emergencies occur.

Traffic Control Centres

Traffic Control Centres (TCCs) are directly or indirectly involved in most RNO operating strategies to some extent. For example TCC managers and operators can use Advanced Travel Information Systems (ATIS) to help mitigate the impact of non-recurring congestion in various ways. The objective is to deliver an as near as possible congestion-free network through the use of direct control measures and maximising the dissemination of traveller information using all available channels, particularly VMS, telephone information services (511 in USA), Highway Advisory Radio, internet web sites and social media. (See Traveller Services)

What’s in a Name?

Traffic Control Centres (TCCs) are known by different names in different regions of the world. Even in Europe, where the term TCC is common, some cities also have multi-modal Travel Information Centres (TICs). Some of the core activities for a TCC are to issue traffic information, which makes the term confusing.

In North America and Australia the term Transportation (or Traffic) Management Centre (TMC) is commonly used. Some USA centres and most in South America are called Traffic Operations Centres (TOCs). In the USA, “traffic control centre” is often used for (usually local) centralised traffic signal system control centres.

To avoid confusion, this website uses TCC to cover all such centres, unless otherwise stated.

TCC managers and operators can use ITS components to manage traffic and respond to incidents and emergencies. Typically ITS functionally in TCCs includes:

  • vehicle detection sensors (See Vehicle Detection)
  • CCTV (See Traffic Control )
  • Variable Message Signs (VMS) (See Traffic Control and Use of VMS)
  • ramp meters (See Highway Traffic)
  • Highway Advisory Radio (HAR) ( See Radio)
  • Road Weather Management Subsystems (RWMS) (See Weather Management)
  • software (See  Data & Information)
  • system telecommunications and in some cases centre to centre (C2C) communications (See Telecommunications)

The primary focus of many TCCs tends to be on supporting traffic management activities on major roadways, including incident response. While this may remain their primary function, a growing number of centres are finding ways to interact, share information and collaborate with partners in the overall management of the road system. Snowplough and ice mitigation operations are examples.

Concept of Operations

One of the key elements in planning for Road Network Operations is to ensure the successful design, implementation, operation and maintenance of the Traffic Control Centres (TCCs). This planning should be based on completed ITS studies and initiatives for the region such as a regional ITS architecture, strategic deployment plan, a “Concept of Operations” for the TCC – and operations and management plans. (See How to Create an Architecture)

The Concept of Operations for a TCC is a high-level description of system capabilities that are based on a vision, goals, identified needs and high-level requirements that are mutually agreed between the leading stakeholders. This forms the basis for defining the detailed requirements and for producing a high-level design. The Concept of Operations will also identify other major stakeholders, planned network coverage and operating hours and required resources (for example, hardware, software, facilities and personnel).

Guidance on how to develop the Concept of Operations for a TCC has been prepared by the Federal Highway Administration (FHWA) in the USA (see below). A Concept of Operations document will form a solid basis for establishing TCC operations and maintenance procedures, acquiring and utilising resources and interfacing with TCC stakeholders. The stakeholders include other public entities, private-sector companies, the general public and the media.

Video:  ITS - Intelligent Transport Systems and Services | the Swedish Transport Administration
The Future Traffic control Centre

A video depicting various scenarios in a futuristic TCC, the TMC of the Future, can be accessed in ITS America's Knowledge Centre under "Featured Videos" at http://itsa.org/knowledgecenter/knowledge-center-20.

The video runs for about 45 minutes. It was produced by the Intelligent Transportation Society of America (ITSA) for the 2008 ITS World Congress in New York City. Using actors, various traffic and incident scenarios were “performed” to live audiences. The TCC featured the more advanced features of a modern TCC and stressed the interagency activities in response to the “incidents” occurring. This video captures one performance.

It features the future use of what in 2008 was called "Vehicle-Infrastructure Integration (VII)" – but is now referred to as "connected vehicles" in the USA and “Cooperative Vehicle Highway Systems (CVHS)” elsewhere. The CVHS programme globally is still largely in the Research and Development (R&D) stage, so its use in the TCC is largely futuristic, although one of the key elements is the use of Floating Vehicle Data for traffic flow characteristics, which is becoming commonplace (See Probe Vehicle Monitoring and Probe Data).

The video shows this TCC also operates traffic signals on the arterial network and Integrated Corridor Management - which are increasingly being implemented across the world. It also addresses integration with other transport modes and services, such as public transport and parking and congestion pricing.

 

Reference sources

US Federal Highway Administration Transportation Management Center Concepts of Operation Implementation Guide Developed by FHWA, December 1999

Traffic Control Centre Functions

A Traffic Control Centre’s functions vary according to which agency operates it. The functional “separations” between motorway and urban network control are not rigid distinctions; and, ideally, the two would merge to enable fully integrated Management and Operations. Some countries, states or regions have moved in this direction, but it can involve considerable effort and expense.

The organisational and operational responsibilities of TCCs for different types of network varies:

  • TCCs for urban networks are typically operated by local governments and public transport companies. Increasingly ITS devices traditionally associated with motorways – such as CCTV and variable message signs – are being deployed. Public transport priority and Bus Rapid Transport (BRT) facilities may be present – in some cases on exclusive lanes or roadways
  • TCCs for regional highway networks are operated by road authorities (national or state agencies) and toll road operators – and tend to focus on managing congestion and incidents and maintaining road safety (for example at work zones)
  • TCCs for secondary inter-urban routes and rural networks are focused strictly on the route itself, for example toll-road operations, with generally no traffic signal operations

There are no clear technology differences between these three groups and they often overlap in function, but the institutional differences are more distinct. Advanced ITS applications provide the means for regional and local TCCs to work together, coordinate activities and share information when the need arises. (See Integrated Operations)

In many countries a growing number of local agencies have, or plan to develop, local fully functional TCCs, which are organised and operated to support the responsibilities of local agencies. On a daily basis this allows each TCC to effectively carry out its core mission.

The various services provided by a TCC can be grouped according to high-level functions, such as those shown in the diagram and described below:

Example of Traffic Control Centre Activities and Services (Source: Highways England UK)

Example of Traffic Control Centre Activities and Services (Source: Highways England UK)

Collection of Network and Traffic Information

The TCC needs decision support information on the network including a database of road network characteristics, information about incidents and other events (roadworks, accidents), traffic flow and journey times, and weather conditions.

This requires the TCC to adopt systems for:

1. the network description and location referencing (See Basic Info-structure)

2. obtaining information about:

  • planned roadworks on the network
  • unplanned events as soon as they occur
  • planned events that will have an impact on traffic conditions, such as major cultural or sporting events
  • planned roadworks on the network

3. continuous monitoring of:

  • traffic conditions
  • weather conditions

(See Data and Information, Traffic & Status Monitoring and Weather Monitoring)

Response to Events

The TCC needs to develop traffic management response plans that support its control strategies and the choice of information to be provided during incidents that affect traffic on the network. When incidents occur the TCC will implement these plans and analyse and update those plans on the basis of experience.

This requires:

  • off-line development of strategic responses
  • on-line selection and implementation of strategic responses
  • off-line evaluation of implemented strategic responses
  • hosting inter-agency Traffic Incident Management Teams

(See Integrated Strategies)

Public Information Services

These are the means by which a TCC provides information to media organisations, road users and the travelling public . They may include providing VMS at key locations on the road network, providing an internet site for public information – and use of social media and an interactive telephone service. 

Specifically the TCC core services will be:

  • provision of information via VMS
  • provision of information to the public via media organisations

(See Travel Information Systems and Traveller Services)

Network Operations Support

These are activities that enable the TCC to provide information and take action that will improve the ability of other organisations (operating partners) to perform their duties in managing the traffic and operations on their networks. The TCC needs to establish links with the traffic controllers for site that generate traffic or are major destinations. Examples might be a ferry port or airport, shipping container terminal, mineral extraction sites, major sports or entertainment centres, retail parks and shopping malls

They include:

  • assistance with planning roadworks, road closures and the movement of abnormal loads
  • the preparation of network management and statistical information
  • assistance to traffic police, emergency services and mobile Safety Service Patrols
  • assistance to other TCCs, passenger transport network operators

(See Planning and Reporting,  Public Transport Operations & Fleet Management and Operations & Fleet Management)

TCC Management Services

Management services relate to the day-to-day operation of the Traffic Control Centre and any additional operations that are required, specifically:

  • staffing, operating and managing the control centre
  • tours, visits and presentations
  • staff training
  • administration of other support services (for example conference room and operations support in emergencies

(See Traffic Control Centre Administration)

Toll Road Operations

For a TCC that covers toll road operations the ITS traffic systems and the electronic tolling systems are usually completely separate. They are not permitted to integrate, at least electronically, to protect the integrity of toll revenues. Toll-road TCCs generally manage incidents in the same way as their non-tolling counterparts. The fact that they operate facilities whose users are paying in real-time increases the pressure to clear incidents quickly. In some locations, such as Santiago, Chile, various toll roads use the same transponders to identify all vehicles passing through the toll gantries.

(See Toll Collection)

 

Urban Network Operations

Urban Traffic Control Centres (TCCs) have operated traffic signal systems for years using a wide range of software packages. Their main purpose is to keep traffic moving in the urban network of arterial roads. As more ITS devices are being deployed in the arterial networks, the use of ITS for Arterial Traffic Management Systems (ATMS) is becoming commonplace. European practice is to refer to Urban Traffic Control (UTC), or Urban Traffic Management and Control (UTMC).

A summary of operations for a TCC that controls an urban arterial road network is given in the tables below. (See also TCC Functions)

All Traffic Conditions

 

Operational Function

    Operational Method

Resources Used

 

Desired Result

 
 Surveillance

Visual monitoring

  CCTV, video wall, work-stations, video “tours”

Maximum visual coverage of network

 

Sensor monitoring

  Electronic detectors

Maximum sensor coverage of network, capture traffic characteristics

 

Vehicle probes

  Mobile safety patrols, crowd sourcing, floating vehicles

Detect and verify incidents in timely fashion

 Traffic control/ influence

Signal operation

  Traffic signal controllers

Regulate traffic flow through intersections, along corridors and in networks

 

Traveller information

  VMS and signals, PDMS, HAR, 511, media feed

Inform public and logistics managers of conditions for self-decisions

Recurring Congestion

Operational Function

Operational Method

Resources Used

Desired Result

Traffic control/ influence

Signal operation

Traffic signal controllers and traffic control software

Regulate traffic flow particularly along corridors and through networks

 

Contra-flow or other special lane use

Lane signals, VMS

Increase roadway capacity

Weather Events

Operational Function

Operational Method

Resources Used

Desired Result

Surveillance

Sensor monitoring

RWMS (although rare on arteries)

Detect adverse weather

 

Visual monitoring

CCTV, video wall, workstations, video “tours”

Detect and verify adverse weather

Traffic Incidents

Operational Function

Operational Method

Resources Used

Desired Result

Surveillance

Visual monitoring

CCTV, video wall, workstations, video “tours”

Detect and verify incident, dispatch response, notify other responders

 

Incident notification

Police, Emergency Control Centres

Initiate response

 

Vehicle probes

Safety service patrol (if used)

Detect incidents, SSP respond and assist

Signal operation

Adaptive signal controllers

Regulate traffic flow around incident

Improve throughput

 

Traveller information

VMS, PDMS, HAR, 511, website, media feed, social media

Encourage diversions and journey time changes

Work Zone and Maintenance activities

Operational Function

Operational Method

Resources Used

Desired Result

Traffic control/ influence

Traveller information

VMS, PDMS, HAR, 511, website, media feed, social media

Safe, free flow past maintenance and other road work or diversion of route

Key to Resources

Resource

Technology

Further information

511 (USA)

Telephone travel information system

Pre-trip Information

CCTV

Closed-circuit Television

CCTV

eCall

Automated vehicle collision reporting system

Warning Systems

Electronic detectors

Vehicle and pedestrian sensors

Roadway Sensors

HAR

Highway Advisory Radio

Radio

Lane signals

Overhead VMS showing lane availability

Highway Traffic

Media feed

Automatic feed of information to websites, radio and TV stations

Pre-trip Information

PDMS

Portable Dynamic Message Sign

User Interfaces

Queue detectors

Electronic sensors to detect queues / queue length

Vehicle Detection

Ramp signals

Traffic signals to control traffic volumes entering a motorway / freeway

Highway Traffic

RWMS

Road Weather Management Systems

Weather Monitoring

Social media

Facebook, Twitter, etc

Social Media & Data

Speed advisory VMS

Advisory Variable Message Signs

Use of VMS

Speed limit VMS

Mandatory Variable Message Signs

Use of VMS

Video “tours”

Successive display of CCTV images from different cameras

Traffic Control

Video wall

Wall-mounted screens to display CCTV images

Traffic Control

VMS

Variable Message Signs

Use of VMS

 

Highway Network Operations

The tables below summarise the typical activities that a Traffic Control Centre will perform for different types of traffic conditions on motorways, freeways, expressways and other regional arterial roads. The desired results (operational outcomes) are indicative of the specific situations. (See also TCC Functions)

Not all of the resources mentioned below will be present in every control centre. Field network telecommunications, device controller infrastructure and control room systems and software, are common to all and are not mentioned in the tables.

All Traffic Conditions

Operational Function

Operational Method

Resources Used

Desired Result

Traffic Monitoring and Surveillance

Visual monitoring

CCTV, video wall, workstations, video “tours”

Maximum visual coverage of network

 

Sensor monitoring

Electronic vehicle detectors

Maximum sensor coverage of network to capture traffic characteristics

 

Vehicle probes

Mobile safety patrols, crowd sourcing, floating vehicles

Detect and verify incidents in timely fashion

Traffic control/ influence

Travel & Traffic information

VMS and signals, PDMS, HAR, media feed

Inform public and logistics managers of conditions for self-decisions

Recurring Congestion

Operational Function

Operational Method

Resources Used

Desired Result

Traffic control/ influence

Ramp metering

Ramp signals, queue detectors

Smooth merging, effect minor diversion

 

Contra-flow, High Occupancy Toll, shoulder running or other special lane use

Lane signals, VMS, PDMS

Increase roadway capacity

 

Variable speed limits

Speed limit VMS

Stabilise flow

Weather Events

Operational Function

Operational Method

Resources Used

Desired Result

Surveillance

Sensor monitoring

Road Weather Management Systems

Detect adverse weather

 

Visual monitoring

CCTV, video wall, workstations, video “tours”

Detect and verify adverse weather

Traffic Incidents

Operational Function

Operational Method

Resources Used

Desired Result

Surveillance

Road-user reports

Cell-phones, 

emergency telephones, social media

Operators alert to possible incident

 

Visual monitoring

CCTV, video wall, workstations, video “tours”

Detect and verify incident, dispatch response, notify other responders

 

Sensor monitoring

Electronic detectors

Incident detection algorithms: automatic alert for potential incident

 

Incident notification

Police, Emergency Control Centres

Initiate response from rescue and ambulance services, vehicle recovery, emergency repair operators

 

Patrol vehicles

Safety service patrol, road watchers

Detect incidents, Mobile patrols respond and assist

Traffic control/ influence

Travel & Traffic information

VMS and signals, PDMS, HAR, 511, website, media feed, social media

Encourage diversions and journey time changes

 

Ramp metering

Ramp signals, queue detectors

Smooth merging, effect increased diversion

 

Speed advisory

Speed advisory VMS

Calming of speeds and reduced lane changing

 

Variable speed limits

Speed limit VMS

Reduce limit to safe speed

 

Lane use control

Lane signals

Open/close lanes as appropriate

 

Maintenance of traffic

VMS, PDMS

Safe, free flow past maintenance and other road work

 

Queue warning

VMS, PDMS

Reduced secondary incidents;

Safe, free flow past maintenance, other road works and incidents

Work Zones and Maintenance Activities

Operational Function

Operational Method

Resources Used

Desired Result

Traffic control/ influence

Traveller information

VMS, PDMS, HAR, eCall (511), website, media feed, social media

Safe, free flow past maintenance and other road work or diversion of route

 

Key to Resources

Resource

Technology

Further information

511[USA]

Telephone travel information system

Pre-trip information

CCTV

Closed-circuit Television

CCTV

eCall

Automated vehicle collision reporting system (Europe)

Warning Systems

Electronic detectors

Vehicle and pedestrian sensors

Roadway Sensors

HAR

Highway Advisory Radio

Radio

Lane signals

Overhead VMS showing lane availability

Highway Traffic

Media feed

Automatic feed of information to websites, radio and TV stations & via social media

Pre-trip information

PDMS

Portable Dynamic Message Sign

User Interfaces

Queue detectors

Electronic sensors to detect queues / queue length

Vehicle Detection

Ramp signals

Traffic signals to control traffic volumes entering a motorway / freeway

Highway Traffic

RWMS

Road Weather Management Systems

Weather Monitoring

Social media

Facebook, Twitter, etc

Social Media & Data

Speed advisory VMS

Advisory Variable Message Signs

Use of VMS

Speed limit VMS

Mandatory Variable Message Signs

Use of VMS

Video “tours”

Successive display of CCTV images from different cameras

Traffic Control

Video wall

Wall-mounted screens to display CCTV images

Traffic Control

VMS

Variable Message Signs

Use of VMS

 

Traffic Control Centre Administration

Successful Traffic Control Centre operations require effective administration. A basic requirement is easily accessible and well-organised reference documentation for control centre staff. A set of policies, plans, guides and instructions is needed to guide TCC managers and operators in their duties and collaboration with others (operating partners and other stakeholders).

A minimum set of documents, available in hard copy and/or on-line electronically, will be:

  • documentation for the ITS Architecture that ensures conformity of ITS devices and identifies at a high level the stakeholders, their roles and responsibilities  (See Why Create an ITS Architecture?)
  • a "Concept of Operations" document that defines policies, interagency agreements and roles and responsibilities (See Traffic Control Centres)
  • Incident Management Plans, which detail the roles and responsibilities of operators and responders (See Incident Response Plans)
  • Emergency Operations Plans, which defines the TCC roles in emergency management  (See Emergency Plans)
  • Systems Engineering Management Plan that maps out the entire process (See Operations & Maintenance)
  • TCC Operations Manual, which details all aspects of centre operations, from system operations, through administrative operations, to personnel matters
  • TCC Software User’s Guide, which provides the details of the central system software and its operation
  • Standard Operating Procedures dealing with the specifics of specialised activities, such as dealing with the media
  • Job Guides, such as pocket guides, that serve as a quick reference or checklist, for operations such as incident management and maintenance

Business Planning

The establishment of a business plan is recommended to provide a roadmap for agencies to establish the TCC goals and objectives and to achieve them. A properly implemented TCC business plan will provide justification for sustained operations by means of on-going performance measurement and reporting of outcomes. The business plan also helps to identify the present and desired future state of the TCC’s operational effectiveness and key gaps that need to be addressed. The plan will include:

  • an analysis of the Strengths, Weaknesses, Opportunities and Threats (SWOT) of TCC implementation scenarios
  • expected benefits, associated funding requirements and a financial strategy
  • requirements for establishing operating partnerships
  • details of the TCC’s organisation and management structure and personnel needs
  • consideration of equipment life-cycles, the need for asset management and opportunities for value engineering

TCCs require significant and committed funding for their deployment, operation and maintenance. A lack of continuing funding will affect and limit the desired results. Adequate staffing and operations planning are also necessary. The majority of transport agencies run TCCs with public-sector staff but some outsource the TCC operations to private-sector companies – sometimes because it has been a challenge to staff and train personnel to effectively operate the TCC.

Organisational Aspects

Key to successful road network operations is the inter-agency, multidisciplinary integration of the TCC with the operational activities of other organisations that have a part to play or who manage adjacent highway networks. This is referred to by some as the “4-Cs": Communication, Cooperation, Coordination, Consensus.

Managing routine traffic, traffic incidents and even transport emergencies is greatly enhanced by organisations collectively applying the 4-Cs. This is best done when centres like the TCC, Emergency Control Centre (ECC) and/or Emergency Operations Centre (EOC) are co-located – or at least have close two-way communication for data and information exchange and sharing of CCTV camera images. For example, information seen on camera can be actively provided to those responding to a traffic incident (police, fire, other emergency services, towing companies and maintenance) so responders can request the resources they need.

The vast majority of ITS technology is deployed in urban areas and alongside motorways, although some ITS devices are deployed in remote rural areas. Given the distances involved, this poses an economic challenge to the responsible organisation. Wireless communications overcome some of the challenges – but full coverage for surveillance and traveller information is still difficult. The increasing use of Floating (or Probe) Vehicle Data (FVD) provides TCCs with the ability to access data that can indicate rural incidents and trigger both response and information dissemination to travellers and responders. (See Probe Vehicle Monitoring)

Staffing

ITS asset management includes not just hardware, but also software and key personnel, in order to support the long-term goals of the organisation and maintain its ITS capability. General guidelines include:

  • staffing should be based on a needs assessment that addresses what the authority or organisation is trying to accomplish and what skills are needed to meet those needs – taking account of the equipment and software deployed
  • the number of TCC operators depends on the functions that are being performed, the number of facilities covered and the operating philosophy of the centre
  • the total number of staff will depend on the hours of operation – in general, staffing for 7/24 operations employs three assignment shifts (8 hours each per day) although other shift assignments are used in some countries
  • peak periods may require more operators. In college/university cities, students can be a source of support operators because they can work peak hours and go to class mid-day

For information on Traffic Control Centre staffing See http://ops.fhwa.dot.gov/freewaymgmt/publications/frwy_mgmt_handbook/chapter14_04.htm

Training

It is essential that managers provide comprehensive training in every aspect of traffic management and related topics to the staff who have a role in TCC operations.

Training comes in many forms, among them:

  • self-administered courses on the web, computers or even paper, for specific topics (their effectiveness is limited)
  • classroom courses using slides, videos and other media to support the lectures – good instructors try to be as interactive with the students as possible
  • interactive, online simulations, which are effective, but generally require specialised software that may not be widely available
  • table-top exercises that take participants through pre-planned scenarios and require them to “act out” the response (very effective for incident and emergency management training, but involve relatively few participants at a time)
  • field exercises, in which participants carry out a simulated situation and perform their duties as realistically as possible (very effective, but costly and time consuming)
  • On-job training under a mentor once basics are learnt using one or more of the other methods (probably the most effective)

Field exercises are generally more appropriate for those who respond to incidents on the road or highway. In-house exercises can be designed for TCC operators – the challenge is the ability to simulate actual operations and procedures including the use of equipment and devices. Some centres have demonstration equipment that can be used for this purpose.

One-on-one training and small group on-job training is most likely to be recalled by those who experience it but it takes time to encounter a wide variety of situations. The more interactive the training can be, the more effective it will be in producing lasting success.

A useful report on “Impacts of Technology Enhancements on Transport Management Centre Operations,” produced by the Transport Management Centre Pooled Fund Study (TMC PFS) in the USA, provides guidance to TMC/TCC managers on how to better position themselves operationally in anticipation of future technology changes and advancements. (See http://www.ops.fhwa.dot.gov/publications/fhwahop13008/index.htm)

Reference sources

Booz Allen Hamilton (2005)Transportation Management Center Business Planning  US Federal Highways Administration, Washington D.C.

Seymour, E.J. J.D. Carvell, Jr., J.L. Carson, and R.E. Brydia (Texas Transportation Institute 2005) Handbook for Developing a TMC Operations Manual Report FHWA-HOP-06-015, US Federal Highways Administration, Washington D.C.

System Monitoring

Effective Road Network Operations (RNO) require that the network monitoring and traffic control systems are fully functional. This is accomplished most effectively by monitoring the system components. There are two aspects to this:

  • monitoring ITS to assess the health of the central operating system
  • ITS-based methods of monitoring the road network for the purposes of traffic management

Traffic Control Centre (TCC) software will monitor the incoming data, images and other media from the field devices that are used for routine traffic management and incident detection, verification, notification and dispatch.

Within the TCC, the software automatically monitors the status of its key processors, servers, video displays, communications and all the other assorted equipment – and the software itself – to ensure a high level of operational efficiency. Equally important, these form the core of data and information used for performance management. (See Planning Procedures)

Monitoring system performance is essential in evaluating its success in achieving its objectives. Typically, the TCC software will have modules that automatically monitor the various components to detect and report failures or other anomalies that need to be brought to the operators’ attention. Depending on the device type, in legacy systems this is generally achieved through: periodic polling of the devices to sense expected responses, monitoring of data streams for continuity – and other diagnostic techniques.

As device sophistication improves the trend is to incorporate more self-diagnostics, pushing data on equipment status and performance to the central system. The results of the monitoring are used for instant failure reporting, as well as providing system performance measures over time.

From a traffic operations perspective, system monitoring and automatic fault reporting is essential. It enables the TCC operators and managers, along with the maintenance team, to keep the system healthy to perform its tasks in managing traffic and providing situational awareness to the travelling public. System monitoring helps to ensure that managers can be confident that the investment in ITS is being nurtured and protected through proper operation, or that problems are identified and can be addressed promptly.

Equipment Monitoring

In the USA, Florida’s Turnpike Enterprise operates a unique tolling and revenue monitoring system. The SunWatch Centre monitors all equipment in the system, alerts operators to malfunctions and failures, and takes action to mitigate the problem.

Given the nature of its operations, the SunWatch Centre is not widely advertised, but some information is available from the International Bridge, Tunnel and Turnpike Association’s website at http://ibtta.org/awards/sunwatch-operations-center

 

System Maintenance

ITS asset management includes not just hardware, but also software and key personnel, in order to support the long-term goals of the organisation and maintain its ITS capability.

Maintenance activities on ITS devices and traffic signal systems can impact on Road Network Operations. When ITS is first deployed, the equipment is new and does not require extensive maintenance resources. As systems expand and age, there is a continuing need for – and complexity of – maintenance operations.Two aspects of maintenance have a direct impact on operations:

  • physical device maintenance
  • maintenance activities on the roadway and its impact on traffic
Physical device maintenance requires monitoring of the operational status of all devices. This includes the maintenance of specialised support systems such as fibre optic communications and requires:
  • monitoring operational performance
  • scheduling routine maintenance

There are two types of routine maintenance: preventive and responsive.

Preventive Maintenance

Preventive Maintenance is generally regularly scheduled maintenance designed to pre-empt device failure that would render the device unserviceable. Preventive maintenance will extend the active life of devices and subsystems. It can use past experience to anticipate when devices should receive attention. Automated maintenance management systems base the scheduling on a number of factors that are analysed by the software to produce a schedule.

Preventive maintenance can be as simple as cleaning cabinets and cable runs/conduits, securing wiring and printed circuit board connections, to scheduled pre-emptive repair. Alternatively it can entail replacement of components or entire devices.

Responsive maintenance

Responsive maintenance (or reactive maintenance) concerns the repair or replacement of a component or system following failure or damage caused by a collision or other incident. Failed ITS equipment and non-functioning network monitoring devices will not provide the images, data or information needed to help maintain stable traffic flow.

When failures occur the devices cannot perform their functions, which will often be detrimental to RNO. Responsive maintenance should be the highest priority, since restoring equipment function is the key objective. It is advisable for TCC operators to prioritise conflicting maintenance needs, rather than leaving maintenance staff to determine this themselves.

The key to successful maintenance is to have a complete, manageable inventory of all devices. Automated support software can be an ideal way to maintain the inventory – and can also assist in preventive and responsive maintenance operations. (See Data Management and Archiving)

Maintenance Management Systems

Florida Department of Transportation provides an example of a combined ITS Maintenance Management Systems (MMS) and Fibre Management Systems (FMS), known as the ITS Facility Management System (ITSFM). (See http://www.dot.state.fl.us/trafficoperations/ITS/Projects_Telecom/ITSFM/ITSFM.shtm)

Automated Maintenance Systems

Factors that lead to the adoption of an automated maintenance system include:

  • the need to minimise system downtime especially when this would affect public confidence in the traffic management and information services that are delivered
  • the size and evolving nature of the equipment inventory due to technological advances, which often results in mixed equipment types
  • the greater the number of stakeholders involved (for example, manufacturers, vendors and suppliers, maintenance staff, sometimes from different agencies)
  • integration issues associated with many different device types and brands
  • difference between ITS maintenance (which mostly involves electronics and communications) and roadway maintenance
  • need for consistent procedures and practices
  • need for accurate and complete ITS inventory (devices, equipment and materials, such as fibre-optic cables)
  • need for an efficient work-order-based maintenance system
  • ability to track expenses (such as, labour, materials, parts, entire devices) to the specific device or subsystem
  • need for timely, accurate and comprehensive reporting
  • limited funding – the need to be efficient and effective with available resources, while at the same time justifying the maintenance programme

Most Traffic Control Centres (TCCs) have “up-time” targets for system availability that challenge the maintenance team to keep devices operational at least a certain percentage of time, for example, 98% or 99% availability. Only automated systems can both organise the maintenance activities and keep track of them. An ITS maintenance management system and a communications management system are part of the ITS operation, just like the TCC software. If the RNO organisation operates its own comprehensive telecommunications networks, this will justify a telecommunications “network manager”, which is common place in the telecommunications sector.

Systems maintenance can be performed either by in-house staff or outsourced to others—usually original equipment suppliers but also third party maintenance companies. In some regions the trend is towards outsourcing systems maintenance to private contractors. The substantial differences in the nature of ITS and roadway maintenance, generally leads to ITS maintenance being outsourced to a specialised electrical contractor.

Some large consulting firms are increasingly expanding their involvement in this business, sometimes called asset management.

Equipment maintenance

The purpose here is to maintain ITS equipment or restore it to a condition that can effectively handle the assigned functions, at the lowest possible cost. To achieve this objective, the operator must:

  • reduce the probability of equipment failure, quickly detect problems and take prompt and effective action
  • upgrade equipment and systems (including software upgrades) to adapt to changing conditions

Organisational arrangements will depend on the size of the maintenance operation, the volume, nature and location of equipment, and the resources and skills available. Organisations will need to determine the scope of maintenance activities to be undertaken internally by the operating organisation and those that will be sub-contracted.

Effective maintenance is based primarily on detailed wording of supply contracts, follow-up and effective handover. This is to ensure a precise definition of the work to be performed, conditions of delivery, contract deadlines for restoring service and penalties for non-compliance. It also relies on:

  • extensive documentation of equipment maintenance procedures
  • fault diagnosis equipment for dynamic equipment and to remotely restart systems
  • prioritisation of safety-related maintenance (such as road tunnel ventilation equipment, lane assignment signals)
  • qualified (training, accreditation) and available staff (noting any restrictions and aiming for permanent assignments)
  • complete maintenance contracts and follow-up
  • spare parts inventory

Motorway ITS Maintenance

Motorway Maintenance Management Systems (MMMS) generally operate on limited-access roadways, which carry high volumes of traffic at relatively high speeds. Disruption to traffic adversely impacts traffic operations. Fortunately, many ITS devices are located off the roadway, but within the s of way, so maintenance activities can be conducted without directly interfering with traffic. Even in these cases temporary traffic control devices may be required for the protection of the maintenance crew. Efficiency of maintenance operations is essential.

The mere presence of maintenance vehicles causes driver distraction (“rubbernecking”), in the same way as roadside incidents. This is a particular concern in restricted situations, for example part of a tunnel or long bridge. Working on, or adjacent to, live carriageways is hazardous and some simple precautions are needed – for example, high visibility clothing, hazard lights and deployment of temporary traffic management to close lanes.

There is greater traffic disruption when the maintenance crew must work over an active lane or median shoulder, such as on the exterior of a VMS. When this happens, the crew is generally required to close the lane(s) over which they work and deploy temporary measures to maintain traffic flow. This work should, whenever possible, be done during off peak times to minimise the adverse effect on traffic. The work is often contracted out to specialist firms to provide temporary traffic management. The TCC will need to be vigilant in ensuring that measures to maintain traffic flow are in place and are operating effectively at all times.

These considerations apply equally to maintenance of routine traffic control and information devices, such as fixed signage – so general maintenance should follow the same practices as the ITS maintenance agency. The TCC should be notified whenever there are activities on the motorway, particularly if lanes are to be closed. Some countries use Lane Closure Management Systems to schedule and manage closure requests and contractor roadwork.

Particularly dangerous work sites – for example on one of the traffic lanes – should be protected by a crash barrier (crash-attenuator or crash cushion) such as a vehicle or trailer positioned upstream of the lane closure. In Santiago, Chile, one of the urban toll road operators requires all providers of maintenance to equip work crews with such equipment.

All maintenance on the highway, while absolutely necessary, should be managed in such a way that the negative impact on traffic is minimised and the safety of maintenance crews and the travelling public are maximised.

Urban ITS Maintenance

The primary difference between motorway and urban arterial road networks is that in the urban situation considerably more maintenance has to be done on, or immediately above, the roadway itself. Traffic signal heads, supporting span arms, signs, wires and overhead vehicle detectors are all located over the roadway. Devices off the roadway, such as signal cabinets and other ITS equipment, will also generally be located in less open spaces. If a hard shoulder is not available it is likely they must be accessed from a traffic lane. Lane closures are far more likely on urban arterials roads and city streets.

Many high-capacity urban arterial roads experience traffic speeds that are not significantly slower than a motorway. Other roads have lower traffic volumes, particularly off peak, and traffic speeds may be lower too. Temporary traffic management is important and without it, conditions may be unsafe. The number of movements possible (such as driveways and turning movements) also greatly increase hazards. The paramount objective must be the safety of the maintenance crew.

 

Planning and Reporting

Traditional planning processes in roads and highways authorities have focused on capital improvements to roadways. In many countries there were few mechanisms to effectively support ways of improving road network operations or to support thinking beyond the physical construction of facilities and infrastructure. This is changing to allow consideration of how road and highway facilities can operate most effectively.

Planning for operations is inevitably part of the long-term planning effort, but the planning process needs to be more than simply planning for, and funding of, the installation of additional infrastructure. Specifically, planning for operations should ensure a long-term, adequate and reliable source of funds for day-to-day traffic operations and maintenance of the ITS infrastructure.

Planning for Road Network Operations (RNO) now normally includes three important aspects:

  • management and operations included as part of the on-going regional transport planning and investment process
  • coordination of transport operations regionally to facilitate network control strategies
  • opportunities for developing links between different operating partners for collaboration and regional planning, including all phases of incident and emergency management

Linking together planning and operations will encourage an improvement in transport decision-making and the overall effectiveness of transport systems. Coordination between the planners and operating units helps ensure that regional transport investment decisions take account of the available operational strategies that can support regional goals and objectives.

In summary, the success of RNO is closely related to the strategic role and objectives of the transport agencies responsible for RNO – such as:

  • engaging in operational policies that will deliver a high level of service to road users - in addition to building roads and maintaining them
  • engaging in inter-agency, multidisciplinary and multimodal planning, preparation and response for routine conditions (for example recurring congestion) – as well as unscheduled (non-recurring) incidents
  • preparing staff at all levels by providing proper training, not only in their own roles and duties, but also, to some degree, in those of their partners – so basic knowledge and expectations are mutual
  • avoiding institutional barriers that deter progress and success
  • using technologies wisely and sharing data and information amongst agencies

These “high-level” concepts should guide agencies in their formulation of policy and operational practices. (See Traffic Management and Demand Management)

Planning Procedures

Planning for Road Network Operations involves consideration of the organisational requirements for the operational activities including preventive actions. Practical constraints (such as inter-agency demarcations) and on-going local factors must be defined together with the supporting information systems and decision-making or control systems that are needed. The success of a plan depends on the distribution of activities between partners and on their full knowledge and understanding of their assigned tasks.

Generally, design procedures require the following:

  • identify underlying traffic and road environmental problems
  • identify the road network section to be covered in the project
  • define objectives including performance criteria
  • select functions and services, including vehicle detection and traffic monitoring
  • identify the information strategy to best achieve the goals
  • identify partners to be involved in the project
  • select technologies based on functional requirements
  • determine funding resources
  • obtain any inter-agency agreements needed
  • implement the project

Establishing a Reference Database

The lead organisation for traffic management on the network will need a reliable database for preparing, organising, implementing, managing and assessing operations more effectively. This will enable the organisation to become a valuable resource for addressing ad hoc issues concerning the network, the need for studies and for providing statistical material for publications. (See Data Management and Archiving)

Data includes:

  • details of the infrastructure
  • sensitive points
  • equipment, including static and mobile equipment
  • traffic data used by computerised systems
  • accident and traffic statistics
  • past events and their consequences
  • events in progress or planned
  • operating partners and players
  • tools and methodologies

This data will be supplemented with:

  • traffic management plans
  • a series of instructions and automatic response sheets
  • a collection of ad hoc data (travel time, occasional traffic counts)
  • assessments and survey results
  • feedback on experience

The tools needed to establish the database are:

  • computers and software for developing, processing and viewing computer databases (geographic information systems)
  • map coverage of the network to a suitable scale
  • video recordings and digital imaging

The network management database is not static: there will be a continual, on-going requirement for up-dates.

Maintenance of the data files is a meticulous, time-consuming process that demands specific training to achieve the results required. Theoretical knowledge of the network and its environment must be supplemented with hands-on experience and local knowledge. For example, to determine whether a planned detour is realistic, it is necessary to know as accurately as possible the level of traffic on each road segment. Lessons learnt from the analysis and response of actual situations must be factored into establishing response procedures for future events.

Events Database

The purpose of an events database is to forecast periods when the probability of traffic disruption is high. The task consists of studying the calendar (dates of public holidays, school holidays and major planned sporting, cultural and entertainment events) and comparing it with previous years, comparable past situations and/or weather forecasts.

Implementation involves specific stages:

  • information gathering (holidays, traffic data, weather conditions, planned events, unplanned events)
  • ranking the information by event typology (based on the type of intervention and methods to be applied)
  • analysing previous similar situations
  • producing calendar-type documents:
    • annual – for risks attributable to seasonal variations in traffic volumes;
    • shorter term – for risks linked to weather conditions, popular sporting, leisure or cultural events

The task requires painstaking attention to detail in collecting and analysing data, particularly keeping logs. It is vital work and helps improve the management of the road network – thereby decreasing the number of unplanned incident and emergency response situations.

Procedure Manuals

The purpose of a procedures manual is to define the operating actions of all roadway partners and guide their implementation. A procedure manual consists of listing all tasks to be performed and all resources required to carry out the task specified for each event or incident scenario. Procedure manuals can be produced for roadworks, mobile traffic patrols, traffic monitoring and traffic management plans. The production of procedure manuals is a good subject for initiating and fostering cooperation with partners.

The events to be handled and their consequences will sometimes differ slightly from the scenarios studied. Although procedure manuals need to be detailed, they can and should leave room for some initiative by those at whom they are aimed.

Since procedures manuals are tools common to many partners, it is important to ensure that the reference framework and vocabulary are understood by all. The design of manuals that link to various plans – must be consistent and support cross-referencing. They must be periodically updated and the updates to all documents must be distributed. The provision of procedure manuals on-line may be the best way of keeping them current and available.

Performance Monitoring

There is a twofold objective in tracking the performance of the operating measures:

  • to determine whether the measures taken have achieved and continue to achieve their objectives, with resources that are sufficient and proportionate
  • to adapt future measures accordingly

Monitoring methods must be developed to quantify the impact of the measures implemented and detect dysfunctions or serious variance from anticipated results.

This approach relies on information gathering that must be a systematic and a planned part of routine documenting procedure (logs, fact sheets and other reports).

A small number of basic performance indicators must be defined case-by-case and changes tracked over time. To define these indicators without overlooking key points, the following factors can serve as a guide:

  • relevance: are the actions, decisions, information, interventions, scenarios, instructions or procedures relevant?
  • communication: is information provided where this would be useful – and do users understand it?
  • knowledge of events: are partners informed of all relevant events; is the information adequate and correct – and if not – what are the consequences?
  • timing: is information gathered and disseminated when needed to support effective decision making and actions?
  • comparison of forecasts and actual data: where forecasts are made are they accurate – and what are the consequences of variances from forecasts (unnecessary work, improvised or poorly adapted measures)?
  • updates: are various components periodically updated (manuals of procedure, work procedures, databases, reporting mechanisms, directories, maps or information bulletins)?
  • staff: are officers adequately trained for their duties?
  • costs: what costs can be identified (time spent and budget) – how are they changing and are they proportionate?

See Measuring Performance

Updating RNO Procedures

The purpose of updating the operating procedures is to plan for, and justify, the resources appropriate to the context. Resources can include hardware, software and documents as well as personnel organisation and training. The context will cover the traffic situation, incident response infrastructure, organisation of other services, user needs and available technologies.

Updating procedures and operating methods extend to physical assets as well as documentation and service organisation. It specifically requires:

  • defining and applying systematic procedures for monitoring existing operating methods (for example – annual information/motivation sessions for officers, annual document updates)
  • remaining attentive, and anticipating changes, to the context (infrastructure, traffic, operating policy, service changes, user needs, technologies, partners) and analysing their impact on operations
  • gathering specific data (counts, compliance rates with VMS recommendations) and monitoring a few simple indicators (frequency of use, availability of equipment and/or organisations)

This work requires effort that is rarely spontaneous – and ultimately may highlight needs for specific resources (studies and production of documents). The outcome may be elimination of unnecessary or out-dated working methods. It is also fairly common for objectives and strategies that are initially defined – to be revised in light of experience gained.

 

Reference sources

Seymour, E.J. J.D. Carvell, Jr., J.L. Carson, and R.E. Brydia (Texas Transportation Institute 2005) Handbook for Developing a TMC Operations Manual FHWA-HOP-06-015 US Federal Highways Agency Washington D.C.

Traffic Management Plans

A Traffic Management Plan (TMP) provides for the allocation of traffic control and information measures in response to a specific, pre-defined traffic scenario – such as the management of peak holiday traffic or the closure of strategic route because of bad weather, maintenance or a serious road accident. The objective is to anticipate the arrangements for controlling and guiding traffic flows in real-time and for informing road-users about the traffic situation in a consistent and timely way.

The plans, which will differ in detail according to local circumstances, apply in the following cases:

  • major traffic accidents
  • very heavy traffic
  • extreme weather conditions
  • natural or technological catastrophes
  • special events (sports, cultural, leisure) resulting in unusually high traffic volumes, capacity constraints or a major displacement of road users

TMPs do not solve all traffic problems but lessen the consequences. They improve coordination and cooperation between partners and facilitate the establishment of mutual agreements on the operational requirements.

A TMP will optimise the use of existing traffic infrastructure capacity in response to a given situation and provide a platform for a cross-regional and cross-border seamless service that provides consistent information for the road user. The situations covered can be unforeseeable (incidents, accidents) or predictable (recurrent or non-recurrent events). The measures are always applied on a temporary basis – although “temporary” may be lengthy, such as a construction or long-term maintenance activity.

TMPs define and formalise:

  • decision-making and coordination
  • driver and traveller information
  • the coordination of traffic management and road information measures

The purpose of this approach is to limit the effects of events that can lead to serious deterioration of traffic conditions and to enhance road safety. The objective is coordinated action by the various authorities and services that participate in the operation of the roadway.

TMPs can be developed for corridors and networks with the aim of delivering effective traffic control, route guidance and information measures to the road user. An improvement in overall performance is possible by securing effective collaboration and coordination between the organisations directly involved. By strengthening cooperation and mutual understanding a more integrated approach will be achieved to the development, deployment and quality control of traffic management measures. (See  TCC Functions, Urban Operations and Highway Operations  )

Four geographic levels can be considered for the elaboration of Traffic Management Plans:

  • Regional TMPs: for networks within areas or regions that can be extended, under certain conditions, to link with neighbouring regions for cross-regional and cross-border levels
  • Cross-regional TMPs: for wide-area networks and key corridors covering multiple regions (sometimes an entire country)
  • Cross-border TMPs: for cross-border networks and key corridors between different counties or states / provinces within a large country
  • Conurbation TMPs: for cities and the associated regional highway networks serving long-distance through / transit traffic

Multiple level TMPs, if properly developed, will provide for various traffic situations in a timely and effective manner.

The implementation of TMPs eases roadway disruptions even if the initial event and its consequences are slightly different from the scenarios adopted for the TMP. When a TMP is put into practice the introduction of measures not included in the plan can be initiated by the operator – provided that the new measures are consistent with the spirit of the plan, after agreement with the coordinating authority. Common terminology and an agreed referencing system for key locations are essential for all stakeholders to understand each other clearly. It is essential that everyone has access to the most up-to-date version of the TMP, making version control very important. The wide distribution of TMP documents can lead to different parties working to different versions but this can be avoided if the current versions are held on-line in a virtual library.

Advice to Practitioners

TMPs are produced from historic analysis and a consideration of potential operating measures and agreements between all future partners and stakeholders. After a TMP has been activated and the situation returns to normal, feedback from the experience will help improve the effectiveness or performance of future activations.

The objective of systematic feedback – often called “after-action” analysis – is to enhance the effectiveness of an operating plan or action and optimise use of resources. Past situations are used to review organisational factors, event planning procedures and detailed incident response plans.

To secure feedback to the required level the following measures are recommended:

  • during response to the event or crisis: store as much information as possible by keeping logs
  • after responding to the event or crisis: assemble all the stakeholders to compare experiences and analyse a player’s response to the event or crisis (schedules, time-lines, methods, systems)
  • check the clarity and applicability of instructions
  • check the respective roles of the traffic control centre, traffic police and emergency services and verify the exchanges between them all
  • define changes to be made to plans, response sheets
  • prepare an after-action report summarising the findings and recommendations of the stakeholder meeting(s)
  • ensure that follow-up action is completed

Organising and using feedback is especially important where the operational plan or measure implemented has not previously been applied in a wide-scale exercise or test.

 

Reference sources

EasyWay ITS Deployment Guideline TMS-DG07 Traffic Management Plan Service for Corridors and Networks (2015) Available for download at: https://dg.its-platform.eu/DGs2012

Planning for Road Works

A survey of all planned roadworks will provide important data for the Traffic Control Centre to assess the duration and the time-line of forecast obstructions and develop the least disruptive master plan. This task requires control centre operator awareness and proficient scheduling.

There are some drawbacks and constraints - such as:

  • the need for control centre staff to have training to carry out this work
  • uncertainty in predicting the combined effect of roadworks in more than one location on traffic demand over the wider network
  • uncertainty over actual periods of construction work
  • lack of information on work performed by utilities (water, electrical, telephone and TV cable, gas)
  • difficulty in controlling the time and space taken by roadworks where plans are changed by the contractors
  • difficulty integrating unplanned, emergency work into any plan

The objective will be to schedule roadworks to minimise their impact and reduce disruption to road users, for example by avoiding:

  • multiple work zones in close succession on the same roadway
  • simultaneous work causing disruption on two parallel routes
  • work requiring lane closures during times of peak-hour or peak season traffic

Operations during construction

The goal is to minimise the actual or probable disruption to users caused by major construction works by initiating consideration of:

  • roadwork logistics, layout and design (as far in advance as possible)
  • operating measures to be implemented
  • choice of timing for work, based on traffic flows

The optimum plan for roadworks operations can be developed by progressively focusing on the best approach for executing the roadworks, incorporating safety concerns and traffic flows, and integrating these considerations and the results into the plan.
This requires knowledge of:

  • historical traffic demands
  • residual capacity at the site
  • potential disruptions
  • various potential work techniques
  • opportunities for diversionary routes
  • possibilities for displacing traffic in time and space
  • other potential planned roadwork nearby
  • other major constraints, such as unavoidable periods of high traffic demand

Sometimes several solutions will be available (local detour, alternative routes, alternating open lanes). The choice will be based on total cost, including the cost of work and cost of delays. While work is in progress it is important to check compliance of signalling and operating methods with the content of the operations plan.

Incident Response Planning

A Traffic Incident Management (TIM) team drawn from the leading organisations involved in responding to traffic incidents is useful in many situations. The team can operate as a unit to create the required contingency plans and the related Concepts of Operations (ConOps) – that identify stakeholders and their respective roles and responsibilities in incident management. (See Traffic Management Plans)

An Incident Management Team can be a continuing mechanism for practicing the essential “4-Cs’ of incident management – Communication, Cooperation, Coordination and Consensus – sharing new techniques, training and conducting post-incident assessments. This is done through regular, on-going meetings, perhaps monthly or bi-monthly.

There should be a core group that participates regularly in the continuing activities of the team. Usually this would include:

  • the person(s) responsible for managing the TIM programme nationally or regionally (if there is one)
  • maintenance and operations units in the national / regional or state/provincial transport departments and any local transport counterparts
  • law enforcement agencies
  • fire rescue and emergency medical services
  • mobile Safety Service Patrol provider
  • representatives of vehicle towing services (preferably an organisation, such as the appropriate professional towing association)

If there is a TCC in the region, it will be a core TIM member as well. The TCC may take the lead in forming the TIM Team. Other members would participate as needed. (See Table  below)

To start a TIM Team, there needs to be a lead organisation or champion to bring together the various parties to create consensus on goals and objectives. In addition there will be logistics to consider (including meeting facilities), which include:

  • provide agendas and recording minutes
  • notifying members of meetings
  • arranging for special presentations
  • training and other team activities

It is generally best if the TIM team champion comes from a public-safety agency, perhaps law enforcement, to encourage colleagues in other public-safety agencies to participate actively.

Effective strategies include promoting the adoption of an “Open Roads Policy” that sets a goal to clear the roadway and open the lanes to traffic as quickly as possible, for example within 90 minutes of the arrival of the first responder (the first official to respond to the scene and render assistance, such as a the police or a safety service patrol).

Some agencies’ delivery of the Open Roads Policy includes the local police and fire rescue departments and the Coroner/Medical Examiner’s Office. The Coroner’s involvement is helpful since it can grant authority to responders to remove fatalities from the roadway providing certain conditions are met (such as taking digital photographs). This avoids any delays in clearing the roadway, arising from having to wait for the Coroner to arrive and direct the removal.

Traffic Incident Management Teams in USA

In the USA members of the TIM Team are drawn from a wide range of stakeholders. Some, such as national agencies, serve more in an advisory role than an active role. Some localities also have a regional TIM Team to provide broad-based, and standardised training, and information sharing. An example is the Traffic Incident Management Enhancement (TIME) Task Force in the greater Atlanta, Georgia, USA.

See: http://www.timetaskforce.com/about-us/mission

 

Potential Stakeholders in a Traffic Incident Management (TIM) team

Category

Stakeholder

National Agencies 

  • National Road / Highway agency
  • Emergency management agency
  • Commercial Goods Vehicle Safety and Licensing agency
  • Defence and Security agency
  • Regional Agencies

Regional Agencies

Regional Department of Transportation (DOT) including as a minimum the following departments:

  • Traffic Engineering/Operations
  • ITS Team
  • Traffic Planning
  • Highway Maintenance
  • Road Safety Team
  • Commercial Vehicle Inspection Office

Sometimes the DOTs for adjacent regions are included:

  • Agency for Environmental protection
  • Ministry of Interior (for emergency management)
  • Law enforcement communications/dispatch centres
  • Emergency Operations Centre
  • Regional public transport agency
  • Regional emergency organisations

Local Agencies

  

  • Law enforcement (police and constables)
  • Fire rescue
  • Emergency Ambulance and Medical Services
  • Mobile Traffic and Safety Service Patrols
  • Metropolitan Planning Organisations
  • Medical Examiner/Coroner
  • City and region public works and traffic engineering
  • Emergency Operation Centres
  • Regional Emergency Control Centre
  • Public transport agencies

Authorities

  • Toll-road Authorities
  • Transport authorities
  • Regional operating organisations

Private Partners

  

  • Towing and recovery operators
  • Hazardous Materials contractors
  • Insurance industry
  • Information Service Providers (ISPs)
  • Traffic media

Associations

  • Professional towing/breakdown associations
  • Technical and Professional societies (including ITS)
  • Automobile associations
  • Chambers of Commerce
  • Associations of Cities, Local Authorities, Police,
  • Emergency Medical Services

Other

  • “Better transport” organisations
  • Citizens’ groups
Reference sources

American Trade Initiatives (2006) Traffic Incident Response Practices in Europe Report No. FHWA-PL-06-002, US Federal Highways Administration Washington D.C. http://www.dot.state.fl.us/trafficoperations/ITS/Projects_Deploy/PerfMeas/presLindley052305.pdf.

Planning for Emergencies

Traffic incidents occur all the time. Events that are more serious in nature are commonly referred to as “emergency events”. Emergency Management brings together different stakeholders to respond to, and manage, emergency events.

Emergency events include events of which there is little or no advance notice – and known events for which the impacts are largely unpredictable – such as a hurricane/typhoon/cyclone. (See Security Threats)

The scope or severity, of incidents is a continuum along which the responders and managers change and the team expands according to the severity of the event. The diagram below illustrates this continuum. Whatever the severity, first-line responders generally include law enforcement, fire rescue, emergency medical services, vehicle breakdown and recovery teams – and in the transport community, the road authority’s maintenance teams and mobile Safety Service Patrols. The TCC will be involved throughout as well. The involvement of agencies providing oversight and support will change as the severity increases – to include other stakeholders such as emergency managers, state and even national agencies. (See Incident Response Planning)

Normal practice is to designate an Emergency Coordination Centre from amongst the first-line responders. Often the Traffic Control Centre is well-placed to take this role. Where possible, the demarcation and allocation of responsibility for public statements, policies on the use of social media and press briefing – for different kinds of emergency, needs to be worked out in advance between those with a close interest.

 

Complexity of different types of Emergency Operations

Complexity of different types of Emergency Operations

 

Scale of the Response

A meaningful way to view this is to consider the degree of public preparedness for the levels of incidents compared with state and national preparedness. Typical types of incident for different levels of severity are shown in the Figure below.  The term “incident” applies to all levels of severity but the agencies involved and extent of their response varies and increases from the side to the .

Classification of Incidents based on Coodination Complexity and Level of Public Preparedness

Classification of Incidents based on Coodination Complexity and Level of Public Preparedness

The task of planning for major emergencies - the Regional/ State/National events shown in the diagram above – can be broken down into different stages:

  • definition of types of disruptions and situations likely to deteriorate into a crisis
  • identification of partners involved in handling each type of disruption
  • joint definition of missions delegated to each service and development of automatic response sheets or – for complex cases – a traffic management plan
  • definition of staff to be provided for each service, during and after operating hours
  • review of the organisation of communications (always a key factor in crisis management)
  • design of the decision-making organisation, coherent with the institutional framework and designation of an Emergency Coordination Centre
  • validation of the operational organisation by all partners
  • training of the officials in crisis response (their role and communications, in particular)
  • exercises to test the organisational arrangements and procedures, and to train staff

During the Emergency

During an emergency situation the Coordination Centre or other lead organisation has various important tasks to perform:

  • evaluation based on information received and discussions with the operational partners
  • implementation of measures that are well-planned or rehearsed, or a real-time search for new appropriate measures
  • centralisation and control of communications with road users and information service providers to avoid releasing confusing or contradictory information and to ensure all media carry current information
  • regular exchanges of information between operating partners to ensure crisis monitoring and the implementation of coordinated traffic management and road information measures
  • keeping a log within each organisation and particularly within the Emergency Coordination Centre (for debriefing and in the event of legal problems)

Advice for Practitioners

After the emergency has passed it is important to obtain feedback on the experience and information on any operational difficulties in order to update incident response plans:

  • hold a debriefing meeting with key players and prepare a record of the meeting as quickly as possible after the crisis
  • record any proposals to change the organisation of services for more effective response to future crises
  • update and improve traffic management plans and crisis management documentation

At the national level in the USA, Federal Highways Agency has brought Emergency Management to the forefront through its Emergency Transport Operations (ETO) Programme. (See http://www.ops.fhwa.dot.gov/eto_tim_pse/index.htm)

All incidents in the USA even minor traffic collisions are subject to National Incident Management System (NIMS) procedures – albeit usually on an informal basis. (See http://www.fema.gov/national-incident-management-system)

Reference sources

Wallace C. E. et al. (2010) Surface and Transportation Security, Volume 16, A Guide to Emergency Response Planning at State Transport Agencies US Transportation Research Board. Washington D.C.

Lockwood, S., J. O’Laughlin, D. Keever, and K. Weiss (2005), Surface and Transportation Security, Volume 6, Guide for Emergency Transportation Operations NCHRP Report 525, US Transportation Research Board. Washington, D.C.

Performance Measures

The need for Performance Measures in Road Network Operations (RNO) is widely recognised. They have been a topic of discussion for many years but it is only recently that ITS devices provided the data necessary to support performance measures and their importance in RNO. (See  Performance Indicators)

ITS can play a major role in performance measurement and will be useful to countries that do not already have strong road network performance management programmes. Performance management is important to ensure that:

  • the transport agency achieves its goals and objectives
  • systems deployed are cost effective
  • managers and operators get feedback so they can assess how effective their actions have been and what changes may be needed to their plans
  • the return on investment is positive in terms of road-user benefits
  • performance measurements are consistent across the country, or even regional group of nations, if appropriate
  • performance measurements are increasingly outcome-based rather than output (production)

Possible categories of performance measures relevant to RNO include:

  • performance of the strategic highways viewed from the operational perspective (not strictly physical condition) – for example, measures of journey time reliability
  • traffic incidents – collisions/incident rates and the incidence of secondary collisions
  • incident severity – for example incident duration, numbers killed and seriously injured
  • traffic congestion – for example an ITS-based measure reflecting accumulated traffic delays
  • on-road mobile source emissions – using environmental sensors as the data collection mechanism
  • freight movements on strategic highways
Examples of RNO Performance Measures

Traffic Incident Management

A USDOT scanning tour of four European nations (England, Germany, Sweden and the Netherlands) in 2005 found a strong interest in performance-based Traffic Incident Management. Performance measures are applied in various ways, to monitor:

  • progress in reducing fatalities and serious injuries (England)
  • response time as the basis for location of fire station and Emergency Management Services - and for resource allocation on a local or regional basis (Germany and the Netherlands)
  • response time as the basis for towing and recovery contracts (the Netherlands)

Levels of Service to Road users

The following are being considered for the USA:

  • travel-time reliability (buffer index) – the buffer index is the additional time that must be added to a trip to ensure that travellers making the trip will arrive at their destination at, or before, the intended time, 95% of the time
  • extent of congestion – spatial (also measurable by time) - miles of roadway within a predefined area and time period, for which average journey times are 30% longer than unconstrained journey times
  • incident duration – the time elapsed from the notification of an incident until all evidence of the incident has been removed from the incident scene
  • customer satisfaction – a qualitative measure of customers’ opinions related to the roadway management and operations services provided in a specified region

 

Reference sources

American Trade Initiatives (2006) Traffic Incident Response Practices in Europe Report No. FHWA-PL-06-002, US Federal Highway Administration, Washington D.C. http://www.dot.state.fl.us/trafficoperations/ITS/Projects_Deploy/PerfMeas/presLindley052305.pdf

.

Mobile Safety Service Patrols

Traffic Officers and Mobile Safety Service Patrols (SSPs) are an important element of road network operations programmes in some countries. Transport agencies are using ITS-type systems to help them improve the efficiency of these operations.

In Europe, Asia and South America it is common for the Automobile Clubs or commercial insurance-related services to provide roadside services, such as changing flat tyres, providing a small amount of fuel, and jumping batteries. Many toll roads (also known as Road Concessions) are legally obliged to provide these services and in many cases within very tight time restraints.

Publically operated Mobile Safety Service Patrols are also deployed. Initially they were usually purely “service patrols,” providing limited roadside assistance to vehicles having difficulty – similar to the automobile club services. Today their responsibilities have expanded. For example Traffic Officers in the United Kingdom have the authority (defined in UK law) to control the traffic flow during traffic incidents and emergencies. Their responsibilities include:

  • dealing with abandoned vehicles
  • removal of damaged / broken down vehicles
  • providing mobile or temporary road closures
  • clearing debris and animals to make the road safe
  • deployment of Emergency Traffic Management (ETM)

Traffic Officers have also taken on other services on behalf of the Road Authority such as:

  • escorting abnormal loads
  • monitoring roadworks
  • assessing roadway asset condition and defect identification

Mobile Safety Service Patrols can now push or pull vehicles from the roadway (if permitted by law), secure and clean up minor vehicle fluid spills, set up temporary traffic controls (such as, traffic cones and flares), perform minor repairs to stalled vehicles, provide information to travellers via truck-mounted Portable Dynamic Message Signs, provide “protection” for the back of the queue and assist injured passengers. Some mobile patrols use sophisticated mobile Personal Digital Assistants (PDAs) to log the “stops” they make for both efficiency of documentation and for immediate transmission of incident data to a TCC.

Whatever their mission and capabilities, the operators’ top priorities are ensuring the safety of themselves and impacted motorists before clearing the roadway. Mobile Safety Patrols are first responders and complement the role of the law enforcement agencies. The first priority of first responders and others who work on the roadway is again, the safety of themselves and road users –above all other activities. The greatest challenge for managing risk is that with time, road workers tend to accept greater risks. This requires constant re-training.

Mobile Safety Service Patrols (UK)

In UK “Traffic Officers” are mobile patrols whose job it is to keep traffic moving at all times. Their role on behalf of the road authority is complementary to the Traffic Police but without replace the police responisibity for law enforcement. In UK they have specific powers to direct traffic but not to enforce the traffic law. Associated with these functions are a set of key operational capabilities and performance indicators. For example:

  • Primary response to any incident on the roadway shall be no more than 20 minutes during core operating hours

Traffic Officers deal with the road user as a customer. They work alongside the traffic police and other emergency services (ambulance, fire brigade and vehicle breakdown). The police retain full responsibility for dealing with public security, law enforcement and criminality.

Legal Powers of Mobile Safety Service Patrols (UK  England & Wales)

Legal Powers of Mobile Safety Service Patrols (UK England & Wales)

 

Travel Information Systems

Authors  John Miles (Editor)  Keith Keen (Assistant Editor) Charlie Wallace  (Courage & Wallace, USA)

Uncertainty over journey and arrival times is a major problem for travellers and companies delivering goods. ‘Smart’ travellers and fleet managers increasingly expect reliable information to help them make well-informed decisions.

Accurate, integrated and comprehensive travel and traffic information helps all road users in their journey planning decisions and how to respond to disturbances that occur on the way. In this respect it supports the task of the road network operators as well.

Travel information – and by extension route advice – is considered to be a basic service. It constitutes the lowest level of traffic management. Road users are free to decide for themselves if and how to react to the information or advice.

Investment in travel information systems by the road operator is a way of improving customer service. Information systems can also promote intermodal travel, for example by encouraging drivers to leave their cars at a Park and Ride site (typically because of localised congestion or high pollution levels ahead) and continue by public transport. Parking information systems also contribute significantly to reducing city-centre congestion and pollution by alerting approaching drivers to available spaces.

Traffic information concerns the conditions of road network use and can include predictive and current (real-time) information on traffic conditions. Stronger forms of direction include hazard messages or incident warning, and eventually control measures such as notice of road obstructions, lane control, or speed control.

Traveller aid covers all measures to disseminate predictive or current information on traffic conditions and to improve general conditions of network use. Its general aim is safety and user comfort.

Travel aid tasks are not specifically aimed at modifying traffic flows. However, when used for information purposes they must be closely coordinated with traffic management measures as they may induce users to change their travel time, route or mode of transport. In this context, they may be integrated in broader strategies related to demand management.

Basic Principals

Generation of travel information by the network operator is a broad concept that cuts across the entire field of operations and entails several areas:

  • gathering regular information from operational partners
  • providing user information on predicted traffic conditions (before trip) or current traffic conditions (on trip)
  • the contribution user information can make to the operator’s communication policy and to the user relationship
  • road and traffic information as an important element for public transport, freight and fleet management operators

To be able to inform partners and drivers effectively, operators must first define information paths that should be coherent with the operation and management plans.

To fulfil the needs and expectations of everyone involved, the information should be timely and disseminated via all available channels and communication modes. They can be channels operated directly by the control centres (variable message signs, travel information website, RDS-TMC, traffic news broadcast etc.) or by added-value service providers who transform the information into the required data formats for smart phones and satellite navigation, and/or operate additional dissemination channels themselves. (See  Traveller Services)

Provision of client-specific, personalised (enriched) information is often let to independent, value-added service providers, who extend and build on the information stream made available by the road operator. However, there should be an agreed framework for safety-related advice and direction in the absence of specific instructions from the traffic centre, in order to avoid confusion or the undermining of the set traffic policy.

RNO Information Systems

The purpose of this approach for the road operator is to achieve widespread, timely information dissemination to operating partners or road users, as required. This action involves listing all components of the information system, identifying blockage points and organising or reorganising the information chain to ensure the system functions effectively. (See  Systems Approach)

Successful dissemination of information is the end result of a system in which each link is crucial to success, so the operator must ensure that each link functions effectively:

  • data gathering system must be adequate and reliable
  • during operations, information systems must be reliable and capable of forwarding data and information on time:
    • substitute or back ups systems may be necessary for network security or emergency response
    • data gathering and information dissemination paths may also differ depending on circumstances (crisis situation)
  • at staging points, information must not be unduly delayed – a person must be identified and available each time an action has to be performed (such as verification of information received or development of information for transmission)
  • at switching points, information must be forwarded as quickly as possible to the correct location

Computers can be used to automate all or part of the actions described above. (See ITS & Network Monitoring)

When information for users is relayed by an intermediary – especially the media – operators must listen to and/or read the messages actually sent by the intermediary, noting the date and time sent, to assess the quality of communication.

An information system is more effective when all players involved have a good overview and a clear understanding of their role. The quality of information received by users is very closely linked to the actual systems and can actually enhance the department’s image.

Objectives and Methods

The common objective of all traveller information services is to provide high quality, real-time, detailed information on transport operating conditions, including weather, so that individual travellers can make informed decisions regarding whether to make a trip, when to make it, what mode to take, and what route to take. Traveller information should be available both before a traveller begins a trip, as well as while the trips are under way, so that adjustments can be made to reflect changing operational conditions.

Traveller information can be provided in a number of ways. A summary is provided here.  (See also Traveller Services and Driver Support)

In recent years the Internet has become ubiquitous as method of conveying pre-trip traveller information. Some systems offer subscribers the option of receiving alerts by mobile phone, e-mail, or other electronic methods regarding major incidents or conditions on specific routes. Telephone dial-up services remain a popular means of pre-trip and en-route information dissemination. Commercial broadcast media, including radio, cable television, commercial television, and teletext services are other commonly used methods of dissemination of travel information.

Telephone: In the United States, a nationwide three digit telephone number, 511, has been designated for traveller information services. The success of this initiative lies in issues such as the perceived accuracy, timeliness and permanent operation of the 511 service. Also, because of the variety of organisations involved (geographically, public/private, different travel modes), the issue of co-operation is the other challenge. The success of this initiative shows that appropriate institutional agreements, when designed early enough in the development process, can be a powerful lever to deploy effective ITS operations services. (See Journey Planning)

Driver information systems: by means of roadside VMS or in-vehicle units, contribute generally to a better performance of the traffic system by raising the level of awareness of drivers about the current status of the network and its likely evolution. Users of traveller information services generally agree that availability of high quality, real-time traveller information saves time, helps them to avoid congested locations and incidents, and reduces uncertainty and stress associated with travel. (See En-Route Information)

Variable Message Signs (VMS) are used to disseminate en-route traveller information in virtually all locations where electronic traffic monitoring also exists. These signs are typically placed in advance of key bottlenecks or decision points and can display fairly detailed information on location and extent of congestion, travel times, alternate routes, and downstream weather conditions (for example wind, precipitation, snow). (See Use of VMS) Highway Advisory Radio is also used, although its use appears to be declining with the growing popularity of traffic-responsive satellite navigation units and smart phone applications, which are now widespread. (See Radio)

In-vehicle navigation: En route information provided through in-vehicle navigation systems and smart phones is spreading. The VICS system in Japan, which enjoys a high market penetration of in-vehicle navigation systems, is one of the most extensive applications. Dissemination of detailed en-route information is accomplished through transmission from beacons or FM sub carrier broadcasts to the in-vehicle device. Other countries have followed Japan in deploying this kind of system. (See Advisory Systems)

Subscription services: Pre-trip and en-route information alerts provided through social media, messaging subscription services (Internet and Smartphone) is growing in popularity.

Information terminals and kiosks: Pre-trip traveller information in kiosks located in employment centres and other public places (e.g. freeway rest areas and shopping malls) are becoming commonplace, although the experience with kiosks this dissemination method has limited utility for real-time road information. Use of kiosks for public transportation information appears to be more successful. Real-time public transportation information is also successfully disseminated at transit stops in many locations using electronic signs. (see Kiosks)

Information Requirements

Information requirements are set by network operations stakeholders, transport operators, emergency services or assistance providers and road users themselves – the latter possibly clustered in Motoring Clubs and Road User Organisations. As might be expected, there can be some variety in the geographical extent and the level of detail of the information these players need in support of their activities, or to really fulfil their travel needs.

Predictive information: This information may be on a weekly, daily or even hourly basis and concerns general traffic condition forecasts and the main anticipated disturbances. Its implementation requires:

  • real-time centralisation of information on the network situation (traffic, weather) and on scheduled actions (roadwork, events)
  • transmission of regular information bulletins through national or local media (radios, newspapers, television), or specific road information facilities (kiosk, telephone enquiry service and Internet)

Real-time information: This information concerns the currently-experienced traffic conditions and disturbances affecting motorists on a given route. It requires:

  • a permanent system to detect and monitor traffic flow conditions
  • real-time information systems by variable message signs installed along the route, by specialised radios or by ITS servers. It may be necessary to have specific in-vehicle equipment to receive some of the information

Real-time information also includes information to operators of customised services or navigation and guidance systems.

Information Quality

High quality traveller information services must be driven by high quality data on transportation system conditions and performance. Effectively fusing data into useful information from various input sources is a significant challenge that is critical to overcome if traveller information services are to be effective.

For systems that automatically post or otherwise provide traveller information based on input from traffic monitoring systems, data reliability is a critical issue. Effective automatic means of checking or filtering raw data must be in place to ensure that erroneous or misleading information is not posted.

In order to be useful to travellers, traveller information needs to be multi-modal (road and transit), and regional (crossing jurisdictional boundaries) in scope and include information about motorways and urban streets, as well as location and availability of parking.

Travellers are interested in receiving end-to-end trip information in a single query. The objective for end-to-end travel planning involves links to intercity travel providers, such as rail and air lines, to provide complete travel and routing information, door-to-door. Future enhancements for end-to-end travel may include linking to intercity travel providers, such as rail and air lines, to provide complete travel and routing information.

Information provided by traveller information services must be immediately beneficial to the user in making travel decisions. Advising travellers through a variable message sign that there is “Congestion Ahead” on the network has little value if not supplemented by information on location, extent, and severity of the congestion and potential alternate actions.

It is important to maintain the accuracy of the information provided. For example, VMS which frequently show incorrect or no information will lose the trust of road users. This will defeat the whole purpose of the system. To ensure accuracy the issue of interconnections between the various centres must be addressed, if they are separate either in terms of the services that they provide or their locations. The seamless integration of information exchange between various centres becomes a major issue. This requires the adoption of a standard for data exchange and cooperation between the various players.

Commercial Services

Though there is significant private sector involvement in many examples of traveller information services, the commercialisation of traveller information for profit is variable. Traveller information services that have been financially successful have generally involved packaging traveller information along with other information. (See  Location Based Services)

For traveller information services to be successful, they must be marketed to potential users on a continuous basis. This marketing should be tailored to various market segments (such as road users, transit users). Successful traveller information services also seek customer input on services offered and are responsive to feedback received. For example, VICS of Japan continually solicit user requests and demand through the Internet, in order to better accommodate their needs.

Though not widely provided at the moment, users are interested not only in real-time information on network conditions but also in predicted conditions (for example: “a key junction is currently uncongested, but if the current trend continues, what will conditions be when I reach the location in 30 minutes?”). This will be the next important development in traveller information services.

 

Information Exchange

Information transmitted must be adapted to the expectations of recipients so it can be used effectively. The information must be clear, understandable and useful to end users. Information that reaches its recipient is the end result of any initiative that answers the following questions:

Is the information accurate? The facts to be conveyed must be accurate or all credibility with partners/users will be lost.

Why provide information? Dissemination of information reflects intent by a operator that must be specifically defined – for example:

  • to provide the recipient with necessary or useful information
  • to elicit from the recipient an action that will be useful to the operator himself
  • to modify driver behaviour, promote safety, prevent or minimise operating problems and give drivers a sense that they are taken into consideration

Who should be informed? The targets for information may be police forces, other road operators, local or national media and the road users themselves. Who should be informaed will vary acording to:

  • the characteristics of the situation (circumstances such as the nature, gravity, location, context, anticipated length of current disruptions, and the timeline of planned events) 
  • the network operator’s intention  – in answer to the question "Why porvide the information?"

When should information be provided?  Information about a current event is of interest to a recipient/users only if the users have it in real time. Choosing the time to send information about a planned event is not easy. This must be done early enough to allow for a response (especially if the operator expects cooperation from partners) but not so soon that it will be forgotten.

Where should information be provided? The destination of information (for example at a control centre, TV and radio stations, emergency servcies or a service provide) is defined by the network operations strategy and will be an integral part of operations planning. (See Planning and Reporting)

How should information be delivered? The information medium (social media, text message, Intenet, telephone, radio, e-mail, VMS’s, leaflets) is also determined by what is most cost-effective and the available resources. (See  Traveller Services)

How should information be presented? Each recipient or group of recipients must receive the information in a personally tailored format. If there is a common language (event nomenclature, location, etc.), a message drafted in technical or even coded terms may be understood by a partner. To be legible by a partner, that message must not be buried in a lot of irrelevant details. For example:

  • traffic forecasts in the form of raw data on flows can be easily interpreted by a freeway operator
  • road users need information that is directly relevant to the route, timing, mode and location to their journeys
  • a message sent to a media outlet must be adapted to the practices of that outlet

Communicating Information

Messages to users must follow the guidelines below:

  • capture the recipients’ interest;
  • use their vocabulary, not operators’ jargon;
  • avoid giving them the impression they are being manipulated;
  • provide explanations wherever feasible;
  • indicate the source of information whenever possible.

It is usually very practical to use forms for exchanging information that has been defined in advance with the partners in question. Where they exist, standards for data exchange should be used.

Communicating is as much of an art as operating the road network. Network operators should:

  • identify staff responsible for presenting information and train them in media operating methods and drafting messages on VMS;
  • canvass at least a few users (not co-workers) to ensure that the planned wording will be clearly understood and will not raise additional questions (VMS message, radio announcement);
  • Make use of communication specialists to design a website or leaflet, for example.

Disseminating information to users entails drawbacks and constraints:

  • the operator needs to monitor the consistency of messages issued consecutively or simultaneously through various media;
  • operators have no control over the final form and timing of release when information is channelled through an intermediary;
  • foreign users may not understand the local language.

Advanced Traveller Information Systems (ATIS)

Road Network Operators and other transport or public safety professional have no direct control over road users (except, perhaps, at traffic signals). Each road user is an independent entity that observes situations from the perspective of his or her specific needs, does their own thinking and decision making and executes their decisions more or less independently. The only thing the transport profession can do is to inform the travellers in the best possible manner to enable them to make informed – and hopefully safe – decisions. (See Traveller Information Systems )

Use of VMS in Florida, USA

A survey by Florida DOT District 6 (Miami-Dade Co. and south) found that 92% of freeway/turnpike drivers read VMSs at least weekly, 97% said these signs provide accurate traffic alerts, and 78% reported a willingness to alter their route based on VMS postings. Use of 511 increased in the past year and 22% of respondents were more willing to change their departure time as a result of 511 information.

(Source: Rodriquez, J., “Miami Drivers Reported Travel Benefits from Using Dynamic Message Signs,” SunGuide® Disseminator, Florida DOT, January 2013.)

Advanced Traveller Information Systems, or ATIS are designed to support individual decision-making. The goal of ATIS is for travellers to have information at their disposal to help them make better-informed travel decisions about mode, route, departure time and activity choices. A side effect of these better decisions can often be supportive of efficient and safe traffic operations.

There is a full range of advanced traveller information provider systems and services. A summary is given in th table below along with advantages and disadvantages (in no particular order):

Characteristics of Traditional Traveller Information Techniques

Technology

Advantages

Disadvantages

Posting of messages on VMSs

  • Point and advanced information to the most-affected drivers

  • Efficiently changed

  • Modern full-matrix signs can use graphics and colour to enhance messages

  • Ideal for child-kidnap alerts in a corridor

  • Doesn’t reach drivers off the roadway

  • Fixed location

  • Old signs difficult to read

  • Not always widely trusted

  • Not always read

Posting of messages on PDMSs

  • Point (and possibly advanced) information to most-affected drivers

  • Can be deployed to unplanned situations/incidents

  • Takes time to deploy for unexpected events

  • Not efficiently changed (unless remotely controlled)

  • Sometimes difficult to read

511 (voice, automated)

  • Widely available

  • Efficiently updated

  • Widely accepted

  • Can be accessed en route

  • Can be (partially) financed by sponsorships or advertising

  • Must be proactively accessed

  • Encourages phone use while driving

  • Language issues, particularly in Interactive Voice Recognition (IVR)

Call taker

  • Highly responsive and effective

  • Personalised

  • Less used today, but popular where they are

  • Encourages phone use while driving

  • More expensive than IVR

Website (TCC or 511)

  • Widely available

  • Efficiently updated

  • Can be automated (such as speed maps)

  • User can view selected CCTV images

  • Can be partially financed by sponsorships or advertising

  • Widely accepted

  • Not universally accessible; must be proactively accessed via computer or mobile device

  • Encourages mobile device use while driving

  • Language issues

Media – radio traffic reports

  • Widely available

  • Can be efficiently updated

  • Widely accepted (many users say this is their primary mode)

  • Can be accessed en route

  • Financed by the media

  • Must be proactively accessed

  • Always maintaining timely and accurate information

Media – TV traffic reports

  • Widely available

  • Can be efficiently updated

  • Can show station-selected CCTV images

  • Widely accepted (many users say this is a primary mode)

  • Can be accessed pre-trip

  • Financed by the media

  • Must be proactively accessed

  • Always maintaining timely and accurate information

  • Not available en route

Airborne spotting and reporting

  • Widely available

  • Agile relocation

  • Efficiently updated

  • Widely accepted

  • Can be accessed en route

  • Financed by the media in some regions

  • Must be proactively accessed

  • Getting timely air time for incidents (unless it is a continuous traffic reporting station)

Kiosks and display signs

  • Popular with older, less tech-savvy and disabled users

  • Provides peace of mind for transit riders

  • Transfers/connection information for transit users

  • Limited availability (for example, transit terminals, rest stops and other fixed locations)

  • Timely and accurate updates

In recent years, the proliferation of smartphones and other mobile devices (such as digital tablets and pads), the expanding use of social media and the increasingly wide-spread use of Floating Vehicle Data collection techniques have led to a number of truly advanced traveller information services. Some services collect data to be used by other traveller information providers.The Table below summarises these.

Characteristics of Advanced Traveller Information Techniques

Technology

Advantages

Disadvantages

Point (that is, fixed location) data collection systems

  • Passive, non-intrusive and non-threatening

  • Reasonably accurate for journey times and inferred speeds

  • Requires additional infrastructure deployment

  • Usually must funnel processed information through public or private entity at a cost

Floating (probe) vehicle tracking

  • Ubiquitous supply of probes

  • More easily deployed in rural areas and areas not covered by ITS

  • Useful for incident detection in such areas

  • Some concern for privacy issues

  • Requires additional infrastructure deployment

  • Must funnel processed information through public or private entity at a cost

Commercial traveller information services

  • Use a variety of data sources, including floating vehicles

  • Feeds data to navigation maps in near real time

  • Navigation maps show alternative routes

  • Can direct information to subscriber via mobile phone (voice or text) or social media

  • Well trusted

  • Sometimes paid by subscription

  • Encourages mobile phone or mobile device use while driving

Social media – situation reporting

  • Expands number of eyes on the roadway
  • Free for all users
  • Increasingly used by traffic and emergency managers to inform travellers about incidents and emergencies
  • Encourages cell phone or other mobile device use while driving

E-mail alerts

  • Low cost
  • Highly customizable
  • Paid by subscription
  • Not as effective for en -route alerts

In-vehicle telematics (including personal navigation devices)

  • Expanding market
  • Combines advantages of several techniques
  • Great potential for growth beyond simple traveller information
  • Paid by subscription
  • Demonstrated, but not widely deployed beyond Europe
  • Marketing and software integration issues
  • Standards among regions

 

Pre-trip information

Using radio and TV traffic reports, websites, navigation maps and Information Service Provider (ISP) feeds to enable travellers to change their travel mode, change the trip departure time or change the route of the trip, all to avoid an incident or just normal congestion, thus reducing traffic demand in the affected area. Further information on pre-trip information is provided here (See Pre-Trip Information).

En-route information

En-route information can be provided though VMS, radio traffic reports, (in Europe the RDS-TMC, Radio Data System – Traffic Message Channel), GPS (Global-Positioning System) or GALILEO navigation maps and Independent Service Provider feeds to a smartphone. The information can assist travellers, including drivers of passenger and freight vehicles, to change their trip plans whilst en route, for example by changing their route or even abandon the trip to avoid an incident or just normal congestion. This reduces traffic demand in the affected area. Even if a traveller does not change any trip plans, just knowing the nature of congestion, perhaps with some indication of journey time or incident location, can reduce driver frustration and anxiety, thus making them safer drivers that are less prone to take unnecessary chances, such as excessive lane changing.

VMS and Highway Advisory Radio (HAR) are used to alert rural travellers in mountainous areas about weather and other conditions on the roadway ahead.

En-route information during longer trips

On long-distance or international trips, applications like those mentioned above (as applicable) or kiosks at rest areas, can help these long-distance travellers either adjust their trip plans or at least have a more secure feeling about their trips. (See Kiosks)

Traveller information in the other modes can do such things as inform public transport passengers of the arrival of the next vehicle and provide transfer information. Whilst these do not directly impact traffic operations at that time, this type of traveller information makes travellers more comfortable and confident about using public transport, thereby encouraging them to continue to do so and not add to clogging the roadways with more cars. Some Integrated Corridor Management (ICM) concepts include public transport as well, particularly Bus Rapid Transit (BRT) systems.

Traveller information can also provide information that does not directly affect current travel, but serves other purposes, such as safety messages, smog alerts and for child-kidnapping alerts. Note that there is some debate about the use of VMSs and HAR for non-mission-critical purposes. (See En-route Information)

Managed lanes and Toll Roads

High-occupancy/toll (HOT) pricing is conveyed by VMSs, allowing Single-Occupancy Vehicle drivers to make a decision to use the HOT lanes, thus relieving demand in the general-use lanes. Similar information should be provided in the case of variable toll rates based on congestion so as to allow a driver to select an optional route.
 

Advice to Practitioners

There is a great deal of potential benefit that can be derived from using third-party data services (for example, real-time journey times on VMS, website traffic information, conducting historical analyses and so on). A number of commercial traffic Independent Service Providers (ISPs) provide services to both individual travellers and businesses as follows:

  • local radio provides traffic information in most metropolitan areas
  • navigation data to in-vehicle devices in a number of areas
  • probe vehicles are providing incident data
  • real-time, historical and predictive traffic information for many USA cities
  • traffic flow data, incident data and construction data in a number of areas

Further information: See Travel Information Systems and Traveller Services

 

Reference sources

The following report has an excellent analysis of the ATIS market in the USA.

Kandarpa, R., J. Sangillo, L. Burgess, and A. Toppen, "Real-Time Traveller Information Market Assessment White Paper," FHWA-JPO-10-055, February 2010.

Other state-of-the-practice reports on traveller information in general can be found at http://ops.fhwa.dot.gov/travelinfo/resources/publications.htm, and in particular business models at http://ops.fhwa.dot.gov/publications/rtis_busmodels/index.htm.

 

Use of Variable Message Signs

Variable Message Signs (VMS) are capable of displaying pre-defined or freely programmable messages which can be changed remotely with individual pixel control. They consist of:

  • large general-purpose panels which allow the display of a variety of text messages and sometimes pictograms. Cost considerations mean these tend to be used on motorways
  • or smaller dedicated panels to display a dynamic speed limit or a specific message
DMS, VMS or CMS?

A Dynamic Message Sign (DMS) is any sign or graphics board that can change the message (text or pictogram) conveyed to the viewer. It may be either a Variable Message Sign (VMS) or a Changeable Message Sign (CMS) where:

  • VMS is a sign capable of displaying pre-defined or freely programmable messages which can be changed remotely with individual pixel control
  • CMS is a sign capable of displaying pre-defined fixed messages which cannot be changed remotely

See Roadside DMS  

Roadside and overhead VMS are a basic traffic management tool for road owners and authorities – to provide information and advice to drivers and riders independent of any in-vehicle systems. In some cases VMS signs can replace fixed roadside signs to inform drivers of speed limits – if necessary with the flexibility of changing mandatory speed limits in response to traffic or road conditions where the legislation allows.

Research evidence shows that road user acceptance and compliance is substantially increased when the reason for a new, lower than normal, speed limit is displayed on the VMS in addition to the prevailing speed limit.

Hazards and Advisory Speed Limits

VMS can be used to convey maximum advisory (non-mandatory) speeds — to advise drivers and riders to slow down in fog, high winds and icy conditions or on the approach to an incident or slow-moving traffic ahead.

Icy Road Warning System in California

Evaluation of an icy road surface warning system installed on a mountain road in California indicated that, when the warnings of icy conditions were activated, mean speeds were more than 5 mph (8 km/h) lower than when no warnings were shown (Veneziano and Ye, 2011). In specific situations where ice was present but not likely to be expected by drivers (such as cold, clear and not-dry conditions), the reduction in speed was somewhat less — under 3 mph to around 3 mph (4.8 km/h). The speed data was collected at the VMS sign – rather than in the subsequent curve where the driver response may have been greater.

Fog Warning System in the Netherlands

A fog-warning system on the A16 in the Netherlands had two levels of lower speed limit available, depending on the level of visibility. It was found that when the system was activated, average speeds decreased by 9-10 km/h. When the very low visibility speed limit was displayed, average speeds were higher than appropriate for the road conditions indicating that the advisory speed limit of 60 km/h was not low enough to influence driver behaviour sufficiently.

Dynamic Speed Limits

Dynamic management of speed limits in response to traffic flows has been shown to reduce speed variability and smooth flows, reduce numbers of accidents and increase overall throughput. It also has environmental benefits through the reduction of emissions. It is mainly applied on motorways. When used in construction zones or for temporary narrow lanes, the safety impacts are considerable, particularly as regards the protection of roadside workers. Dynamic speed limits are often combined with camera-based speed enforcement. (See Work Zones)

Feedback to Drivers

Roadside VMS is commonly used, particularly on urban roads, to inform drivers that they are speeding in the hope of encouraging them to slow down. These VMS are linked to speed detectors. When triggered by a speeding vehicle they display the speed limit or a message such as “Slow down”. The devices can also be mounted on a trailer for portability – for use, for example, in work zones. Portable Dynamic Message Signs (PDMS) have been shown to have an effect on the proportion of drivers speeding and on average traffic speeds. Some of that impact may be a novelty effect — since few evaluations have looked at the persistence of changes.

Managed Motorways

“Smart” or “Managed” motorways are becoming more common as a means of managing high traffic flows on motorways. (See for example http://www.highways.gov.uk/our-road-network/managing-our-roads/improving-our-network/smart-motorways/).

Typically, as traffic builds up towards the critical 2,000 vehicle per lane per hour, speed limits are reduced. The aim is to reduce speed variance and shock waves caused by traffic slowing down and speeding up - which can lead to incidents and accidents. The overall objective is to maintain traffic throughput - but the schemes have also brought about reductions in accidents and secondary incidents. Speed limits are enforced with automatic camera-based technology (time over distance cameras in the more recent schemes). Another common feature is the use of the hard shoulder for traffic at times of high congestion (“hard shoulder running”) with appropriate VMS signing. (See Case Study: Active Traffic Management Pilot M42 (UK))

Advice to practitioners

National and regional standards are likely to apply to the design and installation of VMS. There are also applicable international standards for regulatory signs. Sixty three countries across the world have ratified the Vienna Convention on Road Signs and Signals. This states that road signs conveyed on VMS should generally conform to the text and symbols used on standard road signs. The Convention allows variations in colour in the interests of legibility. For example, it permits the use of dark text on a light background (the norm for speed signs) to be replaced by light text on dark background in the case of VMS - although the border must remain red.

 

Reference sources

Vienna Convention on Road Signs and Signals, 2006 (See http://www.unece.org/fileadmin/DAM/trans/conventn/Conv_road_signs_2006v_EN.pdf)

Chaterjee, K. Hounsell, N.B. Firmin, P.E. and Bonsall P.W. (2002) Driver Response to Variable Message Sign Information in London. Transportation Research Part C 10, pp. 149–169.

Lai, C.J. (2010) Effects of Color Scheme and Message Lines of Variable Message Signs on Driver Performance. Accident Analysis and Prevention 42, 1003-1008.

Rämä, P., Schirokoff, A., & Luoma, J. (2004) Practice and Deployment of Variable Message Signs (VMS) in Viking countries – Potential for Harmonization Finnra internal reports 34/2004. Helsinki: Finnish Roads Administration.

Erke, A., Sagberg, F. and Hagman, R. (2007) Effects of Route Guidance Variable Message Signs (VMS) on Driver Behaviour. Transportation Research Part F 10(6), pp. 447–457.

Network Security

Authors Alexandra Luck (A Luck Associates)  Hugh Boyes (Bodvoc Ltd)

The road network and vehicle industry are at the beginning of a period of significant change as innovative solutions are sought to improve the safety, serviceability, sustainability and resilience of infrastructure. The way in which networks are managed and the way in which road space is utilised is evolving – with greater use of technology to monitor network conditions and to actively manage traffic. (See ITS and Network Monitoring and Traffic Management) There has also been a significant increase in the complexity of vehicle technology – for example, the use of hybrid and electric vehicles, and developments relating to vehicle connectivity and automation. (See Driver Support)

Changes in the use of technology create vulnerabilities. These are open to exploitation for malicious or hostile reasons – risking interference with vehicles and infrastructure. A security minded approach is necessary to assess and minimise potential risks and to manage incidents and evaluate measures taken.

A security-minded approach is defined as the understanding of the need for – and routine application of – appropriate and proportionate security measures to deter and/or disrupt hostile, malicious, fraudulent and criminal behaviours or activities. This approach needs to address four areas – people, processes, physical security and technical security.

By integrating these four areas it is possible to create an approach to network security that delivers:

  • safety - preventing the creation of harmful situations which may lead to injury or loss of life or unintentional environmental damage
  • authenticity - ensuring that inputs and outputs are genuine and no tampering has occurred
  • availability (including reliability) – ensuring road infrastructure accessibility and usability in an appropriate and timely way
  • confidentiality - ensuring control of access and prevention of unauthorised access to both physical and information assets
  • integrity - maintaining consistency, coherence and configuration of the road infrastructure and systems
  • possession - preventing unauthorised control, manipulation or interference with facilities and services
  • resilience - ensuring the ability to transform, renew and recover service in a timely fashion in response to adverse events
  • utility - ensuring usability and usefulness over time, of data, information and systems.

The application of a security-minded approach requires road operators to work with partner organisations, such as the police, and security advisers. (See Planning and Reporting) This helps to develop an understanding of potential threats and their impact, key vulnerabilities and the nature of mitigating measures required. A failure of security – for any reason – will require a full assessment so that the reasons for failure are understood and lessons can be learnt. (See Emergency Response)

Security Planning

The application of a security-minded approach requires road operators, working with partner organisations and security advisers, to understand potential threats and their impact, identify key vulnerabilities and analyse the nature of measures required to manage risks. (See Planning and Reporting) The goal is to enhance the safety, security and resilience of the road network and its associated infrastructure.

Three key elements in the risk management process are:

  • risk assessment
  • risk mitigation (See risk mitigation)
  • risk review

A road authority, with its partner organisations and advisers, should develop a risk management strategy that incorporates each of these three elements – such as the one in the example outlined below.

Road infrastructure security risk management strategy

Road infrastructure security risk management strategy

A systematic approach is useful in developing a risk management strategy – for which a checklist of questions is helpful to guide practitioners through the evaluation process:

  • Step 1: identify the threats
  • Step 2: analyse vulnerabilities and impacts
  • Step 3: evaluate road network and operational resilience
  • Step 4: short-list countermeasures and risk mitigation strategies
  • Step 5: implement security measures and evaluate

Systematic approach

Step 1. Identify the threats

  1. What scenarios need to be considered?
  2. How likely is each kind of threat?
  3. In what ways is the network vulnerable?
  4. How and why?
  5. What is critical?
  6. How would network operations be compromised?
  7. What and where are the vulnerabilities?
  8. What is critical?

Step 2. Analyse vulnerabilities and impact

  1. Worst-case scenarios
  2. Difficult events and combinations of events
  3. Where is there resilience now?
  4. Recovery strategies that are available
  5. Rate the level of risk:
  6. Likelihood vs severity outcome

Step 3. Evaluate road network and operational resilience

  1. How can resilience be strengthened?
  2. What risk mitigation strategies are available?
  3. What specific security measures are available?
  4. Protection of critical sites and equipment
  5. Security through deterrence
  6. Security though design
  7. Security through detection
  8. How might network operations be adapted in response?
  9. Demonstrate benefits and cost-effectiveness of possible countermeasures

Step 4. Short-list countermeasures and risk mitigation strategies

  1. Incident response plans
  2. Partner agency working
  3. Public information strategy

Step 5. Implement security measures and evaluate

 

Risk Assessment

A risk assessment should consider the potential threats to regular road use and operations and consequential vulnerabilities. Some threats that compromise network resilience are quite common, others are less frequent or rare. (See Security Threats) An essential part of the assessment is to consider how likely it is that a particular threat might happen and how disruptive it would be. The assessment needs to consider what harm might be caused to:

  • the road infrastructure and its related systems
  • road users and others who make use of the infrastructure
  • information about the network and its users
  • the benefits for which the road network exists to deliver.

Vulnerabilities

A vulnerability in the context of road network security is defined as a weakness in the road infrastructure or operating systems that can be exploited by one or more threats.

Vulnerabilities associated with the construction, operation or maintenance of the road network relate to its scale, and how easy it is to:

  • obstruct or interfere with logistics, plant and machinery, supply routes, and staff – so as to disrupt the movement of people and goods and the supply chain
  • cause damage to cameras and sensors that provide information on the condition of the road asset
  • cause damage to new or existing roads and highway infrastructure.

Vulnerabilities that affect highway network operations concern cabling, equipment, sensors and associated processing systems that might be attacked:

  • remotely, through internet or wireless connectivity
  • through physical breaches of systems as a result of damage, either accidental or deliberate, interference or tampering
  • by personnel with administrator access.

Likelihood

The likelihood of threats may be relatively predictable for environmental, social, economic or political reasons. For example, a project’s level of profile, its controversy and its impact on local communities will influence how likely it is to provoke civil protests and strikes, malicious attacks, or theft of equipment such as construction plant.

The likelihood of a threat being realised will be greater if security is poor, for example when:

  • equipment or systems are poorly sited
  • the quality and effectiveness of physical protection measures are insufficient
  • the security-force response is too slow or ineffective
  • the value of vulnerable assets are high
  • the cyber-security systems and procedures are unsuitable or ineffective.

Risk Review

In order to maintain the security of the road network and supporting systems it is necessary to establish a process whereby:

  • risks which have changed for political, economic, social, technological, legal or environmental reasons, are identified and assessed
  • risk mitigation plans are reviewed and updated where necessary.

Further Information

Report of the PIARC Security Task Force (See Security of Road Infrastructure)

Reference sources

PIARC Security Task Force (2015)  Security of Road Infrastructure. Report 2015R01EN.  World Road Association, Paris. ISBN 978-2-84060-357-3.

Security Threats

Security threats can be divided into those which:

  • have the capability to cause damage or disruption to the construction, operation or maintenance of the highway infrastructure (the physical infrastructure)
  • could damage or disrupt the infrastructure operating systems and associated information (the ITS infrastructure).

Threats can also be unintentional, non-directed or unpredicted – for example:

  • severe weather events
  • pandemics
  • incidents involving hazardous materials
  • road traffic collisions
  • fall-out from disruption to other transport modes
  • the jamming or interference with navigation signals caused by natural factors
  • malware infection on an IT system.

The potential level of impact will depend on the criticality of the asset, system or information affected. An example is shown in the photo below.

Road Interrupted by direct action (Source : PIARC Security Task Force)

Road Interrupted by direct action (Source : PIARC Security Task Force)

Physical infrastructure

Damage or disruption to the construction, operation or maintenance of the road infrastructure may arise from a number of threats.

Civil protests and strikes

Civil protests and strikes are most likely to arise from social unrest and civil disobedience. Sometimes this is in response to the construction of assets that are sensitive for environmental, social, economic or political reasons. They have the potential to disrupt or delay operations and can be expensive to manage – and expensive in relation to the final cost of the work being undertaken.

Malicious attack

A malicious attack can occur through a range of external and internal/insider threats. These include damage caused by malware, hackers, disaffected personnel or blast. The result of an attack – in relation to the construction, operation and maintenance of the road network – is likely to centre on physical damage/sabotage to the infrastructure, plant or equipment, or disruption to road users.

Severe weather events

Severe and adverse weather – such as periods of rain, flooding, hard frost, snow, prolonged dry weather, excess heat, high winds, dust storms and earthquakes can cause serious disruption and dangerous driving conditions – as well as considerable damage to the network, in particular:
  • the pavement surface condition and structural strength
  • the stability of surrounding and underlying ground and earthworks
  • sensors embedded within the network.
  • The risks of adverse weather can be mitigated to a degree by the installation of road sensor and weather stations at locations that have a high level of exposure. (See.Weather Monitoring)

Pandemics

Pandemics can affect humans, agricultural livestock and wildlife. They can impact on:
  • a population’s capability to travel and to access needed facilities
  • the willingness and ability of staff and external resources – such as contractors and maintenance staff – to enter an area to undertake work.

Theft of equipment

Depending on the type of equipment, theft can impact directly on traffic operations and on the ability of an authority, and the cost to it, of constructing, maintaining and improving transport infrastructure. It can also have a direct influence on road user safety – and the capability of an authority to manage traffic behaviour and enhance a network’s capacity.

Hazardous materials

Hazardous materials (solids, liquids and gases that can be flammable, corrosive or toxic) are frequently transported by road. They are also used within highway construction and management – and may be stored, processed, or used adjacent (or in close proximity) to the road network. An incident involving hazardous materials can lead to closure of the highway – or damage to it and its supporting systems.

Collisions

Road traffic collisions can cause damage to:
  • pavement surface condition
  • structures such as bridges
  • infrastructure such as gantry signs and traffic management equipment
  • sensors embedded within the network.
  • Incidents can also lead to prolonged closure of the highway and have significant social and economic costs. (See Incident Response Plans)

Fall-out from disruption to other modes (rail, ports, airports)

Disruption to other modes of transport can have a significant effect on road traffic. It can force users to make alternative travel arrangements or – where this is not possible or cost effective (for example, in the case of transportation of freight) – to wait until the disruption has been resolved. Contingency plans may be necessary for parking vehicles that are held up by disruption.

Global Navigation Satellite Systems (GNSS)

The jamming of, or interference with, navigation signals may be caused by human factors, such as intentional or malicious acts/attack, or natural factors such as solar flares and disturbance to the ionosphere. It can result in the loss of precision location information, failure of in-vehicle navigation systems and/or loss of accurate timing signals for area-wide systems.

its infrastructure

Damage or disruption to the ITS infrastructure, operating systems and associated information may arise from:

  • similar threats to those facing the physical infrastructure – although with different impacts
  • and from threats directly associated with digital technology

Malicious attack

A malicious attack can occur through a range of external and internal/insider threats. For example, damage may be caused by malware, hackers or disaffected personnel. Physical damage may be caused to:

  • IT equipment and sensors within the highway boundary
  • communications infrastructure or processing systems located outside the highway boundary (such as control centres, data centres, etc.)
  • logical damage to system software, operating systems and stored data or information
  • road users
  • These attacks can lead to loss of communications or network connectivity – and the corruption or loss of information and traffic disruption.

Theft of equipment

Theft of IT equipment, sensors or cables within the highway boundary can lead to loss of functionality or system resilience. It can also impact on the ability of the infrastructure system to perform as efficiently as it would otherwise. Repair and replacement can be disruptive and problematic.

Cyber-threats

Cyber-threats can arise in several ways including:
  • eCrime – such as the interference with road charging or toll systems, can lead to loss, or corruption, of data on charging, revenue or usage
  • loss of communications and power supplies – which can be accidental or due to deliberate damage to cables and/or distribution system components within the highway boundary or supplying systems outside. The impact will be reduced performance of the infrastructure
  • loss or corruption of software systems – which can impact on the system’s availability or integrity, leading to loss of functionality and/or loss or corruption of data.

 

Risk Mitigation

Counter-measures can help reduce the level of threat to the security of roads and highways and mitigate the potential for disruption. The decision whether to accept identified risks or implement mitigation measures, (and what measures to deploy) may fall to different parties according to the circumstances. It may be:

  • the employer or owner – for example, of a traffic control centre
  • the contractor involved in some aspect of managing and maintaining equipment and infrastructure
  • the road authority or road operator – because of possible legal liabilities
  • the financer or investor where privately-owned assets are involved
  • or the state, as a matter of public policy.

The decision about what mitigation measures will be implemented will depend on a number of factors:

  • the cost of the measure and its implementation
  • the anticipated reduction in the identified risk
  • any undesirable impacts which the mitigation measure may have
  • the potential for the measure to introduce other vulnerabilities
  • whether the proposed measure has any benefits in addition to an improvement in security

Damage or disruption to the construction, operation or maintenance of the highway network arising from intended events – such as civil protests and strikes, malicious attacks, or theft of equipment – may be managed by improving security. For example:

  • protective physical measures being placed around sites vulnerable to threats
  • enhanced stakeholder management, for example early community engagement and consultation
  • planning on traffic routeing and the implementation of works – which take into account, the outcome of the security risk assessment.
  • It may also be necessary – depending on the level of criticality – to develop appropriate and proportionate plans and processes for dealing with different potential outcomes – in case mitigation measures fail.
  • Unintentional, non-directed and unpredicted events (such as severe weather events, pandemics, hazardous materials, and disruption to other transport modes) will also need managing – to reduce the risk of damage and disruption to the infrastructure’s safety, sustainability, serviceability and resilience.
  • In all cases it is advisable to have in place appropriate and proportionate plans and processes for dealing with different types of incident.

Network Operating Systems

Damage or disruption to the highway network operating systems and associated information can have a serious impact on road users and network performance. The outcome is unlikely, though, to pose a major danger to road safety or network serviceability. For example, the loss of satellite navigation can be inconvenient and difficult to prevent. In the event of a failure – so long as there is adequate directional signage on the highway – it is unlikely to have a significant impact on the ability of the network to meet users’ needs.

Equipment Security

Measures relating to the design, location and physical security of equipment cabinets, sensors and cabling routes – which may be at risk from theft or other malicious attack – should be taken into consideration when the assets are first introduced. For existing assets, physical security measures will need to be proportionate – when balancing cost and constraints against the impact of the loss, compromise or failure of the network and associated assets.

Software Systems and ITS Infrastructure

A security minded approach can manage the risk of loss, theft or corruption of software systems, systems for processing financial and/or personal data, and systems providing communications or power supply. This approach is based on the implementation of appropriate and proportionate policies, processes and procedures focusing on four areas – people, business process, physical security, and cyber-security. (See Network Security)

Where wireless technologies are employed in the system, consideration needs to be given to the impact of jamming or interference, and appropriate measures adopted to protect system confidentiality, integrity and availability. Depending on the criticality of individual systems, a variety of business continuity and disaster recovery solutions may also need to be developed.

Weather events

It may be possible to mitigate some of the effects of severe weather on the road pavement, structures, drainage systems and sensors – by:
  • carefully selecting the most appropriate design, materials, methods and systems used in new infrastructure
  • incorporating these into the existing network as and when improvement works are undertaken
  • anticipating where severe weather or flooding may occur and installing weather monitoring an flood warning systems (See Weather Management)

 

Security of ITS

ITS makes use of technologies such as Bluetooth, mobile phones and licence plate recognition to monitor traffic behaviour, improve traffic flows and road safety. Many of these systems – such as CCTV, video image processing and vehicle licence plate recognition – can sometimes be used specifically for security purposes. (See CCTV)

ITS is also extensively used in emergency situations to support crisis management and enforcement purposes. (See Emergency Response and Policing / Enforcement) These systems have to be robust enough to withstand unintentional, non-directed and unpredicted events.

The latest ITS applications, use connected vehicle technology to offer added-value services and safety support to the driving public. The possibility, though, that they may malfunction – or be subject to cyber-attack – needs to be taken into account by system designers and operator. (See Connected Vehicles)

In order to manage the security risks around greater automation and connectivity, it is vital that security of the whole system is considered. Alongside the security safeguards that are built into road vehicles it is important that the security of traffic management systems is also addressed.

Traffic management systems

With the current levels of automation in vehicles being very low, security breaches of existing traffic management systems are the most likely risk to efficient operations and increased congestion. Any such breach would bring with it a risk of reputational damage to the relevant highway authority or operating company. It may also impact on the safety of road users if the ability to detect and verify incidents is impeded. This is particularly the case during the hours of darkness when a stationary vehicle on the roadway can be difficult for drivers to detect, and when traffic speeds are high.

If control rooms become more automated in the future, the tolerance of risk will need to decrease as the need for assurance around the security of the systems becomes greater. Mitigation measures will need to be reviewed to ensure that the level of residual risk is at an acceptable level and does not exceed the level that can be tolerated by the road operator – or by road users in general.

Connected Vehicles and Automation

Security risks will need to be comprehensively reassessed with the introduction of Vehicle-to-Infrastructure (V2I) communications into traffic management systems. This is especially so when V2I is used in combination with Vehicle-to-Vehicle (V2V) systems and greater vehicle autonomy. There will need to be far greater emphasis on safety and the prevention of incidents, particularly those that could cause injury or loss of life. For example, V2I systems that regulate vehicle speed or lane use may be vulnerable to streaming of incorrect or malicious data from insecure sources (vehicles) or other attacks on the system infrastructure. This could put large numbers of vehicles and their occupants at risk.

Vehicle Automation

There are six defined levels of automation for on-road vehicles, where zero represents a fully manual vehicle, and level five is a fully automated vehicle. (See Warning and Control) At level two, the driver is required to monitor the surrounding environment continuously but is assisted by vehicle systems such as emergency assisted braking, lane warning and assisted parking.

At levels three and four the automation will probably begin to include both V2V and V2I connectivity – to support increasingly automated driving and navigation processes.

As a result of the relatively long life of vehicles compared to the rapid development and deployment of new technologies, there will be a mixed fleet of vehicles using the highway at any one time. This may range from those with the very latest communications and automation features, to those which are older with legacy systems. The road network and its associated infrastructure will need to be able to ensure the safe interaction of vehicles with these varying capabilities.

Security risks

The increasing connectivity of external systems and devices to a vehicle – and the developments in V2V, V2I and vehicle-to-device (V2X) connectivity – provide external access which will create vulnerabilities. If a threat is realised it may impact on the safety and security of:
  • the vehicles occupants
  • other road users
  • and infrastructure on or around the highway.
  • Currently the risk of these attacks affecting a vehicle, its occupants and other road users, is very low. It will increase as more connections are made and the technology is deployed in new vehicle models.

Legal Issues

Increasing automation – ultimately up to a level where a driver (like a passenger) has no control of the vehicle – raises legal questions surrounding:

  • the continuing responsibilities and duty of care of drivers
  • the responsibility of fleet owners
  • the duty of care owed by the manufacturers of the vehicle and the designers and providers of the advanced technology
  • the responsibility of highway authorities, traffic management system engineers and statutory bodies

Advice to Practitioners

To implement a security-minded approach for ITS, it is essential that security risks are understood not only during design stage, but throughout the lifecycle of operations. This requires the development of an ITS Security Strategy that sets out:

  • the security requirements for the system(s)
  • the risk management strategy
  • the mechanisms for maintaining situational awareness
  • the means for reviewing and updating the strategy.

ITS Security Management Plan

Alongside a risk management strategy for the network (See Security Planning), an ITS Security Management Plan is needed to detail the policies, processes and procedures needed to maintain the required level of security with clear roles and responsibilities for the road authority, the road operator, and any other parties that are directly involved in network operations. This should be embedded in other operating policies and reviewed regularly. (See Planning and Reporting)

The policies, process and procedures in the ITS Security Management Plan will need to deliver:

  • continuity of operations, including safety of drivers, passengers, the vehicles, other road users, and the road network (its availability, safety, and resilience)
  • control of access and system operations (issues such as confidentiality and who is controlling the highway)
  • the quality and validity of information, including configuration of the vehicle, road infrastructure and any connected systems (to preserve the integrity, utility, and authenticity of those systems).
  • Failure to address any of these elements can undermine the safety and security of the vehicle, the road network, and/or any connected systems.

 

Security Incidents

The immediate response to any incident or breach of security which impacts on the integrity of the road network, its associated assets and systems, and/or information is more likely to be effective if:

  • it is based around a plan that has been prepared in advance and rehearsed
  • the plan has been developed in collaboration with key stakeholders
  • the plan has been kept up to date

A security response plan increases the chance that local communities, businesses, transportation and emergency services will be able to continue to function following less severe incidents – without the need for the authorities to implement contingency arrangements. Where contingency arrangements become necessary, these should include business continuity measures as well as disaster and incident recovery actions. The aim is to mitigate impacts arising in the event of failure or impairment or non-availability of part of the network or related systems. (See Incident Response Plans)

To produce a plan of this type, it is necessary to identify:

  • those parts of the network or assets that are most at risk or where the consequences may be most severe. For example, where the network provides access to isolated communities or emergency services, or are part of crucial network links
  • alternative network routes which can be utilised and are at lower risk
  • processes of inspection, public reporting of issues and accurate record-keeping – to better establish and monitor areas where issues arise
  • warning procedures to provide alerts of threats such as severe weather events
  • health and safety issues specific to each threat
  • the lead authority and the key decision-makers and other parties who need to be informed of the situation in the event of an incident, including the emergency services
  • the processes by which key decisions should be made
  • the mitigation measures to be implemented, including specific health and safety considerations
  • methods for communicating with members of the public including effective working arrangements with local press and broadcast media including social media. These can, where applicable, enable presentation of timely and accurate information and advice on infrastructure condition
  • training needs for staff and key stakeholders on measures and processes to be included in the plan(s)
  • arrangements for obtaining reserve supplies of key resources to support a minimum resilience standard
  • the business continuity measures required in the event of a failure or breach of the mitigation measures – resulting in the failure, impairment or non-availability of part of the network or related systems
  • disaster or incident recovery actions
  • arrangements for regular reviews of the plan to take account of changing circumstances, and to monitor of its implementation in the event of incident.

Security Incident response

In the event of a security incident, it is important that steps are taken to contain and recover from the event. (See Traffic Incidents)

During a security incident the response should include:

  • measures for reducing further damage or loss
  • an assessment of what has been lost, compromised, damaged or corrupted
  • and if required, the collection of evidence for law enforcement purposes
  • Where it is necessary to collect evidence for law enforcement – all evidence (both physical and digital) that may help investigators to identify the cause of the event and its perpetrators, should be preserved and collected before any recovery actions are taken. The exception being where immediate recovery actions are critical to saving life

It may also be necessary to notify third parties – for example, service providers, regulatory bodies, and law enforcement agencies – in order to manage the incident effectively, including management of traffic on the surrounding network, and to minimise further disruption.

The provision of appropriate and timely information and advice to members of the public will also help in the management of the incident and minimise further disruption to the network. (See Emergency Response)


Source URL: https://rno-its.piarc.org/en/network-operations