| Number | Description | Associated Functions |
7.1 | Traffic Control |
7.1.0 | Objectives | |
| The system shall support the existing and new traffic management needs of authorities by providing a flexible yet comprehensive approach to determine traffic management strategies (including bridge and tunnel control). | |
| The system shall be able to manage traffic in all or part of the road network using a methodology that is appropriate for urban roads, e.g. using traffic lights at junctions and with the possibility of incorporating facilities for pedestrians to cross the road in a controlled manner. | |
| The system shall be able to manage traffic in all or part of the road network using a methodology that is appropriate for motorways, e.g. no junctions and pedestrian facilities, but with lane use management. | |
| The system shall be able to use different methodologies to control separate areas of the road network. | |
| The system shall be able to manage the urban/inter-urban interface. | |
| The system shall be able to implement identified control strategies that conform with specified policy. | |
| The system shall not do anything to reduce road safety. | |
| The system shall manage road traffic in such a way that levels of environmental (i.e. atmospheric and noise) pollution may be reduced. | |
| The system shall manage road traffic in such a way that congestion (travel time) may be reduced. | |
| The system shall be able to help co-ordinate the activities of TICs and TCCs. | |
| The system shall be able to exchange information between TICs and TCCs, including across national boundaries. | |
| The system shall enable the data that it stores to be extracted by an operator onto a variety of media and used for other purposes, or by other organisations. | |
| The system shall ensure that traveller information service providers are aware of the traffic management strategy, so that they can provide information that conforms to it. | |
7.1 | Traffic Control |
7.1.1 | Monitoring | |
| The system shall be able to monitor sections of the road network to provide the current traffic conditions (e.g. flows, occupancies, speed and travel times etc.) as real time data. | |
| The system shall monitor traffic in all or part of the road network that uses an "urban" style of road management, e.g. using traffic lights at junctions and with the possibility of incorporating facilities for pedestrians to cross the road in a controlled manner. | |
| The system shall monitor traffic in all or part of the road network that uses an "inter-urban" style of road management, e.g. no junctions and pedestrian facilities, but with lane use management. | |
| The system shall be able to monitor traffic flow at, and the operation of, the road intersections of the network over which it has the control. | |
| The system shall be able to monitor the entire road network (network state surveillance tool). | |
| The system shall be able to monitor and record weather conditions (wind, fog, rain level, ice, etc.). | |
| The system shall be able to monitor and record environmental (atmospheric and noise) pollution conditions, and provide an alarm when a certain threshold is exceeded. | |
| The system shall be able to measure the range of visibility and detect reductions caused by adverse weather and pollution conditions (but not darkness). | |
7.1 | Traffic Control |
7.1.10 | Lane Management | |
| The system shall be able to reserve certain traffic lanes exclusively to specific classes of vehicles (e.g. high occupancy vehicles, or buses) and to detect violators. | |
7.1 | Traffic Control |
7.1.11 | Parking Management | |
| The system shall be able to monitor the current usage of the parking facilities. | |
| The system shall be able to forecast the need for parking slots. | |
| The system shall be able to identify those vehicles, or their drivers, which violate the parking regulations, e.g. fail to pay, stay too long, etc.
| |
| The system shall be able to collect and store data from all car parks to provide a historical record. | |
7.1 | Traffic Control |
7.1.12 | Vulnerable Road Users | |
| The system shall be able to control pedestrian and cycle crossings. | |
| The system shall be able to monitor and control pedestrian and cycle crossings in order to optimise their use. | |
7.1 | Traffic Control |
7.1.2 | Planning | |
| The system shall be able to use consistent historical data to complement real-time data, when necessary. | |
| The system shall be able to predict short, medium, and long-term traffic conditions. | |
| The system shall be able to use historical data to complement predicted data, when necessary. | |
| The system shall be able to analyse road and traffic data to predict possible critical situations. | |
| The system shall be able to predict weather conditions, in particular the formation of fog and/or ice. | |
| The system shall be able to predict short, medium and long-term road travel produced environmental (atmospheric and noise) pollution conditions based on traffic and weather conditions. | |
| The system shall be able to provide historical and predicted data. | |
| The system shall be able to produce new traffic management strategies from one or more of historic, current, or predicted road traffic data. | |
7.1 | Traffic Control |
7.1.3 | Traffic Control Centres | |
| The system shall enable a TCC operator to control, possibly remotely, infrastructure elements (e.g. traffic lights, VMS). | |
| The system shall enable a TCC operator to log all significant incidents and to record free text messages prior to their output to travellers. | |
| The system shall be able to provide a graphical representation of the road network (including equipment, incidents, traffic condition etc....) to TCC operators. | |
| The system shall be able to activate control devices (e.g. traffic lights, VMS), either individually or in groups. | |
| The system shall enable TCC operators to make temporary changes to the normal control strategy in real-time. | |
| The system shall be able to implement planned control strategies for planned events (e.g. sport, cultural, etc.). | |
| The system shall be able to support a database of all known (future) events. | |
| The system shall provide TCC/TIC operators with controlled access to all relevant systems. | |
7.1 | Traffic Control |
7.1.4 | Traffic Flow Control | |
| The system shall be able to control the entries and exits to motorways. | |
| The system shall be able to provide ramp metering (e.g. using traffic signals or barriers) at selected locations (e.g. slip road entrances to high speed roads). | |
| The system shall provide Tidal Flow Control (reservation of lanes for exclusive use in one direction for a period, then the other direction for another period, on parts of the road network). | |
| The system shall be able to provide advice to drivers as they approach car parks (on-street and off-street, as well as motorway service area parking). | |
| The system shall be able to provide priority to selected travellers (e.g. PT, emergency vehicles, cycles, pedestrians) through the road network, including on motorways (when applicable). | |
| The system shall be able to provide control measures for bridges so that warnings of weather conditions, vehicle restrictions and closure can be provided. | |
| The system shall be able to provide control measures for "tunnel" environments i.e. vehicle restrictions, fire detection, atmospheric pollution and closure. | |
| The system shall be able to provide co-ordinated traffic management operations during periods of mass movement across (many) regions. | |
| The system shall be able to provide specific traffic management for exceptional vehicles (e.g. very dangerous cargo, wide loads, etc.). | |
7.1 | Traffic Control |
7.1.5 | Exceptions Management | |
| The system shall be able to provide control measures to protect road maintenance work and workers. | |
| The system shall be able to command drivers to change lanes on multi-lane roads. | |
| The system shall be able to change the direction of traffic flow on a some or all of the lanes on a carriageway in an orderly manner so that it does not create a safety hazard to any road user. | |
| The system shall be able to reverse the direction of traffic flow along roads in the urban road network with a single direction of flow in an orderly manner so that it does not create a safety hazard to any road user. | |
| The system shall be able to close roads and advise drivers of a suitable diversionary route for a period of time. | |
| The system shall be able to command drivers of certain classes of vehicle (e.g. heavy vehicles or tourist traffic) to take an alternative route for a period of time. | |
| The system shall be able to recommend re-routing strategies to reduce congestion. | |
| The system shall request confirmation of all exceptional measures before they are executed. | |
| The system shall be able to recommend re-routing strategies to reduce atmospheric pollution. | |
7.1 | Traffic Control |
7.1.6 | O/D Computations | |
| The system shall be able to provide Origin/Destination computations, and route assignment estimations, for the road network. | |
7.1 | Traffic Control |
7.1.7 | Speed Management | |
| The system shall be able to show the maximum authorised speed of vehicles on selected carriageways to be shown to drivers.
| |
| The system shall be able to set variable speed limits on parts of the road network. | |
| The system shall be able to calculate recommended speed limits for given traffic and weather conditions, and road network characteristics. | |
| The system shall transmit recommended speed limits to equipped vehicles. | |
| The system shall be able to support a database of all speed limits on the road network. | |
| The system shall be able to support an in-vehicle database of road network data (e.g. speed limits, road hazards, junctions etc.). | |
| The system shall be able to detect and identify vehicles that exceed the maximum authorised speed limit on selected carriageways. | |
7.1 | Traffic Control |
7.1.8 | Roadside-Vehicle Communications | |
| The system shall be able to transmit information to a vehicle to update its on-board database. | |
7.1 | Traffic Control |
7.1.9 | Adaptive Traffic Control | |
| The system shall be able to provide green wave management for all vehicles. | |
| The system shall be able to minimise delays of all vehicles using adaptive signal control | |
| The system shall be able to grant priority to selected vehicles (e.g. PT, emergency vehicles) at an intersection controlled by some form of traffic signals. | |
| The system shall be able to give priority to PT in a manner that minimises the impact on other road users. | |
7.2 | Incident Management |
7.2.0 | Objectives | |
| The system shall detect and respond to various incidents on the road network. | |
| The system shall be able to co-ordinate the implementation of incident management strategies between associated TCCs. | |
| The system shall not do anything to reduce road safety. | |
| The system shall not do anything that might aggravate, or cause, an incident. | |
| The system shall assist the emergency services to provide an effective response to road traffic incidents. | |
| The system shall collect and filter emergency calls from travellers in the road network using a variety of types of communication (e.g. road-side telephones, mobile phones, (automatic) on-board 'MayDay' etc.) | |
| The system shall minimise the time between the occurrence of an incident and its detection. | |
| The system shall be able to validate that an incident has occurred in order to minimise false alarms. | |
| The system shall be able to suggest one or more responses for dealing with an incident. | |
| The system shall be able to run (pre-)defined incident mitigation strategies automatically. | |
7.2 | Incident Management |
7.2.1 | Emergency Services | |
| The system shall be able to locate and identify emergency vehicles on the road network. | |
| The system shall be able to co-ordinate the emergency and rescue services once an incident has been detected, until all injured persons have reached a hospital. | |
| The system shall provide communications between the emergency services, hospitals and TCCs for the provision of incident information. | |
7.2 | Incident Management |
7.2.2 | Information Management | |
| The system shall be able to collect and store data on each incident, e.g. location, type, severity, number & type of vehicles involved, the emergency/rescue vehicles needed etc. | |
| The system shall be able to identify and classify all incidents on the road network. | |
| The system shall be able to provide information on each incident to TICs for onward transmission to travellers. | |
| The system shall be able to provide information to travellers about the reason why a particular incident management strategy is being implemented. | |
7.2 | Incident Management |
7.2.3 | Reporting | |
| The system shall be able to produce incident data statistics, e.g. frequencies of occurrence, by time, type and location; identification of "high risk" locations on the road network; performance of the incident detection system. | |
7.2 | Incident Management |
7.2.4 | Post-Incident Management | |
| The system shall be able to minimise the consequences of an incident on the road network for those travellers who are not involved. | |
| The system shall be able to monitor the aftermath of an incident. | |
7.2 | Incident Management |
7.2.5 | Pre-Incident Management | |
| The system shall be able to detect "non-vehicle" incidents before they can escalate into traffic accidents, e.g. bad weather conditions, objects on the road, ghost drivers, etc.
| |
| The system shall be able to provide local warnings on dangerous sections of the road network. | |
7.2 | Incident Management |
7.2.6 | Hazardous Goods | |
| The system shall be able to advise the emergency services on any hazardous goods that have been involved in an incident. | |
7.3 | Demand Management |
7.3.0 | Objectives | |
| The system shall provide information that will influence travellers' decisions regarding their destinations, time, mode of travel, route etc. | |
| The system shall receive up-to-date information on those factors that will influence the demand management strategy, e.g. traffic levels, car park usage, other modes usage, fares, tolls, etc. | |
| The system shall be able to recommend a strategy to influence changes in demand for one or more modes of transport. | |
| The system shall be able to simulate a demand management strategy on the road network. | |
| The system shall be able to simulate potential capacity reduction, e.g. due to road works. | |
7.3 | Demand Management |
7.3.1 | Zoning | |
| The system shall be able to create a "traffic collar" and limit the entry of all vehicles into a defined area according to (a set of) criteria. | |
| The system shall be able to recommend alternative routes (e.g. that take into account the needs of heavy vehicles (and hazardous goods)) when it is required to direct certain types of vehicle away from a particular part of the road network. | |
| The system shall be able to control the access of vehicles into a zone using a form of identification, e.g. electronic tags, number plate readers, etc. | |
| The system shall be able to use physical barriers to control the access of vehicles into a zone. | |
7.3 | Demand Management |
7.3.2 | Pricing Management | |
| The system shall be able charge for the use of a section of road, or facility (e.g. bridge, tunnel etc.), based on given policy decisions, e.g. duration, distance, congestion etc. | |
| The system shall be able to adjust toll fees according to a given pricing strategy. | |
| The system shall be able to adjust parking fees according to a given pricing strategy. | |
| The system shall be able to adjust public transport fares according to a given pricing strategy. | |
7.3 | Demand Management |
7.3.3 | Parking Management | |
| The system shall be able to implement parking strategies in specific areas, including P+R strategies. | |
7.3 | Demand Management |
7.3.4 | Vulnerable Road Users | |
| The system shall be able to provide information to promote the use of cycles and walking. | |
7.3 | Demand Management |
7.3.5 | Car Sharing | |
7.4 | Cooperative Systems - Traffic Safety |
7.4.1 | Road Hazard Warning | |
| (X)FCD - The system shall be able to maintain a database of the road network. | |
| (X)FCD - The system shall enable data received from vehicles by a road-side device to be integrated, analysed and fused. | |
| (X)FCD - The system shall enable a road-side device to send fused traffic data to the TCC. | |
| (X)FCD - The system shall enable a road-side device to send weather and environmental conditions to the TCC road-side device. | |
| (X)FCD - The system shall be able to fuse the XFCD data from a number of vehicles with the host vehicle data to create a more accurate view of the road and traffic conditions in that area. | |
| (X)FCD - The system shall be able to send fused FCD to the TCC from a road-side device. | |
| (X)FCD - The system shall be able to send XFCD to the TCC from the host vehicle. | |
| (X)FCD - The system shall be able to add traffic data from the infrastructure (e.g. induction loops, radar) to the fused XFCD data of the road-side device. | |
| (X)FCD - The system shall be able to communicate with another vehicle either directly, or via an road-side device. (Communications). | |
| (X)FCD - The system shall be able to match a visual image of a vehicle with the (un-attributable - for privacy protection) identity of a vehicle that is providing FCD and/or XFCD. | |
| Hazard Detection - The system shall be able to determine the existence of a sharp curve from the road network database. | |
| (X)FCD - The system shall be able to determine the intended route of the host vehicle. | |
| Hazard Detection - The system shall be able to determine that the host vehicle is partially occupying an adjacent lane for a short time, e.g. due to manoeuvre round a sharp bend, or lane width reductions. | |
| Hazard Detection - The system shall be able to detect the presence of fire or smoke on the host vehicle. | |
| Hazard Detection - The system shall enable the host vehicle to send information about its own safety behaviour (i.e. whether or not the vehicle was being driven in an unsafe manner, e.g. excessive speeding, swapping of lanes, overtaking, driver inattention) to a road-side device. | |
| Hazard Detection - The system shall be able to detect presence of other vehicles and traffic participants in the vicinity of the host vehicle, and determine its type, e.g. car, lorry, emergency, maintenance, cycle, pedestrian. | |
| Hazard Detection - The system shall be able to determine the status of the traffic in the vicinity of the host vehicle, e.g. congestion, stationary vehicle(s). | |
| Hazard Detection - The system shall be able to detect the presence of stationary objects (seen or deduced) in the carriageway ahead of the host vehicle, and to warn the driver via an in-vehicle device. | |
| Hazard Detection - The system shall be able to detect the presence of stationary objects (seen or deduced) in the opposite carriageway to that of the host vehicle, and to send a warning to other vehicles. | |
| Hazard Detection - The system shall enable the TCC to determine whether an incident has occurred. | |
| Hazard Detection - The system shall enable an road-side device to determine whether an incident has occurred. | |
| Motorcycle Warning - The system shall be able to detect that the host motorcycle has fallen onto the road pavement, and send this information to other vehicles. | |
| (X)FCD - The system shall be able to determine the relative position of the host vehicle on a road (e.g. lane, distance from a datum point) at all times (urban, inter-urban, tunnels etc.). | |
| Motorcycle Warning - The system shall be able to detect that the host motorcycle has fallen onto the road pavement, and send this information to a road-side device. | |
| Traffic Condition Warning - The system shall be able to warn drivers in a timely manner of moving incidents (e.g. road/winter maintenance vehicles, long/wide loads) via an in-vehicle display. | |
| Traffic Condition Warning -The system shall be able to send to vehicles following the host vehicle information about the traffic conditions, or the traffic signs, near the host vehicle, that it may be useful to receive in advance. | |
| Traffic Queue Detection - The system shall be able to locate the tail end of a traffic queue and estimate its speed of propagation. | |
| Traffic Queue Detection - The system shall be able to inform drivers, via in-vehicle and road-side devices, of slow moving obstacles (e.g. person, animal, slow vehicle) and advise on the appropriate action (e.g. speed and lane). | |
| Hazardous Location Notification - The system shall be able to warn drivers in a timely manner of incidents ahead (e.g. road works, accident, traffic queue) via an in-vehicle display. Where available and relevant this information shall include lane(s)/road section(s) affected and expected delay. | |
| Hazardous Location Notification - The system shall be able to warn the driver in a timely manner, via an in-vehicle display, of adverse road surfaces and weather conditions along the planned route. | |
| Hazardous Location Notification - The system shall be able to warn driver, via an in-vehicle device, of adverse driving conditions ahead (e.g. slippery road, low visibility, queuing traffic) and advise on the appropriate action (e.g. speed). | |
| Hazardous Location Notification - The system shall be able to warn drivers, via a road-side device, of adverse driving conditions ahead (e.g. slippery road, low visibility, queuing traffic) and advise on the appropriate action (e.g. speed). | |
| Hazardous Location Notification - The system shall be able to warn the driver, via an in-vehicle device, that the host vehicle is about to enter a curve that has been classified as a black spot for that category of vehicle, and recommend a suitable speed and trajectory. | |
| (X)FCD - The system shall be able to obtain information (values and status) from the host vehicle’s systems (e.g. ABS, ESP, Longitudinal and Lateral Acceleration, Speed, Wipers) without affecting the safe functioning of those systems. | |
| Hazardous Location Notification - The system shall be able to warn the driver, via an in-vehicle device, that the host vehicle is about to enter a section of road whose surface has less grip than normal (low "mu"). | |
| Hazardous Location Notification - The system shall be able to inform drivers, via an in-vehicle device, of obstacles in the carriageway and advise on the appropriate action (e.g. speed and lane). | |
| Hazardous Location Notification - The system shall be able to inform drivers, via road-side devices, of obstacles in the carriageway and advise on the appropriate action (e.g. speed and lane). | |
| Hazardous Location Notification - The system shall enable a road-side device to select and activate a traffic management strategy in the event of an incident (including poor driving conditions). | |
| Hazardous Location Notification - The system shall be able to send information about incidents ahead in the next section from a road-side device to drivers via an in-vehicle device. | |
| Hazardous Location Notification - The system shall be able to estimate the condition of the road surface in the vicinity of the host vehicle and send warnings to other vehicles. | |
| Hazardous Location Notification - The system shall be able to estimate the condition of the road surface in the vicinity of the host vehicle and send warnings to a road-side device. | |
| Hazardous Location Notification - The system shall be able to send information about incidents on the road network ahead from the TCC to drivers via an in-vehicle device. | |
| Hazardous Location Notification - The system shall provide "copies" of the traffic signs that are relevant to the current section of the road (e.g. speed limit, road hazards, junctions) to the driver at all times via an in-vehicle display. | |
| Hazardous Location Notification - The system shall be able to send to following vehicles "copies" of the traffic signs, or information about the local traffic (e.g. sudden congestion), that it may be useful to receive in advance. | |
| (X)FCD - The system shall be able to determine the environmental conditions in the vicinity of the host vehicle. | |
| (X)FCD - The system shall be able to determine the visibility in the vicinity of the host vehicle, and classify the cause of the reduction, e.g. fog, rain, darkness. | |
| (X)FCD - The system shall be able to infer XFCD, i.e. the road conditions (e.g. reduced friction, aquaplaning) and traffic conditions (e.g. vehicle breakdown, traffic incident), from the state of the host vehicle systems’ data (e.g. speed, acceleration, brakes, lights). | |
| (X)FCD - The system shall be able to maintain a database of dynamic fused XFCD from the host vehicle’s systems and sensors. | |
| (X)FCD - The system shall be able to send XFCD from the host vehicle to a road-side device. | |
7.4 | Cooperative Systems - Traffic Safety |
7.4.2 | Ghost Driver Management | |
| The system shall be able to detect that a (non-self-reporting) vehicle is travelling in the wrong direction along a “one-way” road (i.e. a ghost driver), and warn other vehicles “ahead” of that vehicle. | |
| The system shall be able to warn drivers in a timely manner of self-reporting ghost drivers via an in-vehicle display. | |
| The system shall be able to detect that the host vehicle is travelling in the wrong direction along a “one-way” road (i.e. a ghost driver), and warn/advise that driver to correct the situation. | |
| The system shall be able to detect that a vehicle is overtaking (i.e. in the wrong lane) on a two-lane road and that there is another vehicle approaching in that lane, and provide a warning to the drivers of both vehicles via their in-vehicle devices. | |
| The system shall provide "copies" of the traffic signs that are relevant to the current section of the road (e.g. speed limit, road hazards, junctions) to the driver at all times via an in-vehicle display. | |
| The system shall be able to send to following vehicles "copies" of the traffic signs, or information about the local traffic (e.g. sudden congestion), that it may be useful to receive in advance. | |
7.4 | Cooperative Systems - Traffic Safety |
7.4.3 | Lane Utilization | |
| The system shall be able to provide lane usage information to the driver via an in-vehicle display. | |
| The system shall be able to send to following vehicles "copies" of the traffic signs, or information about the local traffic (e.g. sudden congestion), that it may be useful to receive in advance. | |
| The system shall be able to provide lane restriction information (e.g. HGV, HOV) from outside the vehicle and to confirm that it is consistent with the information that has been sent directly to that vehice. | |
| The system shall be able to provide instructions not to change lanes to the driver via an in-vehicle device in order to stabilise the total traffic flow. These instructions may either apply to all types of vehicle, or to sub-sets. | |
| The system shall provide information to the driver via an in-vehicle display when auxiliary lanes are now available for use by that type of vehicle (e.g. hard shoulder running). | |
| The system shall ensure that the auxiliary lane is free from obstacles before it is released for use. | |
| The system shall be able to provide lane usage information to the driver via an in-vehicle display when there are temporary restrictions to lane usage (e.g. at road works). | |
| The system shall be able to advise a driver, via an in-vehicle device, which lane to use when passing an incident/accident. | |
| The system shall be able to advise a driver, via an in-vehicle device, where to stop safely (e.g. an appropriate exit lane, hard shoulder). | |
| The system shall provide "copies" of the traffic signs that are relevant to the current section of the road (e.g. speed limit, road hazards, junctions) to the driver at all times via an in-vehicle display. | |
7.4 | Cooperative Systems - Traffic Safety |
7.4.4 | Speed Management | |
| The system shall be able to recommend a safe speed limit according to the prevailing traffic, weather and road conditions based on the current legal speed limit. | |
| The system shall enable the TCC to display safety-related information (e.g. legal speed limit, recommended speed limit) to drivers via a road-side device. | |
| The system shall be able to compare the reported speed of a vehicle with the current speed limit and send a warning to that vehicle for display to the driver, via an in-vehicle device, that its current speed is greater than the legal speed limit. | |
| The system shall be able to compare the reported speed of a vehicle with the current legal speed limit and display a warning to the driver, via a road-side device, if its current speed is greater than the legal speed limit. | |
| The system shall be able to compare the reported speed of a vehicle with the current recommended speed limit and send a warning to that vehicle for display to the driver, via an in-vehicle device, if its current speed is greater than the recommended speed limit. | |
| The system shall be able to compare the reported speed of a vehicle with the current recommended speed limit and display a warning to the driver, via a road-side device, if its current speed is greater than the recommended speed limit. | |
| The system shall be able to warn the driver, via an in-vehicle device, that the host vehicle is exceeding the maximum speed limit. | |
| The system shall inform the driver, via an in-vehicle display, that there is a modification to the speed limit ahead, and the reason for it. | |
| The system shall provide "copies" of the traffic signs that are relevant to the current section of the road (e.g. speed limit, road hazards, junctions) to the driver at all times via an in-vehicle display. | |
| The system shall be able to send to following vehicles "copies" of the traffic signs, or information about the local traffic (e.g. sudden congestion), that it may be useful to receive in advance. | |
| The system shall be able to warn drivers, via an in-vehicle display, of different legal speed limits as a result of particular weather conditions. | |
| The system shall provide legal speed limits continuously to the driver via an in-vehicle display according to the type of the host vehicle and the lane in which it is travelling (Intelligent Speed Adaptation - ISA). A suitable message should be provided if the service provision cannot be guaranteed. | |
| The system shall provide recommended speed limits continuously to the driver via an in-vehicle display according to the type of the host vehicle and the lane in which it is travelling (Intelligent Speed Adaptation - ISA). A suitable message should be provided if the service provision cannot be guaranteed. | |
| The system shall enable the driver of the host vehicle, via an in-vehicle device, to receive safety-related information (e.g. legal speed limit, recommended speed limit) from other vehicles in the vicinity. | |
| The system shall enable the driver of the host vehicle, via an in-vehicle device, to receive safety-related information (e.g. legal speed limit, recommended speed limit) from a road-side device. | |
| The system shall enable the driver of the host vehicle, via an in-vehicle device, to receive safety-related information (e.g. legal speed limit, recommended speed limit) from the TCC. | |
| The system shall be able provide recommended speed limits from outside the vehicle, and to confirm that they are consistent with the limits that have been sent directly to that vehicle. | |
| The system shall enable a road-side device to display safety-related information (e.g. legal speed limit, recommended speed limit) to drivers via a road-side device. | |
7.4 | Cooperative Systems - Traffic Safety |
7.4.5 | Headway Management | |
| The system shall enable the TCC to calculate recommended headways for the current traffic and environment conditions. | |
| The system shall provide the current minimum headway for the current speed limit to the driver via an in-vehicle device. | |
| The system shall be able to recommend a safe minimum headway according to the current speed limit, traffic, weather and road conditions to the driver via an in-vehicle device. | |
| The system shall inform the driver, via an in-vehicle display, that there is a modification to the recommended headway ahead, and the reason for it. | |
| The system shall be able to warn the driver, via an in-vehicle device, that the host vehicle is violating the minimum headway. | |
7.4 | Cooperative Systems - Traffic Safety |
7.4.6 | Collision Warning | |
| The system shall be able to determine the type and current position of other vehicle(s) in the vicinity of the host vehicle, and to predict their future path(s). | |
| The system shall be able to compare the current trajectory of a vehicle with the road geometry and send a warning to the drivers of other vehicles that might be affected, via a road-side device, that an oncoming vehicle lane departure into their lane is imminent. | |
| The system shall be able to warn the driver, via an in-vehicle device, that another equipped vehicle is approaching the host vehicle from the front and in the same (partial) lane. | |
| The system shall be able to warn the driver, via an in-vehicle device, that another equipped vehicle is approaching the host vehicle from the rear in the same (partial) lane and, when possible, provide advice, e.g. change to a safe adjacent lane, accelerate. | |
| The system shall be able to warn the driver, via an in-vehicle device, that a slower equipped vehicle is ahead of the host vehicle and in the same (partial) lane and, when possible, provide advice, e.g. change to a safe adjacent lane, decelerate, brake. | |
| The system shall be able to warn the driver, via an in-vehicle device, that there is a stationary object ahead of the host vehicle and in the same (partial) lane and, when possible, provide advice, e.g. change to a safe adjacent lane, brake. | |
| The system shall be able to advise the driver, via an in-vehicle device, of a recommended speed and distance from the vehicle ahead, based on the speed and characteristics (e.g. mass, load being carried) of the host vehicle and of the vehicle ahead. | |
| The system shall be able to calculate the current and future trajectories of each vehicle and VRU approaching the host vehicle at an urban intersection and assess the potential for collisions with the host vehicle. | |
| The system shall be able to warn the driver of the host vehicle, via an in-vehicle device, of any collisions that could occur with other vehicles and/or VRU that are approaching an urban intersection. | |
| The system shall be able to use a road-side device to warn drivers of any collisions that could occur with other vehicles and/or VRU that are approaching an urban intersection. | |
| The system shall be able to calculate the trajectory of each vehicles and VRU approaching a T-junction, predict their future trajectories, assess potential conflicts and advise the driver on the minor road when to exit and join the main road. | |
| The system shall be able to determine that there is a high probability of a collision between the host vehicle and another vehicle. | |
| The system shall be able to receive the status of traffic signals/signs that the host vehicle is approaching. | |
| The system shall be able to provide advice to the driver approaching a junction, via an in-vehicle device, recommendations in terms of lane, speed, when traffic signal will change. | |
| The system shall be able to advise a driver, via an in-vehicle device, how to approach a complex urban junction, e.g. speed required to go through green phase, imminent red phase warning, reduce speed to avoid queuing traffic, another vehicle or VRU, recommended lane choice. | |
| The system shall be able to provide a warning to the driver, via an in-vehicle display, that other drivers ahead are performing an emergency brake manoeuvre. | |
| The system shall be able to inform vehicles behind the host vehicle that it is performing an emergency brake manoeuvre. | |
| The system shall be able to provide a warning to the driver, via an in-vehicle display, that other vehicles behind are behaving in a dangerous manner (e.g. over speed limit, below minimum headway). | |
| The system shall be able to warn the driver approaching a junction, via an in-vehicle device, of other equipped vehicles approaching that junction. | |
| The system shall be able to warn the driver approaching a junction, via an in-vehicle device, of an equipped emergency vehicle that is approaching that junction. | |
| The system shall be able to determine that the host vehicle is (about to) change lanes and warns the driver, via and in-vehicle device, if there are other equipped vehicles on potential collision path (e.g. motor-cycle in a blind spot). | |
| The system shall be able to determine that the host vehicle is (about to) overtake, or turn across the road, and warns the driver, via and in-vehicle device, if there are other equipped vehicles on potential collision path (e.g. motor-cycle in a blind spot). | |
| The system shall be able to compare the current trajectory of a vehicle with the road geometry and send a warning to that vehicle for display to the driver, via an in-vehicle device, that it is about to depart its lane. | |
| The system shall be able to compare the current trajectory of a vehicle with the road geometry and send a warning to the driver, via a road-side device, that it is about to depart its lane. | |
| The system shall be able to compare the current trajectory of a vehicle with the road geometry and send a warning to the drivers of other vehicles that might be affected, via an in-vehicle device, that an oncoming vehicle lane departure into their lane is imminent. | |
7.4 | Cooperative Systems - Traffic Safety |
7.4.7 | Vulnerable Road User Warning | |
| The system shall be able to warn the driver, via an in-vehicle device, that a VRU has been detected in a dangerous location by a system at the road side. | |
| The system shall be able to warn the driver, via an in-vehicle device, that a VRU has been detected in a dangerous location by a system on the host vehicle. | |
7.4 | Cooperative Systems - Traffic Safety |
7.4.8 | Emergency Vehicle Warning | |
| The system shall enable drivers to be warned, via an in-vehicle device, that there are one, or more, stationary assistance/emergency vehicles ahead of them. | |
| The system shall enable drivers to be warned, via a road-side device, that there are one, or more, stationary assistance/emergency vehicles ahead of them. | |
| The system shall enable an emergency vehicle to request a “blue wave” from those other vehicles that are in its path. | |
| The system shall enable an emergency vehicle to request a green signal for when that vehicle passes a controlled intersection. | |
| The system shall enable the trajectory of an emergency vehicle to be predicted and compared with the trajectories of other vehicles in the vicinity, and to warn the drivers of those other vehicles with a potential conflict, via an in-vehicle device. | |
| The system shall be able to inform the driver of the host vehicle, via an in-vehicle device, that an emergency vehicle is approaching, and in sufficient time to enable a “blue corridor” to be created by all equipped vehicles. | |
| The system shall be able to advise the driver, via an in-vehicle device, of an appropriate lane to use to create a “blue corridor”. | |
| The system shall enable the host emergency vehicle to “place” virtual cones around the site of an accident. | |
| The system shall enable the driver of the host vehicle to be advised, via an in-vehicle device, not to enter a zone defined by virtual cones. | |
7.5 | Cooperative Systems - Traffic Efficiency |
7.5.1 | Traffic Flow Optimisation | |
| The system shall enable a traveller to request and receive journey plans in advance, assess different plans according to certain criteria (e.g. vehicle type, travel time, cost, expected traffic density, planned events, facilities en route, parking), and to save one for future use. | |
| The system shall enable the service provided to the traveller to be passed from one TCC to another as the traveller moves from one area of coverage to another. | |
| The system shall be able to provide the driver, via an in-vehicle device, and on request, details of the (predicted) traffic situation in a defined area of interest, and for a time horizon, that has been selected by the driver. This information shall be updated at (selected) intervals. | |
| The system shall enable the driver to store data relating to the characteristics of the host vehicle for that trip (e.g. loaded weight, hazardous goods, (trailer) dimensions). | |
| The system shall be able to determine the characteristics of the host vehicle (e.g. Type, (Total) weight, Width, Length (including trailer)). | |
| The system shall enable the host vehicle to receive information from other vehicles about the goods being carried by those vehicles. | |
| The system shall be able to provide the driver via an in-vehicle device with a route to a selected destination that takes account of the vehicle type, the state of the traffic on the road network and any incidents/congestion (route options may be offered and one selected by the driver). | |
| The system shall be able to calculate an optimal speed for each type of vehicle through designated sections of the road network and provide that information to drivers via an in-vehicle device. | |
| The system shall be able to compute an alternative local route for vehicles approaching a location to be avoided (e.g. one where there is a traffic incident or congestion above a given severity), and does not create congestion downstream. The alternative route computed may depend upon the vehicle type, and may need to be changed as the incident or congestion to be avoided evolves over time. | |
| The system shall be able to inform the driver, via an in-vehicle device, that an incident has been detected ahead on the selected route and provide a revised route. | |
| The system shall be able to present an alternative route that avoids an incident or congestion to the driver via an in-vehicle device, and to update that route if necessary. | |
| (X)FCD - The system shall be able to send the intended route of the host vehicle (e.g. from a navigation system) to a road-side device. | |
| The system shall enable the TCC to instruct drivers, via an in-vehicle device, of an alternative route that should be followed (to avoid an incident). | |
| The system shall be able to “follow” those vehicles that have been provide with individual routes and to prove the effectiveness of those suggested routes, making changes to the algorithms that will be used in the future if necessary. | |
| The system shall be able to inform the driver via an in-vehicle device that part(s) of the selected route include one or more Flexible Lane Allocation sections. | |
| The system shall inform the driver via an in-vehicle device that the vehicle has departed from the selected route and a revised route has been requested. | |
| The system shall be able to calculate a predicted time for a total journey made up from separate links. The predicted time shall be updated regularly as the time for each link changes. | |
| The system shall enable the TCC to recommend the use of alternative routes for different types of vehicle. | |
| The system shall enable the TCC to command the use of alternative routes for different types of vehicle. | |
| The system shall be able to provide current and predicted journey times to another navigation device via an open interface (to enable dynamic navigation on the other device). | |
| The system shall enable the TCC to inform traveller information service providers of the current traffic management strategy. | |
| The system shall be able to analyse traffic data using an off-line simulation tool. | |
| The system shall be able to monitor the current inter-urban traffic and weather/environmental conditions, identify incidents, assess their impact, make short term predictions, and select and initiate an appropriate mitigation strategy. | |
| The system shall be able to use a simulation model for predicting the effects of implementing a given cooperative traffic management scenario. | |
| The system shall be able to manage the traffic in an area using a number of local semi-autonomous traffic management units, whose rules can be modified when required. | |
| The system shall enable the TCC to receive information about emergencies, e.g. eCall, ghost drivers. | |
| The system shall enable the TCC to obtain travel times from cellular telephone service providers. | |
| The system shall enable the TCC to inform drivers, via an in-vehicle device, about (foreseen and unexpected) incidents on the driver’s planned route. | |
| The system shall be able to warn the driver, via an in-vehicle device, of incidents in the urban road network as they are detected. | |
7.5 | Cooperative Systems - Traffic Efficiency |
7.5.2 | Advanced Adaptive Traffic Signals | |
| The system shall enable a road-side device to receive information on the status of traffic signals. | |
| The system shall be able to warn other vehicles that a green wave is in operation. | |
| The system shall be able to determine that the host vehicle is about to go through a red traffic signal, and to broadcast a warning to vehicles in the vicinity. | |
| The system shall enable the host vehicle to receive a message that another vehicle is about to go through a red traffic signal, and to provide a warning to the driver, via an in-vehicle device. | |
| The system shall enable the driver of a host vehicle to request a series of green phases from traffic signals (i.e. a green wave) for the route that is about to be taken. | |
| The system shall enable a traffic signal controller to receive a request for a green phase from an approaching vehicle; in the event that more than one conflicting request is received at the same time they shall be prioritised (e.g. emergency vehicles before private vehicles), possibly by the TCC operator. | |
| The system shall be able to determine the queue length in front of traffic signals in urban areas. | |
| The system shall enable the traffic signal controller to determine the expected arrival time of a vehicle at the junction using data received from that vehicle (e.g. current location and speed profile, estimated time of arrival). | |
| The system shall enable the traffic signal controller to inform the driver, via an in-vehicle display, that a green phase will be available when the host vehicle arrives at that junction; this includes the ability to warn that a green phase is not possible. | |
| The system shall be able to calculate an optimal speed for each vehicle through a section of road.
| |
| The system shall enable a traffic signal controller that has received a green phase request to inform downstream controllers that a green wave vehicle is approaching. | |
| The system shall be able to keep track of the speed profiles of green wave vehicles between signalised junctions. | |
7.5 | Cooperative Systems - Traffic Efficiency |
7.5.3 | Flexible Lane Allocation | |
| The system shall permit approved vehicles to use a section of a bus lane when it is not being used by PT or other specific vehicles (e.g. taxis and emergency services). | |
| The system shall monitor the usage of the bus lanes and record the identification, time and location of any vehicle that does not have permission to use it, for further processing by an enforcement agency. | |
| The system shall collect traffic information (e.g. number of vehicles, speeds, queue lengths, violation details) on the roads covered by flexible bus lane allocation for statistical purposes, and to improve the algorithms used to decide when non-PT vehicles can use the bus lane. | |
| The system shall be able to predict the usage of a particular section of a bus lane for a short time into the future (e.g.15 minutes). | |
| The system shall enable an approved vehicle that wishes to use a section of bus lane to provide its characteristics, destination and speed for lane use management. | |
| The system shall enable the driver to set the destination of the host vehicle that wishes to use a bus lane, if this cannot be provided by the navigation system for lane use management. | |
| The system shall be able to determine whether there is congestion on the normal road and, if so, whether a temporary licence should be given to the approved vehicle that is making a request to use a corresponding section of a bus lane without causing delays to scheduled PT vehicles. | |
| The system shall inform the driver whether a licence has been granted to become an approved vehicle and, if so, for how long it will remain valid. | |
| The system shall monitor the approved vehicles on the bus lanes and, if its licence has expired, that vehicle will be ordered to leave the bus lane at the end of that section. | |
| The system shall monitor the usage of the bus lanes, and if a green wave cannot be sustained for a PT vehicle, then approved vehicles shall be ordered to leave the bus lane at the end of that section, and no further licences will be granted until suitable conditions are resumed. | |
| The system shall monitor the congestion in each section of a bus lane and if a “critical/emergency” situation arises then approved vehicles shall be ordered to leave that section and the up-stream section(s) of bus lanes. | |
7.6 | Cooperative Systems - Value-Added & Other Services |
7.6.1 | eCall | |
| The system shall be able to detect that the host vehicle has been involved in an indecent/accident and to call the emergency services either automatically or on command of the driver/passenger (eCall) | |
| The system shall be able to send a request for assistance (eCall) message to the emergency services from a road-side device. | |
7.6 | Cooperative Systems - Value-Added & Other Services |
7.6.2 | Enhanced Route Guidance and Navigation | |
| The system shall be able to provide data to add to, or to replace, that used to form a digital map. | |
| The system shall enable the driver to (request and) receive, via an in-vehicle device, personalised on-trip information about incidents that may affect the planned journey. | |
| The system shall enable a traveller to request and receive, via an in-vehicle device, personalised on-trip alternative journey plans (to avoid an incident) and to accept/reject the proposal(s). | |
| The system shall be able to provide the pre-trip driver, via an in-vehicle device, with suggested alternative routes. | |
| The system shall enable a traveller to request and receive, via an in-vehicle device, on-trip information about facilities on, or near, the planned route (e.g. fuel stations, refreshment areas). | |
| The system shall be able to send O-D data, from the navigation system, and current location data from the host vehicle to the TCC to enable geo-referenced travel times to be produced. | |
| The system shall enable the service provided to the traveller to be passed from one Service Provide to another as the traveller changes areas of coverage. | |
| The system shall enable the driver of the host vehicle to provide the destination and personal settings for the journey (e.g. desired route, way points, special needs). | |
| The system shall enable a traveller to request and receive personalised journey plans in advance, assess different plans according to certain criteria (e.g. vehicle type, travel time, cost, expected traffic density, planned events, facilities en route, parking), and to save one for future use. | |
| The system shall enable the traveller information service provider to receive current inter-urban traffic management, and weather, conditions and planned events. | |
| The system shall enable the traveller information service provider to be provided with current an predicted inter-urban traffic conditions. | |
| The system shall enable the traveller to request and receive (anticipated) weather/environmental conditions on, or before, a planned trip. | |
| The system shall be able to calculate the expected time of arrival at a destination or way point based on the driver’s profile and the anticipated traffic conditions. | |
| The system shall be able to provide the driver, via an in-vehicle device, with a personalised route. | |
| The system shall be able to provide the driver, via an in-vehicle device, with an estimated time of arrival which is updated at regular intervals. | |
7.6 | Cooperative Systems - Value-Added & Other Services |
7.6.3 | Access Control | |
| The system shall enable the host vehicle to receive the information from a road-side device that it is about to enter a “sensitive are”, and then to contact the relevant Access Control Centre. | |
| The system shall enable the host vehicle to detect (e.g. using map matching) that it is about to enter a “sensitive area” and to contact the relevant Access Control Centre. | |
| The system shall enable the Access Control Centre to give, or deny, permission for an equipped vehicle to enter a “sensitive area”. | |
| The system shall enable the Access Control Centre to monitor all equipped vehicles, and the traffic, within a “sensitive area” and to send instructions to the drivers of the equipped vehicles. | |
| The system shall enable the Access Control Centre to store information about each equipped vehicle. | |
| The system shall enable the host vehicle to close the contact with the Access Control Centre when it leaves the “sensitive area” and to create a report for the freight vehicle driver. | |
7.6 | Cooperative Systems - Value-Added & Other Services |
7.6.4 | Service Continuity | |
| The system shall be able to exchange relevant information between adjacent TCCs and TICs to ensure the continuity of services for travellers. | |