EIDX/CompTIA Shipment Model 1.7
Physical Movement Component

Click here to view a larger image.

Attributes
Note that the ANSI standards encompass the traditional Transportation Data Coordinating Committee (TDCC) 100, 200, 300 and 400 series transaction sets which are mode specific. Also included in ANSI is the 856, 810, 859 and 990 transaction sets which are not mode specific. The EDIFACT messages are not mode specific.

Various and multiple iterations of data exchange may occur for accessorial services, such as warehousing, consolidation, etc.

The Load Tender/Response may not apply to all carriers. (A) The shipper may tender the goods for shipment and/or request a bid for services of the carrier, consolidator or forwarder.

The carrier, consolidator or forwarder may then perform none, one, more than one, or all of the following functions: (B) Send back to the shipper a response to the shipper’s request for services or request for quote for services.

• Response to tender: IFTMBP, 990
• Provisional Booking: IFTMBP, 990
• Firm Booking: IFTMBF, 990
• Booking Confirmation: IFTMBC, 990

(C) Send to Shipper shipment information concerning the initial movement of the goods.

(D) Send to Shipper information concerning:

• Intransit status of the shipment
• Delivery of the shipment.

(E) Send to Consignee shipment information concerning the initial movement of the goods.

(F) Send to Consignee information concerning:

• Intransit status of the shipment
• Delivery of the shipment.

(G) Send to the appropriate party, as determined by the specific contractual arrangements, freight and related charges information and/or invoice.  Please refer to the freight payment cycle for full EIDX recommendations.