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 issues: Shared interests • Lack of information transparency • Leading regional maritime-industrial hub • Inefficient scheduling • Maintain strong volume growth within • Unnecessary moves current infrastructure • “Buffer & suffer” • Direct tradelane for many commodities/ products, same customers • “ Hurry-up & wait ”
30% of vessels get delayed, Lack of timely and reliable Data quality is not assured 90% of delay cascades data sharing is a root cause Lack of common accepted Outdated and inefficient communication standard for Closed data culture among means of communication data exchange martime industry still being used
How it started: Global industrial Taskforce to address standardization element International standards to enable data exchange (2014) • 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 * Standards entail Master and Event data standards. Event Data and application PRONTO are covered in this presentation.
Service operations can also plan better and work more One view for all parties Adapt planning to increase efficiently involved in a port call utilization z Reduce port turn around Optimization within More insights in port time benefits all parties calls leads to higher safety the port and involved level from port to port
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
Conceptual design Pronto Pronto real time dashboard API Notifications (web & app) Common Timeline Event processing logic Predicted Events Data Science Systems Event hub e.g. machine learning Planned Planning & Actual Events Derived events nearby ports generator Planning Planning Planning Vessel location Planning Planning terminals nautical services vessel services (AIS) Port map Ship details ships agent Environmental Data
Jetty planning visibility incl. warnings
Pronto Port Call Optimization Use case benefits realized (a.o) Use case 2: Delay on bunkering Use case 1: Idle time on departure 100% reduction 20% reduction KPI: decrease vessel delay due to bunker activity KPI: decrease vessel idle time on Zero measurement: 19% departure Target: 10% Zero measurement: 3.5 hrs Result 0% Target: 2.5 hrs Result 2.8 hrs Approach: - Terminal, agent, Shipping line share data via Approach: Pronto - Terminal, Agent, Shipping line share - Daily 15 min check-in call; shipping data via Pronto line/agent/Pronto to decide on actions upfront - Work process changed between - All delays were avoided due to way of working terminal & agent regarding ordering pilot with Pronto - 80% reduction of phonecalls to terminal Involved parties: Involved parties: Container line, Agent Shell, Vopak Agencies
Pronto Port Call Optimization Benefit summary • 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 Trial INDICTATIVE Generic timeline & involvement Software Pilot Orientation Preparation Evaluation Development Live Duration ~ overall 35 weeks • Min 6-8weeks (tbd) ▪ 6 months (tbd) ▪ 3 times 1/2 day ▪ 2 weeks Activity ▪ Identify needs ▪ Pilot participants ▪ Zero measurements ▪ Pronto @ ▪ Evaluation on KPIs ▪ Data ▪ Set KPI’s / ▪ Hardware ▪ Share lessons learned workfloor ▪ User monitoring ▪ Next steps requirements evaluation criteria preparation* ▪ Software ▪ Data exchange / ▪ User support ▪ Bug fixing requirements interfaces ▪ Process mapping ▪ User onboarding Roles involved (participant) ▪ Sr management ▪ Ops Manager ▪ IT (tbd) ▪ Ops Manager ▪ Sr management (12) ▪ Operations ▪ Planner ▪ Ops manager (8) ▪ Planner ▪ Ops Manager (12) ▪ IT ▪ Planners (36) ▪ Planner (12) management ▪ Total time: ▪ 8 hrs per role ▪ TBD ▪ 36 hrs • 44 - 60 hrs
Pronto Port Call Optimization Key Lessons learned It all starts with a coalition of the willing 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
Recommend
More recommend
