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

Home > Printer-friendly > Monitoring Activities

Network Monitoring Activities

Authors  PIARC Technical Committee on Road Network Operations

The main objectives of road network monitoring can be summarised as follows:

  • keep track of traffic volumes, service levels, incidents and road environmental conditions
  • support road control room operators in making decisions on how to better operate the network
  • monitor and evaluate network operations functions
  • accumulate and archive data for off-line analysis

Each objective is realised through various solutions, including the application of ITS technolgies.

Network monitoring is expensive. When considering the provision of monitoring systems it is important to establish the key purpose of collecting specific information and to design systems accordingly. Depending on the local context, information may be needed on a variety of factors – such as traffic and weather conditions, incidents and other road and highway status alerts – in order to provide intelligence for network operations activities, traffic control and information systems. Other examples are:

  • vehicle speeds – especially for incident detection and for speed control where traffic is heavy – or for enforcement where road safety is at risk from excessive speeds
  • traffic flows – needed for local traffic control at signalised intersections and across a network to provide information on travel demand
  • vehicle counts – often classified by different types of vehicles for traffic management purposes
  • lane occupancy – to provide an appreciation of the level of service available to road-users on expressways and motorways
  • point-to-point journey times – for route planning and as an important source of real-time information for road-users
  • journey time reliability – to measure of the overall level of service offered to road users and to assess the effectiveness of network operations
  • environmental characteristics – to monitor weather and road surface conditions and atmospheric pollution

Events On the Network

Managing events on the road network in real-time requires the means to detect and rapidly assess any situation that is potentially problematic as soon as it arises, with reliable procedures for a quick and suitable response.

To carry out these tasks, the desk operators must:

  • have ready access to the necessary network and related information (See Basic Info-structure and Data and Information)
  • be able to rely on the organisations that will be involved in event response (See  Incident Response Planning)
  • have a clear vision of what must be done, on their own initiative or as part of an organisation set in motion elsewhere (See Traffic Incidents)
  • know and maintain current response procedures (See Planning Procedures)
  • periodically update their analysis, referring to indicators monitoring the event and the consequences they have recorded (See Monitoring Technologies)
  • forward their analysis and compare it with those of the other players

Analysis of the situation must have regard to: 

  • context, including site details, weather and environmental factors, sensitive points, traffic, stakeholders and players
  • a search for complementary information (including cross-checks of all information received)
  • identification of potential aggravating factors.

This task demands major efforts to develop systems that capitalise on and disseminate past experience. Crucially it requires good staff coordination to avoid instances where staff work at cross-purposes during an emergency.

All the organisations and agencies that have a part to play in the network operation will have an interest in network monitoring activities. In planning, designing and allocating resources to the network monitoring system the equipment, information systems and operational procedures need to be specified in line with the coordination arrangements. In particular, when multiple partners are involved at the operations centre a flow of command needs to be established in order to ensure smooth implementation. (See Operating Agreements)

Agreement on operational procedures is especially important when the data being monitored are used for enforcement purposes. Usually, network operators do not have the power to actually catch or rectify the offending situation even when it is necessary to do so in order to ensure a smooth operation. Close planning and cooperation with enforcement agencies are critical. (See Enforcement)

Information and Data Gathering

The core data used to assess and manage the roadway is collected and collated by manual methods and automatically for use in both real time and non-real time applications. Choice of equipment and methods is dictated by the required services as well as the available human and financial resources. (See Methods & Procedures and Vehicles & Roadways)

Example data includes:

  • equipment fault monitoring
  • information submitted by other departments or users (including mobile patrols)
  • traffic data (surveys and manual counts, aerial observations, sensors and stations, video surveillance, point-to-point journey time monitoring)
  • weather data (subscription to specialised services, local measuring and observation stations, visibility meters)
  • various specific data (Automatic Incident Detection (AID), fire, smoke, pollution, flood, avalanche and other detectors)

Care must be taken not to overload operators and systems with data and information without sufficient filtering or analysis. The following questions must always be addressed:

  • what data is essential?
  • where is the best place to collect the data?
  • will data collection be a temporary or on-going activity?
  • for what periods will data be gathered?
  • how will the data be archived?
  • are human resources sufficient to gather and use the data and to implement the resulting measures?
  • how will the data be processed (systems); do the various systems available complement each other?
  • what will be the cost of gathering the data in terms of capital expenditure, operations and maintenance?

Certain constraints must be considered. The organisation will need to

  • ensure systems are interoperable and implement relevant recommendations (standards)
  • train and motivate staff
  • plan adequate operating, maintenance and capital renewal budgets
  • collect data on significant unplanned events

ITS-related monitoring systems are characterised by the use of electronic sensors, data processing by a central computer, and data transmission. The system requirements are heavily dependent on the operational activities that it will support (operating, controlling and providing services) and the road network characteristics under consideration. (See Information & Data Gathering)

When an existing (legacy) system needs to be incorporated in the new monitoring system, it is important to evaluate the system applicability for continued use and whether it can satisfactorily accommodate new requirements.

Privacy

Privacy is a critical issue when incorporating detection technologies that can identify individual vehicles. Typical technologies for these include CCTV, video image processing, automatic vehicle identification (AVI) and cell-phone tracking. It is therefore important to agree a policy of how to respect privacy at all stages: when information is collected, when it is being used and when it is exchanged and transmitted between relevant organisations, including making it available to the public. (See Privacy)

Incident Detection

A primary aim of network monitoring is to predict or detect traffic incidents or disturbances as quickly as possible, in order to take the necessary steps to remedy the situation in due time. Its quality is characterised by a detection delay (interval between the time the incident occurs and the time the management service is warned of this incident) and the reliability of the information collected. Incident detection and response forms part of most network management systems, although automated incident detection systems are not relied upon as much as in the past, since many incidents are now promptly reported using cellular phones.

Automated incident detection is most commonly found in urban areas where traffic congestion during peak hour periods is experienced. However, initiatives such as e-Call (Europe) are developing integrated emergency response infrastructure, which will improve detection and response to incidents in all areas (rural and urban) by means of global positioning, in-vehicle sensors and satellite and cell phone technology. In-vehicle systems where on-board electronics improve the driver’s competence in congested travel conditions, at night or in bad weather, can also reduce the occurrence of incidents. (See Automatic Incident Detection)

Performance Criteria

In the case of automatic detection, the reliability of the monitoring system needs to be evaluated after installation, with respect to the detection function, the telecommunications function, the data processing function and the overall system function. Typical evaluation points include accuracy of measurement, timeliness of data transmission and processing, ability to provide required data, reliability of software algorithms, system resilience under required environmental conditions and maintenance costs.

In the case of non-automatic detection such as phone calls from users, the reliability and accuracy of the data also becomes an important issue. Another issue is the problem of operators receiving too many calls with redundant information. This often happens in the case of large accidents that many people can clearly observe.

Information from Road Users

The purpose of this approach is to discover breakdowns in the flow of traffic that may not have been detected by traditional road operation equipment or services (automatic data gathering, mobile patrols, and other sources such as probe vehicles). Members of the public are encouraged to report traffic accidents, congestion and other problems. The information may mainly be received by telephone: cellular phones used from the car or emergency phones located along the road.

Information from road users can be gathered directly by the traffic or operations centre or through a dedicated call centre. In both cases it is very important to handle the gathered information quickly and to confirm its value through the use of the other information sources (such as loops, cameras, mobile patrols). Information from drivers can also be a complementary input for the traffic centre database and is an important tool where monitoring equipment is limited.

User feedback concerning the efficiency of the roadway and traffic conditions is a useful input for determining the perception of the network monitoring operation. This can be achieved through:

  • roadwork preparation meetings, especially with local residents
  • meetings organised as part of the assessment of specific operations measures such as regulated access, regulated speed
  • specific meetings on themes defined in conjunction with user groups such as automobile clubs, motorcycle associations, cyclists, road professionals
  • direct surveys within a pre-defined panel or undertaken in the framework of more general surveys on the quality of the road network

Weather and Natural Events

The aim here is to detect or predict any abnormal situation (weather or other) that is likely to affect the level of service to users of the network, in particular its safety of use. The requirements cover forecasts and detection as such and the integration of measurements into the prediction models. (See Weather Monitoring)

Detection systems can enable information to be given to the network operator regarding the onset (or probability of onset) of difficult weather conditions (fog, black ice, snowfall, cyclones, dust-storms) or other unfavourable natural events (landslides, floods). The network operator's task is to respond by issuing appropriate advice on road use through all available channels. (See Traveller Services)

Road works

Road works and bridge maintenance ( including rehabilitation and upgrading) can create substantial traffic congestion if not well-planned and properly designed. Alternative construction methods and working hours (off peak and night-time) will improve road serviceability and safety. Re-routing of traffic by means of pre-trip and en-route information about road works will help reduce congestion in these areas. (See  Planning Road Works) Planned special events may also cause significant traffic congestion if not planned properly, taking into consideration the extra travel demand created by the event and the impact of reductions in capacity on the road network (for example street closures). (See  Planned Events)

Data Archive

An important aspect of network monitoring is the gathering of information on traffic characteristics (such as flow, occupancy rate, speed, percentage of trucks and lorries) in greater or lesser detail in order to monitor or anticipate trends. The required qualities are reliability and completeness of the traffic data collection systems.

This requires systems for the collection, processing and centralisation of counts and information, organised relations with the safety and emergency call-out services or the assistance services, automatic or non-automatic warning systems (emergency call network, automatic incident detection), and the organisation of regular patrols on the most sensitive roads. (See Data Aggregation and Analysis)

Real-time data accumulation to serve as historical data is an important task of the monitoring mission. It can be used in such a way as to compare real-time data with historical data and find out the presence of incidents on the network. Before/after study of operations and control functions also depends on comparison of these data. In addition, historical data can provide important information to the ITS-unrelated programs of network improvement such as geometric improvement and pavement rehabilitation. (See Data Management and Archiving and Data Ownership and Sharing)

 

Methods and Procedures

Information is provided here on a number of methods that are widely used in network monitoring at all levels of operation.

Mobile Patrols

The responsibilities of patrol officers are to:

  • rapidly detect unplanned events on the network, especially in areas and at times susceptible to problems
  • implement the appropriate response
  • restore normal or optimal operations as soon as practicable

To carry out this task the patrol officer monitors the assigned network segment, reports and responds to minor incidents where appropriate. Patrols are developed only if an Operations Centre is capable of undertaking actions proposed by the patrol reports.

Patrol operating procedures, schedules and routes will depend on the department’s objectives and operating strategy, and they must be adjusted to meet actual needs (scope and frequency of problems) and resources available.

Patrols may be conducted in various patterns:

  • continuously throughout the network
  • periodically on major routes (from several times a day to a few times a month)
  • to target certain periods and/or roadways (weekends, for example)
  • in response to events, or alarms

Patrol officers must carry, in their vehicle, a procedures manual, automatic response sheets, a logbook, a communications device (radio, telephone), and possibly response equipment.

Patrol officer training must include an introduction to specific reporting procedures and the submission of reports in a standardised format (For example: I am arriving on the site / I am leaving the site, traffic is reduced to one vehicle approximately every five seconds, the traffic jam is at least 600 m long and growing). (See Mobile Service Patrols)

Aerial Observation

The purpose of aerial observation is to obtain comprehensive information in real time on events in progress in a broader area not systematically equipped to gather data. This essentially involves large migrations as well as serious traffic disruptions: events generating high traffic density, extensive flooding, etc. From the air, an observer can monitor the system, analyse the situation and send information to a central operations centre on traffic conditions as well as implementation of operating measures, which can be reconsidered or completed.

Aerial observation missions provide the opportunity to complement raw data with an analysis and potential solutions together with real-time observations of driver behaviour and the effectiveness of response actions. Nevertheless aerial observations are expensive and are viable only for exceptional events and heavily trafficked areas that routinely experience a high frequency of disruptive incidents.

After-hours Duty Desk

The after-hours duty desk ensures the continuation of some operational tasks outside business hours, with priority on roadway and equipment maintenance. The principle is to provide all external services with a point of contact (duty officer) to record the call and forward the information received to the appropriate department(s), potentially to initiate response or inform partners about the status of the network.

The duty desk essentially involves:

  • receiving, validating and enhancing information, circulating to the appropriate organisations and departments and forwarding it as requested
  • dispatching incident or emergency response and monitoring response actions

The specific resources for the duty desk include:

  • human resources (duty officers with specific training, on-going supervision)
  • material resources (such as CCTV, telephone, radio, procedures manual, maps and directories, event log, response requisitions, decision support systems)

This task requires an intense effort in terms of organisation and communication both internally and externally but it also contributes to improving the department’s efficiency as much from the perspective of users as of partners.

Keeping an event Log

The purpose of keeping a log is to improve management through the monitoring and tracking of events. The following must be chronologically recorded, in real time and using a reliable medium:
  • all calls concerning roadway events, whether within the section or from partners and users
  • all decisions made and actions taken

Calls may be recorded in a format that includes:

  • the date and time of the call
  • name and title of caller
  • reason for call
  • location of problem resulting in the call

The decisions made and actions taken must also be noted, including the date and time.

A log must be kept in real time and the information logged must be complete. The usefulness of a log is directly dependent on the experience and qualifications of the officer who writes it. In major events, a person must be assigned exclusively to this task.

Each participant in the operation of the road system must keep a log of their assigned tasks: after-hours duty officers, patrol officers, winter maintenance services, operating control centres, etc. The log may be kept in a notebook or electronically on a computer.

Since records may be used in legal proceedings, the log must be impossible to falsify (non-removable numbered pages or secure electronic copy).

Maintaining comprehensive logs (record everything in real time, as events unfold, with no possibility of changing entries after they are made) ensures:

  • accountability of officers
  • improved information on network vulnerabilities
  • contribution to critical analysis of a given organisation
  • improved cooperation with partners
  • improved circulation of information
  • reliable information in the event of legal proceedings

Managing Traffic Counts

The goal here is to obtain reliable, representative statistics to analyse traffic disruptions and propose solutions, thus providing road users with authoritative information on forecast events.

To do this, the network operations department needs the ability to provide well-informed solutions based on expert analysis of traffic volumes, traffic distribution and the evolution of traffic trends. It must collate and validate data for future operational planning and for the provision of valuable traffic statistics.

The data required for traffic studies differs according to the problem to be addressed, for example:

  • aggregate measurements over a variety of periods, such as: a few seconds, 1 minute, 3 minutes, 5 minutes, 6 minutes , 1 hour, 1 day;
  • for each year, the average daily traffic and percentage of heavy trucks (for road maintenance programming, development studies and economic studies)
  • weekend outbound and return traffic
  • monthly traffic
  • peak period traffic (for identifying and implementing alternate routes)
  • hours with heavier average traffic (for planning road work periods or the need for patrols)
  • day and night traffic (for mapping traffic noise)

Interpretation of counts often requires consideration of other factors such as weather data, incidents, accidents, major events. It is therefore necessary to relate the collated traffic data to records and observations summarising the day’s events.

Conducting traffic count studies requires high-performance counting equipment, and computers to process the date including:

  • databases or files in standard formats to allow the use of common software in all sections
  • a location reference system that can be easily linked to a road reference framework

The complexity of data management, count evaluation and simulation tools, requires basic training in traffic engineering and in statistics to ensure credible, relevant results.

Traffic Forecasts

The network operator needs to forecast as accurately as possible, often in real-time, the anticipated traffic in the network in order to be prepared to manage the consequences. This is especially important during known high-risk periods.

The programme proceeds as follows:

  • identify comparable periods, networks or situations
  • identify factors likely to skew comparisons (such as the creation or closure of infrastructures, changes to police measures, adverse weather, special popular events)
  • survey corresponding traffic flows
  • apply potential corrective factors
  • study how traffic develops in reality
  • develop and revise forecasts as necessary
  • determine the margin for error in traffic estimates
  • make comparisons with any forecasts produced by other services

The programme requires:

  • consultation of relevant, reliable databases
  • customised software
  • complementary surveys

There is always the risk of an unexpected event (such as adverse weather, major disruptions on a neighbouring arterial) occurring at the last minute, making established forecasts totally irrelevant. Furthermore, some preventive operating measures may prove inadequate. However, regular attention to near-term and future traffic forecasts will reduce the likelihood and frequency of an emergency response being needed.

 


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