Methodology

eCOMPASS phases

eCOMPASS is composed of three main vertical phases that concern the technical work as well as the pilots, assessment and evaluation of the project, and two horizontal phases that include dissemination and project management activities.

The three main vertical phases of the project (illustrated above) are:

1. The Requirements analysis and conceptual design phase, whose goal is to elicit information about user requirements and to conceptually design the use cases and application scenarios to be implemented. This phase includes work to be conducted in WP1.
2. The Technical development phase, which includes all technical activities in the project: investigation, and design of efficient algorithmic solutions (for routing private vehicles, fleets of vehicles and individuals using multi-modal public transportation) and implementation of the respective software components; design and implementation of the Content Gateway Module to enable interoperability between the eCOMPASS framework and external data sources; integration of individual modules into a unified framework. This phase includes work undertaken in WP2-WP5.
3. The Pilots phase that aims at developing usage scenarios applications for the different user target groups in order to implement the concept of eCOMPASS in various real-world situations. This includes work to be done in WP6.

Architecture

The next figure illustrates the overall abstract architecture of eCOMPASS and depicts the interoperations occurring between the basic modules of the eCOMPASS framework, as well as any external interacting entities and endusers.

According to the eCOMPASS abstract architecture diagram, the required data and information becomes available through the Content Gateway Module (CGM), whose role is to enable interoperability with external services and information resources. The CGM is equipped with appropriate data representation interfaces for all common data types that will be supported by the end user applications. Supported data include information from web services and web applications, GPS-based localisation sensors and data from other environmental sensors (e.g. to measure CO₂ levels). Other relevant information may become available through a web-based secure interface. The CGM will be developed as a distributed network of gateway nodes that will allow remote interoperability between available information resources and the applications to be developed for the end users. CGM resides on top of these applications and allows integration of data and services into them. The supported services to be developed within eCOMPASS include:

• Vehicle navigation services
• Fleet management services
• Multimodal Routing services

All of the above services will be developed within WP5 and will integrate the optimised vehicle routing algorithms and multimodal human mobility algorithms to be produced as the outcome of the technical workpackages WP2 and WP3, respectively. All of the above services will be provided in the form of mobile applications in order to allow interaction to the user on-the-go. As the user requests real-time content on the go (e.g. the urban traffic status) the CGM is activated and ensures that the right content is delivered to the right user on time. Appropriate information is also stored in a supported data repository that is used for caching purposes in order to allow more efficient and faster access to the requested data

Structure

The main objectives of eCOMPASS leads to a natural structuring of the overall work into eight work packages (WPs):

WP1 (leader: CERTH) The objectives of WP1 are to: (a) identify the end users (target group) as well as the use cases for each of the proposed mobile web services; (b) follow a formal user requirement analysis procedure in order to capture the user-related parameters and constraints and, hence, determine the UI, functionality and expected output of the services; (c) derive the detailed specifications of the eCOMPASS system architecture.

WP2 (leader: CTI) The aim of WP2 is to develop novel algorithmic methods that optimize single or multiple vehicle routing in urban spaces with respect to their environmental impact. It will also pursue new approaches that accommodate data uncertainty (due to measured travel times, CO₂ emissions, etc) and investigate the trade-off between data precision, information content, and solution robustness.

WP3 (leader: KIT) The aim of this WP3 is to provide novel methods for environment friendly routes in urban public transportation networks. In particular, (a) To develop mathematical sound models for various (context-aware) route-planning scenarios arising in the field of urban human mobility for city residents, commuters and tourists. (b) To provide algorithmic methods for multi-modal routes in urban transportation networks with respect to multiple criteria and high robustness with a strong focus on the environmental footprint of these routes. (c) To provide prototype implementations of the algorithms and methods within this WP. (d) To systematically collect test data and to perform an extensive experimental evaluation on the performance and quality of the various models and algorithms of this WP, thereby, addressing both server-based settings as well as mobile devices.

WP4 (leader: CERTH) The aim of WP4 is to implement the Content Gateway Module (CGM) and all required interfaces that will enable interoperability with external services and information resources. In terms of development this WP will encompass the development of appropriate interfaces to enable interoperability with web-based applications and services, as well as a querying mechanism in order to allow the submission of requests for content. Furthermore, appropriate measurements to safeguard data to be exchanged will be also addressed in this WP.

WP5 (leader: PTV) WP5 will materialize the theoretical work carried out in WP2 and WP3 developing 3 individual application prototypes: a private vehicle navigator, a fleet/logistics management system and a multimodal public transportation route planning service. Those prototypes will be integrated with the Content Gateway Module implemented in WP4.

WP6 (leader: TomTom) The objectives of WP6 are: (a) to define evaluation methods and assessment criteria for the project, (b) to test the reliability and usability of the selected implementation scenarios of WP1 and (c) to test the reliability and usability of the developed environmental-friendly route guidance system (WP5).

WP7 (leader: TomTom) The objectives of WP7 are: (a) Dissemination of project results to all interested actors. (b) Creation of a project User Forum, to guide the project research and adopt/spread its findings. (c) Formulation of sound marketing and business plans for the exploitation of project results. (d) Development of a viable scheme for constant project results application and update.

WP8 (leader: CTI) The objectives of WP8 are: (a) To ensure timely and qualitative achievement of the project results through technical and administrative coordination. (b) To ensure quality control of the project results and risk management of the project as a whole. (c) To provide timely and efficient administrative and financial co-ordination of the project and meet contractual commitments. (d) To co-ordinate the management of knowledge and innovation-related activities.