Proposal for implementation of eDO and Container … - Gate Module... · Web viewThis document...

33
Proposal for implementation of eDO and Container Delivery in PCS Version : 1.3

Transcript of Proposal for implementation of eDO and Container … - Gate Module... · Web viewThis document...

Page 1: Proposal for implementation of eDO and Container … - Gate Module... · Web viewThis document provides the system requirements specification for the implementation of electronic

Proposal for implementation of eDO and Container Delivery in PCS

Version : 1.3

Page 2: Proposal for implementation of eDO and Container … - Gate Module... · Web viewThis document provides the system requirements specification for the implementation of electronic

RELEASE HISTORY

VERSION NUMBER

DATE (DD/MM/YYYY)

SECTION REFERENCE

BRIEF SUMMARY OF CHANGES

1.0 22/03/2016 Initial Version

1.1 03/06/2016 Incorporated with the feedback received from Kolkata and JNPT

1.2 22/06/2016 Updated as per the feedback received from Ports during workshop conducted by IPA on 8th June’16 at Delhi also feedback received post workshop from various ports:

Removed Tranport Order in case of CFS bound containers

Transport Order Acknowledgement is removed for both import and export processes

Updated Import and Export processes

Back to town containers are mentioned in IMP-08

1.3 24/06/2016 Updated as per comments received from meeting held in JNPT on 24th June’16

Page 1 of 28

Page 3: Proposal for implementation of eDO and Container … - Gate Module... · Web viewThis document provides the system requirements specification for the implementation of electronic

Contents1. Introduction..............................................................................................................2

2. Definitions and Abbreviations...............................................................................2

3. Assumptions and Constraints................................................................................3

4. Functional Requirements.......................................................................................3

4.1 Work Flow..........................................................................................................3

4.1.1 Import Process.....................................................................................................3

4.1.2 Export Process.....................................................................................................9

4.2 Electronic Delivery Order..............................................................................13

4.2.1 Data Elements....................................................................................................15

4.3 Transport Order..............................................................................................16

4.3.1 Data Elements....................................................................................................16

4.4 Gate Open – Cut off time................................................................................17

4.4.1 Data Elements....................................................................................................17

4.5 Delivery Gate Schedule..................................................................................18

4.5.1 Data Elements....................................................................................................18

4.6 Gate-In Appointment Booking......................................................................19

4.6.1 Data Elements....................................................................................................20

4.7 Pre Gate...........................................................................................................21

4.7.1 Data Elements....................................................................................................22

Page 2 of 28

Page 4: Proposal for implementation of eDO and Container … - Gate Module... · Web viewThis document provides the system requirements specification for the implementation of electronic

1.Introduction This document provides the system requirements specification for the implementation of electronic delivery order (eDO) and process for implementation of container delivery [Import] and receiving [Export] in PCS.

2.Definitions and AbbreviationsAbbreviation DescriptioneDO Electronic Delivery OrderDPD Direct Port DeliveryTOS Terminal Operating SystemPOS Port Operating SystemVCN Vessel Call NumberPCS Port Community SystemBL Bill of LadingCA Container AgentCT Container TerminalCFS Container Freight StationCHA Custom House AgentCLP Container Loading PlanEDI Electronic Data InterchangeEGM Export General ManifestEIR Equipment Interchange ReceiptEO Entry OutwardETA Expected Time of ArrivalFCL Full Container LoadOOC Out Of ChargeSB Shipping BillUI User InterfaceICD Inland Container DepotICEGATE Indian Customs and Excise GatewayIGM Import General ManifestISO International Organization for StandardizationIST Indian Standard TimeLCL Less Container LoadLEO Let Export OrderMMD Mercantile Marine Department.NIC National Informatics CentrePAN Permanent Account Number (given by Income Tax Dept.)XML Extensible Markup Language

Page 3 of 28

Page 5: Proposal for implementation of eDO and Container … - Gate Module... · Web viewThis document provides the system requirements specification for the implementation of electronic

H2H Host-to-Host

3.Assumptions and Constraints This module will be developed on the existing PCS system No digital signature is required since it is Host-to-Host communication For Host-to-Host integrations, all stakeholders should comply to the message

specifications provided by PCS To use features of this module, all users should be registered with PCS and

should have valid user ID and password Message format to be supported is XML and TXT for all the messages

mentioned in this module

4.Functional Requirements Following functionality will be implemented in existing PCS in order to cater electronic delivery order and delivery of container:

Electronic Delivery Order (eDO) Transport Order Gate Open – Cut off time Delivery Gate Schedule Gate-In Appointment Booking Pre-Gate

4.1 Work FlowFollowing table depicts the overall work flow of container delivery (import & Export):

4.1.1 Import Process

PROCESS ID

BUSINESS PROCESS PROCESS IN PCS VALIDATIONS TO BE CONSIDERED IN PCS

IMP-01 Consignee or his appointed forwarder/broker presents original BL to shipping agent for release of container.

Shipping agent checks all necessary documents, payments and

This is a manual process and not covered in PCS

Page 4 of 28

Page 6: Proposal for implementation of eDO and Container … - Gate Module... · Web viewThis document provides the system requirements specification for the implementation of electronic

processes (shipping agent internal business requirements)

Note: Usual practice for appointment of Forwarder/ Broker is via a hardcopy Authorisation Letter.

IMP-02 Issuance of Delivery Order:

Shipping Agent issues Delivery Order after their internal proceedings are completed

Note: Shipping agent is the authorised agent for the vessel / voyage (SOA or slot owner / consortium member)

For Web Users:

For DPD Containers:

Shipping Agent login to PCS : Go to menu Container

Delivery Order Select VCN / VIA

number Enter Container No, BL

no and other mandatory fields provided in the eDO web form

SA submits the eDO form once all mandatory fields are filled

eDO Reference No will be generated by PCS.

PCS generates eDO message in XML format and transmits to Terminal, Port and Customs

For CFS Containers:

No eDO is required; however PCS allows the Container movement based on destination code of CFS from IGM

For H2H Users: PCS receives eDO

message in XML format from Shipping Lines internal system as per the data elements mentioned under section 4.2.1 however eDO reference number should be unique in the PCS and format of the

Container no. and BL no. against Inward Manifest

Forwarder / Broker is a valid business entity

Customs release has been granted for the BL / container (depending on local customs requirement, this validation can be postponed to Gate Booking, Pre-Gate or actual Gate Entry stage)

EDO Ref no. must be unique for the Vessel / Voyage

Note: Onus should be on the shipping agent to ensure the EDO is issued to the right party.

Page 5 of 28

Page 7: Proposal for implementation of eDO and Container … - Gate Module... · Web viewThis document provides the system requirements specification for the implementation of electronic

eDO number should be defined by PCS.

IMP-03ISSUANCE OF TRANSPORT ORDER:

For DPD Containers:Forwarder / CHA issues Transport Order to Transporter against one or more eDOs

For CFS bound containers:CFS issues Transport Order to shift the container to CFS.CFS provides list of all transporters who will move the containers from Port to CFS

Only Web UI (No messaging):For DPD Containers:CHA / CFS login to PCS: Go to menu Transport

Transport Order Select VCN / VIA Select one or more

eDO numbers from UI Selects a transporter

by entering Transporter Registration No.

Submit Transport Order once all other mandatory fields are entered

PCS generates Transport Order number and sends email notification to Transporter with transport order number which is generated by PCS

For CFS bound containers:

No Transport Order required for CFS bound containers, however CFS can provide all list of transporters which they will deal with that specific containers

EDO reference no. is valid for the Vessel/Voyage

Forwarder / Broker is the authorised released party for the EDO

Transporter is a valid business entity

IMP-04 TRANSPORTER ACKNOWLEDGEMENT:

Transporter accepts / acknowledges Forwarder / CHA / CFS

Only Web UI:Transporter login to PCS: Go to menu Transport

Transport Order PCS displays all

Transport Orders which are pending action from Transporters

Transporter selects Transport Order and click on accept

PCS sends email notification to CHA that

Page 6 of 28

Page 8: Proposal for implementation of eDO and Container … - Gate Module... · Web viewThis document provides the system requirements specification for the implementation of electronic

transporter accepted the transport order

PCS generates transport order XML file and transmits to Port and Terminal

IMP-05 Pre-Gate / Pickup Ticket:

For DPD Containers:Transporter provides pre-gate information like Vessel / Voyage Container no Truck-id / Registration No. Driver details

For CFS Containers:

Transporter provides pre-gate information like:

Vessel / Voyage Truck –ID / Registration No Driver Details

PCS generates and sends the pickup ticket to Terminal TOS and Customs ICEGATE.

Only Web UI:

For DPD Containers:Transporter login to PCS: Go to menu Container

Pre-Gate Enter container

number, driver details and submit

PCS generates Picket Ticket message in XML format and transmit to Port, Terminal and customs.

Transporter prints Pick up ticket with barcode (PCS generated number)

For CFS Bound containers:CFS generate pre-gate information in messages and transmit to PCS

PCS validates: Truck-id is valid

(validate against VAHAN database of MOST) the meeting discussed the possibility of validating against truck registration database of local port instead of VAHAN database.

Truck belongs to Transporter (pre-captured in PCS, if sub-contracting or outsourcing is required, this function can be provided in PCS)

Driver-id is valid (validate against Terminal Entry Pass system)

Driver belongs to Transporter (pre-captured in PCS, if sub-contracting or outsourcing is required, this function can be provided in PCS)

IMP-06 Entry Gate:

Upon production of Pickup ticket print by the TT Driver, CISF personnel verifies the TT number as per print and allows inward entry inside Port Area after verifying the driver license.

TOS Gate system performs the following:

Web UI:CISF login to PCS: Go to Container

Pre-Gate Verify all details like

eDO, Container No, Customs clearance, Transport Order, Driver Name and ID and allow.

Or

Page 7 of 28

Page 9: Proposal for implementation of eDO and Container … - Gate Module... · Web viewThis document provides the system requirements specification for the implementation of electronic

Identify the truck by reading the truck-id RFID (if available, else enter the truck no. into the Gate system)

Validates the driver-id via bio-metric Terminal Entry system (if available, else enter truck-id into the Gate system) and driver PIN.

Gate system checks against E-EIR to confirm container no., truck-id and driver-id.

Re-assign the container if any change in the

CISF personnel will verify the details with physical Pre-Gate print.

IMP-07 PICKUP OF IMPORT CONTAINER FROM IMPORT YARDS.The TT approaches the yard location as indicated in the pick up ticket for picking up the import container as detailed in the ticket. If the container is available readily on Top, the same container is loaded or any other container of the same CFS will be loaded using yard crane in order to avoid undue shifting's based on the import pendency list. The Yard crane loads the import container on the TT according to the information available with them on Vehicle Mounted Terminal / Pendency List.Tractor Trailer carrying import container(s) approaches Out-Gate. For collecting EIR.

Manual process

IMP-08 GENERATION OF EQUIPMENT INTERCHANGE REPORT (EIR) AT FRONT LOADING STATTION:.

Based on the transaction number available on Pick-up Ticket with Driver and the container on Tractor Trailer, EIR is generated and all 4 copies are handed over to him for getting Customs Approval. In case change of container, the container detailed as swapped in the system

TOS / POS updates the details and transmits the EIR message to PCS

Page 8 of 28

Page 10: Proposal for implementation of eDO and Container … - Gate Module... · Web viewThis document provides the system requirements specification for the implementation of electronic

before generating EIR.

Note: In case of Back to town (Export) containers, it will follow the same process as per import process

IMP-09 CUSTOMS APPROVAL PRIOR TO OUTWARD EXIT OF IMPORT CONTAINERS DELIVERED:

After receipt of EIR copies from Terminal, the TT Driver approaches Customs located near Out Gates for authorization of Customs on these EIR copies.

Customs officer will check the clearance of this container in ICEGATE or PCS

PCS gets transmits the message to Port / Terminal from ICEGATE once container clearance is done by customes.

In case of DPD, EIR will be generated once customs clearance is done.

Page 9 of 28

Page 11: Proposal for implementation of eDO and Container … - Gate Module... · Web viewThis document provides the system requirements specification for the implementation of electronic

IMP-10 OUTGATE CHECK BY CIFS:Upon receipt of authorization from Customs on EIR, the TT Driver along with TT carrying import containers approaches CISF personnel at the Out Gates who physically verifies the relevant details available on EIR.Mentions actual time of outward movement of TT on EIR, handover two copies of EIR to the Driver of TT and the container is allowed to go out. However, two copies are retained by CISF along with actual time of outward movement of TT carrying import container out of which one copy is handed over to port/terminal later on for records.

Web UI:CISF login to PCS: Go to menu Container

EIR Verify EIR with all

details.

IMP-11 The TT carrying import containers proceeds to concerned CFS / Factory / Empty Container Yards accordingly.

Not covered in PCS

Page 10 of 28

Page 12: Proposal for implementation of eDO and Container … - Gate Module... · Web viewThis document provides the system requirements specification for the implementation of electronic

4.1.2 Export Process

PROCESS ID

BUSINESS PROCESS PROCESS IN PCS VALIDATIONS TO BE CONSIDERED

IN PCS

EXP-01 FILING OF SHIPPING BILL:

1. Exporter files the Shipping Bill on ICEGATE. ICEGATE forwards the Shipping Bill to PCS.

2. Exporter prepares shipment of goods, and books empty container(s) with the Shipping Line. Shipping Line issues a delivery order. Exporter’s transporter takes container for stuffing [ICD Stuffing, Factory Stuffing, Self-Sealing, CFS stuffing ]

1. PCS will transmit Shipping Bill details to respective Port / Terminal.

2. Off line; not covered in PCS;

EXP-02 ISSUANCE OF TRANSPORT ORDER:

Exporter / Forwarder / CHA issues Transport Order to Transporter against one RFDor more eDOs

Note:

Forwarding agent prepares Request For Delivery (RFD) and submits it to haulier/transport company together with transport /movement order (24 to 48 hours before pick up date for haulier to plan). Depots release empty container to haulier

Transporter picks up empty

Only Web UI (No messaging):CHA login to PCS: Go to menu Transport

Transport Order Select VCN / VIA Select one or more eDO

numbers from UI Selects a transporter by

entering Transporter Registration No.

Submit Transport Order once all other mandatory fields are entered

PCS generates Transport Order number and sends email notification to Transporter with transport order number which is generated by PCS

EDO reference no. is valid for the Vessel/Voyage

Forwarder / Broker is the authorised released party for the EDO

Transporter is a valid business entity

Page 11 of 28

Page 13: Proposal for implementation of eDO and Container … - Gate Module... · Web viewThis document provides the system requirements specification for the implementation of electronic

container & delivers it to exporter’s premises

Exporter stuffs the container, seals and informs transporter to

pick up the container

Page 12 of 28

Page 14: Proposal for implementation of eDO and Container … - Gate Module... · Web viewThis document provides the system requirements specification for the implementation of electronic

EXP-03 TRANSPORTER ACKNOWLEDGEMENT:

Transporter accepts / acknowledges Forwarder / CHA

Only Web UI:Transporter login to PCS: Go to menu Transport

Transport Order PCS displays all Transport

Orders which are pending action from Transporters

Transporter selects Transport Order and click on accept

PCS sends email notification to CHA that transporter accepted the transport order

PCS generates transport order XML file and transmits to Port and Terminal

EXP-04 GATE OPEN – CUT OFF SCHEDULE - DELIVERY BOOKING:

Terminal publishes / informs Delivery Booking Schedules to all Transporters. Delivery booking details mainly contains time slots and number of containers allowed in each time slot.

For Web Users:Terminal login to PCS: Go to menu Container

Delivery Booking Schedule

Create booking schedules for each VCN by providing Delivery Schedule Date/Time From and Date/Time To andQuantity of containers acceptable per Time Slot

PCS sends email notification to all transporters who are accepted transport order for that VCN

For H2H Users: Terminal TOS to send

Booking Schedule to PCS via back-end messaging

Refer to message spec 4.5.1

Page 13 of 28

Page 15: Proposal for implementation of eDO and Container … - Gate Module... · Web viewThis document provides the system requirements specification for the implementation of electronic

EXP-05 APPOINTMENT BOOKING FOR DROPPING CONTAINER:

Transporter / CFS books Time Slot for delivery of containers as per delivery gate schedule

Only Web UI:Transporter login to PCS: Go to menu Container

Gate-In Appointment Booking

Enter VCN / VIA number and click on retrieve time slots

Select Time Slot and enter the quantity of containers

PCS generates message for Gate-In Appointment Booking in XML format and send to Terminal and Customs

Once Vessel / Voyage is keyed in, PCS will display all available Time Slot and balance quantity of containers available for booking

PCS validates that quantity of containers entered does not exceed balance available quantity for the time slot.

EXP-06 PRE-GATE & GENERATE DROP-OFF TICKET

Transporter SA / CFS provides pre-gate information like Vessel / Voyage Delivery Time Slot Container no Truck-id / Registration No. Driver details

PCS generates and sends the Pre Gate message to Terminal TOS and Customs ICEGATE.

Web UI:Transporter / SA login to PCS: Go to menu Container

Pre-Gate Select Gate-In window Enter container number,

driver details and submit PCS generates pre-gate

message in XML format and transmit to Port, Terminal and customs.

Transporter prints Pre-Gate with barcode (PCS generated number)

CFS / SA / Custodian can send this message to PCS.

PCS validates: Truck-id is

valid (validate against VAHAN database of MOST) the meeting discussed the possibility of validating against truck registration database of local port instead of VAHAN database.

Truck belongs to Transporter (pre-captured in PCS, if sub-contracting or outsourcing is required, this function can be provided in PCS)

Driver-id is valid (validate against Terminal Entry Pass system)

Driver belongs

Page 14 of 28

Page 16: Proposal for implementation of eDO and Container … - Gate Module... · Web viewThis document provides the system requirements specification for the implementation of electronic

to Transporter (pre-captured in PCS, if sub-contracting or outsourcing is required, this function can be provided in PCS)

No. of line items does not exceed available balance quantity for the Time Slot

EXP-07 ENTRY INTO EXPORT GATE:

Upon arrival at the Terminal Gate, Gate Officer Does the necessary checks against Customs Release, eDO, Transport Order, Pre-Gate, etc and allows empty truck entry

TOS Gate system performs the following: Identify the truck by reading

the truck-id RFID (if available, else enter the truck no. into the Gate system)

Validates the driver-id via bio-metric Terminal Entry system (if available, else enter truck-id into the Gate system) and driver PIN.

Gate system checks against E-EIR to confirm container no., truck-id and driver-id.

TOS / POS Gate system PCS transmits SB and OOC LEO to respective Port / Terminals from ICEGATE. Customs can verify these details in PCS / ICEGATE before allowing in to the Port / Terminal

EXP-08 CHECK BY CISF AT EXPORT GATE:The CISF personnel posted at In-Gates physically verifies details such as TT number, Container no, Seal No, Drivers details available on Drop-Off-Ticket and the TT is allowed inside the Port Area after retaining one copy of DOT with CISF mentioning actual inward entry of TT on all copies.

Manual (Off line)

Page 15 of 28

Page 17: Proposal for implementation of eDO and Container … - Gate Module... · Web viewThis document provides the system requirements specification for the implementation of electronic

EXP-09 DROP OFF CONTAINER AND TT EXIT:The TT carries the container to designated yard location as indicated in Drop off Ticket. After offloading the container in export yard by the Yard Crane, the empty TT approaches Out-Gate for exit. The Out –Gate Clerk completes the transaction in the system (against transaction number printed in the Drop-Off-Ticket carried by the Driver of TT).

Manual (Off line) PCS Validates the export containers movements against the Gate open and cut-off date and time

EXP-10 CHECK BY CISF AT OUT GATE:

CISF posted at Out Gate collects one copy Drop off print, mentions actual time of outward movement of empty TT on the copy while allowing the TT for outward movement. (This copy is then deposited to Terminal for records).

Manual (Off line)

4.2 Electronic Delivery OrderA Delivery Order is the order given by Carrier of goods or authorized shipping

agent to the importer’s customs broker to take delivery of goods once destination ports customs clearance process is completed.

PCS provides UI to issue DO electronically:

Page 16 of 28

Page 18: Proposal for implementation of eDO and Container … - Gate Module... · Web viewThis document provides the system requirements specification for the implementation of electronic

Fig.4.2. Delivery Order

Page 17 of 28

Page 19: Proposal for implementation of eDO and Container … - Gate Module... · Web viewThis document provides the system requirements specification for the implementation of electronic

4.2.1 Data ElementsPCS uses following data elements to generate eDO (AGDORD) in XML format. Structure of the eDO is as shown below:

Header:

S/N Field name Type Length Status1 Record Type C 1 M2 Delivery Order Number (LDO/ADO No) C 20 C3 Delivery Order Date (LDO/ADO Date) D - C4 Delivery Order for Examination (Y/N) C 1 M5 Validity Period up to (ADO/LDO) D - C6 VIA/VCN C 14 M7 Call Sign/Vessel Code C 10 M8 IMO Number C 10 M9 Voyage Number C 10 M10 Whether (F)oreign/(C)oastal (Y/N) C 1 M11 IGM Number N 5 C12 IGM Date D - C13 IGM Line Number N 4 C14 IGM Sub Line Number N 4 C15 Bill of Lading No C 20 M16 Bill of Lading Date D - M17 House Bill of Lading Number C 20 C18 House Bill of Lading Date D - C

Details: [ Repeat 1..N ]

S/N Field Name Type Length

Status1 Record Type C 1 M2 Record Number N 6 M3 IGM Number N 7 M4 IGM Date D - M5 IGM Line Number N 4 M6 IGM Sub Line Number N 4 C7 Bill of Lading/LDO/ADO No C 20 M8 Bill of Lading/ADO/LDO Date D - M9 Validity Period up to (ADO/LDO) D - C10 Name of Consignee C 35 M11 Consignee Address 1 C 35 M12 Consignee Address 2 C 35 C13 Consignee City C 15 M14 Consignee State C 15 M15 Port of Loading (POL) C 6 M16 Port of Discharge (POD) C 6 M

Page 18 of 28

Page 20: Proposal for implementation of eDO and Container … - Gate Module... · Web viewThis document provides the system requirements specification for the implementation of electronic

17 Containerized (Y/N) C 1 C18 Container No. C 12 C19 ISO Code of Container C 4 C20 Cargo Description C 250 M21 Number of Packages N 5 C22 Package Code C 3 C23 Marks and Numbers C 100 M24 Number of 20 Feet Containers C 3 C25 Number of 40 Feet Containers C 3 C26 Number of Odd Size Containers C 3 C27 Currency Code C 3 M C28 Value in INR (Rs.) N 10.2 M C29 Freight Paid (Y/N) C 1 M C30 Receipt Number C 12 C31 Receipt Date D - C32 Stamp Duty (Y/N) C 1 M33 Stamp Duty Paid Amount N 13.2 C34 Stamp Duty Paid Date D - C35 Delivery to ( Name of Agent ) / Importer / CHA C 35 M36 Authorization code of agent C 15 C37 Authorization code of CHA C 15 C38 Total Gross weight (M.T.) N 10.2 M39 Direct (D) / Transit (T) C 3 C

40 Stage (Full (F)/Part Delivery (P)) C 3 C

41 IE Code C 16 M C

4.3 Transport OrderTransport Order is an order given by CHA to the transporter once Shipping Agent issues Delivery Order to CHA. This order is to inform the transporter to deliver the cargo to the consignee or importer location. Up on Transporter acknowledges the transport order issued by CHA, PCS generates the message in XML format and send to Terminals, Port and Customs if required. This is new message and below data specification have to be reviewed and finalized.

4.3.1 Data Elements PCS generates the transport order message in XML format with the following data elements and send to Terminals, Port and Customs if required.

S/N Field name Type Length Status1 Record Type C 1 M2 Transport Order Number (PCS generated Number) C 20 M3 Transporter Registration No C 20 M4 Transporter Name C 50 M5 Delivery Order Number (eDO) C 20 M

Page 19 of 28

Page 21: Proposal for implementation of eDO and Container … - Gate Module... · Web viewThis document provides the system requirements specification for the implementation of electronic

6 Delivery Order Date D - M7 Validity Period up to D - C8 VIA/VCN C 14 M9 IMO Number C 10 M10 Transport Order Issued by (CHA Code) C 20 M11 Transport Order Issued Date & time

(DDMMYYYY:24HH:MM) C 20 M12 Transport Order Ack date & time (DDMMYYYY:24HH:MM) C 20 M13 Port Delivery Order Number C 20 M

4.4 Gate Open – Cut off timeBefore arriving the vessel in Port, specific hours in advance, Port opens the

gate so that CHA/ Exporter can bring their Container/ Cargo in Port. Similarly Port gives cut off time indicating that the before that time Container / Cargo need to bring to Port. This is done to stream line the loading and un-loading operation on Vessel.

Fig.4.4. Gate Open – Cut off Report

4.4.1 Data Elements Ports or Terminals should use the following data specification for sending Gate Open – Cut off time message in XML format.

S / N Field Type Length Status1. Record Type C 1 M2. VCN C 14 M3. Call Sign/Vessel Code C 10 C M4. IMO Number C 10 M5. Rotation Number C 5 C6. Rotation Date D - C7. Vessel Operator/ Shipping Agent C 15 M C

Page 20 of 28

Page 22: Proposal for implementation of eDO and Container … - Gate Module... · Web viewThis document provides the system requirements specification for the implementation of electronic

8. WIN Schedule Date D - C9. ETA D - M10. Port Floating Line/Length Date & Time D - C11. Cut Off Date and Time

(DDMMYYYY:24HH:MM)D - M

4.5 Delivery Gate ScheduleTerminal or Port publishes the delivery gate schedule to transporters which contains time slots and number of containers allowed in each time slot.

Fig.4.5. Delivery Gate Schedule

4.5.1 Data Elements Ports or Terminals should use the following data specification for sending Delivery Gate Schedule message in XML format.

FLOW: Terminal / Port PCS

Page 21 of 28

Page 23: Proposal for implementation of eDO and Container … - Gate Module... · Web viewThis document provides the system requirements specification for the implementation of electronic

S / N Field Type Length Status1. Record Type C 1 M2. VCN C 14 M3. Call Sign/Vessel Code C 10 C M4. ETA D - M5. IMO Number C 10 M6. IGM Number N 5 C7. IGM Date D - C8. Rotation Number C 5 C9. Rotation Date D - C10. $ Gate-In Window From

(DDMMYYYY:24HH:MM)C - M

11. $ Gate-In Window Up to (DDMMYYYY:24HH:MM)

C - M12. $ Type of Cargo (REF, DRY, OOG, PERI,

GEN)C 4 M

13. $ Number of containers allowed N - MC14.[13.] Cut Off Date and Time

(DDMMYYYY:24HH:MM)C - M

Note: $ represents repetition; data elements 10, 11 & 12 will repeat more than one time as group in the same sequence.

4.6 Gate-In Appointment BookingTransporters will do Gate-In Appointment booking from PCS web user interface based on the Delivery Gate Schedule provided by Terminal. PCS validates number of containers allowed in each slot against the maximum number of containers allowed by terminal.

Page 22 of 28

Page 24: Proposal for implementation of eDO and Container … - Gate Module... · Web viewThis document provides the system requirements specification for the implementation of electronic

Fig.4.6. Gate-In Appointment Booking

4.6.1 Data ElementsTransporter will do the gate-in appointment booking based on the available slots published by terminals. Transport will login to PCS and select the respective VCN and slot and enter the number of containers to be delivered. PCS will generate the message in XML formal and transmit to Terminal.

FLOW: PCS Terminal / Port

Page 23 of 28

Page 25: Proposal for implementation of eDO and Container … - Gate Module... · Web viewThis document provides the system requirements specification for the implementation of electronic

S / N Field Type Length Status1. Record Type C 1 M2. VCN C 14 M3. Call Sign/Vessel Code C 10 M4. ETA D - M5. IMO Number C 10 M6. IGM Number N 5 C7. IGM Date D - C8. Rotation Number C 5 C9. Rotation Date D - C10. $ Gate-In Window From

(DDMMYYYY:24HH:MM)C - M

11. $ Gate-In Window Up to (DDMMYYYY:24HH:MM)

C - M12. $ Type of Cargo (REF, DRY, PERI, OOG,

GEN)C 4 M

13. $ Number of containers to be delivered N - MC14.[13.] Cut Off Date and Time

(DDMMYYYY:24HH:MM)C - M

Note: $ represents repetition; data elements 10, 11 & 12 will repeat more than one time as group in the same sequence.

4.7 Pre GateTransporter provides the pre gate information like VCN, slot number, container numbers, truck ID and driver details before truck enters the gate. PCS generated the message with these details and transmit to Terminal.After pre-gate information is submitted, PCS generates a message in XML format and also shows PCS Reference Number in 2D barcode to the transporter. Transporter can print the pre gate details with barcode and carry with driver while entering the gate. At gate, terminal / port can scan the barcode and allow the truck inside.

Page 24 of 28

Page 26: Proposal for implementation of eDO and Container … - Gate Module... · Web viewThis document provides the system requirements specification for the implementation of electronic

Fig.4.7. Pre Gate

4.7.1 Data ElementsPCS generates the Pre Gate message with below data elements once transporter submits the pre gate details in PCS.

S / N Field Type Length Status

1. Message Type C 3 M

2. VCN C 14 M

3. Vessel Code C 10 M

4. IMO Number C 10 M

5. Voyage Number C 10 M

Page 25 of 28

Page 27: Proposal for implementation of eDO and Container … - Gate Module... · Web viewThis document provides the system requirements specification for the implementation of electronic

6. Equipment Status code (UN/EDIFACT Segment 8249)

Import / Export / Transshipment Flag ( I/ E / T )

C 3 M

7. Origin type (Factory (FAC) / CFS (CFS)

C 3 M

8. Date & Time of Arrival of truck D - M

9.[8.] Transporter Name/Company C 35 MC

10.[9.] Transporter Registration Number C 15 C

11. Truck Number C 12 M

12.[10.] Name of the Driver C 35 M

13.[11.] Driver Licence Number C 15 C M

14.[12.] Driver Mobile Number N 10 M

15. Container Number C 12 MC

16.[13.] Gross Weight N 13.2 M

17.[14.] Verified Gross Mass N 13.2 M

18. UOM (MT, KG) C 4 M

19. ISO Code of Container C 4 C

20.[15.] Container Type Classification Code * ( 8169)( FCL/ LCL/ETY)

C 3 MC

21.[16.] Container Temperature (Mandatory in case of REF container) (C / F)

C 1 C

22. IMO Code C 3 C

23. UN Number of Container C 4 C

24. Custom Seal Number (Mandatory for CFS stuff)

C 15 C

25.[17.] Agent Seal Number C 15 C

26.[18.] Terminal Seal Number C 15 C

27.[19.] Excise Seal Number (Mandatory for Factory Stuff)

C 15 C

Page 26 of 28

Page 28: Proposal for implementation of eDO and Container … - Gate Module... · Web viewThis document provides the system requirements specification for the implementation of electronic

28.[20.] POD – Port of Discharge C 6 M

29.[21.] Port Yard Position for Container/ Rack Position

C 10 C

[22.] Final Port of Discharge/Destinationignation

C 6 M

30.[23.] CHA Name / CHA Code C 35 C

31.[24.] Shipper/Consignee Name C 35 C

32.[25.] MLO / Shipping Line Code C 16 C

33.[26.] Special Details C 35 C

34.[27.] Customs scanning (Y/N) ? C 1 C

Page 27 of 28