Innovating together Roland van Assche Port of Rotterdam Energy - - PowerPoint PPT Presentation

Innovating together

Roland van Assche Port of Rotterdam Energy Breakfast - Houston - May 7th,2019

Introduction Port of Rotterdam

Port of Houston – Port of Rotterdam

Shared interests

• Leading regional maritime-industrial hub
• Maintain strong volume growth within

current infrastructure

• Direct tradelane for many commodities/

products, same customers Shared issues:

• Lack of information transparency
• Inefficient scheduling
• Unnecessary moves
• “Buffer & suffer”
• “Hurry-up & wait”

Closed data culture among martime industry 30% of vessels get delayed, 90% of delay cascades Outdated and inefficient means of communication still being used Lack of common accepted communication standard for data exchange Data quality is not assured Lack of timely and reliable data sharing is a root cause

How it started: Global industrial Taskforce to address standardization element

• Need for global standards to connect

nautical information at sea to supply chain information at shore

• Establishment of International Taskforce

Port Call Optimization, a neutral, global, industry initiative

• Initiated by Maersk Line and Shell, Port of

Rotterdam independent chair

International standards to enable data exchange (2014)

* Standards entail Master and Event data standards. Event Data and application PRONTO are covered in this presentation.

z

One view for all parties involved in a port call Service operations can also plan better and work more efficiently Optimization within the port and from port to port Adapt planning to increase utilization Reduce port turn around time benefits all parties involved More insights in port calls leads to higher safety level

PRONTO Port Rendezvous of Nautical and Terminal Operations PRONTO allows all parties in a port to update their starting and completion times, real time. It is a real time planning and decision support system (platform and app) for all actors in the port Enabling pro-active planning of portcalls instead of reactive

PRONTO facilitates data exchange based on standards to create a Single Point of Truth per portcall

PRONTO

Notifications Common Timeline Event hub Pronto real time dashboard (web & app)

Environmental Data

Data Science Systems

e.g. machine learning

Predicted Events Planned & Actual Events

Conceptual design Pronto

API Event processing logic

Vessel location (AIS) Planning nautical services Planning terminals Planning vessel services Port map Ship details

Derived events generator

Planning ships Planning agent Planning nearby ports

Jetty planning visibility

• incl. warnings

Use case 1: Idle time on departure 20% reduction KPI: decrease vessel idle time on departure Zero measurement: 3.5 hrs Target: 2.5 hrs Result 2.8 hrs Approach:

• Terminal, Agent, Shipping line share

data via Pronto

• Work process changed between

terminal & agent regarding ordering pilot

• 80% reduction of phonecalls to terminal

Involved parties: Shell, Vopak Agencies Use case 2: Delay on bunkering 100% reduction KPI: decrease vessel delay due to bunker activity Zero measurement: 19% Target: 10% Result 0% Approach:

• Terminal, agent, Shipping line share data via

Pronto

• Daily 15 min check-in call; shipping

line/agent/Pronto to decide on actions upfront

• All delays were avoided due to way of working

with Pronto Involved parties: Container line, Agent

Pronto Port Call Optimization

Use case benefits realized (a.o)

• Decrease waiting time per port call

(20% reduction)

• Just-in-time sailing to the port
• Reduce bunker cost and CO2 emissions

(5% CO2 emission reduction)

• Optimize berth utilization
• Optimize resource allocation
• Improved planning horizon
• Avoid redundant communication on vessel status

(80% phonecall reduction)

• Enable decisionmaking based on realtime, reliable information

(80% phonecall reduction)

• Avoid mis- and bilateral communication between parties involved in the port call

Pronto Port Call Optimization

Benefit summary

Orientation Preparation Evaluation Software Development Pilot Live Duration ~ overall 35 weeks ▪ 2 weeks

• Min 6-8weeks (tbd)

▪ 6 months (tbd) ▪ 3 times 1/2 day Activity ▪ Identify needs ▪ Data requirements ▪ Pilot participants ▪ Set KPI’s / evaluation criteria ▪ Software requirements ▪ Process mapping ▪ Zero measurements ▪ Hardware preparation* ▪ Data exchange / interfaces ▪ User onboarding ▪ Pronto @ workfloor ▪ User monitoring ▪ User support ▪ Bug fixing ▪ Evaluation on KPIs ▪ Share lessons learned ▪ Next steps Roles involved (participant) ▪ Sr management ▪ Operations management ▪ Total time: ▪ Ops Manager ▪ Planner ▪ IT ▪ 8 hrs per role ▪ IT (tbd) ▪ Ops manager (8) ▪ Planners (36)

• 44 - 60 hrs

▪ Ops Manager ▪ Planner ▪ TBD ▪ Sr management (12) ▪ Ops Manager (12) ▪ Planner (12) ▪ 36 hrs

PRONTO Trial Generic timeline & involvement

INDICTATIVE

It all starts with a coalition of the willing

Pronto Port Call Optimization

Key Lessons learned

Start small to

• Get working tools in hands of people; learn by doing
• Increase speed , focus on quick wins
• Avoid high cost and complexity

Then scale fast

Business/legal alignment on data exchange = critical

Operator KPIs ≠ Management KPIs; you need to cater for both

Thank you