EIDX Home  
  About EIDX  
  Benefits of Membership  
  Business Process  
Current Projects
Clickable Business Models
Business Model Navigational Help
Business Model Development Methodology
Business Model Legends
  Education  
  Guidelines & Standards  
  Technology  
  Reference Materials  
  Meetings & Events  
  Discussion Forums  
  Community  
  Presentations  
  Work Groups  

LOGIN
PASSWORD
remember my login
forgot my password

EIDX/CompTIA Shipment Model I

Domestic Ship Cycle Overview
Invoice and shipment information originated with the seller/shipper is augmented by the carrier and buyer/consignee.


Click here to view a larger image.


Shipment Notification Component


Click here to view a larger image.

Domestic Ship-Cycle Detail
Shipment Notification Component (A) - Scenario Composite


Click here to view a larger image.

Attributes: Shipper/Seller to Buyer at time of physical shipment

Combined "Seller/Shipper Buyer/Consignee" Scenario

Separate Scenarios:

  • Shipment Model 1.2.   Seller = Shipper and Buyer = Consignee
  • Shipment Model 1.3.  Seller = Shipper and Buyer = Consignee
  • Shipment Model 1.4.  Seller = Shipper and Buyer = Consignee
  • Shipment Model 1.5.  Seller = Shipper and Buyer = Consignee

CONTENT: MATERIAL INFORMATION AND INFO RELATED TO PHYSICAL SHIPMENT
(Part Product Info, Quantity, PO#, Related Timing, Serial Numbers, Certs, "C" of "C", Shipment #, Packing Info, Physical Attributes (packing list), Bill of Lading #, Pro #, Timing (ETA, Ship/Avail Dates), Shipment Attributes, etc.)

USES: SHIP NOTIFICATION; MATCH TO BAR CODE RECEIVING; TRACKING PURPOSES; INFO TO PROCESS PHYSICAL RECEIVING

NOTE: Sending of data already sent by another entity should be avoided. BSN01 = "00" (Original) for 856, BGM03 = "9" (Original) for DESADV

Domestic Ship Cycle -Basic Terms and Definitions:

  • SELLER Party legally obligated to provide product to the buyer.
  • SHIPPER  Party responsible to arrange or schedule transportation for "seller’s" goods to buyer.
  • CARRIER  Mover or transporter of products.
  • CONSOLIDATOR Party that provides "store and forward" value added services.
  • CONSIGNEE Party designated by buyer to receive the goods.
  • BUYER Party (such as purchasing agent) that contracted with seller to provide goods.
  • PRO # Shipment reference number assigned by carrier.
  • HAWB House Airway Bill. Assigned by carrier (like PRO # but a shipper’s document).
  • MAWB Master Airway Bill. Carrier’s airway bill number.  Can have many HAWbs associated with it.
  • CERTS Certificates of compliance.
  • "C" of "C"  Certificates of conformance.
  • SHIPMENT ATTRIBUTES Container #’s, Carton ID’s, TCN’s.
  • PHYSICAL ATTRIBUTES Weight, Dimensions (DIMS), etc.
  • SERVICE LEVEL Measure of transit time.
  • MODE Type of transportation. Physical way the goods move.
  • MULTI-MODAL More than one mode of transportation is used.
  • B/L INFO  All information necessary for the carrier to move freight.
  • TERMS/CONDITIONS   NOTE: Trading partner and carrier/consolidator are assumed to have an existing business terms/conditions agreement or standard operating procedure in place.
  • TRAILER  The container portion of a tractor/trailer combination.
  • TRACTOR  The engine/cab portion of a tractor/trailer combination.
  • LTL Less that Truck Load.
  • TL  Truck Load.
  • TERMINAL TYPES
    • Origin = From shipper to this the first terminal.
    • Destination = The terminal just before delivery to the consignee.
    • Break Bulk = Between the origin and destination where freight is sorted and rerouted.

NOTE: On any given shipment can use some or all of the above.

  • 100/200/300/400 SERIES Are mode-specific Transportation Data Coordinating Committee (TDCC) originated ANSI transaction sets:
    • 100 = Air 104, 110, 114
    • 200 = Motor 204, 210, 213, 214, 217, 218
    • 300 = Ocean 300, 301, 303, 304, 309, 310, 312, 313,
    • 315, 322, 323, 324, 350, 353, 354, 361
    • 400 = Rail 404, 410, 414, 417, 418, 426, 431, 466, 468, 485, 490, 492, 494
  • 858 ANSI Transaction Set "Shipment Information." EIDX decided not to consider its use since a unique version would be required for each mode and each mode already has a transaction set for this purpose.

 


home | about CompTIA | events | press room | members only | certification | initiatives | contact us

© 2004 The Computing Technology Industry Association, Inc.
All rights reserved.