Summary: This document is about CORE review of reference projects and specification of reusable outputs, on FP7-project e-Freight. Authors are Marcus Engler and Oliver Klein, both from ISL. The original files can be found in CORE e-library, with coding CORE3003a. More information on the project at: http://www.efreightproject.eu/

[s2If is_user_logged_in()]

The Integrated FP7-Project ‘e-Freight, European e-Freight capabilities for Co-modal transport’ started in the beginning of 2010 with 30 partners addressing the development, validation and demonstration of innovative e-Freight capabilities. These capabilities have been developed to support the following four main categories of e-Freight stakeholders:

• Transport users (shippers, freight forwarders, etc) to identify and use direct or combined transport services most suited for their purpose.
• Transport service providers in all modes to: (i) provide information about their services and exchange information electronically with relevant actors through planning, executing and completing transport operations; and (ii) setting up of (liner) service networks adhering to co-modality principles for improved efficiency and end-to-end quality of surface freight transportation.
• Transport infrastructure providers to facilitate the best possible use of the complete transport infrastructure and support transport users by providing information about the available transport infrastructure and how to use it.
• Transport regulators to obtain in the simplest possible way the required information for monitoring compliance with applicable regulations, and to exchange information with other authorities for collaboration in security and environmental risk management.

e-Freight outcomes relevant for CORE: The e-Freight Project has multiple valuable inputs towards CORE. First of all the e-Freight common Framework which was developed further in various projects (see doc by David Griffith, BMT) which became partly OASIS UBL 2.1 and an IEC/DIS meanwhile. The Information Models divided into 4 domains and associated roles (described in e-Freight D1.3b e-Freight Framework – Information Models):

• Logistics Demand, which is the domain of Logistics Services Clients (and Consignor and Consignee);
• Logistics Supply, the domain of the Logistics Services Providers;
• Cooperative systems (traffic management), the domain of the Transportation Network manager; and
• Supply chain security and compliance, the domain of the Transport Regulator;

might be reused in CORE WP2 for localization and tracking solutions and in CORE WP6 – which is about an a CORE Common Framework – the e-Freight Common Framework should be taken into account, despite the fact the common framework is not widely accepted today among Governmental Agencies and aspects of real time data sharing are implemented to a minor extend.

Also of interest towards CORE WP2 is the e-Freight D4.3: Transport execution solutions, containing the e-Freight approach for monitoring of transport service executions, based on the requirements and electronic message specification heads into the same CORE direction.

Towards CORE WP3, mainly the e-Freight D3.2 – Reference Solutions for Next Generation National Single Windows – is a good source for reusable information when developing threat and vulnerability analysis methods and further on at the design, implementation and use of SCS Services and Components for Customs in Demonstrators. The same source of information contains Gateways to support data pipelines and SBA and Gateways to national and EU Single Windows which is CORE ST 4.2.

For a Supply Chain Situational Awareness Toolset (CORE ST4.1.1) the European transport document contained in e-Freight D3.1: Reference Solutions for the Single European Transport Document is of interest, as well as the already named e-Freight Framework – Information Models. The latter also might contribute to Supply Chain Data Model and CORE profiles

For the purpose of specifying ontologies in CORE WP6 the e-Freight ontology named inD2.3 – The e-Freight Ontology should serve as an example. The same deliverable also contains information regarding Connectivity Infrastructure. This part is also supported by e-Freight Access Point (EAP) e-delivery infrastructure, which also contains information for access points and a modelling and simulation engine.

Related Documentation – e-Freight Deliverables – Dissemination Level PU: Public

• D1.3b e-Freight Framework.pdf
• D2.3 e-Freight Ontology.pdf
• D2.3 e-Freight Ontology_rel 2_User Guide.pdf
• D3.1_Reference solutions for a Single European Transport Document.pdf (name shortened)
• D3.2 Reference Solutions for Next Generation National Single Windows.pdf (name shortened)

Dissemination Level CO: Confidential, only consortium members and Commission Services:

• D4.3 – Transport execution solutions – version 1.pdf

OASIS Universal Business Language (UBL) – UBL-2.1.pdf

http://docs.oasis-open.org/ubl/os-UBL-2.1/UBL-2.1.pdf

ISO/IEC DIS 19845 / downloadable from link below at cost of 118CHF

http://www.iso.org/iso/catalogue_detail.htm?csnumber=66370

Project web-site:

http://www.efreightproject.eu/

[/s2If]