“Forecast and Real-time Event Information Services” are defined as the provision of information about both expected and unexpected events to road users on identified segments of the road network and interfaces. This predictive or real-time information could be provided on-trip and pre-trip using different information channels, accessible by the road user via different end-user devices. The service may comprise common information as well as individual (personalised, ondemand) information.
“Events” are defined as – expected or unexpected – abnormal situations, which may lead to adverse effects on the road regarding to traffic safety, efficiency and environmental effects.
The main objective of providing forecast and real-time event information and warnings to the road user is improving the safety and the efficiency of the network.
Expected and unexpected events can develop into a traffic bottleneck, due to abrupt reactions of uninformed drivers. However, if those drivers know the upcoming traffic situation in advance they would be prepared and could pro-actively adapt their speed and following distance, thus preserving smooth, stable and safe traffic flow.
Forecast and Real-time Event Information services allow traffic information to be factored into both pre- and on-trip journey planning. This can alter the departure times, assist the driver to take more effective routing decisions, where appropriate, search information for another means of transport or even alter the decision to travel.
The provision of information to drivers enhances the travelling experience even if the information does not directly have an impact on network efficiency or safety. Better-informed drivers tend to be calmer and hence more concentrated. Other impacts can be the increased mode share of public transport, when drivers decided to select another mode of transport for their trip and reduced air pollution.
Service benefit radar
ITS service key words:
The function of the service is to provide forecast and real-time event information to road users either pre-trip or on-trip. This may be demand-responsive or initiated by the information providers.
In Europe, both private and public information providers are involved in this information provision (see organisational requirements). More information on the cooperation between public and private partners is provided in chapter 184.108.40.206.
Based on the TISA/CEDR value chain, Figure 21 shows the typical functional architecture of a “Forecast and Real-time Event Information service”, consisting of four subfunctions:
Subfunction 1 “Detection and content collection”
Devices, tools and methodologies for traffic data collection are not covered by this service description. They depend amongst other things on the particular data collection system used and are left to the operator to select.
Note: “Detection and content collection” is not only done by automatic data collection systems. “Events” are also announced/signalled by so-called ‘non-technical sources’ such as police, fire brigades, local authorities, road users as well as ’generated’ by actions of the road operator.
Sub-function 2 “Content pre-procession”
Note: Content pre-procession includes data validation and certification.
Within Europe different methodologies exist to aggregate collected data and other input information for forecast and real-time event information. These methodologies are not covered by the present guideline and are left to the operator to select. They depend amongst others on the particular data fusion and processing system used and particular traffic model applied.
Sub-function 3 “Info-service provision”
Different service providers in accordance with specific business models carry out information provision. The information provision to the road user on end-user devices has to be done using various information channels. When providing customer-oriented Forecast and Real-time Event Information services, the users’ benefit can be increased by providing event information in combination with general traffic information (i.e. see “TTIS-02 – Traffic Condition and Travel Time Information”, “TTIS-03 – Speed Limit Information” and “TTIS-04 – Road Weather information”).
Sub-function 4 “Info-servicepresentation”
Interface requirements a): Safety Related Events as listed in Delegated Regulation (EU) 886/2013 (SRTI)
Interface requirements b): Real-time Related Events as listed in Delegated Regulation (EU) 2015/962 (RTTI)
Organisational Architecture/Business Model:
A general overarching description of the key actors, their roles in the value chain and the related conditions for TTI service provision are outlined in Chapter 3.1. More information on new models of cooperation between public and private partners can be found in chapter 220.127.116.11
Note: Even though partners involved in the service can be either public or private road organisations as well as public or private service providers, who are legally autonomous in varying degrees and in the international context even work on different national laws, it is not required to define organisational aspects on a legal and binding basis.
Common Look & Feel requirements:
It is up to the deploying road operator to ensure that signs are well and widely understood by the road users, even if some local variations to the Vienna Convention should be adopted in some countries.
No specific requirements or advice.
Information provision standards a): Safety Related Events as listed in Delegated Regulation (EU) 886/2013 (SRTI)
The “Levels of Quality table” for the definition of quality criteria for RTTI and SRTI services, which differentiates data quality into “basic”, “enhanced” and “advanced” (for detailed information see Quality of S Real-Time Services – Quality package) reflects the requirements for the data quality which are needed for Forecast and Real-time Event Information services. This table is not end-user oriented as Table 16.
Level of Quality advice:
Table 15 gives the Level of Service recommendations for a Forecast and Real-time Event Information service. The background of this concept is descripted in chapter 2.6.
Table 15: Level of Service recommendations for Forecast and Real-time Event
Level of service requirement:
Table 16: Level of Service to Operating Environment mapping table (see also chapter 2.5.3 and ANNEX C)
 Definition and description of the key actors: see 3.1.4