Skip to main content

ITS Observatory


Lessons learnt

The report will highlight complementary activities previously undertaken to capture information on previous and current ITS and wider transport projects. How these projects were presented and how outputs from existing case-studies were summarised will be analysed.. In particular the report will look at how key data such as a project summary was captured and how outcomes of the projects, such as benefits, impact returns on investment and how well they met their original objectives. This deliverable will be used in WP3 for improving the architecture and the design of the Software Platform, and also by WP7 when defining a sustainability strategy (D7.2)

Observatory Platform Design

This deliverable includes the graphical design of the user interface including the user interface / user experience elements, data entry elements and onscreen guides, hence linked to D2.5. Emphasis will be given to the ergonomic design of the graphical environment and elements of the platform. The final design will be again tested with selected participants to verify that it is according to their requirements (D4.4 and D6.2).

Operational plan

The Operational Plan will include the business plans and long term viability plans of WP7 in order to define the final operational structure of the ITS Observatory. The necessary specifications will be identified and set up (D3.1), including final system needs (hardware and software), hosting databases and web servers; the data-input processes will be finalised as well as the user interface in order for the platform to be fully operational. The plan will also include the identification of the roles and responsibilities of the stakeholders involved in order to fully adapt the business plans developed under WP7, hence it is related to D7.1 and D7.2.

Analysis of user requirements for input data into the Observatory

This report will capture a preliminary view of what national and local governmental stakeholders would like to have available to support their planning and decision making.

Deployment map

Adding value to the sustainability strategy will be the deployment map which will focus on integrating the business model into the service. The Deployment Map will illustrate how the service will be implemented and maintained. It will address key issues such as marketing and communicating to the targeted user groups. Further collaborative work and funding will be explored as well as considerations such as cost and quality of curation (input or access point, quality, accessibility and search extraction). The Deployment map will be closely related to the D8.2 and D8.4.

Evaluation of user experiences

A methodology will be developed to evaluate the users perceptions regarding the ITS Observatory. The report will also evaluate the usability and the effectiveness of the outputs of the ITS Observatory in terms of impacts, benefits and transferability of the reported case studies. This deliverable takes into account the overall outcomes of the organised stakeholders workshops; hence it is related to D2.5, D4.4 and helps to finalise the Operational plan (D6.1)

Quality Plan

The project quality plan will provide guidelines and procedures for managing efficiently the ITS Observatory project. The document will set out the role of each beneficiary and will define the Project’s Quality Management System. The quality plan will highlight a set of tasks and procedures aiming to ensure that the work and the results are of a uniformly high quality and meet the stated objectives.

Yearly MGT and progress reports

An interim report will be delivered after 50% of the work has been completed.The Annual Project Activity report is a summary of the project activity during the reporting period. This report covers the first year of the project from 1 May 2015 – 30 April 2016.

Final report on the status of content accessible via the Observatory

This document will give a summary on the data collection/selection activities and provide an overview (analysis) of the integrated documents. This deliverable is linked to D5.1.

Stakeholders mapping and Value Propositions

To ensure that relevant stakeholders are aware of and engaged with the ITS Observatory, this deliverable will present a comprehensive list of stakeholders, their expectations and the value proposition that the ITS Observatory will bring to their specific requirements. This deliverable is interacting with D2.1, D2.5 and D6.1.

Quarterly progress reports

A Quarterly Progress Report (QPR) will be provided every three months to the European Commission to state the progress of the project. The QPR consists of brief information on key project actions and provides an overview of progress made and problems encountered during the three months reporting period. In M12 the QPR will be replaced by the Annual Project Activity Report (D1.4). In M24, the QPR will be replaced by the Final Project Report (D1.5).

Final User requirements report

The report will provide requirements for the ITS Observatory and in particular the formats of outputs from the Observatory regarding level of description, assessed impacts, benefits and transferability of examples to another city/region/country. The deliverable will summarise the outcomes from D2.3 and D2.4 and will provide recommendations for the ITS Observatory specifications and Architecture (D3.1).

Final compilation of curated output

Once the operational plan established (D6.1) recommendations will be made to improve and iterate the design and specifications of the inputs and outputs for The Observatory. A continual feedback loop will be in place for the duration of the project. The results from this deliverable will be set up after the User perception Validation (D6.2) and the last stakeholder Workshop (WS3)

Observatory Platform specifications and architecture

Based on the outcomes from D2.5 this deliverable will provide specifications for the ITS Observatory. The specifications are distinguished in data, algorithms, interface and software platform. The report will specify how to present data to users and it is related to D3.2.

Risk Management plan

The Risk Management Plan addresses project internal and external risks and defines corrective actions for each identified risk. The Plan is applicable to all the activities related to the project and thus all partners must comply with the processes listed in this deliverable.

Stakeholder consultation contact list and engagement tools

A list of key stakeholders who will need to be engaged to capture their knowledge and requirements. The primary purpose is to obtain a picture of the level of experience of practitioners and their sectors of activity, to identify their main policy reasons for deploying ITS, to see what tools are used at present for ITS decision-making, and to identify problems encountered by stakeholders regarding decision-making. This deliverable will be used for D7.1, D7.2, D8.2 and D8.4.

Communication and Dissemination plan

The purpose of this document is to plan the communication and outreach activities that will help to widely disseminate the project results and achievements. The Communication Plan is conceived to provide the major rules and guidelines aimed at promoting a structured, effective and integrated communication identity to the ITS Observatory; hence closely related to D2.2, D8.4, D7.2 and D7.3.

Sustainability strategy

This report will identify potential revenue streams and support opportunities for long term continuation of the ITS Observatory. It is a key outcome from the project as developing the ITS Observatory in such a way as to establish a position and maintain continuity is the fundamental objective of all involved. The outcomes from D2.1 and D2.5 are fundamental for the viability of the Sustainability Strategy.

Analysis of output data from the Observatory and guidelines for the quantification of impact data

This report will outline users ‘expectations regarding the ITS Observatory (evaluation studies, best practices, benefit data, guidelines, investment costs, technical cost, cost-benefit calculations….). The objective is to investigate the format of the outputs that the ITS Observatory should deliver.

Strategy for content provision & User guidelines for content entry

This document is user guidance for data entry and is accessible to anyone who would like to enter data in the Observatory.

Final report

The project will also complete a final report, which will detail the project results and benefits together with the strategy for long-term sustainability. The report will also provide a summary of the actions for the period from 1 May 2016 – 30 April 2017.

Project website

The website will cater for all stakeholders and will provide a description of the project objectives and priorities, main areas of activity, profiles of consortium partners with links to partners’ websites, pilot sites, Fora, news and events, project results, links to current and past projects and other relevant websites. The specifications of the project website will be defined in D8.3.


The flagship brochure will be produced at the beginning of the project, illustrating the project concepts, to be distributed at workshops and external conferences, meetings and events, etc. The brochure will be updated as necessary in the course of the project. It may be decided by the consortium that brochure(s) or flyer(s) are translated into the local languages of EU Member states. The brochure will be defined in D8.2 and integrated in the D3.2 Observatory Platform design.

Visual identity

The visual identity will not only include a logo, but also a set of graphics/illustrations that will help to convey the benefits of the project to specific stakeholders. It will also be the basis for the identity of the web-visual identity developed in WP3, WP4 and WP5. It will also be the basis for the D3.2 and D4.3. All the deliverables developed after M2 will integrate the visual identity established by D8.1.

External liaison plan

The External Liaison Plan will identify the relevant RDI projects and reach out to them in order to engage a discussion and knowledge exchange on the results. This report will specify how the liaison with external entities will be done, by whom, when and what the liaison objectives for cooperation with a specific partner are. In order to optimise the results of liaison efforts, project consortium shall in this document identify the key liaison partners (other projects, companies, organisations). This document will be updated throughout the project, when needed. This deliverable will use the findings from D2.2 and will help defining D7.1 and D7.2.

Development of software platform

Technical report documenting the overall ITS Observatory platform, its components and its services. The ITS Observatory platform (software) will be delivered together with the report. This deliverable takes into account the results from D2.3, D2.4 and D2.5.

Technical validation

Technical report documenting the results of the three-stage ITS Platform validation procedures. The technical validation is related to D2.5 and the 2 stakeholder workshops organised before M11 (WS1 and WS2).

Deployment of Data Base

A technical report including details about the Schematics of the Observatory’s database will be provided, together with the database itself (the software). This deliverable will facilitate the start of the data entry which is a milestone (M5.1) together with the provision of D5.1.

Framework for data collection

Once the technical validation finalised (D4.4), this report will provide an overview of the developed document classification system and the quality standards.

Development of onscreen guides

Technical report including details about the Observatory’s intuitive onscreen guides related to data search, data entry and data view will be provided together with the finalised onscreen guides (software).

Searching for OpenAIRE data...