Task 1: UVAR data definition, structuration and exchange
On the basis of the draft DATEX profile defined by the DATEX II CEF programme support action, the contractor shall propose a definition and structuration of UVAR data and define and develop, together with DATEX experts,the necessary interfaces to enable the exchange of such data, taking into account existing databases and/or work already done by stakeholders (e.g. the FIA work on definition of UVAR data, the work undertaken by the DATEX II CEF Programme Support Action). As a minimum requirement, the contractor should address the following:
— define a structure for data sets relevant for the definition of UVARs, to be discussed with relevant stakeholders and validated with the commission services,
• define and develop the necessary interfaces (profiles) allowing the exchange of UVAR data in DATEX format, in cooperation with the DATEX II CEF Programme Support Action,
• define a template (Word file), coherent with the defined UVAR data structure, for providing UVAR information complying with the single digital gateway regulation,
• cooperate with the competent authorities of member states in order to ensure the accessibility of UVAR data on national access points,
— cooperate with the Single Digital Gateway (SDG) national coordinators.
Task 2: UVAR data collection and maintenance
The contractor shall propose functional, technical and organisational provisions for the collection and maintenance of UVAR data, describing in particular the roles of the various stakeholders and the information flows between them.
The contractor shall develop the necessary (open source and user friendly) tools to support these collection and maintenance, in view of making these tools available to the relevant stakeholders (including networks of cities) during and after the project.
The contractor shall collect and maintain during the lifetime of the preparatory action all UVAR data covered bythe geographical scope of the project.
— the contractor will prepare and implement an acceptance procedure for the tools and documentation, involving the Commission and relevant stakeholders,
— organisation of the collection and maintenance of all UVAR data covered by the geographical scope of the project by the various stakeholders, including their training and the definition of the validation processes. In case there are difficulties to involve these relevant stakeholders, the contractor shall ensure the data collection and maintenance of this data during the lifetime of the preparatory action.
Task 3:
This task includes the integration of UVAR data accessible in national access points in navigation service(s) and the test of the provision of related information services to final users. This task includes as well the specifications (to be validated by the Commission services) and organisation of a Hackathon for developers to use the data collected in Task 2 to develop specific apps providing information on UVAR.
Task 4: Definition of a strategy to ensure the sustainability of data collection and accessibility
— the contractor shall propose a strategy to ensure future sustainability of data collection and accessibility to re-users, including the roles of various stakeholders. This strategy may be different for each country in the scope of the pilot.
Task 5: Support tasks
This task concerns the consultation of stakeholders and awareness raising activities includes:
— involvement of stakeholders in the discussion and validation of the outcome of Tasks 1 and 2 via the organisation of min. 2 workshops,
— involving stakeholders for the data collection phase,
— involvement of stakeholders for the validation of the development of tools and documentation,
— a final conference where results from the pilot phase could be disseminated and discussed,
— possible synergies with other mobility related events to be explored,
— awareness-raising campaign in targeted countries showcasing the results of Task 1.3.