Annex 1 INSTRUCTIONS FOR IMPLEMENTATION OF TRAFFIC MANAGEMENT PLAN A TMP is the pre-defined allocation of a set of measures for a specific situation in order to control and guide traffic flow as well as to inform road users in real time and provide a consistent and timely service to the road user. Initial situations can be unforeseeable (incidents, accidents) or predictable (recurrent or non-recurrent events). The scenarios and actions are always selected on a temporary basis. The main procedure is to react to the event ac cording to the TMP instructions. For this particular cross-border area , the following incidents are estimated to b e likely and the relevant scenario and action are to be selected. Table 1 Potential incidents on E67 Via Baltica cross-border section 1. S c enario selecti on criteria The m ain scenario selecti on criteria are traffic and weather impact. For that , two tables ha ve been created . The main criteria for traffic - dependent scenarios is delay from normal traffic. The longer the delay is, the more actions are needed. The table includes actions on white and grey background s; the first means activities within the country and the second cross-border - coordinated activities. The following actions may be required : Monitoring – monitoring of the situation through available information channels and sources ; no need for special action Information sent to VMS s – if the event has a local impact , it is enough to use the closest VMS s for public information, if available. Information sent to social media and TI portals – if the event ha s a broader impact , it is necessary to provide the information to a wider audience than only drivers close to the event . In this case , the traffic information portals https://tarktee.ee and https://lvceli.lv/ and social media channels such as Facebook and Twitter are to be used. Press release – in more serious situations, special press releases are to be prepared with public relations departments to make the news more official and to allow it to be broadcast more widely . Information sent to neighb ouring country – in cases of a certain traffic delay and/or road/weather condition in the border section , information exchange between the TMC and TIC is to be started. Emails and phone calls are usually used , but for a short chat other messaging services can be considered. Recommendation to avoid section (park or reroute) – if traffic is remarkably disrupted and considerable delays are there or expected or road conditions are very poor or severe weather conditions are forecasted, it is appropriate to recommend stopping HGV traffic in order to prevent serious accidents and additional obstacles. There is a limited amount of parking spaces available (see Annex 7) i n the section , and therefore the broad shoulder section between Riga and Tūja or the 1 km 4-lane road exiting from Pärnu towards Riga could be another option for temporary parking. Stop traffic and rerouting – if the event cause s traffic delays for more than two hours or extreme weather conditions are expected , traffic regulatory measures should be made ready, including HGV forced suspension or detouring. In this case , the leading role will be played by the police in close cooperation with road maintenance operators. The TMC and HICERC in Estonia and the TIC in Latvia must play supporti ng role s for those institutions to ensure that the information about the traffic reorganization s is delivered promptly and without error to the parties and road users. Table 2 Traffic - dependent scenarios and actions If a traffic delay is or expected to be less than 10 minutes outside of the norm, then simple monitoring of the situation is needed. When a traffic delay is more than 10 minutes but less than 30 minutes, VMS information is recommended to be add ed . At the moment , there are two VMS s in Estonia where a more detailed description of the event can be displayed. One sign is located at the southern border of Pärnu in the south at km 134.2 and another is located near the border in the north at km 191.8. VMS on E67 Tallinn- Pärnu - Ikla at km 134.2 , south VMS on E67 Tallinn- Pärnu - Ikla at km 191.8 , north In Latvia the typical VMS consist s of two full- matrix VMS displays, where the upper sign c an be used to show a warning sign and the lower sign can be used to show the length of the event or distance to the event. VMS on E67 Rīga - Ainaži at km 1 0.4 , north Some examples of how full - matrix displays can be used to warn road users of potential danger ahead : Source: Hb-V321 Variable trafikkskilt, Norway ; 2100065-v-09-vaihtuvien_opasteiden_kaytto, Finland 13.05.2019 E67 Tallinn- Pärnu - Ikla road at km 119, total road closure, traffic accident, rerouting If the traffic delay is or expected to be longer than 30 minutes in the cross-border area, in addition to informing the public , cross-border information exchange is required . Relevant activities should be started immediately when the situation i s likely and before escalation of the event. The main criteria for weather - dependent scenarios are weather and/or road conditions that have been forecasted or have already occurred . The weather scenarios are mainly based on National Weather Service announcements , which are available on the website www.meteoalarm.eu . The main criteria for acting out the scenarios can be found in Annex 3. Table 3 Weather - and road condition - dependent scenarios and actions 2. Completing the TMP The TMP is introduced for every event separately and final completion is done according to the particular situation. The TMP form consist of two parts : permanent and variable . The p ermanent part ( Table 4 ) will not change from event to event and give s general information about the location, type of the TMP, parties involved and status of the plan. The variable part ( Table 5 ) should be completed every time according to the event situation and location, corresponding traffic and weather condition and for particular situation s’ selected scenarios and actions. Road sections and bypass options can be selected from the table in Annex 6 , and parking options are given in Annex 7 . The f ulfilled TMP is used for guidance and documentation of local TMC/TIC activities as well as for informing the other TMC/TIC about planned activities. TMP form completion is recommended in all cases when there is a traffic - disruptive event or a potential risk for event escalation. In more severe cases, when cross-border activities are required , TMP form completion and sharing with the other centre is mandatory. Two examples have been developed to facilitate the completion of the TMP form ( Table 6 and 7 , full version in Annex 8 and 9 ). Although the TMP examples may be very general, they will start cross-border cooperation for a particular event. It is expected that there will be continuous information exchange during the event and all changes in situations which cause changes in scenarios and actions should be announced . Table 4 TMP permanent part Table 5 TMP variable part Table 6 Example 1 - Operational part of TMP, partial road closure in Latvia Table 7 Example 2 - Operational part of TMP, total road closure in Estonia
Annex 3 J oint data exchange tool description Partners of SMART E67 project have adjusted their Traffic Information Centres infrastructure with software for VMS ( Variable Message Sign ) management. Central software can communicate with new field equipment in applicable and expected manner. According to technical and functional requirements to each partner ’ s Traffic Information Centre, different vendor software was selected. Latvian State Roads have implemented intelligent transportation system FITS ( Future Intelligent Transportation System ) by vendor WeAreDots, which is a web application that retrieves data from road sensors and variable message signs. Estonian Road Administration have implemented traffic mana gement software Omnia by vendors Swarco and IB Foor (local support partner). The software is a web application that retrieves data from road sensors and variable message signs . VMS and RWS data exchange between partner’s systems and thi rd- party systems is provided in Datex II format. Datex II is a standardised e-language for traffic and travel data exchange between traffic control centres, traffic information centres and service providers. Many of priority areas and services mentioned in European ITS Directive include Datex II. (More information in https://datex2.eu/support/ITS_directive ). Description of Datex II data provided by Latvian State Roads (LSR) FITS provides following information services to external parties in Datex II version 3 format: Current RWS (Road Weather Station) location coordinates ; Last known RWS measurement data at the given locations – road surface condition information, air temperature and humidity information, visibility, precipitation and wind information; Last known road condition assessments at the given locations along with road surface measure ment data and road camera images; Current Variable Message Sign (VMS) location coordinates; Current Variable Message Sign indication data at the VMS locations. Information from all RWS in Latvian State Roads network is available (Not only E67 RWS). The client system may call services (1) as necessary or (2) on a regular basis, for example, to populate the client system's dashboard with the latest meteorological data. Each service: Is accessible via HTTPS only and standard SSL/TLS port 443. Responds to both HTTP GET and POST verbs. Requires basic authentification header in request. Other functions and full web developers guide - a document for data clients, is provided after LSR Datex II data subscription. Links for LSR Datex II services are in Table 1. Description of Datex II data provided by Estonian Road Administration (ERA) Estonian Road Administration Datex II service is available through the traffic information portal tarktee.ee . DATEX II services of Estonian Road Administration : Important road safety data ; Traffic restriction data ; Road camera pictures , l ocations of road cameras ; Measurement results of road weather stations , l ocations of road weather stations ; Measurement results of traffic counters , locations of traffic counters ; Current Variable Message Sign (VMS) location coordinates (service in testing, to be made public by the end of 2019); Current Variable Message Sign indication data at the VMS locations coordinates (service in testing, to be made public by the end of 2019) . LSR and ERA Datex II services Both partners are subscribed to each other Datex II services and the data content is well known. Data are exchanged in Client Pull mode (data delivery initiated by the Client, where data is returned as a response) and used in accordance with the Traffic Management Plan and VMS user guidelines. Links to Datex II services are shown in Table 1. Table 1. LSR and ERA Datex II data Description LSR Datex II services ERA Datex II services RWS location data https://fits2-datex-lvc-prod.azurewebsites.net/rws/location/content.xml https://tarktee.mnt.ee/api/v1/datex/measurementSites RWS measurement data https://fits2-datex-lvc-prod.azurewebsites.net/rws/measureddata/content.xml https://tarktee.mnt.ee/api/v1/datex/weatherData Road condition assessments and road camera images https://fits2-datex-lvc-prod.azurewebsites.net/rws/situation/content.xml https://tarktee.mnt.ee/api/v1/datex/roadCameraImages VMS location data https://fits2-datex-lvc-prod.azurewebsites.net/vms/location/content.xml https://tarktee.mnt.ee/api/v1/datex/vmsinventory (service in testing) VMS indication data https://fits2-datex-lvc-prod.azurewebsites.net/vms/vms/content.xml https://tarktee.mnt.ee/api/v1/datex/visualisedstatus (service in testing) Important road safety data - https://tarktee.mnt.ee/api/v1/datex/safetyData Traffic restriction data - https://tarktee.mnt.ee/api/v1/datex/restrictions For example, ERA and LSR data are used by third-party commercial service - TIK service from Teede Tehnokeskus https://tik.teeilm.ee/ .
AGREEMENT ON IMPLEMENTATION OF CROSS BORDER TRAFFIC MANAGEMENT PLAN ON EUROPEAN ROUTE E67 Estonian Road Administration , regist ration No 70001490, location Teelise 4, 10916 Tallinn ( hereafter ERA), represented by Director General Priit Sauk on the basis of the statutes a nd Latvian State Roads , regist ration No 40003344207 , location Gogola 3, LV-1050, Riga ( hereafter L SR ), represented by Chairman of the Board Janis Lange on the basis of the Decision of The Board hereafter P arty or together P arties , whereas : (i) Traffic Management Plan (hereafter TMP) is the pre-defined allocation of a set of measures to a specific situation in order to control and guide traffic flows as well as to inform road-users in real-time and provide a consistent and timely service to the road user (certain TMP approach and some of its activation technical tools have raised from the LV/EE joint project SmartE67 ) ; (ii) The vision of the European Core Service “Traffic Management Plan for Corridors and Networks” is the effective delivery of traffic control, route guidance and information measures to the road user in a consistent manner, thus increasing the performance of transport infrastructure by adding the potential of cross-border, network or multi-stakeholder co-operation, when needed (iii) Route E67 belongs to the Trans-European Transport Network (TEN-T) and is the main connection road between Baltic States and Central Europe for freight and passenger transport; (iv) Estonian Road Administration in Estonia and Latvian State Roads in Latvia are responsible for providing traffic management and information services on route E67; have signed this agreement on implementation of cross border traffic management plan on European route E67 (hereafter Agreement ) to the following : 1. Documents of Agreement 1.1. The documents of the Agreement consist of this Agreement and its annexes, which form an integral part of the Agreement. 1.2. At the moment of signing, the Agreement has the following Annexes: 1.2.1. Annex 1. Instructions for implementat i on of TMP; 1.2.2. Annex 2. TMP template; 1.2.3. Annex 3. Joint data Exchange tool description. 2 . Implementation of TMP 2 .1. Parties will implement TMP in case of traffic disturbances and weather related driving conditions according to the instructions and criteria s et in A nnex 1 (providing the proper adaptation of their own operational procedures to TMP methodology) . 2 .2. Parties will inform each other in case of major traffic disturbances and severe weather conditions by e-mail according to the conditions set in A nnex 1 using the TMP template in Annex 2 . Notice will be sent to the other Party as soon as possible. 2 .3 . Parties will implement TMP on E67 r oute section from Pärnu to Skulte ( Estonian state road no. 4, km 133,4 -192, Latvian state road A1, km 40,3-101,6) . 2 .4. Contact Points for TMP information change are: E RA contact point : e-mail:
[email protected] , tel. +372 612 0100 ; L SR contact point : e-mail:
[email protected] , tel. +371 27872066 . 2 . 5. Parties shall provide their respective road weather and variable message sign data through Datex II service according to the description in Annex 3. 3 . Costs 3 .1. All costs regarding the Agreement are beared by the Parties themselves unless agreed otherway . 3 .2. The Parties do esn’t h o ld any mutual financial obligations upon the Agreement . 4 . Termination, expiry and amendments of the Agreement 4 .1. The Agreement shall enter into force just after signing procedure with indeterminate duration . 4 . 2. The Agreement or its annexes can be amended by agreement of the Parties in written form and signed by representatives of the Agreement . 4 . 3 . A Party may cancel the Agreement by notifying the other Party at least 30 days in advance in written form. 5 . Contact persons of the Parties 5 .1. ERA contact person: Siim Vaikmaa, tel: +372 515 9582; e-mail:
[email protected] . 5 .2. LSR contact person: Lauris Vilnitis, tel: +371 63350260 ; e-mail:
[email protected] . 5 .3. In the event of the P arties contact person being absent, a replacement contact person may be appointed. 5 .4. If a Party's contact person changes, the other Party shall be immediately informed . 6 . Other conditions 6 .1. The content of the Agreement is public information, unless otherwise provided by law. 6 .2. Any differences between the Parties arising under or relating to this Agreement shall be settled through consultations between the Parties. 6.3. Any notices regarding the Agreement shall be given in writing and shall be delivered by e-mail to the contact persons of the Parties. 6 . 4 . The language of communication between the Parties shall be English. 6 . 5 . The Agreement is signed digitally. 7 . Props and s ignatures of the Parties Estonian Road Administration Latvian State Roads Teelise 4 G ogol a iela 3 10916 Tallinn LV-1050 Riga Estonia Latvia E-mail:
[email protected] E mail:
[email protected] Phone: (+372) 611 9300 Phone: (+371) 670 28169 / signed digitally/ / / signed digitally/ / Priit Sauk Janis Lange Director General Chairman of the Board