Business to Motorways of the Sea ITS for Ports and ... · ITS for Ports and Transport Communities...

Business to Motorways of the Sea

ITS for Ports and Transport Communities Document Version: Final Report

Activity 2 Report

ABSTRACT

DISCLAIMER

"The sole responsibility of this publication lies with the author. The European Union is not

responsible for any use that may be made of the information contained therein."

AUTHORS:

WITH CONTRIBUTIONS FROM:

VERSION HISTORY

Date Document Version Document Revision

History

Document

Author/Reviser

29 October 2015 1.0 Final

APPROVALS

Date Document Version Document Approved by

Activity 2 Report

TABLE OF CONTENTS

ABSTRACT ................................................................................................................................................................. 2

DISCLAIMER .............................................................................................................................................................. 2

AUTHORS: .................................................................................................................................................................. 2

WITH CONTRIBUTIONS FROM: ............................................................................................................................... 2

VERSION HISTORY .................................................................................................................................................... 2

APPROVALS ............................................................................................................................................................... 2

TABLE OF CONTENTS ............................................................................................................................................... 3

INDEX OF TABLES ..................................................................................................................................................... 5

INDEX OF GRAPHS AND FIGURES ............................................................................................................................ 5

GLOSSARY OF ABBREVIATIONS .............................................................................................................................. 5

GLOSSARY OF TERMS ............................................................................................................................................... 6

1 INTRODUCTION ................................................................................................................................................... 6

1.1 OBJECTIVE OF THE INITIATIVE......................................................................................... 6

2 REPORT FOR THE PROTOTYPE AND PILOT “BPMN FOR ITS INTEGRATED APPLICATION IN PORT AREA”

– PARTNER(S) RESPONSIBLE FOR THIS REPORT: “AUTORITA’ PORTUALE DI LIVORNO” ............................... 7

2.1 INTRODUCTION: main problem identified at the beginning of the project ................. 7

2.2 MAIN OBJECTIVE OF THE PROTOTYPE ............................................................................ 7

2.3 SCOPE OF THE PILOTs ........................................................................................................ 8

2.4 TECHNICal description of the PROTOTYPE and pilots carried out ............................... 8

2.5 LIST OF USERS AND ROLE OF USERS INVOLVED IN THE TESTS AND PILOTS ............ 11

2.6 TESTS RESULTS................................................................................................................. 12

2.7 main problems encountered during the tests .............................................................. 12

2.8 further work necessary for the implementation of the prototype ............................. 12

Activity 2 Report

3 REPORT FOR THE PROTOTYPE AND PILOT “ITS FOR PORTS AND TRANSPORT COMPANIES” –

PARTNER(S) RESPONSIBLE FOR THIS REPORT: “MARITIME CARGO PROCESSING PLC” ............................... 12

3.1 INTRODUCTION: main problem identified at the beginning of the project ............... 12

3.2 MAIN OBJECTIVE OF THE PROTOTYPE .......................................................................... 13

3.3 SCOPE OF THE PILOTs ...................................................................................................... 14

3.4 TECHNICal description of the PROTOTYPE and pilots carried out ............................. 15


3.6 TESTS RESULTS................................................................................................................. 19



3.9 DESTIN8 USER GUIDES FOR DRV, TRX AND INQ ........................................................... 22

4 REPORT FOR THE PROTOTYPE AND PILOT “MOBILE SERVICE FOR ROAD TRANSPORT OPERATORS” –

PARTNER(S) RESPONSIBLE FOR THIS REPORT: “PORT OF BILBAO AUTHORITY (PBA)” .............................. 36

4.1 INTRODUCTION: main problem identified at the beginning of the project ............... 36

4.2 MAIN OBJECTIVE OF THE PROTOTYPE .......................................................................... 37

4.3 SCOPE OF THE PILOTs ...................................................................................................... 37

4.4 TECHNICal description of the PROTOTYPE and pilots carried out ............................. 37


4.6 TESTS RESULTS................................................................................................................. 41



Activity 2 Report

INDEX OF TABLES

Table 1. KPI considered

Table 2. CBA results

INDEX OF GRAPHS AND FIGURES

Figure 1. As-Is Bunkering Process

Figure 2. To-Be Bunkering Process

Figure 3. Destin8 Drive (DRV) Dashboard

Figure 4. Destin8 Tracker (TRX)

Figure 5. Destin8 Tracker (TRX) Notification Option (DMS01/02/03)

Figure 6. Destin8 Import Enquiry (IEQ)

Figure 7. Destin8 DRV Pilot Transactions

GLOSSARY OF ABBREVIATIONS

BPMN Business Process Model and Notation

PCS Port Community System – see www.ipcsa.international/pcs

ISL Inter System Link Messages

DFS Detailed Functional Specification

OGA Other Government Agencies

HMRC HM Revenue & Customs - is a non-ministerial department supported

by 2 agencies and public bodies

UKBF UK Border Force is a law enforcement command within the Home

Office, responsible for frontline border control operations at 140 air,

sea and rail ports in the United Kingdom and overseas.

SCPHA Suffolk Coastal Port Health Authority is responsible for enforcement of

Environmental, Public and Animal Health Controls at the Port of

Felixstowe, and also delivers port health functions at a number of other

ports

http://www.ipcsa.international/pcs

Activity 2 Report

GLOSSARY OF TERMS

Destin8 UK based port community system – see www.mcpplc.com

MCP plc Operator of the Destin8 Port Community System

Directive

2010/65/EU

Directive 2010/65/EU of the European Parliament and of the Council

of 20 October 2010 on reporting formalities for ships arriving in

and/or departing from ports of the Member States and repealing

Directive 2002/7/EC

1 INTRODUCTION

This Activity 2 initiative is intended to facilitate trade and promote the use of MoS by piloting IT

solutions to increase cohesion and facilitate trade with peripheral and ultra-peripheral regions. The

ultimate aim is to increase the overall effectiveness of intra-EU maritime transport and facilitate

trade with ultra-peripheral EU regions and neighbouring countries by removing major obstacles in

the development of MoS.

1.1 OBJECTIVE OF THE INITIATIVE

Intelligent Transport Systems (ITS) are advanced applications aiming to provide innovative services

relating to different modes of transport and traffic management and to enable various users to be

better informed and make safer, more coordinated and "smarter" use of transport networks. ITS

integrate telecommunications, electronics and information technologies in the supply and logistics

chains in order to plan, design, operate, maintain and manage transport systems.

MoS require good connectivity and good connectivity requires good mobile IT systems. Intelligent

Transport Systems (ITS) for port and transport communities is an ideal platform to push notifications

to different port and transport stakeholders for status changes and general mobile access for on-

line modifications and status enquiries.

http://www.mcpplc.com/

Activity 2 Report

2 REPORT FOR THE PROTOTYPE AND PILOT “BPMN for ITS integrated application in

Port Area” – PARTNER(S) RESPONSIBLE FOR THIS REPORT: “AUTORITA’ PORTUALE

DI LIVORNO”

2.1 INTRODUCTION: MAIN PROBLEM IDENTIFIED AT THE BEGINNING OF THE

PROJECT

The main problem is related to the timing of the public tender, needed to identify the contractor. The

bureaucratic procedures have delay the initial stage related to the prototype implementation.

2.2 MAIN OBJECTIVE OF THE PROTOTYPE

Effectiveness and efficiency of the port nodes' system is the enabling element for the development of

port competitiveness itself. ITS, or intelligent transport system, are widely recognized as a key element

for transport policies, increasing efficiency and capacity of a transport system while reducing congestion

and greenhouse gases emission.

ITS framework policies are very well developed as far as road transport and multi-modal transport are

concerned, whereas ITS architectures in port areas are not developed in the same way.

Port regulators have assisted to the increase of the demand for a higher level of service in port areas,

and, to this aim, they are introducing ITS as a way to increase the productivity of the existing

infrastructure, without modifying it or with minor modifications required. However there's a substantial

lack of details for the characterization of ITS services and the necessary supporting architectures in port

areas. This initiative aims on one hand at defining an ITS standardization in port areas, focusing on well

defined processes, and on the other hand to demonstrate that ITS are the missing link between

operators and Motorways of the seas, with special reference to a complete integration of Port

Community System and proprietary private platforms.

This initiative is aimed at finding new technical possibilities to grant the aforementioned pervasive

integration. Livorno Port is featured by different information technology systems, managing

etherogenous processes. Each system gathers and processes a lot of information, in order to reach

specific purposes (depending on the processes managed). In the proposed prototype systems are

considered as players and they are simplified below:

Tuscan Port Community System (TPCS). Livorno Port Community system.

AIDA. Computerized system of customs agency.

HACPACK. Software for the management of dangerous goods.

Activity 2 Report

PORT MANAGEMENT INFORMATION SYSTEM. System of the Harbour Master related to

Maritime Traffic system, Administration procedures, and ship registry.

UIRNet. National Logistics platform of UIRNet S.p.a.

PIL. “Piattaforma Integrata per la logistica”, a railway platform managed by Gruppo FS

italiane.

MEDITRACKNET. A tracking platform based on RFID UHF technology.

PRIVATELY OWNED SYSTEMS.

The objective of the prototype is to understand and describe the main features and the

interactions between processes carried out in the Port of Livorno, using different systems such

as TPCS, System related to Dangerous Goods management, AIDA and other applications,

including those related to ship processes. The idea is to use a specific modelling tool, in order

to identify “as-is processes” and define the “to-be scenario”, characterized by some

improvements (that will be assessed).

2.3 SCOPE OF THE PILOTS

The scope of the pilot is to create a Business Process Modeling (from now on, BPMN) displaying key

elements related to Information Technology systems involved in the Port Area. An “As-is” scenario is

identified and it represents the current context. Starting from the “As-is” analysis, specific and relevant

processes have been identified, in order to develop a cost-benefits assessment.

The cost-benefits assessment is useful in order to create possible process reengineering in a “To-Be”

perspective. The final objectives of the prototype are listed below:

1. Improvement of key processes efficiency and efficacy.

2. Definition of Standardized Model related to Port Processes.

2.4 TECHNICAL DESCRIPTION OF THE PROTOTYPE AND PILOTS CARRIED OUT

Starting from the current ITS scenario of Livorno Port 3 relevant processes have been identified in

order to develop the aforementioned analysis. The processes identified are:

1. Bunkering process. This process is identified as “operations of both fuels and lube oils for

ships in the foreport or within the harbour”. The bunkering process has to be analysed from

request for the bunkering till service ends. The process is related both to the Maritime

service refuelling and Land service refuelling.

Activity 2 Report

2. Waste process. The waste process is considered as “set of procedures related to statement

on waste on board. The following items can be referred to this service: list of waste disposal

statement, statements’ magement and approval of dispatched statements.” This process has

to be analysed from the the dipstach of the waste statement till waste disposal operations

is completed.

3. Dangerous goods. Dangerous good means all goods, including packaging, waste and

component part thereof, which, due to their specific features, could damage people,

animals, properties and environment.

This process has to analyse:

Cargo Load Units arrival, on board, containing dangerous goods (from the very early

dispatch)

The unloading of dangeros goods

Possible transhipment operations

Loading of dangerous goods.

The prototype is divided into three different steps, as defined below:

A. AS-IS scenario. This scenario considers all processes involved in the systems

aforementioned. For each system, a matrix with public and/or private users and related

phases is developed.

B. TO-BE scenario. This scenario is realized considering in particular bunkering, waste and

dangerous goods processes. Starting from these processes, the idea is to create a

standardized procedure for definining Harmonized Models (procedures, tools, and

parameters used) useful to Port Processes Reenginering. Process Reenginering could make the

process more optimized, considering some Key Perfomance Indicators (they aim at

identifying the critical performance of the processes considered).

Type KPI

Service Expected Operational Time of the process. Operation Lead time (from the

beginning to the finalisation).

Activity 2 Report

Quality Score related to the single customer satisfaction. Output compliance to

with respect to customers expectations. (For instance, % complaints

percentage, number of unsatisfied operators

Efficiency Costs borne for resources deplyoment (material, immaterial and human)

for each process. Taking into consideration one single timeframe, this

indicator is measured adding costs for each resource per time unit.

Quality Reliability measurement of the process. In this specific framework,

reliability has to be calculated taking into account both:

a) level of satisfaction of operator/operators for whom the service is

provided,

b) security

Quantity Number of goods/ handled vehicles for each operator/terminal

Table 1. KPI considered

A BPMN is used to show the results of this analysis, as in the example below:

Figure 1. As-Is Bunkering Process

Activity 2 Report

Figure 2. To-Be Bunkering Process

C. Costs-Benefits Assessment. The step no. 3 consists of a “natural language” representation

of the results obtained in the previous steps. The idea is to compare the as-is and to-be

scenario proposed.

SCENARIO KPI 1 KPI 2 COST

Current process (As-Is)

Strategic Objectives (To-Be)

Gap

Table 2. CBA results

2.5 LIST OF USERS AND ROLE OF USERS INVOLVED IN THE TESTS AND PILOTS

The optimization of the processes (through the reengineering procedures) creates benefits for the

Port community, in particular for the players involved in the bunkering, waste and dangerous good

processes.

Activity 2 Report

The realization of the prototype involves not only Autorità Portuale di Livorno, but also all actors

implicated in the processes and consequently in the systems (i.e. harbour masters, stevedores,

other operators). The players are involved through interviews.

2.6 TESTS RESULTS

The prototype consists of a BPMN realization; presently, no results related to the prototype have to

be reported because the “Cost-benefits” analysis (CBA enables to display the real results related to

the prototype) has to be already done.

However, the results will be intangible because the main objective is to provide a harmonized

business process model used by the Port Community. In this perspective, considering the KPI

aforementioned (or adding other) each port actor (public or private):

could analyse or improve their current process,

could better manage resources (i.e. data and human resources),

could reduce missing links between systems (and other actors)

could reduce data redoundance (and errors) thanks to an optimized information flow.

2.7 MAIN PROBLEMS ENCOUNTERED DURING THE TESTS

In consistence with the previous section, no problems have been identified.

2.8 FURTHER WORK NECESSARY FOR THE IMPLEMENTATION OF THE PROTOTYPE

For the real implementation of the prototype, the “To-Be” and CBA analysis have to be realized. The

CBA will be realized by the end of November.

3 REPORT FOR THE PROTOTYPE AND PILOT “ITS for Ports and Transport Companies”

– PARTNER(S) RESPONSIBLE FOR THIS REPORT: “MARITIME CARGO PROCESSING

PLC”


PROJECT

One of the key topics at the outset was to identify and target those functions and technologies

providing efficient and improved access to real-time data being of direct benefit to logistics

Activity 2 Report

operators as well as the downstream supply chain. Through in-house industry knowledge and

extended customer consultation, the following potential prototype solutions were selected:

DES-5606 - B2MoS A2 i8 - Destin8 notification service prototype/trial

DES-5677 - B2MoS A2 i8 - INQ Import Enquiry Redesign

DES-5680 - B2MoS A2 i8 - Prototype DRV - Destin8 Drive (Haulier Specific Screen)

DES-3363 - B2MoS A2 i8 - Prototype Destin8 phone App

DES-5927 - B2MoS A2 i8 - Prototype ERU add option to release by ISO type

DES-5902 - B2MoS A2 i8 - Prototype TPU/MFA/INQ/TNQ - include Intended On-Carriage Option

DES-5901 - B2MoS A2 i8 - Prototype TRC/TRX Destin8 Notifications

DES-5923 - B2MoS A2 i8 - Prototype VRG/VNU/VAM Import and Export Voyage Number and Repeat

port call


Although the A2 i8 initiative, from a MCP perspective, included 8 different prototypes and pilots,

this report focus on three core prototypes that were ultimately decided as providing broader

benefits to other port community stakeholders.

DES-5680 - B2MoS A2 i8 - Prototype DRV - Destin8 Drive (Haulier Specific Screen) - to create a

module with enhanced display options incorporating all of the data and resources required by

hauliers in a concise functional format. Effectively a one-stop-shop facility using existing port

community system real-time information to support SME based logistics operators in their daily

transport planning.

DES-5901 - B2MoS A2 i8 - Prototype TRC/TRX Destin8 Notifications - introducing changes to the way

operators can track consignments in Destin8. New and more intuitive prototype enhancements now

assist the end-user track business critical status changes on a consignment via email notifications,

in real-time.

DES-5677 - B2MoS A2 i8 – INQ/IEQ Import Enquiry Redesign – introducing changes to the way

operators can search for and view import consignment records. New and more intuitive prototype

Activity 2 Report

enhancements have been applied to assist the end-user with the navigation, display and retention

of frequently used search criteria.

Detailed information on the other prototype/pilot development have been included in section 2.4

where applicable


Proof of concept e.g. the identified prototypes providing extended or stand-alone support options

for the provision of real-time information exchange in support of other tasks or the execution of

related functional transactions either without affecting or complementary to the provision of other

services in the port environment.

Furthermore, and if successful, these prototype solutions may be integrated into the Destin8

infrastructure framework and any other system or process with which they potentially relate to; to

test, where possible, the prototypes include all the functionality enabling them to be successfully

demonstrated during the pilot phase before a potential full deployment after the conclusion of the

B2MoS project in 2015.

Activity 2 Report


DES-5680 - Prototype Destin8 Drive - this fully integrated module; designed specifically for the

haulage sector, provides a haulier-centric view of relevant information and real-time events from

within the Destin8 database. Drive is available to every Haulier who subscribes to Destin8. Haulage

companies are able to complete all functions required from the Drive Transaction without having to

leave the screen i.e. release a consignment to a Vehicle Registration / PIN / Haulier ID, the operator

can click on the release indicator and a simplified RAM Release window will appear. If there is a

need to check the number of packages within a consignment, a simple click on the Unit Id invokes a

simplified Import Enquiry window will appear with the consignment details.

Fig. 3 – Destin8 Drive (DRV) Dashboard

Activity 2 Report

DES-5901 - TRX – introduces a prototype version of Tracker (TRC) that includes optional selection of

email notification of status changes to unitised consignments. Where selected, notifications will

automatically be sent to the designated email address whenever a status change (Landed, Loaded,

Cleared, Released, Arrived or Departed the Terminal) occurs against an Import, Export or

Transhipment consignment.

Fig. 4 – Destin8 Tracker (TRX)

Fig. 5 – Destin8 Tracker (TRX) Notification Option (DMS01/02/03)

Activity 2 Report

DES-5677 - Prototype Import Enquiry Redesign (IEQ) – major changes have been made to the way

users can search for and view import records.

Fig. 6 – Destin8 Import Enquiry (IEQ)

A copy of the widely distributed user guides for Destin8 transactions DRV, TRX and IEQ have been

appended in Section 4 of this High Level Specification.

The following is a brief outline description of the other prototypes developed and released as part

of the wider A2 i8 pilot carried out at Destin8 locations during 2015:

DES-5606 - Destin8 notification service prototype/trial and Prototype Destin8 Tracker Notifications

– this initial prototype service was developed to allow customers to select from Customs Status,

Port Health and/or Local Holds status by device i.e. SMS or email. Following successful completion,

the prototype was superseded by a more cost effective option of selecting dynamic outputs (DMS01,

DMS02, and DMS03) from within the new prototype tracker transaction (TRX) detailed above.

DES-5927 - Prototype Empty Equipment Release by ISO type - additional functionality has been

added to the Export Release Update (ERU) function with an option to release X number of units by

ISO type through a notification to the wharfinger/terminal operator and releasee where applicable.

This intended release will not be applied against any actual empty stock UCN/Unit id - it is only a

Activity 2 Report

notification to the wharfinger who will subsequently select units by stack availability at the time of

collection and then outgate accordingly.

DES-5902 - Prototype On-Carriage Option on intended transhipments and/or rail/barge movements

- the Transhipment Port Update (TPU) function was modified to cater for an optional wharfinger

notification of intended UK/EU on-carriage for transhipments (Transhipment type RTX in free

circulation only) and/or UK rail movements where the terminal has agreed to this. The intended RTX

transhipment option uses 5a UNLocodes whereas the intended rail move use pre-defined 5a Rail

Depot codes (available in TVW). Outputs to wharfingers/terminal operators have been applied to

the manifest create/amendment messages where additional fields have been added to the end of

the manifest create and amendment (ISL) messages respectively.

DES-5923 - Prototype Vessel Voyage Number and Repeat port call functions - VRG/VNU/VAM - in

order to avoid potential Terminal rejection of vessel registrations the lead agents import and export

voyage number must now be unique for the port of call, repeated use of a voyage number at the

working port will no longer be permitted. Feeder services or other vessels calling at two or more

Destin8 ports as part of a single voyage can however be registered with the same voyage numbers

in those ports. As part of this change, we have also extended the Repeat Details option in VRG by

adding a Working Port drop down facility, which, if used, will repeat the vessel characteristics and

other elements of a previous call at the working port as opposed to the last registered vessel/voyage

call in any Destin8 port.


Destin8 Drive (DRV) Test Companies:

Hauliers: Searon Logistics Ltd, Hemisphere Freight Services Ltd, Logistics Planning Services Ltd,

James Kemball Haulage Contractors Ltd, 3rd Party Logistics Ltd, Coggins Haulage Ltd, Port Express

Ltd, Wincanton Container Logistics, Maritime Transport, Multimodal Logistics.

Destin8 Tracker (TRX) Test Companies: A significant number of non-Desti8 customers e.g. importers,

exporters, and other inland operators have expressed interest in using the tracker and notification

functions as a stand-alone module.

Destin8 Import Enquiry (IEQ) Test Companies:

Customs and OGAs: Environment Agency, Animal & Plant Health Agency, Bedfordshire Police

Corporation Of London, Forestry Commission, Mersey Port Health Authority, Office of the Police &

Activity 2 Report

Crime, River Tees Port Health Authority, South Tyneside Council, Suffolk CC Trading Standards and

Suffolk Coastal Port Health Authority.

Ports and Terminal Operators: Clydeport Operations Ltd, Forth Ports Limited, North Tyneside Port,

PD Teesport, Port Of Tilbury London Ltd, The Bristol Port Company.

Shipping lines & Agents: K Line(Europe) Ltd, Maersk Company Ltd, Mediterranean Shipping Co (UK)

Ltd, ICL Agencies UK Ltd, Containerships (UK) Ltd and China Shipping (UK) Agency Co Ltd.

Freight Forwarders: Advanced Forwarding Ltd, Allport Cargo Services Limited, Aramex (UK) Limited,

Asia Freight Solutions Ltd, CML Ltd, Damco, EUF (Felixstowe) Ltd, Expeditors International UK Ltd,

GP Global Logistics Limited, Hine Freight Services Ltd, Interfreight UK Ltd, John Good & Sons (GCB)

Ltd, Karl King Transport Ltd, Kuehne & Nagel Ltd, KWL Logistics Ltd, Newell & Wright ,Octain Ltd,

Pentalver Transport Limited, R Bugg Trading Ltd, Seabourne Forwarding Ltd, Seaport Freight

Services Ltd, Velta International Ltd and WS Logistics Ltd.

3.6 TESTS RESULTS

Destin8 Drive (DRV) Pilot Company Feedback:

The purpose of obtaining initial feedback during the trial implementation was primarily to ensure

the transaction delivered what it was designed to do. This was to offer a complete and rounded

resource to the Destin8 haulier community, while also gauging system response and performance

during the pilot period.

The feedback we have received has provided confidence in the

assumptions we made during development and further solutions

and enhancements have been drawn from this feedback in

preparation for wider deployment. Consideration should be given to

the fact that once you enter this transaction, you need not logout

due to the background auto refresh, therefore 36178 hits during

initial implementation meets expectation.

Use of the DRV transaction progressively rises (adjacent graphic

quantifies over an 8 month period the number of hits).

Fig. 7 – Destin8 DRV Pilot Transactions

Activity 2 Report

Typical findings and average response to a qualitative customer survey included:

Feedback indicates that the overall system performance of the Transaction is ‘Very Good’.

The trial was mainly carried out using both IE 8/9 and Google Chrome 39/46.

The majority of the piloting companies have been using the DMS notification function.

They prefer these notifications in email form and do not see the need for an SMS format of

the notifications.

Companies are utilising the Pre-Exec column to check the status via the indicator. However,

they are not entering their Haulier Code in the field provided. Responses as to why they are

choosing not to do has highlights that they are unsure of the benefits.

In addition, common themes were found when the piloting companies listed their initial ‘Pros and

Cons’.

The most common of these were the opinion that DRV is ‘quick and easy to use’ and users

found the traffic light indicators to be a clear and a concise way of displaying statuses. Users

noted that the particular layout of the screen gives clear visibility across each of their

consignments.

“We do really like the idea of having all of our information in one screen” Andy Lewis –

Transport Manager, James Kemball Road Haulage Contractors Limited.

“For us, it’s just the quick access to pertinent information” Darren Walne – General Manager,

Searon Logistics Ltd.

“Can I just say the new functionality of DRV is absolutely amazing, thank you” Mark Lyons -

Key Account Manager, Wincanton.

“That is magical. Thank you!!! Didn't think it could get better but you pulled it out the bag”

Mark Lyons - Key Account Manager, Wincanton. (in a separate response to a question

Dangerous Goods visibility)

From analysing the response, we have been able draw together an improvements JIRA which, where

practical and scalable, have been included. A few points, such as column filtering and hazardous

implications were dealt with during onward training.

Activity 2 Report

The Destin8 Import Enquiry (IEQ) and Destin8 Tracker (TRX) user feedback were tested throughout

the B2MoS Demonstration Days and Training Seminars undertaken as part of Activity 4. These took

place as follows:

Leicester: 20 October: Number of attendees: 11 (The area concerned is a very large inland

distribution hub). Felixstowe Port: 19 October: Number of Attendees: 9. Birmingham: 30

September: Number of Attendees: 10. Liverpool: 15 October: Number of Attendees: 29 (two

sessions). Bristol: 01 October: Number of Attendees: 9. Grangemouth: 06 October: Number of

Attendees: 9. Port of Tyne: 07 October: Number of Attendees: 6. Tilbury: 13 October: Number of

Attendees: 16. Glasgow (Grangemouth/Greenock Ports): 28 October: Number of Attendees: 28,

Felixstowe: 30 October: Number of Attendees: 15

All the activities detailed above were presented and were very well received, although we often had

more interaction from smaller audiences than larger ones. As part of Activity 4, the B2MoS Survey

Monkey link was distributed by e-mail to a nominated person at each company following the

presentations.


Other than some minor data quality issues, no other significant problems were encountered during

the pilots of this initiative.


Following further consultation with a range of stakeholders a number of enhancements have been

collated which, where practical and scalable, will be developed during 2016.

With the exception of DES-5606, which has been superseded, all seven pilots as described in this

high-level report will continue to be available, as prototype functionality and our pilot period have

already been extended until the end of December 2015. We remain confident that all of them will

be made a permanent feature within the Destin8 production system once the B2MoS project has

been completed.

Activity 2 Report

3.9 DESTIN8 USER GUIDES FOR DRV, TRX AND INQ

Activity 2 Report

Activity 2 Report

4 REPORT FOR THE PROTOTYPE AND PILOT “MOBILE SERVICE FOR ROAD TRANSPORT

OPERATORS” – PARTNER(S) RESPONSIBLE FOR THIS REPORT: “Port of Bilbao

Authority (PBA)”


PROJECT

e-puertobilbao is an electronic commerce platform whose aim is to maximize communications and

facilitate interaction among the different companies in the Bilbao maritime-port community. Its

fundamental goal is to achieve greater speed and efficiency in the passage of vessels and goods

through the Port, in such a way that companies and Port as a whole will be more competitive. More

than 300 companies are currently using e-puertobilbao services, among them, Ship Agents, Terminal

Operators, Customs Agents, Forwarders, Customs authorities, Port Authority, Inspection Services

(Health, Veterinary…), Road Transport operators and Rail Transport Operators Companies (160

companies).

In this Activity 2 the aim is to facilitate to mobile users of e-puertobilbao with an access to specific

services throught mobile applications. Mainly for Road Transport Companies operating in the Port

of Bilbao. In other words, how to address the transition from e-services to m-services. In the case of

road transport operators there are some facilities/services we have to provide them mobile

otherwise they will not be able to fulfil/use.

The pre-entry notification to port/terminals in the Port of Bilbao is being implemented since

beginning of 2014. Most of Container cargo related road transport operators are sending the

information from their offices. From traffic control department or from traffic managers.

However, due to the variety of road transport companies, we have identified specific service

requirements for companies working in a different way. Main tool for these companies are smart

phones and they work on demand basis, last minute transport orders and so on.

For them, it is important to send the pre-entry information from a mobile device and to check if the

cargo is released and it is ready for transportation or has been accepted in the terminals for

embarkment.

Activity 2 Report


The aim is to build a prototype and running a pilot for a range of new specific mobile services or

upgrading of some available services for mobile customers of the Port. It is intended that these

prototypes will only be partial implementations of the full transactions available in e-puertobilbao.

In this prototype we will focuss in the mobile service for pre-entry information to the

Port/Terminals. In short, it will cover the pre-entry requirements for general cargo, contenerized

cargo, dry bulk and liquid bulk.


The scope will cover all functionalities of the e-service for an android App totally integrated with the

Transport order service and the container release/admittance service. It will include the

requirements for port access control, terminal access control and in the containers case it will be

linked with the release/acceptance information.


Service functionalities:

Pre-entry mobile notification

Pre-entry mobile notification from a Release order or from an Acceptance order

Main features

App, first version for android platform (80% market share)

Second version iOS platform

Online and offline capabilities

User/password validation

Authentication

Activity 2 Report

Technical description of the prototype, architecture:

Activity 2 Report

Some screen shots of the prototype:

Activity 2 Report


The companies participating in the test and pilots are:

CECOTRANS BIZ / Road Transport Operator

Activity 2 Report

TPS / Road Transport Operator

PBA-e-puertobilbao / Port of Bilbao Authority Security Division / PCS

NCTB / Container Terminal

4.6 TESTS RESULTS

By sending the pre-entry information they will be able to use the fast line access to the port and to

the terminals. That is to say, they wil have benefits as:

• Avoid queueing, reduction of waiting times

• Better management of port facilities

• Safer port area

• Optimization of port operations

So far we are in an initial testing phase, therefore we have still not data about time and cost saved.

We have a special entry line for those trucks with pre-entry information but still we have not got

the same in the container terminal. They are saving time at the gate control mainly because all the

information needed is being provided but still is not quantified.


Main problems encountered were the usability of the App, the lack of quality of information,

training, integration of information flows between the PCS and the Container Terminal.


The prototype is very close to the final solution. The aim is to develop the same App for Ios platform

with the same functionalities, data model and so on. Besides that there will be a need for a better

physical lay out of the container terminal gates in order to have a specific fast lane but this is out of

the scope of the project.

Business to Motorways of the Sea ITS for Ports and ... · ITS for Ports and Transport Communities...

Documents

Transcript of Business to Motorways of the Sea ITS for Ports and ... · ITS for Ports and Transport Communities...