A global supply chain requires fast reaction to new business requirements. The best answer is with a direct system-to-system interchange, or a so-called “Bilateral EDI” connection (a directly connected electronic data interchange) that delivers efficiency gains for your company.
Our focus is placed on your transport chain processes, from procurement to finance. We aim to find the best fit for your specific requirements by mirroring your specific workflow.
For further details please contact your local Hapag-Lloyd Sales office or your Customer Service Representative today.
When looking at the introduction of useful EDI messages, we focus on your transport-process and endeavour to mirror your specific workflow with our inhouse processes to fit your specific requirements.
Hapag-Lloyd offers professional consultation to ensure mutual agreement on the best solution package to be achieved for your company; this may also involve further complementing e-Business features from our “toolbox” of e-Mail and web-solutions.
Below you will find, for illustration purposes the main typical process steps and touchpoints supporting your logistical needs, exemplary for EDIFACT.
Please find below an overview of our main EDI message types and the customer value they can create for your business.
Requirement | EDI message name | Message description | Customer value |
---|---|---|---|
Obtain Schedule Data | IFTSAI or ANSI 323 | Frequently updated Schedule data | Automatic update of Customer ERP system with latest sailing vessel schedule data. |
Submit Booking | IFTMBF or ANSI 300 | Customer Booking Request message with necessary detail commonly required to arrange for transport | Drives efficiency and better data quality through electronic submission, avoids double input of Booking details, can be generated directly out of Customer ERP system, speeds up processing, avoids fax-or email workload. |
Receive Booking Confirmation | IFTMBC or ANSI 301 | Confirms or declines Booking Request | Provides full detail of confirmed Booking with all relevant details of complete Routing Plan and automatic adoption of data in Customer's ERP system |
Submit verified container gross mass | VERMAS (alternative IFTMIN or ANSI 304) | Customer send verified container gross mass | Comfortable solution to provide the mandatory container total true gross weight information to the carrier as this information is mandatory safety requirement |
Submit B/L Instructions | IFTMIN or ANSI 304 | Customer message with detailed Shipping Instruction for B/L creation | Significant efficiency gains through electronic submission, individual customizing, enhanced data quality, minimizes B/L Draft Cycle efforts, avoids duplication of data, supports faster Document turnaround time |
Obtain B/L Data / Contract Status | IFTMCS or ANSI 310 | Provides Contract Status / B/L data | Allows Customers to use B/L data for inhouse processing and electronically share same with Business Partners, saves time and additional communication efforts |
Receive Status events / Tracing | IFTSTA or ANSI 315 | Delivers latest status on container or vessel events |
Comprehensive scope for all main events along the complete transport-chain, can be individually customized, may include dynamic vessel events, provides timely and proactive information to support Customer Business steering and visibility. |
Obtain Freight Invoice | IFTFCC or ANSI 310 | Provides full detail of Carrier freight invoice | IFTFCC is a modernized EDI Invoice for greatly improved detail and customer usability; it eliminates hardcopy invoicing, facilitates usage of data for payment / accounting processes directly in Customer ERP system and supports leaner workflow process. |
Get Arrival Notification | IFTMAN, ANSI 312 or freighted ANSI 310 | Provides advance notification of arrival for customer shipments | Informs about shipment details in support of IMPORT view prior to Vessel arrival; permits steering of import process directly in Customer ERP system, and offers combination with invoice details on "collect" charges when "freighted arrival notice" is used |
Technical message-receipt Information | CONTRL or ANSI 997 | Constitutes a message that verifies if transmitted EDI data has been adequately received | Supports customer's need for assurance on frequent monitoring of data flow and early detection of any network problems. |