Service definition
The provision of Road Weather Information Services cover in most cases the following dynamic information:
These pre-trip and on-trip weather information are important for the end users in order to optimize and better anticipate their journey ahead.
The main objective of providing weather information to the driver is improving the traffic safety and the efficiency of the European road transportation system.
If drivers are informed of the upcoming weather situation they are able to adapt their driving behaviour. Road weather information can be factored into both pre- and on-trip journey planning. This may avoid congestion and decrease the number of fatalities and accidents.
Service benefit radar
Figure 26 shows the typical functional and informational architecture of the “Road Weather Information Services” and gives a schematic overview of the typical system architecture required for both weather information and weather warnings.
Functional requirements:
Functional advice:
Note: Beside the provision of road weather information other services could benefit from weather information. This provision is not directly the scope of a Road weather information service and therefore the following list is to be seen as functional advice (not a requirement). However, a clear definition of interfaces is needed at a later stage in the development of any further specification: — The provision of the Road Weather Information service may also assist other services in the planning of (Multimodal) routes/ finding of alternative routes and assist in any decision by the user to switch mode (weather information as e.g. input parameter for multimodal services)
Interface requirement a): Safety Related Events as listed in Delegated Regulation (EU) 886/2013 (SRTI)
the service must provide coded information following the Delegated Regulation (EU) 886/2013 (SRTI) and as specified in the Document “Safety related message sets – Selection of DATEX II Codes, DENM Event Types, TPEG2-TEC Causes and TMC Events for EC high level Categories” including the following elements:
Interface requirements b): Real Time Related Events as listed in Delegated Regulation (EU) 2015/962 (RTTI)
Organisational Architecture / BusinessModel
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.4. More information on new models of cooperation between public and private partners can be found in chapter 4.1.4.2
Organisational advice:
Organisational requirements:
Common Look & Feel requirements:
To support the above-mentioned CL&FR3, the EGs take into consideration that the same symbols will be used as in the European weather warning system Meteoalarm, provided by Eumetnet, which is a network of public European weather services. With these symbols and warning levels mentioned above the warnings would already be coherent among most of the European weather services. The following pictograms are taken from the Austrian web-based service SWIS as one deployment in compliance with this service description:
Table 21: Recommendations for common Look & Feel: Weather warnings, exemplary icons
No specific requirement or advice
Information provision standards:
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 Road Weather Information services. This table is not end-user oriented as Table 22.
Level of Quality advice:
Table 22 gives the Level of Service recommendations for a Road Weather Information service. The background of this concept is descripted in chapter 2.6.
Table 22: Level of Service recommendations for Road Weather Information
Level of service requirement:
Note: The Level of Service to Operating Environment mapping table is not an outcome of a specific scientific analysis but an expert view output.
Table 23: Level of Service to Operating Environment mapping table (see also chapter 2.5.3 and ANNEX C)
[1] So there is no ambiguity in the decision making process a balance needs to be struck between what the system can recommend in terms of short term road maintenance activities and the contractual responsibilities of the Maintenance Providers.
[2] In 3.5.2.8 the optimum and minimum Level of Service for EU EIP operating environments are defined
[3] Level 1 could be merged with Level 2 to communicate only three levels towards the end users
[4] Level 1 could be merged with Level 2 to communicate only three levels towards the end users
[5] Level 1 could be merged with Level 2 to communicate only three levels towards the end users
[6] Level 1 could be merged with Level 2 to communicate only three levels towards the end users