Feeder Session 4 th of June 2008

Agenda  Electronic Data Interchange (EDI)  ECT Website possibilities  Port Infolink  No Match - No Access  Cargo Opening Deep-Sea  Cargo Closing Deep-Sea  Delta Barge Feeder Terminal (DBFT)  Lunch!

Electronic Data Interchange No match No acces Tom Niels

EDI: the international standard  EDI stands for Electronic Data Interchange, an international standard for information exchange.  EDI is used in industries where the accuracy of complex and high density information exchange among parties is crucial.  EDI has been developed in the 80’s and has become the international standard for information exchange in the shipping industry.  Standards have been developed by the Ship Message Development Group (SMDG) a working group of the United Nations

EDI usage in container world  The increase of container volume requires electronic data exchange.  Even after twenty years, the usage of EDI is not yet fully incorporated by all parties.  The advantages of EDI can only be realised when the same rules are applicable to all parties.  EDI reduces the number of mistakes, increases efficiency in the chain and improves the reliability of information.  European Custom Authorities enforce mandatory electronic data exchange with the introduction of Export Control System (ECS) in June 2009

Usage of EDI at ECT  The use of EDI by means of EDIfact, Port Infolink and/or - web services will be mandatory for all discharge and load information.  Box operators accept and release containers by electronic means only.  ECT no longer accepts containers without a matching booking number (No Match-No Access).

Possibilities to submit EDI Four Messages required EDIFACT language Load order =COPRAR-load Discharge order= COPRAR-discharge Acceptance order=COPARN Release order= COREOR

Load Situation  When the Feeder operator is loading containers at ECT the following means of Electronic Data Exchange can be used –EDIFACT message Coprar-load. –Port Infolink Service Load List. –These should be at ECT 16 hours before ETA vessel (as from the 1 st of August 2008) (under construction)  When the Feeder operator is loading Transshipment Containers operated by Deep-sea Carrier(s), you should provide the Box operator release number,if the box operator required this.  When the Feeder operator is loading Feeder operated Containers (Feeder operator acting as Box operator), no release number is necessary.  For a clear overview ECT requires a summary of the total load orders from the ships operator EDI loadlist Abbreviations: POL port of loading=previous port PODport of discharge/load=rotterdam POD2port of destination=bv bilbao

Discharge Situation  When the Feeder operator discharging containers at ECT the following means of Electronic Data Exchange can be used –EDIfact message Coprar-discharge. –Port Infolink Service Discharge List.  When the Feeder operator is discharging Transshipment Containers operated by Deep-sea Carrier(s), it is mandatory to provide the Booking number, also known as the Box Operator reference number.  When the Feeder operator is discharging Feeder operated Containers (Feeder operator acting as Box operator), it is mandatory to provide a second modality e.g. for import truck, rail or barge and for transshipment the radio call sign and voyage number of the outgoing vessel.  For a clear overview ECT requires a summary of the total discharge orders from the ships operator

Acceptance Order Acceptance When the Feeder operator is acting as Box operator, you are mandatory to electronically communicate the acceptance of your container. This can be done by means of an EDIFACT message called COPARN or via the e-services on the website of ECT, (authorization can be arranged by request via Make sure you communicate the booking number to the party who needs to deliver the container at ECT.

Release Order Release When the Feeder operator is acting as Box operator and your container is on an ECT terminal, you are mandatory to electronically communicate the release of your container. This can be done by means of an EDIFACT message called COREOR or via the e-services on the website of ECT, (authorization can be arranged by request via Make sure you communicate the release number to the party who needs to load the container at ECT.

ECT Message movement Coprar discharge 2 1 Acceptance order 3 No Match Feedback on daily bases Match on Booking nr. Box operators Feeder operators

No Match – No Access Delivery Booking OK Booking notOK EDI gewenste situatie onbekende boeking Hardcopy manuele invoer Geen EDI onjuiste boeking Delivery OKnotOK EDI proper situation Unknown booking Hardcopy manual input No EDI false booking Pickup Pin/Release OK Pin/Release notOK EDI gewenste situatie onbekende pin/release Hardcopy manuele invoer Geen EDI onjuiste pin/release Pickup Pin/Release OK Pin/Release notOK EDI proper situation Unknown pin/release Hardcopy manual input No EDI false pin/release

Feeder operator Delivery

Feeder Delivery

Website demo Roel Kuyper

Input Data via ECT.NL Acceptance order  enter your acceptance order

Input Data via ECT.NL Release order  enter your release order

Check on information ECT.NL Inland Carrier Tool  Export check the correctness from your Load list before sending EDI below subjects to check  Import check the correctness from your discharge list before sending EDI below subjects to check

Reporting Stanley Brabers

Reporting  Reporting automatic procedure via website  First bookings list on website 62 hours before ETA  Preliminary load list on website 52 hours before ETA  Update every 4 hours until effective Cargo Closing at 24 hours before ETA  Continued updates of preliminary load list after cargo closing  Reporting of Preliminary load list stops 4 hours before ETA

Overview  Reports Delta Terminal  Discharge- and Load lists / Bookings lists  24 Hours Reports  Real time reports  Future reports

Reports Delta Terminal  The reports placed on the ECT website can be divided in to 3 main categories: –Discharge- and Load list/Bookings lists –24hours reports –Real time reports

Discharge- and Load lists  Preliminary reports –Acceptance Orders(Bookings list) Contains bookings received for this vessel hold and released –Preliminary discharge list Contains to be discharged containers, profound ok by COT and/or booking –Preliminary load list Contains released containers which are expected or have a different hold(customs, shipping line and others) If a electronic load list has been processed, contains containers present on a released booking but with a line hold  Final reports –Discharge list – from the waterside system –Load list – from the waterside system  In the directory Reports- Load/Discharges Container Lists the reports are divided by container operator.  In the directory Reports- Load/Discharges Object Lists the reports are combined for the object operator

Timetable for acceptance orders and loadlists Reports triggered by CCO, if blank by ETA: (based on deep sea CCO)

24 Hours Reports  24 Hours Reports with the following information, kicked off every 24 hours, containing the previous 24 hours: –Receivals and deliveries per container by road, rail, barge short sea/feeder –Several RTO storage deadline containers –Containers on storage –Containers on storage longer than 3 or 12 days –Special Handlings

Real time reports  Not quite real-time, but kicked off at 07:30 am, 11:30 am and 15:35 pm  The reports presented are txt files and are a reflection of our database tables, all files are semicolon separated  At the moment the information in these files contain only data regarding present containers  These reports are available as from the 1 st of july  The tables presented contain the following information:

Future reports  Complete preliminary load list landside modalities last quarter 2008  “Real Time” historic data first quarter 2009

Questions? Deep-sea Nathalia Rinus van der Feeder Martijn van Barge Ronald van den Anton Rail Roel Truck Ronald van den Wida van de

Port Infolink Leo van Driel

Cargo Opening Cargo Closing No Match – No Access Florian Vreeburg

Cargo Closing Deep-Sea  Administrative and physical closing 24 hours before the deep-sea vessel’s Estimated Time of Arrival (ETA) as per May 1 st  These procedures are in line with anticipated EU regulations

Administrative Closing  Lines send load list latest 24 hours before ETA  Load list received by ECT is final.  Load list is complete and accurate.  No changes, no voids, no dummy numbers.  Split call: load terminal leading.

Physical Closing  Containers not present are cancelled from load list.  Containers that remain on the load list: –Containers from objects in operation –Late Arrival Requests –Inter terminal transport containers and containers from depot(s). –Custom blocked containers  Administrative processing starts latest after administrative closing at 24 hours before ETA.

Internal Operational Reality  At a certain moment ECT internally needs to finalize closing procedure (blocked containers, depots, vessels in operation etc.). This is done at 6 hours before ETA of vessel (final closing).  Changes in ETA (>24 hours Cargo Closing Time) of the vessel result in a change of all deadlines. The processed actions cannot be changed.

Delta Barge Feeder Terminal (DBFT) Theo van Zijll

Appendix

Loadorder details EDI loadlist Abbreviations: POL port of loading=previous port PODport of discharge/load=rotterdam POD2port of destination=bv bilbao

Dischargeorder details

Further actions necessary  Still too many interruptions.  Late arrivals disturb the process till vessel departure  Container availability vessels in operation not transparent enough.  Too much personal interpretation of guidelines  Transition period until implementation of mandatory rules European Community effective summer 2009.

Late Arrival Requests  Late arrival request on the load list latest at 24 hours before ETA.  Specification of bookings number and container number.  Maximum of 10 Late Arrivals per call per box operator.  ‘Specials’ are possible  Container needs to be present at the terminal 6 hours before ETA (with the exception of banknotes and IMO 1)