• GET Service

Co-funded by the 7th Framework Program of the European Union
 

Public Deliverables

 
  • Click here to download GET Service's public presentation in .pptx format. The document presents the objectives that GET Service aims to achieve as well as the challenges that the project confronts.

  • D1.1: Use Cases, Success Criteria and Usage Scenarios: The document serves as an “introductory chapter” for the whole project and defines some of the basic concepts the final platform has to support. In particular, the objective of this document is to describe real-world transport processes (how they are carried out, which process steps have to be performed) and to identify the stakeholders that are involved. In total, five usage scenarios are presented, each one depicting a particular logistics chain from different industries and focusing on different transport modes.

  • D1.2.1: Data Model. This deliverable presents the data model for the GET Service project. The data model provides definitions for the concepts that are used in the context of the project. As such, its primary goal is to facilitate an understanding of the data entities that are being exchanged both within the project and, once the GET Service platform becomes operational, between the platform and external data and service providers.

  • D1.3: CO2 Calculation Methodology. The increasung demand for transport in Europe results in increasing emmisions of carbon dioxide (CO2) and other greenhouse gases (GHG) which have negative impact on the environment. Since the amount of released GHG emissions is becoming an important topic for companies, it is necessary to search for solutions that would reduce the amount of GHG emissions for transport. This is also one of the objectives of the GET Service platform which should provide tools for making the transport more efficient and environmentally friendly reducing the amount of released GHG emissions. In order to be able to measure the achieved reductions of GHG emissions, it is necessary to define an emission calculation methodology. Therefore the goal of this document is to define the methodology which will be used for calculating GHG emissions for the GET Service platform. 

  • D1.4.1: Evaluation plan. The objective of the GET Service evaluation plan is to track the project progress as well as provide a feedback loop from the end users to the software in order to increase its functionality.

  • D1.4.3: End-user Tests. The assessment of projects is a very fundamental element in controlling the progress and the improvement of any project. The evaluation shall ensure if project objectives are being met. GET Service, as it is defined in its name1, intends to reduce greenhouse gas (GHG) emissions in logistics with improved planning algorithms as well as a better consideration of intermodal planning. The evaluation concept was introduced in the context of the evaluation plan in D1.4.1. The second evaluation cycle is documented in this deliverable.

  • D2.1: Report Message Standards. In this deliverable the following aspects are covered:
    • The role of the architecture
    • The set-up of the GET Service architecture
    • Compliance to existing message standards / architectures
    • Relation to e-freight

  • D2.2.2: Standardized Interface Definitions.  In this deliverable, the main dependencies between the GET Platform components, and the resulting interfaces are identified. By using well-defined interfaces, the functionality of a subsystem is exposed, while its internal structure and internal behaviour remains hidden. This prevents unwanted dependencies between subsystems, and ensure loose coupling. A high degree of unwanted dependencies in a system makes change over time difficult and thus costly. This ensures that the GET Service platform can both meet the required characteristics, and that it can connect to existing systems that are already operational and therefore represent considerable investments. The use of well-defined interfaces also enables the GET work packages to develop their software independent from each other, while maintaining the overall consistency and run-time behaviour of the GET Platform.

  • D3.1: PC-Based aggregated transportation planning and control services. D3.1 describes the PC-based transportation planning and control services as they are being developed within the GET Service project. The services and the application are available as prototype components with standardized interfaces to the GET service platform and the different elements and services. The main content of this short documentation is an overview about the user interface as well as interface descriptions.


  • D3.3: PC-Based real time transportation control services. This document describes the PC-based real-time transportation and control services as they are being developed within the GET Service project. The services and the application are available as prototype components with standardized interfaces to the GET service platform and the different elements and services. The main content of this short documentation is an overview about the user interface as well as interface descriptions. The main focus in this deliverable is to provide real-time services taking into account actual TI especially on road infrastructure.

  • D3.4: GET Service Applications Specifications. The scope of this deliverable is to present the updates developed for the Mobile Application as this was described in D3.2 as well as present the Match Making Application, its features and its functionalities. The main scope of the latter is the aggregation of all information generated from the mobile applications and its presentation to the users through a web-interface. This application is a complementary to the GET Service Platform and can be used as a standalone system in combination with the mobile application. This document includes also design and implementation details.

  • D4.1: Language and Meta-Model for transport processes and snippets. The goal of this document is to develop a language for modeling end-to-end transport processes as well as for modeling their constituent snippets in isolation. This is preliminary to create transport process models and to use them to enable transport-typical use cases. In the document such a language, called BPMN-T, is developed, proposing a formal meta-model for it and explaining how it can be used.

  • D5.1: A Review of Transportation Planning Tools. This document is prepared to see the whole picture of the state of the art transport planning tools for the Green European Transportation (GET Service) project. Around 49 Transportation Management System (TMS) solutions and four online freight platforms are available in the market. This report used the available professional and academic literature, software vendor websites, etc. to identify these tools, and review their functionalities with regards to several dimensions. The focus on the use of the planning tools in real life environment is extremely important. The real life world is dynamic and stochastic and information on this setting should be available via the GET framework as planned.

  • D5.2: Aggregated Planning Algorithms. The deliverable's goal is to develop an offline model which meets several requirements predefined by GET Service and integrate it into prototype. The aim of the planning model is to minimize the likeness of re-planning and as a consequence make schedules more applicable in real-lief environment.

  • D5.3: Real-time Planning Algorithms: The deliverable’s goal is to develop an online planning model which meets several requirements predefined by GET Service platform and integrate the model into a prototype. The aim of this online model is to enhance the plans computed by the offline model with real-time data to improve planning quality. Besides, disrupted network sections can be avoided due to the implementation of online data which, consequently, can contribute to lower CO2 emissions.

  • D6.1: Taxonomy of transportation-related events. The objectives of this document is to sudy the events that may occur in transportation and how they will look like, as well as how they can be captured and processed by a system similar to GET Service Platform.

  • D6.2: Information Aggregation Engine Architecture.  This document aims at defining the architecture of the information aggregation and provisioning engine, in the context of the GET Service platform. Its relevance lies in the fact that it determines the design choices of one of the core components of the project, which will affect the following steps of implementation and reverberate on the inter-component communication means.

  • D6.3: Prototypical Implementation of the Information Aggregation Engine. The documents aims at providing a manual for the interaction with as well as the usage, functions and implementation of the information aggregation engine. This includes a description of functional as well as non-functional aspects, e.g. its architecture, the technologies, security and extension capabilities. 

  • D6.4.1: Automatic aggregation rule generation engine. This deliverable aims at providing prototypes for (semi‐) automatically generating business events from the continuous stream of sensory events. This involves an analysis of the approaches that are required for correlating and aggregating sensory events towards providing business events and state information. For this purpose, the deliverable further includes testing opportunities for event processing, correlation as well as aggregation and pre-processing approaches for logistics in the context of the GET Service project.

  • D6.4.2: Aggregation rules that support usage scenarios. This document aims at providing rules to extract business events from the continuous stream of sensory events. Using these rules it must be possible to derive the state of transportation as well as capture unforeseen exceptions in transportation.

  • D7.1: A survey of orchestration engines. The document presents state-of-the-art engines for executing business logic, in order to select most appropriate engine for the Service Platform for GET Service. A systematic review of 36 systems that have execution engines took place. the most important requirement, on which the engine is selected, is the ability to adapt business logic at run-time environment.

  • D7.2: Design of a Reconfigurable Transportation Orchestration Engine. The goal of this deliverable is to present technology that enables a party in a collaboration to be switched with another party and its state to be transferred to that new party. In developing this technology, this deliverable contributes novel techniques and algorithms to the area of service oriented computing. Prototype tool support is developed to demonstrate the feasibility of the technology.


  • D8.3.1: Exploitation ModelThe first goal of this deliverable is to create an exploitation model for the GET Service project and its project partners, combined with examples on how to create network-centric strategies and business models, thereby visualising the value-in-use of the provided solution. This provides valuable insights in how organizations, clients and providers of transport, IT service providers and community systems can establish services for exchanging information in order to create a flexible, dynamic and green transportation. The second goal of this deliverable is to explain how this exploitation model fits the European-wide Service Platform. 

  • D8.3.2: Deployed prototype platform. This deliverable forms one of the dissemination results of work package 8: the public prototype of the GET Service Platform that is made available to a general audience. By making this functionality publicly available, the public prototype aims to help a general audience understand the benefits of a platform for collaborative transportation planning and monitoring.

  • D9.4: Final Project Report. This deliverable presents the most important results of the GET Service project. It presents a summary of the context and objectives of the project, which is based on the original description of work and updated based on the results that were achieved in the project. It also presents an overview of the main results and foreground that was developed per work package, an overview of the potential impact, the main dissemination activities and the exploitation results. Finally, it contains an overview of the dissemination of the developed foreground.