Document information Version 0.2 Date 01-03-2010 File-id Project: ECP Standaard beheerdocument Author Commercial department ECT Services Operations ICT Application Services Legal department Editor ICT Application Services Target group Electronic Communication Procedure Document history Version: Date: V01 25-01-2010 V02 02-03-2010 Autorisation Concept: Date: Last revison date: Distribution list F. Drukker J. Molenaar J-P. Piters M.E.C. Ruygers Vaillant Inspection: Release: Date: Date:
Content 1 INTRODUCTION...5 2 INCORRECTNESS OF DATA, LIABILITIES AND INDEMNIFICATIONS...6 3 INTELLECTUAL PROPERTY...7 4 INFORMATION ECHANGE PER MODALITY...8 4.1 General...8 4.2 Modality Deepsea (Vessel Operator)...8 4.2.1 Summary of electronic Data to exchange...8 4.2.2 Sequence of Data exchange and parties involved...8 4.3 Modality Deepsea (Container Operator)...10 4.3.1 Summary of electronic Data to exchange...10 4.3.2 Sequence of Data exchange and parties involved...10 4.4 Modality Feeder...13 4.4.1 Summary of electronic Data to exchange...13 4.4.2 Sequence of Data exchange and parties involved...13 4.5 Modality Barge...16 4.5.1 Summary of electronic Data to exchange...16 4.5.2 Sequence of Data exchange and parties involved...16 4.6 Modality Rail...18 4.6.1 Summary of electronic information to exchange...18 4.6.2 Sequence of Data exchange and parties involved...18 4.7 Modality Road Truck...20 4.7.1 Summary of electronic information to exchange...20 4.7.2 Sequence of information exchange...20 4.8 Modality 3rd Party...21 4.8.1 Sequence of information exchange...21 5 TERMINAL COMMUNICATION COORDINATOR...23 6 E-SERVICES...24 6.1 Public services...24 6.1.1 Object Status...24 6.1.2 SMS Object Status...24 6.1.3 Container Status...24 6.1.4 SMS Container Status...24 6.1.5 Terminal Overview...24 6.1.6 Registration Request...24 6.1.7 Request new password...24 6.2 Common non-public services...24 6.2.1 Authorisations...24 6.2.2 My profile...24 6.2.3 Object Status Alert...25 6.2.4 Reference code list Callsigns...25 6.2.5 Reference code list IMO-UNDG...25 6.2.6 Reference code list Mastercodes...25 6.2.7 Reference code list Sizetypes...25 6.2.8 Reference code list UNLO-Codes...25 6.2.9 Terminal Overview...25 ii
6.3 Tracking & Tracing services (authorized)...25 6.3.1 Object Status Extra...25 6.3.2 Container Status Extra...25 6.3.3 Container Status Inland Carrier Delta/Euromax...25 6.3.4 Container Booking Overview Delta/Euromax...26 6.4 Order services (authorized)...26 6.4.1 Acceptance Order Delta/Euromax...26 6.4.2 Acceptance Order Empties City...26 6.4.3 Customer Blockade Order...26 6.4.4 Discharge/load Order...26 6.4.5 Document Order Import...26 6.4.6 External Transport Order from/to Depot...26 6.4.7 Pickup/delivery Order...26 6.4.8 Release Order...26 6.4.9 SMS Release Order...27 6.4.10 Update Vessel Voyage...27 6.5 Orders Overview services (authorized)...27 6.5.1 Acceptance Order Overview Delta/Euromax...27 6.5.2 Discharge/load Order Overview...27 6.5.3 Document Order Overview...27 6.5.4 Pickup/delivery Order Overview...27 6.5.5 Release Orders Overview...27 6.6 Report services (authorized)...27 6.6.1 24 Hours Reports...27 6.6.2 Load/Discharge Object Lists...27 6.6.3 Load/discharge Container lists...27 6.6.4 Load/Discharge Object Detail Lists...27 6.6.5 Terminal Performance Reports...28 6.6.6 Terminal Performance Reports Specials...28 6.6.7 E-Invoicing...28 6.7 Other services...28 6.7.1 Alliance Overview...28 6.7.2 Scan Overview...28 6.8 TCC...28 6.8.1 Authorization Overview...28 6.8.2 Pending Authorization Requests...28 7 EDI MESSAGES...29 7.1 General...29 7.2 APERAK...29 7.3 BAPLIE...29 7.4 COARRI...29 7.5 CODECO...29 7.6 COPARN...29 7.7 COPINO...30 7.7.1 COPINO-delivery:...30 7.7.2 COPINO-pickup:...30 7.8 COPRAR...31 7.8.1 COPRAR-discharge:...31 7.8.2 COPRAR-load:...31 7.9 COREOR...32 7.10 IFTSAI...32 7.11 IFTSTA...32 7.12 INVOIC...32 iii
7.13 MOVINS...32 7.14 TPFREP...33 7.15 TRACOM...33 8 SUMMARY DEFINITIONS...34 8.1 APPLICATION...34 8.2 BARGE OPERATOR...34 8.3 CAD...34 8.4 CAF...34 8.5 CAL...34 8.6 CAR...34 8.7 CCE...34 8.8 CONTAINER OPERATOR...34 8.9 DATA...34 8.10 E-SERVICES...34 8.11 ECT...34 8.12 EDI...34 8.13 FEEDER OPERATOR...35 8.14 FINANCE...35 8.15 GAD...35 8.16 OBJECT INFO RAIL...35 8.17 OPERATING MANUAL...35 8.18 PORTBASE...35 8.19 RAIL OPERATOR...35 8.20 SECOND MODALITY OPERATOR...35 8.21 SERVICES...35 8.22 SHIP OPERATING AGENT...35 8.23 SHIPPLANNING...35 8.24 TRAIN INFO...35 8.25 TRUCK...36 8.26 USER...36 8.27 VESSEL OPERATOR...36 8.28 VOYAGE INFORMATION BARGE...36 8.29 WEBSERVICE...36 8.30 WEBSITE...36 8.31 3rd PARTY...36 iv
1 INTRODUCTION This Electronic Communication Procedure (hereinafter ECP ) describes the roles and responsibilities of ECT and the User for the electronic Data interchange 1. Data is transferred, obtained, shared or exchanged under this ECP by the following three means: a. Via Electronic Data Interchange (hereinafter EDI ), b. Via the port community system of Port Infolink B.V. (hereinafter Portbase ). c. Via the ECT website www.ect.nl (hereinafter Website ) ; this Website will be updated from time to time. The Website offers different types of electronic services, individually referred to as Application and together referred to as E-services. This ECP will be updated from time to time. The latest and valid version of the ECP is published on the Website. 1 All Capitalised terms are defined in Chapter 8 of this ECP. 5
2 INCORRECTNESS OF DATA, LIABILITIES AND INDEMNIFICATIONS 2.1 The User acknowledges that the commitment to this ECP is essential for ECT to provide the agreed Services. Data interchange as mentioned above in Chapter 1 under subs a-c, intends to improve operational efficiency and to abolish the need to issue and/or process hardcopy documentation. 2.2 ECT will execute the Services on its terminals strictly according to the received Data of- or on behalf of the User. In no event ECT will be liable for any damage caused by any incorrectness of - or any inconsistency in the Data provided by and/or on behalf of the User. The User will indemnify ECT for any damage caused to ECT by any incorrectness or inconsistency of the Data provided by and/or on behalf of the User. 2.3 In case the User has chosen for indirect Data communication via an intermediate party such as but not limited to Portbase, the Data from the intermediate party will be leading for ECT for the execution of the Services and ECT will only accept responsibility for Data it has transferred to the intermediate party. ECT will only accept Data communication with intermediate parties which have committed themselves to the ECP. 2.4 Eventual subjects not governed by the ECP are governed by the latest version of the VRTO General Terms and Conditions, to be obtained via www.ect.nl. 6
3 INTELLECTUAL PROPERTY No party is allowed for commercial purposes, to hold or file Data or part of the Data provided by ECT via the means described in chapter 1 of this ECP, or to develop products, materials or methods containing Data or part of the Data provided by ECT. 7
4 INFORMATION ECHANGE PER MODALITY 4.1 General This chapter describes Data communication among ECT and the User via EDI messages or Website E-services. The definition of the EDI messages and the Data required per message are described in chapter 7 EDI Messages. Per modality the paragraph defines the parties involved with the process and a summary of the information exchange, followed by the sequence and the mean of the electronic information exchange. 4.2 Modality Deepsea (Vessel Operator) This chapter describes the communication between ECT and the Vessel Operator. The Vessel Operator, described in chapter 8 Summary definitions in paragraph 8.27 VESSEL OPERATOR The ECT departments CAD (see CAD in chapter 8.3 for the definition). The ECT department Shipplanning (see chapter 8.23) The definition of the EDI messages and the Data required per message are described in chapter 7 EDI Messages. 4.2.1 Summary of electronic Data to exchange Sequence Information: Mandatory Optional 1 Vessel schedules 2 Schedule confirmation 3 Bayplan (incoming) 4 Stowage instructions 5 Bayplan (outgoing) 6 Terminal Performance Report 4.2.2 Sequence of Data exchange and parties involved 1) Vessel Operator To CAD Vessel schedule and/or Website The vessel schedule will be sent by means of the EDI message IFTSAI or will be entered into the Website with E-Service: Update Vessel Voyage 2) CAD To Vessel Operator Schedule confirmation Website 3) Vessel Operator To Shipplanning Bayplan incoming The bayplan incoming BAPLIE message will be sent by the party to ECT Shipplanning department. 8
4) Vessel Operator To Shipplanning Stowage instructions The stowage instructions MOVINS message will be sent by the party to ECT Shipplanning department. 5) Shipplanning Vessel Operator Bayplan outgoing The bayplan outgoing BAPLIE message will be sent by ECT Shipplanning department to the vessel operator. 6) Shipplanning Vessel Operator TPR-report Website The Terminal Performance Reports will be published on the Website by ECT Shipplanning department. The Website will be updated with information on a regular basis. 9
4.3 Modality Deepsea (Container Operator) This chapter describes the Data communication between ECT and the container operator. Container Operator, described in chapter 8 Summary definitions in paragraph 8.8 CONTAINER OPERATOR ECT considers under the name Container operator : owner of the Container boxes and/or rental boxes provided by the Shipping line. DATA ECT department CAD for vessel Data (see CAD in chapter 8.4 for the definition). ECT department GAD for container Data (see GAD in chapter 8.15 for the definition). The ECT department Shipplanning (see Shipplanning chapter 8.23) ECT department Finance for invoicing (see FINANCE in chapter 8.14 for the definition). The definition of the EDI messages and the Data required per message are described in chapter 7 EDI Messages 4.3.1 Summary of electronic Data to exchange Sequence Information: Mandatory Optional 1 Vessel schedules (partner voyage number) 2 Schedule confirmation 3 Booking information 4 Release information 5 Discharge order 6 Load order 7 Gate move report 8 Vessel move report 9 Vessel move report to Portbase 10 Terminal Performance Report 11 Vessel Invoice 12 General reporting 4.3.2 Sequence of Data exchange and parties involved 1) Container Operator To CAD Vessel schedule and/or Website The vessel schedule will be sent by means of the EDI message IFTSAI or will be entered into the Website with E-Service:Update Vessel Voyage. 2) CAD To Container Operator Schedule confirmation Website 3) Container Operator To GAD Acceptance order and/or Website The booking or acceptance order will be sent by means of the EDI message COPARN or will be entered into the Website with E-Service: Acceptance Order Delta/Euromax 10
4) Container Operator To GAD Release order and/or E-Service The release information will be sent by means of the EDI message COREOR or will be entered into the Website with E-Service: Release Order 5) Container Operator To GAD Discharge order The Discharge order information will be sent by means of the EDI message COPRAR. 6) Container Operator To GAD Load order The Load order information will be sent by means of the EDI message COPRAR. 7) GAD To Container Operator Gate-move The Gate-move report will be sent by means of the EDI message CODECO 8) GAD To Container Operator Vessel-move The Vessel-move report will be sent by means of the EDI message COARRI 9) GAD To Portbase Vessel-move The Vessel-move report will be sent by means of the EDI message COARRI. This Data transmission is on behalf of the Portbase service Import Manifest. 10) Shipplanning Container Operator TPR-report Website The Terminal Performance Reports will be published on the Website by ECT Shipplanning department. 11) FINANCE Container Operator Invoice and/or Website The invoice will be sent by means of the EDI message INVOIC and the can be downloaded from the website with E-service E-Invoicing. 12) GAD Container Operator General reporting Pre liminary loadlist 24H reports Final discharge list Final load list Acceptance orders Website The ECT- Website under my e-services will be updated with information on a regular basis. 11
12
4.4 Modality Feeder This chapter describes the Data communication between ECT and the Feeder Operator. Feeder operators can also act as box operator in relation with their own shipments. Feeder Operator, described in chapter 8 Summary definitions in paragraph 8.13 FEEDER ECT department CAF for vessel Data (see CAF in chapter 8.4 for the definition). ECT department GAD for container Data (see GAD in chapter 8.15 for the definition). The ECT department Shipplanning (see Shipplanning chapter 8.23) ECT department Finance for invoicing (see FINANCE in chapter 8.14 for the definition). The definition of the EDI messages and the Data required per message are described in chapter 7 EDI Messages. 4.4.1 Summary of electronic Data to exchange Sequence Information: Mandatory Optional 1 Vessel schedules per call 2 Schedule confirmation 3 Bayplan (incoming) 4 Stowage instructions 5 Booking information (own shipments) 6 Release information (own shipments) 7 Discharge order 8 Load order 9 Gate move report (own shipments) 10 Vessel move report 11 Vessel move report to Portbase 12 Bayplan (outgoing) 13 Terminal Performance Report 14 Vessel invoice (own shipments) 15 General reporting 4.4.2 Sequence of Data exchange and parties involved 1) Feeder Operator To CAF Vessel schedule and/or Website The vessel schedule will be sent by means of the EDI message IFTSAI or will be entered into the Website with E-Service:Update Vessel Voyage. 2) CAF To Feeder Operator Schedule confirmation Website 3) Feeder Operator To Shipplanning Bayplan incoming The bayplan incoming BAPLIE message will be sent by the party to ECT Shipplanning department. 4) Feeder Operator To Shipplanning 13
Stowage instructions The stowage instructions MOVINS message will be sent by the party to ECT Shipplanning department. 5) Feeder Operator To GAD Acceptance order and/or Website The booking or acceptance order will be sent by means of the EDI message COPARN or will be entered into the Website with E-Service:Acceptance Order Delta/Euromax. 6) Feeder Operator To GAD Release order and/or Website The release information will be sent by means of the EDI message COREOR or will be entered into the Website with E-Service: Release Order. 7) Feeder Operator To GAD Discharge order The Discharge order information will be sent by means of the EDI message COPRAR. 8) Feeder Operator To GAD Load order The Load order information will be sent by means of the EDI message COPRAR. 9) GAD To Feeder Operator Gate-move The Gate-move report will be sent by means of the EDI message CODECO 10) GAD To Feeder Operator Vessel-move The Vessel-move report will be sent by means of the EDI message COARRI 11) GAD To Portbase Vessel-move The Vessel-move report will be sent by means of the EDI message COARRI. This Data transmission is on behalf of the Portbase service Import Manifest. 12) Shipplanning Feeder Operator Bayplan outgoing The bayplan outgoing BAPLIE message will be sent by ECT Shipplanning department to the party. 13) Shipplanning Feeder Operator TPR-report Website The Terminal Performance Reports will be published on the Website by ECT Shipplanning department. 14) FINANCE Feeder Operator 14
Invoice and/or Website The invoice will be sent by means of the EDI message INVOIC and the can be downloaded from the website with E-service E-Invoicing. 15) GAD Feeder Operator General reporting Pre liminary loadlist 24H reports Final discharge list Final load list Acceptance orders Website The ECT- Website under my E-services will be updated with information on a regular basis. 15
4.5 Modality Barge This chapter describes the Data communication between ECT and the Barge Operator. Barge Operator, described in chapter 8 Summary definitions in paragraph 8.2 BARGE OPERATOR ECT department CAL for vessel Data (see CAL in chapter 8.5 for the definition). ECT department GAD for container Data (see GAD in chapter 8.15 for the definition). ECT department Finance for invoicing (see FINANCE in chapter 8.14 for the definition). The definition of the EDI messages and the Data required per message and the Data required per message are described in chapter 7 EDI Messages. 4.5.1 Summary of electronic Data to exchange Sequence Information: Mandatory Optional 1 Call information 2 Call confirmation 3 Container status request 4 Discharge order 5 Load order 6 Status report 7 Gate move report 8 Gate move report to Portbase 9 General reporting 4.5.2 Sequence of Data exchange and parties involved 1) Barge Operator To CAL Call information as voyage number, call size, time of arrival (optional via Portbase Bargeplanning). 2) CAL To Barge Operator Confirmation of the call (optional via Portbase Bargeplanning). 3) Barge Operator To GAD Container status request and/or Website The container status request will be sent by means of the EDI message COPINO-13 or will be entered into the Website with E-Service Container Status Inland Carrier Delta/Euromax Using the COPINO message will result in the Status report message APERAK. 4) Barge Operator To GAD Discharge order and/or Website The container discharge order will be sent by means of the EDI message COPINO-delivery or will be entered into the Website with E-Service. Pickup/delivery Order Using the COPINO message will result in the Status report message APERAK. 5) Barge Operator To GAD Load order and/or Website The container load order will be sent by means of the EDI message COPINO-pickup or will be entered into the Website with E-Service Pickup/delivery Order Using the COPINO message will result in the Status report message APERAK. 6) GAD to Barge Operator The Status report will be sent by means of the EDI message APERAK. 16
7) GAD To Barge Operator Gate-move The Gate-move report will be sent by means of the EDI message CODECO. 8) GAD To Portbase Gate-move The Gate-move report will be sent by means of the EDI message CODECO. This Data transmission is on behalf of the Portbase service Barge planning. 15) GAD Barge Operator General reporting Website Final discharge list Final load list The ECT- Website under my E-services will be updated with information on a regular basis. 17
4.6 Modality Rail This chapter describes the Data communication between ECT and the Rail Operator. Rail Operator, described in chapter 8 Summary definitions in paragraph 8.19 RAIL OPERATOR ECT considers Rail operator as: Train operator transporting Containers by Railcar. SECOND MODALITY OPERATOR ECT department CAR for rail Data (see CAR in chapter 8.6 for the definition). ECT department GAD for container Data (see GAD in chapter 8.15 for the definition). ECT department Finance for invoicing (see FINANCE in chapter 8.14 for the definition). The definition of the EDI messages and the Data required per message are described in chapter 7 EDI Messages. 4.6.1 Summary of electronic information to exchange Sequence Information: Mandatory Optional 1 Rail track information 2 Rail track confirmation 3 Container status request 4 Discharge order 5 Load order 6 Status report 7 Gate move report 8 Gate move report to Portbase 9 General reporting 4.6.2 Sequence of Data exchange and parties involved 1) Rail Operator To CAR Rail track information as track number, number of containers, time of arrival (optional via Portbase Railplanning). 2) CAR To Rail Operator Confirmation of the Rail track (optional via Portbase Railplanning). 3) Rail Operator To GAD Container status request and/or Website The container status reqest will be sent by means of the EDI message COPINO-13 or will be entered into the Website with E-Service Container Status Inland Carrier Delta/Euromax Using the COPINO message will result in the Status report message APERAK. 4) Rail Operator To GAD Discharge order and/or Website The container discharge order will be sent by means of the EDI message COPINO-delivery or will be entered into the Website with E-Service Pickup / Delivery Order. Using the COPINO message will result in the Status report message APERAK. 5) Rail Operator To GAD Load order and/or Website 18
The container load order will be sent by means of the EDI message COPINO-pickup or will be entered into the Website with E-Service Pickup / Delivery Order. Using the COPINO message will result in the Status report message APERAK. 6) GAD to Rail Operator The Status report will be sent by means of the EDI message APERAK. 7) GAD To Rail Operator Gate-move The Gate-move report will be sent by means of the EDI message CODECO. 8) GAD To Portbase Gate-move The Gate-move report will be sent by means of the EDI message CODECO. This Data transmission is on behalf of the Portbase service Railplanning. 15) GAD Barge Operator General reporting Final discharge list Final load list Website The ECT- Wbsite under my E-services will be updated with information on a regular basis. 19
4.7 Modality Road Truck This chapter describes the Data communication between ECT and the Truck operator. All communications for the modality Truck will be executed by Portbase. Truck Operotor, described in chapter 8 Summary definitions in paragraph TRUCK ECT department GAD for container Data (see GAD in chapter 8.15 for the definition). The definition of the EDI messages and the Data required per message are described in chapter 7 EDI Messages. 4.7.1 Summary of electronic information to exchange Sequence Information: Mandatory Optional 1 Container status request 2 Delivery order 3 Pickup order 4 Status report 5 Gate move report All the Data exchange 4.7.2 Sequence of information exchange 1) Truck Operator To GAD Container status request and/or Website The container status reqest will be sent by means of the EDI message COPINO-13 or will be entered into the Website with E-Service Container Status Inland Carrier Delta/Euromax Using the COPINO message will result in the Status report message APERAK. 2) Truck Operator To GAD Delivery order and/or Website The container discharge order will be sent by means of the EDI message COPINO-delivery or will be entered into the Website with E-Service Pickup / Delivery Order. Using the COPINO message will result in the Status report message APERAK. 3) Truck Operator To GAD Pickup order and/or Website The container load order will be sent by means of the EDI message COPINO-pickup or will be entered into the Website with E-Service Pickup / Delivery Order. Using the COPINO message will result in the Status report message APERAK. 4) GAD to Truck Operator The Status report will be sent by means of the EDI message APERAK. 5) GAD To Truck Operator Gate-move The Gate-move report will be sent by means of the EDI message CODECO. 20
4.8 Modality 3rd Party This chapter describes the Data communication between ECT and the 3 rd parties (definition 8.31). Definition 3 rd Party: ECT considers 3 rd Party as: APM Terminal B.V. and empty container depots (M.J. Kramer (Delta) Holding B.V. or Kramer Vastgoed BV) which are physically linked to ECT. The definition of the EDI messages and the Data required per message are described in chapter 7 EDI Messages. 4.8.1 Sequence of information exchange Container-flow from 3rd party to ECT-yard Line > 3rd Coreor -- ECT > 3rd Copino-pickup Trigger: Saved changes to laad/loslijst cq ITT-order 3rd > ECT Aperak Status pre-advised container Express shows status in container inquiry: position is on 3rd > ECT Codeco (-50) Container on MTS MTS 3rd > Line Codeco (-) Gate-out move -- 3rd > ECT Codeco (-70) MTS ready (loaded) ECT > 3rd Codeco (-60) MTS departs from 3rd party buffer Trigger: DEPBUFFER ECT > Line Codeco (-) Gate-in move Trigger: GATE IN Container-flow from ECT-yard to 3rd party Line > 3rd Coparn -- ECT > 3rd Copino-delivery Trigger: Saved changes to laad/loslijst cq ITT-order 3rd > ECT Aperak Status pre-advised container Express shows status ECT > Line Codeco (-) Gate-out move Trigger: GATE OUT ECT > 3rd Codeco (-50) MTS arrives at 3rd party buffer Trigger: ARRBUFFER 3rd > ECT Codeco (-60/-11) Container from MTS 3rd > Line Codeco (-) Gate-in move -- 3rd > ECT Codeco (-70) MTS ready (empty) Container-flow from 3rd party to Rail / Barge Operator > ECT Copino-pickup ECT > Operator Aperak Line > 3rd Coreor -- ECT > 3rd Copino-pickup Containers on loadlist Trigger: Saved changes to laad/loslijst cq ITT-order 3rd > ECT Aperak Status pre-advised container Express shows status ECT > 3rd Tracom Planning of containers in container inquiry: position is on 3rd > ECT Codeco (-50) Container on MTS MTS 3rd > Line Codeco (-) Gate-out move -- 3rd > ECT Codeco (-70) MTS ready (loaded) 21
ECT > 3rd Codeco (-60) MTS departs from 3rd party buffer Trigger: DEPBUFFER ECT > Line Codeco (-) Gate-in move Trigger: GATE IN ECT > Line Codeco (-) Gate-out move Trigger: GATE OUT Container-flow from Rail / Barge to 3rd party Operator > ECT Copino-delivery ECT > Operator Aperak Line > 3rd Coparn -- ECT > 3rd Copino-delivery Container on dischargelist Trigger: Saved changes to laad/loslijst cq ITT-order 3rd > ECT Aperak Status pre-advised container Express shows status ECT > Line Codeco (-) Gate-in move Trigger: GATE IN ECT > Line Codeco (-) Gate-out move Trigger: GATE OUT ECT > 3rd Codeco (-50) MTS arrives at 3rd party buffer Trigger: ARRBUFFER 3rd > ECT Codeco (-60/-11) Container from MTS -- 3rd > Line Codeco (-) Gate-in move 3rd > ECT Codeco (-70) MTS ready (empty) Container-flow from 3rd party (origin) to 3rd party (destination) Line > 3rdD Coparn -- Line > ECT Coparn ECT > 3rdO Copino-pickup Trigger: Saved changes to laad/loslijst cq ITT-order 3rdO > ECT Aperak Status pre-advised container Express shows status in container inquiry: position is on 3rdO > ECT Codeco (-50) Container on MTS MTS 3rdO > Line Codeco (-) Gate-out move -- 3rdO > ECT Codeco (-70) MTS ready (loaded) ECT > 3rdO Codeco (-60) MTS departs from 3rd party buffer Trigger: DEPBUFFER ECT > 3rdD Codeco (-50) MTS arrives at 3rd party buffer Trigger: ARRBUFFER 3rdD > Line Codeco (-) Gate-in move -- 3rdD > ECT Codeco (-70) MTS ready (empty) 22
5 TERMINAL COMMUNICATION COORDINATOR The Terminal Communication Coordinator (hereinafter referred to as TCC ), is entrusted with the ma n- agement of the Data communication with ECT on behalf of the User. The TCC will act as the responsible contact person in all matters concerning Data communication. As soon as there has been made any substitution or successive appointment of a TCC, User will immediately notify ECT thereof. Non-contract parties of ECT who want to make use of the ECT Website, have filled out the E-declaration downloaded from Website and signed by the legal representative of the non-contract party (hereinafter the Signee ). The Signee will act as TCC for the non-contract party. The User will insure that the third parties acting on its behalf are informed of the content of the ECP, where relevant, and will insure full use of EDI and ECT Website communications by the Second Modality Operators. ECT will request the third parties acting on behalf of the User to appoint a TCC as well, in order to secure communication between ECT and these third parties concerning the User s containers. The User will work closely together with ECT in order to ensure all third parties acting on its behalf appoint a TCC. 23
6 E-SERVICES The ECT Website is divided into a public and a non-public part. To access the non-public part you have to register yourself. After login with your account and password you have access to the non-public services of the ECT Wbsite. 6.1 Public services 6.1.1 Object Status This service shows you the current status of all objects (deepsea, shortsea, barge, feeder or rail) at the terminals of ECT. 6.1.2 SMS Object Status Get the current status of your object (deepsea, shortsea, barge, feeder or rail) at the terminals of ECT in Rotterdam by sending a SMS to ECT with the following structure: OS [space] [part of objectname] Send your SMS to SMS nr: +31 06 24926060. You only can get more information about your object if you are authorized for Object Status Extra. 6.1.3 Container Status This service shows you the current status of one or more containers at the terminals of ECT. 6.1.4 SMS Container Status Get the current status of your container at the terminals of ECT in Rotterdam by sending a SMS to ECT with the following structure: CS [space] [prefix][number] Send your SMS to SMS nr: +31 06 24926060. You can get more information about your container if you are authorized for Container Status Extra. 6.1.5 Terminal Overview This service shows you a terminal overview of all objects (deepsea, shortsea, barge, feeder or rail) at the terminals of ECT. 6.1.6 Registration Request Use this form to register yourself to ECT.nl. 6.1.7 Request new password Use this service to ask ECT to send you a new password (via e-mail). 6.2 Common non-public services With registration to ECT.nl you have access to the following common non-public services: 6.2.1 Authorisations Use this form for expanding your authorisation on available services and applying for additional e- services. 6.2.2 My profile You can see and update your user profile details. 24
6.2.3 Object Status Alert This service gives you the possibility to configure alerts on events (e.g. alert on arrival) on every object (deepsea, shortsea, barge, feeder or rail) with a specific object name or voyage number. ECT can send an alert to you via SMS or e-mail. You can get more information about your object if you are authorized for Object Status Extra. 6.2.4 Reference code list Callsigns With this service you can find the callsign of a specific vessel. 6.2.5 Reference code list IMO-UNDG With this service you can find a specific IMO code or UNDG number. 6.2.6 Reference code list Mastercodes With this service you can find the mastercode of a specific operatorname. 6.2.7 Reference code list Sizetypes With this service you can find the sizetype of a specific length, height and type. 6.2.8 Reference code list UNLO-Codes With this service you can find the UNLO-code of a specific country and city. 6.2.9 Terminal Overview This service shows a terminal overview of all objects (deepsea, shortsea, barge, feeder or rail) at the terminals of ECT. If you are registered and authorized you can have access to the following non-public services. 6.3 Tracking & Tracing services (authorized) 6.3.1 Object Status Extra For authorized users Object Status Extra contains the actual discharge and loading figures. 6.3.2 Container Status Extra For authorized users Container Status Extra contains more detailed information like release and hold status. 6.3.3 Container Status Inland Carrier Delta/Euromax The inland carrier tool offers an operator the opportunity to check the status of a container which the operator is planning to pre-notify for export or import. The inland carrier tool for export advises the operator about the existence of the export booking, the container s ECT departure terminal and the Cargo Opening Time. The inland carrier tool for import advises about the presence of the import container, the document availability, the release and the customs block. Based on all this information the operator can determine the correct load and discharge list. 6.3.3.1 Container Status Inland Carrier Import This service shows you the current status of one or more containers at the terminals of ECT-Delta or Euromax by entering a container prefix, number and a correct release number (pincode). 6.3.3.2 Container Status Inland Carrier Export 25
This service shows you the current status of one or more bookings at the terminals of ECT-Delta or Euromax by entering a container operator code, booking number and sizetype. By entering one or more container prefix/numbers at the same time you can also check if a specific container is known for one of the bookings. 6.3.4 Container Booking Overview Delta/Euromax This service shows you the current status of one or more bookings at the terminals of ECT by entering a container operator code, booking number and sizetype. This service shows also all containers which are found for the booking. By entering one or more container prefix/numbers at the same time you can also check if a specific container is known for one of the bookings. 6.4 Order services (authorized) 6.4.1 Acceptance Order Delta/Euromax With this service you can send an acceptance order to the ECT-Delta or Euromax terminal for one of more of your containers. Max. 90 days before vessel ETA. 6.4.2 Acceptance Order Empties City With this service you can send an acceptance order to the ECT-City terminal of Rotterdam for one of more of your empty containers. 6.4.3 Customer Blockade Order With this service you can block/unblock (by customer or off-hire) one or more of your containers at all terminals of ECT-Delta or Euromax. 6.4.4 Discharge/load Order With this service you can submit discharge and loading orders for a feeder/deepsea object to all terminals of ECT. 6.4.5 Document Order Import With this service you can send an import document (type and number) to a terminal of ECT in Rotterdam for one or more of your containers. 6.4.6 External Transport Order from/to Depot With this service you can submit External Terminal Transport from Depot to ECT-Delta or External Terminal Transport to Depot. 6.4.7 Pickup/delivery Order The webconverter is an alternative for electronic Data interchange, developed by ECT in order to offer all parties mentioned, the opportunity to sent container pre-notification for both export and import in an electronic way. The operator inserts particular mandatory container Data in an excel file and subsequently submits this file to ECT on the Website where the date in the file is automatically converted into. 6.4.8 Release Order With this authorized service the Container operator / Feeder operator can submit release orders for containers to an object. This service allows to submit a release order to an object per Container or use the multiple button to submit an release order for than one Container (by copy/paste in excel format). Please notice the release order will be expired after the ultimate release date. 26
6.4.9 SMS Release Order You can also send a release order to ECT by sending a SMS to ECT with the following structure: For ECT-Delta terminal: RO [space] [prefix][number] For ECT-City terminal: RH [space] [prefix][number] For Euromax terminal: RE [space] [prefix][number] Send your SMS to SMS nr: +31 06 24926060. You can only release containers by SMS if you are authorized for the service Container Number Release Order. 6.4.10 Update Vessel Voyage With this service you can send a vessel schedule or an update on the voyage numbers to the ECT department CAD. 6.5 Orders Overview services (authorized) If you are authorized to an order service you also are authorized to the specific order overview. 6.5.1 Acceptance Order Overview Delta/Euromax With this service you can see which acceptance orders you send to the ECT-Delta and Euromax terminal. 6.5.2 Discharge/load Order Overview With this service you can see which dicharge/load orders you send to the ECT terminals. 6.5.3 Document Order Overview With this service you can see which document orders you send to the ECT terminals. 6.5.4 Pickup/delivery Order Overview With this service you can see which pickup/delivery orders you send to the ECT terminals. 6.5.5 Release Orders Overview With this service you can see which release orders for your containers are received and confirmed by one of the ECT terminal systems of Rotterdam. 6.6 Report services (authorized) 6.6.1 24 Hours Reports This service shows you all your available 24 hours reports for a specific operator code for a specific day. 6.6.2 Load/Discharge Object Lists This service shows you the load/discharge lists of objects (vessel and rail) at the ECT terminals in Rotterdam. 6.6.3 Load/discharge Container lists This service shows you the load/discharge container lists of objects (vessel and rail) at the terminals of ECT in Rotterdam. 6.6.4 Load/Discharge Object Detail Lists This service shows you the load/discharge container list per object (vessel or train) sorted per container operator for the terminals of ECT in Rotterdam. 27
6.6.5 Terminal Performance Reports This service shows you the Terminal Perfomance Reports per object departed from the ECT terminals in Rotterdam. 6.6.6 Terminal Performance Reports Specials This service shows you the Terminal Perfomance Reports Specials per object at the terminals of ECT. 6.6.7 E-Invoicing Via this service you can download the invoices with container details. 6.7 Other services 6.7.1 Alliance Overview With this authorized service you can see which alliances and services are known in ECT, with their partners, slotcharters and vessels. 6.7.2 Scan Overview With this service a user can find which of your containers are selected for customs scan and see which status they have. This service is only written in Dutch language. 6.8 TCC All authorization requests of ECT.nl users in combination with the operator codes which are linked to the TCC will be granted or rejected by the TCC. Also the TCC can see which ECT.nl users have authorization for the services in combination with linked operator codes. The TCC has the following services: 6.8.1 Authorization Overview With this authorized service the TCC can see an overview of all authorizations of ECT.nl users for the services in combination with operator codes. The TCC can delete an authorization of an user. 6.8.2 Pending Authorization Requests With this authorized service the TCC can see an overview of outstanding authorization requests for the services in combination with operator codes. With this service the TCC can grant or reject an authorization request. 28
7 EDI MESSAGES 7.1 General See SMDG website (http://www.smdg.org) for downloadable message specifications: APERAK BAPLIE Vessel layout COARRI Container load / discharge confirmation CODECO Container gate in / out confirmation COPARN Container Announcement COPINO Container pickup /delivery pre-notification COPRAR Container discharge / load order COREOR Container release order IFTSAI Vessel schedule information IFTSTA Equipment status report INVOIC Invoice Billing message MOVINS Stowage Instruction TPFREP Terminal Performance Report TRACOM Train composition 7.2 APERAK Application error and acknowledgement message. This message informs the message issuer that the message has been received by the addressee's application and has been rejected due to errors encountered during the process in the application. This message is also sent to acknowledge a message issuer the receipt of his message by the addressee's application. 7.3 BAPLIE The Bayplan will be used to transmit information about all occupied places onboard of a vessel to interested parties like the shipowner and the terminal operators in the next port of call. BAPLIE for next port The terminal (ECT) provides the next port with a bayplan regarding the stowage information of the vessel. 7.4 COARRI The COARRI message shows the Data of loaded and discharged containers in operation. Container discharge and loading conformation per container. 7.5 CODECO A message by which a container terminal (in general), depot, etc. confirms that the containers specified has been delivered or picked up by the Inland Carrier (Road Truckoperator, Railoperator or Barge operator). This message can also be used to report internal terminal container movements (excluding loading and discharging a Deepsea vessel or Feeder vessel). 7.6 COPARN Container pre-announcement and release notice. The acceptance order is send by the Container operator to permit ECT to accept the containers on the terminal. COPARN message Information: Header vessel information: Deepsea / Feeder operator Mandatory Optional 29
Voyage nr Objectname Container information: Container number Booking number Line id Size-type Weight POD (Port of Discharge) POD2 (Port of Destination) Full/Empty Category Off standard (when applicable) IMO + UN number (when applicable) Temperature (when applicable) 7.7 COPINO A message by which an inland carrier notifies the delivery or pick-up of containers. This message is part of a total set of container-related messages. These messages serve to facilitate the intermodal handling of containers by streamlining the information exchange. 7.7.1 COPINO-delivery: Information: Mandatory Optional Remarks Voyage number Optional for Truck Transport operator Object Id Container number Container operator Size type Category (Export / Domestic) Full/Empty Booking number Gross Weight Out of gauge Temperature IMO/UN 7.7.2 COPINO-pickup: Information: Voyage number Transport operator Object Id Container number Container operator Sizetype Release number Mandatory Optional 30
7.8 COPRAR The container discharge and loading list (COPRAR message) is used to transmit an order to load containers on or discharge containers from a seagoing vessel. This message is commonly sent by the shipping line (or agent) to the terminal operator handling the vessel. In addition to containers to be loaded or discharged, the COPRAR message may also be used to transmit details on containers that are to be shifted on board the Deep Sea Vessel or Containers that are to be discharged and reloaded (re-stowed) onto the Deep-Sea Vessel. 7.8.1 COPRAR-discharge: Information: Mandatory Optional Remarks Header vessel information: Voyagenumber Deep Sea Vesselname Deep SeaVessel operator Radio call Sign ETA date/time CRN ECT terminal Container information: Container number Containeroperator Sizetype Category (import or transhipment) Conform manifest to customs Full/Empty Reference number Bill of Lading number Cargo reference Dangerous goods Port of loading Port of discharge (POD) Port of destination (POD2) Transhipment (Place of delivery) Gross Weight Non-Standard Temperature related Handling instruction IMO Second modality Third party Cell position Bayplan position 7.8.2 COPRAR-load: Information: Mandatory Optional Remarks Header vessel information: Voyagenumber Deep-Sea Vesselname Deep-Sea Vessel operator Radio Call Sign ETA date/time CRN Container information: Container number Containeroperator Sizetype 31
Category (export or transhipment) Conform manifest to customs Full/Empty Reference number Release number/pincode If required by Container operator Cargo reference DG or Special Handling if applicable Port of discharge (POD) Port of destination (POD2) Gross Weight Non-standard Temperature Handling instruction IMD G (Dangerous Goods) 7.9 COREOR Container release order send by the Container operator to permit ECT to release the container to the collecting party. COREOR message Information: Header vessel information: Deepsea / Feeder operator Container information: Prefixnumber Pincode / release number Line id Size-Type Ultimate release date Mode of transport Mandatory Optional 7.10 IFTSAI Schedule Requests and Reports. A message from/to a liner agent to/from a local authority (e.g. port authority), Container terminals, Schedule Portal or consortia member lines, to inform the parties of the long term schedule, mid term schedule, short term schedule or schedule updates, giving information on the actual vessel schedule information and container or cargo operations. 7.11 IFTSTA A message to report the exchange of information regarding the status of the physical movement of consignments, goods or equipment at any point (in time or place) within the full transport chain. 7.12 INVOIC Electronical invoicing which provides the freight cost and other charges to the Container operator by electronically means. 7.13 MOVINS The Stowage instruction "MOVINS" will be used to transmit information about ALL activities like discharging, shifting, restowing and loading on a specified means of transport from the operator or owner of the means of transport to any party involved with the operation on this means of transport at a certain place. 32
7.14 TPFREP Terminal Performance Departure Report 7.15 TRACOM A message designed to compose a train/shuttle constitution. The TRACOM message this is a bilateral messages between ECT Delta terminal and APMT terminal. TRACOM message Information: Details of transport Date/time/period Sequence details Container number Dimensions Number of units 33
8 SUMMARY DEFINITIONS 8.1 APPLICATION Specific part on the Website where specific Data regarding a Webservice is entered, collected or exchanged. 8.2 BARGE OPERATOR Operator of an inland river vessel. A Barge is a ship constructed to carry containers and fit to be handled by a container gantry crane with standard spreader, which vessel is employed in rendering inland waterway container transportation services to the Line. 8.3 CAD Centraal Aanmeldpunt Deepsea. The ECT department CAD is the focal point for the deepsea operators and liner agents. 8.4 CAF Centraal Aanmeldpunt Feeder. The ECT department CAF is the focal point for the feeder operators. 8.5 CAL Centraal Aanmeldpunt Lichter. The ECT department CAL is the focal point for the barge operators. 8.6 CAR Centraal Aanmeldpunt Rail. The ECT department CAR is the focal point for the rail operators. 8.7 CCE Centraal Coördinatiecentrum ECT. 8.8 CONTAINER OPERATOR ECT considers under the name Container operator : owner of the Container boxes and/or rental boxes provided by the Shipping line. 8.9 DATA All messages, notifications, instructions, invoices or other communication which is electronically transferred, shared, obtained or exchanged via either EDI, Portbase or the Website. 8.10 E-SERVICES All applications of the ECT Website. 8.11 ECT The containerterminals of ECT Delta Terminal B.V., ECT Home Terminal B.V., Euromax C.V. or of subsidiaries of Europe Container Terminals B.V. 8.12 EDI Electronic interchange of a coherent set of Data in accordance with internationally agreed message standards (UN-Edifact), supplementary ECT guidelines, prepared in computer readable format in accordance with adopted protocols and capable of being directly automatically and unambiguously processed between information systems by electronic means. 34
UN-Edifact are the United Nations rules for Electronic Data Interchange for administration, commerce and transport, comprising a set of internationally agreed standards, directories and guidelines for the electronic interchange of structured Data, and in particular, interchange related to trade in goods and services between independent and computerised information systems. The transmission of EDI-messages should be in standard UN-Edifact and the costs for translation from In-house Data to UN-Edifact Data are for the account of the transmitting party. The costs for vice versa translations from UN-Edifact to In-house Data are for the account of the receiving party. 8.13 FEEDER OPERATOR Commercial and dedicated short-sea and feeder operator. A Container Feeder Vessel is a ship constructed to carry containers and fit to be handled by a container gantry crane with standard spreader, which vessel is owned, chartered or employed by the Line in rendering container transportation services to the Line, for connecting purposes to Container Deep-Sea Vessels. 8.14 FINANCE In this document the ECT billing department. 8.15 GAD Gate and administration Desk. The ECT department GAD is the focal point for Data administration and gate facility. 8.16 OBJECT INFO RAIL Pre-notification of containers in combination with train-composition. 8.17 OPERATING MANUAL Guidelines used in the operational performance. 8.18 PORTBASE Port Community System of Port Infolink B.V. More information on Portbase: www.portbase.com. 8.19 RAIL OPERATOR ECT considers Rail operator as: Train operator transporting Containers by Railcar. 8.20 SECOND MODALITY OPERATOR Parties, such as but not limited to, Barge operators, Rail Operators or Truck, working on behalf of ECT s customers or on behalf of the customer of ECT s customers. 8.21 SERVICES Obligations of ECT agreed upon with its customer and/or eventual subsequent activities for a previous or successive party acting on or on behalf of that customer or with permission of the customer of ECT s customer. 8.22 SHIP OPERATING AGENT ECT considers a party as Vessel operating party just for specific vessel Data exchange; all other Data exchange will be done under the Container operator Data exchange. 8.23 SHIPPLANNING Zie CCE. 8.24 TRAIN INFO Pre-notification of containers in combination with train-composition. 35
8.25 TRUCK ECT considers Truck as hauliers transporting containers by road. 8.26 USER Any party who transfers, shares, obtains, exchanges Data directly or indirectly with ECT under this ECP. In case of indirect, transfer, share, obtain or exchange of Data by a User with ECT, the intermediate party automatically becomes a User. 8.27 VESSEL OPERATOR A party operating a commercial and dedicated deepsea vessel on international continental waters, by sequence rotation routings. This also includes consortia member lines operating on the same vessel. The Container Deepsea Vessel is a ship constructed to carry containers and fit to be handled by a container gantry crane with standard spreader, which vessel is owned or chartered (in whole or in part) by the Line and employed in rendering regular intercontinental container transportation liner services. 8.28 VOYAGE INFORMATION BARGE Pre-notification of barge call including forecast of load and discharge numbers provided by the barge operator via Portbase to ECT. 8.29 WEBSERVICE Functionality on the Website whereby Data is enabled to be entered, collected or exchanged regarding specific operational or administrative processes regarding ECT terminals. 8.30 WEBSITE The ECT website: www.ect.nl 8.31 3rd PARTY ECT considers 3rd Party as: APM Terminal B.V. and empty container depots (M.J. Kramer (Delta) Holding B.V. or Kramer Vastgoed BV) which are physically linked to ECT. 36