|
|
(17 intermediate revisions not shown) |
Line 1: |
Line 1: |
| [[Category:Ops]] | | [[Category:Ops]] |
| | | |
- | == Shipment == | + | == Definition for KPI drilldowns == |
| + | |
| + | a) for non Descartes TMS case: |
| + | |
| + | * [[CT]]s |
| + | * [[GRP]]s |
| | | |
- | '''Shipment''' is by definition:
| |
| * in case of Truck with TMS it is a "TMS load" | | * in case of Truck with TMS it is a "TMS load" |
| * in all other cases it is: | | * in all other cases it is: |
| ** a group of CTs (if GRP exists) or | | ** a group of CTs (if GRP exists) or |
- | ** individual CT (if it is not a part of a group)
| |
- |
| |
- | == CT ==
| |
- |
| |
- | == Master ==
| |
- |
| |
- | == MOTs defined ==
| |
- |
| |
- | MOT = Mode Of Transport.
| |
- |
| |
- | CT2 system has these MOTs defined:
| |
- |
| |
- | * Undefined
| |
- | * Air
| |
- | * LCL
| |
- | * Client Consol
| |
- | * FCL(AW)
| |
- | * FCL(MLB)
| |
- | * Truck Air
| |
- | * Truck Domestic
| |
- | * Truck Ocean
| |
- |
| |
- | == Lifecycle ==
| |
- |
| |
- | There are key [[#Events]] and key [[#Milestones]] in terms of geographical path.
| |
- |
| |
- | === Events ===
| |
- |
| |
- | * Approval or Authorization
| |
- |
| |
- | === Milestones ===
| |
- |
| |
- | ==== Origin Door ====
| |
- |
| |
- | * in CT2 called [[#Export Pick Up]]
| |
- |
| |
- | ==== Destination Door ====
| |
- |
| |
- | * truck ocean / tr dom / tr air : Gen Tab > Export Delivery To (T5)
| |
- | * Ocean / Air : Imp Tab > Delivery Address (Import Delivery Location)(T7):
| |
- |
| |
- | ==== Path ====
| |
- |
| |
- | Path for Air:
| |
- |
| |
- | * "departure" from "origin door"
| |
- | * "arrival" to origin airport
| |
- | * ""
| |
- |
| |
- |
| |
- | Key points for Ocean:
| |
- |
| |
- | === Lanes ===
| |
- |
| |
- | We have 2 different flavors of Lane term:
| |
- |
| |
- | ==== Geography From To ====
| |
- |
| |
- | Geography From To is defined as a pair {From, To} where From and To could have 3 different types of values:
| |
- |
| |
- | * Any (indicates that there is no restriction)
| |
- | * Region
| |
- | * Country
| |
- |
| |
- | ==== Shipper to Consignee Lane ====
| |
- |
| |
- | It is defined as a pair {From, To} where From = [[#Shipper]] and To = [[#Consignee]].
| |
- |
| |
- | == Fields ==
| |
- |
| |
- | === Shipper Consignee Notify ===
| |
- |
| |
- | ==== Shipper ====
| |
- |
| |
- | Gen Tab > 2. Shipper (T1):
| |
- |
| |
- | ==== Consignee ====
| |
- |
| |
- | Gen Tab > 3. Consignee (T2):
| |
- |
| |
- | ==== Notify ====
| |
- |
| |
- | Gen Tab > 4. Notify (T3):
| |
- |
| |
- | === Geography ===
| |
- |
| |
- | ==== Origin country ====
| |
- |
| |
- | Defines country of origin door and related note.
| |
- |
| |
- | '''Origin Country selector''':
| |
- |
| |
- | * [[Combobox]] with a list of countries
| |
- | * UI: Gen Tab > 11. Origin country
| |
- | * DB: tblGenericShipment.OriginPointCountryId (join with tblCountry)
| |
- | * Required? No
| |
- |
| |
- | '''Origin Country Note''':
| |
- |
| |
- | TBD
| |
- |
| |
- | ==== Destination country ====
| |
- |
| |
- | Defines country of destination door and related note.
| |
- |
| |
- | * [[Combobox]] with a list of countries
| |
- | * UI: Gen Tab > 12. Destination country
| |
- | * DB: tblGenericShipment.DestinationPointCountryId (join with tblCountry)
| |
- | * Required? No
| |
- |
| |
- | '''Destination Country selector''':
| |
- |
| |
- | TBD
| |
- |
| |
- | ==== Export Pick Up ====
| |
- |
| |
- | Defines [[#Origin Door]].
| |
- |
| |
- | * [[Combobox]] with a list + Textarea with address (pre-filled by system)
| |
- | * UI: Gen Tab > 5. Export Pick-up (T4)
| |
- | * MOTs: all
| |
- | * DB: ???
| |
- |
| |
- | === Dates ===
| |
- |
| |
- | ==== Actual Departure Date ====
| |
- |
| |
- | '''Air'''
| |
- |
| |
- | '''Ocean FCL'''
| |
- |
| |
- | Port of Loading, Actual Time of Departure (Exp Tab > 12c. ATD)
| |
- |
| |
- | '''Ocean LCL and Client Consol'''
| |
- |
| |
- | Port of Loading, Actual Time of Departure (Exp Tab > 12c. ATD)
| |
- |
| |
- | '''Trucking Domestic'''
| |
- |
| |
- | '''Trucking Air'''
| |
- |
| |
- | '''Trucking Ocean'''
| |
- |
| |
- | ''Earliest'' among Actual Collection dates in container table.
| |
- |
| |
- | ==== Actual Delivery Date ====
| |
- |
| |
- | '''Air'''
| |
- |
| |
- | '''Ocean FCL'''
| |
- |
| |
- |
| |
- |
| |
- | '''Ocean LCL and Client Consol'''
| |
- |
| |
- |
| |
- |
| |
- | '''Trucking Domestic'''
| |
- |
| |
- | '''Trucking Air'''
| |
- |
| |
- | '''Trucking Ocean'''
| |
- |
| |
- | ''Latest'' among Actual Delivery dates in container table.
| |
- |
| |
- | == Validations ==
| |
- |
| |
- | *
| |
- |
| |
- | == See Also ==
| |
- |
| |
- | * [[Shipment Milestones and Phases]]
| |
- | * [[CT]]
| |
- |
| |
- | == SOWs ==
| |
- |
| |
- | === SOW 1 Validation to ensure that commodities are assigned to containers ===
| |
- |
| |
- | mantis: '''4206'''
| |
- |
| |
- | Add validations for the session when user sets Actual Departure Date:
| |
- |
| |
- | * 0/ there should be at least one commodity line
| |
- |
| |
- | * 1/ all commodities must be assigned to containers
| |
- | ** Error message should say: "Error: Not all commodities are assigned to containers"
| |
| | | |
- | * 2/ each container of this CT records must have at least ONE commodity assigned (FCL only)
| + | b) for Descartes TMS case: ( needs to be confirmed that we still have this case !!! ) |
- | ** Error message should specify container's numbers that have no assignments
| + | |
| | | |
- | NOTE 1: Do above for Ocean MOTs only of course
| + | * TMS load |
| | | |
- | NOTE 2: Now we have similar validation when Actual Delivery date is set. Remove it.
| + | == Definition for LO and EU KPis == |
| | | |
- | Also after Actual Departure Date is set and user attempts to:
| + | We count unique lanes in the GRP as shipment. |
| | | |
- | * remove all commod lines
| + | == History of use == |
- | * change container assignments to leave one of them unassigned
| + | |
| | | |
- | system should prevent users giving error.
| + | * in the past we referred to Master as shipment as well |
| + | * originally it was used in Main report and List Shipments |
| + | * latest definition was introduced in the context of [[KPI]] module |
| + | * it is not clear that we will be able to use this term consistenly |
b) for Descartes TMS case: ( needs to be confirmed that we still have this case !!! )
We count unique lanes in the GRP as shipment.