Shipment Milestones and Phases

From UG

Revision as of 18:40, 24 August 2009 (edit) Alex (Talk | contribs) (→Simple cases per MOT) ← Older edit		Current revision as of 19:45, 28 September 2013 (edit) (undo) Alex (Talk | contribs) (→Shipment Milestone to CT2 field mapping (including dates))
(2 intermediate revisions not shown)
Line 3:		Line 3:
	Collected (oD) > Departed (oP) >  Arrived (dP) >  Delivered (dD)		Collected (oD) > Departed (oP) >  Arrived (dP) >  Delivered (dD)
		+
		+	Abbreviations:
		+
		+	* origin port(oP)
		+	* destination port(dP)
		+	* destinantion door(dD)
		+	* origin door(oD)
	== Simple cases per MOT ==		== Simple cases per MOT ==
Line 109:		Line 116:
	[[Category:Concepts]]		[[Category:Concepts]]
		+
		+
		+	== Events ==
		+
		+	There are also some events not directly related to geographical points.
		+
		+	* Approval or Authorization

---

Current revision as of 19:45, 28 September 2013

Contents 1 Collected, Departed, Arrived, Delivered chain 2 Simple cases per MOT 2.1 Air 2.2 Ocean LCL 2.3 Ocean FCL 2.4 Trucking MOTs 2.5 Ocean Trucking-Domestic 2.6 Ocean Trucking-Air 2.7 Ocean Trucking-Ocean 3 More complex cases or representations 3.1 Terminals 3.2 Trans-shipment Airport 3.3 Warehouses 4 Representation of Milestones in CT 4.1 Warning: complexity in CT2 in terms of link between milestones, dates and CT2 fields representing them 4.2 Estimated dates vs Actual 4.3 Shipment Milestone to CT2 field mapping (including dates) 5 Events

[edit] Collected, Departed, Arrived, Delivered chain

There are 4 major milestones that are applicable to all MOTs:

Collected (oD) > Departed (oP) >  Arrived (dP) >  Delivered (dD)

Abbreviations:

• origin port(oP)
• destination port(dP)
• destinantion door(dD)
• origin door(oD)

[edit] Simple cases per MOT

Note: milestone and point is the same thing in this article.

[edit] Air

• Export phase
  • {Pick-up or Collection Point}: Truck comes to pick up commodities to the "shipper's" origin door(oD) in Bayonne, NY, USA.
  • {Departure Point}: Truck brings them to Airport of Departure - origin Port(oP) in New York, NY, USA
  • commodities are loaded on the plane
• Import phase
  • {Arrival Point}: Airplane brings them to Airport Of Destination destination Port(dP) in Kiev, Ukraine
  • commodities are unloaded from the plane
  • Truck comes to pick up commodities
  • {Delivery Point}: Truck brings them to "consignee's" destinantion door(dD) in Chernobil, Ukraine

oD > oP > dP > dD

[edit] Ocean LCL

Same as air but instead of airports you have ocean ports.

oD > oP > dP > dD

[edit] Ocean FCL

I this case one shipment consists of multiple containers that travel together from origin port(oP) to destination port(dP).

But there are multiple origin doors(oD) (one per container in the most general case) and multiple destination doors(dD) (one per container in the most general case). Trucking company brings empty container to origin Door to fill it up there.

oD1 > oP > dP > dD1
oD2 >         > dD2
...             ...
oDn >         > dDn

[edit] Trucking MOTs

All trucking MOTs in CT2 cover only import segment. In this case it is assumed that export segment is covered by another freight forwarding company, not Jaguar.

[edit] Ocean Trucking-Domestic

• Truck comes to pick up commodities at {Arrival Point}
• {Delivery Point}: Truck brings them to "consignee's" destinantion door

  dP > dD

[edit] Ocean Trucking-Air

• Truck comes to pick up commodities at {Arrival Point} (which is airport in this case)
• {Delivery Point}: Truck brings them to "consignee's" destinantion door

 dP > dD

[edit] Ocean Trucking-Ocean

• Truck comes to pick up commodities at {Arrival Point} (which is ocean port in this case)
• {Delivery Point}: Truck brings them to "consignee's" destinantion door
• Note, that in CT2 we assume that it is a case with multiple containers (multiple doors)

dP > dD1
   > dD2
   ...
   > dDn

[edit] More complex cases or representations

Sometimes there more milestones that exists for the shipment path and we want to track them all. Examp[les of those: terminals, warehouses, etc.

[edit] Terminals

In case of Ocean it is possible that there are 2 additional points where goods are transferred possibly involving rail. We call them Terminals (T): origin terminal (OT) and destination terminal (DT). In this case CT path would look like this:

orig. Door > orig Terminal > orig. Port > dest. Port > dest. Terminal > Dest. Door

or

oD > oT > oP > dP > dT > dD

[edit] Trans-shipment Airport

In this case goods are transferred from one plane to another.

[edit] Warehouses

• In general or even in most cases there are also origin warehouse (oW) where goods are consolidated and destination Warehouse (dW)were goods are de-consolidated.

If you account for them then CT path would be:

oD > oW > (oT) > oP > dP > dT > dW > dD 

• IN CT2 we do not track much about them so they are mostly excluded from design, etc.

[edit] Representation of Milestones in CT

[edit] Warning: complexity in CT2 in terms of link between milestones, dates and CT2 fields representing them

It is not very easy to understand what each field means in terms of milestones or CT path.

For example, origin Door (oD) should correspond (based on how fields are labeled) to:

• GenTab.Origin Point
• GenTab.Shipper.Address
• GenTab.Export Pick-up

But it is not exactly the case.

Also fields and dates related to say oD are not grouped to gether and could be spread accross multiple tabs.

[edit] Estimated dates vs Actual

For most events we estimate dates first. Estimated date could change multiple times before actual date is set.

[edit] Shipment Milestone to CT2 field mapping (including dates)

TBD

[edit] Events

There are also some events not directly related to geographical points.

• Approval or Authorization